diff --git a/marked/Rel-18/26_series/26110/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26110/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62b3b351577cd935f38e159ee8301ca59d683ed5 --- /dev/null +++ b/marked/Rel-18/26_series/26110/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:928c05e011699969f1dbc5db97fd1fb869120d6ba49711abe49b5371f715257c +size 7548 diff --git a/marked/Rel-18/26_series/26110/e2c1c672349c10dccb2563eff6d8260e_img.jpg b/marked/Rel-18/26_series/26110/e2c1c672349c10dccb2563eff6d8260e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41002fc0a8da309a91bdb63791264a2bcf99c803 --- /dev/null +++ b/marked/Rel-18/26_series/26110/e2c1c672349c10dccb2563eff6d8260e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e7b62aae00af3b7a6291875695a75a3ebf67eb34432194ba1cb5d1e7498ac24 +size 95614 diff --git a/marked/Rel-18/26_series/26110/raw.md b/marked/Rel-18/26_series/26110/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c33d2422b2da71da461a11860f3c0f91fdc5fe4d --- /dev/null +++ b/marked/Rel-18/26_series/26110/raw.md @@ -0,0 +1,407 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Codec for circuit switched multimedia telephony service; General description (Release 18)** + +![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 3GPP logo features the letters '3GPP' in a stylized, bold font. The '3' is black, the 'G' is black with a red signal icon at its base, the 'P' is black, and the 'P' is black with a small 'TM' symbol to its right. + +3GPP logo + +A GLOBAL INITIATIVE + +## --- **Keywords** + +UMTS, codec, telephony, circuit mode, +multimedia + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 7 | +| 5 ITU-T H.324 ..... | 8 | +| 6 Modifications to H.324 (3GPP TS 26.111)..... | 8 | +| 7 Call set-up requirements ..... | 8 | +| 8 Terminal implementor's guide (3GPP TR 26.911) ..... | 8 | +| Annex A (informative): Background information ..... | 9 | +| A.1 Video I/O Equipment..... | 9 | +| A.2 Video Codec..... | 9 | +| A.2.1 H.261 ..... | 10 | +| A.2.2 H.263 ..... | 10 | +| A.2.3 MPEG-4 ..... | 10 | +| A.3 Audio I/O Codec ..... | 10 | +| A.4 Speech Codec..... | 10 | +| A.4.1 3GPP AMR ..... | 10 | +| A.4.2 G.723.1 ..... | 11 | +| A.5 User Data Applications ..... | 11 | +| A.5.1 Data conferencing – T.120 ..... | 11 | +| A.5.2 Text conversation – T.140..... | 12 | +| A.6 Data Protocols..... | 12 | +| A.7 System Control..... | 12 | +| A.8 Call Set-up..... | 12 | +| A.9 H.245..... | 12 | +| A.10 H.223..... | 12 | +| A.10.1 Level 0..... | 13 | +| A.10.2 Level 1..... | 13 | +| A.10.3 Level 2..... | 13 | +| A.10.4 Level 3..... | 13 | +| Annex B (informative): Bibliography ..... | 13 | +| Annex C (informative): Change history..... | 14 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +The present document introduces the set of specifications which apply to 3G-324M multimedia terminals within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 3.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- Introduction + +This document contains a specification for H.324 based multimedia codecs for circuit switched 3GPP networks. The term codec is usually associated with a single media type. However, many multimedia services require a close integration of disparate media types. In this sense, the representations of these media types (in the form of media streams) are at least logically bound into a single multimedia stream. As such, a H.324 based multimedia codec must handle multiplexing/de-multiplexing and skew. It will also have to provide codecs for each of the derived media streams. End-to-end, in-band control is also required for the purposes of configuration and establishing individual media streams. Finally, since 3GPP networks are inherently error prone, error detection and/or correction must also be provided by the multimedia codec since it has a comprehensive view of the bit stream it produces and therefore can apply the most efficient form of error detection and/or correction. + +# --- 1 Scope + +This specification introduces the set of specifications which apply to 3G-324M multimedia terminals. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] ITU-T Recommendation H.223: "Multiplexing protocol for low bitrate multimedia communication" +- [2] ITU-T Recommendation H.223 — Annex A: "Multiplexing protocol for low bitrate multimedia communication over low error-prone channels" +- [3] ITU-T Recommendation H.223 — Annex B: "Multiplexing protocol for low bitrate multimedia communication over moderate error-prone channels" +- [4] ITU-T Recommendation H.223 — Annex C: "Multiplexing protocol for low bitrate multimedia communication over highly error-prone channels" +- [5] ITU-T Recommendation H.223 — Annex D: "Optional multiplexing protocol for low bitrate multimedia communication over highly error-prone channels" +- [6] ITU-T Recommendation H.245: "Control protocol for multimedia communication" +- [7] ITU-T Recommendation G.723.1: "Dual rate speech coder for multimedia communication transmitting at 5.3 & 6.3 kbit/s" +- [8] ITU-T Recommendation H.263: "Video coding for low bitrate communication" +- [9] ITU-T Recommendation H.261: "Video CODEC for audiovisual services at p X 64 kbit/s" +- [10] ITU-T Recommendation H.324: "Terminal for low bitrate multimedia communication" +- [11] 3GPP TS 26.111: "Modifications to H.324" +- [12] 3GPP TR 26.911: "Terminal Implementor's Guide" +- [13] ITU-T Recommendation X.691: "Information Technology - ASN.1 Encoding Rules - Specification of Packed Encoding Rules (PER)" +- [14] International Standard ISO/IEC 14494-2: "Information technology — Generic coding of audiovisual object — Part 2: Visual, 1999" +- [15] 3GPP TS 26.071: "Mandatory Speech Codec; General Description" +- [16] 3GPP TS 26.090: "Mandatory Speech Codec; Speech Transcoding Functions" +- [17] 3GPP TS 26.073: "Mandatory Speech Codec; ANSI C-Code" +- [18] ITU-T T.140 (1998) Presentation protocol for text conversation application. +- [19] 3GPP TS 22.226: "Global Text Telephony; Stage 1" + +- [20] 3GPP TS 24.008: "Mobile Radio Interface - Layer 3 MM/CC Specification". +- [21] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [22] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [23] 3GPP TS 23.108: "Mobile radio interface layer 3 specification; Core Network protocols; stage 2". +- [24] ITU-T Recommendation G.712: "Transmission performance characteristics of pulse code modulation channels". +- [25] ITU-T Recommendation T.120: "Data protocols for multimedia conferencing". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**H.324 terminal:** ITU-T H.324 recommendation, including Annex C + +**3G-324M terminal:** Based on ITU-T H.324 recommendation modified by 3GPP for purposes of 3GPP circuit switched network based video telephony + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|---------------------------------------------------| +| ACELP | Algebraic-Code-Excited Linear-Prediction | +| ADC | Analogue Digital Converter | +| AEC | Acoustic Echo Cancellation | +| AL | Adaptation Layer | +| CCSRL | Control Channel Segmentation and Reassembly Layer | +| CELP | Code-Excited Linear-Prediction | +| CT | Correlation Threshold | +| DAC | Digital Analogue Converter | +| DCT | Discrete Cosine Transformation | +| EI | Error Indication | +| EOB | End Of Block | +| FEC | Forward Error Correction | +| GOB | Group Of Blocks | +| GQUANT | Group Quantizer information | +| GTT | Global Text Telephony | +| HDLC | High-Level Data Link Control | +| HEC | Header Error Control | +| ISDN | Integrated Services Digital Network | +| LAPM | Link Access Procedure for Modems | +| LC | Logical Channel | +| MC | Multiplex Code | +| MCU | Multipoint Communication Unit | +| MP-MLQ | Multipulse Maximum Likelihood Quantization | +| MPL | Multiplex Payload Length | +| MR-ACELP | Multi-rate ACELP | +| PC | Personal Computer | +| MCU | Multipoint Conference Unit | +| MUX | H.223 Multiplex layer | +| PDU | Protocol Data Unit | + +| | | +|-----|----------------------| +| SN | Sequence Number | +| VLC | Variable Length Code | + +# 4 General + +3G-324M terminals provide real-time video, audio, or data, in any combination, including none, over 3GPP circuit-switched, radio networks. They are based on ITU-T H.324 with Annex C, and Annex H when mobile multilink operation is supported. Communication may be either 1-way or 2-way. Such terminals may be part of a portable device or integrated into an automobile or other non fixed location device. They may also be fixed, stand-alone devices; for example, a video telephone or kiosk. 3G-324M terminals may also be integrated into PCs and workstations. + +In addition to 3G-324M to 3G-324M communication, interoperation with other types of multimedia telephone terminals is possible, however a gateway may be required. + +Multipoint communication between more than two 3G-324M terminals is possible using a Multipoint Communication Unit (MCU). MCU functionality is for further study. + +3G-324M terminals are based on ITU-T H.324 with Annex C, and Annex H when mobile multilink operation is supported. For performance reasons and to reference the call set-up procedures, some modifications to H.324 were made. These are described in 3GPP TS 26.111, except call set-up procedures are described in 3GPP TS 24.008, 27.001, 29.007 and 23.108. 3G-324M terminals shall conform to these specifications. Because of the many options in H.324, an implementor's guide, 3GPP TR 26.911, provides preferred options for 3G-324M implementations. + +Figure 1 below shows the functional components of a generic 3GPP multimedia terminal. The video, speech, data and multilink components are optional. If a media type is supported, the standards indicated are mandatory except those enclosed in square brackets are optional. + +![Figure 1: Scope of circuit switched multimedia 3GPP specification. This block diagram illustrates the functional components of a generic 3GPP multimedia terminal. On the left, external components include Video I/O Equipment, Audio I/O Equipment, User Data Applications [T.120, ...], and System Control. These connect to internal processing blocks: Video Codec (H.263, [MPEG-4, H.261 ...]), Speech Codec (3GPP-AMR, [G.723.1 ...]), Data Protocols [V.14, LAPM, ...], H.245, CCSRL, and NSRP[LAP M/V.42]. An Optional Receive Path Delay is shown between the Speech Codec and the Multiplex/Demultiplex block. All internal blocks connect to a central Multiplex/Demultiplex block (H.223, H.223 Annex A, H.223 Annex B, [H.223 Annex C, H.223 Annex D]). This block connects to an Optional Multilink block (H.324 Annex H), which in turn connects to the 3GPP Network. The System Control block also connects to a Call Set-up block, which is connected to the 3GPP Network.](e2c1c672349c10dccb2563eff6d8260e_img.jpg) + +Figure 1: Scope of circuit switched multimedia 3GPP specification. This block diagram illustrates the functional components of a generic 3GPP multimedia terminal. On the left, external components include Video I/O Equipment, Audio I/O Equipment, User Data Applications [T.120, ...], and System Control. These connect to internal processing blocks: Video Codec (H.263, [MPEG-4, H.261 ...]), Speech Codec (3GPP-AMR, [G.723.1 ...]), Data Protocols [V.14, LAPM, ...], H.245, CCSRL, and NSRP[LAP M/V.42]. An Optional Receive Path Delay is shown between the Speech Codec and the Multiplex/Demultiplex block. All internal blocks connect to a central Multiplex/Demultiplex block (H.223, H.223 Annex A, H.223 Annex B, [H.223 Annex C, H.223 Annex D]). This block connects to an Optional Multilink block (H.324 Annex H), which in turn connects to the 3GPP Network. The System Control block also connects to a Call Set-up block, which is connected to the 3GPP Network. + +**Figure 1** Scope of circuit switched multimedia 3GPP specification. Items in [brackets] are optional. + +Short descriptions of ITU-T H.324, 3GPP TS 26.111, and 3GPP TR 26.911 are given below. + +# --- 5 ITU-T H.324 + +ITU-T H.324 describes terminals for low bitrate multimedia communication. That ITU-T recommendation contains "ANNEX C, Multimedia Telephone Terminals Over Error Prone Channels" (sometimes referred to as H.324/M) and "ANNEX H, Mobile Multilink Operation". These annexes are considered an integral part of the recommendation. Therefore, herewith H.324 shall mean ITU-T H.324 with Annex C. When multilink operation is utilized, H.324 shall also mean to include H.324 Annex H. + +Originally designed for V.34 modems, H.324 now supports ISDN and wireless networks. Therefore, it is well suited as a basis for 3GPP multimedia codecs. Relevant to wireless networks, H.324 describes the overall system architecture and introduces control (H.245), mux (H.223), video (H.261 and H.263), text (T.140), and audio (G.723.1). + +Annex A provides a short overview of H.324 and multimedia codecs. + +# --- 6 Modifications to H.324 (3GPP TS 26.111) + +To enable cost-effective, high-quality H.324 terminals for 3GPP networks, some modifications were made to H.324. These modifications are described in 3GPP TS 26.111. Terminals adhering to this specification are herewith known as 3G-324M terminals. 3G-324M terminals shall conform to 3GPP TS 26.111. + +# --- 7 Call set-up requirements + +H.324 does not describe call set-up procedures for 3GPP networks. These are described in 3GPP TS 24.008, 27.001, 29.007, 23.108 and shall be used for 3G-324M terminals. + +# --- 8 Terminal implementor's guide (3GPP TR 26.911) + +A successful 3G-324M terminal will have to function well at bandwidths as low as 32 KBPS and in potentially high error rate environments. 3G-324M contains many options that may be employed by an implementor. To help choose which options and combinations of options are useful, an implementor's guide is provided in 3GPP TR 26.911. + +# --- Annex A (informative): Background information + +The section is intended for informational purposes only. This is not an integral part of this specification. Each section below relates to the functional components in figure 1. + +## --- A.1 Video I/O Equipment + +For a video telephone this would most likely consist of a video camera and display monitor. Other possible input sources could be a VCR or disk drive. While most applicable I/O equipment relies on a standard format for the video signal or bit stream, this format is likely to differ from that mandated by the video codec. In such cases, circuitry or software is used to transcode between the two formats. + +## --- A.2 Video Codec + +ITU-R 601 (NTSC or PAL) is a typical video input signal and represents a bit stream of 20.7 Mbyte/s for the actual image (excluding blanking intervals). The first order of compression occurs by reducing the resolution of the input signal.1 For example, CIF resolution at 30 fps produces a bit stream 4.6 Mbyte/s. Additional savings occur by dropping frames. In a videoconference, where motion is relatively slow, 10 fps is considered adequate. Thus, the original signal of 20.7 Mbytes/s could be reduced to 1.5 Mbyte/s with just these techniques. However, this is still 188 times greater than can be transmitted on, for example, a 64 KBPS channel. Substantial compression is still required, especially considering that framing, control, and audio would as well require a portion of the available bandwidth. + +To achieve the degree of compression required for video telephony, all of the video codecs that can currently be employed in a 3GPP multimedia codec use a combination of spatial and temporal redundancy reduction to reduce the bandwidth required by the video media stream. Spatial redundancy can be reduced by converting the input signal from the time domain to the frequency domain using a DCT. This produces a DC value and other coefficients, where most of the scene energy is concentrated in the coefficients corresponding to the lower frequencies. Next, a coarse quantizer is applied (which, in this domain, has little effect on image quality). This results in many of the coefficients being encoded to 0. The significant coefficients are encoded to a much smaller range of values. The coefficients are then reordered so that, typically, the larger magnitude values will occur first followed by 0 value coefficients. Finally, the coefficients are replaced with a count of the number of zero value coefficients followed by the value of a nonzero coefficient. This combination is translated into a VLC. Applying this type of compression to the entire video frame produces an intra frame. + +Despite the efficiency of intra coding, significantly more compression is required. In addition to removing spatial redundancy, all video codecs apply temporal reduction as well. This is achieved by comparing the current frame to the previous and estimating the set of vectors which when applied to their respective areas of the scene would create the new, current frame based on the old, previous frame. The match is usually not perfect, so an error component is transmitted as well. The error component is also transformed to the frequency domain, so the same compression efficiency achieved in the intra frame is achieved here as well — enhanced by the fact the range of error coefficients is less than intra coefficients. Since generally only a few areas of a scene change from frame to frame, high compression can be achieved by sending a series of inter frames. If the error component for a particular block is too large, it can be encoded as an intra block. + +Since, by their nature, VLCs are not fixed length, a single bit error can make it impossible to decode an entire frame. Unfortunately, each inter coded frame relies on its previous frame to be decoded. Thus, a single bit error can destroy the entire remaining bit stream. Video codecs have various ways of handling errors. The simplest is to use error detection to determine if a frame contains an error. The transmitter is then signalled that an error occurred. It then sends an intra coded frame, which does not depend on any previous frames. This approach consumes considerable bandwidth and is only practical for very low error networks. Other, more sophisticated schemes are available using the video codecs available to 3G-324M terminals. + +--- + +1 Note that ITU-R 601 represents 16 bit precision colour, whereas true colour is usually considered to require 24 bit precision. Also, the spatial resolution of ITU-R 601 is substantially less than can be achieved with normal human vision. + +### A.2.1 H.261 + +H.261 supports CIF and QCIF images as input. It provides good video quality at 64 kbit/s or higher. It uses BCH codes for Forward Error Correction (FEC). However, this is not recommended for H.324. + +### A.2.2 H.263 + +H.263 is an extension of H.261. It allows sub-QCIF, 4CIF and 16CIF as additional input formats. H.263, in its original version, provides four annexes that describe optional modes for enhanced coding. + +- Advanced prediction mode (Annex F) provides half-pel motion estimation, median-based motion vector prediction, 4 motion vectors per macroblock (one per block), and overlapped block motion compensation +- Unrestricted motion vectors (Annex D) work in conjunction with advanced prediction mode and allow motion vectors to point outside the picture area +- Arithmetic coding (Annex E) can be used instead of variable length coding +- PB-frames (Annex G) allow bi-directional prediction similar to MPEG + +Other significant differences exist, but require a level of detail to explain that renders them outside the scope of this document. + +A second version of H.263 (known as H.263+) adds annexes I through T, some of which address error prone environments and are therefore of special interest to 3GPP multimedia codecs. + +### A.2.3 MPEG-4 + +MPEG-4 Visual (ISO/IEC 14496-2) is a generic video codec. One of its target areas is mobile communications. Error resiliency and high efficiency make this codec particularly well suited for 3G-324M. + +MPEG-4 Visual is organised into Profiles. Within a Profile, various Levels are defined. Profiles define subsets of tool sets. Levels are related to computational complexity. Among these Profiles, Simple Visual Profile provides error resilience (through data partitioning, RVLC, resynchronization marker and header extension code) and low complexity. + +MPEG-4 allows various input formats, including general formats such as QCIF and CIF. It is also baseline compatible with H.263. + +## --- A.3 Audio I/O Codec + +Generally, a video telephone would require a handset, headset, or microphone and speaker. Often, integrated circuits are employed that convert the typically analogue input signal to a PCM format bit stream (ADC) and convert PCM to an analogue signal for acoustic output (DAC). This is helpful since many speech codecs use PCM for input and output. Video telephones often use a separate microphone and speaker. This allows the user to be seen without a handset or headset. However, if this is so, AEC will be required. + +## --- A.4 Speech Codec + +### A.4.1 3GPP AMR + +The AMR codec uses eight source codecs with bit-rates of 12.2, 10.2, 7.95, 7.40, 6.70, 5.90, 5.15 and 4.75 kbit/s. The coder operates on speech frames of 20 ms corresponding to 160 samples at the sampling frequency of 8000 sample/s. It performs the mapping from input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits and from encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits to output blocks of 160 reconstructed speech samples. The coding scheme for the multi-rate coding modes is the so-called Algebraic Code Excited Linear Prediction Coder (ACELP). The multi-rate ACELP coder is referred to as MR-ACELP. + +At each 160 speech samples, the speech signal is analysed to extract the parameters of the CELP model (LP filter coefficients, adaptive and fixed codebooks' indices and gains). These parameters are encoded and transmitted. At the decoder, these parameters are decoded and speech is synthesised by filtering the reconstructed excitation signal through the LP synthesis filter. + +The adaptive multi-rate speech codec is described in a bit-exact arithmetic in form of a fixed-point ANSI-C code to allow for easy type approval as well as general testing purposes of the adaptive multi-rate speech codec. + +The DTX mechanism includes a Voice Activity Detector (VAD) on the TX side; evaluation of the background acoustic noise on the TX side, in order to transmit characteristic parameters to the RX side; and generation of comfort noise on the RX side during periods where the radio transmission is turned off. + +The AMR specification contains error concealment. The purpose of frame substitution is to conceal the effect of lost AMR speech frames. The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user and to avoid generating possible annoying sounds as a result from the frame substitution procedure. + +### A.4.2 G.723.1 + +G.723.1 can be used for compressing the speech or other audio signal component of multimedia services at a very low bitrate as part of H.324. This coder has two bit-rates associated with it, 5.3 and 6.3 kbit/s. The higher bitrate has greater quality. The lower bit-rate gives good quality and provides system designers with additional flexibility. Both rates are a mandatory part of the encoder and decoder. It is possible to switch between the two rates at any frame boundary. An option for variable rate operation using discontinuous transmission and noise fill during non-speech intervals is also possible using a series of silence frames or a single silence frame followed by no frames until speech is detected. + +G.723.1 encodes speech or other audio signals in frames using linear predictive analysis-by-synthesis coding. The excitation signal for the high rate coder is Multipulse Maximum Likelihood Quantization (MP-MLQ) and for the low rate coder is Algebraic-Code-Excited Linear-Prediction (ACELP). The frame size is 30 ms and there is an additional look ahead of 7.5 msec,. This coder is designed to operate with a digital signal obtained by first performing telephone bandwidth filtering (ITU-T Recommendation G.712) of the analogue input, then sampling at 8000 Hz and then converting to 16-bit linear PCM for the input to the encoder. The output of the decoder is converted back to analogue by similar means. + +G.723.1 has been designed to be robust for indicated frame erasures. An error concealment strategy for frame erasures has been included in the decoder. However, this strategy must be triggered by an external indication that the bit stream for the current frame has been erased. This can be achieved in H.324 using the AL2 Error Indication (EI) flag and the optional AL2 Sequence Number (SN). Because the coder was designed for burst errors, there is no error correction mechanism provided for random bit errors. If a frame erasure has occurred, the decoder switches from regular decoding to frame erasure concealment mode. + +G.723.1 contains three annexes. Annex A describes the silence compression system designed for the G.723.1 speech coder (mentioned above). Annex B describes an alternative implementation of G.723.1 contained in floating point C source code. Annex C specifies a channel coding scheme which can be used with the triple rate speech codec G.723.1. The channel codec is scalable in bit-rate and is designed for mobile multimedia applications as a part of the overall H.324 family of standards. + +## --- A.5 User Data Applications + +### A.5.1 Data conferencing – T.120 + +An example of a User Data Application is T.120. This protocol allows multipoint data conferencing that includes data and image transferral. Other functions, such as shared whiteboards and applications, are possible. + +### A.5.2 Text conversation – T.140 + +The real time text conversation application, is supported by the presentation protocol ITU-T T.140 [19]. The Global Text Telephony feature is implemented in the CS Multimedia environment by applying T.140, as specified in H.324. + +The text stream may be opened simultaneously with voice, video and other data applications. Text-only sessions are also possible. Further requirements applicable to the Global Text Telephony feature are specified in TS 22.226 [20]. + +The data protocol for T.140 is specified in H.324 to be AL1. + +## --- A.6 Data Protocols + +Various data protocols can be supported. These always support data applications (see A.5 User Data Applications). A specific protocol or set of protocols is often stipulated by the data application. Each protocol provides varying degrees of error detection and/or correction. + +## --- A.7 System Control + +In general, system control constitutes the overall state machine for the terminal. It usually has to be aware of when a connection has been established. At that point it can begin H.245 procedures such as master/slave determination, capabilities exchange, and opening logical channels. Upon call termination, either initiated at the near or far ends, system control generally initiates H.245 end session procedures. + +## --- A.8 Call Set-up + +All out-of-band network signalling for the purpose of call control is handled by call set-up, which is usually implemented as a state machine. This includes initiating, answering, and tearing down calls. + +## --- A.9 H.245 + +H.245 specifies the syntax and semantics for in-band, terminal-to-terminal control messages and the procedures for their use. Most importantly, H.245 is used for master/slave determination, capabilities exchange, H.223 mux table transmission, and opening and closing logical channels. There is also a large array of general control and indication messages. H.245 addresses a wide range of terminals and applications. Therefore, only a subset of the messages listed in H.245 pertain to 3G-324M terminals. Messages fall into one of four categories: Request (requires a Response), Response (in response to a Request), Command (requires an action), and Indication (informative only). + +H.245 messages are carried on a single logical channel within the H.223 mux. This channel is labelled LC 0 and is considered to be open upon establishing digital communications end-to-end and survives until digital communication is terminated. Due to the characteristics of the H.223 mux, bandwidth for H.245 messages is allocated on an as-needed basis. Since most H.245 traffic occurs at the beginning and end of the session, this conserves much needed bandwidth for video and audio. Error control is not provided for within H.245 and is specified elsewhere. + +## --- A.10 H.223 + +H.223 describes the multiplexing protocol used between H.324 terminals. It is packet oriented and each packet can contain a subset of a maximum of 65536 LCs. Each LC represents a single media, information, or control channel. The H.223 protocol is split into two layers, the lowest being the Multiplex Layer. + +The Multiplex Layer exchanges data with the end terminal via MUX-PDUs. Multiplex table entries, of which there are 16 (and can be changed during a session), describe which octets from within the PDU are allocated to which logical channels. The multiplex table entry employed for a particular PDU is indicated by the 4 bit MC field in the MUX-PDU header. MUX-PDUs contain an integer number of octets. Errors within the MUX-PDU header are controlled using the HEC field in the MUX-PDU header. H.324 terminals utilising the V.34 transmission protocol frame MUX-PDUs with HDLC. Bit stuffing is used for data transparency in this case. + +Above the Multiplex Layer is the Adaptation Layer, of which there are three different types. + +- 1) AL1 is designed primarily for control information and data protocols. It can be either framed or unframed and does not provide any error control. +- 2) AL2 is designed primarily for the transfer of digital audio. AL2 PDUs contain 1 octet for an 8-bit CRC and an optional octet for a sequence number. +- 3) AL3 is designed primarily for the transfer of digital video. AL3 PDUs contain 2 octets for a 16-bit CRC. There is also optionally 1 or 2 octets for control. AL3 also allows limited retransmission. + +For purposes of video telecommunications over wireless networks, four annexes to H.223 have been created. These create four levels of error detection and error correction. + +### A.10.1 Level 0 + +Level 0 applies to H.223 as described above. + +### A.10.2 Level 1 + +Level 1, described in Annex A, replaces HDLC framing with 1 or 2 16 bit flags. Unlike HDLC, Level 1 does not guarantee data transparency. However, if the MUX-PDU header is constructed in such a way as to make emulating the Level 1 framing flags impossible, data transparency can be achieved by correctly decoding the MUX-PDU. Should there be an error in the MUX-PDU header, resynchronization techniques will have to be applied. + +### A.10.3 Level 2 + +Level 2, described in Annex B, uses the same framing as Level 1, but utilises a 3 octet header. This header starts with a 4 bit MC, which is the same as in Level 0. This is followed by an 8-bit MPL-field, with a range of values 0 – 254. Lastly, a 12 bit extended Golay code is used for parity bits. The PM in Level 2 is signalled through the polarity of the MUX-PDU flag. If the output of the correlator is greater than or equal to CT, the PM is 0. If it is less than or equal to -CT, the PM equals 1. After the parity bits, there can be an optional MUX-PDU header for the previous (corrupted) MUX-PDU. This 1 octet field uses the format described in Level 0. Level 2 also offers enhanced packet resynchronization. + +### A.10.4 Level 3 + +Level 3, described in Annexes C and D, provides error correction capabilities at the mux level. + +# --- Annex B (informative): Bibliography + +(void) + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 06-1999 | 04 | | | | Approved at TSG-SA#4 | | 3.0.0 | +| 09-2000 | 09 | SP-000395 | 001 | | CS Multimedia Codec specification for real time text conversation | 3.0.1 | 4.0.0 | +| 03-2001 | 011 | SP-010105 | 002 | 1 | Support of mobile multi-link operation in 3G-324M | 4.0.0 | 4.1.0 | +| 03-2001 | 011 | SP-010105 | 004 | 1 | Correction of incorrect reference | 4.0.0 | 4.1.0 | +| 06-2002 | 016 | | | | Version for Release 5 | 4.1.0 | 5.0.0 | +| 12-2004 | 026 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 036 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | 042 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | 046 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 051 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 057 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 09-2014 | 065 | | | | Version for Release 12 | 11.0.0 | 12.0.0 | +| 12-2015 | 070 | | | | Version for Release 13 | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | 75 | | | | | Version for Release 14 | 14.0.0 | +| 2018-06 | 80 | | | | | Version for Release 15 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26111/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26111/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b5d3c69188a610f911a95b8cce8fd4fc6427691 --- /dev/null +++ b/marked/Rel-18/26_series/26111/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:375b2e8bd44894e45839805267b6f566324eee8394026b9f244fcacdd3281b6d +size 7587 diff --git a/marked/Rel-18/26_series/26111/raw.md b/marked/Rel-18/26_series/26111/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..abb329992cf9b30a888a5c15c401532313c3eb26 --- /dev/null +++ b/marked/Rel-18/26_series/26111/raw.md @@ -0,0 +1,378 @@ + + +# 3GPP TS 26.111 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Codec for circuit switched multimedia telephony service; Modifications to H.324 (Release 18)** + +![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 3GPP logo features the letters '3GPP' in a stylized, bold font. The '3' is black, the 'G' is black with a red signal icon at its base, the 'P' is black, and the 'P' is black with a red signal icon at its base. A small 'TM' trademark symbol is located to the right of the 'P'. + +3GPP logo + +A GLOBAL INITIATIVE + +## --- **Keywords** + +UMTS, telephony, multimedia, codec, +circuit mode + +## **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 5 Document structure ..... | 6 | +| 6 Functional requirements..... | 7 | +| 6.1 Required elements ..... | 7 | +| 6.2 Information streams..... | 7 | +| 6.3 Modem ..... | 7 | +| 6.4 Multiplex ..... | 7 | +| 6.5 Control channel ..... | 7 | +| 6.6 Video channels ..... | 7 | +| 6.6.1 MPEG-4 interface to multiplex ..... | 10 | +| 6.6.2 H.264 (MPEG-4 AVC) interface to multiplex ..... | 10 | +| 6.7 Audio channels..... | 11 | +| 6.8 Data channels ..... | 11 | +| 7 Terminal procedures ..... | 11 | +| 8 Optional enhancements ..... | 11 | +| 9 Interoperation with other terminals..... | 11 | +| 10 Multipoint considerations ..... | 11 | +| 11 Maintenance..... | 12 | +| Annex A (informative): Change History..... | 13 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +In the present document is described additions, deletions, and changes made to ITU-T Recommendation H.324 [10] with annex C for the purpose of using that recommendation as a basis for the technical specification for circuit switched multimedia service in 3GPP networks. The present document does not address call setup procedures, but references to the specifications which cover call setup are found in 3GPP TS 26.110 [11]. + +# --- 1 Scope + +In ITU-T Recommendation H.324 [10] with annex C describes a generic multimedia codec for use in error-prone, wireless networks. The scope of the present document are the changes, deletions, and additions to those texts necessary to fully specify a multimedia codec for use in 3GPP networks. Note that this implicitly excludes the network interface and call setup procedures. Also excluded are any general introductions to the system components. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] ITU-T Recommendation H.223: "Multiplexing protocol for low bit rate multimedia communication". +- [2] ITU-T Recommendation H.223 - Annex A: "Multiplexing protocol for low bit rate multimedia mobile communication over low error-prone channels". +- [3] ITU-T Recommendation H.223 - Annex B: "Multiplexing protocol for low bit rate multimedia mobile communication over moderate error-prone channels". +- [4] ITU-T Recommendation H.223 - Annex C: "Multiplexing protocol for low bit rate multimedia mobile communication over highly error-prone channels". +- [5] ITU-T Recommendation H.223 - Annex D: "Optional multiplexing protocol for low bit rate multimedia mobile communication over highly error-prone channels". +- [6] ITU-T Recommendation H.245: "Control protocol for multimedia communication". +- [7] ITU-T Recommendation G.723.1: "Dual rate speech coder for multimedia communication transmitting at 5,3 and 6,3 kbit/s". +- [8] ITU-T Recommendation H.263: "Video coding for low bitrate communication". +- [9] ITU-T Recommendation H.261: "Video CODEC for audiovisual services at px64 kbit/s". +- [10] ITU-T Recommendation H.324: "Terminal for low bitrate multimedia communication". +- [11] 3GPP TS 26.110: "Codec for Circuit Switched Multimedia Telephony Service; General description". +- [12] 3GPP TR 26.911: "Codec for circuit switched multimedia telephony service; terminal implementor's Guide (Release 4)". +- [13] ITU-T Recommendation X.691: "Information Technology - ASN.1 Encoding Rules - Specification of Packed Encoding Rules (PER)". +- [14] ISO/IEC 14496-2: "Information technology - Coding of audio-visual objects - Part 2: Visual". +- [15] 3GPP TS 26.071: "General description". +- [16] 3GPP TS 26.090: "Transcoding functions". + +- [17] 3GPP TS 26.073: "Adaptive Multi-Rate (AMR); ANSI C source code". +- [18] 3GPP TS 26.171: "AMR Wideband Speech codec; General Description". +- [19] ITU-T Recommendation H.264 (2003): "Advanced video coding for generic audiovisual services" | ISO/IEC 14496-10:2003: "Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding". +- [20] ITU-T Recommendation H.241 (2003): "Extended video procedures and control signals for H.300 series terminals". +- [21] ITU-T Recommendation G.722.2 Annex F (2002): "AMR-WB usage in H.245". +- [22] 3GPP TS 26.201 : "Adaptive Multi-Rate – Wideband (AMR-WB) speech codec ; Frame Structure." + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**H.324:** ITU-T H.324 [10] with annex C + +**3G-324M terminal:** based on ITU-T H.324 [10] recommendation modified by 3GPP for purposes of 3GPP circuit switched network based video telephony + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|------------------------------| +| AMR | Adaptive Multi-Rate | +| AMR-WB | AMR Wide-Band | +| AVC | Advanced Video Codec | +| FLC | Fixed Length Code | +| RVLC | Reverse Variable Length Code | +| DP | Data Partitioning | +| RM | Resynchronization Marker | +| MCU | Multipoint Control Unit | + +# --- 4 General + +The present document contains any deviations to ITU-T H.324 [10] required for the specification of 3G-324M Terminals. + +# --- 5 Document structure + +The structure of H.324 [10] is followed in the present document. Where there are no differences in a specific section, that section is skipped. Where differences are minor, only the differences are described. Where major differences exist, the section is rewritten in the present document. It is important to note that for wireless terminals, Annex C of H.324 [10] supersedes respective portions of the main body of H.324 [10] For the present document, these modifications are treated as if they are part of the main body of H.324 [10] Therefore, a reader must keep in mind both the main body and Annex C of H.324 [10] when reading the present document. + +# 6 Functional requirements + +## 6.1 Required elements + +3G-324M implementations are not required to have each functional element except a wireless interface, H.223 [1] with Annex A and B multiplex, and H.245 [6] version 3 or later versions for system control protocol. + +3G-324M terminals offering audio communication shall support the AMR audio codec. Support for G.723.1 [7] is not mandatory, but recommended. + +3G-324M terminals offering video communication shall support the H.263 [8] video codec. Support for MPEG-4 simple profile and H.261 [9] is optional. + +3G-324M terminals shall support H.223 [1] with annex A and annex B. + +3G-324M terminals shall support at least 32 kbit/s minimum bit rate at the mux to wireless network interface. + +## 6.2 Information streams + +V.25ter discussion does not apply. + +## 6.3 Modem + +Does not apply. + +## 6.4 Multiplex + +3G-324M terminals shall support H.223 [1] with annex A and annex B. All other aspects shall follow H.324 [10] with annex C. H.223 [1] Annex C and D are optional. + +## 6.5 Control channel + +No differences with H.324 [10]. + +Should it not be possible to signal an element of the 3G-324M terminal using a published version of H.245 [6], a procedure will be defined here. + +## 6.6 Video channels + +Support for H.261 [9] is optional. + +Support for MPEG-4 Visual is optional. When supported, MPEG-4 Visual codecs shall support Simple Profile @ Level 0. The FLC code 0000 1000 in Table G-1 – "FLC table for profile\_and\_level\_indication" in ISO/IEC 14496-2 [14] is assigned to it. Additional information can be found in [14]. + +MPEG-4 Visual Simple Profile @ level 0 provides error concealment as part of the simple profile through Data Partitioning (DP), Reversible Variable Length Coding (RVLC), Resynchronization Marker (RM) and header extension code. MPEG-4 Visual is baseline compatible with H.263 [8]. + +When opening a logical channel for MPEG-4 Visual, configuration information (Visual Object Sequence Header, Visual Object Header, and Video Object Layer Header) shall be sent in the decoderConfigurationInformation parameter. The same information shall also be sent in the MPEG-4 video bitstream. If the operational mode of MPEG-4 Visual encoder needs to be changed, the existing MPEG-4 video logical channel shall be closed and H.245 [6] procedures for opening a new MPEG-4 video logical channel shall be started. The new operational mode shall be indicated in the parameters of the new logical channel. + +Support for H.264 (MPEG-4 AVC) [19] is optional. When supported, H.264 codecs shall support Baseline level 1, without requirements on output timing conformance (Annex C of [19]). + +Support for H.264 [19] shall be signalled according to H.241 chapter 8 "Capability Exchange signalling" [20]. + +When opening a logical channel for H.264 [19], initial sequence parameter set(s) and picture parameter set(s) should be sent in a H.264 DecoderConfigurationInformation (DCI) defined in Table 1 below, amending H.241 parameters [20]. Additionally, decoder capabilities may be sent in a H.264 AcceptRedundantSlices and a H.264 ProfileIOP defined in Table 2 and 3 below, amending H.241 parameters [20]. + +NOTE: The H.264 DCI parameter can also be used when either party signals a H.245 [6] MasterSlaveDetermination terminalType parameter greater than 128, such as e.g. a Multipoint Conference Unit (MCU). + +A sequence parameter set or a picture parameter set with a particular value of seq\_parameter\_set\_id or pic\_parameter\_set\_id, respectively, sent in the H.264 [19] DCI shall be identical to the earliest occurrence of the sequence parameter set or picture parameter set with the same value of seq\_parameter\_set\_id or pic\_parameter\_set\_id, respectively, sent in the H.264 bitstream. + +If DCI was used when a H.264 [19] logical channel was opened and H.264 sequence parameter sets need to be changed or new sets need to be added during the session, the existing H.264 logical channel shall be closed and H.245 [6] procedures for opening a new H.264 logical channel shall be started, in which sequence parameter set(s) and picture parameter set(s) shall be sent in a DCI. Each sequence parameter set of H.264 [19] shall contain the vui\_parameters syntax structure including the num\_reorder\_frames syntax element set equal to 0. + +If H.264 picture parameter sets need to be changed or new sets need to be added during a session, it may be done either by opening a new logical channel using the same procedure as described above or within the current channel, by including picture parameter set NAL units directly in the bitstream. + +**Table 1 / TS 26.111 – H.264 Capability Parameter – DecoderConfigurationInformation (DCI)** + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | DecoderConfigurationInformation | +| Parameter description | This is a nonCollapsing GenericParameter.

DecoderConfigurationInformation indicates how to configure the decoder for a particular H.264 video sequence [19]. It contains sequence parameter set NAL units, picture parameter set NAL units, or both, using the byte stream format specified in Annex B/H.264, separating NAL units with a start code. The use of a start code before the first parameter set NAL unit is optional. | +| Parameter identifier value | 43 | +| Parameter status | Optional. Shall not be present for Capability Exchange and Mode Request. May be present exactly once for Logical Channel Signalling. | +| Parameter type | OctetString | +| Supersedes | - | + +A decoder may indicate its' capability to make use of H.264 redundant slices by the following parameter. + +**Table 2 / TS 26.111 – H.264 Capability Parameter – AcceptRedundantSlices** + +| | | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | AcceptRedundantSlices | +| Parameter description |

This is a collapsing GenericParameter.

AcceptRedundantSlices indicates the capability to use H.264 redundant slices and corresponds to the MIME video/H264 parameter "redundant-pic-cap".

When False or when the parameter is not present, it indicates that the receiver makes no attempt to use redundant coded pictures to correct incorrectly decoded primary coded pictures and a sender should not send redundant slices.

When True, it indicates that the receiver is capable of decoding any such redundant slice that covers a corrupted area in a primary decoded picture (at least partly), and a sender may send redundant slices.

When using a H.264 profile (or subset of a profile as indicated by the H.264 ProfileIOP parameter defined in Table 3) and level that disallows the use of redundant slices, this parameter shall be ignored.

| +| Parameter identifier value | 44 | +| Parameter status | Optional. May be present exactly once for Capability Exchange Signalling. | +| Parameter type | Logical | +| Supersedes | - | + +NOTE: An encoder should only code redundant slices if it knows that the far-end decoder makes use of this feature. Encoders should also pay attention to potential implications on end-to-end delay. + +A decoder may indicate additional limitations that only the common subset of the algorithmic features and limitations of the Baseline level 1 are supported by the following parameter. + +**Table 3 / TS 26.111 – H.264 Capability Parameter – ProfileIOP** + +| | | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | ProfileIOP | +| Parameter description |

ProfileIOP indicates that the capability to decode H.264 streams is limited to a common subset of the algorithmic features included in the indicated profile and level.

This parameter is a Boolean array.

bit 1 (value 128) is constraint_set0_flag.

bit 2 (value 64) is constraint_set1_flag.

bit 3 (value 32) is constraint_set2_flag.

All other bits are reserved, shall be set to 0, and shall be ignored by receivers.

constraint_set0_flag, constraint_set1_flag and constraint_set2_flag are defined in [18].

As an example, a receiver indicating decoding support of the intersection of the baseline and main profile will signal value 11000000 (constraint_set0_flag = 1, constraint_set1_flag = 1, constraint_set2_flag = 0).

| +| Parameter identifier value | 46 | +| Parameter status | Optional. May be present exactly once for Capability Exchange Signalling. | +| Parameter type | BooleanArray | +| Supersedes | - | + +A terminal supporting H.264 encoding should respond to all `videoFastUpdatePicture` commands received via the H.245 control channel. If an H.264 encoder responds to `videoFastUpdatePicture`, it shall use the procedure specified in subclause 6.2.2 of H.241. + +A terminal supporting H.264 shall start decoding immediately when it receives data (even if the stream does not start with an IDR access unit) or alternatively no later than it receives the next IDR access unit or the next recovery point SEI message, whichever is earlier in decoding order. The decoding process for a stream not starting with an IDR access unit shall be the same as for a valid H.264 bitstream. However, the client shall be aware that such a stream may contain references to picture not available in the decoded picture buffer. The display behaviour of the client is out of scope of this specification. + +NOTE: Terminals may use full-frame freeze and full-frame freeze release SEI messages of H.264 to control the display process. + +### 6.6.1 MPEG-4 interface to multiplex + +As H.263 [8] encoders align picture start codes with the start of an AL-SDU, the same concept applies to MPEG-4 encoders. The following are the requirements of the MPEG-4 interface to the H.223 [1] multiplex. + +- Each 3G-324M MPEG-4 encoder shall align each `visual_object_sequence_start_code` with the start of an AL-SDU. +- Each 3G-324M MPEG-4 encoder shall align each `group_of_vop_start_code` (the beginning of a GOV field) with the start of an AL-SDU unless the GOV field immediately follows configuration information. +- Each 3G-324M MPEG-4 encoder shall align each `vop_start_code` with the start of an AL-SDU unless the `vop_start_code` immediately follows configuration information or a GOV field. + +In these requirements, GOV stands for `Group_of_VideoObjectPlane()` and Configuration information consists of Visual Object Sequence Header, Visual Object Header, and Video Object Layer Header. + +### 6.6.2 H.264 (MPEG-4 AVC) interface to multiplex + +Shall conform to the byte stream format according to H.241 chapter 7.1.5 "Transport of H.264 streams in H.324 systems" [20]. + +More strict alignment of AL-SDU and NAL units may optionally be used. To signal capability for and use of this mode, the generic parameter described in Table 3 shall be used, amending the H.264 Generic Capability in H.241 [20]. + +**Table 3 / TS 26.111 – H.264 Capability Parameter – NalAlignedMode** + +| | | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | NalAlignedMode | +| Parameter description | This is a collapsing GenericParameter.

NalAlignedMode indicates that every AL-SDU carrying H.264 shall contain an integer number of NAL units and that the start of the AL-SDU shall be aligned with the start of a NAL. Individual NAL units within the AL-SDU shall be separated by start codes as described in Annex B/H.264. The use of a start code before the first NAL in an AL-SDU is optional. | +| Parameter identifier value | 45 | +| Parameter status | Optional. May be present exactly once for Capability Exchange, Logical Channel, or Mode Request Signalling. | +| Parameter type | Logical | +| Supersedes | - | + +## 6.7 Audio channels + +AMR is the mandatory speech codec. Support for G.723.1 [7] is not mandatory, but recommended. Support for AMR-WB [18] is also recommended. + +When AMR-WB is supported, the AMR-WB speech data shall be carried in IF2 frame format as defined in Annex A of 3GPP TS 26.201 [22], and the signalling for AMR-WB shall be according to G.722.2 Annex F [21] with the following additional restrictions: + +- octetAlign shall be present +- The following parameters are not compatible with IF2 frame format, and so shall not be used: + - crc + - robustSorting + - interleaving + +When both the receiving and transmitting terminals support multiple codecs in common, the use of AMR and AMR-WB is preferred: + +- If both the receiving and transmitting terminals support AMR and other codecs (e.g. G.723.1) but not AMR-WB, then AMR shall be used. +- If both the receiving and transmitting terminals support AMR and other codecs including AMR-WB, either AMR or AMR-WB shall be used. + +Asymmetric configurations with one codec in one direction and another one in the other direction (e.g. AMR in one direction and AMR-WB in the other direction) are allowed, if supported by both terminals. + +This applies to connections without an Multipoint Control Unit (MCU). + +## 6.8 Data channels + +No differences with H.324 [10]. + +# --- 7 Terminal procedures + +See 3GPP TS 26.110 [11]. + +# --- 8 Optional enhancements + +No differences with H.324 [10]. + +# --- 9 Interoperation with other terminals + +For further study. + +# --- 10 Multipoint considerations + +For further study. + +# --- 11 Maintenance + +No differences with H.324 [10]. + +# Annex A (informative): Change History + +| History | | | | | | | | +|---------|-----------|--------|------------------|--------------|------|-----|------------------------------------------------------------------| +| TSG_# | TSG_DOC | SPEC | VERS_CURRE
NT | VERS_
NEW | CR | REV | SUBJECT | +| SP-05 | SP-99359 | 26.111 | 3.0.1 | 3.0.2 | 001 | | Changes to editorial notes. | +| SP-06 | SP-99434 | 26.111 | 3.0.2 | 3.1.0 | 002 | 2 | Specification of coding parameters for MPEG-4 video codec | +| SP-06 | SP-99514 | 26.111 | 3.0.2 | 3.1.0 | 003 | | Transmission of MPEG-4 configuration information in 3G-324M | +| SP-08 | SP-00263 | 26.111 | 3.1.0 | 3.2.0 | 004 | | Changes to editorial notes | +| SP-09 | SP-000396 | 26.111 | 3.2.0 | 3.3.0 | 006 | | MPEG-4 interface to multiplex | +| SP-10 | SP-000653 | 26.111 | 3.3.0 | 3.4.0 | 005 | 1 | MPEG4 visual simple profile @ level 0 | +| SP-11 | | | | 4.0.0 | | | Version for Release 4 | +| SP-16 | | 26.111 | 4.0.0 | 5.0.0 | | | Version for Release 5 | +| SP-20 | SP-030215 | 26.111 | 5.0.0 | 5.1.0 | 009 | 1 | Removal of Reference to TS 26.112 | +| SP-25 | SP-040659 | 26.111 | 5.1.0 | 6.0.0 | 010 | 3 | 3G-324M Improvements | +| SP-25 | SP-040648 | 26.111 | 5.1.0 | 6.0.0 | 011 | 1 | 3G-324M Improvements: Addition of optional AMR-WB support | +| SP-26 | SP-040842 | 26.111 | 6.0.0 | 6.1.0 | 012 | 1 | Addition of the missing signalling of H.264 decoder capabilities | +| SP-26 | SP-040842 | 26.111 | 6.0.0 | 6.1.0 | 013 | 1 | Reference Corrections | +| SP-36 | | 26.111 | 6.1.0 | 7.0.0 | | | Version for Release 7 | +| SP-40 | SP-080247 | 26.111 | 7.0.0 | 7.1.0 | 0015 | 1 | Use of AMR-WB in 3G-324M | +| SP-42 | | 26.111 | 7.1.0 | 8.0.0 | | | Version for Release 8 | +| SP-46 | | 26.111 | 8.0.0 | 9.0.0 | | | Version for Release 9 | +| SP-51 | | 26.111 | 9.0.0 | 10.0.0 | | | Version for Release 10 | +| SP-57 | | 26.111 | 10.0.0 | 11.0.0 | | | Version for Release 11 | +| SP-65 | | 26.111 | 11.0.0 | 12.0.0 | | | Version for Release 12 | +| SP-70 | | 26.111 | 12.0.0 | 13.0.0 | | | Version for Release 13 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | 75 | | | | | Version for Release 14 | 14.0.0 | +| 2018-06 | 80 | | | | | Version for Release 14 | 15.0.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26116/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26116/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c0fe74b83cb0f5c36bdaf5d8c8713b8313fbcee --- /dev/null +++ b/marked/Rel-18/26_series/26116/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3c1123fd1cabd2005e126e0ce4573a9d75b9f1da3d8ec720111009d4f4f18b2 +size 9291 diff --git a/marked/Rel-18/26_series/26116/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26116/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ca5e9c02e09d9737f1b0bb6fb47beff15d5cdf7 --- /dev/null +++ b/marked/Rel-18/26_series/26116/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:858afaa37aa9480035bff961e43b865a803415dd89f00bfd1b57b9d7489346d9 +size 5711 diff --git a/marked/Rel-18/26_series/26116/raw.md b/marked/Rel-18/26_series/26116/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7a65575eaf25ca67283de59ff11837462ef76f86 --- /dev/null +++ b/marked/Rel-18/26_series/26116/raw.md @@ -0,0 +1,1753 @@ + + +# 3GPP TS 26.116 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Television (TV) over 3GPP services; Video profiles (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +A GLOBAL INITIATIVE + +3GPP logo + +## --- **Keywords** + +TV over 3GPP services, Video Profiles, HDR + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| Introduction ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 Video profiles Operation Points..... | 10 | +| 4.1 Introduction ..... | 10 | +| 4.2 General requirements on video profile Operation Points ..... | 10 | +| 4.3 General Video codec requirements ..... | 11 | +| 4.4 H.264/AVC Operation Points ..... | 12 | +| 4.4.1 Common requirements and recommendations ..... | 12 | +| 4.4.1.1 General..... | 12 | +| 4.4.1.2 Random access point ..... | 12 | +| 4.4.1.2.1 Definition ..... | 12 | +| 4.4.1.2.2 Random access point period..... | 12 | +| 4.4.1.3 Sequence parameter set..... | 12 | +| 4.4.1.4 Video usability information ..... | 13 | +| 4.4.2 H.264/AVC 720p HD Operation Point ..... | 13 | +| 4.4.2.1 Introduction..... | 13 | +| 4.4.2.2 Profile and level..... | 13 | +| 4.4.2.3 Spatial resolutions..... | 13 | +| 4.4.2.4 Colour information ..... | 14 | +| 4.4.2.5 Frame rates..... | 14 | +| 4.4.2.6 Receiver compatibility..... | 14 | +| 4.4.3 H.264/AVC Full HD Operation Point..... | 14 | +| 4.4.3.1 Introduction..... | 14 | +| 4.4.3.2 Profile and level..... | 14 | +| 4.4.3.3 Spatial resolutions..... | 14 | +| 4.4.3.4 Colour information ..... | 15 | +| 4.4.3.5 Frame rates..... | 15 | +| 4.4.3.6 Receiver compatibility..... | 15 | +| 4.5 H.265/HEVC Operation Points..... | 15 | +| 4.5.1 Common requirements and recommendations ..... | 15 | +| 4.5.1.1 General..... | 15 | +| 4.5.1.2 Random access point ..... | 15 | +| 4.5.1.2.1 Definition ..... | 15 | +| 4.5.1.2.2 Random access point period..... | 15 | +| 4.5.1.3 Video parameter set ..... | 16 | +| 4.5.1.4 Sequence parameter set..... | 16 | +| 4.5.1.5 Video usability information ..... | 16 | +| 4.5.2 H.265/HEVC 720p HD Operation Point ..... | 17 | +| 4.5.2.1 Introduction..... | 17 | +| 4.5.2.2 Profile, tier and level..... | 17 | +| 4.5.2.3 Bit depth..... | 17 | +| 4.5.2.4 Spatial resolutions..... | 17 | +| 4.5.2.5 Colour information ..... | 18 | +| 4.5.2.6 Frame rates..... | 18 | +| 4.5.2.7 Receiver compatibility..... | 18 | +| 4.5.3 H.265/HEVC Full HD Operation Point..... | 18 | +| 4.5.3.1 Introduction..... | 18 | +| 4.5.3.2 Profile, tier and level..... | 18 | +| 4.5.3.3 Bit depth..... | 18 | + +| | | | +|-----------|-----------------------------------------------------------|----| +| 4.5.3.4 | Spatial resolution ..... | 18 | +| 4.5.3.5 | Colour information ..... | 19 | +| 4.5.3.6 | Frame rates..... | 19 | +| 4.5.3.7 | Receiver compatibility..... | 19 | +| 4.5.3.8 | SEI messages for HLG Signaling ..... | 19 | +| 4.5.4 | H.265/HEVC UHD Operation Point ..... | 19 | +| 4.5.4.1 | Introduction..... | 19 | +| 4.5.4.2 | Profile, tier and level..... | 19 | +| 4.5.4.3 | Bit depth..... | 20 | +| 4.5.4.4 | Spatial resolution ..... | 20 | +| 4.5.4.5 | Colour information ..... | 20 | +| 4.5.4.6 | Frame rates..... | 20 | +| 4.5.4.7 | Receiver compatibility..... | 21 | +| 4.5.4.8 | SEI messages for HLG Signaling ..... | 21 | +| 4.5.5 | H.265/HEVC Full HD HDR Operation Point ..... | 21 | +| 4.5.5.1 | Introduction..... | 21 | +| 4.5.5.2 | Profile, tier and level..... | 21 | +| 4.5.5.3 | Bit depth..... | 21 | +| 4.5.5.4 | Spatial resolution ..... | 21 | +| 4.5.5.5 | Colour information and HDR transfer characteristics ..... | 22 | +| 4.5.5.6 | Frame rates..... | 22 | +| 4.5.5.7 | SEI messages for metadata signalling ..... | 22 | +| 4.5.5.7.1 | Introduction ..... | 22 | +| 4.5.5.7.2 | Mastering display colour volume ..... | 22 | +| 4.5.5.7.3 | Content light level information ..... | 23 | +| 4.5.5.8 | Receiver compatibility..... | 23 | +| 4.5.5.9 | HD HDR Operating Modes ..... | 23 | +| 4.5.6 | H.265/HEVC UHD HDR Operation Point..... | 23 | +| 4.5.6.1 | Introduction..... | 23 | +| 4.5.6.2 | Profile, tier and level..... | 23 | +| 4.5.6.3 | Bit depth..... | 24 | +| 4.5.6.4 | Spatial resolution ..... | 24 | +| 4.5.6.5 | Colour information and HDR transfer characteristics ..... | 24 | +| 4.5.6.6 | Frame rates..... | 24 | +| 4.5.6.7 | SEI messages for metadata signalling ..... | 25 | +| 4.5.6.7.1 | Introduction ..... | 25 | +| 4.5.6.7.2 | Mastering display colour volume ..... | 25 | +| 4.5.6.7.3 | Content light level information ..... | 25 | +| 4.5.6.8 | Receiver compatibility..... | 25 | +| 4.5.6.9 | UHD HDR operating modes..... | 26 | +| 4.5.7 | H.265/HEVC Full HD HDR HLG Operation Point ..... | 26 | +| 4.5.7.1 | Introduction..... | 26 | +| 4.5.7.2 | Profile, tier and level..... | 26 | +| 4.5.7.3 | Bit depth..... | 26 | +| 4.5.7.4 | Spatial resolution ..... | 26 | +| 4.5.7.5 | Colour information and HDR transfer characteristics ..... | 27 | +| 4.5.7.6 | Frame rates..... | 27 | +| 4.5.7.7 | Receiver compatibility..... | 27 | +| 4.5.7.8 | HD HDR Operating Modes ..... | 27 | +| 4.5.8 | H.265/HEVC UHD HDR HLG Operation Point ..... | 27 | +| 4.5.8.1 | Introduction..... | 27 | +| 4.5.8.2 | Profile, tier and level..... | 28 | +| 4.5.8.3 | Bit depth..... | 28 | +| 4.5.8.4 | Spatial resolution ..... | 28 | +| 4.5.8.5 | Colour information and HDR transfer characteristics ..... | 28 | +| 4.5.8.6 | Frame rates..... | 29 | +| 4.5.8.7 | Receiver compatibility..... | 29 | +| 4.5.8.8 | UHD HDR HLG operating modes..... | 29 | +| 4.5.9 | H.265/HEVC 8K UHD Operation Point ..... | 29 | +| 4.5.9.1 | Introduction..... | 29 | +| 4.5.9.2 | Profile, tier and level..... | 29 | +| 4.5.9.3 | Bit depth..... | 30 | + +| | | | +|---------|-----------------------------------------------------------|----| +| 4.5.9.4 | Spatial resolution ..... | 30 | +| 4.5.9.5 | Colour information and HDR transfer characteristics ..... | 30 | +| 4.5.9.6 | Frame rates..... | 31 | +| 4.5.9.7 | SEI messages for metadata signalling ..... | 31 | +| 4.5.9.8 | Receiver compatibility..... | 31 | +| 5 | Mapping to 3GP-DASH delivery..... | 31 | +| 5.1 | General ..... | 31 | +| 5.1.1 | MPD and 3GP-DASH format..... | 31 | +| 5.1.2 | File Format Signalling ..... | 31 | +| 5.1.3 | Adaptation Set Constraints ..... | 33 | +| 5.2 | H.264/AVC 720p HD Operation Point ..... | 34 | +| 5.2.1 | Operation Point Identifier ..... | 34 | +| 5.2.2 | MPD Signalling ..... | 34 | +| 5.2.3 | File Format Constraints ..... | 34 | +| 5.2.4 | Adaptation Set Constraints ..... | 35 | +| 5.3 | H.264/AVC Full HD Operation Point..... | 35 | +| 5.3.1 | Operation Point Identifier ..... | 35 | +| 5.3.2 | MPD Signalling ..... | 35 | +| 5.3.3 | File Format Signalling ..... | 35 | +| 5.3.4 | Adaptation Set Constraints ..... | 35 | +| 5.4 | H.265/HEVC 720p HD Operation Point..... | 35 | +| 5.4.1 | Operation Point Identifier ..... | 35 | +| 5.4.2 | MPD Signalling ..... | 36 | +| 5.4.3 | File Format Constraints ..... | 36 | +| 5.4.4 | Adaptation Set Constraints ..... | 36 | +| 5.5 | H.265/HEVC Full HD Operation Point ..... | 36 | +| 5.5.1 | Operation Point Identifier ..... | 36 | +| 5.5.2 | MPD Signalling ..... | 36 | +| 5.5.3 | File Format Constraints ..... | 37 | +| 5.5.4 | Adaptation Set Constraints ..... | 37 | +| 5.6 | H.265/HEVC UHD Operation Point..... | 37 | +| 5.6.1 | Operation Point Identifier ..... | 37 | +| 5.6.2 | MPD Signalling ..... | 37 | +| 5.6.3 | File Format Constraints ..... | 37 | +| 5.6.4 | Adaptation Set Constraint..... | 37 | +| 5.7 | H.265/HEVC Full HD HDR Operation Point..... | 38 | +| 5.7.1 | Operation Point Identifier ..... | 38 | +| 5.7.2 | MPD Signalling ..... | 38 | +| 5.7.3 | File Format Constraints ..... | 38 | +| 5.7.4 | Adaptation Set Constraint..... | 38 | +| 5.8 | H.265/HEVC UHD HDR Operation Point ..... | 39 | +| 5.8.1 | Operation Point Identifier ..... | 39 | +| 5.8.2 | MPD Signalling ..... | 39 | +| 5.8.3 | File Format Constraints ..... | 39 | +| 5.8.4 | Adaptation Set Constraint..... | 40 | +| 5.9 | H.265/HEVC Full HD HDR HLG Operation Point..... | 41 | +| 5.9.1 | Operation Point Identifier ..... | 41 | +| 5.9.2 | MPD Signalling ..... | 41 | +| 5.9.3 | File Format Constraints ..... | 41 | +| 5.9.4 | Adaptation Set Constraint..... | 41 | +| 5.10 | H.265/HEVC UHD HDR HLG Operation Point ..... | 42 | +| 5.10.1 | Operation Point Identifier ..... | 42 | +| 5.10.2 | MPD Signalling ..... | 42 | +| 5.10.3 | File Format Constraints ..... | 42 | +| 5.10.4 | Adaptation Set Constraint..... | 42 | +| 5.11 | H.265/HEVC 8K UHD Operation Point..... | 43 | +| 5.11.1 | Operation Point Identifier ..... | 43 | +| 5.11.2 | MPD Signalling ..... | 43 | +| 5.11.3 | File Format Constraints ..... | 43 | +| 5.11.4 | Adaptation Set Constraint..... | 43 | + +**Annex A (informative): Registration Information ..... 45** +A.1 3GPP Registered URIs..... 45 +**Annex B (informative): Change history ..... 46** + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +Linear TV services can be made available on 3GPP services, e.g., based on MBMS, PSS user services and 5GMS. + +For traditional linear TV distribution, TV services accessed through Satellite, Digital Terrestrial TV (DTT), cable or IPTV obey to requirements on the video profiles to ensure a consistent quality of experience while accessing different channels within a TV bouquet. + +On-demand video services, via streaming or downloading, generally obey to the same requirements. + +The purpose of the present document is to specify TV distribution formats with detailed definitions of consistent video distribution formats (such as spatial and temporal resolutions, aspect ratios, random access points, etc.) for which operators can provide consistent quality of experience for TV services. + +The document is not restricted to operator services, but may also be referred to and used by third-party services that expect to have consistent quality of experience for TV services on 3GPP-defined radio bearers. + +# 1 Scope + +The present document specifies requirements and guidelines on video source formats (frame rate, resolution, aspect ratio, colorimetry, bit depth...) and encoding parameters (codec format, random access point period, SEI messages...) for different types of TV services, including linear TV, catch-up TV or on-demand services. A limited set of Operation Points (e.g. SDTV, HDTV, UHD, 8K UHD, ...) are defined to provide confidence to content providers/broadcasters on the quality of experience offered by 3GPP services when used for TV-like distribution. Operation Points define format and encoding restrictions but may also be viewed as compatibility points for UEs. + +In particular, the Operation Points defined in the present document may serve as the primary tested configurations for TV centric video distribution. The Operation Points are defined based on the analysis and findings in the technical report TR 26.949 [2]. + +In addition, in the context of DASH operations, not only the main distribution formats are defined, but also a subset of spatial and temporal resolutions. In order to minimize testing for seamless switching experience, suitable lower resolutions of distribution formats are defined. Furthermore, to compensate congestion situations, a minimum service quality is defined in order to provide service continuity. + +The specification is aligned with the Common Media Application Format (CMAF) as defined in ISO/IEC 23000-19 [13] to a large extent. Differences and further restrictions compared to CMAF baseline formats as well as media profiles are highlighted. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 26.949: "Video formats for 3GPP services". +- [3] Recommendation ITU-R BT.709-6 (06/2015): "Parameter values for the HDTV standards for production and international programme exchange". +- [4] Recommendation ITU-R BT.2020-2 (10/2015): "Parameter values for ultra-high definition television systems for production and international programme exchange". +- [5] Recommendation ITU-T H.264 (04/2017): "Advanced video coding for generic audiovisual services" | ISO/IEC 14496-10:2014: "Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding". +- [6] Recommendation ITU-T H.265 (11/2019): "High efficiency video coding" | ISO/IEC 23008-2:2020: "High Efficiency Coding and Media Delivery in Heterogeneous Environments – Part 2: High Efficiency Video Coding". +- [7] 3GPP TS 26.244: "Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)". +- [8] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". + +- [9] ISO/IEC 14496-15: 2019: "Information technology - Coding of audio-visual objects - Part 15: Carriage of network abstraction layer (NAL) unit structured video in ISO base media file format". +- [10] ISO/IEC 23091-2:2019, "Information technology — Coding-independent code points — Part 2: Video." +- [11] Recommendation ITU-R BT.2100-2 (07/2018): "Image parameter values for high dynamic range television for use in production and international programme exchange". +- [12] 3GPP TS 26.511: "5G Media Streaming (5GMS); Profiles, codecs and formats". +- [13] ISO/IEC 23000-19:2021: "Information technology — Multimedia application format (MPEG-A) — Part 19: Common media application format (CMAF) for segmented media". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Bitstream:** A media bitstream that conforms to a video encoding format and certain Operation Point. + +**Operation Point:** A collection of discrete combinations of different content formats including spatial and temporal resolutions, colour mapping, transfer functions, etc. and the encoding format. + +**Pillarbox:** The pillarbox effect occurs in widescreen video displays when black bars (mattes or masking) are placed on the sides of the image. It becomes necessary when film or video that was not originally designed for widescreen is shown on a widescreen display, or a narrower widescreen image is displayed within a wider aspect ratio. + +**Receiver:** A receiver that can decode and render any bitstream that is conforming to a certain Operation Point. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|----------------------------------------| +| 5GMS | 5G Media Streaming | +| AVC | Advanced Video Coding | +| CVS | Coded Video Sequence | +| DASH | Dynamic Adaptive Streaming over HTTP | +| EOTF | Electro-Optical Transfer Function | +| FFS | For Further Study | +| HD | High Definition | +| HDR | High Dynamic Range | +| HLG | Hybrid Log Gamma | +| HRD | Hypothetical Reference Decoder | +| HEVC | High Efficiency Video Coding | +| MBMS | Multicast Broadcast Multimedia Service | +| MPD | Media Presentation Description | +| OETF | Opto-Electronic Transfer Function | +| NAL | Network Abstraction Layer | +| PPS | Picture Parameter Set | +| PQ | Perceptual Quantization | +| PSS | Packet Switch Streaming | +| RAP | Random Access Point | +| SDR | Standard Dynamic Range | + +| | | +|-----|--------------------------------------| +| SEI | Supplemental Enhancement Information | +| SPS | Sequence Parameter Set | +| TV | Television | +| UHD | Ultra High Definition | +| VCL | Video Coding Layer | +| VUI | Video Usability Information | + +# 4 Video profiles Operation Points + +## 4.1 Introduction + +The video profile Operation Points defined in this clause are primarily defined in order to apply to the content format being delivered to 3GPP UE PSS/DASH, MBMS and 5GMS clients over the 3GPP system. Parameters for video encoder/decoder, content format and transport are defined. + +The following Operation Points are defined in the present document: H.264/AVC 720p HD, H.264/AVC Full HD, H.265/HEVC 720p HD, H.265/HEVC Full HD, H.265/HEVC UHD, H.265/HEVC Full HD HDR, H.265/HEVC UHD HDR, H.265/HEVC Full HD HDR HLG and H.265/HEVC UHD HDR HLG. + +Clause 4.2 specifies general requirements applicable to all Operation Points. Clause 4.3 specifies general requirements applicable to the video codecs. Then for each Operation Point, Bitstream and Receiver requirements are detailed in clause 4.4 for H.264/AVC and clause 4.5 for H.265/HEVC. + +## 4.2 General requirements on video profile Operation Points + +The following requirements apply to video profile Operation Points: + +- 16:9 picture aspect ratio shall be used. 3GPP UEs with display aspect ratio different from 16:9 and supporting the TV services over 3GPP are, by default, assumed to display the video in letter-box or pillarbox modes, depending on the screen size and orientation. +- Y'CbCr (non-constant luminance) as the Chroma Format should be used. +- 4:2:0 chroma sub-sampling shall be used. +- The following spatial resolutions should be used for: + - Operation Points (for video intended to be viewed in full-screen mode): 7680 × 4320, 5120 × 2880, 3840 × 2160, 1920 × 1080 and 1280 × 720. + - Distribution formats: 7680 × 4320, 5120 × 2880, 3840 × 2160, 3200 × 1800, 2560 × 1440, 1920 × 1080, 1600 × 900, 1280 × 720, 960 × 540, 854 × 480, 640 × 360, 426 × 240. + +NOTE 1: Distribution formats within an Operation Point do not exceed the native resolution of the Operation Point, but they may be subsampled in order to optimize distribution or adapt to the viewing conditions. + +- The following frame rates should be used depending on the Operation Point: 24; 25; 30; 50 and 60Hz. The following fractional frame rates may be used: 24/1.001, 30/1.001, 60/1.001 (Hz). Frame rates are not associated to any particular spatial resolution. +- The following colour space formats may be used depending on the Operation Point: ITU-R BT.709 [3] and ITU-R BT.2020 [4]. If no signal is provided for the colour space, BT.709 [3] should be assumed as default colour space. Receiving devices should support BT.2020 [4] signaling and provide an appropriate mapping of the signal to the supported colour space of the device. Colour spaces are not associated to any particular spatial resolution. +- The following transfer characteristics may be used depending on the Operation Point: ITU-R BT.709 [3] and ITU-R BT.2020 [4] non-constant luminance transfer characteristics or the electro-optical transfer function as defined in Recommendation ITU-R BT.2100 [11], either for the Perceptual Quantization (PQ) system, or for the Hybrid Log Gamma (HLG) system. + +NOTE 2: Although ITU-R BT.2020 is originally only recommended for 2160p/4320p resolution, this 3GPP specification recommends that BT.2020 be supported irrespective of the resolution to keep the colour space consistent across resolutions. + +- The Random Access Point period shall be less than or equal to 5 seconds, should be less than or equal to 2 seconds and may be less than or equal to 0.5 second for H.264/AVC [5] and 1 second for H.265/HEVC [6] for specific service requirements such as fast channel change or fast access to the bitstream. +- Bit depth: Either 8 or 10 bits shall be used depending on the Operation Point. + +Table 4.2-1 provides an overview of the Operation Points defined in the present document. + +**Table 4.2-1: TV over 3GPP services Video Profile Operation Points** + +| Operation Point name | Resolution format | Picture aspect ratio | Scan | Max. frame rate | Chroma format | Chroma sub-sampling | Bit depth | Colour space format | Transfer Characteristics | +|----------------------------|-------------------|----------------------|-------------|-----------------|---------------|---------------------|-----------|-------------------------|-------------------------------------------------| +| H.264/AVC 720p HD | 1280 × 720 | 16:9 | Progressive | 30 | Y'CbCr | 4:2:0 | 8 | BT.709 [3] | BT.709 [3] | +| H.265/HEVC 720p HD | 1280 × 720 | 16:9 | Progressive | 30 | Y'CbCr | 4:2:0 | 8 | BT.709 [3] | BT.709 [3] | +| H.264/AVC Full HD | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 8 | BT.709 [3] | BT.709 [3] | +| H.265/HEVC Full HD | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 8; 10 | BT.709 [3]; BT.2020 [4] | BT.709 [3]; BT.2020 [4] | +| H.265/HEVC UHD | 3840 × 2160 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 [4] | BT.2020 [4] | +| H.265/HEVC Full HD HDR | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 [4] | BT.2100 PQ [11] | +| H.265/HEVC UHD HDR | 3840 × 2160 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 [4] | BT.2100 PQ [11] | +| H.265/HEVC Full HD HDR HLG | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 [4] | BT.2100 HLG [11] | +| H.265/HEVC 8K UHD | 7680 × 4320 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 [4] | BT.2020 [4]; BT.2100 PQ; [11]; BT.2100 HLG [11] | + +Operation Points are defined including the video codec format. + +## 4.3 General Video codec requirements + +The following video codecs and associated Profiles and Levels should be used: + +- H.264/AVC Progressive High Profile Level 3.1 [5] for 720p HD services +- H.264/AVC Progressive High Profile Level 4.2 [5] for Full HD services +- H.265/HEVC Main Profile Main Tier Level 3.1 [6] for 720p HD services +- H.265/HEVC Main-10 Profile Main Tier Level 4.1 [6] for Full HD services +- H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6] for UHD services +- H.265/HEVC Main-10 Profile Main Tier Profile Level 4.1 [6] for Full HD HDR services +- H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6] for UHD HDR services + +- H.265/HEVC Main-10 Profile Main Tier Profile Level 6.1 [6] for 8K UHD services + +The Table 4.3-1 presents the mapping of the operation points with the codec type, profile and level. + +**Table 4.3-1: Video codec parameters** + +| Operation Point name | Resolution Format | Codec type, profile and level | +|----------------------------|-------------------|------------------------------------------------| +| H.264/AVC 720p HD | 1280 × 720 | AVC/H.264 Progressive High Profile Level 3.1 | +| HEVC/H.265 720p HD | 1280 × 720 | HEVC/H.265 Main Profile Main Tier Level 3.1 | +| H.264/AVC Full HD | 1920 × 1080 | AVC/H.264 Progressive High Profile Level 4.2 | +| HEVC/H.265 Full HD | 1920 × 1080 | HEVC/H.265 Main-10 Profile Main Tier Level 4.1 | +| HEVC/H.265 UHD | 3840 × 2160 | HEVC/H.265 Main-10 Profile Main Tier Level 5.1 | +| HEVC/H.265 Full HD HDR | 1920 × 1080 | HEVC/H.265 Main-10 Profile Main Tier Level 4.1 | +| HEVC/H.265 UHD HDR | 3840 × 2160 | HEVC/H.265 Main-10 Profile Main Tier Level 5.1 | +| HEVC/H.265 Full HD HDR HLG | 1920 × 1080 | HEVC/H.265 Main-10 Profile Main Tier Level 4.1 | +| HEVC/H.265 UHD HDR HLG | 3840 × 2160 | HEVC/H.265 Main-10 Profile Main Tier Level 5.1 | +| HEVC/H.265 8K UHD | 7680 × 4320 | HEVC/H.265 Main-10 Profile Main Tier Level 6.1 | + +## 4.4 H.264/AVC Operation Points + +### 4.4.1 Common requirements and recommendations + +#### 4.4.1.1 General + +The video Bitstream and Receiver shall conform to Recommendation ITU-T H.264 / ISO/IEC 14496-10 [5] with the restrictions described in this clause. H.264/AVC Bitstreams and Receivers shall support some parts of the "Video Usability Information (VUI)" syntax elements as specified in Recommendation ITU-T H.264 / ISO/IEC 14496-10 [5], annex E, which values are defined in this clause. + +#### 4.4.1.2 Random access point + +##### 4.4.1.2.1 Definition + +An H.264/AVC random access point (RAP) is defined as an access unit in an H.264/AVC Bitstream at which a Receiver can begin decoding the video successfully. This access unit shall include an AU delimiter NAL unit, only one Sequence Parameter Set (that is active) including the VUI and the Picture Parameter Set (PPS) that is required for decoding the associated picture. The access unit shall contain an IDR picture or an I picture. + +##### 4.4.1.2.2 Random access point period + +RAPs shall be present in the Bitstream at least once every 5 seconds. It is recommended that RAPs occur in the video Bitstream on average at least every 2 seconds. The time interval between successive RAPs is measured as the difference between their respective decoding time values. + +#### 4.4.1.3 Sequence parameter set + +The following restrictions apply to the active Sequence Parameter Set (SPS): + +- gaps\_in\_frame\_num\_value\_allowed\_flag value shall be set to 0. +- The Video Usability Information shall be present in the active Sequence Parameter Set. The vui\_parameter\_present\_flag shall be set to 1. +- The source video format shall be progressive. frame\_mbs\_only\_flag shall be set to 1 for every picture of the Bitstream. + +#### 4.4.1.4 Video usability information + +The aspect ratio information shall be present, i.e. + +- The `aspect_ratio_present_flag` value shall be set to 1. +- The `aspect_ratio_idc` value shall be set to 1 indicating a square pixel format. + +NOTE: CMAF [13] permits other pixel format than square pixels, but this is not the case in this specification. The colour parameter information shall be present, i.e. + +- `video_signal_type_present_flag` value and `colour_description_present_flag` value shall be set to 1. +- The values of `colour_primaries`, `transfer_characteristics` and `matrix_coefficients` are defined in clause 4.4.2.4 for H.264/AVC 720p HD and in clause 4.4.3.4 for H.264/AVC Full HD Operation Points. + +The timing information may be present. + +- If the timing information is present, i.e. the value of `timing_info_present_flag` is set to 1, then the values of `num_units_in_tick` and `time_scale` shall be set according to the frame rates allowed in clause 4.4.2.5 for H.264/AVC 720p HD and in clause 4.4.3.5 for H.264/AVC Full HD Operation Points. The timing information present in the video Bitstream should be consistent with the timing information signalled at the system level. + +NOTE: In 3GPP PSS and MBMS User services, the Receiver observes the timing at the system level, and ignores the timing information in the video Bitstream. + +- The frame rate shall not change between two RAPs. `fixed_frame_rate_flag` value shall be set to 1. + +There are no requirements on output timing conformance for H.264/AVC decoding (Annex C of [5]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +### 4.4.2 H.264/AVC 720p HD Operation Point + +#### 4.4.2.1 Introduction + +The following restrictions apply for the **H.264/AVC 720p HD** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.264/AVC Operation Points in clause 4.4.1 shall apply. + +NOTE: This format is within the capabilities of H.264/AVC video codecs of 3GPP video services up to Release 13. + +#### 4.4.2.2 Profile and level + +A Bitstream conforming to the H.264/AVC 720p HD Operation Point shall comply with the following restrictions: + +- The `profile_idc` shall be set to 100 indicating the High profile. +- The `constrain_set0_flag`, `constrain_set1_flag`, `constrain_set2_flag` and `constrain_set3_flag` shall all be set to 0. +- The value of `level_idc` shall not be greater than 31 (corresponding to the level 3.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.4.2.3 Spatial resolutions + +The spatial resolution of the distribution format shall be one of the following: + +- $1280 \times 720$ , +- $960 \times 540$ , + +- 854 × 480, +- 640 × 360, +- 426 × 240. + +#### 4.4.2.4 Colour information + +A Bitstream conforming to the H.264/AVC 720p HD Operation Point shall use Recommendation ITU-R BT.709 [3] colorimetry. + +The `colour_primaries` value, the `transfer_characteristics` value and the `matrix_coefficients` value in the Video Usability Information shall all be set to 1. + +A Receiver conforming to the H.264/AVC 720p HD Operation Point shall be capable of decoding Bitstreams that use Recommendation ITU-R BT.709 [3] colorimetry. + +#### 4.4.2.5 Frame rates + +A Bitstream conforming to the H.264/AVC 720p HD Operation Point shall have one of the following frame rates: 24; 25; 30; 24/1.001; 30/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `time_scale` and `num_units_in_tick`. + +#### 4.4.2.6 Receiver compatibility + +Receivers conforming to the **H.264/AVC 720p** Operation Point shall support decoding and displaying **H.264/AVC 720p HD** Bitstreams. + +Receivers conforming to the **H.264/AVC 720p** Operation Point are only required to support Bitstreams with the maximum VCL Bit Rate constrained to be 14 Mbps with `cpbBrVclFactor` and `cpbBrNalFactor` being fixed to be 1000 and 1200, respectively. + +### 4.4.3 H.264/AVC Full HD Operation Point + +#### 4.4.3.1 Introduction + +The following restrictions apply for the **H.264/AVC Full HD** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.264/AVC Operation Points in clause 4.4.1 shall apply. + +#### 4.4.3.2 Profile and level + +A Bitstream conforming to the H.264/AVC Full HD Operation Point shall comply with the following restrictions: + +- The `profile_idc` shall be set to 100 indicating the High profile. +- The `constrain_set0_flag`, `constrain_set1_flag`, `constrain_set2_flag` and `constrain_set3_flag` shall all be set to 0. +- The value of `level_idc` shall not be greater than 42 (corresponding to the level 4.2) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.4.3.3 Spatial resolutions + +The spatial resolution of the distribution format shall be one of the following: + +- 1920 x 1080, +- 1600 × 900, +- 1280 × 720, +- 960 × 540, + +- 854 × 480, +- 640 × 360, +- 426 × 240. + +#### 4.4.3.4 Colour information + +A Bitstream conforming to the H.264/AVC Full HD Operation Point shall use Recommendation ITU-R BT.709 [3] colorimetry. + +The `colour_primaries` value, the `transfer_characteristics` value and the `matrix_coefficients` value in the Video Usability Information shall all be set to 1. + +A Receiver conforming to the H.264/AVC Full HD Operation Point shall be capable of decoding Bitstreams that use Recommendation ITU-R BT.709 [3] colorimetry. + +#### 4.4.3.5 Frame rates + +A Bitstream conforming to the H.264/AVC Full HD Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `time_scale` and `num_units_in_tick`. + +#### 4.4.3.6 Receiver compatibility + +Receivers conforming to the **H.264/AVC Full HD** Operation Point shall support decoding and displaying **H.264/AVC 720p HD** and **H.264/AVC Full HD** Bitstreams. + +## 4.5 H.265/HEVC Operation Points + +### 4.5.1 Common requirements and recommendations + +#### 4.5.1.1 General + +The video Bitstream and Receiver shall conform to Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] with the restrictions described in this clause. H.265/HEVC Bitstreams and Receivers shall support some parts of the "Video usability information (VUI)" syntax elements as specified in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6], annex E. which values are defined in this clause. + +#### 4.5.1.2 Random access point + +##### 4.5.1.2.1 Definition + +An H.265/HEVC random access point (RAP) is defined as an access unit in an H.265/HEVC Bitstream at which a Receiver can begin decoding the video bitstream successfully. This access unit shall include an AU delimiter NAL unit, only one Video Parameter Set (that is active), only one Sequence Parameter Set (that is active) including the VUI and the Picture Parameter Set that is required for decoding the associated picture. The access unit shall contain an IRAP picture or an I picture, as defined in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6]. + +##### 4.5.1.2.2 Random access point period + +RAPs shall be present in the Bitstream at least once every 5 seconds. It is recommended that RAPs occur in the video Bitstream on average at least every 2 seconds. The time interval between successive RAPs is measured as the difference between their respective decoding time values. + +#### 4.5.1.3 Video parameter set + +H.265/HEVC Receivers should ignore the content of all Video Parameter Sets (VPS) NAL units as defined in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6]. + +**NOTE 1: The content of VPS may be used in future Operation Points.** + +NOTE 2: CMAF requires that each HEVC video media sample in the CMAF track references the VPS in the CMAF header sample entry and that a VPS does not change within CMAF tracks or between CMAF tracks in a CMAF switching set. + +#### 4.5.1.4 Sequence parameter set + +The following restrictions apply to the active Sequence Parameter Set (SPS): + +- The Video Usability Information (VUI) shall be present in the active Sequence Parameter Set. The `vui_parameters_present_flag` shall be set to 1 and the constraints defined in clause 4.5.1.5 for the VUI shall apply. +- The chroma sub-sampling shall be 4:2:0, `chroma_format_idc` value shall be set to 1. + +NOTE: CMAF implicitly requires this as a requirement from its HEVC media profiles. + +- The source video format shall be progressive, i.e. + - The `general_progressive_source_flag` shall be set to 1, + - The `general_interlaced_source_flag` shall be set to 0, + - The `general_frame_only_constraint_flag` shall be set to 1. +- Only 2D contents are required to be supported, i.e. + - The `general_non_packed_constraint_flag` shall be set to 1. + +Receivers conforming to any of the H.265/HEVC Operation Points shall only support Bitstreams with the restrictions on the SPS defined above. + +#### 4.5.1.5 Video usability information + +The aspect ratio information shall be present, i.e. + +- The `aspect_ratio_info_present_flag` value shall be set to 1. +- The `aspect_ratio_idc` value shall be set to 1 indicating a square pixel format. + +The colour parameter information shall be present, i.e. + +- `video_signal_type_present_flag` value and `colour_description_present_flag` value shall be set to 1. + +NOTE: CMAF does not require setting the above flags.- The values of `colour_primaries`, `transfer_characteristics` and `matrix_coeffs` are defined individually for each operation point. + +Only video range signals shall be used, i.e. + +- The `video_full_range_flag` shall be set to 0. + +No overscan signalling shall be present, i.e. + +- the `overscan_info_present_flag` shall be set to 0 + +The timing information may be present. + +- If the timing information is present, i.e. the value of `vui_timing_info_present_flag` is set to 1, then the values of `vui_num_units_in_tick` and `vui_time_scale` shall be set according to the frame rates allowed for each operation point. The timing information present in the video Bitstream should be consistent with the timing information signalled at the system level. +- The frame rate shall not change between two RAPs. `fixed_frame_rate_flag` value, if present, shall be set to 1. + +NOTE 1: In 3GPP PSS and MBMS User services, the Receiver observes the timing at the system level, and ignores the timing information in the video Bitstream. + +NOTE 2: CMAF does recommend to not change the frame rate within an entire CMAF track. + +There are no requirements on output timing conformance for H.265/HEVC decoding (Annex C of [6]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +### 4.5.2 H.265/HEVC 720p HD Operation Point + +#### 4.5.2.1 Introduction + +The following restrictions apply for the **H.265/HEVC 720p HD** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +NOTE: This format is within the capabilities of H.265/HEVC video codecs as defined in 3GPP video services up to Release 13. + +#### 4.5.2.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC 720p HD Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 1 indicating the Main profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 93 (corresponding to the Level 3.1) and should indicate the lowest level to which the Bitstream conforms. + +NOTE: CMAF explicitly requires that the above parameters do not change throughout an HEVC elementary stream. The above statement includes this requirement implicitly. + +#### 4.5.2.3 Bit depth + +Bitstreams conforming to the H.265/HEVC 720p HD Operation Point shall be encoded with 8 bit precision. + +- `bit_depth_luma_minus8 = 0` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC 720p HD Operation Point shall support 8 bit precision. + +#### 4.5.2.4 Spatial resolutions + +The spatial resolution of the distribution format shall be one of the following: + +- 1280 × 720, +- 960 × 540, +- 854 × 480, +- 640 × 360, +- 426 × 240. + +#### 4.5.2.5 Colour information + +A Bitstream conforming to the H.265/HEVC 720p HD Operation Point shall use Recommendation ITU-R BT.709 [3] colorimetry. + +The `colour_primaries` value, the `transfer_characteristics` value and the `matrix_coeffs` value in the Video Usability Information shall all be set to 1. + +A Receiver conforming to the H.265/HEVC 720p HD Operation Point shall be capable of decoding Bitstreams that use Recommendation ITU-R BT.709 [3] colorimetry. + +#### 4.5.2.6 Frame rates + +A Bitstream conforming to the H.265/HEVC 720p HD Operation Point shall have one of the following frame rates: 24; 25; 30; 24/1.001; 30/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.2.7 Receiver compatibility + +Receivers conforming to the **H.265/HEVC 720p** Operation Point shall support decoding and displaying **H.265/HEVC 720p HD** Bitstreams. + +### 4.5.3 H.265/HEVC Full HD Operation Point + +#### 4.5.3.1 Introduction + +The following restrictions apply for the **H.265/HEVC Full HD** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +#### 4.5.3.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC Full HD Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 123 (corresponding to the Level 4.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.3.3 Bit depth + +Bitstreams conforming to the H.265/HEVC Full HD Operation Point shall be encoded with either 8 or 10 bit precision. + +- `bit_depth_luma_minus8 = 0` or `2` (8 or 10 bits respectively) +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC Full HD Operation Point shall support 8 bit and 10 bit precision. + +#### 4.5.3.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- $1920 \times 1080$ , +- $1600 \times 900$ , +- $1280 \times 720$ , +- $960 \times 540$ , + +- $854 \times 480$ , +- $640 \times 360$ , +- $426 \times 240$ . + +#### 4.5.3.5 Colour information + +A Bitstream conforming to the H.265/HEVC Full HD Operation Point shall use either Recommendation ITU-R BT.709 [3] colorimetry or Recommendation ITU-R BT.2020 [4] colorimetry in non-constant luminance. + +- BT.709 [3] shall be signalled by setting `colour_primaries` to the value 1, `transfer_characteristics` to the value 1 and `matrix_coeffs` to the value 1. +- If BT.2020 [4] is used, + - it shall be signalled by setting `colour_primaries` to the value 9, `transfer_characteristics` to the value 14 and `matrix_coeffs` to the value 9, + - the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +A Receiver conforming to the H.265/HEVC Full HD Operation Point shall be capable of decoding Bitstreams that use Recommendation ITU-R BT.709 [3] and ITU-R BT.2020 [4] colorimetry. Such a Receiver should support ITU-R BT.2020 [4] signalling and provide an appropriate mapping of the signal to the supported colour space of the device. + +NOTE: Colour spaces are not associated to any particular spatial resolution. + +#### 4.5.3.6 Frame rates + +A Bitstream conforming to the H.265/HEVC Full HD Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.3.7 Receiver compatibility + +Receivers conforming to the **H.265/HEVC Full HD** Operation Point shall support decoding and displaying **H.265/HEVC 720p HD** and **H.265/HEVC Full HD** Bitstreams. + +NOTE: The requirement infers that the Receivers conforming to the **H.265/HEVC Full HD** support Main and Main10 Profile. + +#### 4.5.3.8 SEI messages for HLG Signaling + +If ITU-R BT.2020 is used and signalled as defined in clause 4.5.3.5, then the Bitstream may contain the `alternative_transfer_characteristics` SEI message to signal the use of HLG transfer characteristic. If present, the `alternative_transfer_characteristics` SEI message shall be inserted at each RAP, and its parameter `preferred_transfer_characteristics` shall be set to the value 18. + +### 4.5.4 H.265/HEVC UHD Operation Point + +#### 4.5.4.1 Introduction + +The following restrictions apply for the **H.265/HEVC UHD** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +#### 4.5.4.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC UHD Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main-10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 153 (corresponding to the Level 5.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.4.3 Bit depth + +A Bitstream conforming to the H.265/HEVC UHD Operation Point shall be encoded with 10 bits precision. + +- `bit_depth_luma_minus8 = 2` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC UHD Operation Point shall support 10 bits precision. + +#### 4.5.4.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- $3840 \times 2160$ , +- $3200 \times 1800$ , +- $2560 \times 1440$ , +- $1920 \times 1080$ , +- $1600 \times 900$ , +- $1280 \times 720$ , +- $960 \times 540$ , +- $854 \times 480$ , +- $640 \times 360$ , +- $426 \times 240$ . + +#### 4.5.4.5 Colour information + +A Bitstream conforming to the H.265/HEVC UHD Operation Point shall use Recommendation ITU-R BT.2020 [4] colorimetry in non-constant luminance. + +- if BT.2020 [4] is used, + - it shall be signalled by setting `colour_primaries` to the value 9, `transfer_characteristics` to the value 14 and `matrix_coeffs` to the value 9, + - the `chroma_loc_info_present_flag` should be equal to 1, and if set, the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +A Receiver conforming to the H.265/HEVC UHD Operation Point shall be capable of decoding Bitstreams that use ITU-R BT.2020 [4] colorimetry. Such a Receiver should support ITU-R BT.2020 [4] signalling and provide an appropriate mapping of the signal to the supported colour space of the device. + +#### 4.5.4.6 Frame rates + +A Bitstream conforming to the H.265/HEVC UHD Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.4.7 Receiver compatibility + +Receivers conforming to the **H.265/HEVC UHD** Operation Point shall support decoding and displaying **H.265/HEVC 720p HD**, **H.265/HEVC Full HD** and **H.265/HEVC UHD** Bitstreams. + +NOTE: The requirement infers that the Receivers conforming to the **H.265/HEVC UHD** support Main and Main-10 Profile. + +#### 4.5.4.8 SEI messages for HLG Signaling + +If ITU-R BT.2020 is used and signalled as defined in clause 4.5.4.5, then the Bitstream may contain the `alternative_transfer_characteristics` SEI message to signal the use of HLG transfer characteristic. If present, the `alternative_transfer_characteristics` SEI message shall be inserted at each RAP, and its parameter `preferred_transfer_characteristics` shall be set to the value 18. + +### 4.5.5 H.265/HEVC Full HD HDR Operation Point + +#### 4.5.5.1 Introduction + +The following restrictions apply for the **H.265/HEVC Full HD HDR** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +#### 4.5.5.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC Full HD HDR Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main-10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 123 (corresponding to the Level 4.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.5.3 Bit depth + +A Bitstream conforming to the H.265/HEVC Full HD HDR Operation Point shall be encoded with 10 bits precision. + +- `bit_depth_luma_minus8 = 2` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC Full HD HDR Operation Point shall support 10 bits precision. + +#### 4.5.5.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- 1920 × 1080, +- 1600 × 900, +- 1280 × 720, +- 960 × 540, +- 854 × 480, +- 640 × 360, + +- 426 × 240. + +#### 4.5.5.5 Colour information and HDR transfer characteristics + +A Bitstream conforming to the H.265/HEVC Full HD HDR Operation Point that uses PQ HDR shall comply with the following restrictions in the VUI: + +- `colour_primaries` shall be set to the value 9, +- `transfer_characteristics` shall be set to the value 16, +- `matrix_coeffs` shall be set to the value 9, +- the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +This signalling implies that BT.2020 [4] colorimetry in non-constant luminance and Perceptual Quantization (PQ) electro-optical transfer function (EOTF) as defined in Recommendation ITU-R BT.2100 [11] are in use. + +#### 4.5.5.6 Frame rates + +A Bitstream conforming to the H.265/HEVC Full HD HDR Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.5.7 SEI messages for metadata signalling + +##### 4.5.5.7.1 Introduction + +In order to help the display device to adapt the rendering of PQ HDR content, the Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] defines SEI messages for this purpose. These PQ HDR SEI messages provide indication on the mastering environment and the brightness limitation characteristics of PQ HDR content. + +NOTE: As per the Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6], SEI messages are optional and may be ignored by the decoder. + +The following clauses describe the restrictions on Mastering display colour volume and Content light level SEI messages, if present in a bitstream conforming to H.265/HEVC Full HD HDR Operation point when PQ HDR is used. + +##### 4.5.5.7.2 Mastering display colour volume + +A Bitstream conforming to the H.265/HEVC Full HD HDR Operation point may indicate the colour volume of the display used when mastering the video content. This mastering display colour volume is described by its colour primaries, white point and luminance range and is signalled in a Mastering display colour volume SEI message as specified in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] clause D.3.28. + +If the Mastering display colour volume SEI message is present, `display_primaries_x[c]`, `display_primaries_y[c]`, `white_point_x`, `white_point_y`, `max_display_mastering_luminance`, and `min_display_mastering_luminance` should be set to a value that is not 0. If a value is set to 0, it means that the value of this field is unknown. + +NOTE 1: The lowest value for a known `min_display_mastering_luminance` that can be signalled is 1 (which is equivalent to 0.0001 candelas per square metre). + +NOTE 2: In accordance to the HEVC specification, if `max_display_mastering_luminance` is set to 0, then `min_display_mastering_luminance` is set to 0 as well. + +According to ITU-T H.265 / ISO/IEC 23008-2 [6] clause D.3.28, when a Mastering display colour volume SEI message is present for any picture of a coded video sequence (CVS), a Mastering display colour volume SEI message is present for the first picture of the CVS. The Mastering display colour volume SEI message persists from the current picture + +until the end of the CVS. All Mastering display colour volume SEI messages that apply to the same CVS have the same content. + +##### 4.5.5.7.3 Content light level information + +A Bitstream conforming to the H.265/HEVC Full HD HDR Operation point may indicate the upper bound on the maximum light level among all individual pictures and the upper bound on the maximum average light level for any individual picture of a video content that are signalled in a Content light level SEI message as specified in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] clause D.3.35. + +If the Content light level SEI message is present, `max_content_light_level` and `max_pic_average_light_level` should be set to values that are not 0. If a value is set to 0 it means that the value of this field is unknown. + +When a Content light level information SEI message is present for any picture of a CVS, a content light level information SEI message shall be present for the first picture of the CVS. The content light level information SEI message message persists from the current picture until the end of the CVS. All content light level information SEI messages that apply to the same CVS shall have the same content. + +#### 4.5.5.8 Receiver compatibility + +Receivers conforming to the **H.265/HEVC Full HD HDR** Operation Point shall support decoding and processing **H.265/HEVC 720p HD**, **H.265/HEVC Full HD** and **H.265/HEVC Full HD HDR** Bitstreams. + +Receivers conforming to the **H.265/HEVC Full HD HDR** Operation Point should support processing the SEI messages defined in clause 4.5.5.7. + +#### 4.5.5.9 HD HDR Operating Modes + +HD HDR services may be defined with lower spatial and temporal resolutions than full HD at 60fps. The following operating modes are defined accordingly: + +- **HEVC/H.265 HDR 720p HD30** mode: Spatial resolutions do not exceed (1280x720) and frame rate does not exceed 30fps. +- **HEVC/H.265 HDR 720p HD60** mode: Spatial resolutions do not exceed (1280x720), frame rate exceeds 30fps. +- **HEVC/H.265 HDR Full HD30** mode: Spatial resolutions exceed the HEVC/H.265 HDR 720p HD mode, but do not exceed (1920x1080). Frame rate does not exceed 30fps. +- **HEVC/H.265 HDR Full HD60** mode: Spatial resolutions exceed the HEVC/H.265 HDR 720p HD mode, but do not exceed (1920x1080). Frame rate exceeds 30fps. + +### 4.5.6 H.265/HEVC UHD HDR Operation Point + +#### 4.5.6.1 Introduction + +The following restrictions apply for the **H.265/HEVC UHD HDR** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +#### 4.5.6.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC UHD HDR Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main-10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. + +- The value of `level_idc` shall not be greater than 153 (corresponding to the Level 5.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.6.3 Bit depth + +A Bitstream conforming to the H.265/HEVC UHD HDR Operation Point shall be encoded with 10 bits precision. + +- `bit_depth_luma_minus8 = 2` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC UHD HDR Operation Point shall support 10 bits precision. + +#### 4.5.6.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- $3840 \times 2160$ , +- $3200 \times 1800$ , +- $2560 \times 1440$ , +- $1920 \times 1080$ , +- $1600 \times 900$ , +- $1280 \times 720$ , +- $960 \times 540$ , +- $854 \times 480$ , +- $640 \times 360$ , +- $426 \times 240$ . + +#### 4.5.6.5 Colour information and HDR transfer characteristics + +A Bitstream conforming to the H.265/HEVC UHD HDR Operation Point that uses PQ HDR shall comply with the following restrictions in the VUI: + +- `colour_primaries` shall be set to the value 9, +- `transfer_characteristics` shall be set to the value 16, +- `matrix_coeffs` shall be set to the value 9, +- the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +This signalling implies that Recommendation BT.2020 [4] colorimetry in non-constant luminance and Perceptual Quantization (PQ) electro-optical transfer function (EOTF) as defined in Recommendation ITU-R BT.2100 [11] are in use. + +#### 4.5.6.6 Frame rates + +A Bitstream conforming to the H.265/HEVC UHD HDR Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.6.7 SEI messages for metadata signalling + +##### 4.5.6.7.1 Introduction + +In order to help the display device to adapt the rendering of PQ HDR content, the Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] defines SEI messages for this purpose. These PQ HDR SEI messages provide indication on the mastering environment and the brightness limitation characteristics of PQ HDR content. + +NOTE: As per the Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6], SEI messages are optional and may be ignored by the decoder. + +The following clauses describe the restrictions on Mastering display colour volume and Content light level SEI messages, if present in a bitstream conforming to H.265/HEVC Full HD HDR Operation point. + +##### 4.5.6.7.2 Mastering display colour volume + +A Bitstream conforming to the H.265/HEVC UHD HDR Operation point may indicate the colour volume of the display used when mastering the video content. This mastering display colour volume is described by its colour primaries, white point and luminance range and is signalled in a Mastering display colour volume SEI message as specified in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] clause D.3.28. + +If the Mastering display colour volume SEI message is present, `display_primaries_x[c]`, `display_primaries_y[c]`, `white_point_x`, `white_point_y`, `max_display_mastering_luminance`, and `min_display_mastering_luminance` should be set to a value that is not 0. If a value is set to 0, it means that the value of this field is unknown. + +NOTE 1: The lowest value for a known `min_display_mastering_luminance` that can be signalled is 1 (which is equivalent to 0.0001 candelas per square metre). + +NOTE 2: In accordance to the HEVC specification, if `max_display_mastering_luminance` is set to 0, then `min_display_mastering_luminance` is set to 0 as well. + +According to ITU-T H.265 / ISO/IEC 23008-2 [6] clause D.3.28, when a Mastering display colour volume SEI message is present for any picture of a coded video sequence (CVS), a Mastering display colour volume SEI message is present for the first picture of the CVS. The Mastering display colour volume SEI message persists from the current picture until the end of the CVS. All Mastering display colour volume SEI messages that apply to the same CVS have the same content. + +##### 4.5.6.7.3 Content light level information + +A Bitstream conforming to the H.265/HEVC UHD HDR Operation point may indicate the upper bound on the maximum light level among all individual pictures and the upper bound on the maximum average light level for any individual picture of a video content that are signalled in a Content light level SEI message as specified in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6] clause D.3.35. + +If the Content light level SEI message is present, `max_content_light_level` and `max_pic_average_light_level` should be set to values that are not 0. + +If a value is set to 0 it means that the value of this field is unknown. + +When a content light level information SEI message is present for any picture of a CVS, a content light level information SEI message shall be present for the first picture of the CVS. The content light level information SEI message message persists from the current picture until the end of the CVS. All content light level information SEI messages that apply to the same CVS shall have the same content. + +#### 4.5.6.8 Receiver compatibility + +Receivers conforming to the **H.265/HEVC UHD HDR** Operation Point shall support decoding and processing **H.265/HEVC 720p HD**, **H.265/HEVC Full HD**, **H.265/HEVC UHD**, **H.265/HEVC Full HD HDR** and **H.265/HEVC UHD HDR** Bitstreams. + +Receivers conforming to the **H.265/HEVC UHD HDR** Operation Point should support processing the optional SEI messages defined in clause 4.5.6.7. + +#### 4.5.6.9 UHD HDR operating modes + +UHD HDR services may be defined with a lower temporal resolution than 60fps. The following additional operating modes beyond those defined for HEVC Full HD HDR Operation point in clause 4.5.5.9 are defined accordingly: + +- **HEVC/H.265 HDR UHD30** mode: Spatial resolutions exceed the HEVC/H.265 HDR Full HD mode, but do not exceed (3840x2160). Frame rate does not exceed 30fps. +- **HEVC/H.265 HDR UHD60** mode: Spatial resolutions exceed the HEVC/H.265 HDR Full HD mode, but do not exceed (3840x2160). Frame rate exceeds 30fps. + +### 4.5.7 H.265/HEVC Full HD HDR HLG Operation Point + +#### 4.5.7.1 Introduction + +The following restrictions apply for the **H.265/HEVC Full HD HDR HLG** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +#### 4.5.7.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC Full HD HDR HLG Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main-10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 123 (corresponding to the Level 4.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.7.3 Bit depth + +A Bitstream conforming to the H.265/HEVC Full HD HDR HLG Operation Point shall be encoded with 10 bits precision. + +- `bit_depth_luma_minus8 = 2` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC Full HD HDR HLG Operation Point shall support 10 bits precision. + +#### 4.5.7.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- 1920 × 1080, +- 1600 × 900, +- 1280 × 720, +- 960 × 540, +- 854 × 480, +- 640 × 360, +- 426 × 240. + +#### 4.5.7.5 Colour information and HDR transfer characteristics + +A Bitstream conforming to the H.265/HEVC Full HD HDR HLG Operation Point shall comply with the following restrictions in the VUI: + +- `colour_primaries` shall be set to the value 9, +- `transfer_characteristics` shall be set to either the value 18, or to the value 14. In the latter case, the Bitstream shall also contain the `alternative_transfer_characteristics` SEI message. The `alternative_transfer_characteristics` SEI message shall be inserted at each RAP, and its parameter `preferred_transfer_characteristics` shall be set to the value 18. +- `matrix_coeffs` shall be set to the value 9, +- the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +This signalling implies that BT.2020 [4] colorimetry in non-constant luminance and Hybrid Log Gamma (HLG) opto-electronic transfer function (OETF) as defined in Recommendation ITU-R BT.2100 [11] are in use. + +#### 4.5.7.6 Frame rates + +A Bitstream conforming to the H.265/HEVC Full HD HDR HLG Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.7.7 Receiver compatibility + +Receivers conforming to the **H.265/HEVC Full HD HDR HLG** Operation Point shall support decoding and processing **H.265/HEVC 720p HD**, **H.265/HEVC Full HD** and **H.265/HEVC Full HD HDR HLG** Bitstreams. + +#### 4.5.7.8 HD HDR Operating Modes + +HD HDR HLG services may be defined with lower spatial and temporal resolutions than full HD at 60fps. The following operating modes are defined accordingly: + +- **HEVC/H.265 HDR HLG 720p HD30** mode: Spatial resolutions do not exceed (1280x720) and frame rate does not exceed 30fps. +- **HEVC/H.265 HDR HLG 720p HD60** mode: Spatial resolutions do not exceed (1280x720), frame rate exceeds 30fps. +- **HEVC/H.265 HDR HLG Full HD30** mode: Spatial resolutions exceed the HEVC/H.265 HDR HLG 720p HD mode, but do not exceed (1920x1080). Frame rate does not exceed 30fps. +- **HEVC/H.265 HDR HLG Full HD60** mode: Spatial resolutions exceed the HEVC/H.265 HDR HLG 720p HD mode, but do not exceed (1920x1080). Frame rate exceeds 30fps. + +### 4.5.8 H.265/HEVC UHD HDR HLG Operation Point + +#### 4.5.8.1 Introduction + +The following restrictions apply for the **H.265/HEVC UHD HDR HLG** Operation Point. The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 shall apply. + +#### 4.5.8.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC UHD HDR HLG Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main-10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 153 (corresponding to the Level 5.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.8.3 Bit depth + +A Bitstream conforming to the H.265/HEVC UHD HDR HLG Operation Point shall be encoded with 10 bits precision. + +- `bit_depth_luma_minus8 = 2` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC UHD HDR HLG Operation Point shall support 10 bits precision. + +#### 4.5.8.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- $3840 \times 2160$ , +- $3200 \times 1800$ , +- $2560 \times 1440$ , +- $1920 \times 1080$ , +- $1600 \times 900$ , +- $1280 \times 720$ , +- $960 \times 540$ , +- $854 \times 480$ , +- $640 \times 360$ , +- $426 \times 240$ . + +#### 4.5.8.5 Colour information and HDR transfer characteristics + +A Bitstream conforming to the H.265/HEVC UHD HDR HLG Operation Point shall comply with the following restrictions in the VUI: + +- `colour_primaries` shall be set to the value 9, +- `transfer_characteristics` shall be set to either the value 18, or to the value 14. In the latter case, the Bitstream shall also contain the `alternative_transfer_characteristics` SEI message. The `alternative_transfer_characteristics` SEI message shall be inserted at each RAP, and its parameter `preferred_transfer_characteristics` shall be set to the value 18. +- `matrix_coeffs` shall be set to the value 9, +- the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +This signalling implies that Recommendation BT.2020 [4] colorimetry in non-constant luminance and Hybrid Log Gamma (HLG) opto-electronic transfer function (OETF) as defined in Recommendation ITU-R BT.2100 [11] are in use. + +#### 4.5.8.6 Frame rates + +A Bitstream conforming to the H.265/HEVC UHD HDR HLG Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.8.7 Receiver compatibility + +Receivers conforming to the **H.265/HEVC UHD HDR HLG** Operation Point shall support decoding and processing **H.265/HEVC 720p HD, H.265/HEVC Full HD, H.265/HEVC UHD, H.265/HEVC Full HD HDR HLG** and **H.265/HEVC UHD HDR HLG** Bitstreams. + +#### 4.5.8.8 UHD HDR HLG operating modes + +UHD HDR HLG services may be defined with a lower temporal resolution than 60fps. The following additional operating modes beyond those defined for HEVC Full HD HDR HLG Operation point in clause 4.5.7.9 are defined accordingly: + +- **HEVC/H.265 HDR HLG UHD30** mode: Spatial resolutions exceed the HEVC/H.265 HDR HLG Full HD mode, but do not exceed (3840x2160). Frame rate does not exceed 30fps. +- **HEVC/H.265 HDR HLG UHD60** mode: Spatial resolutions exceed the HEVC/H.265 HDR HLG Full HD mode, but do not exceed (3840x2160). Frame rate exceeds 30fps. + +### 4.5.9 H.265/HEVC 8K UHD Operation Point + +#### 4.5.9.1 Introduction + +An 8K UHD H.265/HEVC Operation Point is introduced that includes three options for the transfer characteristics: SDR, HDR PQ and HDR HLG. It is considered that receivers that support 10-bit decoding are all capable of handling any of the three transfer characteristics. + +The general requirements and recommendations for Bitstreams and Receivers for H.265/HEVC Operation Points in clause 4.5.1 as well as the additional restrictions documented in this clause 4.5.9 shall apply for the **H.265/HEVC 8K UHD** Operation Point. + +#### 4.5.9.2 Profile, tier and level + +A Bitstream conforming to the H.265/HEVC 8K UHD Operation Point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main-10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 183 (corresponding to the Level 6.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 4.5.9.3 Bit depth + +A Bitstream conforming to the H.265/HEVC 8K UHD Operation Point shall be encoded with 10 bits precision, i.e. the fields shall be set as follows + +- `bit_depth_luma_minus8 = 2` +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the H.265/HEVC 8K UHD Operation Point shall support 10 bit precision. + +#### 4.5.9.4 Spatial resolution + +The spatial resolution of the distribution format shall be one of the following: + +- $7680 \times 4320$ , +- $5120 \times 2880$ , +- $3840 \times 2160$ , +- $3200 \times 1800$ , +- $2560 \times 1440$ , +- $1920 \times 1080$ , +- $1600 \times 900$ , +- $1280 \times 720$ , +- $960 \times 540$ , +- $854 \times 480$ . + +#### 4.5.9.5 Colour information and HDR transfer characteristics + +A Bitstream conforming to the H.265/HEVC 8K UHD Operation Point shall comply with the following restrictions in the VUI: + +- `colour_primaries` shall be set to the value 9, +- `transfer_characteristics` shall be set to one of the following values + - 14 for SDR, + - 16 for HDR PQ, + - 18 for HDR HLG, +- `matrix_coeffs` shall be set to the value 9, +- the `chroma_loc_info_present_flag` shall be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +For `transfer_characteristics` set to 16, it implies that Recommendation BT.2020 [4] colorimetry in non-constant luminance and Perceptual Quantization (PQ) electro-optical transfer function (EOTF) as defined in Recommendation ITU-R BT.2100 [11] are in use. + +For `transfer_characteristics` set to 18, it implies that Recommendation BT.2020 [4] colorimetry in non-constant luminance and Hybrid Log Gamma (HLG) opto-electronic transfer function (OETF) as defined in Recommendation ITU-R BT.2100 [11] are in use. + +#### 4.5.9.6 Frame rates + +A Bitstream conforming to the H.265/HEVC 8K UHD Operation Point shall have one of the following frame rates: 24; 25; 30; 50; 60; 24/1.001; 30/1.001; 60/1.001 Hz. + +The frame rate may be indicated in the VUI by setting `vui_time_scale` and `vui_num_units_in_tick`. + +#### 4.5.9.7 SEI messages for metadata signalling + +If HDR PQ is in use, then the same requirements and recommendations on SEI messages as defined in clause 4.5.6.7 apply. + +#### 4.5.9.8 Receiver compatibility + +Receivers conforming to the **H.265/HEVC 8K UHD** Operation Point shall support decoding and processing + +- H.265/HEVC 720p HD, +- H.265/HEVC Full HD, +- H.265/HEVC UHD, +- H.265/HEVC Full HD HDR, +- H.265/HEVC UHD HDR, +- HEVC/H.265 Full HD HDR HLG, +- H.265/HEVC UHD HDR HLG, and +- H.265/HEVC 8K UHD Bitstreams. + +Receivers conforming to the **H.265/HEVC 8K UHD** Operation Point should support processing the optional SEI messages defined in clause 4.5.9.7. + +# --- 5 Mapping to 3GP-DASH delivery + +## 5.1 General + +### 5.1.1 MPD and 3GP-DASH format + +The MPD shall conform to the 3GP-DASH format [8] with the constraints defined in clause 5.1.3. The MPD may signal the appropriate profiles parameter as defined below in the **MPD@profiles** attribute. + +For the delivery as part of 5G Media Downlink Streaming, in addition to the requirements in this clause 5, also the requirements in TS 26.247 [8], clause 7.3.11, for the 5G Media Streaming DASH Interoperability Point and the requirements in TS 26.511 [12], clause 5.4 for the TV Video profile apply. + +### 5.1.2 File Format Signalling + +Representations used in the context of the specification shall conform to the 3GP File Format [7] and the 3GP-DASH Segment format [8] with the following further requirements: + +- The '3gtv' ISO brand shall be set as a `compatible_brand` in the File Type Box ('ftyp'). +- The value of the `duration` field in the Movie Header Box ('mvhd') shall be set to a value of '0' +- The Track Header Box ('tkhd') shall obey the following constraints: + +- The value of the `duration` field shall be set to '0'. +- The `width` and `height` fields for a visual track shall specify the track's visual presentation size as fixed-point 16.16 values expressed in on a uniformly sampled grid (commonly called square pixels) +- The Media Header Box ('`mdhd`') shall obey the following constraints: + - The value of the `duration` field shall be set to '0'. +- The Video Media Header ('`vmhd`') shall obey the following constraints: + - The value of the `version` field shall be set to '0'. + - The value of the `graphicsmode` field shall be set to '0'. + - The value of the `opcolor` field shall be set to {'0', '0', '0'}. +- The Sample Description Box ('`stsd`') shall obey the following constraints: + - A visual sample entry shall be used. + - The box shall include a NAL Structured Video Parameter Set. + - the maximum width and height values shall correspond to the maximum cropped horizontal and vertical sample counts indicated in any Sequence Parameter Set in the track. + - It shall contain a Decoder Configuration Record which signals the Profile, Level, and other parameters in the video track. +- The `entry_count` field of the Sample-to-Chunk Box ('`stsc`') shall be set to '0'. +- Both the `sample_size` and `sample_count` fields of the Sample Size Box ('`stsz`') box shall be set to zero ('0'). The `sample_count` field of the Sample Size Box ('`stz2`') box shall be set to zero ('0'). The actual sample size information can be found in the Track Fragment Run Box ('`trun`') for the track. + +NOTE: This is because the Movie Box ('`moov`') contains no media samples. + +- The `entry_count` field of the Chunk Offset Box ('`stco`') shall be set to '0'. +- Movie Fragment Header Boxes ('`mfhd`') shall contain `sequence_number` values that are sequentially numbered starting with the number 1 and incrementing by +1, sequenced by movie fragment storage and presentation order. +- Any Segment Index Box ('`sidx`'), if present, shall obey the additional constraints: + - the `timescale` field shall have the same value as the `timescale` field in the Media Header Box ('`mdhd`') within the same track; and + - the `reference_ID` field shall be set to the `track_ID` of the ISO Media track as defined in the Track Header Box ('`tkhd`'). +- For AVCSSampleEntry ('`avc3`') and HEVCSampleEntry ('`hev1`') NAL Structured Video tracks, the '`first_sample_flags`' shall signal the picture type of the first sample in each movie fragment as specified below. + - `sample_is_non_sync_sample=0`: If the first sample is a sync sample. + - `sample_is_non_sync_sample=1`: If the first sample is not a sync sample. + - `sample_depends_on=2`: If the first sample is an I frame. +- The Colour Information Box ('`colr`') should be present. If present, it shall signal the `colour_primaries`, `transfer_characteristics` and `matrix_coeffs` applicable to all the bitstreams associated with this sample entry. + +- The sample timing shall obey the frame rate requirements for each Operation Point. + +For a video track conforming to these above constraints to also conform to a video CMAF track according to ISO/IEC 23000-19 [13], at least the following additional constraints apply: + +- The field matrix is set to its default values as defined in ISO/IEC 14496-12, except to indicate video orientation +- The Sync Sample Box ('stss') has an entry\_count of zero if present +- If Segment Index Boxes ('sidx') exists + - the timescale field has the same value as the timescale field in the Media Header Box ('mdhd') within the same track; and + - the reference\_ID field is set to the track\_ID of the ISO Media track as defined in the Track Header Box ('tkhd'). + +For a track that conforms to the CMAF track constraints according to ISO/IEC 23000-19 [13] to also conform to the the 3GPP profile as defined in this specification, at least the following additional constraints apply: + +- The value of the duration field in the Movie Header Box ('mvhd') is set to a value of '0'. +- The value of the duration field in the Media Header Box ('mdhd') is set to '0'. +- A NAL Structured Video Parameter Set is present in the Sample Description Box ('stsd'). +- Movie Fragment Header Boxes ('mfhd') contain sequence\_number values that are sequentially numbered starting with the number 1 and incrementing by +1, sequenced by movie fragment storage and presentation order. +- If Segment Index Boxes ('sidx') exist, each subsegment referenced in the SegmentIndexBox is a single CMAF fragment contained in the CMAF track file. + +### 5.1.3 Adaptation Set Constraints + +For a video Adaptation Set, the following constraints apply: + +- The @codecs parameter shall be present on Adaptation Set level and shall signal the maximum required capability to decode any Representation in the Adaptation Set. The @codecs parameter should be signalled on the representation level if different from the one on Adaptation Set level. +- The @profiles parameter may be present to signal the constraints for the Adaptation Set. +- The attributes @maxWidth and @maxHeight shall be present. They are expected to be used to signal the original source content format. This means that they may exceed the actual largest size of any coded Representation in one Adaptation Set. More details for each Operation Point are provided. +- The @width and @height shall be signalled for each Representation (possibly defaulted on Adaptation Set level) and shall match the values of the maximum width and height in the Sample Description box of the contained Representation. +- The Chroma Format may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the @schemeIdURI attribute to urn:mpeg:mpegB:cicp:MatrixCoefficients as defined ISO/IEC 23091-2 [10] and the @value attribute according to Table 4 of ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI. + - The signalling shall be on Adaptation Set level. +- The Color Primaries and Transfer Function shall be signalled unless ITU-R BT.709 is used. If signalled: + +- An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics` as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI. +- The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. +- The maximum frame rate may be signalled on Adaptation Set using the `@maxFrameRate` attribute. +- The `@frameRate` shall be signalled for each Representation (possibly defaulted on Adaptation Set level). In one Adaptation Set, only frame rates shall be present from one of the following subsets: + - 24 Hz with proposed signalling `@frameRate="24"` + - 25 Hz, 50 Hz with proposed signalling `@frameRate="25"` or `@frameRate="50"`, + - 30 Hz, 60 Hz with proposed signalling `@frameRate="30"` or `@frameRate="60"`, + - 24/1.001 Hz with proposed signalling `@frameRate="24000/1001"`, + - 30/1.001 Hz, 60/1.001 Hz with proposed signalling `@frameRate="30000/1001"` or `@frameRate="60000/1001"`. +- Random Access Points shall be signalled by `@startsWithSAP` set to 1, 2 or 3. + +## 5.2 H.264/AVC 720p HD Operation Point + +### 5.2.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.264/AVC 720p HD** Operation Point as defined in clause 4.4.2 and the Adaptation Set conforms to the MPD signalling according to clause 5.2.2 and 5.2.4, and the Representations conform to the file format constraints in clause 5.2.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using `"urn:3GPP:video:op:h264-720p-HD"`. + +### 5.2.2 MPD Signalling + +The requirements as defined in clause 5.1.2 shall apply. In addition, the conditions in 5.2.4 shall apply. + +### 5.2.3 File Format Constraints + +For Representations conforming to the **H.264/AVC 720p HD** Operation Point the following requirements apply. + +The requirements as defined in clause 5.1.2 shall apply. In addition, the following shall apply. + +The syntax and values for visual sample entry shall be set as follows: + +- It shall conform to `AVCSampleEntry` (`'avc1'`) or `AVCSampleEntry` (`'avc3'`) as defined in ISO/IEC 14496-15 [9]. +- If `AVCSampleEntry` (`'avc3'`) is used the following requirements apply: + - If the sample is a Sync Sample, all parameter sets needed for decoding that sample SHALL be included in the sample itself. + - If the sample is at the start of a Segment or a Subsegment, (i.e. a random access point position) that is not a Sync Sample, all parameter sets needed for decoding that sample shall occur in one of the samples between the starting point and that sample inclusive. + +- The video track shall be encoded using the requirements and recommendations for H.264/AVC 720p HD Operation Point as defined in clause 4.4.2. + +### 5.2.4 Adaptation Set Constraints + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- @maxWidth shall be set to 1280 and @maxHeight shall be set to 720. +- The @codecs parameter shall be set to avc1.64Y01F or avc3.64Y01F, +- @width and @height for Representations shall be set to one of the following pairs: (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). +- @frameRate shall be set to one of the following values: "24", "25", "30", "24000/1001", or "30000/1001". + +## 5.3 H.264/AVC Full HD Operation Point + +### 5.3.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.264/AVC Full HD** Operation Point as defined in clause 4.4.3 and the Adaptation Set conforms to the MPD signalling according to clause 5.3.2 and 5.3.4, and the Representations conform to the file format constraints in clause 5.3.3, then the @profiles parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h264-Full-HD". + +### 5.3.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.3.4 shall apply. + +### 5.3.3 File Format Signalling + +For Representations conforming to the **H.264/AVC Full HD** Operation Point the following requirements apply. + +The requirements as defined in clause 5.2.3 shall apply. In addition, the video track shall be encoded using the requirements and recommendations for H.264/AVC Full HD Operation Point as defined in clause 4.4.3. + +### 5.3.4 Adaptation Set Constraints + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- @maxWidth and @maxHeight shall be set to one of the following pairs: (1920, 1080), (1280, 720) +- The @codecs parameter shall be set to avc1.64Y030 or avc3.64Y030, +- @width and @height for Representations shall be set to one of the following pairs: (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). +- If ITU-R BT.2020 is used, then the Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled as defined in clause 5.1.3. + +## 5.4 H.265/HEVC 720p HD Operation Point + +### 5.4.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC 720p HD** Operation Point as defined in clause 4.5.2 and the Adaptation Set conforms to the MPD signalling according to + +clause 5.4.2 and 5.4.4, and the Representations conform to the file format constraints in clause 5.4.3, then the @profiles parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-720p-HD". + +### 5.4.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.4.4 shall apply. + +### 5.4.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC 720p HD** Operation Point the following requirements apply. + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- It shall conform to HEVCSampleEntry ('hvc1') or HEVCSampleEntry ('hev1') as defined in ISO/IEC 14496-15 [9]; +- If HEVCSampleEntry ('hev1') is used the following requirements apply: + - If the sample is a Sync Sample, all parameter sets needed for decoding that sample shall be included in the sample itself. + - If the sample is at the start of a Segment or a Subsegment, (i.e. a random access point position) that is not a Sync Sample, all parameter sets needed for decoding that sample occur in one of the samples between the starting point and that sample inclusive. +- The video track shall be encoded using the requirements and recommendations for H.265/HEVC 720p HD Operation Point as defined in clause 4.5.2. + +### 5.4.4 Adaptation Set Constraints + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- @maxWidth shall be set to 1280 and @maxHeight shall be set to 720. +- The @codecs parameter shall be set to hev1.1.2.L93.B0 or hvc1.1.2.L93.B0, +- @width and @height for Representations shall be set to one of the following pairs: (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). +- @frameRate shall be set to one of the following values: "24", "25", "30", "24000/1001", or "30000/1001". + +## 5.5 H.265/HEVC Full HD Operation Point + +### 5.5.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC Full HD** Operation Point as defined in clause 4.5.3 and the Adaptation Set conforms to the MPD signalling according to clause 5.5.2 and 5.5.4, and the Representations conform to the file format constraints in clause 5.5.3, then the @profiles parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-Full-HD". + +### 5.5.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.5.4 shall apply. + +### 5.5.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC Full HD** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. In addition, the video track shall be encoded using the requirements and recommendations for H.265/HEVC Full HD Operation Point as defined in clause 4.5.3. + +### 5.5.4 Adaptation Set Constraints + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- `@maxWidth` and `@maxHeight` shall be set to one of the following pairs: (1920, 1080), (1280, 720). +- The `@codecs` parameter shall be set to hev1.2.4.L123.B0 or hvc1.2.4.L123.B0, +- `@width` and `@height` for Representations shall be set to one of the following pairs: (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). +- If ITU-R BT.2020 is used, then the Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled as defined in clause 5.1.3. +- `@frameRate` shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". + +If the SEI messages for HLG Signaling as defined in clause 4.5.3.8 is present in the bitstream, then a Supplemental Descriptor should be present with the `@schemeIdUri` attribute set to `urn:mpeg:mpegB:cicp:TransferCharacteristics` as defined ISO/IEC 23091-2 [10] and the `@value` attribute according the "Transfer characteristics" Table of ISO/IEC 23091-2 [10] is set to 18. + +## 5.6 H.265/HEVC UHD Operation Point + +### 5.6.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC UHD** Operation Point as defined in clause 4.5.4 and the Adaptation Set conforms to the MPD signalling according to clause 5.6.2 and 5.6.4, and the Representations conform to the file format constraints in clause 5.6.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using `"urn:3GPP:video:op:h265-UHD"`. + +### 5.6.2 MPD Signalling + +The requirements as defined in clause 5.1.2 shall apply. In addition, the conditions in 5.6.3 shall apply. + +### 5.6.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC UHD** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. The video track shall be encoded using the requirements and recommendations for H.265/HEVC UHD Operation Point as defined in clause 4.5.4. + +### 5.6.4 Adaptation Set Constraint + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- `@maxWidth` and `@maxHeight` shall be set to one of the following pairs: (3840, 2160), (1920, 1080), (1280, 720). +- The `@codecs` parameter shall be set to hev1.2.4.L153.B0 or hvc1.2.4.L153.B0. + +- @width and @height for Representations shall be set to one of the following pairs: (3840, 2160), (3200, 1800), (2560, 1440), (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). @width and @height shall not be greater than @MaxWidth and @MaxHeight respectively. +- @frameRate shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". +- The Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled to indicate ITU-R BT.2020 as defined in clause 5.1.3. + +If the SEI messages for HLG Signaling as defined in clause 4.5.3.8 is present in the bitstream, then a Supplemental Descriptor should be present with the @schemeIdUri attribute set to urn:mpeg:mpegB:cicp:TransferCharacteristics as defined ISO/IEC 23091-2 [10] and the @value attribute according the "Transfer characteristics" Table of ISO/IEC 23091-2 [10] is set to 18. + +## 5.7 H.265/HEVC Full HD HDR Operation Point + +### 5.7.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC Full HD HDR** Operation Point as defined in clause 4.5.5 and the Adaptation Set conforms to the MPD signalling according to clause 5.7.2 and 5.7.4, and the Representations conform to the file format constraints in clause 5.7.3, then the @profiles parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-Full-HD-HDR". + +### 5.7.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.7.4 shall apply. + +### 5.7.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC Full HD HDR** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. The video track shall be encoded using the requirements and recommendations for H.265/HEVC Full HD HDR Operation Point as defined in clause 4.5.5. + +If sample entry hvc1 is in use, then any possibly present Mastering display colour volume SEI message or any possibly present Content light level information SEI message shall be provided in the decoder configuration record and shall be constant for the entire file. + +### 5.7.4 Adaptation Set Constraint + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- @maxWidth and @maxHeight shall be set to one of the following pairs: (1920, 1080), (1280, 720). +- The @codecs parameter shall be set to one of the values defined in Table 5.1, depending on the operating mode as defined in clause 4.5.5.9, except that the level indication may indicate a lower level to which all the applicable Bitstreams conform. + +**Table 5.1: Codecs parameters for different HD HDR Operating modes** + +| Operation Modes name | Codecs Parameter for hvc1 | Codecs Parameter for hev1 | +|--------------------------|---------------------------|---------------------------| +| HEVC/H.265 HDR 720p HD30 | hvc1.2.4.L83.B0 | hev1.2.4.L83.B0 | +| HEVC/H.265 HDR 720p HD60 | hvc1.2.4.L93.B0 | hev1.2.4.L93.B0 | +| HEVC/H.265 HDR Full HD30 | hvc1.2.4.L113.B0 | hev1.2.4.L113.B0 | +| HEVC/H.265 HDR Full HD60 | hvc1.2.4.L123.B0 | hev1.2.4.L123.B0 | + +- `@width` and `@height` for Representations shall be set to one of the following pairs: (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). `@width` and `@height` shall not be greater than `@MaxWidth` and `@MaxHeight` respectively. +- `@frameRate` shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". +- The Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled to indicate ITU-R BT.2020 and BT.2100 PQ as defined in clause 5.1.3. In particular, the Essential Descriptors shall be present to signal BT.2020 and BT.2100 PQ as follows: + - an Essential Descriptor shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI, i.e. the value is set to 9. + - Essential Descriptors shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics`, respectively, as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to the "Colour primaries" Table and the "Transfer characteristics" Table of ISO/IEC 23091-2 [10], respectively. The values shall match the values set in the VUI, i.e. + - `urn:mpeg:mpegB:cicp:ColourPrimaries` with value set to 9. + - `urn:mpeg:mpegB:cicp:TransferCharacteristics` with value set to 16. + - The Essential Descriptors, and if applicable the Supplementary Descriptor, shall be on Adaptation Set level only, i.e all Representations in one Adaptation Set are required to have the same Matrix Coefficients, Color Primaries and Transfer Function. + - If any Representation contains a mastering display colour volume SEI message or a content light level information SEI message, the same SEI message shall be present in all Representations in the Adaptation Set. + - For `hvc1` this implies that the SEI messages shall be provided in the decoder configuration record of every Representation. + - For `hev1`, if any of such SEI message is carried inband within a segment/subsegment of any Representation of the Adaptation Set, it shall be carried with the first picture of that segment/subsegment in decode order in all Representations of this Adaptation Set. + +## 5.8 H.265/HEVC UHD HDR Operation Point + +### 5.8.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC UHD HDR** Operation Point as defined in clause 4.5.6 and the Adaptation Set conforms to the MPD signalling according to clause 5.8.2 and 5.8.4, and the Representations conform to the file format constraints in clause 5.8.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-UHD-HDR". + +### 5.8.2 MPD Signalling + +The requirements as defined in clause 5.1.2 shall apply. In addition, the conditions in 5.8.4 shall apply. + +### 5.8.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC UHD HDR** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. The video track shall be encoded using the requirements and recommendations for H.265/HEVC UHD HDR Operation Point as defined in clause 4.5.6. + +If sample entry hvc1 is in use, then any possibly present Mastering display colour volume SEI message or any possibly present Content light level information SEI message shall be provided in the decoder configuration record and shall be constant for the entire file. + +### 5.8.4 Adaptation Set Constraint + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- @maxWidth shall be set to 3840 and @maxHeight shall be set to 2160. +- The @codecs parameter shall be set to one of the values defined in Table 5.2, depending on the operating mode as defined in clause 4.5.6.9, + +**Table 5.2: Codecs parameters for different UHD HDR Operating modes** + +| Operation Modes name | Codecs Parameter for hvc1 | Codecs Parameter for hev1 | +|----------------------|---------------------------|---------------------------| +| HEVC/H.265 HDR UHD30 | hvc1.2.4.L143.B0 | hev1.2.4.L143.B0 | +| HEVC/H.265 HDR UHD60 | hvc1.2.4.L153.B0 | hev1.2.4.L153.B0 | + +- @width and @height for Representations shall be set to one of the following pairs: (3840, 2160), (3200, 1800), (2560, 1440), (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). +- @frameRate shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". +- The Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled to indicate ITU-R BT.2020 and BT.2100 PQ as defined in clause 5.1.3. In particular, the Essential Descriptors shall be present to signal BT.2020 and BT.2100 PQ as follows: + - an Essential Descriptor shall be used to signal the value by setting the @schemeIdUri attribute to urn:mpeg:mpegB:cicp:MatrixCoefficients as defined ISO/IEC 23091-2 [10] and the @value attribute according to Table 4 of ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI, i.e. the value is set to 9. + - Essential Descriptors shall be used to signal the value by setting the @schemeIdUri attribute to urn:mpeg:mpegB:cicp:ColourPrimaries and urn:mpeg:mpegB:cicp:TransferCharacteristics, respectively, as defined ISO/IEC 23091-2 [10] and the @value attribute according to the "Colour primaries" Table and the "Transfer characteristics" Table of ISO/IEC 23091-2 [10], respectively. The values shall match the values set in the VUI, i.e. + - urn:mpeg:mpegB:cicp:ColourPrimaries with value set to 9. + - urn:mpeg:mpegB:cicp:TransferCharacteristics with value set to 16. + - The Essential Descriptors, and if applicable the Supplementary Descriptor, shall be on Adaptation Set level only, i.e all Representations in one Adaptation Set are required to have the same Matrix Coefficients, Color Primaries and Transfer Function. + - If any Representation contains a mastering display colour volume SEI message or a content light level information SEI message, the same SEI message shall be present in all Representations in the Adaptation Set. + - For hvc1 this implies that the SEI messages shall be provided in the decoder configuration record of every Representation. + - For hev1, if any of such SEI message is carried inband within a segment/subsegment of any Representation of the Adaptation Set, it shall be carried with the first picture of that segment/subsegment in decode order in all Representations of this Adaptation Set. + +## 5.9 H.265/HEVC Full HD HDR HLG Operation Point + +### 5.9.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC Full HD HDR HLG** Operation Point as defined in clause 4.5.7 and the Adaptation Set conforms to the MPD signalling according to clause 5.9.2 and 5.9.4, and the Representations conform to the file format constraints in clause 5.9.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-Full-HD-HDR-HLG". + +### 5.9.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.9.4 shall apply. + +### 5.9.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC Full HD HDR HLG** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. The video track shall be encoded using the requirements and recommendations for H.265/HEVC Full HD HDR HLG Operation Point as defined in clause 4.5.7. + +### 5.9.4 Adaptation Set Constraint + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- `@maxWidth` and `@maxHeight` shall be set to one of the following pairs: (1920, 1080), (1280, 720). +- The `@codecs` parameter shall be set to one of the values defined in Table 5.1, depending on the operating mode as defined in clause 4.5.7.8, except that the level indication may indicate a lower level to which all the applicable Bitstreams conform. + +**Table 5.1: Codecs parameters for different HD HDR Operating modes** + +| Operation Modes name | Codecs Parameter for hvc1 | Codecs Parameter for hev1 | +|------------------------------|---------------------------|---------------------------| +| HEVC/H.265 HDR HLG 720p HD30 | hvc1.2.4.L83.B0 | hev1.2.4.L83.B0 | +| HEVC/H.265 HDR HLG 720p HD60 | hvc1.2.4.L93.B0 | hev1.2.4.L93.B0 | +| HEVC/H.265 HDR HLG Full HD30 | hvc1.2.4.L113.B0 | hev1.2.4.L113.B0 | +| HEVC/H.265 HDR HLG Full HD60 | hvc1.2.4.L123.B0 | hev1.2.4.L123.B0 | + +- `@width` and `@height` for Representations shall be set to one of the following pairs: (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). `@width` and `@height` shall not be greater than `@MaxWidth` and `@MaxHeight` respectively. +- `@frameRate` shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". +- The Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled to indicate ITU-R BT.2020 and BT.2100 HLG as defined in clause 5.1.3. In particular, the Essential Descriptors shall be present to signal BT.2020 and BT.2100 HLG as follows: + - an Essential Descriptor shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to the "Matrix coefficients" Table of ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI, i.e. the value is set to 9. + - Essential Descriptors shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and + +urn:mpeg:mpegB:cicp:TransferCharacteristics, respectively, as defined ISO/IEC 23091-2 [10] and the @value attribute according to the "Colour primaries" Table and the "Transfer characteristics" Table of ISO/IEC 23091-2 [10], respectively. The values shall match the values set in the VUI, i.e. + +- urn:mpeg:mpegB:cicp:ColourPrimaries with value set to 9. +- set to either 18 or 14. If 14 is signalled for HLG\_HDR, a Supplementary Descriptor with the same attributes shall be used to signal the value 18, and the @profiles parameter shall not include "urn:3GPP:video:op:h265-Full-HD", but should include "urn:3GPP:video:op:h265-Full-HD-HDR-HLG". +- The Essential Descriptors, and if applicable the Supplementary Descriptors, shall be on Adaptation Set level only, i.e all Representations in one Adaptation Set are required to have the same Matrix Coefficients, Color Primaries and Transfer Function. + +## 5.10 H.265/HEVC UHD HDR HLG Operation Point + +### 5.10.1 Operation Point Identifier + +If all Representations in an Adaptation Set conforms to the elementary stream constraints for the **H.265/HEVC UHD HDR HLG** Operation Point as defined in clause 4.5.8 and the Adaptation Set conforms to the MPD signalling according to clause 5.10.2 and 5.10.4, and the Representations conform to the file format constraints in clause 5.10.3, then the @profiles parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-UHD-HDR-HLG". + +### 5.10.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.10.4 shall apply. + +### 5.10.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC UHD HDR HLG** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. The video track shall be encoded using the requirements and recommendations for H.265/HEVC UHD HDR HLG Operation Point as defined in clause 4.5.8. + +### 5.10.4 Adaptation Set Constraint + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- @maxWidth shall be set to 3840 and @maxHeight shall be set to 2160. +- The @codecs parameter shall be set to one of the values defined in Table 5.2, depending on the operating mode as defined in clause 4.5.6.9, + +**Table 5.2: Codecs parameters for different UHD HDR HLG Operating modes** + +| Operation Modes name | Codecs Parameter for hvc1 | Codecs Parameter for hev1 | +|--------------------------|---------------------------|---------------------------| +| HEVC/H.265 HDR HLG UHD30 | hvc1.2.4.L143.B0 | hev1.2.4.L143.B0 | +| HEVC/H.265 HDR HLG UHD60 | hvc1.2.4.L153.B0 | hev1.2.4.L153.B0 | + +- @width and @height for Representations shall be set to one of the following pairs: (3840, 2160), (3200, 1800), (2560, 1440), (1920, 1080), (1600, 900), (1280, 720), (960, 540), (854, 480), (640, 360), or (426, 240). +- @frameRate shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". + +- The Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled to indicate ITU-R BT.2020 and BT.2100 HLG as defined in clause 5.1.3. In particular, the Essential Descriptors shall be present to signal BT.2020 and BT.2100 HLG as follows: + - an Essential Descriptor shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to the “Matrix coefficients” Table of ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI, i.e. the value is set to 9. + - Essential Descriptors shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics`, respectively, as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to the "Colour primaries" Table and the "Transfer characteristics" Table of ISO/IEC 23091-2 [10], respectively. The values shall match the values set in the VUI, i.e. + - `urn:mpeg:mpegB:cicp:ColourPrimaries` with value set to 9. + - set to either 18 or 14. If 14 is signalled for HLG\_HDR, a Supplementary Descriptor with the same attributes shall be used to signal the value 18, and the `@profiles` parameter shall not include "urn:3GPP:video:op:h265-UHD", but should include "urn:3GPP:video:op:h265-UHD-HDR-HLG". + - The Essential Descriptors, and if applicable the Supplementary Descriptors, shall be on Adaptation Set level only, i.e all Representations in one Adaptation Set are required to have the same Matrix Coefficients, Color Primaries and Transfer Function. + +## 5.11 H.265/HEVC 8K UHD Operation Point + +### 5.11.1 Operation Point Identifier + +If all Representations in an Adaptation Set conform to the elementary stream constraints for the **H.265/HEVC 8K UHD** Operation Point as defined in clause 4.9.6 and the Adaptation Set conforms to the MPD signalling according to clause 5.11.2 and 5.11.4, and the Representations conform to the file format constraints in clause 5.8.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:video:op:h265-8K-UHD". + +### 5.11.2 MPD Signalling + +The requirements as defined in clause 5.1.1 shall apply. In addition, the conditions in 5.11.4 shall apply. + +### 5.11.3 File Format Constraints + +For Representations conforming to the **H.265/HEVC 8K UHD** Operation Point the following requirements apply. + +The requirements as defined in clause 5.4.3 shall apply. The video track shall be encoded using the requirements and recommendations for H.265/HEVC 8K UHD Operation Point as defined in clause 4.9.6. + +In addition, the Representation shall conform to an MPEG CMAF Track that conforms to the ‘c8k0’ media profile as defined ISO/IEC 23000-19 [13]. + +If sample entry `hvc1` is in use, then any possibly present Mastering display colour volume SEI message or any possibly present Content light level information SEI message shall be provided in the decoder configuration record and shall be constant for the entire file. + +### 5.11.4 Adaptation Set Constraint + +The requirements as defined in clause 5.1.3 shall apply. In addition, the following shall apply: + +- `@maxWidth` shall be set to 7680 and `@maxHeight` shall be set to 4320. +- The `@codecs` parameter shall be set to either `hvc1.2.4.L183.B0` or `hev1.2.4.L183.B0`. +- `@width` and `@height` for Representations shall be set to one of the following pairs: (7680, 4320), (5120, 2880), (3840, 2160), (3200, 1800), (2560, 1440), (1920, 1080), (1600, 900), (1280, 720), (960, 540), or (854, 480). +- `@frameRate` shall be set to one of the following values: "24", "25", "30", "50", "60", "24000/1001", "30000/1001" or "60000/1001". +- The Colour Primaries, Transfer Characteristics and Matrix Coefficients shall be signalled to indicate ITU-R BT.2020, and BT.2100 PQ and BT.2100 HLG as defined in clause 5.1.3. In particular, the Essential Descriptors shall be present to signal BT.2020, and BT.2100 PQ and BT.2100 HLG as follows: + - an Essential Descriptor shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to ISO/IEC 23091-2 [10]. The values shall match the values set in the VUI, i.e. the value is set to 9. + - Essential Descriptors shall be used to signal the value by setting the `@schemeIdUri` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics`, respectively, as defined ISO/IEC 23091-2 [10] and the `@value` attribute according to the "Colour primaries" Table and the "Transfer characteristics" Table of ISO/IEC 23091-2 [10], respectively. The values shall match the values set in the VUI, i.e. + - `urn:mpeg:mpegB:cicp:ColourPrimaries` with value set to 9. + - `urn:mpeg:mpegB:cicp:TransferCharacteristics` with value set to + - 14 if SDR is in use, + - 16 if HDR PQ is in use, or + - 18 if HDR HLG is in use. + - The Essential Descriptors, and if applicable the Supplementary Descriptor, shall be on Adaptation Set level only, i.e all Representations in one Adaptation Set are required to have the same Matrix Coefficients, Color Primaries and Transfer Function. + - If any Representation contains a mastering display colour volume SEI message or a content light level information SEI message, the same SEI message shall be present in all Representations in the Adaptation Set. + - For `hvc1` this implies that the SEI messages shall be provided in the decoder configuration record of every Representation. + - For `hev1`, if any of such SEI message is carried inband within a segment/subsegment of any Representation of the Adaptation Set, it shall be carried with the first picture of that segment/subsegment in decode order in all Representations of this Adaptation Set. + +# Annex A (informative): Registration Information + +## A.1 3GPP Registered URIs + +The clause documents the registered URIs in this specification following the process in + +Table A-1 lists all registered URN values as well as + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +**Table A-1: 3GPP Registered URNs** + +| URN | Description | Reference | Contact | Remarks | +|----------------------------------------|------------------------------------------------------------------------|--------------------------|---------------------------------------------|---------| +| urn:3GPP:video:op:h264-720p-HD | DASH profile identifier for H.264/AVC 720p HD Operation Point | TS 26.116, clause 5.2.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h264-Full-HD | DASH profile identifier for H.264/AVC Full HD Operation Point | TS 26.116, clause 5.3.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-720p-HD | DASH profile identifier for H.265/HEVC 720p HD Operation Point | TS 26.116, clause 5.4.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-Full-HD | DASH profile identifier for H.265/HEVC Full HD Operation Point | TS 26.116, clause 5.5.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-UHD | DASH profile identifier for H.265/HEVC UHD Operation Point | TS 26.116, clause 5.6.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-Full-HD-HDR | DASH profile identifier for H.265/HEVC Full HD HDR Operation Point | TS 26.116, clause 5.7.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-UHD-HDR | DASH profile identifier for H.265/HEVC UHD HDR Operation Point | TS 26.116, clause 5.8.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-Full-HD-HDR-HLG | DASH profile identifier for H.265/HEVC Full HD HDR HLG Operation Point | TS 26.116, clause 5.9.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-UHD-HDR-HLG | DASH profile identifier for H.265/HEVC UHD HDR HLG Operation Point | TS 26.116, clause 5.10.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:video:op:h265-8K-UHD | DASH profile identifier for H.265/HEVC 8K UHD Operation Point | TS 26.116, clause 5.11.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|-----------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | 75 | | | | | Version for Release 14 | 14.0.0 | +| 2017-12 | 78 | SP-170821 | 0004 | - | A | URN Registration for DASH profiles | 14.1.0 | +| 2017-12 | 78 | SP-170821 | 0006 | - | A | Corrections to TV Video Profiles | 14.1.0 | +| 2017-12 | 78 | SP-170826 | 0007 | 1 | B | HDR Support in TV Video Profiles | 15.0.0 | +| 2017-12 | 78 | SP-170826 | 0008 | - | B | URN Registration for DASH profiles | 15.0.0 | +| 2018-09 | 81 | SP-180638 | 0012 | - | F | Correction on AVC Colour Parameters | 15.1.0 | +| 2018-09 | 81 | SP-180656 | 0009 | - | B | HLG HDR video | 16.0.0 | +| 2018-12 | 82 | SP-180976 | 0013 | - | F | HLG operating points | 16.1.0 | +| 2020-09 | SA#89-e | SP-200659 | 0014 | 2 | F | TV Video Profiles and 5G Media Streaming | 16.2.0 | +| 2021-06 | SA#92-e | SP-210532 | 0015 | - | F | Spatial positioning of the chroma samples for TV Video Profiles | 16.3.0 | +| 2021-06 | Post SA#92-e | | | | | Minor Editorial corrections in Section 4.5.3.5 and 4.5.4.5 | 16.3.1 | +| 2021-09 | SA#93-e | SP-210822 | 0016 | - | F | Miscellaneous Fixes to TV Video Profile | 16.4.0 | +| 2021-12 | SA#94-e | SP-211346 | 0017 | | F | Reference Fixes to TV Video Profiles | 16.5.0 | +| 2022-03 | SA#95-e | SP-220213 | 0018 | - | B | 8K HEVC Operation Point and CMAF Alignment | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26117/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26117/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc46cd484fd85c31b669345a06576de7874ed0c6 --- /dev/null +++ b/marked/Rel-18/26_series/26117/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee472255fffe47a6f18e032fcb337d0a963e4cf98f68096741c33f34ef85fdd7 +size 9244 diff --git a/marked/Rel-18/26_series/26117/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26117/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1547dc858b4257d7dfe9d152c2ce27b03c57e743 --- /dev/null +++ b/marked/Rel-18/26_series/26117/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14769ea83fbf2d361787ca8d621f3f7dc9335b27ead1cbe6191d963ecb8162d9 +size 5541 diff --git a/marked/Rel-18/26_series/26117/raw.md b/marked/Rel-18/26_series/26117/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..77261fd1a0b0b43134ac440ec91ef79f2a6ebedb --- /dev/null +++ b/marked/Rel-18/26_series/26117/raw.md @@ -0,0 +1,874 @@ + + +# 3GPP TS 26.117 V18.1.0 (2023-06) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Media Streaming (5GMS); Speech and audio profiles (Release 18)** --- + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a small red signal wave icon at its base. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Overview..... | 9 | +| 5 Media Capabilities ..... | 10 | +| 5.1 Introduction ..... | 10 | +| 5.2 Decoding Capabilities ..... | 10 | +| 5.3 Encoding Capabilities ..... | 10 | +| 6 Operation Points..... | 11 | +| 6.1 Introduction ..... | 11 | +| 6.2 Speech Operation Points ..... | 11 | +| 6.2.1 Introduction ..... | 11 | +| 6.2.2 AMR..... | 12 | +| 6.2.2.1 Bitstream Encoding Requirements ..... | 12 | +| 6.2.2.2 Receiver Requirements..... | 12 | +| 6.2.2.3 Sender Requirements ..... | 12 | +| 6.2.3 AMR-WB ..... | 12 | +| 6.2.3.1 Bitstream Requirements..... | 12 | +| 6.2.3.2 Receiver Requirements..... | 12 | +| 6.2.3.3 Sender Requirements ..... | 12 | +| 6.2.4 EVS..... | 12 | +| 6.2.4.1 Bitstream Encoding Requirements ..... | 12 | +| 6.2.4.2 Receiver Requirements..... | 13 | +| 6.2.4.3 Sender Requirements ..... | 13 | +| 6.3 Audio Operation Points..... | 13 | +| 6.3.1 Introduction ..... | 13 | +| 6.3.2 eAAC+ stereo ..... | 13 | +| 6.3.2.1 Bitstream Encoding Requirements ..... | 13 | +| 6.3.2.2 Receiver Requirements..... | 13 | +| 6.3.2.3 Sender Requirements ..... | 13 | +| 6.3.3 AMR-WB+ ..... | 13 | +| 6.3.3.1 Bitstream Encoding Requirements ..... | 13 | +| 6.3.3.2 Receiver Requirements..... | 14 | +| 6.3.3.3 Sender Requirements ..... | 14 | +| 6.3.4 xHE-AAC stereo ..... | 14 | +| 6.3.4.1 Bitstream Encoding Requirements ..... | 14 | +| 6.3.4.2 Receiver Requirements..... | 14 | +| 6.3.4.3 Sender Requirements ..... | 14 | +| 7 Mapping to 5GMS delivery ..... | 14 | +| 7.1 Introduction ..... | 14 | +| 7.2 AMR Media Profile..... | 15 | +| 7.2.1 Mapping to ISO BMFF ..... | 15 | +| 7.2.2 Media Profile Definition..... | 15 | +| 7.2.2.1 CMAF Track Definition ..... | 15 | +| 7.2.2.2 CMAF Switching Set and Media Profile Definition ..... | 15 | +| 7.2.2.3 Mapping to DASH Adaptation Set..... | 15 | +| 7.2.2.4 Playback Requirements..... | 15 | +| 7.2.2.5 Content Generation Requirements..... | 16 | +| 7.3 AMR-WB Media Profile..... | 16 | + +| | | | +|--------------------------------------------------------------|-------------------------------------------------------|-----------| +| 7.3.1 | Mapping to ISO BMFF ..... | 16 | +| 7.3.2 | Media Profile Definition..... | 16 | +| 7.3.2.1 | CMAF Track Definition ..... | 16 | +| 7.3.2.2 | CMAF Switching Set and Media Profile Definition ..... | 16 | +| 7.3.2.3 | Mapping to DASH Adaptation Set..... | 16 | +| 7.3.2.4 | Playback Requirements..... | 17 | +| 7.3.2.5 | Content Generation Requirements..... | 17 | +| 7.4 | EVS Media Profile ..... | 17 | +| 7.4.1 | Mapping to ISO BMFF ..... | 17 | +| 7.4.2 | Media Profile Definition..... | 18 | +| 7.4.2.1 | CMAF Track Definition ..... | 18 | +| 7.4.2.2 | CMAF Switching Set and Media Profile Definition ..... | 18 | +| 7.4.2.3 | Mapping to DASH Adaptation Set..... | 18 | +| 7.4.2.4 | Playback Requirements..... | 18 | +| 7.4.2.5 | Content Generation Requirements..... | 19 | +| 7.5 | void..... | 19 | +| 7.6 | eAAC+ stereo Media Profile..... | 19 | +| 7.6.1 | Void..... | 19 | +| 7.6.2 | Media Profile Definition..... | 19 | +| 7.6.2.1 | CMAF Track Definition ..... | 19 | +| 7.6.2.2 | CMAF Switching Set and Media Profile Definition ..... | 19 | +| 7.6.2.3 | Mapping to DASH Adaptation Set..... | 19 | +| 7.6.2.4 | Playback Requirements..... | 20 | +| 7.6.2.5 | Content Generation Requirements..... | 20 | +| 7.7 | AMR-WB+ Media Profiles ..... | 20 | +| 7.7.1 | Mapping to ISO BMFF ..... | 20 | +| 7.7.2 | Media Profile Definition..... | 21 | +| 7.7.2.1 | CMAF Track Definition ..... | 21 | +| 7.7.2.2 | CMAF Switching Set and Media Profile Definition ..... | 21 | +| 7.7.2.3 | Mapping to DASH Adaptation Set..... | 21 | +| 7.7.2.4 | Playback Requirements..... | 21 | +| 7.7.2.5 | Content Generation Requirements..... | 22 | +| 7.8 | xHE-AAC Media Profile..... | 22 | +| 7.8.1 | CMAF Track Definition ..... | 22 | +| 7.8.2 | CMAF Switching Set and Media Profile Definition ..... | 22 | +| 7.8.3 | Mapping to DASH Adaptation Set..... | 22 | +| 7.8.4 | Playback Requirements ..... | 23 | +| 7.8.5 | Content Generation Requirements ..... | 23 | +| Annex A (informative): Registration Information ..... | | 24 | +| A.1 | 3GPP Registered URIs..... | 24 | +| Annex B (informative): Change history ..... | | 25 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies speech and audio media capabilities, operation points and media profiles for 5G Media Streaming in the context of 3GPP services and deployments. Speech and audio media capabilities, operation points and media profiles are also provided for usage in other streaming applications. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture". +- [3] 3GPP TS 26.071: "Mandatory Speech Codec speech processing functions; AMR Speech CODEC; General description". +- [4] 3GPP TS 26.090: "Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Transcoding functions". +- [5] 3GPP TS 26.073: "ANSI-C code for the Adaptive Multi Rate (AMR) speech codec". +- [6] 3GPP TS 26.104: "ANSI-C code for the floating-point Adaptive Multi Rate (AMR) speech codec". +- [7] 3GPP TS 26.093: "Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Source controlled rate operation". +- [8] 3GPP TS 26.171: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; General description". +- [9] 3GPP TS 26.190: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions". +- [10] 3GPP TS 26.173: "ANSI-C code for the Adaptive Multi Rate - Wideband (AMR-WB) speech codec". +- [11] 3GPP TS 26.204: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; ANSI-C code". +- [12] 3GPP TS 26.193: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Source controlled rate operation". +- [13] 3GPP TS 26.441: "Codec for Enhanced Voice Services (EVS); General Overview". +- [14] 3GPP TS 26.442: "Codec for Enhanced Voice Services (EVS); ANSI C code (fixed-point)". +- [15] 3GPP TS 26.443: "Codec for Enhanced Voice Services (EVS); ANSI C code (floating-point)". +- [16] 3GPP TS 26.445: "Codec for Enhanced Voice Services (EVS); Detailed Algorithmic Description". +- [17] 3GPP TS 26.446: "Codec for Enhanced Voice Services (EVS); Adaptive Multi-Rate - Wideband (AMR-WB) backward compatible functions". + +- [18] 3GPP TS 26.450: "Codec for Enhanced Voice Services (EVS); Discontinuous Transmission (DTX)". +- [19] 3GPP TS 26.401: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description". +- [20] 3GPP TS 26.402: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Additional decoder tools". +- [21] 3GPP TS 26.403: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification; Advanced Audio Coding (AAC) part". +- [22] 3GPP TS 26.404: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Enhanced aacPlus encoder Spectral Band Replication (SBR) part". +- [23] 3GPP TS 26.405: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification parametric stereo part". +- [24] 3GPP TS 26.410: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code". +- [25] 3GPP TS 26.411: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code". +- [26] 3GPP TS 26.290: "Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Transcoding functions". +- [27] 3GPP TS 26.304: "Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Floating-point ANSI-C code". +- [28] 3GPP TS 26.273: "ANSI-C code for the fixed-point Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec". +- [29] 3GPP TS 26.244: "Transparent end-to-end streaming service; 3GPP file format (3GP)". +- [30] ISO/IEC 23000-19:2023 "Information Technology Multimedia Application Format (MPEG-A) – Part 19: Common Media Application Format (CMAF) for segmented media". +- [31] ISO/IEC 23009-1:2022: "Information technology -- Dynamic adaptive streaming over HTTP (DASH) -- Part 1: Media presentation description and segment formats." +- [32] CTA-5003: "Web Application Video Ecosystem (WAVE): Device Playback Capabilities Specification" available here . +- [33] 3GPP TS 26.244: "Transparent end-to-end streaming service; 3GPP file format (3GP)". +- [34] 3GPP TS 26.452: "Codec for Enhanced Voice Services (EVS); ANSI C code; Alternative fixed-point using updated basic operators". +- [35] 3GPP TS 26.447: "Codec for Enhanced Voice Services (EVS); Error concealment of lost packets". +- [36] 3GPP TS 26.511: "5G Media Streaming (5GMS); Profiles, Codecs and Formats". +- [37] ISO/IEC 23003-3: "Information technology — MPEG audio technologies — Part 3: Unified speech and audio coding". +- [38] ISO/IEC 23003-4: "Information technology — MPEG audio technologies — Part 4: Dynamic range control" + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Bitstream:** A media bitstream that conforms to an audio/speech encoding format and certain Operation Point. + +**Media Profile:** A combination of a Bitstream encapsulated into a media container suitable for 5G Media Streaming Delivery. + +**Operation Point:** A collection of discrete combinations of different content formats and the encoding format. + +**Receiver:** A receiver that can decode and render any bitstream that is conforming to a certain Operation Point. + +**Sender:** An entity that can process and encode formats associated to an Operation Point. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|------------------------------------------------------| +| AAC | Advanced Audio Coding | +| ABR | Adaptive BitRate | +| AMR | Adaptive MultiRate | +| CMAF | Common Media Application Format | +| DASH | Dynamic Adaptive Streaming over HTTP | +| DRC | Dynamic Range Control DTX Discontinuous Transmission | +| EVS | Enhanced Voice Services | +| ISO BMFF | ISO Based Media File Format | +| HTTP | Hyper Text Transfer Protocol | +| SBR | Spectral Band Replication | +| URN | Universal Resource Name | +| WAVE | Web Application Video Ecosystem | + +# 4 Overview + +The speech and audio media capabilities defined in this specification are primarily introduced in order to be used as content format in the context of 5G Media Streaming, but not restricted to this use case. Parameters for audio encoder/decoder, content format and transport are defined. + +The present document defines: + +- Media decoding capabilities: the requirements for a receiver in terms of decoding +- Media encoding capabilities: the requirements for a sender in terms of encoding +- Operation Points: A collection of discrete combinations of different content formats and the encoding formats. Operation Points are supported by + - Bitstream Requirements: A media bitstream that conforms to an audio or speech encoding format and certain Operation Point. + +- Receiver Requirements: A function that can decode and playback any Bitstream that is conforming to a certain Operation Point in real-time. + - Sender Requirements: A function that can process and encode any Bitstream that is conforming to a certain Operation Point in real-time. +- +- The integration of each Operation Point in 5G Media Streaming as defined in TS 26.501 [2] and TS 26.511 [36]. + +# 5 Media Capabilities + +## 5.1 Introduction + +This clause documents speech and audio media capabilities in terms of decoding capabilities. + +## 5.2 Decoding Capabilities + +The following speech media decoding capabilities are defined: + +- *AMR*: All decoding requirements for the AMR speech codec as specified in 3GPP TS 26.071 [3], 3GPP TS 26.090 [4], 3GPP TS 26.073 [5] and 3GPP TS 26.104 [6]) including all 8 modes and source-controlled rate operation 3GPP TS 26.093 [7]. +- *AMR-WB*: All decoding requirements for the AMR-WB codec as specified in 3GPP TS 26.171 [8], 3GPP TS 26.190 [9], 3GPP TS 26.173 [10] and 3GPP TS 26.204 [11] including all 9 modes and source-controlled rate operation 3GPP TS 26.193 [12]. +- *EVS*: All decoding requirements for the EVS codec as specified in 3GPP TS 26.441 [13], 3GPP TS 26.445 [16], 3GPP TS 26.442 [14] and 3GPP TS 26.443 [15] as described below including functions for backwards compatibility with AMR-WB (3GPP TS 26.446 [17]) and discontinuous transmission (3GPP TS 26.450 [18]). + +The following audio media decoding capabilities are defined: + +- *eAAC+*: All decoding requirements for the eAAC+ audio codec as specified in 3GPP TS 26.401 [19], 3GPP TS 26.402 [20], 3GPP TS 26.410 [24] and 3GPP TS 26.411 [25]. +- *AMR-WB+*: All decoding requirements for the AMR-WB+ audio codec as specified in 3GPP TS 26.290 [26], 3GPP TS 26.304 [27] and 3GPP TS 26.273 [28]. +- *xHE-AAC stereo*: All decoding requirements for the *xHE-AAC stereo* audio codec as specified in the MPEG-D USAC "Extended high efficiency AAC profile" as defined in ISO/IEC 23003-3 [37] as well as all processing requirements applicable to the MPEG-D DRC loudness control profile and to the dynamic range control profile, level 1 or higher, as specified in ISO/IEC 23003-4 [38]. + +NOTE: xHE-AAC® is a registered trademark of Fraunhofer in Germany and other countries and is used with Fraunhofer's permission. + +## 5.3 Encoding Capabilities + +The following speech media encoding capabilities are defined: + +- *AMR*: The encoding requirements for the AMR speech codec as specified in 3GPP TS 26.401 [19], clause 7, as well as 3GPP TS 26.403 [21], 3GPP TS 26.404 [22] and 3GPP TS 26.405 [23]. +- *AMR-WB*: The encoding requirements for the AMR-WB by one of the following methods: + - according to 3GPP TS 26.173 [10] + - according to 3GPP TS 26.204 [11]; + - the AMR-WB IO mode according to TS 26.442 [14] and TS 26.443 [15], + +- the AMR-WB IO mode according to TS 26.452 [34]. +- *EVS*: The encoding requirements for the EVS codec by one of the following methods: + - TS 26.442 [14] and TS 26.443 [15] encoding functions; or + - TS 26.452 [34] encoding functions. + +The following audio media encoding capabilities are defined: + +- *eAAC+*: The encoding requirements for the AAC+ audio codec as specified 3GPP TS 26.401 [19], clause 7, as well as 3GPP TS 26.403 [21], 3GPP TS 26.404 [22] and 3GPP TS 26.405 [23]. +- *AMR-WB+*: The encoding requirements for the AMR-WB+ audio codec by one of the following methods + - according to 3GPP TS 26.273 [28]; or + - according to 3GPP TS 26.304 [27]. +- *xHE-AAC stereo*: All encoding requirements for the *xHE-AAC stereo* audio codec as specified in the MPEG-D USAC "Baseline USAC" profile as defined in ISO/IEC 23003-3 [37] and with the additional requirements that all encoded media contains the required metadata sets conforming to the MPEG-D DRC loudness control profile or to the dynamic range control profile, level 1 or higher, as specified in ISO/IEC 23003-4 [38]. + +# 6 Operation Points + +## 6.1 Introduction + +The speech and audio Operation Points defined in this clause are primarily introduced in order to be used as content format in the context of 5G Media Streaming, but not restricted to this use case. + +An operation point is a combination of rendering formats and media decoding capabilities. + +For each Operation Point, Bitstream and Receiver requirements are detailed in the remainder of clause 6. + +Table 6.1 provides an overview of the Operation Points defined in the present document. + +**Table 6.1: Speech and Audio Operation Points** + +| Operation Point name | Format Properties | Decoding and Encoding Capabilities | Reference | +|----------------------|---------------------------------------|------------------------------------|-----------| +| AMR speech | Sampling frequency: 8 kHz | AMR | 6.2.2 | +| AMR-WB speech | Sampling frequency: 16 kHz | AMR-WB | 6.2.3 | +| EVS mono | Sampling frequency: 8, 16, 32, 48 kHz | EVS | 6.2.4 | +| eAAC+ stereo | Sampling frequency: 32, 44.1, 48 kHz | eAAC+ | 6.3.2 | +| AMR-WB+ | Sampling frequency: 8, 16, 32, 48 kHz | AMR-WB+ | 6.3.3 | +| xHE-AAC stereo | Sampling frequency: 32, 44.1, 48 kHz | xHE-AAC stereo | 6.3.4 | + +## 6.2 Speech Operation Points + +### 6.2.1 Introduction + +This clause defines speech operation points. For each operation point, the requirements for the bitstream as well as for the receiver are defined. + +### 6.2.2 AMR + +#### 6.2.2.1 Bitstream Encoding Requirements + +The following requirements apply to the **AMR** Operation Point. + +- The sampling frequency shall be 8 kHz. +- The bitstream shall be encoded according to either 3GPP TS 26.073 [5] or 3GPP TS 26.104 [6]. + +Note that the bitstream produced by the AMR encoder consists of 20ms encoded speech frames. + +#### 6.2.2.2 Receiver Requirements + +Receivers conforming to the **AMR** Operation Point shall support the *AMR* speech media decoding capability according to clause 5.2 and shall support playback of the decoded signal. + +#### 6.2.2.3 Sender Requirements + +Senders conforming to the **AMR** Operation Point shall support the *AMR* speech media encoding capability according to clause 5.3 in real-time for any speech source format with sampling frequency 8kHz. + +### 6.2.3 AMR-WB + +#### 6.2.3.1 Bitstream Requirements + +The following requirements apply to the **AMR-WB** Operation Point. + +- The sampling frequency shall be 16 kHz. +- The bitstream shall be encoded by one of the following methods: + - according to 3GPP TS 26.173 [10] + - according to 3GPP TS 26.204 [11]; + - the AMR-WB IO mode according to TS 26.442 [14] and TS 26.443 [15], + - the AMR-WB IO mode according to TS 26.452 [34]. + +Note that the bitstream produced by the AMR-WB encoder consists of 20 ms encoded speech frames. + +#### 6.2.3.2 Receiver Requirements + +Receivers conforming to the **AMR-WB** Operation Point shall support the *AMR-WB* speech media decoding capability according to clause 5.2 and shall support playback of the decoded signal. + +#### 6.2.3.3 Sender Requirements + +Senders conforming to the **AMR-WB** Operation Point shall support the *AMR-WB* speech media encoding capability according to clause 5.3 in real-time for any speech source format with sampling frequency 16kHz. + +### 6.2.4 EVS + +#### 6.2.4.1 Bitstream Encoding Requirements + +The following requirements apply to the **EVS** Operation Point: + +- The sampling frequency shall be one of the following: 8, 16, 32, 48 kHz. + +- The bitstream shall be encoded according to one of the following methods + - TS 26.442 [14] and TS 26.443 [15] encoding functions; or + - TS 26.452 [34] encoding functions. + +Note that the bitstream produced by the EVS encoder consists of 20ms encoded speech frames. + +#### 6.2.4.2 Receiver Requirements + +Receivers conforming to the **EVS** Operation Point shall support the *EVS* speech media decoding capability according to clause 5.2 and shall support playback of the decoded signal. + +#### 6.2.4.3 Sender Requirements + +Senders conforming to the **EVS** Operation Point shall support the *EVS* speech media encoding capability according to clause 5.3 in real-time for any speech source format with sampling frequency 8, 16, 32, 48 kHz. + +## 6.3 Audio Operation Points + +### 6.3.1 Introduction + +This clause defines audio operation points. For each operation point, the requirements for the bitstream as well as for the receiver are defined. + +### 6.3.2 eAAC+ stereo + +#### 6.3.2.1 Bitstream Encoding Requirements + +The following requirements apply to the **eAAC+ stereo** Operation Point. + +- The sampling frequency shall be either 32 kHz, 44.1 kHz or 48 kHz. +- The bitstream shall be encoded according to 3GPP TS 26.401 [19], clause 7, as well as 3GPP TS 26.403 [21], 3GPP TS 26.404 [22] and 3GPP TS 26.405 [23]. + +NOTE: The specified eAAC+ encoder consists of AAC-LC with additional tools that can be enabled (SBR, PS and more), see [19]. + +#### 6.3.2.2 Receiver Requirements + +Receivers conforming to the **eAAC+ stereo** Operation Point shall support the *eAAC+ stereo* media decoding capability according to clause 5.2 and shall support playback of the decoded signal. + +NOTE: The eAAC+ decoder supports decoding of streams encoded with AAC-LC or aacPlus, see [19]. + +#### 6.3.2.3 Sender Requirements + +Senders conforming to the **eAAC+ stereo** Operation Point shall support the *eAAC+ stereo* audio media encoding capability according to clause 5.3 in real-time for any stereo audio source format with sampling frequency 32kHz, 44.1kHz, 48kHz. + +### 6.3.3 AMR-WB+ + +#### 6.3.3.1 Bitstream Encoding Requirements + +The following requirements apply to the **AMR-WB+** Operation Point. + +- The sampling frequency shall be either 8, 16, 32 or 48 kHz. + +- The bitstream shall be encoded by one of the following methods + - according to 3GPP TS 26.273 [28]; or + - according to 3GPP TS 26.304 [27]. + +#### 6.3.3.2 Receiver Requirements + +Receivers conforming to the **AMR-WB+** Operation Point shall support the *AMR-WB+* media decoding capability according to clause 5.2 and shall support playback of the decoded signal. + +#### 6.3.3.3 Sender Requirements + +Senders conforming to the **AMR-WB+** Operation Point shall support the *AMR-WB+* audio media encoding capability according to clause 5.3 in real-time for any stereo audio source format with sampling frequency 8, 16, 32 or 48 kHz. + +### 6.3.4 xHE-AAC stereo + +#### 6.3.4.1 Bitstream Encoding Requirements + +The following requirements apply to the **xHE-AAC stereo** Operation Point. + +- The sampling frequency shall be either 32 kHz, 44.1 kHz or 48 kHz. +- The bitstream shall be encoded according to the MPEG-D USAC "Baseline USAC" profile as defined in ISO/IEC 23003-3 [37] and shall contain the metadata sets conforming to the MPEG-D DRC loudness control profile or to the dynamic range control profile, level 1 or higher, as specified in ISO/IEC 23003-4 [38]. + +#### 6.3.4.2 Receiver Requirements + +Receivers conforming to the **xHE-AAC stereo** Operation Point shall support the *xHE-AAC stereo* media decoding capability according to clause 5.2 and shall support playback of the decoded signal. + +NOTE: The xHE-AAC decoder supports decoding of streams encoded with eAAC+ [19]. Therefore support of xHE-AAC stereo media decoding capabilities implies support of eAAC+ media decoding capabilities. + +#### 6.3.4.3 Sender Requirements + +Senders conforming to the **xHE-AAC stereo** Operation Point shall support the xHE-AAC audio media encoding capability according to clause 5.3 in real-time for any stereo audio source format with sampling frequency 32kHz, 44.1kHz, or 48kHz. + +# --- 7 Mapping to 5GMS delivery + +## 7.1 Introduction + +This clause defines the mapping of the Operation Points as defined in clause 6 to 5G Media Streaming delivery. In particular the following aspects are addressed: + +- Encapsulation of a bitstream into an ISO BMFF track. +- Definition of media content and receivers conforming to media profile including: + - Encapsulation of a bitstream into a CMAF track + - Providing the content in a CMAF Switching Set + - Mapping to DASH-based distribution + +- Playback Requirements for a receiver conforming to this media profile + +## 7.2 AMR Media Profile + +### 7.2.1 Mapping to ISO BMFF + +If media is provided following the operation point **AMR** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'samr' as defined in TS 26.244 [29]. + +### 7.2.2 Media Profile Definition + +#### 7.2.2.1 CMAF Track Definition + +If media is provided following the operation point **AMR** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'samr' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10. + +#### 7.2.2.2 CMAF Switching Set and Media Profile Definition + +If media is provided following the operation point **AMR** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'samr' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF AMR media profile 'camr'. + +#### 7.2.2.3 Mapping to DASH Adaptation Set + +If media is provided following the operation point **AMR** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set: + +- @codecs is set to 'samr' +- @mimeType is set to be compatible with "audio/mp4 profiles='camr'" +- @audioSamplingRate is set to '8000' + +If the Adaptation Set conforms to the constraints for the **AMR** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:amr". + +#### 7.2.2.4 Playback Requirements + +For a receiver supporting the **AMR** media profile the following applies: + +- It shall support the receiver requirements as documented in clause 6.2.2.2 for any CMAF Track conforming to the CMAF **AMR** media profile 'camr' as defined in clause 7.2.2.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF **AMR** media profile 'camr' as defined in clause 7.2.2.2, namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + +- 8.6 Regular Playback of Chunked Content +- 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [29] for any content conforming to a CMAF Switching Set according to CMAF AMR media profile 'camr' as defined in clause 7.2.2.2, namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +#### 7.2.2.5 Content Generation Requirements + +For a transmitter supporting the AMR media profile the following applies: + +- It shall support all media encoding capabilities for AMR as defined in clause 5.3. +- It shall support the sender requirements for AMR as defined in clause 6.2.2.3. +- It shall support the generation of a CMAF Track as defined in clause 7.2.2.2 that conforms to the CMAF Media Profile 'camr' as defined in clause 7.2.2.3. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.2.2.4. + +## 7.3 AMR-WB Media Profile + +### 7.3.1 Mapping to ISO BMFF + +If media is provided following the operation point **AMR-WB** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'sawb' as defined in TS 26.244 [29]. + +### 7.3.2 Media Profile Definition + +#### 7.3.2.1 CMAF Track Definition + +If media is provided following the operation point **AMR-WB** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'sawb' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19, clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10. + +#### 7.3.2.2 CMAF Switching Set and Media Profile Definition + +If media is provided following the operation point **AMR-WB** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'sawb' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF AMR-WB media profile 'camw'. + +#### 7.3.2.3 Mapping to DASH Adaptation Set + +If media is provided following the operation point **AMR-WB** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set: + +- @codecs is set to 'sawb' + +- `@mimeType` is set to be compatible with "audio/mp4 profiles='camw'" +- `@audioSamplingRate` is set to '16000' + +If the Adaptation Set conforms to the constraints for the **AMR-WB** Operation Point as defined in this clause, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:amr-wb". + +#### 7.3.2.4 Playback Requirements + +For a receiver supporting the AMR-WB media profile the following applies: + +- It shall support the receiver requirements as documented in clause 6.2.3.2 for any CMAF Track conforming to the CMAF AMR-WB media profile 'camw' as defined in clause 7.3.2.2. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB media profile 'camw' as defined in clause 7.3.2.2, namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB media profile 'camw' as defined in clause 7.3.2.2, namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +#### 7.3.2.5 Content Generation Requirements + +For a transmitter supporting the AMR-WB media profile the following applies: + +- It shall support all media encoding capabilities for AMR-WB as defined in clause 5.3. +- It shall support the sender requirements for AMR-WB as defined in clause 6.2.3.3. +- It shall support the generation of a CMAF Track as defined in clause 7.3.2.2 that conforms to the CMAF Media Profile 'camw' as defined in clause 7.3.2.3. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.3.2.4. + +## 7.4 EVS Media Profile + +### 7.4.1 Mapping to ISO BMFF + +If media is provided following the operation point **EVS** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'sevs' as defined in TS 26.244 [29]. + +### 7.4.2 Media Profile Definition + +#### 7.4.2.1 CMAF Track Definition + +If media is provided following the operation point **EVS** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'sevs' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10. + +#### 7.4.2.2 CMAF Switching Set and Media Profile Definition + +If media is provided following the operation point **EVS** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'sevs' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF EVS media profile 'cevs'. + +#### 7.4.2.3 Mapping to DASH Adaptation Set + +If media is provided following the operation point **EVS** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set: + +- @codecs is set to 'sevs' +- @mimeType is set to be compatible with "audio/mp4 profiles='cevs'" +- @audioSamplingRate is set to one of the following: '8000', '16000', '24000', '32000' + +If the Adaptation Set conforms to the constraints for the **EVS** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:evs". + +#### 7.4.2.4 Playback Requirements + +For a receiver supporting the EVS media profile the following applies: + +- It shall support the receiver requirements as documented in clause 6.2.4.2 for any CMAF Track conforming to the CMAF EVS media profile 'cevs' as defined in clause 7.4.2.2. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF EVS media profile 'cevs' as defined in clause 7.4.2.2, namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF EVS media profile 'cevs' as defined in clause 7.2.2.2, namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + +- 8.12 Playback of Encrypted Content + +#### 7.4.2.5 Content Generation Requirements + +For a transmitter supporting the EVS media profile the following applies: + +- It shall support all media encoding capabilities for EVS as defined in clause 5.3. +- It shall support the sender requirements for EVS as defined in clause 6.2.4.3. +- It shall support the generation of a CMAF Track as defined in clause 7.4.2.1 that conforms to the CMAF Media Profile 'cevs' as defined in clause 7.4.2.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.4.2.4. + +## 7.5 void + +## 7.6 eAAC+ stereo Media Profile + +### 7.6.1 Void + +### 7.6.2 Media Profile Definition + +#### 7.6.2.1 CMAF Track Definition + +If media is provided following the operation point **eAAC+ stereo** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'mp4a' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7, the general audio track constraints defined in ISO/IEC 23000-19 [30], clause 10 as well as AAC core constraints in clause 10 of ISO/IEC 23000-19 [30]. + +NOTE: A CMAF Track conforming to eAAC+ stereo media profile also conforms to the xHE-AAC Media Profile as defined in clause 7.8. Consequently, such CMAF Track can also be played back by receivers conforming to the xHE-AAC Media Profile. + +#### 7.6.2.2 CMAF Switching Set and Media Profile Definition + +If media is provided following the operation point **eAAC+ stereo** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'mp4a' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7, the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10 as well as the AAC core Switching Set constraints in clause 10 of ISO/IEC 23000-19 [30]. A CMAF Switching Set following these requirements is defined as the CMAF eAAC+ stereo media profile 'ceac'. + +#### 7.6.2.3 Mapping to DASH Adaptation Set + +If media is provided following the operation point **eAAC+ stereo** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set: + +- @codecs is set to 'mp4a' +- @mimeType is set to be compatible with "audio/mp4 profiles='ceac'" +- @audioSamplingRate is set to '32000', '44100', or '48000' + +If the Adaptation Set conforms to the constraints for the **eAAC+ stereo** Operation Point as defined in this clause, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:eAAC+ ". + +NOTE: A DASH Adaptation Set conforming to eAAC+ stereo media profile conforms to the xHE-AAC DASH Adaptation Set as defined in clause 7.8. Hence, such DASH Adaptation Set can also be played back by receivers conforming to the xHE-AAC media profile. + +#### 7.6.2.4 Playback Requirements + +For a receiver supporting the **eAAC+ stereo** media profile the following applies: + +- It shall support the receiver requirements as documented in clause 6.3.2.2 for any CMAF Track conforming to the CMAF eAAC+ stereo media profile 'ceac' as defined in clause 7.6.2.2. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF eAAC+ stereo media profile 'ceac' as defined in clause 7.6.2.2, namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF eAAC+ stereo media profile 'ceac' as defined in clause 7.6.2.2, namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +#### 7.6.2.5 Content Generation Requirements + +For a transmitter supporting the **eAAC+ stereo** media profile the following applies: + +- It shall support all media encoding capabilities for eAAC+ stereo as defined in clause 5.3. +- It shall support the sender requirements for eAAC+ stereo as defined in clause 6.3.2.3. +- It shall support the generation of a CMAF Track as defined in clause 7.6.2.2 that conforms to the CMAF Media Profile 'ceac' as defined in clause 7.6.2.3. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.6.2.4. + +## 7.7 AMR-WB+ Media Profiles + +### 7.7.1 Mapping to ISO BMFF + +If media is provided following the operation point **AMR-WB+** and is encapsulated in the ISO BMFF, then the file format track shall conform to the requirements of the codec entry 'sawp' as defined in TS 26.244 [29]. + +### 7.7.2 Media Profile Definition + +#### 7.7.2.1 CMAF Track Definition + +If media is provided following the operation point **AMR-WB+** and is encapsulated in a CMAF track, then the CMAF track shall conform to the requirements of the codec entry 'sawp' as defined in TS 26.244 [29], the general CMAF Track constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general audio track constraints defined in ISO/IEC 23000-19, clause 10. + +#### 7.7.2.2 CMAF Switching Set and Media Profile Definition + +If media is provided following the operation point **AMR-WB+** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the requirements of the codec entry 'sawp' as defined in TS 26.244 [29], the general CMAF Switching Set constraints in ISO/IEC 23000-19 [30], clause 7 as well as the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19 [30], clause 10. A CMAF Switching Set following these requirements is defined as the CMAF AMR-WB+ media profile 'camp'. + +#### 7.7.2.3 Mapping to DASH Adaptation Set + +If media is provided following the operation point **AMR-WB+** and is provided in a DASH Media Presentation in an Adaptation Set, then the Adaptation Set shall conform to the DASH profile for CMAF as defined in ISO/IEC 23009-1 [31]. The following parameters shall be present on Adaptation Set level and set: + +- @codecs is set to 'sawp' +- @mimeType is set to be compatible with "audio/mp4 profiles='camp'" +- @audioSamplingRate is set to any of the following values: '8000', '16000', '32000', or '38400' + +If the Adaptation Set conforms to the constraints for the **AMR-WB+** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:amr-wb+". + +#### 7.7.2.4 Playback Requirements + +For a receiver supporting the AMR-WB+ media profile the following applies: + +- It shall support the receiver requirements as documented in clause 6.3.2.2 for any CMAF Track conforming to the CMAF AMR-WB+ stereo media profile 'camp' as defined in clause 7.7.2.2. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB+ media profile 'camp' as defined in clause 7.7.2.2, namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF AMR-WB media profile 'camp' as defined in clause 7.7.2.2, namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + +- 8.12 Playback of Encrypted Content + +#### 7.7.2.5 Content Generation Requirements + +For a transmitter supporting the AMR-WB+ media profile the following applies: + +- It shall support all media encoding capabilities for AMR-WB+ stereo as defined in clause 5.3. +- It shall support the sender requirements for AMR-WB+ as defined in clause 6.3.3.3. +- It shall support the generation of a CMAF Track as defined in clause 7.7.2.2 that conforms to the CMAF Media Profile 'cawp' as defined in clause 7.7.2.3. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.7.2.4. + +## 7.8 xHE-AAC Media Profile + +### 7.8.1 CMAF Track Definition + +If media is provided following the operation point **xHE-AAC stereo** and is encapsulated in a CMAF track, then the CMAF track shall conform to the general CMAF Track constraints in ISO/IEC 23000-19:2023 [30], clause 7, the general audio track constraints defined in ISO/IEC 23000-19:2023 [30], clause 10, as well as MPEG-D USAC track format constraints defined in ISO/IEC 23000-19:2023 [30], Annex K. + +### 7.8.2 CMAF Switching Set and Media Profile Definition + +If media is provided following the operation point **xHE-AAC stereo** and is provided in a CMAF Switching Set, then every CMAF track in the CMAF Switching Set shall conform to the general CMAF Track constraints in ISO/IEC 23000-19:2023 [30], clause 7, the general CMAF audio track Switching Set constraints defined in ISO/IEC 23000-19:2023 [30], clause 10, as well as the MPEG-D USAC CMAF media profile constraints defined in ISO/IEC 23000-19:2023 [30], Annex K. + +A CMAF Switching Set following these requirements is defined as the CMAF USAC stereo media profile 'casu'. + +### 7.8.3 Mapping to DASH Adaptation Set + +If media is provided following the operation point **xHE-AAC stereo** and is provided in a DASH Media Presentation in an Adaptation Set, then the following requirements apply: + +- Content representations shall comply with the USAC stereo CMAF media profile 'casu', as defined in ISO/IEC 23000-19:2023 [30]. +- Content representations shall comply with the DASH Profile for CMAF content as defined in ISO/IEC 23009-1:2022 [31] +- If the **ChannelConfiguration** parameter is present in the Movie header, then the identical channel configuration shall be signaled by means of the AudioChannelConfiguration element in the MPD, according to the values specified in ISO/IEC 23000-19:2023 [30] Table K.2. +- @audioSamplingRate is set to '32000', '44100', or '48000' + +If the Adaptation Set conforms to the constraints for the **xHE-AAC stereo** Operation Point as defined in this clause, then the @profiles parameter in the Adaptation Set may signal conformance to this Media Profile by using "urn:3GPP:audio:mp:xHE-AAC". + +### 7.8.4 Playback Requirements + +For a receiver supporting the **xHE-AAC** media profile the following applies: + +- It shall support the receiver requirements as documented in clause 6.3.4.2 for any CMAF Track conforming to the CMAF USAC stereo media profile 'casu' as defined in clause 7.8.2. +- It should support the audio related playback requirements as documented in clause 8 of CTA-WAVE 5003 [32] for any content conforming to a CMAF Switching Set according to CMAF USAC stereo media profile 'casu' as defined in clause 7.8.2. + +### 7.8.5 Content Generation Requirements + +For a transmitter supporting the **xHE-AAC** media profile the following applies: + +- It shall support all media encoding capabilities for xHE-AAC stereo as defined in clause 5.3. +- It shall support the sender requirements for xHE-AAC stereo as defined in clause 6.3.4.3. +- It shall support the generation of a CMAF Track as defined in clause 7.8.1 that conforms to the CMAF Media Profile 'casu' as defined in clause 7.8.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 7.8.2. + +# Annex A (informative): Registration Information + +## A.1 3GPP Registered URIs + +The clause documents the registered URIs in the present document following the process in + +Table A-1 lists all registered URN values as well as: + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +**Table A-1: 3GPP Registered URNs** + +| URN | Description | Reference | Contact | Remarks | +|---------------------------|----------------------------|---------------------------|---------------------------------------------|---------| +| urn:3GPP:audio:mp:amr | AMR Media Profile | TS 26.117, clause 7.2.2.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:audio:mp:amr-wb | AMR-WB Media Profile | TS 26.117, clause 7.3.2.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:audio:mp:evs | EVS Media Profile | TS 26.117, clause 7.4.2.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:audio:mp:eAAC+ | eAAC+ stereo Media Profile | TS 26.117, clause 7.6.2.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:audio:mp:amr-wb+ | AMR-WB+ Media Profile | TS 26.117, clause 7.7.2.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:audio:mp:xHE-AAC | xHE-AAC Media Profile | TS 26.117, clause 7.8.3 | Frédéric Gabin
frederic.gabin@dolby.com | none | + +# Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|----------|-----|-----|----------------------------------------------------------|--|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2019-12 | SA#86 | SP-190990 | | | | Presented to TSG SA#86 (for information) | | 1.0.0 | +| 2020-01 | SA4#107 | S4-200245 | | | | Version agreed by TSG SA WG 4 to be sent for SA approval | | 1.1.0 | +| 2020-03 | SA#87-e | SP-200049 | | | | Presented to TSG SA#87-e (for approval) | | 2.0.0 | +| 2020-03 | SA#87-e | SP-200049 | | | | Approved by TSG SA#87-e | | 16.0.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | | 17.0.0 | +| 2023-03 | SA#99- | SP-230251 | 000
1 | 4 | B | Introduction of xHE-AAC stereo audio operation point | | 18.0.0 | +| 2023-06 | SA#100 | SP-230552 | 000
2 | - | F | Corrections to references | | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26118/0adcd19063a66145a465add40bf956e6_img.jpg b/marked/Rel-18/26_series/26118/0adcd19063a66145a465add40bf956e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceb160f7e19e83641d0de154ea888beaf1a814bd --- /dev/null +++ b/marked/Rel-18/26_series/26118/0adcd19063a66145a465add40bf956e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39e4696db538c359185fc6a37ce9f0dd54263c74cc14a84419b6bf1603bfe4d4 +size 47723 diff --git a/marked/Rel-18/26_series/26118/22529ce6e2914d705243ba1bf43be65d_img.jpg b/marked/Rel-18/26_series/26118/22529ce6e2914d705243ba1bf43be65d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab3f3651210eb185dd8f37056a2c49487bbd9c48 --- /dev/null +++ b/marked/Rel-18/26_series/26118/22529ce6e2914d705243ba1bf43be65d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4adcdd72832322a6d8b93a81f1107f59870180d81d17784d34ac49e6fd0adb75 +size 25009 diff --git a/marked/Rel-18/26_series/26118/239c9d313ad906eda294af980e34ef48_img.jpg b/marked/Rel-18/26_series/26118/239c9d313ad906eda294af980e34ef48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18f18795127ab9ae1d2ffd2cbe7ed07b02b6998e --- /dev/null +++ b/marked/Rel-18/26_series/26118/239c9d313ad906eda294af980e34ef48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10f46036933bc6e45c4a0522a3e46133868ac526cfcdd2ef091e3aaf86dfe38d +size 39424 diff --git a/marked/Rel-18/26_series/26118/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-18/26_series/26118/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b98d46fd923fb14fd5ae141f289f47a69edd31e4 --- /dev/null +++ b/marked/Rel-18/26_series/26118/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49c74d6de049605b36800663b27ef97aec24018acbc8194f7e8e95cd0abeacf5 +size 76992 diff --git a/marked/Rel-18/26_series/26118/34f46103a0c07981b0b51490ea639e25_img.jpg b/marked/Rel-18/26_series/26118/34f46103a0c07981b0b51490ea639e25_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e37c9d6fdb27897258c796f5123376b1d923d2b0 --- /dev/null +++ b/marked/Rel-18/26_series/26118/34f46103a0c07981b0b51490ea639e25_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:163de854cc0dca7fa1a28f9c8ae19a601044bbf64cc1ab3a38afc62e456b9d85 +size 84992 diff --git a/marked/Rel-18/26_series/26118/4224f170b677d60f6f86ce95d8dc725a_img.jpg b/marked/Rel-18/26_series/26118/4224f170b677d60f6f86ce95d8dc725a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5382ce935f69d589c30054abd310e7be8d05564a --- /dev/null +++ b/marked/Rel-18/26_series/26118/4224f170b677d60f6f86ce95d8dc725a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c271a12276b782c50c070e437066b2542cf33a16c1e93a4c2f57a24cc42b993 +size 31791 diff --git a/marked/Rel-18/26_series/26118/4d2624b1b2871a23382b647cd71e1c1c_img.jpg b/marked/Rel-18/26_series/26118/4d2624b1b2871a23382b647cd71e1c1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f68cf6538b59ff75bfb9b37ea6d2bedd9cdf258 --- /dev/null +++ b/marked/Rel-18/26_series/26118/4d2624b1b2871a23382b647cd71e1c1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e65788bf43ceb7dc730aa5d9521e4e6d133de3a13acda48e2410c212ee263f7 +size 25485 diff --git a/marked/Rel-18/26_series/26118/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg b/marked/Rel-18/26_series/26118/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08bbd11b6099d36c8b292a2ebd69d3518974a17e --- /dev/null +++ b/marked/Rel-18/26_series/26118/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:821f33fe95c91fdfc48c287fda0c0823795471b2559bce2cf149e2a0a5e2116a +size 24628 diff --git a/marked/Rel-18/26_series/26118/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26118/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32a50cd156bbafbcc1b01e28038515c8c3ebd28e --- /dev/null +++ b/marked/Rel-18/26_series/26118/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62c58859959146e0c3890792a66ad1250404ceb28e5a89034376cb57ba79531e +size 10038 diff --git a/marked/Rel-18/26_series/26118/64544fbada794f3cdf4f78f5d83613e4_img.jpg b/marked/Rel-18/26_series/26118/64544fbada794f3cdf4f78f5d83613e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fc665c7df71ca1b09e2f7ed2ab6b61e9fdf7ae5 --- /dev/null +++ b/marked/Rel-18/26_series/26118/64544fbada794f3cdf4f78f5d83613e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afe1c0d89bc1b226df088f96a3b3136388601ad160814176d5a485a72d8ac759 +size 35570 diff --git a/marked/Rel-18/26_series/26118/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26118/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97db40d4bc6c9113fb5a5dcbba2bc6cecf99fa59 --- /dev/null +++ b/marked/Rel-18/26_series/26118/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9da2c4a4c2a5b8b3cf5cd93f94c9a6300737d632744507eeb87f1553d6d33f5f +size 5792 diff --git a/marked/Rel-18/26_series/26118/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Rel-18/26_series/26118/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b347e953f9b09046d057e9de3e3130a1390862fe --- /dev/null +++ b/marked/Rel-18/26_series/26118/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69d5a71dbe3d0e29e07a91721a29e210af639fb8fe6c748e8a9f4e0cc26c81d4 +size 102834 diff --git a/marked/Rel-18/26_series/26118/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-18/26_series/26118/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fa3b66957c5559df9e086813f937e7c061be31e --- /dev/null +++ b/marked/Rel-18/26_series/26118/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccc1f8489b73cc0a58771a1d28abe4ff9781918af683c9987ea71985197fe402 +size 52597 diff --git a/marked/Rel-18/26_series/26118/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-18/26_series/26118/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a8b3fe79ba677f7dcf3f4ec8f8cb7694f399602 --- /dev/null +++ b/marked/Rel-18/26_series/26118/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be6de593d38ad9a1d0bad1c65fa26c9bc8e6f9ea7bd5f44335dcb99a4bd5e1ef +size 57524 diff --git a/marked/Rel-18/26_series/26118/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-18/26_series/26118/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dffd8a121dc612094b1915eab01e62b3d4a9ce2 --- /dev/null +++ b/marked/Rel-18/26_series/26118/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:076598af0e6e2671fa71161c55dc21eaadd29907267c181fe2f1db651edc7966 +size 28895 diff --git a/marked/Rel-18/26_series/26118/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/26_series/26118/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbcc15cda62f6ca804207e5046ec5bb1800ae58a --- /dev/null +++ b/marked/Rel-18/26_series/26118/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb72810ae63e21da2d8f14a5f163bb7bdcb45c566c677396997fe99961a0edae +size 51258 diff --git a/marked/Rel-18/26_series/26118/96c8d8b0159c47a7478ada46d781060b_img.jpg b/marked/Rel-18/26_series/26118/96c8d8b0159c47a7478ada46d781060b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..399223fba99b589e8438fbe25778862e886e8723 --- /dev/null +++ b/marked/Rel-18/26_series/26118/96c8d8b0159c47a7478ada46d781060b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9edf22dc020455e4bf9f11acb55331320293b6e57abf5c05130faeea5d6f3174 +size 33847 diff --git a/marked/Rel-18/26_series/26118/a0b72ad654428ce2b44766f24928643e_img.jpg b/marked/Rel-18/26_series/26118/a0b72ad654428ce2b44766f24928643e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55a02b082c7d85b173d109c5271b5dcf46545876 --- /dev/null +++ b/marked/Rel-18/26_series/26118/a0b72ad654428ce2b44766f24928643e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:414daed33bb36f0eefba1acbc12a0f399d8ec644b1698e316c30ac43a2a54c7e +size 82918 diff --git a/marked/Rel-18/26_series/26118/a1d3651b1300f3670e3a9547bafc4db6_img.jpg b/marked/Rel-18/26_series/26118/a1d3651b1300f3670e3a9547bafc4db6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c607de240be169b0e7afc5c795a53202970ed2c5 --- /dev/null +++ b/marked/Rel-18/26_series/26118/a1d3651b1300f3670e3a9547bafc4db6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c1488171c6637f2b343d80df8d9157061ef9ce4e3650f9e62f40e03eea1efb6 +size 36756 diff --git a/marked/Rel-18/26_series/26118/bc6f20871b4f01c61470306c304fc9fe_img.jpg b/marked/Rel-18/26_series/26118/bc6f20871b4f01c61470306c304fc9fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca136fc5b85d093cee0718d6983ed5169e3f555e --- /dev/null +++ b/marked/Rel-18/26_series/26118/bc6f20871b4f01c61470306c304fc9fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa6500c5144580377da10c69872f597d53a9fba74ec49ccbd8ee8ced8bc7b85b +size 37414 diff --git a/marked/Rel-18/26_series/26118/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/marked/Rel-18/26_series/26118/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0988b1b54ccaaeee18d6ab0dc63729402b532a9e --- /dev/null +++ b/marked/Rel-18/26_series/26118/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c8fdcfc63a5789dea1cabb7f44cf7901559b0411aa72a7666c3d1b8fd5330d0 +size 53638 diff --git a/marked/Rel-18/26_series/26118/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/marked/Rel-18/26_series/26118/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef77473f0ee1becb74332dad3f8b654f07b90563 --- /dev/null +++ b/marked/Rel-18/26_series/26118/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c56f6b81f86fb1e934290b246d75ae648bc9e32307264d6210c1d1d5f051ca50 +size 69827 diff --git a/marked/Rel-18/26_series/26118/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-18/26_series/26118/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5403fd1f9c62e8bcd10ba2b01f32ef927a17bcaf --- /dev/null +++ b/marked/Rel-18/26_series/26118/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8911ce82c6e21dbc45fc7c0e1eeb033f103b5fad99c4537fe6aa2a94be68722e +size 26728 diff --git a/marked/Rel-18/26_series/26118/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-18/26_series/26118/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..299bb6e12630fce60c5ef9009cd7496d2c9803aa --- /dev/null +++ b/marked/Rel-18/26_series/26118/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:893a8cabe4995e2c2fcd4487ccdf60316dfb5082b01a92baa6628108c0fcdb0d +size 36777 diff --git a/marked/Rel-18/26_series/26118/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-18/26_series/26118/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..210f604f5ccd8e0ea254284d96cdf8e364d3d53c --- /dev/null +++ b/marked/Rel-18/26_series/26118/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dc3c491e0146b89821fa4ffc98246f9cf6e71685d7cf8a69d760fd6f34b6d70 +size 29048 diff --git a/marked/Rel-18/26_series/26118/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg b/marked/Rel-18/26_series/26118/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45890e73f0f6438f88eaf94024ae914cb7e5e22c --- /dev/null +++ b/marked/Rel-18/26_series/26118/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bf98166ae5cfa111bbcbfa7f47651591ed4fd86c6f21b4753f8c277d0013d23 +size 22020 diff --git a/marked/Rel-18/26_series/26118/raw.md b/marked/Rel-18/26_series/26118/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..548b096a3977f35304a3dce2dc6e1a24361995f6 --- /dev/null +++ b/marked/Rel-18/26_series/26118/raw.md @@ -0,0 +1,3170 @@ + + +# 3GPP TS 26.118 V18.0.0 (2023-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Virtual Reality (VR) profiles for streaming applications (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------|----| +| Foreword ..... | 7 | +| Introduction ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 Architectures and Interfaces for Virtual Reality ..... | 11 | +| 4.1 Definitions and Reference Systems..... | 11 | +| 4.1.1 Overview ..... | 11 | +| 4.1.2 3GPP 3DOF Coordinate System ..... | 12 | +| 4.1.3 Video Signal Representation ..... | 14 | +| 4.1.4 Audio Signal Representation..... | 15 | +| 4.2 End-to-end Architecture ..... | 16 | +| 4.3 Client Reference Architecture..... | 17 | +| 4.4 Rendering Schemes, Operation Points and Media Profiles..... | 19 | +| 4.5 Audio Rendering ..... | 21 | +| 4.5.1 Audio Renderer Definitions ..... | 21 | +| 4.5.1.1 Reference Renderer..... | 21 | +| 4.5.1.2 Common Informative Binaural Renderer (CIBR) ..... | 21 | +| 4.5.1.3 External Renderer ..... | 22 | +| 4.5.1.4 Common Renderer API ..... | 22 | +| 4.5.1.5 External Renderer API..... | 22 | +| 4.5.1.6 Rendering Test..... | 23 | +| 5 Video..... | 23 | +| 5.1 Video Operation Points ..... | 23 | +| 5.1.1 Definition of Operation Point..... | 23 | +| 5.1.2 Parameters of Visual Operation Point ..... | 24 | +| 5.1.3 Operation Point Summary ..... | 24 | +| 5.1.4 Basic H.264/AVC..... | 25 | +| 5.1.4.1 General..... | 25 | +| 5.1.4.2 Profile and level ..... | 25 | +| 5.1.4.3 Aspect Ratios and Spatial resolutions..... | 25 | +| 5.1.4.4 Colour information ..... | 26 | +| 5.1.4.5 Frame rates..... | 26 | +| 5.1.4.6 Random access point ..... | 26 | +| 5.1.4.7 Sequence parameter set..... | 26 | +| 5.1.4.8 Video usability information ..... | 27 | +| 5.1.4.9 Omni-directional Projection Format..... | 27 | +| 5.1.4.10 Restricted Coverage ..... | 27 | +| 5.1.4.11 Other VR Metadata..... | 27 | +| 5.1.4.12 Receiver Compatibility ..... | 27 | +| 5.1.5 Main H.265/HEVC..... | 28 | +| 5.1.5.1 General..... | 28 | +| 5.1.5.2 Profile and level ..... | 28 | +| 5.1.5.3 Bit depth..... | 28 | +| 5.1.5.4 Spatial Resolutions ..... | 28 | +| 5.1.5.5 Colour information and Transfer Characteristics ..... | 29 | +| 5.1.5.6 Frame rates..... | 29 | +| 5.1.5.7 Random access point ..... | 30 | +| 5.1.5.8 Video and Sequence Parameter Sets..... | 30 | +| 5.1.5.9 Video usability information ..... | 30 | + +| | | | +|-----------|----------------------------------------------------------------|----| +| 5.1.5.10 | Omni-directional Projection Formats ..... | 30 | +| 5.1.5.11 | Restricted Coverage ..... | 30 | +| 5.1.5.12 | Viewport-Optimized Content ..... | 31 | +| 5.1.5.13 | Frame packing arrangement..... | 31 | +| 5.1.5.14 | Other VR Metadata ..... | 31 | +| 5.1.5.15 | Receiver Compatibility ..... | 31 | +| 5.1.6 | Flexible H.265/HEVC ..... | 32 | +| 5.1.6.1 | General ..... | 32 | +| 5.1.6.2 | Profile and level ..... | 32 | +| 5.1.6.3 | Bit depth..... | 32 | +| 5.1.6.4 | Spatial Resolutions ..... | 33 | +| 5.1.6.5 | Colour information and Transfer Characteristics ..... | 33 | +| 5.1.6.6 | Frame rates..... | 34 | +| 5.1.6.7 | Random access point ..... | 34 | +| 5.1.6.8 | Video and Sequence Parameter Sets..... | 35 | +| 5.1.6.9 | Video usability information ..... | 35 | +| 5.1.6.10 | Omni-directional Projection Formats ..... | 35 | +| 5.1.6.11 | Restricted Coverage ..... | 35 | +| 5.1.6.12 | Viewport-Optimized Content ..... | 36 | +| 5.1.6.13 | Frame packing arrangement..... | 36 | +| 5.1.6.14 | Other VR Metadata ..... | 36 | +| 5.1.6.15 | Receiver Compatibility ..... | 36 | +| 5.1.7 | Main 8K H.265/HEVC ..... | 37 | +| 5.1.7.1 | General ..... | 37 | +| 5.1.7.2 | Profile and level ..... | 37 | +| 5.1.7.3 | Bit depth..... | 37 | +| 5.1.7.4 | Spatial Resolutions ..... | 38 | +| 5.1.7.5 | Colour information and Transfer Characteristics ..... | 38 | +| 5.1.7.6 | Frame rates..... | 39 | +| 5.1.7.7 | Random access point ..... | 39 | +| 5.1.7.8 | Video and Sequence Parameter Sets..... | 39 | +| 5.1.7.9 | Video usability information ..... | 39 | +| 5.1.7.10 | Omni-directional Projection Formats ..... | 39 | +| 5.1.7.11 | Restricted Coverage ..... | 40 | +| 5.1.7.12 | Frame packing arrangement..... | 40 | +| 5.1.7.13 | Other VR Metadata ..... | 40 | +| 5.1.7.14 | Receiver Compatibility ..... | 40 | +| 5.2 | Video Media Profiles ..... | 40 | +| 5.2.1 | Introduction and Overview ..... | 40 | +| 5.2.2 | Basic Video Media Profile ..... | 41 | +| 5.2.2.1 | Overview..... | 41 | +| 5.2.2.2 | File Format Signaling and Encapsulation ..... | 41 | +| 5.2.2.3 | DASH Integration ..... | 42 | +| 5.2.2.3.1 | Definition ..... | 42 | +| 5.2.2.3.2 | Additional Restrictions for DASH Representations..... | 42 | +| 5.2.2.3.3 | DASH Adaptation Set Constraints..... | 43 | +| 5.2.3 | Main Video Media Profile ..... | 44 | +| 5.2.3.1 | Overview..... | 44 | +| 5.2.3.2 | File Format Signaling and Encapsulation ..... | 44 | +| 5.2.3.3 | DASH Integration ..... | 46 | +| 5.2.3.3.1 | Definition ..... | 46 | +| 5.2.3.3.2 | Additional Restrictions for DASH Representations..... | 46 | +| 5.2.3.3.3 | DASH Adaptation Set Constraints..... | 46 | +| 5.2.3.3.4 | Adaptation Set Ensembles for Viewport-Optimized offering ..... | 48 | +| 5.2.4 | Advanced Video Media Profile ..... | 49 | +| 5.2.4.1 | Overview..... | 49 | +| 5.2.4.2 | File Format Signaling and Encapsulation ..... | 49 | +| 5.2.4.3 | DASH Integration ..... | 51 | +| 5.2.4.3.1 | Definition ..... | 51 | +| 5.2.4.3.2 | Additional Restrictions for DASH Representations..... | 51 | +| 5.2.4.3.3 | DASH Adaptation Set Constraints..... | 52 | +| 5.2.4.3.4 | Adaptation Set Constraints for Viewport Selection ..... | 54 | + +| | | | +|------------------------------------------------------------------|-------------------------------------------------------------------|-----------| +| 6 | Audio..... | 55 | +| 6.1 | Audio Operation Points..... | 55 | +| 6.1.1 | Definition of Operation Point..... | 55 | +| 6.1.2 | Parameters of Audio Operation Point..... | 55 | +| 6.1.3 | Summary of Audio Operation Points ..... | 55 | +| 6.1.4 | 3GPP MPEG-H Audio Operation Point..... | 56 | +| 6.1.4.1 | Overview..... | 56 | +| 6.1.4.2 | Bitstream requirements..... | 56 | +| 6.1.4.3 | Receiver requirements ..... | 56 | +| 6.1.4.3.1 | General ..... | 56 | +| 6.1.4.3.2 | Decoding process ..... | 56 | +| 6.1.4.3.3 | Random Access..... | 57 | +| 6.1.4.3.4 | Configuration change ..... | 57 | +| 6.1.4.3.5 | MPEG-H Multi-stream Audio..... | 58 | +| 6.1.4.3.6 | Rendering requirements ..... | 58 | +| 6.2 | Audio Media Profiles ..... | 60 | +| 6.2.1 | Introduction and Overview ..... | 60 | +| 6.2.2 | OMAF 3D Audio Baseline Media Profile..... | 60 | +| 6.2.2.1 | Overview..... | 60 | +| 6.2.2.2 | File Format Signaling and Encapsulation..... | 60 | +| 6.2.2.2.1 | General ..... | 60 | +| 6.2.2.2.2 | Configuration change constraints..... | 60 | +| 6.2.2.3 | Multi-stream constraints ..... | 61 | +| 6.2.2.3a | Additional Restrictions for DASH Representations ..... | 61 | +| 6.2.2.4 | DASH Adaptation Set Constraints ..... | 61 | +| 6.2.2.4.1 | General ..... | 61 | +| 6.2.2.4.2 | DASH Adaptive Bitrate Switching ..... | 61 | +| 7 | Metadata..... | 61 | +| 7.1 | Presentation without Pose Information to 2D Screens..... | 61 | +| 8 | VR Presentation ..... | 62 | +| 8.1 | Definition ..... | 62 | +| 8.2 | 3GPP VR File..... | 62 | +| 8.3 | 3GPP VR DASH Media Presentation ..... | 62 | +| 9 | VR Metrics..... | 62 | +| 9.1 | General ..... | 62 | +| 9.2 | VR Client Reference Architecture ..... | 63 | +| 9.2.1 | Architecture ..... | 63 | +| 9.2.2 | Observation Point 1 ..... | 63 | +| 9.2.3 | Observation Point 2 ..... | 64 | +| 9.2.4 | Observation Point 3 ..... | 64 | +| 9.2.5 | Observation Point 4 ..... | 64 | +| 9.2.6 | Observation Point 5 ..... | 65 | +| 9.3 | Metrics Definitions..... | 65 | +| 9.3.1 | General ..... | 65 | +| 9.3.2 | Comparable quality viewport switching latency ..... | 65 | +| 9.3.3 | Rendered viewports..... | 67 | +| 9.3.4 | VR Device information ..... | 68 | +| 9.4 | Metrics Configuration and Reporting ..... | 69 | +| 9.4.1 | Configuration..... | 69 | +| 9.4.2 | Reporting ..... | 69 | +| 9.4.3 | Reporting Format..... | 69 | +| Annex A (informative): Content Generation Guidelines..... | | 72 | +| A.1 | Introduction..... | 72 | +| A.2 | Video..... | 72 | +| A.2.1 | Overview ..... | 72 | +| A.2.2 | Decoded Texture Signal Constraints..... | 72 | +| A.2.2.1 | General ..... | 72 | +| A.2.2.2 | Constraints for Main and Flexible H.265/HEVC Operation Point..... | 72 | + +| | | | +|-------------------------------|---------------------------------------------------------|-----------| +| A.2.2.2a | Constraints for Main 8K H.265/HEVC Operation Point..... | 73 | +| A.2.3 | Conversion of ERP Signals to CMP ..... | 74 | +| A.2.3.1 | General ..... | 74 | +| A.2.3.2 | Equirectangular Projection (ERP) ..... | 75 | +| A.2.3.3 | Cubemap Projection (CMP) ..... | 75 | +| A.2.3.4 | Conversion between two projection formats..... | 76 | +| Annex B (informative): | Example External Binaural Renderer..... | 78 | +| B.1 | General ..... | 78 | +| B.2 | Interfaces..... | 78 | +| B.2.1 | Interface for Audio Data and Metadata..... | 78 | +| B.2.2 | Head Tracking Interface..... | 79 | +| B.2.3 | Interface for Head-Related Impulse Responses ..... | 79 | +| B.3 | Preprocessing ..... | 79 | +| B.3.1 | Channel Content..... | 79 | +| B.3.2 | Object Content..... | 79 | +| B.3.3 | HOA Content..... | 79 | +| B.3.4 | Non-diegetic Content ..... | 79 | +| B.4 | Scene Displacement Processing..... | 80 | +| B.4.1 | General ..... | 80 | +| B.4.2 | Applying Scene Displacement Information ..... | 80 | +| B.5 | Headphone Output Signal Computation ..... | 80 | +| B.5.1 | General ..... | 80 | +| B.5.2 | HRIR Selection ..... | 80 | +| B.5.3 | Initialization ..... | 80 | +| B.5.4 | Convolution and Crossfade ..... | 81 | +| B.5.5 | Binaural Downmix ..... | 81 | +| B.5.6 | Complexity ..... | 82 | +| B.5.7 | Motion Latency ..... | 82 | +| Annex C (informative): | Registration Information ..... | 83 | +| C.1 | 3GPP Registered URIs..... | 83 | +| Annex D (informative): | VR metrics calculation examples ..... | 84 | +| D.1 | Comparable quality viewport switching latency..... | 84 | +| D.2 | Rendered viewports..... | 86 | +| Annex E (informative): | Change history ..... | 88 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +The present document provides technologies for interoperable Virtual Reality services with focus on streaming and consumption. + +Virtual Reality (VR) is the ability to be virtually present in a space created by the rendering of natural and/or synthetic image and sound correlated by the movements of the immersed user allowing interacting with that world. + +Suitable media formats for providing immersive experiences are specified to enable Virtual Reality Services in the context of 3GPP bearer and user services. + +# 1 Scope + +The present document defines interoperable formats for Virtual Reality for streaming services. Specifically, the present document defines operation points, media profiles and presentation profiles for Virtual Reality. The present document builds on the findings and conclusions in TR 26.918 [2]. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 26.918: "Virtual Reality (VR) media services over 3GPP". +- [3] Recommendation ITU-R BT.709-6 (06/2015): "Parameter values for the HDTV standards for production and international programme exchange". +- [4] Recommendation ITU-R BT.2020-2 (10/2015): "Parameter values for ultra-high definition television systems for production and international programme exchange". +- [5] Recommendation ITU-T H.264 (04/2017): "Advanced video coding for generic audiovisual services" | ISO/IEC 14496-10:2014: "Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding". +- [6] Recommendation ITU-T H.265 (02/2018): "High efficiency video coding" | ISO/IEC 23008-2:2018: "High Efficiency Coding and Media Delivery in Heterogeneous Environments – Part 2: High Efficiency Video Coding". +- [7] void. +- [8] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [9] ISO/IEC 14496-15: "Information technology - Coding of audio-visual objects - Part 15: Carriage of network abstraction layer (NAL) unit structured video in ISO base media file format". +- [10] ISO/IEC 23001-8: "Information technology -- MPEG systems technologies -- Part 8: Coding-independent code points". +- [11] Recommendation ITU-R BT.2100-1: "Image parameter values for high dynamic range television for use in production and international programme exchange". +- [12] 3GPP TS 26.116: "Television (TV) over 3GPP services; Video profiles". +- [13] ISO/IEC 23090-2: "Coded representation of immersive media -- Part 2: Omnidirectional media format". +- [14] ISO/IEC DIS 23091-2: "Information technology -- Coding-independent code points -- Part 2: Video". +- [15] 3GPP TS 26.260: "Objective test methodologies for the evaluation of immersive audio systems". + +- [16] 3GPP TS 26.259: "Subjective test methodologies for the evaluation of immersive audio systems". +- [17] ISO/IEC 14496-12: "Information technology -- Coding of audio-visual objects -- Part 12: ISO base media file format". +- [18] ISO/IEC 23009-1: "Information technology -- Dynamic adaptive streaming over HTTP (DASH) -- Part 1: Media presentation description and segment formats". +- [19] ISO/IEC 23008-3:2015: "Information technology -- High efficiency coding and media delivery in heterogeneous environments - Part 3: 3D audio", ISO/IEC 23008-3:2015/Amd2:2016: "MPEG-H 3D Audio File Format Support ", ISO/IEC 23008-3:2015/Amd 3:2017: "MPEG-H 3D Audio Phase 2", ISO/IEC 23008-3:2015/Amd 5: "Audio metadata enhancements". +- [20] IETF RFC 6381: "The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types", R. Gellens, D. Singer, P. Frojdh, August 2011. +- [21] AES69-2015: "AES standard for file exchange - Spatial acoustic data file format", 2015. + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**bitstream:** a bitstream that conforms to a video encoding format and certain Operation Point. + +**field of view:** the extent of visible area expressed with vertical and horizontal angles, in degrees in the 3GPP 3DOF reference system. + +**operation point:** a collection of discrete combinations of different content formats including spatial and temporal resolutions, colour mapping, transfer functions, rendering metadata and the encoding format. + +**pose:** position derived by the head tracking sensor expressed by (azimuth; elevation; tilt angle). + +**receiver:** a receiver that can decode and render any bitstream that is conforming to a certain Operation Point. + +**viewport:** the part of the 3DOF content to render based on the pose and the field of view. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|----------------------------------------------| +| $\alpha$ | yaw of the 3GPP 3DOF coordinate system | +| $\beta$ | pitch of the 3GPP 3DOF coordinate system | +| $\gamma$ | roll of the 3GPP 3DOF coordinate system | +| $\phi$ | azimuth of the 3GPP 3DOF coordinate system | +| $\theta$ | elevation of the 3GPP 3DOF coordinate system | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|-----------------------------------| +| 3DOF | 3 Degrees of freedom | +| ACN | Ambisonics Channel Number | +| API | Application Programming Interface | +| AVC | Advanced Video Coding | +| BMFF | Base Media File Format | + +| | | +|-------|-----------------------------------------| +| BRIR | Binaural Room Impulse Response | +| CMP | Cube-Map Projection | +| CIBR | Common Informative Binaural Renderer | +| DASH | Dynamic Adaptive Streaming over HTTP | +| DRC | Dynamic Range Control | +| EOTF | Electro-Optical Transfer Function | +| ERP | EquiRectangular Projection | +| ESD | Equivalent Spatial Domain | +| FFT | Fast Fourier Transform | +| FIR | Finite Impulse Response | +| FOA | First Order Ambisonics | +| FOV | Field Of View | +| GPU | Graphics Processing Unit | +| HDR | High Dynamic Range | +| HDTV | High Definition TeleVision | +| HEVC | High Efficiency Video Coding | +| HMD | Head Mounted Display | +| HOA | High Order Ambisonics | +| HRD | Hypothetical Reference Decoder | +| HRIR | Head-Related Impulse Responses | +| HRTF | Head-Related Transfer Function | +| HTTP | HyperText Transfer Protocol | +| IFFT | Inverse FFT | +| IRFFT | Inverse RFFT | +| MAE | MPEG-H Audio Metadata information | +| MCC | Metrics Collection and Computation | +| MHAS | MPEG-H Audio Stream | +| MIME | Multipurpose Internet Mail Extensions | +| MPD | Media Presentation Description | +| MPEG | Moving Pictures Experts Group | +| NAL | Network Abstraction Layer | +| OMAF | Omnidirectional MediA Format | +| PCM | Pulse Code Modulation | +| RAP | Random Access Point | +| RFFT | Real FFT | +| RWP | Region-Wise Packing | +| SDR | Standard Dynamic Range | +| SEI | Supplemental Enhancement Information | +| SN3D | Schmidt semi-normalisation | +| SOFA | Spatially Oriented Format for Acoustics | +| SPS | Sequence Parameter Set | +| SRQR | Spherical Region-wise Quality Ranking | +| VCL | Video Coding Layer | +| VST | Virtual Studio Technology | +| VUI | Video Usability Information | +| VR | Virtual Reality | + +# --- 4 Architectures and Interfaces for Virtual Reality + +## 4.1 Definitions and Reference Systems + +### 4.1.1 Overview + +Virtual reality is a rendered version of a delivered visual and audio scene. The rendering is designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. + +Virtual reality usually, but not necessarily, assumes a user to wear a head mounted display (HMD), to completely replace the user's field of view with a simulated visual component, and to wear headphones, to provide the user with the accompanying audio as shown in Figure 4.1-1. + +![Figure 4.1-1: Reference System. A diagram showing a person wearing a head-mounted display (HMD) with three axes of rotation: X-axis (Roll γ), Y-axis (Pitch β), and Z-axis (Yaw α).](4d2624b1b2871a23382b647cd71e1c1c_img.jpg) + +A line drawing of a person's head and shoulders wearing a head-mounted display (HMD). Three dashed lines represent the X, Y, and Z axes originating from the center of the head. The Z-axis is vertical, with a curved arrow indicating rotation labeled 'Yaw α'. The X-axis is horizontal and points to the left, with a curved arrow indicating rotation labeled 'Roll γ'. The Y-axis points diagonally forward and to the right, with a curved arrow indicating rotation labeled 'Pitch β'. + +Figure 4.1-1: Reference System. A diagram showing a person wearing a head-mounted display (HMD) with three axes of rotation: X-axis (Roll γ), Y-axis (Pitch β), and Z-axis (Yaw α). + +**Figure 4.1-1: Reference System** + +Some form of head and motion tracking of the user in VR is usually also necessary to allow the simulated visual and audio components to be updated in order to ensure that, from the user's perspective, items and sound sources remain consistent with the user's movements. Sensors typically are able to track the user's pose in the reference system. Additional means to interact with the virtual reality simulation may be provided but are not strictly necessary. + +VR users are expected to be able to look around from a single observation point in 3D space defined by either a producer or the position of one or multiple capturing devices. When VR media including video and audio is consumed with a head-mounted display or a smartphone, only the area of the spherical video that corresponds to the user's viewport is rendered, as if the user were in the spot where the video and audio were captured. + +This ability to look around and listen from a *centre point* in 3D space is defined as 3 degrees of freedom (3DOF). According to the figure 4.1-1: + +- tilting side to side on the X-axis is referred to as *Rolling*, also expressed as $\gamma$ +- tilting forward and backward on the Y-axis is referred to as *Pitching*, also expressed as $\beta$ +- turning left and right on the Z-axis is referred to as *Yawing*, also expressed as $\alpha$ + +It is worth noting that this *centre point* is not necessarily static - it may be moving. Users or producers may also select from a few different observational points, but each observation point in 3D space only permits the user 3 degrees of freedom. For a full 3DOF VR experience, such video content may be combined with simultaneously captured audio, binaurally rendered with an appropriate Binaural Room Impulse Response (BRIR). The third relevant aspect is the interactivity: Only if the content is presented to the user in such a way that the movements are instantaneously reflected in the rendering, then the user will perceive a full immersive experience. For details on immersive rendering latencies, refer to TR 26.918 [2]. + +### 4.1.2 3GPP 3DOF Coordinate System + +The coordinate system is specified for defining the sphere coordinates azimuth ( $\phi$ ) and elevation ( $\theta$ ) for identifying a location of a point on the unit sphere, as well as the rotation angles yaw ( $\alpha\alpha$ ), pitch ( $\beta\beta$ ), and roll ( $\gamma\gamma$ ). The origin of the coordinate system is usually the same as the centre point of a device or rig used for audio or video acquisition as well as the position of the user's head in the 3D space in which the audio or video are rendered. Figure 4.1-2 specifies principal axes for the coordinate system. The X axis is equal to back-to-front axis, Y axis is equal to side-to-side (or lateral) axis, and Z axis is equal to vertical (or up) axis. These axis map to the reference system in Figure 4.1-1. + +![Figure 4.1-2: Coordinate system diagram showing a unit sphere with X, Y, and Z axes. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points towards the bottom-left. Azimuth (phi) is measured clockwise from the Z-axis in the XY-plane. Elevation (theta) is measured from the XY-plane towards the Z-axis. Rotation angles Yaw, Pitch, and Roll are indicated by curved arrows around the Z, Y, and X axes respectively.](eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg) + +Figure 4.1-2: Coordinate system diagram showing a unit sphere with X, Y, and Z axes. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points towards the bottom-left. Azimuth (phi) is measured clockwise from the Z-axis in the XY-plane. Elevation (theta) is measured from the XY-plane towards the Z-axis. Rotation angles Yaw, Pitch, and Roll are indicated by curved arrows around the Z, Y, and X axes respectively. + +Figure 4.1-2: Coordinate system + +Signals defined in the present document are represented in a spherical coordinate space in angular coordinates ( $\phi, \theta$ ) for use in omnidirectional video and 3D audio. The viewing and listing perspective are from the origin sensing/looking/hearing outward toward the inside of the sphere. Even though a spherical coordinate is generally represented by using radius, elevation, and azimuth, it assumes that a unit sphere is used for capturing and rendering of VR media. Thus, a location of a point on the unit sphere is identified by using the sphere coordinates azimuth ( $\phi$ ) and elevation ( $\theta$ ). The spherical coordinates are defined so that $\phi$ is the azimuth and $\theta$ is the elevation. As depicted in Figure 4.1-2, the coordinate axes are also used for defining the rotation angles yaw ( $\alpha\alpha$ ), pitch ( $\beta\beta$ ), and roll ( $\gamma\gamma$ ). The angles increase clockwise when looking from the origin towards the positive end of an axis. The value ranges of azimuth, yaw, and roll are all $-180.0$ , inclusive, to $180.0$ , exclusive, degrees. The value range of elevation and pitch are both $-90.0$ to $90.0$ , inclusive, degrees. + +Depending on the applications or implementations, not all angles may be necessary or available in the signal. The 360 video may have a restricted *coverage* as shown in Figure 4.1-3. When the video signal does not cover the full sphere, the coverage information is described by using following parameters: + +- *centre azimuth*: specifies the azimuth value of the centre point of sphere region covered by the signal. +- *centre elevation*: specifies the elevation value of the centre of sphere region. +- *azimuth range*: specifies the azimuth range through the centre point of the sphere region. +- *elevation range*: specifies the elevation range through the centre point of the sphere region. +- *tilt angle*: indicates the amount of tilt of a sphere region, measured as the amount of rotation of the sphere region along the axis originating from the origin passing through the centre point of the sphere region, where the angle value increases clockwise when looking from the origin towards the positive end of the axis. + +![Figure 4.1-3: A 3D sphere with a grid representing a spherical coordinate system. A shaded rectangular region represents the field of view. Labels include: theta = +90 degrees (+pi/2) at the top pole, theta = -90 degrees (-pi/2) at the bottom pole, phi = 0, theta = 0 at the center of the equator, and phi = phi (equator) along the equator. The center of the shaded region is marked with a crosshair and labeled 'omni_projection_yaw_center (phi)' and 'omni_projection_pitch_center (theta)'. The width and height of the shaded region are labeled 'l_viewWidth-1' and 'l_viewHeight-1'. Arrows indicate 'increasing phi' and 'increasing theta'.](a1d3651b1300f3670e3a9547bafc4db6_img.jpg) + +Figure 4.1-3: A 3D sphere with a grid representing a spherical coordinate system. A shaded rectangular region represents the field of view. Labels include: theta = +90 degrees (+pi/2) at the top pole, theta = -90 degrees (-pi/2) at the bottom pole, phi = 0, theta = 0 at the center of the equator, and phi = phi (equator) along the equator. The center of the shaded region is marked with a crosshair and labeled 'omni\_projection\_yaw\_center (phi)' and 'omni\_projection\_pitch\_center (theta)'. The width and height of the shaded region are labeled 'l\_viewWidth-1' and 'l\_viewHeight-1'. Arrows indicate 'increasing phi' and 'increasing theta'. + +**Figure 4.1-3: Restricted coverage of the sphere region covered by the cropped output picture with `omni_projection_{yaw | pitch | roll}_center` the center of the coverage region** + +For video, such a centre point may exist for each eye, referred to as *stereo* signal, and the video consists of three colour components, typically expressed by the luminance (Y) and two chrominance components (U and V). + +The coordinate systems for all media types are assumed to be aligned in 3GPP 3DOF coordinate system. Within this coordinate system, the *pose* is expressed by a triple of azimuth, elevation, and tilt angle characterizing the head position of a user consuming the audio-visual content. The pose is generally dynamic, and the information may be provided through sensors in a frequently sampled version. + +The *field of view (FoV)* of a rendering device is static and defined in two dimensions, the horizontal and vertical FoV, each in units of degrees in the angular coordinates $(\phi, \theta)$ . The pose together with the field of view of the device enables the system to generate the user viewport, i.e., the presented part of the content at a specific point in time. + +### 4.1.3 Video Signal Representation + +Commonly used video encoders cannot directly encode spherical videos, but only 2D textures. However, there is a significant benefit to reuse conventional 2D video encoders. Based on this, Figure 4.1-4 provides the basic video signal representation in the context of omnidirectional video in the context of the present document. By pre-processing, the spherical video is mapped to a 2D texture. The 2D texture is encoded with a regular 2D video encoder and the VR rendering metadata (i.e. the data describing the mapping from the spherical coordinate to the 2D texture) is encoded and provided along with the video bitstream, such that at the receiving end the inverse process can be applied to reconstruct the spherical video. + +![Figure 4.1-4: A flowchart illustrating the video signal representation process. It starts with a spherical coordinate system icon, followed by a 'Preprocessing Sphere to Texture Mapping' block. This block outputs a '2D Texture' and 'VR Rendering Metadata'. These are then processed by a 'Conventional 2D Video Encoder' and 'VR Metadata Encoding' respectively, resulting in a 'Video Bitstream' and 'Coded Metadata'. These are then processed by a 'Conventional 2D Video Decoder' and 'VR Metadata Decoding' respectively, resulting in a '2D Texture' and 'VR rendering Metadata'. These are then processed by a 'Postprocessing Texture to Sphere Mapping' block, which outputs the final spherical coordinate system icon.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +Figure 4.1-4: A flowchart illustrating the video signal representation process. It starts with a spherical coordinate system icon, followed by a 'Preprocessing Sphere to Texture Mapping' block. This block outputs a '2D Texture' and 'VR Rendering Metadata'. These are then processed by a 'Conventional 2D Video Encoder' and 'VR Metadata Encoding' respectively, resulting in a 'Video Bitstream' and 'Coded Metadata'. These are then processed by a 'Conventional 2D Video Decoder' and 'VR Metadata Decoding' respectively, resulting in a '2D Texture' and 'VR rendering Metadata'. These are then processed by a 'Postprocessing Texture to Sphere Mapping' block, which outputs the final spherical coordinate system icon. + +**Figure 4.1-4: Video Signal Representation** + +Mapping of a spherical picture to a 2D texture signal is illustrated in Figure 4.1-5. The most commonly used mapping from spherical to 2D is the equirectangular projection (ERP) mapping. The mapping is bijective, i.e. it may be expressed in both directions. + +![Figure 4.1-5: Examples of Spherical to 2D mappings. The diagram shows a 3D coordinate system (X, Y, Z) with a sphere. A point on the sphere is defined by azimuth angle phi and elevation angle theta. An arrow labeled 'Mapping' points to a 2D rectangular projection. The projection is labeled 'Projected picture (2D texture signal)' and has angular markings: 90° at the top, -90° at the bottom, -180° on the left, and 180° on the right. The sphere is labeled '3D Space'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 4.1-5: Examples of Spherical to 2D mappings. The diagram shows a 3D coordinate system (X, Y, Z) with a sphere. A point on the sphere is defined by azimuth angle phi and elevation angle theta. An arrow labeled 'Mapping' points to a 2D rectangular projection. The projection is labeled 'Projected picture (2D texture signal)' and has angular markings: 90° at the top, -90° at the bottom, -180° on the left, and 180° on the right. The sphere is labeled '3D Space'. + +**Figure 4.1-5: Examples of Spherical to 2D mappings** + +Following the definitions in clause 4.1.2, the mapping of the colour samples of 2D texture images onto a spherical coordinate space in angular coordinates $(\phi, \theta)$ for use in omnidirectional video applications for which the viewing perspective is from the origin looking outward toward the inside of the sphere. The spherical coordinates are defined so that $\phi$ is the azimuth and $\theta$ is the elevation. + +Assume a 2D texture with `pictureWidth` and `pictureHeight`, being the width and height, respectively, of a monoscopic projected luma picture, in luma samples and the center point of a sample location $(i, j)$ along the horizontal and vertical axes, respectively, then for the *equirectangular* projection the sphere coordinates $(\phi, \theta)$ for the luma sample location, in degrees, are given by the following equations: + +$$\begin{aligned}\phi &= ( 0.5 - i \div \text{pictureWidth} ) * 360 \\ \theta &= ( 0.5 - j \div \text{pictureHeight} ) * 180\end{aligned}$$ + +Whereas ERP is commonly used for production formats, other mappings may be applied, especially for distribution. The present document also introduces cubemap projection (CMP) for distribution in clause 5. In addition to regular projection, other pre-processing may be applied to the spherical video when mapped into 2D textures. Examples include region-wise packing, stereo frame packing or rotation. The present document defines different pre- and post-processing schemes in the context of video rendering schemes. + +### 4.1.4 Audio Signal Representation + +Audio for VR can be produced using three different formats. These are broadly known as channels-, objects- and scene-based audio formats. Audio for VR can use any one of these formats or a hybrid of these (where all three formats are used to represent the spherical soundfield). The audio signal representation model is shown in Figure 4.1-6. + +The present document expects that an audio encoding system is capable to produce suitable audio bitstreams that represent a well-defined audio signal in the reference system as defined in clause 4.1.1. The coding and carriage of the VR Audio Rendering Metadata is expected to be defined by the VR Audio Encoding system. The VR Audio Receiving system is expected to be able to use the VR Audio Bitstream to recover audio signals and VR Audio Rendering metadata. Both signals, audio signals and metadata, are well-defined by the media profile, such that different audio rendering systems may be used to render the audio based on the decoder audio signals, VR audio rendering metadata and the user position. + +In the present document, all media profiles are defined such that for each media profile at least one Audio Rendering System is defined as a reference renderer and additional Audio Rendering systems may be defined. The audio rendering system is described based on well-defined output of the VR Audio decoding system. + +![Figure 4.1-6: Audio Signal Representation. This block diagram shows the flow of audio data. It starts with an icon of a house with sound waves, followed by 'Audio Signal Preprocessing' which outputs 'Audio Signals' and 'VR Audio Rendering Metadata'. These go into the 'VR Audio Encoding System', which outputs a 'VR Audio Bitstream'. This bitstream is then processed by the 'VR Audio Decoding System' (part of the 'VR Audio Receiving System'), which outputs 'Decoded Audio Signals' and 'VR Audio Rendering Metadata'. These are then processed by the 'Audio Rendering System', which finally outputs an icon of a house with sound waves and a head icon.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +Figure 4.1-6: Audio Signal Representation. This block diagram shows the flow of audio data. It starts with an icon of a house with sound waves, followed by 'Audio Signal Preprocessing' which outputs 'Audio Signals' and 'VR Audio Rendering Metadata'. These go into the 'VR Audio Encoding System', which outputs a 'VR Audio Bitstream'. This bitstream is then processed by the 'VR Audio Decoding System' (part of the 'VR Audio Receiving System'), which outputs 'Decoded Audio Signals' and 'VR Audio Rendering Metadata'. These are then processed by the 'Audio Rendering System', which finally outputs an icon of a house with sound waves and a head icon. + +**Figure 4.1-6: Audio Signal Representation** + +For more details on audio rendering, refer to clause 4.5. + +## 4.2 End-to-end Architecture + +The architecture introduced in this clause addresses service scenarios for the distribution of VR content in file-based download and DASH-based streaming services. + +Figure 4.2-1 considers a functional architecture for such scenarios. VR Content is acquired and the content is pre-processed such that all media components are mapped to the 3GPP 3DOF coordinate system and are temporarily synchronized. Such pre-processing may include video stitching, rotation or other translations. The 3GPP VR Headend is responsible for generating content that can be consumed by receivers conforming to the present document. Typically, 3D Audio and spherical video signals are properly encoded. Especially for video, the processing follows the two step approach of mapping, projecting and pre-processing to 2D texture and then encoding with regular 2D video codecs. After media encoding, the content is made available to file format encapsulation engine as elementary streams. The encapsulated streams are referred to as 3GPP VR Tracks, i.e. they are spatially mapped to the same timing system for synchronized playback. For file based distribution a complete file for delivery is generated by multiplexing the 3GPP VR tracks into a single file. For DASH based delivery, the content is mapped to DASH segments and proper Adaptation Sets are generated, including the necessary MPD signaling. The Adaptation Sets are included in a VR Media Presentation, documented in a DASH MPD. Content may be made available such that it is optimized for a specific viewpoint, so the same content may be encoded in an ensemble of multiple viewport-optimized versions. + +The content is delivered through file based delivery or DASH based delivery, potentially using 3GPP services such as DASH in PSS or DASH-over-MBMS. + +At the receiving end, a VR application is assumed that communicates with the different functional blocks in the receivers' 3GPP VR service platform, namely, the DASH client or the download client, the file processing units for each media profile, the media decoding units, the rendering environment and the pose generator. The reverse operations of the VR Headend are performed. The operation is expected to be dynamic, especially taking into account updated pose information in the different stages of the receiver. The pose information is essential in the rendering units, but may also be used in the download or DASH client for delivery and decoding optimizations. For more details on the client reference architecture, refer to clause 4.3. + +![Figure 4.2-1: architecture for VR streaming services. The diagram illustrates the flow of VR content from acquisition to rendering. On the left, 'Acquisition' feeds into 'Audio Preprocessing' and 'Visual Preprocessing'. These lead to '3D Audio Signal' and '3D Video Signal' respectively, which are 'Temporarily synced and spatially aligned in 3GPP 3DOF system'. The '3GPP Virtual Reality Headend' (top right) contains '3D Audio Encoding', 'Projection and Mapping' (for video), 'File Format Encapsulation', 'DASH Integration', 'Multiplexing', and 'DASH MPD'. It outputs '3GPP VR Audio Track(s)' and '3GPP VR Video Track(s)'. These tracks are delivered via 'File Format Delivery' (VR File) or 'DASH Delivery' (VR Media Presentation). The '3GPP VR Service Platform' (bottom) includes 'Access and Demultiplexing', 'File Format Processing', '3D Audio Decoding', '2D Video Decoding', 'Audio Rendering', 'Visual Viewport Rendering', 'Pose Generation', 'Controller', and 'DASH Access Client'. The 'VR Application' (bottom right) interacts with the 'Controller' and 'DASH Access Client'. A human head icon on the left shows orientation parameters: Yaw α, Pitch β, and Roll γ.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +Figure 4.2-1: architecture for VR streaming services. The diagram illustrates the flow of VR content from acquisition to rendering. On the left, 'Acquisition' feeds into 'Audio Preprocessing' and 'Visual Preprocessing'. These lead to '3D Audio Signal' and '3D Video Signal' respectively, which are 'Temporarily synced and spatially aligned in 3GPP 3DOF system'. The '3GPP Virtual Reality Headend' (top right) contains '3D Audio Encoding', 'Projection and Mapping' (for video), 'File Format Encapsulation', 'DASH Integration', 'Multiplexing', and 'DASH MPD'. It outputs '3GPP VR Audio Track(s)' and '3GPP VR Video Track(s)'. These tracks are delivered via 'File Format Delivery' (VR File) or 'DASH Delivery' (VR Media Presentation). The '3GPP VR Service Platform' (bottom) includes 'Access and Demultiplexing', 'File Format Processing', '3D Audio Decoding', '2D Video Decoding', 'Audio Rendering', 'Visual Viewport Rendering', 'Pose Generation', 'Controller', and 'DASH Access Client'. The 'VR Application' (bottom right) interacts with the 'Controller' and 'DASH Access Client'. A human head icon on the left shows orientation parameters: Yaw α, Pitch β, and Roll γ. + +**Figure 4.2-1: architecture for VR streaming services** + +Based on the architecture in Figure 4.2-1, the following components are relevant for 3GPP VR Streaming Services: + +- Consistent source formats that can be distributed by a 3GPP VR Headend: + - For audio that can be used by a 3D audio encoding profile according to the present document. + +- For video that can be used by a spherical video encoding profile according to the present document. +- Mapping formats from a 3-dimensional representation to a 2D representation in order to use regular video encoding engines +- Encapsulation of the media format tracks to ISO file format together, adding sufficient information on to decode and render the VR content. The necessary metadata may be on codec level, file format level, or both. +- Delivery of the formats through file download, DASH delivery and DASH-over-MBMS delivery. +- Static and dynamic capabilities and environmental data, including decoding and rendering capabilities, as well as dynamic pose information. +- Media decoders that support the decoding of the formats delivered to the receiver. +- Information for audio and video rendering to present the VR Presentation on the VR device. + +Based on the considerations above, to support the use case of VR Streaming, the following functions are defined in the present document: + +- Consistent content contribution formats for audio and video for 360/3D AV applications including their metadata. This aspect should be considered informative, but example formats are provided to enable explaining the workflow. +- Efficient encoding of 360 video content. In the present document, this encoding is split in two steps, namely a pre-processing and projection mapping from 360 video to 2D texture and a regular video encoding. +- Efficient encoding of 3D audio including channels, objects and scene-based audio. +- Encapsulation of VR media into a file format for download delivery. +- The relevant enablers for DASH delivery of VR experiences. +- The necessary capabilities for static and dynamic consumption of the encoded and delivered experiences in the Internet media type and the DASH MPD. +- A reference client architecture that provides the signalling and processing steps for download delivery as well as DASH delivery as well as the interfaces between the 3GPP VR service platform, a VR application (e.g. pose information), and the VR rendering system (displays, GPU, loudspeakers). +- Decoding requirements for the defined 360 video formats. +- Decoding requirements for the defined 3D audio formats. +- Rendering requirements or recommendations for the above formats, for both separate and integrated decoding/rendering. + +## 4.3 Client Reference Architecture + +This clause provides more details of a client reference architecture for VR streaming applications and describes their components and interfaces. + +Figure 4.3-1 and Figure 4.3-2 show a high-level structure of the client reference architecture for VR DASH streaming and VR local playback, respectively, which consist of five functional components: + +- *VR Application*: The VR application controls the rendering depending on a user viewport or display capabilities. The application may communicate with other functional components, e.g., the access engine, the file decoder. The access engine or file decoder may parse some abstracted control information to the VR application and the application makes the decision on which adaptation sets or preselections to select or which tracks to choose taking into account platform or user information as well as the dynamic pose information. +- *Access Engine*: The access engine connects through a 3GPP bearer and provides a conforming VR presentation to the receiver. The access engine fetches the Media Presentation Description (MPD), constructs and issues requests and receives Segments or parts of Segments. In the case of local playback, the 3GPP VR Track is accessed from the local storage. The access engine may interface with the VR application function to + +dynamically change the delivery session. The access engine provides a conforming 3GPP VR track to the file decoder. + +- *File Decoder*: The file decoder processes the 3GPP VR Track to generate signals that can be processed by the renderer. The file decoder typically includes at least of two sub-modules; the file parser and the media decoder. The file parser processes the file or segments, extracts elementary streams, and parses the metadata, if present. The processing may be supported by dynamic information provided by the VR application, for example which tracks to choose based on static and dynamic configurations. The media decoder decodes media streams of the selected tracks into the decoded signals. The file decoder outputs the decoded signals and metadata which is used for rendering. The file decoder is the primary focus of the present document. +- *VR Renderer*: The VR Renderer uses the decoded signals and rendering metadata and provides a viewport presentation taking into account the viewport and possible other information. With the pose, a user viewport is determined by determining horizontal/vertical field of view of the screen of a head-mounted display or any other display device to render the appropriate part of decoded video or audio signals. The renderer is addressed in individual media profiles. For video, textures from decoded signals are projected to the sphere with rendering metadata received from the file decoder. During the texture-to-sphere mapping, a sample of the decoded signal is remapped to a position on the sphere. Likewise, the decoded audio signals are represented in the reference system domain. The appropriate part of video and audio signals for a current pose is generated by synchronizing and spatially aligning the rendered video and audio. +- *Sensor*: The sensor extracts the current pose according to the user's movement and provides it to the renderer for viewport generation. The current pose may for example be determined by the head tracking and possibly also eye tracking functionalities. The current pose may also be used by the VR application to control the access engine on which adaptation sets or preselections to select (for the streaming case), or to control the file decoder on which tracks to choose for decoding (for the local playback case). + +The main objective of the present document is to enable the file decoder to generate decoded signals and the rendering metadata from a conforming 3GPP VR Track by generating a bitstream that conforms to a 3GPP Operation Point. Both, a 3GPP VR Track as well as a bitstream conforming to an Operation Point are a well-defined conformance points for a VR File decoder and a Media Decoder. Both enable to represent the contained media in the VR reference system (spatially and temporally). + +NOTE 1: 3GPP VR Track represents media in container formats according to the ISO/IEC 14496-12 [17] ISO Base Media File Format and may consist of one or more ISO BMFF tracks following the requirements of this specification. + +![Figure 4.3-1: Client Reference Architecture for VR DASH Streaming Applications. The diagram shows a flow from MPD and Segment inputs through a DASH Access Engine to a File Decoder (containing File Parser, 3GPP Operation Point, and Media Decoder), then to a VR Renderer, and finally to Viewport Presentation. A VR Application and Sensor provide control and pose information to the components.](77464a47f104d0d647b2414591137b64_img.jpg) + +``` + +graph LR + MPD[MPD] --> DASH[DASH Access Engine] + Segment[Segment] --> DASH + DASH -- "3GPP VR Track" --> FD[File Decoder] + subgraph FD [File Decoder] + direction TB + FP[File Parser] + OP[3GPP Operation Point] + MD[Media Decoder] + end + FD -- "Decoded Signal" --> VR[VR Renderer] + FD -- "Rendering Metadata" --> VR + VR -- "Viewport Presentation" --> VP[Viewport Presentation] + VA[VR Application] -- "Static and Dynamic Configuration and Control" -.-> DASH + VA -- "Static and Dynamic Configuration and Control" -.-> FD + VA -- "Static and Dynamic Configuration and Control" -.-> VR + S[Sensor] -- "Pose" -.-> VA + S -- "Pose" -.-> VR + +``` + +Figure 4.3-1: Client Reference Architecture for VR DASH Streaming Applications. The diagram shows a flow from MPD and Segment inputs through a DASH Access Engine to a File Decoder (containing File Parser, 3GPP Operation Point, and Media Decoder), then to a VR Renderer, and finally to Viewport Presentation. A VR Application and Sensor provide control and pose information to the components. + +Figure 4.3-1: Client Reference Architecture for VR DASH Streaming Applications + +![Figure 4.3-2: Client Reference Architecture for VR Local Playback. This block diagram shows the flow of data for VR playback. On the left, 'Local Storage' provides a '3GPP VR Track' to a 'File Decoder' block. The 'File Decoder' contains a 'File Parser', a '3GPP Operation Point' block, and a 'Media Decoder'. It outputs a 'Decoded Signal' and 'Rendering Metadata' to a 'VR Renderer'. The 'VR Renderer' produces a 'Viewport Presentation'. Below the main flow, a 'VR Application' block is connected to 'Local Storage' and the 'File Decoder' via dashed arrows representing optional interfaces. A 'Sensor' block provides 'Pose' information to the 'VR Renderer' and is also connected to the 'VR Application' via dashed arrows.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 4.3-2: Client Reference Architecture for VR Local Playback. This block diagram shows the flow of data for VR playback. On the left, 'Local Storage' provides a '3GPP VR Track' to a 'File Decoder' block. The 'File Decoder' contains a 'File Parser', a '3GPP Operation Point' block, and a 'Media Decoder'. It outputs a 'Decoded Signal' and 'Rendering Metadata' to a 'VR Renderer'. The 'VR Renderer' produces a 'Viewport Presentation'. Below the main flow, a 'VR Application' block is connected to 'Local Storage' and the 'File Decoder' via dashed arrows representing optional interfaces. A 'Sensor' block provides 'Pose' information to the 'VR Renderer' and is also connected to the 'VR Application' via dashed arrows. + +**Figure 4.3-2: Client Reference Architecture for VR Local Playback** + +NOTE 2: The dashed arrows indicate optional interfaces between components in the Figure 4.3-2. Viewport information should optionally be input to the access engine and file decoder. + +## 4.4 Rendering Schemes, Operation Points and Media Profiles + +The present document provides several interoperability points that may be referred external specifications. These are: + +- **Media profiles:** providing DASH, file format and elementary stream constraints for a single media type. +- **Operation Points:** a collection of discrete combinations of different content formats including spatial and temporal resolutions, colour mapping, transfer functions, rendering metadata and the encoding format. +- **Bitstream:** A video bitstream that conforms to a video encoding format and certain Operation Point including VR Rendering Metadata. +- **Rendering Scheme:** post-decoder processing of decoder output signals together with rendering metadata. + +Note that this applies to both media types, audio and video. For audio, the 3GPP VR Rendering Scheme interoperability point serves as an informative output of the File Decoder. The 3GPP VR viewport interoperability point serves as the output of the entire file decoding process. + +Both features provide clear requirements for interoperability for receiver. Figure 4.4-1 provides an overview on this. + +![Figure 4.4-1: Interoperability aspects for 3GPP VR Profiles. This diagram shows the flow of data through various interoperability points. Inputs (M4D, Segment) enter an 'Access Engine', which outputs a '3GPP VR Track'. This track enters a 'File Decoding Process' block containing 'File Parser', 'Media Bitstream', and 'Media Decoder'. The process outputs 'Decoded Signal' and 'Rendering Metadata' to a 'VR Renderer', which produces 'Viewport Presentation'. Red vertical lines mark five interoperability points: 1) '3GPP VR DASH Interop point' before the Access Engine; 2) '3GPP VR Media Profile Interop point' between the Access Engine and File Decoding Process; 3) '3GPP VR Operation Point' within the File Decoding Process; 4) '3GPP VR Rendering Scheme Interop point' between the File Decoding Process and VR Renderer; 5) '3GPP VR Viewport test point' after the VR Renderer. A green horizontal line labeled '3GPP VR API' connects the 'VR Application' and 'Sensor' blocks at the bottom to the 'Access Engine', 'File Decoding Process', and 'VR Renderer'.](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +Figure 4.4-1: Interoperability aspects for 3GPP VR Profiles. This diagram shows the flow of data through various interoperability points. Inputs (M4D, Segment) enter an 'Access Engine', which outputs a '3GPP VR Track'. This track enters a 'File Decoding Process' block containing 'File Parser', 'Media Bitstream', and 'Media Decoder'. The process outputs 'Decoded Signal' and 'Rendering Metadata' to a 'VR Renderer', which produces 'Viewport Presentation'. Red vertical lines mark five interoperability points: 1) '3GPP VR DASH Interop point' before the Access Engine; 2) '3GPP VR Media Profile Interop point' between the Access Engine and File Decoding Process; 3) '3GPP VR Operation Point' within the File Decoding Process; 4) '3GPP VR Rendering Scheme Interop point' between the File Decoding Process and VR Renderer; 5) '3GPP VR Viewport test point' after the VR Renderer. A green horizontal line labeled '3GPP VR API' connects the 'VR Application' and 'Sensor' blocks at the bottom to the 'Access Engine', 'File Decoding Process', and 'VR Renderer'. + +**Figure 4.4-1: Interoperability aspects for 3GPP VR Profiles** + +Media profile for timed media is defined as requirements and constraints for a set of one or more 3GPP VR tracks of a single media type. The conformance of a set of one or more 3GPP VR tracks to a media profile is specified as a combination of: + +- Specification of which sample entry type(s) are allowed, and which constraints and extensions are required in addition to those imposed by the sample entry type(s). +- Constraints on the samples of the tracks, typically expressed as constraints on the elementary stream contained within the samples of the tracks. + +The elementary stream constraints of a media profile may be indicated by a requirement to comply with a certain profile and level of the media coding specification, possibly including additional constraints and extensions, such as a requirement of the presence of certain information for rendering and presentation. + +Each media profile specified in the present document includes a file decoding process such that all file decoders that conform to the video media profile will produce: + +- For video: numerically identical cropped decoded pictures when invoking the file decoding process associated with that video media profile for a set of 3GPP VR tracks conforming to the video media profile. A bitstream that conforms to the elementary stream constraints specified for the video media profile is reconstructed as an intermediate product of the file decoding process. Output of the file decoding process consists of all of the following: + - a list of decoded pictures with associated presentation times; + - for projected omnidirectional video VR rendering metadata. +- for audio: a set of audio signals when invoking the file decoding process associated with that audio media profile for a VR Track conforming to the audio media profile. A bitstream that conforms to the elementary stream constraints specified for the audio media profile is reconstructed as an intermediate product of the file decoding process. Output of the file decoding process consists of all of the following: + - a sequence of audio samples with associated presentation times; + - audio VR rendering metadata. + +A file decoder conforms to the file decoding process requirements of the present document when it complies with both of the following: + +- for video: + - The file decoder includes a conforming decoder that produces numerically identical cropped decoded pictures to those produced by the file decoding process specified for the video media profile in clause 5 (with the correct output order or output timing, as specified in the video coding specification of the video media profile, respectively). + - The file decoder outputs rendering metadata that is equivalent to that produced by the file decoding process specified for the video media profile in clause 5 (with the correct association of the rendering metadata to particular cropped decoded pictures, as specified in the present document). +- for audio: + - The file decoder includes a conforming decoder that produces a sequence of audio samples with associated presentation times as defined in clause 6. + - The file decoder outputs Audio rendering metadata that is equivalent to that produced by the file decoding process specified for the audio media profile in clause 6 (with the correct association of the rendering metadata to particular audio samples). + +A player claiming conformance to a media profile shall include a file decoder complying with the file decoding process of that video media profile as specified above. While the player operation, with the exception of the file decoding process, is not specified normatively in the present document, specifications of a media profile may include an informative clause on expectations of a player operation, for example including recommendations for rendering. + +In addition to the interoperability on track level, also a DASH level interoperability for each media profile is defined. This interoperability includes the signalling and content generation, such that by dynamic switching based on network constraints or sensor input a conforming 3GPP VR Track for this media profile may be obtained. + +## 4.5 Audio Rendering + +### 4.5.1 Audio Renderer Definitions + +#### 4.5.1.1 Reference Renderer + +a) The purpose of the *Reference Renderer* is to provide a documented audio rendering solution in 3GPP for its corresponding media profile. A *Reference Renderer*: + +- a) Is specified along with the media profile. +- b) Supports binaural and loudspeaker based rendering. +- c) Has a standardized implementable description documented either in 3GPP or in an external SDO. +- d) Supports diegetic and non-diegetic content. +- e) Has a Motion to Sound latency characterized according to the method defined in TS 26.260 [15]. +- f) Has a Loudness characterized according to the method defined in TS 26.260 [15]. +- g) Provides a suitable subjective quality level characterized by the *Rendering Test* (see clause 4.5.1.6). +- h) Provides an interface to specify the set of HRTFs used for binaural rendering. + +NOTE: The *Reference Renderer* could be an external renderer following the properties defined above. + +#### 4.5.1.2 Common Informative Binaural Renderer (CIBR) + +The CIBR is a binaural renderer defined for the purposes of the Renderer Test in TS 26.259 [16]. The CIBR: + +- a) Supports binaural rendering. +- b) Supports diegetic and non-diegetic content. +- c) Has a Motion to Sound latency characterized according to the method defined in TS 26.260 [15]. +- d) Has a Loudness characterized according to the method defined in TS 26.260 [15]. +- e) Is intended to provide a quality comparison point for the *Reference Renderer* (see clause 4.5.1.1) and any *External Renderer* (see clause 4.5.1.3). + +The CIBR consists of four components. The first three are currently available as VST audio plugins: + +- 1) The "*ESD to HOA*" component, which receives a set of audio input signals in an Equivalent Spatial Domain (ESD) representation and converts them into a set of audio output signals in the HOA domain (ACN/SN3D format). The ESD representation corresponds to the immersive audio content rendered at a set of pre-determined virtual loudspeaker locations (Fliege Points). The ESD to HOA conversion is accomplished using the "AmbiX Decoder" plugin () with the appropriate conversion matrices specified in TS 26.260 [15] clause 4.1 (Fliege Points). +- 2) The "*Sound Field rotation*" component, which performs rotation of the soundfield in the HOA domain. The sound field rotation is accomplished with the "AmbiX Soundfield Rotator" plugin () using a connected headtracking device. +- 3) The "*HOA to Binaural*" component, which performs the binaural rendering of the HOA signals. The HOA to binaural conversion is accomplished with the "Google Resonance Monitoring" plugin (), which supports up to 3rd order HOA. +- 4) A "*Diegetic/Non-Diegetic content mixer*". The non-diegetic signals are directly mixed at the headphone output. + +Note that the CIBR may introduce spatial and or timbral quality changes to the rendered objects and channel based-audio signals (ESD loudspeaker inputs). + +![Block diagram of Common Informative Binaural Renderer](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the signal flow of a Common Informative Binaural Renderer. It consists of three main processing blocks: 'ESD to HOA converter', 'Sound Field Rotation', and 'HOA to Binaural converter'. An 'ESD Loudspeaker input' enters the first block. A dashed blue line labeled 'Motion Sensing' connects the 'Sound Field Rotation' block to a 'Headph Output' icon. The output of the third block is combined with 'Non-Diegetic Content' at a circular mixer icon before reaching the headphones. + +Block diagram of Common Informative Binaural Renderer + +**Figure 4.5-1: Block diagram of Common Informative Binaural Renderer** + +#### 4.5.1.3 External Renderer + +The primary purpose of the *External Renderer* is to enable alternatives to the *Reference Renderer*. There may be several *External Renderers* for a given media profile. + +An *External Renderer*: + +- a) Supports binaural and/or loudspeaker based rendering. +- b) Can be the *Reference Renderer* associated to the Audio Media Profile. +- c) Does not require a standardized implementable description. +- d) Exposes an *External Renderer API* (see clause 4.5.1.5) and/or the *Common Renderer API* (see clause 4.5.1.4) for connecting it to an audio decoder. +- e) Supports diegetic and non-diegetic content. +- f) Has a Motion to Sound latency documented according to the method defined in TS 26.260 [15]. +- g) Has a Loudness documented according to the method defined in TS 26.260 [15]. +- h) Provides a suitable subjective quality level characterized according to the *Rendering Test* (see clause 4.5.1.6) with additional comparison with the *Reference Renderer*. +- i) Provides an interface to specify the set of HRTFs used for binaural rendering if applicable. + +#### 4.5.1.4 Common Renderer API + +The purpose of the *Common Renderer API* is to enable the use of an *External Renderer* that can support all VRStream media profiles. The *Common Renderer API*: + +- a) Is normative. +- b) Has a standardized implementable description in 3GPP technical specifications or by reference. + +#### 4.5.1.5 External Renderer API + +The purpose of the *External Renderer API* is to enable the use of an *External Renderer*. The *External Renderer API*: + +- a) Has a standardized implementable description in 3GPP technical specifications or by reference. + +- b) Provides the necessary information to connect a VRStream media profile with an *External Renderer*. + +#### 4.5.1.6 Rendering Test + +The purpose of the Rendering Test is to characterize the Quality of Experience (QoE) when using the *Reference Renderer* or *External Renderer*. + +The *Rendering Test*: + +- a) Is defined in TS 26.259 [16] clause 6. +- b) Characterizes media profile performance with *Reference Renderer* or *External Renderer*. +- c) Assesses performance for multiple audio quality attributes and overall quality. + +# 5 Video + +## 5.1 Video Operation Points + +### 5.1.1 Definition of Operation Point + +For the purpose to define interfaces to a conforming video decoder, video operation points are defined. In this case the following definitions hold: + +- **Operation Point:** A collection of discrete combinations of different content formats including spatial and temporal resolutions, colour mapping, transfer functions, VR specific rendering metadata, etc. and the encoding format. +- **Receiver:** A receiver that can decode and render any bitstream that is conforming to a certain Operation Point. +- **Bitstream:** A video bitstream that conforms to a video encoding format and certain Operation Point including VR rendering metadata. + +![Figure 5.1-1: Video Operation Points. A block diagram showing the flow of video data from a 3GPP VR DASH Profile through an Access Engine, a File Decoder (containing a File Parser and Media Decoder), and a VR Renderer to a Viewport Presentation. The diagram also shows the interaction between a VR Application and a Sensor via the 3GPP VR API, providing Static and Dynamic Configuration and Control, and Pose information.](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +The diagram illustrates the video processing pipeline for VR. It starts with the **3GPP VR DASH Profile** (MPD and Segment) entering the **Access Engine**. The **Access Engine** outputs a **3GPP VR Track** to the **File Decoder**. The **File Decoder** contains a **File Parser** and a **Media Decoder**. The **Media Decoder** outputs a **Decoded Signal** and **Rendering Metadata** to the **VR Renderer**. The **VR Renderer** outputs the **Viewport Presentation**. Below the main flow, a **VR Application** and a **Sensor** are connected via the **3GPP VR API**. The **VR Application** provides **Static and Dynamic Configuration and Control** to the **Access Engine** and receives **Pose** information from the **Sensor**. + +Figure 5.1-1: Video Operation Points. A block diagram showing the flow of video data from a 3GPP VR DASH Profile through an Access Engine, a File Decoder (containing a File Parser and Media Decoder), and a VR Renderer to a Viewport Presentation. The diagram also shows the interaction between a VR Application and a Sensor via the 3GPP VR API, providing Static and Dynamic Configuration and Control, and Pose information. + +Figure 5.1-1: Video Operation Points + +This clause focuses on the interoperability point to a media decoder as indicated in Figure 5.1-1. This clause does not deal with the access engine and file parser which addresses aspects how the video bitstream is delivered. + +In all video operation points, the VR Presentation can be rendered using a single media decoder which provides decoded signals and rendering metadata by decoding relevant SEI messages. + +### 5.1.2 Parameters of Visual Operation Point + +This clause defines the potential parameters of Visual Operation Points. This includes the video decoder profile and levels with additional restrictions, conventional video signal parameters and VR rendering metadata. The requirements are defined from the perspective of the video decoder and renderer. + +Parameters for a Visual Operation Point include: + +- Codec, Profile and level requirements +- Restrictions of regular video parameters, typically expressed in the Video Usability information +- Usage and restrictions of VR rendering metadata + +### 5.1.3 Operation Point Summary + +The present document defines several operation points for different target applications and scenarios. In particular, two legacy operation points are defined that use existing video codecs H.264/AVC and H.265/HEVC to enable distribution of up to 4K full 360 mono video signals up to 60 Hz by using simple equirectangular projection. + +In addition, one operation for each codec is defined that enables enhanced features, in particular stereo video, up to 8K mono, higher frame rates and HDR. + +Furthermore, one additional operation point is defined that uses H.265/HEVC to enable distribution of up to 8K full 360 mono video signals up to 60 Hz and with HDR using equirectangular projection. + +Table 5.1-1 summarizes the Operation Points, the detailed definitions are defined in the remainder of clause 5.1 where 3k refers to 2880 × 1440 pixels, 4k to 4096 × 2048 pixels, 6k to 6144 × 3072 pixels and 8k to 8192 × 4096 pixels (expressed in luminance pixel width × luminance pixel height). + +Note: The Table only provides an informative high-level summary and is not considered to be complete. The specification text in the remainder of clause 5.1 refines the table and takes precedence over any information documented in the table. + +Restrictions on source formats such as resolution and frame rates, content generation and encoding guidelines are provided in Annex A. + +**Table 5.1-1: High-level Summary of Operation Points** + +| Operation Point name | Decoder | Bit depth | Typical Original Spatial Resolution | Frame Rate | Colour space format | Transfer Characteristics | Projection | Rotation | RWP | Stereo | +|----------------------|--------------------------------------|-----------|-------------------------------------|--------------------------------------|---------------------|---------------------------------------|------------------------|----------|---------------------------------|--------| +| Basic H.264/AVC | H.264/AVC HP@L5.1 | 8 | Up to 4k | Up to 60 Hz | BT.709 | BT.709 | ERP w/o padding | No | No | No | +| Main H.265/HEVC | H.265/HEVC MP10@L5.1 | 8, 10 | Up to 6k in mono and 3k in stereo | Up to 60 Hz | BT.709
BT.2020 | BT.709 | ERP w/o padding | No | Yes | Yes | +| Flexible H.265/HEVC | H.265/HEVC MP10@L5.1 | 8, 10 | Up to 8k in mono and 3k in stereo | Up to 120 Hz | BT.709
BT.2020 | BT.709,
BT.2100 PQ,
BT.2100 HLG | ERP w/o padding
CMP | No | Yes | Yes | +| Main 8K H.265/HEVC | H.265/HEVC MP10@L6.1 | 10 | Up to 8k in mono and 6k in stereo | Up to 60 Hz for 8K and 120 Hz for 4k | BT.709
BT.2020 | BT.709,
BT.2100 PQ,
BT.2100 HLG | ERP w/o padding | No | Yes, but restricted to coverage | Yes | + +VR Rendering metadata in the Operation Points is carried in SEI messages. Receivers are expected to be able to process the VR metadata carried in SEI messages. However, the same VR metadata may be duplicated on system-level. In this case, the Receiver may rely on the system level processing to extract the relevant VR Rendering metadata rather than extracting this from the SEI message. + +### 5.1.4 Basic H.264/AVC + +#### 5.1.4.1 General + +This operation point targets simple deployments and legacy receivers at basic quality. A full 360-degree video signal with equirectangular projection following the 3GPP reference system may be provided to the decoding and rendering system for immediate decoding and rendering. Note that this operation point enables to distribute 4k video at regular frame rates and 3k video at higher frame rates. + +Restricted coverage is supported as well, but only in a basic and backward-compatible fashion. + +A Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation point shall conform to the requirements in the remainder of clause 5.1.4. + +A receiver conforming to the 3GPP VR Basic H.264/AVC Operation point shall support decoding and rendering a Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation point. Detailed receiver requirements are provided in the remainder of clause 5.1.4. + +#### 5.1.4.2 Profile and level + +A Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation point shall conform to H.264/AVC Progressive High Profile Level 5.1 [5] for H.264/AVC with the following additional restrictions and requirements: + +- the maximum VCL Bit Rate is constrained to be 120 Mbps with `cpbBrVclFactor` and `cpbBrNalFactor` being fixed to be 1250 and 1500, respectively. +- the bitstream does not contain more than 10 slices per picture. + +NOTE: High Profile for H.264/AVC excludes Flexible macro-block order, Arbitrary slice ordering, Redundant slices, Data partition. + +Hence, for a Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation point, the following applies: + +- The `profile_idc` shall be set to 100 indicating the High profile. +- The `constrain_set0_flag`, `constrain_set1_flag`, `constrain_set2_flag` and `constrain_set3_flag` shall all be set to 0. +- The value of `level_idc` shall not be greater than 51 (corresponding to the level 5.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 5.1.4.3 Aspect Ratios and Spatial resolutions + +Picture aspect ratio 2:1 should be used for the encoded picture. + +The spatial resolution of the original format in equirectangular projection (ERP) should be one of the following (expressed in luminance pixel width $\times$ luminance pixel height): + +- 4096 $\times$ 2048, 3840 $\times$ 1920, 3072 $\times$ 1536, 2880 $\times$ 1440, 2048 $\times$ 1024. + +The spatial resolution of the distribution format should be one of the following (expressed in luminance pixel width $\times$ luminance pixel height): + +- 3840 $\times$ 1920, 2880 $\times$ 1440, 1920 $\times$ 960, 1440 $\times$ 720, 960 $\times$ 480. +- 4096 $\times$ 2048, 3072 $\times$ 1536, 2048 $\times$ 1024, 1536 $\times$ 768, 1024 $\times$ 512. + +NOTE: Distribution formats do not exceed the native resolution of the Operation Point, but they may be subsampled in order to optimize distribution or adapt to the viewing conditions. + +A Receiver conforming to the 3GPP VR Basic H.264/AVC Operation Point shall be capable of decoding and rendering Bitstreams that contain spatial resolutions as above. + +#### 5.1.4.4 Colour information + +A Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation Point shall use Recommendation ITU-R BT.709 [3] colorimetry. Hence, in the VUI, the colour parameter information shall be present, i.e. + +- `video_signal_type_present_flag` value and `colour_description_present_flag` value shall be set to 1. +- The `colour_primaries` value, the `transfer_characteristics` value and the `matrix_coefficients` value in the Video Usability Information shall all be set to 1. + +A Receiver conforming to the 3GPP VR Basic H.264/AVC Operation Point shall be capable of decoding and rendering Bitstreams that use Recommendation ITU-R BT.709 [3] colorimetry according to the bitstream requirements documented above. + +#### 5.1.4.5 Frame rates + +A Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation Point shall have one of the following frame rates: 24; 25; 30; 24/1001; 30/1001; 50; 60; 60/1001 Hz. + +The profile and level constraints of H.264/AVC Progressive High Profile Level 5.1 require careful balance of the permitted frame rates and spatial resolutions. Table 5.1-2 provides the permitted combinations of spatial resolutions and frame rates. + +**Table 5.1-2: Permitted combinations of spatial resolutions and frame rates** + +| Spatial Resolution | Permitted Frame Rates | +|--------------------|--------------------------------------------------| +| 4096 × 2048 | 24; 25; 30; 24/1001; 30/1001 Hz | +| 3840 × 1920 | 24; 25; 30; 24/1001; 30/1001 Hz | +| 3072 × 1536 | 24; 25; 30; 24/1001; 30/1001; 50 Hz | +| 2880 × 1440 | 24; 25; 30; 24/1001; 30/1001; 50; 60; 60/1001 Hz | +| 2048 × 1024 | 24; 25; 30; 24/1001; 30/1001; 50; 60; 60/1001 Hz | + +In the VUI, the timing information may be present: + +- If the timing information is present, i.e. the value of `timing_info_present_flag` is set to 1, then the values of `num_units_in_tick` and `time_scale` shall be set according to the frame rates allowed above. The timing information present in the video Bitstream should be consistent with the timing information signalled at the system level. +- The frame rate shall not change between two RAPs. `fixed_frame_rate_flag` value shall be set to 1. + +A Receiver conforming to the 3GPP VR Basic H.264/AVC Operation Point shall be capable of decoding and rendering Bitstreams that use frame rates according to the bitstream requirements documented above. + +#### 5.1.4.6 Random access point + +For H.264/AVC random access point (RAP) definition refer to TS 26.116 [12], clause 4.4.1.1. + +RAPs shall be present in the Bitstream at least once every 5 seconds. It is recommended that RAPs occur in the video Bitstream on average at least every 2 seconds. The time interval between successive RAPs is measured as the difference between their respective decoding time values. + +#### 5.1.4.7 Sequence parameter set + +The following restrictions apply to the active Sequence Parameter Set (SPS): + +- `gaps_in_frame_num_value_allowed_flag` value shall be set to 0. +- The Video Usability Information shall be present in the active Sequence Parameter Set. The `vui_parameter_present_flag` shall be set to 1. + +- The source video format shall be progressive. `frame_mbs_only_flag` shall be set to 1 for every picture of the Bitstream. + +#### 5.1.4.8 Video usability information + +In addition to the previous constraints on the VUI on colour information in clause 5.1.4.4 and on frame rates in clause 5.1.4.5, this clause contains further requirements. + +The aspect ratio information shall be present, i.e. + +- The `aspect_ratio_present_flag` value shall be set to 1. +- The `aspect_ratio_idc` value shall be set to 1 indicating a square pixel format. + +There are no requirements on output timing conformance for H.264/AVC decoding (Annex C of [5]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +#### 5.1.4.9 Omni-directional Projection Format + +This operation point uses equirectangular projection, such the video is automatically rendered in the 3GPP reference system. This is enabled by using the MPEG metadata on equirectangular projection. + +A Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation Point shall include the equirectangular projection SEI message (`payloadType` equal to 150) at every RAP. The `erp_guard_band_flag` shall be set to 0. + +A Receiver conforming to the 3GPP VR Basic H.264/AVC Operation Point shall be able to process the information contained on equirectangular projection SEI message (`payloadType` equal to 150) with `erp_guard_band_flag` shall be set to 0. + +#### 5.1.4.10 Restricted Coverage + +This operation point permits the decoding and rendering of restricted coverage video signals in a rudimentary way. In this case it is expected that pixels that are projected to a non-covered region are included in the full image, but are visually differentiated from the covered region, for example using black, grey or white colour. + +Application or system-based signalling may support signalling the coverage region. + +#### 5.1.4.11 Other VR Metadata + +For a Bitstream conforming to the 3GPP VR Basic H.264/AVC Operation Point: + +- the equirectangular projection SEI message (`payloadType` equal to 150) with `erp_guard_band_flag` not set to 0 shall not be present, +- the sphere rotation SEI message (`payloadType` equal to 154) shall not be present, +- the region-wise packing SEI message (`payloadType` equal to 155) shall not be present, +- the frame-packing arrangement SEI message (`payloadType` equal to 45) shall not be present. + +#### 5.1.4.12 Receiver Compatibility + +Receivers conforming to the 3GPP VR Basic H.264/AVC Operation Point shall support decoding and displaying 3GPP VR Basic H.264/AVC Operation Point Bitstreams. + +Receivers conforming to the 3GPP VR Basic H.264/AVC Operation Point shall support all Receiver requirements in clause 5.1.4. + +### 5.1.5 Main H.265/HEVC + +#### 5.1.5.1 General + +This operation targets enhanced 360 video decoding and rendering of H.265/HEVC video for VR applications. Among others, this operation point supports among others rendering of: + +- 4K mono video at up to 60 Hz frame rates +- 3K stereoscopic video at up to 60 Hz frame rates +- Higher than 4K resolutions for restricted coverage +- Rendering of certain viewpoints in higher quality than others beyond 4K +- extended colour space and SDR transfer characteristics + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation point shall conform to the requirements in the remainder of clause 5.1.5. + +A Receiver conforming to the 3GPP VR Main H.265/HEVC Operation point shall support decoding and rendering a Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation point. Detailed receiver requirements are provided in the remainder of clause 5.1.5. + +#### 5.1.5.2 Profile and level + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation point shall conform to H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6]. + +Hence, for a Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 153 (corresponding to the Level 5.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 5.1.5.3 Bit depth + +Bitstreams conforming to the 3GPP VR Main H.265/HEVC Operation point shall be encoded with either 8 or 10 bit precision: + +- `bit_depth_luma_minus8 = 0` or `2` (8 or 10 bits respectively) +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the 3GPP VR Main H.265/HEVC Operation Point shall support 8 bit and 10 bit precision. + +#### 5.1.5.4 Spatial Resolutions + +Due to the options provided in this operation point, additional original format may be considered that can then be decoded and rendered by a Receiver conforming to this operation point. Recommended original formats beyond those specified in clause 5.1.4.3 for equirectangular projection (ERP) are: + +- Mono formats: $6144 \times 3072$ , $5880 \times 2880$ +- Stereo formats with resolution for each eye: $3840 \times 1920$ , $2880 \times 1440$ , $2048 \times 1024$ + +If original signals are beyond the maximum permitted resolution of the video codec, then the region-wise packing needs to be applied to generate suitable distribution formats. + +The distribution formats are more flexible as additional VR metadata as defined in the remainder of clause 5.1.5 may be used. However, for the distribution formats, all requirements of H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6] shall apply to the decoded texture signal. + +According to H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6], the maximum luminance width and height does not exceed 8,444 pixels. In addition to the H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6] constraints, a Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation point, the decoded texture signal shall in addition: + +- not exceed the luminance width of 8192 pixels, and +- not exceed the luminance height of 8192 pixels. + +A Receiver conforming to the 3GPP VR Main H.265/HEVC Operation Point shall be capable of decoding and rendering Bitstreams with a decoded texture signal of maximum luminance width of 8192 pixels a, maximum luminance height of 8192 pixels and the overall profile/level constraints. + +#### 5.1.5.5 Colour information and Transfer Characteristics + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation Point shall use either Recommendation ITU-R BT.709 [3] colorimetry or Recommendation ITU-R BT.2020 [4] colorimetry in non-constant luminance for standard dynamic range (SDR). + +Specifically, in the VUI, the colour parameter information shall be present, i.e.: + +- `video_signal_type_present_flag` value and `colour_description_present_flag` value shall be set to 1. +- If BT.709 [3] is used, it shall be signalled by setting `colour_primaries` to the value 1, `transfer_characteristics` to the value 1 and `matrix_coeffs` to the value 1. +- If BT.2020 [4] and SDR is used, + - it shall be signalled by setting `colour_primaries` to the value 9, `transfer_characteristics` to the value 14 and `matrix_coeffs` to the value 9; + - the `chroma_loc_info_present_flag` should be equal to 1, and if set, the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +A Receiver conforming to the 3GPP VR Main H.265/HEVC Operation Point shall be capable of decoding and rendering according to any of the two above configurations. + +#### 5.1.5.6 Frame rates + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation Point shall have one of the following frame rates: 24; 25; 30; 24/1001; 30/1001; 50; 60; 60/1001 Hz. + +Selected combinations of frame rates with other source parameters are provided in Annex A.2.2.2. + +In the VUI, the timing information may be present: + +- If the timing information is present, i.e. the value of `vui_timing_info_present_flag` is set to 1, then the values of `vui_num_units_in_tick` and `vui_time_scale` shall be set according to the frame rates allowed in this clause. The timing information present in the video Bitstream should be consistent with the timing information signalled at the system level. +- The frame rate shall not change between two RAPs. `fixed_frame_rate_flag` value, if present, shall be set to 1. + +There are no requirements on output timing conformance for H.265/HEVC decoding (Annex C of [6]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +A Receiver conforming to the 3GPP VR Main H.265/HEVC Operation Point shall be capable of decoding and rendering Bitstreams that use frame rates according to the bitstream requirements documented above. + +#### 5.1.5.7 Random access point + +For H.265/HEVC random access point (RAP) definition refer to TS 26.116 [12], clause 4.5.1.2.1. + +RAPs shall be present in the Bitstream at least once every 5 seconds. It is recommended that RAPs occur in the video Bitstream on average at least every 2 seconds. The time interval between successive RAPs is measured as the difference between their respective decoding time values. + +If viewport adaptation is offered, then RAPs should occur even more frequently to enable transitioning across these viewport-optimized bitstreams. + +#### 5.1.5.8 Video and Sequence Parameter Sets + +Receivers conforming to the 3GPP VR Main H.265/HEVC Operation Point should ignore the content of all Video Parameter Sets (VPS) NAL units as defined in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6]. + +The following restrictions apply to the active Sequence Parameter Set (SPS): + +- The Video Usability Information (VUI) shall be present in the active Sequence Parameter Set. The `vui_parameters_present_flag` shall be set to 1. +- The chroma sub-sampling shall be 4:2:0, `chroma_format_idc` value shall be set to 1. +- The source video format shall be progressive, i.e.: + - The `general_progressive_source_flag` shall be set to 1, + - The `general_interlaced_source_flag` shall be set to 0, + - The `general_frame_only_constraint_flag` shall be set to 1. + +Receivers conforming to the 3GPP VR Main H.265/HEVC Operation Point shall support Bitstreams with the restrictions on the SPS defined above. + +#### 5.1.5.9 Video usability information + +In addition to the previous constraints on the VUI on colour information in clauses 5.1.5.5 and 5.1.5.6, this clause contains further requirements. + +The aspect ratio information shall be present, i.e.: + +- The `aspect_ratio_present_flag` value shall be set to 1. +- The `aspect_ratio_idc` value shall be set to 1 indicating a square pixel format. + +There are no requirements on output timing conformance for H.265/HEVC decoding (Annex C of [6]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +#### 5.1.5.10 Omni-directional Projection Formats + +This operation point permits using either equirectangular projection following the MPEG metadata specifications, such the video is automatically rendered in the 3GPP reference system. + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation Point shall include at every RAP the equirectangular projection SEI message (`payloadType` equal to 150) with the `erp_guard_band_flag` set to 0. + +#### 5.1.5.11 Restricted Coverage + +This operation point permits to distribute content with less than 360 degree coverage in an encoding optimized manner by the use of region-wise packing. + +It is recommended that the number of pixels that are projected to non-covered regions are minimized in the decoded texture signal. If this is applied and not the full 360 video is encoded, the region-wise packing SEI message (`payloadType` equal to 155) shall be included in the bitstream to signal the encoded regions of the 360 video. If present, it shall be present in a H.265/HEVC RAP. + +Application or system-based signalling may support signalling the exact coverage region in the spherical coordinates. + +#### 5.1.5.12 Viewport-Optimized Content + +This operation point permits the use of region-wise packing, for example to optimize the spatial resolution of specific viewports. For some example usage and settings, refer to Annex A.2. + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation Point may include the region-wise packing SEI message (`payloadType` equal to 155). If present, it shall be present in a H.265/HEVC RAP. + +A Receiver conforming to the 3GPP VR Main H.265/HEVC Operation Point shall be able to process the region-wise packing SEI message (`payloadType` equal to 155). + +#### 5.1.5.13 Frame packing arrangement + +A Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation Point may include the frame packing arrangement SEI message (`payloadType` equal to 45). If present, then the following settings shall apply: + +- The SEI message is present in a H.265/HEVC RAP. +- The value of `frame_packing_arrangement_cancel_flag` is equal to 0. +- The value of `frame_packing_arrangement_type` is equal to 4. +- The value of `quincunx_sampling_flag` is equal to 0. +- The value of `spatial_flipping_flag` is equal to 0. +- The value of `field_views_flag` is equal to 0. +- The value of `frame0_grid_position_x` is equal to 0. +- The value of `frame0_grid_position_y` is equal to 0. +- The value of `frame1_grid_position_x` is equal to 0. +- The value of `frame1_grid_position_y` is equal to 0. + +A Receiver conforming to the 3GPP VR Main H.265/HEVC Operation Point shall process the frame packing arrangement SEI (`payloadType` equal to 45) with settings restrictions as above. If processing is supported, then the Receiver shall render the viewport indicated by the message. + +#### 5.1.5.14 Other VR Metadata + +For a Bitstream conforming to the 3GPP VR Main H.265/HEVC Operation Point: + +- the sphere rotation SEI message (`payloadType` equal to 154) shall not be present. +- any frame-packing arrangement SEI message (`payloadType` equal to 45) that does not conform to an SEI message defined in clause 5.1.5.13 shall not be present. + +#### 5.1.5.15 Receiver Compatibility + +Receivers conforming to the 3GPP VR Main H.265/HEVC Operation Point shall support decoding and displaying 3GPP VR Main H.265/HEVC Operation Point Bitstreams. + +Receivers conforming to the 3GPP VR Main H.265/HEVC Operation Point shall support all Receiver requirements in clause 5.1.5. Specifically, receivers conforming to the 3GPP VR Main H.265/HEVC Operation Point shall support decoding and rendering Bitstreams that include the following VR rendering metadata: + +- the region-wise packing SEI message (for details see clauses 5.1.5.11 and 5.1.5.12) +- the equirectangular projection SEI message (for details see clause 5.1.5.10) +- the frame-packing arrangement SEI message (for details see clause 5.1.5.13) +- any combinations of those + +### 5.1.6 Flexible H.265/HEVC + +#### 5.1.6.1 General + +This operation targets enhanced 360 video decoding and rendering of H.265/HEVC video for VR applications. Among others, this operation point supports rendering of: + +- 4K mono video at up to 120 Hz frame rates +- 3K stereoscopic video at up to 60 Hz frame rates +- Higher than 4K resolutions for restricted coverage +- Rendering of certain viewports in higher quality than others beyond 4K +- ERP and CMP projection +- SDR and HDR transfer characteristics + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation point shall conform to the requirements in the remainder of clause 5.1.6. + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation point shall support decoding and rendering a Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation point. Detailed receiver requirements are provided in the remainder of clause 5.1.6. + +#### 5.1.6.2 Profile and level + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation point shall conform to H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6]. + +Hence, for a Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation point shall comply with the following restrictions: + +- The `general_profile_idc` shall be set to 2 indicating the Main10 profile. +- The `general_tier_flag` shall be set to 0 indicating the Main tier. +- The value of `level_idc` shall not be greater than 153 (corresponding to the Level 5.1) and should indicate the lowest level to which the Bitstream conforms. + +#### 5.1.6.3 Bit depth + +Bitstreams conforming to the 3GPP VR Flexible H.265/HEVC Operation point shall be encoded with either 8 or 10 bit precision: + +- `bit_depth_luma_minus8 = 0 or 2` (8 or 10 bits respectively) +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall support 8 bit and 10 bit precision. + +#### 5.1.6.4 Spatial Resolutions + +Due to the options provided in this operation point, additional original format may be considered that can then be decoded and rendered by a Receiver conforming to this operation point. Recommended original formats beyond those specified in clause 5.1.5.4 for equirectangular projection (ERP) are: + +- Mono formats: 8192 × 4096 + +This operation point permits the distribution of ERP signals directly as well as the conversion of ERP signals to cubemap (CMP) projection. A conversion operation is provided in Annex A.2.3. Typical original cubemap format, either generated by conversion or provided by the content provider, that are suitable for this operation point are listed as follows: + +- Mono Formats: 6144x4096, 4608x3072, 4320x2880, 3072x2048, 2880x1920, 2304x1536, 2160x1440 +- Stereo Formats with resolution for each eye: 4320x2880, 3072x2048, 2880x1920, 2304x1536, 2160x1440 + +If original signals are beyond the maximum permitted resolution of the video codec, then region wise packing needs to be applied to generate suitable distribution formats. + +The distribution formats are more flexible as additional VR metadata as defined in the remainder of clause 5.1.6 may be used. However, for the distribution formats, all requirements of H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6] shall apply to the decoded texture signal. + +According to H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 [6], the maximum luminance width and height does not exceed 8,444 pixels. However, for improved interoperability, for a Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation point, the decoded texture signal: + +- shall not exceed the luminance width of 8192 pixels, and +- shall not exceed the luminance height of 8192 pixels. + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall be capable of decoding and rendering Bitstreams with a decoded texture signal of maximum luminance width of 8192 pixels and maximum luminance height of 8192 pixels. + +#### 5.1.6.5 Colour information and Transfer Characteristics + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall use either Recommendation ITU-R BT.709 [3] colorimetry or Recommendation ITU-R BT.2020 [4] colorimetry in non-constant luminance for standard dynamic range (SDR). + +For Perceptual Quantization (PQ) High Dynamic Range (HDR), BT.2020 [4] colorimetry in non-constant luminance and the PQ electro-optical transfer function (EOTF) as defined in Recommendation ITU-R BT.2100 [11] are used. + +For Hybrid Log-Gamma (HLG) High Dynamic Range (HDR), BT.2020 [4] colorimetry in non-constant luminance and the HLG opto-electronic transfer function (OETF) as defined in Recommendation ITU-R BT.2100 [11] are used. + +Specifically, in the VUI, the colour parameter information shall be present, i.e.: + +- `video_signal_type_present_flag` value and `colour_description_present_flag` value shall be set to 1. +- If BT.709 [3] is used, it shall be signalled by setting `colour_primaries` to the value 1, `transfer_characteristics` to the value 1 and `matrix_coeffs` to the value 1. +- If BT.2020 [4] and SDR is used, + - it shall be signalled by setting `colour_primaries` to the value 9, `transfer_characteristics` to the value 14 and `matrix_coeffs` to the value 9, + - the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2 + +- If BT.2020 [4] and ITU-R BT.2100 [11] are used in HDR, + - it shall be signalled by setting `colour_primaries` to the value 9 and `matrix_coeffs` to the value 9, + - the `chroma_loc_info_present_flag` should be equal to 1, and if set, the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2 +- If the PQ EOTF is used, `transfer_characteristics` shall be set to the value 16. + - If the HLG OETF is used, `transfer_characteristics` shall be set to the value 14. The Bitstream shall also contain the `alternative_transfer_characteristics` SEI message. The `alternative_transfer_characteristics` SEI message shall be inserted at each RAP, and its parameter `preferred_transfer_characteristics` shall be set to the value 18. + +NOTE 1: HLG is specified using the `alternative_transfer_characteristics` method only to ensure backwards compatibility with earlier releases at this Operation Point. + +NOTE 2: If the content is provided to a receiver that is not able to process the SEI message, the receiver uses the backward-compatibility mode of HLG to present an SDR representation of the signal. + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall be capable of decoding and rendering according to any of the above configurations. + +SEI messages for HDR metadata signalling may be used. The requirements and recommendations for Bitstreams and Receivers as documented in TS 26.116 [12], clause 4.5.5.7 also apply for the 3GPP VR Flexible H.265/HEVC Operation Point. + +#### 5.1.6.6 Frame rates + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall have one of the following frame rates: 24; 25; 30; 24/1001; 30/1001; 50; 60; 60/1001, 90, 100, 120 Hz. + +Selected combinations of frame rates with other source parameters are provided in Annex A.2.2.2. + +In the VUI, the timing information may be present: + +- If the timing information is present, i.e. the value of `vui_timing_info_present_flag` is set to 1, then the values of `vui_num_units_in_tick` and `vui_time_scale` shall be set according to the frame rates allowed in this clause. The timing information present in the video Bitstream should be consistent with the timing information signalled at the system level. +- The frame rate shall not change between two RAPs. `fixed_frame_rate_flag` value, if present, shall be set to 1. + +There are no requirements on output timing conformance for H.265/HEVC decoding (Annex C of [6]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall be capable of decoding and rendering Bitstreams that use frame rates according to the bitstream requirements documented above. + +#### 5.1.6.7 Random access point + +For H.265/HEVC random access point (RAP) definition refer to TS 26.116 [12], clause 4.5.1.2.1. + +RAPs shall be present in the Bitstream at least once every 5 seconds. It is recommended that RAPs occur in the video Bitstream on average at least every 2 seconds. The time interval between successive RAPs is measured as the difference between their respective decoding time values. + +If viewport adaptation is offered, then RAPs should occur even more frequently to enable transitioning across these viewport-optimized bitstreams. + +#### 5.1.6.8 Video and Sequence Parameter Sets + +Receivers conforming to the 3GPP VR Flexible H.265/HEVC Operation Point should ignore the content of all Video Parameter Sets (VPS) NAL units as defined in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [6]. + +The following restrictions apply to the active Sequence Parameter Set (SPS): + +- The Video Usability Information (VUI) shall be present in the active Sequence Parameter Set. The `vui_parameters_present_flag` shall be set to 1. +- The chroma sub-sampling shall be 4:2:0, `chroma_format_idc` value shall be set to 1. +- The source video format shall be progressive, i.e.: + - The `general_progressive_source_flag` shall be set to 1, + - The `general_interlaced_source_flag` shall be set to 0, + - The `general_frame_only_constraint_flag` shall be set to 1. + +Receivers conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall support Bitstreams with the restrictions on the SPS defined above. + +#### 5.1.6.9 Video usability information + +In addition to the previous constraints on the VUI on colour information in clauses 5.1.6.5 and 5.1.6.6, this clause contains further requirements. + +The aspect ratio information shall be present, i.e.: + +- The `aspect_ratio_present_flag` value shall be set to 1. +- The `aspect_ratio_idc` value shall be set to 1 indicating a square pixel format. + +There are no requirements on output timing conformance for H.265/HEVC decoding (Annex C of [6]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +#### 5.1.6.10 Omni-directional Projection Formats + +This operation point permits using either equirectangular projection or cubemap projection following the MPEG metadata specifications, such the video is automatically rendered in the 3GPP reference system. + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall include at every RAP either: + +- the equirectangular projection SEI message (`payloadType` equal to 150) with the `erp_guard_band_flag` set to 0, or +- the cubemap projection SEI message (`payloadType` equal to 151). + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall be able to process the equirectangular projection SEI message (`payloadType` equal to 150) and the cubemap projection SEI message (`payloadType` equal to 151). + +#### 5.1.6.11 Restricted Coverage + +This operation point permits to distribute content with less than 360 degree coverage in an encoding optimized manner by the use of region-wise packing. + +It is recommended that the number of pixels that are projected to non-covered regions are minimized in the decoded texture signal. If this is applied and not the full 360 video is encoded, the region-wise packing SEI message (`payloadType` equal to 155) shall be included in the bitstream to signal the encoded regions of the 360 video. If present, it shall be present in a H.265/HEVC RAP. + +Application or system-based signalling may support signalling the exact coverage region in the spherical coordinates. + +#### 5.1.6.12 Viewport-Optimized Content + +This operation point permits the use of region-wise packing, for example to optimize the spatial resolution of specific viewports. For some example usage and settings, refer to Annex A.2. + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation Point may include the region-wise packing SEI message (`payloadType` equal to 155). If present, it shall be present in a H.265/HEVC RAP. + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall be able to process the region-wise packing SEI message (`payloadType` equal to 155). + +#### 5.1.6.13 Frame packing arrangement + +A Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation Point may include the frame packing arrangement SEI message (`payloadType` equal to 45). If present, then the following settings shall apply: + +- The SEI message is present in a H.265/HEVC RAP. +- The value of `frame_packing_arrangement_cancel_flag` is equal to 0. +- The value of `frame_packing_arrangement_type` is equal to 4. +- The value of `quincunx_sampling_flag` is equal to 0. +- The value of `spatial_flipping_flag` is equal to 0. +- The value of `field_views_flag` is equal to 0. +- The value of `frame0_grid_position_x` is equal to 0. +- The value of `frame0_grid_position_y` is equal to 0. +- The value of `frame1_grid_position_x` is equal to 0. +- The value of `frame1_grid_position_y` is equal to 0. + +A Receiver conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall process the frame packing arrangement SEI (`payloadType` equal to 45) with settings restrictions as above. If processing is supported, then the Receiver shall render the viewport indicated by the message. + +#### 5.1.6.14 Other VR Metadata + +For a Bitstream conforming to the 3GPP VR Flexible H.265/HEVC Operation Point: + +- the sphere rotation SEI message (`payloadType` equal to 154) shall not be present. +- any frame-packing arrangement SEI message (`payloadType` equal to 45) that does not conform to an SEI message defined in clause 5.1.6.13 shall not be present. + +#### 5.1.6.15 Receiver Compatibility + +Receivers conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall support decoding and displaying 3GPP VR Main H.265/HEVC Operation Point Bitstreams and 3GPP VR Flexible H.265/HEVC Operation Point Bitstreams. + +Receivers conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall support all Receiver requirements in clause 5.1.6. Specifically, receivers conforming to the 3GPP VR Flexible H.265/HEVC Operation Point shall support decoding and rendering Bitstreams that include the following display or VR rendering metadata: + +- the region-wise packing SEI message (for details see clauses 5.1.6.11 and 5.1.6.12), +- the equirectangular projection SEI message (for details see clause 5.1.6.10), +- the cubemap projection SEI message (for details see clause 5.1.6.10), + +- the frame-packing arrangement SEI message (for details see clause 5.1.6.13), +- the `alternative_transfer_characteristics` SEI message with `preferred_transfer_characteristics` set to the value 18 (for details see clause 5.1.6.5), +- any combinations of those. + +### 5.1.7 Main 8K H.265/HEVC + +#### 5.1.7.1 General + +This operation targets enhanced 360 video decoding and rendering of H.265/HEVC video for VR applications. Among others, this operation point supports among others rendering of: + +- 8K mono video at up to 60 Hz frame rates for full coverage +- 6K stereoscopic video at up to 60 Hz frame rates for full coverage +- 4K mono video at up to 120 Hz frame rates for full coverage +- Higher than 8K resolutions for restricted coverage +- Extended colour space, and SDR and HDR transfer characteristics + +A Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation point shall conform to the requirements in the remainder of clause 5.1.7. + +A Receiver conforming to the 3GPP VR Main 8K H.265/HEVC Operation point shall support decoding and rendering a Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation point. Detailed receiver requirements are provided in the remainder of clause 5.1.7. + +#### 5.1.7.2 Profile and level + +A Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation point + +shall conform to H.265/HEVC Main-10 Profile Main Tier Profile Level 6.1 [6], i.e. for a Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation, + +- the `general_profile_idc` shall be set to 2 indicating the Main10 profile. +- the `general_tier_flag` shall be set to 0 indicating the Main tier. +- the value of `level_idc` shall not be greater than 183 (corresponding to the Level 6.1) and should indicate the lowest level to which the Bitstream conforms. +- shall have `general_progressive_source_flag` equal to 1, +- shall have `general_interlaced_source_flag` equal to 0, +- shall have `general_frame_only_constraint_flag` equal to 1 +- shall conform to following further limitations: + - if frame rate 60 fps is used, then the maximum luma picture size in samples of 33,554,432 is not exceeded, + - the maximum VCL Bit Rate is constrained to be 80 Mbps with `CpbVclFactor` and `CpbNalFactor` being fixed to be 1000 and 1100, respectively. + +#### 5.1.7.3 Bit depth + +Bitstreams conforming to the 3GPP VR Main 8K H.265/HEVC Operation point shall be encoded with 10-bit precision: + +- `bit_depth_luma_minus8 = 2` (10 bits) +- `bit_depth_chroma_minus8 = bit_depth_luma_minus8` + +Receivers conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall support 10-bit precision. + +#### 5.1.7.4 Spatial Resolutions + +Due to the options provided in this operation point, additional original format may be considered that can then be decoded and rendered by a Receiver conforming to this operation point. Recommended original formats beyond those specified in clause 5.1.4.3 for equirectangular projection (ERP) are: + +- Mono formats: $8192 \times 4096$ , $7680 \times 3840$ , $6144 \times 3072$ , $5760 \times 2880$ +- Stereo formats with resolution for each eye: $6144 \times 3072$ , $5860 \times 2880$ , $4096 \times 2048$ , $3840 \times 1920$ , $2880 \times 1440$ , $2048 \times 1024$ + +The distribution formats are more flexible as additional VR metadata as defined in the remainder of clause 5.1.7 may be used. However, for the distribution formats, all requirements of H.265/HEVC Main-10 Profile Main Tier Profile Level 6.1 [5] shall apply to the decoded texture signal. + +According to H.265/HEVC Main-10 Profile Main Tier Profile Level 6.1 [6], the maximum luminance width and height does not exceed 16,888 pixels. In addition to the H.265/HEVC Main-10 Profile Main Tier Profile Level 6.1 [6] constraints, a Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation point, the decoded texture signal shall in addition: + +- not exceed the luminance width of 16,384 pixels, and +- not exceed the luminance height of 16,384 pixels. + +A Receiver conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall be capable of decoding and rendering Bitstreams with a decoded texture signal of maximum luminance width of 16,384 pixels, a maximum luminance height of 16,384 pixels and the overall profile/level constraints. + +#### 5.1.7.5 Colour information and Transfer Characteristics + +A Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall use either Recommendation ITU-R BT.709 [3] colorimetry or Recommendation ITU-R BT.2020 [4] colorimetry in non-constant luminance for standard dynamic range (SDR). + +For Perceptual Quantization (PQ) High Dynamic Range (HDR), BT.2020 [4] colorimetry in non-constant luminance and PQ electro-optical transfer function (EOTF) as defined in Recommendation ITU-R BT.2100 [11] are used. + +For Hybrid Log-Gamma (HLG) High Dynamic Range (HDR), BT.2020 [4] colorimetry in non-constant luminance and the HLG opto-electronic transfer function (OETF) as defined in Recommendation ITU-R BT.2100 [11] are used. + +Specifically, in the VUI, the colour parameter information shall be present, i.e.: + +- `video_signal_type_present_flag` value and `colour_description_present_flag` value shall be set to 1. +- If BT.709 [3] is used, it shall be signalled by setting `colour_primaries` to the value 1, `transfer_characteristics` to the value 1 and `matrix_coeffs` to the value 1. +- If BT.2020 [4] and SDR is used, it shall be signalled by setting `colour_primaries` to the value 9, `transfer_characteristics` to the value 14 and `matrix_coeffs` to the value 9, +- the `chroma_loc_info_present_flag` should be equal to 1, and if set the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. +- If BT.2020 [4] and ITU-R BT.2100 [11] are used in HDR, it shall be signalled by setting `colour_primaries` to the value 9 and `matrix_coeffs` to the value 9. The `chroma_sample_loc_type_top_field` shall be set to 2. + +- If the PQ EOTF is used, `transfer_characteristics` shall be set to the value 16. +- If the HLG OETF is used, `transfer_characteristics` shall be set to either the value 18 or 14. In the latter case, the Bitstream shall also contain the `alternative_transfer_characteristics` SEI message. The `alternative_transfer_characteristics` SEI message shall be inserted at each RAP, and its parameter `preferred_transfer_characteristics` shall be set to the value 18. +- the `chroma_loc_info_present_flag` should be equal to 1, and if set, the `chroma_sample_loc_type_top_field` and `chroma_sample_loc_type_bottom_field` shall both be equal to 2. + +A Receiver conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall be capable of decoding and rendering according to any of the above configurations. + +SEI messages for HDR metadata signalling may be used. The requirements and recommendations for Bitstreams and Receivers as documented in TS 26.116 [12], clause 4.5.5.7 also apply for the 3GPP VR Main 8K H.265/HEVC Operation Point. + +#### 5.1.7.6 Frame rates + +A Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall have one of the following frame rates: 24; 25; 30; 24/1001; 30/1001; 50; 60; 60/1001; 90; 100; 120; 120/1001 Hz. + +Selected combinations of frame rates with other source parameters are provided in Annex A.2.2.2a. + +In the VUI, the timing information may be present: + +- If the timing information is present, i.e. the value of `vui_timing_info_present_flag` is set to 1, then the values of `vui_num_units_in_tick` and `vui_time_scale` shall be set according to the frame rates allowed in this clause. The timing information present in the video Bitstream should be consistent with the timing information signalled at the system level. +- The frame rate shall not change between two RAPs. `fixed_frame_rate_flag` value, if present, shall be set to 1. + +There are no requirements on output timing conformance for H.265/HEVC decoding (Annex C of [6]). The Hypothetical Reference Decoder (HRD) parameters, if present, should be ignored by the Receiver. + +A Receiver conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall be capable of decoding and rendering Bitstreams that use frame rates according to the bitstream requirements documented above. + +#### 5.1.7.7 Random access point + +The same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.7 apply. + +#### 5.1.7.8 Video and Sequence Parameter Sets + +Receivers conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall satisfy the same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.8. + +#### 5.1.7.9 Video usability information + +The same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.9 apply. + +#### 5.1.7.10 Omni-directional Projection Formats + +Bitstreams conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall satisfy the same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.10. + +#### 5.1.7.11 Restricted Coverage + +The same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.11 apply. + +However, the region-wise packing SEI message (payloadType equal to 155) shall only be used for restricted coverage signalling (in contrast to 3GPP VR Main H.265/HEVC Operation Point, where region-wise packing SEI message is used for signalling both restricted coverage and viewport-optimized content). + +When the video does not cover the entire sphere, for each picture, there shall be a region-wise packing SEI message present in the bitstream that applies to the picture. Furthermore, the following restrictions apply: + +- `num_packed_regions` shall be set to 1. +- `rwp_guard_band_flag[0]` shall be equal to 0. +- `rwp_transform_type[0]` shall be equal to 0. +- The value of `packed_region_width[0]` shall be equal to `proj_region_width[0]`. +- The value of `packed_region_height[0]` shall be equal to `proj_region_height[0]`. + +#### 5.1.7.12 Frame packing arrangement + +Bitstreams and receivers conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall satisfy the same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.13. + +#### 5.1.7.13 Other VR Metadata + +For a Bitstream conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point: + +- the equirectangular projection SEI message (payloadType equal to 150) with `erp_guard_band_flag` not set to 0 shall not be present, +- the sphere rotation SEI message (payloadType equal to 154) shall not be present. +- the region-wise packing SEI message (payloadType equal to 155) not conforming to the restrictions stated in clause 5.1.7.11 shall not be present. + +#### 5.1.7.14 Receiver Compatibility + +Receivers conforming to the 3GPP VR Main 8K H.265/HEVC Operation Point shall satisfy the same requirements as those defined for 3GPP VR Main H.265/HEVC Operation Point in clause 5.1.5.15. + +## 5.2 Video Media Profiles + +### 5.2.1 Introduction and Overview + +This clause defines the media profiles for video. Media profiles include specification on the following: + +- Elementary stream constraints based on the video operation points defined in clause 5.1. +- File format encapsulation constraints and signalling including capability signalling. This defines a 3GPP VR Track as defined above. +- DASH Adaptation Set constraints and signalling including capability signalling. This defines a DASH content format profile. + +Table 5.2-1 provides an overview of the Media Profiles in defined in the remainder of clause 5.3.2. + +Table 5.2-1 Video Media Profiles + +| Media Profile | Operation Point | Sample Entry | DASH Integration | +|----------------|---------------------------------------------|--------------------|-----------------------------------------------------------------------------------------------------| +| Basic Video | Basic H.264/AVC | resv
avc1 | Single Adaptation Set
Single Representation streaming | +| Main Video | Main H.265/HEVC or
Main 8K
H.265/HEVC | resv
hvc1 | Single or Multiple independent Adaptation Sets
offered
Single Representation streaming | +| Advanced Video | Flexible H.265/HEVC | resv
hvc1, hvc2 | Single or Multiple dependent Adaptation Sets offered
Single or Multiple representation streaming | + +NOTE: Advanced Video Profile Receivers are expected to playback content conforming to the Main Video Media Profile. + +### 5.2.2 Basic Video Media Profile + +#### 5.2.2.1 Overview + +The Basic Video Media Profile permits to download and stream elementary streams for VR content generated according to the H.264/AVC Basic Operation Point as defined in clause 5.1.4. This enables reuse of the `avc1` sample entry as for example also used in the TV Video Profiles in TS 26.116 [12]. It also permits to reuse streaming the VR video content in an adaptive manner by offering multiple switchable Representations in a single Adaptation Set in a DASH MPD. + +For content generation guidelines for this media profile refer to Annex A.2.3. + +#### 5.2.2.2 File Format Signaling and Encapsulation + +3GP VR Tracks conforming to this media profile used in the context of the specification shall conform to ISO BMFF [17] with the following further requirements: + +- The bitstream included on the track shall comply to the Bitstream requirements and recommendations for the Basic H.264/AVC Operation Point as defined in clause 5.1.4. +- The sample entry type of each sample entry of the track shall be equal to 'resv'. +- The `scheme_type` value of `SchemeTypeBox` in the `RestrictedSchemeInfoBox` shall be 'podv', and all instances of `CompatibleSchemeTypeBox` defined in ISO/IEC 23090-2 [13] in the same `RestrictedSchemeInfoBox` shall include at least the `scheme_type` value 'erpv'. +- The untransformed sample entry type shall be equal to 'avc1' as defined in ISO/IEC 14496-15 [9]. + +NOTE: If a file decoder experiences issues in the playback of the VR Track with the restricted sample 'resv', but the application is able to control the rendering according to the VR rendering metadata, then the untransformed sample entry could be used to initialize the decoding process for the file decoder. + +- The Track Header Box ('tkhd') shall obey the following constraints: + - The `width` and `height` fields for a visual track shall specify the track's visual presentation size as fixed-point 16.16 values expressed in on a uniformly sampled grid (commonly called square pixels) (of the decoded texture signal) +- The Video Media Header ('vmhd') shall obey the following constraints: + - The value of the `version` field shall be set to '0'. + - The value of the `graphicsmode` field shall be set to '0'. + - The value of the `opcolor` field shall be set to {'0', '0', '0'}. +- The Sample Description Box ('stsd') obeys the following constraints: + - A visual sample entry shall be used. + +- The box shall include a NAL Structured Video Parameter Set. +- `width` and `height` field shall correspond to the cropped horizontal and vertical sample counts provided in the Sequence Parameter Set of the track. +- It shall contain a Decoder Configuration Record which signals the Profile, Level, and other parameters of the video track. +- It shall contain `AVCConfigurationBox` as defined in ISO/IEC 14496-15 [9] which signals the Profile, Level, Bit depth, and other parameters conforming to the bitstream constraints specified in clause 5.1.4. +- The Colour Information Box ('`colr`') should be present. If present, it shall signal the `colour_primaries`, `transfer_characteristics` and `matrix_coeffs` applicable to all the bitstreams associated with this sample entry. +- The `ProjectionFormatBox` with `projection_type` equal to 0 as defined in ISO/IEC 23090-2 [13] should be present in the sample entry applying to the sample containing the picture. +- It shall not contain the `RegionWisePackingBox` as defined in ISO/IEC 23090-2 [13] and `StereoVideoBox`. +- If the content contained in the Bitstream in the track does not cover the entire sphere, the `CoverageInformationBox` as defined in ISO/IEC 23090-2 [13] should be present. If present, only a single region may be signaled and the following restrictions apply: + - The `coverage_shape_type` shall be set to 1. + - The `num_regions` value shall be set to 1. + - The `view_idc_presence_flag` shall be set to 0. + - The `default_view_idc` shall be set to 0. + +If 3GP VR Tracks conforming to the constraints of this media profile, the '3vrb' ISO brand should be set as a `compatible_brand` in the File Type Box ('`ftyp`'). + +#### 5.2.2.3 DASH Integration + +##### 5.2.2.3.1 Definition + +If all Representations in an Adaptation Set conform to the requirements in clause 5.2.2.3.2 and the Adaptation Set conforms to the requirements in clause 5.2.2.3.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:vrstream:mp:video:basic". + +##### 5.2.2.3.2 Additional Restrictions for DASH Representations + +If a VR Track conforming to this media profile is included in a DASH Representation, the Representation use movie fragments and therefore, the following additional requirements apply: + +- The Media Header Box ('`mdhd`') shall obey the following constraints: + - The value of the `duration` field shall be set to '0'. + - The value of the `duration` field in the Movie Header Box ('`mvhd`') shall be set to a value of '0'. +- The Sample Table Box ('`stbl`') shall obey the following constraints: + - The `entry_count` field of the Sample-to-Chunk Box ('`stsc`') shall be set to '0'. + - Both the `sample_size` and `sample_count` fields of the Sample Size Box ('`stsz`') box shall be set to zero ('0'). The `sample_count` field of the Sample Size Box ('`stz2`') box shall be set to zero ('0'). The actual sample size information can be found in the Track Fragment Run Box ('`trun`') for the track. + +NOTE: This is because the Movie Box ('moov') contains no media samples. + +- The `entry_count` field of the Chunk Offset Box ('stco') shall be set to '0'. +- The Track Header Box ('tkhd') shall obey the following constraints: + - The value of the `duration` field shall be set to '0'. +- Movie Fragment Header Boxes ('mfhd') shall contain `sequence_number` values that are sequentially numbered starting with the number 1 and incrementing by +1, sequenced by movie fragment storage and presentation order. +- Any Segment Index Box ('sidx'), if present, shall obey the additional constraints: + - The `timescale` field shall have the same value as the `timescale` field in the Media Header Box ('mdhd') within the same track; and + - The `reference_ID` field shall be set to the `track_ID` of the ISO Media track as defined in the Track Header Box ('tkhd'). + - The Segment Index shall describe the entire file and only a single Segment Index Box shall be present. + +For all Representation in an Adaptation Set, the following shall apply: + +- The identical coverage information shall be present on all Representations in one Adaptation Set. +- The frame rates of all Representations in one Adaptation Set shall be identical. + +##### 5.2.2.3.3 DASH Adaptation Set Constraints + +For a video Adaptation Set, the following constraints apply: + +- The `@codecs` parameter shall be present on Adaptation Set level and shall signal the maximum required capability to decode any Representation in the Adaptation Set. The `@codecs` parameter should be signalled on the Representation level if different from the one on Adaptation Set level. +- The attributes `@maxWidth` and `@maxHeight` shall be present. They are expected to be used to signal the original projected source content format. This means that they may exceed the actual largest size of any coded Representation in one Adaptation Set. +- The `@width` and `@height` shall be signalled for each Representation (possibly defaulted on Adaptation Set level) and shall match the values of the maximum width and height in the Sample Description box of the contained Representation. +- The Chroma Format may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23001-8 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23001-8 [10]. The values shall match the values set in the VUI. + - The signalling shall be on Adaptation Set level. +- The Colour Primaries and Transfer Function may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics` as defined ISO/IEC 23001-8 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23001-8 [10]. The values shall match the values set in the VUI. + - The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. +- The `@frameRate` should be signalled on Adaptation Set level. + +- Random Access Points shall be signalled by `@startsWithSAP` set to 1 or 2. +- a Supplemental Descriptor should be used to signal the projection by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegI:omaf:2017:pf` as defined ISO/IEC 23090-2 [13] and the `omaf:projection_type` attribute set to 0. +- If the `CoverageInformationBox` is present, a Supplemental Descriptor should be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegI:omaf:2017:cc` as defined ISO/IEC 23090-2 [13] and shall match the information provided in the `CoverageInformationBox`. Specifically, + - the `cc@shape_type` shall be present and be set to 1. + - the `cc@view_idc_presence_flag` shall not be present. + - exactly one `cc.CoverageInfo` element shall be present. + - any `cc.CoverageInfo` attribute that is not `centre_azimuth`, `centre_elevation`, `azimuth_range` and `elevation_range`, shall not be present. + - The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. +- The `FramePacking` element shall not be present. +- The `@profiles` parameters may be present to signal the constraints for the Adaptation Set. + +### 5.2.3 Main Video Media Profile + +#### 5.2.3.1 Overview + +The Main Video Media Profile permits to download and stream elementary streams for VR content generated according to the H.265/HEVC Main Operation Point as defined in clause 5.1.5 or H.265/HEVC Main 8K Operation Point as defined in clause 5.1.7. This enables reuse of the `hvc1` sample entry as for example also used in the TV Video Profiles in TS 26.116 [12]. It also permits to reuse streaming the VR video content in an adaptive manner by offering multiple switchable Representations in a single Adaptation Set in a DASH MPD. Furthermore, this profile enables that multiple Video Adaptation Sets are offered for the same content, each encoded for a preferred viewport. Multiple Viewpoints may be signaled, for example expressing different type of content or different camera positions. + +For content generation guidelines for this media profile refer to Annex A.2.3.2. + +#### 5.2.3.2 File Format Signaling and Encapsulation + +3GP VR Tracks conforming to this media profile used in the context of the specification shall conform to ISO BMFF [17] with the following further requirements: + +- The included in the video track shall comply to the Bitstream requirements and recommendations for the Main.H.265/HEVC Operation Point as defined in clause 5.1.5 or Main.8K H.265/HEVC Operation Point as defined in clause 5.1.7 with the additional constraints + - the region-wise packing SEI message (payloadType equal to 155). if present in any H.265/HEVC RAP, shall be present in any H.265/HEVC RAP and shall be identical for all H.265/HEVC RAP. +- The sample entry type of each sample entry of the track shall be equal to 'resv'. +- The `scheme_type` value of `SchemeTypeBox` in the `RestrictedSchemeInfoBox` shall be 'podv', and all instances of `CompatibleSchemeTypeBox` defined in ISO/IEC 23090-2 [13] in the same `RestrictedSchemeInfoBox` shall include at least one of the `scheme_type` values 'erpv' and 'ercm'. +- The untransformed sample entry type shall be equal to 'hvc1' as defined in ISO/IEC 14496-15 [9]. + +NOTE: If a file decoder experiences issues in the playback of the VR Track with the restricted sample 'resv', but the application is able to control the rendering according to the VR rendering metadata, then the untransformed sample entry could be used to initialize the decoding process for the file decoder. + +- The Track Header Box ('tkhd') shall obey the following constraints: + - The width and height fields for a visual track shall specify the track's visual presentation size as fixed-point 16.16 values expressed in on a uniformly sampled grid (commonly called square pixels) (of the decoded texture signal) +- The Video Media Header ('vmhd') shall obey the following constraints: + - The value of the version field shall be set to '0'. + - The value of the graphicsmode field shall be set to '0'. + - The value of the opcolor field shall be set to {'0', '0', '0'}. +- The Sample Description Box ('stsd') obeys the following constraints: + - A visual sample entry shall be used. + - The box shall include at least one Sequence Parameter Set NAL unit. + - width and height field shall correspond to the cropped horizontal and vertical sample counts provided in the Sequence Parameter Set of the track. + - It shall contain a Decoder Configuration Record which signals the Profile, Level, and other parameters of the video track. +- The Colour Information Box ('colr') should be present. If present, it shall signal the colour\_primaries, transfer\_characteristics and matrix\_coeffs applicable to all the bitstreams associated with this sample entry. +- The ProjectionFormatBox with projection\_type equal to 0 as defined in ISO/IEC 23090-2 [13] shall be present in the sample entry applying to the sample containing the picture. +- If the content contained in the Bitstream in the track does not cover the entire sphere, the CoverageInformationBox as defined in ISO/IEC 23090-2 [13] should be present. If present, only a single region may be signaled and the following restrictions apply: + - The coverage\_shape\_type shall be set to 1, i.e. the sphere region is specified by two azimuth circles and two elevation circles. + - The num\_regions value shall be set to 1. +- The view\_idc\_presence\_flag shall be set to 0. +- The default\_view\_idc shall be set to 0 or 3. +- If the content contained in the Bitstream in the track includes the region-wise packing SEI message (payloadType equal to 155), then the RegionWisePackingBox as defined in ISO/IEC 23090-2 [13] shall be present. It shall signal the same information that is included in the region-wise packing SEI message(s) in the elementary stream. +- If the content contained in the Bitstream in the track does includes the frame packing arrangement SEI message (payloadType equal to 45) in the video stream, the StereoVideoBox shall be present in the sample entry applying to the sample containing the picture. When StereoVideoBox is present, it shall signal the frame packing format that is included in the frame packing arrangement SEI message(s) in the elementary stream. + +If 3GP VR Tracks conforming to the constraints of this media profile, the '3vrm' ISO brand should be set as a compatible\_brand in the File Type Box ('ftyp'). + +#### 5.2.3.3 DASH Integration + +##### 5.2.3.3.1 Definition + +If all Representations in an Adaptation Set conform to the requirements in clause 5.2.3.3.2 and the Adaptation Set conforms to the requirements in clause 5.2.3.3.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:vrstream:mp:video:main". + +Clause 5.2.3.3.4 defines Adaptation Set Ensembles for viewport-optimized offering. + +##### 5.2.3.3.2 Additional Restrictions for DASH Representations + +If a VR Track conforming to this media profile is included in a DASH Representation, the Representation use movie fragments and therefore, the following additional requirements apply: + +- The Media Header Box ('mdhd') shall obey the following constraints: + - The value of the `duration` field shall be set to '0'. + - The value of the `duration` field in the Movie Header Box ('mvhd') shall be set to a value of '0' +- The Sample Table Box ('stbl') shall obey the following constraints: + - The `entry_count` field of the Sample-to-Chunk Box ('stsc') shall be set to '0'. + - Both the `sample_size` and `sample_count` fields of the Sample Size Box ('stsz') box shall be set to zero ('0'). The `sample_count` field of the Sample Size Box ('stz2') box shall be set to zero ('0'). The actual sample size information can be found in the Track Fragment Run Box ('trun') for the track. + +NOTE: This is because the Movie Box ('moov') contains no media samples. + +- The `entry_count` field of the Chunk Offset Box ('stco') shall be set to '0'. +- The Track Header Box ('tkhd') shall obey the following constraints: + - The value of the `duration` field shall be set to '0'. +- Movie Fragment Header Boxes ('mfhd') shall contain `sequence_number` values that are sequentially numbered starting with the number 1 and incrementing by +1, sequenced by movie fragment storage and presentation order. +- Any Segment Index Box ('sidx'), if present, shall obey the additional constraints: + - The `timescale` field shall have the same value as the `timescale` field in the Media Header Box ('mdhd') within the same track; and + - The `reference_ID` field shall be set to the `track_ID` of the ISO Media track as defined in the Track Header Box ('tkhd'). + - The Segment Index shall describe the entire file and only a single Segment Index Box shall be present. + +##### 5.2.3.3.3 DASH Adaptation Set Constraints + +For all Representation in an Adaptation Set, the following shall apply: + +- The identical coverage information shall be present on all Representations in one Adaptation Set, both on ISO BMFF and elementary stream level. +- The frame rates of all Representations in one Adaptation Set shall be identical. +- The identical region-wise packing information shall be present all Representations in one Adaptation Set, both on ISO BMFF and elementary stream level. + +- The identical stereoscopic information shall be present all Representations in one Adaptation Set, both on ISO BMFF and elementary stream level. + +For an Adaptation Set, the following constraints apply: + +- The `@codecs` parameter shall be present on Adaptation Set level and shall signal the maximum required capability to decode any Representation in the Adaptation Set. The `@codecs` parameter should be signalled on the Representation level if different from the one on Adaptation Set level. +- The attributes `@maxWidth` and `@maxHeight` shall be present. They are expected to be used to signal the used format prior to encoding. This means that they may exceed the actual largest size of any coded Representation in one Adaptation Set. +- The `@width` and `@height` shall be signalled for each Representation (possibly defaulted on Adaptation Set level) and shall match the values of the maximum width and height in the Sample Description box of the contained Representation. +- The Chroma Format may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23001-8 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23001-8 [10]. The values shall match the values set in the VUI. + - The signalling shall be on Adaptation Set level. +- The Colour Primaries and Transfer Function may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics` as defined ISO/IEC 23001-8 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23001-8 [10]. The values shall match the values set in the VUI. + - The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. +- The `@frameRate` shall be signalled on Adaptation Set level. +- Random Access Points shall be signalled by `@startsWithSAP` set to 1 or 2. +- A Supplemental Descriptor should be used to signal the projection by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegI:omaf:2017:pf` as defined ISO/IEC 23090-2 [13] and the `omaf:projection_type` attribute set to 0. +- If the `CoverageInformationBox` is present then the Coverage information should be signaled on Adaptation Set. If signalled + - a Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegI:omaf:2017:cc` as defined ISO/IEC 23090-2 [13] and shall match the information provided in the `CoverageInformationBox`. Specifically: + - The `cc@shape_type` shall be present and be set to 1. + - The `cc@view_idc_presence_flag` shall not be present. + - Exactly one `cc.CoverageInfo` element shall be present. + - Any `cc.CoverageInfo` attribute that is not `centre_azimuth`, `centre_elevation`, `azimuth_range` and `elevation_range`, shall not be present. + - The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. + +- If the `StereoVideoBox` is present then the stereo information should be signaled on Adaptation Set. If signaled +- A **FramePacking** descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:VideoFramePackingType` as defined ISO/IEC 23008-1 [10] and the `@value` attribute shall be set to 4. +- The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. + +##### 5.2.3.3.4 Adaptation Set Ensembles for Viewport-Optimized offering + +###### 5.2.3.3.4.1 Introduction + +If multiple Adaptation Sets are offered for the same content in order to permit seamless switching across Representations for a different Viewports, each offered in a different Adaptation Set, then this forms an Ensemble of Adaptation Sets. Note that switching across viewports is not a DASH client functionality, but it is enabled by possible access to the pose and/or viewport information by the DASH client using the 3GPP VR API as shown in Figure 4.6. + +###### 5.2.3.3.4.2 Definition and Adaptation Set Signalling + +An Ensemble is defined as by Adaptation Sets with a **Viewpoint** Descriptor for which the value of the `@schemeIdURI` is prefixed as `urn:3GPP:vrstream:ve` and the actual value is `urn:3GPP:vrstream:ve:` with `` an unsigned integer that is identical for all Adaptation Sets in one Ensemble. By using different ids, multiple ensembles may be defined, each defining a different content (for example different camera angles). The value of `@value` of the descriptor, if present, is either + +- a single unsigned integer value that is different for each Adaptation Set in the Ensemble. If this is present, then the spherical region-wise quality ranking (SRQR) descriptor as defined in ISO/IEC 23090-2 [13] for which the value of the `@schemeIdURI` is prefixed as `urn:mpeg:mpegI:omaf:2017:srqr` shall be present in the each Adaptation Set, or +- a tuple of integer values, separated by a white-spaces. The semantics and order are as follows: + - `centre_azimuth`: Specifies the azimuth of the centre point of the sphere region in units of $2^{-16}$ degrees relative to the 3GPP coordinate system for which this Ensemble has been optimized. + - `centre_elevation`: Specifies the elevation of the centre point of the sphere region in units of $2^{-16}$ degrees relative to the 3GPP coordinate system for which this Ensemble has been optimized. + +the spherical region-wise quality ranking (SRQR) descriptor as defined in ISO/IEC 23090-2 [13] for which the value of the `@schemeIdURI` is prefixed as `urn:mpeg:mpegI:omaf:2017:srqr` may additionally be present for additional information. + +If the `@value` attribute is not present, then this Adaptation Set is not optimized for any Viewport. At most one adaptation set without the `@value` not present shall be present. + +One Adaptation Set of one Ensemble shall be signalled as the main content. Signaling as main content shall be done by using the Role descriptor with `@schemeIdUri="urn:mpeg:dash:role:2011"` and `@value="main"`. If for the main Ensemble an Adaptation Set is present for which the `@value` of the Viewpoint descriptor is not present, then this should be signalled as the main Adaptation Set. + +The content should be offered such that within an Ensemble, if multiple Adaptation Sets with different centre points are signalled, the one is preferred which has the minimum square distance to actual Viewport center. + +###### 5.2.3.3.4.3 Representation Constraints in an Ensemble + +For all Representations in an Ensemble, the following shall apply: + +- The identical coverage information shall be present on all Representations in one Ensemble, both on ISO BMFF and elementary stream level. + +- The frame rates of all Representations in one Ensemble shall be identical. +- The identical stereoscopic information shall be present all Representations in one Ensemble, both on ISO BMFF and elementary stream level. + +###### 5.2.3.3.4.4 Adaptation Set Constraints in an Ensemble + +For all Adaptation Sets in an Ensemble, the following shall apply: + +- The `@codecs` parameter shall be identical for all Adaptation Sets in one Ensemble. +- The Chroma Format shall be identical for all Adaptation Sets in one Ensemble. +- The Color Primaries and Transfer Function shall be identical for all Adaptation Sets in one Ensemble. +- The `@frameRate` shall be identical for all Adaptation Sets in one Ensemble. +- Segments and subsegments shall be aligned, i.e. `@segmentAlignment` or `@subSegmentAlignment` shall be present and shall signal the same unsigned integer value for all Adaptation Sets in an Ensemble. +- Coverage information shall be identical for all Adaptation Sets in one Ensemble. + +### 5.2.4 Advanced Video Media Profile + +#### 5.2.4.1 Overview + +This Profile permits to download and stream elementary streams for VR content generated according to the Flexible H.265/HEVC operation point as defined in clause 5.1.6. It also allows unconstrained use of rectangular region-wise packing and monoscopic and stereoscopic spherical video up to 360 degrees are supported. With the presence of region-wise packing, the resolution or quality of the omnidirectional video could be emphasized in certain regions, e.g., according to the user's viewing orientation. In addition, the untransformed sample entry type 'hvc2' is allowed, making it possible to use extractors and get a conforming HEVC bitstream when tile-based streaming is used. + +#### 5.2.4.2 File Format Signaling and Encapsulation + +3GP VR Tracks conforming to this media profile used in the context of the specification shall conform to ISO BMFF [17] with the following further requirements. + +When a track is the only track in a file, `compatible_brands` containing a brand equal to '3vra' in `FileTypeBox` indicates that the track conforms to this media profile. When a file contains multiple tracks, `compatible_brands` containing a brand equal to '3vra' in `FileTypeBox` indicates that at least one of the tracks conforms to this media profile. + +- The video track shall be indicated to conform to this media profile through one or both of `FileTypeBox` and `TrackTypeBox`. +- At least one sample entry type of each sample entry of the track shall be equal to 'resv'. +- The `scheme_type` value of `SchemeTypeBox` in the `RestrictedSchemeInfoBox` shall be 'podv', and of all instances of `CompatibleSchemeTypeBox` defined in ISO/IEC 23090-2 [13] in the same `RestrictedSchemeInfoBox` shall include at least one of the `scheme_type` values 'erpv' and 'ercm'. +- The untransformed sample entry type shall be equal to 'hvc1' or 'hvc2' as defined in ISO/IEC 14496-15 [9]. + +NOTE: When tile-based streaming is used, each tile is stored as a VR Track with an untransformed sample entry type equal to 'hvc1' and further VR Tracks with an untransformed sample entry type equal to 'hvc2' contain extractors that combine tiles from 'hvc1' VR Tracks leading to a conforming HEVC bitstream. + +- When the untransformed sample entry type is 'hvc2', the track shall include one or more 'scal' track references. + +- LHEVCConfigurationBox as defined in ISO/IEC 14496-15 [9] shall not be present in VisualSampleEntry. +- HEVCConfigurationBox as defined in ISO/IEC 14496-15 [9] in VisualSampleEntry shall be added such that it does not contradict to the Bitstream requirements of the Flexible H.265/HEVC operation point in clause 5.1.6. +- The track\_not\_intended\_for\_presentation\_alone flag of the TrackHeaderBox may be used to indicate that a track is not intended to be presented alone. +- The Track Header Box ('tkhd') shall obey the following constraints: + - The width and height fields for a visual track shall specify the track's visual presentation size as fixed-point 16.16 values expressed in on a uniformly sampled grid (commonly called square pixels) (of the decoded texture signal) +- The Video Media Header ('vmhd') shall obey the following constraints: + - The value of the version field shall be set to '0'. + - The value of the graphicsmode field shall be set to '0'. + - The value of the opcolor field shall be set to {'0', '0', '0'}. +- The Sample Description Box ('stsd') obeys the following constraints: + - A visual sample entry shall be used. + - The box shall include a NAL Structured Video Parameter Set. + - width and height field shall correspond to the cropped horizontal and vertical sample counts provided in the Sequence Parameter Set of the track. + - It shall contain a Decoder Configuration Record which signals the Profile, Level, and other parameters of the video track. +- The Colour Information Box ('colr') should be present. If present, it shall signal the colour\_primaries, transfer\_characteristics and matrix\_coeffs applicable to all the bitstreams associated with this sample entry. +- A ProjectionFormatBox as defined in ISO/IEC 23090-2 [13] shall be present in the sample entry with projection\_type equal to 0 or 1. +- If the content contained in the Bitstream in the track does not cover the entire sphere, the CoverageInformationBox as defined in ISO/IEC 23090-2 [13] should be present. +- If the video content contained in the Bitstream in the track is a subset of the entire video content carried in the file and the CoverageInformationBox as defined in ISO/IEC 23090-2 [13] is present, the following restrictions apply: + - If the equirectangular projection is used then, + - The coverage\_shape\_type shall be set to 1, i.e. the sphere region is specified by two azimuth circles and two elevation circles. + - The num\_regions value shall be set to 1. + - If the cubemap projection is used, then one of the two following options applies: + - a) The coverage\_shape\_type shall be set to 1, i.e. the sphere region is specified by two azimuth circles and two elevation circles and the num\_regions value shall be set to 1, or + - b) The coverage\_shape\_type shall be set to 0, i.e. the sphere region is specified by four great circles. + - The view\_idc\_presence\_flag shall be set to 0. + +- The `default_view_idc` shall be set to 0 or 3. +- If the content contained in the Bitstream in the track includes the region-wise packing SEI message (`payloadType` equal to 155), then the `RegionWisePackingBox` as defined in ISO/IEC 23090-2 [13] shall be present. It shall signal the same information that is included in the region-wise packing SEI message(s) in the elementary stream. +- If the content contained in the Bitstream in the track includes the frame packing arrangement SEI message (`payloadType` equal to 45) in the video stream, the `StereoVideoBox` shall be present in the sample entry applying to the sample containing the picture. When `StereoVideoBox` is present, it shall signal the frame packing format that is included in the frame packing arrangement SEI message(s) in the elementary stream. + +#### 5.2.4.3 DASH Integration + +##### 5.2.4.3.1 Definition + +If all Representations in an Adaptation Set conform to the requirements in clause 5.2.4.3.2 and the Adaptation Set conforms to the requirements in clause 5.2.4.3.3, then the `@profiles` parameter in the Adaptation Set may signal conformance to this Operation Point by using "urn:3GPP:vrstream:mp:video:advanced". + +##### 5.2.4.3.2 Additional Restrictions for DASH Representations + +If a VR Track conforming to this media profile is included in a DASH Representation, the Representation use movie fragments and therefore, the following additional requirements apply: + +- The value of the duration field in the Media Header Box ('`mdhd`') shall be set to a value of '0'. +- The value of the duration field in the Movie Header Box ('`mvhd`') shall be set to a value of '0'. +- The value of the duration field in the Track Header Box ('`tkhd`') shall be set to a value of '0'. +- Movie Fragment Header Boxes ('`mfhd`') may contain `sequence_number` values that are not sequentially numbered. +- Any Segment Index Box ('`sidx`'), if present, shall obey the additional constraints: + - the `timescale` field shall have the same value as the `timescale` field in the Media Header Box ('`mdhd`') within the same track; + - the `reference_ID` field shall be set to the `track_ID` of the ISO Media track as defined in the Track Header Box ('`tkhd`'). +- The Sample Table Box ('`stbl`') shall obey the following constraints: + - The `entry_count` field of the Sample-to-Chunk Box ('`stsc`') shall be set to '0'. + - Both the `sample_size` and `sample_count` fields of the Sample Size Box ('`stsz`') box shall be set to zero ('0'). The `sample_count` field of the Sample Size Box ('`stz2`') box shall be set to zero ('0'). The actual sample size information can be found in the Track Fragment Run Box ('`trun`') for the track. + +NOTE 1: This is because the Movie Box ('`moov`') contains no media samples. + +- The `entry_count` field of the Chunk Offset Box ('`stco`') shall be set to '0'. +- The same projection format shall be used on all Representations in one Adaptation Set. +- The same frame packing format shall be used on all Representations in one Adaptation Set. +- The same coverage information shall be used on all Representations in one Adaptation Set. +- The same spatial resolution shall be used on all Representations in one Adaptation Set. +- When `@dependencyId` is used, the values of profiles of the respective dependent and complementary Representations shall be the same. + +When the MPD contains a Representation with a track for which the untransformed sample entry type is equal to 'hvc2', the following applies: + +- Either the Representations carrying a track conforming to the media profile track constraints with the untransformed sample entry type equal to 'hvc2' shall contain @dependencyId listing all dependent Representations that carry a track conforming to the media profile track constraints with the untransformed sample entry type equal to 'hvc1' or a Preselection property descriptor shall be present and constrained as follows: +- The Main Adaptation Set shall contain a Representation carrying a track conforming to the media profile track constraints with the untransformed sample entry type equal to 'hvc2'. +- The Partial Adaptation Sets shall contain Representations each carrying a track conforming to the media profile track constraints with the untransformed sample entry type equal to 'hvc1'. + +NOTE 2: When using the Preselection property descriptor, the number of Representations for carrying tracks with the untransformed sample entry type equal to 'hvc2' is typically smaller than when using @dependencyId. However, the use of @dependencyId might be needed for encrypted video tracks. + +- The Initialization Segment of the Representation that contains @dependencyId or belongs to the Main Adaptation Set is constrained as follows: +- Tracks conform to the media profile track constraints. +- The track corresponding to the untransformed sample entry type equal to 'hvc2' refers to the tracks indicated in the TrackReferenceBox of the Initialization Segment. + +NOTE 3: When Preselection is used, the sequence\_number integer values are not required to be processed and therefore the concatenation of the Subsegments (of the different Representations of the Adaptation Sets of a Preselection) in any order results in a conforming file. + +NOTE 4: The conforming Segment sequence formed on the basis of the Preselection property descriptor or by resolving @dependencyId attribute(s) as specified in ISO/IEC 23009-1 [18] and the track\_ID value of the track with the untransformed sample entry type equal to 'hvc2' produces the HEVC bitstream which conforms to H.265/HEVC Flexible Operation Point. + +When switching or accessing Representations at each segment or subsegment is relevant, the following DASH profiles include sufficient constraints: + +- ISO Base Media File Format Live profile: urn:mpeg:dash:profile:isoff-live:2011 +- ISO Base Media File Format Main profile: urn:mpeg:dash:profile:isoff-main:2011 + +When low latency considerations are relevant, the following DASH profiles provide tools to support efficient low latency services: + +- ISO Base Media File Format On Demand profile: urn:mpeg:dash:profile:isoff-on-demand:2011 +- ISO Base Media File Format Broadcast TV profile: urn:mpeg:dash:profile:isoff-broadcast:2015 + +##### 5.2.4.3.3 DASH Adaptation Set Constraints + +For all Representation in an Adaptation Set, the following shall apply: + +- The identical coverage information shall be present on all Representations in one Adaptation Set, both on ISO BMFF and elementary stream level. +- The frame rates of all Representations in one Adaptation Set shall be identical. +- The identical region-wise packing information shall be present all Representations in one Adaptation Set, both on ISO BMFF and elementary stream level. + +- The identical stereoscopic information shall be present all Representations in one Adaptation Set, both on ISO BMFF and elementary stream level. + +For an Adaptation Set, the following constraints apply: + +- The `@codecs` parameter shall be present on Adaptation Set level and shall signal the maximum required capability to decode any Representation in the Adaptation Set. The `@codecs` parameter should be signalled on the Representation level if different from the one on Adaptation Set level. +- The attributes `@maxWidth` and `@maxHeight` shall be present. They are expected to be used to signal the decoded texture format of the original signal. This means that they may exceed the actual largest size of any coded Representation in one Adaptation Set. +- The `@width` and `@height` shall be signalled for each Representation (possibly defaulted on Adaptation Set level) and shall match the values of the maximum width and height in the Sample Description box of the contained Representation. +- The Chroma Format may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:MatrixCoefficients` as defined ISO/IEC 23001-8 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23001-8 [10]. The values shall match the values set in the VUI. + - The signalling shall be on Adaptation Set level. +- The Colour Primaries and Transfer Function may be signalled. If signalled: + - An Essential or Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegB:cicp:ColourPrimaries` and `urn:mpeg:mpegB:cicp:TransferCharacteristics` as defined ISO/IEC 23001-8 [10] and the `@value` attribute according to Table 4 of ISO/IEC 23001-8 [10]. The values shall match the values set in the VUI. + +The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. + +- The `@frameRate` shall be signalled on Adaptation Set level. +- Random Access Points shall be signalled by `@startsWithSAP` set to 1 or 2. +- An Essential Descriptor shall be used to signal the projection by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegI:omaf:2017:pf` as defined ISO/IEC 23090-2 [13] and the `omaf:@projection_type` attribute set to 0 or 1. +- If the `CoverageInformationBox` is present, then the Coverage information should be signaled on Adaptation Set. If signalled: + - A Supplemental Descriptor shall be used to signal the value by setting the `@schemeIdURI` attribute to `urn:mpeg:mpegI:omaf:2017:cc` as defined ISO/IEC 23090-2 [13] and shall match the information provided in the `CoverageInformationBox`. Specifically, + - the `cc@shape_type` shall be present and be set to 0 or 1. + - the `cc@view_idc_presence_flag` shall not be present. + - exactly one `cc.CoverageInfo` element shall be present. + - any `cc.CoverageInfo` attribute that is not `centre_azimuth`, `centre_elevation`, `azimuth_range` and `elevation_range`, shall not be present. + - The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. +- If the `StereoVideoBox` is present, then the stereo information should be signaled on Adaptation Set. If signalled: + +- a FramePacking descriptor shall be used to signal the value by setting the @schemeIdURI attribute to urn:mpeg:mpegB:cicp:VideoFramePackingType as defined ISO/IEC 23008-1 [10] and the @value attribute shall be set to 4. +- The signalling shall be on Adaptation Set level only, i.e. the value shall not be different for different Representations in one Adaptation Set. +- The following applies for the use of @mimeTypes: + - @mimeTypes of the Main Adaptation Set shall include the profiles parameter '3vra'. + - When Preselection is used, the value of profiles of the main Adaptation Set shall be the same as the value of profiles of its partial Adaptation Sets. +- When Preselection is used, the following applies: + - The value of @subsegmentAlignment in the Main Adaptation Set shall be an unsigned integer and equal to the value of @subsegmentAlignment of the each associated Partial Adaptation Set. + - The value of @segmentAlignment in the Main Adaptation Set shall be an unsigned integer and equal to the value of @segmentAlignment of the each associated Partial Adaptation Set. + +##### 5.2.4.3.4 Adaptation Set Constraints for Viewport Selection + +If multiple Adaptation Sets are offered for the same content which have emphasized quality regions for different viewports, in order to provide signaling information for switching across Viewports, the spherical region-wise quality ranking (SRQR) descriptor as defined in ISO/IEC 23090-2 [13] for which the value of the @schemeIdURI is prefixed as urn:mpeg:mpegI:omaf:2017:srqr shall be present in the each Adaptation Set with following restrictions: + +- The **sphRegionQuality**@view\_idc\_presence\_flag shall be set to 0. +- The **sphRegionQuality**@default\_view\_idc shall be set to 0 or 3. +- The value of **sphRegionQuality11.qualityInfo**@quality\_ranking shall be greater than 0. + +For all Representations in multiple Adaptation Sets for switching across Viewports, the following shall apply: + +- The identical coverage information shall be present on all Representations, both on ISO BMFF and elementary stream level. +- The frame rates of all Representations in Adaptation Sets shall be identical. +- The identical stereoscopic information shall be present all Representations, both on ISO BMFF and elementary stream level. + +For all Adaptation Sets with SRQR descriptors for switching across Viewports, the following shall apply: + +- The @codecs parameter shall be identical for all Adaptation Sets. +- The Chroma Format shall be identical for all Adaptation Sets. +- The Colour Primaries and Transfer Function shall be identical for all Adaptation Sets. +- The @frameRate shall be identical for all Adaptation Sets. +- Segments and subsegments shall be aligned, i.e. @segmentAlignment or @subSegmentAlignment shall be present and shall signal the same unsigned integer value for all Adaptation Sets. +- Coverage information shall be identical for all Adaptation Sets. + +# 6 Audio + +## 6.1 Audio Operation Points + +### 6.1.1 Definition of Operation Point + +For the purpose to define interfaces to a conforming audio decoder, audio operation points are defined. In this case the following definitions hold: + +- **Operation Point:** A collection of discrete combinations of different content formats and VR specific rendering metadata, etc. and the encoding format. +- **Receiver:** A receiver that can decode and render any bitstream that is conforming to a certain Operation Point. +- **Bitstream:** A audio bitstream that conforms to an audio format. + +![Figure 6.1-1: Audio Operation Points. A block diagram showing the flow of audio data from an MPD/Segment through an Access Engine, then through a File Decoder (containing a File Parser and Media Decoder), and finally to an Audio Renderer for Audio Presentation. The diagram also shows control signals from a VR Application and a Sensor to the Access Engine and Audio Renderer respectively, mediated by the 3GPP VR API. Red vertical lines indicate the boundaries for the 3GPP VR DASH Profile, 3GPP VR Media Profile, and 3GPP VR OP.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +The diagram illustrates the audio processing pipeline. On the left, 'MPD' and 'Segment' inputs enter an 'Access Engine' (green box). A red vertical line labeled '3GPP VR DASH Profile' is positioned before the Access Engine. The output of the Access Engine is a '3GPP VR Track'. This track enters a 'File Decoder' (yellow box), which contains a 'File Parser' and a 'Media Decoder'. Two red vertical lines labeled '3GPP VR Media Profile' and '3GPP VR OP' are positioned within the File Decoder. The output of the Media Decoder consists of 'Decoded Signals' and 'Rendering Metadata', which are sent to an 'Audio Renderer' (purple box). The Audio Renderer produces the final 'Audio Presentation'. Below the main flow, a 'VR Application' (grey box) and a 'Sensor' (orange box) are shown. The VR Application sends 'Static and Dynamic Configuration and Control' to the Access Engine. The Sensor sends 'Pose' information to the Audio Renderer. Both the VR Application and the Sensor are connected to a central '3GPP VR API' (green line). + +Figure 6.1-1: Audio Operation Points. A block diagram showing the flow of audio data from an MPD/Segment through an Access Engine, then through a File Decoder (containing a File Parser and Media Decoder), and finally to an Audio Renderer for Audio Presentation. The diagram also shows control signals from a VR Application and a Sensor to the Access Engine and Audio Renderer respectively, mediated by the 3GPP VR API. Red vertical lines indicate the boundaries for the 3GPP VR DASH Profile, 3GPP VR Media Profile, and 3GPP VR OP. + +Figure 6.1-1: Audio Operation Points + +This clause focuses on the interoperability point to a media decoder as indicated in Figure 6.1-1. This clause does not deal with the access engine and file parser which addresses aspects how the audio bitstream is delivered. + +In all audio operation points, the VR Presentation can be rendered using a single media decoder which provides decoded PCM signals and rendering metadata to the audio renderer. + +### 6.1.2 Parameters of Audio Operation Point + +This clause defines the potential parameters of Audio Operation Points. This includes the detailed audio decoder requirements and audio rendering metadata. The requirements are defined from the perspective of the audio decoder and renderer. + +Parameters for an Audio Operation Point include: + +- the audio decoder that the bitstream needs to conform to, +- the mandated or permitted rendering data that is included in the audio bitstream. + +### 6.1.3 Summary of Audio Operation Points + +Table 6.1-1 provides an informative overview of the Audio Operating Points. The detailed, normative specification for each audio operating point is subsequently provided in the referenced clause. + +**Table 6.1-1: Overview of OMAF operation points for audio (informative)** + +| Operation Point | Codec | Configuration | | Max Sampling Rate | Clause | +|-------------------|--------------|-----------------------------------------|--|-------------------|--------| +| 3GPP MPEG-H Audio | MPEG-H Audio | Low Complexity Profile, Level 1, 2 or 3 | | 48 kHz | 6.1.4 | + +### 6.1.4 3GPP MPEG-H Audio Operation Point + +#### 6.1.4.1 Overview + +The 3GPP MPEG-H Audio Operation Point fulfills the requirements to support 3D audio and is specified in ISO/IEC 23090-2 [13], clause 10.2.2. Channels, Objects and First/Higher-Order Ambisonics (FOA/HOA) are supported, as well as combinations of those. The Operation Point is based on MPEG-H 3D Audio [19]. + +A bitstream conforming to the 3GPP MPEG-H Audio Operation Point shall conform to the requirements in clause 6.1.4.2. + +A receiver conforming to the 3GPP MPEG-H Audio Operation Point shall support decoding and rendering a Bitstream conforming to the 3GPP MPEG-H Audio Operation Point. Detailed receiver requirements are provided in clause 6.1.4.3. + +#### 6.1.4.2 Bitstream requirements + +The audio stream shall comply with the MPEG-H 3D Audio Low Complexity (LC) Profile, Levels 1, 2 or 3 as defined in ISO/IEC 23008-3, clause 4.8 [19]. The values of the `mpegh3daProfileLevelIndication` for LC Profile Levels 1, 2 and 3 are "0x0B", "0x0C" and "0x0D", respectively, as specified in ISO/IEC 23008-3 [19], clause 5.3.2. + +Audio encapsulation shall be done according to ISO/IEC 23090-2 [12], clause 10.2.2.2. + +All Low Complexity Profile and Levels restrictions specified in ISO/IEC 23008-3 [19], clause 4.8.2 shall apply. The constraints on input and output configurations are provided in *Table 3 — "Levels and their corresponding restrictions for the Low Complexity Profile"*, of ISO/IEC 23008-3 [19]. This includes the following for Low Complexity Profile Level 3: + +- Maximum number of core coded channels (in compressed data stream): 32, +- Maximum number of decoder processed core channels: 16, +- Maximum number of loudspeaker output channels: 12 +- Maximum number of decoded objects: 16 +- Maximum HOA order: 6 + +MPEG-H Audio sync samples contain Immediate Playout Frames (IPFs), as specified in ISO/IEC 23008-3, clause 20.2 [19] and shall follow the requirements specified in ISO/IEC 23090-2 [12], clause 10.2.2.3.1. + +#### 6.1.4.3 Receiver requirements + +##### 6.1.4.3.1 General + +A receiver supporting the 3GPP MPEG-H Audio Operation Point shall fulfill all requirements specified in the remainder of clause 6.1.4.3. + +##### 6.1.4.3.2 Decoding process + +The receiver shall be capable of decoding MPEG-H Audio LC Profile Level 1, Level 2 and Level 3 bitstreams as specified in ISO/IEC 23008-3, clause 4.8 [19] with the following relaxations: + +- The Immersive Renderer defined in ISO/IEC 23008-3 [19], clause 11 is optional. +- The carriage of generic data defined in ISO/IEC 23008-3 [19], clause 14.7 is optional and thus MHAS packets of the type PACTYP\_GENDATA are optional and the decoder may ignore packets of this type. + +The decoder shall read and process MHAS packets of the following types in accordance with ISO/IEC 23008-3 [19], clause 14: + +PACTYP\_SYNC, +PACTYP\_MPEGH3DACFG, +PACTYP\_AUDIOSCENEINFO, +PACTYP\_AUDIOTRUNCATION, +PACTYP\_MPEGH3DAFRAME, +PACTYP\_USERINTERACTION, +PACTYP\_LOUDNESS\_DRC, +PACTYP\_EARCON, +PACTYP\_PCMCONFIG, and +PACTYP\_PCMDATA. + +The decoder may read and process MHAS packets of the following types: + +PACTYP\_SYNC GAP, +PACTYP\_BUFFERINFO, +PACTYP\_MARKER and +PACTYP\_DESCRIPTOR. + +Other MHAS packets may be present in an MHAS elementary stream, but may be ignored. + +The Earcon metadata shall be processed and applied as described in ISO/IEC 23008-3 [19], clause 28. + +##### 6.1.4.3.3 Random Access + +The audio decoder is able to start decoding a new audio stream at every random access point (RAP). As defined in clause 6.1.4.2, the sync sample (RAP) contains the configuration information (PACTYP\_MPEGH3DACFG and PACTYP\_AUDIOSCENEINFO) that is used to initialize the audio decoder. After initialization, the audio decoder reads encoded audio frames (PACTYP\_MPEGH3DAFRAME) and decodes them. + +To optimize startup delay at random access, the information from the MHAS PACTYP\_BUFFERINFO packet should be taken into account. The input buffer should be filled at least to the state indicated in the MHAS PACTYP\_BUFFERINFO packet before starting to decode audio frames. + +NOTE 1: It may be necessary to feed several audio frames into the decoder before the first decoded PCM output buffer is available, as described in ISO/IEC 23008-3 [19], clause 5.5.6.3 and clause 22. + +It is recommended that, at random access into an audio stream, the receiving device performs a 100 ms fade-in on the first PCM output buffer that it receives from the audio decoder. + +NOTE 2: The MPEG-H 3D Audio Codec can output the original input samples without any inherent fade-in behavior. Thus, the receiving device needs to appropriately handle potential signal discontinuities, resulting from the original input signal, by fading in at random access into an audio stream. + +##### 6.1.4.3.4 Configuration change + +If the decoder receives an MHAS stream that contains a configuration change, the decoder shall perform a configuration change according to ISO/IEC 23008-3 [19], clause 5.5.6. The configuration change can, for instance, be detected through the change of the MHASPacketLabel of the packet PACTYP\_MPEGH3DACFG compared to the value of the MHASPacketLabel of previous MHAS packets. + +If MHAS packets of type PACTYP\_AUDIOTRUNCATION are present, they shall be used as described in ISO/IEC 23008-3 [19], clause 14. + +The Access Unit that contains the configuration change and the last Access Unit before the configuration change may contain a truncation message (PACTYP\_AUDIOTRUNCATION) as defined in ISO/IEC 23008-3 [19], clause 14. The MHAS packet of type PACTYP\_AUDIOTRUNCATION enables synchronization between video and audio elementary streams at program boundaries. When used, sample-accurate splicing and reconfiguration of the audio stream are possible. + +##### 6.1.4.3.5 MPEG-H Multi-stream Audio + +The receiver shall be capable of simultaneously receiving at least 3 MHAS streams. The MHAS streams can be simultaneously decoded or combined into a single stream prior to the decoder, by utilizing the field `mae_bsMetaDataElementIDoffset` in the Audio Scene Information as described in ISO/IEC 23008-3 [19], clause 14.6. + +##### 6.1.4.3.6 Rendering requirements + +###### 6.1.4.3.6.1 General + +The 3GPP MPEG-H Audio Operation Point builds on the MPEG-H 3D Audio codec, which includes rendering to loudspeakers, binaural rendering and also provides an interface for external rendering. Legacy binaural rendering using fixed loudspeaker setups can be supported by using loudspeaker feeds as output of the decoder. + +###### 6.1.4.3.6.2 Rendering to Loudspeakers + +Rendering to loudspeakers shall be done according to ISO/IEC 23008-3 [19] using the interface for local loudspeaker setup and rendering as defined in ISO/IEC 23008-3 [19], clause 17.3. + +NOTE: ISO/IEC 23008-3 [19] specifies rendering to predefined loudspeaker setups as well as rendering to arbitrary setups. + +###### 6.1.4.3.6.3 Binaural Rendering of MPEG-H 3D Audio + +###### 6.1.4.3.6.3.1 General + +MPEG-H 3D Audio specifies methods for binauralizing the presentation of immersive content for playback via headphones, as is needed for omnidirectional media presentations. MPEG-H 3D Audio specifies a normative interface for the user's viewing orientation and permits low-complexity, low-latency rendering of the audio scene to any user orientation. + +The binaural rendering of MPEG-H 3D Audio shall be applied as described in ISO/IEC 23008-3 [19], clause 13 according to the Low Complexity Profile and Levels restrictions for binaural rendering specified in ISO/IEC 23008-3 [19], clause 4.8.2.2. + +###### 6.1.4.3.6.3.2 Head Tracking Interface + +For binaural rendering using head tracking the `useTrackingMode` flag in the `BinauralRendering()` syntax element shall be set to 1, as described in ISO/IEC 23008-3 [19], clause 17.4. This flag defines if a tracker device is connected and the binaural rendering shall be processed in a special headtracking mode, using the scene displacement values (yaw, pitch and roll). + +The values for the scene displacement data shall be sent using the interface for scene displacement data specified in ISO/IEC 23008-3 [19], clause 17.9. The syntax of `mpegH3daSceneDisplacementData()` interface provided in ISO/IEC 23008-3 [19], clause 17.9.3 shall be used. + +###### 6.1.4.3.6.3.3 Signaling and processing of diegetic and non-diegetic audio + +The metadata flag `fixedPosition` in `SignalGroupInformation()` indicates if the corresponding audio signals are updated during the processing of scene-displacement angles. In case the flag is equal to one, the positions of the corresponding audio signals are not updated during the processing of scene displacement angles. + +Channel groups for which the flag `gca_directHeadphone` is set to "1" in the `mpegH3da_getChannelMetadata()` syntax element are routed to left and right output channel directly and are excluded from binaural rendering using scene displacement data (non-diegetic content). Non-diegetic content may + +have stereo or mono format. For mono, the signal is mixed to left and right headphone channel with a gain factor of 0.707. + +###### 6.1.4.3.6.3.4 HRIR/BRIR Interface processing + +The interface for binaural room impulse responses (BRIRs) specified in ISO/IEC 23008-3 [19], clause 17.4 shall be used for external BRIRs and HRIRs. The HRIR/BRIR data for the binaural rendering can be fed to the decoder by using the syntax element `BinauralRendering()`. The number of BRIR/HRIR pairs in each BRIR/HRIR set shall correspond to the number indicated in the relevant level-dependent row in Table 9 - *"The binaural restrictions for the LC profile"* of ISO/IEC 23008-3 [19] according to the Low Complexity Profile and Levels restrictions in ISO/IEC 23008-3 [19], clause 4.8.2.2. + +The measured BRIR positions are passed to the `mppeg3daLocalSetupInformation()`, as specified in ISO/IEC 23008-3 [19], clause 4.8.2.2. Thus, all renderer stages are set to the target layout that is equal to the transmitted channel configuration. As one BRIR is available per regular input channel, the Format Converter can be passed through in case regular input channel positions are used. Preferably, the BRIR measurement positions for standard target layouts 2.0, 5.1, 10.2 and 7.1.4 should be provided. + +###### 6.1.4.3.6.4 Rendering with External Binaural Renderer + +MPEG-H 3DA provides the output interfaces for the delivery of un-rendered channels, objects, and HOA content and associated metadata as specified in clause 6.1.4.3.6.5. External binaural renderers can connect to this interface e.g. for playback of head-tracked audio via headphones. An example of such external binaural renderer that connects to the external rendering interface of MPEG-H 3DA is specified in Annex B. + +###### 6.1.4.3.6.5 External Renderer Interface + +ISO/IEC 23008-3 [19], clause 17.10 specifies the output interfaces for the delivery of un-rendered channels, objects, and HOA content and associated metadata. For connecting to external renderers, a receiver shall implement the interfaces for object output, channel output and HOA output as specified in ISO/IEC 23008-3 [19], clause 17.10, including the additional specification of production metadata defined in ISO/IEC 23008-3 [19], clause 27. Any external renderer should apply the metadata provided in this interface and related audio data in the same manner as if MPEG-H internal rendering is applied: + +- Correct handling of loudness-related metadata in particular with the aim of preserving intended target loudness +- Preserving artistic intent, such as applying transmitted Downmix and HOA Rendering matrices correctly +- Rendering spatial attributes of objects appropriately (position, spatial extent, etc.) + +NOTE: The external example binaural renderer in Annex B only handles a subset of the parameters to illustrate the use of the output interface. Alternative external binaural renderers are expected to apply and handle the metadata provided in this interface and related audio data in the same manner as if internal rendering is applied. + +In this interface the PCM data of the channels and objects interfaces is provided through the decoder PCM buffer, which first contains the regular rendered PCM signals (e.g. 12 signals for a 7.1+4 setup). Subsequently $n_{\text{chan. out}}$ additional signals carry the PCM data of the originally transmitted channel representation. These are followed by $n_{\text{obj. ou}}$ signals carrying the PCM data of the un-rendered output objects. Then additional signals carry the $n_{\text{HOA. out}}$ HOA audio PCM data which number is indicated in the HOA metadata interface via the HOA order (e.g. 16 signals for HOA order 3). The HOA audio PCM data in the HOA output interface is provided in the so-called Equivalent Spatial Domain (ESD) representation. The conversion from the HOA domain into the ESD representation and vice versa is described in ISO/IEC 23008-3 [19], Annex C.5.1. + +The metadata for channels, objects, and HOA is available once per frame and their syntax is specified in `mppeg3da_getChannelMetadata()`, `mppeg3da_getObjectAudioAndMetadata()`, and `mppeg3da_getHoaMetadata()` respectively. The metadata and PCM data shall be aligned for an external renderer to match each metadata element with the respective PCM frame. + +## 6.2 Audio Media Profiles + +### 6.2.1 Introduction and Overview + +This clause defines the media profiles for audio. Media profiles include specification on the following: + +- Elementary stream constraints based on the audio operation points defined in clause 6.1. +- File format encapsulation constraints and signalling including capability signalling. This defines a 3GPP VR Track as defined above. +- DASH Adaptation Set constraints and signalling including capability signalling. This defines a DASH content format profile. + +Table 6.2-1 provides an overview of the Media Profiles in defined in the remainder of clause 6.2. + +**Table 6.2-1 Audio Media Profiles** + +| Media Profile | Operation Point | Sample Entry | DASH Integration | +|--------------------------------------|-----------------------------------|--------------|------------------| +| OMAF 3D Audio Baseline Media Profile | 3GPP MPEG-H Audio Operation Point | mhm1
mhm2 | | + +### 6.2.2 OMAF 3D Audio Baseline Media Profile + +#### 6.2.2.1 Overview + +MPEG-H 3D Audio [19] specifies coding of immersive audio material and the storage of the coded representation in an ISO BMFF track. The MPEG-H 3D Audio decoder has a constant latency, see *Table 1 — "MPEG-H 3DA functional blocks and internal processing domain"*, of ISO/IEC 23008-3 [19]. With this information, content authors could synchronize audio and video portions of a media presentation, e.g. ensuring lip-synch. + +ISO BMFF integration for this profile is provided following the requirements and recommendations in ISO/IEC 23090-2 [12], clause 10.2.2.3. + +#### 6.2.2.2 File Format Signaling and Encapsulation + +##### 6.2.2.2.1 General + +3GP VR Tracks conforming to this media profile used in the context of the specification shall conform to the ISO BMFF [17] with the following further requirements: + +- The audio track shall comply to the Bitstream requirements and recommendations for the Operation Point as defined in clause 6.1.4. +- The sample entry 'mhm1' shall be used for encapsulation of MHAS packets into ISO BMFF files, per ISO/IEC 23008-3 [19], clause 20.6. +- All ISO Base Media File Format constraints specified in ISO/IEC 23090-2 [12], clause 10.2.2.3 shall apply. +- ISO BMFF Tracks shall be encoded following the requirements in ISO/IEC 23090-2 [12], clause 10.2.2.3.1. + +##### 6.2.2.2.2 Configuration change constraints + +A configuration change takes place in an audio stream when the content setup or the Audio Scene Information changes (e.g., when changes occur in the channel layout, the number of objects etc.), and therefore new PACTYP\_MPEGH3DACFG and PACTYP\_AUDIOSCENEINFO packets are required upon such occurrences. A configuration change usually happens at program boundaries, but it may also occur within a program. + +Configuration change constraints specified in ISO/IEC 23090-2 [12], clause 10.2.2.3.2 shall apply. + +#### 6.2.2.3 Multi-stream constraints + +The multi-stream-enabled MPEG-H Audio System is capable of handling Audio Programme Components delivered in several different elementary streams (e.g., the main MHAS stream containing one complete audio main, and one or more auxiliary MHAS streams, containing different languages and audio descriptions). The MPEG-H Audio Metadata information (MAE) allows the MPEG-H Audio Decoder to correctly decode several MHAS streams. + +The sample entry 'mhm2' shall be used in cases of multi-stream delivery, i.e., the MPEG-H Audio Scene is split into two or more streams for delivery as described in ISO/IEC 23008-3 [19], clause 14.6. All constraints for file formats using the sample entry 'mhm2' specified in ISO/IEC 23090-2 [12], clause 10.2.2.3.3 shall apply. + +#### 6.2.2.3a Additional Restrictions for DASH Representations + +DASH Integration is provided following the requirements and recommendations in ISO/IEC 23090-2 [12], clause B.2.1. All constraints in ISO/IEC 23090-2 [12], clause B.2.1 shall apply. + +#### 6.2.2.4 DASH Adaptation Set Constraints + +##### 6.2.2.4.1 General + +An instantiation of an OMAF 3D Audio Baseline Profile in DASH should be represented as one Adaptation Set. If so the Adaptation Set should provide the following signalling according to ISO/IEC 23090-2 [12] and ISO/IEC 23008-3 [19], clause 21 as shown in Table 6.2-2. + +**Table 6.2-2: MPEG-H Audio MIME parameter according to RFC 6381 and ISO/IEC 23008-3** + +| Codec | MIME type | codecs parameter | profiles | ISO BMFF Encapsulation | +|-----------------------------------------------|-----------|------------------|----------|------------------------| +| MPEG-H Audio LC Profile Level 1 | audio/mp4 | mhm1.0x0B | 'oabl' | ISO/IEC 23008-3 | +| MPEG-H Audio LC Profile Level 2 | audio/mp4 | mhm1.0x0C | 'oabl' | ISO/IEC 23008-3 | +| MPEG-H Audio LC Profile Level 3 | audio/mp4 | mhm1.0x0D | 'oabl' | ISO/IEC 23008-3 | +| MPEG-H Audio LC Profile Level 1, multi-stream | audio/mp4 | mhm2.0x0B | 'oabl' | ISO/IEC 23008-3 | +| MPEG-H Audio LC Profile Level 2, multi-stream | audio/mp4 | mhm2.0x0C | 'oabl' | ISO/IEC 23008-3 | +| MPEG-H Audio LC Profile Level 3, multi-stream | audio/mp4 | mhm2.0x0D | 'oabl' | ISO/IEC 23008-3 | + +Mapping of relevant MPD elements and attributes to MPEG-H Audio as well as the Preselection Element and Preselection descriptor are specified in ISO/IEC 23090-2 [12], clause B.2.1.2. + +##### 6.2.2.4.2 DASH Adaptive Bitrate Switching + +MPEG-H 3D Audio enables seamless bitrate switching in a DASH environment with different Representations (i.e., bit streams encoded at different bitrates) of the same content, i.e., those Representations are part of the same Adaptation Set. + +If the decoder receives a DASH Segment of another Representation of the same Adaptation Set, the decoder shall perform an adaptive switch according to ISO/IEC 23008-3 [19], clause 5.5.6. + +# 7 Metadata + +## 7.1 Presentation without Pose Information to 2D Screens + +In several devices, the VR sensor providing pose information may not be available or may be disabled by the user and the presentation of the VR360 presentation is on a 2D screen. In this case, the receiver needs to rely on other information to determine a proper rendering of the VR360 presentation that is to be presented at a specific media time. + +For this purpose, a VR Media Presentation may include the recommended viewport metadata. The recommended viewport metadata may be encapsulated in a timed metadata track in either a file or a DASH representation. + +Receivers presenting on a 2D screen and not implementing a viewport sensor should implement the recommended viewport processing to process the recommended viewport metadata and to render VR video or audio accordingly. + +Receivers implementing a viewport sensor may implement the recommended viewport processing. + +If the viewport sensor is not implemented at the receiver, or if the viewport sensor is disabled (permanently or temporarily), the receiver should process the recommended viewport metadata, if present. + +If the viewport metadata is provided in the VR Media Presentation and if processing is supported and applied, then the Receiver shall render the viewport indicated metadata. + +# --- 8 VR Presentation + +## 8.1 Definition + +A VR presentation provides an omnidirectional audio-visual experience. A 3GPP VR Presentation is a VR Presentation for which each of the VR Tracks contained in a VR Presentation are aligned to the 3GPP DOF Reference System as defined in clause 4 and are time-synchronized. + +## 8.2 3GPP VR File + +A 3GPP VR Presentation may be provided in an ISO BMFF conforming file. A 3GPP VR File is defined as a file that conforms to ISO BMFF [17] and for which at least two tracks are present whereby: + +- at least one track conforms to a 3GPP VR Track according to a video media profile defined in clause 5, +- at least one track conforms to a 3GPP VR Track according to an audio media profile defined in clause 6. + +Conformance to a 3GPP VR File may be signalled with a compatibility brand '3gvr'. + +## 8.3 3GPP VR DASH Media Presentation + +A 3GPP VR Presentation may be provided in DASH Media Presentation. A 3GPP VR DASH Media Presentation is defined as a DASH Media Presentation that conforms to 3GP DASH and for which at least two Adaptation Sets are present whereby + +- at least one Adaptation Set conforms to an Adaptation Set for a video media profile defined in clause 5, +- at least one Adaptation Set conforms to an Adaptation Set for an audio media profile defined in clause 6. + +Conformance to a 3GPP VR File may be signalled with an MPD @profiles parameter 'urn:3gpp:vrstream:presentation'. + +# --- 9 VR Metrics + +## 9.1 General + +VR metrics is a functionality where the client collects specific quality-related metrics during a session. These collected metrics can then be reported back to a network side node for further analysis. The metric functionality is based on the QoE metrics concept in 3GP-DASH [8], but further extended to also cover VR-specific metrics. A VR client supporting VR metrics shall support all metrics listed in clause 9.3, and shall handle metric configuration and reporting as specified in clauses 9.4 and 9.5. + +## 9.2 VR Client Reference Architecture + +### 9.2.1 Architecture + +The client reference architecture for VR metrics, shown below in Figure 9.2.1-1, is based on the client architecture in Figure 4.3-1. It also contains a number of observation points where specific metric-related information can be made available to the Metrics Collection and Computation (MCC) function. The MCC can use and combine information from the different observation points to calculate more complex metrics. + +Note that these observation points are only defined conceptually, and might not always directly interface to the MCC. For instance, an implementation might relay information from the actual observation points to the MCC via the VR application. It is also possible that the MCC is not separately implemented, but simply included as an integral part of the VR application. + +Also note that in this version of this specification not all of the described observation points are necessarily used to produce VR metrics. + +![Figure 9.2.1-1: Client reference architecture for VR metrics. The diagram shows a flow from MPD and Segment inputs through a DASH Access Engine (OP1) to a File Decoder (OP2) containing a File Parser, 3GPP Operation Point, and Media Decoder. The File Decoder outputs a Decoded Signal and Rendering Metadata to a VR Renderer (OP4), which produces a Viewport Presentation. A VR Application (OP5) and a Sensor (OP3) are also shown. The VR Application receives Static and Dynamic Configuration and Control from the DASH Access Engine and Pose information from the Sensor. The Sensor receives Pose information from the VR Renderer. All observation points (OP1, OP2, OP3, OP4, OP5) have arrows pointing down to a yellow bar labeled 'Metrics collection and computation'.](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +Figure 9.2.1-1: Client reference architecture for VR metrics. The diagram shows a flow from MPD and Segment inputs through a DASH Access Engine (OP1) to a File Decoder (OP2) containing a File Parser, 3GPP Operation Point, and Media Decoder. The File Decoder outputs a Decoded Signal and Rendering Metadata to a VR Renderer (OP4), which produces a Viewport Presentation. A VR Application (OP5) and a Sensor (OP3) are also shown. The VR Application receives Static and Dynamic Configuration and Control from the DASH Access Engine and Pose information from the Sensor. The Sensor receives Pose information from the VR Renderer. All observation points (OP1, OP2, OP3, OP4, OP5) have arrows pointing down to a yellow bar labeled 'Metrics collection and computation'. + +Figure 9.2.1-1: Client reference architecture for VR metrics + +### 9.2.2 Observation Point 1 + +The access engine fetches the MPD, constructs and issues segment requests for relevant adaptation sets or preselections as ordered by the VR application, and receives segments or parts of segments. It may also adapt between different representations due to changes in available bitrate. The access engine provides a conforming 3GPP VR track to the file decoder. + +The interface from the access engine towards MCC is referred to as observation point 1 (OP1) and is defined to monitor: + +- A sequence of transmitted network requests, each defined by its transmission time, contents, and the TCP connection on which it is sent +- For each network response, the reception time and contents of the response header and the reception time of each byte of the response body +- The projection/orientation metadata carried in network manifest file if applicable +- The reception time and intended playout time for each received segment + +### 9.2.3 Observation Point 2 + +The file decoder processes the 3GPP VR Track and typically includes a file parser and a media decoder. The file parser processes the file or segments, extracts elementary streams, and parses the metadata, if present. The processing may be supported by dynamic information provided by the VR application, for example which tracks to choose based on static and dynamic configurations. The media decoder decodes media streams of the selected tracks into the decoded signals. The file decoder outputs the decoded signals and metadata which is used for rendering. + +The interface from the file decoder towards MCC is referred to as observation point 2 (OP2) and is defined to monitor: + +- Media resolution +- Media codec +- Media frame rate +- Media projection, such as region wise packing, region wise quality ranking, content coverage +- Mono vs. stereo 360 video +- Media decoding time + +### 9.2.4 Observation Point 3 + +The sensor extracts the current pose according to the user's head and/or eye movement and provides it to the renderer for viewport generation. The current pose may also be used by the VR application to control the access engine on which adaptation sets or preselections to fetch. + +The interface from the sensor towards MCC is referred to as observation point 3 (OP3) and is defined to monitor: + +- Head pose +- Gaze direction +- Pose timestamp +- Depth + +### 9.2.5 Observation Point 4 + +The VR Renderer uses the decoded signals and rendering metadata, together with the pose and the knowledge of the horizontal/vertical field of view, to determine a viewport and render the appropriate part of the video and audio signals. + +The interface from the media presentation towards MCC is referred to as observation point 4 (OP4) and is defined to monitor: + +- The media type +- The media sample presentation timestamp +- Wall clock counter +- Actual presentation viewport +- Actual presentation time +- Actual playout frame rate +- Audio-to-video synchronization +- Video-to-motion latency +- Audio-to-motion latency + +### 9.2.6 Observation Point 5 + +The VR application manages the complete device, and controls the access engine, the file decoder and the rendering based on media control information, the dynamic user pose, and the display and device capabilities. + +The interface from the VR application towards MCC is referred to as observation point 5 (OP5) and is defined to monitor: + +- Display resolution +- Max display refresh rate +- Field of view, horizontal and vertical +- Eye to screen distance +- Lens separation distance +- OS support, e.g. OS type, OS version + +## 9.3 Metrics Definitions + +### 9.3.1 General + +As the VR metrics functionality is based on the DASH QoE metrics [8], all metrics already defined in [8] are valid also for a VR client. Thus the following sub-clauses only define additional VR-related metrics. + +### 9.3.2 Comparable quality viewport switching latency + +The comparable quality viewport switching latency metric reports the latency and the quality-related factors when viewport movement causes quality degradations, such as when low-quality background content is briefly shown before the normal higher-quality is restored. Note that this metric is only relevant if the Advanced Video Media profile and region-wise packing is used. Also note that the metric currently does not report factors related to foveated rendering. + +The viewport quality is represented by two factors; the quality ranking (QR) value, and the pixel resolution of one or more regions within the viewport. The resolution is defined by the `orig_width` and `orig_height` values in ISO/IEC 23090-2 [13] in SRQR (Spherical-Region Quality Ranking) or 2DQR (2-Dimensional Quality Ranking). The resolution corresponds to the monoscopic projected picture from which the packed region covering the viewport is extracted. + +In order to determine whether two viewports have a comparable quality, if more than one quality ranking region is visible inside the viewport, the aggregated viewport quality factors are calculated as the area-weighted average for QR and the area-weighted (effective) pixel resolution, respectively. + +For instance, if 60% of the viewport is from a region with `QR=1`, `Res=3840 x 2160`, and 40% is from a region with `QR=2`, `Res=960 x 540`, then the average QR is $0.6 \times 1 + 0.4 \times 2$ , and the effective pixel resolution is $0.6 \times 3840 \times 2160 + 0.4 \times 960 \times 540$ (also see Annex D.1 for more examples). + +If the viewport is moved so that the current viewport includes at least one new quality ranking region (i.e. a quality ranking region not included in the previous viewport), a switch event is started. The list of quality factors related to the last evaluated viewport quality before the switch are assigned to the `firstViewport` log entry. The start time of the switch is also set to the time of the last evaluated viewport before the switch. + +The end time for the switch is defined as when both the weighted average QR and the effective resolution for the viewport reach values comparable to the ones before the switch. A value is comparable if it is not more than `QRT%` (QR threshold) or `ERT%` (effective resolution threshold) worse than the corresponding values before the switch. If comparable values are not achieved within N milliseconds, a timeout occurs (for instance if an adaptation to a lower bitrate occurs, and the viewport never reaches comparable quality). + +Note that smaller QR values and larger resolution values are better. For instance, `QRT=5%` would require a weighted average QR value equal or smaller than 105 % of the weighted average QR before the switch, but `ERT=5%` would require an effective resolution value equal or larger than 95% of the effective resolution before the switch. + +The list of quality factors related to the viewport which fulfills both thresholds are assigned to the `secondViewport` log entry, and the latency (end time minus start time) is assigned to the `latency` log entry. In case of a timeout, this is indicated under the `cause` log entry. + +During the duration of the switch the worst evaluated viewport is also stored, and assigned to the `worstViewport` log entry. The worst viewport is defined as the viewport with the worst relative weighted average QR or relative effective resolution, as compared to the values before the switch. + +If a new viewport switching event occurs (e.g. yet another new region becomes visible) before an ongoing switch event has ended, only the N milliseconds timeout is reset. The ongoing measurement process continues to evaluate the viewport quality until a comparable viewport quality value is achieved (or a timeout occurs). + +The observation points needed to calculate the metrics are: + +- OP2 File Decoder: SRQR/2DQR information +- OP3 Sensor: Gaze information +- OP4 VR Renderer: Start of switch event detection (alternatively, region coverage information from SRQR/2DQR can be used as strict rendering pixel-exactness is not required) +- OP5 VR Application: Field-of-view information of the device + +The accuracy of the measured latency depends on how the client implements the viewport switching monitoring. As this might differ between clients, the client shall report the estimated accuracy. + +The thresholds QRT, ERT, and the timeout N, can be specified during metrics configuration (see clause 9.4) as attributes within parenthesis, e.g. "CompQualLatency(QRT=3.5,ERT=6.8,N=900)". If a threshold or the timeout is not specified the client shall use appropriate default values. + +The data type `ViewportDataType` is defined in Table 9.3.2-1 below, and identifies the direction and coverage of the viewport. + +**Table 9.3.2-1: ViewportDataType** + +| Key | Type | Description | +|-------------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ViewportDataType | Object | | +| centre_azimuth | Integer | Specifies the azimuth of the centre of the viewport in units of $2^{-16}$ degrees. The value shall be in the range of $-180 * 2^{16}$ to $180 * 2^{16} - 1$ , inclusive. | +| centre_elevation | Integer | Specifies the elevation of the centre of the viewport in units of $2^{-16}$ degrees. The value shall be in the range of $-90 * 2^{16}$ to $90 * 2^{16}$ , inclusive. | +| centre_tilt | Integer | Specifies the tilt angle of the viewport in units of $2^{-16}$ degrees. The value shall be in the range of $-180 * 2^{16}$ to $180 * 2^{16} - 1$ , inclusive. | +| azimuth_range | Integer | Specifies the azimuth range of the viewport through the centre point of the viewport, in units of $2^{-16}$ degrees. | +| elevation_range | Integer | Specifies the elevation range of the viewport through the centre point of the viewport, in units of $2^{-16}$ degrees. | + +The data type `Viewport-Item` is defined as shown in Table 9.3.2-2. `Viewport-Item` is an Object which identifies a viewport and quality-related factors for the region(s) covered by the viewport. + +**Table 9.3.2-2: ViewportItem** + +| Key | Type | Description | +|----------------------------|-------------------------------|--------------------------------------------------------------| +| ViewportItem | Object | | +| Position | ViewportDataType | Identifies the viewport | +| QualityLevels | List | List of different quality levels regions within the viewport | + +| | | | | | +|--|--|------------|---------|--------------------------------------------------------| +| | | Coverage | Float | Percentage of the viewport area covered by this region | +| | | QR | Integer | Quality ranking (QR) value of this region | +| | | Resolution | Object | Resolution for this region | +| | | Width | Integer | Horizontal resolution for this region | +| | | Height | Integer | Vertical resolution for this region | + +The comparable quality viewport switching latency metric is specified in Table 9.3.2-1 below. + +**Table 9.3.2-1: Comparable quality viewport switching latency metric** + +| Key | Type | Description | +|-----------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CompQualLatency | List | List of comparable quality viewport switching latencies | +| Entry | Object | | +| firstViewport | ViewportItem | Specifies information about the first viewport | +| secondViewport | ViewportItem | Specifies information about the second viewport | +| worstViewport | ViewportItem | Specifies information about the worst viewport seen during the switch duration | +| time | Real-Time | Wall-clock time when the switch started | +| Mtime | Media-Time | Media presentation time when the switch started. | +| Latency | Integer | Specifies the switching delay in milliseconds. | +| Accuracy | Integer | Specifies the estimated accuracy of the latency metric in milliseconds | +| Cause | List | Specifies a list of possible causes for the latency. | +| Entry | Object | | +| code | Enum | A possible cause for the latency. The value is equal to one of the following:
- 0: Segment duration
- 1: Buffer fullness
- 2: Availability of comparable quality segment
- 3: Timeout | + +### 9.3.3 Rendered viewports + +The rendered viewports metric reports a list of viewports that have been rendered during the media presentation. + +The client shall evaluate the current viewport gaze every X ms and potentially add the viewport to the rendered viewport list. To enable frequent viewport evaluations without necessarily increasing the report size too much, consecutive viewports which are close to each other may be grouped into clusters, where only the average cluster viewport data is reported. Also, clusters which have too short durations may be excluded from the report. + +The viewport clustering is controlled by an angular distance threshold D. If the center (i.e. the azimuth and the elevation) of the current viewport is closer than the distance D to the current cluster center (i.e. the average cluster + +azimuth and elevation), the viewport is added to the cluster. Note that the distance is only compared towards the current (i.e. last) cluster, not to any earlier clusters which might have been created. + +If the distance to the cluster center is instead equal to or larger than D, a new cluster is started based on the current viewport, and the average old cluster data and the start time and duration for the old cluster is added to the viewport list. + +Before reporting a viewport list, a filtering based on viewport duration shall be done. Each entry in the viewport list is first assigned an "aggregated duration" equal to the duration of that entry. Then, for each entry E, the other entries in the viewport list are checked. The duration for a checked entry is added to the aggregated duration for entry E, if the checked entry is both less than T ms away from E, and closer than the angular distance D from E. + +After all viewport entries have been evaluated and have received a final aggregated duration, all viewport entries with an aggregated duration of less than T are deleted from the viewport list (and thus not reported). Note that the aggregated duration is only used for filtering purposes, and not itself included in the viewport list reports. + +Some examples of metric calculation are shown in Annex D.2. + +The observation points needed to calculate the metrics are: + +- OP3 Sensor: Gaze information +- OP5 P5 VR Application: Field-of-view information of the device + +The viewport sample interval X (in ms), the distance threshold D (in degrees), and the duration threshold T (in ms) can be specified during metrics configuration as attributes within parenthesis, e.g. + +"RenderedViewports(X=50,D=15,T=1500)". Note that if no clustering or duration filtering is wanted, the D and T thresholds can be set to 0 (e.g. specifying "RenderedViewports(X=1000,D=0,T=0)" will just log the viewport every 1000 ms). If no sample interval or thresholds values are specified the client shall use appropriate default values. + +The rendered viewports metric is specified in Table 9.3.3-1. + +**Table 9.3.3-1: Rendered viewports metric** + +| Key | Type | Description | +|-------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RenderedViewports | List | List of rendered viewports | +| Entry | Object | | +| startTime | Media-Time | Specifies the media presentation time of the first played out media sample when the viewport cluster indicated in the current entry is rendered starting from this media sample. | +| duration | Integer | The time duration, in units of milliseconds, of the continuously presented media samples when the viewport cluster indicated in the current entry is rendered starting from the media sample indicated by startTime.
"Continuously presented" means that the media clock continued to advance at the playout speed throughout the interval. | +| viewport | ViewportDataType | Indicates the average region of the omnidirectional media corresponding to the viewport cluster being rendered starting from the media sample time indicated by startTime. | + +### 9.3.4 VR Device information + +This metric contains information about the device, and is logged at the start of each session and whenever changed (for instance if the rendered field-of-view for the device is adjusted). If an individual metric cannot be logged, its value shall be set to 0 (zero) or to the empty string. + +The observation point needed to report the metrics is: + +- OP5 VR Application: Device Information + +Table 9.3.4-1: Device information + +| Key | Type | Description | +|-----------------------|------------|-------------------------------------------------------------------| +| VrDeviceInformation | List | A list of device information objects. | +| Entry | Object | A single object containing new device information. | +| start | Real-Time | Wall-clock time when the device information was logged. | +| mstart | Media-Time | The presentation time at which the device information was logged. | +| deviceIdentifier | String | The brand, model and version of the device. | +| horizontalResolution | Integer | The horizontal display resolution, per eye, in pixels. | +| verticalResolution | Integer | The vertical display resolution, per eye, in pixels. | +| horizontalFoV | Integer | Maximum horizontal field-of-view, per eye, in degrees. | +| verticalFoV | Integer | Maximum vertical field-of-view, per eye, in degrees. | +| renderedHorizontalFoV | Integer | Current rendered horizontal field-of-view, per eye, in degrees. | +| renderedVerticalFoV | Integer | Current rendered vertical field-of-view, per eye, in degrees. | +| refreshRate | Integer | Display refresh rate, in Hz | + +## 9.4 Metrics Configuration and Reporting + +### 9.4.1 Configuration + +Metrics configuration is done according to clauses 10.4 and 10.5 in DASH [8], but can also include any metrics defined in clause 9.3. + +### 9.4.2 Reporting + +Metrics reporting is done according to clause 10.6 in DASH [8], with the type QoeReportType extended to handle the additional VR-specific metrics according the XML schema in clause 9.4.3. In this version of the specification the element *vrMetricSchemaVersion* shall be set to 1. + +### 9.4.3 Reporting Format + +``` + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +# --- Annex A (informative): Content Generation Guidelines + +## A.1 Introduction + +This clause collects information that supports the generation of VR Content following the details in the present document. Video and audio related aspects are collected. For additional details and background also refer to TR 26.918 [2]. + +## --- A.2 Video + +### A.2.1 Overview + +This clause collects information on that support the generation of video bitstreams that conform to operation points and media profile in the present document. + +### A.2.2 Decoded Texture Signal Constraints + +#### A.2.2.1 General + +Due to the restrictions to use a single decoder, the decoded texture signals require to follow the profile and level constraints of the decoder. Generally, this requires a careful balance of the permitted frame rates, stereo modes, spatial resolutions, and usage of region wise packing for different resolutions and coverage restrictions. Details on preferred settings such as frame rates and spatial resolutions are for example discussed in TR 26.918 [2]. + +This clause provides a summary of restrictions for the different operation points defined in the present document. + +#### A.2.2.2 Constraints for Main and Flexible H.265/HEVC Operation Point + +The profile and level constraints of H.265/HEVC Main-10 Profile Main Tier Profile Level 5.1 require careful balance of the permitted frame rates, stereo modes, spatial resolutions, and usage of region wise packing for different resolutions and coverage restrictions. If the decoded texture signal is beyond the Profile and Level constraints, then a careful adaptation of the signal is recommended to fulfil the constraints. + +This clause provides a brief overview of potential signal constraints and possible adjustments. + +Table A.2-1 provides selected permitted combinations of spatial resolutions, frame rates and stereo modes assuming full coverage and no region-wise packing applied. Note that fractional frame rates are excluded for better readability. Note that the Main H.265/HEVC Operation Point only allows frame rates up to 60 Hz. + +**Table A.2-1: Selected permitted combinations of spatial resolutions and frame rates** + +| Spatial resolution per eye | Stereo | Permitted Frame Rates in Hz | +|----------------------------|--------|----------------------------------| +| 4096 × 2048 | None | 24; 25; 30; 50; 60 | +| 3840 × 1920 | None | 24; 25; 30; 50; 60 | +| 3072 × 1536 | None | 24; 25; 30; 50; 60; 90; 100 | +| 2880 × 1440 | None | 24; 25; 30; 50; 60; 90; 100; 120 | +| 2048 × 1024 | None | 24; 25; 30; 50; 60; 90; 100; 120 | +| 2880 × 1440 | TaB | 24; 25; 30; 50; 60 | +| 2048 × 1024 | TaB | 24; 25; 30; 50; 60; 90; 100; 120 | + +Table A.2-2 provides the maximum percentage of high-resolution area that can be encoded assuming that the low-resolution area is encoded in 2k resolution covering the full 360 degree area, i.e. using 2048 × 1024 or 1920 × 960 and full coverage is provided for different frame rates. Note also that a viewport typically covers about 12-25% of a full 360 video. Note that fractional frame rates are excluded for better readability. + +**Table A.2-2: Maximum Percentage of high-resolution area when assuming that the low-resolution area is encoded in 2k resolution, i.e. using 2048 × 1024 or 1920 × 960 and full coverage is provided for different frame rates** + +| Spatial resolution per eye in VP | Spatial resolution per eye in non-VP | Stereo | Frame Rates in Hz | | | | | | | | +|----------------------------------|--------------------------------------|--------|-------------------|---------|---------|---------|---------|--------|--------|--------| +| | | | 24 | 25 | 30 | 50 | 60 | 90 | 100 | 120 | +| 6144 × 3072 | 2048 × 1024 | None | 9.29% | 9.29% | 9.29% | 9.29% | 9.29% | 5.24% | 4.43% | 3.21% | +| 4096 × 2048 | 2048 × 1024 | None | 21.67% | 21.67% | 21.67% | 21.67% | 21.67% | 12.22% | 10.33% | 7.50% | +| 3840 × 1920 | 1920 × 960 | None | 100.00% | 100.00% | 100.00% | 100.00% | 100.00% | 74.12% | 63.38% | 47.26% | +| 6144 × 3072 | 2048 × 1024 | TaB | 3.21% | 3.21% | 3.21% | 3.21% | 3.21% | 1.19% | 0.79% | 0.18% | +| 4096 × 2048 | 2048 × 1024 | TaB | 7.50% | 7.50% | 7.50% | 7.50% | 7.50% | 2.78% | 1.83% | 0.42% | +| 3840 × 1920 | 1920 × 960 | TaB | 47.26% | 47.26% | 47.26% | 47.26% | 47.26% | 20.40% | 15.02% | 6.96% | + +Table A.2-3 provides the maximum percentage of coverage area that can be encoded assuming that the remaining pixels are not encoded for different frame rates. Note that fractional frame rates are excluded for better readability. + +**Table A.2-3: Maximum Percentage of coverage area for different frame rates** + +| Spatial resolution per eye | Stereo | Frame Rates in Hz | | | | | | | | +|----------------------------|--------|-------------------|---------|---------|---------|---------|--------|--------|--------| +| | | 24 | 25 | 30 | 50 | 60 | 90 | 100 | 120 | +| 6144 × 3072 | None | 47.22% | 47.22% | 47.22% | 47.22% | 47.22% | 31.48% | 28.33% | 23.61% | +| 4096 × 2048 | None | 100.00% | 100.00% | 100.00% | 100.00% | 100.00% | 70.83% | 63.75% | 53.13% | +| 3840 × 1920 | None | 100.00% | 100.00% | 100.00% | 100.00% | 100.00% | 80.59% | 72.53% | 60.44% | +| 6144 × 3072 | TaB | 23.61% | 23.61% | 23.61% | 23.61% | 23.61% | 15.74% | 14.71% | 11.81% | +| 4096 × 2048 | TaB | 53.13% | 53.13% | 53.13% | 53.13% | 53.13% | 35.42% | 31.88% | 26.56% | +| 3840 × 1920 | TaB | 60.44% | 60.44% | 60.44% | 60.44% | 60.44% | 40.30% | 36.27% | 30.22% | + +### A.2.2a Constraints for Main 8K H.265/HEVC Operation Point + +The profile and level constraints of H.265/HEVC Main-10 Profile Main Tier Profile Level 6.1 require careful balance of the permitted frame rates, stereo modes, spatial resolutions, and usage of region wise packing for different resolutions and coverage restrictions. If the decoded texture signal is beyond the Profile and Level constraints, then a careful adaptation of the signal is recommended to fulfil the constraints. + +This clause provides a brief overview of potential signal constraints and possible adjustments. + +Table A.2a-1 provides selected permitted combinations of spatial resolutions, frame rates and stereo modes assuming full coverage and no region-wise packing applied. Note that fractional frame rates are excluded for better readability. Note that the Main 8K H.265/HEVC Operation Point only allows frame rates up to 60 Hz. + +**Table A.2a-1: Selected permitted combinations of spatial resolutions and frame rates** + +| Spatial resolution per eye | Stereo | Permitted Frame Rates in Hz | +|----------------------------|--------|----------------------------------| +| 8192 × 4096 | None | 24; 25; 30; 50; 60 | +| 7680 × 3840 | None | 24; 25; 30; 50; 60 | +| 6144 × 3072 | None | 24; 25; 30; 50; 60; 90; 100 | +| 5760 × 2880 | None | 24; 25; 30; 50; 60; 90; 100; 120 | +| 4096 × 2048 | None | 24; 25; 30; 50; 60; 90; 100; 120 | +| 5760 × 2880 | TaB | 24; 25; 30; 50; 60 | +| 4096 × 2048 | TaB | 24; 25; 30; 50; 60; 90; 100; 120 | + +Table A.2a-2 provides the maximum percentage of coverage area that can be encoded assuming that the remaining pixels are not encoded for different frame rates. Note that fractional frame rates are excluded for better readability. + +**Table A.2a-2 Maximum Percentage of coverage area for different frame rates** + +| Spatial resolution per eye | Stereo | Frame Rates in Hz | | | | | | | | +|----------------------------|--------|-------------------|---------|---------|---------|---------|--------|--------|--------| +| | | 24 | 25 | 30 | 50 | 60 | 90 | 100 | 120 | +| 12288 × 6144 | None | 47.22% | 47.22% | 47.22% | 47.22% | 47.22% | 31.48% | 28.33% | 23.61% | +| 8192 × 4096 | None | 100.00% | 100.00% | 100.00% | 100.00% | 100.00% | 70.83% | 63.75% | 53.13% | + +| | | | | | | | | | | +|--------------|------|---------|---------|---------|---------|---------|--------|--------|--------| +| 7680 × 3840 | None | 100.00% | 100.00% | 100.00% | 100.00% | 100.00% | 80.59% | 72.53% | 60.44% | +| 12288 × 6144 | TaB | 23.61% | 23.61% | 23.61% | 23.61% | 23.61% | 15.74% | 14.71% | 11.81% | +| 8192 × 4096 | TaB | 53.13% | 53.13% | 53.13% | 53.13% | 53.13% | 35.42% | 31.88% | 26.56% | +| 7680 × 3840 | TaB | 60.44% | 60.44% | 60.44% | 60.44% | 60.44% | 40.30% | 36.27% | 30.22% | + +### A.2.3 Conversion of ERP Signals to CMP + +#### A.2.3.1 General + +The 3D XYZ coordinate system as shown in Figure A.1 can be used to describe the 3D geometry of ERP and CMP projection format representations. Starting from the center of the sphere, X axis points toward the front of the sphere, Z axis points toward the top of the sphere, and Y axis points toward the left of the sphere. + +![Figure A.1: 3D XYZ coordinate definition. A diagram of a sphere with a 3D coordinate system. The Z-axis points to the top, the X-axis points to the front, and the Y-axis points to the left. The sphere has dashed lines for the equator and meridians. A point on the sphere is defined by azimuth (phi) and elevation (theta). The azimuth phi is measured from the X-axis in the XY-plane. The elevation theta is measured from the XY-plane towards the Z-axis. Rotational axes are indicated: Yaw around the Z-axis, Pitch around the Y-axis, and Roll around the X-axis. A label phi = theta = 0 points to the positive X-axis.](22529ce6e2914d705243ba1bf43be65d_img.jpg) + +Figure A.1: 3D XYZ coordinate definition. A diagram of a sphere with a 3D coordinate system. The Z-axis points to the top, the X-axis points to the front, and the Y-axis points to the left. The sphere has dashed lines for the equator and meridians. A point on the sphere is defined by azimuth (phi) and elevation (theta). The azimuth phi is measured from the X-axis in the XY-plane. The elevation theta is measured from the XY-plane towards the Z-axis. Rotational axes are indicated: Yaw around the Z-axis, Pitch around the Y-axis, and Roll around the X-axis. A label phi = theta = 0 points to the positive X-axis. + +Figure A.1: 3D XYZ coordinate definition + +NOTE: The text in this Annex is based on JVET output document (JVET-H1004: Algorithm descriptions of projection format conversion and video quality metrics in 360Lib (Version 5)) with simplifications to only two projection types which are used in the present document and further fixes regarding misalignments. C++ implementation of the concepts described by this annex is available in 360Lib Software: available at: [https://jvet.hhi.fraunhofer.de/svn/svn\\_360Lib](https://jvet.hhi.fraunhofer.de/svn/svn_360Lib). + +The coordinate system is specified for defining the sphere coordinates azimuth ( $\phi$ ) and elevation ( $\theta$ ) for identifying a location of a point on the unit sphere. The azimuth $\phi$ is in the range $[-\pi, \pi]$ , and elevation $\theta$ is in the range $[-\pi/2, \pi/2]$ , where $\pi$ is the ratio of a circle's circumference to its diameter. The azimuth ( $\phi$ ) is defined by the angle starting from X axis in counter-clockwise direction as shown in Figure A.1. The elevation ( $\theta$ ) is defined by the angle from the equator toward Z axis as shown in Figure A.1. The $(X, Y, Z)$ coordinates on the unit sphere can be evaluated from $(\phi, \theta)$ using following equations: + +$$X = \cos(\theta) * \cos(\phi)$$ + +$$Y = \cos(\theta) * \sin(\phi)$$ + +$$Z = \sin(\theta)$$ + +Inversely, the longitude and latitude $(\phi, \theta)$ can be evaluated from $(X, Y, Z)$ coordinates using: + +$$\phi = \tan^{-1}(Y/X)$$ + +$$\theta = \sin^{-1}(Z / (\sqrt{X^2+Y^2+Z^2}))$$ + +A 2D plane coordinate system is defined for each face in the 2D projection plane. Where Equirectangular Projection (ERP) has only one face, Cubemap Projection (CMP) has six faces. In order to generalize the 2D coordinate system, a + +face index is defined for each face in the 2D projection plane. Each face is mapped to a 2D plane associated with one face index. + +#### A.2.3.2 Equirectangular Projection (ERP) + +Equirectangular mapping is the most commonly used mapping from spherical video to a 2D texture signal. The mapping is bijective, i.e. it may be expressed in both directions and is illustrated in Figure A.2. + +![Figure A.2: Mapping of spherical video to a 2D texture signal. The diagram shows a sphere with axes X, Y, Z. The Z-axis is labeled 'Yaw' with a circular arrow. The Y-axis is labeled 'Pitch' with a circular arrow. The X-axis is labeled 'Roll' with a circular arrow. A point on the sphere is defined by coordinates (phi, theta). A double-headed arrow points to a 2D rectangular plane. The horizontal axis is labeled 'i' and has markings for 90, 180, -180, and -90 degrees. The vertical axis is labeled 'j' and has a marking for 0 degrees at the center. A dashed line connects the origin of the sphere to the center of the 2D plane, labeled phi = theta = 0.](64544fbada794f3cdf4f78f5d83613e4_img.jpg) + +Figure A.2: Mapping of spherical video to a 2D texture signal. The diagram shows a sphere with axes X, Y, Z. The Z-axis is labeled 'Yaw' with a circular arrow. The Y-axis is labeled 'Pitch' with a circular arrow. The X-axis is labeled 'Roll' with a circular arrow. A point on the sphere is defined by coordinates (phi, theta). A double-headed arrow points to a 2D rectangular plane. The horizontal axis is labeled 'i' and has markings for 90, 180, -180, and -90 degrees. The vertical axis is labeled 'j' and has a marking for 0 degrees at the center. A dashed line connects the origin of the sphere to the center of the 2D plane, labeled phi = theta = 0. + +**Figure A.2: Mapping of spherical video to a 2D texture signal** + +ERP has only one face and the face index $f$ for ERP is always set to 0. The sphere coordinates $(\phi, \theta)$ for a sample location $(i, j)$ , in degrees, are given by the following equations: + +$$\phi = (0.5 - i/\text{pictureWidth}) * 360$$ + +$$\theta = (0.5 - j/\text{pictureHeight}) * 180$$ + +Finally, $(X, Y, Z)$ can be calculated from the equations given above. + +#### A.2.3.3 Cubemap Projection (CMP) + +Figure A.3 shows the CMP projection with 6 square faces, labelled as PX, PY, PZ, NX, NY, NZ (with "P" standing for "positive" and "N" standing for "negative"). Table A.2-4 specifies the face index values corresponding to each of the six CMP faces. + +![Figure A.3: Relation of the cube face arrangement of the projected picture to the sphere coordinates. The diagram shows a cube with six faces: PZ Top, NX Back, NY Right, PX Front, PY Left, and NZ Bottom. A sphere is inscribed in the cube. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points diagonally down-left. A point on the sphere is defined by coordinates (phi, theta). A double-headed arrow points to a 2D rectangular plane. The horizontal axis is labeled 'i' and the vertical axis is labeled 'j'. The plane is divided into six square regions, each containing one of the cube faces: NY Right (top right), PY Left (middle left), PX Front (center), NX Back (bottom center), NZ Bottom (bottom left), and PZ Top (top center). Blue dots mark the corners of the faces on the cube and the corresponding locations on the 2D plane.](239c9d313ad906eda294af980e34ef48_img.jpg) + +Figure A.3: Relation of the cube face arrangement of the projected picture to the sphere coordinates. The diagram shows a cube with six faces: PZ Top, NX Back, NY Right, PX Front, PY Left, and NZ Bottom. A sphere is inscribed in the cube. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points diagonally down-left. A point on the sphere is defined by coordinates (phi, theta). A double-headed arrow points to a 2D rectangular plane. The horizontal axis is labeled 'i' and the vertical axis is labeled 'j'. The plane is divided into six square regions, each containing one of the cube faces: NY Right (top right), PY Left (middle left), PX Front (center), NX Back (bottom center), NZ Bottom (bottom left), and PZ Top (top center). Blue dots mark the corners of the faces on the cube and the corresponding locations on the 2D plane. + +**Figure A.3: Relation of the cube face arrangement of the projected picture to the sphere coordinates** + +Table A.2-4: Face index of CMP + +| Face index | Face label | Notes | +|------------|------------|----------------------------------------| +| 0 | PX | Front face with positive X axis value | +| 1 | NX | Back face with negative X axis value | +| 2 | PY | Left face with positive Y axis value | +| 3 | NY | Right face with negative Y axis value | +| 4 | PZ | Top face with positive Z axis value | +| 5 | NZ | Bottom face with negative Z axis value | + +The 3D coordinates (X, Y, Z) are derived using following equations: + +``` + +lw = pictureWidth / 3 +lh = pictureHeight / 2 +tmpHorVal = i - Floor( i / lw ) * lw +tmpVerVal = j - Floor( j / lh ) * lh +i' = -( 2 * tmpHorVal / lw ) + 1 +j' = -( 2 * tmpVerVal / lh ) + 1 +w = Floor( i / lw ) +h = Floor( j / lh ) +if( w == 1 && h == 0 ) { // PX: positive x front face + X = 1.0 + Y = i' + Z = j' +} else if( w == 1 && h == 1 ) { // NX: negative x back face + X = -1.0 + Y = -j' + Z = -i' +} else if( w == 2 && h == 1 ) { // PZ: positive z top face + X = -i' + Y = -j' + Z = 1.0 +} else if( w == 0 && h == 1 ) { // NZ: negative z bottom face + X = i' + Y = -j' + Z = -1.0 +} else if( w == 0 && h == 0 ) { // PY: positive y left face + X = -i' + Y = 1.0 + Z = j' +} else { // ( w == 2 && h == 0 ), NY: negative y right face + X = i' + Y = -1.0 + Z = j' +} +} + +``` + +#### A.2.3.4 Conversion between two projection formats + +Denote $(f_d, i_d, j_d)$ as a point $(i_d, j_d)$ on face $f_d$ in the destination projection format, and $(f_s, i_s, j_s)$ as a point $(i_s, j_s)$ on face $f_s$ in the source projection format. Denote $(X, Y, Z)$ as the corresponding coordinates in the 3D XYZ space. The conversion process starts from each sample position $(f_d, i_d, j_d)$ on the destination projection plane, maps it to the corresponding $(X, Y, Z)$ in 3D coordinate system, finds the corresponding sample position $(f_s, i_s, j_s)$ on the source projection plane, and sets the sample value at $(f_d, i_d, j_d)$ based on the sample value at $(f_s, i_s, j_s)$ . + +Therefore, the projection format conversion process from ERP source format to CMP destination format is performed in the following three steps: + +- 1) Map the destination 2D sampling point $(f_d, i_d, j_d)$ to 3D space coordinates $(X, Y, Z)$ based on the CMP format. +- 2) Map $(X, Y, Z)$ from step 1 to 2D sampling point $(f_0, i_s, j_s)$ based to the ERP format. +- 3) Calculate the sample value at $(f_0, i_s, j_s)$ by interpolating from neighboring samples at integer positions on face $f_0$ , and the interpolated sample value is placed at $(f_d, i_d, j_d)$ in the destination projection format. + +The above steps are repeated until all sample positions $(f_d, i_d, j_d)$ in the destination projection format are filled. Note that (Step 1) and (Step 2) can be pre-calculated at the sequence level and stored as a lookup table, and only (Step 3) needs to be performed per sample position for each picture in order to render the sample values. + +# Annex B (informative): Example External Binaural Renderer + +## B.1 General + +Binaural rendering allows 3D audio content to be played back via headphones. The rendering is performed as a fast convolution of point sound source streams in the 3D space with head-related impulse responses (HRIRs) or binaural room impulse responses (BRIRs) corresponding to the direction of incidence relative to the listener. HRIRs will be provided from an external source. + +![Figure B.1-1: High level overview of an external binaural renderer setup. The diagram shows an 'MPEG-H Decoder' block receiving an 'encoded bitstream' and outputting 'audio input streams' and 'stream metadata' to an 'External Binaural Renderer' block. The 'External Binaural Renderer' also receives 'HRIR' data via an 'HRIR interface' and 'scene displacement' information via a 'scene displacement interface'. The 'External Binaural Renderer' outputs 'headphones output'. A legend indicates that solid lines represent audio streams, dashed lines represent metadata, and dotted lines represent HRIRs.](bc6f20871b4f01c61470306c304fc9fe_img.jpg) + +Figure B.1-1: High level overview of an external binaural renderer setup. The diagram shows an 'MPEG-H Decoder' block receiving an 'encoded bitstream' and outputting 'audio input streams' and 'stream metadata' to an 'External Binaural Renderer' block. The 'External Binaural Renderer' also receives 'HRIR' data via an 'HRIR interface' and 'scene displacement' information via a 'scene displacement interface'. The 'External Binaural Renderer' outputs 'headphones output'. A legend indicates that solid lines represent audio streams, dashed lines represent metadata, and dotted lines represent HRIRs. + +Figure B.1-1: High level overview of an external binaural renderer setup. + +The renderer has three input interfaces (see Fig. B.1-1): the audio streams and metadata from the MPEG-H decoder, a head tracking interface for scene displacement information (for listener tracking), and a head-related impulse response (HRIR) interface providing binaural impulse responses for a given direction of incidence. The metadata as described in B.3, together with the scene displacement information, is used to construct a scene model, from which the renderer can infer the proper listener-relative point source positions. + +The audio input streams may include Channel content, Object content, HOA content. The renderer performs pre-processing steps to translate the respective content type into several point sources that are then processed for binaural rendering. Channel groups and objects that are marked a non-diegetic in the metadata are excluded from any scene displacement processing. + +## B.2 Interfaces + +### B.2.1 Interface for Audio Data and Metadata + +The example external binaural renderer has an interface for the input of un-rendered channels, objects, and HOA content and associated metadata. The syntax of this input interface follows the specification of the External Renderer Interface for MPEG-H 3D Audio to output un-rendered channels, objects, and HOA content and associated metadata according to clause 6.1.4.3.6.5. + +The input PCM data of the channels and objects interfaces is provided through an input PCM buffer, which first contains $n_{\text{chan, out}}$ signals carry the PCM data of the channel content. These are followed by $n_{\text{obj, out}}$ signals carrying the PCM data of the un-rendered objects. Then additional signals carry the $n_{\text{HOA, out}}$ HOA data which number is indicated in the HOA metadata via the HOA order (e.g. 16 signals for HOA order 3). The HOA audio data in the HOA interface is + +provided in the ESD representation. The conversion from the HOA domain into the equivalent spatial domain representation and vice versa is described in ISO/IEC 23008-3 [19], Annex C.5.1. + +The metadata for channels, objects, and HOA is received via the input interface once per frame and their syntax is specified in `mpegh3da_getChannelMetadata()`, `mpegh3da_getObjectAudioAndMetadata()`, and `mpegh3da_getHoaMetadata()` respectively, see ISO/IEC 23008-3, clause 17.10 [19]. The metadata and PCM data will be aligned to match each metadata element with the respective PCM frame. + +### B.2.2 Head Tracking Interface. + +The external binaural renderer receives scene displacement values (yaw, pitch and roll) e.g. from an external head tracking device via the head tracking interface. The syntax is specified in `mpegh3daSceneDisplacementData()` as defined in ISO/IEC 23008-3 [19], clause 17.9.3. + +### B.2.3 Interface for Head-Related Impulse Responses + +An interface is provided to specify the set of HRIRs used for the binaural rendering. These directional FIR filters will be input using the SOFA (Spatially Oriented Format for Acoustics) files format according to AES-69 [21]. The SimpleFreeFieldHRIR convention will be used, where binaural filters are indexed by polar coordinates (azimuth $\varphi$ in radians, elevation $\phi$ in radians, and radius $r$ in meters) relative to the listener. + +## --- B.3 Preprocessing + +### B.3.1 Channel Content + +Channel input content is converted into a corresponding set of point sources with associated positions using the loudspeaker configuration data included in `mpegh3da_getChannelMetadata()` and the associated PCM data obtained via the interface specified in B.2.1 + +### B.3.2 Object Content + +Object input content is converted into corresponding point sources with associated positions using the metadata included in `mpegh3da_getObjectAudioAndMetadata()` and the associated PCM data obtained via the interface specified in clause B.2.1 + +### B.3.3 HOA Content + +As specified in clause B.2.1 HOA content is input in the ESD representation together with the metadata included in `mpegh3da_getHoaMetadata()`. As a pre-processing step, the ESD representation is first converted into HOA coefficients. All coefficients associated with HOA of order larger than three are discarded to limit the maximum computational complexity. + +### B.3.4 Non-diegetic Content + +Channel groups for which the `gca_directHeadphone` flag is set in `mpegh3da_getChannelMetadata()` are routed to left and right output channel directly and are excluded from binaural rendering using scene displacement data (non-diegetic content). Non-diegetic content may have stereo or mono format. For mono, the signal is mixed to left and right headphone channel with a gain factor of 0.707. + +For each channel group it has to be checked in the `mpegh3da_getChannelMetadata()` if the `gca_fixedChannelsPosition` flag is equal to 0 or 1. A channel group with an associated '`gca_fixedChannelsPosition == 1`' is included in the binaural rendering but excluded from the scene displacement processing according to clause B.4, i.e. its position is not updated. + +For each object it has to be checked in the `mpeg3da_getObjectAudioAndMetadata()` if the `goa_fixedPosition` flag is equal to 0 or 1. An object with an associated '`goa_fixedPosition == 1`' is included in the binaural rendering but excluded from the scene displacement processing according to clause B.4, i.e. its position is not updated. + +## B.4 Scene Displacement Processing + +### B.4.1 General + +The position of each point source derived from the channels and objects input is represented by a 3-dimensional vector $\vec{s}_c$ in a Cartesian coordinate system. The scene displacement information is used to compute an updated version of the position vector $\vec{s}'_c$ as described in clause B.4.2. The position of point sources that result from non-diegetic channel groups with an associated '`gca_fixedChannelsPosition == 1`' or from non-diegetic objects with an associated '`goa_fixedPosition == 1`' (see clause B.3.4) is not updated, i.e. $\vec{s}'_c$ is equal to $\vec{s}_c$ . + +### B.4.2 Applying Scene Displacement Information + +The vector representation of a point source $\vec{s}_c$ is transformed to the listener-relative coordinate system by rotation based on the scene displacement values obtained via the head tracking interface. This is achieved by multiplying the position $\vec{s}_c$ with a rotation matrix calculated from the orientation of the listener: + +$$\vec{s}'_c = T_{rot} \vec{s}_c$$ + +The determination of the rotation matrix $T_{rot}$ is defined in ISO/IEC 23008-3 [19], Annex I. + +For HOA content, the rotation matrix $T_{rot,hoa}$ suited for rotating the spherical harmonic representation is calculated as defined in ISO/IEC 23008-3 [19], Annex I. After the rotation, the HOA coefficients are transformed back into the ESD representation. Each ESD component is then converted to the corresponding point source with its associated positional information. For the ESD components the position information is fixed, i.e. $\vec{s}'_c = \vec{s}_c$ , as the rotation due to scene displacement is performed in the spherical harmonic representation. + +## B.5 Headphone Output Signal Computation + +### B.5.1 General + +The overall Scene Model is represented by the collection of all point sources with updated position $\vec{s}'_c$ obtained from the rotated channels, objects, and the ESD components as well as the non-diegetic channels and objects for which '`gca_fixedChannelsPosition == 1`' or '`goa_fixedPosition == 1`'. The overall number of point sources in the Scene Model is denoted with $C$ . + +### B.5.2 HRIR Selection + +The position $\vec{s}'_c$ of each point source in the listener-relative coordinate system is used to query a best-match HRIR pair from the set of available HRIRs. For lookup, the polar coordinates of the HRIR locations are transformed into the internally used cartesian coordinates and the closest-match available HRIR for a given point source position is selected. As no interpolation between different HRIRs is performed, HRIR datasets with sufficient spatial resolution should be provided. + +### B.5.3 Initialization + +The HRIR filters used for binauralization are asynchronously partitioned and transformed into the frequency domain using a Fast Fourier Transform (FFT). The necessary steps for each of the $C$ HRIR filter pairs are as follows: + +- 1) Uniformly partition the length $N$ HRIR filter pairs $f_{c,L/R}(n)$ into $P = [N/B]$ filter partitions $f_{c,p,L/R}(n)$ of length $B$ . +- 2) Zero-pad the filter partitions to length $K$ . +- 3) Transform all filter partitions into the frequency domain using real-to-complex FFT to obtain the $P$ frequency domain filter pairs $F_{c,p,L/R}(k)$ , where $k$ denotes the frequency index. + +### B.5.4 Convolution and Crossfade + +Each audio block of a point source of the Scene Model is convolved with its selected HRIR filter pair for the left and right ear respectively. To reduce the computational complexity, a fast frequency domain convolution technique of uniformly partitioned overlap-save processing is useful for typical FIR filter lengths for HRIRs/BRIRs. The required processing steps are described in the following. + +The following block processing steps are performed for each of the $C$ point sources of the Scene Model: + +- a) Obtain a block of $B$ new input samples $x_c(n)$ of the point source $c$ . +- b) Perform a real-to-complex FFT transforms of length $K$ to obtain the frequency domain representation of the input $X_c(k)$ . +- c) Compute the frequency domain headphone output signal pair $Y_{c,L/R}(k)$ for the point source $c$ by multiplying each HRIR frequency domain filter partition $F_{c,p,L/R}(k)$ with the associated frequency domain input block and adding the product results over all partitions. +- d) $K$ samples of the time domain output signal pair $y_{c,L/R}(n)$ are obtained from $Y_{c,L/R}(k)$ by performing a complex-to-real IFFT. +- e) Only the last $B$ output samples represent valid output samples. The $K - B$ samples before are time-aliased and are discarded. +- f) In case of a HRIR filter exchange happens due to changes in the scene displacement, steps 3-5 are computed for both the current HRIR filter and the ones used in the previous block. A time-domain crossfade is performed over the $B$ output samples obtained in step 5: +- g) $y_{c,L/R}(n) = w_{in}(n)y_{c,L/R,current}(n) + w_{out}(n)y_{c,L/R,prev}(n)$ +- h) The crossfade envelopes are defined as + +$$w_{in}(n) = \sin^2\left(\frac{n\pi}{2B}\right)$$ + +$$w_{out}(n) = \cos^2\left(\frac{n\pi}{2B}\right)$$ + +to preserve a constant power of the resulting output signal. + +The crossfade operation defined in step 6 is only applied to point sources of the Scene Model that have been generated from channel or object content. For HOA content, the crossfade is applied between the current and the previous rotation matrices $T_{rot,hoa}$ (see B.4.2). + +### B.5.5 Binaural Downmix + +The rendered headphone output signal is computed as the sum over all binauralized point source signal pairs $y_{c,L/R}(n)$ . In case that the metadata provided together with the audio data at the input interface (see X.3.1) includes gain values applicable to a specific channel group (`gca_channelGain` in `mpegh3da_getChannelMetadata()`) or objects (`goa_objectGainFactor` in `mpegh3da_getObjectAudioAndMetadata()`), these gain values $g_c$ are applied to the corresponding binauralized point source signal $y_{c,L/R}(n)$ before the summation: + +$$y_{L/R}(n) = \sum_{c=0}^{C-1} g_c y_{c,L/R}(n)$$ + +Finally, any additional non-binauralized non-diegetic audio input ('gca\_directHeadphone == 1', see B.3.4) is added time-aligned to the two downmix channels. + +### B.5.6 Complexity + +The algorithmic complexity of the external binaural renderer using a fast convolution approach can be evaluated for the following computations: + +| | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Convolution (B.5.4) | 1) RFFT: $C * F * K * \log_2 K$
(with $F = 2.5$ as an estimated additional complexity factor for the FFT)
2) complex multiplications: $2 * P * C * \left\lceil \frac{K+1}{2} \right\rceil$
3) complex additions: $2 * P * \left\lceil \frac{K+1}{2} \right\rceil$
4) IRFFT: $2 * C * F * K * \log_2 K$ | +| Downmix (B.5.5) | 1) real multiplications: $2 * C * B$
2) real additions: $2 * C * B$ | +| Filter Exchange and Crossfade (B.5.4) | 1) RFFT: $2 * C * P * F * K * \log_2 K$
2) Time-domain crossfade (real multiplications): $4 * C * B$
3) Time-domain crossfade (real additions): $2 * C * B$ | + +Additional computations are required for scene displacement processing (see B.4). + +The total complexity per output sample can be determined by adding the complexity estimation for convolution and downmix and dividing by the block length $B$ . In blocks where a filter exchange is performed, items 2-4 from the convolution contribute two times to the overall complexity in addition to the time-domain crossfade multiplications and additions (filter exchange items 2 and 3). The partitioning and FFT for the filter exchange, as well as the scene displacement, can be performed independent of the input block processing. + +### B.5.7 Motion Latency + +The Scene Model can be updated with arbitrary temporal precision, but the resulting HRIR exchange is only done at processing block boundaries of the convolution. With a standard block size of $B = 256$ samples at 48 kHz sampling rate, this leads to a maximum onset latency of 5.3 ms until there is an audible effect of a motion of sources or the listener. In the following block, a time-domain crossfade between the new and the previous filtered signal is performed (see Convolution/Initialization), so that a discrete, instantaneous motion is completed after a maximum of two convolution processing blocks (10.6 ms for 512 samples at 48 kHz sampling rate). Additional latency from head trackers, audio buffering, etc. is not considered. + +The rotation of the HOA content is performed at a block boundary resulting in a maximum latency of one processing block, until a motion is completed. + +# Annex C (informative): Registration Information + +## C.1 3GPP Registered URIs + +The clause documents the registered URIs in this specification following the process in + +Table C-1 lists all registered URN values as well as: + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +**Table C-1: 3GPP Registered URNs** + +| URN | Description | Reference | Contact | Remarks | +|-------------------------------------|-----------------------------------------------------------------------|-----------------------------|---------------------------------------------|---------| +| urn:3GPP:vrstream:mp:video:basic | DASH profile identifier for VR Streaming Basic Video Media Profile | TS 26.118, clause 5.2.2.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:vrstream:mp:video:main | DASH profile identifier for VR Streaming Main Video Media Profile | TS 26.118, clause 5.2.3.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:vrstream:mp:video:advanced | DASH profile identifier for VR Streaming Advanced Video Media Profile | TS 26.118, clause 5.2.4.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:vrstream:ve: | Viewpoint Descriptor Scheme for Ensemble Signaling | TS 26.118, clause 5.2.3.3.4 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:vrstream:presentation | DASH profile identifier for VR DASH Media Presentation | TS 26.118, clause 8.3 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | + +# Annex D (informative): VR metrics calculation examples + +## D.1 Comparable quality viewport switching latency + +This sub-clause illustrates how the weighted average QR value and the effective resolution can be calculated. + +The quality level of each region is determined with its respective quality ranking (QR) value. A viewport can be covered with multiple regions. A quality level value for the viewport can be derived as weighted average of the QR values of the regions covering the viewport. The weight of each region is defined as the percentage of the viewport area covered by the corresponding region. The viewport quality level can be calculated by the following equation. + +$$QualityLevel(viewport) = \sum_{i=1}^N (QR[i] \times Coverage[i]/100)$$ + +$N$ : Number of regions covering the viewport + +$QR[i]$ : QR value of $i$ -th quality ranking region + +$Coverage[i]$ : The viewport coverage value (in percent) of $i$ -th quality ranking region + +![Diagram illustrating a viewport covered by four quality ranking 2D regions. The viewport is a central black rectangle. It is divided into four quadrants by a vertical and a horizontal line. The top-left quadrant is labeled 'Region [1]' and 'QualityRanking [1]'. The top-right quadrant is labeled 'Region [2]' and 'QualityRanking [2]'. The bottom-left quadrant is labeled 'Region [3]' and 'QualityRanking [3]'. The bottom-right quadrant is labeled 'Region [4]' and 'QualityRanking [4]'. The coverage percentages for each region are: 10% for Region [1], 35% for Region [2], 15% for Region [3], and 40% for Region [4]. Arrows point from the labels 'Coverage [1]', 'Coverage [2]', 'Coverage [3]', and 'Coverage [4]' to their respective percentages within the viewport.](0adcd19063a66145a465add40bf956e6_img.jpg) + +Diagram illustrating a viewport covered by four quality ranking 2D regions. The viewport is a central black rectangle. It is divided into four quadrants by a vertical and a horizontal line. The top-left quadrant is labeled 'Region [1]' and 'QualityRanking [1]'. The top-right quadrant is labeled 'Region [2]' and 'QualityRanking [2]'. The bottom-left quadrant is labeled 'Region [3]' and 'QualityRanking [3]'. The bottom-right quadrant is labeled 'Region [4]' and 'QualityRanking [4]'. The coverage percentages for each region are: 10% for Region [1], 35% for Region [2], 15% for Region [3], and 40% for Region [4]. Arrows point from the labels 'Coverage [1]', 'Coverage [2]', 'Coverage [3]', and 'Coverage [4]' to their respective percentages within the viewport. + +**Figure D.1-1: An example of a viewport covered by four quality ranking 2D region** + +Figure D.1-1 is an example of a viewport covered by four quality ranking regions. The quality of the viewport is equal to the weighted sum of the quality ranking value and the coverage percentage value of each quality ranking region. + +The resolution of each region is determined by its respective width and height values in pixel which are available in the quality ranking box under the name *orig\_width* and *orig\_height*. Note that these values are already normalized to represent the full-sphere resolution you would get if the resolution of this region would be used for the full sphere. + +The effective resolution (i.e. the total number of original pixels) for the content visible in the viewport can be derived as the weighted average of the resolution of each region covering the viewport. The weight of each region is defined by the percentage of the viewport area covered by the corresponding region. The effective viewport resolution can be calculated by the following equation. + +$$EffectiveResolution(viewport) = \sum_{i=1}^N (width[i] \times height[i] \times Coverage[i]/100)$$ + +$N$ : Number of regions covering the viewport + +$width[i]$ : The width component of the original source pixel resolution for the $i$ -th quality ranking region + +$height[i]$ : The height component of the original source pixel resolution for the $i$ -th quality ranking region + +$Coverage[i]$ : The viewport coverage value (in percent) of $i$ -th quality ranking region + +![Figure D.1-2: An example of a source packed image with four quality ranking 2D regions with different resolutions. The diagram shows a large rectangle divided into four regions: Region [1] (top-left, dark blue), Region [2] (top-right, medium blue), Region [3] (bottom-left, light blue), and Region [4] (bottom-right, very light blue). Each region contains a smaller rectangle representing its viewport coverage. Arrows labeled Coverage [1], Coverage [2], Coverage [3], and Coverage [4] point to these smaller rectangles.](4224f170b677d60f6f86ce95d8dc725a_img.jpg) + +Figure D.1-2: An example of a source packed image with four quality ranking 2D regions with different resolutions. The diagram shows a large rectangle divided into four regions: Region [1] (top-left, dark blue), Region [2] (top-right, medium blue), Region [3] (bottom-left, light blue), and Region [4] (bottom-right, very light blue). Each region contains a smaller rectangle representing its viewport coverage. Arrows labeled Coverage [1], Coverage [2], Coverage [3], and Coverage [4] point to these smaller rectangles. + +**Figure D.1-2: An example of a source packed image with four quality ranking 2D regions with different resolutions** + +![Figure D.1-3: An example of a viewport covered by four different quality ranking 2D regions. The diagram shows a black rectangle divided into four regions with their respective coverage percentages: 35% (top-left), 10% (top-right), 15% (bottom-left), and 40% (bottom-right). Arrows labeled Coverage [1], Resolution [1], Resolution [3], and Coverage [3] point to the top-left region. Arrows labeled Coverage [2], Resolution [2], Resolution [4], and Coverage [4] point to the top-right region. The word 'Viewport' is written in the center of the rectangle.](5ec2b6e9c9133bfbb26789d85dc49774_img.jpg) + +Figure D.1-3: An example of a viewport covered by four different quality ranking 2D regions. The diagram shows a black rectangle divided into four regions with their respective coverage percentages: 35% (top-left), 10% (top-right), 15% (bottom-left), and 40% (bottom-right). Arrows labeled Coverage [1], Resolution [1], Resolution [3], and Coverage [3] point to the top-left region. Arrows labeled Coverage [2], Resolution [2], Resolution [4], and Coverage [4] point to the top-right region. The word 'Viewport' is written in the center of the rectangle. + +**Figure D.1-3: An example of a viewport covered by four different quality ranking 2D regions** + +Figure D.1-2 is an example of a source with four regions with different resolution. Figure D.1-3 represents an example of a viewport which is covered by the four quality ranking 2D regions. The effective viewport resolution is equal to the weighted sum of the resolution for each quality-ranking 2D region and its corresponding viewport coverage percentage value. + +![Figure D.1-4: Comparable quality viewport switching latency measurement example. The diagram shows a sequence of five sub-pictures over time. The first sub-picture contains Sub-picture #0 and Sub-picture #1. The second sub-picture contains Sub-picture #0 and Sub-picture #1. The third sub-picture contains Sub-picture #0 and Sub-picture #1. The fourth sub-picture contains Sub-picture #0 and Sub-picture #1. The fifth sub-picture contains Sub-picture #0 and Sub-picture #1. Arrows labeled 'firstViewport' and 'secondViewport' point to the first and fifth sub-pictures respectively. A timeline at the bottom shows time points t0, t1, t2, t3, and t4. A double-headed arrow between t1 and t4 is labeled 'latency' and 'N ms'.](96c8d8b0159c47a7478ada46d781060b_img.jpg) + +Figure D.1-4: Comparable quality viewport switching latency measurement example. The diagram shows a sequence of five sub-pictures over time. The first sub-picture contains Sub-picture #0 and Sub-picture #1. The second sub-picture contains Sub-picture #0 and Sub-picture #1. The third sub-picture contains Sub-picture #0 and Sub-picture #1. The fourth sub-picture contains Sub-picture #0 and Sub-picture #1. The fifth sub-picture contains Sub-picture #0 and Sub-picture #1. Arrows labeled 'firstViewport' and 'secondViewport' point to the first and fifth sub-pictures respectively. A timeline at the bottom shows time points t0, t1, t2, t3, and t4. A double-headed arrow between t1 and t4 is labeled 'latency' and 'N ms'. + +**Figure D.1-4: Comparable quality viewport switching latency measurement example** + +Figure D.1-4 presents an example of the metric measurement operation. The viewport quality is evaluated at time $t_0$ , and then again at time $t_1$ . The media playback module renders the high-resolution sub-picture #1 at time $t_1$ . The user viewing orientation is gradually changing from sub-pic#1 to sub-pic#2 as the time progresses. + +At time $t_2$ , the media playback module starts to render the buffered low-quality representation of sub-pic#2 as the viewport moves into sub-picture #2. At time $t_2$ , the viewport quality drops in values as compared to the viewport quality at time $t_1$ , and a new sub-picture (sub-pic #2) is rendered. A viewport switching event is identified at time $t_2$ . + +The viewport quality values evaluated at $t_1$ identifies the first viewport. The viewport position and viewport quality level list are assigned to the attributed `Position` and `QualityLevel` of the `firstViewportItem`. + +An effective viewport resolution and viewport QR quality value for the new viewport that is comparable to that of the `firstViewportItem` after viewport switching time is logged at time $t_4$ . The new viewport position identifies the `Position` of the `secondViewportItem`. The corresponding `QualityLevel` list for the `secondViewportItem` is assigned. + +The associated viewport values stored for the worst viewport quality during the switch is assigned to the field `Position` of the `worstViewportItem`. The corresponding `QualityLevel` list for the `worstViewportItem` is also assigned. + +The comparable-quality viewport switching latency is measured as the time interval between the logged times for `firstViewportItem` ( $t_1$ in this example) and `secondViewportItem` ( $t_4$ in this example). + +## D.2 Rendered viewports + +**Error! Reference source not found.** illustrates an example of clustering and the associated viewports. The first three evaluated viewports are all with the distance $D$ (indicated by the blue circle), and are thus assigned to the same cluster. Note that the cluster center moves a bit for each new viewport which is added to the cluster. + +Viewport #4 is too far away from the center of cluster #1, and thus starts a new cluster, which eventually gathers three viewport members. Then viewport #7 is too far away from the center of cluster #2, and again starts a new cluster. + +![Figure D.2-1: Clustering example. The diagram shows a sequence of viewports over time (t1 to t10) being clustered into three groups. Cluster #1 (blue) includes viewports 1, 2, and 3. Cluster #2 (orange) includes viewports 4, 5, and 6. Cluster #3 (purple) includes viewports 7, 8, 9, and 10. A 'Radius = D' is indicated for Cluster #1. Below the timeline, a 'Average cluster viewports' section shows the final averaged viewports for each cluster: Cluster #1 (viewports 1, 2, 3), Cluster #2 (viewports 4, 5, 6), and Cluster #3 (viewports 7, 8, 9, 10).](34f46103a0c07981b0b51490ea639e25_img.jpg) + +Figure D.2-1: Clustering example. The diagram shows a sequence of viewports over time (t1 to t10) being clustered into three groups. Cluster #1 (blue) includes viewports 1, 2, and 3. Cluster #2 (orange) includes viewports 4, 5, and 6. Cluster #3 (purple) includes viewports 7, 8, 9, and 10. A 'Radius = D' is indicated for Cluster #1. Below the timeline, a 'Average cluster viewports' section shows the final averaged viewports for each cluster: Cluster #1 (viewports 1, 2, 3), Cluster #2 (viewports 4, 5, 6), and Cluster #3 (viewports 7, 8, 9, 10). + +Figure D.2-1: Clustering example + +For each cluster $j$ , the final averaged viewport parameters can be derived as follows, assuming there are $N$ viewports in the $j:th$ cluster. Note that the center azimuth and tilt averaging also needs to handle the special case around $-180/180$ + +degrees, as some values might be positive (e.g. 176 degrees), while others might be negative (e.g. -178 degrees). This special case is not shown in the equations below. + +Note also that the azimuth and elevation range (i.e. the visible coverage of the viewport) might often be the same for every viewport, unless the user explicitly changes the field-of-view for the device. For consistency, and to catch any during-session field-of-view changes, these two parameters should still be averaged. + +$$average\_centre\_azimuth[j] = \sum_{i=1}^N centre\_azimuth[i] / N$$ + +$$average\_centre\_elevation[j] = \sum_{i=1}^N centre\_elevation[i] / N$$ + +$$average\_centre\_tilt[j] = \sum_{i=1}^N centre\_tile[i] / N$$ + +$$average\_azimuth\_range[j] = \sum_{i=1}^N azimuth\_range[i] / N$$ + +$$average\_elevation\_range[j] = \sum_{i=1}^N elevation\_range[i] / N$$ + +Figure D.2-2 below illustrates an example of the duration filtering. The user starts by looking at the upper left part of the media (viewports #1 to #3), then make a very brief glance to the right (viewport #4), and then moves back to the upper-left again (viewports #5 and #6). Then the user moves his gaze to the lower-right part (viewports #7 to #10). + +Assume here that the duration $T$ is set to 4 times the value of the viewport sample rate $X$ , i.e. a cluster needs to have a duration corresponding to at least four viewports to be reported. Here four clusters are formed, but before filtering only cluster #4 would be reported. After filtering, clusters #1 and #3 are close enough both in time and distance to add to each other's aggregated duration, so each of them will be assigned an aggregated duration of 5, and thus be reported. Cluster #2, the quick glance up to the right, has too short duration and will not be reported. + +![Figure D.2-2: Duration filtering example. The diagram shows a sequence of viewports over time, grouped into clusters. The first row shows viewports 1-5, with clusters #1 (viewports 1-3), #2 (viewport 4), and #3 (viewport 5) starting. The second row shows viewports 6-10, with cluster #4 starting at viewport 7. The third row shows the 'Average cluster viewports' on a media plane, with clusters #1 and #3 merged into a single green area, cluster #4 as an orange rectangle, and cluster #2 as a small green area.](a0b72ad654428ce2b44766f24928643e_img.jpg) + +The diagram illustrates the duration filtering process. It is divided into three horizontal sections. The top section shows a sequence of viewports over time, from $t_1$ to $t_5$ . Viewport 1 is a green rectangle. Viewports 2 and 3 are also green rectangles, slightly overlapping 1. Viewport 4 is an orange rectangle. Viewport 5 is a green rectangle. A dashed line with arrows shows the gaze path: from 1 to 2, then to 3, then to 4, then to 5. Labels 'Cluster #1 started', 'Cluster #2 started', and 'Cluster #3 started' are present. A 'Radius = D' is indicated between viewports 1 and 2. The middle section shows viewports 6 to 10 over time $t_6$ to $t_{10}$ . Viewport 6 is green. Viewport 7 is purple. Viewports 8, 9, and 10 are green. A dashed line with arrows shows the gaze path: from 6 to 7, then to 8, then to 9, then to 10. A label 'Cluster #4 started' is present. The bottom section, titled 'Average cluster viewports', shows the spatial representation of the clusters. Cluster #1 and #3 are shown as a single large green area. Cluster #4 is shown as an orange rectangle. Cluster #2 is shown as a small green area. Arrows point from the viewports in the top and middle sections to their corresponding positions in the bottom section. + +Figure D.2-2: Duration filtering example. The diagram shows a sequence of viewports over time, grouped into clusters. The first row shows viewports 1-5, with clusters #1 (viewports 1-3), #2 (viewport 4), and #3 (viewport 5) starting. The second row shows viewports 6-10, with cluster #4 starting at viewport 7. The third row shows the 'Average cluster viewports' on a media plane, with clusters #1 and #3 merged into a single green area, cluster #4 as an orange rectangle, and cluster #2 as a small green area. + +Figure D.2-2 Duration filtering example + +# Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | SP-180270 | | | | Presented to TSG SA#80 (for information) | 1.0.0 | +| 2018-09 | SA#81 | SP-180647 | | | | Presented to TSG SA#81 (for approval) | 2.0.0 | +| 2018-09 | SA#81 | | | | | Approved at TSG SA#81 | 15.0.0 | +| 2018-12 | SA#82 | SP-180967 | 0001 | 2 | F | Corrections to 26.118 | 15.1.0 | +| 2019-09 | SA#85 | SP-190649 | 0002 | - | F | Correction of figure references | 15.2.0 | +| 2020-03 | SA#87-e | SP-200038 | 0003 | - | B | Addition of Feature | 16.0.0 | +| 2020-03 | SA#87-e | | | | | Editorial Correction in Change History, Copyright etc | 16.0.1 | +| 2020-03 | Post SA#87-e | | | | | Minor Editorial changes | 16.0.2 | +| 2020-12 | SA#90-e | SP-200932 | 0005 | | A | Corrections to Video Operation Points | 16.1.0 | +| 2021-01 | Post SA#90-e | | | | | Update of History Table | 16.1.1 | +| 2021-04 | SA#91-e | SP-210038 | 0006 | 4 | B | Operation Points for 8K VR 360 Video | 16.2.0 | +| 2021-04 | SA#91-e | | | | | This version is identical to 16.1.1 and to be used as the latest Rel 16 version. CR0006r4 had to be implemented on 16.1.1 to build Rel 17 version (instead, 16.2.0 has been inadvertently updated with CR0006r4 and hence this rollback was necessary). | 16.2.1 | +| 2021-06 | SA#92-e | SP-210532 | 0009 | | F | Spatial positioning of the chroma samples for VR Video Profiles | 16.3.0 | +| 2021-06 | SA#92-e | SP-210534 | 0007 | 2 | B | Operation Points for 8K VR 360 Video | 17.0.0 | +| 2021-06 | SA#92-e | SP-210534 | 0008 | | C | Addition of HLG transfer characteristics | 17.0.0 | +| 2021-06 | SA#92-e | SP-210533 | 0010 | 1 | F | Spatial positioning of the chroma samples for VR Video Profiles | 17.0.0 | +| 2023-03 | SA#99 | SP-230264 | 0011 | 2 | F | Reference Fixes and Clarifications | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26119/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/26_series/26119/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f3d816947470fd42ba5ee7c4b43f113316d390 --- /dev/null +++ b/marked/Rel-18/26_series/26119/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0f2f3f05c2f258cc06b98675fdb5a0880766815c614bc9a9253e43b7edabc75 +size 76702 diff --git a/marked/Rel-18/26_series/26119/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26119/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83ac732c679606986e90cd453bbaee68919ae368 --- /dev/null +++ b/marked/Rel-18/26_series/26119/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69d6c991505dcc6eadbb387b6f5d48fe093907a0b020ed6365d79de8031e1aa4 +size 9276 diff --git a/marked/Rel-18/26_series/26119/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26119/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea1bc2845a23309c2f92fda3f1eafffc3bd4aebd --- /dev/null +++ b/marked/Rel-18/26_series/26119/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41f8d26b0b717bc6cefec386e9b6d7945c3f7782f12d858245e5e72fdcd3b84c +size 5697 diff --git a/marked/Rel-18/26_series/26119/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-18/26_series/26119/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aac9e644fdd1cfe7147fe4be151c9d3192398d94 --- /dev/null +++ b/marked/Rel-18/26_series/26119/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbf8cbcd5759e1f0294689ed65fec660a03dbb38b6a83a8975952d33d98e3db2 +size 55583 diff --git a/marked/Rel-18/26_series/26119/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/26_series/26119/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..288524cbb124ca4605d096161392178c651a1260 --- /dev/null +++ b/marked/Rel-18/26_series/26119/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c07a6a285618e0fe99ca91f498c51425961cf7d236e0fe92b4c79a00603e450e +size 81421 diff --git a/marked/Rel-18/26_series/26119/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/marked/Rel-18/26_series/26119/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f2722fd75b592e19e0dd347588d7411efe381ad --- /dev/null +++ b/marked/Rel-18/26_series/26119/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d739fb215fb0ae0967d195cac1a8d8d9ef361a686f646edb07bcba93de034bc +size 97744 diff --git a/marked/Rel-18/26_series/26119/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Rel-18/26_series/26119/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbcdb8654dc9f60e26322729826416bc266e38be --- /dev/null +++ b/marked/Rel-18/26_series/26119/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46dc2c2f12b7e79ae341eaf93f5046083e5e34dabbc372a302e5a3128a1b9723 +size 70281 diff --git a/marked/Rel-18/26_series/26119/raw.md b/marked/Rel-18/26_series/26119/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b0cf9b353848bbf600bec1e0f602b3dc01c7c0a7 --- /dev/null +++ b/marked/Rel-18/26_series/26119/raw.md @@ -0,0 +1,1395 @@ + + +# 3GPP TS 26.119 V18.1.0 (2026-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Device Media Capabilities for Augmented Reality Services (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2026, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 XR concepts and device types ..... | 10 | +| 4.1 XR concepts ..... | 10 | +| 4.1.1 General ..... | 10 | +| 4.1.2 XR Device ..... | 10 | +| 4.1.3 XR application..... | 10 | +| 4.1.4 XR Runtime..... | 10 | +| 4.1.4.1 General..... | 10 | +| 4.1.4.2 XR session and rendering loop using XR Runtime (informative)..... | 11 | +| 4.2 Media pipelines and rendering loop..... | 12 | +| 4.3 Device Types..... | 13 | +| 4.3.1 Device type 1: Thin AR glasses ..... | 13 | +| 4.3.2 Device type 2: AR glasses..... | 13 | +| 4.3.3 Device type 3: XR phone ..... | 13 | +| 4.3.4 Device type 4: XR Head Mounted Display (HMD)..... | 13 | +| 5 Device reference architecture and interfaces ..... | 13 | +| 5.1 Architecture..... | 13 | +| 5.2 Description of the functional blocks ..... | 14 | +| 5.3 Interfaces and APIs ..... | 14 | +| 6 General system functions and capabilities ..... | 15 | +| 6.1 XR system capabilities..... | 15 | +| 7 Visual functions and capabilities ..... | 19 | +| 7.1 Decoding capabilities ..... | 19 | +| 7.1.1 Single decoder instance ..... | 19 | +| 7.1.2 Concurrent decoding capabilities ..... | 19 | +| 7.1.2.1 Definition..... | 19 | +| 7.1.2.2 Capabilities ..... | 20 | +| 7.2 Encoding capabilities ..... | 21 | +| 7.2.1 Single encoder instance ..... | 21 | +| 7.3 Capability exchange..... | 21 | +| 8 Audio functions and capabilities..... | 21 | +| 8.1 Audio/Speech Decoding..... | 21 | +| 8.2 Audio/Speech Encoding..... | 22 | +| 9 Scene processing capabilities..... | 22 | +| 9.1 General ..... | 22 | +| 9.2 glTF-based Scene Description capabilities ..... | 22 | +| 10 Device types and media profiles ..... | 23 | +| 10.1 Introduction ..... | 23 | +| 10.2 Device type 1: Thin AR glasses ..... | 24 | +| 10.2.1 General ..... | 24 | +| 10.2.2 XR System support..... | 24 | +| 10.2.3 Video capabilities support ..... | 24 | +| 10.2.4 Audio/Speech capabilities support ..... | 24 | +| 10.2.5 Scene Description capabilities support..... | 25 | + +| | | | +|-------------------------------|----------------------------------------------------|-----------| +| 10.3 | Device type 2: AR glasses..... | 25 | +| 10.3.1 | General ..... | 25 | +| 10.3.2 | XR System support..... | 25 | +| 10.3.3 | Video capabilities support ..... | 26 | +| 10.3.4 | Audio/Speech capabilities support ..... | 26 | +| 10.3.5 | Scene Description capabilities support..... | 26 | +| 10.4 | Device type 3: XR phone ..... | 27 | +| 10.4.1 | General ..... | 27 | +| 10.4.2 | XR System support..... | 27 | +| 10.4.3 | Video capabilities support ..... | 27 | +| 10.4.4 | Audio/Speech capabilities support ..... | 28 | +| 10.4.5 | Scene Description capabilities support..... | 28 | +| 10.5 | Device type 4: XR HMD..... | 28 | +| 10.5.1 | General ..... | 28 | +| 10.5.2 | XR System support..... | 28 | +| 10.5.3 | Video capabilities support ..... | 29 | +| 10.5.4 | Audio/Speech capabilities support ..... | 29 | +| 10.5.5 | Scene Description capabilities support..... | 30 | +| 11 | QoE metrics..... | 30 | +| 11.1 | Metrics and Observation Points ..... | 30 | +| 11.1.1 | Overview ..... | 30 | +| 11.1.2 | Observation Point 1: XR Runtime information ..... | 30 | +| 11.1.3 | Observation Point 2 ..... | 31 | +| 11.1.4 | Observation Point 3 ..... | 31 | +| 11.1.5 | Observation Point 4 ..... | 31 | +| 11.2 | Metrics Definitions..... | 31 | +| 11.2.1 | Latency metrics ..... | 31 | +| 12 | Metadata formats..... | 33 | +| 12.1 | General ..... | 33 | +| 12.2 | Pose format..... | 33 | +| 12.3 | Action format ..... | 34 | +| 12.4 | Available Visualization Space format..... | 35 | +| 12.5 | Device capabilities signalling..... | 36 | +| Annex A (informative): | Registration Information ..... | 38 | +| A.1 | 3GPP Registered URIs..... | 38 | +| Annex B (informative): | XR Runtime interface ..... | 42 | +| B.1 | Introduction ..... | 42 | +| B.2 | Capability mapping to OpenXR..... | 42 | +| B.2.1 | Mapping overview..... | 42 | +| B.2.2 | XR views and rendering loop..... | 45 | +| B.2.3 | Available Visualization Space implementation ..... | 46 | +| B.2.3.1 | Using OpenXR_XR_FB..... | 46 | +| B.2.3.2 | Using xrComputeNewSceneMSFT ..... | 46 | +| Annex C (informative): | Change history ..... | 48 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +The present document provides technologies for the deployment of Augmented Reality (AR) as defined in 3GPP TR 26.928 [2] and the execution of Augmented Reality applications on targeted devices such as those identified in 3GPP TR 26.998 [3]. + +On the spectrum of eXtended Reality (XR) experiences, Augmented Reality overlay virtual information on top of the user's perception of the real environment. Those virtual and real components of the scene seamlessly blend together from the user's perspective. Additionally, some AR experiences can enable interactivity between the user and the virtual components of the scene. + +In the present document, the focus lies in the definition of the media capabilities for AR devices, including media format encapsulation capabilities, media codec capabilities, processing function capabilities. The related minimum required performances for different device types are also defined. + +# --- 1 Scope + +The present document defines the supported media formats, codecs, processing functions for XR Devices in UE per XR device type category. The present document addresses the interoperability gaps identified in the conclusions of TR 26.998 [3]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 26.928: "Extended Reality (XR) in 5G". +- [3] 3GPP TR 26.998: "Support of 5G glass-type Augmented Reality / Mixed Reality (AR/MR) devices". +- [4] 3GPP TR 26.857: "5G Media Service Enablers". +- [5] Khronos, "The OpenXR Specification", . +- [6] 3GPP TS 26.506: "5G Real-time Media Communication Architecture (Stage 2)". +- [7] ITU-T Recommendation H.264 (08/2021): "Advanced video coding for generic audiovisual services". +- [8] ITU-T Recommendation H.265 (08/2021): "High efficiency video coding". +- [9] 3GPP TS 26.117: "5G Media Streaming (5GMS); Speech and audio profiles". +- [10] ISO/IEC 12113:2022 Information technology Runtime 3D asset delivery format Khronos glTF™2.0 +- [11] ISO/IEC 23090-14:2023 Information technology Coded representation of immersive media Part 14: Scene description +- [12] ISO/IEC 23090-14:2023/Amd 1:2023 Information technology Coded representation of immersive media Part 14: Scene description +- [13] ISO/IEC 23090-14:2023/DAm d 2 Information technology Coded representation of immersive media Part 14: Scene description + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Anchor:** a virtual element for which its position, orientation, scale and other properties are expressed in the trackable space defined by the trackable. A virtual asset's position, orientation, scale and other properties are expressed in relation to an anchor. + +**Media Session Handler:** a set of functions responsible for handling all 5G control plane operations, such as requesting network assistance, discovering and allocating edge resources, etc. + +**Presentation Engine:** a set of composite renderers, rendering the component of the scenes. + +**Reference Points:** geometric points whose position is identified both mathematically and physically. + +**Trackable:** a real-world object that can be tracked by the XR runtime. Each trackable provides a local reference space, also known as a trackable space, in which an anchor can be expressed. + +**Swapchain:** a queue of images shared between the XR Application and the XR Runtime + +**Swapchain image:** image in a swapchain. + +**XR Application:** application running on an XR Device which offers an XR experience based on an XR Runtime. + +**XR Device:** a device capable of offering an XR experience. + +**XR Runtime:** Set of functions provided by the XR Device to the XR Application to create XR experiences. + +**XR Runtime API:** the API to communicate with an XR Runtime. + +**XR Scene Manager:** a set of functions that supports the application in arranging the logical and spatial representations. + +**XR Session:** an application's intention to present XR content to the user. + +**XR Source Management:** management of data sources provided through the XR runtime. + +**XR System:** a collection of resources and capabilities from the XR Runtime exposed to the XR Application for the duration of the XR Session. + +**XR View:** a rendered view of the scene generated by the XR Application and passed on to the XR Runtime during a running XR Session +**XR Space:** a frame of reference in which 3D coordinates are expressed. + +**Warping:** correcting the rendered image based on the latest head pose estimation + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|--------------------------------------| +| API | Application Programming Interface | +| AR | Augmented Reality | +| AAC | Advanced Audio Coding | +| AVC | Advanced Video Coding | +| CPB | Coded Picture Buffer | +| DPB | Decoded Picture Buffer | +| ELD | Enhanced Low Delay | +| EVS | Enhanced Voice Services | +| gITF | graphics library Transmission Format | + +| | | +|---------|---------------------------------------| +| GLB | glTF Binary | +| HEVC | High Efficiency Video Coding | +| HMD | Head-Mounted Display | +| HRD | Hypothetical Reference Decoder | +| HSS | Hypothetical Stream Scheduler | +| IVAS | Immersive Voice and Audio Services | +| JSON | JavaScript Object Notation | +| MPEG | Moving Picture Expert Group | +| MPEG SD | MPEG Scene Description | +| MR | Mixed Reality | +| OP | Observation Point | +| SLAM | Simultaneous Localisation And Mapping | +| UE | User Equipment | +| VCL | Video Coding Layer | +| VR | Virtual Reality | +| XR | eXtended Reality | + +# --- 4 XR concepts and device types + +## 4.1 XR concepts + +### 4.1.1 General + +Extended Reality (XR) refers to a continuum of experiences combine real-a and- virtual combined environments in which the user is immersed through one or more devices capable of audio, visual and haptics rendering generated by computers through human-machine interaction. XR encompasses technologies associated with Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR) which constitute the so-called XR continuum. A detailed overview of definitions, concepts and background on XR and AR is provided in TR 26.928 [2] and TR 26.998 [3], respectively. + +The terms Augmented Reality, Virtual Reality, Mixed Reality and eXtended Reality as used throughout this document are defined in Clause 4.1 of 3GPP TR 26.928 [2]. + +### 4.1.2 XR Device + +An XR device is capable of offering an XR experience. An XR Device is assumed to have one or several displays, speakers, sensors, cameras, microphones, actuators, controllers and/or other peripherals that allow to create XR experiences, i.e. experiences for which the user interacts with the content presented in virtual world and/or augmented to the real-world. Example of XR Devices are AR Glasses, a VR/MR Head-Mounted Display (HMD) or a regular smartphone, etc. + +### 4.1.3 XR application + +An application which offers an XR experience by making use of the hardware capabilities, including media capabilities, of the XR Device it runs on as well as the network connectivity to retrieve the asset being used by the application is referred to as an XR Application. In the context of this specification, it is primarily assumed that access to the network is provided by 5G System functionalities. + +To enable XR experiences, the hardware on an XR Device typically offers a set of functions to perform commonly required XR operations. These operations include, but are not limited to: + +- accessing controller/peripheral state, +- getting current and/or predicted tracking positions and pose information of the user, +- receiving or generating pre-rendered views of the scene for final presentation to the user, taking into account the latest user position and pose. Adaptation to the latest user position and pose is also referred to as warping. + +### 4.1.4 XR Runtime + +#### 4.1.4.1 General + +XR Runtime provides a set of functionalities to XR applications including but not limited to peripheral management, runtime functions as tracking, SLAM, composition and warping etc. The functions are accessible to the XR Application via an API exposed by the XR Runtime referred to as the XR Runtime Application Programming Interface (XR API). The XR Runtime typically handles functionalities such as composition, peripheral management, tracking, Spatial Localization and Mapping (SLAM), capturing and audio-related functions. Further, it is assumed that the hardware and software capabilities of the XR Device are accessible through well-defined device APIs, and in particular the media capabilities are accessible through media APIs. + +An overview of an XR Device logical components is shown in Figure 4.1.4-1. + +![Figure 4.1.4-1: Logical components of an XR Device. The diagram shows an XR Device containing an XR Runtime, an XR Application, and Network connectivity (5G System Uu). The XR Runtime is connected to various hardware components (Controllers, Sensors, Cameras, Actuators, Displays, Speakers, Microphones) and provides an XR Runtime API. The XR Runtime also interacts with the XR Application. The XR Application interacts with the Network connectivity and with Device APIs and Media APIs. The Device APIs and Media APIs are part of the Device Hardware and Software Capabilities.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the logical components of an XR Device. It is structured as follows: + +- XR Device:** The overall container for all components. + - XR Runtime:** A central component that manages hardware resources and provides an API. It includes: + - Controllers, Sensors, Cameras, Actuators, Displays, Speakers, Microphones (hardware interfaces). + - Internal modules: peripheral management, Runtime functions (tracking, SLAM), Composition and Warping, Synchronization and Spatial Alignment, Capturing, and Audio Subsystem. + - XR Runtime API:** A vertical oval representing the interface between the XR Runtime and the XR Application. + - XR Application:** An orange oval that interacts with the XR Runtime API and has bidirectional connections to Network connectivity (5G System Uu) and Device APIs. + - Device Hardware and Software Capabilities:** A green rectangular area containing: + - Device APIs:** A light green oval that interacts with the XR Application. + - Media APIs:** A light green oval that interacts with the XR Application. + - Media Capabilities:** A light green rectangle within the Media APIs. + - Network connectivity (5G System Uu):** A purple rectangle that interacts with the XR Application. + +Figure 4.1.4-1: Logical components of an XR Device. The diagram shows an XR Device containing an XR Runtime, an XR Application, and Network connectivity (5G System Uu). The XR Runtime is connected to various hardware components (Controllers, Sensors, Cameras, Actuators, Displays, Speakers, Microphones) and provides an XR Runtime API. The XR Runtime also interacts with the XR Application. The XR Application interacts with the Network connectivity and with Device APIs and Media APIs. The Device APIs and Media APIs are part of the Device Hardware and Software Capabilities. + +**Figure 4.1.4-1 Logical components of an XR Device** + +This specification relies on a hypothetical XR Runtime and its API in order to define the media capabilities. This way, different implementation of XR runtimes may be compatible with this specification. However, for the purpose of developing this specification, the minimal set of expected functionalities of the XR Runtime has been aligned with the core Khronos' OpenXR specification [5]. Support for other XR Runtime environments is not precluded by this approach. Lastly, a mapping of general functionalities to OpenXR is provided in Annex B. + +#### 4.1.4.2 XR session and rendering loop using XR Runtime (informative) + +At startup, the XR Application creates an XR Session via the XR Runtime API and allocates the necessary resources from the available resources on the XR Device. Upon success, the XR Runtime begins the life cycle of the XR Session whose cycle is typically made of several states. The purpose of those states is to synchronise the rendering operations controlled by the XR Application with the display operations controlled by the XR Runtime. The rendering loop is thus a task jointly executed by the XR Runtime and the XR Application and synchronised via the states of the XR Session. + +The XR Application is responsible of generating a rendered view of the scene from the perspective of the user. To this end, the XR Application produces XR Views which are passed to the XR Runtime at iterations of the rendering loop. The XR Views are generated for one or more poses in the scene for which the XR application can render images. From those views, the view corresponding to the viewer's pose is typically called the primary view. There may be other XR Views defined in the scene, for instance for spectators. + +The XR Views are configured based on the display properties of the XR Device. A typical head-mounted XR System has a stereoscopic view configuration, i.e. two views, while a handheld XR Device has a monoscopic view configuration, i.e. a single view. Other view configurations may exist. At the start of session, the XR Application configures the view type based on those device properties which remains the same for the duration of the XR Session. + +A XR View may also comprise one or more composition layers associated with an image buffer. Those layers are then composed together by the XR Runtime to form the final rendered images. + +In addition to layers containing visual data, an XR View may be complemented with a layer provided depth information of the scene associated with this XR View. This additional information may help the XR Runtime to perform pose correction when generating the final display buffer. Another type of layer can be an alpha channel layer useful for blending the XR View with the real environment for video-see through XR devices, e.g. which is the case for AR applications running on smartphones. + +For the XR Application to render the XR Views, the XR Runtime provides the viewer pose as well as projection parameters which are typically taken into account by applications to render those different XR Views. The viewer pose and projection parameters are provided for a given display time in the near future. The XR Runtime accepts repeated + +calls for prediction updates of the pose, which may not necessarily return the same result for the same target display time. Instead, the prediction gets increasingly accurate as the function is called closer to the given time for which a prediction is made. This allows an application to prepare the predicted views early enough to account for the amount of latency in the rendering while at the same time minimising the prediction error when pre-rendering the views. + +In addition, the XR Application communicates with input devices in order to collect actions. Actions are created at initialization time and later used to request input device state, create action spaces, or control haptic events. Input action handles represent 'actions' that the application is interested in obtaining the state of, not direct input device hardware. + +![Figure 4.1.4-1: Rendering loop for visual data. This diagram shows the interaction between the XR Runtime and the XR Application within an XR Device. The XR Runtime (red box) includes components for peripheral management, runtime functions (tracking, SLAM), and composition and warping. It is connected to external hardware: Controllers, Sensors, Cameras, and Displays. The XR Application (orange oval) contains a 'Rendering' block. Data flow includes: 'Actions' from the Runtime to the Application; 'Viewer pose at expected display time' from the Runtime's runtime functions to the Application's Rendering block; and a 'Swapchain Rendering Loop' from the Application's Rendering block back to the Runtime's composition and warping block. The Rendering block also receives 'Composition Layers + display time + render pose@XRSpace' from the Application.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Figure 4.1.4-1: Rendering loop for visual data. This diagram shows the interaction between the XR Runtime and the XR Application within an XR Device. The XR Runtime (red box) includes components for peripheral management, runtime functions (tracking, SLAM), and composition and warping. It is connected to external hardware: Controllers, Sensors, Cameras, and Displays. The XR Application (orange oval) contains a 'Rendering' block. Data flow includes: 'Actions' from the Runtime to the Application; 'Viewer pose at expected display time' from the Runtime's runtime functions to the Application's Rendering block; and a 'Swapchain Rendering Loop' from the Application's Rendering block back to the Runtime's composition and warping block. The Rendering block also receives 'Composition Layers + display time + render pose@XRSpace' from the Application. + +Figure 4.1.4-1 Rendering loop for visual data + +## 4.2 Media pipelines and rendering loop + +In the context of this specification, media to be rendered and displayed by the XR Device through the XR Runtime is typically available in an compressed form on the device. Media is accessed using a 5G System, decoded in the device using media capabilities, and then the decoded media is rendered to be provided through swapchains to the XR Runtime as shown in Figure 4.2-1. + +![Figure 4.2-1: Media pipelines: Access, decoding and rendering. This diagram illustrates the media pipeline within an XR Device. The XR Runtime (red box) on the left includes components for peripheral management, runtime functions (tracking, SLAM), composition and warping, synchronization and spatial alignment, capturing, and an audio subsystem. It is connected to external hardware: Controllers, Sensors, Cameras, Actuators, Displays, Speakers, and Microphones. The XR Application (orange oval) contains 'Media APIs' which interface with 'Media Capabilities' (green box). The Media Capabilities box contains 'Access', 'Decoding', and 'Rendering' blocks. Data flow: '5G System (Uu)' (purple box) provides data to 'Access', which goes to 'Decoding', then 'Rendering'. The 'Rendering' block sends data to the 'Swapchain Rendering Loop' in the XR Runtime. A dashed line labeled 'Viewer Pose' is shown between the XR Runtime and the Media APIs.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +Figure 4.2-1: Media pipelines: Access, decoding and rendering. This diagram illustrates the media pipeline within an XR Device. The XR Runtime (red box) on the left includes components for peripheral management, runtime functions (tracking, SLAM), composition and warping, synchronization and spatial alignment, capturing, and an audio subsystem. It is connected to external hardware: Controllers, Sensors, Cameras, Actuators, Displays, Speakers, and Microphones. The XR Application (orange oval) contains 'Media APIs' which interface with 'Media Capabilities' (green box). The Media Capabilities box contains 'Access', 'Decoding', and 'Rendering' blocks. Data flow: '5G System (Uu)' (purple box) provides data to 'Access', which goes to 'Decoding', then 'Rendering'. The 'Rendering' block sends data to the 'Swapchain Rendering Loop' in the XR Runtime. A dashed line labeled 'Viewer Pose' is shown between the XR Runtime and the Media APIs. + +Figure 4.2-1 Media pipelines: Access, decoding and rendering + +The rendering function is responsible of generating the content that will be presented by the XR Runtime. This rendering function makes use of rendering loops and provide the results of those loops to the XR Runtime via + +swapchains. The application sets up different pipeline that comprise processes for media access, decoding, and view rendering. To configure those pipelines and the properties of the generated views (e.g. number of layers, stereoscopic/monoscope views), the rendering function needs to have access to the information about the current session defined at the initialisation step: + +- View configuration +- Blend modes +- XR spaces +- swap chain formats and images +- projection layer types + +## 4.3 Device Types + +### 4.3.1 Device type 1: Thin AR glasses + +The thin AR glasses device type represents a type of device which is considered as power-constrained and with limited computing power with respect to the other device types. These limitations typically come from the requirement to design a device with a small and lightweight form factor. Regarding rendering capacity, this device type is expected to rely on remote rendering to be able display complex scenes to the user. For example, such device type may run a split rendering session where the split rendering server delivers pre-rendered views of the scene. However, devices in this category can still operate without external support for applications that do not require complex rendering capabilities, for instance, text messaging, 2D video communication, etc. Lastly, the thin AR glasses offers AR experiences to the user via optical see-through display. + +### 4.3.2 Device type 2: AR glasses + +The AR glasses device type represents a type of device which is considered to have higher computation power compared to the thin AR glasses device type. As a result, this AR device type has higher rendering capacities and is generally expected to be capable of rendering scenes without external support, even though remote rendering is not precluded to lower the power consumption on the device or enable the display of scenes beyond the device's rendering capability. Lastly, the AR glasses offers AR experiences to the user via optical see-through display. + +### 4.3.3 Device type 3: XR phone + +The XR phone device type represents a type of device which corresponds to a smartphone with capacities and resources sufficient to offer AR experiences. As a result, this device type is capable of rendering scenes without external support. Lastly, the XR phone offers AR experiences to the user via video see-through display. + +### 4.3.4 Device type 4: XR Head Mounted Display (HMD) + +The XR HMD device type represents a type of device which corresponds to HMDs capable of offering at least AR experiences but not precluding other types of XR experiences. This device type is expected to be capable of rendering scenes without external support. Lastly, the XR phone offers AR experiences to the user via video see-through display. + +# --- 5 Device reference architecture and interfaces + +## 5.1 Architecture + +The XR Baseline Client represents the functionalities, the peripherals, and the interfaces that are present on a generic XR UE. The XR Baseline Client reference architecture is shown in Figure 5.1-1. The actual device may be realized by a single device, or a combination of devices linked together. The details on how to instantiate an XR Baseline Client in the context of a service or deployment scenario is left for the respective Work Items and Study Items to define. + +![Figure 5.1-1 - XR Baseline terminal architecture and interfaces. The diagram shows the internal components of an XR Baseline Client and its interfaces to external systems. The client contains an Application, XR Runtime, XR Source Management, Presentation engine, Scene Manager, and Media Access Function. It interfaces with Sensors, Cameras, Actuators, Displays, Speakers, Microphones, and a 5G System (Uu).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the XR Baseline terminal architecture. At the top, 'User input' feeds into the 'Application' block. The 'Application' is connected to several functional blocks via interfaces: IF-1a, IF-2, IF-10, IF-7, IF-6, and IF-8. The 'XR Runtime' block (containing 'Runtime functions (tracking, SLAM...)') connects to the 'Application' via IF-1a and to 'XR Source Management' via IF-1b. 'XR Source Management' (containing API-2) connects to the 'Application' via IF-2 and to the 'Presentation engine' via IF-3. The 'Presentation engine' (containing 'Visual renderer' and 'Audio renderer') connects to the 'Scene Manager' via IF-9. The 'Scene Manager' connects to the 'Media Access Function' (containing API-7) via IF-6. The 'Media Access Function' connects to the 'Media Session handler' (containing API-6) via IF-7. The 'Media Session handler' connects to the 'Application' via IF-6 and to the '5G System (Uu)' via IF-5. The '5G System (Uu)' connects to the 'Application' via IF-8 and to the 'Media Access Function' via IF-4. External components include 'Sensor', 'Cameras', 'Actuators', 'Displays', 'Speakers', and 'Microphones' which connect to the 'XR Runtime' via API-1. + +Figure 5.1-1 - XR Baseline terminal architecture and interfaces. The diagram shows the internal components of an XR Baseline Client and its interfaces to external systems. The client contains an Application, XR Runtime, XR Source Management, Presentation engine, Scene Manager, and Media Access Function. It interfaces with Sensors, Cameras, Actuators, Displays, Speakers, Microphones, and a 5G System (Uu). + +Figure 5.1-1 - XR Baseline terminal architecture and interfaces + +## 5.2 Description of the functional blocks + +In terms of functionalities, an XR Baseline Client is composed of: + +- An **XR Application**: a software application that integrates audio-visual content into the user's real-world environment +- An **XR Runtime**: a set of functions that interface with a platform to perform commonly required operations, such as accessing the controller/peripheral state, getting current and/or predicted tracking positions, performing spatial computing, as well as submitting rendered frames to the display processing unit and rendered audio to the speakers with a late stage re-projection to the latest pose (see clause 4.1.3). +- An **XR Source Management**: management of data sources provided through the XR runtime such as microphones, cameras, trackers, etc, for instance, making the information available to the XR application or providing it to the MAF for sending in the uplink. +- A **Media Access Function**: A set of functions that enables access to media and other XR-related data that is needed in the Scene manager or XR Runtime to provide an XR experience as well to create delivery formats for information provided by the XR Source Management. +- A **Scene Manager**: a set of functions that supports the application in arranging the logical and spatial representation of a multisensorial scene based on support from the XR Runtime. +- A **Presentation Engine**: a set of composite renderers, rendering the component of the scenes, based on the input from the Scene Manager. +- A **Media Session Handler**: a set of functions responsible for handling all 5G control plane operations, such as requesting network assistance, discovering and allocating edge resources, etc. This may be realized as a 5G-RTC MSH, 5GMS Media Session Handler, or any other function. In addition, those functional blocks are integrated together via interfaces. Interfaces may be made of APIs and/or data formats and collectively act as a contract between the two sides of the interface. + +In addition, those functional blocks are integrated together via interfaces. Interfaces may be made of APIs and/or data formats and collectively act as a contract between the two sides of the interface. + +## 5.3 Interfaces and APIs + +The XR Baseline Client contains the following interfaces: + +- **IF-1** for the XR Runtime on one side and the Application (1a), the XR Source Management (1b) and the Presentation Engine (1c). IF-1a-c is implemented as an API (API-1) that exposes functions provided by the XR Runtime. An example of this API is the Khronos OpenXR API. +- **IF-2** describes the functions exposed by the XR Source Management that can be accessed and controlled by the XR application, or possibly other functions in the device. IF-2 is typically implemented as an API. +- **IF-3** lies between the XR Source Management and the Media Access Function and provides serialized information accessible on XR Runtime to the MAF. +- **IF-4** between the Media Access Function and the 5G System for user plane data, such as application data or other graphics data needed by the XR application. +- **IF-5** lies between the UE and the 5G System, implementing control sessions. An example instance of this interface is the RTC-5 interface as defined by TS 26.506 [6]. +- **IF-6** connects the Media Session Handler and the Application/MAF. It offers the tools for them to activate 5G media functionality such as network assistance and edge resource discovery. The IF-6 is realized through an API (API-6). +- **IF-7** lies between the XR Application and the Media Access function to configure Media Access. This is typically implemented as an API (API-7) that exposes functions of the MAF. +- **IF-8** is an interface that allows the XR application to make use of 5G System connectivity. +- **IF-9** between the Scene Manager and the Media Access Function. +- **IF-10** between the Scene Manager and the XR Application. + +# 6 General system functions and capabilities + +## 6.1 XR system capabilities + +The XR Runtime comprises functions and hardware components present on the XR Device. However, those functions and hardware components are not directly exposed to the XR Application. Instead, the XR Runtime offers its functions and hardware components via an XR System. A single XR Runtime may expose more than one XR Systems for targeting different purposes, e.g., a handheld device may have two XR Systems, one when the user holds the device and one when the device is inserted into an HMD. At the start of the XR Application, the XR Application is expected to query what XR Systems are available on the XR Device and select one of them to create the XR Session. + +Table 6.1-1 provides capabilities for XR Runtimes exposed through an XR System. This table does not prescribe support for any specific capabilities of an XR device as defined in clause 4.3. The support of XR System capabilities is defined per device category in clause 10. A mapping of these high-level capabilities to XR frameworks are provided in Annex B. + +**Table 6.1-1 XR System capabilities** + +| Capability | Description | Parameters | Value type | Parameter definitions | +|----------------------------------------------|-----------------------------------------------------------|-------------------------|------------|----------------------------------------------------------| +| Create a XR System | An application can create a XR System from an XR Runtime. | xrSystemIdentifier | integer | Identifier of a given XR System exposed by a XR Runtime. | +| Query XR System's graphics properties | An application can query an XR System about its | swapchainSupported | boolean | Indicates whether the XR System supports the swapchains. | +| | | maxSwapchainImageHeight | integer | The maximum swapchain image pixel | + +| | | | | | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | graphics capabilities. | | | height supported by this XR system. | +| | | maxSwapchainImageWidth | integer | The maximum swapchain image pixel height supported by this XR system. | +| | | maxLayerCount | integer | The maximum number of composition layers supported by this XR system | +| Query XR System's tracking properties | An application can query an XR System on the tracking capabilities. | orientationTracking | boolean | Indicates whether the XR System supports orientational tracking of the view pose(s), or not. | +| | | positionTracking | boolean | Indicates whether the XR system supports positional tracking of the view pose(s), | +| Enumerate XR System's supported environment blend modes | An application can query an XR System about its supported environment blend modes, see clause [xxx]. | blendMode | ['opaque', 'additive', 'alpha_blend'] | Indicates the type of blend mode supported by the XR System.

The value 'opaque' relates to the opaque blend mode, the value 'additive' to the additive blend mode and 'alpha_blend' to the alpha blend mode. | +| Enumerate supported view configuration types | An application can query an XR System about the its supported primary view configurations . | viewConfigurationPrimary | ['monoscopic', 'stereoscopic', 'other'] | Indicates the type of primary view configuration of the XR System.

The value 'monoscopic' relates to a single view, the value 'stereoscopic' to the left and right-eye views and 'other' to a type undefined in the scope of this specification. | +| Enumerate the view configuration properties | An application can list the properties associated with different view configurations advertised by an XR System. | recommendedImageRectWidth | integer | The optimal width of imageRect to use when rendering this view into a swapchain. | +| | | maxImageRectWidth | integer | The maximum width of imageRect supported when rendering this view into a swapchain. | +| | | recommendedImageRectHeight | integer | The optimal height of imageRect to use when | + +| | | | | | +|-------------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | rendering this view into a swapchain | +| | | maxImageRectHeight | integer | The maximum height of imageRect supported when rendering this view into a swapchain. | +| | | recommendedSwapchainSampleCount | integer | The recommended number of sub-data element samples to create for each swapchain image that will be rendered into for this view. | +| | | maxSwapchainSampleCount | integer | The maximum number of sub-data element samples supported for swapchain images that will be rendered into for this view. | +| Enumerate reference space types | An application can query an XR System about the supported reference space types, described in [xxx]. | referenceSpaceView | ['view', 'local', 'stage', 'unbounded', 'user_defined'] | Indicates the type of reference spaces supported by the XR System.

The value 'view' relates to view reference space, the value 'local' to the local reference space, the value 'stage' to the stage reference space, the value 'unbounded'. | +| Query the spatial range boundaries | An application can query the spatial ranges in which an XR experience may be rendered. | 2DSpatialRangeBoundaries | rectangle | Provides the rectangle centered on the origin of a given reference space in which the user can freely move. | +| Enumerate swapchain image formats | An application can query the swapchain image formats supported by an XR System. | swapchainImageFormatIdentifier | enumeration | Provides an identifier of a swapchain image format that the XR System supports. | +| Enumerate swapchain images | An application can list the swapchain images allocated to a swapchain. | numberSwapchainImages | enumeration | Provides the number of images allocated for a given swapchain. | +| | | swapchainImages | object | Provide the implementation-specific swapchain image objects for a given swapchain. | + +| | | | | | +|-------------------------------------------|--------------------------------------------------------------------------------|----------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Enumeration composition layer type | An application can list the composition layer types supported by an XR System. | compositionLayerProjection | ['projection', 'quad', 'cylinder', 'cube', 'equirectangular', 'depth'] |

Indicates the type of composition layers supported by the XR Systems supports.

The value 'projection' represents planar projected images, one rendered for each eye using a perspective projection.

The value 'quad' represents quad composition layers which are useful for rendering user interface elements or 2D content on a planar area in the world.

The value 'cylinder' represents cylinder composition layers which maps the texture onto the inside of a cylinder section.

The value 'cube' represents cube composition layer which consists of a cube map with six views to be rendered by the application.

The value 'equirectangular' represents equirectangular composition layers which consists of an equirectangular image that is mapped onto the inside of a sphere in the world.

The value 'depth' represents depth composition layers which allows submitting depth maps as an extra composition layer to be used by the XR Runtime for pose correction.

| +|-------------------------------------------|--------------------------------------------------------------------------------|----------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# 7 Visual functions and capabilities + +## 7.1 Decoding capabilities + +### 7.1.1 Single decoder instance + +The following video decoding capabilities are defined: + +- **AVC-FullIHD-Dec:** the capability to decode H.264 (AVC) Progressive High Profile Level 4.0 [7] bitstreams. +- **AVC-UHD-Dec:** the capability to decode H.264 (AVC) Progressive High Profile Level 5.1 [7] bitstreams with the following additional requirements: + - the maximum VCL Bit Rate is constrained to be 120 Mbps with cpbBrVclFactor and cpbBrNalFactor being fixed to be 1250 and 1500, respectively; and, + - the bitstream does not contain more than 10 slices per picture. +- **AVC-8K-Dec:** the capability to decode H.264 (AVC) Progressive High Profile Level 6.1 [7] bitstreams with the following requirements: + - the maximum VCL Bit Rate is constrained to be 120 Mbps with cpbBrVclFactor and cpbBrNalFactor being fixed to be 1250 and 1500, respectively; and, + - the bitstream does not contain more than 16 slices per picture. + - the bitstream shall not include horizontal motion vector component values that exceed the range from -2048 to 2047, inclusive, or that have vertical motion vector component values that exceed the range from -512 to 511, inclusive, in units of ¼ luma sample displacement. This constraint should be indicated by using values of `log2_max_mv_length_horizontal` less than or equal to 11 and values of `log2_max_mv_length_vertical` less than or equal to 9. +- **HEVC-FullIHD-Dec:** the capability to decode H.265 (HEVC) Main10 Profile, Main Tier, Level 4.1 [8] bitstreams that have `general_progressive_source_flag` equal to 1, `general_interlaced_source_flag` equal to 0, `general_non_packed_constraint_flag` equal to 1 and `general_frame_only_constraint_flag` equal to 1. +- **HEVC-UHD-Dec:** the capability to decode H.265 (HEVC) Main10 Profile, Main Tier, Level 5.1 [8] bitstreams that have `general_progressive_source_flag` equal to 1, `general_interlaced_source_flag` equal to 0, `general_non_packed_constraint_flag` equal to 1 and `general_frame_only_constraint_flag` equal to 1. +- **HEVC-8K-Dec:** the capability to decode H.265 (HEVC) Main10 Profile, Main Tier, Level 6.1 [8] bitstreams that have `general_progressive_source_flag` equal to 1, `general_interlaced_source_flag` equal to 0, `general_non_packed_constraint_flag` equal to 1, and `general_frame_only_constraint_flag` equal to 1 with the following additional requirements: + - the bitstream does not exceed the maximum luma picture size in samples of 33,554,432; and, + - the maximum VCL Bit Rate is constrained to be 80 Mbps with CpbVclFactor and CpbNalFactor being fixed to be 1000 and 1100, respectively. + +### 7.1.2 Concurrent decoding capabilities + +#### 7.1.2.1 Definition + +Concurrent video decoder instances are defined as follows. + +For $N$ video bitstreams encoded according to a video codec profile, decoding units flow into the coded picture buffer (CPB) for each stream according to a specified arrival schedule and are delivered by the common Hypothetical Stream Scheduler (HSS) that schedules the $N$ bitstreams for decoding each of the units. For each access unit + +- all data associated with an access unit is removed and decoded instantaneously by the instantaneous decoding process at CPB removal time of the access unit. +- Each decoded picture is placed in the Decoded Picture Buffer (DPB) for being referenced by the decoding process of this stream as well as for output and cropping. +- A decoded picture is removed from the DPB at the time that it becomes no longer needed for inter-prediction reference as well as the output time of the access unit is the largest of all decoded pictures remaining in the group of N decoders + +Then at any point time, + +- each of the individual streams conforms to the signaled profile/level/tier and HRD parameters of the individual stream. +- The sum of the CPB size conforms to common profile/level/tier signaling +- The aggregate decoder processing speed (samples per seconds) conforms to common profile/level/tier signaling. +- The sum of the DPB size conforms to common profile/level/tier signaling +- The common DPB size conforms to common profile/level/tier signaling + +A set of $N$ concurrent decoder instances conforms to a given capabilities (defined in clause 7.1.2.2), if a set of up to $N$ bitstreams encoded to be decodable by the HRD above, is decodable within the timing limits. + +#### 7.1.2.2 Capabilities + +Based on the definition in clause 7.1.2.1, the following capabilities are defined: + +- **AVC-FullHD-Dec-2:** The capability of supporting up to two ( $N=2$ ) concurrent decoder instances with the aggregate capabilities of *AVC-FullHD-Dec*. +- **AVC-UHD-Dec-4:** The capability of supporting up to four ( $N=4$ ) concurrent decoder instances with the aggregate capabilities of *AVC-UHD-Dec*. +- **HEVC-UHD-Dec-4:** The capability of supporting up to four ( $N=4$ ) concurrent decoder instances with the aggregate capabilities of *HEVC-UHD-Dec*. +- **UHD-Dec-4:** The capability supporting up to four ( $N=4$ ) concurrent decoder instances with either: + - the aggregate capabilities of *AVC-UHD-Dec-4*; + - the aggregate capabilities of *HEVC-UHD-Dec-4*; or, + - the capability of decoding up to 4 bitstreams for which each bitstream does not exceed the capability of being decodable either with *AVC-FullHD-Dec* or *HEVC-FullHD-Dec*. +- **AVC-8K-Dec-8:** The capability of supporting up to eight ( $N=8$ ) concurrent decoder instances with the aggregate capabilities of *AVC-8K-Dec*. +- **HEVC-8K-Dec-8:** The capability of supporting up to eight ( $N=8$ ) concurrent decoder instances with the aggregate capabilities of *HEVC-8K-Dec*. +- **8K-Dec-8:** The capability supporting up to eight ( $N=8$ ) concurrent decoder instances with either: + - the aggregate capabilities of *AVC-8K-Dec-8*; + - the aggregate capabilities of *HEVC-8K-Dec-8*; or, + - the capability of decoding up to: + - eight bitstreams for which each bitstream does not exceed the capability of being decodable either with *AVC-FullHD-Dec* or *HEVC-FullHD-Dec*; or, + - four bitstreams for which each bitstream does not exceed the capability of being decodable either with *AVC-UHD-Dec* or *HEVC-UHD-Dec*. + +## 7.2 Encoding capabilities + +### 7.2.1 Single encoder instance + +The following video encoding capabilities are defined: + +- **AVC-FullIHD-Enc:** the capability to encode a video signal to a bitstream that is decodable by a decoder that is *AVC-FullIHD-Dec* capable as defined in clause 7.1.1.1 with the following additional constraints: + - up to 245,760 macroblocks per second; + - up to a frame size of 8,192 macroblocks; + - up to 240 frames per second; + - the chroma format being 4:2:0; and + - the bit depth being 8 bit; +- **HEVC-FullIHD-Enc:** the capability to encode a video signal to a bitstream that is decodable by a decoder that is *HEVC-FullIHD-Dec* capable as defined in clause 7.1.1 with the following additional constraints: + - up to 133,693,440 luma samples per second; + - up to a luma picture size of 2,228,224 samples; + - up to 240 frames per second; + - the Chroma format being 4:2:0; and + - the bit depth being either 8 or 10 bit; +- **HEVC-UHD-Enc:** the capability to encode a video signal to a bitstream that is decodable by a decoder that is *HEVC-UHD-Dec* capable as defined in clause 7.1.1 with the following additional constraints: + - up to 534,773,760 luma samples per second; + - up to a luma picture size of 8,912,896 samples; + - up to 480 frames per second; + - the Chroma format being 4:2:0; and + - the bit depth being either 8 or 10 bit; + +## 7.3 Capability exchange + +The capabilities of the device are captured in the data structure defined in 12.5. + +# --- 8 Audio functions and capabilities + +## 8.1 Audio/Speech Decoding + +The following audio/speech decoding capabilities are defined: + +- **EVS:** the decoding capability as defined in TS 26.117 [9] clause 5.2. +- **IVAS:** the decoding capability as defined in TS 26.117 [9] clause 5.2. + +- **EVS-2**: the decoding capability as defined TS 26.117 [9] clause 5.2. +- **EVS-4**: the decoding capability as defined TS 26.117 [9] clause 5.2. +- **AAC-ELDV2-Dec**: the decoding capability as defined TS 26.117 [9] clause 5.2. +- **AAC-ELDV2-Dec-2**: the decoding capability as defined TS 26.117 [9] clause 5.2. + +## 8.2 Audio/Speech Encoding + +The following audio/speech encoding capabilities are defined: + +- **EVS**: the sender requirements for the **EVS** Operation Point as defined in TS 26.117 [9] clause 6.2.4.3. +- **IVAS**: the sender requirements for the **IVAS** Operation Point as defined in TS 26.117 [9] clause 6.3.5.3. +- **AAC-ELDV2-Enc**: the sender requirements for the **AAC-ELDV2** Operation Point as defined in TS 26.117 [9] clause 6.3.6.3. + +# --- 9 Scene processing capabilities + +## 9.1 General + +This clause defines scene processing capabilities that enable AR and XR experiences. + +In clause 9.2, glTF-based Scene Description capabilities are defined. + +NOTE: Functionalities of this specification can be used w/o a standardized scene description, for example by an application providing an interoperability on Scene Description. However, in this case, AR experiences may be limited to the functionalities of the application and may be restricted. + +## 9.2 glTF-based Scene Description capabilities + +This clause defines client capabilities for rendering and presenting Scene Description based on glTF2.0 [10]. Additional extended capabilities are defined, primarily to support real-time media based on the extensions defined in the MPEG-I Scene Description in ISO/IEC 23090-14 [11-13]. + +The following scene processing capabilities are defined. + +- **SD-Rendering-glTF-Core**: The capability to process glTF2.0 [10] scene description files and to render the described scenes with the following restrictions: + - The glTF 2.0 scene description can either be a standalone JSON file or an encapsulated GLB file. + - The glTF 2.0 scene description can have an aggregate geometry complexity, including all mesh primitives of the scene, of at least 100k faces and/or points. The requirement on the number of faces in mesh nodes allows for moderate complexity scenes. + - The glTF 2.0 scene description can have at least 20 materials using static image textures. The requirement on the number of materials with image texture maps allows for moderate complexity scenes. + - The glTF 2.0 scene description can use glTF2.0 animations and skinning. + - The glTF 2.0 scene description can use the `KHR_lights_punctual` and `KHR_materials_specular` extensions. +- **SD-Rendering-glTF-Ext1**: On top of the **SD-Rendering-glTF-Core** capability, the capability to process MPEG-I Scene Description documents as specified in [11-13] and to render the described scenes with the following restrictions: + +- The MPEG-I Scene Description document can use the `MPEG_media` extension. +- The MPEG-I Scene Description document can use the `MPEG_accessor_timed` and the `MPEG_buffer_circular` extensions. +- The MPEG-I Scene Description document can use the `MPEG_texture_video` extension. +- The MPEG-I Scene Description document can use the `MPEG_audio_spatial` extension. +- The MPEG-I Scene Description document can use the scene description update mechanism as defined in clause 5.2.4 of [9]. +- Processing of scene description updates as defined in ISO/IEC 23090-14 [11-13] to allow the device to contribute to a scene description of a dynamic shared scene. +- The MPEG-I Scene Description document can use at least 4 materials using video textures + +NOTE: This functionality implies that at least 4 concurrent video decoder instances are available + +- The MPEG-I Scene Description document may use at least 4 object-based mono audio sources, which allows for relatively simple audio support. + +NOTE: This functionality implies that at least 4 concurrent mono sources are available as the output of the audio decoding engine instances are available, potentially requiring concurrent audio decoder instances + +Editor's Note: the audio-specific minimal support, such as the type of audio sources and the number of audio sources to support as part of this capability, are to be agreed with the Audio SWG. + +- **SD-Rendering-gITF-Ext2:** On top of the **SD-Rendering-gITF-Core** capability, the capability to process MPEG-I Scene Description documents as specified in [11-13] with the following restrictions: + - The MPEG-I Scene Description document can use the `MPEG_anchor` extension. + - The MPEG-I Scene Description document can use the `EXT_lights_image_based` and the `MPEG_lights_texture_based` extensions. +- **SD-Rendering-gITF-Interactive:** On top of the **SD-Rendering-gITF-Core** capability, the capability to process the following glTF 2.0 extensions defined in [11-13] to enable user input and local interaction processing. + - The MPEG-I Scene Description document can use the `MPEG_scene_interactivity` extension with the following triggers: `TRIGGER_USER_INPUT`, `TRIGGER_PROXIMITY`, `TRIGGER_COLLISION`, `TRIGGER_VISIBILITY`. + - The MPEG-I Scene Description document can use the `MPEG_scene_interactivity` extension with actions: `ACTION_ACTIVATE`, `ACTION_TRANSFORM`, `ACTION_BLOCK`, `ACTION_ANIMATION`, `ACTION_MEDIA`, `ACTION_MANIPULATE`, `ACTION_SET_MATERIAL` + +# --- 10 Device types and media profiles + +## 10.1 Introduction + +AR experiences may be running on a variety of devices which have different characteristics and capabilities. Certain capabilities may be common to several devices while other capabilities may be unique to a specific device. Therefore, the present specification enables interoperability by collecting the media capabilities and profiles, defined in clauses 6, 7, 8 and 9, per device type. The four device types defined are: + +- Device type 1: Thin AR glasses (see clause 10.2) +- Device type 2: AR glasses (see clause 10.3) +- Device type 3: XR phone (see clause 10.4) + +- Device type 4: XR HMD (see clause 10.5) + +NOTE: A given physical device may be compliant to more than one device types. + +## 10.2 Device type 1: Thin AR glasses + +### 10.2.1 General + +As defined in 4.3.1, the thin AR glasses device type represents a type of device which is considered to be power-constrained and with limited computing power with respect to the other device types. These limitations typically come from the requirement to design a device with a small and lightweight form factor. Regarding rendering capacity, this device type is expected to rely on remote rendering to be able display complex scenes to the user. For example, such device type may run a split rendering session where the split rendering server delivers pre-rendered views of the scene. However, devices in this category can still operate without external support for applications that do not require complex rendering capabilities, for instance, text messaging, 2D video communication, etc. Lastly, the thin AR glasses offers AR experiences to the user via optical see-through display. + +### 10.2.2 XR System support + +An XR Device complying to the thin AR glasses device has an XR System with at least the following capabilities as based on clause 6.1: + +- `orientationTracking` is 'true' +- `positionTracking` is 'true' +- Value 'additive' of the enumeration `blendMode` +- Values 'monoscopic' and 'stereoscopic' of the enumeration `viewConfigurationPrimary` +- Values 'view', 'local' and 'stage' of the enumeration `referenceSpace` +- If `swapchainSupported` is 'true', `numberSwapchainImages` is equal to 2 +- Values 'projection' and 'quad' of the enumeration `compositionLayer` + +NOTE: For the definition of those capabilities, please refer to clause 4.1.3. + +### 10.2.3 Video capabilities support + +An XR Device complying to device type 1 shall support the following decoding capabilities from clause 7: + +- **AVC-FullIHD-Dec** +- **AVC-FullIHD-Dec-2** + +An XR Device complying to device type 1 shall support the following encoding capabilities: + +- **AVC-FullIHD-Enc** + +An XR Device complying to device type 1 should support the following decoding capabilities: + +- **HEVC-FullIHD-Dec** + +An XR Device complying to device type 1 should support the following encoding capabilities: + +- **HEVC-FullIHD-Enc** + +### 10.2.4 Audio/Speech capabilities support + +An XR Device complying to device type 1 device shall support the following decoding capabilities from clause 8: + +- EVS +- AAC-ELDV2-Dec + +An XR Device complying to device type 1 should support the following decoding capabilities: + +- IVAS-SR +- EVS + +An XR Device complying to device type 1 may support the following decoding capabilities: + +- IVAS-L1 +- EVS-4 +- AAC-ELDV2-Dec-2 + +An XR Device complying to device type 1 shall support the following encoding capabilities: + +- EVS + +An XR Device complying to device type 1 should support the following encoding capabilities: + +- IVAS-L1 +- AAC-ELDV2-Enc + +### 10.2.5 Scene Description capabilities support + +A device of type 1 should support glTF-based scene description as defined in clause 9.2. + +If gltf-based scene description is supported, the following requirements and recommendation hold: + +- The **SD-Rendering-gltf-Core** capabilities should be supported. + +## 10.3 Device type 2: AR glasses + +### 10.3.1 General + +As defined in 4.3.2, the AR glasses device type represents a type of device which is considered to have higher computation power compared to the thin AR glasses device type. As a result, this device type has higher rendering capacities and is generally expected to be capable of rendering scenes without external support, even though remote rendering is not precluded to lower the power consumption on the device or enable the display of scenes beyond the device's rendering capability. Lastly, the AR glasses offers AR experiences to the user via optical see-through display. + +### 10.3.2 XR System support + +An XR Device complying to the AR glasses device type has offers XR System with at least the following capabilities from clause 6.1: + +- `orientationTracking` is 'true' +- `positionTracking` is 'true' +- Value 'additive' of the enumeration `blendMode` +- Value 'stereoscopic' of the enumeration `viewConfigurationPrimary` +- Values 'view', 'local' and 'stage' of the enumeration `referenceSpace` +- If `swapchainSupported` is 'true', `numberSwapchainImages` is equal to 2 + +- Values 'projection' and 'quad' of the enumeration compositionLayer + +NOTE: For the definition of those capabilities, please refer to clause 4.1.3. + +### 10.3.3 Video capabilities support + +An XR Device complying to device type 2 shall support the following decoding capabilities from clause 7: + +- **AVC-UHD-Dec** +- **AVC-UHD-Dec-4** +- **HEVC-UHD-Dec** + +An XR Device complying to device type 2 shall support one of the following encoding capabilities: + +- **AVC-FullHD-Enc** +- **HEVC-FullHD-Enc** + +An XR Device complying to device type 2 should support the following decoding capabilities: + +- **HEVC-UHD-Dec-4** +- **UHD-Dec-4** + +### 10.3.4 Audio/Speech capabilities support + +An XR Device complying to device type 2 device shall support the following decoding capabilities from clause 8: + +- **EVS** +- **AAC-ELDV2-Dec** + +An XR Device complying to device type 2 should support the following decoding capabilities: + +- **IVAS-SR** +- **IVAS-L1** +- **EVS-2** + +An XR Device complying to device type 2 may support the following decoding capabilities: + +- **EVS-4** +- **AAC-ELDV2-Dec-2** + +An XR Device complying to device type 2 shall support the following encoding capabilities: + +- **EVS** + +An XR Device complying to device type 2 should support the following encoding capabilities: + +- **IVAS-L1** +- **AAC-ELDV2-Enc** + +### 10.3.5 Scene Description capabilities support + +A device of type 2 should support glTF-based scene description as defined in clause 9.2. + +If gltf-based scene description is supported, the following requirements and recommendation hold. + +- The **SD-Rendering-gltf-Core** capabilities shall be supported + +- The **SD-Rendering-gltf-ext1** capabilities should be supported +- The **SD-Rendering-gltf-ext2** capabilities may be supported +- The **SD-Rendering-gltf-interactive** capabilities may be supported + +## 10.4 Device type 3: XR phone + +### 10.4.1 General + +As defined in 4.3.1, the XR phone device type represents a type of device which corresponds to a smartphone with capacities and resources sufficient to offer AR experiences. As a result, this device type is capable of rendering scenes without external support. Lastly, the XR phone offers AR experiences to the user via video see-through display. + +### 10.4.2 XR System support + +An XR Device complying to the XR phone device type offers an XR System with at least the following capabilities: + +- `orientationTracking` is 'true' +- `positionTracking` is 'true' +- Values 'opaque' and 'alpha\_blend' of the enumeration `blendMode` +- Values 'monoscopic' and 'stereoscopic' of the enumeration `viewConfigurationPrimary` +- Values 'view', 'local' and 'stage' of the enumeration `referenceSpace` +- If `swapchainSupported` is 'true', `numberSwapchainImages` equal to 2 +- Values 'projection' and 'quad' of the enumeration `compositionLayer` + +NOTE: For the definition of those capabilities, please refer to clause 6.1. + +### 10.4.3 Video capabilities support + +An XR Device complying to device type 3 shall support the following decoding capabilities from clause 7: + +- **AVC-UHD-Dec** +- **AVC-UHD-Dec-4** +- **HEVC-UHD-Dec** +- **HEVC-UHD-Dec-4** +- **UHD-Dec-4** + +An XR Device complying to device type 3 shall support one of the following encoding capabilities: + +- **AVC-UHD-Enc** +- **HEVC-UHD-Enc** + +An XR Device complying to device type 3 should support the following decoding capabilities: + +- **AVC-8K-Dec** +- **HEVC-8K-Dec** +- **8K-Dec-8** + +### 10.4.4 Audio/Speech capabilities support + +An XR Device complying to device type 3 device shall support the following decoding capabilities from clause 8: + +- EVS +- AAC-ELDV2-Dec + +An XR Device complying to device type 3 should support the following decoding capabilities: + +- IVAS +- EVS-2 + +An XR Device complying to device type 3 may support the following decoding capabilities: + +- EVS-4 +- AAC-ELDV2-Dec-2 + +An XR Device complying to device type 3 shall support the following encoding capabilities: + +- EVS + +An XR Device complying to device type 3 should support the following encoding capabilities: + +- IVAS +- AAC-ELDV2-Enc + +### 10.4.5 Scene Description capabilities support + +A device of type 3 should support gltf-based scene description as defined in clause 9.2. + +If gltf-based scene description is supported, the following requirements and recommendation hold. + +- The **SD-Rendering-gltf-Core** capabilities shall be supported +- The **SD-Rendering-gltf-ext1** capabilities should be supported +- The **SD-Rendering-gltf-ext2** capabilities should be supported +- The **SD-Rendering-gltf-interactive** capabilities should be supported + +## 10.5 Device type 4: XR HMD + +### 10.5.1 General + +As defined in 4.3.1, the XR HMD device type represents a type of device which corresponds to HMDs capable of offering at least AR experiences but not precluding other types of XR experiences. This device type is expected to be capable of rendering scenes without external support. Lastly, the XR phone offers AR experiences to the user via video see-through display. + +### 10.5.2 XR System support + +An XR Device complying to the XR HMD device type offers an XR System with at least the following capabilities from clause 6.1: + +- `orientationTracking` is 'true' +- `positionTracking` is 'true' +- Value 'additive' or values 'opaque' and 'alpha\_blend' of the enumeration `blendMode` + +- Values 'monoscopic' and 'stereoscopic' of the enumeration `viewConfigurationPrimary` +- Values 'view', 'local' and 'stage' of the enumeration `referenceSpace` +- If `swapchainSupported` is 'true', `numberSwapchainImages` is equal to 2 +- Values 'projection' and 'quad' of the enumeration `compositionLayer` + +NOTE: For the definition of those capabilities, please refer to clause 6.1. + +### 10.5.3 Video capabilities support + +An XR Device complying to device type 4 shall support the following decoding capabilities from clause 7: + +- **AVC-UHD-Dec** +- **AVC-UHD-Dec-4** +- **HEVC-UHD-Dec** +- **HEVC-UHD-Dec-4** +- **UHD-Dec-4** + +An XR Device complying to device type 4 shall support one of the following encoding capabilities: + +- **AVC-UHD-Enc** +- **HEVC-UHD-Enc** + +An XR Device complying to device type 4 should support the following decoding capabilities: + +- **AVC-8K-Dec** +- **HEVC-8K-Dec** +- **8K-Dec-8** + +### 10.5.4 Audio/Speech capabilities support + +An XR Device complying to device type 4 device shall support the following decoding capabilities from clause 8: + +- **EVS** +- **AAC-ELDV2-Dec** + +An XR Device complying to device type 4 should support the following decoding capabilities: + +- **IVAS** +- **EVS-2** + +An XR Device complying to device type 4 may support the following decoding capabilities: + +- **EVS-4** +- **AAC-ELDV2-Dec-2** + +An XR Device complying to device type 4 shall support the following encoding capabilities: + +- **EVS** + +An XR Device complying to device type 4 should support the following encoding capabilities: + +- **IVAS** + +- AAC-ELDv2-Enc + +### 10.5.5 Scene Description capabilities support + +A device of type 4 should support gltf-based scene description as defined in clause 9.2. + +If gltf-based scene description is supported, the following requirements and recommendation hold. + +- The **SD-Rendering-gltf-Core** capabilities shall be supported +- The **SD-Rendering-gltf-ext1** capabilities should be supported +- The **SD-Rendering-gltf-ext2** capabilities should be supported +- The **SD-Rendering-gltf-interactive** capabilities should be supported + +# 11 QoE metrics + +## 11.1 Metrics and Observation Points + +### 11.1.1 Overview + +The Observation Points (OPs) are defined to support the definition of the corresponding metrics. This specification defines four observation points as shown in Figure 11.1.1-1. The metrics collection function, as part of the Media Session Handler, is responsible of collecting specific information observed at each OP in order to generate the metrics. This function has also access to the 5G System such that the metrics can be reported to an external entity. + +![Figure 11.1.1-1 - Observation Points in the XR Baseline Client. This block diagram shows the internal architecture of an XR Baseline Client. At the top, 'User input' enters the 'XR Application' (green bar). Below it, the client contains several functional blocks: 'XR Runtime' (red, with 'Runtime functions (tracking, SLAM)', 'Composition', and 'Audio Subsystem'), 'XR Source Management' (blue, with 'API-2'), 'Presentation Engine' (blue, with 'Visual Renderer' and 'Audio Renderer'), 'Scene Manager' (teal), and 'Media Access Function' (yellow, with 'Content Delivery Protocols', 'Metadata Formats', 'Video Codecs', and 'Audio Codecs'). A 'Media Session Handler' (yellow, with 'Metrics collection & reporting' and 'API-6') is also present. External components include 'Sensor', 'Cameras', 'Actuators', 'Displays', 'Speakers', and 'Microphones' on the left, and a '5G System (Uu)' (purple) on the right. Interfaces are labeled: IF-1a, IF-1b, IF-1c (between XR Runtime and other components), IF-2 (between XR Application and XR Source Management), IF-3 (between XR Source Management and Media Session Handler), IF-4 (between Media Access Function and 5G System), IF-5 (between Media Session Handler and 5G System), IF-6 (between Media Session Handler and Media Access Function), IF-7 (between XR Application and Media Session Handler), IF-8 (between XR Application and 5G System), IF-9 (between Scene Manager and Media Access Function), and IF-10 (between XR Source Management and Media Access Function). Four Observation Points (OPs) are marked with red vertical lines: OP-1 on IF-1a, OP-2 on IF-9, OP-3 on IF-10, and OP-4 on IF-4.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) + +Figure 11.1.1-1 - Observation Points in the XR Baseline Client. This block diagram shows the internal architecture of an XR Baseline Client. At the top, 'User input' enters the 'XR Application' (green bar). Below it, the client contains several functional blocks: 'XR Runtime' (red, with 'Runtime functions (tracking, SLAM)', 'Composition', and 'Audio Subsystem'), 'XR Source Management' (blue, with 'API-2'), 'Presentation Engine' (blue, with 'Visual Renderer' and 'Audio Renderer'), 'Scene Manager' (teal), and 'Media Access Function' (yellow, with 'Content Delivery Protocols', 'Metadata Formats', 'Video Codecs', and 'Audio Codecs'). A 'Media Session Handler' (yellow, with 'Metrics collection & reporting' and 'API-6') is also present. External components include 'Sensor', 'Cameras', 'Actuators', 'Displays', 'Speakers', and 'Microphones' on the left, and a '5G System (Uu)' (purple) on the right. Interfaces are labeled: IF-1a, IF-1b, IF-1c (between XR Runtime and other components), IF-2 (between XR Application and XR Source Management), IF-3 (between XR Source Management and Media Session Handler), IF-4 (between Media Access Function and 5G System), IF-5 (between Media Session Handler and 5G System), IF-6 (between Media Session Handler and Media Access Function), IF-7 (between XR Application and Media Session Handler), IF-8 (between XR Application and 5G System), IF-9 (between Scene Manager and Media Access Function), and IF-10 (between XR Source Management and Media Access Function). Four Observation Points (OPs) are marked with red vertical lines: OP-1 on IF-1a, OP-2 on IF-9, OP-3 on IF-10, and OP-4 on IF-4. + +Figure 11.1.1-1 - Observation Points in the XR Baseline Client + +### 11.1.2 Observation Point 1: XR Runtime information + +Observation point 1 (OP-1) is derived from the XR Runtime API. The OP-1 observes information exchanged between the XR Runtime on one side and the XR Source Management, the Presentation Engine and the application on the other side, i.e. on IF-1. + +On observation point 1, the following observed information is defined: + +- XR runtime clock (XR runtime clock) +- Actual presentation/display time +- user input actions and the time when the action is made +- Rendering loop timing information: to observe the start of the scene update by the scene manager and the start of the rendering process. + +### 11.1.3 Observation Point 2 + +Observation point 2 (OP-2) observes information at the input of the Scene Manager, i.e. on IF-9 for data received from the Media Access Function and the IF-10 for information exchanged between the Scene Manager and the application. + +### 11.1.4 Observation Point 3 + +Observation point 3 (OP-3) is derived from the API which exchanges information between the XR Source Management and the Media Access Functions. It corresponds to the IF-3 interface. + +### 11.1.5 Observation Point 4 + +Observation point 4 (OP-4) observes information between the Media Access Function and the 5G System, i.e. on IF-4 interface. + +## 11.2 Metrics Definitions + +### 11.2.1 Latency metrics + +To enable good XR experiences, it is relevant to monitor latencies such as the pose-to-render-to-photon. + +Beyond the sense of presence and immersiveness, the age of the content and user interaction delay are of the uttermost importance for immersive and non-immersive interactive experiences, i.e. experiences for which the user interaction with the scene impacts the content of scene (such as online gaming). + +Table 11.2.1-1 provides time information that may be gathered to compute the latency metrics. The observation points to collect the time information are indicated per device type. + +**Table 11.2.1-1: Time information for latency metrics** + +| Time information | Definition | Observation Point | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| estimatedAtTime
(ref. T1) | The time when the viewer pose prediction is made. It corresponds to the time when the predicted viewer pose is collected using the XR runtime API-1 by the application or the XR Source Manager.
This time is expressed in XR system time clock. | OP-1 | +| lastChangeTime | The time when the user action is made. It corresponds to the lastChangeTime field defined in the action format in Table 5.1.3-1.
This time is expressed in XR system time clock. | OP-1 | +| sceneUpdateTime
(ref. T6) | The time when the Scene Manager starts to update the 3D scene graph according to the viewer pose and the user actions.
This time is expressed in wall clock time | OP-1 | +| startToRenderAtTime
(ref. T3) | The time when the renderer starts to render the scene according to the viewer pose.
This time is expressed in wall clock time | OP-1 | + +| | | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| actualDisplayTime
(ref. T2.actual) | The actual display time of the rendered frame in the swapchain. The estimation of the actual display time is available through the XR runtime.
This time is expressed in XR system time clock. | OP-1 | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| + +The latency metrics are specified in Table 11.2.1-2. The formula to compute the latencies are defined using the collected time information. + +**Table 11.2.1-2: Latency metrics** + +| Latency metric | Description | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| poseToRenderToPhoton | The time duration, in units of milliseconds, between the time to query the pose information from the XR runtime to the renderer (the renderer uses this pose to generate the rendered frame) and the display time of the rendered frame.
It can be computed as follows:
$\text{actualDisplayTime} - \text{estimatedAtTime}$ | +| renderToPhoton | The time duration, in units of milliseconds, between the start of the rendering by the Presentation Engine and the display time of the rendered frame.
It can be computed as follows:
$\text{actualDisplayTime} - \text{startToRenderAtTime}$ | +| roundtripInteractionDelay | The time duration, in units of milliseconds, between the time a user action is initiated and the time the action is presented to the user.
It can be computed as follows:
$\text{actualDisplayTime} - \text{lastChangeTime}$ | +| userInteractionDelay | The time duration, in units of milliseconds, between the time a user action is initiated and the time the action is taken into account by the content creation engine in the scene manager.
It can be computed as follows:
$\text{sceneUpdateTime} - \text{lastChangeTime}$ | +| ageOfContent | The time duration, in units of milliseconds, between the time the content is created in the scene by the Scene Manager and the time it is presented to the user.
It can be computed as follows:
$\text{actualDisplayTime} - \text{sceneUpdateTime}$ | +| sceneUpdateDelay | The time duration, in units of milliseconds, spent by the Scene Manager to update the scene graph.
It can be computed as follows:
$\text{startToRenderAtTime} - \text{sceneUpdateTime}$ | + +NOTE: The metrics renderToPhoton, userInteractionDelay, and ageOfContent are considered being expressed into a single time format (e.g., wall clock time). + +# 12 Metadata formats + +## 12.1 General + +Several applications may require the exchange of real-time metadata information for about the XR session. For instance, split rendering applications and immersive communication services may require the UE to share Pose and action information pertaining to the user's current pose, to their input (e.g. pulling a trigger on the XR controller) or trackable pose. This clause defines the metadata formats for timed metadata of an XR session. + +## 12.2 Pose format + +The Pose format is used to share pose information, e.g. about predicted poses with the network. + +Each predicted pose shall contain the associated predicted display time and an identifier of the XR space that was used for that pose. + +Depending on the view configuration of the XR session, there could be different pose information for each view. + +The payload of the message shall follow the structure defined in Table 12.2-1. + +**Table 12.2-1 - Pose format** + +| Name | Type | Cardinality | Description | +|------------------|--------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| poseInfo | Object | 1..n | An array of pose information objects, each corresponding to a target display time and XR space. | +| poseTime | number | 1..1 | The time for which the current poses are predicted. This time is expressed in XR system time clock. | +| xrSpaceId | number | 0..1 | An identifier for the XR space in which the poses are expressed. | +| poses | Object | 1..n | An array that provides a list of the poses.

For view poses, the first pose corresponds to the left view and the second to the right view. | +| trackableSpaceId | number | 0..1 | A unique identifier of the XR space of the trackable that was agreed upon during session setup. The pose corresponds to the origin of that trackableSpaceId expressed in the XR space identified by xrSpaceId.

This is only applicable for trackable pose. | +| orientation | Object | 1..1 | Represents the orientation of the pose as a quaternion based on the reference XR space identified by xrSpaceId. | +| x | number | 1..1 | Provides the x coordinate of the quaternion. | +| y | number | 1..1 | Provides the y coordinate of the quaternion. | +| z | number | 1..1 | Provides the z coordinate of the quaternion. | +| w | number | 1..1 | Provides the w coordinate of the quaternion. | + +| | | | | +|-----------------|--------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | Object | 0..1 | Represents the position of the pose relative to the XR space identified by xrSpaceId. | +| x | number | 1..1 | Provides the x coordinate of the position vector. | +| y | number | 1..1 | Provides the y coordinate of the position vector. | +| z | number | 1..1 | Provides the z coordinate of the position vector. | +| confidence | number | 0..1 | Provides a confidence score that reflects the probability for this pose prediction to be correct. For the current pose or a pose in the past, the confidence value would be 1. The confidence can take a value between 0 and 1. | +| estimatedAtTime | number | 0..1 | The wall clock time when the pose estimation was made. (ref. T1) | +| fov | Object | 0..1 | Indicates the four sides of the field of view used for the projection of the corresponding XR view.

This field is only present if these field of view values have changed from the last sent values.

This is only applicable for view poses | +| angleLeft | number | 1..1 | The angle in radians of the left side of the field of view. For a symmetric field of view this value is negative. | +| angleRight | number | 1..1 | The angle in radians of the right side of the field of view. | +| angleUp | number | 1..1 | The angle in radians of the top part of the field of view. | +| angleDown | number | 1..1 | The angle in radians of the bottom part of the field of view. For a symmetric field of view this value is negative. | + +## 12.3 Action format + +Actions are grouped into action sets which may be activated and deactivated during the lifetime of an XR session. The action sets and actions are negotiated at the start of the split rendering session. + +The content of the action message type shall the structure defined in Table 12.3-1. + +**Table 12.3-1 - Action format** + +| Name | Type | Cardinality | Description | +|------------|--------|-------------|------------------------------------------------------------------------------------------------| +| actionSets | Object | 1..n | An array of active action sets, for which there is at least an action that has a state change. | +| actions | number | 1..n | An array of objects that conveys information about the actions of the parent action set. | + +| | | | | +|------------------|--------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | string | 1..1 | A unique identifier of the action. | +| subactionPath | string | 1..1 | The sub-action path for which the state has changed. It abstracts a binding between an action and the hardware input associated to it by the XR runtime. | +| state | object | 1..1 | The state of the action that had a change in state. | +| lastChangeTime | number | 1..1 | The timestamp of the last change to the state of this action. | +| currentStateBool | Bool | 0..1 | The current Boolean state of the action | +| currentStateNum | number | 0..1 | The current numerical state of the action. | +| currentStateVec2 | Array | 0..1 | An array of numerical state values for the action. | + +## 12.4 Available Visualization Space format + +The XR Application may define a three-dimensional space within the user's real-word space that is suitable for rendering virtual objects called the Available Visualization Space. Such a space is defined with a shape which is either cube or sphere with the corresponding size and coordinates. In the case that the virtual scene is rendered by a remote entity (e.g. split rendering), this Available Visualization Space may be transmitted to this remote entity so that the composed AR objects remain within the defined Available Visualization Space. The method of calculating the Available Visualization Space is out of the scope of this document. + +The content of the availableVisualizationSpace type shall follow the format defined in Table 12.4-1. + +**Table 12.4-1 – Available Visualization Space** + +| Name | Type | Cardinality | Description | +|-----------------------------|--------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| availableVisualizationSpace | Object | 0..1 | An object defining the coordinate of the available visualization space. | +| xrSpaceId | number | 0..1 | An identifier for the XR space in which the available visualization space is expressed. | +| cuboid | Object | 0..1* | The available visualization space in form of cuboid. The 3D coordinates are expressed in the XR Space identified by xrSpaceId. | +| x | float | 1 | Offset of the available visualization space starting point in the x direction.

The value is in meters. | +| y | float | 1 | Offset of the available visualization space starting point in the y direction as defined by the Open XR coordinate system.

The value is in meters. | +| z | float | 1 | Offset of the available visualization space starting point in the z direction.

The value is in meters. | + +| | | | | +|----------------------------------------------------|--------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| width | float | 1 | The width of available visualization space in the x direction as defined by the Open XR coordinate system.

The value is in meters. | +| height | float | 1 | The height of available visualization space in the y direction.

The value is in meters. | +| depth | float | 1 | The depth of available visualization space in the z direction.

The value is in meters. | +| sphere | Object | 0..1* | The available visualization space in form of a sphere. The 3D coordinates are expressed in the XR Space identified by xrSpaceId | +| x | float | 1 | Offset of the available visualization space center in the x direction as defined by the Open XR coordinate system.

The value is in meters. | +| y | float | 1 | Offset of the available visualization space center in the y direction.

The value is in meters. | +| z | float | 1 | Offset of the available visualization space center in the z direction.

The value is in meters. | +| radius | float | 1 | The radius of available visualization space.

The value is in meters. | +| *Only one of cuboid or sphere object shall exists. | | | | + +With this Available Visualization Space, a user may for instance avoid the virtual objects to be occluding other real objects in the scene, e.g. TV sets, people, etc., since an AR experience is achieved by the integration of visual objects into the user environment. + +## 12.5 Device capabilities signalling + +Device capabilities may be signalled using the format defined in Table 12.5-1. + +**Table 12.5-1 – Device capabilities exchange format** + +| Name | Type | Cardinality | Description | +|--------------------|--------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deviceCapabilities | Object | 0..1 | Provides the supported device capabilities. | +| deviceType | string | 1..N | A list of device type identifiers formatted as URN defined in table A-1 in Annex A.

For each signalled device type identifier, the associated capabilities are supported by the sending device. | + +| | | | | +|------------------------|--------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalCapabilities | string | 0...N |

A list of additional media capability identifiers formatted as URN defined in table A-2 in Annex A

For each signalled media capability identifier, the associated capabilities are supported by the sending device.

| +|------------------------|--------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# Annex A (informative): Registration Information + +## A.1 3GPP Registered URIs + +The clause documents the registered URIs in this specification following the process in + +Table A-1 lists all registered URN values for device type identifiers as well as + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +**Table A-1: 3GPP Registered URNs for device type identifiers** + +| URN | Description | Reference | Contact | Remarks | +|---------------------------------|--------------------------------------------------------------------|-------------------------|---------------------------------------|---------| +| urn:3GPP:26119:18:device-type-1 | An identifier for the device type 1 defined in this specification. | TS 26.119, clause 4.3.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:device-type-2 | An identifier for the device type 2 defined in this specification. | TS 26.119, clause 4.3.2 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:device-type-3 | An identifier for the device type 3 defined in this specification. | TS 26.119, clause 4.3.3 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:device-type-4 | An identifier for the device type 4 defined in this specification. | TS 26.119, clause 4.3.4 | Emmanuel Thomas
thomase@xiaomi.com | none | + +Table A-2 lists all registered URN values for video capability identifiers as well as + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +Table A-1: 3GPP Registered URNs for video capability identifiers + +| URN | Description | Reference | Contact | Remarks | +|------------------------------------|-----------------------------------------------------------------------------------------|-----------------------|---------------------------------------|---------| +| urn:3GPP:26119:18:AVC-FullHD-Dec | An identifier for the capability AVC-FullHD-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-UHD-Dec | An identifier for the capability AVC-UHD-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-8K-Dec | An identifier for the capability AVC-8K-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-FullHD-Dec | An identifier for the capability HEVC-FullHD-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-UHD-Dec | An identifier for the capability AVC-UHD-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-UHD-Dec | An identifier for the capability HEVC-UHD-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-8K-Dec | An identifier for the capability HEVC-8K-Dec defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-FullHD-Dec-2 | An identifier for the capability AVC-FullHD-Dec-2 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-UHD-Dec-4 | An identifier for the capability AVC-UHD-Dec-4 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-UHD-Dec-4 | An identifier for the capability HEVC-UHD-Dec-4 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:UHD-Dec-4 | An identifier for the capability UHD-Dec-4 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-8K-Dec-8 | An identifier for the capability AVC-8K-Dec-8 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-8K-Dec-8 | An identifier for the capability HEVC-8K-Dec-8 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:8K-Dec-8 | An identifier for the capability 8K-Dec-8 defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AVC-FullHD-Enc | An identifier for the capability AVC-FullHD-Enc defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-FullHD-Enc | An identifier for the capability HEVC-FullHD-Enc defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:HEVC-UHD-Enc | An identifier for the capability HEVC-UHD-Enc defined in this specification. | TS 26.119, clause 7.1 | Emmanuel Thomas
thomase@xiaomi.com | none | + +Table A-3 lists all registered URN values for audio capability identifiers as well as + +- a brief description of its functionality, +- a reference to the specification or other publicly available document (if any) containing the definition, +- the name and email address of the person making the application, and +- any supplementary information considered necessary to support the application. + +Table A-3: 3GPP Registered URNs for audio capability identifiers + +| URN | Description | Reference | Contact | Remarks | +|-----------------------------------|----------------------------------------------------------------------------------------|-----------------------|---------------------------------------|---------| +| urn:3GPP:26119:18:EVS:Dec | An identifier for the capability EVS defined in this specification. | TS 26.119, clause 8:1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:IVAS:Dec | An identifier for the capability IVAS defined in this specification. | TS 26.119, clause 8:1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:EVS-2:Dec | An identifier for the capability EVS-2 defined in this specification. | TS 26.119, clause 8:1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:EVS-4:DEC | An identifier for the capability EVS-4 defined in this specification. | TS 26.119, clause 8:1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AAC-ELDV2-Dec | An identifier for the capability AAC-ELDV2-Dec defined in this specification. | TS 26.119, clause 8:1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AAC-ELDV2-Dec-2 | An identifier for the capability AAC-ELDV2-Dec-2 defined in this specification. | TS 26.119, clause 8:1 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:EVS-Enc | An identifier for the capability EVS defined in this specification. | TS 26.119, clause 8:2 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:IVAS:Enc | An identifier for the capability IVAS defined in this specification. | TS 26.119, clause 8:2 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:AAC-ELDV2-Enc | An identifier for the capability AAC-ELDV2-Enc defined in this specification. | TS 26.119, clause 8:2 | Emmanuel Thomas
thomase@xiaomi.com | none | + +Table A-4 lists all registered URN values for scene processing capability identifiers as well as + +- a brief description of its functionality, +- a reference to the specification or other publicly available document (if any) containing the definition, +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +Table A-4: 3GPP Registered URNs for scene processing capability identifiers + +| URN | Description | Reference | Contact | Remarks | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------|---------| +| urn:3GPP:26119:18:SD-Rendering-gltF-Core | An identifier for the capability SD-Rendering-gltF-Core defined in this specification. | TS 26.119, clause 9.2 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:SD-Rendering-gltF-Ext1 | An identifier for the capability SD-Rendering-gltF-Ext1 defined in this specification. | TS 26.119, clause 9.2 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:SD-Rendering-gltF-Ext2 | An identifier for the capability SD-Rendering-gltF-Ext2 defined in this specification. | TS 26.119, clause 9.2 | Emmanuel Thomas
thomase@xiaomi.com | none | +| urn:3GPP:26119:18:SD-Rendering-gltF-Interactive | An identifier for the capability SD-Rendering-gltF-Interactive defined in this specification. | TS 26.119, clause 9.2 | Emmanuel Thomas
thomase@xiaomi.com | none | + +# Annex B (informative): XR Runtime interface + +## B.1 Introduction + +This annex describes the XR Runtime functions to be used with the 3GPP capabilities defined in the presented document. Clause B.2.2 focused the mapping of the 3GPP capabilities with the OpenXR runtime. Clause B.2.2 extracted relevant information from the OpenXR specification [5] regarding the rendering operations. + +## B.2 Capability mapping to OpenXR + +### B.2.1 Mapping overview + +| Capability | Corresponding OpenXR capability | Parameters | Corresponding OpenXR object | +|----------------------------------------------------------------|-------------------------------------------------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Create an XR System | xrGetSystem() | xrSystemIdentifier | XrSystemId* systemId; | +| Query XR System's graphics properties | xrGetSystemProperties() | swapchainSupported | Implicit, since the OpenXR specification support of swapchain by design. | +| | | maxSwapchainImageHeight | uint32_t maxSwapchainImageHeight; | +| | | maxSwapchainImageWidth | uint32_t maxSwapchainImageWidth; | +| | | maxLayerCount | uint32_t maxLayerCount; | +| Query XR System's tracking properties | xrGetSystemProperties() | orientationTracking | XrBool32 orientationTracking; | +| | | positionTracking | XrBool32 positionTracking; | +| Enumerate XR System's supported environment blend modes | xrEnumerateEnvironmentBlendModes() | Value 'opaque' of blendMode | XrEnvironmentBlendMode* environmentBlendModes;

There is one element of environmentBlendModes whose value is equal to XR_ENVIRONMENT_BLEND_MODE_OPAQUE . | +| | | Value 'additive' of blendMode | XrEnvironmentBlendMode* environmentBlendModes;

There is one element of environmentBlendModes whose value is equal to XR_ENVIRONMENT_BLEND_MODE_ADDITIVE . | + +| | | | | +|-----------------------------------------------------|-------------------------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Value 'alpha_blend' of blendMode | XrEnvironmentBlendMode* environmentBlendModes;

There is one element of environmentBlendModes whose value is equal to XR_ENVIRONMENT_BLEND_MODE_ALPHA_BLEND. | +| Enumerate supported view configuration types | xrEnumerateViewConfigurations() | Value 'monoscopic' of viewConfigurationPrimary | XrViewConfigurationType* viewConfigurationTypes;

There is one element of viewConfigurationTypes whose value is equal to XR_VIEW_CONFIGURATION_TYPE_PRIMARY_MONO. | +| | | Value 'stereoscopic' of viewConfigurationPrimary | XrViewConfigurationType* viewConfigurationTypes;

There is one element of viewConfigurationTypes whose value is equal to XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO. | +| | | Value 'other' of viewConfigurationPrimary | XrViewConfigurationType* viewConfigurationTypes;

There is one element of viewConfigurationTypes whose value is strictly greater than XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO and strictly lower than XR_VIEW_CONFIGURATION_TYPE_MAX_ENUM. | +| Enumerate the view configuration properties | xrEnumerateViewConfigurationViews() | recommendedImageRectWidth | uint32_t recommendedImageRectWidth; | +| | | maxImageRectWidth | uint32_t maxImageRectWidth; | +| | | recommendedImageRectHeight | uint32_t recommendedImageRectHeight; | +| | | maxImageRectHeight | uint32_t maxImageRectHeight; | +| | | recommendedSwapchainSampleCount | uint32_t recommendedSwapchainSampleCount; | +| | | maxSwapchainSampleCount | uint32_t maxSwapchainSampleCount; | +| Enumerate reference space types | xrEnumerateReferenceSpaces() | Value 'view' of referenceSpace | XrReferenceSpaceType* spaces;

There is one element of spaces whose value is equal to XR_REFERENCE_SPACE_TYPE_VIEW. | + +| | | | | +|-------------------------------------------|------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| | | Value 'local' of referenceSpace | XrReferenceSpaceType* spaces;
There is one element of spaces whose value is equal to XR_REFERENCE_SPACE_TYPE_LOCAL. | +| | | Value 'stage' of referenceSpace | XrReferenceSpaceType* spaces;
There is one element of spaces whose value is equal to XR_REFERENCE_SPACE_TYPE_STAGE. | +| | | Value 'unbounded' of referenceSpace | XrReferenceSpaceType* spaces;
There is one element of spaces whose value is equal to XR_REFERENCE_SPACE_TYPE_UNBOUNDED_MSFT. | +| | | Value 'user_defined' of referenceSpace | | +| Query the spatial range boundaries | xrGetReferenceSpaceBoundsRect() | 2DSpatialRangeBoundaries | XrExtent2Df* bounds; | +| Enumerate swapchain image formats | xrEnumerateSwapchainFormats | swapchainImageFormatIdentifier | int64_t* formats; | +| Enumerate swapchain images | xrEnumerateSwapchainImages() | numberSwapchainImages | uint32_t* imageCountOutput; | +| | | swapchainImages | XrSwapchainImageBaseHeader* images; | +| Enumerate composition layer type | N/A | Value 'projection' of compositionLayer | Part of the core specification | +| | | Value 'quad' of compositionLayer | Part of the core specification | +| | xrEnumerateInstanceExtensionProperties() | Value 'cylinder' of compositionLayer | XrStructureType type;
The variable type has the value XR_TYPE_COMPOSITION_LAYER_CYLINDER_KHR. | +| | | Value 'cube' of compositionLayer | XrStructureType type;
The variable type has the value XR_TYPE_COMPOSITION_LAYER_CUBE_KHR. | +| | | Value 'equirectangular' of compositionLayer | XrStructureType type;
The variable type has the value XR_TYPE_COMPOSITION_LAYER_EQUIRECT_KHR or | + +| | | | +|--|-----------------------------------|----------------------------------------------------------------------------------------------------| +| | | XR_TYPE_COMPOSITION_LAYER_EQUIRECT2_KHR. | +| | Value 'depth' of compositionLayer | XrStructureType type;
The variable type has the value XR_TYPE_COMPOSITION_LAYER_DEPTH_INFO_KHR. | + +### B.2.2 XR views and rendering loop + +Those composition layers are drawn in a specified order, with the 0th layer drawn first. Layers are drawn with a “painter’s algorithm,” with each successive layer potentially overwriting the destination layers whether or not the new layers are virtually closer to the viewer. Composition layers are subject to blending with other layers. Blending of layers can be controlled by the alpha channel information present in the image buffer of each layer. In addition, the image buffer of the layer may be limited by a maximum width and a maximum height when rendering them such that they fit into the capabilities of the swapchains. + +For visual rendering, the following applies: + +- 1) To present images to the user, the runtime provides images organized in swapchains for the application to render into. +- 2) The XR Runtime may support different swapchain image formats and the supported image formats may be provided to the application through the runtime API. XR Runtimes typically support at least sRGB formats. Details may depend on the graphics API specified when creating the session. +- 3) *Swapchain* images may be 2D or 2D Array. Arrays allow to extract a subset of the 2D images for rendering. Multiple swapchain handles may exist simultaneously, up to some limit imposed by the XR runtime. Swap chain parameters include: + - texture format identifier, a graphics API specific version of a format, for example sRGB. + - width and height, expressing the pixel count of the images sent to the swapchain + - faceCount, being the number of faces, which can be either 6 (for cubemaps) or 1 + - indication whether the swapchain is dynamic, i.e. updated as part of the XR rendering loop or static, i.e. the application releases only one image to this swapchain over its entire lifetime. + - access protection, indicating that the swapchain’s images are protected from CPU access +- 4) Once a session is running and in focussed state as introduced in clause 4.1.2, the following rendering loop is executed following Figure 4.1.4 + - a) The XR Application retrieves the action state, e.g. the status of the controllers and their associated pose. The application also establishes the location of different trackables. + - b) Before an application can begin writing to a swapchain image, it first waits on the image to avoid writing to it before the Compositor has finished reading from it. Then an XR application synchronizes its rendering loop to the runtime. In the common case that an XR application has pipelined frame submissions, the application is expected to compute the appropriate target display time using both the predicted display time and predicted display interval. An XR Runtime is expected to provide and operate a swapchain that supports a specific frame rate. + - c) Once the wait time completes, the application initiates the rendering process. In order to support the application in rendering different views the XR Runtime provides access to the viewer pose and projection parameters that are needed to render the different views. The view and projection info is provided for a particular display time within a specified XR space. Typically, the target/predicted display time for a given frame. + - d) the application then performs its rendering work. Rendering work may be very simple, for example just directly copying data from the application into the swap chain or may be complex, for example iterating over + +the scene graph nodes and rendering complex objects. Once all views/layers are rendered, the application sends them to the XR Runtime for final compositing including the expected display time as well as the associated render pose. + +- e) An XR Runtime typically supports (i) planar projected images rendered from the eye point of each eye using a perspective projection, typically used to render the virtual world from the user's perspective, and (ii) quad layer type describing a possible planar rectangle in the virtual world for displaying two-dimensional content. Other projection types such as cubemaps, equirectangular or cylindric projection may also be supported. +- f) The XR application offloads the composition of the final image to an XR Runtime-supplied compositor. By this, the rendering complexity is significantly lower since details such as frame-rate interpolation and distortion correction are performed by the XR Runtime. It is assumed that the XR Runtime provides a compositor functionality for device mapping. A Compositor in the runtime is responsible for taking all the received layers, performing any necessary corrections such as pose correction and lens distortion, compositing them, and then sending the final frame to the display. An application may use multiple composition layers for its rendering. Composition layers are drawn in a specified order, with the 0th layer drawn first. Layers are drawn with a "painter's algorithm," with each successive layer potentially overwriting the destination layers whether or not the new layers are virtually closer to the viewer. Composition layers are subject to blending with other layers. Blending of layers can be controlled by layer per-texel source alpha. Layer swapchain textures may contain an alpha channel. Composition and blending is done in RGBA. +- g) After the compositor has blended and flattened all layers, it then presents this image to the system's display. The composited image is then blended with the user's view of the physical world behind the displays in one of three modes, based on the application's chosen environment blend mode: + - OPAQUE. The composition layers are displayed with no view of the physical world behind them. The composited image is interpreted as an RGB image, ignoring the composited alpha channel. This is the typical mode for VR experiences, although this mode can also be supported on devices that support video passthrough. + - ADDITIVE: The composition layers are additively blended with the real world behind the display. The composited image is interpreted as an RGB image, ignoring the composited alpha channel during the additive blending. This is the typical mode for an AR experience on a see-through headset with an additive display, although this mode can also be supported on devices that support video passthrough. + - ALPHA\_BLEND. The composition layers are alpha-blended with the real world behind the display. The composited image is interpreted as an RGBA image, with the composited alpha channel determining each pixel's level of blending with the real world behind the display. This is the typical mode for an AR experience on a phone or headset that supports video passthrough. +- h) Meanwhile, while the XR Runtime uses the submitted frame for compositing and display, a new rendering process may be kicked off for a different swap chain image. + +### B.2.3 Available Visualization Space implementation + +#### B.2.3.1 Using OpenXR\_XR\_FB + +The openXR XR\_FB\_scene extension allows to define the boundary room and also boundary space and objects in the space: + +1. `xrGetSpaceBoundingBox3DFB` provides the defined rectangular cube `XrRect3DFB` by defining the offset `XrOffset3DFB` values `x,y, z` and the extent `XrExtent3DFB` values `width, height and depth` in the `x,y,z` dimensions. +2. `xrGetSpaceSemanticLabelsFB` optionally provides a way to describe the semantic meaning of an space entity. It is recommended to use the label "3GPP-AvailableVisualizationSpace" when it is used to describe available visualization space. + +#### B.2.3.2 Using `xrComputeNewSceneMSFT` + +The `XR_MSFT_scene_understanding` extension allows defining the bounding volume in 3 forms: + +1. XrSceneSphereBoundMSFT for defining a spherical available visualization space +2. XrSceneOrientedBoxBoundMSFT for defining a cuboid available visualization space. Note that the bounding box is defined by its center and its edge to edge dimensions around its center. Therefore, these values shall be translated to the values defined in 6.2.4. + +Also note that the scene components outside of the available visualization space may be excluded from rendering by the runtime. \ No newline at end of file diff --git a/marked/Rel-18/26_series/26142/0a5acc4b370bb711096e04f25b8b3feb_img.jpg b/marked/Rel-18/26_series/26142/0a5acc4b370bb711096e04f25b8b3feb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab10556c57ee746315d89f439d3e27fa6936ae6c --- /dev/null +++ b/marked/Rel-18/26_series/26142/0a5acc4b370bb711096e04f25b8b3feb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d233160aff618735700e79ff346358e7da71cc66e36cb3a1082af5a8276f3814 +size 21467 diff --git a/marked/Rel-18/26_series/26142/10953d657a5f47fdc829a800419dd370_img.jpg b/marked/Rel-18/26_series/26142/10953d657a5f47fdc829a800419dd370_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a31ffd145b13464450db465f3986ec7d31c7f634 --- /dev/null +++ b/marked/Rel-18/26_series/26142/10953d657a5f47fdc829a800419dd370_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:214f328a2dd47031cc9f4ae1af7bd9ca4446b63304051da026b02f41043ebcfd +size 13499 diff --git a/marked/Rel-18/26_series/26142/1695df64fe320e3f81049cfe402c8155_img.jpg b/marked/Rel-18/26_series/26142/1695df64fe320e3f81049cfe402c8155_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d1861dcba5a9098406dfcc302e0e78669e2acc4 --- /dev/null +++ b/marked/Rel-18/26_series/26142/1695df64fe320e3f81049cfe402c8155_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f0157ddb350f6b9f997e0571a231c41b1a2fadcc044c82f9ff4ff2334dc1b6d +size 19560 diff --git a/marked/Rel-18/26_series/26142/1c29dadab94c3fa552d270434db09c81_img.jpg b/marked/Rel-18/26_series/26142/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d35b3d6ad7b47e65f4a508630465259acb1b16c0 --- /dev/null +++ b/marked/Rel-18/26_series/26142/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8819066e9026eddacf6cbc00379be30b6d0237c1fd3a514d2f926dc53c41203b +size 31123 diff --git a/marked/Rel-18/26_series/26142/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26142/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d83cdeb9a87e1932ee26ae743529b6df44f0ef97 --- /dev/null +++ b/marked/Rel-18/26_series/26142/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beaf634f7a033e6f03ec91e31f0a93ac7178076b8a4b5c8d6b59b259fd6c8a7c +size 9419 diff --git a/marked/Rel-18/26_series/26142/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26142/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e4b03b8bbe2d0a66841ab12efb8406eb55e69ea --- /dev/null +++ b/marked/Rel-18/26_series/26142/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1bcd850245700d65e9b3900b512a7b0276e2404fc10b27341fc9b1ad0b28784 +size 5654 diff --git a/marked/Rel-18/26_series/26142/67af94a7c462e85f3a310c9a45c0980d_img.jpg b/marked/Rel-18/26_series/26142/67af94a7c462e85f3a310c9a45c0980d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d82f9bf580dad95a6ce3f3e90da842661bd342fb --- /dev/null +++ b/marked/Rel-18/26_series/26142/67af94a7c462e85f3a310c9a45c0980d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:164ea428521838476ad13c7fe21c500d54ca3bd0e2c3e4fca0a2f3d3a93393d2 +size 20647 diff --git a/marked/Rel-18/26_series/26142/6f659142d4789aa889184459f884787e_img.jpg b/marked/Rel-18/26_series/26142/6f659142d4789aa889184459f884787e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a89c727d6212b79d5f75c2c27f0c4e6df38b531 --- /dev/null +++ b/marked/Rel-18/26_series/26142/6f659142d4789aa889184459f884787e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bead6db01efe34c8bbc97f5f2f8bdbd6659d86a19a5c113d63096fe6db934883 +size 7796 diff --git a/marked/Rel-18/26_series/26142/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-18/26_series/26142/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d79720a3e83e186ec89355f42d1f7b70c7f186b5 --- /dev/null +++ b/marked/Rel-18/26_series/26142/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99bc8f80f93ff0c571081aab58f392ec8c837cb03015e2cf6a9116bd3fc7a1b0 +size 46234 diff --git a/marked/Rel-18/26_series/26142/9a159e2112eac7be06bdb97e84a0c49a_img.jpg b/marked/Rel-18/26_series/26142/9a159e2112eac7be06bdb97e84a0c49a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64f7560b3575441b1d29e019158c1176259a6403 --- /dev/null +++ b/marked/Rel-18/26_series/26142/9a159e2112eac7be06bdb97e84a0c49a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa71f552e7579cb08ab35e642ac64ad06f4f705b832e149c0facd8a63339b3c3 +size 6871 diff --git a/marked/Rel-18/26_series/26142/a86610f7a0e579fec9f34dea52fa088b_img.jpg b/marked/Rel-18/26_series/26142/a86610f7a0e579fec9f34dea52fa088b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15c86151685d82d556bfddc9cc2db71c662cfc8b --- /dev/null +++ b/marked/Rel-18/26_series/26142/a86610f7a0e579fec9f34dea52fa088b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a93bebec760362fa6f5d0290959acc42edde2d9de71d3737991e45b875b11366 +size 20781 diff --git a/marked/Rel-18/26_series/26142/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/26_series/26142/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8edc2e0319a5fad1a64d56a8c939e6fafee451bd --- /dev/null +++ b/marked/Rel-18/26_series/26142/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76c8535cfd463706d71092f35858039d984571d5532b92a81970c284408eadb0 +size 59823 diff --git a/marked/Rel-18/26_series/26142/raw.md b/marked/Rel-18/26_series/26142/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b735bf35c01ccba9fca05ec4ac7fda078996ff41 --- /dev/null +++ b/marked/Rel-18/26_series/26142/raw.md @@ -0,0 +1,1476 @@ + + +# 3GPP TS 26.142 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Dynamic and Interactive Multimedia Scenes (DIMS) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|----------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Overview and architecture ..... | 9 | +| 5 Media-type definition..... | 9 | +| 5.1 Introduction ..... | 9 | +| 5.2 Media type components ..... | 9 | +| 5.3 Namespace ..... | 10 | +| 5.4 Scene description..... | 10 | +| 5.4.1 Base Scene Description ..... | 10 | +| 5.4.2 Scene Description Extensions ..... | 10 | +| 5.4.2.1 Introduction..... | 10 | +| 5.4.2.2 Rectangular clipping of a graphical object ..... | 10 | +| 5.4.2.3 Full-screen video..... | 10 | +| 5.4.2.4 Full-screen SVG ..... | 10 | +| 5.4.2.5 Attributes clipBegin and clipEnd..... | 11 | +| 5.4.2.6 Update Streams ..... | 11 | +| 5.4.2.7 Synchronization of Media Streams..... | 11 | +| 5.4.2.8 Screen orientation ..... | 11 | +| 5.4.2.9 Current-Time Indication ..... | 12 | +| 5.4.2.10 Active attribute ..... | 13 | +| 5.5 Scene Commands ..... | 13 | +| 5.5.1 Scene Updates ..... | 13 | +| 5.5.2 State management commands ..... | 13 | +| 5.5.3 Activate and Deactivate..... | 14 | +| 5.5.4 Distributed Random Access Points ..... | 15 | +| 5.5.4.1 Introduction..... | 15 | +| 5.5.4.2 DRAP syntax and semantics..... | 15 | +| 5.5.5 Immediate Script Execution ..... | 16 | +| 5.5.6 Seeking in the DIMS Stream..... | 16 | +| 5.6 DIMS Unit Definition ..... | 17 | +| 5.6.1 Definition..... | 17 | +| 5.6.2 DIMS Unit Header ..... | 17 | +| 5.7 Timing model..... | 18 | +| 5.8 Processing Model..... | 18 | +| 5.9 Random Access, Tune-in and Error Recovery..... | 20 | +| 5.9.1 Introduction ..... | 20 | +| 5.9.2 Random Access Points in Primary Streams ..... | 20 | +| 5.9.3 Random Access Points in Secondary Streams ..... | 20 | +| 5.9.4 Error Recovery ..... | 20 | +| 6 Interaction and Scripting..... | 21 | +| 6.1 Local interaction..... | 21 | +| 6.1.1 DOM Level 3 events ..... | 21 | +| 6.1.2 Media Access Events..... | 21 | +| 6.1.3 Screen Orientation Events ..... | 21 | +| 6.1.4 Other Events ..... | 21 | +| 6.2 Remote interaction ..... | 22 | +| 6.3 Scripting ..... | 22 | + +| | | | +|-------------------------------|------------------------------------------------------|-----------| +| 7 | Transport..... | 23 | +| 7.1 | Overview ..... | 23 | +| 7.2 | Storage in ISO Base Media File Format Files..... | 23 | +| 7.2.1 | Introduction ..... | 23 | +| 7.2.2 | Stream Type..... | 24 | +| 7.2.3 | Track and Media Header fields ..... | 24 | +| 7.2.4 | Sample Dependency Table..... | 24 | +| 7.2.5 | Sample Entry Name and Format ..... | 25 | +| 7.2.6 | Sample Format..... | 26 | +| 7.2.7 | Other Resources..... | 26 | +| 7.2.8 | Sync Samples..... | 26 | +| 7.2.9 | Separate Redundant Track..... | 26 | +| 7.3 | RTP Payload format for DIMS Streams ..... | 26 | +| 7.3.1 | Priority ..... | 26 | +| 7.3.2 | RTP Packet format ..... | 27 | +| 7.3.2.1 | Introduction..... | 27 | +| 7.3.2.2 | RTP Header Usage..... | 28 | +| 7.3.2.3 | Common Packet Header ..... | 28 | +| 7.3.2.4 | Aggregation Packet..... | 29 | +| 7.3.2.5 | Fragmentation Packets ..... | 29 | +| 7.3.3 | SDP Parameters ..... | 30 | +| 7.3.4 | Separate Redundant Stream..... | 30 | +| 8 | Profiles and Levels..... | 31 | +| 8.1 | Profiles ..... | 31 | +| 8.1.1 | Introduction ..... | 31 | +| 8.1.2 | Mobile profile..... | 31 | +| 8.2 | Levels ..... | 32 | +| 8.2.1 | Introduction ..... | 32 | +| 8.2.2 | Level Axes..... | 32 | +| 8.2.3 | Mobile Profile Level 10 definition ..... | 33 | +| 8.2.4 | Void ..... | 33 | +| 9 | Content usage guidelines ..... | 33 | +| 10 | Security and Content Protection Considerations ..... | 34 | +| 11 | Registered Types..... | 34 | +| 11.1 | RTP Payload format MIME Type..... | 34 | +| 11.2 | 'Codecs' Parameter for 3GP files..... | 36 | +| Annex A (normative): | Conformance Criteria..... | 37 | +| Annex B (informative): | Change history..... | 38 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +Dynamic and Interactive Multimedia Scenes (DIMS) is a dynamic, interactive, scene-based media system which enables display and interactive control of multimedia data such as audio, video, graphics, images and text. It ranges from a movie enriched with vector graphic overlays and interactivity (possibly enhanced with closed captions), to complex multi-step services with fluid interaction/interactivity and different media types at each step. The demand for such Rich Media service is increasing at a high pace, spurred by the development of the next generation mobile infrastructure and the generalization of TV content to new mobile environments. + +In the case of a video portal application, subscribers can watch TV, video and audio enriched with additional data (graphics, text, images) in streaming, progressive download or offline mode. DIMS provides a convenient and natural way to browse rich-media services, a web-like access (content available in less than three clicks, easy discovery, no learning curve), a permanent refresh of content through dynamic updates available on the fly and decreasing latency by allowing the visualization of data as soon as possible. + +Content can be synchronized up to a frame-accurate basis (e.g. to ensure content providers and operators that voting will start and stop at a precise time during a vote within an interactive show or to allow karaoke text flows). + +# --- 1 Scope + +DIMS defines a dynamic rich-media system, including a media type, its packaging, delivery, and interaction with the local terminal, user, and other local and remote sub-systems. Enhanced end-user experiences are provided by the coordinated management and synchronization of media and events, combined with end-user interaction. + +The DIMS media type can be used as a generic media type, allowing creating dynamic interactive rich-media services and can also benefit, or be used in association with other media types (e.g.: audio codecs, video codecs, XHTML browser, etc.). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] W3C Candidate Recommendation: "Scalable Vector Graphics (SVG) Tiny 1.2 Specification". + +NOTE: Available at: . + +[2] Open Mobile Alliance (July 2004): "ECMAScript Mobile Profile 1.0". + +[3] ISO/IEC 14496-20:2006: "Information technology - Coding of audio-visual objects - Part 20: Lightweight Application Scene Representation (LASEr) and Simple Aggregation Format (SAF)", including ISO/IEC 14496-20:2006/COR1, ISO/IEC 14496-20:2006/AMD1. + +[4] ISO/IEC 14496-22: "Information technology - Coding of audio-visual objects - Part 22: Open Font Format". + +[5] W3C Recommendation (December 2005): "Synchronized Multimedia Integration Language (SMIL 2.1)". + +NOTE: Available at: . + +[6] 3GPP TS 26.140: "Multimedia Messaging Service (MMS); Media format and codecs". + +[7] 3GPP TS 26.234: "Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs". + +[8] 3GPP TS 26.244: "Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)". + +[9] The Unicode Consortium: "The Unicode Standard", Version 5.0, . + +[10] ISO/IEC 14496-12: "Information technology - Coding of audio-visual objects - Part 12: ISO base media file format". + +[11] IETF RFC 1952 (May 1996): "GZIP file format specification version 4.3", P. Deutsch. + +[12] IETF RFC 2616 (June 1999): "Hypertext Transfer Protocol -- HTTP/1.1", R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee. + +[13] IETF RFC 4329 (April 2006): "Scripting Media Types", B. Hoehrmann. + +- [14] IETF RFC 4281 (November 2005): "The Codecs Parameter for "Bucket" Media Types", R. Gellens, D. Singer, P. Frodjh. +- [15] IETF STD 0064/RFC 3550 (July 2003) "RTP: A Transport Protocol for Real-Time Applications", H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson. +- [16] IETF RFC 2326 (April 1998): "Real Time Streaming Protocol (RTSP)", H. Schulzrinne, A. Rao, R. Lanphier. +- [17] W3C Document Object Model (DOM) Level 3 Events Specification, Version 1.0, W3C Working Draft 13 April 2006. +- NOTE: Available at: . +- [18] IETF RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", N. Freed, N. Borenstein. +- [19] W3C XML Events, an Events Syntax for XML, W3C Recommendation 14 October 2003. +- NOTE: Available at: . +- [20] W3C Media Access Events +- [21] IETF STD 65, RFC 3551 (July 2003): "RTP Profile for Audio and Video Conferences with Minimal Control", H. Schulzrinne, S. Casner. +- [22] IETF RFC 3388 (December 2002): "Grouping of Media Lines in the Session Description Protocol (SDP)", G. Camarillo, G. Eriksson, J. Holler, H. Schulzrinne. +- [23] IETF RFC 2965 (October 2000): "HTTP State Management Mechanism", D. Kristol, L. Montulli. +- [24] IETF RFC 3926 (October 2004): "FLUTE - File Delivery over Unidirectional Transport", T. Paila, M. Luby, R. Lehtonen, V. Roca, R. Walsh. +- [25] W3C Extensible Markup Language (XML) 1.0, Fourth Edition [Recommendation]. +- NOTE: Available at . +- [26] Open Mobile Alliance "Rich Media Environment (RME)". +- [27] ISO/IEC 14496-4:2004/AMD25 "Information technology - Coding of audio-visual objects - Part 4: Conformance Testing: Amendment 25: LASEr and SAF Conformance". +- [28] ISO/IEC 14496-4:2004/AMD27 "Information technology - Coding of audio-visual objects - Part 4: Conformance Testing: Amendment 27: LASEr and SAF Extensions Conformance". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**DIMS Scene:** an SVG scene, which may include extensions, and may be updated over time + +**DIMS Scene Commands:** a set of one or more commands to modify the state of a DIMS Scene + +**DIMS Unit:** the basic unit of transport, processing, and compression, of DIMS content + +**New Scene:** a complete scene (containing an "svg" element), suitable for starting a session or completely replacing the current scene in a session +(Functions very similarly to an I-frame in video) + +**Normal DIMS Unit:** DIMS Units processed when processing a stream (cf. Redundant DIMS Unit) + +**Primary Stream:** a stream which defines the complete scene tree, i.e. in which all random access points are, or build, a complete DIMS Scene + +**Redundant DIMS Unit:** DIMS Units which supply a redundant 'summary' of the stream, and which can be used for random access, tune-in, or error recovery (cf. Normal DIMS Unit) + +**Scene Update:** a set of differences that make changes to the scene in the current session +(Similar to a P-frame in video) + +**Secondary Stream:** a stream which manages only a portion of the scene tree + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|----------------------------------------------| +| API | Application Program Interface | +| AVP | Audio/Video Profile | +| CTR | CounTeR | +| DIMS | Dynamic and Interactive Multimedia Scenes | +| DOM | Document Object Model | +| FLUTE | File deLivery over Unidirectional Transport | +| HTTP | Hyper Text Transfer Protocol | +| IANA | Internet Assigned Numbers Authority | +| ID | IDentifier | +| LASER | Lightweight Application Scene Representation | +| MIME | Multipurpose Internet Mail Extensions | +| MMS | Multimedia Messaging Service | +| MTU | Maximum Transmission Unit | +| PSS | Packet switched Streaming Service | +| RAP | Random Access Point | +| RTP | Real-Time transport Protocol | +| RTSP | Real Time Streaming Protocol | +| SDP | Session Description Protocol | +| SMIL | Synchronized Multimedia Integration Language | +| SVG | Scalable Vector Graphics | +| TCP | Transmission Control Protocol | +| uDOM | microDOM | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| URL | Uniform Resource Locator | +| URN | Uniform Resource Name | +| W3C | World Wide Web Consortium | +| XHTML | eXtensible HyperText Markup Language | +| XML | eXtensible Markup Language | + +# 4 Overview and architecture + +![Figure 4-1: General architecture of the rich media system. The image is a placeholder with a red 'x' icon and the text: 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.'](a86610f7a0e579fec9f34dea52fa088b_img.jpg) + +Figure 4-1: General architecture of the rich media system. The image is a placeholder with a red 'x' icon and the text: 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.' + +**Figure 4-1: General architecture of the rich media system** + +The rich media system can be perceived as client-server architecture, comprising 3 main components: The rich media server, transport mechanisms and the rich media client. Figure 4-1 illustrates the general architecture. The server takes as input, rich media content comprised of scene description, discrete (e.g. images) and continuous (e.g. audio, video) media. Scene description can be dynamically updated through scene updates. The rich media content can be encapsulated into a container format, containing additional information such as media synchronization, metadata, and hint tracks for packetization. The system then utilizes various transport mechanisms for 1-to-1 and 1-to-many protocols for download, progressive download and streaming scenarios. The content is played on the client, allowing for local and remote interactivity of feedback and data requests. + +# 5 Media-type definition + +## 5.1 Introduction + +The DIMS media type allows spatial and temporal layout of the multimedia scene. This scene can consist of any combination of still pictures, video, audio, and animated graphics. It includes an update mechanism that allows for partial updates of the existing scene, as well as updating the presentation with a completely new scene and streaming tune-in functionality. + +## 5.2 Media type components + +The DIMS media type consists of: + +- Base scene description, which is SVG Tiny 1.2 [1]. +- Scene description extensions. +- Scene commands. +- Event generation and processing. + +## 5.3 Namespace + +The namespace called DIMS here is associated with the URN "". + +## 5.4 Scene description + +### 5.4.1 Base Scene Description + +SVG Tiny 1.2 provides the basic DIMS Scene functionality; layout, inclusion and referencing of objects, synchronization of object timelines and a rendering model. + +The full syntax and semantics of SVG Tiny 1.2 shall be supported for DIMS Scene functionality. The version and baseProfile attributes of the SVG element document the version and profile of SVG on which this scene is based. + +### 5.4.2 Scene Description Extensions + +#### 5.4.2.1 Introduction + +Extensions defined here are designed so that: + +- a) when the same functionality is present in profiles of SVG other than SVG Tiny 1.2, then the extension is compatible with that or a restricted version of that. +- b) A terminal implementing both the present document and SVG (any version) can use a common implementation of the DOM tree, scene graph, rendering model etc. without having variant handling that depends on whether the scene was built using DIMS or SVG. +- c) No extensions are required to be present in all documents; content authored to the SVG Tiny 1.2 specification may be used as the initial scene of a stream designed to the present document. + +The following extensions are defined here. + +#### 5.4.2.2 Rectangular clipping of a graphical object + +The lsr:rectClip mechanism provides pixel aligned clipping defined as a transformable rectangle. + +The lsr:rectClip element shall be supported. The definition of lsr:rectClip is defined in subclause 6.8.28 of [3]. + +#### 5.4.2.3 Full-screen video + +The full-screen video feature consists of the attribute lsr:fullscreen on the SVG video element. + +The lsr:fullscreen attribute shall be supported. The lsr:fullscreen attribute is defined in subclause 6.8.40.2 of [3]. + +See clause 10 for security considerations of fullscreen. + +#### 5.4.2.4 Full-screen SVG + +The fullscreen SVG feature in the DIMS namespace consists of an attribute 'fullscreen' on the element to hint that the scene should be rendered on the full screen. The possible values are "true" and "false" (default). With the attribute set to true the DIMS UE should negotiate the rendering area with its parent UE and get as large part of the screen as possible for the DIMS canvas. + +The dims:fullscreen attribute shall be supported on the svg element. + +See clause 10 for security considerations of fullscreen. + +#### 5.4.2.5 Attributes clipBegin and clipEnd + +Attributes clipBegin and clipEnd defined in subclause 7.6.1 of [5] shall be supported on the following elements: video, audio, animation, and the "updates" element as described in subclause 5.4.2.6. + +#### 5.4.2.6 Update Streams + +The present document defines a new element 'updates' in the DIMS namespace to link secondary streams of updates to a scene. This element has an implicit "simple duration" of 'indefinite'. The synchronization attributes defined in [1] subclause 12.6 can be used with this element. + +The dims:updates element shall be supported. + +NOTE: lsr:updates defined in subclause 6.8.53 of [3] is a superset of this element. + +*Attribute definitions:* + +All timing attributes defined in [1] subclause 16.2.7 are defined for this element, except the "fill" attribute. + +The attributes clipBegin and clipEnd defined in subclause 5.4.2.5, and syncReference defined in subclause 5.4.2.7, are defined for this element. + +xlink:href = "" + +An IRI reference to a source of updates, such as a DIMS stream/file. This attribute specifies the location of the stream of updates. In the absence of this attribute, this element does not have any effect. This attribute is not animatable and not inheritable. In DIMS, support is required only for DIMS streams or files. + +#### 5.4.2.7 Synchronization of Media Streams + +lsr:syncReference = "" + +The attribute lsr:syncReference from subclause 6.8.8.2 of [3] shall be supported on the elements video, audio, and animation from SVG, and 'updates' from the present document, with the associated synchronization behaviour. This attribute holds a reference to the stream or media element whose clock acts as a clock reference for the stream referred to by this element. This attribute is not animatable and not inheritable. + +#### 5.4.2.8 Screen orientation + +Two events and two extension strings are defined that make it possible for scenes to adapt to the screen layout. The events are defined in subclause 6.1.3. + +Whenever the terminal detects a change of orientation, angle, or screen size, one of these two events is dispatched. A portrait event is dispatched if the screen is taller than it is wide, and a landscape event is dispatched if the screen is wider than it is tall. It is the responsibility of the system below the scene to orient the screen buffer to user; the DIMS Scene author does not do this. + +In addition, the orientation is reported in degrees in screenAngle, to the best of the terminal's capability. This is measured as the angle between the positive X-axis of an un-rotated frame of reference, and the orientation of the longer of the positive X or Y axis of the screen, as rotated, as shown in Figure 5-1. Note that the SVG Y axis is downward. + +Specifically, for a screen that is normally portrait and in its normal position, the screenAngle is 90 degrees, since the longest axis is vertical, and the Y-axis is downward in SVG. Similarly, for a terminal that is normally landscape and in its normal position, the screenAngle is 0 degrees, since the longest axis is horizontal, and is the X-axis. This angle therefore would normally be close to 90 or 270 in portrait events, and close to 0 or 180 in landscape events, and 0 or 90 in terminals that are in their normal orientation, and 180 or 270 in terminals that are inverted. + +![A placeholder image with a red 'x' icon and the text 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.'](10953d657a5f47fdc829a800419dd370_img.jpg) + +A placeholder image with a red 'x' icon and the text 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.' + +**Figure 5-1: Screen Orientation** + +These events shall map to the `ScreenOrientationEvent` interface as defined in subclause 6.1.3. + +The screen orientation events shall be supported in DIMS. If the terminal has an orientation sensor, or other physical adaptation that causes the available screen drawing area to change (e.g. a partial cover), events shall be generated whenever the terminal detects a change in any of the parameters to these events. + +The following extension strings shall also be supported, in order to allow the use of the switch element: + +- `orientLandscape` for typical 'landscape' orientation; +- `orientPortrait` for typical 'portrait' orientation. + +The namespace of these feature strings is DIMS. + +If the most recent event generated was a portrait event, then `requiredExtensions="orientPortrait"` tests as true; if the most recent event was a landscape event, `requiredExtensions="orientLandscape"` tests as true. At any time, exactly one of these `requiredExtensions` expressions shall test as true. If no event has been generated, the appropriate `requiredExtensions` expression tests as true. + +Information on softkey location and key mapping may be found in section 9 of [26]. + +#### 5.4.2.9 Current-Time Indication + +In a Primary Stream, Redundant Random-Access Point there is a need to establish the current `SceneTime` of the scene, so that terminals tuning-in, performing random-access, or recovering from a lost high-priority DIMS Unit achieve the same `SceneTime` as terminals which had processed the entire stream from the most recent non-redundant Random Access Point. This media-time (scene time) is indicated by the `currentSceneTime` attribute on the SVG element, and takes a valid clock value in the document timeline, from the SVG specification [1]. + +The scene state is set exactly as if the SVG document had been loaded and displayed at the non-zero time `T` in the current-time indicator. + +**EXAMPLE:** This is the same as if this SVG scene had been used in a SMIL document as the target of an "animation" element with `clipBegin` of `T`, or if conceptually all absolute times `S` in the document were replaced with `S-T` and the document instantiated at time 0. + +*Attribute definition:* + +`currentSceneTime = ""` + +Specifies the current scene time (a valid clock value) in the document timeline, at which the scene is displayed. The scene state is set exactly as if the SVG document had been loaded and displayed at the non-zero time `T` in the current- + +time indicator. This attribute is defined in DIMS namespace, and may be present on the root SVG element in redundant random access points. The default value is zero. + +#### 5.4.2.10 Active attribute + +On all elements, the following attribute is defined in the DIMS namespace: + +`active`: this attribute defines whether the element is active. The possible values are "true" (default) and "false". + +Setting the value of this attribute to true or false is equivalent to executing the commands `activate` and `deactivate`. See subclause 5.5.3 for the behaviour of deactivated elements. This attribute is not animatable and not inheritable. + +The `dims:active` attribute shall be supported. + +## 5.5 Scene Commands + +### 5.5.1 Scene Updates + +The scene update mechanism allows reception of updates that change parts of the current scene, without having to replace the entire scene. + +To account for the different update scenarios two update mechanisms are defined: + +- **Primary-stream updates:** Updates are delivered to the client in the same stream as the original scene. +- **Secondary-stream updates:** Updates are delivered to the client in separate streams from the original scene, e.g. in an interactive scenario or initiated from the scene mark-up. + +In a primary-stream case, the updates and/or scene replacements are sent in the same stream as the initial scene. The temporal management of samples in a primary stream is based upon transport level timestamps. A secondary stream is a stream that does not contain the initial scene. A secondary stream is initiated directly from the DIMS mark-up using the 'updates' element. + +The following LASER commands from subclause 6.7 of [3] in LASER ML format shall be supported. + +- The LASER Insert command from subclause 6.7.5 of [3] shall be supported on elements, attributes and values in list attributes with the following relaxed constraints: values *may* be inserted on attributes `x` and `y` of the `text` element. +- The LASER Delete command from subclause 6.7.4 of [3] shall be supported on elements, attributes and values in list attributes. +- The LASER Replace command from subclause 6.7.8 of [3] shall be supported on elements, attributes and values in list attributes with the following relaxed constraints: attributes `attributeName`, `id`, `type`, `xml:space`, `preserveAspectRatio` and the `x` and `y` attributes of the `text` element *can* be replaced. There are no restrictions on the value of `attributeName`. The text regarding `executionTime` does not apply. +- The LASER Add command from subclause 6.7.2 of [3] shall be supported. + +### 5.5.2 State management commands + +The following state management commands shall be supported: + +- The LASER Save command from subclause 6.7.10 of [3] shall be supported. +- The LASER Restore command from subclause 6.7.9 of [3] shall be supported. +- The LASER Clean command from subclause 6.7.3 of [3] shall be supported. + +These LASER commands are defined as an interface to persistent storage. Selected scene information is cached on a best effort basis. The security principles behind this caching are those of the state caching mechanism in HTTP, commonly called cookies [23]. + +The saved data is defined by a groupID (known as "name" in [23]) and scoped by the "service" defined by a domain-name and path; for a command to operate on the data, all must match. + +The LASEr command "save" saves the values of a set of attributes, each identified by element ID and attribute name. Each save operation uses a groupID. Any other saved state with the same domain-name, path, and groupID is replaced. + +The LASEr command "restore" restores the attributes (if any) previously saved and scoped by the domain-name and path. The set of data restored is defined below. + +The LASEr command "clean" erases the attributes (if any) previously saved and scoped by the domain-name and path. The set of data erased is defined below. + +The following two attributes are defined in the stream signalling, and define the security restrictions for the above commands: + +- **useFullRequestHost**: this Boolean attribute indicates whether the full domain-name of the request-host is used (true, 1) or the first component of the domain-name is elided (false, 0). For example, if the source material came from "www.example.org", then this differentiates between associating the "service" with "www.example.org" and ".example.org". (Note the definition of local names in [23], and the possibility to associate the "service" with locally loaded files, and that the domain-name may be either ".local" or ".local" in that case.) +- **pathComponents**: this 4-bit unsigned integer attribute indicates how much of the source path is used. If this takes the value 0, then the "service" is not associated with a path, and if it takes the special value 15 (or any value equal to or greater than the number of components in the path) then the entire path is used up to but excluding the final file-name. For example, if the source was "/user/laser-expert/demo/art.mp4" then a value of 3 or greater selects "/user/laser-expert/demo" as the path, the value 2 selects "/user/laser-expert" and the value zero sets no path. + +Data is saved as a set of four values, using the URI, pathComponents and useFullRequestHost from the stream containing the save command: + +- the domain-name formed from the URI and useFullRequestHost; +- the path formed from the URI and pathComponents; +- the groupID; +- the set of {element-ID, attribute-name, value} triplets. + +When a restore command is executed all saved sets with the same (equal) groupID, and also where the URI of the stream containing the restore command matches the saved domain-name and path, are restored. This matching is defined in section 3.3.4 of [23]. + +A clean command behaves exactly the same as a save command that saves no state; as is normal for the save command, any other saved state with the same domain-name, path, and groupID is replaced, in this case, with an empty set of saved data. This is functionally equivalent to deleting that saved state, as nothing would be restored. + +NOTE: Be aware that though the data saved and restored is scoped by stream, once it is restored into the tree it is globally visible. + +### 5.5.3 Activate and Deactivate + +The commands activate and deactivate as defined in subclauses 6.7.12 and 6.7.13 of [3] shall be supported, in a manner that is functionally equivalent to that specification. These commands have one attribute: + +- **ref**: the id of the element which is to be activated or de-activated. + +When an element is deactivated, the system then treats the DOM tree as if that element and its descendents were not present in the DOM tree, and invisible to everything except commands and scripts. Commands and scripts can reference it as if it were still in the DOM tree. When activated, the element is then restored to visibility, in the same location in the tree as if it had not been previously deactivated. + +The active attribute is not inherited. However, activated and de-activated events are generated if the effective active state of an element changes as a result of a change to the active state of a parent. This means that a deactivated event may occur for an element, as a result of deactivating a parent, when a test of its dims:active attribute value returns true. + +### 5.5.4 Distributed Random Access Points + +#### 5.5.4.1 Introduction + +A Distributed Random Access Point (DRAP) is a redundant DIMS tune-in point (either primary or secondary) that can, instead of explicitly defining all elements itself, reference elements in coming DIMS units. The commands in these following DIMS units are not executed, elements are simply copied according to references in the DRAP. These references can be used to reduce redundancy (i.e. not defining an element both in a RAP and an update) or to simply spread the size of the RAP over a period of time. + +After this copying operation, the pending action(s) in the DRAP are complete, and are then executed, and normal processing resumes. + +![A placeholder image with a red 'x' icon and the text 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.'](0a5acc4b370bb711096e04f25b8b3feb_img.jpg) + +A placeholder image with a red 'x' icon and the text 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.' This image is a placeholder for Figure 5-2, which is described in the caption as 'Illustration of the DRAP Concept'. + +A placeholder image with a red 'x' icon and the text 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.' + +**Figure 5-2: Illustration of the DRAP Concept** + +#### 5.5.4.2 DRAP syntax and semantics + +The rootmost element in a DRAP document shall be a element in the DIMS namespace. A DIMS Unit containing a DRAP shall contain only the DRAP. + +*Attribute definitions:* + +`unitsrequired="units-required"` + +Indicates the number of coming DIMS units required. + +NOTE 1: These DIMS units are *not* executed in the normal way when tuning in using DRAP; instead, they are used as needed as a source of material for the DRAP. + +The DRAP element contains one or more getfromupdate elements, which form the processing instructions, and one or more other elements that form the pending action(s). The processing instructions are applied to the pending action. The indicated number of DIMS units are processed for the DRAP, and the pending action(s) are performed at the time of the DIMS unit at the indicated distance, and normal DIMS unit processing resumes. + +NOTE 2: All the getfromupdates should have been resolved by the indicated distance. + +The getfromupdate element shall reference an element in another DIMS unit and an element in the pending actions. The element referred to in the other DIMS unit shall replace the element in the DRAP pending actions. + +*Attribute definitions:* + +`source="elementid"` + +Specifies an xml id appearing in an upcoming DIMS unit. If the same xml id appears in different DIMS units, it shall not make a difference which one the client chooses. + +`target="elementid"` + +Specifies an xml id appearing in the DRAP pending action(s). + +### 5.5.5 Immediate Script Execution + +The doScript command in the DIMS namespace shall be supported. This command supplies a script for immediate execution, including the ability to update the DOM. It has a single attribute, the type of the script. The script is in the body of the element. Processing this command involves executing the script in the context of the DIMS stream in which it occurs. + +*Attributes:* + +`type` - is a string that identifies the scripting language used. It takes a suitable MIME type [18] from the IANA registry, such as "application/ecmascript" (see [13]). + +An example is: + +``` + + var root = document.documentElement; + var myGroup = document.createElementNS( + "http://www.w3.org/2000/svg", "g"); + myGroup.id = "myGroup"; + root.appendChild(myGroup); + var myRect = document.createElementNS( + "http://www.w3.org/2000/svg", "rect"); + myRect.id = "myRect"; + var color = root.createRGBColor( 255, 0, 0); + myRect.setRGBColorTrait("fill", color); + myRect.setFloatTrait("x", 10); + myGroup.appendChild(myRect); + +``` + +### 5.5.6 Seeking in the DIMS Stream + +`` + +*Attributes:* + +`seekOffset`: A clock value from subclause 16.2.7 of [1]. + +The command seek in the DIMS namespace results in a seek, by the amount `seekOffset`, in the DIMS stream timeline. The target stream time is obtained by adding `seekOffset` to the current stream time. As a DIMS stream may contain multiple scenes, this seeking can result in a change of scene. A seek to the local time corresponding to the `seekOffset` shall be applied to the (possibly new) scene. The seek command shall be supported. + +**NOTE:** Seeking can be conceptually seen as a function where the global timeline and document timelines are moving forward in a synchronized manner, just as in normal playback, but more quickly and without rendering. A seek backwards in time (negative `seekOffset`) could be done in a similar way, but by starting again from zero and moving forward. + +## 5.6 DIMS Unit Definition + +### 5.6.1 Definition + +A DIMS Unit is built from a header and a body. The DIMS Unit Body is either: + +- a complete SVG document as specified in subclause 5.4, possibly using extensions; or +- a textually concatenated sequence of scene commands as specified in subclause 5.5; + +A DIMS Unit Body may be compressed. + +DIMS Units are framed by the transport layer. Each DIMS Unit has certain characteristics, signalled by the DIMS Unit Header. + +There are DIMS Units used in redundant processing, and DIMS Units used in normal processing. Redundant DIMS Units, and DIMS Units marked as random-access points, are used in random access, tune-in, and error recovery; for a full description of their processing model, see subclause 5.8. + +### 5.6.2 DIMS Unit Header + +DIMS Unit Header is 1 byte long. The length of a DIMS Unit is the length of the DIMS Unit Body plus the length of the DIMS Unit Header. DIMS Unit lengths are carried by the transport layer. + +The DIMS Unit Header has the following layout. + +![](6f659142d4789aa889184459f884787e_img.jpg) + +``` + ++-----+ +|0|1|2|3|4|5|6|7| ++-+-+-+-+-+-+-+-+-+ +| X |C|P|D|I|M|S| ++-----+ + +``` + +**Figure 5-3: DIMS Unit header** + +These fields have the following definitions: + +- S: is-Scene: when 1, indicates that the DIMS Unit contains a Scene Description as documented in subclause 5.4; when 0, indicates that the DIMS Unit contains one or more Scene Commands as documented in subclause 5.5. +- M: is-RAP: when 1, indicates a Random Access Point; when 0, indicates a non-Random-access point. +- I: is-redundant: when 0, indicates a main (normal processing) DIMS Unit; when 1, signals a redundant DIMS Unit. +- D: redundant-exit: shall be 0 on DIMS Units with is-redundant==0; on DIMS Units with is-redundant==1, when 1, indicates that redundant processing is completed by this DIMS Unit, and normal processing should begin, and when 0, indicates that redundant processing should continue. +- P: priority set to 1 indicates a high-priority unit; when set to 0 indicates a low-priority unit. A unit marked as low-priority indicates that if the unit, or any sequence of such low-priority units, is not processed by the terminal: +- all succeeding DIMS Units can be decoded and operated on without error (e.g. their DOM updates do not depend on the possibly lost command(s).) + - the visual and semantic nature of the scene is satisfactory to the content author. + - The loss of those units does not require the terminal to enter into a tune-in or repair state. + +Units fulfilling the above criteria should be marked as low-priority, and shall be marked as high-priority otherwise. + +DIMS Units with is-redundant set to 1 should normally be marked as low-priority, to avoid their loss causing an un-needed entry into tune-in state when redundant and normal data are carried in the same transport. + +C: compression: indicates the compression applied; +0 indicates no compression (textual format); +1 indicates that the content is compressed using the encoding signalled in stream setup. + +X: reserved: shall be set to 0 and shall be ignored by the receiver + +NOTE: The setting of the priority field is, due to point 2 above, partly at the discretion of the content creator. An example of a simple method of evaluating point 2 is to see if, when the next packet is received, the terminal state is identical to what it would have been if the DIMS Unit(s) had not been lost in the first place. + +## 5.7 Timing model + +DIMS inherits the timing model from [1] in its entirety. This section defines the timing of DIMS units. + +DIMS units are associated with a media timestamp which marks + +- the time when the SVG scene is instantiated and the scene time resets to 0, for New Scenes, or +- the time when DIMS units are applied and affect the scene, for other DIMS units. + +The processing order for scene updates is the same as for script and event processing. The present document does not mandate any relative timing or processing order for DIMS units, scripts or events that shall be processed at the same scene time. DIMS Units from the same stream shall be processed in decoding order, i.e. sequence number order in RTP or order inside a sample in the 3GP file format. + +In the main stream the SVG time has periodic resets to 0 on each New Scene (what SVG calls "document time" and is called here "SVG Scene Time"). The SVG scene time, and the media timestamps of the DIMS presentation, are related by a piecewise linear relationship, with discontinuities only at the New Scenes. Secondary streams are synchronized to the main stream using the normal mechanisms for media streams. + +DIMS Units containing commands, with the same timestamp in the same stream, are applied "instantaneously" in scene time, that is, the scene time does not change while they are being applied. + +DIMS units containing commands are applied atomically and have exclusive access to the scene tree during processing; only events and scripts directly resulting from the processing of the DIMS unit, are run. + +## 5.8 Processing Model + +A Scene Description is processed as a complete replacement for the current scene tree. That is, the entire DOM is discarded and replaced with the result of parsing the SVG element. All other DIMS Units retain (and possibly modify) the current scene tree. + +All high-priority data units not marked as redundant shall be processed during normal decoding. All low-priority data units not marked as redundant should be processed during normal decoding. Data units marked as redundant should be ignored during normal processing. All data units marked as RAP are suitable tune-in points. When tuning-in to a stream, decoding shall begin by, at the latest, the first unit marked as RAP irrespective of the value of its is-redundant flag. + +If a normal (non-redundant) random access point is identified during redundant processing or DRAP processing, the normal random access point should take precedence. + +Commands that cannot be executed (e.g. they refer to a DOM node which does not exist) shall be ignored when in tune-in or redundant-processing. This condition should not arise in normal processing, and their handling in this state is not defined by the present document. + +The following state diagram, and processing pseudo-code for each state, illustrate the states and the use of the various flags in the DIMS unit header, and comply with the mandatory and recommended processing requirements. The state diagram and pseudo-code, or better, should be implemented in DIMS clients. + +In the state diagram and pseudo-code, the terminal may be processing a stream under one of three conditions: + +- a) normal processing, 'normal'; +- b) after tuning in, performing random access, or when loss is detected, 'tune-in'; +- c) while processing redundant DIMS units, 'process-redundant'. + +Tune-in state is entered under any of the following circumstances: + +- a) after opening a stream; +- b) after performing random access; +- c) after loss of a high-priority DIMS Unit in normal processing; +- d) after loss of any DIMS Unit in redundant processing. + +![A placeholder for the DIMS Client State Diagram. The image cannot be displayed, and the file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.](67af94a7c462e85f3a310c9a45c0980d_img.jpg) + +A placeholder for the DIMS Client State Diagram. The image cannot be displayed, and the file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location. + +**Figure 5-4: DIMS Client State Diagram** + +The following behaviour is performed for each DIMS Unit in each state, and then a state transition is performed as indicated by the state diagram. + +``` +Normal state: + if DIMS-Unit.is-redundant + then Discard(DIMS-Unit) + else Process(DIMS-Unit); + +Tune-in state: + if DIMS-Unit.is-RAP + then Process(DIMS-Unit) + else Discard(DIMS-Unit); + +Redundant-processing: + if ( DIMS-unit.is-redundant) || +``` + +``` +((not DIMS-Unit.is-redundant) && DIMS-unit.is-RAP) +then Process(DIMS-unit) +else Discard(DIMS-Unit); +``` + +Where this pseudo-code indicates that a DIMS Unit is processed, then if a Distributed Random Access Point (DRAP) is in process, elements required by the DRAP are extracted from this unit. If a DRAP is not in process, the DIMS Unit is processed as normal. If one of the DIMS units identified by units-required is a normal (non-redundant) random access point, DRAP processing should be abandoned, and that normal RAP processed in the usual way. + +## 5.9 Random Access, Tune-in and Error Recovery + +### 5.9.1 Introduction + +Random access points in streams are either normal random access points or redundant random access points. Normal random access points are processed by terminals in all states. Redundant random access points should only be processed by terminals when performing random access, tune-in, or error recovery. + +Random access points are indicated in the DIMS Unit header using the is-RAP flag. Redundant random access points have the is-Redundant flag set to 1; normal Random Access points have this flag set to 0. + +### 5.9.2 Random Access Points in Primary Streams + +A Random Access Point (normal or redundant RAP) in a primary stream shall either contain an entire scene (i.e. be a Scene Description) or the mechanism to build an entire scene (such as DRAP). When used, this scene becomes the current scene and replaces all previous data. There may be further DIMS Units with the same timestamp that modify the scene tree. + +A redundant Random Access Point in a primary stream shall have the currentSceneTime attribute on the SVG element. Any following commands in subsequent DIMS Units with the same timestamp are processed at this time. + +### 5.9.3 Random Access Points in Secondary Streams + +A Random Access Point (normal or redundant RAP) in a secondary stream shall either contain an entire update (i.e. a series of commands) or the mechanism to build an entire update (such as DRAP). The command(s) provided set the scene (specifically, the portion of the scene managed by the secondary stream) into an appropriate state, whether the random access point is used for initial tune-in, or for error recovery. + +**NOTE:** The secondary stream needs to be encoded in such a way that it does not matter which packets were lost or this is an initial tune-in or random access - the appropriate state is set. This would include removing any elements or attributes which should have been removed, etc. A simple way of encoding such a stream would be to only let updates in a secondary stream make modifications to a few nodes. Then this operation could be as simple as removing these few nodes and reinserting them, removing all potential errors. + +### 5.9.4 Error Recovery + +There are several error resilience mechanisms available in DIMS. Among these are: + +- **Priority:** By separating essential and non-essential units one can determine if a loss need repair or not. This is described in subclause 7.3.1. +- **Periodic Random Access Points (RAPs):** Random Access Points can be placed periodically in a stream. In the case of error one can tune-in to the channel again. +- **Separation of static and dynamic data.** This can even increase the efficiency of Distributed Random Access Points. + +A combination of these methods can be used. + +# 6 Interaction and Scripting + +## 6.1 Local interaction + +### 6.1.1 DOM Level 3 events + +The supported local events and their management in DIMS are built upon the events model described in [1]. + +They include DOM Events (focus, activate, etc.), SVG Events (connection, load, etc.) and general XML events [19] (user events, timing, key, and pointer events). + +### 6.1.2 Media Access Events + +The media access events defined in [20] shall be supported. + +### 6.1.3 Screen Orientation Events + +The following events shall be supported. + +| Event Type | Namespace | Description | Interface | Bubble | Canc | +|------------------------------|-----------|-----------------------------------------------------------------------|------------------------|--------|------| +| "screenOrientationPortrait" | DIMS | The screen orientation has changed to typical 'landscape' orientation | ScreenOrientationEvent | No | No | +| "screenOrientationLandscape" | DIMS | The screen orientation has changed to typical 'portrait' orientation | ScreenOrientationEvent | No | No | + +``` +interface ScreenOrientationEvent : Event +{ + readonly attribute unsigned long screenWidth; + readonly attribute unsigned long screenHeight; + readonly attribute unsigned long screenAngle; +} +``` + +**screenWidth** - contains the new screen display or viewport width. + +**screenHeight** -contains the new screen display or viewport height. + +**screenAngle** - documents the angle between the primary axis of the screen, and an unrotated horizontal axis (see 5.4.2.8) with a value between 0 and 359 inclusive. + +NOTE: A superset of the ScreenOrientationEvent interface is specified in [26]. + +### 6.1.4 Other Events + +The events pauseevent and resuméevent from subclause 6.5.2 of [3] shall be supported. + +The following events shall be supported. + +| Event Type | Namespace | Description | Interface | Bubble | Canc | +|--------------------|-----------|--------------------------------------------------------------------|------------------------|--------|------| +| "activatedEvent" | DIMS | Occurs when an element changes state from deactivated to activated | Event (Annex A of [1]) | No | No | +| "deactivatedEvent" | DIMS | Occurs when an element changes state from activated to deactivated | Event (Annex A of [1]) | No | No | + +## 6.2 Remote interaction + +Client-server communication is possible in the DIMS system using three different mechanisms: + +- The client can open a suitable URL. The set of valid URL forms is not specified in DIMS, and may include, for example, protocols such as HTTP [12], RTSP [16] or MailTo. +- By establishing a socket connection between the client and the server using the Connection API in the uDOM [17]. +- By using the HTTP specific SVG uDOM methods `getUrl` or `postURL` [17]. + +## 6.3 Scripting + +SVG Tiny 1.2 contains a uDOM interface that provides linkage to a script engine and adds the possibility to modify the DOM representation of the scene from scripts. + +ECMAScript mobile profile (MP) [2] can be used in conjunction with the `script` and `handler` elements and SVG uDOM API (Appendix A of [1]) in order to provide more powerful DOM manipulation, and interaction. + +UEs supporting the DIMS media type shall support ECMAScript mobile profile (MP) [2] with the following extensions to uDOM API. + +Table 1 adds to the table in subclause A.8.12 of [1]. It contains trait access rules for DIMS extensions. + +**Table 1: Trait access rules for DIMS extensions** + +| Attribute | Trait Getter | Trait Setter | Default Values | Description | +|------------------------------|---------------------------------------|---------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| lsr:fullscreen | getTraitNS[true false] | setTraitNS[true false] | false | Available on <video> element | +| dims:fullscreen | getTraitNS[true false] | setTraitNS[true false] | false | Available on the <svg> element | +| lsr:x | getFloatTraitNS | setFloatTraitNS | 0.0f | Origin x of the <rectClip> | +| lsr:y | getFloatTraitNS | setFloatTraitNS | 0.0f | Origin y of the <rectClip> | +| lsr:width | getFloatTraitNS | setFloatTraitNS | 0.0f | Width of the clipping region defined by <rectClip> | +| lsr:height | getFloatTraitNS | setFloatTraitNS | 0.0f | Height of the clipping region defined by <rectClip> | +| smil:clipBegin | getTraitNS | setTraitNS | "" | Available on <video> , <audio> , <animation> , and <updates> elements | +| smil:clipEnd | getTraitNS | setTraitNS | "" | Available on <video> , <audio> , <animation> , and <updates> elements | +| dims:active | getTraitNS[true false] | setTraitNS[true false] | true | Available on all SVG elements | + +**Description of `getFloatTraitNS` and `setFloatTraitNS` methods available on the `TraitAccess` interface:** + +**`float getFloatTraitNS(in DOMString namespaceURI, in DOMString name) raises(DOMException);`** + +- Same as `getFloatTrait`, but for namespaced traits. Parameter `name` shall be a non-qualified trait name, i.e. without prefix. + +### **Parameters:** + +`namespaceURI` - the `namespaceURI` of the trait to retrieve. + +`name` - the name of the trait to retrieve. + +### **Return Value:** + +the trait value as float. + +### **Exceptions:** + +`DOMException` - with error code `NOT_SUPPORTED_ERR` if the requested trait is not supported on this element or null. + +[DOMException](#) - with error code TYPE\_MISMATCH\_ERR if requested trait's computed value cannot be converted to a float. + +**void setFloatTraitNS(in DOMString namespaceURI, in DOMString name, in float value) +raises(DOMException);** + +Same as setFloatTrait, but for namespaced traits. Parameter name shall be a non-qualified trait name, i.e. without prefix. + +### Parameters: + +namespaceURI - the namespaceURI of the trait to be set. + +name - the name of the trait to be set. + +value - the value of the trait to be set as float. + +### Exceptions: + +[DOMException](#) - with error code NOT\_SUPPORTED\_ERR if the requested trait is not supported on this element or null. + +[DOMException](#) - with error code TYPE\_MISMATCH\_ERR if the requested trait's value cannot be specified as a float (for e.g. NaN) + +[DOMException](#) - with error code INVALID\_ACCESS\_ERR if the input value is an invalid value for the given trait or null. + +ECMAScript bindings for the extensions defined in this specification can be found in Appendix D of [26]. + +# --- 7 Transport + +## 7.1 Overview + +The transport mechanisms support rich media delivery in the following modes: Unicast download (HTTP/TCP [12] or MMS [6] protocol), broadcast/multicast download (FLUTE/UDP [24]), unicast streaming and broadcast/multicast streaming (RTP/UDP [15]). For download mode, reliability is guaranteed by existing mechanisms in the transport and network layers, and no error resilience tools need to be designed at the application layer for rich media delivery. However, rich media transport in streaming mode is more challenging, with UDP being unreliable. Therefore, the RTP design provides some error resilience tools to help the media decoder cope with unreliable transport. + +Rich media is a combination of continuous media and discrete media and relevant transport mechanisms for these two media types should be used. Rich media streaming is thus naturally realized by: + +- a) streaming continuous media such as scene streams, video and audio; and +- b) downloading the discrete media, such as images. + +DIMS Units can be classified as either used in normal processing, or used only for 'redundant' processing. For a given DIMS data-stream, these two kinds of DIMS Units can be managed either: + +- a) in a single transport; or +- b) in two separate transports. + +## 7.2 Storage in ISO Base Media File Format Files + +### 7.2.1 Introduction + +DIMS streams, both primary streams (those containing SVG scenes) and secondary streams (which normally carry only updates) are carried in files of the ISO Base Media File Format [10] (including 3GP files [8]) according to this subclause. + +Either one or two tracks are used in the file for the normal and redundant DIMS Units. + +### 7.2.2 Stream Type + +Scenes are carried in scene tracks in ISO family files. They therefore use: + +- a) a video media handler 'vmhd'; +- b) a media handler type of 'sdsm' (scene description media handler); +- c) a derivative of the base SampleEntry in the sample description box. + +The timescale for the stream should be suitably chosen to achieve the desired accuracy of timing. + +### 7.2.3 Track and Media Header fields + +The width and height in the track header shall be set in the desired ratio, and indicate the suggested minimum display size. A player on a system with an indefinitely large display, in the absence of a fullscreen request, could use this size as a suggested initial display size. + +If the presentation has an expected, reasonable duration, then it is encoded as the track duration. Otherwise the ISO file format recommendation of maxint for the duration, when it is indeterminate, should be used. + +The language code of the track should be set appropriately if the presentation is language-specific, or else the value 'und' (undetermined) or 'mul' (multiple) should be used. + +### 7.2.4 Sample Dependency Table + +The sample dependency table may be used. The 'unknown' field values may be needed under some circumstances. The fields have the following semantics for DIMS streams: + +`sample_depends_on` should be set according to whether the sample contains a normal DIMS Unit (not is-redundant) with is-RAP set to 1: + +- 0: unknown; +- 1: this sample does not contain a normal RAP; +- 2: this sample does contain a normal RAP; +- 3: reserved. + +`sample_is_depended_on` should be set according to the value of the P-bit in the DIMS Unit headers: + +- 0: unknown; +- 1: one or more DIMS Units have the P-bit set to 1; +- 2: no DIMS Unit has the P-bit set to 1 (low-priority sample); +- 3: reserved. + +`sample_has_redundancy` should be set to indicate whether the sample contains redundant DIMS Units: + +- 0: unknown; +- 1: one or more DIMS Units have the is-redundant bit set to 1; +- 2: no DIMS Unit has the is-redundant set to 1; +- 3: reserved. + +### 7.2.5 Sample Entry Name and Format + +The sample entry four-character code for scenes is 'dims'. The configuration box shall be present in the sample entry. + +``` + +class SceneConfiguration extends FullBox ('dimC', version = 0, 0){ + unsigned int(8) profile; + unsigned int(8) level; + unsigned int(4) pathComponents; + unsigned int(1) useFullRequestHost; + unsigned int(1) stream_type; + unsigned int(2) contains_redundant; + string text_encoding; + string content_coding; +} +class MPEG4BitRateBox extends Box('btrt'){ + unsigned int(32) bufferSizeDB; + unsigned int(32) maxBitrate; + unsigned int(32) avgBitrate; +} + +class DIMSScriptTypes extends Box('diST') +{ + string content_script_types; +} + +class DIMSSampleEntry() extends SampleEntry ('dims'){ + SceneConfiguration config; // mandatory + DIMSScriptTypes scripts; // optional + MPEG4BitRateBox bitrateinfo; // optional +} + +``` + +The fields have the following semantics: + +- `profile` – Specifies the profile of DIMS used, for example the valued indicating Mobile Profile as defined in section 8.1 +- `level` – Specifies the minimum DIMS level needed to be able to display the scene as defined in section 8.2. +- `stream_type` - takes the value 1 for primary streams, and the value 0 for secondary streams. Files containing secondary streams are not normally playable by themselves, outside the context of the scene(s) they are designed to update. +- `contains_redundant` - takes the value 1 ("main") if the stream contains only DIMS Units with is-redundant set to 0, the value 2 if the stream contains only DIMS Units with is-redundant set to 1 ("redundant"), and takes the value 3 ("main+redundant") if both occur. The value 0 is reserved. Note that streams containing only redundant units must be linked to the main stream for which they are redundant (see subclause 7.2.9). +- `text_encoding` - is a null terminated string with possible values taken the XML specification for character encoding in entities (e.g. subclause 4.3.3 of XML 1.0 Fourth edition [25]). It describes the text encoding after the content has been de-compressed (e.g. after deflating). This field is only applicable if the content is transmitted as (possibly encoded) text. An empty string shall be used otherwise. +- `content_coding` - this field provides the identification of the compression scheme. It is a null terminated string specifying the encoding (compression) format of the content. It is defined in the same way as the content-coding header in HTTP (subclause 3.5 of [12]). An empty string indicates that no compression is used. +- `content_script_types` - is a null terminated string that identifies the scripting languages used. It is a comma-separated list of MIME types [18] from the IANA registry, such as "application/ecmascript" (see [13]). It shall provide a complete listing of the script types that the terminal must support in order to process the stream. If the box is not present, the set of required script types is unknown. If the box contains the empty string, then the stream does not require any script processing. +- `bufferSizeDB` gives the size of the decoding buffer for the elementary stream in bytes. This is the size of the largest buffer needed to hold a sample in textual format, in bytes (i.e. after any de-compression). +- `maxBitrate` gives the maximum rate in bits/second over any window of one second. +- `avgBitrate` gives the average rate in bits/second over the entire presentation. + +- `useFullRequestHost` and `pathComponents` are defined in subclause 5.5.2. + +The `text_encoding` is required to be consistent over all the DIMS units described by this sample entry. This simplifies processing. It is an error to have a mismatch between this value and those present in the XML of the DIMS units themselves. + +### 7.2.6 Sample Format + +A sample is a concatenated sequence of one or more DIMS Units associated with the same media time, with a two-byte length field in network (big-endian) format preceding each DIMS Unit. The length is the length of the DIMS Unit not including the length field itself (that is, the combined length of the DIMS Unit Body and DIMS Unit Header). + +A sample may contain one or more Normal DIMS Units or Redundant DIMS Units, or both, associated with the same media time. + +### 7.2.7 Other Resources + +Other resources may be carried in the meta-data directories of ISO files, in the track containing the scene, the movie containing that track, or the file containing that movie. If there is no actual meta-data (the meta-data block is there merely to carry resources), the meta-data handler type 'null' may be used. + +URL forms to address these resources are defined in the ISO specification, and are relative to the file containing the resource. + +The meta data box may also be used for multi-scene presentations where the meta box includes the initial SVG scene, and one of the tracks provides the updates. + +### 7.2.8 Sync Samples + +The sync sample table marks samples in which any of the DIMS Units have the is-RAP bit set to 1. + +NOTE: The use of the shadow sync box is deprecated. + +### 7.2.9 Separate Redundant Track + +Redundant DIMS Units may be stored in the file format using a separate track. The redundant track shall be linked to the matching main track by a track reference of type 'swto' in the redundant track. + +Redundant tracks are identified by this track reference, and shall also have `contains_redundant` set to "redundant data only" in their sample entry. The track they link to shall have `contains_redundant` set to "main data only". + +If a stream is converted from a single-track to two-tracks, some small adjustment may be needed. Specifically, any 'normal' DIMS Units following the redundant-exit indication in the same sample will need to be copied into the 'redundant' track, marked as 'redundant' DIMS Units, and the redundant-exit indication moved to the last such DIMS Unit in the sample. + +A terminal may perform tune-in etc. using the 'redundant' track by: + +- a) finding the random access point in the redundant track, closely preceding the desired play point, by using the sync sample table; +- b) processing DIMS Units from the redundant track until the redundant-exit indication; +- c) following the 'swto' track reference and commencing processing at the temporally next sample in the linked (main) track. + +## 7.3 RTP Payload format for DIMS Streams + +### 7.3.1 Priority + +The counter (CTR) field is used to detect the loss of high priority DIMS units. Encoders and decoders keep a running value of the counter; the encoder places in each packet the current value of the counter; after being placed in the packet, the running counter is incremented by one if that packet contains one or more DIMS Units with high priority. The decoder compares the CTR field of each incoming packet with its running counter, and thereby checks for high-priority loss. After the check, the decoder's running counter is incremented by one if the received packet contains one or more DIMS Units with high priority. + +NOTE: A discontinuity in the sequence number indicates a lost packet. A discontinuity in the CTR field indicates the number of prioritized packets which have been lost. + +An example of the use of the CTR and priority (P) bits is shown below: + +![Figure 7-1: Example of prioritization including detection of lost prioritized packets. The image is a placeholder with a red 'x' and the text: 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.'](1695df64fe320e3f81049cfe402c8155_img.jpg) + +Figure 7-1: Example of prioritization including detection of lost prioritized packets. The image is a placeholder with a red 'x' and the text: 'The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location.' + +**Figure 7-1: Example of prioritization including detection of lost prioritized packets** + +Note that loss is only detected on the next packet to arrive; if the content has long periods in which no packets are sent, or is otherwise bursty, it may be inadvisable to have a high-priority packet before a long silence interval, as its loss cannot be detected until the first packet after that interval, at the earliest. + +### 7.3.2 RTP Packet format + +#### 7.3.2.1 Introduction + +In the context of the present document (specifically the MIME type defined in subclause 11.1), the units carried by the RTP Payload Format are DIMS Units. The RTP payload format defines two basic packet structures: + +- a) packets containing one or more entire units; +- b) packets containing a single fragment of a unit. + +Depending on the underlying network and the unit size, it may be desirable to split units or aggregate them. + +#### 7.3.2.2 RTP Header Usage + +The RTP header is defined in [15] and its use in this payload format is described below. + +![Figure 7-2: RTP HEADER diagram showing the structure of the header with fields like Version (V), Payload Type (PT), Sequence Number, Timestamp, SSRC, and CSRC identifiers.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +|V=2|P|X| CC |M| PT | sequence number | ++---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +| timestamp | ++---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +| synchronization source (SSRC) identifier | ++---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +| contributing source (CSRC) identifiers | +| . . . . . | ++---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ + +``` + +Figure 7-2: RTP HEADER diagram showing the structure of the header with fields like Version (V), Payload Type (PT), Sequence Number, Timestamp, SSRC, and CSRC identifiers. + +Figure 7-2: RTP HEADER + +**Marker bit (M):** 1 bit - The marker bit is set for the last packet associated with a timestamp. + +**NOTE:** This is useful when a scene is sent as a combination of a smaller scene and a series of scene commands in separate packets. In this case the marker bit of the packet containing the last scene command is to be set. This is in line with the normal use of the marker bit in video coding and enables efficient buffering. + +**Timestamp:** 32 bits - The timestamp indicates the rendering instant of the unit(s). + +The usage of the remaining RTP header fields follows the rules of [15]. + +#### 7.3.2.3 Common Packet Header + +The RTP payload comprises of a common header and has the following format: + +![Figure 7-3: COMMON PAYLOAD HEADER diagram showing the structure of the header with fields like R, A, T, and CTR.](9a159e2112eac7be06bdb97e84a0c49a_img.jpg) + +``` + ++-----+ +|0|1|2|3|4|5|6|7| ++---+---+---+---+---+---+---+---+ +|R|A| T | CTR | ++-----+ + +``` + +Figure 7-3: COMMON PAYLOAD HEADER diagram showing the structure of the header with fields like R, A, T, and CTR. + +Figure 7-3: COMMON PAYLOAD HEADER + +**R:** 1 bit + +The R bit is reserved, shall be set to 0, and shall be ignored by the receiver. + +**A:** 1 bit + +When set to one, the A bit indicates that the packet contains one or more random access points (in DIMS, DIMS Units with is-RAP set), or the first fragment of a random access point. + +**T:** 3 bits + +The payload type as defined in table 2; Reserved values shall not be used, and packets with reserved values of the type field shall be discarded and not processed. + +**Table 2: Summary of RTP Payload Types and Descriptions** + +| Type | Description | +|--------|---------------------------------| +| 0 | Aggregation packet | +| 1 | Fragmentation start Packet | +| 2 | Fragmentation continuing Packet | +| 3 | Fragmentation end Packet | +| 4 to 7 | Reserved | + +##### **CTR: 3 bits** + +The CTR is used to detect the loss of one or more high-priority units as documented in subclause 7.3.1. + +#### 7.3.2.4 Aggregation Packet + +These packets contain one or more complete units with the same timestamp. The common header values are: + +- Type: 0. +- A (RAP): as needed. + +The RTP payload is presented below. + +![](1c29dadab94c3fa552d270434db09c81_img.jpg) + +``` + + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Header (Type=0) | first Unit length | : + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + : first unit : + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ...OPTIONAL RTP padding | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +**Figure 7-4: Aggregation Packet payload format** + +The units are placed in the RTP payload, in sequence, possibly following by RTP padding. Each unit is preceded by a two-byte length in network (big-endian) byte order. The length is the length of the following unit (both header and body), not including the length field itself. + +#### 7.3.2.5 Fragmentation Packets + +Frames that exceed the networks maximum transmission unit (MTU) size should be fragmented before transmission. By fragmenting at the RTP level one does not need to rely on lower layer fragmentation, e.g. IP. + +The payload format defines fragmentation of units into two or more RTP packets. + +**NOTE:** Fragmentation on the RTP level should however be seen as a solution only when fragmentation on the DIMS level is not possible. Fragmentation can be performed by splitting, for example, a scene into a scene and a number of scene updates. In this way packets can be created that are smaller than MTUs and can be decoded individually, which gives better error resilience when packets are lost. + +The common header values are as follows. + +- Type: 1, 2, or 3. +- A (RAP): as needed in first fragment, and 0 in all other fragments. +- CTR: shall be identical in all the packets of a fragmented unit; increments after the last fragment depending on the priority of the unit. + +Fragments consist of an integer number of consecutive octets of a unit. Fragments of a unit shall be sent as a group and in consecutive order with respect to RTP sequence numbers. The first fragment shall be marked as type 1 and the last fragment shall be marked as type 3. Other fragments shall be marked as type 2. + +The unit is complete with header. The header is not repeated in fragments. There is no length field. + +![Figure 7-5: FRAGMENTATION PACKET FORMATS. The diagram shows two packet structures. The top structure is for type=1, showing a 4-byte header (0-3), a 'Header' field (bytes 4-7), a 'Partial Unit payload' (bytes 8-15), and '...OPTIONAL RTP padding' (bytes 16-19). The bottom structure is for type=2/3, showing a 4-byte header (0-3), a 'Hdr (type=2/3)' field (bytes 4-7), a 'Partial Unit payload' (bytes 8-15), and '...OPTIONAL RTP padding' (bytes 16-19).](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 7-5: FRAGMENTATION PACKET FORMATS. The diagram shows two packet structures. The top structure is for type=1, showing a 4-byte header (0-3), a 'Header' field (bytes 4-7), a 'Partial Unit payload' (bytes 8-15), and '...OPTIONAL RTP padding' (bytes 16-19). The bottom structure is for type=2/3, showing a 4-byte header (0-3), a 'Hdr (type=2/3)' field (bytes 4-7), a 'Partial Unit payload' (bytes 8-15), and '...OPTIONAL RTP padding' (bytes 16-19). + +Figure 7-5: FRAGMENTATION PACKET FORMATS + +### 7.3.3 SDP Parameters + +The Session Description specifies the clock rate, version profile and level. The fields in the Session Description Protocol (SDP) are defined as follows: + +- The media name in the "m=" line of SDP shall be video. +- The encoding name in the "a=rtpmap" line of SDP shall be richmedia+xml. + +The clock rate in the "a=rtpmap" line is not specified in the present document. The resolution of the clock should be sufficient for the desired synchronization accuracy and for measuring packet arrival jitter. The clock rate of the referenced continuous media files within the presentation needs to be considered. For example, if the presentation contains referenced video which is to be synchronized with the presentation, the clock rate should be no less than 90,000. + +The MIME parameters in subclause 11.1, when present, shall be included in the "a=fmtp" line of SDP. These parameters are expressed as a MIME media type string, in the form of a semicolon separated list of parameter=value pairs. + +An example of a media-level description in SDP format is shown below. + +``` +m=video 12345 RTP/AVP 96 +a=rtpmap:96 richmedia+xml/100000 +a=fmtp:96 Version-profile=10; Level=10; +``` + +### 7.3.4 Separate Redundant Stream + +Redundant DIMS Units may be carried in RTP in a separate stream. If there is more than one main stream, the redundant stream(s) shall be linked to the matching main stream(s) that they repair, using the media identification and group attributes as specified in [22]. For any RTP packet A in a redundant stream and any RTP packet B in the corresponding main stream, when the redundant DIMS units in packet A and the main DIMS units in packet B have the same media time, packet A and packet B shall have the same RTP timestamp value. + +Redundant streams have contains-redundant set to "redundant data only". The stream they are connected to shall have contains-redundant set to "main data only". + +A terminal may perform tune-in etc. using the 'redundant' stream by: + +- a) looking for a random access point in the redundant stream, or main stream; + +- b) if the random access point was in the redundant stream, processing DIMS Units from the redundant stream until the redundant-exit indication; +- c) continuing processing at the temporally next DIMS Unit in the main stream. + +# --- 8 Profiles and Levels + +## 8.1 Profiles + +### 8.1.1 Introduction + +A profile indicator in a stream indicates which features (also known as tools) are required to be supported on a terminal. + +Profile indications are unsigned 8-bit integers. Only one profile is defined by the present document; other profiles may be defined in future. + +When opening a bitstream, a terminal should check that the profile indicator is recognized by seeing whether the bitstream profile is equal to a profile supported in the terminal. Profile indicators can only be compared for equality; a terminal presented with an unknown profile indicator should assume it does not support the features required by the indicated profile. + +The value 255 for the profile indication is defined to mean "no profile specified" and shall be used to mark bitstreams which are not known to conform to the requirements of any other profile. + +The behaviour of a terminal when presented with a stream with an unrecognizable profile, or profile 255, is unspecified. + +### 8.1.2 Mobile profile + +**Mobile Profile** : Profile Indicator Value 10. + +Support for the following media types is also required in profile 10: + +- Shall support the Still Image media format as specified in 7.5 of [7] and the Bitmap Graphics format as specified in 7.6 of [7]. +- Shall support Speech as specified in 7.2 of [7] and Audio as specified in 7.3 of [7]. +- Shall support Video as specified in 7.4 of [7]. +- Shall support the 3GP file format as specified in 7.10 of [7]. + +As required in the SVG specification, SVG fonts shall be supported. The lack of hinting in SVG fonts means that small text which is anti-aliased may become unreadable. This problem is even more evident when text is rotated or animated. Recommendation: SVG fonts should be used with care. + +The Open Font Format [4] should be supported at advanced simple text profile, level 2, with the following constraints: if Open Type fonts are supported, the DIMS client shall support downloadable OpenType fonts with TrueType outlines, TrueType hinting shall be supported for improved text readability, and advanced typographic features may be supported. + +NOTE 1: When OpenType fonts are supported, download of them may be initiated using the font-face-uri element from [1]. + +Device-native fonts and fonts identified by generic family names may be used. + +Uncompressed XML shall be supported. XML compressed with GZIP [11] shall be supported. + +NOTE 2: Sub-systems may also require support for other media types (e.g. video) or codecs within those types (e.g. H.263) when support for DIMS is required. + +## 8.2 Levels + +### 8.2.1 Introduction + +Level indicators provide a way to measure the degree of support required in a terminal to render a given scene or scene stream satisfactorily. + +Level indications are unsigned 8-bit integers. + +A level sets limits for quantitative parameters (e.g. a rotation angle) or measures (e.g. the overall bit-rate) of the format. + +Level indicators are within the context of the profile indicator. All levels for a given profile use the same axes of measurement, but different profiles may use different axes; for example, one profile may have limits on rotation angle, and another profile leave that parameter un-limited. Within a given profile, the levels "nest", that is, if $X < Y$ , then the requirements for a level with indicator X are lower than or equal to the requirements for a level with indicator Y, for the same profile. + +The value 255 for the level indication is defined in all profiles to mean "no level specified" and shall be used in bitstreams not known to respect the limits of any known level for the indicated profile, and for all bitstreams labelled as "no profile specified". The behaviour of a terminal when presented with a stream with level 255 is unspecified. + +DIMS Implementations will be able to use the level indicator to optimize the rendering of the content. + +### 8.2.2 Level Axes + +Levels may be measured on the following axes, or other parameters or measurable aspects of the stream. These values represent the maximum that the content may use, or expect., and hence the minimum the terminal must supply. For example, content must be usable if rendered into a minimum size pixel buffer and updated at the minimum pixel update rate. + +- 1) Bitrate of the scene stream(s), including the initial scene, embedded graphics, audio, video, etc. (That is, the minimum bit-rate channel over which the scene could be delivered in a real-time fashion). +- 2) Bitrate of the stream(s) having the DIMS mediatype. (That is, excluding streams with other mediatypes, such as video, audio, etc.). +- 3) The maximum number of simultaneously playing video streams. +- 4) The maximum number of simultaneously playing audio streams. +- 5) The maximum number of simultaneously active DIMS Scenes. +- 6) The minimum output pixel buffer size needed for the scene to be usable. This is specified in nominally square pixels, as a width and height value (therefore 160x120 is wider than it is tall). +- 7) The maximum number of path segments over the entire scene. +- 8) The maximum total number of bytes in text content in text elements in the entire scene. +- 9) The maximum size of a single dash array. +- 10) The number of gradient stops in any single gradient. + +The following limits should be respected by the content and should be supported by the terminal. However, these memory and CPU limits are for a reasonable scene with reasonable attribute values, in a scene which is un-scripted or has a reasonable amount of scripting. Use of large attribute values (e.g. long paths or strings), complex nodes, or scripts that are demanding in memory or processor usage will have an impact on performance and decodability. + +- 1) The size of the DOM tree as measured by the number of nodes in the tree; the number of attributes, or the size of their values, is not calculated. +- 2) The expected minimum refresh rate of the pixel output buffer (e.g. as a result of animations, updates, or script actions) for the scene to be usable. This is expressed as a frame rate. + +- 3) The maximum number of animations that run concurrently. + +The following subclauses define the available levels. + +### 8.2.3 Mobile Profile Level 10 definition + +This level contains the following restrictions: + +- Only one instantiation of a DIMS Scene is allowed. +- Only one Video instantiation along with a DIMS Scene is allowed. + +On the Video Element, the attribute **transformBehavior** shall be restricted to values "pinned | pinned90 | pinned180 | pinned270", and the attribute **overlay** shall be restricted to values "top". + +The following limits also apply: + +**Mobile Profile Level Limits** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| | Level 10 | +| 1 Scene bitrate (includes the static media embedded within the scene/commands and referenced media payloads) | 200 kbit/sec | +| 2 DIMS aggregate bit-rate (excludes media payloads) | 40 kbit/sec | +| 3 Simultaneous video playing | 1 | +| 4 Simultaneous audio playing | 1 | +| 5 Simultaneous active DIMS scenes | 1 | +| 6 Minimum pixel output buffer size | 160 wide by 120 tall | +| 7 Maximum path segments across all paths | 3000 | +| 8 Maximum text content size (this refers to the number of characters and does not include the glyph) | 10k bytes | +| 9 Maximum dash array size | 16 | +| 10 Maximum number of gradient stops | 32 | +| 1 Maximum recommended DOM tree size | 800 nodes | +| 2 Minimum recommended screen refresh rate

Note: Depending on the DOM tree size, the recommended screen refresh rate value may not be feasible and a lower screen refresh rate might be expected. | 10 frames/sec | +| 3 Maximum simultaneous animations | 20 | + +### 8.2.4 Void + +# 9 Content usage guidelines + +The SVGT1.2 guidelines defined in ANNEX L of PSS release 7 [7] apply here. + +NOTE: The recommendation of L2.8 should be read as including downloadable fonts: "Usage of device or system fonts, or downloaded OpenType fonts, is recommended. SVG fonts should be used with care." + +Content creators should take into account the DIMS levels definitions in section 8.2. Those level definitions do not completely assure interoperability in terms of memory or processing requirements. Content authors should be aware that CPU-intensive scripts, for example, may adversely impact update rates, or that heavily recursive scripts, or variables that hold large values, may adversely affect memory usage and hence player performance. + +# --- 10 Security and Content Protection Considerations + +DIMS does not define a security framework. DIMS relies instead on the security frameworks already defined for the mechanisms DIMS uses (e.g. for ECMAScript Mobile Profile [2]), and the frameworks provided by the platforms on which DIMS runs. + +When content requests fullscreen video and especially fullscreen scenes, it is possible for the content to mimic the normal look of the device (the 'desktop' of a computer screen, for example) and persuade the user to enter potentially secure or private information into a presentation while thinking that they are interacting with the local system. This is sometimes called "phishing". Care should be taken to handle content that uses fullscreen requests, such that the user is always aware of when DIMS content is filling the screen (e.g. restrict DIMS to "window-only" mode, or in some other way make it clear to the user that the screen's content is rendered under DIMS control). + +DIMS content can embed scripts. Care should be taken to limit, to the presentation in which they occur, the access that these scripts have. For example, it would normally be inappropriate for these scripts to have access to the local file system outside the scope of presentation. A further possible countermeasure would be to restrict DIMS reception to certified servers only, and to signed contents only, without any means for the user to disable this strict checking in order to mitigate social engineering attacks. + +Authors of web-sites that embed DIMS content, when the scripts in the DIMS content are not under the control of the web site - for example, if the DIMS content is fetched from another site, or uploaded to the web-site by users -- should exercise caution. The embedded scripts may have access to the content of, and interaction of, the web site that embeds them, even though they were not authored by, or provided from, that web site. + +Finally, it is recommended a secure client software update service be provided, so that it is possible to close security holes in the DIMS clients when they are detected + +# --- 11 Registered Types + +## 11.1 RTP Payload format MIME Type + +**Type name:** video + +**Subtype name:** richmedia+xml + +### **Required parameters:** + +- **Version-profile** - A value between 0 and 255 specifying the profile of DIMS used, for example the value indicating Mobile Profile. +- **Level** - A value between 0 and 255 specifying the minimum DIMS level needed to be able to display the scene. + +### **Optional parameters:** + +- **stream-type** - takes the value "primary" for primary streams (in which every random access point is a scene), and the value "secondary" for secondary streams. Secondary streams are not normally playable by themselves, outside the context of the scene(s) they are designed to update. The default value is "primary". +- **contains-redundant** - takes the value "main" if the stream contains only DIMS Units with is-redundant set to 0, the value "redundant" if the stream contains only DIMS Units with is-redundant set to 1, and takes the value + +"main+redundant" if both occur. Note that streams containing only redundant units must be linked to the matching stream carrying main DIMS Units (see subclause 7.3.4). The default value is "main+redundant". + +- `text-encoding` - is a string enclosed in double-quotes with possible values taken the XML specification for character encoding in entities (e.g. subclause 4.3.3 of [25]). It describes the text encoding after the content has been decompressed (e.g. after deflating). The default value is "UTF-8" [9]. This field is only applicable if the content is transmitted as (possibly encoded) text. +- `content-script-types` - is a string enclosed in double-quotes that identifies the scripting languages used. It is formatted as a comma-separated list of MIME types [18] from the IANA registry, such as "application/ecmascript" (see [13]). It shall provide a complete listing of the script types that the terminal must support in order to process the stream. If this attribute is not present, the set of required script types is unknown. If this attribute contains the empty string, then the stream does not require any script processing. +- `content-coding` - this field provides the identification of the compression scheme. It is a string specifying the encoding (compression) format of the content. It is defined in the same way as the content-coding header in HTTP (subclause 3.5 of [12]). The default value is the empty string. +- `useFullRequestHost` takes the value "0" or "1"; the definition of this parameter is in subclause 5.5.2. The default value is "1". +- `pathComponents` takes a value between "0" and "15"; the definition of this parameter is in subclause 5.5.2. The default value is "15". + +### Encoding considerations: + +- This media type is currently only defined for transport via RTP. + +### Security considerations: + +- RTP packets using the payload format defined in the present document are subject to the security considerations discussed in the RTP specification [15] and any applicable RTP profile, e.g., AVP [21]. + +### Interoperability considerations: + +- None. + +### Published specification: + +- 3GPP TS 26.142. + +### Applications that use this media type: + +- DIMS Streaming applications. + +### Additional information: + +- Magic number(s): None. +- File extension(s): None. +- Macintosh file type code(s): None. + +### Person and email address to contact for further information: + +- Clinton Priddle. +- [clinton.priddle@ericsson.com](mailto:clinton.priddle@ericsson.com). +- Multimedia Technologies, Ericsson. + +### Intended usage: + +- COMMON. + +### Restrictions on usage: + +- None. + +#### **Author:** + +- 3GPP SA4 WG. + +### **Change controller:** + +- 3GPP TSG SA. + +## 11.2 'Codecs' Parameter for 3GP files + +When DIMS content is supplied in 3GP files which are identified by MIME type, the 'codecs' parameter defined in [14] may be used to indicate that DIMS content is present. The codecs parameter takes the sample entry name as defined above (that is, 'dims'). + +# --- Annex A (normative): Conformance Criteria + +DIMS constructs scenes which are possibly updated over time. Conformant terminals shall support the delivery of the scenes and updates in formats specified in the 'compression' subclause above, and in the transport environments specified in the 'transport' subclause. + +For the initial scene, a DIMS Scene can be extracted from the transport, and de-compressed if necessary, yielding an XML document. This XML is referred to here as the "initial DIMS document". Similarly, after all updates for a given instant have been applied to the scene tree, there is logically an XML document that is equivalent to the scene DOM tree; these are called "subsequent DIMS documents" here. + +Initial and subsequent DIMS documents shall conform to all of: + +- the conformance requirements in Appendix D of [1]; with the following exceptions: + - The conformance criteria in the SVG specification regarding codecs do not apply for the DIMS media type. + - Clause D.4 is not in scope for DIMS. + - Clause D.7 is not in scope for DIMS. +- the conformance requirements of the LASER Commands and LASER scene extensions as specified in [27] and [28] +- the limitations of the profile and level indications under which they are delivered. + +Conformance of the DIMS extensions is for further study. \ No newline at end of file diff --git a/marked/Rel-18/26_series/26143/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/26_series/26143/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de052cd2a75659a9194a36a7b6d432649189723b --- /dev/null +++ b/marked/Rel-18/26_series/26143/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5649c907e6961280e4fd1190deebfaf2964f535952ba47b6730c75affae0c2aa +size 47466 diff --git a/marked/Rel-18/26_series/26143/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/26_series/26143/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74d150686ccb1d7865229851846e918855dac7e7 --- /dev/null +++ b/marked/Rel-18/26_series/26143/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b40126d4975510b01b6e8a1e18b1e169b359eb69116df88fe7535fc135e6294d +size 43449 diff --git a/marked/Rel-18/26_series/26143/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26143/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..795528ab9548ade9d316906ecd2c1675f00b8e4f --- /dev/null +++ b/marked/Rel-18/26_series/26143/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d988fd2118e12e0e96b2bad02088294218b7f990390dc18ea2fff5480bf21c0a +size 9588 diff --git a/marked/Rel-18/26_series/26143/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26143/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6619776e43bc6171c9830e205ee05e4fdff42be1 --- /dev/null +++ b/marked/Rel-18/26_series/26143/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dee1a0dca69317d74934664398b8a3df5b2365dcf22c36685c24b5a914abe719 +size 5735 diff --git a/marked/Rel-18/26_series/26143/raw.md b/marked/Rel-18/26_series/26143/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c496ee335a6d1c35af006fc10cc3f771d1362d35 --- /dev/null +++ b/marked/Rel-18/26_series/26143/raw.md @@ -0,0 +1,1067 @@ + + +# 3GPP TS 26.143 V18.2.1 (2025-04) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Messaging Media Profiles; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in small capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in small capital letters. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Overview and Context ..... | 9 | +| 4.1 Background and Assumptions..... | 9 | +| 4.2 System Description ..... | 10 | +| 4.3 MMBP Player Model ..... | 11 | +| 4.4 Generic MMBP Data Model ..... | 12 | +| 4.5 Media Capabilities and Profiles ..... | 12 | +| 5 MMBP Media Capabilities for different Media Types ..... | 13 | +| 5.1 Introduction ..... | 13 | +| 5.2 Multipart MMBPs and Container Formats..... | 15 | +| 5.2.1 Player and Decoding capabilities ..... | 15 | +| 5.2.2 MMBP Content Generator capabilities ..... | 16 | +| 5.3 Text..... | 16 | +| 5.3.1 Player and Decoding capabilities ..... | 16 | +| 5.3.2 MMBP Content Generator capabilities ..... | 17 | +| 5.4 Image..... | 17 | +| 5.4.1 Player and Decoding capabilities ..... | 17 | +| 5.4.2 MMBP Content Generator capabilities ..... | 17 | +| 5.5 Speech and Audio..... | 18 | +| 5.5.1 Player and Decoding capabilities ..... | 18 | +| 5.5.2 MMBP Content Generator capabilities ..... | 19 | +| 5.6 Video ..... | 21 | +| 5.6.1 Player and Decoding capabilities ..... | 21 | +| 5.6.2 MMBP Content Generator capabilities ..... | 22 | +| 5.7 Timed Text and Subtitles ..... | 24 | +| 5.7.1 Player and Decoding capabilities ..... | 24 | +| 5.7.2 MMBP Content Generator capabilities ..... | 24 | +| 5.8 3D scenes and assets ..... | 24 | +| 5.9 Presentation format ..... | 25 | +| 6 Messaging Media Profiles..... | 25 | +| 6.1 Overview ..... | 25 | +| 6.2 Baseline MMBP Player Profile ..... | 25 | +| 6.2.1 Overview ..... | 25 | +| 6.2.2 Container Format..... | 26 | +| 6.2.3 Media Types ..... | 26 | +| 6.3 Baseline MMBP Generator Profile ..... | 27 | +| 6.3.1 Overview ..... | 27 | +| 6.3.2 Container Format..... | 28 | +| 6.3.3 Media Types ..... | 28 | +| 6.3.4 Packaging Requirements and Recommendations..... | 28 | +| Annex A (informative): Registration Information ..... | 29 | +| A.1 3GPP Registered URIs ..... | 29 | + +| | | | +|-------------------------------|----------------------------------------|-----------| +| Annex B (informative): | Examples ..... | 29 | +| B.1 | MMBP message with a 3D asset..... | 29 | +| Annex C (informative): | Transcoding Guidelines ..... | 30 | +| C.1 | Transcoding 3D scenes and assets ..... | 30 | +| Annex D (informative): | Change history..... | 31 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document +- might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +- is** (or any other verb in the indicative mood) indicates a statement of fact +- is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document specifies the media types, formats, codecs capabilities and profiles for the messaging applications used over the 5G System. The scope of the present document extends to codecs for speech, audio, video, still images, bitmap graphics, 3D scenes and assets, and other media in general, as well as scene description. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + - [2] Khronos glTF 2.0, [glTF™ 2.0 Specification \(khronos.org\)](#) + - [3] ISO/IEC 23090-14 AMD 2, Information technology — Coded representation of immersive media — Part 14: Scene description — Amendment 2: Support for haptics, augmented reality, avatars, Interactivity, MPEG-I audio, and lighting + - [4] 3GPP TS 26.511: "5G Media Streaming (5GMS); Profiles, Codecs and Formats". + - [5] 3GPP TS 26.117: "5G Media Streaming (5GMS); Speech and audio profiles". + - [6] IETF Draft draft-ietf-mimi-content-01: "More Instant Messaging Interoperability (MIMI) message content", Rohan Mahy + - [7] 3GPP TS 22.140: "Multimedia Messaging Service (MMS); Stage 1". + - [8] Open Mobile alliance, "MMS Architecture" OMA-AD-MMS-V1\_3-20110913-A. + - [9] Open Mobile alliance, "Multimedia Messaging Service Encapsulation Protocol" OMA-TS-MMS\_ENC-V1\_3-20110913-A. + - [10] GSMA "RCS Universal Profile Service Definition Document", Version 2.6, 19 December 2022. + - [11] GSMA PRD RCC.07 version 13.0 - "Rich Communication Suite - Advanced Communications Services and Client Specification" 19 December 2022. + - [12] IETF RFC 2046, "Multipart Internet Mail Extensions (MIME) Part Two: Media Types". + - [13] ISO/IEC 14496-12: "Information technology - Coding of audio-visual objects -Part 12: ISO base media file format". + - [14] ISO/IEC 23000-24:2023 Preliminary Draft of: Information technology — Multimedia application format (MPEG-A) — Part 24: Messaging Media Application Format (MeMAF) ". +- NOTE: A preliminary draft of this standard is available as MDS23345\_W03\_N1082 here: +[https://www.mpeg.org/wp-content/uploads/mpeg\\_meetings/144\\_Hannover/w23345.zip](https://www.mpeg.org/wp-content/uploads/mpeg_meetings/144_Hannover/w23345.zip) +- [15] 3GPP 23.140: "Multimedia Messaging Service (MMS); Functional Description; Stage 2". + - [16] ITU-T Recommendation T.81: "Information technology; Digital compression and coding of continuous-tone still images: Requirements and guidelines". + +- [17] "JPEG File Interchange Format", Version 1.02, September 1, 1992. +- [18] "Exchangeable image file format for digital still cameras: EXIF 2.2", Specification by the Japan Electronics and Information Technology Industries Association (JEITA), April 2002, URL: +- [19] CompuServe Incorporated: "GIF Graphics Interchange Format: A Standard defining a mechanism for the storage and transmission of raster-based graphics information", Columbus, OH, USA, 1987. +- [20] Compuserve Incorporated, Columbus, Ohio (1990): "Graphics Interchange Format (Version 89a)". +- [21] IETF RFC 2083: "PNG (Portable Networks Graphics) Specification version 1.0 ", T. Boutell, et. al., March 1997. +- [22] ISO/IEC 23000-22:2019 Information technology — Multimedia application format (MPEG-A) — Part 22: Multi-image application format (MIAF) +- [23] IETF RFC 2045, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", November 1996 +- [24] ISO/IEC 23008-12:2019 Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 12: Image File Format +- [25] ITU-T Recommendation H.265 (02/2018): "High efficiency video coding". +- [26] 3GPP TS 26.244: "Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)" +- [27] 3GPP TS 26.245: "Transparent end-to-end packet switched streaming service (PSS); Timed text format" +- [28] ISO/IEC 14496-30: "Information technology - Coding of audio-visual objects - Part 30: Timed text and other visual overlays in ISO base media file format". +- [29] IETF RFC 2387, "The MIME Multipart/Related Content-type" +- [30] IETF RFC 6381, "The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types" +- [31] 3GPP TS 26.307, "Presentation Layer for 3GPP Services" +- [32] 3GPP TS 26.140, "Multimedia Messaging Service (MMS); Media formats and codecs" +- [33] IETF RFC 2077, "The Model Primary Content Type for Multipurpose Internet Mail Extensions" +- [34] 3GPP TS 26.119, "Media Capabilities for Augmented Reality" + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Messaging Media Profile:** a set of UE capability requirements associated to a media-centric messaging service scenario. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|-----------------------------------------| +| AAC | Advanced Audio Coding | +| AMR | Adaptive MultiRate | +| API | Application Programming Interface | +| AVC | Advanced Video Coding | +| DCT | Discrete Cosine Transform | +| gITF | Graphics Library Transmission Format | +| IANA | Internet Assigned Numbers Authority | +| MIME | Multipurpose Internet Mail Extensions | +| MIMI | More Instant Messaging Interoperability | +| MMBP | multimedia messaging body part | +| MMS | Multimedia Messaging Service | +| OMA | Open Mobile Alliance | +| PDU | Protocol Data Unit | +| RCS | Rich Communication Services | + +# --- 4 Overview and Context + +## 4.1 Background and Assumptions + +Messaging services typically define a message container. Such a container typically carries one or more body parts with the actual message content (for example, an emoji used in a reaction, a plain text or rich text message or reply, a link, or an inline image, or richer media types). + +An important feature of messages are body parts that include media content. Different media content exists, such as simple and rich text, still images, graphics, speech, audio, video, 3D scenes and many other media types. + +This specification is not defining a container format, but it addresses the usability of 3GPP defined media types and formats into messages as part of a message body within message containers. Examples for message containers are OMA MMS PDUs [7][8][9][15], IETF MIMI message containers [6] or GSMA RCS [10][11]. + +The focus of this specification is the definition of parts of *message body* that carry multimedia content, referred to as *multimedia messaging body part* (MMBP). This specification does not generally define how the body part is encoded: existing functionalities, for example the ones defined in OMA MMS PDUs [7][8][9][15] or MIMI message containers [6] may be used for this purpose. However, this specification provides the definition of an MMBP using the ISO Base Media File format [13] to provide features for mixing multiple sub-parts into a single body part. The specification relies on ISO/IEC 23000-24 [14]. + +NOTE: This specification does not define advanced MMBP features using the ISO Base Media File format [13] such that multiple sub-parts may be mixed into a single body part. This feature is for further study, possibly in alignment with ISO/IEC 23000-24 [14]. + +However, this specification is not restricted to be used with a fully specified Messaging Service, it may as well be used as part of third-party messaging services as message body, or more specifically as MMBP. It may also serve to support content interoperability across different messaging services. + +The term *media type* is used as short to refer to the IANA media type, subtype, and parameters as defined in IETF RFC 2046 [12] and provides defined properties of a *content*. For example, it may tell if the content is video or audio, it + +provides the encapsulation format, and it may provide parameters such as the codec in use. This specification defines, or at least assigns to each defined MMBP a media type, in order to uniquely identify the media type. + +In order to use MMBPs as defined in this specification as part of a message container format, it is expected that the message container format supports the following functionalities: + +- 1) It can carry an octet string representing the *content* of the MMBP +- 2) It can signal the *media type* of the content. +- 3) The content and media type of the content is not restricted but allows to include formats that are not defined in the core container format. + +In addition, a container format may support one or more of the following functionalities in alignment of definitions in IETF MIMI [6] and IETF RFC 2046 [12]: + +- the body can be *multi-part*, i.e, it can have multiple, possibly nested parts, referred to as *sub-parts*, with one of the following properties and structures + - *mixed*: there are multiple media types associated with the same message which need to be rendered together, for example a rich-text message with an inline image. The receiver is expected to process as many of the nested parts at this level as possible. + - *alternative*: there are multiple media types associated with the same message and the receiver can choose an appropriate one based on its own policies using the media type or possibly other parameters (e.g. a language) of each part. + - *related*: there are multiple media types associated with the same message and all the nested body parts at this level are part of a single entity that are processed jointly, possibly by providing a root object for initial processing. If the receiver does not understand even one of the nested parts at this level, the receiver is not expected to process any of them. + - *nested*: there are multiple media types associated with the same message, and one or several of the media types are representing a single, mixed, alternative or related structure. +- it may have body parts that reference external content via URI that will be processed automatically. It includes a media type and may optionally include the size of the data, an expiration timestamp other parameters. The content may be rendered with the other parts of the message, or a be downloaded or rendered separately. +- it may have body parts for which the content is encrypted. + +Note that based on the above, the MMBP may be the entire part of a message body, or it may be a sub-part. + +## 4.2 System Description + +Based on the background and assumptions in clause 4.1, Figure 4.2-1 provides an example system for a messaging services and highlights scope of this specification, namely the definition of a *multimedia messaging body part* (MMBP) and the associated metadata. + +![Figure 4.2-1: Example system for Messaging multimedia message exchange. The diagram shows three main components: Messaging Service Sender, Container Message, and Messaging Service Client. The Sender is connected to an MMBP generator via the MMBP-GEN-API. The generator produces an MMBP which is included in or referenced by the Container Message. The Container Message is sent to the Client, with its metadata (MMBP) being passed to the Client. The Client is connected to an MMBP player via the MMBP-PLAY-API. The player processes the MMBP.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +graph TD + subgraph Sender [Messaging Service Sender] + MMBP_GEN_API((MMBP-GEN-API)) + MMBP_GEN_API --- MMBP_Generator[Multimedia Message Body Part (MMBP) generator] + end + subgraph Container [Container Message] + MMBP_Cylinder[(Multimedia Message Body Part (MMBP))]] + end + subgraph Client [Messaging Service Client] + MMBP_PLAY_API((MMBP-PLAY-API)) + MMBP_PLAY_API --- MMBP_Player[Multimedia Message Body Part (MMBP) Player] + end + Sender -- "Includes or references" --> Container + Container -- "Metadata MMBP" --> Client + MMBP_Generator --> MMBP_Cylinder + MMBP_Cylinder --> MMBP_Player + +``` + +Figure 4.2-1: Example system for Messaging multimedia message exchange. The diagram shows three main components: Messaging Service Sender, Container Message, and Messaging Service Client. The Sender is connected to an MMBP generator via the MMBP-GEN-API. The generator produces an MMBP which is included in or referenced by the Container Message. The Container Message is sent to the Client, with its metadata (MMBP) being passed to the Client. The Client is connected to an MMBP player via the MMBP-PLAY-API. The player processes the MMBP. + +**Figure 4.2-1 Example system for Messaging multimedia message exchange** + +A Messaging Service Sender instructs a MMBP generator to generate an MMBP, for example using an API. This for example allows to define configurations on codecs, size, experiences or other attributes of the MMBP. The details of such an API are outside the scope of this specification. The sender adds the MMBP to a Container Message (either included as a body part or by reference), together with MMBP metadata parameters that provide information about the MMBP. Metadata includes, but is not limited to: + +- The media type of the MMBP, including subtypes and parameters for codecs, etc. +- The size of the MMBP +- Accessibility or language information about the MMBP +- processing requirements or recommendations of the MMBP + +The client of the messaging service receives the container message that includes the above information. The client communicates with a MMBP player its capabilities whether the MMBP can be played back, and if multiple alternatives are present, which of those are to be selected. Then the messaging service client instructs the MMBP player to playback the MMBP as part of the messaging service, based on the processing requirements and instructions. Playback may be combined with additional instructions for a player, including play, pause, seek, etc. + +## 4.3 MMBP Player Model + +The design of the formats defined in this document is based on the player model as shown in Figure 4.3-2. The figure illustrates the logical components of a conceptual MMBP Player model. In this figure, the MMBP parser receives the MMBP, and playback instructions. The Messaging Service Client may use metadata provided in a container message for playback selection. Such metadata may for example include codec capability information, language codes, accessibility information and other information for the selection of alternative parts in the MMBP. + +The client then provides the sub-parts for processing and decoding to the related sub-part processors, and controls those for playback. The rendered message output may be handed back to the Messaging Service client for inband rendering or may be rendered directly. + +![Figure 4.3-1 MMBP Player Model diagram showing the interaction between a Messaging Service Client and an MMBP Player.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the MMBP Player Model. At the top, a dashed box labeled 'Messaging Service Client' receives 'Metadata MMBP' from the left. It has three connections to the 'MMBP-PLAY-API' (represented by an oval): a solid line labeled 'MMBP' pointing down to the player, a solid line labeled 'Capabilities Instructions' pointing down to the player, and a dashed line labeled 'Rendering Output' pointing up from the player. Below the API is the 'MMBP Player' (represented by a large grey box). Inside the player, a dashed box labeled 'MMBP Server' on the left sends 'Sub-parts' to a box labeled 'MMBP Access and Parser'. This box then sends 'Sub-Parts' to a stack of boxes labeled 'Sub-Part Processors and Decoders', which in turn send output to a box labeled 'Message Rendering'. + +Figure 4.3-1 MMBP Player Model diagram showing the interaction between a Messaging Service Client and an MMBP Player. + +**Figure 4.3-1 MMBP Player Model** + +Beyond the MMBP formats, this specification also defines capabilities of 3GPP-based MMBP players. + +## 4.4 Generic MMBP Data Model + +Based on the description in clause 4.1, an MMBP can be the full body or part of the body of a container message. + +An MMBP itself is identified by a media type. + +The MMBP may be a single content with a media type. + +The MMBP may include multiple additional MMBPs. The following multi-part MMBPs are defined: + +- *mixed MMBP*: multiple MMBPs are associated with the mixed MMBP that shall be rendered together. Each MMBP is identified by a media type. The receiver is expected to process *as many as possible* of the included MMBPs based on its capabilities. +- *parallel MMBP*: multiple MMBPs are associated with the parallel MMBP that shall be rendered together. Each MMBP is identified by a media type. Real-time MMBPs included in a parallel MMBP share the same MMBP presentation timeline, which has a value of zero at the earliest media sample intended for presentation. If presented jointly, they shall be presented using this common MMBP presentation timeline. +- *alternative MMBP*: multiple MMBPs are associated with the alternative MMBP. Each MMBP is identified by a media type. The receiver is expected to process *exactly one* based on its capabilities. +- *related MMBP*: multiple objects are associated with the process MMBP. One object is identified as a *root MMBP*. The root MMBP is identified by a media type. The root MMBP is processed and identifies if any, several or all of the remaining objects are used as well. Hence, all other objects are typically also identified by media types, and a URL that links the objects being part of the related MMBP. The processor of the root MMBP also controls the selection, presentation and timing of the other objects. + +MMBPs are a recursive structure. Hence, a receiver shall expect that multi-part MMBPs contain other multi-part MMBPs. + +## 4.5 Media Capabilities and Profiles + +This specification defines media capabilities for both, MMBP generators as well as MMBP players in clause 5. The media capabilities provide requirements for content generation as well as playback instructions, respectively. + +This specification also defines profiles for content generators and players. Profiles are a collection of media capability requirements and recommendations as defined in clause 6. + +External specifications may reference capabilities defined in this specification. + +Preferably, external specifications should reference full media profiles. + +# 5 MMBP Media Capabilities for different Media Types + +## 5.1 Introduction + +In order to guarantee a minimum support and compatibility between messaging capable terminals, MMBP Generators and MMBP Players in UEs supporting specific media content with associated media types. + +The clause defines multimedia messaging body parts (MMBPs) for different media types as well as the associated media types. + +According to the introduction in clause 4, MMBPs defined in this clause, + +- may be used as full body parts or sub-parts in message bodies. +- may either be a single binary octet string, or they may consist of multiple parts. If the latter, the conceptual relationship introduced in clause 4.4 is defined that is mapped to container formats defined in clause 5.2. + +Media Types and related capabilities defined in this specification for playback are provided in Table 5.1-1. + +**Table 5.1-1 Media Types and Capabilities defined in TS 26.143 for playback and decoding** + +| Media Type in the present TS | Capabilities defined in this specification | Clause | Media Type signalling example | +|----------------------------------------------|--------------------------------------------|--------|-------------------------------------| +| Multipart MMBPs and Container Formats | 26143_CONTAINER_RFC2046_SINGLE | 5.2.1 | Media type of subtype | +| | 26143_CONTAINER_RFC2046_MIXED | | multipart/mixed | +| | 26143_CONTAINER_RFC2046_ALTERNATIVE | | multipart/alternative | +| | 26143_CONTAINER_RFC2046_PARALLEL | | multipart/parallel | +| | 26143_CONTAINER_RFC2387_RELATED | | multipart/related | +| | 26143_CONTAINER_MP4_3GP9 | | video/mp4, profile="3gp9" | +| Text | 26143_TEXT_PLAIN | 5.3.1 | text/plain | +| Speech | 26143_AUDIO_IVAS | 5.5.1 | audio/mp4 | +| | 26143_AUDIO_EVS | | | +| | 26143_AUDIO_AMR-WB | | | +| | 26143_AUDIO_AMR | | | +| Audio | 26143_AUDIO_IVAS | 5.5.1 | audio/mp4 | +| | 26143_AUDIO_XHE-AAC | | | +| | 26143_AUDIO_EAAC+ | | | +| Image | 26143_IMG_JPEG | 5.4.1 | image/jpeg | +| | 26143_IMG_HEIC | | image/heic,
profile="heic, MiHB" | +| | 26143_IMG_GIF | | imageTypes="hvc1.1.2.L153.B0" | + +| | | | | +|-----------------------------|---------------------------|-------|---------------------------------------------------------------| +| | 26143_IMG_PNG | | image/gif
image/png | +| Video | 26143_VIDEO_AVC-HD | 5.6.1 | video/mp4, profile="3gp9"
codecs="avc1.640028" | +| | 26143_VIDEO_AVC-FullHD | | video/mp4, profile="3gp9"
codecs="avc1.640029" | +| | 26143_VIDEO_HEVC-HD | | video/mp4, profile="3gp9"
codecs="hvc1.1.2.L93.B0" | +| | 26143_VIDEO_HEVC-FullHD | | video/mp4, profile="3gp9"
codecs="hvc1.1.2.L123.B0" | +| | 26143_VIDEO_HEVC-UHD | | video/mp4, profile="3gp9"
codecs="hvc1.1.2.L153.B0" | +| Subtitles and Text | 26143_TT_3GPP | 5.7.1 | text/mp4, profile="3gp9"
codecs="tx3g" | +| | 26143_TT_IMSC11 | | application/mp4,
profile="3gp9"
codecs="stpp.ttml.im2t" | +| 3d scenes and assets | 26143_SCENE_GLTf20 | 5.8 | model/gltf+json | +| | 26143_SCENE_GLTf20_AR | | | +| | 26143_SCENE_GLTf20_GLB | | model/gltf-binary | +| | 26143_SCENE_GLTf20_GLB_AR | | | +| Presentation format | 26143_PRESENTATION_HTML5 | 5.9 | text/html | + +Media Types and related capabilities defined in this specification for content generation are provided in Table 5.1-2. + +**Table 5.1-2 Media Types and Capabilities defined in TS 26.143 for generation** + +| Media Type in the present TS | Capabilities defined in this specification | Clause | Media Type signalling example | +|----------------------------------------------|--------------------------------------------|--------|-------------------------------| +| Multipart MMBPs and Container Formats | 26143_CONTAINER_RFC2046_SINGLE_GEN | 5.2.2 | Media type of subtype | +| | 26143_CONTAINER_RFC2046_MIXED_GEN | | multipart/mixed | +| | 26143_CONTAINER_RFC2046_ALTERNATIVE_GEN | | multipart/alternative | +| | 26143_CONTAINER_RFC2046_PARALLEL_GEN | | multipart/parallel | +| | 26143_CONTAINER_MP4_3GP9_GEN | | video/mp4, profile="3gp9" | +| Text | 26143_TEXT_ENC_PLAIN | 5.3.1 | text/plain | +| Speech | 26143_AUDIO_ENC_IVAS | 5.5.1 | audio/mp4 | +| | 26143_AUDIO_ENC_EVS | | | + +| | | | | +|--------------|-----------------------------------------------|-------|--------------------------------------------------------| +| | 26143_AUDIO_ENC_AMR-WB
26143_AUDIO_ENC_AMR | | | +| Audio | 26143_AUDIO_ENC_IVAS | 5.5.1 | audio/mp4 | +| | 26143_AUDIO_ENC_XHE-AAC | | | +| | 26143_AUDIO_ENC_EAAC+ | | | +| Image | 26143_IMG_ENC_JPEG | 5.4.1 | image/jpeg | +| Video | 26143_VIDEO_ENC_AVC-HD | 5.6.2 | video/mp4, profile="3gp9"
codecs="avc1.640028" | +| | 26143_VIDEO_ENC_AVC-FullHD | | video/mp4, profile="3gp9"
codecs="avc1.640029" | +| | 26143_VIDEO_ENC_HEVC-HD | | video/mp4, profile="3gp9"
codecs="hvc1.1.2.L93.B0" | +| | 26143_VIDEO_ENC_HEVC-FullHD | | video/mp4, profile="3gp9"
codecs="hvc1.1.2.L123.B0" | +| | 26143_VIDEO_ENC_HEVC-UHD | | video/mp4, profile="3gp9"
codecs="hvc1.1.2.L153.B0" | +| Text | 26143_TT_ENC_3GPP | 5.7.2 | text/mp4, profile="3gp9"
codecs="tx3g" | + +## 5.2 Multipart MMBPs and Container Formats + +### 5.2.1 Player and Decoding capabilities + +The capability 26143\_CONTAINER\_RFC2046\_SINGLE is defined as the capability of processing a body part of with a top-level media type as defined in IETF RFC 2046 [12] with one of the following top-level media types: text, audio, image, video, model, multipart, and application. + +The capability 26143\_CONTAINER\_RFC2046\_MIXED is defined as the capability of processing a body part of subtype multipart/mixed as defined in IETF RFC 2046 [12] further restricted by the processing defined in clause 4.4 for *mixed MMBPs*. In the context of this specification, the media type for multipart media types with this capability 26143\_CONTAINER\_RFC2046\_MIXED shall be signalled with multipart/mixed as defined in IETF RFC 2046 [12]. + +The capability 26143\_CONTAINER\_RFC2046\_ALTERNATIVE is defined as the capability of processing a body part of subtype multipart/alternative as defined in IETF RFC 2046 [12] further restricted by the processing defined in clause 4.4 for *alternative MMBPs*. In the context of this specification, the media type for multipart media types with this capability 26143\_CONTAINER\_RFC2046\_ALTERNATIVE shall be signalled with multipart/alternative as defined in IETF RFC 2046 [12]. + +The capability 26143\_CONTAINER\_RFC2046\_PARALLEL is defined as the capability of processing a body part of subtype multipart/parallel as defined in IETF RFC 2046 [12] further restricted by the processing defined in clause 4.4 for *parallel MMBPs*. In the context of this specification, the media type for multipart media types with this capability 26143\_CONTAINER\_RFC2046\_PARALLEL shall be signalled with multipart/parallel as defined in IETF RFC 2046 [12]. + +The capability 26143\_CONTAINER\_RFC2387\_RELATED is defined as the capability of processing a body part of subtype multipart/related as defined in IETF RFC 2387 [29] further restricted by the processing defined in clause 4.4 for *related MMBPs*. In the context of this specification, the media type for multipart media types with this + +capability 26143\_CONTAINER\_RFC2387\_RELATED shall be signalled with multipart/parallel as defined in IETF RFC 2387 [29] with the *root MMBP* either signalled with the start parameter, or if not present, the *root MMBP* being the first body part within the Multipart/Related body and the type of the *root MMBP* signalled with the type parameter. + +The capability 26143\_CONTAINER\_MP4\_3GP9 is defined as the capability of processing a body part conforming to a 3GP file Rel-9 basic profile as defined in TS 26.244 [26] identified by the brand '3gp9' and further restricted by the processing defined in clause 4.4 for *parallel MMBPs*. In the context of this specification, the media type for multipart media types with this capability 26143\_CONTAINER\_MP4\_3GP9 shall be signalled using a media type as defined IETF RFC 6381 [30] using for example `video/mp4, profile="3gp9"` or an equivalently compatible media type and shall use the `codecs` parameter to further provide information about the contained MMBPs. + +NOTE: This specification does not define mechanisms for referencing external content. This aspect is for further study. + +### 5.2.2 MMBP Content Generator capabilities + +The capability 26143\_CONTAINER\_RFC2046\_SINGLE\_GEN is defined as the capability of generating a body part of with a top-level media type as defined in IETF RFC 2046 [12] with one of the following top-level media types: text, audio, image, video, and multipart that can be processed by a MMBP processor with the capability 26143\_CONTAINER\_RFC2046\_SINGLE. + +The capability 26143\_CONTAINER\_RFC2046\_MIXED\_GEN is defined as the capability of generating a body part of subtype multipart/mixed as defined in IETF RFC 2046 [12] with media type signalling with multipart/mixed as defined in IETF RFC 2046 [12] that can be processed by a MMBP processor with the capability 26143\_CONTAINER\_RFC2046\_MIXED. + +The capability 26143\_CONTAINER\_RFC2046\_ALTERNATIVE\_GEN is defined as the capability of generating a body part of subtype multipart/alternative as defined in IETF RFC 2046 [12] with media type signalling with multipart/alternative as defined in IETF RFC 2046 [12] that can be processed by a MMBP processor with the capability 26143\_CONTAINER\_RFC2046\_ALTERNATIVE. + +The capability 26143\_CONTAINER\_RFC2046\_PARALLEL\_GEN is defined as the capability of generating a body part of subtype multipart/parallel as defined in IETF RFC 2046 [12] with media type signalling with multipart/parallel as defined in IETF RFC 2046 [12] that can be processed by a MMBP processor with the capability 26143\_CONTAINER\_RFC2046\_PARALLEL. + +The capability 26143\_CONTAINER\_MP4\_3GP9\_GEN is defined as the capability of generating a body part conforming to a 3GP file Rel-9 basic profile as defined in TS 26.244 [26] identified by the brand '3gp9' using a media type as defined IETF RFC 6381 [30], for example `video/mp4, profile="3gp9"` or an equivalently compatible media type and using the `codecs` parameter to further provide information about the contained MMBPs. + +## 5.3 Text + +### 5.3.1 Player and Decoding capabilities + +The capability 26143\_TEXT\_PLAIN is defined as the capability of decoding and rendering plain text with any character encoding (charset) that contains a subset of the logical characters in Unicode [2] (e.g. US-ASCII [3], ISO-8859-1 [4], UTF-8 [5], Shift\_JIS, etc.). In the context of this specification, the media type for text with this capability 26143\_TEXT\_PLAIN shall be signalled with `text/plain` as defined in IETF RFC 2046 [12]. However, the decoding and rendering capability 26143\_TEXT\_PLAIN includes that unrecognised subtypes of "text" shall be treated as subtype "plain" as long as the MIME implementation knows how to handle the charset. + +Interoperability with SMS/MMS text type is according to [15]. + +### 5.3.2 MMBP Content Generator capabilities + +The capability 26143\_TEXT\_ENC\_PLAIN for a content generator is defined as the combination of the following capabilities: + +- the capability to generate plain text with any character encoding (charset) that contains a subset of the logical characters in Unicode [2], such that the file can be played back by a player with the capability 26143\_TEXT\_PLAIN, +- the provisioning of media type signalling with the MMBP using text/plain as defined in IETF RFC 2046 [12]. + +## 5.4 Image + +### 5.4.1 Player and Decoding capabilities + +The capability 26143\_IMG\_JPEG is defined as the capability of decoding and rendering images according to, ISO/IEC JPEG [8] together + +- with JFIF [16] and the following two modes: + - baseline DCT, non-differential, Huffman coding, as defined in table B.1, symbol 'SOF0' in [17]; + - progressive DCT, non-differential, Huffman coding, as defined in table B.1, symbol 'SOF2' [17].- with EXIF compressed image file format, as defined in [18] and the baseline DCT mode. + +In the context of this specification, the media type for images with this capability 26143\_IMG\_JPEG shall be signalled with image/jpeg as defined in IETF RFC 2046 [12]. + +The capability 26143\_IMG\_HEIC is defined as the capability of decoding and rendering images conforming to + +- the 'heic' brand as defined in ISO/IEC 23008-12 [24], +- the 'MiHB' brand as defined in ISO/IEC 23000-22:2019 [22], and +- the contained elementary bitstream conforming to H.265 (HEVC) Main Profile, Main Tier, Level 5.1[25] bitstreams have general\_progressive\_source\_flag equal to 1, general\_interlaced\_source\_flag equal to 0, general\_non\_packed\_constraint\_flag equal to 1, and general\_frame\_only\_constraint\_flag equal to 1. + +In the context of this specification, the media type for images with this capability 26143\_IMG\_HEIC shall be signalled with image/heic, profile="heic,MiHB" itemTypes="hvc1.1.2.L153.B0" or an equivalently compatible media type as defined in [22]. + +The capability 26143\_IMG\_GIF is defined as the capability of decoding and rendering bitmap graphics conforming either to GIF87a [19] or to GIF89a, [20]. In the context of this specification, the media type for images with this capability 26143\_IMG\_GIF shall be signalled with image/gif as defined in IETF RFC 2046 [12]. + +The capability 26143\_IMG\_PNG is defined as the capability of decoding and rendering bitmap graphics conforming to PNG [21]. In the context of this specification, the media type for images with this capability 26143\_IMG\_GIF shall be signalled with image/png. + +### 5.4.2 MMBP Content Generator capabilities + +The capability 26143\_IMG\_ENC\_JPEG for a content generator is defined as the combination of the following capabilities: + +- the capability to generate an image according to ISO/IEC JPEG [8] that can be played by a player conforming to 26143\_IMG\_JPEG as defined in clause 5.4.1, i.e. restricted by either +- using JFIF [16] and one of the following two modes: + +- baseline DCT, non-differential, Huffman coding, as defined in table B.1, symbol 'SOF0' in [17], or +- progressive DCT, non-differential, Huffman coding, as defined in table B.1, symbol 'SOF2' [17]. +- using EXIF compressed image file format as defined in [18] and the baseline DCT mode. +- the provisioning of media type signalling with the MMBP using `image/jpeg` as defined in IETF RFC 2046 [12]. + +## 5.5 Speech and Audio + +### 5.5.1 Player and Decoding capabilities + +The capability `26143_AUDIO_IVAS` is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **IVAS** decoding capabilities as defined in clause 5.2 of TS 26.117 [5] and the receiver requirements in clause 6.3.5.2 of TS 26.117 [5], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry '`sivs`' as defined in TS 26.244 [26], +- is contained in a 3GP file that conforms to the `26143_CONTAINER_MP4_3GP9` capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability `26143_AUDIO_IVAS` shall be signalled with `audio/mp4, profiles="3gp9" codecs="sivs"` or an equivalently compatible media type. + +The capability `26143_AUDIO_EVS` is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **EVS** decoding capabilities as defined in clause 5.2 of TS 26.117 [5] and the receiver requirements in clause 6.2.4.2 of TS 26.117 [5], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry '`sevs`' as defined in TS 26.244 [26], +- is contained in a 3GP file that conforms to the `26143_CONTAINER_MP4_3GP9` capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability `26143_AUDIO_EVS` shall be signalled with `audio/mp4, profiles="3gp9" codecs="sevs"` or an equivalently compatible media type. + +The capability `26143_AUDIO_AMR-WB` is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **AMR-WB** decoding capabilities as defined in clause 5.2 of TS 26.117 [5] and the receiver requirements in clause 6.2.3.2 of TS 26.117 [5], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry '`sawb`' as defined in TS 26.244 [26], +- is contained in a 3GP file that conforms to the `26143_CONTAINER_MP4_3GP9` capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability `26143_AUDIO_EVS` shall be signalled with `audio/mp4, profiles="3gp9" codecs="sawb"` or an equivalently compatible media type. + +The capability `26143_AUDIO_AMR` is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **AMR** decoding capabilities as defined in clause 5.2 of TS 26.117 [5] and the receiver requirements in clause 6.2.2.2 of TS 26.117 [5], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry '`samr`' as defined in TS 26.244 [26], + +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_AUDIO\_EVS shall be signalled with `audio/mp4, profiles="3gp9" codecs="samr"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_XHE-AAC is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **xHE-AAC stereo** decoding capabilities as defined in clause 5.2 of TS 26.117 [5] and the receiver requirements in clause 6.4.2.2 of TS 26.117 [5], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry `'mp4a.40.42'`, +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_AUDIO\_XHE-AAC shall be signalled with `audio/mp4, profiles="3gp9" codecs="mp4a.40.42"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_EAAC+ is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **eAAC+** decoding capabilities as defined in clause 5.2 of TS 26.117 [5] and the receiver requirements in clause 6.3.2.2 of TS 26.117 [5], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry `'mp4a.40.29'`, +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_AUDIO\_EAAC+ shall be signalled with `audio/mp4, profiles="3gp9" codecs="mp4a.40.29"` or an equivalently compatible media type. + +### 5.5.2 MMBP Content Generator capabilities + +The capability 26143\_AUDIO\_ENC\_IVAS for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from an audio signal in real-time, such that the file can be played back by a player with the capability 26143\_AUDIO\_IVAS, +- the *IVAS* encoding capabilities as defined in clause 5.3 of TS 26.117 [5] and the sender requirements in clause 6.3.5.3 of TS 26.117 [5], +- the capability to generate an ISO BMFF track that conforms with the requirements of the sample entry `'sivs'` as defined in TS 26.244 [26]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `audio/mp4, profiles="3gp9" codecs="sivs"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_ENC\_EVS for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from an audio signal in real-time, such that the file can be played back by a player with the capability 26143\_AUDIO\_EVS, + +- the *EVS* encoding capabilities as defined in clause 5.3 of TS 26.117 [5] and the sender requirements in clause 6.2.4.3 of TS 26.117 [5], +- the capability to generate an ISO BMFF track that conforms with the requirements of the sample entry 'sevs' as defined in TS 26.244 [26]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `audio/mp4`, `profiles="3gp9"` `codecs="sevs"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_ENC\_AMR-WB for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from an audio signal in real-time, such that the file can be played back by a player with the capability 26143\_AUDIO\_AMR-WB, +- the *AMR-WB* encoding capabilities as defined in clause 5.3 of TS 26.117 [5] and the sender requirements in clause 6.2.3.3 of TS 26.117 [5], +- the capability to generate an ISO BMFF track that conforms with the requirements of the sample entry 'sawb' as defined in TS 26.244 [26]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `audio/mp4`, `profiles="3gp9"` `codecs="sawb"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_ENC\_AMR for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from an audio signal in real-time, such that the file can be played back by a player with the capability 26143\_AUDIO\_AMR, +- the *AMR* encoding capabilities as defined in clause 5.3 of TS 26.117 [5] and the sender requirements in clause 6.2.2.3 of TS 26.117 [5], +- the capability to generate an ISO BMFF track that conforms with the requirements of the sample entry 'samr' as defined in TS 26.244 [26]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `audio/mp4`, `profiles="3gp9"` `codecs="samr"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_ENC\_XHE-AAC for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from an audio signal in real-time, such that the file can be played back by a player with the capability 26143\_AUDIO\_XHE-AAC, +- the *XHE-AAC stereo* encoding capabilities as defined in clause 5.3 of TS 26.117 [5] and the sender requirements in clause 6.4.2.3 of TS 26.117 [5], +- the capability to generate an ISO BMFF track that conforms with the requirements of the sample entry 'mp4a.40.42' as defined in TS 26.244 [26]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `audio/mp4`, `profiles="3gp9"` `codecs="mp4a.40.42"` or an equivalently compatible media type. + +The capability 26143\_AUDIO\_ENC\_EAAC+ for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from an audio signal in real-time, such that the file can be played back by a player with the capability 26143\_AUDIO\_EAAC+, +- the *eAAC+* encoding capabilities as defined in clause 5.3 of TS 26.117 [5] and the sender requirements in clause 6.3.2.3 of TS 26.117 [5], +- the capability to generate an ISO BMFF track that conforms with the requirements of the sample entry 'mp4a.40.29' as defined in TS 26.244 [26]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `audio/mp4, profiles="3gp9" codecs="mp4a.40.29"` or an equivalently compatible media type. + +## 5.6 Video + +### 5.6.1 Player and Decoding capabilities + +The capability 26143\_VIDEO\_AVC-HD is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **AVC-HD-Dec** decoding capabilities as defined in clause 4.2.1.1 of TS 26.511 [4], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry 'avc1' as defined in ISO/IEC 14496-15 [15], +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_VIDEO\_AVC-HD shall be signalled with `video/mp4, profile="3gp9" codecs="avc1.640028"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_AVC-FullHD is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **AVC-FullHD-Dec** decoding capabilities as defined in clause 4.2.1.1 of TS 26.511 [4], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry 'avc1' as defined in ISO/IEC 14496-15 [15], +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_VIDEO\_AVC-FullHD shall be signalled with `video/mp4, profile="3gp9" codecs="avc1.640029"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_HEVC-HD is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **HEVC-HD-Dec** decoding capabilities as defined in clause 4.2.2.1 of TS 26.511 [4], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry 'hvc1' as defined in ISO/IEC 14496-15 [15], + +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_VIDEO\_HEVC-HD shall be signalled with `video/mp4, profile="3gp9" codecs="hvc1.1.2.L93.B0"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_HEVC-FullHD is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **HEVC-FullHD-Dec** decoding capabilities as defined in clause 4.2.2.1 of TS 26.511 [4], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry 'hvc1' as defined in ISO/IEC 14496-15 [15], +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_VIDEO\_HEVC-FullHD shall be signalled with `video/mp4, profile="3gp9" codecs="hvc1.2.4.L123.B0"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_HEVC-UHD is defined as the capability of playing back (decoding and rendering) a file that + +- is decodable by a decoder capable of the **HEVC-UHD-Dec** decoding capabilities as defined in clause 4.2.2.1 of TS 26.511 [4], +- is encapsulated in an ISO BMFF Track [14] conforming with the requirements of the sample entry 'hvc1' as defined in ISO/IEC 14496-15 [15], +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_VIDEO\_HEVC-UHD shall be signalled with `video/mp4, profile="3gp9" codecs="hvc1.2.4.L153.B0"` or an equivalently compatible media type. + +NOTE: In the absence of knowledge of detailed capabilities, 16:9 and 9:16 image formats are preferably used. + +### 5.6.2 MMBP Content Generator capabilities + +The capability 26143\_VIDEO\_ENC\_AVC-HD for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from a video signal in real-time, such that the file can be played back by a player with the capability 26143\_VIDEO\_AVC-HD, +- the **AVC-HD-Enc** encoding capabilities as defined in clause 4.1.2.2 of TS 26.511 [4] to generate a bitstream from the video signal +- the capability to generate an ISO BMFF track from the bitstream that conforms with the requirements of the sample entry 'avc1' as defined in ISO/IEC 14496-15 [15]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `video/mp4, profile="3gp9" codecs="avc1.640028"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_ENC\_AVC-FullHD for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from a video signal in real-time, such that the file can be played back by a player with the capability 26143\_VIDEO\_AVC-FullHD, +- the **AVC-FullHD-Enc** encoding capabilities as defined in clause 4.1.2.2 of TS 26.511 [4] to generate a bitstream from the video signal +- the capability to generate an ISO BMFF track from the bitstream that conforms with the requirements of the sample entry 'avc1' as defined in ISO/IEC 14496-15 [15]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `video/mp4, profile="3gp9" codecs="avc1.640029"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_ENC\_HEVC-HD for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from a video signal in real-time, such that the file can be played back by a player with the capability 26143\_VIDEO\_HEVC-HD, +- the **HEVC-HD-Enc** encoding capabilities as defined in clause 4.2.2.2 of TS 26.511 [4] to generate a bitstream from the video signal +- the capability to generate an ISO BMFF track from the bitstream that conforms with the requirements of the sample entry 'hvc1' as defined in ISO/IEC 14496-15 [15]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `video/mp4, profile="3gp9" codecs="hvc1.1.2.L93.B0"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_ENC\_HEVC-FullHD for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from a video signal in real-time, such that the file can be played back by a player with the capability 26143\_VIDEO\_HEVC-FullHD, +- the **HEVC-FullHD-Enc** encoding capabilities as defined in clause 4.2.2.2 of TS 26.511 [4] to generate a bitstream from the video signal +- the capability to generate an ISO BMFF track from the bitstream that conforms with the requirements of the sample entry 'hvc1' as defined in ISO/IEC 14496-15 [15]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `video/mp4, profile="3gp9" codecs="hvc1.2.4.L123.B0"` or an equivalently compatible media type. + +The capability 26143\_VIDEO\_ENC\_HEVC-UHD for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from a video signal in real-time, such that the file can be played back by a player with the capability 26143\_VIDEO\_HEVC-UHD, +- the **HEVC-UHD-Enc** encoding capabilities as defined in clause 4.2.2.2 of TS 26.511 [4] to generate a bitstream from the video signal +- the capability to generate an ISO BMFF track from the bitstream that conforms with the requirements of the sample entry 'hvc1' as defined in ISO/IEC 14496-15 [15]. + +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `video/mp4`, `profile="3gp9"` `codecs="hvc1.2.4.L153.B0"` or an equivalently compatible media type. + +## 5.7 Timed Text and Subtitles + +### 5.7.1 Player and Decoding capabilities + +The capability 26143\_TT\_3GPP is defined as the capability of decoding and rendering a file that + +- includes a track conforming to the sample entry 'tx3g' as defined in TS 26.245 [27] and +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_TT\_3GPP shall be signalled with `text/mp4`, `profile="3gp9"` `codecs="tx3g"` or an equivalently compatible media type. + +The capability 26143\_TT\_IMSC11 is defined as the capability of decoding and rendering a file that + +- includes a track conforming to the sample entry 'stpp' as defined in ISO/IEC 14496-30 [28] and +- is contained in a 3GP file that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. + +In the context of this specification, the media type for files with this capability 26143\_TT\_IMSC11 shall be signalled with `application/mp4`, `profile="3gp9"` `codecs="stpp.ttml.im2t"` or an equivalently compatible media type. + +### 5.7.2 MMBP Content Generator capabilities + +The capability 26143\_ENC\_TT\_3GPP for a content generator is defined as the combination of the following capabilities: + +- the capability to generate a file from a timed text signal, such that the file can be played back by a player with the capability 26143\_TT\_3GPP, +- the capability to generate an ISO BMFF track from the bitstream track that conforms with the requirements of the sample entry 'tx3g' as defined in TS 26.245 [27]. +- the generation of a 3GP file from the ISO BMFF track that conforms to the 26143\_CONTAINER\_MP4\_3GP9 capability as defined in clause 5.2. +- the provisioning of media type signalling with the generated file using `video/mp4`, `profile="3gp9"` `codecs="tx3g"` or an equivalently compatible media type. + +## 5.8 3D scenes and assets + +The capability 26143\_SCENE\_GLTF20 is defined as the capability of rendering glTF 2.0 scenes as specified in [2] for which all components of the 3D scene are included as multiple parts in a *related MMBP* as defined in clause 4.4, for which the *root MMBP* is a glTF2.0 JSON document. + +The capability 26143\_SCENE\_GLTF20\_GLB is defined as the capability of rendering glTF 2.0 scenes as specified in [2] for which all components of the 3D scene are either + +- encapsulated in a GLB file, or +- included as multiple parts in a *related MMBP*, for which the *root MMBP* is a GLB file. + +The capability 26143\_SCENE\_GLT20\_AR is defined as the capability of 26143\_SCENE\_GLT20 with the addition, that the scene may include MPEG\_anchor extension, EXT\_lights\_image\_based and MPEG\_lights\_texture\_based extensions as defined in [3]. + +The capability 26143\_SCENE\_GLT20\_GLB\_AR is defined as the capability of 26143\_SCENE\_GLT20\_GLB with the addition, that the scene may include MPEG\_anchor extension, EXT\_lights\_image\_based and MPEG\_lights\_texture\_based extensions as defined in [3]. + +It is recommended that clients supporting such capabilities determine if the media can be safely processed prior to any processing and rendering. + +In the context of this specification, the media type for scenes with this capability 26143\_SCENE\_GLT20 and 26143\_SCENE\_GLT20\_AR shall be signalled with `model/gltf+json` as defined in [2]. + +In the context of this specification, the media type for scenes with this capability 26143\_SCENE\_GLT20\_GLB and 26143\_SCENE\_GLT20\_GLB\_AR shall be signalled with `model/gltf-binary` as defined in [2]. + +NOTE: Annex C provides guidelines on the transcoding of 3D scenes and assets in messages for legacy devices. + +## 5.9 Presentation format + +The capability 26143\_PRESENTATION\_HTML5 is defined as the capability of rendering HTML-5 content according to the profile defined TS 26.307 [31] with the following further restrictions: + +- all components of the 3D scene are included as multiple parts in a *related MMBP* as defined in clause 4.4, for which the *root MMBP* is an HTML-5 document. +- the functionalities as defined in TS 26.307 [31], clause 4, are further restricted to the Markup in clause 4.2 and Style in clause 4.3. + +NOTE: In order to address potential security risks, Scripting as defined in TS 26.307 [31], clause 4.4 is excluded from the capabilities. + +- the APIs as defined in TS 26.307 [31], clause 5, are further restricted to the Forms API and the Canvas API. +- the media types may be further restricted. + +NOTE: As this specification does not define mechanisms for referencing external content, any network APIs from TS 26.307 [31] are excluded. + +It is recommended that clients supporting such capabilities determine if the media can be safely processed prior to any processing and rendering. + +In the context of this specification, the media type for scenes with this capability 26143\_PRESENTATION\_HTML5 shall be signalled with `text/html` as defined in [2]. + +# --- 6 Messaging Media Profiles + +## 6.1 Overview + +This specification defines several messaging media profiles that apply for the player or the content generator. + +## 6.2 Baseline MMBP Player Profile + +### 6.2.1 Overview + +The baseline MMBP Player profile is aligned with TS 26.140 [32]. + +The container format is based on IETF RFC 2045 [23] as the format for the MMBPs. Offering of alternative content is the container is permitted. In addition, the profile permits to encapsulate encapsulation of real-time video into the 3GP file format using the baseline profile. The container does not support external bodies, i.e. the MMBP is expected to be delivered as a single message. For details on the container format requirements, refer to clause 6.2.2. + +The media types address basic text, audio/speech, images, video, text/subtitle, 3D scenes including AR as well as simple HTML-5 presentations. + +Content conforming to the baseline MMBP player may include media types that are not explicitly supported by the media capabilities as defined in clause 6.2.3. Receivers shall ignore non-recognized media types. However, based on the container requirements, ignoring media types may results in specific processing requirements, for example pick an alternative, or ignore the entire MMBP. + +Content generated to be compatible for playback on players for this profile as well as players expose their capabilities should use the URN identifier "urn:3GPP:26143:18:baseline-mmmp-player". + +### 6.2.2 Container Format + +The following capabilities for the container format as defined in clause 5.2.1 shall be supported: + +- 26143\_CONTAINER\_RFC2046\_SINGLE +- 26143\_CONTAINER\_RFC2046\_MIXED +- 26143\_CONTAINER\_RFC2046\_ALTERNATIVE +- 26143\_CONTAINER\_RFC2387\_RELATED +- 26143\_CONTAINER\_MP4\_3GP9 + +The following capabilities for the container format as defined in clause 5.2 should be supported: + +- 26143\_CONTAINER\_RFC2046\_PARALLEL + +In addition, multipart/parallel shall not be present in an MMBP on the same level if a 3GP file Rel-9 basic profile as defined in TS 26.244 [26] identified by the brand '3gp9' is present and contains more than one track. + +### 6.2.3 Media Types + +The capability 26143\_TEXT\_PLAIN as defined in clause 5.3 shall be supported. + +If still images are supported, + +- the 26143\_IMG\_JPEG capability as defined in clause 5.4.1 shall be supported, +- the 26143\_IMG\_HEIC capability as defined in clause 5.4.1 should be supported. + +If bitmap graphics are supported, + +- the 26143\_IMG\_GIF capability as defined in clause 5.4.1 should be supported. +- the 26143\_IMG\_PNG capability as defined in clause 5.4.1 should be supported. + +If the reception of audio or speech is supported, then the following applies: + +- the 26143\_AUDIO\_IVAS capability as defined in clause 5.5.1 should be supported. +- the 26143\_AUDIO\_EVS capability as defined in clause 5.5.1 shall be supported. +- the 26143\_AUDIO\_AMR-WB capability as defined in clause 5.5.1 shall be supported. +- the 26143\_AUDIO\_XHE-AAC capability as defined in clause 5.5.1 should be supported. +- the 26143\_AUDIO\_AMR capability as defined in clause 5.5.1 shall be supported. + +- the 26143\_AUDIO\_EAAC+ capability as defined in clause 5.5.1 shall be supported. + +If the reception of video is supported, then the following applies: + +- the 26143\_VIDEO\_AVC-HD capability as defined in clause 5.6.1 shall be supported. +- the 26143\_VIDEO\_HEVC-HD capability as defined in clause 5.6.1 should be supported. + +If the reception of HD-HDR video is supported, then the following applies: + +- the 26143\_VIDEO\_AVC-FullHD capability as defined in clause 5.6.1 shall be supported. +- the 26143\_VIDEO\_HEVC-FullHD capability as defined in clause 5.6.1 shall be supported. +- the 26143\_VIDEO\_HEVC-UHD capability as defined in clause 5.6.1 should be supported. + +If timed text is supported, + +- the 26143\_TT\_3GPP capability as defined in clause 5.7.1 shall be supported. +- the 26143\_TT\_IMSC11 capability as defined in clause 5.7.1 should be supported. + +If a processor for media type 'model' as defined in RFC2077 [33] is supported (i.e. a processor for 3D scenes and objects), then a processor for the media subtype 'model/gltf' should be supported. If a processor for the media subtype 'model/gltf' is supported, + +- the 26143\_SCENE\_GLTF20 capability and the 26143\_SCENE\_GLTF20\_GLB capability as defined in clause 5.8 shall be supported assuming either a single body part or a multipart/related body part as defined in clause 5.2. +- and if the device is a device type as defined in TS 26.119 [34], clause 10, the 26143\_SCENE\_GLTF20\_AR and the 26143\_SCENE\_GLTF20\_GLB\_AR capability as defined in clause 5.8 shall be supported assuming either a single body part or a multipart/related body part as defined in clause 5.2. + +If a processor for the media type text/html is supported, the 26143\_PRESENTATION\_HTML5 capability as defined in clause 5.9 should be supported assuming either a single body part or a multipart/related body part as defined in clause 5.2. The media formats shall be restricted to the capabilities defined in this clause. + +## 6.3 Baseline MMBP Generator Profile + +### 6.3.1 Overview + +The baseline MMBP Generator profile is aligned with TS 26.140 [32]. + +It primarily addresses the ability for users to generate content, for example on a mobile device. + +The container format is based on IETF RFC 2045 [23] as the format for the MMBPs. Offering of alternative content is the container is permitted. In addition, the profile permits to encapsulate encapsulation of real-time video into the 3GP file format using the baseline profile. The container does not support external bodies, i.e. the MMBP is expected to be delivered as a single message. For details on the container format requirements, refer to clause 6.3.2. + +The media types supported by this profile are basic text, audio/speech, images, video, and text. + +Content conforming to the baseline MMBP generator profile may include media types that are not explicitly supported by the media capabilities as defined in clause 6.3.3. Receivers are expected to ignore non-recognized media types. However, based on the container requirements, ignoring media types may results in specific processing requirements, for example pick an alternative, or ignore the entire MMBP. + +Additional packaging requirements and recommendations are provided in clause 6.3.4. + +Content generated to be compatible for this profile as well as generators expose their capabilities should use the URN identifier "urn:3GPP:26143:18:baseline-mmbp-generator". + +### 6.3.2 Container Format + +The following capabilities for the container format as defined in clause 5.2.2 shall be supported: + +- 26143\_CONTAINER\_RFC2046\_SINGLE\_GEN +- 26143\_CONTAINER\_RFC2046\_MIXED\_GEN +- 26143\_CONTAINER\_MP4\_3GP9\_GEN + +The following capabilities for the container format as defined in clause 5.2 should be supported: + +- 26143\_CONTAINER\_RFC2046\_PARALLEL\_GEN +- 26143\_CONTAINER\_RFC2046\_ALTERNATIVE\_GEN + +### 6.3.3 Media Types + +If the transmission of images is supported, then the following applies: + +- the 26143\_IMAGE\_ENC\_JPEG capability as defined in clause 5.4.2 shall be supported. + +If the transmission of speech is supported, then the following applies: + +- the 26143\_AUDIO\_ENC\_IVAS capability as defined in clause 5.5.2 should be supported. +- the 26143\_AUDIO\_ENC\_EVS capability as defined in clause 5.5.2 shall be supported. +- the 26143\_AUDIO\_ENC\_AMR-WB capability as defined in clause 5.5.2 should be supported. +- the 26143\_AUDIO\_ENC\_AMR capability as defined in clause 5.5.2 may be supported. + +If the transmission of audio is supported, then the following applies: + +- the 26143\_AUDIO\_ENC\_IVAS capability as defined in clause 5.5.2 should be supported. +- the 26143\_AUDIO\_ENC\_EAAC+ capability as defined in clause 5.5.2 shall be supported. +- the 26143\_AUDIO\_ENC\_XHE-AAC capability as defined in clause 5.5.2 should be supported. + +If the transmission of video is supported, then the following applies: + +- the 26143\_VIDEO\_ENC\_HEVC-FullHD capability as defined in clause 5.6.2 shall be supported. + +If the transmission of timed text is supported, then the following applies: + +- the 26143\_TT\_ENC\_3GPP capability as defined in clause 5.7.2 shall be supported. + +### 6.3.4 Packaging Requirements and Recommendations + +For content generated by this baseline generator, multipart/parallel shall not be present in an MMBP on the same level if a 3GP file Rel-9 basic profile as defined in TS 26.244 [26] identified by the brand '3gp9' is present and contains more than one track. + +NOTE: This avoids the necessity to playback multiple tracks included in a single file with tracks provided to the multipart MMBP in the parallel structure. + +When generating a speech message, the MMBP Generator shall at least include an EVS Content together with potential alternatives. + +When generating an Audio message, the MMBP Generator shall at least include an eAAC+ stereo Content together with potential alternatives. + +# Annex A (informative): Registration Information + +## A.1 3GPP Registered URIs + +The clause documents the registered URIs in this specification following the process in , + +Table A-1 lists all registered URN values as well as + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +**Table A-1: 3GPP Registered URNs** + +| URN | Description | Reference | Contact | Remarks | +|-----------------------------------------------|----------------------------------------------------|----------------------------|---------------------------------------------|---------| +| urn:3GPP:
26143:18:baseline-mmbp-player | Media Messaging Baseline
MMBP Player Profile | TS 26.143,
clause 6.2.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | +| urn:3GPP:
26143:18:baseline-mmbp-generator | Media Messaging Baseline
MMBP Generator Profile | TS 26.143,
clause 6.3.1 | Thomas Stockhammer
tsto@qti.qualcomm.com | none | + +# Annex B (informative): Examples + +## B.1 MMBP message with a 3D asset + +In this example we show an excerpt of a message that contains a 3D asset. The root entry is a glTF 2.0 file. The message has two additional parts: a binary file that contains the geometry of the 3D asset and an image that provides the texture of the 3D asset. + +``` +MIME-Version: 1.0 +Content-Type: multipart/related; boundary="=====" + +===== +Content-Type: model/gltf+json +Content-Disposition: attachment; filename="sofa.gltf" + +{ + "asset": { + "version": "2.0" + }, + "buffers": [ + { + "uri": "buffer.bin", + "byteLength": 1024 + } + ], + "images": [ + { + "uri": "texture.jpg" + } + ], +} +``` + +``` + +"scenes": [ + { + "nodes": [0] + } +], +"nodes": [ + { + "mesh": 0 + } +], +"meshes": [ + { + "primitives": [ + { + "attributes": { + "POSITION": 0 + }, + "indices": 1 + } + ] + } +], +"accessors": [ + { + "bufferView": 0, + "componentType": 5126, + "count": 24, + "type": "VEC3" + } +], +"bufferViews": [ + { + "buffer": 0, + "byteOffset": 0, + "byteLength": 288 + } +] +} + +===== +Content-Type: application/octet-stream +Content-Disposition: attachment; filename="buffer.bin" + +... binary data ... + +===== +Content-Type: image/jpeg +Content-Disposition: attachment; filename="texture.jpg" + +... binary data ... + +===== + +``` + +# Annex C (informative): Transcoding Guidelines + +## C.1 Transcoding 3D scenes and assets + +Transcoding may need to be performed to support UEs that lack the capabilities to render 3D scenes and assets as defined in clause 5.8. The transcoding operation for 3D scenes and assets is effectively a rendering operation, where the 3D scene or asset is rendered into an image, image sequence, or video. The Messaging Server (e.g. MMS Server/Relay) may select an appropriate pose or set of poses (e.g. along a pre-defined path) that it uses to render the 3D scene or asset. \ No newline at end of file diff --git a/marked/Rel-18/26_series/26173/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26173/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..601828ac08db53884f5d27298fb28d86818ed8bf --- /dev/null +++ b/marked/Rel-18/26_series/26173/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ece8c3f8ed5a80906a42a07f6100652b1a679fecdf4b99bd9055d926f889849 +size 7638 diff --git a/marked/Rel-18/26_series/26173/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26173/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8e7af6578c1801eea72fb1a21652ea7004d5b3b --- /dev/null +++ b/marked/Rel-18/26_series/26173/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c554aaba2ee21a503dcf9af9c4a4ade9f4f7ddcf301dea0560abaef79ac74d45 +size 5321 diff --git a/marked/Rel-18/26_series/26173/raw.md b/marked/Rel-18/26_series/26173/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b49da4d9e89b53e9d5d6d759a388ea9657d8d279 --- /dev/null +++ b/marked/Rel-18/26_series/26173/raw.md @@ -0,0 +1,778 @@ + + +# 3GPP TS 26.173 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; ANSI-C code for the Adaptive Multi-Rate - Wideband (AMR-WB) speech codec (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|-----------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 C code structure ..... | 6 | +| 4.1 Contents of the C source code..... | 6 | +| 4.2 Program execution..... | 6 | +| 4.3 Code hierarchy ..... | 6 | +| 4.5 Variables, constants and tables..... | 10 | +| 4.5.1 Description of constants used in the C-code ..... | 11 | +| 4.5.2 Description of fixed tables used in the C-code..... | 11 | +| 4.5.3 Static variables used in the C-code..... | 13 | +| 5 Homing procedure..... | 16 | +| 6 File formats ..... | 16 | +| 6.1 Speech file (encoder input / decoder output) ..... | 16 | +| 6.2 Mode control file (encoder input) ..... | 16 | +| 6.3 Parameter bitstream file (encoder output / decoder input) ..... | 17 | +| Default 3GPP format: ..... | 17 | +| ITU format (activated with command line parameter -itu) ..... | 18 | +| MIME/file storage format (activated with command line parameter -mime)..... | 18 | +| Annex A (informative): Change history..... | 19 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains an electronic copy of the ANSI-C code for the Adaptive Multi-Rate Wideband codec. The ANSI-C code is necessary for a bit exact implementation of the Adaptive Multi Rate Wideband speech transcoder (3GPP TS 26.190 [2]), Voice Activity Detection (3GPP TS 26.194 [6]), comfort noise (3GPP TS 26.192 [4]), source controlled rate operation (3GPP TS 26.193 [5]) and example solutions for substituting and muting of lost frames (3GPP TS 26.191 [3]). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 26.174: "AMR Wideband Speech Codec; Test sequences". +- [2] 3GPP TS 26.190: "AMR Wideband Speech Codec; Speech transcoding". +- [3] 3GPP TS 26.191: "AMR Wideband Speech Codec; Substitution and muting of lost frames". +- [4] 3GPP TS 26.192: "AMR Wideband Speech Codec; Comfort noise aspects". +- [5] 3GPP TS 26.193: "AMR Wideband Speech Codec; Source controlled rate operation". +- [6] 3GPP TS 26.194: "AMR Wideband Speech Codec; Voice Activity Detection". +- [7] RFC 3267 "A Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs", June 2002. + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document, can be found in 3GPP TS 26.190 [2], 3GPP TS 26.191 [3], 3GPP TS 26.192 [4], 3GPP TS 26.193 [5] and 3GPP TS 26.194 [6]. + +## 3.2 Abbreviations + +For the purpose of the present document, the following abbreviations apply: + +| | | +|--------|-----------------------------------------| +| AMR-WB | Adaptive Multi-Rate Wideband | +| ANSI | American National Standards Institute | +| ETS | European Telecommunication Standard | +| GSM | Global System for Mobile communications | +| I/O | Input/Output | +| RAM | Random Access Memory | +| ROM | Read Only Memory | + +# 4 C code structure + +This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the C code attached to this document. + +The C code has been verified on the following systems: + +- Sun Microsystems workstations and GNU gcc compiler +- HP workstations and cc compiler +- IBM PC compatible computers with Windows NT4 operating system and GNU gcc compiler. + +ANSI-C was selected as the programming language because portability was desirable. + +## 4.1 Contents of the C source code + +The C code distribution has all files in the root level. + +The distributed files with suffix "c" contain the source code and the files with suffix "h" are the header files. The ROM data is contained mostly in files with suffix "tab". + +The C code distribution also contains one speech coder installation verification data file, "spch\_dos.inp". The reference encoder output file is named "spch\_dos.cod", the reference decoder input file is named "spch\_dos.dec" and the reference decoder output file is named "spch\_dos.out". These four files are formatted such that they are correct for an IBM PC/AT compatible computer. The same files with reversed byte order of the 16 bit words are named "spch\_unx.inp", "spch\_unx.cod", "spch\_unx.dec" and "spch\_unx.out", respectively. + +Final verification is to be performed using the GSM Adaptive Multi-Rate Wideband test sequences described in 3GPP TS 26.174 [1]. + +Makefiles are provided for the platforms in which the C code has been verified (listed above). Once the software is installed, this directory will have a compiled version of *encoder* and *decoder* (the bit-exact C executables of the speech codec) and all the object files. + +## 4.2 Program execution + +The GSM Adaptive Multi-Rate Wideband codec is implemented in two programs: + +- (*encoder*) speech encoder; +- (*decoder*) speech decoder. + +The programs should be called like: + +- encoder [encoder options] ; +- decoder . + +The speech files contain 16-bit linear encoded PCM speech samples and the parameter files contain encoded speech data and some additional flags. + +The encoder and decoder options will be explained by running the applications without input arguments. See the file *readme.txt* for more information on how to run the *encoder* and *decoder* programs. + +## 4.3 Code hierarchy + +Tables 1 to 3 are call graphs that show the functions used in the speech codec, including the functions of VAD, DTX, and comfort noise generation. + +Each column represents a call level and each cell a function. The functions contain calls to the functions in rightwards neighbouring cells. The time order in the call graphs is from the top downwards as the processing of a frame advances. All standard C functions: printf(), fwrite(), etc. have been omitted. Also, no basic operations (add(), L\_add(), mac(), etc.) or double precision extended operations (e.g. L\_Extract()) appear in the graphs. The initialization of the static RAM (i.e. calling the \_init functions) is also omitted. + +The basic operations are not counted as extending the depth, therefore the deepest level in this software is level 6. + +The encoder call graph is broken down into two separate call graphs, Table 1 to 2. + +Table 1: Speech encoder call structure + +| | | | | +|-------|-----------------------|-----------------------|-----------------------| +| coder | Copy | | | +| | Decim_12k8 | Down_samp | Interpol (function) | +| | Set_zero | Copy | | +| | HP50_12k8 | | | +| | Scale_sig | | | +| | wb_vad | Filter_bank | Filter5 | +| | | | Filter3 | +| | | | Level calculation | +| | | vad_decision | llog2 | +| | | | Noise estimate update | +| | | | hangover addition | +| | | Estimate_Speech | update_cntrl | +| | tx_dtx_handler | | | +| | Parm_serial | | | +| | Autocorr | | | +| | Lag_window | | | +| | Levinson | | | +| | Az_isp | Chebps2 | | +| | Int_isp | Isp_Az | Get_isp_pol | +| | Isp_isf | | | +| | Gp_clip_test_isf | | | +| | Weight_a | | | +| | Residu | | | +| | Deemph2 | | | +| | LP_Decim2 | | | +| | Scale_mem_Hp_wsp | | | +| | Pitch_med_ol | Hp_wsp | | +| | | lsqrt_n | | +| | wb_vad_tone_detection | | | +| | Med_olag | median5 | | +| | dtx_buffer | Copy | | +| | dtx_enc | Find_frame_indices | | +| | | Aver_isf_history | | +| | | Qisf_ns | Sub_VQ | +| | | | Disf_ns | +| | | | Reorder_isf | +| | | Parm_serial | | +| | | Pow2 | | +| | | Random | | +| | | Dot_product12 | | +| | | lsqrt_n | | +| | Isf_isp | | | +| | Isp_Az | Get_isp_pol | | +| | Synthesis | Copy | | +| | | Syn_filt_32 | | +| | | Deemph_32 | | +| | | HP50_12k8 | | +| | | Random | | +| | | Scale_sig | | +| | | Dot_product12 | | +| | | lsqrt_n | | +| | | HP400_12k8 | | +| | | Weight_a | | +| | | Syn_filt | | +| | | Filt_6k_7k | | +| | Reset_encoder | Set_zero | | +| | | Init_gp_clip | | +| | | Init_Phase_dispersion | Set_zero | +| | Qpisf_2s_36b | VQ_stage1 | | +| | | Sub_VQ | | +| | | Dpisf_2s_36b | Reorder_isf | +| | Qpisf_2s_46b | VQ_stage1 | | +| | | Sub_VQ | | +| | | Dpisf_2s_46b | Reorder_isf | +| | Syn_filt | | | +| | Preemph2 | | | +| | Pitch_fr4 | Norm_Corr | Convolve | +| | | | lsqrt_n | +| | | Interpol_4 | | +| | Gp_clip | | | +| | Pred_lt4 | | | +| | Convolve | | | +| | G_pitch | Dot_product12 | | +| | Updt_tar | | | +| | Preemph | | | +| | Pit_shrp | | | +| | Cor_h_x | | | +| | ACELP_2t64_fx | Dot_product12 | | +| | | lsqrt_n | | +| | ACELP_4t64_fx | See Table 2 | | +| | Q_gain2 | Dot_product12 | | +| | | Pow2 | | +| | Gp_clip_test_gain_pit | | | +| | voice_factor | Dot_product12 | | + +Table 2: ACELP\_4t64\_fx call structure + +| | | | | +|---------------|---------------|--------------|--------------| +| ACELP_4t64_fx | Dot_product12 | | | +| | lsqrt_n | | | +| | cor_h_vec | | | +| | search_ixiy | | | +| | quant_1p_N1 | | | +| | quant_2p_2N1 | | | +| quant_3p_3N1 | quant_3p_3N1 | | | +| | quant_2p_2N1 | | | +| | quant_1p_N1 | | | +| | quant_4p_4N1 | Quant_2p_2N1 | | +| | quant_1p_N1 | | | +| quant_4p_4N | quant_3p_3N1 | Quant_2p_2N1 | | +| | quant_2p_2N1 | Quant_1p_N1 | | +| | quant_1p_N1 | | | +| | quant_4p_4N | | | +| quant_5p_5N | quant_3p_3N1 | Quant_2p_2N1 | | +| | quant_2p_2N1 | Quant_1p_N1 | | +| | quant_1p_N1 | | | +| quant_6p_6N_2 | quant_5p_5N | Quant_3p_3N1 | quant_2p_2N1 | +| | | quant_2p_2N1 | Quant_1p_N1 | +| | quant_1p_N1 | | | +| | quant_4p_4N | quant_4p_4N1 | quant_2p_2N1 | +| | | quant_1p_N1 | | +| | | quant_3p_3N1 | quant_2p_2N1 | +| | | quant_2p_2N1 | quant_1p_N1 | +| | quant_2p_2N1 | | | +| | quant_3p_3N1 | quant_2p_2N1 | | +| | | Quant_1p_N1 | | + +Table 3: Speech decoder call structure + +| | | | | | +|---------|-------------------------|-----------------------|-------------|------------| +| decoder | Rx_dtx_handler | | | | +| | Dtx_dec | Copy | | | +| | | Disf_ns | Reorder isf | | +| | | Serial_parm | | | +| | | Pow2 | | | +| | | Random | | | +| | | Dot_product12 | | | +| | | lsqrt_n | | | +| | Serial_parm | | | | +| | Isf_isp | | | | +| | Isp_Az | Get_isp_pol | | | +| | Copy | | | | +| | Synthesis | Copy | | | +| | | Syn_filt_32 | | | +| | | Deemph_32 | | | +| | | HP50_12k8 | | | +| | | Oversamp_16k | Copy | | +| | | | Up_samp | Interpol | +| | | Random | | | +| | | Scale_sig | | | +| | | Dot_product12 | | | +| | | lsqrt_n | | | +| | | HP400_12k8 | | | +| | | Isf_Extrapolation | Isf_isp | | +| | | Isp_Az | Get_isp_pol | | +| | | Weight_a | | | +| | | Syn_filt | | | +| | | Filt_6k_7k | Copy | | +| | | Filt_7k | Copy | | +| | Reset_decoder | Set_zero | | | +| | | Init_Phase_dispersion | Set_zero | | +| | Dpif_2s_36b | Reorder_isf | | | +| | Dpif_2s_46b | Reorder_isf | | | +| | Int_isp | Isp_Az | Get_isp_pol | | +| | Lagconc | insertion_sort | Insert | | +| | | Random | | | +| | Pred_It4 | | | | +| | Random | | | | +| | DEC_ACELP_2164_fx | | | | +| | DEC_ACELP_4164_fx | dec_1p_N1 | | | +| | | add_pulses | | | +| | | dec_2p_2N1 | | | +| | | dec_3p_3N1 | Dec_2p_2N1 | | +| | | | dec_1p_N1 | | +| | | dec_4p_4N | dec_4p_4N1 | dec_2p_2N1 | +| | | | dec_1p_N1 | | +| | | | Dec_3p_3N1 | Dec_2p_2N1 | +| | | | | Dec_1p_N1 | +| | | dec_5p_5N | Dec_2p_2N1 | | +| | | | dec_3p_3N1 | Dec_2p_2N1 | +| | | | | Dec_1p_N1 | +| | | dec_6p_6N_2 | Dec_2p_2N1 | | +| | | | Dec_5p_5N | dec_3p_3N1 | +| | | | | Dec_2p_2N1 | +| | | | | Dec_1p_N1 | +| | | | dec_1p_N1 | | +| | | | dec_4p_4N | dec_2p_2N1 | +| | | | | dec_1p_N1 | +| | | | Dec_3p_3N1 | Dec_2p_2N1 | +| | | | | Dec_1p_N1 | +| | | | Dec_2p_2N1 | | +| | | dec_2p_2N1 | | | +| | | dec_3p_3N1 | Dec_2p_2N1 | | +| | | | Dec_1p_N1 | | +| | Preemph | | | | +| | Pit_shrp | | | | +| | D_gain2 | Dot_product12 | | | +| | | lsqrt_n | | | +| | | Median5 | | | +| | | Pow2 | | | +| | Scale_sig | | | | +| | voice_factor | Dot_product12 | | | +| | Phase_dispersion | Set_zero | | | +| | Agc2 | lsqrt | lsqrt_n | | +| | Set_zero | | | | +| | Dtx_dec_activity_update | Copy | | | + +## 4.5 Variables, constants and tables + +The data types of variables and tables used in the fixed point implementation are signed integers in 2's complement representation, defined by: + +- **Word16** 16 bit variable; +- **Word32** 32 bit variable. + +### 4.5.1 Description of constants used in the C-code + +This subclause contains a listing of all global constants defined in cnst.h. + +**Table 5: Global constants** + +| Constant | Value | Description | +|-----------------|--------|----------------------------------------------------------| +| L_TOTAL | 384 | total size of speech buffer. | +| L_WINDOW | 384 | window size in LP analysis | +| L_NEXT | 64 | Look-ahead size | +| L_FRAME | 256 | frame size in 12.8 kHz | +| L_FRAME16k | 320 | frame size in 16 kHz | +| L_SUBFR | 64 | Subframe size in 12.8 kHz | +| L_SUBFR16k | 80 | Subframe size in 16 kHz | +| NB_SUBFR | 4 | Number of subframes | +| M16k | 20 | order of LP filter in high-band synthesis in 6.60 mode | +| M | 16 | order of LP filter | +| L_FILT16k | 15 | Delay of down-sampling filter in 16 kHz | +| L_FILT | 12 | Delay of down-sampling filter in 12.8 kHz | +| GP_CLIP | 15565 | Pitch gain clipping | +| PIT_SHARP | 27853 | pitch sharpening factor | +| PIT_MIN | 34 | minimum pitch lag (all modes) | +| PIT_FR2 | 128 | Minimum pitch lag with resolution $\frac{1}{2}$ | +| PIT_FR1_9b | 160 | Minimum pitch lag with resolution for 9 bit quantization | +| PIT_FR1_8b | 92 | Minimum pitch lag with resolution for 8 bit quantization | +| PIT_MAX | 231 | maximum pitch lag | +| L_INTERPOL | (16+1) | length of filter for interpolation | +| OPL_DECIM | 2 | Decimation in open-loop pitch analysis | +| PREEMPH_FAC | 22282 | preemphasis factor | +| GAMMA1 | 30147 | Weighting factor (numerator) | +| TILT_FAC | 22282 | tilt factor (denominator) | +| Q_MAX | 8 | scaling max for signal | +| RANDOM_INITSEED | 21845 | random init value | +| L_MEANBUF | 3 | Size of ISF buffer | +| ONE_PER_MEANBUF | 10923 | Inverse of L_MEANBUF | + +### 4.5.2 Description of fixed tables used in the C-code + +This section contains a listing of all fixed tables sorted by source file name and table name. All table data is declared as **Word16**. + +**Table 6: Fixed tables** + +| File | Table name | Length | Description | +|------------|----------------|--------|---------------------------------------------------------------| +| c4t64fx.c | tipos | 36 | Starting points of iterations | +| cod_main.c | HP_gain | 16 | High band gain table for 23.85 kbit/s mode | +| cod_main.c | interpol_frac | 4 | LPC interpolation coefficients | +| cod_main.c | isp_init | 16 | Isp tables for initialization | +| cod_main.c | isf_init | 16 | Isf tables for initialization | +| d_gain2.c | cdown_unusable | 7 | Attenuation factors for codebook gain in lost frames | +| d_gain2.c | cdown_usable | 7 | Attenuation factors for codebook gain in bad frames | +| d_gain2.c | pdown_unusable | 7 | Attenuation factors for adaptive codebook gain in lost frames | +| d_gain2.c | pdown_usable | 7 | Attenuation factors for adaptive codebook gain in bad frames | +| d_gain2.c | pred | 4 | Algebraic code book gain MA predictor coefficients | +| dec_main.c | HP_gain | 16 | High band gain table for 23.85 kbit/s mode | +| dec_main.c | interpol_frac | 4 | LPC interpolation coefficients | +| dec_main.c | isp_init | 16 | Isp tables for initialization | +| dec_main.c | isf_init | 16 | Isf tables for initialization | +| decim54.c | fir_down | 120 | Downsample FIR filter coefficients | + +| File | Table name | Length | Description | +|--------------|-----------------|--------|------------------------------------------------------------------------| +| decim54.c | fir_up | 120 | Upsample FIR filter coefficients | +| dtx.c | en_adjust | 9 | Energy scaling factor for each mode during comfort noise | +| grid100.tab | grid | 101 | Grid points of Chebyshev polynomials | +| ham_wind.tab | window | 384 | LP analysis window | +| hp400.c | a | 3 | HP filter coefficients (denominator) in higher band energy estimation | +| hp400.c | b | 3 | HP filter coefficients (numerator) in higher band energy estimation | +| hp50.c | a | 3 | HP filter coefficients (denominator) in pre-filtering | +| hp50.c | b | 3 | HP filter coefficients (numerator) in pre-filtering | +| hp6k.c | fir_6k_7k | 31 | Bandpass FIR filter coefficients for higher band generation | +| hp7k.c | fir_7k | 31 | Bandpass FIR filter coefficients for higher band in 23.85 kbit/s mode | +| hp_wsp.c | a | 3 | HP filter coefficients (denominator) in open-loop lag gain computation | +| hp_wsp.c | b | 3 | HP filter coefficients (numerator) in open-loop lag gain computation | +| isp_isf.tab | slope | 128 | Table to compute acos(x) in lsp_isf() | +| isp_isf.tab | table | 129 | Table to compute cos(x) in lsf_isp() | +| lag_wind.tab | lag_h | 16 | High part of the lag window table | +| lag_wind.tab | lag_l | 16 | Low part of the lag window table | +| lp_dec2.c | h_fir | 5 | HP FIR filter coefficients in open-loop lag search | +| math_op.c | table_isqrt | 49 | Table used in inverse square root computation | +| math_op.c | table_pow2 | 33 | Table used in power of two computation | +| p_med_ol.tab | corrweight | 199 | Weighting of the correlation function in open loop LTP search | +| ph_disp.c | ph_imp_low | 64 | Phase dispersion impulse response | +| ph_disp.c | ph_imp_mid | 64 | Phase dispersion impulse response | +| pitch_f4.c | inter4_1 | 32 | Interpolation filter coefficients | +| pred_lt4.c | inter4_2 | 128 | Interpolation filter coefficients | +| q_gain2.c | pred | 4 | Algebraic code book gain MA predictor coefficients | +| q_gain2.tab | t_qua_gain6b | 2*64 | Gain quantization table for 6-bit gain quantization | +| q_gain2.tab | t_qua_gain7b | 2*128 | Gain quantization table for 7-bit gain quantization | +| qisf_ns.tab | dico1_isf_noise | 2*64 | 1st ISF quantizer for comfort noise | +| qisf_ns.tab | dico2_isf_noise | 3*64 | 2nd ISF quantizer for comfort noise | +| qisf_ns.tab | dico3_isf_noise | 3*64 | 3rd ISF quantizer for comfort noise | +| qisf_ns.tab | dico4_isf_noise | 4*32 | 4th ISF quantizer for comfort noise | +| qisf_ns.tab | dico5_isf_noise | 4*32 | 5th ISF quantizer for comfort noise | +| qisf_ns.tab | mean_isf_noise | 16 | ISF mean for comfort noise | +| qpisf_2s.tab | dico1_isf | 9*256 | 1st ISF quantizer of the 1st stage | +| qpisf_2s.tab | dico2_isf | 7*256 | 2nd ISF quantizer of the 1st stage | +| qpisf_2s.tab | dico21_isf | 3*64 | 1st ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico21_isf_36b | 5*128 | 1st ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico22_isf | 3*128 | 2nd ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico22_isf_36b | 4*128 | 2nd ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico23_isf | 3*128 | 3rd ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico23_isf_36b | 7*64 | 3rd ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico24_isf | 3*32 | 4th ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| qpisf_2s.tab | dico25_isf | 4*32 | 5th ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| qpisf_2s.tab | mean_isf | 16 | ISF mean | + +### 4.5.3 Static variables used in the C-code + +In this section two tables that specify the static variables for the speech encoder and decoder respectively are shown. All static variables are declared within a C **struct**. + +Table 7: Speech encoder static variables + +| Struct name | Variable | Type[Length] | Description | +|--------------|--------------------|---------------|-----------------------------------------------------------| +| Coder_State | mem_decim | Word16[30] | Decimation filter memory | +| | mem_sig_in | Word16[6] | Prefilter memory | +| | mem_preemph | Word16 | Preemphasis filter memory | +| | old_speech | Word16[128] | speech buffer | +| | old_wsp | Word16[115] | buffer holding spectral weighted speech | +| | old_exc | Word16[248] | excitation vector | +| | mem_levinson | Word16[18] | Levinson memories | +| | lspold | Word16[16] | Old ISP vector | +| | ispold_q | Word16[16] | Old quantized ISP vector | +| | past_isfq | Word16[16] | past quantized ISF prediction error | +| | mem_wsp | Word16 | Open-loop LTP deemphasis filter memory | +| | mem_decim2 | Word16[3] | Open-loop LTP decimation filter memory | +| | mem_w0 | Word16 | weighting filter memory (applied to error signal) | +| | mem_syn | Word16[16] | synthesis filter memory | +| | tilt_code | Word16 | Preemphasis filter memory | +| | old_wsp_max | Word16 | Open loop scaling factor | +| | old_wsp_shift | Word16 | Maximum open loop scaling factor | +| | Q_old | Word16 | Old scaling factor | +| | Q_max | Word16[2] | Maximum scaling factor | +| | gp_clip | Word16[2] | memory of pitch clipping | +| | qua_gain | Word16[4] | Gain quantization memory | +| | old_T0_med | Word16 | weighted open loop pitch lag | +| | ol_gain | Word16 | Open-loop gain | +| | ada_w | Word16 | weighing level depending on open loop pitch gain | +| | ol_wght_flg | Word16 | switches lag weighting on and off | +| | old_ol_lag | Word16[5] | Open loop lag history | +| | hp_wsp_mem | Word16[9] | Open-loop lag gain filter memory | +| | old_hp_wsp | Word16[243] | Open-loop lag | +| | vadSt | VadVars* | see below in this table | +| | dtx_encSt | dtx_encState* | see below in this table | +| | first_frame | Word16 | First frame indicator | +| | lsfold | Word16[16] | Old ISF vector | +| | L_gc_thres | Word16 | Noise enhancer threshold | +| | mem_syn_hi | Word16[16] | synthesis filter memory (most significant word) | +| | mem_syn_lo | Word16[16] | synthesis filter memory (least significant word) | +| | mem_deemph | Word16 | Deemphasis filter memory | +| | mem_sig_out | Word16[6] | HP filter memory in the synthesis | +| | mem_hp400 | Word16[6] | HP filter memory | +| | mem_oversamp | Word16[2*12] | Oversampling filter memory | +| | mem_syn_hf | Word16[16] | Higher band synthesis filter memory | +| | mem_hf | Word16[30] | Estimated BP filter memory (23.85 kbit/s mode) | +| | mem_hf2 | Word16[30] | Input BP filter memory (23.85 kbit/s mode) | +| | mem_hf3 | Word16[30] | Input LP filter memory (23.85 kbit/s mode) | +| | seed2 | Word16 | Random generation seed | +| | disp_mem | Word16[8] | Phase dispersion memory | +| | vad_hist | Word16 | VAD history | +| | Gain_alpha | Word16 | Higher band gain weighting factor (23.85 kbit/s mode) | +| dtx_encState | lsf_hist | Word16[128] | LSP history (8 frames) | +| | Log_en_hist | Word16[8] | logarithmic frame energy history (8 frames) | +| | Hist_ptr | Word16 | pointer to the cyclic history vectors | +| | Log_en_index | Word16 | Index for logarithmic energy | +| | Cng_seed | Word16 | Comfort noise excitation seed | +| | D | Word16[28] | ISF history distance matrix | +| | sumD | Word16[8] | Sum of ISF history distances | +| | dtxHangoverCount | Word16 | is decreased in DTX hangover period | +| | decAnaElapsedCount | Word16 | counter for elapsed speech frames in DTX | +| vadState1 | bckr_est | Word16[12] | background noise estimate | +| | ave_level | Word16[12] | averaged input components for stationary estimation | +| | old_level | Word16[12] | input levels of the previous frame | +| | sub_level | Word16[12] | input levels calculated at the end of a frame (lookahead) | +| | a_data5 | Word16[5][2] | memory for the filter bank | +| | a_data3 | Word16[6] | memory for the filter bank | +| | burst_count | Word16 | counts length of a speech burst | + +| Struct name | Variable | Type[Length] | Description | +|-------------|--------------|--------------|-----------------------------------------| +| | Hang_count | Word16 | hangover counter | +| | Stat_count | Word16 | stationary counter | +| | Vadreg | Word16 | 15 flags for intermediate VAD decisions | +| | Tone_flag | Word16 | 15 flags for tone detection | +| | sp_est_cnt | Word16 | Speech level estimation counter | +| | Sp_max | Word16 | Maximum signal level | +| | sp_max_cnt | Word16 | Maximum level estimation counter | +| | Speech_level | Word16 | Speech level | +| | prev_pow_sum | Word16 | Power of previous frame | + +Table 8: Speech decoder static variables + +| Struct name | Variable | Type[Length] | Description | +|---------------|---------------------|---------------|--------------------------------------------------| +| Decoder_State | old_exc | Word16[248] | excitation vector | +| | ispold | Word16[16] | Old ISP vector | +| | isfold | Word16[16] | Old ISF vector | +| | isf_buf | Word16[48] | ISF vector history | +| | past_isfq | Word16[16] | past quantized ISF prediction error | +| | tilt_code | Word16 | Preemphasis filter memory | +| | Q_old | Word16 | Old scaling factor | +| | Qsubfr | Word16 | Scaling factor history | +| | L_gc_thres | Word16 | Noise enhancer threshold | +| | mem_syn_hi | Word16[16] | synthesis filter memory (most significant word) | +| | mem_syn_lo | Word16[16] | synthesis filter memory (least significant word) | +| | mem_deemph | Word16 | Deemphasis filter memory | +| | mem_sig_out | Word16[6] | HP filter memory in the synthesis | +| | mem_oversamp | Word16[24] | Oversampling filter memory | +| | mem_syn_hf | Word16[20] | Higher band synthesis filter memory | +| | mem_hf | Word16[30] | Estimated BP filter memory (23.85 kbit/s mode) | +| | mem_hf2 | Word16[30] | Input BP filter memory (23.85 kbit/s mode) | +| | mem_hf3 | Word16[30] | Input LP filter memory (23.85 kbit/s mode) | +| | seed | Word16 | Random code generation seed for bad frames | +| | seed2 | Word16 | Random generation seed for higher band | +| | old_T0 | Word16 | Old LTP lag (integer part) | +| | old_T0_frac | Word16 | Old LTP lag (fraction part) | +| | lag_hist | Word16[5] | LTP lag history | +| | dec_gain | Word16[23] | Gain decoding memory | +| | seed3 | Word16 | Random LTP lag generation seed for bad frames | +| | disp_mem | Word16[8] | Phase dispersion memory | +| | mem_hp400 | Word16[6] | HP filter memory | +| | prev_bfi | Word16 | Previous BFI | +| | state | Word16 | BGH state machine memory | +| | first_frame | Word16 | First frame indicator | +| | dtx_decSt | dtx_decState* | see below in this table | +| | Vad_hist | Word16 | VAD history | +| dtx_decState | Since_last_sid | Word16 | number of frames since last SID frame | +| | true_sid_period_inv | Word16 | inverse of true SID update rate | +| | log_en | Word16 | logarithmic frame energy | +| | old_log_en | Word16 | previous value of log_en | +| | isf | Word16[16] | ISF vector | +| | lsf_old | Word16[16] | Previous ISF vector | +| | Cng_seed | Word16 | Comfort noise excitation seed | +| | lsf_hist | Word16[128] | ISF vector history (8 frames) | +| | Log_en_hist | Word16[8] | logarithmic frame energy history | +| | Hist_ptr | Word16 | index to beginning of LSF history | +| | dtxHangoverCount | Word16 | counts down in hangover period | +| | DecAnaElapsedCount | Word16 | counts elapsed speech frames after DTX | +| | sid_frame | Word16 | flags SID frames | +| | valid_data | Word16 | flags SID frames containing valid data | +| | log_en_adjust | Word16 | mode-dependent frame energy adjustment | +| | dtxHangoverAdded | Word16 | flags hangover period at end of speech | +| | dtxGlobalState | Word16 | DTX state flags | +| | data_updated | Word16 | flags CNI updates | + +# 5 Homing procedure + +The principles of the homing procedures are described in [2]. This specification only includes a detailed description of the 9 decoder homing frames. For each AMR-WB codec mode, the corresponding decoder homing frame has a fixed set of parameters. The parameters in serial format are packed into parameters in 15-bit-long format where the first serial bit is inserted into most significant bit in the 15-bit-long format. These 15-bit-long parameters do not represent real speech parameters, but they decrease memory consumption compared to the speech parameters. Table 9 shows the homing frame in 15-bit-long format for different modes. In the decoder, the received speech parameters in serial format are first converted into 15-bit-long format. Then the obtained parameters are compared against the homing frame table values (Table 9). + +**Table 9: Table values for the decoder homing frame in 15-bit-long format for different modes** + +| Mode | Value (MSB=b0) | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 3168, 29954, 29213, 16121, 64, 13440, 30624, 16430, 19008 | +| 1 | 3168, 31665, 9943, 9123, 15599, 4358, 20248, 2048, 17040, 27787, 16816, 13888 | +| 2 | 3168, 31665, 9943, 9128, 3647, 8129, 30930, 27926, 18880, 12319, 496, 1042, 4061, 20446, 25629, 28069, 13948 | +| 3 | 3168, 31665, 9943, 9131, 24815, 655, 26616, 26764, 7238, 19136, 6144, 88, 4158, 25733, 30567, 30494, 221, 20321, 17823 | +| 4 | 3168, 31665, 9943, 9131, 24815, 700, 3824, 7271, 26400, 9528, 6594, 26112, 108, 2068, 12867, 16317, 23035, 24632, 7528, 1752, 6759, 24576 | +| 5 | 3168, 31665, 9943, 9135, 14787, 14423, 30477, 24927, 25345, 30154, 916, 5728, 18978, 2048, 528, 16449, 2436, 3581, 23527, 29479, 8237, 16810, 27091, 19052, 0 | +| 6 | 3168, 31665, 9943, 9129, 8637, 31807, 24646, 736, 28643, 2977, 2566, 25564, 12930, 13960, 2048, 834, 3270, 4100, 26920, 16237, 31227, 17667, 15059, 20589, 30249, 29123, 0 | +| 7 | 3168, 31665, 9943, 9132, 16748, 3202, 28179, 16317, 30590, 15857, 19960, 8818, 21711, 21538, 4260, 16690, 20224, 3666, 4194, 9497, 16320, 15388, 5755, 31551, 14080, 3574, 15932, 50, 23392, 26053, 31216 | +| 8 | 3168, 31665, 9943, 9134, 24776, 5857, 18475, 28535, 29662, 14321, 16725, 4396, 29353, 10003, 17068, 20504, 720, 0, 8465, 12581, 28863, 24774, 9709, 26043, 7941, 27649, 13965, 15236, 18026, 22047, 16681, 3968 | + +# 6 File formats + +This section describes the file formats used by the encoder and decoder programs. The test sequences defined in [1] also use the file formats described here. + +## 6.1 Speech file (encoder input / decoder output) + +Speech files read by the encoder and written by the decoder consist of 16-bit words where each word contains a 14-bit, left aligned speech sample. The byte order depends on the host architecture (e.g. MSByte first on SUN workstations, LSByte first on PCs etc.). Both the encoder and the decoder program process complete frames (of 320 samples) only. + +This means that the encoder will only process $n$ frames if the length of the input file is $n*320 + k$ words, while the files produced by the decoder will always have a length of $n*320$ words. + +## 6.2 Mode control file (encoder input) + +The encoder program can optionally read in a mode control file which specifies the encoding mode for each frame of speech processed. The file is a text file containing one number per speech frame. Each line contains one of the mode numbers 0-8. + +## 6.3 Parameter bitstream file (encoder output / decoder input) + +The files produced by the speech encoder/expected by the speech decoder contain an arbitrary number of frames in the following available formats. + +### **NOTE ON DEFAULT 3GPP AND ITU BITSTREAM FORMATS:** + +ITU stream format gives very limited possibilities to distinguish NO\_DATA and SID\_FIRST frame types at the beginning of a stream. In some very limited cases for which some instance between encoder and decoder cuts of the first hangover period frames (e.g. handovers, editing of the stream), the output of the decoder is different depending on the stream format, ITU or default 3GPP. + +### Default 3GPP format: + +This is the default format used in 3GPP. This format shall be used when the codec is tested against the test vectors. + +| | | | | | | | +|--------------------|------------|------|----|----|-----|-----| +| TYPE_OF_FRAME_TYPE | FRAME_TYPE | MODE | B1 | B2 | ... | Bnn | +|--------------------|------------|------|----|----|-----|-----| + +Each box corresponds to one `Word16` value in the bitstream file, for a total of 3+nn words or 6+2nn bytes per frame, where nn is the number of encoded bits in the frame. Each encoded bit is represented as follows: Bit 0 = 0xff81, Bit 1 = 0x007f. The fields have the following meaning: + +TYPE\_OF\_FRAME\_TYPE transmit frame type, which is one of +                                         TX\_TYPE (0x6b21) +                                         RX\_TYPE (0x6b20) + +If TYPE\_OF\_FRAME\_TYPE is TX\_TYPE, + +FRAME\_TYPE transmit frame type, which is one of +                                 TX\_SPEECH (0x0000) +                                 TX\_SID\_FIRST (0x0001) +                                 TX\_SID\_UPDATE (0x0002) +                                 TX\_NO\_DATA (0x0003) + +If TYPE\_OF\_FRAME\_TYPE is RX\_TYPE, + +FRAME\_TYPE transmit frame type, which is one of +                                 RX\_SPEECH\_GOOD (0x0000) +                                 RX\_SPEECH\_PROBABLY\_DEGRADED (0x0001) +                                 RX\_SPEECH\_LOST (0x0002) +                                 RX\_SPEECH\_BAD (0x0003) +                                 RX\_SID\_FIRST (0x0004) +                                 RX\_SID\_UPDATE (0x0005) +                                 RX\_SID\_BAD (0x0006) +                                 RX\_NO\_DATA (0x0007) + +B0...B2nn speech encoder parameter bits (i.e. the bitstream itself). Each Bx either has the value 0x0081 (for bit 0) or 0x007F (for bit 1). + +MODE\_INFO encoding mode information, which is one of +                         6.60 kbit/s mode (0x0000) +                         8.85 kbit/s mode (0x0001) +                         12.65 kbit/s mode (0x0002) +                         14.25 kbit/s mode (0x0003) +                         15.85 kbit/s mode (0x0004) +                         18.25 kbit/s mode (0x0005) +                         19.85 kbit/s mode (0x0006) +                         23.05 kbit/s mode (0x0007) +                         23.85 kbit/s mode (0x0008) + +As indicated in section 6.1 above, the byte order depends on the host architecture. + +### ITU format (activated with command line parameter -itu) + +| | | | | | | +|-----------|-------------|----|----|-----|-----| +| SYNC_WORD | DATA_LENGTH | B1 | B2 | ... | Bnn | +|-----------|-------------|----|----|-----|-----| + +Each box corresponds to one Word16 value in the bitstream file, for a total of 2+nn words or 4+2nn bytes per frame, where nn is the number of encoded bits in the frame. Each encoded bit is represented as follows: Bit 0 = 0x007f, Bit 1 = 0x0081. The fields have the following meaning: + +SYNC\_WORD Word to ensure correct frame synchronization between the encoder and the decoder. It is also used to indicate the occurrences of bad frames. + +In the encoder output: (0x6b21) + In the decoder input: Good frames (0x6b21) + Bad frames (0x6b20) + +DATA\_LENGTH Length of the speech data. Codec mode and frame type is extracted in the decoder using this parameter: + +| DATA_LENGTH | PREVIOUS FRAME | CODEC MODE | FRAMETYPE | +|-------------|-------------------------------------------------|--------------|-----------------------------------| +| 0 | RX_SPEECH_GOOD/
RX_SPEECH_LOST | DTX | RX_SID_FIRST | +| 0 | OTHER THAN
RX_SPEECH_GOOD/
RX_SPEECH_LOST | DTX | RX_NO_DATA | +| 35 | - | DTX | RX_SID_UPDATE | +| 132 | - | 6.60 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 177 | - | 8.85 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 253 | - | 12.65 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 285 | - | 14.25 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 317 | - | 15.85 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 365 | - | 18.25 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 397 | - | 19.85 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 461 | - | 23.05 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | +| 477 | - | 23.85 kbit/s | RX_SPEECH_GOOD/
RX_SPEECH_LOST | + +### MIME/file storage format (activated with command line parameter -mime) + +Detailed description of the AMR-WB single channel MIME/file storage format can be found in [7] (sections 5.1 and 5.3). This format is used e.g. by the Multimedia Messaging Service (MMS). \ No newline at end of file diff --git a/marked/Rel-18/26_series/26174/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26174/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8b941ef5ddd3e16e89bb99a7f6c9405d7fbb144 --- /dev/null +++ b/marked/Rel-18/26_series/26174/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe2c8d269a887b03a05ece94c51a2090b64aa6f9b584d5cb60d68e23cd8ee899 +size 7625 diff --git a/marked/Rel-18/26_series/26174/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26174/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e4b03b8bbe2d0a66841ab12efb8406eb55e69ea --- /dev/null +++ b/marked/Rel-18/26_series/26174/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1bcd850245700d65e9b3900b512a7b0276e2404fc10b27341fc9b1ad0b28784 +size 5654 diff --git a/marked/Rel-18/26_series/26174/raw.md b/marked/Rel-18/26_series/26174/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..297f6e8dfd4a9e0004686a141e8709190bee991c --- /dev/null +++ b/marked/Rel-18/26_series/26174/raw.md @@ -0,0 +1,347 @@ + + +# 3GPP TS 26.174 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec test sequences (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 Normative references ..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 General..... | 6 | +| 5 Test sequence format ..... | 6 | +| 5.1 File format..... | 6 | +| 5.2 Codec homing ..... | 6 | +| 6 Speech codec test sequences..... | 6 | +| 6.1 Codec configuration..... | 7 | +| 6.2 Speech codec test sequences ..... | 7 | +| 6.2.1 Speech encoder test sequences ..... | 7 | +| 6.2.2 Speech decoder test sequences ..... | 8 | +| 6.2.3 Codec homing sequence..... | 8 | +| 7 Test sequences for source controlled rate operation ..... | 8 | +| 7.1 Codec configuration ..... | 8 | +| 7.2 Test Sequences ..... | 9 | +| 7.2.1 Test sequences for background noise estimation ..... | 9 | +| 7.2.2 Test sequences for tone signal detection ..... | 9 | +| 7.2.3 Real speech and tones..... | 9 | +| 7.2.4 Test sequence for signal-to-noise ratio estimation ..... | 9 | +| 8 Sequences for finding the 20 ms framing of the adaptive multi-rate speech encoder ..... | 9 | +| 8.1 Bit synchronisation..... | 10 | +| 8.2 Frame synchronisation ..... | 10 | +| 8.3 Formats and sizes of the synchronisation sequences ..... | 10 | +| Annex A (informative): Change history..... | 12 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +The present document is an introduction to the speech processing parts of the wideband telephony speech service employing the Adaptive Multi-Rate Wideband (AMR-WB) speech coder within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- 1 Scope + +The present document specifies the digital test sequences for the adaptive multi-rate wideband (AMR-WB) speech codec. These sequences test for a bit-exact implementation of the adaptive multi-rate wideband (AMR-WB) speech transcoder (TS 26.190 [2]), voice activity detection (TS 26.194 [5]), comfort noise (TS 26.192 [3]), and source controlled rate operation (TS 26.193 [4]). + +# --- 2 Normative references + +This TS incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this TS only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. + +- [1] 3GPP TS 26.201: "AMR wideband speech codec; Frame structure". +- [2] 3GPP TS 26.202: "AMR Wideband Speech Codec; Interface to RAN". +- [3] 3GPP TS 26.190 : "AMR Wideband Speech Codec; Transcoding functions". +- [4] 3GPP TS 26.193: "AMR Wideband Speech Codec; Source Controlled Rate operation". +- [5] 3GPP TS 26.194: "AMR wideband speech codec; Voice Activity Detection (VAD)". +- [6] 3GPP TS 26.201: "AMR Wideband Speech Codec; Frame structure". +- [7] 3GPP TS 26.173 : "AMR Wideband Speech Codec; ANSI-C code". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 26.190 [2], TS 26.091 [6], TS 26.192 [3], TS 26.193 [4] and TS 26.194 [5] apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +# --- 4 General + +Digital test sequences are necessary to test for a bit exact implementation of the adaptive multi-rate wideband (AMR-WB) speech transcoder (TS 26.190 [2]), voice activity detection (TS 26.194 [5]), comfort noise generation (TS 26.192 [3]), and source controlled rate operation (TS 26.193 [4]). + +The test sequences may also be used to verify installations of the ANSI C code in TS 26.173 [7]. + +Clause 5 describes the format of the files which contain the digital test sequences. Clause 6 describes the test sequences for the speech transcoder. Clause 7 describes the test sequences for the VAD, comfort noise and source controlled rate operation. + +Clause 8 describes the method by which synchronisation is obtained between the test sequences and the speech codec under test. + +# --- 5 Test sequence format + +This clause provides information on the format of the digital test sequences for the adaptive multi-rate wideband (AMR-WB) speech transcoder (TS 26.190 [3]), voice activity detection (TS 26.194 [5]), comfort noise generation (TS 26.192 [3]), and source controlled rate operation (TS 26.193 [4]). + +## 5.1 File format + +The test sequence files in PC (little-endian) byte order are provided in archive files (ZIP format) which accompany the present document. + +Following decompression, three types of file are provided: + +- Files for input to the speech encoder: \*.INP +- Files for comparison with the encoder output and for input to the speech decoder: \*.COD +- Files for comparison with the decoder output: \*.OUT +- One mode control file for the mode switching test T22.MOD + +All file formats are described in TS 26.173 [7]. + +## 5.2 Codec homing + +Each \*.INP file includes two homing frames (see TS 26.173 [7]) at the start of the test sequence. The function of these frames is to reset the speech encoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (TS 26.173 [7]), all speech encoder output frames shall be identical to the corresponding frame in the \*.COD file. In the case of a correct hardware implementation undergoing testing, the first speech encoder output frame is undefined and need not be identical to the first frame in the \*.COD file, but all remaining speech encoder output frames shall be identical to the corresponding frames in the \*.COD file. + +The function of the two homing frames in the \*.COD files is to reset the speech decoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (TS 26.173 [7]), all speech decoder output frames shall be identical to the corresponding frame in the \*.OUT file. In the case of a correct hardware implementation undergoing testing, the first speech decoder output frame is undefined and need not be identical to first frame in the \*.OUT file, but all remaining speech decoder output frames shall be identical to the corresponding frames in the \*.OUT file. + +# --- 6 Speech codec test sequences + +This clause describes the test sequences designed to exercise the adaptive multi-rate wideband (AMR-WB) speech transcoder (TS 26.190 [3]). + +## 6.1 Codec configuration + +The speech encoder shall be configured not to operate in the source controlled rate mode. + +## 6.2 Speech codec test sequences + +### 6.2.1 Speech encoder test sequences + +Twenty-three encoder input sequences are provided. Note that for the input sequences T00.INP to T03.INP, the amplitude figures are given in 14-bit precision. The active speech levels are given in dBov. + +- T00.INP - Synthetic harmonic signal. The pitch delay varies slowly from 34 to 231 samples. The minimum and maximum amplitudes are -1475 and +5952. +- T01.INP - Synthetic harmonic signal. The pitch delay varies slowly from 231 down to 34 samples. Amplitudes at saturation point -5386 and +21707. +- T02.INP - Square sweep varying from 50 Hz to 7000 Hz. Amplitudes $\pm 32767$ . +- T03.INP - Sinusoidal sweep varying from 50 Hz to 7000 Hz. Amplitudes $\pm 6217$ . +- T04.INP - Female speech, ambient noise, active speech level: -22.5 dBov, P.341 filtered. +- T05.INP - Male speech, ambient noise, active speech level: -29.9 dBov, P.341 filtered. +- T06.INP - Female and male speech, ambient noise, active speech level: -36.1 dBov, P.341 filtered. +- T07.INP - Female and male speech, ambient noise, active speech level: -45.8 dBov, P.341 filtered. +- T08.INP - Female and male speech, ambient noise, active speech level: -7.7 dBov, P.341 filtered. +- T09.INP - Female and male speech, Hoth noise, active speech level: -37.4 dBov, P.341 filtered. +- T10.INP - Female and male speech, Hoth noise, active speech level: -27.3 dBov, P.341 filtered. +- T11.INP - Female and male speech, Hoth noise, active speech level: -16.9 dBov, P.341 filtered. +- T12.INP - Female and male speech, ambient noise, active speech level: -46.0 dBov, P.341 filtered. +- T13.INP - Speech, very high and low car noise, P.341 filtered. +- T14.INP - Female and male speech, ambient noise, active speech level: -26.0 dBov, P.341 filtered. +- T15.INP - Female and male speech, rain noise, active speech level: -37.2 dBov, P.341 filtered. +- T16.INP - Female and male speech, rain noise, active speech level: -26.5 dBov, P.341 filtered. +- T17.INP - Female and male speech, rain noise, active speech level: -16.4 dBov, P.341 filtered. This file includes homing frame test. +- T18.INP - Male speech, active speech level: -29.7 dBov, P.341 filtered, with many zero frames. +- T19.INP - Child speech, ambient noise, active speech level: -34.7 dBov, P.341 filtered. +- T20.INP - Sequence for exercising the LPC vector quantisation codebooks and ROM tables of the codec. +- T21.INP - Zero signal sequence. +- T22.INP - Speech sequence for mode switching test. + +The output using these input sequences will be different depending on the tested adaptive multi-rate mode. In the notation used below should be changed to the number of the tested mode, i.e. one of 2385, 2305, 1985, 1825, 1585, 1425, 1265, 885 or 660. + +The T00.INP and T01.INP sequences were designed to test the pitch lag of the adaptive multi-rate wideband speech encoder. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the T00\_.COD and T01\_.COD sequences, respectively. + +The T02.INP and T03.INP sequences are particularly suited for testing the LPC analysis, as well as for finding saturation problems. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the T02\_.COD and T03\_.COD sequences, respectively. + +The T04.INP and T05.INP sequences contain a lot of low-frequency components. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the T04\_.COD and T05\_.COD sequences, respectively. + +The T18.INP and T21.INP sequences contain "all zeros" frames (silence) in between segments of speech. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the T18\_.COD and T21\_.COD sequences, respectively. + +The T20.INP sequence was designed to exercise the LPC code indices and the ROM table indices of the codec. + +The sequences T06.INP to T17.INP and T19.INP were selected on the basis of bringing various input characteristics (background noise) and levels to the test sequence set. Homing frame test is also included in T17.INP. T17.INP has homing frames with length 320 smp, 640 smp and 960 smp starting from 32000 smp, 16000 smp and 48000 smp in a respective order. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the T06\_.COD to T17\_.COD sequences, respectively. + +The T22.INP sequence was designed to test mode switching in the encoder. For testing mode switching this sequence is used together with the mode control file T22.MOD. See TS 26.173 [7] for the format of the mode control file. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the sequence T22.COD. Note that T22.COD contains parameter frames in different codec modes. + +### 6.2.2 Speech decoder test sequences + +Twenty-two times nine speech decoder input sequences TXX\_.COD (XX = 00..21, = {2385, 2305, 1985, 1825, 1585, 1425, 1265, 885 or 660}) are provided for the static mode tests. These are the output of the corresponding TXX.INP sequences, one set per mode. In a correct implementation, the resulting speech decoder output shall be identical to the corresponding TXX\_.OUT sequences. + +The switching test decoder input T22.COD shall result in decoder output identical to the T22.OUT sequence. For the decoder switching test no special mode control file is needed since the mode information is included in the .COD file according to the file format (see TS 26.173 [7]). + +### 6.2.3 Codec homing sequence + +In addition to the test sequences described above, the homing sequences are provided to assist in codec testing. T23.INP contains one encoder-homing-frame. The sequences T23\_.COD ( = {2385, 2305, 1985, 1825, 1585, 1425, 1265, 885 or 660}) contain one decoder-homing-frame each for the corresponding mode. The use of these sequences is described in TS 26.171 [1]. + +All files are contained in the archive T.zip which accompanies the present document. + +# --- 7 Test sequences for source controlled rate operation + +This clause describes the test sequences designed to exercise the VAD algorithm (TS 26.194 [5]), comfort noise (TS 26.192 [3]), and source controlled rate operation (TS 26.193 [4]). + +Test sequences DTX1.\*, DT2.\*, DTX4.\* and DTX5.\* shall be run only with speech codec 23.85 kbit/s. Test sequence DTX3.\* shall be run for all the speech codec modes. + +## 7.1 Codec configuration + +The VAD, comfort noise and source controlled rate operation shall be tested in conjunction with the speech coder (TS 26.190 [2]). The speech encoder shall be configured to operate in the source controlled rate mode, with VAD. + +## 7.2 Test Sequences + +Each DTX test sequence consists of three files: + +- Files for input to the speech encoder: \*.INP +- Files for comparison with the encoder output and input to the speech decoder: \*.COD +- Files for comparison with the decoder output: \*.OUT + +The \*.COD and \*.OUT file names has the format DTXA\_.\*, "A" is the test case number (1, 2, 3, 4 or 5) and is the speech codec mode. + +In a correct implementation, the speech encoder parameters generated by the \*.INP file shall be identical to those specified in the \*.COD file; and the speech decoder output generated by the \*.COD file shall be identical to that specified in the \*.OUT file. + +### 7.2.1 Test sequences for background noise estimation + +Background noise estimation algorithm is tested by the following test sequences: + +DTX1.\* + +DTX2.\* + +### 7.2.2 Test sequences for tone signal detection + +Tone signal detection algorithm is tested by the following test sequence: + +DTX3.\* + +### 7.2.3 Real speech and tones + +This test sequence consists of very clean speech, barely detectable speech and a swept frequency tone. + +DTX4.\* + +### 7.2.4 Test sequence for signal-to-noise ratio estimation + +The full range of SNR estimates are tested by the following test sequence: + +DTX5.\* + +# --- 8 Sequences for finding the 20 ms framing of the adaptive multi-rate speech encoder + +When testing the decoder, alignment of the test sequences used to the decoder framing is achieved by the air interface (testing of MS) or can be reached easily on the Abis-interface (testing on network side). + +When testing the encoder, usually there is no information available about where the encoder starts its 20 ms segments of speech input to the encoder. + +In the following, a procedure is described to find the 20 ms framing of the encoder using special synchronisation sequences. This procedure can be used for MS as well as for network side. + +Synchronisation can be achieved in two steps. First, bit synchronisation has to be found. In a second step, frame synchronisation can be determined. This procedure takes advantage of the codec homing feature of the adaptive multi-rate codec, which puts the codec in a defined home state after the reception of the first homing frame. On the reception of further homing frames, the output of the codec is predefined and can be triggered to. + +## 8.1 Bit synchronisation + +The input to the speech encoder is a series of 14 bit long words (224 kbit/s, 14 bit linear PCM). When starting to test the speech encoder, no knowledge is available on bit synchronisation, i.e., where the encoder expects its least significant bits, and where it expects the most significant bits. + +The encoder homing frame consists of 320 samples, all set to 0x0008 hex. If two such encoder homing frames are input to the encoder consecutively, the corresponding decoder homing frame of the used codec mode is expected at the output as a reaction of the second encoder homing frame. + +Since there are only 14 possibilities for bit synchronisation, after a maximum of 14 trials bit synchronisation can be reached for each codec mode. In each trial three consecutive encoder homing frames are input to the encoder. If the corresponding decoder homing frame is not detected at the output, the relative bit position of the three input frames is shifted by one and another trial is performed. As soon as the decoder homing frame of the used codec mode is detected at the output, bit synchronisation is found, and the first step can be terminated. + +The reason why three consecutive encoder homing frames are needed is that frame synchronisation is not known at this stage. To be sure that the encoder reads two complete homing frames, three frames have to be input. Wherever the encoder has its 20 ms segmentation, it will always read at least two complete encoder homing frames. + +An example of the 14 different frame triplets is given in sequence BITSYNC.INP. + +## 8.2 Frame synchronisation + +Once bit synchronisation is found, frame synchronisation can be found by inputting two identical frames consecutively to the encoder. There exist 320 different output sequences depending on the 320 different positions that the beginning of this sequence of frames can possibly have with respect to the encoder framing. + +Before inputting this special synchronisation sequence to the encoder, again the encoder has to be reset by one encoder homing frame. A second encoder homing frame is needed to provoke a decoder homing frame at the output that can be triggered to. And since the framing of the encoder is not known at that stage, three encoder homing frames have to precede the special synchronisation sequence to ensure that the encoder reads at least two homing frames, and at least one decoder homing frame is produced at the output, serving as a trigger for recording. + +After the last decoder homing frame of the used codec mode it is required to detect two consecutive output frames that are different from the preceding decoder homing frame. + +The special synchronisation sequence preceded by three encoder homing frames are given in SEQSYNC.INP. + +Generally, the output sequences will be different depending on the tested adaptive multi-rate wideband mode. In the notation below should be changed to the number of the tested mode, i.e. one of 2385, 2305, 1985, 1825, 1585, 1425, 1265, 885 or 660. + +In all 320 output sequences only the second frame after the last decoder homing frame is given in SYNC000\_.COD through SYNC319\_.COD. These output frames were calculated by shifting the sequence SEQSYNC.INP through the positions 0 to 319, where the samples at the beginning were set to zero. For each codec mode it was finally verified that the last frame in each of the 320 output sequences is different to all other last frames. + +The three digit number in the filenames above indicates the number of samples by which the input was retarded with respect to the encoder framing. By a corresponding shift in the opposite direction, alignment with the encoder framing for the used codec mode can be reached. + +## 8.3 Formats and sizes of the synchronisation sequences + +BITSYNC.INP: + +This sequence consists of 14 frame triplets. It has the format of the speech encoder input test sequences. + +The size of it is therefore: + +$$\text{SIZE (BITSYNC.INP)} = 14 * 3 * 320 * 2 \text{ bytes} = 26880 \text{ bytes}$$ + +SYNCXXX\_.COD: + +These sequences consists of 1 encoder output frame each. They have the format of the speech encoder output test sequences. In these frames the values of the TX/RX\_TYPE is fixed to indicate transmit frame type and FRAME\_TYPE and MODE\_INFO fields are set to the transmit frame type and to the corresponding encoding mode information [3]. + +The sizes of them are therefore: + +SIZE (SYNCXXX\_2385.COD) = (477 + 3) \* 2 bytes = 960 bytes +SIZE (SYNCXXX\_2305.COD) = (461 + 3) \* 2 bytes = 928 bytes +SIZE (SYNCXXX\_1985.COD) = (397 + 3) \* 2 bytes = 800 bytes +SIZE (SYNCXXX\_1825.COD) = (365 + 3) \* 2 bytes = 736 bytes +SIZE (SYNCXXX\_1585.COD) = (317 + 3) \* 2 bytes = 640 bytes +SIZE (SYNCXXX\_1425.COD) = (285 + 3) \* 2 bytes = 576 bytes +SIZE (SYNCXXX\_1265.COD) = (253 + 3) \* 2 bytes = 512 bytes +SIZE (SYNCXXX\_885.COD) = (177 + 3) \* 2 bytes = 360 bytes +SIZE (SYNCXXX\_660.COD) = (132 + 3) \* 2 bytes = 270 bytes + +All files are contained in the archive S.zip which accompanies the present document. \ No newline at end of file diff --git a/marked/Rel-18/26_series/26204/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26204/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8159bc0eae382a49a66d8ac536f7c08f0bd75876 --- /dev/null +++ b/marked/Rel-18/26_series/26204/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f78d55065a3eb69cc3acfe1cc08010c998bc91578faea66cd5c83d6433e0cf +size 7638 diff --git a/marked/Rel-18/26_series/26204/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26204/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7c0fb3ed3a4c952385f539c0388da81a376b549 --- /dev/null +++ b/marked/Rel-18/26_series/26204/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33a4f139e57dff717096db17689ae95e1a615d529a7fcae574195e028e2a1f64 +size 5315 diff --git a/marked/Rel-18/26_series/26204/raw.md b/marked/Rel-18/26_series/26204/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..64aab097e7af123b20674d6b7ffcfd4ff73cba20 --- /dev/null +++ b/marked/Rel-18/26_series/26204/raw.md @@ -0,0 +1,721 @@ + + +# 3GPP TS 26.204 V18.0.0 (2024-03) + +Technical Specification + +**3rd Generation Partnership Project; +Technical Specification Group Services and System Aspects; +Speech codec speech processing functions; +Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; +ANSI-C code +(Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|-------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 C code structure ..... | 6 | +| 4.1 Contents of the C source code..... | 6 | +| 4.2 Program execution..... | 6 | +| 4.3 Code hierarchy ..... | 7 | +| 4.4 Variables, constants and tables..... | 12 | +| 4.4.1 Description of fixed tables used in the C-code..... | 13 | +| 4.4.2 Static variables used in the C-code..... | 14 | +| 5 Homing procedure..... | 17 | +| 6 File formats ..... | 18 | +| 6.1 Speech file (encoder input/decoder output) ..... | 18 | +| 6.2 Mode control file (encoder input) ..... | 18 | +| 6.3 Parameter bitstream file (encoder output/decoder input) ..... | 18 | +| Annex A (informative): Change history..... | 19 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains an electronic copy of the ANSI-C code for the Floating-point Adaptive Multi-Rate Wideband codec. This floating-point codec specification is mainly targeted to be used in multimedia applications or in packet-based applications. The bit-exact fixed-point ANSI-C code in 3GPP TS 26.173 remains the preferred implementation for all applications, but the floating-point codec may be used instead of the fixed-point codec when the implementation platform is better suited for a floating-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts. + +The floating-point ANSI-C code in the present document is the only standard conforming non-bit-exact implementation of the Adaptive Multi-Rate Wideband speech transcoder (3GPP TS 26.190 [2]), Voice Activity Detection (3GPP TS 26.194 [6]), comfort noise generation (3GPP TS 26.192 [4]), and source controlled rate operation (3GPP TS 26.193 [5]). The floating-point code also contains example solutions for substituting and muting of lost frames (3GPP TS 26.191 [3]). + +The fixed-point specification in 26.173 shall remain the only allowed implementation for the 3G AMR-WB speech service and the use of the floating-point codec is strictly limited to other services. + +The floating-point encoder in the present document is a non-bit-exact implementation of the fixed-point encoder producing quality indistinguishable from that of the fixed-point encoder. The decoder in the present document is functionally a bit-exact implementation of the fixed-point decoder, but the code has been optimized for speed and the standard fixed-point libraries are not used as such. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 26.174: "AMR speech codec, wideband; Test sequences". +- [2] 3GPP TS 26.190: "Mandatory Speech Codec speech processing functions AMR Wideband speech codec; Transcoding functions". +- [3] 3GPP TS 26.191: "AMR speech codec, wideband; Error concealment of lost frames". +- [4] 3GPP TS 26.192: "Mandatory Speech Codec speech processing functions AMR Wideband Speech Codec; Comfort noise aspects". +- [5] 3GPP TS 26.193: "AMR speech codec, wideband; Source controlled rate operation". +- [6] 3GPP TS 26.194: "Mandatory Speech Codec speech processing functions AMR Wideband speech codec; Voice Activity Detector (VAD)". +- [7] RFC 3267 "A Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs", June 2002. + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 26.190 [2], TS 26.191 [3], TS 26.192 [4], TS 26.193 [5] and TS 26.194 [6]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-----------------------------------------| +| AMR-WB | Adaptive Multi-Rate WideBand | +| ANSI | American National Standards Institute | +| GSM | Global System for Mobile communications | +| I/O | Input/Output | +| RAM | Random Access Memory | +| ROM | Read Only Memory | + +# --- 4 C code structure + +This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the C code attached to the present document. + +The C code has been verified on the following systems: + +- IBM PC/AT compatible computers with Windows NT40 and Microsoft Visual C++ v.6.0 compiler. +- IBM PC/AT compatible computers with Windows NT40 and Intel C/C++ v.4.0 compiler. + +ANSI-C was selected as the programming language because portability was desirable. + +## 4.1 Contents of the C source code + +The C code distribution has all files in the root level. + +The distributed files with suffix "c" contain the source code and the files with suffix "h" are the header files. The ROM data is contained in "rom" files with suffix "c". + +Makefiles are provided for the platforms in which the C code has been verified (listed above). Once the software is installed, this directory will have a compiled version of encoder and decoder and all the object files. + +## 4.2 Program execution + +The Adaptive Multi-Rate Wideband codec is implemented in two programs: + +- (*encoder*) speech encoder; +- (*decoder*) speech decoder. + +The programs should be called like: + +- encoder [encoder options] +- decoder + +The speech files contain 16-bit linear encoded PCM speech samples and the parameter files contain encoded speech data and some additional flags. + +The encoder and decoder options will be explained by running the applications without input arguments. See the file *readme.txt* for more information on how to run the *encoder* and *decoder* programs. + +## 4.3 Code hierarchy + +Tables 1 and 2 are call graphs that show the functions used in the speech codec, including the functions of VAD, DTX, and comfort noise generation. + +Each column represents a call level and each cell a function. The functions contain calls to the functions in rightwards neighbouring cells. The time order in the call graphs is from the top downwards as the processing of a frame advances. All standard C functions: *memcpy()*, *fwrite()*, etc. have been omitted. The initialization of the static RAM (i.e. calling the *\_init* functions) is also omitted. + +Table 1: Speech encoder call structure + +| | | | | | +|-------------------------|-----------------------------|--------------------------|-----------------------------|---------------------| +| E_MAIN_encode | E_UTIL_decim_12k8 | E_UTIL_down_samp | E_UTIL_interpol | | +| | E_UTIL_decim_12k8 | | | | +| | E_UTIL_hp50_12k8 | | | | +| | E_UTIL_hp50_12k8 | | | | +| | E_UTIL_f_preemph | | | | +| | E_DTX_vad | E_DTX_filter_bank | E_DTX_filter5 | | +| | | | E_DTX_filter3 | | +| | | E_DTX_decision | E_DTX_level_calculation | | +| | | | E_DTX_noise_estimate_update | E_DTX_update_cntrl | +| | | E_DTX_speech_estimate | E_DTX_hangover_addition | | +| | E_DTX_tx_handler | | | | +| | E_DTX_reset | E_LPC_isf_init | | | +| | E_MAIN_parm_store | | | | +| | E_UTIL_autocorr | | | | +| | E_LPC_lag_wind | | | | +| | E_LPC_lev_dur | | | | +| | E_LPC_a_isp_conversion | E_LPC_chebyshev | | | +| | E_LPC_f_int_isp_find | E_LPC_f_isp_a_conversion | E_LPC_f_isp_pol_get | | +| | E_LPC_isp_isf_conversion | | | | +| | E_GAIN_clip_isf_test | | | | +| | E_LPC_a_weight | | | | +| | E_UTIL_residu | | | | +| | E_UTIL_deemph | | | | +| | E_GAIN_lp_decim2 | | | | +| | E_GAIN_open_loop_search | | | | +| | E_GAIN_olag_median | E_GAIN_sort | | | +| | E_DTX_pitch_tone_detection | | | | +| | E_GAIN_open_loop_search | | | | +| | E_GAIN_olag_median | | | | +| | E_DTX_pitch_tone_detection | | | | +| | E_UTIL_residu | | | | +| | E_DTX_buffer | | | | +| E_DTX_exe | E_DTX_frame_indices_finding | | | | +| | | E_DTX_isf_history_aver | | | +| | | E_DTX_isf_q | E_LPC_isf_sub_vq | | +| | | | E_LPC_isf_noise_d | E_LPC_f_isf_reorder | +| | | E_DTX_dithering_control | | | +| E_MAIN_reset | E_UTIL_random | | | | +| | E_GAIN_clip_init | | | | +| | E_DTX_reset | | | | +| | E_DTX_vad_reset | | | | +| E_LPC_isf_2s3s_quantise | E_LPC_stage1_isf_vq | | | | +| | E_LPC_isf_sub_vq | | | | +| | E_LPC_stage1_isf_vq | | | | +| | E_LPC_isf_sub_vq | | | | +| | E_LPC_2s3s_decode | | E_LPC_isf_reorder | | +| | | | | | +| E_LPC_isf_2s5s_quantise | E_LPC_stage1_isf_vq | | | | +| | E_LPC_isf_sub_vq | | | | +| | E_LPC_2s5s_decode | | E_LPC_isf_reorder | | +| | E_LPC_isp_conversion | | | | +| E_LPC_int_isp_find | E_LPC_isp_a_conversion | E_LPC_isp_pol_get | E_UTIL_l_extract | | +| | | | E_UTIL_mpy_32_16 | | +| | | | E_UTIL_l_extract | | +| | | | E_UTIL_mpy_32_16 | | +| | E_UTIL_residu | | | | +| | E_DTX_buffer | | | | +| | E_UTIL_residu | | | | +| | E_UTIL_synthesis | | | | +| | E_LPC_a_weight | | | | +| | E_UTIL_residu | | | | +| | E_UTIL_deemph | | | | +| | E_UTIL_f_preemph | | | | + +| | | | +|-------------------------------------|--------------------------------|------------------------| +| E_LPC_a_weight | | | +| E_UTIL_synthesis | | | +| E_UTIL_residu | | | +| E_LPC_a_weight | | | +| E_UTIL_synthesis | | | +| E_UTIL_deemph | | | +| E_GAIN_closed_loop_search | E_GAIN_norm_corr | E_UTIL_f_convolve | +| | E_GAIN_norm_corr_interpolate | | +| E_GAIN_clip_test | | | +| E_GAIN_adaptive_codebook_excitation | | | +| E_UTIL_convolve | | | +| E_ACELP_xy1_corr | | | +| E_ACELP_codebook_target_update | | | +| E_UTIL_convolve | | | +| E_ACELP_xy1_corr | | | +| E_ACELP_codebook_target_update | | | +| E_UTIL_f_preemph | | | +| E_GAIN_f_pitch_sharpening | | | +| E_ACELP_xh_corr | | | +| E_ACELP_2t | | | +| E_ACELP_4t | E_ACELP_h_vec_corr1 | | +| | E_ACELP_h_vec_corr2 | | +| | E_ACELP_2pulse_search | | +| | E_ACELP_quant_1p_N1 | | +| | E_ACELP_quant_2p_2N1 | | +| | E_ACELP_quant_3p_3N1 | E_ACELP_quant_2p_2N1 | +| | | E_ACELP_quant_1p_N1 | +| | E_ACELP_quant_4p_4N | E_ACELP_quant_4p_4N1 | +| | | E_ACELP_quant_2p_2N1 | +| | | E_ACELP_quant_1p_N1 | +| | | E_ACELP_quant_3p_3N1 | +| | | E_ACELP_quant_2p_2N1 | +| | | E_ACELP_quant_3p_3N1 | +| | E_ACELP_quant_5p_5N | E_ACELP_quant_3p_3N1 | +| | | E_ACELP_quant_2p_2N1 | +| | E_ACELP_quant_6p_6N2 | E_ACELP_quant_5p_5N | +| | | E_ACELP_quant_1p_N1 | +| | | E_ACELP_quant_4p_4N | +| | | E_ACELP_quant_2p_2N1 | +| | | E_ACELP_quant_3p_3N1 | +| E_UTIL_preemph | | | +| E_GAIN_pitch_sharpening | | | +| E_ACELP_xy2_corr | | | +| E_ACELP_gains_quantise | E_UTIL_dot_product12 | E_UTIL_saturate_31 | +| | | E_UTIL_norm_l | +| | E_UTIL_normalized_inverse_sqrt | | +| | E_UTIL_l_extract | | +| | E_UTIL_saturate | | +| | E_UTIL_mpy_32_16 | | +| | E_UTIL_log2_32 | E_UTIL_norm_l | +| | | E_UTIL_normalized_log2 | +| E_UTIL_signal_up_scale | | | +| E_UTIL_signal_down_scale | | | +| E_GAIN_clip_pit_test | | | +| E_UTIL_signal_down_scale | | | +| E_GAIN_voice_factor | E_UTIL_dot_product12 | | +| | E_UTIL_norm_l | | +| | E_UTIL_norm_s | | +| E_UTIL_norm_s | | | +| E_UTIL_synthesis | | | +| E_UTIL_enc_synthesis | E_UTIL_synthesis | | +| | E_UTIL_deemph | | +| | E_UTIL_hp50_12k8 | | + +| | | | +|--|--|-------------------| +| | | E_UTIL_random | +| | | E_UTIL_hp400_12k8 | +| | | E_LPC_a_weight | +| | | E_UTIL_synthesis | +| | | E_UTIL_bp_6k_7k | +| | | E_UTIL_bp_6k_7k | + +Table 2: Speech decoder call structure + +| | | | | | +|---------------|-------------------------------------|--------------------------------|--------------------------|------------------------| +| D_MAIN_decode | D_DTX_rx_handler | D_LPC_isf_noise_d | D_LPC_isf_reorder | | +| | D_DTX_exe | D_DTX_cn_dithering | D_UTIL_random | | +| | | D_UTIL_pow2 | | | +| | | D_UTIL_norm_l | | | +| | | D_UTIL_random | | | +| | | D_UTIL_dot_product12 | D_UTIL_norm_l | | +| | | D_UTIL_normalized_inverse_sqrt | | | +| | D_LPC_isf_isp_conversion | | | | +| | D_LPC_isp_a_conversion | D_LPC_isp_pol_get | D_UTIL_l_extract | | +| | | | D_UTIL_mpy_32_16 | | +| | | D_UTIL_l_extract | | | +| | D_UTIL_dec_synthesis | D_UTIL_synthesis_32 | | | +| | | D_UTIL_deemph_32 | D_UTIL_saturate | | +| | | D_UTIL_hp50_12k8 | D_UTIL_l_extract | | +| | | D_UTIL_oversamp_16k | D_UTIL_up_samp | D_UTIL_interpol | +| | | D_UTIL_random | | | +| | | D_UTIL_signal_down_scale | | | +| | | D_UTIL_dot_product12 | | | +| | | D_UTIL_normalized_inverse_sqrt | | | +| | | D_UTIL_hp400_12k8 | D_UTIL_l_extract | | +| | | D_UTIL_norm_l | | | +| | | D_LPC_isf_extrapolation | D_UTIL_norm_s | | +| | | | D_UTIL_l_extract | | +| | | | D_UTIL_mpy_32 | | +| | | | D_LPC_isf_isp_conversion | | +| | | D_LPC_isp_a_conversion | | | +| | | D_LPC_a_weight | | | +| | | D_UTIL_synthesis | | | +| | | D_LPC_a_weight | | | +| | | D_UTIL_synthesis | | | +| | | D_UTIL_bp_6k_7k | | | +| | | D_UTIL_hp_7k | | | +| | D_MAIN_reset | D_GAIN_init | | | +| | | D_GAIN_lag_concealment_init | | | +| | | D_DTX_reset | | | +| | D_LPC_isf_2s3s_decode | D_LPC_isf_reorder | | | +| | D_LPC_isf_2s5s_decode | D_LPC_isf_reorder | | | +| | D_LPC_isf_isp_conversion | | | | +| | D_LPC_int_isp_find | D_LPC_isp_a_conversion | | | +| | D_GAIN_lag_concealment | D_GAIN_sort_lag | D_GAIN_insert_lag | | +| | | D_UTIL_random | | | +| | D_GAIN_adaptive_codebook_excitation | | | | +| | D_UTIL_random | | | | +| | D_ACELP_decode_2t | | | | +| | D_ACELP_decode_4t | D_ACELP_decode_1p_N1 | | | +| | | D_ACELP_add_pulse | | | +| | | D_ACELP_decode_2p_2_N1 | | | +| | | D_ACELP_decode_3p_3_N1 | D_ACELP_decode_2p_2_N1 | | +| | | | D_ACELP_decode_1p_N1 | | +| | | D_ACELP_decode_4p_4_N | D_ACELP_decode_4p_4_N1 | D_ACELP_decode_2p_2_N1 | +| | | | | D_ACELP_decode_2p_2_N1 | +| | | | D_ACELP_decode_1p_N1 | | +| | | | | | + +| | | | +|--------------------------|--------------------------------|---------------------------| +| | | D_ACELP_decode_3p_3
N1 | +| | | D_ACELP_decode_2p_2
N1 | +| | D_ACELP_decode_5p_5
N | D_ACELP_decode_3p_3
N1 | +| | | D_ACELP_decode_2p_2
N1 | +| | D_ACELP_decode_6p_6
N_2 | D_ACELP_decode_5p_5
N | +| | | D_ACELP_decode_1p_N
1 | +| | | D_ACELP_decode_4p_4
N | +| | | D_ACELP_decode_2p_2
N1 | +| | | D_ACELP_decode_3p_3
N1 | +| D_UTIL_preemph | | | +| D_GAIN_pitch_sharpening | | | +| D_GAIN_decode | D_UTIL_dot_product12 | | +| | D_UTIL_normalized_inverse_sqrt | | +| | D_GAIN_median | | +| | D_UTIL_l_extract | | +| | D_UTIL_pow2 | | +| | D_UTIL_mpy_32_16 | | +| | D_UTIL_log2 | D_UTIL_norm_l | +| | | D_UTIL_normalized_log2 | +| D_UTIL_signal_up_scale | D_UTIL_saturate | | +| D_UTIL_signal_down_scale | | | +| D_GAIN_find_voice_factor | D_UTIL_dot_product12 | | +| | D_UTIL_norm_l | | +| | D_UTIL_norm_s | | +| D_UTIL_norm_s | | | +| D_UTIL_l_extract | | | +| D_ACELP_phase_disper | | | +| D_UTIL_mpy_32_16 | | | +| D_UTIL_l_extract | | | +| D_GAIN_adaptive_control | D_UTIL_norm_l | | +| | D_UTIL_inverse_sqrt | | +| D_UTIL_dec_synthesis | D_UTIL_saturate | | +| D_UTIL_signal_down_scale | | | +| D_DTX_activity_update | D_UTIL_log2 | | + +## 4.4 Variables, constants and tables + +The data types of variables and tables used in the floating-point implementation are signed integers in 2's complement representation, defined by: + +**Word8** 8 bit variable + +**UWord8** 8 bit unsigned variable + +**Word16** 16 bit variable + +**Word16** 16 bit unsigned variable + +**Word32** 32 bit variable + +Floating-point numbers use the IEEE (Institute of Electrical and Electronics Engineers) format: + +**Float32** 8 bit exponent, 23 bit mantissa, 1 bit sign + +**Float64** 11 bit exponent, 52 bit mantissa, 1 bit sign + +### 4.4.1 Description of fixed tables used in the C-code + +This clause contains a listing of all fixed tables declared in enc\_rom.c and dec\_rom.c files. + +**Table 3: Encoder fixed tables** + +| Format | Table name | Size | Description | +|---------|-----------------------|--------|---------------------------------------------------------------| +| Word16 | E_ROM_cdown_unusable | 7 | Attenuation factors for codebook gain in lost frames | +| Word16 | E_ROM_cdown_usable | 7 | Attenuation factors for codebook gain in bad frames | +| Float32 | E_ROM_corrweight | 199 | Weighting of the correlation function in open loop LTP search | +| Word16 | E_ROM_cos | 129 | Table of cos(x) | +| Float32 | E_ROM_dico1_isf | 9*256 | 1st ISF quantizer of the 1st stage | +| Float32 | E_ROM_dico1_isf_noise | 2*64 | 1st ISF quantizer for comfort noise | +| Float32 | E_ROM_dico21_isf | 3*64 | 1st ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico21_isf_36b | 5*128 | 1st ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico22_isf | 3*128 | 2nd ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico22_isf_36b | 4*128 | 2nd ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico23_isf | 3*128 | 3rd ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico23_isf_36b | 7*64 | 3rd ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico24_isf | 3*32 | 4th ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico25_isf | 4*32 | 5th ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Float32 | E_ROM_dico2_isf | 7*256 | 2nd ISF quantizer of the 1st stage | +| Float32 | E_ROM_dico2_isf_noise | 3*64 | 2nd ISF quantizer for comfort noise | +| Float32 | E_ROM_dico3_isf_noise | 3*64 | 3rd LSF quantizer for comfort noise | +| Float32 | E_ROM_dico4_isf_noise | 4*32 | 4th LSF quantizer for comfort noise | +| Float32 | E_ROM_dico5_isf_noise | 4*32 | 5th LSF quantizer for comfort noise | +| Float32 | E_ROM_en_adjust | 9 | Energy scaling factor for each mode during comfort noise | +| Float32 | E_ROM_f_interp_frac | 4 | LPC interpolation coefficients | +| Float32 | E_ROM_fir_6k_7k | 31 | Bandpass FIR filter coefficients for higher band generation | +| Word16 | E_ROM_fir_down | 120 | Downsample FIR filter coefficients | +| Float32 | E_ROM_fir_ipol | 61 | Interpol FIR filter coefficients | +| Word16 | E_ROM_fir_up | 120 | Upsample FIR filter coefficients | +| Float32 | E_ROM_grid | 101 | Chebyshev polynomial grid points | +| Float32 | E_ROM_hamming_cos | 384 | LP analysis window | +| Float32 | E_ROM_hp_gain | 16 | High band gain table for 23.85 kbit/s mode | +| Float32 | E_ROM_inter4_1 | 4*2*4 | Interpolation filter coefficients | +| Word16 | E_ROM_inter4_2 | 4*2*16 | Interpolation filter coefficients | +| Word16 | E_ROM_interp_frac | 4 | Interpolation filter coefficients | +| Float32 | E_ROM_isf | 16 | ISF table for initialization | +| Word16 | E_ROM_isp | 16 | ISP table for initialization | +| Word16 | E_ROM_isqrt | 49 | Table used in inverse square root computation | +| Float32 | E_ROM_lag_window | 16 | Lag window table | +| Word16 | E_ROM_log2 | 33 | Table used in logarithm computation | +| Float32 | E_ROM_f_mean_isf | 16 | ISF mean | +| Word16 | E_ROM_mean_isf | 16 | ISF mean | +| Float32 | E_ROM_mean_isf_noise | 16 | ISF mean for comfort noise | +| Word16 | E_ROM_pdown_unusable | 7 | Attenuation factors for adaptive codebook gain in lost frames | +| Word16 | E_ROM_pdown_usable | 7 | Attenuation factors for adaptive codebook gain in bad frames | +| Word16 | E_ROM_pow2 | 33 | Table used in power of two computation | +| Float32 | E_ROM_qua_gain6b | 2*64 | Gain quantization table for 6-bit gain quantization | +| Float32 | E_ROM_qua_gain7b | 2*128 | Gain quantization table for 7-bit gain quantization | +| Uword8 | E_ROM_tipos | 36 | Starting point for codebook search | + +Table 4: Decoder fixed tables + +| Format | Table name | Size | Description | +|--------|-----------------------|--------|-----------------------------------------------------------------------| +| Word16 | D_ROM_cdown_unusable | 7 | Attenuation factors for codebook gain in lost frames | +| Word16 | D_ROM_cdown_usable | 7 | Attenuation factors for codebook gain in bad frames | +| Word16 | D_ROM_cos | 129 | Table of $\cos(x)$ | +| Word16 | D_ROM_dico1_isf | 9*256 | 1st ISF quantizer of the 1st stage | +| Word16 | D_ROM_dico1_isf_noise | 2*64 | 1st ISF quantizer for comfort noise | +| Word16 | D_ROM_dico21_isf | 3*64 | 1st ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico21_isf_36b | 5*128 | 1st ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico22_isf | 3*128 | 2nd ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico22_isf_36b | 4*128 | 2nd ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico23_isf | 3*128 | 3rd ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico23_isf_36b | 7*64 | 3rd ISF quantizer of the 2nd stage (the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico24_isf | 3*32 | 4th ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico25_isf | 5*32 | 5th ISF quantizer of the 2nd stage (not the 6.60 kbit/s mode) | +| Word16 | D_ROM_dico2_isf | 7*256 | 2nd ISF quantizer of the 1st stage | +| Word16 | D_ROM_dico2_isf_noise | 3*64 | 2nd ISF quantizer for comfort noise | +| Word16 | D_ROM_dico3_isf_noise | 3*64 | 3rd LSF quantizer for comfort noise | +| Word16 | D_ROM_dico4_isf_noise | 4*32 | 4th LSF quantizer for comfort noise | +| Word16 | D_ROM_dico5_isf_noise | 4*32 | 5th LSF quantizer for comfort noise | +| Word16 | D_ROM_fir_6k_7k | 31 | Bandpass FIR filter coefficients for higher band generation | +| Word16 | D_ROM_fir_7k | 31 | Bandpass FIR filter coefficients for higher band in 23.85 kbit/s mode | +| Word16 | D_ROM_fir_down | 120 | Downsample FIR filter coefficients | +| Word16 | D_ROM_fir_up | 120 | Upsample FIR filter coefficients | +| Word16 | D_ROM_hp_gain | 16 | High band gain table for 23.85 kbit/s mode | +| Word16 | D_ROM_inter4_2 | 4*2*16 | Interpolation filter coefficients | +| Word16 | D_ROM_interpol_frac | 4 | LPC interpolation coefficients | +| Word16 | D_ROM_isf | 16 | ISF table for initialization | +| Word16 | D_ROM_isp | 16 | ISP table for initialization | +| Word16 | D_ROM_isqrt | 49 | Table used in inverse square root computation | +| Word16 | D_ROM_log2 | 33 | Table used in logarithm computation | +| Word16 | D_ROM_mean_isf | 16 | ISF mean | +| Word16 | D_ROM_mean_isf_noise | 16 | ISF mean for comfort noise | +| Word16 | D_ROM_pdown_unusable | 7 | Attenuation factors for adaptive codebook gain in lost frames | +| Word16 | D_ROM_pdown_usable | 7 | Attenuation factors for adaptive codebook gain in bad frames | +| Word16 | D_ROM_ph_imp_low | 64 | Phase dispersion impulse response | +| Word16 | D_ROM_ph_imp_mid | 64 | Phase dispersion impulse response | +| Word16 | D_ROM_pow2 | 33 | Table used in power of two computation | +| Word16 | D_ROM_qua_gain6b | 2*64 | Gain quantization table for 6-bit gain quantization | +| Word16 | D_ROM_qua_gain7b | 2*128 | Gain quantization table for 7-bit gain quantization | + +### 4.4.2 Static variables used in the C-code + +In this clause two tables that specify the static variables for the speech encoder and decoder respectively are shown. All static variables are declared within a C **struct**. + +Table 5: Speech encoder static variables + +| Struct name | Variable | Type | Length | Description | +|-----------------|---------------------------|-----------------|--------|------------------------------------------------------------------------------------------| +| Coder_State | mem_speech | Float32 | 384 | speech buffer | +| | mem_wsp | Float32 | 371 | buffer holding spectral weighted speech | +| | mem_hp_wsp | Float32 | 243 | highpass wsp | +| | mem_decim | Float32 | 30 | Open-loop LTP decimation filter memory
Estimated BP filter memory (23.85 kbit/s mode) | +| | mem_hf | Float32 | 30 | Input BP filter memory (23.85 kbit/s mode) | +| | mem_hf2 | Float32 | 30 | Input LP filter memory (23.85 kbit/s mode) | +| | mem_hf3 | Float32 | 30 | | +| | mem_isp | Float32 | 16 | Old ISP vector | +| | mem_syn | Float32 | 16 | synthesis filter memory | +| | mem_syn2 | Float32 | 16 | modified synthesis memory | +| | mem_syn_hf | Float32 | 16 | Higher band synthesis filter memory | +| | mem_isf | Float32 | 16 | Old ISF vector | +| | mem_hf_wsp | Float32 | 9 | Open-loop lag gain filter memory | +| | mem_sig_in | Float32 | 4 | Prefilter memory | +| | mem_sig_out | Float32 | 4 | HP filter memory in the synthesis | +| | mem_hp400 | Float32 | 4 | HP filter memory | +| | mem_decim2 | Float32 | 3 | Open-loop LTP decimation filter memory | +| | mem_gp_clip | Float32 | 2 | Memory of pitch clipping | +| | mem_preemph | Float32 | 1 | Preemphasis filter memory | +| | mem_deemph | Float32 | 1 | Deemphasis filter memory | +| | mem_wsp_df | Float32 | 1 | Open-loop LTP deemphasis filter memory | +| | mem_w0 | Float32 | 1 | Weighting filter memory (applied to error signal) | +| | mem_ol_gain | Float32 | 1 | Open-loop gain | +| | mem_ada_w | Float32 | 1 | Weighting level depending on open loop pitch gain | +| | mem_gc_threshold | Float32 | 1 | Noise enhancer threshold | +| | mem_gain_alpha | Float32 | 1 | Higher band gain weighting factor (23.85 kbit/s mode) | +| | mem_ol_lag | Word32 | 5 | Open loop lag history | +| | mem_T0_med | Word32 | 1 | Weighted open loop pitch lag | +| | mem_exc | Word16 | 505 | Excitation vector | +| | mem_isp_q | Word16 | 16 | Old ISP vector | +| | mem_isf_q | Word16 | 16 | Past quantized ISF prediction error | +| | mem_gain_q | Word16 | 4 | Gain quantization memory | +| | mem_subfr_q | Word16 | 4 | Scaling factor history | +| | mem_tilt_code | Word16 | 1 | Preemphasis filter memory | +| | mem_q | Word16 | 1 | Old scaling factor | +| | mem_seed | Word16 | 1 | Random generation seed | +| | *vadSt | E_DTX_Vad_State | 1 | See below in this table | +| | *dtx_encSt | E_DTX_State | 1 | See below in this table | +| | mem_first_frame | UWord8 | 1 | First frame indicator | +| | mem_ol_wght_flg | UWord8 | 1 | Switches lag weighting on and off | +| | mem_vad_hist | UWord8 | 1 | VAD history | +| E_DTX_State | mem_isf | Float32 | 128 | LSP history | +| | mem_distance | Float32 | 28 | ISF history distance matrix | +| | mem_distance_sum | Float32 | 8 | Sum of ISF history distances | +| | mem_log_en | Float32 | 8 | Logarithmic frame energy history | +| | mem_hist_ptr | Word16 | 1 | Pointer to the cyclic history vectors | +| | mem_log_en_index | Word16 | 1 | Index for logarithmic energy | +| | mem_cng_seed | Word16 | 1 | Comfort noise excitation seed | +| | mem_dtx_hangover_count | Word16 | 1 | DTX hangover period | +| | mem_dec_ana_elapsed_count | Word16 | 1 | Counter for elapsed speech frames in DTX | +| E_DTX_Vad_State | mem_pow_sum | Float64 | 1 | Power of previous frame | +| | mem_bckr_est | Float32 | 12 | Background noise estimate | +| | | | | Averaged input components for stationary estimation | +| | mem_ave_level | Float32 | 12 | Input levels of the previous frame | +| | mem_leve | Float32 | 12 | Input levels calculated at the end of a frame (lookahead) | +| | mem_sub_level | Float32 | 12 | | + +| Struct name | Variable | Type | Length | Description | +|-------------|------------------|---------|--------|--------------------------------------| +| | mem_a_data5 | Float32 | 10 | Memory for the filter bank | +| | mem_a_data3 | Float32 | 6 | Memory for the filter bank | +| | mem_sp_max | Float32 | 1 | Maximum level | +| | mem_speech_level | Float32 | 1 | Estimated speech level | +| | mem_burst_count | Word16 | 1 | Counts length of a speech burst | +| | mem_hang_count | Word16 | 1 | Hangover counter | +| | mem_stat_count | Word16 | 1 | Stationary counter | +| | mem_vadreg | Word16 | 1 | Flags for intermediate VAD decisions | +| | mem_pitch_tone | Word16 | 1 | Flags for pitch and tone detection | +| | mem_sp_est_cnt | Word16 | 1 | Counter for speech level estimation | +| | mem_sp_max_cnt | Word16 | 1 | Counts frames that contains speech | + +Table 6: Speech decoder static variables + +| Struct name | Variable | Type | Length | Description | +|---------------|---------------------------|-------------|--------|-------------------------------------------| +| Decoder_State | mem_gc_thres | Word32 | 1 | Threshold for noise enhancer | +| | mem_exc | Word16 | 505 | INTERPOL]; /* old excitation vector | +| | mem_isf_buf | Word16 | 48 | ISF buffer(frequency domain) | +| | mem_hf | Word16 | 30 | HF band-pass filter memory | +| | mem_hf2 | Word16 | 30 | HF band-pass filter memory | +| | mem_hf3 | Word16 | 30 | HF band-pass filter memory | +| | mem_oversamp | Word16 | 24 | Synthesis oversampled filter memory | +| | mem_gain | Word16 | 23 | Gain decoder memory | +| | mem_syn_hf | Word16 | 20 | HF synthesis memory | +| | mem_isp | Word16 | 16 | Old ISP (immittance spectral pairs) | +| | mem_isf | Word16 | 16 | Old ISF (frequency domain) | +| | mem_isf_q | Word16 | 16 | Past ISF quantizer | +| | mem_syn_hi | Word16 | 16 | Modified synthesis memory (MSB) | +| | mem_syn_lo | Word16 | 16 | Modified synthesis memory (LSB) | +| | mem_ph_disp | Word16 | 8 | Phase dispersion memory | +| | mem_sig_out | Word16 | 6 | Hp50 filter memory for synthesis | +| | mem_hp400 | Word16 | 6 | Hp400 filter memory for synthesis | +| | mem_lag | Word16 | 5 | LTP lag history | +| | mem_subfr_q | Word16 | 4 | Old maximum scaling factor | +| | mem_tilt_code | Word16 | 1 | Tilt of code | +| | mem_q | Word16 | 1 | Old scaling factor | +| | mem_deemph | Word16 | 1 | Speech deemph filter memory | +| | mem_seed | Word16 | 1 | Random memory for frame erasure | +| | mem_seed2 | Word16 | 1 | Random memory for HF generation | +| | mem_seed3 | Word16 | 1 | Random memory for lag concealment | +| | mem_T0 | Word16 | 1 | Old pitch lag | +| | mem_T0_frac | Word16 | 1 | Old pitch fraction lag | +| | mem_vad_hist | UWord16 | 1 | VAD history | +| | dtx_decSt | D_DTX_State | 1 | See below in this table | +| | mem_bfi | UWord8 | 1 | Previous BFI | +| | mem_state | UWord8 | 1 | BGH state machine memory | +| | mem_first_frame | UWord8 | 1 | First frame indicator | +| dtx_decState | mem_isf_buf | Word16 | 128 | ISF vector history (8 frames) | +| | mem_isf | Word16 | 16 | ISF vector | +| | mem_isf_prev | Word16 | 16 | Previous ISF vector | +| | mem_log_en_buf | Word16 | 8 | Logarithmic frame energy history | +| | mem_true_sid_period_inv | Word16 | 1 | Inverse of true SID update rate | +| | mem_log_en | Word16 | 1 | Logarithmic frame energy | +| | mem_log_en_prev | Word16 | 1 | Previous logarithmic frame energy | +| | mem_cng_seed | Word16 | 1 | Comfort noise excitation seed | +| | mem_hist_ptr | Word16 | 1 | Index to beginning of LSF history | +| | mem_dither_seed | Word16 | 1 | Comfort noise dithering seed | +| | mem_cn_dith | Word16 | 1 | Background noise stationarity information | +| | mem_since_last_sid | Word16 | 1 | Number of frames since last SID frame | +| | mem_dec_ana_elapsed_count | UWord8 | 1 | Counts elapsed speech frames after DTX | +| | mem_dtx_global_state | UWord8 | 1 | DTX state flags | +| | mem_data_updated | UWord8 | 1 | Flags CNI updates | +| | mem_dtx_hangover_count | UWord8 | 1 | Counts down in hangover period | +| | mem_sid_frame | UWord8 | 1 | Flags SID frames | +| | mem_valid_data | UWord8 | 1 | Flags SID frames containing valid data | +| | mem_dtx_hangover_added | UWord8 | 1 | Flags hangover period at end of speech | + +# 5 Homing procedure + +The principles of the homing procedures are described in [2]. The present document only includes a description of the 9 decoder homing frames. For each AMR-WB codec mode, the corresponding decoder homing frame has a fixed set of speech parameters. Table 7 shows the homing frame speech parameters for different modes. + +**Table 7: Table values for the decoder homing frame parameters for different modes** + +| Mode | Speech Parameters | +|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 0, 49, 131, 84, 5, 50, 29, 2015, 8, 0, 2061, 8, 1, 3560, 8, 0, 2981, 8 | +| 1 | 0, 49, 131, 55, 49, 38, 26, 29, 29, 3, 15, 7, 15, 8, 16, 13, 7, 17, 16, 8, 0, 16, 20, 16, 27, 8, 23, 0, 27, 0, 27, 8 | +| 2 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 7, 63, 127, 15, 70, 37, 1, 209, 210, 224, 96, 31, 7, 1, 256, 260, 271, 443, 31, 47, 0, 400, 238, 436, 347, 31 | +| 3 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 3847, 3845, 63, 127, 70, 34, 0, 3128, 4517, 192, 96, 0, 2, 1, 4160, 8036, 267, 443, 31, 46, 0, 3840, 7091, 432, 395, 31 | +| 4 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 3847, 3845, 3847, 3843, 70, 31, 0, 3648, 4764, 824, 2864, 0, 6, 1, 4160, 5220, 4319, 7131, 31, 47, 0, 112, 3764, 219, 211, 31 | +| 5 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 3, 2, 3, 2, 7223, 703, 7223, 703, 70, 0, 1, 3, 2, 2, 3, 9475, 9483, 3090, 8737, 0, 0, 1, 0, 0, 2, 0, 4112, 4400, 8415, 14047, 31, 38, 0, 2, 1, 3, 1, 91, 426, 13545, 12955, 0 | +| 6 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 161, 759, 3, 2, 127, 516, 6167, 447, 70, 11, 1, 264, 641, 2, 3, 123, 562, 8347, 4354, 0, 1, 1, 264, 408, 3, 0, 256, 308, 9487, 14047, 31, 46, 0, 320, 885, 2, 2, 464, 439, 11347, 12739, 0 | +| 7 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 1154, 1729, 1154, 1761, 447, 1519, 959, 495, 70, 27, 1, 1800, 1253, 665, 1960, 546, 164, 1043, 335, 0, 28, 1, 580, 196, 1187, 383, 1031, 1052, 359, 1531, 31, 45, 1, 1024, 893, 1272, 1920, 101, 876, 203, 1119, 31 | +| 8 | 0, 49, 131, 55, 49, 38, 26, 29, 58, 1, 1729, 1154, 1761, 1154, 1519, 959, 495, 447, 70, 3, 42, 1, 580, 1436, 1362, 1250, 901, 714, 24, 45, 0, 0, 0, 1, 68, 708, 1212, 383, 1048, 1611, 1756, 1467, 31, 1, 23, 0, 1536, 1460, 861, 1554, 410, 1368, 1008, 594, 31, 0 | + +# 6 File formats + +This clause describes the file formats used by the encoder and decoder programs. The test sequences defined in [1] also use the file formats described here. + +## 6.1 Speech file (encoder input/decoder output) + +Speech files read by the encoder and written by the decoder consist of 16-bit words where each word contains a 14-bit, left aligned speech sample. The byte order depends on the host architecture (e.g. MSByte first on SUN workstations, LSByte first on PCs etc.). Both the encoder and the decoder program process complete frames (of 320 samples) only. + +This means that the encoder will only process $n$ frames if the length of the input file is $n*320 + k$ words, while the files produced by the decoder will always have a length of $n*320$ words. + +## 6.2 Mode control file (encoder input) + +The encoder program can optionally read in a mode control file which specifies the encoding mode for each frame of speech processed. The file is a text file containing one number per speech frame. Each line contains one of the mode numbers 0-8. + +## 6.3 Parameter bitstream file (encoder output/decoder input) + +The files produced by the speech encoder/expected by the speech decoder are described in RFC 3267 [7], sections 5.1 and 5.3. + +By using a preprocessor definition encoder/decoder can optionally use format described in TS26.201 that defines an octet-aligned frame format (Interface format 2) for the AMR-WB codec. \ No newline at end of file diff --git a/marked/Rel-18/26_series/26452/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26452/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adf37a3ac12b21d23f8b0e33a122ce2b320e21ac --- /dev/null +++ b/marked/Rel-18/26_series/26452/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e26c04424e25e72decbc6c5085aabdfce97d16b5b5647f88e6562cec1b3a62a +size 9556 diff --git a/marked/Rel-18/26_series/26452/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26452/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..610e6162a3d2df15050e4b11e643758d1e30b90d --- /dev/null +++ b/marked/Rel-18/26_series/26452/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:937d3aea356be34c0940ec0a07cbb14af3998ee31c0b468fbab55d631398121c +size 5314 diff --git a/marked/Rel-18/26_series/26452/raw.md b/marked/Rel-18/26_series/26452/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05effa6b8f7fde87118250a5a10a19ae97789b78 --- /dev/null +++ b/marked/Rel-18/26_series/26452/raw.md @@ -0,0 +1,308 @@ + + +# 3GPP TS 26.452 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Codec for Enhanced Voice Services (EVS); ANSI C code; Alternative fixed-point using updated basic operators (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo. + +3GPP logo + +## --- **Keywords** + +UMTS, LTE, EVS, telephony, codec + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 C code structure ..... | 6 | +| 4.0 General ..... | 6 | +| 4.1 Contents of the C source code..... | 6 | +| 4.2 Program execution..... | 7 | +| 5 File formats ..... | 7 | +| 5.0 General ..... | 7 | +| 5.1 Speech file (encoder input / decoder output) ..... | 7 | +| 5.2 Rate switching profile (encoder input)..... | 8 | +| 5.3 Parameter bitstream file (encoder output / decoder input) ..... | 8 | +| 5.3.0 General ..... | 8 | +| 5.3.1 ITU-T G.192 compliant format ..... | 8 | +| 5.3.2 Compact storage format file ..... | 8 | +| 5.4 VoIP parameter bitstream file (decoder input)..... | 8 | +| 5.5 Bandwidth switching profile (encoder input)..... | 9 | +| 5.6 Channel-aware configuration file (encoder input and decoder output)..... | 9 | +| 5.7 JBM trace file (decoder output) ..... | 9 | +| Annex A (informative): Change history..... | 10 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains an electronic copy of the ANSI-C code for alternative fixed-point implementation of the Enhanced Voice Services (EVS) Codec using updated basic operators [13]. The ANSI-C code is necessary for a bit exact implementation of the EVS Codec (3GPP TS 26.445), Voice Activity Detection (VAD) (3GPP TS 26.451), Comfort Noise Generation (CNG) (3GPP TS 26.449), Discontinuous Transmission (DTX) (3GPP TS 26.450), Packet Loss Concealment (PLC) of Lost Packets (3GPP TS 26.447), Jitter Buffer Management (JBM) (3GPP TS 26.448), and AMR-WB Interoperable Function (3GPP TS 26.446). + +Requirements for any implementation of the EVS codec to be standard compliant are specified in 3GPP TS 26.444 (Test sequences). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 26.445: "Codec for Enhanced Voice Services (EVS); Detailed Algorithmic Description". +- [3] 3GPP TS 26.451: "Codec for Enhanced Voice Services (EVS); Voice Activity Detection (VAD)". +- [4] 3GPP TS 26.449: "Codec for Enhanced Voice Services (EVS); Comfort Noise Generation (CNG) Aspects". +- [5] 3GPP TS 26.450: "Codec for Enhanced Voice Services (EVS); Discontinuous Transmission (DTX)". +- [6] 3GPP TS 26.447: "Codec for Enhanced Voice Services (EVS); Error Concealment of Lost Packets". +- [7] 3GPP TS 26.448: "Codec for Enhanced Voice Services (EVS); Jitter Buffer Management". +- [8] 3GPP TS 26.446: "Codec for Enhanced Voice Services (EVS); AMR-WB Backward Compatible Functions". +- [9] 3GPP TS 26.444: "Codec for Enhanced Voice Services (EVS); Test Sequences". +- [10] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [11] Recommendation ITU-T G.191 (03/10): "Software tools for speech and audio coding standardization". +- [12] Recommendation ITU-T G.192: "A common digital parallel interface for speech standardization activities". +- [13] 3GPP TR 26.973: "Update to fixed-point basic operators". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +Definition of terms used in the present document, can be found in 3GPP TS 26.445 [2], 3GPP TS 26.451 [3], 3GPP TS 26.449 [4], 3GPP TS 26.450 [5], 3GPP TS 26.447 [6], 3GPP TS 26.448 [7] and 3GPP TS 26.446 [8]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|--------------------------------------------| +| ACELP | Algebraic Code-Excited Linear Prediction | +| AMR-WB | Adaptive Multi Rate Wideband (codec) | +| CNG | Comfort Noise Generator | +| DTX | Discontinuous Transmission | +| EVS | Enhanced Voice Services | +| FB | Fullband | +| FEC | Frame Erasure Concealment | +| IP | Internet Protocol | +| JBM | Jitter Buffer Management | +| MSB | Most Significant Bit | +| MTSI | Multimedia Telephony Service for IMS | +| NB | Narrowband | +| PS | Packet Switched | +| PSTN | Public Switched Telephone Network | +| SAD | Sound Activity Detection | +| SC-VBR | Source Controlled - Variable Bit Rate | +| SID | Silence Insertion Descriptor | +| SWB | Super WideBand | +| VAD | Voice Activity Detection | +| WB | Wideband | +| WMOPS | Weighted Millions of Operations Per Second | + +# --- 4 C code structure + +## 4.0 General + +This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the C code attached to the present document. + +The C code has been verified on the following systems: + +- IBM PC compatible computers with Windows 7 or 8 operating system and Microsoft Visual C++ 2017 compiler, 32 bit builds. +- IBM PC compatible computers with Linux operating system and GNU gcc compiler version 4.3.x, 32 bit builds. + +ANSI-C was selected as the programming language because portability was desirable. + +## 4.1 Contents of the C source code + +The C code distribution is organized as follows: + +**Table 1: Source code directory structure** + +| Directory | Description | +|-----------------|---------------------------------------------------------------------| +| README.txt | information on how to compile | +| Makefile | UNIX style encoder Makefile | +| Workspace_msvc/ | Directory for the MSVC 2017 project files | +| basic_op/ | Source code files containing all ITU-T fixed-point basic operators. | +| basic_math/ | Source code files contains mathematical fixed-point functions | +| lib_com/ | Source code files used in encoder and decoder | +| lib_dec/ | Source code files used solely in the decoder | +| lib_enc/ | Source code files used solely in the encoder | + +The distributed files with suffix "c" contain the source code and the files with suffix "h" are the header files. The ROM data is contained in files named "rom\_xxx" with suffix "c". + +Makefiles are provided for the platforms in which the C code has been verified (listed above). Once the software is installed, this directory will have a compiled version of the encoder (named EVS\_cod) and the decoder (named EVS\_dec). + +## 4.2 Program execution + +The codec for Enhanced Voice Services is implemented in two programs: + +- EVS\_cod: speech/audio encoder; +- EVS\_dec: speech/audio decoder. + +The programs should be called like: + +- EVS\_cod [encoder options] ; +- EVS\_dec [decoder options] . + +The speech/audio files contain 16-bit linear encoded PCM speech/audio samples and the parameter files contain encoded speech/audio data. + +The encoder and decoder options will be explained by running the applications without input arguments. See the file readme.txt for more information on how to run the *encoder* and *decoder* programs. + +# 5 File formats + +## 5.0 General + +This clause describes the file formats used by the encoder and decoder programs. The test sequences defined in [9] also use the file formats described here. + +## 5.1 Speech file (encoder input / decoder output) + +Speech files read by the encoder and written by the decoder consist of 16-bit words speech/audio sample. The byte order depends on the host architecture (e.g. LSByte first on PCs, etc.). Both the encoder and the decoder program process complete frames (corresponding to 20 ms, for example, 640 samples at 32 kHz sampling frequency) only. + +The encoder will pad the last frame to integer multiples of 20ms frames, i.e. $n$ speech frames will be produced from an input file with a length between $[(n-1)*20\text{ms}+1 \text{ sample}; n*20\text{ms}]$ . The files produced by the decoder will always have a length of $n*20\text{ms}$ . + +## 5.2 Rate switching profile (encoder input) + +The encoder program can optionally read in a rate switching profile which specifies the encoding bitrate for each frame of speech processed. The file is a binary file, generated by 'gen-rate-profile', which is part of STL 2009, as contained in ITU-T G.191 [11]. The rate switching profile can contain EVS primary mode bitrates and AMR-WB IO mode bitrates arbitrarily. I.e. switching between the two modes can be specified by the rate switching profile. + +## 5.3 Parameter bitstream file (encoder output / decoder input) + +### 5.3.0 General + +The files produced by the speech/audio encoder/expected by the speech decoder contain an arbitrary number of frames in the following available formats. + +#### 5.3.1 ITU-T G.192 compliant format + +| | | | | | | +|-----------|-------------|----|----|-----|-----| +| SYNC_WORD | DATA_LENGTH | B1 | B2 | ... | Bnn | +|-----------|-------------|----|----|-----|-----| + +Each box corresponds to one `Word16` value in the bitstream file, for a total of $2+nn$ words or $4+2nn$ bytes per frame, where $nn$ is the number of encoded bits in the frame. Each encoded bit is represented as follows: Bit 0 = 0x007f, Bit 1 = 0x0081. The fields have the following meaning: + +- `SYNC_WORD`: Word to ensure correct frame synchronization between the encoder and the decoder. It is also used to indicate the occurrences of bad frames. + +In the encoder output: (0x6b21) + +In the decoder input: Good frames (0x6b21) +Bad frames (0x6b20) + +- `DATA_LENGTH`: Length of the speech data. Codec mode and frame type is extracted in the decoder using this parameter + +#### 5.3.2 Compact storage format file + +The encoder and decoder programs can optionally write and read a file in the octet-based compact storage format. The compact storage format is specified in clause A.2.6 of [2]. + +### 5.4 VoIP parameter bitstream file (decoder input) + +| | | | | +|-------------|--------------|------------|--------------------------| +| Packet size | Arrival time | RTP header | G.192 format (see 5.3.1) | +|-------------|--------------|------------|--------------------------| + +The fields have the following size and meaning: + +- Packet size: 32 bit unsigned integer. ( $= 12 + 2 + \text{DATA\_LENGTH}$ ) +- Arrival time: 32 bit unsigned integer. in ms. +- RTP header: 96 bits (see RFC 3550 [10]), including RTP timestamp and SSRC. + +### 5.5 Bandwidth switching profile (encoder input) + +The encoder program can optionally read in a bandwidth switching profile, which specifies the encoding bandwidth for each frame of speech processed. The file is a text file where each line contains "nb\_frames B". B specifies the signal bandwidth that is one of the supported four bandwidths, i.e. NB, WB, SWB or FB. And "nb\_frames" is an integer number of frames and specifies the duration of activation of the accompanied signal bandwidth B. + +### 5.6 Channel-aware configuration file (encoder input and decoder output) + +The encoder program can optionally read in a configuration file which specifies the values of FEC indicator p and FEC offset o, where FEC indicator, p: LO or HI, and FEC offset, o: 2, 3, 5, or 7 in number of frames. Each line of the configuration file contains the values of p and o separated by a space. + +The channel-aware configuration file is meant to simulate channel feedback from a receiver to a sender, i.e. the decoder would generate FEC indication and FEC offset values for receiver feedback that correspond to the current transmission channel characteristics, thereby allowing optimization of the transmission by the encoder which applies the FEC offset and FEC indication when in the channel-aware mode. + +## 5.7 JBM trace file (decoder output) + +The decoder can generate a JBM trace file with the –Tracefile switch as a by-product of the decoder operation in case of JBM operation (which is triggered with the –VOIP switch on the decoder side). + +The trace file is a CSV file with semi-colon as separator. The trace file starts with one header line that contains the column names in the following order: + +`rtpSeqNo;rtpTs;rcvTime;playtime;active` + +For each played out speech frame one entry is written to the trace file. The interval of the playtime values is usually 20ms, but may differ, depending on the JBM operation. Each entry is a line in the trace file that contains values as specified in Table 2. + +**Table 2: JBM trace file entry format** + +| Name | Unit | Description | +|----------|--------|------------------------------------------------------------------------------------------------------------------------------------------------| +| rtpSeqNo | 1 | RTP sequence number of played out speech frame. -1 if no corresponding RTP packet for the speech frame exists. | +| rtpTs | ms | RTP time stamp of played out speech frame. -1 if no corresponding RTP packet for the speech frame exists | +| rcvTime | ms | Absolute reception time of the RTP packet that corresponds to the speech frame. -1 if no corresponding RTP packet for the speech frame exists. | +| playtime | ms | Absolute play time (i.e. the time at which the PCM data is made available by the decoder). Can be floating-point value. | +| active | 0 or 1 | Binary entry, which is set to 1 for active speech frames (i.e. frames that are neither SID nor NO_DATA) | + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|--------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-12 | SA#82 | SP-180978 | | | | Presented at SA#82 for approval | 1.0.0 | +| 2018-12 | SA#82 | | | | | Approved at SA#82 | 16.0.0 | +| 2019-03 | SA#83 | SP-190036 | 0001 | - | F | Update of EVS Alt FX EVS | 16.1.0 | +| 2020-07 | SA#88-e | SP-200391 | 0002 | 1 | F | Corrections to EVS Alternative Fixed-Point Source Code | 16.2.0 | +| 2020-10 | Post SA#88-e | | | | | Update of the Change History Table | 16.2.1 | +| 2021-09 | SA#93-e | SP-210825 | 0004 | 1 | F | Corrections to EVS Alternative Fixed-Point Source Code | 16.3.0 | +| 2021-12 | SA#94-e | SP-211345 | 0005 | - | F | Corrections to EVS Alternative Fixed-Point Source Code | 16.4.0 | +| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | - | - | - | - | - | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26511/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26511/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3facb33b865fb6600bfb5c8187dc975a438b7204 --- /dev/null +++ b/marked/Rel-18/26_series/26511/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73770d7fa69e538b79aaf9696c60b001e5725897d6fb1eafb70dd67dc21b10a4 +size 9915 diff --git a/marked/Rel-18/26_series/26511/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26511/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61b05d4b09cb919802e4163bc4ec88ef7e05728d --- /dev/null +++ b/marked/Rel-18/26_series/26511/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29dfbbed8d66fca999e7159e5739d46b20c06a653ce8716a154bb1ea1bf51670 +size 5800 diff --git a/marked/Rel-18/26_series/26511/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-18/26_series/26511/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..331949f209ad4a3450873345735f3d9256fcf9c9 --- /dev/null +++ b/marked/Rel-18/26_series/26511/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b01391b8727798c0bc994cb6782c472a8954c3d77a73231d2a7fc1743940d5b4 +size 85686 diff --git a/marked/Rel-18/26_series/26511/raw.md b/marked/Rel-18/26_series/26511/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cd6b96060e32f151b2a99115fc3dd8270cb29d80 --- /dev/null +++ b/marked/Rel-18/26_series/26511/raw.md @@ -0,0 +1,1412 @@ + + +# 3GPP TS 26.511 V18.0.0 (2023-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Media Streaming (5GMS); Profiles, Codecs and Formats (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic element consisting of three curved lines of increasing height, resembling a signal strength indicator or a stylized wave. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. Below the "P" is a small red graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 3A Overview..... | 9 | +| 3A.1 Introduction ..... | 9 | +| 3A.2 Codecs and Formats in Downlink Media Streaming ..... | 9 | +| 3A.2.1 Architecture, Interfaces and APIs..... | 9 | +| 3A.2.2 Hypothetical Device Playback Model..... | 10 | +| 3A.2.3 Necessary Conditions for Codecs and Formats in 5GMSd ..... | 11 | +| 3A.3 Codecs and Formats in Uplink Media Streaming ..... | 11 | +| 4 5GMS codecs and formats capabilities..... | 11 | +| 4.1 Introduction ..... | 11 | +| 4.2 Video ..... | 11 | +| 4.2.1 H.264 (AVC)..... | 11 | +| 4.2.1.1 Decoding..... | 11 | +| 4.2.1.2 Encoding..... | 12 | +| 4.2.1.3 Media Profiles: Mapping to 5GMS Delivery ..... | 13 | +| 4.2.1.3.1 AVC-HD ..... | 13 | +| 4.2.1.3.2 AVC-FullHD ..... | 14 | +| 4.2.1.3.3 AVC-UHD ..... | 15 | +| 4.2.2 H.265 (HEVC)..... | 16 | +| 4.2.2.1 Decoding..... | 16 | +| 4.2.2.2 Encoding..... | 16 | +| 4.2.2.3 Media Profiles: Mapping to 5G Media Streaming..... | 17 | +| 4.2.2.3.1 HEVC-HD..... | 17 | +| 4.2.2.3.2 HEVC-FullHD ..... | 18 | +| 4.2.2.3.3 HEVC-UHD..... | 19 | +| 4.2.2.3.4 HEVC-8K..... | 21 | +| 4.3 Audio..... | 22 | +| 4.3.1 Decoding..... | 22 | +| 4.3.2 Encoding..... | 22 | +| 4.4 Speech ..... | 22 | +| 4.4.1 Decoding..... | 22 | +| 4.4.2 Encoding..... | 22 | +| 4.5 Subtitles..... | 22 | +| 4.5.1 IMSC1.1. Text Track..... | 22 | +| 4.5.1.1 Decoding Capability ..... | 22 | +| 4.5.1.2 ISO BMFF File Format..... | 22 | +| 4.5.1.3 CMAF Track Definition ..... | 22 | +| 4.5.1.4 CMAF Switching Set Definition ..... | 22 | +| 4.5.1.5 Playback Requirements..... | 23 | +| 5 5GMS Profiles..... | 23 | +| 5.1 Introduction ..... | 23 | +| 5.2 Downlink streaming default profile ..... | 23 | +| 5.2.1 Introduction ..... | 23 | +| 5.2.2 Video decoding..... | 23 | +| 5.2.3 Audio decoding ..... | 24 | +| 5.2.4 Speech decoding..... | 24 | +| 5.2.5 Subtitles ..... | 24 | + +| | | | +|-------------------------------|-------------------------------------------------|-----------| +| 5.2.6 | Presentation format..... | 24 | +| 5.2.7 | Decapsulation and decryption ..... | 24 | +| 5.2.7.1 | Introduction..... | 24 | +| 5.2.7.2 | Video media profiles..... | 24 | +| 5.2.7.3 | Speech media profiles..... | 25 | +| 5.2.7.4 | Audio media profiles ..... | 25 | +| 5.2.7.5 | Subtitle media profiles ..... | 25 | +| 5.2.7.6 | Encrypted content ..... | 25 | +| 5.2.8 | Capability discovery ..... | 26 | +| 5.2.8.1 | General..... | 26 | +| 5.2.8.2 | Video media profiles..... | 26 | +| 5.2.8.3 | Audio media profiles ..... | 27 | +| 5.2.8.4 | Subtitle media profiles ..... | 27 | +| 5.2.8.5 | Encryption mode discovery ..... | 28 | +| 5.3 | Uplink streaming default profile ..... | 28 | +| 5.3.1 | Introduction ..... | 28 | +| 5.3.2 | Video encoding..... | 28 | +| 5.3.3 | Audio encoding ..... | 28 | +| 5.3.4 | Speech encoding..... | 28 | +| 5.3.5 | Encapsulation ..... | 28 | +| 5.3.5.1 | Introduction..... | 28 | +| 5.3.5.2 | Video media profile ..... | 29 | +| 5.3.5.3 | Speech media profile ..... | 29 | +| 5.3.5.4 | Audio media profile ..... | 29 | +| 5.4 | Television (TV) profile ..... | 29 | +| 5.4.1 | Video decoding..... | 29 | +| 5.4.1.1 | H.264 (AVC) ..... | 29 | +| 5.4.1.2 | H.265 (HEVC) ..... | 29 | +| 5.4.2 | Audio decoding ..... | 30 | +| 5.4.3 | Subtitle decoding..... | 30 | +| 5.4.4 | Decapsulation and decryption ..... | 30 | +| 5.4.4.1 | Introduction..... | 30 | +| 5.4.4.2 | Video media profiles..... | 30 | +| 5.4.4.3 | Audio media profiles ..... | 31 | +| 5.4.4.4 | Subtitle media profiles ..... | 31 | +| 5.4.4.5 | Encrypted content ..... | 31 | +| 5.4.5 | Capability discovery ..... | 32 | +| 5.5 | Downlink 360 Virtual Reality (VR) profile ..... | 32 | +| 5.5.1 | Video ..... | 32 | +| 5.5.1.1 | Operation Points ..... | 32 | +| 5.5.1.2 | DASH encapsulation..... | 32 | +| 5.5.2 | Audio ..... | 32 | +| 5.5.2.1 | Operation Points ..... | 32 | +| 5.5.2.2 | DASH encapsulation..... | 33 | +| 5.6 | Uplink 360 Virtual Reality (VR) profile ..... | 33 | +| 5.6.1 | Video ..... | 33 | +| 5.6.1.1 | Operation Points ..... | 33 | +| 5.6.1.2 | Encapsulation..... | 33 | +| 5.6.2 | Audio ..... | 33 | +| 5.6.2.1 | Operation Points ..... | 33 | +| 5.6.2.2 | Encapsulation..... | 33 | +| Annex A (informative): | Change history..... | 34 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document specifies the profiles, codecs and formats for 5G Media Streaming (5GMS) services based on the 5G Media Streaming Architecture (5GMSA) including both unicast downlink and unicast uplink. The codec and format recommendations defined for each profile apply to the 5GMSd Client components in the User Equipment (UE) as well as the Media Application Server (AS). Profiles are defined to address specific service scenarios. A default profile is defined in the case no other profile is claimed to be supported. 5G Media Streaming protocols and formats are defined based on the Common Media Application Format (CMAF). + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-T Recommendation H.264 (06/2019): "Advanced video coding for generic audiovisual services". +- [3] ITU-T Recommendation H.265 (02/2018): "High efficiency video coding". +- [4] 3GPP TS 26.117: "5G Media Streaming (5GMS); Speech and audio profiles". +- [5] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture". +- [6] 3GPP TS 26.307: "Presentation Layer for 3GPP Services". +- [7] ISO/IEC 23000-19: "Information Technology Multimedia Application Format (MPEG-A) – Part 19: Common Media Application Format (CMAF) for segmented media". +- [8] ISO/IEC 23001-7: "MPEG systems technologies - Part 7: Common encryption in ISO base media file format files". +- [9] CTA-5003: "Web Application Video Ecosystem (WAVE): Device Playback Capabilities Specification", available at . +- [10] 3GPP TS 26.512: " 5G Media Streaming (5GMS); Protocols". +- [11] IETF RFC 6381: The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types. +- [12] 3GPP TS 26.116: "Television (TV) over 3GPP Services; Video Profiles". +- [13] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications". +- [14] ISO/IEC 14496-12: "Information technology - Coding of audio-visual objects -Part 12: ISO base media file format". +- [15] ISO/IEC 14496-15: "Information technology - Coding of audio-visual objects - Part 15: Carriage of network abstraction layer (NAL) unit structured video in the ISO base media file format". +- [16] W3C IMSC1.1: "TTML Profiles for Internet Media Subtitles and Captions 1.1", available at . + +- [17] ISO/IEC 14496-30: "Information technology - Coding of audio-visual objects - Part 30: Timed text and other visual overlays in ISO base media file format". +- [18] W3C Media Capabilities: "Media Capabilities", available at +- [19] CTA-5000-B: " Web Application Video Ecosystem - Web Media API Snapshot 2019", available at [https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-b-final\\_v2.pdf](https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-b-final_v2.pdf). +- [20] ISO/IEC 23009-1: "Information Technology - Dynamic Adaptive Streaming Over HTTP (DASH) - Part 1: Media Presentation Description and Segment Formats". +- [21] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [22] IETF RFC 8216: "HTTP Live Streaming". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**5GMS Profile:** a set of UE capability requirements associated to a media-centric service scenario. + +**HD-HDR:** the capability of a UE to present video signals with all the following: at least Full-HD resolution, bit depth of at least 10, at least 60 frames per second, Wide Colour Gamut and High Dynamic Range. + +**MPEG-H:** It is a group of international standards under development by the ISO/IEC Moving Picture Experts Group (MPEG) - formally known as ISO/IEC 23008 - High efficiency coding and media delivery in heterogeneous environments + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|----------------------------------------| +| 5GMS | 5G Media Streaming | +| 5GMSA | 5G Media Streaming Architecture | +| AMR | Adaptive Multi Rate | +| AMR-WB | Adaptive Multi Rate – Wide Band | +| API | Application Programming Interface | +| AS | Application Server | +| AVC | Advanced Video Coding | +| AVC-HD | Advanced Video Codec – High Definition | +| CMAF | Common Media Application Format | +| DASH | Dynamic Adaptive Streaming over HTTP | +| EVS | Enhanced Voice Services | +| HD | High Definition | +| HDR | High Dynamic Range | +| HD-HDR | High Definition and High Dynamic Range | +| HEVC | High Efficiency Video Coding | + +| | | +|------|------------------------------------------| +| HLG | Hybrid Log-Gamma | +| HLS | HTTP Live Streaming | +| IMSC | Internet Media Subtitles and Captions | +| MPEG | Moving Picture Experts Group | +| OMAF | Omnidirectional Media Application Format | +| PSS | Packet-switched Streaming Service | +| TTML | Timed Text Markup Language | +| TV | Television | +| UE | User Equipment | +| UHD | Ultra High Definition | +| VR | Virtual Reality | +| VCL | Video Coding Layer | + +# 3A Overview + +## 3A.1 Introduction + +This specification defines profiles, codecs and formats for 5G Media Streaming. In this clause, the connection to 5G Media Streaming Architecture in TS 26.501 [5] is introduced. + +## 3A.2 Codecs and Formats in Downlink Media Streaming + +### 3A.2.1 Architecture, Interfaces and APIs + +According to TS 26.501 [5], Downlink Media Streaming provides the ability for content to be distributed using procedures and protocols defined by 5G Media Streaming as shown in Figure 3A.2.1-1. The detailed procedures for the interfaces and APIs for 5G Media Streaming are defined in TS 26.512 [10]. + +![Figure 3A.2.1-1: Downlink 5G Media Streaming architecture diagram. The diagram shows the interaction between a User Equipment (UE) and a 5GMSd Application Provider. Inside the UE, there is a 5GMSd-Aware Application, a 5GMSd Client, and a Media Player. The 5GMSd Client contains a Media Session Handler and an Access Client. The Media Player contains a Media Playback and Content Decryption Platform (TS 26.511) and an Access Client. Interfaces are labeled M1d, M2d, M4d, M5d, M6d, M7d, and M8d. The 5GMSd AF (Application Function) and 5GMSd AS (Application Server) are shown between the UE and the 5GMSd Application Provider. The 5GMSd AS contains a Manifest Server and a CMAF Segment Server.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +``` + +graph LR + subgraph UE + subgraph 5GMSd_Aware_Application [5GMSd-Aware Application] + M8d((M8d)) + end + subgraph 5GMSd_Client [5GMSd Client] + M6d1((M6d)) + Media_Session_Handler[Media Session Handler] + M6d2((M6d)) + M7d1((M7d)) + M7d2((M7d)) + end + subgraph Media_Player [Media Player] + subgraph Playback_Platform [Media Playback and Content Decryption Platform TS 26.511] + Cap[Capabilities] + Play[Playback] + Status[Status] + Sub[Subscriptions and Notifications] + end + subgraph Access_Client [Access Client] + M4d((M4d)) + end + Playback_Platform -- Cap --> Access_Client + Playback_Platform -- Play --> Access_Client + Playback_Platform -- Status --> Access_Client + Playback_Platform -- Sub --> Access_Client + end + 5GMSd_Aware_Application -- M8d --> 5GMSd_AF + 5GMSd_Aware_Application -- M6d1 --> Media_Session_Handler + Media_Session_Handler -- M5d --> 5GMSd_AF + Media_Session_Handler -- M6d2 --> Media_Player + Media_Player -- M7d1 --> 5GMSd_AF + Media_Player -- M7d2 --> Media_Session_Handler + Media_Player -- M4d --> 5GMSd_AS + end + 5GMSd_AF -- M1d --> 5GMSd_Application_Provider + 5GMSd_AS -- M2d --> 5GMSd_Application_Provider + subgraph 5GMSd_AF [5GMSd AF] + end + subgraph 5GMSd_AS [5GMSd AS] + Manifest_Server[Manifest Server] + CMAF_Segment_Server[CMAF Segment Server] + end + subgraph 5GMSd_Application_Provider [5GMSd Application Provider] + end + +``` + +Figure 3A.2.1-1: Downlink 5G Media Streaming architecture diagram. The diagram shows the interaction between a User Equipment (UE) and a 5GMSd Application Provider. Inside the UE, there is a 5GMSd-Aware Application, a 5GMSd Client, and a Media Player. The 5GMSd Client contains a Media Session Handler and an Access Client. The Media Player contains a Media Playback and Content Decryption Platform (TS 26.511) and an Access Client. Interfaces are labeled M1d, M2d, M4d, M5d, M6d, M7d, and M8d. The 5GMSd AF (Application Function) and 5GMSd AS (Application Server) are shown between the UE and the 5GMSd Application Provider. The 5GMSd AS contains a Manifest Server and a CMAF Segment Server. + +Figure 3A.2.1-1: Downlink 5G Media Streaming architecture + +The present document primarily deals with the segment formats delivered on M4d and the requirements applicable to the media playback platform and content decryption module. According to Figure 3A.2.1-1, the Access Client in the 5GMSd Client uses the manifest, typically the Media Presentation Description (MPD) for Dynamic Streaming over HTTP (DASH) as defined in ISO/IEC 23009-1 [20] and TS 26.247 [21] or the Master Playlist for HTTP Live Streaming (HLS) as defined in IETF RFC 8216 [22] to download Segments to initiate a media playback session. A 5GMSd Application Provider may publish these segments directly through M2d such that the 5GMSd AS acts as a hosting server but does not require the media to be either transcoded or repackaged. Using these unified formats maximizes cacheability and improves general Content Delivery Network (CDN) operations, including usage of secure transport protocols such as HTTPS on interface M4d. + +5G Media Streaming segment formats are defined based on the Common Media Application Format (CMAF) as specified in ISO/IEC 23000-19 [7]. By using this format, 5G Media Streaming is compatible with a broad set of segment-based streaming protocols including Dynamic Streaming over HTTP (DASH) and HTTP Live Streaming (HLS). For example, ISO/IEC 23009-1 [20] defines a detailed DASH profile for delivering CMAF content within a DASH Media Presentation using a converged format for segmented media content. + +Readers of the present document are encouraged to familiarize themselves with terms defined in CMAF such as CMAF Headers, CMAF Fragments, CMAF Tracks and CMAF Switching Sets. CMAF defines a content model for adaptive playback of segmented media (enabling seamless switching across tracks encoded from the same media) and late binding of tracks from different media types, associated with the same presentation. CMAF also defines a content protection and encryption framework for multi-DRM support based on ISO/IEC 23001-7 [8]. Furthermore, CMAF defines media profiles, i.e. encoding constraints on a CMAF track and its contained media samples associated with a specific codec. This specification only uses the structural constraints of CMAF as defined in clause 7 of ISO/IEC 23000-19 [7] and in clause 8 of ISO/IEC 23000-19 [7] for encrypted content. Specific 5GMS media profiles for video, audio and subtitles based on the general constraints of ISO/IEC 23000-19 [7], clauses 9, 10 and 11, respectively, are defined in the present document. However, Downlink Media Streaming is not restricted to the media profiles defined in the present document: any codec that defines a CMAF media profile may be used and distributed with Downlink Media Streaming. + +### 3A.2.2 Hypothetical Device Playback Model + +The media playback platform is initiated and used by the Access Client to create a streaming session and experience. The Access Client itself handles the download of segmented media content via interface M4d. This specification is based on a hypothetical playback model that permits an 5GMSd-Aware Application and/or a media Access Client to play back segmented media content streamed via 5G Media Streaming for downlink. Playback receiver requirements for CMAF content are defined in the CTA WAVE Device Playback Specification [9] documenting how an Access Client can use manifest information for establishing and performing playback of CMAF content based on a CMAF Reference Player model. + +Following the details in Figure 3A.2-1, playback functionalities include: + +- 1) Querying the capabilities of the device to determine if it supports the playback of a specific media profile. Different means exist and are described in CTA-5003 [9], but minimally a well-defined MIME type and a well-defined `codecs` parameter following the requirements in RFC 6381 [11] is needed. +- 2) Initializing the playback platform with the codec by providing appropriate initialization information. At minimum, a CMAF Header is needed for initializing the decoder. Initialization of content decryption, if needed, depends on the used DRM system. +- 3) Playback itself, by appending data to source and track buffers and providing additional instructions such as seek, accelerated playback, random access, etc +- 4) The ability to check the status of the playback platform, for example the size and duration of the media buffers, current playback time, etc. Relevant APIs exposed by the 5GMSd Client via M7d are defined in TS 26.512 [21]. +- 5) The ability to receive notifications and and error events from the playback platform, for example non-conforming content, buffer unde-runs, etc. Relevant APIs exposed by the 5GMSd Client via M7d are defined in TS 26.512 [21]. + +### 3A.2.3 Necessary Conditions for Codecs and Formats in 5GMSd + +In order to use a media codec or a specific media profile of the codec in the context of 5G Media Streaming, the following aspects need to be defined: + +- A CMAF media profile definition with all the requirements according to ISO/IEC 23000-19 [7] for a media profile. +- A definition of how capability discovery can be done, at the minimum a suitable and well-defined MIME type following the requirements in RFC 6381 [11], and in particular the definition of the `codecs` and `profiles` parameters. +- The mapping of media profile parameters to a DASH MPD. The mapping includes the static information (i.e. fixed parameters in the MPD) and dynamic information (e.g., depending on information in the CMAF Header). +- Potential requirements and restrictions for encrypted content. + +This specification defines the above information for several media codecs in clause 4, and provides requirements and recommendations for the support of these media profiles in specific 5G Media Streaming profiles in clause 5. + +NOTE: Downlink Media Streaming is not restricted to the media profiles defined in this specification: any CMAF media profile may be used and distributed within Downlink Media Streaming as long as it can be used with APIs and interfaces defined in TS 26.512 [21] and the above information is provided. + +## 3A.3 Codecs and Formats in Uplink Media Streaming + +Codecs and formats for uplink streaming are defined in the remainder of this specification. + +# --- 4 5GMS codecs and formats capabilities + +## 4.1 Introduction + +This clause defines codecs and formats capabilities for video, audio, speech and subtitles for 5G Media Streaming. + +For each media type, decoding and encoding capabilities are defined. These capabilities are a combination of codecs, profiles, tiers (if applicable), levels and format restrictions. In order to use the codecs in 5G Media Streaming for each capability the following functionalities are defined: + +- Mapping to the ISO Base Media File Format defining a track format. +- The definition of a CMAF Track +- The definition of a CMAF Switching Set and the media profile +- The playback requirements for this media profile +- The content generation requirements for this media profile + +## 4.2 Video + +### 4.2.1 H.264 (AVC) + +#### 4.2.1.1 Decoding + +The following H.264 (AVC) media decoding capabilities are defined: + +- **AVC-HD-Dec:** the capability to decode H.264 (AVC) Progressive High Profile Level 3.1 [2] bitstreams, for which the maximum VCL Bit Rate is constrained to be 14 Mbps with `cpbBrVclFactor` and `cpbBrNalFactor` being fixed to be 1,000 and 1,200, respectively. +- **AVC-FullHD-Dec:** the capability to decode H.264 (AVC) Progressive High Profile Level 4.0 [2] bitstreams. +- **AVC-UHD-Dec:** the capability to decode H.264/AVC Progressive High Profile Level 5.1 [2] bitstreams for H.264/AVC with the following additional restrictions and requirements: + - the maximum VCL Bit Rate is constrained to be 120 Mbps with `cpbBrVclFactor` and `cpbBrNalFactor` being fixed to be 1250 and 1500, respectively. + - the bitstream does not contain more than 10 slices per picture. + +NOTE: High Profile for H.264/AVC excludes Flexible macro-block order, Arbitrary slice ordering, Redundant slices, Data partition. + +#### 4.2.1.2 Encoding + +The following H.264 (AVC) media encoding capabilities are defined: + +- **AVC-HD-Enc:** the capability to encode a video signal with: + +- up to 108,000 macroblocks per second; +- up to a frame size of 3,600 macroblocks; +- up to 120 frames per second; +- the chroma format being 4:2:0; and +- the bit depth being 8 bit; + +to a bitstream that is decodable by a decoder that is **AVC-HD-Dec** capable as defined in clause 4.2.1.1. + +- **AVC-FullHD-Enc:** the capability to encode a video signal with: + +- up to 245,760 macroblocks per second; +- up to a frame size of 8,192 macroblocks; +- up to 240 frames per second; +- the chroma format being 4:2:0; and +- the bit depth being 8 bit; + +to a bitstream that is decodable by a decoder that is **AVC-FullHD-Dec** capable as defined in clause 4.2.1.1. + +- **AVC-UHD-Enc:** the capability to encode a video signal with: + +- up to 983,040 macroblocks per second; +- up to a frame size of 36,864 macroblocks; +- up to 480 frames per second; +- the chroma format being 4:2:0; and +- the bit depth being 8 bit; + +to a bitstream that is decodable by a decoder that is **AVC-UHD-Dec** capable as defined in clause 4.2.1.1. + +#### 4.2.1.3 Media Profiles: Mapping to 5GMS Delivery + +##### 4.2.1.3.1 AVC-HD + +###### 4.2.1.3.1.1 ISO BMFF File Format + +If AVC-HD media is provided in a bitstream that is decodable by a decoder capable of the **AVC-HD-Dec** decoding capabilities as defined in clause 4.2.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'avc1' or 'avc3' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.1.3.1.2 CMAF Track Definition + +If AVC-HD media is provided in an CMAF track, then the CMAF track shall conform with: + +- the requirements of the ISO BMFF File format track defined in clause 4.2.1.3.1.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; +- the general video track constraints defined in ISO/IEC 23000-19; clause 9. + +###### 4.2.1.3.1.3 CMAF Switching Set Definition + +If AVC-HD media is provided in an CMAF Switching Set; then + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.1.3.1.2; +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [7], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7]; clause 9. + +###### 4.2.1.3.1.4 Playback Requirements + +For a receiver supporting the AVC-HD media profile the following applies: + +- It shall support the **AVC-HD-Dec** decoding capabilities as defined in clause 4.2.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.3.1.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.3.1.3 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +###### 4.2.1.3.1.5 Content Generation Requirements + +For a transmitter supporting the AVC-HD media profile the following applies: + +- It shall support the **AVC-HD-Enc** encoding capabilities as defined in clause 4.2.1.2. +- It shall support the generation of a CMAF Track that conforms to the requirements in clause 4.2.1.3.1.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 4.2.1.3.1.3. + +##### 4.2.1.3.2 AVC-FullHD + +###### 4.2.1.3.2.1 ISO BMFF File Format + +If AVC-FullHD media is provided in a bitstream that is decodable by a decoder capable of the **AVC-FullHD-Dec** decoding capabilities as defined in clause 4.2.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'avc1' or 'avc3' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.1.3.2.2 CMAF Track Definition + +If AVC-FullHD media is provided in an CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.2.1.3.2.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; and +- the general video track constraints defined in ISO/IEC 23000-19, clause 9. + +###### 4.2.1.3.2.3 CMAF Switching Set Definition + +If AVC-FullHD media is provided in an CMAF Switching Set, then: + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.1.3.2.2; +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [27], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7], clause 9. + +###### 4.2.1.3.2.4 Playback Requirements + +For a receiver supporting the AVC-FullHD media profile the following applies: + +- It shall support the **AVC-FullHD-Dec** decoding capabilities as defined in clause 4.2.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.3.2.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.3.2.3 namely: + +- 8.9 Out-Of-Order Loading +- 8.10 Overlapping Fragments +- 8.12 Playback of Encrypted Content + +###### 4.2.1.3.2.5 Content Generation Requirements + +For a transmitter supporting the AVC-FullHD media profile the following applies: + +- It shall support the **AVC-FullHD-Enc** encoding capabilities as defined in clause 4.2.1.2. +- It shall support the generation of a CMAF Track that conforms to the requirements in clause 4.2.1.3.2.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 4.2.1.3.2.3. + +##### 4.2.1.3.3 AVC-UHD + +###### 4.2.1.3.3.1 ISO BMFF File Format + +If AVC-UHD media is provided in a bitstream that is decodable by a decoder capable of the **AVC-UHD-Dec** decoding capabilities as defined in clause 4.2.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'avc1' or 'avc3' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.1.3.3.2 CMAF Track Definition + +If AVC-UHD media is provided in an CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.2.1.3.3.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; and +- the general video track constraints defined in ISO/IEC 23000-19, clause 9. + +###### 4.2.1.3.3.3 CMAF Switching Set Definition + +If AVC-UHD media is provided in an CMAF Switching Set, then + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.1.3.3.2; +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [27], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7], clause 9. + +###### 4.2.1.3.3.4 Playback Requirements + +For a receiver supporting the AVC-UHD media profile the following applies: + +- It shall support the **AVC-UHD-Dec** decoding capabilities as defined in clause 4.2.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.3.3.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + +- 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.3.3.3 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +###### 4.2.1.3.3.5 Content Generation Requirements + +For a transmitter supporting the AVC-UHD media profile the following applies: + +- It shall support the AVC-UHD-Enc encoding capabilities as defined in clause 4.2.1.2. +- It shall support the generation of a CMAF Track that conforms to the requirements in clause 4.2.1.3.3.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 4.2.1.3.3.3. + +### 4.2.2 H.265 (HEVC) + +#### 4.2.2.1 Decoding + +The following H.265 (HEVC) media decoding capabilities are defined: + +- **HEVC-HD-Dec:** the capability to decode H.265 (HEVC) Main Profile, Main Tier, Level 3.1[3] bitstreams that have general\_progressive\_source\_flag equal to 1, general\_interlaced\_source\_flag equal to 0, general\_non\_packed\_constraint\_flag equal to 1, and general\_frame\_only\_constraint\_flag equal to 1. +- **HEVC-FullHD-Dec:** the capability to decode H.265 (HEVC) Main10 Profile, Main Tier, Level 4.1[3] bitstreams that have general\_progressive\_source\_flag equal to 1, general\_interlaced\_source\_flag equal to 0, general\_non\_packed\_constraint\_flag equal to 1, and general\_frame\_only\_constraint\_flag equal to 1. +- **HEVC-UHD-Dec:** the capability to decode H.265 (HEVC) Main10 Profile, Main Tier, Level 5.1[3] bitstreams that have general\_progressive\_source\_flag equal to 1, general\_interlaced\_source\_flag equal to 0, general\_non\_packed\_constraint\_flag equal to 1, and general\_frame\_only\_constraint\_flag equal to 1. +- **HEVC-8K-Dec:** the capability to decode H.265 (HEVC) Main10 Profile, Main Tier, Level 6.1[3] bitstreams that have general\_progressive\_source\_flag equal to 1, general\_interlaced\_source\_flag equal to 0, general\_non\_packed\_constraint\_flag equal to 1, and general\_frame\_only\_constraint\_flag equal to 1 with the following further limitations: + - the bitstream does not exceed the maximum luma picture size in samples of 33,554,432, + - the maximum VCL Bit Rate is constrained to be 80 Mbps with CpbVclFactor and CpbNalFactor being fixed to be 1000 and 1100, respectively. + +#### 4.2.2.2 Encoding + +The following H.265 (HEVC) media encoding capabilities are defined: + +- **HEVC-HD-Enc:** the capability to encode a video signal with + - up to 33,177,600 luma samples per second; + - up to a luma picture size of 983,040 samples; + - up to 120 frames per second; + +- the Chroma format being 4:2:0; and + - the bit depth being 8 bit; +- to a bitstream that is decodable by a decoder that is **HEVC-HD-Dec** capable as defined in clause 4.2.2.1. +- **HEVC-FullIHD-Enc**: the capability to encode a video signal with + - up to 133,693,440 luma samples per second; + - up to a luma picture size of 2,228,224 samples; + - up to 240 frames per second; + - the Chroma format being 4:2:0; and + - the bit depth being either 8 or 10 bit;to a bitstream that is decodable by a decoder that is **HEVC-FullIHD-Dec** capable as defined in clause 4.2.2.1. + - **HEVC-UHD-Enc**: the capability to encode a video signal with + - up to 534,773,760 luma samples per second; + - up to a luma picture size of 8,912,896 samples; + - up to 480 frames per second; + - the Chroma format being 4:2:0; and + - the bit depth being either 8 or 10 bit;to a bitstream that is decodable by a decoder that is **HEVC-UHD-Dec** capable as defined in clause 4.2.2.1. + +#### 4.2.2.3 Media Profiles: Mapping to 5G Media Streaming + +##### 4.2.2.3.1 HEVC-HD + +###### 4.2.2.3.1.1 ISO BMFF File Format + +If HEVC-HD media is provided in a bitstream that is decodable by a decoder capable of the **HEVC-HD-Dec** decoding capabilities as defined in clause 4.2.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'hvc1' or 'hev1' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.2.3.1.2 CMAF Track Definition + +If HEVC-HD media is provided in an CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.2.2.3.1.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; and +- the general video track constraints defined in ISO/IEC 23000-19; clause 9. + +###### 4.2.2.3.1.3 CMAF Switching Set Definition + +If HEVC-HD media is provided in an CMAF Switching Set, then + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.2.3.1.2; +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [27], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7], clause 9. + +###### 4.2.2.3.1.4 Playback Requirements + +For a receiver supporting the HEVC-HD media profile the following applies: + +- It shall support the **HEVC-HD-Dec** decoding capabilities as defined in clause 4.2.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.1.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.1.3 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +###### 4.2.2.3.1.5 Content Generation Requirements + +For a transmitter supporting the **HEVC-HD** media profile the following applies: + +- It shall support the HEVC-HD-Enc encoding capabilities as defined in clause 4.2.2.2. +- It shall support the generation of a CMAF Track that conforms to the requirements in clause 4.2.2.3.1.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 4.2.2.3.1.3. + +##### 4.2.2.3.2 HEVC-FullHD + +###### 4.2.2.3.2.1 ISO BMFF File Format + +If HEVC-FullHD media is provided in a bitstream that is decodable by a decoder capable of the **HEVC-FullHD-Dec** decoding capabilities as defined in clause 4.2.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'hvc1' or 'hev1' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.2.3.2.2 CMAF Track Definition + +If HEVC-FullHD media is provided in an CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.2.2.3.2.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; and +- the general video track constraints defined in ISO/IEC 23000-19, clause 9. + +###### 4.2.2.3.2.3 CMAF Switching Set Definition + +If HEVC-FullHD media is provided in an CMAF Switching Set, then + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.2.3.2.2, +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [27], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7], clause 9. + +###### 4.2.2.3.2.4 Playback Requirements + +For a receiver supporting the HEVC-FullHD media profile the following applies: + +- It shall support the **HEVC-FullHD-Dec** decoding capabilities as defined in clause 4.2.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.2.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.2.3 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +###### 4.2.2.3.2.5 Content Generation Requirements + +For a transmitter supporting the HEVC-FullHD media profile the following applies: + +- It shall support the **HEVC-FullHD-Enc** encoding capabilities as defined in clause 4.2.2.2. +- It shall support the generation of a CMAF Track that conforms to the requirements in clause 4.2.2.3.2.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 4.2.2.3.2.3. + +##### 4.2.2.3.3 HEVC-UHD + +###### 4.2.2.3.3.1 ISO BMFF File Format + +If HEVC-UHD media is provided in a bitstream that is decodable by a decoder capable of the **HEVC-UHD-Dec** decoding capabilities as defined in clause 4.2.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'hvc1' or 'hev1' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.2.3.3.2 CMAF Track Definition + +If HEVC-UHD media is provided in an CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.2.2.3.3.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; and + +- the general video track constraints defined in ISO/IEC 23000-19, clause 9. + +###### 4.2.2.3.3.3 CMAF Switching Set Definition + +If HEVC-UHD media is provided in an CMAF Switching Set, then + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.2.3.3.2; +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [27], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7], clause 9. + +###### 4.2.2.3.3.4 Playback Requirements + +For a receiver supporting the HEVC-UHD media profile the following applies: + +- It shall support the **HEVC-UHD-Dec** decoding capabilities as defined in clause 4.2.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.3.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.3.3 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +###### 4.2.2.3.3.5 Content Generation Requirements + +For a transmitter supporting the HEVC-UHD media profile the following applies: + +- It shall support the **HEVC-UHD-Enc** encoding capabilities as defined in clause 4.2.2.2. +- It shall support the generation of a CMAF Track that conforms to the requirements in clause 4.2.2.3.3.2. +- If used for Adaptive Bit Rate (ABR) distribution, it shall support the generation of a CMAF Switching Set as defined in clause 4.2.2.3.3.3. + +##### 4.2.2.3.4 HEVC-8K + +###### 4.2.2.3.4.1 ISO BMFF File Format + +If HEVC-8K media is provided in a bitstream that is decodable by a decoder capable of the **HEVC-8K-Dec** decoding capabilities as defined in clause 4.2.2.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'hvc1' or 'hev1' as defined in ISO/IEC 14496-15 [15]. + +###### 4.2.2.3.4.2 CMAF Track Definition + +If HEVC-UHD media is provided in a CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.2.2.3.4.1; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7, and +- the general video track constraints defined in ISO/IEC 23000-19, clause 9. + +###### 4.2.2.3.4.3 CMAF Switching Set Definition + +If HEVC-UHD media is provided in a CMAF Switching Set, then + +- every CMAF track in the CMAF Switching Set shall conform with the requirements of CMAF Track in clause 4.2.2.3.4.2; +- the general CMAF Switching Set constraints in ISO/IEC 23000-19 [27], clause 7; and +- the general CMAF video track Switching Set constraints defined in ISO/IEC 23000-19 [7], clause 9. + +###### 4.2.2.3.4.4 Playback Requirements + +For a receiver supporting the HEVC-UHD media profile the following applies: + +- It shall support the **HEVC-8K-Dec** decoding capabilities as defined in clause 4.2.2.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.4.3 namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time + - 8.5 Switching Set Playback + - 8.6 Regular Playback of Chunked Content + - 8.7 Regular Playback of Chunked Content, non-aligned append +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.2.3.4.3 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +## 4.3 Audio + +### 4.3.1 Decoding + +Audio decoding capabilities are defined in 3GPP TS 26.117 [4] clause 5.3. + +### 4.3.2 Encoding + +Audio encoding capabilities are defined in 3GPP TS 26.117 [4] clause 5.3. + +## 4.4 Speech + +### 4.4.1 Decoding + +Speech decoding capabilities are defined in 3GPP TS 26.117 [4] clause 5.2. + +### 4.4.2 Encoding + +Speech encoding capabilities are defined in 3GPP TS 26.117 [4] clause 5.3.4.5. + +## 4.5 Subtitles + +### 4.5.1 IMSC1.1. Text Track + +#### 4.5.1.1 Decoding Capability + +The IMSC1.1. Text Track decoding capability is defined as IMSC1.1-TEXT-DEC. Support for IMSC1.1-TEXT-DEC requires the support of an IMSC1.1 text processor as defined in W3C IMSC1.1 [16]. + +#### 4.5.1.2 ISO BMFF File Format + +If an IMSC1.1 Text Track is provided in a bitstream that is decodable by a decoder capable of the IMSC1.1-TEXT-DEC decoding capabilities as defined in clause 4.5.1.1 and the media is encapsulated in an ISO BMFF Track [14], then the file format track shall conform with the requirements of the codec entry 'imt2' as defined in ISO/IEC 14496-30 [17]. + +#### 4.5.1.3 CMAF Track Definition + +If IMSC1.1-TEXT-DEC media is provided in an CMAF track, then the CMAF track shall conform with + +- the requirements of the ISO BMFF File format track defined in clause 4.5.1.2; +- the general CMAF Track constraints in ISO/IEC 23000-19, clause 7; +- the general subtitle track constraints defined in ISO/IEC 23000-19, clause 11; and +- the IMSC1.1. text track constraints defined in ISO/IEC 23000-19, Annex L.2. + +#### 4.5.1.4 CMAF Switching Set Definition + +If IMSC1.1-TEXT-DEC media is provided in an CMAF Switching Set, then: + +- only a single CMAF track according to the requirements in clause 4.5.1.3 shall be present. + +#### 4.5.1.5 Playback Requirements + +For a receiver supporting the IMSC1.1. Text Track media profile the following applies: + +- It shall support the IMSC1.1-TEXT-DEC decoding capabilities as defined in clause 4.5.1.1. +- It shall support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.5.1.4, namely: + - 8.2 Sequential Track Playback + - 8.3 Random Access to Fragment + - 8.4 Random Access to Time +- It should support the following playback requirements as documented in clause 8 of CTA-WAVE 5003 [9] for any content conforming to a CMAF Switching Set as defined in clause 4.2.1.4 namely: + - 8.9 Out-Of-Order Loading + - 8.10 Overlapping Fragments + - 8.12 Playback of Encrypted Content + +# --- 5 5GMS Profiles + +## 5.1 Introduction + +A 5GMS profile describes a set of capability requirements associated to a service scenario. A default profile is defined for minimum media requirements to be supported in case no other profile is claimed to be supported. The Television (TV) profile covers live and on demand streaming of audio-visual TV services. The Virtual Reality (VR) profile covers the live and on demand streaming of omnidirectional media including spherical video and 3D audio. + +## 5.2 Downlink streaming default profile + +### 5.2.1 Introduction + +This profile defines required capabilities for UE-based 5GMSd Client functionalities as defined in TS26.501 [5] and shown in Figure 4.2.2-1 in TS 26.501 [5]. Requirements for the following functions are defined in this clause: + +- Media Decapsulation +- Media Decryption +- Media Decoding +- Media Presentation and Rendering + +### 5.2.2 Video decoding + +If the 5GMSd Client supports the reception of video, then + +- **AVC-HD-Dec** decoding capability shall be supported as defined in clause 4.2.1.1. +- **HEVC-HD-Dec** decoding capability should be supported as defined in clause 4.2.2.1. + +If the 5GMSd Client supports the reception of video and HD-HDR capabilities, then: + +- **AVC-FullHD-Dec** decoding capability shall be supported as defined in clause 4.2.1.1. +- **HEVC-FullHD-Dec** decoding capability shall be supported as defined in clause 4.2.2.1. + +### 5.2.3 Audio decoding + +If the 5GMSd Client supports the reception of audio: + +- **xHE-AAC stereo** decoding capability should be supported as defined in 3GPP TS 26.117 [4] clause 5.2. + +NOTE: xHE-AAC® is a registered trademark of Fraunhofer in Germany and other countries and is used with Fraunhofer's permission. + +- **eAAC+** decoding capability shall be supported as defined in 3GPP TS 26.117 [4] clause 5.2. +- **AMR-WB+** decoding capability may be supported as defined in 3GPP TS 26.117 [4] clause 5.2. + +### 5.2.4 Speech decoding + +If the 5GMSd Client supports the reception of speech: + +- the **EVS** decoding capability shall be supported as defined in 3GPP TS 26.117 [4] clause 5.2. +- the **AMR-WB** decoding capability should be supported as defined in 3GPP TS 26.117 [4] clause 5.2. +- the **AMR** decoding capability may be supported as defined in 3GPP TS 26.117 [4] clause 5.2. + +### 5.2.5 Subtitles + +If the 5GMSd Client supports the reception of subtitles: + +- the IMSC1.1 Text Track decoding capabilities IMSC1.1-TEXT-DEC as defined in clause 4.5.1.1 should be supported. + +### 5.2.6 Presentation format + +If 5GMSd Client supports presentation, then 3GPP HTML5 Profile as defined in 3GPP TS 26.307 [6] should be supported. + +For a relevant set of media related APIs, please also take into account the Web Media API Snapshot 2019 (CTA-5000-B) [19]. + +### 5.2.7 Decapsulation and decryption + +#### 5.2.7.1 Introduction + +This clause defines the requirements in terms of decapsulation and decryption of media for a 5GMSd Media Player in combination with codecs. Media Encapsulation in 5G Media Streaming for downlink is defined based on the MPEG Common Media Application Format (CMAF) [7]. Based on this, this clause documents the requirements and recommendations for the support of media profiles by the definition of media player requirements. + +#### 5.2.7.2 Video media profiles + +If the 5GMSd Client supports the reception of video, then the following applies: + +- the AVC-HD playback requirements as defined in clause 4.2.1.3.1.4 shall be supported. +- the HEVC-HD playback requirements as defined in clause 4.2.2.3.1.4 should be supported. + +If the 5GMSd Client supports the reception of video and HD-HDR Capabilities, then the following applies: + +- the AVC-FullHD playback requirements as defined in clause 4.2.1.3.2.4 shall be supported. +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 shall be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 may be supported. + +#### 5.2.7.3 Speech media profiles + +If the 5GMSd Client supports the reception of speech, then the following shall be supported: + +- the **EVS** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.4.2.4. + +If the 5GMSd Client supports the reception of speech, then the following should be supported: + +- the **AMR-WB** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.3.2.4. + +If the 5GMSd Client supports the reception of speech, then the following may be supported: + +- the **AMR** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.2.2.4. + +#### 5.2.7.4 Audio media profiles + +If the 5GMSd Client supports the reception of audio, then the following should be supported: + +- the **xHE-AAC stereo** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.8.4. + +If the 5GMSd Client supports the reception of audio, then the following shall be supported: + +- the **eAAC+ stereo** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.6.2.4. + +If the 5GMSd Client supports the reception of audio, then the following may be supported: + +- the **AMR-WB+** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.7.2.4. + +#### 5.2.7.5 Subtitle media profiles + +If the 5GMSd Client supports the reception of subtitle, then the following should be supported: + +- the IMSC1.1 text track playback requirements as defined in clause 4.5.1.5. + +#### 5.2.7.6 Encrypted content + +If the 5GMSd Client supports encrypted content and any of the video playback requirement as defined in clause 5.2.7.2, then the 5GMSd client shall support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for either: + +- video content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; or +- video content encrypted according to [7] clause 8, using the 'cbcs' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 10.4, with the following restrictions Pattern Block length of 10 and an `encrypt:skip` pattern of 1:9 as defined in clause 9.6 of [8]. + +If the 5GMSd Client supports decrypted content and any of the video playback requirement in clause 5.2.7.2, then the 5GMSd client should support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for both: + +- video content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; and +- video content encrypted according to [7] clause 8, using the 'cbcs' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 10.4, with the following restrictions Pattern Block length of 10 and an `encrypt:skip` pattern of 1:9 as defined in clause 9.6 of [8]. + +If the 5GMSd Client supports encrypted content and any of the speech and audio playback requirement in clause 5.2.7.3 and clause 5.2.7.4, then the 5GMSd client shall support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for either: + +- audio content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; or +- audio content encrypted according to [7] clause 8, using the 'cbc1' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 9.7. + +If the 5GMSd client supports encrypted content and any of the speech and audio playback requirement in clause 5.2.7.3 and clause 5.2.7.4, then the 5GMSd client should support the playback requirements for encrypted content as documented in clause 8 of CTA-WAVE 5003 [9], clause 8.12 for both: + +- audio content encrypted according to [7] clause 8, using the 'cenc' AES-CTR subsample pattern encryption scheme, as specified in [8], clause 10.1; and +- audio content encrypted according to [7] clause 8, using the 'cbc1' AES-CBC subsample pattern encryption scheme, as specified in [8], clause 9.7. + +Any subtitle track, if present, should not be encrypted. + +### 5.2.8 Capability discovery + +#### 5.2.8.1 General + +A 5GMSd Client is expected to support capability discovery such that 5GMS-Aware Applications can identify if a specific media profile is supported. In order to identify whether a media profile is supported, the 5GMSd Client may provide an API as defined in TS 26.512 [10] via the M7d interface, for which the client can be queried with a specific MIME type string, if the media profile is supported. + +The MIME types follow RFC 6381 [11]. + +A 5GMSd Client should support at least one of the following capability discovery mechanisms for media profiles: + +- If `isTypeSupported()` for the media profile with argument `` results in a `yes`, then the respective media profile is supported with the requirements defined in a specific clause. +- If `isTypeSupported()` for the media profile with argument `` results in a `yes`, then the respective media profile is supported with the requirements defined in a specific clause. +- If a conforming CMAF header is provided for playback initialization and the 5GMSd Client does not throw an error response, then the respective media profile is supported with the requirements defined in a specific clause. + +For each media profile mentioned in clause 5.2.6, the `` parameter and the `` parameter are provided in the following. These parameters should be used in the capability exchange. + +#### 5.2.8.2 Video media profiles + +NOTE: In the following, "compatible" means either that the parameter is identical to the value specified or, if a different value is used for the parameter in a capability query, then it has the same positive result. + +For AVC-HD: + +- the `` parameter is compatible to `video/mp4 profiles='cmfc'` +- the `` parameter is compatible to either `'avc1.640028'` or `'avc3.640028'` + +For AVC-FullHD: + +- the `` parameter is compatible with `video/mp4 profiles='cmfc'` +- the `` parameter is compatible with either `'avc1.640029'` or `'avc3.640029'` + +For AVC-UHD: + +- the `` parameter is compatible with `video/mp4 profiles='cmfc'` +- the `` parameter is compatible with either `'avc1.640028'` or `'avc3.640028'` + +For HEVC-HD: + +- the `` parameter is compatible with `video/mp4 profiles='cmfc'` +- the `` parameter is compatible with either `'hvc1.1.2.L93.B0'` or `'hev1.1.2.L93.B0'` + +For HEVC-FullHD: + +- the `` parameter is compatible with `video/mp4 profiles='cmfc'` +- the `` parameter is compatible with either `'hvc1.2.4.L123.B0'` or `'hev1.2.4.L123.B0'` + +For HEVC-UHD: + +- the `` parameter is compatible with `video/mp4 profiles='cmfc'` +- the `` parameter is compatible with either `'hvc1.2.4.L153.B0'` or `'hev1.2.4.L153.B0'` + +#### 5.2.8.3 Audio media profiles + +For AMR: + +- the `` parameter is defined in TS 26.117, clause 7.2.2.4 as `audio/mp4 profiles='camr'` +- the `` parameter is defined in TS 26.117, clause 7.2.2.4 as `'samr'` + +For AMR-WB: + +- the `` parameter is defined in TS 26.117, clause 7.3.2.4 as `audio/mp4 profiles='camw'` +- the `` parameter is defined in TS 26.117, clause 7.3.2.4 as `'samw'` + +For EVS: + +- the `` parameter is defined in TS 26.117, clause 7.4.2.4 as `audio/mp4 profiles='cevs'` +- the `` parameter is defined in TS 26.117, clause 7.4.2.4 as `'sevs'` + +For xHE-AAC stereo: + +- the `` parameter is defined in TS 26.117, clause 7.8 as `audio/mp4 profiles='casu'` +- the `` parameter is defined in TS 26.117, clause 7.8 as `'mp4a'` + +For eAAC+ stereo: + +- the `` parameter is defined in TS 26.117, clause 7.6.2.4 as `audio/mp4 profiles='ceac'` +- the `` parameter is defined in TS 26.117, clause 7.6.2.4 as `'mp4a'` + +For AMR-WB+: + +- the `` parameter is defined in TS:26.117, clause 7.7.2.4 as `audio/mp4 profiles='camp'` +- the `` parameter is defined in TS:26.117, clause 7.7.2.4 as `'sawp'` + +#### 5.2.8.4 Subtitle media profiles + +For IMSC1.1 Text Tracks: + +- the parameter is defined in ISO/IEC 23000-19 [7], clause 11.3.3 as `application/mp4 profiles='im2t';` +- the parameter is defined in ISO/IEC 23000-19 [7], clause 11.3.3 as `'stpp.ttml.im2t'.` + +#### 5.2.8.5 Encryption mode discovery + +Encryption mode discovery will be studied in due course. + +## 5.3 Uplink streaming default profile + +### 5.3.1 Introduction + +This profile defines required capabilities for UE-based 5GMS Media Streamer functionalities as defined in TS 26.501[5] and shown in Figure 4.3.2-1 in TS 26.501 [5]. Requirements for the following functions are defined in this clause: + +- Media Encoding +- Media Upstream Client Encapsulation + +### 5.3.2 Video encoding + +If the 5GMS UE supports the transmission of video: + +- the real-time encoding capabilities for **HEVC-FullHD-Enc** as defined in clause 4.2.2.2 defined as the sender requirements for **HEVC-FullHD-Enc** Operation Point shall be supported. + +### 5.3.3 Audio encoding + +If the 5GMS UE supports the transmission of audio: + +- the sender requirements for the **eAAC+ stereo** Operation Point as defined in 3GPP TS 26.117 [4] clause 6.3.2.3 shall be supported. +- the sender requirements for the **xHE-AAC stereo** Operation Point as defined in 3GPP TS 26.117 [4] clause 6.3.4.3 should be supported. + +### 5.3.4 Speech encoding + +If the 5GMS UE supports the transmission of speech: + +- the sender requirements for the EVS Operation Point as defined in 3GPP TS 26.117 [4] clause 6.2.4.3 shall be supported; +- the sender requirements for the AMR-WB Operation Point as defined in 3GPP TS 26.117 [4] clause 6.2.3.3 should be supported; +- the sender requirements for the AMR Operation Point as defined in 3GPP TS 26.117 [4] clause 6.2.2.3 may be supported. + +### 5.3.5 Encapsulation + +#### 5.3.5.1 Introduction + +This clause defines the requirements in terms of encapsulation of media for a 5GMSu Media Streamer in combination with codecs. Media Encapsulation in 5G Media Streaming for uplink is defined based on the MPEG Common Media + +Application Format (CMAF) [7]. Based on this, this clause documents the requirements and recommendations for the support of media profiles by the definition of media streamer requirements. + +#### 5.3.5.2 Video media profile + +If the 5GMS UE supports the streaming of video, then the following shall be supported: + +- the content generation requirements for the HEVC-FullHD Media Profile as defined in clause 4.2.2.3.2.5; +- the sender requirements for the HEVC-FullHD Operation Point as defined in clause 5.3.2. + +#### 5.3.5.3 Speech media profile + +If the 5GMSu Client supports the transmission of speech, then the following shall be supported: + +- the EVS content generation requirements as defined in 3GPP TS 26.117 [4] clause 7.4.2.5. + +If the 5GMSu Client supports the transmission of speech, then the following should be supported: + +- the AMR-WB content generation requirements as defined in 3GPP TS 26.117 [4] clause 7.3.2.5. + +If the 5GMSu Client supports the transmission of speech, then the following may be supported: + +- the AMR content generation requirements as defined in 3GPP TS 26.117 [4] clause 7.2.2.5. + +#### 5.3.5.4 Audio media profile + +If the 5GMSu Client supports the transmission of audio, then the following shall be supported: + +- the eAAC+ stereo content generation requirements as defined in 3GPP TS 26.117 [4] clause 7.6.2.5. + +If the 5GMSu Client supports the transmission of audio, then the following should be supported: + +- the xHE-AAC stereo content generation requirements as defined in 3GPP TS 26.117 [4] clause 7.8.5. + +## 5.4 Television (TV) profile + +### 5.4.1 Video decoding + +#### 5.4.1.1 H.264 (AVC) + +If the 5GMSd Client supports the Television (TV) profile, it shall support the *H.264/AVC 720p HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.4.2.6. + +If the 5GMSd Client supports the Television (TV) profile, it should support the *H.264/AVC Full HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.4.3.6. + +#### 5.4.1.2 H.265 (HEVC) + +If the 5GMSd Client supports the Television (TV) profile, it should support: + +- *H.265/HEVC 720p HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.2.7; +- *H.265/HEVC Full HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.3.7; +- *H.265/HEVC UHD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.4.7; +- *H.265/HEVC Full HD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.5.8; +- *H.265/HEVC UHD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.6.8; + +- *H.265/HEVC Full HD HDR HLG* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.7.7; and +- *H.265/HEVC UHD HDR HLG* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.8.7. + +If the 5GMSd Client supports the Television (TV) profile, it may support: + +- *H.265/HEVC 8K UHD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.9.8. + +If the 5GMSd Client supports the Television (TV) profile and HD-HDR capabilities, it shall support: + +- *H.265/HEVC Full HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.3.7. + +### 5.4.2 Audio decoding + +If the 5GMSd Client supports the Television (TV) profile, it shall support *eAAC+ stereo* Operation point as defined in 3GPP TS 26. 117 [4], clause 6.3.2. + +If the 5GMSd Client supports the Television (TV) profile, it should support *xHE-AAC stereo* Operation point as defined in 3GPP TS 26. 117 [4], clause 6.3.4. + +### 5.4.3 Subtitle decoding + +If the 5GMSd Client supports the Television (TV) profile, it should support the **IMSC-1.1-TEXT-DEC** decoding capabilities as defined in clause 4.5.1.1. + +### 5.4.4 Decapsulation and decryption + +#### 5.4.4.1 Introduction + +This clause defines the requirements in terms of decapsulation and decryption of media for a Television (TV) Profile Media Player in combination with codecs. Media Encapsulation in 5G Media Streaming for downlink is defined based on the MPEG Common Media Application Format (CMAF) [7]. However, TS 26.116 [7] defines file format encapsulation and DASH Mapping in clause 5. + +This clause addresses decapsulation and decryption requirements in a sense that a 5GMSd Client supporting the Television (TV) profile requires to be able to process content that conforms to TS26.116 [7] encapsulation and CMAF encapsulation. + +The CMAF Track and Switching Set constraints in the present document and the Representation and Adaptation Set constraints in TS26.116 [7] are considered almost identical, but it still needs to be checked in detail. In the absence of both, it is expected that content offered for TV Profile receivers conform with both specifications. + +#### 5.4.4.2 Video media profiles + +If the 5GMSd client supports the Television (TV) profile, then the following applies: + +- the AVC-HD playback requirements as defined in clause 4.2.1.3.1.4 and the *H.264/AVC 720p HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.4.2.6 shall be supported. +- the AVC-FullHD playback requirements as defined in clause 4.2.1.3.1.4 and the *H.264/AVC Full HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.4.3.6 should be supported. +- the HEVC-HD playback requirements as defined in clause 4.2.2.3.1.4 and the *H.265/HEVC 720p HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.2.7 should be supported. +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the *H.265/HEVC Full HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.3.7 should be supported. + +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the *H.265/HEVC Full HD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.5.7 should be supported. +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the *H.265/HEVC Full HD HLG* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.7.7 should be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the *H.265/HEVC UHD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.4.7 may be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the *H.265/HEVC UHD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.5.7 may be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the *H.265/HEVC UHD HLG* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.8.7 may be supported. +- the HEVC-8K playback requirements as defined in clause 4.2.2.3.4.4 and *H.265/HEVC 8K UHD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.9.8 may be supported. + +If the 5GMSd Client supports the Television (TV) profile and HD-HDR capabilities, then the following applies: + +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the *H.265/HEVC Full HD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.3.7 shall be supported. +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the *H.265/HEVC Full HD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.5.7 shall be supported. +- the HEVC-FullHD playback requirements as defined in clause 4.2.2.3.2.4 and the *H.265/HEVC Full HD HLG* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.7.7 shall be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the *H.265/HEVC UHD* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.4.7 may be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and *the H.265/HEVC UHD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.5.7 may be supported. +- the HEVC-UHD playback requirements as defined in clause 4.2.2.3.3.4 and the *H.265/HEVC UHD HLG* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.8.7 may be supported. +- the HEVC-8K playback requirements as defined in clause 4.2.2.3.4.4 and *H.265/HEVC 8K UHD HDR* Operation Point Receiver requirements as specified in TS 26.116 [12], clause 4.5.9.8 may be supported. + +#### 5.4.4.3 Audio media profiles + +If the 5GMSd Client supports the Television (TV) profile, then the following shall be supported: + +- the **eAAC+ stereo** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.6.2.4. + +If the 5GMSd Client supports the Television (TV) profile, then the following should be supported: + +- the **xHE-AAC stereo** playback requirements as defined in 3GPP TS 26.117 [4] clause 7.8.4. + +#### 5.4.4.4 Subtitle media profiles + +If the 5GMSd Client supports the Television (TV) profile, then the following should be supported: + +- the **IMSC1.1 text track** playback requirements as defined in clause 4.5.1.5. + +#### 5.4.4.5 Encrypted content + +If the 5GMSd Client supports the Television (TV) profile the same requirements apply as in clause 5.2.7.6 for the default profile. + +### 5.4.5 Capability discovery + +If the 5GMSd Client supports the Television (TV) profile it is expected to support capability discovery such that 5GMS-aware applications can identify if a specific media profile is supported. + +The same requirements apply as in clause 5.2.8 for the default profile. + +A 5GMSd Client that supports the Television (TV) profile may support additional capability methods that permits to identify additional capabilities of media profile playback taking into account information provided in the MPD for TV Video Profiles. Examples include the W3C Media Capability APIs [18]. + +## 5.5 Downlink 360 Virtual Reality (VR) profile + +### 5.5.1 Video + +#### 5.5.1.1 Operation Points + +If the 5GMS UE supports 360 VR video, it shall include a receiver that complies with: + +- the *Basic H.264/AVC* Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.4. + +If the 5GMS UE supports 360 VR video, it should include a receiver that complies with: + +- the *Main H.265/HEVC* Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.5. + +If the 5GMS UE supports 360 VR video, it may include a receiver that complies with: + +- the *Flexible H.265/HEVC* Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.6. + +If the 5GMS UE supports 360 VR video, it may include a receiver that complies with: + +- the *H.265/HEVC 8K* Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.7 and the **HEVC-8K-Dec** decoding capabilities as defined in clause 4.2.2.1. + +#### 5.5.1.2 DASH encapsulation + +If the 5GMS UE supports 360 VR video for DASH services, it shall include a receiver that complies with: + +- the Basic Video Media Profile Receiver requirements for DASH as specified in TS 26.118 [13], clause 5.2.2.3. + +If the 5GMS UE supports 360 VR video for DASH services, it should include a receiver that complies with: + +- the Main Video Media Profile Receiver requirements for DASH as specified in TS 26.118 [13], clause 5.2.3.3. + +If the 5GMS UE supports 360 VR video for DASH services, it may include a receiver that complies with: + +- the Advanced Video Media Profile Receiver requirements for DASH as specified in TS 26.118 [13], clause 5.2.3.4. + +If the 5GMS UE supports 360 VR video, it may include a receiver that complies with: + +- the 8K Media Profile Receiver requirements for DASH as specified in TS 26.118 [13], clause 5.2.3.5 and the HEVC-8K playback requirements as defined in clause 4.2.2.3.4.4. + +### 5.5.2 Audio + +#### 5.5.2.1 Operation Points + +If the 5GMS UE supports 3D/VR audio, it should include a receiver that complies with: + +- the *3GPP MPEG-H Audio* Operation Point Receiver requirements as specified in TS 26.118 [13], clause 6.1.4. + +#### 5.5.2.2 DASH encapsulation + +If the 5GMS UE supports 3D/VR audio for DASH services, it should include a receiver that complies with: + +- the *OMAF 3D Audio Baseline* Media Profile Receiver requirements for file format signalling and encapsulation as specified in TS 26.118 [13], clause 6.2.2.3. + +## 5.6 Uplink 360 Virtual Reality (VR) profile + +### 5.6.1 Video + +#### 5.6.1.1 Operation Points + +If the 5GMS UE supports 360 VR video, it shall include an encoder that can encode a bitstream at a minimum of 1080p resolution 60 fps that can be decoded by a receiver that complies with: + +- the Basic H.264/AVC Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.4. + +If the 5GMS UE supports 360 VR video, it should include an encoder that can encode a bitstream at a minimum of 2160p resolution 60 fps that can be decoded by a receiver that complies with: + +- the Main H.265/HEVC Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.5. + +If the 5GMS UE supports 360 VR video, it may include an encoder that can encode a bitstream at a minimum of 2160p resolution 60 fps that can be decoded by a receiver that complies with: + +- the Flexible H.265/HEVC Operation Point Receiver requirements as specified in TS 26.118 [13], clause 5.1.6. + +#### 5.6.1.2 Encapsulation + +Media Encapsulation in 5G Media Streaming for uplink is defined based on the MPEG Common Media Application Format (CMAF) [7]. A sender shall at least support the generation of CMAF tracks. + +### 5.6.2 Audio + +#### 5.6.2.1 Operation Points + +If the 5GMS UE supports 3D/VR audio, it should include an encoder that can encode a bitstream that can be decoded by a receiver that complies with: + +- the 3GPP MPEG-H Audio Operation Point Receiver requirements as specified in TS 26.118 [13], clause 6.1.4. + +#### 5.6.2.2 Encapsulation + +Media Encapsulation in 5G Media Streaming for uplink is defined based on the MPEG Common Media Application Format (CMAF) [7]. A sender shall at least support the generation of CMAF tracks. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|------------------------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-12 | SA#86 | SP=19xxxx | | | | Presented to TSG SA#86 (for information) | 1.0.0 | +| 2020-01 | SA4#107 | S4-200314 | | | | Integration of S4-200033 and S4-200272 | 1.1.0 | +| 2020-04 | SA4#108-e | S4-200510 | | | | Integration of S4-AHI936 | 1.2.0 | +| 2020-04 | SA4#108-e | S4-200631 | | | | Integration of support for subtitles in S4-200626 | 1.3.0 | +| 2020-06 | SA4#109-e | S4-200761
S4-200760 | | | | Inclusion of CMAF references in presentation format capabilities
Implementation of working assumption on video codec requirements for default downlink and TV profiles | 1.4.0 | +| 2020-06 | SA4#109-e | SA4 plenary decision | | | | Inclusion of 10-bit bit depth into the HD-HDR capability | 1.4.1 | +| 2020-06 | SA#88-e | SP-200405 | | | | Profiles, Codecs and Formats (Version 2.0.0) | 2.0.0 | +| 2020-06 | SA#88-e | SP-200405 | | | | Profiles, Codecs and Formats (UCC) | 16.0.0 | +| 2020-09 | SA#89-e | SP-201261 | 0001 | 1 | B | Corrections to 5G Media Streaming | 16.1.0 | +| 2021-04 | SA#91-e | SP-210039 | 0002 | 1 | F | Various Corrections to 5GMS Codecs and Formats | 16.2.0 | +| 2021-04 | SA#91-e | SP-210038 | 0003 | 1 | B | 8K Decoding Capabilities | 17.0.0 | +| 2022-03 | SA#95-e | SP-220032 | 0007 | 1 | B | 8K TV in 5GMS | 17.1.0 | +| 2023-03 | SA#99 | SP-230251 | 0008 | 2 | B | Upgrade of audio profiles for 5G-Advanced | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26517/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-18/26_series/26517/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c91ba5de16d5496116f6d3a507ad8c6f0c70028b --- /dev/null +++ b/marked/Rel-18/26_series/26517/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6188bfca9855bf590e38830ffbebb35cfb7a185fc617c408b68959c19b1729fa +size 88132 diff --git a/marked/Rel-18/26_series/26517/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26517/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de4138277ec8adf2fc475c924d7e0105c40461fb --- /dev/null +++ b/marked/Rel-18/26_series/26517/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e7eb3e11d39acd786cf8b1c167e009cbfb88e5d72bca0b5550cd234a67bad65 +size 9503 diff --git a/marked/Rel-18/26_series/26517/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26517/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33f482c54e1d793894383540fef669bc0df88a4d --- /dev/null +++ b/marked/Rel-18/26_series/26517/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2eb9506d505421bc0612e3f23e972f6d4405b1f3dd50b65cd9b273ab90f2a1d +size 5668 diff --git a/marked/Rel-18/26_series/26517/raw.md b/marked/Rel-18/26_series/26517/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3ad05b4c56860b976305f2547e60071f18fee945 --- /dev/null +++ b/marked/Rel-18/26_series/26517/raw.md @@ -0,0 +1,2137 @@ + + +# 3GPP TS 26.517 V18.5.1 (2025-10) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G Multicast-Broadcast User Services; Protocols and Formats (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions of terms, symbols and abbreviations..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 10 | +| 3.4 Syntax documentation conventions..... | 10 | +| 4 System overview ..... | 10 | +| 5 Announcement of MBS User Services ..... | 11 | +| 5.0 Overview ..... | 11 | +| 5.1 User Service Description data model..... | 11 | +| 5.1.1 General ..... | 11 | +| 5.1A Encoding..... | 13 | +| 5.2 Syntax and associated semantics..... | 13 | +| 5.2.1 General ..... | 13 | +| 5.2.2 User Service Bundle Descriptions document ..... | 14 | +| 5.2.3 User Service Description data type ..... | 14 | +| 5.2.4 Distribution Session Description data type ..... | 15 | +| 5.2.5 Session Description document ..... | 16 | +| 5.2.6 Application Service Description data type ..... | 16 | +| 5.2.6A Application Service Entry Point document ..... | 16 | +| 5.2.7 Service Schedule Description data type ..... | 17 | +| 5.2.8 Object Repair Parameters data type..... | 18 | +| 5.2.9 Availability Information data type ..... | 18 | +| 5.2.10 Security Description data type..... | 19 | +| 5.3 Delivery of User Service Descriptions..... | 20 | +| 5.3.1 General ..... | 20 | +| 5.3.1A User Service Descriptions Bundle..... | 20 | +| 5.3.2 Delivery of User Service Descriptions Bundle Entity in object carousel ..... | 21 | +| 5.3.3 Delivery of User Service Descriptions Bundle Entity via unicast PDU Session ..... | 21 | +| 6 Object Distribution Method ..... | 22 | +| 6.1 General ..... | 22 | +| 6.1.1 Overview ..... | 22 | +| 6.1.2 Object manifest..... | 22 | +| 6.2 Usage of FLUTE for Object Distribution Method ..... | 23 | +| 6.2.1 General ..... | 23 | +| 6.2.2 Session Description document for FLUTE ..... | 23 | +| 6.2.2.1 General..... | 23 | +| 6.2.2.2 MBS service type of MBS Session..... | 24 | +| 6.2.2.3 SDP examples for FLUTE Session..... | 25 | +| 6.2.3 Operating modes for FLUTE-based Object Distribution Method..... | 25 | +| 6.2.3.1 Introduction..... | 25 | +| 6.2.3.2 Single object operating mode ..... | 26 | +| 6.2.3.3 Object collection operating mode..... | 26 | +| 6.2.3.4 Object carousel operating mode ..... | 26 | +| 6.2.3.5 Segment streaming operating mode..... | 26 | +| 6.2.4 Object Repair mechanism for FLUTE..... | 27 | +| 6.2.4.1 General..... | 27 | +| 6.2.4.2 Post-session Object Repair procedure ..... | 28 | +| 6.2.4.3 In-session object repair procedure ..... | 29 | +| 6.2.4.4 Network location of repair object ..... | 29 | +| 6.2.4.5 Byte range determination..... | 29 | + +| | | | +|-----------|------------------------------------------------------------------------|----| +| 6.2.4.6 | Object recovery procedure..... | 30 | +| 7 | Packet Distribution Method ..... | 31 | +| 7.1 | General ..... | 31 | +| 7.2 | Re-using MBMS Delivery Method as Packet Distribution Method ..... | 31 | +| 7.2.1 | General ..... | 31 | +| 7.2.2 | Void ..... | 31 | +| 7.2.3 | Session Description ..... | 31 | +| 7.2.3.1 | General ..... | 31 | +| 7.2.3.2 | SDP examples for Packet Distribution Method ..... | 32 | +| 8 | General aspects of APIs for MBS User Services ..... | 33 | +| 8.1 | HTTP resource URIs and paths..... | 33 | +| 8.2 | Usage of HTTP..... | 33 | +| 8.2.1 | HTTP protocol version..... | 33 | +| 8.2.1.1 | General ..... | 33 | +| 8.2.1.2 | MBSF ..... | 33 | +| 8.2.1.3 | MBSTF ..... | 33 | +| 8.2.1.4 | MBS AF..... | 33 | +| 8.2.1.5 | MBS AS..... | 34 | +| 8.2.1.6 | MBSSF..... | 34 | +| 8.2.2 | HTTP message bodies for API resources ..... | 34 | +| 8.2.3 | Usage of HTTP headers..... | 34 | +| 8.2.3.1 | General ..... | 34 | +| 8.2.3.2 | User Agent identification..... | 34 | +| 8.2.3.2.1 | General ..... | 34 | +| 8.2.3.2.2 | MBSF identification..... | 35 | +| 8.2.3.2.3 | MBSTF identification ..... | 35 | +| 8.2.3.2.4 | MBSF Client identification ..... | 35 | +| 8.2.3.2.5 | MBSTF Client identification..... | 35 | +| 8.2.3.3 | Server identification..... | 35 | +| 8.2.3.3.1 | General ..... | 35 | +| 8.2.3.3.2 | MBSF identification..... | 35 | +| 8.2.3.3.3 | MBSTF identification ..... | 35 | +| 8.2.3.3.4 | MBS AF identification..... | 36 | +| 8.2.3.3.5 | MBS AS identification..... | 36 | +| 8.2.3.4 | Support for conditional HTTP GET requests ..... | 36 | +| 8.2.3.5 | Support for conditional HTTP POST, PUT, PATCH and DELETE requests..... | 36 | +| 8.2.3.3.6 | MBSSF identification..... | 36 | +| 8.3 | HTTP response codes..... | 37 | +| 9 | MBS AF APIs (MBS-5)..... | 37 | +| 9.1 | General ..... | 37 | +| 9.2 | User Service Description retrieval API..... | 37 | +| 9.2.1 | General ..... | 37 | +| 9.2.2 | Resource structure ..... | 37 | +| 9.2.3 | Response format ..... | 38 | +| 9.2.3.1 | User Service Descriptions result..... | 38 | +| 9.2.3.2 | User Service Description result ..... | 39 | +| 10 | MBS AS protocols (MBS-4-UC)..... | 39 | +| 10.1 | General ..... | 39 | +| 10.2 | Unicast Object Repair protocol..... | 39 | +| 10.2.1 | Overview ..... | 39 | +| 10.2.2 | MBSTF Client procedures..... | 39 | +| 10.2.2.1 | General ..... | 39 | +| 10.2.2.2 | Parameters..... | 40 | +| 10.2.2.3 | Back-off time computation ..... | 40 | +| 10.2.2.4 | MBSTF Client unicast repair request ..... | 40 | +| 10.2.3 | MBS AS requirements..... | 41 | +| 11 | MBSSF security protocols (MBS-10)..... | 41 | +| 11.1 | General ..... | 41 | +| 11.2 | MBS Service Key retrieval from MBSSF..... | 41 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------|-----------| +| 11.2.1 | Overview ..... | 41 | +| 11.2.2 | MBSF Client procedures ..... | 41 | +| 11.2.2.1 | MBSSF endpoint selection by MBSF Client ..... | 41 | +| 11.2.2.2 | Back-off time computation ..... | 42 | +| 12 | Conformance profiles for MBS Distribution Sessions ..... | 42 | +| 12.1 | Definition ..... | 42 | +| 12.2 | Identification of conformance profile ..... | 42 | +| 12.3 | Semantics of conformance signalling in User Service Description ..... | 43 | +| 12.4 | Baseline MBS Distribution Session Profile ..... | 43 | +| Annex A (normative): | Syntax for Service Announcement..... | 44 | +| A.1 | Void..... | 44 | +| A.2 | JSON-based representation ..... | 44 | +| A.2.1 | MBS User Service Announcement schema ..... | 44 | +| Annex B (informative): | Service Announcement examples..... | 49 | +| B.1 | XML-based representation..... | 49 | +| B.2 | JSON-based representation ..... | 49 | +| Annex C (normative): | 3GPP Registered URIs..... | 50 | +| C.1 | General..... | 50 | +| C.2 | Controlled vocabulary of conformance profile identifiers..... | 50 | +| Annex D (normative): | Syntax for object manifest..... | 51 | +| D.1 | Object manifest schema ..... | 51 | +| Annex E (normative): | IANA registration..... | 53 | +| E.1 | General..... | 53 | +| E.2 | Registration of MIME media type for MBS User Service Descriptions document..... | 53 | +| E.2.1 | General ..... | 53 | +| E.2.2 | Profiles parameter ..... | 54 | +| E.2.3 | Version parameter ..... | 54 | +| E.3 | Registration of MIME media type for MBS User Services object manifest document..... | 55 | +| E.3.1 | General ..... | 55 | +| E.3.2 | Version parameter ..... | 55 | +| Annex F (informative): | Change history..... | 56 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document defines protocols and formats for User Services as defined in TS 26.502 [6] and conveyed using the 5G multicast–broadcast capabilities of the 5G System defined in TS 23.501 [2], TS 23.502 [3] and TS 23.247 [5]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". +- [3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". +- [4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [5] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [6] 3GPP TS 26.502: "5G multicast–broadcast services; User Service architecture". +- [7] 3GPP TS 26.346: "MBMS; Protocols and Codecs". +- [8] IETF RFC 8866: "Session Description Protocol". +- [9] Void. +- [10] 3GPP TS 23.003: "Numbering, addressing and identification". +- [11] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [12] IETF RFC 3926: "FLUTE - File Delivery over Unidirectional Transport". +- [13] Void. +- [14] OpenAPI: "OpenAPI 3.0.0 Specification", . +- [15] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [16] 3GPP TS 29.501: "5G System: Principles and Guidelines for Services Definition; Stage 3". +- [17] 3GPP TS 29.580: "5G System; Multicast/Broadcast Service Function services; Stage 3". +- [18] 3GPP TS 29.581: "5G System; Multicast/Broadcast Service transport services; Stage 3". +- [19] IETF RFC 9110: "HTTP Semantics", June 2022. +- [20] IETF RFC 9111: "HTTP Caching", June 2022. +- [21] IETF RFC 9112: "HTTP/1.1", June 2022. +- [22] IETF RFC 9113: "HTTP/2", June 2022. + +- [23] Reserved for future use. +- [24] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3", August 2018. +- [25] Open Mobile Alliance: "OMNA BCAST Service Class Registry", . +- [26] IETF RFC 3629: "UTF-8, a transformation format of ISO 10646". +- [27] IETF RFC 8141: "Uniform Resource Names (URNs)". +- [28] ISO 639-2: "Codes for the representation of names of languages - Part 2: Alpha-3 code". +- [29] IETF RFC 6381: "The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types". +- [30] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [31] 3GPP TS 26.512: "5G Media Streaming (5GMS); Protocols". +- [32] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [33] 3GPP TS 33.246: "3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS)". +- [34] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". +- [35] 3GPP TR 26.946: "Multimedia Broadcast/Multicast Service (MBMS) user service guidelines". +- [36] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [37] IETF RFC 2046, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". +- [38] IETF RFC 2387: "The MIME Multipart/Related Content-type". +- [39] IETF RFC 2557: "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)". +- [40] IETF RFC 2017: "Definition of the URL MIME External-Body Access-Type". +- [41] IETF RFC 1952: "GZIP file format specification version 4.3". +- [42] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1], TS 23.501 [2], TS 23.502 [3], TS 23.247 [5], TS 26.502 [6] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**User Service Descriptions document:** a version-controlled document that conveys one or more User Service Description objects. + +**User Service Description object:** a JSON object carrying information about a single MBS User Service corresponding to an MBS User Service Announcement. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], TS 23.501 [2], TS 23.502 [3], TS 23.247 [4] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|-------------------------------------------------| +| ALC | Asynchronous Layered Coding | +| CMAF | Common Media Application Format | +| DASH | Dynamic Adaptive Streaming over HTTP | +| ESI | Encoding Symbol Identifier | +| FDT | File Delivery Table | +| FLUTE | File Delivery over Unidirectional Transport | +| FSA | Frequency Selection Area | +| GBA | Generic Bootstrapping Architecture | +| HTTP | HyperText Transfer Protocol | +| HTTPS | HTTP over TLS | +| JSON | JavaScript Object Notation | +| MBMS | Multimedia Broadcast Multicast Service | +| MBS | Multicast–Broadcast Services | +| MB-SMF | Multicast–Broadcast Session Management Function | +| MB-UPF | Multicast–Broadcast User Plane Function | +| MBSF | Multicast–Broadcast Service Function | +| MBSTF | Multicast–Broadcast Service Transport Function | +| MPD | Media Presentation Description | +| MSK | MBS Service Key | +| PCF | Policy and Charging Function | +| NEF | Network Exposure Function | +| OTI | Object Transmission Information | +| ROHC | Robust Header Compression | +| RTP | Real-Time Protocol | +| SDP | Session Description Protocol | +| TMGI | Temporary Mobile Group Identity | +| TOI | Transmission Object Identifier | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UML | Unified Markup Language | +| XML | eXtensible Markup Language | +| YAML | Yet Another Markup Language | + +## 3.4 Syntax documentation conventions + +The conventions from TS 29.501 [16] apply to this document with the following extensions for OpenAPI [14] structured data type definitions as defined in clause 5.2.4.1 of TS 29.501 [16]: + +1. Data types are annotated in **Bold face**. +2. Properties of data types are noted in `codestyle`. + +# --- 4 System overview + +The present document defines protocols and formats for MBS User Services as defined in TS 26.502 [6] and conveyed using the 5G Multicast–Broadcast capabilities of the 5G System defined in TS 23.501 [2], TS 23.502 [3] and TS 23.247 [5]. + +MBS User Services enable high-level applications to make use of the low-level features of the MBS System. An MBS User Service is provided by the MBSF and MBSTF working in combination to support configuration option 2 and configuration option 3 defined in annex A of TS 23.247 [5]. The MBS User Services architecture is defined in clause 4.2.2 of TS 26.502 [6] and shows the MBS-related entities involved in providing MBS User Services delivery and control. + +The MBSF and MBSTF offer service layer functionality for sending MBS data via MBS Sessions. The MBSF offers control plane functionality while the MBSTF offers user plane functionality. The MBSTF acts as a User Plane anchor when it sources IP multicast traffic. Clause 4.3.1 of TS 26.502 [6] defines the set of functional entities involved in supporting MBS User Services, including client functions in the UE. + +# --- 5 Announcement of MBS User Services + +## 5.0 Overview + +MBS User Service Announcement is needed in order to advertise MBS User Services in advance of, and potentially during, the MBS User Service Sessions described. MBS User Service Announcement (as defined in clauses 4.5.7 and 4.5.8 of TS 26.502 [3]) is provided by means of an *MBS User Service Description*, the syntax of which is defined in this clause. + +The MBS User Service Announcement plays an equivalent role to the MBMS User Service announcement as defined in TS 26.346 [7], but it is simplified and extended for the needs of Multicast-Broadcast Services. + +## 5.1 User Service Description data model + +### 5.1.1 General + +An MBS User Service Description is described by a set of metadata documents that are delivered as described in clause 4.3.2 of TS 26.502 [3]. The data model defined in this clause subdivides the parameters defined in [3] and groups them into a set of *metadata documents*. + +The metadata consists of: + +- A *User Service Descriptions* document (see clause 5.2.2) describing a set of one or more MBS User Services, and containing: + - One of more *User Service Description* objects (see clause 5.2.3), each describing an MBS User Service Session that is associated with: + - One or more *Distribution Session Description* objects (see clause 5.2.4), each of which references a Session Description document [8] (see clause 5.2.5) that may be packaged with the User Service Descriptions document for delivery to the MBS Client in the same User Service Bundle (see clause 5.3.4), and each of which may optionally reference an Object Repair Parameters object (see clause 5.2.7) describing the object repair parameters for the MBS Distribution Session in question. + - Zero or more alternative *Application Service Description* objects (see clause 5.2.5), each of which references an Application Service Entry Point document (see clause 5.2.6) that may be packaged with the User Service Description document for delivery to the MBS Client in the same User Service Bundle (see clause 5.3.4). Additional resources referenced by the Application Service Entry Point document may also be packaged into the User Service Bundle. + - Zero or more *Service Schedule Description* objects (see clause 5.2.7) advertising the delivery schedule for the MBS User Service Session. + +Figure 5.1.1 illustrates the relationships between these metadata entities using UML for a User Service Descriptions document. + +![UML Class Diagram: User Service Data Model simple description](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +classDiagram + class User_Service_Descriptions_document { + User Service Descriptions + } + class User_Service_Description { + } + class Distribution_Session_Description { + } + class Service_Schedule_Description { + } + class Object_Repair_Parameters { + } + class Session_Description_parameters { + } + class Application_Service_Description { + } + class Application_Service_parameters { + } + class Ancillary_resource { + } + + User_Service_Descriptions_document "1" *-- "1..N" User_Service_Description : userServiceDescriptions[] + User_Service_Description "1" *-- "1..N" Distribution_Session_Description : distributionSessionDescriptions[] + User_Service_Description "1" *-- "0..N" Service_Schedule_Description : scheduleDescriptions[] + Distribution_Session_Description "1" *-- "0..1" Object_Repair_Parameters : postSessionObjectRepairParameters + Distribution_Session_Description "1..N" --> "1" Session_Description_parameters : references + Distribution_Session_Description "1" *-- "0..N" Application_Service_Description : applicationServiceDescriptions[] + Application_Service_Description "1..N" --> "1" Application_Service_parameters : references + Application_Service_parameters "1" --> "0..N" Ancillary_resource : references + Object_Repair_Parameters "0..1" --> "1..N" Session_Description_parameters : references + + subgraph Session_Description_document + Session_Description_parameters + end + subgraph Application_Service_Entry_Point_document + Application_Service_parameters + end + +``` + +The diagram illustrates the relationships between metadata entities in a User Service Descriptions document. At the top, the **User Service Descriptions document** contains one or more **User Service Description** objects. Each **User Service Description** object contains one or more **Distribution Session Description** objects and zero or more **Service Schedule Description** objects. Each **Distribution Session Description** object may include an **Object Repair Parameters** object and one or more **Session Description parameters** objects. Each **Session Description parameters** object may include one or more **Object Repair parameters** objects. Each **Distribution Session Description** object may include zero or more **Application Service Description** objects. Each **Application Service Description** object may include one or more **Application Service parameters** objects. Each **Application Service parameters** object may include one or more **Ancillary resource** objects. + +UML Class Diagram: User Service Data Model simple description + +NOTE: “N” means any number in each instance. + +**Figure 5.1-1: User Service Data Model simple description** + +A *User Service Description* document shall contain one or more *User Service Description* objects, each of which describes a single MBS User Service Session. + +Each *User Service Description* object shall include at least one *Distribution Service Description* object describing the set of MBS Distribution Sessions currently associated with the MBS User Service Session. + +- The *Distribution Session Description* object shall refer to one *Session Description document*. +- Each *Distribution Session Description* object may include an *Object Repair Parameters* object. +- Each *Distribution Session Description* object may include zero or more alternative *Application Service Description* object, optionally referencing an *Application Service Entry Point document* (e.g. a DASH MPD, HLS Master Playlist or HTML document) which describes the root of the *Application Service* associated with this MBS Distribution Session. When multiple *Application Service Entry Point documents* are referenced by the same *Distribution Session Description* (not permitted in this release), an MBS Client shall select only one on the basis of a distinct MIME content type indicated in the *Application Service Description* object. + +Each User Service Description object may include *Service Schedule Description* objects. If included, the UE can expect to receive MBS User Service data during the time periods described in the Service Schedule Description object. + +## 5.1A Encoding + +The User Service Descriptions document shall be a JSON instance document formatted according to the schema specified in clause A.2 with the following constraints: + +- The MIME type of the User Service Description document is specified in clause E.2. +- The encoding of the User Service Description document shall be UTF-8 as defined in IETF RFC 3629 [26]. +- The extension of the schemas specified in clause A.2, in particular the addition of information elements, is reserved to 3GPP. +- Additional rules for schema extension are for future study. + +## 5.2 Syntax and associated semantics + +### 5.2.1 General + +The following description in this clause presumes a JSON encoding of the information comprising the MBS User Service Announcement as specified in clause 5.1A. + +The data types in table 5.2.1-1 from other 3GPP specifications are reused in the remainder of the present document. + +**Table 5.2.1 1: Externally defined data types used by User Service Description schema** + +| Data type | Comments | Reference | +|-----------------------|---------------------------------------------|----------------| +| Uri | A Uniform Resource Locator | TS 29.571 [30] | +| DateTime | A date-time value. | | +| MbsServiceArea | An MBS Service Area. | | +| MbsFsald | An MBS Frequency Selection Area identifier. | | +| DurationSec | A time duration expressed in seconds. | TS 29 512 [31] | +| AbsoluteUrl | An absolute URL | | + +The data types in table 5.2.1-2 are defined in the present document. + +**Table 5.2.1 2: User Service Description schema data types defined in the present document** + +| Data type | Clause | +|---------------------------------------|--------| +| UserServiceDescriptions | 5.2.2 | +| UserServiceDescription | 5.2.3 | +| DistributionSessionDescription | 5.2.4 | +| ApplicationServiceDescription | 5.2.6 | +| ServiceScheduleDescription | 5.2.7 | +| ObjectRepairParameters | 5.2.8 | +| AvailabilityInformation | 5.2.9 | +| NrParameterSet | 5.2.9 | +| SecurityDescription | 5.2.10 | + +### 5.2.2 User Service Bundle Descriptions document + +The MBS User Service Descriptions document conveys one or more *User Service Description* objects. Table 5.2.2-1 provides the detailed semantics for the **UserServiceDescriptions** data type that conveys these objects. + +**Table 5.2.2-1: Semantics of **UserServiceDescriptions** data type** + +| Property name | Data Type | P | Cardinality | Description | +|-------------------------|---------------------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| version | integer | O | 0..1 | Provides the version number of the MBS User Service Descriptions document. Any two documents that are different shall have different version numbers. A higher number overwrites a lower version number. Minimum value: 1. If not present, the latest delivered document overwrites any previously delivered ones. | +| userServiceDescriptions | array(UserService Description) | M | 1..N | A set of one or more User Service Description objects (see clause 5.2.3). | + +### 5.2.3 User Service Description data type + +The **UserServiceDescription** data type carries information about a single MBS User Service corresponding to an MBS User Service Announcement as defined in clause 4.5.7 of TS 26.502 [6]. Table 5.2.3-1 provides the detailed semantics for this data type. + +**Table 5.2.3-1: Semantics of **UserServiceDescription** data type** + +| Property name | Data Type | P | Cardinality | Description | +|-----------------------------------------|-----------------------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serviceIds | array(Uri) | M | 1..N | The set of External service identifiers for the MBS User Service as defined in table 4.5.7-1 of TS 26.502 [6]. Each value is expressed as a URI. | +| class | Uri | M | 1 | The Service class of the MBS User Service as defined in table 4.5.7-1 of TS 26.502 [6]. The value is expressed as a fully-qualified term identifier URI. | +| names | array(object) | O | 1..N | The Service names of the MBS User Service as defined in table 4.5.7-1 of TS 26.502 [6]. Each service name is differentiated by a language as defined in the lang property. | +| name | string | M | 1 | One of the Service names . | +| lang | string | M | 1 | Language of the service name encoded using an ISO "alpha-3" language code according to ISO 639-2 [28]. | +| descriptions | array(object) | O | 1..N | The Service descriptions of the MBS User Service as defined in table 4.5.7-1 of TS 26.502 [6]. | +| description | string | M | 1 | One of the Service descriptions . | +| lang | string | M | 1 | Language of the service description encoded using an ISO "alpha-3" language code according to ISO 639-2 [28]. | +| serviceLanguage | string | O | 0..1 | The Main service language of the MBS User Service as defined in table 4.5.7-1 of TS 26.502 [6], encoded using an ISO "alpha-3" language code according to ISO 639-2 [28]. | +| distribution
Session
Descriptions | array(Distribution SessionDescription) | M | 1..N | One or more MBS Distribution Session Descriptions for the MBS User Service (see clause 5.2.4). | + +| Property name | Data Type | P | Cardinality | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serviceSchedule Descriptions | array(Service Schedule Description) | O | 1..N | The Active periods of the MBS User Data Ingest Session as defined in clause 4.5.5 of TS 26.502 [6].
An array of service schedules indicating when the MBS User Service is scheduled to be active (see clause 5.2.7).
If omitted, the MBS User Service is always active (see NOTE). | +| NOTE: The current active period for an individual MBS Distribution Session may be further restricted by information in its Session Description document ( t and/or r lines in the SDP) specified in clause 5.2.5. | | | | | + +### 5.2.4 Distribution Session Description data type + +The *DistributionSessionDescription* data type describes one *MBS Distribution Session* associated with an MBS User Service and carries the MBS Distribution Session Parameters as defined in clause 4.5.8 of TS 26.502 [6]. + +Table 5.2.4-1 provides the detailed semantics of this data type. + +**Table 5.2.4-1: Semantics of *DistributionSessionDescription* data type** + +| Property name | Data Type | P | Cardinality | Description | +|-------------------------------------|----------------------------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| distribution Method | DistributionMethod | M | 1 | The distribution method used for this MBS Distribution Session.
For details, refer to table 5.2.4-2. | +| conformance Profiles | array(Uri) | O | 1..N | A list of profiles indicating the set of features that this MBS Distribution Session conforms to and which the MBS Client needs to support in order to fully decode the MBS Distribution Session. For details refer to clause 12.
If not present, the MBS Distribution Session is assumed to conform to the "Baseline MBS Distribution Session Profile" specified in clause C.2. | +| session Description Locator | AbsoluteUrl | M | 1 | URL to a Session Description document carrying the Session Description parameters for this MBS Distribution Session as defined in table 4.5.8-1 of TS 26.502 [6].
For details, refer to clause 5.2.5. | +| application Service Descriptions | array(Application ServiceDescription) | O | 1..1 | If present, an array containing a set of one or more Application Service Descriptions for the MBS User Service (see clause 5.2.6 and text below this table). | +| postSession ObjectRepair Parameters | ObjectRepair Parameters | O | 0..1 | Parameters to be used by the MBSTF Client at reference point MBS-4-UC for post-session unicast object repair of this MBS Distribution Session, as defined in table 4.5.8-2 of TS 26.502 [6].
For details, refer to clause 5.2.8. | +| availability Infos | array(Availability Information) | O | 1..N | Additional information pertaining to the availability of this MBS Distribution Session within the MBS System.
For details, refer to clause 5.2.9. | +| security Description | SecurityDescription | O | 0..1 | The security parameters for this MBS Distribution Session, as defined in table 4.5.8-1 of TS 26.502 [6].
For details, refer to clause 5.2.10. | + +**Table 5.2.4-2: Semantics of *DistributionMethod* enumeration** + +| Enumerated value | Description | +|------------------|---------------------------------| +| OBJECT | The Object Distribution Method. | +| PACKET | The Packet Distribution Method. | + +If the `applicationServiceDescriptions` array is present: + +1. The `distributionMethod` property of the `DistributionSessionDescription` shall be set to *OBJECT*. +2. All members of the `applicationServiceDescription` array shall reference an Application Service Entry Point document (see clause 5.2.6A) that describes an MBS Distribution Session using the Object Distribution Method as specified in clause 6. +3. The `sessionDescriptionLocator` property shall point to a Session Description document (see clause 5.2.5) describing an MBS Distribution Session according to clause 6 delivering objects that are directly or indirectly referenced by the Application Service Entry Point document. + +### 5.2.5 Session Description document + +Each MBS Distribution Session shall be described by a Session Description document that shall be formatted according to RFC 8866 [8]. The Session Description document may be packaged in the same MBS User Service Bundle (see clause 5.3.1A) as the MBS User Service Descriptions document. + +- The session description for the MBS Object Distribution Method is specified in clause 6.2.2 +- The session description for the MBS Packet Distribution Method is specified in clause 7.2.3. + +### 5.2.6 Application Service Description data type + +Table 5.2.6-1 provides the detailed semantics for the `ApplicationServiceDescription` data type. + +**Table 5.2.6-1: Semantics of `ApplicationServiceDescription` data type** + +| Property name | Data Type | P | Cardinality | Description | +|--------------------------------|---------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| entryPointLocator | Uri | M | 1 | Reference to an Application Service Entry Point document, for example to a DASH MPD. | +| contentType | string | M | 1 | Format of the document referenced by entryPointLocator . This shall be a MIME content type, for example application/dash+xml . | + +### 5.2.6A Application Service Entry Point document + +The Application Service Entry Point document shall follow a format consistent with the value of `contentType` indicated as specified in clause 5.2.6. + +In the case of 3GP-DASH formatted content as defined in TS 26.247 [36], the Application Service Entry Point document may be a unified media manifest which describes Representations available for both MBS reception and unicast retrieval, and this shall be used by MBS Clients compliant with the present document. In practical deployments, different subsets of the Representations described by the unified manifest document may be specified for: + +- Availability via MBS delivery only, +- Availability via both unicast and MBS delivery, +- Availability via unicast only, and the Representation is redundant in MBS area coverage, i.e. the usage of these resources does not provide an improved user experience. As an example, this may be a lower bitrate Representation of a media component for which a higher bitrate is available over MBS distribution, and +- Availability always via unicast, and the Representation is supplementary in MBS area coverage, i.e. even in MBS area coverage these resources provide an improved user experience. As an example, this may be a secondary language that is only accessible over unicast. + +All resources that are directly or indirectly referenced in the Application Service Entry Point document of this metadata unit that are expected to be retrieved by HTTP GET shall be delivered by at least one of the MBS Distribution Sessions associated with the MBS User Service Description. + +### 5.2.7 Service Schedule Description data type + +A Service Schedule Description object describes the distribution schedule of a single instance of the MBS User Service and the availability of content via unicast delivery in terms of: + +- Start/stop time point; or +- Start time point, time duration and periodicity. + +The MBS Client can expect to receive MBS data during the described time period(s). + +The Schedule Description object may be delivered to the MBS Client prior to the MBS Distribution Session as part of the User Service Description document (see clause 5.2.2) and may be updated subsequently along with that document. + +The Service Schedule Description object with the highest version number shall take priority, such that schedule parameters received prior to the MBS Distribution Session are regarded as "initial defaults", and schedule parameters received during the MBS Distribution Session overwrite the earlier received schedule parameters. + +The MBS Distribution Session shall be available to the MBS Client during the time interval(s) announced by the session schedule. The MBS Client shall not activate reception of that MBS Distribution Session outside this time window. + +Schedule information received in the Schedule Description object shall take precedence over timing information that may have been received in the Session Description object (*t* and/or *r* lines in the SDP). + +Table 5.2.7-1 provides the detailed semantics for the **ServiceScheduleDescription** data type which describes a single scheduled instance of the MBS User Service Session. + +**Table 5.2.7-1: Semantics of `ServiceScheduleDescription` data type** + +| Property name | Type | P | Cardinality | Description | +|-----------------------------|-----------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| id | string | M | 1 | An identifier for the MBS User Service Session instance described by this object, unique within the scope of the MBS System.
This value is invariant across all versions of the object. | +| version | integer | M | 1 | The version number of this scheduled MBS User Service Session instance. The value increases monotonically whenever a change to the remaining properties needs to be signalled to the MBS Client.
Minimum value: 1. | +| start | DateTime | C | 1 | The start date-time of this MBS User Service Session instance.
If present, stop shall also be present.
This property shall be mutually exclusive with repetitionRule . | +| stop | DateTime | C | 1 | The stop date-time of this MBS User Service Session instance.
If present, start shall also be present.
This property shall be mutually exclusive with repetitionRule . | +| repetitionRule | RepetitionRule | C | 1 | A rule describing the periodic active time(s) of this MBS User Service Session instance.
This property shall be mutually exclusive with start and stop . | +| cancelled | boolean | O | 0..1 | When set to true , indicates that this MBS User Service Session instance is cancelled and the MBS Client shall terminate all ongoing MBS User Service procedures, including object reception, object repair and reporting.
The MBS Client shall not attempt to join an MBS User Service Session that is marked as cancelled.
If omitted the value is false . | + +**Table 5.2.7-2: Semantics of `RepetitionRule` data type** + +| Property name | Type | P | Cardinality | Description | +|---------------------------------|--------------------|---|-------------|----------------------------------------------------------------------| +| startTime | DateTime | M | 1 | The absolute start date-time of the first occurrence of this period. | +| duration | DurationSec | M | 1 | The duration of each occurrence of this period. | +| repetitionInterval | DurationSec | M | 1 | The time between occurrences of the period. | + +### 5.2.8 Object Repair Parameters data type + +Object Repair Parameters configure the Object Repair as defined in clause 6.2.4. + +Table 5.2.8-1 provides the detailed semantics for the `ObjectRepairParameters` data type. + +**Table 5.2.8-1: Semantics of `ObjectRepairParameters` data type** + +| Property name | Data Type | P | Cardinality | Description | +|--------------------------------------------|---------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| backOffParameters | BackOffParameters | O | 0..1 | The back-off behaviour of the MBSTF Client when using the Object Repair mechanism (see clause 10.2.2.3).
If present, at least one of the contained parameters shall be present.
If omitted, no back-off delay is required. | +| offsetTime | DurationSec | C | 1..1 | The minimum time that an MBSTF Client shall wait after completion of the download delivery session before making an Object Repair request.
If not present the value is assumed to be zero. | +| randomTimePeriod | DurationSec | C | 1..1 | The maximum time window length over which an MBSTF Client shall calculate the value of RandomTime to be used as a delay to its Object Repair request in addition to offsetTime .
If not present the value is assumed to be zero. | +| objectDistributionBaseLocator | Uri | O | 0..1 | The Object distribution base URL of the MBS Distribution as defined in table 4.5.6-2 of TS 26.502 [6]. | +| objectRepairBaseLocators | array(AbsoluteUrl) | M | 0..1 | The Object repair base URL of the MBS Distribution as defined in table 4.5.6-2 of TS 26.502 [6]. | + +### 5.2.9 Availability Information data type + +The `AvailabilityInformation` data type provides additional information pertaining to the availability of the MBS Distribution Session within the 5G Network: + +- The `serviceArea` property declares the one or more service areas in which the MBS Session corresponding to this MBS Distribution Session is currently available. +- In the case of a broadcast MBS Session corresponding to this MBS Distribution Session: + - The `mbsFSAId` property identifies a preconfigured area within which, and in proximity to, the cell(s) announce the MBS Frequency Selection Area (FSA) ID and its associated frequency. + - The `nrRedCapUEInfo` property indicates which classes of UE the MBS Distribution Session is suitable for consumption by. + +NOTE 1: This is used to guide frequency selection by the UE for a broadcast MBS Session. + +- In the case of a broadcast MBS Session corresponding to this MBS Distribution Session, the `nrParameters` property indicates the one or more radio frequencies in the NG-RAN downlink on which the MBS Session is transmitted in the service area(s) identified by the `serviceArea` property. + +NOTE 2: The radio frequencies may be obtained by interrogating the OAM using the value of the *mbsFSAId* property as a lookup key. + +Table 5.2.9-1 provides the detailed semantics for the *AvailabilityInformation* data type. + +**Table 5.2.9-1: Semantics of *AvailabilityInformation* data type** + +| Property name | Type | P | Cardinality | Description | +|------------------------|------------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mbsServiceAreas | array(MbsServiceArea) | O | 1..N | The Target service areas of this MBS Distribution Session, as defined in table 4.5.8-1 of TS 26.502 [6]. | +| mbsFSAId | MbsFsaId | C | 0..1 | (Broadcast MBS Distribution Session only.)
The MBS Frequency Selection Area (FSA) Identifier of the (broadcast) MBS Distribution Session in the parent service area, as defined in table 4.5.8-1 of TS 26.502 [6]. | +| nrParameters | array(NrParameterSet) | M | 1..N | (Broadcast MBS Distribution Session only.)
The New Radio transmission parameters in the parent service areas, expressed using the data type specified in table 5.2.9-2. | +| nrRedCapUEInfo | NrRedCapUeInfo | O | 0..1 | (Broadcast MBS Distribution Session only.)
Indicates whether the MBS session is suitable for consumption by NR RedCap UEs and/or non-RedCap UEs as defined by Target UE classes in TS 26.502 [6]. The data type and its enumerated values are specified in TS 29.571 [30].
If omitted, no information is known and the value NON_REDCAP_UE_ONLY may be assumed. | + +Table 5.2.9-2 provides the detailed semantics for the *NrParameterSet* data type. + +**Table 5.2.9-2: Semantics of *NrParameterSet* data type** + +| Property name | Type | P | Cardinality | Description | +|--------------------------|-----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| freqBandIndicator | UInteger | M | 1 | NR frequency band number, corresponding to the FreqBandIndicatorNR parameter in clause 6.3.2 of TS 38.331 [42]. | +| aRFCNValue | UInteger | M | 1 | ARFCN applicable to a downlink NR global frequency raster, corresponding to the ARFCN-ValueNR parameter specified in clause 6.3.2 of TS 38.331 [42]. | + +### 5.2.10 Security Description data type + +In order to support the transport security for MBS, the *DistributionSessionDescription* object may contain an object of type *SecurityDescription* indicating the User Plane security parameters for the MBS Distribution Session as defined in table 4.5.8-1 of TS 26.502 [6]. The User Plane security mechanisms between the MBS client and the MBSSF are defined in clause W.4.1.3 of TS 33.501 [32] and clause 6 of TS 33.246 [33]. + +**Table 5.2.10-1: Semantics of *SecurityDescription* object** + +| Property name | Type | P | Cardinality | Description | +|--------------------------|---------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------| +| mBSSFAddresses | array(AbsoluteURL) | M | 1..1 | A list of key management servers (i.e., MBSSF instances).
At least one endpoint address shall be listed. | +| mBSServiceKeyInfo | object | M | 1..1 | Information about the MBS Service Key (MSK). | +| mSKId | string | M | 1..1 | Identifies the MSK, as defined in clause 6.3.2.1 of TS 33.246 [33]. | +| mSKDomainId | string | M | 1..1 | Identifies the MSK domain, as defined in clause 6.3.2.1 of TS 33.246 [33]. | + +| | | | | | +|--------------------|--------------------------|---|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| uICCKeysManagement | boolean | O | 0..1 | Indicates whether UICC-based key management is required for the parent MBS Distribution Session.
If false or omitted, this is not required. | +| 2GGBAallowed | boolean | O | 0..1 | Indicates whether the 2G GBA is permitted for the parent MBS Distribution Session.
If false or omitted, this is not permitted. | +| backOffParameters | BackOffParameters | O | 0..1 | The back-off behaviour of the MBSF Client when requesting MBS Service Keys (MSKs) from the MBSSF (see clause 11.2.2.2).
If present, at least one of the contained parameters shall be present.
If omitted, no back-off delay is required. | +| offsetTime | DurationSec | C | 1..1 | The minimum time that an MBSF Client shall wait after initiating reception of the parent MBS User Distribution Session before sending its first MSK request. | +| randomTimePeriod | DurationSec | C | 1..1 | The maximum time window length over which an MBSF Client shall calculate the value of RandomTime to be used as a delay to its first MSK request in addition to offsetTime . | + +## 5.3 Delivery of User Service Descriptions + +### 5.3.1 General + +This clause defines the delivery of User Service Descriptions, i.e. the delivery of a User Service Descriptions document, as well as additional resources (documents and possibly ancillary media objects) that are necessary to provide all necessary parameters required by an MBS Client to initiate one or more MBS User Services. + +The collection of all necessary resources associated with a User Service Descriptions document is referred to as a *User Service Descriptions Bundle* and is specified in clause 5.3.1A. + +A User Service Descriptions Bundle may be delivered to the MBS Client via an MBS Distribution Session at reference point MBS-4-MC (see clause 5.3.2) and/or via a regular unicast PDU Session at reference point MBS-5 (see clause 5.3.3) and/or via application-private means at reference point MBS-8. + +### 5.3.1A User Service Descriptions Bundle + +The User Service Descriptions Bundle includes a single MBS User Service Descriptions document as well as all other associated resources that are directly referenced by the MBS User Service Description(s) included in that document or indirectly referenced by other resources in the same User Service Bundle. Each associated resource included in the User Service Bundle shall have a URL and shall have a MIME content type. + +The set of resources comprising a User Service Bundle shall be aggregated into a single multipart entity, referred to as a *User Service Descriptions Bundle Entity*. Each such resource shall be encapsulated as a distinct body part of this multipart entity. The headers and body of this entity may be conveyed by different application protocols, for example as the headers and body of an HTTP message or as a multicast transmission object. Individual body parts or the entire entity body may be compressed in transit (e.g. using GZip [41]) if the application protocol supports this. + +A User Service Descriptions Bundle Entity (hereafter "entity") shall conform to the following requirements: + +- The Content-Type header of the entity shall be *multipart/related* as specified in RFC 2387 [38]. +- The root body part of the entity shall be a User Service Descriptions document as defined in clause 5.2.2. + - The type parameter of this root body part shall be present as specified in RFC 2387 [38] and shall be set to the MIME content type of the User Service Descriptions document specified in clause E.2. + +- The User Service Descriptions document shall be the first body part of the *multipart/related* entity, and hence the `start` parameter specified in RFC 2387 [38] should be absent. If present, the `start` parameter shall be set to the `content-id` of the MBS User Service Description body part. +- Every other body part in the entity shall have a URI indicated in its `Content-Location` header per RFC 2557 [39] so that it may be cross-referenced by other resources in the same entity. The value of this header may be an absolute URI, or it may be expressed as a path that can be resolved relative to the base URI of the enclosing body part using the rules specified in section 5 of [39]. +- All dependent resources of the User Service Descriptions described in the User Service Descriptions document shall be included as body parts in the entity. The User Service Descriptions document shall not use external references to any resource that it directly references. + +### 5.3.2 Delivery of User Service Descriptions Bundle Entity in object carousel + +In this case, one or more User Service Bundle Entities are delivered repeatedly by the MBSTF to the MBSTF Client via a suitable MBS Distribution Session at reference point MBS-4-MC using the Object Distribution Method, as defined in clause 4.2.4 of TS 26.502 [6]. This is the realisation of the MBS User Service Announcement Channel. The operating mode of this MBS Distribution Session shall be set to *OBJECT\_CAROUSEL* and relies on an object manifest to characterize the repetition and the update pattern of the User Service Bundle Entities in the carousel. The object manifest is specified in clause 6.1.2. The objects described by this manifest shall be User Service Bundle Entities formatted as specified in clause 5.3.1A. + +As defined in clause 5.4 of TS 26.502 [6], the MBSTF Client announces the arrival of an MBS User Service Description to the MBSF Client using a suitable notification at internal reference point MBS-7', and the MBSF Client may subsequently retrieve the MBS User Service Description from the MBSTF Client via internal reference point MBS-6'. It may do so using procedures equivalent to those specified for unicast retrieval at reference point MBS-5 (see clause 5.3.3). In this case, the MBSTF Client acts as a proxy for the MBS AF. + +### 5.3.3 Delivery of User Service Descriptions Bundle Entity via unicast PDU Session + +In this case, a result set of one or more User Service Descriptions Bundle Entities is retrieved by the MBSF Client from the MBS AF at reference point MBS-5 via a regular unicast PDU Session. + +The API at this reference point is specified in clause 9.2 and the format of the response is specified in clause 9.2.3. The OpenAPI [14] specification of the User Service Description retrieval API can be found in clause A.2. + +# 6 Object Distribution Method + +## 6.1 General + +### 6.1.1 Overview + +The Object Distribution Method supports the transmission of media segments, e.g. CMAF media segments [7] and also non-real-time objects. + +The MBS Distribution Session shall be provisioned to accommodate the bit rate of the aggregated object flow, accounting for in-band carriage of metadata units, protocol header overheads, and FEC redundancy (if configured). + +### 6.1.2 Object manifest + +An object manifest document describes a list of objects to be distributed in an MBS Distribution Session. The syntax of the object manifest is specified in clause D.1. The semantics of the document are specified in table 6.1.2-1 below. + +For each object to be delivered in the MBS Distribution session, the attributes under the *objects* property in table 6.1.2-1 shall be maintained by the MBSTF. + +**Table 6.1.2-1: Properties of object manifest** + +| Property name | Cardinality | Description | +|----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| updateInterval | Optional | The time interval, expressed in seconds, according to which the MBSTF attempts to re-acquire the object manifest when pull-based object acquisition is provisioned.
Ignored by the MBSTF for push-based object acquisition. | +| objects | Mandatory | The list of objects to be carouselled from the MBSTF to the MBSTF Client. | +| locator | Mandatory | The URL from which the object is to be ingested by the MBSTF. | +| repetitionInterval | Optional | The time interval, expressed in milliseconds, according to which the object is to be periodically sent to the MBSTF Client.
If omitted, the MBSTF determines the repetition interval for the object.
Ignored by the MBSTF in Object Collection operating mode. | +| keepUpdatedInterval | Optional | The time interval, expressed in seconds, according to which the MBSTF is expected to check for updates made to the object at its origin (as indicated by locator or a redirect from there to another location).
In case of conflicting information, the MBSTF should give precedence in determining the update interval to the HTTP cache control metadata included in the HTTP response from the object origin.
Any changes to the origin object that are detected by the MBSTF shall be reflected in the MBS Distribution Session at the earliest opportunity and the replacement of one object with another shall be signalled to the MBSTF Client by means of the object transport protocol provisioned at reference point MBS-4-MC.
If omitted, the MBSTF shall not attempt to check for updates to the object.
Ignored by the MBSTF in Object Collection operating mode. | +| earliestFetchTime | Optional | The MBSTF shall fetch the object no sooner than this UTC timestamp. If absent, then the object shall be present at its origin (as indicated by locator or a redirect from there to another location) and the MBSTF may fetch it at a time of its choosing. | +| latestFetchTime | Optional | The MBSTF shall fetch the object no later than this UTC timestamp. If absent, then the object shall be present at its origin (as indicated by locator or a redirect from there to another location) and the MBSTF may fetch it at a time of its choosing. | + +## 6.2 Usage of FLUTE for Object Distribution Method + +### 6.2.1 General + +If FLUTE [12] is used to realise the Object Distribution Method, the MBS Distribution Session shall conform to the MBMS Download Profile as defined in clause L.4 of TS 26.346 [7] with the additional requirements in clause 6.2 of the present document. + +The usage of this distribution method is identified in the MBS Session Description metadata unit as defined in clause 6.2.3, in particular by the indication of the protocol FLUTE/UDP in combination with the MBS service type. + +The MBSTF shall use the Profiled FDT Schema according to clause L.6 of TS 26.346 [7] to describe the object list currently being transmitted in the MBS Distribution Session. + +Generally, the end of transmission of an object is the expiry time for the latest FDT instance describing the object. Objects shall be described in an FDT Instance with the *Expires* attribute. Depending on the operating mode (clause 6.2.4), different settings of the expiry time and different numbers of objects per FDT Instance are recommended. + +Inclusion of the @Content-MD5 and @File-ETag FDT Instance attributes is optional. + +The @File-ETag represents the value of the HTTP entity tag as defined in clause 8.8.3 of RFC 9110 [19] which may also serve as the version identifier of the **File** object described by the FDT Instance. + +In order to fetch missing portions of an object, the MBS Client may use the Object Repair mechanism for FLUTE specified in clause 6.2.4. This mechanism is provided by the MBS AS at reference point MBS-4-UC, using the User Service Announcement parameters specified in clause 5.2.8 to identify its endpoint address. + +### 6.2.2 Session Description document for FLUTE + +#### 6.2.2.1 General + +The Session Description document for FLUTE contains the information needed to activate the reception of an MBS Distribution Session using the FLUTE protocol [12] when this is used to realise the Object Distribution Method. The Session Description document is formatted according to the Session Description Protocol [8] and its content is based on the Session Description parameters specified in clause 7.3 of TS 26.346 [7] with the following restrictions and extensions. + +Restrictions: + +- The *Mode of MBMS bearer per media* parameter (clause 7.3.2.7 of [7]) shall not be used. +- The *QoE Metrics* (as defined in clauses 7.3.2.0 of [7]) shall not be used +- The *Service-language(s) per media* (clause 7.3.2.9 of [7]) shall not be used. It is assumed that the service languages are described within an application manifest. +- The *Alternative TMGI* (clause 7.3.2.12 of [7]) shall not be used. +- The *Start time* and *End time* of the session (SDP *t*-line) shall indicate a superset of the active times specified in the MBS Schedule Description metadata unit in the service schedule descriptions of the MBS Distribution Session (see clause 5.2.7), if present. If there is no service schedule specified, both values of the SDP *t*-line should be set to zero indicating undefined times. + +Extensions: + +- When an MBS Session is of MBS Service Type *Broadcast* or when the Multicast MBS Session Type uses a TMGI as MBS Session ID, the *MBS service type of MBS Session* declaration attribute as defined in clause 6.2.2.2 shall be present in the Session Description. + +#### 6.2.2.2 MBS service type of MBS Session + +A new MBS service type declaration attribute *mbs-servicetype* is defined which results in, e.g.: + +- *a=mbs-servicetype:broadcast 123869108302929* + +or: + +- *a=mbs-servicetype:multicast 123869108302929* + +The MBS service type declaration attribute shall be used in Session Description metadata to indicate the type of the corresponding MBS Distribution Session as defined in table 6.2.2.2-1. + +**Table 6.2.2.2-1: Assignment of mbs-servicetype attribute value** + +| Attribute value | Meaning | +|------------------|--------------------------------------------------------------------------| +| multicast | The MBS Distribution Session is delivered using a Multicast MBS Session. | +| broadcast | The MBS Distribution Session is delivered using a Broadcast MBS Session. | + +The MBS service type attribute shall be declared at session level in the Session Description metadata unit. The session level attribute applies to all media entries without a media-level occurrence of the *mbs-servicetype* attribute. The Session Description metadata unit shall include only a single instance of MBS service type declaration attribute. + +Definition: + +- *mbs-service-type-declaration-line = "a=mbs-servicetype:" ("broadcast"/"multicast" SP *tmgi*) CRLF* +- *tmgi = 1\*15DIGIT* + +EXAMPLE: + +UK MCC = 234 (*MCC Digit 1 = 2; MCC Digit 2 = 3 and MCC Digit 3 = 4*) + +Vodafone UK MNC = 15 + +and, with padding, Vodafone UK MNC = 15F (*MNC Digit 1 = 1; MNC Digit 2 = 5 and MNC Digit 3 = F*) + +MBS Service ID = 70A886 + +Therefore, TMGI = 70A886 32F451 (Hex) or 123869108302929 (Decimal) + +The Temporary Mobile Group Identity (*tmgi*) information element is defined in TS 24.008 [11] including the coding of the fields. Octets 3 to 8 (MBS Service ID, MCC and MNC) shall be placed in the *tmgi* attribute of the MBS service type declaration line, and are encoded as a decimal number. Octet 3 is the most significant octet. Because this is encoded as a decimal number, leading zeros of the MBS Service ID field may be omitted. + +#### 6.2.2.3 SDP examples for FLUTE Session + +Listing 6.2.2.3-1 provides a full example of an SDP description describing a FLUTE-based MBS Distribution Session using the Object Distribution Method with a TMGI as MBS Session Id. + +##### **Listing 6.2.2.3-1: Session Description metadata unit for FLUTE-based MBS Distribution Session with TMGI** + +``` +v=0 +o=user123 2890844526 2890842807 IN IP6 2201:056D::112E:144A:1E24 +s=Object Distribution session example +i=More information +t=2873397496 2873404696 +a=mbs-servicetype:broadcast 123869108302929 +a=FEC-declaration:0 encoding-id=1 +a=source-filter: incl IN IP6 * 2001:210:1:2:240:96FF:FE25:8EC9 +a=flute-tsi:3 +m=application 12345 FLUTE/UDP 0 +c=IN IP6 FF1E:03AD::7F2E:172A:1E24/1 +b=1000 +a=lang:EN +a=FEC:0 +``` + +Listing 6.2.2.3-2 provides a second example of an SDP description describing a FLUTE-based MBS Distribution Session using the Object Distribution Method and which indicates that 25% redundant FEC protection is applied to the FEC encoding of the video Segments of the associated DASH-formatted content. + +##### **Listing 6.2.2.3-2: Session Description metadata unit for FLUTE-based MBS Distribution Session with TMGI and 25% FEC redundancy** + +``` +v=0 +o=user123 2890844526 2890842807 IN IP6 2201:056D::112E:144A:1E24 +s=Object Distribution session carrying 2-hour DASH-packaged programme +i=More information +t=3615124600 3615131800 +a=mbs-servicetype:broadcast 123869108302929 +a=FEC-declaration:0 encoding-id=1 +a=FEC-redundancy-level:0 redundancy-level=25 +a=source-filter: incl IN IP6 * 2001:210:1:2:240:96FF:FE25:8EC9 +a=flute-tsi:5 +m=video 10111 FLUTE/UDP 0 +c=IN IP6 FF1E:03AD::7F2E:172A:1E24/1 +b=2048 +a=lang:EN +``` + +### 6.2.3 Operating modes for FLUTE-based Object Distribution Method + +#### 6.2.3.1 Introduction + +The operating modes for the Object Distribution Method are defined in clause 6.1 of TS 26.502 [6]. Operating modes primarily describe the operation of the MBSTF to convert ingest data into an MBS Distribution Session. The following clauses specify how FLUTE is used for each operating mode. + +The Object Repair mechanism for FLUTE specified in clause 6.2.4 may be used with the following operating modes: + +- *OBJECT\_SINGLE*, as specified in clause 6.2.3.2; +- *OBJECT\_COLLECTION*, as specified in clause 6.2.3.3; or +- *OBJECT\_CAROUSEL*, as specified in clause 6.2.3.4. + +The Object Repair mechanism for FLUTE shall not be used with the *OBJECT\_STREAMING* mode (as specified in clause 6.2.3.5) in this Release. + +#### 6.2.3.2 Single object operating mode + +Single object operating mode (*OBJECT\_SINGLE*) refers to the case in which a single object is distributed via the Object Distribution Method. + +No specific aspects beyond the general provisions in clauses 6.1, 6.2.1 and 6.2.2 apply to this operating mode. + +#### 6.2.3.3 Object collection operating mode + +Object collection operating mode (*OBJECT\_COLLECTION*) refers to the case in which multiple objects are distributed via the Object Distribution Method. The list of objects to be distributed is described by an object manifest document as specified in clause 6.1.2. The objects listed in the manifest are distributed only once. Each object listed in the manifest is pulled by the MBSTF from the location indicated prior to inclusion in the FLUTE Session corresponding to the MBS Distribution Session. + +In this operating mode, each FDT Instance delivered in the FLUTE Session should describe all objects that are currently part of the collection. + +#### 6.2.3.4 Object carousel operating mode + +Object carousel operating mode (*OBJECT\_CAROUSEL*) refers to the case in which one or multiple objects are distributed via the Object Distribution Method in a repeated fashion. The list of objects to be distributed is described by an object manifest document as specified in clause 6.1.2. Each object listed in the manifest is pulled by the MBSTF from the location indicated prior to inclusion in the FLUTE Session corresponding to the MBS Distribution Session. + +The list of objects described in the manifest may be updated over time by providing a replacement object manifest. + +In this operating mode, the FDT Instance should describe all objects that are currently available in the FLUTE Session, considering the potential object update interval. + +#### 6.2.3.5 Segment streaming operating mode + +Segment streaming operating mode (*OBJECT\_STREAMING*) refers to the case for which a sequence of objects, typically representing timed segments from a timed presentation, are distributed using the Object Distribution Method. The sequence of objects is referred to as an *object flow*. This operating mode is recommended for streaming DASH or HLS content to a Media Player in the UE using MBS User Services. + +NOTE: This operating mode may also be used for non-media object flows, e.g. in the absence of an Application Service Description. + +For each object associated with the object flow to be delivered in the MBS Distribution Session the following information shall be maintained by the MBSTF in an object list: + +- The URL used by the MBS-Aware Application to request the object, derived from the object ingest URL. +- The object's *latest availability start time* at the MBS Client. After this time, the MBS-Aware Application may request the full object from the MBSTF Client by using the URL of the object. + +This value is determined for each object based on an availability start time at the point of ingest (i.e. reception of first byte of the object) combined with a configured distribution offset. + +- The object's *availability end time* from the MBSTF Client. After this time, the object may no longer be requested by the MBS-Aware Application. + +This value is determined for each object based on an availability start time at the point of ingest (i.e. reception of first byte of the object) combined with a configured clean-up time. + +The object list is typically extended over time, for example as new objects (e.g. media segments) become available. + +The object list may, for example, be provided by an explicit object distribution manifest. + +NOTE: An object distribution manifest format is not defined in the present document. + +The object list may also be defined by a presentation manifest (e.g. DASH MPD), for example in the case of an Application Service, for which the manifest is provided as part of the User Service Description. + +When the Application Service Entry Point document is a DASH MPD, this document is used by the MBSTF to update the object list. The DASH MPD may itself be included in the object list, and hence be delivered in band with the media segment objects it describes on the same MBS Distribution Session. If the content of the Application Service Entry Point document changes during an MBS User Data Ingest Session, the updated document shall be reflected in the MBS Distribution Session at the soonest opportunity. + +For the segment streaming operating mode, the MBSTF acts as follows based on the object list: + +- The MBSTF shall transmit each object in the object list such that the last packet of the delivered FLUTE transmission object (including any FEC recovery packets, when configured) is available at the MBSTF Client no later than its *availability start time*. When the Application Service Entry Point document is a DASH MPD, the availability start time is signalled in this document. +- An FDT Instance object should be sent frequently by the MBSTF, describing all objects of the object list that are not yet fully transmitted. +- The **Content-Location** element in the FDT Instance shall match the URL of the corresponding object in the object list. When the Application Service Entry Point document is a DASH MPD, this shall also match the URL of a DASH Representation described by that document after any template identifiers have been substituted. + +The URL may be rewritten by the MBSTF using the Object distribution base URL property of the MBS Distribution Session. + +- If an update to the Application Service Entry Point document is delivered as a FLUTE transmission object then the Content-Location element in the FLUTE File Delivery Table for the delivered object shall match the URL of the referenced Application Service Entry Point document. +- The **File@Expires** attribute for each object shall be set such that it is equal to or earlier than its *latest availability start time*. +- The **Cache-Control@Expires** attribute shall be used to indicate the *availability end time of the object*. +- **Content-MD5** and **File-ETag** may optionally be used. + +### 6.2.4 Object Repair mechanism for FLUTE + +#### 6.2.4.1 General + +In order to fetch missing portions of an object, the MBS Client shall support the post-session Object Repair procedure as specified in clause 6.2.4.2. + +If the User Service Description provides the Object Repair parameters specified in clause 5.2.8, then: + +- An MBS AS instance assigned to each active MBS User Service Session shall host all objects transmitted on its MBS Distribution Session(s) at the network location *location*. +- An MBS Client shall initiate the post-session Object Repair procedure as needed according to the procedure specified in clause 6.2.4.2. + +NOTE: The use of **File@Alternate-Content-Location-1** and **File@Alternate-Content-Location-2** to advertise the Object Repair parameters in the FLUTE FDT instance as defined in TS 26.346 [7] is not supported in MBS User Services. + +#### 6.2.4.2 Post-session Object Repair procedure + +The post-session Object Repair procedure is aligned with the File Repair procedures defined in clause 9.3 of TS 26.346 [7]. + +It is assumed that a FLUTE File Delivery Table (FDT) Instance document as defined in clauses L.4 and L.6 of TS 26.346 [7] is available in the MBS Client that contains at least the following information: + +- **FDT@Expires** attribute indicating the expiry date of the FDT Instance. +- For one or multiple transmission objects in the FLUTE session, a **File** element with: + - **File@TOI** attribute indicating the ALC Transport Object Identifier of the transmission object. + - **File@Content-Location** attribute indicating the URI of the transmission object. + - **File@Content-Length** attribute indicating the size (in bytes) of the transmission object. + - **File@File-ETag** attribute indicating the entity tag value of the transmission object. + +NOTE: Object Repair without the FDT as, for example, defined in clause 9.3.9 of TS 26.346 [7], is not specified by the present document. + +Then, based on the introduction in clause 9.3.1 of TS 26.346 [7], the MBS Client generally acts as follows. + +1. The MBS Client identifies the end of the MBS Distribution Session. The latest time for this is the value of the **@Expires** attribute indicated in the root element of the FDT Instance document. However, according to clause 9.3.2 of TS 26.346 [7], an MBS Client may determine an earlier end of transmission of files, + - a) if an end-of-session signal (A-flag) is received in an ALC/FLUTE header in the ongoing Object Distribution Session before the FDT instance expires; or + - b) if the end of file transmission time is reached according to the service schedule description specified in clause 5.2.7. +2. The MBS Client identifies that data is missing from an MBS Object Distribution Session for one or multiple FLUTE transmission objects delivered in the Object Distribution Session following the principles in clause 9.3.3 of TS 26.346 [7]. +3. The MBS Client shall select an MBS AS instance *repair URL* randomly from the list of **objectRepairBaseLocators** if present in the **ObjectRepair** object defined in table 5.2.8-1. +4. For each incomplete FLUTE transmission object defined by a **File** element in the FDT Instance document and as identified in step 2: + - a) The MBS Client shall form the network location *location* (URL) of the repair object as defined in clause 6.4.2.4 using (i) the value of the **File@Content-Location** attribute, (ii) the *repair URL* selected in step 3 (if any) and (iii) the value of **objectDistributionBaseLocator** as *distribution URL* if present in the **ObjectRepair** object defined in table 5.2.8-1. + - b) The MBS Client shall define an appropriate *list of byte ranges* **Range[M]** with *M* the number of independent ranges and **Range[m].start** the start of the *m*th range and **Range[m].end** the end of the *m*th range from the repair object using the list of received symbols and additional information from the FDT as defined in clause 6.4.2.5. +5. The MBS Client shall then use the object repair procedures as defined as defined in clause 10.2.2 using the following parameters: + - The **offsetTime** and **randomTimePeriod** parameters indicated in the **ObjectRepair** object as defined in table 5.2.8-1. + - For each incomplete FLUTE transmission object in the FDT Instance document, the MBSTF Client shall use from the corresponding FDT **File** entry the network location *location* formed in step 4a, the size of the transmission object (in bytes), the entity tag value and the minimal *list of byte ranges* **Range[M]** determined in step 4b. + +6. The MBS Client uses the received *list of byte ranges* and the received data in the MBS Object Distribution Session to recover the missing object as defined in clause 6.4.2.6. + +#### 6.2.4.3 In-session object repair procedure + +This procedure is for future study. + +#### 6.2.4.4 Network location of repair object + +The determination of the network location *location* of the repair object uses the **File@Content-Location** attribute in the FDT Instance document, a *repair base URL* (if present) and a *distribution base URL* (if present) as follows: + +- If the *repair base URL* is not present, then the network location of the repair object is the value of **File@Content-Location**. +- If the *repair base URL* is present, but not the *distribution base URL*, then the network location of the repair object is the value of **File@Content-Location** with the Retrieval URI according to RFC 3986 [34] replaced with the *repair base URL*. +- If both the *repair base URL* and the *distribution base URL* are both present, then the network location of the repair object is the value of **File@Content-Location** with the Base URI according to RFC 3986 [34] being the *distribution base URL* replaced with the *repair base URL*. + +Additionally, if the **File@Content-Encoding** attribute is present in the FDT Instance document and is set to the value **gzip**, then a ".gz" extension shall be appended to the path part of the repair object's *location* prior to the query part of the URL, if any. In this case, the GZipped [41] version of the repair object shall be hosted on the MBS AS. The MBSTF Client shall only use this in connection with a byte range request if the **@File-ETag** attribute is present in the FDT Instance of that object, for use as the entity-tag in the request. Otherwise, the MBSTF Client shall request the complete object from the MBS AS. + +#### 6.2.4.5 Byte range determination + +The selection of the byte range is aligned with clause 9.3.6.2 of TS 26.346 [7]. This clause focuses on the selection of a sufficient byte range for an individual FLUTE transmission object requiring repair. For each damaged transmission object, FDT parameters are assumed to be available. + +NOTE: This clause does not address protocol-related aspects specified in clause 9.3.6.2 of TS 26.346 [7]; these are specified in clause 10 of the present document. + +The MBS Client shall identify a *minimal set of source symbols* identified by a list of Encoding Symbol Identifiers (ESIs) that, combined with the already received symbols, allows the FEC decoder to recover the file as follows: + +- When the Compact No-Code FEC scheme is used (i.e., if the FDT parameter **@FEC-OTI-FEC-Encoding-ID** is set to 0), the MBS Client shall consider already received source symbols when making the determination of the repair byte range symbols. The MBS Client shall identify the ESIs of the missing source symbols which constitute the minimal set. +- When the Raptor FEC scheme is used (i.e., if the FDT parameter **@FEC-OTI-FEC-Encoding-ID** is set to 1), the MBS Client shall consider already received source and repair symbols when making the determination of the repair byte range required. In particular, the MBS Client shall identify a minimal set of source symbols that, combined with the already received symbols, allows the Raptor FEC decoder to recover the file. + +NOTE: One way to determine a minimum set of source symbols for repair is described in clause 6.1.3.1 of TR 26.946 [35]. However, any set of symbols that has the same number of necessary source symbols as the set determined according to clause 6.1.3.1 of [35] may be considered a minimal set. + +Once a minimal set of sufficient source symbols for recovery is determined as an ordered list of ESIs, $SS[0], \dots, SS[N-1]$ , with $N$ the total number of source symbols, the list of source symbols is converted to an ordered list of $M$ independent byte ranges $Range[M]$ indexed from 0 in which $Range[m].start$ is the start of the $m$ th range and $Range[m].end$ is the end of the $m$ th range. In the pseudocode presented in listing 6.2.4.5-1, $T$ is the value of the `File@FEC-OTI-Encoding-Symbol-Length` FDT attribute, and $F$ is the value of the `File@Content-Length` FDT attribute. + +**Listing 6.2.4.5-1: Pseudocode for determining repair byte ranges** + +``` +m=-1; +for (n=0; n < N; n++) { + if (n > 0 && SS[n] == (SS[n-1] + 1)) { // Extend same range + Range[m].end += T + } + else { // New Range + m++; + Range[m].start = SS[n] * T; + Range[m].end = Range[m].start + T; + } +} +Range[m].end = min(F, Range[m].end) +``` + +$Range[M]$ then describes the smallest list of byte ranges needed to recover the damaged FLUTE transmission object. + +NOTE: When $M = 1$ , $Range[0].start = 0$ and $Range[0].end = F$ the range describes the entire object. + +#### 6.2.4.6 Object recovery procedure + +Using the byte ranges recovered from the MBS AS, the MBSTF Client shall: + +1. Convert the received data into source symbols with appropriate ESIs. +2. Apply FEC decoding using the originally received symbols and those recovered from the MBS AS. +3. Recover the transmission object together with the corresponding metadata in the FDT. +4. Make the recovered object (along with its metadata) available to the MBS-Aware Application from its Media Server via reference point MBS-7. + +# 7 Packet Distribution Method + +## 7.1 General + +The Packet Distribution Method reuses different delivery concepts from TS 26.346 [7]. Additional distribution methods may be defined in future. + +## 7.2 Re-using MBMS Delivery Method as Packet Distribution Method + +### 7.2.1 General + +The Packet Distribution Method combines three different delivery methods of TS 26.346 [7] (namely the MBMS Streaming Delivery Method, Group Communication Delivery Method and Transparent Delivery Method) into a single distribution method, with a set of modifications. + +For the Packet Distribution Method, the MBSTF may handle the ingested content on two different protocol layers according to the operating mode provisioned for the MBS Distribution Session: + +- *Proxy mode*: The MBSTF handles UDP packet payloads and forwards UDP packet payloads from ingest into the MBS Distribution Session. The MBSTF may use different UDP ports for the MBS Distribution Session. The MBSTF re-uses the Proxy Mode of the Transparent Delivery Method as defined in clause 8B of [7]. +- *Forward-only mode*: The MBSTF receives complete IP packets and forwards the ingested packets as MBS PDUs. The MBSTF re-uses the Group Communication Delivery Method as defined in clause 8A of [7] and the Forward-Only Mode of the Transparent Delivery Method as defined in clause 8B of [7]. + +NOTE: A specific treatment of RTP sessions, for example as provided by the MBMS Streaming Delivery Method, is not provided by MBS User Services. However, RTP sessions may be delivered in proxy or forward-only mode. + +### 7.2.2 Void + +### 7.2.3 Session Description + +#### 7.2.3.1 General + +The Session Description document contains the needed information to activate the reception of a Packet Distribution Method. The Session Description document is formatted according to the Session Description Protocol [8]. The Session Description document for the Packet Distribution Method is based on the Session Description parameters as defined in clauses 8.3, 8A.3 and 8B.3 of TS 26.346 [7] with the following restrictions and extensions. + +Restrictions: + +- The *Mode of MBMS bearer per media* parameter (clauses 8.3.1.5 and 8B.3.2 of [7]) shall not be used. +- The *QoE Metrics* (as defined in clauses 8.3.2.1 and 8.4 of [7]) shall not be used. +- ROHC header compression (as defined in clauses 8A.4 and 8B.4 of [7]) shall not be used. + +NOTE: ROHC is handled by RAN in 5MBS. + +- The *Alternative TMGI* (clause 7.3.2.12 of [7]) shall not be used. +- The *Start time* and *End time* of the session (SDP *t* line) shall indicate a superset of the active times specified in the MBS Schedule Description metadata unit, if present in the service schedule descriptions of the MBS Distribution Session (see clause 5.2.7). If there is no service schedule specified, both values of the SDP *t*-line should be set to zero indicating undefined times. + +Extensions: + +- When the MBS User Service is of MBS Service Type *Broadcast* or when an MBS User Service of type *Multicast* uses a TMGI as its MBS Session ID, the *MBS service type of MBS Session* declaration attribute as defined in clause 6.2.2.2 shall be present in the Session Description. + +#### 7.2.3.2 SDP examples for Packet Distribution Method + +Below is a full example of SDP description describing the media streams part of an MBS Packet Distribution session for RTP streaming: + +##### Listing 7.2.3.2-1: Session description for RTP streaming + +``` +v=0 +o=ghost 2890844526 2890842807 IN IP4 192.168.10.10 +s=3GPP MBS Packet Distribution SDP Example +i=Example of MBS Packet Distribution SDP file +u=http://www.infoserver.example.com/ae600 +e=ghost@mailserver.example.com +c=IN IP6 FF1E:03AD::7F2E:172A:1E24 +t=0 0 +b=AS:77 +a=mbs-mode:broadcast 123869108302929 +a=source-filter: incl IN IP6 * 2001:210:1:2:240:96FF:FE25:8EC9 +m=video 4002 RTP/AVP 96 +b=TIAS:62000 +b=RR:0 +b=RS:600 +a=maxprate:17 +a=rtpmap:96 H264/90000 +a=fmtp:96 profile-level-id=42A01E; packetization-mode=1; sps-parameter-sets=Z0IACpZTBYmI,aMljiA== +``` + +The following is a full example of SDP description for transparent streaming with two MPEG-2 Transport Streams: + +###### Listing 7.2.3.2-2: Session description for MPEG-2 Transport Stream + +``` +v=0 +o=ghost 2890844526 2890842807 IN IP4 192.168.10.10 +s=3GPP MBS Transport-only SDP Example +i=Example of MBS transport-only SDP file +u=http://www.infoserver.example.com/ae600 +e=ghost@mailserver.example.com +c=IN IP6 FF1E:03AD::7F2E:172A:1E24 +t=3034423619 3042462419 +b=AS:8000000 +a=mbs-mode:broadcast 123869108302929 + +a=source-filter: incl IN IP6 * 2001:210:1:2:240:96FF:FE25:8EC9 +m=video 4002 UDP/RTP/AVP 96 +b=TIAS:4000000 +a=mms-framing-header:0 2 +a=rtpmap:100 MP2T/90000 +m=video 4002 RTP/AVP 98 +b=TIAS:4000000 +a=rtpmap:100 MP2T/90000 +a=MBS-framing-trailer:0 2 +``` + +# 8 General aspects of APIs for MBS User Services + +## 8.1 HTTP resource URIs and paths + +The resource URI used in each HTTP request to the API provider shall have the structure defined in subclause 4.4.1 of TS 29.501 [16], i.e.: + +*{apiRoot} / {apiName} / {apiVersion} / {apiSpecificResourceUriPart}* + +with the following components: + +- *{apiRoot}* shall be set as described in TS 29.501 [16]. +- *{apiName}* shall be set as defined by the following clauses. +- *{apiVersion}* shall be set to "v1" in this release. +- *{apiSpecificResourceUriPart}* shall be set as described in the following clauses. + +## 8.2 Usage of HTTP + +### 8.2.1 HTTP protocol version + +#### 8.2.1.1 General + +Content interfaces at reference points specified in the present document shall expose an HTTP/1.1 [21] endpoint to API clients. They may additionally expose an HTTP/2 [22] endpoint, including support for the HTTP/2 starting mechanisms specified in section 3 of [22]. The API client may choose any supported HTTP protocol version. TLS [24] shall be supported on these interfaces and, where the option to use cleartext HTTP is available in the version of HTTP selected by the API client, it should opt for HTTPS interactions in preference. + +#### 8.2.1.2 MBSF + +The HTTP protocol version used to invoke *Nmbsf* service operations on the MBSF at reference point Nbm10 is specified in clauses 6.1.2.1 and 6.2.2.1 of TS 29.580 [17]. + +#### 8.2.1.3 MBSTF + +The HTTP protocol version used to invoke *Nmbstf* service operations on the MBSTF at reference point Nbm2 is specified in clause 6.1.2.1 of TS 29.581 [18]. + +The endpoint exposed by the MBSTF to the MBSF at reference point Nbm2 for the purpose of pushing object manifests into the MBSTF shall comply with the general provisions specified in clause 8.2.1.1. + +The endpoint exposed by the MBSTF to the MBS Application Provider (AF/AS) at reference point Nbm8 for the purpose of pushing objects into the MBSTF shall comply with the general provisions specified in clause 8.2.1.1. + +#### 8.2.1.4 MBS AF + +The endpoint exposed by the MBS AF to the MBSF Client at reference point MBS-5 for the purpose of retrieving User Service Descriptions using the API specified in clause 9.2 shall comply with the general provisions specified in clause 8.2.1.1. + +The endpoint exposed by the MBS AF to the MBSTF at reference point MBS-11 for the purpose of retrieving object manifests and User Service Descriptions shall comply with the general provisions specified in clause 8.2.1.1. + +All responses from the MBS AF that carry a message body shall include a strong entity tag in the form of an ETag response header field and a modification timestamp in the form of a Last-Modified response header per section 8.8 of RFC 9110 [19]. + +All endpoints exposed by the MBS AF shall support conditional HTTP requests using the header fields `If-none-Match` and `If-Modified-Since` per section 13 of RFC 9110 [19]. + +#### 8.2.1.5 MBS AS + +The endpoint exposed by the MBS AS to the MBSTF Client at reference point MBS-4-UC for the purpose of unicast object repair shall comply with the general provisions specified in clause 8.2.1.1. + +Byte range requests per section 14 of RFC 9110 [19] shall be supported by the MBS AS at reference point MBS-4-UC for the purpose of efficient unicast object repair by the MBSTF Client. + +#### 8.2.1.6 MBSSF + +The endpoint exposed by the MBSSF to the MBSF Client at reference point MBS 10 for the purpose of MBS Service Key (MSK) retrieval shall comply with the general provisions specified in clause 8.2.1.1. + +All responses from the MBSSF that carry a message body shall include a strong entity tag in the form of an ETag response header field and a modification timestamp in the form of a Last-Modified response header per clause 8.8 of RFC 9110 [19]. + +All endpoints exposed by the MBSSF shall support conditional HTTP requests using the header fields `If-none-Match` and `If-Modified-Since` per clause 13 of RFC 9110 [19]. + +### 8.2.2 HTTP message bodies for API resources + +Individual APIs in the present document specify the syntax and encoding of HTTP request and response message bodies. MIME content types for a subset of these are registered in annex E. + +Message bodies compressed using GZip [41] content encoding may be returned by HTTP servers if the client indicates that this is acceptable per clause 12.5.3 of RFC 9110 [19]. In this case the content encoding is indicated as specified in clause 8.4 of RFC 9110 [19]. + +### 8.2.3 Usage of HTTP headers + +#### 8.2.3.1 General + +Standard HTTP headers shall be used in accordance with clause 5.2.2 of TS 29.500 [15], encoded appropriately for the version of HTTP in use. + +#### 8.2.3.2 User Agent identification + +##### 8.2.3.2.1 General + +When one of the MBS User Services functions defined in TS 26.502 [6] makes requests to an HTTP endpoint specified in the present document, it shall identify itself to the HTTP server using a `User-Agent` request header field (see section 10.1.5 of RFC 9110 [19]) that includes a *product* identifier indicating the type of client function making the request in its *token* element. + +The optional *product-version* suffix shall be present and should indicate the version number of the present document (without the leading "V") with which the client implementation complies and shall, at minimum, indicate the 3GPP release number with which the implementation complies. + +The `User-Agent` request header field may also include *comment* elements (see section 5.6.5 of RFC 9110 [19]) following the above specified *product* identifier, as well as additional vendor-specific *product* identifiers and *comment* elements compliant with the syntax and guidance provided in section 10.1.5 of RFC 9110 [19]. + +EXAMPLE 1: MBSTF/17.4.0 (build2114) libhttp/1.23.2 + +EXAMPLE 2: MBSFClient/17 + +##### 8.2.3.2.2 MBSF identification + +When invoking the *Nmbstf* service at reference point Nmb2, the MBSF identifies itself to the MBSTF using a *User-Agent* request header as specified in clauses 6.1.2.2.1 and 6.2.2.2.1 of TS 29.580 [17]. + +##### 8.2.3.2.3 MBSTF identification + +When ingesting content using the pull-based object acquisition method (see table 4.5.6-2 of TS 26.502 [6]), the MBSTF shall identify itself to the MBS Application Provider (AF/AS) at reference point Nmb8 and to the MBS AF at reference point MBS-11 using a *User-Agent* request header field that complies with the general provisions specified in clause 8.2.3.2.1. The product identifier *token* shall be set to the value *MBSTF*. + +##### 8.2.3.2.4 MBSF Client identification + +The MBSF Client shall identify itself to the MBS AF at reference point MBS-5 and to the MBSSF at reference point MBS-10 using a *User-Agent* request header field that complies with the general provisions specified in clause 8.2.3.2.1. The product identifier *token* shall be set to the value *MBSFClient*. + +##### 8.2.3.2.5 MBSTF Client identification + +The MBSTF Client shall identify itself to the MBS AS at reference point MBS-4-UC using a *User-Agent* request header field that complies with the general provisions specified in clause 8.2.3.2.1. The product identifier *token* shall be set to the value *MBSTFClient*. + +#### 8.2.3.3 Server identification + +##### 8.2.3.3.1 General + +When one of the MBS User Services functions defined in TS 26.502 [6] responds to an HTTP request, it shall identify itself to the requesting client using a *Server* response header (see section 10.2.4 of RFC 9110 [19]) that includes a *product* identifier indicating the type and host name of the responding server in its *token* element. The server type and host name shall be separated by a single hyphen ('-') character. + +The optional *product-version* suffix shall be present and should indicate the version number of the present document (without the leading "V") with which the server implementation complies and shall, at minimum, indicate the 3GPP release number with which the implementation complies. + +The *Server* response header field may also include *comment* elements (see section 5.6.5 of RFC 9110 [19]) following the above specified *product* identifier, as well as additional vendor-specific *product* identifiers and *comment* elements compliant with the syntax and guidance provided in section 10.2.4 of RFC 9110 [19]. + +EXAMPLE 1: MBSTF-vm10665.mno.net/17.4.0 (api=1.0.0) libsb1/2.1 libnf/1.2 + +EXAMPLE 2: MBSAF-vm10240.mno.net/17 (api=1.0.0) libsb1/2.1 libnf/1.2 + +##### 8.2.3.3.2 MBSF identification + +When responding to *Nmbstf* service operations made by the MBS Application Provider (AF/AS) at reference point Nmb10, the MBSF's *Server* response header is set as specified in clauses 6.1.2.2.1 and 6.2.2.2.1 of TS 29.580 [17]. + +##### 8.2.3.3.3 MBSTF identification + +When responding to *Nmbstf* service operations made by the MBSF at reference point Nmb2, the MBSTF's *Server* response header is set as specified in clause 6.1.2.2.1 of TS 29.581 [18]. + +When acknowledging objects published using the push-based object acquisition method by the MBSF at reference point Nmb2 or by the MBS Application Provider (AF/AS) at reference point Nmb10, the MBSTF shall identify itself using a + +Server response header field that complies with the general provisions specified in clause 8.2.3.3.1. The product identifier token shall be set to the value MBSTF. + +##### 8.2.3.3.4 MBS AF identification + +The MBS AF shall identify itself to the MBSF Client at reference point MBS-5 and to the MBSTF at reference point MBS-11 using a Server response header field that complies with the general provisions specified in clause 8.2.3.3.1. The product identifier token shall be set to the value MBSAF. + +##### 8.2.3.3.5 MBS AS identification + +The MBS AS shall identify itself to the MBSTF Client at reference point MBS-4-UC using a Server response header field that complies with the general provisions specified in clause 8.2.3.3.1. The product identifier token shall be set to the value MBSAS. + +#### 8.2.3.4 Support for conditional HTTP GET requests + +The provisions in clause 5.2.2 of TS 29.500 [15] relating to conditional GET requests using the `If-None-Match` and `If-Modified-Since` request headers apply to all Network Functions in the MBS System. In particular: + +- This is specified for invocations of the *Nmbsf* service at reference point Nmb10 in clauses 6.1.2.2.1 and 6.2.2.2.1 of TS 29.580 [17]. +- This is specified for invocations of the *Nmbstf* service at reference point Nmb2 in clause 6.1.2.2.1 of TS 29.581 [18]. + +All responses from the MBS AF at reference points MBS-5 and MBS-11 that carry a resource message body shall include: + +- a strong entity tag for the resource, conveyed in an `ETag` response header per section 8.8.3 of RFC 9110 [19], +- a resource modification timestamp, conveyed in a `Last-Modified` response header per section 8.8.2 of RFC 9110 [19], and +- a predicted time-to-live period for the resource, conveyed in a `Cache-Control: max-age` response header per section 5.2 of RFC 9111 [20]. + +All API endpoints on the MBS AF that expose the HTTP GET method shall support conditional requests using the `If-None-Match` and `If-Modified-Since` request headers per section 13.1.2 and 13.1.3 respectively of RFC 9110 [19]. API clients should not attempt to revalidate their cached copy of a resource using a conditional GET request before the indicated time-to-live period has elapsed. + +#### 8.2.3.5 Support for conditional HTTP POST, PUT, PATCH and DELETE requests + +The provisions in clause 5.2.2 of TS 29.500 [15] relating to conditional POST, PUT, PATCH and DELETE requests using the `If-Match` request header apply to all Network Functions in the MBS System. In particular: + +- This is specified for invocations of the *Nmbsf* service at reference point Nmb10 in clauses 6.1.2.2.1 and 6.2.2.2.1 of TS 29.580 [17]. +- This is specified for invocations of the *Nmbstf* service at reference point Nmb2 in clause 6.1.2.2.1 of TS 29.581 [18]. + +##### 8.2.3.3.6 MBSSF identification + +The MBSSF shall identify itself to the MBSF Client at reference point MBS 10 using a Server response header field that complies with the general provisions specified in clause 8.2.3.3.1. The product identifier token shall be set to the value MBSSF. + +## 8.3 HTTP response codes + +Guidelines for error responses to the invocation of APIs of NF services are specified in clause 4.8 of TS 29.501 [16]. API-specific error responses are specified in the respective technical specifications. + +# --- 9 MBS AF APIs (MBS-5) + +## 9.1 General + +This clause specifies the network APIs exposed by the MBS AF with reference to the general provisions of clause 8 as they apply to the reference point in question. + +## 9.2 User Service Description retrieval API + +### 9.2.1 General + +In the case where *Service announcement modes* (see table 4.5.3-1 of TS 26.502 [6]) indicates that the MBS User Service Announcement for an MBS User Service is advertised at reference point MBS-5, the User Service Description retrieval API is used by the MBSF Client to retrieve a User Service Descriptions Bundle from the MBS AF that enable reception of the MBS User Service(s) to be initiated by the MBSF Client. + +In the case where *Service announcement modes* (see table 4.5.3-1 of TS 26.502 [6]) indicates that the MBS User Service Announcement for an MBS User Service is advertised via the User Service Announcement Channel at reference point MBS-4-MC, the User Service Description retrieval API is used by the MBSF Client at reference point MBS-7' to retrieve a User Service Descriptions Bundle from the MBSTF Client that enable reception of the MBS User Service(s) to be initiated by the MBSF Client. + +In the absence of prior knowledge about which Service announcement mode(s) are configured for currently provisioned MBS User Services, an MBSF Client may use either or both of the above procedures to proactively retrieve User Service Descriptions Bundles. + +### 9.2.2 Resource structure + +The User Service Description retrieval API is accessible from the MBS AF at reference point MBS-5 and from the MBSTF Client at reference point MBS-7' through the following URL base path: + +`{apiRoot}/3gpp-mbs-user-service-discovery/{apiVersion}/` + +The operations and the corresponding HTTP methods in table 9.2.2-1 are supported through the above API base path. In each case, the sub-resource path specified in the second column shall be appended to the URL base path. The provisions of clause 8.2.3.4 shall apply to all operations. + +Table 9.2.2-1: Operations supported by the User Service Description retrieval API + +| Operation | Sub-resource path | Allowed HTTP method(s) | Description | +|------------------------------------|---------------------------------------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Discover User Service Descriptions | user-service-descriptions?
{queryParameters} | GET | Used to discover a set of User Service Descriptions that match a set of filtering criteria corresponding to at least one of the query parameters specified in table 9.2.2-2.
Multiple query parameters may be concatenated using the ampersand ('&') character as a separator with the resulting semantics of logical conjunction (i.e., Boolean AND).
It is an error to invoke this operation with no query parameters.
A User Service Descriptions Bundle (see clause 9.2.3.1) is returned containing User Service Descriptions matching all of the specified filtering criteria and their dependent resources, which may be empty if none match all of the criteria. | +| Retrieve User Service Description | user-service-descriptions/
{externalServiceId} | GET | The {externalServiceId} uniquely identifies a single User Service Description resource in the MBS AF.
If the requested User Service is known to the MBS AF, a User Service Descriptions Bundle (see clause 9.2.3.2) is returned comprising a single User Service Description and its dependent resources. Otherwise, a suitable HTTP error response code is returned. | + +Table 9.2.2-2 specifies the query parameters that may be combined with the operations specified in table 9.2.2-1. + +Table 9.2.2-2: Query parameters supported by the User Service Description retrieval API + +| Applicable operation | Filter name | Query parameter | Description | +|------------------------------------|---------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Discover User Service Descriptions | Service class | service-class=
{serviceClassTermId} | Used to select User Service Descriptions that are tagged with the supplied service class term identifier (see table 4.5.3-1 of TS 26.502 [6]), which is expressed as a fully-qualified URI string from a controlled vocabulary (e.g., OMNA BCAST Service Class [25]) with appropriate URL encoding applied. | +| | Conformance profile | profile=
{conformanceProfileTermId} | Used to select User Service Descriptions that include Distribution Session Descriptions tagged with the supplied conformance profile term identifier (see clause 12), which is expressed as a fully-qualified URI string from a controlled vocabulary (e.g., clause C.2) with appropriate URL encoding applied. | + +### 9.2.3 Response format + +#### 9.2.3.1 User Service Descriptions result + +The HTTP response message shall convey a User Service Descriptions Bundle Entity as specified in clause 5.3.1A in which the root body part is a User Service Descriptions document that includes a User Service Description for each User Service that matches the filtering criteria. This response message shall conform to the following requirements: + +- The User Service Descriptions Bundle Entity shall include any dependent resources as additional body parts per clause 5.3.1A. +- The headers of the User Service Descriptions Bundle Entity shall be conveyed in the headers of the HTTP response message. +- A strong entity tag shall additionally be conveyed in the headers of the HTTP response per clause 8.2.3.4. +- The body of the User Service Descriptions Bundle Entity shall be conveyed in the body of the HTTP response message. + +- The MBS AF may apply GZip [41] encoding to individual body parts of the User Service Descriptions Bundle Entity, or to the entity as a whole, subject to the provisions of clause 8.2.2. + +#### 9.2.3.2 User Service Description result + +The HTTP response message shall convey a User Service Bundle Entity as specified in clause 5.3.1A in which the root body part is a User Service Descriptions document that includes a single User Service Description. This response message shall conform to the following requirements: + +- The User Service Descriptions Bundle Entity shall include any dependent resources as additional body parts per clause 5.3.1A. +- The headers of the User Service Descriptions Bundle Entity shall be conveyed in the headers of the HTTP response message. +- A strong entity tag shall additionally be conveyed in the headers of the HTTP response per clause 8.2.3.4. +- The body of the User Service Descriptions Bundle Entity shall be conveyed in the body of the HTTP response message. +- The MBS AF may apply GZip [41] encoding to individual body parts of the User Service Descriptions Bundle Entity, or to the entity as a whole, subject to the provisions of clause 8.2.2. + +# --- 10 MBS AS protocols (MBS-4-UC) + +## 10.1 General + +This clause specifies the protocols between the MBSTF Client and the MBS AS with reference to the general provisions of clause 8 as they apply to these functional entities at reference point MBS-4-UC. + +The following protocols are defined in this release: + +- Unicast Object Repair protocol (clause 10.2) between the MBSTF Client and the MBS AS when the delivery of one of several objects in an MBS download delivery session using the Object Distribution Method was not completely successful. + +## 10.2 Unicast Object Repair protocol + +### 10.2.1 Overview + +This clause defines the unicast Object Repair retrieval protocol between the MBSTF Client and the MBS AS at reference point MBS-4-UC when the delivery of one of several objects in an MBS User Service Session was not completely successful. The unicast Object Repair protocol is based on HTTP [19] and the general requirements specified in clause 8.2 and 8.3 of the present document shall apply to all interactions between these two functional entities at this reference point. + +- An MBSTF Client shall implement the procedures defined in clause 10.2.2 to support the object repair protocol. +- An MBS AS shall implement the procedures defined in clause 10.2.3 to support the object repair protocol. + +### 10.2.2 MBSTF Client procedures + +#### 10.2.2.1 General + +This clause defines the MBSTF Client procedures for the unicast Object Repair protocol. + +It is assumed that at a specific time instance, the MBSTF Client is triggered to initiate the Object Repair procedures based on the parameters defined in clause 10.2.2.2. + +Once initiated, the MBSTF Client shall calculate a random *back-off time* using the `offsetTime` and `randomTimePeriod` parameters as defined in clause 10.2.2.3. The MBSTF Client shall start making repair requests as described in clause 10.2.2.3 at the computed *back-off time*. The MBSTF Client shall not start sending any repair request messages before this calculated time *back-off time* has elapsed. + +#### 10.2.2.2 Parameters + +The following parameters are assumed to be available to the MBSTF Client for unicast Object Repair: + +- The `offsetTime` parameter and the `randomTimePeriod` parameter for the back-off time computation. +- For each object with missing data: + - If available to the MBSTF Client in the MBS Distribution Session metadata, an *entity tag* value for the damaged object. + - The *length* (in bytes) of the damaged object. + - The network location *location* referring to a corresponding object hosted on the MBS AS. + - A minimally sized *list of byte ranges* of dimension `Range[M]` with *M* the number of independent ranges and `Range[m].start` the start of the range and `Range[m].end` the end of the range from the repair object. + +#### 10.2.2.3 Back-off time computation + +The computation of the *back-off time* uses the `offsetTime` parameter and the `randomTimePeriod` parameter. In particular, the MBS Client shall implement the back-off timing computation specified in clause 9.3.4 of TS 26.346 [7] as follows: + +- The value of the `offsetTime` parameter is used as the *OffsetTime* as defined in clause 9.3.4.1 of TS 26.346 [7]. +- The value of the `randomTimePeriod` parameter is used as the *Random Time Period* as defined in clause 9.3.4.2 of TS 26.346 [7] to determine a *RandomTime*. +- The back-off time is the sum of *OffsetTime* and *RandomTime*. + +#### 10.2.2.4 MBSTF Client unicast repair request + +The MBSTF Client sends one or more requests to an MBS AS instance requesting transmission of data that allows recovery of missing object data. All unicast Object Repair requests and responses for a particular MBS Distribution Session shall take place in a single HTTP session [19]. + +The MBSTF Client shall start the initial request once initiated after the back-off time, if any, has elapsed (see clause 10.2.2.3). If there is more than one repair request to be made, these are sent one straight after another without further delay. + +The MBSTF Client shall send separate HTTP GET requests for each damaged object. + +For each damaged object, based on the parameters in clause 10.2.2.2, the MBSTF Client shall act as follows: + +1. If the requested range is the entire object, i.e. *M* = 1, `Range[0].start` = 0 and `Range[0].end` = *F*, with *F* the value of the *content length*, then the HTTP GET method shall be used. +2. If the requested range is only a subset of the object, a HTTP partial GET request shall be used with the Range request header (as specified in section 14.1.2 of RFC 9110 [19]) present. + - If *M* > 1, the MBSTF Client shall include multiple byte range requests within a single partial GET request. In particular, the MBSTF Client shall include as many byte ranges as possible in a single HTTP request message without exceeding 2048 bytes for all request headers. If this length is exceeded, the request shall be split into as few requests as possible without any of those exceeding the 2048-byte limit. +3. If the *entity tag* is available to the MBSTF Client for the damaged object, it shall be used as the entity tag value in the `If-Match` or `If-Range` header of a conditional byte-range file request. + +4. If the *entity tag* is not available to the MBSTF Client for the damaged object, the MBSTF Client may omit the `If-Match` or `If-Range` header from its byte range request. + +NOTE 1: The nominal objective of the MBSTF Client using the `If-Match` header is to receive the requested range(s) of the HTTP resource representation associated with the entity tag, or no repair data if the request cannot be satisfied by the MBS AS. + +NOTE 2: The nominal objective of the MBSTF Client using the `If-Range` header is to receive the latest version of the entire HTTP resource representation in case the version associated with the entity tag that was transmitted in the MBS User Service Session and partially received by the MBSTF Client is no longer available on the MBS AS. + +### 10.2.3 MBS AS requirements + +An MBS AS instance is assigned to an MBS User Service Session and hosts all objects at a location as specified in clause 6.2.4.4. + +An MBS AS shall be an HTTP server that complies with the general provisions in clause 8.2 and 8.3 of the present document and shall respond to all requests as specified in clause 10.2.2.4. + +# --- 11 MBSSF security protocols (MBS-10) + +## 11.1 General + +This clause is applicable when the MBS User Plane Security mechanism is provisioned for an MBS User Service. This provisioning is indicated to the MBS Client by the presence of the **SecurityDescription** object in a **Distribution SessionDescription** object (see clause 5.2.10) of a User Service Description it has obtained by one of the methods specified in clause 5.3. + +## 11.2 MBS Service Key retrieval from MBSSF + +### 11.2.1 Overview + +Whenever it needs an MBS Service Key (MSK), the MBSF Client shall interact with the MBSSF at reference point MBS-10 using the protocol specified in clause 6.3 of TS 33.246 [33]. The key retrieval protocol is based on HTTP [19] and the general requirements specified in clause 8.2 and 8.3 of the present document shall apply to all interactions between these two functional entities at this reference point. + +### 11.2.2 MBSF Client procedures + +#### 11.2.2.1 MBSSF endpoint selection by MBSF Client + +Aligned with TS 26.346 [7], before communicating with the MBSSF as part of an MBS User Service Session, the MBSF Client shall first choose an MBSSF endpoint address from those listed in the `mBSSFAddresses` property of the **SecurityDescription** object specified in table 5.2.10-1. The MBSF Client shall use the same endpoint address for all subsequent requests to the MBSSF relating to that MBS User Service Session. + +If the MBSSF at the chosen endpoint address proves to be unresponsive after a number of retry attempts, a different endpoint shall be chosen by the MBSF Client from those listed, if any. + +#### 11.2.2.2 Back-off time computation + +When the back-off mode parameters are present in the **SecurityDescription** object, these are used to calculate a random back-off time as specified in clause 6.3.2.1A of TS 33.246 [33] and clause 11.3.1 of TS 26.346 [7] in order to avoid overloading the MBSSF. + +In case of an MSK request, the MBSF Client shall calculate the random *back-off time* according to clause 10.2.2.3 of the present document, using the *offsetTime* and *randomTimePeriod* parameters indicated in the *backOffParameters* object as specified in table 5.2.10-1. + +# --- 12 Conformance profiles for MBS Distribution Sessions + +## 12.1 Definition + +This clause defines conformance profiles used to characterise MBS Distribution Sessions. + +MBS Distribution Sessions are characterized by features that are required for the consumption of the MBS Distribution Session. An MBS Client needs to support all features of the MBS Distribution Session in order to consume the MBS Distribution Session. + +Conformance profiles are defined to enable interoperability and the signalling of the use of features. + +A conformance profile imposes a set of specific restrictions: + +- It may constrain features of the MBS Distribution Session, i.e. the Distribution Method in use. +- It may constrain the content delivered within the MBS Distribution Session, such as the media content types, media format(s), codec(s), and protection formats. +- It may constrain quantitative parameters, such as bit rate. + +NOTE: A conformance profile can also be understood as permission for an MBS Client that only implements the features required by the profile to process the MBS Distribution Session. + +Conformance profiles defined in the present document constrain features specified in the present document. Externally defined conformance profiles may additionally impose restrictions on other aspects. + +## 12.2 Identification of conformance profile + +A conformance profile is uniquely identified by a fully-qualified term identifier URI from a controlled vocabulary. The term identifiers in the controlled vocabulary shall conform to either the *pro-simple* or *pro-fancy* productions specified in section 4.5 of IETF RFC 6381 [29], without the enclosing *DQUOTE* characters, i.e. only the *unencodedv* or *encodedv* productions respectively. + +- Profile identifiers defined in the present document shall be URNs conforming to IETF RFC 8141 [27]. A controlled vocabulary of conformance profiles defined in the present document is specified in clause C.2. +- Externally defined conformance profiles may use profile identifiers that are URNs conforming to IETF RFC 8141 [27] or URLs conforming to IETF RFC 3986 [34]. + - When a URL is used, it should also contain a date specifier in the form YYYY-MM. The assignment of the URL shall be authorized by the owner of the domain name in the *authority* part of the URL on or very close to that date, to avoid problems when domain names change ownership. + +## 12.3 Semantics of conformance signalling in User Service Description + +The `conformanceProfiles` property as defined in clause 5.2.4 indicates a list of profiles to which an MBS Distribution Session conforms. + +The MBS Distribution Session shall conform to every profile listed. + +An MBS Client conforming to any of the listed profiles is permitted to access and process the MBS Distribution Session and shall process the MBS Distribution Session according to the client requirements defined by its chosen conformance profile. + +MBS Distribution Sessions conforming to the *Baseline MBS Distribution Session Profile* defined in clause 12.4 may omit the `conformanceProfiles` property. + +## 12.4 Baseline MBS Distribution Session Profile + +The Baseline MBS Distribution Session Profile characterises MBS Distribution Sessions as specified in the present document. + +For MBS Distribution Sessions conforming to the Baseline MBS Distribution Session Profile, the following applies: + +- If the User Service Description indicates the Object Distribution Method, then the MBS Distribution Session shall conform to the requirements in clause 6. +- If the User Service Description indicates the Packet Distribution Method, then the MBS Distribution Session shall conform to the requirements in clause 7. + +An MBS Client conforming to this profile shall support the MBS Client requirements for the Object Distribution Method as defined in clause 6 and the MBS Client requirements for the Packet Distribution Method as defined in clause 7. + +The Baseline MBS Distribution Session Profile is identified by the URI `urn:3GPP:26517:17:baseline` as specified in annex C.2. + +# Annex A (normative): Syntax for Service Announcement + +## A.1 Void + +## A.2 JSON-based representation + +### A.2.1 MBS User Service Announcement schema + +Below is the schema specifying the format of User Service Descriptions instance documents using a JSON-based representation. The schema filename is "TS26517\_MBSUserServiceAnnouncement.yaml". + +Documents following this schema shall be identified with the MIME media type *application/3gpp-mbs-user-service-descriptions+json* as registered in clause E.2.1 including the following parameters: + +- The *profiles* parameter (see clause E.2.2) shall include a fully-qualified term identifier from the controlled vocabulary specified in clause C.2. +- The *version* parameter (see clause E.2.3) shall contain the value "Rel18" to indicate conformance with this version of the present document. + +``` +openapi: 3.0.0 + +info: + title: 'MBS User Service Announcement' + version: 2.1.0 + description: | + MBS User Service Announcement Element units. + © 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: 3GPP TS 26.517 V18.3.0; 5G Multicast-Broadcast User Services; Protocols and Formats + url: http://www.3gpp.org/ftp/Specs/archive/26_series/26.517/ + +paths: + /user-service-descriptions: + get: + operationId: discoverUserServiceDescriptions + summary: 'Discover User Service Descriptions' + description: 'Discover User Service Descriptions that match the supplied query filter(s). At least one filter query parameter must be included in the request URL.' + parameters: + - in: query + name: service-class + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + required: true + description: 'Filter for User Service Descriptions tagged with the supplied service class term identifier expressed as a fully-qualified URI string from a controlled vocabulary' + responses: + '200': + # OK + description: "Success" + content: + multipart/related: + schema: + type: string + '204': + # No Content (no matching User Service Descriptions) + description: "No Matches Found" + '500': + # Internal Server Error +``` + +``` +$ref: 'TS29571_CommonData.yaml#/components/responses/500' +'503': + # Service Unavailable + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/user-service-descriptions/{externalServiceId}: + get: + operationId: retrieveUserServiceDescription + summary: 'Retrieve User Service Description' + description: 'Retrieve the User Service Description of a single service by supplying its +external service identifier.' + parameters: + - name: externalServiceId + in: path + required: true + schema: + type: string + description: 'The external service identifier of a User Service provisioned in the +MBF.' + responses: + '200': + # OK + description: "Success" + content: + multipart/related: + schema: + type: string + '404': + # Not Found + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '500': + # Internal Server Error + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + # Service Unavailable + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + schemas: + UserServiceDescriptions: + description: 'A document announcing one or more MBS User Services.' + type: object + properties: + version: + type: integer + minimum: 1 + userServiceDescriptions: + type: array + items: + $ref: '#/components/schemas/UserServiceDescription' + minItems: 1 + required: + - userServiceDescriptions + + UserServiceDescription: + description: 'A description of a single MBS User Service.' + type: object + properties: + serviceIds: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + minItems: 1 + class: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + names: + type: array + items: + type: object + properties: + name: + type: string + lang: + type: string +``` + +``` + pattern: '[a-zA-Z]{3}$' + example: 'eng' + required: + - name + - lang + minItems: 1 + descriptions: + type: array + items: + type: object + properties: + description: + type: string + lang: + type: string + pattern: '[a-zA-Z]{3}$' + example: 'eng' + required: + - description + - lang + minItems: 1 + serviceLanguage: + type: string + pattern: '[a-zA-Z]{3}$' + example: 'eng' + distributionSessionDescriptions: + type: array + items: + $ref: '#/components/schemas/DistributionSessionDescription' + minItems: 1 + serviceScheduleDescriptions: + type: array + items: + $ref: '#/components/schemas/ServiceScheduleDescription' + minItems: 1 + required: + - serviceIds + - class + - distributionSessionDescriptions + +DistributionSessionDescription: + type: object + properties: + distributionMethod: + $ref: '#/components/schemas/DistributionMethod' + conformanceProfiles: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + minItems: 1 + sessionDescriptionLocator: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + applicationServiceDescriptions: + type: array + items: + $ref: '#/components/schemas/ApplicationServiceDescription' + minItems: 1 + postSessionObjectRepairParameters: + $ref: '#/components/schemas/ObjectRepairParameters' + availabilityInfos: + type: array + items: + $ref: '#/components/schemas/AvailabilityInformation' + minItems: 1 + securityDescription: + $ref: '#/components/schemas/SecurityDescription' + required: + - distributionMethod + - sessionDescriptionLocator + +DistributionMethod: + anyOf: + - type: string + enum: + - OBJECT + - PACKET + - type: string + description: > +``` + +This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. + +``` +ApplicationServiceDescription: + type: object + properties: + entryPointLocator: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + contentType: + type: string + pattern: '^[a-zA-Z]+/[a-zA-Z]+$' + example: 'application/dash+xml' + required: + - entryPointLocator + - contentType + +AvailabilityInformation: + type: object + properties: + mbsServiceAreas: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MbsServiceArea' + minItems: 1 + mbsFSAId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MbsFsaId' + nrParameters: + type: array + items: + $ref: '#/components/schemas/NrParameterSet' + minItems: 1 + nrRedCapUEInfo: + $ref: 'TS29571_CommonData.yaml#/components/schemas/NrRedCapUeInfo' + +NrParameterSet: + type: object + properties: + freqBandIndicator: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + aRFCNValue: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + required: + - freqBandIndicator + - aRFCNValue + +ObjectRepairParameters: + type: object + properties: + backOffParameters: + $ref: '#/components/schemas/BackOffParameters' + objectDistributionBaseLocator: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + objectRepairBaseLocator: + $ref: 'TS26510_CommonData.yaml#/components/schemas/AbsoluteUrl' + +BackOffParameters: + type: object + properties: + offsetTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + randomTimePeriod: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + anyOf: + - required: [offsetTime] + - required: [randomTimePeriod] + +ServiceScheduleDescription: + type: object + properties: + id: + type: string + version: + type: integer + minimum: 1 + start: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + stop: +``` + +``` +$ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' +repetitionRule: + $ref: '#/components/schemas/RepetitionRule' +required: +- id +- version +oneOf: +- required: [start, stop] +- required: [repetitionRule] + +RepetitionRule: +type: object +properties: + startTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + duration: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + repetitionInterval: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' +required: +- startTime +- duration +- repetitionInterval + +SecurityDescription: +type: object +properties: + mBSSFAAddresses: + type: array + items: + $ref: 'TS26510_CommonData.yaml#/components/schemas/AbsoluteUrl' + minItems: 1 + mBSSServiceKeyInfo: + type: object + properties: + mBSId: + type: string + mBSDomainId: + type: string + required: + - mBSId + - mBSDomainId + uICCKeyManagement: + type: boolean + 2GGBAllowed: + type: boolean + backOffParameters: + $ref: '#/components/schemas/BackOffParameters' +required: +- mBSSFAAddresses +- mBSSessionKeyInfo +``` + +# --- Annex B (informative): Service Announcement examples + +## B.1 XML-based representation + +## B.2 JSON-based representation + +This example is for future study. + +# Annex C (normative): 3GPP Registered URIs + +## C.1 General + +This annex documents the registered URIs in the present document following the process in . + +As required by this process, the tables in the following clauses list all registered URI values as well as: + +- a brief description of its functionality; +- a reference to the specification or other publicly available document (if any) containing the definition; +- the name and email address of the person making the application; and +- any supplementary information considered necessary to support the application. + +## C.2 Controlled vocabulary of conformance profile identifiers + +**Table C.2-1: Controlled vocabulary of conformance profile identifiers** + +| URI | Description | Reference | Contact | Remarks | +|-----------------------------------|-------------------------------------------|------------------------|----------------------------------------------------------------------------------------|---------| +| urn:3GPP:26517:17:baseline | Baseline MBS Distribution Session Profile | TS 26.517, clause 12.4 | Thomas Stockhammer
tsto@gti.qualcomm.com | None. | + +# Annex D (normative): Syntax for object manifest + +## D.1 Object manifest schema + +Below is the formal syntax of the JSON-based object manifest for use with the Object Collection or Object Carousel operating mode. The schema shall have the filename "TS26517\_MBSObjectManifest.yaml". + +Documents following this schema shall be identified with the MIME media type *application/3gpp-mbs-object-manifest+json* as registered in clause E.3.1 including the following parameters: + +- The *version* parameter (see clause E.3.2) shall contain the value "Rel17" to indicate conformance with this version of the present document. + +``` + +openapi: 3.0.0 +info: + title: MBS User Services Object Manifest + version: 2.0.0 + description: | + MBS User Services Object Manifest syntax + © 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +tags: + - name: MBS User Services Object Manifest + description: '5G Media Streaming: Common Data Types' +externalDocs: + description: 'TS 26.517 V18.1.0; 5G Multicast-Broadcast User Services; Protocols and Formats' + url: 'https://www.3gpp.org/ftp/Specs/archive/26_series/26.517/' +paths: {} +components: + schemas: + ObjectManifest: + type: object + description: A manifest describing a set of binary objects to be transmitted by the MBSTF as part of the MBS Distribution Session. + required: + - objects + properties: + updateInterval: + type: integer + format: int32 + description: The time period (in seconds) after which the MBSTF attempts to re-acquire the object manifest when pull-based object acquisition is provisioned. + objects: + type: array + description: The list of binary objects to be carouselled from the MBSTF to the MBSTF Client. + items: + $ref: '#/components/schemas/Object' + Object: + type: object + description: A binary object to be transmitted by the MBSTF as part of the MBS Distribution Session. + required: + - locator + properties: + locator: + $ref: 'TS26510_CommonData.yaml#/components/schemas/AbsoluteUrl' + repetitionInterval: + type: integer + format: int32 + description: The MBSTF sends the object repeatedly to the MBSTF Client with the given interval (in milliseconds). This parameter is ignored in the case of Object Collection operating mode. + keepUpdatedInterval: + type: integer + format: int32 + description: The MBSTF checks for changes to the object with the given interval (in seconds). This parameter is ignored in the case of Object Collection operating mode. + earliestFetchTime: + type: string + +``` + +``` + format: date-time + description: The MBSTF shall pull each object from its origin location no sooner than +this time or, if this parameter is omitted, at a time of its choosing. + latestFetchTime: + type: string + format: date-time + description: The MBSTF shall pull each object from its origin location no later than +this time, or, if this parameter is omitted, at a time of its choosing. +``` + +# Annex E (normative): IANA registration + +## E.1 General + +This annex provides the formal registrations of MIME media types for different resources specified in the present document. It is referenced from the IANA registry at . + +## E.2 Registration of MIME media type for MBS User Service Descriptions document + +### E.2.1 General + +The MIME media type specified in table E.2.1-1 below denotes that the message body is a JSON instance document compliant with the *UserServiceDescriptions* YAML schema specified in clause A.2.1. + +**Table E.2.1-1: MIME media type registration for MBS User Service Descriptions document** + +| Parameter | Value | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MIME media type name | application | +| MIME subtype name | 3gpp-mbs-user-service-descriptions+json | +| Required parameters | version (see clause E.2.3 of 3GPP TS 26.517). | +| Optional parameters | profiles (see clause E.2.2 of TS 26.517). | +| Encoding considerations | This is a JSON document, and the encoding considerations are the same as for media type application/json defined in IETF RFC 8259. | +| Security considerations | This media format is used to configure the receiver on how to participate in one or more MBS User Services. This format is highly susceptible to manipulation or spoofing for attacks desiring to mislead a receiver about a session. Both integrity protection and source authentication are recommended to prevent misleading of the receiver. | +| Interoperability considerations | The specification defines a platform-independent expression of an entry point document, and it is intended that wide interoperability can be achieved. | +| Published specification | 3GPP TS 26.517 | +| Applications which use this media type | 3GPP MBS-based applications and services | +| Fragment identifier considerations | The provisions of RFC 6901 (JSON Pointer) apply. | +| Restrictions on usage | None | +| Provisional registration? | No | +| Additional information | | +| Deprecated alias names | None | +| Magic number(s) | None | +| File extension(s) | json | +| Macintosh File Type Code(s) | None | +| Object Identifier(s) of OID(s) | None | +| Intended usage | COMMON | +| Other information and general comments | None | +| Contact person | | +| Contact name | Dongwook Kim | +| Contact e-mail address | dongwook.kim@etsi.org | +| Author/Change controller | 3GPP TSG SA WG4 | + +### E.2.2 Profiles parameter + +Table E.2.2-1 specifies the *profiles* parameter to be used with the MIME media type registered in clause E.2.1. + +**Table E.2.2-1: Definition of profiles parameter** + +| Parameter | Value | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | profiles | +| Parameter value | Optional attribute indicating one or more profiles to which the resource representation claims conformance. The contents of this attribute shall conform to either the pro-simple or pro-fancy productions specified in section 4.5 of IETF RFC 6381.
The value is a fully-qualified term identifier URI from a controlled vocabulary.
The set of profile identifiers indicated in this parameter should match the set indicated in the profiles attribute of the corresponding User Service Description. | + +EXAMPLE: `application/3gpp-mbs-user-service-description+json; +profiles="urn:3GPP:26517:17:baseline;version=Rel17"` + +### E.2.3 Version parameter + +Table E.2.3-1 specifies the *version* parameter to be used with the MIME media type registered in clause E.2.1. + +**Table E.2.3-1: Specification of version parameter** + +| Parameter | Value | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | version | +| Parameter value | A comma-separated list of versions of the Object Manifest schema to which the document conforms. The value specified in clause D.1 of 3GPP TS 26.517 encodes the last 3GPP release in which a change to the document schema was approved.
The purpose of the parameter is to allow schema conformance to be assessed by a recipient before attempting to parse the contents of a received document. | + +EXAMPLE: `application/3gpp-mbs-user-service-description+json; +profiles="urn:3GPP:26517:17:baseline";version="Rel17"` + +## E.3 Registration of MIME media type for MBS User Services object manifest document + +### E.3.1 General + +The MIME media type specified in table E.3.1-1 below denotes that the message body is a JSON instance document compliant with the *ObjectManifest* YAML schema specified in clause D.1. + +**Table E.3.1-1: MIME media type registration for MBS User Services object manifest document** + +| Parameter | Value | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MIME media type name | application | +| MIME subtype name | 3gpp-mbs-object-manifest+json | +| Required parameters | version (see clause E.3.2 of 3GPP TS 26.517). | +| Optional parameters | None. | +| Encoding considerations | This is a JSON document, and the encoding considerations are the same as for media type application/json defined in IETF RFC 8259. | +| Security considerations | This media format is used to describe a set of objects to the MBS Transport Function to be transmitted in an MBS Distribution Session as part of an MBS User Service. This format is highly susceptible to manipulation or spoofing for attacks designed to affect the set of objects ingested by the MBSTF and transmitted to receivers. Both integrity protection and source authentication are recommended to prevent misleading of the receiver. | +| Interoperability considerations | The specification defines a platform-independent manifest document format, and it is intended that wide interoperability can be achieved. | +| Published specification | 3GPP TS 26.517 clause D.1 | +| Applications which use this media type | 3GPP MBS-based applications and services | +| Fragment identifier considerations | The provisions of RFC 6901 (JSON Pointer) apply. | +| Restrictions on usage | None | +| Provisional registration? | No | +| Additional information | | +| Deprecated alias names | None | +| Magic number(s) | None | +| File extension(s) | json | +| Macintosh File Type Code(s) | None | +| Object Identifier(s) of OID(s) | None | +| Intended usage | COMMON | +| Other information and general comments | None | +| Contact person | | +| Contact name | Dongwook Kim | +| Contact e-mail address | dongwook.kim@etsi.org | +| Author/Change controller | 3GPP TSG SA WG4 | + +### E.3.2 Version parameter + +Table E.3.2-1 specifies the *version* parameter to be used with the MIME media type registered in clause E.3.1. + +**Table E.3.2-1: Specification of version parameter** + +| Parameter | Value | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Parameter name | version | +| Parameter value | A comma-separated list of versions of the Object Manifest schema to which the document conforms. The value specified in clause D.1 of 3GPP TS 26.517 encodes the last 3GPP release in which a change to the document schema was approved.
The purpose of the parameter is to allow schema conformance to be assessed by a recipient before attempting to parse the contents of a received document. | + +EXAMPLE: `application/3gpp-mbs-object-manifest+json;version="Rel17"` \ No newline at end of file diff --git a/marked/Rel-18/26_series/26804/028422d3e6ce272069a2b4f317c88474_img.jpg b/marked/Rel-18/26_series/26804/028422d3e6ce272069a2b4f317c88474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ea8c942391567c1d72f680ee89dc1d2ff58317f --- /dev/null +++ b/marked/Rel-18/26_series/26804/028422d3e6ce272069a2b4f317c88474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da0a4cdc0ca3a797f4e1f92ab3e4075647c9a3f61e529a3d53d5683855a6e1ff +size 99905 diff --git a/marked/Rel-18/26_series/26804/04f7b8f64493f6d83188232f10f86fe2_img.jpg b/marked/Rel-18/26_series/26804/04f7b8f64493f6d83188232f10f86fe2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da12f67497483e1ef5348dbb208e318368a92280 --- /dev/null +++ b/marked/Rel-18/26_series/26804/04f7b8f64493f6d83188232f10f86fe2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:925c34f734a94cfa77ef81ab40cba08fc481739aec58372bfe6d4cf99bd7b55b +size 186516 diff --git a/marked/Rel-18/26_series/26804/353d05a4935a6b770e9b80ed94762b6a_img.jpg b/marked/Rel-18/26_series/26804/353d05a4935a6b770e9b80ed94762b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaeb9fdee34483652169103dc734670e35d1af2c --- /dev/null +++ b/marked/Rel-18/26_series/26804/353d05a4935a6b770e9b80ed94762b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ceea136af46939f6507e257b78c9f01e83c941486830e6f8564128f0583205d8 +size 128436 diff --git a/marked/Rel-18/26_series/26804/35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg b/marked/Rel-18/26_series/26804/35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79871c5bb7a0302f6ef537cfd779f244683234e0 --- /dev/null +++ b/marked/Rel-18/26_series/26804/35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23676478133685437d70db6bb054fafa494a630be88672d93f10dc16085d64f9 +size 44757 diff --git a/marked/Rel-18/26_series/26804/427095219f3706148e8c03f1013eaec8_img.jpg b/marked/Rel-18/26_series/26804/427095219f3706148e8c03f1013eaec8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08b676b7cf2ddadb29fe486f8f438fa4b7646613 --- /dev/null +++ b/marked/Rel-18/26_series/26804/427095219f3706148e8c03f1013eaec8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea8cc70357020b841f8c6ca4b7a02f9e8cfbe75c10c2b209416eb1da1295b83c +size 159853 diff --git a/marked/Rel-18/26_series/26804/453a1dc18dd2dd3334d19f453b04d11b_img.jpg b/marked/Rel-18/26_series/26804/453a1dc18dd2dd3334d19f453b04d11b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b594914060844e8ee2e4b563084b3f730b8eaff --- /dev/null +++ b/marked/Rel-18/26_series/26804/453a1dc18dd2dd3334d19f453b04d11b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2921262aa7679d70b97d5cadf67a3bc958abaa80c335697cccaa08f8a43b083a +size 111925 diff --git a/marked/Rel-18/26_series/26804/58df9e48362936fbfe061cf470485b4d_img.jpg b/marked/Rel-18/26_series/26804/58df9e48362936fbfe061cf470485b4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25633223e8bd2b2df76c1653eed38b4d4b3d81e4 --- /dev/null +++ b/marked/Rel-18/26_series/26804/58df9e48362936fbfe061cf470485b4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5f49cea75619c33e9ccfa5cbaa74866f5e2e5babba707f58503b724857d3561 +size 6161 diff --git a/marked/Rel-18/26_series/26804/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26804/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462c222da54d9dbbec7cdc4e21c34c9df3967047 --- /dev/null +++ b/marked/Rel-18/26_series/26804/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6a44cef4530e30d221f63982b4437b8835871f9cdccae6f0e1a94e76217752c +size 5657 diff --git a/marked/Rel-18/26_series/26804/691626a7032a642bb74793336c37e274_img.jpg b/marked/Rel-18/26_series/26804/691626a7032a642bb74793336c37e274_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5453ba3697c5170d973ef0622ff2d3fc98959a1 --- /dev/null +++ b/marked/Rel-18/26_series/26804/691626a7032a642bb74793336c37e274_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bd83ae3a36089f787dff31db5236d98b21cfcd51e53ae39b5f6dc7eb0144c67 +size 74326 diff --git a/marked/Rel-18/26_series/26804/82340ab4d7b2db48ce408d8db6fde6b6_img.jpg b/marked/Rel-18/26_series/26804/82340ab4d7b2db48ce408d8db6fde6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7c6880110c6de0a85ad4270a572a50e0a415945 --- /dev/null +++ b/marked/Rel-18/26_series/26804/82340ab4d7b2db48ce408d8db6fde6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:965132e488a19c74409c6cc9415ac372fd78be4f216a42efdec3b5e37ec666c3 +size 52167 diff --git a/marked/Rel-18/26_series/26804/91aa519060714a3ebba978bb68cbf648_img.jpg b/marked/Rel-18/26_series/26804/91aa519060714a3ebba978bb68cbf648_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b036944ea7854103e072274a4329a3875545672a --- /dev/null +++ b/marked/Rel-18/26_series/26804/91aa519060714a3ebba978bb68cbf648_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61119ddcdff9d20a33da8bb55a0f67bf036e090d30e80b0bde146a340722d26a +size 132097 diff --git a/marked/Rel-18/26_series/26804/91e1f604527f292075a070e03c7b55f1_img.jpg b/marked/Rel-18/26_series/26804/91e1f604527f292075a070e03c7b55f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07e4c0322738629e0bc162a5c21928f6f2159f9a --- /dev/null +++ b/marked/Rel-18/26_series/26804/91e1f604527f292075a070e03c7b55f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e2de92ca40b7322068303d3417fb721c19e6774846876fbafcefb12409bc14a +size 46658 diff --git a/marked/Rel-18/26_series/26804/993d36ea4a6a2610f938b1fb97e7c34a_img.jpg b/marked/Rel-18/26_series/26804/993d36ea4a6a2610f938b1fb97e7c34a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13751c87b0c57ea5faebaa27dc2b7b4e23fd80a3 --- /dev/null +++ b/marked/Rel-18/26_series/26804/993d36ea4a6a2610f938b1fb97e7c34a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f14fbaf46933a1e4d730fa96967015311d7375aceafac67d47081e42a45c5c0b +size 58009 diff --git a/marked/Rel-18/26_series/26804/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-18/26_series/26804/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db6a0828356ac47883979bd59c9a2d7efc8b53f --- /dev/null +++ b/marked/Rel-18/26_series/26804/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc57340462cab2690a22ed565e1cb8a367ccbbca845ad35adb0ac9eb32eedf31 +size 42679 diff --git a/marked/Rel-18/26_series/26804/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/Rel-18/26_series/26804/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea896b5e415d1aa94339e3d343543f7487ca85a0 --- /dev/null +++ b/marked/Rel-18/26_series/26804/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58312e0f0ab304f81f3d3a3e50839c4cd2d3549406adbdce1a75d5bb54fd0151 +size 138840 diff --git a/marked/Rel-18/26_series/26804/b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg b/marked/Rel-18/26_series/26804/b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68cb4a241c745115f456dcd387ec22b55b2e7561 --- /dev/null +++ b/marked/Rel-18/26_series/26804/b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d68e43036db7d01b8bcd1fe7c597c135e6a849a5548959db1811851b7f6107c +size 78465 diff --git a/marked/Rel-18/26_series/26804/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg b/marked/Rel-18/26_series/26804/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53129cbf788c036d1aec4ad5e0f9032064e6ad63 --- /dev/null +++ b/marked/Rel-18/26_series/26804/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da04add804c879a7b3199e77c02a5826902c53bb31d4f498452ceee3cc4b0e79 +size 41172 diff --git a/marked/Rel-18/26_series/26804/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-18/26_series/26804/d9cfc30025244dcd75766061f27ee09f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0c9f7218c7cf0c98dba1932718fc31c4486edee --- /dev/null +++ b/marked/Rel-18/26_series/26804/d9cfc30025244dcd75766061f27ee09f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d82632ab491246668a0df4d80a51b4873214d8cd2fe6ebb65c9ebe28921f4de9 +size 178094 diff --git a/marked/Rel-18/26_series/26804/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-18/26_series/26804/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4cf77c472ce2a8fb609c8e7d4f370f3396f37c2 --- /dev/null +++ b/marked/Rel-18/26_series/26804/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b0e63a630db4ac2082229a9ca2262e437650a1ba642415f86ab3d2ca1cdb7f5 +size 106506 diff --git a/marked/Rel-18/26_series/26925/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-18/26_series/26925/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05406a2ec4e5e1ba45cefc01f42762053e1674c --- /dev/null +++ b/marked/Rel-18/26_series/26925/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98863ad72a98042ebf600dda1d0223aaf741e32f4740a07e5d6b992456bed7ed +size 86815 diff --git a/marked/Rel-18/26_series/26925/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26925/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ba69d7d091a1dc7f31ec27e343f5f3fd6580638 --- /dev/null +++ b/marked/Rel-18/26_series/26925/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba15807a7b5f9ca8c8d623f45214141c493366be09b339c7f6762140b3662b6 +size 7739 diff --git a/marked/Rel-18/26_series/26925/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26925/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d54b5b6ae870a9adb78ff51f06049fc780866939 --- /dev/null +++ b/marked/Rel-18/26_series/26925/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0da881c84289a2b452b4b8c27e22bce7eea4294f0ad3a5c1bbd1e0efa5b1383 +size 5783 diff --git a/marked/Rel-18/26_series/26925/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/26_series/26925/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3452965352810657c3c9c9b4e2f262a2666928df --- /dev/null +++ b/marked/Rel-18/26_series/26925/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b82510cf667e6e0f6ea1725a4f34ecc567dca85d95bce0e564dfca3d726bf8f8 +size 100133 diff --git a/marked/Rel-18/26_series/26925/fed39b841ae2dce01088b84bfc1e2789_img.jpg b/marked/Rel-18/26_series/26925/fed39b841ae2dce01088b84bfc1e2789_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bf22537161a7f45f1b61a6852610d36aa79e33e --- /dev/null +++ b/marked/Rel-18/26_series/26925/fed39b841ae2dce01088b84bfc1e2789_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3d882f4535d56c3e667feab5ccc26c2c2366842372fa2f9b8b2b0b5d6ba1082 +size 53267 diff --git a/marked/Rel-18/26_series/26925/raw.md b/marked/Rel-18/26_series/26925/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e395bedd106fc0bde112d50ad9e40c11b871a82a --- /dev/null +++ b/marked/Rel-18/26_series/26925/raw.md @@ -0,0 +1,1003 @@ + + +# 3GPP TR 26.925 V18.1.0 (2023-12) + +Technical Report + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Typical traffic characteristics of media services on 3GPP networks (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring a stylized '5G' with a green signal wave icon above the 'G'. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters '3GPP' in a stylized font with a red signal wave icon below the 'P'. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 10 | +| 4 Media centric Third-Party and Operator services ..... | 10 | +| 4.1 A/V Streaming - Enhanced TV ..... | 10 | +| 4.2 VR 360° Streaming ..... | 10 | +| 4.3 Conversational Multimedia Telephony and Telepresence ..... | 10 | +| 4.4 Live uplink A/V streaming..... | 10 | +| 4.5 Cloud gaming ..... | 10 | +| 4.6 XR Media Services..... | 10 | +| 5 Typical current deployment characteristics ..... | 11 | +| 5.1 Typical streaming/broadcast video and audio bitrates ..... | 11 | +| 5.2 Typical streaming/broadcast 360 VR bitrates ..... | 11 | +| 5.3 Typical conversational speech/audio and video bitrates ..... | 12 | +| 5.4 Typical uplink A/V streaming of A/V, including 360 VR content ..... | 12 | +| 5.4.1 Professional production content bitrates ..... | 12 | +| 5.4.2 Live uplink contribution professional content bitrates ..... | 13 | +| 5.4.3 User generated content ..... | 14 | +| 5.5 Typical Traffic Characteristics for Cloud gaming ..... | 14 | +| 5.6 XR Traffic Characteristics ..... | 15 | +| 6 Overview on technological developments for existing and emerging services ..... | 16 | +| 6.1 Technology Developments..... | 16 | +| 6.1.1 Overview ..... | 16 | +| 6.1.2 Compression Improvements ..... | 16 | +| 6.1.3 New Media Formats ..... | 18 | +| 6.1.4 Protocol Improvements ..... | 19 | +| 6.1.5 Impact on Media Services ..... | 20 | +| 7 Characteristics and requirements for different media services on 3GPP networks ..... | 20 | +| 7.1 Introduction ..... | 20 | +| 7.2 Collection process for requirements for different media services on 3GPP networks..... | 21 | +| 7.3 Summary of Responses for Streaming Services ..... | 23 | +| 7.3.1 Introduction ..... | 23 | +| 7.3.2 Used Technologies ..... | 23 | +| 7.3.2.1 Codecs..... | 23 | +| 7.3.2.2 Media types and formats ..... | 23 | +| 7.3.2.3 Media protocols and containers ..... | 24 | +| 7.3.2.4 Transport protocols ..... | 24 | +| 7.3.2.5 Clients ..... | 24 | +| 7.3.2.6 Other Technologies..... | 24 | +| 7.3.3 Traffic Characteristics ..... | 24 | +| 7.3.3.1 Bitrate Characteristics..... | 24 | +| 7.3.3.2 Other KPIs ..... | 24 | +| 7.3.3.3 Potential mapping to 5QIs ..... | 24 | +| 8 Applicability of existing 5QIs ..... | 25 | +| 8.1 QoS Model ..... | 25 | +| 8.1.1 Overview ..... | 25 | + +| | | | +|-------------------------------------------------------------|-------------------------------------------------------|-----------| +| 8.1.2 | 5G QoS Parameters ..... | 26 | +| 8.1.3 | 5G QoS Characteristics ..... | 26 | +| 8.1.4 | Standardized 5QI to QoS characteristics mapping ..... | 27 | +| 8.1.5 | Considerations for Media Services..... | 29 | +| 8.1.5.1 | General ..... | 29 | +| 8.1.5.2 | Expected TCP/IP Performance for non-GBR ..... | 29 | +| 8.1.5.3 | Bitrate considerations for GBR services..... | 30 | +| 8.1.5.4 | Relevant Parameters for Media Services ..... | 30 | +| Annex A: Background information on cloud gaming..... | | 31 | +| Annex B: Change history..... | | 32 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +The document presents typical media traffic characteristics (including bandwidth and latency requirements) that are of importance for 3GPP standardization work. This includes demands based on current services, but also expectations for new services or emerging services, considering developments in the industry in terms of efficiency improvements. + +# --- 1 Scope + +The present document includes following information: + +- Media centric Third-Party and Operator services currently deployed or expected to be deployed until 2025 on 3GPP defined 4G and 5G networks. +- Typical deployment characteristics today, such as bandwidth requirements, client buffered and rate adaptation reception characteristics, codecs, protocols in use and latency requirements. +- An overview on technological developments for existing and emerging services and their impact on typical traffic characteristics of media services, e.g. evolution of compression technologies, new demands for high quality, new experiences, etc. +- A summary on typical characteristics and requirements for different media services on 3GPP networks. +- An identification of the applicability of existing 5QIs for such services and potentially identify requirements for new 5QIs or QoS related parameters. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 26.234: "Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs". +- [3] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [4] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs ". +- [5] 3GPP TS 26.116: "Television (TV) over 3GPP services; Video profiles". +- [6] 3GPP TS 26.118: "3GPP Virtual reality profiles for streaming applications". +- [7] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction". +- [8] 3GPP TS 26.223: "Telepresence using the IP Multimedia Subsystem (IMS); Media handling and interaction ". +- [9] Recommendation ITU-R BT.1872-3 (10-2019): " User requirements for broadcast auxiliary services including digital television outside broadcast, electronic/satellite news gathering and electronic field production". +- [10] 3GPP TS 23.501: "System Architecture for the 5G System ". +- [11] 3GPP TS 26.238: "Uplink streaming". + +- [12] ST 2110-10:2017 - SMPTE Standard - Professional Media Over Managed IP Networks: System Timing and Definitions. +- [13] Video Services Forum (VSF) Technical Recommendation TR-05, Essential Formats and Descriptions for Interoperability of SMPTE ST 2110-20 Video Signals. +- [14] Recommendation ITU-T H.264 (04/2017): "Advanced video coding for generic audiovisual services" | ISO/IEC 14496-10:2014: "Information technology - Coding of audio-visual objects - Part 10: Advanced Video Coding". +- [15] Recommendation ITU-T H.265 (12/2016): "High efficiency video coding" | ISO/IEC 23008-2:2015: "High Efficiency Coding and Media Delivery in Heterogeneous Environments - Part 2: High Efficiency Video Coding". +- [16] 3GPP TR 26.949: "Video formats for 3GPP services". +- [17] IETF RFC 793: "TCP" +- [18] . +- [19] DVB BlueBook A176: "Adaptive media streaming over IP multicast - reference architecture". +- [20] CableLabs OC-TR-IP-MULTI-ARCH: "IP Multicast Adaptive Bit Rate Architecture Technical Report". +- [21] "How youtube led to Google's cloud-gaming service", [spectrum.ieee.org](https://spectrum.ieee.org) | SEP 2019 | 09. +- [22] 3GPP TR 22.842: "Study on Network Controlled Interactive Services (Release 17)". +- [23] "Cloud Gaming: Architecture and Performance", Ryan Shea and Jiangchuan Liu, Simon Fraser University; Edith C.-H. Ngai, Uppsala University; Yong Cui, Tsinghua University; IEEE Network-July/August 2013. +- [24] Jens-Rainer Ohm, Gary J. Sullivan, Heiko Schwarz, Thiow Keng Tan, and Thomas Wiegand, "Comparison of the Coding Efficiency of Video Coding Standards—including High Efficiency Video Coding (HEVC)" IEEE TRANSACTIONS ON CIRCUITS AND SYSTEMS FOR VIDEO TECHNOLOGY, VOL. 22, NO. 12, DECEMBER 2012. +- [25] T.K. Tan, M. Mrak, R. Weerakkody, N. Ramzan, V. Baroncini, G.J. Sullivan, J.-R. Ohm, K.D. McCann, "HEVC subjective video quality test results", IBC2014 Conference, 2014. +- [26] Thiow Keng Tan ; Rajitha Weerakkody ; Marta Mrak ; Naeem Ramzan ; Vittorio Baroncini, Jens-Rainer Ohm, Gary J. Sullivan, "Video Quality Evaluation Methodology and Verification Testing of HEVC Compression Performance" IEEE Transactions on Circuits and Systems for Video Technology, Volume: 26, Issue: 1, Jan. 2016. +- [27] Minhua Zhou, Jianle Chen, Kiho Choi and Dmytro Rusanovskyy, "Tool comparison between VVC (VTM3.0) and NVC", ISO/IEC JTC1/SC29/WG11 MPEG2019/ m46554, Marrakech, Morocco, January 2019. +- [28] Frank Bossen, Xiang Li, Karsten Suehring, "AHG report: Test model software development (AHG3)", JVET-M0003, Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting: Marrakech, MA, 9-18 Jan. 2019. +- [29] K. Choi et al., "Description of video coding technology proposal by Samsung, Huawei, and Qualcomm for New Video Coding Standard", MPEG-M46354, Marrakech, Morocco, January 2019. +- [30] 3GPP TR 26.928: "Extended Reality over 5G". +- [31] ST 297:2006 - SMPTE Standard - For Television — Serial Digital Fiber Transmission System for SMPTE 259M, SMPTE 344M, SMPTE 292 and SMPTE 424M Signals. +- [32] ST 2081-10:2018 - SMPTE Standard - 2160-line and 1080-line Source Image and Ancillary Data Mapping for 6G-SDI. + +- [33] ST 2082-1:2015 - SMPTE Standard - 12 Gb/s Signal/Data Serial Interface — Electrical ST 2082-1:2015. +- [34] SMPTE ST-2083, 24G-SDI, In development. +- [35] 3GPP TR 22.827: "Study on Audio-Visual Service Production". +- [36] ST 2042-1:2017 - SMPTE Standard - VC-2 Video Compression +- [37] ITU-T/T.802 | ISO/IEC 15444-3 "Information technology - JPEG 2000 image coding system - Part 3: Motion JPEG 2000 +- [38] ITU-T G.1032 "Influence factors on gaming quality of experience" () +- [39] ITU-T P.809 "Subjective evaluation methods for gaming quality" () +- [40] M. Mathis, J. Semke, J. Mahdavi, The macroscopic behavior of the TCP congestion avoidance algorithm. Comput. Commun. Rev. (ACM SIGCOMM) **27**(3), 67–82 (1997) +- [41] Yusuke Miki, Tsuyoshi Sakiyama, Kenichiro Ichikawa, Mayumi Abe, Seiji Mitsuhashi, Masayuki Miyazaki , "Ready for 8K UHDTV broadcasting in Japan", IBC 2015 Conference. +- [42] Hirokazu Kamoda, "NHK Launched World's First 8K Broadcasting in Japan", NAB Pilot guest blog post () +- [43] Thierry Fautier, Eric Mazieres, France Television Lab blog post "8K EXPERIMENT AT ROLAND GARROS 2019" () +- [44] M. Aracena, T. Fautier, O. Oyman, "Live VR end-to-end workflows: real-life deployments and advances in VR and network technology", SMPTE 2020 Annual Technical Conference & Exhibition, November 2020, . +- [45] 3GPP TS 26.511, "5G Media Streaming (5GMS); Profiles, codecs and formats". +- [46] 3GPP TR 26.955, " Video codec characteristics for 5G-based services and applications". +- [47] 3GPP TR 26.926, "Traffic Models and Quality Evaluation Methods for Media and XR Services in 5G Systems". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**360 VR:** Virtual Reality 360° video and 3D audio content. + +**720p:** a video with an image resolution of 1 280 × 720 pixels. + +**4K UHD:** a video with an image resolution of 3 840 x 2 160 pixels a.k.a. 2160p. + +**8K UHD:** a video with an image resolution of 7680 x 4 320 pixels a.k.a. 4320p. + +## 3.2 Symbols + +Void. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-----|---------------------------| +| A/V | Audio/Visual | +| FEC | Forward Error Correction | +| FFS | For Further Study | +| HD | High Definition | +| PSS | Packet Switched Streaming | +| STB | Set-Top-Box | +| TV | Television | +| UHD | Ultra High Definition | +| VR | Virtual Reality | + +# --- 4 Media centric Third-Party and Operator services + +## 4.1 A/V Streaming - Enhanced TV + +Live and on-demand audio-visual streaming and enhanced TV services are considered according to 3GPP PSS [2], 3GP-DASH [3], MBMS [4], 5G Media Streaming for downlink [45] and the media profiles in TS 26.116 [5]. + +## 4.2 VR 360° Streaming + +Live and on-demand VR 360° streaming are considered according to 3GPP PSS [2], 3GP-DASH [3], MBMS [4], 5G Media Streaming [45] and the media profiles in TS 26.118 [6]. + +## 4.3 Conversational Multimedia Telephony and Telepresence + +Conversational Multimedia Telephony and Telepresence are considered according to MTSI [7] and IMS Telepresence [8]. + +## 4.4 Live uplink A/V streaming + +Professional and consumer live uplink streaming contribution of A/V content are considered according to FLUS [11] and 5G Media Streaming for uplink [45]. + +## 4.5 Cloud gaming + +Cloud gaming (a.k.a. game streaming) implies that, while the game is being played by a user on a UE or on a device attached to a UE, game processing and rendering is totally or partly performed in a network entity, potentially at the edge of the network. The traffic typically consists of uplink and downlink game status/control information traffic between a client and a server and of downlink streaming of rendered and encoded 2D or VR360 video. + +## 4.6 XR Media Services + +For details on XR Services including AR and VR, refer to 3GPP TR 26.928 [30] and 3GPP TR 26.926 [47]. Identified scenarios are: + +- Viewport-independent 6DOF streaming, see TR 26.928 [30], clause 6.2.2. +- Viewport-dependent 6DOF streaming, see TR 26.928 [30], clause 6.2.3. + +- Raster-based split rendering, see TR 26.928 [30], clause 6.2.5. +- Generalized split rendering, see TR 26.928 [30], clause 6.2.6. +- XR conversational, see TR 26.928 [30], clause 6.2.7. + +# --- 5 Typical current deployment characteristics + +## 5.1 Typical streaming/broadcast video and audio bitrates + +These figures are valid for both HDR/non-HDR video: + +- 720p HD: 2 - 5 Mbps + +NOTE 1: Today typically 3 Mbps for HEVC [15] and 5Mbps for AVC [14], but bitrate reductions expected with better encoding and coding tools. See Clause 6.1.2. + +- Full HD: 3 - 12 Mbps + +NOTE 2: Today typically 5-7 Mbps for HEVC [15] and 10-12 Mbps for AVC [14], but bitrate reductions expected with better encoding and coding tools. See Clause 6.1.2 as well as TR 26.955 [46]. + +- 4k UHD: 5- 25Mbps + +NOTE 3: Today typically 8-16 Mbps for HEVC [15] and 15-25 Mbps for AVC [14], but bitrate reductions expected with better encoding and coding tools. See Clause 6.1.2 as well as TR 26.955 [46]. + +- 8k UHD: 25 - 80 Mbps + +NOTE 4: Initially up to 80 Mbps for HEVC [15], but bitrate reductions expected with better encoding and coding tools. More advances with new codecs are expected, See Clause 6.1.2. + +These figures apply for audio: + +- Normal quality audio: mono/stereo: 24-48 kbps +- High quality audio: mono/stereo/immersive 24-512 kbps +- Extreme quality audio: mono/stereo/immersive 512 kbps + +## 5.2 Typical streaming/broadcast 360 VR bitrates + +The following bitrates apply for streaming/broadcast 360 VR. + +- Basic 360 VR: 2.5 - 25 Mbps + +NOTE 1: For viewport agnostic, the 4k UHD numbers as defined in clause 5.1 apply. For viewport dependent, the bitrates likely can be reduced to half.- According to [44], with HEVC at 1080p@30fps between 2.5 - 5 Mbps on average with caps at 5 - 8 Mbps. + +- HD 360 VR: 10 - 80 Mbps + +NOTE 2: For viewport agnostic, the 8k UHD numbers as defined in clause 5.1 apply. For viewport dependent, the bitrates likely can be reduced to half. + +- According to [44], with HEVC at 4K@30fps between 10 - 18 Mbps on average with caps between 15 - 25 Mbps. + +- Retinal VR: 15 - 150 MbpsNOTE 3: For viewport agnostic, the 8k UHD numbers multiplied by 4 as defined in clause 5.1 apply. For viewport dependent, the bitrates likely can be reduced to half or even on third. + +- According to [44], with HEVC at 8K@30fps between 30 - 35 Mbps on average with caps at 42 Mbps. + +NOTE 4 on framerates: cinema content is usually captured and distributed at 24 fps. TV content is usually captured and distributed at 50 or 60 fps depending on the region. The above video bitrates include frame rates of up to 60fps. + +NOTE 5 on bitrate ranges: the bitrates are dependent on codec (e.g. AVC/H.264 [14] or HEVC/H.265 [15]), on content type and whether it is live or on-demand. Bitrates are expected to be reduced with expected encoder implementation enhancements and new codecs. In the past, that reduction has been observed to be in the order of 50 % every 10 years. + +## 5.3 Typical conversational speech/audio and video bitrates + +The following bitrates are typical in commercial services according to clause 4.3: + +- Narrowband voice (mono): 7.2-13.2 kbps +- Wideband voice (mono): 7.2-24.4 kbps +- Super-wideband voice (mono): 9.6-24.4 kbps +- Fullband voice (mono): 16.4-[TBD] kbps + +NOTE: Unlike NB, WB and SWB which all are audio bandwidths used in commercial networks, no FB usage has yet been seen for commercial conversational services. + +- VGA video: 300 - 900 kbps +- 720p HD video: 800 - 1500 kbps +- Telepresence video 1080p: 1500 - 3000 kbps + +## 5.4 Typical uplink A/V streaming of A/V, including 360 VR content + +### 5.4.1 Professional production content bitrates + +Table 5.4.1-1 lists common content formats from professional cameras that are output in uncompressed form over the SDI interface, and their corresponding bit rates: + +NOTE 1: The formal standard references are listed in table 5.4.1-1. + +NOTE 2: See also 3GPP TR 22.827 [35]. + +NOTE 3: The SDI rates given below are for wired connections within professional production environments. + +**Table 5.4.1-1: SDI interface, and their corresponding bit rates** + +| Standard | Name | Bitrates | Example video formats | +|--------------------|------------------|----------------------------------------------------|-----------------------| +| SMPTE 259M [31] | SD-SDI | 270 Mbit/s, 360 Mbit/s, 143 Mbit/s, and 177 Mbit/s | 480i, 576i | +| SMPTE 344M [31] | ED-SDI | 540 Mbit/s | 480p, 576p | +| SMPTE 292M [31] | HD-SDI | 1.485 Gbit/s, and 1.485/1.001 Gbit/s | 720p, 1080i | +| SMPTE 372M [31] | Dual Link HD-SDI | 2.970 Gbit/s, and 2.970/1.001 Gbit/s | 1080p60 | +| SMPTE 424M [31] | 3G-SDI | 2.970 Gbit/s, and 2.970/1.001 Gbit/s | 1080p60 | +| SMPTE ST-2081 [32] | 6G-SDI | 6 Gbit/s | 2160p30 | +| SMPTE ST-2082 [33] | 12G-SDI | 12 Gbit/s | 2160p60 | +| SMPTE ST-2083 [34] | 24G-SDI | 24 Gbit/s | 2160p/4k@120,8k@60 | + +SMPTE ST 2110 [12] can support transport of compressed or uncompressed streams from cameras with the resolutions above. According to [13], in case of uncompressed streams, the video rates for YCbCr 4:2:2 10b format can be derived as follows. + +**Table 5.4.1-2: ST 2110 Video uncompressed streams bitrates** + +| Format | Corresponding ST 2110 Video uncompressed bitrate (YCbCr 4:2:2 10b) [12] in Gbps | +|---------------------|---------------------------------------------------------------------------------| +| 480p30, 576p25 | 0.221 | +| 720p50/60 | 0.982 / 1.178 | +| 1080p50/60 | 2.210 / 2.650 | +| 2160p50/60 | 8.842 / 10.600 | +| 2160p100 (4K) | 17.684 | +| 4320p50/60/100 (8K) | 36.103 / 43.280 / 72.206 | + +Audio uncompressed channels come in addition, but their bitrates are some magnitude smaller than uncompressed video. + +Light compression can also be used for such production environments using for example VC-2 (ST 2042-1:2017 - SMPTE Standard - VC-2 Video Compression) [36] which is typically used with a coding ratio of 4:1 and MJ2 - Motion JPEG 2000 (ISO/IEC IS 15444-3 | ITU-T T.802)[37] which is typically used with a coding ratio of 6:1. + +Compression is used for portable cameras equipped with wireless (Wireless LAN and 4G LTE) modules. The bitrates are 9, 6, 3, 2Mbps for up to 720p@60fps and 9, 6, 3 Mbps for 1080@30fps with AVC/H.264 [14]. + +### 5.4.2 Live uplink contribution professional content bitrates + +Contribution feeds as seen in real deployed systems: + +- 80 Mbps 422 10 bits for HD @60fps +- 165 Mbps 422 10 bits for UHD (4K, AVC/H.264 [14]) @60fps +- 120 Mbps 422 10 bits for UHD (4K, HEVC/H.265 [15]) @60fps + +- Normal quality 360 VR: [TBD 96 Mbps] +- High quality 360 VR: [TBD 140 Mbps] + +NOTE 1: The above video profiles include frame rates of up to 60fps. + +- Broadcast auxiliary services (e.g. electronic news gathering) according to Recommendation ITU-R BT.1872-3 [9]:21-35 Mbps for HD TV (AVC/H.264 [14]) +- 18-30 Mbps for HD TV (HEVC/H.265 [15]) +- 96-145 Mbps for UHD TV (4K, HEVC/H.265 [15]) +- 140-285 Mbps for UHD TV (8K, HEVC/H.265 [15]) +- Compressed audio: 96-180 kbps per channel +- Uncompressed audio: 768-1152 kbps per channel + +NOTE 2: The lower video rates from BT.1872-3 concern a single codec while the higher rates have headroom for 3 coding steps in tandem. + +### 5.4.3 User generated content + +The following bitrates are typical for user generated content: + +- 720p HD: 3 - 10 Mbps + +NOTE 1: Today typically 5-10 Mbps for AVC [14] depending on frame rate and dynamic range, but bitrate reductions expected with better encoding and coding tools. See Clause 6.1.2. + +- Full HD: 5 - 15 Mbps + +NOTE 2: Today typically 8-15 Mbps for AVC [14], but bitrate reductions expected with better encoding and coding tools. See Clause 6.1.2. + +- 4k UHD: 10 - 85 Mbps + +NOTE 3: Today typically 8-16 Mbps for HEVC [15] and 15-25 Mbps for AVC [14], but bitrate reductions expected with better encoding and coding tools. See Clause 6.1.2. + +- 8k UHD: 20 - 150 Mbps + +NOTE 4: No information is available today, but the numbers are extrapolated from 4K by multiplying with a factor 4. + +- Basic 360 VR: the numbers for 4k UHD apply +- HD 360 VR: the numbers for 8k UHD apply +- Retinal VR: this is roughly 16k as expected, so a factor 4 to 8k UHD is applicable, i.e. 40-300 Mbps +- Normal quality audio: 24.4kbps/channel + +NOTE 5: Super-wideband 3GPP audio codecs may be used. + +- High quality audio: 128kbps/channel + +NOTE 6 on user generated content: the video bitrate ranges are wide as user generated content may have different quality expectations including semi-professional content. + +## 5.5 Typical Traffic Characteristics for Cloud gaming + +For cloud gaming, the downlink streaming of 720p/1080p/4k @60fps encoded A/V typically consists of a 5-35Mbps bitstream. One instance of a cloud gaming service requires a minimum uplink bitrate of 1.5 Mbps [21]. + +In the future the cloud gaming is presumed to reach up to 8k resolutions and up to 120fps downlink bitstreams. No information on such currently deployed services are available to formulate typical bitrates. However, Clause 6 provides indication that allows estimation of bitrates. Annex A provides background information on deployed cloud gaming services. + +Different game types result in different round-trip user interaction delay requirements (sometimes referred also as acceptable game latency). As discussed in TR 26.928 [30], clause 4.2, with regards to such requirements, games may be divided into the following 4 types: games requiring (i) at most 50 ms, (ii) at most 100 ms, (iii) at most 200ms, and (iv) games with no latency requirements. The game latency impacts the traffic model as well as the requirements on the delivery system. The shorter the latency requirements, the higher the expected bitrate. + +Cloud gaming traffic characteristics are also discussed in 3GPP TR 26.928 [30], clause 6 as well as TR 26.926 [47]. + +## 5.6 XR Traffic Characteristics + +Initial typical bitrates and traffic characteristics for XR services are collected in 3GPP TR 26.928 [30], clause 6 as well as TR 26.926 [47]. A summary of expected bitrates and traffic characteristics are provided: + +- Viewport-independent 6DOF streaming + - Downlink only + - HTTP Streaming + - Up to 100 Mbps to address high-quality 6DOF VR services to allow 2k per eye streaming at 90 fps (see TR 26.928, clause 4.2 and 6.2.2) +- Viewport-dependent 6DOF streaming + - Downlink only + - HTTP streaming, HTTP/TCP level information and responses are exchanged every 100-200 ms in viewport-dependent streaming. + - Up to 25 - 50 Mbps to address high-quality 6DOF VR services to allow 2k per eye streaming at 90 fps (see TR 26.928, clause 4.2 and 6.2.3) +- Raster-based split rendering + - Primarily downlink + - for H.264/AVC the bitrates are in the order of up to 50 Mbps per eye buffer, i.e. up to 100 Mbit/s. + - for H.265/HEVC the bitrates are in the order of 20 - 30 Mbps per eye buffer, i.e. 40 – 60 Mbit/s + - packet latency requirements are in the range of 15ms + - Application Layer FEC may be used with overhead from 10-50%, typically something like 30% + - uplink pose information (see TR 26.926 [47], clause 5.8) + - typically every 10 -15ms constant packet size of up to 100 bytes + - packet latency requirements are 10 – 15 ms +- Generalized split rendering + - details are FFS +- XR conversational + - details are FFS + +# 6 Overview on technological developments for existing and emerging services + +## 6.1 Technology Developments + +### 6.1.1 Overview + +This clause collects developments in the industry on compression advances, content formats, protocol improvements and other advances that may impact the traffic characteristics documented in clause 4. + +### 6.1.2 Compression Improvements + +Due to the increasing consumption of video content with higher resolutions, the need for more efficient video compression techniques is growing. The first version of the High Efficiency Video Coding (HEVC) standard [15], jointly developed by the ITU-T VCEG and the ISO MPEG, was finalized in 2013. A wide range of products and services support HEVC [15] for video encoding/decoding, especially for Ultra High Definition (UHD) content, where HEVC [15] can provide around 50% bitrate savings for the same subjective quality as its predecessor H.264/AVC [14]. + +Both codecs are defined as part of the TV Video Profiles in TS 26.116 [5] and are also the foundation of the VR Video Profiles in TS 26.118 [6]. + +Work on video compression technologies beyond the capabilities of HEVC [15] are continued by the MPEG/ITU, with the creation of the Joint Video Exploration Team (JVET) on future video coding in October 2015. Many new coding tools have been proposed in the context of JVET, which eventually led to a Call for Proposals on video coding technologies with video compression capabilities beyond HEVC [15]. The reference software used in the exploration phase of JVET, called Joint Exploration Model (JEM), was leveraged as the base for the majority of responses to the call. Results included responses demonstrating compression efficiency gains of around 40 % or more with respect to HEVC [15]. This initiated the work by the Joint Video Experts Team (JVET) on the development of a new video coding standard, to be known as Versatile Video Coding (VVC). + +MPEG has started working on a new video coding standard to be known as MPEG-5 Essential Video Coding (EVC) in January 2019. MPEG-5 EVC aims to provide a standardized video coding solution to address business needs in some use cases, such as video streaming, where existing ISO video coding standards have not been as widely adopted as might be expected from their purely technical characteristics. In addition, a main profile adds a small number of additional tools, each of which is individually capable of being either properly deactivated or switched to the corresponding basic tool. The target coding efficiency for the call for proposals was to be at least as efficient as HEVC. This target was exceeded by approximately 24 % in the responses to the call for proposals, which were evaluated at this meeting. The development of the MPEG-5 EVC standard is expected to be completed in 2020. + +Figure 6.1.2-1 shows the typical improvements of video compression rates over time as well as the target for the VVC standard. It is also observed that compression technologies have enabled the reduction of bitrates by 50 % in a time frame of 7-10 years. Most of the gains come by the increase of encoding and decoding complexity, spurred according to Moore's law. + +![Figure 6.1.2-1: Video bitrate efficiency improvements and target for the final VVC standard. The graph plots PSNR (dB) on the y-axis (28 to 40) against bit rate (kbit/s) on the x-axis (0 to 300). Curves represent different video standards: H.261 (1991), JPEG (1990), H.262 / MPEG-2 (1995), H.264 / MPEG-4 AVC (2003), H.265 / MPEG-HEVC (2013), and H.??? / MPEG-VVC. A dashed green line for H.??? / MPEG-VVC shows a significant improvement, with a 'Bit-rate Reduction Target: 50%' indicated. A small inset image shows a man in a hard hat, labeled 'Foreman 10 Hz, QCIF 100 frames'. The Fraunhofer Heinrich Hertz Institute logo is in the bottom right.](fed39b841ae2dce01088b84bfc1e2789_img.jpg) + +Figure 6.1.2-1: Video bitrate efficiency improvements and target for the final VVC standard. The graph plots PSNR (dB) on the y-axis (28 to 40) against bit rate (kbit/s) on the x-axis (0 to 300). Curves represent different video standards: H.261 (1991), JPEG (1990), H.262 / MPEG-2 (1995), H.264 / MPEG-4 AVC (2003), H.265 / MPEG-HEVC (2013), and H.??? / MPEG-VVC. A dashed green line for H.??? / MPEG-VVC shows a significant improvement, with a 'Bit-rate Reduction Target: 50%' indicated. A small inset image shows a man in a hard hat, labeled 'Foreman 10 Hz, QCIF 100 frames'. The Fraunhofer Heinrich Hertz Institute logo is in the bottom right. + +**Figure 6.1.2-1: Video bitrate efficiency improvements and target for the final VVC standard [reproduced with appropriate permission from Fraunhofer]** + +Table 6.1.2-1 provides a summary of the expected compression efficiency of different codecs and expectations on target bitrates for different video technologies. + +**Table 6.1.2-1: Expected Video coding standards performance and bitrate target** + +| Codec | Coding performance (Random-Access) | | Targeted bitrate (Random Access) | +|---------------------|----------------------------------------------------------------------------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Objective | Subjective | | +| HEVC | -40 % vs AVC [24][25][26] | -60 % vs AVC [24][25][26] | 4k:
  • Statmux: 10-13 Mbps
  • CBR: 18-25 Mbps
8k:
  • CBR: 40-56 Mbps
  • High quality: 80-90 Mbps [24][25][26]
| +| EVC-Baseline | -30 % vs AVC [27][29] | n/a | Not expected for 4k or 8k | +| EVC-Main | -24 % vs HEVC [27][29] | n/a | Expected [27][29]
4k CBR: 15-19Mbps
8k CBR: 30-60 Mbps | +| VVC | -30 % vs HEVC [28][29]
Best-CfP: -42 % vs HEVC
Target: -50 % vs HEVC | n/a | Expected [28][29]
4k CBR: 10-15 Mbps
8k CBR: 25-35 Mbps | + +NOTE: (Average) with peaks up to 25Mbps thanks to STATMUX. + +Also noteworthy is the improvement of encoders over time even for existing standards which also leads to bitrate reductions at the same quality. + +Based on this information it can be expected that within the time frame until 2025, video compression technology permit bitrate reductions by a factor of 50 % compared to what is today possible with HEVC [15]. + +However, not to forget according to Jevons Paradox, stating that the efficiency with which a resource is used tends to increase (rather than decrease) the rate of consumption of that resource. This may well mean that the compression efficiency gains spur even more traffic. + +Additional updates to video characteristics and bitrates are available in 3GPP TR 26.955 [46]. + +### 6.1.3 New Media Formats + +New media formats in media generation and distribution are developed on a continuous basis, taking into account improvements in capturing and display systems. TR 26.949 [16] collects TV distribution formats as they were considered in the time frame of 2015 to 2017. The parameters are summarized in clause 5.4 of the present document in terms of: + +- Spatial Resolution +- Frame Rates +- Colorimetry +- Other parameters + +The latest versions, referred to as UHD-1 Phase 2 is summarized according to TR 26.949, clause 5.4.8: + +- UHD-1 phase 2 exclusively operates with HEVC [15] and bit depth of 10 bit. +- only square pixel resolutions and only progressive scan are supported. +- Only BT.2100 [33] non-constant luminance YCbCr is supported. +- High Dynamic Range is added either through the PQ10 or the HLG10 system, relying on HEVC Main-10 Level 5.1 [15]. +- Optional SEI metadata may be provided in the bitstream using HEVC specified SEI messages [15]. +- Addition of High Frame Rate (HFR), i.e. addition of 100, 120 000/1 001 and 120 Hz. +- HFR can be supported by two means: + - Single PID HFR bitstream. + - Dual PID and temporal scalability when the bitstream is intended to be decodable by UHD phase 1 receivers at half frame rate. +- For HFR on HEVC Main-10 Level 5.2 [15] is required. +- Support for Next Generation Audio (NGA) to enable immersive and personalized audio content. + +The TV Video Profiles in TS 26.116 [5] address coded representations of the UHD-1 phase 2 signals to the most extent. Table 6.1.3-1 provides an overview of the TV relevant formats considered in the context of 3GPP TV Video Profiles. + +**Table 6.1.3-1: TV over 3GPP services Video Profile Operation Points (TS 26.116 [5])** + +| Operation Point name | Resolution format | Picture aspect ratio | Scan | Max. frame rate | Chroma format | Chroma sub-sampling | Bit depth | Colour space format | Transfer Characteristics | +|------------------------|-------------------|----------------------|-------------|-----------------|---------------|---------------------|-----------|---------------------|--------------------------| +| H.264/AVC 720p HD | 1280 × 720 | 16:9 | Progressive | 30 | Y'CbCr | 4:2:0 | 8 | BT.709 | BT.709 | +| H.265/HEVC 720p HD | 1280 × 720 | 16:9 | Progressive | 30 | Y'CbCr | 4:2:0 | 8 | BT.709 | BT.709 | +| H.264/AVC Full HD | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 8 | BT.709 | BT.709 | +| H.265/HEVC Full HD | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 8; 10 | BT.709; BT.2020 | BT.709; BT.2020 | +| H.265/HEVC UHD | 3840 × 2160 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 | BT.2020 | +| H.265/HEVC Full HD HDR | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 | BT.2100 PQ | +| H.265/HEVC UHD HDR | 3840 × 2160 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 | BT.2100 PQ | +| H.265/HEVC Full HD | 1920 × 1080 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 | BT.2100 HLG | + +| Operation Point name | Resolution format | Picture aspect ratio | Scan | Max. frame rate | Chroma format | Chroma sub-sampling | Bit depth | Colour space format | Transfer Characteristics | +|------------------------------|-------------------|----------------------|-------------|-----------------|---------------|---------------------|-----------|---------------------|--------------------------| +| HDR HLG | | | | | | | | | | +| H.265/HEVC
UHD HDR
HLG | 3840 x 2160 | 16:9 | Progressive | 60 | Y'CbCr | 4:2:0 | 10 | BT.2020 | BT.2100 HLG | + +Looking further into the future, there is currently only one 8K broadcast service being supported by the Japanese public service broadcaster NHK. This runs 12 hours a day and is to be utilised as part of the promotion for the upcoming Olympics in Japan. This service is supported by a government initiative. A summary of the service launched by NHK was published in [42] and a more detailed description can be found in the IBC paper "Ready for 8K UHDTV broadcasting in Japan" [41]. + +France Television performed a trial of 8K delivery of the Roland Garros Tennis Championship by 5G in June 2019, details can be found in [43]. + +For VR production and distribution, the ITU recommends [TBA] that for eye not to perceive pixels for 360VR, 30K by 15K images should be provided, though other criteria may be used in system design. + +### 6.1.4 Protocol Improvements + +Most of the video traffic used HTTP and TCP for the delivery of both wired and wireless Internet. The transmission control protocol, mostly known as TCP or TCP/IP [17], has been invented over 40 years ago. Over the years, it has been evolving steadily and it became the number transport protocol on the Internet and finally also on mobile networks. Today, around 75 % of the traffic is encrypted in mobile data networks. TCP, in combination with TLS, requires three round trips before the actual data can be sent. However, innovation in the context became very hard. + +In response to these challenges with slow innovation of TCP, Internet companies started experimenting with proprietary protocols build on top of UDP. UDP is a very basic protocol. It only provides the bare minimum functionality and is suitable for new protocols to be built on top of it. It is well supported by all infrastructure on the Internet. Protocols on top of UDP can be implemented in applications so it allows for rapid deployment of new versions. The experiments with UDP protocols evolved into an effort to bring in the engineering community and openly collaborate on a single protocol framework on top of UDP. An Internet Engineering Task Force working group has been established to specify a protocol called QUIC (Quick UDP Internet Connections). Shortly it is likely to see the first QUIC Internet standard published [18]. + +The QUIC Protocol is the next generation of transport for the Internet and is on track to become ubiquitous on end-user platforms and within all server-side workflows. Unlike prior standard technologies, which are struggling to innovate due to compatibility issues with existing infrastructure, QUIC operates on top of UDP in the application layer and that brings flexibility to deploy new features in rapid iterations. + +Google introduced QUIC back in 2013 as an experimental protocol to reduce TCP connection and transport latencies. QUIC, on the other hand, minimizes the number of set-up round trips by combining UDP transport and its own cryptographic handshake. For connections to the same origin server, QUIC facilitates a zero round trip time. + +QUIC also re-implements TCP loss recovery, over UDP and, by using multiplexed connections, it eliminates TCP's head-of-line blocking. This ensures that lost packets do not block any other stream but only those with data in it. Last, but not least, QUIC moves congestion control to the application and the user space, enabling a rapid evolution for the protocol, as opposed to kernel space TCP. + +QUIC has been nicely designed to allow being enabled seamlessly for existing video workflows without any changes needed in the video formats or players. Akamai reports as an example that for a measurement is from a soccer event in 2018 a 25 % throughput improvement for median viewer was achieved compared to TCP for desktop. QUIC performances gains for mobile compared to TCP/TLS, while still positive, have found not to be that significant as for desktop, in particular for video content. + +There are several features of the protocol that contribute to improved video quality, among others: + +- With usual TCP&TLS session which forms HTTPS streaming, there has to be 3 or 4 exchanges of information back and forth between the client and the server, before the video request is made. With QUIC there's none needed, assuming the client communicated with the server previously. The first packet from the client already contains the video request, and the first packet from the server already contains the video content. Or in case the client has not communicated with the server before, it only takes one roundtrip between the client and server. This reduces latency greatly. TCP has similar features available with new version of TLS, TLS-1.3, and TCP Fast Open feature but its deployment is complicated. The 0-RTT (zero round trip time) connection establishment for returning connections applies to about 50 % of connections. +- QUIC also uses more efficient loss recovery - due to more information being provided about the lost packets and timing. +- QUIC allows Multiplexing without head-of-line blocking, i.e. if one packet gets lost then all requests affected. +- QUIC also allows connection migration across different access networks. +- It also allows to measure the performance of each feature and use and apply it selectively for specific deployments. + +On mobile QUIC benefits seem to also be tangible. On mobile Android devices, Google claimsi that QUIC has helped to reduce latency of Google Search responses by 3.6 % and YouTube video buffering by 15.3 %. It was found that by November 2017, QUIC represented 20 % of the total mobile traffic and expected to grow to 35 % by end of 2018. According to MVI data, video accounts for approximately 58 % of the total mobile internet traffic and video represents 64 % of the total QUIC traffic. By November 2018, approximately 90 % of internet traffic will be encrypted and QUIC will be 32 % of global Internet traffic. + +QUIC being an encryption-based protocol such as HTTP/TLS, traffic is typically encrypted over the mobile network delivery, meaning that the use of traditional traffic management tools is limited. On top of what is also observed for HTTP/TLS, QUIC allows multiplexing multiple streams over a single connection, but this comes with the added downside that it is impossible to differentiate between the different streams as the signalling header with the stream identifier is also encrypted. + +Another technology and protocol in media distribution is developed under the umbrella of ABR Multicast. With the recent proliferation of live streaming, especially of premium sports, over the Internet, issues in scale and quality have been exposed. The challenge partially lies in scaling the services to millions of simultaneous users, but also in the associated peering and delivery costs as well as the end-to-end latency. Multicast ABR addresses a problem that had already been solved in the context of managed networks for IPTV with IGMP. However, it is quite difficult to replicate IGMP exactly over an unmanaged network. However, in practice it is possible to control delivery of streams quite precisely over a large part of their journey and multicast ABR effectively provides a tunnel through which multiple unicast streams are combined into single ones, just as with traditional multicast. Multiple unicast streams are converted at the entrance of the tunnel into a single stream and then back to multiple unicast as they exit in a process known as transcasting. These processes have since been documented either as a standard or guidelines towards a standard, by both the DVB [19] and by Cable Labs [20]. Products are being built around these guidelines, with many operators currently in proof of concept or field trials of the technology.] + +### 6.1.5 Impact on Media Services + +The impact of these new developments on Media Service is FFS. + +# --- 7 Characteristics and requirements for different media services on 3GPP networks + +## 7.1 Introduction + +This clause collects characteristics and requirements for different media services on 3GPP networks. + +## 7.2 Collection process for requirements for different media services on 3GPP networks + +Use cases are collected in the context of the present document. The use cases come with an analysis of certain characteristics. For this purpose a template is provided below. + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media Service Description | +| Name: [e.g. StreamOn] | +| Date of submission: [e.g. 18 th October 2018] | +| Source: [e.g. DT] | +| Description: [Free text giving high level description of the service] | +| Categorization | +| Type: [e.g. Third Party, Operator, Combination of both, Other] | +| Status: [e.g. planned, PoC, trialed, commercially deployed] | +| Category: [e.g. Download, Live streaming, On-demand streaming, Interactive, Conversational] | +| Used Technologies | +| Codecs: [e.g. AAC, HE-AAC, HEVC/H.265, AVC/H.264 with Profiles and levels used] | +| Media types and formats: [e.g. 4K video, HDR video, stereo or 5.1 audio] | +| Media protocols and containers: [e.g. DASH, HLS, CMAF, ISOBMFF, MP4, MPEG2 TS, RTP] | +| Transport protocols: [e.g. FLUTE, UDP, TCP, QUIC, HTTP 1.1, HTTP 2.0] | +| Clients: [e.g. iOS or android application, browser, set top boxes, TV set] | +| Others: [e.g. DRM, interactivity framework, QoE and analytics, QoS handling] | +| Deployment Statistics | +| [e.g. number of clients, traffic volumes] | +| Traffic Characteristics | +| Bitrate Characteristics: [typical target bitrates, minimum required bitrate, maximum necessary bitrate,] | +| Other KPIs [end-to-end latency, tune-in times, etc.] | +| Potential mapping to 5QIs (5G QoS Identifier - See TS 23.501 Clause 5.7.4 and Table 5.7.4-1 copied below):
[which 5QIs among 1, 2, 3, 4, 6, 7, 8, 9, 80, e.g. 6, "video buffered streaming and TCP based"] | +| References | +| [list of public documentation in support of the present description e.g. a URL, a scientific publication, an industry or standards organization specification] | +| Any additional information | +| | + +**Table 7.2-1: Standardized 5QI to QoS characteristics mapping (from TS 23.501)** + +| 5QI Value | Resource Type | Default Priority Level | Packet Delay Budget | Packet Error Rate | Default Maximum Data Burst Volume (NOTE 2) | Default Averaging Window | Example Services | +|-----------|---------------------|------------------------|---------------------|-------------------|--------------------------------------------|--------------------------|--------------------------------------------------------------------------------------------------------------------| +| 1 | GBR
(NOTE 1) | 20 | 100 ms | $10^{-2}$ | N/A | 2000 ms | Conversational Voice | +| 2 | | 40 | 150 ms | $10^{-3}$ | N/A | 2000 ms | Conversational Video (Live Streaming) | +| 3 | | 30 | 50 ms | $10^{-3}$ | N/A | 2000 ms | Real Time Gaming,
V2X messages
Electricity distribution - medium voltage,
Process automation - monitoring | +| 4 | | 50 | 300 ms | $10^{-6}$ | N/A | 2000 ms | Non-Conversational Video (Buffered Streaming) | +| 65 | | 7 | 75 ms | $10^{-2}$ | N/A | 2000 ms | Mission Critical user plane Push To Talk voice (e.g., MCPTT) | +| 66 | | 20 | 100 ms | | N/A | 2000 ms | Non-Mission-Critical user plane Push To Talk voice | +| 67 | | 15 | 100 ms | $10^{-3}$ | N/A | 2000 ms | Mission Critical Video user plane | +| 75 | | 25 | 50 ms | $10^{-2}$ | N/A | 2000 ms | V2X messages | +| 5 | Non-GBR
(NOTE 1) | 10 | 100 ms | $10^{-6}$ | N/A | N/A | IMS Signalling | +| 6 | | 60 | 300 ms | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | +| 7 | | 70 | 100 ms | $10^{-3}$ | N/A | N/A | Voice,
Video (Live Streaming)
Interactive Gaming | +| 8 | | 80 | 300 ms | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | +| 9 | | 90 | | | | | | +| 69 | | 5 | 60 ms | $10^{-6}$ | N/A | N/A | Mission Critical delay sensitive signalling (e.g., MC-PTT signalling) | +| 70 | | 55 | 200 ms | $10^{-6}$ | N/A | N/A | Mission Critical Data (e.g. example services are the same as QCI 6/8/9) | +| 79 | | 65 | 50 ms | $10^{-2}$ | N/A | N/A | V2X messages | +| 80 | | 68 | 10 ms | $10^{-6}$ | N/A | N/A | Low Latency eMBB applications Augmented Reality | +| 82 | Delay Critical GBR | 19 | 10 ms
(NOTE 4) | $10^{-4}$ | 255 bytes | 2000 ms | Discrete Automation (see TS 22.261 [2]) | +| 83 | | 22 | 10 ms
(NOTE 4) | $10^{-4}$ | 1358 bytes
(NOTE 3) | 2000 ms | Discrete Automation (see TS 22.261 [2]) | +| 84 | | 24 | 30 ms
(NOTE 6) | $10^{-5}$ | 1354 bytes | 2000 ms | Intelligent transport systems (see | + +| | | | | | | | | +|----|--|----|------------------|-----------|-----------|---------|-----------------------------------------------------------| +| | | | | | | | TS 22.261 [2] | +| 85 | | 21 | 5 ms
(NOTE 5) | $10^{-5}$ | 255 bytes | 2000 ms | Electricity Distribution-high voltage (see TS 22.261 [2]) | + +NOTE 1: A packet which is delayed more than PDB is not counted as lost, thus not included in the PER. +NOTE 2: It is required that default MDBV is supported by a PLMN supporting the related 5QIs. +NOTE 3: This MDBV value is set to 1354 bytes to avoid IP fragmentation for the IPv6 based, IPSec protected GTP tunnel to the 5G-AN node (the value is calculated as in Annex C of TS 23.060 [56] and further reduced by 4 bytes to allow for the usage of a GTP-U extension header). +NOTE 4: A delay of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. +NOTE 5: A delay of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. +NOTE 6: A delay of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. + +NOTE 1: For Standardized 5QI to QoS characteristics mapping, the table will be extended/updated to support service requirements for 5G, e.g. ultralow latency service. + +NOTE 2: It is preferred that a value less than 64 is allocated for any new standardised 5QI of non-GBR Resource Type. This is to allow for option 1 to be used as described in clause 5.7.1.3 of TS 23.501 (as the QFI is limited to less than 64). + +## 7.3 Summary of Responses for Streaming Services + +### 7.3.1 Introduction + +This clause provides a summary of the information that was collected for streaming services. The current information is based on responses from: + +- Comcast VIPER +- AWS Media Services +- Hulu +- Bitmovin +- ARD Mediathek + +The services address live and On-demand streaming services. + +### 7.3.2 Used Technologies + +#### 7.3.2.1 Codecs + +The pre-dominant video codec for the services is still H.264/AVC [14]. H.265/HEVC [15] is also in deployments. Non-MPEG video codecs such as VP9 or AV1 are in use or expected to be in use, but much less prominent than MPEG codecs according to the responses. + +The pre-dominant audio codec is AAC, with some variants. Also, AC-3 is used quite often to support beyond stereo experiences. No other audio codec was mentioned. + +#### 7.3.2.2 Media types and formats + +Most of the services run HD video. Experiments with UHD and HDR are ongoing. Different HDR formats (i.e. HDR10, Dolby Vision, HLG, and SL-HDR) are in use. + +For audio, stereo is deployed and 5.1 is also broadly used. Some initial experiments are done with multichannel audio, NGA (Next Generation Audio). + +#### 7.3.2.3 Media protocols and containers + +All services deploy DASH and HLS. On HLS, the MPEG-2 TS still is maintained. For DASH, exclusively ISO BMFF based distribution is used but a convergence towards a common segment format based on CMAF for DASH and HLS is expected. + +Other formats such as RTMP or RTP are maintained to some extent for legacy reasons. + +#### 7.3.2.4 Transport protocols + +HTTP/1.1 with TCP/IP is used almost exclusively. Some initial tests are ongoing on HTTP/2.0 and HTTP/3 (also known as HTTP over QUIC). No received response indicates the use of multicast protocols. + +#### 7.3.2.5 Clients + +All services provide client application running on iOS and Android for Browser-based playback as well as applications or native integration into set-top boxes, HDMI sticks (i.e. Apple TV™, Fire TV™, Chromecast™, Tizen™) and TV Sets. Game consoles are also targeted. + +#### 7.3.2.6 Other Technologies + +Other mentioned deployed technologies are: + +- DRM (Widevine, PlayReady, Fairplay) based on common encryption +- Analytics collection and QoE Measurement +- Dynamic Ad Insertion +- Watermarking + +### 7.3.3 Traffic Characteristics + +#### 7.3.3.1 Bitrate Characteristics + +Average streaming bitrate + +- STBs: 4-6Mbps +- Mobile applications and browsers: less than 4-6Mbps +- 4K content: 10-15Mbps + +Average segment durations + +- 6 seconds + +#### 7.3.3.2 Other KPIs + +Other KPIs such as video start time, video playback failure, rebuffering ratio, connection induced rebuffering, minimum/average bitrates, ABR adaptation frequency were not reported. + +#### 7.3.3.3 Potential mapping to 5QIs + +Commonly targeted 5QI values are 6 and 8. Others are considered interesting for specific services. + +# 8 Applicability of existing 5QIs + +## 8.1 QoS Model + +### 8.1.1 Overview + +Clause 5.7 of TS 23.501 [10] explains the QoS Model for 5G. The 5G QoS model is based on QoS Flows. The 5G QoS model supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows). The 5G QoS model also supports Reflective QoS (see clause 5.7.5 of TS 23.501 [10]). + +A QoS Flow ID (QFI) is used to identify a QoS Flow in the 5G System. User Plane traffic assigned to the same QoS Flow within a PDU Session receives the same traffic forwarding treatment (e.g. scheduling, admission threshold). + +The QFI may be dynamically assigned or may be equal to the 5QI, for more details on existing 5QI see clause 8.1.2. + +A QoS Flow may either be 'GBR', 'Non-GBR' or "Delay Tolerant GBR" depending on its QoS profile and it contains QoS parameters as follows: + +- For each QoS Flow, the QoS profile includes the QoS parameters: + - 5G QoS Identifier (5QI); and + - Allocation and Retention Priority (ARP). +- For each Non-GBR QoS Flow only, the QoS profile can also include the QoS parameter: + - Reflective QoS Attribute (RQA). +- For each GBR QoS Flow only, the QoS profile also include the QoS parameters: + - Guaranteed Flow Bit Rate (GFBR) - UL and DL; and + - Maximum Flow Bit Rate (MFBR) - UL and DL; and +- In the case of a GBR QoS Flow only, the QoS profile can also include one or more of the QoS parameters: + - Notification control; + - Maximum Packet Loss Rate - UL and DL + +The usage of a dynamically assigned 5QI for a QoS Flow requires in addition the signalling of the complete 5G QoS characteristics (described in clause 5.7.3 of TS 23.501 [10]) as part of the QoS profile. + +The principle for classification and marking of User Plane traffic and mapping of QoS Flows to Access Network (AN) resources is illustrated in Figure 8-1-1. + +![Diagram illustrating the principle for classification and User Plane marking for QoS Flows and mapping to AN Resources. The diagram shows three main components: Application / Service Layer, UE, and UPF, connected via an AN (Access Network).](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +The diagram illustrates the flow of data packets through the User Plane (UP) for QoS management. At the top, the **Application / Service Layer** sends **Data packets from applications** to the **UE** (User Equipment). In the UE, **QoS rules** (mapping UL packets to QoS flows and apply QoS flow marking) are applied. The packets are then categorized into **QoS Flow** (all packets marked with the same QFI). The UE maps these **QoS flows to AN Resources**. The packets then enter the **AN** (Access Network) via a **PDU Session**. In the AN, the packets are processed through **AN Resources**. Finally, the packets reach the **UPF** (UPF), where **PDRs** (classify packets for QoS flow marking and other actions) are applied. + +Diagram illustrating the principle for classification and User Plane marking for QoS Flows and mapping to AN Resources. The diagram shows three main components: Application / Service Layer, UE, and UPF, connected via an AN (Access Network). + +**Figure 8.1-1: The principle for classification and User Plane marking for QoS Flows and mapping to AN Resources** + +### 8.1.2 5G QoS Parameters + +A 5QI is a scalar that is used as a reference to 5G QoS characteristics defined in clause 5.7.4 of TS 23.501 [10], i.e. access node-specific parameters that control QoS forwarding treatment for the QoS Flow (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). + +Standardized 5QI values have one-to-one mapping to a standardized combination of 5G QoS characteristics as specified in Table 5.7.4-1 of TS 23.501 [10] and shown below in Table 8.1.4-1. + +A summary of the most relevant QoS Parameters is provided as follows. For details, please refer to TS 23.501 [10], clause 5.7.2: + +- Guaranteed Flow Bit Rate (GFBR) - UL and DL, for GBR QoS Flows only: denotes the bit rate that is guaranteed to be provided by the network to the QoS Flow over the Averaging Time Window. +- Maximum Flow Bit Rate (MFBR) -- UL and DL, for GBR QoS Flows only limits the bit rate to the highest bit rate that is expected by the QoS Flow (e.g. excess traffic may get discarded or delayed by a rate shaping or policing function). +- The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the QoS flow that can be tolerated in the uplink and downlink direction, if the flow is compliant to the GFBR and is only used for voice media traffic in rel.16. + +### 8.1.3 5G QoS Characteristics + +In addition to 5G QoS parameters, also 5G QoS characteristics are defined in TS 23.501 [10]. The characteristics describe the packet forwarding treatment that a QoS Flow receives edge-to-edge between the UE and the UPF in terms of the following performance characteristics: + +- 1) Resource Type (GBR, Delay critical GBR or Non-GBR): determines if dedicated network resources related to a QoS Flow-level Guaranteed Flow Bit Rate (GFBR) value are permanently allocated (e.g. by an admission control function in a radio base station). +- 2) Priority level; indicates a priority in scheduling resources among QoS Flows. +- 3) Packet Delay Budget; defines an upper bound for the time that a packet may be delayed between the UE and the UPF that terminates the N6 interface. In uncongested scenarios, 98 percent of the packets are expected to be within the packet delay budget. + +- 4) Packet Error Rate: The Packet Error Rate (PER) defines an upper bound for the rate of PDUs (e.g. IP packets) that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). +- 5) Averaging window (for GBR and Delay-critical GBR resource type only): The Averaging window represents the duration over which the GFBR and MFBR are calculated. +- 6) Maximum Data Burst Volume (for Delay-critical GBR resource type only): denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB. + +Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value. Signalled 5G QoS characteristics are provided as part of the QoS profile and include all of the characteristics listed above. + +### 8.1.4 Standardized 5QI to QoS characteristics mapping + +The one-to-one mapping of standardized 5QI values to 5G QoS characteristics is specified in table 5.7.4-1 of TS 23.501 [10] and shown below in Table 8.1.4-1. + +**Table 8.1.4-1: Standardized 5QI to QoS characteristics mapping +(identical to Table 5.7.4.1-1 in TS 23.501 [10])** + +| 5QI Value | Resource Type | Default Priority Level | Packet Delay Budget | Packet Error Rate | Default Maximum Data Burst Volume (NOTE 2) | Default Averaging Window | Example Services | +|-----------|--------------------|------------------------|---------------------|-------------------|--------------------------------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------| +| 1 | GBR (NOTE 1) | 20 | 100 ms | $10^{-2}$ | N/A | 2000 ms | Conversational Voice | +| 2 | | 40 | 150 ms | $10^{-3}$ | N/A | 2000 ms | Conversational Video (Live Streaming) | +| 3 | | 30 | 50 ms | $10^{-3}$ | N/A | 2000 ms | Real Time Gaming, V2X messages
Electricity distribution - medium voltage, Process automation - monitoring | +| 4 | | 50 | 300 ms | $10^{-6}$ | N/A | 2000 ms | Non-Conversational Video (Buffered Streaming) | +| 65 | | 7 | 75 ms | $10^{-2}$ | N/A | 2000 ms | Mission Critical user plane Push To Talk voice (e.g., MCPTT) | +| 66 | | 20 | 100 ms | $10^{-2}$ | N/A | 2000 ms | Non-Mission-Critical user plane Push To Talk voice | +| 67 | | 15 | 100 ms | $10^{-3}$ | N/A | 2000 ms | Mission Critical Video user plane | +| 75 | | 25 | 50 ms | $10^{-2}$ | N/A | 2000 ms | V2X messages | +| 5 | Non-GBR (NOTE 1) | 10 | 100 ms | $10^{-6}$ | N/A | N/A | IMS Signalling | +| 6 | | 60 | 300 ms | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | +| 7 | | 70 | 100 ms | $10^{-3}$ | N/A | N/A | Voice, Video (Live Streaming)
Interactive Gaming | +| 8 | | 80 | 300 ms | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | +| 9 | | 90 | | | | | | +| 69 | | 5 | 60 ms | $10^{-6}$ | N/A | N/A | Mission Critical delay sensitive signalling (e.g., MC-PTT signalling) | +| 70 | | 55 | 200 ms | $10^{-6}$ | N/A | N/A | Mission Critical Data (e.g. example services are the same as QCI 6/8/9) | +| 79 | | 65 | 50 ms | $10^{-2}$ | N/A | N/A | V2X messages | +| 80 | | 68 | 10 ms | $10^{-6}$ | N/A | N/A | Low Latency eMBB applications Augmented Reality | +| 82 | Delay Critical GBR | 19 | 10 ms (NOTE 4) | $10^{-4}$ | 255 bytes | 2000 ms | Discrete Automation (see TS 22.261 [2]) | +| 83 | | 22 | 10 ms (NOTE 4) | $10^{-4}$ | 1358 bytes (NOTE 3) | 2000 ms | Discrete Automation (see TS 22.261 [2]) | +| 84 | | 24 | 30 ms (NOTE 6) | $10^{-5}$ | 1354 bytes | 2000 ms | Intelligent transport systems (see | + +| | | | | | | | | +|----|--|----|------------------|-----------|-----------|---------|------------------------------------------------------------------| +| | | | | | | | TS 22.261 [2]) | +| 85 | | 21 | 5 ms
(NOTE 5) | $10^{-5}$ | 255 bytes | 2000 ms | Electricity Distribution-
high voltage (see
TS 22.261 [2]) | + +NOTE 1: A packet which is delayed more than PDB is not counted as lost, thus not included in the PER. +NOTE 2: It is required that default MDBV is supported by a PLMN supporting the related 5QIs. +NOTE 3: This MDBV value is set to 1354 bytes to avoid IP fragmentation for the IPv6 based, IPSec protected GTP tunnel to the 5G-AN node (the value is calculated as in Annex C of TS 23.060 [56] and further reduced by 4 bytes to allow for the usage of a GTP-U extension header). +NOTE 4: A delay of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. +NOTE 5: A delay of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. +NOTE 6: A delay of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. + +### 8.1.5 Considerations for Media Services + +#### 8.1.5.1 General + +For media traffic considered in the present document, it is appropriate to understand, how they map to QoS parameters and characteristics, including the mapping to the 5QIs as indicated above. + +#### 8.1.5.2 Expected TCP/IP Performance for non-GBR + +Maximum achievable throughput for a single TCP connection is determined by different factors. One trivial limitation is the maximum bandwidth of the slowest link in the path. But there are also other, less obvious limits for TCP throughput. Packet loss can create a limitation for the connection as well as can the roundtrip time of acknowledgements. + +The TCP Receive Window is the amount of data that a receiver can accept without acknowledging the sender. If the sender has not received acknowledgement for the first packet it sent, it will stop and wait and if this wait exceeds a certain limit, it may even retransmit. This is how TCP achieves reliable data transmission. Even if there is no packet loss in the network, this windowing limits throughput. Because TCP transmits data up to the window size before waiting for the acknowledgements, the full bandwidth of the network may not always get used. At any given time, the window advertised by the receive side of TCP corresponds to the amount of free receive memory it has allocated for this connection. + +When packet loss occurs in the network, an additional limit is imposed on the connection. In the case of light to moderate packet loss when the TCP rate is limited by the congestion avoidance algorithm. + +The *Mathis equation* is a formula that approximates the actual impact of loss on the maximum throughput rate: + +$$\text{Max Rate in bps} < (\text{MSS/RTT}) * (1 / \sqrt{p})$$ + +where + +MSS = maximum segment size in bytes + +RTT = round trip time in seconds + +p = the probability of packet loss + +NOTE: The formula is known as the *Mathis equation* given in [40] from a 1997 paper titled [The Macroscopic Behavior of the TCP Congestion Avoidance Algorithm](#) [40]. + +While this equation obviously has limits in the details, it provides an excellent estimate on the estimated TCP throughput. Figure 8.1.5-1 shows the estimated TCP Throughput over One Way Latency for different packet loss rates and MSS 1500 bytes based on this equation, assuming that the RTT is twice the one way latency. + +![Figure 8.1.5-1: Estimated TCP Throughput over One-Way Latency. A log-log plot showing Estimated Throughput in kbit/s (Y-axis, 1 to 100,000,000) versus One-Way Latency in ms (X-axis, 5 to 500). Ten curves represent different packet loss rates: 1,00E-01 (blue), 1,00E-02 (orange), 1,00E-03 (grey), 1,00E-04 (yellow), 1,00E-05 (light blue), 1,00E-06 (green), 1,00E-07 (dark blue), 1,00E-08 (brown), 1,00E-09 (dark grey), and 1,00E-10 (gold). Throughput decreases as latency increases and as packet loss rate increases.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +Figure 8.1.5-1: Estimated TCP Throughput over One-Way Latency. A log-log plot showing Estimated Throughput in kbit/s (Y-axis, 1 to 100,000,000) versus One-Way Latency in ms (X-axis, 5 to 500). Ten curves represent different packet loss rates: 1,00E-01 (blue), 1,00E-02 (orange), 1,00E-03 (grey), 1,00E-04 (yellow), 1,00E-05 (light blue), 1,00E-06 (green), 1,00E-07 (dark blue), 1,00E-08 (brown), 1,00E-09 (dark grey), and 1,00E-10 (gold). Throughput decreases as latency increases and as packet loss rate increases. + +**Figure 8.1.5-1: Estimated TCP Throughput over One-Way Latency for different packet loss rates and MSS 1500 bytes** + +Based on this equation, the estimated TCP throughput for some relevant streaming related Non-GBR 5QIs as documented in Table 8.1.4-1 are as follows: + +- 5QI = 7 with Latency=100ms and Packet loss rate 10e-3 results in estimated TCP Throughput of 237 kbit/s +- 5QI = 8 and 9 with Latency=300ms and Packet loss rate 10e-6 results in estimated TCP Throughput of 2.5 Mbit/s +- 5QI = 7 with Latency=10ms and Packet loss rate 10e-6 results in estimated TCP Throughput of 75 Mbit/s + +The equation shows that typically TCP based streaming traffic is more susceptible to loss rates than to delay. It is also important that packet loss rates and latencies are not guaranteed and may therefore result in lower or higher throughput, for example in case of congestion or cell handoff. Hence, media services using these 5QI assignments preferably apply protocols that enable to adapt to these bitrates and changes. + +#### 8.1.5.3 Bitrate considerations for GBR services + +If the service would be able to benefit from GBR QoS, then the GFBR and MFBR are relevant. A suitable characterization for a media service is the required minimum bitrate that it needs in order to maintain a good service quality. At the same time, a service is well characterized up to which bitrate it would still provide noticeable quality improvements. Such information may be static or may even change over time, depending on the complexity of the service. + +#### 8.1.5.4 Relevant Parameters for Media Services + +Based on this discussion, it is proposed that for Media services that use TCP-based distribution systems and permit rate adaptation (such as adaptive streaming services), the following information is worthwhile to be provided: + +- The typical bitrate at which the service preferable operates, possibly providing a range of the bitrate. It should also be mentioned if such information is static over the service or would change, and if such information may be configurable. +- If there exists a minimum bitrate that the service should not fall below to maintain a sufficient quality. If this exists, a range would be preferable. It should also be mentioned if such information is static over the service or would change, and if such information may be configurable. +- If there exists a maximum bitrate that the service beyond which the services does not create additional quality. If this exists, a range would be preferable. It should also be mentioned if such information is static over the service or would change, and if such information may be configurable. + +# Annex A: Background information on cloud gaming + +Interactive online game applications require connectivity between the game application client and a game application server. The game application client typically runs on a UE or on a device attached to a UE. The type of traffic generated depends on the type of game. The Quality of Experience is influenced by the adequacy of the QoS of the connectivity and the traffic requirements from the game application. + +For example, Ref. [23] provides delay thresholds per game type in table A-1: + +**Table A-1: Delay tolerance in traditional gaming (from [23]).** + +| Example game type | Perspective | Delay threshold | +|----------------------------|--------------|-----------------| +| First person shooter (FPS) | First person | 100 ms | +| Role playing game (RPG) | Third person | 500 ms | +| Real-time strategy (RTS) | Omnipresent | 1000 ms | + +NOTE: The delay tolerance figures of Table A-1. are applicable to regular 2D games and do not take into account any motion-to-photon requirements of VR gaming applications. + +Cloud gaming implies that, while the game is being played by a user on a client, game application processing and rendering is totally or partly performed in a remote network entity, potentially at the edge of the network. The rendered 2D or VR360 video is then encoded and streamed to the client. These extra steps in game workflow influence the overall interactive delay and audio/video quality (e.g. encoding type/profile/level and performances, resolution and frame rate), and hence influence the Quality of Experience. + +There is work in ITU-T Study Group 12 regarding assessment of gaming quality. Two recommendations are published: + +- ITU-T G.1032 "Influence factors on gaming quality of experience" () [38] +- ITU-T P.809 "Subjective evaluation methods for gaming quality" (). [39] + +This last recommendation could be used to produce comparable subjective evaluations of the influence of connectivity characteristics over QoE. + +Clause 5.3.1 of [22] discusses cloud gaming requirements. It states that "Taking out the delay for rendering and encoding/decoding processing, the round-trip time (RTT) delay over 5GS should be less than 5 ms". + +Cloud gaming services already exist, and new ones are being launched, enabling users to play any type of game (whether it is originally offline or online, single player or multiplayer etc.) on a device like a lite smartphone, tablet or TV which would typically be unable to process such a game. The following is a brief look at several of these services and the public information about their requirements. + +Cloud gaming typical traffic characteristics are evolving as services are being deployed. But a tendency can be derived from the data available. Bitrates in the range of 5-35Mbps are expected. Although latency requirements vary from game types and users, cloud gaming services are expected to offer a Quality of Experience which is at least as good as the experience of regular (locally processed) gaming. + +# Annex B: Change history + +| Change history | | | | | | | | +|----------------|------------------------------------------|-----------|----------|-----|-----|---------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-12 | SA#86 | SP-190993 | | | | Provided to TSG SA#86 (for information) | 1.0.0 | +| 2020-01 | MBS SWG
Ad hoc
telco
31/01/2020 | S4-AHI928 | | | | Editor's compilation of S4-200037, S4-200319, S4-200011, S4-200067 in S4-AHI927 and online edits during call. | 1.1.0 | +| 2020-03 | SA#87-e | SP-200048 | | | | Provided to TSG SA#87-e (for approval) | 2.0.0 | +| 2020-03 | SA#87-e | SP-200048 | | | | Approved by TSG SA#87-e | 16.0.0 | +| 2021-09 | SA#93-e | SP-210820 | 000
1 | 01 | B | Typical Traffic Characteristics | 17.0.0 | +| 2022-03 | SA#95-e | SP-220032 | 000
2 | | B | 8K TV Traffic Characteristics | 17.1.0 | +| 2023-09 | SA#101 | SP-230922 | 000
3 | 4 | B | XR Traffic Characteristics | 18.0.0 | +| 2023-12 | SA#102 | SP-231372 | 000
4 | | B | [FS_XRTraffic] Application Layer FEC Traffic characteristics | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/26_series/26941/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-18/26_series/26941/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21299ec575f44995a5f82e4ae93f5ede1ed98824 --- /dev/null +++ b/marked/Rel-18/26_series/26941/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee3de39a19bfb64c8bf96c81a7804b6bab8ec3451cb76fb9ec5d1bb4bc7be002 +size 45225 diff --git a/marked/Rel-18/26_series/26941/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-18/26_series/26941/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73c802a58347aa3c7a2698bf45bc566460f57c87 --- /dev/null +++ b/marked/Rel-18/26_series/26941/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f74833eb2fd726b30f05552a5063b28e5f9f70f568f2dee7ac3a61460d2c39b +size 118462 diff --git a/marked/Rel-18/26_series/26941/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-18/26_series/26941/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..180458957e3bf0e24ef799ce7e4beece39308ff8 --- /dev/null +++ b/marked/Rel-18/26_series/26941/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5c781e2d11d13bd43b5a15fd3ccb9e0a7703d6b23e51b0878ab100e06152288 +size 57857 diff --git a/marked/Rel-18/26_series/26941/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-18/26_series/26941/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9aead9ee6e8202f7eee05ff982be30f59bb3f507 --- /dev/null +++ b/marked/Rel-18/26_series/26941/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4006709d81682fcfcb54bee4dbdc56d45073059c7f4516b027e7119bc246808 +size 121002 diff --git a/marked/Rel-18/26_series/26941/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/26_series/26941/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2556a5af8d22cfba6eae3bf9ee5b14007d9e3557 --- /dev/null +++ b/marked/Rel-18/26_series/26941/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43e91abc05ce9e5bcb2d649fb377eaea781491f420baa4c533a109da47f0b2a0 +size 9389 diff --git a/marked/Rel-18/26_series/26941/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/26_series/26941/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58aa5b9751525efd275bba6f5d4d22463a958b8a --- /dev/null +++ b/marked/Rel-18/26_series/26941/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:737ed5aa4e5b33d4b03109018320f50ef7600cdb59a419f079aa489955d71163 +size 5726 diff --git a/marked/Rel-18/26_series/26941/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-18/26_series/26941/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4931578f8dbe7b8dfa7442b2eaa7fceb34122ebc --- /dev/null +++ b/marked/Rel-18/26_series/26941/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2702e97e885c39947bc4a7136a6954a0ee425cc86bd92290ed77d47f6468331a +size 62831 diff --git a/marked/Rel-18/26_series/26941/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-18/26_series/26941/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d8c00cf443dbe3afb1cd561dcf74780eb91cc2e --- /dev/null +++ b/marked/Rel-18/26_series/26941/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a0f127270a2fcd6ee316171ef3389d42e742befc2da099adc53bd210171510d +size 65901 diff --git a/marked/Rel-18/26_series/26941/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-18/26_series/26941/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03b1b1079156fc3f4a29513fa8c778d4ec84af89 --- /dev/null +++ b/marked/Rel-18/26_series/26941/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:139f67aea044a141da631f9468742633dc5d79d18e56a81dfa2fd2792c1e26ae +size 65414 diff --git a/marked/Rel-18/26_series/26941/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg b/marked/Rel-18/26_series/26941/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8e3a4f829c8a9acbaf17143e95960887c7d7076 --- /dev/null +++ b/marked/Rel-18/26_series/26941/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b21991799f38aa35584915fb2333c09b1d38a9ceeeade959db34402caeee122c +size 46990 diff --git a/marked/Rel-18/26_series/26941/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-18/26_series/26941/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b437919558b9804af441395c7d18c788cca692 --- /dev/null +++ b/marked/Rel-18/26_series/26941/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22cc47172219c874c3c67ffdcdb7e9c5503afe3e06725d5930950adfd0d926e7 +size 95974 diff --git a/marked/Rel-18/26_series/26941/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-18/26_series/26941/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa2e255bc6eeb0b34a1a574fc36e6ae2e9e92da1 --- /dev/null +++ b/marked/Rel-18/26_series/26941/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ded330c45ddf8c8743e5f80dc4d035b77157dbdd75b1d461e342ced262c6d735 +size 94989 diff --git a/marked/Rel-18/26_series/26941/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/Rel-18/26_series/26941/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc54d0f46ed430f241722f84d8399544ad5439c2 --- /dev/null +++ b/marked/Rel-18/26_series/26941/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f8ea79ecfa3294029c0e14a1826fd468db38b721004db2369c5087859c0521b +size 71409 diff --git a/marked/Rel-18/26_series/26941/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-18/26_series/26941/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7277a0cfc270f476f914336fee7e9907f63ba272 --- /dev/null +++ b/marked/Rel-18/26_series/26941/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2a212776dbc87bfe0698f4e1548c143b8c85e61f154525a6567e579625dfda4 +size 101370 diff --git a/marked/Rel-18/26_series/26941/raw.md b/marked/Rel-18/26_series/26941/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..355cf84bf439693c745232e89ecb1da4bf9ad3cf --- /dev/null +++ b/marked/Rel-18/26_series/26941/raw.md @@ -0,0 +1,1146 @@ + + +# 3GPP TR 26.941 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Network Slicing Extensions for 5G media services; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in small capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in small, spaced-out capital letters. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Overview..... | 10 | +| 4.0 Assumptions..... | 10 | +| 4.1 General ..... | 10 | +| 4.2 Network slicing architecture ..... | 10 | +| 4.2.1 General ..... | 10 | +| 4.2.2 Network slicing for specific applications ..... | 11 | +| 4.2.3 Service continuity for media streaming sessions migrated between Network Slices..... | 13 | +| 4.2.3.1 Background..... | 13 | +| 4.2.3.2 Moving application flows to different Network Slices..... | 13 | +| 4.3 Slice orchestration and management..... | 13 | +| 4.4 Network slice capability exposure ..... | 14 | +| 5 Relevant scenarios and use cases ..... | 15 | +| 5.1 General ..... | 15 | +| 5.2 Types of network slicing..... | 15 | +| 5.2.1 Scenario 1: Operator-managed network slicing ..... | 15 | +| 5.2.2 Scenario 2: Third-party-managed network slicing..... | 15 | +| 5.3 Use cases ..... | 16 | +| 5.3.1 Multiple network slices for uplink and downlink streaming..... | 16 | +| 5.3.2 Premium gaming slice ..... | 17 | +| 5.4 Collaboration scenarios for network slicing..... | 17 | +| 5.4.0 General ..... | 17 | +| 5.4.0.1 Scenarios based on network slicing architecture ..... | 17 | +| 5.4.0.2 Network slicing scenarios..... | 17 | +| 5.4.1 Collaboration scenarios for network slicing based on downlink media streaming scenarios ..... | 19 | +| 5.4.1.1 Downlink media streaming with both AF and AS deployed in the trusted Data Network..... | 19 | +| 5.4.1.2 Downlink media streaming with both AF and AS deployed in an external Data Network (OTT) ..... | 19 | +| 5.4.1.3 Downlink media streaming with AFs deployed in two separate trusted Data Networks sharing AS in an external Data Network..... | 20 | +| 5.4.2 Collaboration scenarios for network slicing with multiple slices or Data Networks ..... | 21 | +| 5.4.2.1 Downlink media streaming with AS deployed in external Data Network and AS delivering content through two different network slices ..... | 21 | +| 5.4.2.2 Downlink media streaming with AS deployed in multiple trusted Data Networks..... | 22 | +| 5.4.3 Collaboration options based on network slicing scenarios..... | 23 | +| 5.4.3.0 General ..... | 23 | +| 5.4.3.1 Scenario #1: Slice serving a set of enterprise services/applications ..... | 23 | +| 5.4.3.2 Scenario #2: Slice serving a specific application of an enterprise..... | 25 | +| 5.4.3.3 Scenario #3: Slice optimized for a specific service/application ..... | 25 | +| 5.4.3.4 Scenario #4: Slice serving a virtual operator ..... | 26 | +| 6 Key issues and candidate solutions..... | 27 | +| 6.1 Key Issue #1: Service Provisioning ..... | 27 | +| 6.1.1 Description ..... | 27 | +| 6.1.1.1 Provisioning multiple Network Slices for media streaming..... | 27 | +| 6.1.2 Candidate solutions ..... | 27 | +| 6.1.2.1 Candidate solution #1: Policy template provisioning for a plurality of Network Slices and/or DNNs ..... | 27 | + +| | | | +|---------------------------------------------------|-----------------------------------------------------------------------------------|-----------| +| 6.1.3 | Conclusions ..... | 29 | +| 6.2 | Key Issue #2: Realising dynamic policies using different slices ..... | 29 | +| 6.2.1 | Description ..... | 29 | +| 6.2.1.1 | Slice selection for M5 dynamic policy requests ..... | 29 | +| 6.2.2 | Candidate solutions ..... | 29 | +| 6.2.2.1 | Candidate solution #1 ..... | 29 | +| 6.2.3 | Conclusions ..... | 29 | +| 6.3 | Key Issue #3: Moving media flows to other Network Slices..... | 29 | +| 6.3.1 | Description ..... | 29 | +| 6.3.1.1 | Migration of media streaming application flows between Network Slices ..... | 29 | +| 6.3.2 | Candidate solutions ..... | 30 | +| 6.3.2.1 | Candidate solution #1 ..... | 30 | +| 6.3.3 | Conclusions ..... | 30 | +| 6.4 | Key Issue #4: AF discovery for dynamic policy..... | 30 | +| 6.4.1 | Description ..... | 30 | +| 6.4.1.1 | Discovery of 5GMS AF instance for dynamic policy ..... | 30 | +| 6.4.2 | Candidate solutions ..... | 30 | +| 6.4.2.1 | Candidate solution #1 ..... | 30 | +| 6.4.3 | Conclusions ..... | 30 | +| 6.5 | Key Issue #5: Interoperability considerations..... | 30 | +| 6.5.1 | Description ..... | 30 | +| 6.5.1.1 | Communication between AF instances to support interoperability ..... | 30 | +| 6.5.2 | Candidate solutions ..... | 31 | +| 6.5.2.1 | Candidate solution #1 ..... | 31 | +| 6.5.3 | Conclusions ..... | 31 | +| 6.6 | Key Issue #6: Slice resource resolution ..... | 31 | +| 6.6.1 | Description ..... | 31 | +| 6.6.1.1 | Resolve slice-specific application instances ..... | 31 | +| 6.6.2 | Candidate solutions ..... | 31 | +| 6.6.2.1 | Candidate solution #1 ..... | 31 | +| 6.6.3 | Conclusions ..... | 31 | +| 6.7 | Key Issue #7: Bootstrapping application invocation on Network Slice..... | 31 | +| 6.7.1 | Description ..... | 31 | +| 6.7.1.1 | Discover appropriate Network Slice for 5GMS procedures ..... | 31 | +| 6.7.2 | Candidate solutions ..... | 32 | +| 6.7.2.1 | Candidate solution #1: Bootstrapping based on Traffic Descriptor information..... | 32 | +| 6.7.3 | Conclusions ..... | 33 | +| 7 | Potential requirements..... | 33 | +| 8 | Conclusions and recommendations..... | 33 | +| Annex A (informative): Change history..... | | 35 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +This document covers key issues, candidate solutions and potential requirements for supporting network slicing with 5GMS architecture. Aspects related to provisioning of media services, dynamic policy, and resolution of slice-specific AS instances while using network slicing for media streaming use cases are covered in this document. + +# --- 1 Scope + +The present document identifies standardization needs and potential standards gaps relevant to media streaming while using 5G network slicing. In specific, the following aspects are addressed in this document: + +- To identify relevant use cases that can be addressed using network slicing, and study collaboration scenarios and deployment architectures to support network slicing for media services. +- To identify any missing provisioning aspects for configuring media services with one or more network slices including QoS configuration, reporting and dynamic policy. +- To identify impact of network slicing on dynamic policy invocation APIs, including selection of appropriate network slices for dynamic policy requests, possible migration of UE application traffic flows between network slices due to dynamic policy procedures, discovery of dynamic policy AF, and necessary routing considerations. +- To determine the need and describe methods for AF-to-AF communication to support interoperability if 5GMS AF instances from different vendors are deployed in the same 5GMS System. +- To identify methods for deploying, supporting, and resolving slice-specific 5GMS AS instances. +- To identify potential areas for normative work and communicate/align with SA2 as well as other potential 3GPP WGs (SA5, SA6) on relevant aspects related to the study. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 26.804: "Study on 5G media streaming extensions". +- [3] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements". +- [4] 3GPP TS 28.531: "Management and orchestration; Provisioning". +- [5] GSM Association NG.116, "Generic Network Slice Template", +- [6] 3GPP TR 23.700-40: "Study on enhancement of network slicing; Phase 2". +- [7] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". +- [8] 3GPP TS 23.700-99: "Study in Network slice capability exposure for application layer enablement (NSCALE)". +- [9] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service". +- [10] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3". + +- [11] 3GPP TS 28.542: "Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 1". +- [12] 3GPP TS 28.532: "Management and orchestration; Generic management services". +- [13] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS)". +- [14] 3GPP TS 28.546: "Management and orchestration of networks and network slicing; Fault Supervision (FS); Stage 2 and stage 3". +- [15] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". +- [16] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [17] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [18] 3GPP TS 27.007: "AT command set for User Equipment (UE)". +- [19] 3GPP TS 29.520: "5G System; Network Data Analytics Services; Stage 3". +- [20] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture". +- [21] 3GPP TS 26.512: "5G Media Streaming (5GMS); Protocols". +- [22] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". +- [23] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)". +- [24] 3GPP TS 23.558: "Architecture for enabling Edge Applications". +- [25] 3GPP TR 28.809: "Study on enhancement of management data analytics". +- [26] 3GPP TR 23.700-41: "Enhancement of Network Slicing Phase 3". +- [27] 3GPP TS 22.261: "Service requirements for the 5G system". +- [28] 5G Media Slice Definition, version 1.2: Joint outcome between New European Media and Networld2020 technology platforms, [https://5genesis.eu/wp-content/uploads/2019/10/NEM\\_Networld2020-5GPPP-5G-Media-Slice-White-Paper-V1.pdf](https://5genesis.eu/wp-content/uploads/2019/10/NEM_Networld2020-5GPPP-5G-Media-Slice-White-Paper-V1.pdf). +- [29] Commercializing 5G Network Slicing, 5G Americas White Paper: , July 2022. +- [30] Network Slicing, Technical White Paper: [https://images.samsung.com/is/content/samsung/p5/global/business/networks/insights/white-paper/network-slicing/200420\\_Samsung\\_Network\\_Slicing\\_Final.pdf](https://images.samsung.com/is/content/samsung/p5/global/business/networks/insights/white-paper/network-slicing/200420_Samsung_Network_Slicing_Final.pdf), April 2020 +- [31] FCC Technological Advisory Council, 5G IOT Working Group: "5G Network Slicing Whitepaper", . +- [32] Applied Network Slicing Scenarios in 5G: . +- [33] 5G Network Slicing: How to Secure the Opportunity: . +- [34] Navigate the network slicing transformation journey: . +- [35] GSM Association: "5G Network Slicing", [https://www.gsma.com/futurenetworks/ip\\_services/understanding-5g/network-slicing/](https://www.gsma.com/futurenetworks/ip_services/understanding-5g/network-slicing/). + +- [36] Jose Ordonez-Lucena, Pablo Ameigeiras, Luis M. Contreras, Jesús Folgueira and Diego R. López: "On the Rollout of Network Slicing in Carrier Networks: A Technology Radar", National Library of Medicine, Sensors, , December 2021. +- [37] Network Slicing using User Equipment Route Selection Policy (URSP): , November 2021. +- [38] 5G Network Slicing: Android documentation, . +- [39] Apple device support for private 5G and LTE networks: . +- [40] GSM Association: "Network Slicing: North America's Perspective (Current) Version 1.0", , August 2021. +- [41] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [42] 3GPP TS 26.510: "Media delivery; interactions and APIs for provisioning and media session handling". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-------|---------------------------------------------| +| ANDSP | Access Network Discovery & Selection Policy | +| CSC | Communication Service Customer | +| CSP | Communication Service Provider | +| DN | Data Network | +| DNN | Data Network Name | +| ECS | Edge Configuration Server | +| EEC | Edge Enabler Client | +| eMBB | Enhanced Mobile Broadband | +| EPC | Evolved Packet Core | +| GST | Generic Network Slice Template | +| MIoT | Massive Internet of Things | +| MPS | Multimedia Priority Service | +| MNO | Mobile Network Operator | +| MVNO | Mobile Virtual Network Operator | +| NEST | Network Slice Type | +| NOP | Network Operator | + +| | | +|--------|-------------------------------------| +| NRM | Network Resource Model | +| NSaaS | Network Slice as a Service | +| NSC | Network Slice Customer | +| NSCE | Network Slice Capability Enablement | +| NSI | Network Slice Instance | +| NSP | Network Slice Provider | +| NSSI | Network Slice Subnet Instance | +| NSSP | Network Slice Selection Policy | +| NWDAF | Network Data Analytics Function | +| PDU | Protocol Data Unit | +| ProSe | Proximity based Services | +| ProSeP | ProSe Policy | +| URSP | UE Route Selection Policy | +| V2X | Vehicle-to-Everything | +| V2XP | V2X Policy | + +# 4 Overview + +## 4.0 Assumptions + +The following assumptions apply to the present document: + +1. Possible and efficient solutions based on network slicing are sought to support the use cases listed in clause 5 and many others that also require differentiated QoS for their application streams. Network slicing may not be the only solution to support these use cases, but is one possible solution. +2. Service requirements relating to network slicing specified in TS 22.261 [27] and TR 23700-99 [8] are considered for studying possible issues in relation to 5G Media Streaming. + +## 4.1 General + +Clause 5.12 of TR 26.804 [2] provides a brief overview of network slicing feature standardization in different 3GPP groups, areas of study related to 5G Media Streaming for specifying network slicing extensions, and potential open issues. This clause describes different slice management processes in a little more detail that are relevant for specifying the media streaming aspects of network slicing. + +## 4.2 Network slicing architecture + +### 4.2.1 General + +A Network Slice is a logical network with specific capabilities and characteristics as defined in clause 3.1 of TS 23.501 [7]. According to the supported features, functionalities and different groups of UEs, the multiple Network Slices can be deployed by the operator. More specifically, the network slice can support different functionality (e.g., priority, policy control), different performance requirements (e.g., latency, data rates), or different targeted users (e.g., MPS users, Public Safety users, corporate customers, roamers, or MVNO hosting users). For example, based on the operator's needs, there can be one network slice for MIoT services, one for supporting eMBB UEs and another one for V2X services. + +A Network Slice instance is a set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice. A slice instance includes both core network control plane and user plane network functions as defined in clause 4.15.1 of [7]. + +A UE can access multiple Network Slices simultaneously. Figure 4.2.1-1 below shows some illustrative scenarios. The occurrence of PDU Session Establishment in a Network Slice instance to a DN allows data transmission in that Network Slice instance. + +NOTE: In the context of 5G Media Streaming, PDU Sessions of type IPv4 or IPv6 are the primary focus. + +The Network Slice Selection policies in the UE are used to associate an application with a specific network slice during PDU Session Establishment. A PDU Session belongs to one and only one specific Network Slice instance per PLMN. Therefore, different Network Slice instances do not share a PDU Session. But multiple PDU Sessions in different Network Slice instances may be associated with the same Data Network, identified by the same DNN. + +![Figure 4.2.1-1: Mapping of PDU Sessions to Data Network Names and Network Slice instances. The diagram consists of two parts, (a) and (b), showing different UPF instance configurations for network slices.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates two scenarios for mapping PDU Sessions to Data Network Names (DNNs) and Network Slice instances. + +**(a) UPF instance shared by slice instances** + +In this scenario, a single UPF instance is shared by two network slice instances, Network Slice instance X and Network Slice instance Y. The UE contains URSP Rules. PDU Session #1 (blue) is associated with DNNA and connects to DNA. PDU Session #2 (yellow) is associated with DNNB and connects to DNB. PDU Session #3 (yellow) is also associated with DNNB and connects to DNB. All three PDU sessions are managed by the same UPF instance. + +**(b) UPF instance per slice instance** + +In this scenario, each network slice instance has its own UPF instance. Network Slice instance X includes UPFX and manages PDU Session #1 (blue, DNNA to DNA) and PDU Session #2 (yellow, DNNB to DNB). Network Slice instance Y includes UPFY and manages PDU Session #3 (yellow, DNNB to DNB). The UE contains URSP Rules. + +Figure 4.2.1-1: Mapping of PDU Sessions to Data Network Names and Network Slice instances. The diagram consists of two parts, (a) and (b), showing different UPF instance configurations for network slices. + +**Figure 4.2.1-1: Mapping of PDU Sessions to Data Network Names and Network Slice instances** + +In addition, enhancements to interworking between the EPC and the 5GC have been made to the 5G System, and network slice-specific authentication and authorization are also supported. For each network slice that is subject to Network Slice Admission Control, the monitoring and control of the number of registered UEs, the number of PDU Sessions and the slice-maximum bit rate are defined in order to ensure that the maximum resource of the network slice is not exceeded. + +### 4.2.2 Network slicing for specific applications + +Before application services are allowed to access specific network slices, a third-party Application Service Provider can negotiate with the MNO and the MNO may create or allocate the network slices based on the service requirements. For example, a cloud gaming service provider may interact with the MNO to reserve specific network slices supporting low latency, and high computing resources. + +Afterwards, the Application Function, on behalf of the Application Service Provider, informs the 5GC that the target application service can use the specific network slices, i.e., by providing application guidance for UE Route Selection Policy (URSP) determination as defined in clause 4.15.6.10 of TS 23.502 [15]. Depending on the nature of the application guidance, the operator may update the Network Slice Selection policies in the URSP accordingly. As a consequence, the application service may be migrated to the new network slice/DNN duple based on the updated URSP rule. + +The URSP rules in the UE, which are used to associate applications with usage of particular network slices, may be pre-configured or provided by the PCF as defined in TS 23.503 [16]. Each URSP rule is expressed as a traffic descriptor for application detection, e.g. IP descriptors, application descriptors, domain descriptors. + +NOTE: There is no restriction on which part of UE should (re-)evaluate the URSP rules. This may be done by either the Operating System or the modem layer. + +Once an application is started or detected on the UE, the following procedure is followed: + +1. The UE evaluates its URSP rules in the order of Rule Precedence and determines whether the application matches the Traffic descriptor of any URSP rule. + - a. When a URSP rule is determined to be applicable for a given application, the UE derives the suitable network slices based on the applicable URSP rule. + - b. If the UE determines that there is more than one existing PDU Session which matches a given URSP rule, it is up to UE implementation (Operating System or modem layer) to select one of them to use. Otherwise, the UE tries to establish a new PDU Session using the derived network slices. +2. If there is no matching URSP rule (except the “match all” rule), the UE uses its own local configuration (if any) to determine which PDU Session to use. + +NOTE: The UE local configuration in this context is information about the associated application, such as application-specific parameters to set up a PDU Session or end user configuration for specific applications. This can be provisioned in the UE via the application layer, e.g. following interaction between the Edge Enabler Client (EEC) and the Edge Configuration Server (ECS), as defined in TS 23.558 [24]. + +3. When URSP rules are updated, or when a particular URSP rule's validity changes, the association of existing applications to PDU Sessions may need to be re-evaluated. +4. Depending on UE implementation, the associations between applications and PDU Sessions may also be re-evaluated periodically, independent of any changes to URSP rules. + +In the case where a network slice becomes unavailable (e.g. due to overload), the AMF is triggered, either by local configuration (e.g. trigger from OAM) or by a notification from the Access and Mobility Management PCF (AM PCF) or by the NSSF [26], to replace the current S-NSSAI with a previously chosen Alternative S-NSSAI. Using a suitable NAS procedure (e.g. UE Configuration Update) the AMF informs the UE about the Alternative S-NSSAI as well as providing the mapping between S-NSSAI(s) and Alternative S-NSSAI(s) in the Allowed NSSAI and/or in the Configured NSSAI. + +1. In the case where there is no existing PDU Session in the unavailable slice and the UE is trying to establish a new one to support a 5G Media Streaming session, the UE may provide both the Alternative S-NSSAI and the current S-NSSAI in the PDU Session Establishment message, in which case the AMF provides both S-NSSAI values to the SMF for the PDU Session establishment. The SMF proceeds with the PDU Session Establishment using the Alternative S-NSSAI. As a result, the new PDU Session is established over the Alternative S-NSSAI with a new IP address. +2. In the case where an ongoing 5G Media Streaming session is already being carried over the PDU Session associated with the unavailable slice, the AMF informs the SMF responsible for the PDU Session that it is to be transferred to the Alternative S-NSSAI. Then, depending on the Session and Service Continuity (SSC) mode of the existing PDU Session, either: + - *SSC mode 1*: The SMF further updates the network slices in the UE/RAN/UPF via the PDU Session Modification procedure. In this case, the IP address of the PDU Session remains the same. + - *SSC mode 2 or 3*: The SMF triggers the modification/release of the PDU Session and re-establishment of the PDU Session in the Alternative S-NSSAI. In this case, a new IP address is allocated during the PDU Session re-establishment procedure and the ongoing 5G Media Streaming session at reference point M4 and M5 needs to be migrated to the new PDU Session. + +Editor's note: the above descriptions of Network Slice Replacement will be updated to aligned with SA2's conclusion. + +### 4.2.3 Service continuity for media streaming sessions migrated between Network Slices + +#### 4.2.3.1 Background + +TR 28.809 [25] is the result of a feasibility study that looked into aspects of management data analytics. Clause 6 of [25] specifies use cases, potential requirements and possible solutions for management data analytics. One of the issues relating to service-level specifications documented in clause 6.3.2 of [25] is the issue of network slice load analysis, described as follows: + +Network slice load may vary over time. Therefore, network resources allocated initially could not always satisfy the traffic requirements, for example, the network slice may be overloaded or underutilized. Various factors may impact the network slice load, e.g. number of UEs accessing the network, number of PDU sessions, service types and the end users distribution. Overload of signalling in control plane and/or user data congestion in user plane will lead underperforming network. Besides, allocating excessive resources for network slice with light load will decrease resource efficiency. + +From the above, it is understood that a Network Slice can become overloaded from time to time, and that consequently the slice cannot satisfy the traffic requirements, and therefore may fail to meet its SLA. + +Clause 5.1 of TR 23700-41 [26] describes a related key issue "Key Issue#1: Support of Network Slice Service Continuity" in terms similar to the issue described above in [25] above. Specifically, aspects related to service continuity are being studied for two scenarios - a "no mobility" scenario and an "inter-RA mobility" scenario - in the case when a Network Slice or Network Slice instance in the Core Network (CN) or target CN is overloaded or undergoing planned maintenance (e.g., Network Slice termination), and the network performance of the Network Slice cannot meet the SLA. + +As described in clause 4.2.2 of the present document, SA2 is in the process of specifying a method where an alternative slice is identified in advance, with the aim of migrating application traffic from the PDU Session in the current slice to the existing PDU Session or a new one in that alternative slice. + +#### 4.2.3.2 Moving application flows to different Network Slices + +The 5G System provides generic support for moving application flows to different slices. As described in clause 5.15.5.2.2 of TS 23.501 [7] on determining whether ongoing traffic can be routed over existing PDU Sessions in other Network Slices: + +The UE uses either the URSP rules (which includes the NSSP) or the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503 [16] to determine whether ongoing traffic can be routed over existing PDU Sessions belonging to other Network Slices or establish new PDU Session(s) associated with same/other Network Slice. + +From the above, it is clear that either the URSP rules delivered to the UE or the UE local configuration determine how ongoing application traffic can be routed over existing PDU Sessions belonging to other Network Slices. + +Clause 4.2.2 of the present document describes how the URSP rules are used to route application traffic through appropriate network slices. + +For UE Local Configuration, clause 6.1.2.2.1 of [16] describes UE policy control, and specifies that among the four policy objects - Access Network Discovery & Selection Policy (ANDSP), UE Route Selection Policy (URSP), V2X Policy (V2XP), and ProSe Policy (ProSeP) - only ANDSP and URSP may be pre-configured in the UE. + +## 4.3 Slice orchestration and management + +TS 28.530 [3] and TS 28.531 [4] specify general concepts related to network slicing and slice life cycle management including specification of roles related to network slicing such as the CSC, CSP, NOP, NSC, and NSP. A network operator can perform both the roles of a CSP and NSP. A request from a CSC or NSC to the CSP or the NSP respectively for setting up a network slice is in the form of a set of slice attributes that represents the service requirements for the service that the customer intends to provide to its users. + +The GSM Association describes a GST template [5] which specifies a set of attributes that characterize a given type of network slice/service. The slice customer prepares a NEST based on GST attributes and forwards it to the NSP for slice orchestration. A NEST is a GST filled with values. A study on GST attributes is specified in TR 23.700-40 [6], and a reference to GST attributes is included in clause 5.15.2.2 of TS 23.501 [7]. GST attributes and NEST are also discussed in study on network slice capability exposure for application enablement (NSCALE) in TR 23.700-99 [8]. The normative specification for this work is being specified in TS 23.435 [9]. + +GST attributes, as defined in [5], are categorized into two types: + +- *Character attributes*: These attributes typically characterize a slice (e.g., throughput, latency, APIs etc.). The character attributes can be further classified as relating to performance, function, or control and management +- *Scalability attributes*: These attributes provide information about the scalability of a slice (e.g., number of UEs) + +The CSP/NSP translates the NEST to service requirements for a set of subnets (e.g., core, transport network, RAN) using the slice NRM as described in TS 28.530 [3], TS 28.541 [10], TS 28.542 [11]. Based on individual slice subnet requirements, slice subnet resources are provisioned using slice orchestration operations for creating and managing NSI and NSSI resources as defined in TS 28.531 [4]. Such operations include: + +- Creation/modification/termination of NSI instances. +- Creation/modification/termination of NSSI instances. +- Creation/modification/termination of 3GPP NF instances. + +Management and orchestration concepts such as provisioning management services, fault supervision management services, and performance assurance management services in addition to management service specification on the above slice resources are specified in TS 28.532 [12]. TS 28.545 [13] and TS 28.546 [14] describe fault supervision aspects of management and orchestration of networks and network slicing. + +TS 23.501 [7] and TS 23.502 [15] specify control plane architecture and procedures on enabling the connection of the UE to the above provisioned network slices including establishment of PDU sessions through those slices to the intended DNN. TS 23.503 [16] describes the data model for URSP rules and NSSP policies that enable UE application traffic to be routed through the provisioned network slices to the respective DNNs. + +In addition, a study on network slice capability exposure for application layer enablement is described in TR 23.700-99 [8]. The application layer enablement architecture in [8] is based on the Service Enabler Architecture Layer for Verticals (SEAL) whose functional architecture and information flows are specified in TS 23.434 [17]. + +One of the key issues under study in [8] is whether a more concise approach to managing the lifecycle of network slices exposed to the application layer with additional functionality for verticals can be defined. One of the solutions being studied in clause 6.1.1 of [8] is to interface the network slice capability enablement server with the 5G system in order to perform all the network slice lifecycle management operations defined in [3] and [4]. With this capability, applications of different verticals can interface with the network slice capability enablement server for all network slice related operations. + +TS 27.007 [18], in clause 10.1, describes how via AT commands the UE is able to set network slice preferences. + +## 4.4 Network slice capability exposure + +TR 23.700-99 [8] documents several key issues and candidate solutions in addition to enabling network slice lifecycle management operations using the network slice capability enablement server. Some of the key issues relevant to that study are the following: + +- Discovery and registration aspects for management service exposure. +- Network slice fault management capability. +- Communication service management exposure. +- Application layer QoS verification capability enablement. +- Network slice related performance and analytics exposure. +- Network slice capability exposure in the edge data network. + +- Delivery of existing network slice information to the trusted third party. +- Network slice creation to the third party and UE. + +In addition to the above information available at the network slice capability enablement server, TS 29.520 [19] specifies the stage-3 definition of NWDAF Services of the 5G System and provides a data model for network slice information that NWDAF can provide to authorized customers. Such information can also be used as network slice capability information. + +# --- 5 Relevant scenarios and use cases + +## 5.1 General + +## 5.2 Types of network slicing + +### 5.2.1 Scenario 1: Operator-managed network slicing + +In the operator-managed network slice scenario, the operator instantiates, configures, and manages a network slice that can be used by one or more customers (e.g., third-party service providers). A customer intending to provide a service to its users with differentiated quality of service or experience, requests that the operator sets up communication services in a network slice through which its users can access the customer's service. The customer does not have any information about the slice internals, and completely relies on the operator to set up the resources requested by the customer in a network slice and make the service accessible to that customer's users in that slice. + +The customer and the operator negotiate a set of service requirements based on the expectation of the service that the customer intends to provide to its users. One way of negotiating service requirements is the use of GST attributes specified by GSM Association in [5]. Some of the performance-related GST attributes resemble the QoS service requirements specified in TS 26.501 [20] and TS 26.512 [21] as part of the M1d reference point specification. + +NOTE: A detailed mapping between the GST attributes and the QoS attributes specified in [20] and [21] is for future study. + +In this scenario, an Application Service Provider, as a customer of the operator providing a network slice, can negotiate service parameters to be provided in a network slice. Based on the negotiated service requirements, the operator provisions necessary control and management functions to enable the setting up of an end-to-end network slice spanning different slice domains (e.g., RAN, Core, Transport etc.). The operator-provided management functions manage the end-to-end operation of the network slice and guarantee the availability of application functions that are deployed in that slice. TS 28.545 [13], TS 28.546 [14], TS 28.552 [22], TS 28.554 [23] define fault management and performance management capabilities which can be used to measure and assure the health of different slice resources. + +By delegating these functions to the Mobile Network Operator, a media Application Service Provider can focus on media service delivery, using the 5G Media Streaming capabilities defined in TS 26.501 [20] and TS 26.512 [21], by interacting with the application functions provisioned in the network slice. + +### 5.2.2 Scenario 2: Third-party-managed network slicing + +In this scenario, a third-party entity requests that the operator creates a network slice based on certain requirements. The operator creates a network slice and hands over the network slice to the third-party entity. This mode of operation is specified in [3] and is referred to as NSaaS. Once the slice is handed over, the third-party entity can enhance the network slice e.g., by adding custom network functions, modifying slice configuration etc. + +A method for negotiating requirements for NSaaS service is the use of GST attributes specified by the GSM Association [5]. In addition to the performance-related character attributes, a number of scalability-related attributes can be used to describe the requirements of the slice to be provisioned in the 5G System. + +The third-party entity can then provide the network slice resources to its customers. As described in the previous scenario, customers of the third-party entity can then negotiate with the third-party entity to set up communication + +services in that network slice. The users of the customers will then be able to access the customer's service using the provisioned network slice. + +An Application Service Provider can function as the third-party entity in this scenario and can receive a provisioned network slice as a service from the Mobile Network Operator. In this case, the Application Service Provider may, in addition to the capabilities described in [20] and [21], also have additional facilities to control and manage the resources of the network slice. + +NOTE: It is for future study to identify how the capabilities available as a NSaaS consumer specified in [3] benefit an Application Service Provider whose role is specified in [20] and [21]. This scenario is therefore not considered further in the present document. + +Editor's note: [8] and [9] are to be monitored for specification related to the interface capabilities between the third-party entity and the NSCE server for control of network slices. + +## 5.3 Use cases + +### 5.3.1 Multiple network slices for uplink and downlink streaming + +[28] describes a number of media and content use cases that cover most of the common media and content situations from production to consumption. The two technology groups that co-authored [28] (New European Media and Network2020) present nine use cases and have identified twelve parameters to adapt the network to application requirements. The following table lists the nine use cases, along with a mention of those use cases having strict QoS requirements in the uplink and/or downlink direction. + +| Use Case | Uplink Slice | Downlink Slice | +|------------------------------------------------------------|--------------|----------------| +| Ultra-high fidelity imaging for medical applications | ✓ | | +| Immersive and Interactive Media | ✓ | ✓ | +| Audio Streaming in Live Productions | ✓ | ✓ | +| Remote, Co-operative and Smart Media Production | ✓ | | +| incorporating User-Generated Content | | | +| Professional Content Production | ✓ | | +| Machine generated content | ✓ | | +| Collaborative design including immersive communication | ✓ | ✓ | +| Dynamic and Flexible UHD Content Distribution over 5G CDNs | | ✓ | +| Smart Education | ✓ | ✓ | + +The authors make a case for different design choices using number of slices for media use cases. An extract from the document: + +Other use cases, identified in Chapter 2, requiring a combination of both uplink and downlink traffic, often with strong latency requirements, are the following: + +- Immersive and Interactive media +- Audio Streaming in Live productions +- Collaborative Design including Immersive Communication +- Smart Education + +For these use cases the uplink traffic needs to be synchronised or correlated to the downlink traffic. In order to support these use cases, the 5G system should provide one of the following: + +- a new type of slice with support for downlink and uplink at the same time +- **the ability to link an uplink slice to a downlink slice in order to synchronise or correlate the uplink traffic and the downlink traffic running through them, respectively.** + +One way to realize the use cases referenced above requiring a combination of uplink and downlink traffic is to run them in different network slices. By doing so, QoS requirements for uplink traffic and downlink traffic can be provided using differentiated QoS possible because of network slicing. + +NOTE: Uplink and downlink traffic carried over different network slices should have different Traffic descriptors (containing one or more components, as described in table 6.6.2.1-2 of TS 23.503 [16]). + +### 5.3.2 Premium gaming slice + +[29] discusses aspects related to commercializing 5G network slicing. The white paper discusses network slicing use cases and path to initial commercialization, and evolution of network slicing technology. The white paper discusses gaming slice scenarios, and talks of two use-cases: + +- **Premium service use-case:** where the user pays in a subscription model and will be able to use such premium treatment whenever it needs [**provided using a separate dedicated premium network slice**] +- **Upsell use-case:** where the user pays a one-time fee for a premium slice-enabled treatment, such as in the previously mentioned example of a temporary boost in performance for video or gaming + +The white paper states the following: + +One aspect we have hinted at but not discussed in detail is the on-demand enablement of slicing in the upsell scenario. While the Premium use case approach can be implemented by configuring the network with allowed NSSAI-s and modifying the user profile to use specific NSSAI when accessing the network, the Upsell approach requires communication between subscriber's app, or the OS in case it intermediates the payment, and the Core for the purpose of dynamically managing the slicing activation/deactivation, as well as the monetization aspect. **An example of upsell in our gaming slice scenario involves asking the user to purchase the gaming slice treatment for a desired duration at a premium slice, at which point a network API would be accessed to enable the user to access the gaming slice. In this example, it would trigger the sending of a new URSP table that contains the rule and route for the gaming NSSAI.** + +## 5.4 Collaboration scenarios for network slicing + +### 5.4.0 General + +#### 5.4.0.1 Scenarios based on network slicing architecture + +Clause 4.2 of the present document describes network slicing architecture based on specification in TS 23.501 [7] and figure 4.2.1-1 summarises the relationships between network slice instances, PDU Sessions, and DNNs. + +From figure 4.2.1-1, the following can be inferred: + +1. A UPF instance may be shared between multiple network slices. +2. Multiple PDU Sessions terminating in different Data Networks may share the same slice. +3. PDU Sessions in different network slice instances may terminate in the same Data Network. + +Based on this, the following two collaborations not currently specified in TS 26.501 [20] are possible: + +- Downlink media streaming wherein a 5GMS AS delivers content through two different network slices. +- Downlink media streaming wherein 5GMS AS instances deployed in different Trusted DNs are accessed by the 5GMSd client in the same network slice. + +Clause 5.4.2 of the present document describes collaboration options based on the above two possibilities. + +#### 5.4.0.2 Network slicing scenarios + +There is some literature on the web about 5G network slicing [30][31][32][33][34][35]. Some of these [31][32][33] have information about possible ways network slicing could be used. Based on literature study, and related standard specification in 3GPP and other SDOs, we can discuss network slicing scenarios from the following perspective. + +Clause 5.15.2 of TS 23.501 [7] describes the identification of network slice using NSSAI, and specifies the following: + +*An S-NSSAI identifies a Network Slice.* + +*An S-NSSAI is comprised of:* + +- *A Slice/Service type (SST), which refers to the expected Network Slice behaviour in terms of features and services;* +- *A Slice Differentiator (SD), which is optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices of the same Slice/Service type.* + +Table 5.15.2.2-1 of TS 23.501 [7] specifies standardized SST values. [36][30][37] shed light on usage of the SD value as a way to describe services, customer information and slice priority. Of particular interest amongst these three types of information is the customer information (or the tenancy information) which indicates the slice allocated to a specific customer/tenant, and the service information (to identify a service/application). + +Based on the above NSSAI identification, different network slicing scenarios are possible: + +1. *A slice allocated for a specific customer/tenant.* For example, a network slice allocated by the MNO for a specific enterprise. In this scenario, all applications of every UE in the enterprise use the allocated network slice. The SD field of the S-NSSAI is used to indicate the customer/tenant. + - Both the Android [38] and iOS [39] mobile Operating Systems have recently started supporting 5G network slicing in mobile devices for enterprise users. Android 12 onwards supports network slicing with a separate enterprise slice and slicing based on user profiles, while Android 13 onwards supports network slicing with multiple enterprise slices [38]. +2. *A slice allocated for a specific customer/tenant for a specific service/application.* For example, a network slice allocated by the MNO for a specific enterprise and application. In this scenario, the application in every UE in the enterprise uses the allocated enterprise network slice; all other applications in enterprise UEs use a different (possibly default) network slice. The SD field of the S-NSSAI is used to indicate the customer/tenant and the service information. +3. *A slice allocated for a specific service/application:* For example, a slice optimized for 5G Media Streaming. In this scenario, the optimized slice is shared between all UEs, specifically for 5G Media Streaming application; the UEs use a different (possibly default) slice for other applications/services. The SD field of the S-NSSAI is used to indicate the service/application. + - The GSM Association specifies application-based network slicing [35], in which different network slices are provisioned for different applications. +4. *A slice leased by MNO to a virtual operator.* In this scenario, the virtual operator leases a network slice from the MNO, and in turn, can offer any of the above three network slicing scenarios to its customers over the leased network slice. + +Clause 5.4.3 of the present document describes collaboration options based on the above network slicing scenarios. + +### 5.4.1 Collaboration scenarios for network slicing based on downlink media streaming scenarios + +This clause presents the MNO CDN, OTT, and multi-MNO distribution collaboration scenarios corresponding to those described in clauses A.2, A.3, and A.8 of TS 26.501 [20] enhanced with network slicing. Other MNO CDN and OTT collaboration scenarios (clauses A.1, A.4, A.5, A.6, A.7 of TS 26.501 [20]) can be similarly enhanced, and are therefore not presented here. + +#### 5.4.1.1 Downlink media streaming with both AF and AS deployed in the trusted Data Network + +The collaboration scenario shown in figure 5.4.1.1-1 corresponds to the MNO CDN collaboration scenario described in clause A.2 of TS 26.501 [20] delivered using a network slice. + +![Figure 5.4.1.1-1: Downlink media streaming with AF and AS in the trusted Data Network with Network Slicing. The diagram shows a UE containing a 5GMSd-Aware Application and a 5GMSd Client. The 5GMSd Client connects via a PDU Session #A (labeled M4d) to a Trusted DN. Inside the Trusted DN, there are two components: 5GMSd AF and 5GMSd AS, connected by a vertical dashed line labeled M3d. The 5GMSd AF connects via a horizontal line labeled M1d to an External DN containing a 5GMSd Application Provider. The 5GMSd AS connects via a horizontal line labeled M2d to the same 5GMSd Application Provider. A dashed box labeled M8d encloses the 5GMSd-Aware Application, the 5GMSd Client, and the PDU Session #A. A shaded area labeled Network Slice Instance X covers the UE and the PDU Session #A.](12de9b926df0384ec07702671827c9cd_img.jpg) + +Figure 5.4.1.1-1: Downlink media streaming with AF and AS in the trusted Data Network with Network Slicing. The diagram shows a UE containing a 5GMSd-Aware Application and a 5GMSd Client. The 5GMSd Client connects via a PDU Session #A (labeled M4d) to a Trusted DN. Inside the Trusted DN, there are two components: 5GMSd AF and 5GMSd AS, connected by a vertical dashed line labeled M3d. The 5GMSd AF connects via a horizontal line labeled M1d to an External DN containing a 5GMSd Application Provider. The 5GMSd AS connects via a horizontal line labeled M2d to the same 5GMSd Application Provider. A dashed box labeled M8d encloses the 5GMSd-Aware Application, the 5GMSd Client, and the PDU Session #A. A shaded area labeled Network Slice Instance X covers the UE and the PDU Session #A. + +**Figure 5.4.1.1-1: Downlink media streaming with AF and AS in the trusted Data Network with Network Slicing** + +The 5GMSd Application Provider may negotiate with the MNO for creation of a network slice as described in clause 4.2.2. The network slice is provisioned by the network operator as described in clause 4.3. + +All the interactions between the participating entities (5GMSd Application Provider, 5GMSd-Aware Application, 5GMSd Client, 5GMSd AF, and 5GMSd AS) for the 5G Media Streaming session described in clause A.2 of TS 26.501 [20] apply in this scenario. All M4d interactions happen through a PDU Session established within the provisioned network slice. + +#### 5.4.1.2 Downlink media streaming with both AF and AS deployed in an external Data Network (OTT) + +This collaboration scenario shown in figure 5.4.1.2-1 corresponds to the OTT collaboration scenario described in clause A.3 of TS 26.501 [20] delivered using a network slice. + +![Figure 5.4.1.2-1: Downlink media streaming with AF and AS in an external Data Network (OTT) with Network Slicing. The diagram shows a UE containing a 5GMSd-Aware Application and a 5GMSd Client. The 5GMSd Client connects via a PDU Session #A (labeled M4d) to a Trusted DN. Inside the Trusted DN, there is a NEF connected via a horizontal line labeled N33 to an External DN. The NEF connects to a 5GMSd AF, which in turn connects via a horizontal line labeled M1d' to a 5GMSd Application Provider. The 5GMSd AF is also connected to a 5GMSd AS via a vertical dashed line labeled M3d. The 5GMSd AS connects via a horizontal line labeled M2d' to the same 5GMSd Application Provider. A dashed box labeled M8d encloses the 5GMSd-Aware Application, the 5GMSd Client, and the PDU Session #A. A shaded area labeled Network Slice Instance X covers the UE and the PDU Session #A. There is also a label M5d near the PDU Session #A.](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +Figure 5.4.1.2-1: Downlink media streaming with AF and AS in an external Data Network (OTT) with Network Slicing. The diagram shows a UE containing a 5GMSd-Aware Application and a 5GMSd Client. The 5GMSd Client connects via a PDU Session #A (labeled M4d) to a Trusted DN. Inside the Trusted DN, there is a NEF connected via a horizontal line labeled N33 to an External DN. The NEF connects to a 5GMSd AF, which in turn connects via a horizontal line labeled M1d' to a 5GMSd Application Provider. The 5GMSd AF is also connected to a 5GMSd AS via a vertical dashed line labeled M3d. The 5GMSd AS connects via a horizontal line labeled M2d' to the same 5GMSd Application Provider. A dashed box labeled M8d encloses the 5GMSd-Aware Application, the 5GMSd Client, and the PDU Session #A. A shaded area labeled Network Slice Instance X covers the UE and the PDU Session #A. There is also a label M5d near the PDU Session #A. + +**Figure 5.4.1.2-1: Downlink media streaming with AF and AS in an external Data Network (OTT) with Network Slicing** + +The 5GMSd Application Provider may negotiate with the MNO for the creation of a network slice as described in clause 4.2.2. The network slice is provisioned by the network operator as described in clause 4.3. + +All the interactions between all the participating entities (5GMSd Application Provider, 5GMSd-Aware Application, 5GMSd Client, 5GMSd AF, and 5GMSd AS) described in clause A.3 of TS 26.501 [20] apply in this scenario. All M4d and M5d interactions happen through a PDU Session established within the provisioned network slice. + +#### 5.4.1.3 Downlink media streaming with AFs deployed in two separate trusted Data Networks sharing AS in an external Data Network + +This collaboration scenario shown in figure 5.4.1.3-1 represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content to multiple UEs connected to different 5GMSd-capable PLMNs, as described in clause A.8 of TS 26.501 [20], but delivered using network slices on those PLMNs. + +![Figure 5.4.1.3-1: Downlink media streaming with AFs in two trusted Data Networks sharing AS in an external Data Network with Network Slicing](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + + graph TD + subgraph UE_PLMN1 [UE (PLMN #1)] + App1[5GMSd-Aware Application] + Client1[5GMSd Client] + App1 --- Client1 + end + + subgraph UE_PLMN2 [UE (PLMN #2)] + App2[5GMSd-Aware Application] + Client2[5GMSd Client] + App2 --- Client2 + end + + subgraph TrustedDN1 [Trusted DN (PLMN #1)] + PCF1[PCF] + AF1[5GMSd AF / 5GMSd AF #1] + subgraph SliceX [Network Slice Instance X] + PDU_A((PDU Session #A)) + end + PCF1 -- N5 --- AF1 + end + + subgraph TrustedDN2 [Trusted DN (PLMN #2)] + PCF2[PCF] + AF2[5GMSd AF / 5GMSd AF #1] + subgraph SliceY [Network Slice Instance Y] + PDU_B((PDU Session #B)) + end + PCF2 -- N5 --- AF2 + end + + subgraph ExternalDN [External DN] + Prov[Provisioning] + AS[5GMSd AS] + AP[5GMSd Application Provider] + end + + Client1 -- M5d/M4d --- PDU_A + Client2 -- M4d/M5d --- PDU_B + PDU_A --- AF1 + PDU_B --- AF2 + AF1 -- M1d --- AP + AF2 -- M1d --- AP + Prov -- M1d' --- AP + AS -- M2d' --- AP + PDU_A --- AS + PDU_B --- AS + +``` + +The diagram shows two UEs (PLMN #1 and PLMN #2) each containing a 5GMSd-Aware Application and a 5GMSd Client. Each UE connects to its respective Trusted Data Network (DN) via a Network Slice Instance (X and Y). Within these slices, PDU Sessions (#A and #B) are established. Each Trusted DN contains a PCF and a 5GMSd AF. The 5GMSd AFs connect to a central 5GMSd Application Provider in an External DN via M1d interfaces. The External DN also contains a Provisioning entity (connected via M1d') and a 5GMSd AS (connected via M2d'). The PDU sessions from both PLMNs terminate at the shared 5GMSd AS in the External DN. + +Figure 5.4.1.3-1: Downlink media streaming with AFs in two trusted Data Networks sharing AS in an external Data Network with Network Slicing + +**Figure 5.4.1.3-1: Downlink media streaming with AFs in two trusted Data Networks sharing AS in external Data Network with Network Slicing** + +The 5GMSd Application Provider may negotiate with each of the PLMNs for creation of network sliced as described in clause 4.2.2 of the present document. The network slice for each PLMN is provisioned by the PLMN operator as described in clause 4.3. + +All the interactions between all the participating entities (5GMSd Application Provider, 5GMSd-Aware Application, 5GMSd Client, 5GMSd AF, and 5GMSd AS, PCF) described in clause A.8 of TS 26.501 [20] apply in this scenario. All M4 and M5 interactions happen through PDU Sessions established within the provisioned network slices. Each UE in a different PLMN may use the provisioned network slice in that PLMN for all the 5G Media Streaming operations. The same external CDN (5GMSd AS) serves the users of both the PLMNs, and all the signaling and media traffic is sent through PSU Sessions in respective network slices. + +### 5.4.2 Collaboration scenarios for network slicing with multiple slices or Data Networks + +#### 5.4.2.1 Downlink media streaming with AS deployed in external Data Network and AS delivering content through two different network slices + +This collaboration scenario shown in figure 5.4.2.1-1 represents the case of accessing the same external Data Network through two different network slices shown in figure 4.2.1-1. An external CDN (5GMSd AS) is accessed by the UE via this Data Network. + +![Diagram of downlink media streaming with AS in external Data Network accessible through two different network slices. The diagram shows a UE on the left containing a 5GMSd-Aware Application, 5GMSd Client, and UNP Rules. The UE connects to two Network Slice Instances, X and Y, via PDU Sessions #A and #B respectively. Both sessions pass through a Trusted DN and then to an External DN. In the External DN, the traffic goes to a 5GMSd AS, which is connected to a 5GMSd Application Provider. Reference points M4d, M8d, M1d', M3d', and M2d' are indicated.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +The diagram illustrates the network architecture for downlink media streaming. On the left, a User Equipment (UE) box contains three components: 'UNP Rules', '5GMSd-Aware Application', and '5GMSd Client'. The '5GMSd Client' is connected to two 'Network Slice Instance' boxes, labeled 'X' and 'Y'. Each instance is associated with a 'PDU Session' (labeled '#A' and '#B'). These sessions pass through a 'Trusted DN' (represented by a grey box) and then into an 'External DN' (represented by a light blue box). In the 'External DN', the traffic from both sessions converges at a '5GMSd AS' (yellow box). The '5GMSd AS' is connected to a '5GMSd Application Provider' (light blue box). Reference points are marked: 'M4d' at the UE-to-slice interface, 'M8d' between the UE and the External DN, 'M1d'' between the 5GMSd AS and the 5GMSd Application Provider, 'M3d'' between the 5GMSd AS and the 5GMSd Application Provider, and 'M2d'' between the 5GMSd AS and the 5GMSd Application Provider. + +Diagram of downlink media streaming with AS in external Data Network accessible through two different network slices. The diagram shows a UE on the left containing a 5GMSd-Aware Application, 5GMSd Client, and UNP Rules. The UE connects to two Network Slice Instances, X and Y, via PDU Sessions #A and #B respectively. Both sessions pass through a Trusted DN and then to an External DN. In the External DN, the traffic goes to a 5GMSd AS, which is connected to a 5GMSd Application Provider. Reference points M4d, M8d, M1d', M3d', and M2d' are indicated. + +**Figure 5.4.2.1-1: Downlink media streaming with AS in external Data Network accessible through two different network slices** + +The 5GMSd Application Provider may negotiate with the MNO to setup two different network slices with different SLAs as described in clause 4.3. After the SLA negotiation, the operator may provision two network slices, and provide connectivity services to the external Data Network through both the slices. + +The 5GMSd Application Provider may deliver Service Access Information through reference point M8d. The Service Access Information delivered to the 5GMSd-Aware Application may have information about different Service Operation Points accessible through each of the network slices. Upon receiving the Service Access Information, the 5GMSd-Aware Application passes this information to the 5GMSd Client. The 5GMSd Client selects the Service Operation Point of interest, and requests media streaming session establishment over the PDU Session in the network slice that provides the required Service Operation Point. Media streaming (M4d) thus happens through the selected network slice. + +The other network slice may be used to fetch other media streaming assets (depending on criticality and SLA availability considerations), or serves as an alternate network slice in case the first slice becomes unavailable, as discussed in clause 6.3. + +NOTE: The usage of multiple network slices simultaneously by the same application is currently not supported by either Android or iOS. This collaboration scenario is unlikely to be deployed. + +#### 5.4.2.2 Downlink media streaming with AS deployed in multiple trusted Data Networks + +This collaboration scenario shown in figure 5.4.2.2-1 represents the case of accessing two different Data Networks using the same network slice as shown in figure 4.2.1-1. A CDN server (5GMSd AS) is either deployed in each of the trusted Data Networks, or presents a multi-homed interface at reference point M4d through each of the trusted DNs. + +![Figure 5.4.2.2-1: Downlink media streaming with AS deployed in multiple trusted Data Networks. The diagram shows a User Equipment (UE) on the left containing a 5GMSd Client and a 5GMSd-Aware Application. The UE connects via PDU Session #A and PDU Session #B to two separate Trusted Data Networks (Trusted DN #1 and Trusted DN #2) through a Network Slice Instance X. Each Trusted DN contains a 5GMSd AS. Both 5GMSd ASes connect to a central 5GMSd AF, which in turn connects to a 5GMSd Application Provider in an External DN. Reference points M4d, M2d, M3d, and M1d' are indicated between the components. A dashed line labeled M8d connects the UE to the External DN.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Figure 5.4.2.2-1: Downlink media streaming with AS deployed in multiple trusted Data Networks. The diagram shows a User Equipment (UE) on the left containing a 5GMSd Client and a 5GMSd-Aware Application. The UE connects via PDU Session #A and PDU Session #B to two separate Trusted Data Networks (Trusted DN #1 and Trusted DN #2) through a Network Slice Instance X. Each Trusted DN contains a 5GMSd AS. Both 5GMSd ASes connect to a central 5GMSd AF, which in turn connects to a 5GMSd Application Provider in an External DN. Reference points M4d, M2d, M3d, and M1d' are indicated between the components. A dashed line labeled M8d connects the UE to the External DN. + +**Figure 5.4.2.2-1: Downlink media streaming with AS deployed in multiple trusted Data Networks** + +The 5GMSd Application Provider may negotiate with the MNO to provision a network slice as described in clause 4.3. The operator provisions the network slice, and provides connectivity services to both the DNs through the slice. + +The 5GMSd Application Provider may deliver Service Access Information through reference point M8d. The Service Access Information delivered to the 5GMSd-Aware Application may have information about different Service Operation Points accessible through each of the DNs. For example, an enterprise may utilize an enterprise-specific CDN (e.g., hosting enterprise-related video tutorials). 5G Media Streaming sessions for enterprise-related video tutorials use the PDU Session terminating in the enterprise-specific CDN, while some other video tutorial requests are sent through PDU Sessions terminating in a different CDN. Alternatively, a DN may act as a back-up CDN, utilized by the 5GMSd Client if the primary CDN is inaccessible or unavailable for any reason. + +In a variant of this scenario, the second CDN may be a CDN edge with optional media processing. + +In another variation of the above scenario shown in figure 5.4.2.2-1, a common 5GMS AS may serve traffic via two trusted Data Networks down the separate PDU Sessions, as shown in figure 5.4.2.2-2. + +![Figure 5.4.2.2-2: Downlink media streaming with single AS serving traffic through multiple Data Networks. The diagram shows a UE containing a 5GMSd Client and a 5GMSd-Aware Application. The client connects to Network Slice Instance X, which is part of a larger M8d system. Within M8d, there are two Trusted DNs (Trusted DN #1 and Trusted DN #2). PDU Session #A connects the client to 5GMSd AF in Trusted DN #1 via M5d and M4d interfaces. PDU Session #B connects the client to 5GMSd AF in Trusted DN #2 via M4d and M5d interfaces. Both 5GMSd AFs connect to a 5GMSd AS in an External DN via M1d and M1d' interfaces. The 5GMSd AS connects to a 5GMSd Application Provider via M2d' and M1d interfaces. URSP Rules are shown on the left side of the UE.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Figure 5.4.2.2-2: Downlink media streaming with single AS serving traffic through multiple Data Networks. The diagram shows a UE containing a 5GMSd Client and a 5GMSd-Aware Application. The client connects to Network Slice Instance X, which is part of a larger M8d system. Within M8d, there are two Trusted DNs (Trusted DN #1 and Trusted DN #2). PDU Session #A connects the client to 5GMSd AF in Trusted DN #1 via M5d and M4d interfaces. PDU Session #B connects the client to 5GMSd AF in Trusted DN #2 via M4d and M5d interfaces. Both 5GMSd AFs connect to a 5GMSd AS in an External DN via M1d and M1d' interfaces. The 5GMSd AS connects to a 5GMSd Application Provider via M2d' and M1d interfaces. URSP Rules are shown on the left side of the UE. + +**Figure 5.4.2.2-2: Downlink media streaming with single AS serving traffic through multiple Data Networks** + +### 5.4.3 Collaboration options based on network slicing scenarios + +#### 5.4.3.0 General + +Scenarios described in this clause are based on the MNO CDN collaboration scenario described in clause A.7 of TS 26.501 [20] wherein both the 5GMSd AF and 5GMSd AS are deployed in the Trusted DN, and the 5GMSd Application Provider uses reference points M1d and M2d respectively to interact with them. + +NOTE: All the collaboration scenarios described in clause A of TS 26.501 [20] can be similarly shown with each of the network slicing scenarios described in this clause. + +#### 5.4.3.1 Scenario #1: Slice serving a set of enterprise services/applications + +This is a network slicing scenario wherein the MNO, upon a request from an enterprise, allocates one or more network slices exclusively for enterprise users. + +Figure 5.4.3.1-1 shows the case of an enterprise network slice for all applications in the enterprise UE. Every application on the enterprise UE, including the 5GMSd-Aware Application, uses the allocated network slice for communication with the DN entities. + +NOTE: Android 12 onwards supports network slicing with a separate enterprise network slice allocated by the MNO. + +![Figure 5.4.3.1-1: Network slice for all applications in the enterprise UE.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +This diagram illustrates the network architecture for an Enterprise UE using a single network slice. +- On the left, the **Enterprise UE** contains a **5GMSd-Aware Application** and a **5GMSd Client** (within a 5GMS block) and other **Applications**. +- The **Enterprise Network Slice Instance** spans from the UE to the **Trusted DN**. +- Within the **Trusted DN**, there is a **5GMSd AF** and a **5GMSd AS**, connected by interface **M3d**. +- Interfaces: **M5d** connects the 5GMSd Client to the 5GMSd AF. **M4d** connects the 5GMSd Client to the 5GMSd AS. **Traffic of other Applications** is shown as a separate path. +- On the right, the **External DN** contains the **5GMSd Application Provider**. +- Interfaces: **M1d** connects the 5GMSd AF to the Provider. **M2d** connects the 5GMSd AS to the Provider. +- A dashed line labeled **M8d** connects the 5GMSd-Aware Application directly to the 5GMSd Application Provider. + +Figure 5.4.3.1-1: Network slice for all applications in the enterprise UE. + +**Figure 5.4.3.1-1: Network slice for all applications in the enterprise UE** + +Figure 5.4.3.1-2 shows the case of an enterprise network slice for applications in the enterprise profile of the UE. + +![Figure 5.4.3.1-2: Network slice for enterprise profile applications.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +This diagram illustrates a UE with split profiles: **Enterprise Profile** and **Personal Profile**. +- **Enterprise Profile**: Contains its own 5GMSd-Aware Application and 5GMSd Client. It uses an **Enterprise Network Slice Instance**. It connects to a 5GMSd AF and AS in the Trusted DN via **M5d** and **M4d**. +- **Personal Profile**: Contains its own 5GMSd-Aware Application and 5GMSd Client. It uses a **Default Network Slice Instance**. It connects to a separate set of 5GMSd AF and AS in the Trusted DN via **M5d** and **M4d**. +- Both profiles' AF/AS pairs in the **Trusted DN** connect to the same **5GMSd Application Provider** in the **External DN** via **M1d** and **M2d** interfaces. +- A dashed line labeled **M8d** connects the 5GMSd-Aware Applications from both profiles to the 5GMSd Application Provider. + +Figure 5.4.3.1-2: Network slice for enterprise profile applications. + +**Figure 5.4.3.1-2: Network slice for enterprise profile applications** + +In this scenario: + +- Every application in the enterprise/work profile of the UE, including the 5GMSd-Aware Application, uses the allocated enterprise network slice for communication with DN entities accessible from that slice. +- Every application in the non-enterprise profile of the UE (e.g., personal profile), including the 5GMSd-Aware application, uses the default (e.g., eMBB) network slice for communication with DN entities accessible from that slice. + +NOTE: Android 13 onwards supports network slicing with multiple enterprise slices, and slicing based on user profiles. + +#### 5.4.3.2 Scenario #2: Slice serving a specific application of an enterprise + +This is a network slicing scenario wherein the MNO, upon a request from an enterprise, allocates a specific network slice for a specific service/application for enterprise users. + +Figure 5.4.3.2-1 shows the case of an enterprise network slice for a specific application (e.g., 5GMSd-Aware Application) for enterprise UEs. The media streaming traffic belonging to the 5GMSd-Aware application is sent through the enterprise network slice, while traffic for all other applications is sent through a default network slice (e.g. eMBB). + +![Diagram of network slice for specific application for enterprise users. The diagram shows an Enterprise UE containing a 5GMSd-Aware Application and a 5GMSd Client, and other applications. The 5GMSd Client connects via M5d to the 5GMSd AF and via M4d to the 5GMSd AS within the Enterprise Network Slice Instance. The 5GMSd AF and AS connect via M1d and M2d respectively to the 5GMSd Application Provider in the External DN. Other applications send traffic through the Default Network Slice Instance to the Trusted DN and Other DN. The 5GMSd AF and AS are also connected to the M8d interface.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +The diagram illustrates the network architecture for Scenario #2. On the left, an 'Enterprise UE' is shown, which contains a '5GMSd-Aware Application' and a '5GMSd Client' (both part of the '5GMS' profile), and 'Other Applications'. The '5GMSd Client' connects via the 'M5d' interface to the '5GMSd AF' and via the 'M4d' interface to the '5GMSd AS', both located within the 'Enterprise Network Slice Instance'. The '5GMSd AF' and '5GMSd AS' are connected via the 'M8d' interface to the 'M1d' and 'M2d' interfaces of the '5GMSd Application Provider' in the 'External DN'. The 'Other Applications' send 'Traffic of other Applications' through the 'Default Network Slice Instance' to the 'Trusted DN' and 'Other DN'. The '5GMSd AF' and '5GMSd AS' are also connected to the 'M3d' interface. + +Diagram of network slice for specific application for enterprise users. The diagram shows an Enterprise UE containing a 5GMSd-Aware Application and a 5GMSd Client, and other applications. The 5GMSd Client connects via M5d to the 5GMSd AF and via M4d to the 5GMSd AS within the Enterprise Network Slice Instance. The 5GMSd AF and AS connect via M1d and M2d respectively to the 5GMSd Application Provider in the External DN. Other applications send traffic through the Default Network Slice Instance to the Trusted DN and Other DN. The 5GMSd AF and AS are also connected to the M8d interface. + +Figure 5.4.3.2-1: Network slice for specific application for enterprise users + +URSP rules, provisioned by the PCF, as described in clause 6.6.2.2 of TS 23.503 [16], assist in traffic detection and route selection of appropriate network slice for application traffic in the UE. + +#### 5.4.3.3 Scenario #3: Slice optimized for a specific service/application + +This is a network slicing scenario wherein the MNO allocates a specific network slice for a specific service/application for use by multiple users. (The MNO may also provision additional network slices for carrying traffic of other specific applications.) + +NOTE 1: The GSM Association specifies application-based network slicing [40], in which different network slices are provisioned for different applications. + +NOTE 2: Unlike Scenario#1 and Scenario#2, the users in this scenario need not belong to the same enterprise. + +Figure 5.4.3.3-1 shows the case of a slice optimized for downlink 5G Media Streaming. The traffic belonging to the 5GMSd-Aware Applications of all users is sent through this network slice, while the traffic of other applications is sent through a default network slice (e.g., eMBB). + +![Diagram illustrating a network slice optimized for 5G Media Streaming (5GMSd) for all users. The diagram shows two User Equipment (UE) units, UE #1 and UE #2, connected to a network slice. UE #1 contains 'Other Applications' and a '5GMSd-Aware Application' connected to a '5GMSd Client'. UE #2 contains a '5GMSd Client' connected to a '5GMSd-Aware Application' and 'Other Applications'. Both UEs send traffic to a 'Default Network Slice Instance' (for other applications) and a 'Network Slice Instance optimized for 5GMS' (for 5GMSd traffic). The optimized slice connects to 'Other DN' and 'Trusted DN' areas. Within the Trusted DN, there are '5GMSd AF' and '5GMSd AS' components. The 5GMSd AF connects to a '5GMSd Application Provider' via interface M1d. The 5GMSd AS connects to the '5GMSd Application Provider' via interface M2d. The '5GMSd Application Provider' is connected to an 'External DN'. Interfaces M8d are shown at the top and bottom of the diagram, and interface M3d is shown between the 5GMSd AF and 5GMSd AS.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +Diagram illustrating a network slice optimized for 5G Media Streaming (5GMSd) for all users. The diagram shows two User Equipment (UE) units, UE #1 and UE #2, connected to a network slice. UE #1 contains 'Other Applications' and a '5GMSd-Aware Application' connected to a '5GMSd Client'. UE #2 contains a '5GMSd Client' connected to a '5GMSd-Aware Application' and 'Other Applications'. Both UEs send traffic to a 'Default Network Slice Instance' (for other applications) and a 'Network Slice Instance optimized for 5GMS' (for 5GMSd traffic). The optimized slice connects to 'Other DN' and 'Trusted DN' areas. Within the Trusted DN, there are '5GMSd AF' and '5GMSd AS' components. The 5GMSd AF connects to a '5GMSd Application Provider' via interface M1d. The 5GMSd AS connects to the '5GMSd Application Provider' via interface M2d. The '5GMSd Application Provider' is connected to an 'External DN'. Interfaces M8d are shown at the top and bottom of the diagram, and interface M3d is shown between the 5GMSd AF and 5GMSd AS. + +**Figure 5.4.3.3-1: Network slice for specific application for all users** + +URSP rules, provisioned by the PCF, as described in clause 6.6.2.2 of TS 23.503 [16], assist in traffic detection and route selection of the appropriate network slice for application traffic in the UE. + +#### 5.4.3.4 Scenario #4: Slice serving a virtual operator + +This is a network slicing scenario where a virtual operator leases network slice from the MNO, and uses it to provide service to its customers as described in clause 5.2.2 of present document. The virtual operator may, in turn, offer any of the above three slicing scenarios on the leased network slice. + +# 6 Key issues and candidate solutions + +## 6.1 Key Issue #1: Service Provisioning + +### 6.1.1 Description + +#### 6.1.1.1 Provisioning multiple Network Slices for media streaming + +Clause 5.3.2 of the present document describes a use case for premium gaming where two network slices are provisioned by the 5GMS Application Provider for users with different subscription levels. Clauses 7 and 11 of TS 26.512 [21] describe 5G Media Streaming APIs for (respectively) M1 Provisioning and M5 Media Session Handling. However, the present APIs support only one Network Slice per Provisioning Session. Furthermore, it is not clear from [21] whether the same Service Operation Points and Policy Templates are available in different slices when they are provisioned in this way. + +Open issues: + +- Whether and how the 5GMS Provisioning (M1) APIs and corresponding data model definitions in [21] need to be enhanced to support the use case referenced by this Key Issue. +- Whether and how the Media Session Handling (M5) APIs and corresponding data model definitions in [21] need to be enhanced to support the use case referenced by this Key Issue. + +NOTE: Migration of media flows to different Network Slice is studied separately in clause 6.3 + +Assumptions: + +- Slice creation and activation are out of scope of this Key Issue. The 5GMS Application Provider may perform offline negotiation with MNO OAM for slice creation and activation as described in clause 4.3. + +### 6.1.2 Candidate solutions + +#### 6.1.2.1 Candidate solution #1: Policy template provisioning for a plurality of Network Slices and/or DNNs + +Pre-requisites and assumptions: + +- A single 5GMS Application Provider (with identity *aspId*) intends to provision a Policy Template for a plurality of Network Slices. +- The one or more Network Slices are already provisioned and activated. Appropriate Slice and DNN identifiers are known to the 5GMS Application Provider. +- The 5GMS AF is preconfigured by the 5G System operator with a mapping from IP subnet range(s) to S-NSSAI/DNN duples so that it can select an appropriate Network Slice and/or Data Network when manipulating the network QoS of the application flows described by a Network Assistance session or Dynamic Policy invocation. + +To enable a Policy Template to be valid for more than one Network Slice and/or DNN, in this candidate solution the Policy Template resource specified in clause 7.9.3.1 of TS 26.512 [21] is modified as follows: + +1. Add an array of *networkContexts* as a child under the *applicationSessionContext* parent. For backwards compatibility with the existing syntax, this array may be omitted, or present but empty. +2. Each Network Context object includes the existing *sliceInfo* and *dnn* properties. Both properties remain optional, so it is syntactically valid for the *networkContexts* array to contain empty objects (although this is meaningless semantically). + +### 7.9.3 Data model + +#### 7.9.3.1 PolicyTemplate resource + +The data model for the PolicyTemplate resource is specified in table 7.9.3-1 below: + +**Table 7.9.3-1: Definition of PolicyTemplate resource** + +| Property | Type | Cardinality | Usage | Visibility | Description | +|----------------------------|------------------------|-------------|-------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| policyTemplateId | ResourceId | 1..1 | C: RO
R: RO
U: RO | | Unique identifier of this Policy Template within the scope of the Provisioning Session. | +| state | Enumeration of Strings | 1..1 | C: RO
R: RO
U: RO | | A Policy Template may be in the PENDING, INVALID, READY, or SUSPENDED state.
Only a Policy Template in the READY state may be instantiated as a Dynamic Policy Instance and applied to media streaming sessions. | +| apiEndPoint | String | 1..1 | C: RW
R: RO
U: RW | MNO
Admin | The API endpoint that should be invoked when activating a Dynamic Policy Instance based on this Policy Template. | +| apiType | Enumeration of Strings | 1..1 | C: RW
R: RO
U: RW | MNO
Admin | N5: Npcf_PolicyAuthorization Service.
N33: AsSessionWithQoS or ChargableParty. | +| externalReference | String | 1..1 | C: RW
R: RO
U: RW | | Additional identifier for this Policy Template, unique within the scope of its Provisioning Session, that can be cross-referenced with external metadata about the media streaming session. | +| qoSSpecification | M1QoS Specification | 0..1 | C: RW
R: RO
U: RW | | Specifies the network quality of service to be applied to media streaming sessions at this Policy Template. | +| applicationSession Context | Object | 1..1 | | | Specifies information about the application session context to which this Policy Template can be applied. | +| afAppId | AfAppId | 0..1 | C: RW
R: RW
U: RW | | As defined in clause 5.6.2.3 of TS 29.514 [34] and clause 5.3.2 of TS 29.571 [12]. | +| networkContexts | Array(Object) | 0..1 | | | | +| sliceInfo | Snssai | 0..1 | C: RW
R: RW
U: RW | | | +| dnn | Dnn | 0..1 | C: RW
R: RW
U: RW | | | +| aspId | AspId | 1..1 | C: RW
R: RW
U: RW | | | +| chargingSpecification | Charging Specification | 0..1 | C: RW
R: RW
U: RW | | Provides information about the charging policy to be used for this Policy Template. | + +NOTE: The cardinality relationship between *aspId* and *sliceInfo* is for future study. + +### 6.1.3 Conclusions + +The study of the key issue involved looking into use cases for running 5G Media Streaming services in one or more Network Slices, and the current stage-3 support for provisioning those slices. The stage-3 API for Policy Template provisioning supports one Network Slice and/or Data Network per Provisioning Session. It is useful for the 5G Application Service Provider to provision multiple Network Slices and/or Data Networks at once if the same Policy Template may be applied to one or more Network Slices and/or Data Networks. + +The following is recommended for stage 3: + +- The *PolicyTemplate* resource data model in TS 26.510 [42] is enhanced to include an array of S-NSSAI and DNN duples, as described in clause 6.1.2 of the present document, to support Policy Template provisioning for a plurality of Network Slices and/or Data Networks. + +## 6.2 Key Issue #2: Realising dynamic policies using different slices + +### 6.2.1 Description + +#### 6.2.1.1 Slice selection for M5 dynamic policy requests + +**Editor's note:** Key issue to cover study objective of identifying the appropriate network slice for outbound M5 dynamic policy requests from UE to AF. + +### 6.2.2 Candidate solutions + +#### 6.2.2.1 Candidate solution #1 + +### 6.2.3 Conclusions + +No conclusion has been reached for this Key Issue. + +## 6.3 Key Issue #3: Moving media flows to other Network Slices + +### 6.3.1 Description + +#### 6.3.1.1 Migration of media streaming application flows between Network Slices + +As introduced in clause 4.2.3 of the present document, clause 5.1 of TR 23700-41 [26] studies a Key Issue on network slice service continuity. According to this, a Network Slice or Network Slice instance can become overloaded or the performance of the Network Slice may fall below the requirements of its SLA. + +The recommendation in clause 8.1 of [26] is for the 5G System to identify an alternative slice to migrate application flows from the PDU Session of the current slice to the existing PDU Session or a new one in the chosen alternative slice. When 5G Media Streaming sessions are carried over a PDU Sessions that cannot be migrated transparently to the application layer with the support of the service continuity procedure, the impacts on ongoing 5G Media Streaming sessions needs to be studied. + +Open issues: + +- Whether the service continuity procedure is transparent to 5G Media Streaming or requires enhancement of existing procedures and data model definitions in TS 26.501 [20] and TS 26.512 [21]. + +### 6.3.2 Candidate solutions + +#### 6.3.2.1 Candidate solution #1 + +### 6.3.3 Conclusions + +This Key Issue studied the aspect of network slice replacement specified by 3GPP SA2 in TS 23.501 [7] and its impact on 5G Media Streaming procedures. The study found that: + +- The network slice replacement procedure is transparent to the Application Function and the Application Service Provider. +- There is no guarantee that the Alternative S-NSSAI provides similar performance as that of the replaced S-NSSAI when a network slice replacement procedure is undertaken by the 5G System. + +We conclude that: + +- Per 3GPP SA2 guidance on the current support of network slice replacement in the 5G System, no normative work to enhance existing procedures in TS 26.501 [20] and data model definitions in TS 26.512 [21] is required at this time. +- Future work in 3GPP SA2 related to network slice replacement is to be monitored, and the data model definitions in TS 26.510 [42] enhanced, if necessary. + +## 6.4 Key Issue #4: AF discovery for dynamic policy + +### 6.4.1 Description + +#### 6.4.1.1 Discovery of 5GMS AF instance for dynamic policy + +**Editor's note:** Key issue to cover study objective of discovering dynamic policy AF that the UE sends the outbound M5 requests to. + +### 6.4.2 Candidate solutions + +#### 6.4.2.1 Candidate solution #1 + +### 6.4.3 Conclusions + +No conclusion has been reached for this Key Issue. + +## 6.5 Key Issue #5: Interoperability considerations + +### 6.5.1 Description + +#### 6.5.1.1 Communication between AF instances to support interoperability + +**Editor's note:** Key issue to cover study objective of determining the need and describing methods for AF-to-AF communication to support interoperability if 5GMS instances from different vendors are deployed in the 5GMS system. Media services may have different types of AFs (provisioning AF, dynamic policy AF, DCAF etc.) due to slicing, edge service provisioning, reporting configuration etc., and this key issue will cover communication aspects between those AFs if the AFs are deployed by different vendors. + +### 6.5.2 Candidate solutions + +#### 6.5.2.1 Candidate solution #1 + +### 6.5.3 Conclusions + +No conclusion has been reached for this Key Issue. + +## 6.6 Key Issue #6: Slice resource resolution + +### 6.6.1 Description + +#### 6.6.1.1 Resolve slice-specific application instances + +**Editor's note:** Key issue to cover study objective of identifying methods for deploying, supporting, and resolving slice-specific 5GMS AS instances. Solutions all levels - higher layer methods such as modification of media description documents to lower layer methods using networking protocols - can be included. + +### 6.6.2 Candidate solutions + +#### 6.6.2.1 Candidate solution #1 + +### 6.6.3 Conclusions + +No conclusion has been reached for this Key Issue. + +## 6.7 Key Issue #7: Bootstrapping application invocation on Network Slice + +### 6.7.1 Description + +#### 6.7.1.1 Discover appropriate Network Slice for 5GMS procedures + +Clauses 5 and 6 of TS 26.501 [20] describe the high-level procedures for downlink and uplink media streaming respectively. As part of these procedures, the 5GMS Application Provider performs service provisioning at the 5GMS AF. The 5GMS-Aware Application subsequently receives Service Access Information from the 5GMS Application Provider over reference point M8 or else acquires it directly from the 5GMS AF over reference point M5. If the UE currently has access to more than one Network Slice, it is unclear how the 5GMS-Aware Application and the 5GMS Client on the UE discover the appropriate Network Slice to use to establish a new media streaming session. + +Open issues: + +- How the bootstrapping of the application invocation on a Network Slice happens before the 5GMS Client performs 5G Media Streaming operations. + +### 6.7.2 Candidate solutions + +#### 6.7.2.1 Candidate solution #1: Bootstrapping based on Traffic Descriptor information + +Assumptions: + +- The 5GMS-Aware Application developer is aware of different OS App Ids supported by the UE operating system. + +Figure 6.7.2.1-1 below illustrates the procedure for bootstrapping application invocation on a Network Slice. + +![Sequence diagram showing the call flow for bootstrapping application invocation on a Network Slice. The diagram involves the following entities: 5GMS-Aware Application, 5GMS Client, UE Internal (OS), DNS, PCF, AMF, NEF, 5GMS AF, 5GMS AS, and 5GMS Application Provider. The flow starts with App registration (1) from the application to the OS, followed by session provisioning (2) from the provider to the AF. Guidance (3) is passed from the AF through the NEF to the UE. Service Access Information (4) is provided from the provider to the UE. The session is started (5) from the application to the client. The client selects a network slice (6) based on OS App Id and traffic descriptors. An 'alt' block for 'PDU Session already exists' (7) or 'No PDU Session' (8) handles session establishment. IP address resolution (9) is performed by the client. Media session handling (10) and streaming (11) occur between the client and the AF.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +``` + +sequenceDiagram + participant 5GMS-Aware Application + participant 5GMS Client + participant UE Internal (OS) + participant DNS + participant PCF + participant AMF + participant NEF + participant 5GMS AF + participant 5GMS AS + participant 5GMS Application Provider + + Note left of 5GMS-Aware Application: UE + 5GMS-Aware Application->>UE Internal (OS): 1: App registration with pre-defined OS App Id + 5GMS Application Provider->>5GMS AF: 2: Provision session with set of network slices {Application Information} + 5GMS AF->>NEF: 3: Application guidance for URSP determination + Note right of NEF: + 5GMS Application Provider->>UE Internal (OS): 4: Service Access Information over M8 + Note left of 5GMS-Aware Application: + 5GMS-Aware Application->>5GMS Client: 5: Start session + Note right of 5GMS Client: + 5GMS Client->>5GMS Client: 6: Select Network Slice based on OS App Id of 5GMS-Aware Application and traffic descriptors in URSP rules + alt 7: PDU Session already exists in selected Network Slice + Note right of 5GMS Client: Pick existing PDU Session for Media Streaming Session + else 8: No PDU Session in selected Network Slice + Note right of 5GMS Client: PDU Session Establishment in selected Network Slice + 5GMS Client->>AMF: + end + Note right of 5GMS Client: + 5GMS Client->>DNS: 9: Resolve IP address information of 5GMS AF and AS instances + Note right of DNS: + 5GMS Client->>5GMS AF: 10: Media Session Handling + Note right of 5GMS AF: + 5GMS Client->>5GMS AS: 11: Media streaming + Note right of 5GMS AS: + +``` + +Sequence diagram showing the call flow for bootstrapping application invocation on a Network Slice. The diagram involves the following entities: 5GMS-Aware Application, 5GMS Client, UE Internal (OS), DNS, PCF, AMF, NEF, 5GMS AF, 5GMS AS, and 5GMS Application Provider. The flow starts with App registration (1) from the application to the OS, followed by session provisioning (2) from the provider to the AF. Guidance (3) is passed from the AF through the NEF to the UE. Service Access Information (4) is provided from the provider to the UE. The session is started (5) from the application to the client. The client selects a network slice (6) based on OS App Id and traffic descriptors. An 'alt' block for 'PDU Session already exists' (7) or 'No PDU Session' (8) handles session establishment. IP address resolution (9) is performed by the client. Media session handling (10) and streaming (11) occur between the client and the AF. + +Figure 6.7.2.1-1: Call flow for bootstrapping application invocation on a Network Slice + +The steps are as follows: + +1. The 5GMS-Aware Application is installed on the UE, and and is programmed to invoke an OS-specific network connection API using a pre-defined OS App Id supported by the UE operating system. +2. The 5GMS Application Provider provisions the media streaming session in the 5GMS AF with one or more network slices at reference point M1. The provisioning information may include application information such as the *ProvisioningSession.externalApplicationId* specified in clause 7.2.3.1 of TS 26.512 [21]. The 5GMS AF uses this information to infer application traffic descriptor information used for application guidance, as specified in clause 4.15.6.10 of TS 23.502 [15]. +3. The 5GMS AF uses the *Nnef\_ServiceParameter* service defined in clause 5.2.6.1 of TS 23.502 [15] to provide application guidance for URSP determination via the NEF as described in clause 4.15.6.10 of TS 23.502 [15], which is eventually delivered to the UE as described in clause 4.15.6.7 of TS 23.502 [15]. + +NOTE 1: URSP rules may also be configured in the UE as described in clause 4.2.2 of this present document. + +4. The 5GMS Application Provider may provide Service Access Information to the 5GMS-Aware Application at reference point M8. In the Service Access Information, the 5GMS Application Provider may include information related to Service Operation Points associated with different Network Slices. +5. The 5GMS-Aware Application initiates a media streaming session with the 5GMS Client at reference point M6. The 5GMS Client uses an OS-specific UE-internal API to request a network connection for use at reference points M5 (step 10) and M4 (step 11). + +NOTE 2: If the 5GMS-Aware Application is aware about Network Slices, the 5GMS-Aware Application may explicitly indicate the Network Slice to use as part of its request for a network connection. In this case, the following step is skipped. + +6. Based on the OS App Id configured for the 5GMS-Aware Application in step 1, the UE Operating System enables selection of the appropriate Network Slice using the traffic descriptor information inside the currently configured URSP rules. + +NOTE 3: If multiple network slices are provided for the same traffic descriptor, the precedence information in the route selection descriptor is used to select the appropriate Network Slice. + +7. The UE Operating System checks whether a PDU Session already exists in the selected Network Slice and, if so, selects this PDU Session for further interaction with the media streaming endpoints (steps 10 and 11). + +8. Alternatively, if no PDU Session exists in the Network Slice, the UE Operating System creates a PDU Session using the UE-requested PDU Session establishment procedure specified in clause 4.3.2.2 of TS 23.502 [15]. + +NOTE 4: See table A-1 in TS 23.503 [16] for an example of this procedure. + +NOTE 5: According to clause 4.2.2.2 of TS 24.526 [41], the mechanisms used by the UE Operating System to check for the existence of a PDU Session in the selected Network Slice and to establish a new PDU Session if needed are up to UE implementation. + +9. Once the PDU Session is available, the 5GMS Client interacts with DNS system to resolve the IP address of the 5GMS AF and 5GMS AS instances. + +10. The 5GMS Client interacts with the 5GMS AF for media session handling procedures as specified in clause 11 of TS 26.512 [21]. + +11. The 5GMS Client interacts with the 5GMS AS for media streaming as specified in clause 10 of TS 26.512 [21]. + +### 6.7.3 Conclusions + +This Key Issue studied application bootstrapping onto a Network Slice based on application information provisioned by the 5GMS Application Provider and the configuration information in the 5GMS-Aware Application. The application information provisioned by the 5GMS Application Provider is used by the 5GMS AF to provide application guidance for URSP determination in the 5G System. The configuration in the 5GMS-Aware Application and the currently configured URSP rules help the UE Operating System select the appropriate Network Slice for routing application traffic. + +The following is recommended for stage 2: + +- The Key Issue description and candidate solution in clauses 6.7.1 and 6.7.2 respectively of the present document be included as an informative annex to TS 26.501 [20] as guidance for implementations. + +# --- 7 Potential requirements + +The following topics for further study are identified: + +1. Impact to 5G Media Streaming procedures and data model definitions in TS 26.510 [42] based on specification progress related to Network Slice replacement. + +# --- 8 Conclusions and recommendations + +Network slicing is one of the key features of 5G which allows Mobile Network Operators to provision logical networks to serve a specific service or service category, or to serve customers with specific service requirements. Network slicing standardization has progressed in various different 3GPP Working Groups. Specification related to this feature includes architecture, orchestration and management, network resource models, capability management and exposure. The Key Issues studied in the present document point to a need to extend the 5GMS architecture in order to take advantage of network slicing when delivering 5G Media Streaming services. + +The present document provides an overview of network slicing architecture and aspects related to slice orchestration and management as well as network slice capability exposure. It briefly describes different network slice management options such as operator-managed network slicing and third-party-managed network slicing. The present document also collects a set of use cases for running 5G Media Streaming services in one or more network slices, and describes a number of collaboration scenarios for exploiting network slicing capabilities within the 5GMS architecture. It also documents key issues and candidate solutions related to service provisioning, moving media flows to other network slices, and bootstrapping application invocation on a network slice. + +It is recommended that: + +1. The use cases and collaboration scenarios for network slicing documented in clauses 5.3 and 5.4 respectively be included in an informative annex to TS 26.501 [20]. +2. The changes to the *PolicyTemplate* resource data model definition described in clause 6.1.2.1 be implemented into TS 26.510 [42] to support Policy Template provisioning for a plurality of Network Slices and/or Data Networks. +3. The Key Issue description and corresponding candidate solution on bootstrapping application invocation on a Network Slice documented in clause 6.7 of the present document be included as an informative clause or annex to TS 26.501 [20] as guidance for implementations. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------------------------------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-07 | SA4#120e | S4-221055 | | | | Initial version | 0.1.0 | +| 2022-08 | SA4#120e | S4-221173 | | | | S4-221132: Overview of Network slicing feature and capabilities
S4-221133: Collaboration Scenarios with Network Slicing
S4-221139: Network Slicing in SA2 | 0.2.0 | +| 2022-11 | SA4-e (AH)
MBS SWG
post 120-e | S4-221601 | | | | S4a1221381: [FS_MS_NS_Ph2] Architecture sketches | 0.3.0 | +| 2023-02 | SA4#122 | S4-230339 | | | | S4-230333: Clarification on traffic migration to different network slices.
S4-230336: [FS_MS_NS_Ph2] Network Slice Service Continuity
S4-230337: [FS_MS_NS_Ph2] Use cases for Network Slicing and Architecture Assumptions
S4-230338: [FS_MS_NS_Ph2] Key Issues on service provisioning and dynamic policy | 0.4.0 | +| 2023-04 | SA4#123-e | S4-230597 | | | | S4-230679: [FS_MS_NS_Ph2] Candidate Solution for Key Issue #1: Service Provisioning | 0.5.0 | +| 2023-08 | SA4#125 | S4-231555 | | | | S4-231486: [FS_MS_NS_Ph2] Key Issue on Bootstrapping Application Invocation on a Network Slice
S4-231487: [FS_MS_NS_Ph2] Collaboration Options and Network Slicing Scenarios | 0.6.0 | +| 2023-09 | SA#101 | | | | | Version 1.0.0 created by MCC | 1.0.0 | +| 2023-11 | SA4#126 | S4-231852 | | | | S4-232049: [FS_MS_NS_Ph2] pCR on Conclusions and recommendations
S4-231851: [FS_MS_NS_Ph2] Way forward on network slice replacement | 1.1.0 | +| 2023-12 | SA#102 | SP-231293 | | | | Version 2.0.0 created by MCC | 2.0.0 | +| 2023-12 | SA#102 | | | | | Approved at TSG SA#102 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38106/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/38_series/38106/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bb360f67117a3affb832a7a474aeb6a49bb6341 --- /dev/null +++ b/marked/Rel-18/38_series/38106/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cc828ff2c0ae4ab0211232e223010d1431437706920a689958a3395184c3228 +size 50299 diff --git a/marked/Rel-18/38_series/38106/4a6781ac37759896da5d1eb6a04dae34_img.jpg b/marked/Rel-18/38_series/38106/4a6781ac37759896da5d1eb6a04dae34_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..637c8d83969b3a25cb943d3379bac1181455e16c --- /dev/null +++ b/marked/Rel-18/38_series/38106/4a6781ac37759896da5d1eb6a04dae34_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb00ae9b25924e5adf4bb81c1a3c1af6ea9cab8de5926b6864974d1ade5594e7 +size 53241 diff --git a/marked/Rel-18/38_series/38106/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38106/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11e355699bfc55f0e010153341e4b732c03c8885 --- /dev/null +++ b/marked/Rel-18/38_series/38106/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08b325c5955cf918d262cccaa43f253e251a37f560fe142fe790a18f3c936531 +size 9902 diff --git a/marked/Rel-18/38_series/38106/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/Rel-18/38_series/38106/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a61df81407cd5ad2591d8d838530db9278e46e61 --- /dev/null +++ b/marked/Rel-18/38_series/38106/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b117ee340383dcd6ce29233112e5e952f9651edd938da99948096f393cea1209 +size 22512 diff --git a/marked/Rel-18/38_series/38106/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38106/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b67fd5c2cfe5e20b0875d1eab864387c2fc0b41 --- /dev/null +++ b/marked/Rel-18/38_series/38106/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb9b331598f342cca429895c8182e736523f43773fdfa20e10ea5ba68b05324c +size 5428 diff --git a/marked/Rel-18/38_series/38106/6677c55d7b1a3dcd7ca191501eda544b_img.jpg b/marked/Rel-18/38_series/38106/6677c55d7b1a3dcd7ca191501eda544b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b29a142b69dd14cde0c188dc8f3599ae18a46cd --- /dev/null +++ b/marked/Rel-18/38_series/38106/6677c55d7b1a3dcd7ca191501eda544b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b13ea80ffe7ed19ff67d5914c2284667d30433f74ffb8c2b6ce321407d75c330 +size 54650 diff --git a/marked/Rel-18/38_series/38106/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/38_series/38106/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2062c5af56e1914724e43b53fd22bf8375acf829 --- /dev/null +++ b/marked/Rel-18/38_series/38106/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4e317155dd0659f0b3025c60261a7a173ee0d6edd0d83473f67cde7bcc4bcde +size 82800 diff --git a/marked/Rel-18/38_series/38106/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-18/38_series/38106/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6badfa5fbeabeb1c9fbab761ae8b7a8b2abfe9ae --- /dev/null +++ b/marked/Rel-18/38_series/38106/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492ef82356f2c34d75112f736a20f3e20d8ef94aed926d9e18ee0e25e010c94d +size 82714 diff --git a/marked/Rel-18/38_series/38106/b560268ea8f6526970f23f0da225b099_img.jpg b/marked/Rel-18/38_series/38106/b560268ea8f6526970f23f0da225b099_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80ca009bd2a28fb463f4e998b44eb7bb107dce41 --- /dev/null +++ b/marked/Rel-18/38_series/38106/b560268ea8f6526970f23f0da225b099_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:231290a4758c02dea78b0f30b9c3a6820fd4d9a0ea82dbf3b03ffc530865b613 +size 63780 diff --git a/marked/Rel-18/38_series/38106/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-18/38_series/38106/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5013e068cbbaaf4a3024d6dd092a99a78d76856 --- /dev/null +++ b/marked/Rel-18/38_series/38106/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97825dd61d4266797e389f19405f0f485866b1d7be57b86bea1a19cc87421923 +size 42330 diff --git a/marked/Rel-18/38_series/38106/raw.md b/marked/Rel-18/38_series/38106/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8ab892752a8e0a655120a865eba199d3e9918cdb --- /dev/null +++ b/marked/Rel-18/38_series/38106/raw.md @@ -0,0 +1,5314 @@ + + +# 3GPP TS 38.106 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR Repeater Radio Transmission and Reception (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, black font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------|----| +| Foreword..... | 13 | +| 1 Scope..... | 15 | +| 2 References..... | 15 | +| 3 Definitions of terms, symbols and abbreviations..... | 16 | +| 3.1 Terms..... | 16 | +| 3.2 Symbols..... | 19 | +| 3.3 Abbreviations..... | 20 | +| 4 General..... | 20 | +| 4.1 Relationship between Minimum Requirements and Test Requirements..... | 20 | +| 4.2 Conducted and radiated requirement reference points..... | 21 | +| 4.2.1 Repeater type 1-C ..... | 21 | +| 4.2.1A Network controlled Repeater type 1-C..... | 21 | +| 4.2.1B Network controlled Repeater type 1-H..... | 22 | +| 4.2.2 Repeater type 2-O ..... | 23 | +| 4.2.2A Network controlled Repeater type 2-O..... | 24 | +| 4.3 Repeater classes..... | 25 | +| 4.3.1 Repeater class for downlink..... | 25 | +| 4.3.2 Repeater class for uplink..... | 26 | +| 4.3A Network controlled repeater classes..... | 26 | +| 4.3A.1 Network controlled repeater class for downlink..... | 26 | +| 4.3A.2 Network controlled repeater class for uplink..... | 26 | +| 4.4 Regional requirements..... | 27 | +| 4.5 Applicability of requirements..... | 28 | +| 4.6 Requirements for contiguous and non-contiguous spectrum ..... | 29 | +| 4.7 Requirements for repeater capable of multi-band operation..... | 29 | +| 5 Operating bands..... | 30 | +| 5.1 General..... | 30 | +| 5.2 Operating bands..... | 30 | +| 5.3 Channel arrangement..... | 31 | +| 5.3.1 Channel raster..... | 31 | +| 5.3.1.1 NR-ARFCN and channel raster..... | 31 | +| 5.3.1.2 Channel raster entries for each operating band ..... | 31 | +| 5.3.1.3 Channel raster to resource element mapping..... | 31 | +| 5.3.2 Synchronization raster..... | 31 | +| 5.3.2.1 Synchronization raster and numbering..... | 31 | +| 5.3.2.2 Synchronization raster entries for each operating band..... | 31 | +| 5.3.2.3 Synchronization raster to synchronization block resource element mapping..... | 31 | +| 5.3.3 Channel spacing..... | 32 | +| 5.3.4 TX-RX frequency separation..... | 32 | +| 5.4 NCR-MT channel bandwidth..... | 33 | + +| | | | +|-----------|------------------------------------------------------------------|----| +| 5.4.1 | General..... | 33 | +| 5.4.2 | Transmission bandwidth configuration..... | 33 | +| 5.4.3 | Minimum guardband and transmission bandwidth configuration..... | 33 | +| 5.4.4 | RB alignment..... | 34 | +| 5.4.5 | NCR-MT channel bandwidth per operating band..... | 34 | +| 6 | Conducted characteristics..... | 34 | +| 6.1 | General..... | 34 | +| 6.2 | Repeater output power..... | 34 | +| 6.2.1 | General..... | 34 | +| 6.2.2 | Minimum requirement for RF repeater..... | 35 | +| 6.2.3 | Minimum requirement for NCR..... | 36 | +| 6.2.3.1 | Minimum requirement for NCR-Fwd..... | 36 | +| 6.2.3.1.1 | Minimum requirement for NCR-Fwd type 1-C..... | 36 | +| 6.2.3.1.2 | Minimum requirement for NCR-Fwd type 1-H..... | 36 | +| 6.2.3.2 | Minimum requirement for NCR-MT..... | 36 | +| 6.2.3.2.1 | General..... | 36 | +| 6.2.3.2.2 | Minimum requirement for NCR-MT type 1-C and NCR-MT type 1-H..... | 37 | +| 6.3.3 | Minimum requirement for NCR..... | 37 | +| 6.3.3.1 | Minimum requirement for NCR-Fwd..... | 37 | +| 6.3.3.1.1 | Minimum requirement for NCR-Fwd type 1-C..... | 37 | +| 6.3.3.1.2 | Minimum requirement for NCR-Fwd type 1-H..... | 37 | +| 6.3 | Frequency stability..... | 37 | +| 6.3.1 | General..... | 37 | +| 6.3.2 | Minimum requirement for RF repeater..... | 37 | +| 6.3.3 | Minimum requirement for NCR..... | 37 | +| 6.3.3.1 | Minimum requirement for NCR-Fwd..... | 37 | +| 6.3.3.1.1 | Minimum requirement for NCR-Fwd type 1-C..... | 37 | +| 6.3.3.1.2 | Minimum requirement for NCR-Fwd type 1-H..... | 38 | +| 6.4 | Out of band gain..... | 38 | +| 6.4.1 | General..... | 38 | +| 6.4.2 | Minimum requirement for RF repeater..... | 38 | +| 6.4.3 | Minimum requirement for NCR..... | 38 | +| 6.4.3.1 | Minimum requirement for NCR-Fwd..... | 38 | +| 6.4.3.1.1 | Minimum requirement for NCR-Fwd type 1-C..... | 38 | +| 6.4.3.1.2 | Minimum requirement for NCR-Fwd type 1-H..... | 39 | +| 6.5 | Unwanted emissions..... | 39 | +| 6.5.1 | General..... | 39 | +| 6.5.2 | Adjacent Channel Leakage Power Ratio..... | 40 | +| 6.5.2.1 | General..... | 40 | +| 6.5.2.2 | Limits and basic limits ..... | 40 | +| 6.5.2.3 | Minimum requirement for RF repeater ..... | 45 | +| 6.5.2.4 | Minimum requirement for NCR ..... | 45 | +| 6.5.2.4.1 | Minimum requirements for NCR-Fwd..... | 45 | +| 6.5.2.4.2 | Minimum requirement for NCR-MT..... | 46 | + +| | | | +|------------|----------------------------------------------------------------------------------------------|----| +| 6.5.3 | Operating band unwanted emissions..... | 47 | +| 6.5.3.1 | General..... | 47 | +| 6.5.3.2 | Basic limits..... | 49 | +| 6.5.3.2.1 | basic limits for Wide Area repeater type 1-C (Category A)..... | 49 | +| 6.5.3.2.2 | Basic limit for Wide Area repeater type 1-C (Category B)..... | 50 | +| 6.5.3.2.3 | Basic limits for Medium Range repeater type 1-C (Category A and B) for DL..... | 52 | +| 6.5.3.2.4 | Basic limits for Local Area repeater type 1-C (Category A and B)..... | 54 | +| 6.5.3.2.5 | Additional basic limits ..... | 55 | +| 6.5.3.2.6 | Basic limit inside passband with no UL input signal..... | 56 | +| 6.5.3.3 | Minimum requirement for NCR..... | 57 | +| 6.5.3.3.1 | Minimum requirement for NCR-Fwd..... | 57 | +| 6.5.3.3.2 | Minimum requirement for NCR-MT..... | 58 | +| 6.5.4 | Transmitter spurious emissions..... | 59 | +| 6.5.4.1 | General..... | 59 | +| 6.5.4.2 | Basic limits ..... | 59 | +| 6.5.4.2.1 | General transmitter spurious emissions basic limits ..... | 59 | +| 6.5.4.2.2 | Additional spurious emissions basic limits ..... | 60 | +| 6.5.4.2.3 | Co-location with base stations and repeater Nodes..... | 72 | +| 6.5.4.3 | Minimum requirement for RF repeater ..... | 78 | +| 6.5.4.4 | Minimum requirement for NCR ..... | 78 | +| 6.5.4.4.1 | Minimum requirement for NCR-Fwd..... | 78 | +| 6.5.4.4.2 | Minimum requirement for NCR-MT..... | 79 | +| 6.5.5 | Receiver spurious emissions..... | 79 | +| 6.5.5.1 | General..... | 79 | +| 6.5.5.2 | Basic limits..... | 80 | +| 6.5.5.3 | Minimum requirement for RF repeater ..... | 80 | +| 6.5.5.4 | Minimum requirement for NCR ..... | 80 | +| 6.5.5.4.1 | Minimum requirement for NCR-Fwd..... | 80 | +| 6.6 | Repeater Error Vector Magnitude..... | 81 | +| 6.6.1 | Downlink repeater error vector magnitude..... | 81 | +| 6.6.1.1 | General..... | 81 | +| 6.6.1.2 | Minimum requirement for RF repeater ..... | 82 | +| 6.6.1.2A | Minimum requirement for NCR ..... | 82 | +| 6.6.1.2A.1 | Minimum requirement for NCR-Fwd..... | 82 | +| 6.6.1.3 | Repeater EVM frame structure for measurement..... | 82 | +| 6.6.2 | Uplink repeater error vector magnitude..... | 82 | +| 6.6.2.1 | General..... | 82 | +| 6.6.2.2 | Minimum requirement for RF repeater ..... | 83 | +| 6.6.2.3 | Minimum requirement for NCR ..... | 83 | +| 6.6.2.3.1 | Minimum requirement for NCR-Fwd..... | 83 | +| 6.7 | Input intermodulation..... | 83 | +| 6.7.1 | General requirement..... | 83 | +| 6.7.1.1 | General..... | 83 | +| 6.7.1.2 | Minimum requirement for RF repeater ..... | 84 | +| 6.7.1.3 | Minimum requirement for NCR ..... | 84 | + +| | | | +|------------|--------------------------------------------------------|----| +| 6.7.1.3.1 | Minimum requirement for NCR-Fwd..... | 84 | +| 6.7.2 | Co-location with BS/repeater in other systems..... | 85 | +| 6.7.2.1 | General..... | 85 | +| 6.7.2.2 | Minimum requirement for RF repeater ..... | 85 | +| 6.7.2.3 | Minimum requirement for NCR ..... | 86 | +| 6.7.2.3.1 | Minimum requirement for NCR-Fwd..... | 86 | +| 6.7.3 | Co-existence with other systems..... | 86 | +| 6.7.3.1 | General..... | 86 | +| 6.7.3.2 | Minimum requirement for RF repeater ..... | 86 | +| 6.7.3.3 | Minimum requirement for NCR ..... | 87 | +| 6.7.3.3.1 | Minimum requirement for NCR-Fwd..... | 87 | +| 6.8 | Output intermodulation..... | 87 | +| 6.8.3 | Minimum requirements for NCR ..... | 89 | +| 6.8.3.1 | Minimum requirements for NCR-Fwd..... | 89 | +| 6.8.3.1.1 | Minimum requirements for NCR-Fwd type 1-C..... | 89 | +| 6.8.3.1.2 | Additional requirements for NCR-Fwd type 1-C..... | 89 | +| 6.8.3.1.3 | Minimum requirements for NCR-Fwd type 1-H ..... | 89 | +| 6.8.3.1.4 | Additional requirements for NCR-Fwd type 1-H..... | 89 | +| 6.9 | Adjacent Channel Rejection Ratio (ACRR)..... | 89 | +| 6.9.1 | General..... | 89 | +| 6.9.2 | Minimum Requirements for RF repeater ..... | 90 | +| 6.9.3 | Minimum Requirements for NCR ..... | 91 | +| 6.9.3.1 | Minimum requirements for NCR-Fwd..... | 91 | +| 6.9.3.1.1 | Minimum requirements for NCR-Fwd type 1-C..... | 91 | +| 6.9.3.1.2 | Minimum Requirements for NCR-Fwd type 1-H ..... | 91 | +| 6.10 | Transmit ON/OFF power..... | 92 | +| 6.10.1 | Transmitter OFF power..... | 92 | +| 6.10.1.1 | General..... | 92 | +| 6.10.1.2 | Minimum requirement for RF repeater ..... | 92 | +| 6.10.1.3 | Minimum requirement for NCR ..... | 92 | +| 6.10.1.3.1 | Minimum requirement for NCR Fwd..... | 92 | +| 6.10.2 | Transmitter transient period..... | 92 | +| 6.10.2.1 | General..... | 92 | +| 6.10.2.2 | Minimum requirement for RF repeater ..... | 93 | +| 6.10.2.3 | Minimum requirement for NCR ..... | 93 | +| 6.10.2.3.1 | Minimum requirement for NCR-Fwd..... | 93 | +| 6.11 | Output power dynamics..... | 94 | +| 6.11.1 | General..... | 94 | +| 6.11.2 | Transmit OFF power for NCR-MT..... | 94 | +| 6.11.3 | Transmit ON/OFF time mask for NCR-MT..... | 94 | +| 6.11.4 | Power control for NCR-MT..... | 94 | +| 6.12 | Transmit signal quality..... | 94 | +| 6.12.1 | General..... | 94 | +| 6.12.2 | Frequency error requirements for NCR-MT..... | 95 | +| 6.12.3 | Transmit modulation quality..... | 95 | + +| | | | +|-----------|--------------------------------------------------------------------|-----| +| 6.13 | Transmit intermodulation..... | 95 | +| 6.13.1 | General..... | 95 | +| 6.13.2 | Minimum requirements for NCR-MT..... | 95 | +| 6.14 | General..... | 95 | +| 6.15 | Diversity characteristics..... | 96 | +| 6.16 | Conducted reference sensitivity..... | 96 | +| 6.16.1 | NCR-MT reference sensitivity level..... | 96 | +| 6.16.1.1 | General..... | 96 | +| 6.16.1.2 | Minimum requirements for NCR-MT type 1-C and 1-H ..... | 96 | +| 6.17 | Conducted maximum input level..... | 97 | +| 6.18 | Conducted adjacent channel selectivity..... | 97 | +| 6.18.1 | Adjacent Channel Selectivity (ACS)..... | 97 | +| 6.18.1.1 | General..... | 97 | +| 6.18.1.2 | Minimum requirement for NCR-MT type 1-C ..... | 97 | +| 6.18.1.3 | Minimum requirement for NCR-MT type 1-H ..... | 97 | +| 6.19 | Conducted blocking characteristics..... | 97 | +| 6.19.1 | General..... | 97 | +| 6.19.2 | Minimum requirement for NCR-MT type 1-C..... | 97 | +| 6.19.3 | Minimum requirement for NCR-MT type 1-H..... | 98 | +| 6.20 | Conducted spurious response..... | 98 | +| 6.20.1 | General..... | 98 | +| 6.20.2 | Minimum requirements for NCR-MT type 1-C and NCR-MT type 1-H..... | 98 | +| 6.21 | Conducted intermodulation characteristics..... | 98 | +| 6.21.1 | General..... | 98 | +| 6.21.2 | Minimum requirement for NCR type 1-C..... | 98 | +| 6.21.3 | Minimum requirement for NCR type 1-H..... | 99 | +| 6.22 | Conducted spurious emissions..... | 99 | +| 6.22.1 | General..... | 99 | +| 6.22.2 | Minimum requirements for NCR-MT type 1-C and type 1-H ..... | 99 | +| 7 | Radiated characteristics..... | 100 | +| 7.1 | General..... | 100 | +| 7.2 | OTA output power..... | 100 | +| 7.2.1 | General..... | 100 | +| 7.2.2 | Minimum requirement for NR repeater..... | 102 | +| 7.2.3 | Minimum requirement for NCR..... | 102 | +| 7.2.3.1 | Minimum requirement for NCR-MT..... | 102 | +| 7.2.3.1.1 | Minimum requirement for NCR-MT type 1-H..... | 102 | +| 7.2.3.1.2 | Minimum requirement for NCR-MT type 2-O..... | 102 | +| 7.2.3.2 | Minimum requirement for NCR-Fwd..... | 102 | +| 7.2.3.2.1 | Minimum requirement for NCR-Fwd type 2-O..... | 102 | +| 7.3 | OTA frequency stability..... | 103 | +| 7.3.1 | General..... | 103 | +| 7.3.2 | Minimum requirement for NR repeater..... | 103 | +| 7.3.3 | Minimum requirement for NCR..... | 103 | + +| | | | +|-----------|-------------------------------------------------------------------|-----| +| 7.3.3.1 | Minimum requirement for NCR-Fwd..... | 103 | +| 7.3.3.1.1 | Minimum requirement for NCR-Fwd type 2-O..... | 103 | +| 7.4 | OTA out of band gain..... | 103 | +| 7.4.1 | General..... | 103 | +| 7.4.2 | Minimum requirement for NR repeater..... | 104 | +| 7.4.3 | Minimum requirement for NCR..... | 104 | +| 7.4.3.1 | Minimum requirement for NCR-Fwd..... | 104 | +| 7.4.3.1.1 | Minimum requirement for NCR-Fwd type 2-O..... | 104 | +| 7.5 | OTA unwanted emissions..... | 104 | +| 7.5.1 | General..... | 104 | +| 7.5.2 | OTA Adjacent Channel Leakage Power Ratio (ACLR)..... | 105 | +| 7.5.2.1 | General..... | 105 | +| 7.5.2.2 | Minimum requirement for NR Repeater ..... | 105 | +| 7.5.2.3 | Minimum requirement for NCR..... | 109 | +| 7.5.2.3.1 | Minimum requirement for NCR-Fwd..... | 109 | +| 7.5.2.3.2 | Minimum requirement for NCR-MT..... | 109 | +| 7.5.3 | OTA operating band unwanted emissions..... | 109 | +| 7.5.3.1 | General..... | 109 | +| 7.5.3.2 | Minimum requirement for NR repeater..... | 109 | +| 7.5.3.2.1 | General..... | 109 | +| 7.5.3.2.2 | OTA operating band unwanted emission limits (Category A)..... | 110 | +| 7.5.3.2.3 | OTA operating band unwanted emission limits (Category B)..... | 111 | +| 7.5.3.2.4 | Additional OTA operating band unwanted emission requirements..... | 111 | +| 7.5.3.3 | Minimum requirement for NCR..... | 112 | +| 7.5.3.3.1 | Minimum requirement for NCR-Fwd..... | 112 | +| 7.5.3.3.2 | Minimum requirement for NCR-MT..... | 112 | +| 7.5.4 | OTA transmitter spurious emissions..... | 112 | +| 7.5.4.1 | General..... | 112 | +| 7.5.4.2 | Minimum requirement for NR repeater ..... | 112 | +| 7.5.4.2.1 | General..... | 112 | +| 7.5.4.2.2 | General OTA transmitter spurious emissions requirements..... | 113 | +| 7.5.4.2.3 | Additional OTA transmitter spurious emissions requirements..... | 114 | +| 7.5.4.3 | Minimum requirement for NCR ..... | 114 | +| 7.5.4.3.1 | Minimum requirement for NCR-Fwd..... | 114 | +| 7.5.4.3.2 | Minimum requirement for NCR-MT..... | 114 | +| 7.5.5 | OTA receiver spurious emissions..... | 115 | +| 7.5.5.1 | General..... | 115 | +| 7.5.5.2 | Minimum requirement for NR repeater ..... | 115 | +| 7.5.5.3 | Minimum requirement for NCR ..... | 116 | +| 7.5.5.3.1 | Minimum requirement for NCR-Fwd..... | 116 | +| 7.6 | OTA Repeater Error Vector Magnitude..... | 116 | +| 7.6.1 | Downlink repeater error vector magnitude..... | 116 | +| 7.6.1.1 | General..... | 116 | +| 7.6.1.2 | Minimum requirement for NR repeater..... | 117 | +| 7.6.1.2A | Minimum requirement for NCR..... | 117 | + +| | | | +|------------|---------------------------------------------------|-----| +| 7.6.1.2A.1 | Minimum requirement for NCR-Fwd..... | 117 | +| 7.6.1.3 | Repeater EVM frame structure for measurement..... | 117 | +| 7.6.2 | Uplink repeater error vector magnitude..... | 117 | +| 7.6.2.1 | General..... | 117 | +| 7.6.2.2 | Minimum requirement for NR repeater..... | 118 | +| 7.6.2.3 | Minimum requirement for NCR..... | 119 | +| 7.6.2.3.1 | Minimum requirement for NCR-Fwd..... | 119 | +| 7.7 | OTA input intermodulation..... | 119 | +| 7.7.1 | General..... | 119 | +| 7.7.2 | Minimum requirement for NR repeater..... | 119 | +| 7.7.3 | Minimum requirement for NCR..... | 120 | +| 7.7.3.1 | Minimum requirement for NCR-Fwd..... | 120 | +| 7.7.3.1.1 | Minimum requirement for NCR-Fwd type 2-O..... | 120 | +| 7.8 | OTA Adjacent Channel Rejection Ratio (ACRR)..... | 120 | +| 7.8.1 | General..... | 120 | +| 7.8.2 | Minimum Requirements for NR repeater..... | 120 | +| 7.8.3 | Minimum Requirements for NCR..... | 121 | +| 7.8.3.1 | Minimum Requirements for NCR-Fwd..... | 121 | +| 7.8.3.1.1 | Minimum Requirements for NCR-Fwd type 2-O..... | 121 | +| 7.9 | OTA transmit ON/OFF power..... | 122 | +| 7.9.1 | General..... | 122 | +| 7.9.2 | OTA transmitter OFF power..... | 122 | +| 7.9.2.1 | General..... | 122 | +| 7.9.2.2 | Minimum requirement for NR repeater..... | 122 | +| 7.9.2.3 | Minimum requirement for NCR..... | 122 | +| 7.9.2.3.1 | Minimum requirement for NCR-Fwd..... | 122 | +| 7.9.2.3.2 | Minimum requirement for NCR-MT..... | 122 | +| 7.9.3 | OTA transient period..... | 123 | +| 7.9.3.1 | General..... | 123 | +| 7.9.3.2 | Minimum requirement for NR repeater..... | 123 | +| 7.9.3.3 | Minimum requirement for NCR..... | 124 | +| 7.9.3.3.1 | Minimum requirement for NCR-Fwd..... | 124 | +| 7.9.3.3.2 | Minimum requirement for NCR-MT..... | 124 | +| 7.10 | OTA output power dynamics..... | 124 | +| 7.10.1 | General..... | 124 | +| 7.10.2 | Minimum requirement for NCR-MT..... | 124 | +| 7.11 | OTA transmit signal quality..... | 124 | +| 7.11.1 | General..... | 124 | +| 7.11.2 | Frequency error requirements for NCR-MT..... | 125 | +| 7.11.2.1 | Minimum requirement for NCR-MT type 2-O..... | 125 | +| 7.11.3 | Transmit modulation quality..... | 125 | +| 7.11.3.1 | Minimum requirement for NCR-MT type 2-O..... | 125 | +| 7.12 | Diversity characteristics..... | 125 | +| 7.12.1 | General..... | 125 | +| 7.12.2 | Minimum requirement for NCR-MT..... | 125 | + +| | | | +|------------|-------------------------------------------------|-----| +| 7.13 | OTA reference sensitivity..... | 125 | +| 7.13.1 | General..... | 125 | +| 7.13.2 | Minimum requirement for NCR-MT type 2-O..... | 125 | +| 7.14 | OTA maximum input level..... | 125 | +| 7.14.1 | General..... | 125 | +| 7.14.2 | Minimum requirement for NCR-MT type 2-O..... | 126 | +| 7.15 | OTA adjacent channel selectivity..... | 126 | +| 7.15.1 | General..... | 126 | +| 7.15.1 | Minimum requirement for NCR-MT type 2-O..... | 126 | +| 7.16 | OTA blocking characteristics..... | 126 | +| 7.16.1 | General..... | 126 | +| 7.16.2 | Minimum requirement for NCR-MT type 2-O..... | 126 | +| 7.17 | OTA spurious emissions..... | 127 | +| 7.17.1 | General..... | 127 | +| 7.17.2 | Minimum requirement for NCR-MT type 2-O..... | 127 | +| 8 | (Reserved)..... | 127 | +| 9 | (Reserved)..... | 127 | +| 10 | NCR-MT RRC_CONNECTED state mobility..... | 127 | +| 10.1 | RRC Connection Mobility Control for NCR-MT..... | 127 | +| 10.1.1 | SA: RRC Re-establishment..... | 127 | +| 10.1.1.1 | Introduction..... | 127 | +| 10.1.1.2 | Requirements..... | 128 | +| 10.1.1.2.1 | NCR-MT Re-establishment delay requirement..... | 128 | +| 10.1.2 | Random access..... | 129 | +| 10.1.2.1 | Introduction..... | 129 | +| 10.1.2.2 | Requirements for 4-step RA type..... | 129 | +| 10.1.2.2.1 | Contention based random access..... | 130 | +| 10.1.2.2.2 | Non-Contention based random access..... | 131 | +| 10.2 | Timing..... | 132 | +| 10.2.1 | NCR-MT transmit timing..... | 132 | +| 10.2.1.1 | Introduction..... | 132 | +| 10.2.1.2 | Requirements..... | 132 | +| 10.2.1.2.1 | Gradual timing adjustment..... | 133 | +| 10.2.2.1 | Introduction..... | 134 | +| 10.2.2.2 | Requirements..... | 134 | +| 10.2.3 | NCR-MT timing advance..... | 134 | +| 10.2.3.1 | Introduction..... | 134 | +| 10.2.3.2 | Requirements..... | 135 | +| 10.2.3.2.1 | Timing Advance adjustment delay..... | 135 | +| 10.2.3.2.2 | Timing Advance adjustment accuracy..... | 135 | +| 10.3 | Signalling Characteristics for NCR-MT..... | 135 | +| 10.3.1 | Radio Link Monitoring..... | 135 | +| 10.3.1.1 | Introduction..... | 135 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------|-----| +| 10.3.1.2 | Requirements for SSB based radio link monitoring..... | 136 | +| 10.3.1.2.1 | Introduction..... | 136 | +| 10.3.1.2.2 | Minimum requirement..... | 137 | +| 10.3.1.2.3 | Measurement restrictions for SSB based RLM..... | 138 | +| 10.3.1.3 | Requirements for CSI-RS based radio link monitoring..... | 139 | +| 10.3.1.3.1 | Introduction..... | 139 | +| 10.3.1.3.2 | Minimum requirement..... | 139 | +| 10.3.1.3.3 | Measurement restrictions for CSI-RS based RLM..... | 141 | +| 10.3.1.4 | Minimum requirement for NCR-MT turning off the transmitter..... | 142 | +| 10.3.1.5 | Minimum requirement for L1 indication..... | 142 | +| 10.3.1.6 | Scheduling availability of NCR-MT during radio link monitoring..... | 142 | +| 10.3.1.6.1 | Scheduling availability of NCR-MT performing radio link monitoring with a same subcarrier spacing as PDSCH/PDCCH on FR1..... | 142 | +| 10.3.1.6.2 | Scheduling availability of NCR-MT performing radio link monitoring with a different subcarrier spacing than PDSCH/PDCCH on FR1..... | 142 | +| 10.3.1.6.3 | Scheduling availability of NCR-MT performing radio link monitoring on FR2-1..... | 142 | +| 10.3.2 | Link Recovery Procedure..... | 143 | +| 10.3.2.1 | Introduction..... | 143 | +| 10.3.2.2 | Requirements for SSB based beam failure detection..... | 144 | +| 10.3.2.2.1 | Introduction..... | 144 | +| 10.3.2.2.2 | Minimum requirement..... | 144 | +| 10.3.2.2.3 | Measurement restriction for SSB based beam failure detection..... | 145 | +| 10.3.2.3 | Requirements for CSI-RS based beam failure detection..... | 146 | +| 10.3.2.3.1 | Introduction..... | 146 | +| 10.3.2.3.2 | Minimum requirement..... | 146 | +| 10.3.2.3.3 | Measurement restrictions for CSI-RS based beam failure detection..... | 147 | +| 10.3.2.4 | Minimum requirement for L1 indication..... | 148 | +| 10.3.2.5 | Requirements for SSB based candidate beam detection..... | 149 | +| 10.3.2.5.1 | Introduction..... | 149 | +| 10.3.2.5.2 | Minimum requirement..... | 149 | +| 10.3.2.5.3 | Measurement restriction for SSB based candidate beam detection..... | 150 | +| 10.3.2.6 | Requirements for CSI-RS based candidate beam detection..... | 150 | +| 10.3.2.6.1 | Introduction..... | 150 | +| 10.3.2.6.2 | Minimum requirement..... | 151 | +| 10.3.2.6.3 | Measurement restriction for CSI-RS based candidate beam detection..... | 152 | +| 10.3.2.7 | Scheduling availability of NCR-MT during beam failure detection..... | 152 | +| 10.3.2.7.1 | Scheduling availability of NCR-MT performing beam failure detection with a same subcarrier spacing as PDSCH/PDCCH on FR1..... | 152 | +| 10.3.2.7.2 | Scheduling availability of NCR-MT performing beam failure detection with a different subcarrier spacing than PDSCH/PDCCH on FR1..... | 153 | +| 10.3.2.7.3 | Scheduling availability of NCR-MT performing beam failure detection on FR2-1..... | 153 | +| 10.3.2.8 | Scheduling availability of NCR-MT during candidate beam detection..... | 153 | +| 10.3.2.8.1 | Scheduling availability of NCR-MT performing L1-RSRP measurement with a same subcarrier spacing as PDSCH/PDCCH on FR1..... | 154 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------| +| 10.3.2.8.2 | Scheduling availability of NCR-MT performing L1-RSRP measurement with a different subcarrier spacing than PDSCH/PDCCH on FR1..... | 154 | +| 10.3.2.8.3 | Scheduling availability of NCR-MT performing L1-RSRP measurement on FR2-1..... | 154 | +| Annex A (normative): | Environmental requirements for the Repeater equipment..... | 155 | +| Annex B (informative): | Change history..... | 156 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +**shall** indicates a mandatory requirement to do something + +**shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +**should** indicates a recommendation to do something + +**should not** indicates a recommendation not to do something + +**may** indicates permission to do something + +**need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +**can** indicates that something is possible + +**cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +# 1 Scope + +The present document establishes the minimum RF characteristics of NR Repeater and network controlled repeater. For network controlled repeater (NCR), requirements for NCR-Fwd and NCR-MT apply. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [3] 3GPP TR 25.942: "RF system scenarios". +- [4] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions". +- [5] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [6] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications – 2000". +- [7] 3GPP TS 38.115-1: "NR; Repeater conformance testing - Part 1: Conducted conformance testing". +- [8] 3GPP TS 38.115-2: "NR; Repeater conformance testing - Part 2: Radiated conformance testing". +- [9] ERC Recommendation 74-01, "Unwanted emissions in the spurious domain". +- [10] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [11] Void +- [12] Void +- [13] 3GPP TS 38.101-1: "NR User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [14] 3GPP TS 38.101-2: "NR User Equipment (UE) radio transmission and reception: Part 2: Range 2 Standalone". +- [15] Void + +- [16] Void +- [17] Void +- [18] Void +- [19] 3GPP TS 38.213: “NR; Physical layer procedures for control”. +- [20] 3GPP TS 36.104: “Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception” +- [21] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [22] 3GPP TS 38.174: "NR; Integrated Access and Backhaul (IAB) radio transmission and reception". +- [23] 3GPP TS 38.331: “NR; Radio Resource Control (RRC); Protocol specification”. +- [24] 3GPP TS 38.213: “NR; Physical layer procedures for control”. +- [25] 3GPP TS 38.321: “NR; Medium Access Control (MAC) protocol specification”. +- [26] 3GPP TS 38.211: “NR; Physical channels and modulation”. +- [27] 3GPP TS 38.306: “NR; User Equipment (UE) radio access capabilities”. + +--- + +## 3 Definitions of terms, symbols and abbreviations + +### 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Antenna connector:** connector at the conducted interface of the *repeater type 1-C* + +**Beam:** beam (of the antenna) is the main lobe of the radiation pattern of an *antenna array* + +**Beam centre direction:** direction equal to the geometric centre of the half-power contour of the beam + +**Beam direction pair:** data set consisting of the *beam centre direction* and the related *beam peak direction* + +**Beam peak direction:** direction where the maximum EIRP is found + +**Beamwidth:** beam which has a half-power contour that is essentially elliptical, the half-power beamwidths in the two pattern cuts that respectively contain the major and minor axis of the ellipse + +**directional requirement:** requirement which is applied in a specific direction within the *OTA coverage range*. + +**Equivalent isotropic radiated power:** equivalent power radiated from an isotropic directivity device producing the same field intensity at a point of observation as the field intensity radiated in the direction of the same point of observation by the discussed device + +**Fractional bandwidth:** *fractional bandwidth* FBW is defined as + +**gap between passbands:** frequency gap between two consecutive passbands that belong to the same *operating band*, where the RF requirements in the gap are based on co-existence for un-coordinated operation + +**Inter-passband gap:** The frequency gap between two supported consecutive *passbands* that belong to different operating bands. + +**Maximum passband output power:** mean power level measured per *passband* at the *antenna connector*, during the *transmitter ON state* in a specified reference condition + +**Maximum passband TRP output power:** mean power level measured per passband during the *transmitter ON state* in a specified reference condition and corresponding to the declared *rated passband TRP output power* ( $P_{\text{rated,p,TRP}}$ ) + +**Measurement bandwidth:** RF bandwidth in which an emission level is specified + +**multi-band connector:** *Antenna Connector* for a *Multi-band repeater*. + +**Multi-band repeater:** *Repeater Type 1-C* whose *antenna connector* is associated with a transmitter and/or receiver that is characterized by the ability to process two or more *passband(s)* in common active RF components simultaneously, where at least one *passband* is configured at a different operating band than the other *passband(s)* and where this different operating band is not a sub-band or superseding-band of another supported operating band + +**Nominal channel bandwidth:** Bandwidth calculated as $\min(100\text{MHz}, \text{BW}_{\text{passband}})$ in FR1 or $\min(400\text{MHz}, \text{BW}_{\text{passband}})$ in FR2. If this bandwidth is not defined for BS channel bandwidth for the operating band, *nominal channel bandwidth* shall be defined as the widest BS channel bandwidth for the operating band which is narrower than $\text{BW}_{\text{passband}}$ . + +**Non-contiguous spectrum:** spectrum consisting of two or more *passbands* separated by *inter-passband gap(s)*. + +**Operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements + +**OTA coverage range:** a common range of directions within which OTA requirements that are neither specified in the *OTA peak directions sets* nor as *TRP requirement* are intended to be met + +**OTA peak directions set:** set(s) of *beam peak directions* within which certain OTA requirements are intended to be met, where all *OTA peak directions set(s)* are subsets of the *OTA coverage range* + +**Passband:** The frequency range in which the repeater operates in with operational configuration, this frequency range can correspond to one or several consecutive nominal channels, if they are not consecutive each subset of channels shall be considered as an individual *passband*, a repeater can have one or several *passbands*, all channels within the *passband(s)* shall belong to a single operator or collaborating operators. + +**passband edge:** Frequency at the edge of the passband + +**Radiated interface boundary:** *operating band* specific radiated requirements reference where the radiated requirements apply + +**Rated beam EIRP:** For a declared beam and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the repeater is declared to radiate at the associated *beam peak direction* during the *transmitter ON state* + +**Rated passband output power:** mean power level associated with a *passband* the manufacturer has declared to be available at the *antenna connector*, during the *transmitter ON state* in a specified reference condition + +**Rated passband TRP output power:** mean power level declared by the manufacturer per passband, that the manufacturer has declared to be available at the RIB during the *transmitter ON state* + +**Rated total output power:** mean power level associated with a particular *operating band* the manufacturer has declared to be available at the *antenna connector*, during the *transmitter ON state* in a specified reference condition + +**Rated total TRP output power:** mean power level associated with a particular *operating band*, that the manufacturer has declared to be available at the RIB during the *transmitter ON state* in a specified reference condition + +**Reference beam direction pair:** Beam direction pair in the reference direction declared by the manufacturer. + +**Repeater type 1-C:** Repeater operating at FR1 with a requirement set consisting only of conducted requirements defined at individual *antenna connectors*. + +**Repeater type 2-O:** Repeater operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB + +**Requirement set:** one of the NR requirements set as defined for *NR repeater* + +**single-band connector:** *Repeater type 1-C antenna connector* supporting operation either in a single *operating band* only, or in multiple *operating bands* but does not meet the conditions for a *multi-band connector*. + +**Sub-band:** A *sub-band* of an operating band contains a part of the uplink and downlink frequency range of the operating band. + +**sub-block:** one contiguous allocated block of spectrum for transmission and reception by the repeater. + +**Superseding-band:** A *superseding-band* of an operating band includes the whole of the uplink and downlink frequency range of the operating band. + +**Total radiated power:** is the total power radiated by the antenna + +NOTE: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations. *Total radiated power* is defined in both the near-field region and the far-field region + +**Transmitter OFF state:** Time period during which the repeater downlink or uplink is not allowed to transmit in the corresponding direction. + +**Transmitter ON state:** Time period during which the repeater is transmitting downlink or uplink signals in the corresponding direction. + +**Transmitter transient period:** Time period during which the repeater is changing from the OFF state to the ON state or vice versa. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BW Config | Transmission bandwidth configuration , where $BW_{Config} = N_{RB} \times SCS \times 12$ | +| BW Nominal | Nominal channel bandwidth | +| BW Passband | Passband bandwidth | +| $\Delta f$ | Separation between the passband edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{max}$ | $f\_offset_{max}$ minus half of the bandwidth of the measuring filter | +| $\Delta f_{OBUE}$ | Maximum offset of the operating band unwanted emissions mask from the operating band edge | +| F DL,low | The lowest frequency of the downlink operating band | +| F DL,high | The highest frequency of the downlink operating band | +| F FBWhigh | Highest supported frequency within supported operating band, for which fractional bandwidth support was declared | +| F FBWlow | Lowest supported frequency within supported operating band, for which fractional bandwidth support was declared | +| F filter | Filter centre frequency | +| F offset,high | Frequency offset from F C,high to the upper passband edge | +| F offset,low | Frequency offset from F C,low to the lower passband edge | +| $f\_offset$ | Separation between the passband edge frequency and the centre of the measuring | +| $f\_offset_{max}$ | The offset to the frequency $\Delta f_{OBUE}$ outside the operating band | +| F step,X | Frequency steps for the OTA transmitter spurious emissions (Category B) | +| F UL,low | The lowest frequency of the uplink operating band | +| F UL,high | The highest frequency of the uplink operating band | +| P EM,n50/n75,ind | Declared emission level for Band n50/n75; ind = a, b | +| P EM,n54,ind | Declared emission level for Band n54; ind = a, b, c, d, e, f | +| P rated,p,AC | Rated passband output power per antenna connector | +| P rated,t,AC | Rated total output power declared per antenna connector | +| P rated,p,EIRP | Rated passband EIRP output power | +| P rated,p,TRP | Rated passband TRP output power declared per RIB | +| P rated,t,TRP | Rated total TRP output power declared per RIB | +| P in,p,AC | Input power intended to produce the maximum rated output power (P rated,p,AC ) at the antenna connector | +| P in,p,EIRP | Input power intended to produce the maximum rated output power (P rated,p,TRP ) at the RIB | +| P rated,out,FBWhigh | The rated output EIRP for the higher supported frequency range within supported operating band , for which fractional bandwidth support was declared | +| P rated,out,FBWlow | The rated output EIRP for the lower supported frequency range within supported operating band , for which fractional bandwidth support was declared | +| P max,p,AC | Maximum passband output power measured per antenna connector | +| P max,p,EIRP | Maximum passband EIRP output power when repeater is configured at the rated passband TRP output power (P rated,p,TRP ) | +| P max,p,TRP | Maximum passband TRP output power measured per RIB | +| W gap | Inter passband Bandwidth gap size | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------------|------------------------------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| AoA | Angle of Arrival | +| BW | Bandwidth | +| CACLR | Cumulative ACLR | +| CP-OFDM | Cyclic Prefix-OFDM | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DL | Downlink | +| EIRP | Effective Isotropic Radiated Power | +| EVM | Error Vector Magnitude | +| FBW | Fractional Bandwidth | +| FR | Frequency Range | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LA | Local Area | +| MR | Medium Range | +| NR | New Radio | +| OBUE | Operating Band Unwanted Emissions | +| OOB | Out-of-band | +| OTA | Over-The-Air | +| QAM | Quadrature Amplitude Modulation | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| TX | Transmitter | +| TRP | Total Radiated Power | +| UL | Uplink | +| WA | Wide Area | + +--- + +## 4 General + +### 4.1 Relationship between Minimum Requirements and Test Requirements + +Conformance to the present specification is demonstrated by fulfilling the test requirements specified in the conformance specification TS 38.115-1 [7] or TS 38.115-2 [8]. + +The minimum requirements given in this specification make no allowance for measurement uncertainty. The test specifications TS 38.115-1 [7] and TS 38.115-2 [8] define test tolerances. These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +The measurement results returned by the test system are compared - without any modification - against the test requirements as defined by the shared risk principle. + +The shared risk principle is defined in recommendation ITU-R M.1545 [6]. + +## 4.2 Conducted and radiated requirement reference points + +### 4.2.1 Repeater type 1-C + +For *repeater type 1-C*, the requirements are applied at the repeater *antenna connector* (BS-side connector or UE-side connector) for downlink or uplink for the configuration in normal operating conditions. + +![Diagram of Repeater type 1-C downlink and uplink interface](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +The diagram illustrates the internal structure of a Repeater type 1-C. A central rectangular box represents the repeater unit. Inside, there are two parallel horizontal lines representing signal paths. The top path contains a right-pointing triangle (amplifier) and has a downward arrow above it labeled 'Downlink'. The bottom path contains a left-pointing triangle (amplifier) and has an upward arrow below it labeled 'Uplink'. On the left side of the box, there is a connector labeled 'BS-side connector' with an arrow pointing into the box. On the right side, there is a connector labeled 'UE-side connector' with an arrow pointing out of the box. + +Diagram of Repeater type 1-C downlink and uplink interface + +Figure 4.2.1-1: Repeater type 1-C downlink and uplink interface + +### 4.2.1A Network controlled Repeater type 1-C + +For *NCR type 1-C*, the NCR-Fwd RF requirements are applied at the NCR *antenna connector* (BS-side connector or UE-side connector) for downlink or uplink for the configuration in normal operating conditions. + +For *NCR type 1-C*, the NCR-MT RF requirements are applied at the NCR *antenna connector* (BS-side connector) for the configuration in normal operating conditions. + +![Diagram of Network controlled Repeater type 1-C downlink and uplink interface. The diagram shows a Mobile Termination (MT) block containing a Radio Transceiver, and a Forwarding (Fwd) block containing a loop with two arrows representing Downlink and Uplink. The MT and Fwd blocks are connected by a dashed line. The Fwd block is connected to a BS-side antenna connector on the left and a UE-side antenna connector on the right. The Downlink arrow points from the MT to the Fwd block, and the Uplink arrow points from the Fwd block to the MT.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the internal architecture of a Network controlled Repeater type 1-C. It consists of two main functional blocks: Mobile Termination (MT) and Forwarding (Fwd). The MT block contains a Radio Transceiver. The Fwd block contains a loop with two arrows: one pointing right labeled 'Downlink' and one pointing left labeled 'Uplink'. The MT and Fwd blocks are connected by a dashed line. The Fwd block is connected to a BS-side antenna connector on the left and a UE-side antenna connector on the right. The Downlink arrow points from the MT to the Fwd block, and the Uplink arrow points from the Fwd block to the MT. + +Diagram of Network controlled Repeater type 1-C downlink and uplink interface. The diagram shows a Mobile Termination (MT) block containing a Radio Transceiver, and a Forwarding (Fwd) block containing a loop with two arrows representing Downlink and Uplink. The MT and Fwd blocks are connected by a dashed line. The Fwd block is connected to a BS-side antenna connector on the left and a UE-side antenna connector on the right. The Downlink arrow points from the MT to the Fwd block, and the Uplink arrow points from the Fwd block to the MT. + +**Figure 4.2.1-1A: Network controlled Repeater type 1-C downlink and uplink interface** + +NOTE 1: the NCR-MT and NCR-Fwd may have the same or separate antenna connectors. + +## 4.2.1B Network controlled Repeater type 1-H + +For *NCR type 1-H*, the requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +For *NCR type 1-H*, the NCR-Fwd conducted RF requirements are applied at the NCR individual or groups of *TAB connectors* at the *transceiver array boundary* (BS-side TAB connector or UE-side TAB connector) for downlink or uplink for the configuration in normal operating conditions. + +For *NCR type 1-H*, the NCR-MT conducted RF requirements are applied at the NCR individual or groups of *TAB connectors* at the *transceiver array boundary* (BS-side TAB connector) for the configuration in normal operating conditions. + +![Diagram of Network controlled Repeater type 1-H downlink and uplink interface. It shows a Mobile Termination (MT) with a Radio Transceiver Unit array (TRXUA) connected to a Forwarding (Fwd) unit. The Fwd unit has Downlink and Uplink paths. On the left, a Composite antenna (containing RDN and AA) is connected to the Fwd unit via BS-side TABC. On the right, another Composite antenna (containing RDN and AA) is connected to the Fwd unit via UE-side TABC. The BS-side RIB is on the far left, and the UE-side RIB is on the far right.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram illustrates the internal architecture of a Network Controlled Repeater type 1-H. At the top, a dashed box labeled 'Mobile Termination(MT)' contains a 'Radio Transceiver Unit array (TRXUA)'. Below this, a 'Forwarding (Fwd)' block is shown with two internal arrows: one pointing right labeled 'Downlink' and one pointing left labeled 'Uplink'. To the left of the Fwd block, a 'Composite antenna' block (enclosed in a dashed box) contains 'Radio Distribution network (RDN)' and 'Antenna Array (AA)'. This composite antenna is connected to the Fwd block through a 'BS-side TABC' (Base Station-side Transport Antenna Connector). To the right of the Fwd block, another 'Composite antenna' block (also in a dashed box) contains 'Radio Distribution network (RDN)' and 'Antenna Array (AA)'. This composite antenna is connected to the Fwd block through a 'UE-side TABC' (User Equipment-side Transport Antenna Connector). The entire system is bounded by 'BS-side RIB' (Radiated Interface Boundary) on the far left and 'UE-side RIB' on the far right. + +Diagram of Network controlled Repeater type 1-H downlink and uplink interface. It shows a Mobile Termination (MT) with a Radio Transceiver Unit array (TRXUA) connected to a Forwarding (Fwd) unit. The Fwd unit has Downlink and Uplink paths. On the left, a Composite antenna (containing RDN and AA) is connected to the Fwd unit via BS-side TABC. On the right, another Composite antenna (containing RDN and AA) is connected to the Fwd unit via UE-side TABC. The BS-side RIB is on the far left, and the UE-side RIB is on the far right. + +Figure 4.2.1-1B: Network controlled Repeater type 1-H downlink and uplink interface + +NOTE 1: the NCR-MT and NCR-Fwd may have the same or separate TAB connectors. + +## 4.2.2 Repeater type 2-O + +For *repeater type 2-O*, the radiated characteristics are defined over the air (OTA), where the operating band specific radiated interface is referred to as the Radiated Interface Boundary (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +![Diagram of Radiated reference points for repeater type 2-O](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates the internal architecture and radiated reference points for a repeater type 2-O. It consists of three main components: a BS-side Composite Antenna on the left, a central Repeater unit, and a UE-side Composite Antenna on the right. Each Composite Antenna is composed of an Antenna Array (AA) and a Radio Distribution Network (RDN). The Repeater unit contains two amplifiers, one for the Downlink (indicated by a right-pointing arrow) and one for the Uplink (indicated by a left-pointing arrow). The Downlink path connects the BS-side RDN to the UE-side RDN via the top amplifier. The Uplink path connects the UE-side RDN to the BS-side RDN via the bottom amplifier. Vertical dashed lines mark the BS-side RIB (Radiated Interface Boundary) at the left edge of the BS-side Composite Antenna and the UE-side RIB at the right edge of the UE-side Composite Antenna. A horizontal bracket at the bottom labels the entire assembly as 'Repeater'. + +Diagram of Radiated reference points for repeater type 2-O + +**Figure 4.2.2-1: Radiated reference points for *repeater type 2-O*** + +#### 4.2.2A Network controlled Repeater type 2-O + +For *NCR type 2-O*, the radiated characteristics for NCR-Fwd and NCR-MT are defined over the air (OTA), where the operating band specific radiated interface is referred to as the Radiated Interface Boundary (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +For *NCR type 2-O*, the NCR-MT conducted RF requirements are applied at the BS side RIB for the configuration in normal operating conditions. + +![Figure 4.2.2-1A: Radiated reference points for network controlled repeater type 2-O. The diagram shows a Mobile Termination (MT) connected to a Radio Transceiver Unit array (TRXUA). The TRXUA is connected to a Forwarding (Fwd) unit. The Fwd unit is connected to a Radio Distribution network (RDN) and an Antenna Array (AA). The RDN and AA are part of a Composite antenna. The diagram is divided into BS-side RIB and UE-side RIB. The BS-side RIB contains the MT, TRXUA, and Fwd unit. The UE-side RIB contains the RDN and AA. The Fwd unit has a Downlink arrow pointing to the RDN and an Uplink arrow pointing from the RDN.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +The diagram illustrates the internal architecture of a network controlled repeater type 2-O. On the left, a dashed box labeled 'BS-side RIB' contains a 'Mobile Termination (MT)' block, which is connected to a 'Radio Transceiver Unit array (TRXUA)' block. Below the TRXUA, there are three vertical lines representing connections. The TRXUA is connected to a 'Forwarding (Fwd)' block. The Fwd block has a 'Downlink' arrow pointing to the right and an 'Uplink' arrow pointing to the left. To the right of the Fwd block, another dashed box labeled 'UE-side RIB' contains a 'Radio Distribution network (RDN)' block and an 'Antenna Array (AA)' block. The Fwd block is connected to the RDN block. The RDN and AA blocks are grouped together in a dashed box labeled 'Composite antenna'. The entire diagram is enclosed in a dashed box labeled 'Composite antenna' at the bottom. The labels 'BS-side RIB' and 'UE-side RIB' are placed at the bottom left and bottom right respectively. + +Figure 4.2.2-1A: Radiated reference points for network controlled repeater type 2-O. The diagram shows a Mobile Termination (MT) connected to a Radio Transceiver Unit array (TRXUA). The TRXUA is connected to a Forwarding (Fwd) unit. The Fwd unit is connected to a Radio Distribution network (RDN) and an Antenna Array (AA). The RDN and AA are part of a Composite antenna. The diagram is divided into BS-side RIB and UE-side RIB. The BS-side RIB contains the MT, TRXUA, and Fwd unit. The UE-side RIB contains the RDN and AA. The Fwd unit has a Downlink arrow pointing to the RDN and an Uplink arrow pointing from the RDN. + +**Figure 4.2.2-1A: Radiated reference points for network controlled repeater type 2-O** + +NOTE 1: the NCR-MT and NCR-Fwd may have the same or separate RIB + +## 4.3 Repeater classes + +### 4.3.1 Repeater class for downlink + +The requirements in this specification apply to downlink Wide Area repeaters, downlink Medium Range repeaters and downlink Local Area repeaters unless otherwise stated. The associated deployment scenarios for each class are exactly the same for repeater with and without connectors. + +For *repeater type 1-C* and *type 2-O*, repeater downlink classes are defined as indicated below: + +- Wide Area repeaters are characterised by requirements derived from Macro Cell scenarios with a repeater to UE minimum distance along the ground equal to 35 m. +- Medium Range repeaters are characterised by requirements derived from Micro Cell scenarios with a repeater to UE minimum distance along the ground equal to 5 m. +- Local Area repeaters are characterised by requirements derived from Pico Cell scenarios with a repeater to UE minimum distance along the ground equal to 2 m or from Femto Cell scenarios. + +- Note: The requirements in this specification for LA 1-C repeaters apply to 1-C repeaters with declared output power less than or equal to LA rated output power limits as in table 6.2.1-1. + +### 4.3.2 Repeater class for uplink + +The requirements in this specification apply to uplink Wide Area repeaters and uplink Local Area repeaters unless otherwise stated. The associated deployment scenarios for each class are exactly the same for repeater with and without connectors. + +For *repeater type 1-C* and *type 2-O*, repeater uplink classes are defined as indicated below: + +- Wide Area repeaters are characterised by requirements derived from Macro Cell and/or Micro Cell scenarios. +- Local Area repeaters are characterised by requirements derived from Pico Cell and/or Micro Cell scenarios. + +## 4.3A Network controlled repeater classes + +### 4.3A.1 Network controlled repeater class for downlink + +The requirements in this specification apply to downlink Wide Area NCR, downlink Medium Range NCR and downlink Local Area NCR unless otherwise stated. The associated deployment scenarios for each class are exactly the same for repeater with and without connectors. + +For *NCR type 1-C*, *type 1-H* and *type 2-O*, NCR downlink classes are defined as indicated below: + +- Wide Area NCR are characterised by requirements derived from Macro Cell scenarios with a NCR to UE minimum distance along the ground equal to 35 m. +- Medium Range NCR are characterised by requirements derived from Micro Cell scenarios with a NCR to UE minimum distance along the ground equal to 5 m. +- Local Area NCR are characterised by requirements derived from Pico Cell scenarios with a NCR to UE minimum distance along the ground equal to 2 m or from Femto Cell scenarios. +- Note: The requirements in this specification for LA NCR type 1-C apply to NCR type 1-C with declared output power less than or equal to LA rated output power limits as in table 6.2.1-1. + +### 4.3A.2 Network controlled repeater class for uplink + +The requirements in this specification apply to uplink Wide Area NCR and uplink Local Area NCR unless otherwise stated. The associated deployment scenarios for each class are exactly the same for NCR with and without connectors. + +For *NCR type 1-C*, *type 1-H* and *type 2-O*, NCR uplink classes are defined as indicated below: + +- Wide Area NCR are characterised by requirements derived from Macro Cell and/or Micro Cell scenarios. +- Local Area NCR are characterised by requirements derived from Pico Cell and/or Micro Cell scenarios. + +## 4.4 Regional requirements + +Some requirements in the present document may only apply in certain regions either as optional requirements, or as mandatory requirements set by local and regional regulation. It is normally not stated in the 3GPP specifications under what exact circumstances the regional requirements apply, since this is defined by local or regional regulation. + +Table 4.4-1 lists all requirements in the present specification that may be applied differently in different regions. + +**Table 4.4-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|-------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.2 | Operating bands | Some NR operating bands may be applied regionally. | +| 6.2 | Repeater output power | For Band n41 and n90 operation in Japan, additional output power limits shall be applied. | +| 6.2.4,
7.3.4 | Repeater output power,
OTA repeater output power:
Additional requirements | These requirements may be applied regionally as additional repeater output power requirements. | +| 6.5.2 | Adjacent Channel Leakage Power Ratio | For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all antenna connectors for repeater type 1-C . | +| 6.5.3.2,
7.5.3.2 | Operating band unwanted emission,
OTA operating band unwanted emissions | Category A or Category B operating band unwanted emissions limits may be applied regionally. | +| 6.5.3.2.5.1 | Operating band unwanted emission | The repeater may have to comply with the additional requirements, when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.5.3.2.5.2 | Operating band unwanted emission | The repeater operating in Band n20 may have to comply with the additional requirements for protection of DTT, when deployed in certain regions. | +| 6.5.3.2 | Operating band unwanted emissions | For Band n41 and n90 operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all antenna connectors for repeater type 1-C . | +| 6.5.4.2.1,
7.5.4.2 | Tx spurious emissions,
OTA Tx spurious emissions | Category A or Category B spurious emission limits, as defined in ITU-R Recommendation SM.329 [5], may apply regionally. | +| 6.5.4.2.2,
7.5.4.2.3 | Tx spurious emissions:
additional requirements,
OTA Tx spurious emissions:
additional requirements | These requirements may be applied for the protection of system operating in frequency ranges other than the repeater operating band . | +| 6.5.4.2 | Transmitter spurious emissions | For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all antenna connectors for repeater type 1-C shall not exceed the basic limits . | +| 6.5.5.1 | Receiver spurious emissions | For Band n41 and n90 operation in Japan, the sum of receiver spurious emissions requirements over all antenna connectors for repeater type 1-C shall not exceed minimum requirements defined in clause 6.5.5.2. | +| 6.7.2 | Input intermodulation | Interfering signal positions that are partially or completely outside of any downlink operating band of the repeater are not excluded from the requirement in Japan in Band n77, n78, n79. | + +| Clause number | Requirement | Comments | +|---------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 6.8 | Output intermodulation | For Band n41 and n90 operation in Japan, the repeater may have to comply with the additional requirements, when deployed in certain regions. | + +## 4.5 Applicability of requirements + +In table 4.5-1, the requirement applicability for each requirement set is defined. For each requirement, the applicable requirement clause in the specification is identified. Requirements not included in a requirement set is marked not applicable (NA). + +**Table 4.5-1: Requirement set applicability** + +| Requirement | Requirement set | | +|---------------------------------------------|--------------------------|--------------------------| +| | Repeater type 1-C | Repeater type 2-O | +| Repeater output power | 6.2 | NA | +| Frequency stability | 6.3 | | +| Out of band gain | 6.4 | | +| Unwanted emissions | 6.5 | | +| Error Vector Magnitude | 6.6 | | +| Input intermodulation | 6.7 | | +| Output intermodulation | 6.8 | | +| Adjacent Channel Rejection Ratio (ACRR) | 6.9 | | +| Transmit ON/OFF power | 6.10 | | +| Repeater output power | NA | 7.2 | +| OTA frequency stability | | 7.3 | +| OTA out of band gain | | 7.4 | +| OTA unwanted emissions | | 7.5 | +| OTA Error Vector Magnitude | | 7.6 | +| OTA input intermodulation | | 7.7 | +| | | | +| OTA Adjacent Channel Rejection Ratio (ACRR) | | 7.8 | +| OTA transmit ON/OFF power | | 7.9 | + +**Table 4.5-1a: Requirement set applicability for NCR-Fwd** + +| Requirement | Requirement set | | | +|---------------------------------------------|-----------------------------|-----------------------------|-----------------------------| +| | NCR-Fwd type
1-C | NCR-Fwd type
1-H | NCR-Fwd type
2-O | +| Repeater output power | 6.2 | 6.2 | NA | +| Frequency stability | 6.3 | 6.3 | | +| Out of band gain | 6.4 | 6.4 | | +| Unwanted emissions | 6.5 | 6.5 | | +| Error Vector Magnitude | 6.6 | 6.6 | | +| Input intermodulation | 6.7 | 6.7 | | +| Output intermodulation | 6.8 | 6.8 | | +| Adjacent Channel Rejection Ratio (ACRR) | 6.9 | 6.9 | | +| Transmit ON/OFF power | 6.10 | 6.10 | | +| Repeater output power | NA | NA | 7.2 | +| OTA frequency stability | | | 7.3 | +| OTA out of band gain | | | 7.4 | +| OTA unwanted emissions | | | 7.5 | +| OTA Error Vector Magnitude | | | 7.6 | +| OTA input intermodulation | | | 7.7 | +| OTA Adjacent Channel Rejection Ratio (ACRR) | | | 7.8 | +| OTA transmit ON/OFF power | | | 7.9 | + +**Table 4.5-1b: Requirement set applicability for NCR-MT** + +| Requirement | Requirement set | | | +|-------------------------------------------|----------------------------|----------------------------|----------------------------| +| | NCR-MT type
1-C | NCR-MT type
1-H | NCR-MT type
2-O | +| Conducted transmitter power | 6.2.3.2 | 6.2.3.2 | NA | +| Conducted output power dynamics | 6.11 | 6.11 | | +| Conducted transmit signal quality | 6.12 | 6.12 | | +| Conducted output RF spectrum emissions | 6.5 | 6.5 | | +| Diversity characteristics | 6.13 | 6.13 | | +| Conducted reference sensitivity | 6.14 | 6.14 | | +| Conducted maximum input level | 6.15 | 6.15 | | +| Conducted adjacent channel selectivity | 6.16 | 6.16 | | +| Conducted blocking characteristics | 6.17 | 6.17 | | +| Conducted spurious response | 6.18 | 6.18 | | +| Conducted intermodulation characteristics | 6.19 | 6.19 | NA | +| Conducted spurious emissions | 6.5.5 | 6.5.5 | | +| Radiated transmitter power | NA | NA | 7.2 | +| Radiated output power dynamics | | | 7.10 | +| Radiated transmit signal quality | | | 7.11 | +| Radiated output RF spectrum emissions | | | 7.5 | +| Diversity characteristics | | | 7.12 | +| Radiated reference sensitivity | | | 7.13 | +| Radiated maximum input level | | | 7.14 | +| Radiated adjacent channel selectivity | | | 7.15 | +| Radiated blocking characteristics | | | 7.16 | +| Radiated spurious response | | | 7.17 | +| Radiated intermodulation characteristics | | | 7.18 | +| Radiated spurious emissions | | | 7.19 | + +## 4.6 Requirements for contiguous and *non-contiguous spectrum* + +A spectrum allocation where a repeater operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for repeater configured for both contiguous spectrum operation and non-contiguous spectrum operation. + +For repeater operation in non-contiguous spectrum, some requirements apply at the repeater *passband* edges. For each such requirement, it is stated how the limits apply relative to the repeater *gap between passbands* and the *Inter-passband gap* respectively. + +For NCR operation in non-contiguous spectrum, some requirements apply at the NCR-Fwd *passband* edges or NCR-MT carrier edges. For each such requirement, it is stated how the limits apply relative to the NCR *gap between passbands* and the *Inter-passband gap* respectively. + +## 4.7 Requirements for repeater capable of multi-band operation + +For multi-band connector or multi-band RIB, the RF requirements in clauses 6 and 7 apply separately to each supported operating band unless otherwise stated. For some requirements, it is explicitly stated that specific additions or exclusions to the requirement apply at multi-band connector(s), and multi-band RIB(s) as detailed in the requirement clause. For repeater or NCR capable of multi-band operation, various structures in terms of combinations of different downlink and uplink implementations (multi-band or single band) with mapping to one or more *antenna connectors* for *repeater type 1-C*, *NCR type 1-C*, *type 1-H* in different ways are possible. For multi-band connector(s) the exclusions or provisions for multi-band apply. For single-band connector(s), the following applies: + +- Single-band transmitter spurious emissions, *operating band* unwanted emissions, ACLR, output intermodulation, ACRR and receiver spurious emissions requirements apply to this *connector* that is mapped to single-band. +- If the repeater or NCR is configured for single-band operation, single-band requirements shall apply to this *antenna connector* configured for single-band operation and no exclusions or provisions for multi-band capable repeater or NCR are applicable. Single-band requirements are tested separately at the *antenna connector* configured for single-band operation, with all other *antenna connectors* terminated. + +--- + +## 5 Operating bands + +### 5.1 General + +The channel arrangements presented in this clause are based on the *operating bands* defined in the present release of specifications. + +NOTE: Other *operating bands* may be considered in future releases. + +Requirements throughout the RF specifications are in many cases defined separately for different frequency ranges (FR). The frequency ranges in which NR can operate according to the present version of the specification are identified as described in table 5.1-1. + +**Table 5.1-1: Definition of frequency ranges** + +| Frequency range designation | | Corresponding frequency range | +|-----------------------------|-------|-------------------------------| +| FR1 | | 410 MHz – 7125 MHz | +| FR2 | FR2-1 | 24250 MHz – 52600 MHz | +| | FR2-2 | 52600 MHz – 71000 MHz | + +Whenever FR2 is referred, both FR2-1 and FR2-2 frequency sub-ranges shall be applied, unless otherwise stated. + +## 5.2 Operating bands + +NR repeater is designed to operate in the *operating bands* in FR1 and FR2-1 defined in TS 38.104 [2] except the operating bands n46, n96 and n102. + +## 5.3 Channel arrangement + +### 5.3.1 Channel raster + +#### 5.3.1.1 NR-ARFCN and channel raster + +For repeater and NCR-Fwd, the NR-ARFCN and channel raster is the same as specified for BS in TS 38.104 [2], subclause 5.4.2.1. + +For NCR-MT, the NR-ARFCN and channel raster is the same as specified for UE in TS 38.101-1 [13] for FR1 in subclause 5.4.2.1 and in TS 38.101-2 [14] for FR2-1 in subclause 5.4.2.1. + +#### 5.3.1.2 Channel raster entries for each *operating band* + +For repeater and NCR-Fwd, the channel raster entries for NR bands for FR1 and FR2-1 defined in TS 38.104 [2] are the same as specified for BS in TS38.104 [2], clause 5.4.2.3. + +For NCR-MT, the channel raster entries for NR bands for FR1 are the same as specified for UE in TS 38.101-1 [13] in subclause 5.4.2.3 and for NR bands for FR2-1 are the same as specified for UE in TS 38.101-2 [14] in subclause 5.4.2.3. + +#### 5.3.1.3 Channel raster to resource element mapping + +For NCR-MT, the channel raster to resource element mapping is the same as specified for UE in TS 38.101-1 [13] for FR1 in subclause 5.4.2.2 and in TS 38.101-2 [14] for FR2 in subclause 5.4.2.2. + +### 5.3.2 Synchronization raster + +#### 5.3.2.1 Synchronization raster and numbering + +For repeater and NCR-Fwd, the synchronization raster and numbering are the same as specified for BS in TS38.104 [2], clause 5.4.3.1. + +For NCR-MT, the synchronization raster and numbering are the same as specified for UE in subclause 5.4.3.1 in TS 38.101-1 [13] for FR1 in subclause 5.4.3.1 and in subclause 5.4.3.1 in TS 38.101-2 [14] for FR2-1 in subclause 5.4.3.1. + +### 5.3.2.2 Synchronization raster entries for each operating band + +For repeater and NCR-Fwd, the synchronization raster entries for NR bands for FR1 and FR2-1 defined in TS38.104 [2] are the same as specified for BS in TS38.104 [2], clause 5.4.3.3. + +For NCR-MT, the synchronization raster entries for NR bands for FR1 in Table 5.2-1 are the same as specified for UE in TS 38.101-1 [13] in subclause 5.4.3.3 and for NR bands for FR2-1 are the same as specified for UE in TS 38.101-2 [14] in subclause 5.4.3.3. + +### 5.3.2.3 Synchronization raster to synchronization block resource element mapping + +For NCR-MT, the synchronization raster to synchronization block resource element mapping is the same as specified for UE in TS 38.101-1 [13] for FR1 in subclause 5.4.3.2 and in TS 38.101-2 [14] for FR2-1 in subclause 5.4.3.2. + +## 5.3.3 Channel spacing + +For NCR-MT, the channel spacing is the same as specified for UE in TS 38.101-1 [13] for FR1 in subclause 5.4.1 and in TS 38.101-2 [14] for FR2-1 in subclause 5.4.1. + +## 5.3.4 TX–RX frequency separation + +The default TX channel (carrier centre frequency) to RX channel (carrier centre frequency) separation for operating bands is specified in Table 5.3.4-1. + +**Table 5.3.4-1: NCR-MT TX-RX frequency separation** + +| NR Operating Band | TX – RX
carrier centre frequency
separation | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| n1 | 190 MHz | +| n2 | 80 MHz | +| n3 | 95 MHz | +| n5 | 45 MHz | +| n7 | 120 MHz | +| n8 | 45 MHz | +| n12 | 30 MHz | +| n13 | -31 MHz | +| n14 | -30 MHz | +| n18 | 45 MHz | +| n20 | -41 MHz | +| n24 | -101.5, -120.5 MHz | +| n25 | 80 MHz | +| n26 | 45 MHz | +| n28 | 55 MHz | +| n30 | 45 MHz | +| n65 | 190 MHz | +| n66 | 400 MHz | +| n70 | 300 MHz | +| n71 | -46 MHz | +| n74 | 48 MHz | +| n85 | 30 MHz | +| n91 | 570 MHz – 595 MHz
(NOTE 2) | +| n92 | 575 MHz – 680 MHz ( $\mu = 0$ )
580 MHz – 675 MHz ( $\mu = 1$ )
(NOTE 2) | +| n93 | 517 MHz – 547 MHz
(NOTE 2) | +| n94 | 522 MHz – 632 MHz ( $\mu = 0$ )
527 MHz – 627 MHz ( $\mu = 1$ )
(NOTE 2) | +| n100 | 45 MHz | +| n105 | -51 MHz | +| NOTE 1: Void | | +| NOTE 2: The range of TX-RX frequency separation given paired UL and DL channel bandwidths $BW_{UL}$ and $BW_{DL}$ is given by the respective lower and upper limit $F_{DL\_low} - F_{UL\_high} + 0.5(BW_{DL} + BW_{UL})$ and $F_{DL\_high} - F_{UL\_low} - 0.5(BW_{DL} + BW_{UL})$ . The UL and DL channel bandwidth combinations specified in Clause 5.4 depend on the | | + +| NR Operating Band | TX – RX
carrier centre frequency
separation | +|----------------------------------------------|---------------------------------------------------| +| subcarrier spacing configuration $\mu$ [21]. | | + +## 5.4 NCR-MT channel bandwidth + +### 5.4.1 General + +The NCR-MT supports a single NR RF carrier in the uplink or downlink in this release. From a BS perspective, different NCR-MT channel bandwidths may be supported within the same spectrum for transmitting to and receiving from NCR-MT connected to the BS. Transmission of multiple carriers to different NCR-MT within the BS channel bandwidth can be supported. + +From a NCR-MT perspective, the NCR-MT per passband is configured with one carrier and NCR-MT is configured with one more BWP. The NCR-MT does not need to be aware of the BS channel bandwidth or how the BS allocates bandwidth to different NCR-MT. + +The placement of the NCR-MT channel bandwidth for NCR-MT carrier is flexible but can only be completely within the NCR-Fwd passband. + +The relationship between the NCR-MT channel bandwidth, the guardband and the transmission bandwidth configuration is shown in Figure 5.4.1-1. + +![Figure 5.4.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one NR channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside the channel, a solid vertical line on the left marks the start of the transmission bandwidth, and a solid vertical line on the right marks the end. A double-headed arrow between these lines is labeled 'Transmission Bandwidth Configuration N_RB [RB]'. Within this transmission bandwidth, a group of blue vertical bars represents 'Active Resource Blocks'. A bracket above this group is labeled 'Transmission Bandwidth [RB]'. To the right of the active blocks, a single vertical bar is labeled 'Resource Block'. The area between the transmission bandwidth edges and the channel edges is labeled 'Guardband, can be asymmetric' with arrows pointing to the gaps on both sides.](b560268ea8f6526970f23f0da225b099_img.jpg) + +Figure 5.4.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one NR channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside the channel, a solid vertical line on the left marks the start of the transmission bandwidth, and a solid vertical line on the right marks the end. A double-headed arrow between these lines is labeled 'Transmission Bandwidth Configuration N\_RB [RB]'. Within this transmission bandwidth, a group of blue vertical bars represents 'Active Resource Blocks'. A bracket above this group is labeled 'Transmission Bandwidth [RB]'. To the right of the active blocks, a single vertical bar is labeled 'Resource Block'. The area between the transmission bandwidth edges and the channel edges is labeled 'Guardband, can be asymmetric' with arrows pointing to the gaps on both sides. + +**Figure 5.4.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one NR channel** + +## 5.4.2 Transmission bandwidth configuration + +For NCR-MT, the transmission bandwidth configuration is the same as specified for UE in TS 38.101-1 [13] for FR1 in subclause 5.3.2 and in TS 38.101-2 [14] for FR2-1 in subclause 5.3.2. + +## 5.4.3 Minimum guardband and transmission bandwidth configuration + +For NCR-MT, the minimum guardband and transmission bandwidth configuration is the same as specified for UE in TS38.101-1 [13] for FR1 and in TS 38.101-2 [14] for FR2-1 in subclause 5.3.3. + +## 5.4.4 RB alignment + +For NCR-MT, the RB alignment is the same as specified for UE in TS38.101-1 [13] for FR1 in subclause 5.3.4 and in TS 38.101-2 [14] for FR2-1 in subclause 5.3.4 + +## 5.4.5 NCR-MT channel bandwidth per operating band + +For NCR-MT, the channel bandwidth for NR bands for FR1 in Table 5.2-1 is the same as specified for UE in TS38.101-1 [13] in subclause 5.3.5 and is the same as specified for UE in TS38.101-2 [14] in subclause 5.3.5. + +--- + +# 6 Conducted characteristics + +## 6.1 General + +Unless otherwise stated, the conducted transmitter characteristics are specified at the *antenna connector* for *repeater type 1-C* configuration in normal operating conditions. + +Requirements apply in both DL and UL unless otherwise stated or declared. + +For the DL the *antenna connector* on the BS side is the input and the *antenna connector* on the UE side is the output. + +For the UL the *antenna connector* on the UE side is the input and the *antenna connector* on the BS side is the output. + +## 6.2 Repeater output power + +### 6.2.1 General + +The repeater conducted output power requirement is at the *antenna connector*. + +The *rated passband output power* of the *repeater type 1-C* and *NCR-FWD type 1-C* shall be as specified in table 6.2.1-1 and table 6.2.1-2. + +**Table 6.2.1-1: Repeater type 1-C and NCR-FWD type 1-C DL transmission classes rated output power limits for repeater classes** + +| Repeater class | $P_{\text{rated,p,AC}}$ | +|-----------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Wide Area repeater | Note 1 | +| Medium Range repeater | $\leq 38 \text{ dBm} + X$ , Note 2 | +| Local Area repeater | $\leq 24 \text{ dBm} + X$ , Note 2 | +| NOTE 1: There is no upper limit for the $P_{\text{rated,p,AC}}$ rated passband output power of the Wide Area repeater | | +| NOTE 2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/20\text{MHz}))$ | | + +**Table 6.2.1-2: Repeater type 1-C and NCR-FWD type 1-C UL transmission classes rated output power limits for repeater classes** + +| Repeater class | $P_{\text{rated,p,AC}}$ | +|------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Wide Area repeater | Note 1 | +| Local Area repeater | $\leq 24 \text{ dBm} + X$ , Note 2 | +| NOTE 1: There is no upper limit for the $P_{\text{rated,p,AC}}$ rated passband output power of the Wide Area repeater. | | +| NOTE 2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/20\text{MHz}))$ | | + +The rated passband output power of the NCR-Fwd 1-H shall be as specified in table 6.2.1-3 and table 6.2.1-4. + +**Table 6.2.1-3: NCR-Fwd 1-H DL rated output power limits for NCR classes** + +| Repeater class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|------------------------------------| +| Wide Area NCR | (Note 1) | (Note 1) | +| Medium Range NCR | $\leq 38 \text{ dBm} + 10 \cdot \log(N_{\text{TXU,counted}}) + X$ (NOTE 2) | $\leq 38 \text{ dBm} + X$ (NOTE 2) | +| Local Area NCR | $\leq 24 \text{ dBm} + 10 \cdot \log(N_{\text{TXU,counted}}) + X$ (NOTE 2) | $\leq 24 \text{ dBm} + X$ (NOTE 2) | +| NOTE 1: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide Area NCR-Fwd. | | | +| NOTE 2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/20\text{MHz}))$ | | | + +**Table 6.2.1-4: NCR-Fwd 1-H UL rated output power limits for NCR classes** + +| Repeater class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------| +| Wide Area NCR | (Note 1) | (Note 1) | +| Local Area NCR | $\leq 24 \text{ dBm} + 10 \cdot \log(N_{\text{TXU,counted}}) + X$ (NOTE 2, 3) | $\leq 24 \text{ dBm} + X$ (NOTE 2) | +| NOTE 1: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide Area NCR. | | | +| NOTE 2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/20\text{MHz}))$ | | | +| NOTE 3: For joint transmission of NCR-FWD and NCR-MT, $P_{\text{rated,c,sys}}$ shall apply to the total power of NCR-FWD and NCR-MT. | | | + +## 6.2.2 Minimum requirement for RF repeater + +The requirements shall apply with NR signals in the *passband* of the repeater at: + +The lowest input power ( $P_{\text{in,p,AC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,AC}}$ ). + +Up to: + +The lowest input power ( $P_{\text{in,p,AC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,AC}}$ ), plus 10dB + +In normal conditions, the measured output power, $P_{\text{max,p,AC}}$ shall remain within +2 dB and -2 dB of the *rated passband output power* $P_{\text{rated,p,AC}}$ , declared by the manufacturer. + +In extreme conditions, the measured output power, $P_{\text{max,p,AC}}$ shall remain within +2.5 dB and -2.5 dB of the *rated passband output power* $P_{\text{rated,p,AC}}$ , declared by the manufacturer. + +## 6.2.3 Minimum requirement for NCR + +### 6.2.3.1 Minimum requirement for NCR-Fwd + +#### 6.2.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +The requirements shall apply with NR signals in the *passband* of the NCR-Fwd at: + +The lowest input power ( $P_{\text{in,p,AC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,AC}}$ ). + +Up to: + +The lowest input power ( $P_{\text{in,p,AC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,AC}}$ ), plus 10dB + +In normal conditions, the measured output power, $P_{\text{max,p,AC}}$ shall remain within +2 dB and -2 dB of the *rated passband output power* $P_{\text{rated,p,AC}}$ , declared by the manufacturer. + +In extreme conditions, the measured output power, $P_{\text{max,p,AC}}$ shall remain within +2.5 dB and -2.5 dB of the *rated passband output power* $P_{\text{rated,p,AC}}$ , declared by the manufacturer. + +#### 6.2.3.1.2 Minimum requirement for NCR-Fwd type 1-H + +The requirements shall apply with NR signals in the *passband* of the NCR-Fwd at: + +The lowest input power ( $P_{\text{in,p,TABC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,TABC}}$ ). + +Up to: + +The lowest input power ( $P_{\text{in,p,TABC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,TABC}}$ ), plus 10dB + +In normal conditions, the measured output power, $P_{\text{max,p,TABC}}$ shall remain within +2 dB and -2 dB of the *rated passband output power* $P_{\text{rated,p,TABC}}$ , declared by the manufacturer. + +In extreme conditions, the measured output power, $P_{\max,p,TABC}$ shall remain within +2.5 dB and -2.5 dB of the *rated passband output power* $P_{\text{rated,p,TABC}}$ , declared by the manufacturer. + +### 6.2.3.2 Minimum requirement for NCR-MT + +#### 6.2.3.2.1 General + +The NCR-MT conducted output power requirement is at *antenna connector* for NCR-MT type 1-C, or at *TAB connector* for NCR-MT type 1-H. + +The *rated carrier output power* of the NCR-MT type 1-C shall be as specified in table 6.2.3.2.1-1. + +**Table 6.2.3.2.1-1: NCR-MT type 1-C UL transmission classes rated output power limits** + +| Repeater class | $P_{\text{rated,c,AC}}$ | +|------------------------------------------------------------------------------------------------------------------|-------------------------| +| Wide Area NCR-MT | (Note) | +| Local Area NCR-MT | $\leq 24$ dBm | +| NOTE: There is no upper limit for the $P_{\text{rated,c,AC}}$ rated output power of the Wide Area NCR-MT. | | + +The *rated carrier output power* of the NCR-MT type 1-H shall be as specified in table 6.2.3.2.1-2. + +**Table 6.2.3.2.1-2: NCR-MT type 1-H UL transmission classes rated output power limits** + +| Repeater class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------| +| Wide Area NCR-MT | (Note 1) | (Note 1) | +| Local Area NCR-MT 2,3 | $\leq 24$ dBm + $10\log(N_{\text{TXU, counted}})$ | $\leq 24$ dBm | +| NOTE 1: There is no upper limit for the $P_{\text{rated,c,AC}}$ rated output power of the Wide Area NCR-MT.
NOTE 2: LA MT cannot exceed highest power class for that band as specified in TS 38.101-1.
NOTE 3: $N_{\text{TXU, counted}} = \min(N_{\text{TXU, active}}, 4)$ | | | + +#### 6.2.3.2.2 Minimum requirement for NCR-MT type 1-C and NCR-MT type 1-H + +In normal conditions, $P_{\max,c,AC}$ shall remain within +2 dB and -2 dB of the *rated carrier output power* $P_{\text{rated,c,AC}}$ , declared by the manufacturer. + +In extreme conditions, $P_{\max,c,AC}$ shall remain within +2.5 dB and -2.5 dB of the *rated carrier output power* $P_{\text{rated,c,AC}}$ , declared by the manufacturer. + +### 6.3.3 Minimum requirement for NCR + +#### 6.3.3.1 Minimum requirement for NCR-Fwd + +##### 6.3.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ PPM. + +#### 6.3.3.1.2 Minimum requirement for NCR-Fwd type 1-H + +The frequency deviation of the output signal with respect to the input signal between corresponding input/output TAB connectors shall be no more than $\pm 0,01$ PPM. + +### 6.3 Frequency stability + +#### 6.3.1 General + +Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal. + +#### 6.3.2 Minimum requirement for RF repeater + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ PPM. + +#### 6.3.3 Minimum requirement for NCR + +##### 6.3.3.1 Minimum requirement for NCR-Fwd + +###### 6.3.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ PPM. + +###### 6.3.3.1.2 Minimum requirement for NCR-Fwd type 1-H + +The frequency deviation of the output signal with respect to the input signal between corresponding input/output TAB connectors shall be no more than $\pm 0,01$ PPM. + +### 6.4 Out of band gain + +#### 6.4.1 General + +Out of band gain refers to the gain of the repeater outside the *passband*. + +The intended use of a repeater in a system is to amplify the in-band signals and not to amplify signals outside of the *passband*. + +In the intended application of the repeater, the out of band gain is less than lowest expected the coupling loss to the nearest source of emissions. + +#### 6.4.2 Minimum requirement for RF repeater + +The gain outside the *passband* shall not exceed the maximum level specified in table 6.4.2-1 or table 6.4.2-2, where: + +- $f\_offset\_CW$ is the offset between the outer channel edge frequency of the outer channel in the *passband* and a CW signal. + +**Table 6.4.2-1: Out of band gain limits 1 for bands below 2496 MHz** + +| Frequency offset, $f\_offset\_CW$ | Maximum gain | +|-------------------------------------|--------------| +| $0,2 \leq f\_offset\_CW < 1,0$ MHz | 60 dB | +| $1,0 \leq f\_offset\_CW < 5,0$ MHz | 45 dB | +| $5,0 \leq f\_offset\_CW < 10,0$ MHz | 45 dB | +| $10,0$ MHz $\leq f\_offset\_CW$ | 35 dB | + +**Table 6.4.2-2: Out of band gain limits 1 for bands above 2496 MHz** + +| Frequency offset, $f\_offset\_CW$ | Maximum gain | +|-----------------------------------|--------------| +| $[0,2] < f\_offset\_CW < 4,0$ MHz | 60 dB | +| $4,0 < f\_offset\_CW < 15,0$ MHz | 45 dB | +| $15,0$ MHz $< f\_offset\_CW$ | 35 dB | + +## 6.4.3 Minimum requirement for NCR + +### 6.4.3.1 Minimum requirement for NCR-Fwd + +#### 6.4.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +The gain between the input antenna connector and output antenna connector outside the *passband* shall not exceed the maximum level specified in table 6.4.2-1 or table 6.4.2-2 + +#### 6.4.3.1.2 Minimum requirement for NCR-Fwd type 1-H + +The gain defined between corresponding input/output TAB connectors outside the *passband* shall not exceed the maximum level specified in table 6.4.2-1 or table 6.4.2-2. + +## 6.5 Unwanted emissions + +### 6.5.1 General + +Unwanted emissions consist of out-of-band emissions and spurious emissions according to ITU definitions [5]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +The out-of-band emissions requirement for the Repeater transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and *operating band* unwanted emissions (OBUE). + +The maximum offset of the *operating band* unwanted emissions mask from the *operating band* edge is $\Delta f_{\text{OBUE}}$ . The Operating band unwanted emissions define all unwanted emissions in each supported downlink *operating band* of *repeater type 1-C* DL and uplink *operating band* of *repeater type 1-C* UL, plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band. Unwanted emissions outside of this frequency range are limited by a spurious emissions requirement. + +The values of $\Delta f_{\text{OBUE}}$ are defined in tables 6.5.1-1 and 6.5.1-2 for the NR *operating bands*. + +**Table 6.5.1-1: Maximum offset of OBUE outside the downlink *operating band* of *repeater type 1-C*, *NCR-Fwd type 1-C* and *NCR-Fwd type 1-H* DL** + +| Repeater or NCR type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------| +| NCR-Fwd type 1-H | $F_{\text{DL,high}} - F_{\text{DL,low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900 \text{ MHz}$ | 40 | +| | | | +| Repeater type 1-C and NCR-Fwd type 1-C | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 200 \text{ MHz}$ | 10 | +| | $200 \text{ MHz} < F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900 \text{ MHz}$ | 40 | + +**Table 6.5.1-2: Maximum offset of OBUE outside the uplink *operating band* of *repeater 1-C* UL** + +| Repeater or NCRtype | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------| +| NCR-Fwd type 1-H | $F_{\text{DL,high}} - F_{\text{DL,low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900 \text{ MHz}$ | 40 | +| | | | +| Repeater type 1-C and NCR-Fwd type 1-C | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 200 \text{ MHz}$ | 10 | +| | $200 \text{ MHz} < F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900 \text{ MHz}$ | 40 | + +For *NCR-Fwd type 1-H* the unwanted emission requirements are applied per the *TAB connector TX min cell groups* for all the configurations supported by the repeater. The *basic limits* and corresponding emissions scaling are defined in each relevant clause. + +There is no co-location unwanted emission requirement for LA NCR-Fwd type 1-C and repeaters type 1-C deployed in Femto cell scenario. + +## 6.5.2 Adjacent Channel Leakage Power Ratio + +### 6.5.2.1 General + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +The requirements shall apply outside the *repeater type 1-C passband* whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +For a *repeater* operating in *non-contiguous spectrum*, the ACLR requirement in clause 6.5.2.2 shall apply in *Gaps between passbands* for the frequency ranges defined in table 6.5.2.2-3, while the CACLR requirement in clause 6.5.2.2 shall apply in *gaps between passbands* for the frequency ranges defined in table 6.5.2.2-4. + +For a *multi-band connector*, the ACLR requirement in clause 6.5.2.2 shall apply in *inter-passband gaps* for the frequency ranges defined in table 6.5.2.2-3, while the CACLR requirement in clause 6.5.2.2 shall apply in *inter-passband gaps* for the frequency ranges defined in table 6.5.2.2-4. + +The requirement shall apply during the *transmitter ON state*. + +### 6.5.2.2 Limits and *basic limits* + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For DL (all repeater classes), and for UL for WA class, either the ACLR (CACLR) absolute *basic limits* in table 6.5.2.2-2, 6.5.2.2-5 or else the relevant the ACLR (CACLR) *limits* in table 6.5.2.2-1, 6.5.2.2-3 or 6.5.2.2-4, whichever is less stringent, shall apply for each *antenna connector*. For UL for LA class, the ACLR (CACLR) and *basic limits* in table 6.5.2.2-1a, 6.5.2.2-3 or 6.5.2.2-4a shall apply. + +**Table 6.5.2.2-1: ACLR limit for DL (all repeater classes) and for UL for Wide Area class** + +| nominal channel bandwidth BW_{Nominal} (MHz) (NOTE 5) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband edge | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|----------------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB
(Note 4) | +| | $1.5 \times BW_{Nominal}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB
(Note 4) | +| | 2.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB
(Note 3) | +| | 7.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB
(Note 3) | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +NOTE 4: For repeater operating in band n104, ACLR requirement 38 dB applies. For repeater operating in other bands, ACLR requirement 45 dB applies. + +NOTE 5: For simultaneous NCR-Fwd and NCR-MT transmission, if the NCR-MT carrier is within the NCR-Fwd then the nominal bandwidth shall be the NCR-Fwd passband. If the NCT-MT carrier is adjacent to the NCR-Fwd passband then the nominal bandwidth shall be the combined bandwidth of NCR-Fwd passband and NCR-MT carrier bandwidth. If the NCR-MT carrier is not adjacent to the passband then GACLR shall be applied in the gap between the NCR-Fwd passband and the NCR-MT carrier. + +**Table 6.5.2.2-1a: ACLR limit for UL for Local Area** + +| nominal channel bandwidth BW_{Nominal} (MHz) (NOTE 4) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband edge | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $1.5 \times BW_{Nominal}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | 2.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 31 dB | +| | 7.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 31 dB | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +NOTE 4: For simultaneous NCR-Fwd and NCR-MT transmission, if the NCR-MT carrier is within the NCR-Fwd then the nominal bandwidth shall be the NCR-Fwd passband. If the NCT-MT carrier is adjacent to the NCR-Fwd passband then the nominal bandwidth shall be the combined bandwidth of NCR-Fwd passband and NCR-MT carrier bandwidth. If the NCR-MT carrier is not adjacent to the passband then CACLR shall be applied in the gap between the NCR-Fwd passband and the NCR-MT carrier. + +The ACLR absolute *basic limit* is specified in table 6.5.2.2-2 and is applicable for both contiguous spectrum, non-contiguous spectrum and multiple bands + +**Table 6.5.2.2-2: ACLR absolute *basic* limits for DL and UL for WA class, for DL for MR class and for DL for LA class** + +| Repeater category / class | ACLR absolute basic limit | +|----------------------------------|-----------------------------------------| +| Category A Wide Area DL and UL | -13 dBm/MHz | +| Category B Wide Area DL and UL | -15 dBm/MHz | +| Medium Range DL | -25 dBm/MHz | +| Local Area DL | -32 dBm/MHz | + +**Table 6.5.2.2-3: ACLR limit in non-contiguous spectrum or multiple bands for DL (all repeater classes) and for UL for Wide Area class** + +| nominal channel bandwidth
$BW_{Nominal}$ (MHz)
(NOTE 6) | Gap between passbands or inter-passband gap size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 5, 10, 15, 20 | $W_{gap} \geq 15$ (Note 3)
$W_{gap} \geq 45$ (Note 4) | 2.5 MHz | 5 MHz NR
(Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB
(Note 5) | +| | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR
(Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB
(Note 5) | +| 25, 30, 35, 40,
45, 50, 60, 70,
80, 90, 100 | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR
(Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB
(Note 5) | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR
(Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB
(Note 5) | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +NOTE 5: For repeater operating in band n104, ACLR requirement 38 dB applies. For repeater operating in other bands, ACLR requirement 45 dB applies. + +NOTE 6: For simultaneous NCR-Fwd and NCR-MT transmission, if the NCR-MT carrier is within the NCR-Fwd then the nominal bandwidth shall be the NCR-Fwd passband. If the NCT-MT carrier is adjacent to the NCR-Fwd passband then the nominal bandwidth shall be the combined bandwidth of NCR-Fwd passband and NCR-MT carrier bandwidth. If the NCR-MT carrier is not adjacent to the passband then CACLR shall be applied in the gap between the NCR-Fwd passband and the NCR-MT carrier. + +**Table 6.5.2.2-3a: ACLR limit in non-contiguous spectrum or multiple bands for UL for Local Area class** + +| nominal channel bandwidth
BW_{Nominal} (MHz)
(NOTE 5) | Sub-block or inter-passband gap size (W_{gap}) where the limit applies (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20 | $W_{gap} \geq 15$ (Note 3)
$W_{gap} \geq 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| 25, 30, 35, 40,
45, 50, 60, 70,
80, 90, 100 | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | + +NOTE 1: $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +NOTE 5: For simultaneous NCR-Fwd and NCR-MT transmission, if the NCR-MT carrier is within the NCR-Fwd then the nominal bandwidth shall be the NCR-Fwd passband. If the NCT-MT carrier is adjacent to the NCR-Fwd passband then the nominal bandwidth shall be the combined bandwidth of NCR-Fwd passband and NCR-MT carrier bandwidth. If the NCR-MT carrier is not adjacent to the passband then CACLR shall be applied in the gap between the NCR-Fwd passband and the NCR-MT carrier. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a *gap between passbands* or the *inter-passband gap* is the ratio of: + +- the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the *gap between passbands* or the *inter-passband gap*, and +- the filtered mean power centred on a frequency channel adjacent to one of the respective *repeater type 1-C passband edges*. + +The assumed filter for the adjacent channel frequency is defined in table 6.5.3.2-4 and the filters on the assigned channels are defined in table 6.5.2.2-6. + +CACLR shall also be applied in case NCR-Fwd and NCR-MT transmit simultaneously in uplink and the NCR-Fwd passband and NCR-MT carrier are not contiguous. In this case, the gap between the NCR-Fwd passband and the NCR-MT carrier shall be considered in the same manner as a *gap between passbands*. + +For operation in *non-contiguous spectrum* or multiple bands, the CACLNR for NR carriers located on either side of the *gap between passbands* or the *inter-passband gap* shall be higher than the value specified in table 6.5.2.2-4. + +**Table 6.5.2.2-4: CACLNR limit for DL (all repeater classes) and for UL for Wide Area class** + +| nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands or inter-passband gap size ( $W_{gap}$ ) where the limit applies (MHz) | adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLNR limit | +|------------------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------------------| +| 5, 10, 15, 20 | $5 \leq W_{gap} < 15$ (Note 3) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB (Note 5) | +| | $5 \leq W_{gap} < 45$ (Note 4) | | | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $10 < W_{gap} < 20$ (Note 3) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB (Note 5) | +| | $10 \leq W_{gap} < 50$ (Note 4) | | | | | +| | $20 \leq W_{gap} < 60$ (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB (Note 5) | +| | $20 \leq W_{gap} < 30$ (Note 3) | | | | | +| | $40 < W_{gap} < 80$ (Note 4) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB
38 dB (Note 5) | +| | $40 \leq W_{gap} < 50$ (Note 3) | | | | | + +NOTE 1: $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +NOTE 5: For repeater operating in band n104, ACLR requirement 38 dB applies. For repeater operating in other bands, ACLR requirement 45 dB applies. + +The CACLNR shall be higher than the value specified in table 6.5.2.2-4a for UL Local Area. + +**Table 6.5.2.2-4a: CACLR limit for UL for Local Area** + +| nominal channel bandwidth BW_{Nominal} (MHz) | Gap between passbands or inter-passband gap size (W_{gap}) where the limit applies (MHz) | adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------| +| 5, 10, 15, 20 | $5 \leq W_{gap} < 15$ (Note 3) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $5 \leq W_{gap} < 45$ (Note 4) | | | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $10 < W_{gap} < 20$ (Note 3) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $10 \leq W_{gap} < 50$ (Note 4) | | | | | +| | $20 \leq W_{gap} < 60$ (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $20 \leq W_{gap} < 30$ (Note 3) | | | | | +| | $40 < W_{gap} < 80$ (Note 4) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 31 dB | +| | $40 \leq W_{gap} < 50$ (Note 3) | | | | | + +NOTE 1: $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel.NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ).NOTE 3: Applicable in case the *nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz.NOTE 4: Applicable in case the *nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +The CACLR absolute *minimum requirement* is specified in table 6.5.2.2-5. + +**Table 6.5.2.2-5: CACLR absolute basic limit for DL and UL for WA class, for DL for MR class and for DL for LA class** + +| Repeater category / class | CACLR absolute basic limit | +|----------------------------------|-----------------------------------| +| Category A Wide Area DL and UL | -13 dBm/MHz | +| Category B Wide Area DL and UL | -15 dBm/MHz | +| Medium Range DL | -25 dBm/MHz | +| Local Area DL | -32 dBm/MHz | + +**Table 6.5.2.2-6: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the gap between passbands or inter-passband gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +### 6.5.2.3 Minimum requirement for *RF repeater* + +The ACLR (CACLR) absolute *basic limits* or the ACLR (CACLR) *limits*, whichever is less stringent, shall apply for each *antenna connector*. + +For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all *antenna connectors* for *repeater type 1-C*. + +### 6.5.2.4 Minimum requirement for *NCR* + +#### 6.5.2.4.1 Minimum requirements for NCR-Fwd + +##### 6.5.2.4.1.1 Minimum requirements for NCR-Fwd type 1-C + +The ACLR (CACLR) absolute *basic limits* or the ACLR (CACLR) *limits*, whichever is less stringent, shall apply for each *antenna connector*. + +For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all *antenna connectors* for *NCR-Fwd type 1-C*. + +##### 6.5.2.4.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +The ACLR (CACLR) absolute *basic limits* + X (where $X = 10\log_{10}(N_{\text{TXU, countedpercell}})$ for DL and for WA UL and $X=0$ for LA UL) or the ACLR (CACLR) *limits*, whichever is less stringent, shall apply for each *TAB connector TX min cell group*. For joint transmission of NCR-Fwd and NCR-MT in uplink, the limits shall apply to the sum of emissions from both NCR-Fwd and NCR-MT. + +NOTE: Conformance to the *NCR-Fwd type 1-H* ACLR requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The ratio of the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the assigned channel frequency to the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be greater than or equal to the ACLR *basic limit* of the repeater. This shall apply for each *TAB connector TX min cell group*. + +Or + +- 2) The ratio of the filtered mean power at the *TAB connector* centred on the assigned channel frequency to the filtered mean power at this *TAB connector* centred on the adjacent channel frequency shall be + +greater than or equal to the ACLR *basic limit* of the repeater for every *TAB connector* in the *TAB connector TX min cell group*, for each *TAB connector TX min cell group*. + +In case the ACLR (CACLR) absolute *basic limit of repeater type 1-H* are applied, the conformance can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be less than or equal to the ACLR (CACLR) absolute *basic limit* + X of the repeater. This shall apply to each *TAB connector TX min cell group*. + +Or + +- 2) The filtered mean power at each *TAB connector* centred on the adjacent channel frequency shall be less than or equal to the ACLR (CACLR) absolute *basic limit* + X of the repeater scaled by $X - 10\log_{10}(n)$ for every *TAB connector* in the *TAB connector TX min cell group*, for each *TAB connector TX min cell group*, where *n* is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +#### 6.5.2.4.2 Minimum requirement for NCR-MT + +##### 6.5.2.4.2.1 Minimum requirements for NCR-MT type 1-C + +For WA NCR-MT type 1-C, the BS ACLR basic requirements specified in clause 6.6.3 and 6.6.4 in TS 38.104 apply. + +For LA NCR-MT type 1-C, the UE ACLR requirements specified in clause 6.5.2.5 in TS 38.101-1 apply. + +For simultaneous transmission the limits apply for sum of NCR-MT transmission and NCR-Fwd transmission + +##### 6.5.2.4.2.2 Minimum requirements for NCR-MT type 1-H + +Limits for NCR-MT type 1-H apply to the sum of emissions across all TAB connectors. + +For WA NCR-MT type 1-H, the repeater relative ACLR requirements specified in clause 6.6.3 and 6.6.4 in TS 38.104 apply. For Absolute ACLR requirements, the following scaling factor should be added on top of NCR-MT type 1-C basic limit requirements. + +$$10\log(N_{\text{TXU,counted}}), \text{ where } N_{\text{TXU,counted}} = \min(N_{\text{TXU,active}}, 8)$$ + +For LA NCR-MT type 1-H, the UE ACLR requirements specified in clause 6.5.2.5 in TS 38.101-1 apply. + +For simultaneous transmission the limits apply for sum of NCR-MT transmission and NCR-Fwd transmission. + +### 6.5.3 Operating band unwanted emissions + +#### 6.5.3.1 General + +Unless otherwise stated, the operating band unwanted emission (OBUE) *basic* limits for DL are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported downlink *operating band*. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.5.1-1 for the NR *operating bands*. + +Unless otherwise stated, the operating band unwanted emission (OBUE) *basic* limits for UL are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported uplink *operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported uplink *operating band*. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.5.1-2 for the NR *operating bands*. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. In addition, for *repeater* operating in *non-contiguous spectrum*, the *basic limits* apply inside any *gap between passbands*. In addition, for a *repeater* operating in multiple bands, the *basic limits* apply inside any *inter-passband gap*. + +*Basic Limits* are specified in the tables below, where: + +- $\Delta f$ is the separation between the *passband edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the *passband edge* frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink *operating band* of *repeater type 1-C DL* and uplink *operating band* of *repeater type 1-C UL*, where $\Delta f_{\text{OBUE}}$ is defined in tables 6.5.1-1 and 6.5.1-2. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band connector* inside any *inter-passband gaps* with $W_{\text{gap}} < 2 * \Delta f_{\text{OBUE}}$ , a combined *basic limit* shall be applied which is the cumulative sum of the *basic limit* requirement specified at the *repeater type 1-C passband edges* on each side of the *inter-passband gap*. The *basic limit* requirement for *repeater type 1-C Bandwidth edge* is specified in clauses 6.5.3.2.1 to 6.5.3.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *repeater type 1-C passband edge* frequency and the nominal -3 dB point of the measuring filter closest to the *repeater type 1-C passband edge*. +- $f_{\text{offset}}$ is the separation from the *repeater type 1-C passband edge* frequency to the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the *inter-passband gap* minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band connector* of DL, the operating band unwanted emission basic limits apply also in a supported downlink *operating band* without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported downlink *operating band*. In this case, no cumulative *basic limit* is applied in the *inter-band gap* between a supported downlink *operating band* with carrier(s) transmitted and a supported downlink *operating band* without any carrier transmitted and + +- In case the *inter-band gap* between a supported downlink *operating band* with carrier(s) transmitted and a supported downlink *operating band* without any carrier transmitted is less than $2 * \Delta f_{\text{OBUE}}$ , $f_{\text{offsetmax}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the outermost edges of the two supported downlink *operating bands* and the operating band unwanted emission minimum requirement of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission *basic limit* of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), shall apply from $\Delta f_{\text{OBUE}}$ MHz + +below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ MHz above the highest frequency of the supported downlink *operating band* without any carrier transmitted. + +For a *multi-band connector* of UL, the operating band unwanted emission limits apply also in a supported uplink *operating band* without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported uplink *operating band*. In this case, no cumulative *basic limit* is applied in the *inter-band gap* between a supported uplink *operating band* with carrier(s) transmitted and a supported uplink *operating band* without any carrier transmitted and + +- In case the inter-band gap between a supported uplink operating band with carrier(s) transmitted and a supported uplink operating band without any carrier transmitted is less than $2 \cdot \Delta f_{\text{OBUE}}$ , $f_{\text{offsetmax}}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the outermost edges of the two supported uplink operating bands and the operating band unwanted emission *basic limit* of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both uplink bands. +- In other cases, the operating band unwanted emission basic limits of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\text{max}}$ ), shall apply from $\Delta f_{\text{OBUE}}$ MHz below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ MHz above the highest frequency of the supported uplink operating band without any carrier transmitted. + +In addition, inside any *gap between passbands* for a *single-band connector* operating in *non-contiguous spectrum*, a combined basic limit shall be applied which is the cumulative sum of the basic limit specified for the adjacent *sub-blocks* on each side of the *gap between passbands*. The basic limit for each *sub-block* is specified in clauses 6.5.3.2.1 to 6.5.3.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *sub-block* edge frequency and the nominal -3 dB point of the measuring filter closest to the *sub-block* edge. +- $f_{\text{offset}}$ is the separation between the *sub-block* edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the *gap between passbands* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For Wide Area *repeater type 1-C*, the basic limits of either clause 6.5.3.2.1 (Category A limits) or clause 6.5.3.2.2 (Category B limits) shall apply. + +For Medium Range *repeater type 1-C*, the basic limits in clause 6.5.3.2.3 shall apply (Category A and B). + +For Local Area *repeater type 1-C*, the basic limits of clause 6.5.3.2.4 shall apply (Category A and B). + +The application of either Category A or Category B basic limits shall be the same as for Transmitter spurious emissions in clause 6.5.4. + +In addition to, for the part of passband where there is no input signal at DL input port, the basic limits in Table 6.5.2.2-2 shall apply. In addition to, for the part of passband where there is no input signal at UL input port, the basic limits in clause 6.5.3.2.6 shall apply. + +### 6.5.3.2 Basic limits + +#### 6.5.3.2.1 basic limits for Wide Area repeater type 1-C (Category A) + +For repeater operating in Bands n5, n8, n12, n13, n14, n18, n26, n28, n29, n31, n71, n72, n85, basic limits are specified in table 6.5.3.2.1-1. + +**Table 6.5.3.2.1-1: Wide Area operating band unwanted emission basic limits (NR bands below 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 3) | 100 kHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band*, the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission limits within *gaps between passbands* shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The basic limit is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For repeater operating in Bands n1, n2, n3, n7, n24, n25, n30, n34, n38, n39, n40, n41, n48, n50, n54, n65, n66, n70, n74, n75, n77, n78, n79, n90, n92, n94, n109, basic limits are specified in table 6.5.3.2.1-2. + +**Table 6.5.3.2.1-2: Wide Area *operating band* unwanted emission basic limits (NR bands above 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 3) | 1MHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band*, the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*, where the contribution from the far-end *sub-block* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The basic limit is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.5.3.2.2 Basic limit for Wide Area *repeater type 1-C* (Category B) + +For Category B Operating band unwanted emissions, there are two options for the *basic limits* that may be applied regionally. Either the *basic limits* in clause 6.5.3.2.2.1 or clause 6.5.3.2.2.2 shall be applied. + +##### 6.5.3.2.2.1 Category B basic limits (Option 1) + +For *repeater type 1-C* operating in Bands n5, n8, n12, n20, n26, n28, n29, n31, n67, n71, n72, n85, the basic limits are specified in table 6.5.3.2.2.1-1: + +**Table 6.5.3.2.2.1-1: Wide Area operating band unwanted emission *basic limits* (NR bands below 1 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm (Note 3) | 100 kHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band*, the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For repeater operating in Bands n1, n2, n3, n7, n25, n34, n38, n39, n40, n41, n48, n50, n65, n66, n70, n75, n77, n78, n79, n90, n92, n94, n109 basic limits are specified in table 6.5.3.2.2.1-2. + +**Table 6.5.3.2.2.1-2: Wide Area *repeater type 1-C* operating band unwanted emission basic limits for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 3) | 1MHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band*, the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*, where the contribution from the far-end *sub-block* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The basic limit is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For *repeater type 1-C* operating in Band n104, the *basic* limits are specified in tables 6.5.3.2.2.1-2a: + +**Table 6.5.3.2.2.1-2a: Wide Area operating band unwanted emission basic limits for band n104 for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{\max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 3) | 1MHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band*, the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*, where the contribution from the far-end *sub-block* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block*. Exception is $\Delta f \geq 40 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission basic limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 40 \text{ MHz}$ . + +### 6.5.3.2.2.2 Category B *basic limits* (Option 2) + +The basic limits in this clause are intended for Europe and may be applied regionally for *repeater type 1-C* operating in bands n1, n3, n7, n8, n38, n65. + +For a *repeater type 1-C* operating in bands n1, n3, n7, n8, n38 or n65, *basic limits* are specified in Table 6.5.3.2.2.2-1: + +**Table 6.5.3.2.2.2-1: For a *repeater type 1-C* operating in bands n1, n3, n7, n8, n38 or n65, basic limits are specified in Table 6.5.3.2.2.2-1:** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -13 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 3) | 1 MHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band*, the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*, where the contribution from the far-end *sub-block* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +### 6.5.3.2.3 Basic limits for Medium Range *repeater type 1-C* (Category A and B) for DL + +For Medium Range *repeater* for DL, *basic limits* are specified in table 6.5.3.2.3-1 and table 6.5.3.2.3-2. + +For the tables in this clause for *repeater*, $P_{\text{rated},x} = P_{\text{rated,p,AC}} - 10 * \log(\text{ceil}(\text{BW}_{\text{Passband}}/20 \text{ MHz}))$ + +**Table 6.5.3.2.3-1: Medium Range *repeater operating band* unwanted emission *basic limits*, $31 < P_{\text{rated},x} \leq 38 \text{ dBm}$** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated},x} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated},x} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 3) | 100 kHz | + +NOTE 1: For a *repeater* DL supporting *non-contiguous spectrum* operation within any *operating band* the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be $\min(P_{\text{rated},x} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For *repeater* operating in Band n104, the limits are specified in Table 6.5.3.2.3-1a and Table 6.5.3.2.3-2a. + +**Table 6.5.3.2.3-1a. Medium Range *repeater operating band* unwanted emission *basic limits* for band n104, $31 < P_{\text{rated},x} \leq 38 \text{ dBm}$** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{\max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated},x} - 60 \text{ dB}$ | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated},x} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 3) | 100 kHz | + +NOTE 1: For a *repeater* DL supporting *non-contiguous spectrum* operation within any *operating band* the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*. Exception is $\Delta f \geq 40 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission basic limits within *gaps between passbands* shall be $\min(P_{\text{rated},x} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 40 \text{ MHz}$ . + +**Table 6.5.3.2.3-2: Medium Range repeater operating band unwanted emission basic limits, $P_{\text{rated,x}} \leq 31$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-22 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm (Note 3) | 100 kHz | + +NOTE 1: For a *repeater* DL supporting *non-contiguous spectrum* operation within any *operating band* the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be -29dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.5.3.2.3-2a. Medium Range repeater operating band unwanted emission basic limits for band 104, $P_{\text{rated,x}} \leq 31$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | basic limits (Notes 1, 2) | Measurement bandwidth | +|------------------------------------------------------------------------|--------------------------------------------------------------------------------|---------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{\max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\max})$ | -29 dBm | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm | 100 kHz | + +NOTE 1: For a *repeater* DL supporting *non-contiguous spectrum* operation within any *operating band* the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*. Exception is $f \geq 40 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission basic limits within *gaps between passbands* shall be -29dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The *basic limit* is not applicable when $\Delta f_{\max} < 40 \text{ MHz}$ . + +### 6.5.3.2.4 Basic limits for Local Area repeater type 1-C (Category A and B) + +For Local Area, *basic limits* are specified in table 6.5.3.2.4-1. + +**Table 6.5.3.2.4-1: Local Area repeater operating band unwanted emission basic limits** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-30 \text{ dBm} - \frac{7}{5} \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 10) | 100 kHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band* the emission basic limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passbands*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passbands*, where the emission basic limits within *gaps between passbands* shall be -37dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap* + +NOTE 3: The basic limit is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For *repeater* operating in Band n104, *basic limits* are specified in Table 6.5.3.2.4-1a. + +**Table 6.5.3.2.4-1a. Local Area repeater operating band unwanted emission basic limits for band n104** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Notes 1, 2) | Measurement bandwidth | +|------------------------------------------------------------------------|--------------------------------------------------------------------------------|---------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{\max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm | 100 kHz | + +NOTE 1: For a *repeater* supporting *non-contiguous spectrum* operation within any *operating band* the emission basic limits within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *sub-block gap*. Exception is $\Delta f \geq 40 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *sub-block gap*, where the emission basic limits within *sub-block gaps* shall be -37dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission basic limits within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *RF Bandwidth* on each side of the *Inter RF Bandwidth gap* + +NOTE 3: The basic limit is not applicable when $\Delta f_{\max} < 40 \text{ MHz}$ . + +### 6.5.3.2.5 Additional *basic limits* + +#### 6.5.3.2.5.1 Limits in FCC Title 47 + +In addition to the basic limits in clauses 6.5.3.2.1, 6.5.3.2.2, 6.5.3.2.3 and 6.5.3.2.4, the *repeater type 1-C* may have to comply with the applicable emission basic limits established by FCC Title 47 [10], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +#### 6.5.3.2.5.2 Protection of DTT + +In certain regions the following basic limit may apply for protection of DTT. For *repeater type 1-C* operating in Band n20, the level of emissions in the band 470-790 MHz, measured in an 8 MHz filter bandwidth on centre frequencies $F_{\text{filter}}$ according to table 6.5.3.2.5.2-1, a basic limit $P_{\text{EM,N}}$ is declared by the manufacturer. This basic limit applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.5.3.2.5.2-1: Declared emissions *basic limit* for protection of DTT** + +| Filter centre frequency,
$F_{\text{filter}}$ | Measurement
bandwidth | Declared emission
basic limit (dBm) | +|---------------------------------------------------------------------|--------------------------|-----------------------------------------------| +| $F_{\text{filter}} = 8 \cdot N + 306$ (MHz);
$21 \leq N \leq 60$ | 8 MHz | $P_{\text{EM,N}}$ | + +Note: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the repeater emissions at the *antenna connector* and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the repeater needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in TS 36.104 [20], annex F. + +#### 6.5.3.2.6 Basic limit inside passband with no UL input signal + +The requirement is defined as a function of frequency offset from the edge of some part of passband with non-zero input signal. The requirement is measured as the ratio of the repeater output power in a zero-input basic unit to the repeater output power in a non-zero input basic unit. Basic unit equal to 360KHz. + +The average of the basic limits over 10 sub-frames shall not exceed the values specified in Table 6.5.3.2.6-1. + +**Table 6.5.3.2.6-1: Basic limits inside passband with no UL input signal** + +| Parameter description | Unit | Basic Limit (NOTE 1) | | Applicable Frequencies | +|-----------------------|------|----------------------|----------------------------------------------|----------------------------------------| +| General | dB | | | Any zero-input basic unit (NOTE 2) | +| IQ Image | dB | -28 | Image frequencies when output power > 10 dBm | Image frequencies (NOTES 2, 3) | +| | | -25 | Image frequencies when output power ≤ 10 dBm | | +| Carrier leakage | dBc | -28 | Output power > 10 dBm | Carrier leakage frequency (NOTES 4, 5) | +| | | -25 | 0 dBm ≤ Output power ≤ 10 dBm | | +| | | -20 | -30 dBm ≤ Output power < 0 dBm | | +| | | -10 | -40 dBm ≤ Output power < -30 dBm | | + +NOTE 1: requirement is evaluated in each zero-input basic unit. For each such basic unit, the minimum requirement is calculated as the higher of - 30 dB and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 10. + +NOTE 2: The measurement bandwidth is one basic unit and the limit is expressed as a ratio of measured power in one zero-input basic unit to the measured average power per non-zero input basic unit, where the averaging is done across all non-zero input parts of the passband. + +NOTE 3: The applicable frequencies for this limit are those that are enclosed in the reflection of the non-zero input part of passband, based on symmetry with respect to the carrier leakage frequency, but excluding any non-zero input basic units. + +NOTE 4: The measurement bandwidth is 1 basic unit and the limit is expressed as a ratio of measured power in one zero-input basic unit to the measured total power in all non-zero input basic units + +NOTE 5: The applicable frequencies are those that are enclosed either in the basic unit containing the carrier leakage frequency, or in the two basic units immediately adjacent to the carrier leakage frequency but excluding any non-zero input basic units. + +NOTE 6: $L_{CRB}$ is the . + +NOTE 7: $N_{RB}$ is the . + +NOTE 8: $EVM$ is the limit specified in Table 6.6.2.2-1 for the modulation format used in the non-zero input basic units.. + +NOTE 9: is the starting frequency offset between the end of nearest non-zero input basic unit and the measured zero-input basic unit (e.g. $\Delta_{RB} = 1$ or $\Delta_{RB} = -1$ for the first zero-input basic unit outside of the non-zero input part of passband. + +NOTE 10: is an average of the transmitted power over 10 sub-frames normalized by the number of non-zero input basic units, measured in dBm. + +### 6.5.3.3 Minimum requirement for NCR + +#### 6.5.3.3.1 Minimum requirement for NCR-Fwd + +##### 6.5.3.4.1.1 Minimum requirement for NCR-Fwd type 1-C + +The operating band unwanted emissions for *NCR-Fwd type 1-C* for each *antenna connector* shall be below the applicable *basic limits* defined in clause 6.5.3.2. + +For Band n41 and n90 operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all *antenna connectors* for *NCR-Fwd type 1-C*. + +For joint transmission of NCR-Fwd and NCR-MT in the uplink, the operating band unwanted emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +##### 6.5.3.4.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +The operating band unwanted emissions requirements for *NCR-Fwd type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.5.3.2, the power summation emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed a limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{TXU, countedpercell}})$ for DL and for UL WA and $X=0$ for UL LA. + +For joint transmission of NCR-Fwd and NCR-MT in the uplink, the operating band unwanted emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +NOTE: Conformance to the *repeater type 1-H* spurious emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the limit as defined in this clause for the respective frequency span. + +Or + +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the *repeater type 1-H* limit as defined in this clause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where n is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +#### 6.5.3.3.2 Minimum requirement for NCR-MT + +##### 6.5.3.3.2.1 Minimum requirements for NCR-MT type 1-C + +For LA NCR-MT type 1-C, regardless of simultaneous transmission with NCR- Fwd is transmitting, the UE spectrum emission mask requirements specified in clause 6.5.2 in TS 38.101-1 applies . + +For WA NCR-MT type 1-C, regardless of simultaneous transmission between NCR-MT and NCR-Fwd, the BS requirements specified in clause 6.6.4 in TS 38.104 apply. + +For simultaneous transmission the limits apply for sum of NCR-MT transmission and NCR-Fwd transmission. + +##### 6.5.3.3.2.2 Minimum requirements for NCR-MT type 1-H + +Limits for NCR-MT type 1-H apply to the sum of emissions across all TAB connectors. + +For LA NCR-MT type 1-H, regardless of simultaneous transmission with NCR- Fwd is transmitting, the UE spectrum emission mask requirements specified in clause 6.5.2 in TS 38.101-1 applies without scaling factor allowed. + +For WA NCR-MT type 1-H, the repeater basic requirements specified in clause 6.6.4 in TS 38.104 relaxed with following scaling factor apply. + +$$10\log(N_{\text{TXU,counted}}), \text{ where } N_{\text{TXU,counted}} = \min(N_{\text{TXU,active}}, 8)$$ + +For simultaneous transmission the limits apply for sum of NCR-MT transmission and NCR-Fwd transmission. + +## 6.5.4 Transmitter spurious emissions + +### 6.5.4.1 General + +The transmitter spurious emission limits shall apply from 9 kHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 6.5.1-1. For some *operating bands*, the upper limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the downlink *operating band*, as specified in ITU-R recommendation SM.329 [5]. + +For a *multi-band connector*, for each supported *operating band* together with $\Delta f_{\text{OBUE}}$ around the band is excluded from the transmitter spurious emissions requirement. + +The requirements shall apply whatever the type of transmitter considered (single carrier or multi-carrier). It applies for all transmission modes foreseen by the manufacturer's specification. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all *antenna connectors* for *Repeater type 1-C* shall not exceed the *minimum requirements* defined in clause 6.5.5.2. + +### 6.5.4.2 Basic limits + +#### 6.5.4.2.1 General transmitter spurious emissions *basic limits* + +The *basic limits* of either table 6.5.4.2.1-1, table 6.5.4.2.1-2 (Category A limits) or table 6.5.4.2.1-3 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for operating band unwanted emissions in clause 6.5.3. + +**Table 6.5.4.2.1-1: General transmitter spurious emission *basic limits* for DL in FR1, Category A** + +| Spurious frequency range | Basic limit | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|--------------------|------------------------------|------------------------| +| 9 kHz – 150 kHz | -13 dBm | 1 kHz | Note 1 | +| 150 kHz – 30 MHz | | 10 kHz | Note 1 | +| 30 MHz – 1 GHz | | 100 kHz | Note 1 | +| 1 GHz – 12.75 GHz | | 1 MHz | Note 1, Note 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL operating band in GHz | | 1 MHz | Note 1, Note 2, Note 3 | + +NOTE 1: *Measurement bandwidths* as in ITU-R SM.329 [5], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. +NOTE 3: For DL, this spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the DL *operating band* is reaching beyond 12.75 GHz. + +**Table 6.5.4.2.1-2: General transmitter spurious emission *basic limits* for UL in FR1, Category A** + +| Spurious frequency range | Basic limits | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|---------------------|------------------------------|------------------------| +| 9 kHz – 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz – 30 MHz | | 10 kHz | Note 1 | +| 30 MHz – 1 GHz | | 100 kHz | Note 1 | +| 1 GHz – 12.75 GHz | -30 dBm | 1 MHz | Note 1, Note 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL operating band in GHz | | 1 MHz | Note 1, Note 2, Note 3 | + +NOTE 1: *Measurement bandwidths* as in ITU-R SM.329 [5], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. +NOTE 3: For UL, this spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the UL *operating band* is reaching beyond 12.75 GHz. + +**Table 6.5.4.2.1-3: General transmitter spurious emission *basic limits* in FR1, Category B** + +| Spurious frequency range | basic limits | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|----------------------------|-------------------------------------|------------------------| +| 9 kHz – 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz – 30 MHz | | 10 kHz | Note 1 | +| 30 MHz – 1 GHz | | 100 kHz | Note 1 | +| 1 GHz – 12.75 GHz | -30 dBm | 1 MHz | Note 1, Note 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL operating band in GHz | | 1 MHz | Note 1, Note 2, Note 3 | + +NOTE 1: *Measurement bandwidths* as in ITU-R SM.329 [5], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. +NOTE 3: For DL, this spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the DL *operating band* is reaching beyond 12.75 GHz. +For UL, this spurious frequency range applies only for *operating bands* for which the 5th harmonic of the upper frequency edge of the UL *operating band* is reaching beyond 12.75 GHz. + +#### 6.5.4.2.2 Additional spurious emissions *basic limits* + +These *basic limits* may be applied for the protection of system operating in other frequency ranges. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the repeater-Node, or they may be set by local or regional regulation as a mandatory requirement for an NR *operating band*. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in clause 4.5. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. + +The spurious emission *basic limits* are provided in table 6.5.4.2.2-1 where requirements for co-existence with the system listed in the first column apply for *repeater type 1-C*. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.5.4.2.2-1 apply for each supported *operating band*. + +**Table 6.5.4.2.2-1: Repeater type 1-C spurious emissions basic limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | basic limits | Measurement bandwidth | Note | +|-----------------------------------------|-----------------------------------------------------|----------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n8 | +| | 876 – 915 MHz | -61 dBm | 100 kHz | For the frequency range 880-915 MHz, this basic limit does not apply to repeater operating in band n8, since it is already covered by the basic limit in clause 6.5.5.2.2. | +| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n3. | +| | 1710 – 1785 MHz | -61 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n3, since it is already covered by the basic limit in clause 6.5.5.2.2. | +| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n2, n25 or band n70. | +| | 1850 – 1910 MHz | -61 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n2 or n25 since it is already covered by the basic limit in clause 6.6.5.2.2. | +| GSM850 or | 869 – 894 MHz | -57 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n5 or n26. | +| CDMA850 | 824 – 849 MHz | -61 dBm | 100 kHz | This basic limit does not apply to repeater operating in band n5 or n26, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD | 2110 – 2170 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n1 or n65 | +| Band I or E-UTRA Band 1 or NR Band n1 | 1920 – 1980 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n1 or n65, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD | 1930 – 1990 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n2 or n70. | +| Band II or E-UTRA Band 2 or NR Band n2 | 1850 – 1910 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n2, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD | 1805 – 1880 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n3. | +| Band III or E-UTRA Band 3 or NR Band n3 | 1710 – 1785 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n3, since it is already covered by the basic limit in clause 6.6.5.2.2. | + +| | | | | | +|---------------------------------------------------------------|---------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66 | +| | 1710 – 1755 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n5 or n26. | +| | 824 – 849 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n5 or n26, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 – 890 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n18. | +| | 815 – 830 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n18, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| | 830 – 845 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 – 2690 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n7. | +| | 2500 – 2570 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n7, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n8. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n8, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n3. | + +| | | | | | +|----------------------------------------------------------------|---------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1749.9 – 1784.9 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n3, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD
Band X or
E-UTRA Band
10 | 2110 – 2170 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66 | +| | 1710 – 1770 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD
Band XI or XXI
or
E-UTRA Band
11 or 21 | 1475.9 – 1510.9 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n50, n74, n75, n92, n94 or n109. | +| | 1427.9 – 1447.9 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n50, n74, n75, n92, n94 or n109. | +| UTRA FDD
Band XII or
E-UTRA Band
12 or NR Band
n12 | 729 – 746 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n12 or n85. | +| | 699 – 716 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n12 or n85, since it is already covered by the basic limit in clause 6.6.5.2.2.
For NR repeater operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| UTRA FDD
Band XIII or
E-UTRA Band
13 | 746 – 756 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n13. | +| | 777 – 787 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n13, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD
Band XIV or
E-UTRA Band
14 or NR band
n14 | 758 – 768 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n14. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 788 – 798 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n14, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 17 | 734 – 746 MHz | -52 dBm | 1 MHz | | +| | 704 – 716 MHz | -49 dBm | 1 MHz | For NR repeater operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 – 821 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n20 or n28. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n20, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n48, n77 or n78. | +| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n77 or n78. | +| E-UTRA Band 24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n24. | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n24, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n2, n25 or n70. | +| | 1850 – 1915 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n25 since it is already covered by the basic limit in clause 6.6.5.2.2. For repeater operating in Band n2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.6.5.2.2. | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n5 or n26. | + +| | | | | | +|---------------------------------------|-------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 814 – 849 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n26 since it is already covered by the basic limit in clause 6.6.5.2.2. For repeater operating in Band n5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.6.5.2.2. | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n5. | +| | 807 – 824 MHz | -49 dBm | 1 MHz | This basic limit also applies to repeater operating in Band n28, starting 4 MHz above the Band n28 downlink operating band (Note 5). | +| E-UTRA Band 28 or NR Band n28 | 758 – 803 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n20, n67 or n28. | +| | 703 – 748 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n28, since it is already covered by the basic limit in clause 6.6.5.2.2.
For repeater operating in band n67, it applies for 703 MHz to 736 MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n29 or n85 | +| E-UTRA Band 30 or NR Band n30 | 2350 – 2360 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n30 | +| | 2305 – 2315 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n30, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n31 or n72. | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n31, since it is already covered by the basic limit in clause 6.6.5.2.2. This basic limit does not apply to repeater operating in band n72. | +| UTRA FDD band XXXII or E-UTRA band 32 | 1452 – 1496 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n50, n74, n75, n92, n94 or n109. | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -52 dBm | 1 MHz | | + +| | | | | | +|---------------------------------------------------|-----------------|---------|-------|---------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 – 2025 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n34. | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n2 or n25. | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n39. | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n30 or n40. | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n41, n53 or [n90]. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n48, n77 or n78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n48, n77 or n78. | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n28. | +| E-UTRA Band 45 | 1447 – 1467 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 46 | 5150 – 5925 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 47 | 5855 – 5925 MHz | -52 dBm | 1 MHz | | + +| | | | | | +|-------------------------------|-------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n48, n77 or n78. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n41, n53 or n90. | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n54 | +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n1 or n65. | +| | 1920 – 2010 MHz | -49 dBm | 1 MHz | For repeater operating in Band n1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.6.5.2.2.
This basic limit does not apply to repeater operating in band n65, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66. | +| | 1710 – 1780 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 67 | 738 – 758 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n28 or n67. | +| E-UTRA Band 68 | 753 -783 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n28. | +| | 698-728 MHz | -49 dBm | 1 MHz | For repeater operating in Band n28, this basic limit applies between 698 MHz and 703 MHz, while the rest is covered in clause 6.6.5.2.2. | +| E-UTRA Band 69 | 2570 – 2620 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n38. | +| E-UTRA Band 70 or NR Band n70 | 1995 – 2020 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n2, n25 or n70 | + +| | | | | | +|-------------------------------|-----------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n70, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n71 or n105 | +| | 663 – 698 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n71 or n105, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 72 or NR Band n72 | 461 – 466 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n31 or n72. | +| | 451 – 456 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n72, since it is already covered by the basic limit in clause 6.6.5.2.2. This basic limit does not apply to BS operating in band n31. | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n50, n74, n75, n92, n94 or n109. | +| | 1427 – 1470 MHz | -49 dBm | 1MHz | This basic limit does not apply to repeater operating in band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n75, n76, n91, n92, n93, n94 or n109. | +| NR Band n77 | 3.3 – 4.2 GHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n48, n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n48, n77 or n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n79 | +| NR Band n80 | 1710 – 1785 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n3, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| NR Band n81 | 880 – 915 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n8, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| NR Band n82 | 832 – 862 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n20, since it is already covered by the basic limit in clause 6.6.5.2.2. | + +| | | | | | +|--------------------------------|-----------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n83 | 703 – 748 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n28, since it is already covered by the basic limit in clause 6.6.5.2.2.
For repeater operating in Band n67, it applies for 703 MHz to 736 MHz. | +| NR Band n84 | 1920 – 1980 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n1, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 85 and NR Band n85 | 728 – 746 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n12 or n85.
For NR repeater operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| | 698 – 716 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n12 or n85, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| NR Band n86 | 1710 – 1780 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n66, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| NR Band n89 | 824 – 849 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n5, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n75, n76 or n109. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n20, since it is already covered by the basic limit in clause 6.6.5.5.1.2. | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n74, n75, n76 or n109. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n20, since it is already covered by the basic limit in clause 6.6.5.5.1.2. | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n75, n76 or n109. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n8, since it is already covered by the basic limit in clause 6.6.5.5.1.2. | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n50, n51, n74, n75, n76 or n109. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n8, since it is already covered by the basic limit in clause 6.6.5.5.1.2. | +| NR Band n95 | 2010 – 2025 MHz | -52 dBm | 1 MHz | | +| NR Band n96 | 5925 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n97 | 2300 – 2400MHz | -52 dBm | 1 MHz | | + +| | | | | | +|-----------------|---------------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------| +| NR Band n98 | 1880 – 1920MHz | -52 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n24, since it is already covered by the basic limit in clause 6.5.5.2.2. | +| NR band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n101. | +| NR Band n102 | 5925 – 6425 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -52 dBm | 1 MHz | | +| | 787 – 788 MHz | -49 dBm | 1 MHz | | +| NR Band n104 | 6425 – 7125 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in Band n104 | +| NR band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n71 or n105 | +| | 663 – 703 MHz | -49 dBm | 1 MHz | This basic limit does not apply to repeater operating in band n105, since it is already covered by the basic limit in clause 6.6.5.2.2. | +| E-UTRA Band 106 | 935 - 940 MHz | -52 dBm | 1 MHz | | +| | 896 – 901 MHz | -49 dBm | 1 MHz | | +| NR band n109 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This basic limit does not apply to BS operating in Band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109 | +| | 703 – 733 MHz | -49 dBm | 1 MHz | This basic limit does not apply to BS operating in band n109, since it is already covered by the basic limit in clause 6.6.6.5.2.4. | + +NOTE 1: As defined in the scope for spurious emissions in this clause, except for the cases where the noted basic limits apply to a repeater operating in Band n28, the co-existence requirements in table 6.5.4.2.3 -1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the downlink *operating band* (see table 5.2-1). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: Table 6.5.5.2.3 -1 assumes that two *operating bands*, where the frequency ranges in table 5.2-1 would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +NOTE 3: For unsynchronized operation, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +NOTE 4: For NR Band n28 repeater, specific solutions may be required to fulfil the spurious emissions limits for repeater for co-existence with E-UTRA Band 27 UL *operating band*. + +NOTE 5: For NR Band n29 repeater, specific solutions may be required to fulfil the spurious emissions limits for NR repeater for co-existence with UTRA Band XII, E-UTRA Band 12 or NR Band n12 UL operating band, E-UTRA Band 17 UL operating band or E-UTRA Band 85 UL or NR Band n85 UL operating band. + +The following requirement may be applied for the protection of PHS. This requirement is also applicable at specified frequencies falling between $\Delta f_{\text{OBUE}}$ below the lowest repeater transmitter frequency of the downlink *operating band* and $\Delta f_{\text{OBUE}}$ above the highest repeater transmitter frequency of the downlink *operating band*. $\Delta f_{\text{OBUE}}$ is defined in clause 6.5.1. + +The spurious emission *basic limit* for this requirement are: + +**Table 6.5.4.2.3-2: Repeater spurious emissions basic limit for repeater for co-existence with PHS for DL** + +| Frequency range | basic limit | Measurement Bandwidth | Note | +|---------------------|--------------------|------------------------------|-------------------------------------------------------------------------------| +| 1884.5 – 1915.7 MHz | -41 dBm | 300 kHz | Applicable when co-existence with PHS system operating in 1884.5 – 1915.7 MHz | + +In certain regions, the following requirement may apply to NR repeater operating in Band n50 and n75 within the 1432 – 1452 MHz, and in Band n51 and Band n76. The *basic limit* are specified in Table 6.5.4.2.3-4. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the repeater downlink *operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the repeater downlink *operating band*. + +**Table 6.5.4.2.3-4: Additional operating band unwanted emission basic limit for NR repeater operating in Band n50 and n75 within 1432 – 1452 MHz, and in Band n51 and n76** + +| Filter centre frequency, $F_{\text{filter}}$ | basic limit | Measurement Bandwidth | +|----------------------------------------------|--------------------|------------------------------| +| $F_{\text{filter}} = 1413.5$ MHz | -42 dBm | 27 MHz | + +In certain regions, the following requirement may apply to repeater operating in NR Band n50 and n75 within 1492-1517 MHz and in Band n74 within 1492-1518 MHz. The maximum level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 6.5.4.2.3-5, shall be defined according to the *basic limits* $P_{\text{EM,n50/n75,a}}$ nor $P_{\text{EM,n50/n75,b}}$ declared by the manufacturer. + +**Table 6.5.4.2.3-5: Operating band n50, n74 and n75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared basic limits (dBm) | Measurement bandwidth | +|-------------------------------------------------------|------------------------------------|------------------------------| +| $1518.5$ MHz $\leq F_{\text{filter}} \leq 1519.5$ MHz | $P_{\text{EM,n50/n75,a}}$ | 1 MHz | +| $1520.5$ MHz $\leq F_{\text{filter}} \leq 1558.5$ MHz | $P_{\text{EM,n50/n75,b}}$ | 1 MHz | + +In certain regions, the following requirement shall be applied to repeater operating in Band n13 and n14 to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable + +at the frequency range from 10 MHz below the lowest frequency of the repeater downlink operating band up to 10 MHz above the highest frequency of the repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.2.3-6: Repeater spurious emissions basic limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Basic limit | Measurement Bandwidth | +|----------------|-----------------|-------------|-----------------------| +| n13 | 763 - 775 MHz | -46 dBm | 6.25 kHz | +| n13 | 793 - 805 MHz | -46 dBm | 6.25 kHz | +| n14 | 769 - 775 MHz | -46 dBm | 6.25 kHz | +| n14 | 799 - 805 MHz | -46 dBm | 6.25 kHz | + +In certain regions, the following requirement may apply to NR repeater operating in Band n30. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the repeater downlink operating band up to 10 MHz above the highest frequency of the repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.2.3-7: Additional NR repeater spurious emissions basic limits for Band n30** + +| Frequency range | basic limits | Measurement Bandwidth | Note | +|-------------------|--------------|-----------------------|------| +| 2200 – 2345 MHz | -45 dBm | 1 MHz | | +| 2362.5 – 2365 MHz | -25 dBm | 1 MHz | | +| 2365 – 2367.5 MHz | -40 dBm | 1 MHz | | +| 2367.5 – 2370 MHz | -42 dBm | 1 MHz | | +| 2370 – 2395 MHz | -45 dBm | 1 MHz | | + +The following requirement may apply to repeater operating in Band n48 in certain regions. The power of any spurious emission shall not exceed: + +**Table 6.5.4.2.3-8: Additional repeater spurious emissions basic limits for Band n48** + +| Frequency range | Basic limits | Measurement Bandwidth (NOTE) | Note | +|--------------------------------------------|--------------|------------------------------|----------------------------------------------------------| +| 3530 MHz – 3720 MHz | -25 dBm | 1 MHz | Applicable 10 MHz from the assigned passband edge | +| 3100 MHz – 3530 MHz
3720 MHz – 4200 MHz | -40 dBm | 1 MHz | | + +NOTE: The resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +NOTE: The regional requirement, included in [12], is defined in terms of EIRP, which is dependent on both the repeater emissions at the *antenna connector* and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex F. + +The following requirement shall be applied to repeater operating in Band n26 to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the repeater downlink operating band up to 10 MHz above the highest frequency of the repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.2.3-9: Repeater spurious emissions basic limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Basic limit | Measurement Bandwidth | Note | +|----------------|-----------------|--------------------|-----------------------|----------------------------------------------------------------| +| n26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the passband edge | + +The following requirement may apply to Repeater for Band n41 and n90 operation in Japan. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the Repeater downlink operating band up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the Repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.2.3-10: Additional repeater spurious emissions basic limit for Band n41 and n90** + +| Frequency range | Basic limit | Measurement Bandwidth | +|-----------------------------------------------------------------------------|--------------------|-----------------------| +| 2505 MHz – 2535 MHz | -42 dBm | 1 MHz | +| NOTE: This requirement applies for carriers allocated within 2545-2645 MHz. | | | + +The following requirement may apply to repeater operating in 3.45-3.55 GHz in Band n77 in certain regions. Basic limits are specified in table 6.5.4.2.3-11. + +**Table 6.5.4.2.3-11: Additional repeater spurious emissions basic limits for Band n77** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Filter centre frequency, $F_{\text{filter}}$ [MHz] | Basic limit [dBm] | Measurement bandwidth [MHz] | +|-------------------------|-----------------------|----------------------------------------------------|-------------------|-----------------------------| +| All | 3430 – 3440 | $3430.5 \leq F_{\text{filter}} < 3439.5$ | -25 | 1 | +| | 3560 – 3570 | $3560.5 \leq F_{\text{filter}} < 3569.5$ | | | +| All | $\leq 3430$ | $F_{\text{filter}} < 3429.5$ | -40 | 1 | +| | $> 3570$ | $3570.5 \leq F_{\text{filter}}$ | | | + +NOTE: The resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +The following requirement may also apply to repeater operating in Band n54 in certain regions. The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.5.4.2.3-12 shall not exceed the maximum emission levels $P_{\text{EM,n54,a}}$ , $P_{\text{EM,n54,b}}$ , $P_{\text{EM,n54,c}}$ , $P_{\text{EM,n54,d}}$ , $P_{\text{EM,n54,e}}$ and $P_{\text{EM,n54,f}}$ declared by the manufacturer. + +**Table 6.5.4.2.3-12: Declared Band n54 emissions basic limits for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW) (Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| n54 | 1541 - 1559 MHz | $P_{\text{EM,n54,a}}$ | | $P_{\text{EM,n54,f}}$ | +| | 1559 - 1610 MHz | $P_{\text{EM,n54,b}}$ | $P_{\text{EM,n54,d}}$ | | +| | 1610 - 1650 MHz | $P_{\text{EM,n54,c}}$ | $P_{\text{EM,n54,e}}$ | | + +Note: The regional requirements specified in attachment to the FCC reference document, 0007135419 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: $P_{\text{EIRP}} = P_{\text{E}} + G_{\text{ant}}$ where $P_{\text{E}}$ denotes the repeater unwanted emission level at the antenna connector, $G_{\text{ant}}$ equals the repeater antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. + +### 6.5.4.2.3 Co-location with base stations and repeater Nodes + +These requirements may be applied for the protection of other BS, IAB-DU, IAB-MT and repeater receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA, NR BS, IAB-DU, IAB-MT, or repeater are co-located. + +The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with same class. + +The *basic limits* are in table 6.5.4.2.3-1. Requirements for co-location with a system listed in the first column apply, depending on the declared class. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.5.4.2.3-1 shall apply for each supported *operating band*. + +**Table 6.5.4.2.3-1: Spurious emissions minimum requirements for co-location with BS, IAB-Node or repeater-Node** + +| Type of co-located BS | Frequency range for co-location requirement | Basic limits | | | Measurement bandwidth | Note | +|---------------------------------------------------|---------------------------------------------|--------------|-------------|-------------|-----------------------|------| +| | | WA repeater | MR repeater | LA repeater | | | +| GSM900 | 876 – 915 MHz | -98 dBm | -91 dBm | -70 dBm | 100 kHz | | +| DCS1800 | 1710 – 1785 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | +| PCS1900 | 1850 – 1910 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 – 849 MHz | -98 dBm | -91 dBm | -70 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 1920 – 1980 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1850 – 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1710 – 1785 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 824 – 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 – 845 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2500 – 2570 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 880 – 915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 – 1784.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | + +| | | | | | | | +|-----------------------------------------------------|---------------------|---------|---------|---------|---------|-------------------------------------------------------------------------------------| +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 – 1447.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n50, n75, n91, n92, n93 or n94 | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 699 – 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 777 – 787 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 788 – 798 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 – 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 – 830 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n50, n75, n92 or n94 | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 24 or NR Band n24 | 1626.5 – 1660.5 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR Band n25 | 1850 – 1915 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 814 – 849 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | + +| | | | | | | | +|---------------------------------------------------|-------------------|------------|------------|------------|---------|---------------------------------------------------------------------| +| E-UTRA Band 27 | 807 – 824 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| E-UTRA Band 28 or NR Band n28 | 703 – 748 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| E-UTRA Band 30 or NR Band n30 | 2305 – 2315 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| E-UTRA Band 31 or NR Band n31 | 452.5 – 457.5 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 – 2025 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | This is not applicable to repeater operating in Band n34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | This is not applicable to repeater operating in Band n2 or band n25 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | This is not applicable to repeater operating in Band n38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | This is not applicable to repeater operating in Band n39 | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | This is not applicable to repeater operating in Band n30 or n40. | + +| | | | | | | | +|------------------------------------|-----------------|---------|---------|---------|---------|------------------------------------------------------------------------------------------| +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n41, n53 or [n90] | +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 44 | 703 – 803 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n28 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n51, n74, n75, n91, n92, n93 or n94 | + +| | | | | | | | +|-------------------------------|-------------------|---------|---------|---------|---------|-----------------------------------------------------------------------------------------------| +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n50, n74, n75, n76, n91, n92, n93 or n94 | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n41, n53 or n90 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n54 | +| E-UTRA Band 65 or NR Band n65 | 1920 – 2010 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 66 or NR Band n66 | 1710 – 1780 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 68 | 698 – 728 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 70 or NR Band n70 | 1695 – 1710 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 71 or NR Band n71 | 663 – 698 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 72 or NR Band n72 | 451 – 456 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 74 or NR Band n74 | 1427 – 1470 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n50, n51, n91, n92, n93 or n94 | +| NR Band n77 | 3.3 – 4.2 GHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | + +| | | | | | | | +|-------------------------------|---------------------|------------|------------|------------|---------|----------------------------------------------------------------------| +| NR Band n78 | 3.3 – 3.8 GHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n80 | 1710 – 1785 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n81 | 880 – 915 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n82 | 832 – 862 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n83 | 703 – 748 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n84 | 1920 – 1980 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| E-UTRA Band 85 or NR Band n85 | 698 – 716 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n86 | 1710 – 1780 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n89 | 824 – 849 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n91 | 832 – 862 MHz | N/A | N/A | -88
dBm | 100 kHz | | +| NR Band n92 | 832 – 862 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n93 | 880 – 915 MHz | N/A | N/A | -88
dBm | 100 kHz | | +| NR Band n94 | 880 – 915 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n95 | 2010 – 2025 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n96 | 5925 – 7125 MHz | N/A | -90
dBm | -87
dBm | 100 kHz | | +| NR Band n97 | 2300 – 2400MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n98 | 1880 – 1920MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n101 | 1900 – 1910 MHz | -96
dBm | NA | NA | 100 kHz | | + +| | | | | | | | +|-----------------|-----------------|------------|------------|------------|---------|---------------------------------------------------------------------| +| NR Band n102 | 5925 – 6425 MHz | N/A | -90
dBm | -87
dBm | 100 kHz | | +| E-UTRA Band 103 | 787 – 788 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n104 | 6425 – 7125 MHz | -95
dBm | -90
dBm | -87
dBm | 100 kHz | This requirement does not apply to repeater operating in Band n104. | +| NR Band n105 | 663 – 703 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| E-UTRA Band 106 | 896 – 901 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | +| NR Band n109 | 703 – 733 MHz | -96
dBm | -91
dBm | -88
dBm | 100 kHz | | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.5.4.2.4-1 do not apply for the frequency range extending $\Delta f_{\text{OBUE}}$ immediately outside the transmit frequency range. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30dB antenna to antenna minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [3]. + +NOTE 2: Table 6.5.4.2.3-1 assumes that two *operating bands*, where the corresponding transmit and receive frequency ranges in table 5.2-1 would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-location requirements may apply that are not covered by the 3GPP specifications. + +### 6.5.4.3 Minimum requirement for *RF repeater* + +The Tx spurious emissions for *repeater type 1-C* for each *antenna connector* shall not exceed the *basic limits* specified in clause 6.5.4.2. + +For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all *antenna connectors* for *repeater type 1-C* shall not exceed the *basic limits* defined in clause 6.6.4.2. + +### 6.5.4.4 Minimum requirement for *NCR* + +#### 6.5.4.4.1 Minimum requirement for NCR-Fwd + +##### 6.5.4.4.1.1 Minimum requirement for NCR-Fwd type 1-C + +The Tx spurious emissions for *NCR-Fwd type 1-C* for each *antenna connector* shall not exceed the *basic limits* specified in clause 6.5.4.2. + +For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all *antenna connectors* for *NCR-Fwd type 1-C* shall not exceed the *basic limits* defined in clause 6.6.5.2. + +For joint transmission of NCR-Fwd and NCR-MT in the uplink, the spurious emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +#### 6.5.4.4.1.2 Minimum requirement for NCR-Fwd type 1-H + +The Tx spurious emissions requirements for *NCR-Fwd type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.5.4.2, the power summation emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed a limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{TXU, counted per cell}})$ for DL and for WA UL and $X=0$ for LA UL, unless stated differently in regional regulation. + +NOTE: Conformance to the *NCR-Fwd type 1-H* spurious emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the limit as defined in this clause for the respective frequency span. + +Or + +2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the *NCR-Fwd type 1-H* limit as defined in this clause for the respective frequency span, scaled by $-10\log_{10}(n)$ , where n is the number of *TAB connectors* in the *TAB connector TX min cell group*. + +For joint transmission of NCR-Fwd and NCR-MT in the uplink, the spurious emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +#### 6.5.4.4.2 Minimum requirement for NCR-MT + +##### 6.5.4.4.2.1 Minimum requirements for NCR-MT type 1-C + +When NCR-MT and NCR-Fwd are not transmitting simultaneously, the requirements in clause 6.6.4 of TS 38.104 applies for WA NCR-MT type 1-C and the requirements in clause 6.5.3 in TS 38.101-1 applies for LA NCR-MT type 1-C. + +When NCR-MT and NCR-Fwd are transmitting simultaneously, the requirements in clause 6.5.3 in TS 38.101-1 applies for LA NCR-MT type 1-C for sum of NCR-MT transmission and NCR-Fwd transmission. + +##### 6.5.4.4.2.2 Minimum requirements for NCR-MT type 1-H + +Limits for NCR-MT type 1-H apply to the sum of emissions across all TAB connectors. + +When WA NCR-MT and NCR-Fwd are not transmitting simultaneously, the requirements in clause 6.6.4 of TS 38.104 relaxed with the following scaling factor applies for WA NCR-MT type 1-H. + +$$10\log(N_{\text{TXU, counted}}), \text{ where } N_{\text{TXU, counted}} = \min(N_{\text{TXU, active}}, 8)$$ + +When WA NCR-MT and NCR-Fwd are transmitting simultaneously, the requirements in clause 6.6.4 of TS 38.104 relaxed with the following scaling factor applies for the sum of NCR-MT transmission and NCR-Fwd transmission. + +When LA NCR-MT and NCR-Fwd are not transmitting simultaneously, the requirements in clause 6.5.3 in TS 38.101-1 applies for LA NCR-MT type 1-H without scaling factor allowed for the sum of the spurious emissions. + +When NCR-MT and NCR-Fwd are transmitting simultaneously, the requirements in clause 6.5.3 in TS 38.101-1 applies for sum of NCR-MT transmission and NCR-Fwd transmission. + +## 6.5.5 Receiver spurious emissions + +### 6.5.5.1 General + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *antenna connector*. The requirements only apply to *repeater type 1-C* for TDD operation. + +For each *antenna connectors* on BS-side and UE-side supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF state*. For *antenna connectors* both BS-side and UE-side in FDD, the RX spurious emissions requirements are superseded by the TX spurious emissions requirements, as specified in clause 6.5.4. + +For *multi-band connectors* that both transmit and receive in *operating band* supporting TDD, RX spurious emissions requirements are applicable during the *TX OFF state*, and are subject to exclusion zones in each supported *operating band*. + +For Band n41 and n90 operation in Japan, the sum of receiver spurious emissions requirements over all *antenna connectors* for *repeater type 1-C* shall not exceed *minimum requirements* defined in clause 6.5.5.2. + +### 6.5.5.2 Basic limits + +The receiver spurious emissions requirements, *basic limits* are provided in table 6.5.5.2-1. + +**Table 6.5.5.2-1: Repeater receiver spurious emissions basic limits** + +| Spurious frequency range | Basic limits | Measurement bandwidth | Note | +|--------------------------------------------------------------------------------------------------|--------------|-----------------------|--------------------------------| +| 30 MHz – 1 GHz | -57 dBm | 100 kHz | Note 1 | +| 1 GHz – 12.75 GHz | -47 dBm | 1 MHz | Note 1, Note 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 3, Note 5 | +| 12.75 GHz - 26 GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 6 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [5], s4.1. + +NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. + +NOTE 3: This spurious frequency range applies only for operating bands for which the 5th harmonic of the upper frequency edge of the UL operating band is reaching beyond 12.75 GHz. + +NOTE 4: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the repeater transmitter operating band to $\Delta f_{\text{OBUE}}$ above the highest frequency of the repeater transmitter operating band may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause 6.5.1. For multi-band connectors, the exclusion applies for all supported operating bands. + +NOTE 5: Does not apply for band n104. + +NOTE 6: Applies only for band n104. + +### 6.5.5.3 Minimum requirement for RF repeater + +The RX spurious emissions requirements for *repeater type 1-C* are that for each antenna connector, the power of emissions shall not exceed basic limits specified in table 6.5.5.2-1. + +For Band n41 and n90 operation in Japan, the sum of RX spurious emissions requirements over all antenna connectors for *repeater type 1-C* shall not exceed basic limits specified in table 6.5.5.2-1. + +### 6.5.5.4 Minimum requirement for NCR + +#### 6.5.5.4.1 Minimum requirement for NCR-Fwd + +##### 6.5.5.4.1.1 Minimum requirement for NCR-Fwd type 1-C + +The RX spurious emissions requirements for *NCR-Fwd type 1-C* are that for each antenna connector, the power of emissions shall not exceed basic limits specified in table 6.5.5.2-1. + +For Band n41 and n90 operation in Japan, the sum of RX spurious emissions requirements over all antenna connectors for *NCR-Fwd type 1-C* shall not exceed basic limits specified in table 6.5.5.2-1. + +For joint reception of NCR-Fwd and NCR-MT in the uplink, the receiver spurious emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +#### 6.5.5.4.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +The RX spurious emissions requirements for *NCR-Fwd type 1-H* are that for each applicable *basic limit* specified in table 7.6.2-1 for each *TAB connector RX min cell group*, the power sum of emissions at respective *TAB connectors* shall not exceed the limits specified as the *basic limits* + X, where $X = 10\log_{10}(N_{RXU, countedpercell})$ for DL and for WA UL and $X=0$ for LA UL, unless stated differently in regional regulation. + +The RX spurious emission requirements are applied per the *TAB connector RX min cell group* for all the configurations supported by the repeater. + +NOTE: Conformance to the repeater receiver spurious emissions requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the spurious emissions power measured on each *TAB connector* in the *TAB connector RX min cell group* shall be less than or equal to the limit above for the respective frequency span. + +Or + +- 2) The spurious emissions power at each *TAB connector* shall be less than or equal to the limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where *n* is the number of *TAB connectors* in the *TAB connector RX min cell group*. + +For joint reception of NCR-Fwd and NCR-MT in the uplink, the receiver spurious emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +## 6.6 Repeater Error Vector Magnitude + +### 6.6.1 Downlink repeater error vector magnitude + +#### 6.6.1.1 General + +The Repeater Error Vector Magnitude (EVM) is a measure of the difference between the symbols provided at the input of repeater and the measured signal symbols at the output of the repeater after the equalization by the measurement equipment. This difference is called the error vector. Details about how the repeater EVM is determined are the same as specified in TS 38.104 [2] Annex B for FR1. The repeater EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed in percent. + +The repeater EVM requirement is applicable for a repeater operating at an input power in the range from what is required to reach the maximum output power to the minimum power level in table 6.6.1.1-1. + +**Table 6.6.1.1-1: Minimum input power for repeater EVM** + +| Repeater DL class | Minimum input power spectral density (dBm/MHz) | +|-------------------|------------------------------------------------| +|-------------------|------------------------------------------------| + +| | QPSK, 16 QAM, 64QAM | 256QAM1 | +|-------------------------------------------------------|----------------------------|---------------------------| +| WA | -82 | -75 | +| MR | -77 | -70 | +| LA | -74 | -67 | +| Note 1: support of 256QAM is based on the declaration | | | + +### 6.6.1.2 Minimum requirement for *RF repeater* + +The repeater EVM levels for different modulation schemes outlined in table 6.6.1.2-1 shall be met using the frame structure described in clause 6.6.1.3. + +**Table 6.6.1.2-1: Repeater EVM requirements** + +| Parameter | Required repeater EVM | +|--------------------------------------------------------|------------------------------| +| QPSK, 16QAM, 64QAM | 8 % | +| 256QAM | 3.5 % 1 | +| Note 1: support of 256QAM is based on the declaration. | | + +### 6.6.1.2A Minimum requirement for *NCR* + +#### 6.6.1.2A.1 Minimum requirement for NCR-Fwd + +##### 6.6.1.2A.1.1 Minimum requirement for NCR-Fwd type 1-C + +The NCR-Fwd EVM levels for different modulation schemes outlined in table 6.6.1.2-1 shall be met using the frame structure described in clause 6.6.1.3. + +##### 6.6.1.2A.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +The NCR-Fwd EVM levels for different modulation schemes outlined in table 6.6.1.2-1 shall be met using the frame structure described in clause 6.6.1.3 between corresponding input/output TAB connectors. + +### 6.6.1.3 Repeater EVM frame structure for measurement + +The input signals for the repeater EVM requirement shall have the same frame structure as defined for the BS in TS 38.104 [2]. + +## 6.6.2 Uplink repeater error vector magnitude + +### 6.6.2.1 General + +The Repeater Error Vector Magnitude is a measure of the difference between the reference waveform provided at the input of repeater and the measured waveform at the output of the repeater. This difference is called the error vector. Details about how the repeater EVM is determined are the same as specified in TS 38.101-1 [13] Annex F for FR1. Before calculating the repeater EVM the measured waveform is corrected by the sample timing offset and RF frequency offset. Then the carrier leakage shall be removed from the measured waveform before calculating the repeater EVM. + +The measured waveform is further equalised using the channel estimates subjected to the repeater EVM equaliser spectrum flatness requirement specified in TS 38.101-1 [13] clause 6.4.2.4. For DFT-s-OFDM waveforms, the repeater EVM result is defined after the front-end FFT and IDFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. For CP-OFDM waveforms, the repeater EVM result is defined after the front-end FFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. + +The basic repeater EVM measurement interval in one slot in the time domain. The repeater EVM measurement interval is reduced by any symbols that contains an allowable power transient in the measurement interval, as defined in TS 38.101-1 [13] clause 6.3.3 for EVM for UE. + +The repeater EVM requirement is applicable for a repeater operating at an input power in the range from what is required to reach the maximum output power to the minimum power level in table 6.6.2.1-1. + +**Table 6.6.2.1-1: Minimum input power for repeater EVM** + +| Repeater UL class | Minimum input power spectral density (dBm/MHz) | | +|-------------------------------------------------------|------------------------------------------------|---------------------| +| | QPSK, 16 QAM, 64QAM | 256QAM 1 | +| WA | -82 | -75 | +| LA | -74 | -67 | +| Note 1: support of 256QAM is based on the declaration | | | + +## 6.6.2.2 Minimum requirement for *RF repeater* + +The RMS average of the basic repeater EVM measurements over 10 subframes for the average repeater EVM case for the different modulation schemes shall not exceed the values specified in Table 6.6.2.2-1. + +**Table 6.6.2.2-1: Requirements for Repeater Error Vector Magnitude** + +| Parameter | Unit | Average Repeater EVM Level | +|--------------------------------------------------------|------|----------------------------| +| QPSK, 16 QAM, 64QAM | % | 8 | +| 256 QAM | % | 3.5 1 | +| Note 1: support of 256QAM is based on the declaration. | | | + +## 6.6.2.3 Minimum requirement for *NCR* + +### 6.6.2.3.1 Minimum requirement for NCR-Fwd + +#### 6.6.2.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +The RMS average of the basic NCR-Fwd EVM measurements over 10 subframes for the average NCR-Fwd EVM case for the different modulation schemes shall not exceed the values specified in Table 6.6.2.2-1. + +#### 6.6.2.3.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +The RMS average of the basic NCR-Fwd EVM measurements over 10 subframes for the average NCR-Fwd EVM case for the different modulation schemes shall not exceed the values specified in Table 6.6.2.2-1 between corresponding input/output TAB connectors. + +## 6.7 Input intermodulation + +### 6.7.1 General requirement + +#### 6.7.1.1 General + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the *passband*, in the presence of interfering signals on frequencies other than the *passband*. + +The following requirement applies for interfering signals depending on the repeaters *passband*. + +This requirement applies to the uplink and downlink of the repeater during the *transmitter ON state*. + +There is no co-location input intermodulation requirement for LA 1-C repeaters deployed in Femto cell scenario. + +#### 6.7.1.2 Minimum requirement for *RF repeater* + +For the parameters specified in table 6.7.1.2-1, the power in the *passband* shall not increase with more than 10 dB at the output of the repeater as measured with 1 MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +Table 6.7.1.2-1 specifies the parameters for two interfering signals, where: + +- $f_i$ offset is the offset from the channel edge frequency of the first or last channel in the *passband* of the closer carrier. + +**Table 6.7.1.2-1: Input intermodulation requirement** + +| $f_i$ offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|--------------|---------------------------|-----------------|-----------------------| +| 1 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +### 6.7.1.3 Minimum requirement for *NCR* + +#### 6.7.1.3.1 Minimum requirement for NCR-Fwd + +##### 6.7.1.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +For the parameters specified in table 6.7.1.1-1, the power in the *passband* shall not increase with more than 10 dB at the output of the NCR-Fwd as measured with 1 MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +Table 6.7.1.2-1 specifies the parameters for two interfering signals. + +##### 6.7.1.3.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +For the parameters specified in table 6.7.1.1-1, considering corresponding input/output TAB connectors, the power in the *passband* shall not increase with more than 10 dB at the output of the NCR-Fwd as measured with 1 MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +Table 6.7.1.2-1 specifies the parameters for two interfering signals. + +## 6.7.2 Co-location with BS/repeater in other systems + +### 6.7.2.1 General + +This additional input intermodulation requirement may be applied for the protection of NR repeater receivers when GSM, CDMA, UTRA, E-UTRA, NR BS or repeater operating in a different frequency band are co-located with a NR repeater. + +The following requirement applies for interfering signals depending on the repeaters *passband*. + +This requirement applies to the uplink and downlink of the repeater. If the BS side is declared to meet co-location requirements, then it should meet input intermodulation co-location requirements for the downlink. If the UE side is declared to meet co-location requirements, then it should meet input intermodulation co-location requirements for the uplink. + +### 6.7.2.2 Minimum requirement for *RF repeater* + +For the parameters specified in table 6.7.2.2-1 for DL and 6.7.2.2-2 for UL, the power in the *passband* shall not increase with more than 10 dB at the output of the repeater as measured with 1MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +**Table 6.7.2.2-1: input intermodulation requirement for NR repeater DL when co-located with BS/repeater in other frequency bands.** + +| Frequency range of interfering signal | Interfering signal mean power for repeater with WA UE side (dBm) | Interfering signal mean power for repeater with MR UE side(dBm) | Interfering signal mean power for repeater with LA UE side(dBm) | Type of interfering signals | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------| +| Frequency range of co-located BS's downlink operating band or located repeater's passband | +16 | +8 | x (Note 1) | 2 CW carriers | +| NOTE 1: x = -7 dBm for NR repeater co-located with Pico GSM850 or Pico CDMA850
x = -4 dBm for NR repeater co-located with Pico DCS1800 or Pico PCS1900
x = -6 dBm for NR repeater co-located with UTRA bands or E-UTRA bands or NR bands
NOTE 2: The requirement does not apply when the interfering signal falls within the passband .
NOTE 3: For unsynchronized base stations (except in band n46, n96, and n102) or repeaters, special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | | + +**Table 6.7.2.2-2: input intermodulation requirement for NR repeater UL when co-located with BS/repeater in other frequency bands.** + +| Frequency range of interfering signal | Interfering signal mean power for repeater with WA BS side(dBm) | Interfering signal mean power for repeater with LA BS side(dBm) | Type of interfering signals | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------| +| Frequency range of co-located BS's downlink operating band or located repeater's passband | +16 | $P_{\text{rated,p,AC}} - 30$ | 2 CW carriers | +| NOTE 1: The requirement does not apply when the interfering signal falls within the passband .
NOTE 2: For unsynchronized base stations (except in band n46, n96, and n102) or repeaters, special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | + +## 6.7.2.3 Minimum requirement for *NCR* + +### 6.7.2.3.1 Minimum requirement for NCR-Fwd + +#### 6.7.2.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +For the parameters specified in table 6.7.2.2-1 for DL and 6.7.2.2-2 for UL, the power in the *passband* shall not increase with more than 10 dB at the output of the NCR-Fwd as measured with 1MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +#### 6.7.2.3.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +For the parameters specified in table 6.7.2.2-1 for DL and 6.7.2.2-2 for UL, considering corresponding input/output TAB connectors, the power in the *passband* shall not increase with more than 10 dB at the output of the NCR-Fwd as measured with 1MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +### 6.7.3 Co-existence with other systems + +#### 6.7.3.1 General + +This input intermodulation existence requirement may be applied for the protection of NR repeater receivers when GSM, CDMA, UTRA, E-UTRA, NR BS or repeater operating in another frequency band co-exist with a NR repeater. + +#### 6.7.3.2 Minimum requirement for *RF repeater* + +For the parameters specified in table 6.7.3.2-1, the power in the *passband* shall not increase with more than 10 dB at the output of the repeater as measured with 1MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +**Table 6.7.3.2-1: input intermodulation requirement for NR repeater when co-exist with BS/repeater in other non-overlapping frequency bands** + +| Frequency range of interfering signal | Interfering signal mean power (dBm) | Type of interfering signals | Measurement bandwidth | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------|-----------------------| +| Frequency range of co-existence system operating band | -15 | 2 CW carriers | 1MHz | +| NOTE 1: All the interfering signals should be limited into the frequency ranges that are either X MHz higher than $F_{UL,high}$ or X MHz lower than $F_{UL,low}$ , where X equals to 20MHz when $F_{UL,high} - F_{UL,low}$ is not larger than 200MHz, otherwise X equals to 60MHz | | | | + +#### 6.7.3.3 Minimum requirement for *NCR* + +##### 6.7.3.3.1 Minimum requirement for NCR-Fwd + +###### 6.7.3.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +For the parameters specified in table 6.7.3.2-1, the power in the *passband* shall not increase with more than 10 dB at the output of the NCR-Fwd as measured with 1MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +#### 6.7.3.3.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +For the parameters specified in table 6.7.3.2-1, considering corresponding input/output TAB connectors, the power in the *passband* shall not increase with more than 10 dB at the output of the NCR-Fwd as measured with 1MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the *passband*. + +## 6.8 Output intermodulation + +### 6.8.1 General + +The output intermodulation requirement is a measure of the capability of the repeater to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the repeater via the output port. The requirement shall apply during the *transmitter ON state* and the *transmitter transient period*. + +The requirement shall apply to the uplink and downlink of the Repeater. + +The output intermodulation level is the power of the intermodulation products when an interfering signal is injected into the *antenna connector*. + +### 6.8.2 Minimum requirements for *RF repeater* + +#### 6.8.2.1 Minimum requirements + +The output intermodulation level is the power of the intermodulation products when an interfering signal is injected into the output port. The wanted signal *passband* shall be the maximum bandwidth supported by the repeater. + +For *repeater type 1-C*, the wanted signal and interfering signal centre frequency is specified in table 6.8.2.1-1, where interfering signal level is *rated total output power* ( $P_{\text{rated,t,AC}}$ ) at *antenna connector* in the *passband* – 30 dB. + +The unwanted emission with output intermodulation applied shall not exceed the corresponding uplink and downlink unwanted emission limits in clause 6.5 in the presence of an interfering signal according to table 6.8.2.1-1. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products. + +**Table 6.8.2.1-1: Interfering and wanted signals for the output intermodulation requirement** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | NR signal, filling all supported passbands in the operating band and with sufficient carriers to fill each passband . Minimum defined SCS for the operating band | +| Interfering signal type | NR signal, with the minimum SCS and channel bandwidth defined in the operating band in [2] | +| Interfering signal level | Rated total output power ( $P_{\text{rated,t,AC}}$ ) in the passband – 30 dB | +| Interfering signal centre frequency offset from the lower/upper edge of the wanted signal or edge of sub-block inside a sub-block gap | , for n=1, 2 and 3 | +| NOTE 1: Interfering signal positions that are partially or completely outside of any downlink operating band of the repeater are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band, TS 38.115-1 [7] provides further guidance regarding appropriate test requirements. | | +| NOTE 2: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | + +## 6.8.2.2 Additional requirements + +For repeater supporting Band n41 and n90 operation in Japan, the sum of output intermodulation level over all *antenna connectors* shall not exceed the unwanted emission limits in clauses 6.5 in the presence of an NR interfering signal according to table 6.8.2.2-1. + +**Table 6.8.2.2-1 Interfering and wanted signals for the additional output intermodulation requirement for Band n41 and n90** + +| Parameter | Value | +|-----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| Wanted signal | NR single (NOTE) | +| Interfering signal type | NR signal of 10 MHz passband bandwidth | +| Interfering signal level | Rated total output power ( $P_{\text{rated,t,AC}}$ ) in the passband – 30 dB | +| Interfering signal centre frequency offset from the lower/upper passband centre frequency of the wanted signal | $\pm 5$ MHz
$\pm 15$ MHz
$\pm 25$ MHz | +| NOTE: This requirement applies for passband allocated within 2545-2645 MHz. | | + +## 6.8.3 Minimum requirements for *NCR* + +### 6.8.3.1 Minimum requirements for NCR-Fwd + +#### 6.8.3.1.1 Minimum requirements for NCR-Fwd type 1-C + +The output intermodulation level is the power of the intermodulation products when an interfering signal is injected into the output port. The wanted signal *passband* shall be the maximum bandwidth supported by the NCR-Fwd. + +For *NCR-Fwd type 1-C*, the wanted signal and interfering signal centre frequency is specified in table 6.8.2.1-1, where interfering signal level is *rated total output power* ( $P_{\text{rated,t,AC}}$ ) at *antenna connector* in the *passband* – 30 dB. + +The unwanted emission with output intermodulation applied shall not exceed the corresponding uplink and downlink unwanted emission limits in clause 6.5 in the presence of an interfering signal according to table 6.8.2.1-1. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products. + +#### 6.8.3.1.2 Additional requirements for NCR-Fwd type 1-C + +For NCR supporting Band n41 and n90 operation in Japan, the sum of output intermodulation level over all *antenna connectors* shall not exceed the unwanted emission limits in clauses 6.5 in the presence of an NR interfering signal according to table 6.8.2.2-1. + +#### 6.8.3.1.3 Minimum requirements for *NCR-Fwd type 1-H* + +The output intermodulation level is the power of the intermodulation products when an interfering signal is injected into the output port. The wanted signal *passband* shall be the maximum bandwidth supported by the NCR-Fwd. + +For *NCR-Fwd type 1-H*, the wanted signal and interfering signal centre frequency is specified in table 6.8.2.1-1, where interfering signal level is *rated total output power* ( $P_{\text{rated,t,TABC}}$ ) at *TAB connector* in the *passband* – 30 dB. + +The unwanted emission with output intermodulation applied shall not exceed the corresponding uplink and downlink unwanted emission limits in clause 6.5 in the presence of an interfering signal according to table 6.8.2.1-1. The measurement may be limited to frequencies on which third and fifth order intermodulation products appear, considering the width of these products. + +#### 6.8.3.1.4 Additional requirements for NCR-Fwd type 1-H + +For NCR supporting Band n41 and n90 operation in Japan, the sum of output intermodulation level over all *TAB connectors* shall not exceed the unwanted emission limits in clauses 6.5 in the presence of an NR interfering signal according to table 6.8.2.2-1. + +## 6.9 Adjacent Channel Rejection Ratio (ACRR) + +### 6.9.1 General + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the average gain over a carrier of the repeater in the *passband* to the average gain of the repeater over an adjacent channel outside the repeater *passband*. The carrier in the *passband* + +and in the adjacent channel shall be of the same type (reference carrier) with bandwidths as defined by *nominal channel bandwidth*. + +The requirement shall apply to the uplink and downlink of the Repeater, where the donor link is maintained via antennas (wireless Repeater). + +The requirement is differentiated between uplink and downlink. + +The requirement shall apply during the *transmitter ON state*. + +## 6.9.2 Minimum Requirements for *RF repeater* + +For a repeater operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2-1 shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 6.9.2-1. + +**Table 6.9.2-1: Repeater Downlink ACRR below 2496MHz** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit | +|---------------------------------|-----------------------|-------------------------------------------------------------|----------------| +| UTRA, E-UTRA, NR | Wide Area repeater | $BW_{Nominal}/2$ | 45 | +| | Medium Range repeater | $BW_{Nominal}/2$ | 45 | +| | Local Area repeater | $BW_{Nominal}/2$ | 33
(Note 1) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. + +For a repeater operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2-1a shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 6.9.2-1a. + +**Table 6.9.2-1a: Repeater Downlink ACRR above 2496 MHz** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit | +|---------------------------------|-----------------------|-------------------------------------------------------------|------------------| +| UTRA, E-UTRA, NR | Wide Area repeater | $BW_{Nominal}/2$ | 33dB | +| | Medium Range repeater | $BW_{Nominal}/2$ | 33dB | +| | Local Area repeater | $BW_{Nominal}/2$ | 33dB
(Note 1) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. + +For a repeater operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2-2 shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 6.9.2-2. + +**Table 6.9.2-2: Repeater Uplink ACRR below 2496 MHz** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit | +|-----------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------------------------------------|------------------| +| UTRA, E-UTRA, NR | Wide Area repeater | $BW_{Nominal}/2$ | 33dB | +| | Local Area repeater | $BW_{Nominal}/2$ | 33dB
(Note 1) | +| NOTE 1: This requirement does not applicable if the passband occupies the entire operating band . | | | | + +For a repeater operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2-2a shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 6.9.2-2a. + +**Table 6.9.2-2a: Repeater Uplink ACRR above 2496 MHz** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit | | +|---------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------------------------------------|---------------------------|--| +| UTRA, E-UTRA, NR | Wide Area repeater | $BW_{Nominal}/2$ | 33dB | | +| | Local Area repeater | 5MHz | 20dBc (Note 1,
Note 2) | | +| | | $BW_{Nominal}/2$ | 33dBc (Note 1) | | +| NOTE 1: This requirement does not applicable if the passband occupies the entire operating band . | | | | | +| NOTE 2: In this case, the channel within the passband and the adjacent channel are assumed to have a bandwidth of 10 MHz | | | | | + +## 6.9.3 Minimum Requirements for *NCR* + +### 6.9.3.1 Minimum requirements for NCR-Fwd + +#### 6.9.3.1.1 Minimum requirements for NCR-Fwd type 1-C + +For a NCR-Fwd operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.3-1 shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 6.9.2-1. + +For a NCR-Fwd operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2-1a shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 6.9.2-1a. + +For a NCR-Fwd operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2-2 shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 6.9.2-2. + +For a NCR-Fwd operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2-2a shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 6.9.2-2a. + +#### 6.9.3.1.2 Minimum Requirements for *NCR-Fwd type 1-H* + +For a NCR-Fwd operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2-1 shall apply in downlink. In normal conditions the ACRR for downlink between corresponding input/output TAB connectors shall be higher than the value specified in the Table 6.9.2-1. + +For a NCR-Fwd operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2-1a shall apply in downlink. In normal conditions the ACRR for downlink between corresponding input/output TAB connectors shall be higher than the value specified in the Table 6.9.2-1a. + +For a NCR-Fwd operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2-2 shall apply in uplink. In normal conditions the ACRR for uplink between corresponding input/output TAB connectors shall be higher than the value specified in the Table 6.9.2-2. + +For a NCR-Fwd operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2-2a shall apply in uplink. In normal conditions the ACRR for uplink between corresponding input/output TAB connectors shall be higher than the value specified in the Table 6.9.2-2a. + +## 6.10 Transmit ON/OFF power + +### 6.10.1 Transmitter OFF power + +#### 6.10.1.1 General + +Transmit OFF power requirements apply only to TDD operation of the repeater. The requirement applies to both downlink and uplink of the repeater. + +Transmitter OFF power is defined as the mean power measured over $70/N$ us filtered with a square filter of bandwidth equal to the *passband bandwidth* of the repeater ( $BW_{\text{passband}}$ ) centred on the assigned channel frequency during the *transmitter OFF state*. $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz of the input signal. + +For *multi-band connectors* and for *single band connectors* supporting transmission in multiple *operating bands*, the requirement is only applicable during the *transmitter OFF state* in all supported *operating bands*. + +#### 6.10.1.2 Minimum requirement for *RF repeater* + +For *repeater type 1-C downlink*, the requirements for transmitter OFF power spectral density shall be less than -85 dBm/MHz per *antenna connector*. + +For *repeater type 1-C uplink*, the requirements for transmitter OFF power spectral density shall be less than -50dBm / $(\text{SCS} * (12 * N_{\text{RB}} + 1) / 1000)$ MHz per *antenna connector*, where SCS is Sub Carrier Spacing in kHz. + +#### 6.10.1.3 Minimum requirement for *NCR* + +##### 6.10.1.3.1 Minimum requirement for NCR Fwd + +###### 6.10.1.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +For *NCR-Fwd type 1-C downlink*, the requirements for transmitter OFF power spectral density shall be less than -85 dBm/MHz per *antenna connector*. + +For *NCR-Fwd type 1-C uplink*, the requirements for transmitter OFF power spectral density shall be less than -50dBm / $(\text{SCS} * (12 * N_{\text{RB}} + 1) / 1000)$ MHz per *antenna connector*, where SCS is Sub Carrier Spacing in kHz. + +6.10.1.3.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +For *NCR-Fwd type 1-H downlink*, the requirements for transmitter OFF power spectral density shall be less than -85 dBm/MHz per *TAB connector*. + +For *NCR-Fwd type 1-H uplink*, the requirements for transmitter OFF power spectral density shall be less than -50dBm / (SCS\*(12\*NRB+1)/1000) MHz per *TAB connector*, where SCS is Sub Carrier Spacing in kHz. + +6.10.2 Transmitter transient period + +6.10.2.1 General + +*Transmitter transient period* requirements apply only to TDD operation of the repeater. The requirement applies to both downlink and uplink of the repeater. + +The *transmitter transient period* is the time period during which the transmitter is changing from the *transmitter OFF state* to the *transmitter ON state* or vice versa. The *transmitter transient period* is illustrated in figure 6.10.2.1-1. + +![A graph showing Transmitter Output Power over Time. The y-axis has 'ON power level' and 'OFF power level' marked. The curve shows a transition from OFF to ON, labeled 'Transmit transient period', followed by a period of 'Transmitter ON state (DL/UL transmission)', and then a transition back to OFF, also labeled 'Transmit transient period'. The initial and final states are labeled 'Transmit OFF state'. The ON state is associated with 'UL/DL transmission' and the OFF state with 'GP or UL/DL transmission'.](4a6781ac37759896da5d1eb6a04dae34_img.jpg) + +A graph showing Transmitter Output Power over Time. The y-axis has 'ON power level' and 'OFF power level' marked. The curve shows a transition from OFF to ON, labeled 'Transmit transient period', followed by a period of 'Transmitter ON state (DL/UL transmission)', and then a transition back to OFF, also labeled 'Transmit transient period'. The initial and final states are labeled 'Transmit OFF state'. The ON state is associated with 'UL/DL transmission' and the OFF state with 'GP or UL/DL transmission'. + +**Figure 6.10.2.1-1: Example of relations between transmitter ON state, transmitter OFF state and transmitter transient period** + +For *repeater type 1-C* this requirement shall be applied at the *antenna connector* supporting transmission in the *operating band*. The beginning and end point of downlink and uplink bursts are referenced to the slot timing at the input. + +6.10.2.2 Minimum requirement for *RF repeater* + +For *repeater type 1-C*, the *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 6.10.2.2-1. + +**Table 6.10.2.2-1: Minimum requirement for the transmitter transient period for repeater type 1-C** + +| Transition | Transient period length (μs) | +|------------|------------------------------| +| OFF to ON | 10 | +| ON to OFF | 10 | + +### 6.10.2.3 Minimum requirement for *NCR* + +#### 6.10.2.3.1 Minimum requirement for NCR-Fwd + +##### 6.10.2.3.1.1 Minimum requirement for NCR-Fwd type 1-C + +For *NCR-Fwd type 1-C* this requirement shall be applied at the *antenna connector* supporting transmission in the *operating band*. The beginning and end point of downlink and uplink bursts are referenced to the slot timing at the input. + +For *NCR-Fwd type 1-C*, the *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 6.10.2.2-1. + +##### 6.10.2.3.1.2 Minimum requirement for *NCR-Fwd type 1-H* + +For *NCR-Fwd type 1-H* this requirement shall be applied at the *TAB connector* supporting transmission in the *operating band*. The beginning and end point of downlink and uplink bursts are referenced to the slot timing at the input. + +For *NCR-Fwd type 1-H*, the *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 6.10.2.2-1. + +## 6.11 Output power dynamics + +### 6.11.1 General + +Output power dynamics is specified in terms of: OFF power, ON/OFF time mask and power control requirements. + +### 6.11.2 Transmit OFF power for NCR-MT + +For WA NCR-MT type 1-C and NCR-MT type 1-H, the BS requirements specified in clause 6.4.1.2 in TS 38.104 applies. + +For LA NCR-MT type 1-C and NCR-MT type 1-H , the UE requirement specified in clause 6.3.2 in TS 38.101-1 applies. + +### 6.11.3 Transmit ON/OFF time mask for NCR-MT + +For WA NCR-MT type 1-C and NCR-MT type 1-H, the BS requirements specified in clause 6.4.2.2 in TS 38.104 applies . + +For LA NCR-MT type 1-C and NCR-MT type 1-H, the UE requirements specified in clause 6.3.3 in TS 38.101-1 applies. + +#### 6.11.4 Power control for NCR-MT + +For WA NCR-MT, The IAB-MT requirements specified in clause 6.3.2 output dynamic range requirement, 6.3.3.1 relative power tolerance and 6.3.3.2 aggregated power tolerance requirements in TS 38.174 applies. + +For LA NCR-MT, The UE requirements specified in clause 6.3.4.3 of relative power tolerance and clause 6.3.4.4 of aggregate power tolerance in TS 38.101-1 applies. + +### 6.12 Transmit signal quality + +#### 6.12.1 General + +Transmit signal quality is specified in terms of: frequency error and transmit modulation quality requirements. + +#### 6.12.2 Frequency error requirements for NCR-MT + +The IAB-MT requirements specified in clause 6.5.1.2 in TS 38.174 apply to both NCR-MT type 1-C and NCR-MT type 1-H. + +#### 6.12.3 Transmit modulation quality + +The IAB-MT requirements specified in clause 6.5.2.2 in TS 38.174 apply to both NCR-MT type 1-C and NCR-MT type 1-H. + +### 6.13 Transmit intermodulation + +#### 6.13.1 General + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +NCR-MT transmit intermodulation is defined by the ratio of the mean power of the wanted signal to the mean power of the intermodulation product when an interfering signal is added at a level below the wanted signal at each transmitter antenna port with the other antenna port(s) if any terminated. + +#### 6.13.2 Minimum requirements for NCR-MT + +The Tx IMD requirement for IAB-MT specified in clause 6.7 of Rel-16 TS 38.174 apply for WA and LA NCR-MT. The IM interference level is based on NCR-Fwd link. + +## 6.14 General + +Conducted receiver characteristics are specified at *antenna connector* for *NCR type 1-C* and TAB connector for *NCR type 1-H*, with full complement of transceivers for the configuration in normal operating condition. + +Unless otherwise stated, the following arrangements apply for conducted receiver characteristics requirements in clause 9: + +- Requirements apply during the receive period. +- Requirements shall be met for any transmitter setting. +- Throughput requirements defined for the conducted receiver characteristics do not assume HARQ retransmissions. +- For ACS, blocking and intermodulation characteristics, the negative offsets of the interfering signal apply relative to the lower *passband edge* or *inter-passband gap*, and the positive offsets of the interfering signal apply relative to the upper *passband edge* or *inter-passband gap*. + +NOTE 1: In normal operating condition the NCR-MT in TDD operation is configured to TX OFF power during *receive period*. + +## 6.15 Diversity characteristics + +The Local Area NCR-MT is required to be equipped with a minimum of two Rx antenna ports in all operating bands except for the bands n7, n38, n41, n48, n77, n78, n79, n104 where the NCR-MT is required to be equipped with a minimum of four Rx antenna ports. This requirement applies when the band is used as a standalone band or as part of a band combination. + +For the single carrier REFSENS requirements in Clause 6.16, the Local Area NCR-MT shall be verified with two Rx antenna ports in all supported frequency bands, additional requirements for four Rx ports shall be verified in operating bands where the NCR-MT is equipped with four Rx antenna ports. + +For Rx requirements other than single carrier REFSENS in Clause 6.16, the NCR-MT shall be verified with four Rx antenna ports and skip two Rx antenna ports requirements in operating bands where the NCR-MT is equipped with four Rx antenna ports, otherwise, the NCR-MT shall be verified with two Rx antenna ports. + +## 6.16 Conducted reference sensitivity + +### 6.16.1 NCR-MT reference sensitivity level + +#### 6.16.1.1 General + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the antenna connector for *NCR-MT type 1-C* or TAB connector for *NCR-MT type 1-H* at which a throughput requirement shall be met for a specified reference measurement channel. + +### 6.16.1.2 Minimum requirements for *NCR-MT type 1-C and 1-H* + +The Wide Area NCR-MT reference sensitivity level is specified the same as the Wide Area IAB-MT reference sensitivity level requirement for *IAB-MT type 1-H* in TS 38.174 [22], clause 7.2.2, where references to *nominal channel bandwidth* apply to NCR-MT *passband*. + +The Local Area NCR-MT reference sensitivity level is specified the same as specified in TS 38.101-1 [13] clause 7.3. + +Referenced requirements applying to NB IoT are not applicable to the NCR-MT. + +## 6.17 Conducted maximum input level + +Maximum input level is defined as the maximum mean power received at the Local Area NCR-MT antenna port, at which the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel. For Local Area NCR-MT, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in 38.101-1 [13] Annex A.3.2 and Annex A.3.3 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex A.5.1.1/A.5.2.1) with parameters specified in TS 38.101-1 [13] in Table 7.4-1. + +## 6.18 Conducted adjacent channel selectivity + +### 6.18.1 Adjacent Channel Selectivity (ACS) + +#### 6.18.1.1 General + +Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency at the antenna connector for *NCR-MT type 1-C* or *TAB connector for NCR-MT type 1-H* in the presence of an adjacent channel signal with a specified centre frequency offset of the interfering signal to the band edge of a victim system. + +### 6.18.1.2 Minimum requirement for *NCR-MT type 1-C* + +For Wide Area *NCR-MT type 1-C*, minimum requirement is the same as specified for BS type 1-C in TS 38.104 [2], clause 7.4.1.2. + +For Local Area *NCR-MT type 1-C*, minimum requirement is the same as specified in TS 38.101-1 [13], clause 7.3.2. + +### 6.18.1.3 Minimum requirement for *NCR-MT type 1-H* + +For Wide Area *NCR-MT type 1-H*, minimum requirement is the same as specified for *IAB-MT type 1-H* in TS 38.174 [22], clause 7.4.1.3. + +For Local Area *NCR-MT type 1-H*, minimum requirement is the same as specified in TS 38.101-1 [13], clause 7.3.2. + +## 6.19 Conducted blocking characteristics + +### 6.19.1 General + +The in-band blocking characteristics is a measure of the receiver's ability to receive a wanted signal at its assigned channel at the *TAB connector* for *NCR-MT type 1-C* and *NCR-MT type 1-H* in the presence of an unwanted interferer, which is an NR signal for general blocking or an NR signal with one resource block for narrowband blocking. + +### 6.19.2 Minimum requirement for NCR-MT type 1-C + +For Wide Area *NCR-MT type 1-C*, minimum requirement is the same as specified for BS type 1-C in TS 38.104 [2], clause 7.4.2.2. + +For Local Area *NCR-MT type 1-C*, minimum requirement is the same as specified in TS 38.101-1 [13] clause 7.6.2. + +### 6.19.3 Minimum requirement for NCR-MT type 1-H + +For Wide Area *NCR-MT type 1-H*, minimum requirement at TAB connector is the same as specified for *IAB-MT* in TS 38.174 [22], clause 7.4.2.3. + +For Local Area *NCR-MT type 1-H*, minimum requirement at TAB connector is the same as specified in TS 38.101-1 [13], clause 7.6.2. + +## 6.20 Conducted spurious response + +### 6.20.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency at the *antenna connector* for *NCR-MT type 1-C* or *TAB connector* for *NCR-MT type 1-H* in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +## 6.20.2 Minimum requirements for NCR-MT type 1-C and NCR-MT type 1-H + +For Local Area *NCR-MT type 1-C* and *NCR-MT type 1-H*, minimum requirements are the same as specified in TS 38.101-1 [13], clause 7.7. + +## 6.21 Conducted intermodulation characteristics + +### 6.21.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency at the antenna connector for *NCR-MT type 1-C* or TAB connector for *NCR-MT type 1-H* in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +### 6.21.2 Minimum requirement for NCR type 1-C + +For Wide Area *NCR-MT type 1-C*, minimum requirement at antenna connector is the same as specified for *BS type 1-C* in TS 38.104 [2], clause 7.7.2. + +For Local Area *NCR-MT type 1-C*, minimum requirement at antenna connector is the same as specified in TS 38.101-1 [13], clause 7.8.2. + +### 6.21.3 Minimum requirement for NCR type 1-H + +For Wide Area *NCR-MT type 1-H*, minimum requirement at TAB connector is the same as specified for *IAB-MT type 1-H* in TS 38.174 [22], clause 7.7.3. + +For Local Area *NCR-MT type 1-H*, minimum requirement at TAB connector is the same as specified in TS 38.101-1 [13], clause 7.8.2. + +## 6.22 Conducted spurious emissions + +### 6.22.1 General + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *antenna connector for NCR-MT type 1-C* and at the *TAB connector for NCR-MT type 1-H*. The requirements apply to all NCR-MT with separate RX and TX TAB connectors. + +For TAB connectors supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF period*. + +For RX-only *multi-band connectors*, the spurious emissions requirements are subject to exclusion zones in each supported *operating band*. For *multi-band connectors* that both transmit and receive in *operating band* supporting TDD, RX spurious emissions requirements are applicable during the *TX OFF period*, and are subject to exclusion zones in each supported *operating band*. + +For *NCR-MT type 1-H* manufacturer shall declare *TAB connector RX min cell groups*. Every *TAB connector* of *-NCR-MT type 1-H* supporting reception in an *operating band* shall map to one *TAB connector RX min cell group*, where mapping of *TAB connectors* to cells/beams is implementation dependent. + +The number of active receiver units that are considered when calculating the conducted RX spurious emission limits ( $N_{\text{RXU,counted}}$ ) for Wide Area *NCR-MT type 1-H* is calculated as follows: + +$$N_{\text{RXU,counted}} = \min(N_{\text{RXU,active}}, 8)$$ + +NOTE: $N_{\text{RXU,active}}$ is the number of actually active receiver units. + +## 6.22.2 Minimum requirements for *NCR-MT type 1-C* and *type 1-H* + +The receiver spurious emissions requirements for *NCR-MT type 1-C* at the antenna connector and *NCR-MT type 1-H* are that for each *TAB connector*, the power of emissions shall not exceed the value specified in table 6.22.2-1. + +**Table 6.22.2-1: *NCR-MT type 1-C* and *type 1-H* receiver spurious emissions minimum requirements** + +| Spurious frequency range | Basic requirements | Measurement bandwidth | Note | +|--------------------------------------------------------------------------------------------------|--------------------|-----------------------|--------------------------------| +| 30 MHz – 1 GHz | -57 dBm | 100 kHz | Note 1 | +| 1 GHz – 12.75 GHz | -47 dBm | 1 MHz | Note 1, Note 2 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 3, Note 5 | +| 12.75 GHz - 26 GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 6 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [5], s4.1. + +NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. + +NOTE 3: This spurious frequency range applies only for operating bands for which the 5th harmonic of the upper frequency edge of the UL operating band is reaching beyond 12.75 GHz. + +NOTE 4: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the repeater transmitter operating band to $\Delta f_{\text{OBUE}}$ above the highest frequency of the repeater transmitter operating band may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause 6.5.1. For multi-band connectors, the exclusion applies for all supported operating bands. + +NOTE 5: Does not apply for band n104. + +NOTE 6: Applies only for band n104. + +## 7 Radiated characteristics + +### 7.1 General + +Radiated characteristics are specified at RIB for *repeater type 2-O*. Requirements apply in both DL and UL unless otherwise stated or declared. + +### 7.2 OTA output power + +#### 7.2.1 General + +*Repeater type 2-O*, *NCR-Fwd type 2-O* are declared to support one or more beams, as per manufacturer's declarations specified in TS 38.115-2 [8]. Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. + +For each beam, the requirement is based on declaration of a beam identity, *reference beam direction pair*, beamwidth, *rated beam EIRP*, *OTA peak directions set*, the *beam direction pairs* at the maximum steering directions and their associated *rated beam EIRP* and beamwidth(s). + +For a declared beam and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the repeater is declared to radiate at the associated *beam peak direction*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing as detailed in TS 38.115-2 [8]. + +NOTE 1: *OTA peak directions set* is set of *beam peak directions* for which the EIRP accuracy requirement is intended to be met. The *beam peak directions* are related to a corresponding contiguous range or discrete list of *beam centre directions* by the *beam direction pairs* included in the set. + +NOTE 2: A *beam direction pair* is data set consisting of the *beam centre direction* and the related *beam peak direction*. + +NOTE 3: A declared EIRP value is a value provided by the manufacturer for verification according to the conformance specification declaration requirements, whereas a claimed EIRP value is provided by the manufacturer to the equipment user for normal operation of the equipment and is not subject to formal conformance testing. + +For *pass bands* where the supported *fractional bandwidth* (FBW) is larger than 6%, two rated beam EIRP may be declared by manufacturer: + +- $P_{\text{rated,out,FBWlow}}$ for lower supported frequency range, and +- $P_{\text{rated,out,FBWhigh}}$ for higher supported frequency range. + +For frequencies in between $F_{\text{FBWlow}}$ and $F_{\text{FBWhigh}}$ the rated beam EIRP is: + +- $P_{\text{rated,out,FBWlow}}$ , for the output whose frequency is within frequency range $F_{\text{FBWlow}} \leq f < (F_{\text{FBWlow}} + F_{\text{FBWhigh}}) / 2$ , +- $P_{\text{rated,out,FBWhigh}}$ , for the output whose frequency is within frequency range $(F_{\text{FBWlow}} + F_{\text{FBWhigh}}) / 2 \leq f \leq F_{\text{FBWhigh}}$ . + +For *repeater type 2-O*, *NCR-Fwd type 2-O*, OTA repeater output power is also declared as a TRP radiated requirement, with the output power accuracy requirement defined at the RIB. TRP does not change with beamforming settings as long as the *beam peak direction* is within the *OTA peak directions set*. Thus, the TRP accuracy requirement shall be met for any beamforming setting for which the *beam peak direction* is within the *OTA peak directions set*. + +There is no upper limit for the *rated TRP output power* and the *rated beam EIRP output power* of *repeater type 2-O* DL transmission. + +The *repeater rated TRP output power* and the *rated beam EIRP output power* for *repeater type 2-O* UL transmission shall be within limits as specified in table 7.2.1-1. + +**Table 7.2.1-1: Repeater rated TRP output power limits and rated EIRP output power limits for repeater type 2-O UL transmission** + +| Repeater class | $P_{\text{rated,p,TRP}}$ | $P_{\text{rated,p,EIRP}}$ | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------| +| Wide Area | (note 1) | (note 1) | +| Local Area | $\leq +35 + X$ dBm (Note 2) | $\leq +55 + X$ dBm (Note 2) | +| NOTE1: There is no upper limit for the $P_{\text{rated,p,TRP}}$ or $P_{\text{rated,p,EIRP}}$ of the repeater type 2-O UL transmission. | | | +| NOTE2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/100\text{MHz}))$ | | | + +There is no upper limit for the *rated TRP output power* and the *rated beam EIRP output power* of *NCR-Fwd type 2-O* DL transmission. + +The *repeater rated TRP output power* and the *rated beam EIRP output power* for *NCR-Fwd type 2-O* UL transmission shall be within limits as specified in table 7.2.1-2. + +**Table 7.2.1-2: Rated TRP output power limits and rated beam EIRP output power limits for NCR-Fwd type 2-O UL transmission** + +| NCR-Fwd class | $P_{\text{rated,p,TRP}}$ | $P_{\text{rated,p,EIRP}}$ | +|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------| +| Wide Area | (note 1) | (note 1) | +| Local Area | $\leq +35 + X$ dBm (Note 2) | $\leq +55 + X$ dBm (Note 2) | +| NOTE1: There is no upper limit for the $P_{\text{rated,p,TRP}}$ or $P_{\text{rated,p,EIRP}}$ of the NCR type 2-O UL transmission. | | | +| NOTE2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/100\text{MHz}))$ | | | + +## 7.2.2 Minimum requirement for NR repeater + +The AoA of the input signal shall be the same as the reference direction for the *OTA peak directions set* when operating in the opposite DL/UL direction. + +The requirements shall apply with NR signals in the *passband* of the repeater at: + +The lowest input power ( $P_{p,in,EIRP}$ ) that produces the *rated passband TRP output power* ( $P_{rated,p,TRP}$ ) + +Up to: + +The lowest input power ( $P_{p,in,EIRP}$ ) that produces the *rated passband TRP output power* ( $P_{rated,p,TRP}$ ), plus 10dB + +In normal conditions, the measured output power, $P_{max,p,EIRP}$ shall remain within +3.4 dB and -3.4 dB of the *rated beam EIRP output power* $P_{rated,p,EIRP}$ , declared by the manufacturer. + +In extreme conditions, the measured output power, $P_{max,p,EIRP}$ shall remain within +4.5 dB and -4.5 dB of the *rated beam EIRP output power* $P_{rated,p,EIRP}$ , declared by the manufacturer. + +In normal conditions, the *repeater type 2-O maximum passband TRP output power*, $P_{max,p,TRP}$ measured at the RIB shall remain within $\pm 3$ dB of the *rated passband TRP output power* $P_{rated,p,TRP}$ , as declared by the manufacturer. + +## 7.2.3 Minimum requirement for NCR + +### 7.2.3.1 Minimum requirement for NCR-MT + +#### 7.2.3.1.1 Minimum requirement for NCR-MT type 1-H + +For NCR-MT type 1-H, the IAB requirement specified in clause 9.2.2 in TS 38.174 apply. + +#### 7.2.3.1.2 Minimum requirement for NCR-MT type 2-O + +For NCR-MT type 2-O, the IAB requirement specified in clause 9.2.3 in TS 38.174 apply. + +### 7.2.3.2 Minimum requirement for NCR-Fwd + +#### 7.2.3.2.1 Minimum requirement for NCR-Fwd type 2-O + +The AoA of the input signal shall be within the *Gain REFSENS RoAoA*. + +The requirements shall apply with NR signals in the *passband* of the NCR-Fwd at: + +- The lowest input power ( $P_{p,in,EIRP}$ ) that produces the *rated passband TRP output power* ( $P_{rated,p,TRP}$ ) + +Up to: + +- The lowest input power ( $P_{p,in,EIRP}$ ) that produces the *rated passband TRP output power* ( $P_{rated,p,TRP}$ ), plus 10dB + +In normal conditions, the measured output power, $P_{max,p,EIRP}$ shall remain within +3.4 dB and -3.4 dB of the *rated beam EIRP output power* $P_{rated,p,EIRP}$ , declared by the manufacturer. + +In extreme conditions, the measured output power, $P_{max,p,EIRP}$ shall remain within +4.5 dB and -4.5 dB of the *rated beam EIRP output power* $P_{rated,p,EIRP}$ , declared by the manufacturer. + +In normal conditions, the *repeater type 2-O maximum passband TRP output power*, $P_{max,p,TRP}$ measured at the RIB shall remain within $\pm 3$ dB of the *rated passband TRP output power* $P_{rated,p,TRP}$ , as declared by the manufacturer. + +## 7.3 OTA frequency stability + +### 7.3.1 General + +Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal. + +OTA frequency stability requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range*. + +### 7.3.2 Minimum requirement for NR repeater + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ PPM. + +### 7.3.3 Minimum requirement for NCR + +#### 7.3.3.1 Minimum requirement for NCR-Fwd + +##### 7.3.3.1.1 Minimum requirement for NCR-Fwd type 2-O + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ PPM. + +## 7.4 OTA out of band gain + +### 7.4.1 General + +Out of band gain refers to the gain of the repeater outside the *passband*. + +The requirement is based on the ratio of TRP output power to directional input power. + +The intended use of a repeater in a system is to amplify the in-band signals and not to amplify signals outside of the *passband*. + +In the intended application of the repeater, the out of band gain is less than lowest expected the coupling loss to the nearest source of emissions. + +### 7.4.2 Minimum requirement for NR repeater + +The gain outside the *passband* shall not exceed the maximum level specified in table 7.4.2-1, where: + +- $f\_offset\_CW$ is the offset between the outer channel edge frequency of the outer channel in the *passband* and a CW signal. + +**Table 7.4.2-1: Out of band gain limits 1** + +| Frequency offset, $f\_offset\_CW$ | Maximum gain | +|--------------------------------------------------------------------------------------------------------|--------------| +| $0.1 \cdot \text{Minimum } \{400\text{MHz}, \text{passband BW}\} \leq f\_offset\_CW < 150 \text{ MHz}$ | 68 dB | +| $150 \text{ MHz} \leq f\_offset\_CW < 400 \text{ MHz}$ | 55 dB | +| $400 \text{ MHz} \leq f\_offset\_CW < f\_offset\_max$ | 35 dB | + +## 7.4.3 Minimum requirement for NCR + +### 7.4.3.1 Minimum requirement for NCR-Fwd + +#### 7.4.3.1.1 Minimum requirement for NCR-Fwd type 2-O + +The gain outside the *passband* shall not exceed the maximum level specified in Table 7.4.2-1. + +## 7.5 OTA unwanted emissions + +### 7.5.1 General + +Unwanted emissions consist of so-called out-of-band emissions and spurious emissions according to ITU definitions ITU-R SM.329 [5]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the *passband* resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +The OTA out-of-band emissions requirement for the *repeater type 2-O* transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and operating band unwanted emissions (OBUE). OTA Unwanted emissions outside of this frequency range are limited by an OTA spurious emissions requirement. + +The maximum offset of the operating band unwanted emissions mask from the *operating band* edge is $\Delta f_{\text{OBUE}}$ . The value of $\Delta f_{\text{OBUE}}$ are defined in table 7.5.1-1 and 7.5.1-2 for *repeater type 2-O* for NR *operating bands*. + +**Table 7.5.1-1: Maximum offset $\Delta f_{\text{OBUE}}$ outside the downlink *operating band* for *repeater type 2-O* and *NCR-Fwd type 2-O DL*** + +| Repeater type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|-------------------|----------------------------------------------------------------|--------------------------------| +| Repeater type 2-O | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 4000 \text{ MHz}$ | 1500 | +| NCR-Fwd type 2-O | | | + +**Table 7.5.1-2: Maximum offset $\Delta f_{\text{OBUE}}$ outside the downlink operating band for repeater type 2-O and NCR-Fwd type 2-O UL** + +| Repeater type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|----------------------------------------|----------------------------------------------------------------|--------------------------------| +| Repeater type 2-O,
NCR-Fwd type 2-O | $F_{\text{UL,high}} - F_{\text{UL,low}} \leq 4000 \text{ MHz}$ | 1500 | + +The unwanted emission requirements are applied per cell for all the configurations. Requirements for OTA unwanted emissions are captured using TRP, *directional requirements* or co-location requirements as described per requirement. + +If the NCR supports simultaneous NCR-MT and NCR-Fwd transmission, then the unwanted emissions requirements should be defined on the total emissions from NCR-MT and NCR-Fwd. + +## 7.5.2 OTA Adjacent Channel Leakage Power Ratio (ACLR) + +### 7.5.2.1 General + +OTA Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. The measured power is TRP. + +The requirement shall be applied per RIB during the *transmitter ON state*. + +### 7.5.2.2 Minimum requirement for NR Repeater + +The OTA ACLR limit is specified in table 7.5.2.2-1 for DL and UL for Wide Area class and DL for Local Area class. + +The OTA ACLR limit is specified in table 7.5.2.2-1a for UL for Local Area class. + +The OTA ACLR absolute limit is specified in table 7.5.2.2-2. + +Either the OTA ACLR (CACLR) absolute limit in table 7.5.2.2-2 or 7.5.2.2-5 or the relevant ACLR (CACLR) limit in table 7.5.2.2-1, 7.5.2.2-1a, 7.5.2.2-3, 7.5.5.2-3a, 7.5.2.2-4 or 7.5.2.2-4a, whichever is less stringent, shall apply. + +For a RIB operating in *non-contiguous spectrum*, the OTA ACLR requirement in table 7.5.2.2-3 shall apply in *gaps between passbands* for the frequency ranges defined in the table, while the OTA CACLR requirement in table 7.5.2.2-4 shall apply in *gaps between passbands* for the frequency ranges defined in the table. + +The CACLR in a *gap between passbands* is the ratio of: + +- the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the *gap between passbands*, and +- the filtered mean power centred on a frequency channel adjacent to one of the respective *passband* edges. + +The assumed filter for the adjacent channel frequency is defined in table 7.5.2.2-4 and the filters on the assigned channels are defined in table 7.5.2.2-6. + +For operation in *non-contiguous spectrum*, the CACLR for NR carriers located on either side of the *gap between passbands* shall be higher than the value specified in table 7.5.2.2-4. + +**Table 7.5.2.2-1: Repeater type 2-O ACLR limit for DL and UL for WA class and DL for LA class** + +| Repeater nominal channel bandwidth $BW_{Nominal}$ (MHz) | Repeater adjacent channel centre frequency offset below or above the passband edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit (dB) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 50, 100, 200, 400 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 28 (Note 3)
26 (Note 4) | +| NOTE 1: $BW_{Nominal}$ is the nominal channel bandwidth . $BW_{Config}$ is the transmission bandwidth configuration assumed for the adjacent channel.
NOTE 2: With SCS that provides the largest transmission bandwidth configuration ( $BW_{Config}$ ).
NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz
NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz | | | | | + +**Table 7.5.2.2-1a: Repeater type 2-O ACLR limit for UL LA class** + +| Repeater nominal channel bandwidth $BW_{Nominal}$ (MHz) | Repeater adjacent channel centre frequency offset below or above the passband edge | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit (dB) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 50, 100, 200, 400 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 17 (Note 3)
16 (Note 4) | +| NOTE 1: $BW_{Nominal}$ is the nominal channel bandwidth . $BW_{Config}$ is the transmission bandwidth configuration assumed for the adjacent channel.
NOTE 2: With SCS that provides the largest transmission bandwidth configuration ( $BW_{Config}$ ).
NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz
NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz | | | | | + +**Table 7.5.2.2-2: Repeater type 2-O ACLR absolute limit** + +| Repeater class | ACLR absolute limit | +|---------------------|---------------------| +| Wide area DL and UL | -13 dBm/MHz | +| Medium range DL | -20 dBm/MHz | +| Local area DL | -20 dBm/MHz | + +**Table 7.5.2.2-3: Repeater type 2-O ACLR limit in non-contiguous spectrum for DL and UL for WA class and DL for LA class** + +| Repeater nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 50, 100, 200, 400 | $W_{gap} \geq 100$ (Note 5)
$W_{gap} \geq 250$ (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 28 (Note 3)
26 (Note 4) | +| 50, 100, 200, 400 | $W_{gap} \geq 400$ (Note 6)
$W_{gap} \geq 250$ (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 28 (Note 3)
26 (Note 4) | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. + +NOTE 5: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $\leq 100$ MHz. + +NOTE 6: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $> 100$ MHz. + +**Table 7.5.2.2-3a: Repeater type 2-O ACLR limit in non-contiguous spectrum for UL for LA class** + +| Repeater nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 50, 100, 200, 400 | $W_{gap} \geq 100$ (Note 5)
$W_{gap} \geq 250$ (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 17 (Note 3)
16 (Note 4) | +| 50, 100, 200, 400 | $W_{gap} \geq 400$ (Note 6)
$W_{gap} \geq 250$ (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 17 (Note 3)
16 (Note 4) | + +NOTE 1: $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. + +NOTE 5: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $\leq 100$ MHz. + +NOTE 6: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $> 100$ MHz. + +**Table 7.5.2.2-4: Repeater type 2-O CACLR limit in non-contiguous spectrum for DL and UL for WA class and DL for LA class** + +| Repeater nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|---------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 50, 100, 200, 400 | $50 \leq W_{gap} < 100$ (Note 5)
$50 \leq W_{gap} < 250$ (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 28 (Note 3)
26 (Note 4) | +| 50, 100, 200, 400 | $200 \leq W_{gap} < 400$ (Note 6)
$200 \leq W_{gap} < 250$ (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 28 (Note 3)
26 (Note 4) | + +NOTE 1: $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. +NOTE 5: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $\leq 100$ MHz. +NOTE 6: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $> 100$ MHz. + +**Table 7.5.2.2-4a: Repeater type 2-O CACLR limit in non-contiguous spectrum for UL for LA class** + +| Repeater nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater adjacent channel centre frequency offset below or above the passband edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|---------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|----------------------------| +| 50, 100, 200, 400 | $50 \leq W_{gap} < 100$ (Note 5)
$50 \leq W_{gap} < 250$ (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 17 (Note 3)
16 (Note 4) | +| 50, 100, 200, 400 | $200 \leq W_{gap} < 400$ (Note 6)
$200 \leq W_{gap} < 250$ (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 17 (Note 3)
16 (Note 4) | + +NOTE 1: $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. + +NOTE 5: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $\leq 100$ MHz. + +NOTE 6: Applicable in case the *repeater type 2-O nominal channel bandwidth* at the other edge of the gap is $> 100$ MHz. + +**Table 7.5.2.2-5: Repeater type 2-O CACLR absolute limit** + +| Repeater class | CACLR absolute limit | +|---------------------|----------------------| +| Wide area DL and UL | -13 dBm/MHz | +| Medium range DL | -20 dBm/MHz | +| Local area DL | -20 dBm/MHz | + +**Table 7.5.2.2-6: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the gap between passbands | Filter on the assigned channel frequency and corresponding filter bandwidth | +|----------------------------------------------------------|------------------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +### 7.5.2.3 Minimum requirement for NCR + +#### 7.5.2.3.1 Minimum requirement for NCR-Fwd + +##### 7.5.2.3.1.1 Minimum requirement for NCR-Fwd *type 2-O* + +The requirements in clause 7.5.2.2 apply for NCR-Fwd *type 2-O*. The limits apply to the sum of emissions from NCR-MT and NCR-FWD when transmitting simultaneously. + +#### 7.5.2.3.2 Minimum requirement for NCR-MT + +##### 7.5.2.3.2.1 Minimum requirement for NCR-MT *type 2-O* + +For WA NCR-MT *type 2-O*, the BS ACLR requirements specified in clause 9.7.3.3 in TS 38.104 apply. + +For LA NCR-MT *type 2-O*, the UE ACLR requirements specified in clause 6.5.2.3 in TS 38.101-2 apply. + +For simultaneous transmission the limits apply for sum of NCR-MT transmission and NCR-Fwd transmission + +## 7.5.3 OTA operating band unwanted emissions + +### 7.5.3.1 General + +The OTA limits for operating band unwanted emissions are specified as TRP per RIB unless otherwise stated. + +In addition to, for the part of passband where there is no input signal, -13dBm/MHz shall apply for all classes DL and UL. + +### 7.5.3.2 Minimum requirement for NR repeater + +#### 7.5.3.2.1 General + +The requirements of either clause 7.5.3.2.2 (Category A limits) or clause 7.5.3.2.3 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for General OTA transmitter spurious emissions requirements (*repeater type 2-O*) in clause 7.5.3.3.2. In addition, the limits in clause 7.5.3.2.4 may also apply. + +Out-of-band emissions in FR2 are limited by OTA operating band unwanted emission limits. + +For *repeater type 2-O*, unless otherwise stated, the OTA operating band unwanted emission limits in FR2 are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported downlink *operating band*. + +The values of $\Delta f_{\text{OBUE}}$ are defined in table 7.5.1-1 and 7.5.1-2 for the NR *operating bands*. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. For a *RIB* operating in contiguous CA, the requirements apply to the frequencies ( $\Delta f_{\text{OBUE}}$ ) starting from the edge of the *passband*. In addition, for a *RIB* operating in *non-contiguous spectrum*, the requirements apply inside any *gap between passbands*. + +Emissions shall not exceed the maximum levels specified in the tables below, where: + +- $\Delta f$ is the separation between the *passband* edge frequency and the nominal -3dB point of the measuring filter closest to the *passband* edge. +- $f\_offset$ is the separation between the *passband* edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ outside the downlink *operating band*, where $\Delta f_{OBUE}$ is defined in table 7.5.1-1 and 7.5.1-2.. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +In addition, inside any *gap between passbands* for a RIB operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the limits specified for the adjacent *sub-blocks* on each side of the *gap between passbands*. The limit for each *sub-block* is specified in clauses 7.5.3.2.2 and 7.5.3.2.3 below, where in this case: + +- $\Delta f$ is the separation between the *sub-block* edge frequency and the nominal -3 dB point of the measuring filter closest to the *sub-block* edge. +- $f\_offset$ is the separation between the *sub-block* edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *gap between passbands* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +### 7.5.3.2.2 OTA operating band unwanted emission limits (Category A) + +*Repeater type 2-O* unwanted emissions shall not exceed the maximum levels specified in tables 7.5.3.2.2-1 and 7.5.3.2.2-2. + +**Table 7.5.3.2.2-1: OBUE limits applicable in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Limit | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 * BW_{contiguous}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 * BW_{contiguous} + 0.5 \text{ MHz}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{rated,t,TRP} - 35 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 * BW_{contiguous} \leq \Delta f < \Delta f_{max}$ | $0.1 * BW_{contiguous} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{rated,t,TRP} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| NOTE 1: For non-contiguous spectrum operation within any operating band the limit within gaps between passbands is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the gap between passbands . | | | | + +**Table 7.5.3.2.2-2: OBUE limits applicable in the frequency range 37 – 52.6 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Limit | Measurement bandwidth | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\text{max}}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | + +NOTE 1: For *non-contiguous spectrum* operation within any *operating band* the limit within gaps between passbands is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the gap between passbands. + +### 7.5.3.2.3 OTA operating band unwanted emission limits (Category B) + +*Repeater type 2-O* unwanted emissions shall not exceed the maximum levels specified in table 7.5.3.2.3-1 or 7.5.3.2.3-2. + +**Table 7.5.3.2.3-1: OBUE limits applicable in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Limit | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 35 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_B$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < \Delta f_B + 0.5 \text{ MHz}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| $\Delta f_B \leq \Delta f < \Delta f_{\text{max}}$ | $\Delta f_B + 5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -10 \text{ dBm}))$ | 10 MHz | + +NOTE 1: For non-contiguous spectrum operation within any *operating band* the limit within gaps between passbands is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the gap between passbands. + +NOTE 2: $\Delta f_B = 2 \cdot \text{BW}_{\text{contiguous}}$ when $\text{BW}_{\text{contiguous}} \leq 500 \text{ MHz}$ , otherwise $\Delta f_B = \text{BW}_{\text{contiguous}} + 500 \text{ MHz}$ . + +**Table 7.5.3.2.3-2: OBUE limits applicable in the frequency range 37 – 52.6 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Limit | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_B$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < \Delta f_B + 0.5 \text{ MHz}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| $\Delta f_B \leq \Delta f < \Delta f_{\text{max}}$ | $\Delta f_B + 5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 31 \text{ dB}, -10 \text{ dBm}))$ | 10 MHz | + +NOTE 1: For non-contiguous spectrum operation within any *operating band* the limit within gaps between *passbands* is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the gap between *passbands*. + +NOTE 2: $\Delta f_B = 2 \cdot \text{BW}_{\text{contiguous}}$ when $\text{BW}_{\text{contiguous}} \leq 500 \text{ MHz}$ , otherwise $\Delta f_B = \text{BW}_{\text{contiguous}} + 500 \text{ MHz}$ . + +#### 7.5.3.2.4 Additional OTA operating band unwanted emission requirements + +##### 7.5.3.2.4.1 Protection of Earth Exploration Satellite Service + +For repeater operating in the frequency range 24.25 – 27.5 GHz, the power of unwanted emission shall not exceed the limits in table 7.5.3.2.4.1-1 for DL and in table 7.5.3.2.4.1-2. + +**Table 7.5.3.2.4.1-1: OBUE limits for protection of Earth Exploration Satellite Service for DL** + +| Frequency range | Limit | Measurement Bandwidth | +|-----------------|-----------------|-----------------------| +| 23.6 – 24 GHz | -3 dBm (Note 1) | 200 MHz | +| 23.6 – 24 GHz | -9 dBm (Note 2) | 200 MHz | + +NOTE 1: This limit applies to repeater brought into use on or before 1 September 2027. + +NOTE 2: This limit applies to repeater brought into use after 1 September 2027. + +**Table 7.5.3.2.4.1-2: OBUE limits for protection of Earth Exploration Satellite Service for UL** + +| Frequency range | Limit | Measurement Bandwidth | +|-----------------|-------|-----------------------| +| 23.6 – 24 GHz | 1 dBm | 200 MHz | + +### 7.5.3.3 Minimum requirement for NCR + +#### 7.5.3.3.1 Minimum requirement for NCR-Fwd + +##### 7.5.3.3.1.1 Minimum requirement for NCR-Fwd *type 2-O* + +The requirements in clause 7.5.3.2 apply for NCR-Fwd *type 2-O*. The limits apply to the sum of emissions from NCR-MT and NCR-FWD when transmitting simultaneously. + +#### 7.5.3.3.2 Minimum requirement for NCR-MT + +##### 7.5.3.3.2.1 Minimum requirement for NCR-MT *type 2-O* + +For Wide Area *NCR-MT type 2-O*, the BS OBUE requirements specified in clause 9.7.4.3 in TS 38.104 apply. + +For Local Area *NCR-MT type 2-O*, the UE SEM requirements specified in clause 6.5.2.1 in TS 38.101-2 apply. + +## 7.5.4 OTA transmitter spurious emissions + +### 7.5.4.1 General + +Unless otherwise stated, all requirements are measured as mean power. + +The OTA spurious emissions limits are specified as TRP per RIB unless otherwise stated. + +### 7.5.4.2 Minimum requirement for *NR repeater* + +#### 7.5.4.2.1 General + +For *repeater type 2-O*, the OTA transmitter spurious emission limits apply from 30 MHz to 2nd harmonic of the upper frequency edge of the downlink *operating band*, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 7.5.1-1 and 7.5.1-2. + +### 7.5.4.2.2 General OTA transmitter spurious emissions requirements + +#### 7.5.4.2.2.1 General + +The requirements of either clause 7.5.4.2.2.2 (Category A limits) or clause 7.5.4.2.2.3 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for Operating band unwanted emissions in clause 7.5.3. + +#### 7.5.4.2.2.2 OTA transmitter spurious emissions (Category A) + +The power of any spurious emission shall not exceed the limits in table 7.5.4.2.2.2-1. + +**Table 7.5.4.2.2.2-1: Repeater radiated Tx spurious emission limits in FR2** + +| Frequency range | Limit | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------|---------|-----------------------|----------------| +| 30 MHz – 1 GHz | -13 dBm | 100 kHz | Note 1 | +| 1 GHz – 2 nd harmonic of the upper frequency edge of the passband | | 1 MHz | Note 1, Note 2 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [5], s4.1 | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. | | | | + +#### 7.5.4.2.2.3 OTA transmitter spurious emissions (Category B) + +The power of any spurious emission shall not exceed the limits in table 7.5.4.2.2.3-1. + +**Table 7.5.4.2.2.3-1: Repeater radiated Tx spurious emission limits in FR2 (Category B)** + +| Frequency range (Note 4) | Limit | Measurement Bandwidth | Note | +|---------------------------------------------------------------------------------------------------|---------|-----------------------|----------------| +| 30 MHz ↔ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz ↔ 18 GHz | -30 dBm | 1 MHz | Note 1 | +| 18 GHz ↔ F step,1 | -20 dBm | 10 MHz | Note 2 | +| F step,1 ↔ F step,2 | -15 dBm | 10 MHz | Note 2 | +| F step,2 ↔ F step,3 | -10 dBm | 10 MHz | Note 2 | +| F step,4 ↔ F step,5 | -10 dBm | 10 MHz | Note 2 | +| F step,5 ↔ F step,6 | -15 dBm | 10 MHz | Note 2 | +| F step,6 ↔ 2 nd harmonic of the upper frequency edge of the passband | -20 dBm | 10 MHz | Note 2, Note 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [5], s4.1 | | | | +| NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [9], Annex 2. | | | | +| NOTE 3: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. | | | | +| NOTE 4: The step frequencies F step,x are defined in Table 7.5.4.2.2.3-2. | | | | + +**Table 7.5.4.2.2.3-2: Step frequencies for defining the Repeater radiated Tx spurious emission limits in FR2 (Category B)** + +| Operating band | F step,1
(GHz) | F step,2
(GHz) | F step,3
(GHz)
(Note 2) | F step,4
(GHz)
(Note 2) | F step,5
(GHz) | F step,6
(GHz) | +|--------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------|------------------------------------------|------------------------------------------|------------------------------|------------------------------| +| n258 | 18 | 21 | 22.75 | 29 | 30.75 | 40.5 | +| n259 | 23.5 | 35.5 | 38 | 45 | 47.5 | 59.5 | +| NOTE 1: F step,x are based on ERC Recommendation 74-01 [9], Annex 2. | | | | | | | +| NOTE 2: F step,3 and F step,4 are aligned with the values for Δf OBUE in Table 7.5.1-1. | | | | | | | + +### 7.5.4.2.3 Additional OTA transmitter spurious emissions requirements + +These requirements may be applied for the protection of systems operating in frequency ranges other than the repeater-Node. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the repeater-Node, or they may be set by local or regional regulation as a mandatory requirement for an NR operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. An overview of regional requirements in the present document is given in clause 4.4. + +#### 7.5.4.2.3.1 Limits for protection of Earth Exploration Satellite Service + +For repeater operating in the frequency range 24.25 – 27.5 GHz, the power of any spurious emissions shall not exceed the limits in Table 7.5.4.2.3.1-1 and Table 7.5.4.2.3.1-2. + +**Table 7.5.4.2.3.1-1: Limits for protection of Earth Exploration Satellite Service for DL** + +| Frequency range | Limit | Measurement
Bandwidth | Note | +|----------------------------------------------------------------------------------------|--------|--------------------------|--------| +| 23.6 – 24 GHz | -3 dBm | 200 MHz | Note 1 | +| 23.6 – 24 GHz | -9 dBm | 200 MHz | Note 2 | +| NOTE 1: This limit applies to Repeater brought into use on or before 1 September 2027. | | | | +| NOTE 2: This limit applies to Repeater brought into use after 1 September 2027. | | | | + +**Table 7.5.4.2.3.1-2: OBUE limits for protection of Earth Exploration Satellite Service for UL** + +| Frequency range | Limit | Measurement
Bandwidth | +|-----------------|-------|--------------------------| +| 23.6 – 24 GHz | 1 dBm | 200 MHz | + +### 7.5.4.3 Minimum requirement for *NCR* + +#### 7.5.4.3.1 Minimum requirement for NCR-Fwd + +##### 7.5.4.3.1.1 Minimum requirement for *NCR-Fwd type 2-O* + +The requirements in clause 7.5.4.2 apply. The limits apply to the sum of emissions from NCR-MT and NCR-FWD when transmitting simultaneously. + +#### 7.5.4.3.2 Minimum requirement for NCR-MT + +##### 7.5.4.3.2.1 Minimum requirement for NCR-MT Type 2-O + +For Wide Area *NCR-MT type 2-O*, the OTA TX spurious emission requirements are as defined in clause 7.5.4.2. + +For Local Area *NCR-MT type 2-O*, the OTA TX spurious emission requirements defined for NR UE in clause 6.5.3 in TS 38.101-2 apply. + +## 7.5.5 OTA receiver spurious emissions + +### 7.5.5.1 General + +The OTA RX spurious emission is the power of the emissions radiated from the antenna array from a receiver unit. + +The metric used to capture OTA receiver spurious emissions is *total radiated power* (TRP), with the requirement defined at the RIB. + +For a RIB operating in FDD, OTA RX spurious emissions requirement do not apply as they are superseded by the OTA TX spurious emissions requirement. This is due to the fact that TX and RX spurious emissions cannot be distinguished in OTA domain. + +For a RIB operating in TDD, the OTA RX spurious emissions requirement shall apply during the *transmitter OFF state* only. + +For *multi-band RIB*, the OTA RX spurious emissions requirements are subject to exclusion zones in each supported operating band. + +### 7.5.5.2 Minimum requirement for *NR repeater* + +For the *Repeater type 2-O*, the power of any RX spurious emission shall not exceed the limits in table 7.5.5.2-1. + +### 7.5.5.2-1: OTA receiver spurious emission limits for *Repeater type 2-O* + +| Spurious frequency range (Note 4) | Limit (Note 5) | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------|----------------|-----------------------|----------------| +| 30 MHz $\leftrightarrow$ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz $\leftrightarrow$ 18 GHz | -30 dBm | 1 MHz | Note 1 | +| 18 GHz $\leftrightarrow$ $F_{\text{step},1}$ | -20 dBm | 10 MHz | Note 2 | +| $F_{\text{step},1} \leftrightarrow F_{\text{step},2}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},2} \leftrightarrow F_{\text{step},3}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},4} \leftrightarrow F_{\text{step},5}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},5} \leftrightarrow F_{\text{step},6}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},6} \leftrightarrow$ 2 nd harmonic of the upper frequency edge of the UL operating band | -20 dBm | 10 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [5], s4.1. + +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [9], Annex 2. + +NOTE 3: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. + +NOTE 4: The step frequencies $F_{\text{step},x}$ are defined in table 7.5.5.3-2. + +NOTE 5: Additional limits may apply regionally. + +**Table 7.5.5.2-2: Step frequencies for defining the OTA receiver spurious emission limits for *Repeater type 2-O*** + +| Operating band | $F_{\text{step},1}$ (GHz) | $F_{\text{step},2}$ (GHz) | $F_{\text{step},3}$ (GHz) | $F_{\text{step},4}$ (GHz) | $F_{\text{step},5}$ (GHz) | $F_{\text{step},6}$ (GHz) | +|----------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------| +| n257 | 18 | 23.5 | 25 | 31 | 32.5 | 41.5 | +| n258 | 18 | 21 | 22.75 | 29 | 30.75 | 40.5 | +| n259 | 23.5 | 35.5 | 38 | 45 | 47.5 | 59.5 | +| n260 | 25 | 34 | 35.5 | 41.5 | 43 | 52 | +| n261 | 18 | 25.5 | 26.0 | 29.85 | 30.35 | 38.35 | +| n262 | 37.2 | 45.2 | 45.7 | 49.7 | 50.2 | 58.2 | +| n263 | 18 | 43 | 53.5 | 74.5 | 85 | 127 | + +In addition to the requirements in Table 7.5.5.2-1, the requirement for protection of EESS for *NR repeater* operating in frequency range 24.25 – 27.5 GHz in clause 7.5.4.2.3.1 may be applied. + +### 7.5.5.3 Minimum requirement for *NCR* + +#### 7.5.5.3.1 Minimum requirement for *NCR-Fwd* + +##### 7.5.5.3.1.1 Minimum requirement for *NCR-Fwd type 2-O* + +The requirements in clause 7.5.5.2 apply. + +The receiver spurious emissions limits shall apply to the total emissions from both the NCR-Fwd and NCR-MT. + +## 7.6 OTA Repeater Error Vector Magnitude + +### 7.6.1 Downlink repeater error vector magnitude + +#### 7.6.1.1 General + +The Repeater Error Vector Magnitude (EVM) is a measure of the difference between the symbols provided at the input of the repeater and the measured signal symbols at the output of the repeater after the equalization by the measurement equipment. This difference is called the error vector. Details about how the repeater EVM is determined are same as specified in TS 38.104 [2] Annex C for FR2. The repeater EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed in percent. + +For repeater type 2-O, OTA modulation quality requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range* on the transmit side and the AoA of the incident wave of the received signal is in the reference direction at the receive side. + +For NCR-Fwd type 2-O, OTA modulation quality requirement is defined as a directional requirement at the RIB and shall be met within the OTA coverage range on the transmit side and the AoA of the incident wave of the received signal is within the OTA REFSSENS RoAoA at the receive side. + +The repeater EVM requirement is applicable when the repeater is operating with an input power level within the range from what is required to reach the rated beam EIRP output power ( $P_{\text{rated,p,EIRP}}$ ) to the minimum power levels in table 7.6.1.1-1. + +**Table 7.6.1.1-1: Minimum input power for repeater EVM for repeater type 2-O and NCR-Fwd type 2-O** + +| Repeater class | Minimum input power (dBm/MHz) | | | | | | +|-------------------|-------------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------| +| | 24.25 – 33.4 GHz | | | 37 – 52.6 GHz | | | +| | Up to 16 QAM | 64QAM 1 | 256QAM 2 | Up to 16 QAM | 64QAM 1 | 256QAM 2 | +| WA, MR, LA | $-77 - G_{\text{RX\_ANT}}$ | $-73 - G_{\text{RX\_ANT}}$ | $-66 - G_{\text{RX\_ANT}}$ | $-75 - G_{\text{RX\_ANT}}$ | $-71 - G_{\text{RX\_ANT}}$ | $-64 - G_{\text{RX\_ANT}}$ | + +Note 1: support of 64QAM is based on the declaration +Note 2: support of 256QAM is based on the declaration + +Where $G_{\text{RX\_ANT}}$ is the gain of the receive side antennas and is estimated based on the 3dB gain RoAoA and a formula, $G_{\text{RX\_ANT}} = 44.1 - 10 \cdot \log_{10}(\text{BeW}_{\theta, \text{REFSENS}} \cdot \text{BeW}_{\phi, \text{REFSENS}})$ dB. + +#### 7.6.1.2 Minimum requirement for NR repeater + +The repeater EVM levels for different modulation schemes outlined in table 7.6.1.2-1 shall be met using the frame structure described in clause 7.6.1.3. + +**Table 7.6.1.2-1: Repeater EVM requirements** + +| Parameter | Required repeater EVM | +|--------------------------------------------------------|-----------------------| +| Up to 16QAM | 12.5% | +| 64QAM | 8 % 1 | +| 256QAM | 3.5 % 2 | +| Note 1: support of 64QAM is based on the declaration | | +| Note 2: support of 256QAM is based on the declaration. | | + +### 7.6.1.2A Minimum requirement for NCR + +#### 7.6.1.2A.1 Minimum requirement for NCR-Fwd + +##### 7.6.1.2A.1.1 Minimum requirement for NCR-Fwd type 2-O + +The requirements in clause 7.6.1.2 apply for NCR-Fwd type 2-O. + +### 7.6.1.3 Repeater EVM frame structure for measurement + +The input signals for the repeater EVM requirement shall have the same frame structure as defined for the BS in TS 38.104 [2]. + +## 7.6.2 Uplink repeater error vector magnitude + +### 7.6.2.1 General + +The Repeater Error Vector Magnitude is a measure of the difference between the reference waveform provided at the input of repeater and the measured waveform at the output of the repeater. This difference is called the error vector. Details about how the repeater EVM is determined are the same as specified in TS 38.101-2 [14] Annex F for FR2. Before calculating the repeater EVM, the measured waveform is corrected by the sample timing offset and RF frequency offset. Then the carrier leakage shall be removed from the measured waveform before calculating the repeater EVM. + +The measured waveform is further equalised using the channel estimates subjected to the EVM equaliser spectrum flatness requirement specified in TS 38.101-2 [14] clauses 6.4.2.4 and 6.4.2.5. For DFT-s-OFDM waveforms, the repeater EVM result is defined after the front-end FFT and IDFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. For CP-OFDM waveforms, the repeater EVM result is defined after the front-end FFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. + +The basic repeater EVM measurement interval is one slot in the time domain. The repeater EVM measurement interval is reduced by any symbols that contains an allowable power transient in the measurement interval as defined in TS 38.101-2 [14] clause 6.3.3. + +All the parameters defined in clause 7.6.2 are defined using the measurement methodology specified in TS 38.101-2 [14] Annex F. + +For *repeater type 2-O*, OTA modulation quality requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range* on the transmit side and the AoA of the incident wave of the received signal is in the reference direction at the receive side. + +For *NCR-Fwd type 2-O*, OTA modulation quality requirement is defined as a directional requirement at the RIB and shall be met within the OTA coverage range on the transmit side and the AoA of the incident wave of the received signal is within the OTA REFESENS RoAoA at the receive side. + +The repeater EVM requirement is applicable when the repeater is operating with an input power level within the range from what is required to reach the rated beam EIRP output power ( $P_{\text{rated,p,EIRP}}$ ) to the minimum input power levels in table 7.6.2.1-1. + +**Table 7.6.2.1-1: Minimum input power for repeater EVM for repeater type 2-O and NCR-Fwd type 2-O** + +| Repeater class | Minimum input power (dBm/MHz) | | | | +|------------------------------------------------------|-------------------------------|---------------------------|---------------------------|---------------------------| +| | 24.25 – 33.4 GHz | | 37 – 52.6 GHz | | +| | Up to 16 QAM | 64QAM 1 | Up to 16 QAM | 64QAM 1 | +| WA, LA | -77- $G_{\text{RX\_ANT}}$ | -73- $G_{\text{RX\_ANT}}$ | -75- $G_{\text{RX\_ANT}}$ | -71- $G_{\text{RX\_ANT}}$ | +| Note 1: support of 64QAM is based on the declaration | | | | | + +Where $G_{\text{RX\_ANT}}$ is the gain of the receive side antennas and is estimated based on the 3dB gain RoAoA and a formula, $G_{\text{RX\_ANT}} = 44.1 - 10 \cdot \log_{10}(\text{BeW}_{\theta, \text{REFSENS}} \cdot \text{BeW}_{\phi, \text{REFSENS}})$ dB. + +## 7.6.2.2 Minimum requirement for NR repeater + +The RMS average of the basic repeater EVM measurements over 10 subframes for the average repeater EVM case, for the different modulation schemes shall not exceed the values specified in Table 7.6.2.2-1. + +**Table 7.6.2.2-1: Minimum requirements for repeater error vector magnitude** + +| Parameter | Unit | Average repeater EVM level | +|------------------------------------------------------|------|----------------------------| +| Up to 16 QAM | % | 12.5 | +| 64 QAM | % | 8 1 | +| Note 1: support of 64QAM is based on the declaration | | | + +## 7.6.2.3 Minimum requirement for NCR + +### 7.6.2.3.1 Minimum requirement for NCR-Fwd + +#### 7.6.2.3.1.1 Minimum requirement for *NCR-Fwd type 2-O* + +The requirements in clause 7.6.2.2 apply for *NCR-Fwd type 2-O*. + +## 7.7 OTA input intermodulation + +### 7.7.1 General + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the *passband*, in the presence of interfering signals on frequencies other than the *passband*. The requirement is defined as a directional requirement. + +The requirement shall apply at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction: + +The interfering signals apply to each supported polarization, under the assumption of polarization match. + +The following requirement applies for interfering signals depending on the repeaters *passband*. + +This requirement applies to the uplink and downlink of the repeater during the *transmitter ON state*. + +When GSM, CDMA, UTRA, E-UTRA, NR BS or repeater operating in a different frequency band are co-located with a NCR, additional input intermodulation co-location requirement may be applied for the protection of NR repeater or NCR receivers. This requirement applies to the uplink and downlink of the repeater. If the BS side is declared to meet co-location requirements, then it should meet input intermodulation co-location requirements for the downlink. If the UE side is declared to meet co-location requirements, then it should meet input intermodulation co-location requirements for the uplink. + +When GSM, CDMA, UTRA, E-UTRA, NR BS or repeater operating in another frequency band co-exist with a NCR, additional input intermodulation co-existence requirement may be applied for the protection of NR repeater or NCR receivers. + +### 7.7.2 Minimum requirement for NR repeater + +For the parameters specified in table 7.7.2-1, the power in the *passband* shall not increase with more than 10 dB at the output of the repeater as measured with 1 MHz measurement bandwidth, compared to the level obtained without interfering signals applied. + +The core requirement is applicable for all frequency separation possibilities between the two interfering signals that cause the 3rd order intermodulation product to fall into the whole *passband*. + +Table 7.7.2-1 specifies the parameters for two interfering signals, where: + +- $f_i$ offset is the offset from the channel edge frequency of the first or last channel in the *passband* of the closer carrier. +- $G_{RX\_ANT}$ is the gain of the receive side antennas and is calculated from EIRP and TRP declaration. + +**Table 7.7.2-1: Input intermodulation requirement** + +| $f_i$ offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|--------------|---------------------------|-----------------|-----------------------| +| 1 MHz | -53dBm – $G_{RX\_ANT}$ | 2 CW carriers | 1 MHz | + +## 7.7.3 Minimum requirement for NCR + +### 7.7.3.1 Minimum requirement for NCR-Fwd + +#### 7.7.3.1.1 Minimum requirement for NCR-Fwd type 2-O + +The requirements in clause 7.7.2 apply for NCR-Fwd type 2-O. + +## 7.8 OTA Adjacent Channel Rejection Ratio (ACRR) + +### 7.8.1 General + +OTA Adjacent Channel Rejection Ratio (ACRR) is the ratio of the average gain over a carrier of the repeater in the *passband* to the average gain of the repeater over an adjacent channel outside the repeater *passband*. The requirement shall apply to the uplink and downlink of the Repeater. The bandwidth of the channel inside the *passband* and the adjacent channel shall be of the same type (reference carrier) with bandwidths as defined by *nominal channel bandwidth*. + +The requirement is differentiated between downlink and uplink. + +The requirement shall apply during the *transmitter ON state*. + +The ACRR is a ratio of gain in the adjacent channel to gain in the wanted channel. The gain in each case is defined as the ratio of TRP output power to directional input power. + +### 7.8.2 Minimum Requirements for NR repeater + +The requirement shall apply at the RIB when the AoA of the incident wave of a received signal in the *passband* and a received signal on an adjacent channel outside repeater *passband* is from the same direction and are the same as the TX reference direction for the opposite DL/UL setting. + +For a repeater operating at *passband* operating in FR2, the ACRR requirements in table 7.8.2-1 shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 7.8.2-1. + +**Table 7.8.2-1: Repeater Downlink ACRR** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit (dB) | +|---------------------------------|-----------------------|-------------------------------------------------------------|-----------------------------------| +| NR | Wide Area repeater | $BW_{Nominal}/2$ | 28 (Note 2)
26 (Note 3) | +| | Medium Range repeater | $BW_{Nominal}/2$ | 28 (Note 2)
26 (Note 3) | +| | Local Area repeater | $BW_{Nominal}/2$ | 28 (Notes 1, 2)
26 (Note 1, 3) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. +NOTE 3: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +For a repeater operating at *passband* operating in FR2, the ACRR requirements in table 7.8.2-2 shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 7.8.2-2. + +**Table 7.8.2-2: Repeater Uplink ACRR** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit (dB) | +|---------------------------------|---------------------|-------------------------------------------------------------|----------------------------------| +| NR | Wide Area repeater | $BW_{Nominal}/2$ | 28 (Note 2)
26 (Note 3) | +| | Local Area repeater | $BW_{Nominal}/2$ | 17 (Note 1, 2)
16 (Note 1, 3) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. +NOTE 3: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +## 7.8.3 Minimum Requirements for NCR + +### 7.8.3.1 Minimum Requirements for NCR-Fwd + +#### 7.8.3.1.1 Minimum Requirements for NCR-Fwd type 2-O + +The requirement shall apply at the RIB when the AoA of the incident wave of a received signal in the *passband* and a received signal on an adjacent channel outside repeater *passband* is from the same direction and are the same as the TX reference direction for the opposite DL/UL setting. + +For *NCR-Fwd type 2-O* operating at *passband* operating in FR2, the ACRR requirements in table 7.8.3.1.1-1 shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 7.8.3.1.1-1. + +**Table 7.8.3.1.1-1: NCR-Fwd type 2-O Downlink ACRR** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit (dB) | +|---------------------------------|-----------------------|-------------------------------------------------------------|-----------------------------------| +| NR | Wide Area repeater | $BW_{Nominal}/2$ | 28 (Note 2)
26 (Note 3) | +| | Medium Range repeater | $BW_{Nominal}/2$ | 28 (Note 2)
26 (Note 3) | +| | Local Area repeater | $BW_{Nominal}/2$ | 28 (Notes 1, 2)
26 (Note 1, 3) | + +NOTE 1: This requirement is not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. +NOTE 3: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +For *NCR-Fwd type 2-O* operating at *passband* operating in FR2, the ACRR requirements in table 7.8.3.1.1-2 shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 7.8.3.1.1-2. + +**Table 7.8.3.1.1-2: NCR-Fwd type 2-O Uplink ACRR** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | ACRR limit (dB) | +|---------------------------------|---------------------|-------------------------------------------------------------|----------------------------------| +| NR | Wide Area repeater | $BW_{Nominal}/2$ | 28 (Note 2)
26 (Note 3) | +| | Local Area repeater | $BW_{Nominal}/2$ | 17 (Note 1, 2)
16 (Note 1, 3) | + +NOTE 1: This requirement is not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. +NOTE 3: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +## 7.9 OTA transmit ON/OFF power + +### 7.9.1 General + +OTA transmit ON/OFF power requirements apply only to TDD operation of repeater. The requirements apply to both downlink and uplink of the repeater. + +### 7.9.2 OTA transmitter OFF power + +#### 7.9.2.1 General + +OTA transmitter OFF power is defined as the mean power measured over $70/N \mu s$ filtered with a square filter of bandwidth equal to the *passband bandwidth* of the repeater ( $BW_{passband}$ ) centred on the assigned channel frequency + +during the *transmitter OFF state*. $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz of the input signal. For *repeater type 2-O* and *NCR-Fwd type 2-O*, the OTA transmitter OFF power is defined as TRP. + +### 7.9.2.2 Minimum requirement for NR repeater + +The OTA transmitter OFF TRP spectral density for *repeater type 2-O* shall be less than -36 dBm/MHz. + +### 7.9.2.3 Minimum requirement for NCR + +#### 7.9.2.3.1 Minimum requirement for NCR-Fwd + +##### 7.9.2.3.1.1 Minimum requirement for NCR-Fwd *type 2-O* + +The requirements in clause 7.9.2.2 apply for NCR-Fwd *type 2-O*. + +#### 7.9.2.3.2 Minimum requirement for NCR-MT + +##### 7.9.2.3.2.1 Minimum requirement for NCR-MT *type 2-O* + +For Wide Area NCR-MT *type 2-O*, the OTA transmitter OFF TRP spectral density for shall be less than -36 dBm/MHz. For Local Area *NCR-MT type 2-O*, the transmit OFF power shall not exceed the values specified in Tables 7.9.2.3.2.1-1 for each operating band supported. The requirement is verified with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +**Table 7.9.2.3.2.1-1: Transmit OFF power for FR2-1** + +| Operating band | Channel bandwidth / Transmit OFF power (dBm) / measurement bandwidth | | | | +|------------------------------------|----------------------------------------------------------------------|-----------|------------|------------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257, n258, n259, n260, n261, n262 | -35 | -35 | -35 | -35 | +| | 47.58 MHz | 95.16 MHz | 190.20 MHz | 380.28 MHz | + +## 7.9.3 OTA transient period + +### 7.9.3.1 General + +The OTA *transmitter transient period* is the time period during which the transmitter is changing from the *transmitter OFF state* to the *transmitter ON state* or vice versa. The *transmitter transient period* is illustrated in figure 7.9.3.1-1. + +![Figure 7.9.3.1-1: Example of relations between transmitter ON state, transmitter OFF state and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two horizontal dashed lines: 'ON power level' and 'OFF power level'. The curve shows a transition from a low power level (OFF state) to a high power level (ON state) and back. The 'Transmitter ON state (DL/UL transmission)' is the period where the power is at the ON level. The 'Transmit transient period' is the time interval between the start and end of the ON state. The 'Transmit OFF state' is the period where the power is at the OFF level. The graph is divided into three main sections: 'UL/DL transmission' (before the ON state), 'Transmitter ON state (DL/UL transmission)' (the high power period), and 'GP or UL/DL transmission' (after the ON state).](6677c55d7b1a3dcd7ca191501eda544b_img.jpg) + +Figure 7.9.3.1-1: Example of relations between transmitter ON state, transmitter OFF state and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two horizontal dashed lines: 'ON power level' and 'OFF power level'. The curve shows a transition from a low power level (OFF state) to a high power level (ON state) and back. The 'Transmitter ON state (DL/UL transmission)' is the period where the power is at the ON level. The 'Transmit transient period' is the time interval between the start and end of the ON state. The 'Transmit OFF state' is the period where the power is at the OFF level. The graph is divided into three main sections: 'UL/DL transmission' (before the ON state), 'Transmitter ON state (DL/UL transmission)' (the high power period), and 'GP or UL/DL transmission' (after the ON state). + +**Figure 7.9.3.1-1: Example of relations between transmitter ON state, transmitter OFF state and transmitter transient period** + +This requirement shall be applied at each RIB supporting transmission in the *operating band*. The beginning and end point of downlink and uplink bursts are referenced to the slot timing at the input. + +### 7.9.3.2 Minimum requirement for NR repeater + +For *repeater type 2-O*, the OTA *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 7.9.3.2-1. + +**Table 7.9.3.2-1: Minimum requirement for the OTA transmitter transient period for repeater type 2-O** + +| Transition | Transient period length (μs) | +|------------|------------------------------| +| OFF to ON | 3 | +| ON to OFF | 3 | + +### 7.9.3.3 Minimum requirement for NCR + +#### 7.9.3.3.1 Minimum requirement for NCR-Fwd + +##### 7.9.3.3.1.1 Minimum requirement for NCR-Fwd type 2-O + +The requirements in clause 7.9.3.2 apply for NCR-Fwd type 2-O. + +#### 7.9.3.3.2 Minimum requirement for NCR-MT + +##### 7.9.3.3.2.1 Minimum requirement for NCR-MT type 2-O + +For Wide Area NCR-MT type 2-O, the OTA *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 7.9.3.3.2.1-1. + +**Table 7.9.3.3.2.1-1: Minimum requirement for the OTA transmitter transient period for Wide Area NCR-MT type 2-O** + +| Transition | Transient period length ( $\mu\text{s}$ ) | +|------------|-------------------------------------------| +| OFF to ON | 3 | +| ON to OFF | 3 | + +For Local Area *NCR-MT type 2-O*, the requirement from TS 38.101-2 section 6.3.3.2 applies. + +## 7.10 OTA output power dynamics + +### 7.10.1 General + +### 7.10.2 Minimum requirement for NCR-MT + +## 7.11 OTA transmit signal quality + +### 7.11.1 General + +Transmit signal quality is specified in terms of: frequency error and transmit modulation quality requirements. + +### 7.11.2 Frequency error requirements for NCR-MT + +#### 7.11.2.1 Minimum requirement for NCR-MT type 2-O + +For NCR-MT type 2-O, the requirements specified in clause 9.6.1.2.3 in TS 38.174 applies. + +### 7.11.3 Transmit modulation quality + +#### 7.11.3.1 Minimum requirement for NCR-MT type 2-O + +For NCR-MT type 2-O, the requirements specified in clause 9.6.2.2.3 in TS 38.174 applies. + +## 7.12 Diversity characteristics + +### 7.12.1 General + +### 7.12.2 Minimum requirement for NCR-MT + +The OTA diversity characteristic is specified the same as conducted diversity characteristic for FR1 NCR type 1-C, 1-H in sub-clause 6.13. + +## 7.13 OTA reference sensitivity + +### 7.13.1 General + +The reference sensitivity power level REFSENS is defined as the EIS level at the centre of the quiet zone in the RX beam peak direction, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. + +### 7.13.2 Minimum requirement for NCR-MT type 2-O + +The wide area NCR-MT reference sensitivity level is specified the same as the Wide Area IAB-MT reference sensitivity level requirement in TS 38.174 [22], subclause 10.3.3.3. + +The local area NCR-MT reference sensitivity level is specified the same as reference sensitivity power level for power class 3 in TS 38.101-2 [14], subclause 7.3.2.3. + +## 7.14 OTA maximum input level + +### 7.14.1 General + +The maximum input level is defined as the maximum mean power, for which the throughput shall meet or exceed the minimum requirements for the specified reference measurement channel. + +### 7.14.2 Minimum requirement for NCR-MT type 2-O + +The local area NCR-MT maximum input power is specified the same as maximum input power in TS 38.101-2 [14], subclause 7.4. + +## 7.15 OTA adjacent channel selectivity + +### 7.15.1 General + +Adjacent Channel Selectivity (ACS) is a measure of a receiver's ability to receive a NR signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent channel(s). + +#### 7.15.1 Minimum requirement for NCR-MT type 2-O + +The wide area NCR-MT ACS requirement is specified the same as the Wide Area IAB-MT ACS requirement in TS 38.174 [22], subclause 10.5.1.4. + +The local area NCR-MT reference sensitivity level is specified the same as ACS requirement in TS 38.101-2 [14], subclause 7.5. + +## 7.16 OTA blocking characteristics + +### 7.16.1 General + +The blocking characteristic is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occurs. + +#### 7.16.2 Minimum requirement for NCR-MT type 2-O + +The wide area NCR-MT blocking requirement is specified the same as the Wide Area IAB-MT blocking requirement in TS 38.174 [22], subclause 10.5.2.4. + +The local area NCR-MT blocking requirement is specified the same as blocking requirement in TS 38.101-2 [14], subclause 7.6. + +## 7.17 OTA spurious emissions + +### 7.17.1 General + +The spurious emissions power is the power of emissions generated or amplified in a receiver. The spurious emissions power level is measured as TRP. + +## 7.17.2 Minimum requirement for NCR-MT type 2-O + +The wide area NCR-MT receiver spurious emission requirement is specified the same as the Wide Area IAB-MT receiver spurious emission requirement in TS 38.174 [22], subclause 10.7.3.2. + +The local area NCR-MT receiver spurious emission requirement is specified the same as receiver spurious emission requirement in TS 38.101-2 [14], subclause 7.9. + +--- + +## 8 (Reserved) + +--- + +## 9 (Reserved) + +--- + +## 10 NCR-MT RRC\_CONNECTED state mobility + +### 10.1 RRC Connection Mobility Control for NCR-MT + +#### 10.1.1 SA: RRC Re-establishment + +##### 10.1.1.1 Introduction + +This clause contains requirements on the NCR-MT regarding RRC connection re-establishment procedure. The requirements in this clause are applicable only for local area (LA) NCR-MT. + +RRC connection re-establishment is initiated when an NCR-MT in RRC\_CONNECTED state loses RRC connection due to any of failure cases, including radio link failure, handover failure, and RRC connection reconfiguration failure. The RRC connection re-establishment procedure is specified in clause 5.3.7 of TS 38.331 [23]. + +The requirements in this clause are applicable for RRC connection re-establishment to NR cell. + +##### 10.1.1.2 Requirements + +In RRC\_CONNECTED state the NCR-MT shall be capable of sending *RRCREestablishmentRequest* message within $T_{\text{re-establish\_delay}}$ seconds from the moment it detects a loss in RRC connection. The total RRC connection delay ( $T_{\text{re-establish\_delay}}$ ) shall be less than: + +$T_{\text{UL\_grant}}$ : It is the time required to acquire and process uplink grant from the target PCell. The uplink grant is required to transmit *RRCREestablishmentRequest* message. + +The NCR-MT re-establishment delay ( $T_{\text{NCR-MT\_re-establish\_delay}}$ ) is specified in clause 10.1.1.2.1. + +#### 10.1.1.2.1 NCR-MT Re-establishment delay requirement + +The NCR-MT re-establishment delay ( $T_{\text{NCR-MT\_re-establish\_delay}}$ ) is the time between the moments when any of the conditions requiring RRC re-establishment as defined in clause 5.3.7 in TS 38.331 [23] is detected by the NCR-MT and when the NCR-MT sends PRACH to the target PCell. The NCR-MT re-establishment delay ( $T_{\text{NCR-MT\_re-establish\_delay}}$ ) requirement shall be less than: + +The intra-frequency target NR cell shall be considered detectable if each relevant SSB can satisfy that: + +- the conditions of SSB\_RP and SSB Ês/Iot according to Annex TBD for the LA NCR-MT class and NCR type are fulfilled. + +The inter-frequency target NR cell shall be considered detectable when for each relevant SSB: + +- the conditions of SSB\_RP and SSB Ês/Iot according to Annex TBD for the LA NCR-MT class and NCR type are fulfilled. + +$T_{\text{identify\_intra\_NR}}$ : It is the time to identify the target intra-frequency NR cell and it depends on whether the target NR cell is known cell or unknown cell and on the frequency range (FR) of the target NR cell. If the NCR-MT is not configured with intra-frequency NR carrier for RRC re-establishment then $T_{\text{identify\_intra\_NR}}=0$ ; otherwise $T_{\text{identify\_intra\_NR}}$ shall not exceed the values defined in Table 10.1.1.2.1-1. + +$T_{\text{identify\_inter\_NR},i}$ : It is the time to identify the target inter-frequency NR cell on inter-frequency carrier $i$ configured for RRC re-establishment and it depends on whether the target NR cell is known cell or unknown cell and on the frequency range (FR) of the target NR cell. $T_{\text{identify\_inter\_NR},i}$ shall not exceed the values defined in Table 10.1.1.2.1-2. + +$T_{\text{SMTC}}$ : It is the periodicity of the SMTC occasion configured for the intra-frequency carrier. If the NCR-MT has been provided with higher layer signaling of *smtc2* [23] then $T_{\text{SMTC}}$ follows *smtc1* or *smtc2* according to the physical cell ID of the target cell. + +$T_{\text{SMTC},i}$ : It is the periodicity of the SMTC occasion configured for the inter-frequency carrier $i$ . If the NCR-MT is not provided with SMTC configuration then the NCR-MT may assume that the target SSB periodicity is no larger than 20 ms. + +$T_{\text{SI-NR}}$ : It is the time required for receiving all the relevant system information according to the reception procedure and the RRC procedure delay of system information blocks defined in TS 38.331 [23] for the target NR cell. + +$T_{\text{PRACH}}$ : It is the delay uncertainty in acquiring the first available PRACH occasion in the target NR cell. $T_{\text{PRACH}}$ can be up to the summation of SSB to PRACH occasion association period and 10 ms. SSB to PRACH occasion associated period is defined in clause 14 of TS 38.213 [24]. + +$N_{\text{freq}}$ : It is the total number of NR frequencies to be monitored for RRC re-establishment; $N_{\text{freq}} = 1$ if the target intra-frequency NR cell is known, else $N_{\text{freq}} = 2$ and $T_{\text{identify\_intra\_NR}} = 0$ if the target inter-frequency NR cell is known. + +There is no requirement if the target cell does not contain the NCR-MT context or if the SSB transmission periodicity is larger than 20 ms. + +In the requirement defined in the below tables, the target FR1 cell is known if it has been meeting the relevant cell identification requirement during the last 5 seconds otherwise it is unknown. + +**Table 10.1.1.2.1-1: Time to identify target NR cell for RRC connection re-establishment to NR intra-frequency cell** + +| Serving cell
SSB Ês/lot (dB) | Frequency range (FR)
of target NR cell | $T_{\text{identify\_intra\_NR}}$ [ms] | | +|---------------------------------|-------------------------------------------|---------------------------------------------|----------------------------------------------| +| | | Known NR cell | Unknown NR cell | +| $\geq -8$ | FR1 | MAX (1600 ms, $40 \times T_{\text{SMTc}}$ ) | MAX (6400 ms, $80 \times T_{\text{SMTc}}$ ) | +| $\geq -8$ | FR2-1 | N/A | MAX (8000 ms, $640 \times T_{\text{SMTc}}$ ) | +| $< -8$ | FR1 | N/A | 6400 Note1 | +| $< -8$ | FR2-1 | N/A | 28160 Note1 | + +Note 1: The NCR-MT is not required to successfully identify a cell on any NR frequency layer when $T_{\text{SMTc}} > 20$ ms and serving cell SSB Ês/lot $< -8$ dB. + +**Table 10.1.1.2.1-2: Time to identify target NR cell for RRC connection re-establishment to NR inter-frequency cell** + +| Serving cell SSB
Ês/lot (dB) | Frequency range (FR)
of target NR cell | $T_{\text{identify\_inter\_NR}, i}$ [ms] | | +|---------------------------------|-------------------------------------------|------------------------------------------------|-------------------------------------------------| +| | | Known NR cell | Unknown NR cell | +| $\geq -8$ | FR1 | MAX (1600 ms, $48 \times T_{\text{SMTc}, i}$ ) | MAX (6400 ms, $104 \times T_{\text{SMTc}, i}$ ) | +| $\geq -8$ | FR2-1 | N/A | MAX (8000 ms, $832 \times T_{\text{SMTc}, i}$ ) | +| $< -8$ | FR1 | N/A | 6400 Note1 | +| $< -8$ | FR2-1 | N/A | 32000 Note1 | + +Note 1: The NCR-MT is not required to successfully identify a cell on any NR frequency layer when $T_{\text{SMTc}, i} > 20$ ms and serving cell SSB Ês/lot $< -8$ dB. + +## 10.1.2 Random access + +### 10.1.2.1 Introduction + +This clause contains requirements on the NCR-MT regarding random access procedure. The random access procedure is initiated to establish uplink time synchronization for a NCR-MT which either has not acquired or has lost its uplink synchronization, or to convey NCR-MT's request Other SI, or for beam failure recovery. The random access is specified in clause 8 of TS 38.213 [24] and the control of the RACH transmission is specified in clause 5.1 of TS 38.321 [25]. + +The requirements in this clause apply for LA NCR-MT. + +### 10.1.2.2 Requirements for 4-step RA type + +The NCR-MT shall have capability to calculate PRACH transmission power according to the PRACH power formula defined in clause 7.4 of TS 38.213 [24] and apply this power level at the first preamble or additional preambles. The absolute power applied to the first preamble shall have an accuracy as specified in Table TBA for FR1 and in Table TBA for FR2-1. The relative power applied to additional preambles shall have an accuracy as specified in Table TBA for FR1 and clause TBA for FR2-1. + +The NCR-MT shall indicate a random access problem to upper layers if the maximum number of preamble transmission counter has been reached for the random access procedure on PCell as specified in clause 5.1.4 in TS 38.321 [25]. + +The requirements in this clause apply for NCR-MT in SA operation mode. + +#### 10.1.2.2.1 Contention based random access + +##### 10.1.2.2.1.1 Correct behaviour when transmitting Random Access Preamble + +With the NCR-MT selected SSB with SS-RSRP above *rsrp-ThresholdSSB*, NCR-MT shall have the capability to select a Random Access Preamble randomly with equal probability from the Random Access Preambles associated with the selected SSB if the association between Random Access Preambles and SSB is configured, as specified in clause 5.1.2 in TS 38.321 [25]. + +With the NCR-MT selected SSB with SS-RSRP above *rsrp-ThresholdSSB*, NCR-MT shall have the capability to transmit Random Access Preamble on the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured, if the association between PRACH occasions and SSBs is configured, and PRACH occasion shall be randomly selected with equal probability amongst the selected SSB associated PRACH occasions occurring simultaneously but on different subcarriers, as specified in clause 5.1.2 in TS 38.321 [25]. + +##### 10.1.2.2.1.2 Correct behaviour when receiving Random Access Response + +The NCR-MT may stop monitoring for Random Access Response(s) and shall transmit the msg3 if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble. + +The NCR-MT shall again perform the Random Access Resource selection procedure defined in clause 5.1.2 in TS 38.321 [25], and transmit with the calculated PRACH transmission power when the backoff time expires if all received Random Access Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble. + +##### 10.1.2.2.1.3 Correct behaviour when not receiving Random Access Response + +The NCR-MT shall again perform the Random Access Resource selection procedure defined in clause 5.1.2 in TS 38.321 [25], and transmit with the calculated PRACH transmission power when the backoff time expires if no Random Access Response is received within the RA Response window defined in clause 5.1.4 in TS 38.321 [25]. + +##### 10.1.2.2.1.4 Correct behaviour when receiving an UL grant for msg3 retransmission + +The NCR-MT shall re-transmit the msg3 upon the reception of an UL grant for msg3 retransmission. + +##### 10.1.2.2.1.5 SA: Correct behaviour when receiving a message over Temporary C-RNTI + +The NCR-MT shall send ACK if the Contention Resolution is successful. + +The NCR-MT shall again perform the Random Access Resource selection procedure defined in clause 5.1.2 in TS 38.321 [25], and transmit with the calculated PRACH transmission power when the backoff time expires unless the received message includes a NCR-MT Contention Resolution Identity MAC control element and the NCR-MT Contention Resolution Identity included in the MAC control element matches the CCCH SDU transmitted in the uplink message. + +#### 10.1.2.2.1.6 Correct behaviour when contention Resolution timer expires + +The NCR-MT shall re-select a preamble and transmit with the calculated PRACH transmission power when the backoff time expires if the Contention Resolution Timer expires. + +#### 10.1.2.2.2 Non-Contention based random access + +##### 10.1.2.2.2.1 Correct behaviour when transmitting Random Access Preamble + +If the contention-free Random Access Resources and the contention-free PRACH occasions associated with SSBs is configured, with the NCR-MT selected SSB with SS-RSRP above *rsrp-ThresholdSSB* amongst the associated SSBs, NCR-MT shall have the capability to select the Random Access Preamble corresponding to the selected SSB, and to transmit Random Access Preamble on the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured, and PRACH occasion shall be randomly selected with equal probability amongst the selected SSB associated PRACH occasions occurring simultaneously but on different subcarriers, as specified in clause 5.1.2 in TS 38.321 [25]. + +If the contention-free Random Access Resources and the contention-free PRACH occasions associated with CSI-RSs is configured, with the NCR-MT selected CSI-RS with CSI-RSRP above *rsrp-ThresholdCSI-RS* amongst the associated CSI-RSs, NCR-MT shall have the capability to select the Random Access Preamble corresponding to the selected CSI-RS, and to transmit Random Access Preamble on the next available PRACH occasion from the PRACH occasions in *ra-OccasionList* corresponding to the selected CSI-RS, and PRACH occasion shall be randomly selected with equal probability amongst the selected CSI-RS associated PRACH occasions occurring simultaneously but on different subcarriers, as specified in clause 5.1.2 in TS 38.321 [25]. + +If the random access procedure is initialized for beam failure recovery and if the contention-free Random Access Resources and the contention-free PRACH occasions for beam failure recovery request associated with any of the SSBs and/or CSI-RSs is configured, NCR-MT shall have the capability to select the Random Access Preamble corresponding to the selected SSB with SS-RSRP above *rsrp-ThresholdSSB* amongst the associated SSBs or the selected CSI-RS with CSI-RSRP above *rsrp-ThresholdCSI-RS* amongst the associated CSI-RSs, and to transmit Random Access Preamble on the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured, or from the PRACH occasions in *ra-OccasionList* corresponding to the selected CSI-RS, and PRACH occasion shall be randomly selected with equal probability amongst the selected SSB associated PRACH occasions or the selected CSI-RS associated PRACH occasions occurring simultaneously but on different subcarriers, as specified in clause 5.1.2 in TS 38.321 [25]. + +##### 10.1.2.2.2.2 Correct behaviour when receiving Random Access Response + +The NCR-MT may stop monitoring for Random Access Response(s), if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble, unless the random access procedure is initialized for Other SI request from NCR-MT. + +The NCR-MT may stop monitoring for Random Access Response(s) and shall monitor the Other SI transmission if the Random Access Response only contains a Random Access Preamble identifier which is corresponding to the transmitted Random Access Preamble and the random access procedure is initialized for SI request from NCR-MT, as specified in clause 5.1.4 in TS 38.321 [25]. + +The NCR-MT may stop monitoring for Random Access Response(s), if the contention-free Random Access Preamble for beam failure recovery request was transmitted and if the PDCCH addressed to NCR-MT's C-RNTI is received, as specified in clause 5.1.4 in TS 38.321 [25]. + +The NCR-MT shall again perform the Random Access Resource selection procedure defined in clause 5.1.2 in TS 38.321 [25] for the next available PRACH occasion, and transmit the preamble with the calculated PRACH transmission power if all received Random Access Responses contain Random Access Preamble identifiers that do not match the transmitted Random Access Preamble. + +#### 10.1.2.2.2.3 Correct behaviour when not receiving Random Access Response + +The NCR-MT shall again perform the Random Access Resource selection procedure defined in clause 5.1.2 in TS 38.321 [25] for the next available PRACH occasion, and transmit the preamble with the calculated PRACH transmission power, if no Random Access Response is received within the RA Response window configured in *RACH-ConfigCommon* or if no PDCCH addressed to NCR-MT's C-RNTI is received within the RA Response window configured in *BeamFailureRecoveryConfig*, as defined in clause 5.1.4 in TS 38.321 [25]. + +## 10.2 Timing + +### 10.2.1 NCR-MT transmit timing + +#### 10.2.1.1 Introduction + +The NCR-MT shall have capability to follow the frame timing change of the reference cell in connected state. The uplink frame transmission takes place before the reception of the first detected path (in time) of the corresponding downlink frame from the reference cell. NCR-MT belonging to local area NCR-MT class as defined in clause 4.3A.2 shall use the SpCell as the reference cell for deriving the NCR-MT transmit timing. NCR-MT initial transmit timing accuracy, gradual timing adjustment requirements are defined in the following requirements. + +#### 10.2.1.2 Requirements + +The NCR-MT initial transmission timing error shall be less than or equal to $\pm T_c$ where the timing error limit value $T_c$ is specified in Table 10.2.1.2-1. This requirement applies for PUCCH, PUSCH and SRS or it is the PRACH transmission. + +The NCR-MT shall meet the $T_c$ requirement for an initial transmission provided that at least one SSB is available at the NCR-MT during the last 160 ms. The reference point for the NCR-MT initial transmit timing control requirement shall + +be the downlink timing of the reference cell minus $(N_{TA} + N_{TA\ offset}) \times T_c$ . The downlink timing is defined as the time when the first path (in time) of the corresponding downlink frame used by the NCR-MT to determine downlink timing is received from the reference cell at the NCR-MT antenna. $N_{TA}$ for PRACH is defined as 0. + +$(N_{TA} + N_{TA\ offset}) \times T_c$ (in $T_c$ units) for other channels is the difference between NCR-MT transmission timing and the downlink timing immediately after when the last timing advance in clause 10.2.2 was applied. $N_{TA}$ for other channels is + +not changed until next timing advance is received. The value of $N_{\text{TA offset}}$ depends on the duplex mode of the cell in which the uplink transmission takes place and the frequency range (FR). $N_{\text{TA offset}}$ is defined in Table 10.2.1.2-2. + +**Table 10.2.1.2-1: $T_e$ Timing Error Limit** + +| Frequency Range | SCS of SSB signals ( kHz) | SCS of uplink signals ( kHz) | $T_e$ | +|------------------------------------------------------------------|---------------------------|------------------------------|--------------------------| +| 1 | 15 | 15 | $12 \cdot 64 \cdot T_c$ | +| | | 30 | $10 \cdot 64 \cdot T_c$ | +| | | 60 | $10 \cdot 64 \cdot T_c$ | +| | 30 | 15 | $8 \cdot 64 \cdot T_c$ | +| | | 30 | $8 \cdot 64 \cdot T_c$ | +| | | 60 | $7 \cdot 64 \cdot T_c$ | +| 2-1 | 120 | 60 | $3.5 \cdot 64 \cdot T_c$ | +| | | 120 | $3.5 \cdot 64 \cdot T_c$ | +| | 240 | 60 | $3 \cdot 64 \cdot T_c$ | +| | | 120 | $3 \cdot 64 \cdot T_c$ | +| Note 1: $T_c$ is the basic timing unit defined in TS 38.211 [26] | | | | + +**Table 10.2.1.2-2: The Value of $N_{\text{TA offset}}$** + +| Frequency range and band of cell used for uplink transmission | $N_{\text{TA offset}}$ (Unit: $T_c$ ) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| FR1 TDD band without LTE-NR coexistence case | 25600 (Note 1) | +| FR1 TDD band with LTE-NR coexistence case | 39936 (Note 1) | +| FR2-1 | 13792 | +| Note 1: The NCR-MT identifies $N_{\text{TA offset}}$ based on the information n-TimingAdvanceOffset as specified in TS 38.331 [23]. If NCR-MT is not provided with the information n-TimingAdvanceOffset, the default value of $N_{\text{TA offset}}$ is set as 25600 for FR1 band. | | + +When it is the transmission for PUCCH, PUSCH and SRS transmission, the NCR-MT shall be capable of changing the transmission timing according to the received downlink frame of the reference cell except when the timing advance in clause 10.2.3 is applied. + +#### 10.2.1.2.1 Gradual timing adjustment + +The requirements in this clause apply for NCR-MT belonging to local area NCR-MT class as defined in clause 4.3A.2. + +When the transmission timing error between the NCR-MT and the reference timing exceeds $\pm T_c$ then the NCR-MT is required to adjust its timing to within $\pm T_c$ . The reference timing shall be $(N_{TA} + N_{TA\ offset}) \times T_c$ before the downlink timing of the reference cell. All adjustments made to the NCR-MT uplink timing shall follow these rules: + +- 1) The maximum amount of the magnitude of the timing change in one adjustment shall be $T_q$ . +- 2) The minimum aggregate adjustment rate shall be $T_p$ per second. +- 3) The maximum aggregate adjustment rate shall be $T_q$ per 200 ms. + +where the maximum autonomous time adjustment step $T_q$ and the aggregate adjustment rate $T_p$ are specified in Table 10.2.1.2.1-1. + +**Table 10.2.1.2.1-1: $T_q$ Maximum Autonomous Time Adjustment Step and $T_p$ Minimum Aggregate Adjustment rate** + +| Frequency Range | SCS of uplink signals (kHz) | $T_q$ | $T_p$ | +|-----------------|-----------------------------|----------------------------|----------------------------| +| 1 | 15 | $5.5 \times 64 \times T_c$ | $5.5 \times 64 \times T_c$ | +| | 30 | $5.5 \times 64 \times T_c$ | $5.5 \times 64 \times T_c$ | +| | 60 | $5.5 \times 64 \times T_c$ | $5.5 \times 64 \times T_c$ | +| 2-1 | 60 | $2.5 \times 64 \times T_c$ | $2.5 \times 64 \times T_c$ | +| | 120 | $2.5 \times 64 \times T_c$ | $2.5 \times 64 \times T_c$ | + +NOTE: $T_c$ is the basic timing unit defined in TS 38.211 [26]. + +## 10.2.2 NCR-MT timer accuracy + +### 10.2.2.1 Introduction + +NCR-MT timers are used in different protocol entities to control the NCR-MT behaviour. + +The requirements in clause 10.2.2 apply for NCR-MT belonging to local area NCR-MT class as defined in clause 4.3A.2. + +### 10.2.2.2 Requirements + +For NCR-MT timers specified in TS 38.331 [23], the NCR-MT shall comply with the timer accuracies according to Table 10.2.2.2-1. + +The requirements are only related to the actual timing measurements internally in the NCR-MT. They do not include the following: + +- Inaccuracy in the start and stop conditions of a timer (e.g. NCR-MT reaction time to detect that start and stop conditions of a timer is fulfilled), or +- Inaccuracies due to restrictions in observability of start and stop conditions of an NCR-MT timer (e.g. slot alignment when NCR-MT sends messages at timer expiry). + +**Table 10.2.2.2-1** + +| Timer value [s] | Accuracy | +|----------------------|-------------------| +| timer value < 4 | $\pm 0.1\text{s}$ | +| timer value $\geq 4$ | $\pm 2.5\%$ | + +## 10.2.3 NCR-MT timing advance + +### 10.2.3.1 Introduction + +The timing advance is initiated from gNB to NCR-MT, with MAC message that implies the adjustment of the timing advance, as defined in clause 5.2 of TS 38.321 [25]. + +### 10.2.3.2 Requirements + +#### 10.2.3.2.1 Timing Advance adjustment delay + +NCR-MT shall adjust the timing of its uplink transmission timing at time slot $n + k + l$ for a timing advance command received in time slot $n$ , and the value of $k$ is defined in clause 4.2 in TS 38.213 [24]. The same requirement applies also when NCR-MT is not able to transmit a configured uplink transmission due to the channel assessment procedure. + +#### 10.2.3.2.2 Timing Advance adjustment accuracy + +The NCR-MT shall adjust the timing of its transmissions with a relative accuracy better than or equal to the NCR-MT Timing Advance adjustment accuracy requirement in Table 10.2.3.2.2-1, to the signalled timing advance value compared to the timing of preceding uplink transmission. The timing advance command step is defined in TS 38.213 [24]. + +**Table 10.2.3.2.2-1: NCR-MT Timing Advance adjustment accuracy** + +| UL Sub Carrier Spacing(kHz) | 15 | 30 | 60 | 120 | +|-----------------------------------------------------------------|---------------|---------------|---------------|--------------| +| UE Timing Advance adjustment accuracy | $\pm 256 T_c$ | $\pm 256 T_c$ | $\pm 128 T_c$ | $\pm 32 T_c$ | +| NOTE: $T_c$ is the basic timing unit defined in TS 38.211 [26]. | | | | | + +## 10.3 Signalling Characteristics for NCR-MT + +### 10.3.1 Radio Link Monitoring + +#### 10.3.1.1 Introduction + +The requirements in clause 8.1 apply for radio link monitoring on: + +- PCell in SA NR, + +The NCR-MT shall monitor the downlink radio link quality based on the reference signal configured as RLM-RS resource(s) in order to detect the downlink radio link quality of the PCell as specified in TS 38.213 [24]. The configured RLM-RS resources can be all SSBs, or all CSI-RSs, or a mix of SSBs and CSI-RSs. NCR-MT is not required to perform RLM outside the active DL BWP. + +On each RLM-RS resource, the NCR-MT shall estimate the downlink radio link quality and compare it to the thresholds $Q_{out}$ and $Q_{in}$ for the purpose of monitoring downlink radio link quality of the cell. + +The threshold $Q_{out}$ is defined as the level at which the downlink radio link cannot be reliably received and shall correspond to the out-of-sync block error rate ( $BLER_{out}$ ) as defined in Table 10.3.1-1. For SSB based radio link monitoring, $Q_{out\_SSB}$ is derived based on the hypothetical PDCCH transmission parameters listed in Table 10.3.1.2.1-1. For CSI-RS based radio link monitoring, $Q_{out\_CSI-RS}$ is derived based on the hypothetical PDCCH transmission parameters listed in Table 10.3.1.3.1-1. + +The threshold $Q_{in}$ is defined as the level at which the downlink radio link quality can be received with significantly higher reliability than at $Q_{out}$ and shall correspond to the in-sync block error rate ( $BLER_{in}$ ) as defined in Table 10.3.1-1. For SSB based radio link monitoring, $Q_{in\_SSB}$ is derived based on the hypothetical PDCCH transmission parameters listed in Table 10.3.1.2.1-2. For CSI-RS based radio link monitoring, $Q_{in\_CSI-RS}$ is derived based on the hypothetical PDCCH transmission parameters listed in Table 10.3.1.3.1-2. + +The out-of-sync block error rate ( $BLER_{out}$ ) and in-sync block error rate ( $BLER_{in}$ ) are determined from the network configuration via parameter *rlmInSyncOutOfSyncThreshold* signalled by higher layers. When NCR-MT is not configured with *rlmInSyncOutOfSyncThreshold* from the network, NCR-MT determines out-of-sync and in-sync block error rates from Configuration #0 in Table 10.3.1-1 by default. All requirements in clause 10.3.1 are applicable for BLER Configuration #0 in Table 10.3.1-1. + +**Table 10.3.1-1: Out-of-sync and in-sync block error rates** + +| Configuration | $BLER_{out}$ | $BLER_{in}$ | +|---------------|--------------|-------------| +| 0 | 10% | 2% | + +NCR-MT shall be able to monitor up to $N_{RLM}$ RLM-RS resources of the same or different types in each corresponding carrier frequency range, depending on a maximum number of SSBs per half frame according to TS 38.213 [24], where $N_{RLM}$ is specified in Table 10.3.1-2 according to TS 38.213 [24], and meet the requirements as specified in clause 10.3.1. NCR-MT is not required to meet the requirements in clause 10.3.1 if RLM-RS is not configured and no TCI state for PDCCH is activated. + +**Table 10.3.1-2: Maximum number of RLM-RS resources $N_{RLM}$** + +| Carrier frequency range of PCell | | Maximum number of RLM-RS resources, $N_{RLM}$ | +|-----------------------------------|----|-----------------------------------------------| +| FR1, $\leq 3$ GHz Note | 4 | 2 | +| FR1, $> 3$ GHz Note | 8 | 4 | +| FR2-1 | 64 | 8 | + +### 10.3.1.2 Requirements for SSB based radio link monitoring + +#### 10.3.1.2.1 Introduction + +The requirements in this clause apply for each SSB based RLM-RS resource configured for PCell, provided that the SSB configured for RLM is actually transmitted within NCR-MT active DL BWP during the entire evaluation period specified in clause 10.3.1.2.2. + +**Table 10.3.1.2.1-1: PDCCH transmission parameters for out-of-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 4dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 4dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +**Table 10.3.1.2.1-2: PDCCH transmission parameters for in-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|------------------------------------------------------------------|---------------------------------| +| DCI payload size | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 4 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 0dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 10.3.1.2.2 Minimum requirement + +NCR-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_out\_SSB}}$ [ms] period becomes worse than the threshold $Q_{\text{out\_SSB}}$ within $T_{\text{Evaluate\_out\_SSB}}$ [ms] evaluation period. + +NCR-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_in\_SSB}}$ [ms] period becomes better than the threshold $Q_{\text{in\_SSB}}$ within $T_{\text{Evaluate\_in\_SSB}}$ [ms] evaluation period. + +$T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ are defined in Table 10.3.1.2.2-1 for FR1 with scaling factor $K_1 = 5$ . + +$T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ are defined in Table 10.3.1.2.2-2 for FR2-1 with scaling factor $N=8$ and $K_2 = 3$ . + +For FR1, + +- $P = 1$ + +For FR2-1, + +- $P=1$ , when the RLM-RS resource is not overlapped with SMTC occasion. +- $P=2$ , when the RLM-RS resource is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when RLM-RS resource is fully overlapped with SMTC period ( $T_{\text{SSB}} = T_{\text{SMTCperiod}}$ ). + +If the high layer in TS 38.331 [23] signaling of smtc2 is present, $T_{\text{SMTCperiod}}$ follows smtc2; Otherwise $T_{\text{SMTCperiod}}$ follow smtc1. + +Longer evaluation period would be expected if the combination of RLM-RS resource and SMTC occasion configurations does not meet previous conditions. + +**Table 10.3.1.2.2-1: Evaluation period $T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_out\_SSB}}$ (ms) | $T_{\text{Evaluate\_in\_SSB}}$ (ms) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_1, \text{Ceil}(10 \times P \times K_1) \times T_{\text{SSB}})$ | $\text{Max}(100 \times K_1, \text{Ceil}(5 \times P \times K_1) \times T_{\text{SSB}})$ | +| NOTE: $T_{\text{SSB}}$ is the periodicity of the SSB configured for RLM. | | | + +**Table 10.3.1.2.2-2: Evaluation period $T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_out\_SSB}}$ (ms) | $T_{\text{Evaluate\_in\_SSB}}$ (ms) | +|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_2, \text{Ceil}(10 \times P \times N \times K_2) \times T_{\text{SSB}})$ | $\text{Max}(100 \times K_2, \text{Ceil}(5 \times P \times N \times K_2) \times T_{\text{SSB}})$ | +| NOTE: $T_{\text{SSB}}$ is the periodicity of the SSB configured for RLM. | | | + +### 10.3.1.2.3 Measurement restrictions for SSB based RLM + +The NCR-MT is required to be capable of measuring SSB for RLM without measurement gaps. The NCR-MT is required to perform the SSB measurements with measurement restrictions as described in the following scenarios. + +For FR1, when the SSB for RLM is in the same OFDM symbol as CSI-RS for RLM, BFD, CBD or L1-RSRP measurement, + +- If SSB and CSI-RS have same SCS, NCR-MT shall be able to measure the SSB for RLM without any restriction; +- If SSB and CSI-RS have different SCS, + - If NCR-MT supports *simultaneousRxDatassb-DiffNumerology*, NCR-MT shall be able to measure the SSB for RLM without any restriction; + - If NCR-MT does not support *simultaneousRxDatassb-DiffNumerology*, NCR-MT is required to measure one of but not both SSB for RLM and CSI-RS. Longer measurement period for SSB based RLM is expected, and no requirements are defined. + +For FR2-1, when the SSB for RLM measurement on one CC is in the same OFDM symbol as CSI-RS for RLM, BFD, CBD or L1-RSRP measurement on the same CC or different CCs in the same band, NCR-MT is required to measure one of but not both SSB for RLM and CSI-RS. Longer measurement period for SSB based RLM is expected, and no requirements are defined. + +### 10.3.1.3 Requirements for CSI-RS based radio link monitoring + +#### 10.3.1.3.1 Introduction + +The requirements in this clause apply for each CSI-RS based RLM-RS resource configured for PCell, provided that the CSI-RS configured for RLM is actually transmitted within NCR-MT active DL BWP during the entire evaluation + +period specified in clause 10.3.1.3.2. NCR-MT is not expected to perform radio link monitoring measurements on the CSI-RS configured as RLM-RS if the CSI-RS is not in the active TCI state of any CORESET configured in the NCR-MT active BWP. + +**Table 10.3.1.3.1-1: PDCCH transmission parameters for out-of-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|---------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 4dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 4dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +**Table 10.3.1.3.1-2: PDCCH transmission parameters for in-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|---------------------------------------------------------------------|---------------------------------| +| DCI payload size | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 4 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 0dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 10.3.1.3.2 Minimum requirement + +NCR-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_out\_CSI-RS}}$ [ms] period becomes worse than the threshold $Q_{\text{out\_CSI-RS}}$ within $T_{\text{Evaluate\_out\_CSI-RS}}$ [ms] evaluation period. + +NCR-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_in\_CSI-RS}}$ [ms] period becomes better than the threshold $Q_{\text{in\_CSI-RS}}$ within $T_{\text{Evaluate\_in\_CSI-RS}}$ [ms] evaluation period. + +- $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ are defined in Table 10.3.1.3.2-1 for FR1 with scaling factor $K_1 = 5$ . +- $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ are defined in Table 10.3.1.3.2-2 for FR2-1 with scaling factor $K_2 = 3$ . + +The requirements of $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ apply provided that the CSI-RS for RLM is not in a resource set configured with repetition ON. The requirements do not apply when the CSI-RS resource in the active TCI state of CORESET is the same CSI-RS resource for RLM and the TCI state information of the CSI-RS resource is not given, wherein the TCI state information means QCL Type-D to SSB for L1-RSRP or CSI-RS with repetition ON. + +For FR1, + +- $P=1$ . + +For FR2-1, + +- $P=1$ , when the RLM-RS resource is not overlapped with SMTC occasion. +- $P=2$ , when the RLM-RS resource is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when the RLM-RS resource is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). + +If the high layer in TS 38.331 [23] signaling of smtc2 is present, $T_{\text{SMTCperiod}}$ follows smtc2; Otherwise $T_{\text{SMTCperiod}}$ follow smtc1. + +NOTE: The overlap between CSI-RS for RLM and SMTC means that CSI-RS based RLM is within the SMTC window duration. + +Longer evaluation period would be expected if the combination of RLM-RS resource and SMTC occasion configurations does not meet previous conditions. + +The values of $M_{\text{out}}$ and $M_{\text{in}}$ used in Table 10.3.1.3.2-1 and Table 10.3.1.3.2-2 are defined as: + +- $M_{\text{out}} = 20$ and $M_{\text{in}} = 10$ , if the CSI-RS resource configured for RLM is transmitted with higher layer CSI-RS parameter *density* [8, clause 7.4.1] set to 3 and over the bandwidth $\geq 24$ PRBs. + +**Table 10.3.1.3.2-1: Evaluation period $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_out\_CSI-RS}}$ (ms) | $T_{\text{Evaluate\_in\_CSI-RS}}$ (ms) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_1, \text{Ceil}(M_{\text{out}} \times P \times K_1) \times T_{\text{CSI-RS}})$ | $\text{Max}(100 \times K_1, \text{Ceil}(M_{\text{in}} \times P \times K_1) \times T_{\text{CSI-RS}})$ | +| NOTE: $T_{\text{CSI-RS}}$ is the periodicity of the CSI-RS resource configured for RLM. The requirements in this table apply for $T_{\text{CSI-RS}}$ equal to 5 ms, 10ms, 20 ms or 40 ms. | | | + +**Table 10.3.1.3.2-2: Evaluation period $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_out\_CSI-RS}}$ (ms) | $T_{\text{Evaluate\_in\_CSI-RS}}$ (ms) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_2, \text{Ceil}(M_{\text{out}} \times P \times K_2) \times T_{\text{CSI-RS}})$ | $\text{Max}(100 \times K_2, \text{Ceil}(M_{\text{in}} \times P \times K_2) \times T_{\text{CSI-RS}})$ | +| NOTE: $T_{\text{CSI-RS}}$ is the periodicity of the CSI-RS resource configured for RLM. The requirements in this table apply for $T_{\text{CSI-RS}}$ equal to 5 ms, 10 ms, 20 ms or 40 ms. | | | + +### 10.3.1.3.3 Measurement restrictions for CSI-RS based RLM + +The NCR-MT is required to be capable of measuring CSI-RS for RLM without measurement gaps. The NCR-MT is required to perform the CSI-RS measurements with measurement restrictions as described in the following clauses. + +For both FR1 and FR2-1, when the CSI-RS for RLM is in the same OFDM symbol as SSB for RLM, BFD, CBD or L1-RSRP measurement, NCR-MT is not required to receive CSI-RS for RLM in the PRBs that overlap with an SSB. + +For FR1, when the SSB for RLM, BFD, CBD, or L1-RSRP measurement is within the active BWP and has same SCS than CSI-RS for RLM, the NCR-MT shall be able to perform CSI-RS measurement without restrictions. + +For FR1, when the SSB for RLM, BFD, CBD or L1-RSRP measurement is within the active BWP and has different SCS than CSI-RS for RLM, the NCR-MT shall be able to perform CSI-RS measurement with restrictions according to its capabilities: + +- If the NCR-MT supports *simultaneousRxDataSSB-DiffNumerology* the NCR-MT shall be able to perform CSI-RS for RLM measurement without restrictions. +- If the NCR-MT does not support *simultaneousRxDataSSB-DiffNumerology*, NCR-MT is required to measure one of but not both CSI-RS for RLM and SSB. Longer measurement period for CSI-RS based RLM is expected, and no requirements are defined. + +For FR1, when the CSI-RS for RLM is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD or L1-RSRP measurement, NCR-MT shall be able to measure the CSI-RS for RLM without any restriction. + +For FR2-1, when the CSI-RS for RLM measurement on one CC is in the same OFDM symbol as SSB for RLM, BFD, or L1-RSRP measurement on the same CC or different CCs in the same band, or in the same symbol as SSB for CBD measurement on the same CC or different CCs in the same band when beam failure is detected, NCR-MT is required to measure one of but not both CSI-RS for RLM and SSB. Longer measurement period for CSI-RS based RLM is expected, and no requirements are defined. + +For FR2-1, when the CSI-RS for RLM measurement on one CC is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD or L1-RSRP measurement on the same CC or different CCs in the same band, + +- In the following cases, NCR-MT is required to measure one of but not both CSI-RS for RLM and the other CSI-RS. Longer measurement period for CSI-RS based RLM is expected, and no requirements are defined. + - The CSI-RS for RLM or the other CSI-RS in a resource set configured with repetition ON, or + - The other CSI-RS is configured in q1 and beam failure is detected, or + +- The two CSI-RS-es are not QCL-ed w.r.t. QCL-TypeD, or the QCL information is not known to NCR-MT, +- Otherwise, NCR-MT shall be able to measure the CSI-RS for RLM without any restriction. + +#### 10.3.1.4 Minimum requirement for NCR-MT turning off the transmitter + +The transmitter power of the NCR-MT in the monitored cell shall be turned off within 40ms after expiry of T310 timer as specified in TS 38.331 [23]. + +#### 10.3.1.5 Minimum requirement for L1 indication + +When the downlink radio link quality on all the configured RLM-RS resources is worse than $Q_{out, layer 1}$ of the NCR-MT shall send an out-of-sync indication for the cell to the higher layers. A layer 3 filter shall be applied to the out-of-sync indications as specified in TS 38.331 [23]. + +When the downlink radio link quality on at least one of the configured RLM-RS resources is better than $Q_{in, layer 1}$ of the NCR-MT shall send an in-sync indication for the cell to the higher layers. A layer 3 filter shall be applied to the in-sync indications as specified in TS 38.331 [23]. + +The out-of-sync and in-sync evaluations for the configured RLM-RS resources shall be performed as specified in clause 5 [25]. Two successive indications from layer 1 shall be separated by at least $T_{Indication\_interval}$ . + +$T_{Indication\_interval}$ is $\max(10\text{ms}, T_{RLM-RS,M})$ , where $T_{RLM-RS,M}$ is the shortest periodicity of all configured RLM-RS resources for the monitored cell, which corresponds to $T_{SSB}$ specified in clause 10.3.1.2 if the RLM-RS resource is SSB, or $T_{CSI-RS}$ specified in clause 10.3.1.3 if the RLM-RS resource is CSI-RS. + +#### 10.3.1.6 Scheduling availability of NCR-MT during radio link monitoring + +When the reference signal to be measured for RLM has different subcarrier spacing than PDSCH/PDCCH or is on frequency range 2, there are restrictions on the scheduling availability as described in the following clauses. + +##### 10.3.1.6.1 Scheduling availability of NCR-MT performing radio link monitoring with a same subcarrier spacing as PDSCH/PDCCH on FR1 + +There are no scheduling restrictions due to radio link monitoring performed with a same subcarrier spacing as PDSCH/PDCCH on FR1. + +##### 10.3.1.6.2 Scheduling availability of NCR-MT performing radio link monitoring with a different subcarrier spacing than PDSCH/PDCCH on FR1 + +For NCR-MTs which support *simultaneousRxDatassb-DiffNumerology* [27] there are no restrictions on scheduling availability due to radio link monitoring based on SSB as RLM-RS. For NCR-MTs which do not support *simultaneousRxDatassb-DiffNumerology* [27] the following restrictions apply due to radio link monitoring based on SSB as RLM-RS. + +- The NCR-MT is not expected to transmit PUCCH, PUSCH or SRS or receive PDCCH, PDSCH or CSI-RS for tracking or CSI-RS for CQI on SSB symbols to be measured for radio link monitoring. + +### 10.3.1.6.3 Scheduling availability of NCR-MT performing radio link monitoring on FR2-1 + +The following scheduling restriction applies due to radio link monitoring on an FR2-1 serving PCell . + +- If the RLM-RS is CSI-RS which is type-D QCled with active TCI state for PDCCH or PDSCH, and the CSI-RS is not in a CSI-RS resource set with repetition ON, +- There are no scheduling restrictions due to radio link monitoring based on the CSI-RS. +- Otherwise +- The NCR-MT is not expected to transmit PUCCH, PUSCH or SRS or receive PDCCH, PDSCH or CSI-RS for tracking or CSI-RS for CQI on RLM-RS symbols to be measured for radio link monitoring. + +For FR2-1, if following conditions are met, + +- NCR-MT has been notified about system information update through paging, +- The gap between NCR-MT's reception of PDCCH that NCR-MT monitors in the Type2-PDCCH CSS set and that notifies system information update, and the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, is greater than 2 slots, + +For the SSB for RLM and CORESET for RMSI scheduling multiplexing patterns 3, NCR-MT is expected to receive the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, and the corresponding PDSCH, on SSB symbols to be measured for RLM; and + +For the SSB for RLM and CORESET for RMSI scheduling multiplexing patterns 2, NCR-MT is expected to receive PDSCH that corresponds to the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, on SSB symbols to be measured for RLM. + +## 10.3.2 Link Recovery Procedure + +### 10.3.2.1 Introduction + +The NCR-MT shall assess the downlink radio link quality of a serving cell based on the reference signal in the set as specified in TS 38.213 [24] in order to detect beam failure on: + +- PCell in SA NR,, + +The RS resource configurations in the set on PCell can be periodic CSI-RS resources and/or SSBs. RS resource configuration in the set on SCell shall be periodic CSI-RS. NCR-MT is not required to perform beam failure detection outside the active DL BWP. NCR-MT is not required to meet the requirements in clause 10.3.2.2 and 10.3.2.3 if NCR-MT does not have set . + +On each RS resource configuration in the set , the NCR-MT shall estimate the radio link quality and compare it to the threshold $Q_{out\_LR}$ for the purpose of accessing downlink radio link quality of the serving cell beams. + +The threshold $Q_{out\_LR}$ is defined as the level at which the downlink radio link of a given resource configuration on set cannot be reliably received and shall correspond to the $BLER_{out} = 10\%$ block error rate of a hypothetical PDCCH transmission. For SSB based beam failure detection, $Q_{out\_LR\_SSB}$ is derived based on the hypothetical PDCCH + +transmission parameters listed in Table 10.3.2.2.1. For CSI-RS based beam failure detection, $Q_{out\_LR\_CSI-RS}$ is derived based on the hypothetical PDCCH transmission parameters listed in Table 10.3.2.3.1-1. + +Upon request the NCR-MT shall deliver configuration indexes from the set as specified in TS 38.213 [24], to higher layers, and the corresponding L1-RSRP measurement provided that the measured L1-RSRP is equal to or better than the threshold $Q_{in\_LR}$ , which is indicated by higher layer parameter *rsrp-ThresholdSSB*. The NCR-MT applies the $Q_{in\_LR}$ threshold to the L1-RSRP measurement obtained from an SSB. The NCR-MT applies the $Q_{in\_LR}$ threshold to the L1-RSRP measurement obtained for a CSI-RS resource after scaling a respective CSI-RS reception power with a value provided by higher layer parameter *powerControlOffsetSS*. The RS resource configurations in the set can be periodic CSI-RS resources or SSBs or both SSB and CSI-RS resources. NCR-MT is not required to perform candidate beam detection outside the active DL BWP. + +## 10.3.2.2 Requirements for SSB based beam failure detection + +### 10.3.2.2.1 Introduction + +The requirements in this clause apply for each SSB resource in the set configured for a serving cell, provided that the SSB configured for beam failure detection is actually transmitted within the NCR-MT active DL BWP during the entire evaluation period specified in clause 10.3.2.2.2. The requirements in this clause could not be applicable if NCR-MT is required to perform beam failure detection on more than 1 serving cell per band. + +**Table 10.3.2.2.1-1: PDCCH transmission parameters for beam failure instance** + +| Attribute | Value for BLER | +|------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 0dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | Same as the SCS of RMSI CORESET | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 10.3.2.2.2 Minimum requirement + +NCR-MT shall be able to evaluate whether the downlink radio link quality on the configured SSB resource in set estimated over the last $T_{\text{Evaluate\_BFD\_SSB}}$ ms period becomes worse than the threshold $Q_{\text{out\_LR\_SSB}}$ within $T_{\text{Evaluate\_BFD\_SSB}}$ ms period. + +The value of $T_{\text{Evaluate\_BFD\_SSB}}$ is defined in Table 10.3.2.2.2-1 for FR1. + +The value of $T_{\text{Evaluate\_BFD\_SSB}}$ is defined in Table 10.3.2.2.2-2 for FR2-1 with scaling factor $N=8$ . + +For FR1, + +- $P=1$ . + +For FR2-1, + +- $P=1$ , when the BFD-RS resource is not overlapped with SMTC occasion. +- $P=2$ , when the BFD-RS resource is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P=3$ , when the BFD-RS resource is fully overlapped with SMTC period ( $T_{\text{SSB}} = T_{\text{SMTCperiod}}$ ). + +If the high layer in TS 38.331 [23] signaling of smtc2 is present, $T_{\text{SMTCperiod}}$ follows smtc2; Otherwise $T_{\text{SMTCperiod}}$ follow smtc1. + +Longer evaluation period would be expected if the combination of BFD-RS resource and SMTC occasion does not meet previous conditions. + +**Table 10.3.2.2.2-1: Evaluation period $T_{\text{Evaluate\_BFD\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_BFD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|-----------------------------------------------------------------| +| no DRX | $\text{Max}(50, \text{Ceil}(5 \times P) \times T_{\text{SSB}})$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_0$ . | | + +**Table 10.3.2.2.2-2: Evaluation period $T_{\text{Evaluate\_BFD\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_BFD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|--------------------------------------------------------------------------| +| no DRX | $\text{Max}(50, \text{Ceil}(5 \times P \times N) \times T_{\text{SSB}})$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_0$ . | | + +### 10.3.2.2.3 Measurement restriction for SSB based beam failure detection + +The NCR-MT is required to be capable of measuring SSB for BFD without measurement gaps. The NCR-MT is required to perform the SSB measurements with measurement restrictions as described in the following scenarios. + +For FR1, when the SSB for BFD measurement is in the same OFDM symbol as CSI-RS for RLM, BFD, CBD or L1-RSRP measurement, + +- If SSB and CSI-RS have same SCS, NCR-MT shall be able to measure the SSB for BFD measurement without any restriction; +- If SSB and CSI-RS have different SCS, + - If NCR-MT supports *simultaneousRxDatassb-DiffNumerology*, NCR-MT shall be able to measure the SSB for BFD measurement without any restriction; + - If NCR-MT does not support *simultaneousRxDatassb-DiffNumerology*, NCR-MT is required to measure one of but not both SSB for BFD measurement and CSI-RS. Longer measurement period for SSB based BFD measurement is expected, and no requirements are defined. + +For FR2-1, when the SSB for BFD measurement on one CC is in the same OFDM symbol as CSI-RS for RLM, BFD, CBD or L1-RSRP measurement on the same CC in the same band, NCR-MT is required to measure one of but not both SSB for BFD measurement and CSI-RS. Longer measurement period for SSB based BFD measurement is expected, and no requirements are defined. + +### 10.3.2.3 Requirements for CSI-RS based beam failure detection + +#### 10.3.2.3.1 Introduction + +The requirements in this clause apply for each CSI-RS resource in the set $\bar{q}_0$ of resource configurations for a serving cell, provided that the CSI-RS resource(s) in set $\bar{q}_0$ for beam failure detection are actually transmitted within the NCR-MT active DL BWP during the entire evaluation period specified in clause 10.3.2.3.2. NCR-MT is not expected to perform beam failure detection measurements on the CSI-RS configured for BFD if the CSI-RS is not QCL-ed, with QCL-TypeD when applicable, with the RS in the active TCI state of any CORESET configured in the NCR-MT active BWP. The requirements in this clause apply when NCR-MT is required to perform beam failure detection on no more than 1 serving cell per band. + +**Table 10.3.2.3.1-1: PDCCH transmission parameters for beam failure instance** + +| Attribute | Value for BLER | +|---------------------------------------------------------------------|--------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 0dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 10.3.2.3.2 Minimum requirement + +NCR-MT shall be able to evaluate whether the downlink radio link quality on the CSI-RS resource in set estimated over the last $T_{\text{Evaluate\_BFD\_CSI-RS}}$ ms period becomes worse than the threshold $Q_{\text{out\_LR\_CSI-RS}}$ within $T_{\text{Evaluate\_BFD\_CSI-RS}}$ ms period. + +The value of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ is defined in Table 10.3.2.3.2-1 for FR1. + +The value of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ is defined in Table 10.3.2.3.2-2 for FR2-1 with $N=1$ . + +The requirements of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ apply provided that the CSI-RS for BFD is not in a resource set configured with repetition ON. The requirements shall not apply when the CSI-RS resource in the active TCI state of CORESET is the same CSI-RS resource for BFD and the TCI state information of the CSI-RS resource is not given, wherein the TCI state information means QCL Type-D to SSB for L1-RSRP or CSI-RS with repetition ON. + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P = 1$ , when the BFD-RS resource is not overlapped with SMTC occasion. +- $P = P_{\text{sharing factor}}$ , when the BFD-RS resource is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = P_{\text{sharing factor}}$ , when BFD-RS resource is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). +- $P_{\text{sharing factor}} = 3$ . + +If the high layer in TS 38.331 [23] signaling of smtc2 is present, $T_{\text{SMTCPeriod}}$ follows smtc2; Otherwise $T_{\text{SMTCPeriod}}$ follow smtc1. + +NOTE: The overlap between CSI-RS for BFD and SMTC means that CSI-RS for BFD is within the SMTC window duration. + +Longer evaluation period would be expected if the combination of the BFD-RS resource and SMTC occasion configurations does not meet previous conditions. + +The values of $M_{\text{BFD}}$ used in Table 10.3.2.3.2-1 and Table 10.3.2.3.2-2 are defined as + +- $M_{\text{BFD}} = 10$ , if the CSI-RS resource(s) in set $\bar{q}_0$ used for BFD is transmitted with Density = 3. + +**Table 10.3.2.3.2-1: Evaluation period $T_{\text{Evaluate\_BFD\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_BFD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| no DRX | $\text{Max}(50, [M_{\text{BFD}} \times P] \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_0$ . | | + +**Table 10.3.2.3.2-2: Evaluation period $T_{\text{Evaluate\_BFD\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_BFD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| no DRX | $\text{Max}(50, [M_{\text{BFD}} \times P \times N] \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_0$ . | | + +### 10.3.2.3.3 Measurement restrictions for CSI-RS based beam failure detection + +The NCR-MT is required to be capable of measuring CSI-RS for BFD without measurement gaps. The NCR-MT is required to perform the CSI-RS measurements with measurement restrictions as described in the following scenarios. + +For both FR1 and FR2-1, when the CSI-RS for BFD measurement is in the same OFDM symbol as SSB for RLM, BFD, CBD or L1-RSRP measurement, NCR-MT is not required to receive CSI-RS for BFD measurement in the PRBs that overlap with an SSB. + +For FR1, when the SSB for RLM, BFD, CBD or L1-RSRP measurement is within the active BWP and has same SCS than CSI-RS for BFD measurement, the NCR-MT shall be able to perform CSI-RS measurement without restrictions. + +For FR1, when the SSB for RLM, BFD, CBD or L1-RSRP measurement is within the active BWP and has different SCS than CSI-RS for BFD measurement, the NCR-MT shall be able to perform CSI-RS measurement with restrictions according to its capabilities: + +- If the NCR-MT supports *simultaneousRxDatassb-DiffNumerology* the NCR-MT shall be able to perform CSI-RS measurement without restrictions. + +- If the NCR-MT does not support *simultaneousRxDataSSB-DiffNumerology*, NCR-MT is required to measure one of but not both CSI-RS for BFD measurement and SSB. Longer measurement period for CSI-RS based BFD measurement is expected, and no requirements are defined. + +For FR1, when the CSI-RS for BFD measurement is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD or L1-RSRP measurement, NCR-MT shall be able to measure the CSI-RS for BFD measurement without any restriction. + +For FR2-1, when the CSI-RS for BFD measurement on one CC is in the same OFDM symbol as SSB for RLM, BFD or L1-RSRP measurement on the same CC in the same band, or in the same symbol as SSB for CBD measurement on the same CC in the same band when beam failure is detected, NCR-MT is required to measure one of but not both CSI-RS for BFD measurement and SSB. Longer measurement period for CSI-RS based BFD measurement is expected, and no requirements are defined. + +For FR2-1, when the CSI-RS for BFD measurement on one CC is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD or L1-RSRP measurement on the same CC in the same band, + +- In the following cases, NCR-MT is required to measure one of but not both CSI-RS for BFD measurement and the other CSI-RS. Longer measurement period for CSI-RS based BFD measurement is expected, and no requirements are defined. + - The CSI-RS for BFD measurement or the other CSI-RS in a resource set configured with repetition ON, or + - The other CSI-RS is configured in set $\bar{q}_l$ and beam failure is detected, or + - The two CSI-RS-es are not QCL-ed w.r.t. QCL-TypeD, or the QCL information is not known to NCR-MT, +- Otherwise, NCR-MT shall be able to measure the CSI-RS for BFD measurement without any restriction. + +#### 10.3.2.4 Minimum requirement for L1 indication + +When the radio link quality on all the RS resources in set is worse than $Q_{\text{out\_LR, layer 1}}$ of the NCR-MT shall send a beam failure instance indication to the higher layers. A layer 3 filter may be applied to the beam failure instance indications as specified in TS 38.331 [23]. + +The beam failure instance evaluation for the RS resources in set shall be performed as specified in clause 6 in TS 38.213 [24]. Two successive indications from layer 1 shall be separated by at least $T_{\text{Indication\_interval\_BFD}}$ . + +$T_{\text{Indication\_interval\_BFD}}$ is $\max(2\text{ms}, T_{\text{SSB-RS,M}})$ or $\max(2\text{ms}, T_{\text{CSI-RS,M}})$ , where $T_{\text{SSB-RS,M}}$ and $T_{\text{CSI-RS,M}}$ is the shortest periodicity of all RS resources in set for the accessed cell, corresponding to either the shortest periodicity of the SSB in the set or CSI-RS resource in the set. + +### 10.3.2.5 Requirements for SSB based candidate beam detection + +#### 10.3.2.5.1 Introduction + +The requirements in this clause apply for each SSB resource in the set $\bar{q}_1$ configured for a serving cell, provided that the SSBs configured for candidate beam detection are actually transmitted within NCR-MT active DL BWP during the entire evaluation period specified in clause 10.3.2.5.2. + +#### 10.3.2.5.2 Minimum requirement + +Upon request the NCR-MT shall be able to evaluate whether the L1-RSRP measured on the configured SSB resource in set $\bar{q}_1$ estimated over the last $T_{\text{Evaluate\_CBD\_SSB}}$ ms period becomes better than the threshold $Q_{\text{in\_LR}}$ provided SSB\_RP and SSB Ês/Iot are according to Annex Table in B.2.4.1 [23] for a corresponding band. + +The NCR-MT shall monitor the configured SSB resources using the evaluation period in table 10.3.2.5.2-1 and 10.3.2.5.2-2 which is applicable to the non-DRX mode only. + +The value of $T_{\text{Evaluate\_CBD\_SSB}}$ is defined in Table 10.3.2.5.2-1 for FR1. + +The value of $T_{\text{Evaluate\_CBD\_SSB}}$ is defined in Table 10.3.2.5.2-2 for FR2-1 with scaling factor N=8. + +Where, + +For FR1,, + +- $P = 1$ . + +For FR2-1, + +- $P=1$ , when the candidate beam detection RS resource is not overlapped with SMTC occasion. +- $P=2$ , when candidate beam detection RS is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when candidate beam detection RS is fully overlapped with SMTC period ( $T_{\text{SSB}} = T_{\text{SMTCperiod}}$ ). + +If the high layer in TS 38.331 [23] signaling of smtc2 is present, $T_{\text{SMTCperiod}}$ follows smtc2; Otherwise $T_{\text{SMTCperiod}}$ follow smtc1. + +Longer evaluation period would be expected if the combination of CBD-RS resource and SMTC occasion configurations does not meet previous conditions. + +**Table 10.3.2.5.2-1: Evaluation period $T_{\text{Evaluate\_CBD\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_CBD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|-------------------------------------------------| +| non-DRX | $\text{Ceil}(3 \times P) \times T_{\text{SSB}}$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_1$ . | | + +**Table 10.3.2.5.2-2: Evaluation period $T_{\text{Evaluate\_CBD\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_CBD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|----------------------------------------------------------| +| non-DRX | $\text{Ceil}(3 \times P \times N) \times T_{\text{SSB}}$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_1$ . | | + +### 10.3.2.5.3 Measurement restriction for SSB based candidate beam detection + +For FR1, when the SSB for CBD measurement is in the same OFDM symbol as CSI-RS for RLM, BFD, CBD or L1-RSRP measurement, + +- If SSB and CSI-RS have same SCS, NCR-MT shall be able to measure the SSB for CBD measurement without any restrictions; +- If SSB and CSI-RS have different SCS-es, + - If NCR-MT supports *simultaneousRxDataSSB-DiffNumerology*, NCR-MT shall be able to measure the SSB for CBD measurement without any restriction; + - If NCR-MT does not support *simultaneousRxDataSSB-DiffNumerology*, NCR-MT is required to measure one of but not both SSB for CBD measurement and CSI-RS. Longer measurement period for SSB based CBD measurement is expected, and no requirements are defined. + +For FR2-1, when the SSB for CBD measurement on one CC is in the same OFDM symbol as CSI-RS for RLM, BFD, CBD or L1-RSRP measurement on the same CC in the same band, NCR-MT is required to measure one of but not both SSB for CBD measurement and CSI-RS. Longer measurement period for SSB based CBD measurement is expected, and no requirements are defined. + +### 10.3.2.6 Requirements for CSI-RS based candidate beam detection + +#### 10.3.2.6.1 Introduction + +The requirements in this clause apply for each CSI-RS resource in the set $\bar{q}_1$ configured for a serving cell, provided that the CSI-RS resources configured for candidate beam detection are actually transmitted within NCR-MT active DL BWP during the entire evaluation period specified in clause 10.3.2.6.2. + +#### 10.3.2.6.2 Minimum requirement + +Upon request the NCR-MT shall be able to evaluate whether the L1-RSRP measured on the configured CSI-RS resource in set $\bar{q}_1$ estimated over the last $T_{\text{Evaluate\_CBD\_CSI-RS}}$ [ms] period becomes better than the threshold $Q_{\text{in\_LR}}$ within $T_{\text{Evaluate\_CBD\_CSI-RS}}$ [ms] period provided CSI-RS $\hat{E}_s/\text{Iot}$ is according to Annex Table in B.2.4.2 [23] for a corresponding band. + +The NCR-MT shall monitor the configured CSI-RS resources using the evaluation period in table 10.3.2.6.2-1 and 10.3.2.6.2-2 which is applicable to the non-DRX mode only. + +The value of $T_{\text{Evaluate\_CBD\_CSI-RS}}$ is defined in Table 10.3.2.6.2-1 for FR1. + +The value of $T_{\text{Evaluate\_CBD\_CSI-RS}}$ is defined in Table 10.3.2.6.2-2 for FR2-1 with scaling factor $N=8$ . + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P = 1$ , when candidate beam detection RS is not overlapped with SMTC occasion. +- $P = 2$ , when candidate beam detection RS is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when candidate beam detection RS is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). + +If the high layer in TS 38.331 [23] signaling of smtc2 is present, $T_{\text{SMTCperiod}}$ follows smtc2; Otherwise $T_{\text{SMTCperiod}}$ follow smtc1. + +Longer evaluation period would be expected if the CSI-RS is on the same OFDM symbols with RLM, BFD, BM-RS, or other CBD-RS, according to the measurement restrictions defined in clause 10.3.2.6.3. + +The values of $M_{\text{CBD}}$ used in Table 10.3.2.6.2-1 and Table 10.3.2.6.2-2 are defined as + +- $M_{\text{CBD}} = 3$ , if the CSI-RS resource configured in the set $\bar{q}_1$ is transmitted with Density = 3. + +**Table 10.3.2.6.2-1: Evaluation period $T_{\text{Evaluate\_CBD\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_CBD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| non-DRX | $\text{Max}(25, \text{Ceil}(M_{\text{CBD}} \times P) \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_1$ . | | + +**Table 10.3.2.6.2-2: Evaluation period $T_{\text{Evaluate\_CBD\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_CBD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| non-DRX | $\text{Max}(25, \text{Ceil}(M_{\text{CBD}} \times P \times N) \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_1$ . | | + +### 10.3.2.6.3 Measurement restriction for CSI-RS based candidate beam detection + +For both FR1 and FR2-1, when the CSI-RS for CBD measurement is in the same OFDM symbol as SSB for RLM, BFD, CBD or L1-RSRP measurement, NCR-MT is not required to receive CSI-RS for CBD measurement in the PRBs that overlap with an SSB. + +For FR1, when the SSB for RLM, BFD, CBD or L1-RSRP measurement is within the active BWP and has same SCS than CSI-RS for CBD measurement, the NCR-MT shall be able to perform CSI-RS based CBD measurement without restrictions. + +For FR1, when the SSB for RLM, BFD, CBD or L1-RSRP measurement is within the active BWP and has different SCS than CSI-RS for CBD measurement, the NCR-MT shall be able to perform CSI-RS based CBD measurement with restrictions according to its capabilities: + +- If the NCR-MT supports *simultaneousRxDatassB-DiffNumerology* the NCR-MT shall be able to perform CSI-RS based CBD measurement for without restrictions. +- If the NCR-MT does not support *simultaneousRxDatassB-DiffNumerology*, NCR-MT is required to measure one of but not both CSI-RS for CBD measurement and SSB. Longer measurement period for CSI-RS based CBD measurement is expected, and no requirements are defined. + +For FR1, when the CSI-RS for CBD measurement is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD or L1-RSRP measurement, NCR-MT shall be able to measure the CSI-RS for CBD measurement without any restriction. + +For FR2-1, when the CSI-RS for CBD measurement on one CC is in the same OFDM symbol as SSB for RLM, BFD, CBD or L1-RSRP measurement on the same CC in the same band, NCR-MT is required to measure one of but not both CSI-RS for CBD measurement and SSB. Longer evaluation period for CSI-RS based CBD measurement is expected, and no requirements are defined. + +For FR2-1, when the CSI-RS for CBD measurement on one CC is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD or L1-RSRP measurement on the same CC in the same band, NCR-MT is required to measure one of but not both CSI-RS for CBD measurement and the other CSI-RS. Longer evaluation period for CSI-RS based CBD measurement is expected, and no requirements are defined. + +### 10.3.2.7 Scheduling availability of NCR-MT during beam failure detection + +Scheduling availability restrictions when the NCR-MT is performing beam failure detection are described in the following clauses. + +#### 10.3.2.7.1 Scheduling availability of NCR-MT performing beam failure detection with a same subcarrier spacing as PDSCH/PDCCH on FR1 + +There are no scheduling restrictions due to beam failure detection performed on SSB and CSI-RS configured for BFD with the same SCS as PDSCH or PDCCH in FR1. + +#### 10.3.2.7.2 Scheduling availability of NCR-MT performing beam failure detection with a different subcarrier spacing than PDSCH/PDCCH on FR1 + +For NCR-MTs which support *simultaneousRxDatassB-DiffNumerology* [27] there are no restrictions on scheduling availability due to beam failure detection when SSB is configured as BFD. For NCR-MTs which do not support *simultaneousRxDatassB-DiffNumerology* [27] the following restrictions apply due to beam failure detection when SSB is configured as BFD. + +- The NCR-MT is not expected to transmit PUCCH, PUSCH or SRS or receive PDCCH, PDSCH or CSI-RS for tracking or CSI-RS for CQI on SSB symbols to be measured for beam failure detection. + +### 10.3.2.7.3 Scheduling availability of NCR-MT performing beam failure detection on FR2-1 + +The following scheduling restriction applies due to beam failure detection. + +- For the case where no RSs are provided for BFD, or when CSI-RS is configured for BFD is explicitly configured and is type-D QCled with active TCI state for PDCCH or PDSCH, and the CSI-RS is not in a CSI-RS resource set with repetition ON. +- There are no scheduling restrictions due to beam failure detection performed based on the CSI-RS. +- Otherwise + - The NCR-MT is not expected to transmit PUCCH, PUSCH or SRS or receive PDCCH, PDSCH or CSI-RS for tracking or CSI-RS for CQI on BFD-RS resource symbols to be measured for beam failure detection. + +For FR2-1, if following conditions are met, + +- NCR-MT has been notified about system information update through paging, +- The gap between NCR-MT's reception of PDCCH that NCR-MT monitors in the Type2-PDCCH CSS set and that notifies system information update, and the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, is greater than 2 slots, + +For the SSB and CORESET for RMSI scheduling multiplexing patterns 3, NCR-MT is expected to receive the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, and the corresponding PDSCH, on SSB symbols to be measured for BFD measurement; and + +For the SSB and CORESET for RMSI scheduling multiplexing patterns 2, NCR-MT is expected to receive PDSCH that corresponds to the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, on SSB symbols to be measured for BFD measurement. + +### 10.3.2.8 Scheduling availability of NCR-MT during candidate beam detection + +Scheduling availability restrictions when the NCR-MT is performing L1-RSRP measurement for candidate beam detection are described in the following clauses. + +#### 10.3.2.8.1 Scheduling availability of NCR-MT performing L1-RSRP measurement with a same subcarrier spacing as PDSCH/PDCCH on FR1 + +There are no scheduling restrictions due to L1-RSRP measurement performed on SSB and CSI-RS configured as link recovery detection resource with the same SCS as PDSCH or PDCCH in FR1. + +#### 10.3.2.8.2 Scheduling availability of NCR-MT performing L1-RSRP measurement with a different subcarrier spacing than PDSCH/PDCCH on FR1 + +For NCR-MTs which support *simultaneousRxDatassb-DiffNumerology* [27] there are no restrictions on scheduling availability due to L1-RSRP measurement based on SSB as link recovery detection resource. For NCR-MTs which do not support *simultaneousRxDatassb-DiffNumerology* [27] the following restrictions apply due to L1-RSRP measurement based on SSB configured as link recovery detection resource. + +- The NCR-MT is not expected to transmit PUCCH, PUSCH or SRS or receive PDCCH, PDSCH, TRS, CSI-RS for tracking or CSI-RS for CQI on SSB symbols to be measured for L1-RSRP. + +#### 10.3.2.8.3 Scheduling availability of NCR-MT performing L1-RSRP measurement on FR2-1 + +The following scheduling restriction applies due to candidate beam detection + +- The NCR-MT is not expected to transmit PUCCH, PUSCH or SRS or receive PDCCH, PDSCH, CSI-RS for tracking or CSI-RS for CQI on reference symbols to be measured for candidate beam detection. + +For FR2-1, if following conditions are met, + +- NCR-MT has been notified about system information update through paging, +- The gap between NCR-MT's reception of PDCCH that NCR-MT monitors in the Type2-PDCCH CSS set and that notifies system information update, and the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, is greater than 2 slots, + +For the SSB and CORESET for RMSI scheduling multiplexing patterns 3, NCR-MT is expected to receive the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, and the corresponding PDSCH, on SSB symbols to be measured for CBD measurement; and + +For the SSB and CORESET for RMSI scheduling multiplexing patterns 2, NCR-MT is expected to receive PDSCH that corresponds to the PDCCH that NCR-MT monitors in the Type0-PDCCH CSS set, on SSB symbols to be measured for CBD measurement. + +--- + +## Annex A (normative): + +# Environmental requirements for the Repeater equipment + +** + +## Annex B (informative): + +### Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|----------------------------------------------|-----|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2022-03 | RAN#95e | RP-220790 | | | NR Repeater Radio Transmission and Reception | | 1.0.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|--------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-06 | RAN#96 | RP-221681 | 0002 | 1 | F | CR to 38.106: TDD off power radiated requirement correction | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0003 | 1 | F | CR to 38.106: Corrections to definitions, symbols and abbreviations | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0004 | 1 | F | CR to 38.106: Output power definitions for NR repeaters | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0006 | 1 | F | CR for TS 38.106 R17: clean up of clause 4 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0007 | 1 | F | CR for TS 38.106 R17: clean up of clause 6 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0008 | 1 | F | CR for TS 38.106 R17: clean up of clause 7 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0009 | 1 | F | CR to TS38.106: clarification on the supported operating bands for NR repeater | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0011 | 1 | F | CR to TS 38.106 with corrections to repeater core specification | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0012 | | F | BIG CR to 38.106 maintenance | 17.1.0 | +| 2022-09 | RAN#97 | RP-222034 | 0013 | | F | CR to 38.106: NR repeater ACLR requirements | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0015 | 1 | F | CR to 38.106: NR repeater receiver spurious emissions requirements | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0016 | | F | CR to 38.106: Removal of unlicensed bands for NR repeaters | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0017 | 1 | F | CR to 38.106: Correction of LA ACLR requirements | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0018 | | F | CR to 38.106: Correction of LA ACLR requirements | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0019 | 1 | F | CR to TS 38.106 with updates and corrections for conductive part | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0020 | | F | CR to TS 38.106 with updates and corrections for radiated part | 17.2.0 | +| 2022-09 | RAN#97 | RP-222034 | 0021 | | F | Big CR for TS 38.106 Maintenance (Rel-17, CAT F) | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0026 | 1 | F | CR to 38.106: ACLR requirements | 17.3.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0027 | 1 | F | CR to 38.106: EVM requirements | 17.3.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0028 | 1 | F | CR to 38.106: ACRR requirements | 17.3.0 | +| 2023-03 | RAN#99 | RP-230518 | 0029 | 1 | F | CR for TS 38.106: Correction of some errors in 3.2 | 17.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230535 | 0030 | 1 | B | CR to 38.106 on introduction of Band n54 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230533 | 0032 | | B | CR to TS38.106 the introduction of APT600MHz | 18.0.0 | +| 2023-06 | RAN#100 | RP-231339 | 0036 | | A | CR to 38.106: Corrections on repeater OTA output power requirements (Rel-18) | 18.1.0 | +| 2023-09 | RAN#101 | RP-232496 | 0037 | | D | CR to 38.106: Editorial correction in transmitter transient period for NR repeaters | 18.2.0 | +| 2023-09 | RAN#101 | RP-232496 | 0039 | | A | [NR_repeaters] CR to 38.106: Input intermodulation | 18.2.0 | +| 2023-12 | RAN#102 | RP-233366 | 0041 | | B | CR to TS38.106: introduction of NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0042 | | B | CR to TS 38.106 - Introduction of band n109 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233350 | 0044 | | A | CR to 38.106: Correction of terminologies for NR repeaters (Rel-18) | 18.3.0 | +| 2023-12 | RAN#102 | RP-233350 | 0047 | 1 | F | CR to TS 38.106 with correction of co-existence and co-location requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233361 | 0049 | 1 | B | Big CR to TS 38.106 on RRM core requirements for NR network-controlled repeaters | 18.3.0 | +| 2023-12 | RAN#102 | RP-233361 | 0050 | | B | Big CR to TS 38.106 Introduction of NCR | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38113/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-18/38_series/38113/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03c23fa440478402ed1cc022498d71839112906e --- /dev/null +++ b/marked/Rel-18/38_series/38113/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9141166c58fdae8ab0e08898d804f76778d3990cd68a757d5f76a1d5ef074b23 +size 24807 diff --git a/marked/Rel-18/38_series/38113/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38113/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38 --- /dev/null +++ b/marked/Rel-18/38_series/38113/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5 +size 9571 diff --git a/marked/Rel-18/38_series/38113/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38113/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0832538d0b0fc775d7387c1f50353105f3aa47e --- /dev/null +++ b/marked/Rel-18/38_series/38113/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:304e1fe73ba2e0bc82c25950e394183135f21102f5470dd764cf828943e2ff52 +size 5618 diff --git a/marked/Rel-18/38_series/38113/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-18/38_series/38113/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07379420cf72e0ad27fe4e52d74ff05cdec4fb91 --- /dev/null +++ b/marked/Rel-18/38_series/38113/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8d2e4bf50646f2ee71a5d0ecf4e61051603d1590bf8ce0dcd68b757d9da4e79 +size 28026 diff --git a/marked/Rel-18/38_series/38113/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg b/marked/Rel-18/38_series/38113/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa74ebfb2921869c512864af4dff689f4df510b5 --- /dev/null +++ b/marked/Rel-18/38_series/38113/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2587161b3a254b0fcf948a474760aa2633809888c0410c547b5a26287b8aca30 +size 23341 diff --git a/marked/Rel-18/38_series/38113/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-18/38_series/38113/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e62dc8db88fba639991677dd1eaa3de76fcde81 --- /dev/null +++ b/marked/Rel-18/38_series/38113/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:191927dab03015dfa2c268fd36fbad162a7069514ef10ec35a19a443d16e57a9 +size 24953 diff --git a/marked/Rel-18/38_series/38113/ee8536b235eb6aad21e2048fd5308900_img.jpg b/marked/Rel-18/38_series/38113/ee8536b235eb6aad21e2048fd5308900_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dd33fd6fad2d5707afe740513e77317c6ecdc88 --- /dev/null +++ b/marked/Rel-18/38_series/38113/ee8536b235eb6aad21e2048fd5308900_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08e16ab61410d9dbae6493e8c151a50c6a89789610aae1f1f6166e7b79f0873b +size 23947 diff --git a/marked/Rel-18/38_series/38113/raw.md b/marked/Rel-18/38_series/38113/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..92dce90325a51ae5052253972cdd58ee9fd32ad7 --- /dev/null +++ b/marked/Rel-18/38_series/38113/raw.md @@ -0,0 +1,1281 @@ + + +# 3GPP TS 38.113 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) ElectroMagnetic Compatibility (EMC) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations ..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations ..... | 13 | +| 4 Test conditions ..... | 14 | +| 4.1 General ..... | 14 | +| 4.2 Arrangements for establishing a communication link..... | 15 | +| 4.3 Narrow band responses on receivers..... | 15 | +| 4.4 Exclusion bands..... | 15 | +| 4.4.1 Transmitter exclusion band ..... | 15 | +| 4.4.2 Receiver exclusion band..... | 16 | +| 4.5 BS test configurations ..... | 16 | +| 4.6 Manufacturer declarations..... | 17 | +| 5 Performance assessment ..... | 18 | +| 5.1 General ..... | 18 | +| 5.2 Assessment of throughput in Downlink ..... | 18 | +| 5.3 Assessment of throughput in Uplink..... | 18 | +| 5.4 Ancillary equipment..... | 18 | +| 6 Performance criteria..... | 19 | +| 6.1 Performance criteria for continuous phenomena for BS..... | 19 | +| 6.2 Performance criteria for transient phenomena for BS..... | 20 | +| 6.3 Performance criteria for continuous phenomena for Ancillary equipment..... | 20 | +| 6.4 Performance criteria for transient phenomena for Ancillary equipment..... | 20 | +| 7 Applicability overview..... | 21 | +| 7.1 Emission..... | 21 | +| 7.2 Immunity ..... | 21 | +| 8 Emission..... | 22 | +| 8.1 Test configurations..... | 22 | +| 8.1.1 (Void) ..... | 22 | +| 8.1.2 (Void) ..... | 22 | +| 8.1.3 (Void) ..... | 22 | +| 8.1.4 (Void) ..... | 22 | +| 8.1.5 (Void) ..... | 22 | +| 8.2 Radiated emission ..... | 22 | +| 8.2.1 Radiated emission, BS..... | 22 | +| 8.2.1.1 Definition ..... | 23 | +| 8.2.1.2 Test method..... | 23 | +| 8.2.1.3 Limits ..... | 23 | +| 8.2.1.4 Interpretation of the measurement results..... | 24 | +| 8.2.2 Radiated emission, ancillary equipment..... | 25 | +| 8.2.2.1 Definition ..... | 25 | +| 8.2.2.2 Test method..... | 25 | +| 8.2.2.3 Limits ..... | 25 | +| 8.3 Conducted emission DC power input/output port..... | 26 | +| 8.3.1 Definition..... | 26 | +| 8.3.2 Test method ..... | 26 | +| 8.3.3 Limits..... | 26 | +| 8.4 Conducted emissions, AC mains power input/output port..... | 26 | +| 8.4.1 Definition..... | 27 | + +| | | | +|---------|------------------------------------------------------------------------------------|----| +| 8.4.2 | Test method ..... | 27 | +| 8.4.3 | Limits..... | 27 | +| 8.5 | Conducted emissions, telecommunication port..... | 27 | +| 8.5.1 | Definition..... | 27 | +| 8.5.2 | Test method ..... | 27 | +| 8.5.3 | Limits..... | 27 | +| 8.6 | Harmonic current emissions (AC mains input port) ..... | 28 | +| 8.7 | Voltage fluctuations and flicker (AC mains input port)..... | 28 | +| 9 | Immunity ..... | 28 | +| 9.1 | Test configurations..... | 28 | +| 9.1.1 | (Void) ..... | 29 | +| 9.1.2 | (Void) ..... | 29 | +| 9.1.3 | (Void) ..... | 29 | +| 9.1.4 | (Void) ..... | 29 | +| 9.1.5 | (Void) ..... | 29 | +| 9.2 | RF electromagnetic field (80 MHz to 6000 MHz)..... | 29 | +| 9.2.1 | Definition..... | 29 | +| 9.2.2 | Test method and level..... | 29 | +| 9.2.3 | Performance criteria ..... | 30 | +| 9.3 | Electrostatic discharge..... | 30 | +| 9.3.1 | Definition..... | 30 | +| 9.3.2 | Test method and level..... | 31 | +| 9.3.3 | Performance criteria ..... | 31 | +| 9.4 | Fast transients common mode..... | 31 | +| 9.4.1 | Definition..... | 31 | +| 9.4.2 | Test method and level..... | 31 | +| 9.4.3 | Performance criteria ..... | 31 | +| 9.5 | RF common mode (0.15 MHz - 80 MHz)..... | 32 | +| 9.5.1 | Definition..... | 32 | +| 9.5.2 | Test method and level..... | 32 | +| 9.5.3 | Performance criteria ..... | 32 | +| 9.6 | Voltage dips and interruptions ..... | 32 | +| 9.6.1 | Definition..... | 33 | +| 9.6.2 | Test method and level..... | 33 | +| 9.6.3 | Performance criteria ..... | 33 | +| 9.7 | Surges, common and differential mode..... | 33 | +| 9.7.1 | Definition..... | 33 | +| 9.7.2 | Test method and level..... | 34 | +| 9.7.2.1 | Test method for telecommunication ports directly connected to outdoor cables ..... | 34 | +| 9.7.2.2 | Test method for telecommunication ports connected to indoor cables..... | 34 | +| 9.7.2.3 | Test method for AC power ports ..... | 34 | +| 9.7.3 | Performance criteria ..... | 34 | + +| | | +|---------------------------------------------------|-----------| +| Annex A (informative): Change history..... | 35 | +|---------------------------------------------------|-----------| + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document covers the assessment of NR Base Station (BS) and ancillary equipment in respect of Electromagnetic Compatibility (EMC). + +The present document specifies the applicable requirements, procedures, test conditions, performance assessment and performance criteria for NR base stations and associated ancillary equipment in the following categories: + +- BS equipped with antenna connectors or *TAB connectors* which are possible to be terminated during EMC testing, meeting the *BS type 1-C* and *BS type 1-H* RF requirements of TS 38.104 [2], with conformance demonstrated by compliance to TS 38.141-1 [3]. +- BS not equipped with antenna connectors nor *TAB connectors*, i.e. with antenna elements radiating during the EMC testing, meeting the *BS type 1-O* and *BS type 2-O* RF requirements of TS 38.104 [2], with conformance demonstrated by compliance to TS 38.141-2 [4]. + +Technical requirements related to the antenna and *TAB connectors* are not included in the present document. These are found in the relevant NR BS product standards TS 38.104 [2], 3GPP TS 38.141-1[3], and 3GPP TS 38.141-2 [4]. + +The environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [7], IEC 61000-6-3 [8] and IEC 61000-6-8 [33]. + +The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [3] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing". +- [4] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing". +- [5] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)". +- [6] 3GPP TS 37.114: "Active Antenna System (AAS) Base Station (BS) Electromagnetic Compatibility (EMC)". +- [7] IEC 61000-6-1: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards - Immunity for residential, commercial and light-industrial environments". +- [8] IEC 61000-6-3: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards - Emission standard for equipment in residential environments". + +- [9] IEC 60050-161: "International Electrotechnical Vocabulary (IEV) - Part 161: Electromagnetic compatibility". +- [10] void +- [11] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements". +- [12] void +- [13] IEC 61000-3-2: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current $\leq 16$ A per phase)". +- [14] IEC 61000-3-12: "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic currents produced by equipment connected to public low-voltage system with input current $> 16$ A and $\leq 75$ A per phase". +- [15] IEC 61000-3-3: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems, for equipment with rated current $\leq 16$ A per phase and not subject to conditional connection". +- [16] IEC 61000-3-11: "Electromagnetic compatibility (EMC) - Part 3-11: Limits – Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems - Equipment with rated current $\leq 75$ A and subject to conditional connections". +- [17] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test". +- [18] IEC 61000-4-3:2006+AMD1:2007+AMD2:2010 CSV: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test". +- [19] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4-4: Testing and measurement techniques - Electrical fast transient/burst immunity test". +- [20] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test". +- [21] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances, induced by radio frequency fields". +- [22] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations immunity tests". +- [23] ETSI EN 301 489-1: "ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements; Harmonised Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU and the essential requirements of article 6 of Directive 2014/30/EU". +- [24] Recommendation ITU-R SM.329-12: "Unwanted emissions in the spurious domain". +- [25] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception". +- [26] Recommendation ITU-R SM.1539-1: "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329". +- [27] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [28] ETSI EN 301 489-50: "Electromagnetic compatibility (EMC) standard for radio equipment and services; Part 50: Specific conditions for cellular communication base station (BS), repeater and ancillary equipment; Harmonised standard covering the essential requirements of article 3.1(b) of the Directive 2014/53/EU". +- [29] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods". + +- [30] CISPR 16-1-4: 2019-01: "Specification for radio disturbance and immunity measuring apparatus and methods – Part 1-4: Radio disturbance and immunity measuring apparatus – Antennas and test sites for radiated disturbance measurements" +- [31] CISPR 16-4-2: " Specification for radio disturbance and immunity measuring apparatus and methods - Part 4-2: Uncertainties, statistics and limit modelling - Measurement instrumentation uncertainty, Amendment 2" +- [32] ETSI TR 100 028-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Uncertainties in the measurement of mobile radio equipment characteristics, part 1" +- [33] IEC 61000-6-8:"Electromagnetic compatibility (EMC) - Part 6-8: Generic standards - Emission standard for professional equipment in commercial and light-industrial locations". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**ancillary equipment:** electrical or electronic equipment, that is intended to be used with a receiver or transmitter + +NOTE: It is considered as an ancillary equipment if: + +the equipment is intended for use with a receiver or transmitter to provide additional operational and/or control features to the radio equipment, (e.g. to extend control to another position or location); and + +the equipment cannot be used on a stand alone basis to provide user functions independently of a receiver or transmitter; and + +the receiver or transmitter, to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions). + +**antenna port:** for EMC purposes, port for connection of an antenna used for intentional transmission and/or reception of radiated RF energy, equivalent to an RF antenna connector/*TAB connector* in TS 37.105 [25]. + +**BS type 1-C:** NR base station operating at FR1 with requirements set consisting only of conducted requirements defined at individual antenna connectors. + +**BS type 1-H:** NR base station operating at FR1 with a requirement set consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB. + +**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB. + +**BS type 2-O:** NR base station operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB. + +**channel bandwidth:** the RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The *channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**continuous phenomena:** electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [9]). + +**enclosure port:** physical boundary of the equipment through which electromagnetic fields may radiate or impinge. + +NOTE: In the case of *integral antenna* equipment, this port is inseparable from the antenna port. + +**exclusion band:** frequency range(s) not subject to test or assessment. + +**free-space open area test site:** reference test site with precautions to ensure that reflections do not influence the measurement. + +NOTE: The free-space open area test site (FSOATS) is the concept of the test site. A practical approximation is a Fully-Anechoic Room (FAR). + +**fully-anechoic room:** shielded enclosure, the internal surfaces of which are lined with radio-frequency-energy absorbing material (i.e. RF absorber) that absorbs electromagnetic energy in the frequency range of interest. + +**integral antenna:** antenna designed for permanent connection to the equipment and considered part of the enclosure port. + +NOTE: An *integral antenna* may be fitted internally or externally. + +**lower RF bandwidth edge:** the frequency of the lower edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements. + +**operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements. + +**port:** particular interface of EUT used for EMC requirements testing purposes. + +NOTE: Any connection point on EUT intended for connection of cables to or from EUT during the EMC testing is considered as a port. + +EXAMPLE 1: Examples of ports for *BS type 1-C* and *BS type 1-H* are as presented in figure 3.1-1: + +![Diagram of BS type 1-C and BS type 1-H showing an apparatus inside an enclosure with various ports.](ee8536b235eb6aad21e2048fd5308900_img.jpg) + +The diagram shows a rectangular 'Apparatus' inside a larger rectangular 'Enclosure'. The 'Enclosure' has a label 'Enclosure Port' above it. On the left side of the enclosure, there are three horizontal lines representing ports: 'AC power port', 'DC power port', and 'Earth port'. On the right side, there are four horizontal lines representing ports: 'Antenna port', 'Signal/control port', 'Telecommunication port', and an unlabeled line at the bottom. + +Diagram of BS type 1-C and BS type 1-H showing an apparatus inside an enclosure with various ports. + +**Figure 3.1-1: Examples of ports for BS type 1-C and BS type 1-H** + +EXAMPLE 2: Examples of ports for *BS type 1-O* and *BS type 2-O* (i.e. with no *antenna ports*) are as presented in figure 3.1-2: + +![Diagram of BS type 1-O and BS type 2-O showing an apparatus inside an enclosure with various ports, but no antenna port.](c6005b2627c6ca10f6b0e94cdb34858d_img.jpg) + +The diagram shows a rectangular 'Apparatus' inside a larger rectangular 'Enclosure'. The 'Enclosure' has a label 'Enclosure' above it. On the left side of the enclosure, there are three horizontal lines representing ports: 'AC power port', 'DC power port', and 'Earth port'. On the right side, there are two horizontal lines representing ports: 'Signal/control port' and 'Telecommunication port'. There is no 'Antenna port' on the right side. + +Diagram of BS type 1-O and BS type 2-O showing an apparatus inside an enclosure with various ports, but no antenna port. + +**Figure 3.1-2: Examples of ports for BS type 1-O and BS type 2-O** + +**receiver exclusion band:** band of frequencies over which no tests of radiated immunity of a receiver are made, and expressed relative to the BS receive band. + +**semi-anechoic chamber:** shielded enclosure in which all surfaces except the metal floor are covered with material that absorbs electromagnetic energy (i.e. RF absorber) in the frequency range of interest. + +**signal port:** port intended for the interconnection of components of an EUT, or between an EUT and associated equipment and used in accordance with relevant functional specifications (for example for the maximum length of cable connected to it). + +**spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *BS type 1-O* or *BS type 2-O* (i.e. half sphere around the EUT's radiating direction). + +**TAB connector:** *transceiver array boundary* connector + +**Throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition. + +**transceiver array boundary:** conducted interface between the *transceiver unit* array and the composite antenna. + +**transceiver unit:** active unit consisting of transmitter and/or receiver which transmits and/or receives radio signals, and which may include passive RF filters. + +**telecommunication port:** ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks. + +NOTE: *Telecommunication port* is called "wired network port" in CISPR 32 [11] and ETSI EN 301 489-1 [23]. + +**transient phenomena:** pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [9]). + +**transmitter exclusion band:** band of frequencies over which no tests of radiated immunity of a transmitter are made and is expressed relative to the carrier frequencies used (the carrier frequencies of the base stations activated transmitter(s)). + +**upper RF bandwidth edge:** the frequency of the upper edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\beta$ | Bandwidth | +| $BW_{\text{Channel}}$ | Channel bandwidth | +| $\Delta f_{\text{OBUE}}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $F_{\text{DL,low}}$ | The lowest frequency of the downlink operating band | +| $F_{\text{DL,high}}$ | The highest frequency of the downlink operating band | +| $F_{\text{UL,low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL,high}}$ | The highest frequency of the uplink operating band | +| $\Delta f_{\text{RIexclusion}}$ | Maximum offset of the Radiated Immunity exclusion band from the uplink operating band edge for test without spatial exclusion zone applied | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-----|--------------------------| +| AC | Alternating Current | +| AMN | Artificial Mains Network | +| BC | Band Category | +| BS | Base Station | + +| | | +|----------|-------------------------------------------------| +| CA | Carrier Aggregation | +| CDN | Coupling/Decoupling Network | +| CS | Capability Set | +| DC | Direct Current | +| EIRP | Equivalent Isotropic Radiated Power | +| EMC | Electromagnetic Compatibility | +| e.r.p. | Effective Radiated Power | +| ESD | Electrostatic Discharge | +| EUT | Equipment Under Test | +| FR | Frequency Range | +| FAR | Fully-Anechoic Room | +| FRC | Fixed Reference Channel | +| FSOATS | Free Space OATS | +| NC | Non Contiguous | +| NG | Next Generation | +| NGC | Next Generation Core | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NRTC | NR Test Configuration | +| NTC | Test Configuration for Non-contiguous operation | +| NSA | Normalized Site Attenuation | +| OATS | Open Area Test Site | +| RAT | Radio Access Technology | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| rms | root mean square | +| RSM | Reference Site Method | +| SAC | Semi Anechoic Chamber | +| SC | Single Carrier | +| SDL | Supplementary Downlink | +| TC | Test Configuration | +| UL | Uplink | + +# --- 4 Test conditions + +## 4.1 General + +Requirements throughout the EMC specifications are in some cases defined separately for different frequency ranges (FR). The frequency ranges FR1 and FR2 are defined in subclause 5.1 of TS 38.104 [2]. + +The equipment shall be tested in normal test environment defined in the corresponding BS conformance testing specification TS 38.141-1 [3] for *BS type 1-C* and *BS type 1-H*, or TS 38.141-2 [4] for *BS type 1-O* and *BS type 2-O*. The test conditions shall be recorded in the test report. + +For BS capable of multi-band operation, the requirements in the present document apply for each supported *operating band* unless otherwise stated. *Operating bands* shall be activated according to the test configuration in subclause 4.5. Tests shall be performed relating to each type of port and all *operating bands* shall be assessed during the tests. + +The manufacturer shall declare the supported *operating band(s)* according to the list of NR *operating bands* defined in TS 38.104 [2]. + +NOTE 1: NR *operating bands* for *BS type 1-C* and *BS type 1-H*, are declared by the manufacturer according to the declaration D.3 specified in TS 38.141-1 [3], table 4.6-1. + +NOTE 2: NR *operating bands* for *BS type 1-O* and *BS type 2-O*, are declared by the manufacturer according to the declaration D.4 specified in TS 38.141-2 [4], table 4.6-1. + +## 4.2 Arrangements for establishing a communication link + +The wanted RF input signal nominal frequency shall be selected by setting the NR Absolute Radio Frequency Channel Number (NR-ARFCN) to an appropriate number, as defined in TS 38.104 [2], clause 5.4.2.3. + +A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called "the test system") at the radio interface and *telecommunication port(s)* (the NG interface). The test system shall be located outside of the test environment. + +When the EUT is required to be in the transmit/receive mode, the following conditions shall be met: + +- For the *BS type 1-C* and *BS type 1-H* testing, the EUT shall be commanded to operate at rated transmit power; +- For the *BS type 1-O* and *BS type 2-O* testing, the EUT transmit power shall be configured as stated in subclause 8.1 for emission test and subclause 9.1 for immunity test accordingly; +- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment; +- The wanted input signal level shall be set to a level where the performance is not limited by the receiver noise floor or strong signal effects. + +NOTE: 15 dB above the conducted reference sensitivity level has been used as an example of wanted input signal level in legacy 3GPP EMC specifications for establishing a communication link. + +For immunity tests clause 4.3 shall apply and the conditions shall be as follows. + +## 4.3 Narrow band responses on receivers + +Responses on receivers or duplex transceivers occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method: + +- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by $2 \times BW_{\text{Channel}}$ MHz, where $BW_{\text{Channel}}$ is the channel bandwidth as defined in TS 38.104 [2], clause 5.3; +- if the deviation disappears in either one or both of the above MHz offset cases, then the response is considered as a narrow band response; +- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to $2.5 \times BW_{\text{Channel}}$ MHz; +- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test. + +For immunity test narrow band responses are disregarded. + +For BS capable of multi-band operation, all supported *operating bands* shall be considered for narrowband responses. + +## 4.4 Exclusion bands + +### 4.4.1 Transmitter exclusion band + +The *transmitter exclusion band* for BS is the frequency range over which no tests of radiated immunity of a transmitter are made. The *transmitter exclusion band* only applies to BS type 1-O. + +The *transmitter exclusion band* is defined as: + +$$F_{\text{DL,low}} - \Delta f_{\text{OBUE}} < f < F_{\text{DL,high}} + \Delta f_{\text{OBUE}}$$ + +Where: + +Values of $F_{DL,low}$ and $F_{DL,high}$ are defined for each *operating band* in TS 38.104 [2], clause 5.2. + +The value of $\Delta f_{OBUE}$ is derived considering the width of the *operating band*, and is defined in TS 38.104 [2], clause 6.6.2. + +For BS capable of multi-band operation, the total *transmitter exclusion band* is a combination of the *exclusion bands* for each *operating band* supported by BS. + +NOTE 1: The *transmitter exclusion bands* do not apply for SUL bands. + +NOTE 2: As the radiated immunity testing is defined in the frequency range 80 MHz to 6 GHz, there is no *transmitter exclusion band* defined for BS type 2-O. + +### 4.4.2 Receiver exclusion band + +The *receiver exclusion band* for BS is the frequency range over which no tests of radiated immunity of a receiver are made. + +The *receiver exclusion band* is defined as: + +$$F_{UL,low} - \Delta f_{OOB} < f < F_{UL,high} + \Delta f_{OOB}$$ + +Where: + +Values of $F_{UL,low}$ and $F_{UL,high}$ are defined for each *operating band* in TS 38.104 [2], clause 5.2. + +The value of $\Delta f_{OOB}$ is derived considering the width of the *operating band*, and is defined in TS 38.104 [2], clause 7.4.2.2. + +In case the *spatial exclusion zone* (as depicted in figure 9.2.2-1) is not used during the EMC RI testing, the receiver exclusion band for BS type 1-O is defined as: + +$$F_{UL,low} - \Delta f_{RIexclusion} < f < F_{UL,high} + \Delta f_{RIexclusion}$$ + +Where the values of $\Delta f_{RIexclusion}$ are defined in table 4.4.2-1. + +**Table 4.4.2-1: Maximum $\Delta f_{RIexclusion}$ offset outside the uplink operating band** + +| Operating band characteristics | $\Delta f_{RIexclusion}$ (MHz) | +|-------------------------------------------------|--------------------------------| +| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$ | 60 | +| $100 \text{ MHz} < F_{UL,high} - F_{UL,low}$ | 200 | + +For BS capable of multi-band operation, the total *receiver exclusion band* is a combination of the *exclusion bands* for each *operating band* supported by BS. + +NOTE 1: The *receiver exclusion bands* do not apply for SDL bands. + +NOTE 2: As the radiated immunity testing is defined in the frequency range 80 MHz to 6 GHz, there is no *receiver exclusion band* defined for BS type 2-O. + +## 4.5 BS test configurations + +The present clause defines the BS test configurations that shall be used for demonstrating conformance. A single NR carrier shall be used for testing of single-carrier capable BS. + +Single carrier configuration (SC) tests shall be performed using signal with narrowest supported *BS channel bandwidth* with the smallest supported subcarrier spacing declared per *operating band* in TS 38.141-1 [3] clause 4.6 (see declaration D.14), and TS 38.141-2 [4] clause 4.6 (see declaration D.7). + +For other NR base stations, the test configurations in table 4.5-1 and table 4.5-2 shall be used. The NR test configurations (NRTCx) are defined in TS 38.141-1 [3], clause 4.7 for *BS type 1-C* and *BS type 1-H* and in TS 38.141-2 [4], clause 4.8 for *BS type 1-O* and *BS type 2-O*. + +**Table 4.5-1: Test configurations for *BS type 1-C* and *BS type 1-H*** + +| BS test case | BS capable of multi-carrier and/or CA in a single band | | | BS capable of multi-band operation | | +|----------------|--------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------------------------------------|------------------------------------------------------------| +| | Contiguous spectrum capable BS | C and NC capable BS with identical parameters | C and NC capable BS with different parameters | BS capable of multi-band operation with common connector | BS capable of multi-band operation with separate connector | +| Emission tests | NRTC1 | NRTC3 | NRTC1, NRTC3 | NRTC1/3 (Note 1), NRTC5 | NRTC1/3 (Note 1), NRTC5 (Note 2) | +| Immunity tests | NRTC1 | NRTC3 | NRTC1, NRTC3 | NRTC1/3 (Note 1), NRTC5 | NRTC1/3 (Note 1), NRTC5 (Note 3) | + +Note 1: NRTC1 and/or NRTC3 shall be applied in each supported operating band. +Note 2: For single-band operation test, other antenna connector(s) is (are) terminated. +Note 3: NRTC5 is only applicable for multi-band receiver. + +**Table 4.5-2: Test configurations for *BS type 1-O*** + +| BS test | Single band RIB | | | Multi-band RIB | +|----------------|--------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------| +| | Contiguous spectrum capable BS | C and NC capable BS with identical parameters | C and NC capable BS with different parameters | | +| Emission tests | NRTC1 | NRTC3 | NRTC1, NRTC3 | NRTC1/3 (Note), NRTC5 | +| Immunity tests | NRTC1 | NRTC3 | NRTC1, NRTC3 | NRTC5 | + +Note: NRTC1 and/or NRTC3 shall be applied in each supported operating band. + +**Table 4.5-3: Test configurations for *BS type 2-O*** + +| BS test case | Single band RIB | | | +|----------------|--------------------------------|-----------------------------------------------|-----------------------------------------------| +| | Contiguous spectrum capable BS | C and NC capable BS with identical parameters | C and NC capable BS with different parameters | +| Emission tests | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| Immunity tests | NRTC1 | NRTC3 | NRTC1, NRTC3 | + +## 4.6 Manufacturer declarations + +The following EMC-specific manufacturer's declarations listed in table 4.6-1 are required to be provided by the manufacturer for NR BS requirements testing. + +NOTE: The below listed manufacturer's declarations are supplementary to declarations covered in TS 38.141-1 [3] and/or TS 38.141-2 [4]. + +**Table 4.6-1 EMC-specific manufacturer declarations** + +| Declaration identifier | Declaration | Description | +|--------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------| +| DEMC.1 (NOTE) | Ports intended to be used with cables less than 3 m | Declaration of any port(s) intended to be used with cables less than 3 m. | +| NOTE: This manufacturer declaration is optional. | | | + +# 5 Performance assessment + +## 5.1 General + +The following information shall be recorded in or annexed to the test report: + +- the primary functions of the radio equipment to be tested during and after the EMC testing; +- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment; +- the method to be used to verify that a communications link is established and maintained; +- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress; +- the *ancillary equipment* to be combined with the radio equipment for testing (where applicable); +- the information about *ancillary equipment* intended to be used with the radio equipment; +- information about the common and/or band-specific active RF components and other hardware blocks for a communication link in BS capable of multi-band operation; +- an exhaustive list of ports (and RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power. + +Performance assessment of a BS with multiple enclosures may be done separately for the BS part with the Radio digital unit and the Radio unit respectively, according to the manufacturer's choice. + +A communication link used by more than one *operating band*, shall be assessed on all *operating bands*. Communication link(s) and/or radio performance parameters for the *operating bands* can during the test be assessed simultaneously or separately for each band, depending on the test environment capability. + +## 5.2 Assessment of throughput in Downlink + +A communication link shall be established between the transmitter (via port for the *BS type 1-C* and *BS type 1-H*, or via RIB for the *BS type 1-O* and *BS type 2-O*) and the test equipment. Test equipment shall meet the requirements for the throughput assessment defined in TS 38.101-4 [27] for the bearer used in the immunity tests. The level of the signal supplied to the equipment should be within the range for which the assessment of throughput is not impaired. Power control shall be OFF during the immunity testing. + +## 5.3 Assessment of throughput in Uplink + +The value of the throughput at the output of the receiver shall be monitored at NG interface by using suitable test equipment. + +## 5.4 Ancillary equipment + +At the manufacturer's discretion the test may be performed on the *ancillary equipment* separately or on a representative configuration of the combination of radio and *ancillary equipment*. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the *ancillary equipment* to be used with different radio equipment. + +# 6 Performance criteria + +## 6.1 Performance criteria for continuous phenomena for BS + +The test should, where possible, be performed using a bearer with the characteristics of data rate and throughput defined in table 6.1-1 and table 6.1-2. If the test is not performed using one of these bearers (for example, of none of them are supported by the BS), the characteristics of the bearer used shall be recorded in the test report. + +The throughput in table 6.1-1 and table 6.1-2 is stated relative to the maximum throughput of the FRC. + +The BS uplink and downlink paths shall each meet the performance criteria defined in table 6.1-1 and table 6.1-2 during the test. If the uplink and downlink paths are evaluated as a one loop then the criteria is two times the throughput reduction shown in table 6.1-1 and table 6.1-2 (i.e. throughput > 90 % instead of throughput > 95 %). After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained. + +**Table 6.1-1: FR1 performance criteria for continuous phenomena for BS** + +| NR channel bandwidth (MHz) as defined in TS 38.104 section 5.3.2-1 [2] | Sub-carrier spacing (kHz) | Bearer information data rate | Performance criteria (Note 1, Note 2) | +|------------------------------------------------------------------------|---------------------------|------------------------------------------|------------------------------------------| +| 3 | 15 | G-FR1-A1-7 in annex A.1 in TS 38.104 [2] | Throughput > 95 %,
no loss of service | +| 5, 10, 15 | 15 | G-FR1-A1-1 in annex A.1 in TS 38.104 [2] | | +| 10, 15 | 30 | G-FR1-A1-2 in annex A.1 in TS 38.104 [2] | | +| 10, 15 | 60 | G-FR1-A1-3 in annex A.1 in TS 38.104 [2] | | +| 20 to 50 | 15 | G-FR1-A1-4 in annex A.1 in TS 38.104 [2] | | +| 20 to 100 | 30 | G-FR1-A1-5 in annex A.1 in TS 38.104 [2] | | +| 20 to 100 | 60 | G-FR1-A1-6 in annex A.1 in TS 38.104 [2] | | + +NOTE 1: The performance criteria, throughput > 95 %, no loss of service, applies also if a bearer with another characteristics is used in the test. +NOTE 2: The performance criteria, throughput > 90 %, no loss of service, applies instead if the uplink and downlink paths are evaluated as a one loop. + +**Table 6.1-2: FR2 performance criteria for continuous phenomena for BS** + +| NR channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Bearer information data rate | Performance criteria (Note 1, Note 2) | +|----------------------------|---------------------------|------------------------------------------|------------------------------------------| +| 50, 100, 200 | 60 | G-FR2-A1-1 in annex A.1 in TS 38.104 [2] | Throughput > 95 %,
no loss of service | +| 50 | 120 | G-FR2-A1-2 in annex A.1 in TS 38.104 [2] | | +| 100, 200, 400 | 120 | G-FR2-A1-3 in annex A.1 in TS 38.104 [2] | | + +NOTE 1: The performance criteria, throughput > 95 %, no loss of service, applies also if a bearer with another characteristics is used in the test. +NOTE 2: The performance criteria, throughput > 90 %, no loss of service, applies instead if the uplink and downlink paths are evaluated as a one loop. + +## 6.2 Performance criteria for transient phenomena for BS + +At the conclusion of the total test (comprising the series of individual exposures to transient phenomena) the EUT shall operate as intended with no user noticeable loss of control functions or stored data. At the conclusion of each exposure the EUT shall operate with no user noticeable loss of the communication link. The channel bandwidth, sub-carrier spacing and bearer information data rate should be chosen based on manufacturers declarations (see declaration D.14 in TS 38.141-1 [3] and/or D.7 in TS 38/141-2 [4]) and defined according to table 6.1-1 and table 6.1-2. + +## 6.3 Performance criteria for continuous phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +## 6.4 Performance criteria for transient phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +# 7 Applicability overview + +## 7.1 Emission + +Table 7.1-1: Emission requirements applicability + +| Phenomenon | Application | Equipment test requirement | | Reference clause in the present document | Reference standard | +|----------------------------------|-----------------------------------------|-----------------------------------------------------|---------------------|------------------------------------------|----------------------------------------------------| +| | | BS equipment | Ancillary equipment | | | +| Radiated emission | Enclosure | applicable for BS type 1-C and BS type 1-H (Note 1) | not applicable | 8.2.1 | ITU-R SM.329 [24] | +| Radiated emission | Enclosure of ancillary equipment | not applicable | applicable | 8.2.2 | CISPR 32 [11] | +| Conducted emission | DC power input/output port | applicable | applicable | 8.3 | CISPR 32 [11] | +| Conducted emission | AC mains input/output port | applicable | applicable | 8.4 | CISPR 32 [11] | +| Conducted emission | Telecommunication port | applicable | applicable | 8.5 | CISPR 32 [11] | +| Harmonic current emissions | AC mains input port | applicable | applicable | 8.6 | IEC 61000-3-2 [13] or IEC 61000-3-12 [14] (NOTE 2) | +| Voltage fluctuations and flicker | AC mains input port | applicable | applicable | 8.7 | IEC 61000-3-3 [15] or IEC 61000-3-11 [16] (NOTE 2) | + +NOTE 1: Radiated emission requirements for BS type 1-O and BS type 2-O are described in clause 8.2.1. + +NOTE 2: Selection of the reference IEC specification is based on the rated input current of the EUT's power supply. + +## 7.2 Immunity + +Table 7.2-1: Immunity requirements applicability + +| Phenomenon | Application | Equipment test requirement | | Reference clause in the present document | Reference standard | +|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------|------------------------------------------|---------------------| +| | | BS equipment | Ancillary equipment | | | +| RF electromagnetic field (80 – 6000 MHz) | Enclosure | applicable | applicable | 9.2 | IEC 61000-4-3 [18] | +| Electrostatic discharge | Enclosure | applicable | applicable | 9.3 | IEC 61000-4-2 [17] | +| Fast transients common mode | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | 9.4 | IEC 61000-4-4 [19] | +| RF common mode 0.15 - 80 MHz | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | 9.5 | IEC 61000-4-6 [21] | +| Voltage dips and interruptions | AC mains power input ports | applicable | applicable | 9.6 | IEC 61000-4-11 [22] | +| Surges, common and differential mode | AC power input ports and telecommunications port | applicable | applicable | 9.7 | IEC 61000-4-5 [20] | + +# 8 Emission + +## 8.1 Test configurations + +This clause defines the configurations for emission tests as follows: + +- The equipment shall be tested under normal test conditions as specified in the functional standards; +- The test configuration shall be as close to normal intended use as possible; +- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of *ancillary equipment* necessary to exercise the ports; +- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- The test conditions, test configuration and mode of operation shall be recorded in the test report; +- Ports which in normal operation are connected shall be connected to an *ancillary equipment* or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the *ancillary equipment*; in case of *BS type 1-H*, *antenna ports* shall be correctly terminated; +- For *BS type 1-O* and *BS type 2-O* without *antenna ports* but intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup suitable for the radiated power; +- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- The test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time. + +8.1.1 (Void) + +8.1.2 (Void) + +8.1.3 (Void) + +8.1.4 (Void) + +8.1.5 (Void) + +## 8.2 Radiated emission + +### 8.2.1 Radiated emission, BS + +This test is applicable to *BS type 1-C* and *BS type 1-H*. This test shall be performed on a representative configuration of BS. + +For *BS type 1-O* and *BS type 2-O*, the radiated emission is covered by radiated spurious emission requirement in TS 38.104 [2], conforming to the test requirement in TS 38.141-2 [4]. + +#### 8.2.1.1 Definition + +This test assesses the ability of BS to limit unwanted emission from the *enclosure port*. + +#### 8.2.1.2 Test method + +- a) A test site fulfilling the requirements of ITU-R SM.329 [24] shall be used. The BS shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads. One of the following two alternative measurement methods shall be used: + +- 1) Field strength method measurement + +The test method shall be in accordance with CISPR 32 [11]. The field strength measurements shall be performed on a test site that is validated according to the methods and requirements of CISPR 16-1-4 [30]. + +Unless otherwise stated, measurements are conducted at 3 m or 10 m on an open area test site (OATS) or semi anechoic chamber (SAC) for frequencies up to 1 GHz, or at 3 m on a free space open area test site (FSOATS) or fully-anechoic room (FAR) for frequencies above 1 GHz. Unless otherwise stated, all measurements are done with RMS detector and with the -3 dB bandwidth of the measuring filter equal to the reference bandwidth in table 8.2.1.3-1. + +NOTE 1: Test site validation methods for radiated emissions tests are defined in CISPR 16-1-4 [30], clause 6 and 7. Examples of test site validation methods are listed below: + +- 30 - 1000 MHz frequency range: Normalized Site Attenuation (NSA), Reference Site Method (RSM). +- 1 - 18 GHz frequency range: $S_{VSWR}$ standard test procedure, $S_{VSWR}$ reciprocal test procedure. + +- 2) Substitution method measurement (also called a substitution method) + +Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane. Unless otherwise stated, all measurements are done as mean power (RMS). + +NOTE 2: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2.15 dB between e.i.r.p. and e.r.p., as defined in ITU-R SM.329 annex 1 [24]. + +$$\text{e.r.p. (dBm)} = \text{EIRP (dBm)} - 2.15$$ + +- b) The BS shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated in clause 4.5. +- c) The received power shall be measured over the frequency range from 30 MHz to $F_{DL,low} - \Delta f_{OBUE}$ and from $F_{DL,high} + \Delta f_{OBUE}$ up to 12750 MHz. For some *operating bands*, the upper limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the downlink *operating band*, as specified in ITU-R SM.329 [24]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS). + +#### 8.2.1.3 Limits + +The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [24] and SM.1539 [26]. + +The BS type 1-C and BS type 1-H shall meet the limits below: + +**Table 8.2.1.3-1: Limits for radiated emissions from BS** + +| Frequency range | e.r.p.
(dBm) | Field strength at 3 m
(dB $\mu$ V/m)
(NOTE 4) | Field strength at 10 m
(dB $\mu$ V/m)
(NOTE 4) | Reference bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------|------------------------------------------------------|---------------------|----------| +| 30 MHz $\leq f < 1000$ MHz | -36 | 65.4 (NOTE 5) | 54.9 (NOTE 5) | 100 kHz | | +| 1 GHz $\leq f < 12.75$ GHz | -30 | 67.4 | Not applicable | 1 MHz | | +| 12.75 GHz $\leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the DL operating band in GHz | -30 | 67.4 | Not applicable | 1 MHz | NOTE 1 | +| 12.75 GHz - 26 GHz | -30 | 67.4 | Not applicable | 1 MHz | NOTE 6 | +| $F_{\text{DL,low}} - \Delta f_{\text{OBUE}} < f < F_{\text{DL,high}} + \Delta f_{\text{OBUE}}$ | Not defined | Not defined | Not defined | Not defined | NOTE 2,3 | +| NOTE 1: This frequency range applies only for operating bands for which the 5th harmonic of the upper frequency edge of the DL operating band is reaching beyond 12.75 GHz. | | | | | | +| NOTE 2: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported operating bands apply. | | | | | | +| NOTE 3: $\Delta f_{\text{OBUE}}$ is defined in clause 6.6.1 of TS 38.104 [2]. | | | | | | +| NOTE 4: The field strength measurements shall be conducted on OATS or SAC for frequencies up to 1 GHz, or on FSOATS or FAR for frequencies above 1 GHz. | | | | | | +| NOTE 5: Limits for radiated emissions are translated from the e.r.p. limit of -36 dBm into the field strength limit of 61.4 dB $\mu$ V/m (at 3m) or 50.9 dB $\mu$ V/m (at 10m), and increased by the site gain value of 4 dB. The value of the site gain is based on ITU-R Recommendations SM.329 [24]. | | | | | | +| NOTE 6: Applies only for band n46, n96 and n102. | | | | | | + +#### 8.2.1.4 Interpretation of the measurement results + +The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows: + +- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document; +- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report; +- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figures in table 8.2.1.4-1 for BS. + +Table 8.2.1.4-1 specifies the maximum measurement uncertainty of the test system. The test system shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +**Table 8.2.1.4-1: Maximum measurement uncertainty (BS)** + +| Parameter | Uncertainty for EUT dimension $\leq 1$ m
(NOTE 2) | Uncertainty for EUT dimension $> 1$ m
(NOTE 2) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|---------------------------------------------------| +| Effective radiated RF power between 30 MHz and 180 MHz | $\pm 6$ dB | $\pm 6$ dB | +| Effective radiated RF power between 180 MHz and 4 GHz | $\pm 4$ dB | $\pm 6$ dB | +| Effective radiated RF power between 4 GHz and 12,75 GHz | $\pm 6$ dB | $\pm 9$ dB (NOTE 1) | +| Effective radiated RF power between 12,75 GHz and 26 GHz | $\pm 6$ dB | $\pm 9$ dB (NOTE 1) | +| Field strength between 30 MHz and 12,75 GHz | $\pm 6$ dB | $\pm 6$ dB | +| Field strength between 12,75 GHz and 26 GHz | $\pm 6$ dB | $\pm 6$ dB | +| NOTE 1: This value may be reduced to $\pm 6$ dB when further information on the potential radiation characteristic of the EUT is available. | | | +| NOTE 2: These MU values estimates and are not based on the MU budget calculations. For more background on MU derivation analyses refer to CISPR 16-4-2 [31] and ETSI TR 100 028-1 [32]. | | | + +NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 8.2.1.4-1, this equipment can still be used, provided that an adjustment is made follows: + +Any additional uncertainty in the Test System over and above that specified in table 8.2.1.4-1 is used to tighten the test requirements, i.e. making the test harder to pass. + +This procedure will ensure that a test system not compliant with table 8.2.1.4-1 does not increase the probability of passing an EUT that would otherwise have failed a test if a test system compliant with table 8.2.1.4-1 had been used. + +### 8.2.2 Radiated emission, ancillary equipment + +This test is only applicable to *ancillary equipment* not incorporated in the radio equipment and intended to be measured on a stand-alone basis, as declared by the manufacturer. This test shall be performed on a representative configuration of the *ancillary equipment*. + +This test is not applicable for *ancillary equipment* incorporated in the radio equipment, or for *ancillary equipment* intended to be measured in combination with the radio equipment. In these cases, the requirements of the relevant product standard for the effective use of the radio spectrum shall apply. + +#### 8.2.2.1 Definition + +This test assesses the ability of *ancillary equipment* to limit unwanted emission from the *enclosure port*. + +#### 8.2.2.2 Test method + +The test method shall be in accordance with CISPR 32 [11]. + +#### 8.2.2.3 Limits + +The *ancillary equipment* shall meet the limits according to CISPR 32 [11] table A.4 and table A.5. + +For the referred limit values, the following shall apply: + +- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. +- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +**Table 8.2.2.3-1: (Void)** + +**Table 8.2.2.3-2: (Void)** + +Alternatively, for *ancillary equipment* intended to be used in telecommunication centres only, the class A limits given in CISPR 32 [11], annex A, table A.2 and table A.3 may be used. + +## 8.3 Conducted emission DC power input/output port + +This test is applicable to equipment which may have DC cables longer than 3 m. + +If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in clause 8.4. + +This test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 8.3.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to limit internal noise from the DC power input/output ports. + +### 8.3.2 Test method + +The test method shall be in accordance with CISPR 32 [11] and the Artificial Mains Network (AMN) shall be connected to a DC power source. + +In the case of DC output ports, the ports shall be connected via an AMN to a load drawing the rated current of the source. + +A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded. + +The equipment shall be installed with a ground plane as defined in CISPR 32 [11]. The reference earth point of the AMN shall be connected to the reference ground plane with a conductor as short as possible. + +### 8.3.3 Limits + +The equipment shall meet the limits according to CISPR 32 [11] table A.9, which are defined for average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +Where there is a step in the referred limit values, the lower value shall be applied at the transition frequency. + +**Table 8.3.3-1: (Void)** + +## 8.4 Conducted emissions, AC mains power input/output port + +This test is applicable to equipment powered by the AC mains. + +This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT. + +This test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 8.4.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to limit internal noise from the AC mains power input/output ports. + +### 8.4.2 Test method + +The test method shall be in accordance with CISPR 32 [11]. + +### 8.4.3 Limits + +The equipment shall meet the limits according to CISPR 32 [11] table A.10, which are defined for the average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +For the referred limit values following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +#### Table 8.4.3-1: (Void) + +Alternatively, for equipment intended to be used in telecommunication centres the limits given in CISPR 32 [11] table A.9 shall be used. + +##### Table 8.4.3-2: (Void) + +## 8.5 Conducted emissions, telecommunication port + +This test is applicable for radio equipment and/or *ancillary equipment* for fixed use which have *telecommunication ports*. + +This test shall be performed on a representative configuration of radio equipment, the associated *ancillary equipment*, or a representative configuration of the combination of radio and *ancillary equipment*. + +### 8.5.1 Definition + +This test assesses the EUT unwanted emission present at the *telecommunication ports*. + +### 8.5.2 Test method + +The test method shall be in accordance with CISPR 32 [11]. + +### 8.5.3 Limits + +The *telecommunication ports* shall meet the limits according to CISPR 32 [11] table A.12. + +For the referred limit values, following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +#### Table 8.5.3-1: (Void) + +Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in CISPR 32 [11] table A.11 may be used. + +**Table 8.5.3-2: (Void)** + +## 8.6 Harmonic current emissions (AC mains input port) + +The requirements of IEC 61000-3-2 [13] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current greater than 16 A per phase, IEC 61000-3-12 [14] applies. + +## 8.7 Voltage fluctuations and flicker (AC mains input port) + +The requirements of IEC 61000-3-3 [15] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current greater than 16 A per phase, IEC 61000-3-11 [16] applies. + +# --- 9 Immunity + +## 9.1 Test configurations + +This clause defines the configurations for immunity tests as follows: + +- the equipment shall be tested under normal test conditions as specified in the functional standards; +- during the test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link; +- the test configuration shall be as close to normal intended use as possible; +- if the equipment is part of a system, or can be connected to *ancillary equipment*, then it shall be acceptable to test the equipment while connected to the minimum configuration of *ancillary equipment* necessary to exercise the ports; +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an *ancillary equipment* or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the *ancillary equipment*. In case of *BS type 1-C and BS type 1-H*, antenna ports shall be correctly terminated; +- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- immunity tests on the entire NR BS shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the NG interface (e.g. with an NGC simulator) and evaluating the throughput (see figures 9.1-1 and 9.1-2); +- immunity tests shall be performed on both the uplink and downlink paths. The tests shall also include both the radio interface and the NG interface. Throughput evaluation may be carried out at either interface, where appropriate, and the measurements for the uplink and downlink paths may be carried out as a single path looped at either the radio interface or NG interface. In case of looping is used care have to be taken that the throughput information doesn't change due to looping; + +- for NR BS capable of multi-band operation, communication links shall be established in such a way that all *operating band(s)* are activated during the test according to the applicable test configurations in clause 4.5. Performance assessment may be done separately for each *operating band*. + +![Figure 9.1-1: Communication link set up for BS type 1-C/BS type 1-H immunity measurement. The diagram shows three main components: a UE Simulator on the left, a BS (Base Station) in the center, and an NGC Simulator on the right. The BS is labeled 'BS type 1-C/ BS type 1-H' and '(Antenna Ports Terminated)'. Arrows indicate bidirectional communication links between the UE Simulator and the BS, and between the BS and the NGC Simulator.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` + +graph LR + UE[UE Simulator] <--> BS["BS type 1-C/ +BS type 1-H +(Antenna Ports Terminated)"] + BS <--> NGC[NGC Simulator] + +``` + +Figure 9.1-1: Communication link set up for BS type 1-C/BS type 1-H immunity measurement. The diagram shows three main components: a UE Simulator on the left, a BS (Base Station) in the center, and an NGC Simulator on the right. The BS is labeled 'BS type 1-C/ BS type 1-H' and '(Antenna Ports Terminated)'. Arrows indicate bidirectional communication links between the UE Simulator and the BS, and between the BS and the NGC Simulator. + +Figure 9.1-1: Communication link set up for BS type 1-C/BS type 1-H immunity measurement + +![Figure 9.1-2: Communication link set up for BS type 1-O/BS type 2-O immunity measurement. The diagram shows three main components: a UE Simulator on the left, a BS (Base Station) in the center, and an NGC Simulator on the right. The BS is labeled 'BS type 1-O/ BS type 2-O'. A large double-headed arrow labeled 'OTA Link' connects the UE Simulator and the BS. Arrows also indicate bidirectional communication links between the BS and the NGC Simulator.](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` + +graph LR + UE[UE Simulator] <-->|OTA Link| BS["BS type 1-O/ +BS type 2-O"] + BS <--> NGC[NGC Simulator] + +``` + +Figure 9.1-2: Communication link set up for BS type 1-O/BS type 2-O immunity measurement. The diagram shows three main components: a UE Simulator on the left, a BS (Base Station) in the center, and an NGC Simulator on the right. The BS is labeled 'BS type 1-O/ BS type 2-O'. A large double-headed arrow labeled 'OTA Link' connects the UE Simulator and the BS. Arrows also indicate bidirectional communication links between the BS and the NGC Simulator. + +Figure 9.1-2: Communication link set up for BS type 1-O/BS type 2-O immunity measurement + +9.1.1 (Void) + +9.1.2 (Void) + +9.1.3 (Void) + +9.1.4 (Void) + +9.1.5 (Void) + +## 9.2 RF electromagnetic field (80 MHz to 6000 MHz) + +The test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.2.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. + +### 9.2.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-3 [18], which specifies test methodology based on anechoic chamber. The use of reverberation chamber test method according to IEC 61000-4-21 [29], clause 6.1 and Annex D as alternative method is allowed. + +The following requirements shall apply: + +- The test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 1 % of the momentary frequency; +- The test shall be performed over the frequency range 80 MHz - 6000 MHz; with the exception of the exclusion band for receivers (see clause 4.4); + +- Responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies selected during the test shall be recorded in the test report. +- For the test method in accordance with IEC 61000-4-3[18], the *spatial exclusion zone* can be chosen to protect the base station receiver. For the frequency range above 690 MHz (according to ETSI EN 301 489-50 [28]), the EMC RF electromagnetic field immunity requirement with a level of 10 V/m applies on the non-radiating faces of the *BS type 1-O* or *BS type 2-O*, as depicted on figure 9.2.2-1. + +NOTE: Depending on the BS implementation, application of the spatial exclusion to all radiating faces of the BS may not allow proper execution of the RI testing. In such cases, to protect the *BS type 1-O* or *BS type 2-O* receiver(s), exclusion bands shall be considered, as in table 4.4.2-1. + +![Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for BS type 1-O and BS type 2-O. The diagram shows a dashed rectangular box representing the 'Spatial exclusion zone'. Inside this zone, a semi-circular shape represents the 'EUT' (Equipment Under Test). Arrows indicate the 'RI testing direction' from the top and bottom, pointing towards the EUT. A horizontal arrow pointing to the right is labeled 'EUT radiating direction'.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for BS type 1-O and BS type 2-O. The diagram shows a dashed rectangular box representing the 'Spatial exclusion zone'. Inside this zone, a semi-circular shape represents the 'EUT' (Equipment Under Test). Arrows indicate the 'RI testing direction' from the top and bottom, pointing towards the EUT. A horizontal arrow pointing to the right is labeled 'EUT radiating direction'. + +Figure 9.2.2-1: EMC RF electromagnetic field immunity requirement testing directions for *BS type 1-O* and *BS type 2-O* (horizontal plane depicted) with the *spatial exclusion zone* applied + +### 9.2.3 Performance criteria + +#### Base station: + +The performance criteria of clause 6.1 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.3 shall apply. + +## 9.3 Electrostatic discharge + +The test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.3.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the event of an electrostatic discharge. + +### 9.3.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-2 [17]: + +- for contact discharge, the equipment shall pass at $\pm 4$ kV; +- for air discharge shall pass at $\pm 8$ kV; +- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures. + +NOTE: Ensure that the EUT is fully discharged between each ESD exposure. + +### 9.3.3 Performance criteria + +#### Base station: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. + +## 9.4 Fast transients common mode + +The test shall be performed on AC mains power input ports. + +This test shall be performed on *signal ports*, *telecommunication ports*, *control ports* and DC power input/output ports if the cables may be longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares in EMCD.1 (see table 4.6-1) that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.4.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the event of fast transients present on one of the input/output ports. + +### 9.4.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-4 [19]: + +- The test level for *signal ports*, *telecommunication ports* and *control ports* shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [19]; +- The test level for DC power input/output ports shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [19]; +- The test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [19]. + +For AC and DC power input ports the transients shall be applied (in parallel) to all the conductors in the cable with reference to the cabinet reference earth (true common mode) and the source impedance shall be 50 $\Omega$ . + +### 9.4.3 Performance criteria + +#### Base station: + +The performance criteria of clause 6.2 shall apply. + +#### **Ancillary equipment:** + +The performance criteria of clause 6.4 shall apply. + +## 9.5 RF common mode (0.15 MHz - 80 MHz) + +The test shall be performed on AC mains power input/output ports. + +This test shall be performed on *signal ports*, telecommunication *ports*, control and DC power input/output ports, which may have cables longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares in EMCD.1 (see table 4.6-1) that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [21]. + +### 9.5.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the presence of a radio frequency electromagnetic disturbance. + +### 9.5.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-6 [21]: + +- The test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1% frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz; +- The test level shall be severity level 2 as given in IEC 61000-4-6 [21] corresponding to 3 V rms, at a transfer impedance of 150 Ω; +- The test shall be performed over the frequency range 150 kHz - 80 MHz; +- The injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [21]; +- Responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies of the immunity test signal selected and used during the test shall be recorded in the test report. + +### 9.5.3 Performance criteria + +#### **Base station:** + +The performance criteria of clause 6.1 shall apply. + +#### **Ancillary equipment:** + +The performance criteria of clause 6.3 shall apply. + +## 9.6 Voltage dips and interruptions + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.6.1 Definition + +These tests assess the ability of radio equipment and *ancillary equipment* to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports. + +### 9.6.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-11 [22], where the test levels shall be: + +- Voltage dip: 0 % residual voltage for 0.5 cycle; +- Voltage dip: 0 % residual voltage for 1 cycle; +- Voltage dip: 70 % residual voltage for 25/30 cycles (at 50/60 Hz); +- Voltage interruption: 0 % residual voltage for 250/300 cycles (at 50/60 Hz). + +### 9.6.3 Performance criteria + +For a 0 % residual voltage dip test, the performance criteria for transient phenomena shall be applied: + +- Criteria 6.2 for base station +- Criteria 6.4 for *ancillary equipment* + +For a 70% residual voltage dip test and for voltage interruption test, the following applies: + +1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied: + - Criteria 6.2 for base station + - Criteria 6.4 for *ancillary equipment* +2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator: + - No unintentional responses shall occur at the end of the test, when the voltage is restored to nominal + - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report. + +## 9.7 Surges, common and differential mode + +The tests shall be performed on AC mains power input ports. + +This test shall be additionally performed on *telecommunication ports*. + +These tests shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.7.1 Definition + +These tests assess the ability of radio equipment and *ancillary equipment* to operate as intended in the event of surges being present at the AC mains power input ports and *telecommunication ports*. + +### 9.7.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-5 [20]. + +The requirements and evaluation of test results given in clause 9.7.2.1 (*telecommunication ports*, outdoor cables), clause 9.7.2.2 (*telecommunication ports*, indoor cables) and clause 9.7.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT. + +#### 9.7.2.1 Test method for telecommunication ports directly connected to outdoor cables + +The test level for *telecommunications ports*, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [20]. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [20]. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [20]. + +#### 9.7.2.2 Test method for telecommunication ports connected to indoor cables + +The test level for telecommunication *ports*, intended to be connected to indoor cables (longer than 10 m) shall be 0.5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [20]. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [20]. + +#### 9.7.2.3 Test method for AC power ports + +The test level for AC power input *ports* shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [20]. + +In telecommunication centres 1 kV line to ground and 0.5 kV line to line shall be used. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [20]. + +### 9.7.3 Performance criteria + +#### Base station: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-08 | RAN4#84 | R4-1708861 | | | | Specification Skeleton | 0.0.1 | +| 2017-10 | RAN4#84 bis | R4-1711984 | | | | Capture TPs approved in RAN4#84bis:
R4-1711815, "Draft TS 38.113 v0.0.1"
R4-1711828, "TP to TS 38.113: antenna ports for EMC"
R4-1711829, "TP to TS 38.113 Section 2 (References)"
R4-1711830, "TP to TS 38.113 Section 3 (Definitions, symbols and abbreviations)"
R4-1711831, "TP to TS 38.113 Section 7 (Applicability Overview)"
R4-1711832, "TP to TS 38.113 Section 8 (Emission)"
R4-1711833, "TP to TS 38.113 Section 9 (Immunity)" | 0.0.2 | +| 2017-12 | RAN4#85 | R4-1714545 | | | | Capture TPs approved in RAN4#85:
R4-1714297, "TP to TS 38.113 ESD test level"
R4-1714299, "TP to TS 38.113 section 2, 3 and 7"
R4-1714429, "TP to Section 4.4 in TS 38.113 (NR) Receiver exclusion bands (radiated immunity)"
R4-1714301, "TP to Section 8.2 (Radiated Emission Limits) of TS 38.113"
R4-1712749, "TP for TS 38.113 introduction of band n71" | 0.1.0 | +| 2017-12 | RAN#78 | RP-172420 | | | | v1.0.0 submitted for plenary approval | 1.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2018-03 | RAN#79 | RP-180264 | 0002 | | F | CR to TS 38.113
Cat.F draftCRs
R4-1801258 Draft CR to TS 38.113 Symbol(clause 3.2)
R4-1803309 [NR] DraftCR 38113 Rx exclusion (4.4.2)
R4-1803313 DraftCR to TS 38.113 subclause 5.1 and 5.4
R4-1803314 DraftCR to TS 38.113 subclause 8.2.1.2 radiated emission test method_v2
R4-1803315 DraftCR to TS 38.113 subclause 9.1.1_v3 | 15.1.0 | +| 2018-03 | RAN#79 | RP-180264 | 0003 | | B | CR to TS 38.113
Cat.B draftCRs
R4-1802055 - Draft CR to Section 6.3 in TS 38.113 (NR)
Performance criteria for continuous phenomena for Ancillary equipment
R4-1802056 - Draft CR to Section 6.4 in TS 38.113 (NR)
Performance criteria for transient phenomena for Ancillary equipment
R4-1802057 - Draft CR to Section 8.4 in TS 38.113 (NR) Test method for conducted emissions AC mains power input output port
R4-1803318 [NR] DraftCR 38113 Test conditions (4) | 15.1.0 | +| 2018-06 | RAN#80 | RP-181076 | 0004 | | F | CR to TS 38.113
Implementation of endorsed draft CRs from RAN4 #86bis and RAN4 #87 | 15.2.0 | +| 2018-09 | RAN#81 | RP-181896 | 0005 | | F | CR to TS 38.113: Implementation of endorsed draft CRs from RAN4#88 | 15.3.0 | +| 2018-12 | RAN#82 | RP-182361 | 0008 | 1 | F | CR to TS 38.113 | 15.4.0 | +| 2019-03 | RAN#83 | RP-190403 | 0009 | | F | CR to TS 38.113

Implementation of endorsed draftCRs in RAN4#90:
R4-1900565 - Draft CR to TS 38.113 subclause 9.2.2, ZTE
R4-1900566 - Draft CR to TS 38.113 subclause 9.7.2.1, ZTE
R4-1902330 - Draft CR to TS 38.113 Symbol (subclause 3 and 8.2.1), ZTE
R4-1902332 - Draft CR to TS 38.113 subclause 7.1 and 8.3.2, ZTE
R4-1902334 - Draft CR to TS 38.113 Exclusion Bands for Radiated Immunity Test, Ericsson
R4-1902340 - Draft CR to TS 38.113 on FR1 and FR2 definitions, Ericsson
R4-1902331 - draft CR to 38.113 - NR BS EMC_v1, Nokia | 15.5.0 | +| 2019-06 | RAN#84 | RP-191240 | 0011 | | F | CR to TS 38.113

Endorsed draft CRs in RAN4#90Bis:
R4-1903562 Draft CR to TS 38.113 subclause 4.5
R4-1903636 - Draft CR to TS 38.113 Addition of NR to the scope
R4-1905151 [EMC] CR 38.113 editorials
R4-1905152 - Draft CR to TS 38.113 Correction reference TR 38.817-2
R4-1905154 [EMC] CR 38.113 exclusion updates, R15

Endorsed draft CRs in RAN4#91:
R4-1907703 Draft CR to TS 38.113 (subclause 3.2.3,3.4.4.2)
R4-1907705 Draft CR to TS 38.113 (subclause 8.2.1) | 15.6.0 | +| 2019-09 | RAN#85 | RP-192046 | 0012 | | F | CR to 38.113 Editorial Corrections | 15.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------|---------| +| 2019-12 | RAN#86 | RP-193036 | 0014 | 2 | F | CR to TS 38.113 Correction on abbreviations(subclause 3.3 & 8.2.1.2) | 15.8.0 | +| 2019-12 | RAN#86 | RP-193036 | 0015 | 2 | F | CR to TS 38.113 Correction on definitions subclause 3.1 | 15.8.0 | +| 2019-12 | RAN#86 | RP-193036 | 0016 | 2 | F | CR to TS 38.113 Editorial Corrections(clause 2 & subclause 3.1) r1 | 15.8.0 | +| 2020-03 | RAN#87 | RP-200399 | 0017 | 1 | F | CR to TS 38.113 Add the transmitter exclusion band for NR BS(subclause 4.4.1) | 15.9.0 | +| 2020-06 | RAN#88 | RP-200986 | 0020 | 1 | F | [R15]CR to TS 38.113 Add the reverberation chamber for radiated immunity testing (clause 2) | 15.10.0 | +| 2020-07 | RAN#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2020-09 | RAN#89 | RP-201512 | 0022 | | A | CR to TS 38.113: direct field strength measurements for the EMC RE, Rel-16 | 16.1.0 | +| 2020-12 | RAN#90 | RP-202488 | 0030 | | A | CR to TS 38.113: correction of the scope and other technical improvements, Rel-16 | 16.2.0 | +| 2020-12 | RAN#90 | RP-202489 | 0024 | 1 | A | CR to TS 38.113 on Voltage dips and interruptions, Release 16 | 16.2.0 | +| 2021-03 | RAN#91 | RP-210117 | 0036 | | A | CR to TS 38.113: Radiated emission test method | 16.3.0 | +| 2021-06 | RAN#92 | RP-211086 | 0038 | | A | CR to TS 38.113: Radiated emission, ancillary equipment | 16.4.0 | +| 2021-06 | RAN#92 | RP-211081 | 0040 | 1 | A | CR to TS 38.113 on Performance criteria for transient phenomena, Release 16 | 16.4.0 | +| 2021-09 | RAN#93 | RP-211922 | 0044 | | A | Big CR for TS 38.113 Maintenance (Rel-16, CAT A) | 16.5.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Update to Rel-17 version (MCC) | 17.0.0 | +| 2022-06 | RAN#96 | RP-221655 | 0050 | | A | Big CR for TS 38.113 Maintenance (Rel-17, CAT A) | 17.1.0 | +| 2022-09 | RAN#97 | RP-222023 | 0053 | | F | Big CR for TS 38.113 Maintenance (Rel-17, CAT F) | 17.2.0 | +| 2023-03 | RAN#99 | RP-230505 | 0056 | | A | TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity | 17.3.0 | +| 2023-06 | RAN#100 | RP-231358 | 0058 | 1 | F | CR on TS 38.113 NR BS performance criteria | 17.4.0 | +| 2023-09 | RAN#101 | RP-232502 | 0062 | | A | [NR_newRAT-Core] CR on TS 38.113 NR BS reference maintenance R17 | 17.5.0 | + +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +|---------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------|-------------| +| 2023-09 | RAN#101 | RP-232515 | 0059 | | B | CR to TS 38.113 on introduction of 3 MHz channel bandwidth in clause 6.1 | 18.0.0 | +| 2023-12 | RAN#102 | RP-233372 | 0069 | 1 | F | [NR_newRAT-Perf, TE18] CR to TS 38.113: framework for the EMC-specific manufacturer's declarations, Rel-18 | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38114/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-18/38_series/38114/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f516cb165cc91c6e7456910dc5bdfaeb05f9273 --- /dev/null +++ b/marked/Rel-18/38_series/38114/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3632d714a87d41be350ef9cef4a79165f3abf31126db9132047b5c3a782d549 +size 41582 diff --git a/marked/Rel-18/38_series/38114/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-18/38_series/38114/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2a01901174204bd2be48e1c110d8947ef635d97 --- /dev/null +++ b/marked/Rel-18/38_series/38114/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f55fa0ef662f28181c1e7ddd54e204274d1c802afcb599b9c04bf5e600fa8c +size 20816 diff --git a/marked/Rel-18/38_series/38114/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/38_series/38114/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c75767d0eeb5372b80d0014c5068295b9877eb74 --- /dev/null +++ b/marked/Rel-18/38_series/38114/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72d16569cf78df5e861a0aab6ccdd388e03040012ed08b42500707d4086acf02 +size 79082 diff --git a/marked/Rel-18/38_series/38114/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/38_series/38114/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cc0063589a1fe9064d9ec750a90cadd8fbedf63 --- /dev/null +++ b/marked/Rel-18/38_series/38114/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bca0357f1cf8021d8dfbcecaeda12a0a29b0e5af4c4b4dd4df4b1ceb5fe4be3c +size 81993 diff --git a/marked/Rel-18/38_series/38114/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38114/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6c44bb09d6c948d50b7998c8d46a05e71840d86 --- /dev/null +++ b/marked/Rel-18/38_series/38114/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c672674158c1a57a403d6add5988ae8de54e6ee09a385a3506d650ae3a9f65c +size 9644 diff --git a/marked/Rel-18/38_series/38114/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38114/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08a7eabf42c18eaa3f16072fe26b440a8e343b42 --- /dev/null +++ b/marked/Rel-18/38_series/38114/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32b15fffdbdae1ac01f32ba642de4290b4d86fb22b052650cb016d569da76242 +size 5125 diff --git a/marked/Rel-18/38_series/38114/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-18/38_series/38114/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe4f0e382f1c7d78c3cabf2020c4ae368ef0c48c --- /dev/null +++ b/marked/Rel-18/38_series/38114/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d66d8d029cd2e98ba6cbc075ac9cf0064673584972104cee7e050dd04077a8fb +size 20464 diff --git a/marked/Rel-18/38_series/38114/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/38_series/38114/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..612a80335bacaff4869f16400adff35714ece7c5 --- /dev/null +++ b/marked/Rel-18/38_series/38114/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c81ca14d0087d251e7e4de7f877f31f9091e79de7014c1a29f7a7803a285182 +size 17853 diff --git a/marked/Rel-18/38_series/38114/f1fbb1287d999c7034742de35bdab836_img.jpg b/marked/Rel-18/38_series/38114/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7979061a02d3d2fde289c32b8ead0e67371276ca --- /dev/null +++ b/marked/Rel-18/38_series/38114/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:889c35077f5ddbbd33b2f185616e41ace4de6773f335a3f57ab1d28508c8360b +size 28481 diff --git a/marked/Rel-18/38_series/38114/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Rel-18/38_series/38114/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d098cda20767483e206a9a426fd6af7a66d5cac8 --- /dev/null +++ b/marked/Rel-18/38_series/38114/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f32bceb356fb79c8a726fd7880617fe264f17cd77f140978282d3ec4a53882 +size 29351 diff --git a/marked/Rel-18/38_series/38114/raw.md b/marked/Rel-18/38_series/38114/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..81db2543384ca2da22f48310f3e69a8b36f6cc9a --- /dev/null +++ b/marked/Rel-18/38_series/38114/raw.md @@ -0,0 +1,1085 @@ + + +# 3GPP TS 38.114 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Repeaters ElectroMagnetic Compatibility (EMC) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## --- **Keywords** + +<> + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +--- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations ..... | 13 | +| 4 Test conditions ..... | 14 | +| 4.1 General ..... | 14 | +| 4.2 Arrangements for establishing a communication link..... | 14 | +| 4.3 Narrow band responses ..... | 14 | +| 4.4 Exclusion bands..... | 15 | +| 4.5 NR repeaters test configurations ..... | 15 | +| 5 Performance assessment ..... | 16 | +| 5.1 General ..... | 16 | +| 5.2 NR repeaters..... | 17 | +| 5.3 Ancillary equipment..... | 17 | +| 6 Performance criteria..... | 17 | +| 6.1 Performance criteria for continuous phenomena for NR repeaters..... | 17 | +| 6.2 Performance criteria for transient phenomena for NR repeaters..... | 17 | +| 6.3 Performance criteria for continuous phenomena for Ancillary equipment..... | 17 | +| 6.4 Performance criteria for transient phenomena for Ancillary equipment..... | 17 | +| 7 Applicability overview..... | 18 | +| 7.0 General ..... | 18 | +| 7.1 Emission..... | 18 | +| 7.2 Immunity ..... | 19 | +| 8 Emission..... | 19 | +| 8.1 Test configurations..... | 19 | +| 8.2 Radiated emission ..... | 20 | +| 8.2.1 Radiated emission, Repeater ..... | 20 | +| 8.2.1.1 Definition ..... | 20 | +| 8.2.1.2 Test method..... | 20 | +| 8.2.1.3 Limits ..... | 21 | +| 8.2.1.4 Interpretation of the measurement results..... | 21 | +| 8.2.2 Radiated emission, ancillary equipment..... | 22 | +| 8.2.2.1 Definition ..... | 22 | +| 8.2.2.2 Test method..... | 22 | +| 8.2.2.3 Limits ..... | 22 | +| 8.3 Conducted emission DC power input/output port..... | 23 | +| 8.3.1 Definition..... | 23 | +| 8.3.2 Test method ..... | 23 | +| 8.3.3 Limits..... | 23 | +| 8.4 Conducted emissions, AC mains power input/output port..... | 23 | +| 8.4.1 Definition..... | 23 | +| 8.4.2 Test method ..... | 23 | +| 8.4.3 Limits..... | 23 | +| 8.5 Conducted emissions, telecommunication port..... | 24 | +| 8.5.1 Definition..... | 24 | +| 8.5.2 Test method ..... | 24 | +| 8.5.3 Limits..... | 24 | +| 8.6 Harmonic Current emissions (AC mains input port) ..... | 24 | +| 8.7 Voltage fluctuations and flicker (AC mains input port)..... | 24 | +| 9 Immunity ..... | 24 | +| 9.1 Test configurations..... | 24 | + +| | | | +|--------------------------------------------|------------------------------------------------------------------------------------|----| +| 9.2 | RF electromagnetic field (80 MHz - 6000 MHz)..... | 25 | +| 9.2.1 | Definition..... | 26 | +| 9.2.2 | Test method and level..... | 26 | +| 9.2.3 | Performance criteria ..... | 27 | +| 9.3 | Electrostatic discharge..... | 27 | +| 9.3.1 | Definition..... | 27 | +| 9.3.2 | Test method and level..... | 27 | +| 9.3.3 | Performance criteria ..... | 27 | +| 9.4 | Fast transients common mode..... | 27 | +| 9.4.1 | Definition..... | 27 | +| 9.4.2 | Test method and level..... | 27 | +| 9.4.3 | Performance criteria ..... | 28 | +| 9.5 | RF common mode (0.15 MHz - 80 MHz)..... | 28 | +| 9.5.1 | Definition..... | 28 | +| 9.5.2 | Test method and level..... | 28 | +| 9.5.3 | Performance criteria ..... | 28 | +| 9.6 | Voltage dips and interruptions ..... | 29 | +| 9.6.1 | Definition..... | 29 | +| 9.6.2 | Test method and level..... | 29 | +| 9.6.3 | Performance criteria ..... | 29 | +| 9.7 | Surges, common and differential mode..... | 29 | +| 9.7.1 | Definition..... | 30 | +| 9.7.2 | Test method and level..... | 30 | +| 9.7.2.1 | Test method for telecommunication ports directly connected to outdoor cables ..... | 30 | +| 9.7.2.2 | Test method for telecommunication ports connected to indoor cables..... | 30 | +| 9.7.2.3 | Test method for AC power ports ..... | 30 | +| 9.7.3 | Performance criteria ..... | 30 | +| Annex A (informative): Change history..... | | 31 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document covers the assessment of NR repeater, network-controlled repeater and ancillary equipment in respect of Electromagnetic Compatibility (EMC). For network-controlled repeater (NCR), requirements for NCR-Fwd and NCR-MT apply. + +The present document specifies the applicable requirements, procedures, test conditions, performance assessment and performance criteria for NR repeater, NCR and associated ancillary equipment in the following categories: + +- NR repeater equipped with antenna connectors which are possible to be terminated during EMC testing, meeting the *repeater type 1-C* RF requirements of TS 38.106 [2], with conformance demonstrated by compliance to TS 38.115-1 [3]. +- NR repeater not equipped with antenna connectors, i.e. with antenna elements radiating during the EMC testing, meeting the *repeater type 2-O* RF requirements of TS 38.106 [2], with conformance demonstrated by compliance to TS 38.115-2 [4]. +- NCR equipped with antenna connectors or TAB connectors which are possible to be terminated during EMC testing, meeting the NCR-Fwd/MT type 1-C and type 1-H RF requirements of TS 38.106 [2], with conformance demonstrated by compliance to TS 38.115-1 [3]. +- NCR not equipped with antenna connectors, i.e. with antenna elements radiating during the EMC testing, meeting the NCR-Fwd/MT type 2-O RF requirements of TS 38.106 [2], with conformance demonstrated by compliance to TS 38.115-2 [4]. + +The environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [6], IEC 61000-6-3 [7] and IEC 61000-6-8 [24]. + +The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" +- [2] 3GPP TS 38.106: "NR Repeater Radio Transmission and Reception" +- [3] 3GPP TS 38.115-1: "NR; Repeater conformance testing - Part 1: Conducted conformance testing" +- [4] 3GPP TS 38.115-2: "NR; Repeater conformance testing - Part 1: Radiated conformance testing" +- [5] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements". +- [6] IEC 61000-6-1: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards - Immunity for residential, commercial and light-industrial environments". +- [7] IEC 61000-6-3: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards - Emission standard for equipment in residential environments". + +- [8] IEC 61000-3-2: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current $\leq 16$ A per phase)". +- [9] IEC 61000-3-3: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems, for equipment with rated current $\leq 16$ A per phase and not subject to conditional connection". +- [10] IEC 61000-3-11: "Electromagnetic compatibility (EMC) - Part 3-11: Limits – Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems - Equipment with rated current $\leq 75$ A and subject to conditional connections". +- [11] IEC 61000-3-12: "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic currents produced by equipment connected to public low-voltage system with input current $>16$ A and $\leq 75$ A per phase". +- [12] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test". +- [13] IEC 61000-4-3:2006+AMD1:2007+AMD2:2010 CSV: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test". +- [14] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4-4: Testing and measurement techniques - Electrical fast transient/burst immunity test". +- [15] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test". +- [16] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances, induced by radio frequency fields". +- [17] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations immunity tests". +- [18] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods". +- [19] ITU-R SM.329: "Unwanted emissions in the spurious domain". +- [20] IEC 60050-161: "International Electrotechnical Vocabulary - Chapter 161: Electromagnetic compatibility". +- [21] ETSI EN 301 489-1: "Electromagnetic Compatibility (EMC) standard for radio equipment and services - Part 1: Common technical requirements - Harmonised Standard for Electromagnetic Compatibility". +- [22] ETSI EN 301 489-50: "Electromagnetic compatibility (EMC) standard for radio equipment and services; Part 50: Specific conditions for cellular communication base station (BS), repeater and ancillary equipment; Harmonised standard covering the essential requirements of article 3.1(b) of the Directive 2014/53/EU". +- [23] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [24] IEC 61000-6-8: "Electromagnetic compatibility (EMC) - Part 6-8: Generic standards - Emission standard for professional equipment in commercial and light-industrial locations". +- [25] CISPR 16-1-4: "Specification for radio disturbance and immunity measuring apparatus and methods - Part 1-4: Radio disturbance and immunity measuring apparatus - Antennas and test sites for radiated disturbance measurements". +- [26] ITU-R SM.1539-1: "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329". + +- [27] CISPR 16-4-2 : "Specification for radio disturbance and immunity measuring apparatus and methods - Part 4-2: Uncertainties, statistics and limit modelling - Measurement instrumentation uncertainty". +- [28] ETSI TR 100 028-1: "Electromagnetic Compatibility and Radio Spectrum Matters (ERM); Uncertainties in the Measurement of Mobile Radio Equipment Characteristics; Part 1". +- [29] 3GPP TR 38.867: "Study on NR network-controlled repeaters". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**ancillary equipment:** electrical or electronic equipment, that is intended to be used with a receiver or transmitter + +NOTE: It is considered as an ancillary equipment if: + +the equipment is intended for use with a receiver or transmitter to provide additional operational and/or control features to the radio equipment, (e.g. to extend control to another position or location); and + +the equipment cannot be used on a stand alone basis to provide user functions independently of a receiver or transmitter; and + +the receiver or transmitter, to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions). + +**antenna port:** for EMC purposes, port for connection of an antenna used for intentional transmission and/or reception of radiated RF energy, equivalent to an RF antenna connector. + +**channel bandwidth:** the RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The *channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**continuous phenomena:** electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [20]). + +**exclusion band:** frequency range(s) not subject to test or assessment. + +**multi-band repeater:** *Repeater Type 1-C* whose *antenna connector* is associated with a transmitter and/or receiver that is characterized by the ability to process two or more *passband(s)* in common active RF components simultaneously, where at least one *passband* is configured at a different operating band than the other *passband(s)* and where this different operating band is not a sub-band or superseding-band of another supported operating band + +**NCR-MT:** the NCR-MT is defined as a function entity to communicate with a gNB via a Control link (C-link) to enable exchange of control information (e.g. side control information at least for the control of NCR-Fwd). The C-link is based on NR Uu interface. + +**NCR-Fwd:** the NCR-Fwd is defined as a function entity to perform the amplify-and-forwarding of UL/DL RF signal between gNB and UE via backhaul link and access link. The behavior of the NCR-Fwd will be controlled according to the received side control information from gNB. + +![Figure 3.1-1: Conceptual model of network-controlled repeater. The diagram shows a gNB (base station) connected to a Network-controlled repeater (NCR). The NCR is divided into two main components: NCR-MT (Mobile termination) and NCR-Fwd (Forwarding). A 'Control link' is shown between the gNB and the NCR-MT. A 'Backhaul link' is shown between the gNB and the NCR-Fwd. An 'Access link' is shown between the NCR-Fwd and a UE (User Equipment).](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 3.1-1: Conceptual model of network-controlled repeater. The diagram shows a gNB (base station) connected to a Network-controlled repeater (NCR). The NCR is divided into two main components: NCR-MT (Mobile termination) and NCR-Fwd (Forwarding). A 'Control link' is shown between the gNB and the NCR-MT. A 'Backhaul link' is shown between the gNB and the NCR-Fwd. An 'Access link' is shown between the NCR-Fwd and a UE (User Equipment). + +**Figure 3.1-1: Conceptual model of network-controlled repeater** + +**NCR type 1-C:** network-controlled repeater including both NCR-MT and NCR-Fwd operating at FR1 with requirements set consisting only of conducted requirements defined at individual antenna connectors. + +![Figure 3.1-2: NCR type 1-C downlink and uplink interface. The diagram shows the internal structure of the NCR. It is divided into two main sections: Mobile Termination (MT) and Forwarding (Fwd). The MT section contains a 'Radio Transceiver'. The Fwd section contains a 'Downlink' path (indicated by a right-pointing arrow) and an 'Uplink' path (indicated by a left-pointing arrow). The MT section is connected to the Fwd section via a 'BS-side antenna connector'. The Fwd section is connected to the UE via a 'UE-side antenna connector'.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +Figure 3.1-2: NCR type 1-C downlink and uplink interface. The diagram shows the internal structure of the NCR. It is divided into two main sections: Mobile Termination (MT) and Forwarding (Fwd). The MT section contains a 'Radio Transceiver'. The Fwd section contains a 'Downlink' path (indicated by a right-pointing arrow) and an 'Uplink' path (indicated by a left-pointing arrow). The MT section is connected to the Fwd section via a 'BS-side antenna connector'. The Fwd section is connected to the UE via a 'UE-side antenna connector'. + +**Figure 3.1-2: NCR type 1-C downlink and uplink interface** + +NOTE 1: the NCR-MT and NCR-Fwd may have the same or separate antenna connectors + +**NCR type 1-H:** network-controlled repeater including both NCR-MT and NCR-Fwd operating at FR1 with a requirement set consisting of conducted requirements defined at individual TAB connectors and OTA requirements defined at RIB. + +![Diagram of NCR type 1-H downlink and uplink interface showing BS-side and UE-side composite antennas connected via TABC to an NCR-MT and NCR-Fwd unit.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the NCR type 1-H downlink and uplink interface. It is divided into two main sections: BS-side and UE-side, separated by a central NCR unit. On the BS-side, a 'Composite antenna' (consisting of a 'Radio Distribution network (RDN)' and an 'Antenna Array (AA)') is connected to a 'BS-side TABC'. This TABC is connected to a 'Mobile Termination (MT)' which contains a 'Radio Transceiver Unit array (TRXUA)'. On the UE-side, another 'Composite antenna' (also with 'RDN' and 'AA') is connected to a 'UE-side TABC', which is connected to the same 'Mobile Termination (MT)'. The 'MT' is connected to a 'Forwarding (Fwd)' unit. This unit has two internal components: a 'Downlink' component (represented by a right-pointing triangle) and an 'Uplink' component (represented by a left-pointing triangle). The 'Downlink' component receives signals from the 'MT' and sends them to the 'UE-side TABC'. The 'Uplink' component receives signals from the 'UE-side TABC' and sends them to the 'MT'. The 'BS-side TABC' and 'UE-side TABC' are connected to the 'MT' via multiple lines, representing multiple TAB connectors. The 'BS-side RIB' (Radio Interface Boundary) is indicated at the far left, and the 'UE-side RIB' is indicated at the far right. + +Diagram of NCR type 1-H downlink and uplink interface showing BS-side and UE-side composite antennas connected via TABC to an NCR-MT and NCR-Fwd unit. + +Figure 3.1-3: NCR type 1-H downlink and uplink interface + +NOTE 1: the NCR-MT and NCR-Fwd may have the same or separate TAB connectors. + +**NCR type 2-O:** network-controlled repeater including both NCR-MT and NCR-Fwd operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB. + +![Figure 3.1-4: NCR type 2-O downlink and uplink interface diagram. The diagram shows a Mobile Termination (MT) containing a Radio Transceiver Unit array (TRXUA). Below the TRXUA is a 'Forwarding (Fwd)' unit with two triangles representing signal flow. An arrow labeled 'Downlink' points from the TRXUA through the Forwarding unit to the right. An arrow labeled 'Uplink' points from the right back through the Forwarding unit to the TRXUA. On the left, a 'Composite antenna' block contains a 'Radio Distribution network (RDN)' and an 'Antenna Array (AA)'. It is connected to the TRXUA and the Forwarding unit. On the right, another 'Composite antenna' block, also containing an RDN and an AA, is connected to the Forwarding unit. The left side is labeled 'BS-side RIB' and the right side is labeled 'UE-side RIB'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 3.1-4: NCR type 2-O downlink and uplink interface diagram. The diagram shows a Mobile Termination (MT) containing a Radio Transceiver Unit array (TRXUA). Below the TRXUA is a 'Forwarding (Fwd)' unit with two triangles representing signal flow. An arrow labeled 'Downlink' points from the TRXUA through the Forwarding unit to the right. An arrow labeled 'Uplink' points from the right back through the Forwarding unit to the TRXUA. On the left, a 'Composite antenna' block contains a 'Radio Distribution network (RDN)' and an 'Antenna Array (AA)'. It is connected to the TRXUA and the Forwarding unit. On the right, another 'Composite antenna' block, also containing an RDN and an AA, is connected to the Forwarding unit. The left side is labeled 'BS-side RIB' and the right side is labeled 'UE-side RIB'. + +**Figure 3.1-4: NCR type 2-O downlink and uplink interface** + +NOTE 1: the NCR-MT and NCR-Fwd may have the same or separate RIB. + +**operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements. + +**passband edge:** Frequency at the edge of the passband. + +**port:** A particular interface, of the specified equipment (apparatus), with the electromagnetic environment. For example, any connection point on an equipment intended for connection of cables to or from that equipment is considered as a port (see Figure 3.1-1). + +![Figure 3.1-5: Examples of ports diagram. A central box labeled 'Apparatus' is shown within a larger box labeled 'Enclosure Port'. On the left side of the Apparatus box, three ports are listed: 'AC power port', 'DC power port', and 'Earth port'. On the right side of the Apparatus box, three ports are listed: 'Antenna port', 'Signal/control port', and 'Telecommunication port'.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +Figure 3.1-5: Examples of ports diagram. A central box labeled 'Apparatus' is shown within a larger box labeled 'Enclosure Port'. On the left side of the Apparatus box, three ports are listed: 'AC power port', 'DC power port', and 'Earth port'. On the right side of the Apparatus box, three ports are listed: 'Antenna port', 'Signal/control port', and 'Telecommunication port'. + +**Figure 3.1-5: Examples of ports** + +**repeater type 1-C:** Repeater operating at FR1 with a requirement set consisting only of conducted requirements defined at individual *antenna connectors*. + +**repeater type 2-O:** Repeater operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB. + +**radiated interface boundary:** *operating band* specific radiated requirements reference where the radiated requirements apply. + +**signal/control port:** port intended for the interconnection of components of an EUT, or between an EUT and associated equipment and used in accordance with relevant functional specifications (for example for the maximum length of cable connected to it). + +**single-band connector:** *Repeater type 1-C antenna connector* supporting operation either in a single *operating band* only, or in multiple *operating bands* but does not meet the conditions for a *multi-band connector* + +**spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *repeater type 2-O* (i.e. half sphere around the EUT's radiating direction). + +**telecommunication port:** ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks. + +NOTE: *Telecommunication port* is called "wired network port" in CISPR 32 [5] and ETSI EN 301 489-1 [21]. + +**transient phenomena:** pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [20]). + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|--------------------------|---------------------------------------------------------------------| +| BW Channel | Channel bandwidth | +| P rated,p,AC | Rated passband output power per antenna connector | +| P rated,p,TRP | Rated passband TRP output power declared per RIB | +| P max,p,AC | Maximum passband output power measured per antenna connector | +| P max,p,TRP | Maximum passband TRP output power measured per RIB | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|---------|-------------------------------| +| AC | Alternating Current | +| AMN | Artificial Mains Network | +| CDN | Coupling/Decoupling Network | +| C-link | Control link | +| DC | Direct Current | +| EMC | Electromagnetic Compatibility | +| EUT | Equipment Under Test | +| FR | Frequency Range | +| NCR | Network-controlled repeater | +| NCR-MT | NCR-Mobile termination | +| NCR-Fwd | NCR-Forwarding | +| NR | New Radio | +| RF | Radio Frequency | +| rms | root mean square | + +# 4 Test conditions + +## 4.1 General + +Requirements throughout the EMC specifications are in some cases defined separately for different frequency ranges (FR). The frequency ranges FR1 and FR2 are defined in clause 5.1 of TS 38.106 [2]. NR Repeater is designed to operate in FR1 and FR2-1. + +The equipment shall be tested in normal test environment defined in the corresponding NR Repeater conformance testing specification TS 38.115-1 [3] for *NR Repeater type 1-C* or TS 38.115-2 [4] for *NR Repeater type 2-O*. The test conditions shall be recorded in the test report. + +For Repeater capable of multi-band operation, the requirements in the present document apply for each supported *operating band* unless otherwise stated. *Operating bands* shall be activated according to the test configuration in clause 4.5. Tests shall be performed relating to each type of port and all *operating bands* shall be assessed during the tests. + +The manufacturer shall declare the supported *operating band(s)* according to the list of NR repeater *operating bands* defined in TS 38.106 [2]. + +NOTE 1: NR *operating bands* for *repeater type 1-C*, are declared by the manufacturer according to the declaration D.2 specified in TS 38.115-1 [3], table 4.6-1. + +NOTE 2: NR *operating bands* for *repeater type 2-O*, are declared by the manufacturer according to the declaration D.4 specified in TS 38.115-2 [4], table 4.6-1. + +## 4.2 Arrangements for establishing a communication link + +The wanted RF input signal nominal frequency shall be selected by setting the NR Absolute Radio Frequency Channel Number (NR-ARFCN) to an appropriate number, as defined in TS 38.106 [2], clause 5.3.1.2. + +A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called "the test system") at the radio interface and *telecommunication port(s)* (the BS interface). The test system shall be located outside of the test environment. + +When the EUT is required to be in the uplink/downlink operation, the following conditions shall be met: + +- For the *repeater type 1-C*, the EUT shall be commanded to operate at maximum rated output power; +- For the *repeater type 2-O* testing, the EUT output power shall be configured as stated in clause 8.1 for emission test and clause 9.1 for immunity test accordingly; +- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment; + +For immunity tests clause 4.3 shall apply and the conditions shall be as follows. + +## 4.3 Narrow band responses + +Responses on uplink or downlink occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method: + +- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by $2 \times BW_{\text{Channel}}$ MHz, where $BW_{\text{Channel}}$ is the channel bandwidth as defined in TS 38.106 [2], clause 5.3; +- if the deviation disappears in either one or both of the above MHz offset cases, then the response is considered as a narrow band response; +- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to $2.5 \times BW_{\text{Channel}}$ MHz; +- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test. + +For immunity test narrow band responses are disregarded. + +For EUT capable of multi-band operation, all supported *operating bands* shall be considered for narrowband responses. + +## 4.4 Exclusion bands + +The *exclusion band* for NR repeater is the frequency range over which no tests of radiated immunity are made in UL or DL. + +The *exclusion band* for DL is defined as: + +$$F_{DL,low} - \Delta f_{OBUE} < f < F_{DL,high} + \Delta f_{OBUE}$$ + +Where values of $F_{DL,low}$ and $F_{DL,high}$ are defined for each *operating band* in TS 38.106 [2], clause 5.2. + +The *exclusion band* for UL is defined as: + +$$F_{UL,low} - \Delta f_{OBUE} < f < F_{UL,high} + \Delta f_{OBUE}$$ + +Where values of $F_{UL,low}$ and $F_{UL,high}$ are defined for each *operating band* in TS 38.106 [2], clause 5.2. + +For NR repeater capable of multi-band operation, the total *exclusion band* is a combination of the *exclusion bands* for each *operating band* supported by NR repeater. + +The $\Delta f_{OBUE}$ values for *Repeater type 1-C* is defined in table 4.4-1 for both DL and UL. + +**Table 4.4-1: $\Delta f_{OBUE}$ offset values for NR repeater 1-C** + +| NR repeater type | Operating band characteristics | $\Delta f_{OBUE}$ (MHz) | +|-------------------|------------------------------------------------------------------------------------------------------------------|-------------------------| +| Repeater type 1-C | $F_{UL,high} - F_{UL,low} < 100$ MHz, or
$F_{DL,high} - F_{DL,low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{UL,high} - F_{UL,low} \leq 900$ MHz
$100$ MHz $\leq F_{DL,high} - F_{DL,low} \leq 900$ MHz | 60 | + +NOTE: As the radiated immunity testing is defined in the frequency range 80 MHz to 6 GHz, there is no exclusion band defined for repeater type 2-O. + +## 4.5 NR repeaters test configurations + +The present clause defines the NR repeaters test configurations that shall be used for demonstrating conformance. A single NR repeater carrier shall be used for testing of single-carrier capable NR repeaters. + +The signal's channel bandwidth and subcarrier spacing used to build NR Test Configurations shall be selected according to table 4.7.2-1 in TS 38.115-1 [3] clause 4.7 for *NR repeaters type 1-C*, and table 4.7.2.1-1 in TS 38.115-2 [4] clause 4.7 for *NR repeaters type 2-O*. The passband frequency range declared per *operating band* in TS 38.115-1 [3] clause 4.6, and TS 38.115-2 [4] clause 4.6 shall be used. + +For other NR repeaters, the test configurations in table 4.5-1 and table 4.5-2 shall be used. The NR repeaters test configurations (RTCx) are defined in TS 38.115-1 [3], clause 4.7 for *NR repeaters type 1-C* and in TS 38.115-2 [4], clause 4.7 for *NR repeaters type 2-O*. + +**Table 4.5-1: Test configurations for NR repeaters type 1-C** + +| Repeater test case | Repeater capable of single or multiple passbands in a single band | | | Repeater capable of multi-band operation | | +|--------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------|------------------------------------------|-----------------------------------| +| | Single passband repeater | Multiple passband capable repeater with identical parameters per passband | Multiple passband capable repeater with different parameters per passband | Common connector | Separate connectors | +| Emission tests | RTC1 | RTC1, RTC2 | RTC1, RTC2 | RTC1/2 (Note 1), RTC4 | RTC1/2 (Note 1, 2), RTC4 (Note 2) | +| Immunity tests | RTC1 | RTC1, RTC2 | RTC1, RTC2 | RTC1/2 (Note 1), RTC4 | RTC1/2 (Note 1, 2), RTC4 (Note 2) | + +NOTE 1: RTC1 and/or RTC2 shall be applied in each supported operating band. +NOTE 2: For single-band operation test, other antenna connector(s) is (are) terminated. + +**Table 4.5-2: Test configurations for NR repeaters type 2-O** + +| Repeater test case | Repeater capable of single or multiple passbands in a single band | | | +|--------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------| +| | Single passband repeater | Multiple passband capable repeater with identical parameters per passband | Multiple passband capable repeater with different parameters per passband | +| Emission tests | RTC1 | RTC1, RTC2 | RTC1, RTC2 | +| Immunity tests | RTC1 | RTC1, RTC2 | RTC1, RTC2 | + +# 5 Performance assessment + +## 5.1 General + +The following information shall be recorded in or annexed to the test report: + +- The primary functions of the radio equipment to be tested during and after the EMC testing; +- The intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment; +- The method to be used to verify that a communications link is established and maintained; +- The user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress; +- The *ancillary equipment* to be combined with the radio equipment for testing (where applicable); +- The information about *ancillary equipment* intended to be used with the radio equipment; +- Information about the common and/or band-specific active RF components and other hardware blocks for a communication link in EUT capable of multi-band operation; +- An exhaustive list of ports (or RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power. + +Performance assessment of a NR repeater with multiple enclosures may be done separately, according to the manufacturer's choice. + +A communication link used by more than one *operating band*, shall be assessed on all *operating bands*. Communication link(s) and/or radio performance parameters for the *operating bands* can during the test be assessed simultaneously or separately for each band, depending on the test environment capability. + +## 5.2 NR repeaters + +The parameter used for assessment of performance of a NR repeater is the power accuracy within the operating band. + +## 5.3 Ancillary equipment + +At the manufacturer's discretion the test may be performed on the *ancillary equipment* separately or on a representative configuration of the combination of radio and *ancillary equipment*. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the *ancillary equipment* to be used with different radio equipment. + +# --- 6 Performance criteria + +## 6.1 Performance criteria for continuous phenomena for NR repeaters + +The power accuracy of the EUT shall be measured throughout the period of exposure of the phenomenon. + +For repeater type 1-C, the measured output power $P_{\max,p,AC}$ during the test shall not change from the rated passband output power $P_{\text{rated},p,AC}$ measured before the test by more than $\pm 2$ dB. + +For repeater type 2-O, the maximum passband TRP output power $P_{\max,p,TRP}$ during the test shall not change from the rated passband TRP output power $P_{\text{rated},p,TRP}$ measured before the test by more than $\pm 3$ dB. + +At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data. + +## 6.2 Performance criteria for transient phenomena for NR repeaters + +The power accuracy of the EUT shall be measured before the test and after each exposure. + +For repeater type 1-C, the measured output power $P_{\max,p,AC}$ after each exposure and after the total test shall not change from the rated passband output power $P_{\text{rated},p,AC}$ measured before the test by more than $\pm 2$ dB. + +For repeater type 2-O, the maximum passband TRP output power $P_{\max,p,TRP}$ after each exposure and after the total test shall not change from the rated passband TRP output power $P_{\text{rated},p,TRP}$ measured before the test by more than $\pm 3$ dB. + +At the conclusion of the total test comprising the series of individual exposures, the EUT shall operate as intended with no loss of user control functions or stored data. + +## 6.3 Performance criteria for continuous phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +## 6.4 Performance criteria for transient phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The + +performance level may be replaced by a permissible performance loss. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +# 7 Applicability overview + +## 7.0 General + +Throughout this specification, whenever the NCR repeater requirement is referred, its applicability shall be considered as applicable to the NCR node as a whole (i.e. NCR-Fwd and NCR-MT), irrespective of its implementation. + +## 7.1 Emission + +Table 7.1-1: Emission requirements applicability + +| Phenomenon | Application | Equipment test requirement | | | Reference clause in the present document | Reference standard | +|----------------------------------|-----------------------------------------|----------------------------------------------|-------------------------------------------------------|---------------------|------------------------------------------|---------------------------------------------------| +| | | NR repeater equipment | NCR equipment | Ancillary equipment | | | +| Radiated emission | Enclosure | applicable for NR repeater type 1-C (Note 1) | applicable for NCR type 1-C and NCR type 1-H (Note 1) | not applicable | 8.2.1 | ITU-R SM.329 [19] | +| Radiated emission | Enclosure of ancillary equipment | not applicable | not applicable | applicable | 8.2.2 | CISPR 32 [5] | +| Conducted emission | DC power input/output port | applicable | applicable | applicable | 8.3 | CISPR 32 [5] | +| Conducted emission | AC mains input/output port | applicable | applicable | applicable | 8.4 | CISPR 32 [5] | +| Conducted emission | Telecommunication port | applicable | applicable | applicable | 8.5 | CISPR 32 [5] | +| Harmonic current emissions | AC mains input port | applicable | applicable | applicable | 8.6 | IEC 61000-3-2 [8] or IEC 61000-3-12 [11] (NOTE 2) | +| Voltage fluctuations and flicker | AC mains input port | applicable | applicable | applicable | 8.7 | IEC 61000-3-3 [9] or IEC 61000-3-11 [10] (NOTE 2) | + +NOTE 1: Radiated emission requirements for NR repeater type 2-O and NCR type 2-O are described in clause 8.2.1. + +NOTE 2: Selection of the reference IEC specification is based on the rated input current of the EUT's power supply. + +## 7.2 Immunity + +Table 7.2-1: Immunity requirements applicability + +| Phenomenon | Application | Equipment test requirement | | | Reference clause in the present document | Reference standard | +|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------|---------------------|------------------------------------------|---------------------| +| | | NR repeater equipment | NCR equipment | Ancillary equipment | | | +| RF electromagnetic field (80 – 6000 MHz) | Enclosure | applicable | applicable | applicable | 9.2 | IEC 61000-4-3 [13] | +| Electrostatic discharge | Enclosure | applicable | applicable | applicable | 9.3 | IEC 61000-4-2 [12] | +| Fast transients common mode | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | applicable | 9.4 | IEC 61000-4-4 [14] | +| RF common mode 0.15 - 80 MHz | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | applicable | 9.5 | IEC 61000-4-6 [16] | +| Voltage dips and interruptions | AC mains power input ports | applicable | applicable | applicable | 9.6 | IEC 61000-4-11 [17] | +| Surges, common and differential mode | AC power input ports and telecommunications port | applicable | applicable | applicable | 9.7 | IEC 61000-4-5 [15] | + +# 8 Emission + +## 8.1 Test configurations + +This clause defines the configurations for emission tests as follows: + +- The equipment shall be tested under normal test conditions as specified in the functional standards; +- The test configuration shall be as close to normal intended use as possible; +- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of *ancillary equipment* necessary to exercise the ports; +- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- The test conditions, test configuration and mode of operation shall be recorded in the test report; +- Ports which in normal operation are connected shall be connected to an *ancillary equipment* or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the *ancillary equipment*; in case of *repeater type 1-C*, antenna ports shall be correctly terminated; +- For *repeater type 2-O* without antenna ports but intentionally radiating through the antenna array, the equipment shall be placed in a test setup suitable for the radiated power; +- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- The test arrangements for uplink and downlink of the repeater are described separately for the sake of clarity. However, where possible the test of the uplink clause and downlink clause of the EUT may be carried out simultaneously to reduce test time. + +## 8.2 Radiated emission + +### 8.2.1 Radiated emission, Repeater + +This test is applicable to *repeater type 1-C*. This test shall be performed on a representative configuration of repeater. + +For *repeater type 2-O*, the radiated emission is covered by radiated spurious emission requirement in TS 38.106 [2], conforming to the test requirement in TS 38.115-2 [4]. + +#### 8.2.1.1 Definition + +This test assesses the ability of repeater to limit unwanted emission from the *enclosure port*. + +#### 8.2.1.2 Test method + +- a) A test site fulfilling the requirements of ITU-R SM.329 [19] shall be used. The repeater shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads. One of the following two alternative measurement methods shall be used: + +- 1) Field strength method measurement + +The test method shall be in accordance with CISPR 32 [5]. The field strength measurements shall be performed on a test site that is validated according to the methods and requirements of CISPR 16-1-4 [25]. + +Unless otherwise stated, measurements are conducted at 3 m or 10 m on an open area test site (OATS) or semi anechoic chamber (SAC) for frequencies up to 1 GHz, or at 3 m on a free space open area test site (FSOATS) or fully-anechoic room (FAR) for frequencies above 1 GHz. Unless otherwise stated, all measurements are done with RMS detector and with the -3 dB bandwidth of the measuring filter equal to the reference bandwidth in table 8.2.1.3-1. + +NOTE 1: Test site validation methods for radiated emissions tests are defined in CISPR 16-1-4 [25], clause 6 and 7. Examples of test site validation methods are listed below: + +- 30 - 1000 MHz frequency range: Normalized Site Attenuation (NSA), Reference Site Method (RSM). +- 1 - 18 GHz frequency range: $S_{VSWR}$ standard test procedure, $S_{VSWR}$ reciprocal test procedure. + +- 2) Substitution method measurement (also called a substitution method) + +Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the repeater shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane. Unless otherwise stated, all measurements are done as mean power (RMS). + +NOTE 2: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2.15 dB between e.i.r.p. and e.r.p., as defined in ITU-R SM.329 annex 1 [19]. + +$$\text{e.r.p. (dBm)} = \text{EIRP (dBm)} - 2.15$$ + +- b) The repeater shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the repeater to transmit a signal as stated in clause 4.5. +- c) The received power shall be measured over the frequency range from 30 MHz to $F_{DL,low} - \Delta f_{OBUE}$ and from $F_{DL,high} + \Delta f_{OBUE}$ up to 12750 MHz. For some *operating bands*, the upper limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the downlink *operating band*, as specified in ITU-R SM.329 [19]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS). + +#### 8.2.1.3 Limits + +The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [19] and SM.1539-1 [26]. + +The *repeater type 1-C* shall meet the limits below: + +**Table 8.2.1.3-1: Limits for radiated emissions from Repeater** + +| Frequency range | e.r.p.
(dBm) | Field strength at 3 m
(dBμV/m)
(NOTE 4) | Field strength at 10 m
(dBμV/m)
(NOTE 4) | Reference
bandwidth | Notes | +|-----------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------|------------------------------------------------|------------------------|----------| +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | -36 | 65.4 (NOTE 5) | 54.9 (NOTE 5) | 100 kHz | | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | -30 | 67.4 | Not applicable | 1 MHz | | +| $12.75 \text{ GHz} \leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the DL operating band in GHz | -30 | 67.4 | Not applicable | 1 MHz | NOTE 1 | +| $F_{\text{DL,low}} - \Delta f_{\text{OBUE}} < f < F_{\text{DL,high}} + \Delta f_{\text{OBUE}}$ | Not defined | Not defined | Not defined | Not defined | NOTE 2,3 | + +NOTE 1: This frequency range applies only for operating bands for which the 5th harmonic of the upper frequency edge of the DL operating band is reaching beyond 12.75 GHz. +NOTE 2: For repeater capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported *operating bands* apply. +NOTE 3: $\Delta f_{\text{OBUE}}$ is defined in clause 6.5.3 of TS 38.106 [2]. +NOTE 4: The field strength measurements shall be conducted on OATS or SAC for frequencies up to 1 GHz, or on FSOATS or FAR for frequencies above 1 GHz. +NOTE 5: Limits for radiated emissions are translated from the e.r.p. limit of -36 dBm into the field strength limit of 61.4 dBμV/m (at 3m) or 50.9 dBμV/m (at 10m), and increased by the site gain value of 4 dB. The value of the site gain is based on ITU-R Recommendations SM.329 [19]. + +#### 8.2.1.4 Interpretation of the measurement results + +The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows: + +- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document; +- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report; +- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figures in table 8.2.1.4-1 for repeater. + +Table 8.2.1.4-1 specifies the maximum measurement uncertainty of the test system. The test system shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +**Table 8.2.1.4-1: Maximum measurement uncertainty (Repeater)** + +| Parameter | Uncertainty for EUT dimension $\leq 1$ m
(NOTE 2) | Uncertainty for EUT dimension $> 1$ m
(NOTE 2) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|---------------------------------------------------| +| Effective radiated RF power between 30 MHz and 180 MHz | $\pm 6$ dB | $\pm 6$ dB | +| Effective radiated RF power between 180 MHz and 4 GHz | $\pm 4$ dB | $\pm 6$ dB | +| Effective radiated RF power between 4 GHz and 12,75 GHz | $\pm 6$ dB | $\pm 9$ dB (NOTE 1) | +| Effective radiated RF power between 12,75 GHz and 26 GHz | $\pm 6$ dB | $\pm 9$ dB (NOTE 1) | +| Field strength between 30 MHz and 12,75 GHz | $\pm 6$ dB | $\pm 6$ dB | +| NOTE 1: This value may be reduced to $\pm 6$ dB when further information on the potential radiation characteristic of the EUT is available. | | | +| NOTE 2: These MU values estimates and are not based on the MU budget calculations. For more background on MU derivation analyses refer to CISPR 16-4-2 [27] and ETSI TR 100 028-1 [28]. | | | + +NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 8.2.1.4-1, this equipment can still be used, provided that an adjustment is made follows: + +Any additional uncertainty in the Test System over and above that specified in table 8.2.1.4-1 is used to tighten the test requirements, i.e. making the test harder to pass. + +This procedure will ensure that a test system not compliant with table 8.2.1.4-1 does not increase the probability of passing an EUT that would otherwise have failed a test if a test system compliant with table 8.2.1.4-1 had been used. + +### 8.2.2 Radiated emission, ancillary equipment + +This test is only applicable to *ancillary equipment* not incorporated in the radio equipment and intended to be measured on a stand-alone basis, as declared by the manufacturer. This test shall be performed on a representative configuration of the *ancillary equipment*. + +This test is not applicable for *ancillary equipment* incorporated in the radio equipment, or for *ancillary equipment* intended to be measured in combination with the radio equipment. In these cases, the requirements of the relevant product standard for the effective use of the radio spectrum shall apply. + +#### 8.2.2.1 Definition + +This test assesses the ability of *ancillary equipment* to limit unwanted emission from the *enclosure port*. + +#### 8.2.2.2 Test method + +The test method shall be in accordance with CISPR 32 [5]. + +#### 8.2.2.3 Limits + +The *ancillary equipment* shall meet the limits according to CISPR 32 [5] table A.4 and table A.5. + +For the referred limit values, the following shall apply: + +- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. +- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +Alternatively, for *ancillary equipment* intended to be used in telecommunication centres only, the class A limits given in CISPR 32 [5], annex A, table A.2 and table A.3 may be used. + +## 8.3 Conducted emission DC power input/output port + +This test is applicable to equipment which may have DC cables longer than 3 m. + +If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in clause 8.4. + +This test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 8.3.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to limit internal noise from the DC power input/output ports. + +### 8.3.2 Test method + +The test method shall be in accordance with CISPR 32 [5] and the Artificial Mains Network (AMN) shall be connected to a DC power source. + +In the case of DC output ports, the ports shall be connected via an AMN to a load drawing the rated current of the source. + +A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded. + +The equipment shall be installed with a ground plane as defined in CISPR 32 [5]. The reference earth point of the AMN shall be connected to the reference ground plane with a conductor as short as possible. + +### 8.3.3 Limits + +The equipment shall meet the limits according to CISPR 32 [5] table A.9, which are defined for average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +Where there is a step in the referred limit values, the lower value shall be applied at the transition frequency. + +## 8.4 Conducted emissions, AC mains power input/output port + +This test is applicable to equipment powered by the AC mains. + +This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT. + +This test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 8.4.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to limit internal noise from the AC mains power input/output ports. + +### 8.4.2 Test method + +The test method shall be in accordance with CISPR 32 [5]. + +### 8.4.3 Limits + +The equipment shall meet the limits according to CISPR 32 [5] table A.10, which are defined for the average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +For the referred limit values following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +Alternatively, for equipment intended to be used in telecommunication centres the limits given in CISPR 32 [5] table A.9 shall be used. + +## 8.5 Conducted emissions, telecommunication port + +This test is applicable for radio equipment and/or ancillary equipment for fixed use which have telecommunication ports. + +This test shall be performed on a representative configuration of radio equipment, the associated *ancillary equipment*, or a representative configuration of the combination of radio and *ancillary equipment*. + +### 8.5.1 Definition + +This test assesses the EUT unwanted emission present at the *telecommunication ports*. + +### 8.5.2 Test method + +The test method shall be in accordance with CISPR 32 [5]. + +### 8.5.3 Limits + +The *telecommunication ports* shall meet the limits according to CISPR 32 [5] table A.12. + +For the referred limit values, following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in CISPR 32 [5] table A.11 may be used. + +## 8.6 Harmonic Current emissions (AC mains input port) + +The requirements of IEC 61000-3-2 [8] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current greater than 16 A per phase, IEC 61000-3-12 [11] applies. + +## 8.7 Voltage fluctuations and flicker (AC mains input port) + +The requirements of IEC 61000-3-3 [9] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current greater than 16 A per phase, IEC 61000-3-11 [10] applies. + +# --- 9 Immunity + +## 9.1 Test configurations + +This clause defines the configurations for immunity tests as follows: + +- the equipment shall be tested under normal test conditions as specified in the functional standards; +- during the test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link; +- the test configuration shall be as close to normal intended use as possible; + +- if the equipment is part of a system, or can be connected to *ancillary equipment*, then it shall be acceptable to test the equipment while connected to the minimum configuration of *ancillary equipment* necessary to exercise the ports; +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an *ancillary equipment* or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the *ancillary equipment*. In case of *repeater type 1-C*, *antenna ports* shall be correctly terminated; +- ports which are not connected to cables during normal operation, shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- immunity tests on the entire NR repeater shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the BS interface (e.g. with a BS simulator) and evaluating the power accuracy; +- immunity tests shall be performed on both the uplink and downlink paths. The tests shall also include both the radio interface and the BS interface. Power accuracy evaluation may be carried out at either interface, where appropriate, and the measurements for the uplink and downlink paths may be carried out as a single path looped at either the radio interface or BS interface. In case of looping is used care have to be taken that the power accuracy doesn't change due to looping; +- for NR repeater capable of multi-band operation, communication links shall be established in such a way that all *operating band(s)* are activated during the test according to the applicable test configurations in clause 4.5. Performance assessment may be done separately for each *operating band*. + +![Figure 9.1-1: Communication link set up for repeater type 1-C immunity measurement. The diagram shows a 'UE Simulator' box on the left connected to a 'Repeater type 1-C (Antenna Ports Terminated)' box in the center. This central box is then connected to a 'BS Simulator' box on the right. All connections are shown as double-headed arrows, indicating bidirectional communication links.](e354b57563dae469c00b412b2abdf765_img.jpg) + +Figure 9.1-1: Communication link set up for repeater type 1-C immunity measurement. The diagram shows a 'UE Simulator' box on the left connected to a 'Repeater type 1-C (Antenna Ports Terminated)' box in the center. This central box is then connected to a 'BS Simulator' box on the right. All connections are shown as double-headed arrows, indicating bidirectional communication links. + +Figure 9.1-1: Communication link set up for *repeater type 1-C* immunity measurement + +![Figure 9.1-2: Communication link set up for repeater type 2-O immunity measurement. The diagram shows a 'UE Simulator' box on the left connected to a 'Repeater type 2-O' box in the center via an 'OTA Link' (represented by a double-headed arrow). The 'Repeater type 2-O' box is then connected to a 'BS Simulator' box on the right via another 'OTA Link' (also represented by a double-headed arrow).](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +Figure 9.1-2: Communication link set up for repeater type 2-O immunity measurement. The diagram shows a 'UE Simulator' box on the left connected to a 'Repeater type 2-O' box in the center via an 'OTA Link' (represented by a double-headed arrow). The 'Repeater type 2-O' box is then connected to a 'BS Simulator' box on the right via another 'OTA Link' (also represented by a double-headed arrow). + +Figure 9.1-2: Communication link set up for *repeater type 2-O* immunity measurement + +## 9.2 RF electromagnetic field (80 MHz - 6000 MHz) + +The test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.2.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. + +### 9.2.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-3 [13], which specified test methodology based on anechoic chamber. The use of reverberation chamber test method according to IEC 61000-4-21 [18], clause 6.1 and Annex D as alternative method is allowed. + +The following requirements shall apply: + +- The test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 1 % of the momentary frequency; +- The test shall be performed over the frequency range 80 MHz - 6000 MHz; with the exception of the exclusion band for receivers (see clause 4.4.2); +- Responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies selected during the test shall be recorded in the test report. +- For the test method in accordance with IEC 61000-4-3 [13], for repeater operating in FR2-1 the *spatial exclusion zone* can be chosen to protect the NR repeater's receiver. For the frequency arrange above 690 MHz (according to the test method in ETSI EN 301 489-50 [22]) the EMC RF electromagnetic field immunity requirement applies on the non-radiating faces of the *repeater type 2-O*, as depicted on figure 9.2.2-1. + +NOTE: Depending on the BS implementation, application of the spatial exclusion to all radiating faces of the NR repeater may not allow proper execution of the RI testing. In such cases, to protect the *repeater type 2-O* receiver(s), exclusion bands shall be considered, as in table 4.4.2-2. + +![Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for NR repeater type 2-O. The diagram shows a horizontal plane with a central dashed rectangle representing the 'Spatial exclusion zone'. To the left of this zone is a semi-circular shape labeled 'EUT'. Arrows indicate the 'RI testing direction' from the top and bottom, pointing towards the EUT. An arrow on the right indicates the 'EUT radiating direction' pointing away from the EUT.](f1fbb1287d999c7034742de35bdab836_img.jpg) + +The diagram shows a horizontal plane with a central dashed rectangle representing the 'Spatial exclusion zone'. To the left of this zone is a semi-circular shape labeled 'EUT'. Arrows indicate the 'RI testing direction' from the top and bottom, pointing towards the EUT. An arrow on the right indicates the 'EUT radiating direction' pointing away from the EUT. + +Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for NR repeater type 2-O. The diagram shows a horizontal plane with a central dashed rectangle representing the 'Spatial exclusion zone'. To the left of this zone is a semi-circular shape labeled 'EUT'. Arrows indicate the 'RI testing direction' from the top and bottom, pointing towards the EUT. An arrow on the right indicates the 'EUT radiating direction' pointing away from the EUT. + +Figure 9.2.2-1: EMC RF electromagnetic field immunity requirement testing directions for NR *repeater type 2-O* (horizontal plane depicted) with the *spatial exclusion zone* applied + +### 9.2.3 Performance criteria + +#### NR repeater: + +The performance criteria of clause 6.1 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.3 shall apply. + +## 9.3 Electrostatic discharge + +The test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.3.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the event of an electrostatic discharge. + +### 9.3.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-2 [12]: + +- for contact discharge, the equipment shall pass at $\pm 4$ kV; +- for air discharge shall pass at $\pm 8$ kV; +- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures. + +### 9.3.3 Performance criteria + +#### NR repeater: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. + +## 9.4 Fast transients common mode + +The test shall be performed on AC mains power input ports. + +This test shall be performed on *signal ports*, *telecommunication ports*, *control ports* and DC power input/output ports if the cables may be longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.4.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the event of fast transients present on one of the input/output ports. + +### 9.4.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-4 [14]: + +- The test level for *signal ports*, *telecommunication ports* and *control ports* shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [14]; +- The test level for DC power input/output ports shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [14]; +- The test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [14]. + +### 9.4.3 Performance criteria + +#### NR repeater: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. + +## 9.5 RF common mode (0.15 MHz - 80 MHz) + +The test shall be performed on AC mains power input/output ports. + +This test shall be performed on *signal ports*, *telecommunication ports*, control and DC power input/output ports, which may have cables longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.5.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the presence of a radio frequency electromagnetic disturbance. + +### 9.5.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-6 [16]: + +- The test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1% frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz; +- The test level shall be severity level 2 as given in IEC 61000-4-6 [16] corresponding to 3 V rms, at a transfer impedance of 150 Ω; +- The test shall be performed over the frequency range 150 kHz - 80 MHz; +- The injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [16]; +- Responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies of the immunity test signal selected and used during the test shall be recorded in the test report. + +### 9.5.3 Performance criteria + +#### NR repeater: + +The performance criteria of clause 6.1 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.3 shall apply. + +## 9.6 Voltage dips and interruptions + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.6.1 Definition + +These tests assess the ability of radio equipment and *ancillary equipment* to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports. + +### 9.6.2 Test method and level + +The following requirements shall apply. + +The test method shall be in accordance with IEC 61000-4-11 [17]. + +The test levels shall be: + +- Voltage dip: 0 % residual voltage for 0.5 cycle; +- Voltage dip: 0 % residual voltage for 1 cycle; +- Voltage dip: 70 % residual voltage for 25/30 cycles (at 50/60 Hz); +- Voltage interruption: 0 % residual voltage for 250/300 cycles (at 50/60 Hz). + +### 9.6.3 Performance criteria + +For a 0 % residual voltage dip test, the performance criteria for transient phenomena shall be applied: + +- Criteria 6.2 for NR repeater +- Criteria 6.4 for *ancillary equipment* + +For a 70% residual voltage dip test and for voltage interruption test, the following applies: + +1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied: + - Criteria 6.2 for NR repeater + - Criteria 6.4 for *ancillary equipment* +2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator: + - No unintentional responses shall occur at the end of the test + - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report. + +## 9.7 Surges, common and differential mode + +The tests shall be performed on AC mains power input ports. + +This test shall be additionally performed on *telecommunication ports*. + +These tests shall be performed on a representative configuration of the repeater, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.7.1 Definition + +These tests assess the ability of radio equipment and *ancillary equipment* to operate as intended in the event of surges being present at the AC mains power input ports and *telecommunication ports*. + +### 9.7.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-5 [15]. + +The requirements and evaluation of test results given in clause 9.7.2.1 (*telecommunication ports*, outdoor cables), clause 9.7.2.2 (*telecommunication ports*, indoor cables) and clause 9.7.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT. + +#### 9.7.2.1 Test method for telecommunication ports directly connected to outdoor cables + +The test level for *telecommunications ports*, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [15]. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [15]. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [15]. + +#### 9.7.2.2 Test method for telecommunication ports connected to indoor cables + +The test level for telecommunication *ports*, intended to be connected to indoor cables (longer than 10 m) shall be 0.5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [15]. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [15]. + +#### 9.7.2.3 Test method for AC power ports + +The test level for AC power input *ports* shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [15]. + +In telecommunication centres 1 kV line to ground and 0.5 kV line to line shall be used. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [15]. + +### 9.7.3 Performance criteria + +#### NR repeater: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-05 | RAN4#99-e | R4-2109916 | | | | TS skeleton | 0.0.1 | +| 2021-11 | RAN4#101-e | R4-2118228 | | | | Updating TS38.114 to capture RAN4#101 agreements:
R4-2118064, TP to TS38.114: Emission, ZTE Corporation
R4-2120637, TPs to TS 38.114 on RF Repeater EMC section 1 (Scope) and section 9 (Immunity), Ericsson LM
R4-2120638, TP to TS 38.114 for sections 4.3, 5.3, 6.3, 6.4, Huawei
R4-2120639, TP to TS 38.114 - applicability overview, Nokia, Nokia Shanghai Bell | 0.1.0 | +| 2022-01 | RAN4#101-bis-e | R4-2200730 | | | | Updating TS38.114 to capture RAN4#101-bis agreements:
R4-2202986, TP to TS 38.114: References, ZTE Corporation | 0.2.0 | +| 2022-03 | RAN4#102-e | R4-2204494 | | | | Updating TS38.114 to capture RAN4#102 agreements:
R4-2204358, TP to TS38.114: Definitions, symbols and abbreviations, ZTE Corporation | 0.3.0 | +| 2022-03 | RAN#95-e | RP-220549 | | | | Draft version for approval to the RAN Plenary | 1.0.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control and editorial | 17.0.1 | +| 2022-09 | RAN#97 | RP-222044 | 0002 | | B | Big CR for TS 38.114 (Rel-17, CAT B) | 17.1.0 | +| 2022-12 | RAN#98-e | RP-223305 | 0003 | | F | CR to TS38.114 repeater clause 8.1 R17 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223305 | 0004 | 1 | F | CR to TS 38.114 repeater performance criteria R17 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223305 | 0005 | 1 | B | CR to TS 38.114 Clause 4.5 | 17.2.0 | +| 2023-09 | RAN#101 | RP-232502 | 0006 | 1 | F | [NR_newRAT-Core] CR on TS 38.114 NR repeater general maintenance R17 | 17.3.0 | +| 2023-12 | RAN#102 | RP-233350 | 0008 | | F | CR to TS 38.114 with update to manufacturer declaration and references | 17.4.0 | +| 2023-12 | RAN#102 | RP-233334 | 0009 | | F | CR to TS 38.114 on correction of FR range to FR2-1 | 17.4.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38124/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38124/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90a4557e10a361aa15ebbc1bdb627c12c19411d2 --- /dev/null +++ b/marked/Rel-18/38_series/38124/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19170b18dad39c15291004f33ddc2bec41b11441257ee509d5ec44be04574fdd +size 9692 diff --git a/marked/Rel-18/38_series/38124/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38124/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c5206c4dce4a7e17f54e0a2709b886965a16bc --- /dev/null +++ b/marked/Rel-18/38_series/38124/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a219706914c3036104b27eb90b86c4812b0cc58683332b25592361449d11f28e +size 5624 diff --git a/marked/Rel-18/38_series/38124/raw.md b/marked/Rel-18/38_series/38124/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..de3a8d81353948ebba8b1cd5138e6d102ec325be --- /dev/null +++ b/marked/Rel-18/38_series/38124/raw.md @@ -0,0 +1,938 @@ + + +# 3GPP TS 38.124 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; ElectroMagnetic Compatibility (EMC) requirements for mobile terminals and ancillary equipment (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 11 | +| 4 Test conditions ..... | 11 | +| 4.1 General ..... | 11 | +| 4.2 Arrangements for establishing a communication link..... | 12 | +| 4.3 Narrow band responses on receivers..... | 12 | +| 4.4 Receiver exclusion band..... | 13 | +| 5 Performance assessment ..... | 13 | +| 5.1 General ..... | 13 | +| 5.2 Equipment which can provide a continuous communication link ..... | 13 | +| 5.3 Equipment which can only provide a discontinuous communication link (packet data/transmission) ..... | 14 | +| 5.4 Equipment which does not provide a communication link ..... | 14 | +| 5.5 Conformance of ancillary equipment..... | 14 | +| 5.6 Equipment classification ..... | 14 | +| 6 Performance criteria..... | 14 | +| 6.1 General ..... | 14 | +| 6.2 Performance criteria for continuous phenomena ..... | 15 | +| 6.3 Performance criteria for transient phenomena ..... | 15 | +| 7 Applicability overview tables ..... | 15 | +| 7.1 EMC emissions ..... | 15 | +| 7.2 Immunity ..... | 16 | +| 8 Methods of measurement and limits for EMC emissions ..... | 16 | +| 8.1 Test configurations..... | 16 | +| 8.2 Radiated emission ..... | 17 | +| 8.2.1 General ..... | 17 | +| 8.2.2 Definition..... | 17 | +| 8.2.3 Test method ..... | 17 | +| 8.2.4 Limits..... | 18 | +| 8.2.5 Interpretation of the measurement results ..... | 19 | +| 8.3 Conducted emission DC power input/output port..... | 19 | +| 8.3.1 Definition..... | 20 | +| 8.3.2 Test method ..... | 20 | +| 8.3.3 Limits..... | 20 | +| 8.4 Conducted emissions, AC mains power input/output port..... | 20 | +| 8.4.1 Definition..... | 20 | +| 8.4.2 Test method ..... | 20 | +| 8.4.3 Limits..... | 20 | +| 8.5 Harmonic current emissions (AC mains input port) ..... | 20 | +| 8.6 Voltage fluctuations and flicker (AC mains input port)..... | 21 | +| 9 Test methods and levels for immunity tests ..... | 21 | +| 9.1 Test configurations..... | 21 | +| 9.2 RF electromagnetic field (80 MHz to 6000 MHz) ..... | 21 | +| 9.2.1 Definition..... | 21 | +| 9.2.2 Test method and level..... | 22 | +| 9.2.3 Performance criteria ..... | 22 | +| 9.3 Electrostatic discharge..... | 22 | + +| | | | +|---------------------------------------------------|---------------------------------------------------|-----------| +| 9.3.0 | General ..... | 22 | +| 9.3.1 | Definition..... | 22 | +| 9.3.2 | Test method and level..... | 22 | +| 9.3.3 | Performance criteria ..... | 22 | +| 9.4 | Fast transients common mode..... | 22 | +| 9.4.0 | General ..... | 22 | +| 9.4.1 | Definition..... | 23 | +| 9.4.2 | Test method and level..... | 23 | +| 9.4.3 | Performance criteria ..... | 23 | +| 9.5 | RF common mode (0.15 MHz to 80 MHz)..... | 23 | +| 9.5.0 | General ..... | 23 | +| 9.5.1 | Definition..... | 23 | +| 9.5.2 | Test method and level..... | 23 | +| 9.5.3 | Performance criteria ..... | 24 | +| 9.6 | Transients and surges, vehicular environment..... | 24 | +| 9.6.1 | Definition..... | 24 | +| 9.6.2 | Test method and level..... | 24 | +| 9.6.2.1 | 12 V DC powered equipment ..... | 24 | +| 9.6.2.2 | 24 V DC powered equipment ..... | 24 | +| 9.6.3 | Performance criteria ..... | 24 | +| 9.7 | Voltage dips and interruptions ..... | 25 | +| 9.7.0 | General ..... | 25 | +| 9.7.1 | Definition..... | 25 | +| 9.7.2 | Test method and level..... | 25 | +| 9.7.3 | Performance criteria ..... | 25 | +| 9.8 | Surges, common and differential mode..... | 25 | +| 9.8.1 | Definition..... | 25 | +| 9.8.2 | Test method and level..... | 25 | +| 9.8.3 | Performance criteria ..... | 26 | +| Annex A (informative): Change history..... | | 27 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document establishes the essential EMC requirements for "3rd generation" digital cellular mobile terminal equipment and ancillary accessories in combination with a 3GPP NR user equipment (UE). + +The equipment conforming to the requirements laid out in the present document and used in its intended electromagnetic environment in accordance with the manufacturer's instructions + +- shall not generate electromagnetic disturbances at a level which may interfere with the intended operation of other equipment; +- has an adequate level of intrinsic immunity to electromagnetic disturbances to operate as intended; + +The present document specifies the applicable EMC tests, methods of measurement, frequency ranges, applicable limits and minimum performance criteria for all types of NR UE(s) and their accessories. NR base station equipment operating within network infrastructure is outside the scope of the present document. However, the present document does cover mobile and portable equipment that is intended to be operated in a fixed location while connected to the AC mains. NR base station equipment operating within network infrastructure is covered by the technical specification TS 38.113 [2]. + +Requirements for the radiated emission from the enclosure port of integral antenna equipment and ancillaries are included in the present document. Technical specifications for conducted emissions from the antenna connector are found in the 3GPP specifications for the radio interface of NR UE, e.g. TS 38.101-1 [3], for the effective use of the radio spectrum. + +Requirements for the radiated emissions from the enclosure port and ancillaries cover the following case: + +- UE equipment supporting operations in a frequency range for which antenna connectors are available (i.e. for operations in FR1 as defined in e.g. TS 38.101-1 [3] for the radio interface). + +The immunity requirements are selected to ensure an adequate level of compatibility for apparatus in residential, commercial, light industrial and vehicular environments. The levels however, do not cover extreme cases, which may occur in any location but with low probability of occurrence. + +Compliance of radio equipment to the requirements of the present document does not signify compliance to any requirement related to the use of the equipment (i.e. licensing requirements). + +Compliance to the requirements of the present document does not signify compliance to any safety requirement. However, any temporary or permanent unsafe condition caused by EMC is considered as non-compliance. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] 3GPP TS 38.113: "NR; Base Station (BS) ElectroMagnetic Compatibility (EMC)". + +[3] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". + +- [4] 3GPP TS 38.101-2: " NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [5] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [6] Void +- [7] Void. +- [8] IEC 61000-3-2: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current $\leq 16$ A per phase)". +- [9] IEC 61000-3-3: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems, for equipment with rated current $\leq 16$ A per phase and not subject to conditional connection". +- [10] IEC 61000-4-3:[2006+AMD1:2007+AMD2:2010 CSV](#): "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency electromagnetic field immunity test". +- [11] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test". +- [12] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4-4: Testing and measurement techniques - Electrical fast transient/burst immunity test - Basic EMC publication". +- [13] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances induced by radio frequency fields". +- [14] Void +- [15] ISO 7637-2: "Road vehicles -- Electrical disturbances from conduction and coupling -- Part 2: Electrical transient conduction along supply lines only". +- [16] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions, and voltage variations immunity test". +- [17] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test". +- [18] ITU-R Recommendation SM.1539 (2001): "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329". +- [19] IEC 60050-161: "International Electrotechnical Vocabulary - Chapter 161: Electromagnetic compatibility". +- [20] IEC CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements". +- [21] 3GPP TS 38.508-1: "User Equipment (UE) conformance specification; Part 1: Common test environment". +- [22] 3GPP 38.509: "Special conformance testing functions for User Equipment (UE)". +- [23] CISPR 16-4-2: " Specification for radio disturbance and immunity measuring apparatus and methods - Part 4-2: Uncertainties, statistics and limit modelling - Measurement instrumentation uncertainty, Amendment 2" +- [24] ETSI TR 100 028-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Uncertainties in the measurement of mobile radio equipment characteristics, part 1" + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Ancillary equipment:** Equipment (apparatus), used in connection with a user equipment (UE) is considered as an ancillary equipment (apparatus) if: + +- the equipment is intended for use in conjunction with a UE to provide additional operational and/or control features to the UE, (e.g. to extend control to another position or location); and +- the equipment cannot be used on a stand-alone basis to provide user functions independently of a UE; and +- the UE to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions). + +**Channel bandwidth:** The RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**Enclosure port:** Physical boundary of the apparatus through which electromagnetic fields may radiate or impinge. In the case of integral antenna equipment, this port is inseparable from the antenna port. + +**Idle mode:** state of User Equipment (UE) when switched ON but with no Radio Resource Control (RRC) connection. + +**Integral antenna:** Antenna designed to be connected directly to the equipment with or without the use of an external connector and considered to be part of the equipment. An integral antenna may be fitted internally or externally to the equipment. + +**Necessary bandwidth:** For a given class of emission, the width of the frequency band which is just sufficient to ensure the transmission of information at the rate and with the quality required under specified conditions. + +**Out of band emissions:** Emission on a frequency or frequencies immediately outside the necessary bandwidth, which results from, the modulation process, but excluding spurious emissions. + +**Spurious emission:** Emission on a frequency, or frequencies, which are outside the necessary bandwidth and the level of which may be reduced without affecting the corresponding transmission of information. Spurious emissions include harmonic emissions, parasitic emissions, intermodulation products and frequency conversion products but exclude out-of-band emissions. + +**Traffic mode:** state of User Equipment (UE) when switched ON and with Radio Resource Control (RRC) connection established. + +**Transient phenomena:** Pertaining to or designating a phenomenon or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [19]) + +**User equipment:** is a "Mobile Station" (MS) which is an entity capable of accessing a set of NR services via one or more radio interfaces. This entity may be stationary or in motion within the NR service area while accessing the NR services, and may simultaneously serve one or more users. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----------------------|--------------------------------------------------------------------------------| +| BW Channel | Channel bandwidth | +| F OOB | The boundary between the NR out of band emission and spurious emission domains | + +$N_{RB}$ Transmission bandwidth configuration, expressed in units of resource blocks + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|-------------------------------------| +| AC | Alternating Current | +| CA | Carrier Aggregation | +| DC | Direct Current | +| DRX | Discontinuous Reception | +| DTX | Discontinuous Transmission | +| ESD | Electrostatic Discharge | +| EUT | Equipment Under Test | +| FAC | Fully Anechoic Chamber | +| FR | Frequency Range | +| HCP | Horizontal Coupling Plane | +| LISN | Line Impedance Stabilising Networks | +| LR | Location Registration | +| NR | New Radio | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RRC | Radio Resource Control | +| UE | User Equipment | + +# 4 Test conditions + +## 4.1 General + +The equipment shall be tested under normal test conditions according to the relevant product and basic standards. If these conditions are not specified then the manufacturers declared range of humidity, temperature and supply voltage shall be used. The test conditions shall be recorded in the test report. + +Whenever the Equipment under test (EUT) is provided with a detachable antenna, the EUT shall be tested with the antenna fitted in a manner typical of normal intended use, unless specified otherwise. + +Where the equipment incorporates an external 50 $\Omega$ RF antenna connector that is normally connected via a coaxial cable, then the wanted signal to establish a communication link also uses a coaxial cable. + +Where the equipment has an external 50 $\Omega$ RF antenna connector that is not normally connected via a coaxial cable or where the equipment has no external 50 $\Omega$ RF connector (i.e., integral antenna equipment), then the wanted signal, to establish a communication link, shall be delivered from the equipment to an antenna located within the test environment. + +Requirements throughout the RF specifications are in many cases defined separately for different frequency ranges (FR). The frequency ranges in which a UE equipment (NR) can operate according to this version of the specification are identified as described in table 4.1-1. The test conditions may be different for operations in FR1 and FR2. + +**Table 4.1-1: Definition of frequency ranges** + +| Frequency range designation | Corresponding frequency range | +|-----------------------------|-------------------------------| +| FR1 | 410 MHz – 7125 MHz | +| FR2 | 24250 MHz – 52600 MHz | + +## 4.2 Arrangements for establishing a communication link + +For transmitters with an integral antenna, the wanted RF output signal to establish a communication link shall be delivered from the EUT to an antenna located within the test environment. This antenna shall be connected to the external measuring equipment by a coaxial cable. + +For transmitters with an antenna connector, the wanted RF output signal to establish a communication link shall be delivered from the antenna connector to the external measuring equipment by a shielded transmission line, such as a coaxial cable. Adequate measures shall be taken to minimize the effect of unwanted common mode currents on the external conductor of the transmission line at the point of entry to the transmitter. + +The wanted RF input signal nominal frequency shall be selected by setting the NR Absolute Radio Frequency Channel Number to an appropriate number. + +For UE equipment only support operations in FR1 a communication link shall be set up with a suitable base station simulator (hereafter called "the test system"). The test system shall be located outside of the test environment. + +When the EUT is required to be in the traffic mode, a call is set up according to the generic call set-up procedure and the following conditions shall be met: + +- Set and send continuously positive TPC commands to the UE; +- The DTX shall be disabled; +- Uplink power control shall be enabled; +- transmitting and/or receiving (UL/DL) bit rate for reference test channel shall be the reference measurement channel as specified in annex A in TS 38.101-1 [3] with parameters specified in table 7.3.2-1 and table 7.3.2-2 in TS 38.101-1 [3]; +- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment; +- For immunity testing, the wanted input signal level shall be set to 40 dB above the reference sensitivity level to provide a stable communication link. The reference sensitivity level is defined in TS 38.101-1 [3]; +- For emission testing, the wanted input signal level shall be no more than 15 dB above the reference sensitivity level, such that the performance of the measuring receiver is not limited by strong signal effects. + +See TS 38.508-1 [21] and TS 38.509 [22] for details regarding generic call set-up procedure and throughput test loop scenarios. + +When the EUT is required to be in the idle mode the following conditions shall be met: + +- UE shall be camped on a cell +- UE shall perform Location Registration (LR) before the test, but not during the test; +- UE's neighbour cell list shall be empty; +- Paging repetition period and DRX cycle shall be set to minimum (shortest possible time interval). + +For immunity tests, clause 4.3 applies. + +## 4.3 Narrow band responses on receivers + +Responses on receivers or duplex transceivers occurring during the test at discrete frequencies, which are narrow band responses (spurious responses), are identified by the following method: + +- If during an immunity test the quantity being monitored goes outside the specified tolerances, it is necessary to establish whether the deviation is due to an unwanted effect on the receiver of the UE or on the test system (narrow band response) or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased or decreased by $BW_{\text{Channel}}$ MHz, where $BW_{\text{Channel}}$ is the channel bandwidth as defined in TS 38.101-1 [3]; + +- If the deviation does not disappear, the procedure is repeated the unwanted signal frequency increased or decreased by $2 \times BW_{\text{Channel}}$ MHz, where $BW_{\text{Channel}}$ is the channel bandwidth as defined in TS 38.101-1 [3]; +- If the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test. + +Narrow band responses are disregarded. + +The procedure above does not apply to conducted immunity tests in the frequency range 150 kHz to 80 MHz. + +## 4.4 Receiver exclusion band + +The receiver exclusion band for terminals extends from the lower frequency of the allocated receiver band minus 85 MHz to the upper frequency of the allocated receiver band plus 85 MHz. The *receiver exclusion band* for UE is the frequency range over which no tests of radiated immunity of a receiver are made. The exclusions bands are as set out below: + +$$F_{\text{DL,low}} - 85 < f < F_{\text{DL,high}} + 85 \text{ (MHz)}$$ + +Where values of $F_{\text{DL,low}}$ and $F_{\text{DL,high}}$ are defined for each operating band in TS 38.101-1 [3], clause 5.2. + +# --- 5 Performance assessment + +## 5.1 General + +The manufacturer shall at the time of submission of the equipment for test, supply the following information to be recorded in the test report: + +- The primary functions of the radio equipment to be tested during and after the EMC testing; +- If applicable, the method to be used to verify that a communications link is established and maintained; +- The intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment; +- The user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress; +- The ancillary equipment to be combined with the radio equipment for testing (where applicable); +- Information about ancillary equipment intended to be used with the radio equipment; +- An exhaustive list of ports, classified as either power or signal/control. Power ports shall further be classified as AC or DC power; +- The humidity range, temperature, and supply voltage for all equipment submitted for testing. + +## 5.2 Equipment which can provide a continuous communication link + +The test arrangement and signals, given in clause 4, apply to radio equipment or a combination of radio equipment and ancillary equipment that permits the establishment of a communication link. The assessment of equipment performance shall be based on data transfer according to the criteria in clause 6. + +## 5.3 Equipment which can only provide a discontinuous communication link (packet data/transmission) + +If the equipment does not permit or allow for a communications link to be established and maintained during the EMC tests (as in clause 5.2), the manufacturer shall define the performance assessment. The manufacturer shall provide the method of observing the degradation of performance of the equipment. + +## 5.4 Equipment which does not provide a communication link + +If the equipment is of a specialised nature which does not permit a communication link to be established, the manufacturer shall define the method of test to determine the acceptable level of performance or degradation of performance during and/or after the test. The manufacturer shall provide the method of observing the degradation of performance of the equipment. + +The performance assessment carried out shall be simple, but at the same time give adequate proof that the primary functions of the equipment are operational. + +## 5.5 Conformance of ancillary equipment + +Ancillary equipment shall be tested with it connected to a UE in which case compliance shall be demonstrated to the appropriate clauses of the present document. + +## 5.6 Equipment classification + +Equipment is classified according to the source of power: + +- If power is derived from a fixed AC or DC supply network installation the equipment is classified "for fixed use"; +- If power is derived from a vehicular power supply (car battery + alternator) the equipment is classified "for vehicular use"; +- If power is derived from an integral battery the equipment is classified "for portable use". + +# --- 6 Performance criteria + +## 6.1 General + +The maintenance of a communications link shall be assessed by using an indicator, which may be part of the test system or the equipment under test. + +Specifically the equipment shall meet the minimum performance criteria as specified in the following clauses as appropriate. + +Portable equipment intended for use whilst powered by the main battery of a vehicle shall additionally fulfil the applicable requirements set out by the present document for mobile equipment for vehicular use. + +Portable equipment intended for use whilst powered by AC mains shall additionally fulfil the applicable requirements set out by the present document for equipment for fixed use. + +If an equipment is of such nature, that the performance criteria described in the following clauses are not appropriate, then the manufacturer shall declare, for inclusion in the test report, his own specification for an acceptable level of performance or degradation of performance during and/or after testing, as required by the present document. + +The performance criteria specified by the manufacturer shall give the same degree of immunity protection as called for in the following clauses. + +In addition, the test shall also be performed in idle mode to ensure the transmitter does not unintentionally operate. + +The requirements apply to all types of NR for the UE. + +## 6.2 Performance criteria for continuous phenomena + +A communication link shall be established at the start of the test, and maintained during the test, clauses 4.1 and 4.2. + +In the data transfer mode, the performance criteria shall be that the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A in TS 38.101-1 [3] or TS 38.101-2 [4], with parameters specified in clause 7.3.2 in TS 38.101-1 [3] or TS 38.101-2 [4] during the test sequence. + +At the conclusion of the test, the EUT shall operate as intended with no loss of user control functions or stored data, and the communication link shall have been maintained. + +In addition to confirming the above performance in traffic mode, the test shall be performed in idle mode, and the transmitter shall not unintentionally operate. + +## 6.3 Performance criteria for transient phenomena + +A communications link shall be established at the start of the test, clauses 4.1 and 4.2. + +At the conclusion of each exposure the EUT shall operate with no user noticeable loss of the communication link. + +At the conclusion of the total test comprising the series of individual exposures, the EUT shall operate as intended with no loss of user control functions or stored data, as declared by the manufacturer, and the communication link shall have been maintained. + +In addition to confirming the above performance in traffic mode, the test shall also be performed in idle mode, and the transmitter shall not unintentionally operate. + +# 7 Applicability overview tables + +## 7.1 EMC emissions + +**Table 7.1-1: Emission applicability** + +| Phenomenon | Application | Equipment test requirement | | | Reference clause in the present document | Reference standard | +|-----------------------------------------|----------------------------|-----------------------------------------------------------|----------------------------------------------|---------------------------------------|------------------------------------------|-------------------------------------| +| | | Equipment connected to fixed AC or DC power installations | Equipment connected to vehicular DC supplies | Equipment powered by integral battery | | | +| Radiated emission | Enclosure | applicable | applicable | applicable | 8.2 | ITU-R SM.329 [5]
TS 38.101-1 [3] | +| Conducted emission | DC power input/output port | applicable | applicable | not applicable | 8.3 | CISPR 32 [20] | +| Conducted emission | AC mains input/output port | applicable | not applicable | not applicable | 8.4 | CISPR 32 [20] | +| Harmonic current emissions | AC mains input port | applicable | not applicable | not applicable | 8.5 | IEC 61000-3-2 [8] | +| Voltage fluctuations and flicker | AC mains input port | applicable | not applicable | not applicable | 8.6 | IEC 61000-3-3 [9] | + +For UE equipment operating in FR1 (table 4.1-1), the radiated emission applies to the enclosure port with antenna ports available. + +For UE equipment supporting operations in FR2 (table 4.1-1) the enclosure port is inseparable from the antenna port. + +## 7.2 Immunity + +**Table 7.2-1: Immunity applicability** + +| Phenomenon | Application | Equipment test requirement | | | Reference clause in the present document | Reference standard | +|------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------|---------------------------------------|------------------------------------------|-----------------------------------------------| +| | | Equipment connected to fixed AC or DC power installations | Equipment connected to vehicular DC supplies | Equipment powered by integral battery | | | +| RF electromagnetic field (80 MHz to 6000 MHz) | Enclosure | applicable | applicable | applicable | 9.2 | IEC 61000-4-3 [10] | +| Electrostatic discharge | Enclosure | applicable | applicable | applicable | 9.3 | IEC 61000-4-2 [11] | +| Fast transients common mode | Signal and control ports, DC and AC power input ports | applicable | not applicable | not applicable | 9.4 | IEC 61000-4-4 [12] | +| RF common mode 0.15 MHz to 80 MHz | Signal and control ports, DC and AC power input ports | applicable | applicable | applicable | 9.5 | IEC 61000-4-6 [13] | +| Transients and surges, vehicular environment | DC power input ports | not applicable | applicable | not applicable | 9.6 | ISO 7637 Part 1 [14] and ISO 7637 Part 2 [15] | +| Voltage dips and interruptions | AC mains power input ports | applicable | not applicable | not applicable | 9.7 | IEC 61000-4-11 [16] | +| Surges, common and differential mode | DC and AC power input ports | applicable | not applicable | not applicable | 9.8 | IEC 61000-4-5 [17] | + +# 8 Methods of measurement and limits for EMC emissions + +## 8.1 Test configurations + +This clause defines the configurations for emission tests as follows: + +- the equipment shall be tested under normal test conditions; +- the test configuration shall be as close to normal intended use as possible; +- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports; + +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated; +- ports that are not connected to cables during normal operation, e.g. service connectors, programming connectors; temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- emission tests shall be performed in two modes of operation: + - with a communication link established (traffic mode); and + - without a communication link established (idle mode). +- For UE supporting multiple NR CA or DC band combinations (including EN-DC, as well as NE DC), only one band combination with the largest frequency span (i.e. lowest frequency to highest frequency for the supported band combination) is selected for testing for each supported frequency range (i.e. FR1 only, FR1+FR2, FR2 only) for emission tests, besides radiated emission. + +## 8.2 Radiated emission + +### 8.2.1 General + +This test is applicable to radio communications equipment and ancillary equipment. + +This test shall be performed on the radio equipment and/or a representative configuration of the ancillary equipment. + +### 8.2.2 Definition + +This test assesses the ability of radio equipment and ancillary equipment to limit unwanted emissions from the enclosure port. + +For UE equipment supporting operations in FR2 (table 4.1-1) with integral antennas only (no antenna connectors available), the EMC radiated emissions cannot be distinguished between the intended emissions nor to any spurious emissions related to these intentional transmissions: + +- This test is applicable to UE equipment without integral antennas, i.e. FR1. +- For UE equipment with integral antennas only, i.e. FR2, the radiated emission is covered by radiated spurious emission requirement in TS 38.101-2 [4]. + +### 8.2.3 Test method + +Whenever possible the site shall be a fully anechoic chamber (FAC) simulating the free-space conditions. EUT shall be placed on a non-conducting support. Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). + +At each frequency at which a component is detected, the EUT shall be rotated to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement, which shall be the reference method. The measurement shall be repeated with the test antenna in the orthogonal polarization plane. + +NOTE: Effective radiated power e.r.p. refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2.15 dB between e.i.r.p. and e.r.p. + +$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2.15 \quad , \text{Ref. ITU-R SM. 329 annex 1 [5]}$$ + +Measurements are made with a tuned dipole antenna or a reference antenna with a known gain referenced to an isotropic antenna. Unless otherwise stated, all measurements are done as mean power (RMS). + +### 8.2.4 Limits + +Unless otherwise stated, the radiated spurious emission limits apply for the frequency ranges that are more than $F_{\text{OOB}}$ (MHz) in table 8.2.4-0 from the edge of the channel bandwidth. The radiated spurious emission limits in table 8.2.4-1 for traffic mode and in table 8.2.4-2 for idle mode, apply for all transmitter band configurations ( $N_{\text{RB}}$ ) and channel bandwidths. + +The references for these requirements are ITU-R SM 329 [5], SM.1539 [18] and TS 38.101-1 [3] for FR1. + +The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R SM 329 [5]. + +These requirements are only applicable for frequencies in the spurious domain. The limits are specified in table 8.2.4-1 for traffic mode and in table 8.2.4-2 for idle mode for UE equipment supporting operations in FR1 only. + +**Table 8.2.4-0: Boundary between NR out of band and general spurious emission domain** + +| Channel bandwidth (MHz) | OOB boundary $F_{\text{OOB}}$ (MHz) | +|----------------------------------------|-------------------------------------| +| 3 | 6 | +| BW Channel larger than 3MHz | $BW_{\text{Channel}} + 5$ | + +**Table 8.2.4-1: Radiated spurious emissions requirements for UE equipment supporting operations in FR1, traffic mode** + +| Frequency range | Maximum level (dBm) | Measurement bandwidth | Notes | +|-----------------------------------------------------------------------------------------------------------------|---------------------|-----------------------|-------| +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | -36 | 100 kHz | | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | -30 | 1 MHz | 4 | +| | -25 | 1 MHz | 3 | +| $12.75 \text{ GHz} \leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the UL operating band in GHz | -30 | 1 MHz | 1 | +| $12.75 \text{ GHz} < f < 26 \text{ GHz}$ | -30 | 1 MHz | 2 | + +NOTE 1: Applies for Band that the upper frequency edge of the UL Band more than 2.69 GHz. +NOTE 2: Applies for Band that the upper frequency edge of the UL Band more than 5.2 GHz. +NOTE 3: As specified in TS 38.101-1 [3]: Applies for Band n41, CA configurations including Band n41, and EN-DC configurations that include n41 specified in clause 5.2B of TS 38.101-3 [3] when NS\_04 is signalled. +NOTE 4: As specified in TS 38.101-1 [3]: Does not apply for Band n41, CA configurations including Band n41, and EN-DC configurations that include n41 specified in clause 5.2B of TS 38.101-3 [3] when NS\_04 is signalled. + +NOTE: Void. + +**Table 8.2.4-2: Radiated spurious emissions requirements for UE equipment supporting operations in FR1, idle mode** + +| Frequency range | Maximum level (dBm) | Measurement bandwidth | NOTE | +|--------------------------------------------------------------------------------------------------------------------|---------------------|-----------------------|------| +| $30 \text{ MHz} \leq f < 1 \text{ GHz}$ | -57 | 100 kHz | | +| $1 \text{ GHz} \leq f \leq 12.75 \text{ GHz}$ | -47 | 1 MHz | | +| $12.75 \text{ GHz} \leq f \leq 5^{\text{th}}$ harmonic of the upper frequency edge of the DL operating band in GHz | -47 | 1 MHz | 2 | +| $12.75 \text{ GHz} - 26 \text{ GHz}$ | -47 | 1 MHz | 3 | + +NOTE 1: Unused PDCCH resources are padded with resource element groups with power level given by PDCCH as defined in TS 38.101-1 [3], annex C.3.1. +NOTE 2: Applies for Band that the upper frequency edge of the DL Band more than 2.69 GHz. +NOTE 3: Applies for Band that the upper frequency edge of the DL Band more than 5.2 GHz. + +### 8.2.5 Interpretation of the measurement results + +The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows: + +- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document; +- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report; +- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figure in table 8.2.5-1. + +Table 8.2.5-1 specifies the Maximum measurement uncertainty of the Test System. The Test System shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +**Table 8.2.5-1: Maximum measurement uncertainty** + +| Parameter | Maximum MU
(NOTE) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Effective radiated RF power between 30 MHz and 180 MHz | ±6 dB | +| Effective radiated RF power between 180 MHz and 12.75 GHz | ±3 dB | +| Effective radiated RF power between 12.75 GHz and 26 GHz | ±6 dB | +| NOTE: These MU values estimates and are not based on the MU budget calculations.
For more background on MU derivation analyses refer to CISPR 16-4-2 [23] and ETSI TR 100 028-1 [24]. | | + +NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 8.2.5-1, this equipment can still be used, provided that an adjustment is made follows: +Any additional uncertainty in the Test System over and above that specified in table 8.2.5-1 is used to tighten the Test Requirements - making the test harder to pass. This procedure will ensure that a Test System not compliant with table 8.2.5-1 does not increase the probability of passing an EUT that would otherwise have failed a test if a Test System compliant with table 8.2.5-1 had been used. + +## 8.3 Conducted emission DC power input/output port + +This test is applicable to all equipment, which may have DC cables longer than 3 m. + +If the DC power cable of the UE and/or the ancillary equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in clause 8.4. + +This test shall be performed on a representative configuration of the radio equipment or a representative configuration of the combination of radio and ancillary equipment. + +### 8.3.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the DC power input/output ports. + +### 8.3.2 Test method + +The test method shall be in accordance with CISPR 32 [20], and the Line Impedance Stabilising Networks (LISN) shall be connected to a DC power source. + +In the case of DC output ports, the ports shall be connected via a LISN to a load drawing the rated current of the source. + +A measuring receiver shall be connected to each LISN measurement port in turn and the conducted emission recorded. The LISN measurement ports not being used for measurement shall be terminated with a 50 $\Omega$ load. + +The equipment shall be installed with a ground plane as defined in CISPR 32 [20]. The reference earth point of the LISNs shall be connected to the reference ground plane with a conductor as short as possible. + +### 8.3.3 Limits + +The equipment shall meet the limits according to CISPR 32 [20] table A.9 which are defined for average detector receiver and for quasi peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +## 8.4 Conducted emissions, AC mains power input/output port + +This test is applicable to equipment powered by the AC mains. + +This test is not applicable to AC output ports, which are connected directly (or via a switch or circuit breaker) to the AC input port. + +This test shall be performed on a representative configuration of the radio equipment or a representative configuration of the combination of radio and ancillary equipment. + +### 8.4.1 Definition + +This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the AC mains power input/output ports. + +### 8.4.2 Test method + +The test method shall be in accordance with CISPR 32 [20]. + +### 8.4.3 Limits + +The equipment shall meet the limits according to CISPR 32 [20] table A.10, which are defined for the average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +## 8.5 Harmonic current emissions (AC mains input port) + +The requirements of IEC 61000-3-2 [8] for harmonic current emission apply for equipment covered by the scope of the present document. + +## 8.6 Voltage fluctuations and flicker (AC mains input port) + +The requirements of IEC 61000-3-3 [9] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. + +# --- 9 Test methods and levels for immunity tests + +## 9.1 Test configurations + +This clause defines the configurations for immunity tests as follows: + +- the equipment shall be tested under normal test conditions as specified in the core specification; + +- the test configuration shall be as close to normal intended use as possible; +- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports; +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated; +- ports, which are not, connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- the test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time; +- immunity tests shall be performed in two modes of operation: + - with a communication link established (traffic mode); and + - without a communication link established (idle mode). +- For UE supporting multiple NR CA or DC band combinations (including EN-DC, as well as NE DC), only one band combination with the largest frequency span (i.e. lowest frequency to highest frequency for the supported band combination) is selected for testing for each supported frequency range (i.e. FR1 only, FR1+FR2, FR2 only) for immunity tests, besides RF electromagnetic field and Electrostatic discharge. + +## 9.2 RF electromagnetic field (80 MHz to 6000 MHz) + +The test shall be performed on a representative configuration of the equipment or a representative configuration of the combination of UE and ancillary equipment. + +### 9.2.1 Definition + +This test assesses the ability of UE and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. + +### 9.2.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-3 [10]: + +- For UE and ancillary equipment, the following requirements shall apply; +- The test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 1 % of the momentary frequency; +- The test shall be performed over the frequency range 80 MHz to 6000 MHz; +- Responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies selected during the test shall be recorded in the test report. + +### 9.2.3 Performance criteria + +The performance criteria of clause 6.1 shall apply. + +## 9.3 Electrostatic discharge + +### 9.3.0 General + +The test shall be performed on a representative configuration of the equipment or a representative configuration of the combination of UE and ancillary equipment. + +### 9.3.1 Definition + +This test assesses the ability of UE and ancillary equipment to operate as intended in the event of an electrostatic discharge. + +### 9.3.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-2 [11]: + +- for contact discharge, the equipment shall pass at $\pm 2$ kV and $\pm 4$ kV; +- for air discharge the equipment shall pass at $\pm 2$ kV, $\pm 4$ kV and $\pm 8$ kV (only for non-conducting surfaces, see IEC 61000-4-2 [11]). + +NOTE: The EUT shall be fully discharged between each ESD exposure by connecting its ground point (where applicable) to the HCP by a resistive wire with a 470 k $\Omega$ resistor in either end. + +### 9.3.3 Performance criteria + +The performance criteria of clause 6.2 shall apply. + +## 9.4 Fast transients common mode + +### 9.4.0 General + +The test shall be performed on AC mains power input ports. + +This test shall be performed on signal ports, control ports and DC power input/output ports if the cables may be longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment or a representative configuration of the combination of UE and ancillary equipment. + +### 9.4.1 Definition + +This test assesses the ability of UE and ancillary equipment to operate as intended in the event of fast transients present on one of the input/output ports. + +### 9.4.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-4 [12] + +- the test level for signal and control ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [12]; +- the test level for DC power input/output ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [12]; +- the test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [12]. + +### 9.4.3 Performance criteria + +The performance criteria of clause 6.2 shall apply. + +## 9.5 RF common mode (0.15 MHz to 80 MHz) + +### 9.5.0 General + +This test is applicable for UE for fixed, mobile, and portable use and for ancillary equipment. + +This test shall be performed on signal, control and DC power input/output ports, which may have cables longer than 3 m. + +This test shall be performed on AC mains power input/output ports of UE for fixed use and for fixed ancillary equipment. Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report. + +This test shall be performed on a representative configuration of the UE or a representative configuration of the combination of UE and ancillary equipment. + +#### 9.5.1 Definition + +This test assesses the ability of equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic disturbance. + +### 9.5.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-6 [13]: + +- the test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- the stepped frequency increments shall be either 50 kHz or 1 % frequency increment of the momentary frequency in the frequency range 150 kHz - 5 MHz and 1 % frequency increment of the momentary frequency in the frequency range 5 MHz - 80 MHz; +- the test level shall be severity level 2 as given in IEC 61000-4-6 [13] corresponding to 3 V RMS, at a transfer impedance of 150 Ω; +- the test shall be performed over the frequency range 150 kHz - 80 MHz; +- responses of stand alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- the frequencies selected during the test and the test method used shall be recorded in the test report. + +### 9.5.3 Performance criteria + +The performance criteria of clause 6.1 shall apply. + +## 9.6 Transients and surges, vehicular environment + +### 9.6.1 Definition + +The tests are applicable to UE intended for use in a vehicular environment. + +These tests shall be performed on 12 V and 24 V DC power input. + +These tests shall be performed on a representative configuration of the equipment or a representative configuration of the combination of UE and ancillary equipment. + +These tests assess the ability of UE and ancillary equipment to operate as intended in the event of transients and surges present on the DC power input ports in a vehicular environment. + +### 9.6.2 Test method and level + +The test method shall be in accordance with ISO 7637-2 [15] for nominal 12 V DC powered equipment and nominal 24 V DC powered equipment. The requirements are detailed as follows: + +#### 9.6.2.1 12 V DC powered equipment + +The test pulse severity levels I/II shall apply for nominal 12 V system as specified in table A.1 in accordance with ISO 7637-2 [15]. + +Where the manufacturer declares that the EUT requires a direct connection to the vehicle battery, and the corresponding tests are not carried out, this shall be stated in the test report. + +#### 9.6.2.2 24 V DC powered equipment + +The test pulse severity level I/II shall apply for nominal 24 V system as specified in table A.2 in accordance with ISO 7637-2 [15]. + +Where the manufacturer declares that the EUT requires a direct connection to the vehicle battery, and the corresponding tests are not carried out, this shall be stated in the test report. + +For UE designed to operate at 12 V DC power supply, but operating from a 24 V DC power adapter ancillary, then the UE shall comply with the requirements in 9.6.2.1 and the configuration of the UE and the power adapter shall comply with the requirements of 9.6.2.2. + +### 9.6.3 Performance criteria + +The performance criteria of clause 6.2 shall apply. However, where the equipment is powered without the use of a parallel battery back-up, for pulses 1, 2a, 2b the communications link need not be maintained and may have to be re-established and volatile user data may have been lost. + +## 9.7 Voltage dips and interruptions + +### 9.7.0 General + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the UE or a representative configuration of the combination of UE and ancillary equipment. + +### 9.7.1 Definition + +These tests assess the ability of UE and ancillary equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports. + +### 9.7.2 Test method and level + +The following requirements shall apply. + +The test method shall be in accordance with IEC 61000-4-11 [16]. + +The test levels shall be: + +- a voltage dip corresponding to a reduction of the supply voltage of 60 % for 5 periods; +- a voltage interruption corresponding to a reduction of the supply voltage of > 95 % for 250 periods. + +### 9.7.3 Performance criteria + +The performance criteria of clause 6.2 shall apply. However, in the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) the communications link need not be maintained and may have to be re-established and volatile user data may have been lost. In the event of loss of the communications link or in the event of loss of user data, this fact shall be recorded in the test report, the product description and the user documentation. + +## 9.8 Surges, common and differential mode + +### 9.8.1 Definition + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the UE or a representative configuration of the combination of UE and ancillary equipment. + +These tests assess the ability of UE and ancillary equipment to operate as intended in the event of surges being present at the AC mains power input ports. + +### 9.8.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-5 [17]. + +The following requirements and evaluation of test results shall apply: + +- the test level for ac mains power input ports shall be 1 kV line to ground and 0,5 kV line to line with the output impedance of the surge generator as given in the IEC 61000-4-5 [17]; +- the test generator shall provide the 1,2/50 $\mu$ sec pulse as defined in IEC 61000-4-5 [17]. + +### 9.8.3 Performance criteria + +The performance criteria of clause 6.2 shall apply. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-10 | R4#84bis | R4-1710899 | | | | Specification template | 0.0.1 | +| 2017-12 | RAN4#85 | R4-1714548 | | | | Capture approved Text Proposals in RAN4#85
R4-1712520: TP to 38.124: Scope
R4-1712521: TP to 38.124: Test conditions
R4-1712522: TP to 38.124: Applicability
R4-1712523: TP to 38.124: EMC emissions tests
R4-1712524: TP to 38.124: Immunity tests | 0.1.0 | +| 2017-12 | RAN#78 | RP-172249 | | | | Presentation to TSG RAN for approval | 1.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2018-03 | RAN#79 | RP-180264 | 0001 | | F | Implementation of agreed draft CRs | 15.1.0 | +| 2019-03 | RAN#83 | RP-190401 | 0002 | 2 | F | CR to TS 38.124 on FR1 extension | 15.2.0 | +| 2020-06 | RAN#88 | RP-200986 | 0005 | 1 | F | CR to TS 38.124 adding Methods of measurement and limits for EMC emissions | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0010 | | F | CR to TS 38.124: specification corrections and removal of [], Rel-15 | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0011 | 1 | F | CR to TS 38.124: correction of UE radiated spurious emissions requirement, Rel-15 | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0012 | 1 | F | CR to TS 38.124: correction of the Rx exclusion band, Rel-15 | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0013 | | F | CR to TS 38.124: Performance assessment, Rel-15 | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0014 | | F | CR to TS 38.124: Performance criteria, Rel-15 | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0016 | 1 | B | [EMC] CR TS38.124 CS | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0017 | 1 | B | [EMC] CR TS38.124 dips | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0018 | 1 | B | [EMC] CR TS38.124 EFT | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0019 | 1 | B | [EMC] CR TS38.124 ESD | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0020 | 1 | F | [EMC] CR TS38.124 references | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0023 | 1 | B | [EMC] CR TS38.124 surge | 15.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0024 | 1 | F | [EMC] CR TS38.124 vehicular environment | 15.3.0 | +| 2020-06 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2020-09 | RAN#89 | RP-201512 | 0026 | | A | CR to TS 38.124 combined correction R16 | 16.1.0 | +| 2021-03 | RAN#91 | RP-210117 | 0032 | | A | CR for TS 38.124: Correction of FR1 radiated spurious emissions (R16) | 16.2.0 | +| 2021-06 | RAN#92 | RP-211080 | 0036 | 1 | A | CR to 38.124: TBD removal for the maximum measurement uncertainty for measurements above 12.75GHz, Rel-16 | 16.3.0 | +| 2021-09 | RAN#93 | RP-211922 | 0038 | | A | Big CR for TS 38.124 Maintenance (Rel-16, CAT A) | 16.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Update to Rel-17 version (MCC) | 17.0.0 | +| 2022-06 | RAN#96 | RP-221652 | 0042 | | A | Big CR for TS 38.124 Maintenance (Rel-17, CAT A) | 17.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-09 | RAN#101 | RP-232515 | 0046 | | B | CR to TS 38.124: Introduction of 3 MHz channel bandwidth | 18.0.0 | +| 2023-12 | RAN#102 | RP-233363 | 0048 | | F | CR to TS 38.124 for introduction of 3 MHz channel bandwidth | 18.1.0 | +| 2023-12 | RAN#102 | RP-233364 | 0049 | 1 | B | CR to 38.124: EMC requirements for CA and DC combinations | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38171/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-18/38_series/38171/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..337ab6a7664de25e5b7585674b27e136eb140d56 --- /dev/null +++ b/marked/Rel-18/38_series/38171/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d570f962550f18d4067d843f0fe8ce56c038e0d103bbe600fdb268bd6308e195 +size 25592 diff --git a/marked/Rel-18/38_series/38171/446100c084b94817a19c319fa776b412_img.jpg b/marked/Rel-18/38_series/38171/446100c084b94817a19c319fa776b412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22c84b3b06a2b08b7e7d4936fe7797ad6c8eb627 --- /dev/null +++ b/marked/Rel-18/38_series/38171/446100c084b94817a19c319fa776b412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0e8f02cbc64e51995355c1e294fd2a013321a41d80fe6df2cea5967d685612b +size 64015 diff --git a/marked/Rel-18/38_series/38171/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38171/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bb7a3078fe825e0b6bdad33dc43969e696846e6 --- /dev/null +++ b/marked/Rel-18/38_series/38171/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58aa0deae91ea353d372a980ff4d32e0e43de306da6f900d7ed9525d1327f45b +size 9899 diff --git a/marked/Rel-18/38_series/38171/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38171/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5793fee9744c9b5bb46d8891f962a8f7d3cab103 --- /dev/null +++ b/marked/Rel-18/38_series/38171/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e2cc641cb453377555bba4c19ecbb47266e6f8de0a3e52a28fdae2f00848d85 +size 5236 diff --git a/marked/Rel-18/38_series/38171/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-18/38_series/38171/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb2cbd730df70fa5aae1e8957532bc591f3b0295 --- /dev/null +++ b/marked/Rel-18/38_series/38171/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40b870d7df1e9a6afbc06aef516f2eaf3f2c22e318d5fc56140368061f348b95 +size 68560 diff --git a/marked/Rel-18/38_series/38171/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-18/38_series/38171/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5311ec99e3bcce03e97800cb0a412333a85cba56 --- /dev/null +++ b/marked/Rel-18/38_series/38171/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5ddc1b9760156341a82f4778e4af9e7b9272f69a1ccb9e0b5461a72de130241 +size 24471 diff --git a/marked/Rel-18/38_series/38171/raw.md b/marked/Rel-18/38_series/38171/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..687d5a561d50dcfec3be6de6b15abafa8ca4e63e --- /dev/null +++ b/marked/Rel-18/38_series/38171/raw.md @@ -0,0 +1,1643 @@ + + +# 3GPP TS 38.171 V18.0.1 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Requirements for support of Assisted Global Navigation Satellite System (A-GNSS) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 11 | +| 3.4 Test tolerances..... | 12 | +| 4 General..... | 12 | +| 4.1 Introduction ..... | 12 | +| 4.2 Measurement parameters..... | 12 | +| 4.2.1 UE based A-GNSS measurement parameters ..... | 12 | +| 4.2.2 UE assisted A-GNSS measurement parameters ..... | 12 | +| 4.3 Response time ..... | 12 | +| 4.4 Time assistance ..... | 12 | +| 4.4.1 Use of fine time assistance ..... | 13 | +| 4.5 RRC states..... | 13 | +| 4.6 Error definitions ..... | 13 | +| 5 A-GNSS minimum performance requirements (UE supports A-GPS L1 C/A only) ..... | 14 | +| 5.0 Introduction ..... | 14 | +| 5.1 Sensitivity..... | 14 | +| 5.1.1 Coarse time assistance..... | 14 | +| 5.1.1.1 Minimum requirements (Coarse time assistance)..... | 15 | +| 5.1.2 Fine time assistance..... | 15 | +| 5.1.2.1 Minimum requirements (Fine time assistance)..... | 15 | +| 5.2 Nominal accuracy..... | 15 | +| 5.2.1 Minimum requirements (nominal accuracy) ..... | 16 | +| 5.3 Dynamic range ..... | 16 | +| 5.3.1 Minimum requirements (dynamic range)..... | 16 | +| 5.4 Multi-path scenario ..... | 17 | +| 5.4.1 Minimum requirements (multi-path scenario)..... | 17 | +| 5.5 Moving scenario and periodic update ..... | 17 | +| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 18 | +| 6 A-GNSS minimum performance requirements (UE supports other or additional GNSSs)..... | 18 | +| 6.0 Introduction ..... | 18 | +| 6.1 Sensitivity..... | 19 | +| 6.1.1 Coarse time assistance..... | 19 | +| 6.1.1.1 Minimum requirements (Coarse time assistance)..... | 19 | +| 6.1.2 Fine time assistance..... | 20 | +| 6.1.2.1 Minimum requirements (Fine time assistance)..... | 20 | +| 6.2 Nominal accuracy..... | 20 | +| 6.2.1 Minimum requirements (nominal accuracy) ..... | 21 | +| 6.3 Dynamic range ..... | 21 | +| 6.3.1 Minimum requirements (dynamic range)..... | 22 | +| 6.4 Multi-path scenario ..... | 22 | +| 6.4.1 Minimum requirements (multi-path scenario)..... | 23 | +| 6.5 Moving scenario and periodic update ..... | 23 | +| 6.5.1 Minimum requirements (moving scenario and periodic update)..... | 24 | + +| | | +|-----------------------------------------------------------------------------------------------------|-----------| +| Annex A (normative): Test cases ..... | 26 | +| A.1 Conformance tests..... | 26 | +| A.2 Requirement classification for statistical testing ..... | 26 | +| Annex B (normative): Test conditions..... | 27 | +| B.1 General..... | 27 | +| B.1.1 Parameter values ..... | 27 | +| B.1.2 Time assistance ..... | 27 | +| B.1.3 GNSS reference time..... | 27 | +| B.1.4 Reference and UE locations..... | 28 | +| B.1.5 Satellite constellation and assistance data..... | 28 | +| B.1.5.1 UE supports A-GPS L1 C/A only ..... | 28 | +| B.1.5.2 UE supports other A-GNSSs..... | 28 | +| B.1.6 Atmospheric delays..... | 28 | +| B.1.7 E-UTRA or NR frequency and frequency error..... | 28 | +| B.1.8 Information elements..... | 29 | +| B.1.9 GNSS signals..... | 29 | +| B.1.10 RESET UE POSITIONING STORED INFORMATION Message ..... | 29 | +| B.1.11 GNSS system time offsets..... | 29 | +| B.1.12 Sensors ..... | 29 | +| B.1.13 EN-DC band combinations for testing A-GNSS sensitivity ..... | 29 | +| B.1.13.1 EN-DC band combination groups ..... | 29 | +| B.1.13.2 Applicable EN-DC band combinations for verifying A-GNSS sensitivity requirements ..... | 33 | +| B.1.13.3 Test frequencies for EN-DC band combinations..... | 34 | +| Annex C (normative): Propagation conditions..... | 35 | +| C.1 Static propagation conditions..... | 35 | +| C.2 Multi-path case..... | 35 | +| Annex D (normative): Measurement sequence chart ..... | 37 | +| D.1 General..... | 37 | +| D.2 TTFF measurement sequence chart ..... | 37 | +| D.3 Moving scenario and periodic update measurement sequence chart ..... | 38 | +| Annex E (normative): Assistance data required for testing..... | 41 | +| E.1 Introduction..... | 41 | +| E.2 GNSS assistance data..... | 41 | +| Annex F (normative): Converting UE-assisted measurement reports into position estimates..... | 45 | +| F.1 Introduction..... | 45 | +| F.2 UE measurement reports..... | 45 | +| F.3 WLS position solution ..... | 45 | +| Annex G (informative): Change history..... | 48 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document establishes the minimum requirements for both UE based and UE assisted FDD or TDD A-GNSS terminals which have NG-RAN access via gNB (in SA NR, NR-DC or NE-DC NR operation mode [2]) or via ng-eNB (in EN-DC operation mode [2]) and which are supporting A-GNSS in 5GS via LPP [3] between UE and LMF as described in TS 38.305 [17]. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity", Stage 2. +- [3] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [4] 3GPP TS 38.215: "NR; Physical layer; Measurements". +- [5] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [6] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. +- [7] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996. +- [8] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119. +- [9] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)". +- [10] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005. +- [11] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, September 4, 2008. +- [12] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.1, July 31, 2009. +- [13] Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2, February 2014, European Union. +- [14] Global Navigation Satellite System GLONASS Interface Control Document, Version 5.1, 2008. +- [15] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. + +- [16] BDS-SIS-ICD-B1I-3.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1I (Version 3.0)", China Satellite Navigation Office, February 2019. +- [17] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [18] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [19] 3GPP TS 37.571-1: " User Equipment (UE) conformance specification for UE positioning; Part 1: Terminal conformance". +- [20] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". +- [21] BDS-SIS-ICD-B1C-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1C (Version 1.0)", December, 2017. +- [22] BDS-SIS-ICD-B2a-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B2a (Version 1.0)", December, 2017. +- [23] BDS-SIS-ICD-B3I-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B3I (Version 1.0)", February, 2018. +- [24] IRNSS Signal-In-Space (SPS) Interface Control Document (ICD) for standard positioning service version 1.1, Aug 2017. + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply: + +**EN-DC:** E-UTRA-NR Dual Connectivity as defined in TS 37.340 [2]. + +**en-gNB:** as defined in TS 37.340 [2]. + +**gNB:** as defined in in TS 38.300 [17]. + +**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna + +**NE-DC:** NR-E-UTRA Dual Connectivity as defined in TS 37.340 [2]. + +**ng-eNB:** as defined in TS 38.300 [17]. + +**NR-DC:** NR-NR Dual Connectivity as defined in TS 37.340 [2]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----|----------------------------------------------------------------------| +| B1I | BeiDou B1I navigation signal with carrier frequency of 1561.098 MHz. | +| B1C | BeiDou B1C navigation signal with carrier frequency of 1575.420 MHz. | +| B2a | BeiDou B2a navigation signal with carrier frequency of 1176.450 MHz. | +| B3I | BeiDou B3I navigation signal with carrier frequency of 1268.520 MHz. | +| E1 | Galileo E1 navigation signal with carrier frequency of 1575.420 MHz. | +| E5 | Galileo E5 navigation signal with carrier frequency of 1191.795 MHz. | +| E6 | Galileo E6 navigation signal with carrier frequency of 1278.750 MHz. | + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------| +| G1 | GLONASS navigation signal in the L1 sub-bands with carrier frequencies $1602 \text{ MHz} \pm k \times 562.5 \text{ kHz}$ . | +| G2 | GLONASS navigation signal in the L2 sub-bands with carrier frequencies $1246 \text{ MHz} \pm k \times 437.5 \text{ kHz}$ . | +| k | GLONASS channel number, $k = -7 \dots 13$ . | +| L1 C/A | GPS or QZSS L1 navigation signal carrying the Coarse/Acquisition code with carrier frequency of 1575.420 MHz. | +| L1C | GPS or QZSS L1 Civil navigation signal with carrier frequency of 1575.420 MHz. | +| L2C | GPS or QZSS L2 Civil navigation signal with carrier frequency of 1227.600 MHz. | +| L5 | GPS or QZSS or NavIC L5 navigation signal with carrier frequency of 1176.450 MHz. | +| G | Geometry Matrix. | +| $\rho_{GNSS_m,i}$ | Measured pseudo-range of satellite $i$ of GNSS $_m$ . | +| W | Weighting Matrix. | +| $\mathbf{l}_{GNSS_m,i}$ | Line of sight unit vector from the user to the satellite $i$ of GNSS $_m$ . | +| $\mathbf{x}$ | State vector of user position and clock bias. | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------------------------------------------------------| +| 5GS | 5G System | +| A-GNSS | Assisted Global Navigation Satellite System | +| A-GPS | Assisted - Global Positioning System | +| AWGN | Additive White Gaussian Noise | +| BDS | BeiDou Navigation Satellite System | +| C/A | Coarse/Acquisition | +| DC | Dual Connectivity | +| DUT | Device Under Test | +| ECEF | Earth Centred, Earth Fixed | +| E-UTRA | Evolved UMTS Terrestrial Radio Access | +| E-UTRAN | Evolved UMTS Terrestrial Radio Access Network | +| EN-DC | E-UTRA-NR Dual Connectivity | +| FDD | Frequency Division Duplex | +| GEO | Geostationary Earth Orbit | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| HDOP | Horizontal Dilution Of Precision | +| ICD | Interface Control Document | +| IGSO | Inclined Geosynchronous Satellite Orbit | +| IRNSS | Indian Regional Navigation Satellite System | +| IS | Interface Specification | +| LMF | Location Management Function | +| LOS | Line Of Sight | +| LPP | LTE Positioning Protocol | +| MEO | Medium Earth Orbit | +| NavIC | NAVigation with Indian Constellation | +| NE-DC | NR-E-UTRA Dual Connectivity | +| NR | NR Radio Access | +| NR-DC | NR-NR Dual Connectivity | +| QZSS | Quasi-Zenith Satellite System | +| RRC | Radio Resource Control | +| SBAS | Space Based Augmentation System | +| SFN | System Frame Number | +| SS | System Simulator | +| SV | Space Vehicle | +| TDD | Time Division Duplex | +| TOW | Time Of Week | +| TTFF | Time To First Fix | + +| | | +|--------|----------------------------| +| UE | User Equipment | +| WLS | Weighted Least Square | +| WGS-84 | World Geodetic System 1984 | + +## 3.4 Test tolerances + +The requirements given in the present document make no allowance for measurement uncertainty. The test specification TS 37.571-1 [19] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle. + +Shared Risk is defined in ETR 273-1-2 [7], clause 6.5. + +# --- 4 General + +## 4.1 Introduction + +The present document defines the minimum requirements for both UE based and UE assisted FDD or TDD A-GNSS terminals which have NG-RAN access via gNB (in SA NR, NR-DC or NE-DC operation mode [2]) or via ng-eNB (in EN-DC operation mode [2]) and which are supporting A-GNSS in 5GS via LPP [3] between UE and LMF as described in TS 38.305 [17]. + +## 4.2 Measurement parameters + +### 4.2.1 UE based A-GNSS measurement parameters + +In case of UE-based A-GNSS, the measurement parameters are contained in the *GNSS-LocationInformation* IE which is included in the *A-GNSS-ProvideLocationInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude. + +### 4.2.2 UE assisted A-GNSS measurement parameters + +In case of UE-assisted A-GNSS, the measurement parameters are contained in the *GNSS-SignalMeasurementInformation* IE which is included in the *A-GNSS-ProvideLocationInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION. The measurement parameters in case of UE-assisted A-GNSS are the UE GNSS code phase measurements, as specified in TS 38.215 [4]. The UE GNSS code phase measurements are converted into a horizontal position estimate using the procedure detailed in Annex F. + +## 4.3 Response time + +Max Response Time is defined as the time starting from the moment that the UE receives the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION. The response times specified for all test cases are TTFF unless otherwise stated, i.e. the UE shall not re-use any information on GNSS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' is defined in TS 38.509 [9] clause 5.6 for the purpose of deleting this information and is detailed in clause B.1.10. + +## 4.4 Time assistance + +Time assistance is the provision of GNSS time to the UE from the network via LPP messages. Currently two different GNSS time assistance methods can be provided by the network. + +- a) Coarse time assistance is always provided by the network and provides current GNSS time to the UE. The time provided is within $\pm 2$ seconds of GNSS system time. It is signalled to the UE by means of the *gnss-DayNumber* and *gnss-TimeOfDay* fields in the *gnss-SystemTime* IE. +- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GNSS system time and the current E-UTRAN or NR time. The accuracy of this relationship is $\pm 10 \mu\text{s}$ of the actual relationship. This addresses the case when the network can provide an improved GNSS time accuracy. It is signalled to the UE by means of the *gnss-SystemTime* IE and the *gnss-ReferenceTimeForCells* IE. + +The specific GNSS system time is identified through the *gnss-TimeID* field of the *GNSS-SystemTime* IE. In case where several GNSSs are used in the tests, only one *gnss-TimeID* is used to determine the Time of Day. For all the constellations, the *gnss-TimeModels* IE shall be available at the SS, as specified in Annex E. + +### 4.4.1 Use of fine time assistance + +The use of fine time assistance to improve the GNSS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in clause 5.1.2 for UEs that support A-GPS L1 C/A only and in clause 6.1.2 for UEs that support other GNSSs. + +## 4.5 RRC states + +The minimum A-GNSS performance requirements are specified in clauses 5 and 6 for RRC\_CONNECTED state. The test and verification procedures are separately defined in annex B. + +## 4.6 Error definitions + +The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the LPP message of type PROVIDE LOCATION INFORMATION and the actual position of the UE in the test case considered. + +## 4.7 UEs supporting multiple constellations + +Minimum performance requirements are defined for each global GNSS constellation (BDS, Galileo, GLONASS, GPS/Modernized GPS). UEs supporting multiple global constellations shall meet the minimum performance requirements for a combined scenario where each UE supported constellation is simulated. + +NOTE: For test cases where signals from ‘GPS’ and ‘Modernized GPS’ are included, ‘GPS’ and ‘Modernized GPS’ are considered as a single constellation, unless otherwise specified. + +## 4.8 UEs supporting multiple signals + +For UEs supporting multiple signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.8-1. The individual test scenarios in clause 6 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 6 plus the relative power level defined in Table 4.8-1. + +**Table 4.8-1: Relative signal power levels for each signal type for each GNSS** + +| | BDS | | | Galileo | | GLONASS | | GPS/Modernized GPS | | QZSS | | SBAS | | NavIC | | +|--|-----|----|-------|---------|------|---------|------|--------------------|------|--------|------|------|------|-------|------| +| | B1I | D1 | 0 dB | E1 | 0 dB | G1 | 0 dB | L1 C/A | 0 dB | L1 C/A | 0 dB | L1 | 0 dB | L5 | 0 dB | +| | | D2 | +5 dB | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | +|--------------------------------------------------------|------|-------------------|-------|----|-------|----|-------|-----|---------|-----|---------|--|--|--|--| +| Signal power levels relative to reference power levels | B1 C | D MEO | +4 dB | E6 | +2 dB | G2 | -6 dB | L1C | +1.5 dB | L1C | +1.5 dB | | | | | +| | | D IGSO | +2dB | | | | | | | | | | | | | +| | B2a | D MEO | +7 dB | E5 | +2 dB | | | L2C | -1.5 dB | L2C | -1.5 dB | | | | | +| | | D IGSO | +5dB | | | | | | | | | | | | | +| | B3I | D1 | 0 dB | | | | | L5 | +3.6 dB | L5 | +3.6 dB | | | | | +| | | D2 | +5 dB | | | | | | | | | | | | | + +NOTE 1: For test cases which involve “Modernized GPS”, the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports “GPS” in addition to “Modernized GPS”. + +NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately. + +NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites for B1I and B3I signal types and D2 represents GEO satellites for B1I and B3I signal type. + +NOTE 4: For test cases which involve "BDS", DMEO represents MEO satellites for B1C and B2a signal types and DIGSO represents IGSO satellites for B1C and B2a signal type. + +NOTE 5: For test cases involving NavIC all satellites are either GEO or IGSO as per ICD [24] + +# 5 A-GNSS minimum performance requirements (UE supports A-GPS L1 C/A only) + +## 5.0 Introduction + +The minimum performance requirements specified in clause 5 apply for UEs that support A-GPS L1 C/A only. The requirements for UEs that support other or additional A-GNSSs are specified in clause 6. + +The A-GNSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS L1 C/A measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network. + +In the following clauses the minimum performance requirements are based on availability of the assistance data information and messages defined in annexes D and E. + +## 5.1 Sensitivity + +A sensitivity requirement is essential for verifying the performance of A-GNSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance. + +### 5.1.1 Coarse time assistance + +In this test case 8 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.1.1-1: Test parameters** + +| Parameters | Unit | Value | +|--------------------------------------------|---------|------------| +| Number of generated satellites | - | 8 | +| HDOP Range | - | 1.1 to 1.6 | +| Propagation conditions | - | AWGN | +| GNSS Coarse time assistance error range | seconds | $\pm 2$ | +| GPS L1 C/A Signal for one satellite | dBm | -142 | +| GPS L1 C/A Signal for remaining satellites | dBm | -147 | + +#### 5.1.1.1 Minimum requirements (Coarse time assistance) + +The position estimates shall meet the accuracy and response time specified in Table 5.1.1.1-1. + +**Table 5.1.1.1-1: Minimum requirements (coarse time assistance)** + +| Success rate | 2-D position error | Max response time | +|--------------|--------------------|-------------------| +| 95 % | 100 m | 20 s | + +### 5.1.2 Fine time assistance + +This requirement is only valid for fine time assistance capable UEs. In this requirement 8 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.1.2-1: Test parameters for fine time assistance capable terminals** + +| Parameters | Unit | Value | +|---------------------------------------------|---------------|------------| +| Number of generated satellites | - | 8 | +| HDOP Range | - | 1.1 to 1.6 | +| Propagation conditions | - | AWGN | +| GNSS Coarse time assistance error range | seconds | $\pm 2$ | +| GPS L1 C/A Fine time assistance error range | $\mu\text{s}$ | $\pm 10$ | +| GPS L1 C/A Signal for all satellites | dBm | -147 | + +#### 5.1.2.1 Minimum requirements (Fine time assistance) + +The position estimates shall meet the accuracy and response time requirements in Table 5.1.2.1-1. + +**Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals** + +| Success rate | 2-D position error | Max response time | +|--------------|--------------------|-------------------| +| 95 % | 100 m | 20 s | + +## 5.2 Nominal accuracy + +Nominal accuracy requirement verifies the accuracy of A-GNSS position estimate in ideal conditions. The primary aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate. + +In this requirement 8 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.2-1: Test parameters** + +| Parameters | Unit | Value | +|-----------------------------------------|---------|------------| +| Number of generated satellites | - | 8 | +| HDOP Range | - | 1.1 to 1.6 | +| Propagation conditions | - | AWGN | +| GNSS Coarse time assistance error range | seconds | $\pm 2$ | +| GPS L1 C/A Signal for all satellites | dBm | -130 | + +### 5.2.1 Minimum requirements (nominal accuracy) + +The position estimates shall meet the accuracy and response time requirements in Table 5.2.1-1. + +**Table 5.2.1-1: Minimum requirements** + +| Success rate | 2-D position error | Max response time | +|--------------|--------------------|-------------------| +| 95 % | 30 m | 20 s | + +## 5.3 Dynamic range + +The aim of a dynamic range requirement is to ensure that a GNSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.3-1: Test parameters** + +| Parameters | Unit | Value | +|-------------------------------------------------|---------|------------| +| Number of generated satellites | - | 6 | +| HDOP Range | - | 1.4 to 2.1 | +| GNSS Coarse time assistance error range | seconds | $\pm 2$ | +| Propagation conditions | - | AWGN | +| GPS L1 C/A Signal for 1 st satellite | dBm | -129 | +| GPS L1 C/A Signal for 2 nd satellite | dBm | -135 | +| GPS L1 C/A Signal for 3 rd satellite | dBm | -141 | +| GPS L1 C/A Signal for 4 th satellite | dBm | -147 | +| GPS L1 C/A Signal for 5 th satellite | dBm | -147 | +| GPS L1 C/A Signal for 6 th satellite | dBm | -147 | + +### 5.3.1 Minimum requirements (dynamic range) + +The position estimates shall meet the accuracy and response time requirements in Table 5.3.1-1. + +**Table 5.3.1-1: Minimum requirements** + +| Success rate | 2-D position error | Max response time | +|--------------|--------------------|-------------------| +| 95 % | 100 m | 20 s | + +## 5.4 Multi-path scenario + +The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate. + +In this requirement 5 satellites are generated for the terminal. Two of the satellites have one tap channel representing LOS signal. The three other satellites have two-tap channel, where the first tap represents LOS signal and the second reflected and attenuated signal as specified in Annex C.2. + +**Table 5.4-1: Test parameters** + +| Parameters | Unit | Value | +|--------------------------------------------------------------------------------------------------------------------------|---------|-------------------------------------------------------| +| Number of generated satellites (Satellites 1, 2 unaffected by multi-path)
(Satellites 3, 4, 5 affected by multi-path) | - | 5 | +| GNSS Coarse time assistance error range | seconds | ±2 | +| HDOP Range | - | 1.8 to 2.5 | +| GPS L1 C/A Signal for satellite 1, 2 | dBm | -130 | +| GPS L1 C/A Signal for satellite 3, 4, 5 | dBm | LOS signal of -130 dBm, multi-path signal of -136 dBm | + +### 5.4.1 Minimum requirements (multi-path scenario) + +The position estimates shall meet the accuracy and response time requirements in Table 5.4.1-1. + +**Table 5.4.1-1: Minimum requirements** + +| Success rate | 2-D position error | Max response time | +|--------------|--------------------|-------------------| +| 95 % | 100 m | 20 s | + +## 5.5 Moving scenario and periodic update + +The purpose of the test case is to verify the receiver's capability to produce GNSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GNSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a TTFF test. + +In this requirement 5 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds. + +The UE moves on a rectangular trajectory of 940 m by 1 440 m with rounded corner defined in Figure 5.5-1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle. + +**Table 5.5-1: Trajectory Parameters** + +| Parameter | Distance (m) | Speed (km/h) | +|----------------------------------|--------------|-------------------------| +| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20 | 25 | +| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250 | 25 to 100 and 100 to 25 | +| $l_{13}$ | 400 | 100 | +| $l_{23}$ | 900 | 100 | + +![Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case. The diagram shows a rectangle with a width of 1 440 m and a height of 940 m. The bottom-left corner has a radius r = 20 m. The horizontal axis is labeled with l21, l22, l23, l24, and l25. The vertical axis is labeled with l11, l12, l13, l14, and l15.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case. The diagram shows a rectangle with a width of 1 440 m and a height of 940 m. The bottom-left corner has a radius r = 20 m. The horizontal axis is labeled with l21, l22, l23, l24, and l25. The vertical axis is labeled with l11, l12, l13, l14, and l15. + +Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case + +Table 5.5-2: Test Parameters + +| Parameters | Unit | Value | +|--------------------------------------|------|------------| +| Number of generated satellites | - | 5 | +| HDOP Range | - | 1.8 to 2.5 | +| Propagation condition | - | AWGN | +| GPS L1 C/A signal for all satellites | dBm | -130 | + +### 5.5.1 Minimum requirements (moving scenario and periodic update) + +The position estimates shall meet the accuracy requirement of Table 5.13 with the periodical reporting interval defined in Table 5.13 after the first reported position estimates. + +NOTE: In the actual testing the UE may report error messages until it is able to acquire GNSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in Table 5.5.1-1. + +Table 5.5.1-1: Minimum requirements + +| Success Rate | 2-D position error | Periodical reporting interval | +|--------------|--------------------|-------------------------------| +| 95 % | 100 m | 2 s | + +# 6 A-GNSS minimum performance requirements (UE supports other or additional GNSSs) + +## 6.0 Introduction + +The minimum performance requirements specified in clause 6 apply for UEs that support other A-GNSSs than GPS L1 C/A, or multiple A-GNSSs which may or may not include GPS L1 C/A. The requirements for UEs that support A-GPS L1 C/A only are specified in clause 5. + +The A-GNSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GNSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network. + +In the following clauses the minimum performance requirements are based on availability of the assistance data information and messages defined in annexes D and E. + +## 6.1 Sensitivity + +A sensitivity requirement is essential for verifying the performance of A-GNSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance. + +### 6.1.1 Coarse time assistance + +In this test case 6 satellites are generated for the terminal for single constellation and dual constellation, and 7 satellites are generated for triple constellation. AWGN channel model is used. + +**Table 6.1.1-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 6.1.1-2 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| BDS | Reference high signal power level | dBm | -136 | +| | Reference low signal power level | dBm | -145 | +| Galileo | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| GLONASS | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| GPS (1) | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | + +NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. +NOTE 2: 7 satellites apply only for case of triple constellation. + +**Table 6.1.1-2: Power level and satellite allocation** + +| | | Satellite allocation for each constellation | | | +|----------------------|-------------------|---------------------------------------------|--------|--------| +| | | GNSS-1 (1) | GNSS-2 | GNSS-3 | +| Single constellation | High signal level | 1 | - | - | +| | Low signal level | 5 | - | - | +| Dual constellation | High signal level | 1 | - | - | +| | Low signal level | 2 | 3 | - | +| Triple constellation | High signal level | 1 | - | - | +| | Low signal level | 2 | 2 | 2 | + +Note 1: GNSS-1, i.e. the system having the satellite with high signal level, shall be selected by the device manufacturer. + +#### 6.1.1.1 Minimum requirements (Coarse time assistance) + +The position estimates shall meet the accuracy and response time specified in Table 6.1.1.1-1. + +**Table 6.1.1.1-1: Minimum requirements (coarse time assistance)** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +### 6.1.2 Fine time assistance + +This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal for single constellation and dual constellation, and 7 satellites are generated for triple constellation. AWGN channel model is used. + +**Table 6.1.2-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 6.1.2-2 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| | GNSS fine time assistance error range | µs | ±10 | +| BDS | Reference signal power level | dBm | -147 | +| Galileo | Reference signal power level | dBm | -147 | +| GLONASS | Reference signal power level | dBm | -147 | +| GPS (1) | Reference signal power level | dBm | -147 | + +NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. +NOTE 2: 7 satellites apply only for case of triple constellation. + +**Table 6.1.2-2: Satellite allocation** + +| | Satellite allocation for each constellation | | | +|----------------------|---------------------------------------------|--------|--------| +| | GNSS-1 | GNSS-2 | GNSS-3 | +| Single constellation | 6 | - | - | +| Dual constellation | 3 | 3 | - | +| Triple constellation | 3 | 2 | 2 | + +#### 6.1.2.1 Minimum requirements (Fine time assistance) + +The position estimates shall meet the accuracy and response time requirements in Table 6.1.2.1-1. + +**Table 6.1.2.1-1: Minimum requirements for fine time assistance capable terminals** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 6.2 Nominal accuracy + +Nominal accuracy requirement verifies the accuracy of A-GNSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal for single constellation and dual constellation, and 7 satellites are generated for triple constellation. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in Table 6.2-2. + +**Table 6.2-1: Test parameters** + +| System | Parameters | Unit | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|---------|-------------------------------------------| +| | Number of generated satellites per system | - | See Table 6.2-2 | +| | Total number of generated satellites | - | 6 or 7 (2) or 8 (3) | +| | HDOP Range | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| BDS | Reference signal power level for all satellites | dBm | -133 | +| Galileo | Reference signal power level for all satellites | dBm | -127 | +| GLONASS | Reference signal power level for all satellites | dBm | -131 | +| GPS (1) | Reference signal power level for all satellites | dBm | -128.5 | +| QZSS | Reference signal power level for all satellites | dBm | -128.5 | +| SBAS | Reference signal power level for all satellites | dBm | -131 | +| NavIC | Reference signal power level for all satellites | dBm | -129 | +| NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | +| NOTE 2: 7 satellites apply for case of single or dual constellation and SBAS or NavIC is supported or case of triple constellation and SBAS or NavIC is not supported. | | | | +| NOTE 3: 8 satellites apply only for case of triple constellation and SBAS is supported. | | | | + +If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support. If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario. If NavIC is supported, the NavIC satellite with the highest elevation will be added to the scenario. + +**Table 6.2-2: Satellite allocation** + +| | Satellite allocation for each constellation | | | | | +|------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|------|-------| +| | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | SBAS | NavIC | +| Single constellation | 6 | -- | -- | 1 | 1 | +| Dual constellation | 3 | 3 | -- | 1 | 1 | +| Triple constellation | 3 | 2 | 2 | 1 | 1 | +| NOTE 1: GNSS refers to global systems i.e. BDS, Galileo, GLONASS, GPS. | | | | | | + +### 6.2.1 Minimum requirements (nominal accuracy) + +The position estimates shall meet the accuracy and response time requirements in Table 6.2.1-1. + +**Table 6.2.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 15 m | 20 s | + +## 6.3 Dynamic range + +The aim of a dynamic range requirement is to ensure that a GNSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal for single constellation and dual constellation, and 7 satellites are generated for triple constellation. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 6.3-2. AWGN channel model is used. + +**Table 6.3-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 6.3-2 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP Range | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| BDS | Reference high signal power level | dBm | -133.5 | +| | Reference low signal power level | dBm | -145 | +| Galileo | Reference high signal power level | dBm | -127.5 | +| | Reference low signal power level | dBm | -147 | +| GLONASS | Reference high signal power level | dBm | -131.5 | +| | Reference low signal power level | dBm | -147 | +| GPS (1) | Reference high signal power level | dBm | -129 | +| | Reference low signal power level | dBm | -147 | + +NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. +NOTE 2: 7 satellites apply only for case of triple constellation. + +**Table 6.3-2: Power level and satellite allocation** + +| | | Satellite allocation for each constellation | | | +|----------------------|-------------------|---------------------------------------------|-----------------------|-----------------------| +| | | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | +| Single constellation | High signal level | 2 | -- | -- | +| | Low signal level | 4 | -- | -- | +| Dual constellation | High signal level | 1 | 1 | -- | +| | Low signal level | 2 | 2 | -- | +| Triple constellation | High signal level | 1 | 1 | 1 | +| | Low signal level | 2 | 1 | 1 | + +NOTE 1: GNSS refers to global systems i.e. BDS, Galileo, GLONASS, GPS. + +### 6.3.1 Minimum requirements (dynamic range) + +The position estimates shall meet the accuracy and response time requirements in Table 6.3.1-1. + +**Table 6.3.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 6.4 Multi-path scenario + +The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal for single constellation and dual constellation, and 7 satellites are generated for triple constellation. Some of the satellites have a one tap channel representing the LOS signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in Table 6.4-2. The channel model as specified in Annex C.2 further depends on the generated signal. + +**Table 6.4-1: Test parameter** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 6.14 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| BDS | Reference signal power level | dBm | -133 | +| Galileo | Reference signal power level | dBm | -127 | +| GLONASS | Reference signal power level | dBm | -131 | +| GPS (1) | Reference signal power level | dBm | -128.5 | + +NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. +NOTE 2: 7 satellites apply only for case of triple constellation. + +**Table 6.4-2: Channel model allocation** + +| | | Channel model allocation for each constellation | | | +|----------------------|-----------------|-------------------------------------------------|--------|--------| +| | | GNSS-1 | GNSS-2 | GNSS-3 | +| Single constellation | One-tap channel | 2 | -- | -- | +| | Two-tap channel | 4 | -- | -- | +| Dual constellation | One-tap channel | 1 | 1 | -- | +| | Two-tap channel | 2 | 2 | -- | +| Triple constellation | One-tap channel | 1 | 1 | 1 | +| | Two-tap channel | 2 | 1 | 1 | + +### 6.4.1 Minimum requirements (multi-path scenario) + +The position estimates shall meet the accuracy and response time requirements in Table 6.4.1-1. + +**Table 6.4.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 6.5 Moving scenario and periodic update + +The purpose of the test case is to verify the receiver's capability to produce GNSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GNSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a TTFF test. + +In this requirement 6 satellites are generated for the terminal for single constellation and dual constellation, and 7 satellites are generated for triple constellation. The UE is requested to use periodical reporting with a reporting interval of 2 seconds. + +The UE moves on a rectangular trajectory of 940 m by 1 440 m with rounded corner defined in Figure 6.1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle. + +Table 6.5-1: Trajectory Parameters + +| Parameter | Distance (m) | Speed (km/h) | +|----------------------------------|--------------|-------------------------| +| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20 | 25 | +| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250 | 25 to 100 and 100 to 25 | +| $l_{13}$ | 400 | 100 | +| $l_{23}$ | 900 | 100 | + +![Diagram of a rectangular trajectory. The rectangle has a width of 1 440 m and a height of 940 m. The bottom-left corner is labeled with a radius r = 20 m. The top-left corner is marked with l15 and l14. The bottom-left corner is marked with l12 and l11. The bottom edge is marked with l21, l22, l23, l24, and l25. The left edge is marked with l15, l14, l13, l12, and l11. The right edge is marked with l25, l24, l23, l22, and l21.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Diagram of a rectangular trajectory. The rectangle has a width of 1 440 m and a height of 940 m. The bottom-left corner is labeled with a radius r = 20 m. The top-left corner is marked with l15 and l14. The bottom-left corner is marked with l12 and l11. The bottom edge is marked with l21, l22, l23, l24, and l25. The left edge is marked with l15, l14, l13, l12, and l11. The right edge is marked with l25, l24, l23, l22, and l21. + +Figure 6.5-1: Rectangular trajectory of the moving scenario and periodic update test case + +Table 6.5-2: Test Parameters + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 6.18 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP Range per system | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| BDS | Reference signal power level for all satellites | dBm | -133 | +| Galileo | Reference signal power level for all satellites | dBm | -127 | +| GLONASS | Reference signal power level for all satellites | dBm | -131 | +| GPS (1) | Reference signal power level for all satellites | dBm | -128.5 | +| NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | +| NOTE 2: 7 satellites apply only for case of triple constellation. | | | | + +Table 6.5-3: Satellite allocation + +| | Satellite allocation for each constellation | | | +|------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------| +| | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | +| Single constellation | 6 | -- | -- | +| Dual constellation | 3 | 3 | -- | +| Triple constellation | 3 | 2 | 2 | +| NOTE 1: GNSS refers to global systems i.e. BDS, Galileo, GLONASS, GPS. | | | | + +### 6.5.1 Minimum requirements (moving scenario and periodic update) + +The position estimates shall meet the accuracy requirement of Table 6.5.1-1 with the periodical reporting interval defined in Table 6.5.1-1 after the first reported position estimates. + +NOTE: In the actual testing the UE may report error messages until it is able to acquire GNSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in Table 6.5.1-1. + +**Table 6.5.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Periodical reporting interval | +|---------------|---------------------|---------------------------|--------------------------------------| +| All | 95 % | 50 m | 2 s | + +# --- Annex A (normative): Test cases + +## A.1 Conformance tests + +The conformance tests for E-UTRA A-GNSS specified in TS 37.571-1 [19]. Statistical interpretation of the requirements is described in clause A.2. + +## A.2 Requirement classification for statistical testing + +Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested. + +Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for. + +When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in TS 37.571-1 [19]. + +# Annex B (normative): Test conditions + +## B.1 General + +This annex specifies the additional parameters that are needed for the test cases specified in clauses 5 and 6 and applies to all tests unless otherwise stated. + +### B.1.1 Parameter values + +Additionally, amongst all the listed parameters (see annex E), the following values for some important parameters are to be used in the LPP Request Location Information message. + +**Table B.1: Parameter values** + +| Information element | Value - TTFF tests (except nominal accuracy test) | Value - TTFF tests (nominal accuracy test) | Value - Periodic tests | +|--------------------------------------|---------------------------------------------------|--------------------------------------------|-----------------------------------------| +| periodicalReporting | Not present | Not present | Present | +| > reportingAmount | N/A | N/A | 'ra-Infinity' (Infinite) (1) | +| > reportingInterval | N/A | N/A | 'ri2' (2 seconds) | +| qos | | | | +| > horizontalAccuracy | | | | +| >> accuracy (test cases in clause 5) | 19 (51.2 m) | 10 (15.9 m) | 19 (51.2 m) | +| >> accuracy (test cases in clause 6) | 19 (51.2 m) | 6 (7.7 m) | 13 (24.5 m) | +| > responseTime | 20 (seconds) | 20 (seconds) | Not present | + +NOTE 1: Infinite means during the complete test time. + +In the Sensitivity test case with Fine Time Assistance, the following parameter values are used in the LPP Provide Assistance Data message. + +**Table B.2: Parameters for Fine Time Assistance test** + +| Information element | Value | +|------------------------------|---------------| +| GNSS-ReferenceTimeForOneCell | | +| > networkTime | | +| >> frameDrift | 0 | +| > referenceTimeUnc | 24 (11.11 µs) | + +### B.1.2 Time assistance + +For every Test Instance in each TTFF test case, the IE *gnss-TimeOfDay* shall have a random offset, relative to GNSS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution. + +In addition, for every Fine Time Assistance Test Instance the IE *networkTime* shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution. + +For the Moving Scenario and Periodic Update Test Case the IE *gnss-TimeOfDay* shall be set to the nominal value. + +### B.1.3 GNSS reference time + +For every Test Instance in each TTFF test case, the GNSS reference time shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix. + +### B.1.4 Reference and UE locations + +There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %. + +For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions. + +For test cases which include satellites from regional systems, such as QZSS, NavIC and SBAS, the reference location shall be selected within the defined coverage area of the systems. + +### B.1.5 Satellite constellation and assistance data + +#### B.1.5.1 UE supports A-GPS L1 C/A only + +In the case of test cases in clause 5 (UE supports A-GPS L1 C/A only), the GPS satellite constellation shall consist of 24 satellites. Almanac assistance data shall be available for all these 24 satellites. At least 9 of the satellites shall be visible to the UE (that is above 5 degrees elevation with respect to the UE). Other assistance data shall be available for 9 of these visible satellites. In each test, signals are generated for only a sub-set of these satellites for which other assistance data is available. The number of satellites in this sub-set is specified in the test. The satellites in this sub-set shall all be above 15 degrees elevation with respect to the UE. The HDOP for the test shall be calculated using this sub-set of satellites. The selection of satellites for this sub-set shall be selected consistent with achieving the required HDOP for the test. + +#### B.1.5.2 UE supports other A-GNSSs + +In the case of test cases in clause 6 (UE supports other GNSSs), the satellite constellation shall consist of 35 satellites for BDS (5 GEO, 27 MEO, 3 IGSO); 27 satellites for Galileo; 24 satellites for GLONASS; 27 satellites for GPS/Modernized GPS; 3 satellites for QZSS; 2 satellites for SBAS and 7 satellites for NavIC (3GEO, 4 IGSO). Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per BDS, Galileo, GLONASS, GPS/Modernized GPS constellation shall be visible to the UE (that is, above 15 degrees elevation with respect to the UE). At least 1 of the satellites for QZSS shall be within 15 degrees of zenith; at least 1 of the satellites of NavIC shall be visible to the UE above 15 degrees elevation angle over NavIC service area. (Service area as defined in ICD [24]) and at least 1 of the satellites for SBAS shall be visible to the UE. For BDS with reference location in Asia, at least 1 of the visible satellites shall be a GEO (above 15 degrees elevation with respect to the UE). All other satellite specific assistance data shall be available for all visible satellites. In each test, signals are generated for only 6 satellites for single constellation and dual constellation and 7 satellites for triple constellation (or one additional satellite if SBAS is included). The HDOP for the test shall be calculated using these satellites. The simulated satellites for BDS, Galileo, GLONASS GPS/Modernized GPS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test. For BDS with reference location in Asia, 1 of the simulated satellites shall be a GEO. For NavIC with reference location in the NavIC service area as defined in [24], the simulated satellite shall be an IGSO. + +### B.1.6 Atmospheric delays + +Typical Ionospheric and Tropospheric delays shall be simulated, and the corresponding values inserted into the *GNSS-Ionospheric Model IE*. + +### B.1.7 E-UTRA or NR frequency and frequency error + +In all test cases with E-UTRA frequency, the E-UTRA frequency used shall be the mid-range for the E-UTRA In all test cases other than Sensitivity in clause 5.1 with E-UTRA frequency, the E-UTRA frequency used shall be the mid-range for the E-UTRA operating band. The E-UTRA frequency with respect to the GNSS carrier frequency shall be offset by +0.025 PPM. + +In all test cases other than Sensitivity in clause 5.1 with NR, the NR frequency used shall be as specified in TS 38.508-1 [20], clause 4.3.1. The NR frequency with respect to the GNSS carrier frequency shall be offset by + 0.025 PPM. + +For verifying the sensitivity requirements in clause 5.1 with NR single carrier, the sensitivity tests shall be performed at least in each frequency band listed in Table B.1.7-1. The frequency bands listed in Table B.1.7-1 have been identified to be at high risk of generating interference in the GNSS bands due to mechanisms consisting of harmonics, cross band isolation, and receiver harmonic mixing. Other frequency bands may also impact GNSS sensitivity performance and thus be tested. For the frequency bands listed in Table B.1.7-1, the NR frequency and channel configuration shall be selected to ensure second order harmonics and other distortion will fall into the GNSS receiver bands as defined in clause B.1.13.2 for the particular GNSS. If the DUT does not support any of the frequency bands listed in Table B.1.7-1 the sensitivity tests in clause 5.1 can be performed in any frequency band supported by the DUT. + +**Table B.1.7-1: Minimum set of NR operating bands for verifying GNSS sensitivity** + +| | | +|--------------------|-----| +| NR operating bands | n14 | +|--------------------|-----| + +### B.1.8 Information elements + +The information elements that are available to the UE in all the test cases are listed in annex E. + +### B.1.9 GNSS signals + +The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. + +### B.1.10 RESET UE POSITIONING STORED INFORMATION Message + +In order to ensure each Test Instance in each TTFF test is performed under TTFF conditions, a dedicated test message (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 38.509 [9] clause 5.6 shall be used. + +When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' message, with the IE *UE POSITIONING TECHNOLOGY* set to AGNSS it shall: + +- discard any internally stored GNSS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler); +- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition; +- calculate the position or perform GNSS measurements using the 'new' reference time or reference location or other information. + +### B.1.11 GNSS system time offsets + +If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the SS shall be better than 3 ns. + +### B.1.12 Sensors + +The minimum performances shall be met without the use of any data coming from sensors that can aid the positioning. + +### B.1.13 EN-DC band combinations for testing A-GNSS sensitivity + +#### B.1.13.1 EN-DC band combination groups + +For the A-GNSS sensitivity requirements in EN-DC operation mode with uplink assigned to E-UTRA and NR frequency bands, the requirements in clause 6.1 can be verified by one EN-DC band combination in each of the applicable Frequency Group Combination specified in Table B.1.13.1-1. The A-GNSS sensitivity requirements for the remaining applicable EN-DC band combinations in each Frequency Group Combination are considered to have been verified by using the one EN-DC band combination in each Frequency Group Combination. The Frequency Groups are defined in Table B.1.13.1-2. + +The applicable EN-DC band combinations for verifying A-GNSS sensitivity requirements in EN-DC operation mode are specified in clause B.1.13.2. + +**Table B.1.13.1-1: EN-DC band combination groups for verifying A-GNSS sensitivity requirements in EN-DC operation mode** + +| Frequency Group Combination | EN-DC Band Combinations | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Group VHF-VHF | NA | +| Group VHF-LB | NA | +| Group VHF-MLB | NA | +| Group VHF-MB | NA | +| Group VHF-HB | NA | +| Group VHF-UHB1 | NA | +| Group VHF-UHB2 | NA | +| Group LB-VHF | NA | +| Group LB-LB | DC_5A_n12A
DC_5A_n71A
DC_8A_n20A
DC_8A_n28A
DC_12A_n5A
DC_20A_n8A
DC_20A_n28A
DC_28A_n5A
DC_28A_n8A
DC_71A_n5A
DC_20A_n83A | +| Group LB-MLB | DC_20A_n50A
DC_20A_n51A
DC_28A_n51A
DC_28A_n50A | +| Group LB-MB | DC_5A_n2A
DC_5A_n66A
DC_8A_n1A
DC_8A_n3A
DC_8A_n34A
DC_8A_n39A
DC_12A_n2A
DC_12A_n25A
DC_12A_n66A
DC_18A_n3A
DC_20A_n1A
DC_20A_n3A
DC_26A_n25A
DC_28A_n3A
DC_71A_n66A
DC_8A_n80A
DC_20A_n80A | +| Group LB-HB | DC_5A_n7A | + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | DC_5A_n38A
DC_5A_n40A
DC_8A_n40A
DC_8A_n41A
DC_12A_n7A
DC_12A_n38A
DC_12A_n41A
DC_20A_n7A
DC_20A_n38A
DC_20A_n41A
DC_26A_n41A
DC_28A_n7A
DC_28A_n40A
DC_28A_n41A
DC_71A_n38A | +| Group LB-UHB1 | DC_5A_n48A
DC_5A_n78A
DC_8A_n77A
DC_8A_n78A
DC_12A_n78A
DC_18A_n77A
DC_18A_n78A
DC_19A_n77A
DC_19A_n78A
DC_20A_n77A
DC_20A_n78A
DC_26A_n77A
DC_26A_n78A
DC_28A_n77A
DC_28A_n78A
DC_71A_n48A
DC_71A_n78A | +| Group LB-UHB2 | DC_5A_n79A
DC_8A_n79A
DC_18A_n79A
DC_19A_n79A
DC_26A_n79A
DC_28A_n79A | +| Group MLB-VHF | NA | +| Group MLB-LB | DC_11A_n28A | +| Group MLB-MLB | NA | +| Group MLB-MB | DC_11A_n3A | +| Group MLB-HB | NA | +| Group MLB-UHB1 | DC_11A_n77A
DC_11A_n78A
DC_21A_n77A
DC_21A_n78A | +| Group MLB-UHB2 | DC_11A_n79A
DC_21A_n79A | +| Group MB-VHF | NA | +| Group MB-LB | DC_1A_n5A
DC_1A_n8A
DC_1A_n20A
DC_1A_n28A
DC_1A_n71A
DC_2A_n5A
DC_2A_n12A
DC_2A_n71A
DC_3A_n5A
DC_3A_n8A
DC_3A_n20A
DC_3A_n28A
DC_3A_n71A
DC_66A_n5A
DC_66A_n12A
DC_66A_n71A
DC_3A_n82A | +| Group MB-MLB | DC_1A_n50A | + +| | | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | DC_1A_n51A
DC_3A_n50A
DC_3A_n51A | +| Group MB-MB | DC_1A_n3A
DC_2A_n66A
DC_3A_n1A
DC_3A_n34A
DC_66A_n2A
DC_66A_n25A
DC_1A_n80A
DC_2A_n2A2
DC_66A_n66A2
DC_3A_n3A2
DC_3A_n84A | +| Group MB-HB | DC_1A_n7A
DC_1A_n38A
DC_1A_n40A
DC_1A_n41A
DC_2A_n7A
DC_2A_n38A
DC_2A_n41A
DC_3A_n7A
DC_3A_n38A
DC_3A_n40A
DC_3A_n41A
DC_4A_n38A
DC_4A_n41A
DC_25A_n41A
DC_39A_n40A
DC_39A_n41A
DC_66A_n7A
DC_66A_n38A
DC_66A_n41A | +| Group MB-UHB1 | DC_1A_n77A
DC_1A_n78A
DC_2A_n48A
DC_2A_n78A
DC_3A_n77A
DC_3A_n78A
DC_4A_n78A
DC_39A_n78A
DC_66A_n48A
DC_66A_n78A | +| Group MB-UHB2 | DC_1A_n79A
DC_3A_n79A
DC_39A_n79A | +| Group HB-VHF | NA | +| Group HB-LB | DC_7A_n5A
DC_7A_n8A
DC_7A_n20A
DC_7A_n28A
DC_7A_n71A
DC_30A_n5A
DC_41A_n28A | +| Group HB-MLB | DC_7A_n51A | +| Group HB-MB | DC_7A_n1A
DC_7A_n3A
DC_7A_n66A
DC_30A_n2A
DC_30A_n66A
DC_40A_n1A
DC_41A_n3A
DC_7A_n80A
DC_38A_n3A | +| Group HB-HB | DC_7A_n40A
DC_40A_n41A
DC_7A_n7A2
DC_41A_n41A | + +| | | +|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| Group HB-UHB1 A (NOTE 1) :
B (NOTE 2) :
C (NOTE 3) : | DC_40A_n77A
DC 40A_n78A | +| | DC_7A_n78A
DC_38A_n78A
DC 41A_n78A | +| | DC_7A_n77A
DC 41A_n77A | +| Group HB-UHB2 | DC_40A_n79A
DC 41A_n79A | +| Group UHB1-VHF | NA | +| Group UHB1-LB | NA | +| Group UHB1-MLB | NA | +| Group UHB1-MB | NA | +| Group UHB1-HB | NA | +| Group UHB1-UHB1 | NA | +| Group UHB1-UHB2 | NA | +| Group UHB2-VHF | NA | +| Group UHB2-LB | NA | +| Group UHB2-MLB | NA | +| Group UHB2-MB | NA | +| Group UHB2-HB | NA | +| Group UHB2-UHB1 | NA | +| Group UHB2-UHB2 | NA | +| NOTE 1: | This sub-group generates second order intermodulation products. | +| NOTE 2: | This sub-group generates third order intermodulation products. | +| NOTE 3: | This sub-group generates second and third order intermodulation products. | + +Table B.1.13.1-2: Definition of Frequency Groups + +| Frequency Group | Frequency Range (MHz) | +|-----------------|-----------------------| +| VHF | 400.0 – 458.0 | +| LB | 662.0 – 916.0 | +| MLB | 1426.0 – 1518.0 | +| MB | 1626.0 – 2025.0 | +| HB | 2300.0 – 2690.0 | +| UHB1 | 3300.0 – 4201.0 | +| UHB2 | 4400.0 – 5000.0 | + +#### B.1.13.2 Applicable EN-DC band combinations for verifying A-GNSS sensitivity requirements + +The A-GNSS sensitivity requirements in clause 6.1 when in EN-DC operation mode shall be verified for EN-DC band combinations that can generate second or third order intermodulation products falling into the following GNSS receiver bands for the particular GNSS (where supported by the UE): + +- GPS L1 C/A: 1574.3970 – 1576.4430 MHz +- Galileo E1 / GPS L1C: 1573.3740 – 1577.4660 MHz +- GLONASS G1: 1597.5515 – 1605.8860 MHz +- BDS B1I: 1559.0520 – 1563.1440 MHz + +For each frequency group combination in Table B.1.13.2-1 only one EN-DC band combination needs to be tested for the supported GNSS. + +Table B.1.13.2-1: EN-DC band combinations for verifying A-GNSS sensitivity requirements + +| Frequency Group Combination | EN-DC band combinations | | | +|-----------------------------|-------------------------|------------|------------| +| | GPS L1 / Galileo E1 | GLONASS G1 | BDS B1 | +| Group LB-LB | DC_20A_n28A | DC_8A_n28A | DC_5A_n12A | + +| | | | | +|------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| | DC_28A_n5A
DC_20A_n83A | DC_20A_n28A
DC_28A_n8A
DC_20A_n83A | DC_12A_n5A
DC_20A_n28A
DC_28A_n5A
DC_20A_n83A | +| Group LB-MLB | NA | NA | NA | +| Group LB-MB | NA | NA | NA | +| Group LB-HB | DC_5A_n40A
DC_28A_n40A | DC_8A_n41A
DC_28A_n40A | DC_5A_n40A
DC_28A_n40A | +| Group LB-UHB1 | DC_8A_n77A
DC_8A_n78A
DC_20A_n77A
DC_20A_n78A | DC_5A_n78A
DC_8A_n77A
DC_8A_n78A
DC_20A_n77A
DC_20A_n78A
DC_26A_n77A
DC_26A_n78A | DC_8A_n77A
DC_8A_n78A | +| Group LB-UHB2 | NA | NA | NA | +| Group MLB-LB | NA | NA | NA | +| Group MLB-MLB | NA | NA | NA | +| Group MLB-MB | NA | NA | NA | +| Group MLB-HB | NA | NA | NA | +| Group MLB-UHB1 | NA | NA | NA | +| Group MLB-UHB2 | DC_11A_n79A
DC_21A_n79A | DC_11A_n79A
DC_21A_n79A | DC_11A_n79A
DC_21A_n79A | +| Group MB-LB | NA | NA | NA | +| Group MB-MLB | NA | NA | NA | +| Group MB-MB | DC_1A_n3A
DC_2A_n66A
DC_3A_n1A
DC_66A_n2A
DC_66A_n25A
DC_1A_n80A
DC_3A_n84A | DC_1A_n3A
DC_2A_n66A
DC_3A_n1A
DC_66A_n2A
DC_66A_n25A
DC_1A_n80A
DC_3A_n84A | DC_1A_n3A
DC_2A_n66A
DC_3A_n1A
DC_66A_n2A
DC_66A_n25A
DC_1A_n80A
DC_3A_n84A | +| Group MB-HB | DC_1A_n40A | DC_1A_n7A | DC_1A_n7A | +| Group MB-UHB1 | DC_1A_n77A
DC_1A_n78A
DC_2A_n78A
DC_3A_n77A
DC_3A_n78A
DC_4A_n78A
DC_39A_n78A
DC_66A_n78A | DC_1A_n77A
DC_1A_n78A
DC_2A_n78A
DC_3A_n77A
DC_3A_n79A
DC_4A_n78A
DC_39A_n78A
DC_66A_n78A | DC_1A_n77A
DC_1A_n78A
DC_2A_n78A
DC_3A_n77A
DC_3A_n79A
DC_4A_n78A
DC_39A_n78A
DC_66A_n78A | +| Group MB-UHB2 | DC_3A_n79A | NA | DC_3A_n79A | +| Group HB-LB | NA | DC_7A_n8A | NA | +| Group HB-MLB | NA | NA | NA | +| Group HB-MB | DC_40A_n1A | DC_40A_n1A | DC_40A_n1A | +| Group HB-HB | NA | NA | NA | +| Group HB-UHB1 A:
B:
C: | DC_40A_n77A
DC_7A_n78A
DC_38A_n78A
DC_41A_n78A
DC_7A_n77A
DC_41A_n77A | DC_40A_n77A
DC_7A_n78A
DC_38A_n78A
DC_41A_n78A
DC_7A_n77A
DC_41A_n77A | DC_40A_n77A
DC_7A_n78A
DC_38A_n78A
DC_41A_n78A
DC_7A_n77A
DC_41A_n77A | +| Group HB-UHB2 | NA | NA | NA | + +#### B.1.13.3 Test frequencies for EN-DC band combinations + +For verifying the sensitivity requirements in clause 6.1 in EN-DC operation mode, the E-UTRA and NR frequency and channel configuration shall be selected to ensure the intermodulation products fall into the GNSS receiver bands as defined in clause B.1.13.2 for the particular GNSS. + +# Annex C (normative): Propagation conditions + +## C.1 Static propagation conditions + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model. + +## C.2 Multi-path case + +Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GNSS signal are defined in table C.1. + +**Table C.1: Multipath case** + +| Initial relative delay [m] | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean power [dB] | +|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------| +| 0 | $F_d$ | $F_d / N$ | 0 | +| X | $F_d - 0.1$ | $(F_d - 0.1) / N$ | Y | +| NOTE: Discrete Doppler frequency is used for each tap. | | | | + +Where the X and Y depends on the GNSS signal type and is shown in Table C.2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in Table C.3 (where k in Table C.3 is the GLONASS frequency channel number). + +**Table C.2: Parameter values** + +| System | Signals | X [m] | Y [dB] | +|--------------------|---------|-------|--------| +| BDS | B1I | 75 | -4.5 | +| | B1C | 125 | -4.5 | +| | B2a | 15 | -6 | +| | B3I | 15 | -6 | +| Galileo | E1 | 125 | -4.5 | +| | E5a | 15 | -6 | +| | E5b | 15 | -6 | +| GLONASS | G1 | 275 | -12.5 | +| | G2 | 275 | -12.5 | +| GPS/Modernized GPS | L1 C/A | 150 | -6 | +| | L1C | 125 | -4.5 | +| | L2C | 150 | -6 | +| | L5 | 15 | -6 | + +**Table C.3: Ratio between carrier frequency and chip rate** + +| System | Signals | N | +|--------------------|---------|--------------------------| +| BDS | B1I | 763 | +| | B1C | 1540 | +| | B2a | 115 | +| | B3I | 124 | +| Galileo | E1 | 1540 | +| | E5a | 115 | +| | E5b | 118 | +| GLONASS | G1 | $3135.03 + k \cdot 1.10$ | +| | G2 | $2438.36 + k \cdot 0.86$ | +| GPS/Modernized GPS | L1 C/A | 1540 | +| | L1C | 1540 | +| | L2C | 1200 | +| | L5 | 115 | + +The initial carrier phase difference between taps shall be randomly selected between 0 and $2\pi$ . The initial value shall have uniform random distribution. + +# Annex D (normative): Measurement sequence chart + +## D.1 General + +The measurement Sequence Charts that are required in all the test cases, are defined in this clause. + +## D.2 TTFF measurement sequence chart + +The measurement sequence chart for the TTFF test cases, for both UE-assisted and UE-based GNSS, is defined in this clause. + +![Sequence diagram showing the TTFF measurement sequence between a Server (SS) and a User Equipment (UE). The sequence consists of seven steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'LPP Request Capabilities' to UE; (c) UE sends 'LPP Provide Capabilities' to SS; (d) SS sends 'LPP Provide Assistance Data' to UE; (e) SS sends 'LPP Provide Assistance Data' to UE (dashed line); (f) SS sends 'LPP Request Location Information' to UE; (g) UE sends 'LPP Provide Location Information' to SS. A 'Response Time' is indicated between steps (f) and (g).](446100c084b94817a19c319fa776b412_img.jpg) + +``` + +sequenceDiagram + participant SS + participant UE + Note left of SS: (a) + SS->>UE: Reset UE Positioning Stored Information + Note left of SS: (b) + SS->>UE: LPP Request Capabilities + Note left of UE: (c) + UE->>SS: LPP Provide Capabilities + Note left of SS: (d) + SS->>UE: LPP Provide Assistance Data + Note left of SS: (e) + SS-->>UE: LPP Provide Assistance Data + Note left of SS: (f) + SS->>UE: LPP Request Location Information + Note right of UE: Response Time + Note left of UE: (g) + UE->>SS: LPP Provide Location Information + +``` + +Sequence diagram showing the TTFF measurement sequence between a Server (SS) and a User Equipment (UE). The sequence consists of seven steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'LPP Request Capabilities' to UE; (c) UE sends 'LPP Provide Capabilities' to SS; (d) SS sends 'LPP Provide Assistance Data' to UE; (e) SS sends 'LPP Provide Assistance Data' to UE (dashed line); (f) SS sends 'LPP Request Location Information' to UE; (g) UE sends 'LPP Provide Location Information' to SS. A 'Response Time' is indicated between steps (f) and (g). + +- (a) The SS sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to AGNSS. +- (b) The SS sends an LPP message of type REQUEST CAPABILITIES including the *A-GNSS-RequestCapabilities* IE set to TRUE. +- (c) The UE sends an LPP message of type PROVIDE CAPABILITIES including the *A-GNSS-ProvideCapabilities* IE with the *AssistanceDataSupportList* included, indicating the assistance data supported by the UE. +- (d) – (e) The SS provides the assistance data that are supported by the UE and available as defined in Annex E and Table E.1 in one or more LPP messages of type PROVIDE ASSISTANCE DATA. +- (f) The SS sends an LPP message of type REQUEST LOCATION INFORMATION including the information elements defined in Table D.1. +- (g) The UE sends an LPP message of type PROVIDE LOCATION INFORMATION including either the *GNSS-SignalMeasurementInformation* or *GNSS-LocationInformation* IE, dependent on the test case (UE-assisted or UE-based, respectively). + +Steps (a) to (g) are repeated for each test instance. + +**Table D.1: LPP Request Location Information content for TTFF test cases.** + +| Information Element | Value/remark | Comment | +|--------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------| +| RequestLocationInformation | | | +| > commonEsRequestLocationInformation | | | +| >> locationInformationType | 'locationEstimateRequired' or 'locationMeasurementsRequired' | Depending on test case and UE capabilities, i.e., UE-based or UE-assisted | +| >> additionalInformation | 'onlyReturnInformationRequested' | | +| >> qos | | | +| >>> horizontalAccuracy | As defined in Annex B.1.1 | | +| >>> verticalCoordinateRequest | FALSE | | +| >>> responseTime | '20' | 20 seconds | +| > a-gnss-RequestLocationInformation | | | +| >> gnss-PositioningInstructions | | | +| >>> gnssMethods | | | +| >>>> gnss-ids | According to UE capabilities | | +| >>> fineTimeAssistanceMeasReq | FALSE | | +| >>> adrMeasReq | FALSE | | +| >>> multiFreqMeasReq | TRUE or FALSE | Depending on UE capabilities | +| >>> assistanceAvailability | FALSE | | + +## D.3 Moving scenario and periodic update measurement sequence chart + +The measurement sequence chart for the moving scenario and periodic update test case, for both UE-assisted and UE-based GNSS, is defined in this clause. + +![Sequence diagram showing the interaction between SS (Server) and UE (User Equipment) for positioning. The sequence starts with SS sending 'Reset UE Positioning Stored Information' to UE. Then SS sends 'LPP Request Capabilities' to UE. UE responds with 'LPP Provide Capabilities' to SS. SS then sends 'LPP Provide Assistance Data' to UE. This is followed by a dashed line for another 'LPP Provide Assistance Data' message. SS then sends 'LPP Request Location Information' to UE. UE responds with 'LPP Provide Location Information' to SS. This is followed by a vertical ellipsis. Finally, UE sends another 'LPP Provide Location Information' to SS.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant SS + participant UE + Note left of SS: (a) + SS->>UE: Reset UE Positioning Stored Information + Note left of SS: (b) + SS->>UE: LPP Request Capabilities + Note left of UE: (c) + UE-->>SS: LPP Provide Capabilities + Note left of SS: (d) + SS->>UE: LPP Provide Assistance Data + Note left of UE: (e) + UE-->>SS: LPP Provide Assistance Data + Note left of SS: (f) + SS->>UE: LPP Request Location Information + Note left of UE: (g) + UE-->>SS: LPP Provide Location Information + Note left of UE: (h) + UE-->>SS: LPP Provide Location Information + Note left of UE: (i) + UE-->>SS: LPP Provide Location Information + +``` + +Sequence diagram showing the interaction between SS (Server) and UE (User Equipment) for positioning. The sequence starts with SS sending 'Reset UE Positioning Stored Information' to UE. Then SS sends 'LPP Request Capabilities' to UE. UE responds with 'LPP Provide Capabilities' to SS. SS then sends 'LPP Provide Assistance Data' to UE. This is followed by a dashed line for another 'LPP Provide Assistance Data' message. SS then sends 'LPP Request Location Information' to UE. UE responds with 'LPP Provide Location Information' to SS. This is followed by a vertical ellipsis. Finally, UE sends another 'LPP Provide Location Information' to SS. + +- (a) The SS sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to AGNSS. +- (b) The SS sends an LPP message of type REQUEST CAPABILITIES including the *A-GNSS-RequestCapabilities* IE set to TRUE. +- (c) The UE sends an LPP message of type PROVIDE CAPABILITIES including the *A-GNSS-ProvideCapabilities* IE with the *AssistanceDataSupportList* included, indicating the assistance data supported by the UE. +- (d) – (e) The SS provides the assistance data that are supported by the UE and available as defined in Annex E and table E.1 in one or more LPP messages of type PROVIDE ASSISTANCE DATA. +- (f) The SS sends an LPP message of type REQUEST LOCATION INFORMATION including the information elements defined in Table D.2. +- (g) – (i) The UE provides LPP messages of type PROVIDE LOCATION INFORMATION including either the *GNSS-SignalMeasurementInformation* or *GNSS-LocationInformation* IE, dependent on the test case (UE-assisted or UE-based, respectively) until the moving trajectory is completed. + +NOTE: The UE may report error messages at step (g) until it is able to acquire GNSS signals. + +**Table D.2: LPP Request Location Information content for moving scenario and periodic update test case.** + +| Information Element | Value/remark | Comment | +|--------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------| +| RequestLocationInformation | | | +| > commonEsRequestLocationInformation | | | +| >> locationInformationType | 'locationEstimateRequired' or 'locationMeasurementsRequired' | Depending on test case and UE capabilities, i.e., UE-based or UE-assisted | +| >> periodicalReporting | | | +| >>> reportingAmount | 'ra-Infinity' | As defined in Annex B.1.1 | +| >>> reportingInterval | 'ri2' | As defined in Annex B.1.1 | +| >> additionalInformation | 'onlyReturnInformationRequested' | | +| >> qos | | | +| >>> horizontalAccuracy | As defined in Annex B.1.1 | | +| >>> verticalCoordinateRequest | FALSE | | +| > a-gnss-RequestLocationInformation | | | +| >> gnss-PositioningInstructions | | | +| >>> gnssMethods | | | +| >>>> gnss-ids | According to UE capabilities | | +| >>> fineTimeAssistanceMeasReq | FALSE | | +| >>> adrMeasReq | FALSE | | +| >>> multiFreqMeasReq | FALSE | | +| >>> assistanceAvailability | FALSE | | + +# Annex E (normative): Assistance data required for testing + +## E.1 Introduction + +This annex defines the assistance data IEs available at the SS in all test cases. The assistance data shall be given for satellites as defined in B.1.5. + +The information elements are given with reference to TS 36.355 [3], where the details are defined. + +Table E.1 defines the assistance data elements which shall be provided to the UE in the tests (steps (d) and (e) in the message sequence according to annexes D.2 and D.3). The assistance data provided depends on the mode being used in the test case, the assistance data supported by the UE (indicated in step (c) in the message sequence according to annexes D.2 and D.3) and the GNSSs supported by the UE. Assistance data IEs not supported by the UE shall not be sent. Assistance data IEs supported by the UE but not listed in Table E.1 shall not be sent. + +**Table E.1: Assistance data to be provided to the UE** + +| Assistance data IE supported by UE | Mode used in test case | | | +|------------------------------------|------------------------|----------------------------------------------------------|--------------------------------------------------------------| +| | UE-based | UE-assisted, GNSS- AcquisitionAssistance supported by UE | UE-assisted, GNSS- AcquisitionAssistance not supported by UE | +| GNSS-Reference Time | Yes | Yes | Yes | +| GNSS-ReferenceLocation | Yes | No | Yes | +| GNSS-IonosphericModel | Yes | No | No | +| GNSS-TimeModelList | Yes (1) | No | Yes (1) | +| GNSS-NavigationModel | Yes | No | Yes | +| GNSS-AcquisitionAssistance | No | Yes | No | +| GNSS-Almanac | No | No | Yes | +| GNSS-UTC-Model | Yes (3) | Yes (3) | Yes (3) | +| GNSS-AuxiliaryInformation | Yes (2) | Yes (2) | Yes (2) | + +NOTE 1: In case more than a single GNSS is supported by the UE. +NOTE 2: In case the UE supports GLONASS, and/or more than one GPS signal, and/or BDS B1C/B2a. +NOTE 3: In case more than a single GNSS is supported by the UE and the UE supports GLONASS. + +## E.2 GNSS assistance data + +- GNSS-ReferenceTime IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.2: GNSS-ReferenceTime IE** + +| Information Element | All tests except Sensitivity Fine Time Assistance | Sensitivity Fine Time Assistance test | +|----------------------------------------------|---------------------------------------------------|---------------------------------------| +| GNSS-ReferenceTime | | | +| > gnss-SystemTime | | | +| >> gnss-TimeID | Yes | Yes | +| >> gnss-DayNumber | Yes | Yes | +| >> gnss-TimeOfDay | Yes | Yes | +| >> gnss-TimeOfDayFrac-msec | Yes | Yes | +| >> notificationOfLeapSecond | Yes if gnss-TimeID = 'glonass' | Yes if gnss-TimeID = 'glonass' | +| >> gps-TOW-Assist | Yes if gnss-TimeID = 'gps' | Yes if gnss-TimeID = 'gps' | +| > referenceTimeUnc | Yes | No | +| > gnss-ReferenceTimeForOneCell | No | Yes | +| >> networkTime | | Yes | +| >>> secondsFromFrameStructureStart | | Yes | +| >>> fractionalSecondsFromFrameStructureStart | | Yes | +| >>> frameDrift | | Yes | +| >>> cellID | | Yes | +| >>> CHOICE eUTRA | | | +| >>>> physCellId | | Yes | +| >>>> cellGlobalIdEUTRA | | Yes | +| >>>> earfcn/earfcn-v9a0 | | Yes | +| >>> CHOICE nr-r15 | | | +| >>>> nrPhysCellId-r15 | | Yes | +| >>>> nrCellGlobalID-r15 | | Yes | +| >>>> nrARFCN-r15 | | Yes | +| >> referenceTimeUnc | | Yes | + +b) **GNSS-ReferenceLocation IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.3: GNSS-ReferenceLocation IE** + +| Name of the IE | Fields of the IE | +|------------------------|------------------| +| GNSS-ReferenceLocation | threeDlocation | + +c) **GNSS-IonosphericModel IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.4: GNSS-IonosphericModel IE** + +| Name of the IE | Fields of the IE | +|-----------------------|-----------------------------------------| +| GNSS-IonosphericModel | KlobucharModelParameter | +| | NeQuickModelParameter (1) | +| | KlobucharModel2Parameter (2) | + +NOTE 1: Only required if GNSSs supported include Galileo. +NOTE 2: Only required if GNSSs supported include BDS B1C/B2a. + +d) **GNSS-TimeModelList IE.** This information element is only required for multi system tests, and is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.5: GNSS-TimeModelList IE** + +| Name of the IE | Fields of the IE | +|--------------------|-----------------------------------------------------------| +| GNSS-TimeModelList | gnssTOID
For each GNSS included in the list.
deltaT | + +e) **GNSS-NavigationModel IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.6: GNSS-NavigationModel IE** + +| Name of the IE | Fields of the IE | +|----------------------|------------------| +| GNSS-NavigationModel | | + +**Table E.7: GNSS Clock and Orbit Model choices** + +| GNSS | Clock and Orbit Model choice | +|---------------------|------------------------------| +| BDS B1I/B3I | Model-6 | +| BDS B1C/B2a | Model-7 | +| Galileo | Model-1 | +| GLONASS | Model-4 | +| GPS L1 C/A | Model-2 | +| Modernized GPS | Model-3 | +| QZSS QZS-L1 C/A | Model-2 | +| QZSS QZS-L1C/L2C/L5 | Model-3 | +| SBAS | Model-5 | +| NavIC | Model-8 | + +f) **GNSS-AcquisitionAssistance IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.8: GNSS-AcquisitionAssistance IE** + +| Name of the IE | Fields of the IE | +|----------------------------|------------------| +| GNSS-AcquisitionAssistance | | + +g) **GNSS-Almanac IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.9: GNSS-Almanac IE** + +| Name of the IE | Fields of the IE | +|----------------|------------------| +| GNSS-Almanac | | + +**Table E.10: GNSS Almanac choices** + +| GNSS | Almanac Model choice | +|---------------------|-----------------------------| +| BDS B1I/B3I | Model-7 | +| BDS B1C/B2a | Model-3, 4 | +| Galileo | Model-1 | +| GLONASS | Model-5 | +| GPS L1 C/A | Model-2 | +| Modernized GPS | Model-3, 4 | +| QZSS QZS-L1 C/A | Model-2 | +| QZSS QZS-L1C/L2C/L5 | Model-3, 4 | +| SBAS | Model-6 | +| NavIC | Model-8 | + +h) **GNSS-UTC-Model IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.11: GNSS-UTC-Model IE** + +| Name of the IE | Fields of the IE | +|-----------------------|-------------------------| +| GNSS-UTC-Model | | + +**Table E.12: GNSS UTC Model choices** + +| GNSS | UTC Model choice | +|---------------------|-------------------------| +| BDS B1I/B3I | Model-5 | +| BDS B1C/B2a | Model-2 | +| Galileo | Model-1 | +| GLONASS | Model-3 | +| GPS L1 C/A | Model-1 | +| Modernized GPS | Model-2 | +| QZSS QZS-L1 C/A | Model-1 | +| QZSS QZS-L1C/L2C/L5 | Model-2 | +| SBAS | Model-4 | +| NavIC | Model-2 | + +i) **GNSS-AuxiliaryInformation IE.** This information element is defined in clause 6.5.2.2 of TS 36.355 [3]. + +**Table E.13: GNSS-AuxiliaryInformation IE** + +| Name of the IE | Fields of the IE | +|---------------------------|-------------------------| +| GNSS-AuxiliaryInformation | | + +# --- Annex F (normative): Converting UE-assisted measurement reports into position estimates + +## F.1 Introduction + +To convert the UE measurement reports in case of UE-assisted mode of A-GNSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [6-8] and [10-16]. + +## F.2 UE measurement reports + +In case of UE-assisted A-GNSS, the measurement parameters are contained in the LPP *GNSS-SignalMeasurementInformation* IE (clause 6.5.2.6 in TS 36.355 [3]). The measurement parameters required for calculating the UE position are: + +- 1) Reference Time: The UE has two choices for the Reference Time: + - a) "networkTime"; + - b) "gnss-TOD-msec". +- 2) Measurement Parameters for each GNSS and GNSS signal: 1 to 64: + - a) "svID "; + - b) "codePhase"; + - c) "integerCodePhase"; + - d) "codePhaseRMSError". + +Additional information required at the SS: + +- 1) "GNSS-ReferenceLocation" (clause 6.5.2.2 in TS 36.355 [3]): +Used for initial approximate receiver coordinates. +- 2) "GNSS-NavigationModel" (clause 6.5.2.2 in TS 36.355 [3]): +Contains the GNSS ephemeris and clock correction parameters as specified in the relevant ICD of each supported GNSS; used for calculating the satellite positions and clock corrections. +- 3) "GNSS-IonosphericModel" (clause 6.5.2.2 in TS 36.355 [3]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in the relevant ICD of each supported GNSS for computation of the ionospheric delay. + +## F.3 WLS position solution + +The WLS position solution problem is concerned with the task of solving for four unknowns; $x_u, y_u, z_u$ the receiver coordinates in a suitable frame of reference (usually ECEF) and $b_u$ the receiver clock bias. It typically requires the following steps: + +### Step 1: Formation of pseudo-ranges + +The observation of code phase reported by the UE for each satellite $SV_i$ is related to the pseudo-range/ $c$ modulo the "gnss-CodePhaseAmbiguity". For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite $SV_i$ is calculated and the integer number of milli-seconds to be added to the UE code phase measurements is obtained. + +### Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets + +In the case that the UE reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the SS: + +$$\rho_{GNSS_m,i} \equiv \rho_{GNSS_m,i} - c \cdot (t_{GNSS_k} - t_{GNSS_m}),$$ + +where $\rho_{GNSS_m,i}$ is the measured pseudo-range of satellite $i$ of GNSS $_m$ . The system time $t_{GNSS_k}$ of GNSS $_k$ is the reference time frame, and $(t_{GNSS_k} - t_{GNSS_m})$ is the available GNSS-GNSS time offset, and $c$ is the speed of light. + +### Step 3: Formation of weighting matrix + +The UE reported "codePhaseRMSError" values are used to calculate the weighting matrix for the WLS algorithm [7]. According to TS 36.355 [3], the encoding for this field is a 6 bit value that consists of a 3 bit mantissa, $X_i$ and a 3 bit exponent, $Y_i$ for each $SV_i$ : + +$$w_i = RMSError = 0.5 \times \left( 1 + \frac{X_i}{8} \right) \times 2^{Y_i}$$ + +The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "codePhaseRMSError" values: + +$$\mathbf{W} = \text{diag} \left\{ 1/w_{GNSS_1,1}^2, 1/w_{GNSS_1,2}^2, \dots, 1/w_{GNSS_1,n}^2, \dots, 1/w_{GNSS_m,1}^2, 1/w_{GNSS_m,2}^2, \dots, 1/w_{GNSS_m,l}^2 \right\}$$ + +### Step 4: WLS position solution + +The WLS position solution is described in reference [7] and usually requires the following steps: + +- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed. +- 2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS. +- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model in reference [8] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model adapted to the particular GNSS frequency. +- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required: + - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report. + - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in the relevant ICD of the particular GNSS and [7]. + - c) Calculate difference between predicted and measured pseudo-ranges $\Delta \rho$ + +- d) Calculate the "Geometry Matrix" **G** as defined in [7]: + +$$\mathbf{G} \equiv \begin{bmatrix} -\hat{\mathbf{i}}_{GNSS_{l,1}}^T & 1 \\ -\hat{\mathbf{i}}_{GNSS_{l,2}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{GNSS_{l,n}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{GNSS_{m,1}}^T & 1 \\ -\hat{\mathbf{i}}_{GNSS_{m,2}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{GNSS_{m,l}}^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{i}}_{GNSS_{m,i}} \equiv \frac{\mathbf{r}_{s_{GNSS_{m,i}}} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{s_{GNSS_{m,i}}} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{s_{GNSS_{m,i}}} \text{ is the satellite position vector for SV}_i$$ + +of GNSSm (calculated in 1) above), and $\hat{\mathbf{r}}_u$ is the estimate of the user location. + +- e) Calculate the WLS solution according to [7]: + +$$\Delta \hat{\mathbf{x}} = (\mathbf{G}^T \mathbf{W} \mathbf{G})^{-1} \mathbf{G}^T \mathbf{W} \Delta \boldsymbol{\rho}$$ + +- f) Adding the $\Delta \hat{\mathbf{x}}$ to the initial state estimate gives an improved estimate of the state vector: + +$$\hat{\mathbf{x}} \rightarrow \hat{\mathbf{x}} + \Delta \hat{\mathbf{x}}.$$ + +- 5) This new state vector $\hat{\mathbf{x}}$ can be used as new initial estimate and the procedure is repeated until the change in $\hat{\mathbf{x}}$ is sufficiently small. + +### Step 5: Transformation from Cartesian coordinate system to Geodetic coordinate system + +The state vector $\hat{\mathbf{x}}$ calculated in Step 4 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias relative to the selected GNSS system time. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates $x_u, y_u, z_u$ to geodetic latitude $\phi$ , longitude $\lambda$ and altitude $h$ on the WGS-84 reference ellipsoid. + +### Step 6: Calculation of "2-D Position Errors" + +The latitude $\phi$ / longitude $\lambda$ obtained after Step 5 is used to calculate the 2-D position error. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38201/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38201/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..171f8ad16167c0661d30ba22d3434bb16dcce2c8 --- /dev/null +++ b/marked/Rel-18/38_series/38201/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cac85760b5c814c16f952b021d435921cbae0479cbed6d788f85c2202c61611 +size 9735 diff --git a/marked/Rel-18/38_series/38201/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38201/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45849cd98a580a61dde2ec134bd9a40a0a006f60 --- /dev/null +++ b/marked/Rel-18/38_series/38201/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:093d733c4206e32aaffa5dba4a02cf1d3b8139bf48c26a39263ab9cc50925310 +size 5119 diff --git a/marked/Rel-18/38_series/38201/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Rel-18/38_series/38201/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccdd6b85b3d8c781d2c007370def4ecdaa0a7ad0 --- /dev/null +++ b/marked/Rel-18/38_series/38201/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfc13ecb7f042a0cc635c62b3669c5f70e5777e3b8171799c9bad580871a34b3 +size 40428 diff --git a/marked/Rel-18/38_series/38201/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-18/38_series/38201/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c48c278405eb2a03b49f470790933d6138f32e4e --- /dev/null +++ b/marked/Rel-18/38_series/38201/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f9052b982f95417d9f2ed0ec691973cb8fe53d30ee31428ab4d40ae1e2f09a1 +size 47506 diff --git a/marked/Rel-18/38_series/38201/raw.md b/marked/Rel-18/38_series/38201/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6fc188628336150e606568e26a9ead2cc90e0791 --- /dev/null +++ b/marked/Rel-18/38_series/38201/raw.md @@ -0,0 +1,421 @@ + + +# 3GPP TS 38.201 V18.0.0 (2023-09) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer; General description (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in small capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in small capital letters. + +3GPP logo + +## --- **Keywords** + +3GPP, New Radio, Layer 1 + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|----------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions of terms, symbols and abbreviations..... | 5 | +| 3.1 Terms..... | 5 | +| 3.2 Symbols..... | 5 | +| 3.3 Abbreviations ..... | 5 | +| 4 General description of layer 1 ..... | 6 | +| 4.1 Relation to other layers ..... | 6 | +| 4.1.1 General protocol architecture ..... | 6 | +| 4.1.2 Service provided to higher layers ..... | 7 | +| 4.2 General description of layer 1 ..... | 7 | +| 4.2.1 Multiple access ..... | 7 | +| 4.2.2 Physical channels and modulation..... | 7 | +| 4.2.3 Channel coding..... | 8 | +| 4.2.4 Physical layer procedures ..... | 8 | +| 4.2.5 Physical layer measurements..... | 8 | +| 5 Document structure of physical layer specification..... | 8 | +| 5.1 Overview ..... | 8 | +| 5.2 TS 38.201: Physical layer; General description ..... | 9 | +| 5.3 TS 38.202: Physical layer services provided by the physical layer ..... | 9 | +| 5.4 TS 38.211: Physical channels and modulation..... | 9 | +| 5.5 TS 38.212: Multiplexing and channel coding..... | 10 | +| 5.6 TS 38.213: Physical layer procedures for control..... | 10 | +| 5.7 TS 38.214: Physical layer procedures for data..... | 10 | +| 5.8 TS 38.215: Physical layer measurements..... | 10 | +| 5.9 TS 37.213: Physical layer procedures for shared spectrum channel access..... | 10 | +| Annex A (informative): Preferred mathematical notations ..... | 12 | +| Annex B (informative): Change history..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides a general description of the physical layer of NR radio interface. The present document also describes the document structure of the 3GPP physical layer specifications, i.e. TS 38.200 series. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" +- [2] 3GPP TS 38.202: "NR; Services provided by the physical layer" +- [3] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [4] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [5] 3GPP TS 38.213: "NR; Physical layer procedures for control" +- [6] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [7] 3GPP TS 38.215: "NR; Physical layer measurements" + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +### *Definition format* + +****: . + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +### *Symbol format* + +      + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------------|------------------------------------------------------------------------------| +| BPSK | Binary Phase Shift Keying | +| CP | Cyclic Prefix | +| DFT-s-OFDM | Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing | +| DU | Distributed Unit | + +| | | +|--------|--------------------------------------------| +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| FDD | Frequency Division Duplex | +| FEC | Forward Error Correction | +| HARQ | Hybrid Automatic Repeat Request | +| IAB | Integrated Access and Backhaul | +| LDPC | Low Density Parity Check | +| MAC | Medium Access Control | +| MIMO | Multiple Input Multiple Output | +| MT | Mobile Termination | +| NCR | Network-Controlled Repeater | +| OFDM | Orthogonal Frequency Division Multiplexing | +| PBCH | Physical Broadcast Channel | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PRACH | Physical Random Access Channel | +| PSBCH | Physical Sidelink Broadcast Channel | +| PSCCH | Physical Sidelink Control Channel | +| PSFCH | Physical Sidelink Feedback Channel | +| PSSCH | Physical Sidelink Shared Channel | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| QAM | Quadrature Amplitude Modulation | +| QPSK | Quadrature Phase Shift Keying | +| RLC | Radio Link Control | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| SRS | Sounding Reference Signal | +| TDD | Time Division Duplex | +| UE | User Equipment | + +# 4 General description of layer 1 + +## 4.1 Relation to other layers + +### 4.1.1 General protocol architecture + +The radio interface described in this specification covers the interface between the User Equipment (UE) and gNB, between gNBs, between IAB-node DU and IAB-node MT/UE, between gNB and NCR-MT, and between UEs. The radio interface is composed of the Layer 1, 2 and 3. The TS 38.200 series describes the Layer 1 (Physical Layer) specifications. Layers 2 and 3 are described in the 38.300 series. + +![Diagram of radio interface protocol architecture around the physical layer. It shows three layers: Layer 3 (Radio Resource Control (RRC)), Layer 2 (Medium Access Control), and Layer 1 (Physical layer). Layer 3 is connected to Layer 2 via logical channels. Layer 2 is connected to Layer 1 via transport channels. A vertical line on the left labeled 'Control / Measurements' connects Layer 3 and Layer 1.](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg) + +The diagram illustrates the protocol stack for the radio interface. It consists of three layers: + + +- Layer 3:** Radio Resource Control (RRC) +- Layer 2:** Medium Access Control (MAC) +- Layer 1:** Physical layer + + The connections between layers are as follows: + + +- Between Layer 3 and Layer 2: Logical channels (represented by ovals). +- Between Layer 2 and Layer 1: Transport channels (represented by ovals). +- A vertical line on the left, labeled 'Control / Measurements', connects Layer 3 and Layer 1 directly. + +Diagram of radio interface protocol architecture around the physical layer. It shows three layers: Layer 3 (Radio Resource Control (RRC)), Layer 2 (Medium Access Control), and Layer 1 (Physical layer). Layer 3 is connected to Layer 2 via logical channels. Layer 2 is connected to Layer 1 via transport channels. A vertical line on the left labeled 'Control / Measurements' connects Layer 3 and Layer 1. + +Figure 1: Radio interface protocol architecture around the physical layer + +Figure 1 shows the NR radio interface protocol architecture around the physical layer (Layer 1). The physical layer interfaces the Medium Access Control (MAC) sub-layer of Layer 2 and the Radio Resource Control (RRC) Layer of Layer 3. The circles between different layer/sub-layers indicate Service Access Points (SAPs). The physical layer offers a transport channel to MAC. The transport channel is characterized by how the information is transferred over the radio interface. MAC offers different logical channels to the Radio Link Control (RLC) sub-layer of Layer 2. A logical channel is characterized by the type of information transferred. + +### 4.1.2 Service provided to higher layers + +The physical layer offers data transport services to higher layers. The access to these services is through the use of a transport channel via the MAC sub-layer. Details are specified in [2]. + +## 4.2 General description of layer 1 + +### 4.2.1 Multiple access + +The multiple access scheme for the NR physical layer is based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP). For uplink, Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) with a CP is also supported. To support transmission in paired and unpaired spectrum, both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) are enabled. + +The Layer 1 is defined in a bandwidth agnostic way based on resource blocks, allowing the NR Layer 1 to adapt to various spectrum allocations. A resource block spans 12 sub-carriers with a given sub-carrier spacing. + +The radio frame has a duration of 10ms and consists of 10 sub-frames with a sub-frame duration of 1ms. A sub-frame is formed by one or multiple adjacent slots, each having 14 adjacent symbols. Further details on the frame structure are specified in [2]. + +### 4.2.2 Physical channels and modulation + +The physical channels defined in the downlink are: + +- the Physical Downlink Shared Channel (PDSCH), +- the Physical Downlink Control Channel (PDCCH), +- the Physical Broadcast Channel (PBCH), + +The physical channels defined in the uplink are: + +- the Physical Random Access Channel (PRACH), +- the Physical Uplink Shared Channel (PUSCH), +- and the Physical Uplink Control Channel (PUCCH). + +The physical channels defined in the sidelink are: + +- the Physical Sidelink Broadcast Channel (PSBCH), +- the Physical Sidelink Control Channel (PSCCH), +- the Physical Sidelink Feedback Channel (PSFCH), +- and the Physical Sidelink Shared Channel (PSSCH). + +In addition, signals are defined as reference signals, primary and secondary synchronization signals. + +The modulation schemes supported are + +- in the downlink, QPSK, 16QAM, 64QAM, 256QAM, and 1024QAM, + +- in the uplink, QPSK, 16QAM, 64QAM and 256QAM for OFDM with a CP and $\pi/2$ -BPSK, QPSK, 16QAM, 64QAM and 256QAM for DFT-s-OFDM with a CP. + +### 4.2.3 Channel coding + +The channel coding scheme for transport blocks is quasi-cyclic LDPC codes with 2 base graphs and 8 sets of parity check matrices for each base graph, respectively. One base graph is used for code blocks larger than certain sizes or with initial transmission code rate higher than thresholds; otherwise, the other base graph is used. Before the LDPC coding, for large transport blocks, the transport block is segmented into multiple code blocks with equal size. The channel coding scheme for PBCH and control information is Polar coding based on nested sequences. Puncturing, shortening and repetition are used for rate matching. Further details of channel coding schemes are specified in [4]. + +### 4.2.4 Physical layer procedures + +There are several Physical layer procedures involved. Such procedures covered by the physical layer are; + +- Cell search +- Power control +- Uplink synchronisation and Uplink timing control +- Random access related procedures +- HARQ related procedures +- Beam management and CSI related procedures +- Sidelink related procedures +- Channel access procedures + +Through the control of physical layer resources in the frequency domain as well as in the time and power domains, implicit support of interference coordination is provided in NR. + +### 4.2.5 Physical layer measurements + +Radio characteristics are measured by the UE and the network and reported to higher layers. These include, e.g. measurements for intra- and inter-frequency handover, inter RAT handover, timing measurements, and measurements for RRM. + +Measurements for inter-RAT handover are defined in support of handover to E-UTRA. + +# --- 5 Document structure of physical layer specification + +## 5.1 Overview + +The physical layer specification consists of a general document (TS 38.201), and seven documents (TS 38.202, 38.211 through 38.215, and 37.213). The relation between the physical layer specifications in the context of the higher layers is shown in Figure 2. + +![Diagram showing the relation between Physical Layer specifications. At the top, 'To/From Higher Layers' points to a box labeled '38.202 Services provided by the physical layer'. Below this, '38.212 Multiplexing and channel coding' is connected via a double-headed arrow. Below '38.212' is '38.211 Physical Channels and Modulation', also connected via a double-headed arrow. To the right of '38.211' is '38.213, 38.214 Physical layer procedures for data, control', connected by a double-headed arrow. To the right of '38.213, 38.214' is '38.215 Physical layer - Measurements', connected by a double-headed arrow. Dashed lines connect '38.202' to '38.212', '38.212' to '38.213, 38.214', and '38.213, 38.214' to '38.215'.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Diagram showing the relation between Physical Layer specifications. At the top, 'To/From Higher Layers' points to a box labeled '38.202 Services provided by the physical layer'. Below this, '38.212 Multiplexing and channel coding' is connected via a double-headed arrow. Below '38.212' is '38.211 Physical Channels and Modulation', also connected via a double-headed arrow. To the right of '38.211' is '38.213, 38.214 Physical layer procedures for data, control', connected by a double-headed arrow. To the right of '38.213, 38.214' is '38.215 Physical layer - Measurements', connected by a double-headed arrow. Dashed lines connect '38.202' to '38.212', '38.212' to '38.213, 38.214', and '38.213, 38.214' to '38.215'. + +Figure 2: Relation between Physical Layer specifications + +## 5.2 TS 38.201: Physical layer; General description + +The scope is to describe: + +- The contents of the Layer 1 documents (TS 38.200 series); +- Where to find information; + +## 5.3 TS 38.202: Physical layer services provided by the physical layer + +The scope is to describe services provided by the physical layer, and to specify: + +- Services and functions of the physical layer; +- Model of physical layer of the UE; +- Parallel transmission of simultaneous physical channels and SRS; +- Measurements provided by the physical layer. + +## 5.4 TS 38.211: Physical channels and modulation + +The scope is to establish the characteristics of the Layer-1 physical channels, generation of physical layer signals and modulation, and to specify: + +- Definition of the uplink, downlink and sidelink physical channels; +- Frame structure and physical resources; +- Modulation mapping (BPSK, QPSK, etc); +- OFDM signal generation; +- Scrambling, modulation and upconversion; +- Layer mapping and precoding; +- Physical shared channel in uplink, downlink and sidelink; +- Reference signal in uplink, downlink and sidelink; + +- Physical random access channel; +- Primary and secondary synchronization signals. + +## 5.5 TS 38.212: Multiplexing and channel coding + +The scope is to describe the transport channel and control channel data processing, including multiplexing, channel coding and interleaving, and to specify: + +- Channel coding schemes; +- Rate matching; +- Uplink transport channels and control information; +- Downlink transport channels and control information; +- Sidelink transport channels and control information. + +## 5.6 TS 38.213: Physical layer procedures for control + +The scope is to establish the characteristics of the physical layer procedures for control, and to specify: + +- Synchronization procedures; +- Uplink power control; +- Random access procedure; +- UE procedure for reporting control information; +- UE procedure for receiving control information. + +## 5.7 TS 38.214: Physical layer procedures for data + +The scope is to establish the characteristics of the physical layer procedures for data, and to specify: + +- Power control; +- Physical downlink shared channel related procedures; +- Physical uplink shared channel related procedure; +- Physical sidelink shared channel related procedure. + +## 5.8 TS 38.215: Physical layer measurements + +The scope is to establish the characteristics of the physical layer measurements, and to specify: + +- Control of UE/NG-RAN measurements; +- Measurement capabilities for NR. + +## 5.9 TS 37.213: Physical layer procedures for shared spectrum channel access + +The scope is to establish the characteristics of the physical layer procedures for shared spectrum channel, and to specify: + +- Downlink channel access procedures; + +- Uplink channel access procedures; +- Sidelink channel access procedures. + +# Annex A (informative): Preferred mathematical notations + +The following table contains the preferred mathematical notations used in L1 documentation. + +| item | notation | +|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| multiply product | cross sign, e.g. $a \times b$ | +| matrix product | dot sign, e.g. $a \cdot b$ | +| scalar product (product of a matrix by a scalar) | dot sign, scalar should precede matrix e.g. $(1 + j) \cdot \begin{bmatrix} u \\ v \end{bmatrix}$ | +| matrix dimensioning | number of rows $\times$ number of column, e.g.:
$R \times C$ | +| Kronecker product | $a \otimes b$ | +| bracketing of sets (all elements of same type, not ordered elements) | curly brackets $\{ \}$ , e.g.
$\{a_1, a_2, \dots, a_p\}$ , or $\{a_i\}_{i \in \{1, 2, \dots, p\}}$ | +| bracketing of lists (all elements not necessary of same type, ordered elements) | round brackets $( )$ , e.g. $(A, u, x)$ | +| bracketing of sequences (all elements of same type, ordered elements) | angle brackets, e.g. $\langle a_1, a_2, \dots, a_p \rangle$ or $\langle a_i \rangle_{i \in \{1, 2, \dots, p\}}$ | +| bracketing of function argument | round brackets, e.g. $f(x)$ | +| bracketing of array index | square brackets, e.g. $a[x]$ | +| bracketing of matrix or vector | square brackets $[ ]$ , e.g. $\begin{bmatrix} x \\ y \end{bmatrix}$ , $\begin{bmatrix} x & y \end{bmatrix}$ , or $\begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix}$ | +| Separation of indexes | use a comma : e.g. $N_{i,j}$ | +| use of italic for symbols | a symbol should be either in italic or in normal font, but mixing up should be avoided. | +| bracketing of arithmetic expression to force precedence of operations | round brackets : e.g. $(a + b) \times c$ | +| necessity of bracketing arithmetic expressions | When only $+$ and $\times$ bracketing is not necessary. When the mod operator is used explicit bracketing of mod operands and possibly result should be done. | +| number type | in a context of non negative integer numbers, some notes should stress when a number is signed, or possibly fractional. | +| binary xor and and | respectively use $+$ or $\cdot$ . If no "mod 2" is explicitly in the expression some text should stress that the operation is modulo 2. | +| matrix or vector transpose | $v^T$ | +| $1 \times 1$ matrices | implicitly cast to its unique element. | +| vector dot product | $u^T \cdot v$ for column vectors, and $u \cdot v^T$ for line vectors | +| complex conjugate | $v^*$ | +| matrix or vector Hermitian transpose | $v^H$ | +| real part and imaginary part of complex numbers. | $\text{Re}(x)$ and $\text{Im}(x)$ | +| Modulo operation (including negative value)
$r \equiv a \bmod N$ | Let $q$ be the integer quotient of $a$ and $N$ , $Z$ is integer, $r$ is remainder then
$\begin{cases} q \in Z \\ a = N \times q + r, \text{ where } q = \lfloor a/N \rfloor \text{ for all } a \text{ and } N \\ 0 \leq r < N \end{cases}$ (Note that $\lfloor \cdot \rfloor$ is floor operation to round the elements of $\cdot$ to the nearest integers towards minus infinity) | + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-05 | RAN1#89 | R1-1708435 | | | | Draft skeleton | 0.0.0 | +| 2017-07 | AH_1706 | R1-1712012 | | | | Inclusion of agreements up to and including RAN1 NR Ad-Hoc #2 | 0.0.1 | +| 2017-08 | RAN1#90 | R1-1713894 | | | | Updates according to email discussion "[NRHA2-03-201] TS 38.201" | 0.0.2 | +| 2017-08 | RAN1#90 | R1-1715069 | | | | Clean version | 0.1.0 | +| 2017-08 | RAN1#90 | R1-1715319 | | | | Inclusion of agreements up to and including RAN1 #90 | 0.1.1 | +| 2017-09 | RAN #77 | RP-171998 | | | | For information to RAN | 1.0.0 | +| 2017-11 | RAN1#90b | R1-1719242 | | | | Inclusion of agreements up to and including RAN1#90bis | 1.0.1 | +| 2017-11 | RAN1#91 | R1-1721046 | | | | Endorsed version by RAN1#90bis (email thread) | 1.1.0 | +| 2017-12 | RAN1#91 | R1-1721339 | | | | Editorial update - Endorsed version by RAN1#91 (email thread) | 1.2.0 | +| 2017-12 | RAN#78 | RP-172530 | | | | Endorsed version for approval by plenary. | 2.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2019-12 | RAN#86 | RP-192661 | 0001 | - | B | Introduction of V2X, NR-based access to unlicensed spectrum, integrated access backhaul for NR and remote interference management | 16.0.0 | +| 2021-12 | RAN#94-e | RP-212982 | 0002 | - | B | Introduction of DL 1024QAM | 17.0.0 | +| 2023-09 | RAN#101 | RP-232469 | 0003 | - | B | Introduction of sidelink channel access procedures for Rel-18 NR sidelink evolution | 18.0.0 | +| 2023-09 | RAN#101 | RP-232479 | 0004 | - | B | Introduction of Rel-18 network-controlled repeaters | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38304/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38304/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..096f5370c8eb0bacc24694aa6624051f6ad2d947 --- /dev/null +++ b/marked/Rel-18/38_series/38304/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0c0b86b0786319fe370001d7af35d040747340d45987314cfd8cce03f5a5259 +size 8331 diff --git a/marked/Rel-18/38_series/38304/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38304/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6120655fe6b3244c38eb118947fe13dc5a647c3d --- /dev/null +++ b/marked/Rel-18/38_series/38304/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1abb24b29905ae78f7ec1c6a57502de53aa6a4fa74d606c0d786afb147be74ed +size 5274 diff --git a/marked/Rel-18/38_series/38304/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-18/38_series/38304/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27358f107fb1054adba34aee341bb81f34c2c92c --- /dev/null +++ b/marked/Rel-18/38_series/38304/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5286135b404238d7496c6db3f7fbfad5c24a68049c22b04a83a515d062a86b2f +size 160710 diff --git a/marked/Rel-18/38_series/38304/raw.md b/marked/Rel-18/38_series/38304/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ff8a6eeaa502ee89009d5d86c884355b8c2326c5 --- /dev/null +++ b/marked/Rel-18/38_series/38304/raw.md @@ -0,0 +1,2003 @@ + + +# 3GPP TS 38.304 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved, wave-like lines. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a red graphic consisting of three curved, wave-like lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 9 | +| 4 General description of RRC_IDLE state and RRC_INACTIVE state ..... | 10 | +| 4.1 Overview ..... | 10 | +| 4.2 Functional division between AS and NAS in RRC_IDLE state and RRC_INACTIVE state ..... | 12 | +| 4.3 Service types in RRC_IDLE state..... | 15 | +| 4.4 Service types in RRC_INACTIVE state ..... | 15 | +| 4.5 Cell Categories ..... | 15 | +| 5 Process and procedure descriptions ..... | 16 | +| 5.1 PLMN selection and SNPN selection ..... | 16 | +| 5.1.1 Support for PLMN selection ..... | 17 | +| 5.1.1.1 General..... | 17 | +| 5.1.1.2 NR case ..... | 17 | +| 5.1.1.3 E-UTRA case..... | 17 | +| 5.1.2 Support for SNPN selection ..... | 17 | +| 5.1.2.1 General..... | 17 | +| 5.1.2.2 NR case ..... | 17 | +| 5.2 Cell selection and reselection..... | 18 | +| 5.2.1 Introduction ..... | 18 | +| 5.2.2 States and state transitions in RRC_IDLE state and RRC_INACTIVE state ..... | 19 | +| 5.2.3 Cell Selection process..... | 20 | +| 5.2.3.1 Description..... | 20 | +| 5.2.3.2 Cell Selection Criterion ..... | 21 | +| 5.2.3.3 E-UTRAN case in Cell Selection ..... | 22 | +| 5.2.4 Cell Reselection evaluation process ..... | 22 | +| 5.2.4.1 Reselection priorities handling ..... | 22 | +| 5.2.4.2 Measurement rules for cell re-selection..... | 24 | +| 5.2.4.3 Mobility states of a UE ..... | 26 | +| 5.2.4.3.0 Introduction ..... | 26 | +| 5.2.4.3.1 Scaling rules ..... | 27 | +| 5.2.4.4 Cells with cell reservations, access restrictions or unsuitable for normal camping ..... | 27 | +| 5.2.4.5 NR Inter-frequency and inter-RAT Cell Reselection criteria..... | 28 | +| 5.2.4.6 Intra-frequency and equal priority inter-frequency Cell Reselection criteria..... | 28 | +| 5.2.4.7 Cell reselection parameters in system information broadcasts..... | 29 | +| 5.2.4.7.0 General reselection parameters ..... | 29 | +| 5.2.4.7.1 Speed dependent reselection parameters..... | 32 | +| 5.2.4.7.2 Slice-based cell reselection parameters..... | 33 | +| 5.2.4.8 Inter-RAT Cell reselection in RRC_INACTIVE state ..... | 33 | +| 5.2.4.9 Relaxed measurement ..... | 33 | +| 5.2.4.9.0 Relaxed measurement rules..... | 33 | +| 5.2.4.9.1 Relaxed measurement criterion for UE with low mobility ..... | 35 | +| 5.2.4.9.2 Relaxed measurement criterion for UE not at cell edge..... | 35 | +| 5.2.4.9.3 Relaxed measurement criterion for a stationary (e)RedCap UE..... | 35 | +| 5.2.4.9.4 Relaxed measurement criterion for a stationary (e)RedCap UE not at cell edge..... | 35 | +| 5.2.4.10 Cell reselection with CAG cells..... | 36 | +| 5.2.4.11 Reselection priorities for slice-based cell reselection..... | 36 | +| 5.2.5 Camped Normally state ..... | 37 | +| 5.2.6 Selection of cell at transition to RRC_IDLE or RRC_INACTIVE state ..... | 37 | +| 5.2.7 Any Cell Selection state ..... | 37 | +| 5.2.8 Camped on Any Cell state ..... | 38 | + +| | | | +|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|-----------| +| 5.3 | Cell Reservations and Access Restrictions ..... | 38 | +| 5.3.0 | Introduction ..... | 38 | +| 5.3.1 | Cell status and cell reservations ..... | 38 | +| 5.3.2 | Unified access control ..... | 42 | +| 5.4 | Tracking Area registration ..... | 42 | +| 5.5 | RAN Area registration ..... | 42 | +| 6 | Reception of broadcast information..... | 42 | +| 6.1 | Reception of system information ..... | 42 | +| 6.2 | Reception of MBS..... | 43 | +| 7 | Paging..... | 43 | +| 7.1 | Discontinuous Reception for paging..... | 43 | +| 7.2 | Paging Early Indication..... | 46 | +| 7.2.1 | Paging Early Indication reception ..... | 46 | +| 7.3 | Subgrouping ..... | 47 | +| 7.3.0 | General ..... | 47 | +| 7.3.1 | CN assigned subgrouping..... | 47 | +| 7.3.2 | UE_ID based subgrouping ..... | 47 | +| 7.4 | Paging in extended DRX..... | 48 | +| 8 | Sidelink Operation ..... | 49 | +| 8.1 | NR sidelink communication, and V2X sidelink communication, NR sidelink discovery, and ranging/
sidelink positioning ..... | 49 | +| 8.2 | Cell selection and reselection for Sidelink..... | 50 | +| 8.2.1 | Parameters used for cell selection and reselection triggered for sidelink ..... | 51 | +| 9 | Tracking Reference Signal..... | 51 | +| Annex A (informative): Example of Hashed ID Calculation using 32-bit FCS..... | | 52 | +| Annex B (informative): Change history ..... | | 53 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the Access Stratum (AS) part of the UE procedures in RRC\_IDLE state (also called Idle mode) and RRC\_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122 [9]. + +The present document specifies the model for the functional division between the NAS and AS in a UE. + +The present document applies to all UEs that support at least NR Radio Access, including multi-RAT UEs as described in 3GPP specifications, in the following cases: + +- When the UE is camped on a NR cell; +- When the UE is searching for a cell to camp on; + +NOTE: When the UE is camped on or searching for a cell to camp on belonging to other RATs, the UE behaviour is described in the specifications of the other RATs. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.300: "NR Overall Description; Stage 2". +- [3] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) - Protocol Specification". +- [4] 3GPP TS 38.213: "NR; Physical layer procedures for control ". +- [5] Void +- [6] 3GPP TS 36.331: "E-UTRA; Radio Resource Control (RRC) - Protocol Specification". +- [7] 3GPP TS 36.304: "E-UTRA; User Equipment (UE) procedures in RRC\_IDLE state ". +- [8] 3GPP TS 38.133: "NR; Requirements for Support of Radio Resource Management". +- [9] 3GPP TS 23.122: "NAS functions related to Mobile Station (MS) in RRC\_IDLE state". +- [10] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [11] 3GPP TS 38.215: "NR; Physical layer measurements". +- [12] 3GPP TS 22.261: "Service requirements for the 5G system". +- [13] 3GPP TS 24.890: "5G System – Phase 1; CT WG1 Aspects". +- [14] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [15] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". + +- [16] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [17] 3GPP TS 23.285: "Technical Specification Group Services and System Aspects; Architecture enhancements for V2X services". +- [18] 3GPP TS 22.011: "Service accessibility". +- [19] 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification". +- [20] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". +- [21] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [22] 3GPP TS 23.304: "Proximity based Services (ProSe) in 5G Systems (5GS)". +- [23] 3GPP TS 23.003: "Numbering, addressing and identification". +- [24] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities". +- [25] 3GPP TS 23.586: "Technical Specification Group Services and System Aspects; Architectural Enhancements to support Ranging based services and Sidelink Positioning". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Acceptable Cell:** A cell that satisfies certain conditions as specified in 4.5. + +**Allowed CAG list:** A per-PLMN list of CAG Identifiers the UE is allowed to access (see TS 23.501 [10]). + +**Available PLMN(s):** One or more PLMN(s) for which the UE has found at least one cell and read its PLMN identity(ies). + +**Available SNPN(s):** One or more SNPN(s) for which the UE has found at least one cell and read its SNPN identity(ies). + +**Barred Cell:** A cell a UE is not allowed to camp on. + +**CAG cell:** A cell broadcasting at least one Closed Access Group Identifier. + +**Camped on a cell:** UE has completed the cell selection/reselection process and has chosen a cell. The UE monitors system information and (in most cases) paging information. + +**Camped on any cell:** UE is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity. + +**Closed Access Group Identifier:** Identifier of a CAG within a PLMN. + +**Commercial Mobile Alert System:** Public Warning System that delivers *Warning Notifications* provided by *Warning Notification Providers* to CMAS capable UEs. + +**eCall Only Mode:** A UE configuration option that allows the UE to register at 5GC and register in IMS to perform only eCall Over IMS, and a non-emergency IMS call for test and/or terminal reconfiguration services. + +**EHPLMN:** Any of the PLMN entries contained in the Equivalent HPLMN list TS 23.122 [9]. + +**Equivalent PLMN list:** List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, and handover according to the information provided by the NAS. + +**Equivalent SNPN list:** List of SNPNs considered as equivalent by the UE for cell selection, cell reselection, and handover according to the information provided by the NAS. + +**eRedCap UE:** A UE with enhanced reduced capabilities as specified in clause 4.2.22 in TS 38.306 [24]. + +**Home PLMN:** A PLMN where the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI. + +**HSDN cell:** A cell that has higher priority than other cells for cell reselection for HSDN capable UE in a High-mobility state. + +**Mobile-IAB cell:** As defined in TS 38.300 [2]. + +**Network Identifier:** Identifier of an SNPN in combination with a PLMN ID (TS 23.501 [10]). + +**Non-Public Network:** A network deployed for non-public use, as defined in TS 22.261 [12]. + +**Non-terrestrial network:** An NG-RAN consisting of gNBs, which provides non-terrestrial NR access to UEs by means of an NTN payload embarked on an airborne or space-borne NTN vehicle and an NTN Gateway. + +**NR sidelink communication:** AS functionality enabling at least V2X Communication as defined in TS 23.287 [16], and ProSe communication (including ProSe non-Relay, UE-to-Network Relay communication and, UE-to-UE Relay communication including UE-to-UE Relay communication with integrated discovery) as defined in TS 23.304 [22], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay Discovery, ProSe UE-to-Network Relay discovery and ProSe UE-to-UE Relay discovery for Proximity based Services as defined in TS 23.304 [22] between two or more nearby UEs, using NR technology but not traversing any network node. + +**Process:** A local action in the UE invoked by an RRC procedure or an RRC\_IDLE or RRC\_INACTIVE state procedure. + +**Quasi-earth fixed cell:** An NTN cell fixed with respect to a certain geographic area on the earth during a certain time duration. This can be provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., the case of NGSO satellites generating steerable beams). + +**Radio Access Technology:** Type of technology used for radio access, for instance NR or E-UTRA. + +**Ranging/Sidelink Positioning:** AS functionality enabling ranging-based services and sidelink positioning as defined in TS 23.586 [25]. + +**RedCap UE:** A UE with reduced capabilities as specified in clause 4.2.21 in TS 38.306 [24]. + +**Registration Area:** (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure. + +**Registered PLMN:** This is the PLMN on which certain Location Registration outcomes have occurred, as specified in TS 23.122 [9]. + +**Registered SNPN:** This is the SNPN on which certain Location Registration outcomes have occurred, as specified in TS 23.122 [9]. + +**Reserved Cell:** A cell on which camping is not allowed, except for particular UEs, if so indicated in the system information. + +**Selected PLMN:** This is the PLMN that has been selected by the NAS, either manually or automatically. + +**Selected SNPN:** This is the SNPN that has been selected by the NAS, either manually or automatically. + +**Serving cell:** The cell on which the UE is camped. + +**Sidelink:** UE to UE interface for V2X sidelink communication defined in TS 23.287[16]. + +**SNPN Access Mode:** Mode of operation wherein UE only selects SNPNs (as defined in TS 23.501 [10]). + +**SNPN identity:** An identifier of an SNPN comprising of a PLMN ID and an NID combination. + +**Strongest cell:** The cell on a particular frequency that is considered strongest according to the layer 1 cell search procedure (TS 38.213 [4], TS 38.215 [11]). + +**Suitable Cell:** This is a cell on which a UE may camp. For NR cell, the criteria are defined in clause 4.5, for E-UTRA cell in TS 36.304 [7]. + +**U2N Relay UE:** a UE that provides functionality to support connectivity to the network for U2N Remote UE(s). + +**U2N Remote UE:** a UE that communicates with the network via a U2N Relay UE. + +**U2U Relay UE:** a UE that provides functionality to support connectivity for U2U Remote UE(s). + +**U2U Remote UE:** a UE that communicates with other UE(s) via a U2U Relay UE. + +**V2X sidelink communication:** AS functionality enabling V2X Communication as defined in TS 23.285 [17], between nearby UEs, using E-UTRA technology but not traversing any network node. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----------|-----------------------------------------------| +| AS | Access Stratum | +| ATG | Air To Ground | +| CAG | Closed Access Group | +| CAG-ID | Closed Access Group Identifier | +| CMAS | Commercial Mobile Alert System | +| CN | Core Network | +| DCI | Downlink Control Information | +| DRX | Discontinuous Reception | +| DTX | Discontinuous Transmission | +| eDRX | Extended DRX | +| ETWS | Earthquake and Tsunami Warning System | +| E-UTRA | Evolved UMTS Terrestrial Radio Access | +| E-UTRAN | Evolved UMTS Terrestrial Radio Access Network | +| GIN | Group ID for Network selection | +| H-SFN | Hyper System Frame Number | +| HRNN | Human-Readable Network Name | +| HSDN | High Speed Dedicated Network | +| IAB | Integrated Access and Backhaul | +| IMSI | International Mobile Subscriber Identity | +| L2 | Layer-2 | +| MBS | Multicast/Broadcast Services | +| MBS FSAI | MBS Frequency Selection Area Identity | +| MCC | Mobile Country Code | +| MCCH | MBS Control Channel | +| MICO | Mobile Initiated Connection Only | +| MRB | MBS Radio Bearer | +| MTCH | MBS Traffic Channel | +| NAS | Non-Access Stratum | +| NCR | Network-Controlled Repeater | +| NCR-Fwd | NCR Forwarding | +| NCR-MT | NCR Mobile Termination | +| NES | Network Energy Savings | +| NID | Network Identifier | +| NPN | Non-Public Network | +| NR | NR Radio Access | +| NSAG | Network Slice AS Group | +| NTN | Non-Terrestrial Network | +| PEI | Paging Early Indication | +| PEI-O | Paging Early Indication-Occasion | +| PH | Paging Hyperframe | +| PLMN | Public Land Mobile Network | +| PTW | Paging Time Window | + +| | | +|------|--------------------------------------------| +| RAT | Radio Access Technology | +| RNA | RAN-based Notification Area | +| RNAU | RAN-based Notification Area Update | +| RRc | Radio Resource Control | +| SDT | Small Data Transmission | +| SL | Sidelink | +| SNPN | Stand-alone Non-Public Network | +| TN | Terrestrial Network | +| TRS | Tracking Reference Signal | +| U2N | UE-to-Network | +| U2U | UE-to-UE | +| UAC | Unified Access Control | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| V2X | Vehicle to Everything | + +# 4 General description of RRC\_IDLE state and RRC\_INACTIVE state + +## 4.1 Overview + +The RRC\_IDLE state and RRC\_INACTIVE state tasks can be subdivided into three processes: + +- PLMN selection (for UE not operating in SNPN access mode) or SNPN selection (for UE operating in SNPN access mode); +- Cell selection and reselection; +- Location registration and RNA update. + +PLMN selection, SNPN selection, cell reselection procedures, and location registration are common for both RRC\_IDLE state and RRC\_INACTIVE state. RNA update is only applicable for RRC\_INACTIVE state. When UE selects a new PLMN or SNPN, UE transitions from RRC\_INACTIVE to RRC\_IDLE, as specified in TS 24.501 [14]. + +When a UE is switched on, a public land mobile network (PLMN) or a SNPN is selected by NAS. For the selected PLMN/SNPN, associated RAT(s) may be set, as specified in TS 23.122 [9]. The NAS shall provide a list of equivalent PLMNs or a list of equivalent SNPNs, if available, that the AS shall use for cell selection and cell reselection. + +With cell selection, the UE searches for a suitable cell of the selected PLMN or selected SNPN, chooses that cell to provide available services, and monitors its control channel. This procedure is defined as "camping on the cell". + +The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of the chosen cell. As an outcome of a successful Location Registration, the selected PLMN/SNPN then becomes the registered PLMN/SNPN, as specified in TS 23.122 [9]. + +If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRC\_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed. + +If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in TS 23.122 [9] and search for a suitable cell if another PLMN has been selected by NAS. + +For UE not operating in SNPN access mode, search of available CAGs may be triggered by NAS to support manual CAG selection. The AS shall report available CAG-ID(s) together with their HRNN (if broadcast) and PLMN(s) to the NAS. + +NAS may also provide the network slice(s) and Network Slice AS Group (NSAG) information, which contains NSAG(s), their applicable TA(s) if present and their priorities, to be considered by the UE during cell reselection (as specified in TS 23.501 [10], TS 24.501 [14]). + +If the UE loses coverage of the registered PLMN/SNPN, either a new PLMN/SNPN is selected automatically (automatic mode), or an indication of available PLMNs/SNPNs is given to the user so that a manual selection can be performed (manual mode). As part of manual SNPN selection, the AS shall report available SNPN identifiers together with their HRNN (if broadcast) to the NAS. + +Registration is not performed by UEs only capable of services that need no registration. + +The UE may perform NR sidelink communication and/or V2X sidelink communication while in-coverage or out-of-coverage for sidelink, as specified in clause 8. + +The U2N Remote UE, the U2N Relay UE, the U2U Remote UE, or the U2U Relay UE may perform sidelink discovery transmissions while in-coverage for the purpose of sidelink relay operations, as specified in clause 8. In addition, the U2N Remote UE, the U2U Remote UE, or the U2U Relay UE can also perform sidelink discovery transmissions while out-of-coverage for the purpose of sidelink relay operations. + +An L2 U2N Remote UE in RRC\_IDLE or in RRC\_INACTIVE may perform all the relevant procedures (e.g., acquiring system information and paging message) via the L2 U2N Relay UE. An L2 U2N Remote UE may choose not to perform any procedures related to cell selection and reselection. + +The UE may perform NR sidelink discovery transmissions while in-coverage or out-of-coverage for the purpose of sidelink non-relay operations, as specified in clause 8. + +The UE may perform ranging/sidelink positioning while in-coverage or out-of-coverage, as specified in clause 8. + +The purpose of camping on a cell in RRC\_IDLE state and RRC\_INACTIVE state is as follows: + +- a) It enables the UE to receive system information from the PLMN or the SNPN. +- b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped. +- c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of tracking areas (in RRC\_IDLE state) or RNA (in RRC\_INACTIVE state) in which the UE is camped. It can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The UE will then receive the paging message and can respond. +- d) It enables the UE to receive ETWS and CMAS notifications. +- e) It enables the UE to receive MBS broadcast services. +- f) It enables the UE to receive MBS multicast services in RRC\_INACTIVE state. + +When the UE is in RRC\_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all idle mode tasks. + +## 4.2 Functional division between AS and NAS in RRC\_IDLE state and RRC\_INACTIVE state + +Table 4.2-1 presents the functional division between UE non-access stratum (NAS) and UE access stratum (AS) in RRC\_IDLE state and RRC\_INACTIVE states. The NAS part is specified in TS 23.122 [9] and the AS part in the present document. + +**Table 4.2-1: Functional division between AS and NAS in RRC\_IDLE state and RRC\_INACTIVE state** + +| RRC_IDLE and
RRC_INACTIVE
state Process | UE Non-Access Stratum | UE Access Stratum | +|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Selection
and SNPN
Selection |

For a UE not operating in SNPN access mode, perform the following:

  • Maintain a list of PLMNs in priority order according to TS 23.122 [9]. Select a PLMN using automatic or manual mode as specified in TS 23.122 [9] and request AS to select a cell belonging to this PLMN. For each PLMN, associated RAT(s) may be set.
  • Evaluate reports of available PLMNs and any associated CAG-IDs from AS for PLMN selection.
  • Maintain a list of equivalent PLMN identities.
  • Maintain a list of "PLMNs not allowed to operate at the present UE location".
  • Maintain applicable disaster roaming information for available PLMNs including potential disaster PLMNs for available PLMNs.
  • To support manual CAG selection, provide request to search for available CAGs and evaluate reports of available CAGs from AS for CAG selection.

For a UE operating in SNPN access mode, perform the following:

  • Maintain a list of SNPNs according to TS 23.122 [9]. Select a SNPN using automatic or manual mode as specified in TS 23.122 [9] and request AS to select a cell belonging to this SNPN.
  • Evaluate reports of available SNPNs from AS for SNPN selection.
  • Maintain a list of equivalent SNPN identities.
|

For a UE not operating in SNPN access mode, search for available PLMNs.

If associated RAT(s) is (are) set for the PLMN, search in this (these) RAT(s) and other RAT(s) for that PLMN as specified in TS 23.122 [9].

For a UE operating in SNPN access mode, search for available SNPNs only consider NR cells.

Perform measurements to support PLMN/SNPN selection.

Synchronise to a broadcast channel to identify found PLMNs/SNPNs.

Report available PLMNs and any associated CAG-IDs with associated RAT(s) to NAS on request from NAS or autonomously.

Report applicable disaster roaming information for available PLMNs autonomously including potential disaster PLMNs.

For a UE operating in SNPN access mode, report available SNPNs to NAS autonomously; report information related to SNPN access with subscription of a different Credentials Holder, indicator whether onboarding is enabled, and the list of supported GINs to NAS autonomously, as specified in TS 38.331 [3].

To support manual CAG selection, perform the following:

  • Search for cells broadcasting a CAG-ID.
  • Read the HRNN (if broadcast) for each CAG-ID if a cell broadcasting a CAG-ID is found.
  • Report CAG-ID(s) of found cell(s) broadcasting a CAG-ID together with the associated manual CAG selection allowed indicator, HRNN and PLMNT to NAS.
  • On selection of a CAG by NAS, select any acceptable or suitable cell belonging to the selected CAG and give an indication to NAS that access is possible (for the registration procedure)

To support manual SNPN selection, report available SNPNs together with associated HRNNs (if available) to NAS on request from NAS.

| + +| RRC_IDLE and
RRC_INACTIVE
state Process | UE Non-Access Stratum | UE Access Stratum | +|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell Selection |

Control cell selection for example by indicating RAT(s) associated with the selected PLMN to be used initially in the search of a cell in the cell selection.

Maintain a list of "Forbidden Tracking Areas" and provide the list to AS.

Maintain a list of "PLMNs not allowed to operate at the present UE location" and provide the list to AS.

For a UE not operating in SNPN access mode: Maintain Allowed CAG list and optional CAG-only indication along with associated PLMN ID(s) on which the UE is allowed access and provide these lists to AS. To support manual CAG selection, select a CAG and request AS to select a cell belonging to this CAG.

|

Perform measurements needed to support cell selection.

Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS.

Search for a suitable cell. The cells broadcast one or more 'PLMN identity' or 'SNPN identity' (for a UE operating in SNPN access mode) in the system information. Respond to NAS whether such cell is found or not.

If associated RATs is (are) set for the PLMN, perform the search in this (these) RAT(s) and other RATs for that PLMN as specified in TS 23.122 [9].

If a cell is found which satisfies cell selection criteria, camp on that cell.

| +| Cell Reselection |

For a UE not operating in SNPN access mode, maintain a list of equivalent PLMN identities and provide the list to AS.

For a UE operating in SNPN access mode, maintain a list of equivalent SNPN identities and provide the list to AS.

Maintain a list of "Forbidden Tracking Areas" and provide the list to AS.

Maintain a list of "PLMNs not allowed to operate at the present UE location" and provide the list to AS.

For a UE not operating in SNPN access mode, maintain Allowed CAG list and optional CAG-only indication along with associated PLMN ID(s) on which the UE is allowed access and provide these lists to AS.

Maintain the network slice(s) and NSAG information and provide network slice(s) and NSAG information to AS.

|

Perform measurements needed to support cell reselection.

Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS.

Change cell if a more suitable cell is found.

Derive cell reselection priorities for slice-based cell reselection.

| +| Location registration |

Register the UE as active after power on.

Register the UE's presence in a registration area, for instance regularly or when entering a new tracking area.

Deregister UE when shutting down.

Maintain a list of "Forbidden Tracking Areas".

Maintain a list of "PLMNs not allowed to operate at the present UE location".

Control and restrict location registration for a UE in eCall Only Mode.

|

Report registration area information to NAS.

| + +| RRC_IDLE and
RRC_INACTIVE
state Process | UE Non-Access Stratum | UE Access Stratum | +|-----------------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------| +| RAN Notification
Area Update | Not applicable. | Register the UE's presence in a RAN-based notification area (RNA), periodically or when entering a new RNA. | + +## 4.3 Service types in RRC\_IDLE state + +This clause defines the level of service that may be provided by the network to a UE in RRC\_IDLE state. The following three levels of services are provided while a UE is in RRC\_IDLE state: + +- Limited service (emergency calls, ETWS and CMAS on an acceptable cell); +- Normal service (for public use or non-public use on a suitable cell); +- Operator service (for operators only on a reserved cell). + +## 4.4 Service types in RRC\_INACTIVE state + +This clause defines the level of service that may be provided by the network to a UE in RRC\_INACTIVE state. The following two levels of services are provided while a UE is in RRC\_INACTIVE state: + +- Normal service (for public use or non-public use on a suitable cell); +- Operator service (for operators only on a reserved cell). + +## 4.5 Cell Categories + +The cells are categorised according to which services they offer: + +### acceptable cell: + +An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and receive ETWS and CMAS notifications). Such a cell shall fulfil the following requirements, which is the minimum set of requirements to initiate an emergency call and to receive ETWS and CMAS notification in an NR network: + +- The cell is not barred, see clause 5.3.1; +- The cell selection criteria are fulfilled, see clause 5.2.3.2. + +### suitable cell: + +For UE not operating in SNPN Access Mode, a cell is considered as suitable if the following conditions are fulfilled: + +- The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list, and for that PLMN either: + - The PLMN-ID of that PLMN is broadcast by the cell with no associated CAG-IDs and CAG-only indication in the UE for that PLMN (TS 23.501 [10]) is absent or false; + - Allowed CAG list in the UE for that PLMN (TS 23.501 [10]) includes a CAG-ID broadcast by the cell for that PLMN; +- The cell selection criteria are fulfilled, see clause 5.2.3.2. + +According to the latest information provided by NAS: + +- The cell is not barred, see clause 5.3.1; +- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas for Roaming" (TS 22.011 [18]), which belongs to a PLMN that fulfils the first bullet above. + +For UE operating in SNPN Access Mode, a cell is considered as suitable if the following conditions are fulfilled: + +- The cell is part of the selected SNPN or the registered SNPN or SNPN of the Equivalent SNPN list of the UE; +- The cell selection criteria are fulfilled, see clause 5.2.3.2; + +According to the latest information provided by NAS: + +- The cell is not barred, see clause 5.3.1; +- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas for Roaming" which belongs to the selected SNPN or the registered SNPN or SNPN of the Equivalent SNPN list of the UE. + +### **barred cell:** + +A cell is barred if it is so indicated in the system information, as specified in TS 38.331 [3]. + +### **reserved cell:** + +A cell is reserved if it is so indicated in system information, as specified in TS 38.331 [3]. + +Following exception to these definitions are applicable for UEs: + +- if a UE has an ongoing emergency call, all acceptable cells of that PLMN/SNPN are treated as suitable for the duration of the emergency call. +- camped on a cell that belongs to a tracking area that is forbidden for regional provision of service; a cell that belongs to a tracking area that is forbidden for regional provision service (TS 23.122 [9], TS 24.501 [14]) is suitable but provides only limited service. +- if the UE in RRC\_IDLE fulfils the conditions to support NR sidelink communication/discovery or V2X sidelink communication in limited service state as specified in TS23.287 [16] clause 5.7, the UE may perform NR sidelink communication/discovery or V2X sidelink communication. + +NOTE: UE is not required to support manual search and selection of PLMN or CAG or SNPN while in RRC\_CONNECTED state. The UE may use local release of RRC connection to perform manual search if it is not possible to perform the search while RRC connected. + +# --- **5 Process and procedure descriptions** + +## **5.1 PLMN selection and SNPN selection** + +In the UE not operating in SNPN access mode, the AS shall report available PLMNs and any associated CAG-IDs to the NAS on request from the NAS or autonomously. In the UE operating in SNPN access mode, the AS shall report available SNPNs to the NAS on request from the NAS or autonomously. + +During PLMN selection, based on the list of PLMN identities in priority order, the particular PLMN may be selected either automatically or manually. Each PLMN in the list of PLMN identities is identified by a 'PLMN identity'. In the system information on the broadcast channel, the UE can receive one or multiple 'PLMN identity' in a given cell. The result of the PLMN selection performed by NAS (see TS 23.122 [9]) is an identifier of the selected PLMN. + +During SNPN selection, based on the list of SNPN identities, the particular SNPN may be selected either automatically or manually. Each SNPN in the list of SNPN identities is identified by a 'SNPN identity'. In the system information on the broadcast channel, the UE can receive one or multiple 'SNPN identity' in a given cell and optionally may receive associated HRNNs; the UE may also optionally receive indicators for whether an SNPN allows access using credentials from a Credentials Holder, whether an SNPN allows registration attempts from UEs that are not explicitly configured to select this SNPN, and whether an SNPN allows onboarding; the UE may also optionally receive a list of supported + +Group IDs for Network selection (see TS 38.331 [3]). The result of the SNPN selection performed by NAS (see TS 23.122 [9]) is an identifier of the selected SNPN. + +### 5.1.1 Support for PLMN selection + +#### 5.1.1.1 General + +On request of the NAS, the AS shall perform a search for available PLMNs and report them to NAS. + +#### 5.1.1.2 NR case + +The UE shall scan all RF channels in the NR bands according to its capabilities to find available PLMNs and available CAGs. On each carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN(s) the cell belongs to and any associated CAG(s). For operation with shared spectrum channel access, the UE may also read the system information of multiple strongest cell(s). If the UE can read one or several PLMN identities in the strongest cell or the multiple strongest cell(s) in case of operation with shared spectrum channel access, each found PLMN (see the PLMN reading in TS 38.331 [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value) and any associated CAG-ID, provided that the following high-quality criterion is fulfilled: + +1. For an NR cell, the measured RSRP value shall be greater than or equal to -110 dBm. + +Found PLMNs that do not satisfy the high-quality criterion but for which the UE has been able to read the PLMN identities are reported to the NAS together with their corresponding RSRP values and any associated CAG-ID. The quality measure reported by the UE to NAS shall be the same for each PLMN found in one cell. + +The search for PLMNs may be stopped on request from the NAS. The UE may optimise PLMN search by using stored information e.g. frequencies and optionally also information on cell parameters from previously received measurement control information elements. + +Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of that PLMN to camp on. + +To support manual CAG selection, the UE shall upon request by NAS report available CAG-ID(s) together with their manual CAG selection allowed indicator (if broadcast), HRNN (if broadcast) and PLMN(s) to the NAS. If NAS has selected a CAG and provided this selection to AS, the UE shall search for an acceptable or suitable cell belonging to the selected CAG to camp on. + +#### 5.1.1.3 E-UTRA case + +Support for PLMN selection in E-UTRA is described in TS 36.304 [7]. + +### 5.1.2 Support for SNPN selection + +#### 5.1.2.1 General + +On request of the NAS, the AS shall perform a search for available SNPNs on only NR cells and report them to NAS. + +#### 5.1.2.2 NR case + +The UE shall scan all RF channels in the NR bands according to its capabilities to find available SNPNs. On each carrier, the UE shall search for the strongest cell and read its system information, in order to find out which SNPN(s) the cell belongs to. For operation with shared spectrum channel access, the UE may also read the system information of multiple strongest cell(s). If the UE can read one or several SNPN identities in the strongest cell, each found SNPN (see the SNPN reading in TS 38.331 [3]) shall be reported to the NAS. For manual selection, UE shall upon request by NAS report available SNPN identifiers together with their HRNN (if broadcast) to the NAS and the search for available SNPNs may be stopped on request of the NAS. + +The search for SNPNs may be stopped on request from the NAS. The UE may optimise SNPN search by using stored information e.g. frequencies and optionally also information on cell parameters from previously received measurement control information elements. + +Once the UE has selected a SNPN, the cell selection procedure shall be performed in order to select a suitable cell of that SNPN to camp on. + +## 5.2 Cell selection and reselection + +### 5.2.1 Introduction + +UE shall perform measurements for cell selection and reselection purposes as specified in TS 38.133 [8]. + +When evaluating Srxlev and Squal of non-serving cells for reselection evaluation purposes, the UE shall use parameters provided by the serving cell and for the final check on cell selection criterion, the UE shall use parameters provided by the target cell for cell reselection. + +The NAS can control the RAT(s) in which the cell selection should be performed, for instance by indicating RAT(s) associated with the selected PLMN, and by maintaining a list of forbidden registration area(s) and a list of equivalent PLMNs. The UE shall select a suitable cell based on RRC\_IDLE or RRC\_INACTIVE state measurements and cell selection criteria. + +In order to expedite the cell selection process, stored information for several RATs, if available, may be used by the UE. + +When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If a better cell is found, that cell is selected. The change of cell may imply a change of RAT. Details on performance requirements for cell reselection can be found in TS 38.133 [8]. + +For NCRs, if the NCR-MT in RRC\_INACTIVE (re)selects a cell other than the last serving cell on which side control configuration was received, then the NCR-MT shall indicate to NCR-Fwd to cease forwarding. If the NCR-MT in RRC\_INACTIVE detects no suitable cell, then the NCR-MT shall indicate to NCR-Fwd to cease forwarding. + +The NAS is informed if the cell selection and reselection result in changes in the received system information relevant for NAS. + +For normal service, the UE shall camp on a suitable cell, monitor control channel(s) of that cell so that the UE can: + +- receive system information from the PLMN or SNPN; and + - receive registration area information from the PLMN or SNPN, e.g., tracking area information; and + - receive other AS and NAS Information; and +- if registered: + - receive paging and notification messages from the PLMN or SNPN; and + - initiate transfer to Connected mode. + +For cell selection in multi-beam operations, measurement quantity of a cell is up to UE implementation. + +For cell reselection in multi-beam operations, including inter-RAT reselection from E-UTRA to NR, the measurement quantity of this cell is derived amongst the beams corresponding to the same cell based on SS/PBCH block as follows: + +- if *nrofSS-BlocksToAverage* (*maxRS-IndexCellQual* in E-UTRA) is not configured in *SIB2/SIB4* (*SIB24* in E-UTRA); or +- if *absThreshSS-BlocksConsolidation* (*threshRS-Index* in E-UTRA) is not configured in *SIB2/SIB4* (*SIB24* in E-UTRA); or +- if the highest beam measurement quantity value is below or equal to *absThreshSS-BlocksConsolidation* (*threshRS-Index* in E-UTRA): + - derive a cell measurement quantity as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [11]. +- else: + +- derive a cell measurement quantity as the linear average of the power values of up to *nrofSS-BlocksToAverage* (*maxRS-IndexCellQual* in E-UTRA) of highest beam measurement quantity values above *absThreshSS-BlocksConsolidation* (*threshRS-Index* in E-UTRA). + +NOTE: If both suitable cell(s) and suitable L2 U2N Relay UE(s) (as specified in TS 38.331 [3]) are available, it is up to L2 U2N Remote UE's implementation to select either a suitable cell or a suitable L2 U2N Relay UE. + +### 5.2.2 States and state transitions in RRC\_IDLE state and RRC\_INACTIVE state + +Figure 5.2.2-1 shows the states and state transitions and procedures in RRC\_IDLE and RRC\_INACTIVE. Whenever a new PLMN selection or new SNPN selection is performed, it causes an exit to number 1. + +![Flowchart of RRC_IDLE and RRC_INACTIVE Cell Selection and Reselection process. The process starts at point '1' (go here whenever a new PLMN or new SNPN is selected). It branches into 'Stored information Cell Selection' (if cell information is stored) and 'Initial Cell Selection' (if no cell information is stored). Both lead to 'Camped normally' if a suitable cell is found. If not, 'Initial Cell Selection' leads to 'Any Cell Selection'. 'Camped normally' can lead to 'Connected mode' (if NAS registration is rejected) or 'Cell Reselection Evaluation Process'. 'Cell Reselection Evaluation Process' leads to 'Camped on any cell' if no suitable cell is found, or back to 'Camped normally' if a suitable cell is found. 'Camped on any cell' can lead to 'Connected mode (Emergency calls only)' or 'Cell Reselection Evaluation Process'. 'Cell Reselection Evaluation Process' from 'Camped on any cell' leads to 'Any Cell Selection' if no acceptable cell is found, or back to 'Camped on any cell' if an acceptable cell is found. 'Any Cell Selection' leads to 'Camped on any cell' if an acceptable cell is found, or back to 'Camped normally' if a suitable cell is found. 'Any Cell Selection' also leads to 'Cell Selection when leaving connected mode' if no acceptable cell is found. 'Cell Selection when leaving connected mode' leads to 'Camped on any cell' if an acceptable cell is found, or back to 'Connected mode' if no suitable cell is found. 'Cell Selection when leaving connected mode' also leads to 'Camped normally' if a suitable cell is found. 'Any Cell Selection' also has an entry point for 'USIM inserted or SNPN subscription added' leading to point '1'. A note indicates to go to 'Any Cell Selection' if no USIM is in the UE and no subscription for an SNPN.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +graph TD + Start(( )) -- "go here whenever a new PLMN or new SNPN is selected" --> Point1_1((1)) + Point1_1 -- "cell information stored for the PLMN or the SNPN" --> SICS[Stored information Cell Selection] + Point1_1 -- "no cell information stored for the PLMN or the SNPN" --> ICS[Initial Cell Selection] + SICS -- "no suitable cell found" --> ICS + SICS -- "suitable cell found" --> Point2_1((2)) + ICS -- "no suitable cell found" --> ACS[Any Cell Selection] + ICS -- "suitable cell found" --> Point2_1 + Point2_1 --> CN((Camped normally)) + CN -- "NAS indicates that registration on selected PLMN or selected SNPN is rejected (except with cause #12, #14, #15 or #25 [9][14])" --> CM[Connected mode] + CN -- "trigger" --> CEP1[Cell Reselection Evaluation Process] + CEP1 -- "no suitable cell found" --> COAC((Camped on any cell)) + CEP1 -- "suitable cell found" --> CN + COAC -- "trigger" --> CEP2[Cell Reselection Evaluation Process] + CEP2 -- "no acceptable cell found" --> ACS + CEP2 -- "acceptable cell found" --> COAC + COAC -- "suitable cell found" --> Point2_2((2)) + COAC -- "acceptable cell found; move to idle mode" --> Point1_2((1)) + COAC -- "leave idle mode" --> CM2[Connected mode (Emergency calls only)] + COAC -- "return to idle mode" --> SCM[Cell Selection when leaving connected mode] + CM2 -- "leave idle/inactive mode" --> CN + CM2 -- "return to idle/inactive mode" --> SCM + SCM -- "no suitable cell found" --> CM + SCM -- "suitable cell found" --> CN + SCM -- "acceptable cell found" --> COAC + ACS -- "no acceptable cell found" --> SCM + ACS -- "suitable cell found" --> CN + ACS -- "acceptable cell found" --> COAC + USIM[USIM inserted or SNPN subscription added] --> Point1_2 + NoUSIM[go here when no USIM in the UE and no subscription for an SNPN] --> ACS + +``` + +Flowchart of RRC\_IDLE and RRC\_INACTIVE Cell Selection and Reselection process. The process starts at point '1' (go here whenever a new PLMN or new SNPN is selected). It branches into 'Stored information Cell Selection' (if cell information is stored) and 'Initial Cell Selection' (if no cell information is stored). Both lead to 'Camped normally' if a suitable cell is found. If not, 'Initial Cell Selection' leads to 'Any Cell Selection'. 'Camped normally' can lead to 'Connected mode' (if NAS registration is rejected) or 'Cell Reselection Evaluation Process'. 'Cell Reselection Evaluation Process' leads to 'Camped on any cell' if no suitable cell is found, or back to 'Camped normally' if a suitable cell is found. 'Camped on any cell' can lead to 'Connected mode (Emergency calls only)' or 'Cell Reselection Evaluation Process'. 'Cell Reselection Evaluation Process' from 'Camped on any cell' leads to 'Any Cell Selection' if no acceptable cell is found, or back to 'Camped on any cell' if an acceptable cell is found. 'Any Cell Selection' leads to 'Camped on any cell' if an acceptable cell is found, or back to 'Camped normally' if a suitable cell is found. 'Any Cell Selection' also leads to 'Cell Selection when leaving connected mode' if no acceptable cell is found. 'Cell Selection when leaving connected mode' leads to 'Camped on any cell' if an acceptable cell is found, or back to 'Connected mode' if no suitable cell is found. 'Cell Selection when leaving connected mode' also leads to 'Camped normally' if a suitable cell is found. 'Any Cell Selection' also has an entry point for 'USIM inserted or SNPN subscription added' leading to point '1'. A note indicates to go to 'Any Cell Selection' if no USIM is in the UE and no subscription for an SNPN. + +Figure 5.2.2-1: RRC\_IDLE and RRC\_INACTIVE Cell Selection and Reselection + +### 5.2.3 Cell Selection process + +#### 5.2.3.1 Description + +Cell selection is performed by one of the following two procedures: + +- Initial cell selection (no prior knowledge of which RF channels are NR frequencies): + +1. The UE shall scan all RF channels in the NR bands according to its capabilities to find a suitable cell. + 2. On each frequency, the UE need only search for the strongest cell, except for operation with shared spectrum channel access where the UE may search for the next strongest cell(s). + 3. Once a suitable cell is found, this cell shall be selected. +- b) Cell selection by leveraging stored information: +1. This procedure requires stored information of frequencies and optionally also information on cell parameters from previously received measurement control information elements or from previously detected cells. + 2. Once the UE has found a suitable cell, the UE shall select it. + 3. If no suitable cell is found, the initial cell selection procedure in a) shall be started. + +NOTE: Priorities between different frequencies or RATs provided to the UE by system information or dedicated signalling are not used in the cell selection process. + +#### 5.2.3.2 Cell Selection Criterion + +The cell selection criterion S is fulfilled when: + +$$S_{rxlev} > 0 \text{ AND } S_{qual} > 0$$ + +where: + +$$S_{rxlev} = Q_{rxlevmeas} - (Q_{rxlevmin} + Q_{rxlevminoffset}) - P_{compensation} - Q_{offsettemp}$$ + +$$S_{qual} = Q_{qualmeas} - (Q_{qualmin} + Q_{qualminoffset}) - Q_{offsettemp}$$ + +where: + +| | | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Srxlev | Cell selection RX level value (dB) | +| Squal | Cell selection quality value (dB) | +| Qoffsettemp | Offset temporarily applied to a cell as specified in TS 38.331 [3] (dB) | +| Qrxlevmeas | Measured cell RX level value (RSRP) | +| Qqualmeas | Measured cell quality value (RSRQ) | +| Qrxlevmin | Minimum required RX level in the cell (dBm). If the UE supports SUL frequency for this cell, Qrxlevmin is obtained from q-RxLevMinSUL , if present, in SIB1 , SIB2 and SIB4 , additionally, if Qrxlevminoffsetcell is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell; else Qrxlevmin is obtained from q-RxLevMin in SIB1 , SIB2 and SIB4 , additionally, if Qrxlevminoffsetcell is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell. | +| Qqualmin | Minimum required quality level in the cell (dB). Additionally, if Qqualminoffsetcell is signalled for the concerned cell, this cell specific offset is added to achieve the required minimum quality level in the concerned cell. | +| Qrxlevminoffset | Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN, as specified in TS 23.122 [9]. | +| Qqualminoffset | Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN, as specified in TS 23.122 [9]. | +| Pcompensation | For FR1, if the UE supports the additionalPmax in the NR-NS-PmaxList , if present, in SIB1 , SIB2 and SIB4 :
$\max(P_{EMAX1} - P_{PowerClass}, 0) - (\min(P_{EMAX2}, P_{PowerClass}) - \min(P_{EMAX1}, P_{PowerClass})) \text{ (dB)}$ else:
$\max(P_{EMAX1} - P_{PowerClass}, 0) \text{ (dB)}$ For FR2, Pcompensation is set to 0.
For IAB-MT, Pcompensation is set to 0. | +| PEMAX1, PEMAX2 | Maximum TX power level of a UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in TS 38.101 [15]. If UE supports SUL frequency for this cell, PEMAX1 and PEMAX2 are obtained from the p-Max for SUL in SIB1 and NR-NS-PmaxList for SUL respectively in SIB1 , SIB2 and SIB4 as specified in TS 38.331 [3], else PEMAX1 and PEMAX2 are obtained from the p-Max and NR-NS-PmaxList respectively in SIB1 , SIB2 and SIB4 for normal UL as specified in TS 38.331 [3]. | +| PPowerClass | Maximum RF output power of the UE (dBm) according to the UE power class as defined in TS 38.101-1 [15]. | + +The signalled values Qrxlevminoffset and Qqualminoffset are only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN (TS 23.122 [9]). During this periodic search for higher priority PLMN, the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN. + +#### 5.2.3.3 E-UTRAN case in Cell Selection + +The cell selection criteria and procedures in E-UTRAN are specified in TS 36.304 [7]. + +### 5.2.4 Cell Reselection evaluation process + +#### 5.2.4.1 Reselection priorities handling + +Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the *RRCRelease* message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an NR frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field *cellReselectionPriority* is absent for that frequency). If any fields with *cellReselectionPriority* or *nsag-* + +*CellReselectionPriority* are provided in dedicated signalling, the UE shall ignore any fields with *cellReselectionPriority* and *nsag-CellReselectionPriority* provided in system information. + +When UE is in camped normally state, if it supports slice-based cell reselection and has received the network slice(s) and NSAG information from NAS to be used for cell reselection, UE shall derive reselection priorities according to clause 5.2.4.11. + +NOTE 00: UE derives reselection priorities according to clause 5.2.4.11 also in case *SIB16* (see TS 38.331 [3]) is not broadcast in the camped cell. + +If UE is in *camped on any cell* state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and *deprioritisationReq* received in *RRRelease* unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values). When the HSDN capable UE is in High-mobility state, the UE shall always consider the HSDN cells to be the highest priority (i.e., higher than any other network configured priorities). When the HSDN capable UE is not in High-mobility state, the UE shall always consider HSDN cells to be the lowest priority (i.e., lower than any other network configured priorities). If the UE is configured to perform both NR sidelink communication and V2X sidelink communication, the UE may consider the frequency providing both NR sidelink communication configuration and V2X sidelink communication configuration to be the highest priority. If the UE is configured to perform NR sidelink communication and not perform V2X communication, the UE may consider the frequency providing NR sidelink communication configuration to be the highest priority. If the UE is configured to perform V2X sidelink communication and not perform NR sidelink communication, the UE may consider the frequency providing V2X sidelink communication configuration to be the highest priority. If the UE is configured to perform ranging/sidelink positioning, the UE may consider the frequency providing ranging/sidelink positioning configuration to be the highest priority. + +A UE on a vehicle with a mobile-IAB cell may consider the frequency for which a mobile-IAB cell is the best cell to be the highest priority. The UE identifies a mobile-IAB cell by *mobileIAB-Cell* in SIB1 (see TS 38.331 [3]). The UE may narrow its search scope for mobile-IAB cell(s) by *mobileIAB-InfoList-r18* if broadcasted in SIB4 (see TS 38.331 [3]). A non-mobile-IAB cell may be excluded from this mobile IAB frequency prioritization for up to 300 seconds. + +NOTE 0a: The frequency only providing the anchor frequency configuration should not be prioritized for V2X service during cell reselection, as specified in TS 38.331[3]. + +NOTE 0b: When UE is configured to perform NR sidelink communication or V2X sidelink communication performs cell reselection, it may consider the frequencies providing the intra-carrier and inter-carrier configuration have equal priority in cell reselection. + +NOTE 0c: The prioritization among the frequencies which UE considers to be the highest priority frequency is left to UE implementation unless otherwise stated. + +NOTE 0d: The UE is configured to perform V2X sidelink communication or NR sidelink communication, if it has the capability and is authorized for the corresponding sidelink operation. + +NOTE 0e: When UE is configured to perform both NR sidelink communication and V2X sidelink communication, but cannot find a frequency which can provide both NR sidelink communication configuration and V2X sidelink communication configuration, UE may consider the frequency providing either NR sidelink communication configuration or V2X sidelink communication configuration to be the highest priority. + +NOTE 0f: Void. + +NOTE 0g: How the UE determines itself to be on a vehicle with a mobile-IAB cell is left to the UE's implementation. + +The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided. + +If the MBS broadcast capable UE is receiving or interested to receive an MBS broadcast service(s) and can only receive this MBS broadcast service(s) by camping on a frequency on which it is provided, the UE may consider that frequency to be the highest priority during the MBS broadcast session as specified in TS 38.300 [2] as long as the two following conditions are fulfilled: + +- 1) SIB1 scheduling information of the cell reselected by the UE due to frequency prioritization for MBS contains SIB20; + +2) Either: + +- One or more MBS FSAI(s) of that frequency is indicated in SIB21 of the serving cell and the same MBS FSAI(s) is also indicated for this MBS broadcast service in MBS User Service Description (USD) as specified in TS 26.346 [20], or +- SIB21 is not provided in the serving cell and that frequency is included in the USD of this service, or +- SIB21 is provided in the serving cell but does not provide the frequency mapping for the concerned service, and that frequency is included in the USD of this service. + +NOTE 0g: It is up to UE implementation which frequency to select, when the USD provides multiple frequencies for the service the UE is interested in. + +If the MBS broadcast capable UE is receiving or interested to receive an MBS broadcast service, the UE may consider cell reselection candidate frequencies at which it cannot receive the MBS broadcast service to be of the lowest priority during the MBS broadcast session as specified in TS 38.300 [2], as long as SIB1 scheduling information of the cell contains SIB20 on the MBS frequency which the UE monitors and as long as the condition 2) above is fulfilled for the serving cell. + +NOTE 0h: Example scenarios in which such down-prioritisation may be needed include the cases where camping is not possible for the UE on the MBS broadcast frequency (e.g. the MBS broadcast frequency belongs to a PLMN different from UE's registered PLMN) while the UE can receive the MBS broadcast service when camped on another frequency than the MBS broadcast frequency or current frequency. + +NOTE 0i: The frequency prioritization for MBS broadcast, NR sidelink communication, or V2X sidelink communication may override the re-selection priorities for slice-based cell reselection. + +In case UE receives *RRRelease* with *deprioritisationReq*, UE shall consider current frequency and stored frequencies due to the previously received *RRRelease* with *deprioritisationReq* or all the frequencies of NR to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running irrespective of camped RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection or SNPN selection is performed on request by NAS (TS 23.122 [9]). + +NOTE 1: UE should search for a higher priority layer for cell reselection as soon as possible after the change of priority. The minimum related performance requirements specified in TS 38.133 [8] are still applicable. + +NOTE 1a: The UE does not consider MBS broadcast, NR sidelink communication or V2X sidelink communication functionality to replace cell reselection priorities caused by HSDN or *deprioritisationReq* functionality. + +The UE shall delete priorities provided by dedicated signalling when: + +- the UE enters a different RRC state; or +- the optional validity time of dedicated priorities (T320) expires; or +- the UE receives an *RRRelease* message with the field *cellReselectionPriorities* absent; or +- a PLMN selection or SNPN selection is performed on request by NAS (TS 23.122 [9]). + +NOTE 2: Equal priorities between RATs are not supported. + +The UE shall not consider any exclude-listed cells as candidate for cell reselection. + +The UE shall consider only the allow-listed cells, if configured, as candidates for cell reselection. + +The UE in RRC\_IDLE state shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e. T320 in NR and E-UTRA), if configured, at inter-RAT cell (re)selection. + +NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system information. + +#### 5.2.4.2 Measurement rules for cell re-selection + +Following rules are used by the UE to limit needed measurements: + +- If the serving cell fulfils $S_{\text{rxlev}} > S_{\text{IntraSearchP}}$ and $S_{\text{qual}} > S_{\text{IntraSearchQ}}$ : + - If *distanceThresh* and *referenceLocation* are broadcasted in SIB19, and if UE supports location-based measurement initiation for NTN quasi-Earth-fixed system and has obtained its location information: + - If the distance between UE and the serving cell reference location *referenceLocation* is shorter than *distanceThresh*, the UE may not perform intra-frequency measurements; + - Else, the UE shall perform intra-frequency measurements; + - else if *distanceThresh* and *movingReferenceLocation* are broadcasted in SIB19, and if UE supports location-based measurement initiation for NTN Earth-moving system and has obtained its location information: + - if the distance between UE's location and the serving cell reference location determined based on *movingReferenceLocation* is shorter than *distanceThresh*, the UE may not perform intra-frequency measurements; + - else, the UE shall perform intra-frequency measurements; + - Else, the UE may not perform intra-frequency measurements; +- Else, the UE shall perform intra-frequency measurements. +- The UE shall apply the following rules for NR inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1: + - For a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies according to TS 38.133 [8]. + - For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current NR frequency: + - If the serving cell fulfils $S_{\text{rxlev}} > S_{\text{nonIntraSearchP}}$ and $S_{\text{qual}} > S_{\text{nonIntraSearchQ}}$ : + - If *distanceThresh* and *referenceLocation* are broadcasted in SIB19, and if UE supports location-based measurement initiation for NTN quasi-Earth-fixed system and has obtained its UE location information: + - If the distance between UE and the serving cell reference location *referenceLocation* is shorter than *distanceThresh*, the UE may choose not to perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority; + - Else, the UE shall perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority according to TS 38.133 [8]; + - else if *distanceThresh* and *movingReferenceLocation* are broadcasted in SIB19, and if UE supports location-based measurement initiation for NTN Earth-moving system and has obtained its location information: + - if the distance between UE's location and the serving cell reference location determined based on *movingReferenceLocation* is shorter than *distanceThresh*, the UE may not perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority; + - else, the UE shall perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority according to TS 38.133 [8]; + - Else, the UE may choose not to perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority; + - Else, the UE shall perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority according to TS 38.133 [8]. + +- If the UE supports relaxed measurement and *relaxedMeasurement* is present in *SIB2*, the UE may further relax the needed measurements, as specified in clause 5.2.4.9. +- For UE camping on NTN cell, if the UE supports skipping TN measurement, and the UE has obtained its location information, and if *coverageAreaInfoList* and *tn-AreaIdList* are broadcast in system information, the UE may not perform measurements of a TN frequency when UE is not in the coverage of that frequency provided via *tn-AreaIdList*, regardless of the frequency priority. + +If the *t-Service* of the serving cell is present in *SIB19*, and if UE supports time-based measurement initiation, the UE shall perform intra-frequency, inter-frequency or inter-RAT measurements before the *t-Service*, regardless of the distance between UE and the serving cell reference location or whether the serving cell fulfils $Srxlev > S_{IntraSearchP}$ and $Squal > S_{IntraSearchQ}$ , or $Srxlev > S_{NonIntraSearchP}$ and $Squal > S_{NonIntraSearchQ}$ . The exact time to start measurement before *t-Service* is up to UE implementation. UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies according to TS 38.133 [8] regardless of the remaining service time of the serving cell (i.e. time remaining until *t-Service*). + +NOTE 1: When evaluating the distance between UE and the serving cell reference location, it's up to UE implementation to obtain UE location information. + +NOTE 2: In the Earth-moving system, it's up to UE implementation to maintain a valid serving cell reference location, which is derived based on the serving satellite ephemeris, *epochTime* and *movingReferenceLocation*. + +#### 5.2.4.3 Mobility states of a UE + +##### 5.2.4.3.0 Introduction + +The UE mobility state is determined if the parameters ( $T_{CRmax}$ , $N_{CR\_H}$ , $N_{CR\_M}$ , $T_{CRmaxHyst}$ and *cellEquivalentSize*) are broadcasted in system information for the serving cell. + +###### State detection criteria: + +Normal-mobility state criteria: + +- If number of cell reselections during time period $T_{CRmax}$ is less than $N_{CR\_M}$ . + +Medium-mobility state criteria: + +- If number of cell reselections during time period $T_{CRmax}$ is greater than or equal to $N_{CR\_M}$ but less than or equal to $N_{CR\_H}$ . + +High-mobility state criteria: + +- If number of cell reselections during time period $T_{CRmax}$ is greater than $N_{CR\_H}$ . + +The UE shall not consider consecutive reselections where a cell is reselected again right after one reselection for mobility state detection criteria. If the UE is capable of HSDN and the *cellEquivalentSize* is configured, the UE counts the number of cell reselections for this cell as *cellEquivalentSize* configured for this cell. + +###### State transitions: + +The UE shall: + +- if the criteria for High-mobility state is detected: + - enter High-mobility state. +- else if the criteria for Medium-mobility state is detected: + - enter Medium-mobility state. +- else if criteria for either Medium- or High-mobility state is not detected during time period $T_{CRmaxHyst}$ : + - enter Normal-mobility state. + +If the UE is in High- or Medium-mobility state, the UE shall apply the speed dependent scaling rules as defined in clause 5.2.4.3.1. + +##### 5.2.4.3.1 Scaling rules + +UE shall apply the following scaling rules: + +- If neither Medium- nor High-mobility state is detected: + - no scaling is applied. +- If High-mobility state is detected: + - Add the *sf-High* of "Speed dependent ScalingFactor for $Q_{hyst}$ " to $Q_{hyst}$ if broadcasted in system information; + - For NR cells, multiply $Treselection_{NR}$ by the *sf-High* of "Speed dependent ScalingFactor for $Treselection_{NR}$ " if broadcasted in system information; + - For EUTRA cells, multiply $Treselection_{EUTRA}$ by the *sf-High* of "Speed dependent ScalingFactor for $Treselection_{EUTRA}$ " if broadcasted in system information. +- If Medium-mobility state is detected: + - Add the *sf-Medium* of "Speed dependent ScalingFactor for $Q_{hyst}$ " to $Q_{hyst}$ if broadcasted in system information; + - For NR cells, multiply $Treselection_{NR}$ by the *sf-Medium* of "Speed dependent ScalingFactor for $Treselection_{NR}$ " if broadcasted in system information; + - For EUTRA cells, multiply $Treselection_{EUTRA}$ by the *sf-Medium* of "Speed dependent ScalingFactor for $Treselection_{EUTRA}$ " if broadcasted in system information. + +In case scaling is applied to any $Treselection_{RAT}$ parameter, the UE shall round up the result after all scalings to the nearest second. + +#### 5.2.4.4 Cells with cell reservations, access restrictions or unsuitable for normal camping + +For the highest ranked cell (including serving cell) according to cell reselection criteria specified in clause 5.2.4.6, for the best cell according to absolute priority reselection criteria specified in clause 5.2.4.5, the UE shall check if the access is restricted according to the rules in clause 5.3.1. + +If that cell and other cells have to be excluded from the candidate list, as stated in clause 5.3.1, the UE shall not consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes. + +If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-frequency cell which is not suitable due to one or more of the following reasons: + +- this cell belongs to a PLMN which is not indicated as being equivalent to the registered PLMN, or +- this cell is a CAG cell that belongs to a PLMN which is equivalent to the registered PLMN but with no CAG-ID that is present in the UE's allowed CAG list being broadcasted, or +- this cell is not a CAG cell and the CAG-only indication in the UE is set, or +- this cell does not belong to a SNPN that is equal to or indicated as being equivalent to the registered or selected SNPN of the UE in SNPN access mode, + +the UE shall not consider this cell and, for operation in licensed spectrum, other cells on the same frequency as candidates for reselection for a maximum of 300 seconds. + +For operation with shared spectrum channel access, when the highest ranked cell or best cell is not a candidate for reselection per the previous paragraph, the UE should continue to consider other cells on the same frequency for cell reselection, however if the second highest ranked cell on this frequency is also not suitable due to one or more of the above reasons, the UE may consider this frequency to be the lowest priority for a maximum of 300 seconds. + +If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-frequency cell which is not suitable due to being part of the "list of 5GS forbidden TAs for roaming", the UE shall not consider this cell and other cells on the same frequency as candidates for reselection for a maximum of 300 seconds. + +If the highest ranked cell or best cell according to absolute priority reselection rules is an inter-RAT cell which is not suitable due to being part of the "list of forbidden TAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered PLMN, the UE shall not consider this cell and other cells on the same frequency, as candidates for reselection for a maximum of 300 seconds. + +If the UE enters into state *any cell selection*, any limitation shall be removed. If the UE is redirected under NR control to a frequency for which the timer is running, the limitation(s) on that frequency shall be removed. + +#### 5.2.4.5 NR Inter-frequency and inter-RAT Cell Reselection criteria + +If *threshServingLowQ* is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if: + +- A cell of a higher priority NR or EUTRAN RAT/frequency fulfils $S_{qual} > Thresh_{X, HighQ}$ during a time interval $T_{reselectionRAT}$ + +Otherwise, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if: + +- A cell of a higher priority RAT/ frequency fulfils $S_{rxlev} > Thresh_{X, HighP}$ during a time interval $T_{reselectionRAT}$ ; and +- More than 1 second has elapsed since the UE camped on the current serving cell. + +Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection as defined in clause 5.2.4.6. + +If *threshServingLowQ* is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if: + +- The serving cell fulfils $S_{qual} < Thresh_{Serving, LowQ}$ and a cell of a lower priority NR or E-UTRAN RAT/ frequency fulfils $S_{qual} > Thresh_{X, LowQ}$ during a time interval $T_{reselectionRAT}$ . + +Otherwise, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if: + +- The serving cell fulfils $S_{rxlev} < Thresh_{Serving, LowP}$ and a cell of a lower priority RAT/ frequency fulfils $S_{rxlev} > Thresh_{X, LowP}$ during a time interval $T_{reselectionRAT}$ ; and +- More than 1 second has elapsed since the UE camped on the current serving cell. + +Cell reselection to a higher priority RAT/frequency shall take precedence over a lower priority RAT/frequency if multiple cells of different priorities fulfil the cell reselection criteria. + +If more than one cell meets the above criteria, the UE shall reselect a cell as follows: + +- If the highest-priority frequency is an NR frequency, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria according to clause 5.2.4.6; +- If the highest-priority frequency is from another RAT, the strongest cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT. + +#### 5.2.4.6 Intra-frequency and equal priority inter-frequency Cell Reselection criteria + +The cell-ranking criterion $R_s$ for serving cell and $R_n$ for neighbouring cells is defined by: + +$$R_s = Q_{meas,s} + Q_{hyst} - Q_{offset_{temp}}$$ + +$$R_n = Q_{meas,n} - Q_{offset} - Q_{offset_{temp}}$$ + +where: + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $Q_{meas}$ | RSRP measurement quantity used in cell reselections. | +| $Q_{offset}$ | For intra-frequency: Equals to $Q_{offset_{s,n}}$ , if $Q_{offset_{s,n}}$ is valid, otherwise this equals to zero.
For inter-frequency: Equals to $Q_{offset_{s,n}}$ plus $Q_{offset_{frequency}}$ , if $Q_{offset_{s,n}}$ is valid, otherwise this equals to $Q_{offset_{frequency}}$ . | +| $Q_{offset_{temp}}$ | Offset temporarily applied to a cell as specified in TS 38.331 [3]. | + +The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2. + +The cells shall be ranked according to the R criteria specified above by deriving $Q_{meas,n}$ and $Q_{meas,s}$ and calculating the R values using averaged RSRP results. + +If *rangeToBestCell* is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is found to be not-suitable, the UE shall behave according to clause 5.2.4.4. + +If *rangeToBestCell* is configured, then the UE shall perform cell reselection to the cell with the highest number of beams above the threshold (i.e. *absThreshSS-BlocksConsolidation*) among the cells whose R value is within *rangeToBestCell* of the R value of the highest ranked cell. If there are multiple such cells, the UE shall perform cell reselection to the highest ranked cell among them. If this cell is found to be not-suitable, the UE shall behave according to clause 5.2.4.4. + +In all cases, the UE shall reselect the new cell, only if the following conditions are met: + +- the new cell is better than the serving cell according to the cell reselection criteria specified above during a time interval *TreselectionRAT*; +- more than 1 second has elapsed since the UE camped on the current serving cell. + +NOTE: If *rangeToBestCell* is configured but *absThreshSS-BlocksConsolidation* is not configured on an NR frequency, the UE considers that there is one beam above the threshold for each cell on that frequency. + +#### 5.2.4.7 Cell reselection parameters in system information broadcasts + +##### 5.2.4.7.0 General reselection parameters + +Cell reselection parameters are broadcast in system information and are read from the serving cell as follows: + +###### **absThreshSS-BlocksConsolidation** + +This specifies the minimum threshold for beams which can be used for selection of the highest ranked cells, if *rangeToBestCell* is configured, and for beams used for derivation of cell measurement quantity. The parameter in *SIB2* applies to the current serving frequency and the parameter in *SIB4* applies to the corresponding inter-frequency. + +###### **cellReselectionPriority** + +This specifies the absolute priority for NR frequency or E-UTRAN frequency. + +###### **cellReselectionSubPriority** + +This specifies the fractional priority value added to *cellReselectionPriority* for NR frequency or E-UTRAN frequency. + +###### **combineRelaxedMeasCondition** + +This indicates when the UE needs to fulfil both low mobility criterion and not-at-cell-edge criterion to determine whether to relax measurement requirements. + +###### **combineRelaxedMeasCondition2** + +This indicates when an (e)RedCap UE needs to fulfil both stationary criterion and not-at-cell-edge criterion to determine whether to relax measurement requirements. + +###### **coverageAreaInfoList** + +This indicates a list of TN coverage areas to assist skipping TN measurements for NTN UEs in RRC\_IDLE and RRC\_INACTIVE states. + +###### **distanceThresh** + +This indicates the distance threshold from the serving cell reference location to be used in location-based measurement initiation. + +###### **movingReferenceLocation** + +This indicates the reference location of the serving cell at a time reference, to be used in location-based measurement initiation for NTN Earth-moving system. + +###### **nrofSS-BlocksToAverage** + +This specifies the number of beams which can be used for selection of the highest ranked cell, if *rangeToBestCell* is configured, and the number of beams used for derivation of cell measurement quantity. The parameter in *SIB2* applies to the current serving frequency and the parameter in *SIB4* applies to the corresponding inter-frequency. + +###### **Qoffsets,n** + +This specifies the offset between the two cells. + +###### **Qoffsetfrequency** + +Frequency specific offset for equal priority NR frequencies. + +###### **Qhyst** + +This specifies the hysteresis value for ranking criteria. + +###### **Qoffsettemp** + +This specifies the additional offset to be used for cell selection and re-selection. It is temporarily used in case the RRC Connection Establishment fails on the cell as specified in TS 38.331 [3]. + +###### **Qqualmin** + +This specifies the minimum required quality level in the cell in dB. + +###### **Qrxlevmin** + +This specifies the minimum required Rx level in the cell in dBm. + +###### **Qrxlevminoffsetcell** + +This specifies the cell specific Rx level offset in dB to Qrxlevmin. + +###### **Qqualminoffsetcell** + +This specifies the cell specific quality level offset in dB to Qqualmin. + +###### **rangeToBestCell** + +This specifies the R value range which the cells whose R value is within the range can be a candidate for the highest ranked cell. It is configured in *SIB2* and used for intra-frequency and equal priority inter-frequency cell reselection and among the cells on the highest priority frequency(ies) for inter-frequency cell reselection within NR. + +###### **referenceLocation** + +This indicates the reference location of the serving cell to be used in location-based measurement initiation for NTN (quasi-)Earth-fixed system. + +###### **SIntraSearchP** + +This specifies the Srxlev threshold (in dB) for intra-frequency measurements. + +###### **SIntraSearchQ** + +This specifies the Squal threshold (in dB) for intra-frequency measurements. + +###### **SNonIntraSearchP** + +This specifies the Srxlev threshold (in dB) for NR inter-frequency and inter-RAT measurements. + +###### **SNonIntraSearchQ** + +This specifies the Squal threshold (in dB) for NR inter-frequency and inter-RAT measurements. + +###### **SSearchDeltaP** + +This specifies the threshold (in dB) on Srxlev variation for relaxed measurement. + +###### **SSearchDeltaP-Stationary** + +This specifies the threshold (in dB) on Srxlev variation to evaluate stationary criterion for relaxed measurement. + +###### **SSearchThresholdP** + +This specifies the Srxlev threshold (in dB) for relaxed measurement. + +###### **SSearchThresholdP2** + +This specifies the Srxlev threshold (in dB) to evaluate not-at-cell-edge-criterion for relaxed measurement. + +###### **SSearchThresholdQ** + +This specifies the Squal threshold (in dB) for relaxed measurement. + +###### **SSearchThresholdQ2** + +This specifies the Squal threshold (in dB) to evaluate not-at-cell-edge-criterion for relaxed measurement. + +###### **TreselectionRAT** + +This specifies the cell reselection timer value. For each target NR frequency and for each RAT other than NR, a specific value for the cell reselection timer is defined, which is applicable when evaluating reselection within NR or towards other RAT (i.e. TreselectionRAT for NR is TreselectionNR, for E-UTRAN TreselectionEUTRA). + +NOTE: TreselectionRAT is not broadcast in system information but used in reselection rules by the UE for each RAT. + +###### **TreselectionNR** + +This specifies the cell reselection timer value TreselectionRAT for NR. The parameter can be set per NR frequency as specified in TS 38.331 [3]. + +###### **TreselectionEUTRA** + +This specifies the cell reselection timer value TreselectionRAT for E-UTRAN. + +###### **ThreshX, HighP** + +This specifies the Srxlev threshold (in dB) used by the UE when reselecting towards a higher priority RAT/ frequency than the current serving frequency. Each frequency of NR and E-UTRAN might have a specific threshold. + +###### **ThreshX, HighQ** + +This specifies the Squal threshold (in dB) used by the UE when reselecting towards a higher priority RAT/ frequency than the current serving frequency. Each frequency of NR and E-UTRAN might have a specific threshold. + +###### **ThreshX, LowP** + +This specifies the Srxlev threshold (in dB) used by the UE when reselecting towards a lower priority RAT/ frequency than the current serving frequency. Each frequency of NR and E-UTRAN might have a specific threshold. + +###### **ThreshX, LowQ** + +This specifies the Squal threshold (in dB) used by the UE when reselecting towards a lower priority RAT/ frequency than the current serving frequency. Each frequency of NR and E-UTRAN might have a specific threshold. + +###### **ThreshServing, LowP** + +This specifies the Srxlev threshold (in dB) used by the UE on the serving cell when reselecting towards a lower priority RAT/ frequency. + +###### **ThreshServing, LowQ** + +This specifies the Squal threshold (in dB) used by the UE on the serving cell when reselecting towards a lower priority RAT/ frequency. + +###### **TSearchDeltaP** + +This specifies the time period over which the Srxlev variation is evaluated for relaxed measurement. + +###### **TSearchDeltaP-Stationary** + +This specifies the time period over which the Srxlev variation is evaluated for stationary criterion for relaxed measurement. + +###### **t-Service** + +This indicates the time when an NTN cell is going to stop serving the area where it is currently covering, to be used in time-based measurement initiation. + +###### **tn-AreaIdList** + +This indicates a list of TN area identities associated with each frequency to assist skipping TN measurements for NTN UEs in RRC\_IDLE and RRC\_INACTIVE states. Each TN area identity in the list identifies a TN coverage area. + +##### 5.2.4.7.1 Speed dependent reselection parameters + +Speed dependent reselection parameters are broadcast in system information and are read from the serving cell as follows: + +###### **TCRmax** + +This specifies the duration for evaluating allowed amount of cell reselection(s). + +###### **NCR\_M** + +This specifies the maximum number of cell reselections to enter Medium-mobility state. + +###### **NCR\_H** + +This specifies the maximum number of cell reselections to enter High-mobility state. + +###### **TCRmaxHyst** + +This specifies the additional time period before the UE can enter Normal-mobility state. + +###### **Speed dependent ScalingFactor for Qhyst** + +This specifies scaling factor for Qhyst in *sf-High* for High-mobility state and *sf-Medium* for Medium-mobility state. + +###### **Speed dependent ScalingFactor for TreselectionNR** + +This specifies scaling factor for $\text{Treselection}_{\text{NR}}$ in *sf-High* for High-mobility state and *sf-Medium* for Medium-mobility state. + +###### Speed dependent ScalingFactor for TreselectionEUTRA + +This specifies scaling factor for $\text{Treselection}_{\text{EUTRA}}$ in *sf-High* for High-mobility state and *sf-Medium* for Medium-mobility state. + +##### 5.2.4.7.2 Slice-based cell reselection parameters + +Slice-based cell reselection parameters are broadcast in system information and are read from the serving cell as follows: + +###### nsag-CellReselectionPriority + +This specifies the priority for NR frequency when the given NSAG ID is used to set the frequency priority. + +###### nsag-CellReselectionSubPriority + +This specifies the fractional priority value added to *nsag-CellReselectionPriority* when the given NSAG ID is used to set the frequency priority. + +#### 5.2.4.8 Inter-RAT Cell reselection in RRC\_INACTIVE state + +For UE in the RRC\_INACTIVE state, upon cell reselection to another RAT, UE transitions from RRC\_INACTIVE to RRC\_IDLE and performs actions as specified in TS 38.331 [3]. + +#### 5.2.4.9 Relaxed measurement + +##### 5.2.4.9.0 Relaxed measurement rules + +When the UE is required to perform measurements of intra-frequency cells or NR inter-frequency cells or inter-RAT frequency cells according to the measurement rules in clause 5.2.4.2: + +- if *lowMobilityEvaluation* is configured and *cellEdgeEvaluation* is not configured; and +- if the UE has performed normal intra-frequency, NR inter-frequency, or inter-RAT frequency measurements for at least $T_{\text{SearchDeltaP}}$ after (re-)selecting a new cell; and +- if the relaxed measurement criterion in clause 5.2.4.9.1 is fulfilled for a period of $T_{\text{SearchDeltaP}}$ : + - the UE may choose to perform relaxed measurements for intra-frequency cells, NR inter-frequency cells or inter-RAT frequency cells according to relaxation methods in clauses 4.2.2.9, 4.2.2.10, 4.2.2.11, 4.2C.2.7 and 4.2C.2.8 in TS 38.133 [8]; +- if *cellEdgeEvaluation* is configured and *lowMobilityEvaluation* is not configured; and +- if the relaxed measurement criterion in clause 5.2.4.9.2 is fulfilled: + - the UE may choose to perform relaxed measurements for intra-frequency cells according to relaxation methods in clauses 4.2.2.9 and 4.2C.2.7 in TS 38.133 [8]; + - if the serving cell fulfils $\text{Srxlev} \leq \text{S}_{\text{nonIntraSearchP}}$ or $\text{Squal} \leq \text{S}_{\text{nonIntraSearchQ}}$ : + - the UE may choose to perform relaxed measurements for NR inter-frequency cells or inter-RAT frequency cells according to relaxation methods in clauses 4.2.2.10, 4.2.2.11 and 4.2C.2.8 in TS 38.133 [8]; +- if both *lowMobilityEvaluation* and *cellEdgeEvaluation* are configured: + - if the UE has performed normal intra-frequency, NR inter-frequency, or inter-RAT frequency measurements for at least $T_{\text{SearchDeltaP}}$ after (re-)selecting a new cell; and + - if the relaxed measurement criterion in clause 5.2.4.9.1 is fulfilled for a period of $T_{\text{SearchDeltaP}}$ ; and + +- if the relaxed measurement criterion in clause 5.2.4.9.2 is fulfilled: + - the UE may choose to perform relaxed measurements for NR intra-frequency cells, inter-frequency cells or inter-RAT frequency cells according to relaxation methods in clauses 4.2.2.9, 4.2.2.10, 4.2.2.11, 4.2C.2.7 and 4.2C.2.8 in TS 38.133 [8]; +- else: + - if the UE has performed normal intra-frequency, NR inter-frequency, or inter-RAT frequency measurements for at least $T_{\text{SearchDeltaP}}$ after (re-)selecting a new cell, and the relaxed measurement criterion in clause 5.2.4.9.1 is fulfilled for a period of $T_{\text{SearchDeltaP}}$ ; or, + - if the relaxed measurement criterion in clause 5.2.4.9.2 is fulfilled: + - if *combineRelaxedMeasCondition* is not configured: + - the UE may choose to perform relaxed measurements for intra-frequency cells, NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority according to relaxation methods in clauses 4.2.2.9, 4.2.2.10, 4.2.2.11, 4.2C.2.7 and 4.2C.2.8 in TS 38.133 [8]; + - if the serving cell fulfils $S_{\text{rxlev}} \leq S_{\text{nonIntraSearchP}}$ or $S_{\text{qual}} \leq S_{\text{nonIntraSearchQ}}$ : + - the UE may choose to perform relaxed measurement for NR inter-frequency cells of higher priority, or inter-RAT frequency cells of higher priority according to relaxation methods in clauses 4.2.2.10, 4.2.2.11 and 4.2C.2.8 in TS 38.133 [8]; + - if the UE is an (e)RedCap UE; and + - if *stationaryMobilityEvaluation* is configured and *cellEdgeEvaluationWhileStationary* is not configured; and + - if the UE has performed normal intra-frequency, NR inter-frequency, or inter-RAT frequency measurements for at least $T_{\text{SearchDeltaP-Stationary}}$ after (re-)selecting a new cell; and + - if the relaxed measurement criterion in clause 5.2.4.9.3 is fulfilled for a period of $T_{\text{SearchDeltaP-Stationary}}$ : + - the UE may choose to perform relaxed measurements for intra-frequency cells, NR inter-frequency cells, or inter-RAT frequency cells according to relaxation methods in clauses 4.2B.2.9, 4.2B.2.10, and 4.2B.2.11 in TS 38.133 [8]; + - if the UE is an (e)RedCap UE; and + - if both *stationaryMobilityEvaluation* and *cellEdgeEvaluationWhileStationary* are configured: + - if the UE has performed normal intra-frequency, NR inter-frequency, or inter-RAT frequency measurements for at least $T_{\text{SearchDeltaP-Stationary}}$ after (re-)selecting a new cell; and + - if the relaxed measurement criterion in clause 5.2.4.9.4 is fulfilled: + - the UE may choose to perform relaxed measurements for intra-frequency cells, NR inter-frequency cells, or inter-RAT frequency cells according to relaxation methods in clauses 4.2B.2.9, 4.2B.2.10, and 4.2B.2.11 in TS 38.133 [8]; + - else: + - if *combineRelaxedMeasCondition2* is not configured: + - if the UE has performed normal intra-frequency, NR inter-frequency, or inter-RAT frequency measurements for at least $T_{\text{SearchDeltaP-Stationary}}$ after (re-)selecting a new cell; and + - if the relaxed measurement criterion in clause 5.2.4.9.3 is fulfilled for a period of $T_{\text{SearchDeltaP-Stationary}}$ : + - the UE may choose to perform relaxed measurements for intra-frequency cells, NR inter-frequency cells, or inter-RAT frequency cells according to relaxation methods in clauses 4.2B.2.9, 4.2B.2.10, and 4.2B.2.11 in TS 38.133 [8]; + +NOTE 1: It is up to UE implementation when to start performing relaxed measurements in RRC Idle/Inactive if multiple methods are configured. + +NOTE 2: It is up to UE implementation which relaxation method to perform based on the "allowed" cases as specified in TS 38.133 [8] for RRC Idle/Inactive if multiple methods are configured. + +The above relaxed measurements and no measurement are not applicable for frequencies that are included in *VarMeasIdleConfig*, if configured and for which the UE supports dual connectivity or carrier aggregation between those frequencies and the frequency of the current serving cell. + +##### 5.2.4.9.1 Relaxed measurement criterion for UE with low mobility + +The relaxed measurement criterion for UE with low mobility is fulfilled when: + +- $(Srxlev_{Ref} - Srxlev) < S_{SearchDeltaP}$ , + +Where: + +- $Srxlev$ = current $Srxlev$ value of the serving cell (dB). +- $Srxlev_{Ref}$ = reference $Srxlev$ value of the serving cell (dB), set as follows: + - After selecting or reselecting a new cell, or + - If $(Srxlev - Srxlev_{Ref}) > 0$ , or + - If the relaxed measurement criterion has not been met for $T_{SearchDeltaP}$ : + - The UE shall set the value of $Srxlev_{Ref}$ to the current $Srxlev$ value of the serving cell. + +##### 5.2.4.9.2 Relaxed measurement criterion for UE not at cell edge + +The relaxed measurement criterion for UE not at cell edge is fulfilled when: + +- $Srxlev > S_{SearchThresholdP}$ , and, +- $Squal > S_{SearchThresholdQ}$ , if $S_{SearchThresholdQ}$ is configured, + +Where: + +- $Srxlev$ = current $Srxlev$ value of the serving cell (dB). +- $Squal$ = current $Squal$ value of the serving cell (dB). + +##### 5.2.4.9.3 Relaxed measurement criterion for a stationary (e)RedCap UE + +The relaxed measurement criterion for a stationary (e)RedCap UE is fulfilled when: + +- $(Srxlev_{RefStationary} - Srxlev) < S_{SearchDeltaP-Stationary}$ , + +Where: + +- $Srxlev$ = current $Srxlev$ value of the serving cell (dB). +- $Srxlev_{RefStationary}$ = reference $Srxlev$ value of the serving cell (dB), set as follows: + - After selecting or reselecting a new cell, or + - If $(Srxlev - Srxlev_{RefStationary}) > 0$ , or + - If the relaxed measurement criterion has not been met for $T_{SearchDeltaP-Stationary}$ : + - The UE shall set the value of $Srxlev_{RefStationary}$ to the current $Srxlev$ value of the serving cell. + +##### 5.2.4.9.4 Relaxed measurement criterion for a stationary (e)RedCap UE not at cell edge + +The relaxed measurement criterion for a stationary (e)RedCap UE not at cell edge is fulfilled when: + +- the relaxed measurement criterion in clause 5.2.4.9.3 is fulfilled for a period of $T_{SearchDeltaP-Stationary}$ , + +- $Srxlev > S_{SearchThresholdP2}$ , and, +- $Squal > S_{SearchThresholdQ2}$ , if $S_{SearchThresholdQ2}$ is configured. + +Where: + +- $Srxlev$ = current $Srxlev$ value of the serving cell (dB). +- $Squal$ = current $Squal$ value of the serving cell (dB). + +#### 5.2.4.10 Cell reselection with CAG cells + +In addition to normal cell reselection, a UE may optionally use an autonomous search function to detect CAG cells on serving and non-serving frequencies. However UE shall follow the cell reselection criteria based on dedicated frequency priorities and only follow the autonomous cell search result if the result fulfils also the existing cell reselection criteria based on dedicated frequency priorities. + +NOTE: Mobile-IAB cell reselection priority handling as specified in clause 5.2.4.1 is applicable for a mobile-IAB cell irrespective of whether this cell is a CAG cell or not. + +#### 5.2.4.11 Reselection priorities for slice-based cell reselection + +The UE derives reselection priorities for slice-based cell reselection by using: + +- NAS provided NSAG information, only for NSAG(s) associated with the network slice(s) provided by NAS for cell reselection (see TS 23.501 [10], TS 24.501 [14]), +- *sliceInfoList* and/or *sliceInfoListDedicated* per frequency with *nsag-CellReselectionPriority* per NSAG, if provided in system information and/or dedicated signalling (see TS 38.331 [3]), +- *cellReselectionPriority* per frequency provided in system information and/or dedicated signalling (see TS 38.331 [3]). + +The UE considers an NR frequency to support all slices of an NSAG if + +- the nsag-ID and TA of the NSAG indicated for the NR frequency (see TS 38.331[3]) are included in the NSAG information provided by NAS. If *FreqPriorityListDedicatedSlicing* is configured, UE only considers the NSAG-frequency pairs indicated in *FreqPriorityListDedicatedSlicing* for slice-based cell reselection. + +The UE considers a cell on an NR frequency to support all slices of an NSAG if + +- the nsag-ID and TA of the NSAG indicated for the NR frequency in dedicated signalling but not in *SIB16* (see TS 38.331 [3]) are included in the NSAG information provided by NAS; or +- the nsag-ID and TA of the NSAG indicated for the NR frequency in *SIB16* (see TS 38.331 [3]) are included in the NSAG information provided by NAS; and + - the cell is either listed in the *sliceAllowedCellListNR* (if provided in the *sliceInfoList*) or the cell is not listed in the *sliceExcludedCellListNR* (if provided in the *sliceInfoList*); or + - Neither *sliceAllowedCellListNR* nor *sliceExcludedCellListNR* is configured in the *sliceInfoList*. + +The UE shall derive reselection priorities for slice-based cell reselection according to the following rules: + +- Frequencies that support at least one prioritized NSAG received from NAS have higher reselection priority than frequencies that support none of the NSAG(s) received from NAS. +- Frequencies that support at least one NSAG provided by NAS are prioritised in the order of the NAS-provided priority for the NSAG with highest priority supported on the frequency. +- Among the frequencies (one or multiple) that support the highest prioritised NSAG(s) with the same NAS-provided priorities, the frequencies are prioritized in the order of their highest *nsag-CellReselectionPriority* given for these NSAG(s). If no *nsag-CellReselectionPriority* is given for a NSAG at a frequency, the lowest priority value is used (i.e, lower than any of the network configured values for these frequencies). + +- Frequencies that support none of the NSAG(s) provided by NAS are prioritized in the order of their *cellReselectionPriority*. + +For a UE performing slice-based cell reselection, if the highest ranked cell or best cell in a frequency fulfils the inter-frequency cell reselection criteria (see clause 5.2.4.5) based on reselection priority for the frequency and NSAG derived according to this clause or fulfils intra-frequency and equal priority inter-frequency cell reselection criteria (see clause 5.2.4.6), but this cell does not support the NSAG according to this clause: + +- if this cell supports any other NSAG(s) according to this clause, the UE shall re-derive a reselection priority for the frequency by considering the NSAG(s) supported by this cell (rather than those of the corresponding NR frequency); +- Otherwise, the UE shall re-derive a reselection priority for the frequency as if none of the NSAG(s) provided by NAS is supported. + +This re-derived reselection priority is used for a maximum of 300 seconds, or until new network slice(s) and/or NSAG information are received from NAS. UE shall ensure the cell reselection criteria above are fulfilled based on the newly derived priorities. + +### 5.2.5 Camped Normally state + +This state is applicable for RRC\_IDLE and RRC\_INACTIVE state. + +When camped normally, the UE shall perform the following tasks: + +- monitor the paging channel of the cell as specified in clause 7 according to information broadcast in *SIB1*; +- monitor Short Messages transmitted with P-RNTI over DCI as specified in clause 6.5 in TS 38.331 [3]; +- monitor relevant System Information as specified in TS 38.331 [3]; +- perform necessary measurements for the cell reselection evaluation procedure; +- execute the cell reselection evaluation process on the following occasions/triggers: + - 1) UE internal triggers, so as to meet performance as specified in TS 38.133 [8]; + - 2) When information on the BCCH used for the cell reselection evaluation procedure has been modified. + - 3) When the network slice(s) and/or NSAG information received from NAS changes. + +### 5.2.6 Selection of cell at transition to RRC\_IDLE or RRC\_INACTIVE state + +At reception of *RRCRelease* message to transition the UE to RRC\_IDLE or RRC\_INACTIVE, UE shall attempt to camp on a suitable cell according to *redirectedCarrierInfo* if included in the *RRCRelease* message. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the *RRCRelease* message does not contain the *redirectedCarrierInfo*, UE shall attempt to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to find a suitable cell to camp on. + +When returning to RRC\_IDLE state after UE moved to RRC\_CONNECTED state from *camped on any cell* state, UE shall attempt to camp on an acceptable cell according to *redirectedCarrierInfo*, if included in the *RRCRelease* message. If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the *RRCRelease* message does not contain *redirectedCarrierInfo* UE shall attempt to select an acceptable cell on an NR frequency. If no acceptable cell is found according to the above, the UE not in SNPN Access Mode shall continue to search for an acceptable cell of any PLMN in state *any cell selection*. If no acceptable cell is found according to the above, the UE in SNPN access mode shall continue to search for an acceptable cell of any SNPN in state *any cell selection*. + +### 5.2.7 Any Cell Selection state + +This state is applicable for RRC\_IDLE and RRC\_INACTIVE state. In this state, the UE shall perform cell selection process to find a suitable cell. If the cell selection process fails to find a suitable cell after a complete scan of all RATs + +and all frequency bands supported by the UE, the UE not in SNPN Access Mode shall attempt to find an acceptable cell of any PLMN to camp on, trying all RATs that are supported by the UE and searching first for a high-quality cell, as defined in clause 5.1.1.2. If the cell selection process fails to find a suitable cell after a complete scan of all frequency bands supported by the UE, the UE in SNPN access mode shall attempt to find an acceptable cell of any SNPN to camp on. + +The UE, which is not camped on any cell, shall stay in this state. + +### 5.2.8 Camped on Any Cell state + +This state is only applicable for RRC\_IDLE state. In this state, the UE shall perform the following tasks: + +- monitor Short Messages transmitted with P-RNTI over DCI as specified in clause 6.5 in TS 38.331 [3]; +- monitor relevant System Information as specified in TS 38.331 [3]; +- perform necessary measurements for the cell reselection evaluation procedure; +- execute the cell reselection evaluation process on the following occasions/triggers: + - 1) UE internal triggers, so as to meet performance as specified in TS 38.133 [8]; + - 2) When information on the BCCH used for the cell reselection evaluation procedure has been modified. +- regularly attempt to find a suitable cell trying all frequencies of all RATs that are supported by the UE. If a suitable cell is found, UE shall move to *camped normally* state. +- if the UE supports voice services, the UE is not in SNPN access mode, and the current cell does not support IMS emergency calls as indicated by the field *ims-EmergencySupport* in SIB1 as specified in TS 38.331 [3], the UE shall perform cell selection/reselection to an acceptable cell that supports emergency calls in any supported RAT regardless of priorities provided in system information from current cell, if no suitable cell is found. +- if the UE supports voice services, the UE is in SNPN access mode, and the current cell does not support IMS emergency calls for any SNPN(s) as indicated by the field *imsEmergencySupportForSNPN* in SIB1 as specified in TS 38.331 [3], the UE shall perform cell selection/reselection to an acceptable cell of any available SNPN that supports emergency calls, if no suitable cell is found. + +## 5.3 Cell Reservations and Access Restrictions + +### 5.3.0 Introduction + +There are two mechanisms which allow an operator to impose cell reservations or access restrictions. The first mechanism uses indication of cell status and special reservations for control of cell selection and reselection procedures. The second mechanism, referred to as Unified Access Control as specified in TS 38.331 [3], shall allow preventing selected access categories or access identities from sending initial access messages for load control reasons. + +Unified Access Control does not apply to IAB-MTs and NCR-MTs. + +### 5.3.1 Cell status and cell reservations + +Cell status and cell reservations are indicated in the *MIB* or *SIB1* message as specified in TS 38.331 [3] by means of following fields: + +- *cellBarred* (IE type: "barred" or "not barred") +Indicated in *MIB* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is ignored by UEs supporting NTN while *cellBarredNTN* is included in SIB1. +- *cellBarredATG* (IE type: "barred" or "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to ATG UEs. + +- *cellBarred-eRedCap1Rx* (IE type: "barred" or "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to eRedCap UEs. +- *cellBarred-eRedCap2Rx* (IE type: "barred" or "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to eRedCap UEs. +- *cellBarredNES* (IE type: "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to UEs capable of NES cell DTX/DRX. +- *cellBarredNTN* (IE type: "barred" or "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs indicated in *SIB1*, this field is common for all PLMNs. This field is ignored if the UE does not support NTN connectivity. +- *cellBarredRedCap1Rx* (IE type: "barred" or "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to RedCap UEs. +- *cellBarredRedCap2Rx* (IE type: "barred" or "not barred") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to RedCap UEs. +- *cellReservedForOperatorUse* (IE type: "reserved" or "not reserved") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is specified per PLMN or per SNPN. +- *cellReservedForOtherUse* (IE type: "true") +Indicated in *SIB1* message. In case of multiple PLMNs indicated in *SIB1*, this field is common for all PLMNs. +- *cellReservedForFutureUse* (IE type: "true") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. + +NOTE 0: IAB-MT ignores the *cellBarred*, *cellReservedForOperatorUse*, *cellReservedForFutureUse*, and *intraFreqReselection* (i.e. treats *intraFreqReselection* as if it was set to *allowed*) as defined in TS 38.331 [3]. IAB-MT also ignores *cellReservedForOtherUse* for cell barring determination (i.e. NPN capable IAB-MT considers *cellReservedForOtherUse* for determination of an NPN-only cell) as defined in TS 38.331 [3]. + +NOTE 0a: NCR-MT ignores the *cellBarred*, *cellReservedForOperatorUse*, *cellReservedForFutureUse*, and *intraFreqReselection* (i.e. treats *intraFreqReselection* as if it was set to *allowed*) as defined in TS 38.331 [3]. NCR-MT also ignores *cellReservedForOtherUse* for cell barring determination (i.e. NPN capable NCR-MT considers *cellReservedForOtherUse* for determination of an NPN-only cell) as defined in TS 38.331 [3]. + +- *halfDuplexRedCapAllowed* (IE type: "true") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. This field is only applicable to (e)RedCap UEs. +- *iab-Support* (IE type: "true") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is specified per PLMN or per SNPN. +- *ncri-Support* (IE type: "true") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is common for all PLMNs and NPNs. +- *mobileIAB-Support* (IE type: "true") +Indicated in *SIB1* message. In case of multiple PLMNs or NPNs indicated in *SIB1*, this field is specified per PLMN or per SNPN. + +When cell status is indicated as "not barred" and "not reserved" for operator use and not "true" for other use and not "true" for future use, + +- UEs shall treat this cell as candidate during the cell selection and cell reselection procedures. + +When cell broadcasts any CAG-IDs or NIDs and the cell status is indicated as "not barred" and "not reserved" for operator use and "true" for other use, and not "true" for future use: + +- All NPN-capable UEs shall treat this cell as candidate during the cell selection and cell reselection procedures, other UEs shall treat this cell as if cell status is "barred". + +When cell status is indicated as "true" for other use, and either cell does not broadcast any CAG-IDs or NIDs or does not broadcast any CAG-IDs and the UE is not operating in SNPN Access Mode, + +- The UE shall treat this cell as if cell status is "barred". + +When cell status is indicated as "true" for future use, + +- The UE shall treat this cell as if cell status is "barred". + +When *cellBarredNES* is absent and *cellBarred* is set to "barred", + +- The UE capable of NES cell DTX/DRX shall treat this cell as if cell status is "barred". + +When *cellBarredNTN* is not broadcast in this cell, + +- For NTN access, the UE shall treat this cell as if cell status is "barred". + +When *halfDuplexRedCapAllowed* is not broadcast in this cell, + +- The (e)RedCap UE only capable of operating in half-duplex for FDD shall treat this cell as if cell status is "barred". + +When *cellBarredATG* is not broadcast in this cell, + +- For ATG access, the UE shall treat this cell as if cell status is "barred". + +When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN/SNPN and not "true" for other use and not "true" for future use, + +- UEs assigned to Access Identity 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate during the cell selection and reselection procedures if the field *cellReservedForOperatorUse* for that PLMN set to "reserved". +- UEs assigned to Access Identity 11 or 15 shall treat this cell as candidate during the cell selection and reselection procedures if the field *cellReservedForOperatorUse* for selected/registered SNPN is set to "reserved". +- UEs assigned to an Access Identity 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN/SNPN or the selected PLMN/SNPN. +- UEs assigned to Access Identity 3 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN. + +NOTE 1: Access Identities 11, 15 are only valid for use in the HPLMN/ EHPLMN and registered/selected SNPN; Access Identities 12, 13, 14 are only valid for use in the home country and registered/selected SNPN as specified in TS 22.261 [12]. + +NOTE 1a: Access Identity 3 is only valid for PLMNs that indicate to potential Disaster Inbound Roamers that the UEs can access the PLMN as specified in TS 22.261 [12]. + +When cell status "barred" is indicated or to be treated as if the cell status is "barred", + +- The UE is not permitted to select/reselect this cell, not even for emergency calls. +- The UE shall select another cell according to the following rule: + +- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the *MIB*: + - the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds. + - the UE may select another cell on the same frequency if the selection criteria are fulfilled. +- else: + - If the UE is a RedCap UE, the UE shall acquire SIB1 and, in the remainder of this procedure, consider 'intraFreqReselection in MIB' to be 'intraFreqReselectionRedCap in SIB1', if available; + - If the UE is an eRedCap UE, the UE shall acquire SIB1 and, in the remainder of this procedure, consider 'intraFreqReselection in MIB' to be 'intraFreqReselection-eRedCap in SIB1', if available. + - If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1: + - the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds. + - the UE may select another cell on the same frequency if the selection criteria are fulfilled. + - If the cell status "barred" is indicated in *MIB* but the UE is unable to acquire the SIB1; or + - If the cell is to be treated as if the cell status is "barred" due to not supporting (e)RedCap UEs: + - the UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds. + - the UE may select another cell on the same frequency if re-selection criteria are fulfilled. + - If the UE is neither a RedCap UE nor an eRedCap UE, or if the UE is a RedCap UE and *intraFreqReselectionRedCap* in SIB1 is available, or if the UE is an eRedCap UE and *intraFreqReselection-eRedCap* in SIB1 is available: + - If the field *intraFreqReselection* in *MIB* message is set to "allowed": + - the UE may select another cell on the same frequency if re-selection criteria are fulfilled; + - If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the *SIB1*: + - the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds; + - else: + - the UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds. + - If the field *intraFreqReselection* in *MIB* message is set to "not allowed": + - If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the *SIB1*: + - the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds; + - If the cell operates in licensed spectrum: + - the UE shall not re-select to another cell on the same frequency as the barred cell and exclude such cell(s) as candidate(s) for cell selection/reselection for 300 seconds; + - else: + - the UE may select to another cell on the same frequency if the reselection criteria are fulfilled. + - else: + - If the cell operates in licensed spectrum, or if this cell belongs to a PLMN which is indicated as being equivalent to the registered PLMN or the selected PLMN of the UE, or if this cell belongs to an SNPN which is equal to or indicated as being equivalent to the registered SNPN or the selected SNPN of the UE: + +- the UE shall not re-select to another cell on the same frequency as the barred cell and exclude such cell(s) as candidate(s) for cell selection/reselection for 300 seconds; +- else: + - the UE may select to another cell on the same frequency if the reselection criteria are fulfilled. + - the UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds. + +The cell selection of another cell may also include a change of RAT. + +NOTE 2: If barring of a cell is triggered by the condition of *trackingAreaCode* and *trackingAreaList* not being provided, as specified in TS 38.331 [3], the barring only applies to this PLMN and the UE can re-evaluate the barring condition again due to selection of another PLMN. + +### 5.3.2 Unified access control + +The information on cell access restrictions associated with Access Categories and Identities is broadcast in *SIB1* as part of Unified Access Control as specified in TS 38.331 [3]. + +The UE shall ignore Access Category and Identity related cell access restrictions for cell reselection. A change of the indicated access restriction shall not trigger cell reselection by the UE. + +The UE shall consider Access Category and Identity related cell access restrictions for NAS initiated access attempts and RNAU as specified in TS 38.331 [3]. + +A L2 U2N Relay UE does not need to perform the Unified Access Control as specified in TS 38.331 [3], due to the U2N Remote UE access attempt. + +## 5.4 Tracking Area registration + +In the UE, the AS shall report tracking area information to the NAS. + +If the UE reads more than one PLMN identity in the current cell, the UE shall report the found PLMN identities that make the cell suitable in the tracking area information to NAS. + +If the UE operating in SNPN access mode reads more than one SNPN identity in the current cell, the UE shall report the found SNPN identities that make the cell suitable in the tracking area information to NAS. + +The AS of an L2 U2N Remote UE in RRC\_IDLE or in RRC\_INACTIVE may report the tracking area information to NAS based on the system information received from the connected L2 U2N Relay UE. + +The NAS part of the location registration process is specified in TS 23.122 [9]. + +## 5.5 RAN Area registration + +The UE performs a RAN-based notification area update (RNAU) periodically or when the UE selects a cell that does not belong to the configured RNA. + +A L2 U2N Remote UE, while in RRC\_INACTIVE performs RNAU periodically or when the serving cell of the L2 U2N Relay UE changes (e.g., due to reconfiguration with sync, when a different L2 U2N Relay UE is reselected, or when the L2 U2N Relay UE reselects a new cell) and this new serving cell does not belong to the configured RNA of L2 U2N Remote UE. + +# --- 6 Reception of broadcast information + +## 6.1 Reception of system information + +The NAS is informed if the cell selection and reselection results in changes in the received NAS system information. + +The UE shall monitor the Paging Occasions (POs) as described in clause 7.1 to receive System Information change notifications in RRC\_IDLE and RRC\_INACTIVE. The changes in the system information are notified by the network using a Short Message as specified in TS 38.331 [3]. When the Short Message notifies system information changes, then the UE shall acquire or re-acquire the concerned system information as specified in TS 38.331 [3]. + +A L2 U2N Remote UE when in RRC\_IDLE or RRC\_INACTIVE may not monitor POs as described in clause 7.1 to receive Short Message when connected with a U2N Relay UE, as specified in TS 38.331 [3]. + +A L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE does not receive Short Message from a L2 U2N Relay UE. When receiving a Short Message, the L2 U2N Relay UE may forward to the L2 U2N Remote UE only Public Warning System information (e.g., SIB6, SIB7, and SIB8). + +When system information changes, the L2 U2N Remote UE, when in RRC\_IDLE or RRC\_INACTIVE, relies on the U2N L2 Relay UE to acquire or re-acquire the concerned system information and forward them. Further, the L2 U2N Remote UE, when in RRC\_CONNECTED, relies on the network to receive concerned system information that has changed. + +## 6.2 Reception of MBS + +A UE receiving or interested to receive MBS broadcast services shall apply the MCCH information acquisition procedure as specified in TS 38.331 [3] to receive the MCCH information. A UE interested to receive MBS broadcast services identifies if a service that it is interested to receive is started or ongoing by receiving the MCCH information, and then receives a MTCH(s) configured using the Broadcast MRB establishment procedure as specified in TS 38.331 [3] and using the DL-SCH reception and MBS broadcast DRX procedure as specified in TS 38.321 [19]. + +A UE which has joined multicast session(s) and configured to receive MBS multicast services in RRC\_INACTIVE state shall apply the multicast MCCH information acquisition procedure as specified in TS 38.331 [3] to receive the multicast MCCH information when UE is in RRC\_INACTIVE state and the multicast MCCH is configured in the cell. The UE identifies whether a session is active or not by receiving the indication in *RRRelease*, multicast MCCH information, or group notification in paging message, and receives the multicast MTCH(s) in RRC\_INACTIVE state using the multicast MRB configuration procedure as specified in TS 38.331 [3] and using the DL-SCH reception and MBS multicast DRX procedure as specified in TS 38.321 [19]. + +UEs which have joined a multicast session(s) and are in RRC\_IDLE/RRC\_INACTIVE state shall apply the reception of the paging message procedure as specified in TS 38.331 [3] when the UE expects MBS group notification as specified in clause 16.10.5.2 in TS 38.300 [2]. + +# --- 7 Paging + +## 7.1 Discontinuous Reception for paging + +The UE may use Discontinuous Reception (DRX) in RRC\_IDLE and RRC\_INACTIVE state in order to reduce power consumption. The UE monitors one paging occasion (PO) per DRX cycle. A PO is a set of PDCCH monitoring occasions and can consist of multiple time slots (e.g. subframe or OFDM symbol) where paging DCI can be sent (TS 38.213 [4]). One Paging Frame (PF) is one Radio Frame and may contain one or multiple PO(s) or starting point of a PO. A L2 U2N Relay UE monitors the paging occasions of its PC5-RRC connected L2 U2N Remote UEs. In this case, the DRX cycle and UE ID mentioned in this clause refer to those of the L2 U2N Remote UE. + +In multi-beam operations, the UE assumes that the same paging message and the same Short Message are repeated in all transmitted beams and thus the selection of the beam(s) for the reception of the paging message and Short Message is up to UE implementation. The paging message is same for both RAN initiated paging and CN initiated paging. + +The UE initiates RRC Connection Resume procedure upon receiving RAN initiated paging. If the UE receives a CN initiated paging in RRC\_INACTIVE state, the UE moves to RRC\_IDLE and informs NAS. However, if a L2 U2N Relay UE in RRC\_INACTIVE state receives a CN initiated paging for a L2 U2N Remote UE, the L2 U2N Relay UE does not move to RRC\_IDLE state. + +NOTE 0a: The L2 U2N Remote UE does not need to monitor the PO in order to receive the paging message. + +NOTE 0b: While the SDT procedure is ongoing in RRC\_INACTIVE state, the UE monitors the PO in order to receive only the Short Message as specified in TS 38.331 [3]. + +The PF and PO for paging are determined by the following formulae: + +SFN for the PF is determined by: + +$$(SFN + PF\_offset) \bmod T = (T \bmod N) * (UE\_ID \bmod N)$$ + +Index ( $i\_s$ ), indicating the index of the PO is determined by: + +$$i\_s = \text{floor}(UE\_ID/N) \bmod N_s$$ + +The PDCCH monitoring occasions for paging are determined according to *pagingSearchSpace* as specified in TS 38.213 [4] and *firstPDCCH-MonitoringOccasionOfPO* and *nrofPDCCH-MonitoringOccasionPerSSB-InPO* if configured as specified in TS 38.331 [3]. When *SearchSpaceId* = 0 is configured for *pagingSearchSpace*, the PDCCH monitoring occasions for paging are same as for RMSI as defined in clause 13 in TS 38.213 [4]. + +When *SearchSpaceId* = 0 is configured for *pagingSearchSpace*, $N_s$ is either 1 or 2. For $N_s = 1$ , there is only one PO which starts from the first PDCCH monitoring occasion for paging in the PF. For $N_s = 2$ , PO is either in the first half frame ( $i\_s = 0$ ) or the second half frame ( $i\_s = 1$ ) of the PF. + +When *SearchSpaceId* other than 0 is configured for *pagingSearchSpace*, the UE monitors the $(i\_s + 1)^{\text{th}}$ PO. A PO is a set of 'S\*X' consecutive PDCCH monitoring occasions where 'S' is the number of actual transmitted SSBs determined according to *ssb-PositionsInBurst* in *SIB1* and X is the *nrofPDCCH-MonitoringOccasionPerSSB-InPO* if configured or is equal to 1 otherwise. The $[x*S+K]^{\text{th}}$ PDCCH monitoring occasion for paging in the PO corresponds to the $K^{\text{th}}$ transmitted SSB, where $x=0,1,\dots,X-1$ , $K=1,2,\dots,S$ . The PDCCH monitoring occasions for paging which do not overlap with UL symbols (determined according to *tdd-UL-DL-ConfigurationCommon*) are sequentially numbered from zero starting from the first PDCCH monitoring occasion for paging in the PF. When *firstPDCCH-MonitoringOccasionOfPO* is present, the starting PDCCH monitoring occasion number of $(i\_s + 1)^{\text{th}}$ PO is the $(i\_s + 1)^{\text{th}}$ value of the *firstPDCCH-MonitoringOccasionOfPO* parameter; otherwise, it is equal to $i\_s * S*X$ . If $X > 1$ , when the UE detects a PDCCH transmission addressed to P-RNTI within its PO, the UE is not required to monitor the subsequent PDCCH monitoring occasions for this PO. + +NOTE 1: A PO associated with a PF may start in the PF or after the PF. + +NOTE 2: The PDCCH monitoring occasions for a PO can span multiple radio frames. When *SearchSpaceId* other than 0 is configured for *pagingSearchSpace* the PDCCH monitoring occasions for a PO can span multiple periods of the paging search space. + +The following parameters are used for the calculation of PF and $i\_s$ above: + +T: DRX cycle of the UE. + +If the UE does not operate in eDRX as defined in clause 7.4: + +- T is determined by the shortest of the UE specific DRX value configured by RRC (if any), the UE specific DRX value configured by upper layers (if any), and a default DRX value broadcast in system information. For L2 U2N Relay UE, T for a L2 U2N Remote UE is determined by the shortest of the UE specific DRX value provided in PC5-RRC signalling and a default DRX value broadcast in system information. + +In RRC\_IDLE state, if the UE operates in eDRX and eDRX is configured by upper layers, i.e., $T_{\text{eDRX, CN}}$ , according to clause 7.4: + +- If $T_{\text{eDRX, CN}}$ is no longer than 1024 radio frames: + - $T = T_{\text{eDRX, CN}}$ ; +- else: + - During CN configured PTW, T is determined by the shortest of UE specific DRX value, if configured by upper layers, and the default DRX value broadcast in system information. + +In RRC\_INACTIVE state, if the UE operates in eDRX and eDRX is configured by RRC, i.e., $T_{\text{eDRX, RAN}}$ (if any), and upper layers, i.e., $T_{\text{eDRX, CN}}$ , as defined in clause 7.4: + +- If both $T_{eDRX, CN}$ and used $T_{eDRX, RAN}$ are no longer than 1024 radio frames, $T = \min\{T_{eDRX, RAN}, T_{eDRX, CN}\}$ . +- If $T_{eDRX, CN}$ is no longer than 1024 radio frames and no $T_{eDRX, RAN}$ is configured or used, $T$ is determined by the shortest of UE specific DRX value configured by RRC and $T_{eDRX, CN}$ . +- If $T_{eDRX, CN}$ is longer than 1024 radio frames: + - If $T_{eDRX, RAN}$ is not configured or used: + - During CN configured PTW, $T$ is determined by the shortest of the UE specific DRX value configured by RRC, the UE specific DRX value configured by upper layers (if any), and a default DRX value broadcast in system information. Outside the CN configured PTW, $T$ is determined by the UE specific DRX value configured by RRC; + - else if used $T_{eDRX, RAN}$ is no longer than 1024 radio frames: + - During CN configured PTW, $T$ is determined by the shortest of the UE specific DRX value, if configured by upper layers and $T_{eDRX, RAN}$ , and a default DRX value broadcast in system information. Outside the CN configured PTW, $T$ is determined by $T_{eDRX, RAN}$ ; + - else if used $T_{eDRX, RAN}$ is longer than 1024 radio frames: + - During the overlapped part of CN configured PTW and RAN configured PTW, $T$ is determined by the shortest of the UE specific DRX value configured by RRC, the UE specific DRX value configured by upper layers (if any), and a default DRX value broadcast in system information; + - During CN configured PTW and outside RAN configured PTW, $T$ is determined by the shortest of the UE specific DRX value configured by upper layers (if any), and a default DRX value broadcast in system information; + - Outside CN configured PTW and during RAN configured PTW, $T$ is determined by the UE specific DRX value configured by RRC. + +N: number of total paging frames in T + +Ns: number of paging occasions for a PF + +PF\_offset: offset used for PF determination + +UE\_ID: + +If the UE operates in eDRX as specified in clause 7.4: + +- 5G-S-TMSI mod 4096 + +else: + +- 5G-S-TMSI mod 1024 + +Parameters *Ns*, *nAndPagingFrameOffset*, *nrofPDCCH-MonitoringOccasionPerSSB-InPO*, and the length of default DRX Cycle are signaled in *SIB1*. The values of N and PF\_offset are derived from the parameter *nAndPagingFrameOffset* as defined in TS 38.331 [3]. The parameter *firstPDCCH-MonitoringOccasionOfPO* is signalled in *SIB1* for paging in the BWP configured by *initialDownlinkBWP*. For paging in a DL BWP other than the BWP configured by *initialDownlinkBWP*, the parameter *first-PDCCH-MonitoringOccasionOfPO* is signaled in the corresponding BWP configuration. + +If the UE has no 5G-S-TMSI, for instance when the UE has not yet registered onto the network, the UE shall use as default identity $UE\_ID = 0$ in the PF and $i\_s$ formulas above. + +5G-S-TMSI is a 48 bit long bit string as defined in TS 23.501 [10]. 5G-S-TMSI shall in the formulae above be interpreted as a binary number where the left most bit represents the most significant bit. + +In RRC\_INACTIVE state, if the UE supports *inactiveStatePO-Determination* and the network broadcasts *ranPagingInIdlePO* with value "true", the UE shall use the same $i\_s$ as for RRC\_IDLE state. Otherwise, the UE determines the $i\_s$ based on the parameters and formula above. + +In RRC\_INACTIVE state, if used eDRX value configured by upper layers is no longer than 1024 radio frames, the UE shall use the same *i\_s* as for RRC\_IDLE state. + +In RRC\_INACTIVE state, if used eDRX value configured by upper layers is longer than 1024 radio frames, during CN PTW, the UE shall use the same *i\_s* as for RRC\_IDLE state. Outside CN PTW, the UE shall use the *i\_s* for RRC\_INACTIVE state. + +## 7.2 Paging Early Indication + +### 7.2.1 Paging Early Indication reception + +The UE may use Paging Early Indication (PEI) in RRC\_IDLE and RRC\_INACTIVE states in order to reduce power consumption. If PEI configuration is provided in system information, the UE in RRC\_IDLE or RRC\_INACTIVE state supporting PEI (except for the UEs expecting MBS group notification) can monitor PEI using PEI parameters in system information according to the procedure described below. + +If *lastUsedCellOnly* is configured in system information of a cell, the UE monitors PEI in this cell only if the UE most recently received *RRCRelease* without *noLastCellUpdate* in this cell. Otherwise (i.e., if *lastUsedCellOnly* is not configured in system information of a cell), the UE monitors PEI in the camped cell. + +The UE monitors one PEI occasion per DRX cycle. A PEI occasion (PEI-O) is a set of PDCCH monitoring occasions (MOs) and can consist of multiple time slots (e.g. subframes or OFDM symbols) where PEI can be sent (TS 38.213 [4]). In multi-beam operations, the UE assumes that the same PEI is repeated in all transmitted beams and thus the selection of the beam(s) for the reception of the PEI is up to UE implementation. + +The time location of PEI-O for UE's PO is determined by a reference point and an offset: + +- The reference point is the start of a reference frame determined by a frame-level offset from the start of the first PF of the PF(s) associated with the PEI-O, provided by *pei-FrameOffset* in SIB1; +- The offset is a symbol-level offset from the reference point to the start of the first PDCCH MO of this PEI-O, provided by *firstPDCCH-MonitoringOccasionOfPEI-O* in SIB1. + +If one PEI-O is associated with POs of two PFs, the two PFs are consecutive PFs calculated by the parameters *PF\_offset*, *T*, *Ns*, and *N*. The first PF of the PFs associated with the PEI-O is provided by (SFN for PF) - floor(*ipo/Ns*)\**T/N*, where SFN for PF is determined in clause 7.1, *ipo* is defined in clause 10.4a in TS 38.213[4], *T*, *Ns*, and *N* are determined in clause 7.1. + +The PDCCH MOs for PEI are determined as specified in TS 38.213 [4] according to *pei-SearchSpace*, *pei-FrameOffset*, *firstPDCCH-MonitoringOccasionOfPEI-O* and *nrofPDCCH-MonitoringOccasionPerSSB-InPO* if configured as specified in TS 38.331 [3]. When *SearchSpaceId* = 0 is configured for *pei-SearchSpace*, the PDCCH MOs for PEI are same as for RMSI as defined in clause 13 in TS 38.213 [4]. UE determines first PDCCH MO for PEI-O based on *pei-FrameOffset* and *firstPDCCH-MonitoringOccasionOfPEI-O*, as for the case with *SearchSpaceId* > 0 configured. + +When *SearchSpaceId* = 0 is configured for *pei-SearchSpace*, the UE monitors the PEI-O according to *searchSpaceZero*. When *SearchSpaceId* other than 0 is configured for *pei-SearchSpace*, the UE monitors the PEI-O according to the search space with the configured *SearchSpaceId*. + +A PEI occasion is a set of 'S\*X' consecutive PDCCH MOs, where 'S' is the number of actual transmitted SSBs determined according to *ssb-PositionsInBurst* in SIB1, and X is the *nrofPDCCH-MonitoringOccasionPerSSB-InPO* if configured or is equal to 1 otherwise. The $[x*S+K]^{\text{th}}$ PDCCH MO for PEI in the PEI-O corresponds to the $K^{\text{th}}$ transmitted SSB, where $x=0,1,\dots,X-1$ , $K=1,2,\dots,S$ . The PDCCH MOs for PEI which do not overlap with UL symbols (determined according to *tdd-UL-DL-ConfigurationCommon*) are sequentially numbered from zero starting from the first PDCCH MO for PEI in the PEI-O. When the UE detects a PEI within its PEI-O, the UE is not required to monitor the subsequent MO(s) associated with the same PEI-O. + +If the UE detects PEI and the PEI indicates the subgroup the UE belongs to monitor its associated PO, as specified in clause 10.4a in TS 38.213 [4], the UE monitors the associated PO as specified in clause 7.1. If the UE does not detect PEI on the monitored PEI occasion or the PEI does not indicate the subgroup the UE belongs to monitor its associated PO, as specified in clause 10.4a in TS 38.213 [4], the UE is not required to monitor the associated PO as specified in clause 7.1. + +If the UE is unable to monitor the PEI occasion (i.e. all valid PDCCH MO for PEI) corresponding to its PO, e.g. during cell re-selection, the UE monitors the associated PO according to clause 7.1. + +In RRC\_INACTIVE state, when the UE uses the same *i\_s* as for RRC\_IDLE state as specified in clause 7.1, the UE shall use the same *ipo* as for RRC\_IDLE state. Otherwise, the UE determines the *ipo* based on the formula defined in clause 10.4a in TS 38.213 [4]. + +## 7.3 Subgrouping + +### 7.3.0 General + +If PEI and subgrouping are configured, UEs monitoring the same PO can be divided into one or more subgroups. With subgrouping, the UE monitors the associated PO if the corresponding bit for subgroup the UE belongs to is indicated as 1 by PEI corresponding to its PO, as specified in clause 10.4a in TS 38.213 [4]. + +The following parameters are used for the determination of subgroup ID: + +- *subgroupsNumPerPO*: total number of subgroups for both CN assigned subgrouping (if any) and UE\_ID based subgrouping (if any) in a PO, which is broadcasted in system information; +- *subgroupsNumForUEID*: number of subgroups for UE\_ID based subgrouping in a PO, which is broadcasted in system information. + +UE's subgroup can be either assigned by CN as specified in clause 7.3.1 or formed based on UE\_ID as specified in clause 7.3.2: + +- If *subgroupsNumForUEID* is absent in *subgroupConfig*, the subgroup ID based on CN assigned subgrouping as specified in clause 7.3.1, if available for the UE, is used in the cell. +- If both *subgroupsNumPerPO* and *subgroupsNumForUEID* are configured, and *subgroupsNumForUEID* has the same value as *subgroupsNumPerPO*, the subgroup ID based on UE\_ID based subgrouping as specified in clause 7.3.2 is used in the cell. +- If both *subgroupsNumPerPO* and *subgroupsNumForUEID* are configured, and *subgroupsNumForUEID* < *subgroupsNumPerPO*: + - The subgroup ID based on CN assigned subgrouping as specified in clause 7.3.1, if available for the UE, is used in the cell; + - Otherwise, the subgroup ID based on UE\_ID based subgrouping as specified in clause 7.3.2 is used in the cell. + +If a UE has no CN assigned subgroup ID or does not support CN assigned subgrouping, and there is no configuration for *subgroupsNumForUEID*, the UE monitors the associated PO according to clause 7.1. + +### 7.3.1 CN assigned subgrouping + +Paging with CN assigned subgrouping is used in the cell which supports CN assigned subgrouping, as described in clause 7.3.0. A UE supporting CN assigned subgrouping in RRC\_IDLE or RRC\_INACTIVE state can be assigned a subgroup ID (between 0 to 7) by AMF through NAS signalling. The UE belonging to the assigned subgroup ID monitors its associated PEI which indicates the paged subgroup(s) as specified in clause 7.2. + +### 7.3.2 UE\_ID based subgrouping + +Paging with UE\_ID based subgrouping is used in the cell which supports UE\_ID based subgrouping, as described in clause 7.3.0. + +If the UE is not configured with a CN assigned subgroup ID, or if the UE configured with a CN assigned subgroup ID is in a cell supporting only UE\_ID based subgrouping, the subgroup ID of the UE is determined by the formula below: + +$$\text{SubgroupID} = (\text{floor}(\text{UE\_ID}/(\text{N}*\text{Ns})) \bmod \text{subgroupsNumForUEID}) + (\text{subgroupsNumPerPO} - \text{subgroupsNumForUEID}),$$ + +where: + +N: number of total paging frames in T, which is the DRX cycle of RRC\_IDLE state as specified in clause 7.1 + +Ns: number of paging occasions for a PF + +UE\_ID: 5G-S-TMSI mod X, where X is 32768, if eDRX is applied; otherwise, X is 8192 + +subgroupsNumForUEID: number of subgroups for UE\_ID based subgrouping in a PO, which is broadcasted in system information + +In RRC\_INACTIVE state with CN configured PTW the SubgroupID used outside CN PTW is the same as the SubgroupID used inside CN PTW. + +The UE belonging to the SubgroupID monitors its associated PEI which indicates the paged subgroup(s) as specified in clause 7.2. + +## 7.4 Paging in extended DRX + +The UE may be configured by upper layers and/or RRC with an extended DRX (eDRX) cycle $T_{\text{eDRX, CN}}$ and/or $T_{\text{eDRX, RAN}}$ . + +For CN paging, the UE operates in eDRX in RRC\_IDLE or RRC\_INACTIVE states if the UE is configured for eDRX by upper layers and *eDRX-AllowedIdle* is signalled in SIB1; otherwise, the UE does not operate in eDRX. + +For RAN paging, the UE in RRC\_INACTIVE state: + +- if the UE is configured for eDRX by *ran-ExtendedPagingCycle-r18* and *eDRX-AllowedInactive-r18* is signalled in SIB1: + - operates in eDRX with an eDRX cycle $T_{\text{eDRX, RAN}}$ configured by *extendedPagingCycle-r18*; +- else if the UE is configured for eDRX by *ran-ExtendedPagingCycle-r17* and *eDRX-AllowedInactive-r17* is signalled in SIB1: + - operates in eDRX with an eDRX cycle $T_{\text{eDRX, RAN}}$ configured by *ran-ExtendedPagingCycle-r17*; +- else: + - does not operate in eDRX. + +If the UE operates in eDRX with an eDRX cycle no longer than 1024 radio frames, it monitors POs as defined in 7.1 with configured eDRX cycle. Otherwise, a UE operating in eDRX monitors POs as defined in 7.1 during a periodic Paging Time Window (PTW) configured for the UE. The PTW is UE-specific and is determined by a Paging Hyperframe (PH), a starting position within the PH (PTW\_start) and an ending position (PTW\_end). PH, PTW\_start and PTW\_end are given by the following formula: + +The PH for CN is the H-SFN satisfying the following equations: + +$\text{H-SFN mod } T_{\text{eDRX, CN}} = (\text{UE\_ID\_H mod } T_{\text{eDRX, CN}})$ , where + +- $T_{\text{eDRX, CN}}$ : UE-specific eDRX cycle in Hyper-frames, ( $T_{\text{eDRX, CN}} = 2, \dots, 1024$ Hyper-frames) configured by upper layers. + +The PH for RAN is the H-SFN satisfying the following equations: + +$\text{H-SFN mod } T_{\text{eDRX, RAN}} = (\text{UE\_ID\_H mod } T_{\text{eDRX, RAN}})$ , where + +- $T_{\text{eDRX, RAN}}$ : UE-specific eDRX cycle in Hyper-frames, ( $T_{\text{eDRX, RAN}} = 2, \dots, 1024$ Hyper-frames) configured by RRC. + +For CN configured PTW: + +PTW\_start denotes the first radio frame of the PH for CN that is part of the PTW and has SFN satisfying the following equation: + +$SFN = 128 * i_{eDRX\_CN}$ , where + +- $i_{eDRX\_CN} = \text{floor}(UE\_ID\_H / T_{eDRX\_CN}) \bmod 8$ + +PTW\_end is the last radio frame of the PTW and has SFN satisfying the following equation: + +$SFN = (PTW\_start + L * 100 - 1) \bmod 1024$ , where + +- L = Paging Time Window (PTW) length (in seconds) configured by upper layers + +For RAN configured PTW: + +PTW\_start denotes the first radio frame of the PH for RAN that is part of the PTW and has SFN satisfying the following equation: + +$SFN = 128 * i_{eDRX\_CN}$ , where + +- $i_{eDRX\_CN} = \text{floor}(UE\_ID\_H / T_{eDRX\_CN}) \bmod 8$ + +PTW\_end is the last radio frame of the PTW and has SFN satisfying the following equation: + +$SFN = (PTW\_start + L * 100 - 1) \bmod 1024$ , where + +- L = Paging Time Window (PTW) length (in seconds) configured by RRC + +UE\_ID\_H is defined as follows: + +UE\_ID\_H: 13 most significant bits of the Hashed ID. + +Hashed ID is defined as follows: + +Hashed\_ID is Frame Check Sequence (FCS) for the bits b31, b30..., b0 of 5G-S-TMSI. + +5G-S-TMSI = as defined in TS 23.003 [23]. + +The 32-bit FCS shall be the ones complement of the sum (modulo 2) of Y1 and Y2, where + +- Y1 is the remainder of $x^k$ ( $x^{31} + x^{30} + x^{29} + x^{28} + x^{27} + x^{26} + x^{25} + x^{24} + x^{23} + x^{22} + x^{21} + x^{20} + x^{19} + x^{18} + x^{17} + x^{16} + x^{15} + x^{14} + x^{13} + x^{12} + x^{11} + x^{10} + x^9 + x^8 + x^7 + x^6 + x^5 + x^4 + x^3 + x^2 + x^1 + 1$ ) divided (modulo 2) by the generator polynomial $x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11} + x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1$ , where k is 32; and +- Y2 is the remainder of Y3 divided (modulo 2) by the generator polynomial $x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11} + x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1$ , where Y3 is the product of $x^{32}$ by "b31, b30..., b0 of S-TMSI or 5G-S-TMSI", i.e., Y3 is the generator polynomial $x^{32}$ ( $b31 * x^{31} + b30 * x^{30} + \dots + b0 * 1$ ). + +NOTE: The Y1 is 0xC704DD7B for any 5G-S-TMSI value. An example of hashed ID calculation is in Annex A. + +# 8 Sidelink Operation + +## 8.1 NR sidelink communication, and V2X sidelink communication, NR sidelink discovery, and ranging/ sidelink positioning + +The UE may transmit or receive NR sidelink communication/discovery if it fulfils the condition(s) defined in TS 38.331 [3], clause 5.8.2. When UE is in-coverage for sidelink operation as defined in clause 8.2, the UE may perform NR sidelink communication/discovery according to *SIB12*, and when out-of-coverage for sidelink, the UE may perform NR sidelink communication/discovery according to *SL-PreconfigurationNR* or according to *SIB12* of the cell on the frequency which provides inter-carrier NR sidelink configuration, or according to *SIB12* received from the connected L2 U2N Relay UE as specified in TS 38.331 [3]. The UE shall not perform NR sidelink communication/discovery according to *SL-PreconfigurationNR* if the UE detects a cell providing NR sidelink configuration or inter-carrier NR + +sidelink configuration for the frequency UE is interested to perform NR sidelink communication/discovery on, or if the UE is a L2 U2N Remote UE and has received *SIB12* from the connected L2 U2N Relay UE. + +The UE may transmit or receive V2X sidelink communication if it fulfills the condition(s) defined in TS 36.331[6], clause 5.10.1d. When UE is in-coverage for sidelink operation as defined in clause 8.2, the UE may perform V2X sidelink communication according to *SIB13/ SIB14* of the cell on an NR frequency. + +The UE may transmit or receive SL-PRS for ranging/sidelink positioning if it fulfils the conditions defined in TS 38.331 [3]. + +The U2N Remote UE, the U2N Relay UE, the U2U Remote UE, or the U2U Relay UE may transmit NR sidelink relay discovery (i.e., as specified in TS 23.304 [22]) if it fulfills the condition(s) defined in TS 38.331 [3]. + +For NR sidelink broadcast and groupcast, the UE may obtain SL DRX configuration from *SIB12* (for in-coverage UE, as defined in clause 8.2, in RRC\_IDLE and RRC\_INACTIVE state; or for out-of-coverage, UE as defined in clause 8.2, on the frequency which the UE is configured to perform NR sidelink communication/discovery and which is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12*) or *SL-PreconfigurationNR* (for non L2 U2N Remote UE out-of-coverage, as defined in clause 8.2, on the frequency which the UE is configured to perform NR sidelink communication/discovery and which is not included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12*). + +For inter-UE coordination (IUC) information configuration, the UE may obtain it from *SIB12* (for in-coverage UE, as defined in clause 8.2, in RRC\_IDLE and RRC\_INACTIVE state; or for non L2 U2N Remote UE out-of-coverage, as defined in clause 8.2, on the frequency which UE is configured to perform NR sidelink communication and which is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12*) or *SL-PreconfigurationNR* (for non L2 U2N Remote UE out-of-coverage, as defined in clause 8.2, on the frequency which UE is configured to perform NR sidelink communication and which is not included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12*). + +For ranging/sidelink positioning, the UE may obtain the configuration from *SIB23* (for in-coverage UE, as defined in clause 8.2, in RRC\_IDLE and RRC\_INACTIVE state) or *SL-PreconfigurationNR* (for out-of-coverage UE, as defined in clause 8.2). + +## 8.2 Cell selection and reselection for Sidelink + +The requirements defined in this clause for sidelink operation (including sidelink relay operations) apply for UEs in RRC\_IDLE, RRC\_INACTIVE and in RRC\_CONNECTED. + +When UE is interested to perform NR sidelink communication/discovery and ranging/sidelink positioning on non-serving frequency, it may perform measurements on that frequency or the frequencies which can provide inter carrier NR sidelink configuration for that frequency for cell selection and reselection purpose in accordance with TS 38.133[8]. When UE is interested to perform V2X sidelink communication on non-serving frequency, it may perform measurements on that frequency or the frequencies which can provide inter carrier V2X sidelink configuration for that frequency for cell selection and intra-frequency reselection purpose in accordance with TS 38.133[8]. + +If the UE detects at least one cell on the frequency which UE is configured to perform NR sidelink communication/discovery and ranging/sidelink positioning on fulfilling the S criterion in accordance with clause 8.2.1, it shall consider itself to be in-coverage for NR sidelink communication/discovery and ranging/sidelink positioning on that frequency. If the UE cannot detect any cell on that frequency meeting the S criterion, it shall consider itself to be out-of-coverage for NR sidelink communication/discovery and ranging/sidelink positioning on that frequency. + +If the UE detects at least one cell on the frequency which UE is configured to perform V2X sidelink communication on fulfilling the S criterion in accordance with clause 8.2.1, it shall consider itself to be in-coverage for V2X sidelink communication on that frequency. If the UE cannot detect any cell on that frequency meeting the S criterion, it shall consider itself to be out-of-coverage for V2X sidelink communication on that frequency. + +If the UE has selected a cell on a non-serving frequency for V2X sidelink communication, it shall perform additional intra-frequency reselection process to select a better cell for sidelink operation on that frequency in accordance with clause 8.2.1. + +If the UE has selected a cell on a non-serving frequency for NR sidelink communication/discovery, it shall perform additional reselection process to select a better cell for sidelink operation in accordance with clause 8.2.1. + +### 8.2.1 Parameters used for cell selection and reselection triggered for sidelink + +When evaluating S criterion, R criterion (ranking) or inter-frequency cell reselection criterion, as defined in clause 5.2.3.2, clause 5.2.4.6 and clause 5.2.4.5 respectively, for cell selection/reselection triggered for NR sidelink communication/discovery or V2X sidelink communication on a non-serving frequency, UE shall perform the evaluation as follows: + +- The UE shall use cell selection/reselection parameters broadcast by the concerned cell (i.e. selected cell for the sidelink operation) for the evaluation. + +# --- 9 Tracking Reference Signal + +The UE in RRC\_IDLE and RRC\_INACTIVE states may use Tracking Reference Signal (TRS) whose configurations are provided in system information for its paging reception to save power. In a cell in which TRS are available for the UE in RRC\_IDLE and RRC\_INACTIVE states to use, the availability of the configured TRS is informed to the UEs in RRC\_IDLE and RRC\_INACTIVE states based on explicit L1 based availability indication defined in TS 38.213 [4]. + +# --- Annex A (informative): Example of Hashed ID Calculation using 32-bit FCS + +## **Inputs:** + +- Least significant bits of 5G-S-TMSI: 0x12341234 +- Generator polynomial: 0x104C11DB7 (1 0000 0100 1100 0001 0001 1101 1011 0111) + +### **Procedure to Calculate Hashed ID:** + +#### step a) + +- k = 32 +- numerator: 0xFFFF FFFF 0000 0000 +- denominator: 0x1 04C1 1DB7 +- remainder Y1 = 0xC704DD7B + +#### step b) + +- numerator: 0x1234 1234 0000 0000 +- denominator: 0x1 04C1 1DB7 +- remainder Y2 = 0x1D66F1A6 + +**Hashed\_ID** = FCS = ones complement of (remainder Y1 XOR remainder Y2) + += ones complement of (0xC704DD7B XOR 0x1D66F1A6) + += negation of (0xDA622CDD) + += **0x259DD322** + +# --- Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|------|-----|-----|-------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 3/2017 | | | | | | Initial skeleton | 0.0.1 | +| 5/2017 | | | | | | Updated initial skeleton | 0.0.2 | +| 6/2017 | | | | | | Updated based on RAN2#98 agreements | 0.0.3 | +| 8/2017 | | | | | | Updated based on feedback from companies | 0.0.4 | +| 10/2017 | | | | | | No changes | 0.0.5 | +| 11/2017 | | | | | | No changes | 0.0.6 | +| 01/2018 | | | | | | No changes | 0.0.7 | +| 01/2018 | | | | | | No changes | 0.1.0 | +| 02/2018 | | | | | | Updated based on RAN-NR-AH1801 agreements | 0.1.1 | +| 02/2018 | | | | | | No changes | 0.1.2 | +| 03/2018 | | | | | | Updated based on RAN#101 agreements | 0.2.0 | +| 03/2018 | RAN#79 | RP-180451 | | | | Typo corrections; submitted to RAN#79 for information | 1.0.0 | +| 04/2018 | RAN2#101bis | R2-1805086 | | | | No changes | 1.0.1 | +| 05/2018 | RAN2#102 | R2-1806884 | | | | Updated based on RAN2#101bis agreements | 1.1.0 | +| 06/2018 | | R2-1809262 | | | | Updated based on RAN2#102 agreements | 1.2.0 | +| 06/2018 | RP#80 | RP-180694 | | | | Submitted to RAN#80 for approval | 2.0.0 | +| 06/2018 | | | | | | Upgraded to Rel-15 after the plenary approval | 15.0.0 | +| 09/2018 | RP-81 | RP-181941 | 0024 | 2 | F | Miscellaneous Corrections based on endorsed CRs in RAN2#103 | 15.1.0 | +| 12/2018 | RP-82 | R2-1818509 | 0047 | 4 | F | Clarification of Paging Monitoring Occasion | 15.2.0 | +| | RP-82 | R2-1816301 | 0049 | 2 | F | Correction to description of PO for default association | 15.2.0 | +| | RP-82 | R2-1819196 | 0051 | 3 | F | Corrections on 38.304 | 15.2.0 | +| | RP-82 | R2-1816678 | 0055 | 2 | F | CR on PDCCH monitoring occasions for paging | 15.2.0 | +| | RP-82 | R2-1817200 | 0056 | 2 | F | Release and Redirect in 2-step procedure | 15.2.0 | +| | RP-82 | R2-1818681 | 0062 | 4 | F | Clarification on final suitability check | 15.2.0 | +| | RP-82 | R2-1817261 | 0063 | 2 | D | Correction to Ambiguous Terminologies with respect to Cell Ranking | 15.2.0 | +| | RP-82 | R2-1818125 | 0066 | 2 | F | Correction on definition of PEMAX1, PEMAX2 | 15.2.0 | +| | RP-82 | R2-1817662 | 0067 | 2 | F | Clarification of mobility state detection criteria | 15.2.0 | +| | RP-82 | R2-1818549 | 0074 | 2 | F | CR on UE behaviour upon lack of TAC in SIB1 | 15.2.0 | +| | RP-82 | R2-1818508 | 0075 | 1 | F | Miscellaneous Corrections in Paging | 15.2.0 | +| | RP-82 | R2-1819037 | 0076 | 1 | F | Clarification for the UE behaviour in camped normally and camped on any cell states | 15.2.0 | +| | RP-82 | R2-1818883 | 0079 | 2 | F | Corrections on storing and discarding UE AS context | 15.2.0 | +| | RP-82 | R2-1818998 | 0084 | 2 | F | Correction to UE behavior for barred cell | 15.2.0 | +| | RP-82 | R2-1817141 | 0087 | - | F | Clarification on cell reselection conditions during TreselectionRAT | 15.2.0 | +| | RP-82 | R2-1818881 | 0088 | 2 | F | Introduction of MICO mode | 15.2.0 | +| | RP-82 | R2-1817145 | 0089 | - | F | Correction to monitoring paging in Camped on Any Cell state | 15.2.0 | +| | RP-82 | R2-1818878 | 0090 | 1 | F | Minor clarifications for paging | 15.2.0 | +| | RP-82 | R2-1818688 | 0096 | 1 | F | Correction to cell access barring alleviation in cell reselection | 15.2.0 | +| | RP-82 | R2-1818683 | 0097 | 1 | F | CR on 38.304 corrections | 15.2.0 | +| | RP-82 | R2-1817738 | 0099 | - | F | 38.304 CR on derivation of N for paging | 15.2.0 | +| | RP-82 | R2-1819026 | 0102 | 1 | F | Correction of PLMN selection in RRC_INACTIVE | 15.2.0 | +| 03/2019 | RP-83 | RP-190540 | 0081 | 4 | F | CR on UE behavior if emergency call is not supported in the current cell | 15.3.0 | +| | RP-83 | RP-190540 | 0103 | 2 | F | Correction to number of radio frames spanned by PDCCH monitoring occasions of a PO | 15.3.0 | +| | RP-83 | RP-190540 | 0104 | 1 | F | Correction to signaling aspects of parameter first-PDCCH-MonitoringOccasionOfPO | 15.3.0 | +| | RP-83 | RP-190540 | 0111 | - | F | Clarification for paging and UL symbols | 15.3.0 | +| | RP-83 | RP-190544 | 0113 | 3 | F | Miscellaneous Corrections | 15.3.0 | +| | RP-83 | RP-190544 | 0117 | 1 | F | Correction on exception to cell categories for regional provision of service | 15.3.0 | +| 06/2019 | RP-84 | RP-191373 | 0120 | - | F | UE behavior on cell reselection if rangeToBestCell is configured Option 2 | 15.4.0 | +| | RP-84 | RP-191373 | 0121 | - | F | Miscellaneous Corrections | 15.4.0 | +| | RP-84 | RP-191374 | 0125 | - | F | CR on inter-RAT cell reselection | 15.4.0 | +| | RP-84 | RP-191376 | 0126 | 1 | F | UE behaviour on the cell without TAC | 15.4.0 | +| | RP-84 | RP-191376 | 0128 | 1 | F | Correction for Access Identity 0 when PLMN is reserved for operator use | 15.4.0 | +| | RP-84 | RP-191376 | 0132 | 1 | F | Monitoring of short messages with multi-beams | 15.4.0 | +| 09/2019 | RP-85 | RP-192193 | 0136 | 2 | F | Miscellaneous Corrections | 15.5.0 | +| 12/2019 | RP-86 | RP-192936 | 0139 | 2 | F | Miscellaneous Corrections | 15.6.0 | +| | RP-86 | RP-192938 | 0143 | 1 | F | Correction to Pcompensation for FR2 | 15.6.0 | +| 03/2020 | RP-87 | RP-200344 | 0145 | 4 | B | Introduction of UE Power Saving in NR | 16.0.0 | +| | RP-87 | RP-200353 | 0148 | 2 | B | Introduction of PRN for TS 38.304 | 16.0.0 | +| | RP-87 | RP-200341 | 0149 | 2 | B | Introduction of NR operation with Shared Spectrum Access in Idle/Inactive mode | 16.0.0 | +| | RP-87 | RP-200349 | 0150 | 3 | B | Correction of TS 38.304 to introduce IAB | 16.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-87 | RP-200346 | 0151 | 1 | B | CR on cell selection/ reselection for NR V2X UE | 16.0.0 | +| 07/2020 | RP-88 | RP-201179 | 0153 | 4 | F | Miscellaneous correction to 38.304 for IAB | 16.1.0 | +| | RP-88 | RP-201165 | 0155 | 4 | A | Corrections to cell barred handling | 16.1.0 | +| | RP-88 | RP-201182 | 0156 | 3 | F | Correction to 38.304 for PRN | 16.1.0 | +| | RP-88 | RP-201179 | 0157 | 4 | B | Corrections to 38.304 for supporting IAB in NPN | 16.1.0 | +| | RP-88 | RP-201174 | 0158 | 1 | B | CR for UE Power Saving in NR | 16.1.0 | +| | RP-88 | RP-201190 | 0173 | - | C | Introduction of eCall over IMS for NR | 16.1.0 | +| | RP-88 | RP-201176 | 0174 | 2 | F | CR on cell (re)selection for sidelink in TS 38.304 | 16.1.0 | +| 09/2020 | RP-89 | RP-201927 | 0175 | 1 | F | Correction to TS 38.304 | 16.2.0 | +| | RP-89 | RP-201932 | 0184 | 1 | D | Miscellaneous corrections (Rapporteur) | 16.2.0 | +| | RP-89 | RP-201923 | 0185 | - | F | Miscellaneous corrections for TS 38.304 for IAB | 16.2.0 | +| | RP-89 | RP-201929 | 0186 | 1 | F | CR for UE Power Saving in NR | 16.2.0 | +| | RP-89 | RP-201928 | 0187 | - | F | Idle mode corrections for NPN | 16.2.0 | +| 12/2020 | RP-90 | RP-202776 | 0193 | 1 | F | Correction on RRM relaxation | 16.3.0 | +| | RP-90 | RP-202771 | 0195 | - | F | Miscellaneous Corrections | 16.3.0 | +| | RP-90 | RP-202769 | 0196 | - | F | Correction on inter-frequency operation | 16.3.0 | +| 03/2021 | RP-91 | RP-210689 | 0203 | - | F | Correction to 38.304 on intra-frequency reselection | 16.4.0 | +| 06/2021 | RP-92 | RP-211471 | 0206 | 1 | F | CR on the missing definition of "Available SNPN" in TS 38.304 | 16.5.0 | +| | RP-92 | RP-211475 | 0211 | 2 | F | Correction of IFRI-related conditions | 16.5.0 | +| 09/2021 | RP-93 | RP-212442 | 0215 | 1 | F | Clarification of access restrictions during cell re-selection | 16.6.0 | +| | RP-93 | RP-212439 | 0217 | 1 | A | Clarification of barring when TAC is missing in RAN sharing | 16.6.0 | +| | RP-93 | RP-212438 | 0220 | - | A | Correction to cell selection and reselection due to SIB1 acquisition failure | 16.6.0 | +| 12/2021 | RP-94 | RP-213343 | 0222 | - | F | Correction for TS 38.304 on power class for cell selection of IAB | 16.7.0 | +| 03/2022 | RP-95 | RP-220506 | 0204 | 2 | D | Inclusive Language Review for TS 38.304 | 17.0.0 | +| | RP-95 | RP-220484 | 0221 | 7 | B | Introduction of NR MBS into 38.304 | 17.0.0 | +| | RP-95 | RP-220837 | 0223 | 1 | B | Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN] | 17.0.0 | +| | RP-95 | RP-220837 | 0226 | 1 | B | Introduction of MINT [MINT] | 17.0.0 | +| | RP-95 | RP-220483 | 0227 | 1 | B | Introduction of ePowSav in TS 38.304 | 17.0.0 | +| | RP-95 | RP-220472 | 0228 | 1 | F | Correction on PO determination for UE in inactive state | 17.0.0 | +| | RP-95 | RP-220493 | 0230 | 1 | B | Introduction of Enhancements for Private Networks | 17.0.0 | +| | RP-95 | RP-220491 | 0232 | 1 | B | 38.304 CR for SL Relay | 17.0.0 | +| | RP-95 | RP-220482 | 0233 | 2 | B | Introduction of NTN | 17.0.0 | +| | RP-95 | RP-220480 | 0234 | 1 | B | Introduction of RedCap | 17.0.0 | +| | RP-95 | RP-220490 | 0235 | 1 | B | Introduction of slice-based cell re-selection | 17.0.0 | +| | RP-95 | RP-220476 | 0236 | - | B | Introduction of NR Sidelink enhancements | 17.0.0 | +| 06/2022 | RP-96 | RP-221727 | 0238 | 1 | F | Corrections on TS 38.304 for ePowSav | 17.1.0 | +| | RP-96 | RP-221719 | 0246 | 4 | C | 38.304 CR Corrections on slice-based cell reselection | 17.1.0 | +| | RP-96 | RP-221727 | 0248 | 1 | A | Addressing inconsistency for RRM measurement rules | 17.1.0 | +| | RP-96 | RP-221736 | 0249 | 1 | D | Miscellaneous Editorial Corrections | 17.1.0 | +| | RP-96 | RP-221729 | 0251 | 2 | F | Alignment of DRX for Paging with RRC for SDT | 17.1.0 | +| | RP-96 | RP-221716 | 0252 | 2 | F | Miscellaneous corrections for RedCap WI | 17.1.0 | +| | RP-96 | RP-221717 | 0254 | - | F | NTN corrections to 38.304 | 17.1.0 | +| | RP-96 | RP-221732 | 0255 | - | F | Miscellaneous correction on SL relay | 17.1.0 | +| 09/2022 | RP-97 | RP-222523 | 0256 | 2 | F | 38.304 Corrections for MBS | 17.2.0 | +| | RP-97 | RP-222525 | 0267 | 1 | F | Miscellaneous CR on TS 38.304 for ePowSav | 17.2.0 | +| | RP-97 | RP-222525 | 0276 | 1 | F | Miscellaneous corrections for RedCap WI | 17.2.0 | +| | RP-97 | RP-222524 | 0277 | 1 | F | Miscellaneous corrections on 38.304 | 17.2.0 | +| | RP-97 | RP-222525 | 0280 | 2 | F | Cell reselection corrections to RAN slicing | 17.2.0 | +| 12/2022 | RP-98 | RP-223412 | 0288 | 3 | F | Corrections on 38.304 for SL relay | 17.3.0 | +| | RP-98 | RP-223411 | 0296 | 2 | F | Corrections to TS 38.304 for NR NTN | 17.3.0 | +| | RP-98 | RP-223410 | 0297 | 1 | F | MBS corrections for 38.304 | 17.3.0 | +| | RP-98 | RP-223413 | 0298 | 1 | D | Miscellaneous CR on TS 38.304 for ePowSav | 17.3.0 | +| | RP-98 | RP-223411 | 0301 | 1 | F | Correction on iP0 determination for UE operates with eDRX | 17.3.0 | +| | RP-98 | RP-223412 | 0302 | 1 | F | Clarification on NSAG information in slice-based cell reselection | 17.3.0 | +| | RP-98 | RP-223406 | 0310 | 1 | F | Clarification on cell reselection priority handling for HSDN, MBS, V2X/NR sidelink, Slicing and deprioritization request | 17.3.0 | +| | RP-98 | RP-223411 | 0313 | 1 | F | Miscellaneous corrections for RedCap WI | 17.3.0 | +| 03/2023 | RP-99 | RP-230690 | 0318 | 2 | F | CR to 38.304 on relaxed measurements | 17.4.0 | +| | RP-99 | RP-230691 | 0323 | 1 | F | Correction on eDRX | 17.4.0 | +| | RP-99 | RP-230692 | 0324 | 2 | F | Correction to slice-support cell lists | 17.4.0 | +| 06/2023 | RP-100 | RP-231415 | 0330 | 1 | F | Addition of slice-based cell re-selection parameters | 17.5.0 | +| | RP-100 | RP-231416 | 0333 | 3 | F | Clarification on sidelink communication resource configuration used by OoC L2 Remote UE | 17.5.0 | +| | RP-100 | RP-231417 | 0334 | 2 | F | Corrections for eDRX in RRC_INACTIVE | 17.5.0 | +| | RP-100 | RP-231410 | 0341 | - | A | Correction on TS 38.304 for NR SL | 17.5.0 | +| | RP-100 | RP-231411 | 0343 | 2 | A | Clarification on Access Identities Validity | 17.5.0 | +| | RP-100 | RP-231416 | 0346 | - | F | Corrections on TS 38.304 for SL enhancements | 17.5.0 | +| | RP-100 | RP-231415 | 0348 | - | F | Clarifications on the use of SIB16 | 17.5.0 | +| 09/2023 | RP-101 | RP-232570 | 0351 | 2 | F | NSAG validity when TAI list is omitted | 17.6.0 | +| 12/2023 | RP-102 | RP-233888 | 0353 | 3 | F | Correction on SIB/Preconfiguration applicability | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------|--------| +| | RP-102 | RP-233888 | 0363 | 1 | F | Clarification for the use of term and/or within the context of (e)DRX operation | 17.7.0 | +| 12/2023 | RP-102 | RP-233898 | 0345 | 3 | B | Introduction of NCR in TS 38.304 | 18.0.0 | +| | RP-102 | RP-233907 | 0355 | 1 | B | Introduction of eMBS | 18.0.0 | +| | RP-102 | RP-233912 | 0356 | - | B | Introduction of R18 eNPN for TS 38.304 | 18.0.0 | +| | RP-102 | RP-233906 | 0357 | 2 | B | Introduction of NR NTN enhancements in 38.304 | 18.0.0 | +| | RP-102 | RP-233901 | 0358 | 1 | B | Introduction of R18 positioning to RRC_IDLE mode and RRC inactive state | 18.0.0 | +| | RP-102 | RP-233897 | 0359 | 1 | B | Introduction of Release-18 SL Evolution in TS 38.304 | 18.0.0 | +| | RP-102 | RP-233899 | 0364 | 2 | B | Introduction of eRedCap in TS 38.304 | 18.0.0 | +| | RP-102 | RP-233904 | 0365 | 1 | B | Introduction of Rel-18 support for SL Relay Enhancements | 18.0.0 | +| | RP-102 | RP-233900 | 0369 | 1 | B | Introduction of Network Energy Savings for NR | 18.0.0 | +| | RP-102 | RP-233933 | 0370 | - | B | Introduction of mobile IAB for NR | 18.0.0 | +| | RP-102 | RP-233916 | 0371 | - | B | Introduction of NR ATG in TS 38.304 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38305/034b9d22fdb2e7e61ff3b15f229569bf_img.jpg b/marked/Rel-18/38_series/38305/034b9d22fdb2e7e61ff3b15f229569bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d52fe2b69459d1c4501d12e513766706dadc5e29 --- /dev/null +++ b/marked/Rel-18/38_series/38305/034b9d22fdb2e7e61ff3b15f229569bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85453b2c1da5fe77459601c871e66540b39d4370184fb62a64e7243442a7829e +size 9565 diff --git a/marked/Rel-18/38_series/38305/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-18/38_series/38305/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d0157d7e97de67bdc24596a0721154c35cf33dd --- /dev/null +++ b/marked/Rel-18/38_series/38305/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ebe4bebe0e8292b38f2df05fcaa904b53491a65b75f0e52843fb000e8bf86b9 +size 17704 diff --git a/marked/Rel-18/38_series/38305/0850300da6b28250eb47881da35cabad_img.jpg b/marked/Rel-18/38_series/38305/0850300da6b28250eb47881da35cabad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..742567d4305f85bacd6ce62017c932320a7fbd58 --- /dev/null +++ b/marked/Rel-18/38_series/38305/0850300da6b28250eb47881da35cabad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02fe76f157c830fe61f65b39cb1d9e22362f259de262d4f81fa4b72a24deb121 +size 13268 diff --git a/marked/Rel-18/38_series/38305/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Rel-18/38_series/38305/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d57f74e5879c5ee145d7954895cffa6fffdd95bc --- /dev/null +++ b/marked/Rel-18/38_series/38305/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76e73f8bbad13e2a1e3c788392cd2e8091e90f708cccc9cf12941c5c488e6bd5 +size 19360 diff --git a/marked/Rel-18/38_series/38305/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg b/marked/Rel-18/38_series/38305/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35e31f1ecf0cc70fe3121d67b36a244cdc5c1c8c --- /dev/null +++ b/marked/Rel-18/38_series/38305/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04415178eced8b578b3de2b8cb2515766a426c0100a65621cf750ef2883d69bc +size 19853 diff --git a/marked/Rel-18/38_series/38305/10bf8762a8e8d9385609cc6fb11061fe_img.jpg b/marked/Rel-18/38_series/38305/10bf8762a8e8d9385609cc6fb11061fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f91a473e82dc8fe8b64a7a41d8de5647640cfbb --- /dev/null +++ b/marked/Rel-18/38_series/38305/10bf8762a8e8d9385609cc6fb11061fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92682585b71b427b9edd198b39b0002042894080763f96c65fb716cf1cecd579 +size 21487 diff --git a/marked/Rel-18/38_series/38305/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-18/38_series/38305/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0793425c4f207695bfb9e43e95b073619847774a --- /dev/null +++ b/marked/Rel-18/38_series/38305/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1252669a188313211e8128ab5f51368c7248147beb1869ea6298e81497a33ab4 +size 16843 diff --git a/marked/Rel-18/38_series/38305/131048f570c4d9960a21e7dd73c4fd6b_img.jpg b/marked/Rel-18/38_series/38305/131048f570c4d9960a21e7dd73c4fd6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1a7b2402a97de94aed656f0de31bc97ff50aff0 --- /dev/null +++ b/marked/Rel-18/38_series/38305/131048f570c4d9960a21e7dd73c4fd6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc762e5ea77e63355ba785083827ca8c6ff95509e4a538b75e8d33fbaf137656 +size 24570 diff --git a/marked/Rel-18/38_series/38305/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-18/38_series/38305/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ead232891324f1fe48f86691f064fd3a681960d4 --- /dev/null +++ b/marked/Rel-18/38_series/38305/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8baf455c3ce656ee627e51c9351556f9f278624767a05f048f281d15aa654a6d +size 70874 diff --git a/marked/Rel-18/38_series/38305/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/marked/Rel-18/38_series/38305/1bc1746388cb64bf23b356ce2365dfc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37e4d30d5f3925afca370e119f2766584e934e09 --- /dev/null +++ b/marked/Rel-18/38_series/38305/1bc1746388cb64bf23b356ce2365dfc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0d1b655fc5a1347e6a31781292fb22f413fc004cc6b1cf6a13c4a987317e7b5 +size 9371 diff --git a/marked/Rel-18/38_series/38305/2bea721b89ee5816651ed9cdc328bc9f_img.jpg b/marked/Rel-18/38_series/38305/2bea721b89ee5816651ed9cdc328bc9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86c40638dbaf4057d71322804302f5fd67ecbcd7 --- /dev/null +++ b/marked/Rel-18/38_series/38305/2bea721b89ee5816651ed9cdc328bc9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a3b902fa566ebf17712ebe3c1849aae39a0f04add1457556d0e3f022a41a720 +size 8925 diff --git a/marked/Rel-18/38_series/38305/2fe54eab8d7668ad3b9e56219accbaca_img.jpg b/marked/Rel-18/38_series/38305/2fe54eab8d7668ad3b9e56219accbaca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c40737bff3b94cfb57ef201b6e102bbc34378f2b --- /dev/null +++ b/marked/Rel-18/38_series/38305/2fe54eab8d7668ad3b9e56219accbaca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c021967bcb8b19fbb11c520a870178075cf73faa9919441fb4312896eb989f9 +size 12064 diff --git a/marked/Rel-18/38_series/38305/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/marked/Rel-18/38_series/38305/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4f2f9e295487b888ce3126234367a5b3343d083 --- /dev/null +++ b/marked/Rel-18/38_series/38305/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a47209c8519ccf9092a70346c531074ac90424b9b5e6a9837663c05f82ed1b0f +size 16917 diff --git a/marked/Rel-18/38_series/38305/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-18/38_series/38305/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0e8d50e548e0edfb01500e1805281ba23e7ec28 --- /dev/null +++ b/marked/Rel-18/38_series/38305/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b94217c84849af9f6e5874974f56041e89272e4bc24033a2b210e6659c099e +size 25609 diff --git a/marked/Rel-18/38_series/38305/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-18/38_series/38305/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5d699ff157689e5c6ed0bbd874e7ecd933930ed --- /dev/null +++ b/marked/Rel-18/38_series/38305/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:181a7fc57f3f187649b8280699ab249a0215b44e1963efa97ab39975125bccaf +size 28663 diff --git a/marked/Rel-18/38_series/38305/3489a3f420d1f2d8b7d626d3a6851388_img.jpg b/marked/Rel-18/38_series/38305/3489a3f420d1f2d8b7d626d3a6851388_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebbeb300c6a3c46c95c97e4927caadce10576083 --- /dev/null +++ b/marked/Rel-18/38_series/38305/3489a3f420d1f2d8b7d626d3a6851388_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81f7bee03bfe6dd8e030692b255828e98319072b041263910257e904a90d33c3 +size 1394 diff --git a/marked/Rel-18/38_series/38305/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/Rel-18/38_series/38305/3493d7ba4c86f944e159de1bf45ff03d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfba6d9f5627c707efdaadecb1105c7a9674a7c1 --- /dev/null +++ b/marked/Rel-18/38_series/38305/3493d7ba4c86f944e159de1bf45ff03d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c78298c61d0dc1fb8828bb9791ee2aafa48a499b7f7d3b891f07625e6faecde3 +size 92031 diff --git a/marked/Rel-18/38_series/38305/4304a81342b40a72da20f26eb2cb2aa0_img.jpg b/marked/Rel-18/38_series/38305/4304a81342b40a72da20f26eb2cb2aa0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc6d06319c8bc3948b29ae1d7cad46edec9a6f3b --- /dev/null +++ b/marked/Rel-18/38_series/38305/4304a81342b40a72da20f26eb2cb2aa0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d574a3b80f300bc8cd31e1115995485f65c3d47e53f6f3c357e9a0ac53fa9461 +size 11864 diff --git a/marked/Rel-18/38_series/38305/435cf83a9531da350ea543aafa0add62_img.jpg b/marked/Rel-18/38_series/38305/435cf83a9531da350ea543aafa0add62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c99e10fb9e4e39875b204f016ef54271ab8cf95 --- /dev/null +++ b/marked/Rel-18/38_series/38305/435cf83a9531da350ea543aafa0add62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c873365c8ef91f83cb31c453cfab25c066026bc007037278c4b3adb2c09b2d92 +size 11492 diff --git a/marked/Rel-18/38_series/38305/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-18/38_series/38305/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47412c26b543811d82314a04b959b9522aa85c56 --- /dev/null +++ b/marked/Rel-18/38_series/38305/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:666fe3e421105070b01eeb21058effd412a2d89348629aba7d0f4d5fd1315ff0 +size 63695 diff --git a/marked/Rel-18/38_series/38305/44975a59174a634c7c5f49a9fb8eae71_img.jpg b/marked/Rel-18/38_series/38305/44975a59174a634c7c5f49a9fb8eae71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acad41d78dd46be4c2ff56a91170e132f1ce33b1 --- /dev/null +++ b/marked/Rel-18/38_series/38305/44975a59174a634c7c5f49a9fb8eae71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2455f2037b618d5e2fc20935ddcdb3b371094f31374376014ef7ce9c5f28d1a9 +size 22074 diff --git a/marked/Rel-18/38_series/38305/49b9b8bd6845ff94f361b147c84fc945_img.jpg b/marked/Rel-18/38_series/38305/49b9b8bd6845ff94f361b147c84fc945_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..980c729336f90a1c071ccaef25e281280deeec4a --- /dev/null +++ b/marked/Rel-18/38_series/38305/49b9b8bd6845ff94f361b147c84fc945_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a71e06e070d20195d5987f87a5d3a8ff6a2fd9603db3d50a48c56931c7b267db +size 10385 diff --git a/marked/Rel-18/38_series/38305/4c4c756d9c3797fc23d861bc37d2d63d_img.jpg b/marked/Rel-18/38_series/38305/4c4c756d9c3797fc23d861bc37d2d63d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..219c453a2b48d344e84ce69c8a85bb04a906b71f --- /dev/null +++ b/marked/Rel-18/38_series/38305/4c4c756d9c3797fc23d861bc37d2d63d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3547b0abbfb296cb0e8f8c6c649d39a1e71a985a21dc941125a45ad3c7a3d982 +size 34001 diff --git a/marked/Rel-18/38_series/38305/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-18/38_series/38305/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63541d6f23cdfe47ba5cdf7e58e35282b4944ed6 --- /dev/null +++ b/marked/Rel-18/38_series/38305/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90085490f316d12e51ead8635a0709e8c211379eafd7eaca29d424e10dab72e2 +size 66749 diff --git a/marked/Rel-18/38_series/38305/4f95964fc4eb05cd5cf7294114d77528_img.jpg b/marked/Rel-18/38_series/38305/4f95964fc4eb05cd5cf7294114d77528_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e63c19175a747741374dd60eb02f0d6f5c2adc48 --- /dev/null +++ b/marked/Rel-18/38_series/38305/4f95964fc4eb05cd5cf7294114d77528_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03d261fb6656c69e226f11591141d4e56cbd8868b2b3a8ca2431950cd8acd7d4 +size 15042 diff --git a/marked/Rel-18/38_series/38305/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-18/38_series/38305/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25c1563ddd41d54f83e0d10b760dc53bab365d87 --- /dev/null +++ b/marked/Rel-18/38_series/38305/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f0af854e67944e85b835829daba15a1189f58e17884c872f02c630acd9617b1 +size 71746 diff --git a/marked/Rel-18/38_series/38305/521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg b/marked/Rel-18/38_series/38305/521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae5e16d35b2bc643b1a0d0ddef284e77cdbc384f --- /dev/null +++ b/marked/Rel-18/38_series/38305/521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a5359eb8b995d10c03240e8e54a8e030cd262590391e921bdb4f470c0a838e5 +size 11613 diff --git a/marked/Rel-18/38_series/38305/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-18/38_series/38305/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40417eca04bb264dc5a0dd21235b726585d1fff --- /dev/null +++ b/marked/Rel-18/38_series/38305/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:890864a67e2cacbe6aed742b87777656f02bd581f572d57c42b506fe169137c3 +size 12672 diff --git a/marked/Rel-18/38_series/38305/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Rel-18/38_series/38305/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a5789b43893025d66c5f33093d5f900707f9d01 --- /dev/null +++ b/marked/Rel-18/38_series/38305/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ebf98cba2c0eb10cfb37652d0de7e3058a402024d7c7ef974bd0f8623c6ed39 +size 23656 diff --git a/marked/Rel-18/38_series/38305/54970ef2a417b7f66ddb72ec5c493956_img.jpg b/marked/Rel-18/38_series/38305/54970ef2a417b7f66ddb72ec5c493956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3acbfe7691a1c8074f3265a26665a578b2b76e6 --- /dev/null +++ b/marked/Rel-18/38_series/38305/54970ef2a417b7f66ddb72ec5c493956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e618ac05d7c5e361fcf317184b768182f9f7833284a04730d123e44fc894ff6 +size 13602 diff --git a/marked/Rel-18/38_series/38305/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-18/38_series/38305/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..868dde5f9da88ce92d566f594a1d7dc1b72f4cf8 --- /dev/null +++ b/marked/Rel-18/38_series/38305/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce11a317857937f0f4fcc98bb9ed0ac7b136b4e7ade21a980bb8fab184be6b56 +size 68975 diff --git a/marked/Rel-18/38_series/38305/59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg b/marked/Rel-18/38_series/38305/59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf70b398f22e06bd7f77b468da2df1c32cc8c4f0 --- /dev/null +++ b/marked/Rel-18/38_series/38305/59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e8c9281d864bdbebe434a0dbaa2824b8339aeb3e61b15e25c2846eba481e5f8 +size 43309 diff --git a/marked/Rel-18/38_series/38305/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38305/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5379e8c5f253052e7a3d89e4abc3e121335218e2 --- /dev/null +++ b/marked/Rel-18/38_series/38305/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a973fb5550ad8196ede7dd4a7d44c5ab8c8188b45cc470314931a0f57044ec4d +size 10120 diff --git a/marked/Rel-18/38_series/38305/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-18/38_series/38305/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c567102bc94096e591c9621aed77257c813ff579 --- /dev/null +++ b/marked/Rel-18/38_series/38305/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0a00869f5808ff7bd20099873989e2b1fed728bcde6f70059d562a3572526e +size 9951 diff --git a/marked/Rel-18/38_series/38305/6c03366230af7163bc0866430f8b20c2_img.jpg b/marked/Rel-18/38_series/38305/6c03366230af7163bc0866430f8b20c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6331b0d1b7d5fd542ac524690ac3dd795a9d378 --- /dev/null +++ b/marked/Rel-18/38_series/38305/6c03366230af7163bc0866430f8b20c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a3be5db8620c22adf04fc941e90221ab73658186b5d7103a8edf876007b097f +size 16032 diff --git a/marked/Rel-18/38_series/38305/6d2057d7e401741861ca63545a5d7d3b_img.jpg b/marked/Rel-18/38_series/38305/6d2057d7e401741861ca63545a5d7d3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36243c3ed5c99779440750ff64ad8192b644bab9 --- /dev/null +++ b/marked/Rel-18/38_series/38305/6d2057d7e401741861ca63545a5d7d3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9026e7506281648ce7afbdc31bd8b6ae7bdf2efd4d32bd4825aa4c6178058031 +size 40636 diff --git a/marked/Rel-18/38_series/38305/6d54943c64ae4af089cb9e98a78d0af7_img.jpg b/marked/Rel-18/38_series/38305/6d54943c64ae4af089cb9e98a78d0af7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91308350d6d05bcf4cca474d76249e8cb49eec9a --- /dev/null +++ b/marked/Rel-18/38_series/38305/6d54943c64ae4af089cb9e98a78d0af7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48cc57325f9b031fc144707ae360a8312c34ad786e6746645fc7326e7f90bf0d +size 22470 diff --git a/marked/Rel-18/38_series/38305/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-18/38_series/38305/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04f895e2ebefeb62a9860894d0571ebd35377c38 --- /dev/null +++ b/marked/Rel-18/38_series/38305/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:621f74378f953d32c95b806833bbc77b4de423aab85eb0765a3ef689b2e4098d +size 43345 diff --git a/marked/Rel-18/38_series/38305/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/marked/Rel-18/38_series/38305/710ff83dc4a77abbe489fbf1a462845a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e80f3deb049fa480bb5970915ddcf7615f81233 --- /dev/null +++ b/marked/Rel-18/38_series/38305/710ff83dc4a77abbe489fbf1a462845a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29a493b132ebfe5b673ddee6848158a7e20d7415297b909363270e3d0870dfc8 +size 13103 diff --git a/marked/Rel-18/38_series/38305/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg b/marked/Rel-18/38_series/38305/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d439ab8393636c858842ed18f64aa7d65be29c7d --- /dev/null +++ b/marked/Rel-18/38_series/38305/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36ad658e142861a3fd20880ff50de031ada936071a7425494b136ee14d32bc79 +size 11982 diff --git a/marked/Rel-18/38_series/38305/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-18/38_series/38305/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..708ba2d4495d52a02b0ab663cc1ca69972fcd99f --- /dev/null +++ b/marked/Rel-18/38_series/38305/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f8cfe228e95e9ecc2d93d5492c9eda67e1091550495f5f1c08aa8940f044c4f +size 11558 diff --git a/marked/Rel-18/38_series/38305/76d19e4271bf243b20d55a98efd51483_img.jpg b/marked/Rel-18/38_series/38305/76d19e4271bf243b20d55a98efd51483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f3ec1b2df8ee3b1fb902d80ea5880a0cf3e11bc --- /dev/null +++ b/marked/Rel-18/38_series/38305/76d19e4271bf243b20d55a98efd51483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25d1ae457c4ccda7180f04efe0598e9b13ba584f82a65d532189568c699ffed4 +size 107515 diff --git a/marked/Rel-18/38_series/38305/7bf5a5bb9f3c37fa7a3d32147f25bfda_img.jpg b/marked/Rel-18/38_series/38305/7bf5a5bb9f3c37fa7a3d32147f25bfda_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c341cc3198133c8dfdd37b3c7c33b31a08d1e31 --- /dev/null +++ b/marked/Rel-18/38_series/38305/7bf5a5bb9f3c37fa7a3d32147f25bfda_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a34e40b36322179a8ee3cc19daba26b211e95581dd1e6fdf84e8ae3f3030b37 +size 11233 diff --git a/marked/Rel-18/38_series/38305/7ec3b8a4d03079ca7c2dfaa2cbc54a9c_img.jpg b/marked/Rel-18/38_series/38305/7ec3b8a4d03079ca7c2dfaa2cbc54a9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ef3236f7cabd93acab7c3a5bcbc0847cbc35e10 --- /dev/null +++ b/marked/Rel-18/38_series/38305/7ec3b8a4d03079ca7c2dfaa2cbc54a9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b665cbc47d0bd0060904fbe5927fd0a431feb1e61fce22144bda4c8ebf1a2b0 +size 147246 diff --git a/marked/Rel-18/38_series/38305/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-18/38_series/38305/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47d17ab245e6709e74867b067a6764653347d7a4 --- /dev/null +++ b/marked/Rel-18/38_series/38305/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f08faad4c115104b7dd5a13c3b16107d59e146dc7cdf5738df6c53951609af78 +size 73502 diff --git a/marked/Rel-18/38_series/38305/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg b/marked/Rel-18/38_series/38305/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eed0c70f2e83310dce5939820d79666c07ec3029 --- /dev/null +++ b/marked/Rel-18/38_series/38305/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35c92bc9137021ae77c3f252ee7321bc787fcde36749ee901ee933fae6779b11 +size 29296 diff --git a/marked/Rel-18/38_series/38305/8d0915ee91e7b38094625cfc8d8f039b_img.jpg b/marked/Rel-18/38_series/38305/8d0915ee91e7b38094625cfc8d8f039b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8661304786ba87e4071ec47eae707ff832645ccd --- /dev/null +++ b/marked/Rel-18/38_series/38305/8d0915ee91e7b38094625cfc8d8f039b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68dfe426c64905dbfccff6a8b021d8a94d5e27e07731d843eb6ec17c61a38386 +size 73442 diff --git a/marked/Rel-18/38_series/38305/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-18/38_series/38305/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..166510adc35a2b91e3bee283c3167070c5ed9972 --- /dev/null +++ b/marked/Rel-18/38_series/38305/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17d0e4361efe1ab82940cf81c142b65ac7bac60bd1041f9b044233070b10f1b3 +size 35158 diff --git a/marked/Rel-18/38_series/38305/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-18/38_series/38305/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d624db890184832529b8cf827c73eddd2bc48255 --- /dev/null +++ b/marked/Rel-18/38_series/38305/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0728bd25cff2194a114e51a6f8e8d8781d5d9e430036b4a49c113546d1b7ee02 +size 34450 diff --git a/marked/Rel-18/38_series/38305/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-18/38_series/38305/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8369c4f64516cd0d3b56b64e0053d2270a96f9b --- /dev/null +++ b/marked/Rel-18/38_series/38305/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2ee319717ec725f4fcbff710d1f16bfd866431a8155a3cd6ddcc6c68b65aafb +size 24912 diff --git a/marked/Rel-18/38_series/38305/9bafc60bf378685e5e246c3ffad7b792_img.jpg b/marked/Rel-18/38_series/38305/9bafc60bf378685e5e246c3ffad7b792_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ccce67b4fd356ddc582f1b4349294755b125c7e --- /dev/null +++ b/marked/Rel-18/38_series/38305/9bafc60bf378685e5e246c3ffad7b792_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a8732ce3718baeb3a43c75b730d7baf8507dc4f92539a51882470e38ad84150 +size 15188 diff --git a/marked/Rel-18/38_series/38305/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-18/38_series/38305/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54d4a15a9c720bdf6665dd513965f9f89175dc46 --- /dev/null +++ b/marked/Rel-18/38_series/38305/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f6c00efe6847d4dbac296571cc39388abde90f7520c1c6792a0e4e6d158670a +size 15998 diff --git a/marked/Rel-18/38_series/38305/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-18/38_series/38305/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfe7164cb342db6a4a8c5dc63798095ba350c662 --- /dev/null +++ b/marked/Rel-18/38_series/38305/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2144af356c94547848c4f76d567ae70ff22dfb1d5698d7a6d58690d1bb2069f4 +size 26952 diff --git a/marked/Rel-18/38_series/38305/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-18/38_series/38305/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d18f8de39bb7b9768fd2921403cae4ce32799f7 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8d9520655e7d4cf8257269453a375a384b3c7bf2aff9f75bb5d178f2ac843ad +size 14851 diff --git a/marked/Rel-18/38_series/38305/a1530b77a339c01162a6181e83cbc906_img.jpg b/marked/Rel-18/38_series/38305/a1530b77a339c01162a6181e83cbc906_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..697871063367a09f3f226816852d097e28a8f495 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a1530b77a339c01162a6181e83cbc906_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ee5c0b91678ab69147995f2491bbf82c2c0ffa7249f36a55d2cb0ce4ab3c0bf +size 13632 diff --git a/marked/Rel-18/38_series/38305/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-18/38_series/38305/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2600a0168c6f61d9be793741b7117eb5dad078b3 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbda136c68ddbfe464ee39f6ef43e255ba0e02921afe1b8290c25dea63b18d52 +size 30035 diff --git a/marked/Rel-18/38_series/38305/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/Rel-18/38_series/38305/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb3a7124e90eeddf0dcfba3cc333b265c26fce69 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee6531a17d3e43fbd6aca408c7becf91c3482ea4ba9928ea7764ae1f62fc8891 +size 61892 diff --git a/marked/Rel-18/38_series/38305/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-18/38_series/38305/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14ce1102defc5719733cc6777540ec310506bd4f --- /dev/null +++ b/marked/Rel-18/38_series/38305/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6342eb9e2db645570745d70d7f868ea09a3225ab42de1e6f4ffdc72511e426a2 +size 12232 diff --git a/marked/Rel-18/38_series/38305/a82bc78bff7fbefef1c0fb744365f957_img.jpg b/marked/Rel-18/38_series/38305/a82bc78bff7fbefef1c0fb744365f957_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95a7c816886b3b3e5a9b55b298a9a902bacbbcee --- /dev/null +++ b/marked/Rel-18/38_series/38305/a82bc78bff7fbefef1c0fb744365f957_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a3fa69c7727a07cf03de3a91e07d09e8d7b7aef12eba1aa04323f490eea2214 +size 21081 diff --git a/marked/Rel-18/38_series/38305/a97f7c055c1fd8d79037d02b3fc38496_img.jpg b/marked/Rel-18/38_series/38305/a97f7c055c1fd8d79037d02b3fc38496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b133e79b4445e43a25b620693c415f6cf278585 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a97f7c055c1fd8d79037d02b3fc38496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ebee0d9597cae7e87de956ceafcc43f155dfbdf82742713c750bbf777de8e6d +size 55140 diff --git a/marked/Rel-18/38_series/38305/ade78fa2db5ef634649778c88d67c733_img.jpg b/marked/Rel-18/38_series/38305/ade78fa2db5ef634649778c88d67c733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..321102d86d3566a0f193cc9190a1bbeac4c2476c --- /dev/null +++ b/marked/Rel-18/38_series/38305/ade78fa2db5ef634649778c88d67c733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c65f50319d311a0a65b0ae433aa6fa45a74307b64314e775c38855c36076436 +size 54985 diff --git a/marked/Rel-18/38_series/38305/b02ba0b73e95416eb547976f6145b169_img.jpg b/marked/Rel-18/38_series/38305/b02ba0b73e95416eb547976f6145b169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60cee1cbe0ee2e4a9989e98c1eb24223b0116fb0 --- /dev/null +++ b/marked/Rel-18/38_series/38305/b02ba0b73e95416eb547976f6145b169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5fd7ac51d7663648766b7f5489a55cc9341cf43da528c723b0feef4873d4f51 +size 20960 diff --git a/marked/Rel-18/38_series/38305/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/marked/Rel-18/38_series/38305/b55cd9b5721bd8aabc979c85316924e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a288d767117e55ef60252886648e64ab09663123 --- /dev/null +++ b/marked/Rel-18/38_series/38305/b55cd9b5721bd8aabc979c85316924e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b52cdf0edeaff2e474b534a255ec3d20c7265a31427637c0d10e01e7ba397120 +size 11036 diff --git a/marked/Rel-18/38_series/38305/b6098e84ba6261a5152f5a4fa790c579_img.jpg b/marked/Rel-18/38_series/38305/b6098e84ba6261a5152f5a4fa790c579_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4b96bc723835ccfcfcadf1839062c65f85b310e --- /dev/null +++ b/marked/Rel-18/38_series/38305/b6098e84ba6261a5152f5a4fa790c579_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4949ef41f00f941594830c0df5ab1273cc26c1daab263881b9b32132fe494e8 +size 15615 diff --git a/marked/Rel-18/38_series/38305/b822771c1a5790feaeecfc439e08bcdd_img.jpg b/marked/Rel-18/38_series/38305/b822771c1a5790feaeecfc439e08bcdd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26b871016ebb4e3c51a8181bb8d988be8ca65f78 --- /dev/null +++ b/marked/Rel-18/38_series/38305/b822771c1a5790feaeecfc439e08bcdd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869554b4851299bf7bc199d0673e29e2ebad94a2ba3f75b7039cf106a1077ded +size 9681 diff --git a/marked/Rel-18/38_series/38305/bbd36eba6bb7c4ba87608874c8c714ff_img.jpg b/marked/Rel-18/38_series/38305/bbd36eba6bb7c4ba87608874c8c714ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b06352c8b267f76c33eb392598d9db9b11eb4da --- /dev/null +++ b/marked/Rel-18/38_series/38305/bbd36eba6bb7c4ba87608874c8c714ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac4bb2a96a7646455d644ae2e97fe14b0072b00e220b1808dda4127b2aeea5d1 +size 11510 diff --git a/marked/Rel-18/38_series/38305/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg b/marked/Rel-18/38_series/38305/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a288d767117e55ef60252886648e64ab09663123 --- /dev/null +++ b/marked/Rel-18/38_series/38305/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b52cdf0edeaff2e474b534a255ec3d20c7265a31427637c0d10e01e7ba397120 +size 11036 diff --git a/marked/Rel-18/38_series/38305/cde3789e303efe653250b497e839e243_img.jpg b/marked/Rel-18/38_series/38305/cde3789e303efe653250b497e839e243_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..953593d59b63d4c2c01a61ff529ff21da8c91ea5 --- /dev/null +++ b/marked/Rel-18/38_series/38305/cde3789e303efe653250b497e839e243_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3de5c9c6d120c2d0d4f119553087d68a3d12bbe38ca30e2032ab877fa8df5fe2 +size 15241 diff --git a/marked/Rel-18/38_series/38305/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-18/38_series/38305/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f02db69e3c019332e793d3d1fcbf0cb55fe30056 --- /dev/null +++ b/marked/Rel-18/38_series/38305/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b922d9226881ea9885b6c3865718f4b979fa10d48beb7443e3fa760787cdf1c5 +size 11615 diff --git a/marked/Rel-18/38_series/38305/d53421c44b83ef2ffc1fa09fbebc609f_img.jpg b/marked/Rel-18/38_series/38305/d53421c44b83ef2ffc1fa09fbebc609f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a156416f437195dccb18c388fe3b93a235303def --- /dev/null +++ b/marked/Rel-18/38_series/38305/d53421c44b83ef2ffc1fa09fbebc609f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6fa56715d9e0747c4cc4175ba1a63b0749df6c9cb4971481ed569c474d9d03d +size 14916 diff --git a/marked/Rel-18/38_series/38305/dbe8bef1723acb3e03e8616be4faf939_img.jpg b/marked/Rel-18/38_series/38305/dbe8bef1723acb3e03e8616be4faf939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2be29a11065f0ca9bf7c3dc3ab2d5c09d2ff3a2 --- /dev/null +++ b/marked/Rel-18/38_series/38305/dbe8bef1723acb3e03e8616be4faf939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a0f843a5989e12d0cec51031894791a8e6628531d72197ab2fa3403d9ab34d7 +size 39650 diff --git a/marked/Rel-18/38_series/38305/e1136c8a41c5a8081a8a554e513cd86e_img.jpg b/marked/Rel-18/38_series/38305/e1136c8a41c5a8081a8a554e513cd86e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef027d76a874f2df67a797f08157fa089024bd57 --- /dev/null +++ b/marked/Rel-18/38_series/38305/e1136c8a41c5a8081a8a554e513cd86e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90637477fbd2fb34e2c463b5a5f246ea0fea1d08e9140fcc49793f607d2d9798 +size 13891 diff --git a/marked/Rel-18/38_series/38305/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-18/38_series/38305/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..caa78efa28403d3f656b271fd978053be8863b7f --- /dev/null +++ b/marked/Rel-18/38_series/38305/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ef3ebdf68fde158a78f5a8e37372c1c5c65802c0106dfdfba19dc72a90981e2 +size 16597 diff --git a/marked/Rel-18/38_series/38305/e451a51157214e53bd9c64db914771cc_img.jpg b/marked/Rel-18/38_series/38305/e451a51157214e53bd9c64db914771cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63a43e07139a767db330da95844eb5215d70c319 --- /dev/null +++ b/marked/Rel-18/38_series/38305/e451a51157214e53bd9c64db914771cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cb3c096b209d6c4e6c81eeeba1c2fd24a71bdd8d979387219c1ef1805e4030f +size 11943 diff --git a/marked/Rel-18/38_series/38305/e48a7aa9d3880694350259852fefbef2_img.jpg b/marked/Rel-18/38_series/38305/e48a7aa9d3880694350259852fefbef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fca70ef69e882c7a316a9291f9dd7b2546cae8a --- /dev/null +++ b/marked/Rel-18/38_series/38305/e48a7aa9d3880694350259852fefbef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:323e1b7649eb3891c64b741dabbaf1ede67e8c2d422033db25d8df3c7a2545e0 +size 11763 diff --git a/marked/Rel-18/38_series/38305/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-18/38_series/38305/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..caa78efa28403d3f656b271fd978053be8863b7f --- /dev/null +++ b/marked/Rel-18/38_series/38305/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ef3ebdf68fde158a78f5a8e37372c1c5c65802c0106dfdfba19dc72a90981e2 +size 16597 diff --git a/marked/Rel-18/38_series/38305/eb265f9639a96a8cf1dcdc1603ef0215_img.jpg b/marked/Rel-18/38_series/38305/eb265f9639a96a8cf1dcdc1603ef0215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e99b7eb1243e336d718e15e13f7d3a1adc98523a --- /dev/null +++ b/marked/Rel-18/38_series/38305/eb265f9639a96a8cf1dcdc1603ef0215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87bcfb53d5fbb319d68f53f0d0525cb1e5548d251e63d28f0c873797ae21b743 +size 21937 diff --git a/marked/Rel-18/38_series/38305/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-18/38_series/38305/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b90828ecb8419e5ce52becfcedc61d29e040815 --- /dev/null +++ b/marked/Rel-18/38_series/38305/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45ddc94ac6753dc502f203135667dd10b0af39614f6393688e6e30131b969370 +size 13611 diff --git a/marked/Rel-18/38_series/38305/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-18/38_series/38305/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38fc25c44b6d7fbc3da83b7f4688e21414638708 --- /dev/null +++ b/marked/Rel-18/38_series/38305/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dbd6faf8d5a5b189a88cc45fe84d34b96b36a0ae0ae8fb808bde6934da51486 +size 15629 diff --git a/marked/Rel-18/38_series/38305/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-18/38_series/38305/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a273453cbd1e3d85f9b4eaa68f2370bc9e75f856 --- /dev/null +++ b/marked/Rel-18/38_series/38305/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:499bcf81f19a303262bc5809eb409b9b5e073b329ac403b6acd4323045a22f54 +size 18152 diff --git a/marked/Rel-18/38_series/38305/raw.md b/marked/Rel-18/38_series/38305/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..853d06aaa6e980349ec2b43e5fecb4e0fbfbbb83 --- /dev/null +++ b/marked/Rel-18/38_series/38305/raw.md @@ -0,0 +1,7112 @@ + + +# 3GPP TS 38.305 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, black, sans-serif font. Below the "3GPP" text is a red signal icon consisting of three curved lines. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices + +# **3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +# Contents + +| | | +|---------------------------------------------------------------------------------|----| +| Foreword..... | 12 | +| 1 Scope..... | 13 | +| 2 References..... | 13 | +| 3 Definitions, symbols and abbreviations..... | 15 | +| 3.1 Definitions..... | 15 | +| 3.2 Abbreviations..... | 17 | +| 4 Main concepts and requirements..... | 19 | +| 4.1 Assumptions and Generalities..... | 19 | +| 4.2 Role of UE Positioning Methods..... | 20 | +| 4.3 Standard UE Positioning Methods..... | 21 | +| 4.3.1 Introduction..... | 21 | +| 4.3.2 Network-assisted GNSS methods..... | 22 | +| 4.3.3 OTDOA positioning..... | 23 | +| 4.3.4 Enhanced Cell ID methods..... | 23 | +| 4.3.5 Barometric pressure sensor positioning..... | 23 | +| 4.3.6 WLAN positioning..... | 23 | +| 4.3.7 Bluetooth positioning..... | 23 | +| 4.3.8 TBS positioning..... | 24 | +| 4.3.9 Motion sensor positioning..... | 24 | +| 4.3.10 NR Enhanced Cell ID methods..... | 24 | +| 4.3.11 Multi-RTT positioning..... | 24 | +| 4.3.12 DL-AoD positioning..... | 25 | +| 4.3.13 DL-TDOA positioning..... | 25 | +| 4.3.14 UL-TDOA positioning..... | 25 | +| 4.3.15 UL-AoA..... | 25 | +| 4.3.16 SL Positioning and Ranging..... | 25 | +| 4.3.16.1 Sidelink Round Trip Time Positioning (SL-RTT)..... | 25 | +| 4.3.16.2 Sidelink Angle-of-Arrival (SL-AoA)..... | 26 | +| 4.3.16.3 Sidelink Time Difference of Arrival (SL-TDOA)..... | 26 | +| 4.3.16.4 Sidelink Time of Arrival (SL-TOA)..... | 26 | +| 5 NG-RAN UE Positioning Architecture..... | 26 | +| 5.1 Architecture..... | 26 | +| 5.2 UE Positioning Operations..... | 27 | +| 5.3 NG-RAN Positioning Operations..... | 29 | +| 5.3.1 General NG-RAN Positioning Operations..... | 29 | +| 5.3.2 OTDOA Positioning Support..... | 29 | +| 5.3.3 Assistance Information Broadcast Support..... | 29 | +| 5.3.4 NR RAT-Dependent Positioning Support..... | 29 | +| 5.4 Functional Description of Elements Related to UE Positioning in NG-RAN..... | 29 | +| 5.4.1 User Equipment (UE)..... | 29 | +| 5.4.2 gNB..... | 30 | + +###### Copyright Notification + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association +Bluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its members + +| | | | +|---------|-----------------------------------------------------------------------|----| +| 5.4.3 | ng-eNB..... | 30 | +| 5.4.4 | Location Management Function (LMF)..... | 30 | +| 5.4.5 | Positioning Reference Unit (PRU)..... | 31 | +| 6 | Signalling protocols and interfaces..... | 31 | +| 6.1 | Network interfaces supporting positioning operations..... | 31 | +| 6.1.1 | General LCS control plane architecture..... | 31 | +| 6.1.2 | NR-Uu interface..... | 31 | +| 6.1.3 | LTE-Uu interface..... | 31 | +| 6.1.4 | NG-C interface..... | 31 | +| 6.1.5 | NL1 interface..... | 31 | +| 6.1.6 | F1 interface..... | 32 | +| 6.1.7 | NR PC5 interface..... | 32 | +| 6.2 | UE-terminated protocols..... | 32 | +| 6.2.1 | LTE Positioning Protocol (LPP)..... | 32 | +| 6.2.2 | Radio Resource Control (RRC) for NR..... | 32 | +| 6.2.3 | Radio Resource Control (RRC) for LTE..... | 33 | +| 6.2.4 | Medium Access Control (MAC) for NR..... | 33 | +| 6.2.5 | Sidelink Positioning Protocol (SLPP)..... | 33 | +| 6.3 | NG-RAN Node terminated protocols..... | 34 | +| 6.3.1 | NR Positioning Protocol A (NRPPa)..... | 34 | +| 6.3.2 | NG Application Protocol (NGAP)..... | 34 | +| 6.4 | Signalling between an LMF and UE..... | 34 | +| 6.4.1 | Protocol Layering..... | 34 | +| 6.4.2 | LPP PDU Transfer..... | 35 | +| 6.4.3 | SLPP PDU Transfer..... | 37 | +| 6.5 | Signalling between an LMF and NG-RAN node..... | 38 | +| 6.5.1 | Protocol Layering..... | 38 | +| 6.5.2 | NRPPa PDU Transfer for UE Positioning..... | 38 | +| 6.5.3 | NRPPa PDU Transfer for Positioning Support..... | 39 | +| 6.5.4 | NRPPa PDU Transfer for Assistance Information Broadcast..... | 40 | +| 6.6 | Void..... | 42 | +| 6.7 | Signalling between UEs..... | 42 | +| 6.7.1 | Protocol Layering..... | 42 | +| 6.7.2 | SLPP PDU Transfer..... | 42 | +| 7 | General NG-RAN UE Positioning procedures..... | 44 | +| 7.1 | General LPP procedures for UE Positioning..... | 44 | +| 7.1.1 | LPP procedures..... | 44 | +| 7.1.2 | Positioning procedures..... | 44 | +| 7.1.2.1 | Capability transfer..... | 44 | +| 7.1.2.2 | Assistance data transfer..... | 44 | +| 7.1.2.3 | Location information transfer..... | 44 | +| 7.1.2.4 | Multiple transactions..... | 44 | +| 7.1.2.5 | Sequence of procedures..... | 44 | +| 7.1.2.6 | Error handling..... | 45 | +| 7.1.2.7 | Abort..... | 45 | +| 7.1.3 | UE positioning measurements in RRC_IDLE state for NB-IoT..... | 45 | +| 7.2 | General NRPPa Procedures for UE Positioning..... | 46 | +| 7.2.1 | NRPPa procedures..... | 46 | +| 7.2.2 | NRPPa transaction types..... | 47 | +| 7.2.2.1 | Location information transfer..... | 47 | +| 7.3 | Service Layer Support using combined LPP and NRPPa Procedures..... | 47 | +| 7.3.1 | General..... | 47 | +| 7.3.2 | NI-LR and MT-LR Service Support..... | 47 | +| 7.3.3 | MO-LR Service Support..... | 48 | +| 7.3.4 | Deferred MT-LR Event Reporting Support..... | 49 | +| 7.3A | Service Layer Support for Sidelink Positioning..... | 50 | +| 7.3A.1 | General..... | 50 | +| 7.3A.2 | SL-MT-LR Service Support..... | 50 | +| 7.3A.3 | SL-MT-LR Service Support for periodic, triggered Location Events..... | 52 | +| 7.3A.4 | SL-MO-LR Service Support..... | 53 | + +| | | | +|------------|-----------------------------------------------------------------|----| +| 7.4 | General RRC procedures for UE Positioning..... | 55 | +| 7.4.1 | NR RRC Procedures..... | 55 | +| 7.4.1.0 | General..... | 55 | +| 7.4.1.1 | Location Measurement Indication..... | 55 | +| 7.4.1.2 | UE Positioning Assistance Information..... | 56 | +| 7.4.2 | LTE RRC Procedures..... | 56 | +| 7.4.2.0 | General..... | 56 | +| 7.4.2.1 | Inter-frequency RSTD measurement indication..... | 56 | +| 7.5 | Procedures for Broadcast of Assistance Data..... | 57 | +| 7.5.1 | General..... | 57 | +| 7.5.2 | Broadcast Procedures..... | 57 | +| 7.6 | Procedures for On-Demand PRS transmission..... | 59 | +| 7.6.1 | General..... | 59 | +| 7.6.2 | On-Demand PRS transmission procedures..... | 59 | +| 7.7 | Procedures for Pre-configured Measurement Gap..... | 61 | +| 7.7.1 | General..... | 61 | +| 7.7.2 | Pre-configured Measurement Gap procedures..... | 61 | +| 7.8 | Procedures for Pre-configured PRS processing window..... | 63 | +| 7.8.1 | General..... | 63 | +| 7.8.2 | Pre-configured PRS processing window procedures..... | 63 | +| 7.9 | Positioning in RRC_INACTIVE state..... | 64 | +| 7.10 | Positioning in RRC_IDLE state..... | 64 | +| 7.11 | General SLPP procedures for UE Positioning and Ranging..... | 65 | +| 7.11.1 | SLPP procedures..... | 65 | +| 7.11.2 | SLPP positioning and ranging procedures..... | 65 | +| 7.11.2.1 | SLPP capability transfer..... | 65 | +| 7.11.2.2 | SLPP assistance data transfer..... | 66 | +| 7.11.2.3 | SLPP location information transfer..... | 67 | +| 7.11.2.4 | Error handling..... | 67 | +| 7.11.2.5 | Abort..... | 68 | +| 7.11.2.6 | Sequence of Procedures..... | 68 | +| 7.12 | General UE-only sidelink positioning and ranging procedure..... | 69 | +| 7.13 | Positioning Integrity..... | 70 | +| 7.13.1 | General..... | 70 | +| 7.13.2 | Integrity Principle of Operation..... | 71 | +| 8 | Positioning methods and Supporting Procedures..... | 72 | +| 8.1 | GNSS positioning methods..... | 72 | +| 8.1.1 | General..... | 72 | +| 8.1.2 | Information to be transferred between NG-RAN/5GC Elements..... | 74 | +| 8.1.2.0 | General..... | 74 | +| 8.1.2.1 | Information that may be transferred from the LMF to UE..... | 74 | +| 8.1.2.1.0 | General..... | 74 | +| 8.1.2.1.1 | Reference Time..... | 74 | +| 8.1.2.1.2 | Reference Location..... | 75 | +| 8.1.2.1.3 | Ionospheric Models..... | 75 | +| 8.1.2.1.4 | Earth Orientation Parameters..... | 75 | +| 8.1.2.1.5 | GNSS-GNSS Time Offsets..... | 75 | +| 8.1.2.1.6 | Differential GNSS Corrections..... | 75 | +| 8.1.2.1.7 | Ephemeris and Clock Models..... | 75 | +| 8.1.2.1.8 | Real-Time Integrity..... | 75 | +| 8.1.2.1.9 | Data Bit Assistance..... | 75 | +| 8.1.2.1.10 | Acquisition Assistance..... | 76 | +| 8.1.2.1.11 | Almanac..... | 76 | +| 8.1.2.1.12 | UTC Models..... | 76 | +| 8.1.2.1.13 | RTK Reference Station Information..... | 76 | +| 8.1.2.1.14 | RTK Auxiliary Station Data..... | 76 | +| 8.1.2.1.15 | RTK Observations..... | 76 | +| 8.1.2.1.16 | RTK Common Observation Information..... | 77 | +| 8.1.2.1.17 | GLONASS RTK Bias Information..... | 77 | +| 8.1.2.1.18 | RTK MAC Correction Differences..... | 77 | +| 8.1.2.1.19 | RTK Residuals..... | 77 | + +| | | | +|-------------|----------------------------------------------------------------------------------------------|----| +| 8.1.2.1.20 | RTK FKP Gradients..... | 77 | +| 8.1.2.1.21 | SSR Orbit Corrections..... | 77 | +| 8.1.2.1.22 | SSR Clock Corrections..... | 78 | +| 8.1.2.1.23 | SSR Code Bias..... | 78 | +| 8.1.2.1.24 | SSR Phase Bias..... | 78 | +| 8.1.2.1.25 | SSR STEC Corrections..... | 78 | +| 8.1.2.1.26 | SSR Gridded Correction..... | 79 | +| 8.1.2.1.27 | SSR URA..... | 79 | +| 8.1.2.1.28 | SSR Correction Points..... | 79 | +| 8.1.2.1.29 | Integrity Service Parameters..... | 79 | +| 8.1.2.1.30 | Integrity Alerts..... | 79 | +| 8.1.2.1.31 | SSR IOD Update..... | 79 | +| 8.1.2.1.32 | SSR Satellite PCV Residuals..... | 79 | +| 8.1.2.1a | Recommendations for grouping of assistance data to support different RTK service levels..... | 79 | +| 8.1.2.1b | Mapping of integrity parameters..... | 82 | +| 8.1.2.2 | Information that may be transferred from the UE to LMF..... | 84 | +| 8.1.2.2.0 | General..... | 84 | +| 8.1.2.2.1 | GNSS Measurement Information..... | 84 | +| 8.1.2.2.1.0 | General..... | 84 | +| 8.1.2.2.1.1 | UE-based mode..... | 84 | +| 8.1.2.2.1.2 | UE-assisted mode..... | 84 | +| 8.1.2.2.2 | Additional Non-GNSS Related Information..... | 85 | +| 8.1.3 | Assisted-GNSS Positioning Procedures..... | 85 | +| 8.1.3.1 | Capability Transfer Procedure..... | 85 | +| 8.1.3.2 | Assistance Data Transfer Procedure..... | 85 | +| 8.1.3.2.0 | General..... | 85 | +| 8.1.3.2.1 | LMF initiated Assistance Data Delivery..... | 85 | +| 8.1.3.2.1a | LMF initiated Periodic Assistance Data Delivery..... | 85 | +| 8.1.3.2.2 | UE initiated Assistance Data Transfer..... | 86 | +| 8.1.3.2.2a | UE initiated Periodic Assistance Data Transfer..... | 87 | +| 8.1.3.3 | Location Information Transfer Procedure..... | 88 | +| 8.1.3.3.0 | General..... | 88 | +| 8.1.3.3.1 | LMF initiated Location Information Transfer Procedure..... | 88 | +| 8.1.3.3.2 | UE-initiated Location Information Delivery Procedure..... | 88 | +| 8.2 | OTDOA positioning..... | 89 | +| 8.2.1 | General..... | 89 | +| 8.2.2 | Information to be transferred between NG-RAN/5GC Elements..... | 89 | +| 8.2.2.0 | General..... | 89 | +| 8.2.2.1 | Information that may be transferred from the LMF to UE..... | 89 | +| 8.2.2.2 | Information that may be transferred from the ng-eNB to LMF..... | 90 | +| 8.2.2.3 | Information that may be transferred from the UE to LMF..... | 90 | +| 8.2.2.4 | Information that may be transferred from the gNB to LMF..... | 90 | +| 8.2.3 | OTDOA Positioning Procedures..... | 90 | +| 8.2.3.0 | General..... | 90 | +| 8.2.3.1 | Capability Transfer Procedure..... | 91 | +| 8.2.3.2 | Assistance Data Transfer Procedure..... | 91 | +| 8.2.3.2.1 | Assistance Data Transfer between LMF and UE..... | 91 | +| 8.2.3.2.1.0 | General..... | 91 | +| 8.2.3.2.1.1 | LMF initiated Assistance Data Delivery..... | 91 | +| 8.2.3.2.1.2 | UE initiated Assistance Data Transfer..... | 91 | +| 8.2.3.2.2 | Assistance Data Delivery between LMF and NG-RAN node..... | 92 | +| 8.2.3.2.2.0 | General..... | 92 | +| 8.2.3.2.2.1 | LMF-initiated assistance data delivery to the LMF..... | 92 | +| 8.2.3.3 | Location Information Transfer Procedure..... | 92 | +| 8.2.3.3.0 | General..... | 92 | +| 8.2.3.3.1 | LMF-initiated Location Information Transfer Procedure..... | 92 | +| 8.2.3.3.2 | UE-initiated Location Information Delivery procedure..... | 93 | +| 8.3 | Enhanced cell ID positioning methods..... | 93 | +| 8.3.1 | General..... | 93 | +| 8.3.2 | Information to be transferred between NG-RAN/5GC Elements..... | 94 | +| 8.3.2.0 | General..... | 94 | + +| | | | +|-----------|-----------------------------------------------------------------|-----| +| 8.3.2.1 | Information that may be transferred from the LMF to UE..... | 94 | +| 8.3.2.2 | Information that may be transferred from the ng-eNB to LMF..... | 94 | +| 8.3.2.3 | Information that may be transferred from the gNB to LMF..... | 95 | +| 8.3.2.4 | Information that may be transferred from the UE to LMF..... | 95 | +| 8.3.3 | Downlink E-CID Positioning Procedures..... | 96 | +| 8.3.3.0 | General..... | 96 | +| 8.3.3.1 | Capability Transfer Procedure..... | 96 | +| 8.3.3.2 | Assistance Data Transfer Procedure..... | 96 | +| 8.3.3.3 | Location Information Transfer Procedure..... | 96 | +| 8.3.3.3.1 | LMF-initiated Location Information Transfer..... | 96 | +| 8.3.3.3.2 | UE-initiated Location Information Delivery procedure..... | 96 | +| 8.3.4 | Uplink E-CID Positioning Procedures..... | 97 | +| 8.3.4.0 | General..... | 97 | +| 8.3.4.1 | Capability Transfer Procedure..... | 97 | +| 8.3.4.2 | Assistance Data Transfer Procedure..... | 97 | +| 8.3.4.3 | Position Measurement Procedure..... | 97 | +| 8.3.4.3.0 | General..... | 97 | +| 8.3.4.3.1 | LMF-initiated Position Measurement..... | 97 | +| 8.4 | Barometric pressure sensor positioning..... | 98 | +| 8.4.2 | Information to be transferred between NG-RAN/5GC Elements..... | 99 | +| 8.4.2.0 | General..... | 99 | +| 8.4.2.1 | Information that may be transferred from the LMF to UE..... | 99 | +| 8.4.2.1.0 | General..... | 99 | +| 8.4.2.1.1 | Barometric pressure sensor assistance data..... | 99 | +| 8.4.2.2 | Information that may be transferred from the UE to LMF..... | 99 | +| 8.4.2.2.0 | General..... | 99 | +| 8.4.2.2.1 | Standalone mode..... | 99 | +| 8.4.2.2.2 | UE-assisted mode..... | 99 | +| 8.4.2.2.3 | UE-based mode..... | 100 | +| 8.4.3 | Barometric Pressure Sensor Positioning Procedures..... | 100 | +| 8.4.3.1 | Capability Transfer Procedure..... | 100 | +| 8.4.3.2 | Assistance Data Transfer Procedure..... | 100 | +| 8.4.3.2.0 | General..... | 100 | +| 8.4.3.2.1 | LMF initiated Assistance Data Delivery..... | 100 | +| 8.4.3.2.2 | UE initiated Assistance Data Transfer..... | 100 | +| 8.4.3.3 | Location Information Transfer Procedure..... | 101 | +| 8.4.3.3.0 | General..... | 101 | +| 8.4.3.3.1 | LMF initiated Location Information Transfer Procedure..... | 101 | +| 8.4.3.3.2 | UE-initiated Location Information Delivery Procedure..... | 102 | +| 8.5 | WLAN positioning..... | 102 | +| 8.5.1 | General..... | 102 | +| 8.5.2 | Information to be transferred between NG-RAN/5GC Elements..... | 102 | +| 8.5.2.0 | General..... | 102 | +| 8.5.2.1 | Information that may be transferred from the LMF to UE..... | 103 | +| 8.5.2.1.0 | General..... | 103 | +| 8.5.2.1.1 | WLAN AP BSSID..... | 103 | +| 8.5.2.1.2 | WLAN AP SSID..... | 103 | +| 8.5.2.1.3 | WLAN AP Type Data..... | 103 | +| 8.5.2.1.4 | WLAN AP Location..... | 103 | +| 8.5.2.2 | Information that may be transferred from the UE to LMF..... | 103 | +| 8.5.2.2.0 | General..... | 103 | +| 8.5.2.2.1 | Standalone mode..... | 104 | +| 8.5.2.2.2 | UE-assisted mode..... | 104 | +| 8.5.2.2.3 | UE-based mode..... | 104 | +| 8.5.3 | WLAN Positioning Procedures..... | 104 | +| 8.5.3.1 | Capability Transfer Procedure..... | 104 | +| 8.5.3.2 | Assistance Data Transfer Procedure..... | 104 | +| 8.5.3.2.0 | General..... | 104 | +| 8.5.3.2.1 | LMF initiated Assistance Data Delivery..... | 104 | +| 8.5.3.2.2 | UE initiated Assistance Data Transfer..... | 105 | +| 8.5.3.3 | Location Information Transfer Procedure..... | 105 | + +| | | | +|-----------|-------------------------------------------------------------------------|-----| +| 8.5.3.3.0 | General..... | 105 | +| 8.5.3.3.1 | LMF initiated Location Information Transfer Procedure..... | 106 | +| 8.5.3.3.2 | UE-initiated Location Information Delivery Procedure..... | 106 | +| 8.6 | Bluetooth positioning..... | 106 | +| 8.6.2 | Information to be transferred between NG-RAN/5GC Elements..... | 107 | +| 8.6.2.1 | Information that may be transferred from the LMF to UE..... | 107 | +| 8.6.2.1.0 | General..... | 107 | +| 8.6.2.1.1 | Bluetooth beacon advertising address..... | 108 | +| 8.6.2.1.2 | Bluetooth beacon location..... | 108 | +| 8.6.2.1.3 | Bluetooth beacon antenna array orientation..... | 108 | +| 8.6.2.1.4 | Bluetooth beacon antenna array configuration and switching pattern..... | 108 | +| 8.6.2.1.5 | Bluetooth beacon AoD transmission configuration..... | 108 | +| 8.6.2.2 | Information that may be transferred from the UE to LMF..... | 108 | +| 8.6.2.2.0 | General..... | 108 | +| 8.6.2.2.1 | Standalone mode..... | 109 | +| 8.6.2.2.2 | UE-assisted mode..... | 109 | +| 8.6.2.2.3 | UE-based mode..... | 110 | +| 8.6.3 | Bluetooth Positioning Procedures..... | 110 | +| 8.6.3.1 | Capability Transfer Procedure..... | 110 | +| 8.6.3.2 | Assistance Data Transfer Procedure..... | 110 | +| 8.6.3.2.0 | General..... | 110 | +| 8.6.3.2.2 | UE initiated Assistance Data Transfer..... | 110 | +| 8.6.3.3 | Location Information Transfer Procedure..... | 111 | +| 8.6.3.3.0 | General..... | 111 | +| 8.6.3.3.1 | LMF initiated Location Information Transfer Procedure..... | 111 | +| 8.6.3.3.2 | UE-initiated Location Information Delivery Procedure..... | 112 | +| 8.7 | TBS positioning..... | 112 | +| 8.7.1 | General..... | 112 | +| 8.7.2 | Information to be transferred between NG-RAN/5GC Elements..... | 113 | +| 8.7.2.0 | General..... | 113 | +| 8.7.2.1 | Information that may be transferred from the LMF to UE..... | 113 | +| 8.7.2.1.0 | General..... | 113 | +| 8.7.2.1.1 | Acquisition Assistance..... | 113 | +| 8.7.2.1.2 | Almanac..... | 113 | +| 8.7.2.2 | Information that may be transferred from the UE to LMF..... | 113 | +| 8.7.2.2.0 | General..... | 113 | +| 8.7.2.2.1 | Standalone mode..... | 113 | +| 8.7.2.2.2 | UE-assisted mode..... | 114 | +| 8.7.2.2.3 | UE-based mode..... | 114 | +| 8.7.3 | TBS Positioning Procedures..... | 114 | +| 8.7.3.1 | Capability Transfer Procedure..... | 114 | +| 8.7.3.2 | Assistance Data Transfer Procedure..... | 114 | +| 8.7.3.2.0 | General..... | 114 | +| 8.7.3.2.1 | LMF initiated Assistance Data Delivery..... | 114 | +| 8.7.3.2.2 | UE initiated Assistance Data Transfer..... | 114 | +| 8.7.3.3 | Location Information Transfer Procedure..... | 115 | +| 8.7.3.3.0 | General..... | 115 | +| 8.7.3.3.1 | LMF initiated Location Information Transfer Procedure..... | 115 | +| 8.7.3.3.2 | UE-initiated Location Information Delivery Procedure..... | 116 | +| 8.8 | Motion sensor positioning method..... | 116 | +| 8.8.1 | General..... | 116 | +| 8.8.2 | Information to be transferred between NG-RAN/5GC Elements..... | 116 | +| 8.8.2.1 | General..... | 116 | +| 8.8.2.2 | Information that may be transferred from the UE to LMF..... | 116 | +| 8.8.2.2.0 | General..... | 116 | +| 8.8.2.2.1 | UE-assisted, UE-based, Standalone mode..... | 117 | +| 8.8.2.2.2 | UE Displacement and Movement Information..... | 117 | +| 8.8.2.3 | Information that may be transferred from the LMF to the UE..... | 117 | +| 8.8.3 | Motion Sensors Location Information Transfer Procedure..... | 117 | +| 8.8.3.1 | General..... | 117 | +| 8.8.3.2 | LMF initiated Location Information Transfer Procedure..... | 117 | + +| | | | +|----------------|-----------------------------------------------------------------------|-----| +| 8.8.3.3 | UE-initiated Location Information Delivery Procedure..... | 117 | +| 8.9 | NR Enhanced cell ID positioning methods..... | 118 | +| 8.9.1 | General..... | 118 | +| 8.9.2 | Information to be transferred between NG-RAN/5GC Elements..... | 118 | +| 8.9.2.0 | General..... | 118 | +| 8.9.2.1 | Information that may be transferred from the LMF to UE..... | 119 | +| 8.9.2.2 | Information that may be transferred from the UE to LMF..... | 119 | +| 8.9.2.3 | Information that may be transferred from the gNB to LMF..... | 119 | +| 8.9.3 | Downlink NR E-CID Positioning Procedures..... | 119 | +| 8.9.3.0 | General..... | 119 | +| 8.9.3.1 | Capability Transfer Procedure..... | 119 | +| 8.9.3.2 | Assistance Data Transfer Procedure..... | 119 | +| 8.9.3.3 | Location Information Transfer Procedure..... | 120 | +| 8.9.3.3.0 | General..... | 120 | +| 8.9.3.3.1 | LMF-initiated Location Information Transfer from UE..... | 120 | +| 8.9.3.3.2 | UE-initiated Location Information Delivery procedure..... | 120 | +| 8.9.4 | Uplink NR E-CID Positioning Procedures..... | 121 | +| 8.9.4.0 | General..... | 121 | +| 8.9.4.1 | Capability Transfer Procedure..... | 121 | +| 8.9.4.2 | Assistance Data Transfer Procedure..... | 121 | +| 8.9.4.3 | Location Information Transfer Procedure..... | 121 | +| 8.10 | Multi-RTT positioning..... | 122 | +| 8.10.1 | General..... | 122 | +| 8.10.2 | Information to be transferred between NG-RAN/5GC Elements..... | 122 | +| 8.10.2.0 | General..... | 122 | +| 8.10.2.1 | Information that may be transferred from the LMF to UE..... | 122 | +| 8.10.2.2 | Information that may be transferred from the UE to LMF..... | 123 | +| 8.10.2.3 | Information that may be transferred from the gNB to LMF..... | 123 | +| 8.10.2.4 | Information that may be transferred from the LMF to gNBs..... | 124 | +| 8.10.3 | Multi-RTT Positioning Procedures..... | 125 | +| 8.10.3.0 | General..... | 125 | +| 8.10.3.1 | Procedures between LMF and UE..... | 125 | +| 8.10.3.1.1 | Capability Transfer Procedure..... | 125 | +| 8.10.3.1.2 | Assistance Data Transfer Procedure..... | 125 | +| 8.10.3.1.2.1 | Assistance Data Transfer between LMF and UE..... | 125 | +| 8.10.3.1.2.1.0 | General..... | 125 | +| 8.10.3.1.2.1.1 | LMF initiated Assistance Data Delivery..... | 126 | +| 8.10.3.1.2.1.2 | UE initiated Assistance Data Transfer..... | 126 | +| 8.10.3.1.3 | Location Information Transfer Procedure..... | 127 | +| 8.10.3.1.3.0 | General..... | 127 | +| 8.10.3.1.3.1 | LMF-initiated Location Information Transfer Procedure..... | 127 | +| 8.10.3.1.3.2 | UE-initiated Location Information Delivery procedure..... | 127 | +| 8.10.3.2 | Procedures between LMF and gNB..... | 128 | +| 8.10.3.2.1 | Assistance Data Delivery between LMF and gNB..... | 128 | +| 8.10.3.2.2 | Location Information Transfer/Assistance Data Transfer Procedure..... | 129 | +| 8.10.3.2.3 | Positioning Activation/Deactivation Procedure..... | 130 | +| 8.10.4 | Sequence of Procedure for Multi-RTT positioning..... | 131 | +| 8.11 | DL-AoD positioning..... | 133 | +| 8.11.1 | General..... | 133 | +| 8.11.2 | Information to be transferred between NG-RAN/5GC Elements..... | 133 | +| 8.11.2.0 | General..... | 133 | +| 8.11.2.1 | Information that may be transferred from the LMF to UE..... | 134 | +| 8.11.2.1.0 | General..... | 134 | +| 8.11.2.1.1 | Mapping of integrity parameters..... | 134 | +| 8.11.2.2 | Information that may be transferred from the UE to LMF..... | 135 | +| 8.11.2.3 | Information that may be transferred from the gNB to LMF..... | 135 | +| 8.11.3 | DL-AoD Positioning Procedures..... | 135 | +| 8.11.3.0 | General..... | 135 | +| 8.11.3.1 | Procedures between LMF and UE..... | 135 | +| 8.11.3.1.1 | Capability Transfer Procedure..... | 135 | +| 8.11.3.1.2 | Assistance Data Transfer Procedure..... | 135 | + +| | | | +|--------------|-------------------------------------------------------------------------|-----| +| 8.11.3.1.2.0 | General..... | 135 | +| 8.11.3.1.2.1 | LMF initiated Assistance Data Delivery..... | 136 | +| 8.11.3.1.2.2 | UE initiated Assistance Data Transfer..... | 136 | +| 8.11.3.1.3 | Location Information Transfer Procedure..... | 137 | +| 8.11.3.1.3.0 | General..... | 137 | +| 8.11.3.1.3.1 | LMF-initiated Location Information Transfer Procedure..... | 137 | +| 8.11.3.1.3.2 | UE-initiated Location Information Delivery procedure..... | 137 | +| 8.11.3.2 | Procedures between LMF and gNB..... | 138 | +| 8.11.3.2.1 | Assistance Data Delivery procedure..... | 138 | +| 8.11.3.2.1.0 | General..... | 138 | +| 8.11.3.2.1.1 | LMF-initiated assistance data delivery to the LMF..... | 138 | +| 8.12 | DL-TDOA positioning..... | 139 | +| 8.12.1 | General..... | 139 | +| 8.12.2 | Information to be transferred between NG-RAN/5GC Elements..... | 139 | +| 8.12.2.0 | General..... | 139 | +| 8.12.2.1 | Information that may be transferred from the LMF to UE..... | 139 | +| 8.12.2.1.0 | General..... | 139 | +| 8.12.2.1.1 | Mapping of integrity parameters..... | 139 | +| 8.12.2.2 | Information that may be transferred from the UE to LMF..... | 140 | +| 8.12.2.2.0 | General..... | 140 | +| 8.12.2.3 | Information that may be transferred from the gNB to LMF..... | 140 | +| 8.12.2.3.0 | General..... | 140 | +| 8.12.3 | DL-TDOA Positioning Procedures..... | 141 | +| 8.12.3.0 | General..... | 141 | +| 8.12.3.1 | Procedures between LMF and UE..... | 141 | +| 8.12.3.1.1 | Capability Transfer Procedure..... | 141 | +| 8.12.3.1.2 | Assistance Data Transfer Procedure..... | 141 | +| 8.12.3.1.2.0 | General..... | 141 | +| 8.12.3.1.2.1 | LMF initiated Assistance Data Delivery..... | 141 | +| 8.12.3.1.2.2 | UE initiated Assistance Data Transfer..... | 143 | +| 8.12.3.1.3 | Location Information Transfer Procedure..... | 144 | +| 8.12.3.1.3.0 | General..... | 144 | +| 8.12.3.1.3.1 | LMF-initiated Location Information Transfer Procedure..... | 144 | +| 8.12.3.1.3.2 | UE-initiated Location Information Delivery procedure..... | 145 | +| 8.12.3.2 | Procedures between LMF and gNB..... | 146 | +| 8.12.3.2.1 | Assistance Data Delivery procedure..... | 146 | +| 8.12.3.2.1.0 | General..... | 146 | +| 8.12.3.2.1.1 | LMF-initiated assistance data delivery to the LMF..... | 146 | +| 8.13 | UL-TDOA positioning..... | 146 | +| 8.13.1 | General..... | 146 | +| 8.13.2 | Information to be transferred between NG-RAN/5GC Elements..... | 147 | +| 8.13.2.0 | Assistance Data that may be transferred from the gNB to the LMF..... | 147 | +| 8.13.2.1 | Configuration Data that may be transferred from the gNB to the LMF..... | 147 | +| 8.13.2.2 | Location Information that may be transferred from the gNBs to LMF..... | 147 | +| 8.13.2.3 | Information that may be transferred from the LMF to gNBs..... | 147 | +| 8.13.3 | UL-TDOA Positioning Procedures..... | 149 | +| 8.13.3.0 | General..... | 149 | +| 8.13.3.1 | Capability Transfer Procedure..... | 149 | +| 8.13.3.2 | Assistance Data Transfer Procedure..... | 149 | +| 8.13.3.2.1 | Assistance Data Delivery between LMF and gNB..... | 149 | +| 8.13.3.3 | Location Information Transfer/Assistance Data Transfer Procedure..... | 150 | +| 8.13.3.3a | Positioning Activation/Deactivation Procedure..... | 151 | +| 8.13.3.4 | Sequence of Procedure for UL-TDOA positioning..... | 152 | +| 8.14 | UL-AoA positioning..... | 153 | +| 8.14.1 | General..... | 153 | +| 8.14.2 | Information to be transferred between NG-RAN/5GC Elements..... | 153 | +| 8.14.2.0 | Assistance Data that may be transferred from the gNB to the LMF..... | 153 | +| 8.14.2.1 | Configuration Data that may be transferred from the gNB to the LMF..... | 154 | +| 8.14.2.2 | Location Information that may be transferred from the gNBs to LMF..... | 154 | +| 8.14.2.3 | Information that may be transferred from the LMF to gNB..... | 154 | +| 8.14.3 | UL-AoA Positioning Procedures..... | 156 | + +| | | | +|---------------------------------------------------------|-----------------------------------------------------------------------|------------| +| 8.14.3.0 | General..... | 156 | +| 8.14.3.1 | Capability Transfer Procedure..... | 156 | +| 8.14.3.2 | Assistance Data Transfer Procedure..... | 156 | +| 8.14.3.2.1 | Assistance Data Delivery between LMF and gNB..... | 156 | +| 8.14.3.3 | Location Information Transfer/Assistance Data Transfer Procedure..... | 157 | +| 8.14.3.3a | Positioning Activation/Deactivation Procedure..... | 158 | +| 8.14.3.4 | Sequence of Procedure for UL-AoA positioning..... | 159 | +| 8.15 | SL positioning and ranging..... | 160 | +| 8.15.1 | SL-PRS transmission and reception..... | 160 | +| 8.15.2 | SL-RTT positioning..... | 160 | +| 8.15.2.1 | General..... | 160 | +| 8.15.2.2 | SL-RTT positioning procedures..... | 161 | +| 8.15.2.2.1 | Capability transfer procedure..... | 161 | +| 8.15.2.2.2 | Assistance Data transfer procedure..... | 161 | +| 8.15.2.2.3 | Location Information transfer procedure..... | 162 | +| 8.15.3 | SL-AoA positioning..... | 163 | +| 8.15.3.1 | General..... | 163 | +| 8.15.3.2 | SL-AoA positioning procedures..... | 163 | +| 8.15.3.2.1 | Capability transfer procedure..... | 163 | +| 8.15.3.2.2 | Assistance Data transfer procedure..... | 163 | +| 8.15.3.2.3 | Location Information transfer procedure..... | 164 | +| 8.15.4 | SL-TDOA positioning..... | 166 | +| 8.15.4.1 | General..... | 166 | +| 8.15.4.2 | SL-TDOA positioning procedures..... | 166 | +| 8.15.4.2.1 | Capability transfer procedure..... | 166 | +| 8.15.4.2.2 | Assistance Data transfer procedure..... | 166 | +| 8.15.4.2.3 | Location Information transfer procedure..... | 167 | +| 8.15.5 | SL-TOA positioning..... | 168 | +| 8.15.5.1 | General..... | 168 | +| 8.15.5.2 | SL-TOA positioning procedures..... | 168 | +| 8.15.5.2.1 | Capability transfer procedure..... | 168 | +| 8.15.5.2.2 | Assistance Data transfer procedure..... | 168 | +| 8.15.5.2.3 | Location Information transfer procedure..... | 169 | +| Annex A (informative): Use of LPP with SUPL..... | | 172 | +| A.1 | SUPL 2.0 Positioning Methods and Positioning Protocols..... | 172 | +| A.2 | SUPL 2.0 and NR Architecture..... | 174 | +| A.3 | LPP session procedures using SUPL..... | 174 | +| A.4 | Procedures combining C-plane and U-plane operations..... | 175 | +| Annex B (informative): Change history..... | | 177 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document specifies the stage 2 of the UE Positioning function of NG-RAN which provides the mechanisms to support or assist the calculation of the geographical position of a UE. UE position knowledge can be used, for example, in support of Radio Resource Management functions, as well as location-based services for operators, subscribers, and third-party service providers. The purpose of this stage 2 specification is to define the NG-RAN UE Positioning architecture, functional entities and operations to support positioning methods. This description is confined to the NG-RAN Access Stratum. It does not define or describe how the results of the UE position calculation can be utilised in the Core Network (e.g., LCS) or in NG-RAN (e.g., RRM). + +UE Positioning may be considered as a network-provided enabling technology consisting of standardised service capabilities that enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology is outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included. + +This stage 2 specification covers the NG-RAN positioning methods, state descriptions, and message flows to support UE Positioning. + +This stage 2 specification also covers ranging and sidelink positioning in in-coverage and out-of-coverage of NG-RAN using NR PC5 interface. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501 "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 22.071: "Location Services (LCS); Service description, Stage 1". +- [4] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [5] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. +- [6] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005. +- [7] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, September 4, 2008. +- [8] Galileo OS Signal in Space ICD (OS SIS ICD), Draft 0, Galileo Joint Undertaking, May 23rd, 2006. +- [9] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002. +- [10] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008. +- [11] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. + +- [12] RTCM 10402.3, RTCM Recommended Standards for Differential GNSS Service (v.2.3), August 20, 2001. +- [13] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [14] 3GPP TS 38.331: "NR Radio Resource Control (RRC) protocol specification". +- [15] OMA-AD-SUPL-V2\_0: "Secure User Plane Location Architecture Approved Version 2.0". +- [16] OMA-TS-ULP-V2\_0\_6: "UserPlane Location Protocol Approved Version 2.0.6". +- [17] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer – Measurements". +- [18] 3GPP TS 36.302: "Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by the physical layer". +- [19] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [20] BDS-SIS-ICD-B1I-3.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1I (Version 3.0)", February, 2019. +- [21] IEEE 802.11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications" +- [22] Bluetooth Special Interest Group: "Bluetooth Core Specification v4.2", December 2014. +- [23] ATIS-0500027: "Recommendations for Establishing Wide Scale Indoor Location Performance", May 2015. +- [24] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation". +- [25] 3GPP TS 36.305: "Stage 2 functional specification of User Equipment (UE) positioning in E-UTRA". +- [26] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [27] 3GPP TS 38.455: "NG-RAN; NR Positioning Protocol A (NRPPa)". +- [28] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3". +- [29] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [30] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [31] RTCM 10403.3, "RTCM Recommended Standards for Differential GNSS Services (v.3.3)", October 7, 2016. +- [32] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [33] 3GPP TS 29.572: "Location Management Services; Stage 3". +- [34] BDS-SIS-ICD-B1C-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1C (Version 1.0)", December, 2017 +- [35] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [36] IS-QZSS-L6-001, Quasi-Zenith Satellite System Interface Specification – Centimetre Level Augmentation Service, Cabinet Office, November 5, 2018. +- [37] 3GPP TS 38.215: "NR; Physical layer – Measurements". +- [38] 3GPP TS 38.401: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description". + +- [39] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [40] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [41] 3GPP TS 24.571: "Control plane Location Services (LCS) procedures". +- [42] 3GPP TS 37.355: "Technical Specification Group Radio Access Network; LTE Positioning Protocol (LPP)". +- [43] IRNSS Signal-In-Space (SPS) Interface Control Document (ICD) for standard positioning service version 1.1, August 2017. +- [44] BDS-SIS-ICD-B2a-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B2a (Version 1.0)", December, 2017. +- [45] BDS-SIS-ICD-B3I-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B3I (Version 1.0)", February, 2018. +- [46] 3GPP TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning". +- [47] 3GPP TS 38.355: "NR; Sidelink Positioning Protocol (SLPP); Protocol specification". +- [48] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [49] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [50] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [51] Bluetooth Special Interest Group: "Bluetooth Core Specification v5.4", February 2023. +- [52] 3GPP TS 38.300: "NR; NR and NR-RAN Overall Description; Stage 2". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +As used in this document, the suffixes "-based" and "-assisted" refer respectively to the node that is responsible for making the positioning calculation (and which may also provide measurements) and a node that provides measurements (but which does not make the positioning calculation). Thus, an operation in which measurements are provided by the UE to the LMF to be used in the computation of a position estimate is described as "UE-assisted" (and could also be called "LMF-based"), while one in which the UE computes its own position is described as "UE-based". For sidelink positioning, an operation in which measurements are provided by a SL Target UE to a server (SL Server UE or LMF) to be used in the computation of a position estimate is described as "SL Target UE-assisted" (and could also be called "server-based"), while one in which the SL Target UE computes its own position is described as "SL Target UE-based". + +**Alert Limit (AL):** The maximum allowable positioning error for the purpose of integrity. If the positioning error is beyond this limit, the integrity results of the calculated location may not meet the integrity requirement. + +**Mobile TRP:** a TRP belonging to a mobile IAB-node. + +**Positioning integrity:** A measure of the trust in the accuracy of the position-related data and the ability to provide associated alerts. + +**Pre-configured assistance data:** Refers to the DL-PRS assistance data (with associated validity criteria) that can be provided to the UE (before or during an ongoing LPP positioning session), to be then utilized for potential positioning measurements at a future time (e.g. for deferred MT-LR). Pre-configured DL-PRS assistance data may consist of multiple instances, where each instance is applicable to a different area within the network. + +**Protection Level (PL):** A statistical upper-bound of the Positioning Error (PE) that ensures that, the probability per unit of time of the true error being greater than the AL and the PL being less than or equal to the AL, for longer than the TTA, is less than the TIR, i.e., the PL satisfies the following inequality: + +$$\text{Prob per unit of time } [(PE > AL) \& (PL \leq AL)] \text{ for longer than } TTA < TIR$$ + +When the PL bounds the positioning error in the horizontal plane or on the vertical axis then it is called Horizontal Protection Level (HPL) or Vertical Protection Level (VPL) respectively. + +A specific equation for the PL is not specified as this is implementation-defined. For the PL to be considered valid, it must simply satisfy the inequality above. + +NOTE 1: the PL inequality is valid for all values of the AL. + +NOTE 2: the TIR may correspond to the achievable TIR in the case that the requested TIR cannot be satisfied. + +**PRS-only TP:** A TP which only transmits PRS, DL-PRS signals and is not associated with a cell. + +**PRS Processing Window (PPW):** The PRS Processing Window is configured by the network to a UE for NR DL-PRS measurements without measurement gap. + +**Ranging/SL Positioning Protocol (RSPP):** RSPP comprises SLPP messages and Supplementary Services messages according to TS 23.586 [46]. + +**Ranging:** Refers to the determination of the distance between two UEs or more UEs and/or the direction of one UE from another UE via sidelink interface. + +**Reception Point (RP):** A set of geographically co-located receive antennas (e.g. antenna array (with one or more antenna elements)) for one cell, part of one cell or one UL-SRS-only RP. Reception Points can include base station (ng-eNB or gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a UL-SRS-only RP, etc. One cell can include one or multiple reception points. For a homogeneous deployment, each reception point may correspond to one cell. + +**Relative Position:** An estimate of the UE position relative to other network elements or relative to other UEs. + +**Rx Time Delay:** From a signal reception perspective, there will be a time delay from the time when the RF signal arrives at the Rx antenna to the time when the signal is digitized and time-stamped at the baseband. + +**Rx Timing Error:** Result of Rx time delay involved in the reception of a signal before reporting measurements that are obtained from the signal. It is the uncalibrated Rx time delay, or the remaining delay after the UE/TRP internal calibration/compensation of the Rx time delay, involved in the reception of the DL-PRS/UL SRS signals. The calibration/compensation may also include the calibration/compensation of the relative time delay between different RF chains in the same UE/TRP and may also possibly consider the offset of the Rx antenna phase centre to the physical antenna centre. + +**Sidelink Positioning:** A functionality which determines geographical or relative location and possibly velocity using sidelink measurements. + +**SL Anchor UE:** A UE, supporting positioning of target UE, e.g. by transmitting and/or receiving reference signals for positioning, providing positioning-related information, etc. using Sidelink. + +**SL Server UE:** A UE offering position method determination, assistance data distribution and/or location calculation functionalities for sidelink positioning and ranging based services. It interacts with other UEs over PC5 as necessary in order to determine a ranging/SL position method, distribute assistance data and calculate the location of the target UE. A Target UE or SL Anchor UE can act as SL Server UE if any of the functionalities is supported. + +**SL Target UE:** A UE whose distance, direction and/or position is measured with the support from one or multiple SL Anchor UEs using sidelink. + +**SRS-only RP:** An RP which only receives UL-SRS signals and is not associated with a cell. + +**Transmission Point (TP):** A set of geographically co-located transmit antennas (e.g. antenna array (with one or more antenna elements)) for one cell, part of one cell or one DL-PRS-only TP. Transmission Points can include base station (ng-eNB or gNB) antennas, remote radio heads, a remote antenna of a base station, an antenna of a DL-PRS-only TP, etc. One cell can include one or multiple transmission points. For a homogeneous deployment, each transmission point may correspond to one cell. + +**Transmission-Reception Point (TRP):** A set of geographically co-located antennas (e.g. antenna array (with one or more antenna elements)) supporting TP and/or RP functionality. + +**TRP Rx 'Timing Error Group' (TRP Rx TEG):** Rx timing errors, associated with TRP reporting of one or more UL measurements, that are within a certain margin. + +**TRP RxTx 'Timing Error Group' (TRP RxTx TEG):** Rx timing errors and Tx timing errors, associated with TRP reporting of one or more gNB Rx-Tx time difference measurements, which have the 'Rx timing errors+Tx timing errors' differences within a certain margin. + +**TRP Tx 'Timing Error Troup' (TRP Tx TEG):** Tx timing errors, associated with TRP transmissions on one or more DL-PRS resources, that are within a certain margin. + +**Tx Time Delay:** From a signal transmission perspective, the time delay from the time when the digital signal is generated at baseband to the time when the RF signal is transmitted from the Tx antenna. + +**Tx Timing Error:** Result of Tx time delay involved in the transmission of a signal. It is the uncalibrated Tx time delay, or the remaining delay after the TRP/UE internal calibration/compensation of the Tx time delay, involved in the transmission of the DL-PRS/UL SRS signals. The calibration/compensation may also include the calibration/compensation of the relative time delay between different RF chains in the same TRP/UE and may also possibly consider the offset of the Tx antenna phase centre to the physical antenna centre. + +**U2N Relay UE:** A UE that provides functionality to support connectivity to the network for U2N Remote UE(s). + +**U2N Remote UE:** A UE that communicates with the network via a U2N Relay UE. + +**UE Rx 'Timing Error Group' (UE Rx TEG):** Rx timing errors, associated with UE reporting of one or more DL measurements (RSTD), that are within a certain margin. + +**UE RxTx 'Timing Error Group' (UE RxTx TEG):** Rx timing errors and Tx timing errors, associated with UE reporting of one or more UE Rx-Tx time difference measurements, which have the 'Rx timing errors+Tx timing errors' differences within a certain margin. + +**UE Tx 'Timing Error Group' (UE Tx TEG):** Tx timing errors, associated with UE transmissions on one or more UL SRS resources for positioning purpose, that are within a certain margin. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----------|----------------------------------------------------| +| 5GC | 5G Core Network | +| 5GS | 5G System | +| A-AoA | Azimuth-Angle of Arrival | +| ADR | Accumulated Delta Range | +| AL | Alert Limit | +| AoA | Angle of Arrival | +| AP | Access Point | +| APC | Antenna Phase Center | +| ARP | Antenna Reference Point | +| BDS | BeiDou Navigation Satellite System | +| BSSID | Basic Service Set Identifier | +| CID | Cell-ID (positioning method) | +| CLAS | Centimetre Level Augmentation Service | +| DL-AoD | Downlink Angle-of-Departure | +| DL-PRS | Downlink Positioning Reference Signal | +| DL-RSCP | Downlink Reference Signal Carrier Phase | +| DL-RSCPD | Downlink Reference Signal Carrier Phase Difference | +| DL-TDOA | Downlink Time Difference Of Arrival | +| DNU | Do Not Use | +| DRX | Discontinuous Reception | +| E-SMLC | Enhanced Serving Mobile Location Centre | + +| | | +|--------------|----------------------------------------------------------------------------------------------| +| E-CID | Enhanced Cell-ID (positioning method) | +| ECEF | Earth-Centered, Earth-Fixed | +| ECI | Earth-Centered-Inertial | +| eDRX | Extended Discontinuous Reception | +| EGNOS | European Geostationary Navigation Overlay Service | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| FDMA | Frequency Division Multiple Access | +| FKP | Flächenkorrekturparameter (Engl: Area Correction Parameters) | +| GAGAN | GPS Aided Geo Augmented Navigation | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GMLC | Gateway Mobile Location Centre | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| GRS80 | Geodetic Reference System 1980 | +| HESSID | Homogeneous Extended Service Set Identifier | +| IOD | Issue of Data | +| LCS | LoCation Services | +| LMF | Location Management Function | +| LPP | LTE Positioning Protocol | +| MAC | Master Auxiliary Concept | +| MBS | Metropolitan Beacon System | +| MO-LR | Mobile Originated Location Request | +| MT-LR | Mobile Terminated Location Request | +| Multi-RTT | Multi-Round Trip Time | +| NavIC | NAVigation with Indian Constellation | +| NG-C | NG Control plane | +| NG-AP | NG Application Protocol | +| NI-LR | Network Induced Location Request | +| N-RTK | Network – Real-Time Kinematic | +| NRPPa | NR Positioning Protocol A | +| NTN | Non-Terrestrial Network | +| OTDOA | Observed Time Difference Of Arrival | +| PCO | Phase Center Offset | +| PCV | Phase Center Variation | +| PDU | Protocol Data Unit | +| posSI | Positioning System Information | +| posSIB | Positioning SIB | +| PPP | Precise Point Positioning | +| PPP-RTK | Precise Point Positioning – Real-Time Kinematic | +| PRS | Positioning Reference Signal (for E-UTRA) | +| PRU | Positioning Reference Unit | +| QZSS | Quasi-Zenith Satellite System | +| RP | Reception Point | +| RRM | Radio Resource Management | +| RSPP | Ranging/SL Positioning Protocol | +| RSRP | Reference Signal Received Power | +| RSRPP | Reference Signal Received Path Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| RSTD | Reference Signal Time Difference | +| RTK | Real-Time Kinematic | +| SBAS | Space Based Augmentation System | +| SDT | Small Data Transmission | +| SET | SUPL Enabled Terminal | +| SIB | System Information Block | +| SL | Sidelink | +| SL-PRS | Sidelink Positioning Reference Signal | +| SL-PRS-RSRP | Sidelink PRS Reference Signal Received Power | +| SL-PRS-RSRPP | Sidelink PRS Reference Signal Received Path Power | +| SL-RSTD | Sidelink Reference Signal Time Difference | +| SL-RTOA | Sidelink Relative Time of Arrival | + +| | | +|------------------|---------------------------------------| +| SLP | SUPL Location Platform | +| SLPP | Sidelink Positioning Protocol | +| SP | Semi-Persistent | +| SRS | Sounding Reference Signal | +| SSB | Synchronization Signal Block | +| SSID | Service Set Identifier | +| SSR | State Space Representation | +| STEC | Slant TEC | +| SUPL | Secure User Plane Location | +| T ADV | Timing Advance | +| TBS | Terrestrial Beacon System | +| TEC | Total Electron Content | +| TEG | Timing Error Group | +| TP | Transmission Point | +| TRP | Transmission-Reception Point | +| TTA | Time To Alert | +| TxTEG | Tx Timing Error Group | +| UE | User Equipment | +| UL-AoA | Uplink Angle of Arrival | +| UL-RSCP | Uplink Reference Signal Carrier Phase | +| UL-RTOA | Uplink Relative Time of Arrival | +| UL-SRS | Uplink Sounding Reference Signal | +| UL-TDOA | Uplink Time Difference of Arrival | +| URA | User Range Accuracy | +| WAAS | Wide Area Augmentation System | +| WGS-84 | World Geodetic System 1984 | +| WLAN | Wireless Local Area Network | +| Z-AoA | Zenith Angles of Arrival | + +--- + +## 4 Main concepts and requirements + +### 4.1 Assumptions and Generalities + +The stage 1 description of LCS at the service level is provided in TS 22.071 [3]; the stage 2 LCS functional description, including the LCS system architecture and message flows, is provided in TS 23.501 [2], TS 23.502 [26] and TS 23.273 [35]; the stage 2 including the architectural enhancements and procedures to support ranging based services and sidelink positioning in the 5G System is provided in TS 23.586 [46] and TS 23.273 [35]. + +Positioning functionality provides a means to determine the geographic position and/or velocity of the UE based on measuring radio signals. The position information may be requested by and reported to a client (e.g., an application) associated with the UE, or by a client within or attached to the core network. The position information shall be reported in standard formats, such as those for cell-based or geographical co-ordinates, together with the estimated errors (uncertainty) of the position and velocity of the UE and, if available, the positioning method (or the list of the methods) used to obtain the position estimate. + +Restrictions on the geographic shape encoded within the 'position information' parameter may exist for certain LCS client types. The 5GS, including NG-RAN, shall comply with any shape restrictions defined in 5GS and, in a particular country, with any shape restrictions defined for a specific LCS client type in relevant national standards. For example, in the US, national standard J-STD-036-C-2 restricts the geographic shape for an emergency services LCS client to minimally either an "ellipsoid point" or an "ellipsoid point with uncertainty circle" as defined in TS 23.032 [4]. + +It shall be possible for the majority of the UEs within a network to use the LCS feature without compromising the radio transmission or signalling capabilities of the NG-RAN. + +The uncertainty of the position measurement shall be network-implementation-dependent, at the choice of the network operator. The uncertainty may vary between networks as well as from one area within a network to another. The uncertainty may be hundreds of metres in some areas and only a few metres in others. In the event that a particular position measurement is provided through a UE-assisted process, the uncertainty may also depend on the capabilities of + +the UE. In some jurisdictions, there is a regulatory requirement for location service accuracy that is part of an emergency service. Further details of the accuracy requirements can be found in TS 22.071 [3]. + +The uncertainty of the position information is dependent on the method used, the position of the UE within the coverage area and the activity of the UE. Several design options of the NG-RAN system (e.g., size of cell, adaptive antenna technique, pathloss estimation, timing accuracy, ng-eNB and gNB surveys) shall allow the network operator to choose a suitable and cost-effective UE positioning method for their market. + +There are many different possible uses for the positioning information. The positioning functions may be used internally by the 5GS, by value-added network services, by the UE itself or through the network, and by "third party" services. The feature may also be used by an emergency service (which may be mandated or "value-added"), but the location service is not exclusively for emergencies. + +Design of the NG-RAN positioning capability as documented in this specification includes position methods, protocols and procedures that are either adapted from capabilities already supported for E-UTRAN, UTRAN and GERAN, or created separately from first principles. In contrast to GERAN and UTRAN but similarly to E-UTRAN, the NG-RAN positioning capabilities are intended to be forward compatible to other access types and other position methods, in an effort to reduce the amount of additional positioning support needed in the future. This goal also extends to user plane location solutions such as OMA SUPL ([15], [16]), for which NG-RAN positioning capabilities are intended to be compatible where appropriate. + +As a basis for the operation of UE Positioning in NG-RAN, the following assumptions apply: + +- both TDD and FDD will be supported; +- the provision of the UE Positioning function in NG-RAN and 5GC is optional through support of the specified method(s) in the ng-eNB, gNB and the LMF; +- UE Positioning is applicable to any target UE, whether or not the UE supports LCS, but with restrictions on the use of certain positioning methods depending on UE capability (e.g. as defined within the LPP protocol); +- the positioning information may be used for internal system operations to improve system performance; +- the UE Positioning architecture and functions shall include the option to accommodate several techniques of measurement and processing to ensure evolution to follow changing service requirements and to take advantage of advancing technology; +- the UE Positioning architecture and functions include the option of using sidelink measurements to obtain absolute position, relative position, or ranging information. + +## 4.2 Role of UE Positioning Methods + +The NG-RAN may utilise one or more positioning methods in order to determine the position of an UE. + +Positioning the UE involves two main steps: + +- signal measurements; and +- position estimate and optional velocity computation based on the measurements. + +The signal measurements may be made by the UE or by the serving ng-eNB or gNB. The basic signals measured for terrestrial position methods are typically the LTE or NR radio transmissions; however, other methods may make use of other transmissions such as general radio navigation signals including those from Global Navigation Satellites Systems (GNSSs). + +The positioning function should not be limited to a single method or measurement. That is, it should be capable of utilising other standard methods and measurements, as such methods and measurements are available and appropriate, to meet the required service needs of the location service client. This additional information could consist of readily available E-UTRAN or NG-RAN measurements. + +The position estimate computation may be made by the UE or by the LMF. + +UE positioning methods using sidelink may be used to obtain absolute position, relative position, or ranging information when the UE is inside or outside NG-RAN coverage. + +## 4.3 Standard UE Positioning Methods + +### 4.3.1 Introduction + +The standard positioning methods supported for NG-RAN access are: + +- network-assisted GNSS methods; +- observed time difference of arrival (OTDOA) positioning based on LTE signals; +- enhanced cell ID methods based on LTE signals; +- WLAN positioning; +- Bluetooth positioning; +- terrestrial beacon system (TBS) positioning; +- sensor based methods: + - barometric Pressure Sensor; + - motion sensor. +- NR enhanced cell ID methods (NR E-CID) based on NR signals; +- Multi-Round Trip Time Positioning (Multi-RTT based on NR signals); +- Downlink Angle-of-Departure (DL-AoD) based on NR signals; +- Downlink Time Difference of Arrival (DL-TDOA) based on NR signals; +- Uplink Time Difference of Arrival (UL-TDOA) based on NR signals; +- Uplink Angle-of-Arrival (UL-AoA), including A-AoA and Z-AoA based on NR signals; +- SL positioning and Ranging based on sidelink signals, incl.: + - Sidelink Round Trip Time Positioning (SL-RTT); + - Sidelink Angle-of-Arrival (SL-AoA); + - Sidelink Time Difference of Arrival (SL-TDOA); + - Sidelink Time of Arrival (SL-TOA). + +Hybrid positioning using multiple methods from the list of positioning methods above is also supported. + +Standalone mode (e.g. autonomous, without network assistance) using one or more methods from the list of positioning methods above is also supported. + +These positioning methods (except SL positioning and ranging methods) may be supported in UE-based, UE-assisted/LMF-based, and NG-RAN node assisted versions. Table 4.3.1-1 indicates which of these versions are supported in this version of the specification for the standardised positioning methods. + +**Table 4.3.1-1: Supported versions of UE positioning methods** + +| Method | UE-based | UE-assisted,
LMF-based | NG-RAN node
assisted | SUPL Note 8 | +|---------------------------------------------------------------------------------------------|----------|---------------------------|-------------------------|------------------------| +| A-GNSS | Yes | Yes | No | Yes | +| OTDOA Note 1, Note 2 | No | Yes | No | Yes | +| E-CID Note 4, Note 7 | No | Yes | Yes | Yes for E-UTRA | +| Sensor | Yes | Yes | No | No | +| WLAN | Yes | Yes | No | Yes | +| Bluetooth | No | Yes | No | No | +| TBS Note 5 | Yes | Yes | No | Yes (MBS) | +| DL-TDOA | Yes | Yes | No | Yes | +| DL-AoD | Yes | Yes | No | Yes | +| Multi-RTT | No | Yes | Yes | Yes | +| NR E-CID | No | Yes | Yes | Yes (DL NR E-CID) | +| UL-TDOA | No | No | Yes | Yes | +| UL-AoA | No | No | Yes | Yes | +| NOTE 1: This includes TBS positioning based on PRS signals. | | | | | +| NOTE 2: In this version of the specification only OTDOA based on LTE signals is supported. | | | | | +| NOTE 3: Void | | | | | +| NOTE 4: This includes Cell-ID for NR method when UE is served by gNB. | | | | | +| NOTE 5: In this version of the specification only for TBS positioning based on MBS signals. | | | | | +| NOTE 6: Void | | | | | +| NOTE 7: Enhanced Cell ID based on LTE signals. | | | | | +| NOTE 8: This shows whether the positioning method is supported by SUPL ULP [16]. | | | | | + +Sensor, WLAN, Bluetooth, and TBS positioning methods based on MBS signals are also supported in standalone mode, as described in the corresponding clauses. + +The SL positioning and ranging methods may be supported in SL-Target UE-based or SL-Target UE-assisted/server-based mode, where "server" may be a SL Server UE or LMF. Table 4.3.1-2 indicates which of these versions are supported in this version of the specification for the SL positioning and ranging methods. + +**Table 4.3.1-2: Supported versions of SL positioning and ranging methods.** + +| Method | SL-Target UE-based | SL-Target UE-assisted,
server-based | +|-----------------------------------------------------------------------------|--------------------|----------------------------------------| +| SL-RTT Note 1 | Yes | Yes | +| SL-AoA Note 2 | Yes | Yes | +| SL-TDOA | Yes | Yes | +| SL-TOA | Yes | Yes | +| NOTE 1: The SL-RTT method may also be used for ranging between UEs. | | | +| NOTE 2: The SL-AoA method may also be used to obtain direction between UEs. | | | + +## 4.3.2 Network-assisted GNSS methods + +These methods make use of UEs that are equipped with radio receivers capable of receiving GNSS signals. In 3GPP specifications the term GNSS encompasses both global and regional/augmentation navigation satellite systems. + +Examples of global navigation satellite systems include GPS, Modernized GPS, Galileo, GLONASS, and BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include Quasi Zenith Satellite System (QZSS), and NAVigation with Indian Constellation (NavIC), while the many augmentation systems, listed in 8.1.1, are classified under the generic term of Space Based Augmentation Systems (SBAS) and provide regional augmentation services. + +In this concept, different GNSSs (e.g. GPS, Galileo, etc.) can be used separately or in combination to determine the location of a UE. + +The operation of the network-assisted GNSS methods is described in clause 8.1. + +### 4.3.3 OTDOA positioning + +The OTDOA positioning method makes use of the measured timing of downlink signals received from multiple TPs, comprising eNBs, ng-eNBs and PRS-only TPs, at the UE. The UE measures the timing of the received signals using assistance data received from the positioning server, and the resulting measurements are used to locate the UE in relation to the neighbouring TPs. + +The operation of the OTDOA method is described in clause 8.2. + +### 4.3.4 Enhanced Cell ID methods + +In the Cell ID (CID) positioning method, the position of an UE is estimated with the knowledge of its serving ng-eNB, gNB and cell. The information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods. + +Enhanced Cell ID (E-CID) based on LTE signals positioning refers to techniques which use additional UE measurements and/or NG-RAN radio resource and other measurements to improve the UE location estimate. In the case of a serving ng-eNB, uplink E-CID may be supported based on NR, GERAN, UTRA or WLAN signals. + +Although E-CID based on LTE signals positioning may utilise some of the same measurements as the measurement control system in the RRC protocol, the UE generally is not expected to make additional measurements for the sole purpose of positioning; i.e., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE reports the measurements that it has available rather than being required to take additional measurement actions. + +In cases with a requirement for close time coupling between UE and ng-eNB measurements (e.g., $T_{ADV}$ type 1 and UE E-UTRA Rx-Tx time difference), the ng-eNB configures the appropriate RRC measurements and is responsible for maintaining the required coupling between the measurements. + +The operation of the Enhanced Cell ID based on LTE signals method is described in clause 8.3. + +### 4.3.5 Barometric pressure sensor positioning + +The barometric pressure sensor method makes use of barometric sensors to determine the vertical component of the position of the UE. The UE measures barometric pressure, optionally aided by assistance data, to calculate the vertical component of its location or to send measurements to the positioning server for position calculation. + +This method should be combined with other positioning methods to determine the 3D position of the UE. + +The operation of the Barometric pressure sensor positioning method is described in clause 8.4. + +### 4.3.6 WLAN positioning + +The WLAN positioning method makes use of the WLAN measurements (AP identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from WLAN [21] access points, optionally aided by assistance data, to send measurements to the positioning server for position calculation. Using the measurement results and a references database, the location of the UE is calculated. + +Alternatively, the UE makes use of WLAN measurements and optionally WLAN AP assistance data provided by the positioning server, to determine its location. + +The operation of the WLAN positioning method is described in clause 8.5. + +### 4.3.7 Bluetooth positioning + +The Bluetooth positioning method makes use of Bluetooth to determine the location of the UE. Three modes are supported: + +- the UE measures received signals from Bluetooth [22] beacons, associated to beacon identifiers, +- the UE transmits a Bluetooth Continuous Tone Extension (CTE) signal to enable Bluetooth beacons to estimate AoA from the UE [51], + +- the UE, based on assistance data from the positioning server about Bluetooth beacon's antenna configuration, estimates AoD from the Bluetooth beacons [51]. + +Using the measurement results and a references database, the location of the UE is calculated. The Bluetooth methods may be combined with other positioning methods (e.g. WLAN) to improve positioning accuracy of the UE. + +The operation of the Bluetooth positioning method is described in clause 8.6. + +#### 4.3.8 TBS positioning + +A Terrestrial Beacon System (TBS) consists of a network of ground-based transmitters, broadcasting signals only for positioning purposes. The current type of TBS positioning signals are the MBS (Metropolitan Beacon System) signals [23] and Positioning Reference Signals (PRS) (TS 36.211 [24]). The UE measures received TBS signals, optionally aided by assistance data, to calculate its location or to send measurements to the positioning server for position calculation. + +The operation of the TBS positioning method based on MBS signals is described in clause 8.7. + +TBS positioning based on PRS signals is part of OTDOA positioning and described in clause 8.2. + +#### 4.3.9 Motion sensor positioning + +The motion sensor method makes use of different sensors such as accelerometers, gyros, magnetometers, to calculate the displacement of UE. The UE estimates a relative displacement based upon a reference position and/or reference time. UE sends a report comprising the determined relative displacement which can be used to determine the absolute position. + +This method should be used with other positioning methods for hybrid positioning. + +The operation of the sensor positioning method is described in clause 8.8. + +#### 4.3.10 NR Enhanced Cell ID methods + +NR Enhanced Cell ID (NR E-CID) positioning refers to techniques which use additional UE measurements and/or gNB measurements to improve the UE location estimate. + +Although NR E-CID positioning may utilise some of the same measurements as the measurement control system in the RRC protocol, the UE generally is not expected to make additional measurements for the sole purpose of positioning; i.e., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE reports the measurements that it has available rather than being required to take additional measurement actions. + +The operation of the NR Enhanced Cell ID method is described in clause 8.9. + +#### 4.3.11 Multi-RTT positioning + +The Multi-RTT positioning method makes use of the UE Rx-Tx time difference measurements (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP and/or DL-RSCP) of downlink signals received from multiple TRPs, measured by the UE and the measured gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP and/or UL-RSCP) at multiple TRPs of uplink signals transmitted from UE. + +The UE measures the UE Rx-Tx time difference measurements (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP and/or DL-RSCP of the received signals) using assistance data received from the positioning server, and the TRPs measure the gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP and/or UL-RSCP of the received signals) using assistance data received from the positioning server. The measurements are used to determine the RTT at the positioning server which are used to estimate the location of the UE. + +For network verification of UE location in NTN, the Multi-RTT positioning method makes use of the UE Rx-Tx time difference measurements (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP) of downlink signals received from a single TRP at different time instances, measured by the UE and the measured gNB Rx-Tx time difference measurements (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP) at a single TRP at different time instances of uplink signals transmitted from UE. Together with each UE Rx-Tx time difference measurement, the UE also reports + +the UE Rx – Tx time difference subframe offset measurement in unit of subframe and the DL timing drift due to Doppler on service link between UE and satellite as defined in TS 38.215 [37]. + +The operation of the Multi-RTT positioning method is described in clause 8.10. + +#### 4.3.12 DL-AoD positioning + +The DL-AoD positioning method makes use of the measured DL-PRS-RSRP (and optionally DL-PRS-RSRPP) of downlink signals received from multiple TPs, at the UE. The UE measures the DL-PRS-RSRP (and optionally DL-PRS-RSRPP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighbouring TPs. + +The operation of the DL-AoD positioning method is described in clause 8.11. + +#### 4.3.13 DL-TDOA positioning + +The DL-TDOA positioning method makes use of the DL RSTD (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP and/or DL-RSCPD) of downlink signals received from multiple TPs, at the UE. The UE measures the DL RSTD (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP and/or DL-RSCPD) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighbouring TPs. + +The operation of the DL-TDOA positioning method is described in clause 8.12. + +#### 4.3.14 UL-TDOA positioning + +The UL-TDOA positioning method makes use of the UL-RTOA (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP and/or UL-RSCP) at multiple RPs of uplink signals transmitted from UE. The RPs measure the UL-RTOA (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP and/or UL-RSCP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE. + +The operation of the UL-TDOA positioning method is described in clause 8.13. + +#### 4.3.15 UL-AoA + +The UL-AoA positioning method makes use of the measured azimuth angle of arrival (A-AoA) and/or zenith angle of arrival (Z-AoA) at multiple RPs of uplink signals transmitted from the UE. The RPs measure A-AoA and Z-AoA (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE. + +The operation of the UL-AoA positioning method is described in clause 8.14. + +#### 4.3.16 SL Positioning and Ranging + +##### 4.3.16.1 Sidelink Round Trip Time Positioning (SL-RTT) + +The SL-RTT positioning method makes use of SL Rx-Tx time difference measurements (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) of sidelink signals received at the target UE from one or more peer UEs (e.g., anchor UEs) and the SL Rx-Tx time difference measurements (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) performed at the one or more peer UEs (e.g., anchor UEs) of sidelink signals transmitted by the target UE. The SL Rx-Tx time difference measurements performed by a pair of UEs allows determining the distance/range between the pair of UEs. Distance/range measurements between a target UE and multiple peer UEs can be used to determine the location of the target UE relative to the locations of the peer UEs (e.g., anchor UEs). + +The operation of the SL-RTT positioning method is described in clause 8.15.2. + +#### 4.3.16.2 Sidelink Angle-of-Arrival (SL-AoA) + +The SL-AoA positioning method makes use of SL angle of arrival measurements (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) of sidelink signals received at the target UE from one or more peer UEs (e.g., anchor UEs) or SL angle of arrival measurements (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) performed at one or more peer UEs (e.g., anchor UE) of sidelink signals transmitted by a target UE. The SL angle of arrival measurements performed by a UE of sidelink signals transmitted by a peer UE determines the azimuth and vertical angle (i.e., the direction) between the pair of UEs relative to a reference direction (e.g., geographical North). Direction measurements between a target UE and multiple peer UEs can be used to determine the location of the target UE relative to the locations of the peer UEs (e.g., anchor UEs). + +The operation of the SL-AoA positioning method is described in clause 8.15.3. + +#### 4.3.16.3 Sidelink Time Difference of Arrival (SL-TDOA) + +The SL-TDOA positioning method makes use of SL-RSTD (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) of sidelink signals received at the target UE from two or more peer UEs (e.g., anchor UEs). The target UE measures the SL-RSTD (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) of the received sidelink signals transmitted by two or more peer UEs. SL-RSTD measurements between a target UE and multiple peer UEs can be used to determine the location of the target UE relative to the locations of the peer UEs (e.g., anchor UEs). + +The operation of the SL-TDOA positioning method is described in clause 8.15.4. + +#### 4.3.16.4 Sidelink Time of Arrival (SL-TOA) + +The SL-TOA positioning method makes use of SL-RTOA (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) of sidelink signals transmitted by a target UE and received by multiple peer UEs (e.g., anchor UEs). The peer UEs measure the SL-RTOA (and optionally SL-PRS-RSRP and/or SL-PRS-RSRPP) of the sidelink signals transmitted by the target UE. SL-RTOA measurements performed at multiple peer UEs can be used to determine the location of the target UE relative to the locations of the peer UEs (e.g., anchor UEs). + +The operation of the SL-TOA positioning method is described in clause 8.15.5. + +--- + +## 5 NG-RAN UE Positioning Architecture + +### 5.1 Architecture + +Figure 5.1-1 shows the architecture in 5GS applicable to positioning of a UE with NR or E-UTRA access. The positioning architecture also supports the NR PC5 interface as illustrated in Figure 5.1-1. Sidelink positioning can be supported when the UE is inside NG-RAN coverage (UE A and UE B in Figure 5.1-1) and when the UE is outside NG-RAN coverage (UE C and UE D in Figure 5.1-1). + +NOTE: Sidelink positioning for UEs in partial coverage is not supported in this Release of the specification. + +The AMF receives a request for some location service associated with a particular target UE from another entity (e.g., GMLC or UE) or the AMF itself decides to initiate some location service on behalf of a particular target UE (e.g., for an IMS emergency call from the UE) as described in TS 23.502 [26] and TS 23.273 [35]. The AMF then sends a location services request to an LMF. The LMF processes the location services request which may include transferring assistance data to the target UE to assist with UE-based and/or UE-assisted positioning and/or may include positioning of the target UE. The LMF then returns the result of the location service back to the AMF (e.g., a position estimate for the UE). In the case of a location service requested by an entity other than the AMF (e.g., a GMLC or UE), the AMF returns the location service result to this entity. + +An NG-RAN node may control several TRPs/TPs, such as remote radio heads, or DL-PRS-only TPs for support of PRS-based TBS. + +An LMF may have a proprietary signalling connection to an E-SMLC which may enable an LMF to access information from E-UTRAN (e.g. to support the OTDOA for E-UTRA positioning method using downlink measurements obtained + +by a target UE of signals from eNBs and/or PRS-only TPs in E-UTRAN). Details of the signalling interaction between an LMF and E-SMLC are outside the scope of this specification. + +An LMF may have a proprietary signalling connection to an SLP. The SLP is the SUPL entity responsible for positioning over the user plane. Further details of user-plane positioning are provided in [15][16]. Details of the signalling interaction between an LMF and SLP are outside the scope of this specification. + +![Figure 5.1-1: UE Positioning Overall Architecture applicable to NG-RAN. The diagram shows the network architecture for UE positioning. On the left, UE C and UE D are connected via NR PC5. UE C is also connected to UE A (containing a SET) via NR PC5. UE A is connected to the NG-RAN via LTE-Uu. UE B (containing a SET) is connected to the NG-RAN via NR-Uu. The NG-RAN contains an ng-eNB with two TPs and a gNB with two TRPs. The ng-eNB and gNB are connected via an Xn interface. The gNB is connected to the AMF via an NG-C interface. The AMF is connected to the LMF via an NL1 interface. The LMF is connected to the E-SMLC and the SLP via dashed lines. The ng-eNB is also connected to the AMF via an NG-C interface.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +Figure 5.1-1: UE Positioning Overall Architecture applicable to NG-RAN. The diagram shows the network architecture for UE positioning. On the left, UE C and UE D are connected via NR PC5. UE C is also connected to UE A (containing a SET) via NR PC5. UE A is connected to the NG-RAN via LTE-Uu. UE B (containing a SET) is connected to the NG-RAN via NR-Uu. The NG-RAN contains an ng-eNB with two TPs and a gNB with two TRPs. The ng-eNB and gNB are connected via an Xn interface. The gNB is connected to the AMF via an NG-C interface. The AMF is connected to the LMF via an NL1 interface. The LMF is connected to the E-SMLC and the SLP via dashed lines. The ng-eNB is also connected to the AMF via an NG-C interface. + +**Figure 5.1-1: UE Positioning Overall Architecture applicable to NG-RAN** + +NOTE 1: Void + +NOTE 2: Void + +NOTE 3: Void + +In case of split gNB architecture, a gNB-DU may include TRP functionality where the TRP functionality may support functions for a TP, RP or both TP and RP. A gNB-DU which includes TRP functionality does not need to offer cell services. + +## 5.2 UE Positioning Operations + +To support positioning of a target UE and delivery of location assistance data to a UE with NG-RAN access in 5GS, location related functions are distributed as shown in the architecture in Figure 5.1-1 and as clarified in greater detail in TS 23.501 [2] and TS 23.273 [35]. The overall sequence of events applicable to the UE, NG-RAN and LMF for any location service is shown in Figure 5.2-1. + +Note that when the AMF receives a Location Service Request in case of the UE is in CM-IDLE state, the AMF performs a network triggered service request as defined in TS 23.502 [26] and TS 23.273 [35] in order to establish a signalling connection with the UE and assign a specific serving gNB or ng-eNB. The UE is assumed to be in connected mode before the beginning of the flow shown in the Figure 5.2-1; that is, any signalling that might be required to bring the UE to connected mode prior to step 1a is not shown. The signalling connection may, however, be later released (e.g. by the NG-RAN node as a result of signalling and data inactivity) while positioning is still ongoing. + +![Sequence diagram illustrating Location Service Support by NG-RAN. The diagram shows five vertical lifelines representing different network entities. The sequence of interactions is as follows: 1. A request for a location service is sent from the leftmost lifeline to the third lifeline. 2. The third lifeline sends a response back to the leftmost lifeline. 3. The third lifeline then sends a request to the second lifeline. 4. The second lifeline sends a response back to the third lifeline. 5. The third lifeline sends a request to the fourth lifeline. 6. The fourth lifeline sends a response back to the third lifeline. 7. Finally, the third lifeline sends a response to the fifth lifeline on the far right.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Sequence diagram illustrating Location Service Support by NG-RAN. The diagram shows five vertical lifelines representing different network entities. The sequence of interactions is as follows: 1. A request for a location service is sent from the leftmost lifeline to the third lifeline. 2. The third lifeline sends a response back to the leftmost lifeline. 3. The third lifeline then sends a request to the second lifeline. 4. The second lifeline sends a response back to the third lifeline. 5. The third lifeline sends a request to the fourth lifeline. 6. The fourth lifeline sends a response back to the third lifeline. 7. Finally, the third lifeline sends a response to the fifth lifeline on the far right. + +**Figure 5.2-1: Location Service Support by NG-RAN** + +- 1a. Either: some entity in the 5GC (e.g. GMLC) requests some location service (e.g. positioning) for a target UE to the serving AMF. +- 1b. Or: the serving AMF for a target UE determines the need for some location service (e.g. to locate the UE for an emergency call). +- 1c. Or: the UE requests some location service (e.g. positioning or delivery of assistance data) to the serving AMF at the NAS level. +2. The AMF transfers the location service request to an LMF. +- 3a. The LMF instigates location procedures with the serving and possibly neighbouring ng-eNB or gNB in the NG-RAN – e.g. to obtain positioning measurements or assistance data. +- 3b. In addition to step 3a or instead of step 3a, the LMF instigates location procedures with the UE – e.g. to obtain a location estimate or positioning measurements or to transfer location assistance data to the UE. +4. The LMF provides a location service response to the AMF and includes any needed results – e.g. success or failure indication and, if requested and obtained, a location estimate for the UE. +- 5a. If step 1a was performed, the AMF returns a location service response to the 5GC entity in step 1a and includes any needed results – e.g. a location estimate for the UE. +- 5b. If step 1b occurred, the AMF uses the location service response received in step 4 to assist the service that triggered this in step 1b (e.g. may provide a location estimate associated with an emergency call to a GMLC). +- 5c. If step 1c was performed, the AMF returns a location service response to the UE and includes any needed results – e.g. a location estimate for the UE. + +Location procedures applicable to NG-RAN occur in steps 3a and 3b in Figure 5.2-1 and are defined in greater detail in this specification. Other steps in Figure 5.2-1 are applicable only to the 5GC and are described in greater detail and in TS 23.502 [26] and TS 23.273 [35]. + +Steps 3a and 3b can involve the use of different position methods to obtain location related measurements for a target UE and from these compute a location estimate and possibly additional information like velocity. Positioning methods supported in this release are summarized in clause 4.3 and described in detail in clause 8. + +The case that the NG-RAN node functions as an LCS client is not supported in this version of the specification. + +## 5.3 NG-RAN Positioning Operations + +### 5.3.1 General NG-RAN Positioning Operations + +Separately from location service support for particular UEs, an LMF may interact with elements in the NG-RAN in order to obtain measurement information to help assist one or more position methods for all UEs. An LMF may also interact with NG-RAN node to provide assistance data information for broadcasting. + +### 5.3.2 OTDOA Positioning Support + +An LMF can interact with any ng-eNB reachable from any of the AMFs with signalling access to the LMF in order to obtain location related information to support the OTDOA for E-UTRA positioning method, including PRS-based TBS for E-UTRA. The information can include timing information for the TP in relation to either absolute GNSS time or timing of other TPs and information about the supported cells and TPs including PRS schedule. + +Signalling access between the LMF and ng-eNB may be via any AMF with signalling access to both the LMF and ng-eNB. + +An LMF can also interact with any gNB reachable from any of the AMFs with signalling access to the LMF in order to obtain NR cell timing information to support the OTDOA for E-UTRA positioning method, in case the UE is served by a NR cell. + +### 5.3.3 Assistance Information Broadcast Support + +An LMF can interact with any NG-RAN node reachable from any of the AMFs with signalling access to the LMF in order to provide assistance data information for broadcasting. The information can include positioning System Information Blocks (posSIBs) together with assistance information meta data, broadcast cells and broadcast periodicity. + +Signalling access between the LMF and NG-RAN node is via any AMF with signalling access to both the LMF and NG-RAN node. + +### 5.3.4 NR RAT-Dependent Positioning Support + +An LMF can interact with any gNB reachable from any of the AMFs with signalling access to the LMF in order to obtain location related information to support the NR RAT-Dependent positioning methods. The information can include timing information for the TRP in relation to either absolute GNSS time or timing of other TRPs and information about the supported cells and TRPs including PRS schedule. + +When an LMF determines a positioning method for a UE, which requires gNB measurements, the LMF can interact with the gNB to support the positioning method. The LMF can request the gNB for SRS configuration for the UE and the gNB can respond with the SRS configuration to the LMF. The gNB can provide an updated SRS configuration to the LMF when the SRS configuration changes. If semi-persistent or aperiodic SRS is configured to the UE, the LMF may activate/deactivate the SRS. When the SRS is transmitted by the UE, the LMF can request multiple TRPs to perform uplink measurements and report the results. + +Signalling access between the LMF and gNB for non-UE associated NRPPa procedure in Clause 7.2.1 may be via any AMF with signalling access to both the LMF and gNB. Signalling access between the LMF and gNB for UE associated NRPPa procedure in Clause 7.2.1 is via the serving AMF, as in TS 23.273 [35]. + +## 5.4 Functional Description of Elements Related to UE Positioning in NG-RAN + +### 5.4.1 User Equipment (UE) + +The UE may make measurements of downlink signals from NG-RAN, sidelink signals from other UEs, and other sources such as E-UTRAN, different GNSS and TBS systems, WLAN access points, Bluetooth beacons, UE barometric pressure and motion sensors. The measurements to be made will be determined by the chosen positioning method. + +The UE may also contain LCS applications, or access an LCS application either through communication with a network accessed by the UE or through another application residing in the UE. This LCS application may include the needed measurement and calculation functions to determine the UE's position with or without network assistance. This is outside of the scope of this specification. + +The UE may also, for example, contain an independent positioning function (e.g., GPS) and thus be able to report its position, independent of the NG-RAN transmissions. The UE with an independent positioning function may also make use of assistance information obtained from the network. + +## 5.4.2 gNB + +The gNB is a network element of NG-RAN that may provide measurement information for a target UE and communicates this information to an LMF. + +To support NR RAT-Dependent positioning, the gNB may make measurements of radio signals for a target UE, and provide measurement results for position estimation. A gNB may serve several TRPs, including for example remote radio heads, and UL-SRS only RPs and DL-PRS-only TPs. For NTN, a TRP may be located on board the satellite. + +A gNB may broadcast assistance data information, received from an LMF, in positioning System Information messages. + +## 5.4.3 ng-eNB + +The ng-eNB is a network element of NG-RAN that may provide measurement results for position estimation and makes measurements of radio signals for a target UE and communicates these measurements to an LMF. + +The ng-eNB makes its measurements in response to requests from the LMF (on demand or periodically). + +An ng-eNB may serve several TPs, including for example remote radio heads and PRS-only TPs for PRS-based TBS positioning for E-UTRA. + +An ng-eNB may broadcast assistance data information, received from an LMF, in positioning System Information messages. + +## 5.4.4 Location Management Function (LMF) + +The LMF manages the support of different location services for target UEs, including positioning of UEs and delivery of assistance data to UEs. The LMF may interact with the serving gNB or serving ng-eNB for a target UE in order to obtain position measurements for the UE, including uplink measurements made by an NG-RAN and downlink measurements made by the UE that were provided to an NG-RAN as part of other functions such as for support of handover. + +The LMF may interact with a target UE in order to deliver assistance data if requested for a particular location service, or to obtain a location estimate if that was requested. + +The LMF may interact with multiple NG-RAN nodes to provide assistance data information for broadcasting. The assistance data information for broadcast may optionally be segmented and/or ciphered by the LMF. The LMF may also interact with AMFs to provide ciphering key data information to the AMF as described in greater detail in TS 23.273 [35]. + +For positioning of a target UE, the LMF decides on the position methods to be used, based on factors that may include the LCS Client type, the required QoS, UE positioning capabilities, gNB positioning capabilities and ng-eNB positioning capabilities. The LMF then invokes these positioning methods in the UE, serving gNB and/or serving ng-eNB. The positioning methods may yield a location estimate for UE-based position methods and/or positioning measurements for UE-assisted and network-based position methods. The LMF may combine all the received results and determine a single location estimate for the target UE (hybrid positioning). Additional information like accuracy of the location estimate and velocity may also be determined. + +The LMF may interact with the AMF to provide (updated) UE Positioning Capability to AMF and to receive stored UE Positioning Capability from AMF as described in TS 23.273 [35]. + +For NTN, the LMF is configured by the OAM with satellite related information (described in TS 38.300 [52]), as well as the association between TRP(s) and satellite(s). + +## 5.4.5 Positioning Reference Unit (PRU) + +A Positioning Reference Unit (PRU) at a known location can perform positioning measurements (e.g., RSTD, RSRP, UE Rx-Tx Time Difference measurements, DL-RSCPD, DL-RSCP, etc.) and report these measurements to a location server. In addition, the PRU can transmit SRS to enable TRPs to measure and report UL positioning measurements (e.g., RTOA, UL-AoA, gNB Rx-Tx Time Difference, UL-RSCP, etc.) from PRU at a known location. The PRU measurements can be compared by a location server with the measurements expected at the known PRU location to determine correction terms for other nearby target devices. The DL- and/or UL location measurements for other target devices can then be corrected based on the previously determined correction terms. + +PRU measurements may also be provided to the target device in the assistance data as described in clause 8.12. + +From a location server perspective, the PRU functionality is realized by a UE with known location. + +--- + +# 6 Signalling protocols and interfaces + +## 6.1 Network interfaces supporting positioning operations + +### 6.1.1 General LCS control plane architecture + +The general LCS control plane architecture in the 5GS applicable to a target UE with NG-RAN access is defined in TS 23.501 [2] and TS 23.273 [35]. The general architecture to support ranging based services and sidelink positioning in the 5GS is provided in TS 23.586 [46]. + +### 6.1.2 NR-Uu interface + +The NR-Uu interface, connecting the UE to the gNB over the air, is used as one of several transport links for the NR positioning protocol(s) for a target UE with NR access to NG-RAN. + +### 6.1.3 LTE-Uu interface + +The LTE-Uu interface, connecting the UE to the ng-eNB over the air, is used as one of several transport links for the LTE positioning protocol(s) for a target UE with LTE access to NG-RAN. + +### 6.1.4 NG-C interface + +The NG-C interface between the gNB and the AMF and between the ng-eNB and the AMF is transparent to all UE-positioning-related procedures. It is involved in these procedures only as a transport link for the NR positioning protocol(s). + +For gNB related positioning procedures, the NG-C interface transparently transports both positioning requests from the LMF to the gNB and positioning results from the gNB to the LMF. + +For ng-eNB related positioning procedures, the NG-C interface transparently transports both positioning requests from the LMF to the ng-eNB and positioning results from the ng-eNB to the LMF. + +For delivery of broadcast assistance data information, the NG-C interface transparently transports both the assistance data information from the LMF to the NG-RAN node for broadcasting and the feedback information on assistance information broadcasting from the NG-RAN node to the LMF. The NG-C interface is also used by an AMF to transparently transport ciphering keys via NG-RAN node to UEs using a NAS message. The ciphering keys are used to decipher broadcast assistance data information, if the broadcast assistance data information is ciphered. + +### 6.1.5 NL1 interface + +The NL1 interface, between the LMF and the AMF, is transparent to all UE related, gNB related and ng-eNB related positioning procedures. It is used only as a transport link for the LTE Positioning Protocols LPP, SLPP and NR Positioning Protocol A NRPPa. + +### 6.1.6 F1 interface + +In case of split gNB architecture, the F1 interface is used to support the exchange of positioning information between the gNB-DU and the gNB-CU; it is also used transparently as a transport link for the LPP and SLPP. + +### 6.1.7 NR PC5 interface + +The NR PC5 interface is used as transport link for the SL positioning protocol SLPP. + +## 6.2 UE-terminated protocols + +### 6.2.1 LTE Positioning Protocol (LPP) + +The LTE Positioning Protocol (LPP) is terminated between a target device (the UE in the control-plane case or SET in the user-plane case) and a positioning server (the LMF in the control-plane case or SLP in the user-plane case). It may use either the control- or user-plane protocols as underlying transport. In this specification, only control plane use of LPP is defined. User plane support of LPP is defined in [15] and [16]. + +LPP messages are carried as transparent PDUs across intermediate network interfaces using the appropriate protocols (e.g., NGAP over the NG-C interface, NAS/RRC over the LTE-Uu and NR-Uu interfaces). The LPP protocol is intended to enable positioning for NR and LTE using a multiplicity of different position methods, while isolating the details of any particular positioning method and the specifics of the underlying transport from one another. + +The protocol operates on a transaction basis between a target device and a server, with each transaction taking place as an independent procedure. More than one such procedure may be in progress at any given moment. An LPP procedure may involve a request/response pairing of messages or one or more "unsolicited" messages. Each procedure has a single objective (e.g., transfer of assistance data, exchange of LPP related capabilities, or positioning of a target device according to some QoS and use of one or more positioning methods). Multiple procedures, in series and/or in parallel, can be used to achieve more complex objectives (e.g., positioning of a target device in association with transfer of assistance data and exchange of LPP related capabilities). Multiple procedures also enable more than one positioning attempt to be ongoing at the same time (e.g., to obtain a coarse location estimate with low delay while a more accurate location estimate is being obtained with higher delay). + +An LPP session is defined between a positioning server and the target device, the details of its relation with transactions are described in clause 4.1.2 of TS 36.355 [19]. + +For the 3GPP 5GS Control Plane solution defined in TS 23.501 [2], TS 23.502 [26] and TS 23.273 [35], the UE is the target device and the LMF is the server. For SUPL 2.0 support, the SUPL Enabled Terminal (SET) is the target device and the SUPL Location Platform (SLP) is the server. The operations controlled through LPP are described further in clause 7.1. + +LPP defined data structures for assistance data information are reused for supporting RRC broadcast of assistance data information which are embedded in positioning SIBs. This enables broadcast assistance data using the same data structures which are used for point to point location. + +### 6.2.2 Radio Resource Control (RRC) for NR + +The RRC protocol for NR is terminated between the gNB and the UE. It provides transport for LPP and SLPP messages over the NR-Uu interface. + +In addition to providing transport for LPP and SLPP messages over the NR-Uu interface, it supports transfer of measurements that may be used for positioning purposes through the existing measurement systems specified in TS 38.331 [14]. + +The RRC protocol for NR also supports broadcasting of assistance data via positioning System Information messages. + +The RRC protocol for NR is also used to configure UEs with a sounding reference signal (SRS) for SRS transmission in RRC\_CONNECTED and RRC\_INACTIVE to support NG-RAN measurements for NR positioning, provide pre-configured measurement gap configuration(s) and pre-configured PRS processing window for DL-PRS measurement and report the UE TxTEG (Tx Timing Error Group) for UL-TDOA. + +The RRC protocol for NR also supports SL-PRS Resource Allocation via system information or dedicated signalling or pre-configuration. + +### 6.2.3 Radio Resource Control (RRC) for LTE + +The RRC protocol for LTE is terminated between the ng-eNB and the UE. In addition to providing transport for LPP messages over the LTE-Uu interface, it supports transfer of measurements that may be used for positioning purposes through the existing measurement systems specified in TS 36.331 [13]. + +The RRC protocol for LTE also supports broadcasting of assistance data via positioning System Information messages. + +### 6.2.4 Medium Access Control (MAC) for NR + +The MAC protocol for NR supports activation and deactivation of configured semi-persistent SRS resource sets as specified in TS 38.321 [39] to support NG-RAN measurements for NR positioning. + +The MAC protocol for NR also supports request of positioning measurement gap activation and deactivation from a UE, and activation and deactivation of pre-configured measurement gap from the NG-RAN as specified in TS 38.321 [39]. + +The MAC protocol for NR can also be used to activate and deactivate of PRS Processing Window as specified in TS 38.321 [39]. + +The MAC protocol for NR also supports services and functions for SL-PRS transmission and reception as specified in TS 38.321 [39]. + +### 6.2.5 Sidelink Positioning Protocol (SLPP) + +The Sidelink Positioning Protocol (SLPP) is exchanged over PC5-U reference point between UEs (e.g., target UE, anchor UE, server UE) to manage the ranging/sidelink positioning sessions among a group of UEs. + +SLPP is also exchanged between a target UE and a LMF to support sidelink positioning. In this case, the SLPP messages are carried as transparent PDUs across intermediate network interfaces using the appropriate protocols (e.g., NGAP over the NG-C interface, NAS/RRC over the NR-Uu interface). + +The SLPP protocol is intended to enable sidelink positioning and ranging using a multiplicity of different position methods, while isolating the details of any particular positioning method and the specifics of the underlying transport from one another. + +The protocol operates on a transaction basis between UEs and between a UE and an LMF, with each transaction taking place as an independent procedure as described in TS 38.355 [47]. More than one such procedure may be in progress at any given moment. A SLPP procedure may involve a request/response pairing of messages or one or more "unsolicited" messages. Each procedure has a single objective (e.g., transfer of assistance data, exchange of SLPP related capabilities, or positioning/ranging of a target device according to some QoS and use of one or more SL positioning methods). Multiple procedures, in series and/or in parallel, can be used to achieve more complex objectives (e.g., positioning of a target device in association with transfer of assistance data and exchange of SLPP related capabilities). + +An SLPP Session is used between UEs or between a UE and an LMF to fulfil a ranging/sidelink positioning service request. A SLPP Session comprises one or more SLPP transactions. A UE may simultaneously participate in multiple SLPP sessions. For UE-only scenarios, a SLPP Session ID is used to identify all SLPP transactions belonging to an SLPP session which enables UEs to uniquely distinguish SLPP messages for one session from SLPP messages for other sessions. + +NOTE 1: For LMF involved cases, the SLPP Session ID is assigned by the SL Target UE and used for SLPP messages exchanged between the group of UEs. + +NOTE 2: For LMF involved cases, the SLPP Session ID is optionally included in SLPP messages transferred between SL Target UE and LMF. + +## 6.3 NG-RAN Node terminated protocols + +### 6.3.1 NR Positioning Protocol A (NRPPa) + +The NR Positioning Protocol A (NRPPa) carries information between the NG-RAN Node and the LMF. It is used to support the following positioning functions: + +- E-CID for E-UTRA where measurements are transferred from the ng-eNB to the LMF. +- Data collection from ng-eNB's and gNB's for support of OTDOA positioning for E-UTRA. +- Cell-ID and Cell Portion ID retrieval from gNB's for support of NR Cell ID positioning method. +- Exchange of information between LMF and NG-RAN node for the purpose of assistance data broadcasting. +- NR E-CID where measurements are transferred from the gNB to the LMF. +- NR Multi-RTT where measurements are transferred from the gNB to the LMF. +- NR UL-AoA where measurements are transferred from the gNB to the LMF. +- NR UL-TDOA where measurements are transferred from the gNB to the LMF. +- Data collection from gNBs for support of DL-TDOA, DL-AoD, Multi-RTT, UL-TDOA, UL-AoA. +- Measurement Preconfiguration Information Transfer which allows the LMF to request the NG-RAN node to pre-configure and activate/deactivate measurement gap and/or PRS processing window. + +The NRPPa protocol is transparent to the AMF. The AMF routes the NRPPa PDUs transparently based on a Routing ID corresponding to the involved LMF over NG-C interface without knowledge of the involved NRPPa transaction. It carries the NRPPa PDUs over NG-C interface either in UE associated mode or non-UE associated mode. + +In case of a split gNB architecture, the NRPPa protocol is terminated at the gNB-CU. + +### 6.3.2 NG Application Protocol (NGAP) + +The NGAP protocol, terminated between the AMF and the NG-RAN Node, is used as transport for LPP and NRPPa messages over the NG-C interface. The NGAP protocol is also used to instigate and terminate NG-RAN Node related positioning procedures. + +## 6.4 Signalling between an LMF and UE + +### 6.4.1 Protocol Layering + +Figure 6.4.1-1 shows the protocol layering used to support transfer of LPP messages between an LMF and UE. The LPP PDU is carried in NAS PDU between the AMF and the UE. + +![Figure 6.4.1-1: Protocol Layering for LMF to UE LPP Signalling. This diagram shows the protocol stack for LPP signalling. On the left, the UE stack has layers L1, MAC, RLC, PDCP, RRC, NAS, and SLPP. In the middle, the NG RAN stack has layers L1, MAC, RLC, PDCP, and a 'Relay' block containing RRC and NGAP. On the right, the AMF stack has layers L1, MAC, RLC, PDCP, NGAP, NAS, and SLPP. The LMF stack on the far right has layers L1, MAC, RLC, PDCP, NGAP, NAS, and SLPP. Arrows indicate the flow of data from the LMF down through the AMF, then through the NG RAN relay, and finally to the UE.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Figure 6.4.1-1: Protocol Layering for LMF to UE LPP Signalling. This diagram shows the protocol stack for LPP signalling. On the left, the UE stack has layers L1, MAC, RLC, PDCP, RRC, NAS, and SLPP. In the middle, the NG RAN stack has layers L1, MAC, RLC, PDCP, and a 'Relay' block containing RRC and NGAP. On the right, the AMF stack has layers L1, MAC, RLC, PDCP, NGAP, NAS, and SLPP. The LMF stack on the far right has layers L1, MAC, RLC, PDCP, NGAP, NAS, and SLPP. Arrows indicate the flow of data from the LMF down through the AMF, then through the NG RAN relay, and finally to the UE. + +**Figure 6.4.1-1: Protocol Layering for LMF to UE LPP Signalling** + +Figure 6.4.1-2 shows the protocol layering used to support transfer of SLPP messages between an LMF and UE. The SLPP PDU is carried in NAS PDU between the AMF and the UE. + +![Figure 6.4.1-2: Protocol Layering for LMF to UE SLPP Signalling. This diagram shows the protocol stack for SLPP signalling. On the left, the UE stack has layers L1, MAC, RLC, PDCP, RRC, NAS, and SLPP. In the middle, the NG RAN stack has layers L1, MAC, RLC, PDCP, and a 'Relay' block containing RRC and NGAP. On the right, the AMF stack has layers L1, MAC, RLC, PDCP, NGAP, NAS, and a 'Relay' block containing NGAP and HTTP/2. The LMF stack on the far right has layers L1, MAC, RLC, PDCP, NGAP, HTTP/2, TLS, TCP, IP, L2, and SLPP. Arrows indicate the flow of data from the LMF up through the AMF, then through the NG RAN relay, and finally to the UE.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +Figure 6.4.1-2: Protocol Layering for LMF to UE SLPP Signalling. This diagram shows the protocol stack for SLPP signalling. On the left, the UE stack has layers L1, MAC, RLC, PDCP, RRC, NAS, and SLPP. In the middle, the NG RAN stack has layers L1, MAC, RLC, PDCP, and a 'Relay' block containing RRC and NGAP. On the right, the AMF stack has layers L1, MAC, RLC, PDCP, NGAP, NAS, and a 'Relay' block containing NGAP and HTTP/2. The LMF stack on the far right has layers L1, MAC, RLC, PDCP, NGAP, HTTP/2, TLS, TCP, IP, L2, and SLPP. Arrows indicate the flow of data from the LMF up through the AMF, then through the NG RAN relay, and finally to the UE. + +**Figure 6.4.1-2: Protocol Layering for LMF to UE SLPP Signalling** + +### 6.4.2 LPP PDU Transfer + +Figure 6.4.2-1 shows the transfer of an LPP PDU between an LMF and UE, in the network- and UE-triggered cases. These two cases may occur separately or as parts of a single more complex operation. + +![Figure 6.4.2-1: LPP PDU transfer between LMF and UE (network- and UE-triggered cases). The diagram consists of two sequence diagrams. The top diagram shows network-triggered transfer: LMF (1) sends a message to AMF (2), which is forwarded by AMF to NG-RAN (3), which then forwards it to UE (4). The bottom diagram shows UE-triggered transfer: UE (4) sends a message to NG-RAN (3), which forwards it to AMF (2), which then forwards it to LMF (1).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates two sequence diagrams for LPP PDU transfer between the LMF and the UE. + +**Top Diagram (Network-triggered case):** + +- The LMF (1) sends a message to the AMF (2). +- The AMF (2) sends a message to the NG-RAN (3). +- The NG-RAN (3) sends a message to the UE (4). + +**Bottom Diagram (UE-triggered case):** + +- The UE (4) sends a message to the NG-RAN (3). +- The NG-RAN (3) sends a message to the AMF (2). +- The AMF (2) sends a message to the LMF (1). + +Figure 6.4.2-1: LPP PDU transfer between LMF and UE (network- and UE-triggered cases). The diagram consists of two sequence diagrams. The top diagram shows network-triggered transfer: LMF (1) sends a message to AMF (2), which is forwarded by AMF to NG-RAN (3), which then forwards it to UE (4). The bottom diagram shows UE-triggered transfer: UE (4) sends a message to NG-RAN (3), which forwards it to AMF (2), which then forwards it to LMF (1). + +**Figure 6.4.2-1: LPP PDU transfer between LMF and UE (network- and UE-triggered cases)** + +1. Steps 1 to 4 may occur before, after, or at the same time as steps 5 to 8. Steps 1 to 4 and steps 5 to 8 may also be repeated. Steps 1 to 4 are triggered when the LMF needs to send an LPP message to the UE as part of some LPP positioning activity. The LMF then invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a LPP PDU to the UE. The service operation includes the LPP PDU together with the LCS Correlation ID in the N1 Message Container as defined in TS 29.518 [28]. +2. If the UE is in CM-IDLE state (e.g. if the NG connection was previously released due to data and signalling inactivity), the AMF initiates a network triggered service request as defined in TS 23.502 [26] in order to establish a signalling connection with the UE and assign a serving NG-RAN node. +3. The AMF includes the LPP PDU in the payload container of a DL NAS Transport message, and a Routing Identifier identifying the LMF in the Additional Information of the DL NAS Transport message defined in TS 24.501 [29]. The AMF then sends the DL NAS Transport message to the serving NG-RAN Node in an NGAP Downlink NAS Transport message defined in TS 38.413 [30]. The AMF need not retain state information for this transfer; it can treat any response in step 7 as a separate non-associated transfer. +4. The NG-RAN Node forwards the DL NAS Transport message to the UE in an RRC DL Information Transfer message. +5. Steps 5 to 8 are triggered when the UE needs to send an LPP PDU to the LMF as part of some LPP positioning activity. If the UE is in CM-IDLE state, the UE instigates a UE triggered service request as defined in TS 23.502 [26] in order to establish a signalling connection with the AMF and assign a serving NG-RAN node. +6. The UE includes the LPP PDU in the payload container of an UL NAS Transport message, and the Routing Identifier, which has been received in step 4, in the Additional Information of the UL NAS Transport message defined in TS 24.501 [29]. The UE then sends the UL NAS Transport message to the serving NG-RAN node in an RRC UL Information Transfer message. + +7. The NG-RAN node forwards the UL NAS Transport Message to the AMF in an NGAP Uplink NAS Transport message. +8. The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards the LMF indicated by the Routing Identifier received in step 7. The service operation includes the LPP PDU received in step 7 together with the LCS Correlation ID in the N1 Message Container as defined in TS 29.518 [28]. + +### 6.4.3 SLPP PDU Transfer + +Figure 6.4.3-1 shows the transfer of an SLPP PDU between an LMF and UE, in the network- and UE-triggered cases. These two cases may occur separately or as parts of a single more complex operation. + +![Figure 6.4.3-1: SLPP PDU transfer between LMF and UE (network- and UE-triggered cases). The diagram consists of two sequence diagrams. The top diagram shows the network-triggered case with four steps: 1. LMF to AMF: Namf_Communication_N1N2MessageTransfer (SLPP PDU); 2. AMF to NG-RAN Node: Network Triggered Service Request (dashed box); 3. AMF to NG-RAN Node: NGAP Downlink NAS Transport (SLPP PDU); 4. NG-RAN Node to UE: RRC DL Information Transfer (SLPP PDU). The bottom diagram shows the UE-triggered case with four steps: 5. UE to NG-RAN Node: UE Triggered Service Request (dashed box); 6. UE to NG-RAN Node: RRC UL Information Transfer (SLPP PDU); 7. NG-RAN Node to AMF: NGAP Uplink NAS Transport (SLPP PDU); 8. AMF to LMF: Namf_Communication_N1MessageNotify (SLPP PDU).](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +Figure 6.4.3-1: SLPP PDU transfer between LMF and UE (network- and UE-triggered cases). The diagram consists of two sequence diagrams. The top diagram shows the network-triggered case with four steps: 1. LMF to AMF: Namf\_Communication\_N1N2MessageTransfer (SLPP PDU); 2. AMF to NG-RAN Node: Network Triggered Service Request (dashed box); 3. AMF to NG-RAN Node: NGAP Downlink NAS Transport (SLPP PDU); 4. NG-RAN Node to UE: RRC DL Information Transfer (SLPP PDU). The bottom diagram shows the UE-triggered case with four steps: 5. UE to NG-RAN Node: UE Triggered Service Request (dashed box); 6. UE to NG-RAN Node: RRC UL Information Transfer (SLPP PDU); 7. NG-RAN Node to AMF: NGAP Uplink NAS Transport (SLPP PDU); 8. AMF to LMF: Namf\_Communication\_N1MessageNotify (SLPP PDU). + +**Figure 6.4.3-1: SLPP PDU transfer between LMF and UE (network- and UE-triggered cases)** + +1. Steps 1 to 4 may occur before, after, or at the same time as steps 5 to 8. Steps 1 to 4 and steps 5 to 8 may also be repeated. Steps 1 to 4 are triggered when the LMF needs to send an SLPP message to the UE as part of some SLPP positioning activity. The LMF then invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a SLPP PDU to the UE. The service operation includes the SLPP PDU together with the LCS Correlation ID in the N1 Message Container as defined in TS 29.518 [28]. +2. If the UE is in CM-IDLE state (e.g. if the NG connection was previously released due to data and signalling inactivity), the AMF initiates a network triggered service request as defined in TS 23.502 [26] in order to establish a signalling connection with the UE and assign a serving NG-RAN node. +3. The AMF includes the SLPP PDU in the payload container of a DL NAS Transport message, and a Routing Identifier identifying the LMF in the Additional Information of the DL NAS Transport message defined in TS 24.501 [29]. The AMF then sends the DL NAS Transport message to the serving NG-RAN Node in an NGAP + +Downlink NAS Transport message defined in TS 38.413 [30]. The AMF need not retain state information for this transfer; it can treat any response in step 7 as a separate non-associated transfer. + +4. The NG-RAN Node forwards the DL NAS Transport message to the UE in an RRC DL Information Transfer message. +5. Steps 5 to 8 are triggered when the UE needs to send an SLPP PDU to the LMF as part of some SLPP positioning activity. If the UE is in CM-IDLE state, the UE instigates a UE triggered service request as defined in TS 23.502 [26] in order to establish a signalling connection with the AMF and assign a serving NG-RAN node. +6. The UE includes the SLPP PDU in the payload container of an UL NAS Transport message, and the Routing Identifier, which has been received in step 4, in the Additional Information of the UL NAS Transport message defined in TS 24.501 [29]. The UE then sends the UL NAS Transport message to the serving NG-RAN node in an RRC UL Information Transfer message. +7. The NG-RAN node forwards the UL NAS Transport Message to the AMF in an NGAP Uplink NAS Transport message. +8. The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards the LMF indicated by the Routing Identifier received in step 7. The service operation includes the SLPP PDU received in step 7 together with the LCS Correlation ID in the N1 Message Container as defined in TS 29.518 [28]. + +## 6.5 Signalling between an LMF and NG-RAN node + +### 6.5.1 Protocol Layering + +Figure 6.5.1-1 shows the protocol layering used to support transfer of NRPPa PDUs between an LMF and NG-RAN Node. + +The NRPPa protocol is transparent to the AMF. The AMF routes the NRPPa PDUs transparently based on a Routing ID which corresponds to the involved LMF node over the NG interface without knowledge of the involved NRPPa transaction. It carries the NRPPa PDUs over NG interface either in UE associated mode or non-UE associated mode. + +![Protocol layering diagram for LMF to NG-RAN signalling. It shows three vertical columns representing protocol stacks. The left column (UE) has layers: NAS, RRC, SDAP, PDCP, RLC, MAC, PHY. The middle column (AMF) has layers: NAS, RRC, SDAP, PDCP, RLC, MAC, PHY. The right column (NG-RAN) has layers: NAS, RRC, SDAP, PDCP, RLC, MAC, PHY. Dashed horizontal lines connect corresponding layers across the columns. Vertical dashed lines separate the columns. The diagram illustrates that the AMF acts as a transparent relay for the NAS layer between the UE and the NG-RAN node.](a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg) + +Protocol layering diagram for LMF to NG-RAN signalling. It shows three vertical columns representing protocol stacks. The left column (UE) has layers: NAS, RRC, SDAP, PDCP, RLC, MAC, PHY. The middle column (AMF) has layers: NAS, RRC, SDAP, PDCP, RLC, MAC, PHY. The right column (NG-RAN) has layers: NAS, RRC, SDAP, PDCP, RLC, MAC, PHY. Dashed horizontal lines connect corresponding layers across the columns. Vertical dashed lines separate the columns. The diagram illustrates that the AMF acts as a transparent relay for the NAS layer between the UE and the NG-RAN node. + +Figure 6.5.1-1: Protocol Layering for LMF to NG-RAN Signalling + +### 6.5.2 NRPPa PDU Transfer for UE Positioning + +Figure 6.5.2-1 shows NRPPa PDU transfer between an LMF and NG-RAN Node to support positioning of a particular UE. + +![Sequence diagram illustrating NRPPa PDU Transfer between an LMF and NG-RAN node for UE Positioning. The diagram shows four lifelines: LMF, AMF, NG-RAN Node, and UE. The sequence of messages is: 1. LMF to AMF (Namf_Communication_N1N2MessageTransfer); 2. AMF to NG-RAN Node (NGAP Downlink UE Associated NRPPa Transport); 3. NG-RAN Node to AMF (NGAP Uplink UE Associated NRPPa Transport); 4. AMF to LMF (Namf_Communication_N2InfoNotify). A dashed box highlights the interaction between the LMF and AMF.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Sequence diagram illustrating NRPPa PDU Transfer between an LMF and NG-RAN node for UE Positioning. The diagram shows four lifelines: LMF, AMF, NG-RAN Node, and UE. The sequence of messages is: 1. LMF to AMF (Namf\_Communication\_N1N2MessageTransfer); 2. AMF to NG-RAN Node (NGAP Downlink UE Associated NRPPa Transport); 3. NG-RAN Node to AMF (NGAP Uplink UE Associated NRPPa Transport); 4. AMF to LMF (Namf\_Communication\_N2InfoNotify). A dashed box highlights the interaction between the LMF and AMF. + +**Figure 6.5.2-1: NRPPa PDU Transfer between an LMF and NG-RAN node for UE Positioning** + +1. Steps 1 to 3 are triggered when the LMF needs to send an NRPPa message to the serving NG-RAN Node for a target UE as part of a NRPPa positioning activity. The LMF then invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a NRPPa PDU to the serving NG-RAN Node for the UE. The service operation includes the NRPPa PDU together with the LCS Correlation ID in the N2 Message Container as defined in TS 29.518 [28]. +2. If the UE is in CM-IDLE state (e.g. if the NG connection was previously released due to data and signalling inactivity), the AMF performs a network triggered service request as defined in TS 23.502 [26] in order to establish a signalling connection with the UE and assign a serving NG-RAN Node. +3. The AMF forwards the NRPPa PDU to the serving NG-RAN Node in an NGAP Downlink UE Associated NRPPa Transport message over the NG signalling connection corresponding to the UE and includes the Routing ID related to the LMF. The AMF need not retain state information for this transfer – e.g. can treat any response in step 4 as a separate non-associated transfer. +4. Steps 4 and 5 are triggered when a serving NG-RAN Node needs to send an NRPPa message to the LMF for a target UE as part of an NRPPa positioning activity. The NG-RAN Node then sends an NRPPa PDU to the AMF in an NGAP Uplink UE Associated NRPPa Transport message and includes the Routing ID received in step 3. +5. The AMF invokes the Namf\_Communication\_N2InfoNotify service operation towards the LMF indicated by the Routing ID received in step 4. The service operation includes the NRPPa PDU received in step 4 together with the LCS Correlation ID in the N2 Info Container as defined in TS 29.518 [28]. Steps 1 to 5 may be repeated. + +### 6.5.3 NRPPa PDU Transfer for Positioning Support + +Figure 6.5.3-1 shows NRPPa PDU transfer between an LMF and NG-RAN Node when related to gathering data from the NG-RAN Node for positioning support for all UEs. + +![Sequence diagram illustrating NRPPa PDU Transfer between an LMF and NG-RAN for obtaining NG-RAN Data. The diagram shows four lifelines: LMF, AMF, NG-RAN Node, and another NG-RAN Node. The sequence of messages is: 1. LMF to AMF (dashed arrow), 2. AMF to LMF (dashed arrow), 3. AMF to NG-RAN Node (solid arrow), 4. NG-RAN Node to AMF (solid arrow), 5. AMF to LMF (solid arrow).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant LMF + participant AMF + participant NG-RAN Node 1 + participant NG-RAN Node 2 + Note left of LMF: LMF needs to send an NRPPa message to an NG-RAN Node + LMF->>AMF: NRPPa PDU (dashed) + AMF-->>LMF: Response (dashed) + AMF->>NG-RAN Node 1: Downlink Non UE Associated NRPPa Transport (solid) + NG-RAN Node 1->>AMF: Uplink Non UE Associated NRPPa Transport (solid) + AMF->>LMF: Info Notify (solid) + +``` + +Sequence diagram illustrating NRPPa PDU Transfer between an LMF and NG-RAN for obtaining NG-RAN Data. The diagram shows four lifelines: LMF, AMF, NG-RAN Node, and another NG-RAN Node. The sequence of messages is: 1. LMF to AMF (dashed arrow), 2. AMF to LMF (dashed arrow), 3. AMF to NG-RAN Node (solid arrow), 4. NG-RAN Node to AMF (solid arrow), 5. AMF to LMF (solid arrow). + +**Figure 6.5.3-1: NRPPa PDU Transfer between an LMF and NG-RAN for obtaining NG-RAN Data** + +0. An ng-eNB in the NG-RAN may communicate with several TPs (including PRS-only TPs in case of PRS-based TBS is supported) to configure TPs, obtain TP configuration information, etc. + +A gNB in the NG-RAN may communicate with several TRPs (including PRS-only TRPs) to configure TRPs, obtain TRP configuration information, etc. + +NOTE: NG-RAN-TP/TRP signalling and configuration is outside the scope of this specification. + +1. Steps 1 and 2 are triggered when the LMF needs to send an NRPPa message to an NG-RAN Node to obtain data related to the NG-RAN Node, and possibly associated TPs. The LMF invokes the Namf\_Communication\_NonUeN2MessageTransfer service operation towards the AMF to request the transfer of a NRPPa PDU to a NG-RAN node (gNB or ng-eNB) in the NG-RAN. The service operation includes the target NG-RAN node identity and the NRPPa PDU in the N2 Information Container as defined in TS 29.518 [28]. +2. The AMF forwards the NRPPa PDU to the identified NG-RAN Node in an NGAP Downlink Non UE Associated NRPPa Transport message and includes a Routing ID identifying the LMF. The AMF need not retain state information for this transfer – e.g. can treat any response in step 3 as a separate non-associated transfer. +3. Steps 3 and 4 are triggered when an NG-RAN Node needs to send an NRPPa PDU to an LMF containing data applicable to the NG-RAN Node, and possibly associated TPs. The NG-RAN Node then sends an NRPPa PDU to the AMF in an NGAP Uplink Non UE Associated NRPPa Transport message and includes the Routing ID received in step 2. +4. The AMF invokes the Namf\_Communication\_NonUeN2InfoNotify service operation towards the LMF indicated by the Routing Identifier received in step 3. The service operation includes the NRPPa PDU received in step 3 in the N2 Info Container as defined in TS 29.518 [28]. Steps 1 to 4 may be repeated. + +## 6.5.4 NRPPa PDU Transfer for Assistance Information Broadcast + +Figure 6.5.4-1 shows NRPPa PDU transfer between an LMF and NG-RAN node to support broadcast of assistance data. + +![Sequence diagram for NRPPa PDU Transfer between an LMF and NG-RAN Node for providing assistance information for broadcasting. The diagram shows two vertical lifelines. The left lifeline has a solid black rectangle at the top, representing the LMF. The right lifeline is a simple vertical line, representing the NG-RAN node. A horizontal arrow points from the right lifeline to the left lifeline, indicating a message transfer.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Sequence diagram for NRPPa PDU Transfer between an LMF and NG-RAN Node for providing assistance information for broadcasting. The diagram shows two vertical lifelines. The left lifeline has a solid black rectangle at the top, representing the LMF. The right lifeline is a simple vertical line, representing the NG-RAN node. A horizontal arrow points from the right lifeline to the left lifeline, indicating a message transfer. + +**Figure 6.5.4-1: NRPPa PDU Transfer between an LMF and NG-RAN Node for providing assistance information for broadcasting.** + +1. Step 1 is triggered when the LMF needs to send new or updated assistance information to an NG-RAN node for broadcasting in positioning system information messages. The LMF invokes the *Namf\_Communication\_NonUeN2MessageTransfer* service operation towards the AMF to request the transfer of a NRPPa PDU to a NG-RAN node (gNB or ng-eNB) in the NG-RAN. The service operation includes the target NG-RAN node identity and the NRPPa PDU in the N2 Information Container as defined in TS 29.518 [28]. +2. The AMF forwards the NRPPa PDU to the identified NG-RAN node in an NGAP Downlink Non UE Associated NRPPa Transport message and includes the Routing ID identifying the LMF. The AMF need not retain state information for this transfer. + +Figure 6.5.4-2 shows NRPPa PDU transfer between an NG-RAN node and LMF for providing feedback to the LMF on assistance data broadcasting. + +![Sequence diagram for NRPPa PDU Transfer between an NG-RAN node and LMF for providing feedback on assistance data broadcasting. The diagram shows three vertical lifelines. The first lifeline on the left has a rectangle at the top, representing the NG-RAN node. The second lifeline in the middle has a rectangle at the top, representing the AMF. The third lifeline on the right has a rectangle at the top, representing the LMF. A horizontal arrow points from the first lifeline to the second. Another horizontal arrow points from the second lifeline to the third.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +Sequence diagram for NRPPa PDU Transfer between an NG-RAN node and LMF for providing feedback on assistance data broadcasting. The diagram shows three vertical lifelines. The first lifeline on the left has a rectangle at the top, representing the NG-RAN node. The second lifeline in the middle has a rectangle at the top, representing the AMF. The third lifeline on the right has a rectangle at the top, representing the LMF. A horizontal arrow points from the first lifeline to the second. Another horizontal arrow points from the second lifeline to the third. + +**Figure 6.5.4-2: NRPPa PDU Transfer between an NG-RAN node and LMF for providing feedback on assistance data broadcasting.** + +1. Step 1 is triggered when an NG-RAN node needs to send an NRPPa PDU to an LMF for providing feedback on assistance data broadcasting. Step 1 may only be triggered if the procedure in Figure 6.5.4-1 has already been performed. The NG-RAN node sends an NRPPa PDU to the AMF in an NGAP Uplink Non UE Associated NRPPa Transport message. The NG-RAN node includes the previously received Routing ID related to the LMF (Figure 6.5.4-1). +2. The AMF invokes the *Namf\_Communication\_NonUeN2InfoNotify* service operation towards the LMF indicated by the Routing identifier received at step 1. The service operation includes the NRPPa PDU received in step 1 in the N2 Info Container as defined in TS 29.518 [28]. + +## 6.6 Void + +## 6.7 Signalling between UEs + +### 6.7.1 Protocol Layering + +Figure 6.7.1-1 shows the protocol layering used to support transfer of SLPP messages between UEs. The SLPP PDU is carried using "Non-IP" PDCP SDU type for V2X capable UEs as defined in clause 6.1.1 of TS 23.287 [48], and "Unstructured" PDCP SDU type for 5G ProSe capable UEs as defined in clause 6.1.2.2 of TS 23.304 [49]. + +![Diagram showing protocol layering for UE-to-UE signalling for V2X capable UEs and ProSe capable UEs. Both diagrams show two UEs (UE A and UE B) with layers: SLPP, SDAP, PDCP, RLC, MAC, and PHY. For V2X, SLPP connects to Non-IP PDCP SDU. For ProSe, SLPP connects to Unstructured PDCP SDU. Both are connected via NR PC5-U interface.](43979979715bb3304389a0cb18f34444_img.jpg) + +The diagram illustrates the protocol stack for two types of User Equipment (UE) capable of UE-to-UE signalling over the NR PC5-U interface. On the left, 'V2X capable UEs' are shown. UE A and UE B both have a stack of layers: SLPP, SDAP, PDCP, RLC, MAC, and PHY. The SLPP layer in both UEs is connected to a 'Non-IP' PDCP SDU type. The SDAP, PDCP, RLC, MAC, and PHY layers are stacked vertically below. On the right, 'ProSe capable UEs' are shown. UE A and UE B both have the same stack of layers: SLPP, SDAP, PDCP, RLC, MAC, and PHY. Here, the SLPP layer is connected to an 'Unstructured' PDCP SDU type. The SDAP, PDCP, RLC, MAC, and PHY layers follow. Both diagrams show horizontal double-headed arrows between corresponding layers of UE A and UE B, indicating bidirectional communication. The entire stack for each UE is enclosed in a dashed box, and the interface between the two UEs is labeled 'NR PC5-U' at the bottom. + +Diagram showing protocol layering for UE-to-UE signalling for V2X capable UEs and ProSe capable UEs. Both diagrams show two UEs (UE A and UE B) with layers: SLPP, SDAP, PDCP, RLC, MAC, and PHY. For V2X, SLPP connects to Non-IP PDCP SDU. For ProSe, SLPP connects to Unstructured PDCP SDU. Both are connected via NR PC5-U interface. + +Figure 6.7.1-1: Protocol Layering for UE-to-UE Signalling + +NOTE: As specified in TS 23.586 [46], for a UE that is both, V2X and 5G ProSe capable, SLPP is transported either via the V2X or ProSe protocol layering (i.e. no V2X and ProSe cross-communication is supported). + +### 6.7.2 SLPP PDU Transfer + +Figure 6.7.2-1 shows the general transfer of an SLPP PDU between UEs. + +NOTE: In this version of the specification, SLPP PDU transfer between UEs is supported only via established unicast links. + +![Sequence diagram illustrating SLPP PDU transfer between TX UE and RX UE. The process consists of four steps: 1. SLPP layer provides the SLPP PDU and UE identifiers to V2X/ProSe Layer; 2. Unicast Link Establishment (including PC5-S Direct Communication Request, PC5-S Security Establishment, PC5-S Direct Communication Accept, PC5-RRC Capability Information, and PC5-RRC AS Layer Configuration); 3. Determine transport configuration; 4. SLPP over Unicast Link.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant TX_UE as TX UE + participant RX_UE as RX UE + Note left of TX_UE: 1. SLPP layer provides the SLPP PDU and UE identifiers to V2X/ProSe Layer + Note right of RX_UE: 2. Unicast Link Establishment + TX_UE->>RX_UE: PC5-S Direct Communication Request + RX_UE-->>TX_UE: PC5-S Security Establishment + TX_UE-->>RX_UE: PC5-S Direct Communication Accept + RX_UE-->>TX_UE: PC5-RRC Capability Information + TX_UE-->>RX_UE: PC5-RRC AS Layer Configuration + Note right of TX_UE: 3. Determine transport configuration + Note right of RX_UE: 4. SLPP over Unicast Link + TX_UE->>RX_UE: SLPP PDU + +``` + +Sequence diagram illustrating SLPP PDU transfer between TX UE and RX UE. The process consists of four steps: 1. SLPP layer provides the SLPP PDU and UE identifiers to V2X/ProSe Layer; 2. Unicast Link Establishment (including PC5-S Direct Communication Request, PC5-S Security Establishment, PC5-S Direct Communication Accept, PC5-RRC Capability Information, and PC5-RRC AS Layer Configuration); 3. Determine transport configuration; 4. SLPP over Unicast Link. + +**Figure 6.7.2-1: SLPP PDU transfer between UEs** + +1. The TX UE determines to send an SLPP message to the RX UE as part of some SLPP positioning activity (e.g., to instigate a SLPP procedure or in response to a previously received SLPP message). The SLPP layer in the TX UE determines the SLPP PDU and the application layer ID for the peer UE. +2. The TX UE establishes a unicast link with the peer UE using the application layer ID received from step 1, if not already established, as specified in TS 23.287 [48] for V2X capable UEs and TS 23.304 [49] for ProSe capable UEs. +3. The TX UE determines the transport configurations for the SLPP PDU. +For V2X capable UEs, policies and parameters defined in TS 23.287 [48] clause 5.1.2.1 are used to determine the corresponding transport configurations for the SLPP PDU. +For ProSe capable UEs, policies and parameters defined in TS 23.304 [49] clause 5.1.3.1 are used to determine the corresponding transport configurations for the SLPP PDU. +4. The SLPP PDU is transmitted via the established unicast link according to the procedures for V2X communication over PC5 reference point defined in TS 23.287 [48] or according to the procedures for 5G ProSe direct communication defined in TS 23.304 [49]. + +## 7 General NG-RAN UE Positioning procedures + +### 7.1 General LPP procedures for UE Positioning + +#### 7.1.1 LPP procedures + +Positioning procedures in the NG-RAN are modelled as transactions of the LPP protocol using the procedures defined in this specification. A procedure consists of a single operation of one of the following types: + +- Exchange of positioning capabilities; +- Transfer of assistance data; +- Transfer of location information (positioning measurements and/or position estimate); +- Error handling; +- Abort. + +Parallel transactions are permitted (i.e. a new LPP transaction may be initiated, while another one is outstanding). + +As described in clause 6.2.1, the protocol operates between a "target" and a "server". In the control-plane context, these entities are the UE and LMF respectively; in the SUPL context they are the SET and the SLP. A procedure may be initiated by either the target or the server. + +#### 7.1.2 Positioning procedures + +##### 7.1.2.1 Capability transfer + +The capability transfer procedure between a "target" and a "server" is specified in clause 7.1.2.1 of TS 36.305 [25]. + +##### 7.1.2.2 Assistance data transfer + +The assistance data transfer procedure between a "target" and a "server" is specified in clause 7.1.2.2 of TS 36.305 [25]. + +##### 7.1.2.3 Location information transfer + +The location information transfer procedure between a "target" and a "server" is specified in clause 7.1.2.3 of TS 36.305 [25]. + +##### 7.1.2.4 Multiple transactions + +Multiple LPP transactions may be in progress simultaneously as specified in clause 7.1.2.4 of TS 36.305 [25]. + +##### 7.1.2.5 Sequence of procedures + +LPP procedures are not required to occur in any fixed order, in order to provide greater flexibility in positioning. Thus, a UE may request assistance data at any time in order to comply with a previous request for location measurements from the LMF; an LMF may instigate more than one request for location information (e.g., measurements or a location estimate) in case location results from a previous request were not adequate for the requested QoS; and the target device may transfer capability information to the server at any time if not already performed. + +Despite the flexibility allowed by LPP, it is expected that procedures will normally occur in the following order: + +1. Capability Transfer; +2. Assistance Data Transfer; +3. Location Information Transfer (measurements and/or location estimate). + +Specific examples for each positioning method are shown in clause 8. + +### 7.1.2.6 Error handling + +The error handling procedure is specified in clause 7.1.2.6 of TS 36.305 [25]. + +### 7.1.2.7 Abort + +The abort procedure is specified in clause 7.1.2.7 of TS 36.305 [25]. + +## 7.1.3 UE positioning measurements in RRC\_IDLE state for NB-IoT + +NB-IoT UEs may perform measurements for some positioning methods only when in RRC\_IDLE state. + +Figure 7.1.3-1 shows the general positioning procedure where the UE performs positioning measurements in RRC\_IDLE state. + +![Sequence diagram illustrating the UE positioning procedure in RRC_IDLE state for NB-IoT. The diagram shows interactions between UE, ng-eNB, AMF, and LMF. The process starts with LPP Capability Transfer (1/2) from LMF to UE via AMF and ng-eNB. This is followed by LPP Assistance Data Delivery (3) from AMF to UE via ng-eNB. Then, LPP Request Location Information (4/5) is sent from AMF to UE via ng-eNB. An inactivity timer expires at the AMF, leading to RRC Connection Release from ng-eNB to UE and UE Context Release from AMF to ng-eNB. The UE then performs Location Measurements (7) and sends a UE Triggered Service Request or Connection Resume (8) to the AMF. Finally, the AMF sends LPP Provide Location Information (9) to the UE via ng-eNB. A vertical double-headed arrow on the left indicates the 'LPP Response Time' from step 4/5 to step 9.](822e033872d5ab16e861571f47b81ba7_img.jpg) + +Sequence diagram illustrating the UE positioning procedure in RRC\_IDLE state for NB-IoT. The diagram shows interactions between UE, ng-eNB, AMF, and LMF. The process starts with LPP Capability Transfer (1/2) from LMF to UE via AMF and ng-eNB. This is followed by LPP Assistance Data Delivery (3) from AMF to UE via ng-eNB. Then, LPP Request Location Information (4/5) is sent from AMF to UE via ng-eNB. An inactivity timer expires at the AMF, leading to RRC Connection Release from ng-eNB to UE and UE Context Release from AMF to ng-eNB. The UE then performs Location Measurements (7) and sends a UE Triggered Service Request or Connection Resume (8) to the AMF. Finally, the AMF sends LPP Provide Location Information (9) to the UE via ng-eNB. A vertical double-headed arrow on the left indicates the 'LPP Response Time' from step 4/5 to step 9. + +**Figure 7.1.3-1: UE positioning measurements in RRC\_IDLE state.** + +1. The LMF is aware of the UE access type and/or coverage level if applicable from the Location Service Request message received from the AMF. The LMF may send a LPP Request Capabilities message to the UE to obtain the UE positioning method capabilities from the UE, as described in clause 7.1.2.1. +2. The UE sends its positioning method capabilities to the LMF in a LPP Provide Capabilities message, including an indication of position methods for which the UE needs to make measurements in RRC\_IDLE state. +3. The LMF may determine the assistance data required for the selected position method or methods, and sends them in one or more LPP Provide Assistance data messages to the UE, as described in clause 7.1.2.2. If an LPP acknowledgement was requested, the UE sends an LPP acknowledgment for each received LPP Provide Assistance data message to the LMF. +4. If the UE capabilities from step 2 indicate that RRC\_IDLE state is required for positioning measurements, the LMF may allow additional response time to the UE to obtain the location measurements, and sends one or more LPP Request Location Information messages to the UE requesting positioning measurements or a location estimate, and including the required response time, as described in clause 7.1.2.3. For E-CID positioning method, when NRSRP/NRSRQ measurements are requested the UE is requested to provide NRSRP/NRSRQ measurements for intra-frequency neighbour cells and for inter-frequency neighbour cells. The UE may use inter-frequency information in system information of the serving cell specified in TS 36.331 [13] to decide on which inter-frequency cells to measure. + +5. The UE sends an LPP acknowledgement for each received LPP Request Location Information message to the LMF, if an LPP acknowledgement was requested at step 4 but does not perform the requested measurements. +6. The UE may finish any other activities in progress (e.g., SMS or data transfer), and waits until the network releases or suspends the connection (after a certain period of inactivity). The UE will then receive an RRC connection release or suspend from the ng-eNB due to the expiration of the inactivity timer. +7. When the UE has entered RRC\_IDLE state, the UE performs the measurements requested in step 4. +8. Before the location measurements are to be sent to the LMF, the UE initiates a UE-triggered service request or, when User Plane CIoT 5GC optimization applies, the Connection Resume procedure as defined in TS 23.501 [2], if the UE is not using Control Plane CIoT 5GC Optimisation, in order to establish a signalling connection with the AMF. If the UE is using Control Plane CIoT 5GC Optimisation, procedures for Mobile Originated Data Transport in Control Plane CIoT 5GC optimisation as defined in TS 23.501 [2] are performed by the UE to establish a signalling connection with the AMF. +9. When the LPP response time received in step 4 expires (or when location measurements are available before expiry), the UE sends one or more LPP Provide Location Information messages containing the requested location measurements or location estimate obtained in step 7 to the LMF. + +## 7.2 General NRPPa Procedures for UE Positioning + +### 7.2.1 NRPPa procedures + +Positioning and data acquisition transactions between a LMF and NG-RAN node are modelled by using procedures of the NRPPa protocol. There are two types of NRPPa procedures: + +- UE associated procedure, i.e. transfer of information for a particular UE, including the procedures supporting the Positioning Information Transfer, E-CID Location Information Transfer and Measurement Preconfiguration Information Transfer functions; +- Non UE associated procedure, i.e. transfer of information applicable to the NG-RAN node and associated TRP, including the procedures supporting the OTDOA Information Transfer, Assistance Information Transfer, TRP Information Transfer, Measurement Information Transfer and PRS Information Transfer functions. + +Parallel transactions between the same LMF and NG-RAN node are supported; i.e. a pair of LMF and NG-RAN node may have more than one instance of an NRPPa procedure in execution at the same time. + +For possible extensibility, the protocol is considered to operate between a generic "access node" (e.g. gNB, ng-eNB) and a "server" (e.g. LMF). An NRPPa transaction is only initiated by the server. + +![Sequence diagram illustrating a single NRPPa transaction between a server (LMF) and an access node (gNB/ng-eNB).](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) + +The diagram shows a sequence of messages between two entities. The left entity (server) sends a request message to the right entity (access node). The right entity responds with a response message. A dashed line indicates a subsequent message from the right entity to the left entity. The diagram is a simplified representation of a single NRPPa transaction. + +Sequence diagram illustrating a single NRPPa transaction between a server (LMF) and an access node (gNB/ng-eNB). + +**Figure 7.2.1-1: A single NRPPa transaction** + +Figure 7.2.1-1 shows a single NRPPa transaction. The transaction is terminated in step 2 in procedures including OTDOA Information Exchange, TRP Information Exchange, PRS Configuration Exchange and Measurement Preconfiguration. For procedures such as Positioning Information Exchange, Measurement and E-CID Measurement Initiation, additional responses may be allowed (e.g. sending of updated information periodically and/or whenever there is some significant change). In this case, the transaction may be ended after some additional responses. In the NRPPa + +protocol, the described transaction may be realized by the execution of one procedure defined as a request and a response, followed by one or several procedures initiated by the NG-RAN node (each procedure defined as a single message) to realize the additional responses. The Correlation ID, as specified in TS 29.572 [33], included by the LMF when it invokes the Namf\_Communication\_N1N2MessageTransfer AMF service operation to transfer the NRPPa PDU may be used by the LMF to identify the target UE positioning session. + +## 7.2.2 NRPPa transaction types + +### 7.2.2.1 Location information transfer + +The term "location information" in this clause refers to the information used in, or used for assisting in, computing position (e.g., cell information, SRS configurations, radio measurements or positioning measurements). It is delivered in response to a request. + +![Sequence diagram illustrating the Location information transfer procedure between a server (LMF) and an NG-RAN node. The diagram shows three steps: 1. A dashed arrow from the server to the NG-RAN node representing a request. 2. A solid arrow from the NG-RAN node to the server representing the response. 3. A second dashed arrow from the NG-RAN node to the server representing additional information transfer.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +``` + +sequenceDiagram + participant Server + participant NG-RAN + Note left of Server: Request for location information + Server-->>NG-RAN: Request (dashed arrow) + NG-RAN-->>Server: Response (solid arrow) + Note right of NG-RAN: Additional information + NG-RAN-->>Server: Additional info (dashed arrow) + +``` + +Sequence diagram illustrating the Location information transfer procedure between a server (LMF) and an NG-RAN node. The diagram shows three steps: 1. A dashed arrow from the server to the NG-RAN node representing a request. 2. A solid arrow from the NG-RAN node to the server representing the response. 3. A second dashed arrow from the NG-RAN node to the server representing additional information transfer. + +**Figure 7.2.2-1: Location information transfer** + +1. The server sends a request for location related information to the NG-RAN node, and indicates the type of location information needed. The request may refer to a particular UE. +2. In response to step 1, the NG-RAN Node transfers location related information to the server. The location related information transferred should match the location related information requested in step 1. +3. If requested in step 1, the NG-RAN node may transfer additional location related information to the server in one or more additional NRPPa messages. + +## 7.3 Service Layer Support using combined LPP and NRPPa Procedures + +### 7.3.1 General + +As described in TS 23.502 [26] and TS 23.273 [35], UE-positioning-related services can be instigated from the 5GC for an NI-LR or MT-LR location service, or from the UE in case of an MO-LR location service. The complete sequence of operations in the 5GC is defined in TS 23.502 [26] and TS 23.273 [35]. This clause defines the overall sequences of operations that occur in the LMF, NG-RAN and UE as a result of the 5GC operations. + +### 7.3.2 NI-LR and MT-LR Service Support + +Figure 7.3.2-1 shows the sequence of operations for an NI-LR or MT-LR location service, starting at the point where the AMF initiates the service in the LMF. + +![Figure 7.3.2-1: UE Positioning Operations to support an MT-LR or NI-LR. The diagram shows a sequence of interactions between four entities (UEs) and a central network element (LMF). The sequence starts with the first UE sending a request to the LMF. The LMF then interacts with the second and third UEs, and finally the fourth UE, to obtain location information. The LMF returns a response to the first UE.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +The diagram illustrates the sequence of operations for UE positioning. It features four rectangular boxes at the top representing User Equipment (UEs). Below them is a long horizontal bar representing the Location Management Function (LMF). Vertical lines connect each UE to the LMF. Arrows indicate the flow of messages: from the first UE to the LMF, from the LMF to the second and third UEs, from the third UE back to the LMF, and from the LMF to the fourth UE. Finally, an arrow points from the LMF back to the first UE. + +Figure 7.3.2-1: UE Positioning Operations to support an MT-LR or NI-LR. The diagram shows a sequence of interactions between four entities (UEs) and a central network element (LMF). The sequence starts with the first UE sending a request to the LMF. The LMF then interacts with the second and third UEs, and finally the fourth UE, to obtain location information. The LMF returns a response to the first UE. + +**Figure 7.3.2-1: UE Positioning Operations to support an MT-LR or NI-LR** + +1. The AMF sends a location request to the LMF for a target UE and may include associated QoS, the scheduled location time and the UE LPP positioning capabilities when available, as described in TS 23.273 [35]. +2. The LMF may obtain location related information from the UE and/or from the serving NG-RAN Node. In the former case, the LMF instigates one or more LPP procedures to transfer UE positioning capabilities, provide assistance data to the UE and/or obtain location information from the UE. The UE may also instigate one or more LPP procedures after the first LPP message is received from the LMF (e.g., to request assistance data from the LMF). If a scheduled location time is provided in step 1, the LMF may schedule location measurements by the UE to occur at or near to the scheduled location time. The LPP procedures to transfer UE LPP positioning capabilities may be skipped if the LMF already obtained the UE positioning capabilities from the AMF in step 1. +3. If the LMF needs location related information for the UE from the NG-RAN, the LMF instigates one or more NRPPa procedures. Step 3 is not necessarily serialised with step 2; if the LMF and NG-RAN Node have the information to determine what procedures need to take place for the location service, step 3 could precede or overlap with step 2. If a scheduled location time is provided in step 1, the LMF may schedule location measurements by the NG-RAN to occur at or near to the scheduled location time. +4. The LMF returns a location response to the AMF with any location estimate obtained as a result of steps 2 and 3. The LMF may also return the LPP UE capabilities as described in TS 23.273 [35]. + +NOTE: The LMF may send a location request to the UE at step 2 containing the scheduled location time sometime before the scheduled location time to allow the UE to enter CM Connected state shortly before the scheduled location time. + +### 7.3.3 MO-LR Service Support + +Figure 7.3.3-1 shows the sequence of operations for an MO-LR service, starting at the point where an LCS Client in the UE or the user has requested some location service (e.g., retrieval of the UE's location or transfer of the UE's location to a third party or transfer of the Mobile TRP's location to LMF as specified in TS 23.273 [35]). + +![Sequence diagram illustrating UE Positioning Operations to support an MO-LR. The diagram shows interactions between UE, NG-RAN, AMF, and LMF. The sequence is: 1. UE sends MO-LR Request (LPP PDU) to AMF; 2. AMF sends Location Request (LPP PDU) to LMF; 3. LPP Procedures (between AMF and LMF); 4. NRPPa procedures (between NG-RAN and LMF); 5. LMF sends Location Response to AMF; 6. AMF transfers location to 3rd Party (dashed box); 7. AMF sends MO-LR Response to UE.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note right of AMF: 1. MO-LR Request (LPP PDU) + AMF->>LMF: 2. Location Request (LPP PDU) + Note over AMF, LMF: 3. LPP Procedures + Note over NG-RAN, LMF: 4. NRPPa procedures + LMF->>AMF: 5. Location Response + Note right of AMF: 6. Transfer to 3rd Party + AMF->>UE: 7. MO-LR Response + +``` + +Sequence diagram illustrating UE Positioning Operations to support an MO-LR. The diagram shows interactions between UE, NG-RAN, AMF, and LMF. The sequence is: 1. UE sends MO-LR Request (LPP PDU) to AMF; 2. AMF sends Location Request (LPP PDU) to LMF; 3. LPP Procedures (between AMF and LMF); 4. NRPPa procedures (between NG-RAN and LMF); 5. LMF sends Location Response to AMF; 6. AMF transfers location to 3rd Party (dashed box); 7. AMF sends MO-LR Response to UE. + +**Figure 7.3.3-1: UE Positioning Operations to support an MO-LR** + +1. The UE sends an MO-LR location service request message included in a UL NAS TRANSPORT message as specified in TS 24.501 [29] to the AMF. The MO-LR location service request message may carry an LPP PDU to instigate one or more LPP procedures to transfer capabilities, request assistance data, and/or transfer location information and the scheduled location time, as described in TS 23.273 [35]. +2. The AMF invokes the Nlmf Determine Location Request service operation towards the LMF as specified in TS 29.572 [33] and includes any LPP PDU, the scheduled location time received in step 1 and the UE LPP positioning capabilities when available. +3. The LMF may obtain location related information from the UE and/or from the serving NG-RAN node. In the former case or if an immediate response is needed to any LPP procedure instigated by the UE in step 1 (e.g., a request for assistance data), the LMF instigates one or more LPP procedures to transfer UE positioning capabilities, provide assistance data to the UE and/or obtain location information from the UE. The UE may also instigate further LPP procedures after the first LPP message is received from the LMF (e.g., to request assistance data or to request further assistance data). If a scheduled location time is provided in step 2, the LMF may schedule location measurements by the UE to occur at or near to the scheduled location time. The LPP procedures to transfer UE positioning capabilities may be skipped if the LMF already obtained the UE positioning capabilities from the AMF in step 2. +4. If the LMF needs location related information for the UE from the NG-RAN, the LMF instigates one or more NRPPa procedures. Step 4 may also precede step 3 or occur in parallel with it. If a scheduled location time is provided in step 1, the LMF may schedule location measurements by the NG-RAN to occur at or near to the scheduled location time. +5. The LMF invokes the Nlmf Determine Location Response service operation towards the AMF as specified in TS 29.572 [33] which includes any location estimate obtained as a result of steps 3 and 4. The LMF may also return the LPP UE capabilities as described in TS 23.273 [35]. +6. If the UE requested location transfer to a third party the AMF transfers the location received from the LMF in step 5 to the third party as defined in TS 23.273 [35]. +7. The AMF sends an MO-LR location service response message included in a DL NAS TRANSPORT message as specified in TS 24.501 [29]. + +### 7.3.4 Deferred MT-LR Event Reporting Support + +Figure 7.3.4-1 shows the sequence of operations for a Deferred MT-LR Event Reporting starting at the point where the UE reports an event to the LMF. + +![Sequence diagram illustrating UE Positioning Operations to support a Deferred MT-LR. The diagram shows five entities: UE, NG-RAN, AMF, GMLC, and LMF. The sequence of operations is: 1. Event Report from UE to LMF (via AMF); 2. Need for Positioning from LMF to AMF; 3. LPP Transaction(s) between UE and LMF (via AMF); 4. NRPPa Transaction(s) between NG-RAN and LMF (via AMF); 5. Event Notification from LMF to GMLC.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant GMLC + participant LMF + Note right of LMF: 2. Need for Positioning + UE->>LMF: 1. Event Report + LMF->>AMF: 2. Need for Positioning + Note over UE, LMF: 3. LPP Transaction(s) + Note over NG-RAN, LMF: 4. NRPPa Transaction(s) + LMF->>GMLC: 5. Event Notification + +``` + +Sequence diagram illustrating UE Positioning Operations to support a Deferred MT-LR. The diagram shows five entities: UE, NG-RAN, AMF, GMLC, and LMF. The sequence of operations is: 1. Event Report from UE to LMF (via AMF); 2. Need for Positioning from LMF to AMF; 3. LPP Transaction(s) between UE and LMF (via AMF); 4. NRPPa Transaction(s) between NG-RAN and LMF (via AMF); 5. Event Notification from LMF to GMLC. + +**Figure 7.3.4-1: UE Positioning Operations to support a Deferred MT-LR** + +1. The UE sends a supplementary services event report message to the LMF as described in TS 24.571 [41] which is transferred via the serving AMF and is delivered to the LMF using an Namf\_Communication\_N1MessageNotify service operation. The event report may indicate the type of event being reported and may include an embedded positioning message which includes any location measurements or location estimate, protection level and achievable target integrity risk. +2. If LMF determines no positioning procedure is needed, steps 3 and 4 are skipped. +3. The LMF may utilize any location information received in step 1. The LMF may also retrieve location related information from the UE and/or from the serving NG-RAN Node. In the former case, the LMF instigates one or more LPP procedures to provide assistance data to the UE and/or obtain location information from the UE. The UE may also instigate one or more LPP procedures after the first LPP message is received from the LMF (e.g., to request assistance data from the LMF). +4. If the LMF needs location related information for the UE from the NG-RAN, the LMF instigates one or more NRPPa procedures. Step 4 is not necessarily serialised with step 3; if the LMF and NG-RAN Node have the information to determine what procedures need to take place for the location service, step 4 could precede or overlap with step 3. +5. The LMF invokes an Nlmf\_Location\_EventNotify service operation towards the GMLC with an indication of the type of event being reported and any location estimate obtained as a result of steps 3 and 4. + +## 7.3A Service Layer Support for Sidelink Positioning + +### 7.3A.1 General + +As described in TS 23.273 [35], UE-positioning-related services can be instigated from the 5GC for an SL-MT-LR location service to obtain ranging/sidelink positioning location results for a group of UEs, or from the UE in case of an SL-MO-LR location service to obtain sidelink positioning/ranging location results using one or more other UEs with the assistance of an LMF. The complete sequence of operations in the 5GC is defined in TS 23.273 [35]. This clause defines the overall sequences of operations that occur in the LMF and UE. + +### 7.3A.2 SL-MT-LR Service Support + +Figure 7.3A.2-1 shows the sequence of operations for an SL-MT-LR location service, starting at the point where the AMF initiates the service in the LMF. + +![Sequence diagram illustrating UE Positioning Operations to support an SL-MT-LR. The diagram shows interactions between UEn, UE2, UE1, NG-RAN, AMF, and LMF. The sequence starts with a Location Request from AMF to LMF, followed by an SL-MT-LR Request from LMF to UE1. UE1 then performs UE Discovery and SLPP Capability Transfer. UE1 sends an SL-MT-LR Response to LMF. The LMF may request Supplementary RSPP Capability Transfer, Assistance Data Transfer, and Location Information Transfer from UE1. UE1 may also perform SLPP Capability Transfer, Assistance Data Transfer, and Location Information Transfer with UE2 to n. Finally, the LMF sends a Location Response to the AMF.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant UEn + participant UE2 + participant UE1 + participant NG-RAN + participant AMF + participant LMF + + Note right of AMF: 1. Location Request + AMF->>LMF: 1. Location Request + Note right of LMF: 2. SL-MT-LR Request + LMF->>AMF: 2. SL-MT-LR Request + Note left of AMF: 3. UE Discovery + AMF->>UE1: 3. UE Discovery + Note left of AMF: 4. SLPP Capability Transfer + AMF->>UE1: 4. SLPP Capability Transfer + Note right of AMF: 5. SL-MT-LR Response + AMF->>LMF: 5. SL-MT-LR Response + Note right of LMF: 6a. Supplementary RSPP Capability Transfer + LMF->>AMF: 6a. Supplementary RSPP Capability Transfer + Note left of AMF: 6b. SLPP Capability Transfer + AMF->>UE1: 6b. SLPP Capability Transfer + Note right of LMF: 7a. Supplementary RSPP Assistance Data Transfer + LMF->>AMF: 7a. Supplementary RSPP Assistance Data Transfer + Note left of AMF: 7b. SLPP Assistance Data Transfer + AMF->>UE1: 7b. SLPP Assistance Data Transfer + Note right of LMF: 8a. Supplementary RSPP Location Information Transfer + LMF->>AMF: 8a. Supplementary RSPP Location Information Transfer + Note left of AMF: 8b. SLPP Location Information Transfer + AMF->>UE1: 8b. SLPP Location Information Transfer + Note right of AMF: 9. Location Response + AMF->>LMF: 9. Location Response + +``` + +Sequence diagram illustrating UE Positioning Operations to support an SL-MT-LR. The diagram shows interactions between UEn, UE2, UE1, NG-RAN, AMF, and LMF. The sequence starts with a Location Request from AMF to LMF, followed by an SL-MT-LR Request from LMF to UE1. UE1 then performs UE Discovery and SLPP Capability Transfer. UE1 sends an SL-MT-LR Response to LMF. The LMF may request Supplementary RSPP Capability Transfer, Assistance Data Transfer, and Location Information Transfer from UE1. UE1 may also perform SLPP Capability Transfer, Assistance Data Transfer, and Location Information Transfer with UE2 to n. Finally, the LMF sends a Location Response to the AMF. + +**Figure 7.3A.2-1: UE Positioning Operations to support an SL-MT-LR.** + +1. The AMF serving UE1 sends a location request to the LMF including information on the required location results of the n UEs (e.g., absolute location, relative location or ranges and directions between pairs of UE(s)), the required LCS QoS and the Application layer IDs of the UEs when available, as described in TS 23.273 [35]. +2. The LMF sends an SL-MT-LR request to UE1 (via serving AMF) including the types of required location results (e.g., absolute location, relative locations or distances and/or directions) and the Application layer IDs of the other UEs 2 to n. +3. UE1 attempts to discover the other UEs 2 to n using their Application layer IDs if not already discovered, as described in TS 23.273 [35]. +4. UE1 obtains the sidelink positioning capabilities of the discovered UEs using the SLPP capability transfer procedures specified in clause 7.11.2.1. +5. UE1 returns a SL-MT-LR Response to the LMF (via serving AMF) indicating which of the UEs 2 to n have been discovered and the sidelink positioning capabilities of the discovered UEs, if obtained. +- 6a. The LMF may request the sidelink positioning capabilities of the UEs 1 to n from UE1 if not already received at step 5 using the Supplementary RSPP Capability Transfer procedure. The Supplementary RSPP Capability Transfer messages include embedded SLPP Capability Transfer messages for UEs 1 to n together with their Application Layer IDs. UE1 may instigate the procedure for step 6b and returns the obtained capabilities of the UEs to the LMF using the Supplementary RSPP Capability Transfer procedure which includes embedded SLPP Capability Transfer messages for UEs 1 to n together with their Application Layer IDs. +- 6b. UE1 may instigate the SLPP Capability Transfer procedure specified in clause 7.11.2.1 with UEs 2 to n to obtain the sidelink positioning capabilities for UEs 2 to n, if not already obtained (e.g., at step 4). +- 7a. UE1 may send a request for specific sidelink assistance data to the LMF using the Supplementary RSPP Assistance Data Transfer procedure. The Supplementary RSPP Assistance Data Transfer messages include embedded SLPP Request Assistance Data messages for UEs 1 to n together with their Application Layer IDs. The LMF determines the sidelink assistance data, possibly taking the received UE capabilities from step 4 or 6a into account and provides the assistance data to UE1 using the Supplementary RSPP Assistance Data Transfer procedure which includes embedded SLPP Assistance Data Transfer messages for UEs 1 to n together with their Application Layer IDs. +- 7b. UE1 may instigate the SLPP Assistance Data Transfer procedure specified in clause 7.11.2.2 with UEs 2 to n to provide the received assistance data from step 7a to the UEs 2 to n. The assistance data may assist UEs 1 to n to obtain sidelink location measurements and/or may assist UE1 to calculate sidelink positioning/ranging location results. + +- 8a. The LMF sends a request for sidelink location information to UE1 using the Supplementary RSPP Location Information Transfer procedure. The Supplementary RSPP Location Information Transfer messages include embedded SLPP Location Information Transfer messages for UEs 1 to n together with their Application Layer IDs. The request may include an indication whether location calculation should be performed by the UEs (Target UE-based), or whether location measurements should be provided for location calculation at the LMF (Target UE-assisted). UE1 may instigate the procedure for step 8b and provides the sidelink location measurements or location estimates to the LMF using the Supplementary RSPP Location Information Transfer procedure which includes embedded SLPP Location Information Transfer messages for UEs 1 to n together with their Application Layer IDs. +- 8b. UE1 instigates the SLPP Location Information Transfer procedure specified in clause 7.11.2.3 among UEs 1 to n in which UE1 to n obtain sidelink location measurements and UEs 2 to n transfer their sidelink location measurements to UE1. +- NOTE 1: Steps 6a, 7a, 8a and 6b, 7b, 8b could be performed in any order and may also overlap. +- NOTE 2: Steps 6b, 7b, and 8b are not necessarily serialised with steps 6a, 7a, and 8a, respectively. +9. The LMF returns a location response to the AMF with any sidelink positioning/ranging location results obtained as a result of steps 6 to 8. + +### 7.3A.3 SL-MT-LR Service Support for periodic, triggered Location Events + +Figure 7.3A.3-1 shows the sequence of operations for an SL-MT-LR location service for periodic and triggered location events, starting at the point where the AMF initiates the service in the LMF. + +![Sequence diagram showing UE Positioning Operations to support an SL-MT-LR for periodic, triggered Location Events. The diagram illustrates the interaction between UEs (UE1, UE2, UEn), NG-RAN, AMF, and LMF. The process starts with the AMF sending a Location Request to the LMF. The LMF responds with a Periodic-Triggered SL-MT-LR Request to the AMF, which is then passed to UE1. UE1 initiates UE Discovery and SLPP Capability Transfer with other UEs. The LMF sends a Periodic-Triggered SL-MT-LR Response to the AMF. The AMF then sends a Location Response to the LMF. The diagram also shows SLPP Transactions (6a, 6b, 8, 12a, 12b, 14) and Event Detection/Report/Acknowledgement (9, 10, 11). Finally, the LMF sends an Event Notification to GMLC/NEF/AF/LCS Client, and the AMF sends another SLPP Transaction (14) to the UEs. The diagram ends with another Event Detection (15) at UE1.](3493d7ba4c86f944e159de1bf45ff03d_img.jpg) + +``` + +sequenceDiagram + participant UEn + participant UE2 + participant UE1 + participant NG-RAN + participant AMF + participant LMF + + Note left of UEn: ... + AMF->>LMF: 1. Location Request + LMF-->>AMF: 2. Periodic-Triggered SL-MT-LR Request + AMF-->>UE1: 2. Periodic-Triggered SL-MT-LR Request + UE1->>UE2: 3. UE Discovery + UE2-->>UE1: 4. SLPP Capability Transfer + LMF-->>AMF: 5. Periodic-Triggered SL-MT-LR Response + AMF-->>LMF: 7. Location Response + Note right of LMF: 6a. SLPP Transaction(s) + Note left of AMF: 6b. SLPP Transaction(s) + Note left of AMF: 8. SLPP Transaction(s) + Note right of UE1: 9. Event Detected + UE1->>LMF: 10. Event Report + LMF-->>UE1: 11. Event Report Acknowledgement + Note right of LMF: 12a. SLPP Transaction(s) + Note left of AMF: 12b. SLPP Transaction(s) + Note right of AMF: 13. Event Notification to GMLC/NEF/AF/LCS Client + Note right of LMF: 14. SLPP Transaction(s) + Note left of AMF: 14. SLPP Transaction(s) + Note right of UE1: 15. Event Detected + +``` + +Sequence diagram showing UE Positioning Operations to support an SL-MT-LR for periodic, triggered Location Events. The diagram illustrates the interaction between UEs (UE1, UE2, UEn), NG-RAN, AMF, and LMF. The process starts with the AMF sending a Location Request to the LMF. The LMF responds with a Periodic-Triggered SL-MT-LR Request to the AMF, which is then passed to UE1. UE1 initiates UE Discovery and SLPP Capability Transfer with other UEs. The LMF sends a Periodic-Triggered SL-MT-LR Response to the AMF. The AMF then sends a Location Response to the LMF. The diagram also shows SLPP Transactions (6a, 6b, 8, 12a, 12b, 14) and Event Detection/Report/Acknowledgement (9, 10, 11). Finally, the LMF sends an Event Notification to GMLC/NEF/AF/LCS Client, and the AMF sends another SLPP Transaction (14) to the UEs. The diagram ends with another Event Detection (15) at UE1. + +Figure 7.3A.3-1: UE Positioning Operations to support an SL-MT-LR for periodic, triggered Location Events. + +1. The AMF serving UE1 sends a location request to the LMF to request periodic or triggered sidelink positioning/ranging location results of the n UEs (e.g., absolute locations, relative location or ranges and directions between pairs of UE(s)). The request includes information on the time interval between successive location reports, the total number of reports, and/or the details of the trigger event (e.g., change of location or ranges), the SUPI of UE1, the required LCS QoS and the Application layer IDs of the UEs when available, as described in TS 23.273 [35]. + 2. The LMF sends a Periodic-Triggered SL-MT-LR request to UE1 (via serving AMF) including the information of the periodic or triggered event, the types of required location results (e.g., absolute location, relative locations or distances and/or directions) and the Application layer IDs of the other UEs 2 to n. + 3. UE1 attempts to discover the other UEs 2 to n using their Application layer IDs if not already discovered, as described in TS 23.273 [35]. + 4. UE1 obtains the sidelink positioning capabilities of the discovered UEs using the SLPP capability transfer procedures specified in clause 7.11.2.1. + 5. UE1 returns a Periodic-Triggered SL-MT-LR Response to the LMF (via serving AMF) indicating which of the UEs 2 to n have been discovered, whether the UEs 1 to n accept the periodic or triggered location request, and the sidelink positioning capabilities of the discovered UEs, if obtained. + - 6a. The LMF may instigate one or more SLPP procedures with UE1 to transfer sidelink positioning capabilities for UEs 1 to n, to transfer SLPP assistance data to UE1, and to transfer sidelink location information for UEs 1 to n (e.g., sidelink ranging and/or location measurements or location estimates obtained at step 6b), as described in steps 6 – 8 in Figure 7.3A.2-1. +The UE1 may also instigate one or more SLPP procedures with the LMF after the first SLPP message has been received from the LMF (e.g., to request sidelink assistance data from the LMF). + - 6b. UE1 may instigate one or more SLPP procedures among UEs 1 to n to transfer sidelink positioning capabilities, provide sidelink assistance data to the UEs 2 to n, and/or obtain sidelink location information for UEs 1 to n (e.g., sidelink ranging and/or location measurements or location estimates) as described in steps 6 – 8 in Figure 7.3A.2-1. If UE1 received a SLPP request for sidelink location information at Step 6a, UE1 sends a SLPP response to the LMF and includes the location results obtained at Step 6b. +- NOTE: As described in Figure 7.3A.2-1, the SLPP Transactions between LMF and UE1 may be carried in a Supplementary RSPP message container. +7. The LMF returns a location response to the AMF indicating that the SL-MT-LR for periodic, triggered Location Events has been successfully initiated and with any initial sidelink positioning/ranging location results obtained as a result of steps 6. + 8. The UEs 1 to n may periodically perform sidelink positioning/ranging in order to support steps 9 and 10. The UE may perform steps 6b, 7b, and 8b in Figure 7.3A.2-1. + 9. The UE monitors for occurrence of the trigger or periodic event requested at step 2. + 10. UE1 sends an event report message to the LMF (via serving AMF) indicating the type of event being reported and may include sidelink location results obtained at step 8. + 11. The LMF (via serving AMF) returns an event report acknowledgement to UE1. + 12. If sidelink location results are needed for event reporting and not received at step 10, the LMF may instigate one or more SLPP procedures with UE1 as described in step 6a/6b. + 13. The LMF returns the event report and any sidelink location results to the LCS Client or AF. + 14. The UEs 1 to n continue to periodically perform sidelink positioning/ranging as in step 8. + 15. The UE1 continues to monitor for further periodic or trigger events as in step 9 and instigates steps 10-12 each time a periodic or trigger event is detected. + +### 7.3A.4 SL-MO-LR Service Support + +Figure 7.3A.4-1 shows the sequence of operations for an SL-MO-LR service instigated by UE1 to obtain sidelink positioning/ranging location results using one or more other UEs with the assistance of an LMF. + +![Sequence diagram of UE Positioning Operations to support an SL-MO-LR. The diagram shows interactions between UEn, UE2, UE1, NG-RAN, AMF, and LMF. The sequence starts with UE Discovery and SLPP Capability Transfer between UEs. UE1 then sends an SL-MO-LR Request to the LMF via the AMF. The LMF performs Supplementary RSPP Capability Transfer, Assistance Data Transfer, and Location Information Transfer with UE1. Finally, the LMF sends an SL-MO-LR Response to UE1 via the AMF, and UE1 transfers location results to an AF/LCS Client.](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +``` + +sequenceDiagram + participant UEn + participant UE2 + participant UE1 + participant NG-RAN + participant AMF + participant LMF + + Note left of UEn: 1. UE Discovery + Note left of UEn: 2. SLPP Capability Transfer + UE1->>LMF: 3. SL-MO-LR Request + Note left of UEn: 4b. SLPP Capability Transfer + Note right of LMF: 4a. Supplementary RSPP Capability Transfer + Note left of UEn: 5b. SLPP Assistance Data Transfer + Note right of LMF: 5a. Supplementary RSPP Assistance Data Transfer + Note left of UEn: 6b. SLPP Location Information Transfer + Note right of LMF: 6a. Supplementary RSPP Location Information Transfer + LMF->>AMF: 7. SL-MO-LR Response + AMF->>UE1: + Note right of AMF: 8. Transfer Location Results to AF/LCS Client + +``` + +Sequence diagram of UE Positioning Operations to support an SL-MO-LR. The diagram shows interactions between UEn, UE2, UE1, NG-RAN, AMF, and LMF. The sequence starts with UE Discovery and SLPP Capability Transfer between UEs. UE1 then sends an SL-MO-LR Request to the LMF via the AMF. The LMF performs Supplementary RSPP Capability Transfer, Assistance Data Transfer, and Location Information Transfer with UE1. Finally, the LMF sends an SL-MO-LR Response to UE1 via the AMF, and UE1 transfers location results to an AF/LCS Client. + +**Figure 7.3A.4-1: UE Positioning Operations to support an SL-MO-LR** + +1. Based on a trigger of service request (e.g., received from the application layer in UE1) UE1 discovers the other UEs 2 to n, as described in TS 23.273 [35]. +2. UE1 may obtain the sidelink positioning capabilities of the discovered UEs using the SLPP capability transfer procedures specified in clause 7.11.2.1. +3. UE1 sends an SL-MO-LR Request to the LMF via the serving AMF, including the Application layer IDs of the other UEs 2 to n together with an indication on any sidelink assistance data needed, position calculation assistance from the LMF needed, and/or whether location results should be transferred to an LCS client or AF. For position calculation assistance from the LMF, the SL-MO-LR Request may include information on the type of sidelink positioning/ranging location results (e.g., absolute location, relative location or distances and directions between pairs of UEs) and desired QoS. +- 4a. The LMF may request the sidelink positioning capabilities of the UEs 1 to n from UE1 if not already received at step 3 using the Supplementary RSPP Capability Transfer procedure. The Supplementary RSPP Capability Transfer messages include embedded SLPP Capability Transfer messages for UEs 1 to n together with their Application Layer IDs. UE1 may instigate the procedure for step 4b and returns the obtained capabilities of the UEs to the LMF using the Supplementary RSPP Capability Transfer procedure which includes embedded SLPP Capability Transfer messages for UEs 1 to n together with their Application Layer IDs. +- 4b. UE1 may instigate the SLPP Capability Transfer procedure specified in clause 7.11.2.1 with UEs 2 to n to obtain the sidelink positioning capabilities for UEs 2 to n, if not already obtained (e.g., at step 2). +- 5a. UE1 may send a request for specific sidelink assistance data to the LMF, if the request was not already included at step 3 using the Supplementary RSPP Assistance Data Transfer procedure. The Supplementary RSPP Assistance Data Transfer messages include embedded SLPP Request Assistance Data messages for UEs 1 to n together with their Application Layer IDs. The LMF determines the sidelink assistance data, possibly taking the received UE capabilities from step 2 or 4a into account and provides the assistance data to UE1 using the Supplementary RSPP Assistance Data Transfer procedure which includes embedded SLPP Assistance Data Transfer messages for UEs 1 to n together with their Application Layer IDs. +- 5b. UE1 may instigate the SLPP Assistance Data Transfer procedure specified in clause 7.11.2.2 with UEs 2 to n to provide the received assistance data from step 5a to the UEs 2 to n. The assistance data may assist UEs 1 to n to obtain sidelink location measurements and/or may assist UE1 to calculate sidelink positioning/ranging location results. + +6a. If UE1 requested position calculation assistance from the LMF or location transfer to an LCS client or AF at step 3, the LMF sends a request for sidelink location information to UE1 using the Supplementary RSPP Location Information Transfer procedure. The Supplementary RSPP Location Information Transfer messages include embedded SLPP Location Information Transfer messages for UEs 1 to n together with their Application Layer IDs. The request may also include an indication whether location calculation should be performed by the UEs (SL Target UE-based), or whether location measurements should be provided for location calculation at the LMF (SL Target UE-assisted). UE1 may instigate the procedure for step 6b and provides the sidelink location measurements or location estimates to the LMF using the Supplementary RSPP Location Information Transfer procedure which includes embedded SLPP Location Information Transfer messages for UEs 1 to n together with their Application Layer IDs. + +6b. UE1 instigates the SLPP Location Information Transfer procedure specified in clause 7.11.2.3 among UEs 1 to n in which UE1 to n obtain sidelink location measurements and UEs 2 to n transfer their sidelink location measurements to UE1. + +NOTE 1: Steps 4a, 5a, 6a and 4b, 5b, 6b could be performed in any order and may also overlap. + +NOTE 2: Steps 4b, 5b, and 6b are not necessarily serialised with steps 4a, 5a, and 6a, respectively. + +7. The LMF sends a SL-MO-LR Response to the AMF which forwards the SL-MO-LR Response to UE1. If UE1 requested position calculation assistance at step 3, the SL-MO-LR Response includes the calculated UE locations obtained from step 6. + +8. If requested at step 3, the AMF provides the location results to the AF/LCS Client. + +## 7.4 General RRC procedures for UE Positioning + +### 7.4.1 NR RRC Procedures + +#### 7.4.1.0 General + +NR RRC supports the following positioning related procedures: + +- Location Measurement Indication; +- UE Positioning Assistance Information. + +#### 7.4.1.1 Location Measurement Indication + +The location measurement indication procedure is used by the UE to request measurement gaps for OTDOA RSTD measurements, for subframe and slot timing detection for inter-RAT E-UTRA RSTD measurements, or for NR DL-PRS measurements. + +![Figure 7.4.1.1-1: Location measurement indication procedure. The diagram shows two empty rectangular boxes side-by-side, representing the start and end of the procedure flow.](84db9bf6e93779b67aa320d1dfd38d91_img.jpg) + +Figure 7.4.1.1-1: Location measurement indication procedure. The diagram shows two empty rectangular boxes side-by-side, representing the start and end of the procedure flow. + +**Figure 7.4.1.1-1: Location measurement indication procedure** + +**Precondition:** The UE served by a gNB has received a LPP message from an LMF requesting inter-RAT RSTD measurements for OTDOA positioning or NR DL-PRS measurements. + +1. If the UE requires measurement gaps for performing the requested location measurements while measurement gaps are either not configured or not sufficient, or if the UE needs gaps to acquire the subframe and slot timing + +of the target E-UTRA system before requesting measurement gaps for the inter-RAT RSTD measurements (see TS 38.133 [32], the UE sends an RRC Location Measurement Indication message to the serving gNB. The message indicates that the UE is going to start location measurements, or that the UE is going to acquire subframe and slot timing of the target E-UTRA system, and includes information required for the gNB to configure the appropriate measurement gaps. When the gNB has configured the required measurement gaps the UE performs the location measurements or timing acquisition procedures. + +2. When the UE has completed the location procedures which required measurement gaps, the UE sends another RRC Location Measurement Indication message to the serving gNB. The message indicates that the UE has completed the location measurements or timing acquisition procedures. + +#### 7.4.1.2 UE Positioning Assistance Information + +The UE Positioning Assistance Information procedure is used by UE to report the UE Positioning Assistance Information for UL-TDOA. The UE reports the association between UL-SRS resources for positioning and the UE Tx TEG ID, and the margin value for UE Tx TEGs. + +![Sequence diagram showing the RRC procedure for UE TxTEG between a UE and a gNB. The sequence consists of four steps: 1. RRC Reconfiguration (gNB to UE), 2. RRC UE Positioning Assistance Info (UE to gNB), 3. RRC UE Positioning Assistance Info (UE to gNB), and 4. RRC UE Positioning Assistance Info (UE to gNB).](0997dbaa9dfecedd60029d70b53327b8_img.jpg) + +``` + +sequenceDiagram + participant gNB + participant UE + Note left of gNB: NRPPa from LMF + gNB->>UE: 1. RRC Reconfiguration + UE-->>gNB: 2. RRC UE Positioning Assistance Info + UE-->>gNB: 3. RRC UE Positioning Assistance Info + UE-->>gNB: 4. RRC UE Positioning Assistance Info + +``` + +Sequence diagram showing the RRC procedure for UE TxTEG between a UE and a gNB. The sequence consists of four steps: 1. RRC Reconfiguration (gNB to UE), 2. RRC UE Positioning Assistance Info (UE to gNB), 3. RRC UE Positioning Assistance Info (UE to gNB), and 4. RRC UE Positioning Assistance Info (UE to gNB). + +Figure 7.4.1.2-1: RRC procedure for UE TxTEG + +**Precondition:** The serving gNB of a UE has received a NRPPa message from an LMF requesting the TxTEG of the UE for NR UL-TDOA positioning. + +1. The serving gNB may send a RRC Reconfiguration message to the UE, requesting the UE to provide the association information of UL SRS resources for positioning with Tx TEGs to the serving gNB if the UE supports UE Tx TEG reporting. Based on the request from the LMF, the RRC Reconfiguration message from the serving gNB to the UE indicates the UE should provide either a single report or a periodic report of UE TxTEG association to the serving gNB. +2. When the UE receives the request via RRC Reconfiguration message, the UE sends a UE Positioning Assistance Info message to the serving gNB to report the UE TxTEG information, including all the changes of the UE TxTEG during the report period if the UE is required to report UE Tx TEG periodically. The UE will report all the UE TxTEG at the time when the RRC Reconfiguration message is received if the UE is only required to report the one-shot UE TxTEG information. For each UE Positioning Assistance Info message, only a single margin value can be reported. + +### 7.4.2 LTE RRC Procedures + +#### 7.4.2.0 General + +LTE RRC supports the following positioning related procedures: + +- Inter-frequency RSTD measurement indication. + +#### 7.4.2.1 Inter-frequency RSTD measurement indication + +The Inter-frequency RSTD measurement indication procedure is used by the UE to request measurement gaps for OTDOA RSTD measurements. + +![Placeholder box for a diagram element.](3489a3f420d1f2d8b7d626d3a6851388_img.jpg) + +Placeholder box for a diagram element. + +![Placeholder box for a diagram element.](22c951be5955437ff27274172250e483_img.jpg) + +Placeholder box for a diagram element. + +**Figure 7.4.2.1-1: Inter-frequency RSTD measurement indication procedure** + +**Precondition:** The UE served by an ng-eNB has received a LPP message from an LMF requesting inter-frequency RSTD measurements for OTDOA positioning. + +1. If the UE requires measurement gaps for performing the requested inter-frequency RSTD measurements for OTDOA positioning while measurement gaps are either not configured or not sufficient, the UE sends an RRC Inter-frequency RSTD Measurement Indication message to the serving ng-eNB. The message indicates that the UE is going to start inter-frequency RSTD measurements and includes information required for the ng-eNB to configure the appropriate measurement gaps. When the ng-eNB has configured the required measurement gaps the UE performs the inter-frequency RSTD measurements. +2. When the UE has completed the inter-frequency RSTD measurements which required measurement gaps, the UE sends another RRC Inter-frequency RSTD Measurement Indication message to the serving ng-eNB. The message indicates that the UE has completed the inter-frequency RSTD measurements. + +## 7.5 Procedures for Broadcast of Assistance Data + +### 7.5.1 General + +Positioning assistance data can be included in positioning System Information Blocks (posSIBs) as described in TS 36.331 [13], TS 38.331 [14] and TS 36.355 [19]. The posSIBs are carried in RRC System Information (SI) messages. The mapping of posSIBs (assistance data) to SI messages is flexibly configurable and provided to the UE in SIB1 for NG-RAN node TS 36.331 [13], TS 38.331 [14]. + +The UE may request posSI by means of on-demand SI request in RRC\_IDLE/RRC\_INACTIVE and also request posSIBs by means of on-demand SI request in RRC\_CONNECTED as described in TS 38.331 [14]. U2N Remote UE may also request posSIB via a U2N Relay UE as described in TS 38.331 [14]. The U2N relay UE forwards the posSIB transparently to the U2N Remote UE. + +For each assistance data element, a separate posSIB-type is defined in TS 36.355 [19]. Each posSIB may be ciphered by the LMF using the 128-bit Advanced Encryption Standard (AES) algorithm (with counter mode) as described in TS 36.355 [19], either with the same or different ciphering key. The posSIBs which exceed the maximum size limit defined in TS 36.331 [13], TS 38.331 [14] shall be segmented by the LMF. + +### 7.5.2 Broadcast Procedures + +The general procedures for broadcast of positioning assistance data and delivery of ciphering keys to UEs is described in TS 23.273 [35]. This clause defines the overall sequences of operations that occur in the LMF, NG-RAN node and UE. + +![Sequence diagram illustrating the procedures to support broadcast of assistance data. The diagram shows four lifelines: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. LMF to NG-RAN: NRPPa Assistance Information Control. 2. NG-RAN to UE: RRC System Information Messages (SIB1 and other SIBs). 3. LMF to AMF: Nlmf_Broadcast_CipheringKeyData Notify. 4. AMF to UE: Mobility Management message. 5. NG-RAN to LMF: NRPPa Assistance Information Feedback. 6. LMF to NG-RAN: Updated NRPPa Assistance Information Control. Vertical ellipses indicate repeated or ongoing processes between the UE and NG-RAN, and between the AMF and LMF.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +Sequence diagram illustrating the procedures to support broadcast of assistance data. The diagram shows four lifelines: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. LMF to NG-RAN: NRPPa Assistance Information Control. 2. NG-RAN to UE: RRC System Information Messages (SIB1 and other SIBs). 3. LMF to AMF: Nlmf\_Broadcast\_CipheringKeyData Notify. 4. AMF to UE: Mobility Management message. 5. NG-RAN to LMF: NRPPa Assistance Information Feedback. 6. LMF to NG-RAN: Updated NRPPa Assistance Information Control. Vertical ellipses indicate repeated or ongoing processes between the UE and NG-RAN, and between the AMF and LMF. + +**Figure 7.5.2-1: Procedures to support broadcast of assistance data.** + +1. The LMF sends an NRPPa Assistance Information Control message to the NG-RAN node with an indication to start broadcasting assistance information. The message includes one or more System Information groups, where each group contains the broadcast periodicity and one or more posSIB types together with meta data to be scheduled in the same SI message. Each posSIB type may be ciphered and/or segmented at the LMF. The meta data may include an indication whether the posSIB type in the System Information group is ciphered or not, as well as an indication of an applicable GNSS type. +2. The NG-RAN node includes the received System Information groups in RRC System Information Messages and corresponding scheduling information in SIB1 as described in TS 36.331 [13], TS 38.331 [14]. The UE applies the system information acquisition procedure according to TS 36.331 [13], TS 38.331 [14] for acquiring the assistance data information that is broadcasted. +3. If the posSIB types were ciphered by the LMF, the LMF invokes the Nlmf\_Broadcast\_CipheringKeyData Notify service operation towards the AMF carrying one or more ciphering keys. For each ciphering key, the LMF includes a ciphering key value, a ciphering key identifier, a validity period, a set of applicable tracking areas, and a set of applicable posSIB types. The AMF may then distribute successfully stored ciphering keys and their validity times and validity areas to suitably subscribed UEs using a mobility management message as described in TS 23.273 [35]. The LMF repeats this procedure whenever a ciphering key changes. +4. At any time after Step 1, the NG-RAN node may send a NRPPa Assistance Information Feedback message to the LMF providing feedback on assistance information broadcasting. The message may include an assistance information failure list indicating that certain posSIB types could not be configured for broadcasting by the NG-RAN node. +5. If the assistance information in a System Information group changes, the LMF provides updated information in a NRPPa Assistance Information Control message. +6. The NG-RAN node replaces the previously stored System Information groups with the new information received at Step 5 and includes the new System Information groups in RRC System Information Messages. + +7. If the LMF wants to abort the broadcast of a System Information Group, it sends a NRPPa Assistance Information Control message to the NG-RAN node including an indication to stop broadcasting the assistance information. + +## 7.6 Procedures for On-Demand PRS transmission + +### 7.6.1 General + +On-Demand PRS transmission procedure allows the LMF to control and decide whether PRS is transmitted or not and to change the characteristics of an ongoing PRS transmission. The on-demand PRS transmission procedure can be initiated either by the UE or LMF. The actual PRS changes are requested by the LMF irrespective of whether the procedure is UE- or LMF-initiated. + +### 7.6.2 On-Demand PRS transmission procedures + +Figure 7.6.2-1 shows the general positioning procedure for On-Demand PRS transmission. + +![Sequence diagram of the On-Demand PRS transmission procedure. Lifelines: UE, Serving gNB/TRP, Neighbour gNB/TRP (three instances), and LMF. The sequence starts with '0. NRPPa TRP Information Exchange' between Neighbour gNB/TRPs and LMF. Then, 'UE-initiated On-Demand PRS' is shown, followed by '1. Provide pre-defined PRS configurations' from LMF to UE. '2a. LPP Request Assistance Data (On-Demand PRS Request)' is sent from UE to LMF. Next, 'LMF-initiated On-Demand PRS' is shown, followed by '2b. Possible LPP procedures' from LMF to UE. A box '3. Determine the need for PRS transmission or change to PRS transmission characteristics' is shown on the LMF side. '4. NRPPa PRS CONFIGURATION REQUEST' is sent from LMF to all gNB/TRPs. '5. NRPPa PRS CONFIGURATION RESPONSE' is sent from all gNB/TRPs to LMF. Finally, '6. LPP Provide Assistance Data (On-Demand PRS response)' is sent from LMF to UE.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Serving as Serving gNB/TRP + participant Neighbour1 as Neighbour gNB/TRP + participant Neighbour2 as Neighbour gNB/TRP + participant Neighbour3 as Neighbour gNB/TRP + participant LMF + + Note right of Neighbour3: 0. NRPPa TRP Information Exchange + Note left of UE: UE-initiated On-Demand PRS + Note right of LMF: 1. Provide pre-defined PRS configurations + Note left of UE: 2a. LPP Request Assistance Data (On-Demand PRS Request) + Note left of UE: LMF-initiated On-Demand PRS + Note right of LMF: 2b. Possible LPP procedures + Note right of LMF: 3. Determine the need for PRS transmission or change to PRS transmission characteristics + Note right of LMF: 4. NRPPa PRS CONFIGURATION REQUEST + Note right of LMF: 5. NRPPa PRS CONFIGURATION RESPONSE + Note right of LMF: 6. LPP Provide Assistance Data (On-Demand PRS response) + +``` + +Sequence diagram of the On-Demand PRS transmission procedure. Lifelines: UE, Serving gNB/TRP, Neighbour gNB/TRP (three instances), and LMF. The sequence starts with '0. NRPPa TRP Information Exchange' between Neighbour gNB/TRPs and LMF. Then, 'UE-initiated On-Demand PRS' is shown, followed by '1. Provide pre-defined PRS configurations' from LMF to UE. '2a. LPP Request Assistance Data (On-Demand PRS Request)' is sent from UE to LMF. Next, 'LMF-initiated On-Demand PRS' is shown, followed by '2b. Possible LPP procedures' from LMF to UE. A box '3. Determine the need for PRS transmission or change to PRS transmission characteristics' is shown on the LMF side. '4. NRPPa PRS CONFIGURATION REQUEST' is sent from LMF to all gNB/TRPs. '5. NRPPa PRS CONFIGURATION RESPONSE' is sent from all gNB/TRPs to LMF. Finally, '6. LPP Provide Assistance Data (On-Demand PRS response)' is sent from LMF to UE. + +**Figure 7.6.2-1: On-Demand PRS transmission procedure** + +0. The LMF may receive information on the possible On-Demand PRS configurations that the gNB can support during the TRP Information Exchange procedure. +1. In case of UE-initiated On-Demand PRS, the LMF may configure the UE with pre-defined PRS configurations via LPP Provide Assistance Data message or via posSI. +- 2a. In case of UE-initiated On-Demand PRS, the UE sends an On-Demand PRS request to the LMF via LPP Request Assistance Data message. The On-Demand PRS request can be a request for a pre-defined PRS configuration indicated with pre-defined PRS configuration ID or explicit parameter for PRS configuration and may be a request for PRS transmission or change to the PRS transmission characteristics for positioning measurements. + +NOTE 1: The LPP Request Assistance Data message for On-Demand PRS may also be sent in an MO-LR location service request message. + +- NOTE 2: If the NW has provided the pre-defined On-Demand PRS configurations to the UE, the UE is allowed to request On-Demand PRS parameters based on pre-defined PRS configuration ID (index-based request) or explicit parameter requests that is within the scope of the received pre-defined On-Demand PRS configurations. Otherwise, the UE may blindly request On-Demand PRS parameters via an explicit request within the scope of the allowed parameter list, as specified in TS37.355 [42]. +- 2b. In case of LMF-initiated On-Demand PRS, the LMF and the UE may exchange LPP messages e.g., to obtain UE measurements or the DL-PRS positioning capabilities of the UE, etc. +3. The LMF determines the need for PRS transmission or change to the transmission characteristics of an ongoing PRS transmission. +4. The LMF requests the serving and non-serving gNBs/TRPs for new PRS transmission or PRS transmission with changes to the PRS configuration via NRPPa PRS CONFIGURATION REQUEST message. +5. The gNBs/TRPs provide the successfully configured or updated PRS transmission in the NRPPa PRS CONFIGURATION RESPONSE message accordingly. +6. LMF may provide the PRS configuration used for PRS transmission or error cause via LPP Provide Assistance Data message to the UE. +- NOTE 3: If the LPP Request Assistance Data for On-Demand DL-PRS at Step 2a was sent in an MO-LR location service request message, the LMF provides a MO-LR response as described in clause 7.3.3. +- NOTE 4: It is up to Network (LMF) implementation on the steps to follow (accept/reject/ignore) on receiving UE-initiated On-Demand PRS request. +- NOTE 5: It is up to Network (TRP) implementation on the steps to follow (accept/reject/ignore) on receiving LMF-initiated On-Demand PRS requests. +- NOTE 6: The UE may utilize the UE-initiated on-demand DL-PRS procedure to request a DL-PRS configuration which aligns with any configured (e)DRX, e.g., by setting the explicit parameter for the DL-PRS configuration accordingly. +- NOTE 7: The on-demand DL-PRS procedure may also be used to request a DL-PRS configuration which supports bandwidth aggregation across DL-PRS positioning frequency layers. + +## 7.7 Procedures for Pre-configured Measurement Gap + +### 7.7.1 General + +The pre-configured measurement gap procedure is used by the network to provide measurement gap for NR DL-PRS measurements. The serving gNB may activate/deactivate the pre-configured measurement gap upon receiving the request from a UE or LMF. + +NOTE: The pre-configured measurement gap procedure is not supported for a U2N Remote UE. + +### 7.7.2 Pre-configured Measurement Gap procedures + +Figure 7.7.2-1 shows the procedure for the successful pre-configuration and activation of measurement gap. + +![Sequence diagram for Figure 7.7.2-1: Pre-configured measurement gap configuration and activation procedure. The diagram shows interactions between UE, gNB, and LMF. 0. TRP INFORMATION EXCHANGE (gNB to LMF). 1. NRPPa MEASUREMENT PRECONFIGURATION REQUIRED (LMF to gNB). 2. RRC Reconfiguration message (Pre-configured measurement gap configurations) (gNB to UE). 3. RRC Reconfiguration complete message (UE to gNB). 4. NRPPa MEASUREMENT PRECONFIGURATION CONFIRM (gNB to LMF). 5a. UL MAC CE Positioning Measurement Gap Activation/Deactivation Request (UE to gNB). 5b. NRPPa MEASUREMENT ACTIVATION (LMF to gNB). 6. DL MAC CE Positioning Measurement Gap Activation/Deactivation Command (gNB to UE).](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LMF + Note right of gNB: 0. TRP INFORMATION EXCHANGE + LMF->>gNB: 1. NRPPa MEASUREMENT PRECONFIGURATION REQUIRED + gNB->>UE: 2. RRC Reconfiguration message (Pre-configured measurement gap configurations) + UE->>gNB: 3. RRC Reconfiguration complete message + gNB->>LMF: 4. NRPPa MEASUREMENT PRECONFIGURATION CONFIRM + Note left of gNB: 5a. UL MAC CE Positioning Measurement Gap Activation/Deactivation Request + LMF-->>gNB: 5b. NRPPa MEASUREMENT ACTIVATION + gNB->>UE: 6. DL MAC CE Positioning Measurement Gap Activation/Deactivation Command + +``` + +Sequence diagram for Figure 7.7.2-1: Pre-configured measurement gap configuration and activation procedure. The diagram shows interactions between UE, gNB, and LMF. 0. TRP INFORMATION EXCHANGE (gNB to LMF). 1. NRPPa MEASUREMENT PRECONFIGURATION REQUIRED (LMF to gNB). 2. RRC Reconfiguration message (Pre-configured measurement gap configurations) (gNB to UE). 3. RRC Reconfiguration complete message (UE to gNB). 4. NRPPa MEASUREMENT PRECONFIGURATION CONFIRM (gNB to LMF). 5a. UL MAC CE Positioning Measurement Gap Activation/Deactivation Request (UE to gNB). 5b. NRPPa MEASUREMENT ACTIVATION (LMF to gNB). 6. DL MAC CE Positioning Measurement Gap Activation/Deactivation Command (gNB to UE). + +**Figure 7.7.2-1: Pre-configured measurement gap configuration and activation procedure** + +0. LMF obtains the TRP information required for positioning services from the gNBs. +1. The LMF provides the PRS information of the neighbour TRPs to the serving gNB and requests the serving gNB to configure the UE with measurement pre-configurations via NRPPa MEASUREMENT PRECONFIGURATION REQUIRED message. +2. Based on the assistance information from the LMF and the UE capability, the serving gNB decides to pre-configure the UE with measurement gap and provides pre-configured measurement gap configuration(s) with associated ID(s) to the UE by sending RRC Reconfiguration message specified in TS 38.331 [14]. +3. The UE sends RRC Reconfiguration complete message to the serving gNB to confirm the reception of pre-configured measurement gap configuration(s). +4. The serving gNB sends the confirmation message to the LMF to indicate the success of the pre-configuration via NRPPa MEASUREMENT PRECONFIGURATION CONFIRM message. +- 5a. If the UE requires measurement gaps for performing the requested location measurements, and the triggering condition for UL MAC CE as specified in TS 38.331 [14] is met, the UE sends UL MAC CE Positioning Measurement Gap Activation/Deactivation Request to the serving gNB and indicates the requested measurement gap configuration based on the ID configured in step 2. +- 5b. LMF may send the NRPPa MEASUREMENT ACTIVATION message to request the serving gNB to activate pre-configured measurement gap. +6. Based on the request from the UE in step 5a or the request from the LMF in step 5b, the serving gNB may send DL MAC CE Positioning Measurement Gap Activation/Deactivation Command containing an ID to activate the associated measurement gap. + +Figure 7.7.2-2 shows the procedure for the successful deactivation of measurement gap. + +![Sequence diagram for Figure 7.7.2-2: Pre-configured measurement gap deactivation procedure. The diagram shows interactions between UE, gNB, and LMF. 0. Measurement gap has been activated (gNB to UE). 1a. UL MAC CE Positioning Measurement Gap Activation/Deactivation Request (UE to gNB). 1b. NRPPa MEASUREMENT ACTIVATION (LMF to gNB). 2. DL MAC CE Positioning Measurement Gap Activation/Deactivation Command (gNB to UE).](6d2057d7e401741861ca63545a5d7d3b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LMF + Note right of gNB: 0. Measurement gap has been activated + Note left of gNB: 1a. UL MAC CE Positioning Measurement Gap Activation/Deactivation Request + LMF-->>gNB: 1b. NRPPa MEASUREMENT ACTIVATION + gNB->>UE: 2. DL MAC CE Positioning Measurement Gap Activation/Deactivation Command + +``` + +Sequence diagram for Figure 7.7.2-2: Pre-configured measurement gap deactivation procedure. The diagram shows interactions between UE, gNB, and LMF. 0. Measurement gap has been activated (gNB to UE). 1a. UL MAC CE Positioning Measurement Gap Activation/Deactivation Request (UE to gNB). 1b. NRPPa MEASUREMENT ACTIVATION (LMF to gNB). 2. DL MAC CE Positioning Measurement Gap Activation/Deactivation Command (gNB to UE). + +**Figure 7.7.2-2: Pre-configured measurement gap deactivation procedure** + +0. A measurement gap has been activated as shown in Figure 7.7.2-1. +- 1a. If the UE requires to stop performing the requested location measurements, and the triggering condition for UL MAC CE as specified in TS 38.331 [14] is met, the UE sends UL MAC CE Positioning Measurement Gap Activation/Deactivation Request to the serving gNB to deactivate the activated measurement gap containing the ID associated with the measurement gap for positioning. +- 1b. LMF may send the NRPPa MEASUREMENT ACTIVATION message to request the serving gNB to deactivate pre-configured measurement gap. +2. Based on the request from the UE in step 1a or the request from the LMF in step 1b, the serving gNB may send DL MAC CE Positioning Measurement Gap Activation/Deactivation Command containing an ID to deactivate the associated measurement gap. + +## 7.8 Procedures for Pre-configured PRS processing window + +### 7.8.1 General + +The pre-configured PRS processing window procedure is used by the network to provide PRS processing window for NR DL-PRS measurements to the UE without measurement gap. The serving gNB may activate/deactivate the pre-configured PRS processing window upon receiving the request from LMF. + +NOTE: The pre-configured PRS processing window procedure is not supported for a U2N Remote UE. + +### 7.8.2 Pre-configured PRS processing window procedures + +Figure 7.8.2-1 shows the procedure for the successful pre-configuration and activation of PRS processing window. + +![Sequence diagram illustrating the Pre-configured PRS processing window configuration and activation procedure between UE, gNB, and LMF.](a97f7c055c1fd8d79037d02b3fc38496_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LMF + Note right of LMF: 0. TRP INFORMATION EXCHANGE + LMF->>gNB: 1. NRPPa MEASUREMENT PRECONFIGURATION REQUIRED + gNB->>UE: 2. RRC Reconfiguration message (Pre-configured PRS Processing window configurations) + UE->>gNB: 3. RRC Reconfiguration complete message + gNB->>LMF: 4. NRPPa MEASUREMENT PRECONFIGURATION CONFIRM + LMF->>gNB: 5. NRPPa MEASUREMENT ACTIVATION + gNB->>UE: 6. DL MAC CE PPW Activation/Deactivation Command + +``` + +Sequence diagram illustrating the Pre-configured PRS processing window configuration and activation procedure between UE, gNB, and LMF. + +**Figure 7.8.2-1: Pre-configured PRS processing window configuration and activation procedure** + +0. LMF obtains the TRP information required for positioning services from the gNBs. +1. The LMF provides the PRS information of the neighbour TRPs to the serving gNB and requests the serving gNB to configure the UE with measurement pre-configurations via NRPPa MEASUREMENT PRECONFIGURATION REQUIRED message. +2. Based on the assistance information from the LMF and the UE capability, the serving gNB decides to pre-configure the UE with PRS processing window and provides pre-configured PRS processing window configuration(s) with associated ID(s) to the UE by sending RRC Reconfiguration message specified in TS 38.331 [14]. +3. The UE sends RRC Reconfiguration complete message to the serving gNB to confirm the reception of pre-configured PRS processing window configuration(s). +4. The serving gNB sends the confirmation message to the LMF to indicate the success of the pre-configuration via NRPPa MEASUREMENT PRECONFIGURATION CONFIRM message. + +5. The LMF sends the NRPPa MEASUREMENT ACTIVATION message to request the serving gNB to activate the pre-configured PRS processing window. +6. Based on the request from the LMF in step 5, the serving gNB sends DL MAC CE PPW Activation/Deactivation Command containing ID(s) to activate the associated PRS processing window configuration(s). + +Figure 7.8.2-2 shows the procedure for the successful deactivation of PRS processing window. + +![Sequence diagram illustrating the pre-configured PRS processing window deactivation procedure. The diagram shows three entities: UE, gNB, and LMF. The sequence starts with a message '0. PPW has been activated' from gNB to UE. Then, the LMF sends '1. NRPPa MEASUREMENT ACTIVATION' to the gNB. Finally, the gNB sends '2. DL MAC CE PPW Activation/Deactivation Command' to the UE.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LMF + Note over UE, gNB: 0. PPW has been activated + LMF->>gNB: 1. NRPPa MEASUREMENT ACTIVATION + gNB->>UE: 2. DL MAC CE PPW Activation/Deactivation Command + +``` + +Sequence diagram illustrating the pre-configured PRS processing window deactivation procedure. The diagram shows three entities: UE, gNB, and LMF. The sequence starts with a message '0. PPW has been activated' from gNB to UE. Then, the LMF sends '1. NRPPa MEASUREMENT ACTIVATION' to the gNB. Finally, the gNB sends '2. DL MAC CE PPW Activation/Deactivation Command' to the UE. + +**Figure 7.8.2-2: Pre-configured PRS processing window deactivation procedure** + +0. The PRS processing window has been activated as shown in Figure 7.8.2-1. +1. The LMF sends the NRPPa MEASUREMENT ACTIVATION message to request the serving gNB to deactivate the pre-configured PRS processing window. +2. Based on the request from the LMF in step 1, the serving gNB sends DL MAC CE PPW Activation/Deactivation Command containing ID(s) to deactivate the associated PRS processing window configuration(s). + +## 7.9 Positioning in RRC\_INACTIVE state + +Positioning may be performed when a UE is in RRC\_INACTIVE state. Any uplink LCS or LPP message can be transported in RRC\_INACTIVE state. If the UE initiated data transmission using UL SDT, the network can send DL LCS, LPP, RRC Release message (e.g. to configure SRS for UL positioning, if it is supported) and SP Positioning SRS Activation/Deactivation MAC CE to the UE without the need of state transition. + +Periodic and Semi-persistent UL-SRS transmission for positioning can be supported in RRC\_INACTIVE. The UL-SRS for positioning configuration in RRC\_INACTIVE state may be associated with an SRS Validity Area. The SRS Validity Area contains a list of cells in which the SRS for positioning configuration in RRC\_INACTIVE state is valid. When configured with an SRS configuration for positioning along with SRS Validity Area, if the UE reselects to another cell within the SRS Validity Area during SRS transmission, the UE continues the SRS transmission, subject to validation for SRS transmission as specified in TS 38.321 [39] and TS 38.331 [14]. When the UE reselects out of the SRS for positioning Validity Area during SRS transmission, the UE may send an "RRC Resume Request" message to the network for SRS configuration request. + +NOTE: Aperiodic UL-SRS transmission for positioning is not supported in RRC\_INACTIVE. + +The SRS for positioning configuration in RRC\_INACTIVE state may be pre-configured in the target device. The target device may send an "RRC Resume Request" message to the network when a configured periodic or triggered location event has been detected to request activation of the pre-configured SRS for positioning. For preconfigured multiple SRS configurations, the UE is configured with only one SRS for positioning configuration for each validity area. + +## 7.10 Positioning in RRC\_IDLE state + +Positioning measurements may be performed when a UE is in RRC\_IDLE state and reported when in RRC\_CONNECTED state (see also clause 6.4.2). + +A UE may utilize the positioning assistance data received via broadcast (see clause 7.5) or the positioning assistance data received while in RRC\_CONNECTED state when performing positioning measurements in RRC\_IDLE state. + +## 7.11 General SLPP procedures for UE Positioning and Ranging + +### 7.11.1 SLPP procedures + +Positioning and Ranging procedures using NR sidelink are modelled as transactions of the SLPP protocol using the procedures defined in this specification. A procedure consists of a single operation of one of the following types: + +- Exchange of positioning capabilities; +- Transfer of assistance data; +- Transfer of location information (positioning measurements, ranging measurements, and/or position estimate); +- Error handling; +- Abort. + +Parallel transactions are permitted (i.e. a new SLPP transaction may be initiated, while another one is outstanding). + +### 7.11.2 SLPP positioning and ranging procedures + +#### 7.11.2.1 SLPP capability transfer + +Capabilities in an SLPP context refer to the ability to support different position methods defined for SLPP (e.g., SL-RTT, SL-TDOA, etc.), different aspects of a particular position method (e.g. different types of measurements or assistance data) and common features not specific to only one position method. + +The exchange of capabilities between different endpoints may be initiated by a request or sent as "unsolicited" information. If a request is used, an endpoint A sends an SLPP Request Capabilities message to an endpoint B with a request for capability information. The endpoint B sends an SLPP Provide Capabilities message. + +![Sequence diagram of SLPP Capability Transfer Procedure between Endpoint A and Endpoint B.](a82bc78bff7fbefef1c0fb744365f957_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Capabilities + Endpoint A->>Endpoint B: 1. SLPP Request Capabilities + Note left of Endpoint B: 2. SLPP Provide Capabilities + Endpoint B->>Endpoint A: 2. SLPP Provide Capabilities +``` + +The diagram illustrates the SLPP Capability Transfer Procedure between two endpoints, Endpoint A and Endpoint B. It is a sequence diagram with two vertical lifelines. The first message, labeled '1. SLPP Request Capabilities', is sent from Endpoint A to Endpoint B. The second message, labeled '2. SLPP Provide Capabilities', is sent from Endpoint B back to Endpoint A. + +Sequence diagram of SLPP Capability Transfer Procedure between Endpoint A and Endpoint B. + +**Figure 7.11.2.1-1: SLPP Capability Transfer Procedure** + +1. Endpoint A may send a request for the SLPP related capabilities to endpoint B. +2. Endpoint B transfers its SLPP-related capabilities to endpoint A. The capabilities may refer to particular position methods or may be common to multiple position methods. + +The SLPP Capability Indication procedure is used for unsolicited capability transfer. + +![Sequence diagram showing SLPP Capability Indication Procedure between Endpoint A and Endpoint B.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +A sequence diagram illustrating the SLPP Capability Indication Procedure. It features two lifelines, 'Endpoint A' on the left and 'Endpoint B' on the right. A solid horizontal arrow points from Endpoint A to Endpoint B, labeled '1. SLPP Provide Capabilities'. + +Sequence diagram showing SLPP Capability Indication Procedure between Endpoint A and Endpoint B. + +Figure 7.11.2.1-2: SLPP Capability Indication Procedure + +### 7.11.2.2 SLPP assistance data transfer + +Assistance data may comprise SL-PRS information (e.g., SL-PRS Sequence ID) or position calculation information (e.g., SL Anchor UE location information) and may be transferred either by request or unsolicited. If a request is used, an endpoint A sends an SLPP Request Assistance Data message to an endpoint B and may indicate the assistance data needed. The endpoint B then responds with an SLPP Provide Assistance Data message. + +![Sequence diagram showing SLPP Assistance Data Transfer procedure between Endpoint A and Endpoint B.](83c2ebae8819e9cdca7eb157a13ee26a_img.jpg) + +A sequence diagram illustrating the SLPP Assistance Data Transfer procedure. It features two lifelines, 'Endpoint A' on the left and 'Endpoint B' on the right. The interaction consists of three steps: 1. A solid horizontal arrow points from Endpoint A to Endpoint B, labeled '1. SLPP Request Assistance Data'. 2. A solid horizontal arrow points from Endpoint B back to Endpoint A, labeled '2. SLPP Provide Assistance Data'. 3. A dashed horizontal arrow points from Endpoint B back to Endpoint A, also labeled '2. SLPP Provide Assistance Data'. + +Sequence diagram showing SLPP Assistance Data Transfer procedure between Endpoint A and Endpoint B. + +Figure 7.11.2.2-1: SLPP Assistance Data Transfer procedure + +- 1. Endpoint A may send a request to endpoint B for assistance data and may indicate the particular assistance data needed. +- 2. Endpoint B transfers assistance data to endpoint A. The transferred assistance data should match any assistance data requested in step 1. +- 3. Optionally, endpoint B may transfer additional assistance data to endpoint A in one or more additional SLPP messages. + +SLPP Assistance Data Delivery procedure is used for unsolicited assistance data transfer. + +![Sequence diagram showing SLPP Assistance Data Delivery procedure between Endpoint A and Endpoint B.](d78e519e9186d30807342196675fd440_img.jpg) + +A sequence diagram illustrating the SLPP Assistance Data Delivery procedure. It features two lifelines, 'Endpoint A' on the left and 'Endpoint B' on the right. The interaction consists of two steps: 1. A solid horizontal arrow points from Endpoint A to Endpoint B, labeled '1. SLPP Provide Assistance Data'. 2. A dashed horizontal arrow points from Endpoint A to Endpoint B, also labeled '2. SLPP Provide Assistance Data'. + +Sequence diagram showing SLPP Assistance Data Delivery procedure between Endpoint A and Endpoint B. + +Figure 7.11.2.2-2: SLPP Assistance Data Delivery procedure + +### 7.11.2.3 SLPP location information transfer + +The term "location information" applies both to an actual position estimate and to values used in computing position (e.g., SL-PRS measurements). It can be delivered either in response to a request or unsolicited. + +![Sequence diagram for SLPP Location Information Transfer procedure](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Location Information + Endpoint A->>Endpoint B: 1. SLPP Request Location Information + Note right of Endpoint B: 2. SLPP Provide Location Information + Endpoint B->>Endpoint A: 2. SLPP Provide Location Information + Note right of Endpoint B: 3. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 3. SLPP Provide Location Information +``` + +The diagram illustrates the SLPP Location Information Transfer procedure between Endpoint A and Endpoint B. It consists of three steps: 1. Endpoint A sends a request for location information to Endpoint B. 2. Endpoint B responds with location information. 3. Endpoint B may optionally send additional location information to Endpoint A via a dashed arrow. + +Sequence diagram for SLPP Location Information Transfer procedure + +**Figure 7.11.2.3-1: SLPP Location Information Transfer procedure** + +1. Endpoint A may send a request for location information to endpoint B and may indicate the type of location information needed and associated QoS. +2. In response to step 1, the endpoint B transfers location information to endpoint A. The location information transferred should match the location information requested in step 1. +3. Optionally (e.g., if requested in step 1), endpoint B in step 2 may transfer additional location information to endpoint A in one or more additional SLPP messages. + +SLPP Location Information Delivery procedure is used for unsolicited location information transfer. + +![Sequence diagram for SLPP Location Information Delivery procedure](0ea87c5f55e5857d0969bc5ca36dccba_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Provide Location Information + Endpoint A->>Endpoint B: 1. SLPP Provide Location Information +``` + +The diagram illustrates the SLPP Location Information Delivery procedure between Endpoint A and Endpoint B. It consists of a single step: 1. Endpoint A sends location information to Endpoint B. + +Sequence diagram for SLPP Location Information Delivery procedure + +**Figure 7.11.2.3-2: SLPP Location Information Delivery procedure** + +### 7.11.2.4 Error handling + +The procedure is used to notify the sending endpoint by the receiving endpoint that the receiving SLPP message is erroneous or unexpected. + +![Sequence diagram for SLPP Error handling between Endpoint A and Endpoint B.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Message + Endpoint A->>Endpoint B: 1. SLPP Message + Note right of Endpoint B: 2. SLPP Error + Endpoint B->>Endpoint A: 2. SLPP Error +``` + +The diagram illustrates the interaction for SLPP error handling. It features two lifelines, 'Endpoint A' and 'Endpoint B'. A horizontal arrow labeled '1. SLPP Message' points from Endpoint A to Endpoint B. A return arrow labeled '2. SLPP Error' points from Endpoint B back to Endpoint A. + +Sequence diagram for SLPP Error handling between Endpoint A and Endpoint B. + +**Figure 7.11.2.4-1: SLPP Error handling** + +1. Endpoint A sends a SLPP message to the other endpoint B. +2. If the endpoint B detects that the receiving SLPP message is erroneous or unexpected, endpoint B transfers error indication information to the other endpoint A. + +### 7.11.2.5 Abort + +The procedure is used to notify the other endpoint by one endpoint to abort an ongoing SLPP procedure between the two endpoints. + +![Sequence diagram for SLPP Abort procedure.](10bf8762a8e8d9385609cc6fb11061fe_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. Ongoing SLPP Procedure + Note right of Endpoint B: 1. Ongoing SLPP Procedure + Note right of Endpoint B: 2. SLPP Abort + Endpoint B->>Endpoint A: 2. SLPP Abort +``` + +The diagram illustrates the SLPP Abort procedure. Two lifelines, 'Endpoint A' and 'Endpoint B', are shown. A horizontal bar labeled '1. Ongoing SLPP Procedure' spans across both lifelines, indicating an active session. From Endpoint B, a horizontal arrow labeled '2. SLPP Abort' points to Endpoint A, signaling the termination of the procedure. + +Sequence diagram for SLPP Abort procedure. + +**Figure 7.11.2.5-1: SLPP Abort** + +1. A SLPP procedure is ongoing between the endpoints. +2. If endpoint B determines that the procedure must be aborted, endpoint B sends an SLPP Abort message to the other endpoint A carrying the transaction ID for the procedure. + +### 7.11.2.6 Sequence of Procedures + +SLPP procedures are not required to occur in any fixed order, in order to provide greater flexibility in positioning. Despite the flexibility allowed by SLPP, it is expected that procedures will normally occur in the following order: + +1. Capability Transfer; +2. Assistance Data Transfer; +3. Location Information Transfer (measurements and/or location estimate). + +## 7.12 General UE-only sidelink positioning and ranging procedure + +Figure 7.12-1 shows the sequence of operation for sidelink positioning and ranging in the UE only mode of operation as further defined in TS 23.586 [46]. + +![Sequence diagram of the general UE-only sidelink positioning and ranging procedure. Lifelines: UEn, ..., UE2, UE1, and SL Server UE. The sequence starts with a Ranging/SL Positioning Service Request from UE1. It proceeds through UE Discovery, SLPP Capability Transfer, SL Server UE Discovery & Selection, SL Positioning/Ranging Service Request, SLPP Capability Transfer, Supplementary RSPP Capability Transfer, SLPP Provide Assistance Data, Supplementary RSPP Assistance Data Transfer, SLPP Assistance Data Transfer, SLPP Request Location Information, Supplementary RSPP Location Information Transfer, SLPP Location Information Transfer, SLPP Provide Location Information, Supplementary RSPP Location Information Transfer, Determine Ranging/SL Positioning Results, SL Positioning/Ranging Service Response, and finally a Ranging/SL Positioning Service Response.](76d19e4271bf243b20d55a98efd51483_img.jpg) + +``` + +sequenceDiagram + participant UEn + participant ... + participant UE2 + participant UE1 + participant SL Server UE + + Note right of UE1: 1. Ranging/SL Positioning Service Request + Note over UEn, UE2: 2. UE Discovery + Note over UEn, UE2: 3. SLPP Capability Transfer + Note over UEn, UE2: 4. SL Server UE Discovery&Selection + Note right of UE1: 5. SL Positioning/Ranging Service Request + Note over UE1, SL Server UE: 6. SLPP Capability Transfer + Note over UE1, SL Server UE: 7. Supplementary RSPP Capability Transfer + Note right of SL Server UE: 8. SLPP Provide Assistance Data + Note over UE1, SL Server UE: 9. Supplementary RSPP Assistance Data Transfer + Note over UEn, UE2: 10. SLPP Assistance Data Transfer + Note right of UE1: 11. SLPP Request Location Information + Note over UE1, SL Server UE: 12. Supplementary RSPP Location Information Transfer + Note over UEn, UE2: 13. SLPP Location Information Transfer + Note right of UE1: 14. SLPP Provide Location Information + Note over UE1, SL Server UE: 15. Supplementary RSPP Location Information Transfer + Note right of SL Server UE: 16. Determine Ranging/SL Positioning Results + Note right of SL Server UE: 17. SL Positioning/Ranging Service Response + Note right of UE1: 18. Ranging/SL Positioning Service Response + +``` + +Sequence diagram of the general UE-only sidelink positioning and ranging procedure. Lifelines: UEn, ..., UE2, UE1, and SL Server UE. The sequence starts with a Ranging/SL Positioning Service Request from UE1. It proceeds through UE Discovery, SLPP Capability Transfer, SL Server UE Discovery & Selection, SL Positioning/Ranging Service Request, SLPP Capability Transfer, Supplementary RSPP Capability Transfer, SLPP Provide Assistance Data, Supplementary RSPP Assistance Data Transfer, SLPP Assistance Data Transfer, SLPP Request Location Information, Supplementary RSPP Location Information Transfer, SLPP Location Information Transfer, SLPP Provide Location Information, Supplementary RSPP Location Information Transfer, Determine Ranging/SL Positioning Results, SL Positioning/Ranging Service Response, and finally a Ranging/SL Positioning Service Response. + +**Figure 7.12-1: Procedure for sidelink positioning and ranging (UE-only operation)** + +1. UE1 (e.g., target UE) may receive a Ranging/SL Positioning Service Request from a client UE or from its own application layer as defined in TS 23.586 [46]. +2. UE1 discovers UEs 2 to n, as described in TS 23.586 [46], if not already discovered. +3. UE1 may obtain the sidelink positioning capabilities from UEs 2 to n using the SLPP Capability Transfer procedure described in clause 7.11.2.1. +4. If UE1 does not support SL Server UE functionality or decides to select a different SL Server UE, a SL Server UE may be discovered (if not already discovered at step 2) and selected as described in TS 23.586 [46]. +5. If step 4 was performed, UE1 may send a Supplementary RSPP SL Positioning/Ranging Service Request message to the SL Server UE including the Application layer IDs of UEs 1 to n together with an indication of location results requested (e.g., absolute location, relative location or distances and directions) and desired QoS. +6. If step 4 was performed, the SL Server UE may request the SL positioning and ranging capabilities of UE1 using the SLPP Capability Transfer procedure described in clause 7.11.2.1. + +7. If step 4 was performed, the SL Server UE may request the SL positioning and ranging capabilities of UEs 2 to n using the Supplementary RSPP Capability Transfer Procedure. The Supplementary RSPP Capability Transfer messages may include embedded SLPP Capability Transfer messages for UEs 2 to n together with their Application Layer IDs. If step 3 did not occur, UE1 obtains the sidelink positioning capabilities from UEs 2 to n using the SLPP Capability Transfer procedure described in clause 7.11.2.1 at this step. +8. If step 4 was performed, the SL Server UE may provide assistance data for UE1 using the SLPP Assistance Data Transfer procedure described in clause 7.11.2.2. +9. If step 4 was performed, the SL Server UE may provide assistance data for UEs 2 to n using the Supplementary RSPP Assistance Data Transfer Procedure. The Supplementary RSPP Assistance Data Transfer messages may include embedded SLPP Assistance Data Transfer messages for UEs 2 to n together with their Application Layer IDs. +10. UE1 may provide assistance data to UEs 2 to n using the SLPP Assistance Data Transfer procedure described in clause 7.11.2.2. If step 9 was performed, the SLPP Provide Assistance Data message includes the assistance data received from the SL Server UE at step 9. +11. If step 4 was performed, the SL Server UE may send a SLPP Request Location Information message to UE1 as described in clause 7.11.2.3 if the ranging/positioning result determination is performed by the SL Server UE. +12. If step 4 was performed, the SL Server UE may request location information for UEs 2 to n using the Supplementary RSPP Location Information Transfer Procedure if the ranging/positioning result determination is performed by the SL Server UE. The Supplementary RSPP Location Information Transfer messages may include embedded SLPP Request Location Information messages for UEs 2 to n together with their Application Layer IDs. +13. UE1 may send a request for sidelink location information to UEs 2 to n using the SLPP Location Information Transfer procedure described in clause 7.11.2.3. If step 12 was performed, the SLPP Location Information Request message includes the information received from the SL Server UE at step 12. +14. If step 11 was performed, UE1 sends a SLPP Provide Location Information message containing the sidelink location information obtained by UE1 to the SL Server UE as described in clause 7.11.2.3. +15. If step 12 was performed, UE1 provides the sidelink location information from UEs 2 to n to the SL Server UE using the Supplementary RSPP Location Information Transfer procedure. The Supplementary RSPP Location Information Transfer messages may include embedded SLPP Provide Location Information messages for UEs 2 to n together with their Application Layer IDs. +16. If steps 11 or 12 (and 14 or 15) were performed, the SL Server UE performs the ranging/SL positioning results calculation. +17. If step 5 was performed, the SL Server UE sends a SL Positioning/Ranging Service Response to UE1 including the results requested in step 5. +18. The ranging/positioning result is delivered to the requestor from step 1. + +## 7.13 Positioning Integrity + +### 7.13.1 General + +Positioning Integrity is supported for the following positioning methods: + +- GNSS positioning methods as specified in clause 8.1; +- Multi-RTT positioning as specified in clause 8.10; +- DL-AoD positioning as specified in clause 8.11; +- DL-TDOA positioning as specified in clause 8.12; +- UL-TDOA positioning as specified in clause 8.13; + +- UL-AoA positioning as specified in clause 8.14. + +NOTE: The local errors/threats associated with the UE and TRP measurements are implementation dependent. For UE-based mode, local UE errors/threats may be addressed by the UE when determining protection levels. For UE-assisted mode and network-based positioning, an LMF may address the UE and TRP local errors from UE and/or TRP measurement results. A specific method for determining local UE and TRP errors/threats is not specified as this is implementation defined. + +## 7.13.2 Integrity Principle of Operation + +For integrity operation, the network will ensure that: + +$$P(\text{Error} > \text{Bound for longer than TTA} \mid \text{NOT DNU}) \leq \text{Residual Risk} + \text{IRallocation} \quad (\text{Equation 7.13.2-1})$$ + +for all values of $\text{IRallocation}$ in the range $\text{irMinimum} \leq \text{IRallocation} \leq \text{irMaximum}$ + +for all the errors in Table 8.1.2.1b-1, Table 8.11.2.1.1-1, and Table 8.12.2.1.1-1 which have corresponding integrity assistance data available and where the corresponding DNU flag(s) are set to false. + +The integrity risk probability is decomposed into a constant Residual Risk component provided in the assistance data as well as a variable $\text{IRallocation}$ component that corresponds to the contribution from the Bound according to the Bound formula in Equation 7.13.2-2. $\text{IRallocation}$ may be chosen freely by the client based on the desired Bound, therefore the network should ensure that Equation 7.13.2-1 holds for all possible choices of $\text{IRallocation}$ . The Residual Risk and $\text{IRallocation}$ components may be mapped to fault and fault-free cases respectively, but the implementation is free to choose any other decomposition of the integrity risk probability into these two components. + +For GNSS Integrity in SSR, the validity time of the integrity bounds is set as equal to twice the SSR Update Interval for the given SSR Assistance Data message, i.e. the time period between the SSR Epoch Time and the SSR Epoch Time plus twice the SSR Update Interval in the GPS time scale. + +Equation 7.13.2-1 holds for all assistance data that has been issued that is still within its validity period. If this condition cannot be met then the corresponding DNU flag must be set. + +Equation 7.13.2-1 holds at any epochs for which Assistance Data is provided. Providing Assistance Data without the Integrity Service Alert IE or GNSS Real Time Integrity IEs (in the case of GNSS) is interpreted as a DNU=FALSE condition. For any bound that is still valid (within its validity time), the network ensures that the Integrity Service Alert and/or GNSS Real Time Integrity IEs (in the case of GNSS) are also included in the provided Assistance Data if needed to satisfy the condition in Equation 7.13.2-1. It is up to the implementation how to handle epochs for which integrity results are desired but there are no DNU flag(s) available, e.g. the Time To Alert (TTA) may be set such that there is a "grace period" to receive the next set of DNU flags. + +Only those satellites and TRPs for which the integrity assistance data are provided are monitored by the network and can be used for integrity related applications. + +Where: + +**Error:** Error is the difference between the true value of a parameter (e.g. ionosphere, troposphere etc. in the case of GNSS, or ARP location, RTD, etc. in the case of NR positioning), and its value as estimated and provided in the corresponding assistance data as per Table 8.1.2.1b-1, Table 8.11.2.1.1-1, and Table 8.12.2.1.1-1. + +**Bound:** In the case of GNSS, Integrity Bounds provide the statistical distribution of the residual errors associated with the GNSS positioning corrections (e.g. RTK, SSR etc). In the case of GNSS, integrity bounds are used to statistically bound the residual errors after the positioning corrections have been applied. + +In the case of NR positioning, Integrity Bounds provide the statistical distribution of the errors. + +The bound is computed according to the Bound formula defined in Equation 7.13.2-2. The bound formula describes a bounding model including a mean and standard deviation (e.g. paired over-bounding Gaussian). The bound may be scaled by multiplying the standard deviation by a $K$ factor corresponding to an $\text{IRallocation}$ , for any desired $\text{IRallocation}$ within the permitted range. + +The bound for a particular error is computed according to the following formula: + +$$\text{Bound} = \text{mean} + K * \text{stdDev} \quad (\text{Equation 7.13.2-2})$$ + +$$K = \text{normInv}(IR_{\text{allocation}} / 2)$$ + +$$ir\text{Minimum} \leq IR_{\text{allocation}} \leq ir\text{Maximum}$$ + +where: *mean*: mean value for this specific error, as per Table 8.1.2.1b-1, Table 8.11.2.1.1-1, and Table 8.12.2.1.1-1. + +*stdDev*: standard deviation for this specific error, as per Table 8.1.2.1b-1, Table 8.11.2.1.1-1, and Table 8.12.2.1.1-1. + +**Time-to-Alert (TTA)**: The maximum allowable elapsed time from when the Error exceeds the Bound until a DNU flag must be issued. + +**Target Integrity Risk (TIR)**: The probability per unit of time that the Error exceeds the Bound without issuing a DNU flag within the TTA. + +**DNU**: The DNU flag(s) corresponding to a particular error as per Table 8.1.2.1b-1, Table 8.11.2.1.1-1, and Table 8.12.2.1.1-1. Where multiple DNU flags are specified, the DNU condition in Equation 7.13.2-1 is present when any of the flags are true (logical OR of the flags). + +**Residual Risk**: The residual risk is the component of the integrity risk provided in the assistance data as per Table 8.1.2.1b-1, Table 8.11.2.1.1-1, and Table 8.12.2.1.1-1. This may correspond to the fault case risk but the implementation is permitted to allocate this component in any way that satisfies Equation 7.13.2-1. + +The Residual Risk is the Probability of Onset which is defined per unit of time and represents the probability that the feared event begins. Each Residual Risk is accompanied by a Mean Duration which represents the expected mean duration of the corresponding feared event and is used to convert the Probability of Onset to a probability that the feared event is present at any given time, i.e. + +$$P(\text{Feared Event is Present}) = \text{Mean Duration} * \text{Probability of Onset of Feared Event} \quad (\text{Equation 7.13.2-3})$$ + +**irMinimum, irMaximum**: Minimum and maximum allowable values of *IRallocation* that may be chosen by the client. Provided as service parameters from the Network according to Integrity Service Parameters. + +**Correlation Times**: The minimum time interval beyond which two sets of assistance data parameters for a given error can be considered to be independent from one another. + +## 8 Positioning methods and Supporting Procedures + +### 8.1 GNSS positioning methods + +#### 8.1.1 General + +A navigation satellite system provides autonomous geo-spatial positioning with either global or regional coverage. Augmentation systems, such as SBAS, are navigation satellite systems that provide regional coverage to augment the navigation systems with global coverage. + +By definition, GNSS refers to satellite constellations that achieve global coverage, however, in 3GPP specifications the term GNSS is used to encompass global, regional, and augmentation satellite systems. The following GNSSs are supported in this version of the specification: + +- GPS and its modernization [5], [6], [7]; (global coverage) +- Galileo [8]; (global coverage) +- GLONASS [9]; (global coverage) +- Satellite Based Augmentation Systems (SBAS), including WAAS, EGNOS, MSAS, and GAGAN [11]; (regional coverage) +- Quasi-Zenith Satellite System (QZSS) [10]; (regional coverage) + +- BeiDou Navigation Satellite System (BDS) [20] [34] [44] [45]. (global coverage) +- NAVigation with Indian Constellation (NavIC) [43]. (regional coverage) + +Each global GNSS can be used individually or in combination with others, including regional navigation systems and augmentation systems. When used in combination, the effective number of navigation satellite signals would be increased: + +- extra satellites can improve availability (of satellites at a particular location) and results in an improved ability to work in areas where satellite signals can be obscured, such as in urban canyons; +- extra satellites and signals can improve reliability, i.e., with extra measurements the data redundancy is increased, which helps identify any measurement outlier problems; +- extra satellites and signals can improve accuracy due to improved measurement geometry and improved ranging signals from modernized satellites. + +When GNSS is designed to inter-work with the NG-RAN, the network assists the UE GNSS receiver to improve the performance in several respects. These performance improvements will: + +- reduce the UE GNSS start-up and acquisition times; the search window can be limited and the measurements speed up significantly; +- increase the UE GNSS sensitivity; positioning assistance messages are obtained via NG-RAN so the UE GNSS receiver can operate also in low SNR situations when it is unable to demodulate GNSS satellite signals; +- allow the UE to consume less handset power than with stand-alone GNSS; this is due to rapid start-up times as the GNSS receiver can be in idle mode when it is not needed; +- allow the UE to compute its position with a better accuracy; RTK corrections (for N-RTK) and GNSS physical models (for SSR/PPP) are obtained via NG-RAN so the UE can use these assistance data, together with its own measurements, i.e., code and carrier phase measurements, to enable computation of a position with a high accuracy; +- allow the UE to determine and report the integrity results of the calculated location; the UE can use the integrity requirements and assistance data obtained via NG-RAN, together with its own measurements, to determine the integrity results of the calculated location. + +The network-assisted GNSS methods rely on signalling between UE GNSS receivers (possibly with reduced complexity) and a continuously operating GNSS reference receiver network, which has clear sky visibility of the same GNSS constellation as the assisted UEs. Two assisted modes are supported: + +- *UE-Assisted*: The UE performs GNSS measurements (pseudo-ranges, pseudo Doppler, carrier phase ranges, etc.) and sends these measurements to the LMF where the position calculation takes place, possibly using additional measurements from other (non GNSS) sources; +- *UE-Based*: The UE performs GNSS measurements and calculates its own location, possibly using additional measurements from other (non GNSS) sources and assistance data from the LMF. + +The assistance data content may vary depending on whether the UE operates in UE-Assisted or UE-Based mode. + +The assistance data signalled to the UE can be broadly classified into: + +- *data assisting the measurements*: e.g. reference time, visible satellite list, satellite signal Doppler, code phase, Doppler and code phase search windows; +- *data providing means for position calculation*: e.g. reference time, reference position, satellite ephemeris, clock corrections, code and carrier phase measurements from a GNSS reference receiver or network of receivers; +- *data increasing the position accuracy*: e.g. satellite code biases, satellite orbit corrections, satellite clock corrections, atmospheric models, RTK residuals, gradients; +- *data facilitating the integrity results determination of the calculated location*. + +A UE with GNSS measurement capability may also operate in an autonomous (standalone) mode. In autonomous mode the UE determines its position based on signals received from GNSS without assistance from the network. + +### 8.1.1a Void + +## 8.1.2 Information to be transferred between NG-RAN/5GC Elements + +### 8.1.2.0 General + +This clause defines the information that may be transferred between LMF and UE. + +### 8.1.2.1 Information that may be transferred from the LMF to UE + +#### 8.1.2.1.0 General + +Table 8.1.2.1.0-1 lists assistance data for both UE-assisted and UE-based modes that may be sent from the LMF to the UE. + +NOTE: The provision of these assistance data elements and the usage of these elements by the UE depend on the NG-RAN/5GC and UE capabilities, respectively. + +**Table 8.1.2.1.0-1: Information that may be transferred from the LMF to UE** + +| Assistance Data | +|------------------------------------| +| Reference Time | +| Reference Location | +| Ionospheric Models | +| Earth Orientation Parameters | +| GNSS-GNSS Time Offsets | +| Differential GNSS Corrections | +| Ephemeris and Clock Models | +| Real-Time Integrity | +| Data Bit Assistance | +| Acquisition Assistance | +| Almanac | +| UTC Models | +| RTK Reference Station Information | +| RTK Auxiliary Station Data | +| RTK Observations | +| RTK Common Observation Information | +| GLONASS RTK Bias Information | +| RTK MAC Correction Differences | +| RTK Residuals | +| RTK FKP Gradients | +| SSR Orbit Corrections | +| SSR Clock Corrections | +| SSR Code Bias | +| SSR Phase Bias | +| SSR STEC Corrections | +| SSR Gridded Correction | +| SSR URA | +| SSR Correction Points | +| Integrity Service Parameters | +| Integrity Alerts | +| SSR IOD Update | +| SSR Satellite PCV Residuals | + +#### 8.1.2.1.1 Reference Time + +Reference Time assistance provides the GNSS receiver with coarse or fine GNSS time information. The specific GNSS system times (e.g., GPS, Galileo, GLONASS, BDS, NavIC system time) shall be indicated with a GNSS ID. + +In case of coarse time assistance only, the Reference Time provides an estimate of the current GNSS system time (where the specific GNSS is indicated by a GNSS ID). The LMF should achieve an accuracy of $\pm 3$ seconds for this time including allowing for the transmission delay between LMF and UE. + +In case of fine time assistance, the Reference Time provides the relation between GNSS system time (where the specific GNSS is indicated by a GNSS ID) and NG-RAN air-interface timing. + +#### 8.1.2.1.2 Reference Location + +Reference Location assistance provides the GNSS receiver with an a priori estimate of its location (e.g., obtained via Cell-ID, OTDOA positioning, etc.) together with its uncertainty. + +The geodetic reference frame shall be WGS-84, as specified in TS 23.032 [4]. + +#### 8.1.2.1.3 Ionospheric Models + +Ionospheric Model assistance provides the GNSS receiver with parameters to model the propagation delay of the GNSS signals through the ionosphere. Ionospheric Model parameters as specified by GPS [5], Galileo [8], QZSS [10], BDS [20] [34] [44] [45], and NavIC [43] may be provided. + +#### 8.1.2.1.4 Earth Orientation Parameters + +Earth Orientation Parameters (EOP) assistance provides the GNSS receiver with parameters needed to construct the ECEF-to-ECI coordinate transformation as specified by GPS [5]. + +#### 8.1.2.1.5 GNSS-GNSS Time Offsets + +GNSS-GNSS Time Offsets assistance provides the GNSS receiver with parameters to correlate GNSS time (where the specific GNSS is indicated by a GNSS-1 ID) of one GNSS with other GNSS time (where the specific GNSS is indicated by a GNSS-2 ID). GNSS-GNSS Time Offsets parameters as specified by GPS [5], Galileo [8], GLONASS [9], QZSS [10], BDS [20] [34] [44] [45], and NavIC [43] may be provided. + +#### 8.1.2.1.6 Differential GNSS Corrections + +Differential GNSS Corrections assistance provides the GNSS receiver with pseudo-range and pseudo-range-rate corrections to reduce biases in GNSS receiver measurements as specified in [12]. The specific GNSS for which the corrections are valid is indicated by a GNSS-ID. + +#### 8.1.2.1.7 Ephemeris and Clock Models + +Ephemeris and Clock Models assistance provides the GNSS receiver with parameters to calculate the GNSS satellite position and clock offsets. The various GNSSs use different model parameters and formats, and all parameter formats as defined by the individual GNSSs are supported by the signalling. + +#### 8.1.2.1.8 Real-Time Integrity + +Real-Time Integrity assistance provides the GNSS receiver with information about the health status of a GNSS constellation (where the specific GNSS is indicated by a GNSS ID). + +For integrity purposes (as per Clause 8.1.1a), a GNSS satellite and signal combination should be considered as being marked "Do Not Use" (DNU) if the satellite ID and signal are present in the list of unhealthy (bad) signals. + +NOTE: The absence of the Real Time Integrity assistance from any Provide Assistance Data message is interpreted as DNU=FALSE for all satellites and signals that are monitored for integrity. + +#### 8.1.2.1.9 Data Bit Assistance + +Data Bit Assistance provides the GNSS receiver with information about data bits or symbols transmitted by a GNSS satellite at a certain time (where the specific GNSS is indicated by a GNSS ID). This information may be used by the UE for sensitivity assistance (data wipe-off) and time recovery. + +#### 8.1.2.1.10 Acquisition Assistance + +Acquisition Assistance provides the GNSS receiver with information about visible satellites, reference time, expected code-phase, expected Doppler, search windows (i.e., code and Doppler uncertainty) and other information of the GNSS signals (where the specific GNSS is indicated by a GNSS ID) to enable a fast acquisition of the GNSS signals. + +#### 8.1.2.1.11 Almanac + +Almanac assistance provides the GNSS receiver with parameters to calculate the coarse (long-term) GNSS satellite position and clock offsets. The various GNSSs use different model parameters and formats, and all parameter formats as defined by the individual GNSSs are supported by the signalling. + +#### 8.1.2.1.12 UTC Models + +UTC Models assistance provides the GNSS receiver with parameters needed to relate GNSS system time (where the specific GNSS is indicated by a GNSS ID) to Universal Coordinated Time. The various GNSSs use different model parameters and formats, and all parameter formats as defined by the individual GNSSs are supported by the signalling. + +#### 8.1.2.1.13 RTK Reference Station Information + +RTK Reference Station Information provides the GNSS receiver with the Earth-Centered, Earth-Fixed (ECEF) coordinates of the Reference Station's installed antenna's ARP, and the height of the ARP above the survey monument. Additionally, this assistance data provides information about the antenna type installed at the reference site. + +NOTE: With the MAC N-RTK technique this assistance data is used to provide information regarding the Master Reference Station (see clause 8.1.2.1a). + +#### 8.1.2.1.14 RTK Auxiliary Station Data + +RTK Auxiliary Station Data provides the GNSS receiver with the location for all Auxiliary Reference Stations (see clause 8.1.2.1a) within the assistance data. These values are expressed as relative geodetic coordinates (latitude, longitude, and height) with respect to a Master Reference Station (see clause 8.1.2.1a) and based on the GRS80 ellipsoid. This type of assistance data is relevant only with the MAC N-RTK technique [31]. + +#### 8.1.2.1.15 RTK Observations + +RTK Observations provides the GNSS receiver with all primary observables (pseudo-range, phase-range, phase-range rate (Doppler), and carrier-to-noise ratio) generated at the Reference Station for each GNSS signal. The signal generation from the reference station is in compliance with [31]: as an example, the phase measurements of different signals in the same band must be phased aligned. More examples can be found in [31]. + +The pseudo-range is the distance between the satellite and GNSS receiver antennas, expressed in metres, equivalent to the difference of the time of reception (expressed in the time frame of the GNSS receiver) and the time of transmission (expressed in the time frame of the satellite) of a distinct satellite signal. + +The phase-range measurement is a measurement of the range between a satellite and receiver expressed in units of cycles of the carrier frequency. This measurement is more precise than the pseudo-range (of the order of millimetres), but it is ambiguous by an unknown integer number of wavelengths. + +The phase-range rate is the rate at which the phase-range between a satellite and a GNSS receiver changes over a particular period of time. + +The carrier-to-noise ratio is the ratio of the received modulated carrier signal power to the noise power after the GNSS receiver filters. + +NOTE: With the MAC N-RTK technique this assistance data is used to provide raw observables recorded at the Master Reference Station (see clause 8.1.2.1a). + +#### 8.1.2.1.16 RTK Common Observation Information + +RTK Common Observation Information provides the GNSS receiver with common information applicable to any GNSS, e.g. clock steering indicator. This assistance data is always used together GNSS RTK Observations (see clause 8.1.2.1.15). + +#### 8.1.2.1.17 GLONASS RTK Bias Information + +RTK Bias Information provides the GNSS receiver with information which is intended to compensate for the first-order inter-frequency phase-range biases introduced by the reference receiver code-phase biases. This information is applicable only for GLONASS FDMA signals. In the case that the MAC Network RTK method is used, GLONASS RTK Bias Information defines the code-phase biases related to the Master Reference Station [31]. + +#### 8.1.2.1.18 RTK MAC Correction Differences + +RTK MAC Correction Differences provides the GNSS receiver with information about ionospheric (dispersive) and geometric (non-dispersive) corrections generated between a Master Reference Station and its Auxiliary Reference Stations [31]. + +#### 8.1.2.1.19 RTK Residuals + +RTK Residuals provides the GNSS receiver with network error models generated for the interpolated corrections disseminated in Network RTK techniques. With sufficient redundancy in the RTK network, the location server process can provide an estimate for residual interpolation errors. Such quality estimates may be used by the target UE to optimize the performance of RTK solutions. The values may be considered by the target UE as a priori estimates only, with sufficient tracking data available the target UE might be able to judge residual geometric and ionospheric errors itself. According to [31], RTK Residual error information should be transmitted every 10-60 seconds. + +#### 8.1.2.1.20 RTK FKP Gradients + +RTK FKP Gradients provides the GNSS receiver with horizontal gradients for the geometric (troposphere and satellite orbits) and ionospheric signal components in the observation space. According to [31], RTK FKP gradient information should be typically transmitted every 10-60 seconds. + +#### 8.1.2.1.21 SSR Orbit Corrections + +SSR Orbit Corrections provides the GNSS receiver with parameters for orbit corrections in radial, along-track and cross-track components. These orbit corrections are used to compute a satellite position correction, to be combined with satellite position calculated from broadcast ephemeris (see clause 8.1.2.1.7). + +NOTE 1: The orbit corrections define an offset between the broadcast ephemeris orbit and a satellite antenna reference point (ARP) to which the other corrections refer. The exact definition of the reference point along the satellite antenna is implementation-defined by the Network and use of all corrections together shall yield a consistent solution. + +NOTE 2: The UE should not apply any additional corrections for the Satellite Antenna Phase Center (APC) such as Phase Center Offset (PCO) or Phase Center Variation (PCV), except when provided by the Network in which case the UE may optionally apply the additional PCV residuals contained in the SSR Satellite PCV Residuals correction. The Network may form the SSR corrections (e.g. SSR Phase Bias) to minimise the magnitude of the SSR Satellite PCV Residuals correction, i.e. for Network implementations that do not provide this correction or to minimise the impact on the UEs that do not consume this correction. + +For integrity purposes, SSR Orbit Corrections also provides the correlation time for orbit error and orbit error rate, and the mean and standard deviation that bounds the residual Orbit Error and its associated error rate. The SSR Orbit Corrections also includes the satellite and constellation residual risks. These residual risks are the aggregate residual risk for the satellite or constellation Signal in Space including Orbit, Clock, Bias and all other satellite or constellation feared events, but excluding atmospheric effects. + +When applying the integrity bounds as per 8.1.1a, the mean and stdDev must be calculated by projecting the Orbit error mean and variance along the line-of-sight vector between the satellite and the user, according to the following formula: + +$$stdDev_{orbit} = \quad \text{(Equation 8.1.2.1.21-1)}$$ + +$$mean_{orbit} =$$ + +where: + +- $I$ : 3-D line of sight vector from the user to the satellite in the WGS-84 ECEF coordinate frame. +- $R$ : the rotation matrix from satellite along-track (AT), cross-track (CT) and radial (RA) coordinates into the WGS-84 ECEF coordinate frame. $R^T$ denotes the transposed matrix. +- $v$ : the 3-D Orbit error variance vector expressed in satellite along-track, cross-track and radial coordinates. +- $\mu$ : the Mean Orbit Error vector expressed in satellite along-track, cross-track and radial coordinates. + +The vector $v$ is expressed in the SSR Orbit Corrections as the three elements in the Variance Orbit Residual Error Vector. + +#### 8.1.2.1.22 SSR Clock Corrections + +SSR Clock Corrections provides the GNSS receiver with parameters to compute the GNSS satellite clock correction applied to the broadcast satellite clock (see clause 8.1.2.1.7). A polynomial of order 2 describes the clock differences for a certain time period: clock offset, drift, and drift rate. + +For integrity purposes, SSR Clock Corrections also provides the correlation time for clock error and clock error rate, and the mean and standard deviation that bounds the residual Clock Error and its associated error rate. + +#### 8.1.2.1.23 SSR Code Bias + +SSR Code Bias provides the GNSS receiver with the Code Biases that must be added to the pseudo range measurements of the corresponding code signal to get corrected pseudo ranges. SSR Code Bias contains absolute values, but also enables the alternative use of Differential Code Biases by setting one of the biases to zero. A UE can consistently use signals for which a code bias is transmitted. It is not reliable for a UE to use a signal without retrieving a corresponding code bias from the assistance data message. + +For integrity purposes, SSR Code Bias also provides the mean and standard deviation that bounds the residual Code Bias Error and its associated error rate. + +#### 8.1.2.1.24 SSR Phase Bias + +SSR Phase Bias provides the GNSS receiver with the GNSS signal phase bias that are added to the carrier phase measurements of the corresponding signal to get corrected phase ranges. An indicator used to count events when phase bias is discontinuous is provided. An optional indicator is also provided to indicate whether fixed, widelane fixed or float PPP-RTK positioning modes are supported on a per signal basis. + +NOTE 1: On the UE side, phase bias corrections of appropriate type are needed to restore the integer nature of the phase ambiguities in PPP-RTK. Their absence will affect the quality of the positioning solution and prevent a fast convergence time. + +NOTE 2: PPP-RTK Fixed position mode corresponds to the UE fixing the carrier phase ambiguity to an integer value. The PPP-RTK Widelane Fixed positioning mode corresponds to forming the widelane combination of carrier phase measurements and fixing the resulting ambiguity as an integer value. In PPP-RTK Float positioning mode the carrier phase ambiguity is not treated as an integer value. + +NOTE 3: The SSR Phase Bias values must be consistent with a satellite yaw angle of zero as per [36]. + +For integrity purposes, SSR Phase Bias also provides the mean and standard deviation that bounds the residual Phase Bias Error and its associated error rate. + +#### 8.1.2.1.25 SSR STEC Corrections + +SSR STEC Corrections provides the GNSS receiver with the parameters to compute the ionosphere slant delay correction based on a variable order polynomial on a per satellite basis and applied to the code and phase measurements. + +For integrity purposes, SSR STEC Corrections also provides the ionosphere residual risk parameters, correlation time for ionosphere range error and range error rate, and the mean and standard deviation that bounds the residual Ionospheric Error and its associated error rate. + +#### 8.1.2.1.26 SSR Gridded Correction + +SSR Gridded Corrections provides the GNSS receiver with STEC residuals and Troposphere delays at a series of correction points and expressed as hydrostatic and wet vertical delays. + +NOTE: The final ionosphere slant delay (STEC) consists of the polynomial part provided in SSR STEC Correction and the residual part provided in SSR Gridded Corrections. + +For integrity purposes, SSR Gridded Corrections also provides the troposphere residual risk parameters, correlation time for troposphere range error and range error rate, and the mean and standard deviation that bounds the residual Tropospheric Error and associated its error rate in the Vertical Hydro Static Delay and Vertical Wet Delay components. + +#### 8.1.2.1.27 SSR URA + +SSR URA provides the receiver with information about the estimated accuracy of the corrections for each satellite. + +#### 8.1.2.1.28 SSR Correction Points + +The SSR Correction Points provides a list of correction point coordinates or an array of correction points ("grid") for which the SSR Gridded Corrections are valid. + +#### 8.1.2.1.29 Integrity Service Parameters + +Integrity Service Parameters provide the range of Integrity Risk (IR) for which the associated GNSS integrity assistance data is considered to be valid. + +#### 8.1.2.1.30 Integrity Alerts + +Integrity Service Alerts provide information on whether the service can be used for integrity. A Do Not Use (DNU) flag indicates that the corresponding assistance data is not suitable for the purpose of computing integrity. If an Integrity Service Alert is issued and the DNU flag is false, then the corresponding assistance data may be used for the purpose of computing integrity. The DNU flags are defined to be applicable to the specified epoch time only. + +#### 8.1.2.1.31 SSR IOD Update + +SSR IOD Update is used to link assistance data elements based on their Issue of Data (IOD) values, especially for elements which are infrequently updated. The elements with a matching IOD are linked and valid while the SSR IOD Update element is valid, i.e. during the SSR IOD Update and SSR Update Interval and with respect to the IOD SSR. + +NOTE: It is up to the network to ensure that the Update Interval of the SSR IOD Update and the other SSR assistance data elements are configured so as to prevent inconsistent data being used together, i.e. that when the IOD values within the SSR IOD Update change, it does not cause an inconsistency with existing data that is still within its Update Interval, or the change occurs on a boundary where the other assistance data are expiring. + +#### 8.1.2.1.32 SSR Satellite PCV Residuals + +SSR Satellite Phase Center Variation (PCV) Residuals provide only the nadir angle dependent variations of the satellite APC which can be combined with SSR Orbit Correction and SSR Phase Bias to determine the location of the effective center of the satellite antenna. SSR Satellite PCV Residuals may include residual PCO errors that have not been corrected in the SSR Orbit Correction and SSR Phase Bias. + +#### 8.1.2.1a Recommendations for grouping of assistance data to support different RTK service levels + +This clause provides recommendations for the different high-accuracy GNSS service levels: RTK, N-RTK, PPP and PPP-RTK. + +The high-accuracy GNSS methods can be classified as: + +- *Single base RTK service*: RTK is a technique that uses carrier-based ranging measurements i.e., phase-range to improve the positioning accuracy in a differential approach. The basic concept is to reduce and remove errors common to a Reference Station, with known position, and UE pair. When only pseudo ranges (code-based measurements) are used to compute the UE location, this method is known as DGNSS (Differential GNSS). + +**Table 8.1.2.1a-1: Single base RTK service: Specific information that may be transferred from the LMF to the UE** + +| Assistance Data | +|--------------------------------------------------------------------| +| RTK Reference Station Information | +| RTK Observations | +| RTK Common Observation Information | +| GLONASS RTK Bias Information (if GLONASS data is transmitted) | +| Ephemeris and Clock (if UE did not acquire the navigation message) | + +- *Non-Physical Reference Station Network RTK service*: In this approach the target UE receives synthetic observations from a fictitious Reference Station. The Network RTK software at the location server is performing the error estimation and creates a virtual Reference Station close to the initial location of the target device (provided a priori to the location server). The target UE interprets and uses the data just as if it had come from a single, real Reference Station. Additionally, the target UE can also receive network information such as RTK Network Residuals (see clause 8.1.2.1.19) or even FKP gradients (see clause 8.1.2.1.20). + +**Table 8.1.2.1a-2: Non-Physical Reference Station Network RTK service: Specific information that may be transferred from the LMF to the UE** + +| Assistance Data | +|--------------------------------------------------------------------| +| RTK Reference Station Information | +| RTK Observations | +| RTK Common Observation Information | +| GLONASS RTK Bias Information (if GLONASS data is transmitted) | +| RTK Residuals | +| RTK FKP Gradients | +| Ephemeris and Clock (if UE did not acquire the navigation message) | + +- *MAC Network RTK service*: In MAC network RTK, a group of Reference Stations are used and one of them is chosen as a Master station. The other stations are then called Auxiliary stations. In this service, the location server sends full raw observations and coordinate information for a single Reference Station, the Master Station. For all auxiliary stations in the network (or a suitable subset of stations) the information is provided to the UE in a highly compact form: their reduced ambiguity-levelled observations, coordinate differences (to the Master Station observations and coordinates), and network residuals. Two Reference Stations are said to be on a common ambiguity level if the integer ambiguities for each phase range (satellite-receiver pair) have been removed (or adjusted) so that the integer ambiguities cancel when double-differences (involving two receivers and two satellites) are formed during processing. The maintenance of a common ambiguity level at a specific set of stations rather than across the whole GNSS network will lead to a grouping in network clusters or subnetworks of all ambiguity-levelled Reference Stations. If one network has only one subnetwork, this indicates that an ambiguity level throughout the whole network is established. When subnetworks are predefined, the assistance data can be broadcast to all UEs located in the assigned sub-network. More details on the usage of subnetworks can be found in [31]. + +**Table 8.1.2.1a-3: MAC Network RTK service: Specific Information that may be transferred from the LMF to the UE** + +| Assistance Data | +|--------------------------------------------------------------------| +| RTK Reference Station Information | +| RTK Auxiliary Station Data | +| RTK Observations | +| RTK Common Observation Information | +| GLONASS RTK Bias Information (if GLONASS data is transmitted) | +| RTK MAC Correction Differences | +| RTK Residuals | +| Ephemeris and Clock (if UE did not acquire the navigation message) | + +- *FKP Network RTK service*: With the concept of FKP, horizontal gradients of distance-dependent errors like ionosphere, troposphere and orbits are derived from a network of GNSS Reference Stations and transmitted to a target device together with raw or correction data of a corresponding Reference Station (physical or non physical). The target UE may use the gradients to compute the effect of the distance-dependent errors for its own position. + +**Table 8.1.2.1a-4: FKP Network RTK service: Information that may be transferred from the LMF to the UE** + +| Assistance Data | +|--------------------------------------------------------------------| +| RTK Reference Station Information | +| RTK Observations | +| RTK Common Observation Information | +| GLONASS RTK Bias Information (if GLONASS data is transmitted) | +| RTK Residuals | +| RTK FKP Gradients | +| Ephemeris and Clock (if UE did not acquire the navigation message) | + +- *PPP service*: This concept uses precise satellite orbit and clock parameters derived from global networks of Reference Stations as well as atmospheric models to perform single station positioning [31]. Compared to RTK and Network RTK, PPP is not a differential technique as there is no baseline limitation. When the orbits and clocks assistance data elements are provided in real-time, with no latency, the method is called Real-Time PPP. + +**Table 8.1.2.1a-5: SSR PPP service: Information that may be transferred from the LMF to the UE** + +| Assistance Data | +|--------------------------------------------------------------------| +| SSR Orbit Corrections | +| SSR Clock corrections | +| SSR Code Bias | +| Ephemeris and Clock (if UE did not acquire the navigation message) | +| SSR IOD Update | +| SSR Satellite PCV Residuals | + +- *PPP-RTK service*: This concept uses precise satellite orbits and clock parameters, the satellite signal biases derived from global networks of Reference Stations as well as ionosphere and troposphere corrections to perform single station positioning IS-QZSS-L6-001 [36]. Therefore, PPP-RTK services compensate the global and local corrections for a more accurate location information. Compared to PPP, PPP-RTK requires the UE to be located within the region covered by the ionosphere and troposphere corrections. + +**Table 8.1.2.1a-6: SSR PPP-RTK service: Information that may be transferred from the LMF to the UE** + +| Assistance Data | +|--------------------------------------------------------------------| +| SSR Orbit Corrections | +| SSR Clock corrections | +| SSR Code Bias | +| Ephemeris and Clock (if UE did not acquire the navigation message) | +| SSR Phase Bias | +| SSR STEC Corrections | +| SSR Gridded Correction | +| SSR URA | +| SSR Correction Points | +| SSR IOD Update | +| SSR Satellite PCV Residuals | + +### 8.1.2.1b Mapping of integrity parameters + +Table 8.1.2.1b-1 shows the mapping between the integrity fields and the SSR assistance data according to the Integrity Principle of Operation (Clause 7.13.2). The corresponding field descriptions for each of the field names listed in Table 8.1.2.1b-1 are specified under Clause 6.5.2.2 of TS 37.355 [42]. + +**Table 8.1.2.1b-1: Mapping of Integrity Parameters** + +| Error | GNSS Assistance Data | Integrity Fields | | | | | +|-----------------------------------------|-----------------------------------------------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| | | Integrity Alerts | Integrity Bounds (Mean) | Integrity Bounds (StdDev) | Residual Risks | Integrity Correlation Times | +| Orbit | SSR Orbit Corrections | Real-Time Integrity (see Clause 8.1.2.1.8) | Mean Orbit Error
Mean Orbit Rate Error (Calculated according to Equation 8.1.2.1.21-1) | Standard Deviation Orbit Error
Standard Deviation Orbit Rate Error (Calculated according to Equation 8.1.2.1.21-1) | Probability of Onset of Constellation Fault
Probability of Onset of Satellite Fault | Orbit Range Error Correlation Time
Orbit Range Rate Error Correlation Time | +| Clock | SSR Clock Corrections | | Mean Clock Error
Mean Clock Rate Error | Standard Deviation Clock Error
Standard Deviation Clock Rate Error | Mean Constellation Fault Duration
Mean Satellite Fault Duration | Clock Range Error Correlation Time
Clock Range Rate Error Correlation Time | +| Code Bias | SSR Code Bias | | Mean Code Bias Error
Mean Code Bias Rate Error | Standard Deviation Code Bias Error
Standard Deviation Code Bias Rate Error | | | +| Phase Bias | SSR Phase Bias
SSR Satellite PCV Residuals | | Mean Phase Bias Error
Mean Phase Bias Rate Error | Standard Deviation Phase Bias Error
Standard Deviation Phase Bias Rate Error | | | +| Ionosphere | SSR STEC Correction | Ionosphere DNU | Mean Ionospher Error
Mean Ionospher Rate Error | Standard Deviation Ionosphere Error
Standard Deviation Ionosphere Rate Error | Probability of Onset of Ionosphere Fault
Mean Ionosphere Fault Duration | Ionosphere Range Error Correlation Time
Ionosphere Range Rate Error Correlation Time | +| Troposphere Vertical Hydro Static Delay | SSR Gridded Corrections | Troposphere DNU | Mean Troposphere Vertical Hydro Static Delay Error
Mean Troposphere Vertical Hydro Static Delay Rate Error | Standard Deviation Troposphere Vertical Hydro Static Delay Error
Standard Deviation Troposphere Vertical Hydro Static Delay Rate Error | Probability of Onset of Troposphere Fault
Mean Troposphere Fault Duration | Troposphere Range Error Correlation Time
Troposphere Range Rate Error Correlation Time | +| Troposphere Vertical WetDelay | | | Mean Troposphere Vertical Wet Delay Error
Mean Troposphere Vertical Wet Delay Rate Error | Standard Deviation Troposphere Vertical Wet Delay Error
Standard Deviation Troposphere Vertical Wet Delay Rate Error | | | + +### 8.1.2.2 Information that may be transferred from the UE to LMF + +#### 8.1.2.2.0 General + +The information that may be signalled from UE to the LMF is listed in table 8.1.2.2.0-1. + +**Table 8.1.2.2.0-1: Information that may be transferred from UE to the LMF** + +| Information | UE-assisted | UE-based/
standalone | +|----------------------------------------------------------------------------------------|-------------|-------------------------| +| Latitude/Longitude/Altitude, together with uncertainty shape | No | Yes | +| Velocity, together with uncertainty shape | No | Yes | +| Reference Time, possibly together with GNSS to NG-RAN time association and uncertainty | Yes | Yes | +| Indication of used positioning methods in the fix | No | Yes | +| Code phase measurements, also called pseudorange | Yes | No | +| Doppler measurements | Yes | No | +| Carrier phase measurements, also called Accumulated Delta Range (ADR) | Yes | No | +| Carrier-to-noise ratio of the received signal | Yes | No | +| Measurement quality parameters for each measurement | Yes | No | +| Additional, non-GNSS related measurement information | Yes | No | +| Protection Level, optionally together with achievable Target Integrity Risk | No | Yes | + +#### 8.1.2.2.1 GNSS Measurement Information + +##### 8.1.2.2.1.0 General + +The GNSS measurement information reported from the UE to the LMF depends on the GNSS mode (i.e., UE-based, autonomous (standalone), or UE-assisted). + +##### 8.1.2.2.1.1 UE-based mode + +In UE-based or standalone mode, the GNSS receiver reports the latitude, longitude and possibly altitude, together with an estimate of the location uncertainty, if available. + +If requested by the LMF and supported by the UE, the GNSS receiver may report its velocity, possibly together with an estimate of the uncertainty, if available. + +If requested by the LMF and supported by the UE, the GNSS receiver may report the relation between GNSS system time (where the specific GNSS is indicated by a GNSS ID; the specific GNSS system time may be selected by the UE) and NG-RAN air-interface timing. This information may be used by the LMF to assist other UEs in the network. + +The UE should also report an indication of which GNSSs and possibly other location methods have been used to calculate a fix. + +##### 8.1.2.2.1.2 UE-assisted mode + +In UE-assisted mode, the GNSS receiver reports the Code Phase and Doppler measurements together with associated quality estimates. These measurements enable the LMF to calculate the location of the UE, possibly using other measurements and data. + +If requested by the LMF and supported by the UE, the GNSS receiver may report Carrier Phase measurements (also called Accumulated Delta Range), together with associated quality measurements, if available. + +If requested by the LMF and supported by the UE, the GNSS receiver may report the relation between GNSS system time (where the specific GNSS is indicated by a GNSS ID; the specific GNSS system time may be selected by the UE) and NG-RAN air-interface timing. This information may be used by the LMF to assist other UEs in the network. + +#### 8.1.2.2.2 Additional Non-GNSS Related Information + +Additional non-GNSS measurements performed by NG-RAN or UE may be used by the LMF or UE to calculate or verify a location estimate. This information may include OTDOA positioning measurements, pathloss and signal strength related measurements, etc. + +### 8.1.3 Assisted-GNSS Positioning Procedures + +#### 8.1.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for Assisted-GNSS positioning is described in clause 7.1.2.1. + +#### 8.1.3.2 Assistance Data Transfer Procedure + +##### 8.1.3.2.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). In the case of high-accuracy GNSS positioning techniques (e.g., RTK), the LMF can provide unsolicited periodic assistance data to the UE and the UE can request periodic assistance data from the LMF. + +##### 8.1.3.2.1 LMF initiated Assistance Data Delivery + +Figure 8.1.3.2.1-1 shows the Assistance Data Delivery operations for the network-assisted GNSS method when the procedure is initiated by the LMF. + +![Sequence diagram showing the LMF-initiated Assistance Data Delivery Procedure. The diagram consists of two vertical lifelines labeled 'UE' on the left and 'LMF' on the right. A horizontal arrow points from the LMF lifeline to the UE lifeline, labeled '1. LPP Provide Assistance Data'.](96c8d8b0159c47a7478ada46d781060b_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. LPP Provide Assistance Data + LMF->>UE: 1. LPP Provide Assistance Data +``` + +Sequence diagram showing the LMF-initiated Assistance Data Delivery Procedure. The diagram consists of two vertical lifelines labeled 'UE' on the left and 'LMF' on the right. A horizontal arrow points from the LMF lifeline to the UE lifeline, labeled '1. LPP Provide Assistance Data'. + +**Figure 8.1.3.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the GNSS assistance data defined in clause 8.1.2.1. + +##### 8.1.3.2.1a LMF initiated Periodic Assistance Data Delivery + +The Periodic Assistance Data Delivery procedure allows the server to provide unsolicited periodic assistance data to the target and is shown in Figure 8.1.3.2.1a-1. + +NOTE: In this version of the specification, periodic assistance data delivery is supported for HA GNSS (e.g., RTK) positioning only. + +![Sequence diagram for LPP Periodic Assistance data delivery procedure. It shows two vertical lifelines. The left lifeline has a box at the top with the text 'UE' inside. The right lifeline has a box at the top with the text 'LMF' inside. Three messages are shown from the LMF to the UE: 1. A solid line labeled '1. LPP Provide Assistance Data'. 2. A solid line labeled '2. LPP Provide Assistance Data'. 3. A dashed line labeled '3. LPP Provide Assistance Data'. On the LMF side, there are three corresponding bracket-like shapes indicating the sequence of events.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +Sequence diagram for LPP Periodic Assistance data delivery procedure. It shows two vertical lifelines. The left lifeline has a box at the top with the text 'UE' inside. The right lifeline has a box at the top with the text 'LMF' inside. Three messages are shown from the LMF to the UE: 1. A solid line labeled '1. LPP Provide Assistance Data'. 2. A solid line labeled '2. LPP Provide Assistance Data'. 3. A dashed line labeled '3. LPP Provide Assistance Data'. On the LMF side, there are three corresponding bracket-like shapes indicating the sequence of events. + +**Figure 8.1.3.2.1a-1: LPP Periodic Assistance data delivery procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE and sends an LPP Provide Assistance Data message to the UE. This message includes information to identify the type of periodic assistance data and a duration for ending the assistance data delivery. The message indicates the end of the control transaction. +- (2) When the first periodic message is available, the LMF sends an unsolicited LPP Provide Assistance Data message to the UE containing the periodic assistance data announced in step (1). +- (3) The LMF may continue to send further LPP Provide Assistance Data messages to the target containing the periodic assistance data announced in step (1) when each additional periodicity condition occurs. When the duration for ending the periodic assistance data transfer occurs, the last LPP Provide Assistance Data message transferred indicates the end of transaction. Additionally, the session can be ended on request by the UE or by the LMF with the help of an Abort message. + +#### 8.1.3.2.2 UE initiated Assistance Data Transfer + +Figure 8.1.3.2.2-1 shows the Assistance Data Transfer operations for the network-assisted GNSS method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines. The left lifeline has a box at the top with the text 'UE' inside. The right lifeline has a box at the top with the text 'LMF' inside. Two messages are shown: 1. A solid line from the UE to the LMF labeled '1. LPP Request Assistance Data'. 2. A solid line from the LMF to the UE labeled '2. LPP Provide Assistance Data'.](0d9b44054c70dcda35129f11b97a912f_img.jpg) + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines. The left lifeline has a box at the top with the text 'UE' inside. The right lifeline has a box at the top with the text 'LMF' inside. Two messages are shown: 1. A solid line from the UE to the LMF labeled '1. LPP Request Assistance Data'. 2. A solid line from the LMF to the UE labeled '2. LPP Provide Assistance Data'. + +**Figure 8.1.3.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain A-GNSS assistance data are desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific A-GNSS assistance data are requested for each GNSS, possibly together with additional information (e.g., for which GNSS signal types, or satellites, or times the assistance is requested, etc.). Additional information concerning the UE's approximate location and serving and neighbour cells may also be provided in the Request Assistance Data message and/or in an accompanying Provide Location Information message to help the LMF provide appropriate + +assistance data. This additional data may include the UE's last known location if available, the cell IDs of the UE serving NG-RAN node and possibly neighbour NG-RAN nodes, as well as E-UTRA E-CID measurements. + +- (2) The LMF provides the requested assistance data in a LPP Provide Assistance Data message, if available at the LMF. The entire set of assistance data may be delivered in one or several LPP messages, e.g., one message per GNSS. In this case, this step may be repeated by the LMF several times. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +#### 8.1.3.2.2a UE initiated Periodic Assistance Data Transfer + +Figure 8.1.3.2.2a-1 shows the Periodic Assistance Data Transfer operations for the high-accuracy GNSS methods (e.g., RTK) when the procedure is initiated by the UE. + +NOTE: In this version of the specification, periodic assistance data transfer is supported for HA GNSS (e.g., RTK) positioning only. + +![Sequence diagram illustrating the UE-initiated Periodic Assistance Data Transfer Procedure. The diagram shows two vertical lifelines: UE (left) and LMF (right). The sequence of messages is: 1. UE sends a solid arrow message to LMF. 2. LMF responds with a solid arrow message to UE. 3. LMF sends a dashed arrow message to UE. 4. LMF sends another solid arrow message to UE. Brackets on the LMF side group the last three messages (steps 2, 3, and 4).](0cc154cbdde7cc6c39f394597c7aca0c_img.jpg) + +Sequence diagram illustrating the UE-initiated Periodic Assistance Data Transfer Procedure. The diagram shows two vertical lifelines: UE (left) and LMF (right). The sequence of messages is: 1. UE sends a solid arrow message to LMF. 2. LMF responds with a solid arrow message to UE. 3. LMF sends a dashed arrow message to UE. 4. LMF sends another solid arrow message to UE. Brackets on the LMF side group the last three messages (steps 2, 3, and 4). + +**Figure 8.1.3.2.2a-1: UE-initiated Periodic Assistance Data Transfer Procedure** + +- (1) The UE determines that periodic assistance data are desired and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific assistance data are requested together with additional information such as desired periodicity for sending the assistance data and a duration for ending the periodic assistance data delivery session. +- (2) The LMF responds with a LPP Provide Assistance Data message to the UE. If the UE request can be supported, the message contains information which may confirm or redefine the type of assistance data or periodicity parameters requested at step (1). This response indicates the end of the control transaction. +- (3) When available, the LMF provides the requested assistance data in a LPP Provide Assistance Data message to the UE. If any of the requested assistance data in step (1) or redefined in step (2) are not provided the UE assumes that the requested assistance data are not supported, or currently not available at the LMF. +- (4) The LMF may transmit one or more additional LPP Provide Assistance Data messages to the UE containing further periodic assistance data confirmed or redefined in step (2). When the duration for ending the periodic assistance data transfer occur, the last LPP Provide Assistance Data message transferred indicates the end of the + +transaction. Additionally, the periodic assistance data delivery session can be ended on request by the UE or by the LMF with the help of an Abort message. + +### 8.1.3.3 Location Information Transfer Procedure + +#### 8.1.3.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements or location estimate from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +#### 8.1.3.3.1 LMF initiated Location Information Transfer Procedure + +Figure 8.1.3.3.1-1 shows the Location Information Transfer operations for the network-assisted GNSS method when the procedure is initiated by the LMF. + +![Sequence diagram of LMF-initiated Location Information Transfer Procedure](c6e0b9030f9fb81435eaf9cb71532614_img.jpg) + +A sequence diagram showing the interaction between a User Equipment (UE) and a Location Management Function (LMF). The UE is represented by a box on the left and the LMF by a box on the right. Two vertical lines extend downwards from each box, representing their lifelines. The first message is a horizontal arrow pointing from the LMF lifeline to the UE lifeline, labeled '1. LPP Request Location Information'. The second message is a horizontal arrow pointing from the UE lifeline to the LMF lifeline, labeled '2. LPP Provide Location Information'. + +Sequence diagram of LMF-initiated Location Information Transfer Procedure + +**Figure 8.1.3.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of A-GNSS positioning. This request includes positioning instructions such as the GNSS mode (UE-assisted, UE-based, UE-based preferred but UE-assisted allowed, UE-assisted preferred, but UE-based allowed, standalone), positioning methods (GPS, Galileo, GLONASS, BDS, NavIC, etc. and possibly non-GNSS methods, such as OTDOA positioning or E-CID positioning), specific UE measurements requested if any, such as fine time assistance measurements, velocity, carrier phase, multi-frequency measurements, quality of service parameters (accuracy, response time), and possibly integrity requirements. +- (2) The UE performs the requested measurements and possibly calculates its own location. The UE may also determine the integrity results of the calculated location. The UE sends an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. If the UE is unable to perform the requested measurements, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.1.3.3.2 UE-initiated Location Information Delivery Procedure + +Figure 8.1.3.3.2-1 shows the Location Information delivery operations for the UE-assisted GNSS method when the procedure is initiated by the UE. + +![Sequence diagram showing the UE-initiated Location Information Delivery Procedure. A User Equipment (UE) box on the left sends a message labeled '1. LPP Provide Location Information' to a Location Management Function (LMF) box on the right. Vertical lines extend downwards from both boxes, indicating the timeline of the procedure.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + UE->>LMF: 1. LPP Provide Location Information + Note right of LMF: + Note left of UE: + Note right of LMF: +``` + +Sequence diagram showing the UE-initiated Location Information Delivery Procedure. A User Equipment (UE) box on the left sends a message labeled '1. LPP Provide Location Information' to a Location Management Function (LMF) box on the right. Vertical lines extend downwards from both boxes, indicating the timeline of the procedure. + +**Figure 8.1.3.3.2-1: UE-initiated Location Information Delivery Procedure** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE measurements (GNSS pseudo-ranges, carrier phase-ranges, and other measurements) already available at the UE. + +## 8.2 OTDOA positioning + +### 8.2.1 General + +In this version of the specification, only OTDOA based on LTE signals is supported. + +In the OTDOA positioning method, the UE position is estimated based on measurements taken at the UE of downlink radio signals from multiple E-UTRA TPs (possibly including PRS-only E-UTRA TPs from a PRS-based TBS), along with knowledge of the geographical coordinates of the measured TPs and their relative downlink timing. + +The UE while connected to a gNB may require measurement gaps to perform the OTDOA measurements from E-UTRA TPs. The UE may request measurement gaps from a gNB using the procedure described in clause 7.4.1.1. If the UE is not aware of the SFN of at least one E-UTRA TP in the OTDOA assistance data, the UE may use autonomous gaps to acquire SFN of the E-UTRA OTDOA reference cell prior to requesting measurement gaps for performing the requested E-UTRA RSTD measurements. + +The UE while connected to a ng-eNB may require measurement gaps to perform inter-frequency RSTD measurements for OTDOA from E-UTRA TPs (see TS 38.133 [32]). The UE may request measurement gaps from a ng-eNB using the procedure described in clause 7.4.2.1. + +The specific positioning techniques used to estimate the UE's location from this information are beyond the scope of this specification. + +### 8.2.2 Information to be transferred between NG-RAN/5GC Elements + +#### 8.2.2.0 General + +This clause defines the information that may be transferred between LMF and UE/ng-eNB. + +#### 8.2.2.1 Information that may be transferred from the LMF to UE + +The following assistance data may be transferred from the LMF to the UE: + +- Physical cell IDs (PCIs), global cell IDs (GCIs), and TP IDs of candidate E-UTRA TPs for measurement; +- Timing relative to the reference E-UTRA TP of candidate E-UTRA TPs; +- PRS configuration of candidate E-UTRA TPs; +- If known, the SFN timing offset between the serving NR cell and the E-UTRA assistance data reference cell. + +NOTE: The LMF can provide the UE with a list of E-UTRA TP candidates for measurement, even if the LMF does not know the SFN or frame timing of the E-UTRA TPs. + +### 8.2.2.2 Information that may be transferred from the ng-eNB to LMF + +The following assistance data may be transferred from the ng-eNB to the LMF: + +- PCI, GCI, and TP IDs of the TPs served by the ng-eNB; +- Timing information of TPs served by the ng-eNB; +- PRS configuration of the TPs served by the ng-eNB; +- Geographical coordinates of the TPs served by the ng-eNB. + +An ng-eNB may provide assistance data relating only to itself and served TPs via NRPPa signalling, although assistance data from several ng-eNBs and served TPs may be acquired through other mechanisms, see NOTE below. + +NOTE: The assistance data described in this clause are not necessarily transferred only from the ng-eNB, and in some deployment options may not be delivered from the ng-eNB at all; they may also be delivered to the LMF through OAM or other mechanisms external to the NG-RAN. In addition, in cases where assistance data are delivered from the ng-eNB, how the ng-eNB acquires the data is outside the scope of this specification. + +### 8.2.2.3 Information that may be transferred from the UE to LMF + +The information that may be signalled from UE to the LMF is listed in Table 8.2.2.3-1. The individual UE measurements are defined in TS 36.214 [17]. + +**Table 8.2.2.3-1: Information that may be transferred from UE to the LMF** + +| Information | Measurements | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| Downlink Measurement Results List for EUTRA TPs | Physical cell IDs | +| | Global cell IDs | +| | TP IDs | +| | Downlink timing measurements | +| Information used to compute a reference time corresponding to the downlink timing measurements to allow correlation of downlink timing measurements with motion information independently obtained from motion sensors | Delta SFN for each E-UTRA neighbour cell | + +### 8.2.2.4 Information that may be transferred from the gNB to LMF + +The following assistance data may be transferred from the gNB to the LMF: + +- NR CGI and timing information of the cells served by the gNB; +- Geographical coordinates of the access points associated with each cell served by the gNB. + +## 8.2.3 OTDOA Positioning Procedures + +### 8.2.3.0 General + +The procedures described in this clause support OTDOA positioning measurements obtained by the UE and provided to the LMF using LPP. + +In this version of the specification only the UE-assisted OTDOA positioning is supported. + +### 8.2.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for OTDOA positioning is described in clause 7.1.2.1. + +### 8.2.3.2 Assistance Data Transfer Procedure + +#### 8.2.3.2.1 Assistance Data Transfer between LMF and UE + +##### 8.2.3.2.1.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). + +##### 8.2.3.2.1.1 LMF initiated Assistance Data Delivery + +Figure 8.2.3.2.1.1-1 shows the Assistance Data Delivery operations for the OTDOA positioning method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Assistance Data Delivery Procedure. It shows two vertical lifelines for UE and LMF. A single message arrow labeled '1. LPP Provide Assistance Data' points from the LMF lifeline to the UE lifeline.](bbd36eba6bb7c4ba87608874c8c714ff_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + Note right of LMF: + LMF->>UE: 1. LPP Provide Assistance Data +``` + +Sequence diagram for LMF-initiated Assistance Data Delivery Procedure. It shows two vertical lifelines for UE and LMF. A single message arrow labeled '1. LPP Provide Assistance Data' points from the LMF lifeline to the UE lifeline. + +**Figure 8.2.3.2.1.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the OTDOA positioning assistance data defined in clause 8.2.2.1. + +##### 8.2.3.2.1.2 UE initiated Assistance Data Transfer + +Figure 8.2.3.2.1.2-1 shows the Assistance Data Transfer operations for the OTDOA positioning method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines for UE and LMF. Two message arrows are shown: '1. LPP Request Assistance Data' from UE to LMF, and '2. LPP Provide Assistance Data' from LMF to UE.](e7378ff7bbd173cc8bd53a621907dc1d_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + Note right of LMF: + UE->>LMF: 1. LPP Request Assistance Data + LMF->>UE: 2. LPP Provide Assistance Data +``` + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines for UE and LMF. Two message arrows are shown: '1. LPP Request Assistance Data' from UE to LMF, and '2. LPP Provide Assistance Data' from LMF to UE. + +**Figure 8.2.3.2.1.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain OTDOA positioning assistance data are desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends an LPP Request Assistance Data message to the LMF. This request includes an indication of which specific OTDOA assistance data are requested. Additional information concerning the UE's approximate location and serving and neighbour cells may also be provided in the Request Assistance Data message and/or in an + +accompanying Provide Location Information message to help the LMF provide appropriate assistance data. This additional data may include the UE's last known location if available, the cell IDs of the UE serving NG-RAN node and possibly neighbour NG-RAN nodes, as well as E-UTRA E-CID measurements. + +- (2) The LMF provides the requested assistance in an LPP Provide Assistance Data message, if available at the LMF. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +#### 8.2.3.2.2 Assistance Data Delivery between LMF and NG-RAN node + +##### 8.2.3.2.2.0 General + +The purpose of this procedure is to enable the NG-RAN node to provide assistance data to the LMF, for subsequent delivery to the UE using the procedures of clause 8.2.3.2.1 or for use in the calculation of positioning estimates at the LMF. + +##### 8.2.3.2.2.1 LMF-initiated assistance data delivery to the LMF + +Figure 8.2.3.2.2.1-1 shows the Assistance Data Delivery operation from the NG-RAN node to the LMF for the OTDOA positioning method, in the case that the procedure is initiated by the LMF. + +![Sequence diagram showing LMF-initiated Assistance Data Delivery Procedure. The LMF sends an NRPPa Message (Type: OTDOA INFORMATION REQUEST) to the NG-RAN node, and the NG-RAN node responds with an NRPPa Message (Type: OTDOA INFORMATION RESPONSE/FAILURE).](7c57192c514175021e4560a1a46126c1_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN node + Note left of LMF: LMF-initiated Assistance Data Delivery Procedure + LMF->>NG-RAN node: 1. NRPPa Message (Type: OTDOA INFORMATION REQUEST) + NG-RAN node-->>LMF: 2. NRPPa Message (Type: OTDOA INFORMATION RESPONSE/FAILURE) +``` + +Sequence diagram showing LMF-initiated Assistance Data Delivery Procedure. The LMF sends an NRPPa Message (Type: OTDOA INFORMATION REQUEST) to the NG-RAN node, and the NG-RAN node responds with an NRPPa Message (Type: OTDOA INFORMATION RESPONSE/FAILURE). + +**Figure 8.2.3.2.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that certain OTDOA positioning assistance data are desired (e.g., as part of a periodic update or as triggered by OAM) and sends an NRPPa OTDOA INFORMATION REQUEST message to the NG-RAN node. This request includes an indication of which specific OTDOA assistance data are requested. +- (2) The NG-RAN node provides the requested assistance in an NRPPa OTDOA INFORMATION RESPONSE message, if available at the NG-RAN node. If the NG-RAN node is not able to provide any information, it returns an OTDOA INFORMATION FAILURE message indicating the cause of the failure. + +#### 8.2.3.3 Location Information Transfer Procedure + +##### 8.2.3.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +##### 8.2.3.3.1 LMF-initiated Location Information Transfer Procedure + +Figure 8.2.3.3.1-1 shows the Location Information Transfer operations for the OTDOA positioning method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure. The diagram shows two lifelines: UE and LMF. Step 1: LMF sends '1. LPP Request Location Information' to UE. Step 2: UE sends '2. LPP Provide Location Information' to LMF.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. LPP Request Location Information + LMF->>UE: 1. LPP Request Location Information + Note left of UE: 2. LPP Provide Location Information + UE->>LMF: 2. LPP Provide Location Information +``` + +Sequence diagram for LMF-initiated Location Information Transfer Procedure. The diagram shows two lifelines: UE and LMF. Step 1: LMF sends '1. LPP Request Location Information' to UE. Step 2: UE sends '2. LPP Provide Location Information' to LMF. + +**Figure 8.2.3.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends an LPP Request Location Information message to the UE. This request includes indication of OTDOA measurements requested, including any needed measurement configuration information, and required response time. +- (2) The UE obtains OTDOA measurements as requested in step 1. The UE then sends an LPP Provide Location Information message to the LMF, before the Response Time provided in step (1) elapsed, and includes the obtained OTDOA measurements. If the UE is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.2.3.3.2 UE-initiated Location Information Delivery procedure + +Figure 8.2.3.3.2-1 shows the Location Information Delivery procedure operations for the OTDOA positioning method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Location Information Delivery Procedure. The diagram shows two lifelines: UE and LMF. Step 1: UE sends '1. LPP Provide Location Information' to LMF.](e48a7aa9d3880694350259852fefbef2_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: 1. LPP Provide Location Information + UE->>LMF: 1. LPP Provide Location Information +``` + +Sequence diagram for UE-initiated Location Information Delivery Procedure. The diagram shows two lifelines: UE and LMF. Step 1: UE sends '1. LPP Provide Location Information' to LMF. + +**Figure 8.2.3.3.2-1: UE-initiated Location Information Delivery Procedure.** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE OTDOA measurements already available at the UE. + +### 8.3 Enhanced cell ID positioning methods + +#### 8.3.1 General + +In the Cell ID (CID) positioning method, the UE position is estimated with the knowledge of the geographical coordinates of its serving ng-eNB or gNB. + +Enhanced Cell ID (E-CID) based on LTE signals positioning refers to techniques which use UE and/or NG-RAN radio resource related measurements to improve the UE location estimate. In the case of a serving ng-eNB, uplink E-CID may use inter-RAT NR, GERAN, UTRA or WLAN measurements reported by UE. + +NOTE 1: For E-CID positioning methods the UE reports only the measurements that it has available rather than being required to take additional measurement actions. Therefore, the measurement gap request procedure described in clause 7.4.1.1 is not applicable for E-CID positioning methods. + +E-CID measurements for E-UTRA may include [17, 18]: + +UE measurements (TS 36.214 [17], TS 36.302 [18]): + +- E-UTRA Reference signal received power (RSRP); +- E-UTRA Reference Signal Received Quality (RSRQ); +- UE E-UTRA Rx – Tx time difference; + +E-CID UE measurements for other RAT may include: + +- GERAN RSSI; +- UTRAN CPICH RSCP; +- UTRAN CPICH Ec/Io; +- WLAN RSSI. +- SS Reference signal received power (SS-RSRP); +- SS Reference Signal Received Quality (SS-RSRQ); + +NOTE 2: The above GERAN, UTRAN, WLAN and NR measurements by UE are only used for Uplink E-CID positioning. + +ng-eNB measurements (TS 36.214 [17], TS 36.302 [18]): + +- ng-eNB Rx – Tx time difference; +- Timing Advance ( $T_{ADV}$ ): + - Type1: $T_{ADV} = (\text{ng-eNB Rx – Tx time difference}) + (\text{UE E-UTRA Rx – Tx time difference})$ ; + - Type2: $T_{ADV} = \text{ng-eNB Rx – Tx time difference}$ ; +- Angle of Arrival (AoA). + +Various techniques exist to use these measurements to estimate the location of the UE. The specific techniques are beyond the scope of this specification. + +## 8.3.2 Information to be transferred between NG-RAN/5GC Elements + +### 8.3.2.0 General + +This clause defines the information that may be transferred between LMF and UE/NG-RAN node. + +#### 8.3.2.1 Information that may be transferred from the LMF to UE + +UE-assisted Enhanced Cell-ID location does not require any assistance data to be transferred from the LMF to the UE. + +UE-Based Enhanced Cell-ID location is not supported in this version of the specification. + +#### 8.3.2.2 Information that may be transferred from the ng-eNB to LMF + +The information that may be signalled from ng-eNB to the LMF is listed in table 8.3.2.2-1. + +**Table 8.3.2.2-1: Information that may be transferred from ng-eNB to the LMF** + +| Information | +|----------------------------------------------------------| +| Timing Advance (T ADV ) | +| Angle of Arrival (AoA) | +| E-UTRA Measurement Results List: | +| - Evolved Cell Global Identifier (ECGI)/Physical Cell ID | +| - E-UTRA Reference signal received power (RSRP) | +| - E-UTRA Reference Signal Received Quality (RSRQ) | +| GERAN Measurement Results List: | +| - Base Station Identity Code (BSIC) | +| - ARFCN of Base Station Control Channel (BCCH) | +| - Received Signal Strength Indicator (RSSI) | +| UTRA Measurement Results List: | +| - UTRAN Physical ID | +| - Common Pilot Channel Received Signal Code Power (RSCP) | +| - Common Pilot Channel Ec/Io | +| WLAN Measurement Results List: | +| - WLAN Received Signal Strength Indicator (RSSI) | +| - SSID | +| - BSSID | +| - HESSID | +| - Operating Class | +| - Country Code | +| - WLAN Channel(s) | +| - WLAN Band | +| NR Measurement Results List: | +| - SS Reference Signal Received Power (SS-RSRP) | +| - SS Reference Signal Received Quality (SS-RSRQ) | +| - NR Physical Cell ID | + +Both cell-level and beam-level measurements for SS-RSRP and SS-RSRQ are supported. + +### 8.3.2.3 Information that may be transferred from the gNB to LMF + +The information that may be signalled from gNB to the LMF is listed in table 8.3.2.3-1. + +**Table 8.3.2.3-1: Information that may be transferred from gNB to the LMF** + +| Information | +|--------------------------------------------| +| NR Measurement Results List: | +| - Cell Global Identifier /Physical Cell ID | +| - Cell Portion ID | + +### 8.3.2.4 Information that may be transferred from the UE to LMF + +The information that may be signalled from UE to the LMF is listed in table 8.3.2.4-1. + +**Table 8.3.2.4-1: Information that may be transferred from UE to the LMF** + +| Information | UE-assisted | +|--------------------------------------------------------|-------------| +| Evolved Cell Global Identifier (ECGI)/Physical Cell ID | Yes | +| E-UTRA Reference signal received power (RSRP) | Yes | +| E-UTRA Reference Signal Received Quality (RSRQ) | Yes | +| UE E-UTRA Rx – Tx time difference | Yes | + +### 8.3.3 Downlink E-CID Positioning Procedures + +#### 8.3.3.0 General + +The procedures described in this clause support E-CID related measurements obtained by the UE and provided to the LMF using LPP. The term "downlink" is intended to indicate that from the LMF perspective the involved measurements are provided by the UE; this set of procedures might also be considered as "UE-assisted, LMF-based E-CID". + +#### 8.3.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for E-CID positioning is described in clause 7.1.2.1. + +#### 8.3.3.2 Assistance Data Transfer Procedure + +Assistance data transfer is not required for E-CID positioning. + +#### 8.3.3.3 Location Information Transfer Procedure + +The purpose of this procedure is to enable the LMF to request position measurements from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +##### 8.3.3.3.1 LMF-initiated Location Information Transfer + +Figure 8.3.3.3-1 shows the Location Information Transfer operations for the E-CID method when the procedure is initiated by the LMF. + +![Sequence diagram showing the LMF-initiated Location Information Transfer Procedure. The diagram consists of two vertical lifelines labeled 'UE' and 'LMF'. Step 1 is a message from the LMF to the UE labeled '1. LPP Request Location Information'. Step 2 is a message from the UE to the LMF labeled '2. LPP Provide Location Information'.](4f95964fc4eb05cd5cf7294114d77528_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. LPP Request Location Information + LMF->>UE: 1. LPP Request Location Information + Note left of UE: 2. LPP Provide Location Information + UE->>LMF: 2. LPP Provide Location Information +``` + +Sequence diagram showing the LMF-initiated Location Information Transfer Procedure. The diagram consists of two vertical lifelines labeled 'UE' and 'LMF'. Step 1 is a message from the LMF to the UE labeled '1. LPP Request Location Information'. Step 2 is a message from the UE to the LMF labeled '2. LPP Provide Location Information'. + +**Figure 8.3.3.3-1: LMF-initiated Location Information Transfer Procedure.** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of E-CID positioning. This request includes the E-CID measurements requested by the LMF and supported by the UE as listed in Table 8.3.2.4-1 together with a required response time. +- (2) The UE sends an LPP Provide Location Information message to the LMF and reports the requested measurements that are available in the UE before the Response Time provided in step (1) elapsed. If the requested measurements are not available, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +##### 8.3.3.3.2 UE-initiated Location Information Delivery procedure + +Figure 8.3.3.3.2-1 shows the Location Information Delivery procedure operations for the E-CID method when the procedure is initiated by the UE. + +![Sequence diagram showing the UE-initiated Location Information Delivery Procedure. A User Equipment (UE) box is on the left and a Location Management Function (LMF) box is on the right. A horizontal arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF. Vertical lines extend downwards from both boxes, representing their lifelines.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE-initiated Location Information Delivery Procedure + UE->>LMF: 1. LPP Provide Location Information +``` + +Sequence diagram showing the UE-initiated Location Information Delivery Procedure. A User Equipment (UE) box is on the left and a Location Management Function (LMF) box is on the right. A horizontal arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF. Vertical lines extend downwards from both boxes, representing their lifelines. + +**Figure 8.3.3.3.2-1: UE-initiated Location Information Delivery Procedure.** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE measurements already available at the UE. + +## 8.3.4 Uplink E-CID Positioning Procedures + +### 8.3.4.0 General + +The procedures described in this clause support E-CID related measurements obtained by the NG-RAN node and provided to the LMF using NRPPa. The term "uplink" is intended to indicate that from the LMF point of view, the involved measurements are provided by the NG-RAN node; this set of procedures might also be considered as "NG-RAN node-assisted E-CID". An example of this uplink E-CID positioning method for E-UTRA is AoA+TADV. + +### 8.3.4.1 Capability Transfer Procedure + +The Capability Transfer procedure is not applicable to uplink E-CID positioning not using E-UTRA TADV type 1. For uplink E-CID positioning using E-UTRA TADV type 1, the Capability Transfer procedure for E-CID positioning is described in clause 7.1.2.1. + +### 8.3.4.2 Assistance Data Transfer Procedure + +The assistance data transfer procedure is not applicable to uplink E-CID positioning. + +### 8.3.4.3 Position Measurement Procedure + +#### 8.3.4.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements from the NG-RAN node. + +#### 8.3.4.3.1 LMF-initiated Position Measurement + +Figure 8.3.4.3.1-1 shows the position measurement operations for the uplink E-CID method when the procedure is initiated by the LMF. + +![Diagram illustrating the LMF-initiated Position Measurement Procedure. It shows a black rectangular area representing the network. Inside, there are two white rectangular blocks. Below the main black area, a horizontal line with an arrow pointing left indicates a message flow from right to left, representing the LMF sending a request to the NG-RAN node.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +Diagram illustrating the LMF-initiated Position Measurement Procedure. It shows a black rectangular area representing the network. Inside, there are two white rectangular blocks. Below the main black area, a horizontal line with an arrow pointing left indicates a message flow from right to left, representing the LMF sending a request to the NG-RAN node. + +**Figure 8.3.4.3.1-1: LMF-initiated Position Measurement Procedure** + +- (1) The LMF sends a NRPPa E-CID MEASUREMENT INITIATION REQUEST message to the NG-RAN node. This request includes indication of E-CID measurements requested and whether the result is expected only once or periodically. +- (2) If the LMF in step (1) requested UE measurements (e.g., E-UTRA RSRP, E-UTRA RSRQ measurements, etc.), the NG-RAN node may configure the UE to report the measurement information requested as specified in TS 36.331 [13], TS 38.331 [14]. +- (3) If the result is expected only once and the NG-RAN node initiates at least one of the E-CID measurements as requested, the NG-RAN node sends an NRPPa E-CID MEASUREMENT INITIATION RESPONSE to the LMF, which includes the obtained E-CID measurements. If the result is expected periodically and the NG-RAN node is able to initiate at least one of the E-CID measurements as requested, the NG-RAN node sends an NRPPa E-CID MEASUREMENT INITIATION RESPONSE to the LMF, which does not include any result. The NG-RAN node reports then the obtained measurements by initiating the E-CID Measurement Report procedure, with the requested periodicity. If the NG-RAN node is unable to initiate any of the requested measurements as requested from the LMF, or is unable to instigate any of the required RRC procedures to obtain the requested measurements from the UE, the NG-RAN node sends an NRPPa E-CID MEASUREMENT INITIATION FAILURE message providing the error reason. If the failure occurs during a periodic reporting, the NG-RAN node sends an NRPPa E-CID MEASUREMENT FAILURE INDICATION message. + +## 8.4 Barometric pressure sensor positioning + +### 8.4.1 General + +In the barometric pressure sensor positioning method, the UE vertical component of the position is estimated by combining the measured atmospheric pressure and a reference atmospheric pressure. This is accomplished through barometric sensors measuring atmospheric pressure at the UE, and applying a height determination algorithm using the reference atmospheric pressure. + +Three positioning modes are supported: + +- *UE-Assisted*: The UE performs barometric pressure sensor measurements with or without assistance from the network and sends these measurements to the LMF where the vertical component of the position calculation may take place, possibly using additional measurements from other sources; +- *UE-Based*: The UE performs barometric pressure sensor measurements and calculates its own vertical component of the position, possibly using additional measurements from other sources. +- *Standalone*: The UE performs barometric pressure sensor measurements and calculates its own vertical component of the position, possibly using additional measurements from other sources, without network assistance. + +## 8.4.2 Information to be transferred between NG-RAN/5GC Elements + +### 8.4.2.0 General + +This clause defines the information that may be transferred between LMF and UE. + +### 8.4.2.1 Information that may be transferred from the LMF to UE + +#### 8.4.2.1.0 General + +Table 8.4.2.1.0-1 lists assistance data for both UE-assisted and UE-based modes that may be sent from the LMF to the UE. + +NOTE: The provision of these assistance data elements and the usage of these elements by the UE depend on the NG-RAN/5GC and UE capabilities, respectively. + +**Table 8.4.2.1.0-1: Information that may be transferred from the LMF to UE** + +| Assistance Data | +|---------------------------| +| Reference pressure | +| Additional reference data | + +#### 8.4.2.1.1 Barometric pressure sensor assistance data + +The barometric pressure sensor assistance data may include reference pressure, along with other reference data, such as the reference point where the reference barometric pressure is valid and reference temperature at the reference point. + +### 8.4.2.2 Information that may be transferred from the UE to LMF + +#### 8.4.2.2.0 General + +The information that may be signalled from the UE to the LMF is summarized in Table 8.4.2.2.0-1. + +**Table 8.4.2.2.0-1: Information that may be transferred from UE to the LMF** + +| Information | UE-assisted | UE-based/
Standalone | +|---------------------------------------------------|-------------|-------------------------| +| UE position estimate with uncertainty shape | No | Yes | +| Indication of used positioning methods in the fix | No | Yes | +| Timestamp | Yes | Yes | +| Barometric pressure sensor measurements | Yes | No | + +#### 8.4.2.2.1 Standalone mode + +In Standalone mode, the UE reports the vertical component of the position, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication of which positioning method(s) have been used to calculate a fix. + +#### 8.4.2.2.2 UE-assisted mode + +In UE-assisted mode, the UE reports the barometric pressure sensor measurements together with associated quality estimates. These measurements enable the LMF to calculate the vertical component of the location of the UE, possibly using other measurements and data. + +If requested by the LMF and supported by the UE, the UE may report barometric pressure sensor measurements together with associated quality measurements, if available. + +#### 8.4.2.2.3 UE-based mode + +In UE-based mode, the UE reports the vertical component of the position, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication of which positioning method(s) have been used to calculate a fix. + +### 8.4.3 Barometric Pressure Sensor Positioning Procedures + +#### 8.4.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for Barometric Pressure Sensor positioning is described in clause 7.1.2.1. + +#### 8.4.3.2 Assistance Data Transfer Procedure + +##### 8.4.3.2.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). + +##### 8.4.3.2.1 LMF initiated Assistance Data Delivery + +Figure 8.4.3.2.1-1 shows the Assistance Data Delivery operations for the network-assisted barometric pressure sensor method when the procedure is initiated by the LMF. + +![Sequence diagram showing LMF-initiated Assistance Data Delivery. A box labeled 'UE' is on the left and a box labeled 'LMF' is on the right. A horizontal arrow points from the LMF to the UE, labeled '1. LPP Provide Assistance Data'. Vertical lines extend downwards from both boxes, representing lifelines.](4304a81342b40a72da20f26eb2cb2aa0_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE + Note right of LMF: LMF + LMF->>UE: 1. LPP Provide Assistance Data +``` + +Sequence diagram showing LMF-initiated Assistance Data Delivery. A box labeled 'UE' is on the left and a box labeled 'LMF' is on the right. A horizontal arrow points from the LMF to the UE, labeled '1. LPP Provide Assistance Data'. Vertical lines extend downwards from both boxes, representing lifelines. + +**Figure 8.4.3.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the barometric pressure sensor assistance data defined in clause 8.4.2.1. + +##### 8.4.3.2.2 UE initiated Assistance Data Transfer + +Figure 8.4.3.2.2-1 shows the Assistance Data Transfer operations for the network-assisted Barometric pressure sensor method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE determines assistance data is desired + UE->>LMF: 1. LPP Request Assistance Data + Note right of LMF: LMF provides requested data + LMF-->>UE: 2. LPP Provide Assistance Data +``` + +The diagram illustrates the UE-initiated Assistance Data Transfer Procedure. It features two vertical lifelines for the User Equipment (UE) and the Location Management Function (LMF). Step 1 shows a solid arrow pointing from the UE to the LMF, labeled '1. LPP Request Assistance Data'. Step 2 shows a solid arrow pointing from the LMF back to the UE, labeled '2. LPP Provide Assistance Data'. + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure + +**Figure 8.4.3.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain barometric pressure sensor assistance data is desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific barometric pressure sensor assistance data is requested. +- (2) The LMF provides the requested assistance data in a LPP Provide Assistance Data message, if available at the LMF. The entire set of assistance data may be delivered in one or several LPP messages. In this case, this step may be repeated by the LMF several times. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +#### 8.4.3.3 Location Information Transfer Procedure + +##### 8.4.3.3.0 General + +The purpose of this procedure is to enable the LMF to request barometric pressure sensor measurements or position estimate from the UE, or to enable the UE to provide barometric pressure sensor measurements to the LMF for position calculation. + +##### 8.4.3.3.1 LMF initiated Location Information Transfer Procedure + +Figure 8.4.3.3.1-1 shows the Location Information Transfer operations when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure](6d442ab678ed52045444b3ccd4c0ac9e_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: LMF sends request for positioning + LMF-->>UE: 1. LPP Request Location Information + Note left of UE: UE performs measurements and calculates position + UE->>LMF: 2. LPP Provide Location Information +``` + +The diagram illustrates the LMF-initiated Location Information Transfer Procedure. It features two vertical lifelines for the User Equipment (UE) and the Location Management Function (LMF). Step 1 shows a solid arrow pointing from the LMF to the UE, labeled '1. LPP Request Location Information'. Step 2 shows a solid arrow pointing from the UE to the LMF, labeled '2. LPP Provide Location Information'. + +Sequence diagram for LMF-initiated Location Information Transfer Procedure + +**Figure 8.4.3.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of barometric pressure sensor positioning. This request includes positioning instructions such as the positioning mode (UE-assisted, UE-based, standalone), specific requested UE measurements if any, and quality of service parameters (accuracy, response time). +- (2) The UE performs the requested measurements and possibly calculates its own position. The UE sends an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. If the + +UE is unable to perform the requested measurements, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.4.3.3.2 UE-initiated Location Information Delivery Procedure + +Figure 8.4.3.3.2-1 shows the Location Information delivery operations for the barometric pressure sensor method when the procedure is initiated by the UE. + +![Sequence diagram showing the UE-initiated Location Information Delivery Procedure. The UE sends an LPP Provide Location Information message to the LMF.](7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE-initiated Location Information Delivery Procedure + UE->>LMF: 1. LPP Provide Location Information + +``` + +Sequence diagram showing the UE-initiated Location Information Delivery Procedure. The UE sends an LPP Provide Location Information message to the LMF. + +**Figure 8.4.3.3.2-1: UE-initiated Location Information Delivery Procedure** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include UE barometric pressure sensor measurements or location estimate already available at the UE. + +## 8.5 WLAN positioning + +### 8.5.1 General + +In the WLAN positioning method, the UE position is estimated with the knowledge of geographical coordinate of reference WLAN access points. This is accomplished by collecting a certain amount of measurements from UE's WLAN receivers, and applying a location determination algorithm using databases of the estimated position's references points. + +The UE WLAN measurements may include: + +- WLAN Received Signal Strength (RSSI); +- Round Trip Time (RTT) between WLAN Access Point and the UE. + +Three positioning modes are supported: + +- *Standalone:* +The UE performs WLAN position measurements and location computation, without network assistance. +- *UE-assisted:* +The UE provides WLAN position measurements with or without assistance from the network to the LMF for computation of a location estimate by the network. +- *UE-based:* +The UE performs WLAN position measurements and computation of a location estimate with network assistance. + +## 8.5.2 Information to be transferred between NG-RAN/5GC Elements + +### 8.5.2.0 General + +This clause defines the information that may be transferred between LMF and UE. + +### 8.5.2.1 Information that may be transferred from the LMF to UE + +#### 8.5.2.1.0 General + +Table 8.5.2.1.0-1 lists assistance data for both UE-assisted and UE-based modes that may be sent from the LMF to the UE. + +NOTE: The provision of these assistance data elements and the usage of these elements by the UE depend on the NG-RAN/5GC and UE capabilities, respectively. + +**Table 8.5.2.1.0-1: Information that may be transferred from the LMF to UE** + +| Assistance Data | +|--------------------------------------------------------------------------------------------------------------------------------------| +| WLAN AP List | +| BSSID | +| SSID | +| AP Type Data (1) | +| AP Location | +| NOTE 1: WLAN AP Type Data may include WLAN Type (e.g., 802.11a/b/g/n/ac/ad, etc.), transmit power, antenna gain, coverage area, etc. | + +#### 8.5.2.1.1 WLAN AP BSSID + +This assistance data provides the BSSID of the WLAN access point [21]. + +#### 8.5.2.1.2 WLAN AP SSID + +This assistance data provides the SSID of the WLAN access point [21]. + +#### 8.5.2.1.3 WLAN AP Type Data + +This assistance data provides additional information about the access point and may include WLAN Type (e.g., 802.11a/b/g/n/ac/ad, etc.), transmit power, antenna gain, coverage area, etc. [21] + +#### 8.5.2.1.4 WLAN AP Location + +This assistance data provides the location (possibly including altitude information) of the access point [21]. + +### 8.5.2.2 Information that may be transferred from the UE to LMF + +#### 8.5.2.2.0 General + +The information that may be signalled from the UE to the LMF is summarized in Table 8.5.2.2.0-1. + +**Table 8.5.2.2.0-1: Information that may be transferred from the UE to the LMF** + +| Information | UE-Assisted | UE-based/
Standalone | +|------------------------------------------------------|-------------|-------------------------| +| WLAN Location Information | | | +| BSSID | Yes | No | +| SSID | Yes | No | +| Received Signal Strength (RSSI) | Yes | No | +| Round Trip Time (RTT) | Yes | No | +| Time Stamp | Yes | No | +| Measurement characteristics | Yes | No | +| UE Location Information | | | +| UE position estimate with uncertainty shape | No | Yes | +| Position Time Stamp | No | Yes | +| Location Source (method(s) used to compute location) | No | Yes | + +#### 8.5.2.2.1 Standalone mode + +In Standalone mode, the UE reports the latitude, longitude and possibly altitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication of WLAN method and possibly other positioning methods used to calculate a fix. + +#### 8.5.2.2.2 UE-assisted mode + +In UE-assisted mode, the UE should report: + +- The BSSID/SSID of the measured WLAN access points, and associated RSSI or RTT. + +#### 8.5.2.2.3 UE-based mode + +In UE-based mode, the UE reports the latitude, longitude, and possibly altitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication that WLAN method is used and possibly other positioning methods used to calculate the fix. + +### 8.5.3 WLAN Positioning Procedures + +#### 8.5.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for WLAN positioning is described in clause 7.1.2.1. + +#### 8.5.3.2 Assistance Data Transfer Procedure + +##### 8.5.3.2.0 General + +The purpose of this procedure is to enable the UE to request assistance data from the LMF (e.g., as part of a positioning procedure) and the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure). + +##### 8.5.3.2.1 LMF initiated Assistance Data Delivery + +Figure 8.5.3.2.1-1 shows the Assistance Data Delivery operations for the network-assisted WLAN method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Assistance Data Delivery Procedure](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +A sequence diagram showing the interaction between a User Equipment (UE) and a Location Management Function (LMF). The UE is on the left and the LMF is on the right. A single message arrow points from the LMF to the UE, labeled '1. LPP Provide Assistance Data'. + +Sequence diagram for LMF-initiated Assistance Data Delivery Procedure + +**Figure 8.5.3.2.1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the WLAN assistance data defined in clause 8.5.2.1. + +#### 8.5.3.2.2 UE initiated Assistance Data Transfer + +Figure 8.5.3.2.2-1 shows the Assistance Data Transfer operations for the network-assisted WLAN method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure](025f85981c69ed3274f1aa6c4844266e_img.jpg) + +A sequence diagram showing the interaction between a User Equipment (UE) and a Location Management Function (LMF). The UE is on the left and the LMF is on the right. Two message arrows are shown: the first points from the UE to the LMF and is labeled '1. LPP Request Assistance Data'; the second points from the LMF to the UE and is labeled '2. LPP Provide Assistance Data'. + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure + +**Figure 8.5.3.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain WLAN assistance data is desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific WLAN assistance data is requested. +- (2) The LMF provides the requested assistance data in a LPP Provide Assistance Data message, if available at the LMF. The entire set of assistance data may be delivered in one or several LPP messages. In this case, this step may be repeated by the LMF several times. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +#### 8.5.3.3 Location Information Transfer Procedure + +##### 8.5.3.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements or location estimate from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +### 8.5.3.3.1 LMF initiated Location Information Transfer Procedure + +Figure 8.5.3.3.1-1 shows the Location Information Transfer operations for the WLAN method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure](9bafc60bf378685e5e246c3ffad7b792_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + LMF->>UE: 1. LPP Request Location Information + Note right of LMF: + UE-->>LMF: 2. LPP Provide Location Information + Note right of UE: +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Location Management Function (LMF). The LMF sends a message labeled '1. LPP Request Location Information' to the UE. The UE then responds with a message labeled '2. LPP Provide Location Information' to the LMF. + +Sequence diagram for LMF-initiated Location Information Transfer Procedure + +**Figure 8.5.3.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of WLAN positioning. This request includes positioning instructions such as the positioning mode (UE-assisted, UE-based, Standalone), specific requested UE measurements if any, and quality of service parameters (accuracy, response time). +- (2) The UE performs the requested measurements and possibly calculates its own location. The UE sends an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. If the UE is unable to perform the requested measurements, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +### 8.5.3.3.2 UE-initiated Location Information Delivery Procedure + +Figure 8.5.3.3.2-1 shows the Location Information delivery operations for the WLAN method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Location Information Delivery Procedure](e451a51157214e53bd9c64db914771cc_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + UE-->>LMF: 1. LPP Provide Location Information + Note right of LMF: +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Location Management Function (LMF). The UE sends a message labeled '1. LPP Provide Location Information' to the LMF. + +Sequence diagram for UE-initiated Location Information Delivery Procedure + +**Figure 8.5.3.3.2-1: UE-initiated Location Information Delivery Procedure** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include UE WLAN information or location estimate already available at the UE. + +## 8.6 Bluetooth positioning + +### 8.6.1 General + +In the Bluetooth positioning method, the UE position is estimated with the knowledge of geographical coordinate of reference Bluetooth beacons. This is accomplished by collecting a certain amount of measurements from UE's + +Bluetooth receiver and/or from the receiver of the Bluetooth beacons, and applying a location determination algorithm using databases of the estimated position's references points, reference points antenna configuration and orientation. + +The UE Bluetooth measurements may include: + +- Bluetooth beacon's Received Signal Strength (RSSI). +- Bluetooth beacon's estimated AoD (azimuth and zenith angles). + +The Bluetooth beacon measurements may include: + +- Bluetooth beacon's estimated AoA (azimuth and zenith angles). + +Three positioning modes are supported: + +- *Standalone:* +The UE performs Bluetooth position measurements and location computation. +- *UE-assisted:* +The UE provides Bluetooth position measurements with or without assistance from the network to the LMF for computation of a location estimate by the network. +- *UE-based:* +The UE performs Bluetooth position measurements and computation of a location estimate with network assistance. + +## 8.6.2 Information to be transferred between NG-RAN/5GC Elements + +This clause defines the information that may be transferred between LMF and UE. + +### 8.6.2.1 Information that may be transferred from the LMF to UE + +#### 8.6.2.1.0 General + +Table 8.6.2.1.0-1 lists Bluetooth transmission parameters that LMF may suggest to the UE to consider for UE-assisted Bluetooth AoA positioning. LMF may instead only request to the UE to provide its Bluetooth transmission parameters used for UE-assisted Bluetooth AoA positioning. + +NOTE 1: The provision of these elements and the usage of these elements by the UE depend on the NG-RAN/5GC and UE capabilities, respectively. + +**Table 8.6.2.1.0-1: Suggested UE Bluetooth AoA transmission parameters that may be transferred from LMF to the UE** + +| Information | +|-------------------------------------------------------------------------------------------------------| +| Transmission configuration (advertising periodicities, PHY type, TX power, CTE length and repetition) | + +The AoA transmission configuration is described in more detail in 8.6.2.2. + +Table 8.6.2.1.0-2 lists assistance data for both UE-assisted and UE-based modes that may be sent from the LMF to the UE to support Bluetooth AoD positioning. + +NOTE 2: The provision of these assistance data elements and the usage of these elements by the UE depend on the NG-RAN/5GC and UE capabilities, respectively. + +**Table 8.6.2.1.0-2: Assistance data that may be transferred from LMF to the UE** + +| Information | UE-assisted | UE-based | +|--------------------------------------------------------------------------------------------------------|-------------|----------| +| Bluetooth beacon list: | | | +| Bluetooth advertising address | Yes | Yes | +| Geographical coordinate | Yes | Yes | +| Antenna array orientation (LCS to GCS translation) | Yes | Yes | +| Antenna array configuration (antenna relative location and polarization) and antenna switching pattern | Yes | Yes | +| Transmission configuration (advertising periodicities, PHY type, CTE type, length and repetition) | Yes | Yes | + +#### 8.6.2.1.1 Bluetooth beacon advertising address + +This assistance data provides the Bluetooth advertising address btAddr of the Bluetooth beacon [51]. + +#### 8.6.2.1.2 Bluetooth beacon location + +This assistance data provides the location of the Bluetooth beacon [51]. + +#### 8.6.2.1.3 Bluetooth beacon antenna array orientation + +This assistance data provides the Bluetooth antenna array orientation of the Bluetooth beacon by parameters bearing, downtilt and slant for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS). + +#### 8.6.2.1.4 Bluetooth beacon antenna array configuration and switching pattern + +This assistance data provides the Bluetooth antenna array configuration of the Bluetooth beacon, where each the antenna of the array is characterized by a relative position to an antenna array reference point and a polarization, and the antenna switching pattern lists the order antennas are used for transmissions [51]. One generic antenna array and three parameterized antenna arrays can be defined (linear, rectangular or circular). + +#### 8.6.2.1.5 Bluetooth beacon AoD transmission configuration + +This assistance data provides the Bluetooth beacon AoD transmission configuration parameters for the primary and secondary advertising periodicities, Bluetooth PHY type (1 or 2 Msymbol/s), CTE type (1 us or 2 us switching slot lengths), CTE length (8 to 160 us) and CTE repeated transmission instants (1 - 16). + +### 8.6.2.2 Information that may be transferred from the UE to LMF + +#### 8.6.2.2.0 General + +The information that may be signalled from the UE to the LMF is summarized in Table 8.6.2.2.0-1. + +**Table 8.6.2.2.0-1: Information that may be transferred from the UE to the LMF** + +| Information | UE-Assisted | Standalone | +|-------------------------------------------------------|-------------|------------| +| Bluetooth Location Information | | | +| MAC Address | Yes | No | +| Received Signal Strength (RSSI) | Yes | No | +| Time Stamp | Yes | No | +| Measurement characteristics | Yes | No | +| AoD angles (azimuth and zenith) | Yes | No | +| UE Location Information | | | +| UE position estimate with uncertainty shape | No | Yes | +| Position Time Stamp | No | Yes | +| Location Source (method(s) used to compute location) | No | Yes | +| UE AoA transmission configuration | | | +| Address and address type | Yes | No | +| Primary and secondary channel advertising periodicity | Yes | No | +| Primary and secondary advertising periodicity | Yes | No | +| TX Power | Yes | No | +| CTE transmission configuration | Yes | No | + +Bluetooth AoA positioning is enabled by the UE transmitting Bluetooth periodic advertising with a CTE, configured by the following parameters: + +- UE advertisement address that can be of three different types - public (MAC address), random-static (static random number) or random-private-resolvable (regularly updated random number); +- primary channel advertising periodicity, related to the Bluetooth beacon acquisition time of the UE Bluetooth signal; +- periodic advertising interval on the secondary advertising channel, related to how often the Bluetooth beacons will be able to estimate AoA of the UE; +- TX power related to how strong the UE Bluetooth signal is received at the Bluetooth beacons; +- CTE length (16 – 160 us) of every CTE transmission; +- CTE repeated transmissions instants (1-16) each transmission instant. + +#### 8.6.2.2.1 Standalone mode + +In Standalone mode, the UE reports the latitude, longitude and possibly altitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication of Bluetooth method and possibly other location methods have been used to calculate a fix. + +#### 8.6.2.2.2 UE-assisted mode + +In UE-assisted mode, the UE should either report: + +- The MAC addresses of the measured Bluetooth beacons and one or more of: + - associated RSSI; + - associated AoD, assisted by the positioning server. + +or transmit: + +- periodic advertisements with CTE to enable Bluetooth beacon AoA estimation. + +### 8.6.2.2.3 UE-based mode + +In UE-based mode using Bluetooth AoD, the UE reports the estimated location coordinates together with an estimate of the location uncertainty, if available. + +The UE should also report an indication that Bluetooth method is used and possibly other positioning methods used to calculate the fix. + +## 8.6.3 Bluetooth Positioning Procedures + +### 8.6.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for Bluetooth positioning is described in clause 7.1.2.1. + +### 8.6.3.2 Assistance Data Transfer Procedure + +#### 8.6.3.2.0 General + +The purpose of this procedure is to enable the UE to request Bluetooth AoD assistance data from the LMF (e.g., as part of a positioning procedure) and the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure). + +#### 8.6.3.2.1 LMF initiated Assistance Data Delivery + +Figure 8.6.3.2.1-1 shows the Assistance Data Delivery operations for the network-assisted Bluetooth AoD method when the procedure is initiated by the LMF. + +![Sequence diagram showing LMF-initiated Assistance Data Delivery. The LMF sends an LPP Provide Assistance Data message to the UE.](2bea721b89ee5816651ed9cdc328bc9f_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. LPP Provide Assistance Data + LMF->>UE: 1. LPP Provide Assistance Data +``` + +Sequence diagram showing LMF-initiated Assistance Data Delivery. The LMF sends an LPP Provide Assistance Data message to the UE. + +**Figure 8.6.3.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the Bluetooth assistance data defined in clause 8.6.2.1. + +#### 8.6.3.2.2 UE initiated Assistance Data Transfer + +Figure 8.6.3.2.2-1 shows the Assistance Data Transfer operations for the network-assisted Bluetooth AoD method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure. The UE sends a '1. LPP Request Assistance Data' message to the LMF, and the LMF responds with a '2. LPP Provide Assistance Data' message.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE determines assistance data is desired + UE->>LMF: 1. LPP Request Assistance Data + LMF-->>UE: 2. LPP Provide Assistance Data + +``` + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure. The UE sends a '1. LPP Request Assistance Data' message to the LMF, and the LMF responds with a '2. LPP Provide Assistance Data' message. + +**Figure 8.6.3.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain Bluetooth assistance data is desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific Bluetooth assistance data is requested. +- (2) The LMF provides the requested assistance data in a LPP Provide Assistance Data message, if available at the LMF. The entire set of assistance data may be delivered in one or several LPP messages. In this case, this step may be repeated by the LMF several times. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +### 8.6.3.3 Location Information Transfer Procedure + +#### 8.6.3.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements or location estimate from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +The purpose can also be to enable LMF to request or suggest UE Bluetooth AoA configuration and enable the UE to provide the Bluetooth AoA configuration it will use to enable Bluetooth beacons to provide AoA measurements to LMF. + +#### 8.6.3.3.1 LMF initiated Location Information Transfer Procedure + +Figure 8.6.3.3.1-1 shows the Location Information Transfer operations for the Bluetooth method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure. The LMF sends a '1. LPP Request Location Information' message to the UE, and the UE responds with a '2. LPP Provide Location Information' message.](d53421c44b83ef2ffc1fa09fbebc609f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LMF + LMF->>UE: 1. LPP Request Location Information + UE-->>LMF: 2. LPP Provide Location Information + +``` + +Sequence diagram for LMF-initiated Location Information Transfer Procedure. The LMF sends a '1. LPP Request Location Information' message to the UE, and the UE responds with a '2. LPP Provide Location Information' message. + +**Figure 8.6.3.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of Bluetooth positioning. This request includes positioning instructions such as the positioning mode (UE-assisted, Standalone), specific requested UE measurements if any, quality of service parameters (accuracy, response time), request/suggestion of UE Bluetooth AoA transmission configuration. + +- (2) The UE performs the requested measurements and possibly calculates its own location. The UE sends an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. If the UE is unable to perform the requested measurements, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +Alternatively, for AoA, the UE provides Bluetooth AoA transmission configuration that it will use in an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. + +#### 8.6.3.3.2 UE-initiated Location Information Delivery Procedure + +Figure 8.6.3.3.2-1 shows the Location Information delivery operations for the Bluetooth method when the procedure is initiated by the UE. + +![Sequence diagram showing the UE-initiated Location Information Delivery Procedure. A UE box is on the left and an LMF box is on the right. A horizontal arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF. Vertical lines extend downwards from both boxes.](521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE-initiated Location Information Delivery Procedure + UE->>LMF: 1. LPP Provide Location Information +``` + +Sequence diagram showing the UE-initiated Location Information Delivery Procedure. A UE box is on the left and an LMF box is on the right. A horizontal arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF. Vertical lines extend downwards from both boxes. + +**Figure 8.6.3.3.2-1: UE-initiated Location Information Delivery Procedure** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include UE Bluetooth information or location estimate already available at the UE. For AoA, the UE provides Bluetooth AoA transmission configuration in a Provide Location Information message that it will use. Specifically, the UE will trigger such a message when it has changed Bluetooth advertising address – only applicable for the random-private-resolvable address type. + +## 8.7 TBS positioning + +### 8.7.1 General + +Terrestrial Beacon Systems (TBS) is the standard generic term for a network of ground-based transmitters broadcasting signals for geo-spatial positioning with wide-area or regional coverage. The following TBSs are supported in this version of the specification: + +- Metropolitan Beacon Systems (MBS). + +NOTE: PRS-based TBS is part of downlink OTDOA positioning and described in clause 8.2. + +Three positioning modes are supported: + +- *UE-Assisted*: The UE performs TBS measurements with or without assistance from the network, and sends these measurements to the LMF where the position calculation takes place, possibly using additional measurements from other (non-TBS) sources; +- *UE-Based*: The UE performs TBS measurements and calculates its own location, possibly using additional measurements from other (non-TBS) sources. +- *Standalone*: The UE performs TBS measurements and calculates its own location, possibly using additional measurements from other (non-TBS) sources, without network assistance. + +## 8.7.2 Information to be transferred between NG-RAN/5GC Elements + +### 8.7.2.0 General + +This clause defines the information that may be transferred between LMF and UE. + +### 8.7.2.1 Information that may be transferred from the LMF to UE + +#### 8.7.2.1.0 General + +Table 8.7.2.1.0-1 lists assistance data for both UE-assisted and UE-based modes that may be sent from the LMF to the UE. + +NOTE: The provision of these assistance data elements and the usage of these elements by the UE depend on the NG-RAN/5GC and UE capabilities, respectively. + +**Table 8.7.2.1.0-1: Information that may be transferred from the LMF to UE** + +| Assistance Data | +|------------------------| +| Acquisition assistance | +| Almanac | + +#### 8.7.2.1.1 Acquisition Assistance + +Acquisition assistance provides the MBS receiver with information about visible beacons, PN Codes, and other information of the MBS signals to enable a fast acquisition of the MBS signals. + +#### 8.7.2.1.2 Almanac + +Almanac assistance provides the MBS receiver with MBS beacon parameters that can be used to determine the UE position. + +### 8.7.2.2 Information that may be transferred from the UE to LMF + +#### 8.7.2.2.0 General + +The information that may be signalled from the UE to the LMF is summarized in Table 8.7.2.2.0-1. + +**Table 8.7.2.2.0-1: Information that may be transferred from UE to the LMF** + +| Information | UE-assisted | UE-based/
Standalone | +|-----------------------------------------------------|-------------|-------------------------| +| UE position estimate with uncertainty shape | No | Yes | +| Timestamp | Yes | Yes | +| Indication of used positioning methods in the fix | No | Yes | +| TBS measurements (code phase (MBS)) | Yes | No | +| Measurement quality parameters for each measurement | Yes | No | + +#### 8.7.2.2.1 Standalone mode + +In Standalone mode, the UE reports the latitude, longitude and possibly altitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication that TBS method is used and possibly other positioning methods used to calculate the fix. + +#### 8.7.2.2.2 UE-assisted mode + +In UE-assisted mode, the UE reports the TBS associated measurements, together with associated quality estimates. These measurements enable the LMF to calculate the location of the UE, possibly using other measurements and data. + +#### 8.7.2.2.3 UE-based mode + +In UE-based mode, the UE reports the latitude and longitude, together with an estimate of the location uncertainty, if available. + +The UE should also report an indication that TBS method is used and possibly other positioning methods used to calculate the fix. + +### 8.7.3 TBS Positioning Procedures + +#### 8.7.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for TBS positioning is described in clause 7.1.2.1. + +#### 8.7.3.2 Assistance Data Transfer Procedure + +##### 8.7.3.2.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). + +##### 8.7.3.2.1 LMF initiated Assistance Data Delivery + +Figure 8.7.3.2.1-1 shows the Assistance Data Delivery operations for the network-assisted TBS method when the procedure is initiated by the LMF. + +![Sequence diagram showing LMF-initiated Assistance Data Delivery Procedure. The diagram consists of two vertical lifelines labeled 'UE' and 'LMF'. A horizontal arrow points from the LMF lifeline to the UE lifeline, labeled '1. LPP Provide Assistance Data'.](2fe54eab8d7668ad3b9e56219accbaca_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE + Note right of LMF: LMF + LMF->>UE: 1. LPP Provide Assistance Data +``` + +Sequence diagram showing LMF-initiated Assistance Data Delivery Procedure. The diagram consists of two vertical lifelines labeled 'UE' and 'LMF'. A horizontal arrow points from the LMF lifeline to the UE lifeline, labeled '1. LPP Provide Assistance Data'. + +**Figure 8.7.3.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the TBS assistance data defined in clause 8.7.2.1. + +##### 8.7.3.2.2 UE initiated Assistance Data Transfer + +Figure 8.7.3.2.2-1 shows the Assistance Data Transfer operations for the network-assisted TBS method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE determines assistance data is desired + UE->>LMF: 1. LPP Request Assistance Data + Note right of LMF: LMF provides assistance data + LMF-->>UE: 2. LPP Provide Assistance Data +``` + +The diagram illustrates the UE-initiated Assistance Data Transfer Procedure. It features two vertical lifelines for the User Equipment (UE) and the Location Management Function (LMF). Step 1 shows a solid arrow pointing from the UE to the LMF, labeled '1. LPP Request Assistance Data'. Step 2 shows a solid arrow pointing from the LMF back to the UE, labeled '2. LPP Provide Assistance Data'. + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure + +**Figure 8.7.3.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain TBS assistance data is desired (e.g., when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific TBS assistance data is requested. +- (2) The LMF provides the requested assistance data in a LPP Provide Assistance Data message, if available at the LMF. The entire set of assistance data may be delivered in one or several LPP messages. In this case, this step may be repeated by the LMF several times. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +### 8.7.3.3 Location Information Transfer Procedure + +#### 8.7.3.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements or location estimate from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +#### 8.7.3.3.1 LMF initiated Location Information Transfer Procedure + +Figure 8.7.3.3.1-1 shows the Location Information Transfer operations for the TBS method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure](cde3789e303efe653250b497e839e243_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: LMF sends request for TBS positioning + LMF->>UE: 1. LPP Request Location Information + Note left of UE: UE performs measurements + UE-->>LMF: 2. LPP Provide Location Information +``` + +The diagram illustrates the LMF-initiated Location Information Transfer Procedure. It features two vertical lifelines for the User Equipment (UE) and the Location Management Function (LMF). Step 1 shows a solid arrow pointing from the LMF to the UE, labeled '1. LPP Request Location Information'. Step 2 shows a solid arrow pointing from the UE back to the LMF, labeled '2. LPP Provide Location Information'. + +Sequence diagram for LMF-initiated Location Information Transfer Procedure + +**Figure 8.7.3.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of TBS positioning. This request includes positioning instructions such as the positioning mode (UE-assisted, UE-based, Standalone), specific requested UE measurements if any, and quality of service parameters (accuracy, response time). +- (2) The UE performs the requested measurements and possibly calculates its own location. The UE sends an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. If the UE is unable to perform the requested measurements, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in + +an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +### 8.7.3.3.2 UE-initiated Location Information Delivery Procedure + +Figure 8.7.3.3.2-1 shows the Location Information delivery operations for the TBS method when the procedure is initiated by the UE. + +![Sequence diagram showing the UE-initiated Location Information Delivery Procedure. The UE sends an LPP Provide Location Information message to the LMF.](427095219f3706148e8c03f1013eaec8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE-initiated Location Information Delivery Procedure + UE->>LMF: 1. LPP Provide Location Information + +``` + +Sequence diagram showing the UE-initiated Location Information Delivery Procedure. The UE sends an LPP Provide Location Information message to the LMF. + +**Figure 8.7.3.3.2-1: UE-initiated Location Information Delivery Procedure** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include UE TBS measurements or location estimate already available at the UE. + +## 8.8 Motion sensor positioning method + +### 8.8.1 General + +Motion sensors can be used to estimate the location of the UE. With the combination of other positioning methods (hybrid) a more accurate position of the UE can be computed. UE using one or more motion sensors provides the movement information. The movement information comprises displacement results estimated as an ordered series of points. + +The positioning modes supported are UE-Assisted, UE-Based, and Standalone. + +### 8.8.2 Information to be transferred between NG-RAN/5GC Elements + +#### 8.8.2.1 General + +This clause defines the information (e.g., assistance data, position and/or measurement data) that may be transferred between NG-RAN/5GC elements. + +#### 8.8.2.2 Information that may be transferred from the UE to LMF + +##### 8.8.2.2.0 General + +The information transferred from the UE to the LMF consists of capability information and location measurements or UE position. The supported information elements are given in Table 8.8.2.2.0-1. + +**Table 8.8.2.2.0-1: Sensor Measurement Information that may be transferred from UE to the LMF** + +| Information | UE-assisted | UE-based/
Standalone | +|--------------------------|-------------|-------------------------| +| Displacement Timestamp | Yes | Yes | +| Displacement Information | Yes | Yes | +| Reference Position | Yes | Yes | +| Reference Time | Yes | Yes | + +#### 8.8.2.2.1 UE-assisted, UE-based, Standalone mode + +In the UE-assisted, UE-Based, and Standalone mode, the UE reports, displacement information, displacement timestamp, reference position and reference time. + +#### 8.8.2.2.2 UE Displacement and Movement Information + +The UE may report movement and displacement information which comprises an ordered series of direction, distance travelled by the target device and the time intervals when these measurements are taken. + +#### 8.8.2.3 Information that may be transferred from the LMF to the UE + +In this release, no information, e.g. assistance data is transferred to the UE. + +### 8.8.3 Motion Sensors Location Information Transfer Procedure + +#### 8.8.3.1 General + +The purpose of this procedure is to enable the LMF to request additional sensor measurements or to enable the UE to provide sensor measurements to the LMF for position calculation. + +#### 8.8.3.2 LMF initiated Location Information Transfer Procedure + +Figure 8.8.3.2-1 shows the Location Information Transfer operations when the procedure is initiated by the LMF. + +![Sequence diagram of LMF-initiated Location Information Transfer Procedure](fe4f9338148fd891afbd3e301f9bad33_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. LPP Request Location Information + LMF->>UE: + Note left of UE: 2. LPP Provide Location Information + UE->>LMF: +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Location Management Function (LMF). It consists of two vertical lifelines. The first step is a message from the LMF to the UE, labeled '1. LPP Request Location Information'. The second step is a message from the UE to the LMF, labeled '2. LPP Provide Location Information'. + +Sequence diagram of LMF-initiated Location Information Transfer Procedure + +**Figure 8.8.3.2-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of motion sensor positioning. This request includes positioning instructions such as the positioning mode, specific requested UE measurements if any, and quality of service parameters (accuracy, response time). +- (2) The UE performs the requested measurements. The UE sends an LPP Provide Location Information message to the LMF before the Response Time provided in step (1) elapsed. If the UE is unable to perform the requested measurements, or if the Response Time provided in step 1 elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.8.3.3 UE-initiated Location Information Delivery Procedure + +Figure 8.8.3.3-1 shows the Location Information delivery operations for motion sensor method when the procedure is initiated by the UE. + +![Diagram of UE-initiated Location Information Delivery Procedure. A UE box is on the left and an LMF box is on the right. A horizontal arrow points from the UE to the LMF, labeled '1. LPP Provide Location Information'. Vertical lines extend downwards from both the UE and LMF boxes.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +``` + +graph LR + UE[UE] -- "1. LPP Provide Location Information" --> LMF[LMF] + +``` + +Diagram of UE-initiated Location Information Delivery Procedure. A UE box is on the left and an LMF box is on the right. A horizontal arrow points from the UE to the LMF, labeled '1. LPP Provide Location Information'. Vertical lines extend downwards from both the UE and LMF boxes. + +**Figure 8.8.3.3-1: UE-initiated Location Information Delivery Procedure** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include UE sensor measurements or location estimate already available at the UE. + +## 8.9 NR Enhanced cell ID positioning methods + +### 8.9.1 General + +NR Enhanced Cell ID (NR E-CID) positioning refers to techniques which use UE and/or NR radio resource related measurements to improve the UE location estimate. In the case of uplink NR E-CID inter-RAT E-UTRA measurements reported by UE may also be used. + +- NOTE 1: For NR E-CID positioning methods the UE reports only the measurements that it has available rather than being required to take additional measurement actions. Therefore, the measurement gap request procedure described in clause 7.4.1.1 is not applicable for NR E-CID positioning methods. + +NR E-CID measurements may include: + +UE measurements (TS 38.215 [37]): + +- SS Reference signal received power (SS-RSRP); +- SS Reference Signal Received Quality (SS-RSRQ); +- CSI Reference signal received power (CSI-RSRP); +- CSI Reference Signal Received Quality (CSI-RSRQ). + +The UE measurements above may be aggregated at cell level or measured per SSB or CSI-RS resource. + +NR E-CID UE measurements for other RAT may include: + +- E-UTRA Reference signal received power (RSRP); +- E-UTRA Reference Signal Received Quality (RSRQ); + +- NOTE 2: The above E-UTRA measurements by UE are only used for Uplink NR E-CID positioning. + +gNB measurements (TS 38.215 [37]): + +- UL Angle of Arrival (azimuth and elevation); +- Timing advance ( $T_{ADV}$ ). + +Various techniques exist to use these measurements to estimate the location of the UE. The specific techniques are beyond the scope of this specification. + +### 8.9.2 Information to be transferred between NG-RAN/5GC Elements + +#### 8.9.2.0 General + +This clause defines the information that may be transferred between LMF and UE and from gNB to LMF. + +### 8.9.2.1 Information that may be transferred from the LMF to UE + +UE-assisted NR Enhanced Cell-ID location does not require any assistance data to be transferred from the LMF to the UE. + +UE-Based NR Enhanced Cell-ID location is not supported in this version of the specification. + +### 8.9.2.2 Information that may be transferred from the UE to LMF + +The information that may be signalled from UE to the LMF is listed in table 8.9.2.2-1. + +**Table 8.9.2.2-1: Information that may be transferred from UE to the LMF** + +| Information | UE-assisted | +|--------------------------------------------------|-------------| +| SS Reference signal received power (SS-RSRP) | Yes | +| SS Reference Signal Received Quality (SS-RSRQ) | Yes | +| CSI Reference signal received power (CSI-RSRP) | Yes | +| CSI Reference Signal Received Quality (CSI-RSRQ) | Yes | +| NR Cell Global Identifier, Physical Cell ID | Yes | + +### 8.9.2.3 Information that may be transferred from the gNB to LMF + +The information that may be transferred from gNB to the LMF is listed in table 8.9.2.3-1. + +**Table 8.9.2.3-1: Information that may be transferred from gNB to the LMF** + +| Information | +|----------------------------------------------------| +| UL Angle of Arrival (azimuth and elevation) | +| Cell Portion ID | +| NR Measurement Results List: | +| - SS Reference signal received power (SS-RSRP) | +| - SS Reference Signal Received Quality (SS-RSRQ) | +| - CSI Reference signal received power (CSI-RSRP) | +| - CSI Reference Signal Received Quality (CSI-RSRQ) | +| - NR Cell Global Identifier /Physical Cell ID | +| - Timing Advance ( $T_{ADV}$ ) | +| E-UTRA Measurement Results List: | +| - E-UTRA Physical Cell ID | +| - E-UTRA Reference Signal Received Power (RSRP) | +| - E-UTRA Reference Signal Received Quality (RSRQ) | + +Both cell-level and beam-level measurements for SS-RSRP, SS-RSRQ, CSI-RSRP and CSI-RSRQ are supported. + +## 8.9.3 Downlink NR E-CID Positioning Procedures + +### 8.9.3.0 General + +The procedures described in this clause support NR E-CID related measurements obtained by the UE and provided to the LMF using LPP. The term "downlink" is intended to indicate that from the LMF perspective the involved measurements are provided by the UE; this set of procedures might also be considered as "UE-assisted, LMF-based NR E-CID". + +### 8.9.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for NR E-CID positioning is described in clause 7.1.2.1. + +### 8.9.3.2 Assistance Data Transfer Procedure + +Assistance data transfer is not required for NR E-CID positioning. + +### 8.9.3.3 Location Information Transfer Procedure + +#### 8.9.3.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +#### 8.9.3.3.1 LMF-initiated Location Information Transfer from UE + +Figure 8.9.3.3.1-1 shows the Location Information Transfer operations for the NR E-CID method from UE when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure. The diagram shows two lifelines: UE and LMF. Step 1: LMF sends '1. LPP Request Location Information' to UE. Step 2: UE sends '2. LPP Provide Location Information' to LMF.](fae02fa1dac97fc5f19a7b85d20df290_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + LMF->>UE: 1. LPP Request Location Information + UE-->>LMF: 2. LPP Provide Location Information +``` + +Sequence diagram for LMF-initiated Location Information Transfer Procedure. The diagram shows two lifelines: UE and LMF. Step 1: LMF sends '1. LPP Request Location Information' to UE. Step 2: UE sends '2. LPP Provide Location Information' to LMF. + +**Figure 8.9.3.3.1-1: LMF-initiated Location Information Transfer Procedure.** + +- (1) The LMF sends a LPP Request Location Information message to the UE for invocation of NR E-CID positioning. This request includes the NR E-CID measurements requested by the LMF and supported by the UE as listed in Table 8.9.2.2-1 together with a required response time. +- (2) The UE sends an LPP Provide Location Information message to the LMF and reports the requested measurements that are available in the UE before the Response Time provided in step (1) elapsed. If the requested measurements are not available, or if the Response Time provided in step (1) elapsed before any of the requested measurements have been obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.9.3.3.2 UE-initiated Location Information Delivery procedure + +Figure 8.9.3.3.2-1 shows the Location Information Delivery procedure operations for the NR E-CID method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Location Information Delivery Procedure. The diagram shows two lifelines: UE and LMF. Step 1: UE sends '1. LPP Provide Location Information' to LMF.](b822771c1a5790feaeecfc439e08bcdd_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + UE->>LMF: 1. LPP Provide Location Information +``` + +Sequence diagram for UE-initiated Location Information Delivery Procedure. The diagram shows two lifelines: UE and LMF. Step 1: UE sends '1. LPP Provide Location Information' to LMF. + +**Figure 8.9.3.3.2-1: UE-initiated Location Information Delivery Procedure.** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE measurements already available at the UE. + +## 8.9.4 Uplink NR E-CID Positioning Procedures + +### 8.9.4.0 General + +The procedures described in this clause support NR E-CID related measurements obtained by the serving gNB and provided to the LMF using NRPPa. The term "uplink" is intended to indicate that from the LMF perspective the involved measurements are provided by the serving gNB; this set of procedures might also be considered as "NG-RAN node assisted NR E-CID". + +### 8.9.4.1 Capability Transfer Procedure + +The Capability Transfer procedure is not applicable to UL NR E-CID positioning. + +### 8.9.4.2 Assistance Data Transfer Procedure + +Assistance data transfer is not required for UL NR E-CID positioning. + +### 8.9.4.3 Location Information Transfer Procedure + +The purpose of this procedure is to enable the LMF to request position measurements from the gNB. + +Figure 8.9.4.3-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram of LMF-initiated Location Information Transfer Procedure](ade78fa2db5ef634649778c88d67c733_img.jpg) + +``` +sequenceDiagram + participant gNB + participant LMF + Note right of LMF: 1. NRPPa Message (Type: E-CID) +Measurement Initiation Request + LMF->>gNB: 1. NRPPa Message (Type: E-CID) +Measurement Initiation Request + Note left of gNB: 2. NRPPa Message (Type: E-CID) +Measurement Initiation Response/Failure + gNB->>LMF: 2. NRPPa Message (Type: E-CID) +Measurement Initiation Response/Failure + Note right of gNB: 3. NRPPa Message (Type: E-CID) +Measurement Report + gNB->>LMF: 3. NRPPa Message (Type: E-CID) +Measurement Report + Note right of gNB: ... + Note left of gNB: 4. NRPPa Message (Type: E-CID) +Measurement Failure Indication + gNB->>LMF: 4. NRPPa Message (Type: E-CID) +Measurement Failure Indication + Note right of LMF: 5. NRPPa Message (Type: E-CID) +Measurement Termination Command + LMF->>gNB: 5. NRPPa Message (Type: E-CID) +Measurement Termination Command +``` + +The diagram illustrates the messaging sequence between the LMF and the gNB for the Location Information Transfer Procedure. It consists of five steps: 1. The LMF sends an NRPPa Message (Type: E-CID) labeled 'Measurement Initiation Request' to the gNB. 2. The gNB responds with an NRPPa Message (Type: E-CID) labeled 'Measurement Initiation Response/Failure' to the LMF. 3. The gNB then sends an NRPPa Message (Type: E-CID) labeled 'Measurement Report' to the LMF. 4. The gNB may also send an NRPPa Message (Type: E-CID) labeled 'Measurement Failure Indication' to the LMF. 5. Finally, the LMF sends an NRPPa Message (Type: E-CID) labeled 'Measurement Termination Command' to the gNB. There is a vertical ellipsis between steps 3 and 4, indicating additional possible messages. + +Sequence diagram of LMF-initiated Location Information Transfer Procedure + +**Figure 8.9.4.3-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends an E-CID Measurement Initiation Request message to the serving gNB to request NR E-CID measurement information. The message includes indication of NR E-CID measurements requested and whether the result is expected only once or periodically. +- (2) If the report characteristics in step 1 is set to "on demand", the gNB obtains the requested NR E-CID measurements and returns them in an E-CID Measurement Initiation Response message to the LMF. The E-CID Measurement Initiation Response message includes the obtained NR E-CID measurements as defined in the clause 8.9.2.3. + +If the report characteristics in step 1 is set to "periodic", the gNB replies with an E-CID Measurement Initiation Response message without including any measurements in the message. The gNB then periodically initiates the E-CID Measurement Report procedure in step 3 for the NR E-CID measurements, with the requested reporting periodicity. + +If the gNB is not able to accept the E-CID Measurement Initiation Request message in step 1, the gNB returns a failure message indicating the cause of the failure. + +- (3) The gNB periodically provides the NR E-CID measurements as defined in the clause 8.9.2.3 to the LMF if that was requested at step 1. +- (4) If the previously requested NR E-CID measurements can no longer be reported, the gNB notifies the LMF by sending an E-CID Measurement Failure Indication message. +- (5) When the LMF wants to terminate an ongoing NR E-CID measurement it sends an E-CID Measurement Termination Command message to the gNB. + +## 8.10 Multi-RTT positioning + +### 8.10.1 General + +In the Multi-RTT positioning method, the UE position is estimated based on measurements performed at both, UE and TRPs. The measurements performed at the UE and TRPs are UE/gNB Rx-Tx time difference measurements (and optionally DL-PRS-RSRP, DL-PRS-RSRPP, UL-SRS-RSRP, UL-SRS-RSRPP, and/or DL-RSCP/UL-RSCP) of DL-PRS and UL-SRS, which are used by an LMF to determine the RTTs. + +For network verification of UE location in NTN, the measurements can be performed at a single TRP at different time instances. The additional measurements performed at UE are the UE Rx – Tx time difference subframe offset in unit of subframe and the DL timing drift due to Doppler in service link between UE and satellite as defined in TS 38.215 [37]. + +The UE may require measurement gaps to perform the Multi-RTT measurements from NR TRPs. The UE may request measurement gaps from a gNB using the procedure described in clause 7.4.1.1. The UE may also request to activate pre-configured measurement gaps as described in clause 7.7.2. + +NOTE: Multi-RTT positioning with aperiodic or semi-persistent SRS is not supported for a U2N Remote UE. + +### 8.10.2 Information to be transferred between NG-RAN/5GC Elements + +#### 8.10.2.0 General + +This clause defines the information that may be transferred between LMF and UE/gNB. + +#### 8.10.2.1 Information that may be transferred from the LMF to UE + +The information that may be transferred from the LMF to the UE are listed in Table 8.10.2.1-1. + +**Table 8.10.2.1-1: Assistance data that may be transferred from LMF to the UE** + +| Information | +|--------------------------------------------------------------------------------------------------------------------------------------------| +| Physical cell IDs (PCIs), global cell IDs (GCIs), and PRS IDs, ARFCNs of candidate NR TRPs for measurement | +| Timing relative to the serving (reference) TRP of candidate NR TRPs | +| DL-PRS configuration of candidate NR TRPs | +| Indication of which DL-PRS Resource Sets across DL-PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | +| PRS-only TP indication | +| On-Demand DL-PRS-Configurations, possibly together with information on which configurations are available for DL-PRS bandwidth aggregation | +| Validity Area of the Assistance Data | + +### 8.10.2.2 Information that may be transferred from the UE to LMF + +The information that may be signalled from UE to the LMF is listed in Table 8.10.2.2-1. The individual UE measurements are defined in TS 38.215 [37]. + +**Table 8.10.2.2-1: Measurement results that may be transferred from UE to the LMF** + +| Information | +|---------------------------------------------------------------------------------------------------------| +| PCI, GCI, and PRS ID, ARFCN, PRS resource ID, PRS resource set ID for each measurement | +| DL-PRS-RSRP measurement | +| UE Rx-Tx time difference measurement | +| DL-RSCP measurement NOTE1, NOTE2 | +| Time stamp of the measurement | +| Quality for each measurement | +| TA offset used by UE | +| UE Rx TEG IDs, UE Tx TEG IDs, and UE RxTx TEG IDs associated with UE Rx-Tx time difference measurements | +| LOS/NLOS information for UE measurements | +| DL-PRS-RSRPP measurement | +| The association of UE Tx TEG ID and SRS | +| Indication that DL-PRS bandwidth aggregation has been used for UE Rx-Tx time difference measurement | +| Indication that the reported measurements are based on receiving single or multiple hops of DL-PRS | +| UE Rx – Tx time difference subframe offset | +| DL timing drift | +| NOTE 1: The DL-RSCP measurement may be reported along with the UE Rx-Tx time difference measurement. | +| NOTE 2: The DL-RSCP is measured from a single DL PRS positioning frequency layer. | + +### 8.10.2.3 Information that may be transferred from the gNB to LMF + +The assistance data that may be transferred from gNB to the LMF is listed in Table 8.10.2.3-1. + +**Table 8.10.2.3-1: Assistance data that may be transferred from gNB to the LMF** + +| Information | +|-----------------------------------------------------------------------------------------------------------------------------------------| +| PCI, GCI, ARFCN and TRP IDs of the TRPs served by the gNB | +| Timing information of TRPs served by the gNB | +| DL-PRS configuration of the TRPs served by the gNB | +| Indication of which DL-PRS Resource Sets across DL-PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | +| Spatial direction information of the DL-PRS Resources of the TRPs served by the gNB | +| Geographical coordinates information of the DL-PRS Resources of the TRPs served by the gNB | +| TRP type | +| On-demand DL-PRS information, possibly together with information on which configurations are available for DL-PRS bandwidth aggregation | +| TRP Tx TEG association information | +| Common TA parameters of TRPs | + +The configuration data for a target UE that may be transferred from the serving gNB to the LMF is listed in Table 8.10.2.3-2. + +**Table 8.10.2.3-2: UL information/UE configuration data that may be transferred from serving gNB to the LMF** + +| UE configuration data | +|---------------------------------------------------| +| UE SRS configuration | +| SFN initialization time for the SRS configuration | +| SRS Transmission Status | + +The measurement results that may be signalled from gNBs to the LMF is listed in Table 8.10.2.3-3. + +**Table 8.10.2.3-3: Measurement results that may be transferred from gNBs to the LMF** + +| Measurement results | +|---------------------------------------------------------------------------| +| NCGI and TRP ID of the measurement | +| gNB Rx-Tx time difference measurement | +| UL-SRS-RSRP | +| UL-SRS-RSRPP | +| UL-RSCP measurement | +| UL Angle of Arrival (azimuth and/or elevation) NOTE 1 | +| Multiple UL Angle of Arrival (azimuth and/or elevation) NOTE 1 | +| SRS Resource Type | +| Time stamp of the measurement | +| Quality for each measurement | +| Beam Information of the measurement | +| LoS/NLoS information for each measurement | +| ARP ID of the measurement | +| NOTE 1: When used with UL-AoA for hybrid positioning. | + +#### 8.10.2.4 Information that may be transferred from the LMF to gNBs + +The requested UL-SRS transmission characteristics information that may be signalled from the LMF to the gNB is listed in Table 8.10.2.4-1. + +**Table 8.10.2.4-1: Requested UL-SRS transmission characteristics information that may be transferred from LMF to gNB.** + +| Information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number Of Transmissions/duration for which the UL-SRS is requested | +| Bandwidth | +| Resource type (periodic, semi-persistent, aperiodic) | +| Number of requested SRS resource sets and SRS resources per set | +| Pathloss reference:
  • - PCI, SSB Index
  • - DL-PRS ID, DL-PRS Resource Set ID, DL-PRS Resource ID
| +| Spatial relation info
  • - PCI, SSB Index
  • - DL-PRS ID, DL-PRS Resource Set ID, DL-PRS Resource ID
  • - NZP CSI-RS Resource ID
  • - SRS Resource ID
  • - Positioning SRS Resource ID
| +| Periodicity of the SRS for each SRS resource set | +| SSB Information | +| Carrier frequency of SRS transmission bandwidth | + +The TRP measurement request information that may be signalled from the LMF to the gNBs is listed in Table 8.10.2.4-2. + +**Table 8.10.2.4-2: TRP Measurement request information that may be transferred from LMF to gNBs.** + +| Information | +|------------------------------------------------------------------------------------------------| +| TRP ID, and NCGI of the TRP to receive UL-SRS | +| UE-SRS configuration | +| UL timing information together with timing uncertainty, for reception of SRS by candidate TRPs | +| Report characteristics for the measurements | +| Measurement Quantities | +| Measurement periodicity | +| Measurement beam information request | +| Search window information | +| Expected UL AoA/ZoA and uncertainty range | +| Number of TRP Rx TEGs | +| Number of TRP RxTx TEGs | +| Response time | +| Measurement characteristics request indicator | +| Measurement time occasions for a measurement instance | + +The Positioning Activation/Deactivation request information that may be signalled from the LMF to the gNB is listed in Table 8.10.2.4-3. + +**Table 8.10.2.4-3: Requested positioning activation/deactivation information that may be transferred from LMF to gNB.** + +| Information | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SP UL-SRS:
  • - Activation or Deactivation request
  • - Positioning SRS Resource Set ID which is to be activated/deactivated
  • - Spatial relation for Resource IDi
  • - Activation Time
| +| Aperiodic UL-SRS
  • - Aperiodic SRS Resource Trigger List
  • - Activation Time
| +| UL-SRS:
  • - Release all
| + +## 8.10.3 Multi-RTT Positioning Procedures + +### 8.10.3.0 General + +The procedures described in this clause support Multi-RTT positioning measurements obtained by the UE and TRPs/gNB. + +#### 8.10.3.1 Procedures between LMF and UE + +##### 8.10.3.1.1 Capability Transfer Procedure + +The Capability Transfer procedure for Multi-RTT positioning is described in clause 7.1.2.1. + +##### 8.10.3.1.2 Assistance Data Transfer Procedure + +###### 8.10.3.1.2.1 Assistance Data Transfer between LMF and UE + +###### 8.10.3.1.2.1.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). The LMF may provide the pre-configured DL-PRS assistance data (with associated validity criteria) to the UE (before or during an + +ongoing LPP positioning session), to be utilized for potential positioning measurements at a future time. Pre-configured DL-PRS assistance data may consist of multiple instances, where each instance is applicable to a different area within the network. One or more assistance data instances may be provided. Each instance is provided in one LPP Assistance Data messages. + +If a UE receives assistance data for a TRP for which it has already stored assistance data, it overwrites the stored assistance data, whereas if a UE receives assistance data for a TRP for which it has not stored assistance data, it stores the assistance data for the TRP and maintains the already stored assistance data for other TRPs. The TRPs are uniquely identified using a combination of PRS-ID and Cell-ID. The number TRPs for which the UE can store Assistance Data is a UE capability and is indicated by the number of areas a UE can support. + +#### 8.10.3.1.2.1.1 LMF initiated Assistance Data Delivery + +Figure 8.10.3.1.2.1.1-1 shows the Assistance Data Delivery operations for the Multi-RTT positioning method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Assistance Data Delivery Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. A single message arrow labeled '1. LPP Provide Assistance Data' points from the LMF lifeline to the UE lifeline.](c701a84b904fedcdb0316835eafbd39f_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE + Note right of LMF: LMF + LMF->>UE: 1. LPP Provide Assistance Data +``` + +Sequence diagram for LMF-initiated Assistance Data Delivery Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. A single message arrow labeled '1. LPP Provide Assistance Data' points from the LMF lifeline to the UE lifeline. + +**Figure 8.10.3.1.2.1.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the Multi-RTT positioning assistance data defined in Table 8.10.2.1-1. + +#### 8.10.3.1.2.1.2 UE initiated Assistance Data Transfer + +Figure 8.10.3.1.2.1.2-1 shows the Assistance Data Transfer operations for the Multi-RTT positioning method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. Two message arrows are shown: '1. LPP Request Assistance Data' pointing from the UE lifeline to the LMF lifeline, and '2. LPP Provide Assistance Data' pointing from the LMF lifeline to the UE lifeline.](54970ef2a417b7f66ddb72ec5c493956_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE + Note right of LMF: LMF + UE->>LMF: 1. LPP Request Assistance Data + LMF->>UE: 2. LPP Provide Assistance Data +``` + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. Two message arrows are shown: '1. LPP Request Assistance Data' pointing from the UE lifeline to the LMF lifeline, and '2. LPP Provide Assistance Data' pointing from the LMF lifeline to the UE lifeline. + +**Figure 8.10.3.1.2.1.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain Multi-RTT positioning assistance data are desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends an LPP Request Assistance Data message to the LMF. This request includes an indication of which specific Multi-RTT assistance data are requested. Additional information concerning the UE's approximate location and serving and neighbour cells may also be provided in the Request Assistance Data message and/or in an accompanying Provide Location Information message to help the LMF provide appropriate assistance data. This additional data may include the UE's last known location if available, the cell IDs of the UE serving NG-RAN node and possibly neighbour NG-RAN nodes, as well as NR E-CID measurements. + +- (2) The LMF provides the requested assistance in an LPP Provide Assistance Data message, if available at the LMF. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +### 8.10.3.1.3 Location Information Transfer Procedure + +#### 8.10.3.1.3.0 General + +The purpose of this procedure is to enable the LMF to request position measurements from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +##### 8.10.3.1.3.1 LMF-initiated Location Information Transfer Procedure + +Figure 8.10.3.1.3.1-1 shows the Location Information Transfer operations for the Multi-RTT positioning method when the procedure is initiated by the LMF. + +![Sequence diagram showing the LMF-initiated Location Information Transfer Procedure. The diagram consists of two vertical lifelines labeled 'UE' on the left and 'LMF' on the right. Step 1 is a message arrow pointing from the LMF to the UE, labeled '1. LPP Request Location Information'. Step 2 is a message arrow pointing from the UE to the LMF, labeled '2. LPP Provide Location Information'.](a1530b77a339c01162a6181e83cbc906_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. LPP Request Location Information + LMF->>UE: 1. LPP Request Location Information + Note left of UE: 2. LPP Provide Location Information + UE->>LMF: 2. LPP Provide Location Information +``` + +Sequence diagram showing the LMF-initiated Location Information Transfer Procedure. The diagram consists of two vertical lifelines labeled 'UE' on the left and 'LMF' on the right. Step 1 is a message arrow pointing from the LMF to the UE, labeled '1. LPP Request Location Information'. Step 2 is a message arrow pointing from the UE to the LMF, labeled '2. LPP Provide Location Information'. + +**Figure 8.10.3.1.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends an LPP Request Location Information message to the UE. This request includes indication of Multi-RTT measurements requested, including any needed measurement configuration information, and required response time. +The LPP Request Location Information message may include one or more time windows during which the target device (which may be a UE or a PRU) is requested to perform the Multi-RTT measurements on indicated DL-PRS Resource Sets. +The LPP Request Location Information message may include a request to perform joint UE Rx-Tx time difference measurement(s) across two or three DL-PRS positioning frequency layers. +The LPP Request Location Information message may include a request to perform the Multi-RTT measurements using receiver frequency hopping for a DL PRS resource within a configured measurement gap. +- (2) The UE obtains Multi-RTT measurements as requested in step 1. The UE then sends an LPP Provide Location Information message to the LMF, before the Response Time provided in step (1) elapsed, and includes the obtained Multi-RTT measurements. If the UE is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +##### 8.10.3.1.3.2 UE-initiated Location Information Delivery procedure + +Figure 8.10.3.1.3.2-1 shows the Location Information Delivery procedure operations for the Multi-RTT positioning method when the procedure is initiated by the UE. + +![Sequence diagram showing UE-initiated Location Information Delivery Procedure. A UE sends an LPP Provide Location Information message to an LMF.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE-initiated Location Information Delivery Procedure + UE->>LMF: 1. LPP Provide Location Information +``` + +Sequence diagram showing UE-initiated Location Information Delivery Procedure. A UE sends an LPP Provide Location Information message to an LMF. + +**Figure 8.10.3.1.3.2-1: UE-initiated Location Information Delivery Procedure.** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE Multi-RTT measurements already available at the UE. + +## 8.10.3.2 Procedures between LMF and gNB + +### 8.10.3.2.1 Assistance Data Delivery between LMF and gNB + +The purpose of these procedures is to enable the gNB to provide assistance data described in Table 8.10.2.3-1 to the LMF, for subsequent delivery to the UE using the procedures of clause 8.10.3.1.2.1 or for use in the calculation of positioning estimates at the LMF or enable the LMF to request UL-SRS configuration information from the serving gNB of a target UE. + +Figure 8.10.3.2.1-1 shows the TRP Information Exchange operation from the gNB to the LMF for the Multi-RTT positioning method. + +![Sequence diagram showing LMF-initiated TRP Information Exchange Procedure. The LMF sends an NRPPa TRP INFORMATION REQUEST message to the gNB, and the gNB responds with an NRPPa TRP INFORMATION RESPONSE message.](49b9b8bd6845ff94f361b147c84fc945_img.jpg) + +``` +sequenceDiagram + participant gNB + participant LMF + Note right of LMF: LMF-initiated TRP Information Exchange Procedure + LMF->>gNB: NRPPa TRP INFORMATION REQUEST + gNB-->>LMF: NRPPa TRP INFORMATION RESPONSE +``` + +Sequence diagram showing LMF-initiated TRP Information Exchange Procedure. The LMF sends an NRPPa TRP INFORMATION REQUEST message to the gNB, and the gNB responds with an NRPPa TRP INFORMATION RESPONSE message. + +**Figure 8.10.3.2.1-1: LMF-initiated TRP Information Exchange Procedure** + +- (1) The LMF determines that certain TRP configuration information is desired (e.g., as part of a periodic update or as triggered by OAM) and sends an NRPPa TRP INFORMATION REQUEST message to the gNB. This request includes an indication of which specific TRP configuration information is requested. +- (2) The gNB provides the requested TRP information in an NRPPa TRP INFORMATION RESPONSE message, if available at the gNB. If the gNB is not able to provide any information, it returns an TRP INFORMATION FAILURE message indicating the cause of the failure. + +Figure 8.10.3.2.1-2 shows the UL information Delivery operation from the serving gNB to the LMF. + +![Sequence diagram showing the LMF-initiated UL Information Request Procedure between gNB and LMF.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +``` +sequenceDiagram + participant gNB + participant LMF + Note left of gNB: gNB + Note right of LMF: LMF + LMF->>gNB: 1. NRPPa Message (Type: POSITIONING INFORMATION REQUEST) + gNB-->>LMF: 2. NRPPa Message (Type: POSITIONING INFORMATION RESPONSE/FAILURE) + gNB->>LMF: 3. NRPPa Message (Type: POSITIONING INFORMATION UPDATE) +``` + +The diagram illustrates a sequence of three messages between the gNB and the LMF. The gNB is on the left and the LMF is on the right. The first message is a request from the LMF to the gNB. The second message is a response from the gNB to the LMF. The third message is an update from the gNB to the LMF. + +Sequence diagram showing the LMF-initiated UL Information Request Procedure between gNB and LMF. + +**Figure 8.10.3.2.1-2: LMF-initiated UL Information Request Procedure** + +- (1) The LMF sends a NRPPa message POSITIONING INFORMATION REQUEST to the serving gNB of the target UE to request UE SRS configuration information. If the message includes the Requested UL-SRS Transmission Characteristics as listed in Table 8.10.2.4-1, the gNB should take this information into account when configuring UL-SRS transmissions for the UE. +- (2) The serving gNB determines the UE SRS configuration to be allocated for the UE and sends NRPPa message POSITIONING INFORMATION RESPONSE to the LMF that includes the UE SRS configuration defined in Table 8.10.2.3-2. If the serving gNB is not able to provide the requested information, it returns a failure message indicating the cause of the failure. +- (3) If a change has occurred in the UE SRS configuration during the UE SRS time duration requested at step 1, the gNB sends a POSITIONING INFORMATION UPDATE message to the LMF. This message contains, in the case of a change in UE SRS configuration parameters, the UE SRS configuration information for all cells with UE SRS configured, or an update in SRS transmission status. + +#### 8.10.3.2.2 Location Information Transfer/Assistance Data Transfer Procedure + +The purpose of this procedure is to enable the LMF to request position measurements from a gNB for position calculation of the UE and also provide necessary assistance data to the gNB. + +Figure 8.10.3.2.2-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram illustrating the LMF-initiated Location Information Transfer Procedure. The diagram shows two lifelines: LMF (left) and gNB (right). The sequence of messages is: 1. LMF sends a NRPPa message to gNB. 2. gNB sends a Measurement Response message to LMF. 3. gNB sends a Measurement Report message to LMF. 4. LMF sends a Measurement Update message to gNB. 5. gNB sends a Measurement Failure Indication message to LMF. 6. LMF sends a Measurement Abort message to gNB. Vertical ellipsis between steps 3 and 4 indicates periodic reporting.](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +``` + +sequenceDiagram + participant LMF + participant gNB + Note left of LMF: (1) LMF sends NRPPa + LMF->>gNB: NRPPa + Note right of gNB: (2) gNB obtains measurements + gNB-->>LMF: Measurement Response + Note right of gNB: (3) gNB periodically provides measurements + gNB-->>LMF: Measurement Report + Note left of LMF: (4) LMF may send Update + LMF->>gNB: Measurement Update + Note right of gNB: (5) gNB may fail + gNB-->>LMF: Measurement Failure Indication + Note left of LMF: (6) LMF may abort + LMF->>gNB: Measurement Abort + +``` + +Sequence diagram illustrating the LMF-initiated Location Information Transfer Procedure. The diagram shows two lifelines: LMF (left) and gNB (right). The sequence of messages is: 1. LMF sends a NRPPa message to gNB. 2. gNB sends a Measurement Response message to LMF. 3. gNB sends a Measurement Report message to LMF. 4. LMF sends a Measurement Update message to gNB. 5. gNB sends a Measurement Failure Indication message to LMF. 6. LMF sends a Measurement Abort message to gNB. Vertical ellipsis between steps 3 and 4 indicates periodic reporting. + +**Figure 8.10.3.2.2-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a NRPPa message to the selected gNB to request Multi-RTT measurement information. The message includes any information required for the gNB to perform the measurements as defined in Table 8.10.2.4-2. +- (2) If the report characteristics in step 1 is set to "on demand", the gNB obtains the requested Multi-RTT measurements and returns them in a Measurement Response message to the LMF. The Measurement Response message includes the obtained Multi-RTT measurements as defined in Table 8.10.2.3-3. + +If the report characteristics in step 1 is set to "periodic", the gNB replies with a Measurement Response message without including any measurements in the message. The gNB then periodically initiates the Measurement Report procedure in step 3 for the Multi-RTT measurements, with the requested reporting periodicity. + +If the gNB is not able to accept the Measurement Request message in step 1, the gNB returns a failure message indicating the cause of the failure. + +- (3) The gNB periodically provides the Multi-RTT measurements as defined in Table 8.10.2.3-3. to the LMF if that was requested at step 1. +- (4) At any time after step 2, the LMF may send a Measurement Update message to the gNB providing updated information required for the gNB to perform the Multi-RTT measurements as defined in Table 8.10.2.4-2. Upon receiving the message, the gNB overwrites the previously received measurement configuration information. +- (5) If the previously requested Multi-RTT measurements can no longer be reported, the gNB notifies the LMF by sending a Measurement Failure Indication message. +- (6) When the LMF wants to abort an ongoing Multi-RTT measurement it sends a Measurement Abort message to the gNB. + +### 8.10.3.2.3 Positioning Activation/Deactivation Procedure + +The purpose of this procedure is to enable the LMF to request activation and deactivation of UL-SRS transmission of the target UE. + +Figure 8.10.3.2.3-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram for Positioning Activation/Deactivation Procedure. It shows two vertical lifelines representing the LMF (left) and the gNB (right). The sequence of messages is: 1. A solid arrow pointing from the LMF to the gNB. 2. A solid arrow pointing from the gNB back to the LMF. 3. A dashed arrow pointing from the LMF to the gNB. 4. A dashed arrow pointing from the gNB back to the LMF.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +``` +sequenceDiagram + participant LMF + participant gNB + Note left of LMF: (1) NRPPa Positioning Activation Request + LMF->>gNB: NRPPa Positioning Activation Request + Note right of gNB: (2) SP Positioning SRS Activation/Deactivation MAC CE or DCI + gNB-->>LMF: NRPPa Positioning Activation Response / Failure + Note left of LMF: (3) NRPPa Positioning Deactivation + LMF-->>gNB: NRPPa Positioning Deactivation +``` + +Sequence diagram for Positioning Activation/Deactivation Procedure. It shows two vertical lifelines representing the LMF (left) and the gNB (right). The sequence of messages is: 1. A solid arrow pointing from the LMF to the gNB. 2. A solid arrow pointing from the gNB back to the LMF. 3. A dashed arrow pointing from the LMF to the gNB. 4. A dashed arrow pointing from the gNB back to the LMF. + +**Figure 8.10.3.2.3-1: Positioning Activation/Deactivation Procedure.** + +- (1) The LMF sends the NRPPa Positioning Activation Request message to the serving gNB of the target UE to request UL-SRS activation for the target UE. For a semi-persistent UL-SRS, the message includes an indication of an UL-SRS resource set to be activated and may include information that indicates the spatial relation for the semi-persistent UL-SRS resource to be activated, as listed in Table 8.10.2.4-3. For an aperiodic UL-SRS, the message may include aperiodic SRS Resource trigger list to indicate the UL-SRS resource to be activated. +- (2) For semi-persistent UL-SRS, the serving gNB may then activate the configured semi-persistent UL-SRS resource sets by sending the SP Positioning SRS Activation/Deactivation MAC CE command as specified in TS 38.321 [39]. For aperiodic UL-SRS, the serving gNB may then activate the configured aperiodic UL-SRS resource sets by sending the DCI as specified in TS 38.212 [40]. +If the UL-SRS has been successfully activated as requested in step 1, the gNB sends the NRPPa Positioning Activation Response message to the LMF. The serving gNB may include a system frame number and a slot number in the NRPPa Positioning Activation Response message to the LMF. If the serving gNB is not able to fulfil the request from step 1, it returns the Positioning Activation Failure message indicating the cause of the failure. +- (3) If a previously activated UL-SRS should be deactivated, or the UL-SRS transmission should be released, the LMF sends the NRPPa Positioning Deactivation message to the serving gNB of the target device to request deactivation of UL-SRS resource sets, or release all the UL-SRS resources. This message includes an indication of the UL-SRS resource set to be deactivated, or an indication of releasing all UL-SRS resources. + +## 8.10.4 Sequence of Procedure for Multi-RTT positioning + +Figure 8.10.4-1 shows the messaging between the LMF, the gNBs and the UE to perform LMF-initiated Location Information Transfer Procedure for Multi-RTT. + +![Sequence diagram of the Multi-RTT positioning procedure. The diagram shows interactions between a UE, a Serving gNB/TRP, multiple Neighbour gNB/TRPs, and an LMF. The steps are: 0. NRPPa TRP INFORMATION EXCHANGE; 1. LPP Capability Transfer; 2. NRPPa POSITIONING INFORMATION REQUEST; 3. gNB determines UL SRS Resources; 3a. UE SRS Configuration; 4. NRPPa POSITIONING INFORMATION RESPONSE; 5a. NRPPa POSITIONING ACTIVATION REQUEST; 5b. Activate UE SRS transmission; 5c. NRPPa POSITIONING ACTIVATION RESPONSE; 6. NRPPa MEASUREMENT REQUEST; 7. LPP Provide Assistance Data; 8. LPP Request Location Information; 9a. DL-PRS Measurements; 9b. UL SRS Measurements; 10. LPP Provide Location Information; 11. NRPPa MEASUREMENT RESPONSE; 12. NRPPa POSITIONING DEACTIVATION; 13. LMF calculates position.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Serving as Serving + participant Neighbour as Neighbour + participant LMF + Note right of Neighbour: gNB/TRP, gNB/TRP, gNB/TRP + Note left of Serving: gNB/TRP + + Note over Serving, Neighbour: 0. NRPPa TRP INFORMATION EXCHANGE + Note over UE, LMF: 1. LPP Capability Transfer + LMF->>Serving: 2. NRPPa POSITIONING INFORMATION REQUEST + Note right of Serving: 3. gNB determines UL SRS Resources + Serving->>UE: 3a. UE SRS Configuration + Serving->>LMF: 4. NRPPa POSITIONING INFORMATION RESPONSE + LMF->>Serving: 5a. NRPPa POSITIONING ACTIVATION REQUEST + Serving->>UE: 5b. Activate UE SRS transmission + Serving->>LMF: 5c. NRPPa POSITIONING ACTIVATION RESPONSE + Note over Neighbour: 6. NRPPa MEASUREMENT REQUEST + Note over Neighbour: (Multiple arrows between gNB/TRPs) + Serving->>UE: 7. LPP Provide Assistance Data + Serving->>UE: 8. LPP Request Location Information + Note left of UE: 9a. DL-PRS Measurements + Note right of Serving: 9b. UL SRS Measurements + Serving->>LMF: 10. LPP Provide Location Information + Note over Neighbour: 11. NRPPa MEASUREMENT RESPONSE + Note over Neighbour: (Multiple arrows between gNB/TRPs) + LMF->>Serving: 12. NRPPa POSITIONING DEACTIVATION + Note right of LMF: 13. LMF calculates position + +``` + +Sequence diagram of the Multi-RTT positioning procedure. The diagram shows interactions between a UE, a Serving gNB/TRP, multiple Neighbour gNB/TRPs, and an LMF. The steps are: 0. NRPPa TRP INFORMATION EXCHANGE; 1. LPP Capability Transfer; 2. NRPPa POSITIONING INFORMATION REQUEST; 3. gNB determines UL SRS Resources; 3a. UE SRS Configuration; 4. NRPPa POSITIONING INFORMATION RESPONSE; 5a. NRPPa POSITIONING ACTIVATION REQUEST; 5b. Activate UE SRS transmission; 5c. NRPPa POSITIONING ACTIVATION RESPONSE; 6. NRPPa MEASUREMENT REQUEST; 7. LPP Provide Assistance Data; 8. LPP Request Location Information; 9a. DL-PRS Measurements; 9b. UL SRS Measurements; 10. LPP Provide Location Information; 11. NRPPa MEASUREMENT RESPONSE; 12. NRPPa POSITIONING DEACTIVATION; 13. LMF calculates position. + +**Figure 8.10.4-1: Multi-RTT positioning procedure** + +0. The LMF may use the procedure in Figure 8.10.3.2.1-1 to obtain the TRP information required for Multi-RTT positioning. +1. The LMF may request the positioning capabilities of the target device using the LPP Capability Transfer procedure described in clause 8.10.3.1.1. +2. The LMF sends a NRPPa POSITIONING INFORMATION REQUEST message to the serving gNB to request UL information for the target device as described in Figure 8.10.3.2.1-2. +3. The serving gNB determines the resources available for UL-SRS and configures the target device with the UL-SRS resource sets at step 3a. +4. The serving gNB provides the UL-SRS configuration information to the LMF in a NRPPa POSITIONING INFORMATION RESPONSE message. + +NOTE: It is up to implementation on whether SRS configuration is provided earlier than DL-PRS configuration. + +- 5a. In the case of semi-persistent or aperiodic SRS, the LMF may request activation of UE SRS transmission by sending a NRPPa Positioning Activation Request message to the serving gNB of the target device as described in clause 8.10.3.2.3. +- 5b. The gNB then activates the UE SRS transmission. The target device begins the UL-SRS transmission according to the time domain behavior of UL-SRS resource configuration. +- 5c. The gNB sends a NRPPa Positioning Activation Response message. +6. The LMF provides the UL information to the selected gNBs in a NRPPa MEASUREMENT REQUEST message as described in clause 8.10.3.2.2. The message includes all information required to enable the gNBs/TRPs to perform the UL measurements. +7. The LMF sends a LPP Provide Assistance Data message to the target device as described in clause 8.10.3.1.2.1. The message includes any required assistance data for the target device to perform the necessary DL-PRS measurements. +8. The LMF sends a LPP Request Location Information message to request Multi-RTT measurements. +- 9a: The target device performs the DL-PRS measurements from all gNBs provided in the assistance data at step 7. In NTN, the target device performs the DL-PRS measurements from a single TRP at different time instances. +- 9b: Each gNB configured at step 6 measures the UE SRS transmissions from the target device. +10. The target device reports the DL-PRS measurements for Multi-RTT to the LMF in a LPP Provide Location Information message. +11. Each gNB reports the UE SRS measurements to the LMF in a NRPPa Measurement Response message as described in clause 8.10.3.2.2. +12. The LMF sends a NRPPa POSITIONING DEACTIVATION message to the serving gNB as described in clause 8.10.3.2.3. +13. The LMF determines the RTTs from the UE and gNB Rx-Tx time difference measurements for each gNB for which corresponding UL and DL measurements were provided at steps 10 and 11 and calculates the position of the target device. + +## 8.11 DL-AoD positioning + +### 8.11.1 General + +In the DL-AoD positioning method, the UE position is estimated based on DL-PRS-RSRP and/or DL-PRS-RSRPP measurements taken at the UE of downlink radio signals from multiple NR TRPs, along with knowledge of the spatial information of the downlink radio signals and geographical coordinates of the TRPs. + +The UE while connected to a gNB may require measurement gaps to perform the DL-AoD measurements from NR TRPs. The UE may request measurement gaps from a gNB using the procedure described in clause 7.4.1.1. The UE may also request to activate pre-configured measurement gaps as described in clause 7.7.2. + +The specific positioning techniques used to estimate the UE's location from this information are beyond the scope of this specification. + +### 8.11.2 Information to be transferred between NG-RAN/5GC Elements + +#### 8.11.2.0 General + +This clause defines the information that may be transferred between LMF and UE/gNB. + +## 8.11.2.1 Information that may be transferred from the LMF to UE + +### 8.11.2.1.0 General + +The information that may be transferred from the LMF to the UE are listed in table 8.11.2.1.0-1. + +**Table 8.11.2.1.0-1: Assistance data that may be transferred from LMF to the UE** + +| Information | UE-assisted | UE-based | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------| +| Physical cell IDs (PCIs), global cell IDs (GCIs), ARFCN, and PRS IDs of candidate NR TRPs for measurement | Yes | Yes | +| Timing relative to the serving (reference) TRP of candidate NR TRPs | Yes | Yes | +| DL-PRS configuration of candidate NR TRPs | Yes | Yes | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | Yes | Yes | +| Spatial direction information (e.g. azimuth, elevation etc.) of the DL-PRS Resources of the TRPs served by the gNB | Yes | Yes | +| Geographical coordinates of the TRPs served by the gNB (include a transmission reference location for each DL-PRS Resource ID, reference location for the transmitting antenna of the reference TRP, relative locations for transmitting antennas of other TRPs) | No | Yes | +| PRS-only TP indication | Yes | Yes | +| TRP beam/antenna information (including azimuth angle, zenith angle and relative power between PRS resources per angle per TRP) | No | Yes | +| LOS/NLOS indicators | No | Yes | +| On-Demand DL-PRS-Configurations | Yes | Yes | +| Expected Angle Assistance information | Yes | Yes | +| PRS priority list | Yes | Yes | +| Validity Area of the Assistance Data | Yes | Yes | +| Data facilitating the integrity results determination of the calculated location | No | Yes | + +### 8.11.2.1.1 Mapping of integrity parameters + +Table 8.11.2.1.1-1 shows the mapping between the integrity fields and the assistance data according to the Integrity Principle of Operation (Clause 7.13.2). The corresponding field descriptions for each of the field names listed in Table 8.11.2.1.1-1 are specified in TS 37.355 [42]. + +**Table 8.11.2.1.1-1: Mapping of Integrity Parameters** + +| Error | NR Assistance Data | Integrity Fields | | | | | +|----------------------------------------|-------------------------------|--------------------------------|---------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------|-------------------------------------------------------| +| | | Integrity Alerts | Integrity Bounds (Mean) | Integrity Bounds (StdDev) | Residual Risks | Integrity Correlation Times | +| TRP location | NR-TRP-LocationInfo | TRP DNU | Mean TRP/ARP location error | Standard deviation TRP/ARP location error | Probability of Onset of TRP fault
Mean TRP fault duration | TRP/ARP location error correlation time | +| Boresight Direction of DL-PRS Resource | NR-DL-PRS-BeamInfo | DL-PRS Boresight Direction DNU | Mean Azimuth/Elevation Error of DL-PRS Resource boresight direction | Standard deviation Azimuth/Elevation Error of DL-PRS Resource boresight direction | | Beam Boresight Direction Angle Error Correlation Time | +| Beam information of DL-PRS | NR-TRP-BeamAntennaInfo | DL-PRS Beam Information DNU | Mean Beam Power Error per direction | Standard deviation Beam Power Error per direction | | Beam Power Error Correlation Time | + +### 8.11.2.2 Information that may be transferred from the UE to LMF + +The information that may be signalled from UE to the LMF is listed in Table 8.11.2.2-1. The individual UE measurements are defined in TS 38.215 [37]. + +**Table 8.11.2.2-1: Measurement results that may be transferred from UE to the LMF** + +| Information | UE-assisted | UE-based | +|---------------------------------------------------------------------------------------|-------------|----------| +| Latitude/Longitude/Altitude, together with uncertainty shape | No | Yes | +| PCI, GCI, ARFCN, PRS resource ID, PRS resource set ID and PRS ID for each measurement | Yes | No | +| DL-PRS-RSRP measurement | Yes | No | +| Time stamp of the measurements | Yes | No | +| Time stamp of location estimate | No | Yes | +| DL-PRS receive beam index | Yes | No | +| DL-PRS-RSRPP measurements | Yes | No | +| LOS/NLOS information for UE measurements | Yes | No | +| Protection Level, optionally together with achievable Target Integrity Risk | No | Yes | + +### 8.11.2.3 Information that may be transferred from the gNB to LMF + +The assistance data that may be transferred from gNB to the LMF is listed in Table 8.11.2.3-1. + +**Table 8.11.2.3-1: Assistance data that may be transferred from gNB to the LMF** + +| Information | +|--------------------------------------------------------------------------------------------| +| PCI, GCI, ARFCN, and TRP IDs of the TRPs served by the gNB | +| Timing information of TRPs served by the gNB | +| DL-PRS configuration of the TRPs served by the gNB | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | +| Spatial direction information of the DL-PRS Resources of the TRPs served by the gNB | +| Geographical coordinates information of the DL-PRS Resources of the TRPs served by the gNB | +| TRP type | +| On-demand DL-PRS information | +| TRP beam antenna information | + +## 8.11.3 DL-AoD Positioning Procedures + +### 8.11.3.0 General + +The procedures described in this clause support UE-assisted and UE-based DL-AOD. + +### 8.11.3.1 Procedures between LMF and UE + +#### 8.11.3.1.1 Capability Transfer Procedure + +The Capability Transfer procedure for DL-AoD positioning is described in clause 7.1.2.1. + +#### 8.11.3.1.2 Assistance Data Transfer Procedure + +##### 8.11.3.1.2.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). The LMF may provide the pre-configured DL-PRS assistance data (with associated validity criteria) to the UE (before or during an ongoing LPP positioning session), to be utilized for potential positioning measurements at a future time. Pre-configured + +DL-PRS assistance data may consist of multiple instances, where each instance is applicable to a different area within the network. One or more assistance data instances may be provided. Each instance is provided in one LPP Assistance Data messages. + +If a UE receives assistance data for a TRP for which it has already stored assistance data, it overwrites the stored assistance data, whereas if a UE receives assistance data for a TRP for which it has not stored assistance data, it stores the assistance data for the TRP and maintains the already stored assistance data for other TRPs. The TRPs are uniquely identified using a combination of PRS-ID and Cell-ID. The number TRPs for which the UE can store Assistance Data is a UE capability and is indicated by the number of areas a UE can support. + +#### 8.11.3.1.2.1 LMF initiated Assistance Data Delivery + +Figure 8.11.3.1.2.1-1 shows the Assistance Data Delivery operations for the DL-AoD positioning method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Assistance Data Delivery Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. A single message arrow labeled '1. LPP Provide Assistance Data' points from the LMF lifeline to the UE lifeline.](a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + LMF->>UE: 1. LPP Provide Assistance Data + Note right of LMF: +``` + +Sequence diagram for LMF-initiated Assistance Data Delivery Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. A single message arrow labeled '1. LPP Provide Assistance Data' points from the LMF lifeline to the UE lifeline. + +**Figure 8.11.3.1.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the DL-AoD positioning assistance data defined in Table 8.11.2.1-1. + +#### 8.11.3.1.2.2 UE initiated Assistance Data Transfer + +Figure 8.11.3.1.2.2-1 shows the Assistance Data Transfer operations for the DL-AoD positioning method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. Two message arrows are shown: '1. LPP Request Assistance Data' from UE to LMF, and '2. LPP Provide Assistance Data' from LMF back to UE.](ef3cc411849a8effc80adb5a6ad57b36_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: + UE->>LMF: 1. LPP Request Assistance Data + Note right of LMF: + LMF->>UE: 2. LPP Provide Assistance Data + Note left of UE: +``` + +Sequence diagram for UE-initiated Assistance Data Transfer Procedure. It shows two vertical lifelines: UE on the left and LMF on the right. Two message arrows are shown: '1. LPP Request Assistance Data' from UE to LMF, and '2. LPP Provide Assistance Data' from LMF back to UE. + +**Figure 8.11.3.1.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain DL-AoD positioning assistance data are desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends an LPP Request Assistance Data message to the LMF. This request includes an indication of which specific DL-AoD assistance data are requested. Additional information concerning the UE's approximate location and serving and neighbour cells may also be provided in the Request Assistance Data message and/or in an accompanying Provide Location Information message to help the LMF provide appropriate assistance data. This additional data may include the UE's last known location if available, the cell IDs of the UE serving NG-RAN node and possibly neighbour NG-RAN nodes, as well as NR E-CID measurements. + +- (2) The LMF provides the requested assistance in an LPP Provide Assistance Data message, if available at the LMF. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +### 8.11.3.1.3 Location Information Transfer Procedure + +#### 8.11.3.1.3.0 General + +The purpose of this procedure is to enable the LMF to request location estimate from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +#### 8.11.3.1.3.1 LMF-initiated Location Information Transfer Procedure + +Figure 8.11.3.1.3.1-1 shows the Location Information Transfer operations for the DL-AoD positioning method when the procedure is initiated by the LMF. + +![Sequence diagram of LMF-initiated Location Information Transfer Procedure](e1136c8a41c5a8081a8a554e513cd86e_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE + Note right of LMF: LMF + LMF->>UE: 1. LPP Request Location Information + UE-->>LMF: 2. LPP Provide Location Information +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Location Management Function (LMF). The UE is represented by a box on the left and the LMF by a box on the right. A solid arrow labeled '1. LPP Request Location Information' points from the LMF to the UE. A dashed arrow labeled '2. LPP Provide Location Information' points from the UE back to the LMF. + +Sequence diagram of LMF-initiated Location Information Transfer Procedure + +**Figure 8.11.3.1.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends an LPP Request Location Information message to the UE. This request includes positioning instructions such as the positioning mode (UE-assisted, UE-based, UE-based preferred but UE-assisted allowed, UE-assisted preferred, but UE-based allowed), indication of DL-AoD measurements requested if any, including any needed measurement configuration information, required response time, and possibly integrity requirements. The LPP Request Location Information message may include one or more time windows during which the target device (which may be a UE or a PRU) is requested to perform the DL-AoD measurements on indicated DL-PRS Resource Sets. + +The LPP Request Location Information message may include a request to perform the DL-AoD measurements using receiver frequency hopping for a DL PRS resource within a configured measurement gap. + +- (2) The UE obtains DL-AoD measurements as requested in step 1 and possibly calculates its own location. The UE may also determine the integrity results of the calculated location. The UE then sends an LPP Provide Location Information message to the LMF, before the Response Time provided in step (1) elapsed, and includes the obtained DL-AoD measurements or calculated location. If the UE is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.11.3.1.3.2 UE-initiated Location Information Delivery procedure + +Figure 8.11.3.1.3.2-1 shows the Location Information Delivery procedure operations for the DL-AoD positioning method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Location Information Delivery Procedure. A UE box is on the left and an LMF box is on the right. A solid arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF.](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE sends LPP Provide Location Information + UE->>LMF: 1. LPP Provide Location Information + +``` + +Sequence diagram for UE-initiated Location Information Delivery Procedure. A UE box is on the left and an LMF box is on the right. A solid arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF. + +**Figure 8.11.3.1.3.2-1: UE-initiated Location Information Delivery Procedure.** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE DL-AoD measurements already available at the UE. + +## 8.11.3.2 Procedures between LMF and gNB + +### 8.11.3.2.1 Assistance Data Delivery procedure + +#### 8.11.3.2.1.0 General + +The purpose of this procedure is to enable the gNB to provide assistance data described in Table 8.11.2.3-1 to the LMF, for subsequent delivery to the UE using the procedures of clause 8.11.3.1.2 or for use in the calculation of positioning estimates at the LMF. + +#### 8.11.3.2.1.1 LMF-initiated assistance data delivery to the LMF + +Figure 8.11.3.2.1.1-1 shows the TRP Information Exchange operation from the gNB to the LMF for the DL-AoD positioning method. + +![Sequence diagram for LMF-initiated TRP Information Exchange Procedure. A gNB box is on the left and an LMF box is on the right. A dashed arrow points from the LMF to the gNB, and a solid arrow points from the gNB to the LMF.](7bf5a5bb9f3c37fa7a3d32147f25bfda_img.jpg) + +``` + +sequenceDiagram + participant gNB + participant LMF + Note right of LMF: LMF sends NRPPa TRP INFORMATION REQUEST + LMF-->>gNB: NRPPa TRP INFORMATION REQUEST + Note left of gNB: gNB provides TRP information + gNB->>LMF: NRPPa TRP INFORMATION RESPONSE + +``` + +Sequence diagram for LMF-initiated TRP Information Exchange Procedure. A gNB box is on the left and an LMF box is on the right. A dashed arrow points from the LMF to the gNB, and a solid arrow points from the gNB to the LMF. + +**Figure 8.11.3.2.1.1-1: LMF-initiated TRP Information Exchange Procedure** + +- (1) The LMF determines that certain TRP configuration information is desired (e.g., as part of a periodic update or as triggered by OAM) and sends an NRPPa TRP INFORMATION REQUEST message to the gNB. This request includes an indication of which specific TRP configuration information is requested. +- (2) The gNB provides the requested TRP information in an NRPPa TRP INFORMATION RESPONSE message, if available at the gNB. If the gNB is not able to provide any information, it returns an TRP INFORMATION FAILURE message indicating the cause of the failure. + +## 8.12 DL-TDOA positioning + +### 8.12.1 General + +In the DL-TDOA positioning method, the UE position is estimated based on DL RSTD (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP and/or DL-RSCPD) measurements taken at the UE of downlink radio signals from multiple NR TRPs, along with knowledge of the geographical coordinates of the TRPs and their relative downlink timing. + +The UE while connected to a gNB may require measurement gaps to perform the DL-TDOA measurements from NR TRPs. The UE may request measurement gaps from a gNB using the procedure described in clause 7.4.1.1. The UE may also request to activate pre-configured measurement gaps as described in clause 7.7.2. + +The specific positioning techniques used to estimate the UE's location from this information are beyond the scope of this specification. + +### 8.12.2 Information to be transferred between NG-RAN/5GC Elements + +#### 8.12.2.0 General + +This clause defines the information that may be transferred between LMF and UE/gNB. + +#### 8.12.2.1 Information that may be transferred from the LMF to UE + +##### 8.12.2.1.0 General + +The information that may be transferred from the LMF to the UE are listed in table 8.12.2.1.0-1. + +**Table 8.12.2.1.0-1: Assistance data that may be transferred from LMF to the UE** + +| Information | UE-assisted | UE-based | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------| +| Physical cell IDs (PCIs), global cell IDs (GCIs), ARFCN, and PRS IDs of candidate NR TRPs for measurement | Yes | Yes | +| Timing relative to the serving (reference) TRP of candidate NR TRPs | Yes | Yes | +| DL-PRS configuration of candidate NR TRPs | Yes | Yes | +| Indication of which DL-PRS Resource Sets across DL-PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation | Yes | Yes | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | Yes | Yes | +| Spatial direction information (e.g. azimuth, elevation etc.) of the DL-PRS Resources of the TRPs served by the gNB | No | Yes | +| Geographical coordinates of the TRPs served by the gNB (include a transmission reference location for each DL-PRS Resource ID, reference location for the transmitting antenna of the reference TRP, relative locations for transmitting antennas of other TRPs) | No | Yes | +| Fine Timing relative to the serving (reference) TRP of candidate NR TRPs | No | Yes | +| PRS-only TP indication | Yes | Yes | +| The association information of DL-PRS resources with TRP Tx TEG ID | No | Yes | +| LOS/NLOS indicators | No | Yes | +| On-Demand DL-PRS-Configurations, possibly together with information on which configurations are available for DL-PRS bandwidth aggregation | Yes | Yes | +| Validity Area of the Assistance Data | Yes | Yes | +| PRU measurements together with the location information of the PRU | No | Yes | +| Data facilitating the integrity results determination of the calculated location | No | Yes | + +##### 8.12.2.1.1 Mapping of integrity parameters + +Table 8.12.2.1.1-1 shows the mapping between the integrity fields and the assistance data according to the Integrity Principle of Operation (Clause 7.13.2). The corresponding field descriptions for each of the field names listed in Table 8.12.2.1.1-1 are specified in TS 37.355 [42]. + +**Table 8.12.2.1.1-1: Mapping of Integrity Parameters** + +| Error | NR Assistance Data | Integrity Fields | | | | | +|---------------------------|----------------------------|------------------|-----------------------------|-------------------------------------------|-----------------------------------|-----------------------------------------| +| | | Integrity Alerts | Integrity Bounds (Mean) | Integrity Bounds (StdDev) | Residual Risks | Integrity Correlation Times | +| TRP location | NR-TRP-LocationInfo | TRP DNU | Mean TRP/ARP location error | Standard deviation TRP/ARP location error | Probability of Onset of TRP fault | TRP/ARP location error correlation time | +| Inter-TRP synchronization | NR-RTD-Info | RTD DNU | Mean RTD error | Standard deviation RTD error | Mean TRP fault duration | RTD error correlation time | + +## 8.12.2.2 Information that may be transferred from the UE to LMF + +### 8.12.2.2.0 General + +The information that may be signalled from UE to the LMF is listed in Table 8.12.2.2.0-1. The individual UE measurements are defined in TS 38.215 [37]. + +**Table 8.12.2.2.0-1: Measurement results that may be transferred from UE to the LMF** + +| Information | UE-assisted | UE-based | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------| +| Latitude/Longitude/Altitude, together with uncertainty shape | No | Yes | +| PCI, GCI, ARFCN, PRS resource ID, PRS resource set ID and PRS ID for each measurement | Yes | No | +| DL RSTD measurement | Yes | No | +| DL-PRS-RSRP measurement | Yes | No | +| DL-RSCPD measurement NOTE 1, NOTE 2 | Yes | No | +| Time stamp of the measurements | Yes | No | +| Time stamp of location estimate | No | Yes | +| Quality for each measurement | Yes | No | +| UE Rx TEG IDs for DL RSTD measurements | Yes | No | +| DL-PRS-RSRPP measurement | Yes | No | +| LOS/NLOS information for UE measurements | Yes | No | +| Indication that DL-PRS bandwidth aggregation has been used for DL RSTD measurement | Yes | No | +| Indication that the reported measurements are based on receiving single or multiple hops of DL-PRS. | Yes | No | +| Protection Level, optionally together with achievable Target Integrity Risk | No | Yes | +| NOTE 1: The DL-RSCPD measurement may be reported along with the DL RSTD measurement.
NOTE 2: The DL-RSCPD is measured from a single DL PRS positioning frequency layer. | | | + +## 8.12.2.3 Information that may be transferred from the gNB to LMF + +### 8.12.2.3.0 General + +The assistance data that may be transferred from gNB to the LMF is listed in Table 8.12.2.3.0-1. + +**Table 8.12.2.3.0-1: Assistance data that may be transferred from gNB to the LMF** + +| Information | +|-----------------------------------------------------------------------------------------------------------------------------------------| +| PCI, GCI, ARFCN, and TRP IDs of the TRPs served by the gNB | +| Timing information of TRPs served by the gNB | +| DL-PRS configuration of the TRPs served by the gNB | +| Indication of which DL-PRS Resource Sets across DL-PRS positioning frequency layers are linked for DL-PRS bandwidth aggregation | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | +| Spatial direction information of the DL-PRS Resources of the TRPs served by the gNB | +| Geographical coordinates information of the DL-PRS Resources of the TRPs served by the gNB | +| TRP type | +| On-demand DL-PRS information, possibly together with information on which configurations are available for DL-PRS bandwidth aggregation | +| TRP Tx TEG association information | + +## 8.12.3 DL-TDOA Positioning Procedures + +### 8.12.3.0 General + +The procedures described in this clause support UE-assisted and UE-based DL-TDOA. + +### 8.12.3.1 Procedures between LMF and UE + +#### 8.12.3.1.1 Capability Transfer Procedure + +The Capability Transfer procedure for DL-TDOA positioning is described in clause 7.1.2.1. + +#### 8.12.3.1.2 Assistance Data Transfer Procedure + +##### 8.12.3.1.2.0 General + +The purpose of this procedure is to enable the LMF to provide assistance data to the UE (e.g., as part of a positioning procedure) and the UE to request assistance data from the LMF (e.g., as part of a positioning procedure). The LMF may provide the pre-configured DL-PRS assistance data (with associated validity criteria) to the UE (before or during an ongoing LPP positioning session), to be utilized for potential positioning measurements at a future time. Pre-configured DL-PRS assistance data may consist of multiple instances, where each instance is applicable to a different area within the network. One or more assistance data instances may be provided. Each instance is provided in one LPP Assistance Data messages. + +If a UE receives assistance data for a TRP for which it has already stored assistance data, it overwrites the stored assistance data, whereas if a UE receives assistance data for a TRP for which it has not stored assistance data, it stores the assistance data for the TRP and maintains the already stored assistance data for other TRPs. The TRPs are uniquely identified using a combination of PRS-ID and Cell-ID. The number TRPs for which the UE can store Assistance Data is a UE capability and is indicated by the number of areas a UE can support. + +##### 8.12.3.1.2.1 LMF initiated Assistance Data Delivery + +Figure 8.12.3.1.2.1-1 shows the Assistance Data Delivery operations for the DL-TDOA positioning method when the procedure is initiated by the LMF. + +![Sequence diagram showing the LMF-initiated Assistance Data Delivery Procedure. A box labeled 'UE' is on the left and a box labeled 'LMF' is on the right. A solid arrow labeled '1. LPP Provide Assistance Data' points from the LMF to the UE.](9ba75f891de20483c291538e38701d96_img.jpg) + +Sequence diagram showing the LMF-initiated Assistance Data Delivery Procedure. A box labeled 'UE' is on the left and a box labeled 'LMF' is on the right. A solid arrow labeled '1. LPP Provide Assistance Data' points from the LMF to the UE. + +**Figure 8.12.3.1.2.1-1: LMF-initiated Assistance Data Delivery Procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE (e.g., as part of a positioning procedure) and sends an LPP Provide Assistance Data message to the UE. This message may include any of the DL-TDOA positioning assistance data defined in Table 8.12.2.1-1. + +**8.12.3.1.2.1a LMF initiated Periodic Assistance Data Delivery** + +The Periodic Assistance Data Delivery procedure allows the server to provide unsolicited periodic assistance data to the target and is shown in Figure 8.12.3.1.2.1a-1. + +**NOTE:** In this version of the specification, periodic assistance data delivery is supported for PRU measurement information only (see clause 5.4.5 and Table 8.12.2.1-1). + +![Sequence diagram showing the LPP Periodic Assistance data delivery procedure. Two boxes representing UE and LMF are shown. Three arrows point from the LMF to the UE. The first two are solid lines, and the third is a dashed line. On the LMF side, there are three corresponding bracket-like markers indicating the sequence of events.](6c03366230af7163bc0866430f8b20c2_img.jpg) + +Sequence diagram showing the LPP Periodic Assistance data delivery procedure. Two boxes representing UE and LMF are shown. Three arrows point from the LMF to the UE. The first two are solid lines, and the third is a dashed line. On the LMF side, there are three corresponding bracket-like markers indicating the sequence of events. + +**Figure 8.12.3.1.2.1a-1: LPP Periodic Assistance data delivery procedure** + +- (1) The LMF determines that assistance data needs to be provided to the UE and sends an LPP Provide Assistance Data message to the UE. This message includes information to identify the type of periodic assistance data and a duration for ending the assistance data delivery. The message indicates the end of the control transaction. +- (2) When the first periodic message is available, the LMF sends an unsolicited LPP Provide Assistance Data message to the UE containing the periodic assistance data announced in step (1). +- (3) The LMF may continue to send further LPP Provide Assistance Data messages to the target containing the periodic assistance data announced in step (1) when each additional periodicity condition occurs. When the duration for ending the periodic assistance data transfer occurs, the last LPP Provide Assistance Data message transferred indicates the end of transaction. Additionally, the session can be ended on request by the UE or by the LMF with the help of an Abort message. + +#### 8.12.3.1.2.2 UE initiated Assistance Data Transfer + +Figure 8.12.3.1.2.2-1 shows the Assistance Data Transfer operations for the DL-TDOA positioning method when the procedure is initiated by the UE. + +![Sequence diagram showing UE-initiated Assistance Data Transfer Procedure. The UE sends an LPP Request Assistance Data message to the LMF, and the LMF responds with an LPP Provide Assistance Data message.](0850300da6b28250eb47881da35cabad_img.jpg) + +``` +sequenceDiagram + participant UE + participant LMF + Note left of UE: UE initiates procedure + UE->>LMF: 1. LPP Request Assistance Data + LMF-->>UE: 2. LPP Provide Assistance Data +``` + +Sequence diagram showing UE-initiated Assistance Data Transfer Procedure. The UE sends an LPP Request Assistance Data message to the LMF, and the LMF responds with an LPP Provide Assistance Data message. + +**Figure 8.12.3.1.2.2-1: UE-initiated Assistance Data Transfer Procedure** + +- (1) The UE determines that certain DL-TDOA positioning assistance data are desired (e.g., as part of a positioning procedure when the LMF provided assistance data are not sufficient for the UE to fulfil the request) and sends an LPP Request Assistance Data message to the LMF. This request includes an indication of which specific DL-TDOA assistance data are requested. Additional information concerning the UE's approximate location and serving and neighbour cells may also be provided in the Request Assistance Data message and/or in an accompanying Provide Location Information message to help the LMF provide appropriate assistance data. This additional data may include the UE's last known location if available, the cell IDs of the UE serving NG-RAN node and possibly neighbour NG-RAN nodes, as well as NR E-CID measurements. +- (2) The LMF provides the requested assistance in an LPP Provide Assistance Data message, if available at the LMF. If any of the UE requested assistance data in step (1) are not provided in step 2, the UE shall assume that the requested assistance data are not supported, or currently not available at the LMF. If none of the UE requested assistance data in step (1) can be provided by the LMF, return any information that can be provided in an LPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +#### 8.12.3.1.2.2a UE initiated Periodic Assistance Data Transfer + +Figure 8.12.3.1.2.2a-1 shows the Periodic Assistance Data Transfer operations when the procedure is initiated by the UE. + +NOTE: In this version of the specification, periodic assistance data delivery is supported for PRU measurement information only (see clause 5.4.5 and Table 8.12.2.1-1). + +![Sequence diagram for UE-initiated Periodic Assistance Data Transfer Procedure. The diagram shows two lifelines: UE (left) and LMF (right). The sequence of messages is: 1. UE sends a solid arrow message to LMF. 2. LMF sends a solid arrow message to UE. 3. LMF sends another solid arrow message to UE. 4. LMF sends a dashed arrow message to UE. Brackets on the LMF side group the last three messages.](b02ba0b73e95416eb547976f6145b169_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LMF + Note right of LMF: 1. UE Request Assistance Data + UE->>LMF: Request Assistance Data + Note right of LMF: 2. LMF Provide Assistance Data + LMF-->>UE: Provide Assistance Data + Note right of LMF: 3. LMF Provide Assistance Data + LMF-->>UE: Provide Assistance Data + Note right of LMF: 4. LMF Provide Assistance Data + LMF-->>UE: Provide Assistance Data + +``` + +Sequence diagram for UE-initiated Periodic Assistance Data Transfer Procedure. The diagram shows two lifelines: UE (left) and LMF (right). The sequence of messages is: 1. UE sends a solid arrow message to LMF. 2. LMF sends a solid arrow message to UE. 3. LMF sends another solid arrow message to UE. 4. LMF sends a dashed arrow message to UE. Brackets on the LMF side group the last three messages. + +**Figure 8.12.3.1.2.2a-1: UE-initiated Periodic Assistance Data Transfer Procedure** + +- (1) The UE determines that periodic assistance data are desired and sends a LPP Request Assistance Data message to the LMF. This request includes an indication of which specific assistance data are requested together with additional information such as desired periodicity for sending the assistance data and a duration for ending the periodic assistance data delivery session. +- (2) The LMF responds with a LPP Provide Assistance Data message to the UE. If the UE request can be supported, the message contains information which may confirm or redefine the type of assistance data or periodicity parameters requested at step (1). This response indicates the end of the control transaction. +- (3) When available, the LMF provides the requested assistance data in a LPP Provide Assistance Data message to the UE. If any of the requested assistance data in step (1) or redefined in step (2) are not provided the UE assumes that the requested assistance data are not supported, or currently not available at the LMF. +- (4) The LMF may transmit one or more additional LPP Provide Assistance Data messages to the UE containing further periodic assistance data confirmed or redefined in step (2). When the duration for ending the periodic assistance data transfer occur, the last LPP Provide Assistance Data message transferred indicates the end of the transaction. Additionally, the periodic assistance data delivery session can be ended on request by the UE or by the LMF with the help of an Abort message. + +### 8.12.3.1.3 Location Information Transfer Procedure + +#### 8.12.3.1.3.0 General + +The purpose of this procedure is to enable the LMF to request location estimate from the UE, or to enable the UE to provide location measurements to the LMF for position calculation. + +#### 8.12.3.1.3.1 LMF-initiated Location Information Transfer Procedure + +Figure 8.12.3.1.3.1-1 shows the Location Information Transfer operations for the DL-TDOA positioning method when the procedure is initiated by the LMF. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure. The diagram shows two vertical lifelines: UE (User Equipment) on the left and LMF (Location Management Function) on the right. Step 1: An arrow labeled '1. LPP Request Location Information' points from the LMF to the UE. Step 2: An arrow labeled '2. LPP Provide Location Information' points from the UE to the LMF.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) + +Sequence diagram for LMF-initiated Location Information Transfer Procedure. The diagram shows two vertical lifelines: UE (User Equipment) on the left and LMF (Location Management Function) on the right. Step 1: An arrow labeled '1. LPP Request Location Information' points from the LMF to the UE. Step 2: An arrow labeled '2. LPP Provide Location Information' points from the UE to the LMF. + +**Figure 8.12.3.1.3.1-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends an LPP Request Location Information message to the UE. This request includes positioning instructions such as the positioning mode (UE-assisted, UE-based, UE-based preferred but UE-assisted allowed, UE-assisted preferred, but UE-based allowed), indication of DL-TDOA measurements requested if any, including any needed measurement configuration information, required response time, and possibly integrity requirements. + The LPP Request Location Information message may include one or more time windows during which the target device (which may be a UE or a PRU) is requested to perform the DL-TDOA measurements on indicated DL-PRS Resource Sets. + The LPP Request Location Information message may include a request to perform joint DL-RSTD measurements across two or three DL-PRS positioning frequency layers. + The LPP Request Location Information message may include a request to perform the DL-TDOA measurements using receiver frequency hopping for a DL PRS resource within a configured measurement gap. +- (2) The UE obtains DL-TDOA measurements as requested in step 1 and possibly calculates its own location. The UE may also determine the integrity results of the calculated location. The UE then sends an LPP Provide Location Information message to the LMF, before the Response Time provided in step (1) elapsed, and includes the obtained DL-TDOA measurements or calculated location. If the UE is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, the UE returns any information that can be provided in an LPP message of type Provide Location Information which includes a cause indication for the not provided location information. + +#### 8.12.3.1.3.2 UE-initiated Location Information Delivery procedure + +Figure 8.12.3.1.3.2-1 shows the Location Information Delivery procedure operations for the DL-TDOA positioning method when the procedure is initiated by the UE. + +![Sequence diagram for UE-initiated Location Information Delivery Procedure. The diagram shows two vertical lifelines: UE (User Equipment) on the left and LMF (Location Management Function) on the right. Step 1: An arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF.](034b9d22fdb2e7e61ff3b15f229569bf_img.jpg) + +Sequence diagram for UE-initiated Location Information Delivery Procedure. The diagram shows two vertical lifelines: UE (User Equipment) on the left and LMF (Location Management Function) on the right. Step 1: An arrow labeled '1. LPP Provide Location Information' points from the UE to the LMF. + +**Figure 8.12.3.1.3.2-1: UE-initiated Location Information Delivery Procedure.** + +- (1) The UE sends an LPP Provide Location Information message to the LMF. The Provide Location Information message may include any UE DL-TDOA measurements and, optionally, the DL-PRS-RSRP measurements already available at the UE. + +### 8.12.3.2 Procedures between LMF and gNB + +#### 8.12.3.2.1 Assistance Data Delivery procedure + +##### 8.12.3.2.1.0 General + +The purpose of this procedure is to enable the gNB to provide assistance data to the LMF, for subsequent delivery to the UE using the procedures of clause 8.12.3.1.2 or for use in the calculation of positioning estimates at the LMF. + +##### 8.12.3.2.1.1 LMF-initiated assistance data delivery to the LMF + +Figure 8.12.3.2.1.1-1 shows the TRP Information Exchange operation from the gNB to the LMF for the DL-TDOA positioning method. + +![Sequence diagram showing the LMF-initiated TRP Information Exchange Procedure. The LMF sends an NRPPa TRP INFORMATION REQUEST message to the gNB, and the gNB responds with an NRPPa TRP INFORMATION RESPONSE message.](435cf83a9531da350ea543aafa0add62_img.jpg) + +``` + +sequenceDiagram + participant LMF + participant gNB + Note left of LMF: LMF determines TRP configuration information is desired + LMF->>gNB: NRPPa TRP INFORMATION REQUEST + Note right of gNB: gNB provides requested TRP information + gNB-->>LMF: NRPPa TRP INFORMATION RESPONSE + +``` + +Sequence diagram showing the LMF-initiated TRP Information Exchange Procedure. The LMF sends an NRPPa TRP INFORMATION REQUEST message to the gNB, and the gNB responds with an NRPPa TRP INFORMATION RESPONSE message. + +**Figure 8.12.3.2.1.1-1: LMF-initiated TRP Information Exchange Procedure** + +- (1) The LMF determines that certain TRP configuration information is desired (e.g., as part of a periodic update or as triggered by OAM) and sends an NRPPa TRP INFORMATION REQUEST message to the gNB. This request includes an indication of which specific TRP configuration information is requested. +- (2) The gNB provides the requested TRP information in an NRPPa TRP INFORMATION RESPONSE message, if available at the gNB. If the gNB is not able to provide any information, it returns an TRP INFORMATION FAILURE message indicating the cause of the failure. + +## 8.13 UL-TDOA positioning + +### 8.13.1 General + +In the UL-TDOA positioning method, the UE position is estimated based on UL-RTOA (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP and/or UL-RSCP) measurements taken at different TRPs of uplink radio signals from UE, along with other configuration information. + +The specifics of any UL-TDOA positioning methods or techniques used to estimate the UE's location from these measurements are beyond the scope of this specification. + +In order to obtain uplink measurements, the TRPs need to know the characteristics of the SRS signal transmitted by the UE for the time period required to perform uplink measurement. These characteristics should be static over the periodic transmission of SRS during the uplink measurements. Hence, the LMF will indicate to the serving gNB the need to direct the UE to transmit SRS signals for uplink positioning. It is up to the serving gNB to make the final decision on resources to be assigned and to communicate this SRS configuration information back to the LMF so that LMF can forward the SRS configuration to the TRPs. The gNB may decide (e.g., in case no resources are available) to configure no resources for the UE and report the empty resource configuration to the LMF. + +NOTE: UL-TDOA positioning with aperiodic or semi-persistent SRS is not supported for a U2N Remote UE. + +## 8.13.2 Information to be transferred between NG-RAN/5GC Elements + +This clause defines the information that may be transferred between LMF and gNB/TRPs. + +### 8.13.2.0 Assistance Data that may be transferred from the gNB to the LMF + +The assistance data that may be transferred from the gNB to the LMF is listed in Table 8.13.2.0-1. + +**Table 8.13.2.0-1: Assistance data that may be transferred from gNB to the LMF** + +| Information | +|--------------------------------------------------------------------------------------------| +| PCI, GCI, and TRP IDs of the TRPs served by the gNB | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | +| Geographical coordinates information of the DL-PRS Resources of the TRPs served by the gNB | +| TRP type | + +### 8.13.2.1 Configuration Data that may be transferred from the gNB to the LMF + +The configuration data for a target UE that may be transferred from the serving gNB to the LMF is listed in Table 8.13.2.1-1. + +**Table 8.13.2.1-1: UE configuration data that may be transferred from serving gNB to the LMF** + +| UE configuration data | +|-------------------------------------------------------------------------| +| UE SRS configuration | +| Timing information of the TRP, which configured the UE SRS transmission | +| The association information of SRS resources with UE Tx TEG ID | +| SRS Transmission Status | + +### 8.13.2.2 Location Information that may be transferred from the gNBs to LMF + +The information that may be transferred from gNBs to the LMF include measurement results listed in Table 8.13.2.2-1. The individual measurements are defined in TS 38.215 [37]. + +**Table 8.13.2.2-1: Measurement results that may be transferred from gNBs to the LMF** + +| Measurement results | +|---------------------------------------------------------------------------| +| NCGI and TRP ID of the measurement | +| UL-RTOA | +| UL-SRS-RSRP | +| UL-SRS-RSRPP | +| UL-RSCP measurement | +| UL Angle of Arrival (azimuth and/or elevation) NOTE 1 | +| Multiple UL Angle of Arrival (azimuth and/or elevation) NOTE 1 | +| SRS Resource Type | +| Time stamp of the measurement | +| Quality for each measurement | +| Beam Information for each measurement | +| LoS/NLoS information for each measurement | +| ARP ID of the measurement | +| NOTE 1: When used with UL-AoA for hybrid positioning. | + +### 8.13.2.3 Information that may be transferred from the LMF to gNBs + +The requested UL-SRS transmission characteristics information that may be signalled from the LMF to the gNB is listed in Table 8.13.2.3-1. + +**Table 8.13.2.3-1: Requested UL-SRS transmission characteristics information that may be transferred from LMF to gNB.** + +| Information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number Of Transmissions/duration for which the UL-SRS is requested | +| Bandwidth | +| Resource type (periodic, semi-persistent, aperiodic) | +| Pathloss reference:
  • - PCI, SSB Index, SSB configuration (time/frequency occupancy of SSBs)
  • - DL-PRS ID, DL-PRS Resource Set ID, DL-PRS Resource ID
| +| Spatial relation info
  • - PCI, SSB Index, SSB configuration (time/frequency occupancy of SSBs)
  • - DL-PRS ID, DL-PRS Resource Set ID, DL-PRS Resource ID
  • - NZP CSI-RS Resource ID
  • - SRS Resource ID
  • - Positioning SRS Resource ID
| +| SSB Information | +| Periodicity of the SRS for each SRS resource set | +| Carrier frequency of SRS transmission bandwidth | + +The TRP measurement request information that may be signalled from the LMF to the gNB is listed in table 8.13.2.3-2. + +**Table 8.13.2.3-2: TRP Measurement request information that may be transferred from LMF to gNB.** + +| Information | +|------------------------------------------------------------------------------------------------| +| TRP ID, cell ID of the TRP to receive UL-SRS | +| UE-SRS configuration | +| UL timing information together with timing uncertainty, for reception of SRS by candidate TRPs | +| Report characteristics for the measurements | +| Measurement Quantities | +| Measurement periodicity | +| Measurement beam information request | +| Search window information | +| Expected UL AoA/ZoA and uncertainty range | +| Number of TRP Rx TEGs | +| Response time | +| Measurement characteristics request indicator | +| Measurement time occasions for a measurement instance | + +The Positioning Activation/Deactivation request information that may be signalled from the LMF to the gNB is listed in Table 8.13.2.3-3. + +**Table 8.13.2.3-3: Requested positioning activation/deactivation information that may be transferred from LMF to gNB.** + +| Information | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SP UL-SRS:
  • - Activation or Deactivation request
  • - Positioning SRS Resource Set ID which is to be activated/deactivated
  • - Spatial relation for Resource IDi
  • - Activation Time
| +| Aperiodic UL-SRS:
  • - Aperiodic SRS Resource Trigger List
  • - Activation time
| +| UL-SRS:
  • - Release all
| + +### 8.13.3 UL-TDOA Positioning Procedures + +#### 8.13.3.0 General + +The procedures described in this clause support UL-TDOA positioning measurements obtained by the gNB and provided to the LMF using NRPPa. + +#### 8.13.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for UL-TDOA positioning is described in clause 7.1.2.1. + +#### 8.13.3.2 Assistance Data Transfer Procedure + +##### 8.13.3.2.1 Assistance Data Delivery between LMF and gNB + +The purpose of these procedures is to enable the gNB to provide assistance data described in Table 8.13.2.0-1 to the LMF, for subsequent delivery to the gNB using the procedures of clause 8.13.3.3 or for use in the calculation of positioning estimates at the LMF or enable the LMF to request UL-SRS configuration information from the serving gNB of a target UE. + +Figure 8.13.3.2.1-1 shows the UL information Delivery operation from the serving gNB to the LMF. + +![Sequence diagram of LMF-initiated UL Information Request Procedure](4c4c756d9c3797fc23d861bc37d2d63d_img.jpg) + +``` +sequenceDiagram + participant LMF + participant gNB + Note left of LMF: LMF-initiated UL Information Request Procedure + LMF->>gNB: 1. NRPPa Message (Type: POSITIONING INFORMATION REQUEST) + gNB-->>LMF: 2. NRPPa Message (Type: POSITIONING INFORMATION RESPONSE/FAILURE) + gNB->>LMF: 3. NRPPa Message (Type: POSITIONING INFORMATION UPDATE) +``` + +The diagram illustrates the interaction between the LMF and the gNB for the UL information request procedure. It consists of three steps: 1. The LMF sends a NRPPa Message (Type: POSITIONING INFORMATION REQUEST) to the gNB. 2. The gNB responds with a NRPPa Message (Type: POSITIONING INFORMATION RESPONSE/FAILURE). 3. The gNB sends a NRPPa Message (Type: POSITIONING INFORMATION UPDATE) to the LMF. + +Sequence diagram of LMF-initiated UL Information Request Procedure + +**Figure 8.13.3.2.1-1: LMF-initiated UL Information Request Procedure** + +- (1) The LMF sends a NRPPa message POSITIONING INFORMATION REQUEST to the serving gNB of the target UE to request UE SRS configuration information. If the message includes the Requested UL-SRS Transmission Characteristics as listed in Table 8.13.2.3-1, the gNB should take this information into account when configuring UL-SRS transmissions for the UE. +- (2) The serving gNB determines the UE SRS configuration to be allocated for the UE and sends NRPPa message POSITIONING INFORMATION RESPONSE to the LMF that includes the UE SRS configuration defined in Table 8.13.2.1-1. If the serving gNB is not able to provide the requested information, it returns a failure message indicating the cause of the failure. +- (3) If a change has occurred in the UE SRS configuration during the UE SRS time duration requested at step 1, the gNB sends a POSITIONING INFORMATION UPDATE message to the LMF. This message contains, in the case of a change in UE SRS configuration parameters, the UE SRS configuration information for all cells with UE SRS configured, or an update in SRS transmission status. + +Figure 8.13.3.2.1-2 shows the TRP Information Exchange operation from the gNB to the LMF for the UL-TDOA positioning method. + +![Sequence diagram for LMF-initiated TRP Information Exchange Procedure between LMF and gNB.](b55cd9b5721bd8aabc979c85316924e4_img.jpg) + +This sequence diagram illustrates the LMF-initiated TRP Information Exchange Procedure. It features two vertical lifelines: 'LMF' on the left and 'gNB' on the right. The interaction begins with a solid arrow pointing from the LMF to the gNB, labeled 'NRPPa TRP INFORMATION REQUEST'. The gNB responds with a solid arrow pointing back to the LMF, labeled 'NRPPa TRP INFORMATION RESPONSE'. Below these, a dashed arrow points from the LMF to the gNB, labeled 'NRPPa TRP INFORMATION REQUEST', and the gNB replies with a dashed arrow pointing back to the LMF, labeled 'NRPPa TRP INFORMATION RESPONSE'. + +Sequence diagram for LMF-initiated TRP Information Exchange Procedure between LMF and gNB. + +**Figure 8.13.3.2.1-2: LMF-initiated TRP Information Exchange Procedure** + +- (1) The LMF determines that certain TRP configuration information is desired (e.g., as part of a periodic update or as triggered by OAM) and sends an NRPPa TRP INFORMATION REQUEST message to the gNB. This request includes an indication of which specific TRP configuration information is requested. +- (2) The gNB provides the requested TRP information in an NRPPa TRP INFORMATION RESPONSE message, if available at the gNB. If the gNB is not able to provide any information, it returns an TRP INFORMATION FAILURE message indicating the cause of the failure. + +**8.13.3.3 Location Information Transfer/Assistance Data Transfer Procedure** + +The purpose of this procedure is to enable the LMF to request position measurements from a gNB for position calculation of the UE and also provide necessary assistance data to the gNB. + +Figure 8.13.3.3-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure between LMF and gNB.](a1d3229d6f5d31aceed45f2a88917e4c_img.jpg) + +This sequence diagram illustrates the LMF-initiated Location Information Transfer Procedure. It features two vertical lifelines: 'LMF' on the left and 'gNB' on the right. The interaction consists of a series of messages: 1) A solid arrow from LMF to gNB labeled 'NRPPa LOCATION INFORMATION REQUEST'. 2) A solid arrow from gNB to LMF labeled 'NRPPa LOCATION INFORMATION RESPONSE'. 3) A solid arrow from LMF to gNB labeled 'NRPPa ASSISTANCE DATA'. 4) A solid arrow from gNB to LMF labeled 'NRPPa ASSISTANCE DATA RESPONSE'. 5) A vertical ellipsis indicating additional message exchanges. 6) A solid arrow from LMF to gNB labeled 'NRPPa LOCATION INFORMATION REQUEST'. 7) A solid arrow from gNB to LMF labeled 'NRPPa LOCATION INFORMATION RESPONSE'. 8) A solid arrow from LMF to gNB labeled 'NRPPa ASSISTANCE DATA'. 9) A solid arrow from gNB to LMF labeled 'NRPPa ASSISTANCE DATA RESPONSE'. + +Sequence diagram for LMF-initiated Location Information Transfer Procedure between LMF and gNB. + +**Figure 8.13.3.3-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a NRPPa message to the selected gNB to request UL-TDOA measurement information. The message includes any information required for the gNB to perform the measurements as defined in Table 8.13.2.3-2. +- (2) If the report characteristics in step 1 is set to "on demand", the gNB obtains the requested UL-TDOA measurements and returns them in a Measurement Response message to the LMF. The Measurement Response message includes the obtained UL-TDOA measurements as defined in Table 8.13.2.2-1. + +If the report characteristics in step 1 is set to "periodic", the gNB replies with a Measurement Response message without including any measurements in the message. The gNB then periodically initiates the Measurement Report procedure in step 3 for the UL-TDOA measurements, with the requested reporting periodicity. + +If the gNB is not able to accept the Measurement Request message in step 1, the gNB returns a failure message indicating the cause of the failure. + +- (3) The gNB periodically provides the UL-TDOA measurements as defined in Table 8.13.2.2-1 to the LMF if that was requested at step 1. +- (4) At any time after step 2, the LMF may send a Measurement Update message to the gNB providing updated information required for the gNB to perform the UL-TDOA measurements as defined in Table 8.13.2.3-2. Upon receiving the message, the gNB overwrites the previously received measurement configuration information. +- (5) If the previously requested UL-TDOA measurements can no longer be reported, the gNB notifies the LMF by sending a Measurement Failure Indication message. +- (6) When the LMF wants to abort an ongoing UL-TDOA measurement it sends a Measurement Abort message to the gNB. + +### 8.13.3.3a Positioning Activation/Deactivation Procedure + +The purpose of this procedure is to enable the LMF to request activation and deactivation of UL-SRS transmission of the target UE. + +Figure 8.13.3.3a-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram for Positioning Activation/Deactivation Procedure. It shows two vertical lifelines representing the LMF (left) and the gNB (right). The sequence of messages is: 1. A solid arrow points from the LMF to the gNB. 2. A solid arrow points from the gNB to the LMF. 3. A solid arrow points from the LMF to the gNB. 4. A solid arrow points from the gNB to the LMF.](b6098e84ba6261a5152f5a4fa790c579_img.jpg) + +Sequence diagram for Positioning Activation/Deactivation Procedure. It shows two vertical lifelines representing the LMF (left) and the gNB (right). The sequence of messages is: 1. A solid arrow points from the LMF to the gNB. 2. A solid arrow points from the gNB to the LMF. 3. A solid arrow points from the LMF to the gNB. 4. A solid arrow points from the gNB to the LMF. + +**Figure 8.13.3.3a-1: Positioning Activation/Deactivation Procedure.** + +- (1) The LMF sends the NRPPa Positioning Activation Request message to the serving gNB of the target UE to request UL-SRS activation for the target UE. For a semi-persistent UL-SRS, the message includes an indication of an UL-SRS resource set to be activated and may include information that indicates the spatial relation for the semi-persistent UL-SRS resource to be activated, as listed in Table 8.13.2.3-3. For an aperiodic UL-SRS, the message may include aperiodic SRS Resource trigger list to indicate the UL-SRS resource to be activated. +- (2) For semi-persistent UL-SRS, the serving gNB may then activate the configured semi-persistent UL-SRS resource sets by sending the SP Positioning SRS Activation/Deactivation MAC CE command as specified in TS + +38.321 [39]. For aperiodic UL-SRS, the serving gNB may then activate the configured aperiodic UL-SRS resource sets by sending the DCI as specified in TS 38.212 [40]. + +If the UL-SRS has been successfully activated as requested in step 1, the gNB sends the NRPPa Positioning Activation Response message to the LMF. If the serving gNB is not able to fulfil the request from step 1, it returns the Positioning Activation Failure message indicating the cause of the failure. The serving gNB may include a system frame number and a slot number in the NRPPa Positioning Activation Response message to the LMF. + +- (3) If a previously activated UL-SRS should be deactivated, or the UL-SRS transmission should be released, the LMF sends the NRPPa Positioning Deactivation message to the serving gNB of the target device to request deactivation of UL-SRS resource sets, or release all the UL-SRS resources. This message includes an indication of the UL-SRS resource set to be deactivated, or an indication of releasing all UL-SRS resources. + +### 8.13.3.4 Sequence of Procedure for UL-TDOA positioning + +Figure 8.13.3.4-1 shows the messaging between the LMF, the gNBs and the UE to perform UL-TDOA procedure. + +![Sequence diagram of the UL-TDOA positioning procedure. The diagram shows interactions between a UE, a Serving gNB/TRP, multiple Neighbour gNB/TRPs, and an LMF. The steps are: 0. NRPPa TRP Configuration Information Exchange (between LMF and Neighbour gNBs); 1. LPP Capability Transfer (between LMF and UE); 2. NRPPa POSITIONING INFORMATION REQUEST (from LMF to Serving gNB); 3. gNB determines UL SRS Resources (internal to Serving gNB); 3a. UE SRS configuration (from Serving gNB to UE); 4. NRPPa POSITIONING INFORMATION RESPONSE (from Serving gNB to LMF); 5a. NRPPa POSITIONING ACTIVATION REQUEST (from LMF to Serving gNB); 5b. Activate UE SRS transmission (from Serving gNB to UE); 5c. NRPPa POSITIONING ACTIVATION RESPONSE (from Serving gNB to LMF); 6. NRPPa MEASUREMENT REQUEST (from LMF to Neighbour gNBs); 7. UL SRS Measurements (internal to Neighbour gNBs); 8. NRPPa MEASUREMENT RESPONSE (from Neighbour gNBs to LMF); 9. NRPPa POSITIONING DEACTIVATION (from LMF to Serving gNB).](7ec3b8a4d03079ca7c2dfaa2cbc54a9c_img.jpg) + +Sequence diagram of the UL-TDOA positioning procedure. The diagram shows interactions between a UE, a Serving gNB/TRP, multiple Neighbour gNB/TRPs, and an LMF. The steps are: 0. NRPPa TRP Configuration Information Exchange (between LMF and Neighbour gNBs); 1. LPP Capability Transfer (between LMF and UE); 2. NRPPa POSITIONING INFORMATION REQUEST (from LMF to Serving gNB); 3. gNB determines UL SRS Resources (internal to Serving gNB); 3a. UE SRS configuration (from Serving gNB to UE); 4. NRPPa POSITIONING INFORMATION RESPONSE (from Serving gNB to LMF); 5a. NRPPa POSITIONING ACTIVATION REQUEST (from LMF to Serving gNB); 5b. Activate UE SRS transmission (from Serving gNB to UE); 5c. NRPPa POSITIONING ACTIVATION RESPONSE (from Serving gNB to LMF); 6. NRPPa MEASUREMENT REQUEST (from LMF to Neighbour gNBs); 7. UL SRS Measurements (internal to Neighbour gNBs); 8. NRPPa MEASUREMENT RESPONSE (from Neighbour gNBs to LMF); 9. NRPPa POSITIONING DEACTIVATION (from LMF to Serving gNB). + +**Figure 8.13.3.4-1: UL-TDOA positioning procedure** + +0. The LMF may use the procedure in Figure 8.13.3.2.1-2 to obtain the TRP information required for UL-TDOA positioning. +1. The LMF may request the positioning capabilities of the target device using the LPP Capability Transfer procedure as described in clause 8.13.3.1. + +2. The LMF sends a NRPPa POSITIONING INFORMATION REQUEST message to the serving gNB to request UL-SRS configuration information for the target device as described in Figure 8.13.3.2.1-1. +3. The serving gNB determines the resources available for UL-SRS and configures the target device with the UL-SRS resource sets at step 3a. +4. The serving gNB provides the UL information to the LMF in a NRPPa POSITIONING INFORMATION RESPONSE message. +5. In the case of semi-persistent or aperiodic SRS, the LMF may request activation of UE SRS transmission by sending the NRPPa Positioning Activation Request message to the serving gNB of the target device as described in clause 8.13.3.3a. The gNB then activates the UL-SRS transmission and sends the NRPPa Positioning Activation Response message. The target device begins the UL-SRS transmission according to the time domain behavior of UL-SRS resource configuration. +6. The LMF provides the UL-SRS configuration to the selected gNBs in a NRPPa MEASUREMENT REQUEST message as described in clause 8.13.3.3. The message includes all information required to enable the gNBs/TRPs to perform the UL measurements. +7. Each gNB configured at step 6 measures the UL-SRS transmissions from the target device. +8. Each gNB reports the UL-SRS measurements to the LMF in a NRPPa Measurement Response message as described in clause 8.13.3.3. +9. The LMF sends a NRPPa POSITIONING DEACTIVATION message to the serving gNB as described in clause 8.13.3.3a. + +## 8.14 UL-AoA positioning + +### 8.14.1 General + +In the UL-AoA positioning method, the UE position is estimated based on UL-AoA (and optionally UL-SRS-RSRP and/or UL-SRS-RSRPP) of uplink radio signals taken at different TRPs, along with other configuration information. + +The specific of any UL-AoA positioning methods or techniques used to estimate the UE's location from these measurements are beyond the scope of this specification. + +In order to obtain uplink measurements, the TRPs need to know the characteristics of the SRS signal transmitted by the UE for the time period required to calculate uplink measurement. These characteristics should be static over the periodic transmission of SRS during the uplink measurements. Hence, the LMF will indicate to the serving gNB the need to direct the UE to transmit SRS signals for uplink positioning. It is up to the gNB to make the final decision on resources to be assigned and to communicate this configuration information back to the LMF so that LMF can configure the TRPs. The gNB may decide (e.g., in case no resources are available) to configure no resources for the UE and fail the corresponding NRPPa procedure. + +NOTE: UL-AoA positioning with aperiodic or semi-persistent SRS is not supported for a U2N Remote UE. + +### 8.14.2 Information to be transferred between NG-RAN/5GC Elements + +This clause defines the information that may be transferred between LMF and gNB/TRPs. + +#### 8.14.2.0 Assistance Data that may be transferred from the gNB to the LMF + +The assistance data that may be transferred from the gNB to the LMF is listed in Table 8.14.2.0-1. + +**Table 8.14.2.0-1: Assistance data that may be transferred from gNB to the LMF** + +| Information | +|--------------------------------------------------------------------------------------------| +| PCI, GCI, and TRP IDs of the TRPs served by the gNB | +| SSB information of the TRPs (the time/frequency occupancy of SSBs) | +| Geographical coordinates information of the DL-PRS Resources of the TRPs served by the gNB | +| TRP type | + +#### 8.14.2.1 Configuration Data that may be transferred from the gNB to the LMF + +The configuration data for a target UE that may be transferred from the serving gNB to the LMF is listed in Table 8.14.2.1-1. + +**Table 8.14.2.1-1: UE configuration data that may be transferred from serving gNB to the LMF** + +| UE configuration data | +|-------------------------------------------------------------------------| +| UE SRS configuration | +| Timing information of the TRP, which configured the UE SRS transmission | +| SRS Transmission Status | + +#### 8.14.2.2 Location Information that may be transferred from the gNBs to LMF + +The information that may be transferred from gNBs to the LMF include measurement results are listed in Table 8.14.2.2-1. The individual measurements are defined in TS 38.215 [37]. + +**Table 8.14.2.2-1: Measurement results that may be transferred from gNBs to the LMF** + +| Measurement results | +|---------------------------------------------------------| +| NCGI and TRP ID of the measurement | +| UL Angle of Arrival (azimuth and/or elevation) | +| Multiple UL Angle of Arrival (azimuth and/or elevation) | +| SRS Resource Type | +| UL-SRS-RSRP | +| UL-SRS-RSRPP | +| Time stamp of the measurement | +| Quality for each measurement | +| Beam information for each measurement | +| LoS/NLoS information for each measurement | +| ARP ID of the measurement | + +#### 8.14.2.3 Information that may be transferred from the LMF to gNB + +The requested UL-SRS transmission characteristics information that may be signalled from the LMF to the gNB is listed in Table 8.14.2.3-1. + +**Table 8.14.2.3-1: Requested UL-SRS transmission characteristics information that may be transferred from LMF to gNB.** + +| Information | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number Of Transmissions/duration for which the UL-SRS is requested | +| Bandwidth | +| Resource type (periodic, semi-persistent, aperiodic) | +| Number of requested SRS resource sets and SRS resources per set | +| Pathloss reference:
- PCI, SSB Index, SSB configuration (time/frequency occupancy of SSBs)
- DL-PRS ID, DL-PRS Resource Set ID, DL-PRS Resource ID | +| Spatial relation info
- PCI, SSB Index, SSB configuration (time/frequency occupancy of SSBs)
- DL-PRS ID, DL-PRS Resource Set ID, DL-PRS Resource ID
- NZP CSI-RS Resource ID
- SRS Resource ID
- Positioning SRS Resource ID | +| SSB Information | +| Periodicity of the SRS for each SRS resource set | +| Carrier frequency of SRS transmission bandwidth | + +The TRP measurement request information that may be signalled from the LMF to the gNB is listed in table 8.14.2.3-2. + +**Table 8.14.2.3-2: TRP Measurement request information that may be transferred from LMF to gNB.** + +| Information | +|------------------------------------------------------------------------------------------------| +| TRP ID, cell ID of the TRP to receive UL-SRS | +| UE-SRS configuration | +| UL timing information together with timing uncertainty, for reception of SRS by candidate TRPs | +| Report characteristics for the measurements | +| Measurement Quantities | +| Measurement periodicity | +| Measurement beam information request | +| Expected UL AoA/ZoA and uncertainty range | +| Response time | +| Measurement characteristics request indicator | +| Measurement time occasions for a measurement instance | + +The Positioning Activation/Deactivation request information that may be signalled from the LMF to the gNB is listed in Table 8.14.2.3-3. + +**Table 8.14.2.3-3: Requested positioning activation/deactivation information that may be transferred from LMF to gNB.** + +| Information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SP UL-SRS:
- Activation or Deactivation request
- Positioning SRS Resource Set ID which is to be activated/deactivated
- Spatial relation for Resource ID i
- Activation Time | +| Aperiodic UL-SRS:
- Aperiodic SRS Resource Trigger list
- Activation time | +| UL-SRS:
- Release all | + +## 8.14.3 UL-AoA Positioning Procedures + +### 8.14.3.0 General + +The procedures described in this clause support UL-AoA positioning measurements obtained by the gNB and provided to the LMF using NRPPa. + +### 8.14.3.1 Capability Transfer Procedure + +The Capability Transfer procedure for UL-AoA positioning is described in clause 7.1.2.1. + +### 8.14.3.2 Assistance Data Transfer Procedure + +#### 8.14.3.2.1 Assistance Data Delivery between LMF and gNB + +The purpose of these procedures is to enable the gNB to provide assistance data described in Table 8.14.2.0-1 to the LMF, for subsequent delivery to the gNB using the procedures of clause 8.14.3.3 or for use in the calculation of positioning estimates at the LMF or enable the LMF to request UL-SRS configuration information from the serving gNB of a target UE. + +Figure 8.14.3.2.1-1 shows the UL information Delivery operation from the serving gNB to the LMF. + +![Sequence diagram of LMF-initiated UL Information Request Procedure](a626c4e5f38f8e361cd07c9f73405cc8_img.jpg) + +``` +sequenceDiagram + participant LMF + participant gNB + Note left of LMF: LMF-initiated UL Information Request Procedure + LMF->>gNB: 1. NRPPa Message (Type: POSITIONING INFORMATION REQUEST) + gNB-->>LMF: 2. NRPPa Message (Type: POSITIONING INFORMATION RESPONSE/FAILURE) + gNB->>LMF: 3. NRPPa Message (Type: POSITIONING INFORMATION UPDATE) +``` + +The diagram illustrates a sequence of three messages between the LMF and the gNB. The LMF sends a 'NRPPa Message (Type: POSITIONING INFORMATION REQUEST)' to the gNB. The gNB responds with a 'NRPPa Message (Type: POSITIONING INFORMATION RESPONSE/FAILURE)'. Finally, the gNB sends a 'NRPPa Message (Type: POSITIONING INFORMATION UPDATE)' to the LMF. + +Sequence diagram of LMF-initiated UL Information Request Procedure + +**Figure 8.14.3.2.1-1: LMF-initiated UL Information Request Procedure** + +- (1) The LMF sends a NRPPa message POSITIONING INFORMATION REQUEST to the serving gNB of the target UE to request UE SRS configuration information. If the message includes the Requested UL-SRS Transmission Characteristics as listed in Table 8.14.2.3-1, the gNB should take this information into account when configuring UL-SRS transmissions for the UE. +- (2) The serving gNB determines the UE SRS configuration to be allocated for the UE and sends NRPPa message POSITIONING INFORMATION RESPONSE to the LMF that includes the UE SRS configuration defined in Table 8.14.2.1-1. If the serving gNB is not able to provide the requested information, it returns a failure message indicating the cause of the failure. +- (3) If a change has occurred in the UE SRS configuration during the UE SRS time duration requested at step 1, the gNB sends a POSITIONING INFORMATION UPDATE message to the LMF. This message contains, in the case of a change in UE SRS configuration parameters, the UE SRS configuration information for all cells with UE SRS configured, or an update in SRS transmission status. + +Figure 8.14.3.2.1-2 shows the TRP Information Exchange operation from the gNB to the LMF for the UL-AoA positioning method. + +![Sequence diagram for LMF-initiated TRP Information Exchange Procedure between LMF and gNB.](c15cb6383bc35906e6b3c7c3aac621ed_img.jpg) + +This sequence diagram illustrates the LMF-initiated TRP Information Exchange Procedure. It features two vertical lifelines: LMF on the left and gNB on the right. The interaction begins with a solid arrow pointing from the gNB to the LMF, labeled 'NRPPa TRP INFORMATION REQUEST'. This is followed by a dashed arrow pointing from the LMF to the gNB, labeled 'NRPPa TRP INFORMATION RESPONSE'. The diagram is minimalist, showing only the two main participants and the two messages exchanged between them. + +Sequence diagram for LMF-initiated TRP Information Exchange Procedure between LMF and gNB. + +**Figure 8.14.3.2.1-2: LMF-initiated TRP Information Exchange Procedure** + +- (1) The LMF determines that certain TRP configuration information is desired (e.g., as part of a periodic update or as triggered by OAM) and sends an NRPPa TRP INFORMATION REQUEST message to the gNB. This request includes an indication of which specific TRP configuration information is requested. +- (2) The gNB provides the requested TRP information in an NRPPa TRP INFORMATION RESPONSE message, if available at the gNB. If the gNB is not able to provide any information, it returns an TRP INFORMATION FAILURE message indicating the cause of the failure. + +**8.14.3.3 Location Information Transfer/Assistance Data Transfer Procedure** + +The purpose of this procedure is to enable the LMF to request position measurements from a gNB for position calculation of the UE and also provide necessary assistance data to the gNB. + +Figure 8.14.3.3-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram for LMF-initiated Location Information Transfer Procedure between LMF and gNB.](131048f570c4d9960a21e7dd73c4fd6b_img.jpg) + +This sequence diagram illustrates the LMF-initiated Location Information Transfer Procedure. It features two vertical lifelines: LMF on the left and gNB on the right. The interaction consists of a series of messages: 1) A solid arrow from gNB to LMF labeled 'NRPPa REQUEST'. 2) A dashed arrow from LMF to gNB labeled 'NRPPa RESPONSE'. 3) A solid arrow from gNB to LMF labeled 'NRPPa REQUEST'. 4) A dashed arrow from LMF to gNB labeled 'NRPPa RESPONSE'. 5) A vertical ellipsis indicating additional message exchanges. 6) A solid arrow from gNB to LMF labeled 'NRPPa REQUEST'. 7) A dashed arrow from LMF to gNB labeled 'NRPPa RESPONSE'. The diagram shows a repetitive pattern of request and response messages between the two entities. + +Sequence diagram for LMF-initiated Location Information Transfer Procedure between LMF and gNB. + +**Figure 8.14.3.3-1: LMF-initiated Location Information Transfer Procedure** + +- (1) The LMF sends a NRPPa message to the selected gNB to request UL-AoA measurement information. The message includes any information required for the gNB to perform the measurements as defined in Table 8.14.2.3-2. +- (2) If the report characteristics in step 1 is set to "on demand", the gNB obtains the requested UL-AoA measurements and returns them in a Measurement Response message to the LMF. The Measurement Response message includes the obtained UL-AoA measurements as defined in Table 8.14.2.2-1. + +If the report characteristics in step 1 is set to "periodic", the gNB replies with a Measurement Response message without including any measurements in the message. The gNB then periodically initiates the Measurement Report procedure in step 3 for the UL-AoA measurements, with the requested reporting periodicity. + +If the gNB is not able to accept the Measurement Request message in step 1, the gNB returns a failure message indicating the cause of the failure. + +- (3) The gNB periodically provides the UL-AoA measurements as defined in Table 8.14.2.2-1 to the LMF if that was requested at step 1. +- (4) At any time after step 2, the LMF may send a Measurement Update message to the gNB providing updated information required for the gNB to perform the UL-AoA measurements as defined in Table 8.14.2.3-2. Upon receiving the message, the gNB overwrites the previously received measurement configuration information. +- (5) If the previously requested UL-AoA measurements can no longer be reported, the gNB notifies the LMF by sending a Measurement Failure Indication message. +- (6) When the LMF wants to abort an ongoing UL-AoA measurement it sends a Measurement Abort message to the gNB. + +### 8.14.3.3a Positioning Activation/Deactivation Procedure + +The purpose of this procedure is to enable the LMF to request activation and deactivation of UL-SRS transmission of the target UE. + +Figure 8.14.3.3a-1 shows the messaging between the LMF and the gNB to perform this procedure. + +![Sequence diagram for Positioning Activation/Deactivation Procedure. It shows two vertical lifelines. The first lifeline (left) has a box at the top and a downward arrow pointing to the second lifeline. The second lifeline (right) has a box at the top and a downward arrow pointing to the first lifeline. This represents a request from the first lifeline to the second, and a response from the second to the first.](35361e547fa02f04752bf841677e42b1_img.jpg) + +``` +sequenceDiagram + participant LMF + participant gNB + Note left of LMF: LMF sends NRPPa Positioning Activation Request + LMF->>gNB: NRPPa Positioning Activation Request + Note right of gNB: gNB activates semi-persistent UL-SRS + gNB-->>LMF: SP Positioning SRS Activation/Deactivation MAC CE +``` + +Sequence diagram for Positioning Activation/Deactivation Procedure. It shows two vertical lifelines. The first lifeline (left) has a box at the top and a downward arrow pointing to the second lifeline. The second lifeline (right) has a box at the top and a downward arrow pointing to the first lifeline. This represents a request from the first lifeline to the second, and a response from the second to the first. + +**Figure 8.14.3.3a-1: Positioning Activation/Deactivation Procedure.** + +- (1) The LMF sends the NRPPa Positioning Activation Request message to the serving gNB of the target UE to request UL-SRS activation for the target UE. For a semi-persistent UL-SRS, the message includes an indication of an UL-SRS resource set to be activated and may include information that indicates the spatial relation for the semi-persistent UL-SRS resource to be activated, as listed in Table 8.14.2.3-3. For an aperiodic UL-SRS, the message may include aperiodic SRS Resource trigger list to indicate the UL-SRS resource to be activated. +- (2) For semi-persistent UL-SRS, the serving gNB may then activate the configured semi-persistent UL-SRS resource sets by sending the SP Positioning SRS Activation/Deactivation MAC CE command as specified in TS + +38.321 [39]. For aperiodic UL-SRS, the serving gNB may then activate the configured aperiodic UL-SRS resource sets by sending the DCI as specified in TS 38.212 [40]. + +If the UL-SRS has been successfully activated as requested in step 1, the gNB sends the NRPPa Positioning Activation Response message to the LMF. If the serving gNB is not able to fulfil the request from step 1, it returns the Positioning Activation Failure message indicating the cause of the failure. The serving gNB includes a system frame number and a slot number in the NRPPa Positioning Activation Response message to the LMF. + +- (3) If a previously activated UL-SRS should be deactivated, or the UL-SRS transmission should be released, the LMF sends the NRPPa Positioning Deactivation message to the serving gNB of the target device to request deactivation of UL-SRS resource sets, or release all the UL-SRS resources. This message includes an indication of the UL-SRS resource set to be deactivated, or an indication of releasing all UL-SRS resources. + +#### 8.14.3.4 Sequence of Procedure for UL-AoA positioning + +Figure 8.14.3.4-1 shows the messaging between the LMF, the gNBs and the UE to perform UL-AoA procedure. + +![Sequence diagram of UL-AoA positioning procedure showing interactions between UE, Serving gNB/TRP, Neighbour gNB/TRPs, and LMF.](ae56c99bae77ca28d053b978909e1936_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Serving as Serving gNB/TRP + participant Neighbour as Neighbour gNB/TRPs + participant LMF + + Note right of Serving: 0. NRPPa TRP Configuration Information Exchange + Note right of Serving: 1. LPP Capability Transfer + LMF->>Serving: 2. NRPPa POSITIONING INFORMATION REQUEST + Note left of Serving: 3. gNB determines UL SRS Resources + Serving->>UE: 3a. UE SRS configuration + Serving->>LMF: 4. NRPPa POSITIONING INFORMATION RESPONSE + LMF->>Serving: 5a. NRPPa POSITIONING ACTIVATION REQUEST + Serving->>UE: 5b. Activate UE SRS transmission + Serving->>LMF: 5c. NRPPa POSITIONING ACTIVATION RESPONSE + Note right of Serving: 6. NRPPa MEASUREMENT REQUEST + Note right of Neighbour: 7. UL SRS Measurements + Note right of Serving: 8. NRPPa MEASUREMENT RESPONSE + LMF->>Serving: 9. NRPPa POSITIONING DEACTIVATION + +``` + +The diagram illustrates the sequence of messages for UL-AoA positioning. It starts with the LMF sending an NRPPa POSITIONING INFORMATION REQUEST (step 2) to the Serving gNB/TRP. The Serving gNB/TRP determines UL SRS Resources (step 3) and sends a UE SRS configuration (step 3a) to the UE. The Serving gNB/TRP then sends an NRPPa POSITIONING INFORMATION RESPONSE (step 4) to the LMF. The LMF sends an NRPPa POSITIONING ACTIVATION REQUEST (step 5a) to the Serving gNB/TRP, which activates UE SRS transmission (step 5b) and sends an NRPPa POSITIONING ACTIVATION RESPONSE (step 5c) to the LMF. The Serving gNB/TRP sends an NRPPa MEASUREMENT REQUEST (step 6) to the Neighbour gNB/TRPs, which perform UL SRS Measurements (step 7) and send an NRPPa MEASUREMENT RESPONSE (step 8) to the LMF. Finally, the LMF sends an NRPPa POSITIONING DEACTIVATION (step 9) to the Serving gNB/TRP. + +Sequence diagram of UL-AoA positioning procedure showing interactions between UE, Serving gNB/TRP, Neighbour gNB/TRPs, and LMF. + +Figure 8.14.3.4-1: UL-AoA positioning procedure + +0. The LMF may use the procedure in Figure 8.14.3.2.1-2 to obtain the TRP information required for UL-AoA positioning. +1. The LMF may request the positioning capabilities of the target device using the LPP Capability Transfer procedure as described in clause 8.14.3.1. +2. The LMF sends a NRPPa POSITIONING INFORMATION REQUEST message to the serving gNB to request UL-SRS configuration information for the target device as described in Figure 8.14.3.2.1-1. + +3. The serving gNB determines the resources available for UL-SRS and configures the target device with the UL-SRS resource sets at step 3a. +4. The serving gNB provides the UL-SRS configuration information to the LMF in a NRPPa POSITIONING INFORMATION RESPONSE message. +5. In the case of semi-persistent or aperiodic SRS, the LMF may request activation of UE SRS transmission by sending the NRPPa Positioning Activation Request message to the serving gNB of the target device as described in clause 8.14.3.3a. The gNB then activates the UL-SRS transmission and sends the NRPPa Positioning Activation Response message. The target device begins the UL-SRS transmission according to the time domain behavior of UL-SRS resource configuration. +6. The LMF provides the UL-SRS configuration to the selected gNBs in a NRPPa MEASUREMENT REQUEST message as described in clause 8.14.3.3. The message includes all information required to enable the gNBs/TRPs to perform the UL measurements. +7. Each gNB configured at step 6 measures the UL-SRS transmissions from the target device. +8. Each gNB reports the UL-SRS measurements to the LMF in a NRPPa Measurement Response message as described in clause 8.14.3.3. +9. The LMF sends a NRPPa POSITIONING DEACTIVATION message to the serving gNB as described in clause 8.14.3.3a. + +## 8.15 SL positioning and ranging + +### 8.15.1 SL-PRS transmission and reception + +For SL positioning and ranging using SL-RTT, SL-AoA, SL-TDOA, and SL-TOA methods UEs need to transmit and/or receive SL-PRS as specified in TS 38.211 [50] over the NR PC5 interface. + +A UE can be configured with one or more sidelink resource pools via system information or dedicated signalling while inside NG-RAN coverage or pre-configuration while outside NG-RAN coverage as specified in TS 38.331 [14]. + +A sidelink resource pool which can be used for transmission of both, SL-PRS and SL data is referred to as SL-PRS shared resource pool. A sidelink resource pool which can be used for transmission of SL-PRS and cannot be used for transmission of SL data is referred to as SL-PRS dedicated resource pool. + +Two sidelink resource allocation schemes for SL-PRS are supported: scheme 1 and scheme 2. In scheme 1, the SL-PRS resource allocation is provided by the network. In scheme 2, the UE decides the SL-PRS transmission resources in the resource pool(s). + +- Scheme 1 resource allocation is characterized by: + - The UE needs to be RRC\_CONNECTED state in order to transmit SL-PRS; + - NG-RAN schedules transmission resources. +- Scheme 2 resource selection is characterized by: + - The UE can transmit SL-PRS when inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when outside NG-RAN coverage; + - the UE autonomously selects transmission resources from resource pool(s). + +### 8.15.2 SL-RTT positioning + +#### 8.15.2.1 General + +The SL-RTT positioning method makes use of SL Rx-Tx time difference measurements performed by a pair of UEs (e.g., target UE and anchor UE). Both UEs measure the Rx-Tx time difference using the SL-PRS transmitted/received + +by the pair of UEs. The SL Rx-Tx time difference measurements performed by a pair of UEs defines the RTT between the UEs, which can be converted into a range estimate between the pair of UEs. + +For SL-RTT, the pair of UEs may transmit and receive SL-PRS once (also referred to as "single-sided RTT") or multiple times (also referred to as "double-sided RTT"). A UE may report multiple SL Rx-Tx time difference measurements for the same SL-PRS transmission and up to 4 different SL-PRS receptions, or report multiple SL Rx-Tx time difference measurements for the same SL-PRS reception and up to 4 different SL-PRS transmissions, or both. + +## 8.15.2.2 SL-RTT positioning procedures + +### 8.15.2.2.1 Capability transfer procedure + +The capability transfer procedure for SL-RTT positioning is described in clause 7.11.2.1. + +### 8.15.2.2.2 Assistance Data transfer procedure + +Figure 8.15.2.2.2-1 shows the Assistance Data transfer operations for the SL-RTT positioning method. + +![Sequence diagram illustrating the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B (dashed line). Step 2: Endpoint B sends an SLPP Provide Assistance Data message to Endpoint A (solid line).](eb265f9639a96a8cf1dcdc1603ef0215_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: Step 1 + Endpoint A-->>Endpoint B: 1. SLPP Request Assistance Data + Note right of Endpoint B: Step 2 + Endpoint B-->>Endpoint A: 2. SLPP Provide Assistance Data + +``` + +Sequence diagram illustrating the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B (dashed line). Step 2: Endpoint B sends an SLPP Provide Assistance Data message to Endpoint A (solid line). + +**Figure 8.15.2.2.2-1: Assistance Data transfer procedure.** + +1. Endpoint A may determine that certain SL-RTT positioning assistance data are desired and sends an SLPP Request Assistance Data message to Endpoint B. This request includes an indication of which specific SL-RTT assistance data are requested. +2. If step 1 occurred, Endpoint B provides the requested assistance in an SLPP Provide Assistance Data message to Endpoint A, if available at Endpoint B. The assistance data that may be signalled are listed in Table 8.15.2.2.2-1. If any of the requested assistance data in step 1 are not provided in step 2, the Endpoint A shall assume that the requested assistance data are not supported, or currently not available at Endpoint B. If none of the requested assistance data in step 1 can be provided by Endpoint B, Endpoint B returns any information that can be provided in an SLPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. +If step 1 did not occur, Endpoint B determines that SL-RTT assistance data needs to be provided to Endpoint A (e.g., as part of a positioning procedure) and sends an SLPP Provide Assistance Data message to Endpoint A. + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Server UE or LMF. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Target UE or SL Server UE and Endpoint B may be a SL Anchor UE. + +NOTE 3: Dependent on the scenario, Endpoint A may be a SL-PRS transmitting (Tx) UE and Endpoint B may be a SL-PRS receiving (Rx) UE. + +**Table 8.15.2.2.2-1: Assistance data that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------| +| Application Layer ID, identifying a UE as defined in TS 23.287 [48] | +| SL-PRS Sequence ID as defined in TS 38.211 [50] | +| ARP ID, identifying an SL-PRS Tx ARP associated with a UE | +| Anchor UE location coordinates | +| SL-PRS Tx ARP location coordinates | + +**8.15.2.2.3 Location Information transfer procedure** + +Figure 8.15.2.2.3-1 shows the Location Information transfer operations for the SL-RTT positioning method. + +![Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Location Information message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Location Information message to Endpoint A. Step 3: Endpoint B sends another SLPP Provide Location Information message to Endpoint A.](52ee58fb61d595173f91db2bcbd18557_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Location Information + Endpoint A-->>Endpoint B: 1. SLPP Request Location Information + Note left of Endpoint B: 2. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 2. SLPP Provide Location Information + Note left of Endpoint B: 3. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 3. SLPP Provide Location Information + +``` + +Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Location Information message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Location Information message to Endpoint A. Step 3: Endpoint B sends another SLPP Provide Location Information message to Endpoint A. + +**Figure 8.15.2.2.3-1: Location Information transfer procedure.** + +1. Endpoint A may send an SLPP Request Location Information message to Endpoint B. This request includes an indication of SL-RTT measurements requested, including any needed measurement configuration information, and possibly a required response time as listed in Table 8.15.2.2.3-1. +2. If step 1 occurred, Endpoint B obtains the SL-RTT measurements as requested in step 1. Endpoint B then sends an SLPP Provide Location Information message to Endpoint A, before the Response Time (if provided in step 1) elapsed, and includes the obtained SL-RTT measurements as listed in Table 8.15.2.2.3-2. If Endpoint B is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, Endpoint B returns any information that can be provided in an SLPP message of type Provide Location Information which includes a cause indication for the not provided location information. If step 1 did not occur, Endpoint B may send an SLPP Provide Location Information message to Endpoint A. The SLPP Provide Location Information message may include any SL-RTT results already available at Endpoint B. +3. Optionally (e.g, if requested at step 1), Endpoint B may provide one or more additional SLPP Provide Location Information messages with SL-RTT measurements to Endpoint A (e.g., according to the periodic reporting criteria if received at step1). + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Anchor UE. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Server UE or LMF and Endpoint B may be a SL Target UE. + +**Table 8.15.2.2.3-1: Location request information that may be transferred between endpoints.** + +| Information | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requested location information type (location estimate, location measurements, range estimate, range measurements) | +| Periodic reporting criteria | +| Positioning QoS (desired horizontal/vertical accuracy, desired range accuracy, response time, velocity request) | +| Environment information (expected multipath and non line of sight (NLOS) in the current area) | +| Scheduled location time | +| Requested measurement information:
  • - ARP Information Request
  • - LOS-NLOS Indicator Request
  • - SL-PRS-RSRP Request
  • - First Path SL-PRS-RSRPP Request
  • - Additional Paths Request
  • - Timing Quality Request
  • - Multiple SL-PRS Rx-Tx Time Differences Request
  • - Associated SL-PRS Tx Time Stamp Request
| + +**Table 8.15.2.2.3-2: Location result information that may be transferred between endpoints.** + +| Information | SL Target UE-assisted | SL Target UE-based | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| Location estimate | No | Yes | +| Range estimate | No | Yes | +| Velocity estimate | No | Yes | +| SL-RTT measurement information:
  • - LOS-NLOS Indicator
  • - ARP ID
  • - SL-PRS Resource ID
  • - SL-PRS Rx-Tx Time Difference measurement(s)
  • - SL-PRS-RSRP measurement
  • - SL-PRS First Path RSRPP measurement
  • - Additional paths measurement
  • - Time stamp of measurements
  • - Timing quality of measurements
  • - SL-PRS Tx time information
| Yes | No | + +## 8.15.3 SL-AoA positioning + +### 8.15.3.1 General + +The SL-AoA positioning method makes use of SL angle of arrival measurements performed by a UE (e.g., target UE or anchor UE). The SL angle of arrival measurements performed by a UE of sidelink signals transmitted by a peer UE determines the azimuth and vertical angle (i.e., the direction) between the pair of UEs relative to a reference direction (e.g., geographical North). + +### 8.15.3.2 SL-AoA positioning procedures + +#### 8.15.3.2.1 Capability transfer procedure + +The capability transfer procedure for SL-AoA positioning is described in clause 7.11.2.1. + +#### 8.15.3.2.2 Assistance Data transfer procedure + +Figure 8.15.3.2.2-1 shows the Assistance Data transfer operations for the SL-AoA positioning method. + +![Sequence diagram showing the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Assistance Data message back to Endpoint A.](e01c6273c4177746475715ee9c17a882_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Assistance Data + Endpoint A-->>Endpoint B: 1. SLPP Request Assistance Data + Note left of Endpoint B: 2. SLPP Provide Assistance Data + Endpoint B-->>Endpoint A: 2. SLPP Provide Assistance Data + +``` + +Sequence diagram showing the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Assistance Data message back to Endpoint A. + +**Figure 8.15.3.2.2-1: Assistance Data transfer procedure.** + +1. Endpoint A may determine that certain SL-AoA positioning assistance data are desired and sends an SLPP Request Assistance Data message to Endpoint B. This request includes an indication of which specific SL-AoA assistance data are requested. +2. If step 1 occurred, Endpoint B provides the requested assistance in an SLPP Provide Assistance Data message to Endpoint A, if available at Endpoint B. The assistance data that may be signalled are listed in Table 8.15.3.2.2-1. If any of the requested assistance data in step 1 are not provided in step 2, the Endpoint A shall assume that the requested assistance data are not supported, or currently not available at Endpoint B. If none of the requested assistance data in step 1 can be provided by Endpoint B, Endpoint B returns any information that can be provided in an SLPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. +If step 1 did not occur, Endpoint B determines that SL-AoA assistance data needs to be provided to Endpoint A (e.g., as part of a positioning procedure) and sends an SLPP Provide Assistance Data message to Endpoint A. + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Server UE or LMF. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Target UE or SL Server UE and Endpoint B may be a SL Anchor UE. + +NOTE 3: Dependent on the scenario, Endpoint A may be a SL-PRS transmitting (Tx) UE and Endpoint B may be a SL-PRS receiving (Rx) UE. + +**Table 8.15.3.2.2-1: Assistance data that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------| +| Application Layer ID, identifying a UE as defined in TS 23.287 [48] | +| SL-PRS Sequence ID as defined in TS 38.211 [50] | +| ARP ID, identifying an SL-PRS Tx ARP associated with a UE | +| Anchor UE location coordinates | +| SL-PRS Tx ARP location coordinates | +| Expected AoA and uncertainty | + +### 8.15.3.2.3 Location Information transfer procedure + +Figure 8.15.3.2.3-1 shows the Location Information transfer operations for the SL-AoA positioning method. + +![Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Location Information message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Location Information message to Endpoint A. Step 3: Endpoint B sends another SLPP Provide Location Information message to Endpoint A.](4f7470055bfc22c4aa6b007a4056940e_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Location Information + Endpoint A-->>Endpoint B: 1. SLPP Request Location Information + Note left of Endpoint B: 2. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 2. SLPP Provide Location Information + Note left of Endpoint B: 3. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 3. SLPP Provide Location Information + +``` + +Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Location Information message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Location Information message to Endpoint A. Step 3: Endpoint B sends another SLPP Provide Location Information message to Endpoint A. + +**Figure 8.15.3.2.3-1: Location Information transfer procedure.** + +1. Endpoint A may send an SLPP Request Location Information message to Endpoint B. This request includes an indication of SL-AoA measurements requested, including any needed measurement configuration information, and possibly a required response time as listed in Table 8.15.3.2.3-1. +2. If step 1 occurred, Endpoint B obtains the SL-AoA measurements as requested in step 1. Endpoint B then sends an SLPP Provide Location Information message to Endpoint A, before the Response Time (if provided in step 1) elapsed, and includes the obtained SL-AoA measurements as listed in Table 8.15.3.2.3-2. If Endpoint B is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, Endpoint B returns any information that can be provided in an SLPP message of type Provide Location Information which includes a cause indication for the not provided location information. If step 1 did not occur, Endpoint B may send an SLPP Provide Location Information message to Endpoint A. The SLPP Provide Location Information message may include any SL-AoA results already available at Endpoint B. +3. Optionally (e.g, if requested at step 1), Endpoint B may provide one or more additional SLPP Provide Location Information messages with SL-AoA measurements to Endpoint A (e.g., according to the periodic reporting criteria if received at step1). + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Anchor UE. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Server UE or LMF and Endpoint B may be a SL Target UE. + +**Table 8.15.3.2.3-1: Location request information that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requested location information type (location estimate, location measurements, range estimate, range measurements) | +| Periodic reporting criteria | +| Positioning QoS (desired horizontal/vertical accuracy, desired direction accuracy, response time, velocity request) | +| Environment information (expected multipath and non line of sight (NLOS) in the current area) | +| Scheduled location time | +| Requested measurement information:
  • - LOS-NLOS Indicator Request
  • - SL-PRS-RSRP Request
  • - First Path SL-PRS-RSRPP Request
  • - Additional Paths Request
| + +**Table 8.15.3.2.3-2: Location result information that may be transferred between endpoints.** + +| Information | SL Target UE-assisted | SL Target UE-based | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| Location estimate | No | Yes | +| Direction estimate | No | Yes | +| Velocity estimate | No | Yes | +| SL-AoA measurement information:
- LOS-NLOS Indicator
- Angle quality of measurements
- Additional paths angle measurement
- Azimuth/elevation measurement
- Azimuth/elevation LCS to GCS transformation parameter
- ARP ID
- SL-PRS Resource ID
- SL-PRS-RSRP measurement
- SL-PRS First Path RSRPP measurement
- Additional paths measurement
- Time stamp of measurements | Yes | No | + +## 8.15.4 SL-TDOA positioning + +### 8.15.4.1 General + +The SL-TDOA positioning method makes use of SL-RSTD measurements of SL-PRS received at the target UE from two or more peer UEs (e.g., anchor UEs). The target UE measures the SL-RSTD of the received SL-PRS transmitted by two or more peer UEs. The Target UE position is estimated based on the SL-RSTD measurements and the knowledge of the geographical coordinates of the peer UEs (e.g., Anchor UEs) and their relative sidelink timing. + +### 8.15.4.2 SL-TDOA positioning procedures + +#### 8.15.4.2.1 Capability transfer procedure + +The capability transfer procedure for SL-TDOA positioning is described in clause 7.11.2.1. + +#### 8.15.4.2.2 Assistance Data transfer procedure + +Figure 8.15.4.2.2-1 shows the Assistance Data transfer operations for the SL-TDOA positioning method. + +![Sequence diagram showing the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Assistance Data message back to Endpoint A.](44975a59174a634c7c5f49a9fb8eae71_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Assistance Data + Endpoint A-->>Endpoint B: 1. SLPP Request Assistance Data + Note left of Endpoint B: 2. SLPP Provide Assistance Data + Endpoint B-->>Endpoint A: 2. SLPP Provide Assistance Data + +``` + +Sequence diagram showing the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Assistance Data message back to Endpoint A. + +**Figure 8.15.4.2.2-1: Assistance Data transfer procedure.** + +1. Endpoint A may determine that certain SL-TDOA positioning assistance data are desired and sends an SLPP Request Assistance Data message to Endpoint B. This request includes an indication of which specific SL-TDOA assistance data are requested. +2. If step 1 occurred, Endpoint B provides the requested assistance in an SLPP Provide Assistance Data message to Endpoint A, if available at Endpoint B. The assistance data that may be signalled are listed in Table 8.15.4.2.2-1. + +If any of the requested assistance data in step 1 are not provided in step 2, the Endpoint A shall assume that the requested assistance data are not supported, or currently not available at Endpoint B. If none of the requested assistance data in step 1 can be provided by Endpoint B, Endpoint B returns any information that can be provided in an SLPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. + +If step 1 did not occur, Endpoint B determines that SL-TDOA assistance data needs to be provided to Endpoint A (e.g., as part of a positioning procedure) and sends an SLPP Provide Assistance Data message to Endpoint A. + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Server UE or LMF. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Target UE or SL Server UE and Endpoint B may be a SL Anchor UE. + +NOTE 3: Dependent on the scenario, Endpoint A may be a SL-PRS transmitting (Tx) UE and Endpoint B may be a SL-PRS receiving (Rx) UE. + +**Table 8.15.4.2.2-1: Assistance data that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------| +| Application Layer ID, identifying a UE as defined in TS 23.287 [48] | +| SL-PRS Sequence ID as defined in TS 38.211 [50] | +| ARP ID, identifying an SL-PRS Tx ARP associated with a UE | +| Anchor UE location coordinates | +| SL-PRS Tx ARP location coordinates | +| Synchronization information between anchor UEs | + +### 8.15.4.2.3 Location Information transfer procedure + +Figure 8.15.4.2.3-1 shows the Location Information transfer operations for the SL-TDOA positioning method. + +![Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1 is a dashed arrow from A to B (SLPP Request Location Information). Step 2 is a solid arrow from B to A (SLPP Provide Location Information). Step 3 is a dashed arrow from B to A (SLPP Provide Location Information).](6aec120931a00f0d600bdb4a99d00bcc_img.jpg) + +``` + +sequenceDiagram + participant A as Endpoint A + participant B as Endpoint B + A-->>B: 1. SLPP Request Location Information + B->>A: 2. SLPP Provide Location Information + B-->>A: 3. SLPP Provide Location Information + +``` + +Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1 is a dashed arrow from A to B (SLPP Request Location Information). Step 2 is a solid arrow from B to A (SLPP Provide Location Information). Step 3 is a dashed arrow from B to A (SLPP Provide Location Information). + +**Figure 8.15.4.2.3-1: Location Information transfer procedure.** + +- Endpoint A may send an SLPP Request Location Information message to Endpoint B. This request includes an indication of SL-TDOA measurements requested, including any needed measurement configuration information, and possibly a required response time as listed in Table 8.15.4.2.3-1. +- If step 1 occurred, Endpoint B obtains the SL-TDOA measurements as requested in step 1. Endpoint B then sends an SLPP Provide Location Information message to Endpoint A, before the Response Time (if provided in step 1) elapsed, and includes the obtained SL-TDOA measurements as listed in Table 8.15.4.2.3-2. If Endpoint B is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, Endpoint B returns any information that can be provided in an SLPP message of type Provide Location Information which includes a cause indication for the not provided location information. If step 1 did not occur, Endpoint B may send an SLPP Provide Location Information message to Endpoint A. The SLPP Provide Location Information message may include any SL-TDOA results already available at Endpoint B. +- Optionally (e.g., if requested at step 1), Endpoint B may provide one or more additional SLPP Provide Location Information messages with SL-TDOA measurements to Endpoint A (e.g., according to the periodic reporting criteria if received at step 1). + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Server UE or LMF and Endpoint B may be a SL Target UE. + +**Table 8.15.4.2.3-1: Location request information that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requested location information type (location estimate, location measurements) | +| Periodic reporting criteria | +| Positioning QoS (desired horizontal/vertical accuracy, response time, velocity request) | +| Environment information (expected multipath and non line of sight (NLOS) in the current area) | +| Scheduled location time | +| Requested measurement information:
  • - ARP Information Request
  • - LOS-NLOS Indicator Request
  • - SL-PRS-RSRP Request
  • - First Path SL-PRS-RSRPP Request
  • - Additional Paths Request
  • - SL Timing Quality Request
| + +**Table 8.15.4.2.3-2: Location result information that may be transferred between endpoints.** + +| Information | SL Target UE-assisted | SL Target UE-based | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| Location estimate | No | Yes | +| Velocity estimate | No | Yes | +| SL-TDOA measurement information:
  • - LOS-NLOS Indicator
  • - ARP ID
  • - SL-PRS Resource ID
  • - SL-PRS-RSRP measurement
  • - SL-PRS First Path RSRPP measurement
  • - SL-RSTD measurement
  • - Additional paths measurement
  • - Time stamp of measurements
  • - Timing quality of measurements
| Yes | No | + +## 8.15.5 SL-TOA positioning + +### 8.15.5.1 General + +The SL-TOA positioning method makes use of SL-RTOA measurements performed at multiple peer UEs (e.g., anchor UEs). The target UE transmits SL-PRS and the peer UEs (e.g., anchor UEs) measures the SL-RTOA relative to the peer UEs (e.g., anchor UEs) own time base. The Target UE position is estimated based on the SL-RTOA measurements and the knowledge of the geographical coordinates of the peer UEs (e.g., Anchor UEs) and their relative sidelink timing. + +### 8.15.5.2 SL-TOA positioning procedures + +#### 8.15.5.2.1 Capability transfer procedure + +The capability transfer procedure for SL-TOA positioning is described in clause 7.11.2.1. + +#### 8.15.5.2.2 Assistance Data transfer procedure + +Figure 8.15.5.2.2-1 shows the Assistance Data transfer operations for the SL-TOA positioning method. + +![Sequence diagram showing the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Assistance Data message back to Endpoint A.](6d54943c64ae4af089cb9e98a78d0af7_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Assistance Data + Endpoint A-->>Endpoint B: 1. SLPP Request Assistance Data + Note left of Endpoint B: 2. SLPP Provide Assistance Data + Endpoint B-->>Endpoint A: 2. SLPP Provide Assistance Data + +``` + +Sequence diagram showing the Assistance Data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Assistance Data message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Assistance Data message back to Endpoint A. + +**Figure 8.15.5.2.2-1: Assistance Data transfer procedure.** + +1. Endpoint A may determine that certain SL-TOA positioning assistance data are desired and sends an SLPP Request Assistance Data message to Endpoint B. This request includes an indication of which specific SL-TOA assistance data are requested. +2. If step 1 occurred, Endpoint B provides the requested assistance in an SLPP Provide Assistance Data message to Endpoint A, if available at Endpoint B. The assistance data that may be signalled are listed in Table 8.15.5.2.2-1. If any of the requested assistance data in step 1 are not provided in step 2, the Endpoint A shall assume that the requested assistance data are not supported, or currently not available at Endpoint B. If none of the requested assistance data in step 1 can be provided by Endpoint B, Endpoint B returns any information that can be provided in an SLPP message of type Provide Assistance Data which includes a cause indication for the not provided assistance data. +If step 1 did not occur, Endpoint B determines that SL-TOA assistance data needs to be provided to Endpoint A (e.g., as part of a positioning procedure) and sends an SLPP Provide Assistance Data message to Endpoint A. + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Server UE or LMF. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Target UE or SL Server UE and Endpoint B may be a SL Anchor UE. + +NOTE 3: Dependent on the scenario, Endpoint A may be a SL-PRS transmitting (Tx) UE and Endpoint B may be a SL-PRS receiving (Rx) UE. + +**Table 8.15.5.2.2-1: Assistance data that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------| +| Application Layer ID, identifying a UE as defined in TS 23.287 [48] | +| SL-PRS Sequence ID as defined in TS 38.211 [50] | +| ARP ID, identifying an SL-PRS Tx ARP associated with a UE | +| Anchor UE location coordinates | +| SL-PRS Tx ARP location coordinates | +| Synchronization information between anchor UEs | + +### 8.15.5.2.3 Location Information transfer procedure + +Figure 8.15.5.2.3-1 shows the Location Information transfer operations for the SL-TOA positioning method. + +![Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Location Information message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Location Information message to Endpoint A. Step 3: Endpoint B sends another SLPP Provide Location Information message to Endpoint A.](1fd763be1b7a05b52e554f0583617642_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. SLPP Request Location Information + Endpoint A-->>Endpoint B: 1. SLPP Request Location Information + Note left of Endpoint B: 2. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 2. SLPP Provide Location Information + Note left of Endpoint B: 3. SLPP Provide Location Information + Endpoint B-->>Endpoint A: 3. SLPP Provide Location Information + +``` + +Sequence diagram showing the Location Information transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends an SLPP Request Location Information message to Endpoint B. Step 2: Endpoint B sends an SLPP Provide Location Information message to Endpoint A. Step 3: Endpoint B sends another SLPP Provide Location Information message to Endpoint A. + +**Figure 8.15.5.2.3-1: Location Information transfer procedure.** + +1. Endpoint A may send an SLPP Request Location Information message to Endpoint B. This request includes an indication of SL-TOA measurements requested, including any needed measurement configuration information, and possibly a required response time as listed in Table 8.15.5.2.3-1. +2. If step 1 occurred, Endpoint B obtains the SL-TOA measurements as requested in step 1. Endpoint B then sends an SLPP Provide Location Information message to Endpoint A, before the Response Time (if provided in step 1) elapsed, and includes the obtained SL-TOA measurements as listed in Table 8.15.5.2.3-2. If Endpoint B is unable to perform the requested measurements, or the Response Time elapsed before any of the requested measurements were obtained, Endpoint B returns any information that can be provided in an SLPP message of type Provide Location Information which includes a cause indication for the not provided location information. If step 1 did not occur, Endpoint B may send an SLPP Provide Location Information message to Endpoint A. The SLPP Provide Location Information message may include any SL-TOA results already available at Endpoint B. +3. Optionally (e.g, if requested at step 1), Endpoint B may provide one or more additional SLPP Provide Location Information messages with SL-TOA measurements to Endpoint A (e.g., according to the periodic reporting criteria if received at step1). + +NOTE 1: Dependent on the scenario, Endpoint A may be a SL Server UE or LMF and Endpoint B may be a SL Target UE. + +NOTE 2: Dependent on the scenario, Endpoint A may be a SL Target UE and Endpoint B may be a SL Anchor UE. + +**Table 8.15.5.2.3-1: Location request information that may be transferred between endpoints.** + +| Information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requested location information type (location estimate, location measurements) | +| Periodic reporting criteria | +| Positioning QoS (desired horizontal/vertical accuracy, response time, velocity request) | +| Environment information (expected multipath and non line of sight (NLOS) in the current area) | +| Scheduled location time | +| Requested measurement information:
  • - ARP Information Request
  • - LOS-NLOS Indicator Request
  • - SL-PRS-RSRP Request
  • - First Path SL-PRS-RSRPP Request
  • - Additional Paths Request
  • - SL Timing Quality Request
| + +**Table 8.15.5.2.3-2: Location result information that may be transferred between endpoints.** + +| Information | SL Target UE-assisted | SL Target UE-based | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------| +| Location estimate | No | Yes | +| Velocity estimate | No | Yes | +| SL-TDOA measurement information:
- LOS-NLOS Indicator
- SL-RTOA measurement
- ARP ID
- SL-PRS Resource ID
- SL-PRS-RSRP measurement
- SL-PRS First Path RSRPP measurement
- Additional paths measurement
- Time stamp of measurements
- Timing quality of measurements | Yes | No | + +## Annex A (informative): Use of LPP with SUPL + +The design goal of LPP is to enable it to be used in user plane location solutions such as OMA SUPL ([15], [16]) and this informative annex shows how LPP can be used in SUPL 2.0. + +### A.1 SUPL 2.0 Positioning Methods and Positioning Protocols + +The following table shows how the 3GPP positioning protocols are supported in SUPL 2.0. + +**Table A.1-1: SUPL support of positioning methods** + +| Positioning Protocol: | RRLP
(GSM/GPRS/WCDMA/
LTE/WLAN/WiMAX) | RRC
(WCDMA) | LPP
(NR/LTE) | +|-----------------------------------------------------------------------|------------------------------------------------------|------------------------|-------------------------| +| Positioning Method: | | | | +| A-GPS (A-GANSS) SET Assisted | ✓ | ✓ | ✓ | +| A-GPS (A-GANSS) SET Based | ✓ | ✓ | ✓ | +| Autonomous GPS/GANSS | ✓ | ✓ | ✓ | +| Enhanced Cell ID NOTE 1 | ✓ | ✓ | ✓ NOTE 2 | +| Enhanced Observed Time Difference (E-OTD) | ✓ (GSM only) | NA | NA | +| Observed Time Difference of Arrival (OTDOA) NOTE 1, NOTE 3 | NA | ✓ | ✓ | +| Sensors | NA | ✓ NOTE 5 | ✓ | +| WLAN | NA | ✓ | ✓ | +| Bluetooth | NA | ✓ | ✓ | +| TBS NOTE 4 | NA | ✓ | ✓ | +| NR DL-TDOA | NA | NA | ✓ | +| NR DL-AoD | NA | NA | ✓ | +| NR E-CID (downlink) | NA | NA | ✓ | +| NR Multi-RTT | NA | NA | ✓ | +| NR UL-TDOA | NA | NA | ✓ | +| NR UL-AoA | NA | NA | ✓ | + +NOTE 1: Excludes methods based on NR signals. + +NOTE 2: For LPP, NR CID is supported. + +NOTE 3: This includes TBS positioning based on PRS signals, which is only supported in LPP (LTE). + +NOTE 4: TBS positioning based on MBS signals. + +NOTE 5: Only barometric pressure sensor is supported. + +NOTE: What is referred to in the SUPL specifications as "Enhanced Cell ID", is a UE-Assisted positioning mode, where the neighbouring cell measurements are carried at the SUPL layer (in the SUPL\_POS\_INIT for example). The ASN.1 container for this mode is defined as follows: + +``` +LteCellInformation ::= SEQUENCE { + cellGlobalIdEUTRA CellGlobalIdEUTRA, + physCellId PhysCellId, + trackingAreaCode TrackingAreaCode, + rsrpResult RSRP-Range OPTIONAL, + rsrqResult RSRQ-Range OPTIONAL, + ta INTEGER(0..1282) OPTIONAL, -- Currently used Timing Advance value (N_TA/16 as per [3GPP 36.213]) + measResultListEUTRA MeasResultListEUTRA OPTIONAL, --Neighbour measurements +} +``` + +``` + + .... + earfcn INTEGER(0..65535) OPTIONAL, -- see Table 37 + earfcn-ext INTEGER (65536..262143) OPTIONAL, -- see Table 37 + rsrpResult-ext RSRP-Range-Ext OPTIONAL, + rsrqResult-ext RSQ-Range-Ext OPTIONAL, + rs-sinrResult RS-SINR-Range OPTIONAL, + servingInformation5G ServingInformation5G OPTIONAL +} + +MeasResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRA + +MeasResultEUTRA ::= SEQUENCE { + physCellId PhysCellId, + cgi-Info SEQUENCE { + cellGlobalId CellGlobalIdEUTRA, + trackingAreaCode TrackingAreaCode + } OPTIONAL, + measResult SEQUENCE { + rsrpResult RSRP-Range OPTIONAL, -- Mapping to measured values + rsrqResult RSQ-Range OPTIONAL, -- in 3GPP TS 36.133 + .... + earfcn INTEGER(0..65535) OPTIONAL, -- see Table 37 + earfcn-ext INTEGER (65536..262143) OPTIONAL, -- see Table 37 + rsrpResult-ext RSRP-Range-Ext OPTIONAL, + rsrqResult-ext RSQ-Range-Ext OPTIONAL, + rs-sinrResult RS-SINR-Range OPTIONAL, + neighbourInformation5G NeighbourInformation5G OPTIONAL + } +} + +NRCellInformation ::= SEQUENCE { + servingCellInformation ServingCellInformationNR, --Serving cell information + measuredResultsListNR MeasResultListNR OPTIONAL, --Neighbour measurements + .... +} + +-- Information for serving cells per 3GPP TS 38.331 + +ServingCellInformationNR ::= SEQUENCE (SIZE (1..maxNRServingCell)) OF ServCellNR +-- The first listed serving cell shall be the primary cell + +ServCellNR ::= SEQUENCE { + physCellId PhysCellIdNR, + arfcn-NR ARFCN-NR, + cellGlobalId CellGlobalIdNR, + trackingAreaCode TrackingAreaCodeNR, + ssb-Measurements NR-Measurements OPTIONAL, + csi-rs-Measurements NR-Measurements OPTIONAL, + ta INTEGER(0..3846) OPTIONAL, --Timing Advance value + .... + arfcn-type ENUMERATED {ssb, csi-rs} OPTIONAL, + systemFrameNumber BIT STRING (SIZE (10)) OPTIONAL, + ssb-IndexList-Measurements SSB-IndexList-Measurements OPTIONAL, + csi-rs-IndexList-Measurements CSI-RS-IndexList-Measurements OPTIONAL +} + +MeasResultListNR ::= SEQUENCE (SIZE (1..maxCellReportNR)) OF MeasResultNR +MeasResultNR ::= SEQUENCE { + physCellId PhysCellIdNR, + arfcn-NR ARFCN-NR, + cellGlobalId CellGlobalIdNR OPTIONAL, + trackingAreaCode TrackingAreaCodeNR OPTIONAL, + ssb-Measurements NR-Measurements OPTIONAL, + csi-rs-Measurements NR-Measurements OPTIONAL, + .... + arfcn-type ENUMERATED {ssb, csi-rs} OPTIONAL, + systemFrameNumber BIT STRING (SIZE (10)) OPTIONAL, + ssb-IndexList-Measurements SSB-IndexList-Measurements OPTIONAL, + csi-rs-IndexList-Measurements CSI-RS-IndexList-Measurements OPTIONAL +} + +``` + +It should be noted that in addition to the container provided by SUPL itself, E-CID/NR E-CID positioning methods defined within LPP proper can be supported in SUPL, via tunnelling LPP as shown in this annex (in the same manner that A-GNSS, OTDOA, Barometric Pressure Sensors, WLAN, Bluetooth and TBS are supported). + +## A.2 SUPL 2.0 and NR Architecture + +This clause describes interworking between the control-plane LCS architecture, as defined in the main body of this specification, and SUPL 2.0. Similarly, to the E-SMLC in the LTE architecture (TS 36.305 [25]), the LMF either includes or has an interface to an SPC function, as defined in OMA SUPL V2.0 ([15], [16]). It can thus provide a consistent set of positioning methods for deployments utilizing both control-plane and user-plane. + +The interworking does not enable use of user-plane signalling for part of a control-plane positioning session. The user plane in the interworking here is not intended as an alternative path for control-plane signalling that would be needed between UE and NG-RAN for mechanisms such as A-GPS in a standalone control-plane solution. + +This interworking does enable the SPC to retrieve measurements (e.g., GNSS-to-RAN time relations) from the NG-RAN. + +The underlying architecture is shown in Figure A.2-1 (TS 23.501 [2]). Note that, for interworking between user-plane and control-plane positioning, no new interfaces need to be defined as compared to those in the figure, assuming the SPC is either integrated in the LMF or attached to it with a proprietary interface. + +![Figure A.2-1: System reference architecture reference for Location Services in reference point representation. The diagram shows the interconnection of various network functions for location services. UE is connected to NG-RAN via Uu. NG-RAN is connected to AMF via N2 and to UPF via N3. AMF is connected to UDM via N8, to GMLC via NLg, and to LMF via NLs. LMF is connected to SPC (Non-LCS Entity) via Llp. SPC is connected to SLC (Non-LCS Entity) via Le. SLC is connected to LCS Client via Le. UPF is connected to SLC via Lup and to LCS Client via N6. A legend indicates: Signaling (red solid line), Data/Voice (blue solid line), Connection via intermediate entities (dashed line), and Non-LCS Entity (grey box).](59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg) + +Figure A.2-1: System reference architecture reference for Location Services in reference point representation. The diagram shows the interconnection of various network functions for location services. UE is connected to NG-RAN via Uu. NG-RAN is connected to AMF via N2 and to UPF via N3. AMF is connected to UDM via N8, to GMLC via NLg, and to LMF via NLs. LMF is connected to SPC (Non-LCS Entity) via Llp. SPC is connected to SLC (Non-LCS Entity) via Le. SLC is connected to LCS Client via Le. UPF is connected to SLC via Lup and to LCS Client via N6. A legend indicates: Signaling (red solid line), Data/Voice (blue solid line), Connection via intermediate entities (dashed line), and Non-LCS Entity (grey box). + +**Figure A.2-1: System reference architecture reference for Location Services in reference point representation** + +The Lup and Llp interfaces shown in this architecture are part of the user-plane solution only and are not required for control-plane positioning. + +## A.3 LPP session procedures using SUPL + +This clause indicates how an LPP session relates to the SUPL message set. Figure A.3-1 shows how SUPL and LPP can be combined within a SUPL positioning session. Step 4 here is repeated to exchange multiple LPP messages between the SLP and SET. + +![Sequence diagram of an LPP session over SUPL between an SLP and a SET.](dbe8bef1723acb3e03e8616be4faf939_img.jpg) + +``` + +sequenceDiagram + participant SLP + participant SET + Note right of SLP: 1. SUPL INIT + SLP->>SET: 1. SUPL INIT + Note left of SET: 2. Establish secure TCP/IP Connection + SET->>SLP: 2. Establish secure TCP/IP Connection + Note left of SLP: 3. SUPL POS INIT (E-CID measurements) + SLP->>SET: 3. SUPL POS INIT (E-CID measurements) + Note left of SET: 4. SUPL POS (LPP PDU) + SET->>SLP: 4. SUPL POS (LPP PDU) + Note right of SLP: 5. SUPL END + SLP->>SET: 5. SUPL END + +``` + +Sequence diagram of an LPP session over SUPL between an SLP and a SET. + +**Figure A.3-1: LPP session over SUPL** + +For positioning operations which take place entirely within an LPP session (step 4 in Figure A.3-1), the flow of LPP messages can be the same as in the control-plane version of LPP; the role of the (LPP) target is taken by the target SET, and that of the (LPP) server by the SLP. An example LPP flow, including exchange of capabilities, request and delivery of assistance data, and request and delivery of positioning information, is shown in Figure A.3-2. + +![Sequence diagram of an LPP session over SUPL between an LPP Target (Target SET) and an LPP Server (SLP).](8d0915ee91e7b38094625cfc8d8f039b_img.jpg) + +``` + +sequenceDiagram + participant Target SET as LPP Target (Target SET) + participant SLP as LPP Server (SLP) + Note left of SLP: 1. LPP PDU: Location information request [position estimate, transaction A] + SLP->>Target SET: 1. LPP PDU: Location information request [position estimate, transaction A] + Note left of SLP: 2. LPP PDU: Capability request [transaction B] + SLP->>Target SET: 2. LPP PDU: Capability request [transaction B] + Note right of Target SET: 3. LPP PDU: Capability indication [transaction B] + Target SET->>SLP: 3. LPP PDU: Capability indication [transaction B] + Note left of SLP: 4. LPP PDU: Assistance data request [transaction C] + SLP->>Target SET: 4. LPP PDU: Assistance data request [transaction C] + Note right of Target SET: 5. LPP PDU: Assistance data delivery [transaction C] + Target SET->>SLP: 5. LPP PDU: Assistance data delivery [transaction C] + Note left of SLP: 6. LPP PDU: Location information request [measurements, transaction D] + SLP->>Target SET: 6. LPP PDU: Location information request [measurements, transaction D] + Note right of Target SET: 7. LPP PDU: Location information [measurements, transaction D] + Target SET->>SLP: 7. LPP PDU: Location information [measurements, transaction D] + Note left of SLP: 8. LPP PDU: Location information [position estimate, transaction A] + SLP->>Target SET: 8. LPP PDU: Location information [position estimate, transaction A] + +``` + +Sequence diagram of an LPP session over SUPL between an LPP Target (Target SET) and an LPP Server (SLP). + +**Figure A.3-2: LPP session over SUPL** + +## A.4 Procedures combining C-plane and U-plane operations + +Since SUPL by definition is carried over the user plane, it is not applicable to operations terminating at the NG-RAN. SUPL operations must take place in combination with control-plane procedures over NRPPa. + +This situation could arise in the case of UE-assisted OTDOA, for example, in which the SLP needs to provide the UE (in a SUPL session) with assistance data supplied by the NG-RAN. This clause uses a UE-assisted OTDOA positioning operation as an example. + +Although the positioning server in this operation is the SLP, the existence of an interface to the LMF means that the SLP can communicate with the LMF via the SPC. In particular, this means that assistance data that was delivered to the LMF via NRPPa can be transferred over to the SLP for delivery to the UE via LPP over SUPL. + +There are several ways to realise this general behaviour. In the simplest case, the LMF could be supplied with the necessary assistance data in advance, so that it can be supplied to the SLP without any actual NRPPa procedures taking place in real time (and possibly even before the positioning transaction begins). + +![Sequence diagram showing the transfer of OTDOA assistance data to UE via SUPL when data is already available at the LMF.](e1570156ae4b4ddeb6913fc793678c94_img.jpg) + +``` + +sequenceDiagram + participant UE (SET) + participant NG-RAN + participant LMF + participant SLP + Note right of NG-RAN: Assistance data (via NRPPa) + NG-RAN->>LMF: Assistance data (via NRPPa) + Note right of UE: SUPL session establishment + UE->>SLP: SUPL session establishment + Note right of LMF: Assistance data (via Llp) + LMF->>SLP: Assistance data (via Llp) + Note right of SLP: Assistance data (via LPP/SUPL) + SLP->>UE: Assistance data (via LPP/SUPL) + +``` + +The diagram illustrates a sequence of interactions between four entities: UE (SET), NG-RAN, LMF, and SLP. + 1. The NG-RAN sends 'Assistance data (via NRPPa)' to the LMF. + 2. A 'SUPL session establishment' message is shown as a large double-headed arrow between the UE and the SLP. + 3. The LMF sends 'Assistance data (via Llp)' to the SLP. + 4. Finally, the SLP sends 'Assistance data (via LPP/SUPL)' to the UE. + +Sequence diagram showing the transfer of OTDOA assistance data to UE via SUPL when data is already available at the LMF. + +**Figure A.4-1: Transfer of OTDOA assistance data to UE via SUPL** + +In the event that the LMF does not have the required assistance data available, it would need to retrieve them from the NG-RAN once it was made aware that they were needed. + +![Sequence diagram showing the transfer of OTDOA assistance data to UE via SUPL when data is not already available at the LMF.](071619a7be79904674fb6b1963aa3b67_img.jpg) + +``` + +sequenceDiagram + participant UE (SET) + participant NG-RAN + participant LMF + participant SLP + Note right of UE: SUPL session establishment + UE->>SLP: SUPL session establishment + Note right of SLP: Assistance data request (via LPP/SUPL) + SLP->>LMF: Assistance data request (via Llp) + Note right of LMF: Assistance data request (via NRPPa) + LMF->>NG-RAN: Assistance data request (via NRPPa) + Note right of NG-RAN: Assistance data (via NRPPa) + NG-RAN->>LMF: Assistance data (via NRPPa) + Note right of LMF: Assistance data (via Llp) + LMF->>SLP: Assistance data (via Llp) + Note right of SLP: Assistance data (via LPP/SUPL) + SLP->>UE: Assistance data (via LPP/SUPL) + +``` + +The diagram illustrates a sequence of interactions between four entities: UE (SET), NG-RAN, LMF, and SLP. + 1. A 'SUPL session establishment' message is shown as a large double-headed arrow between the UE and the SLP. + 2. The SLP sends an 'Assistance data request (via LPP/SUPL)' to the LMF. + 3. The LMF sends an 'Assistance data request (via Llp)' to the NG-RAN. + 4. The NG-RAN sends 'Assistance data (via NRPPa)' to the LMF. + 5. The LMF sends 'Assistance data (via Llp)' to the SLP. + 6. Finally, the SLP sends 'Assistance data (via LPP/SUPL)' to the UE. + +Sequence diagram showing the transfer of OTDOA assistance data to UE via SUPL when data is not already available at the LMF. + +**Figure A.4-2: Transfer to the UE via SUPL of OTDOA assistance data not already available at the LMF** + +In both cases, it should be noted that the retrieval of the assistance data is transparent to the UE and to the actual SUPL session. This model is parallel to the approach used with A-GNSS, in which assistance data such as satellite ephemerides are retrieved from sources entirely external to the cellular network. For purposes of LPP over SUPL, the delivery of assistance data to the SLP can be viewed as an independent external process. + +The delivery of assistance data to the UE, however, takes place through the same mechanisms as control-plane LPP, transported through SUPL. + +--- + +## Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 08/2017 | RAN2#99 | R2-1709477 | | | | Skeleton for TS 38.305 | 0.0.1 | +| 03/2018 | RAN2#101 | R2-1803804 | | | | | 0.1.0 | +| 03/2018 | RAN#79 | RP-180171 | | | | Submitted for Information in RAN#79 | 1.0.0 | +| 05/2018 | RAN2#102 | R2-1808695 | | | | | 1.1.0 | +| 05/2018 | RAN2#102 | R2-1809137 | | | | | 1.2.0 | +| 06/2018 | RP-80 | RP-180689 | | | | Submitted for Approval in RAN#80 | 2.0.0 | +| 06/2018 | | | | | | Upgraded to Rel-15 after plenary approval | 15.0.0 | +| 09/2018 | RP-81 | RP-181939 | 0001 | - | F | Signalling between an LMF and NG-RAN node/UE | 15.1.0 | +| | RP-81 | RP-181942 | 0002 | 1 | F | Gaps for positioning measurements | 15.1.0 | +| 12/2018 | RP-82 | RP-182655 | 0006 | - | F | Addition of RTK Assistance Data | 15.2.0 | +| | RP-82 | RP-182656 | 0007 | 1 | F | Capture use of motion information from motion sensors | 15.2.0 | +| 03/2019 | RP-83 | RP-190544 | 0008 | 2 | F | CR to 38.305 on use of positioning measurement gaps for subframe and slot timing detection towards E-UTRA | 15.3.0 | +| 06/2019 | RP-84 | RP-191374 | 0009 | 2 | F | Minor restructuring of sensor references and addition of sensor methods (IMU) | 15.4.0 | +| | RP-84 | RP-191374 | 0010 | 3 | F | Adding missing reference for autonomous and measurements gaps for Inter-RAT RSTD measurements | 15.4.0 | +| | RP-84 | RP-191376 | 0011 | 4 | F | Update of OMA SUPL information | 15.4.0 | +| | RP-84 | RP-191378 | 0012 | 4 | F | UE Identifier for routing message between Core Network Nodes and RAN | 15.4.0 | +| 12/2019 | RP-86 | RP-192938 | 0014 | 2 | F | Correction on the EUTRAN terminology | 15.5.0 | +| | RP-86 | RP-192935 | 0015 | 2 | F | Corrections for Positioning Architecture | 15.5.0 | +| | RP-86 | RP-192935 | 0016 | - | F | Corrections of terminology for stage 2 | 15.5.0 | +| 03/2020 | RP-87 | RP-200357 | 0013 | 1 | B | Introduction of B1C signal in BDS system in A-GNSS | 16.0.0 | +| | RP-87 | RP-200345 | 0017 | 3 | B | Introduction of NR positioning | 16.0.0 | +| 07/2020 | RP-88 | RP-201161 | 0019 | 2 | A | Clarification on UE Positioning Architecture | 16.1.0 | +| | RP-88 | RP-201175 | 0021 | 1 | A | CR to clarify the meaning of GNSS term in 38.305 Rel-16 | 16.1.0 | +| | RP-88 | RP-201190 | 0024 | 1 | F | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | 16.1.0 | +| | RP-88 | RP-201175 | 0025 | 2 | F | Corrections to NR Positioning | 16.1.0 | +| 09/2020 | RP-89 | RP-201989 | 0028 | - | F | Correction to SUPL support for NR positioning methods | 16.2.0 | +| | RP-89 | RP-201989 | 0029 | 1 | F | Correction on Stage-2 for gNB and LMF information transfer | 16.2.0 | +| | RP-89 | RP-201989 | 0032 | 1 | F | Miscellaneous correction to stage2 spec | 16.2.0 | +| | RP-89 | RP-201989 | 0033 | - | F | Signalling sequence correction for UL SRS Configuration | 16.2.0 | +| | RP-89 | RP-201989 | 0034 | - | B | Introduction of NR positioning | 16.2.0 | +| 12/2020 | RP-90 | RP-202775 | 0037 | - | F | Remove the NOTE in architecture figure in TS 38.305 | 16.3.0 | +| | RP-90 | RP-202775 | 0048 | - | A | Correction to OTDOA positioning support descriptions in R16 | 16.3.0 | +| | RP-90 | RP-202775 | 0053 | 1 | F | NR positioning Stage 2 corrections | 16.3.0 | +| 03/2021 | RP-91 | RP-210703 | 0062 | 1 | F | Support OTDOA assistance data for case of NR serving cell | 16.4.0 | +| | RP-91 | RP-210693 | 0065 | 1 | F | Correction on the description for gNB measurements | 16.4.0 | +| 06/2021 | RP-92 | RP-211480 | 0069 | 3 | F | Correction to 5G support for NB-IoT positioning | 16.5.0 | +| | RP-92 | RP-211474 | 0072 | 2 | F | Correction to NR stage2 spec for MO-LR | 16.5.0 | +| | RP-92 | RP-211474 | 0074 | - | F | Addition of missing parameters for the SRS spatial information | 16.5.0 | +| | RP-92 | RP-211474 | 0075 | 1 | F | Correction on NRPPa transaction types | 16.5.0 | +| 09/2021 | RP-93 | RP-212443 | 0064 | 3 | F | Correction to UL E-CID-R16 | 16.6.0 | +| | RP-93 | RP-212443 | 0077 | - | F | Correction to 38.305 on NG-RAN positioning operations | 16.6.0 | +| | RP-93 | RP-212443 | 0078 | 1 | F | Correction on user-plane positioning support by SUPL | 16.6.0 | +| 12/2021 | RP-94 | RP-213344 | 0081 | 2 | F | Alignment between stage 2 and Stage 3 specifications | 16.7.0 | +| | RP-94 | RP-213344 | 0083 | - | F | Corrections on definitions and scope of information transfer | 16.7.0 | +| 03/2022 | RP-95 | RP-220510 | 0082 | 2 | B | Addition of Timing Advance measurement reporting in NR E-CID [NRTADV] | 17.0.0 | +| | RP-95 | RP-220479 | 0086 | - | B | Introduction of R17 Positioning Enhancements | 17.0.0 | +| 06/2022 | RP-96 | RP-221725 | 0099 | - | F | 38.305 CR for Positioning WI | 17.1.0 | +| | RP-96 | RP-221725 | 0100 | 1 | F | Stage 2 corrections for NR Positioning Enhancements | 17.1.0 | +| 09/2022 | RP-97 | RP-222521 | 0102 | - | A | Correction on the description of deferred MT-LR | 17.2.0 | +| | RP-97 | RP-222524 | 0105 | 2 | F | Miscellaneous corrections for TS38.305 | 17.2.0 | +| 12/2022 | RP-98 | RP-223411 | 0117 | 1 | F | Corrections on NRPPa functions and procedures | 17.3.0 | +| 03/2023 | RP-99 | RP-230688 | 0118 | 1 | F | Corrections to stage 2 descriptions for NR positioning | 17.4.0 | +| | RP-99 | RP-230688 | 0119 | 2 | F | Miscellaneous corrections for Positioning Stage2 | 17.4.0 | +| 06/2023 | RP-100 | RP-231412 | 0123 | 2 | F | Miscellaneous corrections on 38.305 | 17.5.0 | +| | RP-100 | RP-231412 | 0124 | 2 | F | Correction to UEPositioningAssistanceInformation | 17.5.0 | +| | RP-100 | RP-231412 | 0125 | 2 | F | Update of information transfer from gNB to LMF | 17.5.0 | +| | RP-100 | RP-231412 | 0126 | 2 | F | Measurements and Assistance Data Transfer | 17.5.0 | +| | RP-100 | RP-231412 | 0127 | 2 | F | Protection Level and Target Integrity Risk | 17.5.0 | +| | RP-100 | RP-231409 | 0131 | 1 | A | APC clarification for SSR positioning | 17.5.0 | +| | RP-100 | RP-231411 | 0133 | 1 | A | Zero Yaw clarification for SSR positioning | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------|--------| +| | RP-100 | RP-231412 | 0135 | 1 | F | Stage 2 procedure for deactivation of MG gap and PPW | 17.5.0 | +| | RP-100 | RP-231412 | 0136 | 1 | F | Alert Limit | 17.5.0 | +| 09/2023 | RP-101 | RP-232667 | 0141 | - | F | Positioning Information Transfer | 17.6.0 | +| | RP-101 | RP-232667 | 0142 | - | F | Correction to missing NRPPa procedures | 17.6.0 | +| 12/2023 | RP-102 | RP-233886 | 0149 | 2 | A | Sequence of Procedure for Multi-RTT positioning correction | 17.7.0 | +| 12/2023 | RP-102 | RP-233881 | 0134 | 2 | C | Positioning restrictions for UE-to-network remote UEs [PosL2RemoteUE] | 18.0.0 | +| | RP-102 | RP-233882 | 0140 | 2 | C | SSR Satellite PCV Residuals [Rel18PCV] | 18.0.0 | +| | RP-102 | RP-233901 | 0150 | 1 | B | Introduction of 'Expanded and improved NR positioning | 18.0.0 | +| | RP-102 | RP-233881 | 0151 | - | B | Forwarding on posSIBs relaying to remote UE [PosL2RemoteUE] | 18.0.0 | +| | RP-102 | RP-233881 | 0153 | - | B | Bluetooth AoA/AoD support [BT-AoA-AoD] | 18.0.0 | +| | RP-102 | RP-233906 | 0154 | - | B | Introduction of network verification of UE location | 18.0.0 | +| | RP-102 | RP-233933 | 0155 | - | B | Introduction of Mobile TRP | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38321/022d1dc5699c55186a08a897cad90392_img.jpg b/marked/Rel-18/38_series/38321/022d1dc5699c55186a08a897cad90392_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..252ef022cb42e50a199bd3aa36b0d137fc8d055b --- /dev/null +++ b/marked/Rel-18/38_series/38321/022d1dc5699c55186a08a897cad90392_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8589692be007a94203659d1f55afa259f67a18082cdbc1df3789adb3bb11e582 +size 11128 diff --git a/marked/Rel-18/38_series/38321/03b1d46bdcb71b03d29c6ab572fb9b33_img.jpg b/marked/Rel-18/38_series/38321/03b1d46bdcb71b03d29c6ab572fb9b33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9f47f8b75792727890479b7ae51f81cd1a7e265 --- /dev/null +++ b/marked/Rel-18/38_series/38321/03b1d46bdcb71b03d29c6ab572fb9b33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40df39eded325d53b3231016a23dadae971b194089592e2cbe8dc2406be9b093 +size 13271 diff --git a/marked/Rel-18/38_series/38321/050e99bf626cb208bd2646b0e0b80708_img.jpg b/marked/Rel-18/38_series/38321/050e99bf626cb208bd2646b0e0b80708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79e5674ec8850226131a5d892d3a1d7606f9079e --- /dev/null +++ b/marked/Rel-18/38_series/38321/050e99bf626cb208bd2646b0e0b80708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14b854e1f6a96be854f093500c2ad06ada82ca2bac7a3fa9a49252019139a9ea +size 11180 diff --git a/marked/Rel-18/38_series/38321/095cb128d8f8cc689f28744e6d5d798d_img.jpg b/marked/Rel-18/38_series/38321/095cb128d8f8cc689f28744e6d5d798d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d8b31600caf337661b60af5ae1580cc7575661b --- /dev/null +++ b/marked/Rel-18/38_series/38321/095cb128d8f8cc689f28744e6d5d798d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518cefe2a8581909145eaf44a6bffc34ee95e0b51e70b0283d327150dee39f2d +size 30222 diff --git a/marked/Rel-18/38_series/38321/0c4c765c70f17bcfc624d914bd321b23_img.jpg b/marked/Rel-18/38_series/38321/0c4c765c70f17bcfc624d914bd321b23_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58ba077f53082a81584bec70f2f2b3dd318c6a3b --- /dev/null +++ b/marked/Rel-18/38_series/38321/0c4c765c70f17bcfc624d914bd321b23_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02d37ed93a59c0e52e809362aa66e2d359d6f1f40922c3001a6da7c549d878d3 +size 40289 diff --git a/marked/Rel-18/38_series/38321/17176612be2d4571951994a0da8a8528_img.jpg b/marked/Rel-18/38_series/38321/17176612be2d4571951994a0da8a8528_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d67a2db1e685b18bc88367c1a1491b9bb14f7038 --- /dev/null +++ b/marked/Rel-18/38_series/38321/17176612be2d4571951994a0da8a8528_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf1de1d179ecaf20fc934e3a424be4e2e3c1b0d6c6aabc4872dcea463926348 +size 14858 diff --git a/marked/Rel-18/38_series/38321/18b439af4d2e65d65a6f8cb3388f7073_img.jpg b/marked/Rel-18/38_series/38321/18b439af4d2e65d65a6f8cb3388f7073_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89bdb7351b4503e239459a2d287294b31e279055 --- /dev/null +++ b/marked/Rel-18/38_series/38321/18b439af4d2e65d65a6f8cb3388f7073_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c92a4c944efe1d98a333356cfe8f9ff961e34e1ab4cc24aa873bb426587957d +size 74663 diff --git a/marked/Rel-18/38_series/38321/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-18/38_series/38321/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0d2f40bc72c6e77284305346c42f3f612fd455d --- /dev/null +++ b/marked/Rel-18/38_series/38321/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01a447e8ec4db1b7ae9c9206d59bdc6b987490efab336ce2a73e49a5b2de0ef2 +size 67863 diff --git a/marked/Rel-18/38_series/38321/1adadd0ae985ea08a9315197cb81a64b_img.jpg b/marked/Rel-18/38_series/38321/1adadd0ae985ea08a9315197cb81a64b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc4acd078ce9c8c90ce813b27d50b690c307caac --- /dev/null +++ b/marked/Rel-18/38_series/38321/1adadd0ae985ea08a9315197cb81a64b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d81816c7373e6b922c5596ccc6ae4a74329e447322a46ea24cb73c98e4a18b12 +size 10371 diff --git a/marked/Rel-18/38_series/38321/1e8845a639705010d5cda27146b8827f_img.jpg b/marked/Rel-18/38_series/38321/1e8845a639705010d5cda27146b8827f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bcc845913b6f8c666e06bf191dfac363e5fd264 --- /dev/null +++ b/marked/Rel-18/38_series/38321/1e8845a639705010d5cda27146b8827f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10e3f90dfbedc4b776fb6b673dcae82b6e23b8a106a602922f9194be2638c6c5 +size 40560 diff --git a/marked/Rel-18/38_series/38321/1eab323450a82831cf78035658284a51_img.jpg b/marked/Rel-18/38_series/38321/1eab323450a82831cf78035658284a51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d5ef4336bf96d05052668250c56dfff304ba543 --- /dev/null +++ b/marked/Rel-18/38_series/38321/1eab323450a82831cf78035658284a51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fb14ffeaad6cb6cf82303a5eb156ffda8100556482696905336eea796657102 +size 21825 diff --git a/marked/Rel-18/38_series/38321/298ee60b468fa168b2d31902628dc264_img.jpg b/marked/Rel-18/38_series/38321/298ee60b468fa168b2d31902628dc264_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6fcd51908e4b607e836fbacf3257ca4aca9a0ab --- /dev/null +++ b/marked/Rel-18/38_series/38321/298ee60b468fa168b2d31902628dc264_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72528fc257e3f11d04f5b63ad5bb82ae41c1b368254bc604267f2a44512cbb61 +size 34679 diff --git a/marked/Rel-18/38_series/38321/31a07dc0617b65d79a4659a346b7ed4c_img.jpg b/marked/Rel-18/38_series/38321/31a07dc0617b65d79a4659a346b7ed4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81cf2854b5a63726cea0f7ade8bdf1dd31ab1086 --- /dev/null +++ b/marked/Rel-18/38_series/38321/31a07dc0617b65d79a4659a346b7ed4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b0a03fe943c885737a2fda42762927afdc7b0c1817944f1904e098678feff88 +size 13025 diff --git a/marked/Rel-18/38_series/38321/31f5b6310f831ca3ea4f18453980c070_img.jpg b/marked/Rel-18/38_series/38321/31f5b6310f831ca3ea4f18453980c070_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57d20984c2c75148b437ec5aec1b25ac36ca27e9 --- /dev/null +++ b/marked/Rel-18/38_series/38321/31f5b6310f831ca3ea4f18453980c070_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:915f3eba8016df810a27333c3f99dd2ce0e6d48f560d10e2df019048622f25e6 +size 10659 diff --git a/marked/Rel-18/38_series/38321/32b4e4122da4364a971829ca7166556e_img.jpg b/marked/Rel-18/38_series/38321/32b4e4122da4364a971829ca7166556e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d5c4477a0f3c587ab413d160d8ded1bb9544c61 --- /dev/null +++ b/marked/Rel-18/38_series/38321/32b4e4122da4364a971829ca7166556e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca57c906efba1cc0257b263c574e153c8a8b56ed440fddaf4bb99ed1794f059c +size 50679 diff --git a/marked/Rel-18/38_series/38321/340e10d75c9e473c73f2f1f9037d8afc_img.jpg b/marked/Rel-18/38_series/38321/340e10d75c9e473c73f2f1f9037d8afc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d51a518cfa38a194dd4b56c1f5190d3f6977746 --- /dev/null +++ b/marked/Rel-18/38_series/38321/340e10d75c9e473c73f2f1f9037d8afc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:612be74039198c5ef4856bfb34e3cd1536f07132933c363517150739e2e68c78 +size 7706 diff --git a/marked/Rel-18/38_series/38321/34f6baf47c53b490142dbe71f900f406_img.jpg b/marked/Rel-18/38_series/38321/34f6baf47c53b490142dbe71f900f406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63441d855c2bd2ff0fab68bae6a953f52a321cde --- /dev/null +++ b/marked/Rel-18/38_series/38321/34f6baf47c53b490142dbe71f900f406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca3dedfba77e31f125e74366662d2934d2ae2919422c0e8d7e2e8366c3358dbd +size 41198 diff --git a/marked/Rel-18/38_series/38321/351243fd59cdae993f191da9ebb48016_img.jpg b/marked/Rel-18/38_series/38321/351243fd59cdae993f191da9ebb48016_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7405682914dbb4156924012b120375ce31c5ea90 --- /dev/null +++ b/marked/Rel-18/38_series/38321/351243fd59cdae993f191da9ebb48016_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e0a04353d74416a7a4a365c377279f4e3b65d0e70b52ed7dff6e440326e9efa +size 38395 diff --git a/marked/Rel-18/38_series/38321/37f059615fb8a05f4da791eb7fde1190_img.jpg b/marked/Rel-18/38_series/38321/37f059615fb8a05f4da791eb7fde1190_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71c23a1adebe179fd24e2fbd99f9739caaa658ea --- /dev/null +++ b/marked/Rel-18/38_series/38321/37f059615fb8a05f4da791eb7fde1190_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6757873568155961ee395a8b03ce819e6c0fc1fab9bc87e469d05595ece77343 +size 30879 diff --git a/marked/Rel-18/38_series/38321/38e71c92bab0b1f77d50284f69e399f4_img.jpg b/marked/Rel-18/38_series/38321/38e71c92bab0b1f77d50284f69e399f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ac06b5e1681670f948ad57dcfdcb4822b41e67a --- /dev/null +++ b/marked/Rel-18/38_series/38321/38e71c92bab0b1f77d50284f69e399f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:232cb1a6d7e8b4aa9372fc4605d60e381d4274d2ff1ffa14d26a9e8eda5eac6f +size 33561 diff --git a/marked/Rel-18/38_series/38321/39d46d66998e38df22b80b0317aa58b6_img.jpg b/marked/Rel-18/38_series/38321/39d46d66998e38df22b80b0317aa58b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbf7e70bd30228e058d3d42b973c5b458cefeda1 --- /dev/null +++ b/marked/Rel-18/38_series/38321/39d46d66998e38df22b80b0317aa58b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b51222052bbb961b1d22e26412d98757712e05e4efd67e6776fa6b41d5ce0ca6 +size 32488 diff --git a/marked/Rel-18/38_series/38321/3a587aa09b68d647ac0381e7e1c7cfec_img.jpg b/marked/Rel-18/38_series/38321/3a587aa09b68d647ac0381e7e1c7cfec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c8c80d7f8043e904c4d605903d50f253b06f65c --- /dev/null +++ b/marked/Rel-18/38_series/38321/3a587aa09b68d647ac0381e7e1c7cfec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56d02c19f2544fa7d16f1223b74a8ec3062ff8a236b25d54eb4546951d13951c +size 10407 diff --git a/marked/Rel-18/38_series/38321/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/Rel-18/38_series/38321/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..321d8f4daa2a44b36c434d35f7ff69b51ec9a67d --- /dev/null +++ b/marked/Rel-18/38_series/38321/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc10c4eb236882e68a37192e8c74a136b34711495bc8432f6048d31a9be1596f +size 72258 diff --git a/marked/Rel-18/38_series/38321/41fdfbcb8ced232d5050bafa1d010287_img.jpg b/marked/Rel-18/38_series/38321/41fdfbcb8ced232d5050bafa1d010287_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ab35c88ee7dddec9a0c7210becf54dd326f137f --- /dev/null +++ b/marked/Rel-18/38_series/38321/41fdfbcb8ced232d5050bafa1d010287_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40bde09350c7dcd7c655cf4ec8fbd556da8116f19648f927f8d5044b7b01e129 +size 10396 diff --git a/marked/Rel-18/38_series/38321/43f0f64c797927f9635b55fa9eb25246_img.jpg b/marked/Rel-18/38_series/38321/43f0f64c797927f9635b55fa9eb25246_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8b7976a30b9c4619b96a8cddcf3bbaef82c9ceb --- /dev/null +++ b/marked/Rel-18/38_series/38321/43f0f64c797927f9635b55fa9eb25246_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:642f1fd9a2776745ff8494c08449cf5fc2e920175ce3dbb1f0aaaf4073eb2cf5 +size 44324 diff --git a/marked/Rel-18/38_series/38321/45902eaeac38a0b8d0e670b205695d13_img.jpg b/marked/Rel-18/38_series/38321/45902eaeac38a0b8d0e670b205695d13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7da9cb4e7b059186b94e72a5b560d468e1758515 --- /dev/null +++ b/marked/Rel-18/38_series/38321/45902eaeac38a0b8d0e670b205695d13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82027eb926d3c9c8979a43cce2eaaca3bdf603bb049638af05bda28e3d7613ff +size 13867 diff --git a/marked/Rel-18/38_series/38321/460b69ceb6eadef472ed6c71b44e920b_img.jpg b/marked/Rel-18/38_series/38321/460b69ceb6eadef472ed6c71b44e920b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45e68dd65ce69b5b3bc559ae7cf01223ae62a41a --- /dev/null +++ b/marked/Rel-18/38_series/38321/460b69ceb6eadef472ed6c71b44e920b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33b667b6a864b1234c7f17fb6a6d9c51930fd70adc73a769f3bf7bf13e1c6d8d +size 20754 diff --git a/marked/Rel-18/38_series/38321/463f6f3874311dc4af977dd4c6290166_img.jpg b/marked/Rel-18/38_series/38321/463f6f3874311dc4af977dd4c6290166_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3efa74eee7f55de955ce7f90cb9776427742f206 --- /dev/null +++ b/marked/Rel-18/38_series/38321/463f6f3874311dc4af977dd4c6290166_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:368f6cdca6afa8015e068936637dc1031a6973c7f2fa831d539a567e3f91ab26 +size 12629 diff --git a/marked/Rel-18/38_series/38321/4a68079a30c96e3aa582574ebc524e46_img.jpg b/marked/Rel-18/38_series/38321/4a68079a30c96e3aa582574ebc524e46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a41ecbcd36f1fbfed73d48c3d5bf96ed9d897116 --- /dev/null +++ b/marked/Rel-18/38_series/38321/4a68079a30c96e3aa582574ebc524e46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6566f6296a8625e7b16698798b12632c3ed3e1058f68db103e55a0e67bcc234 +size 9027 diff --git a/marked/Rel-18/38_series/38321/4c8cb1c6034c92302897fc05e9577ec3_img.jpg b/marked/Rel-18/38_series/38321/4c8cb1c6034c92302897fc05e9577ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91f457463204cfd509d6bab6ead69faa83823ee2 --- /dev/null +++ b/marked/Rel-18/38_series/38321/4c8cb1c6034c92302897fc05e9577ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dc3e7dd12da5e9b4b2e76b625d3291786406e753e762f93c271dda7f3805187 +size 10552 diff --git a/marked/Rel-18/38_series/38321/4cb38c4f736fc47ecbb2641eb07be92f_img.jpg b/marked/Rel-18/38_series/38321/4cb38c4f736fc47ecbb2641eb07be92f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52c537483372fc68738ada86df179c97bbb39ece --- /dev/null +++ b/marked/Rel-18/38_series/38321/4cb38c4f736fc47ecbb2641eb07be92f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e7db7fadbda8e3bf5b34453be439fcf221269ba11a3d06343c3c009508578bd +size 12092 diff --git a/marked/Rel-18/38_series/38321/4dacbe3dedea8f941e6500272dce3539_img.jpg b/marked/Rel-18/38_series/38321/4dacbe3dedea8f941e6500272dce3539_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76517d9531a358422ab61758ba0372596b692f18 --- /dev/null +++ b/marked/Rel-18/38_series/38321/4dacbe3dedea8f941e6500272dce3539_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:507a22e19355f1a3c8e6d727ca4c11a3255968e1dc5da1ea94e5c3ab0888d59e +size 34220 diff --git a/marked/Rel-18/38_series/38321/4e191c69ad9a8ccefa7beb93c5e36591_img.jpg b/marked/Rel-18/38_series/38321/4e191c69ad9a8ccefa7beb93c5e36591_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c7a96f4b70ca295bb4ca083ff4ad384d337734f --- /dev/null +++ b/marked/Rel-18/38_series/38321/4e191c69ad9a8ccefa7beb93c5e36591_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb95f2b0e7d029a8eb7d7aa7fec003c73739e2887fb6c27992a667293ef0ebd +size 58014 diff --git a/marked/Rel-18/38_series/38321/515b883cf43839048d22dbcec99d7d38_img.jpg b/marked/Rel-18/38_series/38321/515b883cf43839048d22dbcec99d7d38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c2bb67c6cc8beec8900131604d6cbcb6574e3b1 --- /dev/null +++ b/marked/Rel-18/38_series/38321/515b883cf43839048d22dbcec99d7d38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ca998038b231033e72285a894a157ca71dc0fc07510ccdc8e9d4b84398f99a6 +size 57513 diff --git a/marked/Rel-18/38_series/38321/53722b37637a6c7f2fa2a01722a164fd_img.jpg b/marked/Rel-18/38_series/38321/53722b37637a6c7f2fa2a01722a164fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..100e490b56199f70a0250614216e2aa135df82d3 --- /dev/null +++ b/marked/Rel-18/38_series/38321/53722b37637a6c7f2fa2a01722a164fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a0b7499af939f3309d65d94dcf0e3deccf31e4ee7a6b8a0a6c08aacdb01d41c +size 34489 diff --git a/marked/Rel-18/38_series/38321/54d030ecf3f147af8773b8a23549856e_img.jpg b/marked/Rel-18/38_series/38321/54d030ecf3f147af8773b8a23549856e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bd908eef3a3481df56e3e3102e759b422bf00c5 --- /dev/null +++ b/marked/Rel-18/38_series/38321/54d030ecf3f147af8773b8a23549856e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21a94cf0411bcc36b2b501065ea557a4586b0704a24f4f334601433dbc882a76 +size 47279 diff --git a/marked/Rel-18/38_series/38321/552214429c77fe87e98d6ec919ad0041_img.jpg b/marked/Rel-18/38_series/38321/552214429c77fe87e98d6ec919ad0041_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2e2cd6fb5a769223f06bd8238e957cb70a2ec1b --- /dev/null +++ b/marked/Rel-18/38_series/38321/552214429c77fe87e98d6ec919ad0041_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91795b7836832866d62d29189922c33dd228838fe131adf2d8acc98b5e5cdc72 +size 25860 diff --git a/marked/Rel-18/38_series/38321/5538dc47e91669a5729142788208c27d_img.jpg b/marked/Rel-18/38_series/38321/5538dc47e91669a5729142788208c27d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df9be4feaf460162352ba430f957855fb3d9a6f7 --- /dev/null +++ b/marked/Rel-18/38_series/38321/5538dc47e91669a5729142788208c27d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2103823b2db53f4aeab069afb4aa39f59eccfda00d775a7b5a6e278f9f8126da +size 75411 diff --git a/marked/Rel-18/38_series/38321/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg b/marked/Rel-18/38_series/38321/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6bbdaa375e1f98c87c98fb4ac1c9059eb174f38 --- /dev/null +++ b/marked/Rel-18/38_series/38321/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f31229eab5b7ff1e5f75f390ede7f00e9c5369f96f1b434e2c93da3686b57ae0 +size 23583 diff --git a/marked/Rel-18/38_series/38321/5f5a8699620b98137f36540ead9912f9_img.jpg b/marked/Rel-18/38_series/38321/5f5a8699620b98137f36540ead9912f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..626248bedbdde711f30109add5921fe6eabdfca3 --- /dev/null +++ b/marked/Rel-18/38_series/38321/5f5a8699620b98137f36540ead9912f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4490715cd342412d48184b0f7f10e65f752085191bc78511f32bddc1cec27a7e +size 33719 diff --git a/marked/Rel-18/38_series/38321/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38321/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb9bd62b321aca82a59cba5ff47e7a80a52b760d --- /dev/null +++ b/marked/Rel-18/38_series/38321/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14f9f929d723b632eeaa6abbb5cb9880bcefece3335c137ff49dddc380c59ad0 +size 9455 diff --git a/marked/Rel-18/38_series/38321/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38321/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32429263fb45de37d0d0b0d2578f9c33e4cd9513 --- /dev/null +++ b/marked/Rel-18/38_series/38321/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623781921dce0cbaa61fa69398c0032452192458b8f34c4a5f2025d853c1f3e0 +size 6558 diff --git a/marked/Rel-18/38_series/38321/66a8d74a23329358359c28ab4b557a23_img.jpg b/marked/Rel-18/38_series/38321/66a8d74a23329358359c28ab4b557a23_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68bbc4583c9b7efbf5586dfdc2d3ed398efadeb9 --- /dev/null +++ b/marked/Rel-18/38_series/38321/66a8d74a23329358359c28ab4b557a23_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c04ca3c90d26f8b94bb6fef430104c9c9e38e372c8dfad347bd7e8a63bb337c2 +size 15539 diff --git a/marked/Rel-18/38_series/38321/67f75a54aad5f67ad7c6eda9e1a676c9_img.jpg b/marked/Rel-18/38_series/38321/67f75a54aad5f67ad7c6eda9e1a676c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a5cdffab761a8733282f91c04d74f66ab0581d4 --- /dev/null +++ b/marked/Rel-18/38_series/38321/67f75a54aad5f67ad7c6eda9e1a676c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a286fb6cf14e0e578fa7c595bdbb75e4d19497a70f8ebef91d52695e4e3ffc0 +size 46019 diff --git a/marked/Rel-18/38_series/38321/704c5137e8e6d3474b72294e6b9c88e4_img.jpg b/marked/Rel-18/38_series/38321/704c5137e8e6d3474b72294e6b9c88e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482d53290bb837126c374c11a47d5b515ec23648 --- /dev/null +++ b/marked/Rel-18/38_series/38321/704c5137e8e6d3474b72294e6b9c88e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e2f5feb163b39167a6a4b2a9e70089c5847e8e3065e74ede8f23de606d9b16 +size 35820 diff --git a/marked/Rel-18/38_series/38321/74340c36eadb11d858e925d7b77260bf_img.jpg b/marked/Rel-18/38_series/38321/74340c36eadb11d858e925d7b77260bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ecbc9569c4dd414d6a61d00981f3e4c097a358a --- /dev/null +++ b/marked/Rel-18/38_series/38321/74340c36eadb11d858e925d7b77260bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3af19c9be2e62bad9e25b09ca31ecb6e35c2a58d84012aa9e399cfe3f40e7143 +size 10001 diff --git a/marked/Rel-18/38_series/38321/761efbc82a397a77e5e4a0afc95a3d44_img.jpg b/marked/Rel-18/38_series/38321/761efbc82a397a77e5e4a0afc95a3d44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..762989c1fcf23c61f702aec3fd652b1e42adb72c --- /dev/null +++ b/marked/Rel-18/38_series/38321/761efbc82a397a77e5e4a0afc95a3d44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c133e8f61bd578c55d7b6ab3340166d6731268b6c6e891538fac60d81c8bff8 +size 21774 diff --git a/marked/Rel-18/38_series/38321/76aaf09224a8270997539c0939061af7_img.jpg b/marked/Rel-18/38_series/38321/76aaf09224a8270997539c0939061af7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..423c8032730420171023b36152e33b3af05d8024 --- /dev/null +++ b/marked/Rel-18/38_series/38321/76aaf09224a8270997539c0939061af7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de81006bb163d4db882aa1b151fa0db2d05d9189af7f87c508b331aecb7766f0 +size 8012 diff --git a/marked/Rel-18/38_series/38321/78ecffc23b5831341cca689039041918_img.jpg b/marked/Rel-18/38_series/38321/78ecffc23b5831341cca689039041918_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a89c2b475fa79bf54ddf40a2f5e17b0f4b45e63 --- /dev/null +++ b/marked/Rel-18/38_series/38321/78ecffc23b5831341cca689039041918_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e83097f138b046179091c986e90e8b24a1f16621fb7f65d76ef7f8c5ecf4f32f +size 8606 diff --git a/marked/Rel-18/38_series/38321/790a528e79f24630685ee621c554b633_img.jpg b/marked/Rel-18/38_series/38321/790a528e79f24630685ee621c554b633_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..140d3c9a2eea2c328ef51ce312336cdcb4d6dd75 --- /dev/null +++ b/marked/Rel-18/38_series/38321/790a528e79f24630685ee621c554b633_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b52589a78c83eb4893284a576f63eddd13cd28bf3a0d23f2a14334b43f42e10c +size 9683 diff --git a/marked/Rel-18/38_series/38321/7a08792c70e070d3716830bdd77391ab_img.jpg b/marked/Rel-18/38_series/38321/7a08792c70e070d3716830bdd77391ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ff85cefeb9856dc0bddc9ac47bc1f9f66324a31 --- /dev/null +++ b/marked/Rel-18/38_series/38321/7a08792c70e070d3716830bdd77391ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d294a6357d3e4b459b3e35b3cff3fd3201061333097e91d007ac2cd31dabb83 +size 25848 diff --git a/marked/Rel-18/38_series/38321/7c5564b9e8a382de9dfa5f44116cbf2b_img.jpg b/marked/Rel-18/38_series/38321/7c5564b9e8a382de9dfa5f44116cbf2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56674c9e6ce52fe9d6b84ed146ff63f2c0e3293d --- /dev/null +++ b/marked/Rel-18/38_series/38321/7c5564b9e8a382de9dfa5f44116cbf2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b3dbc9124431a1902398ec4d31bf18e6f11aee026461bb5e69693667d8a2634 +size 44451 diff --git a/marked/Rel-18/38_series/38321/83fd0d406cba6f9c189e77e05859a600_img.jpg b/marked/Rel-18/38_series/38321/83fd0d406cba6f9c189e77e05859a600_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2facc945add5b1f6cbffe03357d330e50c3a96c7 --- /dev/null +++ b/marked/Rel-18/38_series/38321/83fd0d406cba6f9c189e77e05859a600_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07eb8bf91255084ec9464f3a57109024d871e0ec18d2adfa22385c4913e6fd2d +size 55114 diff --git a/marked/Rel-18/38_series/38321/8450f105f39b5cb87eddb44d739cb1b2_img.jpg b/marked/Rel-18/38_series/38321/8450f105f39b5cb87eddb44d739cb1b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9714fba4806b9a62b1e03a0d9c861d27a19150c2 --- /dev/null +++ b/marked/Rel-18/38_series/38321/8450f105f39b5cb87eddb44d739cb1b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f47ab890f543b38f9fef8a3ba0ac37dc7db1b88668c6915a1954480fbf864d4 +size 31222 diff --git a/marked/Rel-18/38_series/38321/85e117a13c46e2b4c8b69e1179f25f14_img.jpg b/marked/Rel-18/38_series/38321/85e117a13c46e2b4c8b69e1179f25f14_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf507f35acc88e2df2972519ce6ca582afbee7f8 --- /dev/null +++ b/marked/Rel-18/38_series/38321/85e117a13c46e2b4c8b69e1179f25f14_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f92278eb685b8930f456c8988acddc594ed300e44d81fd47341d7f08a1b261b +size 42402 diff --git a/marked/Rel-18/38_series/38321/89c2f25f101a9f211842647dd2373be7_img.jpg b/marked/Rel-18/38_series/38321/89c2f25f101a9f211842647dd2373be7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee0623dcb2cf24af413755860d7b1b7e66de9e67 --- /dev/null +++ b/marked/Rel-18/38_series/38321/89c2f25f101a9f211842647dd2373be7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc1212f95c86d15a1fa745942ac513c2141c173384476d60dd07b5c3950e6332 +size 9757 diff --git a/marked/Rel-18/38_series/38321/8c05782074bb11421b43f2d5d6799b62_img.jpg b/marked/Rel-18/38_series/38321/8c05782074bb11421b43f2d5d6799b62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ce0ba4344953f3b87b03bdba10c964345a01886 --- /dev/null +++ b/marked/Rel-18/38_series/38321/8c05782074bb11421b43f2d5d6799b62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea57aef569cc3223c76d67bb9f2cf073848a3cede39c06115f74e4b01eff91a9 +size 55544 diff --git a/marked/Rel-18/38_series/38321/9144d599bb5bf98cd607202d768a4956_img.jpg b/marked/Rel-18/38_series/38321/9144d599bb5bf98cd607202d768a4956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51f305707baf0860d9246acaf8d01150aa7b4826 --- /dev/null +++ b/marked/Rel-18/38_series/38321/9144d599bb5bf98cd607202d768a4956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:019c4008914852c5f8393c12c0967eb18a2c60a9de81401beebfd1916eeb9a2a +size 26203 diff --git a/marked/Rel-18/38_series/38321/931bd52904f67b17796a38b47af51e30_img.jpg b/marked/Rel-18/38_series/38321/931bd52904f67b17796a38b47af51e30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d9201babbd8a8f9b8119da09955de09dffe2d6b --- /dev/null +++ b/marked/Rel-18/38_series/38321/931bd52904f67b17796a38b47af51e30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dee71315f3be11a2710f2ff09214e829e39da4abf92da46c4d9f3640301dca38 +size 23702 diff --git a/marked/Rel-18/38_series/38321/93c9262c68d25c26b8cf8cd547554d9f_img.jpg b/marked/Rel-18/38_series/38321/93c9262c68d25c26b8cf8cd547554d9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96a0d245dfb78bca14944defc481ca74f08e5109 --- /dev/null +++ b/marked/Rel-18/38_series/38321/93c9262c68d25c26b8cf8cd547554d9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe7a3ac80f07a78a9957f8c12fe28f0a8664547492560e6da0f513c95165f3a +size 46675 diff --git a/marked/Rel-18/38_series/38321/95468bd1e191c4b5b2f6382f413b175e_img.jpg b/marked/Rel-18/38_series/38321/95468bd1e191c4b5b2f6382f413b175e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e36931fdc46599f557cc855b2ba017c085480ef6 --- /dev/null +++ b/marked/Rel-18/38_series/38321/95468bd1e191c4b5b2f6382f413b175e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:520d2218582bfe8b616ad8f7e85dce5c78587ff6bb6d7ac3c3cde0103ae59e0a +size 9458 diff --git a/marked/Rel-18/38_series/38321/9753ea14ea728b0e8fd5c6fde5029d66_img.jpg b/marked/Rel-18/38_series/38321/9753ea14ea728b0e8fd5c6fde5029d66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d34a76cfc0ed1736f43542b237a8262503bb5e39 --- /dev/null +++ b/marked/Rel-18/38_series/38321/9753ea14ea728b0e8fd5c6fde5029d66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38454735592bb6cc3ab9e60c4e07c8fced24181c6b86c6dbdc118ac6ed9d49cb +size 35726 diff --git a/marked/Rel-18/38_series/38321/9ce1c6956cda991930d500ee19416e05_img.jpg b/marked/Rel-18/38_series/38321/9ce1c6956cda991930d500ee19416e05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4bad1d77fb1ab473711a0d8d56697a20ed4a390 --- /dev/null +++ b/marked/Rel-18/38_series/38321/9ce1c6956cda991930d500ee19416e05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c8b17696783ae2dd490c25513b630175cced6e51a41ba1d35e711e7ba367454 +size 14658 diff --git a/marked/Rel-18/38_series/38321/9d05fd876dc28e2fc2d83e9495144a4d_img.jpg b/marked/Rel-18/38_series/38321/9d05fd876dc28e2fc2d83e9495144a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..063dbbfe8141a5f0750d6fad1df7f1489dcd1b87 --- /dev/null +++ b/marked/Rel-18/38_series/38321/9d05fd876dc28e2fc2d83e9495144a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b57d1729ac2c17dd97eab7302d20f679afa72e3f2b295ddf1cb9987d3e508d8 +size 9417 diff --git a/marked/Rel-18/38_series/38321/9d9e171542e7312c3fcf0b217bca5af1_img.jpg b/marked/Rel-18/38_series/38321/9d9e171542e7312c3fcf0b217bca5af1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f29a66734e490666f0438a71ad65623acee5e87b --- /dev/null +++ b/marked/Rel-18/38_series/38321/9d9e171542e7312c3fcf0b217bca5af1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09e59f002de1b01e98c2410df86f31e214cdc42e71092262a4aff2152ca93df0 +size 17231 diff --git a/marked/Rel-18/38_series/38321/9dc21f873b6fe32363beafc29e18ba0f_img.jpg b/marked/Rel-18/38_series/38321/9dc21f873b6fe32363beafc29e18ba0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310c7703228ffb9aca3719bc2a15ad88b19fe49b --- /dev/null +++ b/marked/Rel-18/38_series/38321/9dc21f873b6fe32363beafc29e18ba0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c310a75208d710aee4585e2b2624b32f817e21f5716dc26749236637e3a75fca +size 32417 diff --git a/marked/Rel-18/38_series/38321/9e72357b676f470a106b2011d67d4410_img.jpg b/marked/Rel-18/38_series/38321/9e72357b676f470a106b2011d67d4410_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5de5eb31b2b0468774bdb8c32f6375c441989f9 --- /dev/null +++ b/marked/Rel-18/38_series/38321/9e72357b676f470a106b2011d67d4410_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a432176eec7161dd85397d75bb9a2e393f54266478b2d8c72f6a550000a0defb +size 38641 diff --git a/marked/Rel-18/38_series/38321/9f8138ddf4315e46d5c5255e919adf80_img.jpg b/marked/Rel-18/38_series/38321/9f8138ddf4315e46d5c5255e919adf80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6050a4f46ce06bb25fe397e2573d6a90265abe4d --- /dev/null +++ b/marked/Rel-18/38_series/38321/9f8138ddf4315e46d5c5255e919adf80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09bc1c662f2539c7da740d0582511462631a00a0e6ff07295ae31410fc0cc381 +size 12395 diff --git a/marked/Rel-18/38_series/38321/a194ad55e5e2b04f07456c3c728fae88_img.jpg b/marked/Rel-18/38_series/38321/a194ad55e5e2b04f07456c3c728fae88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c546598800da672d4044eb197b27f2bfc2b1a8cb --- /dev/null +++ b/marked/Rel-18/38_series/38321/a194ad55e5e2b04f07456c3c728fae88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d9f7dda00e263958bd6c3e675a1df8d76828ecff4d45e2d6b4904ae06c2cb1 +size 28505 diff --git a/marked/Rel-18/38_series/38321/a6df95ba6d9243e76701e4db67bf02e3_img.jpg b/marked/Rel-18/38_series/38321/a6df95ba6d9243e76701e4db67bf02e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b023eb439836d26f53585f02ea6394f0ef6f826f --- /dev/null +++ b/marked/Rel-18/38_series/38321/a6df95ba6d9243e76701e4db67bf02e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed584948b58206dc1b6efb9f178883e1d92ed5c00dfca5d4168f344aa30b08d +size 17840 diff --git a/marked/Rel-18/38_series/38321/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg b/marked/Rel-18/38_series/38321/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7284ec5af8ac596e09bb04415506946077e809f2 --- /dev/null +++ b/marked/Rel-18/38_series/38321/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:122cb99d6b1a467d6f36fd36888b81043d9aaea81c23a6b7c6844b953d98b1e1 +size 8889 diff --git a/marked/Rel-18/38_series/38321/b2f6158e74f297659bf41c5939b2c1e0_img.jpg b/marked/Rel-18/38_series/38321/b2f6158e74f297659bf41c5939b2c1e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62fa89932a3aceefa09ec9e2b849462b111fa544 --- /dev/null +++ b/marked/Rel-18/38_series/38321/b2f6158e74f297659bf41c5939b2c1e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:543ce1261d0ba1099b1b68dd85d8f80e9458e9661f19b8d1911110459583e23a +size 21294 diff --git a/marked/Rel-18/38_series/38321/b52be7781106e5dc2fe2720cbee7131f_img.jpg b/marked/Rel-18/38_series/38321/b52be7781106e5dc2fe2720cbee7131f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f43a82ea51d62ac45bcf38621769d6fe53e3afc8 --- /dev/null +++ b/marked/Rel-18/38_series/38321/b52be7781106e5dc2fe2720cbee7131f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b7d8479621c7e23aa4010dc070428765b0db3a454c5a8f1aa3a60b216057cd3 +size 13031 diff --git a/marked/Rel-18/38_series/38321/b6783b3a83a0ade1dd26a3f176399cc2_img.jpg b/marked/Rel-18/38_series/38321/b6783b3a83a0ade1dd26a3f176399cc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99aaf18e9117461231312ef13183f7f639e25b88 --- /dev/null +++ b/marked/Rel-18/38_series/38321/b6783b3a83a0ade1dd26a3f176399cc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bbe0727a882d60465ae499ffb9d0fbaecf7c089478071716535dc28ddab918c +size 38443 diff --git a/marked/Rel-18/38_series/38321/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg b/marked/Rel-18/38_series/38321/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db34d570b323a8e8c1f0e351a91e3adacfb9c39 --- /dev/null +++ b/marked/Rel-18/38_series/38321/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10be583849bb8ba972e00c8b7a4bc604c936023e6255350b3d3850398ad1bd8b +size 27505 diff --git a/marked/Rel-18/38_series/38321/b86a5928690177a50c4fe95603ed3988_img.jpg b/marked/Rel-18/38_series/38321/b86a5928690177a50c4fe95603ed3988_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87c3f1add952a67b8beba0f3dba84b18743145ff --- /dev/null +++ b/marked/Rel-18/38_series/38321/b86a5928690177a50c4fe95603ed3988_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f172451ca20a5d328d3af9cd2922fb5c43b2de5ffbc25a0ad6763ef24364a39c +size 18868 diff --git a/marked/Rel-18/38_series/38321/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-18/38_series/38321/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cdcfd2bed6178a20c6ee3691d0d6f0184ef69de --- /dev/null +++ b/marked/Rel-18/38_series/38321/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6022c0e99aecc13fceb809f393cba8e7b8bbeec1cff3d18c25c1ba73ea00d26 +size 43784 diff --git a/marked/Rel-18/38_series/38321/bcc5e48817a7383c980f2165bb571508_img.jpg b/marked/Rel-18/38_series/38321/bcc5e48817a7383c980f2165bb571508_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01c83b306ca5dedc94176aa00e800ee41bed17f3 --- /dev/null +++ b/marked/Rel-18/38_series/38321/bcc5e48817a7383c980f2165bb571508_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e36752ac43532b3e28fa7ef3614197d8ca965687d8e6b35f2e86d51685cbf1 +size 49215 diff --git a/marked/Rel-18/38_series/38321/bdedc4445bc14629d68d2fed555b83e9_img.jpg b/marked/Rel-18/38_series/38321/bdedc4445bc14629d68d2fed555b83e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c38e9d195ecc36936a38c35f91804d7035d5aa09 --- /dev/null +++ b/marked/Rel-18/38_series/38321/bdedc4445bc14629d68d2fed555b83e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:691fe22574d46499582e1ca9d25a2dc8374fc92cf4d2b412f7151fd292cf9cf6 +size 69596 diff --git a/marked/Rel-18/38_series/38321/c69cb6aeb2c0a91ab4ba98bddf14e55a_img.jpg b/marked/Rel-18/38_series/38321/c69cb6aeb2c0a91ab4ba98bddf14e55a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d23db2fd1beb703ad385a225d8c502feb1edb09 --- /dev/null +++ b/marked/Rel-18/38_series/38321/c69cb6aeb2c0a91ab4ba98bddf14e55a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:051d7eb1fe0f0c7d05d4d015ad9e8f57941542f8d904b7e3ffe2867362530251 +size 32560 diff --git a/marked/Rel-18/38_series/38321/cd2b491634dadbccc5b38620840d01f9_img.jpg b/marked/Rel-18/38_series/38321/cd2b491634dadbccc5b38620840d01f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ff32d968f34f931d79ea7178de298ed92d180e0 --- /dev/null +++ b/marked/Rel-18/38_series/38321/cd2b491634dadbccc5b38620840d01f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:464721835a48b813cac2d027e3282562dde70d9b18ce22ed180e9a1972e14e69 +size 53548 diff --git a/marked/Rel-18/38_series/38321/cd2dcc38fd9463990b9abcd7470b088a_img.jpg b/marked/Rel-18/38_series/38321/cd2dcc38fd9463990b9abcd7470b088a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16c71bfaa758653cd236aff038b25bb622d0b0d9 --- /dev/null +++ b/marked/Rel-18/38_series/38321/cd2dcc38fd9463990b9abcd7470b088a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dafcd81127f73c9b678d242bdd27dc0657660c7942f8d00c32beec7bc14c366 +size 16500 diff --git a/marked/Rel-18/38_series/38321/cdb980c2fe504f3132b907d4de707c7f_img.jpg b/marked/Rel-18/38_series/38321/cdb980c2fe504f3132b907d4de707c7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d19242328e4dd6cc668c9c69560a112524ee72cd --- /dev/null +++ b/marked/Rel-18/38_series/38321/cdb980c2fe504f3132b907d4de707c7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e97e4ddd3f1a3f3d4822be3ec2c9b874f13e6108cad6705499e1671ff37178ec +size 22336 diff --git a/marked/Rel-18/38_series/38321/d1203e87a330a98abf08c99d65e5a24b_img.jpg b/marked/Rel-18/38_series/38321/d1203e87a330a98abf08c99d65e5a24b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e36716ffff6f278f3ef64adaf04e29afee1da967 --- /dev/null +++ b/marked/Rel-18/38_series/38321/d1203e87a330a98abf08c99d65e5a24b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:759f8cae4fd9356340253e76d3e47c2176f9e2ae67335152518bd6783fd5a652 +size 23829 diff --git a/marked/Rel-18/38_series/38321/d1dcd25a3d039a7d41d6699076934c92_img.jpg b/marked/Rel-18/38_series/38321/d1dcd25a3d039a7d41d6699076934c92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b63addbf9135d598ea9f46977c141b3d0a62170 --- /dev/null +++ b/marked/Rel-18/38_series/38321/d1dcd25a3d039a7d41d6699076934c92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b731f2389b80d8c3c4696f5212311736e7acfd76228870ce29c823ad938d43c3 +size 32823 diff --git a/marked/Rel-18/38_series/38321/dd0d48f6aaa992a96a8c48ba232c56e2_img.jpg b/marked/Rel-18/38_series/38321/dd0d48f6aaa992a96a8c48ba232c56e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8fc64ea353582e42d82bbfe751d8ae69e7d8f7f --- /dev/null +++ b/marked/Rel-18/38_series/38321/dd0d48f6aaa992a96a8c48ba232c56e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce0f68b08725e2bce637e382e63573b4c1e0299fe155135e2d8d374c3fdf5894 +size 10854 diff --git a/marked/Rel-18/38_series/38321/dd1dd483573cc9c3bc666a371f59d5d7_img.jpg b/marked/Rel-18/38_series/38321/dd1dd483573cc9c3bc666a371f59d5d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ee84183910f39b5df257e65b8b8a05599e7c1a6 --- /dev/null +++ b/marked/Rel-18/38_series/38321/dd1dd483573cc9c3bc666a371f59d5d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c60e662ec12dda36f09a096f59a33578c644e81fd125abda7c9e347922b31b9 +size 15538 diff --git a/marked/Rel-18/38_series/38321/dd2ddef02cef83a06acfc3e710b36564_img.jpg b/marked/Rel-18/38_series/38321/dd2ddef02cef83a06acfc3e710b36564_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21dd8ea421fe5ea60a11c78e92e23a86c665e94e --- /dev/null +++ b/marked/Rel-18/38_series/38321/dd2ddef02cef83a06acfc3e710b36564_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17366da514d6623f5d7b1412d83a08c1185b748544f92b4205a5af0de083ac12 +size 17717 diff --git a/marked/Rel-18/38_series/38321/df72bd7468eb8bd59e911d0b5cb7a810_img.jpg b/marked/Rel-18/38_series/38321/df72bd7468eb8bd59e911d0b5cb7a810_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74ca06ed6ad63a40af8739a95557deee0bdf397b --- /dev/null +++ b/marked/Rel-18/38_series/38321/df72bd7468eb8bd59e911d0b5cb7a810_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dff4089984d43ab13d572342e6070e805f53e8516077fd12c2e3946b86507fef +size 47107 diff --git a/marked/Rel-18/38_series/38321/e27f0c293be4088211306b9fc673178b_img.jpg b/marked/Rel-18/38_series/38321/e27f0c293be4088211306b9fc673178b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74b5b6e729a0d33afa3d027667e10d8abf108880 --- /dev/null +++ b/marked/Rel-18/38_series/38321/e27f0c293be4088211306b9fc673178b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c991cca60a85e5ba59956fa4bb53aaf03921c73d2a1795c70a89264c989f54e3 +size 30445 diff --git a/marked/Rel-18/38_series/38321/e6be648d8221efac693395d853c3bc77_img.jpg b/marked/Rel-18/38_series/38321/e6be648d8221efac693395d853c3bc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a6aeefba4a287183cd40819a6504b8e8283ae79 --- /dev/null +++ b/marked/Rel-18/38_series/38321/e6be648d8221efac693395d853c3bc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87811b1300a06fc428d15ca940ff406d8510ad02d4b646e5019e47319b5df642 +size 65864 diff --git a/marked/Rel-18/38_series/38321/ea05ea5657f5dce30565bd4b45ed1353_img.jpg b/marked/Rel-18/38_series/38321/ea05ea5657f5dce30565bd4b45ed1353_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d20ec740530fc95e7be5c14e775b9429d1a64bcb --- /dev/null +++ b/marked/Rel-18/38_series/38321/ea05ea5657f5dce30565bd4b45ed1353_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ac7ce08b04ac3a3ae9aefc13565c08b54ec376fe63050e5501a81c094df632d +size 33274 diff --git a/marked/Rel-18/38_series/38321/ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg b/marked/Rel-18/38_series/38321/ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7eeac465d1faf77a109b458a5baa251a43bb2770 --- /dev/null +++ b/marked/Rel-18/38_series/38321/ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:118d624b99050293830d2569de5e65e91bc4cde89da054b9b71df3bf140ca811 +size 52616 diff --git a/marked/Rel-18/38_series/38321/eeb519f37cc42888fa15ab9ea20ba7cb_img.jpg b/marked/Rel-18/38_series/38321/eeb519f37cc42888fa15ab9ea20ba7cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32e43589e061a28731568b9345a2d25671ebc447 --- /dev/null +++ b/marked/Rel-18/38_series/38321/eeb519f37cc42888fa15ab9ea20ba7cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dc78844988735465ddfda8b590ca30def0443a73d5fab57423c04e39aa96e71 +size 57271 diff --git a/marked/Rel-18/38_series/38321/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg b/marked/Rel-18/38_series/38321/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..848a33625c6aef90c37d47b1ba6e0537a04f36b5 --- /dev/null +++ b/marked/Rel-18/38_series/38321/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7d33a30cbbf33373e6691c22015c386dd400643d1f57cfd26dc78bb0a8570ff +size 41751 diff --git a/marked/Rel-18/38_series/38321/f80c936f54d96fe309ff7df916a864c7_img.jpg b/marked/Rel-18/38_series/38321/f80c936f54d96fe309ff7df916a864c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67dc5dfb97cfddc6d5285277907f9c13da67f034 --- /dev/null +++ b/marked/Rel-18/38_series/38321/f80c936f54d96fe309ff7df916a864c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6090a35c7d879bde22ef20b24625160a444a4a13d3eb24e0d904ae49a1ee33a +size 42554 diff --git a/marked/Rel-18/38_series/38321/fb00a9ea622a6fe32404236fbf9b1b6a_img.jpg b/marked/Rel-18/38_series/38321/fb00a9ea622a6fe32404236fbf9b1b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bd9cc99df47d2a5e854311a7d1341cf5b3e29b4 --- /dev/null +++ b/marked/Rel-18/38_series/38321/fb00a9ea622a6fe32404236fbf9b1b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:879fe2e60033c3a6c66b5b0af3767dd6ed27ee8851e21e95151ce1a200c69625 +size 69633 diff --git a/marked/Rel-18/38_series/38321/raw.md b/marked/Rel-18/38_series/38321/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d760536ba1afed754fb6ef30fc3423980e27f0eb --- /dev/null +++ b/marked/Rel-18/38_series/38321/raw.md @@ -0,0 +1,10678 @@ + + +# 3GPP TS 38.321 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a red signal icon consisting of three curved lines. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices + +## **3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +## **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------|----| +| Foreword..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations..... | 12 | +| 4 General..... | 14 | +| 4.1 Introduction..... | 14 | +| 4.2 MAC architecture..... | 14 | +| 4.2.1 General..... | 14 | +| 4.2.2 MAC Entities..... | 14 | +| 4.3 Services..... | 16 | +| 4.3.1 Services provided to upper layers..... | 16 | +| 4.3.2 Services expected from physical layer..... | 16 | +| 4.4 Functions..... | 17 | +| 4.5 Channel structure..... | 17 | +| 4.5.1 General..... | 17 | +| 4.5.2 Transport Channels..... | 17 | +| 4.5.3 Logical Channels..... | 18 | +| 4.5.4 Mapping of Transport Channels to Logical Channels..... | 18 | +| 4.5.4.1 General..... | 18 | +| 4.5.4.2 Uplink mapping..... | 18 | +| 4.5.4.3 Downlink mapping..... | 18 | +| 4.5.4.4 Sidelink mapping..... | 19 | +| 5 MAC procedures..... | 19 | +| 5.1 Random Access procedure..... | 19 | +| 5.1.1 Random Access procedure initialization..... | 19 | +| 5.1.1a Initialization of variables specific to Random Access type..... | 24 | +| 5.1.1b Selection of the set of Random Access resources for the Random Access procedure..... | 27 | +| 5.1.1c Availability of the set of Random Access resources..... | 30 | +| 5.1.1d Selection of the set of Random Access resources based on feature prioritization..... | 31 | +| 5.1.1e Selection of Msg1 repetition for SI request..... | 31 | +| 5.1.2 Random Access Resource selection..... | 31 | +| 5.1.2a Random Access Resource selection for 2-step RA type..... | 35 | +| 5.1.3 Random Access Preamble transmission..... | 37 | +| 5.1.3a MSGA transmission..... | 38 | +| 5.1.4 Random Access Response reception..... | 40 | +| 5.1.4a MSGB reception and contention resolution for 2-step RA type..... | 43 | +| 5.1.5 Contention Resolution..... | 46 | +| 5.1.6 Completion of the Random Access procedure..... | 48 | +| 5.2 Maintenance of Uplink Time Alignment..... | 49 | +| 5.2a Maintenance of UL Synchronization..... | 53 | +| 5.3 DL-SCH data transfer..... | 53 | +| 5.3.1 DL Assignment reception..... | 53 | +| 5.3.2 HARQ operation..... | 56 | +| 5.3.2.1 HARQ Entity..... | 56 | +| 5.3.2.2 HARQ process..... | 56 | +| 5.3.3 Disassembly and demultiplexing..... | 58 | +| 5.4 UL-SCH data transfer..... | 58 | +| 5.4.1 UL Grant reception..... | 58 | +| 5.4.2 HARQ operation..... | 64 | +| 5.4.2.1 HARQ Entity..... | 64 | +| 5.4.2.2 HARQ process..... | 68 | +| 5.4.3 Multiplexing and assembly..... | 70 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------|-----| +| 5.4.3.1 | Logical Channel Prioritization..... | 70 | +| 5.4.3.1.1 | General..... | 70 | +| 5.4.3.1.2 | Selection of logical channels..... | 71 | +| 5.4.3.1.3 | Allocation of resources..... | 71 | +| 5.4.3.2 | Multiplexing of MAC Control Elements and MAC SDUs..... | 73 | +| 5.4.4 | Scheduling Request..... | 73 | +| 5.4.5 | Buffer Status Reporting..... | 78 | +| 5.4.6 | Power Headroom Reporting..... | 81 | +| 5.4.7 | Pre-emptive Buffer Status Reporting..... | 86 | +| 5.4.8 | Timing Advance Reporting..... | 86 | +| 5.4.9 | Delay status reporting..... | 87 | +| 5.5 | PCH reception..... | 88 | +| 5.6 | BCH reception..... | 88 | +| 5.7 | Discontinuous Reception (DRX)..... | 88 | +| 5.7a | Discontinuous Reception (DRX) for MBS Broadcast..... | 96 | +| 5.7b | Discontinuous Reception (DRX) for MBS Multicast..... | 97 | +| 5.8 | Transmission and reception without dynamic scheduling..... | 99 | +| 5.8.1 | Downlink..... | 99 | +| 5.8.1a | Downlink for Multicast..... | 100 | +| 5.8.2 | Uplink..... | 100 | +| 5.8.3 | Sidelink..... | 105 | +| 5.9 | Activation/Deactivation of SCells..... | 107 | +| 5.10 | Activation/Deactivation of PDCP duplication..... | 109 | +| 5.11 | MAC reconfiguration..... | 110 | +| 5.12 | MAC Reset..... | 110 | +| 5.12a | Void..... | 112 | +| 5.13 | Handling of unknown, unforeseen and erroneous protocol data..... | 112 | +| 5.14 | Handling of measurement gaps..... | 112 | +| 5.15 | Bandwidth Part (BWP) operation..... | 112 | +| 5.15.1 | Downlink and Uplink..... | 112 | +| 5.15.2 | Sidelink..... | 117 | +| 5.16 | SUL operation..... | 118 | +| 5.17 | Beam Failure Detection and Recovery procedure..... | 118 | +| 5.18 | Handling of MAC CEs..... | 122 | +| 5.18.1 | General..... | 122 | +| 5.18.2 | Activation/Deactivation of Semi-persistent CSI-RS/CSI-IM resource set..... | 123 | +| 5.18.3 | Aperiodic CSI Trigger State Subselection..... | 124 | +| 5.18.4 | Activation/Deactivation of UE-specific PDSCH TCI state..... | 124 | +| 5.18.5 | Indication of TCI state for UE-specific PDCCH..... | 124 | +| 5.18.6 | Activation/Deactivation of Semi-persistent CSI reporting on PUCCH..... | 125 | +| 5.18.7 | Activation/Deactivation of Semi-persistent SRS and Indication of spatial relation of SP/AP SRS..... | 125 | +| 5.18.8 | Activation/Deactivation of spatial relation of PUCCH resource..... | 125 | +| 5.18.9 | Activation/Deactivation of semi-persistent ZP CSI-RS resource set..... | 126 | +| 5.18.10 | Recommended Bit Rate..... | 126 | +| 5.18.11 | Void..... | 127 | +| 5.18.12 | Void..... | 127 | +| 5.18.13 | Void..... | 127 | +| 5.18.14 | Update of Pathloss Reference RS of SRS..... | 127 | +| 5.18.15 | Update of Pathloss Reference RS of PUSCH..... | 127 | +| 5.18.16 | Indication of spatial relation of SRS resource for a Serving Cell set..... | 127 | +| 5.18.17 | Activation/Deactivation of Semi-Persistent Positioning SRS..... | 127 | +| 5.18.18 | Timing offset adjustments for IAB..... | 128 | +| 5.18.19 | Guard symbols for IAB..... | 128 | +| 5.18.20 | Positioning Measurement Gap Activation/Deactivation Command..... | 129 | +| 5.18.21 | PPW Activation/Deactivation Command..... | 129 | +| 5.18.22 | Update of PUCCH Power Control Set for multiple TRP PUCCH repetition..... | 130 | +| 5.18.23 | Unified TCI States Activation/Deactivation MAC CE..... | 130 | +| 5.18.24 | Update of Differential Koffset..... | 130 | +| 5.18.25 | BFD-RS Indication MAC CE..... | 130 | +| 5.18.26 | Restricted and recommended beam indication for IAB..... | 130 | +| 5.18.27 | DL TX power adjustment for IAB..... | 131 | + +| | | | +|--------------|----------------------------------------------------------------------------------|-----| +| 5.18.28 | UL PSD range adjustment for IAB..... | 132 | +| 5.18.29 | Timing case indication for IAB..... | 132 | +| 5.18.30 | Case-6 Timing Request..... | 132 | +| 5.18.31 | Backhaul Link Beam Indication for NCR..... | 132 | +| 5.18.32 | Access Link Beam Indication for NCR..... | 133 | +| 5.18.33 | Enhanced Unified TCI States Activation/Deactivation MAC CE..... | 133 | +| 5.18.34 | Activation/deactivation of PSI-based SDU discard..... | 133 | +| 5.18.35 | LTM Cell Switch Command..... | 133 | +| 5.18.36 | Candidate Cell TCI States Activation/Deactivation..... | 134 | +| 5.19 | Data inactivity monitoring..... | 134 | +| 5.20 | Void..... | 135 | +| 5.21 | LBT operation..... | 135 | +| 5.21.1 | General..... | 135 | +| 5.21.2 | LBT failure detection and recovery procedure..... | 135 | +| 5.22 | SL-SCH Data transfer and SL-PRS transmission..... | 136 | +| 5.22.1 | SL-SCH Data and SL-PRS transmission..... | 136 | +| 5.22.1.1 | SL Grant reception and SCI transmission..... | 136 | +| 5.22.1.2 | TX resource (re-)selection check..... | 155 | +| 5.22.1.2a | Re-evaluation and Pre-emption..... | 156 | +| 5.22.1.2b | Re-selection for using a received resource conflict indication..... | 158 | +| 5.22.1.2c | Resource re-selection from SL LBT Failure indication..... | 158 | +| 5.22.1.3 | Sidelink HARQ operation and SL-PRS transmission..... | 159 | +| 5.22.1.3.1 | Sidelink HARQ Entity..... | 159 | +| 5.22.1.3.1a | Sidelink process not associated with SL-PRS dedicated resource pool..... | 161 | +| 5.22.1.3.2 | PSFCH reception..... | 163 | +| 5.22.1.3.3 | HARQ-based Sidelink RLF detection..... | 164 | +| 5.22.1.4 | Multiplexing and assembly..... | 166 | +| 5.22.1.4.0 | General..... | 166 | +| 5.22.1.4.1 | Logical channel prioritization..... | 166 | +| 5.22.1.4.1.1 | General..... | 166 | +| 5.22.1.4.1.2 | Selection of logical channels and SL-PRS..... | 167 | +| 5.22.1.4.1.3 | Allocation of sidelink resources..... | 170 | +| 5.22.1.4.2 | Multiplexing of MAC Control Elements and MAC SDUs..... | 171 | +| 5.22.1.5 | Scheduling Request..... | 171 | +| 5.22.1.6 | Buffer Status Reporting..... | 172 | +| 5.22.1.7 | CSI Reporting..... | 175 | +| 5.22.1.8 | Void..... | 175 | +| 5.22.1.9 | IUC-Request transmission..... | 175 | +| 5.22.1.10 | IUC-Information Reporting..... | 175 | +| 5.22.1.10.1 | General..... | 175 | +| 5.22.1.10.2 | Reception of IUC-Information Reporting..... | 176 | +| 5.22.1.11 | TX carrier (re-)selection..... | 176 | +| 5.22.1.12 | SL-PRS Resource Request..... | 177 | +| 5.22.2 | SL-SCH Data and SL-PRS reception..... | 178 | +| 5.22.2.1 | SCI reception..... | 178 | +| 5.22.2.2 | Sidelink HARQ operation and SL-PRS reception on SL-PRS shared resource pool..... | 179 | +| 5.22.2.2.1 | Sidelink HARQ Entity..... | 179 | +| 5.22.2.2.2 | Sidelink process..... | 180 | +| 5.22.2.3 | Disassembly and demultiplexing..... | 181 | +| 5.22.2.4 | SL-PRS reception on SL-PRS dedicated resource pool..... | 181 | +| 5.23 | SL-BCH data transfer..... | 182 | +| 5.23.1 | SL-BCH data transmission..... | 182 | +| 5.23.2 | SL-BCH data reception..... | 182 | +| 5.24 | Handling of PRS Processing Window..... | 182 | +| 5.25 | Positioning Measurement Gap Activation/Deactivation Request..... | 182 | +| 5.26 | Positioning SRS transmission in RRC_INACTIVE..... | 183 | +| 5.26.1 | General..... | 183 | +| 5.26.2 | TA validation for SRS transmission in RRC_INACTIVE..... | 183 | +| 5.27 | Small Data Transmission..... | 184 | +| 5.27.1 | General..... | 184 | +| 5.27.2 | TA Validation for CG-SDT..... | 186 | + +| | | | +|----------|------------------------------------------------------------------------------------|-----| +| 5.28 | Sidelink Discontinuous Reception (DRX)..... | 186 | +| 5.28.1 | General..... | 186 | +| 5.28.2 | Behaviour of UE receiving SL-SCH Data..... | 187 | +| 5.28.3 | Behaviour of UE transmitting SL-SCH Data..... | 190 | +| 5.29 | Activation/Deactivation of SCG..... | 191 | +| 5.30 | Handling of FR2 UL gap..... | 192 | +| 5.31 | Sidelink LBT operation..... | 192 | +| 5.31.1 | General..... | 192 | +| 5.31.2 | Sidelink LBT failure detection and recovery procedure..... | 192 | +| 5.32 | SRS for positioning Tx frequency hopping..... | 194 | +| 5.33 | RACH-less initial UL transmission..... | 194 | +| 5.34 | Cell-Level Energy Saving..... | 194 | +| 5.34.1 | General..... | 194 | +| 5.34.2 | Cell Discontinuous Transmission..... | 195 | +| 5.34.3 | Cell Discontinuous Reception..... | 196 | +| 6 | Protocol Data Units, formats and parameters..... | 197 | +| 6.1 | Protocol Data Units..... | 197 | +| 6.1.1 | General..... | 197 | +| 6.1.2 | MAC PDU (DL-SCH and UL-SCH except transparent MAC and Random Access Response)..... | 197 | +| 6.1.3 | MAC Control Elements (CEs)..... | 200 | +| 6.1.3.1 | Buffer Status Report MAC CEs..... | 200 | +| 6.1.3.2 | C-RNTI MAC CE..... | 207 | +| 6.1.3.3 | UE Contention Resolution Identity MAC CE..... | 207 | +| 6.1.3.4 | Timing Advance Command MAC CE..... | 207 | +| 6.1.3.4a | Absolute Timing Advance Command MAC CE..... | 208 | +| 6.1.3.5 | DRX Command MAC CE..... | 208 | +| 6.1.3.6 | Long DRX Command MAC CE..... | 208 | +| 6.1.3.7 | Configured Grant Confirmation MAC CE..... | 208 | +| 6.1.3.8 | Single Entry PHR MAC CE..... | 208 | +| 6.1.3.9 | Multiple Entry PHR MAC CE..... | 210 | +| 6.1.3.10 | SCell Activation/Deactivation MAC CEs..... | 213 | +| 6.1.3.11 | Duplication Activation/Deactivation MAC CE..... | 214 | +| 6.1.3.12 | SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE..... | 214 | +| 6.1.3.13 | Aperiodic CSI Trigger State Subselection MAC CE..... | 215 | +| 6.1.3.14 | TCI States Activation/Deactivation for UE-specific PDSCH MAC CE..... | 216 | +| 6.1.3.15 | TCI State Indication for UE-specific PDCCH MAC CE..... | 217 | +| 6.1.3.16 | SP CSI reporting on PUCCH Activation/Deactivation MAC CE..... | 217 | +| 6.1.3.17 | SP SRS Activation/Deactivation MAC CE..... | 218 | +| 6.1.3.18 | PUCCH spatial relation Activation/Deactivation MAC CE..... | 219 | +| 6.1.3.19 | SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE..... | 220 | +| 6.1.3.20 | Recommended bit rate MAC CE..... | 220 | +| 6.1.3.21 | Timing Delta MAC CE..... | 221 | +| 6.1.3.22 | Guard Symbols MAC CEs..... | 222 | +| 6.1.3.23 | BFR MAC CEs..... | 222 | +| 6.1.3.24 | Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE..... | 224 | +| 6.1.3.25 | Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE..... | 225 | +| 6.1.3.26 | Enhanced SP/AP SRS Spatial Relation Indication MAC CE..... | 226 | +| 6.1.3.27 | SRS Pathloss Reference RS Update MAC CE..... | 227 | +| 6.1.3.28 | PUSCH Pathloss Reference RS Update MAC CE..... | 228 | +| 6.1.3.29 | Serving Cell Set based SRS Spatial Relation Indication MAC CE..... | 228 | +| 6.1.3.30 | LBT failure MAC CEs..... | 230 | +| 6.1.3.31 | Multiple Entry Configured Grant Confirmation MAC CE..... | 231 | +| 6.1.3.32 | Duplication RLC Activation/Deactivation MAC CE..... | 231 | +| 6.1.3.33 | Sidelink Buffer Status Report MAC CEs..... | 231 | +| 6.1.3.34 | Sidelink Configured Grant Confirmation MAC CE..... | 232 | +| 6.1.3.35 | Sidelink CSI Reporting MAC CE..... | 233 | +| 6.1.3.36 | SP Positioning SRS Activation/Deactivation MAC CE..... | 233 | +| 6.1.3.37 | Guard Symbols MAC CEs for Case-6 and Case-7 timing modes..... | 236 | +| 6.1.3.38 | Case-7 Timing advance offset MAC CE..... | 237 | +| 6.1.3.39 | Case-6 Timing Request MAC CE..... | 237 | +| 6.1.3.40 | Positioning Measurement Gap Activation/Deactivation Request MAC CE..... | 237 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------|------------| +| 6.1.3.41 | Positioning Measurement Gap Activation/Deactivation Command MAC CE..... | 238 | +| 6.1.3.42 | PPW Activation/Deactivation Command MAC CE..... | 238 | +| 6.1.3.43 | Enhanced BFR MAC CEs..... | 239 | +| 6.1.3.44 | Enhanced TCI States Indication for UE-specific PDCCH MAC CE..... | 242 | +| 6.1.3.45 | PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE.... | 243 | +| 6.1.3.46 | PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC CE..... | 244 | +| 6.1.3.47 | Unified TCI States Activation/Deactivation MAC CE..... | 245 | +| 6.1.3.48 | Enhanced Single Entry PHR MAC CE..... | 246 | +| 6.1.3.49 | Enhanced Multiple Entry PHR MAC CE..... | 247 | +| 6.1.3.50 | Enhanced Single Entry PHR for multiple TRP MAC CE..... | 252 | +| 6.1.3.51 | Enhanced Multiple Entry PHR for multiple TRP MAC CE..... | 252 | +| 6.1.3.52 | Sidelink DRX Command MAC CE..... | 255 | +| 6.1.3.53 | Inter-UE Coordination Information MAC CE..... | 256 | +| 6.1.3.54 | Inter-UE Coordination Request MAC CE..... | 257 | +| 6.1.3.55 | Enhanced SCell Activation/Deactivation MAC CEs..... | 258 | +| 6.1.3.56 | Timing Advance Report MAC CE..... | 259 | +| 6.1.3.57 | Differential Koffset MAC CE..... | 260 | +| 6.1.3.58 | BFD-RS Indication MAC CE..... | 260 | +| 6.1.3.59 | SP/AP SRS TCI State Indication MAC CE..... | 260 | +| 6.1.3.60 | Serving Cell Set based SRS TCI State Indication MAC CE..... | 262 | +| 6.1.3.61 | Child IAB-DU Restricted Beam Indication MAC CE..... | 263 | +| 6.1.3.62 | IAB-MT Recommended Beam Indication MAC CE..... | 266 | +| 6.1.3.63 | DL TX Power Adjustment and Desired DL TX Power Adjustment MAC CEs..... | 269 | +| 6.1.3.64 | Desired IAB-MT PSD range MAC CE..... | 270 | +| 6.1.3.65 | Timing Case Indication MAC CE..... | 272 | +| 6.1.3.66 | NCR Downlink Backhaul Link Beam Indication MAC CE..... | 273 | +| 6.1.3.67 | NCR Uplink Backhaul Link Beam Indication MAC CE..... | 273 | +| 6.1.3.68 | NCR Access Link Beam Indication MAC CE..... | 274 | +| 6.1.3.69 | SL LBT failure MAC CEs..... | 274 | +| 6.1.3.70 | Enhanced Unified TCI States Activation/Deactivation MAC CE for Joint TCI States..... | 274 | +| 6.1.3.71 | Enhanced Unified TCI States Activation/Deactivation MAC CE for Separate TCI States..... | 275 | +| 6.1.3.72 | Delay Status Report MAC CE..... | 276 | +| 6.1.3.73 | PSI-Based SDU Discard Activation/Deactivation MAC CE..... | 277 | +| 6.1.3.74 | SL-PRS Resource Request MAC CE..... | 278 | +| 6.1.3.75 | LTM Cell Switch Command MAC CE..... | 278 | +| 6.1.3.76 | Candidate Cell TCI States Activation/Deactivation MAC CE..... | 279 | +| 6.1.3.77 | Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE..... | 280 | +| 6.1.3.78 | Single Entry PHR with assumed PUSCH MAC CE..... | 281 | +| 6.1.3.79 | Multiple Entry PHR with assumed PUSCH MAC CE..... | 282 | +| 6.1.3.80 | Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE..... | 284 | +| 6.1.4 | MAC PDU (transparent MAC)..... | 285 | +| 6.1.5 | MAC PDU (Random Access Response)..... | 286 | +| 6.1.5a | MAC PDU (MSG3)..... | 286 | +| 6.1.6 | MAC PDU (SL-SCH)..... | 288 | +| 6.2 | Formats and parameters..... | 289 | +| 6.2.1 | MAC subheader for DL-SCH and UL-SCH..... | 289 | +| 6.2.2 | MAC subheader for Random Access Response..... | 294 | +| 6.2.2a | MAC subheader for MSG3..... | 294 | +| 6.2.3 | MAC payload for Random Access Response..... | 295 | +| 6.2.3a | MAC payload for MSG3..... | 296 | +| 6.2.4 | MAC subheader for SL-SCH..... | 297 | +| 7 | Variables and constants..... | 298 | +| 7.1 | RNTI values..... | 298 | +| 7.2 | Backoff Parameter values..... | 301 | +| 7.3 | DELTA_PREAMBLE values..... | 301 | +| 7.4 | PRACH Mask Index values..... | 302 | +| Annex A (informative): | Change history..... | 303 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document specifies the NR MAC protocol. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.300: "NR; Overall description; Stage 2". +- [3] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification". +- [4] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) protocol specification". +- [5] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [6] 3GPP TS 38.213: "NR; Physical Layer Procedures for control". +- [7] 3GPP TS 38.214: "NR; Physical Layer Procedures for data". +- [8] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [9] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [10] Void. +- [11] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [12] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". +- [13] 3GPP TS 26.114: "Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [14] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [15] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [16] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- [17] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer Procedures". +- [18] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [19] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". + +- [20] 3GPP TS 23.285: "Architecture enhancements for V2X services". +- [21] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [22] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC); Protocol specification". +- [23] 3GPP TS 37.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [24] 3GPP TS 38.215: "NR; Physical layer measurements". +- [25] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities". +- [26] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [27] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)". +- [28] 3GPP TS 24.587: " Technical Specification Group Core Network and Terminals; Vehicle-to-Everything (V2X) services in 5G System (5GS)". +- [29] 3GPP TS 24.554: "Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) in 5G System (5GS) protocol". +- [30] 3GPP TS 23.586: "Technical Specification Group Services and System Aspects; Architectural Enhancements to support Ranging based services and Sidelink Positioning". +- [31] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**A2X communication:** A communication to support A2X services leveraging PC5 reference points, as defined in TS 23.256 [31]. A2X services are realized by various types of A2X applications, e.g., BRID or DAA. + +**Air to Ground network:** An NG-RAN consisting of ground-based gNBs, which provide cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal, with typical vertical altitude of around 10,000 m and take-off/landing altitudes down to 3000 m. + +**BWP for SRS for positioning Tx frequency hopping:** For SRS for positioning Tx frequency hopping, separate BWP configuration outside BWP configuration for data transmission. + +**Dormant BWP:** The dormant BWP is one of downlink BWPs configured by the network via dedicated RRC signaling. In the dormant BWP, the UE stop monitoring PDCCH on/for the SCell, but continues performing CSI measurements, Automatic Gain Control (AGC) and beam management, if configured. + +**DRX group:** A group of Serving Cells that is configured by RRC and that have the same DRX Active Time. + +**eRedCap UE:** A UE with enhanced reduced capabilities as specified in clause 4.2.22.1 of TS 38.306 [25]. + +**HARQ information:** HARQ information for DL-SCH, for UL-SCH, or for SL-SCH transmissions consists of New Data Indicator (NDI), Transport Block Size (TBS), Redundancy Version (RV), and HARQ process ID. + +**IAB-donor:** gNB that provides network access to UEs via a network of backhaul and access links. + +**IAB-node:** RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes. + +**Listen Before Talk:** A procedure according to which transmissions are not performed if the channel is identified as being occupied, see TS 37.213 [18]. + +**LTM candidate cell:** A candidate cell configured for LTM as defined in TS 38.331 [5]. + +**Msg3:** Message transmitted on UL-SCH containing a C-RNTI MAC CE or CCCH SDU, submitted from upper layer and associated with the UE Contention Resolution Identity, as part of a Random Access procedure. + +**Multi-path:** Mode of operation of a remote UE in RRC\_CONNECTED configured with one direct path on which the UE connects to gNB using NR Uu, and one indirect path on which the UE connects to the same gNB via a relay UE using L2 U2N relay operation or non-3GPP connectivity (N3C). + +**Multi-path U2N N3C relay:** AS functionality providing both direct path and indirect path via relay UE with non-3GPP connectivity. + +**Multi-PUSCH configured grant:** A configured grant configuration that includes multiple consecutive configured uplink grants within a single periodicity. + +**NCR-Fwd:** NCR-node function, which performs amplifying-and-forwarding of UL/DL RF signals between gNB and UE. The behavior of the NCR-Fwd is controlled according to the side control information received by the NCR-MT from a gNB. + +**NCR-MT:** NCR-node entity which communicates with a gNB via a control link to receive side control information. The control link is based on NR Uu interface. + +**NCR-node:** RAN node comprising NCR-MT and NCR-Fwd. + +**Non-terrestrial network:** An NG-RAN consisting of gNBs, which provide non-terrestrial NR access to UEs by means of an NTN payload embarked on an airborne or space-borne NTN vehicle and an NTN Gateway. + +**NR backhaul link:** NR link used for backhauling between an IAB-node and an IAB-donor, and between IAB-nodes in case of a multi-hop backhauling. + +**NR sidelink communication:** AS functionality enabling at least V2X Communication as defined in TS 23.287 [19] and ProSe communication (including ProSe non-Relay, UE-to-Network Relay and UE-to-UE Relay communication (including ProSe UE-to-UE Relay communication with integrated discovery)) as defined in TS 23.304 [26], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay discovery, ProSe UE-to-Network Relay discovery and ProSe UE-to-UE Relay discovery for Proximity based Services as defined in TS 23.304 [26], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink transmission:** Any NR Sidelink-based transmission, including transmission for NR sidelink discovery, transmission for NR sidelink communication, transmission of SL-PRS, and transmission for A2X communication. + +**PDCCH occasion:** A time duration (i.e. one or a consecutive number of symbols) during which the MAC entity is configured to monitor the PDCCH. + +**Positioning SRS Bandwidth Aggregation:** Transmission of positioning SRS on multiple carriers in RRC\_CONNECTED and RRC\_INACTIVE where the positioning SRS resources are linked in RRC configuration as defined in TS 38.331 [5]. + +**PRS Processing Window:** A time window during which UE may perform PRS measurement inside the active DL BWP with the same numerology as the active DL BWP without measurement gap. + +**Ranging/Sidelink Positioning:** AS functionality enabling ranging-based services and sidelink positioning as specified in TS 23.586 [30]. + +**RB set:** A RB set refers to a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in shared spectrum as defined in TS 37.213 [18]. + +**RedCap UE:** A UE with reduced capabilities as specified in clause 4.2.21.1 in TS 38.306 [25]. + +**Serving Cell:** A PCell, a PSCell, or an SCell in TS 38.331 [5]. + +**Sidelink transmission information:** Sidelink transmission information included in an SCI for an SL-SCH transmission or SL-PRS transmission with or without SL-SCH transmission on SL-PRS shared resource pool as specified in clause 8.3 and 8.4 of TS 38.212 [9] consists of Sidelink HARQ information including NDI, RV, Sidelink process ID, HARQ feedback enabled/disabled indicator, Sidelink identification information including cast type indicator, Source Layer-1 ID and Destination Layer-1 ID, and Sidelink other information including CSI request, SL-PRS request, SL-PRS resource ID, a priority, a communication range requirement and Zone ID. + +**SL-PRS delay budget:** Delay budget before which the SL-PRS is expected to be transmitted by the Tx UE. + +**SL-PRS dedicated resource pool:** A sidelink resource pool which can be used for the transmission of SL-PRS and cannot be used for the transmission of PSSCH. + +**SL-PRS shared resource pool:** A sidelink resource pool which can be used for the transmission of both SL-PRS and PSSCH. + +**SL-PRS transmission information on SL-PRS dedicated resource pool:** SL-PRS transmission information on SL-PRS dedicated resource pool is included in an SCI for an SL-PRS transmission on SL-PRS dedicated resource pool, as specified in TS 38.212 [9], consisting of + +- SL-PRS identification information, including cast type indicator, source ID and destination ID; +- SL-PRS transmission other information, including SL-PRS priority, SL-PRS request, SL-PRS resource ID and resource reservation period. + +**SRS for positioning Tx frequency hopping:** Transmit frequency hopping of positioning SRS in RRC\_INACTIVE and RRC\_CONNECTED. + +**SRS positioning validity area:** An area consisting of a list of cells within which the corresponding positioning SRS configuration is considered as valid. + +**Special Cell:** For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG depending on if the MAC entity is associated to the MCG or the SCG, respectively. Otherwise the term Special Cell refers to the PCell. A Special Cell supports PUCCH transmission and contention-based Random Access, and is always activated. + +**Timing Advance Group:** A group of Serving Cells that is configured by RRC and that, for the cells with a UL configured, using the same timing reference cell and the same Timing Advance value. A Timing Advance Group containing the SpCell of a MAC entity is referred to as Primary Timing Advance Group (PTAG), whereas the term Secondary Timing Advance Group (STAG) refers to other TAGs. + +**UE-gNB RTT:** For non-terrestrial networks, the sum of the UE's Timing Advance value (see TS 38.211 [8] clause 4.3.1) and *kmac*. + +**V2X sidelink communication:** AS functionality enabling V2X Communication as defined in TS 23.285 [20], between nearby UEs, using E-UTRA technology but not traversing any network node. + +NOTE 1: A timer is running once it is started, until it is stopped or until it expires; otherwise it is not running. A timer can be started if it is not running or restarted if it is running. A Timer is always started or restarted from its initial value. The duration of a timer is not updated until it is stopped or expires (e.g. due to BWP switching). When the MAC entity applies zero value for a timer, the timer shall be started and immediately expire unless explicitly stated otherwise. + +NOTE 2: In this version of the specification, the SRS in the procedural description includes Positioning SRS except for the Positioning SRS for transmission in RRC\_INACTIVE as in clause 5.26. Positioning SRS except for the Positioning SRS for transmission in RRC\_INACTIVE is treated the same as SRS by the UE unless explicitly stated otherwise. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------------|---------------------------------------| +| A2X | Aircraft-to-Everything | +| AP | Aperiodic | +| BFR | Beam Failure Recovery | +| BRID | Broadcast Remote Identification | +| BSR | Buffer Status Report | +| BWP | Bandwidth Part | +| CE | Control Element | +| CG | Cell Group | +| CG-SDT | Configured Grant-based SDT | +| CI-RNTI | Cancellation Indication RNTI | +| CSI | Channel State Information | +| CSI-IM | CSI Interference Measurement | +| CSI-RS | CSI Reference Signal | +| CS-RNTI | Configured Scheduling RNTI | +| DAA | Detect And Avoid | +| DAPS | Dual Active Protocol Stack | +| DCP | DCI with CRC scrambled by PS-RNTI | +| DL-PRS | DownLink-Positioning Reference Signal | +| DSR | Delay Status Report | +| DTX | Discontinuous Transmission | +| G-CS-RNTI | Group Configured Scheduling RNTI | +| G-RNTI | Group RNTI | +| IAB | Integrated Access and Backhaul | +| INT-RNTI | Interruption RNTI | +| LBT | Listen Before Talk | +| LCG | Logical Channel Group | +| LCP | Logical Channel Prioritization | +| LTM | L1/L2 Triggered Mobility | +| MBS | Multicast/Broadcast Services | +| MCCH | MBS Control Channel | +| MCCH-RNTI | MBS Control Channel RNTI | +| MCG | Master Cell Group | +| MO-SDT | Mobile Originated SDT | +| MP | Multi-path | +| MPE | Maximum Permissible Exposure | +| MTCH | MBS Traffic Channel | +| MT-SDT | Mobile Terminated SDT | +| N3C | Non-3GPP Connection | +| NCD-SSB | Non Cell Defining SSB | +| NCR | Network-Controlled Repeater | +| NSAG | Network Slice AS Group | +| NUL | Normal Uplink | +| NZP CSI-RS | Non-Zero Power CSI-RS | +| PDB | Packet Delay Budget | +| PEI-RNTI | Paging Early Indication RNTI | +| PHR | Power Headroom Report | +| PQI | PC5 QoS Identifier | +| PS-RNTI | Power Saving RNTI | +| PSI | PDU Set Importance | +| PTAG | Primary Timing Advance Group | +| PTM | Point to Multipoint | +| PTP | Point to Point | +| QCL | Quasi-colocation | +| PPW | PRS Processing Window | +| PRS | Positioning Reference Signal | + +| | | +|----------------|-------------------------------------------------------| +| RA-SDT | Random Access-based SDT | +| RRH | Remote Radio Head | +| RS | Reference Signal | +| SCG | Secondary Cell Group | +| SDT | Small Data Transmission | +| SFI-RNTI | Slot Format Indication RNTI | +| SI | System Information | +| SL-PRS-CS-RNTI | SL-PRS Configured Scheduling RNTI | +| SL-PRS-RNTI | SL-PRS RNTI | +| SL-CS-RNTI | Sidelink Configured Scheduling RNTI | +| SL-PRS | Sidelink PRS | +| SL-RNTI | Sidelink RNTI | +| SpCell | Special Cell | +| SP | Semi-Persistent | +| SP-CSI-RNTI | Semi-Persistent CSI RNTI | +| SPS | Semi-Persistent Scheduling | +| SR | Scheduling Request | +| SRI | SRS Resource Indicator | +| SS | Synchronization Signals | +| SSB | Synchronization Signal Block | +| STAG | Secondary Timing Advance Group | +| SUL | Supplementary Uplink | +| TAG | Timing Advance Group | +| TCI | Transmission Configuration Indicator | +| TPC-SRS-RNTI | Transmit Power Control-Sounding Reference Signal-RNTI | +| TRIV | Time Resource Indicator Value | +| TRP | Transmit/Receive Point | +| TRS | CSI-RS for tracking | +| U2N | UE-to-Network | +| U2U | UE-to-UE | +| UCI | Uplink Control Information | +| UTO-UCI | Unused Transmission Occasion - UCI | +| UTW | Uplink Time Window | +| V2X | Vehicle-to-Everything | +| ZP CSI-RS | Zero Power CSI-RS | + +## 4 General + +### 4.1 Introduction + +The objective of this clause is to describe the MAC architecture and the MAC entity of the UE from a functional point of view. + +### 4.2 MAC architecture + +#### 4.2.1 General + +This clause describes a model of the MAC i.e. it does not specify or restrict implementations. + +RRC is in control of the MAC configuration. + +#### 4.2.2 MAC Entities + +The MAC entity of the UE handles the following transport channels: + +- Broadcast Channel (BCH); + +- Downlink Shared Channel(s) (DL-SCH); +- Paging Channel (PCH); +- Uplink Shared Channel(s) (UL-SCH); +- Random Access Channel(s) (RACH). + +When the UE is configured with SCG, two MAC entities are configured to the UE: one for the MCG and one for the SCG. + +When the UE is configured with DAPS handover, two MAC entities are used by the UE: one for the source cell (source MAC entity) and one for the target cell (target MAC entity). + +The functions of the different MAC entities in the UE operate independently unless otherwise specified. The timers and parameters used in each MAC entity are configured independently unless otherwise specified. The Serving Cells, C-RNTI, radio bearers, logical channels, upper and lower layer entities, LCGs, and HARQ entities considered by each MAC entity refer to those mapped to that MAC entity unless otherwise specified. + +If the MAC entity is configured with one or more SCells, there are multiple DL-SCH and there may be multiple UL-SCH as well as multiple RACH per MAC entity; one DL-SCH, one UL-SCH, and one RACH on the SpCell, one DL-SCH, zero or one UL-SCH and zero or one RACH for each SCell. + +If the MAC entity is not configured with any SCell, there is one DL-SCH, one UL-SCH, and one RACH per MAC entity. + +If the UE is configured with LTM candidate cell(s), there may be zero or one RACH for each LTM candidate cell, which shares the same corresponding MAC entity with Serving Cell. + +Figure 4.2.2-1 illustrates one possible structure of the MAC entity when SCG is not configured and for each MAC entity during DAPS handover. + +![Figure 4.2.2-1: MAC structure overview. This diagram illustrates the internal structure of a MAC entity. At the top, 'Upper layers' are shown with various logical channels: MCCH, MTCH, PCCH, BCCH, CCCH, DCCH, DTCH, and MAC-control. These channels connect to internal MAC processing blocks. MTCH and PCCH go through '(De-) Multiplexing' blocks. MCCH, BCCH, and CCCH connect to 'Logical Channel Prioritization (UL only)'. DCCH and DTCH connect to another '(De-) Multiplexing' block. All these paths lead into a central 'Control' block. Below the Control block are 'HARQ' and 'Random Access Control' blocks. The bottom section, 'Lower layer', contains physical channels: PCH, BCH, DL-SCH, UL-SCH, and RACH. Lines connect the internal MAC blocks to these physical channels: MTCH/PCCH to PCH; MCCH to BCH; BCCH/CCCH to DL-SCH; DCCH/DTCH to UL-SCH; and MAC-control to RACH.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +Figure 4.2.2-1: MAC structure overview. This diagram illustrates the internal structure of a MAC entity. At the top, 'Upper layers' are shown with various logical channels: MCCH, MTCH, PCCH, BCCH, CCCH, DCCH, DTCH, and MAC-control. These channels connect to internal MAC processing blocks. MTCH and PCCH go through '(De-) Multiplexing' blocks. MCCH, BCCH, and CCCH connect to 'Logical Channel Prioritization (UL only)'. DCCH and DTCH connect to another '(De-) Multiplexing' block. All these paths lead into a central 'Control' block. Below the Control block are 'HARQ' and 'Random Access Control' blocks. The bottom section, 'Lower layer', contains physical channels: PCH, BCH, DL-SCH, UL-SCH, and RACH. Lines connect the internal MAC blocks to these physical channels: MTCH/PCCH to PCH; MCCH to BCH; BCCH/CCCH to DL-SCH; DCCH/DTCH to UL-SCH; and MAC-control to RACH. + +**Figure 4.2.2-1: MAC structure overview** + +Figure 4.2.2-2 illustrates one possible structure for the MAC entities when MCG and SCG are configured. + +![Figure 4.2.2-2: MAC structure overview with two MAC entities. The diagram shows two parallel MAC entities. The left entity is for the Master Cell Group (MCG) and the right is for the Secondary Cell Group (SCG). Both entities have 'Upper layers' at the top and 'Lower layer of MCG/SCG' at the bottom. Inside each entity, there are blocks for 'Logical Channel Prioritization (UL only)', '(De-) Multiplexing', 'HARQ', and 'Random Access Control'. A 'Control' block is shared between the two entities. Transport channels like MCCH, MTCH, PCCH, BCCH, CCCH, DCCH, DTCH, PCH of MCG, BCH of MCG, DL-SCH of MCG, UL-SCH of MCG, and RACH of MCG/SCG are shown connecting to the MAC entities.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 4.2.2-2: MAC structure overview with two MAC entities. The diagram shows two parallel MAC entities. The left entity is for the Master Cell Group (MCG) and the right is for the Secondary Cell Group (SCG). Both entities have 'Upper layers' at the top and 'Lower layer of MCG/SCG' at the bottom. Inside each entity, there are blocks for 'Logical Channel Prioritization (UL only)', '(De-) Multiplexing', 'HARQ', and 'Random Access Control'. A 'Control' block is shared between the two entities. Transport channels like MCCH, MTCH, PCCH, BCCH, CCCH, DCCH, DTCH, PCH of MCG, BCH of MCG, DL-SCH of MCG, UL-SCH of MCG, and RACH of MCG/SCG are shown connecting to the MAC entities. + +**Figure 4.2.2-2: MAC structure overview with two MAC entities** + +In addition, the MAC entity of the UE handles the following transport channel for sidelink: + +- Sidelink Shared Channel (SL-SCH); +- Sidelink Broadcast Channel (SL-BCH). + +Figure 4.2.2-3 illustrates one possible structure for the MAC entity when sidelink is configured. + +![Figure 4.2.2-3: MAC structure overview for sidelink. This diagram shows a single MAC entity for sidelink. 'Upper layers' at the top include SBCCH, SCCH, STCH, and MAC-control. These connect to a 'Logical Channel Prioritization (TX only)' block, which then connects to '(De-) Multiplexing'. Below that is 'PDU filtering (RX only)', then 'HARQ'. A 'Control' block is on the right. At the bottom, 'Lower layer' includes SL-BCH and SL-SCH transport channels.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Figure 4.2.2-3: MAC structure overview for sidelink. This diagram shows a single MAC entity for sidelink. 'Upper layers' at the top include SBCCH, SCCH, STCH, and MAC-control. These connect to a 'Logical Channel Prioritization (TX only)' block, which then connects to '(De-) Multiplexing'. Below that is 'PDU filtering (RX only)', then 'HARQ'. A 'Control' block is on the right. At the bottom, 'Lower layer' includes SL-BCH and SL-SCH transport channels. + +**Figure 4.2.2-3: MAC structure overview for sidelink** + +### 4.3 Services + +#### 4.3.1 Services provided to upper layers + +The MAC sublayer provides the following services to upper layers: + +- data transfer; +- radio resource allocation. + +#### 4.3.2 Services expected from physical layer + +The MAC sublayer expects the following services from the physical layer: + +- data transfer services; +- signalling of HARQ feedback; +- signalling of Scheduling Request; +- measurements (e.g. Channel Quality Indication (CQI)). + +## 4.4 Functions + +The MAC sublayer supports the following functions: + +- mapping between logical channels and transport channels; +- multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels; +- demultiplexing of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels; +- scheduling information reporting; +- error correction through HARQ; +- logical channel prioritization; +- priority handling between overlapping resources of one UE; +- radio resource selection. + +The relevance of MAC functions for uplink, downlink, and sidelink is indicated in Table 4.4-1. + +**Table 4.4-1: The link direction association of MAC functions.** + +| MAC function | Downlink | Uplink | Sidelink TX | Sidelink RX | +|---------------------------------------------------------|----------|--------|-------------|-------------| +| Mapping between logical channels and transport channels | X | X | X | X | +| Multiplexing | | X | X | | +| Demultiplexing | X | | | X | +| Scheduling information reporting | | X | X | | +| Error correction through HARQ | X | X | X | X | +| Logical Channel prioritization | | X | X | | +| Radio resource selection | | | X | | + +## 4.5 Channel structure + +### 4.5.1 General + +The MAC sublayer operates on the channels defined below; transport channels are SAPs between MAC and Layer 1, logical channels are SAPs between MAC and RLC. + +### 4.5.2 Transport Channels + +The MAC sublayer uses the transport channels listed in Table 4.5.2-1 below. + +**Table 4.5.2-1: Transport channels used by MAC** + +| Transport channel name | Acronym | Downlink | Uplink | Sidelink | +|----------------------------|---------|----------|--------|----------| +| Broadcast Channel | BCH | X | | | +| Downlink Shared Channel | DL-SCH | X | | | +| Paging Channel | PCH | X | | | +| Uplink Shared Channel | UL-SCH | | X | | +| Random Access Channel | RACH | | X | | +| Sidelink Broadcast Channel | SL-BCH | | | X | +| Sidelink Shared Channel | SL-SCH | | | X | + +## 4.5.3 Logical Channels + +The MAC sublayer provides data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels are defined i.e. each supporting transfer of a particular type of information. + +Each logical channel type is defined by what type of information is transferred. + +The MAC sublayer provides the control and traffic channels listed in Table 4.5.3-1 below. + +**Table 4.5.3-1: Logical channels provided by MAC.** + +| Logical channel name | Acronym | Control channel | Traffic channel | +|------------------------------------|---------|-----------------|-----------------| +| Broadcast Control Channel | BCCH | X | | +| Paging Control Channel | PCCH | X | | +| Common Control Channel | CCCH | X | | +| Dedicated Control Channel | DCCH | X | | +| Dedicated Traffic Channel | DTCH | | X | +| MBS Control Channel | MCCH | X | | +| MBS Traffic Channel | MTCH | | X | +| Sidelink Broadcast Control Channel | SBCCH | X | | +| Sidelink Control Channel | SCCH | X | | +| Sidelink Traffic Channel | STCH | | X | + +## 4.5.4 Mapping of Transport Channels to Logical Channels + +### 4.5.4.1 General + +The MAC entity is responsible for mapping logical channels onto transport channels. This mapping depends on the multiplexing that is configured by RRC. + +### 4.5.4.2 Uplink mapping + +The uplink logical channels can be mapped as described in Table 4.5.4.2-1. + +**Table 4.5.4.2-1: Uplink channel mapping.** + +| Transport channel | UL-SCH | RACH | +|-------------------|--------|------| +| Logical channel | | | +| CCCH | X | | +| DCCH | X | | +| DTCH | X | | + +### 4.5.4.3 Downlink mapping + +The downlink logical channels can be mapped as described in Table 4.5.4.3-1. + +**Table 4.5.4.3-1: Downlink channel mapping.** + +| Transport channel
Logical channel | BCH | PCH | DL-SCH | +|--------------------------------------|-----|-----|--------| +| BCCH | X | | X | +| PCCH | | X | | +| CCCH | | | X | +| DCCH | | | X | +| DTCH | | | X | +| MCCH | | | X | +| MTCH | | | X | + +#### 4.5.4.4 Sidelink mapping + +The sidelink logical channels can be mapped as described in Table 4.5.4.4-1. + +**Table 4.5.4.4-1: Sidelink channel mapping.** + +| Transport channel
Logical channel | SL-BCH | SL-SCH | +|--------------------------------------|--------|--------| +| SBCCH | X | | +| SCCH | | X | +| STCH | | X | + +--- + +## 5 MAC procedures + +### 5.1 Random Access procedure + +#### 5.1.1 Random Access procedure initialization + +The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC entity itself, or by RRC for the events in accordance with TS 38.300 [2]. There is only one Random Access procedure ongoing at any point in time in a MAC entity. The Random Access procedure on an SCell or an LTM candidate cell shall only be initiated by a PDCCH order with *ra-PreambleIndex* different from 0b000000. + +NOTE 1: If a new Random Access procedure is triggered while another is already ongoing in the MAC entity, it is up to UE implementation whether to continue with the ongoing procedure or start with the new procedure (e.g. for SI request). + +NOTE 2: If there was an ongoing Random Access procedure that is triggered by a PDCCH order while the UE receives another PDCCH order indicating the same Random Access Preamble, PRACH mask index and uplink carrier, the Random Access procedure is considered as the same Random Access procedure as the ongoing one and not initialized again. + +When a Random Access procedure is initiated, UE selects a set of Random Access resources as specified in clause 5.1.1b and initialises the following parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources: + +- *prach-ConfigurationIndex*: the available set of PRACH occasions for the transmission of the Random Access Preamble for Msg1. These are also applicable to the MSGA PRACH if the PRACH occasions are shared between 2-step and 4-step RA types; +- *prach-ConfigurationPeriodScaling-IAB*: the scaling factor defined in TS 38.211 [8] and applicable to IAB-MTs, extending the periodicity of the PRACH occasions baseline configuration indicated by *prach-ConfigurationIndex*; +- *prach-ConfigurationFrameOffset-IAB*: the frame offset defined in TS 38.211 [8] and applicable to IAB-MTs, altering the ROs frame defined in the baseline configuration indicated by *prach-ConfigurationIndex*; + +- *prach-ConfigurationSOffset-IAB*: the subframe/slot offset defined in TS 38.211 [8] and applicable to IAB-MTs, altering the ROs subframe or slot defined in the baseline configuration indicated by *prach-ConfigurationIndex*; +- *msgA-PRACH-ConfigurationIndex*: the available set of PRACH occasions for the transmission of the Random Access Preamble for MSGA in 2-step RA type; +- *preambleReceivedTargetPower*: initial Random Access Preamble power for 4-step RA type; +- *msgA-PreambleReceivedTargetPower*: initial Random Access Preamble power for 2-step RA type; +- *rsrp-ThresholdSSB*: an RSRP threshold for the selection of the SSB for 4-step RA type. If the Random Access procedure is initiated for beam failure recovery, *rsrp-ThresholdSSB* used for the selection of the SSB within *candidateBeamRSList* refers to *rsrp-ThresholdSSB* in *BeamFailureRecoveryConfig* IE; +- *rsrp-ThresholdCSI-RS*: an RSRP threshold for the selection of CSI-RS for 4-step RA type. If the Random Access procedure is initiated for beam failure recovery, *rsrp-ThresholdCSI-RS* is equal to *rsrp-ThresholdSSB* in *BeamFailureRecoveryConfig* IE; +- *msgA-RSRP-ThresholdSSB*: an RSRP threshold for the selection of the SSB for 2-step RA type; +- *rsrp-ThresholdSSB-SUL*: an RSRP threshold for the selection between the NUL carrier and the SUL carrier; +- *msgA-RSRP-Threshold*: an RSRP threshold for selection between 2-step RA type and 4-step RA type when both 2-step and 4-step RA type Random Access Resources are configured in the UL BWP; +- *rsrp-ThresholdMsg1-RepetitionNum2*: an RSRP threshold for Msg1 repetition with repetition number 2 (see clause 5.1.1b); +- *rsrp-ThresholdMsg1-RepetitionNum4*: an RSRP threshold for Msg1 repetition with repetition number 4 (see clause 5.1.1b); +- *rsrp-ThresholdMsg1-RepetitionNum8*: an RSRP threshold for Msg1 repetition with repetition number 8 (see clause 5.1.1b); +- *rsrp-ThresholdMsg3*: an RSRP threshold for Msg3 repetition (see clause 5.1.1b); +- *FeatureCombination*: feature or a combination of features associated with a set of Random Access resources; +- *featurePriorities*: priorities for features, such as (e)RedCap, Slicing, etc. (see clause 5.1.1d); +- *msgA-TransMax*: The maximum number of MSGA transmissions when both 4-step and 2-step RA type Random Access Resources are configured; +- *candidateBeamRSList*: a list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated Random Access parameters; +- *recoverySearchSpaceId*: the search space identity for monitoring the response of the beam failure recovery request; +- *powerRampingStep*: the power-ramping factor; +- *msgA-PreamblePowerRampingStep*: the power ramping factor for MSGA preamble; +- *powerRampingStepHighPriority*: the power-ramping factor in case of prioritized Random Access procedure; +- *scalingFactorBI*: a scaling factor for prioritized Random Access procedure; +- *ra-PreambleIndex*: Random Access Preamble; +- *ra-ssb-OccasionMaskIndex*: defines PRACH occasion(s) associated with an SSB in which the MAC entity may transmit a Random Access Preamble (see clause 7.4); +- *msgA-SSB-SharedRO-MaskIndex*: Indicates the subset of 4-step RA type PRACH occasions shared with 2-step RA type PRACH occasions for each SSB. If 2-step RA type PRACH occasions are shared with 4-step RA type PRACH occasions and *msgA-SSB-SharedRO-MaskIndex* is not configured, then all 4-step RA type PRACH occasions are available for 2-step RA type (see clause 7.4); + +- *ssb-SharedRO-MaskIndex*: defines PRACH occasions, on which preambles are allocated for a feature or a combination of features, associated with an SSB in which the MAC entity may transmit a Random Access Preamble (see clause 7.4); +- *ra-OccasionList*: defines PRACH occasion(s) associated with a CSI-RS in which the MAC entity may transmit a Random Access Preamble; +- *ra-PreambleStartIndex*: the starting index of Random Access Preamble(s) for on-demand SI request; +- *startPreambleForThisPartition*: the first preamble associated with the set of Random Access Resources applicable to the Random Access procedure; +- *preambleTransMax*: the maximum number of Random Access Preamble transmission; +- *preambleTransMax-Msg1-Repetition*: the maximum number of Random Access Preamble transmissions with a given Msg1 repetition number before switching to Msg1 repetition with the next available higher Msg1 repetition number; +- *ssb-perRACH-OccasionAndCB-PreamblesPerSSB*: defines the number of SSBs mapped to each PRACH occasion for 4-step RA type and the number of contention-based Random Access Preambles mapped to each SSB; +- *msgA-CB-PreamblesPerSSB-PerSharedRO*: defines the number of contention-based Random Access Preambles for 2-step RA type mapped to each SSB when the PRACH occasions are shared between 2-step and 4-step RA types; +- *msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB*: defines the number of SSBs mapped to each PRACH occasion for 2-step RA type and the number of contention-based Random Access Preambles mapped to each SSB; +- *numberOfPreamblesPerSSB-ForThisPartition*: defines the number of consecutive preambles for a feature or a combination of features mapped to each SSB; +- *msgA-PUSCH-ResourceGroupA*: defines MSGA PUSCH resources that the UE shall use when performing MSGA transmission using Random Access Preambles group A; +- *msgA-PUSCH-ResourceGroupB*: defines MSGA PUSCH resources that the UE shall use when performing MSGA transmission using Random Access Preambles group B; +- *msgA-PUSCH-Resource-Index*: identifies the index of the PUSCH resource used for MSGA in case of contention-free Random Access with 2-step RA type; +- if *groupBconfigured* is configured, then Random Access Preambles group B is configured for 4-step RA type. + - Amongst the contention-based Random Access Preambles associated with an SSB (as defined in TS 38.213 [6]), the first *numberOfRA-PreamblesGroupA* included in *groupBconfigured* Random Access Preambles belong to Random Access Preambles group A. The remaining Random Access Preambles associated with the SSB belong to Random Access Preambles group B (if configured). +- if *groupB-ConfiguredTwoStepRA* is configured, then Random Access Preambles group B is configured for 2-step RA type. + - Amongst the contention-based Random Access Preambles for 2-step RA type associated with an SSB (as defined in TS 38.213 [6]), the first *numberOfRA-PreamblesGroupA* included in *GroupB-ConfiguredTwoStepRA* Random Access Preambles belong to Random Access Preambles group A. The remaining Random Access Preambles associated with the SSB belong to Random Access Preambles group B (if configured). + +NOTE 3: If Random Access Preambles group B is supported by the cell Random Access Preambles group B is included for each SSB. + +- if Random Access Preambles group B is configured for 4-step RA type: + - *ra-Msg3SizeGroupA*: the threshold to determine the groups of Random Access Preambles for 4-step RA type; + - *msg3-DeltaPreamble*: $\Delta_{\text{PREAMBLE\_Msg3}}$ in TS 38.213 [6]; + +- *messagePowerOffsetGroupB*: the power offset for preamble selection included in *groupBconfigured*; +- *numberOfRA-PreamblesGroupA*: defines the number of Random Access Preambles in Random Access Preamble group A for each SSB included in *groupBconfigured*. +- if Random Access Preambles group B is configured for 2-step RA type: + - *msgA-DeltaPreamble*: $\Delta_{MsgA\_PUSCH}$ in TS 38.213 [6]; + - *messagePowerOffsetGroupB*: the power offset for preamble selection included in *GroupB-ConfiguredTwoStepRA*; + - *numberOfRA-PreamblesGroupA*: defines the number of Random Access Preambles in Random Access Preamble group A for each SSB included in *GroupB-ConfiguredTwoStepRA*; + - *ra-MsgA-SizeGroupA*: the threshold to determine the groups of Random Access Preambles for 2-step RA type. +- the set of Random Access Preambles and/or PRACH occasions for SI request, if any; +- the set of Random Access Preambles and/or PRACH occasions for beam failure recovery request, if any; +- the set of Random Access Preambles and/or PRACH occasions for reconfiguration with sync, if any; +- *ra-ResponseWindow*: the time window to monitor RA response(s) (SpCell only); +- *ra-ContentionResolutionTimer*: the Contention Resolution Timer (SpCell only); +- *msgB-ResponseWindow*: the time window to monitor RA response(s) for 2-step RA type (SpCell only). + +In addition, the following information for related Serving Cell is assumed to be available for UEs: + +- if Random Access Preambles group B is configured: + - if the Serving Cell for the Random Access procedure is configured with supplementary uplink as specified in TS 38.331 [5], and SUL carrier is selected for performing Random Access Procedure: + - $P_{CMAX,fc}$ of the SUL carrier as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]. + - else: + - $P_{CMAX,fc}$ of the NUL carrier as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]. + +The following UE variables are used for the Random Access procedure: + +- *PREAMBLE\_INDEX*; +- *PREAMBLE\_TRANSMISSION\_COUNTER*; +- *PREAMBLE\_POWER\_RAMPING\_COUNTER*; +- *PREAMBLE\_POWER\_RAMPING\_STEP*; +- *PREAMBLE\_RECEIVED\_TARGET\_POWER*; +- *PREAMBLE\_BACKOFF*; +- *PCMAX*; +- *SCALING\_FACTOR\_BI*; +- *TEMPORARY\_C-RNTI*; +- *RA\_TYPE*; +- *POWER\_OFFSET\_2STEP\_RA*; +- *MSG\_A\_PREAMBLE\_POWER\_RAMPING\_STEP*. + +When the Random Access procedure is initiated on a Serving Cell or to an LTM candidate cell, the MAC entity shall: + +- 1> flush the Msg3 buffer; +- 1> flush the MSGA buffer; +- 1> set the *PREAMBLE\_TRANSMISSION\_COUNTER* to 1; +- 1> if the Random Access procedure is initiated on a Serving Cell; or +- 1> if the Random Access procedure is initiated by the PDCCH order to an LTM candidate cell and the PDCCH order indicates preamble initial transmission; or +- 1> if the Random Access procedure is initiated by the PDCCH order to an LTM candidate cell, which is different from the LTM candidate cell to perform the last Random Access Preamble transmission initiated by the PDCCH order to an LTM candidate cell, and the PDCCH order indicates preamble re-transmission: + - 2> set the *PREAMBLE\_POWER\_RAMPING\_COUNTER* to 1; +- 1> set the *PREAMBLE\_BACKOFF* to 0 ms; +- 1> set *POWER\_OFFSET\_2STEP\_RA* to 0 dB; +- 1> if the carrier to use for the Random Access procedure is explicitly signalled: + - 2> select the signalled carrier for performing Random Access procedure; + - 2> set the *PCMAX* to $P_{\text{CMAX,fc}}$ of the signalled carrier. +- 1> else if the carrier to use for the Random Access procedure is not explicitly signalled; and +- 1> if the Serving Cell for the Random Access procedure is configured with supplementary uplink as specified in TS 38.331 [5]; and +- 1> if the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdSSB-SUL*: + - 2> select the SUL carrier for performing Random Access procedure; + - 2> set the *PCMAX* to $P_{\text{CMAX,fc}}$ of the SUL carrier. +- 1> else: + - 2> select the NUL carrier for performing Random Access procedure; + - 2> set the *PCMAX* to $P_{\text{CMAX,fc}}$ of the NUL carrier. + +NOTE 4: Void. + +- 1> perform the BWP operation as specified in clause 5.15, except when the Random Access procedure is initiated by the PDCCH order to an LTM candidate cell; +- 1> select the set of Random Access resources applicable to the current Random Access procedure according to clause 5.1.1b; +- 1> if the Random Access procedure is initiated by PDCCH order and if the *ra-PreambleIndex* explicitly provided by PDCCH is not 0b000000; or +- 1> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]) and the Random Access Resources for SI request have been explicitly provided by RRC; or +- 1> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause 5.17) and if the contention-free Random Access Resources for beam failure recovery request for 4-step RA type have been explicitly provided by RRC for the BWP selected for Random Access procedure; or +- 1> if the Random Access procedure was initiated for reconfiguration with sync and if the contention-free Random Access Resources for 4-step RA type have been explicitly provided in *rach-ConfigDedicated* for the BWP selected for Random Access procedure; or + +- 1> if the Random Access procedure was initiated for LTM cell switch and if the contention-free Random Access Resources have been explicitly provided in LTM Cell Switch Command MAC CE: + - 2> set the *RA\_TYPE* to *4-stepRA*. +- 1> else if the BWP selected for Random Access procedure is configured with both 2-step and 4-step RA type Random Access Resources within the selected set of Random Access resources (as specified in clause 5.1.1b) and the RSRP of the downlink pathloss reference is above *msgA-RSRP-Threshold*; or +- 1> if the BWP selected for Random Access procedure is only configured with 2-step RA type Random Access resources within the selected set of Random Access resources according to clause 5.1.1b; or +- 1> if the Random Access procedure was initiated for reconfiguration with sync and if the contention-free Random Access Resources for 2-step RA type have been explicitly provided in *rach-ConfigDedicated* for the BWP selected for Random Access procedure: + - 2> set the *RA\_TYPE* to *2-stepRA*. +- 1> else: + - 2> set the *RA\_TYPE* to *4-stepRA*. +- 1> perform initialization of variables specific to Random Access type as specified in clause 5.1.1a; +- 1> if *RA\_TYPE* is set to *2-stepRA*: + - 2> perform the Random Access Resource selection procedure for 2-step RA type (see clause 5.1.2a). +- 1> else: + - 2> perform the Random Access Resource selection procedure (see clause 5.1.2). + +### 5.1.1a Initialization of variables specific to Random Access type + +The MAC entity shall: + +- 1> if *RA\_TYPE* is set to *2-stepRA*: + - 2> set *PREAMBLE\_POWER\_RAMPING\_STEP* to *msgA-PreamblePowerRampingStep*; + - 2> set *SCALING\_FACTOR\_BI* to 1; + - 2> apply *preambleTransMax* included in the *RACH-ConfigGenericTwoStepRA*; + - 2> if the Random Access procedure was initiated for reconfiguration with sync or for SCG activation; and + - 2> if *cfra-TwoStep* is configured for the selected carrier: + - 3> if *msgA-TransMax* is configured in the *cfra-TwoStep*: + - 4> apply *msgA-TransMax* configured in the *cfra-TwoStep*. + - 2> else if *msgA-TransMax* is included in the *RACH-ConfigCommonTwoStepRA*: + - 3> apply *msgA-TransMax* included in the *RACH-ConfigCommonTwoStepRA*. + - 2> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause 5.17); and + - 2> if *beamFailureRecoveryConfig* is configured for the active UL BWP of the selected carrier; and + - 2> if *ra-PrioritizationTwoStep* is configured in the *beamFailureRecoveryConfig*: + - 3> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority* included in the *ra-PrioritizationTwoStep* in *beamFailureRecoveryConfig*; + - 3> if *scalingFactorBI* is configured in the *ra-PrioritizationTwoStep* in *beamFailureRecoveryConfig*: + - 4> apply *scalingFactorBI* configured in the *ra-PrioritizationTwoStep* in *beamFailureRecoveryConfig*. + +- 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. +- 2> else if the Random Access procedure was initiated for reconfiguration with sync or for SCG activation; and +- 2> if *rach-ConfigDedicated* is configured for the selected carrier; and +- 2> if *ra-PrioritizationTwoStep* is configured in the *rach-ConfigDedicated*: + - 3> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority* included in the *ra-PrioritizationTwoStep* in *rach-ConfigDedicated*; + - 3> if *scalingFactorBI* is configured in *ra-PrioritizationTwoStep* in the *rach-ConfigDedicated*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. +- 2> else if both *ra-PrioritizationForSlicingTwoStep* for a *NSAG-ID* and *ra-PrioritizationForAccessIdentityTwoStep* are configured for the selected carrier; and +- 2> if the MAC entity is provided by upper layers with both this *NSAG-ID* and Access Identity 1 or 2; and +- 2> if for at least one of these Access Identities the corresponding bit in the *ra-PrioritizationForAI* is set to *one*: + - 3> if *enableRA-PrioritizationForSlicing* is set to *true*: + - 4> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForSlicingTwoStep* for this *NSAG-ID*: + - 5> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 4> if *scalingFactorBI* is configured in the *ra-PrioritizationForSlicingTwoStep* for this *NSAG-ID*: + - 5> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 3> else if *enableRA-PrioritizationForSlicing* is set to *false*: + - 4> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForAccessIdentityTwoStep*: + - 5> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 4> if *scalingFactorBI* is configured in the *ra-PrioritizationForAccessIdentityTwoStep*: + - 5> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. +- 2> else if *ra-PrioritizationForSlicingTwoStep* for a *NSAG-ID* is configured for the selected carrier; and +- 2> if the MAC entity is provided by upper layers with this *NSAG-ID*: + - 3> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForSlicingTwoStep* for this *NSAG-ID*: + - 4> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 3> if *scalingFactorBI* is configured in the *ra-PrioritizationForSlicingTwoStep* for this *NSAG-ID*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. +- 2> else if *ra-PrioritizationForAccessIdentityTwoStep* is configured for the selected carrier; and +- 2> if the MAC entity is provided by upper layers with Access Identity 1 or 2; and +- 2> if for at least one of these Access Identities the corresponding bit in the *ra-PrioritizationForAI* is set to *one*: + - 3> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForAccessIdentityTwoStep*: + - 4> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 3> if *scalingFactorBI* is configured in the *ra-PrioritizationForAccessIdentityTwoStep*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + +- 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 2> set *MSG\_A\_PREAMBLE\_POWER\_RAMPING\_STEP* to *PREAMBLE\_POWER\_RAMPING\_STEP*. +- 1> else (i.e. *RA\_TYPE* is set to *4-stepRA*): + - 2> set *PREAMBLE\_POWER\_RAMPING\_STEP* to *powerRampingStep*; + - 2> set *SCALING\_FACTOR\_BI* to 1; + - 2> set *preambleTransMax* to *preambleTransMax* included in the *RACH-ConfigGeneric*; + - 2> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause 5.17); and + - 2> if *beamFailureRecoveryConfig* is configured for the active UL BWP of the selected carrier: + - 3> start the *beamFailureRecoveryTimer*, if configured; + - 3> apply the parameters *powerRampingStep*, *preambleReceivedTargetPower*, and *preambleTransMax* configured in the *beamFailureRecoveryConfig*. + - 2> if the Random Access procedure was initiated for beam failure recovery (as specified in clause 5.17); and + - 2> if *beamFailureRecoveryConfig* is configured for the active UL BWP of the selected carrier; and + - 2> if *ra-Prioritization* is configured in the *beamFailureRecoveryConfig*: + - 3> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority* included in the *ra-Prioritization* in *beamFailureRecoveryConfig*; + - 3> if *scalingFactorBI* is configured in *ra-Prioritization* in the *beamFailureRecoveryConfig*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 2> else if the Random Access procedure was initiated for reconfiguration with sync or for SCG activation; and + - 2> if *rach-ConfigDedicated* is configured for the selected carrier; and + - 2> if *ra-Prioritization* is configured in the *rach-ConfigDedicated*: + - 3> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority* included in the *ra-Prioritization* in *rach-ConfigDedicated*; + - 3> if *scalingFactorBI* is configured in *ra-Prioritization* in the *rach-ConfigDedicated*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 2> else if both *ra-PrioritizationForSlicing* for a *NSAG-ID* and *ra-PrioritizationForAccessIdentity* are configured for the selected carrier; and + - 2> if the MAC entity is provided by upper layers with both this *NSAG-ID* and Access Identity 1 or 2; and + - 2> if for at least one of these Access Identities the corresponding bit in the *ra-PrioritizationForAI* is set to *one*: + - 3> if *enableRA-PrioritizationForSlicing* is set to *true*: + - 4> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForSlicing* for this *NSAG-ID*: + - 5> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 4> if *scalingFactorBI* is configured in the *ra-PrioritizationForSlicing* for this *NSAG-ID*: + - 5> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 3> else if *enableRA-PrioritizationForSlicing* is set to *false*: + - 4> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForAccessIdentity*: + - 5> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + +- 5> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 4> if *scalingFactorBI* is configured in the *ra-PrioritizationForAccessIdentity*: + - 5> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 2> else if *ra-PrioritizationForSlicing* for a *NSAG-ID* is configured for the selected carrier; and + - 2> if the MAC entity is provided by upper layers with this *NSAG-ID*: + - 3> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForSlicing* for this *NSAG-ID*: + - 4> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 3> if *scalingFactorBI* is configured in the *ra-PrioritizationForSlicing* for this *NSAG-ID*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 2> else if *ra-PrioritizationForAccessIdentity* is configured for the selected carrier; and + - 2> if the MAC entity is provided by upper layers with Access Identity 1 or 2; and + - 2> if for at least one of these Access Identities the corresponding bit in the *ra-PrioritizationForAI* is set to *one*: + - 3> if *powerRampingStepHighPriority* is configured in the *ra-PrioritizationForAccessIdentity*: + - 4> set *PREAMBLE\_POWER\_RAMPING\_STEP* to the *powerRampingStepHighPriority*. + - 3> if *scalingFactorBI* is configured in the *ra-PrioritizationForAccessIdentity*: + - 4> set *SCALING\_FACTOR\_BI* to the *scalingFactorBI*. + - 2> if *RA\_TYPE* is switched from *2-stepRA* to *4-stepRA* during this Random Access procedure: + - 3> set *POWER\_OFFSET\_2STEP\_RA* to $(PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) \times (MSGA\_PREAMBLE\_POWER\_RAMPING\_STEP - PREAMBLE\_POWER\_RAMPING\_STEP)$ . +- NOTE: If *enableRA-PrioritizationForSlicing* is not configured in *BWP-UplinkCommon* and if both the provided *NSAG-ID* and the provided Access Identity whose corresponding bit in the *ra-PrioritizationForAI* is set to *one* are configured with *ra-Prioritization* either in *RACH-ConfigCommon* or *RACH-ConfigCommonTwoStepRA*, it is up to UE implementation how to determine the values of *PREAMBLE\_POWER\_RAMPING\_STEP* and *SCALING\_FACTOR\_BI*. + +### 5.1.1b Selection of the set of Random Access resources for the Random Access procedure + +The MAC entity shall: + +- 1> if the BWP selected for Random Access procedure is configured with both set(s) of Random Access resources with *msg3-Repetitions* set to *true* and set(s) of Random Access resources without *msg3-Repetitions* set to *true* and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg3*; or +- 1> if the BWP selected for Random Access procedure is only configured with the set(s) of Random Access resources with *msg3-Repetitions* set to *true*: + - 2> assume Msg3 repetition is applicable for the current Random Access procedure. +- 1> else: + - 2> assume Msg3 repetition is not applicable for the current Random Access procedure. +- 1> if contention-free Random Access Resources have been provided for this Random Access procedure and a Msg1 repetition number is indicated in *rach-ConfigDedicated*: + - 2> assume Msg1 repetition is applicable and Msg1 repetition number applicable for the current Random Access procedure is the Msg1 repetition number indicated in *rach-ConfigDedicated*. + +- 1> else if contention free Random Access Resources have not been provided for this Random Access procedure and the BWP selected for the Random Access procedure is configured with set(s) of Random Access resources with *msg1-Repetitions* set to *true* and set(s) of Random Access resources without *msg1-Repetitions* set to *true*: + - 2> if the BWP selected for the Random Access procedure is configured with set(s) of Random Access resources associated with Msg1 repetition number 8 and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum8*: + - 3> assume Msg1 repetition is applicable and Msg1 repetition number applicable for the current Random Access procedure includes 8. + - 2> if the BWP selected for the Random Access procedure is configured with set(s) of Random Access resources associated with Msg1 repetition number 4 and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum4*: + - 3> assume Msg1 repetition is applicable and Msg1 repetition number applicable for the current Random Access procedure includes 4. + - 2> if the BWP selected for the Random Access procedure is configured with set(s) of Random Access resources associated with Msg1 repetition number 2 and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum2*: + - 3> assume Msg1 repetition is applicable and Msg1 repetition number applicable for the current Random Access procedure includes 2. + - 2> else if the RSRP of the downlink pathloss reference is not less than any configured *rsrp-ThresholdMsg1-RepetitionNumX*: + - 3> assume Msg1 repetition is not applicable for the current Random Access procedure. +- 1> else if the BWP selected for Random Access procedure is configured only with Random Access resources with *msg1-Repetitions* set to *true*: + - 2> assume Msg1 repetition is applicable for the current Random Access procedure; + - 2> if at least one of *rsrp-ThresholdMsg1-RepetitionNumX* is configured: + - 3> if *rsrp-ThresholdMsg1-RepetitionNum8* is configured and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum8*: + - 4> assume Msg1 repetition number applicable for the current Random Access procedure includes 8. + - 3> if *rsrp-ThresholdMsg1-RepetitionNum4* is configured and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum4*: + - 4> assume Msg1 repetition number applicable for the current Random Access procedure includes 4. + - 3> if *rsrp-ThresholdMsg1-RepetitionNum2* is configured and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum2*: + - 4> assume Msg1 repetition number applicable for the current Random Access procedure includes 2. + - 3> else if the RSRP of the downlink pathloss reference is not less than any configured *rsrp-ThresholdMsg1-RepetitionNumX*: + - 4> assume Msg1 repetition number applicable for the current Random Access procedure is the lowest Msg1 repetition number configured for this BWP. + - 2> else (none of *rsrp-ThresholdMsg1-RepetitionNumX* is configured): + - 3> assume Msg1 repetition number applicable for the current Random Access procedure is the Msg1 repetition number that configured for this BWP. + +NOTE 1: Void. + +1> if neither contention-free Random Access Resources nor Random Access Resources for SI request have been provided for this Random Access procedure and one or more of the features including (e)RedCap and/or Slicing and/or SDT and/or MSG3 repetition and/or MSG1 repetition is applicable for this Random Access procedure: + +NOTE 2: The applicability of SDT is determined by MAC entity according to clause 5.27. The applicability of *NSAG-ID* is determined by upper layers when the Random Access procedure is initiated. The applicability of (e)RedCap is also determined by upper layers when Random Access procedure is initiated and it is applicable to the Random Access procedures initiated by PDCCH orders and any Random Access procedure initiated by the MAC entity. + +NOTE 3: SDT is not applicable for the Random Access procedure initiated by upper layers for MT-SDT. + +2> if none of the sets of Random Access resources are available for any feature applicable to the current Random Access procedure (as specified in clause 5.1.1c): + +3> select the set(s) of Random Access resources that are not associated with any feature indication (as specified in clause 5.1.1c) for this Random Access procedure. + +2> else if there is one set of Random Access resources available which can be used for indicating all features triggering this Random Access procedure: + +3> select this set of Random Access resources for this Random Access procedure. + +2> else if there are more than one set of Random Access resources available which can be used for indicating all features triggering this Random Access procedure and Msg1 repetition is applicable for this Random Access procedure: + +3> select the set of Random Access resources that associated with highest repetition number among the sets of Random Access resources. + +2> else (i.e. there are one or more sets of Random Access resources available that are configured with indication(s) for a subset of all features triggering this Random Access procedure): + +3> select a set of Random Access resources from the available set(s) of Random Access resources based on the priority order indicated by upper layers as specified in clause 5.1.1d for this Random Access Procedure. + +1> else if contention-free Random Access Resources with Msg1 repetition have been provided for this Random Access procedure and Msg1 repetition number is indicated in *rach-ConfigDedicated*, and RedCap is applicable for the current Random Access procedure: + +2> select the set of Random Access resources that is only configured with RedCap indication and Msg1 repetition indication and associated with the indicated Msg1 repetition number for this Random Access procedure. + +1> else if contention-free Random Access Resources have been provided for this Random Access procedure and RedCap is applicable for the current Random Access procedure and there is one set of Random Access resources available that is only configured with RedCap indication; or + +1> else if contention-free Random Access Resources have been provided for this Random Access procedure and eRedCap is applicable for the current Random Access procedure and there is one set of Random Access resources available that is only configured with eRedCap indication; or + +1> else if contention-free Random Access Resources have been provided for this Random Access procedure and eRedCap is applicable for the current Random Access procedure and there is no set of Random Access resources available that is only configured with eRedCap indication and there is one set of Random Access resources available that is only configured with RedCap indication: + +2> select this set of Random Access resources for this Random Access procedure. + +1> else: + +2> if the Random Access procedure is initiated by PDCCH order with DCI *PRACH association indicator* field set to 1 and *SSB-MTC-AdditionalPCI* is configured by upper layers, as specified in clause 7.3.1.2.1 of TS 38.212 [9]: + +- 3> select the set of Random Access resources corresponding to the active *additionalPCI*. +- 2> else if contention-free Random Access Resources with Msg1 repetition have been provided for this Random Access procedure, and Msg1 repetition number is indicated in *rach-ConfigDedicated*: + - 3> select the set of Random Access resources that is only configured with Msg1 repetition indication and associated with the indicated Msg1 repetition number for this Random Access procedure. +- 2> else if the Random Access procedure was initiated for SI request and Random Access Resources associated with Msg1 repetition for SI request and Msg1 repetition number have been provided for this Random Access procedure: + - 3> select the set of Random Access resources that is only configured with Msg1 repetition indication and associated with the indicated Msg1 repetition number for this Random Access procedure. +- 2> else: + - 3> select the set of Random Access resources that are not associated with any feature indication (as specified in clause 5.1.1c) for the current Random Access procedure. + +### 5.1.1c Availability of the set of Random Access resources + +The MAC entity shall for each set of configured Random Access resources for 4-step RA type and for each set of configured Random Access resources for 2-step RA type: + +- 1> if *eRedCap* is set to *true* for a set of Random Access resources: + - 2> consider the set of Random Access resources as not available for a Random Access procedure for which *eRedCap* is not applicable. +- 1> if *redCap* is set to *true* for a set of Random Access resources configured for 4-step RA type, but not for 2-step RA type: + - 2> consider the set of Random Access resources as not available for a Random Access procedure for which *RedCap* is not applicable. +- 1> if *redCap* is set to *true* for a set of Random Access resources configured for 2-step RA type regardless of whether it is also configured for 4-step RA type: + - 2> consider the set of Random Access resources as not available for a Random Access procedure for which (e)*RedCap* is not applicable; + - 2> consider *eRedCap* as both *eRedCap* and *RedCap* in the following procedure in clause 5.1.1c and 5.1.1d. +- 1> if *smallData* is set to *true* for a set of Random Access resources: + - 2> consider the set of Random Access resources as not available for the Random Access procedure which is not triggered for RA-SDT by MO-SDT as specified in TS 38.331 [5]. +- 1> if *NSAG-List* is configured for a set of Random Access resources: + - 2> consider the set of Random Access resources as not available for the Random Access procedure unless it is triggered for any one of the *NSAG-ID(s)* in the *NSAG-List*. +- 1> if *msg3-Repetitions* is set to *true* for a set of Random Access resources: + - 2> consider the set of Random Access resources as not available for the Random Access procedure if Msg3 repetition is not applicable. +- 1> if *msg1-Repetitions* is set to *true* for a set of Random Access resources: + - 2> if Msg1 repetition is not applicable to the current Random Access procedure; or + - 2> if the set of Random Access resources is not associated with any of the Msg1 repetition number that is applicable to the current Random Access procedure: + +- 3> consider the set of Random Access resources as not available for the Random Access procedure. +- 1> if a set of Random Access resources is not configured with *FeatureCombination*: + - 2> consider the set of Random Access resources to not associated with any feature. + +### 5.1.1d Selection of the set of Random Access resources based on feature prioritization + +The MAC entity shall: + +- 1> among the available sets of Random Access resources for this Random Access procedure (as specified in clause 5.1.1c), identify those configured with a feature which has the highest priority assigned in *featurePriorities* among all the features applicable to this Random Access procedure as specified in TS 38.331 [5]. +- 1> if a single set of Random Access resources is identified: + - 2> select this set of Random Access resources. +- 1> else if more than one set of Random Access resources is identified: + - 2> if all the identified sets of Random Access resources are configured with Msg1 repetition indication and the same *featureCombination*: + - 3> select the set of Random Access resources that associated with highest Msg1 repetition number among the identified sets of Random Access resources. + - 2> else: + - 3> repeat the procedure taking as an input the identified sets of Random Access resources and the feature applicable to the current Random Access procedure with the highest priority assigned in *featurePriorities* among all the features applicable to this Random Access procedure, except the features considered already. +- 1> else (i.e. no set of Random Access resources is identified): + - 2> repeat the procedure taking as an input the previous identified available sets of Random Access resources and the feature applicable to the current Random Access procedure with the highest priority assigned in *featurePriorities* among all the features applicable to this Random Access procedure, except the features considered already. + +### 5.1.1e Selection of Msg1 repetition for SI request + +The MAC entity shall: + +- 1> if *si-RequestResourcesRepetitionNum8* is configured and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum8*: + - 2> criteria to apply Msg1 repetition for SI request is considered met and Msg1 repetition number applicable is 8. +- 1> else if *si-RequestResourcesRepetitionNum4* is configured and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum4*: + - 2> criteria to apply Msg1 repetition for SI request is considered met and Msg1 repetition number applicable is 4. +- 1> else *si-RequestResourcesRepetitionNum2* is configured and the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdMsg1-RepetitionNum2*: + - 2> criteria to apply Msg1 repetition for SI request is considered met and Msg1 repetition number applicable is 2. + +## 5.1.2 Random Access Resource selection + +If the selected *RA\_TYPE* is set to *4-stepRA*, the MAC entity shall: + +- 1> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause 5.17); and +- 1> if the *beamFailureRecoveryTimer* (in clause 5.17) is either running or not configured; and +- 1> if the contention-free Random Access Resources for beam failure recovery request associated with any of the SSBs and/or CSI-RSs have been explicitly provided by RRC; and +- 1> if at least one of the SSBs with SS-RSRP above *rsrp-ThresholdSSB* amongst the SSBs in *candidateBeamRSList* or the CSI-RSs with CSI-RSRP above *rsrp-ThresholdCSI-RS* amongst the CSI-RSs in *candidateBeamRSList* is available: + - 2> select an SSB with SS-RSRP above *rsrp-ThresholdSSB* amongst the SSBs in *candidateBeamRSList* or a CSI-RS with CSI-RSRP above *rsrp-ThresholdCSI-RS* amongst the CSI-RSs in *candidateBeamRSList*; + - 2> if CSI-RS is selected, and there is no *ra-PreambleIndex* associated with the selected CSI-RS: + - 3> set the *PREAMBLE\_INDEX* to a *ra-PreambleIndex* corresponding to the SSB in *candidateBeamRSList* which is quasi-colocated with the selected CSI-RS as specified in TS 38.214 [7]. + - 2> else: + - 3> set the *PREAMBLE\_INDEX* to a *ra-PreambleIndex* corresponding to the selected SSB or CSI-RS from the set of Random Access Preambles for beam failure recovery request. +- 1> else if the *ra-PreambleIndex* has been explicitly provided by PDCCH; and +- 1> if the *ra-PreambleIndex* is not 0b000000: + - 2> set the *PREAMBLE\_INDEX* to the signalled *ra-PreambleIndex*; + - 2> select the SSB signalled by PDCCH. +- 1> else if the *ra-PreambleIndex* has been explicitly provided by an LTM Cell Switch Command MAC CE: + - 2> set the *PREAMBLE\_INDEX* to the indicated *ra-PreambleIndex*; + - 2> select the SSB signalled by the LTM Cell Switch Command MAC CE. +- 1> else if the contention-free Random Access Resources associated with SSBs have been explicitly provided in *rach-ConfigDedicated* and at least one SSB with SS-RSRP above *rsrp-ThresholdSSB* amongst the associated SSBs is available: + - 2> select an SSB with SS-RSRP above *rsrp-ThresholdSSB* amongst the associated SSBs; + - 2> set the *PREAMBLE\_INDEX* to a *ra-PreambleIndex* corresponding to the selected SSB. +- 1> else if the contention-free Random Access Resources associated with CSI-RSs have been explicitly provided in *rach-ConfigDedicated* and at least one CSI-RS with CSI-RSRP above *rsrp-ThresholdCSI-RS* amongst the associated CSI-RSs is available: + - 2> select a CSI-RS with CSI-RSRP above *rsrp-ThresholdCSI-RS* amongst the associated CSI-RSs; + - 2> set the *PREAMBLE\_INDEX* to a *ra-PreambleIndex* corresponding to the selected CSI-RS. +- 1> else if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and +- 1> if the Random Access Resources for SI request have been explicitly provided by RRC: + - 2> if at least one of the SSBs with SS-RSRP above *rsrp-ThresholdSSB* is available: + - 3> select an SSB with SS-RSRP above *rsrp-ThresholdSSB*. + - 2> else: + - 3> select any SSB. + - 2> select a Random Access Preamble corresponding to the selected SSB, from the Random Access Preamble(s) determined according to *ra-PreambleStartIndex* as specified in TS 38.331 [5]; + +- 2> set the *PREAMBLE\_INDEX* to selected Random Access Preamble. +- 1> else (i.e. for the contention-based Random Access preamble selection): + - 2> if at least one of the SSBs with SS-RSRP above *rsrp-ThresholdSSB* is available: + - 3> select an SSB with SS-RSRP above *rsrp-ThresholdSSB*. + - 2> else: + - 3> select any SSB. + - 2> if the *RA\_TYPE* is switched from *2-stepRA* to *4-stepRA*: + - 3> if a Random Access Preambles group was selected during the current Random Access procedure: + - 4> select the same group of Random Access Preambles as was selected for the 2-step RA type. + - 3> else: + - 4> if Random Access Preambles group B is configured; and + - 4> if the transport block size of the MSGA payload configured in the *rach-ConfigDedicated* corresponds to the transport block size of the MSGA payload associated with Random Access Preambles group B: + - 5> select the Random Access Preambles group B. + - 4> else: + - 5> select the Random Access Preambles group A. + - 2> else if Msg3 buffer is empty: + - 3> if Random Access Preambles group B is configured: + - 4> if the potential Msg3 size (UL data available for transmission plus MAC subheader(s) and, where required, MAC CEs) is greater than *ra-Msg3SizeGroupA* and the pathloss is less than *PCMAX* (of the Serving Cell performing the Random Access Procedure) – *preambleReceivedTargetPower* – *msg3-DeltaPreamble* – *messagePowerOffsetGroupB*; or + - 4> if the Random Access procedure was initiated for the CCCH logical channel and the CCCH SDU size plus MAC subheader is greater than *ra-Msg3SizeGroupA*: + - 5> select the Random Access Preambles group B. + - 4> else: + - 5> select the Random Access Preambles group A. + - 3> else: + - 4> select the Random Access Preambles group A. + - 2> else (i.e. Msg3 is being retransmitted): + - 3> select the same group of Random Access Preambles as was used for the Random Access Preamble transmission attempt corresponding to the first transmission of Msg3. + - 2> select a Random Access Preamble randomly with equal probability from the Random Access Preambles associated with the selected SSB and the selected Random Access Preambles group; + - 2> set the *PREAMBLE\_INDEX* to the selected Random Access Preamble. +- 1> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and +- 1> if *ra-AssociationPeriodIndex* and *si-RequestPeriod* are configured: + +- 2> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB in the association period given by *ra-AssociationPeriodIndex* in the *si-RequestPeriod* permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6] corresponding to the selected SSB). +- 1> else if an SSB is selected above: + - 2> if the set of Random Access resources associated with Msg1 repetition is selected for this Random Access procedure: + - 3> determine the next available set of PRACH occasions (as specified in TS 38.213 [6]) for the Msg1 repetition number applicable for this Random Access procedure corresponding to the selected SSB, permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured, or *ssb-SharedRO-MaskIndex* if configured (the MAC entity shall select a set of PRACH occasions randomly with equal probability amongst the consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6] regardless the FR2 UL gap, corresponding to the selected SSB and selected Msg1 repetition number for this Random Access procedure; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available set of PRACH occasions corresponding to the selected SSB). + - 2> else: + - 3> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured, or *ssb-SharedRO-MaskIndex* if configured, or indicated by PDCCH, or indicated by the LTM Cell Switch Command MAC CE (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6] regardless the FR2 UL gap, corresponding to the selected SSB; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB). +- 1> else if a CSI-RS is selected above: + - 2> if there is no contention-free Random Access Resource associated with the selected CSI-RS: + - 3> determine the next available PRACH occasion from the PRACH occasions, permitted by the restrictions given by the *ra-ssb-OccasionMaskIndex* if configured, corresponding to the SSB in *candidateBeamRSList* which is quasi-colocated with the selected CSI-RS as specified in TS 38.214 [7] (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6] regardless the FR2 UL gap, corresponding to the SSB which is quasi-colocated with the selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the SSB which is quasi-colocated with the selected CSI-RS). + - 2> else: + - 3> determine the next available PRACH occasion from the PRACH occasions in *ra-OccasionList* corresponding to the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers regardless the FR2 UL gap, corresponding to the selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected CSI-RS). +- 1> perform the Random Access Preamble transmission procedure (see clause 5.1.3). + +NOTE 1: When the UE determines if there is an SSB with SS-RSRP above *rsrp-ThresholdSSB* or a CSI-RS with CSI-RSRP above *rsrp-ThresholdCSI-RS*, the UE uses the latest unfiltered L1-RSRP measurement. + +NOTE 2: Void. + +- NOTE 3: If an (e)RedCap UE in RRC\_IDLE or RRC\_INACTIVE mode is configured with a BWP indicated by *initialDownlinkBWP-RedCap* which is not associated with any SSB, SS-RSRP measurement is performed based on the SSB associated with the BWP indicated by *initialDownlinkBWP*. If a RedCap UE in RRC\_INACTIVE mode is configured with SDT and with a BWP indicated by *initialDownlinkBWP-RedCap* which is associated with NCD-SSB, SS-RSRP measurement can also be performed based on this NCD-SSB during SDT. +- NOTE 4: If an (e)RedCap UE in RRC\_IDLE or RRC\_INACTIVE mode is configured with a BWP indicated by *initialDownlinkBWP-RedCap* which is not associated with any SSB for RACH, it is up to the UE implementation to perform a new RSRP measurements before Msg1/MsgA retransmission. + +## 5.1.2a Random Access Resource selection for 2-step RA type + +If the selected *RA\_TYPE* is set to *2-stepRA*, the MAC entity shall: + +- 1> if the contention-free 2-step RA type Resources associated with SSBs have been explicitly provided in *rach-ConfigDedicated* and at least one SSB with SS-RSRP above *msgA-RSRP-ThresholdSSB* amongst the associated SSBs is available: + - 2> select an SSB with SS-RSRP above *msgA-RSRP-ThresholdSSB* amongst the associated SSBs; + - 2> set the *PREAMBLE\_INDEX* to a *ra-PreambleIndex* corresponding to the selected SSB. +- 1> else (i.e. for the contention-based Random Access Preamble selection): + - 2> if at least one of the SSBs with SS-RSRP above *msgA-RSRP-ThresholdSSB* is available: + - 3> select an SSB with SS-RSRP above *msgA-RSRP-ThresholdSSB*. + - 2> else: + - 3> select any SSB. + - 2> if contention-free Random Access Resources for 2-step RA type have not been configured and if Random Access Preambles group has not yet been selected during the current Random Access procedure: + - 3> if Random Access Preambles group B for 2-step RA type is configured: + - 4> if the potential MSGA payload size (UL data available for transmission plus MAC subheader and, where required, MAC CEs) is greater than the *ra-MsgA-SizeGroupA* and the pathloss is less than *PCMAX* (of the Serving Cell performing the Random Access Procedure) – *msgA-PreambleReceivedTargetPower* – *msgA-DeltaPreamble* – *messagePowerOffsetGroupB*; or + - 4> if the Random Access procedure was initiated for the CCCH logical channel and the CCCH SDU size plus MAC subheader is greater than *ra-MsgA-SizeGroupA*: + - 5> select the Random Access Preambles group B. + - 4> else: + - 5> select the Random Access Preambles group A. + - 3> else: + - 4> select the Random Access Preambles group A. + - 2> else if contention-free Random Access Resources for 2-step RA type have been configured and if Random Access Preambles group has not yet been selected during the current Random Access procedure: + - 3> if Random Access Preambles group B for 2-step RA type is configured; and + - 3> if the transport block size of the MSGA payload configured in the *rach-ConfigDedicated* corresponds to the transport block size of the MSGA payload associated with Random Access Preambles group B: + +- 4> select the Random Access Preambles group B. +- 3> else: + - 4> select the Random Access Preambles group A. +- 2> else (i.e. Random Access preambles group has been selected during the current Random Access procedure): + - 3> select the same group of Random Access Preambles as was used for the Random Access Preamble transmission attempt corresponding to the earlier transmission of MSGA. +- 2> select a Random Access Preamble randomly with equal probability from the 2-step RA type Random Access Preambles associated with the selected SSB and the selected Random Access Preambles group; +- 2> set the *PREAMBLE\_INDEX* to the selected Random Access Preamble. +- 1> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the *msgA-SSB-SharedRO-MaskIndex* if configured, or *ra-ssb-OccasionMaskIndex* if configured, or *ssb-SharedRO-MaskIndex* if configured (the MAC entity shall select a PRACH occasion randomly with equal probability among the consecutive PRACH occasions allocated for 2-step RA type according to clause 8.1 of TS 38.213 [6] regardless the FR2 UL gap, corresponding to the selected SSB; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB); +- 1> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble(s): + - 2> select a PUSCH occasion from the PUSCH occasions configured in *msgA-CFRA-PUSCH* corresponding to the PRACH slot of the selected PRACH occasion, according to *msgA-PUSCH-Resource-Index* corresponding to the selected SSB; + - 2> determine the UL grant and the associated HARQ information for the MSGA payload in the selected PUSCH occasion; + - 2> deliver the UL grant and the associated HARQ information to the HARQ entity. +- 1> else: + - 2> select a PUSCH occasion corresponding to the selected preamble and PRACH occasion according to clause 8.1A of TS 38.213 [6]; + - 2> determine the UL grant for the MSGA payload according to the PUSCH configuration associated with the selected Random Access Preambles group and determine the associated HARQ information; + - 2> if the selected preamble and PRACH occasion is mapped to a valid PUSCH occasion as specified in clause 8.1A of TS 38.213 [6]: + - 3> deliver the UL grant and the associated HARQ information to the HARQ entity. +- 1> perform the MSGA transmission procedure (see clause 5.1.3a). + +NOTE 1: To determine if there is an SSB with *SS-RSRP* above *msgA-RSRP-ThresholdSSB*, the UE uses the latest unfiltered *LI-RSRP* measurement. + +NOTE 2: If an (e)RedCap UE in RRC\_IDLE or RRC\_INACTIVE mode is configured with a BWP indicated by *initialDownlinkBWP-RedCap* which is not associated with any SSB, SS-RSRP measurement is performed based on the SSB associated with the BWP indicated by *initialDownlinkBWP*. If a RedCap UE in RRC\_INACTIVE mode is configured with SDT and with a BWP indicated by *initialDownlinkBWP-RedCap* which is associated with NCD-SSB, SS-RSRP measurement can also be performed based on this NCD-SSB during SDT. + +NOTE 3: If an (e)RedCap UE in RRC\_IDLE or RRC\_INACTIVE mode is configured with a BWP indicated by *initialDownlinkBWP-RedCap* which is not associated with any SSB for RACH, it is up to the UE implementation to perform a new RSRP measurements before Msg1/MsgA retransmission. + +### 5.1.3 Random Access Preamble transmission + +The MAC entity shall, for each Random Access Preamble: + +- 1> if *PREAMBLE\_TRANSMISSION\_COUNTER* is greater than one; and +- 1> if the notification of suspending power ramping counter has not been received from lower layers; and +- 1> if LBT failure indication was not received from lower layers for the last Random Access Preamble transmission; and +- 1> if SSB or CSI-RS selected is not changed from the selection in the last Random Access Preamble transmission; and +- 1> if the Random Access procedure is not initiated by the PDCCH order for an LTM candidate cell: + - 2> increment *PREAMBLE\_POWER\_RAMPING\_COUNTER* by 1. +- 1> if the Random Access procedure is initiated by the PDCCH order for an LTM candidate cell as preamble re-transmission; and +- 1> if the PDCCH order indicates the same LTM candidate cell and the same SSB as the last Random Access Preamble transmission: + - 2> increment *PREAMBLE\_POWER\_RAMPING\_COUNTER* by 1. +- 1> select the value of *DELTA\_PREAMBLE* according to clause 7.3; +- 1> set *PREAMBLE\_RECEIVED\_TARGET\_POWER* to $preambleReceivedTargetPower + DELTA\_PREAMBLE + (PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) \times PREAMBLE\_POWER\_RAMPING\_STEP + POWER\_OFFSET\_2STEP\_RA$ ; +- 1> except for contention-free Random Access Preamble for beam failure recovery request and contention-free Random Access Preamble triggered by a PDCCH order for an LTM candidate cell, compute the RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted; +- 1> instruct the physical layer to transmit the Random Access Preamble using the selected PRACH occasion, corresponding RA-RNTI (if available), *PREAMBLE\_INDEX*, and *PREAMBLE\_RECEIVED\_TARGET\_POWER*. +- 1> if the Random Access Procedure is triggered by a PDCCH order for an LTM candidate cell: + - 2> consider this Random Access procedure completed. +- 1> if LBT failure indication is received from lower layers for this Random Access Preamble transmission: + - 2> if *lbt-FailureRecoveryConfig* is configured: + - 3> perform the Random Access Resource selection procedure (see clause 5.1.2). + - 2> else: + - 3> increment *PREAMBLE\_TRANSMISSION\_COUNTER* by 1; + - 3> if *PREAMBLE\_TRANSMISSION\_COUNTER* = *preambleTransMax* + 1: + - 4> if the Random Access Preamble is transmitted on the SpCell: + - 5> indicate a Random Access problem to upper layers; + - 5> if this Random Access procedure was triggered for SI request: + - 6> consider the Random Access procedure unsuccessfully completed. + - 4> else if the Random Access Preamble is transmitted on an SCell: + - 5> consider the Random Access procedure unsuccessfully completed. + +- 3> if the Random Access procedure is not completed: + - 4> perform the Random Access Resource selection procedure (see clause 5.1.2). + +The RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted or the RA-RNTI associated with the last valid PRACH occasion in the set of PRACH occasions (as specified in TS 38.213 [6]) for Msg1 repetition, is computed as: + +$$\text{RA-RNTI} = 1 + s\_id + 14 \times t\_id + 14 \times 80 \times f\_id + 14 \times 80 \times 8 \times ul\_carrier\_id$$ + +where $s\_id$ is the index of the first OFDM symbol of the PRACH occasion ( $0 \leq s\_id < 14$ ), $t\_id$ is the index of the first slot of the PRACH occasion in a system frame ( $0 \leq t\_id < 80$ ), where the subcarrier spacing to determine $t\_id$ is based on the value of $\mu$ specified in clause 5.3.2 in TS 38.211 [8] for $\mu = \{0, 1, 2, 3\}$ , and for $\mu = \{5, 6\}$ , $t\_id$ is the index of the 120 kHz slot in a system frame that contains the PRACH occasion ( $0 \leq t\_id < 80$ ), $f\_id$ is the index of the PRACH occasion in the frequency domain ( $0 \leq f\_id < 8$ ), and $ul\_carrier\_id$ is the UL carrier used for Random Access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). + +### 5.1.3a MSGA transmission + +The MAC entity shall, for each MSGA: + +- 1> if *PREAMBLE\_TRANSMISSION\_COUNTER* is greater than one; and +- 1> if the notification of suspending power ramping counter has not been received from lower layers; and +- 1> if LBT failure indication was not received from lower layers for the last MSGA Random Access Preamble transmission; and +- 1> if SSB selected is not changed from the selection in the last Random Access Preamble transmission: + - 2> increment *PREAMBLE\_POWER\_RAMPING\_COUNTER* by 1. +- 1> select the value of *DELTA\_PREAMBLE* according to clause 7.3; +- 1> set *PREAMBLE\_RECEIVED\_TARGET\_POWER* to $\text{msgA-PreambleReceivedTargetPower} + \text{DELTA\_PREAMBLE} + (\text{PREAMBLE\_POWER\_RAMPING\_COUNTER} - 1) \times \text{PREAMBLE\_POWER\_RAMPING\_STEP}$ ; +- 1> if this is the first MSGA transmission within this Random Access procedure: + - 2> if the transmission is not being made for the CCCH logical channel: + - 3> indicate to the Multiplexing and assembly entity to include a C-RNTI MAC CE in the subsequent uplink transmission. + - 2> if the Random Access procedure was initiated for SpCell beam failure recovery and *spCell-BFR-CBRA* with value *true* is configured: + - 3> if there is at least one Serving Cell of this MAC entity configured with two BFD-RS sets: + - 4> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission. + - 3> else: + - 4> indicate to the Multiplexing and assembly entity to include a BFR MAC CE or a Truncated BFR MAC CE in the subsequent uplink transmission. + - 2> else if the Random Access procedure was initiated for beam failure recovery of both BFD-RS sets of SpCell: + - 3> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission. + - 2> obtain the MAC PDU to transmit from the Multiplexing and assembly entity according to the HARQ information determined for the MSGA payload (see clause 5.1.2a) and store it in the MSGA buffer. + +- 1> compute the MSGB-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted; +- 1> instruct the physical layer to transmit the MSGA using the selected PRACH occasion and the associated PUSCH resource of MSGA (if the selected preamble and PRACH occasion is mapped to a valid PUSCH occasion), using the corresponding RA-RNTI, MSGB-RNTI, *PREAMBLE\_INDEX*, *PREAMBLE\_RECEIVED\_TARGET\_POWER*, *msgA-PreambleReceivedTargetPower*, and the amount of power ramping applied to the latest MSGA preamble transmission (i.e. $(PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) \times PREAMBLE\_POWER\_RAMPING\_STEP$ ); +- 1> if LBT failure indication is received from lower layers for the transmission of this MSGA Random Access Preamble: + - 2> instruct the physical layer to cancel the transmission of the MSGA payload on the associated PUSCH resource; + - 2> if *lbt-FailureRecoveryConfig* is configured: + - 3> perform the Random Access Resource selection procedure for 2-step RA type (see clause 5.1.2a). + - 2> else: + - 3> increment *PREAMBLE\_TRANSMISSION\_COUNTER* by 1; + - 3> if *PREAMBLE\_TRANSMISSION\_COUNTER* = *preambleTransMax* + 1: + - 4> indicate a Random Access problem to upper layers; + - 4> if this Random Access procedure was triggered for SI request: + - 5> consider this Random Access procedure unsuccessfully completed. + - 3> if the Random Access procedure is not completed: + - 4> if *msgA-TransMax* is applied (see clause 5.1.1a) and *PREAMBLE\_TRANSMISSION\_COUNTER* = *msgA-TransMax* + 1: + - 5> set the *RA\_TYPE* to *4-stepRA*; + - 5> perform initialization of variables specific to Random Access type as specified in clause 5.1.1a; + - 5> if the Msg3 buffer is empty: + - 6> obtain the MAC PDU to transmit from the MSGA buffer and store it in the Msg3 buffer; + - 5> flush HARQ buffer used for the transmission of MAC PDU in the MSGA buffer; + - 5> discard explicitly signalled contention-free 2-step RA type Random Access Resources, if any; + - 5> perform the Random Access Resource selection procedure as specified in clause 5.1.2. + - 4> else: + - 5> perform the Random Access Resource selection procedure for 2-step RA type (see clause 5.1.2a). + +NOTE: The MSGA transmission includes the transmission of the PRACH Preamble as well as the contents of the MSGA buffer in the PUSCH resource corresponding to the selected PRACH occasion and *PREAMBLE\_INDEX* (see TS 38.213 [6]) + +The MSGB-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, is computed as: + +$$MSGB-RNTI = 1 + s\_id + 14 \times t\_id + 14 \times 80 \times f\_id + 14 \times 80 \times 8 \times ul\_carrier\_id + 14 \times 80 \times 8 \times 2$$ + +where *s\_id* is the index of the first OFDM symbol of the PRACH occasion ( $0 \leq s\_id < 14$ ), *t\_id* is the index of the first slot of the PRACH occasion in a system frame ( $0 \leq t\_id < 80$ ), where the subcarrier spacing to determine *t\_id* is based on the value of $\mu$ specified in clause 5.3.2 in TS 38.211 [8] for $\mu = \{0, 1, 2, 3\}$ , and for $\mu = \{5, 6\}$ , *t\_id* is the index of + +the 120 kHz slot in a system frame that contains the PRACH occasion ( $0 \leq t\_id < 80$ ), $f\_id$ is the index of the PRACH occasion in the frequency domain ( $0 \leq f\_id < 8$ ), and $ul\_carrier\_id$ is the UL carrier used for Random Access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3. + +### 5.1.4 Random Access Response reception + +Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the MAC entity shall: + +- 1> if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC entity: + - 2> if the contention-free Random Access Preamble for beam failure recovery request was transmitted on a non-terrestrial network: + - 3> start the *ra-ResponseWindow* configured in *BeamFailureRecoveryConfig* at the PDCCH occasion as specified in TS 38.213 [6]. + - 2> else: + - 3> start the *ra-ResponseWindow* configured in *BeamFailureRecoveryConfig* at the first PDCCH occasion as specified in TS 38.213 [6] from the end of the Random Access Preamble transmission. + - 2> monitor for a PDCCH transmission on the search space indicated by *recoverySearchSpaceId* of the SpCell identified by the C-RNTI while *ra-ResponseWindow* is running. +- 1> else: + - 2> if the Random Access Preamble was transmitted on a non-terrestrial network: + - 3> start the *ra-ResponseWindow* configured in *RACH-ConfigCommon* at the PDCCH occasion as specified in TS 38.213 [6]. + - 2> else if the Random Access Preamble is transmitted with repetitions: + - 3> start the *ra-ResponseWindow* configured in *RACH-ConfigCommon* at the first PDCCH occasion from the end of all repetitions of the Random Access Preamble transmission as specified in TS 38.213 [6]. + - 2> else: + - 3> start the *ra-ResponseWindow* configured in *RACH-ConfigCommon* at the first PDCCH occasion as specified in TS 38.213 [6] from the end of the Random Access Preamble transmission. + - 2> monitor the PDCCH of the SpCell for Random Access Response(s) identified by the RA-RNTI while the *ra-ResponseWindow* is running. +- 1> if notification of a reception of a PDCCH transmission on the search space indicated by *recoverySearchSpaceId* is received from lower layers on the Serving Cell where the preamble was transmitted; and +- 1> if PDCCH transmission is addressed to the C-RNTI; and +- 1> if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC entity: + - 2> consider the Random Access procedure successfully completed. +- 1> else if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the RA-RNTI and the received TB is successfully decoded: + - 2> if the Random Access Response contains a MAC subPDU with Backoff Indicator: + - 3> set the *PREAMBLE\_BACKOFF* to value of the BI field of the MAC subPDU using Table 7.2-1, multiplied with *SCALING\_FACTOR\_BI*. + - 2> else: + +- 3> set the *PREAMBLE\_BACKOFF* to 0 ms. +- 2> if the Random Access Response contains a MAC subPDU with Random Access Preamble identifier corresponding to the transmitted *PREAMBLE\_INDEX* (see clause 5.1.3): + + - 3> consider this Random Access Response reception successful. + +- 2> if the Random Access Response reception is considered successful: + + - 3> if the Random Access Response includes a MAC subPDU with RAPID only: + + - 4> consider this Random Access procedure successfully completed; + - 4> indicate the reception of an acknowledgement for SI request to upper layers. + + - 3> else: + + - 4> apply the following actions for the Serving Cell where the Random Access Preamble was transmitted: + + - 5> process the received Timing Advance Command (see clause 5.2); + - 5> indicate the *preambleReceivedTargetPower* and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. $(PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) \times PREAMBLE\_POWER\_RAMPING\_STEP$ ); + - 5> if the Random Access procedure for an SCell is performed on uplink carrier where *pusch-Config* is not configured: + + - 6> ignore the received UL grant. + + - 5> else: + + - 6> process the received UL grant value and indicate it to the lower layers. + + - 4> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble(s): + + - 5> consider the Random Access procedure successfully completed. + + - 4> else: + + - 5> set the *TEMPORARY\_C-RNTI* to the value received in the Random Access Response; + - 5> if this is the first successfully received Random Access Response within this Random Access procedure: + + - 6> if the transmission is not being made for the CCCH logical channel: + + - 7> indicate to the Multiplexing and assembly entity to include a C-RNTI MAC CE in the subsequent uplink transmission. + + - 6> if the Random Access procedure was initiated for SpCell beam failure recovery and *spCell-BFR-CBRA* with value *true* is configured: + + - 7> if there is at least one Serving Cell of this MAC entity configured with two BFD-RS sets: + + - 8> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission. + + - 7> else: + + - 8> indicate to the Multiplexing and assembly entity to include a BFR MAC CE or a Truncated BFR MAC CE in the subsequent uplink transmission. + + - 6> else if the Random Access procedure was initiated for beam failure recovery of both BFD-RS sets of SpCell: + +7> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission. + +6> obtain the MAC PDU to transmit from the Multiplexing and assembly entity and store it in the Msg3 buffer. + +NOTE 1: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the same group of contention-based Random Access Preambles has a different size than the first uplink grant allocated during that Random Access procedure, the UE behavior is not defined. + +1> if *ra-ResponseWindow* configured in *BeamFailureRecoveryConfig* expires and if a PDCCH transmission on the search space indicated by *recoverySearchSpaceId* addressed to the C-RNTI has not been received on the Serving Cell where the preamble was transmitted; or + +1> if *ra-ResponseWindow* configured in *RACH-ConfigCommon* expires, and if the Random Access Response containing Random Access Preamble identifiers that matches the transmitted *PREAMBLE\_INDEX* has not been received: + +2> consider the Random Access Response reception not successful; + +2> increment *PREAMBLE\_TRANSMISSION\_COUNTER* by 1; + +2> if *PREAMBLE\_TRANSMISSION\_COUNTER* = *preambleTransMax* + 1: + +3> if the Random Access Preamble is transmitted on the SpCell: + +4> indicate a Random Access problem to upper layers; + +4> if this Random Access procedure was triggered for SI request: + +5> consider the Random Access procedure unsuccessfully completed. + +3> else if the Random Access Preamble is transmitted on an SCell: + +4> consider the Random Access procedure unsuccessfully completed. + +2> if the Random Access procedure is not completed: + +3> if the Random Access Preamble is transmitted with repetitions and neither contention-free Random Access Resources nor Random Access resources for SI request have been provided for this Random Access procedure: + +4> if *PREAMBLE\_TRANSMISSION\_COUNTER* = [*preambleTransMax-Msg1-Repetition*] + 1; or + +4> if *PREAMBLE\_TRANSMISSION\_COUNTER* = 2 × [*preambleTransMax-Msg1-Repetition*] + 1: + +5> if set of Random Access resources configured with the same *prach-ConfigurationIndex* and associated with a higher Msg1 repetition number with the same feature or feature combination as the current set of Random Access resources is available: + +6> select the set of Random Access resources associated with the next higher Msg1 repetition number with the same feature or feature combination for this Random Access procedure; + +6> initialize *startPreambleForThisPartition*, *numberOfPreamblesPerSSB-ForThisPartition*, *ssb-SharedRO-MaskIndex* and *numberOfRA-PreamblesGroupA* parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources. + +3> select a random backoff time according to a uniform distribution between 0 and the *PREAMBLE\_BACKOFF*; + +3> if the criteria (as defined in clause 5.1.2) to select contention-free Random Access Resources is met during the backoff time: + +4> perform the Random Access Resource selection procedure (see clause 5.1.2). + +- 3> else if the Random Access procedure for an SCell is performed on uplink carrier where *pusch-Config* is not configured: + - 4> delay the subsequent Random Access transmission until the Random Access Procedure is triggered by a PDCCH order with the same *ra-PreambleIndex*, *ra-ssb-OccasionMaskIndex*, and UL/SUL indicator TS 38.212 [9]. +- 3> else: + - 4> perform the Random Access Resource selection procedure (see clause 5.1.2) after the backoff time. + +The MAC entity may stop *ra-ResponseWindow* (and hence monitoring for Random Access Response(s)) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted *PREAMBLE\_INDEX*. + +HARQ operation is not applicable to the Random Access Response reception. + +NOTE 2: For the case that RAR PDSCH bandwidth is larger than the bandwidth the eRedCap UE can receive or process per slot, and the UL grant in RAR indicates that the time is not enough for Msg3 transmission, as specified in TS 38.213 [6], it is up to UE implementation, e.g. either to consider the Random Access Response reception not successful, or transmit Msg3. + +#### 5.1.4a MSGB reception and contention resolution for 2-step RA type + +Once the MSGA preamble is transmitted, regardless of the possible occurrence of a measurement gap, the MAC entity shall: + +- 1> start the *msgB-ResponseWindow* at the PDCCH occasion as specified in TS 38.213 [6], clause 8.2A; +- 1> monitor the PDCCH of the SpCell for a Random Access Response identified by MSGB-RNTI while the *msgB-ResponseWindow* is running; +- 1> if C-RNTI MAC CE was included in the MSGA: + - 2> monitor the PDCCH of the SpCell for Random Access Response identified by the C-RNTI while the *msgB-ResponseWindow* is running. +- 1> if notification of a reception of a PDCCH transmission of the SpCell is received from lower layers: + - 2> if the C-RNTI MAC CE was included in MSGA: + - 3> if the Random Access procedure was initiated for SpCell beam failure recovery or for beam failure recovery of both BFD-RS sets of SpCell (as specified in clause 5.17) and the PDCCH transmission is addressed to the C-RNTI: + - 4> consider this Random Access Response reception successful; + - 4> stop the *msgB-ResponseWindow*; + - 4> consider this Random Access procedure successfully completed. + - 3> else if the *timeAlignmentTimer* associated with at least one PTAG is running; or + - 3> if CG-SDT procedure is ongoing and *cgr-SDT-TimeAlignmentTimer* is running: + - 4> if the PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new transmission: + - 5> consider this Random Access Response reception successful; + - 5> stop the *msgB-ResponseWindow*; + - 5> consider this Random Access procedure successfully completed. + - 3> else: + +- 4> if a downlink assignment has been received on the PDCCH for the C-RNTI and the received TB is successfully decoded: + - 5> if the MAC PDU contains the Absolute Timing Advance Command MAC CE: + - 6> process the received Timing Advance Command (see clause 5.2); + - 6> consider this Random Access Response reception successful; + - 6> stop the *msgB-ResponseWindow*; + - 6> consider this Random Access procedure successfully completed and finish the disassembly and demultiplexing of the MAC PDU. + - 2> if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the MSGB-RNTI and the received TB is successfully decoded: + - 3> if the MSGB contains a MAC subPDU with Backoff Indicator: + - 4> set the *PREAMBLE\_BACKOFF* to value of the BI field of the MAC subPDU using Table 7.2-1, multiplied with *SCALING\_FACTOR\_BI*. + - 3> else: + - 4> set the *PREAMBLE\_BACKOFF* to 0 ms. + - 3> if the MSGB contains a fallbackRAR MAC subPDU; and + - 3> if the Random Access Preamble identifier in the MAC subPDU matches the transmitted *PREAMBLE\_INDEX* (see clause 5.1.3a): + - 4> consider this Random Access Response reception successful; + - 4> apply the following actions for the SpCell: + - 5> process the received Timing Advance Command (see clause 5.2); + - 5> indicate the *msgA-PreambleReceivedTargetPower* and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. $(PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) \times PREAMBLE\_POWER\_RAMPING\_STEP$ ); + - 5> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble(s): + - 6> consider the Random Access procedure successfully completed; + - 6> process the received UL grant value and indicate it to the lower layers. + - 5> else: + - 6> set the *TEMPORARY\_C-RNTI* to the value received in the Random Access Response; + - 6> if the Msg3 buffer is empty: + - 7> obtain the MAC PDU to transmit from the MSGA buffer and store it in the Msg3 buffer; + - 6> process the received UL grant value and indicate it to the lower layers and proceed with Msg3 transmission. +- NOTE: If within a 2-step RA type procedure, an uplink grant provided in the fallback RAR has a different size than the MSGA payload, the UE behavior is not defined. +- 3> else if the MSGB contains a successRAR MAC subPDU; and + - 3> if the CCCH SDU was included in the MSGA and the UE Contention Resolution Identity in the MAC subPDU matches the CCCH SDU: + - 4> stop *msgB-ResponseWindow*; + +- 4> if this Random Access procedure was initiated for SI request: + - 5> indicate the reception of an acknowledgement for SI request to upper layers. + - 4> else: + - 5> set the C-RNTI to the value received in the *successRAR*; + - 5> apply the following actions for the SpCell: + - 6> process the received Timing Advance Command (see clause 5.2); + - 6> indicate the *msgA-PreambleReceivedTargetPower* and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. $(PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) \times PREAMBLE\_POWER\_RAMPING\_STEP$ ). + - 4> deliver the *TPC*, *PUCCH resource Indicator*, *ChannelAccess-CPext* (if indicated), and *HARQ feedback Timing Indicator* received in *successRAR* to lower layers. + - 4> consider this Random Access Response reception successful; + - 4> consider this Random Access procedure successfully completed; + - 4> finish the disassembly and demultiplexing of the MAC PDU. +- 1> if *msgB-ResponseWindow* expires, and the Random Access Response Reception has not been considered as successful based on descriptions above: +- 2> increment *PREAMBLE\_TRANSMISSION\_COUNTER* by 1; + - 2> if $PREAMBLE\_TRANSMISSION\_COUNTER = preambleTransMax + 1$ : + - 3> indicate a Random Access problem to upper layers; + - 3> if this Random Access procedure was triggered for SI request: + - 4> consider this Random Access procedure unsuccessfully completed. + - 2> if the Random Access procedure is not completed: + - 3> if *msgA-TransMax* is applied (see clause 5.1.1a) and $PREAMBLE\_TRANSMISSION\_COUNTER = msgA-TransMax + 1$ : + - 4> set the *RA\_TYPE* to *4-stepRA*; + - 4> perform initialization of variables specific to Random Access type as specified in clause 5.1.1a; + - 4> if the Msg3 buffer is empty: + - 5> obtain the MAC PDU to transmit from the MSGA buffer and store it in the Msg3 buffer; + - 4> flush HARQ buffer used for the transmission of MAC PDU in the MSGA buffer; + - 4> discard explicitly signalled contention-free 2-step RA type Random Access Resources, if any; + - 4> perform the Random Access Resource selection procedure as specified in clause 5.1.2. + - 3> else: + - 4> select a random backoff time according to a uniform distribution between 0 and the *PREAMBLE\_BACKOFF*; + - 4> if the criteria (as defined in clause 5.1.2a) to select contention-free Random Access Resources is met during the backoff time: + - 5> perform the Random Access Resource selection procedure for 2-step RA type Random Access (see clause 5.1.2a). + +- 4> else: + - 5> perform the Random Access Resource selection procedure for 2-step RA type Random Access (see clause 5.1.2a) after the backoff time. + +Upon receiving a fallbackRAR, the MAC entity may stop *msgB-ResponseWindow* once the Random Access Response reception is considered as successful. + +### 5.1.5 Contention Resolution + +Once Msg3 is transmitted the MAC entity shall: + +- 1> if the Msg3 transmission (i.e. initial transmission or HARQ retransmission) is scheduled with PUSCH repetition Type A: + - 2> if Msg3 is transmitted on a non-terrestrial network: + - 3> start or restart the *ra-ContentionResolutionTimer* in the first symbol after the end of all repetitions of the Msg3 transmission plus the UE-gNB RTT. + - 2> else: + - 3> start or restart the *ra-ContentionResolutionTimer* in the first symbol after the end of all repetitions of the Msg3 transmission. +- 1> else if Msg3 transmission (i.e. initial transmission or HARQ retransmission) is transmitted on a non-terrestrial network: + - 2> start or restart the *ra-ContentionResolutionTimer* in the first symbol after the end of the Msg3 transmission plus the UE-gNB RTT. +- 1> else: + - 2> start or restart the *ra-ContentionResolutionTimer* in the first symbol after the end of the Msg3 transmission. +- 1> monitor the PDCCH while the *ra-ContentionResolutionTimer* is running regardless of the possible occurrence of a measurement gap; +- 1> if notification of a reception of a PDCCH transmission of the SpCell is received from lower layers: + - 2> if the C-RNTI MAC CE was included in Msg3: + - 3> if the Random Access procedure was initiated for SpCell beam failure recovery or for beam failure recovery of both BFD-RS sets of SpCell (as specified in clause 5.17) and the PDCCH transmission is addressed to the C-RNTI; or + - 3> if the Random Access procedure was initiated by a PDCCH order and the PDCCH transmission is addressed to the C-RNTI; or + - 3> if the Random Access procedure was initiated by the MAC sublayer itself or by the RRC sublayer and the PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new transmission: + - 4> consider this Contention Resolution successful; + - 4> stop *ra-ContentionResolutionTimer*; + - 4> discard the *TEMPORARY\_C-RNTI*; + - 4> consider this Random Access procedure successfully completed. + - 2> else if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its *TEMPORARY\_C-RNTI*: + - 3> if the MAC PDU is successfully decoded: + - 4> stop *ra-ContentionResolutionTimer*; + +- 4> if the MAC PDU contains a UE Contention Resolution Identity MAC CE; and +- 4> if the UE Contention Resolution Identity in the MAC CE matches the CCCH SDU transmitted in Msg3: + - 5> consider this Contention Resolution successful and finish the disassembly and demultiplexing of the MAC PDU; + - 5> if this Random Access procedure was initiated for SI request: + - 6> indicate the reception of an acknowledgement for SI request to upper layers. + - 5> else: + - 6> set the C-RNTI to the value of the *TEMPORARY\_C-RNTI*; + - 5> discard the *TEMPORARY\_C-RNTI*; + - 5> consider this Random Access procedure successfully completed. +- 4> else: + - 5> discard the *TEMPORARY\_C-RNTI*; + - 5> consider this Contention Resolution not successful and discard the successfully decoded MAC PDU. +- 3> else, for eRedCap UE, if lower layer detects that PDSCH transmission scheduled by PDCCH has a larger bandwidth than UE can receive or process per slot: + - 4> stop *ra-ContentionResolutionTimer*; + - 4> discard the *TEMPORARY\_C-RNTI*; + - 4> consider this Contention Resolution not successful. +- 1> if *ra-ContentionResolutionTimer* expires: + - 2> if Msg3 transmission was transmitted on a non-terrestrial network: + - 3> if no PDCCH addressed to TC-RNTI indicating uplink grant for a Msg3 retransmission is received after the start of the *ra-ContentionResolutionTimer*: + - 4> discard the *TEMPORARY\_C-RNTI*; + - 4> consider the Contention Resolution not successful. + - 2> else: + - 3> discard the *TEMPORARY\_C-RNTI*; + - 3> consider the Contention Resolution not successful. +- 1> if the Contention Resolution is considered not successful: + - 2> flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer; + - 2> increment *PREAMBLE\_TRANSMISSION\_COUNTER* by 1; + - 2> if *PREAMBLE\_TRANSMISSION\_COUNTER* = *preambleTransMax* + 1: + - 3> indicate a Random Access problem to upper layers. + - 3> if this Random Access procedure was triggered for SI request: + - 4> consider the Random Access procedure unsuccessfully completed. + - 2> if the Random Access procedure is not completed: + +- 3> if the *RA\_TYPE* is set to 4-stepRA: + - 4> if the Random Access Preamble is transmitted with repetitions and contention-free Random Access Resources have not been provided for this Random Access procedure: + - 5> if *PREAMBLE\_TRANSMISSION\_COUNTER* = [*preambleTransMax-Msg1-Repetition*] + 1; or + - 5> if *PREAMBLE\_TRANSMISSION\_COUNTER* = 2 × [*preambleTransMax-Msg1-Repetition*] + 1: + - 6> if set of Random Access resources configured with the same *prach-ConfigurationIndex* and associated with a higher Msg1 repetition number with the same feature or feature combination as the current set of Random Access resources is available: + - 7> select the set of Random Access resources associated with the next higher Msg1 repetition number with the same feature or feature combination for this Random Access procedure; + - 7> initialize *startPreambleForThisPartition*, *numberOfPreamblesPerSSB-ForThisPartition*, *ssb-SharedRO-MaskIndex* and *numberOfRA-PreamblesGroupA* parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources. + - 4> select a random backoff time according to a uniform distribution between 0 and the *PREAMBLE\_BACKOFF*; + - 4> if the criteria (as defined in clause 5.1.2) to select contention-free Random Access Resources is met during the backoff time: + - 5> perform the Random Access Resource selection procedure (see clause 5.1.2); + - 4> else: + - 5> perform the Random Access Resource selection procedure (see clause 5.1.2) after the backoff time. +- 3> else (i.e. the *RA\_TYPE* is set to 2-stepRA): + - 4> if *msgA-TransMax* is applied (see clause 5.1.1a) and *PREAMBLE\_TRANSMISSION\_COUNTER* = *msgA-TransMax* + 1: + - 5> set the *RA\_TYPE* to 4-stepRA; + - 5> perform initialization of variables specific to Random Access type as specified in clause 5.1.1a; + - 5> flush HARQ buffer used for the transmission of MAC PDU in the MSGA buffer; + - 5> discard explicitly signalled contention-free 2-step RA type Random Access Resources, if any; + - 5> perform the Random Access Resource selection as specified in clause 5.1.2. + - 4> else: + - 5> select a random backoff time according to a uniform distribution between 0 and the *PREAMBLE\_BACKOFF*; + - 5> if the criteria (as defined in clause 5.1.2a) to select contention-free Random Access Resources is met during the backoff time: + - 6> perform the Random Access Resource selection procedure for 2-step RA type as specified in clause 5.1.2a. + - 5> else: + - 6> perform the Random Access Resource selection for 2-step RA type procedure (see clause 5.1.2a) after the backoff time. + +### 5.1.6 Completion of the Random Access procedure + +Upon completion of the Random Access procedure, the MAC entity shall: + +- 1> discard any explicitly signalled contention-free Random Access Resources for 2-step RA type and 4-step RA type except the 4-step RA type contention-free Random Access Resources for beam failure recovery request, if any; +- 1> flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer and the MSGA buffer. + +Upon successful completion of the Random Access procedure initiated for DAPS handover, the target MAC entity shall: + +- 1> indicate the successful completion of the Random Access procedure to the upper layers. + +## 5.2 Maintenance of Uplink Time Alignment + +RRC configures the following parameters for the maintenance of UL time alignment: + +- *timeAlignmentTimer* (per TAG) which controls how long the MAC entity considers the Serving Cells to the associated TAG to be uplink time aligned for the TAG; +- *inactivePosSRS-TimeAlignmentTimer* which controls how long the MAC entity considers the Positioning SRS transmission in RRC\_INACTIVE in clause 5.26 to be uplink time aligned; +- *cg-SDT-TimeAlignmentTimer* which controls how long the MAC entity considers the uplink transmission for CG-SDT to be uplink time aligned; +- *srs-ValidityAreaTimeAlignmentTimer* which controls how long the MAC entity considers Positioning SRS transmission in RRC\_INACTIVE in clause 5.26 to be uplink time aligned when SRS positioning validity area is configured. + +The MAC entity shall: + +- 1> when a Timing Advance Command MAC CE is received, and if an $N_{TA}$ (as defined in TS 38.211 [8]) has been maintained with the indicated TAG: + - 2> apply the Timing Advance Command for the indicated TAG; + - 2> if there is ongoing Positioning SRS Transmission in RRC\_INACTIVE as in clause 5.26: + - 3> if SRS positioning validity area is configured: + - 4> start or restart the *srs-ValidityAreaTimeAlignmentTimer* associated with the indicated TAG. + - 3> else: + - 4> start or restart the *inactivePosSRS-TimeAlignmentTimer* associated with the indicated TAG. + - 2> if CG-SDT procedure triggered as in clause 5.27 is ongoing: + - 3> start or restart the *cg-SDT-TimeAlignmentTimer* associated with the indicated TAG. + - 2> else: + - 3> start or restart the *timeAlignmentTimer* associated with the indicated TAG. +- 1> when a Timing Advance Command is received in a Random Access Response message for a Serving Cell configured with two TAGs or in a MSGB for an SpCell configured with two TAGs: + - 2> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble: + - 3> apply the Timing Advance Command for the TAG indicated in the received Random Access Response message or MSGB; + +- 3> start or restart the *timeAlignmentTimer* associated with TAG indicated in the received Random Access Response message or MSGB. +- 2> else if the *timeAlignmentTimer* associated with the TAG indicated in the received Random Access Response message or MSGB is not running: + - 3> apply the Timing Advance Command for this TAG; + - 3> start the *timeAlignmentTimer* associated with this TAG; + - 3> when the Contention Resolution is considered not successful as described in clause 5.1.5: + - 4> stop the *timeAlignmentTimer* associated with this TAG. +- 2> else: + - 3> ignore the received Timing Advance Command. +- 1> when a Timing Advance Command is received in a Random Access Response message for a Serving Cell not configured with two TAGs or in a MSGB for an SpCell not configured with two TAGs: + - 2> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble: + - 3> apply the Timing Advance Command for this TAG; + - 3> start or restart the *timeAlignmentTimer* associated with this TAG. + - 2> else if the *timeAlignmentTimer* associated with this TAG is not running: + - 3> apply the Timing Advance Command for this TAG; + - 3> start the *timeAlignmentTimer* associated with this TAG; + - 3> when the Contention Resolution is considered not successful as described in clause 5.1.5; or + - 3> when the Contention Resolution is considered successful for SI request as described in clause 5.1.5, after transmitting HARQ feedback for MAC PDU including UE Contention Resolution Identity MAC CE: + - 4> stop *timeAlignmentTimer* associated with this TAG. + - 3> when the Contention Resolution is considered not successful as described in clause 5.1.5: + - 4> if CG-SDT procedure triggered as in clause 5.27 is ongoing: + - 5> set the $N_{TA}$ value to the value before applying the received Timing Advance Command as in TS 38.211 [8]. + - 3> when the Contention Resolution is considered successful for Random Access procedure while the CG-SDT procedure is ongoing: + - 4> stop *timeAlignmentTimer* associated with this TAG; + - 4> start or restart the *cgsdt-TimeAlignmentTimer* associated with this TAG. + - 3> when the Contention Resolution is considered successful for Random Access procedure while SRS transmission in RRC\_INACTIVE is ongoing: + - 4> if SRS positioning validity area is configured: + - 5> start or restart the *srs-ValidityAreaTimeAlignmentTimer* associated with the indicated TAG. + - 4> else: + - 5> start or restart the *inactivePosSRS-TimeAlignmentTimer* associated with this TAG. + +- 3> ignore the received Timing Advance Command. +- 1> when an Absolute Timing Advance Command is received in response to a MSGA transmission including C-RNTI MAC CE, as specified in clause 5.1.4a, for an SpCell configured with two TAGs: + - 2> apply the Timing Advance Command for the PTAG indicated in the Absolute Timing Advance Command MAC CE; + - 2> start or restart the *timeAlignmentTimer* associated with this PTAG. +- 1> when an Absolute Timing Advance Command is received in response to a MSGA transmission including C-RNTI MAC CE, as specified in clause 5.1.4a, for an SpCell not configured with two TAGs: + - 2> apply the Timing Advance Command for PTAG; + - 2> if there is ongoing Positioning SRS Transmission in RRC\_INACTIVE as in clause 5.26: + - 3> if SRS positioning validity area is configured: + - 4> start or restart the *srs-ValidityAreaTimeAlignmentTimer* associated with the indicated TAG. + - 3> else: + - 4> start or restart the *inactivePosSRS-TimeAlignmentTimer* associated with the indicated TAG. + - 2> if CG-SDT procedure is ongoing: + - 3> start or restart the *cg-SDT-TimeAlignmentTimer* associated with PTAG. + - 2> else: + - 3> start or restart the *timeAlignmentTimer* associated with PTAG. +- 1> when the MAC entity is configured with *rach-LessHO*: + - 2> set the NTA value (as defined in TS 38.211 [8]) to the value indicated by *targetNTA* in *rach-LessHO* for PTAG; + - 2> start the *timeAlignmentTimer* associated with PTAG. +- 1> when the indication is received from upper layer for stopping the *inactivePosSRS-TimeAlignmentTimer*: + - 2> stop the *inactivePosSRS-TimeAlignmentTimer*. +- 1> when the indication is received from upper layer for starting the *inactivePosSRS-TimeAlignmentTimer*: + - 2> start or restart the *inactivePosSRS-TimeAlignmentTimer*. +- 1> when instruction from the upper layer has been received for starting the *cg-SDT-TimeAlignmentTimer*: + - 2> start the *cg-SDT-TimeAlignmentTimer*. +- 1> when instruction from the upper layer has been received for stopping the *cg-SDT-TimeAlignmentTimer*: + - 2> consider the *cg-SDT-TimeAlignmentTimer* as expired. +- 1> when the indication is received from upper layer for starting the *srs-ValidityArea-TimerAlignmentTimer*: + - 2> start or restart the *srs-ValidityArea-TimerAlignmentTimer*. +- 1> when the indication is received from upper layer for stopping the *srs-ValidityArea-TimerAlignmentTimer*: + - 2> stop the *srs-ValidityArea-TimerAlignmentTimer*. +- 1> when instruction from the upper layer has been received for starting the *TimeAlignmentTimer* associated with PTAG: + - 2> start the *TimeAlignmentTimer* associated with PTAG. + +- 1> when an LTM Cell Switch Command MAC CE including a Timing Advance Command is received: + - 2> apply the Timing Advance Command for the PTAG; + - 2> start or restart the *timeAlignmentTimer* associated with the PTAG. +- 1> when an LTM Cell Switch Command MAC CE is received and the UE has successfully measured the Timing Advance as in clause 5.18.35: + - 2> apply the measured Timing Advance for the PTAG; + - 2> start or restart the *timeAlignmentTimer* associated with the PTAG. +- 1> when a *timeAlignmentTimer* expires: + - 2> if the *timeAlignmentTimer* is associated with a PTAG and the SpCell is not configured with two PTAGs; or + - 2> if the *timeAlignmentTimer* is associated with a PTAG, the SpCell is configured with two PTAGs, and the *timeAlignmentTimer* associated with the other PTAG is not running: + - 3> flush all HARQ buffers for all Serving Cells; + - 3> notify RRC to release PUCCH for all Serving Cells, if configured; + - 3> notify RRC to release SRS for all Serving Cells, if configured; + - 3> clear any configured downlink assignments and configured uplink grants; + - 3> clear any PUSCH resource for semi-persistent CSI reporting; + - 3> consider all running *timeAlignmentTimers* as expired; + - 3> maintain $N_{TA}$ (defined in TS 38.211 [8]) of all TAGs. + - 2> else if the *timeAlignmentTimer* is associated with a TAG for an SCell, then for all SCells configured with only this TAG; or + - 2> if the *timeAlignmentTimer* is associated with a TAG for an SCell, and if the SCell is configured with two TAGs and the *timeAlignmentTimer* associated with the other TAG is not running, then for all such SCells: + - 3> flush all HARQ buffers; + - 3> notify RRC to release PUCCH, if configured; + - 3> notify RRC to release SRS, if configured; + - 3> clear any configured downlink assignments and configured uplink grants; + - 3> clear any PUSCH resource for semi-persistent CSI reporting; + - 3> maintain $N_{TA}$ (defined in TS 38.211 [8]) of this TAG. + - 2> else if the *timeAlignmentTimer* is associated with a TAG for a Serving Cell configured with two TAGs, and if the *timeAlignmentTimer* associated with the other TAG is running, then for all such Serving Cells: + - 3> clear any configured downlink assignment, if the activated TCI state(s) for all PUCCH resources configured for the configured downlink assignment is associated with the TAG of the expired *timeAlignmentTimer*; + - 3> clear any configured uplink grant, if the activated TCI state(s) for the configured uplink grant is associated with the TAG of the expired *timeAlignmentTimer*; + - 3> clear any PUSCH resource for semi-persistent CSI reporting, if the activated TCI state(s) for the PUSCH resource is associated with the TAG of the expired *timeAlignmentTimer*; + - 3> maintain $N_{TA}$ (defined in TS 38.211 [8]) of this TAG. +- 1> when the *inactivePosSRS-TimeAlignmentTimer* expires: + +- 2> notify RRC to release Positioning SRS for RRC\_INACTIVE configuration(s). +- 1> when the *cg-SDT-TimeAlignmentTimer* expires: + - 2> clear any configured uplink grants; + - 2> if a PDCCH addressed to the MAC entity's C-RNTI after initial transmission for the CG-SDT with CCCH message has not been received: + - 3> consider ongoing CG-SDT procedure as terminated; + - 3> indicate the expiry of *cg-SDT-TimeAlignmentTimer* to the upper layer. + - 2> flush all HARQ buffers; + - 2> maintain $N_{TA}$ (defined in TS 38.211 [8]) of this TAG. + +When the MAC entity stops uplink transmissions for an SCell not configured with two TAGs due to the fact that the maximum uplink transmission timing difference between TAGs of the MAC entity or the maximum uplink transmission timing difference between TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the *timeAlignmentTimer* associated with the SCell as expired. + +When the MAC entity stops uplink transmissions associated to a STAG for an SCell configured with two TAGs due to the fact that the maximum uplink transmission timing difference between TAGs of the MAC entity or the maximum uplink transmission timing difference between TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the *timeAlignmentTimer* associated with the STAG as expired. + +The MAC entity shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble and MSGA transmission when the *timeAlignmentTimer(s)* associated with all TAG(s) to which this Serving Cell belongs is not running, CG-SDT procedure is not ongoing and SRS transmission in RRC\_INACTIVE as in clause 5.26 is not ongoing. Furthermore, when the *timeAlignmentTimer(s)* associated with all PTAG(s) is not running, CG-SDT procedure is not ongoing and SRS transmission in RRC\_INACTIVE as in clause 5.26 is not ongoing, the MAC entity shall not perform any uplink transmission on any Serving Cell except the Random Access Preamble and MSGA transmission on the SpCell. The MAC entity shall not perform any uplink transmission except the Random Access Preamble and MSGA transmission when the *cg-SDT-TimeAlignmentTimer* is not running during the ongoing CG-SDT procedure as triggered in clause 5.27 and the *inactivePosSRS-TimeAlignmentTimer* or *srs-ValidityAreaTimeAlignmentTimer* is not running. The MAC entity shall not perform any uplink transmission except the Random Access Preamble and MSGA transmission on a Serving Cell using TCI state(s) associated with a TAG for which the *timeAlignmentTimer* is not running. + +## 5.2a Maintenance of UL Synchronization + +The MAC entity shall for each Serving Cell: + +- 1> if an indication of uplink synchronization has been received from upper layers (see clauses 5.2.2.6 and 5.7.19 of TS 38.331 [5]): + - 2> if indication of uplink synchronization is received after indication of uplink synchronization loss due to satellite switch with re-synchronization (see clause 5.7.19 of TS 38.331 [5]): + - 3> set $N_{TA}$ value (as defined in TS 38.211 [8]) to zero for PTAG; + - 3> indicate to lower layers a Differential Koffset with value zero. + - 2> allow uplink transmission on the Serving Cell. +- 1> if an indication of uplink synchronization loss or uplink synchronization loss due to satellite switch with re-synchronization is received from upper layers (see clause 5.2.2.6 and 5.7.19 of TS 38.331 [5]): + - 2> flush all HARQ buffers; + - 2> not perform any uplink transmission on the Serving Cell. + +NOTE: The MAC entity suspends all UL operations (e.g. stop RACH, SR, and UL HARQ operation) after receiving the indication of an uplink synchronization loss and resumes the operation when receiving an indication of uplink synchronization. + +## 5.3 DL-SCH data transfer + +### 5.3.1 DL Assignment reception + +Downlink assignments received on the PDCCH both indicate that there is a transmission on a DL-SCH for a particular MAC entity and provide the relevant HARQ information. + +When the MAC entity has a C-RNTI, Temporary C-RNTI, CS-RNTI, G-RNTI or G-CS-RNTI, the MAC entity shall for each PDCCH occasion during which it monitors PDCCH and for each Serving Cell: + +- 1> if a downlink assignment for this PDCCH occasion and this Serving Cell has been received on the PDCCH for the MAC entity's C-RNTI, or Temporary C-RNTI, or G-RNTI configured for multicast MTCH: + - 2> if this is the first downlink assignment for this Temporary C-RNTI: + - 3> consider the NDI to have been toggled. + - 2> if the downlink assignment is for the MAC entity's C-RNTI, and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the MAC entity's CS-RNTI or G-CS-RNTI, or a configured downlink assignment for unicast or MBS multicast; or + - 2> if the downlink assignment is for the MAC entity's G-RNTI configured for multicast MTCH, and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the MAC entity's CS-RNTI or G-CS-RNTI, or other G-RNTI, or C-RNTI, or a configured downlink assignment for unicast or MBS multicast: + - 3> consider the NDI to have been toggled regardless of the value of the NDI. + - 2> stop the *cg-SDT-RetransmissionTimer*, if it is running, for the corresponding HARQ process for initial transmission with CCCH message; + - 2> stop the *cg-RACH-less-RetransmissionTimer*, if it is running, for the corresponding HARQ process for initial transmission of RACH-less handover; + - 2> stop the *cg-LTM-RetransmissionTimer*, if it is running, for the corresponding HARQ process for the first PUSCH transmission at LTM cell switch; + - 2> stop the *configuredGrantTimer*, if it is running, for the corresponding HARQ process for initial transmission with CCCH message; + - 2> if there is an ongoing RACH-less handover procedure; and + - 2> if the downlink assignment has been received on the PDCCH for the MAC entity's C-RNTI after the first PUSCH transmission to the Serving Cell; and + - 2> if the downlink assignment is for a new transmission: + - 3> indicate to upper layers the successful completion of RACH-less handover. + - 2> indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity. + - 2> if there is an ongoing RACH-less LTM cell switch; and + - 2> if the downlink assignment has been received on the PDCCH for the MAC entity's C-RNTI after the first PUSCH transmission to the Serving Cell; and + - 2> if the downlink assignment is for a new transmission: + +- 3> consider the LTM cell switch to be successfully completed and indicate it to upper layers. +- 1> else if a downlink assignment for this PDCCH occasion has been received for this Serving Cell on the PDCCH for the MAC entity's CS-RNTI or G-CS-RNTI: + - 2> if the NDI in the received HARQ information is 1: + - 3> consider the NDI for the corresponding HARQ process not to have been toggled; + - 3> indicate the presence of a downlink assignment for this Serving Cell and deliver the associated HARQ information to the HARQ entity. + - 2> if the NDI in the received HARQ information is 0: + - 3> if PDCCH contents indicate SPS deactivation: + - 4> clear the configured downlink assignment for this Serving Cell (if any); + - 4> if the *timeAlignmentTimer*, associated with the TAG containing the Serving Cell on which the HARQ feedback is to be transmitted, is running, and the Serving Cell is not configured with two TAGs; or + - 4> if the Serving Cell on which the HARQ feedback is to be transmitted is configured with two TAGs and if the *timeAlignmentTimer* of the TAG, associated with the TCI state(s) used for transmitting the HARQ feedback, is running: + - 5> indicate a positive acknowledgement for the SPS deactivation to the physical layer. + - 3> else if PDCCH content indicates SPS activation: + - 4> store the downlink assignment for this Serving Cell and the associated HARQ information as configured downlink assignment; + - 4> initialise or re-initialise the configured downlink assignment for this Serving Cell to start in the associated PDSCH duration and to recur according to rules in clause 5.8.1 or in clause 5.8.1a; + +For each Serving Cell and each configured downlink assignment, if configured and activated, the MAC entity shall: + +- 1> if the PDSCH duration of the configured downlink assignment does not overlap with the PDSCH duration of a downlink assignment received on the PDCCH for this Serving Cell: + - 2> instruct the physical layer to receive, in this PDSCH duration, transport block on the DL-SCH according to the configured downlink assignment and to deliver it to the HARQ entity; + - 2> set the HARQ Process ID to the HARQ Process ID associated with this PDSCH duration; + - 2> consider the NDI bit for the corresponding HARQ process to have been toggled; + - 2> indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity. + +For configured downlink assignments without *harq-ProcID-Offset*, the HARQ Process ID associated with the slot where the DL transmission starts is derived from the following equation: + +$$\text{HARQ Process ID} = \left[ \text{floor} \left( \text{CURRENT\_slot} \times 10 / (\text{numberOfSlotsPerFrame} \times \text{periodicity}) \right) \right] \bmod \text{nrofHARQ-Processes}$$ + +where $\text{CURRENT\_slot} = [(\text{SFN} \times \text{numberOfSlotsPerFrame}) + \text{slot number in the frame}]$ and $\text{numberOfSlotsPerFrame}$ refers to the number of consecutive slots per frame as specified in TS 38.211 [8]. + +For configured downlink assignments with *harq-ProcID-Offset*, the HARQ Process ID associated with the slot where the DL transmission starts is derived from the following equation: + +$$\text{HARQ Process ID} = \left[ \text{floor} \left( \text{CURRENT\_slot} \times 10 / (\text{numberOfSlotsPerFrame} \times \text{periodicity}) \right) \right] \bmod \text{nrofHARQ-Processes} + \text{harq-ProcID-Offset}$$ + +where $\text{CURRENT\_slot} = [(\text{SFN} \times \text{numberOfSlotsPerFrame}) + \text{slot number in the frame}]$ and $\text{numberOfSlotsPerFrame}$ refers to the number of consecutive slots per frame as specified in TS 38.211 [8]. + +NOTE 1: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to calculate the HARQ Process ID used for configured downlink assignments. + +NOTE 2: *CURRENT\_slot* refers to the slot index of the first transmission occasion of a bundle of configured downlink assignment. + +When the MAC entity needs to read BCCH, the MAC entity may, based on the scheduling information from RRC: + +- 1> if a downlink assignment for this PDCCH occasion has been received on the PDCCH for the SI-RNTI; + - 2> indicate a downlink assignment and redundancy version for the dedicated broadcast HARQ process to the HARQ entity. + +When the MAC entity needs to read MCCH, the MAC entity may, based on the scheduling information from RRC: + +- 1> if a downlink assignment for this PDCCH occasion has been received on the PDCCH for the MCCH-RNTI or Multicast MCCH-RNTI; + - 2> indicate a downlink assignment and redundancy version for the selected HARQ process to the HARQ entity. + +When the MAC entity needs to read broadcast MTCH, the MAC entity may, based on the scheduling information from RRC and DCI: + +- 1> if a downlink assignment for this PDCCH occasion has been received on the PDCCH for the G-RNTI configured for broadcast MTCH; + - 2> indicate the presence of a downlink assignment and deliver the associated HARQ information for the selected HARQ process to the HARQ entity. + +## 5.3.2 HARQ operation + +### 5.3.2.1 HARQ Entity + +The MAC entity includes a HARQ entity for each Serving Cell, which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see clause 5.3.2.2). + +The number of parallel DL HARQ processes per HARQ entity is specified in TS 38.214 [7]. The dedicated broadcast HARQ process is used for BCCH. + +The HARQ process supports one TB when the physical layer is not configured for downlink spatial multiplexing. The HARQ process supports one or two TBs when the physical layer is configured for downlink spatial multiplexing. + +When the MAC entity is configured with *pdsch-AggregationFactor* > 1, the parameter *pdsch-AggregationFactor* provides the number of transmissions of a TB within a bundle of the downlink assignment. Bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, *pdsch-AggregationFactor* – 1 HARQ retransmissions follow within a bundle. + +The MAC entity shall: + +- 1> if a downlink assignment has been indicated: + - 2> allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information. +- 1> if a downlink assignment has been indicated for the broadcast HARQ process: + - 2> allocate the received TB to the broadcast HARQ process. + +NOTE: It is up to UE implementation to allocate the received TB for multicast MCCH or broadcast MCCH or broadcast MTCH to one HARQ process. + +### 5.3.2.2 HARQ process + +When a transmission takes place for the HARQ process, one or two (in case of downlink spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity. + +For each received TB and associated HARQ information, the HARQ process shall: + +- 1> if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or +- 1> if the HARQ process is equal to the broadcast process, and this is the first received transmission for the TB according to the system information schedule indicated by RRC; or +- 1> if the HARQ process is associated with a transmission indicated with a MCCH-RNTI for MBS broadcast, and this is the first received transmission for the TB according to the broadcast MCCH schedule indicated by RRC; or +- 1> if the HARQ process is associated with a transmission indicated with a Multicast MCCH-RNTI for MBS multicast, and this is the first received transmission for the TB according to the multicast MCCH schedule indicated by RRC; or +- 1> if the HARQ process is associated with a transmission indicated with a G-RNTI for MBS broadcast, and this is the first received transmission for the TB according to the MTCH schedule indicated by RRC or according to the scheduling indicated by DCI as specified in TS 38.214 [7]; or +- 1> if this is the very first received transmission for this TB (i.e. there is no previous NDI for this TB): + - 2> consider this transmission to be a new transmission. +- 1> else: + - 2> consider this transmission to be a retransmission. + +The MAC entity then shall: + +- 1> if this is a new transmission: + - 2> attempt to decode the received data. +- 1> else if this is a retransmission: + - 2> if the data for this TB has not yet been successfully decoded: + - 3> instruct the physical layer to combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data. +- 1> if the data which the MAC entity attempted to decode was successfully decoded for this TB; or +- 1> if the data for this TB was successfully decoded before: + - 2> if the HARQ process is equal to the broadcast process: + - 3> deliver the decoded MAC PDU to upper layers. + - 2> else if this is the first successful decoding of the data for this TB: + - 3> deliver the decoded MAC PDU to the disassembly and demultiplexing entity. +- 1> else: + - 2> instruct the physical layer to replace the data in the soft buffer for this TB with the data which the MAC entity attempted to decode. +- 1> if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not yet successful (see clause 5.1.5); or + +- 1> if the HARQ process is associated with a transmission indicated with a MSGB-RNTI and the Random Access procedure is not yet successfully completed (see clause 5.1.4a); or +- 1> if the HARQ process is equal to the broadcast process; or +- 1> if the HARQ process is associated with a transmission indicated with a MCCH-RNTI or a G-RNTI for MBS broadcast; or +- 1> if the HARQ process is associated with a transmission indicated with a Multicast MCCH-RNTI for MBS multicast; or +- 1> if the HARQ process is associated with a transmission indicated with a G-RNTI or a G-CS-RNTI or a configured downlink assignment for MBS multicast and HARQ feedback is disabled for this G-RNTI or G-CS-RNTI or the corresponding G-CS-RNTI, as specified in clause 18 of TS 38.213 [6]; or +- 1> if the HARQ process is associated with a transmission indicated with a G-RNTI or a G-CS-RNTI or a configured downlink assignment for MBS multicast and NACK only HARQ feedback is used for this G-RNTI or G-CS-RNTI or the corresponding G-CS-RNTI and the data for this TB is successfully decoded and the transmission is not the first transmission of PDSCH where the configured downlink assignment was (re-)initialised; or +- 1> if the *timeAlignmentTimer*, associated with the TAG containing the Serving Cell on which the HARQ feedback is to be transmitted, is stopped or expired, and the Serving Cell is not configured with two TAGs, and if the *cg-SDT-TimeAlignmentTimer*, if configured, is not running; or +- 1> if the Serving Cell on which the HARQ feedback is to be transmitted is configured with two TAGs and if the *timeAlignmentTimer* of the TAG, associated with the TCI state(s) used for transmitting the HARQ feedback, is stopped or expired: + - 2> not instruct the physical layer to generate acknowledgement(s) of the data in this TB. +- 1> else if the HARQ process is configured with disabled HARQ feedback: + - 2> if *harq-FeedbackEnablingforSPSactive* is configured with value *true* and the transmission is the first transmission on the configured downlink assignment after activation of the configured downlink assignment: + - 3> instruct the physical layer to generate acknowledgement(s) of the data in this TB. + - 2> else: + - 3> not instruct the physical layer to generate acknowledgement(s) of the data in this TB. +- 1> else: + - 2> instruct the physical layer to generate acknowledgement(s) of the data in this TB. + +The MAC entity shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission. + +NOTE: If the MAC entity receives a retransmission with a TB size different from the last TB size signalled for this TB, the UE behavior is left up to UE implementation. + +### 5.3.3 Disassembly and demultiplexing + +The MAC entity shall disassemble and demultiplex a MAC PDU as defined in clauses 6.1.2 and 6.1.5a. + +When a MAC entity receives a MAC PDU for MAC entity's G-RNTI or G-CS-RNTI, or by the configured downlink assignment for MBS multicast containing an LCID or eLCID which is not configured, the MAC entity shall at least: + +- 1> discard the received subPDU. + +## 5.4 UL-SCH data transfer + +### 5.4.1 UL Grant reception + +Uplink grant is either received dynamically on the PDCCH, in a Random Access Response, configured semi-persistently by RRC or determined to be associated with the PUSCH resource of MSGA as specified in clause 5.1.2a. The MAC entity shall have an uplink grant to transmit on the UL-SCH. To perform the requested transmissions, the MAC layer receives HARQ information from lower layers. An uplink grant addressed to CS-RNTI with NDI = 0 is considered as a configured uplink grant. An uplink grant addressed to CS-RNTI with NDI = 1 is considered as a dynamic uplink grant. + +If the MAC entity has a C-RNTI, a Temporary C-RNTI, or CS-RNTI, the MAC entity shall for each PDCCH occasion and for each Serving Cell belonging to a TAG that has a running *timeAlignmentTimer* or a running *cg-SDT-TimeAlignmentTimer* and for each grant received for this PDCCH occasion: + +- 1> if an uplink grant for this Serving Cell has been received on the PDCCH for the MAC entity's C-RNTI or Temporary C-RNTI; or +- 1> if an uplink grant has been received in a Random Access Response: + - 2> if the uplink grant is for MAC entity's C-RNTI and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was either an uplink grant received for the MAC entity's CS-RNTI or a configured uplink grant: + - 3> consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI. + - 2> if the uplink grant is for MAC entity's C-RNTI, and the identified HARQ process is configured for a configured uplink grant: + - 3> start or restart the *configuredGrantTimer* for the corresponding HARQ process, if configured; + - 3> stop the *cg-RetransmissionTimer* for the corresponding HARQ process, if running. + - 2> stop the *cg-SDT-RetransmissionTimer* for the corresponding HARQ process, if running. + - 2> stop the *cg-LTM-RetransmissionTimer* for the corresponding HARQ process, if running. + - 2> stop the *cg-RACH-less-RetransmissionTimer* for the corresponding HARQ process, if running. + - 2> if there is an ongoing RACH-less handover procedure; and + - 2> if the uplink grant has been received on the PDCCH for the MAC entity's C-RNTI after the first PUSCH transmission to the Serving Cell; and + - 2> if the uplink grant is for a new transmission on the same HARQ process used for the first PUSCH transmission to the Serving Cell: + - 3> indicate to upper layers the successful completion of RACH-less handover. + - 2> deliver the uplink grant and the associated HARQ information to the HARQ entity; + - 2> if there is an ongoing RACH-less LTM cell switch; and + - 2> if the uplink grant has been received on the PDCCH for the MAC entity's C-RNTI after the first PUSCH transmission to the Serving Cell; and + - 2> if the uplink grant is for a new transmission on the same HARQ process used for the first PUSCH transmission to the Serving Cell: + - 3> consider the LTM cell switch to be successfully completed and indicate it to upper layers. +- 1> else if an uplink grant for this PDCCH occasion has been received for this Serving Cell on the PDCCH for the MAC entity's CS-RNTI: + +- 2> if the NDI in the received HARQ information is 1: + - 3> consider the NDI for the corresponding HARQ process not to have been toggled; + - 3> start or restart the *configuredGrantTimer* for the corresponding HARQ process, if configured; + - 3> stop the *cg-RetransmissionTimer* for the corresponding HARQ process, if running; + - 3> stop the *cg-SDT-RetransmissionTimer* for the corresponding HARQ process, if running; + - 3> stop the *cg-LTM-RetransmissionTimer* for the corresponding HARQ process, if running; + - 3> stop the *cg-RACH-less-RetransmissionTimer* for the corresponding HARQ process, if running; + - 3> deliver the uplink grant and the associated HARQ information to the HARQ entity; + - 3> if a logical channel associated with a DRB configured with *survivalTimeStateSupport* is multiplexed in the MAC PDU stored in the HARQ buffer for the corresponding HARQ process: + - 4> trigger activation of PDCP duplication for all configured RLC entities of the DRB. +- 2> else if the NDI in the received HARQ information is 0: + - 3> if PDCCH contents indicate configured grant Type 2 deactivation: + - 4> trigger configured uplink grant confirmation. + - 3> else if PDCCH contents indicate configured grant Type 2 activation: + - 4> trigger configured uplink grant confirmation; + - 4> store the uplink grant for this Serving Cell and the associated HARQ information as configured uplink grant; + - 4> initialise or re-initialise the configured uplink grant for this Serving Cell to start in the associated PUSCH duration and to recur according to rules in clause 5.8.2; + - 4> stop the *configuredGrantTimer* for the corresponding HARQ process, if running; + - 4> stop the *cg-RetransmissionTimer* for the corresponding HARQ process, if running. + +For each Serving Cell and each configured uplink grant, if configured and activated and available for use as specified in clause 5.8.2, the MAC entity shall: + +- 1> if the MAC entity is configured with *lch-basedPrioritization*, and the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or the PUSCH duration of a MSGA payload for this Serving Cell; or +- 1> if the MAC entity is not configured with *lch-basedPrioritization*, and the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a Random Access Response or the PUSCH duration of a MSGA payload for this Serving Cell: +- 2> set the HARQ Process ID to the HARQ Process ID associated with this PUSCH duration; +- 2> if, for the corresponding HARQ process, the *configuredGrantTimer* is not running and *cg-RetransmissionTimer* is not configured and *cg-SDT-RetransmissionTimer* is not configured, and *cg-LTM-RetransmissionTimer* is not configured, and *cg-RACH-less-RetransmissionTimer* is not configured (i.e. new transmission): + - 3> if there is an on-going CG-SDT procedure and PDCCH addressed to the MAC entity's C-RNTI has been received; or + - 3> if there is an on-going RACH-less LTM cell switch procedure and PDCCH addressed to the MAC entity's C-RNTI has been received; or + +- 3> if there is an on-going RACH-less handover procedure and PDCCH addressed to the MAC entity's C-RNTI has been received; or +- 3> if there is no on-going CG-SDT nor on-going RACH-less LTM cell switch nor on-going RACH-less handover procedure: + - 4> consider the NDI bit for the corresponding HARQ process to have been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. +- 2> else if the *cg-RetransmissionTimer* for the corresponding HARQ process is configured and not running, then for the corresponding HARQ process: + - 3> if the *configuredGrantTimer* is not running, and the HARQ process is not pending (i.e. new transmission): + - 4> consider the NDI bit to have been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. + - 3> else if the previous uplink grant delivered to the HARQ entity for the same HARQ process was a configured uplink grant (i.e. retransmission on configured grant): + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. +- 2> else if the *cg-SDT-RetransmissionTimer* is configured and not running for the corresponding HARQ process; + - 3> if the configured uplink grant is for the initial transmission for the CG-SDT with CCCH message (i.e., initial new transmission); or + - 3> if the *configuredGrantTimer* is not running or not configured, and PDCCH addressed to the MAC entity's C-RNTI has been received after the initial transmission of the CG-SDT with CCCH message (i.e., subsequent new transmission): + - 4> consider the NDI bit to have been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. + - 3> else if the previous uplink grant delivered to the HARQ entity for the same HARQ process was a configured uplink grant for initial transmission of CG-SDT with CCCH message or for its retransmission; and + - 3> if PDCCH addressed to the MAC entity's C-RNTI has not been received (i.e., retransmission for initial CG-SDT transmission): + - 4> consider the NDI bit to have not been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. +- 2> else if the *cg-LTM-RetransmissionTimer* is configured and not running for the corresponding HARQ process: + - 3> if the configured uplink grant is for the first PUSCH transmission at LTM cell switch (i.e., initial new transmission): + - 4> consider the NDI bit to have been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. + - 3> else if the previous uplink grant delivered to the HARQ entity for the same HARQ process was a configured uplink grant for first PUSCH transmission at LTM cell switch or for its retransmission; and + - 3> if PDCCH addressed to the MAC entity's C-RNTI has not been received on the same HARQ process used for the first PUSCH transmission to the Serving Cell (i.e., retransmission for initial transmission): + - 4> consider the NDI bit to have not been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. + +- 2> else if the *cg-RACH-less-RetransmissionTimer* is configured and not running for the corresponding HARQ process; + - 3> if the configured uplink grant is for the initial transmission of RACH-less handover (i.e., initial new transmission): + - 4> consider the NDI bit to have been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. + - 3> else if the previous uplink grant delivered to the HARQ entity for the same HARQ process was a configured uplink grant for initial transmission of RACH-less handover or for its retransmission; and + - 3> if PDCCH addressed to the MAC entity's C-RNTI has not been received (i.e., retransmission for initial transmission): + - 4> consider the NDI bit to have not been toggled; + - 4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity. + +For configured uplink grants that are not part of a multi-PUSCH configured grant and neither configured with *harq-ProcID-Offset2* nor with *cg-RetransmissionTimer*, the HARQ Process ID associated with the first symbol of a UL transmission is derived from the following equation: + +$$\text{HARQ Process ID} = [\text{floor}(\text{CURRENT\_symbol} / \text{periodicity})] \bmod \text{nrofHARQ-Processes}$$ + +For configured uplink grants that are not part of a multi-PUSCH configured grant and configured with *harq-ProcID-Offset2*, the HARQ Process ID associated with the first symbol of a UL transmission is derived from the following equation: + +$$\text{HARQ Process ID} = [\text{floor}(\text{CURRENT\_symbol} / \text{periodicity})] \bmod \text{nrofHARQ-Processes} + \text{harq-ProcID-Offset2}$$ + +For a multi-PUSCH configured grant (as specified in clause 5.8.2) configured with neither *harq-ProcID-Offset2* nor *cg-RetransmissionTimer*, the HARQ Process ID associated with the first symbol of a UL transmission is derived from the following equation: + +$$\text{HARQ Process ID} = [\text{nrofSlotsInCG-Period} \times \text{floor}(\text{CURRENT\_symbol} / \text{periodicity}) + \text{ID\_OFFSET}] \bmod \text{nrofHARQ-Processes}$$ + +For a multi-PUSCH configured grant configured with *harq-ProcID-Offset2*, the HARQ Process ID associated with the first symbol of a UL transmission is derived from the following equation: + +$$\text{HARQ Process ID} = [\text{nrofSlotsInCG-Period} \times \text{floor}(\text{CURRENT\_symbol} / \text{periodicity}) + \text{ID\_OFFSET}] \bmod \text{nrofHARQ-Processes} + \text{harq-ProcID-Offset2}$$ + +where $\text{CURRENT\_symbol}$ if *cg-SDT-PeriodicityExt* (as defined in TS 38.331 [5]) is not configured = $(\text{SFN} \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot} + \text{slot number in the frame} \times \text{numberOfSymbolsPerSlot} + \text{symbol number in the slot})$ , and $\text{numberOfSlotsPerFrame}$ and $\text{numberOfSymbolsPerSlot}$ refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively as specified in TS 38.211 [8]. For a multi-PUSCH configured grant, $\text{ID\_OFFSET}$ equals 0 for the first configured uplink grant within a *periodicity* of the configuration and $K$ for the $K^{\text{th}}$ ( $1 \leq K < \text{nrofSlotsInCG-Period}$ ) valid configured uplink grant after the first configured uplink grant within the same *periodicity*. A configured uplink grant in a multi-PUSCH configured grant is not considered valid if it satisfies the conditions specified in clause 6.1 in TS 38.214 [7]. + +Alternatively, if *cg-SDT-PeriodicityExt* (as defined in TS 38.331 [5]) is configured, $\text{CURRENT\_symbol} = ((\text{H-SFN} \times \text{numberOfSFNperH-SFN} + \text{SFN}) \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot} + \text{slot number in the frame} \times \text{numberOfSymbolsPerSlot} + \text{symbol number in the slot})$ , and $\text{numberOfSFNperH-SFN}$ , $\text{numberOfSlotsPerFrame}$ and $\text{numberOfSymbolsPerSlot}$ refer to the number of consecutive frames per H-SFN, the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively as specified in TS 38.211 [8]. + +For configured uplink grants configured with *cg-RetransmissionTimer*, the UE implementation selects an HARQ Process ID among the HARQ process IDs available for the configured grant configuration. If the MAC entity is configured with *intraCG-Prioritization*, for HARQ Process ID selection, the UE shall prioritize the HARQ Process ID with the highest priority, where the priority of HARQ process is determined by the highest priority among priorities of the logical channels that are multiplexed (i.e. the MAC PDU to transmit is already stored in the HARQ buffer) or have + +data available that can be multiplexed (i.e. the MAC PDU to transmit is not stored in the HARQ buffer) in the MAC PDU, according to the mapping restrictions as described in clause 5.4.3.1.2. If the MAC entity is configured with *intraCG-Prioritization*, for HARQ Process ID selection among initial transmission and retransmission with equal priority, the UE shall prioritize retransmissions before initial transmissions. The priority of a HARQ Process for which no data for logical channels is multiplexed or can be multiplexed in the MAC PDU is lower than the priority of a HARQ Process for which data for any logical channels is multiplexed or can be multiplexed in the MAC PDU. If the MAC entity is not configured with *intraCG-Prioritization*, for HARQ Process ID selection, the UE shall prioritize retransmissions before initial transmissions. The UE shall toggle the NDI in the CG-UCI for new transmissions and not toggle the NDI in the CG-UCI in retransmissions. + +NOTE 1: *CURRENT\_symbol* refers to the symbol index of the first transmission occasion of a bundle of configured uplink grant. + +NOTE 2: A HARQ process is configured for a configured uplink grant where neither *harq-ProcID-Offset* nor *harq-ProcID-Offset2* is configured, if the configured uplink grant is activated and the associated HARQ process ID is less than *nrofHARQ-Processes*. A HARQ process is configured for a configured uplink grant where *harq-ProcID-Offset2* is configured, if the configured uplink grant is activated and the associated HARQ process ID is greater than or equal to *harq-ProcID-Offset2* and less than sum of *harq-ProcID-Offset2* and *nrofHARQ-Processes* for the configured grant configuration. + +NOTE 3: If the MAC entity receives a grant in a Random Access Response (i.e. MAC RAR or fallbackRAR), or addressed to Temporary C-RNTI or determines a grant as specified in clause 5.1.2a for MSGA payload and if the MAC entity also receives an overlapping grant for its C-RNTI or CS-RNTI, requiring concurrent transmissions on the SpCell, the MAC entity may choose to continue with either the grant for its RA-RNTI/Temporary C-RNTI/MSGB-RNTI/the MSGA payload transmission or the grant for its C-RNTI or CS-RNTI. + +NOTE 4: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to calculate the HARQ Process ID used for configured uplink grants. + +NOTE 5: If *cg-RetransmissionTimer* is not configured, a HARQ process is not shared between different configured grant configurations in the same BWP. + +For the MAC entity configured with *lch-basedPrioritization*, priority of an uplink grant is determined by the highest priority among priorities of the logical channels that are multiplexed (i.e. the MAC PDU to transmit is already stored in the HARQ buffer) or have data available that can be multiplexed (i.e. the MAC PDU to transmit is not stored in the HARQ buffer) in the MAC PDU, according to the mapping restrictions as described in clause 5.4.3.1.2. The priority of an uplink grant for which no data for logical channels is multiplexed or can be multiplexed in the MAC PDU is lower than either the priority of an uplink grant for which data for any logical channels is multiplexed or can be multiplexed in the MAC PDU or the priority of the logical channel triggering an SR. + +For the MAC entity configured with *lch-basedPrioritization*, if the corresponding PUSCH transmission of a configured uplink grant is cancelled by CI-RNTI as specified in clause 11.2A of TS 38.213 [6] or cancelled by a high PHY-priority PUCCH transmission as specified in clause 9 of TS 38.213 [6], this configured uplink grant is considered as a de-prioritized uplink grant. If this de-prioritized uplink grant is configured with *autonomousTx*, the *configuredGrantTimer* for the corresponding HARQ process of this de-prioritized uplink grant shall be stopped if it is running. If this de-prioritized uplink grant is configured with *autonomousTx*, the *cg-RetransmissionTimer* for the corresponding HARQ process of this de-prioritized uplink grant shall be stopped if it is running. + +When the MAC entity is configured with *lch-basedPrioritization*, for each uplink grant delivered to the HARQ entity and whose associated PUSCH can be transmitted by lower layers, the MAC entity shall: + +- 1> if this uplink grant is received in a Random Access Response (i.e. in a MAC RAR or fallback RAR), or addressed to Temporary C-RNTI, or is determined as specified in clause 5.1.2a for the transmission of the MSGA payload: + - 2> consider this uplink grant as a prioritized uplink grant. +- 1> else if this uplink grant is addressed to CS-RNTI with NDI = 1 or C-RNTI: + - 2> if there is no overlapping PUSCH duration of a configured uplink grant which was not already de-prioritized, in the same BWP, whose priority is higher than the priority of the uplink grant; and + +- 2> if there is no overlapping PUCCH resource with an SR transmission which was not already de-prioritized and the simultaneous transmission of the SR and the uplink grant is not allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCH-Groups*, and the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant: + - 3> consider this uplink grant as a prioritized uplink grant; + - 3> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s); + - 3> consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s), except for the SR transmission(s) whose simultaneous transmission is allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCH-Groups*; + - 3> if the de-prioritized uplink grant(s) is a configured uplink grant configured with *autonomousTx* whose PUSCH has already started: + - 4> stop the *configuredGrantTimer* for the corresponding HARQ process of the de-prioritized uplink grant(s); + - 4> stop the *cg-RetransmissionTimer* for the corresponding HARQ process of the de-prioritized uplink grant(s). +- 1> else if this uplink grant is a configured uplink grant: + - 2> if there is no overlapping PUSCH duration of another configured uplink grant which was not already de-prioritized, in the same BWP, whose priority is higher than the priority of the uplink grant; and + - 2> if there is no overlapping PUSCH duration of an uplink grant addressed to CS-RNTI with NDI = 1 or C-RNTI which was not already de-prioritized, in the same BWP, whose priority is higher than or equal to the priority of the uplink grant; and + - 2> if there is no overlapping PUCCH resource with an SR transmission which was not already de-prioritized and the simultaneous transmission of the SR and the uplink grant is not allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCH-Groups*, and the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant: + - 3> consider this uplink grant as a prioritized uplink grant; + - 3> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s); + - 3> if the de-prioritized uplink grant(s) is a configured uplink grant configured with *autonomousTx* whose PUSCH has already started: + - 4> stop the *configuredGrantTimer* for the corresponding HARQ process of the de-prioritized uplink grant(s); + - 4> stop the *cg-RetransmissionTimer* for the corresponding HARQ process of the de-prioritized uplink grant(s). + - 3> consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s), except for the SR transmission(s) whose simultaneous transmission is allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCH-Groups*. + +NOTE 6: If the MAC entity is configured with *lch-basedPrioritization* and if there is overlapping PUSCH duration of at least two configured uplink grants whose priorities are equal, the prioritized uplink grant is determined by UE implementation. + +NOTE 7: If the MAC entity is not configured with *lch-basedPrioritization* and if there is overlapping PUSCH duration of at least two configured uplink grants, it is up to UE implementation to choose one of the configured uplink grants. + +NOTE 8: If the MAC entity is configured with *lch-basedPrioritization*, the MAC entity does not take UCI multiplexing according to the procedure specified in TS 38.213 [6] into account when determining whether the PUSCH duration of an uplink grant overlaps with the PUCCH resource for an SR transmission. + +## 5.4.2 HARQ operation + +### 5.4.2.1 HARQ Entity + +The MAC entity includes a HARQ entity for each Serving Cell with configured uplink (including the case when it is configured with *supplementaryUplink*), which maintains a number of parallel HARQ processes. + +The number of parallel UL HARQ processes per HARQ entity is specified in TS 38.214 [7]. + +Each HARQ process supports one TB. + +Each HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RA Response or for UL transmission for MSGA payload, HARQ process identifier 0 is used. + +NOTE: When a single DCI is used to schedule multiple PUSCH, the UE is allowed to map generated TB(s) internally to different HARQ processes in case of LBT failure(s), i.e. UE may transmit a new TB on any HARQ process in the grants that have the same TBS, the same RV and the NDIs indicate new transmission. + +The maximum number of transmissions of a TB within a bundle of the dynamic grant or configured grant or the uplink grant received in a MAC RAR is given by *REPETITION\_NUMBER* as follows: + +- For a dynamic grant, *REPETITION\_NUMBER* is set to a value provided by lower layers, as specified in clause 6.1.2.1 of TS 38.214 [7]; +- For a configured grant, *REPETITION\_NUMBER* is set to a value provided by lower layers, as specified in clause 6.1.2.3 of TS 38.214 [7]; +- For an uplink grant received in a MAC RAR, *REPETITION\_NUMBER* is set to a value provided by lower layers, as specified in clause 6.1.2.1 of TS 38.214 [7]. + +If *REPETITION\_NUMBER* > 1, after the first transmission within a bundle, at most *REPETITION\_NUMBER* – 1 HARQ retransmissions follow within the bundle. For both dynamic grant and configured uplink grant, and uplink grant received in a MAC RAR bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle, HARQ retransmissions are triggered without waiting for feedback from previous transmission according to *REPETITION\_NUMBER* for a dynamic grant or configured uplink grant or uplink grant received in a MAC RAR unless they are terminated as specified in clause 6.1 of TS 38.214 [7]. Each transmission within a bundle is a separate uplink grant delivered to the HARQ entity. + +For each transmission within a bundle of the dynamic grant or uplink grant received in a MAC RAR, the sequence of redundancy versions is determined according to clause 6.1.2.1 of TS 38.214 [7]. For each transmission within a bundle of the configured uplink grant, the sequence of redundancy versions is determined according to clause 6.1.2.3 of TS 38.214 [7]. + +For each uplink grant, the HARQ entity shall: + +- 1> identify the HARQ process associated with this grant, and for each identified HARQ process: + - 2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process; or + - 2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or + - 2> if the uplink grant was received in a Random Access Response (i.e. in a MAC RAR or a fallback RAR); or + - 2> if the uplink grant was determined as specified in clause 5.1.2a for the transmission of the MSGA payload; or + +- 2> if the uplink grant was received on PDCCH for the C-RNTI in *ra-ResponseWindow* and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery; or +- 2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission according to clause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU has been obtained for this bundle: + - 3> if there is a MAC PDU in the MSGA buffer and the uplink grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload was selected; or + - 3> if there is a MAC PDU in the MSGA buffer and the uplink grant was received in a *fallbackRAR* and this *fallbackRAR* successfully completed the Random Access procedure: + - 4> obtain the MAC PDU to transmit from the MSGA buffer. + - 3> else if there is a MAC PDU in the *Msg3* buffer and the uplink grant was received in a *fallbackRAR*: + - 4> obtain the MAC PDU to transmit from the *Msg3* buffer. + - 3> else if there is a MAC PDU in the *Msg3* buffer and the uplink grant was received in a MAC RAR; or + - 3> if there is a MAC PDU in the *Msg3* buffer and the uplink grant was received on PDCCH for the C-RNTI in *ra-ResponseWindow* and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery: + - 4> obtain the MAC PDU to transmit from the *Msg3* buffer. + - 4> if the uplink grant size does not match with size of the obtained MAC PDU; and + - 4> if the Random Access procedure was successfully completed upon receiving the uplink grant: + - 5> indicate to the Multiplexing and assembly entity to include MAC subPDU(s) carrying MAC SDU from the obtained MAC PDU in the subsequent uplink transmission; + - 5> obtain the MAC PDU to transmit from the Multiplexing and assembly entity. +- 3> else if this uplink grant is a configured grant configured with *autonomousTx*; and +- 3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and +- 3> if a MAC PDU had already been obtained for this HARQ process; and +- 3> if the uplink grant size matches with size of the obtained MAC PDU; and +- 3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed: + - 4> consider the MAC PDU has been obtained. +- 3> else if the MAC entity is not configured with *lch-basedPrioritization*; or +- 3> if this uplink grant is a prioritized uplink grant: + - 4> obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any; +- 3> if a MAC PDU to transmit has been obtained: + - 4> if the uplink grant is not a configured grant configured with *autonomousTx*; or + - 4> if the uplink grant is a prioritized uplink grant: + - 5> deliver the MAC PDU and the uplink grant and the HARQ information of the TB to the identified HARQ process; + - 5> instruct the identified HARQ process to trigger a new transmission; + - 5> if the uplink grant is a configured uplink grant: + - 6> start or restart the *configuredGrantTimer*, if configured, for the corresponding HARQ process when the transmission is performed if LBT failure indication is not received from lower layers; + +- 6> start or restart the *cg-RetransmissionTimer*, if configured, for the corresponding HARQ process when the transmission is performed if LBT failure indication is not received from lower layers. +- 6> if the configured uplink grant is for the initial transmission for CG-SDT with CCCH message: + - 7> start or restart the *cg-SDT-RetransmissionTimer*, if configured, for the corresponding HARQ process when the transmission is performed. +- 6> if the configured uplink grant is for the initial transmission at LTM cell switch: + - 7> start or restart the *cg-LTM-RetransmissionTimer*, if configured, for the corresponding HARQ process when the transmission is performed. +- 6> if the configured uplink grant is for the initial transmission of RACH-less handover: + - 7> start or restart the *cg-RACH-less-RetransmissionTimer*, if configured, for the corresponding HARQ process when the transmission is performed. +- 5> if the uplink grant is addressed to C-RNTI, and the identified HARQ process is configured for a configured uplink grant: + - 6> start or restart the *configuredGrantTimer*, if configured, for the corresponding HARQ process when the transmission is performed if LBT failure indication is not received from lower layers. +- 5> if *cg-RetransmissionTimer* is configured for the identified HARQ process; and +- 5> if the transmission is performed and LBT failure indication is received from lower layers: + - 6> consider the identified HARQ process as pending. +- 3> else: + - 4> flush the HARQ buffer of the identified HARQ process. +- 2> else (i.e. retransmission): + - 3> if the uplink grant received on PDCCH was addressed to CS-RNTI and if the HARQ buffer of the identified process is empty; or + - 3> if the uplink grant is part of a bundle and if no MAC PDU has been obtained for this bundle; or + - 3> if the uplink grant is part of a bundle of the configured uplink grant, and the PUSCH duration of the uplink grant overlaps with an uplink grant received in a Random Access Response (i.e. MAC RAR or fallbackRAR) or an uplink grant determined as specified in clause 5.1.2a for MSGA payload for this Serving Cell; or + - 3> if the MAC entity is not configured with *lch-basedPrioritization* and this uplink grant is part of a bundle of the configured uplink grant, and the PUSCH duration of the uplink grant overlaps with a PUSCH duration of another uplink grant received on the PDCCH; or + - 3> if the MAC entity is configured with *lch-basedPrioritization* and this uplink grant is not a prioritized uplink grant: + - 4> ignore the uplink grant. + - 3> else: + - 4> deliver the uplink grant and the HARQ information (redundancy version) of the TB to the identified HARQ process; + - 4> instruct the identified HARQ process to trigger a retransmission; + - 4> if the uplink grant is addressed to CS-RNTI; or + - 4> if the uplink grant is addressed to C-RNTI, and the identified HARQ process is configured for a configured uplink grant: + +- 5> start or restart the *configuredGrantTimer*, if configured, for the corresponding HARQ process when the transmission is performed if LBT failure indication is not received from lower layers. +- 4> if the uplink grant is a configured uplink grant: + - 5> if the identified HARQ process is pending: + - 6> start or restart the *configuredGrantTimer*, if configured, for the corresponding HARQ process when the transmission is performed if LBT failure indication is not received from lower layers; + - 5> start or restart the *cg-RetransmissionTimer*, if configured, for the corresponding HARQ process when the transmission is performed if LBT failure indication is not received from lower layers. + - 5> if the configured uplink grant is for the retransmission of the initial transmission of the CG-SDT with CCCH message: + - 6> start or restart the *cg-SDT-RetransmissionTimer* for the corresponding HARQ process when transmission is performed. + - 5> if the configured uplink grant is for the retransmission of the initial transmission at LTM cell switch: + - 6> start or restart the *cg-LTM-RetransmissionTimer* for the corresponding HARQ process when transmission is performed. + - 5> if the configured uplink grant is for the retransmission of the initial transmission of RACH-less handover: + - 6> start or restart the *cg-RACH-less-RetransmissionTimer* for the corresponding HARQ process when transmission is performed. +- 4> if the identified HARQ process is pending and the transmission is performed and LBT failure indication is not received from lower layers: + - 5> consider the identified HARQ process as not pending. + +When determining if NDI has been toggled compared to the value in the previous transmission the MAC entity shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI. + +When *configuredGrantTimer* or *cg-RetransmissionTimer* or *cg-SDT-RetransmissionTimer* or *cg-LTM-RetransmissionTimer* or *cg-RACH-less-RetransmissionTimer* is started or restarted by a PUSCH transmission, it shall be started at the beginning of the first symbol of the PUSCH transmission. + +#### 5.4.2.2 HARQ process + +Each HARQ process is associated with a HARQ buffer. + +New transmissions are performed on the resource and with the MCS indicated on PDCCH or indicated in the Random Access Response (i.e. MAC RAR or fallbackRAR), or signalled in RRC or determined as specified in clause 5.1.2a for MSGA payload. Retransmissions are performed on the resource and, if provided, with the MCS indicated on PDCCH, or on the same resource and with the same MCS as was used for last made transmission attempt within a bundle, or on stored configured uplink grant resources and stored MCS when *cg-RetransmissionTimer* or *cg-SDT-RetransmissionTimer* or *cg-LTM-RetransmissionTimer* or *cg-RACH-less-RetransmissionTimer* is configured. If *cg-RetransmissionTimer* is configured, retransmissions with the same HARQ process may be performed on any configured grant configuration if the configured grant configurations have the same TBS. If *cg-SDT-RetransmissionTimer* is configured, retransmission for the initial CG-SDT transmission with the same HARQ process may be performed on any configured grant configuration if the configured grant configurations have the same TBS. + +When *cg-RetransmissionTimer* is configured and the HARQ entity obtains a MAC PDU to transmit and LBT failure indication is received from lower layer, the corresponding HARQ process is considered to be pending. For a configured uplink grant, configured with *cg-RetransmissionTimer*, each associated HARQ process is considered as not pending when: + +- a transmission is performed on that HARQ process and LBT failure indication is not received from lower layers; or + +- the configured uplink grant is initialised and this HARQ process is not associated with another active configured uplink grant; or +- the HARQ buffer for this HARQ process is flushed. + +If the HARQ entity requests a new transmission for a TB, the HARQ process shall: + +- 1> store the MAC PDU in the associated HARQ buffer; +- 1> store the uplink grant received from the HARQ entity; +- 1> generate a transmission as described below. + +If the HARQ entity requests a retransmission for a TB, the HARQ process shall: + +- 1> store the uplink grant received from the HARQ entity; +- 1> generate a transmission as described below. + +To generate a transmission for a TB, the HARQ process shall: + +- 1> if the MAC PDU was obtained from the Msg3 buffer; or +- 1> if the MAC PDU was obtained from the MSGA buffer; or +- 1> if there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer or the MSGA buffer: + - 2> if there are neither NR sidelink transmission nor transmission of V2X sidelink communication at the time of the transmission; or + - 2> if the transmission of the MAC PDU is prioritized over sidelink transmission or can be simultaneously performed with sidelink transmission: +- 3> instruct the physical layer to generate a transmission according to the stored uplink grant. + +If a HARQ process receives downlink feedback information, the HARQ process shall: + +- 1> stop the *cg-RetransmissionTimer*, if running; +- 1> if acknowledgement is indicated: + - 2> stop the *configuredGrantTimer*, if running. + +If the *configuredGrantTimer* expires for a HARQ process, the HARQ process shall: + +- 1> stop the *cg-RetransmissionTimer*, if running; +- 1> stop the *cg-SDT-RetransmissionTimer*, if running. +- 1> stop the *cg-LTM-RetransmissionTimer*, if running; +- 1> stop the *cg-RACH-less-RetransmissionTimer*, if running; +- 1> if a PDCCH addressed to the MAC entity's C-RNTI has not been received after initial transmission for the CG-SDT with CCCH message to which the *configuredGrantTimer* corresponds: + - 2> indicate failure to perform SDT procedure to the upper layer. + +The transmission of the MAC PDU is prioritized over sidelink transmission or can be performed simultaneously with sidelink transmission if one of the following conditions is met: + +- if there are both a sidelink grant for NR sidelink transmission and configured grant(s) for transmission of V2X sidelink communication on SL-SCH as determined in clause 5.14.1.2.2 of TS 36.321 [22] at the time of the transmission, and neither the NR sidelink transmission is prioritized as determined in clause 5.22.1.3.1a nor the transmission(s) of V2X sidelink communication is prioritized as determined in clause 5.14.1.2.2 of TS 36.321 [22]; or + +- if there are both a sidelink grant NR sidelink transmission and configured grant(s) for transmission of V2X sidelink communication on SL-SCH as determined in clause 5.14.1.2.2 of TS 36.321 [22] at the time of the transmission, and the MAC entity is able to perform this UL transmission simultaneously with the NR sidelink transmission and/or the transmission(s) of V2X sidelink communication; or +- if there is only configured grant(s) for transmission of V2X sidelink communication on SL-SCH as determined in clause 5.14.1.2.2 of TS 36.321 [22] at the time of the transmission, and either none of the transmission(s) of V2X sidelink communication is prioritized as determined in clause 5.14.1.2.2 of TS 36.321 [22] or the MAC entity is able to perform this UL transmission simultaneously with the transmission(s) of V2X sidelink communication; or +- if there is only a sidelink grant for NR sidelink transmission at the time of the transmission, and if the NR sidelink transmission is not prioritized as determined in clause 5.22.1.3.1a, or there is a sidelink grant for NR sidelink transmission at the time of the transmission and the MAC entity is able to perform this UL transmission simultaneously with the NR sidelink transmission; or +- if there are both a sidelink grant for NR sidelink transmission and configured grant(s) for transmission of V2X sidelink communication on SL-SCH as determined in clause 5.14.1.2.2 of TS 36.321 [22] at the time of the transmission, and either only the of NR sidelink transmission is prioritized as determined in clause 5.22.1.3.1a or only the transmission(s) of V2X sidelink communication is prioritized as determined in clause 5.14.1.2.2 of TS 36.321 [22] and the MAC entity is able to perform this UL transmission simultaneously with the prioritized NR sidelink transmission or the transmission of V2X sidelink communication: + +NOTE 1: Among the UL transmissions where the MAC entity is able to perform the transmission of NR sidelink communication prioritized simultaneously, if there are more than one UL transmission which the MAC entity is not able to perform simultaneously, it is up to UE implementation whether this UL transmission is performed. + +NOTE 2: Among the UL transmissions that the MAC entity is able to perform simultaneously with all transmission(s) of V2X sidelink communication prioritized, if there are more than one UL transmission which the MAC entity is not able to perform simultaneously, it is up to UE implementation whether this UL transmission is performed. + +NOTE 3: Among the UL transmissions where the MAC entity is able to perform the NR sidelink transmission prioritized simultaneously with all transmission(s) of V2X sidelink communication prioritized, if there are more than one UL transmission which the MAC entity is not able to perform simultaneously, it is up to UE implementation whether this UL transmission is performed. + +NOTE 4: If there is configured grant(s) for transmission of V2X sidelink communication on SL-SCH as determined in clause 5.14.1.2.2 of TS 36.321 [22] at the time of the transmission, and the MAC entity is not able to perform this UL transmission simultaneously with the transmission(s) of V2X sidelink communication, and prioritization-related information is not available prior to the time of the transmission due to processing time restriction, it is up to UE implementation whether this UL transmission is performed. + +## 5.4.3 Multiplexing and assembly + +### 5.4.3.1 Logical Channel Prioritization + +#### 5.4.3.1.1 General + +The Logical Channel Prioritization (LCP) procedure is applied whenever a new transmission is performed. + +RRc controls the scheduling of uplink data by signalling for each logical channel per MAC entity: + +- *priority* where an increasing priority value indicates a lower priority level; +- *prioritisedBitRate* which sets the Prioritized Bit Rate (PBR); +- *bucketSizeDuration* which sets the Bucket Size Duration (BSD). + +RRc additionally controls the LCP procedure by configuring mapping restrictions for each logical channel: + +- *allowedSCS-List* which sets the allowed Subcarrier Spacing(s) for transmission; + +- *maxPUSCH-Duration* which sets the maximum PUSCH duration allowed for transmission; +- *configuredGrantType1Allowed* which sets whether a configured grant Type 1 can be used for transmission; +- *allowedServingCells* which sets the allowed cell(s) for transmission; +- *allowedCG-List* which sets the allowed configured grant(s) for transmission; +- *allowedPHY-PriorityIndex* which sets the allowed PHY priority index(es) of a dynamic grant for transmission; +- *allowedHARQ-mode* which sets the allowed UL HARQ mode for transmission. + +The following UE variable is used for the Logical channel prioritization procedure: + +- *Bj* which is maintained for each logical channel *j*. + +The MAC entity shall initialize *Bj* of the logical channel to zero when the logical channel is established. + +For each logical channel *j*, the MAC entity shall: + +- 1> increment *Bj* by the product PBR × T before every instance of the LCP procedure, where T is the time elapsed since *Bj* was last incremented; +- 1> if the value of *Bj* is greater than the bucket size (i.e. PBR × BSD): + - 2> set *Bj* to the bucket size. + +NOTE: The exact moment(s) when the UE updates *Bj* between LCP procedures is up to UE implementation, as long as *Bj* is up to date at the time when a grant is processed by LCP. + +#### 5.4.3.1.2 Selection of logical channels + +The MAC entity shall, when a new transmission is performed: + +- 1> select the logical channels for each UL grant that satisfy all the following conditions: + - 2> the set of allowed Subcarrier Spacing index values in *allowedSCS-List*, if configured, includes the Subcarrier Spacing index associated to the UL grant; and + - 2> *maxPUSCH-Duration*, if configured, is larger than or equal to the PUSCH transmission duration associated to the UL grant; and + - 2> *configuredGrantType1Allowed*, if configured, is set to *true* in case the UL grant is a Configured Grant Type 1; and + - 2> *allowedServingCells*, if configured, includes the Cell information associated to the UL grant. Does not apply to logical channels associated with a DRB configured with PDCP duplication within the same MAC entity (i.e. CA duplication) when CA duplication is deactivated for this DRB in this MAC entity; and + - 2> *allowedCG-List*, if configured, includes the configured grant index associated to the UL grant; and + - 2> *allowedPHY-PriorityIndex*, if configured, includes the priority index (as specified in clause 9 of TS 38.213 [6]) associated to the dynamic UL grant; and + - 2> *allowedHARQ-mode*, if configured, includes the allowed UL HARQ mode for the HARQ process associated to the UL grant. + +NOTE: The Subcarrier Spacing index, PUSCH transmission duration, Cell information, and priority index are included in Uplink transmission information received from lower layers for the corresponding scheduled uplink transmission. + +#### 5.4.3.1.3 Allocation of resources + +Before the successful completion of the Random Access procedure initiated for DAPS handover, the target MAC entity shall not select the logical channel(s) corresponding to non-DAPS DRB(s) for the uplink grant received in a Random + +Access Response or the uplink grant for the transmission of the MSGA payload. The source MAC entity shall select only the logical channel(s) corresponding to DAPS DRB(s) during DAPS handover. + +The MAC entity shall, when a new transmission is performed: + +- 1> allocate resources to the logical channels as follows: + - 2> logical channels selected in clause 5.4.3.1.2 for the UL grant with $B_j > 0$ are allocated resources in a decreasing priority order. If the PBR of a logical channel is set to *infinity*, the MAC entity shall allocate resources for all the data that is available for transmission on the logical channel before meeting the PBR of the lower priority logical channel(s); + - 2> decrement $B_j$ by the total size of MAC SDUs served to logical channel $j$ above; + - 2> if any resources remain, all the logical channels selected in clause 5.4.3.1.2 are served in a strict decreasing priority order (regardless of the value of $B_j$ ) until either the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally. + +NOTE 1: The value of $B_j$ can be negative. + +If the MAC entity is requested to simultaneously transmit multiple MAC PDUs, or if the MAC entity receives the multiple UL grants within one or more coinciding PDCCH occasions (i.e. on different Serving Cells), it is up to UE implementation in which order the grants are processed. + +The UE shall also follow the rules below during the scheduling procedures above: + +- the UE should not segment an RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the whole SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources of the associated MAC entity; +- if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill the grant of the associated MAC entity as much as possible; +- the UE should maximise the transmission of data; +- if the MAC entity is given a UL grant size that is equal to or larger than 8 bytes (when eLCID is not used) or 10 bytes (when eLCID is used) while having data available and allowed (according to clause 5.4.3.1) for transmission, the MAC entity shall not transmit only padding BSR and/or padding. + +The MAC entity shall: + +- 1> if the MAC entity is configured with *enhancedSkipUplinkTxDynamic* with value *true* and the grant indicated to the HARQ entity was addressed to a C-RNTI, or if the MAC entity is configured with *enhancedSkipUplinkTxConfigured* with value *true* and the grant indicated to the HARQ entity is a configured uplink grant: + - 2> if there is no UCI to be multiplexed on this PUSCH transmission as specified in TS 38.213 [6]; and + - 2> if there is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.212 [9]; and + - 2> if the MAC PDU includes zero MAC SDUs; and + - 2> if the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR: + - 3> not generate a MAC PDU for the HARQ entity. +- 1> else if the MAC entity is configured with *skipUplinkTxDynamic* with value *true* and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant: + - 2> if there is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.212 [9]; and + - 2> if the MAC PDU includes zero MAC SDUs; and + +- 2> if the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR: +- 3> not generate a MAC PDU for the HARQ entity. + +Logical channels shall be prioritised in accordance with the following order (highest priority listed first): + +- MAC CE for C-RNTI, or data from UL-CCCH; +- MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation; +- MAC CE for Sidelink Configured Grant Confirmation; +- MAC CE for LBT failure; +- MAC CE for SL LBT failure according to clause 5.31.2; +- MAC CE for Timing Advance Report; +- MAC CE for Delay Status Report; +- MAC CE for SL-BSR prioritized according to clause 5.22.1.6; +- MAC CE for (Extended) BSR, with exception of BSR included for padding; +- MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR or MAC CE for Single Entry PHR with assumed PUSCH, or MAC CE for Multiple Entry PHR with assumed PUSCH; +- MAC CE for Positioning Measurement Gap Activation/Deactivation Request; +- MAC CE for the number of Desired Guard Symbols; +- MAC CE for Case-6 Timing Request; +- MAC CE for (Extended) Pre-emptive BSR; +- MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding; +- MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment; +- data from any Logical Channel, except data from UL-CCCH; +- MAC CE for Recommended bit rate query; +- MAC CE for BSR included for padding; +- MAC CE for SL-BSR included for padding. + +NOTE 2: Prioritization among MAC CEs of same priority is up to UE implementation. + +The MAC entity shall prioritize any MAC CE listed in a higher order than 'data from any Logical Channel, except data from UL-CCCH' over NR sidelink transmission. + +#### 5.4.3.2 Multiplexing of MAC Control Elements and MAC SDUs + +The MAC entity shall multiplex MAC CEs and MAC SDUs in a MAC PDU according to clauses 5.4.3.1 and 6.1.2. + +NOTE: Content of a MAC PDU does not change after being built for transmission on a dynamic uplink grant, regardless of LBT outcome. + +#### 5.4.4 Scheduling Request + +The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission. + +The MAC entity may be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For a logical channel or for SCell beam failure recovery (see clause 5.17) and for consistent LBT failure recovery (see clause 5.21), at most one PUCCH resource for SR is configured per BWP. For a logical channel serving a radio bearer configured with SDT, PUCCH resource for SR is not configured for SDT. For beam failure recovery of BFD-RS set(s) of Serving Cell, up to two PUCCH resources for SR is configured per BWP. For positioning measurement gap activation/deactivation request, a dedicated SR configuration is configured. + +Each SR configuration corresponds to one or more logical channels and/or to SCell beam failure recovery and/or to consistent LBT failure recovery and/or to beam failure recovery of a BFD-RS set and/or to positioning measurement gap activation/deactivation request. Each logical channel, SCell beam failure recovery, beam failure recovery of a BFD-RS set and consistent LBT failure recovery, may be mapped to zero or one SR configuration, which is configured by RRC. The SR configuration of the logical channel that triggered a BSR (clause 5.4.5) or a DSR (clause 5.4.9) or the SCell beam failure recovery or the beam failure recovery of a BFD-RS set or the consistent LBT failure recovery (clause 5.21) (if such a configuration exists) or positioning measurement gap activation/deactivation request (clause 5.25) is considered as corresponding SR configuration for the triggered SR. Any SR configuration may be used for an SR triggered by Pre-emptive BSR (clause 5.4.7) or Timing Advance reporting (clause 5.4.8). + +RRC configures the following parameters for the scheduling request procedure: + +- *sr-ProhibitTimer* (per SR configuration); +- *sr-TransMax* (per SR configuration). + +The following UE variables are used for the scheduling request procedure: + +- *SR\_COUNTER* (per SR configuration). + +If an SR is triggered and there are no other SRs pending corresponding to the same SR configuration, the MAC entity shall set the *SR\_COUNTER* of the corresponding SR configuration to 0. + +When an SR is triggered, it shall be considered as pending until it is cancelled. + +All pending SR(s) for BSR triggered according to the BSR procedure (clause 5.4.5) prior to the MAC PDU assembly shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the MAC PDU is transmitted and this PDU includes a Long, Refined Long or Short BSR MAC CE which contains buffer status up to (and including) the last event that triggered a BSR (see clause 5.4.5) prior to the MAC PDU assembly. All pending SR(s) for BSR triggered according to the BSR procedure (clause 5.4.5) shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the UL grant(s) can accommodate all pending data available for transmission. + +The MAC entity shall for each pending SR not triggered according to the BSR procedure (clause 5.4.5) for a Serving Cell: + +- 1> if this SR was triggered by Pre-emptive BSR procedure (see clause 5.4.7) prior to the MAC PDU assembly and a MAC PDU containing the relevant Pre-emptive BSR MAC CE is transmitted; or +- 1> if this SR was triggered by beam failure recovery (see clause 5.17) of an SCell and a MAC PDU is transmitted and this PDU includes a MAC CE for BFR which contains beam failure recovery information for this SCell; or +- 1> if this SR was triggered by beam failure recovery (see clause 5.17) for a BFD-RS set of a Serving Cell and a MAC PDU is transmitted and this PDU includes an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE which contains beam failure recovery information for this BFD-RS set of the Serving Cell; or +- 1> if this SR was triggered by beam failure recovery (see clause 5.17) of an SCell and this SCell is deactivated (see clause 5.9); or +- 1> if this SR was triggered by beam failure recovery (see clause 5.17) for a BFD-RS set of an SCell and this SCell is deactivated (see clause 5.9); or +- 1> if the SR is triggered by positioning measurement gap activation/deactivation request (see clause 5.25) and the Positioning Measurement Gap Activation/Deactivation Request MAC CE that triggers the SR has already been cancelled; or + +- 1> if this SR was triggered by consistent LBT failure recovery (see clause 5.21) of an SCell and a MAC PDU is transmitted and the MAC PDU includes an LBT failure MAC CE that indicates consistent LBT failure for this SCell; or +- 1> if this SR was triggered by consistent LBT failure recovery (see clause 5.21) of an SCell and all the triggered consistent LBT failure(s) for this SCell are cancelled; or +- 1> if this SR was triggered by Timing Advance reporting (see clause 5.4.8) and all the triggered Timing Advance reports are cancelled; or +- 1> if this SR was triggered by DSR procedure (see clause 5.4.9) and the DSR that triggered the SR has been cancelled: + - 2> cancel the pending SR and stop the corresponding *sr-ProhibitTimer*, if running. + +Only PUCCH resources on a BWP which is active at the time of SR transmission occasion are considered valid. + +As long as at least one SR is pending, the MAC entity shall for each pending SR: + +- 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and +- 1> if there is no ongoing LTM cell switch; and +- 1> if *rach-lessHO* is not configured: + - 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR. +- 1> else, for the SR configuration corresponding to the pending SR: + - 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and + - 2> if *sr-ProhibitTimer* is not running at the time of the SR transmission occasion; and + - 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap: + - 3> if the PUCCH resource for the SR transmission occasion overlaps with neither a UL-SCH resource whose simultaneous transmission with the SR is not allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCH-Groups* nor an SL-SCH resource; or + - 3> if the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or + - 3> if the MAC entity is configured with *lch-basedPrioritization*, and the PUCCH resource for the SR transmission occasion does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or with the PUSCH duration of a MSGA payload, and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCHgroups*, and the priority of the uplink grant is determined as specified in clause 5.4.1; or + - 3> if both *sl-PrioritizationThres* and *ul-PrioritizationThres* are configured and the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5 overlaps with any UL-SCH resource(s) carrying a MAC PDU, and the value of the priority of the triggered SR determined as specified in clause 5.22.1.5 is lower than *sl-PrioritizationThres* and the value of the highest priority of the logical channel(s) in the MAC PDU is higher than or equal to *ul-PrioritizationThres* and any MAC CE prioritized as described in clause 5.4.3.1.3 is not included in the MAC PDU and the MAC PDU is not prioritized by upper layer according to TS 23.287 [19]; or + - 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and either transmission on + +the SL-SCH resource is not prioritized as described in clause 5.22.1.3.1a or the priority value of the logical channel that triggered SR is lower than *ul-PrioritizationThres*, if configured; or + +- 3> if an SL-SCH resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU determined as specified in clause 5.22.1.3.1a for the SL-SCH resource; or +- 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.4.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and either transmission on the SL-PRS resource is not prioritized as described in clause 5.22.1.3.1a or 5.22.1.3.1b or the priority value of the logical channel that triggered SR is lower than *ul-PrioritizationThres*, if configured; or +- 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3.1a for the SL-PRS resource: +- 4> consider the SR transmission as a prioritized SR transmission. +- 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of *simultaneousPUCCH-PUSCH* or *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup* or *simultaneousSR-PUSCH-diffPUCCH-Groups*; +- 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with *autonomousTx* whose PUSCH has already started: + - 5> stop the *configuredGrantTimer* for the corresponding HARQ process of the de-prioritized uplink grant(s); + - 5> stop the *cg-RetransmissionTimer* for the corresponding HARQ process of the de-prioritized uplink grant(s). +- 4> if *SR\_COUNTER* < *sr-TransMax*: + - 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR; + - 5> if LBT failure indication is not received from lower layers: + - 6> increment *SR\_COUNTER* by 1; + - 6> start the *sr-ProhibitTimer*. + - 5> else if *lbt-FailureRecoveryConfig* is not configured: + - 6> increment *SR\_COUNTER* by 1. +- 4> else: + - 5> notify RRC to release PUCCH for all Serving Cells; + - 5> notify RRC to release SRS for all Serving Cells; + - 5> clear any configured downlink assignments and uplink grants; + - 5> clear any PUSCH resources for semi-persistent CSI reporting; + - 5> if *rach-lessHO* is not configured: + - 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs. +- 3> else: + +4> consider the SR transmission as a de-prioritized SR transmission. + +- NOTE 1: Except for SR for SCell beam failure recovery, the selection of which valid PUCCH resource for SR to signal SR on when the MAC entity has more than one overlapping valid PUCCH resource for the SR transmission occasion is left to UE implementation. +- NOTE 2: If more than one individual SR triggers an instruction from the MAC entity to the PHY layer to signal the SR on the same valid PUCCH resource, the *SR\_COUNTER* for the relevant SR configuration is incremented only once. +- NOTE 3: When the MAC entity has pending SR for SCell beam failure recovery and the MAC entity has one or more PUCCH resources (other than PUCCH resources of pending SR for beam failure recovery of a BFD-RS set) overlapping with PUCCH resource for SCell beam failure recovery for the SR transmission occasion, the MAC entity considers only the PUCCH resource for SCell beam failure recovery as valid. When the MAC entity has pending SR for beam failure recovery of a BFD-RS set of Serving Cell and the MAC entity has one or more PUCCH resources (other than PUCCH resources of pending SR for beam failure recovery) overlapping with PUCCH resource for beam failure recovery of that BFD-RS set for the SR transmission occasion, the MAC entity considers only the PUCCH resource for beam failure recovery of that BFD-RS set as valid. +- NOTE 4: For a UE operating in a semi-static channel access mode as described in TS 37.213 [18], PUCCH resources overlapping with the set of consecutive symbols where the UE does not transmit before the start of a next channel occupancy time are not considered valid. +- NOTE 5: If the MAC entity is configured with *lch-basedPrioritization*, the MAC entity does not take UCI multiplexing according to the procedure specified in TS 38.213 [6] into account when determining whether the valid PUCCH resource for the SR transmission can be signalled by the physical layer and the SR transmission occasion overlaps with the PUSCH duration of an uplink grant of a MSGA payload. +- NOTE 6: When the MAC entity has PUCCH resource for pending SR for SCell beam failure recovery overlapping with PUCCH resource for pending SR for beam failure recovery of a BFD-RS set for the SR transmission occasion, it's up to UE implementation to select PUCCH resource for SCell beam failure recovery or PUCCH resource for beam failure recovery of a BFD-RS set. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for BSR, which was initiated by the MAC entity prior to the MAC PDU assembly and which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU includes a BSR MAC CE which contains buffer status up to (and including) the last event that triggered a BSR (see clause 5.4.5) prior to the MAC PDU assembly; or +- the UL grant(s) can accommodate all pending data available for transmission. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for SL-BSR, which was initiated by the MAC entity prior to the sidelink MAC PDU assembly and which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU includes an SL-BSR MAC CE which contains buffer status up to (and including) the last event that triggered an SL-BSR (see clause 5.22.1.6) prior to the MAC PDU assembly; or +- the SL grant(s) can accommodate all pending data available for transmission. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for SL-CSI reporting, which has no valid PUCCH resources configured, if: + +- the SL grant can accommodate SL-CSI reporting MAC CE for transmission. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for SL-DRX command indication, which has no valid PUCCH resources configured, if: + +- the SL grant can accommodate SL-DRX command indication for transmission. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for BFR of an SCell, which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU contains a MAC CE for BFR which includes beam failure recovery information of that SCell; or +- the SCell is deactivated (as specified in clause 5.9) and all triggered BFRs for SCells are cancelled. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for BFR of a BFD-RS set of a Serving Cell, which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU contains an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE which includes beam failure recovery information of that BFD-RS set of the Serving Cell. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for consistent LBT failure recovery, which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU includes an LBT failure MAC CE that indicates consistent LBT failure for all the SCells that triggered consistent LBT failure; or +- all the SCells that triggered consistent LBT failure recovery are deactivated (see clause 5.9). + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for SL consistent LBT failure recovery, which has no valid PUCCH resources configured, if one of the following conditions is met: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU includes an SL LBT failure MAC CE that indicates SL consistent LBT failure; or +- all the triggered SL consistent LBT failure recovery are cancelled (see clause 5.31.2). + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for positioning measurement gap activation/deactivation request, which has no valid PUCCH resources configured, if: + +- the Positioning Measurement Gap Activation/Deactivation Request MAC CE that triggers the SR corresponding to the Random Access procedure has already been cancelled. + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for Timing Advance report, which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU includes a Timing Advance Report MAC CE (see clause 5.4.8). + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for DSR, which has no valid PUCCH resources configured, if: + +- the DSR that triggered the SR has been cancelled (see clause 5.4.9). + +The MAC entity may stop, if any, ongoing Random Access procedure due to a pending SR for SL-PRS Resource Request, which has no valid PUCCH resources configured, if: + +- a MAC PDU is transmitted using a UL grant other than a UL grant provided by Random Access Response or a UL grant determined as specified in clause 5.1.2a for the transmission of the MSGA payload, and this PDU includes a SL-PRS Resource Request MAC CE (see clause 5.22.1.12). + +## 5.4.5 Buffer Status Reporting + +The Buffer Status reporting (BSR) procedure is used to provide the serving gNB with information about UL data volume in the MAC entity. + +RRC configures the following parameters to control the BSR: + +- *periodicBSR-Timer*; +- *retxBSR-Timer*; +- *logicalChannelSR-DelayTimerApplied*; +- *logicalChannelSR-DelayTimer*; +- *logicalChannelSR-Mask*; +- *logicalChannelGroup*, *logicalChannelGroupIAB-Ext*; +- *sdt-LogicalChannelSR-DelayTimer*; +- *additionalBSR-TableAllowed*. + +Each logical channel may be allocated to an LCG using the *logicalChannelGroup*. The maximum number of LCGs is eight except for IAB-MTs configured with *logicalChannelGroupIAB-Ext*, for which the maximum number of LCGs is 256. + +The MAC entity determines the amount of UL data available for a logical channel according to the data volume calculation procedure in TSs 38.322 [3] and 38.323 [4]. + +A BSR shall be triggered if any of the following events occur for activated cell group: + +- UL data, for a logical channel which belongs to an LCG, becomes available to the MAC entity; and either + - this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG; or + - none of the logical channels which belong to an LCG contains any available UL data. + in which case the BSR is referred below to as 'Regular BSR'; +- UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status Report MAC CE plus its subheader, in which case the BSR is referred below to as 'Padding BSR'; +- *retxBSR-Timer* expires, and at least one of the logical channels which belong to an LCG contains UL data, in which case the BSR is referred below to as 'Regular BSR'; +- *periodicBSR-Timer* expires, in which case the BSR is referred below to as 'Periodic BSR'. + +NOTE 1: When Regular BSR triggering events occur for multiple logical channels simultaneously, each logical channel triggers one separate Regular BSR. + +For Regular BSR, the MAC entity shall: + +- 1> if the BSR is triggered for a logical channel for which *logicalChannelSR-DelayTimerApplied* with value *true* is configured by upper layers and SDT procedure is not on-going according to clause 5.27: + - 2> start or restart the *logicalChannelSR-DelayTimer*. +- 1> else if BSR is triggered for a logical channel for which *logicalChannelSR-DelayTimerApplied* with value *true* is configured by upper layers and SDT procedure is on-going according to clause 5.27: + - 2> start or restart *logicalChannelSR-DelayTimer* with the value as configured by the *sdt-LogicalChannelSR-DelayTimer*. +- 1> else: + - 2> if running, stop the *logicalChannelSR-DelayTimer*. + +For Regular and Periodic BSR, the MAC entity for which *logicalChannelGroupIAB-Ext* is not configured by upper layers shall: + +- 1> if for at least one LCG configured with *additionalBSR-TableAllowed*, the amount of UL data available for transmission is within the buffer sizes specified in Table 6.1.3.1-3: + - 2> report Refined Long BSR for all LCGs which have data available for transmission; +- 1> else: + - 2> if more than one LCG has data available for transmission when the MAC PDU containing the BSR is to be built: + - 3> report Long BSR for all LCGs which have data available for transmission. + - 2> else: + - 3> report Short BSR. + +For Regular and Periodic BSR, the MAC entity for which *logicalChannelGroupIAB-Ext* is configured by upper layers shall: + +- 1> if more than one LCG has data available for transmission when the MAC PDU containing the BSR is to be built: + - 2> if the maximum LCG ID among the configured LCGs is 7 or lower: + - 3> report Long BSR for all LCGs which have data available for transmission. + - 2> else: + - 3> report Extended Long BSR for all LCGs which have data available for transmission. +- 1> else: + - 2> report Extended Short BSR. + +For Padding BSR, the MAC entity for which *logicalChannelGroupIAB-Ext* is not configured by upper layers shall: + +- 1> if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader: + - 2> if more than one LCG has data available for transmission when the BSR is to be built: + - 3> if the number of padding bits is equal to the size of the Short BSR plus its subheader: + - 4> report Short Truncated BSR of the LCG with the highest priority logical channel with data available for transmission. + - 3> else: + - 4> report Long Truncated BSR of the LCG(s) with the logical channels having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG(s), and in case of equal priority, in increasing order of LCGID. + - 2> else: + - 3> report Short BSR. +- 1> else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader: + - 2> report Long BSR for all LCGs which have data available for transmission. + +For Padding BSR, the MAC entity for which *logicalChannelGroupIAB-Ext* is configured by upper layers shall: + +- 1> if the number of padding bits is equal to or larger than the size of the Extended Short BSR plus its subheader but smaller than the size of the Extended Long BSR plus its subheader: + - 2> if more than one LCG has data available for transmission when the BSR is to be built: + - 3> if the number of padding bits is equal to the size of the Short BSR plus its subheader: + - 4> report Short Truncated BSR of the LCG with the highest priority logical channel with data available for transmission. + - 3> else: + - 4> report Long Truncated BSR of the LCG(s) with the logical channels having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG(s), and in case of equal priority, in increasing order of LCGID. + - 2> else: + - 3> report Extended Short BSR. +- 1> else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader: + - 2> report Long BSR for all LCGs which have data available for transmission. + +- 3> if the number of padding bits is smaller than the size of the Extended Long Truncated BSR with zero Buffer Size field plus its subheader: + - 4> report Extended Short Truncated BSR of the LCG with the highest priority logical channel with data available for transmission. +- 3> else: + - 4> report Extended Long Truncated BSR of the LCG(s) with the logical channels having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG(s), and in case of equal priority, in increasing order of LCGID. +- 2> else: + - 3> report Extended Short BSR. +- 1> else if the number of padding bits is equal to or larger than the size of the Extended Long BSR plus its subheader: + - 2> report Extended Long BSR for all LCGs which have data available for transmission. + +For BSR triggered by *retxBSR-Timer* expiry, the MAC entity considers that the logical channel that triggered the BSR is the highest priority logical channel that has data available for transmission at the time the BSR is triggered. + +The MAC entity shall: + +- 1> if the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled: + - 2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the BSR MAC CE plus its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate the BSR MAC CE(s) as defined in clause 6.1.3.1; + - 3> start or restart *periodicBSR-Timer* except when all the generated BSRs are long or short Truncated or Extended long or short Truncated BSRs; + - 3> start or restart *retxBSR-Timer*. + - 2> if a Regular BSR has been triggered and *logicalChannelSR-DelayTimer* is not running: + - 3> if there is no UL-SCH resource available for a new transmission; or + - 3> if the MAC entity is configured with configured uplink grant(s) and the Regular BSR was triggered for a logical channel for which *logicalChannelSR-Mask* is set to *false*; or + - 3> if the UL-SCH resources available for a new transmission do not meet the LCP mapping restrictions (see clause 5.4.3.1) configured for the logical channel that triggered the BSR: + - 4> trigger a Scheduling Request. + +NOTE 2: UL-SCH resources are considered available if the MAC entity has been configured with, receives, or determines an uplink grant. If the MAC entity has determined at a given point in time that UL-SCH resources are available, this need not imply that UL-SCH resources are available for use at that point in time. + +A MAC PDU shall contain at most one BSR MAC CE, even when multiple events have triggered a BSR. The Regular BSR and the Periodic BSR shall have precedence over the padding BSR. + +The MAC entity shall restart *retxBSR-Timer* upon reception of a grant for transmission of new data on any UL-SCH. + +All triggered BSRs may be cancelled when the UL grant(s) can accommodate all pending data available for transmission but is not sufficient to additionally accommodate the BSR MAC CE plus its subheader. All BSRs triggered prior to MAC PDU assembly shall be cancelled when a MAC PDU is transmitted and this PDU includes a Long, + +Refined Long, Extended Long, Short, or Extended Short BSR MAC CE which contains buffer status up to (and including) the last event that triggered a BSR prior to the MAC PDU assembly. + +NOTE 3: MAC PDU assembly can happen at any point in time between uplink grant reception and actual transmission of the corresponding MAC PDU. BSR and SR can be triggered after the assembly of a MAC PDU which contains a BSR MAC CE, but before the transmission of this MAC PDU. In addition, BSR and SR can be triggered during MAC PDU assembly. + +NOTE 4: Void + +NOTE 5: If a HARQ process is configured with *cq-RetransmissionTimer* and if the BSR is already included in a MAC PDU for transmission on configured grant by this HARQ process, but not yet transmitted by lower layers, it is up to UE implementation how to handle the BSR content. + +## 5.4.6 Power Headroom Reporting + +The Power Headroom reporting procedure is used to provide the serving gNB with the following information: + +- Type 1 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated Serving Cell; +- Type 2 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH and PUCCH transmission on SpCell of the other MAC entity (i.e. E-UTRA MAC entity in EN-DC, NE-DC, and NGEN-DC cases); +- Type 3 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for SRS transmission per activated Serving Cell; +- MPE P-MPR: the power backoff to meet the MPE FR2 requirements for a Serving Cell operating on FR2; +- DPC: the adjustment to maximum output power for a given power class for a Serving Cell operating on FR1; +- DPCBC: the adjustment to maximum output power for a given power class for a Band Combination operating on FR1. + +RRc controls Power Headroom reporting by configuring the following parameters: + +- *dpc-Reporting-FR1*; +- *phr-AssumedPUSCH-Reporting*; +- *phr-PeriodicTimer*; +- *phr-ProhibitTimer*; +- *phr-Tx-PowerFactorChange*; +- *phr-Type2OtherCell*; +- *phr-ModeOtherCG*; +- *multiplePHR*; +- *mpe-Reporting-FR2*; +- *mpe-ProhibitTimer*; +- *mpe-Threshold*; +- *numberOfN*; +- *mpe-ResourcePoolToAddModList*; +- *twoPHRMode*. + +A Power Headroom Report (PHR) shall be triggered if any of the following events occur: + +- *phr-ProhibitTimer* expires or has expired and the path loss has changed more than *phr-Tx-PowerFactorChange* dB for at least one RS used as pathloss reference for one activated Serving Cell of any MAC entity of which the active DL BWP is not dormant BWP since the last transmission of a PHR in this MAC entity when the MAC entity has UL resources for new transmission; + +NOTE 1: The path loss variation for one cell assessed above is between the pathloss measured at present time on the current pathloss reference and the pathloss measured at the transmission time of the last transmission of PHR on the pathloss reference in use at that time, irrespective of whether the pathloss reference has changed in between. The current pathloss reference for this purpose does not include any pathloss reference configured using *pathlossReferenceRS-Pos* in TS 38.331 [5]. + +- *phr-PeriodicTimer* expires; +- upon configuration or reconfiguration of the power headroom reporting functionality by upper layers, which is not used to disable the function; +- activation of an SCell of any MAC entity with configured uplink of which *firstActiveDownlinkBWP-Id* is not set to dormant BWP; +- activation of an SCG; +- addition of the PSCell except if the SCG is deactivated (i.e. PSCell is newly added or changed); +- *phr-ProhibitTimer* expires or has expired, when the MAC entity has UL resources for new transmission, and the following is true for any of the activated Serving Cells of any MAC entity with configured uplink: + - there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the required power backoff due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]) for this cell has changed more than *phr-Tx-PowerFactorChange* dB since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or PUCCH transmission on this cell. +- Upon switching of activated BWP from dormant BWP to non-dormant DL BWP of an SCell of any MAC entity with configured uplink; +- if *dpc-Reporting-FR1* is configured, $\Delta P_{\text{PowerClass}} / \Delta P_{\text{PowerClass, CA}} / \Delta P_{\text{PowerClass, EN-DC}} / \Delta P_{\text{PowerClass, NR-DC}}$ reporting is triggered upon uplink duty cycle exceedance or upon return to the power class after the duty cycle exceedance, as specified in TS 38.101-1 [14] and TS 38.101-3 [16]). +- if *mpe-Reporting-FR2* is configured, and *mpe-ProhibitTimer* is not running: + - the measured P-MPR applied to meet FR2 MPE requirements as specified in TS 38.101-2 [15] is equal to or larger than *mpe-Threshold* for at least one activated FR2 Serving Cell since the last transmission of a PHR in this MAC entity; or + - the measured P-MPR applied to meet FR2 MPE requirements as specified in TS 38.101-2 [15] has changed more than *phr-Tx-PowerFactorChange* dB for at least one activated FR2 Serving Cell since the last transmission of a PHR due to the measured P-MPR applied to meet MPE requirements being equal to or larger than *mpe-Threshold* in this MAC entity. + +in which case the PHR is referred below to as 'MPE P-MPR report'. + +NOTE 2: The MAC entity should avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such temporary decrease in the values of $P_{\text{CMAX,fc}} / \text{PH}$ when a PHR is triggered by other triggering conditions. + +NOTE 3: If a HARQ process is configured with *cg-RetransmissionTimer* and if the PHR is already included in a MAC PDU for transmission on configured grant by this HARQ process, but not yet transmitted by lower layers, it is up to UE implementation how to handle the PHR content. + +If the MAC entity has UL resources allocated for a new transmission the MAC entity shall: + +1) if it is the first UL resource allocated for a new transmission since the last MAC reset: + +2) start *phr-PeriodicTimer*. + +- 1> if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and +- 1> if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of LCP as defined in clause 5.4.3.1: + - 2> if *multiplePHR* with value *true* is configured: + - 3> for each activated Serving Cell with configured uplink associated with any MAC entity of which the active DL BWP is not dormant BWP; and + - 3> for each activated Serving Cell with configured uplink associated with E-UTRA MAC entity: + - 4> if this MAC entity is configured with *twoPHRMode*: + - 5> if this Serving Cell is configured with multiple TRP PUSCH repetition and the MAC entity this Serving Cell belongs to is configured with *twoPHRMode*: + - 6> obtain two values of the Type 1 or the value of Type 3 power headroom for the corresponding uplink carrier as specified in clause 7.7 of TS 38.213 [6] for NR Serving Cell. + - 5> else: + - 6> obtain the value of the Type 1 or Type 3 power headroom for the corresponding uplink carrier as specified in clause 7.7 of TS 38.213 [6] for NR Serving Cell and clause 5.1.1.2 of TS 36.213 [17] for E-UTRA Serving Cell. + - 4> else (i.e. this MAC entity is not configured with *twoPHRMode*): + - 5> if this Serving Cell is configured with multiple TRP PUSCH repetition and the MAC entity this Serving Cell belongs to is configured with *twoPHRMode*: + - 6> if there is at least one real PUSCH transmission at the slot where the PHR MAC CE is transmitted: + - 7> obtain the value of the Type 1 power headroom of the first real transmission of the corresponding uplink carrier as specified in clause 7.7 of TS 38.213[6] for NR Serving Cell. + - 6> else if there is no real PUSCH transmission at the slot where the PHR MAC CE is transmitted: + - 7> obtain the value of the type 1 power headroom of the reference PUSCH transmission associated with the *SRS-ResourceSet* with a lower *SRS-resourceSetID* or the value of the type 3 power headroom for the corresponding uplink carrier as specified in clause 7.7 of TS 38.213[6] for NR Serving Cell. + - 5> else: + - 6> obtain the value of the Type 1 or Type 3 power headroom for the corresponding uplink carrier as specified in clause 7.7 of TS 38.213 [6] for NR Serving Cell and clause 5.1.1.2 of TS 36.213 [17] for E-UTRA Serving Cell. + - 4> if this MAC entity is configured with *phr-AssumedPUSCH-Reporting*: + - 5> if this MAC entity has UL resources allocated for transmission on this Serving Cell; or + - 5> if the other MAC entity, if configured, has UL resources allocated for transmission on this Serving Cell and *phr-ModeOtherCG* is set to *real* by upper layers: + - 6> if *dynamicTransformPrecoderFieldPresenceDCI-0-1-r18* or *dynamicTransformPrecoderFieldPresenceDCI-0-2-r18* is set to *enabled* in the active BWP of this Serving Cell: + - 7> obtain the value for the corresponding $P_{CMAX,fc}$ field for assumed PUSCH from the physical layer if available, as specified in clause 7.7 of TS 38.213 [6]. + - 6> obtain the value for the corresponding $P_{CMAX,fc}$ field from the physical layer. + +- 4> else (i.e. if this MAC entity is not configured with *phr-AssumedPUSCH-Reporting*) : + - 5> if this MAC entity has UL resources allocated for transmission on this Serving Cell; or + - 5> if the other MAC entity, if configured, has UL resources allocated for transmission on this Serving Cell and *phr-ModeOtherCG* is set to *real* by upper layers: + - 6> obtain the value for the corresponding $P_{\text{CMAX,fc}}$ field from the physical layer. + - 6> if *mpe-Reporting-FR2* is configured and this Serving Cell operates on FR2 and this Serving Cell is associated to this MAC entity: + - 7> obtain the value for the corresponding MPE field from the physical layer. + - 6> if *mpe-Reporting-FR2-r17* is configured and this Serving Cell operates on FR2 and this Serving Cell is associated to this MAC entity: + - 7> obtain the value for the corresponding MPEi field from the physical layer; + - 7> obtain the value for the corresponding Resourcei field from the physical layer. + - 6> if *dpc-Reporting-FR1* is configured and $\Delta P_{\text{PowerClass, CA}} / \Delta P_{\text{PowerClass, EN-DC}} / \Delta P_{\text{PowerClass, NR-DC}}$ reporting is triggered and this Serving Cell operates on FR1 and this Serving Cell is associated to this MAC entity: + - 7> obtain the value for the corresponding DPC field(s) from the physical layer. +- 3> if *phr-Type2OtherCell* with value *true* is configured: + - 4> if the other MAC entity is E-UTRA MAC entity: + - 5> obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity (i.e. E-UTRA MAC entity); + - 5> if *phr-ModeOtherCG* is set to *real* by upper layers: + - 6> obtain the value for the corresponding $P_{\text{CMAX,fc}}$ field for the SpCell of the other MAC entity (i.e. E-UTRA MAC entity) from the physical layer. + - 3> instruct the Multiplexing and Assembly procedure to generate and transmit the Enhanced Multiple entry PHR as defined in clause 6.1.3.49 if this MAC entity is configured with *mpe-Reporting-FR2-r17* or the Enhanced Multiple Entry PHR for multiple TRP MAC CE as defined in clause 6.1.3.51 if this MAC entity is configured with *twoPHRMode* or the Multiple Entry PHR with assumed PUSCH MAC CE as defined in clause 6.1.3.78 if this MAC entity is configured with *phr-AssumedPUSCH-Reporting* or the Multiple Entry PHR MAC CE as defined in clause 6.1.3.9 otherwise based on the values reported by the physical layer. +- 2> else (i.e. Single Entry PHR format is used): + - 3> if this MAC entity is configured with *twoPHRMode*: + - 4> obtain two values of the Type 1 power headroom from the physical layer for the corresponding uplink carrier of the PCell. + - 3> else: + - 4> obtain the value of the Type 1 power headroom from the physical layer for the corresponding uplink carrier of the PCell. + - 3> if this MAC entity is configured with *phr-AssumedPUSCH-Reporting*: + - 4> if *dynamicTransformPrecoderFieldPresenceDCI-0-1-r18* or *dynamicTransformPrecoderFieldPresenceDCI-0-2-r18* is set to *enabled* in the active BWP of this Serving Cell: + - 5> obtain the value for the corresponding $P_{\text{CMAX,fc}}$ field for assumed PUSCH from the physical layer, if available, as specified in clause 7.7 of TS 38.213 [6]. + +- 3> obtain the value for the corresponding $P_{CMAX,fc}$ field from the physical layer; + - 3> if *mpe-Reporting-FR2* is configured and this Serving Cell operates on FR2: + - 4> obtain the value for the corresponding MPE field from the physical layer. + - 3> if *mpe-Reporting-FR2-r17* is configured and this Serving Cell operates on FR2 and this Serving Cell is associated to this MAC entity: + - 4> obtain the value for the corresponding $MPE_i$ field from the physical layer; + - 4> obtain the value for the corresponding $Resource_i$ field from the physical layer. + - 3> if *dpc-Reporting-FR1* is configured and this Serving Cell operates on FR1: + - 4> obtain the value for the corresponding DPC field from the physical layer. + - 3> instruct the Multiplexing and Assembly procedure to generate and transmit the Enhanced Single entry PHR as defined in clause 6.1.3.48 if this MAC entity is configured with *mpe-Reporting-FR2-r17* or the Enhanced Single Entry PHR for multiple TRP MAC CE as defined in clause 6.1.3.50 if this MAC entity is configured with *twoPHRMode* or the Single Entry PHR with assumed PUSCH MAC CE as defined in clause 6.1.3.78 if this MAC entity is configured with *phr-AssumedPUSCH-Reporting* or the Single Entry PHR MAC CE as defined in clause 6.1.3.8 otherwise based on the values reported by the physical layer. +- 2> if this PHR report is an MPE P-MPR report: +- 3> start or restart the *mpe-ProhibitTimer*; + - 3> cancel triggered MPE P-MPR reporting for Serving Cells included in the PHR MAC CE. +- 2> start or restart *phr-PeriodicTimer*; +- 2> start or restart *phr-ProhibitTimer*; +- 2> cancel all triggered PHR(s). + +All triggered PHRs shall be cancelled when there is an ongoing SDT procedure as in clause 5.27 and the UL grant(s) can accommodate all pending data available for transmission but is not sufficient to additionally accommodate the PHR MAC CE plus its subheader. + +## 5.4.7 Pre-emptive Buffer Status Reporting + +The Pre-emptive Buffer Status reporting (Pre-emptive BSR) procedure is used by an IAB-MT to provide its parent IAB-DU(s) or IAB-donor-DU(s) with the information about the amount of the data expected to arrive at the IAB-MT from its child node(s) and/or UE(s) connected to it. + +If configured, Pre-emptive BSR may be triggered for the specific case of an IAB-MT if any of the following events occur: + +- UL grant is provided to child IAB node or UE; +- BSR is received from child IAB node or UE. + +IAB-MT may report Extended Pre-emptive BSR (as defined in clause 6.1.3.1) if the MAC entity of the IAB-MT is configured with *logicalChannelGroupIAB-Ext* by upper layers. Otherwise IAB-MT may report Pre-emptive BSR (as defined in clause 6.1.3.1). + +The MAC entity shall: + +- 1> if the Pre-emptive Buffer Status reporting procedure determines that at least one Pre-emptive BSR has been triggered and not cancelled: +- 2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the Extended Pre-emptive BSR or Pre-emptive BSR MAC CE plus its subheader as a result of logical channel prioritization: + +- 3> instruct the Multiplexing and Assembly procedure to generate the Extended Pre-emptive BSR or Pre-emptive BSR MAC CE as defined in clause 6.1.3.1. +- 2> else: + - 3> trigger a Scheduling Request. + +A MAC PDU shall contain at most one Pre-emptive BSR MAC CE or Extended Pre-emptive BSR MAC CE, even when multiple events have triggered a Pre-emptive BSR. + +All triggered Pre-emptive BSR(s) shall be cancelled when a MAC PDU is transmitted and this PDU includes the corresponding Pre-emptive BSR MAC CE or Extended Pre-emptive BSR MAC CE. + +NOTE: Pre-emptive BSR may be used for the case of dual-connected IAB node. It is up to network implementation to work out the associated MAC entity or entities which report the Pre-emptive BSR, and the associated expected amount of data reported by any such entity or entities. For the case of dual-connected IAB node, if two ingress BH RLC channels belonging to the same ingress LCG are mapped to two different egress Cell Groups (corresponding to different parent nodes), there may be ambiguity in Pre-emptive BSR calculations and interpretation by the receiving parent node(s) and the IAB node reporting pre-emptive BSR. + +## 5.4.8 Timing Advance Reporting + +The Timing Advance reporting procedure is used in a non-terrestrial network or an air to ground network to provide the gNB with an estimate of the UE's Timing Advance value (i.e., $T_{TA}$ as defined in the UE's TA formula, see TS 38.211 [8] clause 4.3.1). + +RRM controls Timing Advance reporting by configuring the following parameters: + +- *offsetThresholdTA*; +- *timingAdvanceSR*. + +A Timing Advance report (TAR) shall be triggered if any of the following events occur: + +- upon indication from upper layers to trigger a Timing Advance report; +- upon configuration of *offsetThresholdTA* by upper layers, if the UE has not previously reported Timing Advance value to current Serving Cell; +- if the variation between the current estimate of the Timing Advance value and the last reported Timing Advance value is equal to or larger than *offsetThresholdTA*, if configured. + +The MAC entity shall: + +- 1> if the Timing Advance reporting procedure determines that at least one TAR has been triggered and not cancelled: + - 2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the Timing Advance Report MAC CE plus its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate the Timing Advance Report MAC CE as defined in clause 6.1.3.56. + - 2> else: + - 3> if *timingAdvanceSR* is configured with value *enabled*: + - 4> trigger a Scheduling Request. + +NOTE: UL-SCH resources are considered available if the MAC entity has been configured with, receives, or determines an uplink grant. If the MAC entity has determined at a given point in time that UL-SCH resources are available, this need not imply that UL-SCH resources are available for use at that point in time. + +A MAC PDU shall contain at most one Timing Advance Report MAC CE, even when multiple events have triggered a Timing Advance report. The Timing Advance Report MAC CE shall be generated based on the latest available estimate of the UE's Timing Advance value prior to the MAC PDU assembly. + +All triggered Timing Advance reports shall be cancelled when a MAC PDU is transmitted and this PDU includes a Timing Advance Report MAC CE. + +### 5.4.9 Delay status reporting + +The Delay Status Reporting (DSR) procedure is used to provide the serving gNB with delay status of LCGs. This delay status for an LCG includes remaining time, which is the smallest remaining value of the PDCP *discardTimers* among SDUs buffered for the LCG as specified in clause 7.3 in TS 38.323 [4], and the total amount of delay-critical UL data for the LCG according to the data volume calculation procedure specified in clause 5.5 in TS 38.322 [3] and clause 5.6 in TS 38.323 [4] for the associated RLC and PDCP entities, respectively. + +RRC controls the DSR procedure by configuring the following parameter: + +- *remainingTimeThreshold*: the threshold on remaining time for triggering a DSR for an LCG. + +If an LCG is configured for delay status reporting, the MAC entity shall: + +- 1> if the smallest remaining value of the PDCP *discardTimers* among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE becomes below *remainingTimeThreshold* of the LCG; and +- 1> if there is no DSR pending for the LCG since the last transmission of a DSR MAC CE: + - 2> trigger a DSR for the LCG. + +If there is at least one DSR pending, the MAC entity shall: + +- 1> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the DSR MAC CE plus its subheader as a result of logical channel prioritization: + - 2> instruct the Multiplexing and Assembly procedure to generate the DSR MAC CE; +- 1> else if there is no pending SR already triggered by the DSR procedure for the same logical channel as of this DSR: + - 2> trigger a Scheduling Request. + +NOTE: The availability of UL-SCH resources for the transmission of the DSR MAC CE follows the same criteria specified in clause 5.4.5. + +An SDU is considered to be associated with a DSR if it is associated with the LCG which triggered the DSR and the remaining value of its PDCP *discardTimer* is below *remainingTimeThreshold*. + +A MAC PDU shall contain at most one DSR MAC CE. The MAC entity shall not include a DSR MAC CE in a MAC PDU if the MAC PDU can accommodate the SDUs associated with all the pending DSRs. + +After a DSR is triggered, it is considered as pending until it is cancelled. The MAC entity shall cancel a pending DSR, either when all the SDUs associated with the DSR have been discarded, or when a MAC PDU is transmitted and this MAC PDU includes either all the SDUs associated with the DSR or a DSR MAC CE that contains the delay information of all the SDUs associated with the DSR (as described in the clause 6.1.3.72). + +## 5.5 PCH reception + +When the MAC entity needs to receive PCH, the MAC entity shall: + +- 1> if a PCH assignment has been received on the PDCCH for the P-RNTI: + - 2> attempt to decode the TB on the PCH as indicated by the PDCCH information; + - 2> if the TB on the PCH has been successfully decoded: + +3> deliver the decoded MAC PDU to upper layers. + +## 5.6 BCH reception + +When the MAC entity needs to receive BCH, the MAC entity shall: + +- 1> receive and attempt to decode the BCH; +- 1> if a TB on the BCH has been successfully decoded: + - 2> deliver the decoded MAC PDU to upper layers. + +## 5.7 Discontinuous Reception (DRX) + +The MAC entity may be configured by RRC with a DRX functionality that controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SL-CS-RNTI and SL Semi-Persistent Scheduling V-RNTI. When using DRX operation, the MAC entity shall also monitor PDCCH according to requirements found in other clauses of this specification. When in RRC\_CONNECTED, if DRX is configured, for all the activated Serving Cells, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213 [6]. + +NOTE 1: Void + +RRC controls DRX operation by configuring the following parameters: + +- *drx-onDurationTimer*: the duration at the beginning of a DRX cycle; +- *drx-SlotOffset*: the delay before starting the *drx-onDurationTimer*; +- *drx-InactivityTimer*: the duration after the PDCCH occasion in which a PDCCH indicates a new UL, DL or SL transmission for the MAC entity; +- *drx-RetransmissionTimerDL* (per DL HARQ process except for the broadcast process): the maximum duration until a DL retransmission is received; +- *drx-RetransmissionTimerUL* (per UL HARQ process): the maximum duration until a grant for UL retransmission is received; +- *drx-LongCycleStartOffset*: the Long DRX cycle and *drx-StartOffset* which defines the subframe where the Long and Short DRX cycle starts; +- *drx-NonIntegerLongCycleStartOffset* (optional): the Long DRX cycle and *drx-StartOffset* which defines the subframe where the Long and Short DRX cycle start, when the length of the Long DRX cycle and/or the short DRX cycle is not an integer; +- *drx-ShortCycle* (optional): the Short DRX cycle; +- *drx-NonIntegerShortCycle* (optional): the Short DRX cycle whose length is not an integer; +- *drx-ShortCycleTimer* (optional): the duration the UE shall follow the Short DRX cycle; +- *drx-HARQ-RTT-TimerDL* (per DL HARQ process except for the broadcast process): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity; +- *drx-HARQ-RTT-TimerUL* (per UL HARQ process): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity; +- *drx-RetransmissionTimerSL* (per sidelink process): the maximum duration until a grant for SL retransmission is received; +- *drx-HARQ-RTT-TimerSL* (per sidelink process): the minimum duration before an SL retransmission grant is expected by the MAC entity; + +- *drx-LastTransmissionUL* (optional): the configuration to start *drx-HARQ-RTT-TimerUL* after the last transmission within a bundle; +- *ps-Wakeup* (optional): the configuration to start associated *drx-onDurationTimer* in case DCP is monitored but not detected; +- *ps-TransmitOtherPeriodicCSI* (optional): the configuration to report periodic CSI that is not L1-RSRP on PUCCH during the time duration indicated by *drx-onDurationTimer* in case DCP is configured but associated *drx-onDurationTimer* is not started; +- *ps-TransmitPeriodicL1-RSRP* (optional): the configuration to transmit periodic CSI that is L1-RSRP on PUCCH during the time duration indicated by *drx-onDurationTimer* in case DCP is configured but associated *drx-onDurationTimer* is not started; +- *downlinkHARQ-FeedbackDisabled* (optional): the configuration to disable HARQ feedback per DL HARQ process; +- *uplinkHARQ-Mode* (optional): the configuration to set *HARQmodeA* or *HARQmodeB* per UL HARQ process; +- *disableCG-RetransmissionMonitoring* (optional): the configuration to disable starting *drx-HARQ-RTT-TimerUL* for UL transmission over a configured uplink grant; +- *drx-TimeReferenceSFN* (optional): the reference SFN used in determining the start time of DRX on durations when short and/or long DRX cycle is not an integer. + +The following UE variable is used for the DRX operation if *drx-NonIntegerLongCycleStartOffset* is configured: + +- *DRX\_SFN\_COUNTER*: the counter that increments when SFN changes to 0. This counter can be implemented with a maximum value of 65535. + +Serving Cells of a MAC entity may be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all Serving Cells belong to that one DRX group. When two DRX groups are configured, each Serving Cell is uniquely assigned to either of the two groups. The DRX parameters that are separately configured for each DRX group are: *drx-onDurationTimer*, *drx-InactivityTimer*. The DRX parameters that are common to the DRX groups are: *drx-SlotOffset*, *drx-RetransmissionTimerDL*, *drx-RetransmissionTimerUL*, *drx-LongCycleStartOffset*, *drx-NonIntegerLongCycleStartOffset*, *drx-ShortCycle* (optional), *drx-NonIntegerShortCycle* (optional), *drx-ShortCycleTimer* (optional), *drx-HARQ-RTT-TimerDL*, and *drx-HARQ-RTT-TimerUL*. + +When DRX is configured, the Active Time for Serving Cells in a DRX group includes the time while: + +- *drx-onDurationTimer* or *drx-InactivityTimer* configured for the DRX group is running; or +- *drx-RetransmissionTimerDL*, *drx-RetransmissionTimerUL* or *drx-RetransmissionTimerSL* is running on any Serving Cell in the DRX group; or +- *ra-ContentionResolutionTimer* (as described in clause 5.1.5) or *msgB-ResponseWindow* (as described in clause 5.1.4a) is running; or +- a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4 or 5.22.1.5). If this Serving Cell is part of a non-terrestrial network, the Active Time is started after the Scheduling Request transmission that is performed when the *SR\_COUNTER* is 0 for all the SR configurations with pending SR(s) plus the UE-gNB RTT; or +- a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble (as described in clauses 5.1.4 and 5.1.4a); or +- there is an ongoing RACH-less LTM cell switch; or +- there is an ongoing RACH-less handover in a terrestrial network. + +The following MAC timers are used for DRX operation in a non-terrestrial network: + +- *HARQ-RTT-TimerDL-NTN* (per DL HARQ process configured with HARQ feedback enabled): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity; + +- *HARQ-RTT-TimerUL-NTN* (per UL HARQ process configured with *HARQModeA*): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity. + +When DRX is not configured and multicast DRX is configured for a G-RNTI or G-CS-RNTI, the MAC entity shall: + +- 1> monitor the PDCCH as specified in TS 38.213 [6]; +- 1> if a MAC PDU is received in a configured downlink assignment for unicast; or +- 1> if the PDCCH indicates a DL unicast transmission: + - 2> stop the *drx-RetransmissionTimerDL-PTM* for the corresponding HARQ process. + +When DRX is configured, the MAC entity shall: + +- 1> if a MAC PDU is received in a configured downlink assignment for unicast: + - 2> if this Serving Cell is configured with *downlinkHARQ-FeedbackDisabled*: + - 3> if the corresponding HARQ process is configured with HARQ feedback enabled: + - 4> set *HARQ-RTT-TimerDL-NTN* for the corresponding HARQ process equal to *drx-HARQ-RTT-TimerDL* plus the latest available UE-gNB RTT value; + - 4> start the *HARQ-RTT-TimerDL-NTN* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. + - 2> else: + - 3> start the *drx-HARQ-RTT-TimerDL* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. + +NOTE 1a: Void. + +NOTE 1b: Void. + +- 2> stop the *drx-RetransmissionTimerDL* for the corresponding HARQ process; +- 2> stop the *drx-RetransmissionTimerDL-PTM* for the corresponding HARQ process. +- 1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers: + - 2> if this Serving Cell is configured with *uplinkHARQ-Mode*: + - 3> if the corresponding HARQ process is configured as *HARQModeA*: + - 4> set *HARQ-RTT-TimerUL-NTN* for the corresponding HARQ process equal to *drx-HARQ-RTT-TimerUL* plus the latest available UE-gNB RTT value; + - 4> if *drx-LastTransmissionUL* is configured: + - 5> start the *HARQ-RTT-TimerUL-NTN* for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. + - 4> else: + - 5> start the *HARQ-RTT-TimerUL-NTN* for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. + - 2> else: + - 3> if *disableCG-RetransmissionMonitoring* is not configured for the configured uplink grant: + - 4> if *drx-LastTransmissionUL* is configured: + - 5> start the *drx-HARQ-RTT-TimerUL* for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. + +4> else: + +5> start the *drx-HARQ-RTT-TimerUL* for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. + +2> stop the *drx-RetransmissionTimerUL* for the corresponding HARQ process at the first transmission (within a bundle) of the corresponding PUSCH transmission. + +1> if a MAC PDU is transmitted in a configured sidelink grant: + +2> if the PUCCH resource is configured: + +3> start the *drx-HARQ-RTT-TimerSL* for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH transmission carrying the SL HARQ feedback; or + +3> start the *drx-HARQ-RTT-TimerSL* for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH resource for the SL HARQ feedback when the PUCCH is not transmitted; + +3> stop the *drx-RetransmissionTimerSL* for the corresponding HARQ process. + +2> else: + +3> start the *drx-HARQ-RTT-TimerSL* for the corresponding HARQ process at the first symbol after the end of the corresponding PSSCH transmission; + +3> stop the *drx-RetransmissionTimerSL* for the corresponding HARQ process. + +1> if a *drx-HARQ-RTT-TimerDL* expires: + +2> if the data of the corresponding HARQ process was not successfully decoded: + +3> start the *drx-RetransmissionTimerDL* for the corresponding HARQ process in the first symbol after the expiry of *drx-HARQ-RTT-TimerDL*. + +1> if a *HARQ-RTT-TimerDL-NTN* expires: + +2> if the data of the corresponding HARQ process was not successfully decoded: + +3> start the *drx-RetransmissionTimerDL* for the corresponding HARQ process in the first symbol after the expiry of *HARQ-RTT-TimerDL-NTN*. + +1> if a *drx-HARQ-RTT-TimerUL* expires: + +2> start the *drx-RetransmissionTimerUL* for the corresponding HARQ process in the first symbol after the expiry of *drx-HARQ-RTT-TimerUL*. + +1> if a *HARQ-RTT-TimerUL-NTN* expires: + +2> start the *drx-RetransmissionTimerUL* for the corresponding HARQ process in the first symbol after the expiry of *HARQ-RTT-TimerUL-NTN*. + +1> if a *drx-HARQ-RTT-TimerSL* expires: + +2> if a HARQ NACK feedback for the corresponding HARQ process is transmitted on PUCCH; or + +2> if a HARQ NACK feedback for the corresponding HARQ process is generated but not transmitted on PUCCH; or + +2> if the PUCCH resource is not configured for the SL grant: + +3> start the *drx-RetransmissionTimerSL* for the corresponding HARQ process in the first symbol after the expiry of *drx-HARQ-RTT-TimerSL*. + +NOTE : The UE handles the *drx-RetransmissionTimerSL* operation when *sl-PUCCH-Config* is configured by RRC but PUCCH resource is not scheduled same as when *sl-PUCCH-Config* is not configured. + +- 1> if a DRX Command MAC CE indicated by PDCCH addressed to C-RNTI or CS-RNTI, or by a configured downlink assignment for unicast transmission or a Long DRX Command MAC CE is received: + - 2> stop *drx-onDurationTimer* for each DRX group; + - 2> stop *drx-InactivityTimer* for each DRX group. +- 1> if *drx-InactivityTimer* for a DRX group expires: + - 2> if the Short DRX cycle is configured: + - 3> start or restart *drx-ShortCycleTimer* for this DRX group in the first symbol after the expiry of *drx-InactivityTimer*; + - 3> use the Short DRX cycle for this DRX group. + - 2> else: + - 3> use the Long DRX cycle for this DRX group. +- 1> if a DRX Command MAC CE indicated by PDCCH addressed to C-RNTI or CS-RNTI, or by a configured downlink assignment for unicast transmission is received: + - 2> if the Short DRX cycle is configured: + - 3> start or restart *drx-ShortCycleTimer* for each DRX group in the first symbol after the end of DRX Command MAC CE reception; + - 3> use the Short DRX cycle for each DRX group. + - 2> else: + - 3> use the Long DRX cycle for each DRX group. +- 1> if *drx-ShortCycleTimer* for a DRX group expires: + - 2> use the Long DRX cycle for this DRX group. +- 1> if a Long DRX Command MAC CE is received: + - 2> stop *drx-ShortCycleTimer* for each DRX group; + - 2> use the Long DRX cycle for each DRX group. +- 1> if the *drx-NonIntegerLongCycleStartOffset* is configured: + - 2> increment *DRX\_SFN\_COUNTER* by 1 in the first symbol of a slot in which SFN changes to 0; + - 2> if DRX is (re-)configured by RRC: + - 3> set *DRX\_SFN\_COUNTER* to 0 in the first symbol of the slot immediately after the successful completion of the RRC (re-)configuration; +- 1> if the Short DRX cycle is used for a DRX group and the *drx-NonIntegerShortCycle* is not configured, and $[(\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{drx-ShortCycle}) = (\text{drx-StartOffset}) \bmod (\text{drx-ShortCycle})$ ; or +- 1> if the Short DRX cycle is used for a DRX group and the *drx-NonIntegerShortCycle* is configured, and $\text{floor}([(DRX\_SFN\_COUNTER \times 10240) + (\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{drx-NonIntegerShortCycle})) = \text{floor}([(drx-TimeReferenceSFN \times 10) + \text{drx-StartOffset}] \bmod (\text{drx-NonIntegerShortCycle}))$ : + - 2> start *drx-onDurationTimer* for this DRX group after *drx-SlotOffset* from the beginning of the subframe. +- 1> if the Long DRX cycle is used for a DRX group and the *drx-NonIntegerLongCycleStartOffset* is not configured, and $[(\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{drx-LongCycle}) = \text{drx-StartOffset}$ ; or + +- 1> if the Long DRX cycle is used for a DRX group and the *drx-NonIntegerLongCycleStartOffset* is configured, and + +$$\text{floor}([(DRX\_SFN\_COUNTER \times 10240) + (SFN \times 10) + \text{subframe number}] \bmod (drx-NonIntegerLongCycle)) = \text{floor}([(drx-TimeReferenceSFN \times 10) + drx-StartOffset] \bmod (drx-NonIntegerLongCycle))$$ +- 2> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6], clause 10.3: + - 3> if DCP indication associated with the current DRX cycle received from lower layer indicated to start *drx-onDurationTimer*, as specified in TS 38.213 [6]; or + - 3> if all DCP occasion(s) in time domain, as specified in TS 38.213 [6], associated with the current DRX cycle occurred in Active Time considering grants/assignments/DRX Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to start of the last DCP occasion, or during a measurement gap, or when the MAC entity monitors for a PDCCH transmission on the search space indicated by *recoverySearchSpaceId* of the SpCell identified by the C-RNTI while the *ra-ResponseWindow* is running (as specified in clause 5.1.4); or + - 3> if *ps-Wakeup* is configured with value *true* and DCP indication associated with the current DRX cycle has not been received from lower layers: + - 4> start *drx-onDurationTimer* after *drx-SlotOffset* from the beginning of the subframe. +- 2> else: + - 3> start *drx-onDurationTimer* for this DRX group after *drx-SlotOffset* from the beginning of the subframe. + +NOTE 2: In case of unaligned SFN across carriers in a cell group, the SFN of the SpCell is used to calculate the DRX duration. + +- 1> if a DRX group is in Active Time: + - 2> monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38.213 [6]; + - 2> if the PDCCH indicates a DL transmission; or + - 2> if the PDCCH indicates a one-shot HARQ feedback as specified in clause 9.1.4 of TS 38.213 [6]; or + - 2> if the PDCCH indicates a retransmission of HARQ feedback as specified in clause 9.1.5 of TS 38.213 [6]: + - 3> if this Serving Cell is configured with *downlinkHARQ-FeedbackDisabled*: + - 4> if the corresponding HARQ process is configured with HARQ feedback enabled: + - 5> set *HARQ-RTT-TimerDL-NTN* for the corresponding HARQ process equal to *drx-HARQ-RTT-TimerDL* plus the latest available UE-gNB RTT value; + - 5> start the *HARQ-RTT-TimerDL-NTN* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. + - 3> else: + - 4> start or restart the *drx-HARQ-RTT-TimerDL* for the corresponding HARQ process(es) whose HARQ feedback is reported in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. + +NOTE 3: When HARQ feedback is postponed by PDSCH-to-HARQ\_feedback timing indicating an inapplicable k1 value, as specified in TS 38.213 [6], the corresponding transmission opportunity to send the DL HARQ feedback is indicated in a later PDCCH requesting the HARQ-ACK feedback. + +- 3> stop the *drx-RetransmissionTimerDL* for the corresponding HARQ process(es) whose HARQ feedback is reported; +- 3> stop the *drx-RetransmissionTimerDL-PTM* for the corresponding HARQ process; +- 3> if the PDSCH-to-HARQ\_feedback timing indicate an inapplicable k1 value as specified in TS 38.213 [6]: + - 4> start the *drx-RetransmissionTimerDL* in the first symbol after the (end of the last) PDSCH transmission (within a bundle) for the corresponding HARQ process. + +- 2> if the PDCCH indicates a UL transmission: + - 3> if this Serving Cell is configured with *uplinkHARQ-Mode*: + - 4> if the corresponding HARQ process is configured as *HARQModeA*: + - 5> set *HARQ-RTT-TimerUL-NTN* for the corresponding HARQ process equal to *drx-HARQ-RTT-TimerUL* plus the latest available UE-gNB RTT value; + - 5> if *drx-LastTransmissionUL* is configured: + - 6> start the *HARQ-RTT-TimerUL-NTN* for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. + - 5> else: + - 6> start the *HARQ-RTT-TimerUL-NTN* for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. + - 3> else: + - 4> if *drx-LastTransmissionUL* is configured: + - 5> start the *drx-HARQ-RTT-TimerUL* for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission. + - 4> else: + - 5> start the *drx-HARQ-RTT-TimerUL* for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission. + - 3> stop the *drx-RetransmissionTimerUL* for the corresponding HARQ process. + - 2> if the PDCCH indicates an SL transmission: + - 3> if the PUCCH resource is configured: + - 4> start the *drx-HARQ-RTT-TimerSL* for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH transmission carrying the SL HARQ feedback; or + - 4> start the *drx-HARQ-RTT-TimerSL* for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH resource for the SL HARQ feedback when the PUCCH is not transmitted; + - 4> stop the *drx-RetransmissionTimerSL* for the corresponding HARQ process. + - 3> else: + - 4> start the *drx-HARQ-RTT-TimerSL* for the corresponding HARQ process at the first symbol after end of PDCCH occasion; + - 4> stop the *drx-RetransmissionTimerSL* for the corresponding HARQ process. + - 2> if the PDCCH indicates a new transmission (DL, UL or SL) on a Serving Cell in this DRX group: + - 3> start or restart *drx-InactivityTimer* for this DRX group in the first symbol after the end of the PDCCH reception. + +NOTE 3a: A PDCCH indicating activation of SPS, configured grant type 2, or configured sidelink grant of configured grant Type 2 is considered to indicate a new transmission. + +NOTE 3b: If the PDCCH reception includes two PDCCH candidates from corresponding search spaces, as described in clause 10.1 in 38.213, start or restart *drx-InactivityTimer* for this DRX group in the first symbol after the end of the PDCCH candidate that ends later in time. + +- 2> if a HARQ process receives downlink feedback information and acknowledgement is indicated: + - 3> stop the *drx-RetransmissionTimerUL* for the corresponding HARQ process. +- 1> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6], clause 10.3; and +- 1> if the current symbol n occurs within *drx-onDurationTimer* duration; and +- 1> if *drx-onDurationTimer* associated with the current DRX cycle is not started as specified in this clause: + - 2> if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and + - 2> if *allowCSI-SRS-Tx-MulticastDRX-Active* is not configured, or if *cfr-ConfigMulticast* is not configured for any of the active BWP(s) of the Serving Cell(s), or if all multicast DRXes would not be in Active Time considering multicast assignments/DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions are configured with multicast DRX: + - 3> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7]; + - 3> not report semi-persistent CSI configured on PUSCH; + - 3> not report semi-persistent CSI on PUCCH; + - 3> if *ps-TransmitPeriodicL1-RSRP* is not configured with value *true*: + - 4> not report periodic CSI that is L1-RSRP on PUCCH. + - 3> if *ps-TransmitOtherPeriodicCSI* is not configured with value *true*: + - 4> not report periodic CSI that is not L1-RSRP on PUCCH. +- 1> else: + - 2> in current symbol n, if a DRX group would not be in Active Time considering grants/assignments scheduled on Serving Cell(s) in this DRX group and DRX Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and + - 2> if *allowCSI-SRS-Tx-MulticastDRX-Active* is not configured, or if *cfr-ConfigMulticast* is not configured for any of the active BWP(s) of the Serving Cell(s), or, in current symbol n, if all multicast DRXes corresponding to the DRX group would not be in Active Time considering multicast assignments/DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions corresponding to the DRX group are configured with multicast DRX: + - 3> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7] in this DRX group; + - 3> not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group. +- 2> if CSI masking (*csi-Mask*) is setup by upper layers: + - 3> in current symbol n, if *drx-onDurationTimer* of a DRX group would not be running considering grants/assignments scheduled on Serving Cell(s) in this DRX group and DRX Command MAC CE/Long DRX Command MAC CE received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and + - 3> if *allowCSI-SRS-Tx-MulticastDRX-Active* is not configured, or if *cfr-ConfigMulticast* is not configured for any of the active BWP(s) of the Serving Cell(s), or, in current symbol n, if *drx-onDurationTimerPTM(s)* of all multicast DRXes corresponding to the DRX group would not be running considering DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions corresponding to the DRX group are configured with multicast DRX: + +4> not report CSI on PUCCH in this DRX group. + +NOTE 4: If a UE multiplexes a CSI configured on PUCCH with other overlapping UCI(s) according to the procedure specified in TS 38.213 [6] clause 9.2.5 and this CSI multiplexed with other UCI(s) would be reported on a PUCCH resource either outside DRX Active Time of the DRX group in which this PUCCH is configured or outside the on-duration period of the DRX group in which this PUCCH is configured if CSI masking is setup by upper layers, it is up to UE implementation whether to report this CSI multiplexed with other UCI(s). + +The MAC entity shall ensure no rounding error is generated when performing the modulus operation with *drx-NonIntegerShortCycle* or *drx-NonIntegerLongCycle* as the divisor. + +Regardless of whether the MAC entity is monitoring PDCCH or not on the Serving Cells in a DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS defined in TS 38.214 [7] on the Serving Cells in the DRX group when such is expected. + +The MAC entity needs not to monitor the PDCCH if it is not a complete PDCCH occasion (e.g. the Active Time starts or ends in the middle of a PDCCH occasion). + +## 5.7a Discontinuous Reception (DRX) for MBS Broadcast + +For MBS broadcast, the MAC entity may be configured by RRC with a DRX functionality per G-RNTI that controls the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s) as specified in TS 38.331 [5]. When in RRC\_IDLE or RRC\_INACTIVE or RRC\_CONNECTED, if broadcast DRX is configured for a G-RNTI, the MAC entity is allowed to monitor the PDCCH for this G-RNTI discontinuously using the broadcast DRX operation specified in this clause; otherwise the MAC entity monitors each PDCCH for this G-RNTI as specified in TS 38.213 [6]. The broadcast DRX operation specified in this clause is performed independently for each G-RNTI and independently from the DRX operation specified in clauses 5.7 and 5.7b. + +RRC controls broadcast DRX operation by configuring the following parameters: + +- *drx-onDurationTimerPTM*: the duration at the beginning of a DRX cycle; +- *drx-SlotOffsetPTM*: the delay before starting the *drx-onDurationTimerPTM*; +- *drx-InactivityTimerPTM*: the duration after the PDCCH occasion in which a PDCCH indicates a new DL broadcast transmission for the MAC entity; +- *drx-LongCycleStartOffsetPTM*: the long DRX cycle *drx-LongCycle-PTM* and *drx-StartOffset-PTM* which defines the subframe where the DRX cycle starts. + +When broadcast DRX is configured for a G-RNTI, the Active Time includes the time while: + +- *drx-onDurationTimerPTM* or *drx-InactivityTimerPTM* for this G-RNTI is running. + +When broadcast DRX is configured for a G-RNTI, the MAC entity shall for this G-RNTI: + +- 1> if $[(\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{drx-LongCycle-PTM}) = \text{drx-StartOffset-PTM}$ : + - 2> start *drx-onDurationTimerPTM* after *drx-SlotOffsetPTM* from the beginning of the subframe. +- 1> if the MAC entity is in Active Time for this G-RNTI: + - 2> monitor the PDCCH for this G-RNTI as specified in TS 38.213 [6]; + - 2> if the PDCCH indicates a DL transmission for MBS broadcast: + - 3> start or restart *drx-InactivityTimerPTM* in the first symbol after the end of the PDCCH reception. + +NOTE: If a cell is configured for MBS broadcast reception, the SFN of this cell is used to calculate the DRX duration of MBS broadcast on this cell. + +## 5.7b Discontinuous Reception (DRX) for MBS Multicast + +For MBS multicast, the MAC entity may be configured by RRC with a DRX functionality per G-RNTI or per G-CS-RNTI that controls the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s) and G-CS-RNTI(s) as specified in TS 38.331 [5]. When in RRC\_CONNECTED, if multicast DRX is configured for a G-RNTI or G-CS-RNTI, the MAC entity is allowed to monitor the PDCCH for this G-RNTI or G-CS-RNTI discontinuously using the multicast DRX operation specified in this clause; otherwise the MAC entity monitors the PDCCH for this G-RNTI or G-CS-RNTI as specified in TS 38.213 [6]. When in RRC\_INACTIVE, if the UE is configured to receive multicast in RRC\_INACTIVE and multicast DRX is configured for a G-RNTI, the MAC entity is allowed to monitor the PDCCH for this G-RNTI discontinuously using the multicast DRX operation specified in this clause; otherwise the MAC entity monitors the PDCCH for this G-RNTI as specified in TS 38.213 [6]. The multicast DRX operation specified in this clause is performed independently for each G-RNTI or G-CS-RNTI and independently from the DRX operation specified in clauses 5.7 and 5.7a. + +RRC controls multicast DRX operation per G-RNTI or per G-CS-RNTI by configuring the following parameters: + +- *drx-onDurationTimerPTM*: the duration at the beginning of a DRX cycle; +- *drx-SlotOffsetPTM*: the delay before starting the *drx-onDurationTimerPTM*; +- *drx-InactivityTimerPTM*: the duration after the PDCCH occasion in which a PDCCH indicates a new DL multicast transmission for the MAC entity; +- *drx-LongCycleStartOffsetPTM*: the long DRX cycle *drx-LongCycle-PTM* and *drx-StartOffset-PTM* which defines the subframe where the long DRX cycle starts; +- *drx-RetransmissionTimerDL-PTM* (per DL HARQ process for MBS multicast): the maximum duration until a DL multicast retransmission is received; +- *drx-HARQ-RTT-TimerDL-PTM* (per DL HARQ process for MBS multicast): the minimum duration before a DL multicast assignment for HARQ retransmission is expected by the MAC entity. + +When multicast DRX is configured for a G-RNTI or G-CS-RNTI, the Active Time includes the time while: + +- *drx-onDurationTimerPTM* or *drx-InactivityTimerPTM* or *drx-RetransmissionTimerDL-PTM* for this G-RNTI or G-CS-RNTI is running. + +When multicast DRX is not configured for a G-RNTI or G-CS-RNTI, and the *cfr-ConfigMulticast* is configured for at least one of the active BWP(s) of the Serving Cell(s), and unicast DRX is configured, the MAC entity shall for this G-RNTI or G-CS-RNTI: + +- 1> monitor the PDCCH as specified in TS 38.213 [6]; +- 1> if the PDCCH indicates a DL multicast transmission; or +- 1> if a MAC PDU is received in a configured downlink multicast assignment: + - 2> stop the *drx-RetransmissionTimerDL* for the corresponding HARQ process. +- 1> if the PDCCH addressed to G-RNTI indicates a DL multicast transmission; or +- 1> if the PDCCH addressed to G-CS-RNTI indicates a DL multicast transmission and CS-RNTI is configured; or +- 1> if a MAC PDU is received in a configured downlink multicast assignment and CS-RNTI is configured: + - 2> if the first HARQ-ACK reporting mode (i.e. ack-nack) is used as specified in TS 38.213 [6]; and + - 2> if HARQ feedback is enabled: + - 3> start the *drx-HARQ-RTT-TimerDL* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. + +When multicast DRX is configured for a G-RNTI or G-CS-RNTI, and the *cfr-ConfigMulticast* is configured for at least one of the active BWP(s) of the Serving Cell(s), the MAC entity shall for this G-RNTI or G-CS-RNTI: + +- 1> if a MAC PDU is received in a configured downlink multicast assignment: + +- 2> if HARQ feedback is enabled: + - 3> start the *drx-HARQ-RTT-TimerDL-PTM* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback; + - 3> if the first HARQ-ACK reporting mode (i.e. ack-nack) is used as specified in TS 38.213 [6]; and + - 3> if CS-RNTI is configured: + - 4> start the *drx-HARQ-RTT-TimerDL* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. +- 2> else if *drx-HARQ-RTT-TimerDL-PTM* is configured: + - 3> start the *drx-HARQ-RTT-TimerDL-PTM* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback that would be performed if HARQ feedback were enabled. +- 2> stop the *drx-RetransmissionTimerDL-PTM* for the corresponding HARQ process; +- 2> stop the *drx-RetransmissionTimerDL* for the corresponding HARQ process. +- 1> if a *drx-HARQ-RTT-TimerDL-PTM* expires: + - 2> if the data of the corresponding HARQ process was not successfully decoded: + - 3> start the *drx-RetransmissionTimerDL-PTM* for the corresponding HARQ process in the first symbol after the expiry of *drx-HARQ-RTT-TimerDL-PTM*. +- 1> if a DRX Command MAC CE indicated by PDCCH addressed to a G-RNTI or G-CS-RNTI, or by a configured downlink multicast assignment is received: + - 2> stop *drx-onDurationTimerPTM* of the DRX for this G-RNTI or G-CS-RNTI, or the corresponding G-CS-RNTI; + - 2> stop *drx-InactivityTimerPTM* of the DRX for this G-RNTI or G-CS-RNTI, or the corresponding G-CS-RNTI. +- 1> if $[(\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{drx-LongCycle-PTM}) = \text{drx-StartOffset-PTM}$ : + - 2> start *drx-onDurationTimerPTM* after *drx-SlotOffsetPTM* from the beginning of the subframe. +- 1> if the MAC entity is in Active Time for this G-RNTI or G-CS-RNTI: + - 2> monitor the PDCCH for this G-RNTI or G-CS-RNTI as specified in TS 38.213 [6]; + - 2> if the PDCCH indicates a DL multicast transmission: + - 3> if HARQ feedback is enabled: + - 4> start the *drx-HARQ-RTT-TimerDL-PTM* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback; + - 4> if the first HARQ-ACK reporting mode (i.e. ack-nack) is used as specified in TS 38.213 [6]: + - 5> if the PDCCH addressed to G-RNTI indicates a DL multicast transmission; or + - 5> if the PDCCH addressed to G-CS-RNTI indicates a DL multicast transmission and CS-RNTI is configured: + - 6> start the *drx-HARQ-RTT-TimerDL* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. + - 3> else if *drx-HARQ-RTT-TimerDL-PTM* is configured in RRC\_INACTIVE, and the UE supports *ptm-RetransmissionInactive*: + - 4> start the *drx-HARQ-RTT-TimerDL-PTM* for the corresponding HARQ process in the first symbol after the end of the corresponding multicast transmission. + +3> else if *drx-HARQ-RTT-TimerDL-PTM* is configured: + +4> start the *drx-HARQ-RTT-TimerDL-PTM* for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback that would be performed if HARQ feedback were enabled. + +3> stop the *drx-RetransmissionTimerDL-PTM* for the corresponding HARQ process; + +3> stop the *drx-RetransmissionTimerDL* for the corresponding HARQ process. + +2> if the PDCCH indicates a new multicast transmission for this G-RNTI or G-CS-RNTI: + +3> start or restart *drx-InactivityTimerPTM* in the first symbol after the end of the PDCCH reception. + +NOTE 1: A PDCCH indicating activation of multicast SPS is considered to indicate a new transmission. + +NOTE 2: The UE may start the *drx-HARQ-RTT-TimerDL* after receiving a PTM transmission only if *ptp-Retx-Multicast* or *ptp-Retx-SPS-Multicast* was included in the *UECapabilityInformation* message to network. + +The MAC entity needs not to monitor the PDCCH for a G-RNTI or a G-CS-RNTI if it is not a complete PDCCH occasion (e.g. the Active Time for a G-RNTI or a G-CS-RNTI starts or ends in the middle of a PDCCH occasion). + +## 5.8 Transmission and reception without dynamic scheduling + +### 5.8.1 Downlink + +Semi-Persistent Scheduling (SPS) is only applicable for UEs in RRC\_CONNECTED and is configured by RRC for a Serving Cell per BWP. Multiple assignments can be active simultaneously in the same BWP. Activation and deactivation of the DL SPS are independent among the Serving Cells. + +For the DL SPS, a DL assignment is provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS activation or deactivation. + +RRC configures the following parameters when the SPS is configured: + +- *cs-RNTI*: CS-RNTI for activation, deactivation, and retransmission; +- *nrofHARQ-Processes*: the number of configured HARQ processes for SPS; +- *harq-ProcID-Offset*: Offset of HARQ process for SPS; +- *periodicity*: periodicity of configured downlink assignment for SPS. + +When the SPS is released by upper layers, all the corresponding configurations shall be released. + +After a downlink assignment is configured for SPS, the MAC entity shall consider sequentially that the Nth downlink assignment occurs in the slot for which: + +$$\begin{aligned} & (\text{numberOfSlotsPerFrame} \times \text{SFN} + \text{slot number in the frame}) = \\ & [(\text{numberOfSlotsPerFrame} \times \text{SFN}_{\text{start time}} + \text{slot}_{\text{start time}}) + N \times \text{periodicity} \times \text{numberOfSlotsPerFrame} / 10] \\ & \text{modulo } (1024 \times \text{numberOfSlotsPerFrame}) \end{aligned}$$ + +where $\text{SFN}_{\text{start time}}$ and $\text{slot}_{\text{start time}}$ are the SFN and slot, respectively, of the first transmission of PDSCH where the configured downlink assignment was (re-)initialised. + +NOTE: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to calculate the occurrences of configured downlink assignments. + +### 5.8.1a Downlink for Multicast + +MBS Semi-Persistent Scheduling (SPS) is configured by RRC on one Serving Cell per BWP. Multiple assignments can be active simultaneously in the same BWP. + +For the DL MBS SPS, a DL assignment is provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS activation or deactivation. + +RRC configures the following parameters when the MBS SPS is configured: + +- *cs-RNTI*: CS-RNTI for MBS SPS deactivation, PTP for PTM retransmission if configured; +- *g-cs-RNTI*: G-CS-RNTI for activation, deactivation, and retransmission; +- *nrofHARQ-Processes*: the number of configured HARQ processes for MBS SPS; +- *harq-ProcID-Offset*: Offset of HARQ process for MBS SPS; +- *periodicity*: periodicity of configured downlink assignment for MBS SPS. + +When the MBS SPS is released by upper layers, all the corresponding configurations shall be released. + +After a downlink assignment is configured for MBS SPS, the MAC entity shall consider sequentially that the Nth downlink assignment occurs in the slot for which: + +$$\begin{aligned} & (\text{numberOfSlotsPerFrame} \times \text{SFN} + \text{slot number in the frame}) = \\ & [(\text{numberOfSlotsPerFrame} \times \text{SFN}_{\text{start time}} + \text{slot}_{\text{start time}}) + N \times \text{periodicity} \times \text{numberOfSlotsPerFrame} / 10] \\ & \text{modulo } (1024 \times \text{numberOfSlotsPerFrame}) \end{aligned}$$ + +where $\text{SFN}_{\text{start time}}$ and $\text{slot}_{\text{start time}}$ are the SFN and slot, respectively, of the first transmission of PDSCH where the configured downlink assignment was (re-)initialised. + +## 5.8.2 Uplink + +There are two types of transmission without dynamic grant: + +- configured grant Type 1 where an uplink grant is provided by RRC, and stored as configured uplink grant; +- configured grant Type 2 where an uplink grant is provided by PDCCH, and stored or cleared as configured uplink grant based on L1 signalling indicating configured uplink grant activation or deactivation. + +Type 1 and Type 2 are configured by RRC for a Serving Cell per BWP. Multiple configurations can be active simultaneously in the same BWP. For Type 2, activation and deactivation are independent among the Serving Cells. For the same BWP, the MAC entity can be configured with both Type 1 and Type 2. + +A multi-PUSCH configured grant has multiple consecutive configured uplink grants within a *periodicity*. Both Type 1 and Type 2 can be configured for a multi-PUSCH configured grant by RRC. + +Only configured grant Type 1 can be configured for CG-SDT. CG-SDT can only be configured on initial BWP. + +RRC configures the following parameters when the configured grant Type 1 is configured: + +- *cs-RNTI*: CS-RNTI for retransmission; +- *cg-SDT-CS-RNTI*: CS-RNTI for CG-SDT retransmission; +- *cg-SDT-RSRP-ThresholdSSB*: an RSRP threshold configured for SSB selection for CG-SDT; +- *rach-less-RSRP-ThresholdSSB*: an RSRP threshold configured for SSB selection for RACH-less handover; +- *periodicity*: periodicity of the configured grant Type 1; +- *timeDomainOffset*: Offset of a resource with respect to $\text{SFN} = \text{timeReferenceSFN}$ in time domain; +- *timeDomainAllocation*: Allocation of configured uplink grant in time domain which contains *startSymbolAndLength* (i.e. *SLIV* in TS 38.214 [7]) or *startSymbol* (i.e. *S* in TS 38.214 [7]); +- *nrofHARQ-Processes*: the number of HARQ processes for configured grant; +- *harq-ProcID-Offset*: offset of HARQ process for configured grant configured with *cg-RetransmissionTimer* for operation with shared spectrum channel access; + +- *harq-ProcID-Offset2*: offset of HARQ process for configured grant not configured with *cg-RetransmissionTimer*; +- *timeReferenceSFN*: SFN used for determination of the offset of a resource in time domain. The UE uses the closest SFN with the indicated number preceding the reception of the configured grant configuration; +- *timeReferenceH-SFN*: H-SFN used for determination of the offset of a resource in time domain. The UE uses the closest H-SFN with the indicated number preceding the reception of the configured grant configuration. + +RRc configures the following parameters when the configured grant Type 2 is configured: + +- *cs-RNTI*: CS-RNTI for activation, deactivation, and retransmission; +- *periodicity*: periodicity of the configured grant Type 2; +- *nrofHARQ-Processes*: the number of HARQ processes for configured grant; +- *harq-ProcID-Offset*: offset of HARQ process for configured grant configured with *cg-RetransmissionTimer* for operation with shared spectrum channel access; +- *harq-ProcID-Offset2*: offset of HARQ process for configured grant not configured with *cg-RetransmissionTimer*. + +RRc configures the following parameter when retransmissions on configured uplink grant is configured: + +- *cg-RetransmissionTimer*: the duration after a configured grant (re)transmission of a HARQ process when the UE shall not autonomously retransmit that HARQ process; +- *cg-SDT-RetransmissionTimer*: the duration after a configured grant (re)transmission of a HARQ process of the initial CG-SDT transmission with CCCH message when the UE shall not autonomously retransmit the HARQ process; +- *cg-LTM-RetransmissionTimer*: the duration after a configured grant (re)transmission of a HARQ process of the initial transmission at LTM cell switch when the UE shall not autonomously initiate a retransmission on the HARQ process; +- *cg-RACH-less-RetransmissionTimer*: the duration after a configured grant (re)transmission of a HARQ process of the initial transmission of RACH-less handover when the UE shall not autonomously retransmit the HARQ process. + +RRc configures the following additional parameter for a multi-PUSCH configured grant: + +- *nrofSlotsInCG-Period*: the number of configured uplink grants in a *periodicity* of a multi-PUSCH configured grant. + +For a configured uplink grant, the MAC entity shall: + +- 1> if the configured uplink grant is associated with a multi-PUSCH configured grant: + - 2> if configured uplink grant has not been indicated to the lower layers as to be unused for PUSCH transmission; and + - 2> if the configured uplink grant meets the validity conditions specified in the clause 6.1 in TS 38.214 [7]: + - 3> consider the configured uplink grant available for use; +- 1> else if the configured uplink grant has not been indicated to lower layers as to be unused for PUSCH transmission: + - 2> consider the configured uplink grant available for use. + +The MAC entity determines if a configured uplink grant is going to be used for PUSCH transmission or not by considering the amount of buffered data that can be transmitted on the available occasions of the associated configured grant and other available UL-SCH resources. Upon this determination, the MAC entity sends an indication to the lower layers regarding this decision, for use in the procedure for reporting UTO-UCI (as specified in clause 9.3 in TS 38.213 [6]). + +Upon configuration of a configured grant Type 1 for a BWP of a Serving Cell by upper layers, the MAC entity shall: + +- 1> store the uplink grant provided by upper layers as a configured uplink grant for the indicated BWP of the Serving Cell; +- 1> initialise or re-initialise the configured uplink grant to start in the symbol according to *timeDomainOffset*, *timeReferenceSFN*, and *S* (derived from *SLIV* or provided by *startSymbol* as specified in TS 38.214 [7]), and to reoccur with *periodicity*. + +After an uplink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the configured uplink grant, or the first configured uplink grant in a multi-PUSCH configured grant, in the $N^{\text{th}}$ ( $N \geq 0$ ) *periodicity* occurs in the symbol for which: + +- if *cg-SDT-PeriodicityExt* (as defined in TS 38.331 [5]) is not configured: + +$$\begin{aligned} & [(SFN \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot}) \\ & + (\text{slot number in the frame} \times \text{numberOfSymbolsPerSlot}) + \text{symbol number in the slot}] = \\ & (\text{timeReferenceSFN} \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot} \\ & + \text{timeDomainOffset} \times \text{numberOfSymbolsPerSlot} + S + N \times \text{periodicity}) \\ & \text{modulo } (1024 \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot}) \end{aligned}$$ + +- else: + +$$\begin{aligned} & [(H-SFN \times \text{numberOfSFNperH-SFN} + SFN) \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot} \\ & + (\text{slot number in the frame} \times \text{numberOfSymbolsPerSlot}) + \text{symbol number in the slot}] = \\ & ((\text{timeReferenceH-SFN} \times \text{numberOfSFNperH-SFN} + \text{timeReferenceSFN}) \\ & \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot} \\ & + \text{timeDomainOffset} \times \text{numberOfSymbolsPerSlot} + S + N \times \text{periodicity}) \\ & \text{modulo } (1024 \times 1024 \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot}) \end{aligned}$$ + +For a multi-PUSCH configured grant Type 1, the $M^{\text{th}}$ ( $1 < M \leq \text{nrofSlotsInCG-Period}$ ) configured uplink grant within a *periodicity* occurs $(M-1) \times \text{numberOfSymbolsPerSlot}$ symbols after the symbol in which the first configured uplink grant in that *periodicity* occurs. + +For an uplink grant configured for configured grant Type 1 for CG-SDT on the selected uplink carrier as in clause 5.27, when CG-SDT is triggered and not terminated, for each configured uplink grant valid according to TS 38.214 [7] for which the above formula is satisfied, the MAC entity shall: + +- 1> if, after initial transmission for CG-SDT with CCCH message has been performed according to clause 5.4.1, PDCCH addressed to the MAC entity's C-RNTI has not been received: + - 2> if the SSB corresponding to the configured UL grant has the same SSB index as the SSB selected for initial transmission for CG-SDT with CCCH message (i.e., retransmission of initial transmission of CG-SDT): + - 3> select this SSB; + - 3> indicate the SSB index corresponding to the configured uplink grant to the lower layer; + - 3> consider this configured uplink grant as valid. + - 1> else if at least one SSB configured for CG-SDT with SS-RSRP above *cg-SDT-RSRP-ThresholdSSB* is available: + - 2> if at least one SSB corresponding to the configured uplink grant with SS-RSRP above the *cg-SDT-RSRP-ThresholdSSB* is available: + - 3> if this is the initial transmission of CG-SDT with CCCH message after the CG-SDT procedure is initiated as in clause 5.27 (i.e., initial transmission for CG-SDT): + - 4> select an SSB with SS-RSRP above *cg-SDT-RSRP-ThresholdSSB* amongst the SSB(s) associated with the configured uplink grant. + - 3> else if PDCCH addressed to C-RNTI has been received after the initial transmission of CG-SDT with CCCH message (i.e., subsequent new transmission for CG-SDT): + - 4> if SS-RSRP of the SSB selected for the previous transmission for CG-SDT is above *cg-SDT-RSRP-ThresholdSSB* and this SSB is associated with this configured uplink grant: + +- 5> select this SSB. +- 4> else if SS-RSRP of the SSB selected for the previous transmission for CG-SDT is not above *cgsdt-RSRP-ThresholdSSB*: + - 5> select an SSB with SS-RSRP above *cgsdt-RSRP-ThresholdSSB* amongst the SSB(s) associated with the configured uplink grant. +- 3> if SSB is selected above: + - 4> indicate the SSB index to the lower layer; + - 4> consider this configured uplink grant as valid. +- 1> else: + - 2> consider this configured uplink grant as not valid. + - 2> if PDCCH addressed to C-RNTI after the initial transmission of the CG-SDT with CCCH message has been received: + - 3> if there is data available for transmission for at least one RB configured for SDT: + - 4> initiate Random Access procedure in clause 5.1. + +NOTE 1: When the UE determines if there is an SSB with SS-RSRP above *cgsdt-RSRP-ThresholdSSB*, the UE uses the latest unfiltered L1-RSRP measurement. + +For an uplink grant configured for configured grant Type 1 for LTM cell switch, when there is an on-going RACH-less LTM cell switch procedure, for each configured uplink grant valid according to TS 38.214 [7] for which the above formula is satisfied, the MAC entity shall: + +- 1> if an SSB corresponding to the configured UL grant has the same SSB index as the SSB associated with the TCI state indicated by LTM Cell Switch Command MAC CE, as specified in clause 5.18.35: + - 2> select the SSB associated with the TCI state indicated by LTM Cell Switch Command MAC CE. + - 2> indicate the SSB index to the lower layer; + - 2> consider this configured uplink grant as valid. +- 1> else: + - 2> consider this configured uplink grant as not valid. + +For an uplink grant configured for configured grant Type 1 for RACH-less handover, when RACH-less handover is triggered and not terminated, for each configured uplink grant valid according to TS 38.214 [7] for which the above formula is satisfied, the MAC entity shall: + +- 1> if, after the initial transmission of RACH-less handover has been performed according to clause 5.4.1 and 5.33, PDCCH addressed to the MAC entity's C-RNTI has not been received: + - 2> if the SSB corresponding to the configured UL grant has the same SSB index as the SSB selected for the initial transmission of RACH-less handover (i.e., retransmission of initial transmission of RACH-less handover): + - 3> select this SSB; + - 3> indicate the SSB index corresponding to the configured uplink grant to the lower layer; + - 3> consider this configured uplink grant as valid. +- 1> else if at least one SSB corresponding to the configured uplink grant with SS-RSRP above *rach-less-RSRP-ThresholdSSB* is available: + - 2> select an SSB with SS-RSRP above *rach-less-RSRP-ThresholdSSB* amongst the SSB(s) associated with the configured uplink grant; + +- 2> indicate the selected SSB index to the lower layer; + - 2> consider this configured uplink grant as valid. +- 1> else: +- 2> consider this configured uplink grant as not valid; + - 2> initiate Random Access procedure in clause 5.1. + +NOTE 1A: When the UE determines if there is an SSB with SS-RSRP above *rach-less-RSRP-ThresholdSSB*, the UE uses the latest unfiltered L1-RSRP measurement. + +After an uplink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the configured uplink grant, or the first configured uplink grant in a multi-PUSCH configured grant, in the Nth (N ≥ 0) *periodicity* occurs in the symbol for which: + +$$\begin{aligned} & [(SFN \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot}) \\ & + (\text{slot number in the frame} \times \text{numberOfSymbolsPerSlot}) + \text{symbol number in the slot}] = \\ & [(SFN_{\text{start time}} \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot} \\ & + \text{slot}_{\text{start time}} \times \text{numberOfSymbolsPerSlot} + \text{symbol}_{\text{start time}}) + N \times \text{periodicity}] \\ & \text{modulo } (1024 \times \text{numberOfSlotsPerFrame} \times \text{numberOfSymbolsPerSlot}) \end{aligned}$$ + +where SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, of the first transmission opportunity of PUSCH where the configured uplink grant was (re-)initialised. + +For a multi-PUSCH configured grant Type 2, the Mth (1 < M ≤ *nrofSlotsInCG-Period*) configured uplink grant within the same *periodicity* occurs (M-1) × *numberOfSymbolsPerSlot* symbols after the symbol in which the first configured uplink grant in that *periodicity* occurs. + +If *cgr-nrofPUSCH-InSlot* or *cgr-nrofSlots* is configured for a configured grant Type 1 or Type 2, the MAC entity shall consider the uplink grants occur in those additional PUSCH allocations as specified in clause 6.1.2.3 of TS 38.214 [7]. + +NOTE 2: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to calculate the occurrences of configured uplink grants. + +When the configured uplink grant is released by upper layers, all the corresponding configurations shall be released and all corresponding uplink grants shall be cleared. + +The MAC entity shall: + +- 1> if at least one configured uplink grant confirmation has been triggered and not cancelled; and +- 1> if the MAC entity has UL resources allocated for new transmission: + - 2> if, in this MAC entity, at least one configured uplink grant is configured by *configuredGrantConfigToAddModList*: + - 3> instruct the Multiplexing and Assembly procedure to generate a Multiple Entry Configured Grant Confirmation MAC CE as defined in clause 6.1.3.31. + - 2> else: + - 3> instruct the Multiplexing and Assembly procedure to generate a Configured Grant Confirmation MAC CE as defined in clause 6.1.3.7. + - 2> cancel all triggered configured uplink grant confirmation(s). + +For a configured grant Type 2, the MAC entity shall clear the configured uplink grant(s) immediately after first transmission of Configured Grant Confirmation MAC CE or Multiple Entry Configured Grant Confirmation MAC CE which confirms the configured uplink grant deactivation. + +Retransmissions use: + +- repetition of configured uplink grants; or +- received uplink grants addressed to CS-RNTI; or + +- configured uplink grants with *cg-RetransmissionTimer*, *cg-LTM-RetransmissionTimer*, *cg-RACH-less-RetransmissionTimer* or *cg-SDT-RetransmissionTimer* configured. + +### 5.8.3 Sidelink + +There are two types of transmission without dynamic sidelink grant: + +- configured grant Type 1 where an sidelink grant is provided by RRC, and stored as configured sidelink grant; +- configured grant Type 2 where an sidelink grant is provided by PDCCH, and stored or cleared as configured sidelink grant based on L1 signalling indicating configured sidelink grant activation or deactivation. + +Type 1 and/or Type 2 are configured with a single BWP. Multiple configurations of up to 8 configured grants (including both Type 1 and Type 2, if configured) can be active simultaneously on the BWP. + +RRC configures the following parameters when the configured grant Type 1 is configured, as specified in TS 38.331 [5] or TS 36.331 [21]: + +- *sl-ConfigIndexCG*: the identifier of a configured grant for sidelink; +- *sl-CS-RNTI*: SL-CS-RNTI for retransmission; +- *sl-NrOfHARQ-Processes*: the number of HARQ processes for configured grant; +- *sl-PeriodCG*: periodicity of the configured grant Type 1; +- *sl-TimeOffsetCG-Type1*: Offset of a resource with respect to reference logical slot defined by *sl-TimeReferenceSFN-Type1* in time domain, referring to the number of logical slots in a resource pool; +- *sl-TimeResourceCG-Type1*: time resource location of the configured grant Type 1; +- *sl-CG-MaxTransNumList*: the maximum number of times that a TB can be transmitted using the configured grant; +- *sl-HARQ-ProcID-offset*: offset of HARQ process for configured grant Type 1; +- *sl-PRS-ResourceID*: SL-PRS configuration index for configured grant Type 1; +- *sl-TimeReferenceSFN-Type1*: SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the first logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration Type 1 as reference logical slot. If it is absent, the indicated reference SFN is zero. + +RRC configures the following parameters when the configured grant Type 2 is configured, as specified in TS 38.331 [5]: + +- *sl-ConfigIndexCG*: the identifier of a configured grant for sidelink; +- *sl-CS-RNTI*: SL-CS-RNTI for activation, deactivation, and retransmission; +- *sl-PRS-CS-RNTI*: SL-PRS-CS-RNTI for activation, and deactivation; +- *sl-NrOfHARQ-Processes*: the number of HARQ processes for configured grant; +- *sl-PeriodCG*: periodicity of the configured grant Type 2; +- *sl-CG-MaxTransNumList*: the maximum number of times that a TB can be transmitted using the configured grant; +- *sl-HARQ-ProcID-offset*: offset of HARQ process for configured grant Type 2. + +Upon configuration of a configured grant Type 1, the MAC entity shall for each configured sidelink grant: + +- 1> store the sidelink grant provided by RRC as a configured sidelink grant; + +- 1> initialise or re-initialise the configured sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) and SL-PRS transmission occasion(s) according to *sl-TimeOffsetCG-Type1* and *sl-TimeResourceCG-Type1*, and to reoccur with *sl-periodCG* for transmissions of multiple MAC PDUs and SL-PRS(s) according to clause 8.1.2 of TS 38.214 [7]. + +NOTE 1: If the MAC entity is configured with multiple configured sidelink grants, collision among the configured sidelink grants may occur. How to handle the collision is left to UE implementation. + +After a sidelink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the first slot of the Sth sidelink grant occurs in the logical slot for which: + +$$CURRENT\_slot = (sl-ReferenceSlotCG-Type1 + sl-TimeOffsetCG-Type1 + S \times PeriodicitySL) \text{ modulo } T'_{max}$$ + +where *CURRENT\_slot* refers to current logical slot in the associated resource pool, and *T'max* is the number of slots that belongs to the associated resource pool as defined in clause 8 of TS 38.214[7]. *sl-ReferenceSlotCG-Type1* refers to reference logical slot defined by *sl-TimeReferenceSFN-Type1*. + +After a sidelink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the first slot of Sth sidelink grant occurs in the logical slot for which: + +$$CURRENT\_slot = (sl-StartSlotCG-Type2 + S \times PeriodicitySL) \text{ modulo } T'_{max}$$ + +where *sl-StartSlotCG-Type2* refers to the logical slot of the first transmission opportunity of PSSCH or SL-PRS where the configured sidelink grant was (re)initialised. + +When a configured sidelink grant is released by RRC, all the corresponding configurations shall be released and all corresponding sidelink grants shall be cleared. + +The MAC entity shall: + +- 1> if the configured sidelink grant confirmation has been triggered and not cancelled; and +- 1> if the MAC entity has UL resources allocated for new transmission: + - 2> instruct the Multiplexing and Assembly procedure to generate a Sidelink Configured Grant Confirmation MAC CE as defined in clause 6.1.3.34; + - 2> cancel the triggered configured sidelink grant confirmation. + +For a configured grant Type 2, the MAC entity shall clear the corresponding configured sidelink grant immediately after first transmission of Sidelink Configured Grant Confirmation MAC CE triggered by the configured sidelink grant deactivation. + +## 5.9 Activation/Deactivation of SCells + +If the MAC entity is configured with one or more SCells, the network may activate and deactivate the configured SCells. Upon configuration of an SCell, the SCell is deactivated unless the parameter *sCellState* is set to *activated* for the SCell by upper layers. + +The configured SCell(s) is activated and deactivated by: + +- receiving the SCell Activation/Deactivation MAC CE described in clause 6.1.3.10; +- receiving the Enhanced SCell Activation/Deactivation MAC CE described in clause 6.1.3.55; +- configuring *sCellDeactivationTimer* timer per configured SCell (except the SCell configured with PUCCH, if any): the associated SCell is deactivated upon its expiry; +- configuring *sCellState* per configured SCell: if configured, the associated SCell is activated upon SCell configuration; +- receiving *scg-State*: the SCells of SCG are deactivated. + +The MAC entity shall for each configured SCell: + +- 1> if an SCell is configured with *sCellState* set to *activated* upon SCell configuration, or an SCell Activation/Deactivation MAC CE or an Enhanced SCell Activation/Deactivation MAC CE is received activating the SCell: + - 2> if the SCell was deactivated prior to receiving this Enhanced SCell Activation/Deactivation MAC CE and a TRS is indicated for this SCell: + - 3> indicate to lower layers the information regarding the TRS. + - 2> if the SCell was deactivated prior to receiving this SCell Activation/Deactivation MAC CE or this Enhanced SCell Activation/Deactivation MAC CE; or + - 2> if the SCell is configured with *sCellState* set to *activated* upon SCell configuration: + - 3> if *firstActiveDownlinkBWP-Id* is not set to dormant BWP: + - 4> activate the SCell according to the timing defined in TS 38.213 [6] for MAC CE activation and according to the timing defined in TS 38.133 [11] for direct SCell activation; i.e. apply normal SCell operation including: + - 5> SRS transmissions on the SCell; + - 5> CSI reporting for the SCell; + - 5> PDCCH monitoring on the SCell; + - 5> PDCCH monitoring for the SCell; + - 5> PUCCH transmissions on the SCell, if configured. + - 3> else (i.e. *firstActiveDownlinkBWP-Id* is set to dormant BWP): + - 4> stop the *bwp-InactivityTimer* of this Serving Cell, if running. + - 3> activate the DL BWP and UL BWP indicated by *firstActiveDownlinkBWP-Id* and *firstActiveUplinkBWP-Id* respectively. + - 2> start or restart the *sCellDeactivationTimer* associated with the SCell according to the timing defined in TS 38.213 [6] for MAC CE activation and according to the timing defined in TS 38.133 [11] for direct SCell activation; + - 2> if the active DL BWP is not the dormant BWP: + - 3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2; + - 3> trigger PHR according to clause 5.4.6. + - 1> else if an SCell Activation/Deactivation MAC CE or an Enhanced SCell Activation/Deactivation MAC CE is received deactivating the SCell; or + - 1> if the *sCellDeactivationTimer* associated with the activated SCell expires; or + - 1> if the SCG associated with the activated SCell is deactivated: + - 2> deactivate the SCell according to the timing defined in TS 38.213 [6]; + - 2> stop the *sCellDeactivationTimer* associated with the SCell; + - 2> stop the *bwp-InactivityTimer* associated with the SCell; + - 2> deactivate any active BWP associated with the SCell; + - 2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively; + +- 2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell; +- 2> suspend any configured uplink grant Type 1 associated with the SCell; +- 2> flush all HARQ buffers associated with the SCell; +- 2> cancel, if any, triggered consistent LBT failure for the SCell. +- 1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or +- 1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or +- 1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or +- 1> if a MAC PDU is received in a configured downlink assignment: + - 2> restart the *sCellDeactivationTimer* associated with the SCell. +- 1> if the SCell is deactivated: + - 2> not transmit SRS on the SCell; + - 2> not report CSI for the SCell; + - 2> not transmit on UL-SCH on the SCell; + - 2> not transmit on RACH on the SCell; + - 2> not monitor the PDCCH on the SCell; + - 2> not monitor the PDCCH for the SCell; + - 2> not transmit PUCCH on the SCell. + +When the measurement reporting for fast unknown SCell activation is configured by RRC, the MAC entity shall: + +- 1> if SCell Activation/Deactivation MAC CE or an Enhanced SCell Activation/Deactivation MAC CE is received activating the SCell(s): + - 2> if SCell(s) was deactivated prior to receiving this SCell Activation/Deactivation MAC CE or this Enhanced SCell Activation/Deactivation MAC CE: + - 3> indicate to upper layers SCell(s) activation indication. + +HARQ feedback for the MAC PDU containing SCell Activation/Deactivation MAC CE or Enhanced SCell Activation/Deactivation MAC CE shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation/deactivation in TS 38.133 [11]. + +When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted. + +## 5.10 Activation/Deactivation of PDCP duplication + +If one or more DRBs are configured with PDCP duplication, the network may activate and deactivate the PDCP duplication for all or a subset of associated RLC entities for the configured DRB(s). + +The PDCP duplication for the configured DRB(s) is activated and deactivated by: + +- receiving the Duplication Activation/Deactivation MAC CE described in clause 6.1.3.11; +- receiving the Duplication RLC Activation/Deactivation MAC CE described in clause 6.1.3.32; +- indication by RRC. + +The PDCP duplication for all or a subset of associated RLC entities for the configured DRB(s) is activated and deactivated by: + +- receiving the Duplication RLC Activation/Deactivation MAC CE described in clause 6.1.3.32; +- indication by RRC. + +The PDCP duplication for all associated RLC entities for the configured DRB(s) is activated by: + +- receiving an uplink grant addressed to CS-RNTI with NDI=1 for a logical channel associated with the DRB configured with *survivalTimeStateSupport*, described in clause 5.4.1. + +The MAC entity shall for each DRB configured with PDCP duplication: + +- 1> if a Duplication Activation/Deactivation MAC CE is received activating the PDCP duplication of the DRB: + - 2> indicate the activation of PDCP duplication of the DRB to upper layers. +- 1> if a Duplication Activation/Deactivation MAC CE is received deactivating the PDCP duplication of the DRB: + - 2> indicate the deactivation of PDCP duplication of the DRB to upper layers. +- 1> if a Duplication RLC Activation/Deactivation MAC CE is received activating PDCP duplication for associated RLC entities of a DRB configured with PDCP duplication: + - 2> indicate the activation of PDCP duplication for the indicated secondary RLC entity(ies) of the DRB to upper layers. +- 1> if a Duplication RLC Activation/Deactivation MAC CE is received deactivating PDCP duplication for associated RLC entities of a DRB configured with PDCP duplication: + - 2> indicate the deactivation of PDCP duplication for the indicated secondary RLC entity(ies) of the DRB to upper layers. +- 1> if activation of a PDCP duplication for all configured RLC entities is triggered for the DRB as specified in clause 5.4.1: + - 2> indicate the activation of PDCP duplication for all configured RLC entities of the DRB to upper layers. + +NOTE: How to identify "associated RLC entity" or equivalent entity in N3C interface for a DRB configured in Multi-path U2N N3C relay is out of scope of 3GPP. + +## 5.11 MAC reconfiguration + +When a reconfiguration of the MAC entity is requested by upper layers, the MAC entity shall: + +- 1> initialize the corresponding HARQ entity upon addition of an SCell; +- 1> remove the corresponding HARQ entity upon removal of an SCell; +- 1> apply the new value for timers when the timer is (re)started; +- 1> apply the new maximum parameter value when counters are initialized; +- 1> apply immediately the configurations received from upper layers for other parameters. + +## 5.12 MAC Reset + +If a reset of the MAC entity is requested by upper layers or the reset of the MAC entity is triggered due to SCG deactivation as defined in clause 5.29, the MAC entity shall: + +- 1> if the MAC reset is not due to SCG deactivation: + - 2> initialize *Bj* for each logical channel to zero; + +- 1> initialize *SBj* for each logical channel to zero if Sidelink resource allocation mode 1 is configured by RRC; +- 1> if upper layers indicate SCG deactivation and *bfd-and-RLM* with value *true* is configured for the deactivated SCG: + - 2> stop (if running) all timers except *beamFailureDetectionTimer* associated with PSCell and *timeAlignmentTimers*. +- 1> else: + - 2> stop (if running) all timers, except MBS broadcast DRX timers; + - 2> consider all *timeAlignmentTimers*, *inactivePosSRS-TimeAlignmentTimer*, and *cg-SDT-TimeAlignmentTimer*, if configured, as expired and perform the corresponding actions in clause 5.2; +- 1> set the NDIs for all uplink HARQ processes to the value 0; +- 1> sets the NDIs for all HARQ process IDs to the value 0 for monitoring PDCCH in Sidelink resource allocation mode 1; +- 1> stop, if any, ongoing Random Access procedure; +- 1> discard explicitly signalled contention-free Random Access Resources for 4-step RA type and 2-step RA type, if any; +- 1> flush Msg3 buffer; +- 1> flush MSGA buffer; +- 1> cancel, if any, triggered Scheduling Request procedure; +- 1> cancel, if any, triggered Buffer Status Reporting procedure; +- 1> cancel, if any, triggered Delay Status Reporting procedure; +- 1> cancel, if any, triggered Power Headroom Reporting procedure; +- 1> cancel, if any, triggered consistent LBT failure; +- 1> cancel, if any, triggered Sidelink consistent LBT failure; +- 1> cancel, if any, triggered BFR; +- 1> cancel, if any, triggered Sidelink Buffer Status Reporting procedure; +- 1> cancel, if any, triggered Pre-emptive Buffer Status Reporting procedure; +- 1> cancel, if any, triggered Timing Advance Reporting procedure; +- 1> cancel, if any, triggered Recommended bit rate query procedure; +- 1> cancel, if any, triggered Configured uplink grant confirmation; +- 1> cancel, if any, triggered configured sidelink grant confirmation; +- 1> clear, if any, configured sidelink grants; +- 1> cancel, if any, triggered Desired Guard Symbol query; +- 1> cancel, if any, triggered Positioning Measurement Gap Activation/Deactivation Request procedure; +- 1> cancel, if any, triggered SDT procedure; +- 1> cancel, if any, triggered IAB-MT Recommended Beam Indication query; +- 1> cancel, if any, triggered Desired DL TX Power Adjustment query; +- 1> cancel, if any, triggered Desired IAB-MT PSD range query; + +- 1> cancel, if any, triggered Case-6 Timing Request query; +- 1> flush the soft buffers for all DL HARQ processes, except for the DL HARQ process being used for MBS broadcast; +- 1> for each DL HARQ process, except for the DL HARQ process being used for MBS broadcast, consider the next received transmission for a TB as the very first transmission; +- 1> release, if any, Temporary C-RNTI; +- 1> clear, if any, Differential Koffset; +- 1> if upper layers indicate SCG deactivation and *bfd-and-RLM* with value *true* is not configured; or +- 1> if the MAC reset is not due to SCG deactivation: + - 2> reset all *BFI\_COUNTERs*; +- 1> reset all *LBT\_COUNTERs*. + +If a Sidelink specific reset of the MAC entity is requested for a PC5-RRC connection by upper layers, the MAC entity shall: + +- 1> flush the soft buffers for all Sidelink processes for all TB(s) associated to the PC5-RRC connection; +- 1> consider all Sidelink processes for all TB(s) associated to the PC5-RRC connection as unoccupied; +- 1> cancel, if any, triggered Scheduling Request procedure only associated to the PC5-RRC connection; +- 1> cancel, if any, triggered Sidelink Buffer Status Reporting procedure only associated to the PC5-RRC connection; +- 1> cancel, if any, triggered Sidelink CSI Reporting procedure associated to the PC5-RRC connection; +- 1> cancel, if any, triggered Sidelink DRX Command MAC CE associated to the PC5-RRC connection; +- 1> cancel, if any, triggered Sidelink IUC-Request transmission procedure associated to the PC5-RRC connection; +- 1> cancel, if any, triggered Sidelink IUC-Information Reporting procedure associated to the PC5-RRC connection; +- 1> stop (if running) all timers associated to the PC5-RRC connection; +- 1> reset the *numConsecutiveDTX* associated to the PC5-RRC connection; +- 1> initialize *SBj* for each logical channel associated to the PC5-RRC connection to zero. + +## 5.12a Void + +## 5.13 Handling of unknown, unforeseen and erroneous protocol data + +When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI or by the configured downlink assignment, containing a Reserved LCID or eLCID value, or an LCID or eLCID value the MAC Entity does not support, the MAC entity shall at least: + +- 1> discard the received subPDU and any remaining subPDUs in the MAC PDU. + +When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI or CS-RNTI, or by the configured downlink assignment, containing an LCID or eLCID value which is not configured, or an LCID or eLCID value associated with a suspended RB as specified in TS 38.331 [5], the MAC entity shall at least: + +- 1> discard the received subPDU. + +When a MAC entity receives a MAC PDU on SL-SCH containing a Reserved LCID value for broadcast or groupcast, or an LCID value which is not configured, the MAC entity shall: + +1> discard the received subPDU. + +When a MAC entity receives a MAC PDU on SL-SCH containing a Reserved LCID value for unicast, the MAC entity shall: + +1> discard the received subPDU and any remaining subPDUs in the MAC PDU. + +## 5.14 Handling of measurement gaps + +During an activated measurement gap, the MAC entity shall, on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by *measGapConfig* as specified in TS 38.331 [5]: + +1> not perform the transmission of HARQ feedback, SR, and CSI; + +1> not report SRS; + +1> not transmit on UL-SCH except for Msg3 or the MSGA payload as specified in clause 5.4.2.2; + +1> if the *ra-ResponseWindow* or the *ra-ContentionResolutionTimer* or the *msgB-ResponseWindow* is running, or if there is an ongoing RACH-less LTM cell switch, or if there is an ongoing RACH-less handover in a terrestrial network: + +2> monitor the PDCCH as specified in clauses 5.1.4 and 5.1.5. + +1> else: + +2> not monitor the PDCCH; + +2> not receive on DL-SCH. + +## 5.15 Bandwidth Part (BWP) operation + +### 5.15.1 Downlink and Uplink + +In addition to clause 12 of TS 38.213 [6], this clause specifies requirements on BWP operation. + +A Serving Cell may be configured with one or multiple BWPs, and the maximum number of BWP per Serving Cell is specified in TS 38.213 [6]. + +The BWP switching for a Serving Cell is used to activate an inactive BWP and deactivate an active BWP at a time. The BWP switching is controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the *bwp-InactivityTimer*, by RRC signalling, or by the MAC entity itself upon initiation of Random Access procedure or upon detection of consistent LBT failure on SpCell. Upon RRC (re-)configuration of *firstActiveDownlinkBWP-Id* and/or *firstActiveUplinkBWP-Id* for SpCell except for PSCell when SCG is deactivated (see clause 5.29) or activation of an SCell, the DL BWP and/or UL BWP indicated by *firstActiveDownlinkBWP-Id* and/or *firstActiveUplinkBWP-Id* respectively (as specified in TS 38.331 [5]) is active without receiving PDCCH indicating a downlink assignment or an uplink grant. Upon RRC (re-)configuration of *firstActiveDownlinkBWP-Id* for PSCell when SCG is deactivated, the DL BWP is switched to the *firstActiveDownlinkBWP-Id* as specified in TS 38.331 [5]. The active BWP for a Serving Cell is indicated by either RRC or PDCCH (as specified in TS 38.213 [6]). For unpaired spectrum, a DL BWP is paired with a UL BWP, and BWP switching is common for both UL and DL. + +For each SCell a dormant BWP may be configured with *dormantBWP-Id* by RRC signalling as described in TS 38.331 [5]. Entering or leaving dormant BWP for SCells is done by BWP switching per SCell or per dormancy SCell group based on instruction from PDCCH (as specified in TS 38.213 [6]). The dormancy SCell group configurations are configured by RRC signalling as described in TS 38.331 [5]. Upon reception of the PDCCH indicating leaving dormant BWP, the DL BWP indicated by *firstOutsideActiveTimeBWP-Id* or by *firstWithinActiveTimeBWP-Id* (as specified in TS 38.331 [5] and TS 38.213 [6]) is activated. Upon reception of the PDCCH indicating entering dormant BWP, the DL BWP indicated by *dormantBWP-Id* (as specified in TS 38.331 [5]) is activated. The dormant BWP configuration for SpCell or PUCCH SCell is not supported. + +BWP for SRS for positioning Tx frequency hopping can be configured for a Serving Cell in TS 38.331 [5]. BWP for SRS Tx frequency hopping is considered as activated when it is configured. BWP switching is not applicable for BWP for SRS Tx frequency hopping. + +For each activated Serving Cell configured with a BWP, the MAC entity shall: + +- 1> if a BWP is activated and the active DL BWP for the Serving Cell is not the dormant BWP and the Serving Cell is not the PSCell of deactivated SCG: + - 2> transmit on UL-SCH on the BWP; + - 2> transmit on RACH on the BWP, if PRACH occasions are configured; + - 2> monitor the PDCCH on the BWP; + - 2> transmit PUCCH on the BWP, if configured; + - 2> report CSI for the BWP; + - 2> transmit SRS on the BWP, if configured; + - 2> receive DL-SCH on the BWP; + - 2> (re-)initialize any suspended configured uplink grants of configured grant Type 1 on the active BWP according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2; + - 2> if *lbt-FailureRecoveryConfig* is configured: + - 3> stop the *lbt-FailureDetectionTimer*, if running; + - 3> set *LBT\_COUNTER* to 0; + - 3> monitor LBT failure indications from lower layers as specified in clause 5.21.2. +- 1> if a BWP is activated and the active DL BWP for the Serving Cell is dormant BWP: + - 2> stop the *bwp-InactivityTimer* of this Serving Cell, if running. + - 2> not monitor the PDCCH on the BWP; + - 2> not monitor the PDCCH for the BWP; + - 2> not receive DL-SCH on the BWP; + - 2> not report CSI on the BWP, report CSI except aperiodic CSI for the BWP; + - 2> not transmit SRS on the BWP; + - 2> not transmit on UL-SCH on the BWP; + - 2> not transmit on RACH on the BWP; + - 2> not transmit PUCCH on the BWP; + - 2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively; + - 2> suspend any configured uplink grant Type 1 associated with the SCell; + - 2> if configured, perform beam failure detection and beam failure recovery for the SCell if beam failure is detected. +- 1> if a BWP is deactivated or the Serving Cell is PSCell of deactivated SCG: + - 2> not transmit on UL-SCH on the BWP; + - 2> not transmit on RACH on the BWP; + +- 2> not monitor the PDCCH on the BWP; +- 2> not transmit PUCCH on the BWP; +- 2> not report CSI for the BWP; +- 2> not transmit SRS on the BWP; +- 2> not receive DL-SCH on the BWP; +- 2> clear any configured downlink assignment and configured uplink grant of configured grant Type 2 on the BWP; +- 2> suspend any configured uplink grant of configured grant Type 1 on the inactive BWP. + +Upon initiation of the Random Access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure as specified in clause 5.1.1, the MAC entity shall for the selected carrier of this Serving Cell: + +- 1> if PRACH occasions are not configured for the active UL BWP: + - 2> if the UE is an (e)RedCap UE; and + - 2> if *initialUplinkBWP-RedCap* is configured: + - 3> switch the active UL BWP to BWP indicated by *initialUplinkBWP-RedCap*. + - 2> else: + - 3> switch the active UL BWP to BWP indicated by *initialUplinkBWP*. + - 2> if the Serving Cell is an SpCell: + - 3> if the UE is an (e)RedCap UE; and + - 3> if *initialDownlinkBWP-RedCap* is configured: + - 4> switch the active DL BWP to BWP indicated by *initialDownlinkBWP-RedCap*. + - 3> else: + - 4> switch the active DL BWP to BWP indicated by *initialDownlinkBWP*. +- 1> else: + - 2> if the Serving Cell is an SpCell: + - 3> if the active DL BWP does not have the same *bwp-Id* as the active UL BWP: + - 4> switch the active DL BWP to the DL BWP with the same *bwp-Id* as the active UL BWP. + - 1> stop the *bwp-InactivityTimer* associated with the active DL BWP of this Serving Cell, if running. + - 1> if the Serving Cell is SCell: + - 2> stop the *bwp-InactivityTimer* associated with the active DL BWP of SpCell, if running. + - 1> perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving Cell. + +If the MAC entity receives a PDCCH for BWP switching of a Serving Cell, the MAC entity shall: + +- 1> if there is no ongoing Random Access procedure associated with this Serving Cell; or +- 1> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (as specified in clauses 5.1.4, 5.1.4a, and 5.1.5): + - 2> cancel, if any, triggered consistent LBT failure for this Serving Cell; + +2> perform BWP switching to a BWP indicated by the PDCCH. + +If the MAC entity receives a PDCCH for BWP switching for a Serving Cell(s) or a dormancy SCell group(s) while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, it is up to UE implementation whether to switch BWP or ignore the PDCCH for BWP switching, except for the PDCCH reception for BWP switching addressed to the C-RNTI for successful Random Access procedure completion (as specified in clauses 5.1.4, 5.1.4a, and 5.1.5) in which case the UE shall perform BWP switching to a BWP indicated by the PDCCH. Upon reception of the PDCCH for BWP switching other than successful contention resolution, if the MAC entity decides to perform BWP switching, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure after performing the BWP switching; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue with the ongoing Random Access procedure on the Serving Cell. + +Upon reception of RRC (re-)configuration for BWP switching for a Serving Cell while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure after performing the BWP switching. + +Upon reception of RRC (re-)configuration for BWP switching for a Serving Cell, cancel any triggered consistent LBT failure in this Serving Cell. + +The MAC entity shall for each activated Serving Cell configured with *bwp-InactivityTimer*: + +- 1> if the *defaultDownlinkBWP-Id* is configured, and the active DL BWP is not the BWP indicated by the *defaultDownlinkBWP-Id*, and the active DL BWP is not the BWP indicated by the *dormantBWP-Id* if configured; or +- 1> if the UE is neither a RedCap nor an eRedCap UE, and if the *defaultDownlinkBWP-Id* is not configured, and the active DL BWP is not the *initialDownlinkBWP*, and the active DL BWP is not the BWP indicated by the *dormantBWP-Id* if configured; or +- 1> if the UE is an (e)RedCap UE, and if the *defaultDownlinkBWP-Id* is not configured, and *initialDownlinkBWP-RedCap* is not configured, and the active DL BWP is not the *initialDownlinkBWP*; or +- 1> if the UE is an (e)RedCap UE, and if the *defaultDownlinkBWP-Id* is not configured, and *initialDownlinkBWP-RedCap* is configured, and the active DL BWP is not the *initialDownlinkBWP-RedCap*: + - 2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or + - 2> if a PDCCH addressed to G-RNTI or G-CS-RNTI configured for multicast indicating downlink assignment is received on the active BWP; or + - 2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or + - 2> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or + - 2> if a MAC PDU is received in a configured downlink assignment for unicast or MBS multicast: + - 3> if there is no ongoing Random Access procedure associated with this Serving Cell; or + - 3> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (as specified in clauses 5.1.4, 5.1.4a and 5.1.5): + - 4> start or restart the *bwp-InactivityTimer* associated with the active DL BWP. +- 2> if the *bwp-InactivityTimer* associated with the active DL BWP expires: + - 3> if the *defaultDownlinkBWP-Id* is configured: + - 4> perform BWP switching to a BWP indicated by the *defaultDownlinkBWP-Id*. + - 3> else: + - 4> if the UE is a (e)RedCap UE; and + +- 4> if *initialDownlinkBWP-RedCap* is configured: + - 5> perform BWP switching to the *initialDownlinkBWP-RedCap*. +- 4> else: + - 5> perform BWP switching to the *initialDownlinkBWP*. + +NOTE: If a Random Access procedure is initiated on an SCell, both this SCell and the SpCell are associated with this Random Access procedure. + +- 1> if a PDCCH for BWP switching is received, and the MAC entity switches the active DL BWP: + - 2> if the *defaultDownlinkBWP-Id* is configured, and the MAC entity switches to the DL BWP which is not indicated by the *defaultDownlinkBWP-Id* and is not indicated by the *dormantBWP-Id* if configured; or + - 2> if the UE is neither a RedCap nor an eRedCap UE, and if the *defaultDownlinkBWP-Id* is not configured, and the MAC entity switches to the DL BWP which is not the *initialDownlinkBWP* and is not indicated by the *dormantBWP-Id* if configured; or + - 2> if the UE is an (e)RedCap UE, and if the *defaultDownlinkBWP-Id* is not configured, and *initialDownlinkBWP-RedCap* is not configured, and the MAC entity switches to the DL BWP which is not the *initialDownlinkBWP*; or + - 2> if the UE is an (e)RedCap UE, and if the *defaultDownlinkBWP-Id* is not configured, and *initialDownlinkBWP-RedCap* is configured, and the MAC entity switches to the DL BWP which is not the *initialDownlinkBWP-RedCap*: + - 3> start or restart the *bwp-InactivityTimer* associated with the active DL BWP. + +Upon initiation of the Random Access procedure, after selection of the carrier for performing Random Access procedure as specified in clause 5.1.1, if the UE is an (e)RedCap UE in RRC\_IDLE or RRC\_INACTIVE mode, the MAC entity shall: + +- 1> if *initialUplinkBWP-RedCap* is configured for the selected carrier: + - 2> perform the Random Access procedure as specified in clause 5.1 by using the BWP configured by *initialUplinkBWP-RedCap*. +- 1> else: + - 2> perform the Random Access procedure as specified in clause 5.1 by using the BWP configured by *initialUplinkBWP*. +- 1> if *initialDownlinkBWP-RedCap* is configured: + - 2> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]) and the Random Access Resources for SI request have been explicitly provided by RRC, and if the selected carrier is SUL carrier: + - 3> monitor the PDCCH on the BWP configured by *initialDownlinkBWP*. + - 2> else: + - 3> monitor the PDCCH on the BWP configured by *initialDownlinkBWP-RedCap*. +- 1> else: + - 2> monitor the PDCCH on the BWP configured by *initialDownlinkBWP*. + +## 5.15.2 Sidelink + +In addition to clause 16 of TS 38.213 [6], this clause specifies requirements on BWP operation for sidelink. + +The MAC entity is configured with at most a single SL BWP per sidelink carrier where sidelink transmission and reception are performed. + +For a BWP, the MAC entity shall: + +- 1> if the BWP is activated: + - 2> transmit SL-BCH on the BWP, if configured; + - 2> transmit S-PSS and S-SSS on the BWP, if configured; + - 2> transmit PSCCH on the BWP; + - 2> transmit SL-PRS on the BWP; + - 2> transmit SL-SCH on the BWP; + - 2> receive PSFCH on the BWP, if configured; + - 2> receive S-PSS and S-SSS on the BWP, if configured; + - 2> receive SL-BCH on the BWP, if configured; + - 2> receive PSCCH on the BWP; + - 2> receive SL-PRS on the BWP; + - 2> receive SL-SCH on the BWP; + - 2> transmit PSFCH on the BWP, if configured; + - 2> (re-)initialize any suspended configured sidelink grant of configured grant Type 1. + - 2> if *sl-lbt-FailureRecoveryConfig* is configured: + - 3> set *SL\_LBT\_COUNTER* to 0 for all RB sets in the SL BWP; + - 3> monitors SL LBT failure indications from lower layers as specified in clause 5.31.2. +- 1> if the BWP is deactivated: + - 2> not transmit SL-BCH on the BWP, if configured; + - 2> not transmit S-PSS and S-SSS on the BWP, if configured; + - 2> not transmit PSCCH on the BWP; + - 2> not transmit SL-PRS on the BWP; + - 2> not transmit SL-SCH on the BWP; + - 2> not receive PSFCH on the BWP, if configured; + - 2> not receive SL-BCH on the BWP, if configured; + - 2> not receive S-PSS and S-SSS on the BWP, if configured; + - 2> not receive PSCCH on the BWP; + - 2> not receive SL-PRS on the BWP; + - 2> not receive SL-SCH on the BWP; + - 2> not transmit PSFCH on the BWP, if configured; + - 2> suspend any configured sidelink grant of configured grant Type 1; + - 2> clear any configured sidelink grant of configured grant Type 2; + - 2> cancel, if any, triggered Scheduling Request procedure for sidelink; + - 2> cancel, if any, triggered Sidelink Buffer Status Reporting procedure; + +- 2> cancel, if any, triggered Sidelink CSI Reporting procedure; +- 2> cancel, if any, triggered Sidelink DRX Command MAC CE; +- 2> cancel, if any, triggered Sidelink IUC-Request transmission procedure; +- 2> cancel, if any, triggered Sidelink IUC-Information Reporting procedure; +- 2> if *sl-lbt-FailureDetectionTimer* is configured: + - 3> stop the *sl-lbt-FailureDetectionTimer* for all RB sets in the SL BWP, if running. + +## 5.16 SUL operation + +The Supplementary UL (SUL) carrier can be configured as a complement to the normal UL (NUL) carrier. Switching between the NUL carrier and the SUL carrier means that the UL transmissions move from one carrier to the other carrier, which is done by: + +- an indication in DCI; +- the Random Access procedure as specified in clause 5.1.1; +- the SDT procedure as specified in clause 5.27. + +If the MAC entity receives a UL grant indicating an SUL switch while a Random Access procedure is ongoing, the MAC entity shall ignore the UL grant. + +The Serving Cell configured with *supplementaryUplink* belongs to a single TAG. + +## 5.17 Beam Failure Detection and Recovery procedure + +The MAC entity may be configured by RRC per Serving Cell or per BFD-RS set with a beam failure recovery procedure which is used for indicating to the serving gNB of a new SSB or CSI-RS when beam failure is detected on the serving SSB(s)/CSI-RS(s). Beam failure is detected by counting beam failure instance indication from the lower layers to the MAC entity. If *beamFailureRecoveryConfig* is reconfigured by upper layers during an ongoing Random Access procedure for beam failure recovery for SpCell, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure using the new configuration. The Serving Cell is configured with two BFD-RS sets if and only if *failureDetectionSet1* and *failureDetectionSet2* are configured for the active DL BWP of the Serving Cell. When the SCG is deactivated, the UE performs beam failure detection on the PSCell if *bfd-and-RLM* is set to *true*. + +RRC configures the following parameters in the *beamFailureRecoveryConfig*, *beamFailureRecoverySpCellConfig*, *beamFailureRecoverySCellConfig* and the *radioLinkMonitoringConfig* for the Beam Failure Detection and Recovery procedure: + +- *beamFailureInstanceMaxCount* for the beam failure detection (per Serving Cell or per BFD-RS set of Serving Cell configured with two BFD-RS sets); +- *beamFailureDetectionTimer* for the beam failure detection (per Serving Cell or per BFD-RS set of Serving Cell configured with two BFD-RS sets); +- *beamFailureRecoveryTimer* for the beam failure recovery procedure for SpCell; +- *rsrp-ThresholdSSB*: an RSRP threshold for the SpCell beam failure recovery; +- *rsrp-ThresholdBFR*: an RSRP threshold for the SCell beam failure recovery or for the beam failure recovery of BFD-RS set of Serving Cell; +- *powerRampingStep*: *powerRampingStep* for the SpCell beam failure recovery; +- *powerRampingStepHighPriority*: *powerRampingStepHighPriority* for the SpCell beam failure recovery; +- *preambleReceivedTargetPower*: *preambleReceivedTargetPower* for the SpCell beam failure recovery; + +- *preambleTransMax*: *preambleTransMax* for the SpCell beam failure recovery; +- *scalingFactorBI*: *scalingFactorBI* for the SpCell beam failure recovery; +- *ssb-perRACH-Occasion*: *ssb-perRACH-Occasion* for the SpCell beam failure recovery using contention-free Random Access Resources; +- *ra-ResponseWindow*: the time window to monitor response(s) for the SpCell beam failure recovery using contention-free Random Access Resources; +- *prach-ConfigurationIndex*: *prach-ConfigurationIndex* for the SpCell beam failure recovery using contention-free Random Access Resources; +- *ra-ssb-OccasionMaskIndex*: *ra-ssb-OccasionMaskIndex* for the SpCell beam failure recovery using contention-free Random Access Resources; +- *ra-OccasionList*: *ra-OccasionList* for the SpCell beam failure recovery using contention-free Random Access Resources; +- *candidateBeamRSList*: list of candidate beams for SpCell beam failure recovery; +- *candidateBeamRS-List-r16*: list of candidate beams for SCell beam failure recovery or list of candidate beams for beam failure recovery of a Serving Cell for BFD-RS set one; +- *candidateBeamRS-List2-r17*: list of candidate beams for beam failure recovery of a Serving Cell for BFD-RS set two. + +The following UE variables are used for the beam failure detection procedure: + +- *BFI\_COUNTER* (per Serving Cell or per BFD-RS set of Serving Cell configured with two BFD-RS sets): counter for beam failure instance indication which is initially set to 0. + +The MAC entity shall for each Serving Cell configured for beam failure detection: + +- 1> if the Serving Cell is configured with two BFD-RS sets: + - 2> if beam failure instance indication for a BFD-RS set has been received from lower layers: + - 3> start or restart the *beamFailureDetectionTimer* of the BFD-RS set; + - 3> increment *BFI\_COUNTER* of the BFD-RS set by 1; + - 3> if *BFI\_COUNTER* of the BFD-RS set $\geq$ *beamFailureInstanceMaxCount*: + - 4> trigger a BFR for this BFD-RS set of the Serving Cell; + - 2> if BFR is triggered for both BFD-RS sets of the SpCell and the Beam Failure Recovery procedure is not successfully completed for any of the BFD-RS sets: + - 3> initiate a Random Access procedure (see clause 5.1) on the SpCell; + - 2> if the Serving Cell is SpCell and the Random Access procedure initiated for beam failure recovery of both BFD-RS sets of SpCell is successfully completed (see clause 5.1): + - 3> set *BFI\_COUNTER* of each BFD-RS set of SpCell to 0. + - 3> consider the Beam Failure Recovery procedure successfully completed. + - 2> if the *beamFailureDetectionTimer* of this BFD-RS set expires; or + - 2> if *beamFailureDetectionTimer*, *beamFailureInstanceMaxCount*, or any of the reference signals used for beam failure detection is reconfigured by upper layers or by the BFD-RS Indication MAC CE associated with a BFD-RS set of the Serving Cell; or + - 2> if the reference signal(s) associated with a BFD-RS set of the Serving Cell used for beam failure detection is changed: + +- 3> set *BFI\_COUNTER* of the BFD-RS set to 0. +- 2> if a PDCCH addressed to C-RNTI indicating uplink grant for a new transmission is received for the HARQ process used for the transmission of the Enhanced BFR MAC CE or Truncated Enhanced BFR MAC CE which contains beam failure recovery information of this BFD-RS set of the Serving Cell: + - 3> set *BFI\_COUNTER* of the BFD-RS set to 0; + - 3> consider the Beam Failure Recovery procedure successfully completed for this BFD-RS set and cancel all the triggered BFRs of this BFD-RS set of the Serving Cell. +- 2> if the Serving Cell is SCell and the SCell is deactivated as specified in clause 5.9: + - 3> set *BFI\_COUNTER* of each BFD-RS set of SCell to 0; + - 3> consider the Beam Failure Recovery procedure successfully completed and cancel all the triggered BFRs of all BFD-RS sets of the Serving Cell. +- 1> else: + - 2> if beam failure instance indication has been received from lower layers: + - 3> start or restart the *beamFailureDetectionTimer*; + - 3> increment *BFI\_COUNTER* by 1; + - 3> if *BFI\_COUNTER* >= *beamFailureInstanceMaxCount*: + - 4> if the Serving Cell is SCell: + - 5> trigger a BFR for this Serving Cell; + - 4> else if the Serving Cell is PSCell and, the SCG is deactivated: + - 5> if beam failure of the PSCell has not been indicated to upper layers since the SCG was deactivated or since the deactivated SCG was last reconfigured with BFD-RS: + - 6> indicate beam failure of the PSCell to upper layers. + - NOTE: After beam failure is indicated to upper layers, the UE may stop the *beamFailureDetectionTimer* and lower layer beam failure indication while *BFI\_COUNTER* >= *beamFailureInstanceMaxCount* for the deactivated SCG. + - 4> else: + - 5> initiate a Random Access procedure (see clause 5.1) on the SpCell; + - 5> if beam failure is detected for an NCR-MT: + - 6> indicate to NCR-Fwd to cease forwarding. +- 2> if the *beamFailureDetectionTimer* expires; or +- 2> if *beamFailureDetectionTimer*, *beamFailureInstanceMaxCount*, or any of the reference signals used for beam failure detection is reconfigured by upper layers associated with this Serving Cell; or +- 2> if the reference signal(s) associated with this Serving Cell used for beam failure detection is changed: + - 3> set *BFI\_COUNTER* to 0. +- 2> if the Serving Cell is SpCell and the Random Access procedure initiated for SpCell beam failure recovery is successfully completed (see clause 5.1): + - 3> set *BFI\_COUNTER* to 0; + - 3> stop the *beamFailureRecoveryTimer*, if configured; + - 3> if the Random Access procedure was triggered by beam failure recovery for NCR-MT: + +- 4> indicate to NCR-Fwd to resume forwarding using the last forwarding configuration received by NCR-MT as part of side control information before beam failure detection; +- 3> consider the Beam Failure Recovery procedure successfully completed. +- 2> else if the Serving Cell is SCell, and a PDCCH addressed to C-RNTI indicating uplink grant for a new transmission is received for the HARQ process used for the transmission of the MAC CE for BFR which contains beam failure recovery information of this Serving Cell; or +- 2> if the SCell is deactivated as specified in clause 5.9: + - 3> set *BFI\_COUNTER* to 0; + - 3> consider the Beam Failure Recovery procedure successfully completed and cancel all the triggered BFRs for this Serving Cell. + +The MAC entity shall: + +- 1> if the Beam Failure Recovery procedure determines that at least one BFR has been triggered and not cancelled for an SCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed and if none of the Serving Cell(s) of this MAC entity are configured with two BFD-RS sets: + - 2> if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the BFR MAC CE plus its subheader as a result of LCP: + - 3> instruct the Multiplexing and Assembly procedure to generate the BFR MAC CE. + - 2> else if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the Truncated BFR MAC CE plus its subheader as a result of LCP: + - 3> instruct the Multiplexing and Assembly procedure to generate the Truncated BFR MAC CE. + - 2> else: + - 3> trigger the SR for SCell beam failure recovery for each SCell for which BFR has been triggered, not cancelled, and for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed. +- 1> if the Beam Failure Recovery procedure determines that at least one BFR for any BFD-RS set has been triggered and not cancelled for an SCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed; or +- 1> if the Beam Failure Recovery procedure determines that at least one BFR for only one BFD-RS set has been triggered and not cancelled for an SpCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed; or +- 1> if the Beam Failure Recovery procedure determines that at least one BFR has been triggered and not cancelled for an SCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed and if at least one Serving Cell of this MAC entity is configured with two BFD-RS sets: + - 2> if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the Enhanced BFR MAC CE plus its subheader as a result of LCP: + - 3> instruct the Multiplexing and Assembly procedure to generate the Enhanced BFR MAC CE. + - 2> else if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the Truncated Enhanced BFR MAC CE plus its subheader as a result of LCP: + - 3> instruct the Multiplexing and Assembly procedure to generate the Truncated Enhanced BFR MAC CE. + - 2> else: + - 3> trigger the SR for beam failure recovery of each BFD-RS set for which BFR has been triggered, not cancelled, and for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed; + +- 3> trigger the SR for SCell beam failure recovery for each SCell for which BFR has been triggered, not cancelled, and for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed. + +All BFRs triggered for an SCell shall be cancelled when a MAC PDU is transmitted and this PDU includes a MAC CE for BFR which contains beam failure information of that SCell. All BFRs triggered for a BFD-RS set of a Serving Cell shall be cancelled when a MAC PDU is transmitted and this PDU includes an Enhanced BFR MAC CE or Truncated Enhanced BFR MAC CE which contains beam failure recovery information of that BFD-RS set of the Serving Cell. + +## 5.18 Handling of MAC CEs + +### 5.18.1 General + +This clause specifies the requirements upon reception or transmission of the following MAC CEs: + +- SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE; +- Aperiodic CSI Trigger State Subselection MAC CE; +- TCI States Activation/Deactivation for UE-specific PDSCH MAC CE; +- TCI State Indication for UE-specific PDCCH MAC CE; +- SP CSI reporting on PUCCH Activation/Deactivation MAC CE; +- Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE; +- SP SRS Activation/Deactivation MAC CE; +- PUCCH spatial relation Activation/Deactivation MAC CE; +- Enhanced PUCCH spatial relation Activation/Deactivation MAC CE; +- SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE; +- Recommended Bit Rate MAC CE; +- Enhanced SP/AP SRS Spatial Relation Indication MAC CE; +- SRS Pathloss Reference RS Update MAC CE; +- PUSCH Pathloss Reference RS Update MAC CE; +- Serving Cell set based SRS Spatial Relation Indication MAC CE; +- SP Positioning SRS Activation/Deactivation MAC CE; +- Timing Delta MAC CE; +- Guard Symbols MAC CEs; +- Positioning Measurement Gap Activation/Deactivation Command MAC CE; +- PPW Activation/Deactivation Command MAC CE; +- PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE; +- PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC CE; +- Unified TCI States Activation/Deactivation MAC CE; +- Differential Koffset MAC CE; +- Case-7 Timing advance offset MAC CE; +- DL TX Power Adjustment MAC CEs; + +- Child IAB-DU Restricted Beam Indication MAC CE; +- Timing Case Indication MAC CE; +- PSI-Based SDU Discard Activation/Deactivation MAC CE; +- BFD-RS Indication MAC CE; +- IAB-MT Recommended Beam Indication MAC CE; +- UL PSD range adjustment for IAB MAC CE; +- Case-6 Timing Request MAC CE; +- NCR Backhaul Link Beam Indication MAC CEs; +- NCR Access Link Beam Indication MAC CE; +- Enhanced Unified TCI States Activation/Deactivation MAC CE; +- LTM Cell Switch Command MAC CE; +- Candidate Cell TCI States Activation/Deactivation MAC CE. + +## 5.18.2 Activation/Deactivation of Semi-persistent CSI-RS/CSI-IM resource set + +The network may activate and deactivate the configured Semi-persistent CSI-RS/CSI-IM resource sets of a Serving Cell by sending the SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE described in clause 6.1.3.12. The configured Semi-persistent CSI-RS/CSI-IM resource sets are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives an SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE on a Serving Cell: +- 2> indicate to lower layers the information regarding the SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE. + +## 5.18.3 Aperiodic CSI Trigger State Subselection + +The network may select among the configured aperiodic CSI trigger states of a Serving Cell by sending the Aperiodic CSI Trigger State Subselection MAC CE described in clause 6.1.3.13. + +The MAC entity shall: + +- 1> if the MAC entity receives an Aperiodic CSI trigger State Subselection MAC CE on a Serving Cell: +- 2> indicate to lower layers the information regarding Aperiodic CSI trigger State Subselection MAC CE. + +## 5.18.4 Activation/Deactivation of UE-specific PDSCH TCI state + +The network may activate and deactivate the configured TCI states for PDSCH of a Serving Cell or a set of Serving Cells configured in *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* by sending the TCI States Activation/Deactivation for UE-specific PDSCH MAC CE described in clause 6.1.3.14. The network may activate and deactivate the configured TCI states for a codepoint of the DCI *Transmission configuration indication* field as specified in TS 38.212 [9] for PDSCH of a Serving Cell by sending the Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE described in clause 6.1.3.24. The configured TCI states for PDSCH are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives a TCI States Activation/Deactivation for UE-specific PDSCH MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the TCI States Activation/Deactivation for UE-specific PDSCH MAC CE. +- 1> if the MAC entity receives an Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE. + +### 5.18.5 Indication of TCI state for UE-specific PDCCH + +The network may indicate a TCI state for PDCCH reception for a CORESET of a Serving Cell or a set of Serving Cells configured in *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* by sending the TCI State Indication for UE-specific PDCCH MAC CE described in clause 6.1.3.15 or the cross-RRH TCI State Indication for UE-specific PDCCH MAC CE described in clause 6.1.3.77. The network may also indicate two TCI states for PDCCH reception for a CORESET of a Serving Cell or a set of Serving Cells configured in *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* by sending the Enhanced TCI States Indication for UE-specific PDCCH MAC CE described in clause 6.1.3.44. + +The MAC entity shall: + +- 1> if the MAC entity receives a TCI State Indication for UE-specific PDCCH MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the TCI State Indication for UE-specific PDCCH MAC CE. +- 1> if the MAC entity receives an Enhanced TCI States Indication for UE-specific PDCCH MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Enhanced TCI States Indication for UE-specific PDCCH MAC CE. +- 1> if the MAC entity receives a cross-RRH TCI State Indication for UE-specific PDCCH MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the cross-RRH TCI State Indication for UE-specific PDCCH MAC CE. + +### 5.18.6 Activation/Deactivation of Semi-persistent CSI reporting on PUCCH + +The network may activate and deactivate the configured Semi-persistent CSI reporting on PUCCH of a Serving Cell by sending the SP CSI reporting on PUCCH Activation/Deactivation MAC CE described in clause 6.1.3.16 or the Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE described in clause 6.1.3.80. The network may activate and deactivate at least one of the configured sub configuration of a configured Semi-Persistent CSI reporting on PUCCH of a Serving Cell by sending the Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE described in clause 6.1.3.80. For each Semi-persistent CSI reporting on PUCCH configuration configured with *csi-ReportSubConfigList*, the network may deactivate all configured sub configurations by sending the SP CSI reporting on PUCCH Activation/Deactivation MAC CE. The configured Semi-persistent CSI reporting on PUCCH is initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives an SP CSI reporting on PUCCH Activation/Deactivation MAC CE or an Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the SP CSI reporting on PUCCH Activation/Deactivation MAC CE or the Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE. + +## 5.18.7 Activation/Deactivation of Semi-persistent SRS and Indication of spatial relation of SP/AP SRS + +The network may activate and deactivate the configured Semi-persistent SRS resource sets of a Serving Cell by sending the SP SRS Activation/Deactivation MAC CE described in clause 6.1.3.17. The network may also activate and deactivate the configured Semi-persistent SRS resource sets of a Serving Cell by sending the Enhanced SP/AP SRS Spatial Relation Indication MAC CE described in clause 6.1.3.26. The network may also activate and deactivate the configured Semi-persistent SRS resource sets of a Serving Cell by sending the SP/AP SRS TCI State Indication MAC CE described in clause 6.1.3.59. The configured Semi-persistent SRS resource sets are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. The network may indicate the spatial relation info of SP/AP SRS resource sets of a Serving Cell by sending the Enhanced SP/AP SRS spatial relation Indication MAC CE described in clause 6.1.3.26. + +The MAC entity shall: + +- 1> if the MAC entity receives an SP SRS Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the SP SRS Activation/Deactivation MAC CE. +- 1> if the MAC entity receives an Enhanced SP/AP SRS Spatial Relation Indication MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Enhanced SP/AP SRS Spatial Relation Indication MAC CE. +- 1> if the MAC entity receives an SP/AP SRS TCI State Indication MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the SP/AP SRS TCI State Indication MAC CE. + +## 5.18.8 Activation/Deactivation of spatial relation of PUCCH resource + +The network may activate and deactivate a spatial relation for a PUCCH resource of a Serving Cell by sending the PUCCH spatial relation Activation/Deactivation MAC CE described in clause 6.1.3.18. The network may also activate and deactivate a spatial relation for a PUCCH resource or a PUCCH resource group of a Serving Cell by sending the Enhanced PUCCH spatial relation Activation/Deactivation MAC CE described in clause 6.1.3.25. The configured spatial relation for a PUCCH resource is initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. The network may also activate and deactivate the two spatial relations for a PUCCH resource or a PUCCH resource group of a Serving Cell by sending the PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE described in clause 6.1.3.45. + +The MAC entity shall: + +- 1> if the MAC entity receives a PUCCH spatial relation Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the PUCCH spatial relation Activation/Deactivation MAC CE. +- 1> if the MAC entity receives an Enhanced PUCCH spatial relation Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Enhanced PUCCH spatial relation Activation/Deactivation MAC CE. +- 1> if the MAC entity receives a PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE. + +## 5.18.9 Activation/Deactivation of semi-persistent ZP CSI-RS resource set + +The network may activate and deactivate the configured Semi-persistent ZP CSI-RS resource set of a Serving Cell by sending the SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE described in clause 6.1.3.19. The configured + +Semi-persistent ZP CSI-RS resource sets are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives an SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE. + +## 5.18.10 Recommended Bit Rate + +The recommended bit rate procedure is used to provide the MAC entity with information about the bit rate which the gNB recommends. The bit rate is the recommended bit rate of the physical layer. Averaging window of default value 2000 ms will apply as specified in TS 26.114 [13]. + +The gNB may transmit the Recommended bit rate MAC CE to the MAC entity to indicate the recommended bit rate for the UE for a specific logical channel and a specific direction (either uplink or downlink). Upon reception of a Recommended bit rate MAC CE the MAC entity shall: + +- indicate to upper layers the recommended bit rate for the indicated logical channel and direction. + +The MAC entity may request the gNB to indicate the recommended bit rate for a specific logical channel and a specific direction. If the MAC entity is requested by upper layers to query the gNB for the recommended bit rate for a logical channel and for a direction (i.e. for uplink or downlink), the MAC entity shall: + +- 1> if a Recommended bit rate query for this logical channel and this direction has not been triggered: + - 2> trigger a Recommended bit rate query for this logical channel, direction, and desired bit rate. + +If the MAC entity has UL resources allocated for new transmission the MAC entity shall: + +- 1> for each Recommended bit rate query that the Recommended Bit Rate procedure determines has been triggered and not cancelled: + - 2> if *bitRateQueryProhibitTimer* for the logical channel and the direction of this Recommended bit rate query is configured, and it is not running; and + - 2> if the MAC entity has UL resources allocated for new transmission and the allocated UL resources can accommodate a Recommended bit rate MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1: + - 3> instruct the Multiplexing and Assembly procedure to generate the Recommended bit rate MAC CE for the logical channel and the direction of this Recommended bit rate query; + - 3> start the *bitRateQueryProhibitTimer* for the logical channel and the direction of this Recommended bit rate query; + - 3> cancel this Recommended bit rate query. + +## 5.18.11 Void + +## 5.18.12 Void + +## 5.18.13 Void + +## 5.18.14 Update of Pathloss Reference RS of SRS + +The network may activate and update a pathloss reference RS for an SRS resource of a Serving Cell by sending the SRS Pathloss Reference RS Update MAC CE described in clause 6.1.3.27. + +The MAC entity shall: + +- 1> if the MAC entity receives an SRS Pathloss Reference RS Update MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the SRS Pathloss Reference RS Update MAC CE. + +### 5.18.15 Update of Pathloss Reference RS of PUSCH + +The network may activate and update a pathloss reference RS for PUSCH of a Serving Cell by sending the PUSCH Pathloss Reference RS Update MAC CE described in clause 6.1.3.28. + +The MAC entity shall: + +- 1> if the MAC entity receives a PUSCH Pathloss Reference RS Update MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the PUSCH Pathloss Reference RS Update MAC CE. + +### 5.18.16 Indication of spatial relation of SRS resource for a Serving Cell set + +The network may indicate the spatial relation info of SRS resource of a set of Serving Cells configured in *simultaneousSpatial-UpdatedList1* or *simultaneousSpatial-UpdatedList2* by sending the Serving Cell set based SRS Spatial Relation Indication MAC CE and the Serving Cell Set based SRS TCI State Indication MAC CE described in clause 6.1.3.29 and 6.1.3.60, respectively. + +The MAC entity shall: + +- 1> if the MAC entity receives a Serving Cell set based SRS Spatial Relation Indication MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Serving Cell set based SRS Spatial Relation Indication MAC CE. +- 1> if the MAC entity receives a Serving Cell Set based SRS TCI State Indication MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Serving Cell Set based SRS TCI State Indication MAC CE. + +### 5.18.17 Activation/Deactivation of Semi-Persistent Positioning SRS + +The network may activate and deactivate the configured resource sets of Semi-Persistent Positioning SRS of a Serving Cell by sending the SP Positioning SRS Activation/Deactivation MAC CE described in clause 6.1.3.36. The configured resource sets Semi-Persistent Positioning SRS are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives an SP Positioning SRS Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the SP Positioning SRS Activation/Deactivation MAC CE. + +### 5.18.18 Timing offset adjustments for IAB + +For IAB operation, in order to achieve time-domain synchronization across multiple backhaul hops, a timing adjustment may be provided to an IAB node by its parent node. Two different values may be provided, related to Case-1/Case-6, and Case-7 timing modes respectively. The Timing Delta MAC CE carries $T_{\text{delta}}$ which is used to determine the IAB-DU DL Tx timing adjustment for the Case-1 timing mode, and to determine the IAB-DU DL Tx and IAB-MT UL Tx timing adjustment for the Case-6 timing mode. The Case-7 Timing advance offset MAC CE carries $T_{\text{offset},2}$ which is used to determine the IAB-MT UL Tx timing adjustment for the Case-7 timing mode. + +Upon reception of a Timing Delta MAC CE the IAB node shall: + +- apply the value of $T_{\text{delta}}$ as specified in TS 38.213 [6]. + +Upon reception of a Case-7 Timing advance offset MAC CE the IAB node shall: + +- apply the value of $T_{\text{offset},2}$ as specified in TS 38.213 [6]. + +## 5.18.19 Guard symbols for IAB + +For IAB operation, the MAC entity on the IAB-DU or IAB-donor-DU reserves a sufficient number of symbols at the beginning and/or the end of slots where the child IAB-node switches operation from its IAB-DU to its IAB-MT function and operation from its IAB-MT to its IAB-DU function. The MAC entity on the IAB-DU or IAB-donor-DU informs the child node about the number of guard symbols it provides via the Provided Guard Symbols MAC CE. The IAB-MT on the child node may inform the parent IAB-DU or IAB-donor-DU about the number of guard symbols desired via the Desired Guard Symbols MAC CE. IAB-MT transmission timing modes are specified in clause 14 of TS 38.213 [6]. + +Upon reception of a Provided Guard Symbols MAC CE the MAC entity shall: + +- indicate to lower layers the number of provided guard symbols and the SCS configuration for the indicated Serving Cell. + +The MAC entity may: + +- 1> if a Desired Guard Symbol query has not been triggered: + - 2> trigger a Desired Guard Symbol query for this Serving Cell. + +If the MAC entity has UL resources allocated for new transmission the MAC entity shall: + +- 1> for each Desired Guard Symbol query that has been triggered and not cancelled: + - 2> if the allocated UL resources can accommodate a Desired Guard Symbols MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1: + - 3> instruct the Multiplexing and Assembly procedure to generate the Desired Guard Symbols MAC CE; + - 3> cancel this Desired Guard Symbol query. + +For Case-1 timing mode, a separate value for the number of guard symbols is specified for each of the following eight switching scenarios (see Table 5.18.19-1). + +**Table 5.18.19-1: Switching scenarios and relevant guard symbols for Case-1 timing mode** + +| Switching scenario | | Field for number of guard symbols in MAC CE | +|--------------------------------------|----------------|---------------------------------------------| +| IAB-MT operation to IAB-DU operation | MT Rx to DU Tx | NmbGS 1 | +| | MT Rx to DU Rx | NmbGS 2 | +| | MT Tx to DU Tx | NmbGS 3 | +| | MT Tx to DU Rx | NmbGS 4 | +| IAB-DU operation to IAB-MT operation | DU Rx to MT Tx | NmbGS 5 | +| | DU Rx to MT Rx | NmbGS 6 | +| | DU Tx to MT Tx | NmbGS 7 | +| | DU Tx to MT Rx | NmbGS 8 | + +For Case-6 and Case-7 timing modes, a separate value for the number of guard symbols is specified for each of the following eight switching scenarios (see Table 5.18.19-2): + +**Table 5.18.19-2: Switching scenarios and relevant guard symbols for Case-6 and Case-7 timing modes** + +| Switching scenario | | Field for number of guard symbols in MAC CE | +|--------------------------------------|----------------------------------|---------------------------------------------| +| IAB-MT operation to IAB-DU operation | MT Tx (Case-6) to DU Tx (Case-1) | NmbGS 9 | +| | MT Tx (Case-6) to DU Rx (Case-1) | NmbGS 10 | +| | MT Tx (Case-7) to DU Tx (Case-1) | NmbGS 11 | +| | MT Tx (Case-7) to DU Rx (Case-1) | NmbGS 12 | +| IAB-DU operation to IAB-MT operation | DU Tx (Case-1) to MT Tx (Case-6) | NmbGS 13 | + +| | | | +|--------------|----------------------------------|---------------------| +| MT operation | DU Rx (Case-1) to MT Tx (Case-6) | NmbGS 14 | +| | DU Tx (Case-1) to MT Tx (Case-7) | NmbGS 15 | +| | DU Rx (Case-1) to MT Tx (Case-7) | NmbGS 16 | + +## 5.18.20 Positioning Measurement Gap Activation/Deactivation Command + +If the UE is configured with pre-configured measurement gaps, the network may send DL MAC CE for Positioning Measurement Gap Activation/Deactivation Command to the UE as in clause 6.1.3.41. For the activated measurement gap, the UE shall follow the specified UE behaviour in clause 5.14. + +Upon the reception of the MAC CE for Positioning Measurement Gap Activation/Deactivation Command, the MAC entity shall: + +- 1> if the Measurement Gap Activation/Deactivation Command MAC CE indicates the deactivation of a pre-configured positioning measurement gap: + - 2> deactivate the positioning measurement gap. +- 1> else if the Positioning Measurement Gap Activation/Deactivation Command MAC CE indicates the activation of a pre-configured measurement gap: + - 2> activate the positioning measurement gap and perform the procedure specified in clause 5.14. + +## 5.18.21 PPW Activation/Deactivation Command + +If the UE is configured with pre-configured PPW, the network may send DL MAC CE for PPW Activation/Deactivation Command to the UE as in clause 6.1.3.42. For the activated PPW, the UE shall follow the specified UE behaviour in clause 5.24. + +Upon activation of DL BWP, the PPW(s) configured for that BWP are considered deactivated. Upon reconfiguration of PPW(s) of the active DL BWP, all the PPW(s) for that BWP are considered deactivated. + +Upon the reception of the MAC CE for PPW Activation/Deactivation Command, the MAC entity shall: + +- 1> if the DL MAC CE for PPW Activation/Deactivation Command indicates the deactivation of a pre-configured PPW: + - 2> deactivate the PPW. +- 1> else if the DL MAC CE for PPW Activation/Deactivation Command indicates the activation of a pre-configured PPW: + - 2> activate the PPW according to the procedure specified in clause 5.24. + +## 5.18.22 Update of PUCCH Power Control Set for multiple TRP PUCCH repetition + +The network may activate and deactivate PUCCH power control set(s) for multiple TRP PUCCH repetition for a PUCCH resource or a PUCCH resource group of a Serving Cell by sending the PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC CE described in clause 6.1.3.46. + +The MAC entity shall: + +- 1> if the MAC entity receives a PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the PUCCH power control set update for multiple TRP PUCCH repetition MAC CE. + +## 5.18.23 Unified TCI States Activation/Deactivation MAC CE + +The network may activate and deactivate the configured unified TCI states of a Serving Cell or a set of Serving Cells configured in *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4* by sending the Unified TCI States Activation/Deactivation MAC CE described in clause 6.1.3.47. The configured unified TCI states are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives a Unified TCI States Activation/Deactivation MAC CE on a Serving Cell: +- 2> indicate to lower layers the information regarding the Unified TCI States Activation/Deactivation MAC CE. + +## 5.18.24 Update of Differential Koffset + +The network may provide and update the Differential Koffset of a Serving Cell in a non-terrestrial network by sending the Differential Koffset MAC CE described in clause 6.1.3.57. + +The MAC entity shall: + +- 1> if the MAC entity receives a Differential Koffset MAC CE on a Serving Cell: +- 2> indicate to lower layers the information regarding the Differential Koffset MAC CE. + +## 5.18.25 BFD-RS Indication MAC CE + +The network may activate and deactivate the configured beam failure detection resources of a Serving Cell by sending the BFD-RS indication MAC CE described in clause 6.1.3.58. + +The MAC entity shall: + +- 1> if the MAC entity receives a BFD-RS indication MAC CE on a Serving Cell: +- 2> indicate to lower layers the information regarding the BFD-RS Indication MAC CE. + +## 5.18.26 Restricted and recommended beam indication for IAB + +Child IAB-DU Restricted Beam Indication MAC CE is used by an IAB-node to indicate to its child node spatial resources and associated frequency information where simultaneous transmission/reception from the IAB-MT and transmission from the IAB-DU cells is restricted. IAB-MT Recommended Beam Indication MAC CE is used by an IAB-node to indicate to its parent node recommendations for such a restriction. Time resources where these restrictions/recommendations can apply are indicated via RRC, while the MAC CE further selects from these time resources the specific time resource configuration (comprising a list of slot indices) to which information provided in the MAC CE applies. + +Upon reception of a Child IAB-DU Restricted Beam Indication MAC CE the IAB-node shall: + +- apply the configuration signalled in the MAC CE to the time slots indicated in *IAB-ResourceConfig* (as specified in TS 38.331 [5]) which contains *iab-ResourceConfigID* parameter which matches the Resource Configuration ID field of the MAC CE. + +The MAC entity may: + +- 1> if an IAB-MT Recommended Beam Indication query has not been triggered: +- 2> trigger an IAB-MT Recommended Beam Indication query for this Serving Cell. + +If the MAC entity has UL resources allocated for new transmission the MAC entity shall: + +- 1> for each IAB-MT Recommended Beam Indication query that has been triggered and not cancelled: +- 2> if the allocated UL resources can accommodate a IAB-MT Recommended Beam Indication MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1: + +- 3> instruct the Multiplexing and Assembly procedure to generate the IAB-MT Recommended Beam Indication MAC CE; +- 3> cancel this IAB-MT Recommended Beam Indication query. + +## 5.18.27 DL TX power adjustment for IAB + +DL TX Power Adjustment MAC CE is used by an IAB-node to indicate to its child node spatial resources and associated frequency information where the DL TX power adjustment contained in the MAC CE applies. Desired DL TX Power Adjustment MAC CE is used by an IAB-node to indicate to its parent node recommendations for such a restriction. Time resources where these restrictions/recommendations can apply are indicated via RRC, while the MAC CE further selects from these time resources the specific time resource configuration (comprising a list of slot indices) to which information provided in the MAC CE applies. + +Upon reception of a DL TX Power Adjustment MAC CE the IAB-node shall: + +- apply the configuration signalled in the MAC CE to the time slots indicated in *IAB-ResourceConfig* (as specified in TS 38.331 [5]) which contains *iab-ResourceConfigID* parameter which matches the Resource Configuration ID field of the MAC CE. + +The MAC entity may: + +- 1> if a Desired DL TX Power Adjustment query has not been triggered: + - 2> trigger a Desired DL TX Power Adjustment query for this Serving Cell. + +If the MAC entity has UL resources allocated for new transmission the MAC entity shall: + +- 1> for each Desired DL TX Power Adjustment query that has been triggered and not cancelled: + - 2> if the allocated UL resources can accommodate a Desired DL TX Power Adjustment MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1: + - 3> instruct the Multiplexing and Assembly procedure to generate the Desired DL TX Power Adjustment MAC CE; + - 3> cancel this Desired DL TX Power Adjustment query. + +## 5.18.28 UL PSD range adjustment for IAB + +Desired IAB-MT PSD range MAC CE is used by an IAB-node to indicate to its parent node a recommendation of spatial resources and associated frequency information where the desired PSD range, contained in the MAC CE (and provided to help with the node's UL TX power control) could apply. Time resources where these recommendations can apply are indicated via RRC, while the MAC CE further selects from these time resources the specific time resource configuration (comprising a list of slot indices) to which information provided in the MAC CE applies. + +The MAC entity may: + +- 1> if a Desired IAB-MT PSD range query has not been triggered: + - 2> trigger a Desired IAB-MT PSD range query for this Serving Cell. + +If the MAC entity has UL resources allocated for new transmission the MAC entity shall: + +- 1> for each Desired IAB-MT PSD range query that has been triggered and not cancelled: + - 2> if the allocated UL resources can accommodate a Desired IAB-MT PSD range MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1: + - 3> instruct the Multiplexing and Assembly procedure to generate the Desired IAB-MT PSD range MAC CE; + - 3> cancel this Desired IAB-MT PSD range query. + +## 5.18.29 Timing case indication for IAB + +Timing Case Indication MAC CE is used by an IAB-node to indicate to its child node timing modes which should apply to time resources indicated via RRC. + +Upon reception of a Timing Case Indication MAC CE the IAB-node shall: + +- apply the configuration signalled in the MAC CE to the time slots indicated in *IAB-ResourceConfig* which contains *iab-ResourceConfigID* parameter (as specified in TS 38.331 [5]) which matches the Resource Configuration ID field of the MAC CE. + +## 5.18.30 Case-6 Timing Request + +The Case-6 Timing Request MAC CE is used by the IAB-MT to inform its parent node whether Case-6 timing is required for simultaneous operation. + +The MAC entity may: + +- 1> if a Case-6 Timing Request query has not been triggered: + - 2> trigger a Case-6 Timing Request query for this Serving Cell. + +If the MAC entity has UL resources allocated for new transmission the MAC entity shall: + +- 1> for each Case-6 Timing Request query that has been triggered and not cancelled: + - 2> if the allocated UL resources can accommodate a Case-6 Timing Request MAC CE plus its subheader as a result of LCP as defined in clause 5.4.3.1: + - 3> instruct the Multiplexing and Assembly procedure to generate the Case-6 Timing Request MAC CE; + - 3> cancel this Case-6 Timing Request query. + +## 5.18.31 Backhaul Link Beam Indication for NCR + +NCR Downlink Backhaul Link Beam Indication MAC CE and NCR Uplink Backhaul Link Beam Indication MAC CE are used by a gNB to indicate to an NCR-node the beam to be used for the downlink and uplink backhaul transmission respectively between the gNB and the NCR-node. + +Upon reception of an NCR Downlink Backhaul Link Beam Indication MAC CE, the NCR-node shall: + +- indicate to NCR-Fwd to apply the configuration contained in NCR Downlink Backhaul Link Beam Indication MAC CE as received by the NCR-MT. + +Upon reception of an NCR Uplink Backhaul Link Beam Indication MAC CE, the NCR-node shall: + +- indicate to NCR-Fwd to apply the configuration contained in the NCR Uplink Backhaul Link Beam Indication MAC CE as received by the NCR-MT. + +## 5.18.32 Access Link Beam Indication for NCR + +NCR Access Link Beam Indication MAC CE is used by a gNB to indicate to an NCR-node the forwarding resources to be used for the semi-persistent access link transmission between the NCR-node and the UE(s) served by this device. + +Upon reception of an NCR Access Link Beam Indication MAC CE, the NCR-node shall: + +- apply the configuration signalled in the MAC CE as received by NCR-MT to the forwarding resource lists indicated via RRC, and use it to operate the NCR-Fwd. + +### 5.18.33 Enhanced Unified TCI States Activation/Deactivation MAC CE + +The network may activate and deactivate the configured unified TCI states of a Serving Cell or a set of Serving Cells configured in *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4* by sending the Enhanced Unified TCI States Activation/Deactivation MAC CE described in clause 6.1.3.70 and 6.1.3.71. The configured unified TCI states are initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall: + +- 1> if the MAC entity receives an Enhanced Unified TCI States Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Enhanced Unified TCI States Activation/Deactivation MAC CE. + +### 5.18.34 Activation/deactivation of PSI-based SDU discard + +The network activates and deactivates PSI-based SDU discard by sending the PSI-Based SDU Discard Activation/Deactivation MAC CE described in clause 6.1.3.73. The PSI-based SDU discard is initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync. + +The MAC entity shall for each DRB configured with PSI-based SDU discard: + +- 1> if a PSI-Based SDU Discard Activation/Deactivation MAC CE is received activating the PSI-based SDU discard for the DRB: + - 2> indicate the activation of the PSI-based SDU discard for the DRB to upper-layers. +- 1> if a PSI-Based SDU Discard Activation/Deactivation MAC CE is received deactivating the PSI-based SDU discard for the DRB: + - 2> indicate the deactivation of the PSI-based SDU discard for the DRB to upper-layers. + +### 5.18.35 LTM Cell Switch Command + +The network may instruct the UE to perform LTM cell switch procedure by sending the LTM Cell Switch Command MAC CE described in clause 6.1.3.75. + +The MAC entity shall: + +- 1> if the MAC entity receives an LTM Cell Switch Command MAC CE on a Serving Cell: + - 2> indicate to upper layers that the LTM cell switch procedure is triggered and the Target Configuration ID included in the MAC CE; + - 2> if the MAC reset operation as specified in clause 5.12 is performed, as requested by upper layers: + - 3> if Timing Advance Command value (hexa-decimal) is not set as FFF: + - 4> process the received Timing Advance Command (see clause 5.2); + - 4> consider the RACH-less LTM cell switch to be ongoing; + - 4> if the MAC entity is associated with SCG: + - 5> indicate to upper layers to skip the Random Access procedure for this LTM cell switch. + - 3> else if the Timing Advance measurement is configured as specified in TS 38.331 [5] and the UE has successfully measured the Timing Advance for the indicated LTM target: + - 4> process the measured Timing Advance (see clause 5.2); + - 4> consider the RACH-less LTM cell switch to be ongoing. + - 4> if the MAC entity is associated with SCG: + +- 5> indicate to upper layers to skip the Random Access procedure for this LTM cell switch. +- 3> if TCI state information is included: + - 4> consider the SSB corresponding to the indicated TCI state as the one used for configured uplink grant selection for the initial uplink transmission towards the candidate cell for RACH-less LTM cell switch (as in clause 5.8.2); + - 4> indicate to lower layers the information regarding the TCI state information included in the LTM Cell Switch Command MAC CE. + +## 5.18.36 Candidate Cell TCI States Activation/Deactivation + +The network may activate and deactivate the TCI states of LTM candidate cell(s) configured in *CandidateTCI-State* and *CandidateTCI-UL-State* by sending the Candidate Cell TCI States Activation/Deactivation MAC CE described in clause 6.1.3.76. + +The MAC entity shall: + +- 1> if the MAC entity receives a Candidate Cell TCI States Activation/Deactivation MAC CE on a Serving Cell: + - 2> indicate to lower layers the information regarding the Candidate Cell TCI States Activation/Deactivation MAC CE. + +## 5.19 Data inactivity monitoring + +The UE may be configured by RRC with a Data inactivity monitoring functionality, when in RRC\_CONNECTED. RRC controls Data inactivity operation by configuring the timer *dataInactivityTimer*. + +When *dataInactivityTimer* is configured, the UE shall: + +- 1> if any MAC entity receives a MAC SDU for DTCH logical channel, DCCH logical channel, or CCCH logical channel, or multicast MTCH logical channel; or +- 1> if any MAC entity transmits a MAC SDU for DTCH logical channel, or DCCH logical channel: + - 2> start or restart *dataInactivityTimer*. +- 1> if the *dataInactivityTimer* expires: + - 2> indicate the expiry of the *dataInactivityTimer* to upper layers. + +## 5.20 Void + +## 5.21 LBT operation + +### 5.21.1 General + +The lower layer may perform an LBT procedure, see TS 37.213 [18], according to which a transmission is not performed by lower layers if the channel is identified as being occupied. When lower layer performs an LBT procedure before a transmission and the transmission is not performed, an LBT failure indication is sent to the MAC entity from lower layers. Unless otherwise specified, when LBT procedure is performed for a transmission, actions as specified in this specification are performed regardless of if an LBT failure indication is received from lower layers. When LBT is not performed by the lower layers, LBT failure indication is not received from lower layers. + +## 5.21.2 LBT failure detection and recovery procedure + +The MAC entity may be configured by RRC with a consistent LBT failure recovery procedure. Consistent LBT failure is detected per UL BWP by counting LBT failure indications, for all UL transmissions, from the lower layers to the MAC entity. + +RRC configures the following parameters in the *lbt-FailureRecoveryConfig*: + +- *lbt-FailureInstanceMaxCount* for the consistent LBT failure detection; +- *lbt-FailureDetectionTimer* for the consistent LBT failure detection; + +The following UE variable is used for the consistent LBT failure detection procedure: + +- *LBT\_COUNTER* (per Serving Cell): counter for LBT failure indication which is initially set to 0. + +For each activated Serving Cell configured with *lbt-FailureRecoveryConfig*, the MAC entity shall: + +- 1> if LBT failure indication has been received from lower layers: + - 2> start or restart the *lbt-FailureDetectionTimer*; + - 2> increment *LBT\_COUNTER* by 1; + - 2> if *LBT\_COUNTER* >= *lbt-FailureInstanceMaxCount*: + - 3> trigger consistent LBT failure for the active UL BWP in this Serving Cell; + - 3> if this Serving Cell is the SpCell: + - 4> if consistent LBT failure has been triggered in all UL BWPs configured with PRACH occasions on same carrier in this Serving Cell: + - 5> indicate consistent LBT failure to upper layers. + - 4> else: + - 5> stop any ongoing Random Access procedure in this Serving Cell; + - 5> switch the active UL BWP to a UL BWP, on same carrier in this Serving Cell, configured with PRACH occasion and for which consistent LBT failure has not been triggered; + - 5> initiate a Random Access Procedure (as specified in clause 5.1.1). + - 1> if all triggered consistent LBT failures are cancelled in this Serving Cell; or + - 1> if the *lbt-FailureDetectionTimer* expires; or + - 1> if *lbt-FailureDetectionTimer* or *lbt-FailureInstanceMaxCount* is reconfigured by upper layers: + - 2> set *LBT\_COUNTER* to 0. + +The MAC entity shall: + +- 1> if consistent LBT failure has been triggered, and not cancelled, in the SpCell; and +- 1> if UL-SCH resources are available for a new transmission in the SpCell and these UL-SCH resources can accommodate the LBT failure MAC CE plus its subheader as a result of logical channel prioritization: + - 2> instruct the Multiplexing and Assembly procedure to generate the LBT failure MAC CE. +- 1> else if consistent LBT failure has been triggered, and not cancelled, in at least one SCell: + - 2> if UL-SCH resources are available for a new transmission in a Serving Cell for which consistent LBT failure has not been triggered and these UL-SCH resources can accommodate the LBT failure MAC CE plus its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate the LBT failure MAC CE. + +2> else: + +3> trigger a Scheduling Request for LBT failure MAC CE. + +1> if a MAC PDU is transmitted and LBT failure indication is not received from lower layers and this PDU includes the LBT failure MAC CE: + +2> cancel all the triggered consistent LBT failure(s) in SCell(s) for which consistent LBT failure was indicated in the transmitted LBT failure MAC CE. + +1> if consistent LBT failure is triggered and not cancelled in the SpCell; and + +1> if the Random Access procedure is considered successfully completed (see clause 5.1) in the SpCell: + +2> cancel all the triggered consistent LBT failure(s) in the SpCell. + +1> if *lbt-FailureRecoveryConfig* is reconfigured by upper layers for a Serving Cell: + +2> cancel all the triggered consistent LBT failure(s) in this Serving Cell. + +## 5.22 SL-SCH Data transfer and SL-PRS transmission + +### 5.22.1 SL-SCH Data and SL-PRS transmission + +#### 5.22.1.1 SL Grant reception and SCI transmission + +Sidelink grant is received dynamically on the PDCCH, configured semi-persistently by RRC or autonomously selected by the MAC entity. The MAC entity may have a sidelink grant on an active SL BWP to determine a set of PSCCH duration(s) in which transmission of SCI occurs and a set of PSSCH duration(s) in which transmission of SL-SCH associated with the SCI occurs. The MAC entity may have a sidelink grant on the SL-PRS shared resource pool of an active BWP to determine a set of PSCCH duration(s) in which transmission of SCI occurs and a set of SL-PRS transmission occasion(s) and PSSCH duration(s) in which transmission of SL-PRS and SL-SCH associated with the SCI occur. The MAC entity may have a sidelink grant on the SL-PRS dedicated resource pool of an active BWP to determine a set of PSCCH duration(s) in which transmission of SCI occurs and a set of SL-PRS transmission occasion(s) in which transmission of SL-PRS associated to the SCI occurs. A sidelink grant addressed to SL-CS-RNTI with NDI = 1 is considered as a dynamic sidelink grant. A sidelink grant addressed to SL-PRS-CS-RNTI with Activation/Release indication = 1 as in clause 7.3.1.4.3 in TS 38.212 [9] is considered as a dynamic sidelink grant. + +If the MAC entity has been configured with Sidelink resource allocation mode 1 as indicated in TS 38.331 [5] or if the MAC entity has been configured with Sidelink resource allocation scheme 1 as indicated in TS 38.331 [5] and PDCCH is received for resource allocation on SL-PRS shared resource pool, the MAC entity shall for each PDCCH occasion and for each grant received for this PDCCH occasion: + +1> if a sidelink grant has been received on the PDCCH for the MAC entity's SL-RNTI: + +2> if the NDI received on the PDCCH has not been toggled compared to the value in the previously received HARQ information for the HARQ Process ID: + +3> use the received sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) and SL-PRS transmission occasion(s), if available, for one or more retransmissions of a single MAC PDU for the corresponding Sidelink process according to clause 8.1.2 of TS 38.214 [7] and SL-PRS according to clause 8.1.4 of TS 38.214 [7]. + +2> else: + +3> use the received sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) and SL-PRS transmission occasion(s), if available, for initial transmission and, if available, retransmission(s) of a single MAC PDU and SL-PRS according to clause 8.1.2 of TS 38.214 [7]. + +NOTE 0: When SL-PRS is transmitted on SL-PRS shared resource pool, the PSSCH duration(s) and SL-PRS transmission occasion(s) are determined only after the LCP procedure in clause 5.22.1.4.1. + +1> else if a sidelink grant has been received on the PDCCH for the MAC entity's SL-CS-RNTI: + +- 2> if PDCCH contents indicate retransmission(s) for the identified HARQ process ID that has been set for an activated configured sidelink grant identified by *sl-ConfigIndexCG*: + - 3> use the received sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) and SL-PRS transmission occasion(s), if available, for one or more retransmissions of a single MAC PDU and SL-PRS according to clause 8.1.2 of TS 38.214 [7]. +- 2> else if PDCCH contents indicate configured grant Type 2 deactivation for a configured sidelink grant: + - 3> trigger configured sidelink grant confirmation for the configured sidelink grant. +- 2> else if PDCCH contents indicate configured grant Type 2 activation for a configured sidelink grant: + - 3> trigger configured sidelink grant confirmation for the configured sidelink grant; + - 3> store the configured sidelink grant; + - 3> initialise or re-initialise the configured sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations for transmissions of multiple MAC PDUs according to clause 8.1.2 of TS 38.214 [7] and the set of SL-PRS transmission occasions for transmission of multiple SL-PRS according to clause of 8.2.4 of TS 38.214 [7], if available. +- 1> if a dynamic sidelink grant is available for retransmission(s) of a MAC PDU which has been positively acknowledged as specified in clause 5.22.1.3.1a: + - 2> clear the PSCCH duration(s) and PSSCH duration(s) corresponding to retransmission(s) of the MAC PDU from the sidelink grant. + +If the MAC entity has been configured with Sidelink resource allocation scheme 1 as in TS 38.331 [5] and PDCCH is received for resource allocation on SL-PRS dedicated resource pool, the MAC entity shall for each PDCCH occasion: + +- 1> if a sidelink grant has been received on the PDCCH for the MAC entity's SL-PRS-RNTI: (i.e., dynamic grant) + - 2> use the received sidelink grant to determine the PSCCH duration(s) and the corresponding SL-PRS occasion(s) for the transmission of SL-PRS. +- 1> else if a sidelink grant has been received on the PDCCH for MAC entity's SL-PRS-CS-RNTI: (i.e., configured sidelink grant type 2) + - 2> if the PDCCH content indicates the configured grant Type 2 activation for a configured sidelink grant: + - 3> store the configured sidelink grant; + - 3> trigger configured grant confirmation for the configured sidelink grant; + - 3> initialise or re-initialise the configured sidelink grant to determine the set of PSCCH duration(s) and the corresponding SL-PRS occasion for the transmission of SL-PRS. + - 2> else if the PDCCH content indicates the configured Type 2 deactivation for a configured sidelink grant: + - 3> trigger configured grant confirmation for the configured sidelink grant. + +If the MAC entity has been configured with Sidelink resource allocation mode 2 to transmit or Sidelink resource allocation scheme 2 using pool(s) of resources in one or multiple carriers as indicated in TS 38.331 [5] or TS 36.331 [21] based on full sensing, or partial sensing, or random selection or any combination(s), the MAC entity shall for each Sidelink process: + +NOTE 0A: For SL-PRS transmission by Sidelink resource allocation scheme 2 on SL-PRS dedicated resource pool, partial sensing is not supported. + +NOTE 1: If the MAC entity is configured with Sidelink resource allocation mode 2 or Sidelink resource allocation scheme 2 to transmit using a pool of resources in one or multiple carriers as indicated in TS 38.331 [5] or TS 36.331 [21], the MAC entity can create a selected sidelink grant on the pool of resources based on random selection, or partial sensing, or full sensing only after releasing configured sidelink grant(s), if any. + +NOTE 2: The MAC entity expects that PSFCH is always configured by RRC for at least one pool of resources in *sl-TxPoolSelectedNormal* and for the resource pool in *sl-TxPoolExceptional* in case that at least a logical channel configured with *sl-HARQ-FeedbackEnabled* is set to *enabled*. + +NOTE 2A: For the transmission of Sidelink Inter-UE Coordination Request MAC CE, the MAC entity selects the TX pool of resource where the IUC resource set is required. For the transmission of Sidelink Inter-UE Coordination Information MAC CE, the MAC entity selects the TX pool of resource where the IUC resource set is located. + +NOTE 2B: For dynamic co-channel coexistence of LTE sidelink and NR sidelink, when the same TB or different TBs are transmitted on the NR SL slots overlapping with the LTE SL subframe, it is up to UE implementation how to avoid transmitting NR PSCCH/PSSCH only in the subsequent NR SL slot overlapping with an LTE SL subframe for NR PSCCH/PSSCH transmissions of 30kHz SCS. + +1) if the MAC entity has selected to create a selected sidelink grant corresponding to transmissions of multiple MAC PDUs, and SL data is available in a logical channel; or + +1) if the MAC entity has selected to create a selected sidelink grant corresponding to transmission(s) of multiple SL-PRS(s), which have been triggered by the upper layer or by the reception of a SCI from a peer UE; 2) if the MAC entity has not selected a pool of resources allowed for the logical channel or SL-PRS transmission: + +3) if single carrier frequency is configured: + +4) if SL data is available in the logical channel for NR sidelink discovery: + +5) if *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon* is configured according to TS 38.331 [5]: + +6) select the *sl-DiscTxPoolSelected* configured in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon* for the transmission of NR sidelink discovery message. + +5) else: + +6) select any pool of resources among the configured pools of resources except for SL-PRS dedicated resource pool, if configured. + +4) else if SL data is available in the logical channel for BRID for A2X communication: + +5) if *sl-A2X-Service* in *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* indicates *brid* or *bridAndDAA* according to TS 38.331 [5]: + +6) select the *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* for the transmission of SL data for A2X communication. + +5) else: + +6) select any pool of resources among the configured pools of resources. + +4) else if SL data is available in the logical channel for DAA for A2X communication: + +5) if *sl-A2X-Service* in *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* indicates *daa* or *bridAndDAA* according to TS 38.331 [5]: + +6) select the *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* for the transmission of SL data for A2X communication. + +5) else: + +6) select any pool of resources among the configured pools of resources. + +NOTE 2C: The MAC entity identifies the logical channel(s) for BRID or DAA based on the QoS information associated to BRID or DAA, i.e. PQI(s), from upper layers. + +4) else if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the logical channel: + +- 5> select any pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig*, *sl-BWP-DiscPoolConfigCommon*, *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X*, if configured or SL-PRS dedicated resource pool, if configured. +- 4> else if SL-PRS is pending for transmission: + - 5> select any resource pool among the resource pool(s) allowing for SL-PRS transmission. +- 4> else: + - 5> select any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig*, *sl-BWP-DiscPoolConfigCommon*, *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X*, if configured or SL-PRS dedicated resource pool, if configured. +- 3> else (i.e. multiple carrier frequencies are configured): + - 4> trigger the TX carrier (re-)selection procedure as specified in clause 5.22.1.11. +- 2> if Sidelink consistent LBT failure is detected as specified in clause 5.31.2 in all RB sets of the selected resource pool, if single carrier frequency is configured: + - 3> if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the logical channel: + - 4> select any pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured and the pool(s) in which all RB sets had Sidelink consistent LBT failure detected and not cancelled. + - 3> else: + - 4> select any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured and the pool(s) in which all RB sets had Sidelink consistent LBT failure detected and not cancelled. +- 2> perform the TX resource (re-)selection check on the selected pool of resources as specified in clause 5.22.1.2; + +NOTE 2D: It is up to UE implementation to select a resource pool that has at least one RB set in which SL consistent LBT failure was not detected. + +NOTE 3: The MAC entity continuously performs the TX resource (re-)selection check until the corresponding pool of resources is released by RRC or the MAC entity decides to cancel creating a selected sidelink grant corresponding to transmissions of multiple MAC PDUs. + +- 2> if the TX resource (re-)selection is triggered as the result of the TX resource (re-)selection check: + - 3> if *sl-lbt-FailureRecoveryConfig* is configured in the SL BWP: + - 4> indicate to the physical layer RB set information for which Sidelink consistent LBT failure was detected and not cancelled as specified in clause 5.31.2. + - 3> if the TX carrier (re-)selection procedure was triggered in above and one or more carriers have been (re-)selected in the TX carrier (re-)selection according to clause 5.22.1.11: + - 4> determine the order of the (re-)selected carriers, according to the decreasing order based on the highest priority of logical channels which are allowed on each (re-)selected carrier, and perform the resource selection procedure as specified in this clause for each Sidelink process on each (re-)selected carrier according to the order. + - 3> if one or multiple SL DRX(s) is configured in the destination UE(s) receiving SL-SCH data: + - 4> indicate to the physical layer SL DRX Active time in the destination UE(s) receiving SL-SCH data, as specified in clause 5.28.2. + +NOTE 3A: The MAC entity selects a value for the resource reservation interval which is larger than the remaining PDB of SL data available in the logical channel or remaining SL-PRS delay budget. + +- 3> randomly select, with equal probability, an integer value in the interval [5, 15] for the resource reservation interval higher than or equal to 100ms or in the interval for the resource reservation interval lower than 100ms and set *SL\_RESOURCE\_RESELECTION\_COUNTER* to the selected value; +- 3> if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> select one of the allowed values configured by RRC in *sl-ResourceReservePeriodList* and set the resource reservation interval, *Prspv\_TX*, with the selected value; + - 4> select the number of HARQ retransmissions from the allowed numbers, if configured by RRC, in *sl-MaxTxTransNumPSSCH* included in *sl-PSSCH-TxConfigList* and, if configured by RRC, overlapped in *sl-MaxTxTransNumPSSCH* indicated in *sl-CBR-PriorityTxConfigList* for the highest priority of the logical channel(s) and pending SL-PRS transmission(s), if available, allowed on the carrier and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding *sl-defaultTxConfigIndex* configured by RRC if CBR measurement results are not available or the corresponding *sl-DefaultCBR-PartialSensing* configured by RRC if partial sensing is selected and CBR measurement results are not available, or the corresponding *sl-DefaultCBR-RandomSelection* configured by RRC if random selection is selected and CBR measurement results are not available in case the *sl-TxPoolExceptional* is not used; + +NOTE 3Aa: For Multi-consecutive slots transmission as specified in clause 8.1.4 of TS 38.214 [7], during resource (re)selection, leave it to UE implementation, regarding whether to calculate the number of HARQ retransmissions from the allowed numbers based on the number of MCSt transmissions, or the number of slot(s) within Multi-consecutive slots transmission. + +- 4> select an amount of frequency resources within the range, if configured by RRC, between *sl-MinSubChannelNumPSSCH* and *sl-MaxSubchannelNumPSSCH* included in *sl-PSSCH-TxConfigList* and, if configured by RRC, overlapped between *sl-MinSubChannelNumPSSCH* and *sl-MaxSubchannelNumPSSCH* indicated in *sl-CBR-PriorityTxConfigList* for the highest priority of the logical channel(s) and pending SL-PRS transmission(s), if available, allowed on the carrier and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding *sl-defaultTxConfigIndex* configured by RRC if CBR measurement results are not available or the corresponding *sl-DefaultCBR-PartialSensing* configured by RRC if partial sensing is selected and CBR measurement results are not available, or the corresponding *sl-DefaultCBR-RandomSelection* configured by RRC if random selection is selected and CBR measurement results are not available in case the *sl-TxPoolExceptional* is not used; +- 3> else if the selected resource pool is SL-PRS dedicated resource pool: + - 4> select one of the allowed values configured by RRC in *sl-PRS-ResourceReservePeriodList* and set the resource reservation interval, , with the selected value; + - 4> select the number of SL-PRS retransmissions from the allowed numbers, if configured by RRC, in *sl-PRS-MaxNum-Transmissions* included in *sl-CBR-SL-PRS-TxConfigList*. +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is not configured by RRC: + - 4> if transmission based on random selection is configured by upper layers: + - 5> if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resource pool which occur within the SL DRX Active time, if configured, as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above, and the pool(s) in which all RB sets with Sidelink consistent LBT failure detected and not cancelled are excluded, if configured, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. + +NOTE 3Ab: When there are both SL data available in the logical channel(s) and SL-PRS pending for transmission, the resources are selected based on the shorter one of the corresponding remaining PDB and the corresponding remaining SL-PRS delay budget. + +- 5> else if the selected resource pool is SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resource pool as specified in clause 5.28.2, according to the remaining SL-PRS delay budget of the SL-PRS transmission(s). +- 4> else: + - 5> if *sl-NRPSSCH-EUTRA-ThresRSRP-List* is configured by the RRC: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier; + - 7> when SCS of NR SL is (pre-)configured as $\mu = 1$ : + - 8> select the time and frequency resources in the first of NR SL slots overlapping with an LTE SL subframe; + - 8> may additionally select the time and frequency resources in the subsequent NR SL slot overlapping with the LTE SL subframe. + - 5> else if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] which occur within the SL DRX Active time, if configured, as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. + - 5> else if the selected resource pool is SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by physical layer as clause 8.2.4 of TS 38.214 [7] as specified in clause 5.28.2, according to the remaining SL-PRS delay budget of the SL-PRS transmission(s). +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and preferred resource set is not received from a UE: + - 4> if transmission based on random selection is configured by upper layers: + - 5> if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources pool excluding all RB sets had Sidelink consistent LBT failure detected and not cancelled, if configured, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. + - 5> else if the selected resource pool is SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resource pool which as specified in clause 5.28.2, according to the remaining SL-PRS delay budget of the SL-PRS transmission(s). + - 4> else: + - 5> if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the remaining PDB of SL data + +available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. + +- 5> else if the selected resource pool is SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by physical layer as clause 8.2.4 of TS 38.214 [7], according to the remaining SL-PRS delay budget of the SL-PRS transmission. +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE does not have its own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE and if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resources for one transmission opportunity from the resources belonging to the received preferred resource set for SL-SCH data to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE has its own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE and if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resources for one transmission opportunity within the intersection of the received preferred resource set and the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] for an SL-SCH data to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. + - 4> if there are no resources within the intersection that can be selected as the time and frequency resources for the one transmission opportunity according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier. + - 5> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier. +- 3> use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for transmissions of PSCCH, PSSCH and SL-PRS corresponding to the number of transmission opportunities of MAC PDUs or SL-PRSs determined in TS 38.214 [7]. +- 3> if one or more SL-PRS retransmissions are selected and the selected resource pool is SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resources for one or more transmission opportunities from the available resources, according to the selected number of retransmissions and the remaining SL-PRS delay budget and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]; + - 4> use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for transmissions of PSCCH and SL-PRS corresponding to the number of retransmission opportunities of SL-PRS; + - 4> consider the first set of transmission opportunities as the initial transmission opportunities and the other set(s) of transmission opportunities as the retransmission opportunities; + - 4> consider the sets of initial transmission opportunities and retransmission opportunities as the selected sidelink grant. + +- 3> else if one or more HARQ retransmissions are selected and the selected resource pool is not SL-PRS dedicated resource pool: + - 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is not configured by RRC: + - 5> if transmission based on full sensing or partial sensing is configured by upper layers and there are available resources left in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7] for more transmission opportunities; or + - 5> if transmission based on random selection is configured by upper layers and there are available resources left in the resource pool for more transmission opportunities: + - 6> if *sl-NRPSSCH-EUTRA-ThresRSRP-List* is configured by the RRC: + - 7> randomly select the time and frequency resources for one or more transmission opportunities from the available resources, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + - 8> when SCS of NR SL is (pre-)configured as $\mu = 1$ : + - 9> select the time and frequency resources in the second of NR SL slots of NR SL slots overlapping with an LTE SL subframe to which the selected initial transmission resources belongs, or at least select the time and frequency resources in the first of NR SL slots overlapping with an LTE SL subframe. +- 6> else: + - 7> randomly select the time and frequency resources for one or more transmission opportunities from the available resources which occur within the SL DRX Active time, if configured, as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above, and the pool(s) in which all RB sets with Sidelink consistent LBT failure detected and not cancelled are excluded, if configured, according to the amount of selected frequency resources, the selected number of HARQ retransmissions, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. +- 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and preferred resource set is not received from a UE: + - 5> if transmission based on full sensing or partial sensing is configured by upper layers and there are available resources left in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7] for more transmission opportunities; or + - 5> if transmission based on random selection is configured by upper layers and there are available resources left in the resource pool for more transmission opportunities: + - 6> randomly select the time and frequency resources for one or more transmission opportunities from the available resources excluding all RB sets had Sidelink consistent LBT failure detected and not cancelled, if configured according to the amount of selected frequency resources, the selected number of HARQ retransmissions, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + +- 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE has own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE: + - 5> if there are available resources left in the intersection of the received preferred resource set and the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] for more transmission opportunities: + - 6> randomly select the time and frequency resources for one or more transmission opportunities from the available resources within the intersection for SL-SCH data to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the selected number of HARQ retransmissions, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + - 5> if the number of time and frequency resources that has been maximally selected for one or more transmission opportunities from the available resources within the intersection is smaller than the selected number of HARQ retransmissions and there are available resources left in the resources indicated by the physical layer for more transmission opportunities: + - 6> randomly select the time and frequency resources for the remaining transmission opportunities except for the selected resources within the intersection from the available resources outside the intersection but left in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the selected number of HARQ retransmissions, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + - 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE does not have own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE; and + - 4> if there are available resources left in the received preferred resource set for more transmission opportunities: + - 5> randomly select the time and frequency resources for one or more transmission opportunities from the available resources belonging to the received preferred resource set for SL-SCH data to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the selected number of HARQ retransmissions, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + - 4> use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for transmissions of PSCCH, PSSCH, if available and SL-PRS, if available corresponding to the number of retransmission opportunities of the MAC PDUs determined in TS 38.214 [7] or SL-PRS(s); + - 4> consider the first set of transmission opportunities as the initial transmission opportunities and the other set(s) of transmission opportunities as the retransmission opportunities; + - 4> consider the sets of initial transmission opportunities and retransmission opportunities as the selected sidelink grant. +- 3> else: + +- 4> consider the set as the selected sidelink grant. +- 3> use the selected sidelink grant to determine the set of PSCCH durations and the set of PSSCH durations and the set of SL-PRS transmission occasion(s), if available, according to TS 38.214 [7] if the selected resource pool is not SL-PRS dedicated resource pool or to determine the set of PSCCH durations and SL-PRS transmission occasion(s) if the selected resource pool is SL-PRS dedicated resource pool according to TS 38.214 [7]. +- 2> else if *SL\_RESOURCE\_RESELECTION\_COUNTER* = 0 and when *SL\_RESOURCE\_RESELECTION\_COUNTER* was equal to 1 the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is less than or equal to the probability configured by RRC in *sl-ProbResourceKeep*: + - 3> clear the selected sidelink grant, if available; + - 3> randomly select, with equal probability, an integer value in the interval [5, 15] for the resource reservation interval higher than or equal to 100ms or in the interval for the resource reservation interval lower than 100ms and set *SL\_RESOURCE\_RESELECTION\_COUNTER* to the selected value; + - 3> reuse the previously selected sidelink grant for the number of transmissions of the MAC PDUs or SL-PRS(s) determined in TS 38.214 [7] with the resource reservation interval to determine the set of PSCCH durations, the set of PSSCH durations, and the pending SL-PRS transmission(s), if available, according to TS 38.214 [7]. +- 1> if the MAC entity has selected to create a selected sidelink grant corresponding to transmission(s) of a single MAC PDU, and if SL data is available in a logical channel, or an SL-CSI reporting is triggered, or a Sidelink DRX Command indication is triggered or a Sidelink Inter-UE Coordination Information reporting is triggered, or a Sidelink Inter-UE Coordination Request is triggered: +- 1> if the MAC entity has selected to create a selected sidelink grant corresponding to transmission of a single SL-PRS transmission, which has been triggered by the upper layer or by the reception of a SCI from a peer UE: + - 2> if single carrier frequency is configured: + - 3> if SL data is available in the logical channel for NR sidelink discovery: + - 4> if *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon* is configured according to TS 38.331 [5]: + - 5> select the *sl-DiscTxPoolSelected* configured in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon* for the transmission of NR sidelink discovery message. + - 4> else: + - 5> select any pool of resources among the configured pools of resources except for SL-PRS dedicated resource pool, if configured. + - 3> else if SL data is available in the logical channel for BRID for A2X communication: + - 4> if *sl-A2X-Service* in *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* indicates *brid* or *bridAndDAA* according to TS 38.331 [5]: + - 5> select the *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* for the transmission of SL data for A2X communication. + - 4> else: + - 5> select any pool of resources among the configured pools of resources. + - 3> else if SL data is available in the logical channel for DAA for A2X communication: + - 4> if *sl-A2X-Service* in *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* indicates *daa* or *bridAndDAA* according to TS 38.331 [5]: + - 5> select the *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* for the transmission of SL data for A2X communication. + +- 4> else: + - 5> select any pool of resources among the configured pools of resources. + +NOTE 3Ac: The MAC entity identifies the logical channel(s) for BRID or DAA based on the QoS information associated to BRID or DAA, i.e. PQI(s), from upper layers. + +- 3> else if SL data for NR sidelink communication is available in the logical channel: + - 4> if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the logical channel: + - 5> select any pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig*, *sl-BWP-DiscPoolConfigCommon*, *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X*, if configured or SL-PRS dedicated resource pool, if configured. + - 4> else: + - 5> select any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig*, *sl-BWP-DiscPoolConfigCommon*, *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X*, if configured or SL-PRS dedicated resource pool, if configured. +- 3> else if an SL-CSI reporting or a Sidelink DRX Command or a Sidelink Inter-UE Coordination Request or a Sidelink Inter-UE Coordination Information is triggered: + - 4> select any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig*, *sl-BWP-DiscPoolConfigCommon*, *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X*, if configured or SL-PRS dedicated resource pool, if configured. +- 2> else (i.e. multiple carrier frequencies are configured): + - 3> trigger the TX carrier (re-)selection procedure as specified in clause 5.22.1.11. +- 2> if Sidelink consistent LBT Failure is detected as specified in clause 5.31.2 in all RB sets of the selected resource pool for the logical channel, if single carrier frequency is configured: + - 3> clear the selected sidelink grant on the selected pool of resources. + - 3> if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the logical channel: + - 4> select any pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured and the pool(s) including all RB sets for which Sidelink consistent LBT failures were detected. + - 3> else: + - 4> select any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured and the pool(s) including all RB sets for which Sidelink consistent LBT failures were detected. +- 2> perform the TX resource (re-)selection check on the selected pool of resources as specified in clause 5.22.1.2; +- 2> if the TX resource (re-)selection is triggered as the result of the TX resource (re-)selection check + - 3> if *sl-lbt-FailureRecoveryConfig* is configured in the SL BWP: + - 4> indicate to the physical layer RB set information for which Sidelink consistent LBT failure was detected as specified in clause 5.31.2. + - 3> if the TX carrier (re-)selection procedure was triggered in above and one or more carriers have been (re-)selected in the Tx carrier (re-)selection according to clause 5.22.1.11: + - 4> determine the order of the (re-)selected carriers, according to the decreasing order based on the highest priority of logical channels which are allowed on each (re-)selected carrier, and perform the resource selection procedure as specified in this clause for each Sidelink process on each (re-)selected carrier according to the order. + +- 3> if one or multiple SL DRX(s) is configured in the destination UE(s) receiving SL-SCH data: + - 4> indicate to the physical layer SL DRX Active time in the destination UE(s) receiving SL-SCH data, as specified in clause 5.28.2. +- 3> if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> select the number of HARQ retransmissions from the allowed numbers, if configured by RRC, in *sl-MaxTxTransNumPSSCH* included in *sl-PSSCH-TxConfigList* and, if configured by RRC, overlapped in *sl-MaxTxTransNumPSSCH* indicated in *sl-CBR-PriorityTxConfigList* for the highest priority of the logical channel(s) and pending SL-PRS transmission(s), if available allowed on the carrier and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding *sl-defaultTxConfigIndex* configured by RRC if CBR measurement results are not available or the corresponding *sl-DefaultCBR-PartialSensing* configured by RRC if partial sensing is selected and CBR measurement results are not available, or the corresponding *sl-DefaultCBR-RandomSelection* configured by RRC if random selection is selected and CBR measurement results are not available in case the *sl-TxPoolExceptional* is not used; + +NOTE 3Ad: For Multi-consecutive slots transmission as specified in clause 8.1.4 of TS 38.214 [7], during resource (re)selection, leave it to UE implementation, regarding whether to calculate the number of HARQ retransmissions from the allowed numbers based on the number of MCSt transmissions, or the number of slot(s) within Multi-consecutive slots transmission. + +- 4> select an amount of frequency resources within the range, if configured by RRC, between *sl-MinSubChannelNumPSSCH* and *sl-MaxSubChannelNumPSSCH* included in *sl-PSSCH-TxConfigList* and, if configured by RRC, overlapped between *sl-MinSubChannelNumPSSCH* and *sl-MaxSubChannelNumPSSCH* indicated in *sl-CBR-PriorityTxConfigList* for the highest priority of the logical channel(s) and pending SL-PRS transmission(s), if available allowed on the carrier and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding *sl-defaultTxConfigIndex* configured by RRC if CBR measurement results are not available or the corresponding *sl-DefaultCBR-PartialSensing* configured by RRC if partial sensing is selected and CBR measurement results are not available, or the corresponding *sl-DefaultCBR-RandomSelection* configured by RRC if random selection is selected and CBR measurement results are not available in case the *sl-TxPoolExceptional* is not used; + +- 3> if the selected resource pool is SL-PRS dedicated resource pool: + - 4> select the number of SL-PRS retransmissions from the allowed numbers, if configured by RRC, in *sl-PRS-MaxNum-Transmissions* included in *sl-CBR-SL-PRS-TxConfigList*. +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is not configured by RRC: + - 4> if transmission based on random selection is configured by upper layers: + - 5> if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources pool which occur within the SL DRX Active time, if configured, as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above, if configured and the pool(s) in which all RB sets had Sidelink consistent LBT failure detected and not cancelled, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier, and the latency requirement of the triggered SL-CSI reporting. + - 5> if the selected resource pool is SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resource pool as specified in clause 5.28.2, according to the remaining SL-PRS delay budget of the SL-PRS transmission. + - 4> else: + - 5> if *sl-NRPSSCH-EUTRA-ThresRSRP-List* is configured by the RRC: + +- 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting; + - 7> when SCS of NR SL is (pre-)configured as $\mu = 1$ : + - 8> select the time and frequency resources in the first of NR SL slots overlapping with an LTE SL subframe; + - 8> may additionally select the time and frequency resources in the subsequent NR SL slot overlapping with the LTE SL subframe. + - 5> else if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] which occur within the SL DRX Active time, if configured, as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting. + - 5> if the selected resource pool is SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by physical layer as clause 8.2.4 of TS 38.214 [7] as specified in clause 5.28.2, according to the remaining SL-PRS delay budget of the SL-PRS transmission. +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and preferred resource set is not received from a UE: + - 4> if transmission based on random selection is configured by upper layers: + - 5> if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources pool excluding all RB sets had Sidelink consistent LBT failure detected and not cancelled, if configured according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting. + - 4> else: + - 5> if the selected resource pool is not SL-PRS dedicated resource pool: + - 6> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting. + - 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE does not have own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE and if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resources for one transmission opportunity from the resources belonging to the received preferred resource set for a MAC PDU to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget + +of the SL-PRS transmission(s), if available, allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting. + +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE has own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE and if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resources for one transmission opportunity within the intersection of the received preferred resource set and the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] for a MAC PDU to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting; + - 4> if there are no resources within the intersection that can be selected as the time and frequency resources for the one transmission opportunity according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier. + - 5> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s), and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting. +- 3> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE determines the resources for Sidelink Inter-UE Coordination Information transmission upon explicit request from a UE: + - 4> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting and the latency requirement of the Sidelink Inter-UE Coordination Information transmission, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available. +- 3> if one or more SL-PRS retransmissions are selected and the selected resource pool is SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resources for one or more transmission opportunities from the available resources, according to the selected number of retransmissions and the remaining SL-PRS delay budget and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]; + - 4> consider the first set of transmission opportunities as the initial transmission opportunities and the other set(s) of transmission opportunities as the retransmission opportunities; + - 4> consider the sets of initial transmission opportunities and retransmission opportunities as the selected sidelink grant. +- 3> else if one or more HARQ retransmissions are selected and the selected resource pool is not SL-PRS dedicated resource pool: + - 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is not configured by RRC: + - 5> if transmission based on full sensing or partial sensing is configured by upper layers and there are available resources left in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7] for more transmission opportunities; or + - 5> if transmission based on random selection is configured by upper layers and there are available resources left in the resources pool for more transmission opportunities: + - 6> if *sl-NRPSSCH-EUTRA-ThresRSRP-List* is configured by the RRC: + +- 7> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources, and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]; + - 8> when SCS of NR SL is (pre-)configured as $\mu = 1$ : + - 9> select the time and frequency resources in the second of NR SL slots of NR SL slots overlapping with an LTE SL subframe to which the selected initial transmission resources belongs, or at least select the time and frequency resources in the first of NR SL slots overlapping with an LTE SL subframe. +- 6> else: + - 7> randomly select the time and frequency resources for one or more transmission opportunities from the available resources which occur within the SL DRX Active time, if configured, as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above, and the pool(s) in which all RB sets with Sidelink consistent LBT failure detected and not cancelled are excluded, if configured, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources, and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]; +- 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and preferred resource set is not received from a UE: + - 5> if transmission based on sensing is configured by upper layers and there are available resources left in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7] for more transmission opportunities; or + - 5> if transmission based on random selection is configured by upper layers and there are available resources left in the resource pool for more transmission opportunities: + - 6> randomly select the time and frequency resources for one or more transmission opportunities from the available resources excluding all RB sets had Sidelink consistent LBT failure detected and not cancelled, if configured according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. +- 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE has own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE: + - 5> if there are available resources left in the intersection of the received preferred resource set and the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] for more transmission opportunities: + - 6> randomly select the time and frequency resources for one or more transmission opportunities from the available resources within the intersection for a MAC PDU to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data + +available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + +- 5> if the number of time and frequency resources that has been maximally selected for one or more transmission opportunities from the available resources within the intersection is smaller than the selected number of HARQ retransmissions and there are available resources left in the resources indicated by the physical layer for more transmission opportunities: + - 6> randomly select the time and frequency resources for the remaining transmission opportunities except for the selected resources within the intersection from the available resources outside the intersection but left in the resources indicated by the physical layer according to clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + - 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE does not have own sensing result as specified in clause 8.1.4 of TS 38.214 [7] and if a preferred resource set is received from a UE; and + - 4> if there are available resources left in the received preferred resource set for more transmission opportunities: + - 5> randomly select the time and frequency resources for one or more transmission opportunities from the available resources belonging to the received preferred resource set for a MAC PDU to be transmitted to the UE providing the preferred resource set, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available, by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources and that a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212 [9]. + - 4> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and when the UE determines the resources for Sidelink Inter-UE Coordination Information transmission upon explicit request from a UE: + - 5> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the remaining PDB of SL data available in the logical channel(s) allowed on the carrier, and/or the latency requirement of the triggered SL-CSI reporting and the latency requirement of the Sidelink Inter-UE Coordination Information transmission, and the remaining SL-PRS delay budget of the SL-PRS transmission(s), if available. + - 4> consider a transmission opportunity which comes first in time as the initial transmission opportunity and other transmission opportunities as the retransmission opportunities; + - 4> consider all the transmission opportunities as the selected sidelink grant. +- 3> else: +- 4> consider the set as the selected sidelink grant. +- 3> use the selected sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) and the SL-PRS transmission occasion(s), if available, according to TS 38.214 [7] if the selected resource pool is not SL- + +PRS dedicated resource pool or to determine the PSCCH duration(s) and SL-PRS transmission occasion(s) if the selected resource pool is SL-PRS dedicated resource pool according to TS 38.214 [7]. + +- NOTE 3Ae: MAC entity, based on UE implementation, decides whether to indicate the number of consecutive slots for Multi-consecutive slots transmission as specified in clause 8.1.4 of TS 38.214 [7] larger than 1. +- NOTE 3Af: MAC entity, based on UE implementation, decides the value of the number of consecutive slots for Multi-consecutive slots transmission if it decides the number of consecutive slots for Multi-consecutive slots transmission larger than 1, as long as it meets the CAPC maximum COT duration requirement as specified in TS 37.213 [18]. +- NOTE 3Ag: When the MAC entity selects the time and frequency resources from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], it is up to the UE implementation whether to randomly select resources for transmission opportunities from the resources indicated by the physical layer or to select resources in consecutive slots by UE implementation from the resources indicated by the physical layer. +- NOTE 3Ah: For a resource pool configured with PSFCH resource, UE cannot select consecutive slots for SL transmissions of a single TB for Multi-consecutive slots transmission. +- NOTE 3Ai: UE may avoid selection of N consecutive resource(s) before a reserved resource of its own, where the selection of N is up to UE implementation from {0,1,2}. UE may avoid selection of M consecutive resource(s) after a reserved resource of its own, where the selection of M is up to UE implementation (at least including 0). +- NOTE 3Aj: If configured, UE may avoid selection of N consecutive resource(s) before a reserved resource of other UE when the L1 SL priority value for the transmission is higher than the L1 SL priority value of the reserved resource, where the selection of N is up to UE implementation from {0,1,2}. UE may avoid selection of M consecutive resource(s) after a reserved resource of other UE when the transmitting symbols of the reserved resource overlap with LBT of its own selected resource, where the selection of M is up to UE implementation from {0,1,2}. It is up to UE implementation how the physical layer reports detected reserved resources to MAC layer. +- NOTE 3Ak: If configured, if transmission in slot(s) at least before a reserved resource of other UE is able to share its initiated COT to the reservation, UE may prioritize/select resource(s) in the slot(s) for transmission. It is up to UE implementation how the physical layer reports detected reserved resources to MAC layer. +- NOTE 3A1: If *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC and if multiple preferred resource sets are received from the same UE, it is up to UE implementation to use one or multiple of them in its resource (re)selection. +- NOTE 3B1: If retransmission resource(s) cannot be selected by ensuring that the resource(s) can be indicated by the time resource assignment of a prior SCI, how to select the time and frequency resources for one or more transmission opportunities from the available resources is left for UE implementation by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources. +- NOTE 3B2: When the UE receives both a single preferred resource set and a single non-preferred resource set from the same peer UE or different peer UEs, when the UE has own sensing results, it is up to the UE implementation to use the preferred resource set in its resource (re)selection for transmissions to the peer UE providing the preferred resource set. +- NOTE 3B3: The UE is not required to use any resource from the preferred resource set in its resource (re)selection if that resource is earlier than (++) after the resource of Inter-UE Coordination Information transmission, where $\Delta$ is equal to (+) when only MAC CE is used for inter-UE Coordination Information transmission, or $\Delta$ is equal to $\Delta_{SCI}$ when MAC CE and SCI format 2-C are both used for Inter-UE Coordination Information transmission. The case when $\Delta$ is equal to $\Delta_{SCI}$ is assuming that SCI format 2-C is received. $\Delta$ and $\Delta_{SCI}$ are specified in clause 8.1.4 of TS 38.214 [7]. +- NOTE 3B4: For Inter-UE Coordination Information triggered by an explicit Inter-UE Coordination Request in Scheme 1, whether or not to transmit the Inter-UE Coordination Information upon the Inter-UE Coordination Request reception is determined by UE implementation subject to Release-16 procedure of UL/SL prioritization, LTE SL/NR SL prioritization, and congestion control. + +NOTE 3B5: If configured by RRC, *sl-IUC-Explicit* set to *enabled* and an SL-IUC request is received for the Source Layer-2 ID and Destination Layer-2 ID pair of a unicast, MAC layer indicates to physical layer the resource selection window, resource set type (i.e., preferred resource set), L1 priority, the number of sub-channels to be used for the PSSCH/PSCCH transmission and the resource reservation period for preferred resource set. If configured by RRC, *sl-IUC-Explicit* set to *enabled* and an SL-IUC request is received for the Source Layer-2 ID and Destination Layer-2 ID pair of a unicast, MAC layer indicates to physical layer resource set type (i.e., non-preferred resource set) and the resource selection window for non-preferred resource set. + +NOTE 3B6: If either *sl-IUC-Explicit* or *sl-IUC-Condition* is configured as *enabled*, UE considers the reception of preferred and non-preferred resource is enabled. + +NOTE 3B7: When *sl-TriggerConditionCoordInfo* is set to value 0, for groupcast or broadcast of Inter-UE Coordination Information triggered by a condition in Scheme 1, which Destination Layer-2 ID (and the corresponding cast-type) a UE selects among Destination Layer-2 IDs that are already used or interested in NR sidelink transmission is up to the UE implementation. + +1> if a selected sidelink grant is available for retransmission(s) of a MAC PDU which has been positively acknowledged as specified in clause 5.22.1.3.3, except a positive acknowledgement to Multi-consecutive slots transmission (i.e., multiple TBs case) of the MAC PDU and there is remaining slot(s) for this MAC PDU: + +2> clear the PSCCH duration(s) and PSSCH duration(s) corresponding to retransmission(s) of the MAC PDU from the selected sidelink grant. + +NOTE 3C: How the MAC entity determines the remaining PDB of SL data is left to UE implementation. + +For a selected sidelink grant, the minimum time gap between any two selected resources comprises: + +- a time gap between the end of the last symbol of a PSSCH transmission of the first resource and the start of the first symbol of the corresponding PSFCH reception determined by *sl-MinTimeGapPSFCH* and *sl-PSFCH-Period* for the pool of resources; and +- For SL operation with shared spectrum channel access, the time gap between the end of the last symbol of a PSSCH transmission of the first resource and the start of the first symbol of the last corresponding PSFCH reception determined by *sl-MinTimeGapPSFCH* and *sl-PSFCH-Period* for the pool of resources; and +- a time required for PSFCH reception and processing plus sidelink retransmission preparation including multiplexing of necessary physical channels and any TX-RX/RX-TX switching time. + +NOTE : How to determine the time required for PSFCH reception and processing plus sidelink retransmission preparation is left to UE implementation. + +The MAC entity shall for each PSSCH duration not on SL-PRS dedicated resource pool: + +1> for each sidelink grant occurring in this PSSCH duration: + +2> select a MCS table allowed in the pool of resource which is associated with the sidelink grant; + +NOTE 4a: MCS table selection is up to UE implementation if more than one MCS table is configured. + +2> if the MAC entity has been configured with Sidelink resource allocation mode 1 or Sidelink resource allocation Scheme 1 for SL-PRS transmission on SL-PRS shared resource pool: + +3> select a MCS which is, if configured, within the range that is configured by RRC between *sl-MinMCS-PSSCH* and *sl-MaxMCS-PSSCH* associated with the selected MCS table included in *sl-ConfigDedicatedNR*; + +3> set the resource reservation interval to 0ms. + +2> else if the MAC entity has been configured with Sidelink resource allocation mode 2 or Sidelink resource allocation Scheme 2 for SL-PRS transmission on SL-PRS shared resource pool: + +3> select a MCS which is, if configured, within the range, if configured by RRC, between *sl-MinMCS-PSSCH* and *sl-MaxMCS-PSSCH* associated with the selected MCS table included in *sl-PSSCH-TxConfigList* and, if configured by RRC, overlapped between *sl-MinMCS-PSSCH* and *sl-MaxMCS-PSSCH* associated with the selected MCS table indicated in *sl-CBR-PriorityTxConfigList* for the highest + +priority of the sidelink logical channel(s) in the MAC PDU or pending SL-PRS transmission(s), if available, and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding *sl-defaultTxConfigIndex* configured by RRC if CBR measurement results are not available or the corresponding *sl-DefaultCBR-PartialSensing* configured by RRC if partial sensing is selected and CBR measurement results are not available, or the corresponding *sl-DefaultCBR-RandomSelection* configured by RRC if random selection is selected and CBR measurement results are not available in case the *sl-TxPoolExceptional* is not used; + +3> if the MAC entity decides not to use the selected sidelink grant for the next PSSCH duration corresponding to an initial transmission opportunity: + +4> set the resource reservation interval to 0ms. + +3> else: + +4> set the resource reservation interval to the selected value. + +NOTE 5: MCS selection is up to UE implementation if the MCS or the corresponding range is not configured by RRC. + +2> if the configured sidelink grant has been activated and this PSSCH duration corresponds to the first PSSCH transmission opportunity within this *sl-PeriodCG* of the configured sidelink grant: + +3> set the HARQ Process ID to the HARQ Process ID associated with this PSSCH duration and, if available, all subsequent PSSCH duration(s) occurring in this *sl-PeriodCG* for the configured sidelink grant; + +3> determine that this PSSCH duration is used for initial transmission; + +3> flush the HARQ buffer of Sidelink process associated with the HARQ Process ID. + +2> deliver the sidelink grant, the selected MCS, and the associated HARQ information to the Sidelink HARQ Entity for this PSSCH duration. + +The MAC entity shall for each PSCCH duration on SL-PRS dedicated resource pool: + +1> if the MAC entity is not configured with multiple SL-PRS transmissions with Sidelink resource allocation scheme 2; or + +1> if the MAC entity is configured with Sidelink resource allocation scheme 1: + +2> set the resource reservation period to 0. + +1> else if the MAC entity is configured with multiple SL-PRS transmission with Sidelink resource allocation scheme 2: + +2> set the resource reservation period to the selected value. + +1> if the configured sidelink grant has been activated and this PSSCH duration corresponds to the first PSSCH transmission opportunity within this *sl-PeriodCG* of the configured sidelink grant: + +2> set the SL-PRS Process ID to the SL-PRS Process ID associated with this PSSCH duration and, if available, all subsequent SL-PRS transmission occasion(s) occurring in this *sl-PeriodCG* for the configured sidelink grant; + +2> determine that this SL-PRS transmission occasion is used for initial transmission. + +1> process the sidelink grant according to clause 5.22.1.3.4 with the corresponding SL-PRS transmission information. + +For configured sidelink grants not on SL-PRS dedicated resource pool, the HARQ Process ID associated with the first slot of an SL transmission is derived from the following equation: + +$$\text{HARQ Process ID} = [\text{floor}(\text{CURRENT\_slot} / \text{PeriodicitySL})] \bmod \text{sl-NrOfHARQ-Processes} \\ + \text{sl-HARQ-ProcID-offset}$$ + +For configured sidelink grant on SL-PRS dedicated resource pool, the SL-PRS Process ID associated with the first slot of an SL transmission is derived from the following equation: + +$$\text{SL-PRS Process ID} = [\text{floor}(\text{CURRENT\_slot} / \text{PeriodicitySL})] \bmod [\text{nrOfSL-PRSProc}]$$ + +where *CURRENT\_slot* refers to current logical slot in the associated resource pool, and *PeriodicitySL* is defined in clause 5.8.3. + +### 5.22.1.2 TX resource (re-)selection check + +If the TX resource (re-)selection check procedure is triggered on the selected pool of resources for a Sidelink process according to clause 5.22.1.1, the MAC entity shall for the Sidelink process: + +- 1> if PSCCH duration(s) and 2nd stage SCI on PSSCH for all transmissions of a MAC PDU of any selected sidelink grant(s) are not in SL DRX Active time as specified in clause 5.28.3 of the destination that has data to be sent; or +- 1> if *SL\_RESOURCE\_RESELECTION\_COUNTER* = 0 and when *SL\_RESOURCE\_RESELECTION\_COUNTER* was equal to 1 the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is above the probability configured by RRC in *sl-ProbResourceKeep*; or +- 1> if the pool of resources is configured or reconfigured by RRC; or +- 1> if there is no selected sidelink grant on the selected pool of resources; or +- 1> if neither transmission nor retransmission has been performed by the MAC entity on any resource indicated in the selected sidelink grant during the last second; or +- 1> if *sl-ReselectAfter* is configured and the number of consecutive unused transmission opportunities on resources indicated in the selected sidelink grant, which is incremented by 1 when none of the resources of the selected sidelink grant within a resource reservation interval is used, is equal to *sl-ReselectAfter*; or +- 1> if the selected sidelink grant cannot accommodate a RLC SDU by using the maximum allowed MCS configured by RRC in *sl-MaxMCS-PSSCH* associated with the selected MCS table and the UE selects not to segment the RLC SDU; or + +NOTE 1: If the selected sidelink grant cannot accommodate the RLC SDU, it is left for UE implementation whether to perform segmentation or sidelink resource reselection. + +- 1> if transmission(s) with the selected sidelink grant cannot fulfil the remaining PDB of the data in a logical or the remaining SL-PRS delay budget for SL-PRS transmission, if available channel, and the MAC entity selects not to perform transmission(s) corresponding to a single MAC PDU or SL-PRS transmission; or +- 1> if Sidelink consistent LBT failure is detected as specified in clause 5.31.2 in some RB set(s) of the selected resource pool that spans multiple RB sets for the logical channel, if single carrier frequency is configured; or +- 1> if a MAC PDU is not transmitted (i.e. initial transmission or retransmission) in any of the resources for this MAC PDU that are associated with the sidelink process for Multi-consecutive slots transmission due to the Sidelink LBT failure: + +NOTE 2: If the remaining PDB is not met, it is left for UE implementation whether to perform transmission(s) corresponding to single MAC PDU or sidelink resource reselection. + +NOTE 3: It is left for UE implementation whether to trigger the TX resource (re-)selection due to the latency requirement of the MAC CEs triggered according to clause 5.22.1.7 and clause 5.22.1.10.1. + +- 2> if multiple carrier frequencies are configured: + - 3> trigger the TX carrier (re-)selection procedure as specified in clause 5.22.1.11. +- 2> clear the selected sidelink grant associated to the Sidelink process, if available; +- 2> trigger the TX resource (re-)selection. + +NOTE 4: Void. + +NOTE 5: Void. + +### 5.22.1.2a Re-evaluation and Pre-emption + +A resource(s) of the selected sidelink grant for a MAC PDU to transmit from multiplexing and assembly entity or for a SL-PRS transmission is re-evaluated by physical layer at $T_3$ before the slot where the SCI indicating the resource(s) is signalled at first time as specified in clause 8.1.4 of TS 38.214 [7]. + +A resource(s) of the selected sidelink grant which has been indicated by a prior SCI for a MAC PDU to transmit from multiplexing and assembly entity or for a SL-PRS transmission could be checked for pre-emption by physical layer at $T_3$ before the slot where the resource(s) is located as specified in clause 8.1.4 of TS 38.214 [7]. + +NOTE 1: It is up to UE implementation to re-evaluate or pre-empt before ' $m - T_3$ ' or after ' $m - T_3$ ' but before ' $m$ '. For re-evaluation, $m$ is the slot where the SCI indicating the resource(s) is signalled at first time as specified in clause 8.1.4 of TS 38.214. For pre-emption, $m$ is the slot where the resource(s) is located as specified in clause 8.1.4 of TS 38.214. + +If the MAC entity has been configured with Sidelink resource allocation mode 2 or Sidelink resource allocation scheme 2 to transmit using pool(s) of resources in a carrier as indicated in TS 38.331 [5] or TS 36.331 [21] based on sensing or random selection the MAC entity shall for each Sidelink process or for each SL-PRS transmission: + +- 1> if a resource(s) of the selected sidelink grant which has not been identified by a prior SCI is indicated for re-evaluation by the physical layer as specified in clause 8.1.4 of TS 38.214 [7]; + - 2> remove the resource(s) from the selected sidelink grant associated to the Sidelink process or SL-PRS transmission; + - 2> if the selected resource pool is not SL-PRS dedicated resource pool: + - 3> randomly select the time and frequency resource from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] for either the removed resource or the dropped resource, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of either SL data available in the logical channel(s), and the remaining SL-PRS delay budget for SL-PRS transmission, if available, by ensuring the minimum time gap between any two selected resources of the selected sidelink grant in case that PSFCH is configured for this pool of resources, and that a resource can be indicated by the time resource assignment of an SCI for a retransmission according to clause 8.3.1.1 of TS 38.212 [9]; + - 2> else if the selected resource pool is SL-PRS dedicated resource pool: + - 3> randomly select the time and frequency resource from the resources indicated by the physical layer as specified in clause 8.2.4 of TS 38.214 [7] for either the removed resource or the dropped resource, according to the selected number of SL-PRS retransmissions and the remaining SL-PRS delay budget for SL-PRS transmission and that a resource can be indicated by the time resource assignment of an SCI for a retransmission according to clause 8.3.1.2 of TS 38.212 [9]. + - 2> replace the removed or dropped resource(s) by the selected resource(s) for the selected sidelink grant. +- 1> if any resource(s) of the selected sidelink grant which has been indicated by a prior SCI is indicated for pre-emption by the physical layer as specified in clause 8.1.4 of TS 38.214 [7]: + - 2> remove the resource(s) from the selected sidelink grant associated to the Sidelink process; + - 2> if one or multiple SL DRX is configured: + - 3> if the selected resource pool is not SL-PRS dedicated resource pool: + - 4> randomly select the time and frequency resource from the resources later than the resources for either the removed resource or the dropped resource indicated by a prior SCI, from the resource indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] which occur within the SL DRX active time as specified in clause 5.28.3 of the destination UE selected for indicating to the physical layer the SL DRX active time above, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of either SL data available in the logical channel(s) by ensuring the minimum time gap between any two selected resources of the selected sidelink grant in case that PSFCH is configured for this pool of resources, and the remaining SL-PRS delay budget for SL-PRS transmission, if available, and that a resource can be indicated by the time resource assignment of an SCI for a retransmission according to clause 8.3.1.1 of TS 38.212 [9]. + +2> else: + +3> if the selected resource pool is not SL-PRS dedicated resource pool: + +4> randomly select the time and frequency resource from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] for either the removed resource or the dropped resource, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of either SL data available in the logical channel(s) by ensuring the minimum time gap between any two selected resources of the selected sidelink grant in case that PSFCH is configured for this pool of resources, and the remaining SL-PRS delay budget for SL-PRS transmission, if available, and that a resource can be indicated by the time resource assignment of an SCI for a retransmission according to clause 8.3.1.1 of TS 38.212 [9]. + +3> else if the selected resource pool is SL-PRS dedicated resource pool: + +4> randomly select the time and frequency resource from the resources indicated by the physical layer as specified in clause 8.2.4 of TS 38.214 [7] for either the removed resource or the dropped resource, according to the selected number of SL-PRS retransmissions and the remaining SL-PRS delay budget for SL-PRS transmission and that a resource can be indicated by the time resource assignment of an SCI for a retransmission according to clause 8.3.1.1 of TS 38.212 [9]. + +NOTE 2: If retransmission resource(s) cannot be selected by ensuring that the resource(s) can be indicated by the time resource assignment of a prior SCI, how to select the time and frequency resources for one or more transmission opportunities from the available resources is left for UE implementation by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources. + +2> replace the removed or dropped resource(s) by the selected resource(s) for the selected sidelink grant. + +NOTE 3: It is left for UE implementation to reselect any pre-selected but not reserved resource(s) other than the resource(s) indicated for pre-emption or re-evaluation by the physical layer during reselection triggered by re-evaluation or pre-emption indicated by the physical layer. + +NOTE 4: It is up to UE implementation whether to set the resource reservation interval in the re-selected resource to replace pre-empted resource. + +NOTE 5: It is up to UE implementation whether to trigger resource reselection due to de-prioritization as specified in clause 16.2.4 of TS 38.213 [6], clause 5.14.1.2.2 of TS 36.321 [22] and clause 5.22.1.3.1a. + +NOTE 6: For the selected sidelink grant corresponds to transmissions of multiple MAC PDU, it is up to UE implementation whether to apply re-evaluation check to the resources in non-initial reservation period that have been signalled neither in the immediate last nor in the current period. + +## 5.22.1.2b Re-selection for using a received resource conflict indication + +If the MAC entity has been configured with Sidelink resource allocation mode 2 or Sidelink resource allocation scheme 2 to transmit using pool(s) of resources in a carrier as indicated in TS 38.331 [5] based on full sensing, or partial sensing or random selection or any combination(s), the MAC entity shall for each Sidelink process: + +1> if *sl-interUECoordinationScheme2* enabling reception/transmission of a resource conflict indication is configured by RRC; and + +1> if the next resource of the selected sidelink grant which has been indicated by a prior SCI is overlapped with conflict resource(s) indicated by the physical layer as specified in clause 16.3.1 of TS 38.213 [6]: + +2> remove the resource from the selected sidelink grant associated to the Sidelink process; + +2> randomly select the time and frequency resource from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7] excluding the conflict resource(s) for the removed resource, according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of either SL data available in the logical channel(s), and the remaining SL-PRS delay budget for SL-PRS transmission, if available, by ensuring the minimum time gap between any two selected resources of the selected sidelink grant in case that PSFCH is configured for this pool of resources, and that a + +resource can be indicated by the time resource assignment of an SCI for a retransmission according to clause 8.3.1.1 of TS 38.212 [9]; + +NOTE 1: If retransmission resource cannot be selected by ensuring that the resource can be indicated by the time resource assignment of a prior SCI, how to select the time and frequency resource for more transmission opportunities from the available resources is left for UE implementation by ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources. + +2> replace the removed resource by the selected resource for the selected sidelink grant. + +NOTE 2: It is left for UE implementation to reselect any pre-selected but not reserved resource(s) other than the resource overlapping with the conflict resource(s) indicated by the physical layer during reselection triggered by the conflict resource(s) indicated by the physical layer. + +NOTE 3: It is up to UE implementation whether and how to set the resource reservation interval in the re-selected resource to replace the resource overlapping with the conflict resource(s) indicated by the physical layer. + +### 5.22.1.2c Resource re-selection from SL LBT Failure indication + +If the MAC entity has been configured with Sidelink resource allocation mode 2 to transmit using pool(s) of resources in a carrier as indicated in TS 38.331 [5] or TS 36.331 [21] based on sensing or random selection the MAC entity shall for each Sidelink process: + +1> if SL LBT failure indication is received from lower layers: + +2> for the resource(s) where SL LBT failure is detected from the selected sidelink grant associated to the Sidelink process: + +3> if transmission based on random selection is configured by upper layers: + +4> randomly select the time and frequency resources for one transmission opportunity from the resource pool excluding all RB sets for which Sidelink consistent LBT failures were detected and not cancelled, if configured according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) by ensuring the minimum time gap between any two selected resources of the selected sidelink grant in case that PSFCH is configured for this pool of resources. + +3> else: + +4> randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer as specified in clause 8.1.4 of TS 38.214 [7], according to the amount of selected frequency resources, the selected number of HARQ retransmissions and the remaining PDB of SL data available in the logical channel(s) by ensuring the minimum time gap between any two selected resources of the selected sidelink grant in case that PSFCH is configured for this pool of resources. + +### 5.22.1.3 Sidelink HARQ operation and SL-PRS transmission + +#### 5.22.1.3.1 Sidelink HARQ Entity + +The MAC entity is configured by upper layers to transmit using pool(s) of resources on one or more carriers as indicated in clause 5.8.8 of TS 38.331 [5]. For each carrier, the MAC entity includes at most one Sidelink HARQ entity for transmission on SL-SCH, which maintains a number of parallel Sidelink processes. + +The maximum number of transmitting Sidelink processes associated with the Sidelink HARQ Entity is 16. A sidelink process may be configured for transmissions of multiple MAC PDUs. For transmissions of multiple MAC PDUs with Sidelink resource allocation mode 2, the maximum number of transmitting Sidelink processes associated with the Sidelink HARQ Entity is 4. + +A delivered sidelink grant and its associated Sidelink transmission information are associated with a Sidelink process. Each Sidelink process supports one TB. + +For each sidelink grant, the Sidelink HARQ Entity shall: + +- 1> if the MAC entity determines that the sidelink grant is used for initial transmission as specified in clause 5.22.1.1; or +- 1> if the sidelink grant is a configured sidelink grant and no MAC PDU has been obtained in an *sl-PeriodCG* of the configured sidelink grant; or +- 1> if the sidelink grant is a dynamic sidelink grant or selected sidelink grant and no MAC PDU has been obtained in the previous sidelink grant when PSCCH duration(s) and 2nd stage SCI on PSSCH of the previous sidelink grant is not in SL DRX Active time as specified in clause 5.28.3 of any destination that has data to be sent: + +NOTE 1: Void. + +- 2> (re-)associate a Sidelink process to this grant, and for the associated Sidelink process: +- 2> if all PSCCH duration(s) and PSSCH duration(s) for initial transmission of a MAC PDU of the dynamic sidelink grant or the configured sidelink grant is not in SL DRX Active time as specified in clause 5.28.3 of the destination that has data to be sent: +- 3> ignore the sidelink grant. + +NOTE 1A: The Sidelink HARQ Entity will associate the selected sidelink grant to the Sidelink process determined by the MAC entity. + +- 2> else: +- 3> obtain the MAC PDU and SL-PRS, if any, to transmit from the Multiplexing and assembly entity, if any; +- 3> if a MAC PDU to transmit has been obtained: +- 4> if a HARQ Process ID has been set for the sidelink grant: +- 5> (re-)associate the HARQ Process ID corresponding to the sidelink grant to the Sidelink process. + +NOTE 1a: There is one-to-one mapping between a HARQ Process ID and a Sidelink process in the MAC entity configured with Sidelink resource allocation mode 1. + +- 4> determines Sidelink transmission information of the TB for the source and destination pair of the MAC PDU as follows: +- 5> set the Source Layer-1 ID to the 8 LSB of the Source Layer-2 ID of the MAC PDU; +- 5> set the Destination Layer-1 ID to the 16 LSB of the Destination Layer-2 ID of the MAC PDU; +- 5> (re-)associate the Sidelink process to a Sidelink process ID; + +NOTE 1b: How UE determine Sidelink process ID in SCI is left to UE implementation for NR sidelink. + +- 5> consider the NDI to have been toggled compared to the value of the previous transmission corresponding to the Sidelink identification information and the Sidelink process ID of the MAC PDU and set the NDI to the toggled value; + +NOTE 2: The initial value of the NDI set to the very first transmission for the associated Sidelink process is left to UE implementation. + +NOTE 3: Void. + +- 5> if the MAC PDU is for NR sidelink discovery: +- 6> set the cast type indicator to broadcast. +- 5> else: +- 6> set the cast type indicator to one of broadcast, groupcast and unicast as indicated by upper layers. +- 5> if HARQ feedback has been enabled for the MAC PDU according to clause 5.22.1.4.2; + +6> set the HARQ feedback enabled/disabled indicator to *enabled*. + +5> else: + +6> set the HARQ feedback enabled/disabled indicator to *disabled*. + +5> set the priority to the value of the highest priority of the logical channel(s), if any, and MAC CE(s), if included, in the MAC PDU and SL-PRS, if any; + +NOTE 3A: When determining Sidelink transmission information, the priority of the Sidelink Inter-UE Coordination Information MAC CE is the value configured in RRC parameters *sl-PriorityCoordInfoCondition* when triggered by a condition, or *sl-PriorityCoordInfoExplicit* when triggered by an explicit request. When determining Sidelink transmission information, the priority of the Sidelink Inter-UE Coordination Request MAC CE is the value configured in RRC parameter *sl-PriorityRequest*. When determining Sidelink transmission information, the priority of the Sidelink Inter-UE Coordination Information MAC CE is the value indicated in Priority field in the Sidelink Inter-UE Coordination Request MAC CE provided by the UE when triggered by an explicit request, if *sl-PriorityCoordInfoExplicit-r17* is not configured. When determining Sidelink transmission information for performing sensing and candidate resource selections in PHY, the priority value of the Sidelink Inter-UE Coordination Information MAC CE triggered under a condition is up to UE implementation, if *sl-PriorityCoordInfoCondition-r17* is not configured. When determining Sidelink transmission information for performing sensing and candidate resource selections in PHY, the priority value of Sidelink Inter-UE Coordination Request MAC CE is the same as that of a TB to be transmitted by the UE, if *sl-PriorityRequest-r17* is not configured. + +5> if HARQ feedback is enabled for groupcast: + +6> if both a group size and a member ID are provided by upper layers and the group size is not greater than the number of candidate PSFCH resources in a slot associated with this sidelink grant: + +7> select either positive-negative acknowledgement or negative-only acknowledgement. + +NOTE 4: Selection of positive-negative acknowledgement or negative-only acknowledgement is up to UE implementation. + +6> else: + +7> select negative-only acknowledgement. + +NOTE 5: UE operating in SL unlicensed does not use negative-only acknowledgement for groupcast HARQ. + +6> if negative-only acknowledgement is selected, UE's location information is available, and *sl-TransRange* has been configured for a logical channel in the MAC PDU, and *sl-ZoneConfig* is configured as specified in TS 38.331 [5]: + +7> set the communication range requirement to the value of the longest communication range of the logical channel(s) in the MAC PDU; + +7> determine the value of *sl-ZoneLength* corresponding to the communication range requirement and set *Zone\_id* to the value of *Zone\_id* calculated using the determined value of *sl-ZoneLength* as specified in TS 38.331 [5]. + +5> set the Redundancy version to the selected value. + +5> if the sidelink grant is associated with request from the higher layer for triggering the SL-PRS transmission of the peer UE identified by the Destination layer-2 ID: + +6> set the SL-PRS request to *request*. + +5> set the SL-PRS resource ID, if SL-PRS is available, within Sidelink transmission information. + +4> deliver the MAC PDU, the SL-PRS, if available, the sidelink grant and the Sidelink transmission information of the TB to the associated Sidelink process; + +4> instruct the associated Sidelink process to trigger a new transmission. + +3> else: + +4> flush the HARQ buffer of the associated Sidelink process. + +1> else (i.e. retransmission): + +2> if the HARQ Process ID corresponding to the sidelink grant received on PDCCH, the configured sidelink grant or the selected sidelink grant is associated to a Sidelink process of which HARQ buffer is empty; or + +2> if the HARQ Process ID corresponding to the sidelink grant received on PDCCH is not associated to any Sidelink process; or + +2> if PSCCH duration(s) and PSSCH duration(s) for one or more retransmissions of a MAC PDU of the dynamic sidelink grant or the configured sidelink grant is not in SL DRX Active time as specified in clause 5.28.3 of the destination that has data to be sent: + +3> ignore the sidelink grant. + +2> else: + +3> identify the Sidelink process associated with this grant, and for the associated Sidelink process: + +4> deliver the sidelink grant of the MAC PDU and the SL-PRS, if available, to the associated Sidelink process; + +4> instruct the associated Sidelink process to trigger a retransmission. + +#### 5.22.1.3.1a Sidelink process not associated with SL-PRS dedicated resource pool + +The Sidelink process is associated with a HARQ buffer. + +New transmissions and retransmissions are performed on the resource indicated in the sidelink grant as specified in clause 5.22.1.1 and with the MCS selected as specified in clause 8.1.3.1 of TS 38.214 [7] and clause 5.22.1.1. + +If the Sidelink process is configured to perform transmissions of multiple MAC PDUs with Sidelink resource allocation mode 2, the process maintains a counter *SL\_RESOURCE\_RESELECTION\_COUNTER*. For other configurations of the Sidelink process, this counter is not available. + +Priority of a MAC PDU and SL-PRS, if available, is determined by the highest priority of the logical channel(s), MAC CE(s) in the MAC PDU or SL-PRS. + +If the Sidelink HARQ Entity requests a new transmission, the Sidelink process shall: + +1> store the MAC PDU in the associated HARQ buffer; + +1> store the sidelink grant received from the Sidelink HARQ Entity; + +1> generate a transmission as described below. + +If the Sidelink HARQ Entity requests a retransmission, the Sidelink process shall: + +1> store the sidelink grant received from the Sidelink HARQ Entity; + +1> generate a transmission as described below. + +To generate a transmission, the Sidelink process shall: + +1> if there is no uplink transmission; or + +1> if the MAC entity is able to simultaneously perform uplink transmission(s) and sidelink transmission at the time of the transmission; or + +1> if the other MAC entity and the MAC entity are able to simultaneously perform uplink transmission(s) and sidelink transmission at the time of the transmission respectively; or + +- 1> if there is a MAC PDU to be transmitted for this duration in uplink, except a MAC PDU obtained from the Msg3 buffer, the MSGA buffer, or prioritized as specified in clause 5.4.2.2, and the sidelink transmission is prioritized over uplink transmission: + - 2> instruct the physical layer to transmit SCI according to the stored sidelink grant with the associated Sidelink transmission information; + - 2> instruct the physical layer to generate a transmission according to the stored sidelink grant; + - 2> if HARQ feedback has been enabled for the MAC PDU according to clause 5.22.1.4.2: + - 3> instruct the physical layer to monitor PSFCH for the transmission and perform PSFCH reception as specified in clause 5.22.1.3.2. + - 2> if *sl-PUCCH-Config* is configured by RRC for the stored sidelink grant: + - 3> determine transmission of an acknowledgement on the PUCCH as specified in clause 5.22.1.3.2. + - 1> if this transmission corresponds to the last transmission of the MAC PDU and SL-PRS, if available: + - 2> decrement *SL\_RESOURCE\_RESELECTION\_COUNTER* by 1, if available. +- NOTE 1: If the number of HARQ retransmissions selected by the MAC entity has been reached, or if a positive acknowledgement to a transmission of the MAC PDU has been received, or if a negative-only acknowledgement was enabled in the SCI and no negative acknowledgement was received for the transmission of the MAC PDU, the MAC entity determines this transmission corresponds to the last transmission of the MAC PDU for Sidelink resource allocation mode 2. How to determine the last transmission in other cases is up to UE implementation. +- 1> if *sl-MaxTransNum* corresponding to the highest priority of the logical channel(s) in the MAC PDU has been configured in *sl-CG-MaxTransNumList* for the sidelink grant by RRC and the number of transmissions of the MAC PDU has been reached to *sl-MaxTransNum*; or + - 1> if a positive acknowledgement to this transmission of the MAC PDU was received according to clause 5.22.1.3.2, except a positive acknowledgement to Multi-consecutive slots transmission (i.e., multiple TBs case) of the MAC PDU and there is remaining slot(s) for this MAC PDU; or + - 1> if negative-only acknowledgement was enabled in the SCI and no negative acknowledgement was received for this transmission of the MAC PDU according to clause 5.22.1.3.2: + - 2> flush the HARQ buffer of the associated Sidelink process. + +The transmission of the MAC PDU or SL-PRS, if available, is prioritized over uplink transmission(s) of the MAC entity or the other MAC entity if the following conditions are met: + +- 1> if the MAC entity is not able to perform this sidelink transmission simultaneously with all uplink transmission(s) at the time of the transmission, and +- 1> if none of the uplink transmission(s) is prioritized by upper layer according to TS 23.287 [19], and +- 1> if none of the NR uplink MAC PDU(s) includes any MAC CE prioritized as described in clause 5.4.3.1.3, and +- 1> if *ul-PrioritizationThres* is configured and if the value of the highest priority of logical channel(s) of all the NR uplink transmission(s) is not lower than *ul-PrioritizationThres*, and +- 1> if *sl-PrioritizationThres* is configured and if the value of the highest priority of logical channel(s) or MAC CE(s) in the MAC PDU is lower than *sl-PrioritizationThres*. + +NOTE 2: If the MAC entity is not able to perform this sidelink transmission simultaneously with all uplink transmissions as specified in clause 5.4.2.2 of TS 36.321 [22] at the time of the transmission, and prioritization-related information is not available prior to the time of this sidelink transmission due to processing time restriction, it is up to UE implementation whether this sidelink transmission is performed. + +### 5.22.1.3.2 PSFCH reception + +The MAC entity shall for each PSSCH transmission: + +- 1> if an acknowledgement corresponding to the PSSCH transmission in clause 5.22.1.3.1a is obtained from the physical layer: + - 2> deliver the acknowledgement to the corresponding Sidelink HARQ entity for the Sidelink process; +- 1> else: + - 2> deliver a negative acknowledgement to the corresponding Sidelink HARQ entity for the Sidelink process; +- 1> if the PSSCH transmission occurs for a pair of Source Layer-2 ID and Destination Layer-2 ID corresponding to a PC5-RRC connection which has been established by upper layers: + - 2> perform the HARQ-Based Sidelink RLF Detection procedure as specified in clause 5.22.1.3.3. + +If *sl-PUCCH-Config* is configured by RRC, the MAC entity shall for a PUCCH transmission occasion: + +- 1> if the *timeAlignmentTimer*, associated with the TAG containing the Serving Cell on which the HARQ feedback is to be transmitted, is stopped or expired, and the Serving Cell is not configured with two TAGs; or +- 1> if the Serving Cell on which the HARQ feedback is to be transmitted is configured with two TAGs and if the *timeAlignmentTimer* of the TAG, associated with the TCI state(s) used for transmitting the HARQ feedback, is stopped or expired: + - 2> not instruct the physical layer to generate acknowledgement(s) of the data in this TB. +- 1> else if all PSCCH duration(s) and PSSCH duration(s) for initial transmission of a MAC PDU of the dynamic sidelink grant or the configured sidelink grant is not in SL DRX Active time as specified in clause 5.28.3 of the destination that has data to be sent and the sidelink grant is ignored according to clause 5.22.1.3.1: + - 2> instruct the physical layer to signal a positive acknowledgement corresponding to the transmission on the PUCCH according to clause 16.5 of TS 38.213 [6]. +- 1> else if a MAC PDU has been obtained for a sidelink grant associated to the PUCCH transmission occasion in clause 5.22.1.3.1, the MAC entity shall: + - 2> if the most recent transmission of the MAC PDU was not prioritized as specified in clause 5.22.1.3.1a: + - 3> instruct the physical layer to signal a negative acknowledgement on the PUCCH according to clause 16.5 of TS 38.213 [6]. + - 2> else if HARQ feedback has been disabled for the MAC PDU and next retransmission(s) of the MAC PDU is not required: + - 3> instruct the physical layer to signal a positive acknowledgement corresponding to the transmission on the PUCCH according to clause 16.5 of TS 38.213 [6]. + - 2> else if HARQ feedback has been disabled for the MAC PDU, and no sidelink grant is available for next retransmission(s) of the MAC PDU (including immediately after all PSSCH duration(s) in an *sl-PeriodCG* for the sidelink grant, the number of transmissions of the MAC PDU has not reached *sl-MaxTransNum* corresponding to the highest priority of the logical channel(s) in the MAC PDU, if configured in *sl-CG-MaxTransNumList* for the sidelink grant by RRC), if any; or + - 2> else if PSCCH duration(s) and PSSCH duration(s) for one or more retransmissions of a MAC PDU of the dynamic sidelink grant or the configured sidelink grant is not in SL DRX Active time as specified in clause 5.28.3 of the destination that has data to be sent: + - 3> instruct the physical layer to signal a negative acknowledgement corresponding to the transmission on the PUCCH according to clause 16.5 of TS 38.213 [6]. + - 2> else: + - 3> instruct the physical layer to signal an acknowledgement corresponding to the transmission on the PUCCH according to clause 16.5 of TS 38.213 [6] +- 1> else: + +- 2> instruct the physical layer to signal a positive acknowledgement on the PUCCH according to clause 16.5 of TS 38.213 [6]. + +#### 5.22.1.3.3 HARQ-based Sidelink RLF detection + +For each carrier associated with a PC5-RRC connection, the HARQ-based Sidelink RLF detection procedure is used to detect Sidelink RLF based on a number of consecutive DTX on PSFCH reception occasions for a PC5-RRC connection. + +RRC configures the following parameter to control HARQ-based Sidelink RLF detection: + +- *sl-maxNumConsecutiveDTX*. + +The following UE variable is used for HARQ-based Sidelink RLF detection. + +- *numConsecutiveDTX*, which is maintained per carrier per PC5-RRC connection. + +For each carrier associated with a PC5-RRC connection, the Sidelink HARQ Entity shall (re-)initialize *numConsecutiveDTX* to zero for each PC5-RRC connection which has been established by upper layers, if any, upon establishment of the PC5-RRC connection or (re)configuration of *sl-maxNumConsecutiveDTX*. + +For each carrier associated with a PC5-RRC connection, the Sidelink HARQ Entity shall for each PSFCH reception occasion associated to the PSSCH transmission: + +- 1> if PSFCH reception is absent on the PSFCH reception occasion: + +- 2> increment *numConsecutiveDTX* by 1; + +NOTE 1: For SL operation with shared spectrum channel access, UE increases the *numConsecutiveDTX* by 1 when the UE fails to detect the HARQ feedback on all the associated PSFCH resources according to clause 16.3.0 of TS 38.213 [6]. + +- 2> if more than one carrier selected as defined in clause 5.22.1.11 is considered as the carriers for HARQ-based Sidelink RLF detection: + +- 3> if *numConsecutiveDTX* reaches *sl-maxNumConsecutiveDTX* for a carrier applied for HARQ-based Sidelink RLF detection: + +- 4> trigger the TX carrier (re-)selection procedure as specified in clause 5.22.1.11; + +- 4> indicate HARQ-based Sidelink carrier failure to RRC. + +- 3> if *numConsecutiveDTX* reaches *sl-maxNumConsecutiveDTX* for all carriers applied for HARQ-based Sidelink RLF detection: + +- 4> indicate HARQ-based Sidelink RLF detection to RRC. + +- 2> else: + +- 3> if *numConsecutiveDTX* reaches *sl-maxNumConsecutiveDTX*: + +- 4> indicate HARQ-based Sidelink RLF detection to RRC. + +- 1> else: + +- 2> re-initialize *numConsecutiveDTX* to zero. + +#### 5.22.1.3.4 Processing of sidelink grant on SL-PRS dedicated resource pool + +For each sidelink grant, the MAC entity shall: + +- 1> if the MAC entity determines that the sidelink grant is used for initial transmission as specified in clause 5.22.1.1; or + +- 1> if the sidelink grant is a configured sidelink grant and no MAC PDU has been obtained in an *sl-PeriodCG* of the configured sidelink grant: + +- 2> associate a Sidelink process to this sidelink grant; +- 2> set the Destination ID to the Destination layer-2 ID corresponding to the SL-PRS transmission; +- 2> if the length of the Source ID is configured to as 12 bit: + - 3> set the Source ID to the 12 LSB of the Source layer-2 ID corresponding to the SL-PRS transmission; +- 2> else if length of the Source ID is configured to as 24 bit: + - 3> set the Source ID to the Source layer-2 ID corresponding to the SL-PRS transmission; +- 2> set the cast type indicator to one of broadcast, groupcast and unicast as indicated by the upper layer; +- 2> set the SL-PRS priority as the value indicated by upper layer; +- 2> set the SL-PRS resource ID; +- 2> if the higher layer triggers SL-PRS transmission to the peer UE identified by the Destination layer-2 ID: + - 3> set the SL-PRS request to *request*; +- 2> deliver the SL-PRS transmission information to the Sidelink process; +- 2> instruct the associated Sidelink process to trigger a new transmission as defined in 5.22.1.3.5. +- 1> else (i.e., retransmission): + - 2> identify the Sidelink process associated with this grant; + - 2> if *sl-PRS-MaxNumTransmissions* is configured and the number of transmissions of the SL-PRS has not reached *sl-PRS-MaxNumTransmissions*: + - 3> deliver the same SL-PRS transmission information as the initial transmission to the Sidelink process; + - 3> instruct the associated Sidelink process to trigger a retransmission as defined in 5.22.1.3.5. + +NOTE: For configured sidelink grant, the Sidelink process for retransmission is identified by the SL-PRS Process ID as specified in clause 5.22.1.3.1. + +### 5.22.1.3.5 Sidelink process associated with SL-PRS dedicated resource pool + +If the Sidelink process is configured to perform transmissions of multiple SL-PRS with Sidelink resource allocation scheme 2, the process maintains a counter *SL\_RESOURCE\_RESELECTION\_COUNTER*. For other configurations of the Sidelink process, this counter is not available. For each SL-PRS new transmission or retransmission, the MAC entity shall: + +- 1> if there is no uplink transmission; or +- 1> if there is uplink transmission and the sidelink transmission is prioritized over uplink transmission: + - 2> instruct the physical layer to transmit SCI of the SL grant with the associated SL-PRS transmission information on SL-PRS dedicated resource pool; + - 2> instruct the physical layer to generate the SL-PRS on SL-PRS dedicated resource pool. +- 1> if this transmission corresponds to the last transmission of the SL-PRS transmission: + - 2> decrement *SL\_RESOURCE\_RESELECTION\_COUNTER* by 1, if available. + +The transmission of the SL-PRS is prioritized over uplink transmission(s) of the MAC entity or the other MAC entity if the following conditions are met: + +- 1> if the MAC entity is not able to perform this sidelink transmission simultaneously with all uplink transmission(s) at the time of the transmission, and + +- 1> if *ul-PrioritizationThres* is configured and if the value of the highest priority of logical channel(s) of all the NR uplink transmission(s) is not lower than *ul-PrioritizationThres*, and +- 1> if *sl-PrioritizationThres* is configured and if the value of SL-PRS priority is lower than *sl-PrioritizationThres*. + +#### 5.22.1.4 Multiplexing and assembly + +##### 5.22.1.4.0 General + +For PDU(s) associated with one SCI, MAC shall consider only logical channels with the same Source Layer-2 ID-Destination Layer-2 ID pair for one of unicast, groupcast and broadcast which is associated with the pair. Multiple transmissions for different Sidelink processes are allowed to be independently performed in different PSSCH durations. + +NOTE: Sidelink data for discovery and sidelink data for non-discovery transmitted by a UE cannot be multiplexed into the same TB because they are always associated with different destination L2 IDs (see TS 23.304 [26]). + +##### 5.22.1.4.1 Logical channel prioritization + +###### 5.22.1.4.1.1 General + +The sidelink Logical Channel Prioritization procedure is applied whenever a new transmission is performed. + +RRc controls the scheduling of sidelink data by signalling for each logical channel: + +- *sl-Priority* where an increasing priority value indicates a lower priority level; +- *sl-PrioritisedBitRate* which sets the sidelink Prioritized Bit Rate (sPBR); +- *sl-BucketSizeDuration* which sets the sidelink Bucket Size Duration (sBSD). + +RRc additionally controls the LCP procedure by configuring mapping restrictions for each logical channel: + +- *sl-configuredGrantType1Allowed* which sets whether a configured grant Type 1 can be used for sidelink transmission; +- *sl-AllowedCG-List* which sets the allowed configured grant(s) for sidelink transmission; +- *sl-HARQ-FeedbackEnabled* which sets whether the logical channel is allowed to be multiplexed with logical channel(s) with *sl-HARQ-FeedbackEnabled* set to *enabled* or *disabled*. + +The following UE variable is used for the Logical channel prioritization procedure: + +- *SBj* which is maintained for each logical channel *j*. + +The MAC entity shall initialize *SBj* of the logical channel to zero when the logical channel is established. + +For each logical channel *j*, the MAC entity shall: + +- 1> increment *SBj* by the product sPBR $\times$ T before every instance of the LCP procedure, where T is the time elapsed since *SBj* was last incremented; +- 1> if the value of *SBj* is greater than the sidelink bucket size (i.e. sPBR $\times$ sBSD): + - 2> set *SBj* to the sidelink bucket size. + +NOTE: The exact moment(s) when the UE updates *SBj* between LCP procedures is up to UE implementation, as long as *SBj* is up to date at the time when a grant is processed by LCP. + +###### 5.22.1.4.1.2 Selection of logical channels and SL-PRS + +The MAC entity shall for each SCI corresponding to a new transmission: + +- 1> if *sl-BWP-DiscPoolConfig*, *sl-BWP-DiscPoolConfigCommon*, *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X* is configured according to TS 38.331 [5]; and + - 1> if the new transmission is not associated to a sidelink grant on SL-PRS dedicated resource pool: + - 2> if the new transmission is associated to a sidelink grant in *sl-DiscTxPoolSelected* or *sl-DiscTxPoolScheduling* configured in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*: + - 3> select a Destination associated with NR sidelink discovery as specified in TS 23.304 [26], that is in the SL Active time for the SL transmission occasion if SL DRX is applied for the destination, and among the logical channels that satisfy all the following conditions for the SL grant associated to the SCI: + - 4> SL data for NR sidelink discovery is available for transmission; and + - 4> *SBj* > 0, in case there is any logical channel having *SBj* > 0; and + - 4> *sl-configuredGrantType1Allowed*, if configured, is set to *true* in case the SL grant is a Configured Grant Type 1; and + - 4> *sl-AllowedCG-List*, if configured, includes the configured grant index associated to the SL grant. + - 2> else if the new transmission is associated to a sidelink grant in *sl-TxPoolSelectedNormal* configured in *sl-BWP-PoolConfigA2X* or *sl-BWP-PoolConfigCommonA2X*: + - 3> select a Destination associated with BRID if *sl-A2X-Service* in *sl-TxPoolSelectedNormal* indicates *brid* or *bridAndDAA* or select a Destination associated with DAA if *sl-A2X-Service* in *sl-TxPoolSelectedNormal* indicates *daa* or *bridAndDAA* as specified in TS 23.256 [31], and the logical channel with the highest priority, among the logical channels that satisfy all the following conditions for the SL grant associated to the SCI: + - 4> SL data for A2X communication is available for transmission; and + - 4> *SBj* > 0, in case there is any logical channel having *SBj* > 0. + - 2> else: + - 3> select a Destination associated to one of unicast, groupcast and broadcast (excluding the Destination(s) associated with NR sidelink discovery as specified in TS 23.304 [26]), that is in the SL Active time for the SL transmission occasion if SL DRX is applied for the destination, and having at least one of the MAC CE and the logical channel and pending SL-PRS transmission(s) with the highest priority, among the logical channels that satisfy all the following conditions and MAC CE(s), if any, and SL-PRS(s), if any for the SL grant associated to the SCI: + - 4> SL data for NR sidelink communication is available for transmission; and + - 4> *SBj* > 0, in case there is any logical channel having *SBj* > 0; and + - 4> *sl-configuredGrantType1Allowed*, if configured, is set to *true* in case the SL grant is a Configured Grant Type 1; and + - 4> *sl-AllowedCG-List*, if configured, includes the configured grant index associated to the SL grant; and + - 4> *sl-HARQ-FeedbackEnabled* is set to *disabled*, if PSFCH is not configured for the SL grant associated to the SCI. + - 4> allowed on the carrier where the SCI is transmitted, if the carrier is configured by upper layers according to TS 38.331 [5] and TS 23.287 [19], if multiple carrier frequencies are configured and if the MAC entity has been configured with Sidelink resource allocation mode 2; and +- NOTE 0: A LCH is allowed in a carrier based on whether this selected carrier is within a subset of frequencies associated with all the PC5 QoS flows allowed to be mapped to this LCH based on RRC configuration. +- 4> having a priority whose associated *sl-threshCBR-FreqReselection* is no lower than the CBR of the carrier when the carrier is (re-)selected in accordance with clause 5.22.1.11, if multiple carrier frequencies are configured and if the MAC entity has been configured with Sidelink resource allocation mode 2. + +1> else: + +2> if COT sharing information has been received from lower layers as specified in TS 37.213[18]: + +3> if resources used for initial transmission for the SL grant associated to the SCI are within the COT duration and MAC entity decides to use shared COT with type-2 LBT: + +4> select a Destination associated to one of unicast, groupcast and broadcast that satisfy the following destination condition and CAPC condition, and having at least one of the MAC CE and the logical channel with the highest priority, among the logical channels that satisfy all the following conditions and MAC CE(s) satisfying CAPC and destination requirement, if any, for the SL grant associated to the SCI: + +5> if a Source Layer-1 ID and a Destination Layer-1 ID contained in the COT initiator's SCI match to the corresponding Destination Layer-1 ID and a Source Layer-1 IDs relating to the same unicast at the receiving UE and cast type indicator in the SCI is set to unicast; or if a Destination Layer-1 ID contained in the COT initiator's SCI match to a Destination Layer-1 ID known at the receiving UE and cast type indicator in the SCI is set to groupcast or broadcast; and + +5> if a CAPC value of the SL data has an equal or smaller CAPC value than a CAPC value indicated in the COT sharing information; and + +5> SL data is available for transmission; and + +5> $SB_j > 0$ , in case there is any logical channel having $SB_j > 0$ ; and + +5> *sl-configuredGrantType1Allowed*, if configured, is set to *true* in case the SL grant is a Configured Grant Type 1; and + +5> *sl-AllowedCG-List*, if configured, includes the configured grant index associated to the SL grant; and + +5> *sl-HARQ-FeedbackEnabled* is set to *disabled*, if PSFCH is not configured for the SL grant associated to the SCI. + +2> else if *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon* is not configured according to TS 38.331 [5]; and + +2> if the new transmission is not associated to a sidelink grant on SL-PRS dedicated resource pool: + +3> select a Destination associated to one of unicast, groupcast and broadcast, that is in the SL Active time for the SL transmission occasion if SL DRX is applied for the destination, and having at least one of the MAC CE and the logical channel and pending SL-PRS transmission(s) with the highest priority, among the logical channels that satisfy all the following conditions and MAC CE(s), if any, and SL-PRS(s), if any, for the SL grant associated to the SCI: + +4> SL data is available for transmission; and + +4> $SB_j > 0$ , in case there is any logical channel having $SB_j > 0$ ; and + +4> *sl-configuredGrantType1Allowed*, if configured, is set to *true* in case the SL grant is a Configured Grant Type 1; and + +4> *sl-AllowedCG-List*, if configured, includes the configured grant index associated to the SL grant; and + +4> *sl-HARQ-FeedbackEnabled* is set to *disabled*, if PSFCH is not configured for the SL grant associated to the SCI; and + +4> allowed on the carrier where the SCI is transmitted, if the carrier is configured by upper layers according to TS 38.331 [5] and TS 23.287 [19], if multiple carrier frequencies are configured and if the MAC entity has been configured with Sidelink resource allocation mode 2; and + +4> having a priority whose associated *sl-threshCBR-FreqReselection* is no lower than the CBR of the carrier when the carrier is (re-)selected in accordance with clause 5.22.1.11, if multiple carrier frequencies are configured and if the MAC entity has been configured with Sidelink resource allocation mode 2. + +NOTE 1: If multiple Destinations have the logical channels satisfying all conditions above with the same highest priority or if multiple Destinations have either the MAC CE and/or the logical channels satisfying all conditions above with the same priority as the MAC CE, which Destination is selected among them is up to UE implementation. + +- 1> else: (i.e., the sidelink grant is associated with SL-PRS dedicated resource pool) + - 2> select a Destination corresponding to the cast type of the SL grant and having pending SL-PRS transmission(s) with the highest priority for the SL grant associated to the SCI. +- 1> select the logical channels satisfying all the following conditions among the logical channels belonging to the selected Destination when the UL grant is not associated to a sidelink grant on SL-PRS dedicated resource pool: + - 2> SL data is available for transmission; and + - 2> *sl-configuredGrantType1Allowed*, if configured, is set to *true* in case the SL grant is a Configured Grant Type 1; and + - 2> *sl-AllowedCG-List*, if configured, includes the configured grant index associated to the SL grant; and + - 2> allowed on the carrier where the SCI is transmitted, if the carrier is configured by upper layers according to TS 38.331 [5] and TS 23.287 [19], if multiple carrier frequencies are configured and if the MAC entity has been configured with Sidelink resource allocation mode 2; and + - 2> having a priority whose associated *sl-threshCBR-FreqReselection* is no lower than the CBR of the carrier when the carrier is (re-)selected in accordance with clause 5.22.1.11, if multiple carrier frequencies are configured if the MAC entity has been configured with Sidelink resource allocation mode 2; and + - 2> CAPC value of the SL data has an equal or smaller CAPC value than a CAPC value indicated in the COT sharing information if MAC decides to use the shared COT; and + - 2> *sl-HARQ-FeedbackEnabled* is set to the value that satisfies the following conditions: + - 3> if PSFCH is configured for the sidelink grant associated to the SCI and the UE is capable of PSFCH reception: + - 4> *sl-HARQ-FeedbackEnabled* is set to *enabled*, if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the highest priority logical channel satisfying the above conditions; or + - 4> *sl-HARQ-FeedbackEnabled* is set to *disabled*, if *sl-HARQ-FeedbackEnabled* is set to *disabled* for the highest priority logical channel satisfying the above conditions. + - 3> else: + - 4> *sl-HARQ-FeedbackEnabled* is set to *disabled*. + +NOTE 2: HARQ feedback enabled/disabled indicator is set to disabled for the transmission of a MAC PDU only carrying CSI reporting MAC CE or Sidelink DRX Command MAC CE or Sidelink Inter-UE Coordination Request MAC CE or Sidelink Inter-UE Coordination Information MAC CE. + +#### 5.22.1.4.1.3 Allocation of sidelink resources + +The MAC entity shall for each sidelink grant associated with SL-PRS shared resource pool: + +- 1> if there is SL-PRS pending for transmission for the selected destination; and +- 2> if all the SL-SCH data within logical channel with lower priority value than that of the SL-PRS can be allocated with resources when SL-PRS is transmitted: + - 3> determine that the pending SL-PRS can be transmitted in the sidelink grant. +- 2> derive the Transport Block Size for a new transmission for SL-SCH according to clause 8.1.3.2 in TS 38.214 [7]. + +The MAC entity shall for each SCI corresponding to a new transmission for SL-SCH: + +- 1> allocate resources to the logical channels as follows: + - 2> logical channels selected in clause 5.22.1.4.1.2 for the SL grant with $SB_j > 0$ are allocated resources in a decreasing priority order. If the sPBR of a logical channel is set to *infinity*, the MAC entity shall allocate resources for all the data that is available for transmission on the logical channel before meeting the sPBR of the lower priority logical channel(s); + - 2> decrement $SB_j$ by the total size of MAC SDUs served to logical channel $j$ above; + - 2> if any resources remain, all the logical channels selected in clause 5.22.1.4.1.2 are served in a strict decreasing priority order (regardless of the value of $SB_j$ ) until either the data for that logical channel or the SL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally. + +NOTE 1: The value of $SB_j$ can be negative. + +The UE shall also follow the rules below during the SL scheduling procedures above: + +- the UE should not segment an RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the whole SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources of the associated MAC entity; +- if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill the grant of the associated MAC entity as much as possible; +- the UE should maximise the transmission of data; +- if the MAC entity is given a sidelink grant size that is equal to or larger than 12 bytes while having data available and allowed (according to clause 5.22.1.4.1) for transmission, the MAC entity shall not transmit only padding; +- A logical channel configured with *sl-HARQ-FeedbackEnabled* set to *enabled* and a logical channel configured with *sl-HARQ-FeedbackEnabled* set to *disabled* cannot be multiplexed into the same MAC PDU. + +The MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied: + +- there is no Sidelink CSI Reporting MAC CE generated for this PSSCH transmission as specified in clause 5.22.1.7; and +- there is no Sidelink DRX Command MAC CE generated for this PSSCH transmission as specified in clause 5.22.1.8; and +- there is no Sidelink Inter-UE Coordination Request MAC CE generated for this PSSCH transmission as specified in clause 5.22.1.9; and +- there is no Sidelink Inter-UE Coordination Information MAC CE generated for this PSSCH transmission as specified in clause 5.22.1.10; and +- the MAC PDU includes zero MAC SDUs and the MAC PDU is not associated with SL-PRS transmission on SL-PRS shared resource pool. + +Logical channels shall be prioritised in accordance with the following order (highest priority listed first): + +- data from SCCH; +- Sidelink CSI Reporting MAC CE; +- Sidelink Inter-UE Coordination Request MAC CE and Sidelink Inter-UE Coordination Information MAC CE; +- Sidelink DRX Command MAC CE; +- data from any STCH or SL-PRS. + +NOTE 2: The priority order between Sidelink Inter-UE Coordination Request MAC CE and Sidelink Inter-UE Coordination Information MAC CE is up to UE implementation. + +#### 5.22.1.4.2 Multiplexing of MAC Control Elements and MAC SDUs + +The MAC entity shall multiplex MAC CEs and MAC SDUs in a MAC PDU according to clauses 5.22.1.4.1 and 6.1.6. + +#### 5.22.1.5 Scheduling Request + +In addition to clause 5.4.4, the Scheduling Request (SR) is also used for requesting SL-SCH resources for new transmission when triggered by the Sidelink BSR (clause 5.22.1.6) or the SL-CSI reporting (clause 5.22.1.7) or SL-DRX Command indication or SL consistent LBT failure recovery (see clause 5.31.2) or SL-PRS Resource Request (clause 6.1.3.74). If configured, the MAC entity performs the SR procedure as specified in this clause unless otherwise specified in clause 5.4.4. For a sidelink logical channel or for SL-CSI reporting or for SL-DRX Command indication or for SL consistent LBT failure recovery or for SL-PRS Resource Request, at most one PUCCH resource for SR is configured per UL BWP. + +The SR configuration of the logical channel that triggered the Sidelink BSR (clause 5.22.1.6) is also considered as corresponding SR configuration for the triggered SR (clause 5.4.4). The value of the priority of the triggered SR corresponds to the value of priority of the logical channel that triggered the SR. + +Each sidelink logical channel and SL consistent LBT failure recovery may be mapped to zero or one SR configuration, which is configured by RRC. If the SL-CSI reporting procedure is enabled by RRC, the SL-CSI reporting is mapped to one SR configuration for all PC5-RRC connections. The SR configuration of the SL-CSI reporting triggered according to 5.22.1.7 is considered as corresponding SR configuration for the triggered SR (clause 5.4.4). The value of the priority of the triggered SR triggered by SL-CSI reporting corresponds to the value of the priority of the Sidelink CSI Reporting MAC CE. The SR configuration of the SL-CSI reporting is considered as corresponding SR configuration for the triggered SR of SL-DRX Command indication triggered according to 5.28.3. The value of the priority of the triggered SR triggered by SL-DRX Command indication corresponds to the value of the priority of the Sidelink DRX Command MAC CE. The SR configuration of the SL consistent LBT failure recovery triggered according to 5.31.2 is considered as corresponding SR configuration for the triggered SR (clause 5.4.4). The value of the priority of the triggered SR triggered by SL consistent LBT failure recovery corresponds to the value of the priority of the SL LBT failure MAC CE. Each SL-PRS priority may be mapped to zero or one SR configuration, which is configured by RRC. The value of the priority of the triggered SR triggered by SL-PRS resource request corresponds to the value of the priority of the SL-PRS triggering the SL-PRS Resource Request MAC CE. + +All pending SR(s) triggered according to the Sidelink BSR procedure (clause 5.22.1.6) prior to the MAC PDU assembly shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the MAC PDU is transmitted and this PDU includes an SL-BSR MAC CE which contains buffer status up to (and including) the last event that triggered a Sidelink BSR (see clause 5.22.1.4) prior to the MAC PDU assembly. + +All pending SR(s) triggered according to the Sidelink consistent LBT failure recovery (clause 5.31.2) shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the MAC PDU is transmitted and this PDU includes an SL LBT failure MAC CE that indicates Sidelink consistent LBT failure or when all the triggered Sidelink consistent LBT failure(s) for an SL BWP is cancelled. + +All pending SR(s) triggered according to the Sidelink BSR procedure (clause 5.22.1.6) shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the SL grant(s) can accommodate all pending data available for transmission in sidelink. + +If there is pending SR triggered by Sidelink consistent LBT failure recovery which has no corresponding SR configuration, MAC entity initiate a Random Access procedure (see clause 5.1) on the Serving Cell and cancel the pending SR. + +The pending SR triggered according to the SL-CSI reporting for a destination shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the SL grant(s) can accommodate the Sidelink CSI Reporting MAC CE when the SL-CSI reporting that has been triggered but not cancelled or when the triggered SL-CSI reporting is cancelled due to latency non-fulfilment as specified in 5.22.1.7. The pending SR triggered according to the SL-DRX Command indication for a destination shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the SL grant(s) can accommodate the Sidelink DRX Command MAC CE when the SL-DRX Command indication that has been triggered but not cancelled. All pending SR(s) triggered by either Sidelink BSR or Sidelink CSI report or Sidelink DRX Command indication shall be cancelled, when RRC configures Sidelink resource allocation mode 2. + +All pending SR(s) triggered according to the SL-PRS Resource Request procedure (clause 5.22.1.12) prior to the MAC PDU assembly shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the MAC PDU is transmitted and this PDU includes an SL-PRS Resource Request MAC CE which contains status of the pending SL- + +PRS transmission(s) up to (and including) the last event that triggered a SL-PRS Resource Request (see clause 5.22.1.12) prior to the MAC PDU assembly. + +All pending SR(s) triggered according to the SL-PRS Resource Request procedure (clause 5.22.1.12) shall be cancelled and each respective *sr-ProhibitTimer* shall be stopped when the SL grant(s) can accommodate the all the pending SL-PRS transmission(s). + +### 5.22.1.6 Buffer Status Reporting + +The Sidelink Buffer Status reporting (SL-BSR) procedure is used to provide the serving gNB with information about SL data volume in the MAC entity. + +RRC configures the following parameters to control the SL-BSR: + +- *sl-periodicBSR-Timer*, configured by *periodicBSR-Timer* in *sl-BSR-Config*; +- *sl-retxBsR-Timer*, configured by *retxBsR-Timer* in *sl-BSR-Config*; +- *sl-logicalChannelSR-DelayTimerApplied*; +- *sl-logicalChannelSR-DelayTimer*, configured by *logicalChannelSR-DelayTimer* in *sl-BSR-Config*; +- *sl-logicalChannelGroup*. + +Each logical channel which belongs to a Destination is allocated to an LCG as specified in TS 38.331 [5]. The maximum number of LCGs is eight. + +The MAC entity determines the amount of SL data available for a logical channel according to the data volume calculation procedure in TSs 38.322 [3] and 38.323 [4]. + +An SL-BSR shall be triggered if any of the following events occur: + +- 1> if the MAC entity has been configured with Sidelink resource allocation mode 1: + - 2> SL data, for a logical channel which belongs to an LCG of a Destination, becomes available to the MAC entity; and either + - 3> this SL data belongs to a logical channel with higher priority than the priorities of the logical channels containing available SL data which belong to any LCG belonging to the same Destination; or + - 3> none of the logical channels which belong to an LCG belonging to the same Destination contains any available SL data. + in which case the SL-BSR is referred below to as 'Regular SL-BSR'; + - 2> UL resources are allocated and number of padding bits remaining after a Padding BSR has been triggered is equal to or larger than the size of the SL-BSR MAC CE plus its subheader, in which case the SL-BSR is referred below to as 'Padding SL-BSR'; + - 2> *sl-retxBsR-Timer* expires, and at least one of the logical channels which belong to an LCG contains SL data, in which case the SL-BSR is referred below to as 'Regular SL-BSR'; + - 2> *sl-periodicBSR-Timer* expires, in which case the SL-BSR is referred below to as 'Periodic SL-BSR'. +- 1> else: + - 2> Sidelink resource allocation mode 1 is configured by RRC and SL data is available for transmission in the RLC entity or in the PDCP entity, in which case the Sidelink BSR is referred below to as 'Regular SL-BSR'. + +For Regular SL-BSR, the MAC entity shall: + +- 1> if the SL-BSR is triggered for a logical channel for which *sl-logicalChannelSR-DelayTimerApplied* with value *true* is configured by RRC: + - 2> start or restart the *sl-logicalChannelSR-DelayTimer*. + +- 1> else: + - 2> if running, stop the *sl-logicalChannelSR-DelayTimer*. + +For Regular and Periodic SL-BSR, the MAC entity shall: + +- 1> if *sl-PrioritizationThres* is configured and the value of the highest priority of the logical channels that belong to any LCG and contain SL data for any Destination is lower than *sl-PrioritizationThres*; and +- 1> if *ul-PrioritizationThres* is configured and the value of the highest priority of the logical channels that belong to any LCG and contain UL data is equal to or higher than *ul-PrioritizationThres* according to clause 5.4.5: + - 2> prioritize the LCG(s) for the Destination(s). +- 1> if the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled according to clause 5.4.5 and the UL grant cannot accommodate an SL-BSR MAC CE containing buffer status only for all prioritized LCGs having data available for transmission plus the subheader of the SL-BSR according to clause 5.4.3.1.3, in case the SL-BSR is considered as not prioritized: + - 2> prioritize the SL-BSR for logical channel prioritization specified in clause 5.4.3.1; + - 2> report Truncated SL-BSR containing buffer status for as many prioritized LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration. +- 1> else if the number of bits in the UL grant is expected to be equal to or larger than the size of an SL-BSR containing buffer status for all LCGs having data available for transmission plus the subheader of the SL-BSR according to clause 5.4.3.1.3: + - 2> report SL-BSR containing buffer status for all LCGs having data available for transmission. +- 1> else: + - 2> report Truncated SL-BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration. + +For Padding SL-BSR: + +- 1> if the number of padding bits remaining after a Padding BSR has been triggered is equal to or larger than the size of an SL-BSR containing buffer status for all LCGs having data available for transmission plus its subheader: + - 2> report SL-BSR containing buffer status for all LCGs having data available for transmission; +- 1> else: + - 2> report Truncated SL-BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration. + +For SL-BSR triggered by *sl-retxBSP-Timer* expiry, the MAC entity considers that the logical channel that triggered the SL-BSR is the highest priority logical channel that has data available for transmission at the time the SL-BSR is triggered. + +The MAC entity shall: + +- 1> if the sidelink Buffer Status reporting procedure determines that at least one SL-BSR has been triggered and not cancelled: + - 2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL-BSR MAC CE plus its subheader as a result of logical channel prioritization according to clause 5.4.3.1: + - 3> instruct the Multiplexing and Assembly procedure in clause 5.4.3 to generate the SL-BSR MAC CE(s); + - 3> start or restart *sl-periodicBSR-Timer* except when all the generated SL-BSRs are Truncated SL-BSRs; + - 3> start or restart *sl-retxBSP-Timer*. + - 2> if a Regular SL-BSR has been triggered and *sl-logicalChannelSR-DelayTimer* is not running: + +- 3> if there is no UL-SCH resource available for a new transmission; or +- 3> if UL-SCH resources are available for a new transmission and the UL-SCH resources cannot accommodate the SL-BSR MAC CE plus its subheader as a result of logical channel prioritization according to clause 5.4.3.1; or +- 3> if the set of Subcarrier Spacing index values in *sl-AllowedSCS-List*, if configured for the logical channel that triggered the SL-BSR, does not include the Subcarrier Spacing index associated to the UL-SCH resources available for a new transmission; or +- 3> if *sl-MaxPUSCH-Duration*, if configured for the logical channel that triggered the SL-BSR, is smaller than the PUSCH transmission duration associated to the UL-SCH resources available for a new transmission; +- 4> trigger a Scheduling Request. + +NOTE 1: UL-SCH resources are considered available if the MAC entity has been configured with, receives, or determines an uplink grant. If the MAC entity has determined at a given point in time that UL-SCH resources are available, this need not imply that UL-SCH resources are available for use at that point in time. + +A MAC PDU shall contain at most one SL-BSR MAC CE, even when multiple events have triggered an SL-BSR. The Regular SL-BSR and the Periodic SL-BSR shall have precedence over the padding SL-BSR. + +The MAC entity shall restart *sl-retxBSR-Timer* upon reception of an SL grant for transmission of new data on any SL-SCH. + +All triggered SL-BSRs may be cancelled when the SL grant(s) can accommodate all pending data available for transmission. All BSRs triggered prior to MAC PDU assembly shall be cancelled when a MAC PDU is transmitted and this PDU includes an SL-BSR MAC CE which contains buffer status up to (and including) the last event that triggered an SL-BSR prior to the MAC PDU assembly. All triggered SL-BSRs shall be cancelled, and *sl-retx-BSR-Timer* and *sl-periodic-BSR-Timer* shall be stopped, when RRC configures Sidelink resource allocation mode 2. + +NOTE 2: MAC PDU assembly can happen at any point in time between uplink grant reception and actual transmission of the corresponding MAC PDU. SL-BSR and SR can be triggered after the assembly of a MAC PDU which contains an SL-BSR MAC CE, but before the transmission of this MAC PDU. In addition, SL-BSR and SR can be triggered during MAC PDU assembly. + +### 5.22.1.7 CSI Reporting + +The Sidelink Channel State Information (SL-CSI) reporting procedure is used to provide a peer UE with sidelink channel state information as specified in clause 8.5 of TS 38.214 [7]. + +RRC configures the following parameters to control the SL-CSI reporting procedure: + +- *sl-LatencyBoundCSI-Report*, which is maintained for each PC5-RRC connection. + +The MAC entity maintains an *sl-CSI-ReportTimer* for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to a PC5-RRC connection. *sl-CSI-ReportTimer* is used for an SL-CSI reporting UE to follow the latency requirement signalled from a CSI triggering UE. The value of *sl-CSI-ReportTimer* is the same as the latency requirement of the SL-CSI reporting in *sl-LatencyBoundCSI-Report* configured by RRC. + +The MAC entity shall for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to a PC5-RRC connection which has been established by upper layers: + +- 1> if the SL-CSI reporting has been triggered by an SCI and not cancelled: + - 2> if the *sl-CSI-ReportTimer* for the triggered SL-CSI reporting is not running: + - 3> start the *sl-CSI-ReportTimer*. + - 2> if the *sl-CSI-ReportTimer* for the triggered SL-CSI reporting expires: + - 3> cancel the triggered SL-CSI reporting. + +- 2> else if the MAC entity has SL resources allocated for new transmission and the SL-SCH resources can accommodate the SL-CSI reporting MAC CE and its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate a Sidelink CSI Reporting MAC CE as defined in clause 6.1.3.35; + - 3> stop the *sl-CSI-ReportTimer* for the triggered SL-CSI reporting; + - 3> cancel the triggered SL-CSI reporting. +- 2> else if the MAC entity has been configured with Sidelink resource allocation mode 1: + - 3> trigger a Scheduling Request. + +NOTE 1: The MAC entity configured with Sidelink resource allocation mode 1 may trigger a Scheduling Request if transmission of a pending SL-CSI reporting with the sidelink grant(s) cannot fulfil the latency requirement associated to the SL-CSI reporting. + +NOTE 2: Regardless of a carrier that receives an indicator triggering SL-CSI reporting in the SL Carrier Aggregation, it is up to UE implementation to decide which carrier the UE sends SL-CSI reporting MAC CE. + +#### 5.22.1.8 Void + +#### 5.22.1.9 IUC-Request transmission + +The Sidelink Inter-UE Coordination Request transmission procedure is used to trigger a peer UE to transmit Sidelink Inter-UE Coordination Information as specified in clause 8.4.1.3 of TS 38.212 [9]. + +#### 5.22.1.10 IUC-Information Reporting + +##### 5.22.1.10.1 General + +The Sidelink Inter-UE Coordination Information reporting procedure is used to provide a peer UE with inter-UE coordination information as specified in clause 8.1.4 of TS 38.214 [7]. The Sidelink Inter-UE Coordination reporting procedure can be triggered by Sidelink Inter-UE Coordination Request MAC CE or condition (See TS 38.331 [5] and TS 38.214 [7]). Unicast for preferred resource set and non-preferred resource set and Groupcast/Broadcast for non-preferred resource set are supported for inter-UE coordination information transmission triggered by a condition other than explicit request reception. + +RRC configures the following parameter to control the SL-IUC Information reporting procedure: + +- *sl-LatencyBoundIUC-Report*, which is maintained for each PC5-RRC connection. + +The MAC entity maintains an *sl-IUC-ReportTimer* for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to a PC5-RRC connection. *sl-IUC-ReportTimer* is used for an SL-IUC Information reporting UE to follow the latency requirement signalled from an IUC-Information triggering UE. The value of *sl-IUC-ReportTimer* is the same as the latency requirement of the SL-IUC Information in *sl-LatencyBoundIUC-Report* configured by RRC. + +The MAC entity shall for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to a PC5-RRC connection which has been established by upper layers: + +- 1> if the SL-IUC Information reporting has been triggered by an SL-IUC Request MAC CE (and/or an SCI) and not cancelled: + - 2> if the *sl-IUC-ReportTimer* for the triggered SL-IUC Information reporting is not running: + - 3> start the *sl-IUC-ReportTimer*. + - 2> if the *sl-IUC-ReportTimer* for the triggered SL-IUC Information reporting expires: + - 3> cancel the triggered SL-IUC Information reporting. + +- 2> else if the MAC entity has SL resources allocated for new transmission and the SL-SCH resources can accommodate the SL-IUC Information MAC CE and its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate a Sidelink Inter-UE Coordination Information MAC CE as defined in clause 6.1.3.53; + - 3> stop the *sl-IUC-ReportTimer* for the triggered SL-IUC Information reporting; + - 3> cancel the triggered SL-IUC Information reporting. + +#### 5.22.1.10.2 Reception of IUC-Information Reporting + +Upon the reception of SL-IUC Information MAC CE from another UE, the MAC entity shall: + +- 1> if *sl-InterUE-CoordinationScheme1* enabling reception/transmission of preferred resource set and non-preferred resource set is configured by RRC: + - 2> if the SL-IUC Information MAC CE contains a non-preferred resource set and if the UE is configured to use full sensing or partial sensing in the resource pool where the non-preferred resource set is located: + - 3> indicate the received non-preferred resource set to physical layer. + +#### 5.22.1.11 TX carrier (re-)selection + +The MAC entity shall consider a CBR of a carrier to be one measured by lower layers according to TS 38.214 [7] if CBR measurement results are available, or the corresponding *sl-defaultTxConfigIndex* configured by upper layers if CBR measurement results are not available. + +If the TX carrier (re-)selection is triggered for a Sidelink process according to clause 5.22.1.1, the MAC entity shall: + +- 1> if there is no selected sidelink grant on any carrier allowed for the sidelink logical channel where data is available as indicated by upper layers (TS 38.331 [5] and TS 23.287 [19]): + - 2> for each carrier configured by upper layers associated with the concerned sidelink logical channel: + - 3> if the CBR of the carrier is below *sl-threshCBR-FreqReselection* associated with the priority of the sidelink logical channel: + + +NOTE 1: In the case of multiple resource pools configured on a carrier, which specific resource pool is used to determine the CBR of this carrier is up to UE implementation. + + - 4> consider the carrier as a candidate carrier for TX carrier (re-)selection for the concerned sidelink logical channel when the carrier satisfies all the following conditions; + - 5> if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the sidelink logical channel: + - 6> the carrier includes at least one pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured. + - 5> else: + - 6> the carrier includes any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured. +- 1> else: + - 2> if the CBR of the carrier is below *sl-threshCBR-FreqKeeping* associated with priority of the sidelink logical channel, for each sidelink logical channel, if any, where data is available and that are allowed on the carrier for which Tx carrier (re-)selection is triggered according to clause 5.22.1.1: + - 3> select the carrier and the associated pool of resources. + - 2> else: + +- 3> if the CBR of the carrier is below *sl-threshCBR-FreqReselection* associated with the priority of the sidelink logical channel: + - 4> consider the carrier as a candidate carrier for TX carrier (re-)selection, for each carrier configured by upper layers on which the sidelink logical channel is allowed when the carrier satisfies all the following conditions; + - 5> if *sl-HARQ-FeedbackEnabled* is set to *enabled* for the sidelink logical channel: + - 6> the carrier includes at least one pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured. + - 5> else: + - 6> the carrier includes any pool of resources among the pools of resources except the pool(s) in *sl-BWP-DiscPoolConfig* or *sl-BWP-DiscPoolConfigCommon*, if configured. + +The MAC entity shall: + +- 1> if one or more carriers are considered as the candidate carriers for TX carrier (re-)selection: + - 2> if Tx carrier (re-)selection is triggered, for each sidelink logical channel allowed on the carrier where data is available: + - 3> select one or more carrier(s) and associated pool(s) of resources among the candidate carriers with increasing order of CBR from the lowest CBR. + +NOTE 2: It is left to UE implementation how many carriers to select based on UE capability. + +NOTE 3: It is left to UE implementation to determine the sidelink logical channels among the sidelink logical channels where data is available and that are allowed on the carrier for which Tx carrier (re-) selection is triggered. + +## 5.22.1.12 SL-PRS Resource Request + +SL-PRS transmission can be triggered either by lower layer signalling from the peer UE or the UE's own higher layer. The SL-PRS Resource Request procedure is used to provide gNB with information about the triggered SL-PRS transmission. + +The MAC entity shall, if Sidelink resource allocation scheme 1 for SL-PRS transmission is configured: + +- 1> if aperiodic SL-PRS is triggered: + - 2> trigger the SL-PRS Resource Request. +- 1> else if periodic SL-PRS is triggered: + - 2> notify RRC to send SL-PRS Resource Request. + +The MAC entity shall: + +- 1> if SL-PRS Resource Request is triggered and not cancelled: + - 2> if UL-SCH resources are available for a new transmission and these UL-SCH resources can accommodate the SL-PRS Resource Request MAC CE plus its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly entity to generate the SL-PRS Resource Request MAC CE. + - 2> else: + - 3> trigger a Scheduling Request for the SL-PRS Resource Request MAC CE as specified in clause 5.4.4. + +The SL-PRS Resource Request MAC CE may be cancelled when SL grant can accommodate all the pending SL-PRS transmissions. The SL-PRS Resource Request MAC CE shall be cancelled when a MAC PDU is transmitted and this + +PDU includes a SL-PRS Resource Request MAC CE that indicates request for all the pending SL-PRS transmission(s) since the last event the MAC CE is triggered. + +## 5.22.2 SL-SCH Data and SL-PRS reception + +### 5.22.2.1 SCI reception + +SCI indicates if there is a transmission on SL-SCH and provide the relevant HARQ information. SCI can also indicate if there is a SL-PRS transmission. An SCI for SL-SCH transmission with or without corresponding SL-PRS on SL-PRS shared resource pool consists of two parts: the 1st stage SCI on PSCCH and the 2nd stage SCI on PSSCH as specified in clause 8.1 of TS 38.214 [7]. An SCI for SL-PRS transmission on SL-PRS dedicated resource pool consists of a single part on PSCCH as specified in TS 38.212 [9]. + +The MAC entity shall: + +- 1> for each PSCCH duration during which the MAC entity monitors PSCCH: + - 2> if a 1st stage SCI has been received on the PSCCH: + - 3> determine the set of PSSCH durations in which reception of a 2nd stage SCI and the transport block occur using the received part of the SCI; + - 3> if the 2nd stage SCI for this PSSCH duration has been received on the PSSCH: + - 4> store the SCI as a valid SCI for the PSSCH durations corresponding to transmission(s) of the transport block and SL-PRS, if available and the associated HARQ information and QoS information; + - 2> else if an SCI has been received on the PSCCH reception on SL-PRS dedicated resource pool for SL-PRS transmission: + - 3> determine the SL-PRS transmission occasion corresponding to the SCI; + - 3> store the SCI as a valid SCI for the SL-PRS transmission and the corresponding SL-PRS transmission information on SL-PRS dedicated resource pool.1> for each PSSCH duration for which the MAC entity has a valid SCI: + - 2> deliver the SCI and the associated Sidelink transmission information to the Sidelink HARQ Entity. +- 1> for each SL-PRS transmission occasion for which MAC entity has a valid SCI: + - 2> perform SL-PRS reception according to the SL-PRS transmission information within the SCI as in clause 5.22.2.2.2 for SL-PRS received on SL-PRS shared resource pool and as in clause 5.22.2.4 for SL-PRS received on SL-PRS dedicated resource pool. + +### 5.22.2.2 Sidelink HARQ operation and SL-PRS reception on SL-PRS shared resource pool + +#### 5.22.2.2.1 Sidelink HARQ Entity + +There is at most one Sidelink HARQ Entity at the MAC entity for reception of the SL-SCH, which maintains a number of parallel Sidelink processes. + +Each Sidelink process is associated with SCI in which the MAC entity is interested. This interest is determined by the Sidelink identification information of the SCI. The Sidelink HARQ Entity directs Sidelink transmission information and associated TBs received on the SL-SCH to the corresponding Sidelink processes. + +The number of Receiving Sidelink processes associated with the Sidelink HARQ Entity is defined in TS 38.306 [5]. + +For each PSSCH duration, the Sidelink HARQ Entity shall: + +- 1> for each SCI valid for this PSSCH duration: + +- 2> if the NDI has been toggled compared to the value of the previous received transmission corresponding to the Sidelink identification information and the Sidelink process ID of the SCI or this is the very first received transmission for the pair of the Sidelink identification information and the Sidelink process ID of the SCI: + - 3> if there is a Sidelink process associated with the Sidelink identification information and the Sidelink process ID of the SCI: + - 4> consider the Sidelink process as unoccupied; + - 4> flush the soft buffer for the Sidelink process. + - 3> allocate the TB received from the physical layer and the associated Sidelink identification information and Sidelink process ID to an unoccupied Sidelink process; + - 3> associate the Sidelink process with the Sidelink identification information and the Sidelink process ID of this SCI and consider this transmission to be a new transmission. + +NOTE 1: When a new TB arrives, the Sidelink HARQ Entity allocates the TB to any unoccupied Sidelink process. If there is no unoccupied Sidelink process in the Sidelink HARQ entity, how to manage receiving Sidelink processes is up to UE implementation. + +NOTE 1a: If the NDI has not been toggled compared to the value of the previous received transmission corresponding to the Sidelink identification information and the Sidelink process ID of the SCI, and if there is no Sidelink process associated with the Sidelink identification information and the Sidelink process ID of the SCI, it is up to UE implementation to handle the corresponding TB. + +1> for each Sidelink process: + +- 2> if the NDI has not been toggled compared to the value of the previous received transmission corresponding to the Sidelink identification information and the Sidelink process ID of the SCI for the Sidelink process according to its associated SCI: + - 3> allocate the TB received from the physical layer to the Sidelink process and consider this transmission to be a retransmission. + +NOTE 2: A single sidelink process can only be (re-)associated to a single combination of Sidelink identification information and Sidelink process ID at a time and a single combination of Sidelink identification information and Sidelink process ID can only be (re-)associated to a single sidelink process at a time. + +#### 5.22.2.2.2 Sidelink process + +For each PSSCH duration where a transmission takes place for the Sidelink process, one TB and the associated HARQ information is received from the Sidelink HARQ Entity. + +For each received TB and SL-PRS, if available and associated Sidelink transmission information, the Sidelink process shall: + +1> if this is a new transmission: + +- 2> attempt to decode the received data. + +1> else if this is a retransmission: + +- 2> if the data for this TB has not yet been successfully decoded: + - 3> instruct the physical layer to combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data. + +1> if the sidelink transmission information in the SCI indicates SL-PRS transmission: + +- 2> if the SL-PRS transmission is associated to unicast: + - 3> if the DST field of the decoded MAC PDU subheader is equal to the 8 MSB of any of the Source Layer-2 ID(s) of the UE for which the 16 LSB are equal to the Destination ID in the corresponding SCI; and + +- 3> if the SRC field of the decoded MAC PDU subheader is equal to the 16 MSB of any of the Destination Layer-2 ID(s) of the UE for which the 8 LSB are equal to the Source ID in the corresponding SCI: + - 4> instruct the physical layer to perform SL-PRS reception. +- 2> else if the SL-PRS tnramission is associated with groupcast or broadcast: + - 3> if the DST field of the decoded MAC PDU subheader is equal to the 8 MSB of any of the Destination Layer-2 ID(s) of the UE for which the 16 LSB are equal to the Destination ID in the corresponding SCI: + - 4> instruct the physical layer to perform SL-PRS reception. +- 1> if the data which the MAC entity attempted to decode was successfully decoded for this TB; or +- 1> if the data for this TB was successfully decoded before: + - 2> if this is the first successful decoding of the data for this TB: + - 3> if this TB is associated to unicast and the DST field of the decoded MAC PDU subheader is equal to the 8 MSB of any of the Source Layer-2 ID(s) of the UE for which the 16 LSB are equal to the Destination ID in the corresponding SCI: + - 4> if the SRC field of the decoded MAC PDU subheader is equal to the 16 MSB of any of the Destination Layer-2 ID(s) of the UE for which the 8 LSB are equal to the Source ID in the corresponding SCI; or + - 4> if this TB is corresponding to the logical channel with LCID equal to 0 or 1 and determined to be the first TB: + - 5> deliver the decoded MAC PDU to the disassembly and demultiplexing entity. + - 3> if this TB is associated to groupcast or broadcast: + - 4> if the DST field of the decoded MAC PDU subheader is equal to the 8 MSB of any of the Destination Layer-2 ID(s) of the UE for which the 16 LSB are equal to the Destination ID in the corresponding SCI; or + - 4> if this TB is corresponding to the logical channel with LCID equal to 58, and the DST field of the decoded MAC PDU subheader is equal to the 8 MSB of any of the Source Layer-2 ID(s) of the UE for which the 16 LSB are equal to the Destination ID in the corresponding SCI: + - 5> deliver the decoded MAC PDU to the disassembly and demultiplexing entity. + +NOTE: Whether the TB is the first TB can be determined based on the Source Layer-2 ID and Destination Layer-2 ID pair. + +- 2> consider the Sidelink process as unoccupied. +- 1> else: + - 2> instruct the physical layer to replace the data in the soft buffer for this TB with the data which the MAC entity attempted to decode. +- 1> if HARQ feedback is enabled by the SCI: + - 2> if negative-only acknowledgement is indicated by the SCI according to clause 8.4.1 of TS 38.212 [9]: + - 3> if UE's location information is available and distance between UE's location and the central location of the nearest zone that is calculated based on the *Zone\_id* in the SCI and the value of *sl-ZoneLength* corresponding to the communication range requirement in the SCI as specified in TS 38.331 [5] is smaller or equal to the communication range requirement in the SCI; or + - 3> if none of *Zone\_id* and communication range requirement is indicated by the SCI; or + - 3> if UE's location information is not available: + +- 4> if the data which the MAC entity attempted to decode was not successfully decoded for this TB and the data for this TB was not successfully decoded before: + - 5> instruct the physical layer to generate a negative acknowledgement of the data in this TB. + - 2> if negative-positive acknowledgement or unicast is indicated by the SCI according to clause 8.4.1 of TS 38.212 [9]: + - 3> if the data which the MAC entity attempted to decode was successfully decoded for this TB or the data for this TB was successfully decoded before: + - 4> instruct the physical layer to generate a positive acknowledgement of the data in this TB. + - 3> else: + - 4> instruct the physical layer to generate a negative acknowledgement of the data in this TB. + +### 5.22.2.3 Disassembly and demultiplexing + +The MAC entity shall disassemble and demultiplex a MAC PDU as defined in clause 6.1.6. + +### 5.22.2.4 SL-PRS reception on SL-PRS dedicated resource pool + +For each SL-PRS transmission occasion on SL-PRS dedicated resource pool, the MAC entity shall: + +- 1> if this SL-PRS transmission is associated to unicast: + - 2> if the destination ID in the corresponding SCI is equal to the UE's source ID; and if *[12bitSourceID]* is configured: + - 3> if source ID in the corresponding SCI is equal to the 12 LSB of the UE's destination layer-2 ID: + - 4> instruct the physical layer to perform SL-PRS reception on the SL-PRS transmission occasion. + - 2> else if the destination ID in the corresponding SCI is equal to the UE's source ID, and if *[24bitSourceID]* is configured: + - 3> if source ID in the corresponding SCI is equal to the UE's destination layer-2 ID: + - 4> instruct the physical layer to perform SL-PRS reception on the SL-PRS transmission occasion. +- 1> else if this SL-PRS transmission is associated to broadcast or groupcast: + - 2> if the destination ID in the corresponding SCI is equal to the UE's destination layer-2 ID + - 3> instruct the physical layer to perform SL-PRS reception on the SL-PRS transmission occasion. + +## 5.23 SL-BCH data transfer + +### 5.23.1 SL-BCH data transmission + +When instructed to send SL-BCH, the MAC entity shall: + +- 1> obtain the MAC PDU to transmit from SBCCH; +- 1> deliver the MAC PDU to the physical layer and instruct it to generate a transmission. + +### 5.23.2 SL-BCH data reception + +When the MAC entity needs to receive SL-BCH, the MAC entity shall: + +- 1> receive and attempt to decode the SL-BCH; + +- 1> if a TB on the SL-BCH has been successfully decoded: + - 2> deliver the decoded MAC PDU to upper layers. + +## 5.24 Handling of PRS Processing Window + +When PPW is activated and PRS has higher priority than DL channel and signals, for the affected symbols within the PPW according to clause 5.1.6.5 in TS 38.214 [7], the MAC entity shall: + +- 1> if the *ra-ResponseWindow* or the *ra-ContentionResolutionTimer* or the *msgB-ResponseWindow* is running: + - 2> monitor the PDCCH as specified in clauses 5.1.4 and 5.1.5. +- 1> else: + - 2> not receive DL-SCH; + - 2> not receive PDCCH. + +## 5.25 Positioning Measurement Gap Activation/Deactivation Request + +If the UE is configured with pre-configured positioning measurement gap and the request of the activation/deactivation of the positioning measurement gap by UL MAC CE, the UE may request the network to activate or deactivate the Positioning measurement gap with UL MAC CE for Positioning Measurement Gap Activation/Deactivation Request in clause 6.1.3.40. + +The MAC entity shall, when triggered by the upper layer to send Positioning Measurement Gap Activation/Deactivation Request, cancel the triggered Positioning Measurement Gap Activation/Deactivation Request, if any and trigger another Positioning Measurement Gap Activation/Deactivation Request according to the upper layer's request. + +The MAC entity shall, + +- 1>if Positioning Measurement Gap Activation/Deactivation Request MAC CE has been triggered, and not cancelled: + - 2> if indication from upper layer has been received that the triggered Positioning Measurement Gap Activation/Deactivation Request MAC CE should be cancelled; or + - 2> if the pre-configured measurement gap indicated in the Positioning Measurement Gap Activation/Deactivation Request MAC CE has already been activated/deactivated according to clause 5.18.20: + - 3> cancel the triggered Positioning Measurement Gap Activation/Deactivation Request MAC CE. + - 2> if UL-SCH resources are available for a new transmission and these UL-SCH resources can accommodate the Positioning Measurement Gap Activation/Deactivation Request MAC CE plus its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate the Positioning Measurement Gap Activation/Deactivation Request MAC CE according to the upper layer's request; + - 3> cancel triggered Positioning Measurement Gap Activation/Deactivation Request MAC CE. + - 2> else: + - 3> trigger a Scheduling Request for Positioning Measurement Gap Activation/Deactivation Request MAC CE as specified in clause 5.4.4. + +## 5.26 Positioning SRS transmission in RRC\_INACTIVE + +### 5.26.1 General + +Periodic and semi-persistent Positioning SRS with or without positioning SRS bandwidth aggregation can be configured for Positioning SRS transmission in RRC\_INACTIVE. + +SRS for positioning Tx frequency hopping as in clause 5.32 can also be configured for Positioning SRS transmission in RRC\_INACTIVE. + +The MAC entity shall, + +- 1> if the TA of the configured Positioning SRS is valid according to clause 5.26.2, and the conditions for positioning SRS transmission in clause 7.3.1 of TS 38.213 [6] and clause 6.2.1.4 of TS 38.214 [7] are satisfied: + - 2> if the UE is configured with UTW and the *UplinkTimeWindowTimer* is running according to clause 5.32; or + - 2> if the UE is not configured with UTW: + - 3> instruct to the lower layer according to TS 38.214 [7] to transmit Positioning Periodic SRS or Semi-Persistent SRS that is activated according to clause 5.18.17. + +### 5.26.2 TA validation for SRS transmission in RRC\_INACTIVE + +RRC configures the following parameters for validation for SRS transmission in RRC\_INACTIVE: + +- *inactivePosSRS-RSRP-ChangeThreshold*: RSRP threshold for the increase/decrease of RSRP for time alignment validation. + +The MAC entity shall: + +- 1> if the UE receives configuration for SRS transmission in RRC\_INACTIVE: + - 2> store the RSRP of the downlink pathloss reference with the current RSRP value of the downlink pathloss reference as in TS 38.331 [5]. +- 1> else if the UE is configured with SRS transmission in RRC\_INACTIVE: + - 2> if Timing Advance Command MAC CE is received as in clause 5.2, or; + - 2> if Timing Advance Command or Absolute Timing Advance Command is received for Random Access procedure that is successfully completed: + - 3> update the stored the RSRP of the downlink pathloss reference with the current RSRP value of the downlink pathloss reference. + - 2> if the UE is configured with SRS with validity area and the upper layer indicates the MAC to update the stored RSRP: + - 3> update the RSRP of the downlink pathloss reference with the current RSRP value of the downlink pathloss reference of the camped cell as specified in TS 38.331 [5]. + +The MAC entity shall consider the TA to be valid when the following conditions are fulfilled: + +- 1> compared to the stored downlink pathloss reference RSRP value, the current RSRP value of the downlink pathloss reference has not increased/decreased by more than *inactivePosSRS-RSRP-ChangeThreshold*, if configured; and +- 1> *inactivePosSRS-TimeAlignmentTimer* is running or *srs-ValidityArea-TimerAlignmentTimer* is running when positioning validity area is configured. + +## 5.27 Small Data Transmission + +### 5.27.1 General + +The MAC entity may be configured by RRC with SDT and the SDT procedure may be initiated by RRC layer for MO-SDT or MT-SDT. The SDT procedure initiated for MO-SDT can be performed either by Random Access procedure with 2-step RA type or 4-step RA type (i.e., RA-SDT) or by configured grant Type 1 (i.e., CG-SDT). The SDT procedure initiated for MT-SDT can be performed either by Random Access procedure with 2-step RA type or 4-step RA type (i.e., RA-SDT is not applicable as specified in clause 5.1.1b) or by configured grant Type 1 (i.e., CG-SDT). + +RRC configures the following parameters for SDT procedure: + +- *sdt-DataVolumeThreshold*: data volume threshold for the UE to determine whether to perform SDT procedure initiated for MO-SDT; +- *sdt-RSRP-Threshold*: RSRP threshold for UE to determine whether to perform SDT procedure initiated for MO-SDT; +- *sdt-RSRP-ThresholdMT*: RSRP threshold for UE to determine whether to perform SDT procedure initiated for MT-SDT; +- *cg-SDT-RSRP-ThresholdSSB*: an RSRP threshold configured for SSB selection for CG-SDT; +- *cg-MT-SDT-MaxDurationToNextCG-Occasion*: time threshold which is used by the UE to determine whether to perform CG-SDT for MT-SDT; +- *cg-SDT-MaxDurationToNextCG-Occasion*: time threshold configured per logical channel which is used by the UE to determine whether to perform CG-SDT for MO-SDT. + +The following UE variable is used for the SDT procedure: + +- *MAX\_DURATION\_TO\_NEXT\_CG\_OCCASION*; +- *RSRP\_THRESHOLD*. + +The MAC entity shall, if initiated by the upper layers for SDT procedure: + +- 1> if SDT procedure is initiated for MO-SDT as specified in TS 38.331 [5]: + - 2> set the *MAX\_DURATION\_TO\_NEXT\_CG\_OCCASION* to the shortest value of *cg-SDT-MaxDurationToNextCG-Occasion*, if configured, among all the logical channel configured with this parameter by upper layer and having data for transmission; + - 2> set the *RSRP\_THRESHOLD* to the value of *sdt-RSRP-Threshold*, if configured. +- 1> else if SDT procedure is initiated for MT-SDT as specified in TS 38.331 [5]: + - 2> set the *MAX\_DURATION\_TO\_NEXT\_CG\_OCCASION* to the value of *cg-MT-SDT-MaxDurationToNextCG-Occasion*, if configured; + - 2> if *sdt-RSRP-ThresholdMT* is configured: + - 3> set the *RSRP\_THRESHOLD* to the value of *sdt-RSRP-ThresholdMT*. + - 2> else if *sdt-RSRP-Threshold* is configured: + - 3> set the *RSRP\_THRESHOLD* to the value of *sdt-RSRP-Threshold*. +- 1> if the SDT procedure is initiated for MO-SDT as specified in TS 38.331 [5], and the data volume of the pending UL data across all RBs configured for SDT is less than or equal to *sdt-DataVolumeThreshold*, or if the SDT procedure is initiated for MT-SDT as specified in TS 38.331 [5]; and + +NOTE 1: For SDT procedure, the MAC entity also considers the suspended RBs configured with SDT for data volume calculation. It is up to the UE's implementation how the UE calculates the data volume for the suspended RBs. Size of the CCCH message is not considered for data volume calculation + +- 1> if the RSRP of the downlink pathloss reference is higher than *RSRP\_THRESHOLD* or if *RSRP\_THRESHOLD* is not set: + - 2> if the Serving Cell is configured with supplementary uplink as specified in TS 38.331 [5]; and + - 2> if the RSRP of the downlink pathloss reference is less than *rsrp-ThresholdSSB-SUL*: + - 3> select the SUL carrier. + - 2> else: + - 3> select the NUL carrier. + - 2> if CG-SDT is configured on the selected UL carrier, and TA for CG-SDT is valid according to clause 5.27.2 in the first available CG occasion for initial CG-SDT transmission with CCCH message according to clause 5.8.2; and + - 2> if the SDT procedure is initiated for MO-SDT as specified in TS 38.331 [5], and, for each RB having data available for transmission, *configuredGrantType1Allowed*, if configured for CG-SDT, is configured with value *true* for the corresponding logical channel, or if the SDT procedure is initiated for MT-SDT as specified in TS 38.331 [5]; and + - 2> if at least one SSB configured for CG-SDT with SS-RSRP above *cg-SDT-RSRP-ThresholdSSB* is available, and if either the time gap between the initiation of the SDT procedure and first available CG occasion for initial CG-SDT transmission with CCCH message according to clause 5.8.2 is less than *MAX\_DURATION\_TO\_NEXT\_CG\_OCCASION*, or if the *MAX\_DURATION\_TO\_NEXT\_CG\_OCCASION* is not set: + - 3> indicate to the upper layers that the conditions for initiating SDT procedure are fulfilled; + - 3> perform CG-SDT procedure on the selected UL carrier according to clause 5.8.2. + - 2> else if a set of Random Access resources for RA-SDT is configured and can be selected according to clause 5.1.1b on the selected UL carrier on the BWP configured by *initialUplinkBWP-RedCap*, if configured for a RedCap UE; otherwise, on the BWP configured by *initialUplinkBWP*; or + - 2> if the SDT procedure is initiated for MT-SDT as specified in TS 38.331 [5]: + - 3> if *cg-SDT-TimeAlignmentTimer* is running, consider *cg-SDT-TimeAlignmentTimer* as expired and perform the corresponding actions in clause 5.2; + - 3> indicate to the upper layers that the conditions for initiating SDT procedure are fulfilled. + - 2> else: + - 3> indicate to the upper layers that the conditions for initiating SDT procedure are not fulfilled. +- 1> else: + - 2> indicate to the upper layers that the conditions for initiating SDT procedure are not fulfilled. + +If Random Access procedure is selected above for SDT procedure initiated for MO-SDT or MT-SDT and after the Random Access procedure is successfully completed (see clause 5.1.6), the UE monitors PDCCH addressed to C-RNTI received in random access response until the SDT procedure is terminated. If CG-SDT is selected above and after the initial transmission for CG-SDT is performed, the UE monitors PDCCH addressed to C-RNTI as stored in UE Inactive AS context as specified in TS 38.331 [5] and CS-RNTI until the SDT procedure is terminated. + +NOTE 2: When the UE determines if there is an SSB with SS-RSRP above *cg-SDT-RSRP-ThresholdSSB*, the UE uses the latest unfiltered L1-RSRP measurement. + +## 5.27.2 TA Validation for CG-SDT + +RRC configures the following parameters for TA validation for CG-SDT: + +- *cg-SDT-RSRP-ChangeThreshold*: RSRP threshold for the increase/decrease of RSRP for time alignment validation. + +The MAC entity shall, upon the reception of CG-SDT configuration: + +- 1) store the current RSRP of the downlink pathloss reference for TA validation as defined in TS 38.331 [5] clause 5.7.17. + +The MAC entity shall consider the TA of the initial CG-SDT transmission with CCCH message to be valid when the following conditions are fulfilled: + +- 1) The RSRP values for the stored downlink pathloss reference and the current downlink pathloss reference are valid according to TS 38.133 [11]; and +- 1) Compared to the stored downlink pathloss reference RSRP value, the current RSRP value of the downlink pathloss reference calculated as specified in TS 38.133 [11] has not increased/decreased by more than *cg-SDT-RSRP-ChangeThreshold*, if configured; and +- 1) *cg-SDT-TimeAlignmentTimer* is running. + +## 5.28 Sidelink Discontinuous Reception (DRX) + +### 5.28.1 General + +The MAC entity may be configured by RRC with an SL DRX functionality that controls the UE's SCI (i.e., 1st stage SCI and 2nd stage SCI) monitoring activity for unicast, groupcast and broadcast. When using SL DRX operation, the MAC entity shall also monitor SCI (i.e., 1st stage SCI and 2nd stage SCI) according to requirements found in other clauses of this specification. + +Sidelink DRX and UE procedure on SL-PRS dedicated resource pool are not applied at the same time. + +RRC controls Sidelink DRX operation by configuring the following parameters: + +- *sl-drx-onDurationTimer/sl-DRX-GC-BC-OnDurationTimer*: the duration at the beginning of an SL DRX cycle; +- *sl-drx-SlotOffset*: the delay before starting the *sl-drx-onDurationTimer/sl-DRX-GC-BC-OnDurationTimer*; +- *sl-drx-InactivityTimer/sl-DRX-GC-InactivityTimer* (except for the SL broadcast communication): the duration after the first slot of SCI (i.e., 1st stage SCI and 2nd stage SCI) reception in which an SCI indicates a new SL transmission for the MAC entity; +- *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer* (per Sidelink process except for the SL broadcast process): the maximum duration until an SL retransmission is received; +- *sl-drx-StartOffset*: the slot where the SL DRX cycle starts; +- *sl-drx-Cycle/sl-DRX-GC-BC-Cycle*: the Sidelink DRX cycle; +- *sl-drx-HARQ-RTT-Timer/sl-DRX-GC-HARQ-RTT-Timer* (per Sidelink process except for the SL broadcast process): the minimum duration before an SL HARQ retransmission is expected by the MAC entity. + +### 5.28.2 Behaviour of UE receiving SL-SCH Data + +When SL DRX is configured, the Active Time includes the time while: + +- *sl-drx-onDurationTimer/sl-DRX-GC-BC-OnDurationTimer* or *sl-drx-InactivityTimer/sl-DRX-GC-InactivityTimer* is running; or +- *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer* is running; or +- period of *sl-LatencyBoundCSI-Report* configured by RRC in case SL-CSI reporting MAC CE is not received; or +- the time between the transmission of the request of SL-CSI reporting and the reception of the SL-CSI reporting MAC CE in case SL-CSI reporting MAC CE is received; or +- Slot(s) associated with the announced periodic transmission(s) by the UE transmitting SL-SCH Data; or + +- the time between transmission/reception of Direct Link Establishment Request message (TS 24.587 [28]) or ProSe Direct Link Establishment Request message (TS 24.554 [29]) and reception of *RRCReconfigurationSidelink* message including initial DRX configuration or the link establishment procedure being aborted by upper layer; or +- the time between transmission of *RRCReconfigurationSidelink* message including initial DRX configuration and reception of corresponding *RRCReconfigurationCompleteSidelink* or *RRCReconfigurationFailureSidelink* message. + +When one or multiple SL DRX is configured, the MAC entity shall: + +- 1> if a single *sl-DRX-GC-BC-Cycle* that is mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* or a single *sl-DRX-GC-BC-Cycle* that is configured in *sl-DefaultDRX-GC-BC* and cannot be mapped with any *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* is associated to a Destination and the associated cast type is groupcast or broadcast: + - 2> select the *sl-DRX-GC-BC-Cycle* that is mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* or the *sl-DRX-GC-BC-Cycle* configured in *sl-DefaultDRX-GC-BC* associated with the Destination. +- 1> else if multiple *sl-DRX-GC-BC-Cycle* that include one or multiple *sl-DRX-GC-BC-Cycle* that are mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* and, if applicable, one *sl-DRX-GC-BC-Cycle* that is configured in *sl-DefaultDRX-GC-BC* and cannot be mapped with any *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* are associated to a Destination Layer-2 ID and the associated cast type groupcast or broadcast: + - 2> select the *sl-DRX-GC-BC-Cycle* whose length is the shortest one among multiple *sl-DRX-GC-BC-Cycle* that are mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* and *sl-DRX-GC-BC-Cycle* configured in *sl-DefaultDRX-GC-BC* associated with the Destination Layer-2 ID. +- 1> if a single *sl-DRX-GC-BC-OnDurationTimer* that is mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* or a single *sl-DRX-GC-BC-OnDurationTimer* that is configured in *sl-DefaultDRX-GC-BC* and cannot be mapped with any *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* is associated to a Destination and the associated cast type is groupcast or broadcast: + - 2> select the *sl-DRX-GC-BC-OnDurationTimer* that is mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* or the *sl-DRX-GC-BC-OnDurationTimer* configured in *sl-DefaultDRX-GC-BC* associated with the Destination. +- 1> else if multiple *sl-DRX-GC-BC-OnDurationTimer* that include one or multiple *sl-DRX-GC-BC-OnDurationTimer* that are mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* and, if applicable, one *sl-DRX-GC-BC-OnDurationTimer* that is configured in *sl-DefaultDRX-GC-BC* and cannot be mapped with any *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* are associated to a Destination Layer-2 ID and the associated cast type is groupcast or broadcast: + - 2> select the *sl-DRX-GC-BC-OnDurationTimer* whose length is the longest one among multiple *sl-DRX-GC-BC-OnDurationTimer* that are mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* and *sl-DRX-GC-BC-Cycle* configured in *sl-DefaultDRX-GC-BC* associated with the Destination Layer-2 ID. +- 1> if a single *sl-DRX-GC-InactivityTimer* that is mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* or a single *sl-DRX-GC-InactivityTimer* that is configured in *sl-DefaultDRX-GC-BC* and cannot be mapped with any *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* is associated to a Destination and the associated cast type is groupcast: + - 2> select the *sl-DRX-GC-InactivityTimer* that is mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* or the *sl-DRX-GC-InactivityTimer* configured in *sl-DefaultDRX-GC-BC* associated with the Destination. +- 1> else if multiple *sl-DRX-GC-InactivityTimer* that include one or multiple *sl-DRX-GC-InactivityTimer* that are mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* and, if applicable, one *sl-DRX-GC-InactivityTimer* that is configured in *sl-DefaultDRX-GC-BC* and cannot be mapped with any *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* of a Destination Layer-2 ID and the associated cast type is groupcast: + +2> select *sl-DRX-GC-InactivityTimer* whose length is the longest one among multiple *sl-DRX-GC-InactivityTimer* that are mapped with one or multiple *SL-QoS-Profile* in *sl-DRX-GC-BC-PerQoS-List* and *sl-DRX-GC-InactivityTimer* configured in *sl-DefaultDRX-GC-BC* associated with the Destination Layer-2 ID. + +1> if an *sl-drx-HARQ-RTT-Timer* expires: + +2> if the data of the corresponding Sidelink process was not successfully decoded or if the HARQ feedback (i.e., negative acknowledgement) is not transmitted for unicast due to UL/SL prioritization: + +3> start the *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer* for the corresponding Sidelink process in the first slot after the expiry of *sl-drx-HARQ-RTT-Timer*. + +When the cast type is groupcast or broadcast as indicated by upper layer, or the cast type is unicast for the reception of Direct Link Establishment Request message [28] or ProSe Direct Link Establishment Request message [29] as indicated by upper layer, or for the reception of discovery message [26], the *sl-drx-StartOffset* and *sl-drx-SlotOffset* are derived from the following equations: + +$$sl-drx-StartOffset \text{ (ms)} = \text{Destination Layer-2 ID modulo } sl-DRX-GC-BC-Cycle \text{ (ms)}.$$ + +$$sl-drx-SlotOffset \text{ (ms)} = (\text{Destination Layer-2 ID modulo the number of slots in one subframe}) / (\text{the number of slots in one subframe}) \text{ (ms)}.$$ + +1> if the SL DRX cycle is used, and $[(DFN \times 10) + \text{subframe number}] \text{ modulo } (sl-drx-Cycle \text{ or } sl-DRX-GC-BC-Cycle) = sl-drx-StartOffset$ : + +2> start *sl-drx-onDurationTimer/sl-DRX-GC-BC-OnDurationTimer* after *sl-drx-SlotOffset* from the beginning of the subframe. + +1> if an SL DRX is in Active Time: + +2> monitor the SCI (i.e., 1st stage SCI and 2nd stage SCI). + +2> if the SCI indicates a new SL transmission: + +3> if Source Layer-1 ID of the SCI is equal to the 8 LSB of the intended Destination Layer-2 ID and Destination Layer-1 ID of the SCI is equal to the 16 LSB of the intended Source Layer-2 ID and the cast type indicator in the SCI is set to unicast: + +4> start or restart *sl-drx-InactivityTimer* for the corresponding Source Layer-2 ID and Destination Layer-2 ID pair in the first slot after SCI reception. + +3> if Destination Layer-1 ID of the SCI (i.e., 2nd stage SCI) is equal to the 16 LSB of the intended Destination Layer-2 ID and the cast type indicator in the SCI is set to groupcast: + +4> start or restart *sl-DRX-GC-InactivityTimer* for the corresponding Destination Layer-2 ID in the first slot after SCI reception. + +2> if the SCI indicates an SL transmission: + +3> if a next retransmission opportunity is indicated in the SCI: + +4> derive the *sl-drx-HARQ-RTT-Timer* from the retransmission resource timing of the next retransmission resource in the SCI. + +3> else if PSFCH resource is configured for the SL grant associated to the SCI: + +4> set the *sl-drx-HARQ-RTT-Timer* based on *sl-drx-HARQ-RTT-Timer1* configured by upper layer if the cast type associated with the SCI is unicast or *sl-DRX-GC-HARQ-RTT-Timer1* configured by upper layer if the cast type associated with the SCI is groupcast when HARQ feedback is enabled, or based on *sl-drx-HARQ-RTT-Timer2* configured by upper layer if the cast type associated with the SCI is unicast or *sl-DRX-GC-HARQ-RTT-Timer2* configured by upper layer if the cast type associated with the SCI is groupcast when HARQ feedback is disabled, for resource pool configured with PSFCH. + +3> else (i.e., if PSFCH resource is not configured for the SL grant associated to the SCI): + +4> set the *sl-drx-HARQ-RTT-Timer* as 0 slots. + +- 3> if PSFCH resource is not configured for the SL grant associated to the SCI: + - 4> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the slot following the end of PSSCH transmission (i.e., currently received PSSCH). +- 3> if PSFCH resource is configured for the SL grant associated to the SCI: + - 4> if HARQ feedback is enabled by the SCI and the cast type associated with the SCI is unicast: + - 5> if *numPSFCHOccasions* is configured as specified in TS 38.331 [5]: + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of corresponding PSFCH transmission carrying the SL HARQ Feedback when the SL HARQ feedback is successfully transmitted in one of PSFCH occasions from *numPSFCHOccasions*; or + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the last PSFCH occasion for the SL HARQ Feedback when the SL HARQ feedback is not transmitted in all PSFCH occasions from *numPSFCHOccasions*. + - 5> else: + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH transmission carrying the SL HARQ feedback; or + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH resource for the SL HARQ feedback when the SL HARQ feedback is not transmitted due to UL/SL prioritization or SL LBT failure. + - 4> if HARQ feedback is enabled by the SCI and the cast type associated with the SCI is groupcast and positive-negative acknowledgement is selected: + - 5> if *numPSFCHOccasions* is configured as specified in TS 38.331 [5]: + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the last PSFCH occasion for the SL HARQ Feedback from + - 5> else: + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH transmission carrying the SL HARQ feedback; or + - 6> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH resource for the SL HARQ feedback when the SL HARQ feedback is not transmitted due to UL/SL prioritization. + - 4> if HARQ feedback is enabled by the SCI and the cast type associated with the SCI is groupcast and negative-only acknowledgement is selected: + - 5> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH transmission carrying the SL HARQ feedback; or + - 5> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH resource for the SL HARQ feedback when the SL HARQ feedback is not transmitted due to UL/SL prioritization; or + - 5> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the first slot after the end of the corresponding PSFCH resource for the SL HARQ feedback when the SL HARQ feedback is a positive acknowledgement. + - 4> if HARQ feedback is disabled by the SCI and the resource(s) for one or more retransmission opportunities is not scheduled in the SCI: + - 5> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the slot following the end of PSFCH resource. + +- 4> if HARQ feedback is disabled by the SCI and the resource(s) for one or more retransmission opportunities is scheduled in the SCI: + - 5> start the *sl-drx-HARQ-RTT-Timer* for the corresponding Sidelink process in the slot following the end of PSSCH transmission (i.e., currently received PSSCH). + +NOTE: Void. + +- 3> stop the *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer* for the corresponding Sidelink process. +- 1> if an SL DRX Command MAC CE is received for the Source Layer-2 ID and Destination Layer-2 ID pair of a unicast: + - 2> stop *sl-drx-onDurationTimer* for the Source Layer-2 ID and Destination Layer-2 ID pair of a unicast; + - 2> stop *sl-drx-InactivityTimer* for the Source Layer-2 ID and Destination Layer-2 ID pair of a unicast. + +### 5.28.3 Behaviour of UE transmitting SL-SCH Data + +The UE transmitting SL-SCH Data should keep aligned with its intended UE receiving the SL-SCH Data regarding the SL DRX Active time as specified in clause 5.28.2. + +Furthermore, the UE transmitting SL-SCH Data determines the SL DRX Active time based on SL DRX timers that are running (e.g., *sl-drx-onDurationTimer/sl-DRX-GC-BC-OnDurationTimer*, *sl-drx-InactivityTimer/sl-DRX-GC-InactivityTimer*, *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer*) or will be running in the future (e.g., *sl-drx-onDurationTimer/sl-DRX-GC-BC-OnDurationTimer*, *sl-drx-InactivityTimer/sl-DRX-GC-InactivityTimer*, *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer*) at the UE(s) receiving SL-SCH data. The UE may select resource for the initial transmission of groupcast within the time when *sl-DRX-GC-BC-OnDurationTimer* or *sl-DRX-GC-InactivityTimer* of the destination is running. + +NOTE 1: A UE may assume that a resource for retransmission is in the Active time if an initial transmission causes the *sl-drx-RetransmissionTimer/sl-DRX-GC-RetransmissionTimer* to be started at the receiving UE. + +NOTE 2: A UE may send SL DRX Command MAC CE to receiving UE for unicast and when to send SL DRX Command MAC CE is up to UE implementation. + +The MAC entity shall for each Destination Layer-2 ID associated with groupcast that is interested in NR sidelink transmission: + +- 1> if the SCI indicates a new transmission where the cast type is set to groupcast is transmitted: + - 2> start or restart *sl-DRX-GC-InactivityTimer* for the corresponding Destination Layer-2 ID in the first slot after SCI transmission. + +The MAC entity shall for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to each PC5-RRC connection which has been established by upper layers: + +- 1> if the SL DRX Command indication has been triggered by the UE: + - 2> if the MAC entity has SL resources allocated for new transmission and the SL-SCH resources can accommodate the SL DRX Command MAC CE and its subheader as a result of logical channel prioritization: + - 3> instruct the Multiplexing and Assembly procedure to generate a Sidelink DRX Command MAC CE as defined in clause 6.1.3.52; + - 3> cancel the triggered SL DRX Command indication. + - 2> else if the MAC entity has been configured with Sidelink resource allocation mode 1: + - 3> trigger a Scheduling Request. + +## 5.29 Activation/Deactivation of SCG + +The network may activate and deactivate the configured SCG. + +The MAC entity shall for the configured SCG: + +- 1> if upper layers indicate that SCG is activated: + - 2> if *BFI\_COUNTER* >= *beamFailureInstanceMaxCount* for the PSCell or the *timeAlignmentTimer* associated with PTAG is not running: + - 3> indicate to upper layers that a Random Access Procedure (as specified in clause 5.1.1) is needed for SCG activation. + - 2> activate the SCG according to the timing defined in TS 38.133 [11]. + - 2> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this PSCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2.2; + - 2> apply normal SCG operation including: + - 3> SRS transmissions on the PSCell; + - 3> CSI reporting for the PSCell; + - 3> PDCCH monitoring on the PSCell; + - 3> PUCCH transmissions on the PSCell; + - 3> transmit on RACH on the PSCell; + - 3> initialize *Bj* for each logical channel to zero. +- 1> else if upper layers indicate that the SCG is deactivated: + - 2> deactivate all the SCells of the SCG according to clause 5.9; + - 2> deactivate SCG according to the timing defined in TS 38.133 [11]; + - 2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the PSCell respectively; + - 2> suspend any configured uplink grant Type 1 associated with the PSCell; + - 2> reset MAC according to clause 5.12. +- 1> if the SCG is deactivated: + - 2> not transmit SRS on the PSCell; + - 2> not report CSI for the PSCell; + - 2> not transmit on UL-SCH on the PSCell; + - 2> not transmit PUCCH on the PSCell; + - 2> not transmit on RACH on the PSCell; + - 2> not monitor the PDCCH on the PSCell. + +## 5.30 Handling of FR2 UL gap + +During the FR2 UL gap configured by *ul-GapFR2-Config* as specified in TS 38.331 [5], the MAC entity shall, on the Serving Cell(s) of FR2 single CC and intra-band CA, or on the Serving Cell(s) of FR2 inter-band CA where UE does not support *tx-Support-UL-GapFR2*: + +- 1> only perform transmission of: + - 2> PRACH preamble as specified in clause 5.1.2 and 5.1.2a; + - 2> UL-SCH for Msg3 or the MSGA payload as specified in clause 5.4.2.2; + - 2> UL-SCH for configured grant; + - 2> the valid CSI report during SCell activation procedure where the valid CSI report is valid CQI with non-zero CQI index defined in TS 38.214 [7], clause 5.2.2.1, when the time period between UL gap colliding with CSI report of non-zero CQI and the slot where the SCell activation MAC CE or CSI report activation command is received is no less than 10 ms; + - 2> the valid L1 RSRP report during SCell activation procedure, where the valid L1 RSRP report is non lowest L1 RSRP defined in TS 38.133 [11], clause 10.1.6, when the time period between UL gap colliding with L1 RSRP reporting and the slot where the SCell activation MAC CE or CSI report activation command is received is no less than 10 ms; + - 2> the PUCCH transmission for SR, and link recovery request (LRR) defined in TS 38.133 [11], clause 8.5. + +## 5.31 Sidelink LBT operation + +### 5.31.1 General + +The lower layer may perform an SL LBT procedure, see TS 37.213 [18], according to which a transmission is not performed by lower layers if the channel is identified as being occupied. When lower layer performs an SL LBT procedure before a transmission and the transmission is not performed, an SL LBT failure indication is sent to the MAC entity from lower layers. Unless otherwise specified, when SL LBT procedure is performed for a transmission, actions as specified in this specification are performed regardless of if an SL LBT failure indication is received from lower layers. When SL LBT is not performed by the lower layers, SL LBT failure indication is not received from lower layers. + +### 5.31.2 Sidelink LBT failure detection and recovery procedure + +The MAC entity may be configured by RRC with a SL consistent LBT failure detection and recovery procedure. SL consistent LBT failure is detected per RB set by counting SL LBT failure indications, for all SL transmissions, from the lower layers to the MAC entity. + +RRC configures the following parameters in the *sl-lbt-FailureRecoveryConfig*: + +- *sl-lbt-FailureInstanceMaxCount* for the SL consistent LBT failure detection; +- *sl-lbt-FailureDetectionTimer* for the SL consistent LBT failure detection; + +The following UE variable is used for the SL consistent LBT failure detection procedure: + +- *SL\_LBT\_COUNTER* (per RB set): counter for SL LBT failure indication which is initially set to 0. + +For activated SL BWP configured with *sl-lbt-FailureRecoveryConfig*, the MAC entity shall: + +- 1> if SL LBT failure indication has been received from lower layers for an RB set of the configured pool(s) of resources in the SL BWP: + - 2> start or restart the *sl\_lbt-FailureDetectionTimer* for the RB set, and it is not running; + - 2> increment *SL\_LBT\_COUNTER* for the RB set by 1; + - 2> if *SL\_LBT\_COUNTER* >= *sl-lbt-FailureInstanceMaxCount*: + - 3> trigger SL consistent LBT failure for the RB set in the SL BWP; + - 3> if consistent LBT failure has been triggered in all the RB sets of the configured pool(s) of resources in the SL BWP: + +4> indicate SL consistent LBT failure based Sidelink RLF detection to RRC. + +1> if all triggered SL consistent LBT failures are cancelled in a RB set; or + +1> if the *sl-lbt-FailureDetectionTimer* expires for a RB set: + +2> set *SL\_LBT\_COUNTER* to 0 for the RB set. + +1> if *sl-lbt-FailureDetectionTimer* or *sl-lbt-FailureInstanceMaxCount* is reconfigured by upper layers: + +2> set *SL\_LBT\_COUNTER* to 0 for all the RB sets. + +The *sl-LBT-RecoveryTimer* is used for recovery of the triggered SL consistent LBT failure, when RRC configures Sidelink resource allocation mode 2. + +The MAC entity shall: + +1> if SL consistent LBT failure has been triggered, and not cancelled, in the RB set(s), and SL LBT failure MAC CE(s) has not been generated; + +2> if the *sl-LBT-RecoveryTimer* for the triggered SL consistent LBT failure is not running: + +3> start the *sl-LBT-RecoveryTimer*. + +2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL LBT failure MAC CE plus its subheader as a result of logical channel prioritization according to clause 5.4.3.1: + +3> instruct the Multiplexing and Assembly procedure in clause 5.4.3 to generate the SL LBT failure MAC CE(s). + +2> else: + +3> trigger a Scheduling Request for SL LBT failure MAC CE. + +1> if a MAC PDU is transmitted and this PDU includes the SL LBT failure MAC CE; or + +2> cancel the triggered SL consistent LBT failure(s) in RB set(s) for which SL consistent LBT failure was indicated in the transmitted SL LBT failure MAC CE if the MAC entity has been configured with Sidelink resource allocation mode 1. + +1> if the *sl-LBT-RecoveryTimer* for the triggered SL consistent LBT failure(s) expires: + +2> cancel the triggered SL consistent LBT failure(s) in RB set(s) for which SL consistent LBT failure was detected. + +1> if *sl-lbt-FailureRecoveryConfig* is reconfigured by upper layers for the BWP: + +2> cancel all the triggered SL consistent LBT failure(s) in the SL BWP. + +## 5.32 SRS for positioning Tx frequency hopping + +SRS for positioning Tx frequency hopping can be supported for UE in RRC\_CONNECTED and RRC\_INACTIVE. The UE can be configured with UTW during which the UE is allowed to transmit SRS for positioning Tx frequency hopping. + +RRc configures the following parameters for the UTW for SRS for positioning Tx frequency hopping: + +- *utw-SlotPeriodicity*: Periodicity of the UTW in slot; +- *utw-SlotOffset*: Offset of the beginning of the UTW with respect to the beginning of the UTW periodicity in time domain in slot; +- *uplinkTimeWindowTimer*: Time duration when the UE performs SRS transmission for positioning Tx frequency hopping. + +When UTW is configured, the MAC entity shall start the *uplinkTimeWindowTimer* in the first symbol of the slot that the following condition is satisfied + +$$\text{CURRENT\_slot modulo (utw-SlotPeriodicity)} = \text{utw-SlotOffset}$$ + +where $\text{CURRENT\_slot} = [(\text{SFN} \times \text{numberOfSlotsPerFrame}) + \text{slot number in the frame}]$ and *numberOfSlotsPerFrame* refers to the number of consecutive slots per frame as specified in TS 38.211 [8]. + +When UTW is configured and the UE is in RRC\_CONNECTED, the MAC entity shall instruct the lower layer to transmit SRS for positioning Tx frequency hopping when the *uplinkTimeWindowTimer* is running. + +## 5.33 RACH-less initial UL transmission + +The initial uplink transmission of a RACH-less handover procedure can be performed either using a dynamic uplink grant or a configured uplink grant Type 1 preallocated by RRC, if configured. + +When *rach-LessHO* is configured, the MAC entity shall: + +- 1> if *cg-RACH-less-Configuration* is configured: + - 2> select a configured uplink grant for initial uplink transmission according to clause 5.8.2; + - 2> perform initial uplink transmission in the first available CG occasion for RACH-less handover according to clause 5.8.2. +- 1> else: + - 2> if *tci-StateID* is configured in *rach-lessHO*: + - 3> indicate to lower layers the TCI state information included in *tci-StateID*. + - 2> else if *dg-beam* is configured in *rach-lessHO*: + - 3> indicate to lower layers the SSB index included in *dg-beam*. +- 1> monitor the PDCCH as specified in TS 38.213 [6]. + +## 5.34 Cell-Level Energy Saving + +### 5.34.1 General + +Each Serving Cell may be configured by RRC with a periodic cell DTX pattern (i.e., Active and Non-Active Periods). The cell DTX operation affects UE's monitoring activity of PDCCH and configured downlink assignments in RRC\_CONNECTED. For all activated Serving Cells with cell DTX configured and activated, the MAC entity may monitor PDCCH and configured downlink assignments using the cell DTX operation specified in clause 5.34.2. + +Each Serving Cell may be configured by RRC with a periodic cell DRX pattern (i.e., Active and Non-Active Periods). The cell DRX operation controls Scheduling Request and configured uplink grant transmission activity in RRC\_CONNECTED. For all activated Serving Cells with cell DRX configured and activated, the MAC entity may transmit configured uplink grant transmissions and Scheduling Request using the cell DRX operation specified in clause 5.34.3. + +RRC controls cell DTX and cell DRX operation by configuring the following parameters in *CellDTXDRX-Config* per Serving Cell: + +- *cellDTXDRXconfigType*: defines whether only cell DTX is configured, only cell DRX is configured, or both are configured; +- *celldtxdrx-onDurationTimer*: the active duration at the beginning of a cell DTX/DRX cycle; +- *celldtxdrx-StartOffset*: defines the subframe where the cell DTX/DRX cycle starts; +- *celldtxdrx-SlotOffset*: the delay before starting the *celldtxdrx-onDurationTimer*; + +- *celldtxdrx-Cycle*: the cell DTX/DRX cycle period. +- *cellDTXDRXActivationStatus*: the initial activation status of cell DTX and cell DRX operation. + +## 5.34.2 Cell Discontinuous Transmission + +Cell DTX is configured if *cellDTXDRXconfigType* is set to *dtx* or *dtxdrx*. Cell DTX operation is activated and deactivated for each Serving Cell by: + +- receiving a cell DTX indication from lower layers indicating *activation* or *deactivation* of cell DTX operation, as specified in TS 38.213 [6]; +- configuring *CellDTXDRX-Config* by upper layers: if cell DTX is configured and *cellDTXDRXActivationStatus* is set to *activated*, cell DTX operation is activated upon cell DTX configuration; if cell DTX is configured and *cellDTXDRXActivationStatus* is set to *deactivated*, cell DTX operation is deactivated upon cell DTX configuration; if *CellDTXDRX-Config* is released, cell DTX operation is deactivated and all the corresponding configurations are released. + +When cell DTX is configured and activated for a Serving Cell, the cell DTX Active Period includes the time while: + +- *celldtxdrx-onDurationTimer* is running for the associated Serving Cell. + +For each Serving Cell configured with cell DTX, the MAC entity shall: + +- 1> if cell DTX is activated for this Serving Cell: + - 2> if $[(\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{celldtxdrx-Cycle}) = (\text{celldtxdrx-StartOffset})$ : + - 3> start *celldtxdrx-onDurationTimer* for this serving cell after *celldtxdrx-SlotOffset* from the beginning of the subframe. +- 1> if cell DTX operation is deactivated for this Serving Cell; or +- 1> if the Serving Cell is in the cell DTX Active Period: + - 2> monitor PDCCH on this Serving Cell, as specified in TS 38.213 [6] and other clauses of this specification. +- 1> if any *drx-RetransmissionTimerDL*, *drx-RetransmissionTimerUL* or *drx-RetransmissionTimerSL* (as described in clause 5.7) is running on any Serving Cell in the DRX group of this Serving Cell; or +- 1> if *ra-ContentionResolutionTimer* (as described in clause 5.1.5) or *msgB-ResponseWindow* (as described in clause 5.1.4a) is running; or +- 1> if a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4 or 5.22.1.5); or +- 1> if a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble (as described in clauses 5.1.4 and 5.1.4a): + - 2> monitor PDCCH on the Serving Cells in the DRX group of this Serving Cell, as specified in TS 38.213 [6] and other clauses of this specification. +- 1> if *ra-ResponseWindow* (as described in clause 5.1.4) is running and this Serving Cell is the SpCell: + - 2> monitor PDCCH on this Serving Cell (as described in clause 5.1.4). + +For each Serving Cell configured with cell DTX, the MAC entity may: + +- 1> if cell DTX operation is activated and the Serving Cell is not in the cell DTX Active Period: + - 2> not monitor PDCCH irrespective of the requirements of clauses 5.7 and 5.7b, unless stated otherwise in this clause; + - 2> not instruct the physical layer to receive transport block on the DL-SCH of this Serving Cell according to a configured downlink assignment for SPS; + +- 2> not indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity; +- 2> not set the HARQ Process ID to the HARQ Process ID associated with the PDSCH duration of a configured downlink assignment; +- 2> not consider the NDI bit for the HARQ process corresponding to the PDSCH duration of a configured downlink assignment to have been toggled for the configured downlink assignment. + +### 5.34.3 Cell Discontinuous Reception + +Cell DRX is configured if *cellDTXDRXConfigType* is set to *drx* or *dtxdrx*. Cell DRX operation is activated and deactivated for each Serving Cell by: + +- receiving a cell DRX indication from lower layers indicating *activation* or *deactivation* of cell DRX operation, as specified in TS 38.213 [6]; +- configuring *CellDTXDRX-Config* by upper layers: if cell DRX is configured and *cellDTXDRXActivationStatus* is set to *activated*, cell DRX operation is activated upon cell DRX configuration; if cell DRX is configured and *cellDTXDRXActivationStatus* is set to *deactivated*, cell DRX operation is deactivated upon cell DRX configuration; if *CellDTXDRX-Config* is released, cell DRX operation is deactivated and all the corresponding configurations are released. + +When cell DRX is configured and activated for a Serving Cell, the cell DRX Active Period includes the time while: + +- *celldtxdrx-onDurationTimer* is running for the associated Serving Cell. + +For each Serving Cell configured with cell DRX, the MAC entity shall: + +- 1> if cell DRX is activated for this Serving Cell: + - 2> if $[(\text{SFN} \times 10) + \text{subframe number}] \bmod (\text{celldtxdrx-Cycle}) = (\text{celldtxdrx-StartOffset})$ : + - 3> start *celldtxdrx-onDurationTimer* for this serving cell after *celldtxdrx-SlotOffset* from the beginning of the subframe. +- 1> if cell DRX is activated and the Serving Cell is not in the cell DRX Active Period: + - 2> not instruct the physical layer to signal a SR on a PUCCH resource for SR; + - 2> not increment the *SR\_COUNTER* for a SR; + - 2> not start the *sr-ProhibitTimer* for a SR; + - 2> not deliver any configured uplink grant and the associated HARQ information to the HARQ entity; + - 2> not instruct a HARQ process associated with a configured uplink grant to trigger a new transmission or a retransmission; + - 2> not report periodic CSI on PUCCH and semi-persistent CSI configured on PUSCH; + - 2> if an emergency service is initiated by upper layers and this Serving Cell is the SpCell: + - 3> initiate a Random Access procedure (as specified in clause 5.1.1). + +NOTE: How the MAC layer in the UE is aware of an ongoing emergency service is up to UE implementation. + +## 6 Protocol Data Units, formats and parameters + +### 6.1 Protocol Data Units + +#### 6.1.1 General + +A MAC PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in clause 6, bit strings are represented by tables in which the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit. + +A MAC SDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. A MAC SDU is included into a MAC PDU from the first bit onward. + +A MAC CE is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. + +A MAC subheader is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. Each MAC subheader is placed immediately in front of the corresponding MAC SDU, MAC CE, or padding. + +The MAC entity shall ignore the value of the Reserved bits in downlink MAC PDUs. + +#### 6.1.2 MAC PDU (DL-SCH and UL-SCH except transparent MAC and Random Access Response) + +A MAC PDU consists of one or more MAC subPDUs. Each MAC subPDU consists of one of the following: + +- A MAC subheader only (including padding); +- A MAC subheader and a MAC SDU; +- A MAC subheader and a MAC CE; +- A MAC subheader and padding. + +The MAC SDUs are of variable sizes. + +Each MAC subheader corresponds to either a MAC SDU, a MAC CE, or padding. + +A MAC subheader except for fixed sized MAC CE, padding, and a MAC SDU containing UL CCCH consists of the header fields R/F/LCID/(eLCID)/L. A MAC subheader for fixed sized MAC CE and padding consists of the header fields R/LCID/(eLCID). A MAC subheader for a MAC SDU containing UL CCCH consists of the header fields (LX)/R/LCID. + +![Diagram showing three examples of MAC subheaders with 8-bit L field. Each example shows a header with R, F, and LCID fields, followed by one or more data blocks (L or eLCID). Labels Oct 1, Oct 2, Oct 3, and Oct 4 are on the right.](93c9262c68d25c26b8cf8cd547554d9f_img.jpg) + +The diagram illustrates three examples of MAC subheaders with an 8-bit L field. Each example consists of a header row and one or more data rows. + +**Example 1:** + +| | | | | | | | | +|---|---|------|--|--|--|--|--| +| | | | | | | | | +| R | F | LCID | | | | | | +| L | | | | | | | | + +Labels: Oct 1, Oct 2 + +**Example 2:** + +| | | | | | | | | +|-------|---|------|--|--|--|--|--| +| | | | | | | | | +| R | F | LCID | | | | | | +| eLCID | | | | | | | | +| L | | | | | | | | + +Labels: Oct 1, Oct 2, Oct 3 + +**Example 3:** + +| | | | | | | | | +|-------|---|------|--|--|--|--|--| +| | | | | | | | | +| R | F | LCID | | | | | | +| eLCID | | | | | | | | +| eLCID | | | | | | | | +| L | | | | | | | | + +Labels: Oct 1, Oct 2, Oct 3, Oct 4 + +Diagram showing three examples of MAC subheaders with 8-bit L field. Each example shows a header with R, F, and LCID fields, followed by one or more data blocks (L or eLCID). Labels Oct 1, Oct 2, Oct 3, and Oct 4 are on the right. + +Figure 6.1.2-1: R/F/LCID/(eLCID)/L MAC subheader with 8-bit L field + +![Diagram showing three examples of MAC subheaders with 16-bit L field. Each example starts with a header row containing R, F, and LCID. The first example has two 'L' fields (Oct 2, Oct 3). The second example has 'eLCID' (Oct 2), 'L' (Oct 3), and 'L' (Oct 4). The third example has 'eLCID' (Oct 2), 'eLCID' (Oct 3), 'L' (Oct 4), and 'L' (Oct 5).](83fd0d406cba6f9c189e77e05859a600_img.jpg) + +| | | | | | | | | | +|---|---|------|--|--|--|--|--|-------| +| | | | | | | | | | +| R | F | LCID | | | | | | Oct 1 | +| L | | | | | | | | Oct 2 | +| L | | | | | | | | Oct 3 | + + + +| | | | | | | | | | +|-------|---|------|--|--|--|--|--|-------| +| | | | | | | | | | +| R | F | LCID | | | | | | Oct 1 | +| eLCID | | | | | | | | Oct 2 | +| L | | | | | | | | Oct 3 | +| L | | | | | | | | Oct 4 | + + + +| | | | | | | | | | +|-------|---|------|--|--|--|--|--|-------| +| | | | | | | | | | +| R | F | LCID | | | | | | Oct 1 | +| eLCID | | | | | | | | Oct 2 | +| eLCID | | | | | | | | Oct 3 | +| L | | | | | | | | Oct 4 | +| L | | | | | | | | Oct 5 | + +Diagram showing three examples of MAC subheaders with 16-bit L field. Each example starts with a header row containing R, F, and LCID. The first example has two 'L' fields (Oct 2, Oct 3). The second example has 'eLCID' (Oct 2), 'L' (Oct 3), and 'L' (Oct 4). The third example has 'eLCID' (Oct 2), 'eLCID' (Oct 3), 'L' (Oct 4), and 'L' (Oct 5). + +Figure 6.1.2-2: R/F/LCID/(eLCID)/L MAC subheader with 16-bit L field + +![Diagram showing two examples of (LX)/R/LCID/(eLCID) MAC subheaders. The first example has a header row with LX or R, R, and LCID (Oct 1), followed by a row with eLCID (Oct 2). The second example has a header row with R, R, and LCID (Oct 1), followed by a row with eLCID (Oct 2).](460b69ceb6eadef472ed6c71b44e920b_img.jpg) + +| | | | | | | | | | +|---------|---|------|--|--|--|--|--|-------| +| | | | | | | | | | +| LX or R | R | LCID | | | | | | Oct 1 | +| eLCID | | | | | | | | Oct 2 | + + + +| | | | | | | | | | +|-------|---|------|--|--|--|--|--|-------| +| | | | | | | | | | +| R | R | LCID | | | | | | Oct 1 | +| eLCID | | | | | | | | Oct 2 | + +Diagram showing two examples of (LX)/R/LCID/(eLCID) MAC subheaders. The first example has a header row with LX or R, R, and LCID (Oct 1), followed by a row with eLCID (Oct 2). The second example has a header row with R, R, and LCID (Oct 1), followed by a row with eLCID (Oct 2). + +Figure 6.1.2-3: (LX)/R/LCID/(eLCID) MAC subheader + +MAC CEs are placed together. DL MAC subPDU(s) with MAC CE(s) is placed before any MAC subPDU with MAC SDU and MAC subPDU with padding as depicted in Figure 6.1.2-4. UL MAC subPDU(s) with MAC CE(s) is placed after all the MAC subPDU(s) with MAC SDU and before the MAC subPDU with padding in the MAC PDU as depicted in Figure 6.1.2-5. The size of padding can be zero. + +![Figure 6.1.2-4: Example of a DL MAC PDU. This diagram illustrates the structure of a Downlink MAC Protocol Data Unit (PDU). It shows three MAC subPDUs. The first subPDU contains a subheader with R/LCID and a fixed-sized MAC Control Element (CE). The second subPDU contains a subheader with R/F/LCID/L and a variable-sized MAC CE. The third subPDU contains a subheader with R/F/LCID/L and a MAC SDU. Dashed lines connect the subheaders to their respective subPDUs. The third subPDU is followed by an ellipsis, and then another subPDU containing a MAC SDU and a subPDU containing optional padding.](df72bd7468eb8bd59e911d0b5cb7a810_img.jpg) + +Figure 6.1.2-4: Example of a DL MAC PDU. This diagram illustrates the structure of a Downlink MAC Protocol Data Unit (PDU). It shows three MAC subPDUs. The first subPDU contains a subheader with R/LCID and a fixed-sized MAC Control Element (CE). The second subPDU contains a subheader with R/F/LCID/L and a variable-sized MAC CE. The third subPDU contains a subheader with R/F/LCID/L and a MAC SDU. Dashed lines connect the subheaders to their respective subPDUs. The third subPDU is followed by an ellipsis, and then another subPDU containing a MAC SDU and a subPDU containing optional padding. + +Figure 6.1.2-4: Example of a DL MAC PDU + +![Figure 6.1.2-5: Example of a UL MAC PDU. This diagram illustrates the structure of an Uplink MAC Protocol Data Unit (PDU). It shows three MAC subPDUs. The first subPDU contains a subheader with R/F/LCID/L and a MAC SDU. The second subPDU contains a subheader with R/LCID and a fixed-sized MAC CE. The third subPDU contains a subheader with R/F/LCID/L and a variable-sized MAC CE. Dashed lines connect the subheaders to their respective subPDUs. The first subPDU is followed by an ellipsis, and then another subPDU containing a MAC SDU. The second subPDU is followed by an ellipsis, and then another subPDU containing a MAC CE. The third subPDU is followed by an ellipsis, and then another subPDU containing optional padding.](54d030ecf3f147af8773b8a23549856e_img.jpg) + +Figure 6.1.2-5: Example of a UL MAC PDU. This diagram illustrates the structure of an Uplink MAC Protocol Data Unit (PDU). It shows three MAC subPDUs. The first subPDU contains a subheader with R/F/LCID/L and a MAC SDU. The second subPDU contains a subheader with R/LCID and a fixed-sized MAC CE. The third subPDU contains a subheader with R/F/LCID/L and a variable-sized MAC CE. Dashed lines connect the subheaders to their respective subPDUs. The first subPDU is followed by an ellipsis, and then another subPDU containing a MAC SDU. The second subPDU is followed by an ellipsis, and then another subPDU containing a MAC CE. The third subPDU is followed by an ellipsis, and then another subPDU containing optional padding. + +Figure 6.1.2-5: Example of a UL MAC PDU + +A maximum of one MAC PDU can be transmitted per TB per MAC entity. + +### 6.1.3 MAC Control Elements (CEs) + +#### 6.1.3.1 Buffer Status Report MAC CEs + +Buffer Status Report (BSR) MAC CEs consist of either: + +- Short BSR format (fixed size); or +- Extended Short BSR format (fixed size); or +- Long BSR format (variable size); or +- Refined Long BSR format (variable size); or +- Extended Long BSR format (variable size); or +- Short Truncated BSR format (fixed size); or +- Extended Short Truncated BSR format (fixed size); or +- Long Truncated BSR format (variable size); or +- Extended Long Truncated BSR format (variable size). + +Pre-emptive BSR MAC CE consists of: + +- Pre-emptive BSR format (variable size); or +- Extended Pre-emptive BSR format (variable size). + +The BSR formats are identified by MAC subheaders with LCIDs as specified in Table 6.2.1-2. + +The Refined Long BSR format, Extended BSR formats and Pre-emptive BSR format are identified by MAC subheaders with eLCIDs as specified in Table 6.2.1-2b. + +The fields in the BSR MAC CE are defined as follows: + +- LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) whose buffer status is being reported. The length of the field is 3 bits for the case of Short BSR and Short Truncated BSR formats, and 8 bits for the case of Extended Short BSR and Extended Short Truncated BSR formats; +- LCGi: For the Long BSR format, Refined Long BSR format, Extended Long BSR format, Pre-emptive BSR format, and Extended Pre-emptive BSR format, this field indicates the presence of the Buffer Size field for the logical channel group i. The LCGi field set to 1 indicates that the Buffer Size field for the logical channel group i is reported. The LCGi field set to 0 indicates that the Buffer Size field for the logical channel group i is not reported. For the Long Truncated BSR format and the Extended Long Truncated BSR format, this field indicates whether logical channel group i has data available. The LCGi field set to 1 indicates that logical channel group i has data available. The LCGi field set to 0 indicates that logical channel group i does not have data available; +- BTi: This field is included only in the Refined Long BSR format. This field is present only if the corresponding LCGi is set to 1; otherwise, this field is reserved. If present, this field indicates which buffer size table is used to set the Buffer Size field for the logical channel group i. The BTi field set to 1 indicates that the buffer size table specified in Table 6.1.3.1-3 is used for the logical channel group i. The BTi field set to 0 indicates that the buffer size table specified in Table 6.1.3.1-2 is used for the logical channel group i; +- Buffer Size: The Buffer Size field identifies the total amount of data available according to the data volume calculation procedure in TSs 38.322 [3] and 38.323 [4] across all logical channels of a logical channel group after the MAC PDU has been built (i.e. after the logical channel prioritization procedure, which may result the value of the Buffer Size field to zero). The amount of data is indicated in number of bytes. The size of the RLC headers and MAC subheaders are not considered in the buffer size computation. The length of this field for the Short BSR format and the Short Truncated BSR format is 5 bits. The length of this field for the Extended Short BSR format and the Extended Short Truncated BSR format is 8 bits. The length of this field for the Long BSR format, the Refined Long BSR format, the Long Truncated BSR format, the Extended Long BSR format, and the Extended Long Truncated format is 8 bits. The values for the 5-bit Buffer Size fields are shown in Tables 6.1.3.1-1. The values for the 8-bit Buffer Size fields in the Long BSR format, the Long Truncated BSR format, the Extended Long BSR format, and the Extended Long Truncated format are shown in Table 6.1.3.1-2. For the Refined Long BSR format, if an LCG is configured with *additionalBSR-TableAllowed* and the amount of data for an LCG is within the buffer sizes specified in Table 6.1.3.1-3, the MAC entity shall use the buffer sizes specified in Table 6.1.3.1-3 to set the value of this field; otherwise, the MAC entity shall use Table 6.1.3.1-2 instead. For the Long BSR format, the Refined Long BSR format, the Long Truncated BSR format, the Extended Long BSR format, and the Extended Long Truncated format, the Buffer Size fields are included in ascending order based on the LCGi. For the Long Truncated BSR format and the Extended Long Truncated format the number of Buffer Size fields included is maximised, while not exceeding the number of padding bits. For the Pre-emptive BSR format and the Extended Pre-emptive BSR format, the Buffer Size field identifies the total amount of the data expected to arrive at the IAB-MT of the node where the Pre-emptive BSR/Extended Pre-emptive BSR is triggered and does not include the volume of data currently available in the IAB-MT. Pre-emptive BSR format is identical to the Long BSR format. Extended Pre-emptive BSR format is identical to the Extended Long BSR format. + +NOTE 1: For the Pre-emptive BSR, if configured, the LCGs to be reported, the expected data volume calculation, the exact time to report Pre-emptive BSR and the associated LCH are left to implementation. + +NOTE 2: The mapping of LCGs between the ingress and egress links of an IAB node for purposes of determining expected change in occupancy of IAB-MT buffers (to be reported as Pre-emptive BSR) is left to implementation. + +NOTE 3: The number of the Buffer Size fields in the Long BSR, Extended Long BSR, Long Truncated BSR, and Extended Long Truncated BSR format can be zero. + +NOTE 4: The Extended versions of the BSR formats can only be used by IAB nodes. + +![Diagram of Short BSR and Short Truncated BSR MAC CE structure. It shows a header with 8 bits, where the first 3 bits are LCG ID and the remaining 5 bits are Buffer Size. The diagram is labeled 'Oct 1' on the right.](89c2f25f101a9f211842647dd2373be7_img.jpg) + +| | | | | | | | | | +|--------|--|--|-------------|--|--|--|--|-------| +| | | | | | | | | | +| LCG ID | | | Buffer Size | | | | | Oct 1 | + +Diagram of Short BSR and Short Truncated BSR MAC CE structure. It shows a header with 8 bits, where the first 3 bits are LCG ID and the remaining 5 bits are Buffer Size. The diagram is labeled 'Oct 1' on the right. + +Figure 6.1.3.1-1: Short BSR and Short Truncated BSR MAC CE + +![Diagram of Long BSR, Long Truncated BSR, and Pre-emptive BSR MAC CE structure. It shows a header row of 8 empty cells, followed by a row of LCG IDs (LCG7 to LCG0), then rows for Buffer Size 1, Buffer Size 2, an ellipsis, and Buffer Size m. To the right of each row are labels Oct 1, Oct 2, Oct 3, ..., Oct m+1.](e27f0c293be4088211306b9fc673178b_img.jpg) + +| | | | | | | | | | +|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|---------| +| | | | | | | | | | +| LCG 7 | LCG 6 | LCG 5 | LCG 4 | LCG 3 | LCG 2 | LCG 1 | LCG 0 | Oct 1 | +| Buffer Size 1 | | | | | | | | Oct 2 | +| Buffer Size 2 | | | | | | | | Oct 3 | +| ... | | | | | | | | | +| Buffer Size m | | | | | | | | Oct m+1 | + +Diagram of Long BSR, Long Truncated BSR, and Pre-emptive BSR MAC CE structure. It shows a header row of 8 empty cells, followed by a row of LCG IDs (LCG7 to LCG0), then rows for Buffer Size 1, Buffer Size 2, an ellipsis, and Buffer Size m. To the right of each row are labels Oct 1, Oct 2, Oct 3, ..., Oct m+1. + +Figure 6.1.3.1-2: Long BSR, Long Truncated BSR, and Pre-emptive BSR MAC CE + +![Diagram of Extended Short BSR and Extended Short Truncated BSR MAC CE structure. It shows a header row of 8 empty cells, followed by a row for LCG ID, then a row for Buffer Size. To the right of these rows are labels Oct 1, Oct 2.](463f6f3874311dc4af977dd4c6290166_img.jpg) + +| | | | | | | | | | +|-------------|--|--|--|--|--|--|--|-------| +| | | | | | | | | | +| LCG ID | | | | | | | | Oct 1 | +| Buffer Size | | | | | | | | Oct 2 | + +Diagram of Extended Short BSR and Extended Short Truncated BSR MAC CE structure. It shows a header row of 8 empty cells, followed by a row for LCG ID, then a row for Buffer Size. To the right of these rows are labels Oct 1, Oct 2. + +Figure 6.1.3.1-3: Extended Short BSR and Extended Short Truncated BSR MAC CE + +![Diagram of Extended Long BSR, Extended Long Truncated BSR, and Extended Pre-emptive BSR MAC CE structure. It shows a header row of 8 empty cells, followed by two rows of LCG IDs (LCG7-LCG0 and LCG15-LCG8), an ellipsis, a row of LCG IDs (LCG255-LCG248), then rows for Buffer Size 1, Buffer Size 2, an ellipsis, and Buffer Size m. To the right of each row are labels Oct 1, Oct 2, ..., Oct 32, Oct 33, Oct 34, ..., Oct m+32.](ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg) + +| | | | | | | | | | +|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------|----------| +| | | | | | | | | | +| LCG 7 | LCG 6 | LCG 5 | LCG 4 | LCG 3 | LCG 2 | LCG 1 | LCG 0 | Oct 1 | +| LCG 15 | LCG 14 | LCG 13 | LCG 12 | LCG 11 | LCG 10 | LCG 9 | LCG 8 | Oct 2 | +| ... | | | | | | | | | +| LCG 255 | LCG 254 | LCG 253 | LCG 252 | LCG 251 | LCG 250 | LCG 249 | LCG 248 | Oct 32 | +| Buffer Size 1 | | | | | | | | Oct 33 | +| Buffer Size 2 | | | | | | | | Oct 34 | +| ... | | | | | | | | | +| Buffer Size m | | | | | | | | Oct m+32 | + +Diagram of Extended Long BSR, Extended Long Truncated BSR, and Extended Pre-emptive BSR MAC CE structure. It shows a header row of 8 empty cells, followed by two rows of LCG IDs (LCG7-LCG0 and LCG15-LCG8), an ellipsis, a row of LCG IDs (LCG255-LCG248), then rows for Buffer Size 1, Buffer Size 2, an ellipsis, and Buffer Size m. To the right of each row are labels Oct 1, Oct 2, ..., Oct 32, Oct 33, Oct 34, ..., Oct m+32. + +Figure 6.1.3.1-4: Extended Long BSR, Extended Long Truncated BSR, and Extended Pre-emptive BSR MAC CE + +![Diagram of Refined Long BSR MAC CE structure showing octets Oct 1 to Oct m+2. Oct 1 contains LCG7 to LCG0. Oct 2 contains BT7 to BT0. Oct 3 contains Buffer Size 1. Oct 4 contains Buffer Size 2. Ellipsis indicates intermediate octets. Oct m+2 contains Buffer Size m.](351243fd59cdae993f191da9ebb48016_img.jpg) + +| | | | | | | | | | +|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|---------| +| | | | | | | | | | +| LCG 7 | LCG 6 | LCG 5 | LCG 4 | LCG 3 | LCG 2 | LCG 1 | LCG 0 | Oct 1 | +| BT 7 | BT 6 | BT 5 | BT 4 | BT 3 | BT 2 | BT 1 | BT 0 | Oct 2 | +| Buffer Size 1 | | | | | | | | Oct 3 | +| Buffer Size 2 | | | | | | | | Oct 4 | +| ... | | | | | | | | | +| Buffer Size m | | | | | | | | Oct m+2 | + +Diagram of Refined Long BSR MAC CE structure showing octets Oct 1 to Oct m+2. Oct 1 contains LCG7 to LCG0. Oct 2 contains BT7 to BT0. Oct 3 contains Buffer Size 1. Oct 4 contains Buffer Size 2. Ellipsis indicates intermediate octets. Oct m+2 contains Buffer Size m. + +Figure 6.1.3.1-5: Refined Long BSR MAC CE + +Table 6.1.3.1-1: Buffer size levels (in bytes) for 5-bit Buffer Size field + +| Index | BS value | Index | BS value | Index | BS value | Index | BS value | +|-------|----------|-------|----------|-------|----------|-------|----------| +| 0 | 0 | 8 | ≤ 102 | 16 | ≤ 1446 | 24 | ≤ 20516 | +| 1 | ≤ 10 | 9 | ≤ 142 | 17 | ≤ 2014 | 25 | ≤ 28581 | +| 2 | ≤ 14 | 10 | ≤ 198 | 18 | ≤ 2806 | 26 | ≤ 39818 | +| 3 | ≤ 20 | 11 | ≤ 276 | 19 | ≤ 3909 | 27 | ≤ 55474 | +| 4 | ≤ 28 | 12 | ≤ 384 | 20 | ≤ 5446 | 28 | ≤ 77284 | +| 5 | ≤ 38 | 13 | ≤ 535 | 21 | ≤ 7587 | 29 | ≤ 107669 | +| 6 | ≤ 53 | 14 | ≤ 745 | 22 | ≤ 10570 | 30 | ≤ 150000 | +| 7 | ≤ 74 | 15 | ≤ 1038 | 23 | ≤ 14726 | 31 | > 150000 | + +**Table 6.1.3.1-2: Buffer size levels (in bytes) for 8-bit Buffer Size field** + +| Index | BS value | Index | BS value | Index | BS value | Index | BS value | +|-------|------------|-------|--------------|-------|----------------|-------|-----------------| +| 0 | 0 | 64 | $\leq 560$ | 128 | $\leq 31342$ | 192 | $\leq 1754595$ | +| 1 | $\leq 10$ | 65 | $\leq 597$ | 129 | $\leq 33376$ | 193 | $\leq 1868488$ | +| 2 | $\leq 11$ | 66 | $\leq 635$ | 130 | $\leq 35543$ | 194 | $\leq 1989774$ | +| 3 | $\leq 12$ | 67 | $\leq 677$ | 131 | $\leq 37850$ | 195 | $\leq 2118933$ | +| 4 | $\leq 13$ | 68 | $\leq 720$ | 132 | $\leq 40307$ | 196 | $\leq 2256475$ | +| 5 | $\leq 14$ | 69 | $\leq 767$ | 133 | $\leq 42923$ | 197 | $\leq 2402946$ | +| 6 | $\leq 15$ | 70 | $\leq 817$ | 134 | $\leq 45709$ | 198 | $\leq 2558924$ | +| 7 | $\leq 16$ | 71 | $\leq 870$ | 135 | $\leq 48676$ | 199 | $\leq 2725027$ | +| 8 | $\leq 17$ | 72 | $\leq 926$ | 136 | $\leq 51836$ | 200 | $\leq 2901912$ | +| 9 | $\leq 18$ | 73 | $\leq 987$ | 137 | $\leq 55200$ | 201 | $\leq 3090279$ | +| 10 | $\leq 19$ | 74 | $\leq 1051$ | 138 | $\leq 58784$ | 202 | $\leq 3290873$ | +| 11 | $\leq 20$ | 75 | $\leq 1119$ | 139 | $\leq 62599$ | 203 | $\leq 3504487$ | +| 12 | $\leq 22$ | 76 | $\leq 1191$ | 140 | $\leq 66663$ | 204 | $\leq 3731968$ | +| 13 | $\leq 23$ | 77 | $\leq 1269$ | 141 | $\leq 70990$ | 205 | $\leq 3974215$ | +| 14 | $\leq 25$ | 78 | $\leq 1351$ | 142 | $\leq 75598$ | 206 | $\leq 4232186$ | +| 15 | $\leq 26$ | 79 | $\leq 1439$ | 143 | $\leq 80505$ | 207 | $\leq 4506902$ | +| 16 | $\leq 28$ | 80 | $\leq 1532$ | 144 | $\leq 85730$ | 208 | $\leq 4799451$ | +| 17 | $\leq 30$ | 81 | $\leq 1631$ | 145 | $\leq 91295$ | 209 | $\leq 5110989$ | +| 18 | $\leq 32$ | 82 | $\leq 1737$ | 146 | $\leq 97221$ | 210 | $\leq 5442750$ | +| 19 | $\leq 34$ | 83 | $\leq 1850$ | 147 | $\leq 103532$ | 211 | $\leq 5796046$ | +| 20 | $\leq 36$ | 84 | $\leq 1970$ | 148 | $\leq 110252$ | 212 | $\leq 6172275$ | +| 21 | $\leq 38$ | 85 | $\leq 2098$ | 149 | $\leq 117409$ | 213 | $\leq 6572925$ | +| 22 | $\leq 40$ | 86 | $\leq 2234$ | 150 | $\leq 125030$ | 214 | $\leq 6999582$ | +| 23 | $\leq 43$ | 87 | $\leq 2379$ | 151 | $\leq 133146$ | 215 | $\leq 7453933$ | +| 24 | $\leq 46$ | 88 | $\leq 2533$ | 152 | $\leq 141789$ | 216 | $\leq 7937777$ | +| 25 | $\leq 49$ | 89 | $\leq 2698$ | 153 | $\leq 150992$ | 217 | $\leq 8453028$ | +| 26 | $\leq 52$ | 90 | $\leq 2873$ | 154 | $\leq 160793$ | 218 | $\leq 9001725$ | +| 27 | $\leq 55$ | 91 | $\leq 3059$ | 155 | $\leq 171231$ | 219 | $\leq 9586039$ | +| 28 | $\leq 59$ | 92 | $\leq 3258$ | 156 | $\leq 182345$ | 220 | $\leq 10208280$ | +| 29 | $\leq 62$ | 93 | $\leq 3469$ | 157 | $\leq 194182$ | 221 | $\leq 10870913$ | +| 30 | $\leq 66$ | 94 | $\leq 3694$ | 158 | $\leq 206786$ | 222 | $\leq 11576557$ | +| 31 | $\leq 71$ | 95 | $\leq 3934$ | 159 | $\leq 220209$ | 223 | $\leq 12328006$ | +| 32 | $\leq 75$ | 96 | $\leq 4189$ | 160 | $\leq 234503$ | 224 | $\leq 13128233$ | +| 33 | $\leq 80$ | 97 | $\leq 4461$ | 161 | $\leq 249725$ | 225 | $\leq 13980403$ | +| 34 | $\leq 85$ | 98 | $\leq 4751$ | 162 | $\leq 265935$ | 226 | $\leq 14887889$ | +| 35 | $\leq 91$ | 99 | $\leq 5059$ | 163 | $\leq 283197$ | 227 | $\leq 15854280$ | +| 36 | $\leq 97$ | 100 | $\leq 5387$ | 164 | $\leq 301579$ | 228 | $\leq 16883401$ | +| 37 | $\leq 103$ | 101 | $\leq 5737$ | 165 | $\leq 321155$ | 229 | $\leq 17979324$ | +| 38 | $\leq 110$ | 102 | $\leq 6109$ | 166 | $\leq 342002$ | 230 | $\leq 19146385$ | +| 39 | $\leq 117$ | 103 | $\leq 6506$ | 167 | $\leq 364202$ | 231 | $\leq 20389201$ | +| 40 | $\leq 124$ | 104 | $\leq 6928$ | 168 | $\leq 387842$ | 232 | $\leq 21712690$ | +| 41 | $\leq 132$ | 105 | $\leq 7378$ | 169 | $\leq 413018$ | 233 | $\leq 23122088$ | +| 42 | $\leq 141$ | 106 | $\leq 7857$ | 170 | $\leq 439827$ | 234 | $\leq 24622972$ | +| 43 | $\leq 150$ | 107 | $\leq 8367$ | 171 | $\leq 468377$ | 235 | $\leq 26221280$ | +| 44 | $\leq 160$ | 108 | $\leq 8910$ | 172 | $\leq 498780$ | 236 | $\leq 27923336$ | +| 45 | $\leq 170$ | 109 | $\leq 9488$ | 173 | $\leq 531156$ | 237 | $\leq 29735875$ | +| 46 | $\leq 181$ | 110 | $\leq 10104$ | 174 | $\leq 565634$ | 238 | $\leq 31666069$ | +| 47 | $\leq 193$ | 111 | $\leq 10760$ | 175 | $\leq 602350$ | 239 | $\leq 33721553$ | +| 48 | $\leq 205$ | 112 | $\leq 11458$ | 176 | $\leq 641449$ | 240 | $\leq 35910462$ | +| 49 | $\leq 218$ | 113 | $\leq 12202$ | 177 | $\leq 683087$ | 241 | $\leq 38241455$ | +| 50 | $\leq 233$ | 114 | $\leq 12994$ | 178 | $\leq 727427$ | 242 | $\leq 40723756$ | +| 51 | $\leq 248$ | 115 | $\leq 13838$ | 179 | $\leq 774645$ | 243 | $\leq 43367187$ | +| 52 | $\leq 264$ | 116 | $\leq 14736$ | 180 | $\leq 824928$ | 244 | $\leq 46182206$ | +| 53 | $\leq 281$ | 117 | $\leq 15692$ | 181 | $\leq 878475$ | 245 | $\leq 49179951$ | +| 54 | $\leq 299$ | 118 | $\leq 16711$ | 182 | $\leq 935498$ | 246 | $\leq 52372284$ | +| 55 | $\leq 318$ | 119 | $\leq 17795$ | 183 | $\leq 996222$ | 247 | $\leq 55771835$ | +| 56 | $\leq 339$ | 120 | $\leq 18951$ | 184 | $\leq 1060888$ | 248 | $\leq 59392055$ | +| 57 | $\leq 361$ | 121 | $\leq 20181$ | 185 | $\leq 1129752$ | 249 | $\leq 63247269$ | +| 58 | $\leq 384$ | 122 | $\leq 21491$ | 186 | $\leq 1203085$ | 250 | $\leq 67352729$ | +| 59 | $\leq 409$ | 123 | $\leq 22885$ | 187 | $\leq 1281179$ | 251 | $\leq 71724679$ | +| 60 | $\leq 436$ | 124 | $\leq 24371$ | 188 | $\leq 1364342$ | 252 | $\leq 76380419$ | +| 61 | $\leq 464$ | 125 | $\leq 25953$ | 189 | $\leq 1452903$ | 253 | $\leq 81338368$ | +| 62 | $\leq 494$ | 126 | $\leq 27638$ | 190 | $\leq 1547213$ | 254 | $> 81338368$ | +| 63 | $\leq 526$ | 127 | $\leq 29431$ | 191 | $\leq 1647644$ | 255 | Reserved | + + + +**Table 6.1.3.1-3. Buffer size levels (in bytes) for the Buffer Size field in Refined Long BSR** + +| | | | | | | | | +|----|-----------------------|-----|--------------|-----|---------------|-----|---------------| +| 0 | >4903 and $\leq$ 5000 | 64 | $\leq$ 17584 | 128 | $\leq$ 61841 | 192 | $\leq$ 217489 | +| 1 | $\leq$ 5099 | 65 | $\leq$ 17933 | 129 | $\leq$ 63069 | 193 | $\leq$ 221805 | +| 2 | $\leq$ 5200 | 66 | $\leq$ 18289 | 130 | $\leq$ 64320 | 194 | $\leq$ 226207 | +| 3 | $\leq$ 5303 | 67 | $\leq$ 18652 | 131 | $\leq$ 65596 | 195 | $\leq$ 230695 | +| 4 | $\leq$ 5408 | 68 | $\leq$ 19022 | 132 | $\leq$ 66898 | 196 | $\leq$ 235273 | +| 5 | $\leq$ 5516 | 69 | $\leq$ 19399 | 133 | $\leq$ 68226 | 197 | $\leq$ 239942 | +| 6 | $\leq$ 5625 | 70 | $\leq$ 19784 | 134 | $\leq$ 69580 | 198 | $\leq$ 244703 | +| 7 | $\leq$ 5737 | 71 | $\leq$ 20177 | 135 | $\leq$ 70960 | 199 | $\leq$ 249559 | +| 8 | $\leq$ 5851 | 72 | $\leq$ 20577 | 136 | $\leq$ 72368 | 200 | $\leq$ 254511 | +| 9 | $\leq$ 5967 | 73 | $\leq$ 20985 | 137 | $\leq$ 73804 | 201 | $\leq$ 259562 | +| 10 | $\leq$ 6085 | 74 | $\leq$ 21402 | 138 | $\leq$ 75269 | 202 | $\leq$ 264713 | +| 11 | $\leq$ 6206 | 75 | $\leq$ 21827 | 139 | $\leq$ 76763 | 203 | $\leq$ 269966 | +| 12 | $\leq$ 6329 | 76 | $\leq$ 22260 | 140 | $\leq$ 78286 | 204 | $\leq$ 275323 | +| 13 | $\leq$ 6455 | 77 | $\leq$ 22702 | 141 | $\leq$ 79839 | 205 | $\leq$ 280786 | +| 14 | $\leq$ 6583 | 78 | $\leq$ 23152 | 142 | $\leq$ 81424 | 206 | $\leq$ 286358 | +| 15 | $\leq$ 6713 | 79 | $\leq$ 23611 | 143 | $\leq$ 83040 | 207 | $\leq$ 292041 | +| 16 | $\leq$ 6847 | 80 | $\leq$ 24080 | 144 | $\leq$ 84687 | 208 | $\leq$ 297836 | +| 17 | $\leq$ 6983 | 81 | $\leq$ 24558 | 145 | $\leq$ 86368 | 209 | $\leq$ 303746 | +| 18 | $\leq$ 7121 | 82 | $\leq$ 25045 | 146 | $\leq$ 88082 | 210 | $\leq$ 309774 | +| 19 | $\leq$ 7262 | 83 | $\leq$ 25542 | 147 | $\leq$ 89830 | 211 | $\leq$ 315921 | +| 20 | $\leq$ 7407 | 84 | $\leq$ 26049 | 148 | $\leq$ 91612 | 212 | $\leq$ 322190 | +| 21 | $\leq$ 7554 | 85 | $\leq$ 26566 | 149 | $\leq$ 93430 | 213 | $\leq$ 328583 | +| 22 | $\leq$ 7703 | 86 | $\leq$ 27093 | 150 | $\leq$ 95284 | 214 | $\leq$ 335104 | +| 23 | $\leq$ 7856 | 87 | $\leq$ 27631 | 151 | $\leq$ 97175 | 215 | $\leq$ 341754 | +| 24 | $\leq$ 8012 | 88 | $\leq$ 28179 | 152 | $\leq$ 99103 | 216 | $\leq$ 348535 | +| 25 | $\leq$ 8171 | 89 | $\leq$ 28738 | 153 | $\leq$ 101070 | 217 | $\leq$ 355452 | +| 26 | $\leq$ 8333 | 90 | $\leq$ 29309 | 154 | $\leq$ 103076 | 218 | $\leq$ 362505 | +| 27 | $\leq$ 8499 | 91 | $\leq$ 29890 | 155 | $\leq$ 105121 | 219 | $\leq$ 369699 | +| 28 | $\leq$ 8667 | 92 | $\leq$ 30483 | 156 | $\leq$ 107207 | 220 | $\leq$ 377035 | +| 29 | $\leq$ 8839 | 93 | $\leq$ 31088 | 157 | $\leq$ 109335 | 221 | $\leq$ 384517 | +| 30 | $\leq$ 9015 | 94 | $\leq$ 31705 | 158 | $\leq$ 111504 | 222 | $\leq$ 392147 | +| 31 | $\leq$ 9194 | 95 | $\leq$ 32334 | 159 | $\leq$ 113717 | 223 | $\leq$ 399929 | +| 32 | $\leq$ 9376 | 96 | $\leq$ 32976 | 160 | $\leq$ 115973 | 224 | $\leq$ 407865 | +| 33 | $\leq$ 9562 | 97 | $\leq$ 33630 | 161 | $\leq$ 118275 | 225 | $\leq$ 415959 | +| 34 | $\leq$ 9752 | 98 | $\leq$ 34298 | 162 | $\leq$ 120622 | 226 | $\leq$ 424213 | +| 35 | $\leq$ 9946 | 99 | $\leq$ 34978 | 163 | $\leq$ 123016 | 227 | $\leq$ 432631 | +| 36 | $\leq$ 10143 | 100 | $\leq$ 35672 | 164 | $\leq$ 125457 | 228 | $\leq$ 441216 | +| 37 | $\leq$ 10344 | 101 | $\leq$ 36380 | 165 | $\leq$ 127946 | 229 | $\leq$ 449971 | +| 38 | $\leq$ 10549 | 102 | $\leq$ 37102 | 166 | $\leq$ 130485 | 230 | $\leq$ 458900 | +| 39 | $\leq$ 10759 | 103 | $\leq$ 37839 | 167 | $\leq$ 133074 | 231 | $\leq$ 468007 | +| 40 | $\leq$ 10972 | 104 | $\leq$ 38589 | 168 | $\leq$ 135715 | 232 | $\leq$ 477294 | +| 41 | $\leq$ 11190 | 105 | $\leq$ 39355 | 169 | $\leq$ 138408 | 233 | $\leq$ 486765 | +| 42 | $\leq$ 11412 | 106 | $\leq$ 40136 | 170 | $\leq$ 141155 | 234 | $\leq$ 496425 | +| 43 | $\leq$ 11639 | 107 | $\leq$ 40933 | 171 | $\leq$ 143956 | 235 | $\leq$ 506276 | +| 44 | $\leq$ 11870 | 108 | $\leq$ 41745 | 172 | $\leq$ 146813 | 236 | $\leq$ 516322 | +| 45 | $\leq$ 12105 | 109 | $\leq$ 42573 | 173 | $\leq$ 149726 | 237 | $\leq$ 526568 | +| 46 | $\leq$ 12345 | 110 | $\leq$ 43418 | 174 | $\leq$ 152697 | 238 | $\leq$ 537017 | +| 47 | $\leq$ 12590 | 111 | $\leq$ 44280 | 175 | $\leq$ 155727 | 239 | $\leq$ 547674 | +| 48 | $\leq$ 12840 | 112 | $\leq$ 45158 | 176 | $\leq$ 158817 | 240 | $\leq$ 558542 | +| 49 | $\leq$ 13095 | 113 | $\leq$ 46055 | 177 | $\leq$ 161969 | 241 | $\leq$ 569625 | +| 50 | $\leq$ 13355 | 114 | $\leq$ 46968 | 178 | $\leq$ 165183 | 242 | $\leq$ 580929 | +| 51 | $\leq$ 13620 | 115 | $\leq$ 47900 | 179 | $\leq$ 168461 | 243 | $\leq$ 592457 | +| 52 | $\leq$ 13890 | 116 | $\leq$ 48851 | 180 | $\leq$ 171804 | 244 | $\leq$ 604213 | +| 53 | $\leq$ 14166 | 117 | $\leq$ 49820 | 181 | $\leq$ 175213 | 245 | $\leq$ 616203 | +| 54 | $\leq$ 14447 | 118 | $\leq$ 50809 | 182 | $\leq$ 178690 | 246 | $\leq$ 628431 | +| 55 | $\leq$ 14734 | 119 | $\leq$ 51817 | 183 | $\leq$ 182236 | 247 | $\leq$ 640902 | +| 56 | $\leq$ 15026 | 120 | $\leq$ 52846 | 184 | $\leq$ 185852 | 248 | $\leq$ 653620 | +| 57 | $\leq$ 15324 | 121 | $\leq$ 53894 | 185 | $\leq$ 189540 | 249 | $\leq$ 666590 | +| 58 | $\leq$ 15628 | 122 | $\leq$ 54964 | 186 | $\leq$ 193302 | 250 | $\leq$ 679818 | +| 59 | $\leq$ 15938 | 123 | $\leq$ 56054 | 187 | $\leq$ 197137 | 251 | $\leq$ 693308 | +| 60 | $\leq$ 16255 | 124 | $\leq$ 57167 | 188 | $\leq$ 201049 | 252 | $\leq$ 707066 | +| 61 | $\leq$ 16577 | 125 | $\leq$ 58301 | 189 | $\leq$ 205039 | 253 | $\leq$ 721097 | +| 62 | $\leq$ 16906 | 126 | $\leq$ 59458 | 190 | $\leq$ 209108 | 254 | $\leq$ 735406 | +| 63 | $\leq$ 17242 | 127 | $\leq$ 60638 | 191 | $\leq$ 213257 | 255 | $\leq$ 750000 | + +### 6.1.3.2 C-RNTI MAC CE + +The C-RNTI MAC CE is identified by MAC subheader with LCID as specified in Table 6.2.1-2. + +It has a fixed size and consists of a single field defined as follows (Figure 6.1.3.2-1): + +- C-RNTI: This field contains the C-RNTI of the MAC entity. The length of the field is 16 bits. + +![Diagram of C-RNTI MAC CE structure showing two octets labeled Oct 1 and Oct 2, each containing a 16-bit C-RNTI field.](31a07dc0617b65d79a4659a346b7ed4c_img.jpg) + +| | | | | | | | | | +|--------|--|--|--|--|--|--|--|-------| +| | | | | | | | | | +| C-RNTI | | | | | | | | Oct 1 | +| C-RNTI | | | | | | | | Oct 2 | + +Diagram of C-RNTI MAC CE structure showing two octets labeled Oct 1 and Oct 2, each containing a 16-bit C-RNTI field. + +Figure 6.1.3.2-1: C-RNTI MAC CE + +### 6.1.3.3 UE Contention Resolution Identity MAC CE + +The UE Contention Resolution Identity MAC CE is identified by MAC subheader with LCID as specified in Table 6.2.1-1. + +It has a fixed 48-bit size and consists of a single field defined as follows (Figure 6.1.3.3-1): + +- UE Contention Resolution Identity: This field contains the UL CCCH SDU. If the UL CCCH SDU is longer than 48 bits, this field contains the first 48 bits of the UL CCCH SDU. + +![Diagram of UE Contention Resolution Identity MAC CE structure showing six octets labeled Oct 1 through Oct 6, each containing a 48-bit UE Contention Resolution Identity field.](43f0f64c797927f9635b55fa9eb25246_img.jpg) + +| | | | | | | | | | +|-----------------------------------|--|--|--|--|--|--|--|-------| +| | | | | | | | | | +| UE Contention Resolution Identity | | | | | | | | Oct 1 | +| UE Contention Resolution Identity | | | | | | | | Oct 2 | +| UE Contention Resolution Identity | | | | | | | | Oct 3 | +| UE Contention Resolution Identity | | | | | | | | Oct 4 | +| UE Contention Resolution Identity | | | | | | | | Oct 5 | +| UE Contention Resolution Identity | | | | | | | | Oct 6 | + +Diagram of UE Contention Resolution Identity MAC CE structure showing six octets labeled Oct 1 through Oct 6, each containing a 48-bit UE Contention Resolution Identity field. + +Figure 6.1.3.3-1: UE Contention Resolution Identity MAC CE + +### 6.1.3.4 Timing Advance Command MAC CE + +The Timing Advance Command MAC CE is identified by MAC subheader with LCID as specified in Table 6.2.1-1. + +It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.4-1): + +- TAG Identity (TAG ID): This field indicates the TAG Identity of the addressed TAG. The TAG with the Identity 0 contains the SpCell. The length of the field is 2 bits; +- Timing Advance Command: This field indicates the index value $T_A$ (0, 1, 2... 63) used to control the amount of timing adjustment that MAC entity has to apply (as specified in TS 38.213 [6]). The length of the field is 6 bits. + +![Figure 6.1.3.4-1: Timing Advance Command MAC CE diagram. It shows a single octet structure. The first 4 bits are labeled 'TAG ID' and the remaining 8 bits are labeled 'Timing Advance Command'. To the right of the octet, it is labeled 'Oct 1'.](74340c36eadb11d858e925d7b77260bf_img.jpg) + +| | | | | | | | | | | | +|--------|--|------------------------|--|--|--|--|--|--|--|-------| +| TAG ID | | Timing Advance Command | | | | | | | | Oct 1 | +|--------|--|------------------------|--|--|--|--|--|--|--|-------| + +Figure 6.1.3.4-1: Timing Advance Command MAC CE diagram. It shows a single octet structure. The first 4 bits are labeled 'TAG ID' and the remaining 8 bits are labeled 'Timing Advance Command'. To the right of the octet, it is labeled 'Oct 1'. + +**Figure 6.1.3.4-1: Timing Advance Command MAC CE** + +#### 6.1.3.4a Absolute Timing Advance Command MAC CE + +The Absolute Timing Advance Command MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. + +It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.4a-1): + +- Timing Advance Command: This field indicates the index value TA used to control the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the field is 12 bits; +- TI: If two TAGs are configured for the SpCell, this field indicates one of the two TAGs to which the Timing Advance Command is applied. If *tag2-flag* is set to *true* by upper layers, the field set to 0 indicates the *tag2-Id* and the field set to 1 indicates the *tag-Id* of the SpCell, otherwise the field set to 0 indicates the *tag-Id* and the field set to 1 indicates the *tag2-Id* of the SpCell. If the SpCell is not configured with two TAGs, the R bit is present instead; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.4a-1: Absolute Timing Advance Command MAC CE diagram. It shows two octets. Octet 1 contains three 'R' (Reserved) bits, a 'TI or R' bit, and the first 5 bits of the 'Timing Advance Command'. Octet 2 contains the remaining 7 bits of the 'Timing Advance Command'. To the right of the octets, they are labeled 'Oct 1' and 'Oct 2'.](9d9e171542e7312c3fcf0b217bca5af1_img.jpg) + +| | | | | | | | | | | | +|------------------------|---|---|---------|------------------------|--|--|--|--|-------|-------| +| R | R | R | TI or R | Timing Advance Command | | | | | Oct 1 | | +| Timing Advance Command | | | | | | | | | | Oct 2 | + +Figure 6.1.3.4a-1: Absolute Timing Advance Command MAC CE diagram. It shows two octets. Octet 1 contains three 'R' (Reserved) bits, a 'TI or R' bit, and the first 5 bits of the 'Timing Advance Command'. Octet 2 contains the remaining 7 bits of the 'Timing Advance Command'. To the right of the octets, they are labeled 'Oct 1' and 'Oct 2'. + +**Figure 6.1.3.4a-1: Absolute Timing Advance Command MAC CE** + +#### 6.1.3.5 DRX Command MAC CE + +The DRX Command MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. + +It has a fixed size of zero bits. + +#### 6.1.3.6 Long DRX Command MAC CE + +The Long DRX Command MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. + +It has a fixed size of zero bits. + +#### 6.1.3.7 Configured Grant Confirmation MAC CE + +The Configured Grant Confirmation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-2. + +It has a fixed size of zero bits. + +#### 6.1.3.8 Single Entry PHR MAC CE + +The Single Entry PHR MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-2. + +It has a fixed size and consists of two octets defined as follows (figure 6.1.3.8-1): + +- R: Reserved bit, set to 0; + +- Power Headroom (PH): This field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 below (the corresponding measured values in dB are specified in TS 38.133 [11]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding PCMAX,f,c field would have had a different value if no power backoff due to power management had been applied; +- PCMAX,f,c: This field indicates the PCMAX,f,c (as specified in TS 38.213 [6]) used for calculation of the preceding PH field. The reported PCMAX,f,c and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm are specified in TS 38.133 [11]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits or DPC is present instead; +- DPC: If *dpc-Reporting-FR1* is configured, and the Serving Cell operates on FR1, this field indicates the ΔPPowerClass, as specified in TS 38.101-1[14] and TS 38.101-3 [16]. This field indicates an index to Table 6.1.3.8-4 and the corresponding measured values of DPC levels in dB are specified in TS 38.133 [11], the DPC field is set to 0 if the criteria to report DPC is not met. The length of the field is 2 bits. If the Serving Cell operates on FR2, R bits or MPE is present instead. + +![Diagram of Single Entry PHR MAC CE structure. It shows a header row with 8 empty cells. Below it is a table with two rows. The first row has two cells: the first contains 'P' and 'R', and the second contains 'PH (Type 1, PCell)'. The second row has two cells: the first contains 'MPE or DPC or R', and the second contains 'P_CMAX,f,c'.](03b1d46bdcb71b03d29c6ab572fb9b33_img.jpg) + +| | | | | | | | | +|-----------------|---|-----------------------|--|--|--|--|--| +| | | | | | | | | +| P | R | PH (Type 1, PCell) | | | | | | +| MPE or DPC or R | | P CMAX,f,c | | | | | | + +Diagram of Single Entry PHR MAC CE structure. It shows a header row with 8 empty cells. Below it is a table with two rows. The first row has two cells: the first contains 'P' and 'R', and the second contains 'PH (Type 1, PCell)'. The second row has two cells: the first contains 'MPE or DPC or R', and the second contains 'P\_CMAX,f,c'. + +Figure 6.1.3.8-1: Single Entry PHR MAC CE + +Table 6.1.3.8-1: Power Headroom levels for PHR + +| PH | Power Headroom Level | +|-----|----------------------| +| 0 | POWER_HEADROOM_0 | +| 1 | POWER_HEADROOM_1 | +| 2 | POWER_HEADROOM_2 | +| 3 | POWER_HEADROOM_3 | +| ... | ... | +| 60 | POWER_HEADROOM_60 | +| 61 | POWER_HEADROOM_61 | +| 62 | POWER_HEADROOM_62 | +| 63 | POWER_HEADROOM_63 | + +**Table 6.1.3.8-2: Nominal UE transmit power level for PHR** + +| $P_{\text{CMAX,fc}}$ | Nominal UE transmit power level | +|----------------------|---------------------------------| +| 0 | PCMAX_C_00 | +| 1 | PCMAX_C_01 | +| 2 | PCMAX_C_02 | +| ... | ... | +| 61 | PCMAX_C_61 | +| 62 | PCMAX_C_62 | +| 63 | PCMAX_C_63 | + +**Table 6.1.3.8-3: Effective power reduction for MPE P-MPR** + +| MPE | Measured P-MPR value | +|-----|----------------------| +| 0 | P-MPR_00 | +| 1 | P-MPR_01 | +| 2 | P-MPR_02 | +| 3 | P-MPR_03 | + +**Table 6.1.3.8-4: Delta power class for DPC** + +| DPC | Measured DPC value | +|-----|--------------------| +| 0 | reserved | +| 1 | DPC_00 | +| 2 | DPC_03 | +| 3 | DPC_06 | + +### 6.1.3.9 Multiple Entry PHR MAC CE + +The Multiple Entry PHR MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-2. + +It has a variable size, and includes the bitmap, a Type 2 PH field and an octet containing the associated $P_{\text{CMAX,fc}}$ field (if reported) for SpCell of the other MAC entity, a Type 1 PH field and an octet containing the associated $P_{\text{CMAX,fc}}$ field (if reported) for the PCell. It further includes, in ascending order based on the *ServCellIndex*, one or multiple of Type X PH fields and octets containing the associated $P_{\text{CMAX,fc}}$ fields (if reported) for Serving Cells other than PCell indicated in the bitmap. X is either 1 or 3 according to TS 38.213 [6] and TS 36.213 [17]. + +The presence of Type 2 PH field for SpCell of the other MAC entity is configured by *phr-Type2OtherCell* with value *true*. + +A single octet bitmap is used for indicating the presence of PH per Serving Cell when the highest *ServCellIndex* of Serving Cell with configured uplink is less than 8, otherwise four octets are used. + +The MAC entity determines whether PH value for an activated Serving Cell is based on real transmission or a reference format by considering the configured grant(s) and downlink control information which has been received until and including the PDCCH occasion in which the first UL grant for a new transmission that can accommodate the MAC CE for PHR as a result of LCP as defined in clause 5.4.3.1 is received since a PHR has been triggered if the PHR MAC CE is reported on an uplink grant received on the PDCCH or until the first uplink symbol of PUSCH transmission minus PUSCH preparation time as defined in clause 7.7 of TS 38.213 [6] if the PHR MAC CE is reported on a configured grant. + +For a band combination in which the UE does not support dynamic power sharing, the UE may omit the octets containing Power Headroom field and $P_{\text{CMAX,fc}}$ field for Serving Cells in the other MAC entity except for the PCell in the other MAC entity and the reported values of Power Headroom and $P_{\text{CMAX,fc}}$ for the PCell are up to UE implementation. + +The PHR MAC CEs are defined as follows: + +- $C_i$ : This field indicates the presence of a PH field for the Serving Cell with *ServCellIndex* $i$ as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that a PH field for the Serving Cell with *ServCellIndex* $i$ is reported. The $C_i$ field set to 0 indicates that a PH field for the Serving Cell with *ServCellIndex* $i$ is not reported; +- R: Reserved bit, set to 0; +- DPCBC: If *dpc-Reporting-FR1* is configured, this field indicates the $\Delta P_{\text{PowerClass, CA}} / \Delta P_{\text{PowerClass, EN-DC}} / \Delta P_{\text{PowerClass, NR-DC}}$ , as specified in TS 38.101-1[14] and TS 38.101-3 [16], this field set to 0 indicates the delta power class for band combination is 0dB, this field set to 1 indicates the delta power class for band combination is same or larger than 3 dB. Otherwise, R bit is present, set to 0; +- V: This field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, the V field set to 0 indicates real transmission on PUSCH and the V field set to 1 indicates that a PUSCH reference format is used. For Type 2 PH, the V field set to 0 indicates real transmission on PUCCH and the V field set to 1 indicates that a PUCCH reference format is used. For Type 3 PH, the V field set to 0 indicates real transmission on SRS and the V field set to 1 indicates that an SRS reference format is used. Furthermore, for Type 1, Type 2, and Type 3 PH, the V field set to 0 indicates the presence of the octet containing the associated $P_{\text{CMAX,fc}}$ field and the MPE or DPC field, and the V field set to 1 indicates that the octet containing the associated $P_{\text{CMAX,fc}}$ field and the MPE or DPC field is omitted; +- Power Headroom (PH): This field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dB for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding $P_{\text{CMAX,fc}}$ field would have had a different value if no power backoff due to power management had been applied; +- $P_{\text{CMAX,fc}}$ : If present, this field indicates the $P_{\text{CMAX,fc}}$ (as specified in TS 38.213 [6]) for the NR Serving Cell and the $P_{\text{CMAX,c}}$ or $\tilde{P}_{\text{CMAX,c}}$ (as specified in TS 36.213 [17]) for the E-UTRA Serving Cell used for calculation of the preceding PH field. The reported $P_{\text{CMAX,fc}}$ and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dBm for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits or DPC is present instead. +- DPC: If *dpc-Reporting-FR1* is configured, and the Serving Cell operates on FR1, this field indicates the $\Delta P_{\text{PowerClass}}$ , as specified in TS 38.101-1[14] and TS 38.101-3 [16]. This field indicates an index to Table 6.1.3.8-4 and the corresponding measured values of DPC levels in dB are specified in TS 38.133 [11], the DPC field is set to 0 if the criteria to report DPC is not met. The length of the field is 2 bits. If the Serving Cell operates on FR2, R bits or MPE is present instead. + +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | DPC bc or R | +|-----------------|----------------|---------------------------------------------|----------------|----------------|----------------|----------------|------------------------| +| P | V | PH (Type 2, SpCell of the other MAC entity) | | | | | | +| MPE or DPC or R | | P CMAX,f,c 1 | | | | | | +| P | V | PH (Type 1, PCell) | | | | | | +| MPE or DPC or R | | P CMAX,f,c 2 | | | | | | +| P | V | PH (Type X, Serving Cell 1) | | | | | | +| MPE or DPC or R | | P CMAX,f,c 3 | | | | | | +| ... | | | | | | | | +| P | V | PH (Type X, Serving Cell n) | | | | | | +| MPE or DPC or R | | P CMAX,f,c m | | | | | | + +Figure 6.1.3.9-1: Multiple Entry PHR MAC CE with the highest *ServCellIndex* of Serving Cell with configured uplink is less than 8 + +| | | | | | | | | +|-----------------|-----------------|---------------------------------------------|-----------------|-----------------|-----------------|-----------------|------------------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | DPC BC or R | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | +| P | V | PH (Type 2, SpCell of the other MAC entity) | | | | | | +| MPE or DPC or R | | P CMAX,f,c 1 | | | | | | +| P | V | PH (Type 1, PCell) | | | | | | +| MPE or DPC or R | | P CMAX,f,c 2 | | | | | | +| P | V | PH (Type X, Serving Cell 1) | | | | | | +| MPE or DPC or R | | P CMAX,f,c 3 | | | | | | +| ... | | | | | | | | +| P | V | PH (Type X, Serving Cell n) | | | | | | +| MPE or DPC or R | | P CMAX,f,c m | | | | | | + +**Figure 6.1.3.9-2: Multiple Entry PHR MAC CE with the highest ServCellIndex of Serving Cell with configured uplink is equal to or higher than 8** + +### 6.1.3.10 SCell Activation/Deactivation MAC CEs + +The SCell Activation/Deactivation MAC CE of one octet is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The SCell Activation/Deactivation MAC CE with one octet is defined as follows (Figure 6.1.3.10-1). + +The SCell Activation/Deactivation MAC CE of four octets is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size and consists of four octets containing 31 C-fields and one R-field. The SCell Activation/Deactivation MAC CE of four octets is defined as follows (Figure 6.1.3.10-2). + +- Ci: If there is an SCell configured for the MAC entity with *SCellIndex* i as specified in TS 38.331 [5], this field indicates the activation/deactivation status of the SCell with *SCellIndex* i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 to indicate that the SCell with *SCellIndex* i shall be activated. The Ci field is set to 0 to indicate that the SCell with *SCellIndex* i shall be deactivated; +- R: Reserved bit, set to 0. + +| | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|---| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | + +Oct 1 + +**Figure 6.1.3.10-1: SCell Activation/Deactivation MAC CE of one octet** + +![Figure 6.1.3.10-2: SCell Activation/Deactivation MAC CE of four octets. The diagram shows four octets (Oct 1 to Oct 4) each containing eight fields. Oct 1 contains C7, C6, C5, C4, C3, C2, C1, and R. Oct 2 contains C15, C14, C13, C12, C11, C10, C9, and C8. Oct 3 contains C23, C22, C21, C20, C19, C18, C17, and C16. Oct 4 contains C31, C30, C29, C28, C27, C26, C25, and C24.](5f5a8699620b98137f36540ead9912f9_img.jpg) + +| | | | | | | | | | +|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-------| +| | | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | Oct 1 | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | Oct 2 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | Oct 3 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | Oct 4 | + +Figure 6.1.3.10-2: SCell Activation/Deactivation MAC CE of four octets. The diagram shows four octets (Oct 1 to Oct 4) each containing eight fields. Oct 1 contains C7, C6, C5, C4, C3, C2, C1, and R. Oct 2 contains C15, C14, C13, C12, C11, C10, C9, and C8. Oct 3 contains C23, C22, C21, C20, C19, C18, C17, and C16. Oct 4 contains C31, C30, C29, C28, C27, C26, C25, and C24. + +**Figure 6.1.3.10-2: SCell Activation/Deactivation MAC CE of four octets** + +NOTE: If UE receives the SCell Activation/Deactivation MAC CE for an SCell configured with TRS for fast activation of the SCell, such TRS is not used for the corresponding SCell. + +### 6.1.3.11 Duplication Activation/Deactivation MAC CE + +The Duplication Activation/Deactivation MAC CE of one octet is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size and consists of a single octet containing eight D-fields. The Duplication Activation/Deactivation MAC CE is defined, for a MAC entity, as follows (Figure 6.1.3.11-1). + +- Di: This field indicates the activation/deactivation status of the PDCP duplication of DRB i where i is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with RLC entity(ies) associated with this MAC entity. The Di field is set to 1 to indicate that the PDCP duplication of DRB i shall be activated. The Di field is set to 0 to indicate that the PDCP duplication of DRB i shall be deactivated. + +![Figure 6.1.3.11-1: Duplication Activation/Deactivation MAC CE. The diagram shows a single octet (Oct 1) containing eight fields: D7, D6, D5, D4, D3, D2, D1, and D0.](41fdfbcb8ced232d5050bafa1d010287_img.jpg) + +| | | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-------| +| | | | | | | | | | +| D 7 | D 6 | D 5 | D 4 | D 3 | D 2 | D 1 | D 0 | Oct 1 | + +Figure 6.1.3.11-1: Duplication Activation/Deactivation MAC CE. The diagram shows a single octet (Oct 1) containing eight fields: D7, D6, D5, D4, D3, D2, D1, and D0. + +**Figure 6.1.3.11-1: Duplication Activation/Deactivation MAC CE** + +NOTE: The Duplication Activation/Deactivation MAC CE is not used if a DRB is configured with more than two RLC entities, i.e. with *moreThanTwoRLC-DRB*. + +### 6.1.3.12 SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE + +The SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a variable size and consists of the following fields: + +- A/D: This field indicates whether to activate or deactivate indicated SP CSI-RS and CSI-IM resource set(s). The field is set to 1 to indicate activation, otherwise it indicates deactivation; +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- SP CSI-RS resource set ID: This field contains an index of *NZP-CSI-RS-ResourceSet* containing Semi Persistent NZP CSI-RS resources, as specified in TS 38.331 [5], indicating the Semi Persistent NZP CSI-RS resource set, which shall be activated or deactivated. The length of the field is 6 bits; +- IM: This field indicates the presence of the octet containing SP CSI-IM resource set ID field. If the IM field is set to 1, the octet containing SP CSI-IM resource set ID field is present. If IM field is set to 0, the octet containing SP CSI-IM resource set ID field is not present; + +- SP CSI-IM resource set ID: This field contains an index of *CSI-IM-ResourceSet* containing Semi Persistent CSI-IM resources, as specified in TS 38.331 [5], indicating the Semi Persistent CSI-IM resource set, which shall be activated or deactivated. The length of the field is 6 bits; +- TCI State IDi: This field contains *TCI-StateId*, as specified in TS 38.331 [5], of a TCI State, which is used as QCL source for the resource within the Semi Persistent NZP CSI-RS resource set indicated by SP CSI-RS resource set ID field. TCI State ID0 indicates TCI State for the first resource within the set, TCI State ID1 for the second one and so on. The length of the field is 7 bits. If the A/D field is set to 0, the octets containing TCI State ID field(s) are not present; +- R: Reserved bit, set to 0. + +![Diagram of SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE structure showing octets 1 to N+4.](9e72357b676f470a106b2011d67d4410_img.jpg) + +| | | | | | | | | +|-----|---------------------------|---------------------------|--------|--|--|--|---------| +| | | | | | | | | +| A/D | Serving Cell ID | | BWP ID | | | | Oct 1 | +| R | IM | SP CSI-RS resource set ID | | | | | Oct 2 | +| R | R | SP CSI-IM resource set ID | | | | | Oct 3 | +| R | TCI State ID 0 | | | | | | Oct 4 | +| | | | | | | | ... | +| R | TCI State ID N | | | | | | Oct N+4 | + +Diagram of SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE structure showing octets 1 to N+4. + +**Figure 6.1.3.12-1: SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE** + +### 6.1.3.13 Aperiodic CSI Trigger State Subselection MAC CE + +The Aperiodic CSI Trigger State Subselection MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a variable size consisting of following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- Ti: This field indicates the selection status of the Aperiodic Trigger States configured within *aperiodicTriggerStateList*, as specified in TS 38.331 [5]. T0 refers to the first trigger state within the list, T1 to the second one and so on. If the list does not contain entry with index i, MAC entity shall ignore the Ti field. The Ti field is set to 1 to indicate that the Aperiodic Trigger State i shall be mapped to the codepoint of the DCI *CSI request* field, as specified in TS 38.214 [7]. The codepoint to which the Aperiodic Trigger State is mapped is determined by its ordinal position among all the Aperiodic Trigger States with Ti field set to 1, i.e. the first Aperiodic Trigger State with Ti field set to 1 shall be mapped to the codepoint value 1, second Aperiodic Trigger State with Ti field set to 1 shall be mapped to the codepoint value 2 and so on. The maximum number of mapped Aperiodic Trigger States is 63; +- R: Reserved bit, set to 0. + +![Diagram of Aperiodic CSI Trigger State Subselection MAC CE structure. It shows a header with R, Serving Cell ID, and BWP ID, followed by multiple octets (Oct 1 to Oct N) containing TCI state trigger bits (T0 to T15).](c69cb6aeb2c0a91ab4ba98bddf14e55a_img.jpg) + +| | | | | | | | | | +|------------------------|------------------------|------------------------|------------------------|------------------------|------------------------|------------------------|----------------------|-------| +| | | | | | | | | | +| R | Serving Cell ID | | | | | BWP ID | | Oct 1 | +| T 7 | T 6 | T 5 | T 4 | T 3 | T 2 | T 1 | T 0 | Oct 2 | +| T 15 | T 14 | T 13 | T 12 | T 11 | T 10 | T 9 | T 8 | Oct 3 | +| ⋮ | | | | | | | | | +| T (N-2)×8+7 | T (N-2)×8+6 | T (N-2)×8+5 | T (N-2)×8+4 | T (N-2)×8+3 | T (N-2)×8+2 | T (N-2)×8+1 | T (N-2)×8 | Oct N | + +Diagram of Aperiodic CSI Trigger State Subselection MAC CE structure. It shows a header with R, Serving Cell ID, and BWP ID, followed by multiple octets (Oct 1 to Oct N) containing TCI state trigger bits (T0 to T15). + +**Figure 6.1.3.13-1: Aperiodic CSI Trigger State Subselection MAC CE** + +### 6.1.3.14 TCI States Activation/Deactivation for UE-specific PDSCH MAC CE + +The TCI States Activation/Deactivation for UE-specific PDSCH MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a variable size consisting of following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells configured in the set *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2*, respectively; +- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits. This field is ignored if this MAC CE applies to a set of Serving Cells; +- Ti: If there is a TCI state with *TCI-StateId* i as specified in TS 38.331 [5], this field indicates the activation/deactivation status of the TCI state with *TCI-StateId* i, otherwise MAC entity shall ignore the Ti field. The Ti field is set to 1 to indicate that the TCI state with *TCI-StateId* i shall be activated and mapped to the codepoint of the DCI *Transmission Configuration Indication* field, as specified in TS 38.214 [7]. The Ti field is set to 0 to indicate that the TCI state with *TCI-StateId* i shall be deactivated and is not mapped to the codepoint of the DCI *Transmission Configuration Indication* field. The codepoint to which the TCI State is mapped is determined by its ordinal position among all the TCI States with Ti field set to 1, i.e. the first TCI State with Ti field set to 1 shall be mapped to the codepoint value 0, second TCI State with Ti field set to 1 shall be mapped to the codepoint value 1 and so on. The maximum number of activated TCI states is 8. The activated TCI states can be associated with at most one PCI different from the Serving Cell PCI at a time; +- CORESET Pool ID: This field indicates that mapping between the activated TCI states and the codepoint of the DCI *Transmission Configuration Indication* set by field Ti is specific to the *ControlResourceSetId* configured with CORESET Pool ID as specified in TS 38.331 [5]. This field set to 1 indicates that this MAC CE shall be applied for the DL transmission scheduled by CORESET with the CORESET pool ID equal to 1, otherwise, this MAC CE shall be applied for the DL transmission scheduled by CORESET pool ID equal to 0. If the *coresetPoolIndex* is not configured for any CORESET, MAC entity shall ignore the CORESET Pool ID field in this MAC CE when receiving the MAC CE. If the Serving Cell in the MAC CE is configured in a cell list that contains more than one Serving Cell, the CORESET Pool ID field shall be ignored when receiving the MAC CE. + +![Figure 6.1.3.14-1: TCI States Activation/Deactivation for UE-specific PDSCH MAC CE. The diagram shows a table with 8 columns. The first column is 'CORE SET Pool ID'. The next 5 columns are grouped under 'Serving Cell ID'. The last 2 columns are 'BWP ID'. Rows are labeled Oct 1, Oct 2, Oct 3, ..., Oct N. Oct 1 contains CORE SET Pool ID, Serving Cell ID, and BWP ID. Oct 2 contains T7, T6, T5, T4, T3, T2, T1, T0. Oct 3 contains T15, T14, T13, T12, T11, T10, T9, T8. Oct N contains T(N-2)x8+7, T(N-2)x8+6, T(N-2)x8+5, T(N-2)x8+4, T(N-2)x8+3, T(N-2)x8+2, T(N-2)x8+1, T(N-2)x8.](38e71c92bab0b1f77d50284f69e399f4_img.jpg) + +| | | | | | | | | | +|------------------------|------------------------|------------------------|------------------------|------------------------|------------------------|------------------------|----------------------|-------| +| | | | | | | | | | +| CORE
SET
Pool ID | Serving Cell ID | | | | | BWP ID | | Oct 1 | +| T 7 | T 6 | T 5 | T 4 | T 3 | T 2 | T 1 | T 0 | Oct 2 | +| T 15 | T 14 | T 13 | T 12 | T 11 | T 10 | T 9 | T 8 | Oct 3 | +| ⋮ | | | | | | | | | +| T (N-2)×8+7 | T (N-2)×8+6 | T (N-2)×8+5 | T (N-2)×8+4 | T (N-2)×8+3 | T (N-2)×8+2 | T (N-2)×8+1 | T (N-2)×8 | Oct N | + +Figure 6.1.3.14-1: TCI States Activation/Deactivation for UE-specific PDSCH MAC CE. The diagram shows a table with 8 columns. The first column is 'CORE SET Pool ID'. The next 5 columns are grouped under 'Serving Cell ID'. The last 2 columns are 'BWP ID'. Rows are labeled Oct 1, Oct 2, Oct 3, ..., Oct N. Oct 1 contains CORE SET Pool ID, Serving Cell ID, and BWP ID. Oct 2 contains T7, T6, T5, T4, T3, T2, T1, T0. Oct 3 contains T15, T14, T13, T12, T11, T10, T9, T8. Oct N contains T(N-2)x8+7, T(N-2)x8+6, T(N-2)x8+5, T(N-2)x8+4, T(N-2)x8+3, T(N-2)x8+2, T(N-2)x8+1, T(N-2)x8. + +Figure 6.1.3.14-1: TCI States Activation/Deactivation for UE-specific PDSCH MAC CE + +### 6.1.3.15 TCI State Indication for UE-specific PDCCH MAC CE + +The TCI State Indication for UE-specific PDCCH MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 16 bits with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2*, respectively; +- CORESET ID: This field indicates a Control Resource Set identified with *ControlResourceSetId* as specified in TS 38.331 [5], for which the TCI State is being indicated. In case the value of the field is 0, the field refers to the Control Resource Set configured by *controlResourceSetZero* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- TCI State ID: This field indicates the TCI state identified by *TCI-StateId* as specified in TS 38.331 [5] applicable to the Control Resource Set identified by CORESET ID field. If the field of CORESET ID is set to 0, this field indicates a *TCI-StateId* for a TCI state of the first 64 TCI-states configured by *tci-StatesToAddModList* and *tci-StatesToReleaseList* in the *PDSCH-Config* in the active BWP or by *dl-OrJoint-TCI-State-ToAddModList* and *dl-OrJoint-TCI-State-ToReleaseList* in the *PDSCH-Config* in the active BWP or the reference BWP. If the field of CORESET ID is set to the other value than 0, this field indicates a *TCI-StateId* configured by *tci-StatesPDCCH-ToAddList* and *tci-StatesPDCCH-ToReleaseList* in the *controlResourceSet* identified by the indicated CORESET ID. The length of the field is 7 bits. + +![Figure 6.1.3.15-1: TCI State Indication for UE-specific PDCCH MAC CE. The diagram shows a table with 2 columns. The first column is 'Serving Cell ID'. The second column is 'CORESET ID'. Rows are labeled Oct 1, Oct 2. Oct 1 contains Serving Cell ID and CORESET ID. Oct 2 contains CORE SET ID and TCI State ID.](66a8d74a23329358359c28ab4b557a23_img.jpg) + +| | | | | | | | | | +|-----------------|--------------|--|--|------------|--|--|--|-------| +| | | | | | | | | | +| Serving Cell ID | | | | CORESET ID | | | | Oct 1 | +| CORE
SET ID | TCI State ID | | | | | | | Oct 2 | + +Figure 6.1.3.15-1: TCI State Indication for UE-specific PDCCH MAC CE. The diagram shows a table with 2 columns. The first column is 'Serving Cell ID'. The second column is 'CORESET ID'. Rows are labeled Oct 1, Oct 2. Oct 1 contains Serving Cell ID and CORESET ID. Oct 2 contains CORE SET ID and TCI State ID. + +Figure 6.1.3.15-1: TCI State Indication for UE-specific PDCCH MAC CE + +### 6.1.3.16 SP CSI reporting on PUCCH Activation/Deactivation MAC CE + +The SP CSI reporting on PUCCH Activation/Deactivation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 16 bits with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; + +- $S_i$ : This field indicates the activation/deactivation status of the Semi-Persistent CSI report configuration within *csi-ReportConfigToAddModList*, as specified in TS 38.331 [5]. $S_0$ refers to the report configuration which includes PUCCH resources for SP CSI reporting in the indicated BWP and has the lowest *CSI-ReportConfigId* within the list with type set to *semiPersistentOnPUCCH*, $S_1$ to the report configuration which includes PUCCH resources for SP CSI reporting in the indicated BWP and has the second lowest *CSI-ReportConfigId* and so on. If the number of report configurations within the list with type set to *semiPersistentOnPUCCH* in the indicated BWP is less than $i + 1$ , MAC entity shall ignore the $S_i$ field. The $S_i$ field is set to 1 to indicate that the corresponding Semi-Persistent CSI report configuration shall be activated. The $S_i$ field is set to 0 to indicate that the corresponding Semi-Persistent CSI report configuration $i$ shall be deactivated. If the Semi-Persistent CSI report configuration $i$ is configured with *csi-ReportSubConfigList*, the $S_i$ field is set to 0 to additionally indicate that all SubConfigurations within *csi-ReportSubConfigList* shall be deactivated; +- R: Reserved bit, set to 0. + +NOTE: If a Semi-Persistent CSI report configuration $i$ is configured with *csi-ReportSubConfigList*, the corresponding $S_i$ field is not set to 1. + +| | | | | | | | | | +|---|-----------------|---|---|-------|-------|-------|--------|-------| +| | | | | | | | | | +| R | Serving Cell ID | | | | | | BWP ID | Oct 1 | +| R | R | R | R | $S_3$ | $S_2$ | $S_1$ | $S_0$ | Oct 2 | + +Figure 6.1.3.16-1: SP CSI reporting on PUCCH Activation/Deactivation MAC CE + +### 6.1.3.17 SP SRS Activation/Deactivation MAC CE + +The SP SRS Activation/Deactivation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a variable size with following fields: + +- A/D: This field indicates whether to activate or deactivate indicated SP SRS resource set. The field is set to 1 to indicate activation, otherwise it indicates deactivation; +- SRS Resource Set's Cell ID: This field indicates the identity of the Serving Cell, which contains activated/deactivated SP SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the Serving Cell which contains all resources indicated by the Resource IDi fields. The length of the field is 5 bits; +- SRS Resource Set's BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains activated/deactivated SP SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the BWP which contains all resources indicated by the Resource IDi fields. The length of the field is 2 bits; +- C: This field indicates whether the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present. If this field is set to 1, the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present, otherwise they are not present; +- SUL: This field indicates whether the MAC CE applies to the NUL carrier or SUL carrier configuration. This field is set to 1 to indicate that it applies to the SUL carrier configuration, and it is set to 0 to indicate that it applies to the NUL carrier configuration; +- SP SRS Resource Set ID: This field indicates the SP SRS Resource Set ID identified by *SRS-ResourceSetId* as specified in TS 38.331 [5], which is to be activated or deactivated. The length of the field is 4 bits; +- $F_i$ : This field indicates the type of a resource used as a spatial relationship for SRS resource within SP SRS Resource Set indicated with SP SRS Resource Set ID field. $F_0$ refers to the first SRS resource within the resource set, $F_1$ to the second one and so on. The field is set to 1 to indicate NZP CSI-RS resource index is used, and it is set to 0 to indicate either SSB index or SRS resource index is used. The length of the field is 1 bit. This field is only present if MAC CE is used for activation, i.e. the A/D field is set to 1; +- Resource IDi: This field contains an identifier of the resource used for spatial relationship derivation for SRS resource $i$ . Resource ID0 refers to the first SRS resource within the resource set, Resource ID1 to the second one + +and so on. If $F_i$ is set to 0, and the first bit of this field is set to 1, the remainder of this field contains *SSB-Index* as specified in TS 38.331 [5]. If $F_i$ is set to 0, and the first bit of this field is set to 0, the remainder of this field contains *SRS-ResourceId* as specified in TS 38.331 [5]. The length of the field is 7 bits. This field is only present if MAC CE is used for activation, i.e. the A/D field is set to 1; + +- Resource Serving Cell ID $_i$ : This field indicates the identity of the Serving Cell on which the resource used for spatial relationship derivation for SRS resource $i$ is located. The length of the field is 5 bits; +- Resource BWP ID $_i$ : This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], on which the resource used for spatial relationship derivation for SRS resource $i$ is located. The length of the field is 2 bits; +- R: Reserved bit, set to 0. + +![](eeb519f37cc42888fa15ab9ea20ba7cb_img.jpg) + +| | | | | | | | | | +|-----------|-----------------------------------|---|-----|------------------------|---------------------------|--|--|-----------| +| | | | | | | | | | +| A/D | SRS Resource Set's Cell ID | | | | SRS Resource Set's BWP ID | | | Oct 1 | +| R | R | C | SUL | SP SRS Resource Set ID | | | | Oct 2 | +| $F_0$ | Resource ID $_0$ | | | | | | | Oct 3 | +| ... | | | | | | | | | +| $F_{M-1}$ | Resource ID $_{M-1}$ | | | | | | | Oct N-M | +| R | Resource Serving Cell ID $_0$ | | | | Resource BWP ID $_0$ | | | Oct N-M+1 | +| ... | | | | | | | | | +| R | Resource Serving Cell ID $_{M-1}$ | | | | Resource BWP ID $_{M-1}$ | | | Oct N | + +**Figure 6.1.3.17-1: SP SRS Activation/Deactivation MAC CE** + +### 6.1.3.18 PUCCH spatial relation Activation/Deactivation MAC CE + +The PUCCH spatial relation Activation/Deactivation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 24 bits with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- PUCCH Resource ID: This field contains an identifier of the PUCCH resource ID identified by *PUCCH-ResourceId* as specified in TS 38.331 [5]. The length of the field is 7 bits; +- $S_i$ : If, in *PUCCH-Config* in which the PUCCH Resource ID is configured, there is a PUCCH Spatial Relation Info with *PUCCH-SpatialRelationInfoId* as specified in TS 38.331 [5], configured for the uplink bandwidth part indicated by BWP ID field, $S_i$ indicates the activation status of PUCCH Spatial Relation Info with *PUCCH-SpatialRelationInfoId* equal to $i + 1$ , otherwise MAC entity shall ignore this field. The $S_i$ field is set to 1 to indicate PUCCH Spatial Relation Info with *PUCCH-SpatialRelationInfoId* equal to $i + 1$ shall be activated. The $S_i$ field is set to 0 to indicate PUCCH Spatial Relation Info with *PUCCH-SpatialRelationInfoId* equal to $i + 1$ shall be deactivated. Only a single PUCCH Spatial Relation Info can be active for a PUCCH Resource at a time; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.18-1: PUCCH spatial relation Activation/Deactivation MAC CE diagram. The diagram shows three octets. Octet 1 contains 'R' (1 bit), 'Serving Cell ID' (5 bits), and 'BWP ID' (2 bits). Octet 2 contains 'R' (1 bit) and 'PUCCH Resource ID' (7 bits). Octet 3 contains eight bits labeled S7, S6, S5, S4, S3, S2, S1, S0.](59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg) + +| | | | | | | | | | +|----------------|-------------------|----------------|----------------|----------------|----------------|----------------|----------------|-------| +| | | | | | | | | | +| R | Serving Cell ID | | | | | | BWP ID | Oct 1 | +| R | PUCCH Resource ID | | | | | | | Oct 2 | +| S 7 | S 6 | S 5 | S 4 | S 3 | S 2 | S 1 | S 0 | Oct 3 | + +Figure 6.1.3.18-1: PUCCH spatial relation Activation/Deactivation MAC CE diagram. The diagram shows three octets. Octet 1 contains 'R' (1 bit), 'Serving Cell ID' (5 bits), and 'BWP ID' (2 bits). Octet 2 contains 'R' (1 bit) and 'PUCCH Resource ID' (7 bits). Octet 3 contains eight bits labeled S7, S6, S5, S4, S3, S2, S1, S0. + +Figure 6.1.3.18-1: PUCCH spatial relation Activation/Deactivation MAC CE + +### 6.1.3.19 SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE + +The SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 16 bits with following fields: + +- A/D: This field indicates whether to activate or deactivate indicated SP ZP CSI-RS resource set. The field is set to 1 to indicate activation, otherwise it indicates deactivation; +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint value of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- SP ZP CSI-RS resource set ID: This field contains an index of *sp-ZP-CSI-RS-ResourceSetsToAddModList*, as specified in TS 38.331 [5], indicating the Semi Persistent ZP CSI-RS resource set, which shall be activated or deactivated. The length of the field is 4 bits; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.19-1: SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE diagram. The diagram shows two octets. Octet 1 contains 'A/D' (1 bit), 'Serving Cell ID' (5 bits), and 'BWP ID' (2 bits). Octet 2 contains four 'R' (Reserved) bits and 'SP ZP CSI-RS resource set ID' (4 bits).](dd2ddef02cef83a06acfc3e710b36564_img.jpg) + +| | | | | | | | | | +|-----|-----------------|---|---|------------------------------|--|--|--------|-------| +| | | | | | | | | | +| A/D | Serving Cell ID | | | | | | BWP ID | Oct 1 | +| R | R | R | R | SP ZP CSI-RS resource set ID | | | | Oct 2 | + +Figure 6.1.3.19-1: SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE diagram. The diagram shows two octets. Octet 1 contains 'A/D' (1 bit), 'Serving Cell ID' (5 bits), and 'BWP ID' (2 bits). Octet 2 contains four 'R' (Reserved) bits and 'SP ZP CSI-RS resource set ID' (4 bits). + +Figure 6.1.3.19-1: SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE + +### 6.1.3.20 Recommended bit rate MAC CE + +The Recommended bit rate MAC CE is identified by a MAC subheader with LCID as specified in Tables 6.2.1-1 and 6.2.1-2 for bit rate recommendation message from the gNB to the UE and bit rate recommendation query message from the UE to the gNB, respectively. It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.20-1): + +- LCID: This field indicates the identity of the logical channel for which the recommended bit rate or the recommended bit rate query is applicable. The length of the field is 6 bits; +- Uplink/Downlink (UL/DL): This field indicates whether the recommended bit rate or the recommended bit rate query applies to uplink or downlink. The length of the field is 1 bit. The UL/DL field set to 0 indicates downlink. The UL/DL field set to 1 indicates uplink; +- Bit Rate: This field indicates an index to Table 6.1.3.20-1. The length of the field is 6 bits. For bit rate recommendation the value indicates the recommended bit rate. For bit rate recommendation query the value indicates the desired bit rate; +- X: Bit rate multiplier. For UEs supporting recommended bit rate multiplier, when *bitRateMultiplier* is configured for the logical channel indicated by LCID field, X field set to 1 indicates the actual value of bit rate is the value + +corresponding to the index indicated by the Bit Rate field multiplied by *bitRateMultiplier* as specified in TS 38.331 [5]. + +- R: reserved bit, set to 0. + +![](45902eaeac38a0b8d0e670b205695d13_img.jpg) + +| | | | | | | +|----------|--|---|-----------|-------------|-------| +| | | | | | | +| LCID | | | UL/
DL | Bit
Rate | Oct 1 | +| Bit Rate | | X | R | R | Oct 2 | + +**Figure 6.1.3.20-1: Recommended bit rate MAC CE** + +**Table 6.1.3.20-1: Values (kbit/s) for Bit Rate field** + +| Index | NR
Recommended
Bit Rate value
[kbit/s] | Index | NR
Recommended
Bit Rate value
[kbit/s] | +|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-------|-------------------------------------------------| +| 0 | Note 1 | 32 | 700 | +| 1 | 0 | 33 | 800 | +| 2 | 9 | 34 | 900 | +| 3 | 11 | 35 | 1000 | +| 4 | 13 | 36 | 1100 | +| 5 | 17 | 37 | 1200 | +| 6 | 21 | 38 | 1300 | +| 7 | 25 | 39 | 1400 | +| 8 | 29 | 40 | 1500 | +| 9 | 32 | 41 | 1750 | +| 10 | 36 | 42 | 2000 | +| 11 | 40 | 43 | 2250 | +| 12 | 48 | 44 | 2500 | +| 13 | 56 | 45 | 2750 | +| 14 | 72 | 46 | 3000 | +| 15 | 88 | 47 | 3500 | +| 16 | 104 | 48 | 4000 | +| 17 | 120 | 49 | 4500 | +| 18 | 140 | 50 | 5000 | +| 19 | 160 | 51 | 5500 | +| 20 | 180 | 52 | 6000 | +| 21 | 200 | 53 | 6500 | +| 22 | 220 | 54 | 7000 | +| 23 | 240 | 55 | 7500 | +| 24 | 260 | 56 | 8000 | +| 25 | 280 | 57 | Reserved | +| 26 | 300 | 58 | Reserved | +| 27 | 350 | 59 | Reserved | +| 28 | 400 | 60 | Reserved | +| 29 | 450 | 61 | Reserved | +| 30 | 500 | 62 | Reserved | +| 31 | 600 | 63 | Reserved | +| Note 1: For bit rate recommendation message this index is used for indicating that no new recommendation on bit rate is given. | | | | + +### 6.1.3.21 Timing Delta MAC CE + +The Timing Delta MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. + +It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.21-1): + +- R: Reserved bit, set to 0; + +- $T_{\delta}$ : This field indicates the value (0, 1, ..., 2047) used to control the amount of timing adjustment that MAC entity indicates (as specified in TS 38.213 [6]). The length of the field is 11 bits. + +![Timing Delta MAC CE structure diagram showing two octets. Octet 1 contains five 'R' (Reserved) bits followed by the 'T_delta' field. Octet 2 contains the remaining bits of the 'T_delta' field.](9ce1c6956cda991930d500ee19416e05_img.jpg) + +| | | | | | | | | | +|--------------|---|---|---|---|--------------|--|-------|-------| +| | | | | | | | | | +| R | R | R | R | R | $T_{\delta}$ | | Oct 1 | | +| $T_{\delta}$ | | | | | | | | Oct 2 | + +Timing Delta MAC CE structure diagram showing two octets. Octet 1 contains five 'R' (Reserved) bits followed by the 'T\_delta' field. Octet 2 contains the remaining bits of the 'T\_delta' field. + +Figure 6.1.3.21-1: Timing Delta MAC CE + +### 6.1.3.22 Guard Symbols MAC CEs + +The Guard Symbols MAC CEs (i.e. Provided Guard Symbols MAC CE and Desired Guard Symbols MAC CE) for Case-1 timing mode are identified by the MAC subheader with eLCID as specified in Table 6.2.1-1b for DL-SCH and in Table 6.2.1-2b for UL-SCH. + +It has fixed size and consists of four octets defined as follows (Figure 6.1.3.22-1): + +- R: Reserved bit, set to 0; +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- Sub-carrier spacing (SCS): This field indicates the subcarrier spacing used as reference for the guard spacing. The length of this field is 2bits. The values for the SCS field are shown in Table 6.1.3.22-2; +- Number of Guard Symbols (NmbGSi): This field indicates the number of guard symbols for the switching scenarios shown in Table 5.18.19-1. The number of guard symbols can take values within the range of 0 to 4. Higher values 5 to 7 are reserved. + +![Guard Symbols MAC CE structure diagram showing four octets. Octet 1: R (1 bit), Serving Cell ID (5 bits), SCS (2 bits). Octet 2: NmbGS1 (2 bits), NmbGS2 (2 bits), NmbGS3 (2 bits). Octet 3: NmbGS3 (2 bits), NmbGS4 (2 bits), NmbGS5 (2 bits), NmbGS6 (2 bits). Octet 4: NmbGS6 (2 bits), NmbGS7 (2 bits), NmbGS8 (2 bits).](d1dcd25a3d039a7d41d6699076934c92_img.jpg) + +| | | | | | | | | +|-----------|-----------------|-----------|-----------|-----------|-----------|--|-------| +| | | | | | | | | +| R | Serving Cell ID | | | SCS | | | Oct 1 | +| $NmbGS_1$ | | $NmbGS_2$ | | $NmbGS_3$ | | | Oct 2 | +| $NmbGS_3$ | $NmbGS_4$ | | $NmbGS_5$ | | $NmbGS_6$ | | Oct 3 | +| $NmbGS_6$ | | $NmbGS_7$ | | $NmbGS_8$ | | | Oct 4 | + +Guard Symbols MAC CE structure diagram showing four octets. Octet 1: R (1 bit), Serving Cell ID (5 bits), SCS (2 bits). Octet 2: NmbGS1 (2 bits), NmbGS2 (2 bits), NmbGS3 (2 bits). Octet 3: NmbGS3 (2 bits), NmbGS4 (2 bits), NmbGS5 (2 bits), NmbGS6 (2 bits). Octet 4: NmbGS6 (2 bits), NmbGS7 (2 bits), NmbGS8 (2 bits). + +Figure 6.1.3.22-1: Guard Symbols MAC CEs + +Table 6.1.3.22-2: Subcarrier spacing for Guard Symbols MAC CEs + +| Subcarrier spacing | SCS value | +|--------------------|-----------| +| 15kHz | 00 | +| 30kHz | 01 | +| 60kHz | 10 | +| 120kHz | 11 | + +### 6.1.3.23 BFR MAC CEs + +The MAC CEs for BFR consists of either: + +- BFR MAC CE; or + +- Truncated BFR MAC CE. + +The BFR MAC CE and Truncated BFR MAC CE are identified by a MAC subheader with LCID/eLCID as specified in Table 6.2.1-2 and Table 6.2.1-2b. + +The BFR MAC CE and Truncated BFR MAC CE have a variable size. They include a bitmap and in ascending order based on the *ServCellIndex*, beam failure recovery information i.e. octets containing candidate beam availability indication (AC) for SCells indicated in the bitmap. For BFR MAC CE, a single octet bitmap is used when the highest *ServCellIndex* of this MAC entity's SCell for which beam failure is detected and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed is less than 8, otherwise four octets are used. A MAC PDU shall contain at most one BFR MAC CE. + +For Truncated BFR MAC CE, a single octet bitmap is used for the following cases, otherwise four octets are used: + +- the highest *ServCellIndex* of this MAC entity's SCell for which beam failure is detected and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed is less than 8; or +- beam failure is detected for SpCell (as specified in Clause 5.17) and the SpCell is to be indicated in a Truncated BFR MAC CE and the UL-SCH resources available for transmission cannot accommodate the Truncated BFR MAC CE with the four octets bitmap plus its subheader as a result of LCP. + +The fields in the BFR MAC CEs are defined as follows: + +- SP: This field indicates beam failure detection (as specified in clause 5.17) for the SpCell of this MAC entity. The SP field is set to 1 to indicate that beam failure is detected for SpCell only when BFR MAC CE or Truncated BFR MAC CE is to be included into a MAC PDU as part of Random Access Procedure (as specified in 5.1.3a and 5.1.4), otherwise, it is set to 0; +- $C_i$ (BFR MAC CE): This field indicates beam failure detection (as specified in clause 5.17) and the presence of an octet containing the AC field for the SCell with *ServCellIndex* $i$ as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that beam failure is detected, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed, and the octet containing the AC field is present for the SCell with *ServCellIndex* $i$ . The $C_i$ field set to 0 indicates that the beam failure is either not detected or the beam failure is detected but the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has not been completed, and the octet containing the AC field is not present for the SCell with *ServCellIndex* $i$ . The octets containing the AC field are present in ascending order based on the *ServCellIndex*; +- $C_i$ (Truncated BFR MAC CE): This field indicates beam failure detection (as specified in clause 5.17) for the SCell with *ServCellIndex* $i$ as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that beam failure is detected, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed, and the octet containing the AC field for the SCell with *ServCellIndex* $i$ may be present. The $C_i$ field set to 0 indicates that the beam failure is either not detected or the beam failure is detected but the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has not been completed, and the octet containing the AC field is not present for the SCell with *ServCellIndex* $i$ . The octets containing the AC field, if present, are included in ascending order based on the *ServCellIndex*. The number of octets containing the AC field included is maximised, while not exceeding the available grant size; + +NOTE: The number of the octets containing the AC field in the Truncated BFR MAC CE can be zero. + +- AC: This field indicates the presence of the Candidate RS ID field in this octet. If at least one of the SSBs with SS-RSRP above *rsrp-ThresholdBFR* amongst the SSBs in *candidateBeamRSSCellList* or the CSI-RSs with CSI-RSRP above *rsrp-ThresholdBFR* amongst the CSI-RSs in *candidateBeamRSSCellList* is available, the AC field is set to 1; otherwise, it is set to 0. If the AC field set to 1, the Candidate RS ID field is present. If the AC field set to 0, R bits are present instead; +- Candidate RS ID: This field is set to the index of an SSB with SS-RSRP above *rsrp-ThresholdBFR* amongst the SSBs in *candidateBeamRSSCellList* or to the index of a CSI-RS with CSI-RSRP above *rsrp-ThresholdBFR* amongst the CSI-RSs in *candidateBeamRSSCellList*. Index of an SSB or CSI-RS is the index of an entry in *candidateBeamRSSCellList* corresponding to the SSB or CSI-RS. Index 0 corresponds to the first entry in the *candidateBeamRSSCellList*, index 1 corresponds to the second entry in the list and so on. The length of this field is 6 bits. +- R: Reserved bit, set to 0. + +![](cdb980c2fe504f3132b907d4de707c7f_img.jpg) + +| | | | | | | | | +|----------------|----------------|---------------------------|----------------|----------------|----------------|----------------|----| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | SP | +| AC | R | Candidate RS ID or R bits | | | | | | + +... + +| | | | | | | | | +|----|---|---------------------------|--|--|--|--|--| +| AC | R | Candidate RS ID or R bits | | | | | | +|----|---|---------------------------|--|--|--|--|--| + +**Figure 6.1.3.23-1: BFR and Truncated BFR MAC CE with one octet Ci field** + +![](f80c936f54d96fe309ff7df916a864c7_img.jpg) + +| | | | | | | | | +|-----------------|-----------------|---------------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | SP | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | +| AC | R | Candidate RS ID or R bits | | | | | | + +... + +| | | | | | | | | +|----|---|---------------------------|--|--|--|--|--| +| AC | R | Candidate RS ID or R bits | | | | | | +|----|---|---------------------------|--|--|--|--|--| + +**Figure 6.1.3.23-2: BFR and Truncated BFR MAC CE with four octets Ci field** + +### 6.1.3.24 Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE + +The Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE is identified by a MAC PDU subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells configured in the set *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2*, respectively; +- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- Ci: This field indicates whether the octet containing TCI state IDi,2 is present. If this field is set to 1, the octet containing TCI state IDi,2 is present. If this field is set to 0, the octet containing TCI state IDi,2 is not present; +- TCI state IDi,j: This field indicates the TCI state identified by *TCI-StateId* as specified in TS 38.331 [5], where i is the index of the codepoint of the DCI *Transmission configuration indication* field as specified in TS 38.212 [9] and TCI state IDi,j denotes the jth TCI state indicated for the ith codepoint in the DCI *Transmission Configuration Indication* field. The TCI codepoint to which the TCI States are mapped is determined by its ordinal position among all the TCI codepoints with sets of TCI state IDi,j fields, i.e. the first TCI codepoint with TCI state ID0,1 and TCI state ID0,2 shall be mapped to the codepoint value 0, the second TCI codepoint with TCI state ID1,1 and TCI state ID1,2 shall be mapped to the codepoint value 1 and so on. The TCI state IDi,2 is optional + +based on the indication of the $C_i$ field. The maximum number of activated TCI codepoint is 8 and the maximum number of TCI states mapped to a TCI codepoint is 2. + +- R: Reserved bit, set to 0. + +![](4dacbe3dedea8f941e6500272dce3539_img.jpg) + +| | | | | | | | | +|-------|-----------------------|--|--------|--|--|--|---------------------| +| | | | | | | | | +| R | Serving Cell ID | | BWP ID | | | | Oct 1 | +| $C_0$ | TCI state ID $_{0,1}$ | | | | | | Oct 2 | +| R | TCI state ID $_{0,2}$ | | | | | | Oct 3
(Optional) | +| | ... | | | | | | | +| $C_N$ | TCI state ID $_{N,1}$ | | | | | | Oct M-1 | +| R | TCI state ID $_{N,2}$ | | | | | | Oct M
(Optional) | + +**Figure 6.1.3.24-1: Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE** + +### 6.1.3.25 Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE + +The Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- PUCCH Resource ID: This field contains an identifier of the PUCCH resource ID identified by *PUCCH-ResourceId* as specified in TS 38.331 [5], which is to be activated with a spatial relation indicated by Spatial Relation Info ID field in the subsequent octet. The length of the field is 7 bits. If the indicated PUCCH Resource ID is included in a PUCCH Resource Group (configured via *resourceGroupToAddModList* as specified in TS 38.331 [5]) of the indicated UL BWP, no other PUCCH Resources within the same PUCCH Resource group are indicated in the MAC CE, and this MAC CE applies to all the PUCCH Resources in the PUCCH Resource group; +- Spatial Relation Info ID: This field contains *PUCCH-SpatialRelationInfoId* – 1 where *PUCCH-SpatialRelationInfoId* is the identifier of the PUCCH Spatial Relation Info in *PUCCH-Config* in which the PUCCH Resource ID is configured, as specified in TS 38.331 [5]. The length of the field is 6 bits; +- R: Reserved bit, set to 0. + +| | | | | | | | | | | +|-----|-------------------|--------------------------|--|--|----------|----------|--|--|--| +| | | | | | | | | | | +| R | Serving Cell ID | | | | BWP ID | Oct 1 | | | | +| R | PUCCH Resource ID | | | | Oct 2 | | | | | +| R | R | Spatial Relation Info ID | | | | Oct 3 | | | | +| ... | | | | | | | | | | +| R | PUCCH Resource ID | | | | Oct 2N-2 | | | | | +| R | R | Spatial Relation Info ID | | | | Oct 2N-1 | | | | + +**Figure 6.1.3.25-1: Enhanced PUCCH spatial relation Activation/Deactivation MAC CE** + +### 6.1.3.26 Enhanced SP/AP SRS Spatial Relation Indication MAC CE + +The Enhanced SP/AP SRS Spatial Relation Indication MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields: + +- A/D: This field indicates whether to activate or deactivate indicated SP SRS resource set. The field is set to 1 to indicate activation, otherwise it indicates deactivation. If the indicated SRS resource set ID is for the AP SRS resource set, MAC entity shall ignore this field; +- SRS Resource Set's Cell ID: This field indicates the identity of the Serving Cell, which contains the indicated SP/AP SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the Serving Cell which contains all resources indicated by the Resource IDi fields. The length of the field is 5 bits; +- SRS Resource Set's BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains the indicated SP/AP SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the BWP which contains all resources indicated by the Resource IDi fields. The length of the field is 2 bits; +- C: This field indicates whether the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present. If this field is set to 1, Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present, otherwise they are not present so MAC entity shall ignore Resource Serving Cell ID field(s) and Resource BWP ID field(s); +- SUL: This field indicates whether the MAC CE applies to the NUL carrier or SUL carrier configuration. This field is set to 1 to indicate that it applies to the SUL carrier configuration, and it is set to 0 to indicate that it applies to the NUL carrier configuration; +- SRS Resource Set ID: This field indicates the SP/AP SRS Resource Set ID identified by *SRS-ResourceSetId* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- Fi: This field indicates the type of a resource used as a spatial relationship for SRS resource within SP/AP SRS Resource Set indicated with SP/AP SRS Resource Set ID field. F0 refers to the first SRS resource within the resource set, F1 to the second one and so on. The field is set to 1 to indicate NZP CSI-RS resource index is used, and it is set to 0 to indicate either SSB index or SRS resource index is used. The length of the field is 1 bit. This field is only present if MAC CE is used for activation of SP SRS resource set, i.e. the A/D field is set to 1, or for AP SRS resource set; +- Resource Serving Cell IDi: This field indicates the identity of the Serving Cell on which the resource used for spatial relationship derivation for SRS resource i is located. The length of the field is 5 bits; +- Resource BWP IDi: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], on which the resource used for spatial relationship derivation for SRS resource i is located. The length of the field is 2 bits; + +- Resource IDi: This field contains an identifier of the resource used for spatial relationship derivation for SRS resource i. Resource ID0 refers to the first SRS resource within the resource set, Resource ID1 to the second one and so on. If Fi is set to 0, the first bit of this field is always set to 0. If Fi is set to 0, and the second bit of this field is set to 1, the remainder of this field contains *SSB-Index* as specified in TS 38.331 [5]. If Fi is set to 0, and the second bit of this field is set to 0, the remainder of this field contains *SRS-ResourceId* as specified in TS 38.331 [5]. The length of the field is 8 bits. This field is only present if MAC CE is used for activation of SP SRS resource set, i.e. the A/D field is set to 1, or for AP SRS resource set; +- R: Reserved bit, set to 0. + +![](bcc5e48817a7383c980f2165bb571508_img.jpg) + +| | | | | | | | | | +|----------------------------|-----------------------------------------|---|-----|---------------------|--------------------------------|--|--|----------| +| | | | | | | | | | +| A/D | SRS Resource Set's Cell ID | | | | SRS Resource Set's BWP ID | | | Oct 1 | +| R | R | C | SUL | SRS Resource Set ID | | | | Oct 2 | +| F 0 | Resource Serving Cell ID 0 | | | | Resource BWP ID 0 | | | Oct 3 | +| Resource ID 0 | | | | | | | | Oct 4 | +| ... | | | | | | | | | +| F N-1 | Resource Serving Cell ID N-1 | | | | Resource BWP ID N-1 | | | Oct 2N+1 | +| Resource ID N-1 | | | | | | | | Oct 2N+2 | + +**Figure 6.1.3.26-1: Enhanced SP/AP SRS spatial relation Indication MAC CE** + +### 6.1.3.27 SRS Pathloss Reference RS Update MAC CE + +The SRS Pathloss Reference RS Update MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size of 24 bits: + +- Serving Cell ID: This field indicates the identity of the Serving Cell, which contains activated SRS Resource Set. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains activated SRS Resource Set. The length of the field is 2 bits; +- SRS Resource Set ID: This field indicates the SRS Resource Set ID identified by *SRS-ResourceSetId* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- Pathloss Reference RS ID: This field indicates the Pathloss Reference RS ID identified by *srs-PathlossReferenceRS-Id* as specified in TS 38.331 [5]. It updates the pathloss reference RS for an SRS-resource set indicated by SRS Resource Set ID field. The length of the field is 6 bits; +- R: Reserved bit, set to 0. + +![Diagram of SRS Pathloss Reference RS Update MAC CE structure showing three octets. Oct 1 contains R, Serving Cell ID, and BWP ID. Oct 2 contains four R bits and SRS Resource Set ID. Oct 3 contains two R bits and Pathloss Reference RS ID.](931bd52904f67b17796a38b47af51e30_img.jpg) + +| | | | | | | | | | +|---|-----------------|--------------------------|---|---------------------|--------|--|-------|-------| +| | | | | | | | | | +| R | Serving Cell ID | | | | BWP ID | | Oct 1 | | +| R | R | R | R | SRS Resource Set ID | | | Oct 2 | | +| R | R | Pathloss Reference RS ID | | | | | | Oct 3 | + +Diagram of SRS Pathloss Reference RS Update MAC CE structure showing three octets. Oct 1 contains R, Serving Cell ID, and BWP ID. Oct 2 contains four R bits and SRS Resource Set ID. Oct 3 contains two R bits and Pathloss Reference RS ID. + +Figure 6.1.3.27-1: SRS Pathloss Reference RS Update MAC CE + +### 6.1.3.28 PUSCH Pathloss Reference RS Update MAC CE + +The PUSCH Pathloss Reference RS Update MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of the following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell, which contains activated PUSCH Pathloss Reference RS. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains activated PUSCH Pathloss Reference RS. The length of the field is 2 bits; +- T: If the UE is configured with two SRS resources sets for codebook or non-codebook, as specified in TS 38.331 [5], in the indicated bandwidth part of the indicated Serving Cell, if this field is set to 0, SRI ID(s) to be updated are the ones associated with the first SRS resource set, and if is set to 1 the SRI ID(s) to be updated are the ones associated with the second SRS resource set. Otherwise, this field is a reserved bit set to 0; +- PUSCH Pathloss Reference RS ID: This field indicates the PUSCH Pathloss Reference RS ID identified by *PUSCH-PathlossReferenceRS-Id* as specified in TS 38.331 [5], which is to be updated in the SRI PUSCH power control mappings indicated by SRI ID fields indicated in the same MAC CE. The length of the field is 6 bits; +- C: This field indicates the presence of the additional SRI ID in the last octet of this MAC CE. If this field is set to 1, two SRI ID(s) are present in the last octet. Otherwise only one SRI ID (i.e. the first SRI ID) is present in the last octet; +- SRI ID: This field indicates the SRI PUSCH power control ID identified by *sri-PUSCH-PowerControlId* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- R: Reserved bit, set to 0. + +![Diagram of PUSCH Pathloss Reference RS Update MAC CE structure showing multiple octets. Oct 1 contains R, Serving Cell ID, and BWP ID. Oct 2 contains T, C, and PUSCH Pathloss Reference RS ID. Oct 3 contains SRI ID0 and SRI ID1. Subsequent octets (Oct N) contain pairs of SRI IDs (SRI ID2N-6 and SRI ID2N-5).](8450f105f39b5cb87eddb44d739cb1b2_img.jpg) + +| | | | | | | | | | +|------------------------|-----------------|--------------------------------|--|------------------------|--------|--|-------|-------| +| | | | | | | | | | +| R | Serving Cell ID | | | | BWP ID | | Oct 1 | | +| T | C | PUSCH Pathloss Reference RS ID | | | | | | Oct 2 | +| SRI ID 0 | | | | SRI ID 1 | | | | Oct 3 | +| ... | | | | | | | | | +| SRI ID 2N-6 | | | | SRI ID 2N-5 | | | | Oct N | + +Diagram of PUSCH Pathloss Reference RS Update MAC CE structure showing multiple octets. Oct 1 contains R, Serving Cell ID, and BWP ID. Oct 2 contains T, C, and PUSCH Pathloss Reference RS ID. Oct 3 contains SRI ID0 and SRI ID1. Subsequent octets (Oct N) contain pairs of SRI IDs (SRI ID2N-6 and SRI ID2N-5). + +Figure 6.1.3.28-1: PUSCH Pathloss Reference RS Update MAC CE + +### 6.1.3.29 Serving Cell Set based SRS Spatial Relation Indication MAC CE + +The Serving Cell Set based SRS Spatial Relation indication MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of the following fields: + +- SRS Resource's Cell ID: This field indicates the identity of the Serving Cell, which contains the indicated SP/AP SRS Resource. If the C field is set to 0, this field also indicates the identity of the Serving Cell which contains all resources indicated by the Resource IDi fields. The length of the field is 5 bits. The indicated Serving Cell is configured as part of a *simultaneousSpatial-UpdatedList1* or *simultaneousSpatial-UpdatedList2* as specified in TS 38.331 [5], and this MAC CE applies to all the Serving Cells configured in the set *simultaneousSpatial-UpdatedList1* or *simultaneousSpatial-UpdatedList2*, respectively; +- SRS Resource's BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains the indicated AP/SP SRS Resource. If the C field is set to 0, this field also indicates the identity of the BWP which contains all resources indicated by the Resource IDi fields. The length of the field is 2 bits; +- C: This field indicates whether the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present. If this field is set to 1, the Resource Serving Cell ID field(s) and Resource BWP ID field(s) are present, otherwise they are not present so MAC entity shall ignore Resource Serving Cell ID field(s) and Resource BWP ID field(s); +- SRS Resource IDi: This field indicates the SP/AP SRS Resource ID identified by *SRS-ResourceId* as specified in TS 38.331 [5]. The length of the field is 6 bits; +- Fi: This field indicates the type of a resource used as a spatial relationship for SRS resource indicated with SRS Resource IDi field. F0 refers to the first SRS resource which is indicated SRS Resource ID1, F1 to the second one and so on. The field is set to 1 to indicate NZP CSI-RS resource index is used, and it is set to 0 to indicate either SSB index or SRS resource index is used. The length of the field is 1 bit; +- Resource Serving Cell IDi: This field indicates the identity of the Serving Cell on which the resource used for spatial relationship derivation for SRS Resource IDi is located. The length of the field is 5 bits; +- Resource BWP IDi: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], on which the resource used for spatial relationship derivation for SRS Resource IDi is located. The length of the field is 2 bits; +- Resource IDi: This field contains an identifier of the resource used for spatial relationship derivation for SRS resource i. Resource ID0 refers to the first SRS resource which is indicated SRS Resource ID0, Resource ID1 to the second one and so on. If Fi is set to 0, the first bit of this field is always set to 0. If Fi is set to 0, and the second bit of this field is set to 1, the remainder of this field contains *SSB-Index* as specified in TS 38.331 [5]. If Fi is set to 0, and the second bit of this field is set to 0, the remainder of this field contains *SRS-ResourceId* as specified in TS 38.331 [5]. The length of the field is 8 bits. +- R: Reserved bit, set to 0. + +![Diagram of Serving Cell set based SRS Spatial Relation Indication MAC CE structure showing octets Oct 1 to Oct 3N+1 with fields R, C, F0, FN-1, SRS Resource's Cell ID, SRS Resource ID, Resource Serving Cell ID, and Resource BWP ID.](8c05782074bb11421b43f2d5d6799b62_img.jpg) + +| | | | | | | | | +|----------------------------|-----------------------------------------|--------------------------------|--------------------------------|--|--|--|----------| +| | | | | | | | | +| R | SRS Resource's Cell ID | | SRS Resource's BWP ID | | | | Oct 1 | +| R | C | SRS Resource ID 0 | | | | | Oct 2 | +| F 0 | Resource Serving Cell ID 0 | | Resource BWP ID 0 | | | | Oct 3 | +| Resource ID 0 | | | | | | | Oct 4 | +| ... | | | | | | | | +| R | R | SRS Resource ID N-1 | | | | | Oct 3N-1 | +| F N-1 | Resource Serving Cell ID N-1 | | Resource BWP ID N-1 | | | | Oct 3N | +| Resource ID N-1 | | | | | | | Oct 3N+1 | + +Diagram of Serving Cell set based SRS Spatial Relation Indication MAC CE structure showing octets Oct 1 to Oct 3N+1 with fields R, C, F0, FN-1, SRS Resource's Cell ID, SRS Resource ID, Resource Serving Cell ID, and Resource BWP ID. + +Figure 6.1.3.29-1: Serving Cell set based SRS Spatial Relation Indication MAC CE + +### 6.1.3.30 LBT failure MAC CEs + +The LBT failure MAC CE of one octet is identified by a MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of a single octet containing 8 C-fields as follows (Figure 6.1.3.30-1). + +The LBT failure MAC CE of four octets is identified by a MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of four octets containing 32 C-fields as follows (Figure 6.1.3.30-2). + +A single octet format is used when the highest *ServCellIndex* of this MAC entity's Serving Cell for which consistent LBT failure is detected is less than 8, otherwise four octets format is used. + +- Ci: If there is a Serving Cell configured for the MAC entity with *ServCellIndex* i as specified in TS 38.331 [5] and if consistent LBT failure have been triggered and not cancelled in this Serving Cell, the field is set to 1, otherwise the field is set to 0. + +![Diagram of LBT failure MAC CE of one octet showing fields C7 to C0 in a single row for Oct 1.](4c8cb1c6034c92302897fc05e9577ec3_img.jpg) + +| | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | C 0 | +| | | | | | | | Oct 1 | + +Diagram of LBT failure MAC CE of one octet showing fields C7 to C0 in a single row for Oct 1. + +Figure 6.1.3.30-1: LBT failure MAC CE of one octet + +![Diagram of LBT failure MAC CE of four octets showing fields C7 to C0 across four rows (Oct 1 to Oct 4).](ea05ea5657f5dce30565bd4b45ed1353_img.jpg) + +| | | | | | | | | +|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | C 0 | +| | | | | | | | Oct 1 | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | +| | | | | | | | Oct 2 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | +| | | | | | | | Oct 3 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | +| | | | | | | | Oct 4 | + +Diagram of LBT failure MAC CE of four octets showing fields C7 to C0 across four rows (Oct 1 to Oct 4). + +Figure 6.1.3.30-2: LBT failure MAC CE of four octets + +### 6.1.3.31 Multiple Entry Configured Grant Confirmation MAC CE + +The Multiple Entry Configured Grant Confirmation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2b. It has a fixed size and consists of a four octets containing 32 CG-fields. The Multiple Entry Configured Grant Confirmation MAC CE is defined as follows (Figure 6.1.3.31-1). + +- $CG_i$ : This field indicates whether PDCCH indicating activation or deactivation of configured uplink grant with *ConfiguredGrantConfigIndexMAC i* has been received. The $CG_i$ field is set to 1 to indicate that PDCCH indicating activation or deactivation of type 2 configured uplink grant with *ConfiguredGrantConfigIndexMAC i* has been received. The $CG_i$ field is set to 0 to indicate that PDCCH indicating activation or deactivation of type 2 configured uplink grant with *ConfiguredGrantConfigIndexMAC i* has not been received. + +![Figure 6.1.3.31-1: Multiple Entry Configured Grant Confirmation MAC CE diagram. It shows a 4x8 grid of CG fields. The first row contains CG7 to CG0, labeled Oct 1. The second row contains CG15 to CG8, labeled Oct 2. The third row contains CG23 to CG16, labeled Oct 3. The fourth row contains CG31 to CG24, labeled Oct 4. Above the grid is a header row with 8 empty cells.](f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg) + +| | | | | | | | | | +|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-------| +| | | | | | | | | | +| $CG_7$ | $CG_6$ | $CG_5$ | $CG_4$ | $CG_3$ | $CG_2$ | $CG_1$ | $CG_0$ | Oct 1 | +| $CG_{15}$ | $CG_{14}$ | $CG_{13}$ | $CG_{12}$ | $CG_{11}$ | $CG_{10}$ | $CG_9$ | $CG_8$ | Oct 2 | +| $CG_{23}$ | $CG_{22}$ | $CG_{21}$ | $CG_{20}$ | $CG_{19}$ | $CG_{18}$ | $CG_{17}$ | $CG_{16}$ | Oct 3 | +| $CG_{31}$ | $CG_{30}$ | $CG_{29}$ | $CG_{28}$ | $CG_{27}$ | $CG_{26}$ | $CG_{25}$ | $CG_{24}$ | Oct 4 | + +Figure 6.1.3.31-1: Multiple Entry Configured Grant Confirmation MAC CE diagram. It shows a 4x8 grid of CG fields. The first row contains CG7 to CG0, labeled Oct 1. The second row contains CG15 to CG8, labeled Oct 2. The third row contains CG23 to CG16, labeled Oct 3. The fourth row contains CG31 to CG24, labeled Oct 4. Above the grid is a header row with 8 empty cells. + +Figure 6.1.3.31-1: Multiple Entry Configured Grant Confirmation MAC CE + +### 6.1.3.32 Duplication RLC Activation/Deactivation MAC CE + +The Duplication RLC Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.32-1). + +- DRB ID: This field indicates the identity of DRB for which the MAC CE applies. The length of the field is 5 bits; +- $RLC_i$ : This field indicates the activation/deactivation status of PDCP duplication for the RLC entity i where i is ascending order of logical channel ID of secondary RLC entities in the order of MCG and SCG, for the DRB. For Multi-path, RLC entity i is counted in order of direct path (where i is ascending order of logical channel ID of secondary RLC entities) and indirect path. The $RLC_i$ field is set to 1 to indicate that the PDCP duplication for the RLC entity i shall be activated. The $RLC_i$ field is set to 0 to indicate that the PDCP duplication for the RLC entity i shall be deactivated. + +![Figure 6.1.3.32-1: Duplication RLC Activation/Deactivation MAC CE diagram. It shows a single row of 8 cells. The first 5 cells are grouped as 'DRB ID'. The next three cells are labeled RLC2, RLC1, and RLC0. To the right of the row is the label 'Oct 1'. Above the row is a header row with 8 empty cells.](1adadd0ae985ea08a9315197cb81a64b_img.jpg) + +| | | | | | | | | | +|--------|--|--|--|--|---------|---------|---------|-------| +| | | | | | | | | | +| DRB ID | | | | | $RLC_2$ | $RLC_1$ | $RLC_0$ | Oct 1 | + +Figure 6.1.3.32-1: Duplication RLC Activation/Deactivation MAC CE diagram. It shows a single row of 8 cells. The first 5 cells are grouped as 'DRB ID'. The next three cells are labeled RLC2, RLC1, and RLC0. To the right of the row is the label 'Oct 1'. Above the row is a header row with 8 empty cells. + +Figure 6.1.3.32-1: Duplication RLC Activation/Deactivation MAC CE + +### 6.1.3.33 Sidelink Buffer Status Report MAC CEs + +Sidelink Buffer Status Report (SL-BSR) MAC CEs consist of either: + +- SL-BSR format (variable size); or +- Truncated SL-BSR format (variable size). + +SL-BSR and Truncated SL-BSR MAC control elements consist of one Destination Index field, one LCG ID field and one corresponding Buffer Size field per reported target group. + +The SL-BSR formats are identified by MAC subheaders with LCIDs as specified in in Table 6.2.1-2. + +The fields in the SL-BSR MAC CE are defined as follows: + +- Destination Index: The Destination Index field identifies the destination. The length of this field is 5 bits. The value is set to one index corresponding to SL destination identity associated to same destination reported in *sl-TxResourceReqList*, *sl-TxResourceReqListDisc* and *sl-TxResourceReqListCommRelay*, if present. The value is indexed sequentially from 0 in the same ascending order of SL destination identity in *sl-TxResourceReqList*, *sl-TxResourceReqListDisc* and *sl-TxResourceReqListCommRelay* as specified in TS 38.331 [5]. When multiple lists are reported, the value is indexed sequentially across all the lists in the same order as presented in *SidelinkUEInformationNR* message; +- LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) whose SL buffer status is being reported. The length of the field is 3 bits; +- Buffer Size: The Buffer Size field identifies the total amount of data available according to the data volume calculation procedure in TSs 38.322 [3] and 38.323 [4] across all logical channels of a logical channel group of a destination after the MAC PDU has been built (i.e. after the logical channel prioritization procedure, which may result the value of the Buffer Size field to zero). The amount of data is indicated in number of bytes. The size of the RLC headers and MAC subheaders are not considered in the buffer size computation. The length of this field is 8 bits. The values for the Buffer Size field are shown in Table 6.1.3.1-2, respectively. For the Truncated SL-BSR format the number of Buffer Size fields included is maximised, while not exceeding the number of padding bits. + +Buffer Sizes of LCGs are included in decreasing order of the highest priority of the sidelink logical channel having data available for transmission in each of the LCGs irrespective of the value of the Destination Index field. + +NOTE: Void. + +![Diagram of SL-BSR and Truncated SL-BSR MAC control element structure. The diagram shows a sequence of octets (Oct 1 to Oct 2N) containing Destination Index, LCG ID, and Buffer Size fields for multiple logical channel groups (LCGs).](1e8845a639705010d5cda27146b8827f_img.jpg) + +| | | | | | | | | | +|--------------------------------|--|--|--|---------------------|--|--|--|----------| +| | | | | | | | | | +| Destination Index 1 | | | | LCG ID 1 | | | | Oct 1 | +| Buffer Size 1 | | | | | | | | Oct 2 | +| Destination Index 2 | | | | LCG ID 2 | | | | Oct 3 | +| Buffer Size 2 | | | | | | | | Oct 4 | +| ... | | | | | | | | | +| Destination Index N | | | | LCG ID N | | | | Oct 2N-1 | +| Buffer Size N | | | | | | | | Oct 2N | + +Diagram of SL-BSR and Truncated SL-BSR MAC control element structure. The diagram shows a sequence of octets (Oct 1 to Oct 2N) containing Destination Index, LCG ID, and Buffer Size fields for multiple logical channel groups (LCGs). + +Figure 6.1.3.33-1: SL-BSR and Truncated SL-BSR MAC control element + +### 6.1.3.34 Sidelink Configured Grant Confirmation MAC CE + +The Sidelink Configured Grant Confirmation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2b. The Sidelink Configured Grant Confirmation MAC CE is defined as follows (Figure 6.1.3.34-1): + +- $C_i$ : If there is a configured grant Type 2 with *sl-ConfigIndexCG* $i$ configured for the MAC entity as specified in TS 38.331 [5], this field indicates the confirmation to activation/deactivation of the configured grant with *sl-ConfigIndexCG* $i$ , else the MAC entity shall ignore the $C_i$ field. The $C_i$ field is set to 1 to confirm that the configured grant with *sl-ConfigIndexCG* $i$ shall be activated. The $C_i$ field is set to 0 to indicate that the configured grant with *sl-ConfigIndexCG* $i$ shall be deactivated. + +![Figure 6.1.3.34-1: Sidelink Configured Grant Confirmation MAC CE diagram. It shows a row of 8 cells labeled C8, C7, C6, C5, C4, C3, C2, C1 from left to right. Above each cell is a vertical line, and above the entire row is a horizontal line. To the right of the row is the text 'Oct 1'.](31f5b6310f831ca3ea4f18453980c070_img.jpg) + +Figure 6.1.3.34-1: Sidelink Configured Grant Confirmation MAC CE diagram. It shows a row of 8 cells labeled C8, C7, C6, C5, C4, C3, C2, C1 from left to right. Above each cell is a vertical line, and above the entire row is a horizontal line. To the right of the row is the text 'Oct 1'. + +**Figure 6.1.3.34-1: Sidelink Configured Grant Confirmation MAC CE** + +### 6.1.3.35 Sidelink CSI Reporting MAC CE + +The Sidelink CSI Reporting MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.4-1. The priority of the Sidelink CSI Reporting MAC CE is fixed to '1'. The Sidelink CSI Reporting MAC CE is defined as follows (Figure 6.1.3.35-1): + +- RI: This field indicates the derived value of the Rank Indicator for sidelink CSI reporting as specified in clause 8.5 of TS 38.214 [7]. The length of the field is 1 bit, the values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value; +- CQI: This field indicates the derived value of the Channel Quality Indicator for sidelink CSI reporting as specified in clause 8.5 of TS 38.214 [7]. The length of the field is 4 bit; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.35-1: Sidelink CSI Reporting MAC CE diagram. It shows a row of 5 cells. The first cell is labeled 'RI'. The second cell is labeled 'CQI' and is wider than the others. The third, fourth, and fifth cells are each labeled 'R'. Above each cell is a vertical line, and above the entire row is a horizontal line. To the right of the row is the text 'Oct 1'.](af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg) + +Figure 6.1.3.35-1: Sidelink CSI Reporting MAC CE diagram. It shows a row of 5 cells. The first cell is labeled 'RI'. The second cell is labeled 'CQI' and is wider than the others. The third, fourth, and fifth cells are each labeled 'R'. Above each cell is a vertical line, and above the entire row is a horizontal line. To the right of the row is the text 'Oct 1'. + +**Figure 6.1.3.35-1: Sidelink CSI Reporting MAC CE** + +### 6.1.3.36 SP Positioning SRS Activation/Deactivation MAC CE + +The SP Positioning SRS Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields: + +- A/D: This field indicates whether to activate or deactivate indicated SP Positioning SRS resource set. The field is set to 1 to indicate activation, otherwise it indicates deactivation; +- Positioning SRS Resource Set's Cell ID: This field indicates the identity of the Serving Cell, which contains activated/deactivated SP Positioning SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the Serving Cell which contains all resources indicated by the Spatial Relation for Resource IDi fields, if present. The length of the field is 5 bits; +- Positioning SRS Resource Set's BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains activated/deactivated SP Positioning SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the BWP which contains all resources indicated by the Spatial Relation for Resource IDi fields, if present. The length of the field is 2 bits; +- C: This field indicates whether the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) within the field Spatial Relation for Resource IDi are present, except for Spatial Relation Resource IDi with DL-PRS or SSB. When A/D is set to 1, if this field is set to 1, the octets containing Resource Serving Cell ID field(s) and Resource BWP ID field(s) in the field Spatial Relation for Resource IDi are present, otherwise if this field is set to 0, they are not present. When A/D is set to 0, this field is always set to 0 that they are not present; +- SUL: This field indicates whether the MAC CE applies to the NUL carrier or SUL carrier configuration. This field is set to 1 to indicate that it applies to the SUL carrier configuration, and it is set to 0 to indicate that it applies to the NUL carrier configuration; +- Positioning SRS Resource Set ID: This field indicates the SP Positioning SRS Resource Set identified by *SRS-PosResourceSetId* as specified in TS 38.331 [5], which is to be activated or deactivated. The length of the field is 4 bits; + +- Spatial Relation for Resource IDi: The field Spatial Relation for Resource IDi is only present if MAC CE is used for activation, i.e. the A/D field is set to 1. M is the total number of Positioning SRS resource(s) configured under the SP Positioning SRS resource set indicated by the field Positioning SRS Resource Set ID. There are 4 types of Spatial Relation for Resource IDi, which is indicated by the F (F0 and F1) field within. The fields within Spatial Relation for Resource IDi are shown in Figures 6.1.3.36-2 to 6.1.3.36-5 for the 4 types of Spatial Relations for Resource IDi; +- S: This field indicates whether the fields Spatial Relation for Resource IDi for the positioning SRS resource i within the positioning SRS resource set are present. If the field is set to 1, the fields Spatial Relation for Resource IDi are present; otherwise, they are absent; +- R: Reserved bit, set to 0. + +![Diagram of SP Positioning SRS Activation/Deactivation MAC CE structure. It shows a header with A/D, Positioning SRS Resource Set's Cell ID, and Positioning SRS Resource Set's BWP ID. Below the header are R, S, C, SUL, and Positioning SRS Resource Set ID fields. The main part consists of multiple 'Spatial Relation for Resource ID' blocks (ID0, ID1, ..., IDM-1), each with a length and fields determined by F and C.](4e191c69ad9a8ccefa7beb93c5e36591_img.jpg) + +| | | | | | | | | +|----------------------------------------------------------------------------------------------|----------------------------------------|---|-----|---------------------------------|---------------------------------------|--|--| +| | | | | | | | | +| A/D | Positioning SRS Resource Set's Cell ID | | | | Positioning SRS Resource Set's BWP ID | | | +| R | S | C | SUL | Positioning SRS Resource Set ID | | | | +| Spatial Relation for Resource ID 0
(Length and fields determined by F and C) | | | | | | | | +| Spatial Relation for Resource ID 1
(Length and fields determined by F and C) | | | | | | | | +| ... | | | | | | | | +| Spatial Relation for Resource ID M-1
(Length and fields determined by F and C) | | | | | | | | + +Diagram of SP Positioning SRS Activation/Deactivation MAC CE structure. It shows a header with A/D, Positioning SRS Resource Set's Cell ID, and Positioning SRS Resource Set's BWP ID. Below the header are R, S, C, SUL, and Positioning SRS Resource Set ID fields. The main part consists of multiple 'Spatial Relation for Resource ID' blocks (ID0, ID1, ..., IDM-1), each with a length and fields determined by F and C. + +Figure 6.1.3.36-1: SP Positioning SRS Activation/Deactivation MAC CE + +![Diagram of Spatial Relation for Resource IDi with NZP CSI-RS structure. It shows a header with F0, R, R, R, R, R, R. Below the header is NZP CSI-RS resource ID. The bottom part shows R, Resource Serving Cell IDi, and Resource BWP IDi.](1eab323450a82831cf78035658284a51_img.jpg) + +| | | | | | | | | +|------------------------|---------------------------------------|---|---|---|------------------------------|---|--| +| | | | | | | | | +| F 0 | R | R | R | R | R | R | | +| NZP CSI-RS resource ID | | | | | | | | +| R | Resource Serving Cell ID i | | | | Resource BWP ID i | | | + +Diagram of Spatial Relation for Resource IDi with NZP CSI-RS structure. It shows a header with F0, R, R, R, R, R, R. Below the header is NZP CSI-RS resource ID. The bottom part shows R, Resource Serving Cell IDi, and Resource BWP IDi. + +Figure 6.1.3.36-2: Spatial Relation for Resource IDi with NZP CSI-RS + +![](dd1dd483573cc9c3bc666a371f59d5d7_img.jpg) + +| | | | | | | | | +|-------|---|-----------|---|----|-----|--|--| +| | | | | | | | | +| $F_0$ | R | R | R | SI | PCI | | | +| PCI | | | | | | | | +| R | R | SSB index | | | | | | + +**Figure 6.1.3.36-3: Spatial Relation for Resource IDi with SSB** + +![](a6df95ba6d9243e76701e4db67bf02e3_img.jpg) + +| | | | | | | | | +|-------|---------------------------------------|-------------------------------|--|--|------------------------------|--|--| +| | | | | | | | | +| $F_0$ | $F_1$ | (Positioning) SRS resource ID | | | | | | +| E | Resource Serving Cell ID i | | | | Resource BWP ID i | | | + +**Figure 6.1.3.36-4: Spatial Relation for Resource IDi with SRS** + +![](b86a5928690177a50c4fe95603ed3988_img.jpg) + +| | | | | | | | | +|-----------|---|--------------------|----|------------------------|--|--|--| +| | | | | | | | | +| $F_0$ | R | R | PI | DL-PRS Resource Set ID | | | | +| R | R | DL-PRS Resource ID | | | | | | +| DL-PRS ID | | | | | | | | + +**Figure 6.1.3.36-5: Spatial Relation for Resource IDi with DL-PRS** + +The field Spatial Relation for Resource IDi consists of the following fields: + +- $F_0$ : This field indicates the type of a resource used as a spatial relation for the $i^{\text{th}}$ Positioning SRS resource within the Positioning SRS Resource Set indicated with the field Positioning SRS Resource Set ID. The field is set to 00 to indicate NZP CSI-RS resource index is used; it is set to 01 to indicate SSB index is used; it is set to 10 to indicate SRS resource index is used; it is set to 11 to indicate DL-PRS index is used. The length of the field is 2 bits; +- $F_1$ : This field indicates the type of SRS resource used as spatial relation for the $i^{\text{th}}$ Positioning SRS resource within the SP Positioning SRS Resource Set indicated with the field Positioning SRS Resource Set ID when $F_0$ is set to 10. The field is set to 0 to indicate SRS resource index *SRS-ResourceId* as defined in TS 38.331 [5] is used; the field is set to 1 to indicate Positioning SRS resource index *SRS-PosResourceId* as defined in TS 38.331 [5] is used; +- NZP CSI-RS Resource ID: This field contains an index of *NZP-CSI-RS-ResourceID*, as specified in TS 38.331 [5], indicating the NZP CSI-RS resource, which is used to derive the spatial relation for the positioning SRS. The length of the field is 8 bits; +- SSB index: This field contains an index of SSB *SSB-Index* as specified in TS 38.331 [5] and/or TS 37.355 [23]. The length of the field is 6 bits; +- PCI: This field contains physical cell identity *PhysCellId* as specified in TS 38.331 [5] and/or TS 37.355 [23]. The length of the field is 10 bits; +- SRS resource ID: When $F_1$ is set to 0, the field indicates an index for SRS resource *SRS-ResourceId* as defined in TS 38.331 [5]; When $F_1$ is set to 1, the field indicates an index for Positioning SRS resource *SRS-PosResourceId* as defined in TS 38.331 [5]. The length of the field is 5 bits representing the index from 0 to 31; + +- E: This field indicates the extension of SRS resource ID as the MSB of SRS resource ID. The total length of the extended SRS resource ID is 6 bits. If E bit is set to 1, the SRS resource ID value is 5-bit SRS resource ID field + 32; +- DL-PRS Resource Set ID: This field contains an index for DL-PRS Resource Set *nr-DL-PRS-ResourceSetId* as defined in TS 37.355 [23]. The length of the field is 3 bits; +- DL-PRS Resource ID: This field contains an index for DL-PRS resource *nr-DL-PRS-Resource-Id* as defined in TS 37.355 [23]. The length of the field is 6 bits; +- DL-PRS ID: This field contains an identity for DL-PRS resource *dl-PRS-ID* as defined in TS 37.355 [23]. The length of the field is 8 bits; +- PI: This field indicates whether the field DL-PRS resource ID is present within the Spatial Relation for Resource IDi with DL-PRS. If the field is set to 1, the octet containing the field DL-PRS resource ID is present; otherwise, the octet is omitted; +- SI: This field indicates whether the field SSB index is present within the Spatial Relation for Resource IDi with SSB. If the field is set to 1, the octet containing the field SSB index is present; otherwise, the octet is omitted; +- Resource Serving Cell IDi: This field indicates the identity of the Serving Cell on which the resource used for spatial relationship derivation for the ith Positioning SRS resource is located. The length of the field is 5 bits; +- Resource BWP IDi: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], on which the resource used for spatial relationship derivation for the ith Positioning SRS resource is located. The length of the field is 2 bits. + +### 6.1.3.37 Guard Symbols MAC CEs for Case-6 and Case-7 timing modes + +The Guard Symbols MAC CEs (i.e. Provided Guard Symbols MAC CE and Desired Guard Symbols MAC CE) for Case-6 and Case-7 timing modes are identified by the MAC subheader with eLCIDs as specified in Table 6.2.1-1b for DL-SCH and in Table 6.2.1-2b for UL-SCH. + +The MAC CEs have fixed size and consist of three octets each, defined as follows (Figure 6.1.3.37-1 and Figure 6.1.3.37-2): + +- R: Reserved bit, set to 0; +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- Sub-carrier spacing (SCS): This field indicates the subcarrier spacing used as reference for the guard spacing. The length of this field is 2 bits. The values for the SCS field are shown in Table 6.1.3.22-2; +- Number of Guard Symbols (NmbGSi): This field indicates the number of guard symbols for the switching scenarios shown in Table 5.18.19-2. + +![](552214429c77fe87e98d6ec919ad0041_img.jpg) + +| | | | | | | | | +|---------------------|-----------------|---------------------|---|---------------------|---------------------|-------|--| +| | | | | | | | | +| R | Serving Cell ID | | | | SCS | Oct 1 | | +| R | R | R | R | NmbGS 9 | NmbGS 10 | Oct 2 | | +| NmbGS 10 | | NmbGS 13 | | NmbGS 14 | | Oct 3 | | + +Figure 6.1.3.37-1: Case-6 timing Guard Symbols MAC CEs + +![Figure 6.1.3.37-2: Case-7 timing Guard Symbols MAC CEs. The diagram shows three octets (Oct 1, Oct 2, Oct 3) of a MAC CE. Oct 1 contains R, Serving Cell ID, and SCS. Oct 2 contains R, R, R, R, NmbGS11, and NmbGS12. Oct 3 contains NmbGS12, NmbGS15, and NmbGS16.](9144d599bb5bf98cd607202d768a4956_img.jpg) + +| | | | | | | | | +|---------------------|-----------------|---------------------|---|---------------------|-----|---------------------|-------| +| | | | | | | | | +| R | Serving Cell ID | | | | SCS | | Oct 1 | +| R | R | R | R | NmbGS 11 | | NmbGS 12 | Oct 2 | +| NmbGS 12 | | NmbGS 15 | | NmbGS 16 | | | Oct 3 | + +Figure 6.1.3.37-2: Case-7 timing Guard Symbols MAC CEs. The diagram shows three octets (Oct 1, Oct 2, Oct 3) of a MAC CE. Oct 1 contains R, Serving Cell ID, and SCS. Oct 2 contains R, R, R, R, NmbGS11, and NmbGS12. Oct 3 contains NmbGS12, NmbGS15, and NmbGS16. + +**Figure 6.1.3.37-2: Case-7 timing Guard Symbols MAC CEs** + +### 6.1.3.38 Case-7 Timing advance offset MAC CE + +The Case-7 Timing advance offset MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. + +The Case-7 Timing advance offset MAC CE is related to the Case-7 timing mode, has a fixed size and consists of two octets defined as follows (Figure 6.1.3.21-2): + +- R: Reserved bit, set to 0; +- $T_{offset,2}$ : This field indicates the value (-3072, -3071, ..., 1023) used to control the amount of timing adjustment that MAC entity indicates (as specified in TS 38.213 [6]). The length of the field is 12 bits. + +![Figure 6.1.3.38-1: Case-7 Timing advance offset MAC CE. The diagram shows two octets (Oct 1, Oct 2) of a MAC CE. Oct 1 contains R, R, R, R, and T_offset,2. Oct 2 contains T_offset,2.](9f8138ddf4315e46d5c5255e919adf80_img.jpg) + +| | | | | | | | | +|----------------|---|---|---|----------------|--|--|-------| +| | | | | | | | | +| R | R | R | R | $T_{offset,2}$ | | | Oct 1 | +| $T_{offset,2}$ | | | | | | | Oct 2 | + +Figure 6.1.3.38-1: Case-7 Timing advance offset MAC CE. The diagram shows two octets (Oct 1, Oct 2) of a MAC CE. Oct 1 contains R, R, R, R, and T\_offset,2. Oct 2 contains T\_offset,2. + +**Figure 6.1.3.38-1: Case-7 Timing advance offset MAC CE** + +### 6.1.3.39 Case-6 Timing Request MAC CE + +The Case-6 Timing Request MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-2b. This MAC CE is used by the IAB-MT node to inform its parent node whether Case-6 timing is required for simultaneous operation. + +It has a fixed size of zero bits. + +### 6.1.3.40 Positioning Measurement Gap Activation/Deactivation Request MAC CE + +The Positioning Measurement Gap Activation/deactivation request MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-2b. + +It has a fixed 8-bit size defined as follows (Figure 6.1.3.40-1): + +- Positioning MG ID: This field indicates the identifier for the pre-configured positioning measurement gap. The length of the field is 4 bits; +- A/D: This field indicates the activation or deactivation of the Positioning Measurement Gap. The field is set to 1 to indicate activation, otherwise it indicates deactivation. The length of the field is 1 bit; +- R: Reserved bit, set to 0. + +![Diagram of MAC CE structure for Figure 6.1.3.40-1. It shows a header row of 8 empty cells above a data row. The data row contains five cells: 'R', 'R', 'R', 'A/D', and 'Positioning MG ID'. To the right of the diagram is the text 'Oct 1'.](050e99bf626cb208bd2646b0e0b80708_img.jpg) + +Diagram of MAC CE structure for Figure 6.1.3.40-1. It shows a header row of 8 empty cells above a data row. The data row contains five cells: 'R', 'R', 'R', 'A/D', and 'Positioning MG ID'. To the right of the diagram is the text 'Oct 1'. + +**Figure 6.1.3.40-1: Positioning Measurement Gap Activation/Deactivation Request MAC CE** + +### 6.1.3.41 Positioning Measurement Gap Activation/Deactivation Command MAC CE + +The Positioning Measurement Gap Activation/Deactivation Command MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. + +It has a fixed 8-bit size defined as follows (Figure 6.1.3.41-1): + +- Positioning MG ID: This field indicates the identifier for the preconfigured positioning measurement gap. The length of the field is 4 bits; +- A/D: This field indicates the activation or deactivation of the Positioning Measurement Gap. The field is set to 1 to indicate activation, otherwise it indicates deactivation. The length of the field is 1 bit; +- R: Reserved bit, set to 0. + +![Diagram of MAC CE structure for Figure 6.1.3.41-1. It shows a header row of 8 empty cells above a data row. The data row contains five cells: 'R', 'R', 'R', 'A/D', and 'Positioning MG ID'. To the right of the diagram is the text 'Oct 1'.](022d1dc5699c55186a08a897cad90392_img.jpg) + +Diagram of MAC CE structure for Figure 6.1.3.41-1. It shows a header row of 8 empty cells above a data row. The data row contains five cells: 'R', 'R', 'R', 'A/D', and 'Positioning MG ID'. To the right of the diagram is the text 'Oct 1'. + +**Figure 6.1.3.41-1: Positioning Measurement Gap Activation/Deactivation Command MAC CE** + +### 6.1.3.42 PPW Activation/Deactivation Command MAC CE + +The PPW Activation/Deactivation Command MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. + +It has variable size defined as follows (Figure 6.1.3.42-1): + +- numEntry: This field indicates the number of entries N-1 in the MAC CE. 00 indicates that N equals to 2; 01 indicates that N equals to 3 and so on. The length of the field is 2 bits; +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- PPW ID: This field indicates the index of the PPW configured on active DL BWP of the Serving Cell identified by the above Serving Cell ID. Index 0 corresponds to the first entry within the list of the PPW configuration by the increasing order of *dl-PPW-ID* in TS 38.331 [5] in this BWP, index 1 corresponds to the second entry in the list and so on. The length of the field is 2 bits; +- A/D: This field indicates the activation or deactivation of the PPW. The field is set to 1 to indicate activation, otherwise it indicates deactivation. The length of the field is 1 bit; +- R: Reserved bit, set to 0. + +![Diagram of PPW Activation/Deactivation Command MAC CE structure. It shows a series of octets. Octet 1 contains seven 'R' (Reserved) bits and a 'numEntry' field. Octet 2 contains 'Serving Cell ID', 'PPW ID', and 'A/D' (Activation/Deactivation) bits. Ellipses indicate intermediate octets. Octet N contains 'Serving Cell ID', 'PPW ID', and 'A/D' bits.](b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg) + +| | | | | | | | | +|-----------------|---|---|---|--------|---|----------|-------| +| | | | | | | | | +| R | R | R | R | R | R | numEntry | Oct 1 | +| Serving Cell ID | | | | PPW ID | | A/D | Oct 2 | +| ... | | | | | | | | +| Serving Cell ID | | | | PPW ID | | A/D | Oct N | + +Diagram of PPW Activation/Deactivation Command MAC CE structure. It shows a series of octets. Octet 1 contains seven 'R' (Reserved) bits and a 'numEntry' field. Octet 2 contains 'Serving Cell ID', 'PPW ID', and 'A/D' (Activation/Deactivation) bits. Ellipses indicate intermediate octets. Octet N contains 'Serving Cell ID', 'PPW ID', and 'A/D' bits. + +**Figure 6.1.3.42-1: PPW Activation/Deactivation Command MAC CE** + +### 6.1.3.43 Enhanced BFR MAC CEs + +The Enhanced MAC CEs for BFR consists of either: + +- Enhanced BFR MAC CE; or +- Truncated Enhanced BFR MAC CE. + +The Enhanced BFR MAC CE and Truncated Enhanced BFR MAC CE are identified by a MAC subheader with eLCID/LCID as specified in Table 6.2.1-2 and Table 6.2.1-2b. + +The Enhanced BFR MAC CE and Truncated Enhanced BFR MAC CE have a variable size. They include an SP field, $C_i$ bitmap (single octet or four octets), $S_j$ bitmap (0 to 4 octets), beam failure recovery information i.e. octets containing candidate beam availability indication (AC) for BFD-RS set(s) of SpCell configured with two BFD-RS sets, and in ascending order based on *ServCellIndex*, beam failure recovery information i.e. octets containing candidate beam availability indication (AC) for SCells or BFD-RS set(s) of SCells configured with two BFD-RS sets indicated in the $C_i$ bitmap. For Enhanced BFR MAC CE, a single octet $C_i$ bitmap is used when the highest *ServCellIndex* of this MAC entity's SCell for which beam failure is detected for SCell or for at least one BFD-RS set of SCell and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed is less than 8, otherwise four octets $C_i$ bitmap is used. A MAC PDU shall contain at most one MAC CE for BFR. + +For Truncated Enhanced BFR MAC CE, a single octet $C_i$ bitmap is used for the following cases, otherwise four octets $C_i$ bitmap is used: + +- the highest *ServCellIndex* of this MAC entity's SCell for which beam failure is detected for SCell or for at least one BFD-RS set of SCell and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed is less than 8; or +- beam failure is detected for SpCell (as specified in Clause 5.17) not configured with two BFD-RS sets, and the SpCell is to be indicated in a Truncated Enhanced BFR MAC CE and the UL-SCH resources available for transmission cannot accommodate the Truncated Enhanced BFR MAC CE with the four octets $C_i$ bitmap plus its subheader as a result of LCP; or +- Random Access procedure is initiated for beam failure recovery of both BFD-RS sets of SpCell (as specified in Clause 5.17) configured with two BFD-RS sets and the SpCell is to be indicated in a Truncated Enhanced BFR MAC CE and the UL-SCH resources available for transmission cannot accommodate the Truncated Enhanced BFR MAC CE with the four octets $C_i$ bitmap plus its subheader as a result of LCP. + +For Enhanced BFR MAC CE and Truncated Enhanced BFR MAC CE, a single octet $S_k$ bitmap is included if the total number of Serving Cells configured with two BFD-RS sets for which SP/ $C_i$ field set to 1 is greater than 0 and less than 9; a two octets $S_k$ bitmap is included if the total number of Serving Cells configured with two BFD-RS sets for which SP/ $C_i$ field set to 1 is greater than 8 and less than 17; a three octets $S_k$ bitmap is included if the total number of Serving Cells configured with two BFD-RS sets for which SP/ $C_i$ field is set to 1 is greater than 16 and less than 25; a four octets $S_k$ bitmap is included if the total number of Serving Cells configured with two BFD-RS sets for which SP/ $C_i$ field set to 1 is greater than 24; $S_k$ bitmap is not included if the total number of Serving Cells configured with two BFD-RS sets for which SP/ $C_i$ field is set to 1 is zero. + +For Truncated Enhanced BFR MAC CE, octet(s) containing the AC field, if any, are included for SpCell first, then one octet containing the AC field is included for SCell(s) (in ascending order of the *ServCellIndex*) and then the second + +octet containing the AC field, if any, is included for SCell(s) (in ascending order of the *ServCellIndex*), while not exceeding the available grant size. The number of the octets containing the AC field in the Truncated Enhanced BFR MAC CE can be zero. + +The fields in the Enhanced BFR MAC CEs are defined as follows: + +- SP (Enhanced BFR MAC CE): This field indicates beam failure detection (as specified in clause 5.17) for the SpCell of this MAC entity and the presence of octet(s) containing the AC field if the SpCell is configured with multiple BFD-RS sets. For the SpCell configured with two BFD-RS sets, this field set to 1 indicates that beam failure is detected for at least one BFD-RS set, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed, and the octet(s) containing the AC field is present for the SpCell; otherwise, it is set to 0. The octet(s) containing the AC field for SpCell are included before those of SCell(s). For the SpCell not configured with multiple BFD-RS sets, the SP field is set to 1 to indicate that beam failure is detected for SpCell when Enhanced BFR MAC CE is to be included into a MAC PDU as part of Random Access Procedure (as specified in 5.1.3a and 5.1.4); otherwise, it is set to 0; +- SP (Truncated Enhanced BFR MAC CE): This field indicates beam failure detection (as specified in clause 5.17) for the SpCell of this MAC entity. For the SpCell configured with two BFD-RS sets, this field set to 1 indicates that beam failure is detected for at least one BFD-RS set, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed, and the octet(s) containing the AC field may be present for the SpCell; otherwise, it is set to 0. For the SpCell not configured with multiple BFD-RS sets, the SP field is set to 1 to indicate that beam failure is detected for SpCell when Truncated Enhanced BFR MAC CE is to be included into a MAC PDU as part of Random Access Procedure (as specified in 5.1.3a and 5.1.4); otherwise, it is set to 0; +- $C_i$ (Enhanced BFR MAC CE): This field indicates beam failure detection (as specified in clause 5.17) and the presence of octet(s) containing the AC field for the SCell with *ServCellIndex* $i$ as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that beam failure is detected for the SCell or at least one BFD-RS set of the SCell, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed, and the octet(s) containing the AC field is present for the SCell with *ServCellIndex* $i$ . The $C_i$ field set to 0 indicates either that the beam failure is not detected for the SCell or any BFD-RS set of the SCell, and the octet(s) containing the AC field is not present for the SCell with *ServCellIndex* $i$ ; or that the beam failure is detected for the SCell or at least one BFD-RS set of the SCell but the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has not been completed, and the octets containing the AC field is not present for the SCell with *ServCellIndex* $i$ . The octets containing the AC field are present in ascending order based on the *ServCellIndex* and are included after the octet(s) containing the AC field for SpCell, if any; +- $C_i$ (Truncated Enhanced BFR MAC CE): This field indicates beam failure detection (as specified in clause 5.17) for the SCell with *ServCellIndex* $i$ as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that beam failure is detected for the SCell or at least one BFD-RS set of the SCell, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed, and the octet(s) containing the AC field for the SCell with *ServCellIndex* $i$ may be present. The $C_i$ field set to 0 indicates either that the beam failure is not detected for the SCell or any BFD-RS set of the SCell, and the octet(s) containing the AC field is not present for the SCell with *ServCellIndex* $i$ ; or that the beam failure is detected for the SCell or at least one BFD-RS set of the SCell but the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has not been completed, and the octet(s) containing the AC field is not present for the SCell with *ServCellIndex* $i$ ; +- $S_k$ (Enhanced BFR MAC CE): This field corresponds to the $k^{\text{th}}$ Serving Cell for which SP/ $C_i$ field is set to 1 and is configured with two BFD-RS sets. The Serving Cells for which SP/ $C_i$ field is set to 1 and are configured with two BFD-RS sets, are indexed sequentially starting with SpCell and followed by SCells in ascending order of *ServCellIndex* $i$ . This field indicates whether beam failure is detected for one or both BFD-RS sets and presence of one or two octets containing the AC field of the Serving Cell. The $S_k$ field set to 1 indicates that beam failure is detected for both the BFD-RS sets, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed for both the BFD-RS sets, and the octets containing the AC field are present for both the BFD-RS sets, of the Serving Cell. The $S_k$ field set to 0 indicates that beam failure is either detected for one of the BFD-RS sets and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed or beam failure is detected for both the BFD-RS sets but the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has not been completed for both the BFD-RS sets, and the octet containing the AC field is present for only one BFD-RS set of the Serving Cell. The $S_k$ field not mapped to any Serving Cell is set to 0; + +- $S_k$ (Truncated Enhanced BFR MAC CE): This field corresponds to the $k^{\text{th}}$ Serving Cell for which SP/ $C_i$ field is set to 1 and is configured with two BFD-RS sets. The Serving Cells for which SP/ $C_i$ field is set to 1 and are configured with two BFD-RS sets, are indexed sequentially starting with SpCell and followed by SCells in ascending order of *ServCellIndex* $i$ . This field indicates whether beam failure is detected for one or both BFD-RS sets of the Serving Cell. The $S_k$ field set to 1 indicates that beam failure is detected for both the BFD-RS sets, the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed for both the BFD-RS sets, and the octet containing the AC field is present for zero, one or two BFD-RS sets of the Serving Cell. The $S_k$ field set to 0 indicates that beam failure is either detected for one of the BFD-RS sets and the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has been completed or beam failure is detected for both the BFD-RS sets but the evaluation of the candidate beams according to the requirements as specified in TS 38.133 [11] has not been completed for both the BFD-RS sets, and the octet containing the AC field is present for zero or one BFD-RS set of the Serving Cell. The $S_k$ field not mapped to any Serving Cell is set to 0; +- AC: This field indicates the presence of the Candidate RS ID field in this octet. If at least one of the SSBs with SS-RSRP above *rsrp-ThresholdBFR* amongst the SSBs in list of candidate beams (i.e. *candidateBeamRS-List-r16* for the SCell not configured with two BFD-RS sets, *candidateBeamRS-List-r16* or *candidateBeamRS-List2-r17* for Serving Cell configured with two BFD-RS sets) or the CSI-RSs with CSI-RSRP above *rsrp-ThresholdBFR* amongst the CSI-RSs in list of candidate beams is available, the AC field is set to 1; otherwise, it is set to 0. If the AC field set to 1, the Candidate RS ID field is present. If the AC field set to 0, R bits are present instead; +- ID: This field indicates the identity of the BFD-RS set. It is set to 0 if this octet corresponds to BFD-RS set one, *failureDetectionSet1-r17*. It is set to 1 if this octet corresponds to BFD-RS set two, *failureDetectionSet2-r17*. For the Serving cell not configured with two BFD-RS sets, this field is set to 0; +- Candidate RS ID: This field is set to the index of an SSB with SS-RSRP above *rsrp-ThresholdBFR* amongst the SSBs in list of candidate beams (i.e. *candidateBeamRS-List-r16* for the SCell not configured with two BFD-RS sets, *candidateBeamRS-List-r16* or *candidateBeamRS-List2-r17* for Serving Cell configured with two BFD-RS sets) or to the index of a CSI-RS with CSI-RSRP above *rsrp-ThresholdBFR* amongst the CSI-RSs in the list of candidate beams. Index of an SSB or CSI-RS is the index of an entry in the list of candidate beams corresponding to the SSB or CSI-RS. Index 0 corresponds to the first entry in the list of candidate beams, index 1 corresponds to the second entry in the list and so on. The length of this field is 6 bits; +- R: Reserved bit, set to 0. + +![](095cb128d8f8cc689f28744e6d5d798d_img.jpg) + +| | | | | | | | | +|-------|-------|---------------------------|-------|-------|-------|-------|-------| +| | | | | | | | | +| $C_7$ | $C_6$ | $C_5$ | $C_4$ | $C_3$ | $C_2$ | $C_1$ | SP | +| $S_7$ | $S_6$ | $S_5$ | $S_4$ | $S_3$ | $S_2$ | $S_1$ | $S_0$ | +| AC | ID | Candidate RS ID or R bits | | | | | | + +... + +| | | | +|----|----|---------------------------| +| AC | ID | Candidate RS ID or R bits | +|----|----|---------------------------| + +Figure 6.1.3.43-1: Enhanced BFR and Truncated Enhanced BFR MAC CE with one octet $C_i$ field + +| | | | | | | | | +|-----------------|-----------------|---------------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | SP | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | +| S 7 | S 6 | S 5 | S 4 | S 3 | S 2 | S 1 | S 0 | +| S 15 | S 14 | S 13 | S 12 | S 11 | S 10 | S 9 | S 8 | +| S 23 | S 22 | S 21 | S 20 | S 19 | S 18 | S 17 | S 16 | +| S 31 | S 30 | S 29 | S 28 | S 27 | S 26 | S 25 | S 24 | +| AC | ID | Candidate RS ID or R bits | | | | | | +| ... | | | | | | | | +| AC | ID | Candidate RS ID or R bits | | | | | | + +Figure 6.1.3.43-2: Enhanced BFR and Truncated Enhanced BFR MAC CE with four octets Ci field + +#### 6.1.3.44 Enhanced TCI States Indication for UE-specific PDCCH MAC CE + +The Enhanced TCI States Indication for UE-specific PDCCH MAC CE is identified by a MAC PDU subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size of 24 bits with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2*, respectively; +- CORESET ID: This field indicates a Control Resource Set identified with *ControlResourceSetId* as specified in TS 38.331 [5], for which the TCI State is being indicated. In case the value of the field is 0, the field refers to the Control Resource Set configured by *controlResourceSetZero* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- TCI state IDi: This field indicates the TCI state identified by *TCI-StateId* as specified in TS 38.331 [5] applicable to the Control Resource Set identified by CORESET ID field. If the field of CORESET ID is set to the other value than 0, this field indicates a *TCI-StateId* configured by *tci-StatesPDCCH-ToAddList* and *tci-StatesPDCCH-ToReleaseList* in the *controlResourceSet* identified by the indicated CORESET ID. The length of the field is 7 bits. + +NOTE 1: The Enhanced TCI State Indication for UE specific PDCCH MAC CE is not applicable to any of the configured CORESETs in a BWP if the CORESETs are configured with different *CORESETPoolIndex* values in the BWP. + +NOTE 2: The Enhanced TCI State Indication for UE specific PDCCH MAC CE is applied only if *sfnSchemePdcch* is configured. + +NOTE 3: The Enhanced TCI State Indication for UE specific PDCCH MAC CE is not applicable to the CORESET configured by *controlResourceSetZero* if the CORESET is associated with the search space configured by *pdcch-ConfigSIB1* in *MIB*, or *searchSpaceSIB1*, *searchSpaceZero*, *searchSpaceOtherSystemInformation*, or *pagingSearchSpace* in *PDCCH-ConfigCommon*. + +| | | | | | | | | +|-----------------|---------------------------|--|--|------------|--|--|-------| +| | | | | | | | | +| Serving Cell ID | | | | CORESET ID | | | | +| CORE
SET ID | TCI State ID 1 | | | | | | Oct 2 | +| R | TCI State ID 2 | | | | | | Oct 3 | + +Figure 6.1.3.44-1: Enhanced TCI States Indication for UE-specific PDCCH MAC CE + +### 6.1.3.45 PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE + +The PUCCH Spatial Relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- C: This field indicates whether single or two spatial relation info(s) is activated for the indicated PUCCH Resource ID. If this field is set to 1, octet containing the second spatial relation info for the indicated PUCCH Resource is present. If this field is set to 0, octet containing the second spatial relation info for the indicated PUCCH Resource is not present; +- PUCCH Resource ID: This field contains an identifier of the PUCCH resource ID identified by *PUCCH-ResourceId* as specified in TS 38.331 [5], which is to be activated with a spatial relations indicated by Spatial Relation Info IDi fields in the subsequent octet(s). The length of the field is 7 bits. If the indicated PUCCH Resource ID is included in a PUCCH Resource Group (configured via *resourceGroupToAddModList* as specified in TS 38.331 [5]) of the indicated UL BWP, no other PUCCH Resources within the same PUCCH Resource group are indicated in the MAC CE, and this MAC CE applies to all the PUCCH Resources in the PUCCH Resource group; +- Spatial Relation Info IDi: This field contains *PUCCH-SpatialRelationInfoId-r16* where *PUCCH-SpatialRelationInfoId* is the identifier of the PUCCH Spatial Relation Info in *PUCCH-Config* in which the PUCCH Resource ID is configured, as specified in TS 38.331 [5], where i is the index of the activated spatial relation info ID. The length of the field is 6 bits; +- R: Reserved bit, set to 0. + +| | | | | | | | | | | | | +|-----|-------------------|---------------------------------------|--|--|--------|----------|----------|--|--|--|--| +| | | | | | | | | | | | | +| R | Serving Cell ID | | | | BWP ID | Oct 1 | | | | | | +| C | PUCCH Resource ID | | | | | | Oct 2 | | | | | +| R | R | Spatial Relation Info ID 0 | | | | Oct 3 | | | | | | +| R | R | Spatial Relation Info ID 1 | | | | Oct 4 | | | | | | +| ... | | | | | | | | | | | | +| C | PUCCH Resource ID | | | | | | Oct 2N-3 | | | | | +| R | R | Spatial Relation Info ID 0 | | | | Oct 2N-2 | | | | | | +| R | R | Spatial Relation Info ID 1 | | | | Oct 2N-1 | | | | | | + +**Figure 6.1.3.45-1: PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE** + +#### 6.1.3.46 PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC CE + +The PUCCH Power Control Set Update for multiple TRP PUCCH repetition MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- C: This field indicates whether single or two power control set(s) is activated for the indicated PUCCH Resource ID. If this field is set to 1, the second power control set index (i.e. Power Control Set ID1) for the indicated PUCCH Resource is present. If this field is set to 0, the second power control set index (i.e. Power Control Set ID1) for the indicated PUCCH Resource is not present; +- PUCCH Resource ID: This field contains an identifier of the PUCCH resource ID identified by *PUCCH-ResourceId* as specified in TS 38.331 [5], which is to be activated with a power control set(s) indicated by Power Control Set IDi fields in the subsequent octet. The length of the field is 7 bits. If the indicated PUCCH Resource ID is included in a PUCCH Resource Group (configured via *resourceGroupToAddModList* as specified in TS 38.331 [5]) of the indicated UL BWP, no other PUCCH Resources within the same PUCCH Resource group are indicated in the MAC CE, and this MAC CE applies to all the PUCCH Resources in the PUCCH Resource group; +- Power Control Set IDi: This field contains *PUCCH-PowerControlSetInfoId* where *PUCCH-PowerControlSetInfoId* is the identifier of the PUCCH Power Control Set in *PUCCH-Config* in which the PUCCH Resource ID is configured, as specified in TS 38.331 [5], where i is the index of the power control set ID. The length of the field is 3 bits; +- R: Reserved bit, set to 0. + +| | | | | | | | | | | | | +|-----|-------------------|-----------------------------------------|--|-----------------------------------------|--------|----------|----------|--|--|--|--| +| | | | | | | | | | | | | +| R | Serving Cell ID | | | | BWP ID | Oct 1 | | | | | | +| C | PUCCH Resource ID | | | | | | Oct 2 | | | | | +| R | R | PUCCH Power Control Set ID 0 | | PUCCH Power Control Set ID 1 | | Oct 3 | | | | | | +| ... | | | | | | | | | | | | +| C | PUCCH Resource ID | | | | | | Oct 2N-2 | | | | | +| R | R | PUCCH Power Control Set ID 0 | | PUCCH Power Control Set ID 1 | | Oct 2N-1 | | | | | | + +**Figure 6.1.3.46-1: PUCCH power control set update for multiple TRP PUCCH repetition MAC CE** + +### 6.1.3.47 Unified TCI States Activation/Deactivation MAC CE + +The Unified TCI States Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of following fields: + +- CORESET Pool ID: This field indicates that the mapping between the activated TCI states and the codepoint of the DCI *Transmission Configuration Indication* set by field TCI state ID is specific to the *ControlResourceSetId* configured with CORESET Pool ID as specified in TS 38.331 [5]. This field set to 1 indicates that the TCI states are specified to CORESET pool ID equal to 1, otherwise the TCI states are specified to CORESET pool ID equal to 0. If the *coresetPoolIndex* is not configured for any CORESET or only one *coresetPoolIndex* is configured for any CORESET, the R bit is present instead; +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4*, respectively; +- DL BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- UL BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. If value of *unifiedTCI-StateType* in the Serving Cell indicated by Serving Cell ID is *joint*, this field is considered as the reserved bits. The length of the BWP ID field is 2 bits; +- Pi: This field indicates whether each TCI codepoint has multiple TCI states or single TCI state. If Pi field is set to 1, it indicates that ith TCI codepoint includes the DL TCI state and the UL TCI state. If Pi field is set to 0, it indicates that ith TCI codepoint includes only the DL/joint TCI state or the UL TCI state. The codepoint to which a TCI state is mapped is determined by its ordinal position among all the TCI state ID fields; +- D/U: This field indicate whether the TCI state ID in the same octet is for joint/downlink or uplink TCI state. If this field is set to 1, the TCI state ID in the same octet is for joint/downlink. If this field is set to 0, the TCI state ID in the same octet is for uplink; +- TCI state ID: This field indicates the TCI state identified by *TCI-StateId* as specified in TS 38.331 [5]. If D/U is set to 1, 7-bits length TCI state ID i.e. *TCI-StateId* as specified in TS 38.331 [5] is used. If D/U is set to 0, the most significant bit of TCI state ID is considered as the reserved bit and remainder 6 bits indicate the *TCI-UL-State-Id* as specified in TS 38.331 [5]. The maximum number of activated TCI states is 16; +- R: Reserved bit, set to 0. + +![Diagram of Unified TCI state activation/deactivation MAC CE structure. The diagram shows a series of octets (Oct 1 to Oct N+3). Oct 1 contains CORE SET Pool ID, Serving Cell ID, and DL BWP ID. Oct 2 contains six R (Reserved) bits and UL BWP ID. Oct 3 contains eight power levels P1 through P8. Oct 4 contains D/U and TCI state ID 1. Oct 5 contains D/U and TCI state ID 2. An ellipsis indicates intermediate octets. Oct N+3 contains D/U and TCI state ID N.](7c5564b9e8a382de9dfa5f44116cbf2b_img.jpg) + +| | | | | | | | | | +|------------------|-----------------|----------------|----------------|----------------|----------------|----------------|----------------|---------| +| | | | | | | | | | +| CORE SET Pool ID | Serving Cell ID | | | | | DL BWP ID | | Oct 1 | +| R | R | R | R | R | R | UL BWP ID | | Oct 2 | +| P 1 | P 2 | P 3 | P 4 | P 5 | P 6 | P 7 | P 8 | Oct 3 | +| D/U | TCI state ID 1 | | | | | | | Oct 4 | +| D/U | TCI state ID 2 | | | | | | | Oct 5 | +| ... | | | | | | | | | +| D/U | TCI state ID N | | | | | | | Oct N+3 | + +Diagram of Unified TCI state activation/deactivation MAC CE structure. The diagram shows a series of octets (Oct 1 to Oct N+3). Oct 1 contains CORE SET Pool ID, Serving Cell ID, and DL BWP ID. Oct 2 contains six R (Reserved) bits and UL BWP ID. Oct 3 contains eight power levels P1 through P8. Oct 4 contains D/U and TCI state ID 1. Oct 5 contains D/U and TCI state ID 2. An ellipsis indicates intermediate octets. Oct N+3 contains D/U and TCI state ID N. + +**Figure 6.1.3.47-1: Unified TCI state activation/deactivation MAC CE** + +### 6.1.3.48 Enhanced Single Entry PHR MAC CE + +The Enhanced Single Entry PHR MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2b. It has a variable size with following fields: + +- R: Reserved bit, set to 0; +- Power Headroom (PH): This field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 below (the corresponding measured values in dB are specified in TS 38.133 [11]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding PCMAX,fc field would have had a different value if no power backoff due to power management had been applied; +- PCMAX,fc: This field indicates the PCMAX,fc (as specified in TS 38.213 [6]) used for calculation of the preceding PH field. The reported PCMAX,fc and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm are specified in TS 38.133 [11]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits are present instead; +- B1: This field indicates whether the candidate beam information identified by Resource1 is present or not. If the B1 field is set to 1, the first octet containing Resource1 is present and if the B2 field is set to 1, the second octet containing Resource2 is present, and so on; +- Pi: If *mpe-Reporting-FR2-r17* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise; +- MPEi: If *mpe-Reporting-FR2-r17* is configured, and the Serving Cell operates on FR2, and if the corresponding Pi field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR + +levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2-r17* is not configured, or if the Serving Cell operates on FR1, or if the $P_i$ field is set to 0, R bits are present instead; + +- Resourcei: This field indicates the candidate beam identified by the number of entries in the corresponding *mpe-ResourcePoolToAddModList* as specified in TS 38.331 [5]. The length of this field 6 bits; +- R: Reserved bit, set to 0. + +| | | | | | | | | | | | | | +|-----------------------|----------------|-----------------------|----------------|-----------------------|----------------|-----------------------|----------------|---------------------|--|--|--|--| +| | | | | | | | | | | | | | +| P | R | PH (Type 1, PCell) | | | | | | Oct 1 | | | | | +| MPE or R | | $P_{\text{CMAX},f,c}$ | | | | | | Oct 2 | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | Oct 3 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | Oct 4 | | | | | +| R | R | Resource 1 | | | | | | Oct 5 | | | | | +| R | R | Resource 2 | | | | | | Oct 6
(Optional) | | | | | +| R | R | Resource 3 | | | | | | Oct 7
(Optional) | | | | | +| R | R | Resource 4 | | | | | | Oct 8
(Optional) | | | | | + +**Figure 6.1.3.48-1: Enhanced Single Entry PHR MAC CE** + +### 6.1.3.49 Enhanced Multiple Entry PHR MAC CE + +The Enhanced Multiple Entry PHR MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2b. It has a variable size with following fields: + +- Ci: This field indicates the presence of PH field(s) for the Serving Cell with *ServCellIndex* i as specified in TS 38.331 [5]. The Ci field set to 1 indicates that PH field(s) for the Serving Cell with *ServCellIndex* i is reported. The Ci field set to 0 indicates that a PH field for the Serving Cell with *ServCellIndex* i is not reported; +- R: Reserved bit, set to 0; +- V: This field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, the V field set to 0 indicates real transmission on PUSCH and the V field set to 1 indicates that a PUSCH reference format is used. For Type 2 PH, the V field set to 0 indicates real transmission on PUCCH and the V field set to 1 indicates that a PUCCH reference format is used. For Type 3 PH, the V field set to 0 indicates real transmission on SRS and the V field set to 1 indicates that an SRS reference format is used. Furthermore, for Type 1, Type 2, and Type 3 PH, the V field set to 0 indicates the presence of the octet containing the associated $P_{\text{CMAX},f,c}$ field and the MPE field, and the V field set to 1 indicates that the octet containing the associated $P_{\text{CMAX},f,c}$ field and the MPE field is omitted; +- Power Headroom (PH): This field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dB for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC + +entity shall set the P field to 1 if the corresponding $P_{\text{CMAX,fc}}$ field would have had a different value if no power backoff due to power management had been applied; + +- $P_{\text{CMAX,fc}}$ : If present, this field indicates the $P_{\text{CMAX,fc}}$ (as specified in TS 38.213 [6]) for the NR Serving Cell and the $P_{\text{CMAX,c}}$ or $\tilde{P}_{\text{CMAX,c}}$ (as specified in TS 36.213 [17]) for the E-UTRA Serving Cell used for calculation of the preceding PH field. The reported $P_{\text{CMAX,fc}}$ and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dBm for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits are present instead; +- Bi: This field indicates whether the candidate beam information identified by either Resourcei is present or not. If the B1 field is set to 1, the first octet containing Resource1 is present and if the B2 field is set to 1, the second octet containing Resource2 is present, and so on. +- Pi: If *mpe-Reporting-FR2-r17* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise; +- MPEi: If *mpe-Reporting-FR2-r17* is configured, and the Serving Cell operates on FR2, and if the corresponding Pi field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2-r17* is not configured, or if the Serving Cell operates on FR1, or if the Pi field is set to 0, R bits are present instead; +- Resourcei: This field indicates the candidate beam identified by by the number of entries in the corresponding *mpe-ResourcePoolToAddModList* as specified in TS 38.331 [5]. The length of this field 6 bits. +- R: Reserved bit, set to 0. + +| | | | | | | | | | | | | +|-----------------------|----------------|---------------------------------------------|----------------|-----------------------|----------------|-----------------------|----------------|--|--|--|--| +| | | | | | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | | | | | +| P | V | PH (Type 2, SpCell of the other MAC entity) | | | | | | | | | | +| MPE or R | | P CMAX,f,c 1 | | | | | | | | | | +| P | V | PH (Type 1, PCell) | | | | | | | | | | +| MPE or R | | P CMAX,f,c 2 | | | | | | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | | | | | +| R | R | Resource 1 | | | | | | | | | | +| R | R | Resource 2 | | | | | | | | | | +| R | R | Resource 3 | | | | | | | | | | +| R | R | Resource 4 | | | | | | | | | | +| P | V | PH (Type X, Serving Cell 1) | | | | | | | | | | +| MPE or R | | P CMAX,f,c 3 | | | | | | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | | | | | +| R | R | Resource 1 | | | | | | | | | | +| R | R | Resource 2 | | | | | | | | | | +| R | R | Resource 3 | | | | | | | | | | +| R | R | Resource 4 | | | | | | | | | | + +... + +| | | | | | | | | | | | | +|-----------------------|----------------|-----------------------------|----------------|-----------------------|----------------|-----------------------|----------------|--|--|--|--| +| P | V | PH (Type X, Serving Cell n) | | | | | | | | | | +| MPE or R | | P CMAX,f,c m | | | | | | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | | | | | +| R | R | Resource 1 | | | | | | | | | | +| R | R | Resource 2 | | | | | | | | | | +| R | R | Resource 3 | | | | | | | | | | +| R | R | Resource 4 | | | | | | | | | | + +**Figure 6.1.3.49-1: Enhanced Multiple Entry PHR MAC CE with the highest ServCellIndex of Serving Cell with configured uplink is less than 8** + +| | | | | | | | | | | | | +|-----------------------|-----------------|---------------------------------------------|-----------------|-----------------------|-----------------|-----------------------|-----------------|--|--|--|--| +| | | | | | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | | | | | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | | | | | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | | | | | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | | | | | +| P | V | PH (Type 2, SpCell of the other MAC entity) | | | | | | | | | | +| MPE or R | | P CMAX,f,c 1 | | | | | | | | | | +| P | V | PH (Type 1, PCell) | | | | | | | | | | +| MPE or R | | P CMAX,f,c 2 | | | | | | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | | | | | +| R | R | Resource 1 | | | | | | | | | | +| R | R | Resource 2 | | | | | | | | | | +| R | R | Resource 3 | | | | | | | | | | +| R | R | Resource 4 | | | | | | | | | | +| P | V | PH (Type X, Serving Cell 1) | | | | | | | | | | +| MPE or R | | P CMAX,f,c 3 | | | | | | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | | | | | +| R | R | Resource 1 | | | | | | | | | | +| R | R | Resource 2 | | | | | | | | | | +| R | R | Resource 3 | | | | | | | | | | +| R | R | Resource 4 | | | | | | | | | | + +... + +| | | | | | | | | | | | | +|-----------------------|----------------|-----------------------------|----------------|-----------------------|----------------|-----------------------|----------------|--|--|--|--| +| P | V | PH (Type X, Serving Cell n) | | | | | | | | | | +| MPE or R | | P CMAX,f,c m | | | | | | | | | | +| B 1 | B 2 | B 3 | B 4 | P 1 | P 2 | P 3 | P 4 | | | | | +| MPE 1 or R | | MPE 2 or R | | MPE 3 or R | | MPE 4 or R | | | | | | +| R | R | Resource 1 | | | | | | | | | | +| R | R | Resource 2 | | | | | | | | | | +| R | R | Resource 3 | | | | | | | | | | +| R | R | Resource 4 | | | | | | | | | | + +**Figure 6.1.3.49-2: Enhanced Multiple Entry PHR MAC CE with the highest ServCellIndex of Serving Cell with configured uplink is equal to or higher than 8** + +### 6.1.3.50 Enhanced Single Entry PHR for multiple TRP MAC CE + +The Enhanced Single Entry PHR for multiple TRP MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2b. + +The two PHs together with one $P_{CMAX,fc}$ for the Serving Cell are reported if UE is configured with *twoPHRMode* with the multiple TRP PUSCH repetition feature is configured. + +It has a fixed size and consists of three octets defined as follows (Figure 6.1.3.50-1): + +- R: Reserved bit, set to 0; +- Power Headroom i (PH i): This field indicates the power headroom level, where PH 1 is associated with the *SRS-ResourceSet* with a lower *srs-ResourceSetId* and PH 2 is associated with the *SRS-ResourceSet* with a higher *srs-ResourceSetId*. PH fields for a Serving Cell are included in ascending order based on i. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB are specified in TS 38.133 [11]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding $P_{CMAX,fc}$ field would have had a different value if no power backoff due to power management had been applied; +- V: This field indicates if the PH value for the corresponding TRP is based on a real transmission or a reference format. For Type 1 PH, the V field set to 0 indicates real transmission on PUSCH and the V field set to 1 indicates that a PUSCH reference format is used; +- $P_{CMAX,fc}$ : This field indicates the $P_{CMAX,fc}$ (as specified in TS 38.213 [6]) used for calculation of the preceding PH fields. The reported $P_{CMAX,fc}$ and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm are specified in TS 38.133 [11]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits are present instead. + +| | | | | | | | | +|----------|---|----------------------|--|--|--|--|-------| +| | | | | | | | | +| P | V | PH 1 (Type 1, PCell) | | | | | Oct 1 | +| R | V | PH 2 (Type 1, PCell) | | | | | Oct 2 | +| MPE or R | | $P_{CMAX,fc}$ | | | | | Oct 3 | + +**Figure 6.1.3.50-1: Enhanced Single Entry PHR for multiple TRP MAC CE** + +### 6.1.3.51 Enhanced Multiple Entry PHR for multiple TRP MAC CE + +The Enhanced Multiple Entry PHR for multiple TRP MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2b. + +It has a variable size, and includes the bitmaps, a Type 2 PH field and an octet containing the associated $P_{CMAX,fc}$ field (if reported) for SpCell of the other MAC entity, a Type 1 PH field and an octet containing the associated $P_{CMAX,fc}$ field (if + +reported) for the PCell. It further includes, in ascending order based on the *ServCellIndex*, one or multiple of Type X PH fields and octets containing the associated $P_{\text{CMAX,fc}}$ fields (if reported) for Serving Cells other than PCell indicated in the bitmap for indicating the presence of PH(s). X is either 1 or 3 according to TS 38.213 [6] and TS 36.213 [17]. + +The presence of Type 2 PH field for SpCell of the other MAC entity is configured by *phr-Type2OtherCell* with value *true*. + +A single octet bitmap is used for indicating the presence of PH(s) per Serving Cell when the highest *ServCellIndex* of Serving Cell with configured uplink is less than 8, otherwise four octets are used. + +The MAC entity determines whether PH value for an activated Serving Cell is based on real transmission or a reference format by considering the configured grant(s) and downlink control information which has been received until and including the PDCCH occasion in which the first UL grant for a new transmission that can accommodate the MAC CE for PHR as a result of LCP as defined in clause 5.4.3.1 is received since a PHR has been triggered if the PHR MAC CE is reported on an uplink grant received on the PDCCH or until the first uplink symbol of PUSCH transmission minus PUSCH preparation time as defined in clause 7.7 of TS 38.213 [6] if the PHR MAC CE is reported on a configured grant. + +For a band combination in which the UE does not support dynamic power sharing, the UE may omit the octets containing Power Headroom field and $P_{\text{CMAX,fc}}$ field for Serving Cells in the other MAC entity except for the PCell in the other MAC entity and the reported values of Power Headroom and $P_{\text{CMAX,fc}}$ for the PCell are up to UE implementation. + +The two PHs together with one $P_{\text{CMAX,fc}}$ for the Serving Cell configured with the multiple TRP PUSCH repetition feature is configured are reported if the MAC entity is configured with *twoPHRMode*. + +The Enhanced Multiple Entry PHR for multiple TRP MAC CEs are defined as follows: + +- $C_i$ : This field indicates the presence of PH field(s) for the Serving Cell with *ServCellIndex* i as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that PH field(s) for the Serving Cell with *ServCellIndex* i is reported. The $C_i$ field set to 0 indicates that a PH field for the Serving Cell with *ServCellIndex* i is not reported; +- R: Reserved bit, set to 0; +- V: This field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, the V field set to 0 indicates real transmission on PUSCH and the V field set to 1 indicates that a PUSCH reference format is used. For Type 2 PH, the V field set to 0 indicates real transmission on PUCCH and the V field set to 1 indicates that a PUCCH reference format is used. For Type 3 PH, the V field set to 0 indicates real transmission on SRS and the V field set to 1 indicates that an SRS reference format is used. Furthermore, for Type 1, Type 2, and Type 3 PH, the V field set to 0 indicates the presence of the octet containing the associated $P_{\text{CMAX,fc}}$ field and the MPE field, and all of the V field(s) for the Serving Cell set to 1 indicates that the octet containing the associated $P_{\text{CMAX,fc}}$ field and the MPE field is omitted; +- Power Headroom i (PH i): This field indicates the power headroom level, where PH 1 is associated with the *SRS-ResourceSet* with a lower *srs-ResourceSetId* and PH 2 is associated with the *SRS-ResourceSet* with a higher *srs-ResourceSetId*. PH fields for a Serving Cell are included in ascending order based on i. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dB for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding $P_{\text{CMAX,fc}}$ field would have had a different value if no power backoff due to power management had been applied; +- $P_{\text{CMAX,fc}}$ : If present, this field indicates the $P_{\text{CMAX,fc}}$ (as specified in TS 38.213 [6]) for the NR Serving Cell and the $P_{\text{CMAX,c}}$ or $\hat{P}_{\text{CMAX,c}}$ (as specified in TS 36.213 [17]) for the E-UTRA Serving Cell used for calculation of the preceding PH field. The reported $P_{\text{CMAX,fc}}$ and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dBm for the E-UTRA Serving Cell are specified in TS 36.133 [12]); + +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits are present instead. + +| | | | | | | | | +|----------------|----------------|-----------------------------------------------|----------------|----------------|----------------|----------------|---| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | +| P | V | PH 1 (Type 2, SpCell of the other MAC entity) | | | | | | +| R | V | PH 2 (Type 2, SpCell of the other MAC entity) | | | | | | +| MPE or R | | P CMAX,f,c 1 | | | | | | +| P | V | PH 1 (Type 1, PCell) | | | | | | +| R | V | PH 2 (Type 1, PCell) | | | | | | +| MPE or R | | P CMAX,f,c 2 | | | | | | +| P | V | PH 1 (Type X, Serving Cell 1) | | | | | | +| R | V | PH 2 (Type X, Serving Cell 1) | | | | | | +| MPE or R | | P CMAX,f,c 3 | | | | | | +| ... | | | | | | | | +| P | V | PH 1 (Type X, Serving Cell n) | | | | | | +| R | V | PH 2 (Type X, Serving Cell n) | | | | | | +| MPE or R | | P CMAX,f,c m | | | | | | + +**Figure 6.1.3.51-1: Enhanced Multiple Entry PHR for multiple TRP MAC CE with the highest ServCellIndex of Serving Cell with configured uplink is less than 8** + +| | | | | | | | | +|-----------------|-----------------|-----------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | +| P | V | PH 1 (Type 2, SpCell of the other MAC entity) | | | | | | +| R | V | PH 2 (Type 2, SpCell of the other MAC entity) | | | | | | +| MPE or R | | P CMAX,f,c 1 | | | | | | +| P | V | PH 1 (Type 1, PCell) | | | | | | +| R | V | PH 2 (Type 1, PCell) | | | | | | +| MPE or R | | P CMAX,f,c 2 | | | | | | +| P | V | PH 1 (Type X, Serving Cell 1) | | | | | | +| R | V | PH 2 (Type X, Serving Cell 1) | | | | | | +| MPE or R | | P CMAX,f,c 3 | | | | | | +| ... | | | | | | | | +| P | V | PH 1 (Type X, Serving Cell n) | | | | | | +| R | V | PH 2 (Type X, Serving Cell n) | | | | | | +| MPE or R | | P CMAX,f,c m | | | | | | + +**Figure 6.1.3.51-2: Enhanced Multiple Entry PHR for multiple TRP MAC CE with the highest ServCellIndex of Serving Cell with configured uplink is equal to or higher than 8** + +### 6.1.3.52 Sidelink DRX Command MAC CE + +The Sidelink DRX Command MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.4-1. The priority of the Sidelink DRX Command MAC CE is fixed to '1'. + +It has a fixed size of zero bits. + +SL DRX Command MAC CE is only supported in sidelink unicast. + +### 6.1.3.53 Inter-UE Coordination Information MAC CE + +The Inter-UE Coordination Information MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.4-1. The priority of the Inter-UE Coordination Information MAC CE is fixed to '1' for Logical Channel Prioritization (LCP) procedure. It has a variable size with following fields: + +- RT: This field indicates the resource set type, i.e., preferred resource set or non-preferred resource set, as the codepoint value of the SCI format 2-C *resourceSetType* field as specified in TS 38.212 [9]. +- RSL: This field indicates the location of reference slot, as the codepoint value of the SCI format 2-C *referenceSlotLocation* field as specified in TS 38.212 [9]. The length of the field is 17 bits. If the length of *referenceSlotLocation* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 17 bit, this field contains *referenceSlotLocation* field using the LSB bits; +- LSIi: This field indicates lowest subchannel indices for the first resource location of each TRIV, as the codepoint value of the SCI format 2-C *lowestIndices* field as specified in TS 38.212 [9]. LSI0 indicates lowest subchannel indices for the first resource location of TRIV within the first resource combination, LSI1 indicates lowest subchannel indices for the first resource location of TRIV within the second resource combination and so on. The length of the field is 5 bits. If the length of *lowestIndices* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 5 bit, this field contains *lowestIndices* field using the LSB bits; +- RCi: This field indicates resource combination, as the codepoint value of the SCI format 2-C *resourceCombination* field as specified in TS 38.212 [9]. The number of RC is based on upper bound of the L field in the MAC subheader as indicated in clause 6.2.1. RC0 indicates the first resource combination, RC1 indicates the second resource combination and so on. The length of the field is 26 bits. If the length of *resourceCombination* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 26 bit, this field contains *resourceCombination* field using the LSB bits; +- First resource locationi+1: This field indicates first resource location, as the codepoint value of the SCI format 2-C *firstResourceLocation* field as specified in TS 38.212 [9]. First Resource Location0 indicates the first resource location for the second resource combination, First Resource Location1 indicates the first resource location for the third resource combination and so on. The length of the field is 13 bits. If the length of *firstResourceLocation* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 13 bit, this field contains *firstResourceLocation* field using the LSB bits; +- R: Reserved bit, set to 0. + +NOTE: It is up to UE implementation to determine whether and how to select a subset of RCs to be included in the Inter-UE Coordination Information MAC CE. + +![](bdedc4445bc14629d68d2fed555b83e9_img.jpg) + +| | | | | | | | | | +|----------------------------------------|-----|------------------|---|------------------|---|-----------------|---|----------| +| | | | | | | | | | +| RT | RSL | | | | | | | Oct 1 | +| RSL | | | | | | | | Oct 2 | +| RSL | | LSI 0 | | | | RC 0 | | Oct 3 | +| RC 0 | | | | | | | | Oct 4 | +| RC 0 | | | | | | | | Oct 5 | +| RC 0 | | | | | | | | Oct 6 | +| RC 0 | R | R | R | R | R | R | R | Oct 7 | +| ... | | | | | | | | | +| First resource location i-1 | | | | | | | | Oct 6N-4 | +| First resource location i-1 | | | | LSI i | | | | Oct 6N-3 | +| LSI i | | RC i | | | | | | Oct 6N-2 | +| RC i | | | | | | | | Oct 6N-1 | +| RC i | | | | | | | | Oct 6N | +| RC i | | | | R | R | R | R | Oct 6N+1 | + +**Figure 6.1.3.53-1: Inter-UE Coordination Information MAC CE** + +### 6.1.3.54 Inter-UE Coordination Request MAC CE + +The Inter-UE Coordination request MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.4-1. The priority of the Inter-UE Coordination Request MAC CE is fixed to '1' for Logical Channel Prioritization (LCP) procedure. It has a fixed size of 48 bits with following fields: + +- RT: If the value of *sl-DetermineResourceType* (as specified in TS 38.331 [5] clause 6.3.5) is set to *ueb*, this field indicates the resource set type, i.e., preferred resource set or non-preferred resource set, as the codepoint value of the SCI format 2-C *resourceSetType* field as specified in TS 38.212 [9]. This field is ignored if the value of *sl-DetermineResourceType* is set to *uea*; +- RP: This field indicates the resource reservation period, as the codepoint value of the SCI format 2-C *resourceReservationPeriod* field as specified in TS 38.212 [9]. The length of the field is 4 bits. If the length of *resourceReservationPeriod* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 4 bit, this field contains *resourceReservationPeriod* field using the LSB bits; +- Priority: This field indicates the priority, as the codepoint value of the SCI format 2-C *priority* field as specified in TS 38.212 [9]. The length of the field is 3 bits; +- RSWL: This field indicates resource selection window location, as the codepoint value of the SCI format 2-C *resourceSelectionWindowLocation* field as specified in TS 38.212 [9]. The length of the field is 34 bits. If the length of *resourceSelectionWindowLocation* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 34 bit, this field contains *resourceSelectionWindowLocation* field using the LSB bits; + +- Number of Subchannel: This field indicates the number of subchannels, as the codepoint value of the SCI format 2-C *numberOfSubchannel* field as specified in TS 38.212 [9]. The length of the field is 5 bits. If the length of *numberOfSubchannel* field in SCI format 2-C as specified in TS 38.212 [9] is shorter than 5 bit, this field contains *numberOfSubchannel* field using the LSB bits; +- R: Reserved bit, set to 0. + +![](9dc21f873b6fe32363beafc29e18ba0f_img.jpg) + +| | | | | | | | | +|------|----------------------|--|----------|---|--|-------|-------| +| | | | | | | | | +| RT | RP | | Priority | | | | Oct 1 | +| RSWL | | | | | | | Oct 2 | +| RSWL | | | | | | | Oct 3 | +| RSWL | | | | | | | Oct 4 | +| RSWL | | | | | | | Oct 5 | +| RSWL | Number of Subchannel | | | R | | Oct 6 | | + +**Figure 6.1.3.54-1: Inter-UE Coordination Request MAC CE** + +### 6.1.3.55 Enhanced SCell Activation/Deactivation MAC CEs + +The Enhanced SCell Activation/Deactivation MAC CE with one octet $C_i$ field is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of seven $C_i$ -fields, one R-field and zero or more TRS IDj fields in ascending order based on the *SCellIndex* for SCells indicated by the $C_i$ field(s) to be activated. The Enhanced SCell Activation/Deactivation MAC CE of with one octet $C_i$ field is defined as follows (Figure 6.1.3.55-1). + +The Enhanced SCell Activation/Deactivation MAC CE with four octet $C_i$ field is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of 31 $C_i$ -fields, one R-field and zero or more TRS IDj fields in ascending order based on the *SCellIndex* for SCells indicated by the $C_i$ field(s) to be activated. The Enhanced SCell Activation/Deactivation MAC CE with four octet $C_i$ field is defined as follows (Figure 6.1.3.55-2). + +- $C_i$ : If there is an SCell configured for the MAC entity with *SCellIndex* $i$ as specified in TS 38.331 [5], this field indicates the activation/deactivation status of the SCell with *SCellIndex* $i$ , else the MAC entity shall ignore the $C_i$ field. The $C_i$ field is set to 1 to indicate that the SCell with *SCellIndex* $i$ shall be activated and that a TRS IDj field is included for the SCell. The $C_i$ field is set to 0 to indicate that the SCell with *SCellIndex* $i$ shall be deactivated and that no TRS ID field is included for this SCell; +- TRS IDj: If TRS IDj is set to a non-zero value, it indicates the corresponding TRS address by *scellActivationRS-Id* as specified in TS 38.331 [5] is activated. If TRS IDj is set to zero, it indicates that no TRS is used for the corresponding SCell; +- R: Reserved bit, set to 0. + +![Diagram of Enhanced SCell Activation/Deactivation MAC CE with one octet Ci field. It shows a header row of 8 empty cells, followed by Octet 1 containing C7, C6, C5, C4, C3, C2, C1, and R. Octet 2 contains TRS ID1. An ellipsis indicates intermediate octets, and Octet N+1 contains TRS IDN.](b2f6158e74f297659bf41c5939b2c1e0_img.jpg) + +| | | | | | | | | | +|---------------------|----------------|----------------|----------------|----------------|----------------|----------------|---|---------| +| | | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | Oct 1 | +| TRS ID 1 | | | | | | | | Oct 2 | +| ... | | | | | | | | | +| TRS ID N | | | | | | | | Oct N+1 | + +Diagram of Enhanced SCell Activation/Deactivation MAC CE with one octet Ci field. It shows a header row of 8 empty cells, followed by Octet 1 containing C7, C6, C5, C4, C3, C2, C1, and R. Octet 2 contains TRS ID1. An ellipsis indicates intermediate octets, and Octet N+1 contains TRS IDN. + +Figure 6.1.3.55-1: Enhanced SCell Activation/Deactivation MAC CE with one octet Ci field + +![Diagram of Enhanced SCell Activation/Deactivation MAC CE with four octet Ci field. It shows a header row of 8 empty cells, followed by Octet 1 (C7-R), Octet 2 (C15-C8), Octet 3 (C23-C16), Octet 4 (C31-C24), and Octet 5 (TRS ID1). An ellipsis indicates intermediate octets, and Octet N+4 contains TRS IDN.](67f75a54aad5f67ad7c6eda9e1a676c9_img.jpg) + +| | | | | | | | | | +|---------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|---------| +| | | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | Oct 1 | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | Oct 2 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | Oct 3 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | Oct 4 | +| TRS ID 1 | | | | | | | | Oct 5 | +| ... | | | | | | | | | +| TRS ID N | | | | | | | | Oct N+4 | + +Diagram of Enhanced SCell Activation/Deactivation MAC CE with four octet Ci field. It shows a header row of 8 empty cells, followed by Octet 1 (C7-R), Octet 2 (C15-C8), Octet 3 (C23-C16), Octet 4 (C31-C24), and Octet 5 (TRS ID1). An ellipsis indicates intermediate octets, and Octet N+4 contains TRS IDN. + +Figure 6.1.3.55-2: Enhanced SCell Activation/Deactivation MAC CE with four octet Ci field + +### 6.1.3.56 Timing Advance Report MAC CE + +The Timing Advance Report MAC CE is identified by MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.56-1): + +- R: Reserved bit, set to 0; +- Timing Advance: In FR1 except for ATG, the Timing Advance field indicates the least integer number of slots for NTN or symbols for ATG, using subcarrier spacing of 15 kHz for NTN and either 15 kHz or 30 kHz for ATG, greater than or equal to the Timing Advance value (see TS 38.211 [8], clause 4.3.1). For ATG, the Timing Advance field indicates the least integer number of symbols greater than or equal to the Timing Advance value (see TS 38.211 [8], clause 4.3.1). The symbol duration is based on the subcarriers spacing the UE is currently configured with. In this release of the specification, only 15 kHz and 30 kHz SCS are applicable and only values 1 ... 56 are used. The length of the field is 14 bits. + +![Diagram of Timing Advance Report MAC CE. Octet 1 contains two reserved bits (R) and the first 14 bits of the Timing Advance field. Octet 2 contains the remaining 14 bits of the Timing Advance field.](17176612be2d4571951994a0da8a8528_img.jpg) + +| | | | | | | | | | +|----------------|---|----------------|--|--|--|--|--|-------| +| | | | | | | | | | +| R | R | Timing Advance | | | | | | Oct 1 | +| Timing Advance | | | | | | | | Oct 2 | + +Diagram of Timing Advance Report MAC CE. Octet 1 contains two reserved bits (R) and the first 14 bits of the Timing Advance field. Octet 2 contains the remaining 14 bits of the Timing Advance field. + +Figure 6.1.3.56-1: Timing Advance Report MAC CE + +### 6.1.3.57 Differential Koffset MAC CE + +The Differential Koffset MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.57-1): + +- R: Reserved bit, set to 0; +- Differential Koffset: This field indicates the differential Koffset in the number of slots (see clause 4.2 in TS 38.213 [6]), using subcarrier spacing of 15 kHz. The length of the field is 6 bits. + +![Figure 6.1.3.57-1: Differential Koffset MAC CE diagram. It shows a single octet structure with two reserved bits (R) and a 6-bit Differential Koffset field. The octet is labeled 'Oct 1'.](3a587aa09b68d647ac0381e7e1c7cfec_img.jpg) + +| | | | | | | | | | +|---|---|----------------------|--|--|--|--|--|-------| +| | | | | | | | | | +| R | R | Differential Koffset | | | | | | Oct 1 | + +Figure 6.1.3.57-1: Differential Koffset MAC CE diagram. It shows a single octet structure with two reserved bits (R) and a 6-bit Differential Koffset field. The octet is labeled 'Oct 1'. + +Figure 6.1.3.57-1: Differential Koffset MAC CE + +### 6.1.3.58 BFD-RS Indication MAC CE + +The BFD-RS Indication MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size, and includes a BFD-RS-ID0 field and a BFD-RS-ID1 field (optional) of *failureDetectionSet1*, and a BFD-RS-ID0 field and a BFD-RS-ID1 field (optional) of *failureDetectionSet2*. + +It has a variable size consisting of following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.213 [6]. The length of the BWP ID field is 2 bits; +- S: This field indicates the presence of the octet containing the BFD-RS ID1 of the same BFD-RS set. The S field set to 1 indicates that the octet containing BFD-RS ID1 is included. The S field set to 0 indicates that the octet containing the BFD-RS ID1 of the same BFD-RS set is not included; +- BFD-RS IDi: This field indicates the BFD-RS resource from *failureDetectionSet1* or *failureDetectionSet2* as specified in TS 38.331 [5]; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.58-1: BFD-RS Indication MAC CE diagram. It shows a variable size structure with multiple octets. Oct 1 contains R, Serving Cell ID (5 bits), and BWP ID (2 bits). Oct 2 contains R, S, and Set1: BFD-RS ID0. Oct 3 contains R, R, and Set1: BFD-RS ID1. Oct 4 contains R, S, and Set2: BFD-RS ID0. Oct 5 contains R, R, and Set2: BFD-RS ID1.](9753ea14ea728b0e8fd5c6fde5029d66_img.jpg) + +| | | | | | | | | | +|---|-----------------|------------------------------|--|--|--|--------|-------|-------| +| | | | | | | | | | +| R | Serving Cell ID | | | | | BWP ID | Oct 1 | | +| R | S | Set1: BFD-RS ID 0 | | | | | | Oct 2 | +| R | R | Set1: BFD-RS ID 1 | | | | | | Oct 3 | +| R | S | Set2: BFD-RS ID 0 | | | | | | Oct 4 | +| R | R | Set2: BFD-RS ID 1 | | | | | | Oct 5 | + +Figure 6.1.3.58-1: BFD-RS Indication MAC CE diagram. It shows a variable size structure with multiple octets. Oct 1 contains R, Serving Cell ID (5 bits), and BWP ID (2 bits). Oct 2 contains R, S, and Set1: BFD-RS ID0. Oct 3 contains R, R, and Set1: BFD-RS ID1. Oct 4 contains R, S, and Set2: BFD-RS ID0. Oct 5 contains R, R, and Set2: BFD-RS ID1. + +Figure 6.1.3.58-1: BFD-RS Indication MAC CE + +### 6.1.3.59 SP/AP SRS TCI State Indication MAC CE + +The SP/AP SRS TCI State Indication MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields: + +- A/D: This field indicates whether to activate or deactivate indicated SP SRS resource set. The field is set to 1 to indicate activation, otherwise it indicates deactivation. If the indicated SRS resource set ID is for the AP SRS resource set, MAC entity shall ignore this field; +- SRS Resource Set's Cell ID: This field indicates the identity of the Serving Cell, which contains the indicated SP/AP SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the Serving Cell associated with all TCI states indicated by the TCI State IDi fields. The length of the field is 5 bits; +- SRS Resource Set's BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains the indicated SP/AP SRS Resource Set. If the C field is set to 0, this field also indicates the identity of the BWP associated with all TCI states indicated by the TCI State IDi fields. The length of the field is 2 bits; +- C: This field indicates whether the octets containing TCI State Serving Cell ID field(s) and TCI State BWP ID field(s) are present. If this field is set to 1, TCI State Serving Cell ID field(s) and TCI State BWP ID field(s) are present, otherwise they are not present so MAC entity shall ignore TCI State Serving Cell ID field(s) and TCI State BWP ID field(s); +- SUL: This field indicates whether the MAC CE applies to the NUL carrier or SUL carrier configuration. This field is set to 1 to indicate that it applies to the SUL carrier configuration, and it is set to 0 to indicate that it applies to the NUL carrier configuration; +- SRS Resource Set ID: This field indicates the SP/AP SRS Resource Set ID identified by *SRS-ResourceSetId* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- TCI State Serving Cell IDi: This field indicates the identity of the Serving Cell on which the TCI State used for SRS resource i is located. The length of the field is 5 bits; +- TCI State BWP IDi: This field indicates a BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], on which the TCI State used for SRS resource i is located. If value of *unifiedTCI-StateType* in the Serving Cell indicated by TCI State Serving Cell IDi is *joint*, this field indicates a DL BWP. If value of *unifiedTCI-StateType* in the Serving Cell indicated by TCI State Serving Cell IDi is *separate*, this field indicates a UL BWP. The length of the field is 2 bits; +- TCI State IDi: This field contains an identifier of the TCI state used for SRS resource i. TCI State ID0 refers to the first SRS resource within the resource set, TCI State ID1 refers to the second one and so on. If joint/downlink TCI State is used, 7-bits length TCI state ID i.e. *TCI-StateId* as specified in TS 38.331 [5] is used. If separate downlink and uplink TCI State is used, the most significant bit of TCI state ID is considered as a reserved bit and the remaining 6 bits indicate the *TCI-UL-State-Id* as specified in TS 38.331 [5]. The length of the field is 7 bits. This field is only present if MAC CE is used for activation of SP SRS resource set, i.e. the A/D field is set to 1, or for AP SRS resource set; +- R: Reserved bit, set to 0. + +![](cd2b491634dadbccc5b38620840d01f9_img.jpg) + +| | | | | | | | | +|-----|------------------------------------------|---|-----|---------------------|---------------------------------|----------|----------| +| | | | | | | | | +| A/D | SRS Resource Set's Cell ID | | | | SRS Resource Set's BWP ID | Oct 1 | | +| R | R | C | SUL | SRS Resource Set ID | | Oct 2 | | +| R | TCI State Serving Cell ID 0 | | | | TCI State BWP ID 0 | Oct 3 | | +| R | TCI State ID 0 | | | | | | Oct 4 | +| ... | | | | | | | | +| R | TCI State Serving Cell ID N-1 | | | | TCI State BWP ID N-1 | Oct 2N+1 | | +| R | TCI State ID N-1 | | | | | | Oct 2N+2 | + +**Figure 6.1.3.59-1: SP/AP SRS TCI State Indication MAC CE** + +### 6.1.3.60 Serving Cell Set based SRS TCI State Indication MAC CE + +The Serving Cell Set based SRS TCI State Indication MAC CE is identified by a MAC subheader with eLCID as specified. It has a variable size with following fields: + +- SRS Resource's Cell ID: This field indicates the identity of the Serving Cell, which contains the indicated SP/AP SRS Resource. If the C field is set to 0, this field also indicates the identity of the Serving Cell associated with all TCI States indicated by the TCI State IDi fields. The length of the field is 5 bits. The indicated Serving Cell is configured as part of *simultaneousSpatial-UpdatedList1* or *simultaneousSpatial-UpdatedList2* in TS 38.331 [5], and this MAC CE applies to all the Serving Cells configured in the set *simultaneousSpatial-UpdatedList1* or *simultaneousSpatial-UpdatedList2*, respectively; +- SRS Resource's BWP ID: This field indicates a UL BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], which contains the indicated AP/SP SRS Resource. If the C field is set to 0, this field also indicates the identity of the BWP associated with all TCI States indicated by the TCI State IDi fields. The length of the field is 2 bits; +- C: This field indicates whether the octets containing TCI State Serving Cell ID field(s) and TCI State BWP ID field(s) are present. If this field is set to 1, the TCI State Serving Cell ID field(s) and TCI State BWP ID field(s) are present, otherwise they are not present so MAC entity shall ignore TCI State Serving Cell ID field(s) and TCI State BWP ID field(s); +- SRS Resource IDi: This field indicates the SP/AP SRS Resource ID identified by *SRS-ResourceId* as specified in TS 38.331 [5]. The length of the field is 6 bits; +- TCI State Serving Cell IDi: This field indicates the identity of the Serving Cell on which the TCI State used for SRS Resource IDi is located. The length of the field is 5 bits; +- TCI State BWP IDi: This field indicates a BWP as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9], on which the TCI State used for SRS Resource IDi is located. If value of *unifiedTCI-StateType* in the Serving Cell indicated by TCI State Serving Cell IDi is joint, this field indicates a DL BWP. If value of *unifiedTCI-StateType* in the Serving Cell indicated by TCI State Serving Cell IDi is separate, this field indicates a UL BWP. The length of the field is 2 bits; +- TCI State IDi: This field contains an identifier of the TCI state used for SRS resource i. TCI State ID0 refers to the first SRS resource which is indicated SRS Resource ID0, TCI State ID1 refers to the second one and so on. If joint/downlink TCI State is used, 7-bits length TCI state ID i.e. *TCI-StateId* as specified in TS 38.331 [5] is used. If separate downlink and uplink TCI State is used, the most significant bit of TCI state ID is considered as a reserved bit and the remaining 6 bits indicate the *TCI-UL-State-Id* as specified in TS 38.331 [5]. The length of the field is 7 bits; + +- R: Reserved bit, set to 0. + +![](515b883cf43839048d22dbcec99d7d38_img.jpg) + +| | | | | | | | | +|-----|------------------------------------------|--------------------------------|---------------------------------|--|--|--|----------| +| | | | | | | | | +| A/D | SRS Resource's Cell ID | | SRS Resource's BWP ID | | | | Oct 1 | +| R | C | SRS Resource ID 0 | | | | | Oct 2 | +| R | TCI State Serving Cell ID 0 | | TCI State BWP ID 0 | | | | Oct 3 | +| R | TCI State ID 0 | | | | | | Oct 4 | +| | | | | | | | ... | +| R | C | SRS Resource ID N-1 | | | | | Oct 3N-1 | +| R | TCI State Serving Cell ID N-1 | | TCI State BWP ID N-1 | | | | Oct 3N | +| R | TCI State ID N-1 | | | | | | Oct 3N+1 | + +**Figure 6.1.3.60-1: Serving Cell Set based SRS TCI State Indication MAC CE** + +### 6.1.3.61 Child IAB-DU Restricted Beam Indication MAC CE + +The Child IAB-DU Restricted Beam Indication MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields (Figure 6.1.3.61-1): + +- Resource Configuration ID: This field indicates the RRC configuration which applies to this MAC CE and corresponds to *iab-ResourceConfigID* parameter in *IAB-ResourceConfig* as specified in TS 38.331 [5]. The length of the field is 16 bits; +- Number of child IAB-DU beams: This field indicates the number of restricted child IAB-DU beams included in the MAC CE. The length of the field is 8 bits. The number of restricted child IAB-DU beams is contained in the 3 rightmost bits of the field while the remaining 5 bits are considered as reserved bits; +- IAB-DU restricted beams type IDi: This field determines the type of information used as an indication of a set of child IAB-DU's restricted beams, indicated with the Child IAB-DU Resource set IDi field. IAB-DU restricted beams type ID0 refers to the first restricted beam within the resource set, IAB-DU restricted beams type ID1 to the second one and so on. If the value of the field is 00, SSB index is used (contained in the 6 rightmost bits of the Child IAB-DU Resource set IDi field, with the two leftmost bits being set to zero). If the value of the field is 01, SSB index (contained in the 6 rightmost bits of the Child IAB-DU Resource set IDi field) and STC index (contained in the two leftmost bits of the Child IAB-DU Resource set IDi field) are both used. If the value of the field is set to 11, CSI-RS index, which is the *NZP-CSI-RS-ResourceId* as specified in TS 38.331 [5], is used (comprising all 8 bits of the Child IAB-DU Resource set IDi field). The length of the field is 2 bits; +- Ci1: This field indicates whether the octet containing the Number of cell configurations IDi field is included or not. C01 refers to the first restricted beam within the resource set, C11 to the second one and so on. The field is set to 0 to indicate the octet is not included (and subsequently, that no cell information is included for the relevant restricted beam). The field is set to 1 to indicate that Number of cell configurations IDi field is included. The length of the field is 1 bits; +- Ci2: This field indicates whether the child IAB-DU beam indicated with the Child IAB-DU Resource set IDi field is associated with one or more uplink or downlink IAB-MT beams, indicated with the IAB-MT Resource set IDij fields. C02 refers to the first restricted beam within the resource set, C12 to the second one and so on. The field is set to 1 to indicate that at least one IAB-MT Resource set IDij field is included (and that Number of associated IAB-MT beams IDi is included), and it is set to 0 to indicate that no IAB-MT Resource set IDij field is present (and that the Number of associated IAB-MT beams IDi is absent). The length of the field is 1 bit; + +- R: Reserved bit, set to 0; +- Child IAB-DU Resource set IDi: an indication of the child IAB-DU's beam in the direction of which simultaneous operation is restricted. The length of the field is 8 bits; +- Number of cell configurations IDi: This field indicates the number of cell configurations associated with the beam restriction indicated in Child IAB-DU Resource set IDi. Number of cell configurations ID0 refers to the first restricted beam within the resource set, Number of cell configurations ID1 to the second one and so on. The length of the field is 8 bits; +- Cell info type IDij: indicates the type of information included in the Cell info IDij field. If the value of the field is set to zero, the combination of {MT CC, DU cell} is included in the Cell info IDij field, by including the IAB-DU cell in the first nine bits of the field, and the IAB-MT Serving Cell index into the next 5 bits of the field,. If the value of the field is set to one, only DU cell is included in the Cell info IDij field, by including the IAB-DU cell in the first nine bits of the field, and by setting the remaining five bits to zero. The length of the field is 1 bit; +- Mij: This field indicates whether the octet containing multiplexing mode info (containing the Multiplexing mode info IDij field) is included or not. Mi0 refers to the first combination of {MT CC, DU cell} associated with Child IAB-DU Resource set IDi, Mi1 to the second one and so on. The field is set to 1 to indicate that multiplexing mode info is included, and it is set to 0 to indicate that multiplexing mode info is not present. The length of the field is 1 bit; +- Cell info IDij: indicates the cell configuration associated with beam restriction indicated in Child IAB-DU Resource set IDi. Cell info IDi0 field refers to the first cell configuration associated with the beam restriction indicated in Child IAB-DU Resource set IDi, Cell info IDi1 field refers to the second cell configuration associated with the beam restriction indicated in Child IAB-DU Resource set IDi, and so on. The length of the field is 15 bits; +- Multiplexing mode info IDij: The two rightmost bits indicate which of the four multiplexing modes defined in TS 38.473 [27] is applicable. The third rightmost bit of this field indicates whether multiplexing restrictions mode information contained in the two rightmost bits of the field are applicable to non-overlapping frequency resources. This bit is set to 1 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info IDij field is applicable to non-overlapping frequency resources. This field is set to 0 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info IDij field is not applicable to non-overlapping frequency resources. The remaining 5 bits of this field are set to zero. The length of the field is 8 bits; +- Number of associated IAB-MT beams IDi: This field indicates the number of IAB-MT beams associated with the beam indicated in Child IAB-DU Resource set IDi. Number of associated IAB-MT beams ID0 refers to the first restricted beam within the resource set, Number of associated IAB-MT beams ID1 to the second one and so on. The length of the field is 8 bits. The number of IAB-MT beams associated with the beam indicated in Child IAB-DU Resource set IDi is contained in the 3 rightmost bits of the field while the remaining 5 bits are considered as reserved bits; +- Associated IAB-MT's beams type IDij: This field determines the type of information used as an indication of an uplink or downlink IAB-MT beam associated with the child IAB-DU's restricted beams, indicated with the IAB-MT Resource set IDij. If the value of the field is 00, the information included in the IAB-MT Resource set IDij field is the TCI state ID (contained in the 7 rightmost bits of the field). If the value of the field is 01, the information included in the IAB-MT Resource set IDij field is the SSB ID (contained in the 6 rightmost bits of the field). If the value of the field is 10, the information included in the IAB-MT Resource set IDij field is the CSI-RS index (comprising all 8 bits), which is the *NZP-CSI-RS-ResourceId* as specified in TS 38.331 [5]. If the value of the field is 11, the information included in the 6 rightmost bits in the IAB-MT Resource set IDij field is the *SRS-ResourceID*. The length of the field is 2 bits; +- IAB-MT Resource set IDij: an indication of the IAB-MTs downlink or uplink beams which are associated with the child IAB-DU restricted beam indicated in Child IAB-DU Resource set IDi field. IAB-MT Resource set IDi0 field refers to the first IAB-MT's beam associated with the child IAB-DU's restricted beam indicated in Child IAB-DU Resource set IDi field, IAB-MT Resource set IDi1 field refers to the second IAB-MT's beam associated with the child IAB-DU's restricted beam indicated in Child IAB-DU Resource set IDi field, and so on. The length of the field is 8 bits. + +| | | | | | | | | +|-----------------------------------------------|--|------------------|-----------------------------|-----------------|---|---|---| +| | | | | | | | | +| Resource Configuration ID | | | | | | | | +| Resource Configuration ID | | | | | | | | +| Number of child IAB-DU beams | | | | | | | | +| IAB-DU restricted beams type ID 0 | | R | C 01 | C 02 | R | R | R | +| Child IAB-DU Resource set ID 0 | | | | | | | | +| Number of cell configurations ID 0 | | | | | | | | +| Cell info type ID 0,0 | | M 0,0 | Cell info ID 0,0 | | | | | +| Cell info ID 0,0 | | | | | | | | +| Multiplexing mode info ID 0,0 | | | | | | | | + +... + +| | | | | | | | | +|------------------------------------------------------|--|------------------------------|-----------------------------------------|---|---|---|---| +| Cell info type ID 0,n0 | | M 0,n0 | Cell info ID 0,n0 | | | | | +| Cell info ID 0,n0 | | | | | | | | +| Multiplexing mode info ID 0,n0 | | | | | | | | +| Number of associated IAB-MT beams ID 0 | | | | | | | | +| Associated MT beams type ID 0,0 | | R | R | R | R | R | R | +| IAB-MT Resource set ID 0,0 | | | | | | | | + +... + +| | | | | | | | | +|--------------------------------------------------------|--|---|---|---|---|---|---| +| Associated MT beams type ID 0,m0 | | R | R | R | R | R | R | +| IAB-MT Resource set ID 0,m0 | | | | | | | | + +... + +| | | | | | | | | +|-----------------------------------------------|--|------------------|-----------------------------|-----------------|---|---|---| +| IAB-DU restricted beams type ID N | | R | C N1 | C N2 | R | R | R | +| Child IAB-DU Resource set ID N | | | | | | | | +| Number of cell configurations ID N | | | | | | | | +| Cell info type ID N,0 | | M N,0 | Cell info ID N,0 | | | | | +| Cell info ID N,0 | | | | | | | | +| Multiplexing mode info ID N,0 | | | | | | | | + +... + +| | | | | | | | | +|------------------------------------------------------|--|------------------------------|-----------------------------------------|---|---|---|---| +| Cell info type ID N,nN | | M N,nN | Cell info ID N,nN | | | | | +| Cell info ID N,nN | | | | | | | | +| Multiplexing mode info ID N,nN | | | | | | | | +| Number of associated IAB-MT beams ID N | | | | | | | | +| Associated MT beams type ID N,0 | | R | R | R | R | R | R | +| IAB-MT Resource set ID N,0 | | | | | | | | + +... + +| | | | | | | | | +|--------------------------------------------------------|--|---|---|---|---|---|---| +| Associated MT beams type ID N,mN | | R | R | R | R | R | R | +| IAB-MT Resource set ID N,mN | | | | | | | | + +**Figure 6.1.3.61-1: Child IAB-DU Restricted Beam Indication MAC CE****6.1.3.62 IAB-MT Recommended Beam Indication MAC CE** + +The IAB-MT Recommended Beam Indication MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-2b. It has a variable size with following fields (Figure 6.1.3.62-1): + +- Resource Configuration ID: This field indicates the RRC configuration which applies to this MAC CE and corresponds to *iab-ResourceConfigID* parameter in *IAB-ResourceConfig* as specified in TS 38.331 [5]. The length of the field is 16 bits; +- Number of IAB-MT beams: This field indicates the number of recommended IAB-MT beams included in the MAC CE. The length of the field is 8 bits. The number of recommended IAB-MT beams is contained in the 3 rightmost bits of the field while the remaining 5 bits are considered as reserved bits; +- IAB-MT beam type IDi: This field determines the type of information used as an indication of an uplink or downlink IAB-MT beam, indicated with the IAB-MT Resource set IDi. If the value of the field is 00, the information included in the IAB-MT Resource set IDi field is the TCI state ID (contained in the 7 rightmost bits of the field). If the value of the field is 01, the information included in the IAB-MT Resource set IDi field is the SSB ID (contained in the 6 rightmost bits of the field). If the value of the field is 10, the information included in the IAB-MT Resource set IDi field is the CSI-RS index (comprising all 8 bits), which is the *NZP-CSI-RS-ResourceId* as specified in TS 38.331 [5]. If the value of the field is 11, the information included in the 6 rightmost bits in the IAB-MT Resource set IDi field is the *SRS-ResourceID*. The length of the field is 2 bits; +- IAB-MT Resource set IDi: an indication of the IAB-MTs recommended downlink or uplink beams. IAB-MT Resource set ID0 field refers to the first IAB-MT's beam, IAB-MT Resource set ID1 field refers to the second IAB-MT's beam, and so on. The length of the field is 8 bits; +- Cii: This field indicates whether the octet containing the Number of cell configurations IDi field is included or not. C0i refers to the first recommended beam within the resource set, C1i to the second one and so on. The field is set to 0 to indicate the octet is not included (and subsequently, that no cell information is included for the relevant recommended beam). The field is set to 1 to indicate that Number of cell configurations IDi field is included. The length of the field is 1 bits; +- R: Reserved bit, set to 0; +- Number of cell configurations IDi: This field indicates the number of cell configurations associated with the beam indicated in IAB-MT Resource set IDi. Number of cell configurations ID0 refers to the first recommended beam within the resource set, Number of cell configurations ID1 to the second one and so on. The length of the field is 8 bits; +- Cell info type IDij: indicates the type of information included in the Cell info IDij field. If the value of the field is set to zero, the combination of {MT CC, DU cell} is included in the Cell info IDij field, by including the IAB-DU cell in the first nine bits of the field, and the IAB-MT Serving Cell index into the next 5 bits of the field. If the value of the field is set to one, only MT CC information is included in the Cell info IDij field, by including the IAB-MT Serving Cell index in the first 5 bits of the field, and by setting the remaining nine bits to zero. The length of the field is 1 bit; +- Mij: This field indicates whether the octet containing multiplexing mode info (containing the Multiplexing mode info IDij field) is included or not. M0i refers to the first combination of {MT CC, DU cell} associated with IAB-MT Resource set IDi, M1i to the second one and so on. The field is set to 1 to indicate that multiplexing mode info is included, and it is set to 0 to indicate that multiplexing mode info is not present. The length of the field is 1 bit; +- Cell info IDij: indicates the cell configuration associated with beam recommendation indicated in IAB-MT Resource set IDi. Cell info ID0i field refers to the first cell configuration associated with the beam recommendation indicated in IAB-MT Resource set IDi, Cell info ID1i field refers to the second cell configuration associated with the beam recommendation indicated in IAB-MT Resource set IDi, and so on. The length of the field is 14 bits. +- Multiplexing mode info IDij: The two rightmost bits indicate which of the four multiplexing modes defined in TS 38.473 [27] is applicable. The third rightmost bit of this field indicates whether multiplexing restrictions mode information contained in the two rightmost bits of the field are applicable to non-overlapping frequency + +resources. This bit is set to 1 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info IDij field is applicable to non-overlapping frequency resources. This field is set to 0 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info IDij field is not applicable to non-overlapping frequency resources. The remaining 5 bits of this field are set to zero. The length of the field is 8 bits. + +| | | | | | | | | | | | | +|-----------------------------------------------|-----------------|----------------------------|---|---|---|---|--|--|--|--|--| +| | | | | | | | | | | | | +| Resource Configuration ID | | | | | | | | | | | | +| Resource Configuration ID | | | | | | | | | | | | +| Number of IAB-MT beams | | | | | | | | | | | | +| MT beam type ID 0 | R | C 01 | R | R | R | R | | | | | | +| IAB-MT Resource set ID 0 | | | | | | | | | | | | +| Number of cell configurations ID 0 | | | | | | | | | | | | +| Cell info type ID 00 | M 00 | Cell info ID 00 | | | | | | | | | | +| Cell info ID 00 | | | | | | | | | | | | +| Multiplexing mode info ID 00 | | | | | | | | | | | | + +... + +| | | | | | | | | | | | | +|-------------------------------------------|-------------------|------------------------------|--|--|--|--|--|--|--|--|--| +| Cell info type ID 0,n0 | M 0,n0 | Cell info ID 0,n0 | | | | | | | | | | +| Cell info ID 0,n0 | | | | | | | | | | | | +| Multiplexing mode info ID 0,n0 | | | | | | | | | | | | + +... + +| | | | | | | | | | | | | +|-----------------------------------------------|------------------|-----------------------------|---|---|---|---|--|--|--|--|--| +| MT beam type ID m | R | C m1 | R | R | R | R | | | | | | +| IAB-MT Resource set ID m | | | | | | | | | | | | +| Multiplexing mode info ID m | | | | | | | | | | | | +| Number of cell configurations ID m | | | | | | | | | | | | +| Cell info type ID m,0 | M m,0 | Cell info ID m,0 | | | | | | | | | | +| Cell info ID m,0 | | | | | | | | | | | | +| Multiplexing mode info ID m,0 | | | | | | | | | | | | + +... + +| | | | | | | | | | | | | +|-------------------------------------------|-------------------|------------------------------|--|--|--|--|--|--|--|--|--| +| Cell info type ID m,nm | M m,nm | Cell info ID m,nm | | | | | | | | | | +| Cell info ID m,nm | | | | | | | | | | | | +| Multiplexing mode info ID m,nm | | | | | | | | | | | | + +**Figure 6.1.3.62-1: IAB-MT Recommended Beam Indication MAC CE****6.1.3.63 DL TX Power Adjustment and Desired DL TX Power Adjustment MAC CEs** + +The DL TX Power Adjustment MAC CE and Desired DL TX Power Adjustment MAC CEs are identified by MAC subheaders with eLCIDs as specified in Table 6.2.1-1b and Table 6.2.1-1b, respectively. Otherwise the format of the two MAC CEs is identical. Each has a variable size with following fields (Figure 6.1.3.63-1): + +- Resource Configuration ID: This field indicates the RRC configuration which applies to this MAC CE and corresponds to *iab-ResourceConfigID* parameter in *IAB-ResourceConfig* as specified in TS 38.331 [5]. The length of the field is 16 bits; +- DL Tx Power adjustment: For the case of the Desired DL TX Power Adjustment MAC CE, this field contains desired DL TX power adjustment sent by an IAB-MT to assist with the parent node's DL TX power allocation. For the case of the DL TX Power Adjustment MAC CE, this field contains adjustment to a node's DL TX power sent by its parent node. The value of the power adjustment is in both cases contained in the 5 right-most bits of the field with codepoints (00000, 00001, ..., 11101, 11110) indicating the corresponding value (-15dB, -14dB, ..., 14dB, 15dB) and the codepoint 11111 not being used, while the remaining 3 bits are set to zero. The length of the field is 8 bits; +- Reference CSI-RS ID: This field indicates the CSI-RS used as reference for power adjustment, which is identified by *NZP-CSI-RS-ResourceId* as specified in TS 38.331 [5]. The indicated DL TX power adjustment is in terms of a relative offset to the CSI-RS TX power of the indicated CSI-RS. The length of this field is 8 bits; +- $C_0$ : This field indicates whether the octet containing multiplexing mode info (containing the Multiplexing mode info field) is included or not. The field is set to 1 to indicate that multiplexing mode info is included, and it is set to 0 to indicate that multiplexing mode info is not present. The length of the field is 1 bit; +- $C_1$ : This field indicates whether the two octets containing the Cell info are included or not. The field is set to 0 to indicate the two octets are not included (and subsequently, that no cell information is included). The field is set to 1 to indicate that the two octets are included. The length of the field is 1 bits; +- $C_2$ : This field indicates whether any information on IAB-MT DL beams is included or not. The field is set to 1 to indicate that at least one IAB-MT Resource set IDi field is included, and it is set to 0 to indicate that no IAB-MT Resource set IDi field is present. The length of the field is 1 bit; +- R: Reserved bit, set to 0. +- Multiplexing mode info: The two rightmost bits indicate which of the four multiplexing modes defined in TS 38.473 [27] is applicable. The third rightmost bit of this field indicates whether multiplexing restrictions mode information contained in the two rightmost bits of the field are applicable to non-overlapping frequency resources. This bit is set to 1 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info field is applicable to non-overlapping frequency resources. This field is set to 0 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info field is not applicable to non-overlapping frequency resources. The remaining 5 bits of this field are set to zero. The length of the field is 8 bits; +- Number of IAB-MT DL beams: This field indicates the number of IAB-MT beams included in the MAC CE. The length of the field is 8 bits; +- IAB-MT beam type IDi: This field determines the type of information used as an indication of a downlink IAB-MT beam, indicated with the IAB-MT Resource set IDi. If the value of the field is 00, the information included in the IAB-MT Resource set IDi field is the TCI state ID (contained in the 7 rightmost bits of the field). If the value of the field is 01, the information included in the IAB-MT Resource set IDi field is the SSB ID (contained in the 6 rightmost bits of the field). If the value of the field is 10, the information included in the IAB-MT Resource set IDi field is the CSI-RS index (comprising all 8 bits), which is the *NZP-CSI-RS-ResourceId* as specified in TS 38.331 [5]. The length of the field is 2 bits; +- IAB-MT Resource set IDi: an indication of the IAB-MTs downlink beams. IAB-MT Resource set ID0 field refers to the first IAB-MT downlink beam, IAB-MT Resource set ID1 field refers to the second IAB-MT downlink beam, and so on. The length of the field is 8 bits; + +- DU resource configuration: when this field is set to 00, the provided power adjustment is applied on FDM resources where the simultaneous MT and DU signals are non-overlapping in the frequency-domain; when this field is set to 01, the provided power adjustment is applied on non-FDM resources where the simultaneous MT and DU signals may overlap in the frequency-domain for a given (MT CC, DU cell); when this field is set to 10, the provided power adjustment is applied on FDM resources where the simultaneous MT and DU signals are non-overlapping in the frequency-domain, and on non-FDM resources where the simultaneous MT and DU signals may overlap in the frequency-domain for a given (MT CC, DU cell). The length of the field is 2 bits; +- Cell info: indicates the cell configuration associated with the information contained in the MAC CE. The length of the field is 14 bits. IAB-DU cell is contained in the first nine bits of the field, while the Child IAB-MT Serving Cell index into the next 5 bits of the field. The length of the field is 14 bits. + +![](18b439af4d2e65d65a6f8cb3388f7073_img.jpg) + +| | | | | | | | | +|-------------------------------------|----------------|----------------|---|---|---|---|---| +| | | | | | | | | +| Resource Configuration ID | | | | | | | | +| Resource Configuration ID | | | | | | | | +| DL Tx Power adjustment | | | | | | | | +| Reference CSI-RS ID | | | | | | | | +| C 0 | C 1 | C 2 | R | R | R | R | R | +| Multiplexing mode info | | | | | | | | +| Number of IAB-MT DL beams | | | | | | | | +| IAB-MT beam type ID 0 | | R | R | R | R | R | R | +| IAB-MT Resource set ID 0 | | | | | | | | +| ... | | | | | | | | +| IAB-MT beam type ID N | | R | R | R | R | R | R | +| IAB-MT Resource set ID N | | | | | | | | +| DU resource configuration | | Cell info | | | | | | +| Cell info | | | | | | | | + +Figure 6.1.3.63-1: DL TX Power Adjustment and Desired DL TX Power Adjustment MAC CEs + +### 6.1.3.64 Desired IAB-MT PSD range MAC CE + +The Desired IAB-MT PSD range MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-2b. It has a variable size with following fields (Figure 6.1.3.64-1): + +- Resource Configuration ID: This field indicates the RRC configuration which applies to this MAC CE and corresponds to *iab-ResourceConfigID* parameter in *IAB-ResourceConfig* as specified in TS 38.331 [5]. The length of the field is 16 bits; + +- PSD range: This field contains the desired PSD range a node sends to its parent node to help with the sending node's MT UL TX power control. The desired PSD range is indicated by a maximum value (i.e. Pmax), and an offset relative to the maximum value, i.e. the desired PSD range is from Pmax - offset to Pmax. The 4 left-most bits of the field indicate the offset, the offset range is from 0 dB to 10 dB, the value 0000 corresponds to 0 dB, the value 0001 corresponds to 1 dB and so on, the values from 1011 onwards are reserved. The next 7 left-most bits indicate the Pmax range, the Pmax range is from -60 dBm to 50 dBm, the value 0000000 corresponds to -60 dBm, the value 0000001 corresponds to -59 dBm and so on, the values from 1101111 onwards are reserved. The remaining 5 bits are set to zero. The length of the field is 16 bits; +- C0: This field indicates whether the octet containing multiplexing mode info (containing the Multiplexing mode info field) is included or not. The field is set to 1 to indicate that multiplexing mode info is included, and it is set to 0 to indicate that multiplexing mode info is not present. The length of the field is 1 bit; +- C1: This field indicates whether the two octets containing the Cell info are included or not. The field is set to 0 to indicate the two octets are not included (and subsequently, that no cell information is included). The field is set to 1 to indicate that the two octets are included. The length of the field is 1 bits; +- C2: This field indicates whether any information on IAB-MT UL beams is included or not. The field is set to 1 to indicate that at least one IAB-MT Resource set IDi field is included, and it is set to 0 to indicate that no IAB-MT Resource set IDi field is present. The length of the field is 1 bit; +- R: Reserved bit, set to 0; +- Multiplexing mode info: The two rightmost bits indicate which of the four multiplexing modes defined in TS 38.473 [27] is applicable. The third rightmost bit of this field indicates whether multiplexing restrictions mode information contained in the two rightmost bits of the field are applicable to non-overlapping frequency resources. This bit is set to 1 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info field is applicable to non-overlapping frequency resources. This field is set to 0 when multiplexing mode information contained in the two rightmost bits of the Multiplexing mode info field is not applicable to non-overlapping frequency resources. The remaining 5 bits of this field are set to zero. The length of the field is 8 bits; +- Number of IAB-MT UL beams: This field indicates the number N of IAB-MT UL beams included in the MAC CE. The length of the field is 8 bits; +- IAB-MT Resource set IDi: an indication of the IAB-MTs uplink beams. IAB-MT Resource set ID0 field refers to the first IAB-MT uplink beam, IAB-MT Resource set ID1 field refers to the second IAB-MT uplink beam, and so on. If the total number N of beams included in the MAC CE is odd, the 4 right-most bits in the final octet of the IAB-MT Resource set are disregarded by the UE. The length of the field is 4 bits; +- DU resource configuration: when this field is set to 00, the provided power adjustment is applied on FDM resources where the simultaneous MT and DU signals are non-overlapping in the frequency-domain; when this field is set to 01, the provided power adjustment is applied on non-FDM resources where the simultaneous MT and DU signals may overlap in the frequency-domain for a given (MT CC, DU cell); when this field is set to 10, the provided power adjustment is applied on FDM resources where the simultaneous MT and DU signals are non-overlapping in the frequency-domain, and on non-FDM resources where the simultaneous MT and DU signals may overlap in the frequency-domain for a given (MT CC, DU cell). The length of the field is 2 bits; +- Cell info: indicates the cell configuration associated with the information contained in the MAC CE. IAB-DU cell is contained in the first nine bits of the field, while the Child IAB-MT Serving Cell index into the next 5 bits of the field. The length of the field is 14 bits. + +![](e6be648d8221efac693395d853c3bc77_img.jpg) + +| | | | | | | | | +|---------------------------------------|----------------|----------------|---|---------------------------------------|---|---|---| +| | | | | | | | | +| Resource Configuration ID | | | | | | | | +| Resource Configuration ID | | | | | | | | +| PSD range | | | | | | | | +| PSD range | | | | | | | | +| C 0 | C 1 | C 2 | R | R | R | R | R | +| Multiplexing mode info | | | | | | | | +| Number of IAB-MT UL beams | | | | | | | | +| IAB-MT Resource set ID 0 | | | | IAB-MT Resource set ID 1 | | | | +| ... | | | | | | | | +| IAB-MT Resource set ID N-2 | | | | IAB-MT Resource set ID N-1 | | | | +| DU resource configuration | | Cell info | | | | | | +| Cell info | | | | | | | | + +**Figure 6.1.3.64-1: Desired IAB-MT PSD range MAC CE** + +### 6.1.3.65 Timing Case Indication MAC CE + +The Timing Case Indication MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields (Figure 6.1.3.65-1): + +- Resource Configuration ID: This field indicates the RRC configuration which applies to this MAC CE and corresponds to *iab-ResourceConfigID* parameter in *IAB-ResourceConfig* as specified in TS 38.331 [5]. The length of the field is 16 bits; +- Timing mode IDi: when this field is set to 00, the timing mode applied to the ith slot in the list of slots *slotList* provided via RRC in *IAB-ResourceConfig* is Case-1; when this field is set to 01, the timing mode applied to the ith slot in the list of slots *slotList* provided via RRC in *IAB-ResourceConfig* is Case-6; when this field is set to 10, the timing mode applied to the ith slot in the list of slots *slotList* provided via RRC in *IAB-ResourceConfig* is Case-7. The total number N of Timing mode IDi fields corresponds to the size of *slotList* provided via RRC in *IAB-ResourceConfig*. If number N is not divisible by 4, (4 - N mod 4) of the final Timing mode IDi fields are disregarded by the receiving IAB node. The length of the field is 2 bits. + +![Figure 6.1.3.65-1: Timing Case Indication MAC CE diagram. The diagram shows a sequence of octets. The first octet is split into two 'Resource Configuration ID' fields. The second octet is split into four 'Timing mode ID' fields: ID0, ID1, ID2, and ID3. An ellipsis indicates subsequent octets. The final octet shown is split into four 'Timing mode ID' fields: IDN-4, IDN-3, IDN-2, and IDN-1.](704c5137e8e6d3474b72294e6b9c88e4_img.jpg) + +Figure 6.1.3.65-1: Timing Case Indication MAC CE diagram. The diagram shows a sequence of octets. The first octet is split into two 'Resource Configuration ID' fields. The second octet is split into four 'Timing mode ID' fields: ID0, ID1, ID2, and ID3. An ellipsis indicates subsequent octets. The final octet shown is split into four 'Timing mode ID' fields: IDN-4, IDN-3, IDN-2, and IDN-1. + +**Figure 6.1.3.65-1: Timing Case Indication MAC CE** + +### 6.1.3.66 NCR Downlink Backhaul Link Beam Indication MAC CE + +The NCR Downlink Backhaul Link Beam Indication MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.66-1): + +- Downlink TCI state ID: This field is used to indicate the downlink beam to be used for backhaul link transmission. It contains *TCI-StateId* (comprising all 7 bits), as specified in TS 38.331 [5], of a TCI State in the active DL BWP. The length of the field is 7 bits; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.66-1: NCR Downlink Backhaul Link Beam Indication MAC CE diagram. The diagram shows a single octet structure. The first bit is labeled 'R' (Reserved). The remaining 7 bits are labeled 'Downlink TCI state ID'. The entire octet is labeled 'Oct 1' on the right.](790a528e79f24630685ee621c554b633_img.jpg) + +Figure 6.1.3.66-1: NCR Downlink Backhaul Link Beam Indication MAC CE diagram. The diagram shows a single octet structure. The first bit is labeled 'R' (Reserved). The remaining 7 bits are labeled 'Downlink TCI state ID'. The entire octet is labeled 'Oct 1' on the right. + +**Figure 6.1.3.66-1: NCR Downlink Backhaul Link Beam Indication MAC CE** + +### 6.1.3.67 NCR Uplink Backhaul Link Beam Indication MAC CE + +The NCR Uplink Backhaul Link Beam Indication MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.67-1): + +- Uplink TCI state ID or SRS Resource ID: This field is used to indicate the uplink beam to be used for backhaul link transmission. If the *dl-OrJointTCI-StateList* is configured as specified in TS 38.331 [5] and *unifiedTCI-StateType* is configured with a value *joint*, this field contains *TCI-StateId* (comprising all 7 bits) of a Joint TCI State configured in the active DL BWP, which is used as the uplink beam indication for backhaul link transmission. If the *ul-TCI-StateList* is configured as specified in TS 38.331 [5], this field contains *TCI-UL-State-Id* (contained in the 6 rightmost bits) of an UL TCI State configured in the active UL BWP, which is used as the uplink beam indication for backhaul link transmission, with the 1 remaining bit set to zero. Otherwise, 6 rightmost bits of this field contain *SRS-ResourceID* configured in the active UL BWP which is used as the uplink beam indication for backhaul link transmission, with the 1 remaining bit set to zero; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.67-1: NCR Uplink Backhaul Link Beam Indication MAC CE diagram. The diagram shows a single octet structure. The first bit is labeled 'R' (Reserved). The remaining 7 bits are labeled 'Uplink TCI state ID or SRS Resource ID'. The entire octet is labeled 'Oct 1' on the right.](4cb38c4f736fc47ecbb2641eb07be92f_img.jpg) + +Figure 6.1.3.67-1: NCR Uplink Backhaul Link Beam Indication MAC CE diagram. The diagram shows a single octet structure. The first bit is labeled 'R' (Reserved). The remaining 7 bits are labeled 'Uplink TCI state ID or SRS Resource ID'. The entire octet is labeled 'Oct 1' on the right. + +**Figure 6.1.3.67-1: NCR Uplink Backhaul Link Beam Indication MAC CE** + +### 6.1.3.68 NCR Access Link Beam Indication MAC CE + +The NCR Access Link Beam Indication MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of the following fields (Figure 6.1.3.68-1): + +- Resource set ID: This field is used to indicate one of forwarding semi-persistent resource lists signalled in NCR-*SemiPersistentFwdResourceSet* (as specified in TS 38.331 [5]). The field contains a list ID (comprising all 5 bits); +- A/D: If the value of this field is set to 1, the forwarding resource list indicated in Resource set ID field is being activated. If the value of this field is set to 0, the forwarding resource list indicated in Resource set ID field is being deactivated; +- C: If the value of this field is set to 1, the Beam index IDi field is present. If the value of this field is set to 0, the Beam index IDi field is absent. This field can be set to 1 only if MAC CE is used for activation, i.e., when the A/D field is set to 1. If MAC CE is used for deactivation, this field is set to 0; +- Beam index IDi: This field indicates the updated beam index for forwarding resources within the list indicated by the Resource set ID field. Beam index ID0 indicates the beam index for the first forwarding resource within the list; Beam index ID1 indicates the beam index for the second forwarding resource within the list and so on. The length of the field is 6 bits; the number of updated beams, *N*, is equal to the number of the beam indications in the semi-persistent resource set with ID *Resource set ID*; - R: Reserved bit, set to 0. + +![Diagram of NCR Access Link Beam Indication MAC CE structure showing Octet 1 with R, C, A/D, and Resource set ID fields, followed by Octet 2 with R, R, and Beam index ID0, and Octet N+1 with R, R, and Beam index IDN-1.](7a08792c70e070d3716830bdd77391ab_img.jpg) + +| | | | | | | | | +|-----|---|------------------------------|-----------------|--|--|--|---------| +| | | | | | | | | +| R | C | A/D | Resource set ID | | | | Oct 1 | +| R | R | Beam index ID 0 | | | | | Oct 2 | +| ... | | | | | | | | +| R | R | Beam index ID N-1 | | | | | Oct N+1 | + +Diagram of NCR Access Link Beam Indication MAC CE structure showing Octet 1 with R, C, A/D, and Resource set ID fields, followed by Octet 2 with R, R, and Beam index ID0, and Octet N+1 with R, R, and Beam index IDN-1. + +Figure 6.1.3.68-1: NCR Access Link Beam Indication MAC CE + +### 6.1.3.69 SL LBT failure MAC CEs + +The SL LBT failure MAC CE of one octet is identified by a MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size of 8bits: + +- Ri: If there is a RB set configured for the MAC entity with RB set index *i* as specified in TS 38.214 [7] and if SL consistent LBT failure have been triggered and not cancelled in this RB set, the field is set to 1, otherwise the field is set to 0; +- R: Reserved bit, set to 0. + +![Diagram of SL LBT failure MAC CE structure showing Octet 1 with R, R, R, R4, R3, R2, R1, and R0 fields.](dd0d48f6aaa992a96a8c48ba232c56e2_img.jpg) + +| | | | | | | | | +|---|---|---|----------------|----------------|----------------|----------------|----------------------| +| | | | | | | | | +| R | R | R | R 4 | R 3 | R 2 | R 1 | R 0 Oct 1 | + +Diagram of SL LBT failure MAC CE structure showing Octet 1 with R, R, R, R4, R3, R2, R1, and R0 fields. + +Figure 6.1.3.69-1: SL LBT failure MAC CE + +### 6.1.3.70 Enhanced Unified TCI States Activation/Deactivation MAC CE for Joint TCI States + +The Enhanced Unified TCI States Activation/Deactivation MAC CE for Joint TCI States is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4*, respectively; +- DL BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- $F_{ij}$ : This field indicates for the TCI state ID fields associated with the codepoint $i$ of the DCI *Transmission Configuration Indication* field whether the $j$ -th joint TCI state is present or not, where $j=1, 2$ . If $F_{ij}$ field is set to 1, it indicates the $j$ -th joint TCI state for codepoint $i$ is present. If $F_{ij}$ field is set to 0, it indicates the $j$ -th joint TCI state for codepoint $i$ is absent. The codepoint to which a TCI state is mapped is determined by its ordinal position among all the TCI state ID fields; +- TCI state ID: This field indicates the 7-bits length TCI state ID identified by *TCI-StateId* as specified in TS 38.331 [5]. The maximum number of activated TCI states is 16; +- R: Reserved bit, set to 0. + +![Diagram of Enhanced TCI state activation/deactivation MAC CE for Joint TCI States. The diagram shows a sequence of fields: R, Serving Cell ID (5 bits), DL BWP ID (2 bits), followed by a grid of Fij fields (F1,1 to F8,2), then TCI state ID 1, TCI state ID 2, an ellipsis, and finally TCI state ID N. Each TCI state ID is preceded by a reserved bit R. To the right of the fields are labels Oct 1, Oct 2, Oct 3, Oct 4, Oct 5, and Oct N+3.](85e117a13c46e2b4c8b69e1179f25f14_img.jpg) + +| | | | | | | | | | +|-----------|-----------------|-----------|-----------|-----------|-----------|-----------|-----------|---------| +| | | | | | | | | | +| R | Serving Cell ID | | | | | DL BWP ID | | Oct 1 | +| $F_{1,1}$ | $F_{1,2}$ | $F_{2,1}$ | $F_{2,2}$ | $F_{3,1}$ | $F_{3,2}$ | $F_{4,1}$ | $F_{4,2}$ | Oct 2 | +| $F_{5,1}$ | $F_{5,2}$ | $F_{6,1}$ | $F_{6,2}$ | $F_{7,1}$ | $F_{7,2}$ | $F_{8,1}$ | $F_{8,2}$ | Oct 3 | +| R | TCI state ID 1 | | | | | | | Oct 4 | +| R | TCI state ID 2 | | | | | | | Oct 5 | +| ... | | | | | | | | | +| R | TCI state ID N | | | | | | | Oct N+3 | + +Diagram of Enhanced TCI state activation/deactivation MAC CE for Joint TCI States. The diagram shows a sequence of fields: R, Serving Cell ID (5 bits), DL BWP ID (2 bits), followed by a grid of Fij fields (F1,1 to F8,2), then TCI state ID 1, TCI state ID 2, an ellipsis, and finally TCI state ID N. Each TCI state ID is preceded by a reserved bit R. To the right of the fields are labels Oct 1, Oct 2, Oct 3, Oct 4, Oct 5, and Oct N+3. + +Figure 6.1.3.70-1: Enhanced TCI state activation/deactivation MAC CE for Joint TCI States + +### 6.1.3.71 Enhanced Unified TCI States Activation/Deactivation MAC CE for Separate TCI States + +The Enhanced Unified TCI States Activation/Deactivation MAC CE for Separate TCI States is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set *simultaneousU-TCI-UpdateList1*, *simultaneousU-TCI-UpdateList2*, *simultaneousU-TCI-UpdateList3* or *simultaneousU-TCI-UpdateList4*, respectively; +- DL BWP ID: This field indicates a DL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- UL BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; + +- $F_{ij}$ : This field indicates for the TCI state ID fields associated with the codepoint $i$ of the DCI *Transmission Configuration Indication* field whether the $j$ -th DL TCI state is present or not, where $j=1, 2$ . If $F_{ij}$ field is set to 1, it indicates the $j$ -th DL TCI state for codepoint $i$ is present. If $F_{ij}$ field is set to 0, it indicates the $j$ -th DL TCI state for codepoint $i$ is absent; +- $S_{ij}$ : This field indicates for the TCI state ID fields associated with the codepoint $i$ of the DCI *Transmission Configuration Indication* field whether the $j$ -th UL TCI state is present or not, where $j=1, 2$ . If $S_{ij}$ field is set to 1, it indicates the $j$ -th UL TCI state for codepoint $i$ is present. If $S_{ij}$ field is set to 0, it indicates the $j$ -th UL TCI state for codepoint $i$ is absent; +- TCI state ID: This field indicates the TCI state identified by *TCI-StateId* as specified in TS 38.331 [5]. If the indicated TCI state ID is DL TCI state, 7-bits length TCI state ID, i.e. *TCI-StateId*, as specified in TS 38.331 [5] is used. If the indicated TCI state ID is UL TCI state, the most significant bit of TCI state ID is considered as the reserved bit and remainder 6 bits indicate the *TCI-UL-State-Id* as specified in TS 38.331 [5]. TCI state IDs are in the order of indication of $F_{ij}$ and $S_{ij}$ fields. The maximum number of activated TCI states is 32; +- R: Reserved bit, set to 0. + +![](fb00a9ea622a6fe32404236fbf9b1b6a_img.jpg) + +| | | | | | | | | | | +|-----------|-----------------|-----------|-----------|-----------|-----------|-----------|-----------|--|---------| +| | | | | | | | | | | +| R | Serving Cell ID | | | | | | DL BWP ID | | Oct 1 | +| R | R | R | R | R | R | UL BWP ID | | | Oct 2 | +| $F_{1,1}$ | $F_{1,2}$ | $S_{1,1}$ | $S_{1,2}$ | $F_{2,1}$ | $F_{2,2}$ | $S_{2,1}$ | $S_{2,2}$ | | Oct 3 | +| $F_{3,1}$ | $F_{3,2}$ | $S_{3,1}$ | $S_{3,2}$ | $F_{4,1}$ | $F_{4,2}$ | $S_{4,1}$ | $S_{4,2}$ | | Oct 4 | +| $F_{5,1}$ | $F_{5,2}$ | $S_{5,1}$ | $S_{5,2}$ | $F_{6,1}$ | $F_{6,2}$ | $S_{6,1}$ | $S_{6,2}$ | | Oct 5 | +| $F_{7,1}$ | $F_{7,2}$ | $S_{7,1}$ | $S_{7,2}$ | $F_{8,1}$ | $F_{8,2}$ | $S_{8,1}$ | $S_{8,2}$ | | Oct 6 | +| R | TCI state ID 1 | | | | | | | | Oct 7 | +| R | TCI state ID 2 | | | | | | | | Oct 8 | +| ... | | | | | | | | | | +| R | TCI state ID N | | | | | | | | Oct N+6 | + +**Figure 6.1.3.71-1: Enhanced TCI state activation/deactivation MAC CE for Separate TCI States** + +## 6.1.3.72 Delay Status Report MAC CE + +The Delay Status Report (DSR) MAC CE is identified by MAC subheader with an eLCID as specified in Table 6.2.1-2b. + +The fields in the DSR MAC CE are defined as follows: + +- $LCG_i$ : This field indicates the presence of delay information (i.e. the Remaining Time and Buffer Size fields) for the LCG $i$ . The $LCG_i$ field set to 1 indicates that the delay information for the LCG $i$ is reported. The $LCG_i$ field set to 0 indicates that the delay information for the LCG $i$ is not reported; +- Remaining Time: This field indicates the shortest remaining value of PDCP *discardTimer* (described in clause 7.3 in TS 38.323 [4]) among all PDCP SDUs buffered for an LCG, at the time of the first symbol of the first + +PUSCH transmission that includes this DSR MAC CE. The length of this field is 6 bits. The value $r$ in this field indicates a remaining time within the range of $(r, r + 1]$ msec; + +- BT: This field is present only if the corresponding LCG is configured with *additionalBSR-TableAllowed*; otherwise, this field is reserved. If present, the BT field set to 1 indicates that the buffer sizes specified in Table 6.1.3.1-3 are used to set the value of the Buffer Size field, while the BT field set to 0 indicates that the buffer sizes specified in Table 6.1.3.1-2 are used instead; +- Buffer Size: The Buffer Size field indicates the total amount of delay-critical UL data for an LCG according to the data volume calculation procedure specified in clause 5.5 in TS 38.322 [3] and clause 5.6 in TS 38.323 [4] for the associated RLC and PDCP entities, respectively, after the MAC PDU has been built. If the corresponding LCG is configured with *additionalBSR-TableAllowed* and the amount of delay-critical UL data for an LCG is within the buffer sizes specified in Table 6.1.3.1-3, the MAC entity shall use the buffer sizes specified in Table 6.1.3.1-3 to set the value of this field; otherwise, the MAC entity shall use Table 6.1.3.1-2 instead. This field is indicated in number of bytes. The length of this field is 8 bits. + +The Remaining Time, the BT, and the Buffer Size fields for an LCG shall be reported in two consecutive octets. These three fields for different LCGs shall be included in a DSR MAC CE in ascending order based on the LCGi. + +![Figure 6.1.3.72-1: DSR MAC CE structure diagram. The diagram shows a sequence of octets for LCGs 7 down to 0. Octet 1 contains LCG7, LCG6, LCG5, LCG4, LCG3, LCG2, LCG1, LCG0. Octet 2 contains BT 1, R, and Remaining Time 1. Octet 3 contains Buffer Size 1. An ellipsis indicates intermediate octets. Octet 2m contains BT m, R, and Remaining Time m. Octet 2m+1 contains Buffer Size m.](b6783b3a83a0ade1dd26a3f176399cc2_img.jpg) + +| | | | | | | | | | +|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|----------| +| | | | | | | | | | +| LCG 7 | LCG 6 | LCG 5 | LCG 4 | LCG 3 | LCG 2 | LCG 1 | LCG 0 | Oct 1 | +| BT 1 | R | Remaining Time 1 | | | | | | Oct 2 | +| Buffer Size 1 | | | | | | | | Oct 3 | +| ... | | | | | | | | | +| BT m | R | Remaining Time m | | | | | | Oct 2m | +| Buffer Size m | | | | | | | | Oct 2m+1 | + +Figure 6.1.3.72-1: DSR MAC CE structure diagram. The diagram shows a sequence of octets for LCGs 7 down to 0. Octet 1 contains LCG7, LCG6, LCG5, LCG4, LCG3, LCG2, LCG1, LCG0. Octet 2 contains BT 1, R, and Remaining Time 1. Octet 3 contains Buffer Size 1. An ellipsis indicates intermediate octets. Octet 2m contains BT m, R, and Remaining Time m. Octet 2m+1 contains Buffer Size m. + +Figure 6.1.3.72-1: DSR MAC CE + +### 6.1.3.73 PSI-Based SDU Discard Activation/Deactivation MAC CE + +The PSI-Based SDU Discard Activation/Deactivation MAC CE is identified by MAC subheader with an one-octet eLCID as specified in Table 6.2.1-1b. + +It has a fixed size and consists of one octet defined as follows (Figure 6.1.3.73-1): + +- Di: This field indicates the activation/deactivation status of the PSI-based SDU discard of DRB i, where i is the ascending order of the DRB ID among the DRBs configured with PSI-based SDU discard. The Di field set to 1 indicates that the PSI-based SDU discard shall be activated for DRB i. The Di field set to 0 indicates that the PSI-based SDU discard shall be deactivated for DRB i. + +![Figure 6.1.3.73-1: PSI-based SDU Discard Activation/Deactivation MAC CE structure diagram. The diagram shows a single octet containing bits D7, D6, D5, D4, D3, D2, D1, D0.](b52be7781106e5dc2fe2720cbee7131f_img.jpg) + +| | | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-------| +| | | | | | | | | | +| D 7 | D 6 | D 5 | D 4 | D 3 | D 2 | D 1 | D 0 | Oct 1 | + +Figure 6.1.3.73-1: PSI-based SDU Discard Activation/Deactivation MAC CE structure diagram. The diagram shows a single octet containing bits D7, D6, D5, D4, D3, D2, D1, D0. + +Figure 6.1.3.73-1: PSI-based SDU Discard Activation/Deactivation MAC CE + +### 6.1.3.74 SL-PRS Resource Request MAC CE + +The SL-PRS Resource Request MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has the following fields: + +- Destination index: The Destination Index field identifies the destination. The length of this field is 5 bits. The value is set to one index corresponding to SL destination identity associated to same destination reported in *sl-PosTxResourceReqList* if present. The value is indexed sequentially from 0 in the same ascending order of SL destination identity in *sl-PosTxResourceReqList* as specified in TS 38.331 [5]. When multiple lists are reported, the value is indexed sequentially across all the lists in the same order as presented in *SidelinkUEInformationNR* message; +- Priority: Priority of pending SL-PRS transmission. The length of this field is 3 bits. + +![Diagram of SL-PRS Resource Request MAC control element structure. It shows a series of rows, each containing 'Destination index' (5 bits) and 'SL-PRS priority' (3 bits). The rows are labeled Oct 1, Oct 2, ..., Oct N. Above the first row, there are 8 empty boxes representing the MAC header fields.](a194ad55e5e2b04f07456c3c728fae88_img.jpg) + +| | | | | | | | | +|--------------------------------|-----------------|-------|--|--|--|--|--| +| | | | | | | | | +| Destination index 1 | SL-PRS priority | Oct 1 | | | | | | +| Destination index 2 | SL-PRS priority | Oct 2 | | | | | | +| ... | | | | | | | | +| Destination index N | SL-PRS priority | Oct N | | | | | | + +Diagram of SL-PRS Resource Request MAC control element structure. It shows a series of rows, each containing 'Destination index' (5 bits) and 'SL-PRS priority' (3 bits). The rows are labeled Oct 1, Oct 2, ..., Oct N. Above the first row, there are 8 empty boxes representing the MAC header fields. + +Figure 6.1.3.74-1: SL-PRS Resource Request MAC control element + +### 6.1.3.75 LTM Cell Switch Command MAC CE + +The LTM Cell Switch Command MAC CE is identified by MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size with following fields (Figure 6.1.3.75-1): + +- R: Reserved bit, set to 0; +- Target Configuration ID: This field indicates the index of candidate target configuration to apply for LTM cell switch, corresponding to *ltm-CandidateId* minus 1 as specified in TS 38.331 [5]. The length of the field is 3 bits; +- Timing Advance Command: This field indicates whether the TA is valid for the LTM target cell (i.e. the SpCell corresponding to the target configuration indicated by Target Configuration ID field). If the value of this field is set to FFF, this field indicates that no valid timing adjustment is available for the PTAG of the LTM target cell; Otherwise, this field indicates the index value $T_A$ used to control the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6], and that the UE can skip the Random Access procedure for this LTM cell switch. The length of the field is 12 bits; +- TCI state ID: This field indicates and activates the TCI state for the LTM target cell (i.e. the SpCell of the target configuration indicated by the Target Configuration ID field). The TCI state is identified by *TCI-StateId* in *ltm-DL-OrJointTCI-StateToAddModList* as specified in TS 38.331 [5]. If the value of *unifiedTCI-StateType* in the configuration indicated by Target Configuration ID field is *joint*, this field is for joint TCI state, otherwise, this field is for downlink TCI state. The length of the field is 7 bits; +- UL TCI state ID: This field indicates and activates the uplink TCI state for the LTM target cell (i.e. the SpCell of the target configuration indicated by the Target Configuration ID field). The most significant bits of UL TCI state ID are considered as reserved bits and the remainder 6 bits indicate the *TCI-UL-StateId* in *ltm-UL-TCI-StatesToAddModList* as specified in TS 38.331 [5]. This field is included if the value of *unifiedTCI-StateType* in the configuration indicated by Target Configuration ID field is *separate*. The length of the field is 8 bits; +- C: This field indicates the presence of the contention-free Random Access Resources fields. If the value of this field is set to 1, the following fields are present, including Random Access Preamble index field, S/U field, SS/PBCH index field and PRACH Mask index field. If the value of this field is set to 0, Random Access Preamble index field, SS/PBCH index field and PRACH Mask index field are absent, and S/U field is considered as Reserved field. + +- S/U: This field indicates which UL carrier to transmit the PRACH of the contention-free Random Access Resources. If the value of this field is set to 1, SUL is used; otherwise, NUL is used. The length of the field is 1 bit; +- Random Access Preamble index: This field indicates the Random Access Preamble index of the contention-free Random Access Resources. The length of the field is 6 bits; +- SS/PBCH index: This field indicates the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission of the contention-free Random Access Resources. The length of the field is 6 bits; +- PRACH Mask index: This field indicates the RACH occasion(s) associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH transmission of the contention-free Random Access Resources, referring to the *rach-ConfigDedicated* (if not provided otherwise to the *rach-ConfigCommon*) in the UL BWP configuration of *firstActiveUplinkBWP-Id* as specified in TS 38.331 [5]. The length of the field is 4 bits. + +![Diagram of LTM Cell Switch Command MAC CE structure showing 8 octets. Octet 1: R R R C S/U Target Config ID. Octet 2: R R R R Timing Advance Command. Octet 3: Timing Advance Command. Octet 4: R TCI state ID. Octet 5: UL TCI state ID. Octet 6: Random Access Preamble index SS/PBCH index. Octet 7: SS/PBCH index PRACH Mask index.](32b4e4122da4364a971829ca7166556e_img.jpg) + +| | | | | | | | | | +|------------------------------|--------------|---|------------------|------------------------|------------------|--|--|-------| +| | | | | | | | | | +| R | R | R | C | S/U | Target Config ID | | | Oct 1 | +| R | R | R | R | Timing Advance Command | | | | Oct 2 | +| Timing Advance Command | | | | | | | | Oct 3 | +| R | TCI state ID | | | | | | | Oct 4 | +| UL TCI state ID | | | | | | | | Oct 5 | +| Random Access Preamble index | | | | SS/PBCH index | | | | Oct 6 | +| SS/PBCH index | | | PRACH Mask index | | | | | Oct 7 | + +Diagram of LTM Cell Switch Command MAC CE structure showing 8 octets. Octet 1: R R R C S/U Target Config ID. Octet 2: R R R R Timing Advance Command. Octet 3: Timing Advance Command. Octet 4: R TCI state ID. Octet 5: UL TCI state ID. Octet 6: Random Access Preamble index SS/PBCH index. Octet 7: SS/PBCH index PRACH Mask index. + +Figure 6.1.3.75-1: LTM Cell Switch Command MAC CE + +### 6.1.3.76 Candidate Cell TCI States Activation/Deactivation MAC CE + +The Candidate Cell TCI States Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of following fields: + +- Candidate Cell ID: This field indicates the identity of an LTM candidate cell for which the MAC CE applies, corresponding to the *ltm-CandidateId* minus 1 as specified in TS 38.331 [5]. The length of the field is 3 bits; +- $P_i$ : This field indicates whether each TCI codepoint has multiple TCI states or a single TCI state. If the $P_i$ field is set to 1, the $i^{\text{th}}$ TCI codepoint includes the DL TCI state and the UL TCI state. If the $P_i$ field is set to 0, the $i^{\text{th}}$ TCI codepoint includes only the DL/joint TCI state or the UL TCI state. The codepoint to which a TCI state is mapped is determined by its ordinal position among all the TCI state ID fields; +- D/U: This field indicates whether the TCI state ID in the same octet is for a joint/downlink or an uplink TCI state. If this field is set to 1, the TCI state ID in the same octet is for joint/downlink TCI state. If this field is set to 0, the TCI state ID in the same octet is for uplink TCI state; +- TCI state ID: This field indicates the TCI state identified by *TCI-StateId* in *ltm-DL-OrJointTCI-StateToAddModList* or *TCI-UL-StateId* in *ltm-UL-TCI-StatesToAddModList* as specified in TS 38.331 [5]. If D/U is set to 1, 7-bits length TCI state ID i.e. *TCI-StateId* as specified in TS 38.331 [5] is used. If D/U is set to 0, the most significant bit of TCI state ID is considered as the reserved bit and remaining 6 bits indicate the *TCI-UL-StateId* as specified in TS 38.331 [5]. The maximum number of activated TCI states is 16; +- R: Reserved bit, set to 0. + +| | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|-------------------|----------------|----------------| +| | | | | | | | | +| R | R | R | R | R | Candidate Cell ID | | | +| P 1 | P 2 | P 3 | P 4 | P 5 | P 6 | P 7 | P 8 | +| D/U | TCI state ID 1 | | | | | | | +| D/U | TCI state ID 2 | | | | | | | +| ... | | | | | | | | +| D/U | TCI state ID N | | | | | | | + +**Figure 6.1.3.76-1: Candidate Cell TCI state activation/deactivation MAC CE** + +### 6.1.3.77 Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE + +The Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a fixed size of 24 bits with following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2*, respectively; +- CORESET ID: This field indicates a Control Resource Set identified with *ControlResourceSetId* as specified in TS 38.331 [5], for which the TCI State is being indicated. In case the value of the field is 0, the field refers to the Control Resource Set configured by *controlResourceSetZero* as specified in TS 38.331 [5]. The length of the field is 4 bits; +- TCI State ID: This field indicates the TCI state identified by *TCI-StateId* as specified in TS 38.331 [5] applicable to the Control Resource Set identified by CORESET ID field. If the field of CORESET ID is set to 0, this field indicates a *TCI-StateId* for a TCI state of the first 64 TCI-states configured by *tci-StatesToAddModList* and *tci-StatesToReleaseList* in the *PDSCH-Config* in the active BWP. If the field of CORESET ID is set to the other value than 0, this field indicates a *TCI-StateId* configured by *tci-StatesPDCCH-ToAddList* and *tci-StatesPDCCH-ToReleaseList* in the *controlResourceSet* identified by the indicated CORESET ID. The length of the field is 7 bits; +- Cross RRH Indicator: This field indicates whether the lower layers follow TCI state switching delay requirements in high speed train FR2 scenarios and apply the one shot large UL timing adjustment after switching to a TCI state identified by *TCI-StateId* as specified in TS 38.331 [5]. The field is set to 1 to indicate that the lower layers apply the TCI state switching delay requirements specified in Clause 8.10.3A of TS 38.133 [11] and apply the one shot large timing adjustment requirements specified in Clause 7.1.2.3 of TS 38.133 [11] immediately to the first UL transmission after TCI state switch without checking the DL timing difference threshold. The field is set to 0 to indicate that the lower layers apply the TCI state switching delay requirements specified in clause 8.10.3 of TS 38.133 [11] and apply the gradual timing adjustment requirements specified in Clause 7.1.2.1 of TS 38.133 [11] to the first UL transmission after TCI state switch without evaluating the DL timing difference. The length of the field is 1 bit; +- R: Reserved bit, set to 0. + +![Figure 6.1.3.77-1: Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE. The diagram shows three octets (Oct 1, Oct 2, Oct 3) of the MAC CE structure. Oct 1 contains 'Serving Cell ID' (6 bits) and 'CORESET ID' (2 bits). Oct 2 contains 'CORE SET ID' (3 bits) and 'TCI State ID' (5 bits). Oct 3 contains seven 'R' (Reserved) bits and a 'Cross RRH Indicator' bit.](d1203e87a330a98abf08c99d65e5a24b_img.jpg) + +| | | | | | | | | | +|-----------------|--------------|---|---|------------|---|---|---------------------|-------| +| | | | | | | | | | +| Serving Cell ID | | | | CORESET ID | | | | Oct 1 | +| CORE SET ID | TCI State ID | | | | | | | Oct 2 | +| R | R | R | R | R | R | R | Cross RRH Indicator | Oct 3 | + +Figure 6.1.3.77-1: Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE. The diagram shows three octets (Oct 1, Oct 2, Oct 3) of the MAC CE structure. Oct 1 contains 'Serving Cell ID' (6 bits) and 'CORESET ID' (2 bits). Oct 2 contains 'CORE SET ID' (3 bits) and 'TCI State ID' (5 bits). Oct 3 contains seven 'R' (Reserved) bits and a 'Cross RRH Indicator' bit. + +Figure 6.1.3.77-1: Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE + +### 6.1.3.78 Single Entry PHR with assumed PUSCH MAC CE + +The Single Entry PHR with assumed PUSCH MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2. + +It has a fixed size and consists of three octets defined as follows (Figure 6.1.3.8-1): + +- R: Reserved bit, set to 0; +- Power Headroom (PH): This field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 below (the corresponding measured values in dB are specified in TS 38.133 [11]); +- E: This field indicates the presence of a $P_{\text{CMAX,fc}}$ for assumed PUSCH field for PCell. The E field set to 1 indicates that a $P_{\text{CMAX,fc}}$ for assumed PUSCH field for PCell is reported. The E field set to 0 indicates that a $P_{\text{CMAX,fc}}$ for assumed PUSCH field for PCell is not reported; +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding $P_{\text{CMAX,fc}}$ field would have had a different value if no power backoff due to power management had been applied; +- $P_{\text{CMAX,fc}}$ : This field indicates the $P_{\text{CMAX,fc}}$ (as specified in TS 38.213 [6]) used for calculation of the preceding PH field. The reported $P_{\text{CMAX,fc}}$ and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm are specified in TS 38.133 [11]); +- $P_{\text{CMAX,fc}}$ for assumed PUSCH: This field indicates the $P_{\text{CMAX,fc}}$ for assumed PUSCH (as specified in TS 38.213 [6]). The reported $P_{\text{CMAX,fc}}$ and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm are specified in TS 38.133 [11]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits are present instead. + +![Figure 6.1.3.78-1: Single Entry PHR with assumed PUSCH MAC CE. The diagram shows three octets (Oct 1, Oct 2, Oct 3) of the MAC CE structure. Oct 1 contains 'P' (1 bit), 'E' (1 bit), and 'PH (Type 1, PCell)' (6 bits). Oct 2 contains 'MPE or R' (2 bits) and 'P_CMAX,fc' (6 bits). Oct 3 contains two 'R' (Reserved) bits and 'P_CMAX,fc (assumed PUSCH)' (6 bits).](761efbc82a397a77e5e4a0afc95a3d44_img.jpg) + +| | | | | | | | | | +|----------|---|--------------------------------------|--|--|--|--|--|-------| +| | | | | | | | | | +| P | E | PH (Type 1, PCell) | | | | | | Oct 1 | +| MPE or R | | $P_{\text{CMAX,fc}}$ | | | | | | Oct 2 | +| R | R | $P_{\text{CMAX,fc}}$ (assumed PUSCH) | | | | | | Oct 3 | + +Figure 6.1.3.78-1: Single Entry PHR with assumed PUSCH MAC CE. The diagram shows three octets (Oct 1, Oct 2, Oct 3) of the MAC CE structure. Oct 1 contains 'P' (1 bit), 'E' (1 bit), and 'PH (Type 1, PCell)' (6 bits). Oct 2 contains 'MPE or R' (2 bits) and 'P\_CMAX,fc' (6 bits). Oct 3 contains two 'R' (Reserved) bits and 'P\_CMAX,fc (assumed PUSCH)' (6 bits). + +Figure 6.1.3.78-1: Single Entry PHR with assumed PUSCH MAC CE + +### 6.1.3.79 Multiple Entry PHR with assumed PUSCH MAC CE + +The Multiple Entry PHR with assumed PUSCH MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-2. + +It has a variable size, and includes the bitmap, a Type 2 PH field, an octet containing the associated $P_{\text{CMAX,fc}}$ field (if reported) and an octet containing the associated $P_{\text{CMAX,fc}}$ field for assumed PUSCH (if reported) for SpCell of the other MAC entity; a Type 1 PH field, an octet containing the associated $P_{\text{CMAX,fc}}$ field (if reported) and an octet containing the associated $P_{\text{CMAX,fc}}$ field for assumed PUSCH (if reported) for the PCell. It further includes, in ascending order based on the *ServCellIndex*, one or multiple of Type X PH fields, octets containing the associated $P_{\text{CMAX,fc}}$ fields (if reported) and octets containing the associated $P_{\text{CMAX,fc}}$ fields for assumed PUSCH (if reported) for Serving Cells other than PCell indicated in the bitmap. X is either 1 or 3 according to TS 38.213 [6] and TS 36.213 [17]. + +The presence of Type 2 PH field for SpCell of the other MAC entity is configured by *phr-Type2OtherCell* with value *true*. + +A single octet bitmap is used for indicating the presence of PH per Serving Cell when the highest *ServCellIndex* of Serving Cell with configured uplink is less than 8, otherwise four octets are used. + +The MAC entity determines whether PH value for an activated Serving Cell is based on real transmission or a reference format by considering the configured grant(s) and downlink control information which has been received until and including the PDCCH occasion in which the first UL grant for a new transmission that can accommodate the MAC CE for PHR as a result of LCP as defined in clause 5.4.3.1 is received since a PHR has been triggered if the PHR MAC CE is reported on an uplink grant received on the PDCCH or until the first uplink symbol of PUSCH transmission minus PUSCH preparation time as defined in clause 7.7 of TS 38.213 [6] if the PHR MAC CE is reported on a configured grant. + +For a band combination in which the UE does not support dynamic power sharing, the UE may omit the octets containing Power Headroom field and $P_{\text{CMAX,fc}}$ field for Serving Cells in the other MAC entity except for the PCell in the other MAC entity and the reported values of Power Headroom and $P_{\text{CMAX,fc}}$ for the PCell are up to UE implementation. + +The PHR MAC CEs are defined as follows: + +- $C_i$ : This field indicates the presence of a PH field for the Serving Cell with *ServCellIndex* i as specified in TS 38.331 [5]. The $C_i$ field set to 1 indicates that a PH field for the Serving Cell with *ServCellIndex* i is reported. The $C_i$ field set to 0 indicates that a PH field for the Serving Cell with *ServCellIndex* i is not reported; +- $E_i$ : This field indicates the presence of a $P_{\text{CMAX,fc}}$ for assumed PUSCH field for the Serving Cell with *ServCellIndex* i as specified in TS 38.331 [5]. The $E_i$ field set to 1 indicates that a $P_{\text{CMAX,fc}}$ for assumed PUSCH field for the Serving Cell with *ServCellIndex* i is reported. The $E_i$ field set to 0 indicates that a $P_{\text{CMAX,fc}}$ for assumed PUSCH field for the Serving Cell with *ServCellIndex* i is not reported. For the E-UTRA Serving Cell, the corresponding $E_i$ field is set to 0; +- R: Reserved bit, set to 0; +- V: This field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, the V field set to 0 indicates real transmission on PUSCH and the V field set to 1 indicates that a PUSCH reference format is used. For Type 2 PH, the V field set to 0 indicates real transmission on PUCCH and the V field set to 1 indicates that a PUCCH reference format is used. For Type 3 PH, the V field set to 0 indicates real transmission on SRS and the V field set to 1 indicates that an SRS reference format is used. Furthermore, for Type 1, Type 2, and Type 3 PH, the V field set to 0 indicates the presence of the octet containing the associated $P_{\text{CMAX,fc}}$ field and the MPE field, and the V field set to 1 indicates that the octet containing the associated $P_{\text{CMAX,fc}}$ field and the MPE field is omitted; +- Power Headroom (PH): This field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.8-1 (the corresponding measured values in dB for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dB for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- P: If *mpe-Reporting-FR2* is configured and the Serving Cell operates on FR2, the MAC entity shall set this field to 0 if the applied P-MPR value, to meet MPE requirements, as specified in TS 38.101-2 [15], is less than P-MPR\_00 as specified in TS 38.133 [11] and to 1 otherwise. If *mpe-Reporting-FR2* is not configured or the Serving Cell operates on FR1, this field indicates whether power backoff is applied due to power management + +(as allowed by P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set the P field to 1 if the corresponding PCMAX,fc field would have had a different value if no power backoff due to power management had been applied; + +- PCMAX,fc: If present, this field indicates the PCMAX,fc (as specified in TS 38.213 [6]) for the NR Serving Cell and the PCMAX,c or PCMAX,c (as specified in TS 36.213 [17]) for the E-UTRA Serving Cell used for calculation of the preceding PH field. The reported PCMAX,fc and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.8-2 (the corresponding measured values in dBm for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding measured values in dBm for the E-UTRA Serving Cell are specified in TS 36.133 [12]); +- PCMAX,fc for assumed PUSCH: If present, this field indicates the PCMAX,fc for assumed PUSCH (as specified in TS 38.213 [6]) for the NR Serving Cell. The reported PCMAX,fc and the corresponding nominal UE transmit power levels are shown in [Table 6.1.3.8-2] (the corresponding measured values in dBm for the NR Serving Cell are specified in TS 38.133 [11]); +- MPE: If *mpe-Reporting-FR2* is configured, and the Serving Cell operates on FR2, and if the P field is set to 1, this field indicates the applied power backoff to meet MPE requirements, as specified in TS 38.101-2 [15]. This field indicates an index to Table 6.1.3.8-3 and the corresponding measured values of P-MPR levels in dB are specified in TS 38.133 [11]. The length of the field is 2 bits. If *mpe-Reporting-FR2* is not configured, or if the Serving Cell operates on FR1, or if the P field is set to 0, R bits are present instead. + +| | | | | | | | | +|----------------|----------------|---------------------------------------------|----------------|----------------|----------------|----------------|----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | +| E 7 | E 6 | E 5 | E 4 | E 3 | E 2 | E 1 | E 0 | +| P | V | PH (Type 2, SpCell of the other MAC entity) | | | | | | +| MPE or R | | P CMAX,fc 1 | | | | | | +| P | V | PH (Type 1, PCell) | | | | | | +| MPE or R | | P CMAX,fc 2 | | | | | | +| R | R | P CMAX,fc 2 (assumed PUSCH) | | | | | | +| P | V | PH (Type X, Serving Cell 1) | | | | | | +| MPE or R | | P CMAX,fc 3 | | | | | | +| R | R | P CMAX,fc 3 (assumed PUSCH) | | | | | | +| ... | | | | | | | | +| P | V | PH (Type X, Serving Cell n) | | | | | | +| MPE or R | | P CMAX,fc m | | | | | | +| R | R | P CMAX,fc m (assumed PUSCH) | | | | | | + +Figure 6.1.3.79-1: Multiple Entry PHR with assumed PUSCH MAC CE with the highest *ServCellIndex* of Serving Cell with configured uplink is less than 8 + +| | | | | | | | | +|-----------------|-----------------|---------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | | | | | +| C 7 | C 6 | C 5 | C 4 | C 3 | C 2 | C 1 | R | +| C 15 | C 14 | C 13 | C 12 | C 11 | C 10 | C 9 | C 8 | +| C 23 | C 22 | C 21 | C 20 | C 19 | C 18 | C 17 | C 16 | +| C 31 | C 30 | C 29 | C 28 | C 27 | C 26 | C 25 | C 24 | +| E 7 | E 6 | E 5 | E 4 | E 3 | E 2 | E 1 | E 0 | +| E 15 | E 14 | E 13 | E 12 | E 11 | E 10 | E 9 | E 8 | +| E 23 | E 22 | E 21 | E 20 | E 19 | E 18 | E 17 | E 16 | +| E 31 | E 30 | E 29 | E 28 | E 27 | E 26 | E 25 | E 24 | +| P | V | PH (Type 2, SpCell of the other MAC entity) | | | | | | +| MPE or R | | P CMAX,f,c 1 | | | | | | +| P | V | PH (Type 1, PCell) | | | | | | +| MPE or R | | P CMAX,f,c 2 | | | | | | +| R | R | P CMAX,f,c 2 (assumed PUSCH) | | | | | | +| P | V | PH (Type X, Serving Cell 1) | | | | | | +| MPE or R | | P CMAX,f,c 3 | | | | | | +| R | R | P CMAX,f,c 3 (assumed PUSCH) | | | | | | +| ... | | | | | | | | +| P | V | PH (Type X, Serving Cell n) | | | | | | +| MPE or R | | P CMAX,f,c m | | | | | | +| R | R | P CMAX,f,c m (assumed PUSCH) | | | | | | + +**Figure 6.1.3.79-2: Multiple Entry PHR with assumed PUSCH MAC CE with the highest ServCellIndex of Serving Cell with configured uplink is equal to or higher than 8** + +### 6.1.3.80 Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE + +The enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE is identified by a MAC subheader with eLCID as specified in Table 6.2.1-1b. It has a variable size and consists of the following fields: + +- Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits; +- BWP ID: This field indicates a UL BWP for which the MAC CE applies as the codepoint of the DCI *bandwidth part indicator* field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits; +- $S_i$ : This field indicates the activation/deactivation status of the Semi-Persistent CSI report configuration within *csi-ReportConfigToAddModList*, as specified in TS 38.331 [5]. $S_0$ refers to the report configuration which includes PUCCH resources for SP CSI reporting in the indicated BWP and has the lowest *CSI-ReportConfigId* within the list with type set to *semiPersistentOnPUCCH*, $S_1$ to the report configuration which includes PUCCH resources for SP CSI reporting in the indicated BWP and has the second lowest *CSI-ReportConfigId* and so on. If the number of report configurations within the list with type set to *semiPersistentOnPUCCH* in the indicated BWP is less than $i + 1$ , MAC entity shall ignore the $S_i$ field. The $S_i$ field is set to 1 to indicate that the corresponding Semi-Persistent CSI report configuration shall be activated. The $S_i$ field is set to 0 to indicate that the corresponding Semi-Persistent CSI report configuration $i$ shall be deactivated; +- $N_{i,x}$ : this field indicates the activation/deactivation status of the Semi-Persistent CSI report SubConfiguration $x$ within *csi-ReportSubConfigList* of *CSI-ReportConfigId* $i$ , as specified in TS 38.331 [5]. If $S_i$ set to 1, the octet corresponding to $N_{i,0}$ to $N_{i,7}$ is present. If $S_i$ set to 0, the octet corresponding to $N_{i,0}$ to $N_{i,7}$ is not present. $N_{0,0}$ refers to the report SubConfiguration which has the lowest *csi-ReportSubConfigID* within the list, $N_{0,1}$ to the report SubConfiguration which has the second lowest *csi-ReportSubConfigID* and so on. If the number of report SubConfigurations within the list with type set to *csi-ReportSubConfigList* in the indicated BWP is less than $x + 1$ , the MAC entity shall ignore the $N_{i,x}$ field. The $N_{i,x}$ field is set to 1 to indicate that the corresponding Semi-Persistent CSI report SubConfiguration $x$ shall be activated. The $N_{i,x}$ field is set to 0 to indicate that the corresponding Semi-Persistent CSI report SubConfiguration $x$ shall be deactivated; +- R: Reserved bit, set to 0. + +| | | | | | | | | | +|-----------|-----------------|-----------|-----------|-----------|-----------|-----------|-----------|---------------------| +| | | | | | | | | | +| R | Serving Cell ID | | | | BWP ID | | | Oct 1 | +| R | R | R | R | $S_3$ | $S_2$ | $S_1$ | $S_0$ | Oct 2 | +| $N_{0,7}$ | $N_{0,6}$ | $N_{0,5}$ | $N_{0,4}$ | $N_{0,3}$ | $N_{0,2}$ | $N_{0,1}$ | $N_{0,0}$ | Oct 3
(Optional) | +| $N_{1,7}$ | $N_{1,6}$ | $N_{1,5}$ | $N_{1,4}$ | $N_{1,3}$ | $N_{1,2}$ | $N_{1,1}$ | $N_{1,0}$ | Oct 4
(Optional) | +| $N_{2,7}$ | $N_{2,6}$ | $N_{2,5}$ | $N_{2,4}$ | $N_{2,3}$ | $N_{2,2}$ | $N_{2,1}$ | $N_{2,0}$ | Oct 5
(Optional) | +| $N_{3,7}$ | $N_{3,6}$ | $N_{3,5}$ | $N_{3,4}$ | $N_{3,3}$ | $N_{3,2}$ | $N_{3,1}$ | $N_{3,0}$ | Oct 6
(Optional) | + +Figure 6.1.3.80-1: Enhanced SP CSI reporting on PUCCH Activation/Deactivation MAC CE + +### 6.1.4 MAC PDU (transparent MAC) + +A MAC PDU consists solely of a MAC SDU whose size is aligned to a TB; as described in Figure 6.1.4-1. This MAC PDU is used for transmissions on PCH, BCH, DL-SCH including BCCH, and SL-BCH. + +![Diagram showing a MAC SDU block with a double-headed arrow below it labeled MAC PDU, indicating the entire block is the PDU.](95468bd1e191c4b5b2f6382f413b175e_img.jpg) + +Diagram showing a MAC SDU block with a double-headed arrow below it labeled MAC PDU, indicating the entire block is the PDU. + +Figure 6.1.4-1: Example of MAC PDU (transparent MAC) + +### 6.1.5 MAC PDU (Random Access Response) + +A MAC PDU consists of one or more MAC subPDUs and optionally padding. Each MAC subPDU consists one of the following: + +- a MAC subheader with Backoff Indicator only; +- a MAC subheader with RAPID only (i.e. acknowledgment for SI request); +- a MAC subheader with RAPID and MAC RAR. + +A MAC subheader with Backoff Indicator consists of five header fields E/T/R/R/BI as described in Figure 6.1.5-1. A MAC subPDU with Backoff Indicator only is placed at the beginning of the MAC PDU, if included. 'MAC subPDU(s) with RAPID only' and 'MAC subPDU(s) with RAPID and MAC RAR' can be placed anywhere between MAC subPDU with Backoff Indicator only (if any) and padding (if any). + +A MAC subheader with RAPID consists of three header fields E/T/RAPID as described in Figure 6.1.5-2. + +Padding is placed at the end of the MAC PDU if present. Presence and length of padding is implicit based on TB size, size of MAC subPDU(s). + +![Figure 6.1.5-1: E/T/R/R/BI MAC subheader diagram. It shows a header with five fields: E, T, R, R, and BI. Above the header is a row of eight small boxes. To the right of the header is the text 'Oct 1'.](4a68079a30c96e3aa582574ebc524e46_img.jpg) + +Figure 6.1.5-1: E/T/R/R/BI MAC subheader diagram. It shows a header with five fields: E, T, R, R, and BI. Above the header is a row of eight small boxes. To the right of the header is the text 'Oct 1'. + +Figure 6.1.5-1: E/T/R/R/BI MAC subheader + +![Figure 6.1.5-2: E/T/RAPID MAC subheader diagram. It shows a header with three fields: E, T, and RAPID. Above the header is a row of eight small boxes. To the right of the header is the text 'Oct 1'.](340e10d75c9e473c73f2f1f9037d8afc_img.jpg) + +Figure 6.1.5-2: E/T/RAPID MAC subheader diagram. It shows a header with three fields: E, T, and RAPID. Above the header is a row of eight small boxes. To the right of the header is the text 'Oct 1'. + +Figure 6.1.5-2: E/T/RAPID MAC subheader + +![Figure 6.1.5-3: Example of MAC PDU consisting of MAC RARs. This diagram shows the structure of a MAC PDU. At the top, three subheader types are shown: 'E/T/R/R/BI subheader', 'E/T/RAPID subheader', and another 'E/T/RAPID subheader' followed by 'MAC RAR'. Below this, a sequence of MAC subPDUs is shown: 'MAC subPDU 1 (BI only)', 'MAC subPDU 2 (RAPID only)', 'MAC subPDU 3 (RAPID and RAR)', 'MAC subPDU 4', an ellipsis, 'MAC subPDU n', and finally 'Padding (opt)'. Dashed lines connect the subheader types at the top to the corresponding MAC subPDUs below: the first subheader to MAC subPDU 1, the second to MAC subPDU 2, and the third (subheader + RAR) to MAC subPDU 3.](39d46d66998e38df22b80b0317aa58b6_img.jpg) + +Figure 6.1.5-3: Example of MAC PDU consisting of MAC RARs. This diagram shows the structure of a MAC PDU. At the top, three subheader types are shown: 'E/T/R/R/BI subheader', 'E/T/RAPID subheader', and another 'E/T/RAPID subheader' followed by 'MAC RAR'. Below this, a sequence of MAC subPDUs is shown: 'MAC subPDU 1 (BI only)', 'MAC subPDU 2 (RAPID only)', 'MAC subPDU 3 (RAPID and RAR)', 'MAC subPDU 4', an ellipsis, 'MAC subPDU n', and finally 'Padding (opt)'. Dashed lines connect the subheader types at the top to the corresponding MAC subPDUs below: the first subheader to MAC subPDU 1, the second to MAC subPDU 2, and the third (subheader + RAR) to MAC subPDU 3. + +Figure 6.1.5-3: Example of MAC PDU consisting of MAC RARs + +### 6.1.5a MAC PDU (MSGb) + +A MAC PDU consists of one or more MAC subPDUs and optionally padding. Each MAC subPDU consists one of the following: + +- a MAC subheader with Backoff Indicator only; +- a MAC subheader and fallbackRAR; +- a MAC subheader and successRAR; +- a MAC subheader and MAC SDU for CCCH, DCCH or DTCH; +- a MAC subheader and padding. + +A MAC subheader with Backoff Indicator consists of five header fields E/T1/T2/R/BI as described in Figure 6.1.5a-1. A MAC subPDU with Backoff Indicator only is placed at the beginning of the MAC PDU, if included. + +A MAC subheader for fallbackRAR consists of three header fields E/T1/RAPID as described in Figure 6.1.5a-2. A MAC subheader for successRAR consists of eight header fields E/T1/T2/S/R/R/R/R as described in Figure 6.1.5a-3. A MAC subheader for MAC SDU consists of the four header fields R/F/LCID/L as described in Figure 6.1.2-1 and Figure 6.1.2-2. + +At most one 'MAC subPDU for successRAR' indicating presence of 'MAC subPDU(s) for MAC SDU' is included in a MAC PDU. MAC subPDU(s) for MAC SDU are placed immediately after the 'MAC subPDU for successRAR' indicating presence of 'MAC subPDU(s) for MAC SDU'. + +If MAC PDU includes MAC subPDU(s) for MAC SDU, the last MAC subPDU for MAC SDU is placed before MAC subPDU with padding as depicted in Figure 6.1.5a-4. Otherwise, the last MAC subPDU in MAC PDU is placed before padding as depicted in Figure 6.1.5a-5. The MAC subPDU with padding includes R/R/LCID MAC subheader as described in Figure 6.1.2-3 and padding. The size of padding in the MAC subPDU with padding can be zero. The length of padding is implicit based on TB size, size of MAC subPDU(s). + +![Figure 6.1.5a-1: BI MAC subheader diagram showing fields E, T1, T2, R, and BI within an Octet 1 structure.](78ecffc23b5831341cca689039041918_img.jpg) + +| | | | | | | | | +|---|----|----|---|----|--|--|-------| +| | | | | | | | | +| E | T1 | T2 | R | BI | | | Oct 1 | + +Figure 6.1.5a-1: BI MAC subheader diagram showing fields E, T1, T2, R, and BI within an Octet 1 structure. + +Figure 6.1.5a-1: BI MAC subheader + +![Figure 6.1.5a-2: FallbackRAR MAC subheader diagram showing fields E, T1, and RAPID within an Octet 1 structure.](76aaf09224a8270997539c0939061af7_img.jpg) + +| | | | | | | | | +|---|----|-------|--|--|--|--|-------| +| | | | | | | | | +| E | T1 | RAPID | | | | | Oct 1 | + +Figure 6.1.5a-2: FallbackRAR MAC subheader diagram showing fields E, T1, and RAPID within an Octet 1 structure. + +Figure 6.1.5a-2: FallbackRAR MAC subheader + +![Figure 6.1.5a-3: SuccessRAR MAC subheader diagram showing fields E, T1, T2, S, R, R, R, and R within an Octet 1 structure.](9d05fd876dc28e2fc2d83e9495144a4d_img.jpg) + +| | | | | | | | | +|---|----|----|---|---|---|---|-------| +| | | | | | | | | +| E | T1 | T2 | S | R | R | R | R | +| | | | | | | | Oct 1 | + +Figure 6.1.5a-3: SuccessRAR MAC subheader diagram showing fields E, T1, T2, S, R, R, R, and R within an Octet 1 structure. + +Figure 6.1.5a-3: SuccessRAR MAC subheader + +![Figure 6.1.5a-4: Example of a MSGB MAC PDU with MAC SDU(s) diagram showing the sequence of subPDUs: BI only, fallbackRAR, successRAR, MAC SDU, ..., MAC SDU, MAC subPDU including padding (opt).](298ee60b468fa168b2d31902628dc264_img.jpg) + +| | | | | | | | +|------------------------|--------------------------|-------------------------|-----------------------------|------------|----------------------|------------------------------------| +| E/T1/T2/R/BI subheader | E/T1/RAPID subheader | fallbackRAR | E/T1/T2/S/R/R/R/R subheader | successRAR | R/F/LCID/L subheader | MAC SDU | +| MAC subPDU (BI only) | MAC subPDU (fallbackRAR) | MAC subPDU (successRAR) | MAC subPDU (MAC SDU) | ... | MAC subPDU (MAC SDU) | MAC subPDU including padding (opt) | + +Figure 6.1.5a-4: Example of a MSGB MAC PDU with MAC SDU(s) diagram showing the sequence of subPDUs: BI only, fallbackRAR, successRAR, MAC SDU, ..., MAC SDU, MAC subPDU including padding (opt). + +Figure 6.1.5a-4: Example of a MSGB MAC PDU with MAC SDU(s) + +![Figure 6.1.5a-5: Example of a MSGB MAC PDU without MAC SDU(s) diagram showing the sequence of subPDUs: BI only, fallbackRAR, successRAR, (fallbackRAR or successRAR), ..., (fallbackRAR or successRAR), Padding (opt).](37f059615fb8a05f4da791eb7fde1190_img.jpg) + +| | | | | | | | +|------------------------|--------------------------|-------------------------|----------------------------------------|------------|----------------------------------------|---------------| +| E/T1/T2/R/BI subheader | E/T1/RAPID subheader | fallbackRAR | E/T1/T2/S/R/R/R/R subheader | successRAR | | | +| MAC subPDU (BI only) | MAC subPDU (fallbackRAR) | MAC subPDU (successRAR) | MAC subPDU (fallbackRAR or successRAR) | ... | MAC subPDU (fallbackRAR or successRAR) | Padding (opt) | + +Figure 6.1.5a-5: Example of a MSGB MAC PDU without MAC SDU(s) diagram showing the sequence of subPDUs: BI only, fallbackRAR, successRAR, (fallbackRAR or successRAR), ..., (fallbackRAR or successRAR), Padding (opt). + +Figure 6.1.5a-5: Example of a MSGB MAC PDU without MAC SDU(s) + +### 6.1.6 MAC PDU (SL-SCH) + +A MAC PDU consists of one SL-SCH subheader and one or more MAC subPDUs. Each MAC subPDU consists of one of the following: + +- A MAC subheader only (including padding); +- A MAC subheader and a MAC SDU; +- A MAC subheader and a MAC CE; +- A MAC subheader and padding. + +The MAC SDUs are of variable sizes. + +Each MAC subheader except SL-SCH subheader corresponds to either a MAC SDU, a MAC CE, or padding. + +The SL-SCH subheader is of a fixed size and consists of the seven header fields V/R/R/R/R/SRC/DST. + +![Diagram of SL-SCH MAC subheader structure showing fields V, R, R, R, R, SRC, and DST across four octets.](cd2dcc38fd9463990b9abcd7470b088a_img.jpg) + +| | | | | | | | | +|-----|--|--|--|---|---|---|---| +| | | | | | | | | +| V | | | | R | R | R | R | +| SRC | | | | | | | | +| DST | | | | | | | | + +Oct 1 +Oct 2 +Oct 3 +Oct 4 + +Diagram of SL-SCH MAC subheader structure showing fields V, R, R, R, R, SRC, and DST across four octets. + +Figure 6.1.6-1: SL-SCH MAC subheader + +A MAC subheader except for fixed-sized MAC CE and padding consists of the four header fields R/F/LCID/L as depicted in Figure 6.1.2-1 (with 8-bit L field) and Figure 6.1.2-2 (with 16-bit L field). A MAC subheader for fixed-sized MAC CE and padding consists of the two header fields R/LCID as depicted in Figure 6.1.2-3. + +SL MAC subPDU(s) with MAC SDU(s) is placed after the SL-SCH subheader and before the MAC subPDU with a MAC CE and the MAC subPDU with padding in the MAC PDU as depicted in Figure 6.1.6-2. SL MAC subPDU with a MAC CE is placed after all the MAC subPDU(s) with MAC SDU and before the MAC subPDU with padding in the MAC PDU as depicted in Figure 6.1.6-2. The size of padding can be zero. + +![Diagram showing the sequence of MAC subPDUs following the SL-SCH subheader: MAC SDU, MAC CE, and MAC padding.](53722b37637a6c7f2fa2a01722a164fd_img.jpg) + +| | | | | | | | | +|------------------|------------------------------|------------------------------|-----|-----------------------------|------------------------------------|--|--| +| | R/F/LCID/L subheader | MAC SDU | | | | | | +| | | | | | | | | +| SL-SCH subheader | MAC subPDU including MAC SDU | MAC subPDU including MAC SDU | ... | MAC subPDU including MAC CE | MAC subPDU including padding (opt) | | | + +Diagram showing the sequence of MAC subPDUs following the SL-SCH subheader: MAC SDU, MAC CE, and MAC padding. + +Figure 6.1.6-2: Example of an SL MAC PDU + +A maximum of one MAC PDU can be transmitted per TB per MAC entity. + +## 6.2 Formats and parameters + +### 6.2.1 MAC subheader for DL-SCH and UL-SCH + +The MAC subheader consists of the following fields: + +- LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE or padding as described in Tables 6.2.1-1 and 6.2.1-1c for the DL-SCH and Tables 6.2.1-2 and 6.2.1-2c for the UL-SCH. There is one LCID field per MAC subheader. The size of the LCID field is 6 bits. If the LCID field is set to 34 as in Table 6.2.1-1 or 6.2.1-2, one additional octet is present in the MAC subheader containing the eLCID field and follow the octet containing LCID field. If the LCID field is set to 33 as in Table 6.2.1-1 or 6.2.1-2, two additional octets are present in the MAC subheader containing the eLCID field and these two additional octets follow the octet containing LCID field; + +NOTE 1: For MBS broadcast, a logical channel is identified based on G-RNTI and LCID if the same LCID is allocated for logical channels corresponding to different G-RNTIs. + +- eLCID: The extended Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE as described in tables 6.2.1-1a, 6.2.1-1b, 6.2.1-2a and 6.2.1-2b for the DL-SCH and UL-SCH respectively. The size of the eLCID field is either 8 bits or 16 bits. + +NOTE 2: The extended Logical Channel ID space using two-octet eLCID and the relevant MAC subheader format is used, only when configured, on the NR backhaul links between IAB nodes or between IAB node and IAB Donor, or for multicast MTCHs. + +- L: The Length field indicates the length of the corresponding MAC SDU or variable-sized MAC CE in bytes. There is one L field per MAC subheader except for subheaders corresponding to fixed-sized MAC CEs, padding, and MAC SDUs containing UL CCCH. The size of the L field is indicated by the F field; +- F: The Format field indicates the size of the Length field. There is one F field per MAC subheader except for subheaders corresponding to fixed-sized MAC CEs, padding, and MAC SDUs containing UL CCCH. The size of the F field is 1 bit. The value 0 indicates 8 bits of the Length field. The value 1 indicates 16 bits of the Length field; +- LX: The LCID extension field indicates the use of extended LCID space. The size of the LX field is 1 bit. The LX field set to 1 indicates the use of Table 6.2.1-2c, otherwise R bit is present instead (i.e. set to 0); +- R: Reserved bit, set to 0. + +The MAC subheader is octet aligned. + +**Table 6.2.1-1: Values of LCID for DL-SCH** + +| Codepoint/Index | LCID values | +|-----------------|------------------------------------------------------------------| +| 0 | CCCH | +| 1–32 | Identity of the logical channel of DCCH, DTCH and multicast MTCH | +| 33 | Extended logical channel ID field (two-octet eLCID field) | +| 34 | Extended logical channel ID field (one-octet eLCID field) | +| 35–46 | Reserved | +| 47 | Recommended bit rate | +| 48 | SP ZP CSI-RS Resource Set Activation/Deactivation | +| 49 | PUCCH spatial relation Activation/Deactivation | +| 50 | SP SRS Activation/Deactivation | +| 51 | SP CSI reporting on PUCCH Activation/Deactivation | +| 52 | TCI State Indication for UE-specific PDCCH | +| 53 | TCI States Activation/Deactivation for UE-specific PDSCH | +| 54 | Aperiodic CSI Trigger State Subselection | +| 55 | SP CSI-RS/CSI-IM Resource Set Activation/Deactivation | +| 56 | Duplication Activation/Deactivation | +| 57 | SCell Activation/Deactivation (four octets) | +| 58 | SCell Activation/Deactivation (one octet) | +| 59 | Long DRX Command | +| 60 | DRX Command | +| 61 | Timing Advance Command | +| 62 | UE Contention Resolution Identity | +| 63 | Padding | + +**Table 6.2.1-1a: Values of two-octet eLCID for DL-SCH** + +| Codepoint | Index | LCID values | +|---------------------|-------------------------|---------------------------------| +| 0 to $(2^{16} - 1)$ | 320 to $(2^{16} + 319)$ | Identity of the logical channel | + +**Table 6.2.1-1b: Values of one-octet eLCID for DL-SCH** + +| Codepoint | Index | LCID values | +|-----------|-----------|--------------------------------------------------------------------------------------------| +| 0 to 216 | 64 to 280 | Reserved | +| 217 | 281 | Enhanced SP CSI reporting on PUCCH
Activation/Deactivation MAC CE | +| 218 | 282 | Cross-RRH TCI State Indication for UE-specific PDCCH MAC CE | +| 219 | 283 | LTM Cell Switch Command | +| 220 | 284 | Candidate Cell TCI States
Activation/Deactivation | +| 221 | 285 | PSI-Based SDU Discard
Activation/Deactivation MAC CE | +| 222 | 286 | Enhanced Unified TCI state
Activation/Deactivation MAC CE for Joint TCI States | +| 223 | 287 | Enhanced Unified TCI state
Activation/Deactivation MAC CE for Separate TCI States | +| 224 | 288 | NCR Access Link Beam Indication MAC CE | +| 225 | 289 | NCR Downlink Backhaul Link Beam Indication
MAC CE | +| 226 | 290 | NCR Uplink Backhaul Link Beam Indication
MAC CE | +| 227 | 291 | Serving Cell Set based SRS TCI State
Indication MAC CE | +| 228 | 292 | SP/AP SRS TCI State Indication MAC CE | +| 229 | 293 | BFD-RS Indication MAC CE | +| 230 | 294 | Differential Koffset | +| 231 | 295 | Enhanced SCell Activation/Deactivation MAC
CE with one octet C i field | +| 232 | 296 | Enhanced SCell Activation/Deactivation MAC
CE with four octet C i field | +| 233 | 297 | Unified TCI States Activation/Deactivation
MAC CE | +| 234 | 298 | PUCCH Power Control Set Update for multiple
TRP PUCCH repetition MAC CE | +| 235 | 299 | PUCCH spatial relation Activation/Deactivation
for multiple TRP PUCCH repetition MAC CE | +| 236 | 300 | Enhanced TCI States Indication for UE-specific
PDCCH | +| 237 | 301 | Positioning Measurement Gap
Activation/Deactivation Command | +| 238 | 302 | PPW Activation/Deactivation Command | +| 239 | 303 | DL Tx Power Adjustment | +| 240 | 304 | Timing Case Indication | +| 241 | 305 | Child IAB-DU Restricted Beam Indication | +| 242 | 306 | Case-7 Timing advance offset | +| 243 | 307 | Provided Guard Symbols for Case-6 timing | +| 244 | 308 | Provided Guard Symbols for Case-7 timing | +| 245 | 309 | Serving Cell Set based SRS Spatial Relation
Indication | +| 246 | 310 | PUSCH Pathloss Reference RS Update | +| 247 | 311 | SRS Pathloss Reference RS Update | +| 248 | 312 | Enhanced SP/AP SRS Spatial Relation
Indication | +| 249 | 313 | Enhanced PUCCH Spatial Relation
Activation/Deactivation | +| 250 | 314 | Enhanced TCI States Activation/Deactivation
for UE-specific PDSCH | +| 251 | 315 | Duplication RLC Activation/Deactivation | +| 252 | 316 | Absolute Timing Advance Command | +| 253 | 317 | SP Positioning SRS Activation/Deactivation | +| 254 | 318 | Provided Guard Symbols | +| 255 | 319 | Timing Delta | + +**Table 6.2.1-1c: Values of LCID for MBS multicast MCCH and MBS broadcast on DL-SCH** + +| Codepoint/Index | LCID values | +|-----------------|---------------------------------------------------| +| 0 | Broadcast MCCH or multicast MCCH | +| 1–32 | Identity of the logical channel of broadcast MTCH | +| 33–63 | Reserved | + +**Table 6.2.1-2: Values of LCID for UL-SCH when the LX field is not present or is set to 0** + +| Codepoint/Index | LCID values | +|-----------------|-----------------------------------------------------------| +| 0 | CCCH of size 64 bits, except for an (e)RedCap UE | +| 1–32 | Identity of the logical channel of DCCH and DTCH | +| 33 | Extended logical channel ID field (two-octet eLCID field) | +| 34 | Extended logical channel ID field (one-octet eLCID field) | +| 35 | CCCH of size 48 bits for a RedCap UE | +| 36 | CCCH of size 64 bits for a RedCap UE | +| 37 | SL LBT failure | +| 38–42 | Reserved | +| 43 | Truncated Enhanced BFR (one octet $C_i$ ) | +| 44 | Timing Advance Report | +| 45 | Truncated Sidelink BSR | +| 46 | Sidelink BSR | +| 47 | Reserved | +| 48 | LBT failure (four octets) | +| 49 | LBT failure (one octet) | +| 50 | BFR (one octet $C_i$ ) | +| 51 | Truncated BFR (one octet $C_i$ ) | +| 52 | CCCH of size 48 bits, except for an (e)RedCap UE | +| 53 | Recommended bit rate query | +| 54 | Multiple Entry PHR (four octets $C_i$ ) | +| 55 | Configured Grant Confirmation | +| 56 | Multiple Entry PHR (one octet $C_i$ ) | +| 57 | Single Entry PHR | +| 58 | C-RNTI | +| 59 | Short Truncated BSR | +| 60 | Long Truncated BSR | +| 61 | Short BSR | +| 62 | Long BSR | +| 63 | Padding | + +NOTE: CCCH of size 48 bits and CCCH of size 64 bits are referred to as CCCH and CCCH1, respectively, in TS 38.331 [5]. + +**Table 6.2.1-2a: Values of two-octet eLCID for UL-SCH** + +| Codepoint | Index | LCID values | +|---------------------|-------------------------|---------------------------------| +| 0 to $(2^{16} - 1)$ | 320 to $(2^{16} + 319)$ | Identity of the logical channel | + +**Table 6.2.1-2b: Values of one-octet eLCID for UL-SCH** + +| Codepoint | Index | LCID values | +|-----------|-----------|-------------------------------------------------------------------| +| 0 to 222 | 64 to 286 | Reserved | +| 223 | 287 | Multiple Entry PHR with assumed PUSCH MAC CE (four octets $C_i$ ) | +| 224 | 288 | Multiple Entry PHR with assumed PUSCH MAC CE (one octets $C_i$ ) | +| 225 | 289 | Single Entry PHR with assumed PUSCH MAC CE | +| 226 | 290 | SL-PRS Resource Request | +| 227 | 291 | Refined Long BSR | +| 228 | 292 | Delay Status Report | +| 229 | 293 | Enhanced Multiple Entry PHR for multiple TRP (four octets $C_i$ ) | +| 230 | 294 | Enhanced Multiple Entry PHR for multiple TRP (one octets $C_i$ ) | +| 231 | 295 | Enhanced Single Entry PHR for multiple TRP | +| 232 | 296 | Enhanced Multiple Entry PHR (four octets $C_i$ ) | +| 233 | 297 | Enhanced Multiple Entry PHR (one octets $C_i$ ) | +| 234 | 298 | Enhanced Single Entry PHR | +| 235 | 299 | Enhanced BFR (one octet $C_i$ ) | +| 236 | 300 | Enhanced BFR (four octet $C_i$ ) | +| 237 | 301 | Truncated Enhanced BFR (four octet $C_i$ ) | +| 238 | 302 | Positioning Measurement Gap Activation/Deactivation Request | +| 239 | 303 | IAB-MT Recommended Beam Indication | +| 240 | 304 | Desired IAB-MT PSD range | +| 241 | 305 | Desired DL Tx Power Adjustment | +| 242 | 306 | Case-6 Timing Request | +| 243 | 307 | Desired Guard Symbols for Case 6 timing | +| 244 | 308 | Desired Guard Symbols for Case 7 timing | +| 245 | 309 | Extended Short Truncated BSR | +| 246 | 310 | Extended Long Truncated BSR | +| 247 | 311 | Extended Short BSR | +| 248 | 312 | Extended Long BSR | +| 249 | 313 | Extended Pre-emptive BSR | +| 250 | 314 | BFR (four octets $C_i$ ) | +| 251 | 315 | Truncated BFR (four octets $C_i$ ) | +| 252 | 316 | Multiple Entry Configured Grant Confirmation | +| 253 | 317 | Sidelink Configured Grant Confirmation | +| 254 | 318 | Desired Guard Symbols | +| 255 | 319 | Pre-emptive BSR | + +**Table 6.2.1-2c: Values of LCID for UL-SCH when the LX field is set to 1** + +| Codepoint | Index | LCID values | +|-----------|--------------------------------------|----------------------------------------------------------------------------------------| +| 0 | $(2^{16} + 320)$ | CCCH of size 48 bits for an eRedCap UE | +| 1 | $(2^{16} + 321)$ | CCCH of size 64 bits for an eRedCap UE | +| 2 | $(2^{16} + 322)$ | CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK, except for an (e)RedCap UE | +| 3 | $(2^{16} + 323)$ | CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK, except for an (e)RedCap UE | +| 4 | $(2^{16} + 324)$ | CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK of a RedCap UE | +| 5 | $(2^{16} + 325)$ | CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK of a RedCap UE | +| 6 | $(2^{16} + 326)$ | CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK of an eRedCap UE | +| 7 | $(2^{16} + 327)$ | CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK of an eRedCap UE | +| 8 to 63 | $(2^{16} + 328)$ to $(2^{16} + 383)$ | Reserved | + +NOTE 1: The MAC entity may use the code point corresponding to a given feature or feature combination in Table 6.2.1-2c only if network indicates support for the corresponding feature or feature combination. + +NOTE 2: CCCH of size 48 bits and CCCH of size 64 bits are referred to as CCCH and CCCH1, respectively, in TS 38.331 [5]. + +## 6.2.2 MAC subheader for Random Access Response + +The MAC subheader consists of the following fields: + +- E: The Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU or not in the MAC PDU. The E field is set to 1 to indicate at least another MAC subPDU follows. The E field is set to 0 to indicate that the MAC subPDU including this MAC subheader is the last MAC subPDU in the MAC PDU; +- T: The Type field is a flag indicating whether the MAC subheader contains a Random Access Preamble ID or a Backoff Indicator. The T field is set to 0 to indicate the presence of a Backoff Indicator field in the subheader (BI). The T field is set to 1 to indicate the presence of a Random Access Preamble ID field in the subheader (RAPID); +- R: Reserved bit, set to 0; +- BI: The Backoff Indicator field identifies the overload condition in the cell. The size of the BI field is 4 bits; +- RAPID: The Random Access Preamble Identifier field identifies the transmitted Random Access Preamble (see clause 5.1.3). The size of the RAPID field is 6 bits. If the RAPID in the MAC subheader of a MAC subPDU corresponds to one of the Random Access Preambles configured for SI request, MAC RAR is not included in the MAC subPDU. + +The MAC subheader is octet aligned. + +## 6.2.2a MAC subheader for MSGB + +The MAC subheader consists of the following fields: + +- E: The Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU (other than MAC subPDU for MAC SDU) or not in the MAC PDU. The E field is set to 1 to indicate at least another MAC subPDU (other than MAC subPDU for MAC SDU) follows. The E field is set to 0 to indicate that the MAC subPDU including this MAC subheader is the last MAC subPDU (other than MAC subPDU for MAC SDU) in the MAC PDU; +- T1: The T1 field is a flag indicating whether the MAC subheader contains a Random Access Preamble ID or T2. The T1 field is set to 1 to indicate the presence of a Random Access Preamble ID field in the subheader (RAPID). The T1 field is set to 0 to indicate the presence of T2 field in the subheader; + +- T2: The T2 field is a flag indicating whether the MAC subheader contains a Backoff Indicator (BI) or a MAC SDU indicator (S). The T2 field is set to 0 to indicate the presence of a Backoff Indicator field in the subheader. The T2 field is set to 1 to indicate the presence of the S field in the subheader; +- S: This field indicates whether 'MAC subPDU(s) for MAC SDU' follow the MAC subPDU including this MAC subheader or not; The S field is set to 1 to indicate presence of 'MAC subPDU(s) for MAC SDU'. The S field is set to 0 to indicate absence of 'MAC subPDU(s) for MAC SDU'; +- R: Reserved bit, set to 0; +- BI: The Backoff Indicator field identifies the overload condition in the cell. The size of the BI field is 4 bits; +- RAPID: The Random Access Preamble IDentifier field identifies the transmitted Random Access Preamble (see clause 5.1.3). The size of the RAPID field is 6 bits. + +The MAC subheader is octet aligned. + +### 6.2.3 MAC payload for Random Access Response + +The MAC RAR is of fixed size as depicted in Figure 6.2.3-1, and consists of the following fields: + +- R: Reserved bit, set to 0; +- TI: If two TAGs are configured for the Serving Cell in which the Random Access procedure is being performed, this field indicates one of the two TAGs to which the Timing Advance Command is applied. If *tag2-flag* is set to *true* by upper layers, the field set to 0 indicates the *tag2-Id* and the field set to 1 indicates the *tag-Id* of the Serving Cell, otherwise the field set to 0 indicates the *tag-Id* and the field set to 1 indicates the *tag2-Id* of the Serving Cell. If the Serving Cell in which the Random Access procedure is being performed is not configured with two TAGs, the R bit is present instead; +- Timing Advance Command: The Timing Advance Command field indicates the index value $T_A$ used to control the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the Timing Advance Command field is 12 bits; +- UL Grant: The Uplink Grant field indicates the resources to be used on the uplink in TS 38.213 [6]. The size of the UL Grant field is 27 bits; +- Temporary C-RNTI: The Temporary C-RNTI field indicates the temporary identity that is used by the MAC entity during Random Access. The size of the Temporary C-RNTI field is 16 bits. + +The MAC RAR is octet aligned. + +![Diagram of MAC RAR structure showing fields across 8 octets. Octet 1 contains TI or R and Timing Advance Command. Octet 2 contains Timing Advance Command and UL Grant. Octets 3-5 contain UL Grant. Octets 6-7 contain Temporary C-RNTI.](0c4c765c70f17bcfc624d914bd321b23_img.jpg) + +| | | | | | | | | +|------------------------|------------------------|----------|--|--|--|--|-------| +| | | | | | | | | +| TI
or R | Timing Advance Command | | | | | | Oct 1 | +| Timing Advance Command | | UL Grant | | | | | Oct 2 | +| UL Grant | | | | | | | Oct 3 | +| UL Grant | | | | | | | Oct 4 | +| UL Grant | | | | | | | Oct 5 | +| Temporary C-RNTI | | | | | | | Oct 6 | +| Temporary C-RNTI | | | | | | | Oct 7 | + +Diagram of MAC RAR structure showing fields across 8 octets. Octet 1 contains TI or R and Timing Advance Command. Octet 2 contains Timing Advance Command and UL Grant. Octets 3-5 contain UL Grant. Octets 6-7 contain Temporary C-RNTI. + +Figure 6.2.3-1: MAC RAR + +### 6.2.3a MAC payload for MSGB + +The fallbackRAR is of fixed size as depicted in Figure 6.2.3a-1, and consists of the following fields: + +- R: Reserved bit, set to 0; +- TI: If two TAGs are configured for the SpCell, this field indicates one of the two TAGs to which the Timing Advance Command is applied. If *tag2-flag* is set to *true* by upper layers, the field set to 0 indicates the *tag2-Id* and the field set to 1 indicates the *tag-Id* of the SpCell, otherwise the field set to 0 indicates the *tag-Id* and the field set to 1 indicates the *tag2-Id* of the SpCell. If the SpCell is not configured with two TAGs, the R bit is present instead; +- Timing Advance Command: The Timing Advance Command field indicates the index value $T_A$ used to control the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the Timing Advance Command field is 12 bits; +- UL Grant: The Uplink Grant field indicates the resources to be used on the uplink in TS 38.213 [6]. The size of the UL Grant field is 27 bits; +- Temporary C-RNTI: The Temporary C-RNTI field indicates the temporary identity that is used by the MAC entity during Random Access. The size of the Temporary C-RNTI field is 16 bits. + +The fallbackRAR is octet aligned. + +![Diagram of fallbackRAR structure showing octet alignment. The structure is a table with 7 rows representing octets. Row 1 (Oct 1) contains 'TI or R' (1 bit) and 'Timing Advance Command' (11 bits). Row 2 (Oct 2) contains 'Timing Advance Command' (12 bits) and 'UL Grant' (15 bits). Rows 3-5 (Oct 3-5) each contain 'UL Grant' (27 bits). Rows 6-7 (Oct 6-7) each contain 'Temporary C-RNTI' (16 bits).](34f6baf47c53b490142dbe71f900f406_img.jpg) + +| | | | | | | | | +|------------------------|------------------------|--|----------|--|--|--|-------| +| | | | | | | | | +| TI
or R | Timing Advance Command | | | | | | Oct 1 | +| Timing Advance Command | | | UL Grant | | | | Oct 2 | +| UL Grant | | | | | | | Oct 3 | +| UL Grant | | | | | | | Oct 4 | +| UL Grant | | | | | | | Oct 5 | +| Temporary C-RNTI | | | | | | | Oct 6 | +| Temporary C-RNTI | | | | | | | Oct 7 | + +Diagram of fallbackRAR structure showing octet alignment. The structure is a table with 7 rows representing octets. Row 1 (Oct 1) contains 'TI or R' (1 bit) and 'Timing Advance Command' (11 bits). Row 2 (Oct 2) contains 'Timing Advance Command' (12 bits) and 'UL Grant' (15 bits). Rows 3-5 (Oct 3-5) each contain 'UL Grant' (27 bits). Rows 6-7 (Oct 6-7) each contain 'Temporary C-RNTI' (16 bits). + +**Figure 6.2.3a-1: fallbackRAR** + +The successRAR is of fixed size as depicted in Figure 6.2.3a-2, and consists of the following fields: + +- UE Contention Resolution Identity: This field contains the UL CCCH SDU. If the UL CCCH SDU is longer than 48 bits, this field contains the first 48 bits of the UL CCCH SDU. +- R: Reserved bit, set to 0; +- ChannelAccess-CPext: The channel access type and CP extension for the PUCCH resource containing the HARQ feedback for MSGB in shared spectrum channel access as specified in TS 38.213 [6]. The field is only present when the MSGB HARQ feedback is to be transmitted with shared spectrum channel access as specified in TS 37.213 [18]. Otherwise, the field is not present and R bits are present instead. The size of the ChannelAccess-CPext field is 2 bits; +- TPC: The TPC command for the PUCCH resource containing HARQ feedback for MSGB, as specified in TS 38.213 [6]. The size of the TPC field is 2 bits; +- HARQ Feedback Timing Indicator: The PDSCH-to-HARQ feedback timing indicator field for MSGB HARQ feedback as specified in TS 38.213 [6]. The size of the HARQ Feedback Timing Indicator field is 3 bits; + +- PUCCH Resource Indicator: The PUCCH resource indicator for HARQ feedback for MSGB, as specified in TS 38.213[6]. The size of the PUCCH resource Indicator field is 4 bits; +- Timing Advance Command: The Timing Advance Command field indicates the index value $T_A$ used to control the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the Timing Advance Command field is 12 bits; +- C-RNTI: The C-RNTI field indicates the identity that is used by the MAC entity upon completion of Random Access. The size of the C-RNTI field is 16 bits. + +The successRAR is octet aligned. + +![](5538dc47e91669a5729142788208c27d_img.jpg) + +| UE Contention Resolution Identity | | | | Oct 1 | +|-----------------------------------|----------------------|------------------------|--------------------------------|--------| +| UE Contention Resolution Identity | | | | Oct 2 | +| UE Contention Resolution Identity | | | | Oct 3 | +| UE Contention Resolution Identity | | | | Oct 4 | +| UE Contention Resolution Identity | | | | Oct 5 | +| UE Contention Resolution Identity | | | | Oct 6 | +| R | Channel Access-CPext | TPC | HARQ Feedback Timing Indicator | Oct 7 | +| PUCCH Resource Indicator | | Timing Advance Command | | Oct 8 | +| Timing Advance Command | | | | Oct 9 | +| C-RNTI | | | | Oct 10 | +| C-RNTI | | | | Oct 11 | + +Figure 6.2.3a-2: successRAR + +## 6.2.4 MAC subheader for SL-SCH + +The MAC subheader consists of the following fields: + +- V: The MAC PDU format version number field indicates which version of the SL-SCH subheader is used. In this version of the specification, the V field is set to 0. The size of the V field is 4 bits; +- SRC: The SRC field carries the 16 most significant bits of the Source Layer-2 ID set to the identifier provided by upper layers as defined in TS 23.287 [19] or TS 23.304 [26]. The length of the field is 16 bits; +- DST: The DST field carries the 8 most significant bits of the Destination Layer-2 ID set to the identifier provided by upper layers as defined in TS 23.287 [19] or TS 23.304 [26]. The length of the field is 8 bits; +- LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE within the scope of one Source Layer-2 ID and Destination Layer-2 ID pair or padding as described in Tables 6.2.4-1 for SL-SCH. There is one LCID field per MAC subheader except for SL-SCH subheader. The values of LCID from 21 to 36 identify the logical channels used to send duplicated + +RLC SDUs from logical channels of which the values of LCID from 4 to 19 respectively in sequential order. The size of the LCID field is 6 bits; + +- L: The Length field indicates the length of the corresponding MAC SDU or variable-sized MAC CE in bytes. There is one L field per MAC subheader except for SL-SCH subheader and subheaders corresponding to the fixed-sized MAC CE or padding. The size of the L field is indicated by the F field; +- F: The Format field indicates the size of the Length field. There is one F field per MAC subheader except for SL-SCH subheader and subheaders corresponding to the fixed-sized MAC CE or padding. The size of the F field is 1 bit. The value 0 indicates 8 bits of the Length field. The value 1 indicates 16 bits of the Length field; +- R: Reserved bit, set to 0. + +The MAC subheader is octet aligned. + +**Table 6.2.4-1: Values of LCID for SL-SCH** + +| Index | LCID values | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | SCCH carrying PC5-S messages that are not protected | +| 1 | SCCH carrying PC5-S messages "Direct Security Mode Command" and "Direct Security Mode Complete", "ProSe direct link security mode command" and "ProSe direct link security mode complete" | +| 2 | SCCH carrying other PC5-S messages that are protected | +| 3 | SCCH carrying PC5-RRC messages | +| 4-19 | Identity of the logical channel | +| 20 | SCCH carrying PC5-S messages ("Direct Security Mode Command" and "Direct Security Mode Complete") which is used for duplication | +| 21 | SCCH carrying other PC5-S messages that are protected which is used for duplication | +| 22 | SCCH carrying PC5-RRC messages which is used for duplication | +| 23-38 | Identity of the logical channel which is used for duplication | +| 39-54 | Reserved | +| 55 | SCCH carrying end-to-end SL-SRB0/1/2/3 messages delivered via SL-U2U-RLC as specified in TS 38.331 [5] | +| 56 | SCCH carrying RRC messages delivered via SL-RLC0 as specified in TS 38.331 [5] | +| 57 | SCCH carrying RRC message delivered via SL-RLC1 as specified in TS 38.331 [5] | +| 58 | SCCH for Sidelink Discovery Messages | +| 59 | Sidelink Inter-UE Coordination Request | +| 60 | Sidelink Inter-UE Coordination Information | +| 61 | Sidelink DRX Command | +| 62 | Sidelink CSI Reporting | +| 63 | Padding | + +## 7 Variables and constants + +### 7.1 RNTI values + +RNTI values are presented in Table 7.1-1. + +**Table 7.1-1: RNTI values.** + +| Value (hexa-decimal) | RNTI | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 | N/A | +| 0001-FFF2 | RA-RNTI, MSGB-RNTI, Temporary C-RNTI, C-RNTI, CI-RNTI, MCS-C-RNTI, CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, PS-RNTI, SL-RNTI, SL-CS-RNTI, SL-PRS-RNTI, SL-PRS-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI, AI-RNTI, G-RNTI, G-CS-RNTI, CG-SDT-CS-RNTI, and NCR-RNTI | +| FFF3-FFFA | Reserved | +| FFFB | Multicast MCCH-RNTI | +| FFFC | PEI-RNTI | +| FFFD | MCCH-RNTI | +| FFFE | P-RNTI | +| FFFF | SI-RNTI | + +**Table 7.1-2: RNTI usage.** + +| RNTI | Usage | Transport Channel | Logical Channel | +|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------| +| P-RNTI | Paging and System Information change notification | PCH | PCCH | +| SI-RNTI | Broadcast of System Information | DL-SCH | BCCH | +| RA-RNTI | Random Access Response | DL-SCH | N/A | +| MSGB-RNTI | Random Access Response for 2-step RA type | DL-SCH | CCCH, DCCH, DTCH | +| Temporary C-RNTI | Contention Resolution (when no valid C-RNTI is available) | DL-SCH | CCCH, DCCH, DTCH | +| Temporary C-RNTI | Msg3 transmission | UL-SCH | CCCH, DCCH, DTCH | +| C-RNTI, MCS-C-RNTI | Dynamically scheduled unicast transmission | UL-SCH | DCCH, DTCH | +| C-RNTI | Dynamically scheduled unicast transmission | DL-SCH | CCCH, DCCH, DTCH | +| NCR-RNTI | Transmission of Side Control Information for NCR operation | N/A | N/A | +| MCS-C-RNTI | Dynamically scheduled unicast transmission | DL-SCH | DCCH, DTCH | +| C-RNTI | Triggering of PDCCH ordered random access | N/A | N/A | +| C-RNTI | Dynamically scheduled PTP retransmission for initial PTM transmission for multicast MBS. | DL-SCH | MTCH | +| CG-SDT-CS-RNTI | Dynamically scheduled unicast transmission (retransmission) | UL-SCH | CCCH, DCCH, DTCH | +| CS-RNTI | Configured scheduled unicast transmission (activation, reactivation and retransmission) | DL-SCH, UL-SCH | DCCH, DTCH | +| CS-RNTI | Configured scheduled unicast transmission (deactivation) | N/A | N/A | +| CS-RNTI | Configured scheduled unicast transmission (PTP retransmission for initial PTM transmission) | DL-SCH | MTCH | +| CS-RNTI | Configured scheduled unicast transmission (MBS SPS deactivation) | N/A | N/A | +| G-CS-RNTI | Configured scheduled multicast transmission (activation, reactivation and retransmission) | DL-SCH | MTCH | +| G-CS-RNTI | Configured scheduled multicast transmission (deactivation) | N/A | N/A | +| TPC-PUCCH-RNTI | PUCCH power control | N/A | N/A | +| TPC-PUSCH-RNTI | PUSCH power control | N/A | N/A | +| TPC-SRS-RNTI | SRS trigger and power control | N/A | N/A | +| INT-RNTI | Indication pre-emption in DL | N/A | N/A | +| SFI-RNTI | Slot Format Indication on the given cell | N/A | N/A | +| SP-CSI-RNTI | Activation of Semi-persistent CSI reporting on PUSCH | N/A | N/A | +| CI-RNTI | Cancellation indication in UL | N/A | N/A | +| PS-RNTI | DCP to indicate whether to start drx-onDurationTimer for associated DRX cycle | N/A | N/A | +| SL-RNTI | Dynamically scheduled sidelink transmission | SL-SCH | SCCH, STCH | +| SL-CS-RNTI | Configured scheduled sidelink transmission (activation, reactivation and retransmission) | SL-SCH | SCCH, STCH | +| SL-CS-RNTI | Configured scheduled sidelink transmission (deactivation) | N/A | N/A | +| SL-PRS-RNTI | Dynamically scheduled sidelink PRS transmission | N/A | N/A | +| SL-PRS-CS-RNTI | Configured scheduled sidelink PRS transmission (activation and reactivation) | N/A | N/A | +| SL-PRS-CS-RNTI | Configured scheduled sidelink PRS transmission (deactivation) | N/A | N/A | +| SL Semi-Persistent Scheduling V-RNTI (NOTE 2) | Semi-Persistently scheduled sidelink transmission for V2X sidelink communication (activation, reactivation and retransmission) | SL-SCH | STCH | +| SL Semi-Persistent Scheduling V-RNTI (NOTE 2) | Semi-Persistently scheduled sidelink transmission for V2X sidelink communication (deactivation) | N/A | N/A | +| AI-RNTI | Availability indication on the given cell | N/A | N/A | +| G-RNTI | Dynamically scheduled MBS PTM transmission | DL-SCH | MTCH | +| MCCH-RNTI | Dynamically scheduled MCCH signalling and MCCH change notification | DL-SCH | MCCH | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----|-----| +| PEI-RNTI | Paging Early Indication | N/A | N/A | +| NOTE 1: The usage of MCS-C-RNTI is equivalent to that of C-RNTI in MAC procedures (except for the C-RNTI MAC CE). | | | | +| NOTE 2: The MAC entity uses SL Semi-Persistent Scheduling V-RNTI to control semi-persistently scheduled sidelink transmission on SL-SCH for V2X sidelink communication as specified in clause 5.14.1.1 of TS 36.321 [22]. | | | | +| NOTE 3: The usage of CG-SDT-CS-RNTI is equivalent to that of CS-RNTI when there is an CG-SDT procedure ongoing. | | | | + +## 7.2 Backoff Parameter values + +Backoff Parameter values are presented in Table 7.2-1. + +**Table 7.2-1: Backoff Parameter values.** + +| Index | Backoff Parameter value (ms) | +|-------|------------------------------| +| 0 | 5 | +| 1 | 10 | +| 2 | 20 | +| 3 | 30 | +| 4 | 40 | +| 5 | 60 | +| 6 | 80 | +| 7 | 120 | +| 8 | 160 | +| 9 | 240 | +| 10 | 320 | +| 11 | 480 | +| 12 | 960 | +| 13 | 1920 | +| 14 | Reserved | +| 15 | Reserved | + +## 7.3 DELTA\_PREAMBLE values + +The DELTA\_PREAMBLE preamble format based power offset values are presented in Tables 7.3-1 and 7.3-2. + +**Table 7.3-1: DELTA\_PREAMBLE values for long preamble formats.** + +| Preamble Format | DELTA_PREAMBLE values | +|-----------------|-----------------------| +| 0 | 0 dB | +| 1 | -3 dB | +| 2 | -6 dB | +| 3 | 0 dB | + +**Table 7.3-2: DELTA\_PREAMBLE values for short preamble formats.** + +| Preamble Format | DELTA_PREAMBLE values (dB) | +|-----------------|----------------------------| +| A1 | $8 + 3 \times \mu$ | +| A2 | $5 + 3 \times \mu$ | +| A3 | $3 + 3 \times \mu$ | +| B1 | $8 + 3 \times \mu$ | +| B2 | $5 + 3 \times \mu$ | +| B3 | $3 + 3 \times \mu$ | +| B4 | $3 \times \mu$ | +| C0 | $11 + 3 \times \mu$ | +| C2 | $5 + 3 \times \mu$ | + +where $\mu$ is the sub-carrier spacing configuration determined by *msg1-SubcarrierSpacing* or *msgA-SubcarrierSpacing*, as specified in TS 38.331 [5] and Table 4.2-1 in TS 38.211 [8], and the preamble formats are given by *prach-ConfigurationIndex* or *msgA-PRACH-ConfigurationIndex*, as specified in TS 38.331 [5] and Tables 6.3.3.2-2 to 6.3.3.2-4 in TS 38.211 [8]. + +## 7.4 PRACH Mask Index values + +**Table 7.4-1: PRACH Mask Index values** + +| PRACH Mask Index/
msgA-SSB-SharedRO-
MaskIndex /
ssb-SharedRO-
MaskIndex | Allowed PRACH occasion(s) of SSB | +|------------------------------------------------------------------------------------------------------|----------------------------------| +| 0 | All | +| 1 | PRACH occasion index 1 | +| 2 | PRACH occasion index 2 | +| 3 | PRACH occasion index 3 | +| 4 | PRACH occasion index 4 | +| 5 | PRACH occasion index 5 | +| 6 | PRACH occasion index 6 | +| 7 | PRACH occasion index 7 | +| 8 | PRACH occasion index 8 | +| 9 | Every even PRACH occasion | +| 10 | Every odd PRACH occasion | +| 11 | Reserved | +| 12 | Reserved | +| 13 | Reserved | +| 14 | Reserved | +| 15 | Reserved | + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|------------|------|-----|-----|------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | RAN2#97bis | R2-1703006 | - | - | - | Skeleton of NR MAC specification | 0.0.1 | +| 2017-04 | RAN2#97bis | R2-1703915 | - | - | - | Editorial updates | 0.0.2 | +| 2017-05 | RAN2#98 | R2-1704475 | - | - | - | To capture agreements from RAN2#97bis | 0.0.3 | +| 2017-06 | RAN2 NR AH#2 | R2-1706608 | - | - | - | To capture agreements from RAN2#98 | 0.0.4 | +| 2017-06 | RAN2 NR AH#2 | R2-1707471 | - | - | - | Endorsement of v0.0.4 (including minor updates) | 0.1.0 | +| 2017-08 | RAN2#99 | R2-1707510 | - | - | - | To capture agreements from RAN2 NR AH#2 | 0.2.0 | +| 2017-08 | RAN2#99 | R2-1709946 | - | - | - | To capture agreements from RAN2#99 | 0.3.0 | +| 2017-09 | RAN#77 | RP-171733 | - | - | - | To be presented to RAN for information | 1.0.0 | +| 2017-11 | RAN2#100 | R2-1712698 | - | - | - | To capture agreements from RAN2#99bis | 1.1.0 | +| 2017-12 | RAN2#100 | R2-1714253 | - | - | - | To capture agreements from RAN2#100 | 1.2.0 | +| 2017-12 | RP-78 | RP-172419 | - | - | - | To be presented to RAN for approval | 2.0.0 | +| 2017-12 | RP-78 | | | | | Upgraded to Rel-15 | 15.0.0 | +| 2018-03 | RP-79 | RP-180440 | 0039 | 1 | F | General corrections on TS 38.321 | 15.1.0 | +| 2018-03 | RP-79 | RP-180440 | 0041 | - | B | Introduction of MAC CEs for NR MIMO | 15.1.0 | +| 2018-06 | RP-80 | RP-181216 | 0057 | 5 | F | Miscellaneous corrections | 15.2.0 | +| | RP-80 | RP-181216 | 0103 | 2 | F | Addition of the beamFailureRecoveryTimer | 15.2.0 | +| | RP-80 | RP-181214 | 0115 | - | F | Correction to SR triggering to accommodate the configured grant | 15.2.0 | +| | RP-80 | RP-181215 | 0145 | 1 | F | Corrections on the timers in MAC | 15.2.0 | +| | RP-80 | RP-181215 | 0148 | 1 | F | Alternative 1 for Cross Carrier Indication for Semi-Persistent SRS MAC CE | 15.2.0 | +| | RP-80 | RP-181215 | 0153 | 2 | F | Flush HARQ buffer upon skipping a UL transmission | 15.2.0 | +| | RP-80 | RP-181215 | 0166 | 1 | F | Addition of Prioritized Random Access | 15.2.0 | +| | RP-80 | RP-181216 | 0185 | - | F | Introduction of PDCP duplication | 15.2.0 | +| | RP-80 | RP-181216 | 0186 | - | B | MAC CE adaptation for NR for TS 38.321 | 15.2.0 | +| 2018-09 | RP-81 | RP-181941 | 0058 | 5 | F | Clarification on starting of drx-HARQ-RTT-TimerDL | 15.3.0 | +| | RP-81 | RP-181939 | 0094 | 3 | F | Correction of Configured Grant formula | 15.3.0 | +| | RP-81 | RP-181940 | 0100 | 4 | F | Introduction of DRX ambiguous period | 15.3.0 | +| | RP-81 | RP-181938 | 0139 | 2 | F | Clarification on timing requirement of SCell deactivation timer | 15.3.0 | +| | RP-81 | RP-181938 | 0141 | 2 | F | Correction on PUSCH resource handling for Semi-Persistent CSI reporting | 15.3.0 | +| | RP-81 | RP-181940 | 0184 | 3 | F | CR to 38.321 on the allocation of preambles for group B | 15.3.0 | +| | RP-81 | RP-181940 | 0189 | 3 | F | PRACH Preamble Selection for Msg1 based SI Request | 15.3.0 | +| | RP-81 | RP-181938 | 0190 | 1 | F | PRACH Resource Selection for RA Initiated by PDCCH Order | 15.3.0 | +| | RP-81 | RP-181942 | 0193 | 4 | F | Miscellaneous corrections | 15.3.0 | +| | RP-81 | RP-181938 | 0200 | 1 | F | Correction on BWP inactivity timer configuration | 15.3.0 | +| | RP-81 | RP-181938 | 0203 | 2 | F | Correction on Ci bitmap length determination in the Activation/Deactivation MAC CE | 15.3.0 | +| | RP-81 | RP-181938 | 0206 | 2 | F | Addition of NOTE to clarify meaning of available UL-SCH resource | 15.3.0 | +| | RP-81 | RP-181939 | 0214 | 2 | F | Correction to RO selection procedure | 15.3.0 | +| | RP-81 | RP-181938 | 0215 | 2 | F | CR on Semi-Persistent CSI Reporting and SRS for DRX | 15.3.0 | +| | RP-81 | RP-181940 | 0234 | 2 | F | Correction to CCCH LCID | 15.3.0 | +| | RP-81 | RP-181938 | 0242 | 2 | F | Correction to SP CSI reporting on PUCCH Activation and Deactivation MAC CE | 15.3.0 | +| | RP-81 | RP-181938 | 0243 | 1 | F | Correction to TCI State Indication for UE-specific PDCCH MAC CE | 15.3.0 | +| | RP-81 | RP-181938 | 0245 | 1 | F | CR on MAC RAR | 15.3.0 | +| | RP-81 | RP-181939 | 0252 | 1 | F | Correction for LCP restriction for duplication and non-duplication | 15.3.0 | +| | RP-81 | RP-181939 | 0254 | 2 | F | CR on BWP Inactivity timer | 15.3.0 | +| | RP-81 | RP-181939 | 0255 | 2 | F | Correction to BWP operations | 15.3.0 | +| | RP-81 | RP-181938 | 0259 | 2 | F | CR on BSR transmission with insufficient grant | 15.3.0 | +| | RP-81 | RP-181940 | 0262 | 2 | F | Corrections on Configured Grants and SPS | 15.3.0 | +| | RP-81 | RP-181938 | 0272 | 2 | F | CR on RA parameter description in TS 38.321 | 15.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------|--------| +| | RP-81 | RP-181940 | 0275 | 1 | F | Correction to acknowledgement for SPS deactivation | 15.3.0 | +| | RP-81 | RP-181940 | 0276 | 1 | F | Correction to handling of retransmission with a different TBS in DL HARQ | 15.3.0 | +| | RP-81 | RP-181980 | 0279 | 2 | F | Correction to BWP handling upon SCell deactivation | 15.3.0 | +| | RP-81 | RP-181940 | 0280 | 2 | F | Correction to MAC handling during different measurement gaps | 15.3.0 | +| | RP-81 | RP-181939 | 0283 | 1 | F | PDCCH for BFR termination | 15.3.0 | +| | RP-81 | RP-181939 | 0285 | 1 | F | CSI reporting in DRX | 15.3.0 | +| | RP-81 | RP-181940 | 0290 | 1 | F | Introduction of MCS-C-RNTI | 15.3.0 | +| | RP-81 | RP-181941 | 0297 | 1 | F | Clarification on the duration of timers in MAC | 15.3.0 | +| | RP-81 | RP-181941 | 0300 | 1 | F | Clarification on support of Type 2 PH | 15.3.0 | +| | RP-81 | RP-181938 | 0302 | - | F | PRACH Occasion Selection for Msg1 based SI Request | 15.3.0 | +| | RP-81 | RP-181938 | 0304 | - | F | Correction to RA Resource Selection Procedure | 15.3.0 | +| | RP-81 | RP-181941 | 0306 | 2 | F | Correction on BWP operation procedure | 15.3.0 | +| | RP-81 | RP-181941 | 0326 | 2 | F | CR on padding BSR | 15.3.0 | +| | RP-81 | RP-181941 | 0328 | 1 | F | CR on SR cancellation | 15.3.0 | +| | RP-81 | RP-181941 | 0329 | 2 | F | CR on BWP with ongoing RA procedure - Option 1 | 15.3.0 | +| | RP-81 | RP-181940 | 0331 | 1 | F | CR on BWP inactivity timer stopping due to RA | 15.3.0 | +| | RP-81 | RP-181941 | 0342 | 1 | F | Correction for Random Access Back off | 15.3.0 | +| | RP-81 | RP-181941 | 0356 | 1 | F | RSRP measurements for Random Access | 15.3.0 | +| | RP-81 | RP-181938 | 0357 | 1 | F | Reset of BFD | 15.3.0 | +| | RP-81 | RP-181942 | 0368 | 2 | F | CR on first active BWP switching upon RRC (re)configuration | 15.3.0 | +| | RP-81 | RP-181941 | 0371 | 1 | F | Clarification on Long Truncated BSR | 15.3.0 | +| | RP-81 | RP-181940 | 0376 | - | F | Correction on SR with PUSCH resource handling of Semi-Persistent CSI reporting | 15.3.0 | +| | RP-81 | RP-181940 | 0378 | 1 | F | BWP operation for BFR RA | 15.3.0 | +| | RP-81 | RP-181942 | 0402 | 2 | F | Changes for MAC CEs to Support the Extended Maximum Number of TCI States | 15.3.0 | +| 2018-12 | RP-82 | RP-182658 | 0303 | 6 | F | Msg3 handling for switching from CBRA to CFRA | 15.4.0 | +| | RP-82 | RP-182658 | 0354 | 6 | F | Clarification on PHR timing for configured grant | 15.4.0 | +| | RP-82 | RP-182652 | 0399 | 5 | F | Preamble power ramping | 15.4.0 | +| | RP-82 | RP-182651 | 0406 | 2 | F | bwp-InactivityTimer when PDCCH indicating BWP switching is received | 15.4.0 | +| | RP-82 | RP-182666 | 0409 | 3 | F | RRR triggered BWP switching while RACH is ongoing | 15.4.0 | +| | RP-82 | RP-182658 | 0411 | 3 | F | Miscellaneous corrections | 15.4.0 | +| | RP-82 | RP-182658 | 0413 | 2 | F | RA Preamble Selection Procedure | 15.4.0 | +| | RP-82 | RP-182658 | 0421 | 3 | F | Correction for Msg3 grant overlapping with another UL grant | 15.4.0 | +| | RP-82 | RP-182649 | 0423 | 1 | F | Correction on the scaling between CSI-RS and SSB for BFR | 15.4.0 | +| | RP-82 | RP-182654 | 0432 | 2 | F | Corrections on CFRA BFR termination | 15.4.0 | +| | RP-82 | RP-182658 | 0445 | 2 | F | Correction on PHR references | 15.4.0 | +| | RP-82 | RP-182653 | 0452 | 3 | F | Correction of BWP switching when SUL is configured | 15.4.0 | +| | RP-82 | RP-182658 | 0459 | 2 | F | Correction on BSR triggered SR | 15.4.0 | +| | RP-82 | RP-182656 | 0471 | 2 | F | Correction for Reconfiguration of CFRA during ongoing RA | 15.4.0 | +| | RP-82 | RP-182656 | 0475 | 2 | F | Introduction of Data Inactivity timer in MAC | 15.4.0 | +| | RP-82 | RP-182658 | 0486 | 3 | F | Correction to RA prioritization | 15.4.0 | +| | RP-82 | RP-182653 | 0488 | 2 | F | Correction to BFR procedure | 15.4.0 | +| | RP-82 | RP-182658 | 0505 | 2 | F | Handling of overlapped configured grant and UL grant received in RAR | 15.4.0 | +| | RP-82 | RP-182658 | 0523 | 1 | F | Allow padding when UL grant size is larger than 8 bytes | 15.4.0 | +| | RP-82 | RP-182658 | 0535 | 1 | F | Clarification on LCH-to-cell restriction | 15.4.0 | +| | RP-82 | RP-182658 | 0547 | 4 | F | Clarification on BWP ID in MAC CE | 15.4.0 | +| | RP-82 | RP-182658 | 0551 | 1 | F | Corrections for alignments in RACH resource selection | 15.4.0 | +| | RP-82 | RP-182658 | 0553 | 1 | F | Correction on the RO selection for PDCCH order triggered RA | 15.4.0 | +| | RP-82 | RP-182665 | 0564 | 2 | F | Correction to SR triggering | 15.4.0 | +| | RP-82 | RP-182655 | 0575 | - | F | Handling of Msg3 size allocated by RAR mismatch during CBRA procedure | 15.4.0 | +| | RP-82 | RP-182658 | 0582 | 1 | F | Clarification to value table for recommended bit rate MAC CE | 15.4.0 | +| | RP-82 | RP-182656 | 0587 | - | F | Clarification for CCCH1 | 15.4.0 | +| | RP-82 | RP-182666 | 0593 | 5 | F | Correction to PHR procedures in dual-connectivity | 15.4.0 | +| | RP-82 | RP-182664 | 0594 | 1 | F | Correction on DL SPS configuration | 15.4.0 | +| | RP-82 | RP-182664 | 0595 | - | F | Enabling to configure TCI-state for CORESET#0 by MAC CE | 15.4.0 | +| 2019-03 | RP-83 | RP-190540 | 0603 | 1 | F | Miscellaneous corrections | 15.5.0 | +| | RP-83 | RP-190540 | 0630 | 1 | F | Correction on PH omitting of dynamic power sharing incapable UE | 15.5.0 | +| | RP-83 | RP-190540 | 0634 | 1 | F | CR on RA-RNTI calculation | 15.5.0 | +| | RP-83 | RP-190545 | 0638 | 1 | F | Clarification for random access on SUL | 15.5.0 | +| 2019-06 | RP-84 | RP-191379 | 0639 | 1 | F | Correction to PUCCH spatial relation Activation/Deactivation MAC CE | 15.6.0 | +| | RP-84 | RP-191375 | 0642 | 1 | F | Correction on NR PHR for late drop | 15.6.0 | +| | RP-84 | RP-191376 | 0646 | 1 | F | Miscellaneous corrections | 15.6.0 | +| | RP-84 | RP-191375 | 0648 | - | F | Clarification on PH value type determination | 15.6.0 | +| 2019-09 | RP-85 | RP-192190 | 0650 | 1 | F | Miscellaneous corrections | 15.7.0 | +| | RP-85 | RP-192192 | 0661 | 1 | F | Correction to semi-persistent CSI report in DRX | 15.7.0 | +| 2019-12 | RP-86 | RP-192935 | 0672 | 3 | F | Clarification on CSI reporting in C-DRX | 15.8.0 | +| | RP-86 | RP-192937 | 0680 | 1 | F | Correction on PRACH procedure with SRS switching | 15.8.0 | +| 2020-03 | RP-87 | RP-200335 | 0675 | 1 | B | PRACH prioritization procedure for MPS and MCS | 16.0.0 | +| | RP-87 | RP-200349 | 0677 | 6 | B | Introduction of Integrated Access and Backhaul for NR | 16.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------|--------| +| | RP-87 | RP-200348 | 0685 | 2 | B | Introduction of dormant BWP operation and Async CA | 16.0.0 | +| | RP-87 | RP-200347 | 0687 | 2 | B | Introduction NR mobility enhancement | 16.0.0 | +| | RP-87 | RP-200359 | 0688 | 1 | B | Recommended Bit Rate/Query for FLUS and MTSI | 16.0.0 | +| | RP-87 | RP-200339 | 0691 | 2 | B | Introduction of eMIMO for NR | 16.0.0 | +| | RP-87 | RP-200342 | 0692 | 3 | B | Introduction of 2-step RACH in 38.321 | 16.0.0 | +| | RP-87 | RP-200341 | 0694 | 1 | B | Introduction of NR-U in 38.321 | 16.0.0 | +| | RP-87 | RP-200343 | 0695 | 1 | B | Introduction of NR eURLLC | 16.0.0 | +| | RP-87 | RP-200357 | 0696 | - | F | Correction on autonomous RACH retransmission for SRS switching | 16.0.0 | +| | RP-87 | RP-200352 | 0698 | 1 | B | Introduction of NR IIOT | 16.0.0 | +| | RP-87 | RP-200344 | 0699 | 2 | B | Introduction of Rel-16 NR UE power saving in 38.321 | 16.0.0 | +| | RP-87 | RP-200346 | 0701 | 1 | B | Introduction of 5G V2X with NR Sidelink | 16.0.0 | +| | RP-87 | RP-200358 | 0703 | - | B | Introduction of a new MAC subheader for MAC CEs | 16.0.0 | +| | RP-87 | RP-200345 | 0704 | 1 | B | Introduction of NR positioning on MAC spec | 16.0.0 | +| 2020-07 | RP-88 | RP-201191 | 0705 | 2 | F | Corrections to PRACH prioritization procedure for MPS and MCS | 16.1.0 | +| | RP-88 | RP-201179 | 0708 | 4 | F | IAB MAC - rapporteur corrections and clarifications | 16.1.0 | +| | RP-88 | RP-201170 | 0711 | 4 | F | Miscellaneous corrections on eMIMO | 16.1.0 | +| | RP-88 | RP-201181 | 0712 | 3 | F | Correction for NR IIOT in 38.321 | 16.1.0 | +| | RP-88 | RP-201172 | 0714 | 5 | F | Updates to MAC spec for 2-step RACH | 16.1.0 | +| | RP-88 | RP-201190 | 0716 | 1 | F | P bit for Single Entry PHR | 16.1.0 | +| | RP-88 | RP-201174 | 0719 | 4 | F | MAC CR for Rel-16 UE power saving | 16.1.0 | +| | RP-88 | RP-201172 | 0726 | 4 | F | Corrections of NR operating with shared spectrum channel access in 38.321 | 16.1.0 | +| | RP-88 | RP-201176 | 0730 | 2 | F | Corrections to 5G V2X with NR Sidelink | 16.1.0 | +| | RP-88 | RP-201188 | 0734 | 2 | F | Correction to MAC spec for eURLLC | 16.1.0 | +| | RP-88 | RP-201159 | 0739 | - | A | Clarification on obtaining of PH values | 16.1.0 | +| | RP-88 | RP-201178 | 0743 | 1 | F | Corrections on dormant BWP operation | 16.1.0 | +| | RP-88 | RP-201177 | 0744 | 1 | B | CR on 38.321 for NR mobility enhancement | 16.1.0 | +| | RP-88 | RP-201198 | 0746 | 2 | C | Introduction of secondary DRX group CR 38.321 | 16.1.0 | +| | RP-88 | RP-201191 | 0752 | 1 | F | 38321 CR Clarification on eLCID | 16.1.0 | +| | RP-88 | RP-201166 | 0756 | 2 | F | CR to 38321 on RACH Prioritization for MPS and MCS | 16.1.0 | +| | RP-88 | RP-201175 | 0758 | 1 | F | CR for MAC in R16 positioning | 16.1.0 | +| 2020-09 | RP-89 | RP-201932 | 0769 | 2 | F | Miscellaneous corrections | 16.2.0 | +| | RP-89 | RP-201927 | 0773 | 3 | F | Corrections to 5G V2X with NR Sidelink | 16.2.0 | +| | RP-89 | RP-201963 | 0774 | 1 | F | Correction on the calculation of HARQ Process ID for SPS | 16.2.0 | +| | RP-89 | RP-201963 | 0775 | 1 | F | Correction on the term of configuredGrantConfigList | 16.2.0 | +| | RP-89 | RP-201920 | 0784 | 1 | F | Corrections to description of Candidate RS ID in BFR MAC CE | 16.2.0 | +| | RP-89 | RP-201929 | 0794 | 3 | F | Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR – Option 2 | 16.2.0 | +| | RP-89 | RP-201963 | 0802 | 1 | F | Modifications for LCH and PHY Prioritization Scenarios | 16.2.0 | +| | RP-89 | RP-201938 | 0804 | 1 | A | Clarification on HARQ process ID determination for SPS | 16.2.0 | +| | RP-89 | RP-201924 | 0809 | 3 | F | IAB MAC - miscellaneous corrections and clarifications | 16.2.0 | +| | RP-89 | RP-201920 | 0824 | 1 | F | Correction on the BFR cancellation | 16.2.0 | +| | RP-89 | RP-201920 | 0837 | - | F | BFR Cancellation regarding MAC reset | 16.2.0 | +| | RP-89 | RP-201927 | 0854 | 2 | F | Corrections to SL-BSR truncation | 16.2.0 | +| | RP-89 | RP-201927 | 0858 | 1 | F | Correction on resource (re)selection | 16.2.0 | +| | RP-89 | RP-201963 | 0876 | 1 | F | Miscellaneous corrections for IIOT MAC | 16.2.0 | +| | RP-89 | RP-201920 | 0878 | - | F | Correction on AP and SP SRS MAC-CE | 16.2.0 | +| | RP-89 | RP-201927 | 0881 | - | F | Corrections for CSI reporting | 16.2.0 | +| | RP-89 | RP-201921 | 0882 | 1 | F | Corrections for NR operating with shared spectrum channel access | 16.2.0 | +| | RP-89 | RP-201925 | 0883 | 1 | B | Introduction of MPE reporting | 16.2.0 | +| | RP-89 | RP-201922 | 0884 | - | F | Correction on dormant SCell | 16.2.0 | +| | RP-89 | RP-201932 | 0886 | - | F | Corrections to secondary DRX | 16.2.0 | +| | RP-89 | RP-201927 | 0887 | - | F | Corrections to Prioritization for 5G V2X with NR Sidelink | 16.2.0 | +| | RP-89 | RP-201963 | 0888 | - | F | Miscellaneous Corrections for intra-UE prioritization | 16.2.0 | +| | RP-89 | RP-201927 | 0889 | - | F | Correction on the calculation of CG occasion | 16.2.0 | +| | RP-89 | RP-201920 | 0890 | - | F | Corrections to SUL field in SRS Spatial Relation Indication MAC CE | 16.2.0 | +| | RP-89 | | | | | Various editorial corrections by the rapporteur | 16.2.1 | +| 2020-12 | RP-90 | RP-202767 | 0732 | 4 | F | Alignment of SR clause | 16.3.0 | +| | RP-90 | RP-202776 | 0902 | 2 | F | MAC CR for specification redundancy between MAC and PHY | 16.3.0 | +| | RP-90 | RP-202771 | 0907 | 1 | F | Correction to parameter list for beam failure recovery procedure | 16.3.0 | +| | RP-90 | RP-202769 | 0920 | 1 | F | Corrections to 5G V2X with NR Sidelink | 16.3.0 | +| | RP-90 | RP-202773 | 0927 | 2 | F | Correction on resource overlapping with grants addressed to TC-RNTI | 16.3.0 | +| | RP-90 | RP-202773 | 0928 | 1 | F | Clarification on the condition of a de-prioritized grant | 16.3.0 | +| | RP-90 | RP-202695 | 0936 | 2 | F | Miscellaneous correction on MPE reporting to 38.321 | 16.3.0 | +| | RP-90 | RP-202772 | 0938 | 1 | F | Correction on Tdelta | 16.3.0 | +| | RP-90 | RP-202789 | 0942 | 1 | A | Clarification on configured grant (re-)initialization | 16.3.0 | +| | RP-90 | RP-202771 | 0947 | 2 | F | 38.321 correction on Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE | 16.3.0 | +| | RP-90 | RP-202770 | 0956 | 1 | F | Timing of direct SCell activation upon RRC configuration | 16.3.0 | +| | RP-90 | RP-202773 | 0957 | 1 | F | Correction for SPS HARQ process ID calculation | 16.3.0 | +| | RP-90 | RP-202772 | 0962 | - | F | Pre-emptive BSR handling at MAC Reset | 16.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| | RP-90 | RP-202767 | 0966 | 1 | F | MAC corrections for NR operating in shared spectrum channel access | 16.3.0 | +| | RP-90 | RP-202789 | 0969 | - | A | Clarification of timer value zero interpretation in MAC | 16.3.0 | +| | RP-90 | RP-202775 | 0970 | 2 | F | Correction on SP posSRS (de-)activation MAC CE | 16.3.0 | +| | RP-90 | RP-202769 | 0974 | 1 | F | Correction on the SL process handling | 16.3.0 | +| | RP-90 | RP-202769 | 0977 | 1 | F | Correction on the MAC reset | 16.3.0 | +| | RP-90 | RP-202771 | 0982 | 1 | F | Correction on DELTA_PREAMBLE and parameters for 2-step RA | 16.3.0 | +| | RP-90 | RP-202772 | 0984 | - | F | Correction on the condition check in Pre-emptive BSR procedure | 16.3.0 | +| | RP-90 | RP-202777 | 0987 | 1 | F | Correction on DRX with bundle transmission of configured uplink grant | 16.3.0 | +| | RP-90 | RP-202771 | 0994 | 4 | F | Correction for CC list operation for TCI state update MAC CE | 16.3.0 | +| | RP-90 | RP-202773 | 0997 | - | F | Configured Grant related MAC CR for IoT | 16.3.0 | +| | RP-90 | RP-202773 | 0998 | - | F | Correction for Priority of Uplink Grant | 16.3.0 | +| | RP-90 | RP-202771 | 0999 | - | F | Correction on BFR MAC CE Generation and Build after Triggering of BFR | 16.3.0 | +| | RP-90 | RP-202769 | 1000 | - | F | Miscellaneous Corrections to 5G V2X with NR Sidelink | 16.3.0 | +| 2021-03 | RP-91 | RP-210689 | 1001 | 3 | F | Correction on mode2 operation | 16.4.0 | +| | RP-91 | RP-210702 | 1004 | 1 | A | Miscellaneous corrections | 16.4.0 | +| | RP-91 | RP-210691 | 1017 | 1 | F | Corrections on the description of Pre-emptive BSR MAC CE | 16.4.0 | +| | RP-91 | RP-210691 | 1026 | 1 | F | Correction for Uplink Grant Received in RAR and Addressed to Temporary C-RNTI | 16.4.0 | +| | RP-91 | RP-210691 | 1030 | 1 | F | Introduction of the Configuration for SpCell BFR Enhancement | 16.4.0 | +| | RP-91 | RP-210691 | 1034 | 1 | F | Correction on PUCCH group for enhanced PUCCH Spatial Relation | 16.4.0 | +| | RP-91 | RP-210689 | 1037 | 2 | F | Correction on available UL-SCH resource | 16.4.0 | +| | RP-91 | RP-210691 | 1043 | 1 | F | Correction on configuredGrantTimer handling on the deprioritized configured grant | 16.4.0 | +| | RP-91 | RP-210703 | 1051 | 2 | F | Corrections to MAC reset | 16.4.0 | +| | RP-91 | RP-210703 | 1053 | 2 | F | Correction on CSI reporting when CSI masking is setup | 16.4.0 | +| | RP-91 | RP-210693 | 1057 | - | F | Correction to 38.321 on MPE P-MPR Report | 16.4.0 | +| | RP-91 | RP-210702 | 1058 | - | A | Activation of CG and DRX inactivity timer | 16.4.0 | +| | RP-91 | RP-210689 | 1061 | - | F | Miscellaneous MAC corrections | 16.4.0 | +| | RP-91 | RP-210695 | 1062 | - | F | Correction to PUSCH skipping with UCI without LCH-based prioritization | 16.4.0 | +| 2021-06 | RP-92 | RP-211470 | 1065 | 1 | F | Correction on SL configured grant | 16.5.0 | +| | RP-92 | RP-211472 | 1066 | 1 | F | Clarification on which uplink grants participate to the intra-UE prioritization procedure | 16.5.0 | +| | RP-92 | RP-211472 | 1070 | 2 | F | Correction on MAC handling of uplink grants within a bundle | 16.5.0 | +| | RP-92 | RP-211474 | 1072 | 4 | F | Corrections on SP Positioning SRS Activation and Deactivation MAC CE | 16.5.0 | +| | RP-92 | RP-211470 | 1074 | 2 | F | Correction on mode 2 UE performing re-evaluation check | 16.5.0 | +| | RP-92 | RP-211475 | 1075 | 1 | F | Corrections on BSR/PHR content handling | 16.5.0 | +| | RP-92 | RP-211470 | 1095 | 2 | F | Corrections on MCS selection | 16.5.0 | +| | RP-92 | RP-211470 | 1096 | 2 | F | Miscellaneous MAC corrections | 16.5.0 | +| | RP-92 | RP-211470 | 1102 | - | F | Correction on SR procedure for sidelink BSR | 16.5.0 | +| | RP-92 | RP-211470 | 1106 | 2 | F | Handling of the retransmission TB without an associated SL process | 16.5.0 | +| | RP-92 | RP-211471 | 1112 | - | F | Correction to 38.321 on msga-TransMax selection for 2-step RACH | 16.5.0 | +| | RP-92 | RP-211475 | 1115 | - | F | Clarification on prioritization of retransmission over initial transmission for HARQ PID selection in NR-U | 16.5.0 | +| | RP-92 | RP-211473 | 1117 | - | F | CR on LCP of the source MAC entity | 16.5.0 | +| | RP-92 | RP-211472 | 1118 | - | F | CR for not transmitting only padding and padding BSR with eLCID | 16.5.0 | +| 2021-09 | RP-93 | RP-212442 | 1098 | 1 | F | Correction on UL skipping with Lch-basedPrioritization | 16.6.0 | +| | RP-93 | RP-212444 | 1122 | 1 | F | Correction on R16 uplink skipping procedure | 16.6.0 | +| | RP-93 | RP-212441 | 1123 | 1 | F | Corrections on the dynamic sidelink grants | 16.6.0 | +| | RP-93 | RP-212441 | 1125 | - | F | Correct on priority of MAC PDU for SL-SCH | 16.6.0 | +| | RP-93 | RP-212441 | 1126 | 1 | F | Correct on random selection | 16.6.0 | +| | RP-93 | RP-212441 | 1127 | 1 | F | Correction on condition of setting the resource reservation interval for mode 2 | 16.6.0 | +| | RP-93 | RP-212443 | 1129 | - | F | Correction on starting of RetransmissionTimerDL | 16.6.0 | +| | RP-93 | RP-212439 | 1134 | 1 | F | Clarification on E-UTRA MAC entity in PHR | 16.6.0 | +| | RP-93 | RP-212441 | 1139 | - | F | Corrections on MCS selection when UE performing TX resource (re-)selection check | 16.6.0 | +| | RP-93 | RP-212441 | 1140 | 1 | F | Correction on SR procedure for SL-CSI reporting | 16.6.0 | +| | RP-93 | RP-212442 | 1141 | 1 | F | Clarification of PUCCH resource in LCH-based Prioritization | 16.6.0 | +| | RP-93 | RP-212442 | 1145 | 1 | F | Correction to 38.321 on priority handling of the UL grant addressed to TC-RNTI | 16.6.0 | +| | RP-93 | RP-212441 | 1154 | - | F | Corrections for SR configuration for SL | 16.6.0 | +| 2021-12 | RP-94 | RP-213342 | 1158 | 1 | F | Correction on resource reselection behaviour | 16.7.0 | +| | RP-94 | RP-213343 | 1160 | 1 | F | Corrections to LCP for truncated SCell BFR MAC CE | 16.7.0 | +| | RP-94 | RP-213342 | 1168 | 1 | F | Miscellaneous CR on 38.321 (Rapporteur CR) | 16.7.0 | +| | RP-94 | RP-213342 | 1169 | - | F | Corrections to prioritization for NR sidelink communication | 16.7.0 | +| | RP-94 | RP-213344 | 1179 | - | F | Clarification on posSRS in MAC spec | 16.7.0 | +| | RP-94 | RP-213343 | 1180 | - | F | Clarification on Duplication MAC CE | 16.7.0 | +| 2022-03 | RP-95 | RP-220473 | 1187 | 1 | F | Correction on UL/SL prioritization | 16.8.0 | +| | RP-95 | RP-220473 | 1189 | - | F | Corrections on the Unexpected SL-BSR Trigger for SL-CSI MAC CE | 16.8.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------|--------| +| | RP-95 | RP-220473 | 1193 | - | F | Correction on the PDB derivation from LCH priority | 16.8.0 | +| | RP-95 | RP-220473 | 1202 | 1 | F | Correction on SL HARQ feedback indicator | 16.8.0 | +| | RP-95 | RP-220473 | 1207 | - | F | Correction of RV indication | 16.8.0 | +| | RP-95 | RP-220472 | 1209 | 1 | F | Clarification on the initial state of elements controlled by MAC CE and non-numerical K1 value | 16.8.0 | +| | RP-95 | RP-220473 | 1218 | 1 | F | Correction on NACK reporting on PUCCH for NR SL | 16.8.0 | +| 2022-03 | RP-95 | RP-220486 | 1171 | 7 | B | CR to 38.321 introducing Integrated Access and Backhaul for NR Rel-17 | 17.0.0 | +| | RP-95 | RP-220484 | 1184 | 1 | B | Introduction of NR MBS | 17.0.0 | +| | RP-95 | RP-220480 | 1186 | 1 | B | Introduction of RedCap in TS 38.321 | 17.0.0 | +| | RP-95 | RP-220490 | 1190 | 1 | B | Introduction of RAN Slicing | 17.0.0 | +| | RP-95 | RP-220500 | 1191 | 1 | B | Introduction of FR2 UL gap for Rel-17 | 17.0.0 | +| | RP-95 | RP-220491 | 1194 | 1 | B | Introduction of Sidelink Relay | 17.0.0 | +| | RP-95 | RP-220479 | 1197 | 2 | B | Introduction of R17 positioningEnh for MAC spec | 17.0.0 | +| | RP-95 | RP-220487 | 1198 | 1 | B | Introduction of Small Data Transmission for MAC spec | 17.0.0 | +| | RP-95 | RP-220478 | 1199 | 1 | B | TS 38.321 CR for NR coverage enhancements | 17.0.0 | +| | RP-95 | RP-220481 | 1200 | 1 | B | Introduction of enhanced IloT&URLLC support for NR | 17.0.0 | +| | RP-95 | RP-220474 | 1204 | 1 | B | Introduction of feMIMO | 17.0.0 | +| | RP-95 | RP-220476 | 1206 | 1 | B | CR of TS 38.321 for Sidelink enhancement | 17.0.0 | +| | RP-95 | RP-220485 | 1210 | 2 | B | Introduction of eDCCA | 17.0.0 | +| | RP-95 | RP-220487 | 1214 | 1 | B | Introduction of common RACH partitioning aspects in MAC | 17.0.0 | +| | RP-95 | RP-220482 | 1215 | 2 | B | Introduction of Release-17 support for Non-Terrestrial Networks (NTN) | 17.0.0 | +| | RP-95 | RP-220475 | 1219 | - | B | Introduction of Extending NR operation to 71GHz | 17.0.0 | +| 2022-06 | RP-96 | RP-221716 | 1238 | 1 | F | Miscellaneous CR on TS 38.321 for RedCap | 17.1.0 | +| | RP-96 | RP-221729 | 1243 | 3 | F | Correction to MAC spec for Small Data Transmission | 17.1.0 | +| | RP-96 | RP-221722 | 1261 | 1 | F | MAC Corrections on feMIMO | 17.1.0 | +| | RP-96 | RP-221727 | 1262 | - | F | Introduction of PEI-RNTI | 17.1.0 | +| | RP-96 | RP-221763 | 1264 | 4 | F | Corrections to MAC regarding deactivated SCG | 17.1.0 | +| | RP-96 | RP-221718 | 1266 | 1 | B | CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 | 17.1.0 | +| | RP-96 | RP-221716 | 1273 | 1 | F | MAC Corrections for RACH partitioning | 17.1.0 | +| | RP-96 | RP-221732 | 1277 | 1 | F | Correction for sidelink relay in MAC | 17.1.0 | +| | RP-96 | RP-221721 | 1279 | 1 | F | Correction on FR2 UL gap | 17.1.0 | +| | RP-96 | RP-221726 | 1281 | 1 | F | Correction for Enhanced NR IloT and URLLC in 38.321 | 17.1.0 | +| | RP-96 | RP-221713 | 1283 | 1 | A | Clarification on Duplication MAC CE | 17.1.0 | +| | RP-96 | RP-221719 | 1292 | 1 | F | Correction on MAC specification for RAN slicing | 17.1.0 | +| | RP-96 | RP-221712 | 1293 | - | A | Corrections on the MAC filtering for SL-SRB0/SL-SRB1 | 17.1.0 | +| | RP-96 | RP-221736 | 1295 | - | F | Priority of MAC CEs | 17.1.0 | +| | RP-96 | RP-221717 | 1296 | 1 | F | Corrections to Release-17 NR Non-Terrestrial Networks (NTN) | 17.1.0 | +| | RP-96 | RP-221724 | 1297 | 1 | F | Corrections for NR coverage enhancements | 17.1.0 | +| | RP-96 | RP-221725 | 1298 | - | F | Correction on MAC spec for posEnh | 17.1.0 | +| | RP-96 | RP-221712 | 1299 | - | A | Corrections on SL BSR | 17.1.0 | +| | RP-96 | RP-221718 | 1300 | 1 | F | Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 | 17.1.0 | +| | RP-96 | RP-221754 | 1301 | 1 | F | Corrections on MBS | 17.1.0 | +| | RP-96 | RP-221728 | 1302 | 1 | F | Corrections for TRS-based SCell activation | 17.1.0 | +| | RP-96 | RP-221739 | 1303 | - | F | Correction on user plane aspects for SL enhancement | 17.1.0 | +| 2022-09 | RP-97 | RP-222524 | 1318 | 2 | F | Miscellaneous corrections for NR Sidelink Relay (rapporteur CR) | 17.2.0 | +| | RP-97 | RP-222522 | 1322 | 3 | F | Corrections to MAC regarding deactivated SCG | 17.2.0 | +| | RP-97 | RP-222523 | 1327 | 1 | F | Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 | 17.2.0 | +| | RP-97 | RP-222518 | 1331 | 1 | A | Correction on the SL LCP restriction for sl-HARQ-FeedbackEnabled | 17.2.0 | +| | RP-97 | RP-222518 | 1335 | 1 | A | Clarification on the Buffer Size field in the Sidelink BSR formats | 17.2.0 | +| | RP-97 | RP-222525 | 1336 | 1 | F | Miscellaneous CR on TS 38.321 for RedCap | 17.2.0 | +| | RP-97 | RP-222524 | 1344 | 2 | F | Change to the MAC spec for R17 Positioning enhancement | 17.2.0 | +| | RP-97 | RP-222525 | 1357 | 1 | F | Change to MAC spec for Small Data Transmission | 17.2.0 | +| | RP-97 | RP-222524 | 1378 | 2 | F | Corrections to Release-17 Non-Terrestrial Networks (NTN) for TS 38.321 | 17.2.0 | +| | RP-97 | RP-222523 | 1389 | 2 | F | Miscellaneous MAC Corrections on feMIMO | 17.2.0 | +| | RP-97 | RP-222602 | 1398 | 2 | F | Correction on RO Selection with RA Partitioning | 17.2.0 | +| | RP-97 | RP-222524 | 1400 | 2 | F | 38.321 corrections for SL enhancement | 17.2.0 | +| | RP-97 | RP-222522 | 1401 | - | F | MAC corrections on MUSIM | 17.2.0 | +| | RP-97 | RP-222525 | 1402 | 1 | F | Corrections on TS 38.321 for RAN Slicing | 17.2.0 | +| | RP-97 | RP-222523 | 1403 | 1 | F | 38.321 corrections for MBS | 17.2.0 | +| | RP-97 | RP-222523 | 1404 | - | F | Correction for Simultaneous Transmission of SR and UL-SCH | 17.2.0 | +| | RP-97 | RP-222524 | 1405 | - | F | Correction on active time | 17.2.0 | +| | RP-97 | RP-222524 | 1406 | - | F | Correction on user plane aspects | 17.2.0 | +| | RP-97 | RP-222526 | 1407 | - | B | Start drx-HARQ-RTT-TimerUL after last repetition [ulHARQ_RTT_Timer] | 17.2.0 | +| 2022-12 | RP-98 | RP-223411 | 1399 | 3 | F | Correction on FR2 UL gap | 17.3.0 | +| | RP-98 | RP-223411 | 1408 | 4 | F | Correction to MAC spec for positioning enhancement | 17.3.0 | +| | RP-98 | RP-223410 | 1418 | 4 | F | Miscellaneous MAC Corrections on feMIMO | 17.3.0 | +| | RP-98 | RP-223412 | 1428 | 1 | F | Correction on SL DRX Offset Calculation | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-98 | RP-223409 | 1439 | 2 | F | Correction on BWP handling for deactivated SCG and the timing requirement for SCG activation | 17.3.0 | +| | RP-98 | RP-223412 | 1445 | 2 | F | 38.321 corrections for SL enhancement | 17.3.0 | +| | RP-98 | RP-223411 | 1446 | 1 | F | Corrections to Release-17 Non-Terrestrial Networks (NTN) for TS 38.321 | 17.3.0 | +| | RP-98 | RP-223413 | 1451 | 1 | F | Correction to MAC spec for Small Data Transmission | 17.3.0 | +| | RP-98 | RP-223406 | 1454 | 1 | F | Corrections for MBS | 17.3.0 | +| | RP-98 | RP-223411 | 1461 | 1 | F | Miscellaneous CR on TS 38.321 for RedCap | 17.3.0 | +| | RP-98 | RP-223410 | 1474 | 1 | F | Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 | 17.3.0 | +| | RP-98 | RP-223413 | 1501 | - | F | Correction to RACH partitioning features | 17.3.0 | +| | RP-98 | RP-223406 | 1505 | - | A | R16 MAC corrections | 17.3.0 | +| | RP-98 | RP-223412 | 1506 | 1 | F | R17 MAC corrections | 17.3.0 | +| | RP-98 | RP-223412 | 1507 | - | F | Correction on cast type setting for discovery message | 17.3.0 | +| 2023-03 | RP-99 | RP-230688 | 1508 | 3 | F | Correction to INACTIVE posSRS transmission | 17.4.0 | +| | RP-99 | RP-230688 | 1512 | 2 | F | Correction to PosMG Activation/Deactivation Request | 17.4.0 | +| | RP-99 | RP-230688 | 1521 | - | F | MAC Corrections on SDT | 17.4.0 | +| | RP-99 | RP-230688 | 1535 | 1 | F | Correction on uplink TA maintenance for positioning | 17.4.0 | +| | RP-99 | RP-230689 | 1537 | 2 | F | Clarification on the Serving Cell configured with two BFD-RS sets | 17.4.0 | +| | RP-99 | RP-230689 | 1538 | - | F | Clarification on desired IAB-MT PSD range | 17.4.0 | +| | RP-99 | RP-230689 | 1539 | - | F | Correction to add the missing eIAB MAC CEs | 17.4.0 | +| | RP-99 | RP-230689 | 1540 | - | F | Correction to 38.321 on Integrated Access and Backhaul for NR Rel-17 concerning DL TX power adjustment range extension | 17.4.0 | +| | RP-99 | RP-230688 | 1541 | 2 | F | Corrections for RA-SDT and CG-SDT | 17.4.0 | +| | RP-99 | RP-230689 | 1544 | 1 | F | Correction on implicit BFD-RS change | 17.4.0 | +| | RP-99 | RP-230692 | 1553 | 1 | F | Correction on discovery message filtering | 17.4.0 | +| | RP-99 | RP-230690 | 1560 | 2 | F | Corrections to NR NTN for 38.321 | 17.4.0 | +| | RP-99 | RP-230688 | 1569 | 1 | F | Correction to RA-SDT | 17.4.0 | +| | RP-99 | RP-230692 | 1571 | 1 | F | R17 MAC corrections | 17.4.0 | +| | RP-99 | RP-230694 | 1572 | 1 | D | Miscellaneous editorial changes for 38.321 | 17.4.0 | +| | RP-99 | RP-230690 | 1573 | 1 | F | MBS MAC Corrections | 17.4.0 | +| 2023-06 | RP-100 | RP-231415 | 1576 | 2 | F | Clarification on RA Resource Selection During CG-SDT | 17.5.0 | +| | RP-100 | RP-231414 | 1579 | 3 | F | Corrections on cfr-ConfigMulticast and Multicast DRX | 17.5.0 | +| | RP-100 | RP-231415 | 1580 | 2 | F | Correction to CG-SDT LCH restriction | 17.5.0 | +| | RP-100 | RP-231414 | 1583 | 3 | F | Corrections on SPS Initialization and Handling of Unknown, Unforeseen and Erroneous Protocol Data for MBS | 17.5.0 | +| | RP-100 | RP-231415 | 1584 | 2 | F | Corrections on SDT using NCD-SSB for RedCap | 17.5.0 | +| | RP-100 | RP-231418 | 1588 | 2 | F | Clarification on UL operation upon validity timer expiry | 17.5.0 | +| | RP-100 | RP-231413 | 1589 | 1 | F | Correction to MAC reset for eIAB | 17.5.0 | +| | RP-100 | RP-231418 | 1597 | 3 | F | Corrections to NR NTN for 38.321 | 17.5.0 | +| | RP-100 | RP-231416 | 1605 | 3 | F | Corrections on MAC reset regarding configured sidelink grant | 17.5.0 | +| | RP-100 | RP-231416 | 1611 | 1 | F | Correction on the usage of default CBR values for NR sidelink | 17.5.0 | +| | RP-100 | RP-231412 | 1613 | 2 | F | RA partition selection for Msg1 based SI request | 17.5.0 | +| | RP-100 | RP-231412 | 1614 | 1 | F | Correction to MAC spec for Positioning Enhancements | 17.5.0 | +| | RP-100 | RP-231416 | 1615 | - | F | Correction on 38.321 for SL enhancements | 17.5.0 | +| | RP-100 | RP-231415 | 1616 | 1 | F | Correction on SDT with separate initial BWP | 17.5.0 | +| | RP-100 | RP-231416 | 1618 | - | F | Miscellaneous corrections on TS 38.321 for NR sidelink | 17.5.0 | +| | RP-100 | RP-231415 | 1621 | 1 | F | Clarification on unknown, unforeseen and erroneous protocol data during SDT | 17.5.0 | +| | RP-100 | RP-231413 | 1622 | 1 | F | Clarification on respective roles of MAC and RRC in configuring various IAB parameters | 17.5.0 | +| | RP-100 | RP-231413 | 1624 | 2 | F | Clarification on which CSI-RS resources in IAB restricted beam MAC CEs | 17.5.0 | +| | RP-100 | RP-231416 | 1627 | 2 | F | MAC PDU filtering | 17.5.0 | +| | RP-100 | RP-231413 | 1629 | 1 | F | Correction on Enhanced BFR MAC CE | 17.5.0 | +| | RP-100 | RP-231414 | 1630 | - | F | Correction on the start condition of drx-HARQ-RTT-TimerDL | 17.5.0 | +| 2023-09 | RP-101 | RP-232568 | 1625 | 2 | F | Correction on number of restricted beams for eIAB | 17.6.0 | +| | RP-101 | RP-232667 | 1642 | 1 | F | Correction on NR Sidelink MAC | 17.6.0 | +| | RP-101 | RP-232568 | 1643 | - | F | Correction on the use of the term ID in IAB MAC CEs | 17.6.0 | +| | RP-101 | RP-232568 | 1644 | - | F | Clarification on use of SRI in IAB MAC CEs | 17.6.0 | +| | RP-101 | RP-232667 | 1653 | 1 | F | DRX Command MAC CE for MBS | 17.6.0 | +| | RP-101 | RP-232570 | 1656 | 1 | F | Correction on SDT Triggering Conditions | 17.6.0 | +| | RP-101 | RP-232667 | 1659 | - | F | Miscellaneous corrections on TS 38.321 for NR sidelink | 17.6.0 | +| | RP-101 | RP-232566 | 1660 | 1 | A | Correction on NR Sidelink MAC | 17.6.0 | +| 2023-12 | RP-102 | RP-233885 | 1669 | 2 | A | Corrections to random access cancellation criteria for sidelink BSR and CSI reporting | 17.7.0 | +| | RP-102 | RP-233886 | 1673 | 1 | A | Correction on CSI reporting for DCP function | 17.7.0 | +| | RP-102 | RP-233885 | 1676 | 3 | A | Correction on MAC layer for sidelink | 17.7.0 | +| | RP-102 | RP-233890 | 1686 | 2 | F | Correction on the condition of HARQ feedback generation and the condition of stopping drx-RetransmissionTimerDL | 17.7.0 | +| | RP-102 | RP-233890 | 1688 | 2 | F | Correction on SRI in IAB MAC CEs | 17.7.0 | +| | RP-102 | RP-233888 | 1691 | 1 | F | Rel-17 MAC corrections | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|-------------------------------------------------------------------------------------------------------|--------| +| | RP-102 | RP-233965 | 1692 | 2 | F | Correction to 38.321 on Koffset handling during MAC reset | 17.7.0 | +| | RP-102 | RP-233890 | 1714 | 1 | F | Correction on the list of MAC CEs for which there are requirements upon reception | 17.7.0 | +| | RP-102 | RP-233888 | 1718 | 1 | F | Correction on NR SL MAC | 17.7.0 | +| | RP-102 | RP-233888 | 1720 | - | F | MAC correction for Sidelink CSI reporting | 17.7.0 | +| 2023-12 | RP-102 | RP-233898 | 1554 | 11 | B | Introduction of support for Network Controlled Repeaters | 18.0.0 | +| | RP-102 | RP-233899 | 1694 | 2 | B | Introduction of eRedCap in TS 38.321 | 18.0.0 | +| | RP-102 | RP-233897 | 1695 | 2 | B | Introduction of Release-18 SL Evolution in TS 38.321 | 18.0.0 | +| | RP-102 | RP-233896 | 1696 | 1 | B | Introduction of Rel-18 MIMOevo for TS 38.321 | 18.0.0 | +| | RP-102 | RP-233914 | 1697 | 3 | B | Introduction of FR2 SCell enhancements | 18.0.0 | +| | RP-102 | RP-233908 | 1698 | 2 | B | Introduction of XR enhancements | 18.0.0 | +| | RP-102 | RP-233902 | 1699 | 2 | B | Introduction of MT-SDT and CG-SDT enhancement for MAC spec [CG-SDT-enh] | 18.0.0 | +| | RP-102 | RP-233901 | 1700 | 2 | B | Introduction of R18 positioning to MAC spec | 18.0.0 | +| | RP-102 | RP-233907 | 1701 | 2 | B | Introduction of NR MBS enhancements | 18.0.0 | +| | RP-102 | RP-233904 | 1703 | 2 | B | Introduction of NR sidelink relay enhancements | 18.0.0 | +| | RP-102 | RP-233930 | 1705 | 2 | B | Introduction of NR further mobility enhancements in TS 38.321 | 18.0.0 | +| | RP-102 | RP-233939 | 1706 | 2 | B | Introduction of Cross-RRH TCI state switch indication for high speed train | 18.0.0 | +| | RP-102 | RP-233916 | 1710 | 2 | B | Introduction of NR ATG in TS 38.321 | 18.0.0 | +| | RP-102 | RP-233895 | 1711 | 2 | B | Introduction of Further NR Coverage Enhancements in MAC spec | 18.0.0 | +| | RP-102 | RP-233906 | 1716 | 2 | B | Introduction of RACH-less handover for NR NTN and mobile IAB to TS 38.321 | 18.0.0 | +| | RP-102 | RP-233900 | 1717 | 1 | B | Introduction of Network energy savings to TS 38.321 | 18.0.0 | +| | RP-102 | RP-233906 | 1721 | 1 | B | LCID extension for CCCH/CCCH1 [LCID-extension] | 18.0.0 | +| | RP-102 | RP-233890 | 1727 | 1 | B | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | 18.0.0 | +| | RP-102 | RP-233931 | 1728 | - | B | Introduction of NR Support for Uncrewed Aerial Vehicles | 18.0.0 | +| | RP-102 | RP-233906 | 1730 | - | B | Introduction of Rel-18 NTN enhancements to TS 38.321 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38460/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38460/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e3cd33e7edb3778c9390ad569d4f2853448b5b6 --- /dev/null +++ b/marked/Rel-18/38_series/38460/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a92a9053e10a82d343fd61a67b245334e71a517850053bb732294a56a341a54 +size 7746 diff --git a/marked/Rel-18/38_series/38460/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38460/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd71ab559f921f0ce8008e8737d51c3cd9e5c105 --- /dev/null +++ b/marked/Rel-18/38_series/38460/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:196cf7bea3119193ce1af6887e6a9213d0ad85c65e2f096b72757ec90600907f +size 5805 diff --git a/marked/Rel-18/38_series/38460/raw.md b/marked/Rel-18/38_series/38460/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ea78e5f725e1947a053a6b52b6d93704208b00b6 --- /dev/null +++ b/marked/Rel-18/38_series/38460/raw.md @@ -0,0 +1,113 @@ + + +# 3GPP TS 38.460 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 general aspects and principles (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon at its base. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 to 8 Void..... 5 + +**Annex A (informative): Change history..... 6** + +## --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +## --- 1 Scope + +See TS 37.480 [8]. + +## --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] – [7] Void + +[8] 3GPP TS 37.480: “E1 general aspects and principles”. + +### --- 3 to 8 Void + +## --- 9 E1 general aspects and principles + +See TS 37.480 [8]. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38461/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38461/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93c4d0bda174b0bd353ced9a4097e6ca326bdc6 --- /dev/null +++ b/marked/Rel-18/38_series/38461/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d26e9e9c68d911ea3ae8a17036e086dca6dc531854441b038d29d927e6239d37 +size 9460 diff --git a/marked/Rel-18/38_series/38461/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38461/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe7358dd789ac29a1c3832788b147ef89a71b19b --- /dev/null +++ b/marked/Rel-18/38_series/38461/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8a119b55ea69080042d9cee1aa04514ec0fe872de7c1ba5ab416ef93dde6f1e +size 6893 diff --git a/marked/Rel-18/38_series/38461/raw.md b/marked/Rel-18/38_series/38461/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fab4b5cf82054f26f9ac8ebe5ff52b0120a9d628 --- /dev/null +++ b/marked/Rel-18/38_series/38461/raw.md @@ -0,0 +1,115 @@ + + +# 3GPP TS 38.461 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 layer 1 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in small black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +- Foreword ..... 5 +- 1 Scope..... 6 +- 2 References..... 6 +- 3 Void..... 6 + - 3.1 Void..... 6 + - 3.2 Void..... 6 +- 4 Void..... 6 +- 5 E1 layer 1 ..... 6 +- Annex A (informative): Change history ..... 7** + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +See TS 37.481 [2]. + +## --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] Void. + +[2] 3GPP TS 37.481: "E1 layer 1". + +# --- 3 Void + +## 3.1 Void + +## 3.2 Void + +## --- 4 Void + +## --- 5 E1 layer 1 + +See TS 37.481 [2]. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38521-3/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Rel-18/38_series/38521-3/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5da3a45b70ddf0f8df7a373e77a763072e7d521a --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d4238be724771db00a27ee313f2567274f8e57c637bcd48bb2478e0c4ef7838 +size 5765 diff --git a/marked/Rel-18/38_series/38521-3/0955cb376118079cebbd9e7b2eff2b05_img.jpg b/marked/Rel-18/38_series/38521-3/0955cb376118079cebbd9e7b2eff2b05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be49ffc91466666ca2a168cd2e06bcb2826e5e01 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/0955cb376118079cebbd9e7b2eff2b05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8eed55c16f3c2a365e2b992502f9852e8993f133364073ba39c6f0fc34e7a53 +size 118905 diff --git a/marked/Rel-18/38_series/38521-3/215e8d5e5ba38df215b55049d255b2ed_img.jpg b/marked/Rel-18/38_series/38521-3/215e8d5e5ba38df215b55049d255b2ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a0fa7ac8d370208e759485eb988b92774c0ec89 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/215e8d5e5ba38df215b55049d255b2ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e84ea3d54fea53aae8de2a9d6ba75ce6e6878e5ea409be6cf4e689f464c9d3dd +size 109132 diff --git a/marked/Rel-18/38_series/38521-3/2957154f4dc666a6cafb7b4d2d882910_img.jpg b/marked/Rel-18/38_series/38521-3/2957154f4dc666a6cafb7b4d2d882910_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a49d109d376ebdada781dd11a0da690e293d7ce1 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/2957154f4dc666a6cafb7b4d2d882910_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf821e6cfb78b500ea4e48a440996b821c65d3e0233eba1a63eca152e2d37373 +size 109393 diff --git a/marked/Rel-18/38_series/38521-3/4f4b52340aaccb1bcf733468dca9ee03_img.jpg b/marked/Rel-18/38_series/38521-3/4f4b52340aaccb1bcf733468dca9ee03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bd75c85bc50d402794b63c67af8794185f8413d --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/4f4b52340aaccb1bcf733468dca9ee03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64aa45f2f21b38892e7a8a09ad59903085fc4876af1a872aded40a96c6977688 +size 9704 diff --git a/marked/Rel-18/38_series/38521-3/63a2519518616620ef0e53d98b923c05_img.jpg b/marked/Rel-18/38_series/38521-3/63a2519518616620ef0e53d98b923c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42450d23c3545859073ba838128a51b63c110d54 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/63a2519518616620ef0e53d98b923c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21928b2de0eed240f309f789d6a5b3d8c22fcc72407c10a2c2b15d78a2ee3549 +size 27563 diff --git a/marked/Rel-18/38_series/38521-3/67c5b121b58d497a6de5addf4e7bd555_img.jpg b/marked/Rel-18/38_series/38521-3/67c5b121b58d497a6de5addf4e7bd555_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60033a3c453817b2730a89e954d7f6c10d84bf44 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/67c5b121b58d497a6de5addf4e7bd555_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d70343a8938bc0fbeb2fd64d58ee687916e1a2fb1ee3bd16c6fb1b501ed7274 +size 102359 diff --git a/marked/Rel-18/38_series/38521-3/843c1635ec8d9d05abf22214cb262fb4_img.jpg b/marked/Rel-18/38_series/38521-3/843c1635ec8d9d05abf22214cb262fb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bd23e18c7d33cb0613f3e7e0a16010c56dabbc2 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/843c1635ec8d9d05abf22214cb262fb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0e7cfd40c65fbe2c2af78af400c2d53cdd9f58926c96f8cb4af0d5b06725ffa +size 117794 diff --git a/marked/Rel-18/38_series/38521-3/88a6d9692a52989caa6b208a1ba70dc0_img.jpg b/marked/Rel-18/38_series/38521-3/88a6d9692a52989caa6b208a1ba70dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..375e8e60246203c13d8703cc97678cd803c2a251 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/88a6d9692a52989caa6b208a1ba70dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb347465a928024d8daa13c69e10085627fe8643895f5d2278772d8fdb48ec50 +size 41883 diff --git a/marked/Rel-18/38_series/38521-3/8d91c13d9c584af8129133d91ecb4bb9_img.jpg b/marked/Rel-18/38_series/38521-3/8d91c13d9c584af8129133d91ecb4bb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7e09b6acf2032d8b5307b7c3d67dd7957353917 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/8d91c13d9c584af8129133d91ecb4bb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4317e37a5d85b33dfc644e212f5ed2ce9eb9f9a692f095d1e8f26b23ce55d301 +size 102942 diff --git a/marked/Rel-18/38_series/38521-3/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/Rel-18/38_series/38521-3/9687bd5e8b62cadba093b0d1b70536cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24a7cddfd6d8062fc1a13c09abd3f320b9f3c229 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/9687bd5e8b62cadba093b0d1b70536cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8001d56fc09139920f3d81cacdaf3cb4aedec4493e0d83637c1e38812240421 +size 107750 diff --git a/marked/Rel-18/38_series/38521-3/a680643d7564c58bfaae20cb643d5da7_img.jpg b/marked/Rel-18/38_series/38521-3/a680643d7564c58bfaae20cb643d5da7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa6f813f5bcfe494eaa86681fd55855910acb45 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/a680643d7564c58bfaae20cb643d5da7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50c13ea728399bdff7057c23113d5a4db54c1639c43b9bacf4dacfa8231a3459 +size 106663 diff --git a/marked/Rel-18/38_series/38521-3/d66f6b708b0f0f8717f85872afec0089_img.jpg b/marked/Rel-18/38_series/38521-3/d66f6b708b0f0f8717f85872afec0089_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d39433265218449bf474d6c8cddf90e4ec74ee20 --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/d66f6b708b0f0f8717f85872afec0089_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9be159b1d0305e9f1dec350506974ba1d61f6b5684f63330a83c779d89d83be8 +size 117325 diff --git a/marked/Rel-18/38_series/38521-3/raw.md b/marked/Rel-18/38_series/38521-3/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..365c81a378dae6a6e6b1f252e97657f15267533b --- /dev/null +++ b/marked/Rel-18/38_series/38521-3/raw.md @@ -0,0 +1,33659 @@ +# 3GPP TS 38.521-3 V18.1.1 (2024-01) --- + +*Technical Specification* + +**3rd Generation Partnership Project; +Technical Specification Group Radio Access Network;** + +**NR;** + +**User Equipment (UE) conformance specification; +Radio transmission and reception;** + +**Part 3: Range 1 and Range 2 Interworking operation with other +radios +(Release 18)** + +--- + +![5G logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](4f4b52340aaccb1bcf733468dca9ee03_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +## --- **Keywords** + +3GPP, New Radio + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|----------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 17 | +| 1 Scope..... | 18 | +| 2 References..... | 18 | +| 3 Definitions, symbols and abbreviations ..... | 19 | +| 3.1 Definitions..... | 19 | +| 3.2 Symbols..... | 19 | +| 3.3 Abbreviations ..... | 20 | +| 4 General..... | 22 | +| 4.1 Relationship between minimum requirements and test requirements..... | 22 | +| 4.2 Applicability of minimum requirements ..... | 22 | +| 4.3 Specification suffix information..... | 23 | +| 4.4 Test points analysis ..... | 24 | +| 4.5 Applicability and test coverage rules ..... | 24 | +| 4.5.0 General ..... | 24 | +| 4.5.1 Test coverage across 5G NR connectivity options..... | 25 | +| 4.6 E-UTRA configuration for EN-DC FR1 tests applying the E-UTRA anchor-agnostic approach..... | 25 | +| 4.7 E-UTRA configuration for EN-DC FR2 tests applying the E-UTRA anchor-agnostic approach..... | 27 | +| 4.8 E-UTRA configuration for EN-DC FR1 tests not applying the E-UTRA anchor-agnostic approach..... | 29 | +| 5 Operating bands and channel arrangement ..... | 29 | +| 5.1 General ..... | 29 | +| 5.2 Operating bands..... | 30 | +| 5.2A Operating bands for CA ..... | 30 | +| 5.2A.1 Inter-band CA between FR1 and FR2..... | 30 | +| 5.2B Operating bands for DC ..... | 30 | +| 5.2B.1 General ..... | 30 | +| 5.2B.2 to 5.2B.7 Void..... | 30 | +| 5.2E Operating bands for V2X..... | 30 | +| 5.2E.1 Intra-band V2X bands ..... | 30 | +| 5.2E.2 Inter-band V2X bands ..... | 30 | +| 5.3 UE Channel bandwidth ..... | 31 | +| 5.3A UE Channel bandwidth for CA ..... | 31 | +| 5.3A.1 Inter-band CA between FR1 and FR2..... | 31 | +| 5.3B UE Channel bandwidth for DC ..... | 31 | +| 5.3B.0 General ..... | 31 | +| 5.3B.1 Intra-band EN-DC in FR1 ..... | 32 | +| 5.3B.1.1 General..... | 32 | +| 5.3B.1.2 BCS for Intra-band contiguous EN-DC..... | 32 | +| 5.3B.1.3 BCS for Intra-band non-contiguous EN-DC ..... | 32 | +| 5.3E UE Channel bandwidth for V2X..... | 33 | +| 5.3E.0 General ..... | 33 | +| 5.3E.1 Intra-band contiguous V2X in FR1 ..... | 33 | +| 5.3E.2 Intra-band non-contiguous V2X in FR1 ..... | 34 | +| 5.3E.3 Inter-band V2X in FR1 ..... | 34 | +| 5.4 Void..... | 34 | +| 5.4A Channel arrangement for CA ..... | 34 | +| 5.4B Channel arrangement for DC ..... | 34 | +| 5.4B.0 General ..... | 34 | +| 5.4B.1 Channel spacing for intra-band EN-DC carriers ..... | 34 | +| 5.5 Configuration ..... | 35 | +| 5.5A Configuration for CA ..... | 35 | +| 5.5A.1 Inter-band CA configurations between FR1 and FR2..... | 35 | +| 5.5B Configuration for DC ..... | 37 | +| 5.5B.1 General ..... | 37 | +| 5.5B.2 Intra-band contiguous EN-DC..... | 37 | + +| | | | +|--------------|-------------------------------------------------------------------------------------------------------------|-----| +| 5.5B.3 | Intra-band non-contiguous EN-DC ..... | 38 | +| 5.5B.4 | Inter-band EN-DC within FR1 ..... | 38 | +| 5.5B.4.1 | Inter-band EN-DC configurations within FR1 (two bands) ..... | 39 | +| 5.5B.4.2 | Inter-band EN-DC configurations within FR1 (three bands) ..... | 44 | +| 5.5B.4.3 | Inter-band EN-DC configurations within FR1 (four bands)..... | 51 | +| 5.5B.4.4 | Inter-band EN-DC configurations within FR1 (five bands) ..... | 56 | +| 5.5B.4.5 | Inter-band EN-DC configurations within FR1 (six bands)..... | 58 | +| 5.5B.4a | Inter-band NE-DC within FR1 ..... | 59 | +| 5.5B.4a.1 | Inter-band NE-DC configurations within FR1 (two bands) ..... | 59 | +| 5.5B.5 | Inter-band EN-DC including FR2 ..... | 59 | +| 5.5B.5.1 | Inter-band EN-DC configurations including FR2 (two bands) ..... | 60 | +| 5.5B.5.2 | Inter-band EN-DC configurations including FR2 (three bands) ..... | 63 | +| 5.5B.5.3 | Inter-band EN-DC configurations including FR2 (four bands)..... | 69 | +| 5.5B.5.4 | Inter-band EN-DC configurations including FR2 (five bands) ..... | 73 | +| 5.5B.5.5 | Void ..... | 73 | +| 5.5B.6 | Inter-band EN-DC including FR1 and FR2..... | 73 | +| 5.5B.6.1 | Void ..... | 74 | +| 5.5B.6.2 | Inter-band EN-DC configurations including FR1 and FR2 (three bands)..... | 74 | +| 5.5B.6.3 | Inter-band EN-DC configurations including FR1 and FR2 (four bands)..... | 74 | +| 5.5B.6.4 | Inter-band EN-DC configurations including FR1 and FR2 (five bands)..... | 74 | +| 5.5B.6.5 | Inter-band EN-DC configurations including FR1 and FR2 (six bands)..... | 74 | +| 5.5B.7 | Inter-band NR-DC between FR1 and FR2 ..... | 74 | +| 5.5B.7.0 | General..... | 74 | +| 5.5B.7.1 | Inter-band NR-DC configurations between FR1 and FR2 (two bands) ..... | 74 | +| 5.5E | Configuration for V2X operation..... | 74 | +| 5.5E.1 | General ..... | 74 | +| 5.5E.2 | Intra-band contiguous V2X operation in FR1 ..... | 75 | +| 5.5E.3 | Intra-band non-contiguous V2X operation in FR1 ..... | 75 | +| 5.5E.4 | Inter-band V2X operation in FR1..... | 75 | +| 5.5E.4.1 | Inter-band V2X configurations within FR1 (two bands)..... | 75 | +| 6 | Transmitter characteristics ..... | 75 | +| 6.1 | General ..... | 75 | +| 6.2 | Transmitter power ..... | 77 | +| 6.2A | Transmitter power for CA without EN-DC..... | 77 | +| 6.2A.1 | UE maximum output power for CA ..... | 77 | +| 6.2A.1.1 | UE maximum output power for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 77 | +| 6.2A.2 | UE maximum output power reduction for CA ..... | 77 | +| 6.2A.2.1 | UE maximum output power reduction for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 77 | +| 6.2A.3 | UE additional maximum output power reduction for CA ..... | 77 | +| 6.2A.3.1 | UE additional maximum output power reduction for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 77 | +| 6.2A.4 | Configured output power level for CA ..... | 78 | +| 6.2A.4.1 | Configured output power level for inter-band NR CA between FR 1 and FR 2 without EN-DC..... | 78 | +| 6.2A.4.2 | $\Delta T_{IB,c}$ for CA..... | 78 | +| 6.2A.4.2.1 | $\Delta T_{IB,c}$ for inter-band CA between FR 1 and FR 2..... | 78 | +| 6.2B | Transmitter power for DC ..... | 78 | +| 6.2B.1 | UE Maximum Output Power for DC..... | 78 | +| 6.2B.1.1 | UE Maximum Output Power for Intra-Band Contiguous EN-DC ..... | 78 | +| 6.2B.1.2 | UE Maximum Output Power for Intra-Band Non-Contiguous EN-DC ..... | 83 | +| 6.2B.1.3 | UE Maximum Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC)..... | 87 | +| 6.2B.1.3_1 | UE Maximum Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC)..... | 110 | +| 6.2B.1.3a | UE Maximum Output Power for Inter-Band NE-DC within FR1..... | 115 | +| 6.2B.1.4 | UE Maximum Output Power for Inter-Band EN-DC including FR2..... | 116 | +| 6.2B.1.4.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP and TRP..... | 116 | +| 6.2B.1.4.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - Spherical Coverage..... | 117 | +| 6.2B.1.4_1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (>1 NR CC)..... | 118 | +| 6.2B.1.4_1.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs)..... | 118 | + +| | | | +|----------------|----------------------------------------------------------------------------------------------------|-----| +| 6.2B.1.4_1.1.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - EIRP and TRP..... | 118 | +| 6.2B.1.4_1.1.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - Spherical Coverage..... | 119 | +| 6.2B.1.4_1.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs)..... | 120 | +| 6.2B.1.4_1.2.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - EIRP and TRP ..... | 120 | +| 6.2B.1.4_1.2.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - Spherical Coverage..... | 121 | +| 6.2B.1.4_1.3 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs)..... | 122 | +| 6.2B.1.4_1.3.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) - EIRP and TRP ..... | 122 | +| 6.2B.1.4_1.3.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) – Spherical Coverage..... | 123 | +| 6.2B.1.4_1.4 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs)..... | 124 | +| 6.2B.1.4_1.4.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) - EIRP and TRP ..... | 124 | +| 6.2B.1.4_1.4.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) – Spherical Coverage..... | 124 | +| 6.2B.1.4_1.5 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs)..... | 124 | +| 6.2B.1.4_1.5.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) - EIRP and TRP ..... | 124 | +| 6.2B.1.4_1.5.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) – Spherical Coverage..... | 125 | +| 6.2B.1.4_1.6 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs)..... | 125 | +| 6.2B.1.4_1.6.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) - EIRP and TRP ..... | 125 | +| 6.2B.1.4_1.6.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) – Spherical Coverage..... | 125 | +| 6.2B.1.4_1.7 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (8 NR CCs)..... | 125 | +| 6.2B.1.4_1.7.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (8 NR CCs) - EIRP and TRP ..... | 125 | +| 6.2B.1.4_1.7.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (8 NR CCs) – Spherical Coverage..... | 126 | +| 6.2B.1.4D | UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO - EIRP and TRP..... | 126 | +| 6.2B.1.4D.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO..... | 126 | +| 6.2B.1.4D.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO- Spherical coverage ..... | 127 | +| 6.2B.1.5 | UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 ..... | 128 | +| 6.2B.1.5D | UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 for UL MIMO... .. | 128 | +| 6.2B.1.6 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP with UL Gaps..... | 128 | +| 6.2B.2 | UE Maximum Output Power reduction for EN-DC..... | 129 | +| 6.2B.2.0 | General ..... | 129 | +| 6.2B.2.1 | UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC ..... | 129 | +| 6.2B.2.2 | UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC ..... | 142 | +| 6.2B.2.3 | UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 (1 NR CC)..... | 152 | +| 6.2B.2.3a | UE Maximum Output Power reduction for Inter-Band NE-DC within FR1 (1 NR CC)..... | 153 | +| 6.2B.2.4 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC)..... | 153 | +| 6.2B.2.4a | UE Maximum Output Power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) ..... | 154 | +| 6.2B.2.4D | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC)..... | 155 | +| 6.2B.2.4_1 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (>1 NR CC)..... | 156 | +| 6.2B.2.4_1.1 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (2 NR CCs)..... | 156 | +| 6.2B.2.4_1.2 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (3 NR CCs)..... | 157 | +| 6.2B.2.4_1.3 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (4 NR CCs)..... | 158 | +| 6.2B.2.5 | UE Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 ..... | 159 | +| 6.2B.2.5D | UE Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 for UL MIMO..... | 159 | +| 6.2B.3 | UE additional maximum output power reduction for EN-DC ..... | 159 | +| 6.2B.3.1 | UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC..... | 159 | + +| | | | +|--------------|----------------------------------------------------------------------------------------------------------------|-----| +| 6.2B.3.2 | UE Additional Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC ..... | 184 | +| 6.2B.3.3 | UE Additional Maximum Output Power reduction for Inter-Band EN-DC within FR1 (1 NR CC) .. | 202 | +| 6.2B.3.4 | UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC)..... | 203 | +| 6.2B.3.4D | UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) for UL MIMO ..... | 205 | +| 6.2B.3.5 | UE Additional Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2..... | 206 | +| 6.2B.3.5D | UE Additional Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 for UL MIMO ..... | 206 | +| 6.2B.4 | Configured Output Power for EN-DC..... | 206 | +| 6.2B.4.1 | Configured Output Power Level for EN-DC ..... | 206 | +| 6.2B.4.1.0 | Minimum Conformance Requirements..... | 206 | +| 6.2B.4.1.1 | Configured Output Power Level for Intra-Band Contiguous EN-DC..... | 216 | +| 6.2B.4.1.2 | Configured Output Power for Intra-Band Non-Contiguous EN-DC ..... | 221 | +| 6.2B.4.1.3 | Configured Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) ..... | 226 | +| 6.2B.4.1.3_1 | Configured Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC)..... | 233 | +| 6.2B.4.1.4 | Configured Output Power for Inter-Band EN-DC including FR2 (1 NR CC) ..... | 238 | +| 6.2B.4.1.4_1 | Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC) ..... | 239 | +| 6.2B.4.1.5 | Configured Output Power for Inter-Band EN-DC including both FR1 and FR2 ..... | 240 | +| 6.2B.4.2 | $\Delta T_{IB,c}$ for EN-DC ..... | 240 | +| 6.2B.4.2.1 | Intra-Band Contiguous EN-DC..... | 240 | +| 6.2B.4.2.2 | Intra-Band non-Contiguous EN-DC..... | 240 | +| 6.2B.4.2.3 | Inter-Band EN-DC within FR1 ..... | 241 | +| 6.2B.4.2.3a | Inter-band NE-DC within FR1 ..... | 260 | +| 6.2B.4.2.4 | Inter-band EN-DC including FR2..... | 260 | +| 6.2B.4.2.5 | Inter-band EN-DC including both FR1 and FR2 ..... | 261 | +| 6.2B.5 | Configured Output Power for NR-DC ..... | 261 | +| 6.2B.5.1 | Configured Output power Level ..... | 261 | +| 6.2B.5.1.1 | Configured Output Power Level for Inter-band NR-DC between FR1 and FR2 ..... | 261 | +| 6.2E | Transmitter power for V2X in FR1 ..... | 262 | +| 6.2E.1 | UE Maximum Output Power for V2X ..... | 262 | +| 6.2E.1.0 | Minimum conformance requirements..... | 262 | +| 6.2E.1.1 | UE maximum output power for Intra-band contiguous V2X..... | 263 | +| 6.2E.1.2 | UE maximum output power for Intra-band non-contiguous V2X..... | 263 | +| 6.2E.1.3 | UE maximum output power for Inter-band V2X..... | 263 | +| 6.2E.1.3.1 | UE maximum output power for Inter-band V2X with E-UTRA Uu and NR Sidelink..... | 263 | +| 6.2E.1.3.2 | UE maximum output power reduction for Inter-band V2X with NR Uu and E-UTRA V2X..... | 265 | +| 6.2E.2 | UE maximum output power reduction for V2X ..... | 267 | +| 6.2E.2.0 | Minimum conformance requirements..... | 267 | +| 6.2E.2.1 | UE maximum output power reduction for Intra-band V2X ..... | 267 | +| 6.2E.2.2 | UE maximum output power reduction for Inter-band V2X ..... | 267 | +| 6.2E.2.2.1 | UE maximum output power reduction for Inter-band V2X with E-UTRA Uu and NR Sidelink..... | 267 | +| 6.2E.2.2.2 | UE maximum output power reduction for Inter-band V2X with NR Uu and E-UTRA V2X..... | 269 | +| 6.3 | Output power dynamics ..... | 271 | +| 6.3A | Output Power Dynamics for CA without EN-DC..... | 271 | +| 6.3A.1 | UE Output Power Dynamics for CA ..... | 271 | +| 6.3A.1.1 | UE Output Power Dynamics for NR CA between FR 1 and FR 2 without EN-DC..... | 271 | +| 6.3B | Output power dynamics for DC ..... | 272 | +| 6.3B.1 | Minimum Output Power for EN-DC ..... | 272 | +| 6.3B.1.1 | Minimum Output Power for intra-band contiguous EN-DC ..... | 272 | +| 6.3B.1.2 | Minimum output power for intra-band non-contiguous EN-DC ..... | 273 | +| 6.3B.1.3 | Minimum output power for inter-band EN-DC within FR1 (1 NR CC) ..... | 274 | +| 6.3B.1.4 | Minimum Output Power for EN-DC Interband including FR2 (1 NR CC) ..... | 275 | +| 6.3B.1.4_1 | Minimum output power for inter-band EN-DC including FR2 (>1 NR CC)..... | 275 | +| 6.3B.1.4_1.1 | Minimum output power for inter-band EN-DC including FR2 (2 NR CCs) ..... | 275 | +| 6.3B.1.4_1.2 | Minimum output power for inter-band EN-DC including FR2 (3 NR CCs) ..... | 276 | +| 6.3B.1.4_1.3 | Minimum output power for inter-band EN-DC including FR2 (4 NR CCs) ..... | 277 | +| 6.3B.1.4_1.4 | Minimum output power for inter-band EN-DC including FR2 (5 NR CCs) ..... | 278 | +| 6.3B.1.4_1.5 | Minimum output power for inter-band EN-DC including FR2 (6 NR CCs) ..... | 279 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------|-----| +| 6.3B.1.4_1.6 | Minimum output power for inter-band EN-DC including FR2 (7 NR CCs) ..... | 280 | +| 6.3B.1.4_1.7 | Minimum output power for inter-band EN-DC including FR2 (8 NR CCs) ..... | 281 | +| 6.3B.1.4D | Minimum output power for inter-band EN-DC including FR2 for UL MIMO..... | 282 | +| 6.3B.2 | Transmit OFF Power for EN-DC ..... | 283 | +| 6.3B.2.1 | Transmit OFF Power for intra-band contiguous EN-DC..... | 283 | +| 6.3B.2.2 | Transmit OFF Power for intra-band non-contiguous EN-DC ..... | 283 | +| 6.3B.2.3 | Transmit OFF Power for inter-band EN-DC within FR1 (1 NR CC) ..... | 284 | +| 6.3B.2.4 | Transmit OFF Power for inter-band EN-DC including FR2 (1 NR CC)..... | 284 | +| 6.3B.2.4_1 | Void ..... | 285 | +| 6.3B.2.4D | Transmit OFF Power for inter-band EN-DC including FR2 for UL-MIMO ..... | 285 | +| 6.3B.3 | Transmit ON/OFF time mask/PUCCH time mask for EN-DC ..... | 286 | +| 6.3B.3.1 | Transmit ON/OFF time mask for intra-band contiguous EN-DC ..... | 286 | +| 6.3B.3.2 | Transmit ON/OFF time mask for intra-band non-contiguous EN-DC..... | 287 | +| 6.3B.3.3 | Transmit ON/OFF time mask for inter-band EN-DC within FR1 (1 NR CC)..... | 288 | +| 6.3B.3.4 | Transmit ON/OFF time mask for inter-band EN-DC including FR2 (1 NR CC)..... | 288 | +| 6.3B.3.4_1 | Transmit ON/OFF time mask for Inter-Band EN-DC including FR2 (>1 NR CC) ..... | 289 | +| 6.3B.3.4_1.1 | Transmit ON/OFF time mask for Inter-Band EN-DC including FR2 (2 NR CCs) ..... | 289 | +| 6.3B.3.4D | Transmit ON/OFF time mask for inter-band EN-DC including FR2 for UL-MIMO ..... | 290 | +| 6.3B.3_1 | E-UTRA and NR switching time mask for switching between two uplink carriers ..... | 291 | +| 6.3B.3_1.1 | E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC ..... | 291 | +| 6.3B.4 | PRACH time mask for EN-DC ..... | 294 | +| 6.3B.4.1 | PRACH time mask for intra-band contiguous EN-DC..... | 294 | +| 6.3B.4.2 | PRACH Time Mask for intra-band non-contiguous EN-DC..... | 296 | +| 6.3B.4.3 | PRACH Time Mask for inter-band EN-DC within FR1 (1 NR CC)..... | 297 | +| 6.3B.4.4 | PRACH Time Mask for inter-band EN-DC including FR2 (1 NR CC)..... | 298 | +| 6.3B.5 | Output power dynamics for EN-DC with UL sharing from UE perspective ..... | 298 | +| 6.3B.5.1 | E-UTRA and NR switching time mask for TDM based UL sharing from UE perspective ..... | 298 | +| 6.3B.6 | Output power dynamics for intra-band EN-DC without dual PA capability ..... | 299 | +| 6.3B.7 | Output power dynamics for intra-band EN-DC with dual PA capability..... | 299 | +| 6.3B.8 | Power control for EN-DC..... | 299 | +| 6.3B.8.1 | Absolute power tolerance for EN-DC ..... | 299 | +| 6.3B.8.1.1 | Absolute power tolerance for intra-band contiguous EN-DC..... | 299 | +| 6.3B.8.1.2 | Absolute power tolerance for intra-band non-contiguous EN-DC..... | 300 | +| 6.3B.8.1.3 | Absolute power tolerance for inter-band EN-DC within FR1 (1 NR CC)..... | 300 | +| 6.3B.8.1.4 | Absolute power tolerance for inter-band EN-DC including FR2 (1 NR CC)..... | 301 | +| 6.3B.8.2 | Relative power tolerance for EN-DC..... | 302 | +| 6.3B.8.2.1 | Relative power tolerance for intra-band contiguous EN-DC..... | 302 | +| 6.3B.8.2.2 | Relative power tolerance for intra-band non-contiguous EN-DC..... | 303 | +| 6.3B.8.2.3 | Relative power tolerance for inter-band EN-DC within FR1 (1 NR CC)..... | 304 | +| 6.3B.8.2.4 | Relative power tolerance for inter-band EN-DC including FR2 (1 NR CC)..... | 304 | +| 6.3B.8.3 | Aggregate power tolerance for EN-DC ..... | 305 | +| 6.3B.8.3.1 | Aggregate power tolerance for intra-band contiguous EN-DC..... | 305 | +| 6.3B.8.3.2 | Aggregate power tolerance for intra-band non-contiguous EN-DC ..... | 306 | +| 6.3B.8.3.3 | Aggregate power tolerance for inter-band EN-DC within FR1 (1 NR CC)..... | 307 | +| 6.3B.8.3.4 | Aggregate power tolerance for inter-band EN-DC including FR2 (1 NR CC)..... | 307 | +| 6.3E | Output power dynamics for V2X..... | 308 | +| 6.3E.0 | Minimum conformance requirements ..... | 308 | +| 6.3E.1 | Output power dynamics for intra-band V2X operation..... | 309 | +| 6.3E.2 | Output power dynamics for inter-band V2X operation..... | 309 | +| 6.4 | Transmit signal quality..... | 309 | +| 6.4A | Transmit Signal Quality for inter-band NR CA between FR and FR2 without EN-DC ..... | 309 | +| 6.4A.1 | Frequency error for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 309 | +| 6.4A.2 | Transmit Modulation Quality for inter-band NR CA without EN-DC ..... | 310 | +| 6.4A.2.1 | Error Vector Magnitude for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 310 | +| 6.4A.2.2 | Carrier Leakage for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 310 | +| 6.4A.2.3 | In-band Emissions for inter-band NR CA between FR 1 and FR 2 without EN-DC ..... | 310 | +| 6.4A.2.4 | EVM Equalizer Spectral Flatness for inter-band NR CA between FR 1 and FR 2 without EN-DC .. | 311 | +| 6.4B | Transmit Signal Quality for DC ..... | 311 | +| 6.4B.1 | Frequency error ..... | 311 | +| 6.4B.1.1 | Frequency error for Intra-band contiguous EN-DC..... | 311 | +| 6.4B.1.2 | Frequency error for Intra-band non-contiguous EN-DC ..... | 312 | + +| | | | +|----------------|-------------------------------------------------------------------------------------------|-----| +| 6.4B.1.3 | Frequency error for Inter-band EN-DC within FR1 (1 NR CC)..... | 313 | +| 6.4B.1.3a | Frequency Error for inter-band NE-DC within FR1 ..... | 314 | +| 6.4B.1.4 | Frequency Error for inter-band EN-DC including FR2 (1 NR CC) ..... | 314 | +| 6.4B.1.4_1 | Frequency Error for Inter-band EN-DC including FR2 (>1 NR CC)..... | 315 | +| 6.4B.1.4_1.1 | Frequency Error for Inter-band EN-DC including FR2 (2 NR CCs)..... | 315 | +| 6.4B.1.4_1.2 | Frequency Error for Inter-band EN-DC including FR2 (3 NR CCs)..... | 316 | +| 6.4B.1.4_1.3 | Frequency Error for Inter-band EN-DC including FR2 (4 NR CCs)..... | 317 | +| 6.4B.1.4D | Frequency error for inter-band EN-DC including FR2 for UL-MIMO ..... | 318 | +| 6.4B.2 | Transmit Modulation Quality for DC ..... | 319 | +| 6.4B.2.1 | Transmit Modulation Quality for intra-band contiguous EN-DC ..... | 319 | +| 6.4B.2.1.1 | Error Vector Magnitude for intra-band contiguous EN-DC ..... | 319 | +| 6.4B.2.1.2 | Carrier Leakage for intra-band contiguous EN-DC ..... | 320 | +| 6.4B.2.1.3 | In-band Emissions for intra-band contiguous EN-DC ..... | 321 | +| 6.4B.2.1.4 | EVM Equalizer Flatness for intra-band contiguous EN-DC..... | 326 | +| 6.4B.2.2 | Transmit Modulation Quality for intra-band non-contiguous EN-DC ..... | 327 | +| 6.4B.2.2.1 | Error Vector Magnitude for intra-band non-contiguous EN-DC ..... | 327 | +| 6.4B.2.2.2 | Carrier Leakage for intra-band non-contiguous EN-DC..... | 329 | +| 6.4B.2.2.3 | In-band Emissions for intra-band non-contiguous EN-DC..... | 330 | +| 6.4B.2.2.4 | EVM Equalizer Flatness for intra-band non-contiguous EN-DC ..... | 331 | +| 6.4B.2.3 | Transmit Modulation Quality for inter-band EN-DC within FR1 ..... | 332 | +| 6.4B.2.3.1 | Error Vector Magnitude for inter-band EN-DC within FR1 (1 NR CC) ..... | 332 | +| 6.4B.2.3.2 | Carrier Leakage for inter-band EN-DC within FR1 (1 NR CC)..... | 333 | +| 6.4B.2.3.3 | In-band Emissions for inter-band EN-DC within FR1 (1 NR CC)..... | 334 | +| 6.4B.2.3.4 | EVM Equalizer Flatness for inter-band EN-DC within FR1 (1 NR CC)..... | 334 | +| 6.4B.2.3a | Transmit Modulation Quality for inter-band NE-DC within FR1 ..... | 335 | +| 6.4B.2.3a.1 | Error Vector Magnitude for inter-band NE-DC within FR1 ..... | 335 | +| 6.4B.2.3a.2 | Carrier Leakage for inter-band NE-DC within FR1..... | 335 | +| 6.4B.2.3a.3 | In-band Emissions for inter-band NE-DC within FR1..... | 335 | +| 6.4B.2.3a.4 | EVM Equalizer Flatness for inter-band NE-DC within FR1 (1 NR CC)..... | 335 | +| 6.4B.2.4 | Transmit Modulation Quality for inter-band EN-DC including FR2 ..... | 336 | +| 6.4B.2.4.1 | Error Vector Magnitude for inter-band EN-DC including FR2 (1 NR CC)..... | 336 | +| 6.4B.2.4.1a | Error Vector Magnitude with Power Boost for inter-band EN-DC including FR2 (1 NR CC)..... | 337 | +| 6.4B.2.4.1_1 | Error Vector Magnitude for inter-band EN-DC including FR2 (>1 NR CC)..... | 338 | +| 6.4B.2.4.1_1.1 | Error Vector Magnitude for inter-band EN-DC including FR2 (2 NR CCs)..... | 338 | +| 6.4B.2.4.1_1.2 | Error Vector Magnitude for inter-band EN-DC including FR2 (3 NR CCs)..... | 339 | +| 6.4B.2.4.1_1.3 | Error Vector Magnitude for inter-band EN-DC including FR2 (4 NR CCs)..... | 339 | +| 6.4B.2.4.1_1.4 | Error Vector Magnitude for inter-band EN-DC including FR2 (5 NR CCs)..... | 340 | +| 6.4B.2.4.1_1.5 | Error Vector Magnitude for inter-band EN-DC including FR2 (6 NR CCs)..... | 341 | +| 6.4B.2.4.1_1.6 | Error Vector Magnitude for inter-band EN-DC including FR2 (7 NR CCs)..... | 342 | +| 6.4B.2.4.1_1.7 | Error Vector Magnitude for inter-band EN-DC including FR2 (8 NR CCs)..... | 343 | +| 6.4B.2.4.1D | Error Vector Magnitude for inter-band EN-DC including FR2 for UL MIMO..... | 344 | +| 6.4B.2.4.2 | Carrier Leakage for inter-band EN-DC including FR2 (1 NR CC)..... | 345 | +| 6.4B.2.4.2D | Carrier Leakage for inter-band EN-DC including FR2 for UL MIMO ..... | 346 | +| 6.4B.2.4.2_1 | Carrier Leakage for inter-band EN-DC including FR2 (>1 NR CC)..... | 347 | +| 6.4B.2.4.2_1.1 | Carrier Leakage for inter-band EN-DC including FR2 (2 NR CCs)..... | 347 | +| 6.4B.2.4.2_1.2 | Carrier Leakage for inter-band EN-DC including FR2 (3 NR CCs)..... | 348 | +| 6.4B.2.4.2_1.3 | Carrier Leakage for inter-band EN-DC including FR2 (4 NR CCs)..... | 349 | +| 6.4B.2.4.2_1.4 | Carrier Leakage for inter-band EN-DC including FR2 (5 NR CCs)..... | 349 | +| 6.4B.2.4.2_1.5 | Carrier Leakage for inter-band EN-DC including FR2 (6 NR CCs)..... | 350 | +| 6.4B.2.4.2_1.6 | Carrier Leakage for inter-band EN-DC including FR2 (7 NR CCs)..... | 351 | +| 6.4B.2.4.2_1.7 | Carrier Leakage for inter-band EN-DC including FR2 (8 NR CCs)..... | 352 | +| 6.4B.2.4.3 | In-band Emissions for inter-band EN-DC including FR2 (1 NR CC)..... | 353 | +| 6.4B.2.4.3D | In-band Emissions for inter-band EN-DC including FR2 for UL MIMO ..... | 354 | +| 6.4B.2.4.3_1 | In-band Emissions for inter-band EN-DC including FR2 (>1 NR CC)..... | 355 | +| 6.4B.2.4.3_1.1 | In-band Emissions for inter-band EN-DC including FR2 (2 NR CCs)..... | 355 | +| 6.4B.2.4.3_1.2 | In-band Emissions for inter-band EN-DC including FR2 (3 NR CCs)..... | 356 | +| 6.4B.2.4.3_1.3 | In-band Emissions for inter-band EN-DC including FR2 (4 NR CCs)..... | 356 | +| 6.4B.2.4.3_1.4 | In-band Emissions for inter-band EN-DC including FR2 (5 NR CCs)..... | 357 | +| 6.4B.2.4.3_1.5 | In-band Emissions for inter-band EN-DC including FR2 (6 NR CCs)..... | 358 | +| 6.4B.2.4.3_1.6 | In-band Emissions for inter-band EN-DC including FR2 (7 NR CCs)..... | 359 | +| 6.4B.2.4.3_1.7 | In-band Emissions for inter-band EN-DC including FR2 (8 NR CCs)..... | 360 | +| 6.4B.2.4.4 | EVM Equalizer Flatness for inter-band EN-DC including FR2 (1 NR CC)..... | 361 | + +| | | | +|----------------|---------------------------------------------------------------------------------------------------|-----| +| 6.4B.2.4.4D | EVM Equalizer Flatness for inter-band EN-DC including FR2 for UL MIMO ..... | 362 | +| 6.4B.2.4.5 | EVM spectral flatness for pi/2 BPSK modulation for inter-band EN-DC including FR2 (1 NR CC) ..... | 363 | +| 6.4E | Transmit signal quality for V2X operation in FR1 ..... | 364 | +| 6.4E.1 | Frequency error for V2X ..... | 364 | +| 6.4E.1.0 | Minimum conformance requirements..... | 364 | +| 6.4E.1.1 | Frequency error for Intra-band V2X..... | 364 | +| 6.4E.1.2 | Frequency error for Inter-band V2X..... | 364 | +| 6.4E.2 | Transmit modulation quality for V2X..... | 364 | +| 6.4E.2.1 | Error Vector Magnitude for V2X ..... | 364 | +| 6.4E.2.1.1 | Error Vector Magnitude for intra-band V2X ..... | 365 | +| 6.4E.2.1.2 | Error Vector Magnitude for Inter-band V2X ..... | 365 | +| 6.4E.2.2 | Carrier leakage for V2X ..... | 365 | +| 6.4E.2.2.1 | Carrier leakage for intra-band V2X ..... | 365 | +| 6.4E.2.3 | In-band emissions for V2X..... | 365 | +| 6.4E.2.3.1 | In-band emissions for intra-band V2X..... | 366 | +| 6.5 | Output RF spectrum emissions ..... | 366 | +| 6.5A | Output RF spectrum emissions for CA ..... | 366 | +| 6.5A.1 | Occupied bandwidth for CA without EN-DC ..... | 366 | +| 6.5A.2 | Out-of-band emissions for CA without EN-DC..... | 366 | +| 6.5A.2.1 | Spectrum emissions mask for CA without EN-DC ..... | 366 | +| 6.5A.2.2 | Additional Spectrum emissions mask for CA without EN-DC ..... | 366 | +| 6.5A.2.3 | Adjacent channel leakage ratio for CA without EN-DC ..... | 367 | +| 6.5A.3 | Spurious emissions for CA without EN-DC ..... | 367 | +| 6.5A.3.1 | Inter-band CA between FR1 and FR2 ..... | 367 | +| 6.5B | Output RF spectrum emissions for DC ..... | 367 | +| 6.5B.1 | Occupied bandwidth for EN-DC ..... | 367 | +| 6.5B.1.1 | Occupied bandwidth for Intra-Band Contiguous EN-DC..... | 367 | +| 6.5B.1.2 | Occupied bandwidth for Intra-Band Non-Contiguous EN-DC ..... | 370 | +| 6.5B.1.3 | Occupied bandwidth for Inter-Band EN-DC within FR1 (1 NR CC) ..... | 371 | +| 6.5B.1.4 | Occupied bandwidth for Inter-Band EN-DC including FR2 (1 NR CC) ..... | 371 | +| 6.5B.1.4_1 | Occupied bandwidth for Inter-band EN-DC including FR2 (>1 NR CC)..... | 372 | +| 6.5B.1.4_1.1 | Occupied bandwidth for Inter-band EN-DC including FR2 (2 NR CCs)..... | 372 | +| 6.5B.1.4_1.2 | Occupied bandwidth for Inter-band EN-DC including FR2 (3 NR CCs)..... | 373 | +| 6.5B.1.4_1.3 | Occupied bandwidth for Inter-band EN-DC including FR2 (4 NR CCs)..... | 374 | +| 6.5B.1.4D | Occupied bandwidth for inter-band EN-DC including FR2 for UL MIMO..... | 375 | +| 6.5B.2 | Out-of-band emissions for EN-DC..... | 376 | +| 6.5B.2.1 | Out-of-band emissions for Intra-band contiguous EN-DC..... | 376 | +| 6.5B.2.1.1 | Spectrum emissions mask for intra-band contiguous EN-DC ..... | 376 | +| 6.5B.2.1.2 | Additional spectrum emissions mask for intra-band contiguous EN-DC..... | 384 | +| 6.5B.2.1.3 | Adjacent channel leakage ratio for intra-band contiguous EN-DC..... | 389 | +| 6.5B.2.2 | Out-of-band emissions for Intra-band non-contiguous EN-DC ..... | 391 | +| 6.5B.2.2.1 | Spectrum emissions mask for intra-band non-contiguous EN-DC..... | 391 | +| 6.5B.2.2.2 | Additional Spectrum emissions mask for intra-band non-contiguous EN-DC ..... | 393 | +| 6.5B.2.2.3 | Adjacent channel leakage ratio for intra-band non-contiguous EN-DC ..... | 395 | +| 6.5B.2.3 | Out-of-band emissions for Inter-band EN-DC within FR1 ..... | 397 | +| 6.5B.2.3.1 | Spectrum emissions mask for Inter-band EN-DC within FR1 (1 NR CC)..... | 397 | +| 6.5B.2.3.2 | Additional Spectrum emissions mask for Inter-band EN-DC within FR1 (1 NR CC)..... | 397 | +| 6.5B.2.3.3 | Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) ..... | 398 | +| 6.5B.2.3.3.1 | NR - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC)..... | 398 | +| 6.5B.2.3.3.2 | UTRA - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) ..... | 399 | +| 6.5B.2.3a | Out-of-band emissions for Inter-band NE-DC within FR1 ..... | 400 | +| 6.5B.2.3a.1 | Spectrum emissions mask for Inter-band NE-DC within FR1..... | 400 | +| 6.5B.2.3a.2 | Additional Spectrum emissions mask for Inter-band NE-DC within FR1..... | 400 | +| 6.5B.2.3a.3 | Adjacent channel leakage ratio for inter-band NE-DC within FR1 ..... | 400 | +| 6.5B.2.4 | Out-of-band emissions for Inter-band EN-DC including FR2 ..... | 400 | +| 6.5B.2.4.1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (1 NR CC) ..... | 400 | +| 6.5B.2.4.1a | Spectrum emissions mask with Power Boost for Inter-band EN-DC including FR2 (1 NR CC) ..... | 401 | +| 6.5B.2.4.1_1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (>1 NR CC)..... | 402 | +| 6.5B.2.4.1_1.1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (2 NR CCs)..... | 402 | +| 6.5B.2.4.1_1.2 | Spectrum emissions mask for Inter-band EN-DC including FR2 (3 NR CCs)..... | 403 | + +| | | | +|----------------|-----------------------------------------------------------------------------------------------------|-----| +| 6.5B.2.4.1_1.3 | Spectrum emissions mask for Inter-band EN-DC including FR2 (4 NR CCs)..... | 404 | +| 6.5B.2.4.1D | Spectrum emissions mask for inter-band EN-DC including FR2 for UL MIMO..... | 405 | +| 6.5B.2.4.3 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (1 NR CC) ..... | 405 | +| 6.5B.2.4.3_1 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (>1 NR CC)..... | 406 | +| 6.5B.2.4.3_1.1 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (2 NR CCs)..... | 406 | +| 6.5B.2.4.3_1.2 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (3 NR CCs)..... | 407 | +| 6.5B.2.4.3_1.3 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (4 NR CCs)..... | 408 | +| 6.5B.2.4.3_1.4 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (5 NR CCs)..... | 409 | +| 6.5B.2.4.3_1.5 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (6 NR CCs)..... | 410 | +| 6.5B.2.4.3_1.6 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (7 NR CCs)..... | 411 | +| 6.5B.2.4.3_1.7 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (8 NR CCs)..... | 412 | +| 6.5B.2.4D.3 | Adjacent channel leakage ratio for inter-band EN-DC including FR2 for UL MIMO ..... | 413 | +| 6.5B.3 | Spurious emissions for EN-DC ..... | 414 | +| 6.5B.3.1 | Spurious Emissions for intra-band contiguous EN-DC..... | 414 | +| 6.5B.3.1.1 | General spurious emissions for intra-band contiguous EN-DC..... | 414 | +| 6.5B.3.1.2 | Spurious emission band UE co-existence for intra-band contiguous EN-DC ..... | 416 | +| 6.5B.3.2 | Spurious Emissions for intra-band non-contiguous EN-DC..... | 419 | +| 6.5B.3.2.1 | General spurious emissions for Intra-band non-contiguous EN-DC ..... | 419 | +| 6.5B.3.2.2 | Spurious emission band UE co-existence for intra-band non-contiguous EN-DC ..... | 421 | +| 6.5B.3.3 | Spurious Emissions for Inter-band EN-DC within FR1 ..... | 424 | +| 6.5B.3.3.1 | General spurious emissions for Inter-band EN-DC within FR1 ..... | 424 | +| 6.5B.3.3.2 | Spurious emission band UE co-existence for Inter-band within FR1 ..... | 440 | +| 6.5B.3.3a | Inter-band NE-DC within FR1 ..... | 507 | +| 6.5B.3.3a.1 | General Spurious Emissions for Inter-band NE-DC within FR1 ..... | 507 | +| 6.5B.3.3a.2 | Spurious emission band UE co-existence for Inter-band NE-DC within FR1..... | 507 | +| 6.5B.3.4 | Spurious Emissions for Inter-band including FR2 ..... | 507 | +| 6.5B.3.4.1 | General Spurious Emissions for Inter-band including FR2 (1 NR CC)..... | 507 | +| 6.5B.3.4.1a | General Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC)..... | 508 | +| 6.5B.3.4.1_1 | General Spurious emissions for Inter-band EN-DC including FR2 (>1 NR CC)..... | 509 | +| 6.5B.3.4.1_1.1 | General Spurious emissions for Inter-band EN-DC including FR2 (2 NR CCs)..... | 509 | +| 6.5B.3.4.1_1.2 | General Spurious emissions for Inter-band EN-DC including FR2 (3 NR CCs)..... | 510 | +| 6.5B.3.4.1_1.3 | General Spurious emissions for Inter-band EN-DC including FR2 (4 NR CCs)..... | 511 | +| 6.5B.3.4.1_1.4 | General Spurious emissions for Inter-band EN-DC including FR2 (5 NR CCs)..... | 512 | +| 6.5B.3.4.1_1.5 | General Spurious emissions for Inter-band EN-DC including FR2 (6 NR CCs)..... | 513 | +| 6.5B.3.4.1_1.6 | General Spurious emissions for Inter-band EN-DC including FR2 (7 NR CCs)..... | 514 | +| 6.5B.3.4.1_1.7 | General Spurious emissions for Inter-band EN-DC including FR2 (8 NR CCs)..... | 515 | +| 6.5B.3.4.1D | General Spurious Emissions for inter-band EN-DC including FR2 for UL MIMO..... | 516 | +| 6.5B.3.4.2 | Spurious emission band UE co-existence for Inter-band including FR2 (1 NR CC) ..... | 516 | +| 6.5B.3.4.2a | Spurious emission band UE co-existence with Power Boost for Inter-band including FR2 (1 NR CC)..... | 517 | +| 6.5B.3.4.2_1 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (>1 NR CC)..... | 518 | +| 6.5B.3.4.2_1.1 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (2 NR CCs)..... | 518 | +| 6.5B.3.4.2_1.2 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (3 NR CCs)..... | 519 | +| 6.5B.3.4.2_1.3 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (4 NR CCs)..... | 520 | +| 6.5B.3.4.2_1.4 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (5 NR CCs)..... | 521 | +| 6.5B.3.4.2_1.5 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (6 NR CCs)..... | 522 | +| 6.5B.3.4.2_1.6 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (6 NR CCs)..... | 523 | +| 6.5B.3.4.2_1.7 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (8 NR CCs)..... | 524 | +| 6.5B.3.4.2D | Spurious emission band UE co-existence for inter-band EN-DC including FR2 for UL MIMO..... | 525 | +| 6.5B.3.5 | Spurious emissions for Inter-band including FR1 and FR2 ..... | 526 | +| 6.5B.3.5.1 | General Spurious Emissions for Inter-band including FR1 and FR2..... | 526 | +| 6.5B.3.5.2 | Spurious emission band UE co-existence for Inter-band including FR1 and FR2 ..... | 526 | +| 6.5B.4 | Additional Spurious Emissions for EN-DC ..... | 527 | +| 6.5B.4.1 | Additional Spurious Emissions for Intra-band contiguous EN-DC..... | 527 | +| 6.5B.4.2 | Additional Spurious Emissions for Intra-band non-contiguous EN-DC ..... | 530 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------|-----| +| 6.5B.4.3 | Additional Spurious Emissions for Inter-band EN-DC within FR1 (1 NR CC) ..... | 531 | +| 6.5B.4.4 | Additional Spurious Emissions for Inter-band including FR2 (1 NR CC)..... | 532 | +| 6.5B.4.4a | Additional Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) ..... | 532 | +| 6.5B.4.4_1 | Additional Spurious Emissions for Inter-band including FR2 (>1 NR CC)..... | 533 | +| 6.5B.4.4_1.1 | Additional Spurious Emissions for Inter-band including FR2 (2 NR CC)..... | 533 | +| 6.5B.4.4_1.2 | Additional Spurious Emissions for Inter-band including FR2 (3 NR CC)..... | 534 | +| 6.5B.4.4_1.3 | Additional Spurious Emissions for Inter-band including FR2 (4 NR CC)..... | 535 | +| 6.5B.5 | Transmit intermodulation ..... | 536 | +| 6.5B.5.1 | Transmit intermodulation for Intra-band contiguous EN-DC ..... | 536 | +| 6.5B.5.2 | Transmit intermodulation for Intra-band non-contiguous EN-DC ..... | 536 | +| 6.5B.5.3 | Transmit intermodulation for Inter-band EN-DC within FR1 (1 NR CC) ..... | 537 | +| 6.5B.5.3a | Transmit Intermodulation for Inter-band NE-DC within FR1..... | 537 | +| 6.5B.5.4 | Transmit intermodulation for Inter-band EN-DC including FR2 ..... | 538 | +| 6.5B.5.5 | Transmit intermodulation for Inter-band EN-DC including both FR1 and FR2 ..... | 538 | +| 6.5E | Output RF spectrum emissions for V2X operation in FR1 ..... | 538 | +| 6.5E.1 | Occupied bandwidth for V2X ..... | 538 | +| 6.5E.1.0 | Minimum conformance requirements..... | 538 | +| 6.5E.1.1 | Occupied bandwidth for intra-band V2X ..... | 538 | +| 6.5E.1.2 | Occupied bandwidth for inter-band V2X ..... | 538 | +| 6.5E.2 | Out of band emission for V2X ..... | 538 | +| 6.5E.2.0 | Minimum conformance requirements..... | 538 | +| 6.5E.2.1 | Out of band emission for intra-band V2X ..... | 539 | +| 6.5E.2.2 | Out of band emission for inter-band V2X ..... | 539 | +| 6.5E.3 | Spurious emissions for V2X..... | 539 | +| 6.5E.3.1 | General spurious emissions for V2X..... | 539 | +| 6.5E.3.1.1 | General spurious emissions for intra-band V2X..... | 539 | +| 6.5E.3.1.2 | General spurious emissions for inter-band V2X..... | 540 | +| 6.5E.4 | Transmit intermodulation for V2X..... | 540 | +| 6.5E.4.0 | Minimum conformance requirements..... | 540 | +| 6.5E.4.1 | Transmit intermodulation for intra-band V2X..... | 540 | +| 6.5E.4.2 | Transmit intermodulation for inter-band V2X..... | 540 | +| 6.6B | Beam Correspondence for EN-DC..... | 541 | +| 6.6B.4 | Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP ..... | 541 | +| 6.6B.5 | Enhanced Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP ..... | 542 | +| 7 | Receiver characteristics..... | 543 | +| 7.1 | General ..... | 543 | +| 7.2 | Void..... | 544 | +| 7.3 | Void..... | 544 | +| 7.3A | Reference sensitivity for CA without EN-DC..... | 544 | +| 7.3A.1 | General ..... | 544 | +| 7.3A.2 | Reference sensitivity power level for CA without EN-DC ..... | 544 | +| 7.3A.3 | $\Delta R_{IB,c}$ for CA without EN-DC..... | 544 | +| 7.3A.3.1 | $\Delta R_{IB,c}$ for Inter-band CA between FR1 and FR2 without EN-DC..... | 545 | +| 7.3A.4 | Void..... | 545 | +| 7.3B | Reference sensitivity level for DC ..... | 545 | +| 7.3B.1 | General ..... | 545 | +| 7.3B.2 | Reference sensitivity for EN-DC..... | 545 | +| 7.3B.2.0 | Minimum Conformance Requirements of Reference sensitivity for EN-DC..... | 545 | +| 7.3B.2.0.1 | Intra-band contiguous EN-DC ..... | 545 | +| 7.3B.2.0.2 | Intra-band non-contiguous EN-DC ..... | 546 | +| 7.3B.2.0.3 | Inter-band EN-DC within FR1 ..... | 546 | +| 7.3B.2.0.3a | Inter-band NE-DC within FR1 ..... | 574 | +| 7.3B.2.0.4 | Inter-band EN-DC including FR2 ..... | 574 | +| 7.3B.2.0.5 | Inter-band EN-DC including both FR1 and FR2 ..... | 574 | +| 7.3B.2.1 | Reference sensitivity for Intra-band Contiguous EN-DC (2 CCs) ..... | 575 | +| 7.3B.2.2 | Reference sensitivity for Intra-band non-contiguous EN-DC (2 CCs)..... | 580 | +| 7.3B.2.3 | Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs)..... | 580 | +| 7.3B.2.3_1 | Reference sensitivity for EN-DC within FR1 (>2 CCs)..... | 615 | +| 7.3B.2.3_1.1 | Reference sensitivity for EN-DC within FR1 (3 CCs)..... | 615 | +| 7.3B.2.3_1.2 | Reference sensitivity for EN-DC within FR1 (4 CCs)..... | 650 | +| 7.3B.2.3_1.3 | Reference sensitivity for EN-DC within FR1 (5 CCs)..... | 655 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.3B.2.3_1.4 | Reference sensitivity for EN-DC within FR1 (6 CCs)........................................................................ | 658 | +| 7.3B.2.4 | Reference sensitivity for Inter-band EN-DC including FR2 (1 NR CC)............................................. | 658 | +| 7.3B.2.4_1 | Reference sensitivity for Inter-band EN-DC including FR2 (>1 NR CC) .......................................... | 659 | +| 7.3B.2.4_1.1 | Reference sensitivity for Inter-band EN-DC including FR2 (2 NR CCs).......................................... | 659 | +| 7.3B.2.4_1.2 | Reference sensitivity for Inter-band EN-DC including FR2 (3 NR CCs).......................................... | 660 | +| 7.3B.2.4_1.3 | Reference sensitivity for Inter-band EN-DC including FR2 (4 NR CCs).......................................... | 661 | +| 7.3B.2.4_1.4 | Reference sensitivity for Inter-band EN-DC including FR2 (5 NR CCs).......................................... | 661 | +| 7.3B.2.4_1.5 | Reference sensitivity for Inter-band EN-DC including FR2 (6 NR CCs).......................................... | 662 | +| 7.3B.2.4_1.6 | Reference sensitivity for Inter-band EN-DC including FR2 (7 NR CCs).......................................... | 663 | +| 7.3B.2.4_1.7 | Reference sensitivity for Inter-band EN-DC including FR2 (8 NR CCs).......................................... | 663 | +| 7.3B.2.4D | Reference sensitivity for inter-band EN-DC including FR2 for UL MIMO ........................................ | 664 | +| 7.3B.2.5 | Reference sensitivity for Inter-band EN-DC including FR1 and FR2 (3 CCs)................................... | 664 | +| 7.3B.2.5D | Reference sensitivity for inter-band EN-DC including FR1 and FR2 for UL MIMO ........................ | 664 | +| 7.3B.2.6 | Void ....................................................................................................................................................... | 665 | +| 7.3B.3 | $\Delta R_{IB,c}$ $\Delta R_{IB,NC}$ for EN-DC ........................................................................................................ | 665 | +| 7.3B.3.0 | General .................................................................................................................................................. | 665 | +| 7.3B.3.1 | Reference sensitivity $\Delta R_{IB,c}$ for Intra-band Contiguous EN-DC ..................................................... | 665 | +| 7.3B.3.2 | Reference sensitivity $\Delta R_{IB,c}$ for Intra-band non-contiguous EN-DC................................................ | 665 | +| 7.3B.3.3 | $\Delta R_{IB,c}$ for Inter-band EN-DC within FR1 ........................................................................................ | 666 | +| 7.3B.3.3.1 | $\Delta R_{IB,c}$ for EN-DC in two bands................................................................................................... | 666 | +| 7.3B.3.3.2 | $\Delta R_{IB,c}$ for EN-DC in three bands ................................................................................................. | 669 | +| 7.3B.3.3.3 | $\Delta R_{IB,c}$ for EN-DC in four bands ................................................................................................... | 674 | +| 7.3B.3.3.4 | $\Delta R_{IB,c}$ for EN-DC in five bands................................................................................................... | 678 | +| 7.3B.3.3.5 | $\Delta R_{IB,c}$ for EN-DC six bands ........................................................................................................ | 680 | +| 7.3B.3.3a | $\Delta R_{IB,c}$ for Inter-band NE-DC within FR1 ........................................................................................ | 680 | +| 7.3B.3.4 | Reference sensitivity for $\Delta R_{IB,c}$ Inter-band EN-DC including FR2................................................... | 680 | +| 7.3B.3.5 | Reference sensitivity for $\Delta R_{IB,c}$ Inter-band EN-DC including both FR1 and FR2........................... | 680 | +| 7.3B.4 | EIS Spherical Coverage for Inter-band EN-DC including FR2 (1 NR CC).......................................... | 680 | +| 7.4 | Void....................................................................................................................................................... | 681 | +| 7.4A | Maximum Input Level for CA ............................................................................................................. | 681 | +| 7.4B | Maximum Input Level for DC ............................................................................................................. | 681 | +| 7.4B.0 | Minimum conformance requirement ..................................................................................................... | 681 | +| 7.4B.0.1 | Intra-band contiguous EN-DC .......................................................................................................... | 681 | +| 7.4B.0.2 | Intra-band non-contiguous EN-DC................................................................................................... | 682 | +| 7.4B.0.3 | Inter-band EN-DC within FR1 ......................................................................................................... | 682 | +| 7.4B.0.4 | Inter-band EN-DC including FR2..................................................................................................... | 682 | +| 7.4B.0.5 | Inter-band EN-DC including both FR1 and FR2.............................................................................. | 682 | +| 7.4B.1 | Maximum Input Level for Intra-Band Contiguous EN-DC (2 CCs)..................................................... | 682 | +| 7.4B.2 | Maximum Input Level for Intra-Band Non-Contiguous EN-DC (2 CCs) ............................................ | 685 | +| 7.4B.3 | Maximum Input Level for Inter-band EN-DC within FR1 (1 NR CC)................................................. | 687 | +| 7.4B.3_1 | Maximum Input Level for EN-DC within FR1 (>2 CCs) ..................................................................... | 688 | +| 7.4B.3_1.1 | Maximum Input Level for EN-DC within FR1 (3 CCs)..................................................................... | 688 | +| 7.4B.3_1.2 | Maximum Input Level for EN-DC within FR1 (4 CCs)..................................................................... | 688 | +| 7.4B.3_1.3 | Maximum Input Level for EN-DC within FR1 (5 CCs)..................................................................... | 689 | +| 7.4B.3_1.4 | Maximum Input Level for EN-DC within FR1 (6 CCs)..................................................................... | 690 | +| 7.4B.3a | Maximum Input Level for inter-band NE-DC within FR1 (2 CCs)....................................................... | 691 | +| 7.4B.4 | Maximum Input Level for inter-band EN-DC including FR2 (1 NR CC)............................................. | 691 | +| 7.4B.4_1 | Maximum Input Level for inter-band EN-DC including FR2 (>1 NR CC)........................................... | 692 | +| 7.4B.4_1.1 | Maximum Input Level for Inter-Band EN-DC including FR2 (2 NR CCs)....................................... | 692 | +| 7.4B.4_1.2 | Maximum Input Level for Inter-Band EN-DC including FR2 (3 NR CCs)....................................... | 693 | +| 7.4B.4_1.3 | Maximum Input Level for Inter-Band EN-DC including FR2 (4 NR CCs)....................................... | 694 | +| 7.4B.4_1.4 | Maximum Input Level for Inter-Band EN-DC including FR2 (5 NR CCs)....................................... | 695 | +| 7.4B.4D | Maximum Input Level for inter-band EN-DC including FR2 for UL MIMO ....................................... | 696 | +| 7.4B.5 | Maximum Input Level for inter-band EN-DC including both FR1 and FR2......................................... | 696 | +| 7.4B.5D | Maximum Input Level for inter-band EN-DC including FR1 and FR2 for UL MIMO......................... | 696 | +| 7.5 | Void....................................................................................................................................................... | 697 | +| 7.5A | Adjacent Channel Selectivity for CA.................................................................................................... | 697 | +| 7.5B | Adjacent channel selectivity for DC ..................................................................................................... | 697 | +| 7.5B.0 | Minimum Conformance Requirements ................................................................................................. | 697 | +| 7.5B.0.1 | Intra-band contiguous EN-DC .......................................................................................................... | 697 | +| 7.5B.0.2 | Intra-band non-contiguous EN-DC................................................................................................... | 698 | +| 7.5B.0.3 | Inter-band EN-DC within FR1 ......................................................................................................... | 698 | + +| | | | +|--------------|-------------------------------------------------------------------------------------------|-----| +| 7.5B.0.3a | Inter-band NE-DC within FR1 ..... | 698 | +| 7.5B.0.4 | Inter-band EN-DC including FR2..... | 698 | +| 7.5B.0.4a | Inter-band NE-DC including FR2..... | 698 | +| 7.5B.0.5 | Inter-band EN-DC including both FR1 and FR2..... | 698 | +| 7.5B.1 | Adjacent Channel Selectivity for intra-band contiguous EN-DC (2 CCs)..... | 699 | +| 7.5B.2 | Adjacent Channel Selectivity for intra-band non-contiguous EN-DC (2 CCs)..... | 702 | +| 7.5B.3 | Adjacent Channel Selectivity for inter-band EN-DC within FR1 (1 NR CC) ..... | 703 | +| 7.5B.3_1 | Adjacent Channel Selectivity for EN-DC within FR1 (>2 CCs) ..... | 703 | +| 7.5B.3_1.1 | Adjacent Channel Selectivity for EN-DC within FR1 (2 NR CCs) ..... | 704 | +| 7.5B.3_1.2 | Adjacent Channel Selectivity for EN-DC within FR1 (3 NR CCs) ..... | 704 | +| 7.5B.3_1.3 | Adjacent Channel Selectivity for EN-DC within FR1 (4 NR CCs) ..... | 705 | +| 7.5B.3_1.4 | Adjacent Channel Selectivity for EN-DC within FR1 (5 NR CCs) ..... | 706 | +| 7.5B.3a | Adjacent Channel Selectivity for inter-band NE-DC within FR1 (2 CCs)..... | 707 | +| 7.5B.4 | Adjacent Channel Selectivity for inter-band EN-DC including FR2 (1 NR CC) ..... | 707 | +| 7.5B.4_1 | Adjacent Channel Selectivity for inter-band EN-DC including FR2 (>1 NR CC)..... | 708 | +| 7.5B.4_1.1 | Adjacent Channel Selectivity for inter-band EN-DC including FR2 (2 NR CCs)..... | 708 | +| 7.5B.4_1.2 | Void ..... | 710 | +| 7.5B.4_1.3 | Void ..... | 710 | +| 7.5B.4_1.4 | Void ..... | 710 | +| 7.5B.4D | Adjacent Channel Selectivity for inter-band EN-DC including FR2 for UL MIMO..... | 710 | +| 7.5B.5 | Adjacent Channel Selectivity for inter-band EN-DC including both FR1 and FR2 ..... | 710 | +| 7.5B.5D | Adjacent Channel Selectivity for inter-band EN-DC including FR1 and FR2 for UL MIMO ..... | 710 | +| 7.6 | Void..... | 710 | +| 7.6A | Blocking characteristics for CA ..... | 710 | +| 7.6B | Blocking characteristics for DC ..... | 711 | +| 7.6B.1 | General ..... | 711 | +| 7.6B.2 | Inband blocking for DC ..... | 711 | +| 7.6B.2.0 | Minimum Conformance Requirements ..... | 711 | +| 7.6B.2.0.1 | Intra-band contiguous EN-DC ..... | 711 | +| 7.6B.2.0.2 | Intra-band non-contiguous EN-DC ..... | 711 | +| 7.6B.2.0.3 | Inter-band EN-DC within FR1 ..... | 712 | +| 7.6B.2.0.3a | Inter-band NE-DC within FR1 ..... | 712 | +| 7.6B.2.0.4 | Inter-band EN-DC including FR2 ..... | 712 | +| 7.6B.2.0.5 | Inter-band EN-DC including both FR1 and FR2 ..... | 712 | +| 7.6B.2.1 | Inband blocking for intra-band contiguous EN-DC (2 CCs)..... | 712 | +| 7.6B.2.2 | Inband blocking for intra-band non-contiguous EN-DC (2 CCs)..... | 715 | +| 7.6B.2.3 | Inband blocking for inter-band EN-DC within FR1 (1 NR CC) ..... | 716 | +| 7.6B.2.3_1 | Inband blocking for EN-DC within FR1 (>2 CCs)..... | 717 | +| 7.6B.2.3_1.1 | Inband blocking for EN-DC within FR1 (3 CCs)..... | 717 | +| 7.6B.2.3_1.2 | Inband blocking for EN-DC within FR1 (4 CCs)..... | 720 | +| 7.6B.2.3_1.3 | Inband blocking for EN-DC within FR1 (5 CCs)..... | 723 | +| 7.6B.2.3_1.4 | Void..... | 724 | +| 7.6B.2.3a | In-band blocking for inter-band NE-DC within FR1 (2 CCs)..... | 724 | +| 7.6B.2.4 | Inband blocking for inter-band EN-DC including FR2 (1 NR CC) ..... | 724 | +| 7.6B.2.4_1 | Inband blocking for inter-band EN-DC including FR2 (>1 NR CC)..... | 725 | +| 7.6B.2.4_1.1 | Inband blocking for inter-band EN-DC including FR2 (2 NR CCs)..... | 725 | +| 7.6B.2.4_1.2 | Void..... | 725 | +| 7.6B.2.4_1.3 | Void..... | 725 | +| 7.6B.2.4_1.4 | Void..... | 725 | +| 7.6B.2.4D | Inband blocking for inter-band EN-DC including FR2 for UL MIMO..... | 726 | +| 7.6B.2.5 | Inband blocking for inter-band EN-DC including both FR1 and FR2 ..... | 726 | +| 7.6B.2.5D | Inband blocking for inter-band EN-DC including FR1 and FR2 for UL MIMO ..... | 726 | +| 7.6B.3 | Out-of-band blocking for DC ..... | 726 | +| 7.6B.3.0 | Minimum Conformance Requirements ..... | 726 | +| 7.6B.3.0.1 | Intra-band contiguous EN-DC ..... | 726 | +| 7.6B.3.0.2 | Intra-band non-contiguous EN-DC ..... | 727 | +| 7.6B.3.0.3 | Inter-band EN-DC within FR1 ..... | 727 | +| 7.6B.3.0.3a | Inter-band NE-DC within FR1 ..... | 728 | +| 7.6B.3.0.4 | Inter-band EN-DC including FR2 ..... | 729 | +| 7.6B.3.0.5 | Inter-band EN-DC including both FR1 and FR2 ..... | 729 | +| 7.6B.3.1 | Out-of-band blocking for intra-band contiguous EN-DC (2 CCs)..... | 729 | +| 7.6B.3.2 | Out-of-band blocking for intra-band non-contiguous EN-DC (2 CCs)..... | 732 | + +| | | | +|--------------|----------------------------------------------------------------------------|-----| +| 7.6B.3.3 | Out-of-band blocking for inter-band EN-DC within FR1 (2 CCs)..... | 733 | +| 7.6B.3.3_1 | Out-of-band blocking for EN-DC within FR1 (>2 CCs)..... | 741 | +| 7.6B.3.3_1.1 | Out-of-band blocking for EN-DC within FR1 (3 CCs)..... | 741 | +| 7.6B.3.3_1.2 | Out-of-band blocking for EN-DC within FR1 (4 CCs)..... | 744 | +| 7.6B.4 | Narrow band blocking for DC ..... | 748 | +| 7.6B.4.0 | Minimum Conformance Requirements ..... | 748 | +| 7.6B.4.0.1 | Intra-band contiguous EN-DC ..... | 748 | +| 7.6B.4.0.2 | Intra-band non-contiguous EN-DC ..... | 749 | +| 7.6B.4.0.3 | Inter-band EN-DC within FR1 ..... | 749 | +| 7.6B.4.0.3a | Inter-band NE-DC within FR1 ..... | 749 | +| 7.6B.4.0.4 | Inter-band EN-DC including FR2..... | 749 | +| 7.6B.4.0.5 | Inter-band EN-DC including both FR1 and FR2 ..... | 749 | +| 7.6B.4.1 | Narrow band blocking for intra-band contiguous EN-DC (2 CCs)..... | 750 | +| 7.6B.4.2 | Narrow band blocking for intra-band non-contiguous EN-DC (2 CCs)..... | 753 | +| 7.6B.4.3 | Narrow band blocking for inter-band EN-DC within FR1 (1 NR CC) ..... | 754 | +| 7.6B.4.3_1 | Narrow band blocking for EN-DC within FR1 (>2 CCs)..... | 755 | +| 7.6B.4.3_1.1 | Narrow band blocking for EN-DC within FR1 (3 CCs) ..... | 755 | +| 7.6B.4.3_1.2 | Narrow band blocking for EN-DC within FR1 (4 CCs) ..... | 758 | +| 7.6B.4.3_1.3 | Narrow band blocking for EN-DC within FR1 (5 CCs) ..... | 761 | +| 7.6B.4.3_1.4 | Void..... | 762 | +| 7.6B.4.3a | Narrow band blocking for inter-band NE-DC within FR1 (2 CCs) ..... | 762 | +| 7.6E | Blocking characteristics for V2X in FR1 ..... | 762 | +| 7.6E.0 | Minimum conformance requirements ..... | 762 | +| 7.6E.1 | In-band blocking for V2X operation ..... | 762 | +| 7.6E.2 | Out-of-band blocking for V2X operation..... | 762 | +| 7.7 | Void..... | 763 | +| 7.7A | Spurious response for CA ..... | 763 | +| 7.7B | Spurious response for DC ..... | 763 | +| 7.7B.0 | Minimum Conformance Requirements ..... | 763 | +| 7.7B.0.1 | Intra-band contiguous EN-DC ..... | 763 | +| 7.7B.0.2 | Intra-band non-contiguous EN-DC..... | 763 | +| 7.7B.0.3 | Inter-band EN-DC within FR1 ..... | 764 | +| 7.7B.0.3a | Inter-band NE-DC within FR1 ..... | 764 | +| 7.7B.0.4 | Inter-band EN-DC including FR2..... | 764 | +| 7.7B.0.5 | Inter-band EN-DC including both FR1 and FR2..... | 764 | +| 7.7B.1 | Spurious Response for intra-band contiguous EN-DC (2 CCs)..... | 764 | +| 7.7B.2 | Spurious Response for intra-band non-contiguous EN-DC (2 CCs)..... | 766 | +| 7.7B.3 | Spurious Response for inter-band EN-DC within FR1 (2 CCs)..... | 767 | +| 7.7B.3_1 | Spurious Response for EN-DC within FR1 (>2 CCs)..... | 771 | +| 7.7B.3_1.1 | Spurious Response for EN-DC within FR1 (3 CCs) ..... | 771 | +| 7.7B.3_1.2 | Spurious Response for EN-DC within FR1 (4 CCs) ..... | 773 | +| 7.7E | Spurious response for V2X in FR1 ..... | 775 | +| 7.7E.0 | Minimum conformance requirements ..... | 775 | +| 7.7E.1 | Spurious response for V2X operation ..... | 776 | +| 7.8 | Void..... | 776 | +| 7.8B | Intermodulation characteristics for DC ..... | 776 | +| 7.8B.1 | General ..... | 776 | +| 7.8B.2 | Wide band Intermodulation..... | 776 | +| 7.8B.2.0 | Minimum Conformance Requirements ..... | 776 | +| 7.8B.2.0.1 | Intra-band contiguous EN-DC ..... | 776 | +| 7.8B.2.0.2 | Intra-band non-contiguous EN-DC ..... | 776 | +| 7.8B.2.0.3 | Inter-band EN-DC within FR1 ..... | 777 | +| 7.8B.2.0.4 | Inter-band EN-DC including FR2..... | 777 | +| 7.8B.2.0.5 | Inter-band EN-DC including both FR1 and FR2 ..... | 777 | +| 7.8B.2.1 | Wideband Intermodulation for intra-band contiguous EN-DC (2 CCs)..... | 777 | +| 7.8B.2.2 | Wideband Intermodulation for intra-band non-contiguous EN-DC (2 CCs) ..... | 780 | +| 7.8B.2.3 | Wideband Intermodulation for inter-band EN-DC within FR1 (2 CCs) ..... | 781 | +| 7.8B.2.3_1 | Wideband Intermodulation for EN-DC within FR1 (>2 CCs) ..... | 782 | +| 7.8B.2.3_1.1 | Wideband Intermodulation for EN-DC within FR1 (3 CCs) ..... | 782 | +| 7.8B.2.3_1.2 | Wideband Intermodulation for EN-DC within FR1 (4 CCs) ..... | 785 | +| 7.8B.2.3_1.3 | Wideband Intermodulation for EN-DC within FR1 (5 CCs) ..... | 788 | +| 7.8B.2.3_1.4 | Wideband Intermodulation for EN-DC within FR1 (6 CCs)..... | 790 | + +| | | | +|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------| +| 7.8B.2.3a | Wideband Intermodulation for inter-band NE-DC within FR1 (2 CCs) ..... | 790 | +| 7.8B.2.4 to 7.8B.2.9 | Void ..... | 791 | +| 7.8E | Intermodulation characteristics for V2X operation in FR1 ..... | 791 | +| 7.8E.1 | Wide band Intermodulation for V2X ..... | 791 | +| 7.8E.1.0 | Minimum conformance requirements..... | 791 | +| 7.8E.1.1 | Wide band Intermodulation for V2X operation..... | 791 | +| 7.9 | Void..... | 791 | +| 7.9B | Spurious emissions for DC..... | 791 | +| 7.9B.0 | Minimum Conformance Requirements ..... | 791 | +| 7.9B.0.1 | Intra-band contiguous EN-DC ..... | 791 | +| 7.9B.0.2 | Intra-band non-contiguous EN-DC..... | 791 | +| 7.9B.0.3 | Inter-band EN-DC within FR1 ..... | 792 | +| 7.9B.0.4 | Inter-band EN-DC including FR2..... | 792 | +| 7.9B.0.5 | Inter-band EN-DC including both FR1 and FR2..... | 792 | +| 7.9B.1 | Spurious Emissions for intra-band contiguous EN-DC (2 CCs)..... | 792 | +| 7.9B.2 | Spurious Emissions for intra-band non-contiguous EN-DC (2 CCs)..... | 793 | +| 7.9B.3 | Spurious Emissions for inter-band EN-DC within FR1 (1 NR CC) ..... | 794 | +| 7.9B.3_1 | Spurious Emissions for EN-DC within FR1 (>2 CCs)..... | 795 | +| 7.9B.3_1.1 | Spurious Emissions for EN-DC within FR1 (3 CCs)..... | 795 | +| 7.9B.3a | Spurious Emissions for inter-band NE-DC within FR1 (2 CCs) ..... | 795 | +| 7.9B.4 | Spurious Emissions for inter-band EN-DC including FR2 (1 NR CC)..... | 796 | +| 7.9B.5 | Spurious Emissions for inter-band EN-DC including both FR1 and FR2 (3 CCs)..... | 797 | +| Annex A (normative): Measurement Channels..... | | 798 | +| A.1 | General..... | 798 | +| A.2 | UL reference measurement channels for E-UTRA TDD Config 2 ..... | 798 | +| A.2.1 | General ..... | 798 | +| A.2.2 | Reference measurement channels for E-UTRA..... | 799 | +| A.2.2.1 | Full RB allocation..... | 799 | +| A.2.2.1.1 | QPSK ..... | 799 | +| A.2.2.1.2 | 16-QAM..... | 799 | +| A.2.2.1.3 | 64-QAM..... | 800 | +| A.2.2.1.4 | 256 QAM..... | 801 | +| A.2.2.2 | Partial RB allocation..... | 802 | +| A.2.2.2.1 | QPSK ..... | 802 | +| A.2.2.2.2 | 16-QAM..... | 804 | +| A.2.2.2.3 | 64-QAM..... | 807 | +| A.2.2.2.4 | 256 QAM..... | 810 | +| A.3 | DL reference measurement channels for E-UTRA..... | 811 | +| A.3.1 | General ..... | 811 | +| Annex B (normative): Propagation Conditions..... | | 816 | +| Annex C (normative): Downlink Physical Channels ..... | | 817 | +| Annex D (normative): Characteristics of the Interfering Signal ..... | | 818 | +| Annex E (normative): Global In-Channel Tx Test ..... | | 818 | +| Annex F (informative): Measurement uncertainties and Test Tolerances ..... | | 819 | +| F.1 | Acceptable uncertainty of Test System (normative)..... | 819 | +| F.1.0 | General ..... | 819 | +| F.1.0.1 | Conducted Measurements ..... | 819 | +| F.1.0.2 | Radiated Measurements..... | 819 | +| F.1.1 | Measurement of test environments ..... | 819 | +| F.1.1.1 | Conducted Measurements ..... | 819 | +| F.1.1.2 | Radiated Measurements..... | 819 | +| F.1.2 | Measurement of transmitter ..... | 820 | +| F.1.3 | Measurement of receiver..... | 831 | + +| | | | +|-------------------------------|------------------------------------------------------------------------|------------| +| F.2 | Interpretation of measurement results (normative) ..... | 835 | +| F.3 | Test Tolerance and Derivation of Test Requirements (informative) ..... | 835 | +| F.3.1 | Measurement of test environments ..... | 835 | +| F.3.2 | Measurement of transmitter ..... | 836 | +| F.3.3 | Measurement of receiver ..... | 846 | +| F.4 | Uplink power window ..... | 849 | +| F.4.1 | Introduction ..... | 849 | +| F.4.2 | Setting the power window above a requirement ..... | 850 | +| F.4.2.1 | NR FR1 ..... | 850 | +| F.4.2.2 | NR FR2 ..... | 851 | +| F.4.2.3 | E-UTRA ..... | 852 | +| F.4.3 | Setting the power window below a requirement ..... | 853 | +| F.4.3.1 | NR FR1 ..... | 853 | +| F.4.3.2 | NR FR2 ..... | 854 | +| F.4.3.3 | E-UTRA ..... | 855 | +| F.4.4 | Setting the power window centred on a target value ..... | 856 | +| F.4.4.1 | NR FR1 ..... | 856 | +| F.4.4.2 | NR FR2 ..... | 857 | +| F.4.4.3 | E-UTRA ..... | 858 | +| Annex G (normative): | Uplink Physical Channels ..... | 860 | +| Annex H (normative): | Statistical Testing ..... | 861 | +| H.1 | General ..... | 861 | +| H.2 | Statistical testing of receiver characteristics ..... | 861 | +| H.2.1 | General ..... | 861 | +| H.2.2 | Mapping throughput to error ratio ..... | 861 | +| H.2.3 | Design of the test ..... | 862 | +| H.2.4 | Numerical definition of the pass fail limits ..... | 863 | +| H.2.5 | Pass fail decision rules ..... | 864 | +| Annex I (normative): | Void 865 | | +| Annex J (normative): | Test applicability per permitted test method ..... | 866 | +| Annex K (normative): | EIRP, TRP, and EIS measurement procedures ..... | 867 | +| Annex L (normative): | Void 868 | | +| Annex M (normative): | Dual uplink interferer ..... | 869 | +| Annex N (normative): | Modified MPR behaviour ..... | 870 | +| N.1 | Indication of modified MPR behaviour ..... | 870 | +| Annex O (informative): | Change history ..... | 871 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +The present document is part 3 of a multi-part Technical Specification (TS) covering the New Radio (NR) User Equipment (UE) conformance specification, which is divided in the following parts: + +- TS 38.521-1 [8]: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone" (the present document). +- TS 38.521-2 [9]: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". +- TS 38.521-3: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- TS 38.521-4 [22]: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 4: Performance". +- TS 38.522 [14]: "NR; User Equipment (UE) conformance specification; Applicability of RF and RRM test cases". +- TS 38.533 [23]: "NR; User Equipment (UE) conformance specification; Radio resource management (RRM)". + +# 1 Scope + +The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain RF characteristics for carrier aggregation between Range 1 and Range 2 and additional requirements for EN-DC, NE-DC and NGEN-DC. + +The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "*definition and applicability*" part of the test. + +For example only Release 15 and later UE declared to support 5G-NR shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" +- [2] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [3] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [4] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- [5] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [6] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". +- [7] 3GPP TR 38.905: "NR; Derivation of test points for radio transmission and reception conformance test cases". +- [8] 3GPP TS 38.521-1: " User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone. +- [9] 3GPP TS 38.521-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". +- [10] 3GPP TS 36.521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Conformance testing" +- [11] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing". +- [12] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". + +- [13] 3GPP TS 36.211: "E-UTRA; Physical channels and modulation". +- [14] 3GPP TS 38.522: "NR; User Equipment (UE) conformance specification; Applicability of radio transmission, radio reception and radio resource management test cases". +- [15] Void. +- [16] 3GPP TS 38.306: "NR: User Equipment (UE) radio access capabilities". +- [17] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [18] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [19] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [20] 3GPP TS 36.213: "E-UTRA Physical layer procedures". +- [21] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [22] 3GPP TS 38.521-4: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 4: Performance". +- [23] 3GPP TS 38.533: "NR; User Equipment (UE) conformance specification; Radio resource management (RRM)". +- [24] 3GPP TS 36.214: "E-UTRA; Physical layer; Measurements". +- [25] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Con-current operation:** The simultaneous transmission and reception of sidelink and Uu interfaces while operation is agnostic of the service used on each interface. + +### 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\Delta R_{IB,c}$ | Allowed reference sensitivity relaxation due to support for CA or DC operation, for serving cell $c$ | +| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for CA or DC operation, for serving cell $c$ | +| $BW_{E-UTRA\_Channel}$ | Channel bandwidth of E-UTRA carrier | +| $BW_{E-UTRA\_Channel\_CA}$ | Channel bandwidth of E-UTRA sub-block which is composed of intra-band contiguous CA E-UTRA carriers | +| $BW_{NR\_Channel}$ | Channel bandwidth of NR carrier | +| $BW_{NR\_Channel\_CA}$ | Channel bandwidth of NR sub-block which is composed of intra-band contiguous CA NR carriers | +| Ceil( $x$ ) | Rounding upwards; ceil( $x$ ) is the smallest integer such that $\text{ceil}(x) \geq x$ | +| $EN-DC_{ACLR}$ | The ratio of the filtered mean power centred on the aggregated sub-block bandwidth ENBW to the filtered mean power centred on an adjacent bandwidth of the same size ENBW | +| $E-UTRA_{ACLR}$ | E-UTRA ACLR | +| $F_C$ | RF reference frequency for the carrier centre on the channel raster | +| $F_{DL\_low}$ | The lowest frequency of the downlink operating band | +| $F_{DL\_high}$ | The highest frequency of the downlink operating band | + +| | | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $F_{\text{Interferer}}$ | Frequency of the interferer | +| $F_{\text{Interferer}}(\text{offset})$ | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL\_high}}$ | The highest frequency of the uplink operating band | +| $F_{\text{OOB}}$ | The boundary between the NR out of band emission and spurious emission domains | +| $L_{\text{CRB}}$ | Transmission bandwidth which represents the length of a contiguous resource block allocation expressed in units of resources blocks | +| Max() | The largest of given numbers | +| Min() | The smallest of given numbers | +| $\text{NR}_{\text{ACLR}}$ | NR ACLR | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks | +| $N_{\text{RB\_agg}}$ | The number of the aggregated RBs within the fully allocated aggregated channel bandwidth
$N_{\text{RB\_agg}} = \sum_{j=1}^J N_{\text{RB}_j} * 2^{\mu_j}$ for carrier 1 to j, where $\mu$ is defined in TS 38.211 [13] | +| $N_{\text{RB,c}}$ | The transmission bandwidth configuration of component carrier c, expressed in units of resource blocks
$N_{\text{RB,cj}} = N_{\text{RB}_j} * 2^{\mu_j}$ for carrier j, where $\mu$ is defined in TS 38.211 [13] | +| $P_{\text{CMAX}}$ | The configured maximum UE output power | +| $P_{\text{EMAX}}$ | Maximum allowed UE output power signalled by higher layers | +| $P_{\text{Interferer}}$ | Modulated mean power of the interferer | +| $P_{\text{PowerClass}}$ | The nominal UE power (i.e. no tolerance) | +| $P_{\text{UMAX}}$ | The measured configured maximum UE output power | +| $P_{\text{uw}}$ | Power of an unwanted DL signal | +| $P_{\text{w}}$ | Power of a wanted DL signal | +| $\text{RB}_{\text{start}}$ | Indicates the lowest RB index of transmitted resource blocks | +| $W_{\text{gap}}$ | The sub-block gap between the two sub-blocks | + +### 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------------|------------------------------------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| A-MPR | Additional Maximum Power Reduction | +| BCS | Bandwidth Combination Set | +| BPSK | Binary Phase Shift Keying | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CC | Component Carrier | +| CG | Carrier Group | +| CP-OFDM | Cyclic Prefix-OFDM | +| CQI | Channel quality indicator | +| CW | Continuous Wave | +| DC | Dual Connectivity | +| DCI | Downlink Control Information | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DL | Downlink | +| DTX | Discontinuous Transmission | +| EIRP | Equivalent Isotropically Radiated Power | +| EIS | Effective Isotropic Sensitivity | +| EN-DC | E-UTRA/NR DC | +| E-UTRA | Evolved UTRA | +| EVM | Error Vector Magnitude | +| FDM | Frequency Division Multiplexing | +| FFT | Fast Fourier Transformation | +| FR | Frequency Range | +| ENBW | The aggregated bandwidth of an E-UTRA sub-block and an adjacent NR sub-block | +| HARQ | Hybrid automatic repeat request | + +| | | +|----------|-----------------------------------------------------------------------------------------------| +| IDFT | Inverse Discrete Fourier Transformation | +| ITS | Intelligent Transportation System | +| ITU-R | Radio communication Sector of the International Telecommunication Union | +| MBW | Measurement bandwidth defined for the protected band | +| MCG | Master Cell Group | +| MPR | Allowed maximum power reduction | +| MSD | Maximum Sensitivity Degradation | +| MU | Measurement Uncertainty | +| MR-DC | Multi-Radio Dual Connectivity | +| NE-DC | NR-E-UTRA Dual Connectivity | +| NGEN-DC | NG-RAN E-UTRA-NR Dual Connectivity | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NR/5GC | NR connected to 5GC | +| NS | Network Signalling | +| NSA | Non-Standalone, a mode of operation where operation of a radio is assisted with another radio | +| OCNG | OFDMA Channel Noise Generator | +| OFDM | Orthogonal frequency division multiplex | +| OOB | Out-of-band | +| OOBE | Out-of-band emission | +| OTA | Over The Air | +| PBCH | Physical broadcast channel | +| PDCCH | Physical downlink control channel | +| PDSCH | Physical downlink shared channel | +| P-MPR | Power Management Maximum Power Reduction | +| PRACH | Physical random-access channel | +| PRB | Physical Resource Block | +| PSCCH | Physical Sidelink Control CHannel | +| PSSCH | Physical Sidelink Shared CHannel | +| PUCCH | Physical uplink control channel | +| PUSCH | Physical uplink shared channel | +| QAM | Quadrature Amplitude Modulation | +| QPSK | Quadrature Phase Shift Keying | +| RE | Resource Element | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RMC | Reference Measurement Channel | +| RNTI | Radio Network Temporary Identifier | +| Rx | Receiver | +| SCG | Secondary Cell Group | +| SCS | Subcarrier spacing | +| SEM | Spectrum Emission Mask | +| SL | Sidelink | +| SRS | Sounding Reference Symbol | +| SS | Synchronization Symbol / System Simulator | +| SUL | Supplementary uplink | +| TDM | Time Division Multiplex | +| TPC | Transmit Power Control | +| TRP | Total Radiated Power | +| TT | Test Tolerance | +| Tx | Transmitter | +| UE | User Equipment | +| UL | Uplink | +| UL MIMO | Up Link Multiple Antenna transmission | +| ULSUP | Uplink sharing from UE perspective | +| V2X | Vehicle to Everything | + +## 4 General + +### 4.1 Relationship between minimum requirements and test requirements + +TS 38.101-3 [4] is interwork specification for NR UE, covering RF characteristics and minimum performance requirements. Conformance to TS 38.101-3 [4] is demonstrated by fulfilling the test requirements specified in the present document. + +The Minimum Requirements given in TS 38.101-3 [4] make no allowance for measurement uncertainty (MU). The present document defines test tolerances (TT). These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in TS 38.101-3 [4] to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +The measurement results returned by the test system are compared - without any modification - against the test requirements as defined by various levels of "Shared Risk" principle as described below. + +- a) Core specification value is not relaxed by any relaxation value ( $TT=0$ ). For each single measurement, the probability of a borderline good UE being judged as FAIL equals the probability of a borderline bad UE being judged as PASS. + - Test tolerances equal to 0 ( $TT=0$ ) are considered in this specification. +- b) Core specification value is relaxed by a relaxation value ( $TT>0$ ). For each single measurement, the probability of a borderline bad UE being judged as PASS is greater than the probability of a borderline good UE being judged as FAIL. + - Test tolerances lower than measurement uncertainty and greater than 0 ( $0 < TT < MU$ ) are considered in this specification. + - Test tolerances high up to measurement uncertainty ( $TT = MU$ ) are considered in this specification which is also known as "Never fail a good DUT" principle. +- c) Core specification value is tightened by a stringent value ( $TT<0$ ). For each single measurement, the probability of a borderline good UE being judged as FAIL is greater than the probability of a borderline bad UE being judged as PASS. + - Test tolerances lower than 0 ( $TT<0$ ) are not considered in this specification. + +The "Never fail a good DUT" and the "Shared Risk" principles are defined in Recommendation ITU-R M.1545 [21]. + +### 4.2 Applicability of minimum requirements + +- a) In TS 38.101-3 [4] the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios +- b) For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements. +- c) The spurious emissions power requirements are for the long-term average of the power. For the purpose of reducing measurement uncertainty, it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal. +- d) Terminal that supports EN-DC or NE-DC configuration shall meet E-UTRA requirements as specified in TS 36.101 [5] and NR requirements as in TS 38.101-1 [2] and TS 38.101-2 [3] unless otherwise specified in TS 38.101-3 [4]. +- e) All the requirements for intra-band contiguous and non-contiguous EN-DC or NE-DC apply under the assumption of the same uplink-downlink and special subframe configurations in the E-UTRA and slot format + +indicated by UL-DL-configurationCommon and UL-DL-configurationDedicated in the NR for the EN-DC or NE-DC, a time offset between the two RATs configurations may be required. + +- f) For EN-DC or NE-DC combinations with CA configurations for E-UTRA and/or NR, all the requirements for E-UTRA and/or NR all the requirements for E-UTRA and/or NR intra-band contiguous and non-contiguous CA apply under the assumption of the same slot format indicated by UL-DL-configurationCommon and UL-DL-configurationDedicated in the PSCell and SCells for NR and the same uplink-downlink and special subframe configurations in PCell and SCells for E-UTRA. + +A terminal which supports an EN-DC or NE-DC configuration shall support: + +- If any subsets of the EN-DC or NE-DC configuration do not specify its own bandwidth combination sets in 5.3B, then the terminal shall support the same E-UTRA bandwidth combination sets it signals the support for in E-UTRA CA configuration part of E-UTRA – NR DC and shall support the same NR bandwidth combination sets it signals the support for in NR CA configuration part of E-UTRA – NR DC. +- Else if one of the subsets of the EN-DC or NE-DC configuration specify its own bandwidth combination sets in 5.3B, then the terminal shall support a product set of channel bandwidth for each band specified by E-UTRA bandwidth combination sets, NR bandwidth combination sets, and EN-DC or NE-DC bandwidth combination sets it signals the support. + +A terminal which supports an inter-band EN-DC or NE-DC configuration with a certain UL configuration shall support the all lower order DL configurations of the lower order EN-DC or NE-DC combinations, which have this certain UL configuration and the fallbacks of this UL configuration. + +A terminal which supports NE-DC configurations shall meet the minimum requirements for corresponding EN-DC configuration, unless otherwise specified. + +For CA or DC configurations, which include FR2 intra-band CA combinations with multiple FR2 subblocks, where at least one of the subblocks is contiguous CA combination. + +- if the field *partialFR2-FallbackRX-Req* is not present, the UE shall meet all applicable UE RF requirements for the highest order CA configuration and all associated fallback CA configurations; +- if the field *partialFR2-FallbackRX-Req* is present, for each FR2 intra-band CA configuration with multiple sub-blocks that the UE indicates support for explicitly in UE capability signalling: the in-gap UE RF requirements in clauses 7.5A, 7.5B, 7.6A, 7.6B apply as the equivalent requirements for the associated fallback FR2 intra-band CA configurations with the same number of sub-blocks, where at least one of the sub-blocks consists of a contiguous CA configuration. The UE shall meet all applicable UE RF requirements for fallback CA configurations with a lesser number of sub-blocks; +- regardless of the field *partialFR2-FallbackRX-Req*, the UE shall meet all DL out-of-gap requirements for all lower order fallback CA configurations. + +Terminal that supports inter-band NR-DC between FR1 and FR2 configuration shall meet the requirements for corresponding CA configuration (suffix A), unless otherwise specified. + +## 4.3 Specification suffix information + +Unless stated otherwise the following suffixes are used for indicating at 2nd level clause, shown in Table 4.3-1. + +**Table 4.3-1: Definition of suffixes** + +| Clause suffix | Variant | +|---------------|----------------------------------------------------------------------------------------------------------------------------| +| None | Single Carrier | +| A | Carrier Aggregation (CA) between FR1 and FR2 | +| B | Dual-Connectivity (DC) with and without SUL including UL sharing from UE perspective, inter-band NR DC between FR1 and FR2 | +| D | UL MIMO | +| E | V2X | +| F | Shared spectrum channel access | + +## 4.4 Test points analysis + +The information on test point analysis and test point selection including number of test points for each test case is shown in TR 38.905 [7] clause 4.3. + +## 4.5 Applicability and test coverage rules + +### 4.5.0 General + +- (1) The applicability and test coverage rules for Non-Standalone (NSA) only capable devices shall include the following: + - a) For each NR band in a device; test all the EN-DC or NE-DC exception test requirements as per test procedures in this specification. + - b) Test all the EN-DC or NE-DC FR2 non-exception test requirements in this specification with test procedures which refer appropriately back to TS 38.521-2 [9] for each NR band. Test only one EN-DC or NE-DC combination per FR2 band for each EN-DC or NE-DC configuration as defined in clause 5.5B of TS 38.101-3 [4] using LTE anchor agnostic approach. + - c) Test all the EN-DC or NE-DC FR1 non-exception test requirements in this specification with test procedures which refer appropriately back to TS 38.521-1 [8] for each NR band. Test only one EN-DC or NE-DC combination per FR1 band for each EN-DC or NE-DC configuration as defined in clause 5.5B of 38.101-3 [4] using LTE anchor agnostic approach. +- (2) The applicability and test coverage rules for Standalone (SA) and NSA capable devices shall include the following: + - a) For each NR band in a device, test all the EN-DC or NE-DC exception test requirements as per test procedures in this specification. + - b) Test all the Standalone FR2 test requirements as per test procedures in TS 38.521-2 [9] for each NR band. This also fulfils coverage for all non-exception EN-DC or NE-DC FR2 test requirements for that NR band and need not be retested. If Standalone FR2 cannot be tested (due to test case not being complete), then test in EN-DC or NE-DC mode following (1) b) above. + - c) Test all the Standalone FR1 test requirements as per test procedures in TS 38.521-1 [8] for each NR band. This also fulfils coverage for all non-exception EN-DC or NE-DC FR1 test requirements for that NR band and need not be retested. If Standalone FR1 cannot be tested (due to test case not being complete or if the UE does not support the band in SA mode), then test in EN-DC or NE-DC mode following (1)c) above. + +#### 4.5.1 Test coverage across 5G NR connectivity options + +The test cases in this specification cover both NR/5GC (including FR1+FR2 CA or FR1+FR2 NR-DC) as well as EN-DC, NE-DC and NGEN-DC testing. Below shall be the understanding with respect to coverage across 5G NR connectivity options: + +- 1) Unless otherwise stated within the test case, it shall be understood that test requirements are agnostic of the EN-DC, NE-DC and NGEN-DC connectivity options configured within the test. The test coverage across the EN-DC, NE-DC and NGEN-DC connectivity options shall be considered fulfilled by executing the test case in one of these connectivity options. In the case of non-exception requirements, test coverage of NE-DC is fulfilled by execution of NR/5GC connectivity option test cases. +- 2) EN-DC is the default connectivity option used for EN-DC, NE-DC and NGEN-DC test cases. +- 3) If a UE does not support EN-DC, any other supported connectivity option of NE-DC or NGEN-DC can be configured to execute the test. The leverage rule detailed in (1) would apply. + +**Table 4.5.1-1: Void** + +**Table 4.5.1-2: Void** + +#### 4.6 E-UTRA configuration for EN-DC FR1 tests applying the E-UTRA anchor-agnostic approach + +This clause applies to EN-DC test cases where E-UTRA anchor needs to be configured as per the anchor-agnostic approach outlined in clauses 6.1 and 7.1 of TS 38.101-3 [4]. The LTE anchor-agnostic approach is defined as measurements on the NR carrier under conditions where the LTE anchor resources do not interfere with NR operation. The configuration defined in this clause ensures establishment of such conditions. + +For baseline configuration, the E-UTRA carrier will be configured for each test case in clauses 6 and 7 as defined in the equivalent standalone E-UTRA test in TS 36.521-1 [10]. However, the below exceptions defined in Table 4.6-1, 4.6-2, 4.6-3, 4.6-4 and 4.6-5 are applied to ensure that the E-UTRA anchor resources do not interfere with NR operation. + +For EN-DC within FR1 band combinations with multiple E-UTRA component carriers, it is sufficient to configure any one E-UTRA carrier from the carrier group whenever it is determined that anchor agnostic approach can be applied. Unless otherwise stated, the number of component carriers (CCs) listed in the test case titles of Clause 6 and clause 7 shall refer to the number of component carriers configured within the test case. + +**Table 4.6-1: E-UTRA configuration for EN-DC FR1 tests applying anchor agnostic approach** + +| Parameter | Value | Comments | +|--------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test Frequency during and after connection setup | Mid (See Table 4.6-2) | As defined in TS 36.508 for the LTE band under test | +| Bandwidth during and after connection setup | 5 MHz (See Table 4.6-2) | Supported by all LTE bands. | +| DL signal levels during connection setup | RS EPRE -85.0 dBm/15kHz | DL physical channels as defined in Annex C0, C.1, C.2 and Annex C.3 of TS 36.521-1 [10].
TS 36.521-1 [10] annex C.0 defines the default DL power level of RS EPRE to be -85dBm/15kHz. | +| UL Signal levels during connection setup | PUSCH Power | Attained by enabling open loop power control and setting up UL signal levels according to Annex H.0, H.2 and H.3 of TS 36.521-1 [10]. | +| DL/UL RMC after connection setup | 0 RB allocation on both DL and UL (see Table 4.6-2) | Once the LTE link is established, then LTE Tx can be restricted by configuring 0 RB allocation on DL and UL.
TimeAlignmentTimerDedicated IE to be set to infinity to ensure UE doesn't look for TA adjustments (See Table 4.6-5) | +| CQI Reports and SRS after connection setup | Disabled (See Table 4.6-3 and 4.6-4) | Disable periodic and aperiodic CQI reports to ensure none of these transmissions occur on the LTE uplink.
Since LTE transmissions could easily exceed spurious emissions limits, tests that are intended to measure RF parameters on the NR should simply avoid LTE transmit altogether. | +| Number of OFDM symbols for PDCCH | 3 | The PCFICH carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe, as specified in TS 36.211 [8] clause 6.7 | + +**Table 4.6-2: E-UTRA Test Configuration Table** + +| E-UTRA Test Parameters | | | | | | +|--------------------------|-----------------------|------------|---------------|------------|---------------| +| E-UTRA Channel Bandwidth | E-UTRA Test Frequency | Downlink | | Uplink | | +| | | Modulation | RB allocation | Modulation | RB allocation | +| 5 MHz 2 | MidRange 1 | N/A | 0 | N/A | 0 | + +NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [11] clause 4.3.1. +NOTE 2: For EN-DC Intra-band tests that need to apply E-UTRA anchor agnostic approach, refer to and pick applicable E-UTRA channel bandwidth from clause 5.3B.1 and indicate within test case if it is different than 5 MHz. + +**Table 4.6-3: CQI-ReportConfig-DEFAULT: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT | | | | +|-------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| CQI-ReportConfig-DEFAULT ::= SEQUENCE { | | | | +| cgi-ReportModeAperiodic | NOT PRESENT | | | +| cgi-ReportPeriodic | NOT PRESENT | | | +| } | | | | + +**Table 4.6-4: PhysicalConfigDedicated-DEFAULT: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.8.2, Table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT | | | | +|------------------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { | | | | +| soundingRS-UL-ConfigDedicated | Not present | | RBC | +| } | | | | + +**Table 4.6-5: MAC-MainConfig-RBC: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.8.2.1.5, Table 4.8.2.1.5-1 MAC-MainConfig-RBC | | | | +|---------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| timeAlignmentTimerDedicated | Infinity | | | + +## 4.7 E-UTRA configuration for EN-DC FR2 tests applying the E-UTRA anchor-agnostic approach + +This clause applies to EN-DC test cases where E-UTRA anchor needs to be configured as per the anchor-agnostic approach outlined in clauses 6.1 and 7.1 of TS 38.101-3 [4]. The LTE anchor-agnostic approach is defined as measurements on the NR carrier under conditions where the LTE anchor resources do not interfere with NR operation. The configuration defined in this clause ensures establishment of such conditions. + +For baseline configuration, the E-UTRA carrier will be configured for each test case in clauses 6 and 7 as defined in the equivalent standalone E-UTRA test in TS 36.521-1 [10]. However, the below exceptions defined in Table 4.7-1 to 4.7-7 are applied to ensure that the E-UTRA anchor resources do not interfere with NR operation. + +Since the E-UTRA link is always a functional link when testing EN-DC including FR2 band combinations, it is sufficient to configure any one E-UTRA carrier from the carrier group, irrespective of the number of E-UTRA carriers in the EN-DC combination under test. Unless otherwise stated, the number of component carriers (CCs) listed in the test case titles of Clause 6 and clause 7 shall refer to the number of component carriers configured within the test case. + +**Table 4.7-1: E-UTRA configuration for EN-DC FR2 tests applying anchor agnostic approach** + +| Parameter | Value | Comments | +|--------------------------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test Frequency during and after connection setup | Mid (See Table 4.7-2) | As defined in TS 36.508 for the LTE band under test | +| Bandwidth during and after connection setup | 5 MHz (See Table 4.7-2) | Supported by all LTE bands. | +| DL signal levels | See table 4.7-3 | DL physical channels as defined in Annex C0, C.1, C.2 and Annex C.3 of TS 36.521-1 [10]. | +| UL Signal levels for connection setup and UBF transmission | PUSCH Power | Attained by enabling open loop power control and setting up UL signal levels according to Annex H.0, H.2 and H.3 of TS 36.521-1 [10] with the exception for power control message exception defined in Table 4.7-5 | +| DL/UL RMC after connection setup except for UBF transmission | 0 RB allocation on both DL and UL (see Table 4.7-2) | Once the LTE link is established, then LTE Tx can be restricted by configuring 0 RB allocation on DL and UL.
TimeAlignmentTimerDedicated IE to be set to infinity to ensure UE doesn't look for TA adjustments (See Table 4.7-7) | +| CQI Reports and SRS after connection setup | Disabled (See Table 4.7-4 and 4.7-6) | Disable periodic and aperiodic CQI reports to ensure none of these transmissions occur on the LTE uplink.
Since LTE transmissions could easily exceed spurious emissions limits, tests that are intended to measure RF parametrics on the NR should simply avoid LTE transmit altogether. | +| Number of OFDM symbols for PDCCH | 3 | The PCFICH carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe, as specified in TS 36.211 [8] clause 6.7 | + +Table 4.7-2: E-UTRA Test Configuration Table + +| E-UTRA Test Parameters | | | | | | +|--------------------------|-----------------------|------------|---------------|------------|---------------| +| E-UTRA Channel Bandwidth | E-UTRA Test Frequency | Downlink | | Uplink | | +| | | Modulation | RB allocation | Modulation | RB allocation | +| 5 MHz 2 | MidRange 1 | N/A | 0 | N/A | 0 | + +NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [11] clause 4.3.1 + +NOTE 2: For EN-DC Intra-band tests that need to apply E-UTRA anchor agnostic approach, refer to and pick applicable E-UTRA channel bandwidth from clause 5.3B.1 and indicate within test case if it is different than 5 MHz. + +Table 4.7-3: Default Downlink power levels for E-UTRA anchor + +| | Unit | Band Group | Channel Bandwidth | | | | | | +|---------|-----------|----------------|-------------------|-------|----------|-------|--------|--------| +| | | | 1.4 MHz | 3 MHz | 5MHz | 10MHz | 15 MHz | 20 MHz | +| RS EPRE | dBm/15kHz | FDD_A, TDD_A | N/A | N/A | ≥ -120.0 | N/A | N/A | N/A | +| | | FDD_B1, TDD_B1 | N/A | N/A | ≥ -119.5 | N/A | N/A | N/A | +| | | FDD_C, TDD_C | N/A | N/A | ≥ -119.0 | N/A | N/A | N/A | +| | | FDD_D, TDD_D | N/A | N/A | ≥ -118.5 | N/A | N/A | N/A | +| | | FDD_E, TDD_E | N/A | N/A | ≥ -118.0 | N/A | N/A | N/A | +| | | FDD_G, TDD_G | N/A | N/A | ≥ -117.0 | N/A | N/A | N/A | +| | | FDD_H, TDD_H | N/A | N/A | ≥ -116.5 | N/A | N/A | N/A | +| | | FDD_N, TDD_N | N/A | N/A | ≥ -113.5 | N/A | N/A | N/A | + +NOTE 1: The power level is specified at RSRP reference point as defined in TS 36.214 [24] + +NOTE 2: E-UTRA Band groups are defined in TS 36.133 [12] clause 3.5.1. + +Table 4.7-4: CQI-ReportConfig-DEFAULT: Additional E-UTRA Anchor Configuration + +| Derivation Path: TS 36.508 [7] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT | | | | +|-------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| CQI-ReportConfig-DEFAULT ::= SEQUENCE { | | | | +| cgi-ReportModeAperiodic | NOT PRESENT | | | +| cgi-ReportPeriodic | NOT PRESENT | | | +| } | | | | + +Table 4.7-5: UplinkPowerControlCommon-DEFAULT : Additional E-UTRA Anchor Configuration + +| Derivation Path: TS 36.508 [7] clause 4.6.3, UplinkPowerControlCommon-DEFAULT | | | | +|-------------------------------------------------------------------------------|---------------|--------------------------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UplinkPowerControlCommon-DEFAULT ::= SEQUENCE { | | | | +| p0-NominalPUSCH | -60 (-60 dBm) | To attain maximum power from the DUT | | +| } | | | | + +Table 4.7-6: PhysicalConfigDedicated-DEFAULT: Additional E-UTRA Anchor Configuration + +| Derivation Path: TS 36.508 [7] clause 4.8.2, Table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT | | | | +|------------------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { | | | | +| soundingRS-UL-ConfigDedicated | Not present | | RBC | +| } | | | | + +**Table 4.7-7: MAC-MainConfig-RBC: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.8.2.1.5, Table 4.8.2.1.5-1 MAC-MainConfig-RBC | | | | +|---------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| timeAlignmentTimerDedicated | Infinity | | | + +## 4.8 E-UTRA configuration for EN-DC FR1 tests not applying the E-UTRA anchor-agnostic approach + +Unless otherwise stated, the following message exception defined in tables 4.8-1, 4.8-2 and 4.8-3 apply for EN-DC FR1 tests not applying the E-UTRA anchor-agnostic approach. + +**Table 4.8-1: CQI-ReportConfig-DEFAULT: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT | | | | +|-------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| CQI-ReportConfig-DEFAULT ::= SEQUENCE { | | | | +| cqi-ReportModeAperiodic | NOT PRESENT | | | +| cqi-ReportPeriodic | NOT PRESENT | | | +| } | | | | + +**Table 4.8-2: PhysicalConfigDedicated-DEFAULT: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.8.2, Table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT | | | | +|------------------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { | | | | +| soundingRS-UL-ConfigDedicated | Not present | | RBC | +| } | | | | + +**Table 4.8-3: MAC-MainConfig-RBC: Additional E-UTRA Anchor Configuration** + +| Derivation Path: TS 36.508 [7] clause 4.8.2.1.5, Table 4.8.2.1.5-1 MAC-MainConfig-RBC | | | | +|---------------------------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| timeAlignmentTimerDedicated | Infinity | | | + +# 5 Operating bands and channel arrangement + +## 5.1 General + +The channel arrangements presented in this clause are based on the operating bands and channel bandwidths defined in the present release of specifications. + +NOTE: Other operating bands and channel bandwidths may be considered in future releases. + +Requirements throughout the RF specifications are in many cases defined separately for different frequency ranges (FR). The frequency ranges in which NR can operate according to this version of the specifications are identified as described in Table 5.1-1. + +**Table 5.1-1: Definition of frequency ranges** + +| Frequency range designation | Corresponding frequency range | +|-----------------------------|-------------------------------| +| FR1 | 410 MHz – 7125 MHz | +| FR2 | 24250 MHz – 52600 MHz | + +The present specification covers band combinations including + +- at least one FR1 operating band and one FR2 operating band for carrier aggregation and dual connectivity operations; +- at least one E-UTRA operating band for dual connectivity operations. + +## 5.2 Operating bands + +NR is designed to operate in FR1 operating bands defined in TS 38.101-1 [2] and FR2 operating bands defined in TS 38.101-2 [3]. E-UTRA is designed to operate in operating bands defined in TS 36.101 [4]. + +### 5.2A Operating bands for CA + +#### 5.2A.1 Inter-band CA between FR1 and FR2 + +NR carrier aggregation is designed to operate in the operating bands defined in Table 5.2A.1-1. The band combinations include at least one FR1 operating band and one FR2 operating band. + +If the mandatory simultaneous Rx/Tx capability applies for a lower order band combination, when the applicable lower order band combination is a band pair in a higher order band combination, the mandatory simultaneous Rx/Tx capability also applies for the band pair in the higher order band combination. + +**Table 5.2A.1-1: Band combinations for inter-band NR CA between FR1 and FR2** + +Editor's note: No band combinations for inter-band NR CA between FR1 and FR2 specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode. + +### 5.2B Operating bands for DC + +#### 5.2B.1 General + +The operating bands are specified in clause 5.5B for operation with EN-DC, NGEN-DC, NE-DC or NR-DC configured. + +#### 5.2B.2 to 5.2B.7 Void + +### 5.2E Operating bands for V2X + +#### 5.2E.1 Intra-band V2X bands + +NR V2X operation is designed to operate with E-UTRA sidelink in TDM mode on the operating bands combinations listed in Table 5.2E.1-1. + +**Table 5.2E.1-1: Intra-band V2X operating bands** + +| E-UTRA V2X-NR V2X Band combination | E-UTRA or NR Band | Interface | +|-----------------------------------------------|-------------------|-----------| +| V2X_47_n47 1 | 47 | PC5 | +| | n47 | PC5 | +| NOTE 1: Only single switched SL is supported. | | | + +#### 5.2E.2 Inter-band V2X bands + +NR V2X operation is designed to operate concurrent with E-UTRA uplink/downlink on the operating bands combinations listed in Table 5.2E.2-1. + +**Table 5.2E.2-1: Inter-band concurrent V2X operating bands** + +| E-UTRA-NR V2X Band Combination | E-UTRA or NR Band | Interface | +|-----------------------------------------------------------|-------------------|-----------| +| V2X_20_n38 | 20 | Uu | +| | n38 | PC5 | +| V2X_n71_47 | 47 | PC5 | +| | n71 | Uu | +| V2X_n71_(n) 47 1 | 47 | PC5 | +| | n47 | PC5 | +| | n71 | Uu | +| NOTE 1: Only single switched SL in ITS band is supported. | | | + +## 5.3 UE Channel bandwidth + +### 5.3A UE Channel bandwidth for CA + +#### 5.3A.1 Inter-band CA between FR1 and FR2 + +For inter-band NR CA between FR1 and FR2, a carrier aggregation configuration is a combination of operating bands, each supporting a carrier aggregation bandwidth class as specified in clause 5.3A.5 of TS 38.101-1 [2] and clause 5.3A.4 of TS 38.101-2 [3] independently. + +### 5.3B UE Channel bandwidth for DC + +#### 5.3B.0 General + +For intra-band contiguous EN-DC, the aggregated channel bandwidth is sum of the individual NR and E-UTRA channel bandwidths assuming nominal EN-DC channel with 0 kHz offset spacing as specified in clause 5.4. + +$$ENBW = BW_{NR\_Channel} + BW_{E-UTRA\_Channel}$$ + +In the case where the NR sub-block and/or the E-UTRA sub-block itself is composed of intra-band contiguous CA carriers, the EN-DC aggregated channel bandwidth is the sum of the aggregated channel bandwidths of the NR and E-UTRA sub-blocks assuming nominal EN-DC channel spacing between the NR sub-block and E-UTRA sub-block. + +$$ENBW = BW_{NR\_Channel\_CA} + BW_{E-UTRA\_Channel\_CA}$$ + +Intra-band contiguous EN-DC configurations are defined using intra-band contiguous EN-DC bandwidth class notation DC\_(n)Xyz where the first EN-DC bandwidth class letter indicates the number of contiguous E-UTRA carriers and the second EN-DC bandwidth class letter indicates the number of contiguous NR carriers for the EN-DC combination of E-UTRA Band X and NR Band nX. Applicable contiguous intraband EN-DC bandwidth classes are listed in Table 5.3B.0-1 + +**Table 5.3B.0-1: Intra-band contiguous EN-DC bandwidth classes** + +| Intra-band contiguous EN-DC bandwidth class | Number of contiguous CC | | +|---------------------------------------------|-------------------------|----| +| | E-UTRA | NR | +| AA | 1 | 1 | +| AB | 1 | 2 | +| CA | 2 | 1 | +| DA | 3 | 1 | + +## 5.3B.1 Intra-band EN-DC in FR1 + +### 5.3B.1.1 General + +The requirements for intra-band EN-DC in this specification are defined for EN-DC configurations with associated bandwidth combination sets. + +For each EN-DC configuration, requirements are specified for all bandwidth combinations contained in a *bandwidth combination set*, which is indicated per supported band combination in the UE radio access capability. A UE can indicate support of several bandwidth combination sets per band combination. + +### 5.3B.1.2 BCS for Intra-band contiguous EN-DC + +For intra-band contiguous EN-DC, an EN-DC configuration is consisting of an E-UTRA band and a corresponding NR band having the same frequency range which supports an intra-band contiguous EN-DC bandwidth class. + +Bandwidth combination sets for intra-band contiguous EN-DC are specified in Table 5.3B.1.2-1. The EN-DC configurations and bandwidth combination sets in Table 5.3B.1.2-1 also apply to higher order EN-DC combinations that include inter-band and intra-band EN-DC on the downlink and inter-band EN-DC on the uplink. If no BCS is reported in the UE capabilities for an intra-band combination the default is that the UE supports BCS0. + +**Table 5.3B.1.2-1: EN-DC configurations and bandwidth combination sets defined for intra-band contiguous EN-DC** + +| E-UTRA – NR configuration / Bandwidth combination set | | | | | | | +|-------------------------------------------------------|-----------------------------|-------------------------------------------------------------|-----------------------------------------|---------------------------------------------|------------------------------------|---------------------------| +| Downlink EN-DC configuration | Uplink EN-DC configurations | Component carriers in order of increasing carrier frequency | | | Maximum aggregated bandwidth (MHz) | Bandwidth combination set | +| | | Channel bandwidths for E-UTRA carrier (MHz) | Channel bandwidths for NR carrier (MHz) | Channel bandwidths for E-UTRA carrier (MHz) | | | +| DC_(n)41AA | DC_(n)41AA | 20 | 40, 60, 80,100 | | 120 | 0 | +| | | | 40, 60, 80,100 | 20 | | | +| | | 20 | 40, 50, 60, 80,100 | | 120 | 1 | +| | | | 40, 50, 60, 80,100 | 20 | | | +| DC_(n)41CA | DC_(n)41AA | 20+20 | 40, 60, 80,100 | | 140 | 0 | +| | | | 40, 60, 80,100 | 20+20 | | | +| | | 20+20 | 40, 50, 60, 80,100 | | 140 | 1 | +| | | | 40, 50, 60, 80,100 | 20+20 | | | +| DC_(n)71AA | DC_(n)71AA | 15 | 5 | | 20 | 0 | +| | | 10 | 5, 10 | | | | +| | | 5 | 5, 10, 15 | | | | +| | | | 5 | 15 | | | +| | | | 5, 10 | 10 | | | +| | | | 5, 10, 15 | 5 | | | + +NOTE 1: Void + +NOTE 2: Void + +NOTE 3: Void + +NOTE 4: The channel bandwidths for E-UTRA or NR carrier should be at least supported in one of the BCS indicated in E-UTRA bandwidth combination sets or NR bandwidth combination sets if reported. + +### 5.3B.1.3 BCS for Intra-band non-contiguous EN-DC + +For intra-band non-contiguous EN-DC, an EN-DC configuration is consisting of an E-UTRA band and a corresponding NR band having the same frequency range which supports E-UTRA and NR carriers, where E-UTRA configuration is + +indicated by using E-UTRA CA bandwidth class as defined in TS 36.101 [5] and NR configuration is indicated by using NR CA bandwidth class as defined in TS 38.101-1 [2]. + +Requirements for intra-band non-contiguous EN-DC are defined for the EN-DC configurations and bandwidth combination sets specified in Table 5.3B.1.3-1. The EN-DC configurations and bandwidth combination sets in Table 5.3B.1.3-1 also apply to higher order EN-DC combinations that include inter-band and intra-band EN-DC on the downlink and inter-band EN-DC on the uplink. If no BCS is reported in the UE capabilities for an intra-band combination the default is that the UE supports BCS0. + +**Table 5.3B.1.3-1: EN-DC configurations and bandwidth combination sets defined for intra-band non-contiguous EN-DC** + +| E-UTRA – NR configuration / Bandwidth combination set | | | | | | | +|-------------------------------------------------------|-----------------------------|-------------------------------------------------------------|-----------------------------------------|---------------------------------------------|------------------------------------|---------------------------| +| Downlink EN-DC configuration | Uplink EN-DC configurations | Component carriers in order of increasing carrier frequency | | | Maximum aggregated bandwidth (MHz) | Bandwidth combination set | +| | | Channel bandwidths for E-UTRA carrier (MHz) | Channel bandwidths for NR carrier (MHz) | Channel bandwidths for E-UTRA carrier (MHz) | | | +| DC_41A_n41A | DC_41A_n41A | 20 | 40, 60, 80, 100 | | 120 | 0 | +| | | | 40, 60, 80, 100 | 20 | | | +| | | 20 | 40, 50, 60, 80, 100 | | 120 | 1 | +| | | | 40, 50, 60, 80, 100 | 20 | | | +| DC_41C_n41A | DC_41A_n41A | 20+20 | 40, 60, 80, 100 | | 140 | 0 | +| | | | 40, 60, 80, 100 | 20+20 | | | +| | | 20+20 | 40, 50, 60, 80, 100 | | 140 | 1 | +| | | | 40, 50, 60, 80, 100 | 20+20 | | | +| DC_41D_n41A | DC_41A_n41A | 20+20+20 | 40, 60, 80, 100 | | 160 | 0 | +| | | | 40, 60, 80, 100 | 20+20+20 | | | +| | | 20+20+20 | 40, 50, 60, 80, 100 | | 160 | 1 | +| | | | 40, 50, 60, 80, 100 | 20+20+20 | | | + +NOTE 1: Only single switched UL is supported in Rel-15. + +## 5.3E UE Channel bandwidth for V2X + +### 5.3E.0 General + +The requirements specified in clause 5.3B are applicable to NR V2X UE. + +### 5.3E.1 Intra-band contiguous V2X in FR1 + +For intra-band contiguous E-UTRA NR V2X UE, an EN-DC bandwidth class in Table 5.3B.0-1 are considered to specify the V2X transmission/reception configurations. + +Bandwidth combination sets and V2X transmission/reception configurations for intra-band contiguous V2X UE are specified in Table 5.3E.1-1. + +**Table 5.3E.1-1: E-UTRA-NR V2X configurations and bandwidth combination sets for intra-band contiguous V2X UE** + +| V2X configuration | SL transmission band | Channel bandwidths for E-UTRA carrier (MHz) | Channel bandwidths for NR carrier (MHz) | Maximum aggregated bandwidth (MHz) | Bandwidth combination set | +|-------------------|-------------------------------|---------------------------------------------|-----------------------------------------|------------------------------------|---------------------------| +| V2X_(n)47AA | E-UTRA Band 47 or NR band n47 | 10 | 10,20,30,40 | 60 | 0 | +| | | 20 | 10,20,30,40 | | | + +## 5.3E.2 Intra-band non-contiguous V2X in FR1 + +For intra-band non-contiguous E-UTRA NR V2X UE, an EN-DC bandwidth class in Table 5.3B.0-1 are considered to specify the V2X transmission/reception configurations. + +Bandwidth combination sets and SL transmission/reception configurations for intra-band non-contiguous V2X are specified in Table 5.3E.2-1. + +**Table 5.3E.2-1: E-UTRA-NR V2X configurations and bandwidth combination sets for intra-band non-contiguous V2X UE** + +| V2X configuration | SL transmission band | Channel bandwidths for E-UTRA carrier (MHz) | Channel bandwidths for NR carrier (MHz) | Maximum aggregated bandwidth (MHz) | Bandwidth combination set | +|-------------------|-------------------------------|---------------------------------------------|-----------------------------------------|------------------------------------|---------------------------| +| V2X_47A_n47A | E-UTRA Band 47 or NR band n47 | 10 | 10,20,30,40 | 60 | 0 | +| | | 20 | 10,20,30,40 | | | + +## 5.3E.3 Inter-band V2X in FR1 + +For inter-band E-UTRA NR V2X UE, the each channel bandwidth for inter-band V2X operations in FR1 is specified in TS 36.101 [4] and TS 38.101-1 [2], respectively. + +# 5.4 Void + +## 5.4A Channel arrangement for CA + +The channel arrangement for CA operations in FR1 and FR2 as specified in TS 38.101-1 [2] and TS 38.101-2 [3], respectively. + +## 5.4B Channel arrangement for DC + +### 5.4B.0 General + +The channel arrangement for intra-band EN-DC operations in FR1 is specified in TS 36.101 [5] and TS 38.101-1 [2], respectively. + +### 5.4B.1 Channel spacing for intra-band EN-DC carriers + +The spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between E-UTRA carrier and an adjacent NR carrier for intra-band contiguous EN-DC is defined as following: + +- For NR operating bands with 100 kHz channel raster, + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{E-UTRA\_Channel}} + \text{BW}_{\text{NR\_Channel}})/2$$ + +- For NR operating bands with 15 kHz channel raster, + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{E-UTRA\_Channel}} + \text{BW}_{\text{NR\_Channel}})/2 + \{-5\text{kHz}, 0\text{kHz}, 5\text{kHz}\} \text{ for } \Delta F_{\text{Raster}} \text{ equals to } 15 \text{ kHz}$$ + +$$\text{Nominal Channel spacing} = (\text{BW}_{\text{E-UTRA\_Channel}} + \text{BW}_{\text{NR\_Channel}})/2 + \{-10\text{kHz}, 0\text{kHz}, 10\text{kHz}\} \text{ for } \Delta F_{\text{Raster}} \text{ equals to } 30 \text{ kHz}$$ + +where $\text{BW}_{\text{E-UTRA\_Channel}}$ and $\text{BW}_{\text{NR\_Channel}}$ are the channel bandwidths of the E-UTRA and NR carriers, $\Delta F_{\text{Raster}}$ is the band dependent channel raster granularity defined in TS38.101-1[2]. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario. + +For intra-band non-contiguous EN-DC the channel spacing between E-UTRA and NR carriers shall be larger than the nominal channel spacing defined in this clause. + +## 5.5 Configuration + +### 5.5A Configuration for CA + +#### 5.5A.1 Inter-band CA configurations between FR1 and FR2 + +**Table 5.5A.1-1: Inter-band CA configurations and bandwidth combinations sets between FR1 and FR2 (two bands)** + +Editor's note: No Inter-band CA configurations between FR1 and FR2 (two bands) specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode. + +## 5.5B Configuration for DC + +### 5.5B.1 General + +The operating bands and bandwidth classes are specified for operation with EN-DC, NGEN-DC, NE-DC or NR-DC configured. The EN-DC, NE-DC or NGEN-DC band combinations include at least one E-UTRA operating band. + +For EN-DC or NE-DC configurations indicated by column "Single Uplink allowed" (e.g., problematic band combinations as defined in TS 38.306 [16]) in tables in this clause the UE may indicate capability of not supporting simultaneous dual and triple uplink operation due to possible intermodulation interference to its own primary downlink channel bandwidth of PCell or PSCell if the intermodulation order is 2 or if the intermodulation order is 3 for the combinations when both operating bands are between 450 MHz – 960 MHz or between 1427 MHz – 2690 MHz. + +In the case for EN-DC or NE-DC configurations listed in tables in this clause for which the intermodulation products caused by the dual and triple uplink operation fall into the receive band but do not interfere with its own primary downlink channel bandwidth of PCell or PSCell as defined in Annex I the UE is mandated to operate in dual and triple uplink mode. Single Uplink is also allowed for certain band combinations where intermodulation or reverse intermodulation products could create difficulty for meeting emission requirements. + +For EN-DC combinations of order 3 or higher, "Single Uplink allowed" UL configurations captured in Table 5.5B.2-1, Table 5.5B.3-1, and Table 5.5B.4-1 apply. + +If multiple UL DC configurations are listed for multiple DL DC configurations, valid uplink configurations are such that uplink does not have more carriers than downlink. + +Non-contiguous resource allocation and almost contiguous allocation are not applicable for E-UTRA or NR carrier part of intra-band EN-DC configuration. + +If the mandatory simultaneous Rx/Tx capability applies for a lower order DC configuration, when the applicable lower order DC configuration is a band pair in a higher order DC configuration, the mandatory simultaneous Rx/Tx capability also applies for the band pair in the higher order DC configuration. + +For a higher order EN-DC band combination of which DC\_20\_n28/ DC\_28\_n20/ CA\_20-28/ CA\_n20-n28 is a subset, the frequency range in band n28/28 is restricted for the higher order band combination to 703-733 MHz for the UL and 758-788 MHz for the DL. + +For NR inter-band dual connectivity specified in 5.5B.7, the corresponding NR CA configurations in 5.5A.1, i.e., dual uplink inter-band carrier aggregation between FR1 and FR2 with uplink assigned to two NR bands, are applicable to Dual Connectivity. + +NOTE 1: Requirements for the dual connectivity configurations are defined in the clause corresponding NR uplink CA between FR1 and FR2 configurations, unless otherwise specified. + +### 5.5B.2 Intra-band contiguous EN-DC + +Supported channel bandwidths for E-UTRA operating bands are defined in TS 36.521-1 [10] and for NR operating bands in TS 38.521-1 [8]. + +**Table 5.5B.2-1: Intra-band contiguous EN-DC configurations** + +| EN-DC Configuration | Uplink EN-DC configuration (NOTE 1) | Single UL allowed | +|----------------------------------------------------|-------------------------------------|-------------------| +| DC_(n)41AA 5
DC_(n)41CA 5 | DC_(n)41AA | Yes 3 | +| DC_(n)71AA 2 | DC_(n)71AA | No 4 | + +NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. +NOTE 2: Requirements in this specification apply for NR SCS of 15 kHz only. +NOTE 3: Single UL allowed due to potential emission issues, not self-interference. +NOTE 4: For UE(s) supporting dynamic power sharing it is mandatory to do dual simultaneous UL. For UE(s) not supporting dynamic power sharing single UL is allowed. +NOTE 5: The minimum requirements only apply for non-simultaneous Tx/Rx between all carriers. + +### 5.5B.3 Intra-band non-contiguous EN-DC + +Supported channel bandwidths for E-UTRA operating bands are defined in TS 36.521-1 [10] and for NR operating bands in TS 38.521-1 [8]. + +**Table 5.5B.3-1: Intra-band non-contiguous EN-DC configurations** + +| EN-DC Configuration | Uplink EN-DC configuration (NOTE 1) | Single UL allowed | +|----------------------------------------------------------------------------------|-------------------------------------|-------------------| +| DC_41A_n41A 3
DC_41C_n41A 3
DC_41D_n41A 3 | DC_41A_n41A | Yes 4 | +| DC_66A_n66A | DC_66A_n66A 5 | Yes 5 | + +NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. +NOTE 2: Only single switched UL is supported in Rel-15 +NOTE 3: The minimum requirements only apply for non-simultaneous Tx/Rx between all carriers. +NOTE 4: Single UL allowed due to potential emission issues, not self-interference. +NOTE 5: Only single switched UL is supported. +NOTE 6: Reserve. +NOTE 7: Single UL allowed due to potential emission issues and self-interference. + +### 5.5B.4 Inter-band EN-DC within FR1 + +Supported channel bandwidths for E-UTRA operating bands and CA configurations are defined in TS 36.521-1 [10] and for NR operating bands and CA configurations in TS 38.521-1 [8] and present document. + +#### 5.5B.4.1 Inter-band EN-DC configurations within FR1 (two bands) + +**Table 5.5B.4.1-1: Inter-band EN-DC configurations within FR1 (two bands)** + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | Single UL allowed | DL interruption allowed (Note 14) | +|-------------------------------------------------------------------------------|-------------------------------------|-------------------|-----------------------------------| +| DC_1A_n3A | DC_1A_n3A | DC_1_n3 | | +| DC_1A_n5A | DC_1A_n5A | No | | +| DC_1A_n7A | DC_1A_n7A | No | | +| DC_1A_n28A | DC_1A_n28A | No | | +| DC_1A_n41A 7 | DC_1A_n41A | No | | +| DC_1A_n77A 7 | DC_1A_n77A | DC_1_n77 | No | +| DC_1A_n78A 7
DC_1A_n78C 7 | DC_1A_n78A | No | No | +| DC_1A-1A_n78A | DC_1A_n78A | No | | +| DC_1A_n79A 7
DC_1A_n79C 7 | DC_1A_n79A | No | No | +| DC_2A_n5A | DC_2A_n5A | No | | +| DC_2A-2A_n5A | DC_2A_n5A | No | | +| DC_2A_n41A
DC_2C_n41A | DC_2A_n41A
DC_2C_n41A | No | | +| DC_2A_n66A | DC_2A_n66A | DC_2_n66 | | +| DC_2A_n71A | DC_2A_n71A | No | | +| DC_2A_n77A | DC_2A_n77A 21 | DC_2_n77 | | +| DC_2A_n77(2A) | DC_2A_n77A | DC_2_n77 | | +| DC_2A-2A_n77A 21 | DC_2A_n77A 21 | DC_2_n77 | | +| DC_2A-2A_n77(2A) | DC_2A_n77A | DC_2_n77 | | +| DC_2A_n78A | DC_2A_n78A | DC_2_n78 | | +| DC_3A_n1A | DC_3A_n1A | DC_3_n1 | | +| DC_3A_n5A | DC_3A_n5A | DC_3_n5 | | +| DC_3A_n7A | DC_3A_n7A | No | | +| DC_3A_n28A | DC_3A_n28A | No | | +| DC_3A_n41A 7 | DC_3A_n41A | DC_3_n41 | No | +| DC_3A_n77A 7 | DC_3A_n77A | DC_3_n77 | No | +| DC_3A_n78A 7
DC_3A_n78C 7
DC_3C_n78A 7 | DC_3A_n78A | DC_3_n78 | No | +| DC_3A_n79A 7
DC_3A_n79C 7 | DC_3A_n79A | No | No | +| DC_5A_n2A | DC_5A_n2A | No | | +| DC_5A_n66A | DC_5A_n66A | DC_5_n66 | | +| DC_5A_n77A | DC_5A_n77A | No | | +| DC_5A_n77(2A) | DC_5A_n77A | No | | +| DC_5A_n78A 7
DC_5A_n78C 7 | DC_5A_n78A | No | No | +| DC_7A_n1A | DC_7A_n1A | No | | +| DC_7A_n3A | DC_7A_n3A | No | | +| DC_7A_n5A | DC_7A_n5A | DC_7_n5 | | +| DC_7A_n28A | DC_7A_n28A | No | | +| DC_7A_n66A
DC_7C_n66A | DC_7A_n66A | No | | +| DC_7A_n71A | DC_7A_n71A | No | | +| DC_7A_n77A 7 | DC_7A_n77A | No | | +| DC_7A_n78A 7
DC_7C_n78A 7 | DC_7A_n78A | No | | +| DC_7A-7A_n78A 7, 21 | DC_7A_n78A 21 | No | | +| DC_8A_n1A | DC_8A_n1A | No | | +| DC_8A_n3A | DC_8A_n3A | No | | +| DC_8A_n20A | DC_8A_n20A | Yes | | +| DC_8A_n41A 7 | DC_8A_n41A | No | No | +| DC_8A_n77A 7 | DC_8A_n77A | No | No | +| DC_8A_n78A 7 | DC_8A_n78A | No | No | +| DC_8A_n94A | DC_8A_n94A_ULSUP-TDM | N/A | | +| DC_11A_n77A 7 | DC_11A_n77A | No | No | +| DC_11A_n78A 7 | DC_11A_n78A | No | No | +| DC_11A_n79A 7 | DC_11A_n79A | No | | +| DC_12A_n2A | DC_12A_n2A | No | | +| DC_12A_n5A | DC_12A_n5A | No | | + +| EN-DC configuration | Uplink EN-DC configuration
(NOTE 1) | Single UL allowed | DL interruption allowed
(Note 14) | +|------------------------------------------------------------|----------------------------------------|-------------------|--------------------------------------| +| DC_12A_n66A | DC_12A_n66A | No | | +| DC_12A_n77A | DC_12A_n77A | DC_12_n77 | | +| DC_12A_n77(2A) | DC_12A_n77A | DC_12_n77 | | +| DC_12A_n78A | DC_12A_n78A | DC_12_n78 | | +| DC_13A_n2A | DC_13A_n2A | No | | +| DC_13A_n66A | DC_13A_n66A | No | | +| DC_13A_n77A | DC_13A_n77A | No | | +| DC_14A_n2A | DC_14A_n2A | No | | +| DC_14A_n66A | DC_14A_n66A | No | | +| DC_14A_n77A | DC_14A_n77A | No | | +| DC_14A_n77(2A) | DC_14A_n77A | No | | +| DC_18A_n77A 7 | DC_18A_n77A | No | No | +| DC_18A_n78A 7 | DC_18A_n78A | No | No | +| DC_18A_n79A 7 | DC_18A_n79A | No | | +| DC_19A_n1A | DC_19A_n1A | No | | +| DC_19A_n77A 7
DC_19A_n77C 7 | DC_19A_n77A | No | | +| DC_19A_n78A 7
DC_19A_n78C 7 | DC_19A_n78A | No | No | +| DC_19A_n79A 7 | DC_19A_n79A | No | No | +| DC_20A_n1A | DC_20A_n1A | No | | +| DC_20A_n3A | DC_20A_n3A | No | | +| DC_20A_n7A | DC_20A_n7A | DC_20_n7 | | +| DC_20A_n8A | DC_20A_n8A | DC_20_n8 | | +| DC_20A_n28A 8,11,13 | DC_20A_n28A | No | | +| DC_20A_n78A 7 | DC_20A_n78A | No | | +| DC_20A_n92A | DC_20A_n92A_ULSUP-TDM | N/A | | +| DC_21A_n1A | DC_21A_n1A | No | | +| DC_21A_n28A 17 | DC_21A_n28A | DC_21_n28 | | +| DC_21A_n77A 7 | DC_21A_n77A | No | | +| DC_21A_n78A 7
DC_21A_n78C 7 | DC_21A_n78A | No | No | +| DC_21A_n79A 7
DC_21A_n79C 7 | DC_21A_n79A | No | No | +| DC_25A_n41A | DC_25A_n41A | No | | +| DC_26A_n41A | DC_26A_n41A | No | | +| DC_26A_n77A 7 | DC_26A_n77A | No | | +| DC_26A_n78A 7 | DC_26A_n78A | No | | +| DC_26A_n79A 7 | DC_26A_n79A | No | | +| DC_28A_n3A | DC_28A_n3A | No | | +| DC_28A_n5A | DC_28A_n5A | No | | +| DC_28A_n7A | DC_28A_n7A | No | | +| DC_28A_n77A 7 | DC_28A_n77A | No | No | +| DC_28A_n78A 7
DC_28A_n78C 7 | DC_28A_n78A | No | No | +| DC_28A_n79A 7 | DC_28A_n79A | No | | +| DC_30A_n2A | DC_30A_n2A | No | | +| DC_30A_n5A | DC_30A_n5A | No | | +| DC_30A_n66A | DC_30A_n66A | No | | +| DC_30A_n77A | DC_30A_n77A | No | | +| DC_30A_n77(2A) | DC_30A_n77A | No | | +| DC_38A_n78A 7 | DC_38A_n78A | No | | +| DC_39A_n41A 3
DC_39C_n41A 3 | DC_39A_n41A
DC_39C_n41A | No | No | +| DC_39A_n79A 7 | DC_39A_n79A | No | No | +| DC_40A_n1A | DC_40A_n1A | No | | +| DC_40A_n41A 3 | DC_40A_n41A | No | | +| DC_40A_n78A
DC_40C_n78A | DC_40A_n78A
DC_40C_n78A | No | | +| DC_40A_n79A 7,12
DC_40C_n79A 7,12 | DC_40A_n79A | No | No | +| DC_41A_n28A 7 | DC_41A_n28A | No | | + +| EN-DC configuration | Uplink EN-DC configuration
(NOTE 1) | Single UL allowed | DL interruption allowed
(Note 14) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------|--------------------------------------| +| DC_41A_n77A
DC_41C_n77A | DC_41A_n77A | No | | +| DC_41A_n78A
DC_41C_n78A | DC_41A_n78A | No | | +| DC_41A_n79A 6,7 | DC_41A_n79A | No | No | +| DC_42A_n77A 3,4,9,11
DC_42C_n77A 3,4,9,11
DC_42D_n77A 3,4,9,11 | N/A | N/A | | +| DC_42A_n78A 3,4,9,11
DC_42A_n78C 3,4,9,11
DC_42C_n78A 3,4,9,11
DC_42C_n78C 3,4,9,11
DC_42D_n78A 3,4,9,11
DC_42E_n78A 3,4,9,11 | N/A | N/A | | +| DC_42A_n79A 9,15
DC_42A_n79C 9,15
DC_42C_n79A 9,15
DC_42C_n79C 9,15
DC_42D_n79A 9,15
DC_42E_n79A 9,15 | N/A | N/A | | +| DC_48A_n46A | DC_48A_n46A | No | | +| DC_48A_n5A | DC_48A_n5A | No | | +| DC_48A_n66A | DC_48A_n66A | No | | +| DC_66A_n2A | DC_66A_n2A | DC_66_n2 | | +| DC_66A_n5A | DC_66A_n5A | DC_66_n5 | | +| DC_66A-66A_n5A | DC_66A_n5A | DC_66_n5 | | +| DC_66A_n25A | DC_66A_n25A | DC_66_n25 | | +| DC_66A_n41A | DC_66A_n41A | No | | +| DC_66A_n71A | DC_66A_n71A | No | | +| DC_66A_n77A | DC_66A_n77A 21 | DC_66_n77 | | +| DC_66A_n77(2A) | DC_66A_n77A | DC_66_n77 | | +| DC_66A-66A_n77A 21 | DC_66A_n77A 21 | DC_66_n77 | | +| DC_66A-66A_n77(2A) | DC_66A_n77A | DC_66_n77 | | +| DC_66A_n78A | DC_66A_n78A | No | | +| DC_71A_n2A | DC_71A_n2A | No | | +| DC_71A_n66A | DC_71A_n66A | No | | + +| EN-DC configuration | Uplink EN-DC configuration
(NOTE 1) | Single UL allowed | DL interruption allowed
(Note 14) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------|--------------------------------------| +|

NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications.

NOTE 2: Restricted to E-UTRA operation when inter-band carrier aggregation is configured. The downlink operating band for Band 46 is paired with the uplink operating band (external E-UTRA band) of the carrier aggregation configuration that is supporting the configured PCell.

NOTE 3: The minimum requirements apply only when there is non-simultaneous Tx/Rx operation between E-UTRA and NR carriers. This restriction applies also for these carriers when applicable EN-DC configuration is part of a higher order EN-DC configuration.

NOTE 4: For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16, the minimum requirements for intra-band non-contiguous EN-DC apply for the Band 42/48 and Band n77/n78 combination. For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16, when UE capability interBandContiguousMRDC is indicated, the minimum requirements for intra-band-contiguous EN-DC also should be met in addition to intra-band non-contiguous EN-DC. The intra-band requirements also apply for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.

NOTE 5: The frequency range above 3600 MHz for Band n78 is not used in this combination.

NOTE 6: The frequency range below 2506 MHz for Band 41 is not used in this combination.

NOTE 7: Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability.

NOTE 8: The frequency range in band n28 / 28 is restricted for this band combination to 703 - 733 MHz for the UL and 758-788 MHz for the DL.

NOTE 9: The combination is not used alone as fallback mode of other band combinations in which UL in Band 42 is not used.

NOTE 10: Void.

NOTE 11: For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16, the minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers is within 6 dB. For UEs indicating interBandMRDC-WithOverlapDL-Bands-r16, the power imbalance requirement defined in clause 7.6B.2.6 of 38.101-3 [4] apply. For these UEs, the power spectral density imbalance condition also applies for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.

NOTE 12: Applicable for frequency range above 4800 MHz for Band n79 in this combination.

NOTE 13: For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16, the minimum requirements apply for synchronized DL carriers with a maximum receive time difference \leq 3 usec. The requirements also apply for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.

NOTE 14: Applicable when dynamic switching between two uplink carriers is conducted. The DL interruption requirements for NR DL carrier(s) and E-UTRA DL carrier(s) are specified in clause 8.2.1.2.14 of 38.133 [25] and clause 7.32.2.12 of 36.133 [12] respectively.

NOTE 15: Simultaneous Rx/Tx capability does not apply for UEs supporting band 42 with a n77 implementation only. Same restrictions are applied to related higher order configurations.

NOTE 16: Reserved.

NOTE 17: The frequency range in band n28 is restricted for this band combination to 728 - 738 MHz for the UL and 783 - 793 MHz for the DL. This restriction applies also for these band combinations when applicable EN-DC configuration is part of a higher order EN-DC configuration. Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1.

NOTE 18: Reserved.

NOTE 19: Reserved.

NOTE 20: Reserved.

NOTE 21: Minimum requirements for PC2 are applicable for this uplink EN-DC configuration in this downlink/uplink EN-DC configuration.

| | | | + +## 5.5B.4.2 Inter-band EN-DC configurations within FR1 (three bands) + +**Table 5.5B.4.2-1: Inter-band EN-DC configurations within FR1 (three bands)** + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|------------------------------------------------------------|----------------------------------------| +| DC_1A-3A_n28A | DC_1A_n28A
DC_3A_n28A | +| DC_1A-3A_n41A 5 | DC_1A_n41A
DC_3A_n41A | +| DC_1A-3A_n77A 5 | DC_1A_n77A
DC_3A_n77A | +| DC_1A-3A_n78A 5 DC_1A-3C_n78A 5 | DC_1A_n78A
DC_3A_n78A
DC_3C_n78A | +| DC_1A-1A-3A_n78A
DC_1A-1A-3C_n78A | DC_1A_n78A
DC_3A_n78A
DC_3C_n78A | +| DC_1A-3C_n78(2A) 5 | DC_1A_n78A
DC_3A_n78A
DC_3C_n78A | +| DC_1A-3A_n79A 5 | DC_1A_n79A
DC_3A_n79A | +| DC_1A-5A_n78A 5
DC_1A-5A_n78C 5 | DC_1A_n78A
DC_5A_n78A | +| DC_1A-1A-5A_n78A | DC_1A_n78A
DC_5A_n78A | +| DC_1A-7A_n3A | DC_1A_n3A
DC_7A_n3A | +| DC_1A-7A_n28A 5 | DC_1A_n28A
DC_7A_n28A | +| DC_1A-7A_n78A 5 | DC_1A_n78A
DC_7A_n78A | +| DC_1A-8A_n3A | DC_1A_n3A
DC_8A_n3A | +| DC_1A-8A_n78A 5 | DC_1A_n78A
DC_8A_n78A | +| DC_1A-8A_n78(2A) 5 | DC_1A_n78A
DC_8A_n78A | +| DC_1A-18A_n77A 5 | DC_1A_n77A
DC_18A_n77A | +| DC_1A-19A_n77A 5 | DC_1A_n77A
DC_19A_n77A | +| DC_1A-19A_n78A 5
DC_1A-19A_n78C 5 | DC_1A_n78A
DC_19A_n78A | +| DC_1A-19A_n79A 5
DC_1A-19A_n79C 5 | DC_1A_n79A
DC_19A_n79A | +| DC_1A-20A_n3A | DC_1A_n3A
DC_20A_n3A | +| DC_1A-20A_n8A | DC_1A_n8A
DC_20A_n8A | +| DC_1A-20A_n28A 6,11,12 | DC_1A_n28A
DC_20A_n28A | +| DC_1A-20A_n78A 5 | DC_1A_n78A
DC_20A_n78A | +| DC_1A-21A_n77A 5 | DC_1A_n77A
DC_21A_n77A | +| DC_1A-21A_n78A 5
DC_1A-21A_n78C 5 | DC_1A_n78A
DC_21A_n78A | +| DC_1A-21A_n79A 5
DC_1A-21A_n79C 5 | DC_1A_n79A
DC_21A_n79A | +| DC_1A-28A_n3A | DC_1A_n3A
DC_28A_n3A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| DC_1A-28A_n5A 6 | DC_1A_n5A
DC_28A_n5A | +| DC_1A_n28A-n78A 5 | DC_1A_n28A
DC_1A_n78A | +| DC_1A-28A_n79A
DC_1A-28A_n79C | DC_1A_n79A
DC_28A_n79A | +| DC_1A-41A_n28A 5
DC_1A-41C_n28A 5 | DC_1A_n28A
DC_41A_n28A
DC_41C_n28A | +| DC_1A-41A_n41A | DC_1A_n41A | +| DC_1A-41A_n77A | DC_1A_n77A
DC_41A_n77A | +| DC_1A-41A_n78A | DC_1A_n78A
DC_41A_n78A | +| DC_1A-42A_n77A 10,11
DC_1A-42C_n77A 10,11
DC_1A-42D_n77A 10,11 | DC_1A_n77A | +| DC_1A-42A_n78A 10,11
DC_1A-42A_n78C 10,11
DC_1A-42C_n78A 10,11
DC_1A-42C_n78C 10,11
DC_1A-42D_n78A 10,11
DC_1A-42E_n78A 10,11 | DC_1A_n78A | +| DC_1A-42A_n79A
DC_1A-42A_n79C
DC_1A-42C_n79A
DC_1A-42C_n79C
DC_1A-42D_n79A
DC_1A-42E_n79A | DC_1A_n79A | +| DC_1A_n77A-n79A | DC_1A_n77A
DC_1A_n79A | +| DC_1A_n78A-n79A | DC_1A_n78A
DC_1A_n79A | +| DC_2A-5A_n66A | DC_2A_n66A
DC_5A_n66A | +| DC_2A-12A_n66A | DC_2A_n66A
DC_12A_n66A | +| DC_2A-13A_n77A | DC_2A_n77A
DC_13A_n77A | +| DC_2A-14A_n2A | DC_2A_n2A 2
DC_14A_n2A | +| DC_2A-14A_n66A | DC_2A_n66A
DC_14A_n66A | +| DC_2A-2A-14A_n66A | DC_2A_n66A
DC_14A_n66A | +| DC_2A-30A_n66A | DC_2A_n66A
DC_30A_n66A | +| DC_2A-66A_n5A | DC_2A_n5A
DC_66A_n5A | +| DC_2A-66A_n41A | DC_2A_n41A
DC_66A_n41A | +| DC_2A-66A_n71A | DC_2A_n71A
DC_66A_n71A | +| DC_2A-66A_n77A | DC_2A_n77A
DC_66A_n77A | +| DC_2A-(n)71AA | DC_2A_n71A
DC_(n)71AA | +| DC_2A_n5A-n77A 14 | DC_2A_n5A
DC_2A_n77A 14 | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|------------------------------------------------------------|------------------------------------------| +| DC_3A_n1A-n78A 5 | DC_3A_n1A
DC_3A_n78A | +| DC_3A_n1A-n79A 5 | DC_3A_n1A
DC_3A_n79A | +| DC_3A-5A_n78A 5
DC_3A-5A_n78C 5 | DC_3A_n78A
DC_5A_n78A | +| DC_3A-7A_n5A | DC_3A_n5A
DC_7A_n5A | +| DC_3A-7A_n28A | DC_3A_n28A
DC_7A_n28A | +| DC_3A-7A_n78A 5
DC_3C-7A_n78A 5 | DC_3A_n78A
DC_7A_n78A | +| DC_3A-8A_n1A | DC_3A_n1A
DC_8A_n1A | +| DC_3A-8A_n28A | DC_3A_n28A
DC_8A_n28A | +| DC_3A-8A_n78A 5 | DC_3A_n78A
DC_8A_n78A | +| DC_3A-18A_n77A | DC_3A_n77A
DC_18A_n77A | +| DC_3A-8A_n78(2A) | DC_3A_n78A
DC_8A_n78A | +| DC_3A-18A_n78A | DC_3A_n78A
DC_18A_n78A | +| DC_3A-19A_n77A 5 | DC_3A_n77A
DC_19A_n77A | +| DC_3A-19A_n78A 5
DC_3A-19A_n78C 5 | DC_3A_n78A
DC_19A_n78A | +| DC_3A-19A_n79A 5
DC_3A-19A_n79C 5 | DC_3A_n79A
DC_19A_n79A | +| DC_3A-20A_n1A | DC_3A_n1A
DC_20A_n1A | +| DC_3A-20A_n28A 5,6,11,12 | DC_3A_n28A
DC_20A_n28A | +| DC_3A-20A_n78A 5 | DC_3A_n78A
DC_20A_n78A | +| DC_3A-21A_n77A 5 | DC_3A_n77A
DC_21A_n77A | +| DC_3A-21A_n78A 5
DC_3A-21A_n78C 5 | DC_3A_n78A
DC_21A_n78A | +| DC_3A-21A_n79A 5
DC_3A-21A_n79C 5 | DC_3A_n79A
DC_21A_n79A | +| DC_3A-28A_n78A 5 | DC_3A_n78A
DC_28A_n78A | +| DC_3A_n28A-n78A 5 | DC_3A_n28A
DC_3A_n78A | +| DC_3A-40A_n1A | DC_3A_n1A
DC_40A_n1A | +| DC_3A-41A_n28A 5
DC_3A-41C_n28A 5 | DC_3A_n28A
DC_41A_n28A
DC_41C_n28A | +| DC_3A-41A_n41A | DC_3A_n41A | +| DC_3A-41A_n77A
DC_3A-41C_n77A | DC_3A_n77A
DC_41A_n77A | +| DC_3A-41A_n77(2A) | DC_3A_n77A
DC_41A_n77A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| DC_3A-42A_n77A 10,11
DC_3A-42C_n77A 10,11
DC_3A-42D_n77A 10,11 | DC_3A_n77A | +| DC_3A-42A_n78A 10,11
DC_3A-42A_n78C 10,11
DC_3A-42C_n78A 10,11
DC_3A-42C_n78C 10,11
DC_3A-42D_n78A 10,11
DC_3A-42E_n78A 10,11 | DC_3A_n78A | +| DC_3A-42A_n79A
DC_3A-42A_n79C
DC_3A-42C_n79A
DC_3A-42C_n79C
DC_3A-42D_n79A
DC_3A-42E_n79A | DC_3A_n79A | +| DC_3A_n77A-n79A | DC_3A_n77A
DC_3A_n79A | +| DC_3A_n78A-n79A | DC_3A_n78A
DC_3A_n79A | +| DC_5A-7A_n78A | DC_5A_n78A
DC_7A_n78A | +| DC_5A-30A_n66A | DC_5A_n66A
DC_30A_n66A | +| DC_7A_n5A-n78A
DC_7C_n5A-n78A | DC_7A_n5A
DC_7C_n5A
DC_7A_n78A
DC_7C_n78A | +| DC_7A-8A_n1A | DC_7A_n1A
DC_8A_n1A | +| DC_7A-8A_n3A | DC_7A_n3A
DC_8A_n3A | +| DC_7A-20A_n1A | DC_7A_n1A
DC_20A_n1A | +| DC_7A-20A_n3A | DC_7A_n3A
DC_20A_n3A | +| DC_7A-20A_n8A | DC_7A_n8A
DC_20A_n8A | +| DC_7A-20A_n28A 6,11,12 | DC_7A_n28A
DC_20A_n28A | +| DC_7A-20A_n78A 5 | DC_7A_n78A
DC_20A_n78A | +| DC_7A-28A_n3A | DC_7A_n3A
DC_28A_n3A | +| DC_7A-28A_n5A 6 | DC_7A_n5A
DC_28A_n5A | +| DC_7A-28A_n78A 5 | DC_7A_n78A
DC_28A_n78A | +| DC_7A_n28A-n78A 5
DC_7C_n28A-n78A | DC_7A_n28A
DC_7A_n78A
DC_7C_n28A
DC_7C_n78A | +| DC_12A-30A_n66A | DC_12A_n66A
DC_30A_n66A | +| DC_13A-66A_n2A | DC_13A_n2A
DC_66A_n2A | +| DC_13A-66A_n77A | DC_13A_n77A
DC_66A_n77A | +| DC_13A_n2A-n77A 14 | DC_13A_n2A
DC_13A_n77A 14 | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| DC_18A-41A_n3A | DC_18A_n3A
DC_41A_n3A | +| DC_18A-41A_n77A
DC_18A-41C_n77A | DC_18A_n77A
DC_41A_n77A
DC_41C_n77A | +| DC_18A-41A_n78A
DC_18A-41C_n78A | DC_18A_n78A
DC_41A_n78A
DC_41C_n78A | +| DC_19A_n1A-n78A 5 | DC_19A_n1A
DC_19A_n78A | +| DC_19A_n1A-n79A 5 | DC_19A_n1A
DC_19A_n79A | +| DC_19A-21A_n77A 5 | DC_19A_n77A
DC_21A_n77A | +| DC_19A-21A_n78A 5
DC_19A-21A_n78C 5 | DC_19A_n78A
DC_21A_n78A | +| DC_19A-21A_n79A 5
DC_19A-21A_n79C 5 | DC_19A_n79A
DC_21A_n79A | +| DC_19A-42A_n77ADC_19A-42C_n77A | DC_19A_n77A | +| DC_19A-42A_n78A
DC_19A-42C_n78A
DC_19A-42A_n78C
DC_19A-42C_n78C | DC_19A_n78A | +| DC_19A-42A_n79A
DC_19A-42C_n79A
DC_19A-42A_n79C
DC_19A-42C_n79C | DC_19A_n79A | +| DC_19A_n77A-n79A | DC_19A_n77A
DC_19A_n79A | +| DC_19A_n78A-n79A | DC_19A_n78A
DC_19A_n79A | +| DC_20A_n28A-n78A 5,6,11,12 | DC_20A_n28A
DC_20A_n78A | +| DC_20A_n76A-n78A 5 | DC_20A_n78A | +| DC_21A_n1A-n78A 5 | DC_21A_n1A
DC_21A_n78A | +| DC_21A_n1A-n79A 5 | DC_21A_n1A
DC_21A_n79A | +| DC_21A-42A_n77A 10,11
DC_21A-42C_n77A 10,11 | DC_21A_n77A | +| DC_21A-42A_n78A 10,11
DC_21A-42A_n78C 10,11
DC_21A-42C_n78A 10,11
DC_21A-42C_n78C 10,11 | DC_21A_n78A | +| DC_21A-42A_n79A
DC_21A-42A_n79C
DC_21A-42C_n79A
DC_21A-42C_n79C | DC_21A_n79A | +| DC_21A_n77A-n79A | DC_21A_n77A
DC_21A_n79A | +| DC_21A_n78A-n79A | DC_21A_n78A
DC_21A_n79A | +| DC_28A_n7A-n78A | DC_28A_n7A
DC_28A_n78A | +| DC_28A-42A_n78A 10,11 | DC_28A_n78A | +| DC_41A-42A_n78A 10,11 | DC_41A_n78A | +| DC_66A_n2A-n77A 14 | DC_66A_n2A
DC_66A_n77A 14 | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-------------------------------|-----------------------------------------| +| DC_66A_n5A-n77A 14 | DC_66A_n5A
DC_66A_n77A 14 | +| DC_66A-(n)71AA | DC_66A_n71A
DC_(n)71AA | + +NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. + +NOTE 2: Only single switched UL is supported. + +NOTE 3: Restricted to E-UTRA operation when inter-band carrier aggregation is configured. The downlink operating band for Band 46 is paired with the uplink operating band (external E-UTRA band) of the carrier aggregation configuration that is supporting the configured PCell. + +NOTE 4: If a UE is configured with both NR UL and NR SUL carriers in a cell, the switching time between NR UL carrier and NR SUL carrier can be up to 140us and placed in SUL resources. + +NOTE 5: Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability + +NOTE 6: The frequency range in band n28 is restricted for this band combination to 703-733 MHz for the UL and 758-788 MHz for the DL. + +NOTE 7: Void. + +NOTE 8: Reserved. + +NOTE 9: Reserved. + +NOTE 10: For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, the minimum requirements for intra-band non-contiguous EN-DC apply for the Band 42 and Band n77/n78 combination. For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, when UE capability *interBandContiguousMRDC* is indicated, the minimum requirements for intra-band-contiguous EN-DC also should be met in addition to intra-band non-contiguous EN-DC. + +NOTE 11: For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, the minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers contained in overlapping or partially overlapping DL bands is within 6 dB. + +NOTE 12: For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, the minimum requirements apply for synchronized DL carriers with a maximum receive time difference $\leq 3$ usec between overlapping or partially overlapping DL bands contained in different cell groups. + +NOTE 13: Reserved. + +NOTE 14: Minimum requirements for PC2 are applicable for this uUplink EN-DC configuration in this downlink/uplink to EN-DC configuration. + +### 5.5B.4.3 Inter-band EN-DC configurations within FR1 (four bands) + +**Table 5.5B.4.3-1: Inter-band EN-DC configurations within FR1 (four bands)** + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| DC_1A-3A-7A_n28A | DC_1A_n28A
DC_3A_n28A
DC_7A_n28A | +| DC_1A-3A-7A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_7A_n78A | +| DC_1A-3A-8A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_8A_n78A | +| DC_1A-3A-19A_n77A 2 | DC_1A_n77A
DC_3A_n77A
DC_19A_n77A | +| DC_1A-3A-19A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_19A_n78A | +| DC_1A-3A-19A_n79A 2 | DC_1A_n79A
DC_3A_n79A
DC_19A_n79A | +| DC_1A-3A-20A_n28A 3,7,8 | DC_1A_n28A
DC_3A_n28A
DC_20A_n28A | +| DC_1A-3A-20A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_20A_n78A | +| DC_1A-3A-21A_n77A 2 | DC_1A_n77A
DC_3A_n77A
DC_21A_n77A | +| DC_1A-3A-21A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_21A_n78A | +| DC_1A-3A-21A_n79A 2 | DC_1A_n79A
DC_3A_n79A
DC_21A_n79A | +| DC_1A-3A-28A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_28A_n78A | +| DC_1A-3A_n28A-n78A 2 | DC_1A_n28A
DC_1A_n78A
DC_3A_n28A
DC_3A_n78A | +| DC_1A-3A-42A_n78A 6,7
DC_1A-3A-42C_n78A 6,7 DC_1A-3A-42D_n78A 6,7 | DC_1A_n78A
DC_3A_n78A | +| DC_1A-3A-42A_n79A
DC_1A-3A-42C_n79ADC_1A-3A-42D_n79A | DC_1A_n79A
DC_3A_n79A | +| DC_1A-7A-20A_n28A 3,7,8 | DC_1A_n28A
DC_7A_n28A
DC_20A_n28A | +| DC_1A-7A-20A_n78A 2 | DC_1A_n78A
DC_7A_n78A
DC_20A_n78A | +| DC_1A-7A-28A_n78A | DC_1A_n78A
DC_7A_n78A
DC_28A_n78A | +| DC_1A-7A_n28A-n78A 2 | DC_1A_n28A
DC_1A_n78A
DC_7A_n28A
DC_7A_n78A | +| DC_1A-19A-21A_n77A | DC_1A_n77A
DC_19A_n77A
DC_21A_n77A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| DC_1A-19A-21A_n78A 2
DC_1A-19A-21A_n78C 2 | DC_1A_n78A
DC_19A_n78A
DC_21A_n78A | +| DC_1A-19A-21A_n79A
DC_1A-19A-21A_n79C | DC_1A_n79A
DC_19A_n79A
DC_21A_n79A | +| DC_1A-19A-42A_n77A 6,7
DC_1A-19A-42C_n77A 6,7 | DC_19A_n77A | +| DC_1A-19A-42A_n78A
DC_1A-19A-42A_n78C
DC_1A-19A-42C_n78A
DC_1A-19A-42C_n78C | DC_1A_n78A
DC_19A_n78A | +| DC_1A-19A-42A_n79A
DC_1A-19A-42A_n79C
DC_1A-19A-42C_n79A
DC_1A-19A-42C_n79C | DC_1A_n79A
DC_19A_n79A | +| DC_1A-20A_n28A-n78A 2,3,7,8 | DC_1A_n28A
DC_1A_n78A
DC_20A_n28A
DC_20A_n78A | +| DC_1A-21A-42A_n77A 6,7
DC_1A-21A-42C_n77A 6,7 | DC_1A_n77A
DC_21A_n77A | +| DC_1A-21A-42A_n78A 6,7
DC_1A-21A-42A_n78C 6,7
DC_1A-21A-42C_n78A 6,7
DC_1A-21A-42C_n78C 6,7 | DC_1A_n78A
DC_21A_n78A | +| DC_1A-21A-42A_n79A
DC_1A-21A-42A_n79C
DC_1A-21A-42C_n79A
DC_1A-21A-42C_n79C | DC_1A_n79A
DC_21A_n79A | +| DC_2A-7A-13A_n66A
DC_2A-7C-13A_n66A | DC_2A_n66A
DC_7A_n66A
DC_13A_n66A | +| DC_2A-7A-7A-13A_n66A | DC_2A_n66A
DC_7A_n66A
DC_13A_n66A | +| DC_2A-7A-66A_n66A
DC_2A-7C-66A_n66A | DC_2A_n66A
DC_7A_n66A
DC_66A_n66A 4 | +| DC_2A-7A-7A-66A_n66A | DC_2A_n66A
DC_7A_n66A
DC_66A_n66A 4 | +| DC_2A-7C-66A_n78A | DC_2A_n78A
DC_7A_n78A
DC_66A_n78A | +| DC_2A-7A-7A-66A_n78A | DC_2A_n78A
DC_7A_n78A
DC_66A_n78A | +| DC_2A-13A-66A_n77A 9 | DC_2A_n77A 9
DC_13A_n77A 9
DC_66A_n77A 9 | +| DC_2A-14A-66A_n2A | DC_2A_n2A 4
DC_14A_n2A
DC_66A_n2A | +| DC_2A-14A-66A-66A_n2A | DC_2A_n2A 4
DC_14A_n2A
DC_66A_n2A | +| DC_2A-14A-66A_n66A | DC_2A_n66A
DC_14A_n66A
DC_66A_n66A 4 | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| DC_2A-2A-14A-66A_n66A | DC_2A_n66A
DC_14A_n66A
DC_66A_n66A 4 | +| DC_2A-66A_n5A-n77A 9 | DC_2A_n5A
DC_2A_n77A 9
DC_66A_n5A
DC_66A_n77A 9 | +| DC_2A-66A-(n)71AA | DC_2A_n71A
DC_66A_n71A
DC_(n)71AA | +| DC_3A-7A-20A_n8A | DC_3A_n8A
DC_7A_n8A
DC_20A_n8A | +| DC_3A-7A-20A_n28A 3,7,8 | DC_3A_n28A
DC_7A_n28A
DC_20A_n28A | +| DC_3A-7A-20A_n78A 2 | DC_3A_n78A
DC_7A_n78A
DC_20A_n78A | +| DC_3A-7A-28A_n78A 2 | DC_3A_n78A
DC_7A_n78A
DC_28A_n78A | +| DC_3A-7A_n28A-n78A 2 | DC_3A_n28A
DC_3A_n78A
DC_7A_n28A
DC_7A_n78A | +| DC_3A-19A-21A_n78A 2
DC_3A-19A-21A_n78C 2 | DC_3A_n78A
DC_19A_n78A
DC_21A_n78A | +| DC_3A-19A-21A_n79A 2
DC_3A-19A-21A_n79C 2 | DC_3A_n79A
DC_19A_n79A
DC_21A_n79A | +| DC_3A-19A-42A_n77A 6,7
DC_3A-19A-42C_n77A 6,7 | DC_3A_n77A
DC_19A_n77A | +| DC_3A-19A-42A_n78A 6,7
DC_3A-19A-42A_n78C 6,7
DC_3A-19A-42C_n78A 6,7
DC_3A-19A-42C_n78C 6,7 | DC_3A_n78A
DC_19A_n78A | +| DC_3A-19A-42A_n79A 2
DC_3A-19A-42A_n79C 2
DC_3A-19A-42C_n79A 2
DC_3A-19A-42C_n79C 2 | DC_3A_n79A
DC_19A_n79A | +| DC_3A-20A_n28A-n78A 2,3,7,8 | DC_3A_n28A
DC_3A_n78A
DC_20A_n28A
DC_20A_n78A | +| DC_3A-21A-42A_n77A 6,7
DC_3A-21A-42C_n77A 6,7 | DC_3A_n77A
DC_21A_n77A | +| DC_3A-21A-42A_n78A 6,7
DC_3A-21A-42A_n78C 6,7
DC_3A-21A-42C_n78A 6,7
DC_3A-21A-42C_n78C 6,7 | DC_3A_n78A
DC_21A_n78A | +| DC_3A-21A-42A_n79A
DC_3A-21A-42A_n79C
DC_3A-21A-42C_n79A
DC_3A-21A-42C_n79C | DC_3A_n79A
DC_21A_n79A | +| DC_7A-20A_n28A-n78A 2,3,7,8 | DC_7A_n28A
DC_7A_n78A
DC_20A_n28A
DC_20A_n78A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| DC_13A-66A_n2A-n77A 9 | DC_13A_n2A
DC_13A_n77A 9
DC_66A_n2A
DC_66A_n77A 9 | +| DC_19A-21A-42A_n77A 6,7
DC_19A-21A-42C_n77A 6,7 | DC_19A_n77A
DC_21A_n77A | +| DC_19A-21A-42A_n78A 6,7
DC_19A-21A-42A_n78C 6,7
DC_19A-21A-42C_n78A 6,7
DC_19A-21A-42C_n78C 6,7 | DC_19A_n78A
DC_21A_n78A | +| DC_19A-21A-42A_n79A
DC_19A-21A-42A_n79C
DC_19A-21A-42C_n79A
DC_19A-21A-42C_n79C | DC_19A_n79A
DC_21A_n79A | + +NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. + +NOTE 2: Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability + +NOTE 3: The frequency range in band n28 is restricted for this band combination to 703-733 MHz for the UL and 758-788 MHz for the DL. + +NOTE 4: Only single switched UL is supported. + +NOTE 5: UL carrier shall be supported in Band 2 or band 66 only. Power imbalance between downlink carriers on Band 7 and Band 38 is assumed to be within 6dB. + +NOTE 6: For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, the minimum requirements for intra-band non-contiguous EN-DC apply for the Band 42 and Band n77/n78 combination. For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, when UE capability *interBandContiguousMRDC* is indicated, the minimum requirements for intra-band-contiguous EN-DC also should be met in addition to intra-band non-contiguous EN-DC. + +NOTE 7: For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, the minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers contained in overlapping or partially overlapping DL bands is within 6 dB. + +NOTE 8: For UEs not indicating *interBandMRDC-WithOverlapDL-Bands-r16*, the minimum requirements apply for synchronized DL carriers with a maximum receive time difference $\leq 3$ usec between overlapping or partially overlapping DL bands contained in different cell groups. + +NOTE 9: Minimum requirements for PC2 are applicable for this uplink EN-DC configuration in this downlink/uplink EN-DC configuration. + +#### 5.5B.4.4 Inter-band EN-DC configurations within FR1 (five bands) + +**Table 5.5B.4.4-1: Inter-band EN-DC configurations within FR1 (five bands)** + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| DC_1A-3A-7A-20A_n28A 3,6,7 | DC_1A_n28A
DC_3A_n28A
DC_7A_n28A
DC_20A_n28A | +| DC_1A-3A-7A-20A_n78A 2 | DC_1A_n78A
DC_3A_n78A
DC_7A_n78A
DC_20A_n78A | +| DC_1A-3A-7A_n28A-n78A 2 | DC_1A_n28A
DC_1A_n78A
DC_3A_n28A
DC_3A_n78A
DC_7A_n28A
DC_7A_n78A | +| DC_1A-3A-7A-28A_n78A | DC_1A_n78A
DC_3A_n78A
DC_7A_n78A
DC_28A_n78A | +| DC_1A-3A-19A-42A_n78A 5,6
DC_1A-3A-19A-42C_n78A 5,6 | DC_1A_n78A
DC_3A_n78A
DC_19A_n78A | +| DC_1A-3A-19A-42A_n79A
DC_1A-3A-19A-42C_n79A | DC_1A_n79A
DC_3A_n79A
DC_19A_n79A | +| DC_1A-3A-20A_n28A-n78A 2,3,6,7 | DC_1A_n28A
DC_1A_n78A
DC_3A_n28A
DC_3A_n78A
DC_20A_n28A
DC_20A_n78A | +| DC_1A-3A-21A-42A_n78A 5,6
DC_1A-3A-21A-42C_n78A 5,6 | DC_1A_n78A
DC_3A_n78A
DC_21A_n78A | +| DC_1A-3A-21A-42A_n79A
DC_1A-3A-21A-42C_n79A | DC_1A_n79A
DC_3A_n79A
DC_21A_n79A | +| DC_1A-7A-20A_n28A-n78A 2,3,6,7 | DC_1A_n28A
DC_1A_n78A
DC_7A_n28A
DC_7A_n78A
DC_20A_n28A
DC_20A_n78A | +| DC_1A-19A-21A-42A_n78A 5,6
DC_1A-19A-21A-42A_n78C 5,6
DC_1A-19A-21A-42C_n78A 5,6
DC_1A-19A-21A-42C_n78C 5,6 | DC_1A_n78A
DC_19A_n78A
DC_21A_n78A | +| DC_1A-19A-21A-42A_n79A
DC_1A-19A-21A-42A_n79C
DC_1A-19A-21A-42C_n79A
DC_1A-19A-21A-42C_n79C | DC_1A_n79A
DC_19A_n79A
DC_21A_n79A | +| DC_3A-7A-20A_n28A-n78A 2,3,6,7 | DC_3A_n28A
DC_3A_n78A
DC_7A_n28A
DC_7A_n78A
DC_20A_n28A
DC_20A_n78A | +| DC_3A-19A-21A-42A_n78A 5,6
DC_3A-19A-21A-42C_n78A 5,6 | DC_3A_n78A
DC_19A_n78A
DC_21A_n78A | +| DC_3A-19A-21A-42A_n79A 5,6
DC_3A-19A-21A-42C_n79A 5,6 | DC_3A_n79A
DC_19A_n79A
DC_21A_n79A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Uplink EN-DC configurations are the configurations supported by the present release of specifications. | +| NOTE 2: | Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability | +| NOTE 3: | The frequency range in band n28 is restricted for this band combination to 703-733 MHz for the UL and 758-788 MHz for the DL | +| NOTE 4: | Reserved. | +| NOTE 5: | For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16 , the minimum requirements for intra-band non-contiguous EN-DC apply for the Band 42 and Band n77/n78 combination. For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16 , when UE capability interBandContiguousMRDC is indicated, the minimum requirements for intra-band-contiguous EN-DC also should be met in addition to intra-band non-contiguous EN-DC. | +| NOTE 6: | For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16 , the minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers contained in overlapping or partially overlapping DL bands is within 6 dB. | +| NOTE 7: | For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16 , the minimum requirements apply for synchronized DL carriers with a maximum receive time difference $\leq 3$ usec between overlapping or partially overlapping DL bands contained in different cell groups. | + +#### 5.5B.4.5 Inter-band EN-DC configurations within FR1 (six bands) + +**Table 5.5B.4.5-1: Inter-band EN-DC configurations within FR1 (six bands)** + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_1A-3A-7A-20A_n28A-n78A 2,3,5,6 | DC_1A_n28A
DC_1A_n78A
DC_3A_n28A
DC_3A_n78A
DC_7A_n28A
DC_7A_n78A
DC_20A_n28A
DC_20A_n78A | +| NOTE 1: | Uplink EN-DC configurations are the configurations supported by the present release of specifications. | +| NOTE 2: | Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability. | +| NOTE 3: | The frequency range in band n28 is restricted for this band combination to 703-733 MHz for the UL and 758-788 MHz for the DL. | +| NOTE 4: | Reserved | +| NOTE 5: | For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16 , the minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers contained in overlapping or partially overlapping DL bands is within 6 dB. | +| NOTE 6: | For UEs not indicating interBandMRDC-WithOverlapDL-Bands-r16 , the minimum requirements apply for synchronized DL carriers with a maximum receive time difference $\leq 3$ usec between overlapping or partially overlapping DL bands contained in different cell groups. | + +## 5.5B.4a Inter-band NE-DC within FR1 + +### 5.5B.4a.1 Inter-band NE-DC configurations within FR1 (two bands) + +**Table 5.5B.4a.1-1: Inter-band NE-DC configurations within FR1 (two bands)** + +| NE-DC configuration | Uplink NE-DC configuration (NOTE 1) | Single UL allowed | +|----------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------| +| DC_n28A_3A
DC_n28A_3C | DC_n28A_3A | No | +| DC_n28A_39A
DC_n28A_39C | DC_n28A_39A | No | +| NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. | | | + +## 5.5B.5 Inter-band EN-DC including FR2 + +Supported channel bandwidths for E-UTRA operating bands and CA configurations are defined in TS 36.521-1 [10] and for NR operating bands and CA configurations in TS 38.521-1 [8], TS 38.521-2 [9] and present document. + +## 5.5B.5.1 Inter-band EN-DC configurations including FR2 (two bands) + +Table 5.5B.5.1-1: Inter-band EN-DC configurations including FR2 (two bands) + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| DC_1A_n257A | DC_1A_n257A | +| DC_2A_n257A | DC_2A_n257A | +| DC_2A_n257(2A) | DC_2A_n257A | +| DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_2A_n260J
DC_2A_n260K
DC_2A_n260L
DC_2A_n260M
DC_2C_n260A | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H | +| DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A_n261J
DC_2A_n261M | DC_2A_n261G
DC_2A_n261H
DC_2A_n261I | +| DC_2A_n261(2A)
DC_2A_n261(3A) | DC_2A_n261A | +| DC_2A_n261(2G)
DC_2A_n261(2H) | DC_2A_n261A
DC_2A_n261G
DC_2A_n261H | +| DC_2A_n261(A-G)
DC_2A_n261(A-2G)
DC_2A_n261(A-H)
DC_2A_n261(A-I)
DC_2A_n261(G-H)
DC_2A_n261(G-I)
DC_2A_n261(H-I)
DC_2A_n261(2A-G)
DC_2A_n261(2A-I) | DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I | +| DC_2A_n261(A-G-H)
DC_2A_n261(A-G-I) | DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I | +| DC_3A_n257G
DC_3A_n257H
DC_3A_n257I | DC_3A_n257G
DC_3A_n257H
DC_3A_n257I | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| +| DC_5A_n260A
DC_5A_n260G
DC_5A_n260H
DC_5A_n260I
DC_5A_n260J
DC_5A_n260K
DC_5A_n260L
DC_5A_n260M
DC_5A_n260ODC_5B_n260A | DC_5A_n260A
DC_5A_n260G
DC_5A_n260H
DC_5A_n260O
DC_5A_n260P
DC_5A_n260Q | +| DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I
DC_5A_n261J
DC_5A_n261M | DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I | +| DC_5A_n261(2A)
DC_5A_n261(3A)
DC_5A_n261(4A) | DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I | +| DC_8A_n257A
DC_8A_n257D
DC_8A_n257E
DC_8A_n257F
DC_8A_n257G
DC_8A_n257H
DC_8A_n257I
DC_8A_n257J
DC_8A_n257K
DC_8A_n257L
DC_8A_n257M | DC_8A_n257A | +| DC_13A_n257A | DC_13A_n257A | +| DC_13A_n260A
DC_13A_n260G
DC_13A_n260H
DC_13A_n260I
DC_13A_n260J
DC_13A_n260M | DC_13A_n260A
DC_13A_n260G
DC_13A_n260H
DC_13A_n260O | +| DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I | DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I | +| DC_18A_n257A
DC_18A_n257I | DC_18A_n257A
DC_18A_n257I | +| DC_19A_n257A
DC_19A_n257D
DC_19A_n257G
DC_19A_n257H
DC_19A_n257I | DC_19A_n257A
DC_19A_n257G
DC_19A_n257H
DC_19A_n257I | +| DC_20A_n257A | DC_20A_n257A | +| DC_21A_n257A
DC_21A_n257G | DC_21A_n257A
DC_21A_n257G | +| DC_66A_n260A
DC_66A_n260D
DC_66A_n260E
DC_66A_n260F
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I
DC_66A_n260J
DC_66A_n260K
DC_66A_n260L
DC_66A_n260M
DC_66A_n260O | DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260O
DC_66A_n260P
DC_66A_n260Q | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| DC_66A-66A_n260A
DC_66A-66A_n260G
DC_66A-66A_n260H
DC_66A-66A_n260I
DC_66A-66A_n260J
DC_66A-66A_n260K
DC_66A-66A_n260L
DC_66A-66A_n260M | DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | +| DC_66A_n261G
DC_66A_n261H
DC_66A_n261I
DC_66A_n261J
DC_66A_n261K
DC_66A_n261L
DC_66A_n261M | DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I | +| DC_66A_n261(2G)
DC_66A_n261(2H) | DC_66A_n261A
DC_66A_n261G
DC_66A_n261H | +| DC_66A_n261(A-2G)
DC_66A_n261(2A-G)
DC_66A_n261(2A-H)
DC_66A_n261(2A-I) | DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I | +| DC_66A_n261(A-G-H)
DC_66A_n261(A-G-I) | DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I | +| DC_66A-66A_n260G
DC_66A-66A_n260H
DC_66A-66A_n260I
DC_66A-66A_n260J
DC_66A-66A_n260K
DC_66A-66A_n260L
DC_66A-66A_n260M | DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I | + +NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. + +NOTE 2: Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability for all of the above combinations + +### 5.5B.5.2 Inter-band EN-DC configurations including FR2 (three bands) + +**Table 5.5B.5.2-1: Inter-band EN-DC configurations including FR2 (three bands)** + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| DC_1A-3A_n257A 2
DC_1A-3A_n257G
DC_1A-3A_n257H
DC_1A-3A_n257I | DC_1A_n257A
DC_3A_n257A
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I | +| DC_1A-18A_n257A 2
DC_1A-18A_n257I | DC_1A_n257A
DC_1A_n257I
DC_18A_n257A
DC_18A_n257I | +| DC_1A-19A_n257A 2
DC_1A-19A_n257G
DC_1A-19A_n257H
DC_1A-19A_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_19A_n257A | +| DC_1A-21A_n257A 2
DC_1A-21A_n257G
DC_1A-21A_n257H
DC_1A-21A_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_21A_n257A
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I | +| DC_1A-41A_n257A
DC_1A-41A_n257I | DC_1A_n257A
DC_1A_n257I
DC_41A_n257A
DC_41A_n257I | +| DC_1A-42A_n257A
DC_1A-42A_n257G
DC_1A-42A_n257H
DC_1A-42A_n257I
DC_1A-42C_n257A
DC_1A-42D_n257A
DC_1A-42D_n257G
DC_1A-42D_n257H
DC_1A-42D_n257I
DC_1A-42E_n257A
DC_1A-42E_n257G
DC_1A-42E_n257H
DC_1A-42E_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_42A_n257A | +| DC_2A-5A_n257A 2 | DC_2A_n257A
DC_5A_n257A | +| DC_2A-5A_n260A
DC_2A-5A_n260G
DC_2A-5A_n260H
DC_2A-5A_n260I
DC_2A-5A_n260J
DC_2A-5A_n260K
DC_2A-5A_n260L
DC_2A-5A_n260M | DC_2A_n260A
DC_5A_n260A | +| DC_2A-5A_n261A
DC_2A-5A_n261G
DC_2A-5A_n261H
DC_2A-5A_n261I
DC_2A-5A_n261J
DC_2A-5A_n261K
DC_2A-5A_n261L
DC_2A-5A_n261M | DC_2A_n261A
DC_5A_n261A
DC_2A_n261G
DC_5A_n261G
DC_2A_n261H
DC_5A_n261H
DC_2A_n261I
DC_5A_n261I | +| DC_2A-13A_n260A 2 | DC_2A_n260A
DC_13A_n260A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| DC_2A-13A_n261A
DC_2A-13A_n261G
DC_2A-13A_n261H
DC_2A-13A_n261I
DC_2A-13A_n261J
DC_2A-13A_n261K
DC_2A-13A_n261L
DC_2A-13A_n261M | DC_2A_n261A
DC_13A_n261A
DC_2A_n261G
DC_13A_n261G
DC_2A_n261H
DC_13A_n261H | +| DC_2A-13A_n261(2A)
DC_2A-13A_n261(2G)
DC_2A-13A_n261(2H)
DC_2A-13A_n261(3A) | DC_2A_n261A
DC_13A_n261A
DC_2A_n261G
DC_13A_n261G
DC_2A_n261H
DC_13A_n261H | +| DC_2A-13A_n261(A-G)
DC_2A-13A_n261(A-2G)
DC_2A-13A_n261(A-H)
DC_2A-13A_n261(A-I)
DC_2A-13A_n261(G-H)
DC_2A-13A_n261(G-I)
DC_2A-13A_n261(H-I)
DC_2A-13A_n261(2A-G)
DC_2A-13A_n261(2A-H)
DC_2A-13A_n261(2A-I) | DC_2A_n261A
DC_13A_n261A
DC_2A_n261G
DC_13A_n261G
DC_2A_n261H
DC_13A_n261H | +| DC_2A-13A_n261(A-G-H)
DC_2A-13A_n261(A-G-I) | DC_2A_n261A
DC_13A_n261A
DC_2A_n261G
DC_13A_n261G
DC_2A_n261H
DC_13A_n261H | +| DC_2A-14A_n260A
DC_2A-14A_n260G
DC_2A-14A_n260H
DC_2A-14A_n260I | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I | +| DC_2A-2A-14A_n260A
DC_2A-2A-14A_n260G
DC_2A-2A-14A_n260H
DC_2A-2A-14A_n260I | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I | +| DC_2A-30A_n260A
DC_2A-30A_n260G
DC_2A-30A_n260H
DC_2A-30A_n260I
DC_2A-30A_n260J
DC_2A-30A_n260K
DC_2A-30A_n260L
DC_2A-30A_n260M | DC_2A_n260A
DC_30A_n260A | +| DC_2A-66A_n257A 2 | DC_2A_n257A
DC_66A_n257A | +| DC_2A-66A_n260A
DC_2A-66A_n260G
DC_2A-66A_n260H
DC_2A-66A_n260I
DC_2A-66A_n260J
DC_2A-66A_n260K
DC_2A-66A_n260L
DC_2A-66A_n260M | DC_2A_n260A
DC_66A_n260A
DC_2A_n260G
DC_66A_n260G
DC_2A_n260H
DC_66A_n260H
DC_2A_n260I
DC_66A_n260I | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| DC_3A-18A_n257A
DC_3A-18A_n257I | DC_3A_n257A
DC_3A_n257I
DC_18A_n257A
DC_18A_n257I | +| DC_3A-19A_n257A 2
DC_3A-19A_n257D 2
DC_3A-19A_n257G
DC_3A-19A_n257H
DC_3A-19A_n257I | DC_3A_n257A
DC_3A_n257D
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_19A_n257A
DC_19A_n257D | +| DC_3A-21A_n257A 2
DC_3A-21A_n257D 2
DC_3A-21A_n257G
DC_3A-21A_n257H
DC_3A-21A_n257I | DC_3A_n257A
DC_3A_n257D
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_21A_n257A
DC_21A_n257D | +| DC_3A-41A_n257A
DC_3A-41A_n257I | DC_3A_n257A
DC_3A_n257I
DC_41A_n257A
DC_41A_n257I | +| DC_3A-42A_n257A 2
DC_3A-42A_n257D 2
DC_3A-42A_n257G
DC_3A-42A_n257H
DC_3A-42A_n257I
DC_3A-42C_n257A 2
DC_3A-42C_n257D 2
DC_3A-42C_n257G
DC_3A-42C_n257H
DC_3A-42C_n257I
DC_3A-42D_n257A 2
DC_3A-42D_n257G
DC_3A-42D_n257H
DC_3A-42D_n257I
DC_3A-42E_n257A 2
DC_3A-42E_n257G
DC_3A-42E_n257H
DC_3A-42E_n257I | DC_3A_n257A
DC_3A_n257D
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_42A_n257A
DC_42A_n257D | +| DC_5A-7A_n257A 2 | DC_5A_n257A
DC_7A_n257A | +| DC_5A-30A_n260A
DC_5A-30A_n260G
DC_5A-30A_n260H
DC_5A-30A_n260I
DC_5A-30A_n260J
DC_5A-30A_n260K
DC_5A-30A_n260L
DC_5A-30A_n260M | DC_5A_n260A
DC_30A_n260A | +| DC_5A-66A_n257A | DC_5A_n257A
DC_66A_n257A | +| DC_5A-66A_n260A
DC_5A-66A_n260G
DC_5A-66A_n260H
DC_5A-66A_n260I
DC_5A-66A_n260J
DC_5A-66A_n260K
DC_5A-66A_n260L
DC_5A-66A_n260M | DC_5A_n260A
DC_66A_n260A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_12A-30A_n260A
DC_12A-30A_n260G
DC_12A-30A_n260H
DC_12A-30A_n260I
DC_12A-30A_n260J
DC_12A-30A_n260K
DC_12A-30A_n260L
DC_12A-30A_n260M | DC_12A_n260A
DC_30A_n260A | +| DC_12A-66A_n260A
DC_12A-66A_n260G
DC_12A-66A_n260H
DC_12A-66A_n260I
DC_12A-66A_n260J
DC_12A-66A_n260K
DC_12A-66A_n260L
DC_12A-66A_n260M | DC_12A_n260A
DC_66A_n260A | +| DC_13A-66A_n260A 2 | DC_13A_n260A
DC_66A_n260A | +| DC_14A-30A_n260A
DC_14A-30A_n260G
DC_14A-30A_n260H
DC_14A-30A_n260I | DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_30A_n260A
DC_30A_n260G
DC_30A_n260H
DC_30A_n260I | +| DC_14A-66A_n260A
DC_14A-66A_n260G
DC_14A-66A_n260H
DC_14A-66A_n260I | DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | +| DC_14A-66A-66A_n260A
DC_14A-66A-66A_n260G
DC_14A-66A-66A_n260H
DC_14A-66A-66A_n260I | DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | +| DC_19A-21A_n257A 2
DC_19A-21A_n257D 2
DC_19A-21A_n257G
DC_19A-21A_n257H
DC_19A-21A_n257I | DC_19A_n257A
DC_19A_n257D
DC_21A_n257A
DC_21A_n257D
DC_21A_n257G | +| DC_19A-42A_n257A 2
DC_19A-42A_n257D 2
DC_19A-42A_n257G 2
DC_19A-42A_n257H 2
DC_19A-42A_n257I 2
DC_19A-42C_n257A 2
DC_19A-42C_n257G 2
DC_19A-42C_n257H 2
DC_19A-42C_n257I 2 | DC_19A_n257A
DC_19A_n257D
DC_19A_n257G
DC_19A_n257H
DC_19A_n257I
DC_42A_n257A
DC_42A_n257D
DC_42A_n257G
DC_42A_n257H
DC_42A_n257I | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| DC_21A-42A_n257A 2
DC_21A-42A_n257D 2
DC_21A-42A_n257G
DC_21A-42A_n257H
DC_21A-42A_n257I
DC_21A-42C_n257A 2
DC_21A-42C_n257G
DC_21A-42C_n257H
DC_21A-42C_n257I | DC_21A_n257A
DC_21A_n257D
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I
DC_42A_n257A
DC_42A_n257D | +| DC_28A-42A_n257A 2 | DC_28A_n257A
DC_42A_n257A | +| DC_30A-66A_n260A
DC_30A-66A_n260G
DC_30A-66A_n260H
DC_30A-66A_n260I
DC_30A-66A_n260J
DC_30A-66A_n260K
DC_30A-66A_n260L
DC_30A-66A_n260M | DC_30A_n260A
DC_66A_n260A | +| DC_41A-42A_n257A | DC_41A_n257A
DC_42A_n257A | +| NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. | | +| NOTE 2: Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability for all of the above combinations. | | + +## 5.5B.5.3 Inter-band EN-DC configurations including FR2 (four bands) + +Table 5.5B.5.3-1: Inter-band EN-DC configurations including FR2 (four bands) + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| DC_1A-3A-18A_n257A
DC_1A-3A-18A_n257I | DC_1A_n257A
DC_1A_n257I
DC_3A_n257A
DC_3A_n257I
DC_18A_n257A
DC_18A_n257I | +| DC_1A-3A-19A_n257A 2
DC_1A-3A-19A_n257G
DC_1A-3A-19A_n257H
DC_1A-3A-19A_n257I | DC_1A_n257A
DC_3A_n257A
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_19A_n257A | +| DC_1A-3A-21A_n257A 2
DC_1A-3A-21A_n257G
DC_1A-3A-21A_n257H
DC_1A-3A-21A_n257I | DC_1A_n257A
DC_3A_n257A
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_21A_n257A | +| DC_1A-3A-41A_n257A
DC_1A-3A-41A_n257I | DC_1A_n257A
DC_1A_n257I
DC_3A_n257A
DC_3A_n257I
DC_41A_n257A
DC_41A_n257I | +| DC_1A-3A-42A_n257A
DC_1A-3A-42A_n257G
DC_1A-3A-42A_n257H
DC_1A-3A-42A_n257I
DC_1A-3A-42C_n257A
DC_1A-3A-42C_n257G
DC_1A-3A-42C_n257H
DC_1A-3A-42C_n257I
DC_1A-3A-42D_n257G
DC_1A-3A-42D_n257H
DC_1A-3A-42D_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_3A_n257A
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I | +| DC_1A-19A-21A_n257G
DC_1A-19A-21A_n257H
DC_1A-19A-21A_n257I | DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_1A-19A-42A_n257A
DC_1A-19A-42A_n257G
DC_1A-19A-42A_n257H
DC_1A-19A-42A_n257I
DC_1A-19A-42C_n257A
DC_1A-19A-42C_n257G
DC_1A-19A-42C_n257H
DC_1A-19A-42C_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_19A_n257A
DC_42A_n257A | +| DC_1A-21A-42A_n257A
DC_1A-21A-42A_n257G
DC_1A-21A-42A_n257H
DC_1A-21A-42A_n257I
DC_1A-21A-42C_n257A
DC_1A-21A-42C_n257G
DC_1A-21A-42C_n257H
DC_1A-21A-42C_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_21A_n257A
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I
DC_42A_n257A
DC_42A_n257D | +| DC_2A-14A-30A_n260A
DC_2A-14A-30A_n260G
DC_2A-14A-30A_n260H
DC_2A-14A-30A_n260I | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_30A_n260A
DC_30A_n260G
DC_30A_n260H
DC_30A_n260I | +| DC_2A-14A-66A_n260A
DC_2A-14A-66A_n260G
DC_2A-14A-66A_n260H
DC_2A-14A-66A_n260I | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | +| DC_2A-14A-66A-66A_n260A
DC_2A-14A-66A-66A_n260G
DC_2A-14A-66A-66A_n260H
DC_2A-14A-66A-66A_n260I | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | +| DC_3A-19A-21A_n257A 2 | DC_3A_n257A
DC_19A_n257A
DC_21A_n257A | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_3A-19A-42A_n257A
DC_3A-19A-42A_n257G
DC_3A-19A-42A_n257H
DC_3A-19A-42A_n257I
DC_3A-19A-42C_n257A
DC_3A-19A-42C_n257D
DC_3A-19A-42C_n257G
DC_3A-19A-42C_n257H
DC_3A-19A-42C_n257I | DC_3A_n257A
DC_3A_n257D
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_19A_n257A
DC_19A_n257D
DC_19A_n257G
DC_19A_n257H
DC_19A_n257I
DC_42A_n257A
DC_42A_n257D
DC_42A_n257G
DC_42A_n257H
DC_42A_n257I | +| DC_3A-21A-42A_n257A
DC_3A-21A-42A_n257G
DC_3A-21A-42A_n257H
DC_3A-21A-42A_n257I
DC_3A-21A-42C_n257A
DC_3A-21A-42C_n257D
DC_3A-21A-42C_n257G
DC_3A-21A-42C_n257H
DC_3A-21A-42C_n257I | DC_3A_n257A
DC_3A_n257D
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_21A_n257A
DC_21A_n257D
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I
DC_42A_n257A
DC_42A_n257D
DC_42A_n257G
DC_42A_n257H
DC_42A_n257I | +| DC_14A-30A-66A_n260A
DC_14A-30A-66A_n260G
DC_14A-30A-66A_n260H
DC_14A-30A-66A_n260I | DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_30A_n260A
DC_30A_n260G
DC_30A_n260H
DC_30A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | +| DC_14A-30A-66A-66A_n260A
DC_14A-30A-66A-66A_n260G
DC_14A-30A-66A-66A_n260H
DC_14A-30A-66A-66A_n260I | DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_30A_n260A
DC_30A_n260G
DC_30A_n260H
DC_30A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_19A-21A-42A_n257A 2
DC_19A-21A-42A_n257G 2
DC_19A-21A-42A_n257H 2
DC_19A-21A-42A_n257I 2
DC_19A-21A-42C_n257A 2
DC_19A-21A-42C_n257D 2
DC_19A-21A-42C_n257G 2
DC_19A-21A-42C_n257H 2
DC_19A-21A-42C_n257I 2 | DC_19A_n257A
DC_19A_n257D
DC_19A_n257G
DC_19A_n257H
DC_19A_n257I
DC_21A_n257A
DC_21A_n257D
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I
DC_42A_n257A
DC_42A_n257D
DC_42A_n257G
DC_42A_n257H
DC_42A_n257I | +| NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. | | +| NOTE 2: Applicable for UE supporting inter-band EN-DC with mandatory simultaneous Rx/Tx capability for all of the above combinations. | | + +## 5.5B.5.4 Inter-band EN-DC configurations including FR2 (five bands) + +Table 5.5B.5.4-1: Inter-band EN-DC configurations including FR2 (five bands) + +| EN-DC configuration | Uplink EN-DC configuration (NOTE 1) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_1A-3A-19A-42A_n257A
DC_1A-3A-19A-42A_n257G
DC_1A-3A-19A-42A_n257H
DC_1A-3A-19A-42A_n257I
DC_1A-3A-19A-42C_n257A
DC_1A-3A-19A-42C_n257G
DC_1A-3A-19A-42C_n257H
DC_1A-3A-19A-42C_n257I | DC_1A_n257A
DC_3A_n257A
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_19A_n257A
DC_42A_n257A | +| DC_1A-3A-21A-42A_n257A
DC_1A-3A-21A-42C_n257A
DC_1A-3A-21A-42C_n257G
DC_1A-3A-21A-42C_n257H
DC_1A-3A-21A-42C_n257I | DC_1A_n257A
DC_3A_n257A
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_3A_n257J
DC_21A_n257A
DC_42A_n257A | +| DC_1A-19A-21A-42A_n257A
DC_1A-19A-21A-42A_n257G
DC_1A-19A-21A-42A_n257H
DC_1A-19A-21A-42A_n257I
DC_1A-19A-21A-42C_n257A
DC_1A-19A-21A-42C_n257G
DC_1A-19A-21A-42C_n257H
DC_1A-19A-21A-42C_n257I | DC_1A_n257A
DC_1A_n257G
DC_1A_n257H
DC_1A_n257I
DC_19A_n257A
DC_21A_n257A
DC_21A_n257G
DC_21A_n257H
DC_21A_n257I
DC_42A_n257A | +| DC_2A-14A-30A-66A_n260A
DC_2A-14A-30A-66A_n260G
DC_2A-14A-30A-66A_n260H
DC_2A-14A-30A-66A_n260I | DC_2A_n260A
DC_2A_n260G
DC_2A_n260H
DC_2A_n260I
DC_14A_n260A
DC_14A_n260G
DC_14A_n260H
DC_14A_n260I
DC_30A_n260A
DC_30A_n260G
DC_30A_n260H
DC_30A_n260I
DC_66A_n260A
DC_66A_n260G
DC_66A_n260H
DC_66A_n260I | + +NOTE 1: Uplink EN-DC configurations are the configurations supported by the present release of specifications. + +## 5.5B.5.5 Void + +## 5.5B.6 Inter-band EN-DC including FR1 and FR2 + +Supported channel bandwidths for E-UTRA operating bands and CA configurations are defined in TS 36.521-1 [10] and for NR operating bands and CA configurations in TS 38.521-1 [8], TS 38.521-2 [9] and present document. + +5.5B.6.1 Void + +5.5B.6.2 Inter-band EN-DC configurations including FR1 and FR2 (three bands) + +**Table 5.5B.6.2-1: Inter-band EN-DC configurations including FR1 and FR2 (three bands)** + +*Editor's note: No Inter-band EN-DC configurations including FR1 and FR2 (three bands) specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode.* + +5.5B.6.3 Inter-band EN-DC configurations including FR1 and FR2 (four bands) + +**Table 5.5B.6.3-1: Inter-band EN-DC configurations including FR1 and FR2 (four bands)** + +*Editor's note: No Inter-band EN-DC configurations including FR1 and FR2 (four bands) specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode.* + +5.5B.6.4 Inter-band EN-DC configurations including FR1 and FR2 (five bands) + +**Table 5.5B.6.4-1: Inter-band EN-DC configurations including FR1 and FR2 (five bands)** + +Editor's note: No Inter-band EN-DC configurations including FR1 and FR2 (five bands) specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode. + +#### 5.5B.6.5 Inter-band EN-DC configurations including FR1 and FR2 (six bands) + +**Table 5.5B.6.5-1: Inter-band EN-DC configurations including FR1 and FR2 (six bands)** + +Editor's note: No Inter-band EN-DC configurations including FR1 and FR2 (six bands) specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode. + +#### 5.5B.7 Inter-band NR-DC between FR1 and FR2 + +Supported channel bandwidths for E-UTRA operating bands and CA configurations are defined in TS 36.521-1 [10] and for NR operating bands and CA configurations in TS 38.521-1 [8], TS 38.521-2 [9] and present document. + +#### 5.5B.7.0 General + +The configurations and bandwidth combination sets for the FR1-FR2 NR-DC combinations in the following sub-section are defined in the tables for FR1-FR2 carrier aggregation in section 5.5A.1. + +#### 5.5B.7.1 Inter-band NR-DC configurations between FR1 and FR2 (two bands) + +**Table 5.5B.7-1: Inter-band NR-DC configurations between FR1 and FR2 (two bands)** + +Editor's note: No Inter-band NR-DC configurations between FR1 and FR2 (two bands) specified due to the testability issues that combined testing of NR FR1 in conducted mode and NR FR2 in radiated mode. + +## 5.5E Configuration for V2X operation + +#### 5.5E.1 General + +The operating bands and bandwidth classes are specified for V2X operation. + +#### 5.5E.2 Intra-band contiguous V2X operation in FR1 + +**Table 5.5E.2-1: Intra-band contiguous V2X configurations** + +| V2X configuration | SL transmission | +|-----------------------------------------------|-------------------------------| +| V2X_(n)47AA | E-UTRA Band 47 or NR band n47 | +| NOTE 1: Only single switched SL is supported. | | + +#### 5.5E.3 Intra-band non-contiguous V2X operation in FR1 + +**Table 5.5E.3-1: Intra-band non-contiguous V2X configurations** + +| V2X configuration | SL transmission | +|-----------------------------------------------|-------------------------------| +| V2X_47A_n47A | E-UTRA Band 47 or NR band n47 | +| NOTE 1: Only single switched SL is supported. | | + +#### 5.5E.4 Inter-band V2X operation in FR1 + +##### 5.5E.4.1 Inter-band V2X configurations within FR1 (two bands) + +**Table 5.5E.4.1-1: Inter-band V2X configurations** + +| V2X configuration | V2X transmission configuration | +|--------------------------------------------------------------------------------------------------------------------|--------------------------------| +| V2X_20A_n38A | V2X_20A_n38A | +| V2X_n71A_47A | V2X_n71A_47A | +| NOTE 1: V2X transmission configurations are the configurations supported by the present release of specifications. | | + +# --- 6 Transmitter characteristics + +## 6.1 General + +**Editor's note: Test configurations/environments that require new spherical scan shall be included in test procedure clause and identifying such scenarios is currently FFS and owned by RAN5.** + +Unless otherwise stated the transmitter, characteristics are specified at the antenna connector(s) of the UE for the bands operating on frequency range 1 and over the air of the UE for the bands operating on frequency range 2. The requirements for frequency range 1 and frequency range 2 can be verified separately. For the carrier in frequency range 1, requirements can be verified with NR FR2 link disabled. For the carrier in frequency range 2, requirements can be verified in OTA mode with E-UTRA connecting to the network by OTA without calibration. + +For NR FR2 Tx test cases the identified beam peak direction can be stored and reused for a device under test in various configurations/environments for the full duration of device testing as long as beam peak direction is the same. + +Unless otherwise stated, requirements for NR transmitter written in TS 38.521-1 [8] and TS 38.521-2 [9] apply and are assumed anchor agnostic. Requirements are verified under conditions where anchor resources do not interfere NR operation. For Rel-15, unless otherwise stated, if UE indicates IE maxNumberSRS-Ports-PerResource = n2 in NR standalone operation mode, the said UE shall meet the NR requirements for either power class 2 or power class 3 in EN-DC within FR1 if UE indicates IE maxNumberSRS-Ports-PerResource = n1 for EN-DC on this NR band. For Rel-16 and forward, if UE indicates IE powerClassNRPart-r16 as defined in TS 38.331 [18] in EN-DC, UE shall meet NR requirements according to this power class. + +Unless otherwise stated, Channel Bandwidth shall be prioritized in the selecting of test points. Subcarrier spacing shall be selected after Test Channel Bandwidth is selected. + +For conformance testing involving FR2 test cases in this specification, the UE under test shall be pre-configured with UL Tx diversity schemes disabled to account for single polarization System Simulator (SS) in the test environment. The UE under test may transmit with dual polarization. + +Uplink RB allocations for NR FR1 carrier given in TS 38.521-1 [8] Table 6.1-1 are used throughout this clause, unless otherwise stated by the test case. + +Uplink RB allocations for NR FR2 carrier given in TS 38.521-2 [9] Table 6.1-1 are used throughout this clause, unless otherwise stated by the test case. + +Uplink RB allocations for E-UTRA carrier and E-UTRA intra-band contiguous CA (2CC) given in Table 6.1-1 and Table 6.1-2 respectively are used throughout this clause, unless otherwise stated by the test case. + +**Table 6.1-1: Common uplink configuration for E-UTRA carrier** + +| Channel Bandwidth | RB allocation | | | | +|-------------------|-----------------|--------------------|----------|-----------| +| | Full_Allocation | Partial_Allocation | 1RB_Left | 1RB_Right | +| 1.4MHz | 6@0 | 5@0 | 1@0 | 1@5 | +| 3MHz | 15@0 | 4@0 | 1@0 | 1@14 | +| 5MHz | 25@0 | 8@0 | 1@0 | 1@24 | +| 10MHz | 50@0 | 12@0 | 1@0 | 1@49 | +| 15MHz | 75@0 | 16@0 | 1@0 | 1@74 | +| 20MHz | 100@0 | 18@0 | 1@0 | 1@99 | + +NOTE: Partial\_Allocation corresponds to the test points with 0dB MPRsingle,E-UTRA for QPSK modulation type included in TS 36.521-1 Table 6.2.2.4.1-1. + +**Table 6.1-2 Common uplink RB allocation for E-UTRA intra-band contiguous CA (2CC)** + +| Smallest Component Carrier Transmission Bandwidth | PCC & SCC RB allocation | | | | | | +|---------------------------------------------------|-------------------------|-------|----------|-------|-----------|-------| +| | Partial_Allocation | | 1RB_Left | | 1RB_Right | | +| | PCC | SCC | PCC | SCC | PCC | SCC | +| 5MHz | P 8@0 | S 0@0 | P 1@0 | S 0@0 | P 1@RBmax | S 0@0 | +| 10MHz | P 12@0 | S 0@0 | P 1@0 | S 0@0 | P 1@RBmax | S 0@0 | +| 15MHz | P 16@0 | S 0@0 | P 1@0 | S 0@0 | P 1@RBmax | S 0@0 | +| 20MHz | P 18@0 | S 0@0 | P 1@0 | S 0@0 | P 1@RBmax | S 0@0 | + +NOTE: Partial\_Allocation corresponds to the test points with 0dB MPRE-UTRA, CA for QPSK modulation type included in TS 36.521-1 Table 6.2.2.4.1-1. + +## 6.2 Transmitter power + +### 6.2A Transmitter power for CA without EN-DC + +#### 6.2A.1 UE maximum output power for CA + +##### 6.2A.1.1 UE maximum output power for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.2A.1.1.1 Test purpose + +Same test purpose as in clause 6.2.1 in TS 38.521-1 [8] for NR/5GC FR1 carrier(s) and clause 6.2.1 in TS 38.521-2 [9] for NR/5GC FR2 carrier(s). + +##### 6.2A.1.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR/5GC FR1 conducted mode with NR/5GC FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for maximum output power apply and are tested in TS 38.521-1 [8] clauses 6.2 and 6.2A and TS 38.521-2 [9] clauses 6.2 and 6.2A. + +#### 6.2A.2 UE maximum output power reduction for CA + +##### 6.2A.2.1 UE maximum output power reduction for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.2A.2.1.1 Test purpose + +Same test purpose as in clause 6.2.2 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.2.2 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.2A.2.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The SA requirements for additional spectrum emissions mask apply and are tested in TS 38.521-1 [8] clauses 6.2 and 6.2A and TS 38.521-2 [9] clauses 6.2 and 6.2A. + +#### 6.2A.3 UE additional maximum output power reduction for CA + +##### 6.2A.3.1 UE additional maximum output power reduction for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.2A.3.1.1 Test purpose + +Same test purpose as in clause 6.2.3.1 in TS 38.521-1 [8] for NR FR1 carrier and clause 6.2.3.1 in TS 38.521-2 [9] for NR FR2 carrier. + +###### 6.2A.3.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The single carrier requirements for Additional Maximum Output Power apply and are tested as part of clause 6.2.3 in TS 38.521-1 [8] for NR FR1 carrier and clause 6.2.3 in TS 38.521-2 [9] for NR FR2 carrier. + +#### 6.2A.4 Configured output power level for CA + +##### 6.2A.4.1 Configured output power level for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.2A.4.1.1 Test purpose + +Same test purpose as in clause 6.2.4 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.2.4 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.2A.4.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for configured output power level apply and are tested in TS 38.521-1 [8] clauses 6.2 and 6.2A and TS 38.521-2 [9] clauses 6.2 and 6.2A. + +#### 6.2A.4.2 $\Delta T_{IB,c}$ for CA + +##### 6.2A.4.2.1 $\Delta T_{IB,c}$ for inter-band CA between FR 1 and FR 2 + +For the UE which supports inter-band NR CA configuration, $\Delta T_{IB,c}$ in Table 6.2A.4.2.1-1 applies. Unless otherwise stated, $\Delta T_{IB,c}$ is set to zero. + +**Table 6.2A.4.2.1-1: Void** + +### 6.2B Transmitter power for DC + +#### 6.2B.1 UE Maximum Output Power for DC + +##### 6.2B.1.1 UE Maximum Output Power for Intra-Band Contiguous EN-DC + +**Editor's note:** + +- For overlapping transmission there is no test point satisfying 0dB MPR according to RAN4 specification. + +##### 6.2B.1.1.1 Test purpose + +To verify that the error of the UE maximum output power does not exceed the range prescribed by the specified nominal maximum output power and tolerance. + +An excess maximum output power has the possibility to interfere to other channels or other systems. A small maximum output power decreases the coverage area. + +##### 6.2B.1.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC operation on FR1. + +##### 6.2B.1.1.3 Minimum conformance requirements + +The following UE Power Classes define the total maximum output power for any transmission bandwidth(s) of the CG(s) configured. + +The maximum output power is measured as the total maximum output power across the UE antenna connector(s). The period of measurement shall be at least one sub frame. + +**Table 6.2B.1.1.3-1: Maximum output power for EN-DC (continuous sub-blocks)** + +| DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|------------------|---------------------|--------------------|---------------------|--------------------| +| DC_(n)71AA | | | 23 | +2/-3 | +| DC_(n)41AA | 26 | +2/-3 1 | 23 | +2/-3 1 | + +NOTE 1: An uplink EN-DC configuration in which the band has NOTE 3 in Table 6.2.1-1 in TS 38.101-1 or NOTE 2 in Table 6.2.2-1 in TS 36.101 is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ . + +NOTE 2: Power Class 3 is the default power class unless otherwise stated. + +If UE supports a different power class than the default UE power class for EN-DC band combination, and the supported power class enables higher maximum output power than that of the default power class: + +- if the E-UTRA UL/DL configuration is 0 or 6; or +- if the E-UTRA UL/DL configuration is 1 and special subframe configuration is 0 or 5; or + +- if the IE *p-maxUE-FR1-r15* as defined in TS 36.331 [17] is provided and set to the maximum output power of the default power class or lower; +- apply all requirements for the default power class, and set the configured transmitted power as specified in clause 6.2B.4; +- else + - apply all requirements for the supported power class, and set the configured transmitted power class as specified in subclause 6.2B.4; + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1. + +LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 6.2B.1.1.4 Test description + +###### 6.2B.1.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2, and are shown in table 6.2B.1.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C, clause C.2 and in TS 38.521-1 [8] Annex C, clause C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.1.1.4.1-1: Test configuration table for Intra-Band Contiguous EN-DC** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------|------------------------|--------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| NR Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508-1 [11] clause 4.3.1 | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | Highest N RB_agg | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest (NOTE 3) | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | +| 1 | N/A | QPSK | Partial_Allocation | N/A | N/A | +| 2 | N/A | QPSK | 1RB Left | N/A | N/A | +| 3 | N/A | N/A | N/A | DFT-s-OFDM
QPSK | Inner Full | +| 4 | N/A | N/A | N/A | DFT-s-OFDM
QPSK | Inner_1RB_LEFT | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. +NOTE 3: For DC\_(n)71AA, only NR SCS of 15 kHz is tested. + +**Table 6.2B.1.1.4.1-2: Void** + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] clause A.3.1.1 for SS diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C, clause C.0 and TS 38.521-1 [8] Annex C, clause C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B, clause B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### **6.2B.1.1.4.2 Test procedure** + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.2B.1.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send, the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level. +3. For a UE supporting dynamic power sharing, measure the mean power over all component carriers. For a UE not supporting dynamic power sharing, measure the power of each component carrier individually. For the tested EN-DC configuration, the requirements described in clause 6.2B.2.1.5 shall be met. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). For TDD slots with transient periods are not under test. +4. For UEs supporting Power Class 2, repeat steps 1~3 on the applicable bands with message exception defined in Table 6.2B.1.1.4.3-5. + +###### **6.2B.1.1.4.3 Message contents** + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.2B.1.1.4.3-0: PUSCH-Config** + +| | +|---------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|---------------------------------------------------------------------------------------------| + +**Table 6.2B.1.1.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE | +| | 26 | | Power Class 2 UE | + +**Table 6.2B.1.1.4.3-2: *RRConnectionReconfiguration: nr-Config-r15*** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 3 UE | +| | 26 | | Power Class 2 UE | + +**Table 6.2B.1.1.4.3-3: *RRConnectionReconfiguration: tdm-PatternConfig* if operating on FDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|-----------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 ::= CHOICE{
setup ::= SEQUENCE { | | | Test IDs 7-15 | +| | | Apply if operating on FDD band for a UE NOT indicating support of dynamicPowerSharing in the UE-MRDC-Capability IE according to TS 38.213 [x] clause 7.6.1 | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.1.1.4.3-4: *SystemInformationBlockType1: tdd-Config* if operating on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.1.1.4.3-5: *RRConnectionReconfiguration: p-MaxUE-FR1-r15* (step 4 in 6.2B.1.1.4.2)** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 2 UE | +| } | | | | + +##### 6.2B.1.1.5 Test requirements + +The maximum output power for the DC configuration, derived in step 3 shall be within the range prescribed by the DC UE Power Class and tolerance in Table 6.2B.1.1.5-1 for power class 3 UE and Table 6.2B.1.1.5-2 for power class 2 UE. The corresponding requirements is specified in Table 6.2.2.5-1, 6.2.2\_1.5-1 in TS 36.521-1 [10] or Table 6.2.1.5-1, 6.2.1.5-2 in TS 38.521-1 [8]. + +The maximum output power for the DC configuration, derived in step 4 shall be within the range prescribed in Table 6.2B.1.1.5-1. + +**Table 6.2B.1.1.5-1: Maximum output power for EN-DC (continuous sub-blocks) for power class 3** + +| DC configuration | Power class2 | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|------------------|--------------|----------------|---------------------|---------------------------| +| DC_(n)71AA | | | 23 | +2+TT/-3-TT | +| DC_(n)41AA | | | 23 | +2+TT/-3 1 +TT | + +NOTE 1: It is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high - 4 MHz and FUL\_high. +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.1.1.5-3. + +**Table 6.2B.1.1.5-2: Maximum output power for EN-DC (continuous sub-blocks) for Power Class 2 for Rel-15** + +| DC configuration | Carrier | Power class2 | Tolerance (dB) | Condition | Comment | +|------------------|----------------|--------------|---------------------------|---------------------------------|-------------------------------------| +| DC_(n)41AA | NR carrier | 26 | +2+TT/-3 1 -TT | UE indicates PC2 on NR band | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3 1 -TT | UE indicates PC3 on NR band | UE meets power class 3 requirements | +| | E-UTRA carrier | 26 | +2+TT/-3 1 -TT | UE indicates PC2 ON E-UTRA band | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3 1 -TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +NOTE 1: It is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high - 4 MHz and FUL\_high. +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.1.1.5-3. + +**Table 6.2B.1.1.5-2a: Maximum output power for EN-DC (continuous sub-blocks) for Power Class 2 for Rel-16 and forward** + +| DC configuration | Carrier | Power class2 | Tolerance (dB) | Condition | Comment | +|------------------|----------------|--------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_(n)41AA | NR carrier | 26 | +2+TT/-3 1 -TT | UE reporting (PC2 by P PowerClass,NR , and PC2 or Not present by powerClassNRPart-r16) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3 1 -TT | UE reporting (PC2 by P PowerClass,NR , and PC3 by powerClassNRPart-r16) or UE reporting (PC3 by P PowerClass,NR ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 26 | +2+TT/-3 1 -TT | UE indicates PC2 ON E-UTRA band | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3 1 -TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +NOTE 1: It is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high - 4 MHz and FUL\_high. +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.1.1.5-3. + +**Table 6.2B.1.1.5-3: Test Tolerance (Maximum Output Power for Intra-Band Contiguous EN-DC)** + +| | f ≤ 3.0GHz | 3.0GHz < f ≤ 6GHz | +|-----------------------|------------|-------------------| +| ENBW ≤ 40MHz | 0.7 dB | 1.0 dB | +| 40MHz < ENBW ≤ 100MHz | 1.0 dB | 1.0 dB | + +#### 6.2B.1.2 UE Maximum Output Power for Intra-Band Non-Contiguous EN-DC + +Editor's note: + +- For overlapping transmission there is no test point satisfying 0dB MPR according to RAN4 specification. + +##### 6.2B.1.2.1 Test purpose + +To verify that the error of the UE maximum output power does not exceed the range prescribed by the specified nominal maximum output power and tolerance. + +An excess maximum output power has the possibility to interfere to other channels or other systems. A small maximum output power decreases the coverage area. + +##### 6.2B.1.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC operation on FR1. + +##### 6.2B.1.2.3 Minimum conformance requirements + +The following UE Power Classes define the total maximum output power for any transmission bandwidth(s) of the CG(s) configured. + +The maximum output power is measured as the total maximum output power across the UE antenna connector(s). The period of measurement shall be at least one sub frame. + +**Table 6.2B.1.2.3-1: Maximum output power for EN-DC (non-continuous sub-blocks)** + +| DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|--------------------------|---------------------|--------------------|---------------------|--------------------| +| DC_2A_n2A 4 | | | 23 | +2/-3 | +| DC_41A_n41A | 26 | +2/-3 1 | 23 | +2/-3 1 | +| DC_66A_n66A 4 | | | 23 | +2/-3 | + +NOTE 1: An uplink EN-DC configuration in which the band has NOTE 3 in Table 6.2.1-1 in TS 38.101-1 or NOTE 2 in Table 6.2.2-1 in TS 36.101 is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high - 4 MHz and FUL\_high. + +NOTE 2: Only single switched UL is supported in Rel-15. + +NOTE 3: Power Class 3 is the default power class unless otherwise stated. + +NOTE 4: Only single switched UL is supported. + +If UE supports a different power class than the default UE power class for EN-DC band combination, and the supported power class enables higher maximum output power than that of the default power class: + +- if the E-UTRA UL/DL configuration is 0 or 6; or +- if the E-UTRA UL/DL configuration is 1 and special subframe configuration is 0 or 5; or +- if the IE *p-maxUE-FR1-r15* as defined in TS 36.331 [17] is provided and set to the maximum output power of the default power class or lower: + - apply all requirements for the default power class, and set the configured transmitted power as specified in subclause 6.2B.4; +- else + - apply all requirements for the supported power class, and set the configured transmitted power class as specified in subclause 6.2B.4. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1. + +LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 6.2B.1.2.4 Test description + +###### 6.2B.1.2.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in Table 5.3B.1.3-1, channel bandwidths and sub-carrier spacings for the NR cell are specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in Table 5.3B.1.3-1, and are shown in table 6.2B.1.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexe A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C, clause C.2 and in TS 38.521-1 [8] Annex C, clause C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.1.2.4.1-1: Test configuration table for intra-band non-contiguous EN-DC** + +| | | Initial Conditions | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------------|------------------------|--------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| NR Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508-1 [11] clause 4.3.1 | | Minimum Wgap, Maximum Wgap | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | | Highest N RB_agg | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | | Highest | | | | +| NR/E-UTRA Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | +| 1 | N/A | QPSK | Partial_Allocation | N/A | N/A | +| 2 | N/A | QPSK | 1RB Left | N/A | N/A | +| 3 | N/A | N/A | N/A | DFT-s-OFDM
QPSK | Inner Full | +| 4 | N/A | N/A | N/A | DFT-s-OFDM
QPSK | Inner_1RB_LEFT | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] A.3.1.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.2.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### **6.2B.1.2.4.2 Test procedure** + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.2B.1.2.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level for Power class 3. +3. Measure the mean transmitted power over all EN-DC component carriers in the EN-DC, which shall meet the requirements described in table 6.2B.1.2.5-1 and the period of the measurement shall be at least the continuous duration of one active sub-frame. +4. For UEs supporting Power Class 2, repeat steps 1~3 on the applicable bands with message exception defined in Table 6.2B.1.1.4.3-5. + +###### **6.2B.1.2.4.3 Message contents** + +Same message contents as specified in 6.2B.1.1.4.3. + +##### **6.2B.1.2.5 Test requirements** + +The maximum output power for the DC configuration, derived in step 3 shall be within the range prescribed by the DC UE Power Class and tolerance in Table 6.2B.1.2.5-1 for power class 3 UE and Table 6.2B.1.2.5-2 for power class 2 UE. The corresponding requirements is specified in table 6.2.2.5-1, 6.2.2\_1.5-1 in TS 36.521-1 [10] or table 6.2.1.5-1, 6.2.1.5-2 in TS 38.521-1 [8]. + +The maximum output power for the DC configuration, derived in step 4 shall be within the range prescribed in Table 6.2B.1.2.5-1. + +**Table 6.2B.1.2.5-1: Maximum output power for EN-DC (non-continuous sub-blocks) for power class 3** + +| DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|--------------------------|---------------------|----------------|---------------------|---------------------------| +| DC_2A_n2A 4 | | | 23 | +2+TT/-3-TT | +| DC_41A_n41A | | | 23 | +2+TT/-3 1 -TT | +| DC_66A_n66A 4 | | | 23 | +2+TT/-3-TT | + +NOTE 1: It is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ . +NOTE 2: Only single switched UL is supported in Rel-15. +NOTE 3: TT for each frequency and channel bandwidth is specified in Table 6.2B.1.2.5-3 +NOTE 4: Only single switched UL is supported. + +**Table 6.2B.1.2.5-2: Maximum output power for EN-DC (non-continuous sub-blocks) for power class 2 for Rel-15** + +| DC configuration | Carrier | Power class2 | Tolerance (dB) | Condition | Comment | +|------------------|----------------|--------------|---------------------------|-------------------------------------------------------------|-------------------------------------| +| DC_41A_n41A | NR carrier | 26 | +2+TT/-3 1 -TT | UE indicates PC2 on NR band | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2 1 -TT | UE indicates PC3 on NR band | UE meets power class 3 requirements | +| | E-UTRA carrier | 26 | +2+TT/-3 1 -TT | UE indicates PC3 on E-UTRA carrier of this DC_Configuration | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2 1 -TT | UE indicates PC3 on E-UTRA carrier of this DC_Configuration | UE meets power class 3 requirements | + +NOTE 1: It is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high - 4 MHz and FUL\_high. +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.1.1.5-3 + +**Table 6.2B.1.2.5-2a: Maximum output power for EN-DC (non-continuous sub-blocks) for power class 2 for Rel-16 and forward** + +| DC configuration | Carrier | Power class2 | Tolerance (dB) | Condition | Comment | +|------------------|----------------|--------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_41A_n41A | NR carrier | 26 | +2+TT/-3 1 -TT | UE reporting (PC2 by P PowerClass,NR , and PC2 or Not present by powerClassNRPart-r16) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2 1 -TT | UE reporting (PC2 by P PowerClass,NR , and PC3 by powerClassNRPart-r16) or UE reporting (PC3 by P PowerClass,NR ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 26 | +2+TT/-2 1 -TT | UE indicates PC2 ON E-UTRA carrier of this DC_Configuration | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2 1 -TT | UE indicates PC3 on E-UTRA carrier of this DC_Configuration | UE meets power class 3 requirements | + +NOTE 1: It is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands are confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high - 4 MHz and FUL\_high. +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.1.2.5-3 + +**Table 6.2B.1.2.5-3: Test Tolerance** + +| Uplink TX | | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6GHz | +|-----------|---------------------|------------|---------------------|-------------------| +| E-UTRA | BW ≤ 20MHz | 0.7 dB | 1.0 dB | N/A | +| NR | BW ≤ 40MHz | 0.7 dB | 1.0 dB | 1.0 dB | +| | 40MHz < BW ≤ 100MHz | 1.0 dB | 1.0 dB | 1.0 dB | + +#### 6.2B.1.3 UE Maximum Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) + +##### 6.2B.1.3.1 Test purpose + +To verify that the error of the UE maximum output power does not exceed the range prescribed by the specified nominal maximum output power and tolerance. + +An excess maximum output power has the possibility to interfere to other channels or other systems. A small maximum output power decreases the coverage area. + +##### 6.2B.1.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC with 1 E-UTRA CC and 1 NR CC operating on FR1. + +##### 6.2B.1.3.3 Minimum conformance requirements + +For inter-band EN-DC of E-UTRA and NR in FR1, the following UE Power Classes define the maximum output power for any transmission bandwidth within the aggregated channel bandwidth. The maximum output power is measured as the sum of the maximum output power at each UE antenna connector. The period of measurement shall be at least one sub frame (1ms). UE maximum output power shall be measured over all component carriers from different bands. If each band has separate antenna connectors, maximum output power is measured as the sum of maximum output power at each UE antenna connector. + +**Table 6.2B.1.3.3-1: Maximum output power for inter-band EN-DC (two bands)** + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------------|---------------------|----------------|---------------------|----------------| +| DC_1A_n3A | | | 23 | +2/-3 | +| DC_1A_n5A | | | 23 | +2/-3 | +| DC_1A_n7A | | | 23 | +2/-3 | +| DC_1A_n8A | | | 23 | +2/-3 | +| DC_1A_n28A | | | 23 | +2/-3 | +| DC_1A_n41A | | | 23 | +2/-3 | +| DC_1A_n77A | | | 23 | +2/-3 | +| DC_1A_n78A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_1A_n79A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_2A_n5A | | | 23 | +2/-3 | +| DC_2A_n41A | | | 23 | +2/-3 | +| DC_2A_n66A | | | 23 | +2/-3 | +| DC_2A_n71A | | | 23 | +2/-3 | +| DC_2A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_2A_n78A | | | 23 | +2/-3 | +| DC_3A_n1A | | | 23 | +2/-3 | +| DC_3A_n5A | | | 23 | +2/-3 | +| DC_3A_n7A | | | 23 | +2/-3 | +| DC_3A_n8A | | | 23 | +2/-3 | +| DC_3A_n28A | | | 23 | +2/-3 | +| DC_3A_n41A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_3A_n77A | | | 23 | +2/-3 | +| DC_3A_n78A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_3A_n79A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_5A_n2A | | | 23 | +2/-3 | +| DC_5A_n40A | | | 23 | +2/-3 | +| DC_5A_n66A | | | 23 | +2/-3 | +| DC_5A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_5A_n78A | | | 23 | +2/-3 | +| DC_7A_n1A | | | 23 | +2/-3 | +| DC_7A_n3A | | | 23 | +2/-3 | +| DC_7A_n5A | | | 23 | +2/-3 | +| DC_7A_n8A | | | 23 | +2/-3 | +| DC_7A_n28A | | | 23 | +2/-3 | +| DC_7A_n66A | | | 23 | +2/-3 | +| DC_7A_n78A | | | 23 | +2/-3 | +| DC_8A_n1A | | | 23 | +2/-3 | +| DC_8A_n3A | | | 23 | +2/-3 | +| DC_8A_n20A | | | 23 | +2/-3 | +| DC_8A_n28A | | | 23 | +2/-3 | +| DC_8A_n41A | | | 23 | +2/-3 | +| DC_8A_n77A | | | 23 | +2/-3 | +| DC_8A_n78A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_8A_n81A_ULSUP-TDM_n78A | | | 23 | +2/-3 | +| DC_11A_n77A | | | 23 | +2/-3 | + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------|---------------------|----------------|---------------------|----------------| +| DC_11A_n78A | | | 23 | +2/-3 | +| DC_11A_n79A | | | 23 | +2/-3 | +| DC_12A_n2A | | | 23 | +2/-3 | +| DC_12A_n5A | | | 23 | +2/-3 | +| DC_12A_n66A | | | 23 | +2/-3 | +| DC_12A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_12A_n78A | | | 23 | +2/-3 | +| DC_13A_n2A | | | 23 | +2/-3 | +| DC_13A_n66A | | | 23 | +2/-3 | +| DC_13A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_14A_n2A | | | 23 | +2/-3 | +| DC_14A_n66A | | | 23 | +2/-3 | +| DC_14A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_18A_n77A | | | 23 | +2/-3 | +| DC_18A_n78A | | | 23 | +2/-3 | +| DC_19A_n1A | | | 23 | +2/-3 | +| DC_18A_n79A | | | 23 | +2/-3 | +| DC_19A_n77A | | | 23 | +2/-3 | +| DC_19A_n78A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_19A_n79A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_20A_n1A | | | 23 | +2/-3 | +| DC_20A_n3A | | | 23 | +2/-3 | +| DC_20A_n7A | | | 23 | +2/-3 | +| DC_20A_n8A | | | 23 | +2/-3 | +| DC_20A_n28A | | | 23 | +2/-3 | +| DC_20A_n78A | | | 23 | +2/-3 | +| DC_21A_n1A | | | 23 | +2/-3 | +| DC_21A_n28A | | | 23 | +2/-3 | +| DC_21A_n77A | | | 23 | +2/-3 | +| DC_21A_n78A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_21A_n79A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_25A_n41A | | | 23 | +2/-3 | +| DC_26A_n41A | | | 23 | +2/-3 | +| DC_26A_n77A | | | 23 | +2/-3 | +| DC_26A_n78A | | | 23 | +2/-3 | +| DC_26A_n79A | | | 23 | +2/-3 | +| DC_28A_n3A | | | 23 | +2/-3 | +| DC_28A_n5A | | | 23 | +2/-3 | +| DC_28A_n7A | | | 23 | +2/-3 | +| DC_28A_n77A | | | 23 | +2/-3 | +| DC_28A_n78A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_28A_n79A | | | 23 | +2/-3 | +| DC_30A_n2A | | | 23 | +2/-3 | +| DC_30A_n5A | | | 23 | +2/-3 | +| DC_30A_n66A | | | 23 | +2/-3 | +| DC_30A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------|---------------------|----------------|---------------------|----------------| +| DC_38A_n78A | | | N/A | N/A | +| DC_39A_n41A | 26 5 | +2/-3 | 23 | +2/-2 | +| DC_39A_n79A | 26 5 | +2/-3 | 23 | +2/-3 | +| DC_40A_n1A | | | 23 | +2/-3 | +| DC_40A_n41A | | | 23 | +2/-3 | +| DC_40A_n78A | | | 23 | +2/-3 | +| DC_40A_n79A | | | 23 | +2/-3 | +| DC_41A_n28A | | | 23 | +2/-3 | +| DC_41A_n77A | | | 23 | +2/-3 | +| DC_41A_n78A | | | 23 | +2/-3 | +| DC_41A_n79A | 26 5 | +2/-3 | 23 | +2/-3 | +| DC_42A_n77A | | | N/A | N/A | +| DC_42A_n78A | | | N/A | N/A | +| DC_42A_n79A | | | N/A | N/A | +| DC_48A_n5A | | | 23 | +2/-3 | +| DC_48A_n66A | | | 23 | +2/-3 | +| DC_48A_n66A | | | 23 | +2/-3 | +| DC_66A_n2A | | | 23 | +2/-3 | +| DC_66A_n5A | | | 23 | +2/-3 | +| DC_66A_n41A | | | 23 | +2/-3 | +| DC_66A_n71A | | | 23 | +2/-3 | +| DC_66A_n77A | 26 6 | +2/-3 | 23 | +2/-3 | +| DC_66A_n78A | | | 23 | +2/-3 | +| DC_71A_n2A | | | 23 | +2/-3 | +| DC_71A_n66A | | | 23 | +2/-3 | + +NOTE 1: An uplink DC configuration in which at least one of the bands has NOTE 3 in Table 6.2.1-1 in TS 38.101-1 or NOTE 2 in Table 6.2.2-1 in TS 36.101 is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands is confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high – 4 MHz and FUL\_high. + +NOTE 2: PPowerClass, EN-DC is the maximum UE power specified without taking into account the tolerance. + +NOTE 3: For inter-band EN-DC the maximum power requirement should apply to the total transmitted power over all component carriers (per UE). + +NOTE 4: Power Class 3 is the default power class unless otherwise stated. + +NOTE 5: The UE is not required to support PC2 within each individual cell group. Power class support within each individual cell group is signaled separately by the UE. + +NOTE 6: The UE supports PC3 within E-UTRA cell group, and supports either PC3 or PC2 within NR cell group. Power class support within each individual cell group is signaled separately by the UE. + +NOTE 7: Only single switched UL is supported. + +NOTE 8: The UE that supports a PC2 uplink EN-DC configuration with single carrier for each individual band and a composite of supporting PC3 within a TDD or FDD band and PC2 within a second TDD band may signal a *higherPowerLimit-r17* capability whereby the maximum output power indicated in the table may be exceeded in accordance with sub-clause 6.2B.4.1.3. + +If a UE supports a different power class than the default UE power class for an EN-DC band combination and NR TDD inter-band EN-DC combination and the supported power class enables higher maximum output power than that of the default power class: + +- if the field of UE capability *maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16* is absent and the percentage of NR uplink symbols transmitted in a certain evaluation period is larger than 30% (The exact evaluation period is no less than one radio frame); or +- if the field of UE capability *maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16* is not absent and the percentage of NR uplink symbols transmitted in a certain evaluation period is larger than *maxUplinkDutyCycle-* + +*interBandENDC-TDD-PC2-r16* as defined in TS 38.331 (The exact evaluation period is no less than one radio frame); or + +- if the IE *p-maxUE-FR1* as defined in TS 38.331 is provided and set to the maximum output power of the default power class or lower; + - shall apply all requirements for the default power class to the supported power class and set the configured transmitted power as specified clause 6.2B.4; +- Else if the IE *p-maxUE-FR1* as defined in TS 38.331 is not provided or set to the higher value than the maximum output power of the default power class and the percentage of uplink symbols transmitted in a certain evaluation period is less than or equal to *maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16* as defined in TS 38.331; or +- if the IE *p-maxUE-FR1* as defined in TS 38.331 is not provided or set to the higher value than the maximum output power of the default power class and the percentage of NR uplink symbols transmitted in a certain evaluation period is less than or equal to 30% when *maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16* is absent. (The exact evaluation period is no less than one radio frame): +- shall apply all requirements for the supported power class and set the configured transmitted power class as specified in clause 6.2B.4. + +If a UE supports a different power class than the default UE power class for an E-UTRA FDD and NR TDD EN-DC band combination and the supported power class enables higher maximum output power than that of the default power class: + +If UE indicating the two capabilities *maxUplinkDutyCycle-FDD-TDD-EN-DC1* and *maxUplinkDutyCycle-FDD-TDD-EN-DC2*: + +- if the IE *p-maxUE-FR1* as defined in TS 38.331 is not provided or set to the higher value than the maximum output power of the default power class, and the percentage of E-UTRA uplink symbols transmitted in a certain evaluation period is between 40% and 70%, and the percentage of NR uplink symbols transmitted in a certain evaluation period is less than or equal to *maxUplinkDutyCycle-FDD-TDD-EN-DC1* as defined in TS 38.331 (The exact evaluation period is no less than one radio frame); or +- if the IE *p-maxUE-FR1* as defined in TS 38.331 is not provided or set to the higher value than the maximum output power of the default power class, and the percentage of E-UTRA uplink symbols transmitted in a certain evaluation period is no larger than 40%, and the percentage of NR uplink symbols transmitted in a certain evaluation period is less than or equal to *maxUplinkDutyCycle-FDD-TDD-EN-DC2* as defined in TS 38.331 (The exact evaluation period is no less than one radio frame) + - shall apply all requirements for the supported power class and set the configured transmitted power class as specified in sub-clause 6.2B.4. +- else + - shall apply all requirements for the default power class and set the configured transmitted power as specified sub-clause 6.2B.4; +- shall apply all requirements for the supported power class and set the configured transmitted power as specified sub-clause 6.2B.4; + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1. + +LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 6.2B.1.3.4 Test description + +###### 6.2B.1.3.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, DC configuration specified in clause 5.5B.4 and test channel bandwidths specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1, and sub-carrier spacing based on NR operating bands specified in TS 38.521-1 [8] clause 5.3. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration, and are shown in table 6.2B.1.3.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexe A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C, clause C.2 and in TS 38.521-1 [8] Annex C, clause C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.1.3.4.1-1: Test configuration table** + +| Default Conditions | | | | | | | | | +|------------------------------------------------------------------------------------------------------|------------------|------------------|-----------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------|----------------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 and TS 36.508 [6] | | | | | Low range for E-UTRA CC1 and NR CC1,
Mid range for E-UTRA CC1 and NR CC1,
High range for E-UTRA CC1 and NR CC1 (NOTE 4) | | | | +| Test EN-DC channel bandwidth as specified in TS 36.508 [6] clause 4.3.1 and TS 38.508-1 clause 4.3.1 | | | | | 5MHz for E-UTRA CC1 and Lowest for NR CC1,
Highest for E-UTRA CC1 and Highest for NR CC1 | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | | | | | Lowest, Highest | | | | +| Test Parameters | | | | | EN-DC Uplink Configuration | | | | +| Test ID | Test Freq | E-UTRA BW | NR BW | Downlink Configuration | E-UTRA Cell | | NR Cell | | +| | | | | | Modulation | RB allocation (NOTE 1) | Modulation (NOTE 3) | RB allocation (NOTE 2) | +| 1 5 | High | Default | Default | N/A | QPSK | 1RB_Right | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Right | +| 2 5 | Low | Default | Default | | QPSK | 1RB_Left | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Left | +| 3 5 | Default | Default | Default | | QPSK | Partial_Allocation | DFT-s-OFDM Pi/2 BPSK | Inner_Full | +| 4 5 | High | Default | Default | | QPSK | 1RB_Right | DFT-s-OFDM QPSK | Inner_1RB_Right | +| 5 5 | Low | Default | Default | | QPSK | 1RB_Left | DFT-s-OFDM QPSK | Inner_1RB_Left | +| 6 5 | Default | Default | Default | | QPSK | Partial_Allocation | DFT-s-OFDM QPSK | Inner_Full | +| 7 | High | 5MHz, Highest | Lowest | | QPSK | 1RB_Right | N/A | N/A | +| 8 | Low | 5MHz, Highest | Lowest | | QPSK | 1RB_Left | N/A | N/A | +| 9 | Default | 5MHz, Highest | Lowest | | QPSK | Partial_Allocation | N/A | N/A | +| 10 | High | 5MHz | Lowest, Highest | | N/A | N/A | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Right | +| 11 | Low | 5MHz | Lowest, Highest | | N/A | N/A | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Left | +| 12 | Default | 5MHz | Lowest, Highest | | N/A | N/A | DFT-s-OFDM Pi/2 BPSK | Inner_Full | +| 13 | High | 5MHz | Lowest, Highest | | N/A | N/A | DFT-s-OFDM QPSK | Inner_1RB_Right | +| 14 | Low | 5MHz | Lowest, Highest | | N/A | N/A | DFT-s-OFDM QPSK | Inner_1RB_Left | +| 15 | Default | 5MHz | Lowest, Highest | | N/A | N/A | DFT-s-OFDM QPSK | Inner_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +NOTE 3: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in NR FR1. +NOTE 4: For NR band n28, the Highest test channel bandwidth is replaced by 20MHz due to MPR is always larger than 0dB for 30MHz bandwidth. +NOTE 5: Only applicable to UEs not supporting UE capability *singleUL-Transmission*. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] clause A.3.1.1 for SS and clause A.3.2.1 for UE. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set according to Table 6.2B.1.3.3-1. +5. Propagation conditions are set according to TS 36.521-1 [10] and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.3.4.3. +7. For the case of testing overlapping E-UTRA and NR UL transmission scenario when both bands are TDD, ensure E-UTRA UL transmission overlaps with NR UL transmission in time by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.1.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.2B.1.3.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. For an E-UTRA FDD and NR TDD EN-DC band combination, if UE supports PC2, the percentage of EUTRA uplink symbols transmitted in each radio frame shall be less than 40%. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level. +3. For test ID 1~6 measure the sum of mean transmitted power over all EN-DC component carriers in the EN-DC, which shall meet the requirements described in table 6.2B.1.3.5-1 and the period of the measurement shall be at least the continuous duration of one active sub-frame. For FDD band in inter-band CA with both TDD band and FDD band, only slots overlapping with only UL symbols in TDD are under test. + +For test ID 7~15 measure the mean transmitted power over E-UTRA carrier or NR carrier, which shall meet the requirements described in table 6.2.2.5-1 in TS 36.521-1 [10] or table 6.2.1.5-1 in TS 38.521-1 [8] respectively. The period of the measurement shall be at least the continuous duration of one active sub-frame. + +4. For UEs supporting Power Class 2, repeat steps 1~3 on the applicable bands with message exception defined in Table 6.2B.1.3.4.3-5. + +###### 6.2B.1.3.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions: + +**Table 6.2B.1.3.4.3-0: PUSCH-Config** + +| | +|---------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|---------------------------------------------------------------------------------------------| + +**Table 6.2B.1.3.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|-------------------------------------------------------------|--------------------------------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalCellGroupConfig ::= SEQUENCE { | | | | +| p-NR-FR1 | 20 | For simultaneous E-UTRA and NR transmission | Power Class 3 UE Test IDs 1-6 | +| | 23 | For Test IDs 7~9 NR carrier is configured but not measured. | Power Class 3 UE Test IDs 7-15 | +| | 23 | For simultaneous E-UTRA and NR transmission | Power Class 2 UE Test IDs 1-6 | +| | 26 | For Test IDs 7~9 NR carrier is configured but not measured. | Power Class 2 UE Test IDs 7-15 | +| | 26 | For simultaneous E-UTRA and NR transmission | Power Class 2 UE Test IDs 1-6 if UE indicates support of higherPowerLimit-r17 | +| } | | | | + +**Table 6.2B.1.3.4.3-2: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|-------------------------------------------------------------------|--------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 20 | For simultaneous E-UTRA and NR transmission | Power Class 3 UE Test IDs 1-6 | +| | 23 | For Test IDs 10~15 E-UTRA carrier is configured but not measured. | Power Class 3 UE Test IDs 7-15 | +| | 23 | For simultaneous E-UTRA and NR transmission | Power Class 2 UE Test IDs 1-6 | +| | 26 | For Test IDs 10~15 E-UTRA carrier is configured but not measured. | Power Class 2 UE Test IDs 7-15 | + +**Table 6.2B.1.3.4.3-3: RRCConnectionReconfiguration: tdm-PatternConfig if E-UTRA on FDD band and UE does not support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|---------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | Test IDs 7-15 | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.1.3.4.3-4: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.1.3.4.3-5: RRCConnectionReconfiguration: p-MaxUE-FR1-r15 (step 4 in 6.2B.1.3.4.2)** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 2 UE | +| } | | | | + +###### 6.2B.1.3.5 Test requirements + +For test ID 1~6 the maximum output power for the DC configuration, derived in step 3 shall be within the range prescribed by the UE Power Class and tolerance in Table 6.2B.1.3.5-1. + +For test ID 7~15 the maximum output power for the DC configuration, derived in step 3 shall be within the range prescribed by the UE Power Class and tolerance in table 6.2.2.5-1 in TS 36.521-1 [10] or table 6.2.1.5-1 in TS 38.521-1 [8] for E-UTRA carrier and NR carrier respectively for Power class 3, and in Table 6.2B.1.3.5-2a for Power class 2. + +For test ID 1~6 the maximum output power for the DC configuration, derived in step 4 shall be within the range prescribed by Power Class 3 and tolerance in Table 6.2B.1.3.5-1. + +For test ID 7~15 the maximum output power for the DC configuration, derived in step 4 shall be within the range prescribed by Power Class 3 and tolerance in table 6.2.2.5-1 in TS 36.521-1 [10] or table 6.2.1.5-1 in TS 38.521-1 [8] for E-UTRA carrier and NR carrier respectively. + +**Table 6.2B.1.3.5-1: Maximum output power for inter-band EN-DC (two bands), for overlapping UL transmission** + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------|-------------------------------------|--------------------------|---------------------|----------------| +| DC_1A_n3A | | | 23 | +2 +TT/-3-TT | +| DC_1A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_1A_n7A | | | 23 | +2 +TT/-3-TT | +| DC_1A_n28A | | | 23 | +2 +TT/-3-TT | +| DC_1A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_1A_n78A | 26 8 , 27.8 9 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_1A_n79A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_2A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_2A_n41A | | | 23 | +2 +TT/-3-TT | +| DC_2A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_2A_n71A | | | 23 | +2 +TT/-3-TT | +| DC_2A_n77A | 26 8 , 27.8 9 | +2+TT/-3-TT | 23 | +2+TT/-3-TT | +| DC_2A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n1A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n7A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n8A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n28A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n41A | 26 8 , 27.8 9 | +2+TT/-3-TT 3 | 23 | +2+TT/-3-TT | +| DC_3A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_3A_n78A | 26 8 , 27.8 9 | +2+TT/-3-TT 3 | 23 | +2 +TT/-3-TT | +| DC_3A_n79A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_5A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_5A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_5A_n77A | 26 8 , 27.8 9 | +2+TT/-3-TT | 23 | +2+TT/-3-TT | +| DC_5A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_7A_n1A | | | 23 | +2 +TT/-3-TT | +| DC_7A_n3A | | | 23 | +2 +TT/-3-TT | +| DC_7A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_7A_n28A | | | 23 | +2 +TT/-3-TT | +| DC_7A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_7A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_8A_n1A | | | | +2 +TT/-3-TT | +| DC_8A_n3A | | | | +2 +TT/-3-TT | +| DC_8A_n20A | | | 23 | +2 +TT/-3-TT | +| DC_8A_n41A | | | 23 | +2 +TT/-3-TT | +| DC_8A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_8A_n78A | 26 8 , 27.8 9 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_11A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_11A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_11A_n79A | | | 23 | +2 +TT/-3-TT | +| DC_12A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_12A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_12A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_12A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_12A_n78A | | | 23 | +2 +TT/-3-TT | + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------|-------------------------------------|--------------------|---------------------|----------------| +| DC_13A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_13A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_13A_n77A | 26 8 , 27.8 9 | +2+TT/-3-TT | 23 | +2+TT/-3-TT | +| DC_14A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_14A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_14A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_18A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_18A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_18A_n79A | | | 23 | +2 +TT/-3-TT | +| DC_19A_n1A | | | 23 | +2 +TT/-3-TT | +| DC_19A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_19A_n78A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_19A_n79A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_20A_n1A | | | 23 | +2 +TT/-3-TT | +| DC_20A_n3A | | | 23 | +2 +TT/-3-TT | +| DC_20A_n7A | | | 23 | +2 +TT/-3-TT | +| DC_20A_n8A | | | 23 | +2 +TT/-3-TT | +| DC_20A_n28A | | | 23 | +2 +TT/-3-TT | +| DC_20A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_21A_n1A | | | 23 | +2 +TT/-3-TT | +| DC_21A_n28A | | | 23 | +2 +TT/-3-TT | +| DC_21A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_21A_n78A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_21A_n79A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_25A_n41A | | | 23 | +2 +TT/-3-TT | +| DC_26A_n41A | | | 23 | +2 +TT/-3-TT | +| DC_26A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_26A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_26A_n79A | | | 23 | +2 +TT/-3-TT | +| DC_28A_n3A | | | 23 | +2 +TT/-3-TT | +| DC_28A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_28A_n7A | | | 23 | +2 +TT/-3-TT | +| DC_28A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_28A_n78A | 26 8 | +2+TT/-3-TT | 23 | +2 +TT/-3-TT | +| DC_28A_n79A | | | 23 | +2 +TT/-3-TT | +| DC_30A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_30A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_30A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_30A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_38A_n78A | | | N/A | N/A | +| DC_39A_n41A | 26, 27.8 9 | +2/-3 1 | 23 | +2 +TT/-3-TT | +| DC_39A_n79A | 26, 27.8 9 | +2/-3 | 23 | +2 +TT/-3-TT | +| DC_40A_n1A | | | 23 | +2 +TT/-3-TT | +| DC_40A_n41A | | | 23 | +2 +TT/-3-TT | +| DC_40A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_40A_n79A | | | 23 | +2 +TT/-3-TT | + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------|-------------------------------------|--------------------|---------------------|----------------| +| DC_41A_n77A | | | 23 | +2 +TT/-3-TT | +| DC_41A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_41A_n79A | 26, 27.8 9 | +2/-3 1 | 23 | +2 +TT/-3-TT | +| DC_42A_n77A | | | N/A | N/A | +| DC_42A_n78A | | | N/A | N/A | +| DC_42A_n79A | | | N/A | N/A | +| DC_48A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_48A_n46A | | | 23 | +2 +TT/-3-TT | +| DC_48A_n66A | | | 23 | +2 +TT/-3-TT | +| DC_66A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_66A_n5A | | | 23 | +2 +TT/-3-TT | +| DC_66A_n41A | | | 23 | +2 +TT/-3-TT | +| DC_66A_n71A | | | 23 | +2 +TT/-3-TT | +| DC_66A_n77A | 26 8 , 27.8 9 | +2+TT/-3-TT | 23 | +2+TT/-3-TT | +| DC_66A_n78A | | | 23 | +2 +TT/-3-TT | +| DC_71A_n2A | | | 23 | +2 +TT/-3-TT | +| DC_71A_n66A | | | 23 | +2 +TT/-3-TT | + +NOTE 1: TT applies to output power in each UL carrier with E-UTRA UL transmission not overlapping with NR UL transmission in time, and its value is the same as TT of standalone E-UTRA or NR transmission. For detailed values refer to Table 6.2B.1.3.5-4. + +NOTE 2: TT applies to overall output power with E-UTRA UL transmission overlapping with NR UL transmission in time, and its value is the maximum TT among all E-UTRA and NR UL carriers. For detailed values refer to Table 6.2B.1.3.5-3. + +NOTE 3: An uplink DC configuration in which at least one of the bands has NOTE 3 in Table 6.2.1.3-1 in TS 38.521-1 [8] or NOTE 2 in Table 6.2.2.3-1 in TS 36.521-1 [21] is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands is confined within FUL\_low and FUL\_low + 4 MHz or FUL\_high – 4 MHz and FUL\_high. + +NOTE 4: PPowerClass, EN-DC is the maximum UE power specified without taking into account the tolerance. + +NOTE 5: For inter-band EN-DC the maximum power requirement should apply to the total transmitted power over all component carriers (per UE). + +NOTE 6: Power Class 3 is the default power class unless otherwise stated. + +NOTE 7: The UE is not required to support PC2 within each individual cell group. Power class support within each individual cell group is signaled separately by the UE. + +NOTE 8: The UE supports PC3 within E-UTRA cell group and supports either PC3 or PC2 within NR cell group. Power class support within each individual cell group is signalled separately by the UE. + +NOTE 9: The UE that supports PC3 within a TDD or FDD band and supports PC2 within a second TDD band and indicates support of *higherPowerLimit-r17* capability. + +Table 6.2B.1.3.5-2: Void + +**Table 6.2B.1.3.5-2a: Maximum output power for inter-band EN-DC (two bands), for non-overlapping UL transmission for power class 2** + +| EN-DC configuration | Carrier | Power class 2 (dBm) | Tolerance (dB) | Condition | Comment | +|---------------------|----------------|---------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_1A_n78A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_1A_n79A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_2A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | | | | | +|------------|----------------|----|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_3A_n41A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_3A_n78A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_3A_n79A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | | | | | +|-------------|----------------|----|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_5A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) or UE reporting (PC3 by $P_{PowerClass,NR}$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_8A_n78A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_12A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | | | | | +|-------------|----------------|----|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_13A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_14A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_19A_n78A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | | | | | +|-------------|----------------|----|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_19A_n79A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_21A_n78A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_21A_n79A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by powerClassNRPart-r16 ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by powerClassNRPart-r16 ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | | | | | +|-------------|----------------|----|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_28A_n78A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_30A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_39A_n41A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | | | | | +|-------------|----------------|----|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| DC_39A_n79A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_41A_n79A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 26 | +2+TT/-2-TT | UE indicates PC2 on E-UTRA band | UE meets power class 2 requirements | +| | | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | +| DC_66A_n77A | NR carrier | 26 | +2+TT/-3-TT | Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC2 or Not present by $powerClassNRPart-r16$ ) | UE meets power class 2 requirements | +| | | 23 | +2+TT/-3-TT | Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{PowerClass,NR}$ , and PC3 by $powerClassNRPart-r16$ ) | UE meets power class 3 requirements | +| | E-UTRA carrier | 23 | +2+TT/-2-TT | UE indicates PC3 on E-UTRA band | UE meets power class 3 requirements | + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | TT applies to output power in each UL carrier with E-UTRA UL transmission not overlapping with NR UL transmission in time, and its value is the same as TT of standalone E-UTRA or NR transmission. For detailed values refer to Table 6.2B.1.3.5-4. | +| NOTE 2: | An uplink DC configuration in which at least one of the bands has NOTE 3 in Table 6.2.1.3-1 in TS 38.521-1 [8] or NOTE 2 in Table 6.2.2.3-1 in TS 36.521-1 [21] is allowed to reduce the lower tolerance limit by 1.5 dB when the transmission bandwidths of at least one of the bands is confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ . | +| NOTE 3: | $P_{PowerClass, EN-DC}$ is the maximum UE power specified without taking into account the tolerance. | + +**Table 6.2B.1.3.5-3: Test Tolerance for UE maximum output power (Overlapping UL transmission)** + +| TT for overall output power | | | | | | | | | | | | +|-----------------------------|------------|--------------------------|-----------------|--------------------------|--------------------------|---------------------|--------------------------|--------------------------|---------------------|--------------------------|--------------------------| +| | | | NR | | | | | | | | | +| | | | BW ≤ 20MHz | | | 20 MHz < BW ≤ 40MHz | | | 40MHz < BW ≤ 100MHz | | | +| | | | $f \leq 3.0GHz$ | $3.0GHz < f \leq 4.2GHz$ | $4.2GHz < f \leq 6.0GHz$ | $f \leq 3.0GHz$ | $3.0GHz < f \leq 4.2GHz$ | $4.2GHz < f \leq 6.0GHz$ | $f \leq 3.0GHz$ | $3.0GHz < f \leq 4.2GHz$ | $4.2GHz < f \leq 6.0GHz$ | +| E-UTRA | BW ≤ 20MHz | $f \leq 3.0GHz$ | 0.7 dB | 1.0 dB | 1.0 dB | 0.7 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | +| | | $3.0GHz < f \leq 4.2GHz$ | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | + +**Table 6.2B.1.3.5-4: Test Tolerance for UE maximum output power (Separate measurements over E-UTRA and NR CCs)** + +| Uplink TX | | $f \leq 3.0GHz$ | $3.0GHz < f \leq 4.2GHz$ | $4.2GHz < f \leq 6GHz$ | +|-----------|---------------------|-----------------|--------------------------|------------------------| +| E-UTRA | BW ≤ 20MHz | 0.7 dB | 1.0 dB | N/A | +| NR | BW ≤ 40MHz | 0.7 dB | 1.0 dB | 1.0 dB | +| | 40MHz < BW ≤ 100MHz | 1.0 dB | 1.0 dB | 1.0 dB | + +##### 6.2B.1.3\_1 UE Maximum Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) + +###### 6.2B.1.3\_1.1 Test purpose + +Same test purpose as in clause 6.2B.1.3.1 + +###### 6.2B.1.3\_1.2 Test applicability + +This test applies to all types of E-UTRA UE release 16 and forward, supporting inter-band EN-DC with 2 E-UTRA CCs and 1 NR CC operating on FR1. + +###### 6.2B.1.3\_1.3 Minimum conformance requirements + +For inter-band EN-DC of E-UTRA and NR in FR1, the following UE Power Classes define the maximum output power for any transmission bandwidth within the aggregated channel bandwidth. The maximum output power is measured as the sum of the maximum output power at each UE antenna connector. The period of measurement shall be at least one sub frame (1ms). UE maximum output power shall be measured over all component carriers from different bands. If each band has separate antenna connectors, maximum output power is measured as the sum of maximum output power at each UE antenna connector. + +**Table 6.2B.1.3\_1.3-1: Maximum output power for inter-band EN-DC (two bands)** + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------|---------------------|----------------| +| DC_7C_n78A | | | 23 | +2/-3 | +| NOTE 1: For the transmission bandwidths confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB. | | | | | +| NOTE 2: $P_{PowerClass, EN-DC}$ is the maximum UE power specified without taking into account the tolerance. | | | | | +| NOTE 3: For inter-band EN-DC the maximum power requirement should apply to the total transmitted power over all component carriers (per UE). | | | | | +| NOTE 4: Power Class 3 is the default power class unless otherwise stated. | | | | | +| NOTE 5: The UE is not required to support PC2 within each individual cell group. Power class support within each individual cell group is signalled separately by the UE. | | | | | +| NOTE 6: The UE supports PC3 within E-UTRA cell group, and supports either PC3 or PC2 within NR cell group. Power class support within each individual cell group is signalled separately by the UE. | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1. + +LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.2B.1.3\_1.4 Test description + +###### 6.2B.1.3\_1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, DC configuration specified in clause 5.5B.4 and test channel bandwidths specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1, and sub-carrier spacing based on NR operating bands specified in TS 38.521-1 [8] clause 5.3. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration, and are shown in table 6.2B.1.3\_1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexe A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C, clause C.2 and in TS 38.521-1 [8] Annex C, clause C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.1.3\_1.4.1-1: Test configuration table** + +| Default Conditions | | | | | | | | | +|------------------------------------------------------------------------------------------------------|-----------|----------------------------------------------------------|-----------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 and TS 36.508 [6] | | | | | Low range for MCG and SCG, High range for MCG and SCG | | | | +| Test EN-DC channel bandwidth as specified in TS 36.508 [6] clause 4.3.1 and TS 38.508-1 clause 4.3.1 | | | | | Lowest N RB_agg for E-UTRA CCs and Lowest for NR CC1, Highest N RB_agg for E-UTRA CCs and Highest for NR CC1 | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | | | | | Lowest, Highest | | | | +| Test Parameters | | | | | EN-DC Uplink Configuration | | | | +| Test ID | Test Freq | E-UTRA BW | NR BW | Downlink Configuration | MCG – EUTRA PCC&SCC | | SCG - NR | | +| | | | | | Modulation | RB allocation (NOTE 1) | Modulation (NOTE 3) | RB allocation (NOTE 2) | +| 1 | High | Default | Default | N/A | QPSK | 1RB_Right | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Right | +| 2 | Low | Default | Default | | QPSK | 1RB_Left | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Left | +| 3 | Default | Default | Default | | QPSK | Partial_Allocation | DFT-s-OFDM Pi/2 BPSK | Inner_Full | +| 4 | High | Default | Default | | QPSK | 1RB_Right | DFT-s-OFDM QPSK | Inner_1RB_Right | +| 5 | Low | Default | Default | | QPSK | 1RB_Left | DFT-s-OFDM QPSK | Inner_1RB_Left | +| 6 | Default | Default | Default | | QPSK | Partial_Allocation | DFT-s-OFDM QPSK | Inner_Full | +| 7 | High | Lowest N RB_agg , Highest N RB_agg | Lowest | | QPSK | 1RB_Right | N/A | N/A | +| 8 | Low | Lowest N RB_agg , Highest N RB_agg | Lowest | | QPSK | 1RB_Left | N/A | N/A | +| 9 | Default | Lowest N RB_agg , Highest N RB_agg | Lowest | | QPSK | Partial_Allocation | N/A | N/A | +| 10 | High | Lowest N RB_agg | Lowest, Highest | | N/A | N/A | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Right | +| 11 | Low | Lowest N RB_agg | Lowest, Highest | | N/A | N/A | DFT-s-OFDM Pi/2 BPSK | Inner_1RB_Left | +| 12 | Default | Lowest N RB_agg | Lowest, Highest | | N/A | N/A | DFT-s-OFDM Pi/2 BPSK | Inner_Full | +| 13 | High | Lowest N RB_agg | Lowest, Highest | | N/A | N/A | DFT-s-OFDM QPSK | Inner_1RB_Right | +| 14 | Low | Lowest N RB_agg | Lowest, Highest | | N/A | N/A | DFT-s-OFDM QPSK | Inner_1RB_Left | +| 15 | Default | Lowest N RB_agg | Lowest, Highest | | N/A | N/A | DFT-s-OFDM QPSK | Inner_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-2 in current specification. For 1RB\_Left allocation, the PCC is located on the lower frequency while SCC is located on the higher frequency. For 1RB\_Right allocation, the PCC is located on the higher frequency while SCC is located on the lower frequency. + +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 3: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in NR FR1. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] clause A.3.1.1 for SS and clause A.3.2.1 for UE. + +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG PCC and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set according to Table 6.2B.1.3\_1.3-1. +5. Propagation conditions are set for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.3\_1.4.3. +7. For the case of testing overlapping E-UTRA and NR UL transmission scenario when both bands are TDD, ensure E-UTRA UL transmission overlaps with NR UL transmission in time by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.1.3\_1.4.2 Test procedure + +1. Configure E-UTRA SCC according to TS 36.521-1 [10] Annex C.0, C.1 and Annex C.3.0 for all E-UTRA downlink physical channels. +2. The SS shall configure SCC as per TS 36.508 [11] clause 5.2A.4. Message contents are defined in clause 6.2B.1.3\_1.4.3. +3. SS activates SCC by sending the activation MAC-CE (Refer TS 36.321, clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133 [12], clauses 8.3.3.2). +4. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.2B.1.3\_1.4.1-1 on E-UTRA PCC and SCC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +5. Send continuously uplink power control "up" commands in every uplink scheduling information to the UE until the UE transmits at its PUMAX level; allow at least 200 ms from the first TPC command for the UE to reach PUMAX level. +6. For test ID 1~6 measure the sum of mean transmitted power over all EN-DC component carriers in the EN-DC, which shall meet the requirements described in table 6.2B.1.3\_1.5-1 and the period of the measurement shall be at least the continuous duration of one active sub-frame. + +For test ID 7~9 measure the sum of mean transmitted power over all E-UTRA component carriers, which shall meet the requirements described in Table 6.2.2A.1.5-1 in TS 36.521-1 [10]. The period of the measurement shall be at least the continuous duration of one active sub-frame. + +For test ID 10~15 measure the mean transmitted power over NR carrier, which shall meet the requirements described in Table 6.2.1.5-1 in TS 38.521-1 [8] respectively. The period of the measurement shall be at least the continuous duration of one active sub-frame. + +###### 6.2B.1.3\_1.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions: + +**Table 6.2B.1.3\_1.4.3-1: PUSCH-Config** + +| | +|---------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|---------------------------------------------------------------------------------------------| + +**Table 6.2B.1.3\_1.4.3-2: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|-------------------------------------------------------------|--------------------------------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalCellGroupConfig ::= SEQUENCE { | | | | +| p-NR-FR1 | 20 | For simultaneous E-UTRA and NR transmission | Power Class 3 UE Test IDs 1-6 | +| | 23 | For Test IDs 7~9 NR carrier is configured but not measured. | Power Class 3 UE Test IDs 7-15 | +| } | | | | + +**Table 6.2B.1.3\_1.4.3-3: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|-------------------------------------------------------------------|--------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 20 | For simultaneous E-UTRA and NR transmission | Power Class 3 UE Test IDs 1-6 | +| | 23 | For Test IDs 10~15 E-UTRA carrier is configured but not measured. | Power Class 3 UE Test IDs 7-15 | + +**Table 6.2B.1.3\_1.4.3-4: RRCConnectionReconfiguration: tdm-PatternConfig if E-UTRA on FDD band and UE does not support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|---------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | Test IDs 7-15 | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.1.3\_1.4.3-5: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +###### 6.2B.1.3\_1.5 Test requirements + +For test ID 1~6 the maximum output power for the DC configuration, derived in step 6 shall be within the range prescribed by the UE Power Class and tolerance in Table 6.2B.1.3\_1.5-1. + +For test ID 7~15 the maximum output power for the DC configuration, derived in step 6 shall be within the range prescribed by the UE Power Class and tolerance in Table 6.2.2A.1.5-1 in TS 36.521-1 [10] or Table 6.2.1.5-1 in TS 38.521-1 [8] for E-UTRA CG and NR CG respectively for Power class 3. + +**Table 6.2B.1.3\_1.5-1: Maximum output power for inter-band EN-DC (two bands), for overlapping UL transmission** + +| EN-DC configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------|---------------------|----------------| +| DC_7C_n78A | | | 23 | +2+TT/-3-TT | +| NOTE 1: TT applies to output power in each UL carrier with E-UTRA UL transmission not overlapping with NR UL transmission in time, and its value is the same as TT of standalone E-UTRA or NR transmission. For detailed values refer to Table 6.2B.1.3_1.5-2. | | | | | +| NOTE 2: TT applies to overall output power with E-UTRA UL transmission overlapping with NR UL transmission in time, and its value is the maximum TT among all E-UTRA and NR UL carriers. For detailed values refer to Table 6.2B.1.3_1.5-2. | | | | | +| NOTE 3: For the transmission bandwidths confined within F UL_low and F UL_low + 4 MHz or F UL_high - 4 MHz and F UL_high , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB. | | | | | +| NOTE 4: P PowerClass, EN-DC is the maximum UE power specified without taking into account the tolerance. | | | | | +| NOTE 5: For inter-band EN-DC the maximum power requirement should apply to the total transmitted power over all component carriers (per UE). | | | | | +| NOTE 6: Power Class 3 is the default power class unless otherwise stated. | | | | | +| NOTE 7: The UE is not required to support PC2 within each individual cell group. Power class support within each individual cell group is signalled separately by the UE. | | | | | +| NOTE 8: The UE supports PC3 within E-UTRA cell group, and supports either PC3 or PC2 within NR cell group. Power class support within each individual cell group is signalled separately by the UE. | | | | | + +**Table 6.2B.1.3\_1.5-2: Test Tolerance for UE maximum output power (Overlapping UL transmission)** + +| TT for overall output power | | | | | | | | | | | | +|-----------------------------|------------|---------------------|------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------| +| | | | NR | | | | | | | | | +| | | | BW ≤ 20MHz | | | 20 MHz < BW ≤ 40MHz | | | 40MHz < BW ≤ 100MHz | | | +| | | | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | +| E-UTRA | BW ≤ 20MHz | f ≤ 3.0GHz | 0.7 dB | 1.0 dB | 1.0 dB | 0.7 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | +| | | 3.0GHz < f ≤ 4.2GHz | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | + +#### 6.2B.1.3a UE Maximum Output Power for Inter-Band NE-DC within FR1 + +###### 6.2B.1.3a.1 Test purpose + +Same test purpose as in clause 6.2B.1.3.1. + +##### 6.2B.1.3a.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band NE-DC operating on FR1. + +##### 6.2B.1.3a.3 Minimum conformance requirements + +For inter-band NE-DC of E-UTRA and NR in FR1, the following UE power classes define the maximum output power for any transmission bandwidth within the aggregated channel bandwidth. The maximum output power is measured as the sum of the maximum output power at each UE antenna connector. The period of measurement shall be at least one sub frame (1 ms). UE maximum output power shall be measured over all component carriers from different bands. If each band has separate antenna connectors, maximum output power is measured as the sum of maximum output power at each UE antenna connector. + +**Table 6.2B.1.3a.3-1: Maximum output power for inter-band NE-DC (two bands)** + +| NE-DC configuration | Power class 3 (dBm) | Tolerance (dB) | +|--------------------------|---------------------|----------------| +| DC_n28A_3A
DC_n28A_3C | 23 | +2/-3 | +| DC_n28A_39A | 23 | +2/-3 | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1.3a. + +##### 6.2B.1.3a.4 Test description + +###### 6.2B.1.3a.4.1 Initial condition + +Same initial condition as in clause 6.2B.1.3.4.1 with the following exception: + +Step 6 of Initial conditions will be updated as below: + +- Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity NE-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.3a.4.3. + +###### 6.2B.1.3a.4.2 Test procedure + +Same test procedure as in clause 6.2B.1.3.4.2 + +###### 6.2B.1.3a.4.3 Message contents + +Same message contents as in clause 6.2B.1.3.4.3. + +###### 6.2B.1.3a.5 Test requirements + +For test ID 1~6 the maximum output power for the DC configuration, derived in step 3 shall be within the range prescribed by the UE Power Class and tolerance in Table 6.2B.1.3a.5-1 for NE-DC. + +**Table 6.2B.1.3a.5-1: Maximum output power for inter-band NE-DC (two bands), for overlapping UL transmission** + +| NE-DC configuration | Power class 3 (dBm) | Tolerance (dB) | +|--------------------------|---------------------|----------------| +| DC_n28A_3A
DC_n28A_3C | 23 | +2+TT/-3-TT | +| DC_n28A_39A | 23 | +2+TT/-3-TT | + +Same Test Tolerance as in Table 6.2B.1.3.5-3. + +#### 6.2B.1.4 UE Maximum Output Power for Inter-Band EN-DC including FR2 + +##### 6.2B.1.4.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP and TRP + +Editor's note: The following aspects are either missing or not yet determined: + +- The referred test case 6.2.1.1 in TS 38.521-2 is incomplete for power class 2 and 4. + +###### 6.2B.1.4.1.1 Test purpose + +Same test purpose as in clause 6.2.1.1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.2B.1.4.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.2B.1.4.1.3 Minimum conformance requirements + +UE maximum output power requirement for E-UTRA single carrier and CA operation specified in subclauses 6.2.2 and 6.2.2A of TS 36.101 [10] and for NR single carrier and CA operation specified in subclause 6.2.1, 6.2A.1, and 6.2D.1 of TS 38.101-2 [9] apply. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1.4. + +###### 6.2B.1.4.1.4 Test description + +Same test description as in clause 6.2.1.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.2.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4.1.5 Test requirement + +Same test requirement as in clause 6.2.1.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.2B.1.4.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - Spherical Coverage + +**Editor's note:** The following aspects are either missing or not yet determined: + +- Measurement Uncertainties and Test Tolerances are FFS for power class 2 and 4. + +###### 6.2B.1.4.2.1 Test purpose + +Same test purpose as in clause 6.2.1.2.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.2B.1.4.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.2B.1.4.2.3 Minimum conformance requirements + +UE maximum output power requirement for E-UTRA single carrier and CA operation specified in subclauses 6.2.2 and 6.2.2A of TS 36.101 [10] and for NR single carrier and CA operation specified in subclause 6.2.1, 6.2A.1, and 6.2D.1 of TS 38.101-2 [9] apply. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1.4. + +###### 6.2B.1.4.2.4 Test description + +Same test description as in clause 6.2.1.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.2.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of initial conditions as in clause 6.2.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4.2.5 Test requirement + +Same test requirement as in clause 6.2.1.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.2B.1.4\_1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (>1 NR CC) + +###### 6.2B.1.4\_1.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) + +###### 6.2B.1.4\_1.1.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - EIRP and TRP + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.1.1.1 in TS 38.521-2 [9] is incomplete for aggregated BW > 400MHz. +- The referred test case 6.2A.1.1.1 in TS 38.521-2 [9] is incomplete for power class 1, 2 and 4. +- Test Procedures for EIRP beam peak Extreme Conditions are FFS. + +###### 6.2B.1.4\_1.1.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.2B.1.4\_1.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.2B.1.4\_1.1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2A.1.1.1.3 in TS 38.521-2 [9]. + +###### 6.2B.1.4\_1.1.1.4 Test description + +###### 6.2B.1.4\_1.1.1.4.1 Initial condition + +Same test description as in clause 6.2A.1.1.1.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.1.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.1.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.1.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4\_1.1.1.5 Test Requirements + +Same test requirement as in clause 6.2A.1.1.1.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.1.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - Spherical Coverage + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.1.2.1 in TS 38.521-2 is incomplete for aggregated BW > 400MHz. +- The referred test case 6.2A.1.2.1 in TS 38.521-2 is incomplete for power class 1, 2 and 4. + +###### 6.2B.1.4\_1.1.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.2B.1.4\_1.1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2NR UL CCs. + +###### 6.2B.1.4\_1.1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2A.1.2.1.3 in TS 38.521-2 [9]. + +###### 6.2B.1.4\_1.1.2.4 Test description + +###### 6.2B.1.4\_1.1.2.4.1 Initial condition + +Same test description as in clause 6.2A.1.2.1.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.1.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.1.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.1.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4\_1.1.2.5 Test Requirements + +Same test requirement as in clause 6.2A.1.2.1.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) + +###### 6.2B.1.4\_1.2.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - EIRP and TRP + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.1.1.2 in TS 38.521-2 is incomplete for aggregated BW > 400MHz. +- The referred test case 6.2A.1.1.2 in TS 38.521-2 is incomplete for power class 1, 2 and 4. +- Test Procedures for EIRP beam peak Extreme Conditions are FFS. + +###### 6.2B.1.4\_1.2.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.2.1 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.2.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3NR UL CCs. + +###### 6.2B.1.4\_1.2.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2A.1.1.2.3 in TS 38.521-2 [9]. + +###### 6.2B.1.4\_1.2.1.4 Test description + +###### 6.2B.1.4\_1.2.1.4.1 Initial condition + +Same test description as in clause 6.2A.1.1.2.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.1.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.1.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.1.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4\_1.2.1.5 Test Requirements + +Same test requirement as in clause 6.2A.1.1.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.2B.1.4\_1.2.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - Spherical Coverage + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.1.2.2 in TS 38.521-2 is incomplete for aggregated BW > 400MHz. +- The referred test case 6.2A.1.2.2 in TS 38.521-2 is incomplete for power class 1, 2 and 4. + +###### 6.2B.1.4\_1.2.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.2.1 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.2.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.2B.1.4\_1.2.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2A.1.2.2.3 in TS 38.521-2 [9]. + +###### 6.2B.1.4\_1.2.2.4 Test description + +###### 6.2B.1.4\_1.2.2.4.1 Initial condition + +Same test description as in clause 6.2A.1.2.2.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.1.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.1.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.1.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4\_1.2.2.5 Test Requirements + +Same test requirement as in clause 6.2A.1.2.2.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.3 UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) + +###### 6.2B.1.4\_1.3.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) - EIRP and TRP + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.2A.1.1.3 in TS 38.521-2 is incomplete for aggregated BW > 400MHz. +- The referred test case 6.2A.1.1.3 in TS 38.521-2 is incomplete for power class 1, 2 and 4. +- Test Procedures for EIRP beam peak Extreme Conditions are FFS. + +###### 6.2B.1.4\_1.3.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.3.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.2B.1.4\_1.3.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4NR UL CCs. + +###### 6.2B.1.4\_1.3.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2A.1.1.3.3 in TS 38.521-2 [9]. + +###### 6.2B.1.4\_1.3.1.4 Test description + +###### 6.2B.1.4\_1.3.1.4.1 Initial condition + +Same test description as in clause 6.2A.1.1.3.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.1.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.1.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.1.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4\_1.3.1.5 Test Requirements + +Same test requirement as in clause 6.2A.1.1.3.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.3.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) – Spherical Coverage + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.2A.1.2.3 in TS 38.521-2 is incomplete for aggregated BW > 400MHz. +- The referred test case 6.2A.1.2.3 in TS 38.521-2 is incomplete for power class 1, 2 and 4. + +###### 6.2B.1.4\_1.3.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.3.1 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.3.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4NR UL CCs. + +###### 6.2B.1.4\_1.3.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2A.1.2.3.3 in TS 38.521-2[9]. + +###### 6.2B.1.4\_1.3.2.4 Test description + +###### 6.2B.1.4\_1.3.2.4.1 Initial condition + +Same test description as in clause 6.2A.1.2.3.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.1.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.1.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.1.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4\_1.3.2.5 Test Requirements + +Same test requirement as in clause 6.2A.1.2.3.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.4 UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) + +###### 6.2B.1.4\_1.4.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) - EIRP and TRP + +###### 6.2B.1.4\_1.4.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.4.1 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.4.1.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 *NR* carrier. + +No test case details are specified + +###### 6.2B.1.4\_1.4.1.5 Test Requirements + +Same test requirement as in clause 6.2A.1.1.4.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.4.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) – Spherical Coverage + +###### 6.2B.1.4\_1.4.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.4.1 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.4.2.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 *NR* carrier. + +No test case details are specified. + +###### 6.2B.1.4\_1.4.2.5 Test Requirements + +Same test requirement as in clause 6.2A.1.2.4.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.5 UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) + +###### 6.2B.1.4\_1.5.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) - EIRP and TRP + +###### 6.2B.1.4\_1.5.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.5.1 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.1.4\_1.5.1.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 NR carrier. + +No test case details are specified. + +###### 6.2B.1.4\_1.5.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) – Spherical Coverage + +###### 6.2B.1.4\_1.5.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.5.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.2B.1.4\_1.5.2.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 NR carrier. + +No test case details are specified. + +###### 6.2B.1.4\_1.6 UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) + +###### 6.2B.1.4\_1.6.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) - EIRP and TRP + +###### 6.2B.1.4\_1.6.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.6.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.2B.1.4\_1.6.1.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 NR carrier. + +No test case details are specified. + +###### 6.2B.1.4\_1.6.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) – Spherical Coverage + +###### 6.2B.1.4\_1.6.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.6.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.2B.1.4\_1.6.2.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 NR carrier. + +No test case details are specified. + +###### 6.2B.1.4\_1.7 UE Maximum Output Power for Inter-Band EN-DC including FR2 (8 NR CCs) + +###### 6.2B.1.4\_1.7.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (8 NR CCs) - EIRP and TRP + +###### 6.2B.1.4\_1.7.1.1 Test purpose + +Same test purpose as in clause 6.2A.1.1.7.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.2B.1.4\_1.7.1.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 NR carrier. + +No test case details are specified. + +###### 6.2B.1.4\_1.7.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (8 NR CCs) – Spherical Coverage + +###### 6.2B.1.4\_1.7.2.1 Test purpose + +Same test purpose as in clause 6.2A.1.2.7.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.2B.1.4\_1.7.2.2 Test applicability + +The requirements in this test are not testable due to lack of appropriate test points since there's no configuration satisfying MPR=0dB requirements in RAN4 for FR2 NR carrier. + +No test case details are specified. + +#### 6.2B.1.4D UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO - EIRP and TRP + +##### 6.2B.1.4D.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.2D.1.1 in TS 38.521-2 [9] is incomplete for ETC. + +###### 6.2B.1.4D.1.1 Test purpose + +Same test purpose as in clause 6.2D.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.2B.1.4D.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with UL MIMO. + +###### 6.2B.1.4D.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2D.1.1 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.2B.1.4. + +###### 6.2B.1.4D.1.4 Test description + +Same test description as in clause 6.2D.1.1 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.2D.1.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2D.1.1 in TS 38.521-2 [9] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.6. + +###### 6.2B.1.4D.1.5 Test requirement + +Same test requirement as in clause 6.2D.1.5 of TS 38.521-2 [9] for the NR carrier. + +##### 6.2B.1.4D.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO-Spherical coverage + +###### 6.2B.1.4D.2.1 Test purpose + +Same test purpose as in clause 6.2D.1.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.2B.1.4D.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with UL MIMO. + +###### 6.2B.1.4D.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2D.1.2 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.2B.1.4. + +###### 6.2B.1.4D.2.4 Test description + +Same test description as in clause 6.2D.1.2 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.2D.1.2 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2D.1.2 in TS 38.521-2 [9] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.1.4D.2.5 Test requirement + +Same test requirement as in clause 6.2D.1.2 of TS 38.521-2 [9] for the NR carrier. + +#### 6.2B.1.5 UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 + +##### 6.2B.1.5.1 Test purpose + +Same test purpose as in clause 6.2.1.1 in TS 38.521-1 [8] for NR FR1 carrier and 6.2.1.1 in TS 38.521-2 [9] for NR FR2 carrier. + +##### 6.2B.1.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum output power apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.2B. + +#### 6.2B.1.5D UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 for UL MIMO + +##### 6.2B.1.5D.1 Test purpose + +Same test purpose as in clause 6.2.1.1 in TS 38.521-1 [8] for NR FR1 carrier and 6.2.1.1 in TS 38.521-2 [9] for NR FR2 carrier. + +##### 6.2B.1.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum output power apply and are tested as part of the EN-DC within FR1 as in clause 6.2.1 in TS 38.521-1 [8] and EN-DC within FR2 as in clause 6.2.1 in TS 38.521-2 [9]. + +#### 6.2B.1.6 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP with UL Gaps + +**Editor's note:** This clause is incomplete. The associated standalone test 6.2.5 in TS 38.521-2 [9] is incomplete as the following aspects are either missing or not yet determined: + +- The test case is incomplete for band n259. +- Initial conditions are pending analysis for PC1, PC5, PC6 and PC7. +- Impact of polarization on the measurements is still FFS. +- MU and TT and structure of the Test Requirements Section are pending further analysis + +##### 6.2B.1.6.1 Test purpose + +Same test purpose as in clause 6.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.2B.1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 17 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC along with support for UL-gaps + +##### 6.2B.1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.1.6. + +##### 6.2B.1.6.4 Test description + +Same test description as in clause 6.2.5 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.2.5 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of initial conditions as in clause 6.2.5 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2.5 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.2B.1.6.5 Test requirements + +Same test requirement as in clause 6.2.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.2B.2 UE Maximum Output Power reduction for EN-DC + +#### 6.2B.2.0 General + +The UE maximum output power reduction (MPR) specified in this clause is applicable for UEs configured with EN-DC when NS\_01 is indicated in the MCG and the SCG. The MPR applies subject to indication in the field *modifiedMPRbehavior* for the SCG [2]. + +#### 6.2B.2.1 UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC + +##### 6.2B.2.1.1 Test purpose + +Same test purpose as in clause 6.2.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.2B.2.1.2 Test applicability + +This test case applies to all types of E-UTRA power class 3 and power class 2 UE release 15 and forward, supporting intra-band contiguous EN-DC. + +NOTE: Test execution is not necessary if clause 6.5B.2.1.3 ACLR is executed since MPR requirement is verified in this test case. + +##### 6.2B.2.1.3 Minimum conformance requirements + +###### 6.2B.2.1.3.1 General + +When the UE is configured for intra-band contiguous EN-DC, the UE determines the total allowed maximum output power reduction as specified in this clause. + +For UE supporting dynamic power sharing the following: + +- for the MCG, $MPR_c$ in accordance with TS 36.101 [5] +- for the SCG, + +$$MPR'_c = MPR_{NR} = \text{MAX}(MPR_{\text{single,NR}}, MPR_{\text{ENDC}})$$ + +- for the total configured transmission power, + +$$MPR_{\text{tot}} = P_{\text{PowerClass,EN-DC}} - \min(P_{\text{PowerClass,EN-DC}}, 10 * \log_{10}(10^{(P_{\text{PowerClass,E-UTRA}} - MPR_{\text{E-UTRA}})/10}) + 10^{(P_{\text{PowerClass,NR}} - MPR_{\text{NR}})/10}))$$ + +where + +$$MPR_{\text{E-UTRA}} = \text{MAX}(MPR_{\text{single,E-UTRA}}, MPR_{\text{ENDC}})$$ + +with + +- $MPR_{\text{single,E-UTRA}}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [5] +- $MPR_{\text{single,NR}}$ is the MPR defined for the NR transmission in TS 38.101-1 [2] + +For UEs not supporting dynamic power sharing the following + +- for the MCG, + +$$MPR_c = \text{MAX}(MPR_{\text{single,E-UTRA}}, MPR_{\text{ENDC}})$$ + +- for the SCG, + +$$MPR'_c = \text{MAX}(MPR_{\text{single,NR}}, MPR_{\text{ENDC}})$$ + +where + +- $MPR_{\text{single,NR}}$ is the MPR defined for the NR transmission in TS 38.101-1 [2] +- $MPR_{\text{single,E-UTRA}}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [5] + +$MPR_{\text{ENDC}}$ is defined in Clause 6.2B.2.1.3.2. + +###### 6.2B.2.1.3.2 MPR for power class 3 and power class 2 + +MPR in this subclause is applicable for power class 3 and power class 2 UEs indicating IE *dualPA-Architecture* supported with ENDC power class being the same as the E-UTRA and NR power class, otherwise the UE can use as much MPR as needed to fulfil emissions requirements when scheduled with dual uplink transmission. For UEs scheduled with single uplink transmission, MPR in subclause 6.2.4 of TS 36.101 [5] and 6.2.2 of TS 38.101-1 [2] apply. For a UE supporting dynamic power sharing for DC\_(n)71AA for which dual simultaneous uplink transmissions are mandatory and A-MPR defined in subclause 6.2B.3.1.1 is applied as MPR. The allowed maximum output power reduction for IM3 related emissions applied to transmission on the MCG and the SCG is defined as follows: + +$$MPR_{\text{ENDC}} = M_A$$ + +Where $M_A$ is defined as follows + +$$\begin{aligned} M_A = \quad & 15; & 0 \leq B < 0.5 \\ & 10; & 0.5 \leq B < 1.0 \\ & 8; & 1.0 \leq B < 2.0 \\ & 6; & 2.0 < B \end{aligned}$$ + +Where: + +For UEs supporting dynamic power sharing, + +$$B = (L_{\text{CRB\_alloc,E-UTRA}} * 12 * SCS_{\text{E-UTRA}} + L_{\text{CRB\_alloc,NR}} * 12 * SCS_{\text{NR}}) / 1,000,000$$ + +For UEs not supporting dynamic power sharing, + +For E-UTRA + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{NR}} = 15$ kHz is assumed in calculation of B. + +For NR + +$$B = (12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{E-UTRA}} = 15$ kHz is assumed in calculation of B. + +and $M_A$ is reduced by 1 dB for $B < 2$ . + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.2.1. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR. LTE anchor agnostic approach is not applied for this case. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +No exception requirements for NR or E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that supports dynamic power sharing. LTE anchor agnostic approach is not applied for this case based on the test point analysis in TS 38.905 [7]. + +##### 6.2B.2.1.4 Test description + +###### 6.2B.2.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and test channel bandwidths based on NR operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.4B.2.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521.1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.2.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | | | +|-------------------------------------------------------------------------|---------|---------|---------|------------------------|-------------------------------------------------------------------|------------------------|----------------------|------------------------|------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1. | | | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1. | | | | | Low range, High range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1. | | | | | Lowest N RB_agg , Highest N RB_agg (Note 2) | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1. | | | | | Lowest, Highest (NOTE 10) | | | | | +| Test Parameters | | | | | | | | | | +| Test ID | Freq | ChBw | SCS | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | | | | E-UTRA Cell | | NR Cell | | Common Power config (NOTE 8) | +| | | | | | Modulation | RB allocation (Note 5) | Modulation | RB allocation (NOTE 1) | | +| 1 | Default | Default | Default | N/A | 16QAM | Outer_Full | DFT-s-OFDM Pi/2 BPSK | Outer_Full | B | +| 2 (Note 3) | Default | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | B | +| 3 (Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 4 (Note 3) | High | | | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | A | +| 5 (Note 4) | Default | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | B | +| 6 (Note 4) | Low | | | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | A | +| 7 (Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 8 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM QPSK | Outer_Full | B | +| 9 (Note 3) | Default | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | Edge_1RB_Right | B | +| 10 (Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | N/A | A | +| 11 (Note 3) | High | | | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Right | A | +| 12 (Note 4) | Default | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | Edge_1RB_Left | B | +| 13 (Note 4) | Low | | | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Left | A | +| 14 (Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | N/A | A | +| 15 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 16QAM | Outer_Full | B | +| 16 (Note 3) | Default | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | Edge_1RB_Right | B | +| 17 (Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | N/A | A | + +| | | | | | | | | | | +|----------------|---------|--|--|--|-------|-----------------|-------------------|----------------|---| +| 18
(Note 3) | High | | | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Right | A | +| 19
(Note 4) | Default | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | Edge_1RB_Left | B | +| 20
(Note 4) | Low | | | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Left | A | +| 21
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | N/A | A | +| 22 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 64QAM | Outer_Full | B | +| 23
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 64QAM | Edge_1RB_Right | B | +| 24
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 64QAM | Edge_1RB_Left | B | +| 25 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 256QAM | Outer_Full | B | +| 26
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 256QAM | Edge_1RB_Right | B | +| 27
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 256QAM | Edge_1RB_Left | B | +| 28 | Default | | | | 16QAM | Outer_Full | CP-OFDM QPSK | Outer_Full | B | +| 29
(Note 3) | Default | | | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Right | B | +| 30
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | N/A | A | +| 31
(Note 3) | High | | | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Right | A | +| 32
(Note 4) | Default | | | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | Edge_1RB_Left | B | +| 33
(Note 4) | Low | | | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Left | A | +| 34
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | N/A | A | +| 35 | Default | | | | 16QAM | Outer_Full | CP-OFDM 16QAM | Outer_Full | B | +| 36
(Note 3) | Default | | | | 16QAM | Outer_1RB_Left | CP-OFDM 16QAM | Edge_1RB_Right | B | +| 37
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM 16QAM | N/A | A | +| 38
(Note 3) | High | | | | 16QAM | N/A | CP-OFDM 16QAM | Edge_1RB_Right | A | +| 39
(Note 4) | Default | | | | 16QAM | Outer_1RB_Right | CP-OFDM 16QAM | Edge_1RB_Left | B | +| 40
(Note 4) | Low | | | | 16QAM | N/A | CP-OFDM 16QAM | Edge_1RB_Left | A | + +| | | | | | | | | | | +|----------------|---------|--|--|--|-------|-----------------|-------------------|----------------|---| +| 41
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM
16QAM | N/A | A | +| 42 | Default | | | | 16QAM | Outer_Full | CP-OFDM
64QAM | Outer_Full | B | +| 43
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM
64QAM | Edge_1RB_Right | B | +| 44
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM
64QAM | Edge_1RB_Left | B | +| 45 | Default | | | | 16QAM | Outer_Full | CP-OFDM
256QAM | Outer_Full | B | +| 46
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM
256QAM | Edge_1RB_Right | B | +| 47
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM
256QAM | Edge_1RB_Left | B | +| 48
(Note 4) | Default | | | | 16QAM | Edge_Full_Right | CP-OFDM
256QAM | Edge_Full_Left | B | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same $N_{RB\_agg}$ , select the combination to test as follows: + +- Lowest ENBW: NR component with lowest $N_{RB}$ is tested. +- Highest ENBW: NR component with highest $N_{RB}$ is tested. + +NOTE 3: Applicable when E-UTRA cell carrier frequency is lower than NR cell carrier. + +NOTE 4: Applicable when NR cell carrier frequency is lower than E-UTRA cell carrier. + +NOTE 5: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Edge\_Full\_Right is defined as 2 RBs allocated at the right edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. + +NOTE 6: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in FR1 + +NOTE 7: Test IDs with simultaneous E-UTRA and NR UL transmission only apply for UEs indicating dualPA-Architecture. + +NOTE 8: Power config as specified in Table 6.2B.2.1.4.3-3 and Table 6.2B.2.1.4.3-4 for PC3 UE or Table 6.2B.2.1.4.3-5 and Table 6.2B.2.1.4.3-6 for PC2 UE. + +NOTE 9: Test IDs with simultaneous E-UTRA and NR UL transmission don't apply to DC\_(n)71AA for a UE supporting dynamic power sharing (A-MPR is applied as MPR and covered by 6.2B.3.1.1). + +NOTE 10: For DC\_(n)71AA, only NR SCS of 15 kHz is tested. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. NR downlink signals are initially set up according to Annex C.0, C.1, and C.2 and uplink signals according to Annex G.0, G.1, G.2, and G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.2.1.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.2.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.2B.2.1.4.1-1 on E-UTRA CC and NR CC respectively. For test points configured with message in Table 6.2B.2.1.4.3-7, NR SS only schedules UL RMC on NR slots that does not overlap with E-UTRA uplink subframe. Since the UL has no payload and no loopback data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command starting in this step for the UE to reach $P_{UMAX}$ level. +3. For a UE supporting dynamic power sharing, measure the mean power over all component carriers. For a UE not supporting dynamic power sharing, measure the power of each component carrier individually. For the tested EN-DC configuration, the requirements described in clause 6.2B.2.1.5 shall be met. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). For TDD slots with transient periods are not under test. +4. For UEs supporting Power Class 2, repeat steps 1~3 for Test ID 2 and 4 in Table 6.2B.2.1.4.1-1 on the applicable bands with message exception defined in Table 6.2B.2.1.4.3-7. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.2B.2.1.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.2.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1 with the following exceptions: + +**Table 6.2B.2.1.4.3-1: AdditionalSpectrumEmission for MCG** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.4.3.3-1 | | | | +|------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 0 (NS_01) | | | + +**Table 6.2B.2.1.4.3-2: AdditionalSpectrumEmission for SCG** + +| Derivation Path: 38.508-1 [5] clause 4.6.3, Table 4.6.3-1 | | | | +|-----------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 0 (NS_01) | | | + +**Table 6.2B.2.1.4.3-3: PhysicalCellGroupConfig for PC3** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | + +NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. +NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. + +**Table 6.2B.2.1.4.3-4: RRCConnectionReconfiguration: nr-Config-r15 for PC3** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.2B.2.1.4.3-5: PhysicalCellGroupConfig for PC2** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.2B.2.1.4.3-6: RRCConnectionReconfiguration: nr-Config-r15 for PC2** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**6.2B.2.1.4.3-7: RRCConnectionReconfiguration: p-MaxUE-FR1-r15 (step 4 in 6.2B.2.1.4.2)** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 2 UE | +| } | | | | + +**Table 6.2B.2.1.4.3-8: RRCConnectionReconfiguration: tdm-PatternConfig if operating on FDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 ::= CHOICE{ | | | Power config A (NOTE 1) | +| setup ::= SEQUENCE { | | Apply if operating on FDD band for a UE NOT indicating support of dynamicPowerSharing in the UE-MRDC-Capability IE according to TS 38.213 [x] clause 7.6.1 | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. + +**6.2B.2.1.4.3-9: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +##### 6.2B.2.1.5 Test requirement + +The maximum output power, derived in step 3 shall be within the range prescribed by the UE Power Class, the nominal maximum output power and tolerance in Table 6.2B.2.1.5-1 ~ Table 6.2B.2.1.5-6a. + +The maximum output power, derived in step 4 shall be within the range prescribed by Power Class 3, the nominal maximum output power and tolerance in Table 6.2B.2.1.5-1 ~ Table 6.2B.2.1.5-3a. + +**Table 6.2B.2.1.5-1: UE Power Class 3 test requirements, UE supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|-------------------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 3.0 | 20.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 14.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15 | 11.0 | 12.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 6.0 - TT | +| | 30, 60 | 6.0 | 17.0 | 23.0 | 5.0 | 2.0 | 25.0 + TT | 12.0 - TT | +| 48 (NOTE 3) | 15 | 7.0 | 16.0 | 23.0 | 5.0 | 2.0 | 25.0 + TT | 11.0 - TT | +| | 30, 60 | 5.0 | 18.0 | 23.0 | 5.0 | 2.0 | 25.0 + TT | 13.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.1.5-2: UE Power Class 3 test requirements, UE with/without supporting dynamic power sharing, E-UTRA UL transmission not overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MPR (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L (dB)) | T HIGH (P CMAX, H (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|----------------------------|----------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (NOTE 1) | N/A | 1.0 | 22.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.0 - TT | +| 4, 6 (NOTE 2) | 15, 30, 60 | 3.5 | 19.5 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 17.5 - TT | +| 11, 13 (NOTE 2) | 15, 30, 60 | 1 | 22.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.0 - TT | +| 18, 20 (NOTE 2) | 15, 30, 60 | 2 | 21.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 19.0 - TT | +| 31, 33, 38, 40 (NOTE 2) | 15, 30, 60 | 3 | 20.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 18.0 - TT | + +NOTE 1: Test configuration IDs without transmission overlap with E-UTRA allocation, MPR requirements in TS 36.101 [4] apply. +NOTE 2: Test configuration IDs without transmission overlap with NR allocation, MPR requirements in TS 38.101-1 [2] apply. + +**Table 6.2B.2.1.5-3: UE Power Class 3 E-UTRA carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MCG MPR c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L (dB)) | T HIGH (P CMAX, H (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|---------------------------|----------------------------|----------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 6.0 | 17.0 | 20.0 | 5.0 | 2.5 | 22.5 + TT | 12.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 14.0 | 9.0 | 20.0 | 6.0 | 2.5 | 22.5 + TT | 3.0 - TT | +| 48 (NOTE 3) | 15, 30, 60 | 9.0 | 14.0 | 20.0 | 5.0 | 2.5 | 22.5 + TT | 9.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.1.5-3a: UE Power Class 3 NR carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | SCG MPR' c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|----------------------------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 6.0 | 17.0 | 20.0 | 5.0 | 2.5 | 22.5 + TT | 12.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15 | 14.0 | 9.0 | 20.0 | 6.0 | 2.5 | 22.5 + TT | 3.0 - TT | +| | 30, 60 | 9.0 | 14.0 | 20.0 | 5.0 | 2.5 | 22.5 + TT | 9.0 - TT | +| 48 (NOTE 3) | 15, 30 | 9.0 | 14.0 | 20.0 | 5.0 | 2.5 | 22.5 + TT | 9.0 - TT | +| | 60 | 7.0 | 16.0 | 20.0 | 5.0 | 2.5 | 22.5 + TT | 11.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.1.5-4: UE Power Class 2 test requirements, UE supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|-------------------------|---------------------------------|---------------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 3.0 | 23.0 | 26.0 | 3.0 | 2.0 | 28.0 + TT | 20.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15 | 11.0 | 15.0 | 26.0 | 6.0 | 2.0 | 28.0 + TT | 9.0 - TT | +| | 30, 60 | 6.0 | 20.0 | 26.0 | 6.0 | 2.0 | 28.0 + TT | 14.0 - TT | +| 48 (NOTE 3) | 15 | 7.0 | 19.0 | 26.0 | 5.0 | 2.0 | 28.0 + TT | 14.0 - TT | +| | 30, 60 | 5.0 | 21.0 | 26.0 | 5.0 | 2.0 | 28.0 + TT | 16.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.1.5-5: UE Power Class 2 test requirements, UE with/without supporting dynamic power sharing, E-UTRA UL transmission not overlapping with NR UL transmission (Rel-15 UE indicates PC2 on NR band Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by $\text{powerClassNRPart-r16}$ ))** + +| Configuration ID | Test SCS (kHz) | MPR (dB) | $P_{\text{CMAX, L}}$ (dBm) | $P_{\text{CMAX, H}}$ (dBm) | $T_{\text{LOW}}$ ( $P_{\text{CMAX, L}}$ (dB)) | $T_{\text{HIGH}}$ ( $P_{\text{CMAX, H}}$ (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (NOTE 1) | N/A | 1.0 | 25.0 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 23.0 - TT | +| 4, 6 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | +| 11, 13 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | +| 18, 20 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | +| 31,33, 38, 40 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | + +NOTE 1: Test configuration IDs without transmission overlap with E-UTRA allocation, MPR requirements in TS 36.101 [4] apply. + +NOTE 2: Test configuration IDs without transmission overlap with NR allocation, MPR requirements in TS 38.101-1 [2] apply. + +**Table 6.2B.2.1.5-5a: UE Power Class 2 test requirements, UE with/without supporting dynamic power sharing, E-UTRA UL transmission not overlapping with NR UL transmission (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by $\text{powerClassNRPart-r16}$ ))** + +| Configuration ID | Test SCS (kHz) | MPR (dB) | $P_{\text{CMAX, L}}$ (dBm) | $P_{\text{CMAX, H}}$ (dBm) | $T_{\text{LOW}}$ ( $P_{\text{CMAX, L}}$ (dB)) | $T_{\text{HIGH}}$ ( $P_{\text{CMAX, H}}$ (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (NOTE 1) | N/A | 1.0 | 25.0 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 23.0 - TT | +| 4, 6 (NOTE 2) | 15, 30, 60 | 0.5 | 22.5 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.5 - TT | +| 11, 13 (NOTE 2) | 15, 30, 60 | 1.0 | 22.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.0 - TT | +| 18, 20 (NOTE 2) | 15, 30, 60 | 2.0 | 21.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 19.0 - TT | +| 31,33, 38, 40 (NOTE 2) | 15, 30, 60 | 3.0 | 20.0 | 23.0 | 2.5 | 2.0 | 25.0 + TT | 17.5 - TT | + +NOTE 1: Test configuration IDs without transmission overlap with NR allocation, MPR requirements in TS 36.101 [4] apply. + +NOTE 2: Test configuration IDs without transmission overlap with E-UTRA allocation, MPR requirements in TS 38.101-1 [2] apply. + +**Table 6.2B.2.1.5-6: UE Power Class 2 E-UTRA carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MCG MPR c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|---------------------------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 6.0 | 20.0 | 23.0 | 2.5 | 2.0 | 25.0 + TT | 17.5 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 14.0 | 12.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 6.0 - TT | +| 48 (NOTE 3) | 15, 30, 60 | 9.0 | 17.0 | 23.0 | 5.0 | 2.0 | 25.0 + TT | 12.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.1.5-6a: UE Power Class 2 NR carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | SCG MPR' c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|----------------------------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 6.0 | 20.0 | 23.0 | 2.5 | 2.0 | 25.0 + TT | 17.5 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15 | 14.0 | 12.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 6.0 - TT | +| | 30, 60 | 9.0 | 17.0 | 23.0 | 5.0 | 2.0 | 25.0 + TT | 12.0 - TT | +| 48 (NOTE 3) | 15, 30 | 9.0 | 17.0 | 23.0 | 5.0 | 2.0 | 25.0 + TT | 12.0 - TT | +| | 60 | 7.0 | 19.0 | 23.0 | 3.5 | 2.0 | 25.0 + TT | 15.5 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.1.5-7: Test Tolerance** + +| | f ≤ 3.0GHz | 3.0GHz < f ≤ 6GHz | +|-----------------------|------------|-------------------| +| ENBW ≤ 40MHz | 0.7 dB | 1.0 dB | +| 40MHz < ENBW ≤ 100MHz | 1.0 dB | 1.0 dB | + +#### 6.2B.2.2 UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC + +##### 6.2B.2.2.1 Test purpose + +Same test purpose as in clause 6.2B.2.1.1. + +##### 6.2B.2.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +NOTE: Test execution is not necessary if clause 6.5B.2.2.3 ACLR is executed since MPR requirement is verified in this test case. + +##### 6.2B.2.2.3 Minimum conformance requirements + +###### 6.2B.2.2.3.1 General + +When the UE is configured for intra-band non-contiguous EN-DC, the UE determines the total allowed maximum output power reduction as specified in this subclause. + +For UE supporting dynamic power sharing the following: + +- for the MCG, $MPR_c$ in accordance with TS 36.101 [4] +- for the SCG, + +$$MPR'_c = MPR_{NR} = \text{MAX}(MPR_{\text{single},NR}, MPR_{\text{ENDC}})$$ + +- for the total configured transmission power, + +$$MPR_{\text{tot}} = P_{\text{PowerClass,EN-DC}} - \min(P_{\text{PowerClass,EN-DC}}, 10 * \log_{10}(10^{(P_{\text{PowerClass,E-UTRA}} - MPR_{\text{E-UTRA}})/10)} + 10^{(P_{\text{PowerClass,NR}} - MPR_{\text{NR}})/10}))$$ + +where + +$$MPR_{\text{E-UTRA}} = \text{MAX}(MPR_{\text{single},E-UTRA}, MPR_{\text{ENDC}})$$ + +with + +- $MPR_{\text{single},E-UTRA}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [4] +- $MPR_{\text{single},NR}$ is the MPR defined for the NR transmission in TS 38.101-1 [2] + +For UEs not supporting dynamic power sharing the following + +- for the MCG, + +$$MPR_c = \text{MAX}(MPR_{\text{single},E-UTRA}, MPR_{\text{ENDC}})$$ + +- for the SCG, + +$$MPR'_c = \text{MAX}(MPR_{\text{single},NR}, MPR_{\text{ENDC}})$$ + +where + +- $MPR_{\text{single},NR}$ is the MPR defined for the NR transmission in TS 38.101-1 [2] +- $MPR_{\text{single},E-UTRA}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [4] + +$MPR_{\text{ENDC}}$ is defined in Clause 6.2B.2.2.3.2. + +###### 6.2B.2.2.3.2 MPR for power class 3 and power class 2 + +MPR in this subclause is applicable for power class 3 and power class 2 UEs indicating IE *dualPA-Architecture* supported with ENDC power class being the same as the E-UTRA and NR power class, otherwise the UE can use as much MPR as needed to fulfil emissions requirements when scheduled with dual uplink transmission. For UEs scheduled with single uplink transmission, MPR in subclause 6.2.4 of TS 36.101 [5] and 6.2.3 of TS 38.101-1 [2] apply. The allowed maximum output power reduction for IM3 related emissions applied to transmission on the MCG and the SCG is defined as follows: + +$$MPR_{\text{ENDC}} = M_A$$ + +Where $M_A$ is defined as follows + +$$\begin{aligned} M_A = \quad & 18 \ ; \quad 0 \leq B < 1.0 \\ & 17 \ ; \quad 1.0 \leq B < 2.0 \\ & 16 \ ; \quad 2.0 \leq B < 5.0 \\ & 15 \ ; \quad 5.0 \leq B \end{aligned}$$ + +Where: + +For UEs supporting dynamic power sharing, + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +For UEs not supporting dynamic power sharing, + +For E-UTRA + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{NR}} = 15$ kHz is assumed in calculation of B. + +For NR + +$$B = (12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{E-UTRA}} = 15$ kHz is assumed in calculation of B. + +and $M_A$ is reduced by 1 dB for $B < 2$ . + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.2.2. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA overlap in time with NR. LTE anchor agnostic approach is not applied for this case. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +No exception requirements for NR or E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR. LTE anchor agnostic approach is not applied for this case based on the test point analysis in TS 38.905 [7]. + +6.2B.2.2.4 Test description + +6.2B.2.2.4.1 Initial conditions + +Same initial conditions as described in clause 6.2B.2.1.4.1 for both E-UTRA and NR carriers with the following exception: + +- Instead of Table 6.2B.2.1.4.1-1 --> use Table 6.2B.2.2.4.1-1. + +**Table 6.2B.2.2.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | | | | | | | +|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|------|-----|------------------------|-----------------------------------|------------------------|----------------|------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1. | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | | | +| Test Frequencies as specified in TS 38.508 [7] clause 4.3.1 for different DC bandwidth classes | Low with maxWgap (NR low – E-UTRA high);
High with maxWgap (E-UTRA low – NR high) | | | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1. | Lowest N RB_agg , Highest N RB_agg
(Note 2) | | | | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1. | Lowest, Highest | | | | | | | | | +| Test Parameters | | | | | | | | | | +| Test ID | Freq | ChBw | SCS | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | | | | E-UTRA Cell | | NR Cell | | Common | +| | | | | | Modulation | RB allocation (Note 3) | Modulation | RB allocation (NOTE 1) | Power config (NOTE 6) | + +| | | | | | | | | | | +|----|---------|---------|---------|-----|-------|-----------------|----------------------|----------------|---| +| 1 | Default | Default | Default | N/A | QPSK | Outer_Full | DFT-s-OFDM Pi/2 BPSK | Outer_Full | B | +| 2 | High | | | | QPSK | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | B | +| 3 | High | | | | QPSK | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 4 | High | | | | QPSK | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | A | +| 5 | Low | | | | QPSK | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | B | +| 6 | Low | | | | QPSK | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | A | +| 7 | Low | | | | QPSK | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 8 | Default | | | | QPSK | Outer_Full | DFT-s-OFDM QPSK | Outer_Full | B | +| 9 | High | | | | QPSK | Outer_1RB_Left | DFT-s-OFDM QPSK | Edge_1RB_Right | B | +| 10 | High | | | | QPSK | Outer_1RB_Left | DFT-s-OFDM QPSK | N/A | A | +| 11 | High | | | | QPSK | N/A | DFT-s-OFDM QPSK | Edge_1RB_Right | A | +| 12 | Low | | | | QPSK | Outer_1RB_Right | DFT-s-OFDM QPSK | Edge_1RB_Left | B | +| 13 | Low | | | | QPSK | N/A | DFT-s-OFDM QPSK | Edge_1RB_Left | A | +| 14 | Low | | | | QPSK | Outer_1RB_Right | DFT-s-OFDM QPSK | N/A | A | +| 15 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 16QAM | Outer_Full | B | +| 16 | High | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | Edge_1RB_Right | B | +| 17 | High | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | N/A | A | +| 18 | High | | | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Right | A | +| 19 | Low | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | Edge_1RB_Left | B | +| 20 | Low | | | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Left | A | +| 21 | Low | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | N/A | A | +| 22 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 64QAM | Outer_Full | B | + +| | | | | | | | | | | +|----|---------|--|--|--|-------|-----------------|-------------------|----------------|---| +| 23 | High | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 64QAM | Edge_1RB_Right | B | +| 24 | Low | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 64QAM | Edge_1RB_Left | B | +| 2 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 256QAM | Outer_Full | B | +| 26 | High | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 256QAM | Edge_1RB_Right | B | +| 27 | Low | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 256QAM | Edge_1RB_Left | B | +| 28 | Default | | | | QPSK | Outer_Full | CP-OFDM QPSK | Outer_Full | B | +| 29 | High | | | | QPSK | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Right | B | +| 30 | High | | | | QPSK | Outer_1RB_Left | CP-OFDM QPSK | N/A | A | +| 31 | High | | | | QPSK | N/A | CP-OFDM QPSK | Edge_1RB_Right | A | +| 32 | Low | | | | QPSK | Outer_1RB_Right | CP-OFDM QPSK | Edge_1RB_Left | B | +| 33 | Low | | | | QPSK | N/A | CP-OFDM QPSK | Edge_1RB_Left | A | +| 34 | Low | | | | QPSK | Outer_1RB_Right | CP-OFDM QPSK | N/A | A | +| 3 | Default | | | | 16QAM | Outer_Full | CP-OFDM 16QAM | Outer_Full | B | +| 36 | High | | | | 16QAM | Outer_1RB_Left | CP-OFDM 16QAM | Edge_1RB_Right | B | +| 37 | High | | | | 16QAM | Outer_1RB_Left | CP-OFDM 16QAM | N/A | A | +| 38 | High | | | | 16QAM | N/A | CP-OFDM 16QAM | Edge_1RB_Right | A | +| 39 | Low | | | | 16QAM | Outer_1RB_Right | CP-OFDM 16QAM | Edge_1RB_Left | B | +| 40 | Low | | | | 16QAM | N/A | CP-OFDM 16QAM | Edge_1RB_Left | A | +| 41 | Low | | | | 16QAM | Outer_1RB_Right | CP-OFDM 16QAM | N/A | A | +| 42 | Default | | | | 16QAM | Outer_Full | CP-OFDM 64QAM | Outer_Full | B | +| 43 | High | | | | 16QAM | Outer_1RB_Left | CP-OFDM 64QAM | Edge_1RB_Right | B | +| 44 | Low | | | | 16QAM | Outer_1RB_Right | CP-OFDM 64QAM | Edge_1RB_Left | B | +| 45 | Default | | | | 16QAM | Outer_Full | CP-OFDM 256QAM | Outer_Full | B | +| 46 | High | | | | 16QAM | Outer_1RB_Left | CP-OFDM 256QAM | Edge_1RB_Right | B | +| 47 | Low | | | | 16QAM | Outer_1RB_Right | CP-OFDM 256QAM | Edge_1RB_Left | B | +| 48 | Low | | | | 16QAM | Edge_Full_Right | CP-OFDM 256QAM | Edge_Full_Left | B | + +- NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +- NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same $N_{RB\_agg}$ , select the combination to test as follows: +- Lowest ENBW: NR component with lowest $N_{RB}$ is tested. + - Highest ENBW: NR component with highest $N_{RB}$ is tested. +- NOTE 3: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Edge\_Full\_Right is defined as 2 RBs allocated at the right edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. +- NOTE 4: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in FR1 +- NOTE 5: Test IDs with simultaneous E-UTRA and NR UL transmission only apply for UEs indicating dualPA-Architecture. +- NOTE 6: Power config as specified in Table 6.2B.2.1.4.3-3 and Table 6.2B.2.1.4.3-4 for PC3 UE or Table 6.2B.2.1.4.3-5 and Table 6.2B.2.1.4.3-6 for PC2 UE. + +###### 6.2B.2.2.4.2 Test procedure + +Same test procedure as described in clause 6.2B.2.1.4.2. + +###### 6.2B.2.2.4.3 Message contents + +Same message contents as in clause 6.2B.2.1.4.3. + +##### 6.2B.2.2.5 Test requirement + +The maximum output power, derived in step 3 shall be within the range prescribed by the nominal maximum output power and tolerance in Table 6.2B.2.2.5-1 ~ Table 6.2B.2.2.5-8a. + +**Table 6.2B.2.2.5-1: UE Power Class 3 test requirements, UE supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|-------------------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 12.0 | 11.0 | 23.0 | 6.0 | 4.0 | 27.0 + TT | 5.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 15.0 | 8.0 | 23.0 | 7.0 | 4.0 | 27.0 + TT | 1.0 - TT | +| 48 (NOTE 3) | 15 | 14.0 | 9.0 | 23.0 | 7.0 | 4.0 | 27.0 + TT | 2.0 - TT | +| | 30, 60 | 13.0 | 10.0 | 23.0 | 7.0 | 4.0 | 27.0 + TT | 3.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.2.5-2: UE Power Class 3 test requirements, UE with/without supporting dynamic power sharing, E-UTRA UL transmission not overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MPR (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L (dB)) | T HIGH (P CMAX, H (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|----------------------------|----------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (NOTE 1) | 15, 30, 60 | 1.0 | 22.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.0 - TT | +| 4, 6 (NOTE 2) | 15, 30, 60 | 3.5 | 19.5 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 17.5 - TT | +| 11, 13 (NOTE 2) | 15, 30, 60 | 1 | 22.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.0 - TT | +| 18, 20 (NOTE 2) | 15, 30, 60 | 2 | 21.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 19.0 - TT | +| 31, 33, 38, 40 (NOTE 2) | 15, 30, 60 | 3 | 20.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 18.0 - TT | + +NOTE 1: Test configuration IDs without transmission overlap with E-UTRA allocation, MPR requirements in TS 36.101 [4] apply. + +NOTE 2: Test configuration IDs without transmission overlap with NR allocation, MPR requirements in TS 38.101-1 [2] apply. + +**Table 6.2B.2.2.5-3: UE Power Class 3 E-UTRA carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MCG MPR c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L (dB)) | T HIGH (P CMAX, H (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|---------------------------|----------------------------|----------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 15.0 | 8.0 | 20.0 | 6.0 | 2.5 | 22.5 + TT | 2.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 17.0 | 6.0 | 20.0 | 7.0 | 2.5 | 22.5 + TT | -1.0 - TT | +| 48 (NOTE 3) | 15, 30, 60 | 17.0 | 6.0 | 20.0 | 7.0 | 2.5 | 22.5 + TT | -1.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.2.5-3a: UE Power Class 3 NR carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | SCG MPR' c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|----------------------------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 15.0 | 8.0 | 20.0 | 6.0 | 2.5 | 22.5 + TT | 2.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 17.0 | 6.0 | 20.0 | 7.0 | 2.5 | 22.5 + TT | -1.0 - TT | +| 48 (NOTE 3) | 15, 30 | 17.0 | 6.0 | 20.0 | 7.0 | 2.5 | 22.5 + TT | -1.0 - TT | +| | 60 | 16.0 | 7.0 | 20.0 | 7.0 | 2.5 | 22.5 + TT | - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.2.5-4: Void** + +**Table 6.2B.2.2.5-5: UE Power Class 2 test requirements, UE supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|-------------------------|---------------------------------|---------------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 12.0 | 14.0 | 26.0 | 6.0 | 4.0 | 30.0 + TT | 8.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 15.0 | 11.0 | 26.0 | 6.0 | 4.0 | 30.0 + TT | 5.0 - TT | +| 48 (NOTE 3) | 15 | 14.0 | 12.0 | 26.0 | 6.0 | 4.0 | 30.0 + TT | 6.0 - TT | +| | 30, 60 | 13.0 | 13.0 | 26.0 | 6.0 | 4.0 | 30.0 + TT | 7.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.2.5-6: UE Power Class 2 test requirements, UE with/without supporting dynamic power sharing, E-UTRA UL transmission not overlapping with NR UL transmission (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by $\text{powerClassNRPart-r16}$ ))** + +| Configuration ID | Test SCS (kHz) | MPR (dB) | $P_{\text{CMAX, L}}$ (dBm) | $P_{\text{CMAX, H}}$ (dBm) | $T_{\text{LOW}}$ ( $P_{\text{CMAX, L}}$ (dB)) | $T_{\text{HIGH}}$ ( $P_{\text{CMAX, H}}$ (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (NOTE 1) | 15, 30, 60 | 1.0 | 25.0 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 23.0 - TT | +| 4, 6 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | +| 11, 13 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | +| 18, 20 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | +| 31, 33, 38, 40 (NOTE 2) | 15, 30, 60 | 3.5 | 22.5 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 20.5 - TT | + +NOTE 1: Test configuration IDs without transmission overlap with E-UTRA allocation, MPR requirements in TS 36.101 [4] apply. + +NOTE 2: Test configuration IDs without transmission overlap with NR allocation, MPR requirements in TS 38.101-1 [2] apply. + +**Table 6.2B.2.2.5-6a: UE Power Class 2 test requirements, UE with/without supporting dynamic power sharing, E-UTRA UL transmission not overlapping with NR UL transmission (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by $\text{powerClassNRPart-r16}$ ))** + +| Configuration ID | Test SCS (kHz) | MPR (dB) | $P_{\text{CMAX, L}}$ (dBm) | $P_{\text{CMAX, H}}$ (dBm) | $T_{\text{LOW}}$ ( $P_{\text{CMAX, L}}$ (dB)) | $T_{\text{HIGH}}$ ( $P_{\text{CMAX, H}}$ (dB)) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (NOTE 1) | 15, 30, 60 | 1.0 | 25.0 | 26.0 | 2.0 | 2.0 | 28.0 + TT | 23.0 - TT | +| 4, 6 (NOTE 2) | 15, 30, 60 | 0.5 | 22.5 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.5 - TT | +| 11, 13 (NOTE 2) | 15, 30, 60 | 1.0 | 22.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 20.0 - TT | +| 18, 20 (NOTE 2) | 15, 30, 60 | 2.0 | 21.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 19.0 - TT | +| 31, 33, 38, 40 (NOTE 2) | 15, 30, 60 | 3.0 | 20.0 | 23.0 | 2.0 | 2.0 | 25.0 + TT | 17.5 - TT | + +NOTE 1: Test configuration IDs without transmission overlap with E-UTRA allocation, MPR requirements in TS 36.101 [4] apply. + +NOTE 2: Test configuration IDs without transmission overlap with NR allocation, MPR requirements in TS 38.101-1 [2] apply. + +**Table 6.2B.2.2.5-7: UE Power Class 2 E-UTRA carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | MCG MPR c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|---------------------------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 15.0 | 11.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 5.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 17.0 | 9.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 3.0 - TT | +| 48 (NOTE 3) | 15, 30, 60 | 17.0 | 9.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 3.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.2.5-7a: UE Power Class 2 NR carrier test requirements, UE not supporting dynamic power sharing, E-UTRA UL transmission overlapping with NR UL transmission** + +| Configuration ID | Test SCS (kHz) | SCG MPR c (dB) | P CMAX, L (dBm) | P CMAX, H (dBm) | T LOW (P CMAX, L ) (dB) | T HIGH (P CMAX, H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------|----------------|---------------------------|----------------------------|----------------------------|-----------------------------------------------|------------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (NOTE 1) | 15, 30, 60 | 15.0 | 11.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 5.0 - TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (NOTE 2) | 15, 30, 60 | 17.0 | 9.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 3.0 - TT | +| 48 (NOTE 3) | 15, 30 | 17.0 | 9.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 3.0 - TT | +| | 60 | 16.0 | 10.0 | 23.0 | 6.0 | 2.0 | 25.0 + TT | 4.0 - TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +**Table 6.2B.2.2.5-8: Void** + +**Table 6.2B.2.2.5-8a: Void** + +**Table 6.2B.2.2.5-9: Test Tolerance for UE maximum output power (Combined measurements of E-UTRA and NR CCs)** + +| TT for overall output power | | | | | | | | | | | | +|-----------------------------|------------|---------------------|------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------| +| | | | NR | | | | | | | | | +| | | | BW ≤ 20MHz | | | 20 MHz < BW ≤ 40MHz | | | 40MHz < BW ≤ 100MHz | | | +| | | | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | +| E-UTRA | BW ≤ 20MHz | f ≤ 3.0GHz | 0.7 dB | 1.0 dB | 1.0 dB | 0.7 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | +| | | 3.0GHz < f ≤ 4.2GHz | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | + +**Table 6.2B.2.2.5-9a: Test Tolerance for UE maximum output power (Separate measurements over E-UTRA and NR CCs)** + +| Uplink TX | | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6GHz | +|-----------|---------------------|------------|---------------------|-------------------| +| E-UTRA | BW ≤ 20MHz | 0.7 dB | 1.0 dB | N/A | +| NR | BW ≤ 40MHz | 0.7 dB | 1.0 dB | 1.0 dB | +| | 40MHz < BW ≤ 100MHz | 1.0 dB | 1.0 dB | 1.0 dB | + +#### 6.2B.2.3 UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 (1 NR CC) + +##### 6.2B.2.3.1 Test purpose + +Same test purpose as in clause 6.2.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.2B.2.3.2 Test applicability + +The requirements of this test apply to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +NOTE: Test execution is not necessary if clause 6.5B.2.3.3 ACLR is executed since MPR requirement is verified in this test cases. + +##### 6.2B.2.3.3 Minimum conformance requirements + +For inter-band EN-DC between E-UTRA and NR FR1, UE maximum output power reduction specified in TS 36.101 [5] and TS 38.101-1 [2] apply for E-UTRA and NR respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.2.3. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +##### 6.2B.2.3.4 Test description + +Same test description as in clause 6.2.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.2.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 4.6-1. +- 3.1. Downlink E-UTRA signals are initially set up according to TS 36.521-1 [10] Annex C0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0. + +4.1. The E-UTRA UL Reference Measurement channels are set according to Table 4.6-1. + +Step 6 of Initial conditions as in clause 6.2.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Same test procedure as in clause 6.2.2.4.2 in TS 38.521-1 [8]. + +##### 6.2B.2.3.5 Test requirement + +For PC3 UE, same test requirement as in clause 6.2.2.5 in TS 38.521-1 [8]. + +For PC2 UE (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by *powerClassNRPart-r16*), same test requirement for PC2 UE as in clause 6.2.2.5 in TS 38.521-1 [8]. For PC2 UE (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by *powerClassNRPart-r16*), same test requirement for PC3 UE as in clause 6.2.2.5 in TS 38.521-1 [8]. + +##### 6.2B.2.3.a UE Maximum Output Power reduction for Inter-Band NE-DC within FR1 (1 NR CC) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier in this test case are tested in 6.2.2 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.2.3 and 6.2.3A of TS 36.521-1 [10]. Neither NR carrier nor LTE carrier(s) needs to be tested again. + +#### 6.2B.2.4 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) + +**Editor's note:** Following aspects are missing or under discussion + +- The referred test case 6.2.2 in TS 38.521-2 [9] is incomplete for PC2 and PC4. + +##### 6.2B.2.4.1 Test purpose + +To verify that the error of the UE maximum output power does not exceed the range prescribed by the specified maximum output power with MPR and tolerance. + +An excess maximum output power has the possibility to interfere to other channels or other systems. A small maximum output power decreases the coverage area. + +##### 6.2B.2.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.2B.2.4.3 Minimum conformance requirements + +UE maximum output power reduction requirement for E-UTRA single carrier and CA operation specified in clauses 6.2.3 and 6.2.3A of TS 36.101[5] and for NR single carrier and CA operation specified in clauses 6.2.2, 6.2A.2, and 6.2D.2 of TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.2.4. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.2B.2.4.4 Test description + +###### 6.2B.2.4.4.1 Initial conditions + +Same test description as in clause 6.2.2.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 4.7-1. +- 3.1. Downlink E-UTRA signals are initially set up according to TS 36.521-1 [10] Annex C, clauses C.0, C.1 and C.3.0, and uplink signals according to Annex H, clauses H.1 and H.3.0. +- 4.1. The E-UTRA UL Reference Measurement channels are set according to Table 4.7-1. + +Step 6 of Initial conditions as in clause 6.2.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. + +Same test procedure as in clause 6.2.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.2B.2.4.5 Test requirement + +Same test requirement as in clause 6.2.2.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.2B.2.4a UE Maximum Output Power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) + +##### 6.2B.2.4a.1 Test purpose + +Same test purpose as in clause 6.2.2\_1 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.2B.2.4a.2 Test applicability + +This test case applies to: + +- All types of E-UTRA PC3 UE release 15 supporting inter-band EN-DC including FR2 with 1 NR UL CC and *modifiedMPRbehaviour* bit 0 capability (according to Annex P.1 in TS38.521-2 [9]). +- All types of E-UTRA PC3 UE release 16 and forward supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.2B.2.4a.3 Minimum conformance requirements + +UE maximum output power reduction requirement for E-UTRA single carrier and CA operation specified in clauses 6.2.3 and 6.2.3A of TS 36.101[5] and for NR single carrier and CA operation specified in clauses 6.2.2, 6.2A.2, and 6.2D.2 of TS 38.101-2 [3] apply. + +Same minimum conformance requirements as in clause 6.2.2\_1.3 in TS 38.521-2 [9] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.2.4. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.2B.2.4a.4 Test description + +Same test description as in clause 6.2.2\_1.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.2.2\_1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 4.6-1. +- 3.1. Downlink E-UTRA signals are initially set up according to TS 36.521-1 [10] Annex C, clauses C.0, C.1 and C.3.0, and uplink signals according to Annex H, clauses H.1 and H.3.0. +- 4.1. The E-UTRA UL Reference Measurement channels are set according to Table 4.6-1. + +Step 6 of Initial conditions as in clause 6.2.2\_1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. + +Same test procedure as in clause 6.2.2\_1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.2B.2.4a.5 Test requirement + +Same test requirement as in clause 6.2.2\_1.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.2B.2.4D UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) + +**Editor's note:** Following aspects are missing or under discussion + +- The referred test case 6.2D.2 in TS 38.521-2 [9] is incomplete. + +##### 6.2B.2.4D.1 Test purpose + +To verify that the error of the UE maximum output power does not exceed the range prescribed by the specified maximum output power with MPR and tolerance. + +An excess maximum output power has the possibility to interfere to other channels or other systems. A small maximum output power decreases the coverage area. + +##### 6.2B.2.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC with UL MIMO. + +##### 6.2B.2.4D.3 Minimum conformance requirements + +UE maximum output power reduction requirement for E-UTRA single carrier and CA operation specified in clauses 6.2.3 and 6.2.3A of TS 36.101[5] and for NR single carrier and CA operation specified in clauses 6.2.2, 6.2A.2, and 6.2D.2 of TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.2.4. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +##### 6.2B.2.4D.4 Test description + +###### 6.2B.2.4D.4.1 Initial conditions + +Same test description as in clause 6.2D.2.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.2D.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 4.6-1. +- 3.1. Downlink E-UTRA signals are initially set up according to TS 36.521-1 [10] Annex C, clauses C.0, C.1 and C.3.0, and uplink signals according to Annex H, clauses H.1 and H.3.0. +- 4.1. The E-UTRA UL Reference Measurement channels are set according to Table 4.6-1. + +Step 6 of Initial conditions as in clause 6.2D.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. + +Same test procedure as in clause 6.2D.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.2B.2.4.5 Test requirement + +Same test requirement as in clause 6.2D.2.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.2B.2.4\_1 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (>1 NR CC) + +###### 6.2B.2.4\_1.1 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.2.1 in TS 38.521-2 [9] is incomplete for aggregated BW > 400MHz and intra-band non-contiguous CA. +- The referred test case 6.2A.2.1 in TS 38.521-2 [9] is incomplete for power class 1, 2 and 4. + +###### 6.2B.2.4\_1.1.1 Test purpose + +Same test purpose as in clause 6.2.2.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.2B.2.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.2B.2.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2B.2.4.3. + +###### 6.2B.2.4\_1.1.4 Test description + +###### 6.2B.2.4\_1.1.4.1 Initial condition + +Same test description as in clause 6.2A.2.1.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.2.4\_1.1.5 Test Requirements + +Same test requirement as in clause 6.2A.2.1.5 in TS 38.521-2 [9] for the *NR* carriers. + +###### 6.2B.2.4\_1.2 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (3 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.2.2 in TS 38.521-2 [9] is incomplete for aggregated BW > 400MHz and intra-band non-contiguous CA. +- The referred test case 6.2A.2.2 in TS 38.521-2 [9] is incomplete for power class 1, 2 and 4. + +###### 6.2B.2.4\_1.2.1 Test purpose + +Same test purpose as in clause 6.2.2.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.2B.2.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.2B.2.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2B.2.4.3. + +###### 6.2B.2.4\_1.2.4 Test description + +###### 6.2B.2.4\_1.2.4.1 Initial condition + +Same test description as in clause 6.2A.2.2.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.2.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.2.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.2.4\_1.2.5 Test Requirements + +Same test requirement as in clause 6.2A.2.2.5 in TS 38.521-2 [9] for the NR carriers. + +##### 6.2B.2.4\_1.3 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (4 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2A.2.3 in TS 38.521-2 [9] is incomplete for aggregated BW > 400MHz and intra-band non-contiguous CA. +- The referred test case 6.2A.2.3 in TS 38.521-2 [9] is incomplete for power class 1, 2 and 4. + +###### 6.2B.2.4\_1.3.1 Test purpose + +Same test purpose as in clause 6.2.2.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.2B.2.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.2B.2.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2B.2.4.3. + +###### 6.2B.2.4\_1.3.4 Test description + +###### 6.2B.2.4\_1.3.4.1 Initial condition + +Same test description as in clause 6.2A.2.3.4 in TS 38.521-2 [9] for the *NR* carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.2A.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2A.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.2A.2.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.2.4\_1.3.5 Test Requirements + +Same test requirement as in clause 6.2A.2.3.5 in TS 38.521-2 [9] for the *NR* carriers. + +#### 6.2B.2.5 UE Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 + +##### 6.2B.2.5.1 Test purpose + +Same test purpose as in clause 6.2B.2.3.1 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.2B.2.4.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.2B.2.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum output power apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.2B. + +#### 6.2B.2.5D UE Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 for UL MIMO + +##### 6.2B.2.5D.1 Test purpose + +Same test purpose as in clause 6.2D.2.1 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.2D.2.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.2B.2.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum output power apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.2B. + +### 6.2B.3 UE additional maximum output power reduction for EN-DC + +#### 6.2B.3.1 UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC + +Editor's note: + +- Test requirements for non-overlapping transmission of non-DPS UE need further investigation + +##### 6.2B.3.1.1 Test purpose + +Additional emission requirements can be signalled by the network with network signalling value indicated by the field *additionalSpectrumEmission*. To meet these additional requirements, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in Table 6.2B.1.1.3-1. Unless stated otherwise, an A-MPR of 0 dB shall be used. + +##### 6.2B.3.1.2 Test applicability + +The requirements of this test apply in test case 6.5B.2.1.2 Additional spectrum emission mask for network signalled values NS\_04 and NS\_35 to all types of E-UTRA power class 3 and power class 2 UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.2B.3.1.3 Minimum conformance requirements + +For intra-band contiguous EN-DC band combinations with additional requirements the allowed A-MPR is specified in table 6.2B.3.1.3-1 for UEs configured with EN-DC and combinations of network signalling values indicated in the E-UTRA and NR cell groups. + +Unless otherwise stated the A-MPR specified in clause 6.2B.3.1 for intra-band contiguous EN-DC configurations is the total power reduction allowed including MPR. + +**Table 6.2B.3.1.3-1: Additional maximum power reduction for Intra-band contiguous EN-DC** + +| DC configuration | Requirement (subclause) | E-UTRA network signalling value | NR network signalling value | A-MPR (clause) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------------------|-----------------------------|---------------------------| +| DC_(n)71AA | 6.5B.2.1.2.3.1 | NS_35 | NS_35 | 6.2B.3.1.3.1 3 | +| DC_(n)41AA 1 | 6.5B.2.1.2.3.2 | NS_01 or NS_04 | NS_04 | 6.2B.3.1.3.2 4 | +| NOTE 1: Only applies to UEs that support dual UL transmission for this EN-DC combination. | | | | | +| NOTE 2: The additional emission requirement is indicated when the combination of network signalling values in the two CGs is set (only for UEs configured with EN-DC). | | | | | +| NOTE 3: The A-MPR is applied as MPR if NS_35 is not signalled. | | | | | +| NOTE 4: Void. | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.3.1. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA overlap in time with NR. LTE anchor agnostic approach is not applied for this case. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that doesn't support dynamic power sharing. LTE anchor agnostic approach is not applied for this case. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +No exception requirements for NR or E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that supports dynamic power sharing. LTE anchor agnostic approach is not applied for this case. + +###### 6.2B.3.1.3.1 A-MPR for DC\_(n)71AA + +For UE supporting dynamic power sharing the following: + +- for the MCG, $A\text{-MPR}_c$ in accordance with TS 36.101 [5] +- for the SCG, $A\text{-MPR}'_c = [A\text{-MPR}_{\text{DC}}]$ +- for the total configured transmission power, $A\text{-MPR}_{\text{tot}} = A\text{-MPR}_{\text{DC}}$ + +with $A\text{-MPR}_{\text{DC}}$ as defined in this subclause. + +For UEs not supporting dynamic power sharing the following + +- for the MCG, + +$$A\text{-MPR}_c = A\text{-MPR}_{\text{E-UTRA}}$$ + +- for the SCG, + +$$A\text{-MPR}'_c = A\text{-MPR}_{\text{NR}}$$ + +with $A\text{-MPR}_{\text{E-UTRA}}$ and $A\text{-MPR}_{\text{NR}}$ as defined in this subclause. + +For DC\_(n)71AA with configured with network signaling values as per Table 6.2B.3.1.0-1 the allowed A-MPR is defined by + +- for UE indicating support of dynamicPowerSharing in the *UE-MRDC-Capability* IE + +$$A\text{-MPR}_{\text{DC}} = \text{CEIL}\{ M_{\text{A,DC}}(A), 0.5 \}$$ + +where $A\text{-MPR}_{\text{DC}}$ is the total power reduction allowed (dB), + +- for OFDM: + +$$M_{\text{A,DC}} = 11.00 - 11.67 * A; \quad 0.00 < A \leq 0.30$$ + +$$8.10 - 2.00 * A; \quad 0.30 < A \leq 0.80$$ + +$$6.50; \quad 0.80 < A \leq 1.00$$ + +- for DFT-S-OFDM: + +$$M_{\text{A,DC}} = 11.00 - 13.33 * A; \quad 0.00 < A \leq 0.30$$ + +$$8.00 - 3.33 * A; \quad 0.30 < A \leq 0.60$$ + +$$6.00; \quad 0.60 < A \leq 1.00$$ + +where: + +with $L_{\text{CRB,E-UTRA}}$ and $N_{\text{RB,E-UTRA}}$ the number of allocated PRB and transmission bandwidth for MCG, $L_{\text{CRB,NR}}$ and $N_{\text{RB,NR}}$ the number of allocated PRB and transmission bandwidth for SCG with SCS = 15 kHz. + +- for UE not indicating support of dynamicPowerSharing + +$$A\text{-MPR}_{\text{E-UTRA}} = \text{CEIL}\{ M_{\text{A,E-UTRA}}, 0.5 \}$$ + +$$A\text{-MPR}_{\text{NR}} = \text{CEIL}\{ M_{\text{A,NR}}, 0.5 \}$$ + +where A-MPR is the total power reduction allowed per CG with + +Where $L_{\text{CRB,NR}}$ and $N_{\text{RB,NR}}$ the number of allocated PRB and transmission bandwidth for SCG with SCS = 15 kHz. + +###### 6.2B.3.1.3.2 A-MPR for NS\_04 + +###### 6.2B.3.1.3.2.0 General + +When the UE is configured for B41/n41 intra-band contiguous EN-DC and it receives IE NS\_04, the UE determines the total allowed maximum output power reduction as specified in this clause. The A-MPR for EN-DC defined in this clause is used instead of MPR defined in 6.2B.2.2, not additively, so EN-DC MPR = 0 when NS\_04 is signaled. For UEs scheduled with single uplink transmission, AMPR in subclause 6.2.4 of [5] and 6.2.3 of [2] apply. + +For UE supporting dynamic power sharing the following: + +- for the MCG, $A\text{-MPR}_c$ in accordance with 36.101 [5] +- for the SCG, + +$$A\text{-MPR}'_c = A\text{-MPR}_{\text{NR}} = \text{MAX}( A\text{-MPR}_{\text{single,NR}}, A\text{-MPR}_{\text{IM3}} )$$ + +- for the total configured transmission power, + +$$A\text{-MPR}_{\text{tot}} = P_{\text{PowerClass,EN-DC}} - \min(P_{\text{PowerClass,EN-DC}}, 10 * \log_{10}(10^{((P_{\text{PowerClass,E-UTRA}} - A\text{-MPR}_{\text{E-UTRA}})/10)} + 10^{((P_{\text{PowerClass,NR}} - A\text{-MPR}_{\text{NR}})/10)}))$$ + +where + +$$A\text{-MPR}_{\text{E-UTRA}} = \text{MAX}( A\text{-MPR}_{\text{single,E-UTRA}} + \text{MPR}_{\text{single,E-UTRA}}, A\text{-MPR}_{\text{IM3}} )$$ + +with + +- $A\text{-MPR}_{\text{single,E-UTRA}}$ is the A-MPR defined for the E-UTRA transmission in TS 36.101 [5] +- $A\text{-MPR}_{\text{single,NR}}$ is the A-MPR defined for the NR transmission in TS 38.101-1 [2] +- $\text{MPR}_{\text{single,E-UTRA}}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [5] + +For UEs not supporting dynamic power sharing the following + +- for the MCG, + +$$A\text{-MPR}_c = \text{MAX}( A\text{-MPR}_{\text{single, E-UTRA}} + \text{MPR}_{\text{single, E-UTRA}}, A\text{-MPR}_{\text{IM3}} )$$ + +- for the SCG, + +$$A\text{-MPR}'_c = \text{MAX}( A\text{-MPR}_{\text{single, NR}}, A\text{-MPR}_{\text{IM3}} )$$ + +where + +- $A\text{-MPR}_{\text{single, E-UTRA}}$ is the A-MPR defined for the E-UTRA transmission in TS 36.101 [5] +- $A\text{-MPR}_{\text{single, NR}}$ is the A-MPR defined for the NR transmission in TS 38.101-1 [2] +- $\text{MPR}_{\text{single, E-UTRA}}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [5] + +The UE determines the Channel Configuration Case and the value of $A\text{-MPR}_{\text{IM3}}$ as follows: + +If $F_{\text{IM3, low\_block, low}} < 2490.5 \text{ MHz}$ + +Channel Configuration Case B. $A\text{-MPR}_{\text{IM3}}$ defined in clause 6.2B.3.1.3.2.2. + +Else + +Channel Configuration Case A. $A\text{-MPR}_{\text{IM3}}$ defined in clause 6.2B.3.1.3.2.1. + +where + +- $F_{\text{IM3, low\_block, low}} = (2 * F_{\text{low\_channel, low\_edge}}) - F_{\text{high\_channel, high\_edge}}$ +- $F_{\text{low\_channel, low\_edge}}$ is the lowermost frequency of lower transmission bandwidth configuration. +- $F_{\text{high\_channel, high\_edge}}$ is the uppermost frequency of upper transmission bandwidth configuration. + +Where the transmission bandwidth configuration for NR is the maximum frequency span covering all the configured SCSSpecificCarrier for scenarios that carrier bandwidths with different SCS can be fully overlapped. + +###### 6.2B.3.1.3.2.1 $A\text{-MPR}_{\text{IM3}}$ for NS\_04 to meet -13 dBm / 1MHz for 26dBm UE power + +$A\text{-MPR}$ in this subclause is relative to 26 dBm for a power class 2 Cell Group. The same $A\text{-MPR}$ is used relative to 23 dBm for a power class 3 Cell Group. For the UE is configured with channel configurations Case A or Case C (defined in Clause 6.2B.3.2.3.1), the allowed maximum output power reduction for IM3s applied to transmission on the MCG and the SCG with non-contiguous resource allocation is defined as follows: + +$$A\text{-MPR}_{\text{IM3}} = M_A$$ + +Where $M_A$ is defined as follows + +$$M_A = 15 ; 0 \leq B < 0.5$$ + +$$10 ; 0.5 \leq B < 1.0$$ + +$$8 ; 1.0 \leq B < 2.0$$ + +$$6 ; 2.0 \leq B$$ + +Where: + +For UEs supporting dynamic power sharing, + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +For UEs not supporting dynamic power sharing, + +For E-UTRA + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{NR}} = 15$ kHz is assumed in calculation of B. + +For NR + +$$B = (12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{E-UTRA}} = 15$ kHz is assumed in calculation of B + +and $M_A$ is reduced by 1 dB for $B < 2.0$ . + +###### 6.2B.3.1.3.2.2 A-MPR for NS\_04 to meet -25 dBm / 1MHz for 26 dBm UE power + +A-MPR in this subclause is relative to 26 dBm for a power class 2 Cell Group. The same A-MPR is used relative to 23 dBm for a power class 3 Cell Group. For the UE is configured with channel configurations Case B or Case D (defined in clause 6.2B.3.2.1), the allowed maximum output power reduction for IM3s applied to transmission on the MCG and the SCG with non-contiguous resource allocation is defined as follows: + +$$\text{A-MPR}_{\text{IM3}} = M_A$$ + +Where $M_A$ is defined as follows + +$$M_A = 15 ; 0 \leq B < 1.0$$ + +$$14 ; 1.0 \leq B < 2.0$$ + +$$13 ; 2.0 \leq B < 5.0$$ + +$$12 ; 5.0 \leq B$$ + +Where: + +For UEs supporting dynamic power sharing, + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +For UEs not supporting dynamic power sharing, + +For E-UTRA + +$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{NR}} = 15$ kHz is assumed in calculation of B. + +For NR + +$$B = (12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000,000$$ + +Where $\text{SCS}_{\text{E-UTRA}} = 15$ kHz is assumed in calculation of B + +and $M_A$ is reduced by 1 dB. + +##### 6.2B.3.1.4 Test description + +###### 6.2B.3.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on NR operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.2B.3.1.4.1-1 through 6.2B.3.1.4.1-2. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +Table 6.2B.3.1.4.1-0: Void + +**Table 6.2B.3.1.4.1-1: Test configuration table (network signalled value "NS\_35")** + +| Initial Conditions | | | | | | | | +|------------------------------------------------------------------------|---------|-------------------------------------------------------------------|----------------------------|------------------------|----------------------|------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | Normal | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | | Low range, High range | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | | Lowest N RB_agg , Highest N RB_agg (Note 2) | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | | Lowest, Highest | | | | | | +| Test Parameters | | | | | | | | +| Test ID | Freq | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | | E-UTRA Cell | | NR Cell | | Common | +| | | | Modulation | RB allocation (Note 5) | Modulation | RB allocation (Note 1) | Power config (Note 8) | +| 1 | Default | N/A | 16QAM | Outer_Full | DFT-s-OFDM Pi/2 BPSK | Outer_Full | B | +| 2 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | B | +| 3 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 4 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | A | +| 5 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | B | +| 6 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | A | +| 7 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 8 | Default | | 16QAM | Outer_Full | DFT-s-OFDM QPSK | Outer_Full | B | +| 9 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | Edge_1RB_Right | B | +| 10 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | N/A | A | +| 11 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Right | A | +| 12 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | Edge_1RB_Left | B | +| 13 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Left | A | +| 14 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | N/A | A | +| 15 | Default | | 16QAM | Outer_Full | DFT-s-OFDM 16QAM | Outer_Full | B | +| 16 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | Edge_1RB_Right | B | +| 17 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | N/A | A | +| 18 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Right | A | +| 19 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | Edge_1RB_Left | B | +| 20 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Left | A | +| 21 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | N/A | A | +| 22 | Default | | 16QAM | Outer_Full | DFT-s-OFDM | Outer_Full | B | + +| | | | | | | | | +|--|--|--|--|--|-------|--|--| +| | | | | | 64QAM | | | +|--|--|--|--|--|-------|--|--| + +| | | | | | | | | +|-------------|---------|--|-------|-----------------|----------------------|----------------|---| +| 23 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM
64QAM | Edge_1RB_Right | B | +| 24 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM
64QAM | Edge_1RB_Left | B | +| 25 | Default | | 16QAM | Outer_Full | DFT-s-OFDM
256QAM | Outer_Full | B | +| 26 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM
256QAM | Edge_1RB_Right | B | +| 27 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM
256QAM | Edge_1RB_Left | B | +| 28 | Default | | 16QAM | Outer_Full | CP-OFDM QPSK | Outer_Full | B | +| 29 (Note 3) | Default | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Right | B | +| 30 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | N/A | A | +| 31 (Note 3) | High | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Right | A | +| 32 (Note 4) | Default | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | Edge_1RB_Left | B | +| 33 (Note 4) | Low | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Left | A | +| 34 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | N/A | A | +| 35 | Default | | 16QAM | Outer_Full | CP-OFDM
16QAM | Outer_Full | B | +| 36 (Note 3) | Default | | 16QAM | Outer_1RB_Left | CP-OFDM
16QAM | Edge_1RB_Right | B | +| 37 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM
16QAM | N/A | A | +| 38 (Note 3) | High | | 16QAM | N/A | CP-OFDM
16QAM | Edge_1RB_Right | A | +| 39 (Note 4) | Default | | 16QAM | Outer_1RB_Right | CP-OFDM
16QAM | Edge_1RB_Left | B | +| 40 (Note 4) | Low | | 16QAM | N/A | CP-OFDM
16QAM | Edge_1RB_Left | A | +| 41 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM
16QAM | N/A | A | +| 42 | Default | | 16QAM | Outer_Full | CP-OFDM
64QAM | Outer_Full | B | +| 43 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM
64QAM | Edge_1RB_Right | B | +| 44 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM
64QAM | Edge_1RB_Left | B | +| 45 | Default | | 16QAM | Outer_Full | CP-OFDM
256QAM | Outer_Full | B | +| 46 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM
256QAM | Edge_1RB_Right | B | +| 47 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM
256QAM | Edge_1RB_Left | B | +| 48 (Note 4) | Default | | 16QAM | Edge_Full_Right | CP-OFDM
256QAM | Edge_Full_Left | B | + +- NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +- NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same $N_{RB\_agg}$ , select the combination to test as follows: +- Lowest ENBW: NR component with lowest $N_{RB}$ is tested. + - Highest ENBW: NR component with highest $N_{RB}$ is tested. +- NOTE 3: Applicable when E-UTRA cell carrier frequency is lower than NR cell carrier. +- NOTE 4: Applicable when NR cell carrier frequency is lower than E-UTRA cell carrier. +- NOTE 5: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Edge\_Full\_Right is defined as 2 RBs allocated at the right edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. +- NOTE 6: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in FR1. +- NOTE 7: Test IDs with simultaneous E-UTRA and NR UL transmission only apply for UEs indicating dualPA-Architecture. +- NOTE 8: Power config as specified in Table 6.2B.3.1.4.3-1-1 to 6.2B.3.1.4.3-2 (PC3) or Table 6.2B.3.1.4.3-3 to 6.2B.3.1.4.3-4 (PC2). + +**Table 6.2B.3.1.4.1-2: NR test configuration table for NS\_04** + +| Initial Conditions | | | | | | | | +|------------------------------------------------------------------------|---------|------------------------|-------------------------------------------------------------------|------------------------|----------------------|------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | | | Low range, High range (Note 7) | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | | | Lowest N RB_agg , Highest N RB_agg (Note 2) | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | | | Lowest, Highest | | | | | +| Test Parameters | | | | | | | | +| Test ID | Freq | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | | E-UTRA Cell | | NR Cell | | Common | +| | | | Modulation | RB allocation (Note 5) | Modulation | RB allocation (Note 1) | Power config (Note 8) | +| 1 | Default | N/A | 16QAM | Outer_Full | DFT-s-OFDM Pi/2 BPSK | Outer_Full | B | +| 2 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | B | +| 3 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 4 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | A | +| 5 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | B | +| 6 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | A | +| 7 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 8 | Default | | 16QAM | Outer_Full | DFT-s-OFDM QPSK | Outer_Full | B | +| 9 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | Edge_1RB_Right | B | +| 10 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | N/A | A | +| 11 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Right | A | +| 12 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | Edge_1RB_Left | B | +| 13 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Left | A | +| 14 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | N/A | A | +| 15 | Default | | 16QAM | Outer_Full | DFT-s-OFDM 16QAM | Outer_Full | B | +| 16 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | Edge_1RB_Right | B | +| 17 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | N/A | A | +| 18 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Right | A | +| 19 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | Edge_1RB_Left | B | +| 20 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Left | A | +| 21 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | N/A | A | +| 22 | Default | | 16QAM | Outer_Full | DFT-s-OFDM | Outer_Full | B | + +| | | | | | | | | +|--|--|--|--|--|-------|--|--| +| | | | | | 64QAM | | | +|--|--|--|--|--|-------|--|--| + +| | | | | | | | | +|-------------|---------|--|-------|-----------------|----------------------|----------------|---| +| 23 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM
64QAM | Edge_1RB_Right | B | +| 24 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM
64QAM | Edge_1RB_Left | B | +| 25 | Default | | 16QAM | Outer_Full | DFT-s-OFDM
256QAM | Outer_Full | B | +| 26 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM
256QAM | Edge_1RB_Right | B | +| 27 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM
256QAM | Edge_1RB_Left | B | +| 28 | Default | | 16QAM | Outer_Full | CP-OFDM QPSK | Outer_Full | B | +| 29 (Note 3) | Default | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Right | B | +| 30 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | N/A | A | +| 31 (Note 3) | High | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Right | A | +| 32 (Note 4) | Default | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | Edge_1RB_Left | B | +| 33 (Note 4) | Low | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Left | A | +| 34 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | N/A | A | +| 35 | Default | | 16QAM | Outer_Full | CP-OFDM
16QAM | Outer_Full | B | +| 36 (Note 3) | Default | | 16QAM | Outer_1RB_Left | CP-OFDM
16QAM | Edge_1RB_Right | B | +| 37 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM
16QAM | N/A | A | +| 38 (Note 3) | High | | 16QAM | N/A | CP-OFDM
16QAM | Edge_1RB_Right | A | +| 39 (Note 4) | Default | | 16QAM | Outer_1RB_Right | CP-OFDM
16QAM | Edge_1RB_Left | B | +| 40 (Note 4) | Low | | 16QAM | N/A | CP-OFDM
16QAM | Edge_1RB_Left | A | +| 41 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM
16QAM | N/A | A | +| 42 | Default | | 16QAM | Outer_Full | CP-OFDM
64QAM | Outer_Full | B | +| 43 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM
64QAM | Edge_1RB_Right | B | +| 44 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM
64QAM | Edge_1RB_Left | B | +| 45 | Default | | 16QAM | Outer_Full | CP-OFDM
256QAM | Outer_Full | B | +| 46 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM
256QAM | Edge_1RB_Right | B | +| 47 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM
256QAM | Edge_1RB_Left | B | +| 48 (Note 4) | Default | | 16QAM | Edge_Full_Right | CP-OFDM
256QAM | Edge_Full_Left | B | + +- NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +- NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same $N_{RB\_agg}$ , select the combination to test as follows: +- Lowest ENBW: NR component with lowest $N_{RB}$ is tested. + - Highest ENBW: NR component with highest $N_{RB}$ is tested. +- NOTE 3: Applicable when E-UTRA cell carrier frequency is lower than NR cell carrier. +- NOTE 4: Applicable when NR cell carrier frequency is lower than E-UTRA cell carrier. +- NOTE 5: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Edge\_Full\_Right is defined as 2 RBs allocated at the right edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. +- NOTE 6: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in FR1. +- NOTE 7: Additional IM3 test frequencies may apply. +- NOTE 8: Power config as specified in Table 6.2B.3.1.4.3-1 to 6.2B.3.1.4.3-2 (PC3) or Table 6.2B.3.1.4.3-3 to 6.2B.3.1.4.3-4 (PC2). +- NOTE 9: Test IDs with simultaneous E-UTRA and NR UL transmission only apply for UEs indicating dualPA-Architecture. + +**Table 6.2B.3.1.4.1-3: Additional IM3 Test Frequencies for NS\_04 intra-band contiguous EN-DC** + +| Additional Initial Condition | | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Additional IM3 Test Frequencies |

if SCS 15 kHz, 15 kHz NR raster, and NR ChBw 40 MHz or 50 MHz then IM3 test frequencies as specified in Table 6.2B.3.1.4.1-4.

if SCS 30 kHz, 30 kHz NR raster, and NR ChBw 40 MHz, 50 MHz or 60 MHz then IM3 test frequencies as specified in Table 6.2B.3.1.4.1-5.

if SCS 60 kHz, 15 kHz NR raster, and NR ChBw 40 MHz, 50 MHz or 60 MHz then IM3 test frequencies as specified in Table 6.2B.3.1.4.1-6.

| + +Table 6.2B.3.1.4.1-4: EN-DC combination DC\_(n)41AA, intra-band contiguous, SCS 15 kHz, 15 kHz NR raster, IM3 test frequencies + +| EN-DC channel bandwidth combination | CC | Bandwidth [MHz] | carrier Bandwidth [PRBs] | Range | | Carrier centre [MHz] Note 2 | Carrier centre [ARFCN] | point A [MHz] | absolute Frequency Point A [ARFCN] | offset ToCarrier [Carrier PRBs ] | SS block SCS [kHz] | GSCN | absolute Frequency SSB [ARFCN] | +|-------------------------------------|------------|-----------------|--------------------------|-------------------|-----|-----------------------------|------------------------|---------------|------------------------------------|----------------------------------|--------------------|------|--------------------------------| +| E-UTRA: 20MHz + NR: 40MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2600.400 | 40694 | - | - | - | - | - | - | +| | NR CC1 | 40 | 216 | Downlink & Uplink | IM3 | 2570.400 | 514080 | 2550.96 | 510192 | 0 | 15 | 6384 | 514080 | +| E-UTRA: 20MHz + NR: 50MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2620.400 | 40894 | - | - | - | - | - | - | +| | NR CC1 | 50 | 270 | Downlink & Uplink | IM3 | 2585.400 | 517080 | 2561.1 | 512220 | 0 | 15 | 6408 | 517080 | + +Table 6.2B.3.1.4.1-5: EN-DC combination DC\_(n)41AA, intra-band contiguous, SCS 30 kHz, 30 kHz NR raster, IM3 test frequencies + +| EN-DC channel bandwidth combination | CC | Bandwidth [MHz] | carrier Bandwidth [PRBs] | Range | | Carrier centre [MHz] Note 2 | Carrier centre [ARFCN] | point A [MHz] | absolute Frequency Point A [ARFCN] | offset ToCarrier [Carrier PRBs ] | SS block SCS [kHz] | GSCN | absolute Frequency SSB [ARFCN] | +|-------------------------------------|------------|-----------------|--------------------------|-------------------|-----|-----------------------------|------------------------|---------------|------------------------------------|----------------------------------|--------------------|------|--------------------------------| +| E-UTRA: 20MHz + NR: 40MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2600.400 | 40694 | - | - | - | - | - | - | +| | NR CC1 | 40 | 216 | Downlink & Uplink | IM3 | 2570.400 | 514080 | 2550.96 | 510192 | 0 | 15 | 6384 | 514080 | +| E-UTRA: 20MHz + NR: 50MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2620.400 | 40894 | - | - | - | - | - | - | +| | NR CC1 | 50 | 270 | Downlink & Uplink | IM3 | 2585.400 | 517080 | 2561.1 | 512220 | 0 | 15 | 6408 | 517080 | +| E-UTRA: 20MHz + NR: 60MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2640.500 | 41095 | - | - | - | - | - | - | + +| | | | | | | | | | | | | | | +|--|--------|----|-----|-------------------|-----|----------|--------|---------|--------|---|----|------|--------| +| | NR CC1 | 60 | 162 | Downlink & Uplink | IM3 | 2600.500 | 520100 | 2571.34 | 514268 | 0 | 30 | 6438 | 520100 | +|--|--------|----|-----|-------------------|-----|----------|--------|---------|--------|---|----|------|--------| + +**Table 6.2B.3.1.4.1-6: EN-DC combination DC\_(n)41AA, intra-band contiguous, SCS 60 kHz, 15 kHz NR raster, IM3 test frequencies** + +| EN-DC channel bandwidth combination | CC | Bandwidth [MHz] | carrier Bandwidth [PRBs] | Range | Carrier centre [MHz] Note 2 | Carrier centre [ARFCN] | point A [MHz] | absolute Frequency Point A [ARFCN] | offset ToCarrier [Carrier PRBs ] | SS block SCS [kHz] | GSCN | absolute Frequency SSB [ARFCN] | +|-------------------------------------|------------|-----------------|--------------------------|-------------------|-----------------------------|------------------------|---------------|------------------------------------|----------------------------------|--------------------|------|--------------------------------| +| E-UTRA: 20MHz + NR: 40MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2600.400 | 40694 | - | - | - | - | - | +| | NR CC1 | 40 | 51 | Downlink & Uplink | IM3 | 2570.400 | 514080 | 2552.04 | 510408 | 0 | 15 | 6387 | +| E-UTRA: 20MHz + NR: 50MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2620.400 | 40894 | - | - | - | - | - | +| | NR CC1 | 50 | 65 | Downlink & Uplink | IM3 | 2585.400 | 517080 | 2562 | 512400 | 0 | 15 | 6411 | +| E-UTRA: 20MHz + NR: 60MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2640.500 | 41095 | - | - | - | - | - | +| | NR CC1 | 60 | 79 | Downlink & Uplink | IM3 | 2600.500 | 520100 | 2572.06 | 514412 | 0 | 15 | 6435 | + +Editor's note: The following lines belong at the end of clause 6.2B.3.1.4.1. As new tables are added to this clause, these lines should always follow the tables. + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for E-UTRA the cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. NR downlink signals are initially set up according to Annex C.0, C.1, and C.2 and uplink signals according to Annex G.0, G.1, G.2, and G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG and NR CG link respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.3.1.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.3.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.2B.3.1.4.1-1 or 6.2B.3.1.4.1-2 on both EN-DC component carriers. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{\text{UMAX}}$ level; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean power over all component carriers for the EN-DC configuration, which shall meet the requirements described in table 6.2B.3.1.5.1-1 through to 6.2B.3.1.5.2-6. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). For TDD, only slots consisting of only UL symbols are under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.2B.3.1.4.1-1 or 6.2B.3.1.4.1-2, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.3.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1, with the following exceptions. + +**Table 6.2B.3.1.4.3-1: RRCConnectionReconfiguration: nr-Config-r15 for PC3** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.2B.3.1.4.3-2: PhysicalCellGroupConfig for PC3** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.2B.3.1.4.3-3: RRCConnectionReconfiguration: nr-Config-r15 for PC2** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.2B.3.1.4.3-4: PhysicalCellGroupConfig for PC2** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +###### **6.2B.3.1.4.3-5: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.3.1.4.3-6: RRCConnectionReconfiguration: tdm-PatternConfig if E-UTRA on FDD band and UE does not support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | Power config A (NOTE 1) | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. + +###### **6.2B.3.1.4.3.1 Message contents exceptions (network signalled value "NS\_04")** + +Message contents are according to TS 38.508-1 [6] clause 4.6.1 with the following exceptions for NS\_04: + +**Table 6.2B.3.1.4.3.1-1: AdditionalSpectrumEmission for MCG and "NS\_04"** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.4.3.3-1 | | | | +|------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 1 (NS_04) | | | + +**Table 6.2B.3.1.4.3.1-2: AdditionalSpectrumEmission for SCG and "NS\_04"** + +| Derivation Path: TS 38.508-1 [6] clause 4.6.3, Table 4.6.3-1 | | | | +|--------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 1 (NS_04) | | | + +###### **6.2B.3.1.4.3.2 Message contents exceptions (network signalled value "NS\_35")** + +Message contents are according to TS 38.508-1 [6] clause 4.6.1 with the following exceptions for NS\_35: + +**Table 6.2B.3.1.4.3.2-1: AdditionalSpectrumEmission for MCG and "NS\_35"** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.4.3.3-1 | | | | +|------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 1 (NS_35) | | | + +**Table 6.2B.3.1.4.3.2-2: AdditionalSpectrumEmission for for SCG "NS\_35"** + +| Derivation Path: TS 38.508-1 [5] clause 4.6.3, Table 4.6.3-1 | | | | +|--------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 1 (NS_35) | | | + +6.2B.3.1.5 Test requirement + +**Table: 6.2B.3.1.5-1: Test Tolerance for UE maximum output power** + +| | f ≤ 3.0GHz | 3.0GHz < f ≤ 6GHz | +|---------------------------------|-------------------|-----------------------------| +| ENBW ≤ 40MHz | 0.7 dB | 1.0 dB | +| 40MHz < ENBW ≤ 100MHz | 1.0 dB | 1.0 dB | + +6.2B.3.1.5.1 Test requirement for network signalled value "NS\_35" + +The maximum output power, derived in step 3 shall be within the range prescribed by the nominal maximum output power and tolerance in table 6.2B.3.1.5.1-1. The allowed A-MPR values specified in table 6.2B.3.1.3-1 are in addition to the allowed MPR requirements specified in clause 6.2B.1.1.3. For the UE maximum output power modified by MPR and/or A-MPR, the power limits specified in table 6.2B.1.1.3-1 apply. + +**Table 6.2B.3.1.5.1-1: UE Power Class test requirements for network signalled value "NS\_35" for UEs not supporting dynamic power sharing** + +| Test ID | Test freq. range | E-UTRA BW | NR BW | Modulation | P PowerClass ass (dBm) | ΔP Pow erClass (dB) | A-MPR c (dB) | ΔTC,c (dB) Note 7 | P CMAX,c (dBm) | T(P CMAX,c L,f,c ) (dB) | T L,c (dB) | Upper limit | Lower limit | +|----------------------------------------|------------------|-----------|-------|------------|----------------------------------------------|-------------------------------------------|-------------------------|-------------------|---------------------------|-----------------------------------------------|-----------------------|-------------|-------------| +| 1, 8, 15, 22, 25 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 6.0 | 0 | 17.0 | 5 | +2/-3 | 25+TT | 12-TT | +| 1, 8, 15, 22, 25 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 6.0 | 0 | 17.0 | 5 | +2/-3 | 25+TT | 12-TT | +| 1, 8, 15, 22, 25 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 6.0 | 0 | 17.0 | 5 | +2/-3 | 25+TT | 12-TT | +| 1, 8, 15, 22, 25 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 6.0 | 0 | 17.0 | 5 | +2/-3 | 25+TT | 12-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 10.5 | 0 | 12.5 | 6 | +2/-3 | 25+TT | 6.5-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 10.5 | 0 | 12.5 | 6 | +2/-3 | 25+TT | 6.5-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 3, 10, 17 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 12.5 | 0 | 10.5 | 6 | +2/-3 | 25+TT | 4.5-TT | +| 3, 14, 17 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 4, 11, 18 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 12.5 | 0 | 10.5 | 12.5 | +2/-3 | 25+TT | 4.5-TT | +| 4, 11, 18 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 16.0 | 0 | 7.0 | 16.0 | +2/-3 | 25+TT | 0-TT | +| 6, 13, 20 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 6, 13, 20 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 7, 14, 21 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 7, 14, 21 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 28, 35, 42, 45 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 6.5 | 0 | 16.5 | 5 | +2/-3 | 25+TT | 11.5-TT | +| 28, 35, 42, 45 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 6.5 | 0 | 16.5 | 5 | +2/-3 | 25+TT | 11.5-TT | +| 28, 35, 42, 45 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 6.5 | 0 | 16.5 | 5 | +2/-3 | 25+TT | 11.5-TT | +| 28, 35, 42, 45 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 6.5 | 0 | 16.5 | 5 | +2/-3 | 25+TT | 11.5-TT | +| 29, 35, 42, 45 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6.5-TT | +| 29, 35, 42, 45 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 29, 35, 42, 45 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6.5-TT | +| 29, 35, 42, 45 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 30, 34, 37, 41 | Low | 5 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 30, 34, 37, 41 | Low | 5 | 15 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 31, 33, 38, 40 | High | 5 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 31, 33, 38, 40 | High | 15 | 5 | E-UTRA/NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | + +**Table 6.2B.3.1.5.1-1A: UE Power Class test requirements for network signalled value "NS\_35" for UEs supporting dynamic power sharing** + +| Test ID | Test freq. range | E-UTRA BW | NR BW | Modulation | P PowerClass ass (dBm) | ΔP Pow erClass (dB) | A-MPR c (dB) | ΔTC,c (dB) Note 7 | P CMAX,c (dBm) | T(P CMAX,c f,c ) (dB) | T L,c (dB) | Upper limit | Lower limit | +|----------------------------------------|------------------|-----------|-------|------------|----------------------------------------------|-------------------------------------------|-------------------------|-------------------|---------------------------|---------------------------------------------|-----------------------|-------------|-------------| +| 1, 8, 15, 22, 25 | Low | 5 | 5 | E-UTRA | 23 | 0 | 8.5 | 0 | 14.5 | 5 | +2/-3 | 25+TT | 9.5-TT | +| 1, 8, 15, 22, 25 | Low | 5 | 5 | NR | 23 | 0 | 8.5 | 0 | 14.5 | 5 | +2/-3 | 25+TT | 9.5-TT | +| 1, 8, 15, 22, 25 | Low | 5 | 15 | E-UTRA | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 1, 8, 15, 22, 25 | Low | 5 | 15 | NR | 23 | 0 | 6.5 | 0 | 16.5 | 5 | +2/-3 | 25+TT | 11.5-TT | +| 1, 8, 15, 22, 25 | High | 5 | 5 | E-UTRA | 23 | 0 | 8.5 | 0 | 14.5 | 5 | +2/-3 | 25+TT | 9.5-TT | +| 1, 8, 15, 22, 25 | High | 5 | 5 | NR | 23 | 0 | 8.5 | 0 | 14.5 | 5 | +2/-3 | 25+TT | 9.5-TT | +| 1, 8, 15, 22, 25 | High | 15 | 5 | E-UTRA | 23 | 0 | 6.5 | 0 | 16.5 | 5 | +2/-3 | 25+TT | 11.5-TT | +| 1, 8, 15, 22, 25 | High | 15 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | Low | 5 | 5 | E-UTRA | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | Low | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | Low | 5 | 15 | E-UTRA | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | Low | 5 | 15 | NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | High | 5 | 5 | E-UTRA | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | High | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | High | 15 | 5 | E-UTRA | 23 | 0 | 11.5 | 0 | 11.5 | 6 | +2/-3 | 25+TT | 5.5-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 2, 26, 27 | High | 15 | 5 | NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 3, 10, 17 | Low | 5 | 5 | E-UTRA/ | 23 | 0 | 12.5 | 0 | 10.5 | 6 | +2/-3 | 25+TT | 4.5-TT | +| 3, 10, 17 | Low | 5 | 15 | E-UTRA | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 4, 11, 18 | High | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 4, 11, 18 | High | 15 | 5 | NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 6, 17, 20 | Low | 5 | 5 | E-UTRA/ | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 6, 17, 20 | Low | 5 | 15 | E-UTRA | 23 | 0 | 16.5 | 0 | 6.5 | 7 | +2/-3 | 25+TT | -0.5-TT | + +| | | | | | | | | | | | | | | +|----------------|------|----|----|---------|----|---|------|---|------|---|-------|-------|---------| +| 7, 14, 21 | High | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 7, 14, 21 | High | 15 | 5 | NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 28, 35, 42, 45 | Low | 5 | 5 | E-UTRA | 23 | 0 | 9.5 | 0 | 13.5 | 5 | +2/-3 | 25+TT | 8.5-TT | +| 28, 35, 42, 45 | Low | 5 | 5 | NR | 23 | 0 | 9.5 | 0 | 13.5 | 5 | +2/-3 | 25+TT | 8.5-TT | +| 28, 35, 42, 45 | Low | 5 | 15 | E-UTRA | 23 | 0 | 13.5 | 0 | 9.5 | 6 | +2/-3 | 25+TT | 3.5-TT | +| 28, 35, 42, 45 | Low | 5 | 15 | NR | 23 | 0 | 7.0 | 0 | 16.0 | 5 | +2/-3 | 25+TT | 11-TT | +| 28, 35, 42, 45 | High | 5 | 5 | E-UTRA | 23 | 0 | 9.5 | 0 | 13.5 | 5 | +2/-3 | 25+TT | 8.5-TT | +| 28, 35, 42, 45 | High | 5 | 5 | NR | 23 | 0 | 9.5 | 0 | 13.5 | 5 | +2/-3 | 25+TT | 8.5-TT | +| 28, 35, 42, 45 | High | 15 | 5 | E-UTRA | 23 | 0 | 7.0 | 0 | 16.0 | 5 | +2/-3 | 25+TT | 11-TT | +| 28, 35, 42, 45 | High | 15 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 29, 36, 43, 46 | Low | 5 | 5 | E-UTRA | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 29, 36, 43, 46 | Low | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 29, 36, 43, 46 | Low | 5 | 15 | E-UTRA | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 0-TT | +| 29, 36, 43, 46 | Low | 5 | 15 | NR | 23 | 0 | 11.0 | 0 | 12.0 | 6 | +2/-3 | 25+TT | 6-TT | +| 29, 36, 43, 46 | High | 5 | 5 | E-UTRA | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 29, 36, 43, 46 | High | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | +2/-3 | 25+TT | 4-TT | +| 29, 36, 43, 46 | High | 15 | 5 | E-UTRA | 23 | 0 | 11.5 | 0 | 11.5 | 6 | +2/-3 | 25+TT | 0-TT | +| 29, 36, 43, 46 | High | 15 | 5 | NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | +2/-3 | 25+TT | 5.5-TT | +| 30, 37 | Low | 5 | 5 | E-UTRA/ | 23 | 0 | 13.0 | 0 | 10.0 | 6 | | 25+TT | 4-TT | +| 30, 37 | Low | 5 | 15 | E-UTRA | 23 | 0 | 16.0 | 0 | 7.0 | 7 | | 25+TT | 0-TT | +| 31, 38 | High | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | | 25+TT | 4-TT | +| 31, 38 | High | 15 | 5 | NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | | 25+TT | 0-TT | +| 34, 41 | High | 5 | 5 | NR | 23 | 0 | 13.0 | 0 | 10.0 | 6 | | 25+TT | 4-TT | +| 34, 41 | High | 15 | 5 | NR | 23 | 0 | 16.0 | 0 | 7.0 | 7 | | 25+TT | 0-TT | +| 33, 40 | Low | 5 | 5 | E-UTRA/ | 23 | 0 | 13.0 | 0 | 10.0 | 6 | | 25+TT | 4-TT | +| 33, 40 | Low | 5 | 15 | E-UTRA | 23 | 0 | 16.5 | 0 | 6.5 | 7 | | 25+TT | -0.5-TT | + +NOTE 8: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +###### 6.2B.3.1.5.2 + +Test requirement for network signalled value "NS\_04" + +**Table 6.2B.3.1.5.2-1: UE Power Class 3 test requirements for NS\_04, supporting dynamic power sharing and E-UTRA UL transmission overlapping with NR UL transmission** + +| Test ID | Test SCS (kHz) | A-MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------------|----------------|---------------------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 4) | 15, 30, 60 | 3 | 20 | 23 | 6 | 2 | 25+TT | 14-TT | +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 5) | 15, 30, 60 | 9 | 14 | 23 | 6 | 2 | 25+TT | 8-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4, 5) | 15 | 11 | 12 | 23 | 6 | 2 | 25+TT | 6-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4) | 30, 60 | 6 | 17 | 23 | 5 | 2 | 25+TT | 12-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 5) | 30, 60 | 11 | 12 | 23 | 6 | 2 | 25+TT | 6-TT | +| 48 (Note 3, 4) | 15 | 7 | 16 | 23 | 5 | 2 | 25+TT | 11-TT | +| 48 (Note 3, 4) | 30, 60 | 12 | 11 | 23 | 6 | 2 | 25+TT | 5-TT | +| 48 (Note 3, 5) | 15, 30, 60 | 7 | 16 | 23 | 5 | 2 | 25+TT | 11-TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. + +NOTE 4: When FIM3,low\_block,low ≥ 2490.5 MHz (Case A)NOTE 5: When FIM3,low\_block,low < 2490.5 MHz (Case B) + +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +**Table 6.2B.3.1.5.2-2: UE Power Class 3 test requirements for NS\_04, supporting dynamic power sharing and E-UTRA UL transmission not overlapping with NR UL transmission** + +| Test ID | Test SCS (kHz) | MPR (dB) | A-MPR (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (Note 1) | 15, 30, 60 | 0 | 3 | 20 | 23 | 4 | 2 | 25+TT | 16-TT | +| 4 (Note 2) | 15, 30, 60 | 0.5 | 0 | 22.5 | 23 | 2 | 2 | 25+TT | 20.5-TT | +| 6 (Note 2) | 15, 30, 60 | 0 | 3.5 | 19.5 | 23 | 3.5 | 2 | 25+TT | 16-TT | +| 11 (Note 2) | 15, 30, 60 | 1 | 0 | 22 | 23 | 2 | 2 | 25+TT | 20-TT | +| 13 (Note 2) | 15, 30, 60 | 0 | 4 | 19 | 23 | 3.5 | 2 | 25+TT | 15.5-TT | +| 18 (Note 2) | 15, 30, 60 | 2 | 0 | 21 | 23 | 2 | 2 | 25+TT | 19-TT | +| 20 (Note 2) | 15, 30, 60 | 0 | 4 | 19 | 23 | 3.5 | 2 | 25+TT | 15.5-TT | +| 31 (Note 2) | 15, 30, 60 | 3 | 0 | 20 | 23 | 2.5 | 2 | 25+TT | 17.5-TT | +| 33 (Note 2) | 15, 30, 60 | 0 | 5.5 | 17.5 | 23 | 5 | 2 | 25+TT | 12-TT | +| 38 (Note 2) | 15, 30, 60 | 3 | 0 | 20 | 23 | 2.5 | 2 | 25+TT | 17.5-TT | +| 40 (Note 2) | 15, 30, 60 | 0 | 5.5 | 17.5 | 23 | 5 | 2 | 25+TT | 12-TT | + +NOTE 1: Test configuration IDs without transmission overlap, 1RB E-UTRA allocation, A-MPR requirements in TS 36.101 [5] apply + +NOTE 2: Test configuration IDs without transmission overlap, 1RB NR allocation, A-MPR requirements in TS 38.101-1 [2] apply. + +NOTE 3: Void. + +NOTE 4: Void. + +NOTE 5: Void. + +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +**Table 6.2B.3.1.5.2-3: UE Power Class 3 test requirements for NS\_04, not supporting dynamic power sharing and E-UTRA UL transmission overlapping with NR UL transmission** + +| Test ID | Test SCS (kHz) | A-MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------------|----------------|---------------------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 4) | 15, 30, 60 | 6 | 17 | 23 | 5 | 2 | 25+TT | 12-TT | +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 5) | 15, 30, 60 | 12 | 11 | 23 | 6 | 2 | 25+TT | 5-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4, 5) | 15 | 14 | 9 | 23 | 7 | 2 | 25+TT | 2-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4) | 30, 60 | 9 | 14 | 23 | 6 | 2 | 25+TT | 8-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 5) | 30, 60 | 14 | 9 | 23 | 7 | 2 | 25+TT | 2-TT | +| 48 (Note 3, 4) | 15 | 10 | 13 | 23 | 6 | 2 | 25+TT | 7-TT | +| 48 (Note 3, 4) | 30, 60 | 15 | 8 | 23 | 7 | 2 | 25+TT | 1-TT | +| 48 (Note 3, 5) | 15, 30, 60 | 10 | 13 | 23 | 6 | 2 | 25+TT | 7-TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 4: When FIM3,low\_block,low ≥ 2490.5 MHz (Case A) +NOTE 5: When FIM3,low\_block,low < 2490.5 MHz (Case B) +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +**Table 6.2B.3.1.5.2-4: UE Power Class 2 test requirements for NS\_04, supporting dynamic power sharing and E-UTRA UL transmission overlapping with NR UL transmission** + +| Test ID | Test SCS (kHz) | A-MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------------|----------------|---------------------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 4) | 15, 30, 60 | 3 | 23 | 26 | 3 | 2 | 28+TT | 20-TT | +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 5) | 15, 30, 60 | 9 | 17 | 26 | 5 | 2 | 28+TT | 12-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4, 5) | 15 | 11 | 15 | 26 | 6 | 2 | 28+TT | 9-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4) | 30, 60 | 6 | 20 | 26 | 6 | 2 | 28+TT | 14-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 5) | 30, 60 | 11 | 15 | 26 | 6 | 2 | 28+TT | 9-TT | +| 48 (Note 3, 4) | 15 | 7 | 19 | 26 | 5 | 2 | 28+TT | 14-TT | +| 48 (Note 3, 4) | 30, 60 | 12 | 14 | 26 | 6 | 2 | 28+TT | 8-TT | +| 48 (Note 3, 5) | 15, 30, 60 | 7 | 19 | 26 | 5 | 2 | 28+TT | 14-TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 4: When FIM3,low\_block,low ≥ 2490.5 MHz (Case A) +NOTE 5: When FIM3,low\_block,low < 2490.5 MHz (Case B) +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +**Table 6.2B.3.1.5.2-5: UE Power Class 2 test requirements for NS\_04, supporting dynamic power sharing and E-UTRA UL transmission not overlapping with NR UL transmission (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by $\text{powerClassNRPart-r16}$ ))** + +| Test ID | Test SCS (kHz) | MPR (dB) | A-MPR (dB) | $P_{\text{EN-DC, tot\_L}}$ (dBm) | $P_{\text{EN-DC, tot\_H}}$ (dBm) | $T_{\text{LOW}}$ ( $P_{\text{CMAX\_L}}$ ) (dB) | $T_{\text{HIGH}}$ ( $P_{\text{CMAX\_H}}$ ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|------------|----------------------------------|----------------------------------|------------------------------------------------|-------------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (Note 1) | 15, 30, 60 | 0 | 3 | 23 | 26 | 2 | 2 | 28+TT | 21-TT | +| 4 (Note 2) | 15, 30, 60 | 3.5 | 0 | 22.5 | 26 | 2 | 2 | 28+TT | 20.5-TT | +| 6 (Note 2) | 15, 30, 60 | 0 | 5.5 | 20.5 | 26 | 2.5 | 2 | 28+TT | 18-TT | +| 11 (Note 2) | 15, 30, 60 | 3.5 | 0 | 22.5 | 26 | 2 | 2 | 28+TT | 20.5-TT | +| 13 (Note 2) | 15, 30, 60 | 0 | 6 | 20 | 26 | 2.5 | 2 | 28+TT | 17.5-TT | +| 18 (Note 2) | 15, 30, 60 | 3.5 | 0 | 22.5 | 26 | 2 | 2 | 28+TT | 20.5-TT | +| 20 (Note 2) | 15, 30, 60 | 0 | 6 | 20 | 26 | 2.5 | 2 | 28+TT | 17.5-TT | +| 31 (Note 2) | 15, 30, 60 | 3.5 | 0 | 22.5 | 26 | 2 | 2 | 28+TT | 20.5-TT | +| 33 (Note 2) | 15, 30, 60 | 0 | 7.5 | 18.5 | 26 | 4 | 2 | 28+TT | 14.5-TT | +| 38 (Note 2) | 15, 30, 60 | 3.5 | 0 | 22.5 | 26 | 2 | 2 | 28+TT | 20.5-TT | +| 40 (Note 2) | 15, 30, 60 | 0 | 7.5 | 18.5 | 26 | 4 | 2 | 28+TT | 14.5-TT | + +NOTE 1: Test configuration IDs without transmission overlap, 1RB E-UTRA allocation, A-MPR requirements in TS 36.101 [5] apply. + +NOTE 2: Test configuration IDs without transmission overlap, 1RB NR allocation, A-MPR requirements in TS 38.101-1 [2] apply. + +NOTE 3: Void. + +NOTE 4: Void. + +NOTE 5: Void. + +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +**Table 6.2B.3.1.5.2-5a: UE Power Class 2 test requirements for NS\_04, E-UTRA UL transmission not overlapping with NR UL transmission (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by $\text{powerClassNRPart-r16}$ ))** + +| Test ID | Test SCS (kHz) | MPR (dB) | A-MPR (dB) | $P_{\text{EN-DC, tot\_L}}$ (dBm) | $P_{\text{EN-DC, tot\_H}}$ (dBm) | $T_{\text{LOW}}$ ( $P_{\text{CMAX\_L}}$ ) (dB) | $T_{\text{HIGH}}$ ( $P_{\text{CMAX\_H}}$ ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|-----------------------------------------------|----------------|----------|------------|----------------------------------|----------------------------------|------------------------------------------------|-------------------------------------------------|-------------------|-------------------| +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 (Note 1) | 15, 30, 60 | 0 | 3 | 23 | 26 | 2 | 2 | 28+TT | 21+TT | +| 4 (Note 2) | 15, 30, 60 | 0.5 | 0 | 22.5 | 23 | 2 | 2 | 25+TT | 20.5+TT | +| 6 (Note 2) | 15, 30, 60 | 0 | 3.5 | 19.5 | 23 | 3.5 | 2 | 25+TT | 16+TT | +| 11 (Note 2) | 15, 30, 60 | 1 | 0 | 22 | 23 | 2 | 2 | 25+TT | 20+TT | +| 13 (Note 2) | 15, 30, 60 | 0 | 4 | 19 | 23 | 3.5 | 2 | 25+TT | 15.5+TT | +| 18 (Note 2) | 15, 30, 60 | 2 | 0 | 21 | 23 | 2 | 2 | 25+TT | 19+TT | +| 20 (Note 2) | 15, 30, 60 | 0 | 4 | 19 | 23 | 3.5 | 2 | 25+TT | 15.5+TT | +| 31 (Note 2) | 15, 30, 60 | 3 | 0 | 20 | 23 | 2.5 | 2 | 25+TT | 17.5+TT | +| 33 (Note 2) | 15, 30, 60 | 0 | 5.5 | 17.5 | 23 | 5 | 2 | 25+TT | 12.5+TT | +| 38 (Note 2) | 15, 30, 60 | 3 | 0 | 20 | 23 | 2.5 | 2 | 25+TT | 17.5+TT | +| 40 (Note 2) | 15, 30, 60 | 0 | 5.5 | 17.5 | 23 | 5 | 2 | 25+TT | 12.5+TT | + +NOTE 1: Test configuration IDs without transmission overlap, 1RB E-UTRA allocation, A-MPR requirements in TS 36.101 [5] apply. + +NOTE 2: Test configuration IDs without transmission overlap, 1RB NR allocation, A-MPR requirements in TS 38.101- [2] apply. + +NOTE 3: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +**Table 6.2B.3.1.5.2-6: UE Power Class 2 test requirements for NS\_04, not supporting dynamic power sharing and E-UTRA UL transmission overlapping with NR UL transmission** + +| Test ID | Test SCS (kHz) | A-MPR tot (dB) | P EN-DC, tot_L (dBm) | P EN-DC, tot_H (dBm) | T LOW (P CMAX_L ) (dB) | T HIGH (P CMAX_H ) (dB) | Upper limit (dBm) | Lower limit (dBm) | +|------------------------------------------------------------------------------------|----------------|---------------------------|---------------------------------|---------------------------------|----------------------------------------------|-----------------------------------------------|-------------------|-------------------| +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 4) | 15, 30, 60 | 6 | 20 | 26 | 6 | 2 | 28+TT | 14-TT | +| 1, 8, 15, 22, 25, 28, 35, 42, 45 (Note 1, 5) | 15, 30, 60 | 12 | 14 | 26 | 6 | 2 | 28+TT | 8-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4, 5) | 15 | 14 | 12 | 26 | 6 | 2 | 28+TT | 6-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 4) | 30, 60 | 9 | 17 | 26 | 5 | 2 | 28+TT | 12-TT | +| 2, 5, 9, 12, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, 47 (Note 2, 5) | 30, 60 | 14 | 12 | 26 | 6 | 2 | 28+TT | 6-TT | +| 48 (Note 3, 4) | 15 | 10 | 16 | 26 | 5 | 2 | 28+TT | 11-TT | +| 48 (Note 3, 4) | 30, 60 | 15 | 11 | 26 | 6 | 2 | 28+TT | 5-TT | +| 48 (Note 3, 5) | 15, 30, 60 | 10 | 16 | 26 | 5 | 2 | 28+TT | 11-TT | + +NOTE 1: Test configuration IDs with transmission overlap with full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 2: Test configuration IDs with transmission overlap with 1RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 3: Test configuration IDs with transmission overlap with edge full RB allocation, requirements in TS 38.101-3 [4] apply. +NOTE 4: When FIM3,low\_block,low ≥ 2490.5 MHz (Case A) +NOTE 5: When FIM3,low\_block,low < 2490.5 MHz (Case B) +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.1.5-1. + +#### 6.2B.3.2 UE Additional Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC + +Editor's note: This test case is incomplete. The following aspects are either missing or not yet determined: + +- Test frequencies for the Minimum WGAP +- Test requirements for non-overlapping transmission of non-DPS UE need further investigation + +##### 6.2B.3.2.1 Test purpose + +Additional emission requirements can be signalled by the network with network signalling value indicated by the field *additionalSpectrumEmission*. To meet these additional requirements, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in Table 6.2B.1.1.3-1. Unless stated otherwise, an A-MPR of 0 dB shall be used. + +##### 6.2B.3.2.2 Test applicability + +The requirements of this test apply in test case 6.5B.2.2.2 Additional spectrum emission mask for network signalled values NS\_04 to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.2B.3.2.3 Minimum conformance requirements + +For intra-band non-contiguous EN-DC band combinations with additional requirements the A-MPR allowed are specified in table 6.2B.3.2.3-1 for UEs configured with EN-DC and combinations of network signalling values indicated in the E-UTRA and NR cell group(s). Unless otherwise stated the A-MPR specified in subclause 6.2B.3.2 for + +intra-band non-contiguous EN-DC configurations is the total power reduction allowed including MPR. For UEs scheduled with single uplink transmission, AMPR in subclause 6.2.4 of [4] and 6.2.3 of [2] apply. + +**Table 6.2B.3.2.3-1: Allowed power reduction for intra-band non-contiguous EN-DC** + +| DC configuration | Requirement (clause) | E-UTRA network signalling value | NR network signalling value | A-MPR (clause) | +|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|---------------------------------|-----------------------------|----------------| +| DC_41A_n41A 1 | 6.6.3.3.19 and 6.6.2.2.2 of TS 36.101 [5] and 6.5.2.3.2 and 6.5.3.3.1 of TS 38.101-1 [2] | NS_01 or NS_04 | NS_04 | 6.2B.3.2.3.1 | +| NOTE 1: Only applies to UEs that support dual UL transmission for this EN-DC combination. | | | | | +| NOTE 2: The requirement applies when the combination of network signalling values in the two CGs is set (only for UEs configured with EN-DC). | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.3.2. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA overlap in time with NR.LTE anchor agnostic approach is not applied for this case and referred to as sub-test 1. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that doesn't support dynamic power sharing. LTE anchor agnostic approach is not applied for this case. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +No exception requirements for NR or E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that supports dynamic power sharing. LTE anchor agnostic approach is not applied for this case. + +###### 6.2B.3.2.3.1 A-MPR for NS\_04 + +When the UE is configured for B41/n41 intra-band non-contiguous EN-DC and it receives IE NS\_04, the UE determines the total allowed maximum output power reduction as specified in this clause. The A-MPR for EN-DC defined in this clause is used instead of MPR defined in 6.2B.2.2, not additively, so EN-DC MPR=0 when NS\_04 is signalled. + +For UE supporting dynamic power sharing the following: + +- for the MCG, A-MPRc in accordance with TS 36.101 [5] +- for the SCG, + +$$A-MPR'_c = A-MPR_{NR} = \text{MAX}( A-MPR_{\text{single,NR}}, A-MPR_{\text{EN-DC}} )$$ + +- for the total configured transmission power, + +$$A-MPR_{\text{tot}} = P_{\text{PowerClass,EN-DC}} - \min(P_{\text{PowerClass,EN-DC}}, 10 * \log_{10}(10^{\frac{(P_{\text{PowerClass,E-UTRA}} - A-MPR_{\text{E-UTRA}})}{10}} + 10^{\frac{(P_{\text{PowerClass,NR}} - A-MPR_{\text{NR}})}{10}}))$$ + +where + +$$A-MPR_{\text{E-UTRA}} = \text{MAX}( A-MPR_{\text{single,E-UTRA}} + MPR_{\text{single,E-UTRA}}, A-MPR_{\text{EN-DC}} )$$ + +$$A-MPR_{\text{EN-DC}} = \text{MAX}(A-MPR_{\text{IM3}}, A-MPR_{\text{ACLRoverlap}} )$$ + +with + +- $A\text{-MPR}_{\text{single, E-UTRA}}$ is the A-MPR defined for the E-UTRA transmission in TS 38.101-3 [4] +- $A\text{-MPR}_{\text{single, NR}}$ is the A-MPR defined for the NR transmission in TS 38.101-1 [2] +- $MPR_{\text{single, E-UTRA}}$ is the MPR defined for the E-UTRA transmission in TS 38.101-3 [4] + +For UEs not supporting dynamic power sharing the following + +- for the MCG, + +$$A\text{-MPR}_c = \text{MAX}( A\text{-MPR}_{\text{single, E-UTRA}} + MPR_{\text{single, E-UTRA}}, A\text{-MPR}_{\text{IM3}}, A\text{-MPR}_{\text{ACLRoverlap}} )$$ + +- for the SCG, + +$$A\text{-MPR}'_c = \text{MAX}( A\text{-MPR}_{\text{single, NR}}, A\text{-MPR}_{\text{IM3}}, A\text{-MPR}_{\text{ACLRoverlap}} )$$ + +where + +- $A\text{-MPR}_{\text{single, E-UTRA}}$ is the A-MPR defined for the E-UTRA transmission in TS 36.101 [5] +- $A\text{-MPR}_{\text{single, NR}}$ is the A-MPR defined for the NR transmission in TS 38.101-1 [2] +- $MPR_{\text{single, E-UTRA}}$ is the MPR defined for the E-UTRA transmission in TS 36.101 [5] + +The UE determines the Channel Configuration Case and the value of $A\text{-MPR}_{\text{IM3}}$ as follows: + +$$\text{If AND}( F_{\text{IM3, low\_block, high}} < F_{\text{filter, low}}, \text{MAX}( SEM_{\text{-13, high}}, F_{\text{IM3, high\_block, low}} ) > F_{\text{filter, high}} )$$ + +Channel Configuration Case C. $A\text{-MPR}_{\text{IM3}}$ defined in Clause 6.2B.3.1.3.2.1 + +Else + +Channel Configuration Case D. $A\text{-MPR}_{\text{IM3}}$ defined in Clause 6.2B.3.1.3.2.2 + +where + +- $F_{\text{IM3, low\_block, high}} = (2 * F_{\text{low\_channel, high\_edge}}) - F_{\text{high\_channel, low\_edge}}$ +- $F_{\text{IM3, high\_block, low}} = (2 * F_{\text{high\_channel, low\_edge}}) - F_{\text{low\_channel, high\_edge}}$ +- $F_{\text{low\_channel, low\_edge}}$ is the lowermost frequency of lower transmission bandwidth configuration. +- $F_{\text{low\_channel, high\_edge}}$ is the uppermost frequency of lower transmission bandwidth configuration. +- $F_{\text{high\_channel, low\_edge}}$ is the lowermost frequency of upper transmission bandwidth configuration. +- $F_{\text{high\_channel, high\_edge}}$ is the uppermost frequency of upper transmission bandwidth configuration. +- $F_{\text{filter, low}} = 2480 \text{ MHz}$ +- $F_{\text{filter, high}} = 2745 \text{ MHz}$ +- $SEM_{\text{-13, high}} = \text{Threshold frequency where upper spectral emission mask for upper channel drops from } -13 \text{ dBm / } 1\text{MHz to } -25 \text{ dBm / } 1\text{MHz, as specified in Clause 6.6.2.2.2 in [5] and Subclause 6.5.2.3.2 in [2] respectively.}$ + +Where the transmission bandwidth configuration for NR is the maximum frequency span covering all the configured SCSSpecificCarrier for scenarios that carrier bandwidths with different SCS can be fully overlapped. + +The UE determines the value of $A\text{-MPR}_{\text{ACLRoverlap}}$ as specified in Table 6.2B.3.2.3.1-1: + +**Table 6.2B.3.2.3.1-1: A-MPRACLR overlap** + +| $W_{gap}$ | A-MPR ACLR overlap | +|-------------------------------------------------------------------------------|-------------------------------| +| $< BW_{channel,E-UTRA} + BW_{channel,NR}$ | 4 dB | +| $\geq BW_{channel,E-UTRA} + BW_{channel,NR}$ | 0 dB | +| NOTE 1: $W_{gap} = F_{high\_channel,low\_edge} - F_{low\_channel,high\_edge}$ | | + +##### 6.2B.3.2.4 Test description + +###### 6.2B.3.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.5B.3-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in test configuration table 6.2B.3.1.4.1-1 through 6.2B.3.1.4.1-2 with additional IM3 test frequencies for NS\_04 in 6.2B.3.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in Annex TS 36.521-1 [10] Annex C and in Annex C2 for LTE link and NR link respectively. + +**Table 6.2B.3.2.4.1-0: E-UTRA test configuration table** + +| E-UTRA Test Parameters | | | | | +|--------------------------------------------------------------------------|-----------------------------------|-----------------------|------------|---------------| +| E-UTRA Channel Bandwidth | E-UTRA Test Frequency (Note 1) | Downlink | Uplink | | +| | | N/A for A-MPR testing | Modulation | RB allocation | +| 20 MHz | Low range and High range (Note 2) | | QPSK | 100 | +| NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [6] clause 4.3.1 | | | | | +| NOTE 2: NR carrier shall be the outermost carrier during test. | | | | | + +**Table 6.2B.3.2.4.1-1: Additional IM3 Test Frequencies for NS\_04 intra-band non-contiguous EN-DC** + +| Additional Initial Condition | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Additional IM3 Test Frequencies |

if maximum W_{GAP} > 88.4 MHz, and SCS 15 kHz, 15 kHz NR raster then IM3 test frequencies as specified in Table 6.2B.3.2.4.1-2.

if maximum W_{GAP} > 88.4 MHz, and SCS 15 kHz, 30 kHz NR raster then IM3 test frequencies as specified in Table 6.2B.3.2.4.1-3.

if maximum W_{GAP} > 88.4 MHz, and SCS 15 kHz, 60 kHz NR raster then IM3 test frequencies as specified in Table 6.2B.3.2.4.1-4.

| + +Table 6.2B.3.2.4.1-2: EN-DC combination DC\_41A\_n41A, intra-band non-contiguous, SCS 15 kHz, 15 kHz NR raster, IM3 test frequencies + +| EN-DC channel bandwidth combination | CC | Bandwidth [MHz] | carrierBandwidth [PRBs] | Range | | Carrier centre [MHz] Note 2 | Carrier centre [ARFCN] | point A [MHz] | absolute FrequencyPoint A [ARFCN] | offsetTo Carrier [Carrier PRBs] | SS block SCS [kHz] | GSC N | absoluteFrequency SSB [ARFCN] | +|-------------------------------------|------------|-----------------|-------------------------|-------------------|-----|-----------------------------|------------------------|---------------|-----------------------------------|---------------------------------|--------------------|-------|-------------------------------| +| E-UTRA: 20MHz + NR: 40MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2666.700 | 41357 | - | - | - | - | - | - | +| | NR CC1 | 40 | 216 | Downlink & Uplink | IM3 | 2548.300 | 509660 | 2528.86 | 505772 | 0 | 15 | 6327 | 509660 | +| NR: 40MHz + E-UTRA: 20MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2558.300 | 40273 | - | - | - | - | - | - | +| | NR CC1 | 40 | 216 | Downlink & Uplink | IM3 | 2676.700 | 535340 | 2657.26 | 531452 | 0 | 15 | 6648 | 535340 | +| E-UTRA: 20MHz + NR: 50MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2524.900 | 39939 | - | - | - | - | - | - | +| | NR CC1 | 50 | 270 | Downlink & Uplink | IM3 | 2665.000 | 533000 | 2640.7 | 528140 | 0 | 15 | 6606 | 533000 | +| NR: 50MHz + E-UTRA: 20MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2666.700 | 41357 | - | - | - | - | - | - | +| | NR CC1 | 50 | 270 | Downlink & Uplink | IM3 | 2543.300 | 508660 | 2519 | 503800 | 0 | 15 | 6303 | 508660 | + +Table 6.2B.3.2.4.1-3: EN-DC combination DC\_41A\_n41A, intra-band non-contiguous, SCS 30 kHz, 30 kHz NR raster, IM3 test frequencies + +| EN-DC channel bandwidth combination | CC | Bandwidth [MHz] | carrierBandwidth [PRBs] | Range | | Carrier centre [MHz] Note 2 | Carrier centre [ARFCN] | point A [MHz] | absolute FrequencyPoint A [ARFCN] | offsetTo Carrier [Carrier PRBs] | SS block SCS [kHz] | GSC N | absoluteFrequency SSB [ARFCN] | +|-------------------------------------|------------|-----------------|-------------------------|-------------------|-----|-----------------------------|------------------------|---------------|-----------------------------------|---------------------------------|--------------------|-------|-------------------------------| +| E-UTRA: 20MHz + NR: 40MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2666.700 | 41357 | - | - | - | - | - | - | +| | NR CC1 | 40 | 106 | Downlink & Uplink | IM3 | 2548.300 | 509660 | 2529.22 | 505844 | 0 | 30 | 6333 | 509660 | +| NR: 40MHz + E-UTRA: 20MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2558.300 | 40273 | - | - | - | - | - | - | +| | NR CC1 | 40 | 106 | Downlink & Uplink | IM3 | 2676.700 | 535340 | 2657.62 | 531524 | 0 | 30 | 6654 | 535340 | +| E-UTRA: 20MHz + NR: 50MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2524.900 | 39939 | - | - | - | - | - | - | +| | NR CC1 | 50 | 133 | Downlink & Uplink | IM3 | 2665.000 | 533000 | 2641.06 | 528212 | 0 | 30 | 6612 | 533000 | +| NR: 50MHz + E-UTRA: 20MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2666.700 | 41357 | - | - | - | - | - | - | +| | NR CC1 | 50 | 133 | Downlink & Uplink | IM3 | 2543.300 | 508660 | 2519.36 | 503872 | 0 | 30 | 6309 | 508660 | + +Table 6.2B.3.2.4.1-4: EN-DC combination DC\_41A\_n41A, intra-band non-contiguous, SCS 60 kHz, 15 kHz NR raster, IM3 test frequencies + +| EN-DC channel bandwidth combination | CC | Bandwidth [MHz] | carrierBandwidth [PRBs] | Range | | Carrier centre [MHz] Note 2 | Carrier centre [ARFCN] | point A [MHz] | absolute FrequencyPoint A [ARFCN] | offsetTo Carrier [Carrier PRBs] | SS block SCS [kHz] | GSC N | absoluteFrequency SSB [ARFCN] | +|-------------------------------------|------------|-----------------|-------------------------|-------------------|-----|-----------------------------|------------------------|---------------|-----------------------------------|---------------------------------|--------------------|-------|-------------------------------| +| E-UTRA: 20MHz + NR: 40MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2666.700 | 41357 | - | - | - | - | - | - | +| | NR CC1 | 40 | 51 | Downlink & Uplink | IM3 | 2548.300 | 509660 | 2529.94 | 505988 | 0 | 15 | 6330 | 509660 | +| NR: 40MHz + E-UTRA: 20MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2558.300 | 40273 | - | - | - | - | - | - | +| | NR CC1 | 40 | 51 | Downlink & Uplink | IM3 | 2676.700 | 535340 | 2658.34 | 531668 | 0 | 15 | 6651 | 535340 | +| E-UTRA: 20MHz + NR: 50MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2524.900 | 39939 | - | - | - | - | - | - | +| | NR CC1 | 50 | 65 | Downlink & Uplink | IM3 | 2665.000 | 535340 | 2653.3 | 530660 | 0 | 15 | 6639 | 535340 | +| NR: 50MHz + E-UTRA: 20MHz | E-UTRA CC1 | 20 | 100 | Downlink & Uplink | IM3 | 2666.700 | 41357 | - | - | - | - | - | - | +| | NR CC1 | 50 | 65 | Downlink & Uplink | IM3 | 2543.300 | 508660 | 2519.9 | 503980 | 0 | 15 | 6306 | 508660 | + +Editor's note: The following lines belong at the end of clause 6.2B.3.2.4.1. As new tables are added to this clause, these lines should always follow the tables. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. NR downlink signals are initially set up according to Annex C.0, C.1, and C.2 and uplink signals according to Annex G.0, G.1, G.2, and G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for LTE link and NR link respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.3.2.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.3.2.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.2B.3.2.4.1-1 on both EN-DC component carriers. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{\text{UMAX}}$ level; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean power over all component carriers for the EN-DC configuration, which shall meet the requirements described in table 6.2B.3.2.5-1. The period of the measurement shall be at least the continuous duration of one sub-frame (1ms). + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.2B.3.1.4.1-2, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.3.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1, with the following exceptions. + +Table 6.2B.3.2.4.3-1: *RRConnectionReconfiguration: nr-Config-r15* + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Apply if run test points with E-UTRA UL transmission not overlapping with NR UL transmission in time for PC3 UE | +| | 20 | | Apply if run test points with E-UTRA UL transmission overlapping with NR UL transmission in time for PC3 UE, and UE doesn't support dynamic power sharing. | +| P-Max | 23 | | Apply if run test points with E-UTRA UL transmission not overlapping with NR UL transmission in time for PC3 UE | +| | 20 | | Apply if run test points with E-UTRA UL transmission overlapping with NR UL transmission in time for PC3 UE, and UE doesn't support dynamic power sharing. | + +6.2B.3.2.4.3-2: *SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band* + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.3.2.4.3-3: RRCConnectionReconfiguration: tdm-PatternConfig if E-UTRA on FDD band and UE does not support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|-----------------------------------------------------------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | Apply if run test points with E-UTRA UL transmission not overlapping with NR UL transmission in time for PC3 UE | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. + +###### 6.2B.3.2.4.3.1 Message contents exceptions (network signalled value "NS\_04") + +For "NS\_04" see A-MPR test case in table 6.2B.3.1.4.3.1-1 and table 6.2B.3.1.4.3.1-2. + +##### 6.2B.3.2.5 Test requirement + +The maximum output power, derived in step 3 shall be within the range prescribed by the nominal maximum output power and tolerance in Table 6.2B.3.2.5-0 to Table 6.2B.3.2.5-2a. The allowed A-MPR values specified in Table 6.2B.3.2.3-1 are in addition to the allowed MPR requirements specified in clause 6.2B.1.1.3. For the UE maximum output power modified by MPR and/or A-MPR, the power limits specified in Table 6.2B.1.1.3-1 apply. + +**Table 6.2B.3.2.5-0: Test Tolerance for UE maximum output power (LTE, NR TX separately)** + +| Uplink TX | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6\text{GHz}$ | +|-----------|-----------------------------------------------|------------------------|----------------------------------------|--------------------------------------| +| LTE | BW $\leq 20\text{MHz}$ | 0.7 dB | 1.0 dB | N/A | +| NR | BW $\leq 40\text{MHz}$ | 0.7 dB | 1.0 dB | 1.0 dB | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | 1.0 dB | 1.0 dB | 1.0 dB | + +**Table 6.2B.3.2.5-1: UE Power Class 3 test requirements for network signalled value "NS\_04"** + +| Test ID | Modulation | $\Delta P_{\text{PowerClass}}$ (dB) | MPR (dB) | A-MPR (dB) | A-MPR EN-DC (dB) | A-MPR c (dB) | $\Delta T_{C,c}$ (dB) Note 7 | $P_{\text{CMAX},c}$ (dBm) | $T(P_{\text{CMAX\_L},c})$ (dB) | $T_{L,c}$ (dB) | Upper limit | Lower limit | +|---------------------------------------------------------------------|------------------|-------------------------------------|----------|------------|-----------------------------|-------------------------|------------------------------|---------------------------|--------------------------------|----------------|-------------|-----------------| +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | E-UTRA Note 1 | 0 | 2 | 0 | 6 | 6 | 0 (1.5) | 17 (15.5) | 5 (5) | 2 (3.5) | 25+TT | 12-TT (10.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | E-UTRA Note 2 | 0 | 2 | 0 | 11 | 11 | 0 (1.5) | 12 (10.5) | 6 (6) | 2 (3.5) | 25+TT | 6-TT (4.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | NR, Note 1 | 0 | - | Note 5 | 6 | 6 | 0 (1.5) | 17 (15.5) | 5 (5) | 2 (3.5) | 25+TT | 12-TT (10.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | NR, Note 2 | 0 | - | Note 5 | 11 | 11 | 0 (1.5) | 12 (10.5) | 6 (6) | 2 (3.5) | 25+TT | 6-TT (4.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 1, 3 | 0 | 1 | Note 6 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 (7) | 2 (3.5) | 25+TT | 3-TT (0.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 1, 4 | 0 | 1 | Note 6 | 9 | 9 | 0 (1.5) | 14 (12.5) | 5 (6) | 2 (3.5) | 25+TT | 9-TT (6.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 2 | 0 | 1 | Note 6 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 | 2 (3.5) | 25+TT | 3-TT (0.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR Note 1, 3 | 0 | - | Note 5 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 (7) | 2 (3.5) | 25+TT | 3-TT (0.5-TT) | + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------|------------------|---|-----|--------|-----|-----|------------|--------------|------------|------------|-------|----------------------| +| 47 | | | | | | | | | | | | | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR
Note 1, 4 | 0 | - | Note 5 | 9 | 9 | 0
(1.5) | 14
(12.5) | 5
(6) | 2
(3.5) | 25+TT | 9-TT
(6.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR
Note 2 | 0 | - | Note 5 | 11 | 11 | 0
(1.5) | 9
(7.5) | 6
(6) | 2
(3.5) | 25+TT | 3-TT
(0.5-TT) | +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 | E-UTRA
Note 1 | 0 | 1 | Note 6 | 14 | 14 | 0
(1.5) | 9
(7.5) | 6
(7) | 2
(3.5) | 25+TT | 3-TT
(0.5-TT) | +| 3, 7, 10, 14, 17, 21, 30, 34, 37 and 41 | E-UTRA
Note 2 | 0 | 1 | Note 6 | 14 | 14 | 0
(1.5) | 9
(7.5) | 6
(7) | 2
(3.5) | 25+TT | 3-TT
(0.5-TT) | +| 4 | NR | 0 | 0.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 25+TT | 20.5-TT
(19-TT) | +| 6 | NR | 0 | 0 | Note 9 | 3.5 | 3.5 | 0
(1.5) | 19.5
(18) | 3.5
(4) | 2
(3.5) | 25+TT | 16-TT
(14-TT) | +| 11 | NR | 0 | 1 | Note 9 | 0 | 0 | 0
(1.5) | 22
(20.5) | 2
(2.5) | 2
(3.5) | 25+TT | 20-TT
(18-TT) | +| 13 | NR | 0 | 0 | Note 9 | 4 | 4 | 0
(1.5) | 19
(17.5) | 3.5
(5) | 2
(3.5) | 25+TT | 15.5-TT
(12.5-TT) | +| 18 | NR | 0 | 2 | Note 9 | 0 | 0 | 0
(1.5) | 21
(19.5) | 2
(3.5) | 2
(3.5) | 25+TT | 19-TT
(16-TT) | +| 20 | NR | 0 | 0 | Note 9 | 4 | 4 | 0
(1.5) | 19
(17.5) | 3.5
(5) | 2
(3.5) | 25+TT | 15.5-TT
(12.5-TT) | +| 31 | NR | 0 | 3 | Note 9 | 0 | 0 | 0
(1.5) | 20
(18.5) | 2.5
(4) | 2
(3.5) | 25+TT | 17.5-TT
(14.5-TT) | +| 33 | NR | 0 | 0 | Note 9 | 5.5 | 5.5 | 0
(1.5) | 17.5
(16) | 5
(5) | 2
(3.5) | 25+TT | 12-TT
(11-TT) | +| 38 | NR | 0 | 3 | Note 9 | 0 | 0 | 0
(1.5) | 20
(18.5) | 2.5
(4) | 2
(3.5) | 25+TT | 17.5-TT
(14.5-TT) | +| 40 | NR | 0 | 0 | Note 9 | 5.5 | 5.5 | 0
(1.5) | 17.5
(16) | 5
(5) | 2
(3.5) | 25+TT | 12-TT
(11-TT) | + +NOTE 1: When $F_{IM3,low\_block,low} \geq 2490.5$ MHz (Case A)NOTE 2: When $F_{IM3,low\_block,low} < 2490.5$ MHz (Case B) + +NOTE 3: When NR SCS = 15kHz. + +NOTE 4: When NR SCS = 30 kHz or 60 kHz. + +NOTE 5: NR A-MPR values for NS\_04 are defined in Table 6.2.3.3.2-1. + +NOTE 6: E-UTRA A-MPR= 3 dB for 1 RB and $f_c < 2517.5$ MHz, otherwise 0 dB. + +NOTE 7: $\Delta T_{C,c} = 1.5$ dB for transmission bandwidths confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , otherwise 0 dB. + +NOTE 8: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.2.5-0. + +NOTE 9: Apply for UE supporting dynamic power sharing. NR A-MPR values for NS\_04 are defined in TS 38.101-1 [2]. + +**Table 6.2B.3.2.5-2: UE Power Class 2 test requirements for network signalled value "NS\_04" (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by *powerClassNRPart-r16*))** + +| Test ID | Modulation | $\Delta P_{\text{PowerClass}}$ (dB) | MPR (dB) | A-MPR (dB) | A-MPR EN-DC (dB) | A-MPR c (dB) | $\Delta T_{C,c}$ (dB) Note 7 | $P_{\text{CMAX},c}$ (dBm) | $T(P_{\text{CMAX\_L},f,c})$ (dB) | $T_{L,c}$ (dB) | Upper limit | Lower limit | +|---------------------------------------------------------------------|------------------|-------------------------------------|----------|------------|-----------------------------|-------------------------|------------------------------|---------------------------|----------------------------------|----------------|-------------|-----------------| +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | E-UTRA Note 1 | 3 | 2 | 0 | 6 | 6 | 0 (1.5) | 17 (15.5) | 5 (5) | 2 (3.5) | 28+TT | 12-TT (10.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | E-UTRA Note 2 | 3 | 2 | 0 | 11 | 11 | 0 (1.5) | 12 (10.5) | 6 (6) | 2 (3.5) | 28+TT | 6-TT (4.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | NR, Note 1 | 3 | - | Note 5 | 6 | 6 | 0 (1.5) | 17 (15.5) | 5 (5) | 2 (3.5) | 28+TT | 12-TT (10.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | NR, Note 2 | 3 | - | Note 5 | 11 | 11 | 0 (1.5) | 12 (10.5) | 6 (6) | 2 (3.5) | 28+TT | 6-TT (4.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 1, 3 | 3 | 1 | Note 6 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 (7) | 2 (3.5) | 28+TT | 3-TT (0.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 1, 4 | 3 | 1 | Note 6 | 9 | 9 | 0 (1.5) | 14 (12.5) | 5 (6) | 2 (3.5) | 28+TT | 9-TT (6.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 2 | 3 | 1 | Note 6 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 | 2 (3.5) | 28+TT | 3-TT (0.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and | NR Note 1, 3 | 3 | - | Note 5 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 (7) | 2 (3.5) | 28+TT | 3-TT (0.5-TT) | + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------|------------------|---|-----|--------|-----|-----|------------|--------------|--------------|------------|-------|----------------------| +| 47 | | | | | | | | | | | | | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR
Note 1, 4 | 3 | - | Note 5 | 9 | 9 | 0
(1.5) | 14
(12.5) | 5
(6) | 2
(3.5) | 28+TT | 9-TT
(6.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR
Note 2 | 3 | - | Note 5 | 11 | 11 | 0
(1.5) | 9
(7.5) | 6
(6) | 2
(3.5) | 28+TT | 3-TT
(0.5-TT) | +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 | E-UTRA
Note 1 | 0 | 1 | Note 6 | 14 | 14 | 0
(1.5) | 9
(7.5) | 6
(7) | 2
(3.5) | 28+TT | 3-TT
(0.5-TT) | +| 3, 7, 10, 14, 17, 21, 30, 34, 37 and 41 | E-UTRA
Note 2 | 0 | 1 | Note 6 | 14 | 14 | 0
(1.5) | 9
(7.5) | 6
(7) | 2
(3.5) | 28+TT | 3-TT
(0.5-TT) | +| 4 | NR | 0 | 3.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 28+TT | 20.5-TT
(19-TT) | +| 6 | NR | 0 | 0 | Note 9 | 5.5 | 5.5 | 0
(1.5) | 20.5
(19) | 2.5
(3.5) | 2
(3.5) | 28+TT | 18-TT
(15.5-TT) | +| 11 | NR | 0 | 3.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 28+TT | 20.5-TT
(19-TT) | +| 13 | NR | 0 | 0 | Note 9 | 6 | 6 | 0
(1.5) | 20
(18.5) | 2.5
(4) | 2
(3.5) | 28+TT | 17.5-TT
(14.5-TT) | +| 18 | NR | 0 | 3.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 28+TT | 20.5-TT
(19-TT) | +| 20 | NR | 0 | 0 | Note 9 | 6 | 6 | 0
(1.5) | 20
(18.5) | 2.5
(4) | 2
(3.5) | 28+TT | 17.5-TT
(14.5-TT) | +| 31 | NR | 0 | 3.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 28+TT | 20.5-TT
(19-TT) | +| 33 | NR | 0 | 0 | Note 9 | 7.5 | 7.5 | 0
(1.5) | 18.5
(17) | 4
(5) | 2
(3.5) | 28+TT | 14.5-TT
(12-TT) | +| 38 | NR | 0 | 3.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 28+TT | 20.5-TT
(19-TT) | +| 40 | NR | 0 | 0 | Note 9 | 7.5 | 7.5 | 0
(1.5) | 18.5
(17) | 4
(5) | 2
(3.5) | 28+TT | 14.5-TT
(12-TT) | + +NOTE 1: When $F_{IM3,low\_block,low} \geq 2490.5$ MHz (Case A).NOTE 2: When $F_{IM3,low\_block,low} < 2490.5$ MHz (Case B). + +NOTE 3: When NR SCS = 15kHz. + +NOTE 4: When NR SCS = 30 kHz or 60 kHz. + +NOTE 5: NR A-MPR values for NS\_04 are defined in Table 6.2.3.3.2-1. + +NOTE 6: E-UTRA A-MPR= 3 dB for 1 RB and $f_c < 2517.5$ MHz, otherwise 0 dB.NOTE 7: $\Delta T_{C,c} = 1.5$ dB for transmission bandwidths confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , otherwise 0 dB. + +NOTE 8: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.2.5-0. + +NOTE 9: Apply for UE supporting dynamic power sharing. NR A-MPR values for NS\_04 are defined in TS 38.101-1 [24]. + +**Table 6.2B.3.2.5-2a: UE Power Class 2 test requirements for network signalled value "NS\_04" (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by $\text{powerClassNRPart-r16}$ ))** + +| Test ID | Modulation | $\Delta P_{\text{PowerClass}}$ (dB) | MPR (dB) | A-MPR (dB) | A-MPR EN-DC (dB) | A-MPR c (dB) | $\Delta T_{C,c}$ (dB) Note 7 | $P_{\text{CMAX},c}$ (dBm) | $T(P_{\text{CMAX\_L},f,c})$ (dB) | $T_{L,c}$ (dB) | Upper limit | Lower limit | +|---------------------------------------------------------------------|------------------|-------------------------------------|----------|------------|-----------------------------|-------------------------|------------------------------|---------------------------|----------------------------------|----------------|-------------|-----------------| +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | E-UTRA Note 1 | 3 | 2 | 0 | 6 | 6 | 0 (1.5) | 17 (15.5) | 5 (5) | 2 (3.5) | 28+TT | 12-TT (10.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | E-UTRA Note 2 | 3 | 2 | 0 | 11 | 11 | 0 (1.5) | 12 (10.5) | 6 (6) | 2 (3.5) | 28+TT | 6-TT (4.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | NR, Note 1 | 3 | - | Note 5 | 6 | 6 | 0 (1.5) | 17 (15.5) | 5 (5) | 2 (3.5) | 28+TT | 12-TT (10.5-TT) | +| 1, 8, 15, 22, 25, 28, 35, 42 and 45 | NR, Note 2 | 3 | - | Note 5 | 11 | 11 | 0 (1.5) | 12 (10.5) | 6 (6) | 2 (3.5) | 28+TT | 6-TT (4.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 1, 3 | 3 | 1 | Note 6 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 (7) | 2 (3.5) | 28+TT | 3-TT (0.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 1, 4 | 3 | 1 | Note 6 | 9 | 9 | 0 (1.5) | 14 (12.5) | 5 (6) | 2 (3.5) | 28+TT | 9-TT (6.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | E-UTRA Note 2 | 3 | 1 | Note 6 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 | 2 (3.5) | 28+TT | 3-TT (0.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and | NR Note 1, 3 | 3 | - | Note 5 | 14 | 14 | 0 (1.5) | 9 (7.5) | 6 (7) | 2 (3.5) | 28+TT | 3-TT (0.5-TT) | + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------|------------------|---|-----|--------|-----|-----|------------|--------------|------------|------------|-------|----------------------| +| 47 | | | | | | | | | | | | | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR
Note 1, 4 | 3 | - | Note 5 | 9 | 9 | 0
(1.5) | 14
(12.5) | 5
(6) | 2
(3.5) | 28+TT | 9-TT
(6.5-TT) | +| 2, 5, 9, 16, 19, 23, 24, 26, 27, 29, 32, 36, 39, 43, 44, 46, and 47 | NR
Note 2 | 3 | - | Note 5 | 11 | 11 | 0
(1.5) | 9
(7.5) | 6
(6) | 2
(3.5) | 28+TT | 3-TT
(0.5-TT) | +| 3, 7, 10, 14, 17, 21, 30, 34, 37, 41 | E-UTRA
Note 1 | 3 | 1 | Note 6 | 14 | 14 | 0
(1.5) | 9
(7.5) | 6
(7) | 2
(3.5) | 28+TT | 3-TT
(0.5-TT) | +| 3, 7, 10, 14, 17, 21, 30, 34, 37 and 41 | E-UTRA
Note 2 | 3 | 1 | Note 6 | 14 | 14 | 0
(1.5) | 9
(7.5) | 6
(7) | 2
(3.5) | 28+TT | 3-TT
(0.5-TT) | +| 4 | NR | 0 | 0.5 | Note 9 | 0 | 0 | 0
(1.5) | 22.5
(21) | 2
(2) | 2
(3.5) | 25+TT | 20.5-TT
(19-TT) | +| 6 | NR | 0 | 0 | Note 9 | 3.5 | 3.5 | 0
(1.5) | 19.5
(18) | 3.5
(4) | 2
(3.5) | 25+TT | 16-TT
(14-TT) | +| 11 | NR | 0 | 1 | Note 9 | 0 | 0 | 0
(1.5) | 22
(20.5) | 2
(2.5) | 2
(3.5) | 25+TT | 20-TT
(18-TT) | +| 13 | NR | 0 | 0 | Note 9 | 4 | 4 | 0
(1.5) | 19
(17.5) | 3.5
(5) | 2
(3.5) | 25+TT | 15.5-TT
(12.5-TT) | +| 18 | NR | 0 | 2 | Note 9 | 0 | 0 | 0
(1.5) | 21
(19.5) | 2
(3.5) | 2
(3.5) | 25+TT | 19-TT
(16-TT) | +| 20 | NR | 0 | 0 | Note 9 | 4 | 4 | 0
(1.5) | 19
(17.5) | 3.5
(5) | 2
(3.5) | 25+TT | 15.5-TT
(12.5-TT) | +| 31 | NR | 0 | 3 | Note 9 | 0 | 0 | 0
(1.5) | 20
(18.5) | 2.5
(4) | 2
(3.5) | 25+TT | 17.5-TT
(14.5-TT) | +| 33 | NR | 0 | 0 | Note 9 | 5.5 | 5.5 | 0
(1.5) | 17.5
(16) | 5
(5) | 2
(3.5) | 25+TT | 12-TT
(11-TT) | +| 38 | NR | 0 | 3 | Note 9 | 0 | 0 | 0
(1.5) | 20
(18.5) | 2.5
(4) | 2
(3.5) | 25+TT | 17.5-TT
(14.5-TT) | +| 40 | NR | 0 | 0 | Note 9 | 5.5 | 5.5 | 0
(1.5) | 17.5
(16) | 5
(5) | 2
(3.5) | 25+TT | 12-TT
(11-TT) | + +NOTE 1: When $F_{IM3,low\_block,low} \geq 2490.5$ MHz (Case A).NOTE 2: When $F_{IM3,low\_block,low} < 2490.5$ MHz (Case B). + +NOTE 3: When NR SCS = 15kHz. + +NOTE 4: When NR SCS = 30 kHz or 60 kHz. + +NOTE 5: NR A-MPR values for NS\_04 are defined in Table 6.2.3.3.2-1. + +NOTE 6: E-UTRA A-MPR= 3 dB for 1 RB and $f_c < 2517.5$ MHz, otherwise 0 dB.NOTE 7: $\Delta T_{C,c} = 1.5$ dB for transmission bandwidths confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , otherwise 0 dB. + +NOTE 8: TT for each frequency and channel bandwidth is specified in Table 6.2B.3.2.5-0. + +NOTE 9: Apply for UE supporting dynamic power sharing. NR A-MPR values for NS\_04 are defined in TS 38.101-1 [2]. + +#### 6.2B.3.3 UE Additional Maximum Output Power reduction for Inter-Band EN-DC within FR1 (1 NR CC) + +##### 6.2B.3.3.1 Test purpose + +Same test purpose as in clause 6.2.3.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.2B.3.3.2 Test applicability + +The requirements of this test apply to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +NOTE: Test execution is not necessary if clause 6.5B.2.3.2, 6.5B.2.3.3.2 and 6.5B.4.3 are executed since A-MPR requirements are verified in these test cases. + +##### 6.2B.3.3.3 Minimum conformance requirements + +For inter-band EN-DC between E-UTRA and NR FR1, UE additional maximum output power reduction specified in TS 36.101 [5] and TS 38.101-1 [2] apply for E-UTRA and NR respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.3.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied + +##### 6.2B.3.3.4 Test description + +Same test description as in clause 6.2.3.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.2.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 6.2B.3.3.4-1. +- 3.1. Downlink E-UTRA signals are initially set up according to TS 36.521-1 [10] Annex C0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0. +- 4.1. The E-UTRA UL Reference Measurement channels are set according to Table 6.2B.3.3.4-1. + +Step 6 of Initial conditions as in clause 6.2.3.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. Same test procedure as in clause 6.2.3.4.2 in TS 38.521-1 [8]. + +##### 6.2B.3.3.5 Test requirement + +For PC3 UE, same test requirement as in clause 6.2.2.5 in TS 38.521-1 [8]. + +For PC2 UE (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by *powerClassNRPart-r16*)), same test requirement for PC2 UE as in clause 6.2.3.5 in TS 38.521-1 [8]. For PC2 UE (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by *powerClassNRPart-r16*)), same test requirement for PC3 UE as in clause 6.2.3.5 in TS 38.521-1 [8]. + +#### 6.2B.3.4 UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) + +##### 6.2B.3.4.1 Test purpose + +Same test purpose as in clause 6.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.2B.3.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.2B.3.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.2B.3.4.4 Test description + +###### 6.2B.3.4.4.1 Initial conditions + +Same test description as in clause 6.2.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +###### 6.2B.3.4.4.2 Test procedure + +Same test procedure as in clause 6.2.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.3.4.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] clause 4.6 with the following exceptions for each network signalled value. + +1. Information element AdditionalSpectrumEmission for NR can be set in *nr-SecondaryCellGroupConfig* according to TS 38.331 [15]. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.2B.3.4.4.3-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement** + +| Derivation Path: TS 38.508-1 [5] clause 4.6.3, Table 4.6.3-1 | | | | +|--------------------------------------------------------------|--------------|---------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 1 (NS_202) | for band n257 | | +| AdditionalSpectrumEmission | 2 (NS_202) | for band n258 | | +| AdditionalSpectrumEmission | 3 (NS_203) | for band n258 | | + +##### 6.2B.3.4.5 Test requirement + +Same test requirement as in clause 6.2.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.2B.3.4D UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.2D.3 in TS 38.521-2 [9] is incomplete + +##### 6.2B.3.4D.1 Test purpose + +Same test purpose as in clause 6.2D.3.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.2B.3.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC with UL MIMO. + +##### 6.2B.3.4D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.2D.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +##### 6.2B.3.4D.4 Test description + +###### 6.2B.3.4D.4.1 Initial conditions + +Same test description as in clause 6.2D.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.2D.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2D.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +###### 6.2B.3.4D.4.2 Test procedure + +Same test procedure as in clause 6.2D.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.3.4D.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] clause 4.6 ensuring Table 4.6.3-182 with condition 2TX\_UL\_MIMO, with the following exceptions for each network signalled value. + +1. Information element AdditionalSpectrumEmission for NR can be set in *nr-SecondaryCellGroupConfig* according to TS 38.331 [15]. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.2B.3.4D.4.3-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement** + +| Derivation Path: TS 38.508-1 [5] clause 4.6.3, Table 4.6.3-1 | | | | +|--------------------------------------------------------------|--------------|---------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 1 (NS_202) | for band n257 | | +| AdditionalSpectrumEmission | 2 (NS_202) | for band n258 | | +| AdditionalSpectrumEmission | 3 (NS_203) | for band n258 | | + +###### 6.2B.3.4D.5 Test requirement + +Same test requirement as in clause 6.2D.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.2B.3.5 UE Additional Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 + +##### 6.2B.3.5.1 Test purpose + +Same test purpose as in clause 6.2.3.1 in TS 38.521-1 [8] for NR FR1 carrier and clause 6.2.3.1 in TS 38.521-2 [9] for NR FR2 carrier. + +##### 6.2B.3.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for Additional Maximum Output Power apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.2B.3. + +#### 6.2B.3.5D UE Additional Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 for UL MIMO + +##### 6.2B.3.5D.1 Test purpose + +Same test purpose as in clause 6.2D.3.1 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.2D.3.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.2B.3.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum output power apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.2B. + +### 6.2B.4 Configured Output Power for EN-DC + +#### 6.2B.4.1 Configured Output Power Level for EN-DC + +##### 6.2B.4.1.0 Minimum Conformance Requirements + +###### 6.2B.4.1.0.1 Configured output power level + +###### 6.2B.4.1.0.1.1 Intra-band contiguous EN-DC + +The following requirements apply for one component carrier per CG configured for synchronous DC. + +For intra-band dual connectivity with one uplink serving cell per CG on E-UTRA and NR respectively, the UE is allowed to set its configured maximum output power $P_{\text{CMAX},c(i)}$ for serving cell $c(i)$ of CG $i$ , $i = 1, 2$ , and its total configured maximum transmission power for EN-DC operation = $10\log_{10}()$ with as specified in clause 7.6 of TS 38.213 [19]. + +The configured maximum output power $P_{\text{CMAX\_E-UTRA},c}(p)$ in sub-frame $p$ for the configured E-UTRA uplink carrier shall be set within the bounds: + +$$P_{\text{CMAX\_L\_E-UTRA},c}(p) \leq P_{\text{CMAX\_E-UTRA},c}(p) \leq P_{\text{CMAX\_H\_E-UTRA},c}(p)$$ + +where $P_{\text{CMAX\_L\_E-UTRA},c}$ and $P_{\text{CMAX\_H\_E-UTRA},c}$ are the limits for a serving cell $c$ as specified in TS 36.101 [5] clause 6.2.5 modified by $P_{\text{LTE}}$ as follows: + +$$P_{\text{CMAX\_L\_E-UTRA},c} = \text{MIN} \{ \text{MIN}(P_{\text{EMAX},c}, P_{\text{EMAX\_EN-DC}}, P_{\text{LTE}}) - \Delta t_{\text{C\_E-UTRA},c}, (P_{\text{PowerClass\_EN-DC}} - \Delta P_{\text{PowerClass\_EN-DC}}), (P_{\text{PowerClass}} - \Delta P_{\text{PowerClass}}) - \text{MAX}(\text{MPR}_c + \text{A-MPR}_c + \Delta T_{\text{IB},c} + \Delta T_{\text{C\_E-UTRA},c} + \Delta T_{\text{ProSe}}, P\text{-MPR}_c) \}$$ + +$$P_{\text{CMAX\_H\_E-UTRA},c} = \text{MIN} \{ P_{\text{EMAX},c}, P_{\text{EMAX\_EN-DC}}, P_{\text{LTE}}, P_{\text{PowerClass\_EN-DC}}, P_{\text{PowerClass}} - \Delta P_{\text{PowerClass}} \}$$ + +where + +- $P_{\text{EMAX\_EN-DC}}$ is the value given by the field *p-maxUE-FR1* of the *RRCConnectionReconfiguration-v1530* IE as defined in TS 36.331 [17]; +- $P_{\text{LTE}}$ is the value given by the field *p-maxEUTRA-r15* of the *RRCConnectionReconfiguration-v1510* IE as defined in TS 36.331 [17] which is the same as $P_{\text{LTE}}$ in TS 38.213 [19]; + +- $\Delta T_{C\_EUTRA, c} = 1.5$ dB when NOTE 2 in Table 6.2.2-1 of TS 36.101 [5] applies; $\Delta T_{C\_EUTRA, c} = 0$ dB otherwise; + +and whenever NS\_01 is not indicated within CG 1: + +- for a UE indicating support of dynamicPowerSharing, the $MPR_c$ and the $A-MPR_c$ are determined in accordance with the DCI of serving cell $c$ of the CG 1 and the specification in clause 6.2.4 of TS 36.101 [5]; +- for a UE not indicating support of dynamicPowerSharing, the $A-MPR_c$ is determined in accordance with clause 6.2B.3.1 with parameters applicable for UEs not indicating support of dynamicPowerSharing and $MPR_c = 0$ dB; + +and whenever NS\_01 is indicated in CG 1: + +- for a UE indicating support of dynamicPowerSharing, the $MPR_c$ is determined in accordance with the DCI of serving cell $c$ of the CG 1 and the specification in clause 6.2.4 of TS 36.101 [5]; +- for a UE not indicating support of dynamicPowerSharing, the $MPR_c$ is determined in accordance with clause 6.2B.2.1 with parameters applicable for UEs not indicating support of dynamicPowerSharing and $A-MPR_c = 0$ dB; + +The configured maximum output power $P_{CMAX\_NR, c}(q)$ in physical channel $q$ for the configured NR carrier shall be set within the bounds: + +$$P_{CMAX\_L, f, c, NR}(q) \leq P_{CMAX, f, c, NR}(q) \leq P_{CMAX\_H, f, c, NR}(q)$$ + +where $P_{CMAX\_L\_NR, c}$ and $P_{CMAX\_H\_NR, c}$ are the limits for a serving cell $c$ as specified in clause 6.2.4 of TS 38.101-1 [2] modified as follows: + +$$P_{CMAX\_L, f, c, NR} = \text{MIN} \{ \text{MIN}(P_{EMAX, c}, P_{EMAX\_EN-DC}, P_{NR}) - \Delta T_{C\_NR, c}, (P_{PowerClass\_EN-DC} - \Delta P_{PowerClass\_EN-DC}), (P_{PowerClass} - \Delta P_{PowerClass}) - \text{MAX}(\text{MAX}(MPR_c, A-MPR_c) + \Delta T_{IB, c} + \Delta T_{C\_NR, c} + \Delta T_{RxSRS}, P-MPR_c) \}$$ + +$$P_{CMAX\_H, f, c, NR} = \text{MIN} \{ P_{EMAX, c}, P_{EMAX\_EN-DC}, P_{NR}, P_{PowerClass\_EN-DC}, P_{PowerClass} - \Delta P_{PowerClass} \}$$ + +where + +- $P_{EMAX\_EN-DC}$ is the value given by the field *p-maxUE-FR1* of the *RRConnectionReconfiguration-v1530* IE as defined in TS 36.331 [17]; +- $P_{LTE}$ signalled by RRC as *p-MaxEUTRA-r15* in TS 36.331 [17] +- $P_{NR}$ is the value given by the field *p-NR-FR1* of the *PhysicalCellGroupConfig* IE as defined in [18] and signalled by RRC; +- $\Delta T_{C\_E-UTRA, c} = 1.5$ dB when NOTE 2 in Table 6.2.2-1 in TS 36.101 [4] applies for a serving cell $c$ , otherwise $\Delta T_{C\_E-UTRA, c} = 0$ dB; +- $\Delta T_{C\_NR, c} = 1.5$ dB when NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] applies for a serving cell $c$ , otherwise $\Delta T_{C\_NR, c} = 0$ dB; +- $\Delta T_{IB, c}$ specified in clause 6.2B.4.2.1 for EN-DC, the individual Power Class defined in table 6.2B.1.1 and any other additional power reductions parameters specified in clauses 6.2B.2 and 6.2B.3 for EN-DC are applicable to $P_{CMAX\_E-UTRA, c}$ and $P_{CMAX, f, c, NR}$ evaluations. + +$P_{PowerClass\_EN-DC}$ is defined in clause 6.2B.1.1 for intra-band contiguous EN-DC; + +- $P_{PowerClass\_NR}$ is the nominal UE power of the power class that the UE supports for the NR band of the EN-DC combination as defined in clause 6.2.1 of 38.101-1 [2]; in case IE *[powerClassNRPart]* as defined in TS 38.331 [18] is indicated, $P_{PowerClass\_NR}$ should use that value instead. + +- $P_{\text{PowerClass,E-UTRA}}$ is the nominal UE power of the power class that the UE supports for the E-UTRA band of the EN-DC combination as defined in clause 6.2.2 of 36.101 [5];- + +$\Delta P_{\text{PowerClass,EN-DC}}$ is 3 dB for a power class 2 capable EN-DC UE when LTE UL/DL configuration is 0 or 6; or LTE UL/DL configuration is 1 and special subframe configuration is 0 or 5; $\Delta P_{\text{PowerClass,EN-DC}} = 3$ dB when the IE *p-maxUE-FRI* as defined in TS 36.331 [17] is provided and set to the maximum output power of the default power class or lower; $\Delta P_{\text{PowerClass,EN-DC}}$ is 6 dB for a power class 1.5 capable EN-DC UE when the LTE UL duty cycle is greater than $\max(50\%, \max\text{UplinkDutyCycle})$ ; $\Delta P_{\text{PowerClass,EN-DC}}$ is 3 dB for a power class 1.5 capable EN-DC UE when the LTE UL duty cycle is between $\max(50\%, \max\text{UplinkDutyCycle})$ and $\max(25\%, \max\text{UplinkDutyCycle}/2)$ ; otherwise $\Delta P_{\text{PowerClass,EN-DC}} = 0$ dB; + +and whenever NS\_01 is not indicated within CG 2: + +- for a UE indicating support of dynamicPowerSharing, $A\text{-MPR}_c = A\text{-MPR}'_c$ with $A\text{-MPR}'_c$ determined in accordance with clause 6.2B.3.1 and $\text{MPR}_c = 0$ dB if transmission(s) in subframe $p$ on CG 1 overlap in time with physical channel $q$ on CG 2; +- for a UE indicating support of dynamicPowerSharing, $A\text{-MPR}_c$ is determined in accordance with TS 38.101-1 [2] if transmission(s) in subframe $p$ on CG 1 does not overlap in time with physical channel $q$ on CG 2; +- for a UE not indicating support of dynamicPowerSharing, the $A\text{-MPR}_c$ is determined in accordance with clause 6.2B.3.1 with parameters applicable for UEs not indicating support of dynamicPowerSharing and $\text{MPR}_c = 0$ dB; + +and whenever NS\_01 is indicated in CG 2: + +- for a UE indicating support of dynamicPowerSharing, $\text{MPR}_c = \text{MPR}'_c$ with $\text{MPR}'_c$ determined in accordance with clause 6.2B.2.1 and $A\text{-MPR}_c = 0$ dB if transmission(s) in subframe $p$ on CG 1 overlap in time with physical channel $q$ on CG 2; +- for a UE indicating support of dynamicPowerSharing, $\text{MPR}_c$ is determined in accordance with TS 38.101-1 [2] if transmission(s) in subframe $p$ on CG 1 does not overlap in time with physical channel $q$ on CG 2; +- for a UE not indicating support of dynamicPowerSharing, the $\text{MPR}_c$ is determined in accordance with clause 6.2B.2.1 with parameters applicable for UEs not indicating support of dynamicPowerSharing and $A\text{-MPR}_c = 0$ dB; + +If the transmissions from NR and E-UTRA do not overlap, then the complete clauses for configured transmitted power for E-UTRA and NR respectively from their own specifications apply with the modifications specified above. The lower value between $P_{\text{PowerClass,EN-DC}}$ or $P_{\text{EMAX,EN-DC}}$ shall not be exceeded at any time by UE. + +If the EN-DC UE is not supporting dynamic power sharing, then the complete clauses for configured transmitted power for E-UTRA and NR respectively from their own specifications TS 36.101 [5] and TS 38.101-1 [2] respectively apply with the modifications specified above. + +If the UE does not support dynamic power sharing, + +$$= \text{MIN} \{ P_{\text{EMAX,EN-DC}}, P_{\text{PowerClass,EN-DC}} - \Delta P_{\text{PowerClass,EN-DC}} \} + 0.3 \text{ dB}$$ + +For UEs indicating support of dynamicPowerSharing in the *UE-MRDC-Capability* IE the UE can configure the total maximum transmission power within the range + +$$P_{\text{EN-DC,tot\_L}} \leq P_{\text{EN-DC,tot\_H}}$$ + +where + +$$P_{\text{EN-DC,tot\_L}}(p,q) = \text{MIN} \{ P_{\text{PowerClass,EN-DC}} - \Delta P_{\text{PowerClass,EN-DC}} - \text{MAX} \{ \text{MPR}_{\text{tot}}, A\text{-MPR}_{\text{tot}} \}, P_{\text{EMAX,EN-DC}} \}$$ + +$$P_{EN-DC,tot\_H}(p,q) = \text{MIN}\{P_{PowerClass,EN-DC}, P_{EMAX,EN-DC}\}$$ + +for sub-frame $p$ on CG 1 overlapping with physical channel $q$ on CG 2 and with $MPR_{tot}$ and $A-MPR_{tot}$ in accordance with 6.2B.2.1 and clause 6.2B.3.1, respectively. + +The measured total maximum output power $P_{UMAX}$ over both CGs/RATs, measured over the transmission reference time duration is + +$$P_{UMAX} = 10 \log_{10} [p_{UMAX,c,E-UTRA} + p_{UMAX,f,c,NR}],$$ + +where $p_{UMAX,c,E-UTRA}$ and $p_{UMAX,c,NR}$ denotes the measured output power of serving cell $c$ for *E-UTRA* and *NR* respectively, expressed in linear scale. + +For UEs indicating support of dynamicPowerSharing, the measured total configured maximum output power $P_{UMAX}$ shall be within the following bounds: + +$$P_{CMAX\_L} - T_{LOW}(P_{CMAX\_L}) \leq P_{UMAX} \leq P_{CMAX\_H} + T_{HIGH}(P_{CMAX\_H})$$ + +with the tolerances $T_{LOW}(P_{CMAX\_L})$ and $T_{HIGH}(P_{CMAX\_H})$ for applicable values of $P_{CMAX\_L}$ and $P_{CMAX\_H}$ specified in Table 6.2B.4.1.0.1.1-2. + +When an UL subframe transmission $p$ from E-UTRA overlap with a physical channel $q$ from the NR, then for $P_{UMAX}$ evaluation, the E-UTRA subframe $p$ is taken as reference period $T_{REF}$ and always considered as the reference measurement duration and the following rules are applicable. + +$T_{REF}$ and $T_{eval}$ are specified in Table 6.2B.4.1.0.1.1-1 when same or different subframes and physical channel durations are used in aggregated carriers. $P_{PowerClass,EN-DC}$ shall not be exceeded by the UE during any evaluation period of time. + +**Table 6.2B.4.1.0.1.1-1: $P_{CMAX}$ evaluation window** + +| transmission duration | $T_{REF}$ | $T_{eval}$ | +|-----------------------------------------------------------|-----------------|---------------------------------------------------------------| +| Different transmission duration in different RAT carriers | E-UTRA Subframe | $\text{Min}(T_{no\_hopping}, \text{Physical Channel Length})$ | + +For each $T_{REF}$ , the $P_{CMAX\_H}$ is evaluated per $T_{eval}$ and given by the maximum value over the transmission(s) within the $T_{eval}$ as follows: + +$$P_{CMAX\_H} = \text{MAX} \{ P_{CMAX\_EN-DC\_H}(p,q), P_{CMAX\_EN-DC\_H}(p,q+1), \dots, P_{CMAX\_EN-DC\_H}(p,q+n) \}$$ + +where $P_{CMAX\_EN-DC\_H}$ are the applicable upper limits for each overlapping scheduling unit pairs $(p,q)$ , $(p,q+1)$ , up to $(p,q+n)$ for each applicable $T_{eval}$ duration, where $q+n$ is the last NR UL physical channel overlapping with LTE subframe $p$ . + +While $P_{CMAX\_L}$ is computed as follows: + +$$P_{CMAX\_L} = \text{MIN} \{ P_{CMAX\_EN-DC\_L}(p,q), P_{CMAX\_EN-DC\_L}(p,q+1), \dots, P_{CMAX\_EN-DC\_L}(p,q+n) \}$$ + +where $P_{CMAX\_EN-DC\_L}$ are the applicable lower limits for each overlapping scheduling unit pairs $(p,q)$ , $(p,q+1)$ , up to $(p,q+n)$ for each applicable $T_{eval}$ duration, where $q+n$ is the last NR UL physical channel overlapping with E-UTRA subframe $p$ , + +With + +$$P_{CMAX\_EN-DC\_H}(p,q) = \text{MIN} \{ 10 \log_{10} [p_{CMAX\_H,E-UTRA,c}(p) + p_{CMAX\_H,f,c,NR,c}(q)], P_{EMAX,EN-DC}, P_{PowerClass,EN-DC} \}$$ + +And: + +$$a = 10 \log_{10} [p_{CMAX\_E-UTRA,c}(p) + p_{CMAX\_f,c,NR}(q)] > P_{EN-DC,tot\_L}$$ + +$$b = 10 \log_{10} [p_{\text{CMAX\_E-UTRA},c}(p) + p_{\text{CMAX},f,c,NR}(q) / X\_scale] > P_{\text{EN-DC,tot\_L}}$$ + +If a= FALSE and the configured transmission power spectral density between the MCG and SCG differs by less than 6 dB + +$$P_{\text{CMAX\_EN-DC\_L}}(p,q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_L\_E-UTRA},c}(p) + p_{\text{CMAX\_L},f,c,NR}(q)], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} - \Delta P_{\text{PowerClass\_EN-DC}} \}$$ + +ELSE If (a=TRUE) AND (b=FALSE) and the configured transmission power spectral density between the MCG and SCG differs by less than 6 dB + +$$P_{\text{CMAX\_EN-DC\_L}}(p,q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_L\_E-UTRA},c}(p) + p_{\text{CMAX\_L},f,c,NR}(q) / X\_scale], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} - \Delta P_{\text{PowerClass\_EN-DC}} \}$$ + +ELSE If b= TRUE or the transmission power after power scaling spectral density between the MCG and SCG differs by more than 6 dB + +$$P_{\text{CMAX\_EN-DC\_L}}(p,q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_L\_E-UTRA},c}(p)], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} - \Delta P_{\text{PowerClass\_EN-DC}} \}$$ + +where + +- $p_{\text{CMAX\_H\_E-UTRA},c}(p)$ is the E-UTRA higher limit of the maximum configured power expressed in linear scale; +- $p_{\text{CMAX\_H\_NR},c}(q)$ is the NR higher limit of the maximum configured power expressed in linear scale; +- $p_{\text{CMAX\_L\_E-UTRA},c}(p)$ is the E-UTRA lower limit of the maximum configured power expressed in linear scale; +- $p_{\text{CMAX\_L\_NR},c}(q)$ is the NR lower limit of the maximum configured power expressed in linear scale; +- $P_{\text{PowerClass\_EN-DC}}$ is defined in clause 6.2B.1.1.3-1 for intra-band EN-DC; +- $X\_scale$ is the linear value of X dB which is configured by RRC and can only take values [0 , 6] dB +- $p_{\text{CMAX\_E-UTRA},c}(p)$ is the linear value of $P_{\text{CMAX\_E-UTRA},c}(p)$ , the real configured max power for E-UTRA +- $p_{\text{CMAX},f,c,NR}(q)$ is the linear value of $P_{\text{CMAX},f,c,NR}(q)$ , the real configured max power of NR + +**Table 6.2B.4.1.0.1.1-2: $P_{\text{CMAX}}$ tolerance for Dual Connectivity E-UTRANR** + +| $P_{\text{CMAX}}(\text{dBm})$ | Tolerance
$T_{\text{LOW}}(P_{\text{CMAX\_L}}) \text{ (dB)}$ | Tolerance
$T_{\text{HIGH}}(P_{\text{CMAX\_H}}) \text{ (dB)}$ | +|-----------------------------------|----------------------------------------------------------------|-----------------------------------------------------------------| +| $23 \leq P_{\text{CMAX}} \leq 33$ | 3.0 | 2.0 | +| $22 \leq P_{\text{CMAX}} < 23$ | 5.0 | 2.0 | +| $21 \leq P_{\text{CMAX}} < 22$ | 5.0 | 3.0 | +| $20 \leq P_{\text{CMAX}} < 21$ | 6.0 | 4.0 | +| $16 \leq P_{\text{CMAX}} < 20$ | | 5.0 | +| $11 \leq P_{\text{CMAX}} < 16$ | | 6.0 | +| $-40 \leq P_{\text{CMAX}} < 11$ | | 7.0 | + +If the UE supports dynamic power sharing, and when LTE and NR transmissions overlap and the condition (If (a=TRUE) AND (b=FALSE)) is met, SCG shall be transmitted and the following supplementary minimum requirement apply for the measured SCG power, $P_{\text{UMAX},f,c,NR}(q)$ , under nominal conditions and unless otherwise stated. + +$$10 \log(p_{\text{CMAX\_L},f,c,NR}(q) / X\_scale) - T_{\text{LOW}}(10 \log(p_{\text{CMAX\_L},f,c,NR}(q) / X\_scale)) \leq P_{\text{UMAX},f,c,NR}(q) \leq 10 \log(p_{\text{CMAX\_H},f,c,NR}(q) / X\_scale) + T_{\text{HIGH}}(10 \log(p_{\text{CMAX\_H},f,c,NR}(q) / X\_scale)).$$ + +with the tolerances $T_{\text{LOW}}$ and $T_{\text{HIGH}}$ for applicable values of $P_{\text{CMAX}}$ specified in Table 6.2B.4.1.0.1.1-2. + +If the UE supports dynamic power sharing, the measured maximum output power in subframe $p$ on CG 1, $P_{\text{UMAX},c,E\text{-UTRA}}$ , shall meet the requirements in clause 6.2.5 in TS 36.101 [5] with the limits $P_{\text{CMAX},L,c}$ and $P_{\text{CMAX},H,c}$ replaced by $P_{\text{CMAX},L,E\text{-UTRA},c}$ and $P_{\text{CMAX},H,E\text{-UTRA},c}$ as specified above, respectively. + +If the configured transmission power spectral density between the MCG and SCG differs by more than 6 dB, then + +$$P_{\text{UMAX},f,c,NR}(q) \leq 10\log(P_{\text{CMAX},H,f,c,NR}(q)) + T_{\text{HIGH}}(10\log(P_{\text{CMAX},H,f,c,NR}(q))).$$ + +###### 6.2B.4.1.0.1.2 Intra-band non-contiguous EN-DC + +The following requirements apply for one component carrier per CG configured for synchronous DC. The CG(s) are indexed by $j = 1$ for MCG and $j = 2$ for SCG. + +The configured maximum output power $P_{\text{CMAX},E\text{-UTRA},c}(p)$ in sub-frame $p$ for the configured E-UTRA uplink carrier shall be set in accordance with clause 6.2B.4.1.0.1.1 but where + +- for a UE not indicating support of dynamicPowerSharing, the A-MPR $_c$ determined in accordance with clause 6.2B.3.2 with parameters applicable for UEs not indicating support of dynamicPowerSharing and MPR $_c = 0$ dB; + +whenever NS\_01 is not indicated within CG 1 while + +- for a UE not indicating support of dynamicPowerSharing, the MPR $_c$ determined in accordance with clause 6.2B.2.2 with parameters applicable for UEs not indicating support of dynamicPowerSharing and A-MPR $_c = 0$ dB; + +whenever NS\_01 is indicated in CG 1. + +The configured maximum output power $P_{\text{CMAX},NR,c}(q)$ in physical channel $q$ for the configured NR carrier shall be set in accordance with clause 6.2B.4.1.0.1.1 but where + +- for a UE indicating support of dynamicPowerSharing, A-MPR $_c = A\text{-MPR}'_c$ with A-MPR' $_c$ determined in accordance with clause 6.2B.3.2 and MPR $_c = 0$ dB if transmission(s) in subframe $p$ on CG 1 overlap in time with physical channel $q$ on CG 2; +- for a UE indicating support of dynamicPowerSharing, A-MPR $_c$ is determined in accordance with [2] if transmission(s) in subframe $p$ on CG 1 does not overlap in time with physical channel $q$ on CG 2; +- for a UE not indicating support of dynamicPowerSharing, the A-MPR $_c$ is determined in accordance with clause 6.2B.3.2 with parameters applicable for UEs not indicating support of dynamicPowerSharing and MPR $_c = 0$ dB; + +For UEs indicating support of dynamicPowerSharing in the *UE-MRDC-Capability* IE, the UE can configure the total transmission power in accordance with clause 6.2B.4.1.0.1.1 but with $P_{\text{powerclass},EN\text{-DC}}$ the EN-DC power class of the intra-band non-contiguous band combination configured and A-MPR determined in accordance with clause 6.2B.3.2. + +whenever NS\_01 is not indicated in CG 2 while + +- for a UE indicating support of dynamicPowerSharing, MPR $_c = MPR'_c$ with MPR' $_c$ determined in accordance with clause 6.2B.2.2 and A-MPR $_c = 0$ dB if transmission(s) in subframe $p$ on CG 1 overlap in time with physical channel $q$ on CG 2; +- for a UE indicating support of dynamicPowerSharing, MPR $_c$ is determined in accordance with TS 38.101-1 [2] if transmission(s) in subframe $p$ on CG 1 does not overlap in time with physical channel $q$ on CG 2; +- for a UE not indicating support of dynamicPowerSharing, the MPR $_c$ is determined in accordance with clause 6.2B.2.2 with parameters applicable for UEs not indicating support of dynamicPowerSharing and A-MPR $_c = 0$ dB; + +whenever NS\_01 is indicated in CG 2. + +For UEs indicating support of dynamicPowerSharing in the *UE-MRDC-Capability IE*, the UE can configure the total transmission power in accordance with clause 6.2B.4.1.1 but with $P_{\text{powerclass,EN-DC}}$ the EN-DC power class of the intra-band non-contiguous band combination configured and A-MPR determined in accordance with clause 6.2B.3.2. + +The total maximum output power $P_{\text{UMAX}}$ over both CGs is measured in accordance with clause 6.2B.4.1.0.1.1 and shall be within the limits specified in clause 6.2B.4.1.0.1.1 but with parameters applicable for the non-contiguous band combination configured. + +The maximum output power levels $p_{\text{UMAX,c,E-UTRA}}$ and $p_{\text{UMAX,f,c,NR}}$ for the CGs are measured in accordance with clause 6.2B.4.1.0.1.1 and shall be within the limits specified in clause 6.2B.4.1.0.1.1 but with parameters applicable for the non-contiguous band combination configured. + +###### 6.2B.4.1.0.1.3 Inter-band EN-DC within FR1 + +For inter-band dual connectivity with one uplink serving cell or more than one uplink serving cells configured for intra-band UL CA on the E-UTRA CG and one uplink serving cell on the NR CG or more than one uplink serving cells configured for intra-band UL CA, the UE is allowed to set its configured maximum output power $P_{\text{CMAX,c(i),i}}$ for serving cell $c(i)$ of CG $i$ , $i = 1, 2$ , and its total configured maximum transmission power for EN-DC operation, $= 10\log_{10}()$ with as specified in clause 7.6 of TS 38.213 [19]. For EN-DC with more than one uplink serving cells configured for intra-band UL CA on the E-UTRA CG, the $P_{\text{CMAX}}$ applies to the entire E-UTRA CG. For EN-DC with more than one uplink serving cells configured for intra-band UL CA on the NR CG, the $P_{\text{CMAX}}$ applies to the entire NR CG. + +For a UE configured with EN-DC and serving cell frame structure type 1, if the UE is configured with *subframeAssignment-r15* for the serving cell and E-UTRA Pcell is FDD, the UE is not expected to be configured with more than one serving cells in the uplink. + +The configured maximum output power $P_{\text{CMAX\_E-UTRA,c}}(p)$ in sub-frame $p$ for the configured E-UTRA uplink carrier shall be set within the bounds: + +$$P_{\text{CMAX\_L\_E-UTRA,c}}(p) \leq P_{\text{CMAX\_E-UTRA,c}}(p) \leq P_{\text{CMAX\_H\_E-UTRA,c}}(p)$$ + +where $P_{\text{CMAX\_L\_E-UTRA,c}}$ and $P_{\text{CMAX\_H\_E-UTRA,c}}$ are the limits for a serving cell $c$ as specified in TS 36.101 [5] clause 6.2.5 modified by $P_{\text{LTE}}$ as follows: + +$$P_{\text{CMAX\_L\_E-UTRA,c}} = \text{MIN} \{ P_{\text{EMAX, EN-DC}}, (P_{\text{PowerClass, EN-DC}} - \Delta P_{\text{PowerClass, EN-DC}}), \text{MIN}(P_{\text{EMAX,c}}, P_{\text{LTE}}) - \Delta t_{\text{c\_E-UTRA,c}}, (P_{\text{PowerClass,E-UTRA}} - \Delta P_{\text{PowerClass,E-UTRA}}) - \text{MAX}(\text{MPR}_c + \text{A-MPR}_c + \Delta T_{\text{IB,c}} + \Delta t_{\text{c\_E-UTRA,c}} + \Delta T_{\text{ProSe}}, P\text{-MPR}_c) \}$$ + +$$P_{\text{CMAX\_H\_E-UTRA,c}} = \text{MIN} \{ P_{\text{EMAX,c}}, P_{\text{EMAX, EN-DC}}, (P_{\text{PowerClass, EN-DC}} - \Delta P_{\text{PowerClass, EN-DC}}), P_{\text{LTE}}, P_{\text{PowerClass, E-UTRA}} - \Delta P_{\text{PowerClass, E-UTRA}} \}$$ + +For EN-DC with more than one uplink serving cells configured for intra-band UL CA on the E-UTRA CG, $P_{\text{CMAX\_L\_E-UTRA,c}}$ and $P_{\text{CMAX\_H\_E-UTRA,c}}$ are the limits for the E-UTRA CG as specified in TS 36.101 [5] clause 6.2.5A modified by $P_{\text{LTE}}$ as follows: + +$$P_{\text{CMAX\_L\_E-UTRA,c}} = \text{MIN} \{ 10 \log_{10} \sum p_{\text{EMAX,c}} - \Delta T_{\text{C}}, (P_{\text{PowerClass,E-UTRA}} - \Delta P_{\text{PowerClass,E-UTRA}}) - \text{MAX}(\text{MPR} + \text{A-MPR} + \Delta T_{\text{IB,c}} + \Delta T_{\text{C}} + \Delta T_{\text{ProSe}}, P\text{-MPR}) \}, P_{\text{LTE}}, P_{\text{PowerClass,EN-DC}} \}$$ + +$$P_{\text{CMAX\_H\_E-UTRA,c}} = \text{MIN} \{ 10 \log_{10} \sum p_{\text{EMAX,c}}, P_{\text{PowerClass,E-UTRA}}, P_{\text{LTE}}, P_{\text{PowerClass,EN-DC}} \}$$ + +The configured maximum output power $P_{\text{CMAX\_NR,c}}(q)$ in physical-channel $q$ for the configured NR carrier shall be set within the bounds: + +$$P_{\text{CMAX\_L,f,c,NR}}(q) \leq P_{\text{CMAX,f,c,NR}}(q) \leq P_{\text{CMAX\_H,f,c,NR}}(q)$$ + +where $P_{\text{CMAX\_L\_NR,c}}$ and $P_{\text{CMAX\_H\_NR,c}}$ are the limits for a serving cell $c$ as specified in clause 6.2.4 of TS 38.101-1 [2] modified as follows: + +$$P_{\text{CMAX\_L,fc,NR}} = \text{MIN} \{ P_{\text{EMAX, EN-DC}}, (P_{\text{PowerClass, EN-DC}} - \Delta P_{\text{PowerClass, EN-DC}}), \text{MIN}(P_{\text{EMAX,c}}, P_{\text{NR}}) - \Delta T_{\text{C\_NR,c}}, (P_{\text{PowerClass, NR}} - \Delta P_{\text{PowerClass, NR}}) - \text{MAX}(\text{MAX}(\text{MPR}_c, \text{A-MPR}_c) + \Delta T_{\text{IB,c}} + \Delta T_{\text{C\_NR,c}} + \Delta T_{\text{RxSRS}}, \text{P-MPR}_c) \}$$ + +$$P_{\text{CMAX\_H,fc,NR}} = \text{MIN} \{ P_{\text{EMAX,c}}, P_{\text{EMAX, EN-DC}}, (P_{\text{PowerClass, EN-DC}} - \Delta P_{\text{PowerClass, EN-DC}}), P_{\text{NR}}, P_{\text{PowerClass, NR}} - \Delta P_{\text{PowerClass, NR}} \}$$ + +For EN-DC with more than one uplink serving cells configured for intra-band UL CA on the NR CG, $P_{\text{CMAX\_L,fc,NR}}$ and $P_{\text{CMAX\_H,fc,NR}}$ are the limits for the NR CG as specified in [2] subclause 6.2A.4 modified by $P_{\text{NR}}$ as follows: + +$$P_{\text{CMAX\_L,fc,NR}} = \text{MIN} \{ 10 \log_{10} \sum p_{\text{EMAX,c}} - \Delta T_{\text{C}}, P_{\text{EMAX,CA}}, P_{\text{PowerClass,NR}} - \text{MAX}(\text{MPR} + \text{A-MPR} + \Delta T_{\text{IB,c}} + \Delta T_{\text{C\_NR,c}} + \Delta T_{\text{RxSRS}}, \text{P-MPR}), P_{\text{NR}}, P_{\text{PowerClass,EN-DC}} \}$$ + +$$P_{\text{CMAX\_H,fc,NR}} = \text{MIN} \{ 10 \log_{10} \sum p_{\text{EMAX,c}}, P_{\text{EMAX,CA}}, P_{\text{PowerClass,NR}}, P_{\text{NR}}, P_{\text{PowerClass,EN-DC}} \}$$ + +where + +- $P_{\text{EMAX,EN-DC}}$ is the value given by the field *p-maxUE-FR1* of the *RRConnectionReconfiguration-v1530* IE as defined in TS 36.331 [17]; +- If more than one E-UTRA uplink serving cell is configured as intra-band UL CA in the E-UTRA CG, $P_{\text{PowerClass}}$ refers to the maximum output power of the E-UTRA intra-band CA power class given in Table 6.2.2A-1 of TS 36.101 [5]; +- $P_{\text{LTE}}$ is the value given by the field *p-maxEUTRA-r15* of the *RRConnectionReconfiguration-v1510* IE as defined in TS 36.331 [17]; +- If more than one E-UTRA uplink serving cell is configured as intra-band UL CA in the E-UTRA CG, $\text{MPR}_c = \text{MPR}$ and $\text{A-MPR}_c = \text{A-MPR}$ with $\text{MPR}$ and $\text{A-MPR}$ specified in clause 6.2.3A and clause 6.2.4A of TS 36.101 [5] respectively. There is one power management term for the UE, denoted $\text{P-MPR}$ , and $\text{P-MPR}_c = \text{P-MPR}$ . $P_{\text{CMAX\_E-UTRA,c}}$ is calculated under the assumption that the transmit power is increased by the same amount in dB on all component carriers within the E-UTRA CG. +- If more than one NR uplink serving cell is configured as intra-band UL CA in the NR CG, $\text{MPR}_c$ and $\text{A-MPR}_c$ are determined by subclause 6.2.2 of [2]. There is one power management term for the UE, denoted $\text{P-MPR}$ , and $\text{P-MPR}_c = \text{P-MPR}$ . +- $P_{\text{NR}}$ is the value given by the field *p-NR-FR1* of the *PhysicalCellGroupConfig* IE as defined TS 38.331 [18]; +- $\Delta t_{\text{c\_E-UTRA,c}} = 1.5$ dB when NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] applies for a serving cell $c$ , otherwise $\Delta t_{\text{c\_E-UTRA,c}} = 0$ dB; +- $\Delta T_{\text{C\_NR,c}} = 1.5$ dB when NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] applies for a serving cell $c$ , otherwise $\Delta T_{\text{C\_NR,c}} = 0$ dB; $\Delta T_{\text{C\_NR,c}}$ is the highest value $\Delta T_{\text{C\_NR,c}}$ among all serving cells $c$ if more than one NR uplink serving cell is configured as intra-band UL CA in the NR CG; +- $P_{\text{PowerClass, EN-DC}}$ is defined in clause 6.2B.1.3 for inter-band EN-DC; if the UE indicates *higherPowerLimit-r17* and $\Delta P_{\text{PowerClass, EN-DC}} = 0$ , $P_{\text{PowerClass, EN-DC}}$ is replaced by the sum of the linear powers of $P_{\text{PowerClass, NR}}$ and $P_{\text{PowerClass, E-UTRA}}$ converted to dB; +- $\Delta P_{\text{PowerClass, EN-DC}} = 3$ dB for a power class 2 capable EN-DC UE when requirements of default power class had been applied as specified in sub-clause 6.2B.1; otherwise $\Delta P_{\text{PowerClass, EN-DC}} = 0$ dB; +- $P_{\text{PowerClass, NR}}$ is the nominal UE power of the power class that the UE supports for the NR band of the EN-DC combination as defined in clause 6.2.1 of 38.101-1 [2]; in case IE *[powerClassNRPart]* as defined in TS 38.331 [18] is indicated, $P_{\text{PowerClass, NR}}$ should use that value instead. +- $\Delta P_{\text{PowerClass, NR}}$ is 3 dB or 0 dB according to clause 6.2.4 of TS 38.101-1 [2] for a UE that supports power class 2 in the NR band of the EN-DC combination as defined in clause 6.2.1 of TS 38.101-1 [2]; + +- $P_{\text{PowerClass,E-UTRA}}$ is the nominal UE power of the power class that the UE supports for the E-UTRA band of the EN-DC combination as defined in clause 6.2.2 of 36.101 [5]; +- $\Delta P_{\text{PowerClass,E-UTRA}}$ is 3 dB or 0 dB according to clause 6.2.5 of TS 36.101 [5] for a UE that supports power class 2 in the E-UTRA band of the EN-DC combination as defined in clause 6.2.2 of TS 36.101 [5]; +- $\Delta T_{\text{IB,c}}$ specified in clause 6.2B.4.2.3 for EN-DC, the individual Power Class defined in table 6.2B.1.3 and any other additional power reductions parameters specified in clauses 6.2B.2 and 6.2B.3 for EN-DC are applicable to $P_{\text{CMAX\_E-UTRA,c}}$ and $P_{\text{CMAX\_f,c,NR}}$ evaluations. +- $\Delta T_{\text{RxSRS}}$ is the highest value among all serving cells $c$ . + +If the transmissions from NR and E-UTRA do not overlap, then the complete clauses for configured transmitted power for E-UTRA and NR respectively from their own specifications apply with the modifications specified above. The lower value between $P_{\text{PowerClass, EN-DC}}$ or $P_{\text{EMAX, EN-DC}}$ shall not be exceeded at any time by UE. + +$= 10 \log 10()$ with the configured maximum transmission power for EN-DC operation as specified in clause 7.6 of TS 38.213 [19]. + +The total configured maximum transmission power for both synchronous and non-synchronous operation is + +$$= \text{MIN} \{ P_{\text{EMAX, EN-DC}}, P_{\text{PowerClass, EN-DC}} - \Delta P_{\text{PowerClass, EN-DC}} \}$$ + +If the UE does not support dynamic power sharing, + +$$= \text{MIN} \{ P_{\text{EMAX, EN-DC}}, P_{\text{PowerClass, EN-DC}} - \Delta P_{\text{PowerClass, EN-DC}} \} + 0.3 \text{ dB}$$ + +If the EN-DC UE does not support dynamic power sharing, then the complete clauses for configured transmitted power for E-UTRA and NR respectively from their own specifications TS 36.101 [5] and TS 38.101-1 [2] respectively apply with the modifications specified above and applies. + +When a UE supporting dynamic sharing is configured for overlapping E-UTRA uplink and NR uplink transmissions, the UE can set its configured maximum output power $P_{\text{CMAX\_E-UTRA,c}}$ and $P_{\text{CMAX\_NR,c}}$ for the configured E-UTRA and NR uplink carriers, respectively, and its configured maximum transmission power for EN-DC operation, , as specified above. + +The measured total maximum output power $P_{\text{UMAX}}$ over both CGs/RATs, measured over the transmission reference time duration is + +$$P_{\text{UMAX}} = 10 \log_{10} [p_{\text{UMAX,c,E-UTRA}} + p_{\text{UMAX,c,NR}}],$$ + +where $p_{\text{UMAX,c,E-UTRA}}$ and $p_{\text{UMAX,c,NR}}$ denotes the measured output power of serving cell $c$ for E-UTRA and NR respectively, expressed in linear scale. + +The measured total configured maximum output power $P_{\text{UMAX}}$ shall be within the following bounds: + +$$P_{\text{CMAX\_L}} - T_{\text{LOW}}(P_{\text{CMAX\_L}}) \leq P_{\text{UMAX}} \leq P_{\text{CMAX\_H}} + T_{\text{HIGH}}(P_{\text{CMAX\_H}})$$ + +with the tolerances $T_{\text{LOW}}(P_{\text{CMAX\_H}})$ and $T_{\text{HIGH}}(P_{\text{CMAX\_H}})$ for applicable values of $P_{\text{CMAX}}$ specified in Table 6.2B.4.1.0.1.3-2. When an UL subframe transmission $p$ from E-UTRA overlap with a physical-channel $q$ from the NR, then for $P_{\text{UMAX}}$ evaluation, the E-UTRA subframe $p$ is taken as reference period $T_{\text{REF}}$ and always considered as the reference measurement duration and the following rules are applicable. + +$T_{\text{REF}}$ and $T_{\text{eval}}$ are specified in Table 6.2B.4.1.0.1.3-1 when same or different subframe and physical-channel durations are used in aggregated carriers. The lesser of $P_{\text{PowerClass, EN-DC}}$ and $P_{\text{EMAX, EN-DC}}$ shall not be exceeded by the UE during any evaluation period of time where $P_{\text{PowerClass, EN-DC}}$ is replaced by the sum of the linear powers of $P_{\text{PowerClass,NR}}$ and $P_{\text{PowerClass,E-UTRA}}$ converted to dB if the UE indicates *higherPowerLimit-r17*. + +**Table 6.2B.4.1.0.1.3-1: PCMAX evaluation window** + +| transmission duration | T REF | T eval | +|-----------------------------------------------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------| +| Different transmission duration in different RAT carriers | E-UTRA Subframe on all aggregated cells of E-UTRA | Min( Tno_hopping , Physical Channel Length) on all aggregated cells of NR | + +For each TREF, the PCMAX\_H is evaluated per Teval and given by the maximum value over the transmission(s) within the Teval as follows: + +$$P_{\text{CMAX\_H}} = \text{MAX} \{ P_{\text{CMAX\_EN-DC\_H}}(p, q), P_{\text{CMAX\_EN-DC\_H}}(p, q+1), \dots, P_{\text{CMAX\_EN-DC\_H}}(p, q+n) \}$$ + +where PCMAX\_EN-DC\_H are the applicable upper limits for each overlapping scheduling unit pairs (p, q), (p, q+1), up to (p, q+n) for each applicable Teval duration, where q+n is the last NR UL physical-channel overlapping with E-UTRA subframe p. + +While PCMAX\_L is computed as follows: + +$$P_{\text{CMAX\_L}} = \text{MIN} \{ P_{\text{CMAX\_EN-DC\_L}}(p, q), P_{\text{CMAX\_EN-DC\_L}}(p, q+1), \dots, P_{\text{CMAX\_EN-DC\_L}}(p, q+n) \}$$ + +where PCMAX\_EN-DC\_L are the applicable lower limits for each overlapping scheduling unit pairs (p, q), (p, q+1), up to (p, q+n) for each applicable Teval duration, where q+n is the last NR UL physical-channel overlapping with E-UTRA subframe p, + +With + +$$P_{\text{CMAX\_EN-DC\_H}}(p, q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_H\_E-UTRA},c}(p) + p_{\text{CMAX\_H},fc,NR,c}(q)], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} \}$$ + +And: + +$$a = 10 \log_{10} [p_{\text{CMAX\_E-UTRA},c}(p) + p_{\text{CMAX\_fc,NR}}(q)] >$$ + +$$b = 10 \log_{10} [p_{\text{CMAX\_E-UTRA},c}(p) + p_{\text{CMAX\_fc,NR}}(q) / X\_scale] >$$ + +If a= FALSE + +$$P_{\text{CMAX\_EN-DC\_L}}(p, q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_L\_E-UTRA},c}(p) + p_{\text{CMAX\_L},fc,NR,c}(q)], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} \}$$ + +ELSE If (a=TRUE) AND (b=FALSE) + +$$P_{\text{CMAX\_EN-DC\_L}}(p, q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_L\_E-UTRA},c}(p) + p_{\text{CMAX\_L},fc,NR,c}(q) / X\_scale], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} \}$$ + +ELSE If b= TRUE + +$$P_{\text{CMAX\_EN-DC\_L}}(p, q) = \text{MIN} \{ 10 \log_{10} [p_{\text{CMAX\_L\_E-UTRA},c}(p)], P_{\text{EMAX\_EN-DC}}, P_{\text{PowerClass\_EN-DC}} \}$$ + +where + +- pCMAX\_H\_E-UTRA,c(p) is the E-UTRA higher limit of the maximum configured power expressed in linear scale; +- pCMAX\_L,fc,NR(q) is the NR higher limit of the maximum configured power expressed in linear scale; +- pCMAX\_H\_NR,c(q) is the NR higher limit of the maximum configured power expressed in linear scale; +- pCMAX\_L\_E-UTRA,c(p) is the E-UTRA lower limit of the maximum configured power expressed in linear scale; +- pCMAX\_L\_NR,c(q) is the NR lower limit of the maximum configured power expressed in linear scale; +- PPowerClass\_EN-DC is defined in clause 6.2B.1.3-1 for inter-band EN-DC; if the UE indicates *higherPowerLimit-r17*, PPowerClass\_EN-DC is replaced by the sum of the linear powers of PPowerClass\_NR and PPowerClass\_E-UTRA converted to dB; + +- $X\_scale$ is the linear value of X dB which is configured by RRC and can only take values [0 , 6] +- $P_{CMAX\_E-UTRA,c}(p)$ is the linear value of $P_{CMAX\_E-UTRA,c}(p)$ , the configured max power for E-UTRA. If more than one E-UTRA uplink serving cell is configured as intra-band UL CA in the E-UTRA CG, $P_{CMAX\_E-UTRA,c}(p)$ will be replaced by $P_{CMAX}(p)$ which is the configured maximum power for the entire E-UTRA CG. +- $P_{CMAX,f,c,NR}(q)$ is the linear value of $P_{CMAX,f,c,NR}(q)$ , the configured max power of NR. If more than one NR uplink serving cell is configured as intra-band UL CA in the NR CG, $P_{CMAX\_NR,c}(q)$ will be replaced by $P_{CMAX}(q)$ which is the configured maximum power for the entire NR CG. + +**Table 6.2B.4.1.0.1.3-2: $P_{CMAX}$ tolerance for Dual Connectivity E-UTRA-NR** + +| $P_{CMAX}(\text{dBm})$ | Tolerance
$T_{LOW}(P_{CMAX\_L})$ (dB) | Tolerance
$T_{HIGH}(P_{CMAX\_H})$ (dB) | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-------------------------------------------| +| $23 \leq P_{CMAX} \leq 33$ | 3.0 | 2.0 | +| $22 \leq P_{CMAX} < 23$ | 5.0 | 2.0 | +| $21 \leq P_{CMAX} < 22$ | 5.0 | 3.0 | +| $20 \leq P_{CMAX} < 21$ | 6.0 | 4.0 | +| $16 \leq P_{CMAX} < 20$ | | 5.0 | +| $11 \leq P_{CMAX} < 16$ | | 6.0 | +| $-40 \leq P_{CMAX} < 11$ | | 7.0 | +| NOTE 1: For UEs not indicating support of dynamic power sharing, the upper tolerance $T_{high}$ shall be reduced by 0.3 dB for $P \geq 20$ dBm. | | | + +When E-UTRA and NR transmissions overlap and the condition (If (a=TRUE) AND (b=FALSE)) is met, SCG shall be transmitted and the following supplementary minimum requirement apply for the measured SCG power, $P_{UMAX,f,c,NR}(q)$ , under nominal conditions. + +$$10\log(P_{CMAX\_L,f,c,NR}(q)/X\_scale) - T_{LOW}(10\log(P_{CMAX\_L,f,c,NR}(q)/X\_scale)) \leq P_{UMAX,f,c,NR}(q) \leq 10\log(P_{CMAX\_H,f,c,NR}(q)/X\_scale) + T_{HIGH}(10\log(P_{CMAX\_H,f,c,NR}(q)/X\_scale)).$$ + +with the tolerances $T_{LOW}$ and $T_{HIGH}$ for applicable values of $P_{CMAX}$ specified in Table 6.2B.4.1.0.1.3-2. + +###### 6.2B.4.1.0.1.4 Inter-band EN-DC including FR2 + +For inter-band dual connectivity with one uplink serving cell per CG on E-UTRA and NR respectively, with NR configured in FR2, the UE is allowed to set its configured maximum output power $P_{CMAX,c(i),i}$ for serving cell $c(i)$ of CG $i$ , $i = 1,2$ . + +The UE maximum configured power $P_{CMAX,c(i),i}$ on E-UTRA for the subframe $i$ shall be set according to clause 6.2.5 from TS 36.101 [5]. Applicable inter-band $\Delta T_{IB,c}$ parameters shall be used according to the clauses 6.2B.4.2.4 or 6.2B.4.2.5. + +The UE maximum configured power $P_{CMAX,c(j),j}$ on NR for the slot $j$ shall be set according to clause 6.2.4 from TS 38.101-2 [3]. + +For the configured power measurements TS 36.101 [5] clause 6.2.5 and TS 38.101-2 [3] clause 6.2.4 are applicable. + +###### 6.2B.4.1.0.1.5 Inter-band EN-DC including both FR1 and FR2 + +For inter-band dual connectivity with one uplink serving cell per CG on E-UTRA and NR respectively, with both CGs configured in FR1, the requirements specified in clause 6.2B.4.1.0.1.3 apply. + +For inter-band dual connectivity with one uplink serving cell per CG on E-UTRA and NR respectively, with NR configured in FR2, the requirements specified in clause 6.2B.4.1.0.1.4 apply. + +For inter-band dual connectivity with one uplink serving cell in first CG on E-UTRA and two uplink serving cells in second CG on NR FR1 and NR FR2 respectively, the UE is allowed to set its configured maximum output power $P_{\text{CMAX},c(i),i}$ for serving cell $c(i)$ , $i = 1,2,3$ with $i=1$ for E-UTRA, $i=2$ for NR FR1 and $i=3$ for NR FR2. + +- For serving cell on FR2, the requirements specified in clause 6.2.4 in TS 38.101-2 [3] apply to the UE maximum configured power $P_{\text{CMAX},c(3),3}$ and the measured maximum configured power. +- For remaining inter-band dual connectivity involving CG1 and CG2, the requirements specified in clause 6.2B.4.1.0.1.3 apply. + +##### 6.2B.4.1.1 Configured Output Power Level for Intra-Band Contiguous EN-DC + +###### 6.2B.4.1.1.1 Test purpose + +To verify the UE does not exceed the power bounds defined by $P_{\text{CMAX\_L}}$ and $P_{\text{CMAX\_H}}$ + +###### 6.2B.4.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.2B.4.1.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2B.4.1.0.1.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.2B.4.1.1.4 Test description + +###### 6.2B.4.1.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.2B.4.1.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.4.1.1.4.1-1: Test configurations table for intra-band contiguous EN-DC** + +| Initial Conditions | | | | | | | | +|-------------------------------------------------------------------------------|----------------------------------------------------------|----------------------------|---------------------------|----------------------------------------------------------------------------------|--------------------|---------------------------|----------------------------------------------------------------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | +| NR and E-UTRA Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1 | Mid range | | | | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | Lowest N RB_agg , Highest N RB_agg | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | | | +| NR/E-UTRA Test Parameters for UE supporting DPS | | | | | | | | +| Test ID
(NOTE 3) | Downlink
Configuration | EN-DC Uplink Configuration | | | | | | +| | | E-UTRA Cell | | | NR Cell | | | +| | | Modulation | RB allocation
(NOTE 2) | P LTE | Modulation | RB allocation
(NOTE 1) | P NR | +| 1a-1f | N/A | QPSK | Full_Allocation | {-13, 7, 12, 15, 19, 23}
for PC3 UE
{-13, 7, 12, 15, 21, 26}
for PC2 UE | CP-OFDM
QPSK | Outer_Full | {-13, 7, 12, 15, 18, 23}
for PC3 UE
{-13, 7, 12, 15, 21, 26}
for PC2 UE | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM
QPSK | Inner Full | {-10, 10, 15} | +| NR/E-UTRA Test Parameters for UE not supporting DPS | | | | | | | | +| Test ID
(NOTE 3) | Downlink
Configuration | EN-DC Uplink Configuration | | | | | | +| | | E-UTRA Cell | | | NR Cell | | | +| | | Modulation | RB allocation
(NOTE 2) | P LTE | Modulation | RB allocation
(NOTE 1) | P NR | +| 1a-1d | N/A | QPSK | Full_Allocation | {-10, 10, 15, 23} for PC3 UE
{-10, 10, 15, 26} for PC2 UE | CP-OFDM
QPSK | Outer_Full | {-10, 10, 15, 23} for PC3 UE
{-10, 10, 15, 26} for PC2 UE | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM
QPSK | Inner Full | {-10, 10, 15} | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. + +NOTE 3: The suffix in Test ID identifies the configured power level being tested from the PLTE and PNR lists + +**Table 6.2B.4.1.1.4.1-2: Void** + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. + +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.4.1.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.4.1.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according table 6.2B.4.1.1.4.1-1 on E-UTRA CC and NR CC respectively. For test points configured with message in Table 6.2B.4.1.1.4.3-1, NR SS only schedules UL RMC on NR slots that does not overlap with E-UTRA uplink subframe. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level. +3. Measure the mean transmitted power over E-UTRA component carrier and NR component carrier respectively, or/and measure the sum of mean transmitted power over E-UTRA and NR component carriers according to Table 6.2B.4.1.1.5-1 and Table 6.2B.4.1.1.5-2. The period of the measurement shall be at least the continuous duration of one active sub-frame. For TDD, only slots consisting of only UL symbols are under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.2B.4.1.1.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.4.1.1.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.2B.4.1.1.4.3-1: RRCConnectionReconfiguration: tdm-PatternConfig if E-UTRA on FDD band and UE doesn't support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | Test ID 1d | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.4.1.1.4.3-2: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.4.1.1.4.3-3: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|-------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | Defined as P LTE in Table 6.2B.4.1.1.4.1-1 | | | + +**Table 6.2B.4.1.1.4.3-4: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalCellGroupConfig ::= SEQUENCE { | | | | +| p-NR-FR1 | Defined as P NR in Table 6.2B.4.1.1.4.1-1 | | | +| } | | | | + +**Table 6.2B.4.1.1.4.3-5: RRCConnectionReconfiguration: p-MaxUE-FR1-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|------------------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension
SEQUENCE { | | RRCConnection
Reconfiguration-
v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE | +| | 26 | | Power Class 2 UE | +| } | | | | + +###### 6.2B.4.1.1.5 Test requirement + +For UE supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.1.5-1. + +**Table 6.2B.4.1.1.5-1: PCMAX configured UE output power for UE supporting DPS** + +| | E-UTRA component carrier | NR component carrier | Total power measured over E-UTRA and NR component carriers | +|--|--------------------------|----------------------|------------------------------------------------------------| +| | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test ID 1a | Not measured | Not measured | -10dBm ± (7+TT) | +| Test ID 1b | Not measured | Not measured | 10dBm ± (7+TT) | +| Test ID 1c | Not measured | Not measured | 15 ± (6+TT) | +| Test ID 1d | Not measured | Not measured | 18 ± (5+TT) | +| Test ID 1e | Not measured | 18 + (5+TT) / 11 – (6+TT) for PC3 UE | 21.54dBm + (3+TT) / 19.64 - (5+TT) for PC3 UE | +| | | 21 + (3+TT) / 14 - (6+TT) for PC2 UE (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by powerClassNRPart-r16 )) | 24 + (2+TT) / 21.8 - (5+TT) for PC2 UE (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC2 or Not present by powerClassNRPart-r16 )) | +| | | 21 + (3+TT) / 11 - (6+TT) for PC2 UE (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by powerClassNRPart-r16 )) | 24 + (2+TT) / 21.4 - (5+TT) for PC2 UE (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by $P_{\text{PowerClass,NR}}$ , and PC3 by powerClassNRPart-r16 )) | +| Test ID 1f | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | +| | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE | | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE | +| Test ID 2a | -10dBm ± (7+TT) | N/A- | Not measured | +| Test ID 2b | 10dBm ± (6+TT) | N/A- | Not measured | +| Test ID 2c | 15dBm ± (5+TT) | N/A- | Not measured | +| Test ID 3a | N/A | -10dBm ± (7+TT) | Not measured | +| Test ID 3b | N/A | 10dBm ± (6+TT) | Not measured | +| Test ID 3c | N/A | 15dBm ± (5+TT) | Not measured | +| NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. | | | | +| NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.1.5-3 | | | | + +For UE not supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.1.5-2. + +**Table 6.2B.4.1.1.5-2: $P_{\text{CMAX}}$ configured UE output power for UE not supporting DPS** + +| | E-UTRA component carrier | NR component carrier | Total power measured over E-UTRA and NR component carriers | +|--|--------------------------|----------------------|------------------------------------------------------------| +| | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------------------|--------------| +| Test ID 1a | -10 dBm $\pm$ (7+TT) | -10 dBm $\pm$ (7+TT) | Not measured | +| Test ID 1b | 10 dBm $\pm$ (6+TT) | 10 dBm $\pm$ (6+TT) | Not measured | +| Test ID 1c | 15 dBm $\pm$ (5+TT) | 15 dBm $\pm$ (5+TT) | Not measured | +| Test ID 1d | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Not measured | +| | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE | | | +| Test ID 2a | -10dBm $\pm$ (7+TT) | N/A | Not measured | +| Test ID 2b | 10dBm $\pm$ (6+TT) | N/A | Not measured | +| Test ID 2c | 15dBm $\pm$ (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10dBm $\pm$ (7+TT) | Not measured | +| Test ID 3b | N/A | 10dBm $\pm$ (6+TT) | Not measured | +| Test ID 3c | N/A | 15dBm $\pm$ (5+TT) | Not measured | +| NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. | | | | +| NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.1.5-3 | | | | + +**Table 6.2B.4.1.1.5-3: Test Tolerance (UE configured UE output power)** + +| | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | +|----------------------------------------------------------------------|------------------------|----------------------------------------|----------------------------------------| +| ENBW \leq 40\text{MHz} | 0.7 dB | 1.0 dB | 1.0 dB | +| 40\text{MHz} < \text{ENBW} \leq 100\text{MHz} | 1.0 dB | 1.0 dB | 1.0 dB | + +##### 6.2B.4.1.2 Configured Output Power for Intra-Band Non-Contiguous EN-DC + +###### 6.2B.4.1.2.1 Test purpose + +To verify the UE does not exceed the power bounds defined by $P_{\text{CMAX\_L}}$ and $P_{\text{CMAX\_H}}$ . + +###### 6.2B.4.1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.2B.4.1.2.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2B.4.1.0.1.2. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.2B.4.1.2.4 Test description + +###### 6.2B.4.1.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell + +specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.2B.4.1.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.4.1.2.4.1-1: Test configurations table for intra-band non-contiguous EN-DC** + +| Initial Conditions | | | | | | | | +|-------------------------------------------------------------------------------|----------------------------------------------------------|----------------------------|---------------------------|------------------------------------------------------------|--------------------|---------------------------|------------------------------------------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | +| NR and E-UTRA Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1 | Maximum Wgap | | | | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | Lowest N RB_agg , Highest N RB_agg | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest (NOTE 4) | | | | | | | +| NR/E-UTRA Test Parameters for UE supporting DPS | | | | | | | | +| Test ID
(NOTE 3) | Downlink
Configuration | EN-DC Uplink Configuration | | | | | | +| | | E-UTRA Cell | | | NR Cell | | | +| | | Modulation | RB allocation
(NOTE 2) | P LTE | Modulation | RB allocation
(NOTE 1) | P NR | +| 1a-1d | N/A | QPSK | Full_Allocation | {-13, 7, 10, 23} for PC3 UE
{-13, 7, 12, 26} for PC2 UE | CP-OFDM
QPSK | Outer_Full | {-13, 7, 10, 23} for PC3 UE
{-13, 7, 13, 26} for PC2 UE | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM
QPSK | Inner Full | {-10, 10, 15} | +| NR/E-UTRA Test Parameters for UE not supporting DPS | | | | | | | | +| Test ID
(NOTE 3) | Downlink
Configuration | EN-DC Uplink Configuration | | | | | | +| | | E-UTRA Cell | | | NR Cell | | | +| | | Modulation | RB allocation
(NOTE 2) | P LTE | Modulation | RB allocation
(NOTE 1) | P NR | +| 1a-1b | N/A | QPSK | Full_Allocation | {-10, 23} for PC3 UE
{-10, 26} for PC2 UE | CP-OFDM
QPSK | Outer_Full | {-10, 23} for PC3 UE
{-10, 26} for PC2 UE | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM
QPSK | Inner Full | {-10, 10, 15} | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. + +NOTE 3: The suffix in Test ID identifies the configured power level being tested from the PLTE and PNR lists. + +NOTE 4: For DC\_(n)71AA, only NR SCS of 15 kHz is tested. + +**Table 6.2B.4.1.2.4.1-2: Void** + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.4.1.2.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.4.1.2.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according table 6.2B.4.1.2.4.1-1 on E-UTRA CC and NR CC respectively. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{\text{UMAX}}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean transmitted power over E-UTRA component carrier and NR component carrier respectively, or/and measure the sum of mean transmitted power over E-UTRA and NR component carriers according to Table 6.2B.4.1.2.5-1 and Table 6.2B.4.1.2.5-2. The period of the measurement shall be at least the continuous duration of one active sub-frame. For TDD, only slots consisting of only UL symbols are under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.2B.4.1.2.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.4.1.2.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.2B.4.1.2.4.3-1: *RRConnectionReconfiguration*: tdm-PatternConfig if E-UTRA on FDD band and UE doesn't support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.4.1.2.4.3-2: *SystemInformationBlockType1*: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.4.1.2.4.3-3: *RRConnectionReconfiguration*: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|-------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | Defined as $P_{\text{LTE}}$ in Table 6.2B.4.1.2.4.1-1 | | | + +**Table 6.2B.4.1.2.4.3-4: *PhysicalCellGroupConfig*** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalCellGroupConfig ::= SEQUENCE { | | | | +| p-NR-FR1 | Defined as $P_{\text{NR}}$ in Table 6.2B.4.1.2.4.1-1 | | | +| } | | | | + +**Table 6.2B.4.1.2.4.3-5: *RRConnectionReconfiguration*: p-MaxUE-FR1-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|-----------------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension ::=
SEQUENCE { | | RRConnection
Reconfiguration-
v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE | +| | 26 | | Power Class 2 UE | +| } | | | | + +###### 6.2B.4.1.2.5 Test requirement + +For UE supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.2.5-1. + +**Table 6.2B.4.1.2.5-1: PCMAX configured UE output power for UE supporting DPS** + +| | E-UTRA component carrier | NR component carrier | Total power measured over E-UTRA and NR component carriers | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test ID 1a | Not measured | Not measured | -10dBm $\pm$ (7+TT) | +| Test ID 1b | Not measured | Not measured | 10dBm $\pm$ (7+TT) | +| Test ID 1c | Not measured | 10 + (7+TT) / 2 - (7+TT) for PC3 UE | 13.0 + (6+TT) / 10.64 - (7+TT) for PC3 UE | +| | | 13 + (6+TT) / 5 - (7+TT) for PC2 UE (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by P PowerClass,NR , and PC2 or Not present by powerClassNRPart-r16 )) | 15.5 + (6+TT) / 12.8 - (6+TT) for PC2 UE (Rel-15 UE indicates PC2 on NR band, Rel-16 and forward UE reporting (PC2 by P PowerClass,NR , and PC2 or Not present by powerClassNRPart-r16 )) | +| | | 13 + (6+TT) / 2 - (7+TT) for PC2 UE (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by P PowerClass,NR , and PC3 by powerClassNRPart-r16 )) | 15.5 + (6+TT) / 12.4 - (6+TT) for PC2 UE (Rel-15 and forward UE indicates PC3 on NR band, Rel-16 and forward UE reporting (PC2 by P PowerClass,NR , and PC3 by powerClassNRPart-r16 )) | +| Test ID 1d | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | +| | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE | | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE | +| Test ID 2a | -10dBm $\pm$ (7+TT) | N/A | Not measured | +| Test ID 2b | 10dBm $\pm$ (6+TT) | N/A | Not measured | +| Test ID 2c | 15dBm $\pm$ (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10dBm $\pm$ (7+TT) | Not measured | +| Test ID 3b | N/A | 10dBm $\pm$ (6+TT) | Not measured | +| Test ID 3c | N/A | 15dBm $\pm$ (5+TT) | Not measured | +| NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. | | | | +| NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.1.5-3 | | | | + +For UE not supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.1.5-2. + +**Table 6.2B.4.1.2.5-2: PCMAX configured UE output power for UE not supporting DPS** + +| | E-UTRA component carrier | NR component carrier | Total power measured over E-UTRA and NR component carriers | +|--|--------------------------|----------------------|------------------------------------------------------------| +| | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------------------|--------------| +| Test ID 1a | -10 dBm $\pm$ (7+TT) | -10 dBm $\pm$ (7+TT) | Not measured | +| Test ID 1b | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Not measured | +| | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE | | | +| Test ID 2a | -10dBm $\pm$ (7+TT) | N/A | Not measured | +| Test ID 2b | 10dBm $\pm$ (6+TT) | N/A | Not measured | +| Test ID 2c | 15dBm $\pm$ (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10dBm $\pm$ (7+TT) | Not measured | +| Test ID 3b | N/A | 10dBm $\pm$ (6+TT) | Not measured | +| Test ID 3c | N/A | 15dBm $\pm$ (5+TT) | Not measured | +| NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. | | | | +| NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.1.5-3 | | | | + +**Table 6.2B.4.1.2.5-3: Test Tolerance for UE configured UE output power (Separate measurements over E-UTRA and NR CCs)** + +| Uplink TX | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6\text{GHz}$ | +|-----------|-----------------------------------------------|------------------------|----------------------------------------|--------------------------------------| +| E-UTRA | BW $\leq 20\text{MHz}$ | 0.7 dB | 1.0 dB | N/A | +| NR | BW $\leq 40\text{MHz}$ | 0.7 dB | 1.0 dB | 1.0 dB | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | 1.0 dB | 1.0 dB | 1.0 dB | + +**Table 6.2B.4.1.2.5-4: Test Tolerance for UE configured UE output power (Combined measurements of E-UTRA and NR CCs)** + +| TT for overall output power | | | | | | | | | | | | +|-----------------------------|------------------------|----------------------------------------|------------------------|----------------------------------------|----------------------------------------|-----------------------------------------------|----------------------------------------|----------------------------------------|-----------------------------------------------|----------------------------------------|----------------------------------------| +| | | | NR | | | | | | | | | +| | | | BW $\leq 20\text{MHz}$ | | | $20\text{ MHz} < \text{BW} \leq 40\text{MHz}$ | | | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | | | +| | | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | +| E-UTRA | BW $\leq 20\text{MHz}$ | $f \leq 3.0\text{GHz}$ | 0.7 dB | 1.0 dB | 1.0 dB | 0.7 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | +| | | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | + +##### 6.2B.4.1.3 Configured Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) + +###### 6.2B.4.1.3.1 Test purpose + +To verify the UE does not exceed the power bounds defined by $P_{\text{CMAX}}$ and $P_{\text{CMAX\_H}}$ . + +###### 6.2B.4.1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC with 1 E-UTRA CC and 1 NR CC within FR1. + +###### 6.2B.4.1.3.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2B.4.1.0.1.3. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.2B.4.1.3.4 Test description + +###### 6.2B.4.1.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.2B.4.1.3.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.4.1.3.4.1-1: Test configurations table for inter-band EN-DC** + +| Initial Conditions | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|----------------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------|--------------------------------------------------------------------------------------------------------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | +| NR Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508-1 [11] clause 4.3.1 | Mid range (NOTE 4) | | | | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | 5MHz for E-UTRA CC1 and Lowest for NR CC1, Highest for E-UTRA CC1 and Highest for NR CC1 | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | | | +| NR/E-UTRA Test Parameters for UE supporting DPS (NOTE 6) | | | | | | | | +| Test ID (NOTE 3) | Downlink Configuration | EN-DC Uplink Configuration | | | | | | +| | | E-UTRA Cell | | | NR Cell | | | +| | | Modulation | RB allocation (NOTE 2) | P LTE | Modulation | RB allocation (NOTE 1) | P NR | +| 1a-1h | N/A | QPSK | Partial_Allocation | {-13, 12, 14, 17, 18, 19, 20, 23} for PC3 UE
{-13, 12, 14, 17, 18, 19, 23 7 , 26 5 } for PC2 UE | DFT-s-OFDM QPSK | Inner_Full | {-13, 12, 14, 17, 18, 19, 23, 23} for PC3 UE
{-13, 12, 14, 17, 18, 19, 26 7 , 26 5 } for PC2 UE | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM QPSK | Inner_Full | {-10, 10, 15} | +| NR/E-UTRA Test Parameters for UE not supporting DPS | | | | | | | | +| Test ID (NOTE 3) | Downlink Configuration | EN-DC Uplink Configuration | | | | | | +| | | E-UTRA Cell | | | NR Cell | | | +| | | Modulation | RB allocation (NOTE 2) | P LTE | Modulation | RB allocation (NOTE 1) | P NR | +| 1a-1d | N/A | QPSK | Partial_Allocation | {-10, 10, 15, 23} for PC3 UE
{-10, 10, 15, 26} for PC2 UE | CP-OFDM QPSK | Inner_Full | {-10, 10, 15, 23} for PC3 UE
{-10, 10, 15, 26} for PC2 UE | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM QPSK | Inner_Full | {-10, 10, 15} | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. + +NOTE 3: The suffix in Test ID identifies the configured power level being tested from the PLTE and PNR lists. + +NOTE 4: For NR band n28, 30MHz test channel bandwidth is tested with Low range test frequency. + +NOTE 5: Only applicable to UEs indicating PC2 on E-UTRA band. + +NOTE 6: For PC2 UE, Test ID 1g and 1h are not required if UE indicates support of *higherPowerLimit-r17*. NOTE 7: The test point is only applicable to Rel-15 UEs supporting PC2 on NR band. Test point is applicable for UEs Rel-16 and forward, supporting PC2 on both NR band and NR part power class, or supporting PC2 on NR band and not supporting NR part power class. The capability of NR part power class is indicated in TS 38.508-2 Table A.4.3.2B.2.3.1-3a. + +NOTE 7: For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is + +| | +|---------------------------------------| +| tested with Low range test frequency. | +|---------------------------------------| + +**Table 6.2B.4.1.3.4.1-2: Void** + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to Table 6.2B.4.1.3.4.1-1. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.4.1.3.4.3. +7. For the case of testing overlapping E-UTRA and NR UL transmission scenario when both bands are TDD, ensure E-UTRA UL transmission overlaps with NR UL transmission in time by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.4.1.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for *C\_RNTI* to schedule the UL RMC according table 6.2B.4.1.3.4.1-1 on E-UTRA CC and NR CC respectively. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level. +3. Measure the mean transmitted power over E-UTRA component carrier and NR component carrier respectively, or/and measure the sum of mean transmitted power over E-UTRA and NR component carriers according to Table 6.2B.4.1.3.5-1 and Table 6.2B.4.1.3.5-2. The period of the measurement shall be at least the continuous duration of one active sub-frame. For TDD, only slots consisting of only UL symbols are under test. For FDD band in inter-band CA with both TDD band and FDD band, only slots overlapping with only UL symbols in TDD are under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.2B.4.1.3.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.4.1.3.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.2B.4.1.3.4.3-1: *RRConnectionReconfiguration*: tdm-PatternConfig if E-UTRA on FDD band and UE doesn't support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.4.1.3.4.3-2: *SystemInformationBlockType1*: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.4.1.3.4.3-3: *RRConnectionReconfiguration*: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | Defined as $P_{LTE}$ in Table 6.2B.4.1.3.4.1-1 | | | + +**Table 6.2B.4.1.3.4.3-4: *PhysicalCellGroupConfig*** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|-----------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalCellGroupConfig ::= SEQUENCE { | | | | +| p-NR-FR1 | Defined as $P_{NR}$ in Table 6.2B.4.1.3.4.1-1 | | | +| } | | | | + +**Table 6.2B.4.1.3.4.3-5: *RRConnectionReconfiguration*: p-MaxUE-FR1-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|-----------------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension
SEQUENCE { | | RRConnection
Reconfiguration-
v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE | +| | 26 | | Power Class 2 UE | +| } | | | | + +###### 6.2B.4.1.3.5 Test requirement + +For UE supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.3.5-1. + +**Table 6.2B.4.1.3.5-1: PCMAX configured UE output power for UE supporting DPS** + +| | E-UTRA component carrier | NR component carrier | Total power measured over E-UTRA and NR component carriers | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Test ID 1a | Not measured | Not measured | -10dBm $\pm$ (7+TT) | +| Test ID 1b | Not measured | Not measured | 15dBm $\pm$ (6+TT) | +| Test ID 1c | Not measured | Not measured | 17 $\pm$ (5+TT) | +| Test ID 1d | Not measured | Not measured | 20 + (4+TT) / - (6+TT) | +| Test ID 1e | Not measured | Not measured | 21 + (3+TT) / - (5+TT) | +| Test ID 1f | Not measured | Not measured | 22+ (2+TT) / - (5+TT) | +| Test ID 1g | Not measured | 23 + (2+TT) / 17 - (5+TT) for PC3 UE
26 + (2+TT) / 20 - (6+TT) for PC2 UE | 23 + (2+TT) / 21.8 - (5+TT) for PC3 UE
26 + (2+TT) / 24.8 - (3+TT) for PC2 UE | +| Test ID 1h | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE.
Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE (For a power class 2 capable UE operating on LTE band) | N/A | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE
Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE (For a power class 2 capable UE operating on LTE band) | +| Test ID 2a | -10dBm $\pm$ (7+TT) | N/A | Not measured | +| Test ID 2b | 10dBm $\pm$ (6+TT) | N/A | Not measured | +| Test ID 2c | 15dBm $\pm$ (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10dBm $\pm$ (7+TT) | Not measured | +| Test ID 3b | N/A | 10dBm $\pm$ (6+TT) | Not measured | +| Test ID 3c | N/A | 15dBm $\pm$ (5+TT) | Not measured | + +NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. + +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.3.5-3 and Table 6.2B.4.1.3.5-4. + +For UE not supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.3.5-2. + +**Table 6.2B.4.1.3.5-2: PCMAX configured UE output power for UE not supporting DPS** + +| | E-UTRA component carrier | NR component carrier | Total power measured over E-UTRA and NR component carriers | +|--|--------------------------|----------------------|------------------------------------------------------------| +|--|--------------------------|----------------------|------------------------------------------------------------| + +| | | | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------| +| Test ID 1a | -10 dBm ± (7+TT) | -10 dBm ± (7+TT) | Not measured | +| Test ID 1b | 10 dBm ± (6+TT) | 10 dBm ± (6+TT) | Not measured | +| Test ID 1c | 15 dBm ± (5+TT) | 15 dBm ± (5+TT) | Not measured | +| Test ID 1d | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Not measured | +| | Maximum output power with reduction as defined in Table 6.2.3_1.5-1 of TS 36.521-1 [10] for PC2 UE (For a power class 2 capable UE operating on LTE band) | | | +| | Maximum output power with reduction as defined in Table 6.2.3.5-1 of TS 36.521-1 [10] for PC2 UE (For a power class 3 UE operating on LTE band) | | | +| Test ID 2a | -10dBm ± (7+TT) | N/A | Not measured | +| Test ID 2b | 10dBm ± (6+TT) | N/A | Not measured | +| Test ID 2c | 15dBm ± (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10dBm ± (7+TT) | Not measured | +| Test ID 3b | N/A | 10dBm ± (6+TT) | Not measured | +| Test ID 3c | N/A | 15dBm ± (5+TT) | Not measured | + +NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. + NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.3.5-3 and Table 6.2B.4.1.3.5-4. + +**Table 6.2B.4.1.3.5-3: Test Tolerance for UE maximum output power (Separate measurements over E-UTRA and NR CCs)** + +| Uplink TX | | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6GHz | +|-----------|---------------------|------------|---------------------|-------------------| +| E-UTRA | BW ≤ 20MHz | 0.7 dB | 1.0 dB | N/A | +| NR | BW ≤ 40MHz | 0.7 dB | 1.0 dB | 1.0 dB | +| | 40MHz < BW ≤ 100MHz | 1.0 dB | 1.0 dB | 1.0 dB | + +**Table 6.2B.4.1.3.5-4: Test Tolerance for UE maximum output power (Combined measurements of E-UTRA and NR CCs)** + +| TT for overall output power | | | | | | | | | | | +|-----------------------------|------------|---------------------|------------|---------------------|---------------------|---------------------|---------------------|---------------------|---------------------|-------------------------------------------| +| | | | NR | | | | | | | | +| | | | BW ≤ 20MHz | | | 20 MHz < BW ≤ 40MHz | | | 40MHz < BW ≤ 100MHz | | +| | | | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz | 4.2GHz < f ≤ 6.0GHz | f ≤ 3.0GHz | 3.0GHz < f ≤ 4.2GHz / 4.2GHz < f ≤ 6.0GHz | +| E-UTRA | BW ≤ 20MHz | f ≤ 3.0GHz | 0.7 dB | 1.0 dB | 1.0 dB | 0.7 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | +| | | 3.0GHz < f ≤ 4.2GHz | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | + +For the UE which supports inter-band EN-DC configuration, $\Delta T_{IB,c}$ in 6.2B.4.2 applies where unless otherwise stated, the same $\Delta T_{IB,c}$ is applicable to NR band(s) part for DC configurations which have the same NR operating band combination. Unless otherwise stated, $\Delta T_{IB,c}$ is set to zero. + +###### 6.2B.4.1.3\_1 Configured Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) + +###### 6.2B.4.1.3\_1.1 Test purpose + +Same test purpose as in clause 6.2B.4.1.3.1 + +###### 6.2B.4.1.3\_1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 16 and forward, supporting inter-band EN-DC with 2 E-UTRA CCs and 1 NR CC FR1. + +###### 6.2B.4.1.3\_1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2B.4.1.0.1.3. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.2B.4.1.3\_1.4 Test description + +###### 6.2B.4.1.3\_1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.2B.4.1.3\_1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.2B.4.1.3\_1.4.1-1: Test configurations table for inter-band EN-DC** + +| Initial Conditions | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------|-------------------|-----------------------------------|-----------------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | +| NR Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508-1 [11] clause 4.3.1 | Mid range for MCG and SCG | | | | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | Lowest N RB_agg for E-UTRA CCs and Lowest for NR CC1,
Highest N RB_agg for E-UTRA CCs and Highest for NR CC1 | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | | | +| NR/E-UTRA Test Parameters for UE supporting DPS | | | | | | | | +| Test ID
(NOTE 3) | Downlink
Configuration | EN-DC Uplink Configuration | | | | | | +| | | MCG – EUTRA PCC&SCC | | | SCG - NR | | | +| | | Modulation | RB allocation
(NOTE 2) | PLTE | Modulation | RB allocation
(NOTE 1) | PNR | +| 1a-1h | N/A | QPSK | Partial_Allocation | {-13, 12, 14, 17, 18, 19, 20, 23} | DFT-s-OFDM QPSK | Inner_Full | {-13, 12, 14, 17, 18, 19, 23, 23} | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM QPSK | Inner_Full | {-10, 10, 15} | +| NR/E-UTRA Test Parameters for UE not supporting DPS | | | | | | | | +| Test ID
(NOTE 3) | Downlink
Configuration | EN-DC Uplink Configuration | | | | | | +| | | MCG – EUTRA PCC&SCC | | | SCG - NR | | | +| | | Modulation | RB allocation
(NOTE 2) | PLTE | Modulation | RB allocation
(NOTE 1) | PNR | +| 1a-1d | N/A | QPSK | Partial_Allocation | {-10, 10, 15, 23} | DFT-s-OFDM QPSK | Inner_Full | {-10, 10, 15, 23} | +| 2a-2c | | QPSK | Partial_Allocation | {-10, 10, 15} | N/A | N/A | {-10, 10, 15} | +| 3a-3c | | N/A | N/A | {-10, 10, 15} | DFT-s-OFDM QPSK | Inner_Full | {-10, 10, 15} | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-2 in current specification. + NOTE 3: The suffix in Test ID identifies the configured power level being tested from the PLTE and PNR lists. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG PCC and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set according to Table 6.2B.4.1.3\_1.4.1-1. + +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.4.1.3\_1.4.3. +7. For the case of testing overlapping E-UTRA and NR UL transmission scenario when both bands are TDD, ensure E-UTRA UL transmission overlaps with NR UL transmission in time by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.2B.4.1.3\_1.4.2 Test procedure + +1. Configure E-UTRA SCC according to TS 36.521-1 [10] Annex C.0, C.1, and Annex C.3.0 for all E-UTRA downlink physical channels. +2. The SS shall configure SCC as per TS 36.508 [11] clause 5.2A.4. Message contents are defined in clause 6.2B.4.1.3\_1.4.3. +3. SS activates SCC by sending the MAC-CE according to TS 36.321 clauses 5.13 and 6.1.3.8. Wait for at least 2 seconds as per TS 36.133 [12] clause 8.3.3.2. +4. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according Table 6.2B.4.1.3\_1.4.1-1 on E-UTRA PCC and SCC and NR CC respectively. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +5. Send continuously uplink power control "up" commands in every uplink scheduling information to the UE until the UE transmits at its $P_{\text{UMAX}}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{\text{UMAX}}$ level. +6. Measure the mean transmitted power over E-UTRA CG and NR CG respectively, or/and measure the sum of mean transmitted power over E-UTRA CG and NR CG according to Table 6.2B.4.1.3\_1.5-1 and Table 6.2B.4.1.3\_1.5-2. The period of the measurement shall be at least the continuous duration of one active subframe. For TDD, only slots consisting of only UL symbols are under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.2B.4.1.3\_1.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2B.4.1.3\_1.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.2B.4.1.3\_1.4.3-1: RRCConnectionReconfiguration: tdm-PatternConfig if E-UTRA on FDD band and UE doesn't support dynamic power sharing** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 CHOICE{ | | | | +| setup SEQUENCE { | | | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | + +**Table 6.2B.4.1.3\_1.4.3-2: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +**Table 6.2B.4.1.3\_1.4.3-3: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|---------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | Defined as $P_{\text{LTE}}$ in Table 6.2B.4.1.3_1.4.1-1 | | | + +**Table 6.2B.4.1.3\_1.4.3-4: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PhysicalCellGroupConfig ::= SEQUENCE { | | | | +| p-NR-FR1 | Defined as $P_{\text{NR}}$ in Table 6.2B.4.1.3_1.4.1-1 | | | +| } | | | | + +**Table 6.2B.4.1.3\_1.4.3-5: RRCConnectionReconfiguration: p-MaxUE-FR1-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|------------------------------------------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension
SEQUENCE { | | RRCConnection
Reconfiguration-
v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE | +| | 26 | | Power Class 2 UE | +| } | | | | + +###### 6.2B.4.1.3\_1.5 Test requirement + +For UE supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.3\_1.5-1. + +**Table 6.2B.4.1.3\_1.5-1: $P_{\text{CMAX}}$ configured UE output power for UE supporting DPS for PC3 UE** + +| | E-UTRA CG | NR CG | Total power measured over all E-UTRA and NR component carriers | +|--|-----------|-------|----------------------------------------------------------------| +| | | | | + +| | | | | +|------------|-------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------| +| Test ID 1a | Not measured | Not measured | -10 dBm $\pm$ (7+TT) | +| Test ID 1b | Not measured | Not measured | 15 dBm $\pm$ (6+TT) | +| Test ID 1c | Not measured | Not measured | 17 dBm $\pm$ (5+TT) | +| Test ID 1d | Not measured | Not measured | 20 dBm + (4+TT) / - (6+TT) | +| Test ID 1e | Not measured | Not measured | 21 dBm + (3+TT) / - (5+TT) | +| Test ID 1f | Not measured | Not measured | 22 dBm + (2+TT) / - (5+TT) | +| Test ID 1g | Not measured | 23 dBm + (2+TT) / 17 dBm - (5+TT) | 23 dBm + (2+TT) / 21.8 dBm - (5+TT) | +| Test ID 1h | Maximum output power with reduction as defined in Table 6.2.3A.1.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Maximum output power with reduction as defined in Table 6.2.3A.1.5-1 of TS 36.521-1 [10] for PC3 UE | +| | Maximum output power with reduction as defined in Table 6.2.3A.1_3.5-1 of TS 36.521-1 [10] for PC2 UE | | Maximum output power with reduction as defined in Table 6.2.3A.1_3.5-1 of TS 36.521-1 [10] for PC2 UE | +| Test ID 2a | -10 dBm $\pm$ (7+TT) | N/A | Not measured | +| Test ID 2b | 10 dBm $\pm$ (6+TT) | N/A | Not measured | +| Test ID 2c | 15 dBm $\pm$ (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10 dBm $\pm$ (7+TT) | Not measured | +| Test ID 3b | N/A | 10 dBm $\pm$ (6+TT) | Not measured | +| Test ID 3c | N/A | 15 dBm $\pm$ (5+TT) | Not measured | + +NOTE 1: In addition NOTE 2 in Table 6.2.2-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. + +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.3\_1.5-3 and Table 6.2B.4.1.3\_1.5-4. + +For UE not supporting DPS, the output power measured shall not exceed the values specified in Table 6.2B.4.1.3\_1.5-2. + +**Table 6.2B.4.1.3\_1.5-2: PCMAX configured UE output power for UE not supporting DPS** + +| | E-UTRA CG | NR CG | Total power measured over all E-UTRA and NR component carriers | +|------------|-------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------------------------| +| Test ID 1a | -10 dBm $\pm$ (7+TT) | -10 dBm $\pm$ (7+TT) | Not measured | +| Test ID 1b | 10 dBm $\pm$ (6+TT) | 10 dBm $\pm$ (6+TT) | Not measured | +| Test ID 1c | 15 dBm $\pm$ (5+TT) | 15 dBm $\pm$ (5+TT) | Not measured | +| Test ID 1d | Maximum output power with reduction as defined in Table 6.2.3A.1.5-1 of TS 36.521-1 [10] for PC3 UE | N/A | Not measured | +| | Maximum output power with reduction as defined in Table 6.2.3A.1_3.5-1 of TS 36.521-1 [10] for PC2 UE | | | +| Test ID 2a | -10 dBm $\pm$ (7+TT) | N/A | Not measured | +| Test ID 2b | 10 dBm $\pm$ (6+TT) | N/A | Not measured | +| Test ID 2c | 15 dBm $\pm$ (5+TT) | N/A | Not measured | +| Test ID 3a | N/A | -10 dBm $\pm$ (7+TT) | Not measured | +| Test ID 3b | N/A | 10 dBm $\pm$ (6+TT) | Not measured | +| Test ID 3c | N/A | 15 dBm $\pm$ (5+TT) | Not measured | + +NOTE 1: In addition NOTE 2 in Table 6.2.2A-1 in TS 36.101 [5] and/or NOTE 3 in Table 6.2.1-1 in TS 38.101-1 [2] shall apply to the tolerances. + +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2B.4.1.3\_1.5-3 and Table 6.2B.4.1.3\_1.5-4. + +**Table 6.2B.4.1.3\_1.5-3: Test Tolerance for UE maximum output power (Separate measurements over E-UTRA and NR CCs)** + +| Uplink TX | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6\text{GHz}$ | +|-----------|-----------------------------------------------|------------------------|----------------------------------------|--------------------------------------| +| E-UTRA | BW $\leq 20\text{MHz}$ | 0.7 dB | 1.0 dB | N/A | +| NR | BW $\leq 40\text{MHz}$ | 0.7 dB | 1.0 dB | 1.0 dB | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | 1.0 dB | 1.0 dB | 1.0 dB | + +**Table 6.2B.4.1.3\_1.5-4: Test Tolerance for UE maximum output power (Combined measurements of E-UTRA and NR CCs)** + +| TT for overall output power | | | | | | | | | | | | +|-----------------------------|------------------------|----------------------------------------|------------------------|----------------------------------------|----------------------------------------|----------------------------------------------|----------------------------------------|----------------------------------------|-----------------------------------------------|----------------------------------------|----------------------------------------| +| | | | NR | | | | | | | | | +| | | | BW $\leq 20\text{MHz}$ | | | $20\text{MHz} < \text{BW} \leq 40\text{MHz}$ | | | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | | | +| | | | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | +| E-UTRA | BW $\leq 20\text{MHz}$ | $f \leq 3.0\text{GHz}$ | 0.7 dB | 1.0 dB | 1.0 dB | 0.7 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | +| | | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | 1.0 dB | + +For the UE which supports inter-band EN-DC configuration, $\Delta T_{\text{IB,c}}$ in 6.2B.4.2 applies where unless otherwise stated, the same $\Delta T_{\text{IB,c}}$ is applicable to NR band(s) part for DC configurations which have the same NR operating band combination. Unless otherwise stated, $\Delta T_{\text{IB,c}}$ is set to zero. + +##### 6.2B.4.1.4 Configured Output Power for Inter-Band EN-DC including FR2 (1 NR CC) + +###### 6.2B.4.1.4.1 Test purpose + +Same test purpose as in clause 6.2.4.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.2B.4.1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +The requirements of this test for NR carrier are covered in test cases 6.2B.1.4 Maximum output power for Inter-Band EN-DC including FR2, 6.2B.2.4 Maximum output power reduction for Inter-Band EN-DC including FR2 and 6.2B.3.4 UE maximum output power with additional requirements for Inter-Band EN-DC including FR2 to all types of NR UE release 15 and forward. + +###### 6.2B.4.1.4.3 Minimum conformance requirements + +UE configured output power requirement for E-UTRA single carrier and CA operation specified in subclauses 6.2.5 and 6.2.5A of [10] and for NR single carrier and CA operation specified in subclause 6.2.4, 6.2A.4 and 6.2D.4 of [9] apply. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.4.1.4. + +###### 6.2B.4.1.4.4 Test description + +This test is covered by clause 6.2B.1.4 Maximum output power for Inter-Band EN-DC including FR2, 6.2B.2.4 Maximum output power reduction for Inter-Band EN-DC including FR2 and 6.2B.3.4 UE maximum output power with additional requirements for Inter-Band EN-DC including FR2. + +###### 6.2B.4.1.4.5 Test requirement + +This test is covered by clause 6.2B.1.4 Maximum output power for Inter-Band EN-DC including FR2, 6.2B.2.4 Maximum output power reduction for Inter-Band EN-DC including FR2 and 6.2B.3.4 UE maximum output power with additional requirements for Inter-Band EN-DC including FR2. + +##### 6.2B.4.1.4\_1 Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.2.4\_1 in TS 38.521-2 is incomplete for power class 1, 2 and 4. +- The referred test case 6.2.4\_1 in TS 38.521-2 is incomplete for band n259. + +###### 6.2B.4.1.4\_1.1 Test purpose + +Same test purpose as in clause 6.2.4\_1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.2B.4.1.4\_1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 16 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC and supporting *mpr-PowerBoost-FR2-r16* UE capability. + +###### 6.2B.4.1.4\_1.3 Minimum conformance requirements + +UE configured output power requirement for E-UTRA single carrier and CA operation specified in subclauses 6.2.5 and 6.2.5A of [10] and for NR single carrier specified in subclause 6.2.4\_1 of [9] apply. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2B.4.1.4. + +###### 6.2B.4.1.4\_1.4 Test description + +Same test description as in clause 6.2.4\_1.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.2.4\_1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 4.6-1. +- 3.1. Downlink E-UTRA signals are initially set up according to TS 36.521-1 [10] Annex C, clauses C.0, C.1 and C.3.0, and uplink signals according to Annex H, clauses H.1 and H.3.0. +- 4.1. The E-UTRA UL Reference Measurement channels are set according to Table 4.6-1. + +Step 6 of Initial conditions as in clause 6.2.4\_1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. + +Same test procedure as in clause 6.2.4\_1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.2B.4.1.4\_1.5 Test requirement + +Same test requirement as in clause 6.2.4\_1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.2B.4.1.5 Configured Output Power for Inter-Band EN-DC including both FR1 and FR2 + +###### 6.2B.4.1.5.1 Test purpose + +Same test purpose as in clause 6.2.4.1 in TS 38.521-1 [8] for NR FR1 carrier and 6.2.4.1 in TS 38.521-2 [9] for NR FR2 carrier. + +###### 6.2B.4.1.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum output power apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.2B. + +#### 6.2B.4.2 $\Delta T_{IB,c}$ for EN-DC + +For the UE which supports inter-band EN-DC configuration, $\Delta T_{IB,c}$ in Tables below applies where unless otherwise stated, the same $\Delta T_{IB,c}$ is applicable to NR band(s) part for DC configurations which have the same NR operating band combination. Unless otherwise stated, $\Delta T_{IB,c}$ is set to zero. + +Unless $\Delta T_{IB,c}$ is specified for the NE-DC configuration, the specified $\Delta T_{IB,c}$ for the EN-DC configuration including same bands as the corresponding NE-DC configuration is applicable for the NE-DC configuration. + +##### 6.2B.4.2.1 Intra-Band Contiguous EN-DC + +$\Delta T_{IB,c}$ is not applicable for intra-band contiguous EN-DC. + +##### 6.2B.4.2.2 Intra-Band non-Contiguous EN-DC + +$\Delta T_{IB,c}$ is not applicable for intra-band non-contiguous EN-DC. + +6.2B.4.2.3 Inter-Band EN-DC within FR1 + +6.2B.4.2.3.1 $\Delta T_{IB,c}$ for EN-DC two bands + +**Table 6.2B.4.2.3.1-1: $\Delta T_{IB,c}$ due to EN-DC(two bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1_n3 | 1 | 0.3 | +| | n3 | 0.3 | +| DC_1_n5 | 1 | 0.3 | +| | n5 | 0.3 | +| DC_1_n8 | 1 | 0.3 | +| | n8 | 0.3 | +| DC_1_n28 | 1 | 0.3 | +| | n28 | 0.6 | +| DC_1_n41 | 1 | 0.5 | +| | n41 | 0.5 | +| DC_1_n77 | 1 | 0.6 | +| | n77 | 0.8 | +| DC_1_n78 | 1 | 0.3 | +| | n78 | 0.8 | +| DC_2_n5 | 2 | 0.3 | +| | n5 | 0.3 | +| DC_2_n41 | 2 | 0.5 | +| | n41 | $0.4^1$ | +| | | $0.9^2$ | +| DC_2_n66 | 2 | 0.5 | +| | n66 | 0.5 | +| DC_2_n71 | 2 | 0.3 | +| | n71 | 0.3 | +| DC_2_n77 | 2 | 0.6 | +| DC_2-2_n77 | n77 | 0.8 | +| DC_2_n78 | 2 | 0.6 | +| | n78 | 0.8 | +| DC_3_n1 | 3 | 0.3 | +| | n1 | 0.3 | +| DC_3_n5 | 3 | 0.3 | +| | n5 | 0.3 | +| DC_3_n7 | 3 | 0.5 | +| | n7 | 0.5 | +| DC_3_n8 | 3 | 0.3 | +| | n8 | 0.3 | +| DC_3_n28 | 3 | 0.3 | +| | n28 | 0.3 | +| DC_3_n41 | 3 | 0.5 | +| | n41 | $0.3^3$ | +| | | $0.8^4$ | +| DC_3_n77 | 3 | 0.6 | +| | n77 | 0.8 | +| DC_3_n78 | 3 | 0.6 | +| | n78 | 0.8 | +| DC_5_n2,
DC_5-5_n2 | 5 | 0.3 | +| | n2 | 0.3 | +| DC_5_n66 | 5 | 0.3 | +| | n66 | 0.3 | +| DC_5_n77 | 5 | 0.6 | +| | n77 | 0.8 | +| DC_5_n78 | 5 | 0.6 | +| | n78 | 0.8 | +| DC_7_n1 | 7 | 0.6 | +| | n1 | 0.5 | + +| | | | +|-------------------------|-----|-----| +| DC_7_n3 | 7 | 0.5 | +| | n3 | 0.5 | +| DC_7_n5 | 7 | 0.3 | +| | n5 | 0.3 | +| DC_7_n8 | 7 | 0.3 | +| | n8 | 0.6 | +| DC_7_n28 | 7 | 0.3 | +| | n28 | 0.3 | +| DC_7_n66,
DC_7-7_n66 | 7 | 0.5 | +| | n66 | 0.5 | +| DC_7_n78,
DC_7-7_n78 | 7 | 0.5 | +| | n78 | 0.8 | +| DC_8_n1 | 8 | 0.3 | +| | n1 | 0.3 | +| DC_8_n3 | 8 | 0.3 | +| | n3 | 0.3 | +| DC_8_n20 | 8 | 0.4 | +| | n20 | 0.4 | +| DC_8_n28 | 8 | 0.6 | +| | n28 | 0.5 | +| DC_8_n41 | 8 | 0.3 | +| | n41 | 0.3 | +| DC_8_n77 | 8 | 0.6 | +| | n77 | 0.8 | +| DC_8_n78 | 8 | 0.6 | +| | n78 | 0.8 | +| DC_11_n77 | 11 | 0.4 | +| | n77 | 0.8 | +| DC_11_n78 | 11 | 0.4 | +| | n78 | 0.8 | +| DC_12_n2 | 12 | 0.3 | +| | n2 | 0.3 | +| DC_12_n5 | 12 | 0.4 | +| | n5 | 0.8 | +| DC_12_n66 | 12 | 0.8 | +| | n66 | 0.3 | +| DC_12_n78 | 12 | 0.5 | +| | n78 | 0.8 | +| DC_13_n2 | 13 | 0.3 | +| | n2 | 0.3 | +| DC_13_n66 | 13 | 0.3 | +| | n66 | 0.3 | +| DC_13_n77 | 13 | 0.5 | +| | n77 | 0.8 | +| DC_14_n2 | 14 | 0.3 | +| | n2 | 0.3 | +| DC_14_n66 | 14 | 0.3 | +| | n66 | 0.3 | +| DC_18_n77 | 18 | 0.3 | +| | n77 | 0.8 | +| DC_18_n78 | 18 | 0.3 | +| | n78 | 0.8 | +| DC_19_n77 | 19 | 0.3 | +| | n77 | 0.8 | +| DC_19_n78 | 19 | 0.3 | +| | n78 | 0.8 | + +| | | | +|------------------------|-----|------------------| +| DC_20_n1 | 20 | 0.3 | +| | n1 | 0.3 | +| DC_20_n3 | 20 | 0.3 | +| | n3 | 0.3 | +| DC_20_n7 | 20 | 0.3 | +| | n7 | 0.3 | +| DC_20_n8 | 20 | 0.4 | +| | n8 | 0.4 | +| DC_20_n28 | 20 | 0.5 | +| | n28 | 0.5 | +| DC_20_n78 | 20 | 0.6 | +| | n78 | 0.8 | +| DC_21_n77 | 21 | 0.4 | +| | n77 | 0.8 | +| DC_21_n78 | 21 | 0.4 | +| | n78 | 0.8 | +| DC_25_n41 | 25 | 0.5 | +| | n41 | 0.4 1 | +| | | 0.9 2 | +| DC_26_n41 | 26 | 0.3 | +| | n41 | 0.3 | +| DC_26_n77 | 26 | 0.3 | +| | n77 | 0.8 | +| DC_26_n78 | 26 | 0.3 | +| | n78 | 0.8 | +| DC_28_n5 | 28 | 0.5 | +| | n5 | 0.5 | +| DC_28_n77 | 28 | 0.5 | +| | n77 | 0.8 | +| DC_28_n78 | 28 | 0.5 | +| | n78 | 0.8 | +| DC_30_n5 | 30 | 0.3 | +| | n5 | 0.3 | +| DC_30_n66 | 30 | 0.5 | +| | n66 | 0.8 | +| DC_38_n78 | n78 | 0.5 | +| DC_39_n41 | 39 | 0.5 | +| | n41 | 0.5 | +| DC_39_n79 | 39 | 0.3 | +| | n79 | 0.8 | +| DC_40_n1 | n1 | 0.5 | +| | 40 | 0.5 | +| DC_40_n41 5 | 40 | 0.5 | +| | n41 | 0.5 | +| DC_40_n78 | n78 | 0.5 6 | +| DC_40_n79 | 40 | 0.3 | +| | n79 | 0.8 | +| DC_41_n28 | 41 | 0.3 | +| | n28 | 0.3 | +| DC_41_n77 | 41 | 0.3 | +| | n77 | 0.8 | +| DC_41_n78 | 41 | 0.3 | +| | n78 | 0.8 | +| DC_41_n79 | 41 | 0.3 | +| | n79 | 0.8 | +| DC_48_n5 | 48 | 0.3 | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|-----|------------------| +| | n5 | 0.3 | +| DC_48_n46 | 48 | 0.8 | +| DC_48_n66 | 48 | 0.8 | +| | n66 | 0.6 | +| DC_66_n2 | 66 | 0.5 | +| | n2 | 0.5 | +| DC_66_n5 | 66 | 0.3 | +| | n5 | 0.3 | +| DC_66_n41 | 66 | 0.5 | +| | n41 | 0.8 1 | +| | | 1.3 2 | +| DC_66_n71 | 66 | 0.3 | +| | n71 | 0.3 | +| DC_66_n77 | 66 | 0.6 | +| DC_66-66_n77 | n77 | 0.8 | +| DC_66_n78 | 66 | 0.6 | +| | n78 | 0.8 | +| DC_71_n2 | 71 | 0.3 | +| | n2 | 0.3 | +| DC_71_n66 | 71 | 0.3 | +| | N66 | 0.3 | +| NOTE 1: The requirement is applied for UE transmitting on the frequency range of 2545-2690 MHz. | | | +| NOTE 2: The requirement is applied for UE transmitting on the frequency range of 2496-2545 MHz. | | | +| NOTE 3: Applicable for the frequency range of 2515 - 2690 MHz. | | | +| NOTE 4: Applicable for the frequency range of 2496 - 2515 MHz. | | | +| NOTE 5: Applicable for UE supporting inter-band EN-DC without simultaneous Rx/Tx. | | | +| NOTE 6: Only applicable for UE supporting inter-band carrier aggregation with uplink in one E-UTRA band and without simultaneous Rx/Tx. | | | + +6.2B.4.2.3.2 $\Delta T_{IB,c}$ for EN-DC three bands + +**Table 6.2B.4.2.3.2-1: $\Delta T_{IB,c}$ due to EN-DC (three bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1-3_n28 | 1 | 0.3 | +| | 3 | 0.3 | +| | n28 | 0.6 | +| DC_1-3_n41 | 1 | 0.5 | +| | 3 | 0.5 | +| | n41 | 0.3 3 | +| DC_1-3_n77 | 1 | 0.6 | +| | 3 | 0.6 | +| | n77 | 0.8 | +| DC_1-3_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | n78 | 0.8 | +| DC_1-3_n79 | 1 | 0.3 | +| | 3 | 0.3 | +| DC_1-5_n78 | 1 | 0.3 | +| | 5 | 0.6 | +| | n78 | 0.8 | +| DC_1-7_n3 | 1 | 0.6 | +| | 7 | 0.6 | +| | n3 | 0.6 | +| DC_1-7_n28 | 1 | 0.5 | +| | 7 | 0.6 | +| | n28 | 0.6 | +| DC_1-7_n78 | 1 | 0.6 | +| | 7 | 0.6 | +| | n78 | 0.8 | +| DC_1-8_n3 | 1 | 0.3 | +| | 8 | 0.3 | +| | n3 | 0.3 | +| DC_1-8_n78 | 1 | 0.3 | +| | 8 | 0.6 | +| | n78 | 0.8 | +| DC_1-18_n77 | 1 | 0.3 | +| | 18 | 0.3 | +| | n77 | 0.8 | +| DC_1-19_n77 | 1 | 0.3 | +| | 19 | 0.3 | +| | n77 | 0.8 | +| DC_1-19_n78 | 1 | 0.3 | +| | 19 | 0.3 | +| | n78 | 0.8 | +| DC_1-19_n79 | 1 | 0.3 | +| | 19 | 0.3 | +| DC_1-20_n3 | 1 | 0.3 | +| | 20 | 0.3 | +| | n3 | 0.3 | +| DC_1-20_n28 | 1 | 0.3 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| DC_1-20_n78 | 1 | 0.3 | +| | 20 | 0.3 | +| | n78 | 0.8 | +| DC_1-21_n77 | 1 | 0.3 | + +| | | | +|------------------------------|-----------|-----| +| | 21 | 0.3 | +| | n77 | 0.8 | +| DC_1-21_n78 | 1 | 0.6 | +| | 21 | 0.4 | +| | n78 | 0.8 | +| DC_1-21_n79 | 1 | 0.3 | +| | 21 | 0.3 | +| DC_1-28_n3 | 1 | 0.3 | +| | 28 | 0.6 | +| | n3 | 0.3 | +| DC_1-28_n78
DC_1_n28-n78 | 1 | 0.3 | +| | 28 or n28 | 0.6 | +| | n78 | 0.8 | +| DC_1_n28-n79 | 1 | 0.3 | +| | n28 | 0.3 | +| DC_1-41_n28 | 1 | 0.5 | +| | 41 | 0.5 | +| | n28 | 0.5 | +| DC_1-41_n41 | 1 | 0.5 | +| | 41 | 0.5 | +| | n41 | 0.5 | +| DC_1-41_n77 | 1 | 0.5 | +| | 41 | 0.5 | +| | n77 | 0.8 | +| DC_1-41_n78 | 1 | 0.5 | +| | 41 | 0.5 | +| | n78 | 0.8 | +| DC_1-42_n77 | 1 | 0.6 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_1-42_n78 | 1 | 0.3 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_1-42_n79 | 1 | 0.3 | +| | 42 | 0.8 | +| DC_1_n77-n79 | 1 | 0.6 | +| | n77 | 0.8 | +| DC_1_n78-n79 | 1 | 0.3 | +| | n78 | 0.8 | +| | n79 | 0.5 | +| DC_2-5_n66 | 2 | 0.5 | +| | 5 | 0.3 | +| | n66 | 0.5 | +| DC_2_n5-n77 | 2 | 0.6 | +| | n5 | 0.3 | +| | n77 | 0.8 | +| DC_2-13_n77 | 2 | 0.6 | +| | 13 | 0.5 | +| | n77 | 0.8 | +| DC_2-14_n2 | 2 | 0.3 | +| | 14 | 0.3 | +| | n2 | 0.3 | +| DC_2-14_n66
DC_2-2-14_n66 | 2 | 0.5 | +| | 14 | 0.3 | +| | n66 | 0.5 | +| DC_2-30_n66 | 2 | 0.5 | + +| | | | +|-------------|-----|------------------| +| | 30 | 0.3 | +| | n66 | 0.5 | +| DC_2-66_n5 | 2 | 0.5 | +| | 66 | 0.5 | +| | n5 | 0.3 | +| DC_2-66_n41 | 2 | 0.5 | +| | 66 | 0.5 | +| | n41 | 0.8 1 | +| | | 1.3 2 | +| DC_2-66_n71 | 2 | 0.5 | +| | 66 | 0.5 | +| | n71 | 0.3 | +| DC_2-66_n77 | 2 | 0.6 | +| | 66 | 0.6 | +| | n77 | 0.8 | +| DC_2-(n)71 | 2 | 0.3 | +| | 71 | 0.3 | +| | n71 | | +| DC_3-5_n78 | 3 | 0.6 | +| | 5 | 0.6 | +| | n78 | 0.8 | +| DC_3-7_n28 | 3 | 0.5 | +| | 7 | 0.5 | +| | n28 | 0.3 | +| DC_3-7_n78 | 3 | 0.6 | +| | 7 | 0.6 | +| | n78 | 0.8 | +| DC_3-8_n78 | 3 | 0.6 | +| | 8 | 0.6 | +| | n78 | 0.8 | +| DC_3-18_n77 | 3 | 0.6 | +| | 18 | 0.3 | +| | n77 | 0.8 | +| DC_3-18_n78 | 3 | 0.6 | +| | 18 | 0.3 | +| | n78 | 0.8 | +| DC_3-19_n77 | 3 | 0.6 | +| | 19 | 0.3 | +| | n77 | 0.8 | +| DC_3-19_n78 | 3 | 0.6 | +| | 19 | 0.3 | +| | n78 | 0.8 | +| DC_3-19_n79 | 3 | 0.3 | +| | 19 | 0.3 | +| DC_3-20_n1 | 3 | 0.3 | +| | 20 | 0.3 | +| | n1 | 0.3 | +| DC_3-20_n28 | 3 | 0.3 | +| | 20 | 0.5 | +| | n28 | 0.5 | +| DC_3-20_n78 | 3 | 0.5 | +| | 20 | 0.3 | +| | n78 | 0.8 | +| DC_3-21_n77 | 3 | 0.8 | + +| | | | +|--------------|-----|------------------| +| | 21 | 0.9 | +| | n77 | 0.8 | +| DC_3-21_n78 | 3 | 0.8 | +| | 21 | 0.9 | +| | n78 | 0.8 | +| DC_3-21_n79 | 3 | 0.8 | +| | 21 | 0.9 | +| DC_3-28_n78 | 3 | 0.5 | +| | 28 | 0.3 | +| | n78 | 0.8 | +| DC_3_n28-n78 | 3 | 0.5 | +| | n28 | 0.3 | +| | n78 | 0.8 | +| DC_3-40_n1 | 3 | 0.5 | +| | 40 | 0.5 | +| | n1 | 0.5 | +| DC_3-41_n28 | 3 | 0.5 | +| | 41 | 0.3 3 | +| | n28 | 0.3 | +| DC_3-41_n41 | 3 | 0.5 | +| | 41 | 0.3 3 | +| | n41 | 0.3 3 | +| | | 0.8 4 | +| DC_3-41_n77 | 3 | 0.6 | +| | 41 | 0.3 3 | +| | n77 | 0.8 | +| DC_3-42_n77 | 3 | 0.6 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_3-42_n78 | 3 | 0.6 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_3-42_n79 | 3 | 0.6 | +| | 42 | 0.8 | +| DC_3_n77-n79 | 3 | 0.6 | +| | n77 | 0.8 | +| DC_3_n78-n79 | 3 | 0.6 | +| | n78 | 0.8 | +| | n79 | 0.5 | +| DC_5-7_n78 | 5 | 0.6 | +| | 7 | 0.6 | +| | n78 | 0.8 | +| DC_5-30_n66 | 5 | 0.3 | +| | 30 | 0.3 | +| | n66 | 0.5 | +| DC_7-20_n28 | 7 | 0.3 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| DC_7-20_n1 | 7 | 0.6 | +| | 20 | 0.3 | +| | n1 | 0.5 | +| DC_7-20_n3 | 7 | 0.5 | + +| | | | +|-------------------------------|-----|------------------| +| | 20 | 0.3 | +| | n3 | 0.5 | +| DC_7-20_n78 | 7 | 0.3 | +| | 20 | 0.3 | +| | n78 | 0.8 | +| DC_7-28_n3 | 7 | 0.5 | +| | 28 | 0.3 | +| | n3 | 0.5 | +| DC_7-28_n78 | 7 | 0.3 | +| | 28 | 0.3 | +| | n78 | 0.8 | +| DC_7_n28-n78 | 7 | 0.3 | +| | n28 | 0.3 | +| | n78 | 0.8 | +| DC_13_n2-n77 | 13 | 0.3 | +| | n2 | 0.6 | +| | n77 | 0.8 | +| DC_13-66-n2 | 13 | 0.3 | +| | 66 | 0.5 | +| | n2 | 0.5 | +| DC_13-66_n77 | 13 | 0.5 | +| | 66 | 0.6 | +| | n77 | 0.8 | +| DC_14-66_n2
DC_14-66-66_n2 | 14 | 0.3 | +| | 66 | 0.5 | +| | n2 | 0.5 | +| DC_14-66_n66 | 14 | 0.3 | +| | 66 | 0.3 | +| | n66 | 0.3 | +| DC_18-41_n3 | 18 | 0.3 | +| | 41 | 0.3 3 | +| | | 0.8 4 | +| | n3 | 0.5 | +| DC_18-41_n77 | 18 | 0.3 | +| | 41 | 0.3 3 | +| | | 0.8 4 | +| | n77 | 0.8 | +| DC_18-41_n78 | 18 | 0.3 | +| | 41 | 0.3 3 | +| | | 0.8 4 | +| | n78 | 0.8 | +| DC_19-21_n77 | 19 | 0.3 | +| | 21 | 0.4 | +| | n77 | 0.8 | +| DC_19-21_n78 | 19 | 0.3 | +| | 21 | 0.4 | +| | n78 | 0.8 | +| DC_19-21_n79 | 19 | 0.3 | +| | 21 | 0.4 | +| DC_19-42_n77 | 19 | 0.3 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_19-42_n78 | 19 | 0.3 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_19-42_n79 | 19 | 0.3 | + +| | | | | +|---------------------------------------------------------------------------------------------------|-----|-----|--| +| | 42 | 0.8 | | +| DC_19_n77-n79 | 19 | 0.3 | | +| | n77 | 0.8 | | +| DC_19_n78-n79 | 19 | 0.3 | | +| | n78 | 0.8 | | +| | n79 | 0.5 | | +| DC_20_n28-n78 | 20 | 0.6 | | +| | n28 | 0.6 | | +| | n78 | 0.8 | | +| DC_20_n76-n78 | 20 | 0.5 | | +| | n78 | 0.8 | | +| DC_21-42_n77 | 21 | 0.4 | | +| | 42 | 0.8 | | +| | n77 | 0.8 | | +| DC_21-42_n78 | 21 | 0.4 | | +| | 42 | 0.8 | | +| | n78 | 0.8 | | +| DC_21-42_n79 | 21 | 0.4 | | +| | 42 | 0.8 | | +| DC_21_n77-n79 | 21 | 0.4 | | +| | n77 | 0.8 | | +| DC_21_n78-n79 | 21 | 0.4 | | +| | n78 | 0.8 | | +| | n79 | 0.5 | | +| DC_28_n7-n78 | 28 | 0.3 | | +| | n7 | 0.3 | | +| | n78 | 0.8 | | +| DC_28-42_n78 | 28 | 0.5 | | +| | 42 | 0.8 | | +| | n78 | 0.8 | | +| DC_41-42_n78 | 41 | 0.5 | | +| | 42 | 0.8 | | +| | n78 | 0.8 | | +| DC_66_n2-n77 | 66 | 0.6 | | +| | n2 | 0.6 | | +| | n77 | 0.8 | | +| DC_66_n5-n77 | 66 | 0.6 | | +| | n5 | 0.3 | | +| | n77 | 0.8 | | +| DC_66-(n)71 | 66 | 0.3 | | +| | 71 | 0.3 | | +| | n71 | | | +| NOTE 1: The requirement is applied for UE transmitting on the frequency range of 2545-2690 MHz. | | | | +| NOTE 2: The requirement is applied for UE transmitting on the frequency range of 2496-2545 MHz. | | | | +| NOTE 3: The requirement is applied for UE transmitting on the frequency range of 2515 – 2690 MHz. | | | | +| NOTE 4: The requirement is applied for UE transmitting on the frequency range of 2496 – 2515 MHz. | | | | +| | | | | + +6.2B.4.2.3.3 $\Delta T_{IB,c}$ for EN-DC four bands + +**Table 6.2B.4.2.3.3-1: $\Delta T_{IB,c}$ due to EN-DC(four bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|---------------------------------|-------------------|------------------------| +| DC_1-3-7_n28 | 1 | 0.6 | +| | 3 | 0.6 | +| | 7 | 0.6 | +| | n28 | 0.6 | +| DC_1-3-7_n78 | 1 | 0.7 | +| | 3 | 0.7 | +| | 7 | 0.7 | +| | n78 | 0.8 | +| DC_1-3-8_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 8 | 0.6 | +| | n78 | 0.8 | +| DC_1-3-19_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 19 | 0.3 | +| | n78 | 0.8 | +| DC_1-3-19_n79 | 1 | 0.3 | +| | 3 | 0.3 | +| | 19 | 0.3 | +| DC_1-3-20_n28 | 1 | 0.3 | +| | 3 | 0.3 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| DC_1-3-20_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 20 | 0.3 | +| | n78 | 0.8 | +| DC_1-3-21_n77 | 1 | 0.6 | +| | 3 | 0.8 | +| | 21 | 0.9 | +| | n77 | 0.8 | +| DC_1-3-21_n78 | 1 | 0.6 | +| | 3 | 0.8 | +| | 21 | 0.9 | +| | n78 | 0.8 | +| DC_1-3-21_n79 | 1 | 0.3 | +| | 3 | 0.8 | +| | 21 | 0.9 | +| DC_1-3-28_n78
DC_1-3_n28-n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 28 or n28 | 0.6 | +| | n78 | 0.8 | +| DC_1-3-42_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_1-3-42_n79 | 1 | 0.6 | +| | 3 | 0.6 | +| | 42 | 0.8 | +| DC_1-7-20_n28 | 1 | 0.5 | +| | 7 | 0.6 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| DC_1-7-20_n78 | 1 | 0.6 | + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|----------------------------------|-------------------|------------------------| +| | 7 | 0.7 | +| | 20 | 0.4 | +| | n78 | 0.8 | +| DC_1-7-28-n78 | 1 | 0.6 | +| | 7 | 0.6 | +| | 28 | 0.6 | +| | n78 | 0.8 | +| DC_1-7_n28-n78 | 1 | 0.6 | +| | 7 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_1-19-42_n77 | 1 | 0.6 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_1-19-42_n78 | 1 | 0.3 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_1-19-42_n79 | 1 | 0.3 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| DC_1-20_n28-n78 | 1 | 0.3 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_1-21-42_n77 | 1 | 0.6 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_1-21-42_n78 | 1 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_1-21-42_n79 | 1 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| DC_2-7-13_n66
DC_2-7-7-13_n66 | 2 | 0.5 | +| | 7 | 0.5 | +| | 13 | 0.3 | +| | n66 | 0.5 | +| DC_2-7-66_n66
DC_2-7-7-66_n66 | 2 | 0.5 | +| | 7 | 0.5 | +| | 66 | 0.5 | +| | n66 | | +| DC_2-7-66_n78
DC_2-7-7-66_n78 | 2 | 0.6 | +| | 7 | 0.5 | +| | 66 | 0.6 | +| | n78 | 0.8 | +| DC_2-13-66_n77 | 2 | 0.5 | +| | 13 | 0.3 | +| | 66 | 0.5 | +| | n77 | 0.8 | +| DC_2-14-66_n2 | 2 | 0.5 | + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|------------------------------------|-------------------|------------------------| +| DC_2-14-66-66_n2 | 14 | 0.3 | +| | 66 | 0.5 | +| | n2 | 0.5 | +| DC_2-14-66_n66
DC_2-2-14-66_n66 | 2 | 0.5 | +| | 14 | 0.3 | +| | 66 | 0.5 | +| | n66 | 0.5 | +| DC_2-66_n5-n77 | 2 | 0.6 | +| | 66 | 0.6 | +| | n5 | 0.3 | +| | n77 | 0.8 | +| DC_2-66-(n)71 | 2 | 0.5 | +| | 66 | 0.5 | +| | 71 | 0.3 | +| | n71 | | +| DC_3-7-20_n28 | 3 | 0.5 | +| | 7 | 0.5 | +| | 20 | 0.6 | +| | n28 | 0.5 | +| DC_3-7-20_n78 | 3 | 0.6 | +| | 7 | 0.6 | +| | 20 | 0.3 | +| | n78 | 0.8 | +| DC_3-7-28_n78 | 3 | 0.6 | +| | 7 | 0.6 | +| | 28 | 0.6 | +| | n78 | 0.8 | +| DC_3-7_n28-n78 | 3 | 0.6 | +| | 7 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_3-19-21_n78 | 3 | 0.8 | +| | 19 | 0.3 | +| | 21 | 0.9 | +| | n78 | 0.8 | +| DC_3-19-21_n79 | 3 | 0.8 | +| | 19 | 0.3 | +| | 21 | 0.9 | +| DC_3-19-42_n77 | 3 | 0.6 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_3-19-42_n78 | 3 | 0.6 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_3-19-42_n79 | 3 | 0.6 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| DC_3-20_n28-n78 | 3 | 0.6 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_3-21-42_n77 | 3 | 0.8 | + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| | 21 | 0.9 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_3-21-42_n78 | 3 | 0.8 | +| | 21 | 0.9 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_3-21-42_n79 | 3 | 0.8 | +| | 21 | 0.9 | +| | 42 | 0.8 | +| DC_7-20_n28-n78 | 7 | 0.3 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_13-66_n2-n77 | 13 | 0.3 | +| | 66 | 0.6 | +| | n2 | 0.6 | +| | n77 | 0.8 | +| DC_19-21-42_n77 | 19 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| | n77 | 0.8 | +| DC_19-21-42_n78 | 19 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_19-21-42_n79 | 19 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| | | | + +###### 6.2B.4.2.3.4 $\Delta T_{IB,c}$ for EN-DC five bands + +**Table 6.2B.4.2.3.4-1: $\Delta T_{IB,c}$ due to EN-DC (five bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1-3-7-20_n28 | 1 | 0.6 | +| | 3 | 0.6 | +| | 7 | 0.6 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| DC_1-3-7-20_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 7 | 0.6 | +| | 20 | 0.6 | +| | n78 | 0.6 | +| DC_1-3-7-28-n78 | 1 | 0.7 | +| | 3 | 0.7 | +| | 7 | 0.7 | +| | 28 | 0.6 | +| | n78 | 0.8 | +| DC_1-3-7_n28-n78 | 1 | 0.7 | +| | 3 | 0.7 | +| | 7 | 0.7 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_1-3-19-42_n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_1-3-19-42_n79 | 1 | 0.6 | +| | 3 | 0.6 | +| | 19 | 0.3 | +| | 42 | 0.8 | +| DC_1-3-20_n28-n78 | 1 | 0.6 | +| | 3 | 0.6 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_1-3-21-42_n78 | 1 | 0.6 | +| | 3 | 0.8 | +| | 21 | 0.9 | +| | 42 | 0.8 | +| | n78 | 0.6 | +| DC_1-3-21-42_n79 | 1 | 0.6 | +| | 3 | 0.8 | +| | 21 | 0.9 | +| | 42 | 0.8 | +| DC_1-7-20_n28-n78 | 1 | 0.6 | +| | 7 | 0.7 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | +| DC_1-19-21-42_n78 | 1 | 0.3 | +| | 19 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| | n78 | 0.8 | +| DC_1-19-21-42_n79 | 1 | 0.3 | + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| | 19 | 0.3 | +| | 21 | 0.4 | +| | 42 | 0.8 | +| DC_3-7-20_n28-n78 | 3 | 0.6 | +| | 7 | 0.6 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | + +6.2B.4.2.3.5 + + $\Delta T_{IB,c}$ for EN-DC six bands**Table 6.2B.4.2.3.5-1: $\Delta T_{IB,c}$ due to EN-DC (six bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1-3-7-20_n28-n78 | 1 | 0.7 | +| | 3 | 0.7 | +| | 7 | 0.7 | +| | 20 | 0.6 | +| | n28 | 0.6 | +| | n78 | 0.8 | + +6.2B.4.2.3a + +Inter-band NE-DC within FR1 + +Unless $\Delta T_{IB,c}$ is specified in this clause, the value of $\Delta T_{IB,c}$ for the correspondingly specified EN-DC configuration in clause 6.2B.4.2.3 is applicable. + +**Table 6.2B.4.2.3a-1: $\Delta T_{IB,c}$ due to NE-DC(two bands)** + +| Inter-band NE-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_n28_39 | n28 | 0.3 | +| | 39 | 0.3 | + +6.2B.4.2.4 + +Inter-band EN-DC including FR2 + +6.2B.4.2.4.1 + + $\Delta T_{IB,c}$ for EN-DC two bands + +Unless otherwise stated, $\Delta T_{IB,c}$ for E-UTRA and NR FR2 bands of inter-band EN-DC combinations defined in table 5.5B.5.1-1 is set to zero. + +**Table 6.2B.4.2.4.1-1: Void** + +6.2B.4.2.4.2 + + $\Delta T_{IB,c}$ for EN-DC three bands + +Unless otherwise stated, $\Delta T_{IB,c}$ for NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA bands for inter-band EN-DC defined in table 5.5B.5.2-1 is the same as those for the corresponding E-UTRA CA configuration specified in TS 36.101 [4], without the NR FR2 bands. + +###### **Table 6.2B.4.2.4.2-1: Void** + +6.2B.4.2.4.3 $\Delta T_{IB,c}$ for EN-DC four bands + +Unless otherwise stated, $\Delta T_{IB,c}$ for NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA bands for inter-band EN-DC defined in table 5.5B.5.3-1 is the same as those for the corresponding E-UTRA CA configuration specified in TS 36.101 [4], without the NR FR2 bands. + +###### **Table 6.2B.4.2.4.3-1: Void** + +6.2B.4.2.4.4 $\Delta T_{IB,c}$ for EN-DC five bands + +Unless otherwise stated, $\Delta T_{IB,c}$ for NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA bands for inter-band EN-DC defined in table 5.5B.5.4-1 is the same as those for the corresponding E-UTRA CA configuration specified in TS 36.101 [4], without the NR FR2 bands. + +###### **Table 6.2B.4.2.4.4-1: Void** + +6.2B.4.2.4.5 Void + +6.2B.4.2.5 Inter-band EN-DC including both FR1 and FR2 + +6.2B.4.2.5.1 $\Delta T_{IB,c}$ for EN-DC three bands + +Unless otherwise stated, for inter-band EN-DC configurations defined in table 5.5B.6.2-1, $\Delta T_{IB,c}$ for constituent NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA and NR FR1 bands is the same as those for the corresponding inter band EN-DC configuration without the NR FR2 bands specified in 6.2B.4.2.3. + +###### **Table 6.2B.4.2.5.1-1: Void** + +6.2B.4.2.5.2 $\Delta T_{IB,c}$ for EN-DC four bands + +Unless otherwise stated, for inter-band EN-DC configurations defined in table 5.5B.6.3-1, $\Delta T_{IB,c}$ for constituent NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA and NR FR1 bands is the same as those for the corresponding inter band EN-DC configuration without the NR FR2 bands specified in 6.2B.4.2.3. + +6.2B.4.2.5.3 $\Delta T_{IB,c}$ for EN-DC five bands + +Unless otherwise stated, for inter-band EN-DC configurations defined in table 5.5B.6.4-1, $\Delta T_{IB,c}$ for constituent NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA and NR FR1 bands is the same as those for the corresponding inter band EN-DC configuration without the NR FR2 bands specified in 6.2B.4.2.3. + +6.2B.4.2.5.4 $\Delta T_{IB,c}$ for EN-DC six bands + +Unless otherwise stated, for inter-band EN-DC configurations defined in table 5.5B.6.5-1, $\Delta T_{IB,c}$ for constituent NR FR2 bands is set to zero, and $\Delta T_{IB,c}$ for constituent E-UTRA and NR FR1 bands is the same as those for the corresponding inter band EN-DC configuration without the NR FR2 bands specified in 6.2B.4.2.3. + +### 6.2B.5 Configured Output Power for NR-DC + +#### 6.2B.5.1 Configured Output power Level + +##### 6.2B.5.1.1 Configured Output Power Level for Inter-band NR-DC between FR1 and FR2 + +###### 6.2B.5.1.1.1 Test purpose + +Same test purpose as in clause 6.2.4.1 in TS 38.521-1 [8] for NR FR1 carrier and 6.2.4.1 in TS 38.521-2 [9] for NR FR2 carrier. + +###### 6.2B.5.1.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for configured output power apply and are tested as part of the standalone NR within FR1 in clause 6.2.4 in TS 38.521-1 [8] and standalone NR within FR2 in clause 6.2.4 in TS 38.521-2 [9]. + +## 6.2E Transmitter power for V2X in FR1 + +### 6.2E.1 UE Maximum Output Power for V2X + +#### 6.2E.1.0 Minimum conformance requirements + +##### 6.2E.1.0.1 UE maximum output power for Intra-band contiguous V2X + +For intra-band contiguous V2X operating UE, the allowed UE maximum output power shall be applied in Table 6.2.2-1 [5] for E-UTRA SL transmission or applied in Table 6.2.1-1 [2] for NR SL transmission, respectively. + +**Table 6.2E.1.0.1-1: Maximum output power for V2X combination (continuous sub-blocks)** + +| V2X configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------|---------------------|--------------------| +| V2X_(n)47AA | | | 23 | +2/-3 1 | +| NOTE 1: If all transmitted resource blocks over all component carriers are confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or/and $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB | | | | | +| NOTE 2: Power Class 3 is the default power class unless otherwise stated. | | | | | +| NOTE 3: Only single switched UL is supported | | | | | + +##### 6.2E.1.0.2 UE maximum output power for Intra-band non-contiguous V2X + +For intra-band non-contiguous V2X operating UE, the allowed UE maximum output power shall be applied in Table 6.2.2-1 [5] for E-UTRA SL transmission or applied in Table 6.2.1-1 [2] for NR SL transmission, respectively. + +**Table 6.2E.1.0.2-1: Maximum output power for V2X combination (non-contiguous sub-blocks)** + +| V2X configuration | Power class 2 (dBm) | Tolerance (dB) | Power class 3 (dBm) | Tolerance (dB) | +|-------------------|---------------------|----------------|---------------------|--------------------| +| V2X_47A_n47A | | | 23 | +2/-3 1 | + +NOTE 1: If all transmitted resource blocks over all component carriers are confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or/and $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB + +NOTE 2: Power Class 3 is the default power class unless otherwise stated. + +NOTE 3: Only single switched UL is supported + +##### 6.2E.1.0.3 UE maximum output power for Inter-band V2X + +For the inter-band con-current NR V2X operation, the maximum output power is specified in Table 6.2E.1.0.3-1. The period of measurement shall be at least one sub frame (1ms). + +**Table 6.2E.1.0.3-1: Con-current V2X UE Power Class** + +| V2X con-current operating band Configuration | Class 1 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | Class 4 (dBm) | Tolerance (dB) | +|----------------------------------------------|---------------|----------------|---------------|----------------|---------------|--------------------|---------------|----------------| +| V2X_20A_n38A | | | | | 23 | +2/-3 4 | | | +| V2X_n71A_47A | | | | | 23 | +2/-3 4 | | | + +NOTE 1: The con-current band combinations is used for NR V2X Service. + +NOTE 2: $P_{PowerClass}$ is the maximum UE power specified without taking into account the tolerance + +NOTE 3: For inter-band con-current aggregation the maximum power requirement apply to the total transmitted power over all component carriers (per UE). + +NOTE 4: 4 refers to the transmission bandwidths (Figure 5.6-1) confined within $F_{UL\_low}$ and $F_{UL\_low} + 4$ MHz or $F_{UL\_high} - 4$ MHz and $F_{UL\_high}$ , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2E.1. + +#### 6.2E.1.1 UE maximum output power for Intra-band contiguous V2X + +##### 6.2E.1.1.1 Test purpose + +To verify that UE's transmit power doesn't exceed the range prescribed by the specified power value. + +##### 6.2E.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.2E.1.0.1. The requirements in this test case can be well covered in clause 6.2.2G of TS 36.521-1 [10] and clause 6.2E.1 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.2E.1.2 UE maximum output power for Intra-band non-contiguous V2X + +##### 6.2E.1.1.1 Test purpose + +To verify that UE's transmit power doesn't exceed the range prescribed by the specified power value. + +##### 6.2E.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.2E.1.0.2. The requirements in this test case can be well covered in clause 6.2.2G of TS 36.521-1 [10] and clause 6.2E.1 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.2E.1.3 UE maximum output power for Inter-band V2X + +##### 6.2E.1.3.1 UE maximum output power for Inter-band V2X with E-UTRA Uu and NR Sidelink + +###### Editor's note: + +- Connection diagram is FFS +- Generic test procedure is FFS +- Message exception is FFS +- Test requirements are FFS + +###### 6.2E.1.3.1.1 Test purpose + +Same test purpose as in clause 6.2E.1.1.1 in TS 38.521-1 [8]. + +###### 6.2E.1.3.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 16 and forward supporting concurrent operation between E-UTRA Uu and NR sidelink. + +###### 6.2E.1.3.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2E.1.0.3. + +###### 6.2E.1.3.1.4 Test description + +###### 6.2E.1.3.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and test channel bandwidths based on NR operating bands specified in clause 5.3E.3, channel bandwidths and sub-carrier spacings for the NR sidelink carrier specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each E-UTRA-NR V2X band combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.2E.1.3.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexes A.2 of TS 36.521-1 [10] for E-UTRA Uu carrier. The details of sidelink reference measurement channels (RMCs) are specified in A.7 of TS 38.521-1 [8] for NR V2X carrier. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521.1 [10] Annex C.2 for E-UTRA Uu carrier. + +**Table 6.2E.1.3.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------|----------------------------|-----------------------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1. | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 36.508 [11] subclause 4.3.1 for E-UTRA carrier and TS 38.508-1 [6] clause 4.3.1 for NR carrier. | Low range for E-UTRA Uu carrier and NR sidelink carrier
High range for E-UTRA Uu carrier and NR sidelink carrier | | | | | +| Test inter-band V2X bandwidth combination as specified in clause 5.3E.3. | Lowest for E-UTRA Uu carrier and NR sidelink carrier
Highest for E-UTRA Uu carrier and NR sidelink carrier | | | | | +| Test SCS for the NR carrier as specified in TS 38.521-1 [8] Table 5.3.5-1. | 15kHz | | | | | +| Test Parameters | | | | | | +| Test ID | E-UTRA Uu carrier | | | NR sidelink Carrier | | +| | Downlink Configuration | Uplink Configuration | | Modulation | PSCCH and PSSCH RB allocation (Note 2) | +| | | Modulation | RB allocation (Note 1) | | | +| 1 | N/A | QPSK | Partial_Allocation | CP-OFDM QPSK | Inner_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. + +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1E-1 in TS 38.521-1 [8]. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, FFS for TE diagram and clause FFS for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The parameter settings for the V2X sidelink transmission over PC5 are pre-configured according to TS 38.508-1 [5] clause 4.10. Message content exceptions are defined in clause 6.2E.1.3.1.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0, and uplink signals according to TS 36.521-1 [10] Annex H for the E-UTRA cell. +4. The E-UTRA UL Reference Measurement channels and the V2X Reference Measurement Channel are set according to Table 6.2E.1.3.1.4.1-1. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in State FFS according to TS 36.508 [7] clause FFS. + +###### 6.2E.1.3.1.4.2 Test procedure + +1. The SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the E-UTRA UL RMC according to Table 6.2E.1.3.1.4.1-1. The UE starts to perform the NR sidelink communication according to *SL-PreconfigurationNR*. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the E-UTRA UL and NR sidelink RMCs. +2. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE to ensure that the UE transmits at PUMAX level. Configure the UE to transmit PSCCH and PSSCH with the PUMAX level of each test points. +3. Measure the mean power over all component carriers in the inter-band con-current V2X configuration. The period of measurement shall be at least continuous duration of one sub-frame (1ms). + +###### 6.2E.1.3.1.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6 for E-UTRA Uu carrier and TS 38.508-1 [6] clause 4.6.3 for NR sidelink carrier with the following exceptions: + +FFS + +###### 6.2E.1.3.1.5 Test requirement + +FFS + +##### 6.2E.1.3.2 UE maximum output power reduction for Inter-band V2X with NR Uu and E-UTRA V2X + +###### Editor's note: + +- Connection diagram is FFS +- Generic test procedure is FFS +- Message exception is FFS +- Test requirements are FFS + +###### 6.2E.1.3.2.1 Test purpose + +Same test purpose as in clause 6.2E.1.1.1 in TS 38.521-1 [8]. + +###### 6.2E.1.3.2.2 Test applicability + +This test applies to all types of NR UE release 16 and forward supporting concurrent operation between NR Uu and E-UTRA V2X. + +###### 6.2E.1.3.2.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2E.1.0.3. + +###### 6.2E.1.3.2.4 Test description + +###### 6.2E.1.3.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and test channel bandwidths based on NR operating bands specified in clause 5.3E.3, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA V2X carrier are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each E-UTRA-NR V2X band combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.2E.1.3.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2 of TS 38.521-1 [8] for NR Uu carrier. The details of sidelink reference measurement channels (RMCs) are specified in Annex A.6 of TS 36.521-1 [10] for E-UTRA V2X carrier. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [8] Annex C.2 for NR Uu carrier. + +**Table 6.2E.1.3.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------|---------------------------|----------------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1. | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 36.508 [11] subclause 4.3.1 for E-UTRA carrier and TS 38.508-1 [6] clause 4.3.1 for NR carrier. | Low range for NR Uu carrier and E-UTRA sidelink carrier
High range for NR Uu carrier and E-UTRA sidelink carrier | | | | | +| Test inter-band V2X bandwidth combination as specified in clause 5.3E.3. | Lowest for NR Uu carrier and E-UTRA sidelink carrier
Highest for NR Uu carrier and E-UTRA sidelink carrier | | | | | +| Test SCS for the NR carrier as specified in TS 38.521-1 [8] Table 5.3.5-1. | 15kHz | | | | | +| Test Parameters | | | | | | +| Test ID | NR Uu Carrier | | | E-UTRA V2X Carrier | | +| | Downlink Configuration | Uplink Configuration | | Modulation | PSSCH RB allocation | +| | | Modulation | RB allocation (Note 1) | | | +| 1 | N/A | DFT-s-OFDM QPSK | Inner Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1E-1 in TS 38.521-1 [8]. | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, FFS for TE diagram and clause FFS for UE diagram. +2. The parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. The parameter settings for the E-UTRA V2X sidelink transmission are pre-configured according to TS 38.508-1 [5] subclause 4.10. Message content exceptions are defined in clause 6.2E.1.3.2.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [8] Annex C.0, and uplink signals according to TS 38.521-1 [8] Annex G for the NR cell. +4. The NR UL Reference Measurement channels and the E-UTRA V2X Reference Measurement Channel are set according to Table 6.2E.1.3.2.4.1-1. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +8. Ensure the UE is in state FFS according to TS 38.508-1 [6] clause FFS. + +###### 6.2E.1.3.2.4.2 Test procedure + +1. The SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the NR UL RMC according to Table 6.2E.1.3.2.4.1-1 on NR CC. The UE starts to perform the E-UTRA V2X sidelink communication according to SL-V2X-Preconfiguration. Since the UL has no payload and no loopback data to send, the UE transmits uplink MAC padding bits on the NR UL and E-UTRA V2X sidelink RMC. +2. Send continuously uplink power control "up" commands to the UE until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command starting in this step for the UE to reach $P_{UMAX}$ level. +3. Measure the mean power over all component carriers in the inter-band con-current V2X configuration. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). For TDD slots with transient periods are not under test. + +###### 6.2E.1.3.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1 for NR Uu carrier and TS 36.508 [11] clause 4.6 for E-UTRA V2X sidelink carrier with the following exceptions: + +FFS + +###### 6.2E.1.3.2.5 Test requirement + +FFS + +### 6.2E.2 UE maximum output power reduction for V2X + +#### 6.2E.2.0 Minimum conformance requirements + +##### 6.2E.2.0.1 UE maximum output power reduction for Intra-band V2X + +For intra-band V2X operating UE, maximum output power reduction specified in clause 6.2.3G [5] and in clause 6.2E.2 [2] apply, respectively. + +##### 6.2E.2.0.2 UE maximum output power reduction for Inter-band V2X + +For the inter-band concurrent NR V2X operation, the allowed maximum power reduction (MPR) for the maximum output power shall be applied per each component carrier. The MPR requirements in subclause 6.2.3 of TS 36.101 [5] apply for E-UTRA Uu operation in licensed band, and the MPR requirements in subclause 6.2E.2 of TS 38.101-1 [2] apply for NR sidelink operation. The MPR requirements in subclause 6.2.3G of TS 36.101 [5] apply for E-UTRA V2X operation, and the MPR requirements in subclause 6.2.2 of TS 38.101-1 [2] apply for NR Uu operation. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.2E.2. + +#### 6.2E.2.1 UE maximum output power reduction for Intra-band V2X + +##### 6.2E.2.1.1 Test purpose + +To verify that the backoff of UE's transmit power doesn't exceed the range prescribed by the specified MPR value and tolerance specified in clause of configured output power. + +##### 6.2E.2.1.2 Test applicability + +This test applies to all types of UE release 16 and forward, supporting E-UTRA-NR intra-band contiguous V2X configuration or E-UTRA-NR intra-band non-contiguous V2X configuration. + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.2E.1.1 and 6.2E.1.2. The requirements in this test case can be well covered in clause 6.2.3G of TS 36.521-1 [10] and clause 6.2E.2 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.2E.2.2 UE maximum output power reduction for Inter-band V2X + +##### 6.2E.2.2.1 UE maximum output power reduction for Inter-band V2X with E-UTRA Uu and NR Sidelink + +**Editor's note:** + +- Connection diagram is FFS +- Generic test procedure is FFS +- Message exception is FFS +- Test requirements are FFS + +###### 6.2E.2.2.1.1 Test purpose + +Same test purpose as in clause 6.2E.2.1.1 in TS 38.521-1 [8]. + +###### 6.2E.2.2.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 16 and forward supporting concurrent operation between E-UTRA Uu and NR sidelink. + +##### 6.2E.2.2.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2E.2.0.2. + +###### 6.2E.2.2.1.4 Test description + +###### 6.2E.2.2.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and test channel bandwidths based on NR operating bands specified in clause 5.3E.3, channel bandwidths and sub-carrier spacings for the NR sidelink carrier specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each E-UTRA-NR V2X band combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.2E.2.2.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexes A.2 of TS 36.521-1 [10] for E-UTRA Uu carrier. The details of sidelink reference measurement channels (RMCs) are specified in A.7 of TS 38.521-1 [8] for NR V2X carrier. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521.1 [10] Annex C.2 for E-UTRA Uu carrier. + +**Table 6.2E.2.2.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------|--------------------|---------------------|----------------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1. | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 36.508 [11] subclause 4.3.1 for E-UTRA carrier and TS 38.508-1 [6] clause 4.3.1 for NR carrier. | Low range for E-UTRA Uu carrier and NR sidelink carrier
High range for E-UTRA Uu carrier and NR sidelink carrier | | | | | +| Test inter-band V2X bandwidth combination as specified in clause 5.3E.3. | Lowest for E-UTRA Uu carrier and NR sidelink carrier
Highest for E-UTRA Uu carrier and NR sidelink carrier | | | | | +| Test SCS for the NR carrier as specified in TS 38.521-1 [8] Table 5.3.5-1. | 15kHz | | | | | +| Test Parameters | | | | | | +| Test ID | E-UTRA Uu carrier | | | NR sidelink Carrier | | +| | Downlink Configuration | Uplink Configuration | | Modulation | PSCCH and PSSCH RB allocation (Note 2) | +| Modulation | | RB allocation (Note 1) | | | | +| 1 | N/A | QPSK | Partial Allocation | CP-OFDM 16QAM | Inner_Full | +| 2 | | QPSK | Full Allocation | CP-OFDM 16QAM | Outer_Full | +| 3 | | 16QAM | Partial Allocation | CP-OFDM 64QAM | Outer_Full | +| 4 | | 16QAM | Full Allocation | CP-OFDM 256QAM | Outer_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1E-1 in TS 38.521-1 [8]. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, FFS for TE diagram and clause FFS for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The parameter settings for the V2X sidelink transmission over PC5 are pre-configured according to TS 38.508-1 [5] clause 4.10. Message content exceptions are defined in clause 6.2E.1.1.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0, and uplink signals according to TS 36.521-1 [10] Annex H for the E-UTRA cell. +4. The E-UTRA UL Reference Measurement channels and the V2X Reference Measurement Channel are set according to Table 6.2E.2.2.1.4.1-1. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in State FFS according to TS 36.508 [7] clause FFS. Message content exceptions are defined in clause 6.2E.2.2.1.4.3. + +###### 6.2E.2.2.1.4.2 Test procedure + +1. The SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the E-UTRA UL RMC according to Table 6.2E.2.2.1.4.1-1. The UE starts to perform the NR sidelink communication according to *SL-PreconfigurationNR*. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the E-UTRA UL and NR sidelink RMCs. +2. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE to ensure that the UE transmits at PUMAX level. Configure the UE to transmit PSCCH and PSSCH with the PUMAX level of each test points. +3. Measure the mean power over all component carriers in the inter-band concurrent V2X configuration. The period of measurement shall be at least continuous duration of one sub-frame (1ms). + +###### 6.2E.2.2.1.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6 for E-UTRA Uu carrier and TS 38.508-1 [6] clause 4.6.3 for NR sidelink carrier with the following exceptions: + +FFS + +##### 6.2E.2.2.1.5 Test requirement + +FFS + +#### 6.2E.2.2.2 UE maximum output power reduction for Inter-band V2X with NR Uu and E-UTRA V2X + +**Editor's note:** + +- Connection diagram is FFS +- Generic test procedure is FFS +- Message exception is FFS +- Test requirements are FFS + +##### 6.2E.2.2.2.1 Test purpose + +Same test purpose as in clause 6.2E.2.1.1 in TS 38.521-1 [8]. + +##### 6.2E.2.2.2.2 Test applicability + +This test applies to all types of NR UE release 16 and forward supporting concurrent operation between NR Uu and E-UTRA V2X. + +##### 6.2E.2.2.2.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 6.2E.2.0.2. + +##### 6.2E.2.2.2.4 Test description + +###### 6.2E.2.2.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and test channel bandwidths based on NR operating bands specified in clause 5.3E.3, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA V2X carrier are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each E-UTRA-NR V2X band combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.2E.2.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2 of TS 38.521-1 [8] for NR Uu carrier. The details of sidelink reference measurement channels (RMCs) are specified in Annex A.6 of TS 36.521-1 [10] for E-UTRA V2X carrier. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [8] Annex C.2 for NR Uu carrier. + +**Table 6.2E.2.2.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------|---------------------------|----------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1. | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 36.508 [11] subclause 4.3.1 for E-UTRA carrier and TS 38.508-1 [6] clause 4.3.1 for NR carrier. | Low range for NR Uu carrier and E-UTRA sidelink carrier
High range for NR Uu carrier and E-UTRA sidelink carrier | | | | | +| Test inter-band V2X bandwidth combination as specified in clause 5.3E.3. | Lowest for NR Uu carrier and E-UTRA sidelink carrier
Highest for NR Uu carrier and E-UTRA sidelink carrier | | | | | +| Test SCS for the NR carrier as specified in TS 38.521-1 [8] Table 5.3.5-1. | 15kHz | | | | | +| Test Parameters | | | | | | +| Test ID | NR Uu Carrier | | | E-UTRA V2X Carrier | | +| | Downlink Configuration | Uplink Configuration | | Modulation | PSSCH RB allocation | +| | | Modulation | RB allocation (Note 1) | | | + +| | | | | | | +|---------------------------------------------------------------------------------------------------------|-----|-------------------|------------|-------|----------------------------------------| +| 1 | N/A | DFT-s-OFDM QPSK | Inner_Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 2 | | DFT-s-OFDM QPSK | Outer_Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 3 | | DFT-s-OFDM 16QAM | Inner_Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 4 | | DFT-s-OFDM 16QAM | Outer_Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 5 | | DFT-s-OFDM 64QAM | Outer_Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 6 | | DFT-s-OFDM 256QAM | Outer_Full | QPSK | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 7 | | CP-OFDM QPSK | Inner_Full | 16QAM | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 8 | | CP-OFDM 16PSK | Inner_Full | 16QAM | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 9 | | CP-OFDM 16PSK | Outer_Full | 16QAM | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 10 | | CP-OFDM 64PSK | Outer_Full | 16QAM | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| 11 | | CP-OFDM 256PSK | Outer_Full | 16QAM | 48@2 for 10MHz BW
96@2 for 20MHz BW | +| NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1E-1 in TS 38.521-1 [8]. | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, FFS for TE diagram and clause FFS for UE diagram. +2. The parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. The parameter settings for the E-UTRA V2X sidelink transmission are pre-configured according to TS 38.508-1 [5] subclause 4.10. Message content exceptions are defined in clause 6.2E.1.1.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [8] Annex C.0, and uplink signals according to TS 38.521-1 [8] Annex G for the NR cell. +4. The NR UL Reference Measurement channels and the E-UTRA V2X Reference Measurement Channel are set according to Table 6.2E.2.2.2.4.1-1. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +8. Ensure the UE is in state FFS according to TS 38.508-1 [6] clause FFS. Message contents are defined in clause 6.2E.2.2.2.4.3. + +###### 6.2E.2.2.2.4.2 Test procedure + +1. The SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the NR UL RMC according to Table 6.2E.2.2.2.4.1-1 on NR CC. The UE starts to perform the E-UTRA V2X sidelink communication according to SL-V2X-Preconfiguration. Since the UL has no payload and no loopback data to send, the UE transmits uplink MAC padding bits on the NR UL and E-UTRA V2X sidelink RMC. +2. Send continuously uplink power control "up" commands to the UE until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command starting in this step for the UE to reach $P_{UMAX}$ level. +3. Measure the mean power over all component carriers in the inter-band concurrent V2X configuration. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). For TDD slots with transient periods are not under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.2E.2.2.2.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.2E.2.2.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1 for NR Uu carrier and TS 36.508 [11] clause 4.6 for E-UTRA V2X sidelink carrier with the following exceptions: + +FFS + +###### 6.2E.2.2.2.5 Test requirement + +FFS + +## 6.3 Output power dynamics + +## 6.3A Output Power Dynamics for CA without EN-DC + +### 6.3A.1 UE Output Power Dynamics for CA + +#### 6.3A.1.1 UE Output Power Dynamics for NR CA between FR 1 and FR 2 without EN-DC + +##### 6.3A.1.1.1 Test purpose + +Same test purpose as in clause 6.3 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.3 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.3A.1.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for maximum output power apply and are tested in TS 38.521-1 [8] clauses 6.3 and 6.2A and TS 38.521-2 [9] clauses 6.3 and 6.3A. + +## 6.3B Output power dynamics for DC + +### 6.3B.1 Minimum Output Power for EN-DC + +#### 6.3B.1.1 Minimum Output Power for intra-band contiguous EN-DC + +##### 6.3B.1.1.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.1.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.3B.1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-1 [8] for the NR carrier. + +Same minimum conformance requirements as in clause 6.3.2.3 in TS 36.521-1 [10] for E-UTRA carrier. + +For intra-band contiguous EN-DC operation in FR1, minimum output power requirements specified in clause 6.3.1 of TS 38.101-1 [2] and clause 6.3.2 of TS 36.101 [5] shall only apply when the power of all NR and E-UTRA carriers are set to minimum value. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.1.1.4 Test description + +Same test descriptions as in clause 6.3.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 6.3B.1.1.4-1: Test configuration table** + +| E-UTRA Test Parameters | | | | | +|----------------------------------------------------------------------------|-----------------------|-------------------------------|------------|---------------| +| E-UTRA Channel Bandwidth | E-UTRA Test Frequency | Downlink | Uplink | | +| | | N/A for min output power test | Modulation | RB allocation | +| 5 MHz | MidRange | | QPSK | 25 | +| NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [11] clause 4.3.1. | | | | | + +For Initial conditions as in clause 6.3.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 6.3B.1.1.4-1. +- 3.1. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0. +- 4.1. The UL Reference Measurement channels are set according to Table 6.3B.1.1.4-1. + +Step 6 of Initial conditions as in clause 6.3.1.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.3.1.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1. For E-UTRA component, SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to table 6.3B.1.1.4-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +- 2.1. For E-UTRA component, send continuously uplink power control "down" commands in every uplink scheduling information to the UE. + +##### 6.3B.1.1.5 Test requirements + +Same test requirement as in clause 6.3.1.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.1.2 Minimum output power for intra-band non-contiguous EN-DC + +##### 6.3B.1.2.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.1.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.3B.1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-1 [2] clause 6.3. + +##### 6.3B.1.2.4 Test description + +Same test descriptions as in clause 6.3.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 6.3B.1.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Low with maxWGap, High with maxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the lowest N RB_SCG and highest N RB_SCG are tested for Lowest N RB_agg , and Highest N RB_agg , respectively. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 6.3B.1.2.4-1. + +For Initial conditions as in clause 6.3.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 6.3B.1.2.4-1. +- 3.1. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C, clauses C.0, C.1 and C.3.0, and uplink signals according to Annex H, clauses H.1 and H.3.0. +- 4.1. The UL Reference Measurement channels are set according to Table 6.3B.1.2.4-1. + +Step 6 of Initial conditions as in clause 6.3.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +##### 6.3B.1.2.5 Test requirements + +Same test requirement as in clause 6.3.1.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.1.3 Minimum output power for inter-band EN-DC within FR1 (1 NR CC) + +##### 6.3B.1.3.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +##### 6.3B.1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.1.3.4 Test description + +Same test descriptions as in clause 6.3.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + - 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +- Step 6 of Initial conditions as in clause 6.3.1.4.1 in TS 38.521-1 [8] is replaced by the following two steps: +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. + 7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 6.3B.1.3.5 Test requirements + +Same test requirement as in clause 6.3.1.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.1.4 Minimum Output Power for EN-DC Interband including FR2 (1 NR CC) + +**Editor's note: The following aspects of the clause are for future consideration:** + +- Testing of extreme conditions for FR2 is FFS. +- Measurement Uncertainties and Test Tolerances are FFS for power class 2 and 4. + +##### 6.3B.1.4.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.3B.1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B.1. + +##### 6.3B.1.4.4 Test description + +Same test description as in clause 6.3.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.3.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of initial conditions as in clause 6.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.1.4.5 Test requirements + +Same test requirement as in clause 6.3.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +#### 6.3B.1.4\_1 Minimum output power for inter-band EN-DC including FR2 (>1 NR CC) + +##### 6.3B.1.4\_1.1 Minimum output power for inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.3A.1.1 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. + +###### 6.3B.1.4\_1.1.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.3B.1.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.3B.1.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.1.4 Test description + +###### 6.3B.1.4\_1.1.4.1 Initial condition + +Same test description as in clause 6.3A.1.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.1.5 Test Requirements + +Same test requirement as in clause 6.3A.1.1.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.2 Minimum output power for inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.3A.1.2 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. + +###### 6.3B.1.4\_1.2.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.3B.1.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.2.4 Test description + +###### 6.3B.1.4\_1.2.4.1 Initial condition + +Same test description as in clause 6.3A.1.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.2.5 Test Requirements + +Same test requirement as in clause 6.3A.1.2.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.3 Minimum output power for inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.3A.1.3 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. + +###### 6.3B.1.4\_1.3.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.3B.1.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.3.4 Test description + +###### 6.3B.1.4\_1.3.4.1 Initial condition + +Same test description as in clause 6.3A.1.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.3.5 Test Requirements + +Same test requirement as in clause 6.3A.1.3.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.4 Minimum output power for inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.3A.1.3 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.3B.1.4\_1.4.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.3B.1.4\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.4.4 Test description + +###### 6.3B.1.4\_1.4.4.1 Initial condition + +Same test description as in clause 6.3A.1.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.4.5 Test Requirements + +Same test requirement as in clause 6.3A.1.4.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.5 Minimum output power for inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.3A.1.3 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.3B.1.4\_1.5.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.3B.1.4\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.5.4 Test description + +###### 6.3B.1.4\_1.5.4.1 Initial condition + +Same test description as in clause 6.3A.1.5.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.5.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.5.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.5.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.5.5 Test Requirements + +Same test requirement as in clause 6.3A.1.5.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.6 Minimum output power for inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.3A.1.3 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.3B.1.4\_1.6.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.3B.1.4\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.6.4 Test description + +###### 6.3B.1.4\_1.6.4.1 Initial condition + +Same test description as in clause 6.3A.1.6.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.6.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.6.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.6.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.6.5 Test Requirements + +Same test requirement as in clause 6.3A.1.6.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.1.4\_1.7 Minimum output power for inter-band EN-DC including FR2 (8 NR CCs) + +Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.3A.1.3 in TS 38.521-2 [9] is incomplete for NR aggregated channel bandwidth wider than 400MHz and power classes 1, 2, 4. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.3B.1.4\_1.7.1 Test purpose + +Same test purpose as in clause 6.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.3B.1.4\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.3B.1.4\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.1.4\_1.7.4 Test description + +###### 6.3B.1.4\_1.7.4.1 Initial condition + +Same test description as in clause 6.3A.1.7.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.1.7.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.1.7.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.1.7.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.1.4\_1.7.5 Test Requirements + +Same test requirement as in clause 6.3A.1.7.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.3B.1.4D Minimum output power for inter-band EN-DC including FR2 for UL MIMO + +##### 6.3B.1.4D.1 Test purpose + +Same test purpose as in clause 6.3D.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.1.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2. + +##### 6.3B.1.4D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3D.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.3B. + +##### 6.3B.1.4D.4 Test Description + +Same test description as in clause 6.3D.1.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.3D.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3D.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. + +Same Test procedure as in clause 6.3D.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.1.4D.5 Test Requirement + +Same test requirement as specified in clause 6.3D.1.5 of TS 38.521-2 [9] for the NR carrier(s). + +### 6.3B.2 Transmit OFF Power for EN-DC + +#### 6.3B.2.1 Transmit OFF Power for intra-band contiguous EN-DC + +##### 6.3B.2.1.1 Test purpose + +Same test purpose as in clause 6.3.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.2.1.2 Test applicability + +The requirements of this test apply in Clause 6.3B.3 Tx ON/OFF time mask/PUCCH time mask to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.3B.2.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.2.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.2.1.4 Test description + +This test is covered by Clause 6.3B.3 Tx ON/OFF time mask/PUCCH time mask for EN-DC. + +##### 6.3B.2.1.5 Test requirements + +Same test requirement as in clause 6.3.2.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.2.2 Transmit OFF Power for intra-band non-contiguous EN-DC + +##### 6.3B.2.2.1 Test purpose + +Same test purpose as in clause 6.3.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.2.2.2 Test applicability + +The requirements of this test apply in clause 6.3B.3 Tx ON/OFF time mask/PUCCH time mask to all types of E-UTRA UE Release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.3B.2.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.2.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.2.2.4 Test description + +This test is covered by Clause 6.3B.3 Tx ON/OFF time mask/PUCCH time mask for EN-DC. + +##### 6.3B.2.2.5 Test requirements + +Same test requirement as in clause 6.3.2.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.2.3 Transmit OFF Power for inter-band EN-DC within FR1 (1 NR CC) + +##### 6.3B.2.3.1 Test purpose + +Same test purpose as in clause 6.3.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.2.3.2 Test applicability + +The requirements of this test apply in Clause 6.3B.3 Tx ON/OFF time mask/PUCCH time mask to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +##### 6.3B.2.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.2.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.2.3.4 Test description + +This test is covered by Clause 6.3B.3 Tx ON/OFF time mask/PUCCH time mask for EN-DC. + +##### 6.3B.2.3.5 Test requirements + +Same test requirement as in clause 6.3.2.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.2.4 Transmit OFF Power for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note:** This test case is complete for Band n257. Following aspects are either missing or not yet determined: + +- The referred test case 6.3.2 in TS 38.521-2 [9] is incomplete for other than band n257. +- Measurement Uncertainties and Test Tolerances are FFS for power class 1 FR2b, 2 and 4. + +##### 6.3B.2.4.1 Test purpose + +Same test purpose as in clause 6.3.2.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.2.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.3B.2.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.2.4.4 Test description + +Same test description as in clause 6.3.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.2.4.5 Test requirements + +Same test requirement as in clause 6.3.2.5 in TS 38.521-2 [8] for the NR carrier. + +##### 6.3B.2.4\_1 Void + +#### 6.3B.2.4D Transmit OFF Power for inter-band EN-DC including FR2 for UL-MIMO + +##### 6.3B.2.4D.1 Test purpose + +Same test purpose as in clause 6.3D.2.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.2.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 for UL-MIMO. + +##### 6.3B.2.4D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3D.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.3B. + +##### 6.3B.2.4D.4 Test Description + +Same test description as in clause 6.3D.2.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.3D.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3D.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. + +Same Test procedure as in clause 6.3D.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.2.4D.5 Test Requirement + +Same test requirement as specified in clause 6.3D.2.5 of TS 38.521-2 [9] for the NR carrier(s). + +### 6.3B.3 Transmit ON/OFF time mask/PUCCH time mask for EN-DC + +#### 6.3B.3.1 Transmit ON/OFF time mask for intra-band contiguous EN-DC + +##### 6.3B.3.1.1 Test purpose + +Same test purpose as in clause 6.3.3.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.3.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.3B.3.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.2.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.3.1.4 Test description + +Same test descriptions as in clause 6.3.3.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA Downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, *Connected without release On* according to TS 38.508-1 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.3.3.2.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 6.3B.3.1.5 Test requirements + +Same test requirement as in clause 6.3.3.2.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.3.2 Transmit ON/OFF time mask for intra-band non-contiguous EN-DC + +##### 6.3B.3.2.1 Test purpose + +Same test purpose as in clause 6.3.3.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.3.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.3B.3.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.2.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.3.2.4 Test description + +Same test descriptions as in clause 6.3.3.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA Downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, *Connected without release On* according to TS 38.508-1 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.3.3.2.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 6.3B.3.2.5 Test requirements + +Same test requirement as in clause 6.3.3.2.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.3.3 Transmit ON/OFF time mask for inter-band EN-DC within FR1 (1 NR CC) + +##### 6.3B.3.3.1 Test purpose + +Same test purpose as in clause 6.3.3.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.3.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +##### 6.3B.3.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.2.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +##### 6.3B.3.3.4 Test description + +Same test descriptions as in clause 6.3.3.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA Downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, *Connected without release* *On* according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3.3.2.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 6.3B.3.3.5 Test requirements + +Same test requirement as in clause 6.3.3.2.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.3B.3.4 Transmit ON/OFF time mask for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.3.3.2 in TS 38.521-2 [9] is incomplete for power class 1, 2 and 4. +- The referred test case 6.3.3.2 in TS 38.521-2 [9] is incomplete for band n259. + +##### 6.3B.3.4.1 Test purpose + +Same test purpose as in clause 6.3.3.2.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.3.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2 with 1 NR UL CC. + +##### 6.3B.3.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.3B. + +##### 6.3B.3.4.4 Test Description + +Same test description as in clause 6.3.3.2.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.3.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, *Connected without release* *On* according to TS 38.508-1 [6] clause 4.5. + +Same Test procedure as in clause 6.3.3.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.3.4.5 Test Requirement + +Same test requirement as specified in clause 6.3.3.2.5 of TS 38.521-2 [9] for the NR carrier(s). + +#### 6.3B.3.4\_1 Transmit ON/OFF time mask for Inter-Band EN-DC including FR2 (>1 NR CC) + +##### 6.3B.3.4\_1.1 Transmit ON/OFF time mask for Inter-Band EN-DC including FR2 (2 NR CCs) + +Editor's note: This test case is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.3A.3.1.1 in TS 38.521-2 is incomplete on test requirements. +- Measurement Uncertainty and Test Tolerances are FFS. +- The method of setting UE transmitted power is FFS. +- TP analysis is FFS. +- Applicability of Beam peak of single UL is FFS. +- The UPLF test mode is applicable to UEs Release 16 and forward. This test case is incomplete for Release 15 until UE PHR method is used to prevent SCell drop. + +###### 6.3B.3.4\_1.1.1 Test purpose + +Same test purpose as in clause 6.3A.3.1.1.1 in TS 38.521-2 [9] for the NR carriers. + +###### 6.3B.3.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.3B.3.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3A.3.1.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.3B. + +###### 6.3B.3.4\_1.1.4 Test description + +Same test description as in clause 6.3A.3.1.1.4 in TS 38.521-2 [9] for the NR carriers with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.3A.3.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3A.3.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3A.3.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7 of TS 36.508 [11]. + +###### 6.3B.3.4\_1.1.5 Test Requirements + +Same test requirement as in clause 6.3A.3.1.1.5 in TS 38.521-2 [9] for the *NR* carriers. + +#### 6.3B.3.4D Transmit ON/OFF time mask for inter-band EN-DC including FR2 for UL-MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.3D.3 in TS 38.521-2 [9] is incomplete + +##### 6.3B.3.4D.1 Test purpose + +Same test purpose as in clause 6.3D.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.3.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2. + +##### 6.3B.3.4D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3D.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.3B. + +##### 6.3B.3.4D.4 Test Description + +Same test description as in clause 6.3D.3.1.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.3D.3.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3D.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. + +Same Test procedure as in clause 6.3D.3.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.3.4D.5 Test Requirement + +Same test requirement as specified in TS 38.521-2 [9] clause 6.3D.3.1.5 for the NR carrier(s). + +### 6.3B.3\_1 E-UTRA and NR switching time mask for switching between two uplink carriers + +#### 6.3B.3\_1.1 E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC + +Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- The test clause number needs further discussion. + +##### 6.3B.3\_1.1.1 Test purpose + +To verify that the E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC meets the requirements given in 6.3B.4.1 in TS 38.101-3 [4]. + +The E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC defines the transient period(s) and the switching period allowed between two uplink carriers for an uplink band pair of an inter-band EN-DC configuration when the capability *uplinkTxSwitchingPeriod* is present. + +##### 6.3B.3\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 16 and forward, supporting 2UL inter-band EN-DC and dynamic UL Tx switching. + +##### 6.3B.3\_1.1.3 Minimum conformance requirements + +In addition to the requirements in 6.3B.0 and the maximum output power requirement specified in Table 6.2B.1.3-1 with inter-band EN-DC (two bands), the switching time mask specified in this sub-clause is applicable for an uplink band pair of an inter-band EN-DC configuration without SUL band when the capability *uplinkTxSwitchingPeriod* is present, and is only applicable for uplink switching mechanisms specified in sub-clause 6.1.6 of TS 38.214 [14], where E-UTRA UL carrier 1 is capable of one transmit antenna connector and NR UL carrier 2 is capable of two transmit antenna connectors, and the two uplink carriers are in different bands with different carrier frequencies. The UE shall support the switch between single layer transmission with one antenna port and two-layer transmission with two antenna ports on the two uplink carriers following the scheduling commands and rank adaptation, i.e., both single layer and two-layer transmission with 2 antenna ports, and single layer transmission with 1 antenna port shall be supported on NR UL carrier 2. + +The switching periods described in Figure 6.3B.4.1-1 are only located in NR carrier, and the length of uplink switching period *X* is less than the value indicated by UE capability *uplinkTxSwitchingPeriod*. + +![Timing diagram showing E-UTRA subframes and NR Slot/subslots with switching periods and transient periods.](88a6d9692a52989caa6b208a1ba70dc0_img.jpg) + +The diagram illustrates the timing for switching between E-UTRA and NR uplink carriers. It shows a sequence of three main blocks: an E-UTRA subframe, an NR Slot/subslot, and another E-UTRA subframe. The NR Slot/subslot is divided into two segments, each containing an 'ON power requirement' period. Between these segments, there is a 'Switching period, X μs'. Transient periods are indicated by double-headed arrows: a '20 μs transient period' at the boundary between the first E-UTRA subframe and the NR Slot/subslot, a '10 μs transient period' between the two ON power requirement segments within the NR Slot/subslot, and another '20 μs transient period' at the boundary between the NR Slot/subslot and the second E-UTRA subframe. Vertical dashed lines mark the boundaries between these periods and segments. + +Timing diagram showing E-UTRA subframes and NR Slot/subslots with switching periods and transient periods. + +**Figure 6.3B.4.1-1: Time mask for switching between E-UTRA UL carrier and NR UL carrier, where the switching period is located in NR carrier** + +The requirements apply for the case of co-located and synchronized network deployment with the max receiving timing difference of 3us between the two carriers. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3B.4.1 for the NR and the E-UTRA carrier. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. + +###### 6.3B.3\_1.1.4 Test description + +###### 6.3B.3\_1.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2, and are shown in table 6.3B.3\_1.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C, clause C.2 and in TS 38.521-1 [8] Annex C, clause C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.3B.3\_1.1.4.1-1: Test configuration table for Inter-band EN-DC Uplink switching** + +| | | Initial Conditions | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|----------------------------------------------|-------------------------------|--------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [5] clause 4.1 | | Normal | | | | +| NR Test Frequencies as specified in TS 38.508-1 [5] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508-1 [11] clause 4.3.1 | | Mid range for E-UTRA CC1 and NR CC1 (NOTE 3) | | | | +| Test EN-DC bandwidth combination as specified in TS 38.508-1 [5] clause 4.3.1 | | Highest for E-UTRA CC1 and NR CC1 | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | | Highest | | | | +| NR/E-UTRA Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | +| 1 | N/A | QPSK | Outer Full | DFT-s-OFDM
QPSK | Inner Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +NOTE 2: The specific configuration of each RB allocation is defined in Table 6.1-1 in current specification. +NOTE 3: For NR band n28, 30MHz test channel bandwidth is tested with Low range test frequency. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.2 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. + +4. NR downlink signals are initially set up according to Annex C.0, C.1, and C.2 and uplink signals according to Annex G.0, G.1, G.2, and G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement Channel is set according to Table 6.3A.3.1\_1.4.1-1 for E-UTRA CG and NR CG respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.3A.3.1\_1.4.3 in TS 38.521-1 [8] for the NR CG. + +###### 6.3B.3\_1.1.4.2 Test procedure + +Carrier 1 and Carrier 2 refers to the E-UTRA component and the NR carrier respectively + +1. Configure Carrier 2 according to Annex C.0, C.1, C.2 for all downlink physical channels. +2. The SS shall configure Carrier 2 as per TS 38.508-1 [5] clause 5.5.1. Message contents are defined in clause 6.3A.3.1\_1.4.3 in TS 38.521-1 [8] for the NR Carrier 2. +3. For Carrier 1, SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.3B.3\_1.1.4.1-1 on E-UTRA subframe n-1, where E-UTRA subframe n is an uplink slot for Carrier 2 and $n-1 \geq 20$ when SCS=15 kHz ( $n-1 \geq 40$ when SCS=30 kHz, $n-1 \geq 80$ when SCS=60 kHz). Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +4. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200ms starting from the first TPC command in this step for the UE to reach $P_{UMAX}$ level. +5. The SS sends uplink scheduling information via DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.3B.3\_1.1.4.1-1 on Carrier 2 on slot n ( $n \geq 1$ ) and slot m, with both slot n and slot m being uplink slots for Carrier 2 and $m \geq n+20$ when SCS=15kHz ( $m \geq n+40$ when SCS=30 kHz, $m \geq n+80$ when SCS=60 kHz). Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. The PDCCH DCI format 0\_1 is specified with the condition 2TX\_UL\_MIMO in TS 38.508-1 [5] subclause 4.3.6.1.1.2. +6. Measure the output power of UE PUSCH transmission for Carrier 1 during the E-UTRA subframe n-1, for Carrier 1 excluding a transient period of 20 $\mu$ s in the end of the E-UTRA subframe n-1. +7. Measure the sum of output power of UE PUSCH transmission on Carrier 2 over all antenna connectors during slot n and slot m excluding a switching period X and a transient period of 10 $\mu$ s in the beginning of slot n and in the end of slot m. The length of uplink switching period X is indicated by UE capability *uplinkTxSwitchingPeriod*. +8. For Carrier 1, SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.3B.3\_1.1.4.1-1 on E-UTRA subframe m+1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +9. Measure the output power of UE PUSCH transmission for Carrier 1 during slot m+1 excluding a transient period of 20 $\mu$ s in the beginning of slot m+1. + +##### 6.3B.3\_1.1.5 Test requirements + +The requirements for the power of Carrier 1 measured in step 6, step 9 of the test procedure, and the power of Carrier 2 measured in step 7 shall not exceed the values specified in Table 6.3B.3\_1.1.5-1 and Table 6.3B.3\_1.1.5-2, respectively. + +**Table 6.3B.3\_1.1.5-1: E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC (On power on the E-UTRA Carrier)** + +| | Measured output power | +|-------------------|--------------------------------------------------------------------------------------------------------------| +| Transmit ON power | For each E-UTRA band tested, same as the requirements in Table 6.2.3.5-1 of TS 36.521-1 [10] as appropriate. | + +**Table 6.3B.3\_1.1.5-2: E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC (On power on the NR Carrier)** + +| | Measured output power | +|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Transmit ON power | For each NR band tested, same as Test ID 9 in Table 6.2.2.5-1 to Table 6.2.2.5-3 of TS 38.521-1 [8] as appropriate | +| NOTE1: TT or each frequency and channel bandwidth of Transmit ON power is specified in Table 6.2.2.5-5 of TS 38.521-1 [8] | | + +### 6.3B.4 PRACH time mask for EN-DC + +#### 6.3B.4.1 PRACH time mask for intra-band contiguous EN-DC + +##### 6.3B.4.1.1 Test purpose + +Same test purpose as in clause 6.3.3.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.4.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.3B.4.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.4.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.3B.4.1.4 Test description + +Same test description as in clause 6.3.3.4.4 in TS 38.521-1 [8] with the following exception: + +**Table 6.3B.4.1.4-1: Test Configuration Table** + +| Initial Conditions | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different DC bandwidth classes. | Mid range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest NRB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg , only the combination with the highest NRB_SCG is tested | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 6.3B.4.1.4-1. + +For Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 5 of Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +5. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +6. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +For Message contents as in clause 6.3.3.4.4.3 in TS 38.521-1 [8], the following exception: + +**Table 6.3B.4.1.4-2: RACH-ConfigGeneric: PRACH measurement** + +| Derivation Path: TS 38.508-1[5], Table 4.6.3-130 | | | | +|--------------------------------------------------|--------------|-------------------|-----------------| +| Information Element | Value/remark | Comment | Condition | +| RACH-ConfigGeneric ::= SEQUENCE { | | | | +| prach-ConfigurationIndex | 14 | Unpaired Spectrum | PRACH Format 0 | +| | 128 | Unpaired Spectrum | PRACH Format A3 | + +##### 6.3B.4.1.5 Test requirements + +Same test requirement as in clause 6.3.3.4.5 in TS 38.521-1 [8]. + +#### 6.3B.4.2 PRACH Time Mask for intra-band non-contiguous EN-DC + +##### 6.3B.4.2.1 Test purpose + +Same test purpose as in clause 6.3.3.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.4.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.3B.4.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.4.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.3B.4.2.4 Test description + +Same test description as in clause 6.3.3.4.4 in TS 38.521-1 [8] with the following exception: + +**Table 6.3B.4.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Test Frequencies as specified in TS 36TS 38.508-1 [76] clause 4.3.1 for different EN-DC bandwidth classes | MaxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1 across bandwidth combination sets supported by the UE | Highest NRB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg , only the combination with the highest NRB_SCG is tested | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 6.3B.4.2.4-1. + +For Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 5 of Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +5. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +6. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +For Message contents as in clause 6.3.3.4.4.3 in TS 38.521-1 [8], the following exception: + +**Table 6.3B.4.2.4-2: RACH-ConfigGeneric: PRACH measurement** + +| Derivation Path: TS 38.508-1[5], Table 4.6.3-130 | | | | +|--------------------------------------------------|--------------|-------------------|-----------------| +| Information Element | Value/remark | Comment | Condition | +| RACH-ConfigGeneric ::= SEQUENCE { | | | | +| prach-ConfigurationIndex | 14 | Unpaired Spectrum | PRACH Format 0 | +| | 128 | Unpaired Spectrum | PRACH Format A3 | + +##### 6.3B.4.2.5 Test requirements + +Same test requirement as in clause 6.3.3.4.5 in TS 38.521-1 [8]. + +#### 6.3B.4.3 PRACH Time Mask for inter-band EN-DC within FR1 (1 NR CC) + +##### 6.3B.4.3.1 Test purpose + +Same test purpose as in clause 6.3.3.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.4.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +##### 6.3B.4.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.4.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.3B.4.3.4 Test description + +Same test description as in clause 6.3.3.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 5 of Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +5. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +6. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Same test requirement as in clause 6.3.3.4.5 in TS 38.521-1 [8]. + +#### 6.3B.4.4 PRACH Time Mask for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.3.3.4 in TS 38.521-2 [9] is incomplete + +##### 6.3B.4.4.1 Test purpose + +Same test purpose as in clause 6.3.3.4.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.3B.4.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 . + +##### 6.3B.4.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.3.4.3 in TS 38.521-2 [9] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +##### 6.3B.4.4.4 Test description + +Same test description as in clause 6.3.3.4.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 5 of Initial conditions as in clause 6.3.3.4.4.1 in TS 38.521-2 [9] is replaced by the following two steps: + +5. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +6. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.3B.4.4.5 Test requirement + +Same test requirement as specified in clause 6.3.3.4.5 of TS 38.521-2 [9] for the NR carrier(s). + +### 6.3B.5 Output power dynamics for EN-DC with UL sharing from UE perspective + +#### 6.3B.5.1 E-UTRA and NR switching time mask for TDM based UL sharing from UE perspective + +No test case details are specified. Current test procedures for time masks are based on power measurement in relatively long period compared with transient period. For time masks between 2 active time slots with different power level, the test procedure can't provide enough resolution to identify non-conformant UEs. Therefore the minimum requirement is not testable. + +### 6.3B.6 Output power dynamics for intra-band EN-DC without dual PA capability + +No test case details are specified. Current test procedures for time masks are based on power measurement in relatively long period compared with transient period. For time masks between 2 active time slots with different power level, the test procedure can't provide enough resolution to identify non-conformant UEs. Therefore the minimum requirement is not testable. + +### 6.3B.7 Output power dynamics for intra-band EN-DC with dual PA capability + +No test case details are specified. Current test procedures for time masks are based on power measurement in relatively long period compared with transient period. For time masks between 2 active time slots with different power level, the test procedure can't provide enough resolution to identify non-conformant UEs. Therefore the minimum requirement is not testable. + +### 6.3B.8 Power control for EN-DC + +#### 6.3B.8.1 Absolute power tolerance for EN-DC + +##### 6.3B.8.1.1 Absolute power tolerance for intra-band contiguous EN-DC + +###### 6.3B.8.1.1.1 Test purpose + +Same test purpose as in clause 6.3.4.2.1 in TS 38.521-1 [8] for the NR FR1 carrier(s), + +###### 6.3B.8.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.3B.8.1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.2.3 in TS 38.521-1 [8] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.1.1.4 Test description + +Same test description as in clause 6.3.4.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.2.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.3B.8.1.1.5 Test Requirement + +Same test requirement as in clause 6.3.4.2.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.1.2 Absolute power tolerance for intra-band non-contiguous EN-DC + +###### 6.3B.8.1.2.1 Test purpose + +Same test purpose as in clause 6.3.4.2.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.3B.8.1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.2.3 in TS 38.521-1 [8] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.1.2.4 Test description + +Same test description as in clause 6.3.4.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.2.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.3B.8.1.2.5 Test Requirement + +Same test requirement as in clause 6.3.4.2.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.1.3 Absolute power tolerance for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.3B.8.1.3.1 Test purpose + +Same test purpose as in clause 6.3.4.2.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +###### 6.3B.8.1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.2.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.1.3.4 Test description + +Same test description as in clause 6.3.4.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.2.4.1-1 will be updated as below. + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.3B.8.1.3.5 Test Requirement + +Same test requirement as in clause 6.3.4.2.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.1.4 Absolute power tolerance for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.3.4.2 in TS 38.521-2 [9] is incomplete for extreme conditions. +- The referred test case 6.3.4.2 in TS 38.521-2 [9] is incomplete for PC 1, 2, and 4. + +###### 6.3B.8.1.4.1 Test purpose + +Same test purpose as in clause 6.3.4.2.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +###### 6.3B.8.1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.3B.8.1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.1.4.4 Test description + +Same test description as in clause 6.3.4.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.2.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.2.4.1 in TS 38.521-2 [9] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.7. + +###### 6.3B.8.1.4.5 Test Requirement + +Same test requirement as in clause 6.3.4.2.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.3B.8.2 Relative power tolerance for EN-DC + +##### 6.3B.8.2.1 Relative power tolerance for intra-band contiguous EN-DC + +###### 6.3B.8.2.1.1 Test purpose + +Same test purpose as in clause 6.3.4.3.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.2.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.3B.8.2.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.3.3 in TS 38.521-1 [8] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.2.1.4 Test description + +Same test description as in clause 6.3.4.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.3.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.3B.8.2.1.5 Test Requirement + +Same test requirement as in clause 6.3.4.3.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.2.2 Relative power tolerance for intra-band non-contiguous EN-DC + +###### 6.3B.8.2.2.1 Test purpose + +Same test purpose as in clause 6.3.4.3.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.2.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.3B.8.2.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.3.3 in TS 38.521-1 [8] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.2.2.4 Test description + +Same test description as in clause 6.3.4.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.3.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.3B.8.2.2.5 Test Requirement + +Same test requirement as in clause 6.3.4.3.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.2.3 Relative power tolerance for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.3B.8.2.3.1 Test purpose + +Same test purpose as in clause 6.3.4.3.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.2.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +###### 6.3B.8.2.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.3.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.2.3.4 Test description + +Same test description as in clause 6.3.4.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.3.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.3B.8.2.3.5 Test Requirement + +Same test requirement as in clause 6.3.4.3.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.2.4 Relative power tolerance for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.3.4.3 in TS 38.521-2 [9] is incomplete + +###### 6.3B.8.2.4.1 Test purpose + +Same test purpose as in clause 6.3.4.3.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +###### 6.3B.8.2.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.3B.8.2.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.2.4.4 Test description + +Same test description as in clause 6.3.4.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.3.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-2 [9] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.7. + +###### 6.3B.8.2.4.5 Test Requirement + +Same test requirement as in clause 6.3.4.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.3B.8.3 Aggregate power tolerance for EN-DC + +##### 6.3B.8.3.1 Aggregate power tolerance for intra-band contiguous EN-DC + +###### 6.3B.8.3.1.1 Test purpose + +Same test purpose as in clause 6.3.4.4.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.3.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.3B.8.3.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.4.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.3.1.4 Test description + +Same test description as in clause 6.3.4.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.4.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.3.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.3B.8.3.1.5 Test Requirement + +Same test requirement as in clause 6.3.4.4.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.3.2 Aggregate power tolerance for intra-band non-contiguous EN-DC + +###### 6.3B.8.3.2.1 Test purpose + +Same test purpose as in clause 6.3.4.4.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.3.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.3B.8.3.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.4.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.3.2.4 Test description + +Same test description as in clause 6.3.4.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.4.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.3B.8.3.2.5 Test Requirement + +Same test requirement as in clause 6.3.4.4.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.3.3 Aggregate power tolerance for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.3B.8.3.3.1 Test purpose + +Same test purpose as in clause 6.3.4.4.1 in TS 38.521-1 [8] for the NR FR1 carrier(s). + +###### 6.3B.8.3.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL CC. + +###### 6.3B.8.3.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.4.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.3.3.4 Test description + +Same test description as in clause 6.3.4.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.4.4.1-1 will be updated as below. + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.3B.8.3.3.5 Test Requirement + +Same test requirement as in clause 6.3.4.4.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.3B.8.3.4 Aggregate power tolerance for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.3.4.4 in TS 38.521-2 [9] is incomplete for PC 1, 2, and 4. + +###### 6.3B.8.3.4.1 Test purpose + +Same test purpose as in clause 6.3.4.4.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +###### 6.3B.8.3.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.3B.8.3.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.3.4.4.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.3B.8.3.4.4 Test description + +Same test description as in clause 6.3.4.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +Notes defined in Table 6.3.4.4.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.3.4.4.4.1 in TS 38.521-2 [9] is replaced by the following steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.3B.8.3.4.5 Test Requirement + +Same test requirement as in clause 6.3.4.4.5 in TS 38.521-2 [9] for the NR carrier. + +## 6.3E Output power dynamics for V2X + +### 6.3E.0 Minimum conformance requirements + +#### 6.3E.0.1 General + +The E-UTRA SL and NR SL switching time mask defines the observation period between E-UTRA subframe and NR slot/mini-slot boundary. Both E-UTRA subframe and NR slot/mini-slot have ON power transmissions. The ON power is defined as the mean power over the symbol duration excluding any transient period. For E-UTRA subframe or NR slot/mini-slot having OFF power transmission, the general time mask for E-UTRA or NR shall apply. + +#### 6.3E.0.2 Output power dynamics for intra-band V2X operation + +For intra-band V2X operation bands specified in subclause 5.3E.1 and 5.3E.2, the SL switching time masks in Figure 6.3E.2-1 shall apply. + +The switching time shall be located on the RAT of lower priority when NR SL and LTE SL have different priorities based on priority information specified in TS 38.213. It is up to UE implementation when NR SL and LTE SL have the same priority based on priority information specified in TS 38.213. + +![Figure 6.3E.0.2-1: Time mask for switching between NR SL and E-UTRA SL. The diagram shows a horizontal timeline with two green arrows pointing to each other. The left arrow is labeled 'NR SL slot/LTE SL subframe (Lower priority)' and the right arrow is labeled 'LTE SL subframe/NR SL slot (Higher priority)'. A vertical dashed line separates the two arrows, labeled 'Switching time'. Below the arrows, two horizontal lines with arrows pointing to the switching time are labeled 'ON power requirement'.](63a2519518616620ef0e53d98b923c05_img.jpg) + +Figure 6.3E.0.2-1: Time mask for switching between NR SL and E-UTRA SL. The diagram shows a horizontal timeline with two green arrows pointing to each other. The left arrow is labeled 'NR SL slot/LTE SL subframe (Lower priority)' and the right arrow is labeled 'LTE SL subframe/NR SL slot (Higher priority)'. A vertical dashed line separates the two arrows, labeled 'Switching time'. Below the arrows, two horizontal lines with arrows pointing to the switching time are labeled 'ON power requirement'. + +**Figure 6.3E.0.2-1: Time mask for switching between NR SL and E-UTRA SL** + +#### 6.3E.0.3 Output power dynamics for inter-band V2X con-current operation + +For inter-band con-current NR V2X operation, the output power dynamics requirement shall be applied per each component carrier. The output dynamic requirements specified in clause 6.3 of TS 36.101 [5] apply for E-UTRA UL transmission and the requirements specified in clause 6.3E of TS 38.101-1 [2] apply for NR SL transmission. The output dynamic requirements specified in clause 6.3.2G, 6.3.3G, 6.3.4G of TS 36.101 [5] apply for E-UTRA SL transmission and the requirements specified in clause 6.3 of TS 38.101-1 [2] apply for NR UL transmission. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.3E. + +### 6.3E.1 Output power dynamics for intra-band V2X operation + +SL switching time mask requirements are specified for intra-band V2X operation, giving criteria on how the switching period position is decided based on priority information. No test is needed for this time mask requirement. + +### 6.3E.2 Output power dynamics for inter-band V2X operation + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.3.2, 6.3.3, 6.3.4 and 6.3.5 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.3E.1.1, [6.3E.2.2, 6.3E.3.2.1, 6.3E.3.3.1 and 6.3E.3.4.1] of TS 38.521-1 [8] and don't need to be tested again. + +For inter-band V2X configuration with NU Uu and E-UTRA V2X sidelink, the requirements in this test case can be well covered in clause 6.3.1, 6.3.2, 6.3.3 and 6.3.4 of TS 38.521-1 [8] for NR Uu carrier and clause 6.3.2G.1, 6.3.3G.1, 6.3.4G.1 and 6.3.4G.4 of TS 36.521-1 [10] and don't need to be tested again. + +## 6.4 Transmit signal quality + +## 6.4A Transmit Signal Quality for inter-band NR CA between FR and FR2 without EN-DC + +### 6.4A.1 Frequency error for inter-band NR CA between FR 1 and FR 2 without EN-DC + +#### 6.4A.1.1 Test purpose + +Same test purpose as in clause 6.4.1 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.4.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +#### 6.4A.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for frequency error apply and are tested in TS 38.521-1 [8] clauses 6.4 and 6.4A and TS 38.521-2 [9] clauses 6.4 and 6.4A. + +### 6.4A.2 Transmit Modulation Quality for inter-band NR CA without EN-DC + +#### 6.4A.2.1 Error Vector Magnitude for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.4A.2.1.1 Test purpose + +Same test purpose as in clause 6.4.2.1 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.4.2.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.4A.2.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for error vector magnitude apply and are tested in TS 38.521-1 [8] clauses 6.4 and 6.4A and TS 38.521-2 [9] clauses 6.4 and 6.4A. + +#### 6.4A.2.2 Carrier Leakage for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.4A.2.2.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.4.2.2 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.4A.2.2.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for carrier leakage apply and are tested in TS 38.521-1 [8] clauses 6.4 and 6.4A and TS 38.521-2 [9] clauses 6.4 and 6.4A. + +#### 6.4A.2.3 In-band Emissions for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.4A.2.3.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.4.2.3 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.4A.2.3.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for in-band emissions apply and are tested in TS 38.521-1 [8] clauses 6.4 and 6.4A and TS 38.521-2 [9] clauses 6.4 and 6.4A. + +#### 6.4A.2.4 EVM Equalizer Spectral Flatness for inter-band NR CA between FR 1 and FR 2 without EN-DC + +##### 6.4A.2.4.1 Test purpose + +Same test purpose as in clause 6.4.2.4 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.4.2.4 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.4A.2.4.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for EVM equalizer spectral flatness apply and are tested in TS 38.521-1 [8] clauses 6.4 and 6.4A and TS 38.521-2 [9] clauses 6.4 and 6.4A. + +## 6.4B Transmit Signal Quality for DC + +### 6.4B.1 Frequency error + +#### 6.4B.1.1 Frequency error for Intra-band contiguous EN-DC + +##### 6.4B.1.1.1 Test purpose + +Same test purpose as in clause 6.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.4B.1.1.3 Minimum conformance requirements + +For intra-band contiguous EN-DC, the requirement shall apply on each component carrier as defined in clause 6.5.1 in TS 38.101-3 [4] and in clause 6.4.1 in TS 38.101-1 [2], respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.4B.1.1. + +##### 6.4B.1.1.4 Test description + +Same test description as in clause 6.4.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +Notes defined in Table 6.4.1.4.1-1 will be updated as below. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +##### 6.4B.1.1.5 Test Requirement + +The 10 frequency error $\Delta f$ results must fulfil the test requirement defined in clause 6.4.1.5 TS 38.521-1 [8]. + +#### 6.4B.1.2 Frequency error for Intra-band non-contiguous EN-DC + +##### 6.4B.1.2.1 Test purpose + +Same test purpose as in clause 6.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.4B.1.2.3 Minimum conformance requirements + +For intra-band non-contiguous EN-DC, the requirement shall apply on each component carrier as defined in clause 6.5.1 in TS 38.101-3 [4] and in clause 6.4.1 in TS 38.101-1 [2], respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.4B.1.2. + +##### 6.4B.1.2.4 Test description + +Same test description as in clause 6.4.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.3, all of these configurations shall be tested with applicable test parameters for each intra-band non-contiguous EN-DC configuration specified in clause 5.3B.1.3, and are shown in table 6.4B.1.2.4-1. + +**Table 6.4B.1.2.4-1: Test Configuration Table** + +| Initial Conditions | | | | | +|-----------------------------------------------------------------------------------------------------|-------------------------------------|----------------------|-----------------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | MinWgap , MaxWgap | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [6] clause 4.3.1 | Highest N RB_agg (NOTE3) | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | | +| Test Parameters | | | | | +| | Downlink Configuration | | Uplink Configuration | | +| Test ID | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM
QPSK | Full RB (NOTE 1) | DFT-s-OFDM
QPSK | REFSENS (NOTE 2) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2. +NOTE 2: REFSENS refers to Table 7.3.2.4.1-3 which defines uplink RB configuration and start RB location for each SCS, channel BW and NR band. +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB\_agg , only the combination with the highest NRB\_SCG is tested. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1 with the exception that E-UTRA test frequency are specified in Table 7.4B.2.4.1-1 based on intra-band non-contiguous EN-DC configuration specified in clause 5.3B.1.3. + +For Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Steps 4 and 6 of Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8] is replaced by: + +4. The DL and UL Reference Measurement frequencies are set according to Table 6.4B.1.2.4-1. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +##### 6.4B.1.2.5 Test Requirement + +The 10 frequency error $\Delta f$ results must fulfil the test requirement defined in TS 38.521-1 [8], clause 6.4.1.5. + +#### 6.4B.1.3 Frequency error for Inter-band EN-DC within FR1 (1 NR CC) + +##### 6.4B.1.3.1 Test purpose + +Same test purpose as in clause 6.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +##### 6.4B.1.3.3 Minimum conformance requirements + +For inter-band EN-DC with uplink assigned to one E-UTRA band and one NR band, the requirements shall apply on each component carrier as defined in clause 6.5.1 in TS 36.101 [5] and in clause 6.4.1 in TS 38.101-1 [2], respectively, with all component carriers active. If multiple component carriers are assigned to one E-UTRA band, the requirements in clauses 6.5.1A in TS 36.101 [5] apply for those component carriers, and if multiple component carriers are assigned to one NR band, the requirements in clauses 6.4A.1 in TS 38.101-1 [2] apply for those component carriers. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.4B.1.3. + +##### 6.4B.1.3.4 Test description + +Same test description as in clause 6.4.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 6.4B.1.3.5 Test Requirement + +The 10 frequency error $\Delta f$ results must fulfil the test requirement defined in 6.4.1.5 TS 38.521-1 [8]. + +#### 6.4B.1.3a Frequency Error for inter-band NE-DC within FR1 + +No exception requirements applicable to E-UTRA or LTE. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.4.1 and 6.4A.1 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.5.1 and 6.5.1A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +#### 6.4B.1.4 Frequency Error for inter-band EN-DC including FR2 (1 NR CC) + +##### 6.4B.1.4.1 Test purpose + +Same test purpose as in clause 6.4.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.1.4.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.4B.1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.1.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B. + +##### 6.4B.1.4.4 Test description + +Same test description as in clause 6.4.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.4.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.4B.1.4.5 Test requirements + +Same test requirement as in clause 6.4.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +#### 6.4B.1.4\_1 Frequency Error for Inter-band EN-DC including FR2 (>1 NR CC) + +##### 6.4B.1.4\_1.1 Frequency Error for Inter-band EN-DC including FR2 (2 NR CCs) + +###### 6.4B.1.4\_1.1.1 Test purpose + +Same test purpose as in clause 6.4.1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.4B.1.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.4B.1.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.1.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +###### 6.4B.1.4\_1.1.4 Test description + +###### 6.4B.1.4\_1.1.4.1 Initial condition + +Same test description as in clause 6.4A.1.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.1.4\_1.1.5 Test Requirements + +Same test requirement as in clause 6.4A.1.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.4B.1.4\_1.2 Frequency Error for Inter-band EN-DC including FR2 (3 NR CCs) + +###### 6.4B.1.4\_1.2.1 Test purpose + +Same test purpose as in clause 6.4.1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.4B.1.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.4B.1.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.1.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +###### 6.4B.1.4\_1.2.4 Test description + +###### 6.4B.1.4\_1.2.4.1 Initial condition + +Same test description as in clause 6.4A.1.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.1.4\_1.2.5 Test Requirements + +Same test requirement as in clause 6.4A.1.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.4B.1.4\_1.3 Frequency Error for Inter-band EN-DC including FR2 (4 NR CCs) + +###### 6.4B.1.4\_1.3.1 Test purpose + +Same test purpose as in clause 6.4.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.1.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.4B.1.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +###### 6.4B.1.4\_1.3.4 Test description + +###### 6.4B.1.4\_1.3.4.1 Initial condition + +Same test description as in clause 6.4A.1.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.1.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.1.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.1.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.1.4\_1.3.5 Test Requirements + +Same test requirement as in clause 6.4A.1.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.4B.1.4D Frequency error for inter-band EN-DC including FR2 for UL-MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4D.1 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS and Annex F needs to be updated. + +##### 6.4B.1.4D.1 Test purpose + +Same test purpose as in clause 6.4D.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.1.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 and UL MIMO. + +##### 6.4B.1.4D.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], 38.101-1 [2] and 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +Same minimum conformance requirements as in clause 6.4D.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.4B.1.4D.4 Test description + +###### 6.4B.1.4D.4.1 Initial conditions + +Same test description as in clause 6.4D.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4D.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4D.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4D.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.4B.1.4D.5 Test requirement + +Same test requirement as in clause 6.4D.1.5 in TS 38.521-2 [9] for the NR carrier. + +### 6.4B.2 Transmit Modulation Quality for DC + +#### 6.4B.2.1 Transmit Modulation Quality for intra-band contiguous EN-DC + +##### 6.4B.2.1.1 Error Vector Magnitude for intra-band contiguous EN-DC + +###### 6.4B.2.1.1.1 Test purpose + +The Error Vector Magnitude is a measure of the difference between the reference waveform and the measured waveform. This difference is called the error vector. Before calculating the EVM the measured waveform is corrected by the sample timing offset and RF frequency offset. Then the carrier leakage shall be removed from the measured waveform before calculating the EVM. + +The measured waveform is further equalised using the channel estimates subjected to the EVM equaliser spectrum flatness requirement specified in clause 6.4B.2.1.4.3. For DFT-s-OFDM waveforms, the EVM result is defined after the front-end FFT and IDFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. For CP-OFDM waveforms, the EVM result is defined after the front-end FFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. + +The basic EVM measurement interval in the time domain is one preamble sequence for the PRACH and the duration of PUCCH/PUSCH channel, or one hop, if frequency hopping is enabled for PUCCH and PUSCH in the time domain. The EVM measurement interval is reduced by any symbols that contains an allowable power transient as defined in clause 6.3.3.3 of TS 38.521-1 [8]. + +###### 6.4B.2.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band EN-DC. + +###### 6.4B.2.1.1.3 Minimum conformance requirements + +For the intra-band contiguous EN-DC with one component carrier per CG the EVM requirement applies with PRB allocation in one of the CG and the other CG unallocated. + +The EVM requirements for each CG are according to clause 6.5.2 of TS 36.101 [5] for the MCG and clause 6.4.2 of TS 38.101-1 [2] for the SCG with EN-DC configured. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.1.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.1.1.4 Test description + +Same test description as in clause 6.4.2.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +**Table 6.4B.2.1.1.4-1: Test Configuration Table** + +| Initial Conditions | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Mid range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | Highest NRB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg, only the combination with the highest NRB_SCG is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 6.4B.2.1.1.4-1. + +For Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.4.2.1.4.2 in TS 38.521-1 [8]. + +For Message contents as in clause 6.4.2.1.4.3 in TS 38.521-1 [8], the following exception: + +**Table 6.4B.2.1.1.4-2: RACH-ConfigGeneric: PRACH measurement** + +| Derivation Path: TS 38.508-1[5], Table 4.6.3-130 | | | | +|--------------------------------------------------|--------------|-------------------|--------------------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| RACH-ConfigGeneric ::= SEQUENCE { | | | | +| prach-ConfigurationIndex | 14 | Unpaired Spectrum | PRACH Format 0 AND delay is given to SCG in Step 8 of Initial conditions | +| | 12 | Unpaired Spectrum | PRACH Format 0 AND delay is given to MCG in Step 8 of Initial conditions | + +###### 6.4B.2.1.1.5 Test requirements + +Same test requirement as in clause 6.4.2.1.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.1.2 Carrier Leakage for intra-band contiguous EN-DC + +###### 6.4B.2.1.2.1 Test purpose + +Carrier leakage expresses itself as unmodulated sine wave with the carrier frequency or centre frequency of aggregated transmission bandwidth configuration. It is an interference of approximately constant amplitude and independent of the amplitude of the wanted signal. Carrier leakage interferes with the centre sub carriers of the UE under test (if allocated), especially, when their amplitude is small. The measurement interval is defined over one slot in the time domain. + +The purpose of this test is to exercise the UE transmitter to verify its modulation quality in terms of carrier leakage. + +###### 6.4B.2.1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band EN-DC. + +###### 6.4B.2.1.2.3 Minimum conformance requirements + +The carrier leakage requirements for each CG are according to clause 6.5.2 of TS 36.101 [5] for the MCG and clause 6.4.2 of TS 38.101-1 [2] for the SCG with EN-DC configured. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.1.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.1.2.4 Test description + +Same test description as in clause 6.4.2.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +**Table 6.4B.2.1.2.4-1: Test Configuration** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Mid range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | Highest NRB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg , only the combination with the highest NRB_SCG is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 6.4B.2.1.2.4-1 For Initial conditions as in clause 6.4.2.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.2.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.4B.2.1.2.5 Test requirements + +Same test requirement as in clause 6.4.2.2.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.1.3 In-band Emissions for intra-band contiguous EN-DC + +###### 6.4B.2.1.3.1 Test purpose + +The in-band emissions are a measure of the interference falling into the non-allocated resources blocks. + +The in-band emission is defined as the average emission across 12 sub-carriers and as a function of the RB offset from the edge of the allocated UL transmission bandwidth. The in-band emission is measured as the ratio of the UE output power in a non-allocated RB to the UE output power in an allocated RB. + +The basic in-band emissions measurement interval is defined over one slot in the time domain, however, the minimum requirement applies when the in-band emission measurement is averaged over 10 sub-frames. When the PUSCH or PUCCH transmission slot is shortened due to multiplexing with SRS, the in-band emissions measurement interval is reduced by one or more symbols, accordingly. + +The purpose of this test is to exercise the UE transmitter to verify its modulation quality in terms of in-band emissions. + +###### 6.4B.2.1.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.4B.2.1.3.3 Minimum conformance requirements + +For the MCG the in-band emission requirements in Table 6.5.2A.3.1-1 and Table 6.5.2A.3.1-2 in TS 36.101 [5] apply within the aggregated transmission bandwidth configuration of the EN-DC bandwidth with the carriers of both CGs active and one single contiguous PRB allocation of bandwidth $L_{CRB}$ within the MCG at the edge of the said aggregated transmission bandwidth configuration. + +For the SCG the in-band emission requirements in Table 6.5.2A.3.1-1 and Table 6.5.2A.3.1-2 in TS 36.101 [5] apply within the aggregated transmission bandwidth configuration of the EN-DC bandwidth with the carriers of both CGs active and one single contiguous PRB allocation of bandwidth $L_{CRB}$ within the SCG at the edge of the aggregated transmission bandwidth configuration. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.1.3 + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.4B.2.1.3.4 Test description + +###### 6.4B.2.1.3.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and test channel bandwidths based on NR operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.4B.2.1.3.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521.1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.4B.2.1.3.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|------------------------------------------------------------------------|-------------------------------------------------------------------|-----------------------------------|-------------------------------|-------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Low range, Mid range, High range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | Lowest N RB_agg , Highest N RB_agg (NOTE 2) | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest | | | | | +| Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 5) | Modulation | RB allocation (NOTE 1) | +| 1
(NOTE3) | N/A for In-band emission test | QPSK | 0 | DFT-s-OFDM QPSK | Inner_1RB_Right | +| 2
(NOTE 4) | | QPSK | 0 | DFT-s-OFDM QPSK | Inner_1RB_Left | +| 3
(NOTE3) | | QPSK | 0 | CP-OFDM QPSK | Inner_1RB_Right | +| 4
(NOTE 4) | | QPSK | 0 | CP-OFDM QPSK | Inner_1RB_Left | +| 5
(NOTE3) | | QPSK | Outer_1RB_Left | DFT-s-OFDM QPSK | 0 | +| 6
(NOTE 4) | | QPSK | Outer_1RB_Right | DFT-s-OFDM QPSK | 0 | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same NRB\_agg, select the combination to test as follows: +- Lowest ENBW: NR component with lowest NRB is tested. +- Highest ENBW: NR component with highest NRB is tested. +NOTE 3: Applicable when E-UTRA cell carrier frequency is lower than NR cell carrier. +NOTE 4: Applicable when NR cell carrier frequency is lower than E-UTRA cell carrier. +NOTE 5: Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. NR downlink signals are initially set up according to Annex C.0, C.1, and C.2 and uplink signals according to Annex G.0, G.1, G.2, and G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.4B.2.1.3.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.4B.2.1.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.4B.2.1.3.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. For NR CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as +MU to +(MU + Uplink power control window size) dB of the target power level 0dBm, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.2-1 for the carrier frequency f and the channel bandwidth BW. + - Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. +3. Measure In-band emission on NR CC using Global In-Channel Tx-Test (Annex E). Measure power spectral density on E-UTRA CC. For TDD slots with transient periods are not under test. +4. For NR CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as +MU to +(MU + Uplink power control window size) dB of the target power level -30dBm, where MU and Uplink power control window size are defined above. +5. Measure In-band emission on NR CC using Global In-Channel Tx-Test (Annex E). Measure power spectral density on E-UTRA CC. For TDD slots with transient periods are not under test +6. For NR CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as +MU to +(MU + Uplink power control window size) dB of the target power level -40dBm, where MU and Uplink power control window size are defined above. +7. Measure In-band emission on NR CC using Global In-Channel Tx-Test (Annex E). Measure power spectral density on E-UTRA CC. For TDD slots with transient periods are not under test. +8. For E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as +MU to +(MU + Uplink power control window size) dB of the target power level 0dBm, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.2-1 for the carrier frequency f and the channel bandwidth BW. + - Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. +9. Measure In-band emission on E-UTRA CC using Global In-Channel Tx-Test (Annex E). Measure power spectral density on NR CC. For TDD slots with transient periods are not under test. +10. For E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as +MU to +(MU + Uplink power control window size) dB of the target power level -30dBm, where MU and Uplink power control window size are defined above. +11. Measure In-band emission on E-UTRA CC using Global In-Channel Tx-Test (Annex E). Measure power spectral density on NR CC. For TDD slots with transient periods are not under test +12. For E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as +MU to +(MU + Uplink power control window size) dB of the target power level -40dBm, where MU and Uplink power control window size are defined above. + +13. Measure In-band emission on E-UTRA CC using Global In-Channel Tx-Test (Annex E). Measure power spectral density on NR CC. For TDD slots with transient periods are not under test. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.4B.2.1.3.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +NOTE 2: The purpose of the Uplink power control window is to ensure that the actual UE output power is no less than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +**Table 6.4B.2.1.3.4.2-1: Void** + +**Table 6.4B.2.1.3.4.2-2: Void** + +###### **6.4B.2.1.3.4.3 Message contents** + +Message contents are according to TS 36.508-1 [11] clause 4.6 and TS 38.508-1 [6] clause 4.6.1. + +###### **6.4B.2.1.3.5 Test requirements** + +Each of the [20] In-band emissions results, derived in Annex E.4.3 shall not exceed the corresponding values in Table 6.4B.2.1.3.5-1. + +**Table 6.4B.2.1.3.5-1: Test requirements for in-band emissions (allocated component carrier)** + +| Parameter | Unit | Limit | | Applicable Frequencies | +|-----------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|------------------------------------------| +| General | dB | $\max \left\{ \begin{aligned} & -25 - 10 \cdot \log_{10}(N_{RB} / L_{CRB}), \\ & 20 \cdot \log_{10} EVM - 3 - 5 \cdot ( \Delta_{RB} - 1) / L_{CRB}, \\ & -57 \text{ dBm} / 180\text{kHz} - P_{RB} \end{aligned} \right\} + TT$ | | Any non-allocated (NOTE 2) | +| IQ Image | dB | -25 | | Exception for IQ image (NOTE 3) | +| Carrier leakage | dBc | 25 + TT | Output power > 0 dBm | Exception for Carrier frequency (NOTE 4) | +| | | 20 + TT | -30 dBm ≤ Output power ≤ 0 dBm | | +| | | 10 + TT | -40 dBm ≤ Output power < -30 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of $P_{RB} - 30$ dB and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. $P_{RB}$ is defined in NOTE 9. The limit is evaluated in each non-allocated RB. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs + +NOTE 3: Exceptions to the general limit are allowed for up to $L_{CRBs} + 1$ RBs within a contiguous width of $L_{CRBs} + 1$ non-allocated RBs. The measurement bandwidth is 1 RB. + +NOTE 4: Exceptions to the general limit are allowed for up to two contiguous non-allocated RBs. The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in the non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: $L_{CRB}$ is the Transmission Bandwidth (see Figure 5.6-1) not exceeding $\lfloor N_{RB} / 2 - 1 \rfloor$ + +NOTE 6: $N_{RB}$ is the Transmission Bandwidth Configuration (see Figure 5.6-1) of the component carrier with RBs allocated. + +NOTE 7: $EVM$ is the limit specified in Table 6.5.2.1.1-1 for the modulation format used in the allocated RBs. + +NOTE 8: $\Delta_{RB}$ is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. $\Delta_{RB} = 1$ or $\Delta_{RB} = -1$ for the first adjacent RB outside of the allocated bandwidth). + +NOTE 9: $P_{RB}$ is the transmitted power per 180 kHz in allocated RBs, measured in dBm. + +NOTE 10: Test tolerance $TT = 0.8$ dB. + +The in-band emissions results, measured with the spectral test shall not exceed the corresponding values in Table 6.4B.2.1.3.5-2. + +**Table 6.4B.2.1.3.5-2: Test requirements for in-band emissions (not allocated component carrier)** + +| Para-meter | Unit | Meas BW
NOTE 1 | Limit | | remark | Applicable
Frequencies | +|-----------------|------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| General | dB | BW of 1 RB
(180KHz
rectangular) | $\max \left\{ -25 - 10 \cdot \log_{10} (N_{RB} / L_{CRB}), \right. \\ \left. 20 \cdot \log_{10} EVM - 3 - 5 \cdot ( \Delta_{RB} - 1) / L_{CRB}, \right. \\ \left. -57 \text{ dBm} / 180\text{kHz} - P_{RB} \right\}$ | | The reference value is the average power per allocated RB in the allocated component carrier | Any RB in the non-allocated component carrier. The frequency raster of the RBs is derived when this component carrier is allocated with RBs | +| IQ Image | dB | BW of 1 RB
(180KHz
rectangular) | -25 + TT

NOTE 2 | | The reference value is the average power per allocated RB in the allocated component carrier | The frequencies of the $L_{CRB}$ contiguous non-allocated RBs are unknown. The frequency raster of the RBs is derived when this component carrier is allocated with RBs | +| Carrier leakage | dBc | BW of 1 RB
(180KHz
rectangular) | NOTE 3 | | The reference value is the total power of the allocated RBs in the allocated component carrier | The frequencies of the up to 2 non-allocated RBs are unknown. The frequency raster of the RBs is derived when this component carrier is allocated with RBs | +| | | | -25 + TT | Output power > 0 dBm | | | +| | | | -20 + TT | -30 dBm ≤ Output power ≤ 0 dBm | | | +| | | | -10 + TT | -40 dBm ≤ Output power < -30 dBm | | | + +NOTE 1: Resolution BWs smaller than the measurement BW may be integrated to achieve the measurement bandwidth. + +NOTE 2: Exceptions to the general limit are allowed for up to $L_{CRB} + 1$ RBs within a contiguous width of $L_{CRB} + 1$ non-allocated RBs. + +NOTE 3: Two Exceptions to the general limit are allowed for up to two contiguous non-allocated RBs + +NOTE 4: NOTES 1, 5, 6, 7, 8, 9 from Table 6.5.2A.3.1-1 apply for Table 6.5.2A.3.1-2 as well. + +NOTE 5: $\Delta_{RB}$ for measured non-allocated RB in the non-allocated component carrier may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. + +NOTE 6: Test tolerance TT = 0.8 dB. + +##### 6.4B.2.1.4 EVM Equalizer Flatness for intra-band contiguous EN-DC + +###### 6.4B.2.1.4.1 Test purpose + +Same test purpose as in clause 6.4.2.4 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.4B.2.1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.4.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.1.4.4 Test description + +Same test description as in clause 6.4.2.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +**Table 6.4B.2.1.4.4-1: Test Configuration Table** + +| Initial Conditions | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Mid range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | Highest NRB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg, only the combination with the highest NRB_SCG is tested. | | + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.4.2.4.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.4B.2.1.4.5 Test requirement + +Same test requirement as in clause 6.4.2.4.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.4B.2.2 Transmit Modulation Quality for intra-band non-contiguous EN-DC + +##### 6.4B.2.2.1 Error Vector Magnitude for intra-band non-contiguous EN-DC + +###### 6.4B.2.2.1.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.2.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.4B.2.2.1.3 Minimum conformance requirements + +For the intra-band non-contiguous EN-DC with one component carrier per CG the EVM requirement applies with PRB allocation in one of the CG and the other CG unallocated. + +The EVM requirements for each CG are according to clause 6.5.2.1 of TS 36.101 [5] for the MCG and clause 6.4.2.1.3 of TS 38.521-1 [8] for the SCG with EN-DC configured. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.2.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.2.1.4 Test description + +Same test description as in clause 6.4.2.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.4.2.1.4.2 in TS 38.521-1 [8]. + +For Message contents as in clause 6.4.2.1.4.3 in TS 38.521-1 [8], the following exception: + +**Table 6.4B.2.2.1.4-1: RACH-ConfigGeneric: PRACH measurement** + +| Derivation Path: TS 38.508-1[5], Table 4.6.3-130 | | | | +|--------------------------------------------------|--------------|-------------------|--------------------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| RACH-ConfigGeneric ::= SEQUENCE { | | | | +| prach-ConfigurationIndex | 14 | Unpaired Spectrum | PRACH Format 0 AND delay is given to SCG in Step 8 of Initial conditions | +| | 12 | Unpaired Spectrum | PRACH Format 0 AND delay is given to MCG in Step 8 of Initial conditions | + +###### 6.4B.2.2.1.5 Test requirement + +Same test requirement as in clause 6.4.2.1.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.2.2 Carrier Leakage for intra-band non-contiguous EN-DC + +###### 6.4B.2.2.2.1 Test purpose + +Same test purpose as in clause 6.4.2.2.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.2.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.4B.2.2.2.3 Minimum conformance requirements + +The carrier leakage requirements for each CG are according to clause 6.5.2.2 of TS 36.101 [5] for the MCG and clause 6.4.2.2.3 of TS 38.521-1 [8] for the SCG with EN-DC configured and PRB allocation only in the CG being measured. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.2.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.2.2.4 Test description + +Same test description as in clause 6.4.2.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.4.2.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.2.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.4B.2.2.2.5 Test requirement + +Same test requirement as in clause 6.4.2.2.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.2.3 In-band Emissions for intra-band non-contiguous EN-DC + +###### 6.4B.2.2.3.1 Test purpose + +Same test purpose as in clause 6.4.2.3.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.2.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.4B.2.2.3.3 Minimum conformance requirements + +For the MCG the in-band emission requirements in Table 6.5.2A.3.1-1 and Table 6.5.2A.3.1-2 in TS 36.101 [5] apply within the transmission bandwidth configuration of the MCG with the carriers of both CGs active and one single contiguous PRB allocation of bandwidth $L_{CRB}$ within the MCG at the edge of the transmission bandwidth configuration. + +For the SCG the in-band emission requirements in Table 6.4.2.3-1 TS 38.101-1 [2] apply within the transmission bandwidth configuration of the SCG with the carriers of both CGs active and one single contiguous PRB allocation of bandwidth $L_{CRB}$ within the SCG at the edge of the transmission bandwidth configuration. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.2.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.2.3.4 Test description + +Same test description as in clause 6.4.2.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +**Table 6.4B.2.2.3.4-1: Test Configuration Table** + +| Initial Conditions | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Low range, Mid range, High range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1 | Lowest $N_{RB\_agg}$ , Highest $N_{RB\_agg}$ (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same $N_{RB\_agg}$ , only the combination with the highest $N_{RB\_SCG}$ is tested for Lowest $N_{RB\_agg}$ and Highest $N_{RB\_agg}$ . | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 6.4B.2.2.3.4-1. + +For Initial conditions as in clause 6.4.2.3.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.3.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.4B.2.2.3.5 Test requirements + +Same test requirement as in clause 6.4.2.3.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.2.4 EVM Equalizer Flatness for intra-band non-contiguous EN-DC + +###### 6.4B.2.2.4.1 Test purpose + +Same test purpose as in clause 6.4.2.4 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.2.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.4B.2.2.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.4.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.2.4.4 Test description + +Same test description as in clause 6.4.2.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +**Table 6.4B.2.2.4.4-1: Test Configuration Table** + +| Initial Conditions | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--|----------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | MaxWGap | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [6] clause 4.3.1 | Highest N RB_agg (NOTE 1, 2) | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | +| Test parameters | | | | +| | Downlink Configuration | | Uplink Configuration | +| Test ID | N/A for EVM equalizer flatness testing | | Modulation | +| 1 | | | NR RB allocation (NOTE 3) | +| 2 | | | DFT-s-OFDM QPSK | +| | | | Outer Full | +| | | | CP-OFDM QPSK | +| | | | Outer Full | +| NOTE 1: Test Channel Bandwidths are checked separately for each NR band, which applicable channel bandwidths are specified in Table 5.3.5-1 of 38.521-1 [8]. | | | | +| NOTE 2: Lowest and highest allowed NR channel BW as specified in Table 5.3B.1.3-1. If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg, only the combination with the highest NRB_SCG is tested. | | | | +| NOTE 3: The specific configuration of each RB allocation is defined in Table 6.1-1 of 38.521-1 [8]. | | | | + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.4.2.4.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.4B.2.2.4.5 Test requirement + +Same test requirement as in clause 6.4.2.4.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.4B.2.3 Transmit Modulation Quality for inter-band EN-DC within FR1 + +##### 6.4B.2.3.1 Error Vector Magnitude for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.4B.2.3.1.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.3.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.4B.2.3.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.3.1.4 Test description + +Same test description as in clause 6.4.2.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Same test procedure as in clause 6.4.2.1.4.2 in TS 38.521-1 [8]. + +###### 6.4B.2.3.1.5 Test requirement + +Same test requirement as in clause 6.4.2.1.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.3.2 Carrier Leakage for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.4B.2.3.2.1 Test purpose + +Same test purpose as in clause 6.4.2.2.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.3.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.4B.2.3.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.2.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.3.2.4 Test description + +Same test description as in clause 6.4.2.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.4.2.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.4B.2.3.2.5 Test requirement + +Same test requirement as in clause 6.4.2.2.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.3.3 In-band Emissions for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.4B.2.3.3.1 Test purpose + +Same test purpose as in clause 6.4.2.3.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.3.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.4B.2.3.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.3.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.3.3.4 Test description + +Same test description as in clause 6.4.2.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.4.2.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.3.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Same test procedure as in clause 6.4.2.3.4.2 in TS 38.521-1 [8]. + +###### 6.4B.2.3.3.5 Test requirement + +Same test requirement as in clause 6.4.2.3.5 in TS 38.521-1 [8] for the NR carrier. + +##### 6.4B.2.3.4 EVM Equalizer Flatness for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.4B.2.3.4.1 Test purpose + +Same test purpose as in clause 6.4.2.4 in TS 38.521-1 [8] for the NR carrier. + +###### 6.4B.2.3.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.4B.2.3.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.4.3 in TS 38.521-1 [8] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.3.4.4 Test description + +###### 6.4B.2.3.4.4.1 Initial conditions + +Same test description as in clause 6.4.2.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.4.4.2 in TS 38.521-1 [8] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.4B.2.3.4.5 Test requirement + +Same test requirement as in clause 6.4.2.4.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.4B.2.3a Transmit Modulation Quality for inter-band NE-DC within FR1 + +##### 6.4B.2.3a.1 Error Vector Magnitude for inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested covered in 6.4.2.1 and 6.4A.2.1 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.5.2.1 and 6.5.2A.1 of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +##### 6.4B.2.3a.2 Carrier Leakage for inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.4.2.2 and 6.4A.2.2 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.5.2.2 and 6.5.2A.2 of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +##### 6.4B.2.3a.3 In-band Emissions for inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.4.2.3 and 6.4A.2.3 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.5.2 and 6.5.2A.3 of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +##### 6.4B.2.3a.4 EVM Equalizer Flatness for inter-band NE-DC within FR1 (1 NR CC) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier in this test case are tested in 6.4.2.4 and 6.4.2.5 of TS 38.521-1 [8], and the requirements for LTE carrier in this test case are tested in 6.5.2.4 of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +#### 6.4B.2.4 Transmit Modulation Quality for inter-band EN-DC including FR2 + +##### 6.4B.2.4.1 Error Vector Magnitude for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note:** This clause is incomplete. The following aspects are either missing or not yet determined in the referred test case 6.4.2.1 in TS 38.521-2 [9]: + +- Measurement Uncertainty and Test Tolerance are FFS except for PUSCH, PC3 in FR2a and FR2b, and PC1 in FR2a. + +###### 6.4B.2.4.1.1 Test purpose + +Same test purpose as in clause 6.4.2.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.4B.2.4.1.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], 38.101-1 [2] and 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.1.4 Test description + +###### 6.4B.2.4.1.4.1 Initial conditions + +Same test description as in clause 6.4.2.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.1.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1.5 Test requirement + +Same test requirement as in clause 6.4.2.1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.1a Error Vector Magnitude with Power Boost for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined in the referred test case 6.4.2.1\_1 in TS 38.521-2 [9]:** + +- **Measurement Uncertainty and Test Tolerance are FFS except for PUSCH, PC3 in FR2a and FR2b.** + +###### 6.4B.2.4.1a.1 Test purpose + +Same test purpose as in clause 6.4.2.1\_1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1a.2 Test applicability + +This test case applies to all types of NR UE release 16 and forward supporting *mpr-PowerBoost-FR2-r16* UE capability, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.4B.2.4.1a.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], 38.101-1 [2] and 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4.2.1\_1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.1a.4 Test description + +Same test description as in clause 6.4.2.1\_1.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4.2.1\_1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.1\_1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.1\_1.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_2.5 Test requirement + +Same test requirement as in clause 6.4.2.1\_1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.1\_1 Error Vector Magnitude for inter-band EN-DC including FR2 (>1 NR CC) + +###### 6.4B.2.4.1\_1.1 Error Vector Magnitude for inter-band EN-DC including FR2 (2 NR CCs) + +Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.4A.2.1.1 in TS 38.521-2 [9] is incomplete. +- Test configuration table is FFS. +- This test is incomplete due to lack of RRC framework for LO position retrieval + +###### 6.4B.2.4.1\_1.1.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.4B.2.4.1\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.1.4 Test description + +###### 6.4B.2.4.1\_1.1.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.1.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.1.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.2 Error Vector Magnitude for inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.1.2 in TS 38.521-2 [9] is incomplete. +- Test configuration table is FFS. + +###### 6.4B.2.4.1\_1.2.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.4B.2.4.1\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.2.4 Test description + +###### 6.4B.2.4.1\_1.2.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.2.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.2.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.3 Error Vector Magnitude for inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.1.3 in TS 38.521-2 [9] is incomplete. + +- Test configuration table is FFS. + +###### 6.4B.2.4.1\_1.3.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.4B.2.4.1\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.3.4 Test description + +###### 6.4B.2.4.1\_1.3.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.3.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.3.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.4 Error Vector Magnitude for inter-band EN-DC including FR2 (5 NR CCs) + +Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.1\_1.4.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.4B.2.4.1\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.4.4 Test description + +###### 6.4B.2.4.1\_1.4.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.4.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.4.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.5 Error Vector Magnitude for inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- **Measurement Uncertainty and Test Tolerance are FFS.** + +###### 6.4B.2.4.1\_1.5.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.4B.2.4.1\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.5.4 Test description + +###### 6.4B.2.4.1\_1.5.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.5.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.5.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.5.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.5.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.5.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.5.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.6 Error Vector Magnitude for inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- **Measurement Uncertainty and Test Tolerance are FFS.** + +###### 6.4B.2.4.1\_1.6.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.4B.2.4.1\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.6.4 Test description + +###### 6.4B.2.4.1\_1.6.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.6.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.6.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.6.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.6.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.6.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.6.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.7 Error Vector Magnitude for inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- **Measurement Uncertainty and Test Tolerance are FFS.** + +###### 6.4B.2.4.1\_1.7.1 Test purpose + +Same test purpose as in clause 6.4.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.1\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.4B.2.4.1\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.4B.2.4.1\_1.7.4 Test description + +###### 6.4B.2.4.1\_1.7.4.1 Initial condition + +Same test description as in clause 6.4A.2.1.7.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.1.7.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.1.7.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.1.7.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1\_1.7.5 Test Requirements + +Same test requirement as in clause 6.4A.2.1.7.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.4B.2.4.1D Error Vector Magnitude for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4D.2.1 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS and Annex F needs to be updated. + +##### 6.4B.2.4.1D.1 Test purpose + +Same test purpose as in clause 6.4D.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.1D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 and UL MIMO. + +##### 6.4B.2.4.1D.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], 38.101-1 [2] and 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4D.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.4B.2.4.1D.4 Test description + +###### 6.4B.2.4.1D.4.1 Initial conditions + +Same test description as in clause 6.4D.2.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4D.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4D.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4D.2.1.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.1D.5 Test requirement + +Same test requirement as in clause 6.4D.2.1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.2 Carrier Leakage for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- Measurement Uncertainty and Test Tolerance are FFS for PC1, PC2, and PC4. +- The test case is incomplete for band n259. + +###### 6.4B.2.4.2.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.4B.2.4.2.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], 38.101-1 [2] and 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4.2.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied + +###### 6.4B.2.4.2.4 Test description + +###### 6.4B.2.4.2.4.1 Initial conditions + +Same test description as in clause 6.4.2.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.2.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2.5 Test requirement + +Same test requirement as in clause 6.4.2.2.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.2D Carrier Leakage for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4D.2.2 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS and Annex F needs to be updated. + +###### 6.4B.2.4.2D.1 Test purpose + +Same test purpose as in clause 6.4D.2.2.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 and UL MIMO. + +##### 6.4B.2.4.2D.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], 38.101-1 [2] and 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4D.2.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied + +###### 6.4B.2.4.2D.4 Test description + +###### 6.4B.2.4.2D.4.1 Initial conditions + +Same test description as in clause 6.4D.2.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4D.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4D.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4D.2.2.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2D.5 Test requirement + +Same test requirement as in clause 6.4D.2.2.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.2\_1 Carrier Leakage for inter-band EN-DC including FR2 (>1 NR CC) + +###### 6.4B.2.4.2\_1.1 Carrier Leakage for inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.2.1 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. +- This test is incomplete due to lack of RRC framework for LO position retrieval. + +###### 6.4B.2.4.2\_1.1.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR CCs. + +###### 6.4B.2.4.2\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.1.4 Test Description + +###### 6.4B.2.4.2\_1.1.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.1.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.1.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.2 Carrier Leakage for inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.2.2 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.2\_1.2.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR CCs. + +###### 6.4B.2.4.2\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.2.4 Test Description + +###### 6.4B.2.4.2\_1.2.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.2.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.2.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.3 Carrier Leakage for inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.2.3 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.2\_1.3.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.4B.2.4.2\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.3.4 Test Description + +###### 6.4B.2.4.2\_1.3.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.3.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.3.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.4 Carrier Leakage for inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.2.4 in TS 38.521-2 [9] is incomplete. + +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.2\_1.4.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.4B.2.4.2\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.4.4 Test Description + +###### 6.4B.2.4.2\_1.4.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.4.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.4.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.5 Carrier Leakage for inter-band EN-DC including FR2 (6 NR CCs) + +Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.4A.2.2.5 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.2\_1.5.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.4B.2.4.2\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.5.4 Test Description + +###### 6.4B.2.4.2\_1.5.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.5.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.5.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.5.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.5.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.5.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.5.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.6 Carrier Leakage for inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.2.6 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.2\_1.6.1 Test purpose + +Same test purpose as in clause 6.4.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.4B.2.4.2\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.6.4 Test Description + +###### 6.4B.2.4.2\_1.6.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.6.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.6.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.6.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.6.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.6.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.6.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.7 Carrier Leakage for inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.2.7 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.2\_1.7.1 Test purpose + +Same test purpose as in clause 6.4A.2.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.2\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.4B.2.4.2\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.2.3. + +###### 6.4B.2.4.2\_1.7.4 Test Description + +###### 6.4B.2.4.2\_1.7.4.1 Initial conditions + +Same test description as in clause 6.4A.2.2.7.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.4A.2.2.7.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.2.7.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.2.7.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.2\_1.7.5 Test Requirement + +Same test requirement as in clause 6.4A.2.2.7.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.3 In-band Emissions for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4.2.3 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. +- 38.101-2 [3] clause 6.3.4.3: Relative power tolerances are in square brackets. + +###### 6.4B.2.4.3.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.4B.2.4.3.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], TS 38.101-1 [2] and TS 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.3.4 Test description + +###### 6.4B.2.4.3.4.1 Initial conditions + +Same test description as in clause 6.4.2.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.3.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3.5 Test requirement + +Same test requirement as in clause 6.4.2.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.4B.2.4.3D In-band Emissions for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4D.2.3 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS and Annex F needs to be updated. + +##### 6.4B.2.4.3D.1 Test purpose + +Same test purpose as in clause 6.4D.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.3D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 and UL MIMO. + +##### 6.4B.2.4.3D.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], TS 38.101-1 [2] and TS 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4D.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.3D.4 Test description + +###### 6.4B.2.4.3D.4.1 Initial conditions + +Same test description as in clause 6.4D.2.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4D.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4D.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4D.2.3.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3D.5 Test requirement + +Same test requirement as in clause 6.4D.2.3.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.3\_1 In-band Emissions for inter-band EN-DC including FR2 (>1 NR CC) + +###### 6.4B.2.4.3\_1.1 In-band Emissions for inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.1 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. +- This test is incomplete due to lack of RRC framework for LO position retrieval. + +###### 6.4B.2.4.3\_1.1.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2NR UL CCs. + +###### 6.4B.2.4.3\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.3. + +###### 6.4B.2.4.3\_1.1.4 Test description + +###### 6.4B.2.4.3\_1.1.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.1.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.1.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.2 In-band Emissions for inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.2 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.3\_1.2.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3NR UL CCs. + +###### 6.4B.2.4.3\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.3. + +###### 6.4B.2.4.3\_1.2.4 Test description + +###### 6.4B.2.4.3\_1.2.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.2.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.2.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.3 In-band Emissions for inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.3 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.3\_1.3.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.4B.2.4.3\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.3. + +###### 6.4B.2.4.3\_1.3.4 Test description + +###### 6.4B.2.4.3\_1.3.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.3.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.3.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.4 In-band Emissions for inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.4 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.3\_1.4.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.4B.2.4.3\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.3. + +###### 6.4B.2.4.3\_1.4.4 Test description + +###### 6.4B.2.4.3\_1.4.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.4.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.4.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.5 In-band Emissions for inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.5 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.3\_1.5.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.4B.2.4.3\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.5. + +###### 6.4B.2.4.3\_1.5.4 Test description + +###### 6.4B.2.4.3\_1.5.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.5.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.5.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.5.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.5.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.5.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.5.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.6 In-band Emissions for inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.6 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.3\_1.6.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.4B.2.4.3\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.3. + +###### 6.4B.2.4.3\_1.6.4 Test description + +###### 6.4B.2.4.3\_1.6.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.6.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.6.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.6.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.6.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.6.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.6.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.7 In-band Emissions for inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4A.2.3.7 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.3\_1.7.1 Test purpose + +Same test purpose as in clause 6.4.2.3 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.3\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.4B.2.4.3\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.4B.2.4.3.3. + +###### 6.4B.2.4.3\_1.7.4 Test description + +###### 6.4B.2.4.3\_1.7.4.1 Initial conditions + +Same test description as in clause 6.4A.2.3.7.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4A.2.3.7.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4A.2.3.7.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4A.2.3.7.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.3\_1.7.5 Test requirement + +Same test requirement as in clause 6.4A.2.3.7.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.4 EVM Equalizer Flatness for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4.2.4 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS. + +###### 6.4B.2.4.4.1 Test purpose + +Same test purpose as in clause 6.4.2.4 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.4B.2.4.4.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], TS 38.101-1 [2] and TS 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4.2.4.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.4.4 Test description + +###### 6.4B.2.4.4.4.1 Initial conditions + +Same test description as in clause 6.4.2.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4.2.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.4.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.4.5 Test requirement + +Same test requirement as in clause 6.4.2.4.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.4.D EVM Equalizer Flatness for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.4D.2.4 in TS 38.521-2 [9] is incomplete. +- Measurement Uncertainty and Test Tolerance are FFS and Annex F needs to be updated. + +###### 6.4B.2.4.4.D.1 Test purpose + +Same test purpose as in clause 6.4D.2.4.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.4.D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 and UL MIMO. + +###### 6.4B.2.4.4.D.3 Minimum conformance requirements + +For inter-band EN-DC including FR2 or both FR1 and FR2, transmit modulation quality for EN-DC operations in FR1 and FR2 as specified in TS 36.101 [5], TS 38.101-1 [2] and TS 38.101-2 [3] apply for E-UTRA, NR FR1 and NR FR2 respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4D.2.4.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.4D.4 Test description + +###### 6.4B.2.4.4D.4.1 Initial conditions + +Same test description as in clause 6.4D.2.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4D.2.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4D.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4D.2.4.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.4D.5 Test requirement + +Same test requirement as in clause 6.4D.2.4.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.4B.2.4.5 EVM spectral flatness for pi/2 BPSK modulation for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +**- The referred test case 6.4.2.5 in TS 38.521-2 [9] is incomplete.** + +###### 6.4B.2.4.5.1 Test purpose + +Same test purpose as in clause 6.4.2.5 in TS 38.521-2 [9] for the NR carrier. + +###### 6.4B.2.4.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.4B.2.4.5.3 Minimum conformance requirements + +Transmit modulation quality requirement for E-UTRA single carrier and CA operation specified in clauses 6.5.2 and 6.5.2A of TS 36.101 [4] and for NR single carrier, CA operation and UL-MIMO specified in clause 6.4.2, 6.4A.2 and 6.4D.2 of TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +Same minimum conformance requirements as in clause 6.4.2.5.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.4B.2.4.5.4 Test description + +###### 6.4B.2.4.5.4.1 Initial conditions + +Same test description as in clause 6.4.2.5.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.4.2.5.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.2.4.5.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.4.2.5.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.4B.2.4.5.5 Test requirement + +Same test requirement as in clause 6.4.2.5.5 in TS 38.521-2 [9] for the NR carrier. + +## 6.4E Transmit signal quality for V2X operation in FR1 + +### 6.4E.1 Frequency error for V2X + +#### 6.4E.1.0 Minimum conformance requirements + +For intra-band V2X operating UE, the requirement shall apply on each component carrier as defined in clause 6.5.1G in TS 36.101 [5] and in clause 6.4E.1 in TS 38.101-1 [2], respectively. + +For the inter-band concurrent NR V2X operation, the requirements specified in subclause 6.4.1 of TS 36.101 [5] shall apply for the E-UTRA uplink in licensed band and the requirements specified in subclause 6.4E.1 of TS 38.101-1 [2] shall apply for the sidelink in NR Band n47. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4E.1. + +#### 6.4E.1.1 Frequency error for Intra-band V2X + +##### 6.4E.1.1.1 Test purpose + +This test verifies the ability of both, the receiver and the transmitter, to process frequency correctly. + +Receiver: to extract the correct frequency from the stimulus signal, offered by the System simulator, under ideal propagation conditions and low level. + +Transmitter: to derive the correct modulated carrier frequency from the results, gained by the receiver. + +##### 6.4E.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.4E.1.0. The requirements in this test case can be well covered in clause 6.5.1G of TS 36.521-1 [10] and clause 6.4E.1 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.4E.1.2 Frequency error for Inter-band V2X + +##### 6.4E.1.2.1 Test purpose + +Same test purpose as in clause 6.4E.1 in TS 38.521-1 [8]. + +##### 6.4E.1.2.2 Test applicability + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.5.1 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.4E.1.1 of TS 38.521-1 [8] and don't need to be tested again. + +### 6.4E.2 Transmit modulation quality for V2X + +#### 6.4E.2.1 Error Vector Magnitude for V2X + +##### 6.4E.2.1.0 Minimum conformance requirements + +For intra-band V2X operating UE, the requirement shall apply on each SL transmission as defined in clause 6.5.2G.1 in TS 36.101 [5] and in clause 6.4E.2.1 in TS 38.101-1 [2], respectively. + +For the inter-band concurrent NR V2X operation, the requirements specified in subclause 6.5.2 of TS 36.101 [5] shall apply for the E-UTRA uplink in licensed band and the requirements specified in subclause 6.4E.2.1 of TS 38.101-1 [2] shall apply for the sidelink in NR Band n47. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4E.2.1.1. + +##### 6.4E.2.1.1 Error Vector Magnitude for intra-band V2X + +###### 6.4E.2.1.1.1 Test purpose + +Same test purpose as in clause 6.4E.2 in TS 38.521-1 [8]. + +###### 6.4E.2.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.4E.2.1.0. The requirements in this test case can be well covered in clause 6.5.2.1G of TS 36.521-1 [10] and clause 6.4E.2.1 of TS 38.521-1 [8] and don't need to be tested again. + +##### 6.4E.2.1.2 Error Vector Magnitude for Inter-band V2X + +###### 6.4E.2.1.2.1 Test purpose + +Same test purpose as in clause 6.4E.2 in TS 38.521-1 [8]. + +###### 6.4E.2.1.2.2 Test applicability + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.5.2.1 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.4E.2.2.1 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.4E.2.2 Carrier leakage for V2X + +##### 6.4E.2.2.0 Minimum conformance requirements + +For intra-band V2X operating UE, the requirement shall apply on each SL transmission as defined in clause 6.5.2G.2 in TS 36.101 [5] and in clause 6.4E.2.2 in TS 38.101-1 [2], respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4E.2.2.2. + +##### 6.4E.2.2.1 Carrier leakage for intra-band V2X + +###### 6.4E.2.2.1.1 Test purpose + +Same test purpose as in clause 6.4E.2.3.1 in TS 38.521-1 [8]. + +###### 6.4E.2.2.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.2E.1.0. The requirements in this test case can be well covered in clause 6.5.2.2G of TS 36.521-1 [10] and clause 6.4E.2.3 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.4E.2.3 In-band emissions for V2X + +##### 6.4E.2.3.0 Minimum conformance requirements + +For intra-band V2X operating UE, the requirement shall apply on each SL transmission as defined in clause 6.5.2G.3 in TS 36.101 [5] and in clause 6.4E.2.3 in TS 38.101-1 [2], respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4E.2.2.3. + +##### 6.4E.2.3.1 In-band emissions for intra-band V2X + +###### 6.4E.2.3.1.1 Test purpose + +Same test purpose as in clause 6.4E.2.4.1 in TS 38.521-1 [8]. + +###### 6.4E.2.3.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.2E.1.0. The requirements in this test case can be well covered in clause 6.5.2.3G of TS 36.521-1 [10] and clause 6.4E.2.4 of TS 38.521-1 [8] and don't need to be tested again. + +## 6.5 Output RF spectrum emissions + +## 6.5A Output RF spectrum emissions for CA + +### 6.5A.1 Occupied bandwidth for CA without EN-DC + +#### 6.5A.1.1 Test purpose + +Same test purpose as in clause 6.5.1 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.5.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +#### 6.5A.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for occupied bandwidth apply and are tested in TS 38.521-1 [8] clauses 6.5 and 6.5A and TS 38.521-2 [9] clauses 6.5 and 6.5A. + +### 6.5A.2 Out-of-band emissions for CA without EN-DC + +#### 6.5A.2.1 Spectrum emissions mask for CA without EN-DC + +##### 6.5A.2.1.1 Test purpose + +Same test purpose as in clause 6.5.2.2 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.5.2.1 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.5A.2.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for additional spectrum emissions mask apply and are tested in TS 38.521-1 [8] clauses 6.5 and 6.5A and TS 38.521-2 [9] clauses 6.5 and 6.5A. + +#### 6.5A.2.2 Additional Spectrum emissions mask for CA without EN-DC + +##### 6.5A.2.2.1 Test purpose + +Same test purpose as in clause 6.5.2.3 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.5.2.2 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.5A.2.2.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for additional spectrum emissions mask apply and are tested in TS 38.521-1 [8] clauses 6.5 and 6.5A and TS 38.521-2 [9] clauses 6.5 and 6.5A. + +#### 6.5A.2.3 Adjacent channel leakage ratio for CA without EN-DC + +No test case details specified as there are no exception requirements applicable to NR FR1 or NR FR2 as per TS 38.101-3 [4], clause 6.5A.2. The NR/5GC requirement for ACLR applies and is tested in TS 38.521-1 [8] and TS 38.521-2 [9] for FR1 and FR2 respectively. + +### 6.5A.3 Spurious emissions for CA without EN-DC + +#### 6.5A.3.1 Inter-band CA between FR1 and FR2 + +##### 6.5A.3.1.1 Test purpose + +Same test purpose as in clause 6.5.3 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.5.3 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 6.5A.3.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for spurious emission for inter-band CA between FR1 and FR2 and UE co-existence requirements apply for each component carrier and are tested in TS 38.521-1 [8] clauses 6.5 and 6.5A and TS 38.521-2 [9] clauses 6.5 and 6.5A. + +## 6.5B Output RF spectrum emissions for DC + +### 6.5B.1 Occupied bandwidth for EN-DC + +#### 6.5B.1.1 Occupied bandwidth for Intra-Band Contiguous EN-DC + +**Editor's note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- measurement uncertainty for ENBW > 100 MHz is FFS. + +##### 6.5B.1.1.1 Test purpose + +To verify that the UE occupied bandwidth for intra-band contiguous EN-DC for all transmission bandwidth configurations supported by the UE are less than their specific limits. + +##### 6.5B.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +##### 6.5B.1.1.3 Minimum conformance requirements + +For intra-band contiguous EN-DC, the occupied bandwidth is a measure of the bandwidth containing the 99% of the total integrated power of the transmitted spectrum. The OBW shall be less than the aggregated channel bandwidth for EN-DC, denoted as EN-BW in clause 5.3B. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.5B.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 6.5B.1.1.4 Test description + +###### 6.5B.1.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.5B.1.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.1.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|------------------------------------------------------------------------|----------------------------------|----------------------------|------------------------|-----------------|------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | All | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | | | +| Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | +| 1 | N/A for OBW testing. | QPSK | Outer_Full | CP-OFDM
QPSK | Outer_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521-1 [10] Table 5.4.2-1. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.1.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.5B.1.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level. +3. Measure the power spectrum distribution over all EN-DC component carriers in the EN-DC within two times or more range over the requirement for Occupied Bandwidth specification for intra-band contiguous EN-DC centring on the current carrier frequency in the EN-DC configuration. The characteristics of the filter shall be approximately Gaussian (typical spectrum analyser filter). Other methods to measure the power spectrum distribution are allowed. The measuring duration is at least 1ms over consecutive active uplink slots. +4. Calculate the total power within the range of all frequencies measured in step 3 and save this value as "Total power". + +5. Sum up the power upward from the lower boundary of the measured frequency range in step 3 and seek the limit frequency point by which this sum becomes 0.5% of "Total power" and save this point as "Lower Frequency". +6. Sum up the power downward from the upper boundary of the measured frequency range in step 3 and seek the limit frequency point by which this sum becomes 0.5% of "Total power" and save this point as "Upper Frequency". +7. Calculate the difference "Upper Frequency" – "Lower Frequency" = "Occupied Bandwidth" between the two limit frequencies obtained in step 5 and step 6. + +###### 6.5B.1.1.4.3 Message contents + +Message contents are according to TS 36.508 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.5B.1.1.4.3-1: *RRConnectionReconfiguration: nr-Config-r15*** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +**Table 6.5B.1.1.4.3-2: *PhysicalCellGroupConfig*** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +**Table 6.5B.1.1.4.3-4: *SystemInformationBlockType1: tdd-Config if operating on TDD band*** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +##### 6.5B.1.1.5 Test requirements + +The measured Occupied Bandwidth shall not exceed values of aggregated channel bandwidth as defined in clause 5.3B.1.2 for intra-band contiguous EN-DC. + +#### 6.5B.1.2 Occupied bandwidth for Intra-Band Non-Contiguous EN-DC + +##### 6.5B.1.2.1 Test purpose + +Same test purpose as in clause 6.5.1.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.5B.1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.5B.1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.1.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.1.2.4 Test description + +Same test description as in clause 6.5.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 6.5B.1.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|--------------------------------------------------------------------------------------------------------|-----------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1.4.3 for cases with single E-UTRA carrier | Low with maxWgap (NR low – E-UTRA high) | +| Test Channel Bandwidths as specified in TS 38.508-1 [6] subclause 4.3.1.4.3 | All for NR;
Lowest for E-UTRA | + +For Initial conditions as in clause 6.5.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.5.1.4.2 in TS 38.521-1 [8]. + +##### 6.5B.1.2.5 Test requirement + +Same test requirement as in clause 6.5.1.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.5B.1.3 Occupied bandwidth for Inter-Band EN-DC within FR1 (1 NR CC) + +##### 6.5B.1.3.1 Test purpose + +Same test purpose as in clause 6.5.1.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.5B.1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +##### 6.5B.1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.1.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.1.3.4 Test description + +Same test description as in clause 6.5.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.1.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 6.5B.1.3.5 Test requirement + +Same test requirement as in clause 6.5.1.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.5B.1.4 Occupied bandwidth for Inter-Band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5.1 in TS 38.521-2 [9] is incomplete for some scenarios (band, bandwidth, power class etc...) as indicated in its editor's note. + +##### 6.5B.1.4.1 Test purpose + +Same test purpose as in clause 6.5.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.5B.1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.1.4.4 Test description + +###### 6.5B.1.4.4.1 Initial conditions + +Same test description as in clause 6.5.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.5.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.5B.1.4.5 Test requirement + +Same test requirement as in clause 6.5.1.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.5B.1.4\_1 Occupied bandwidth for Inter-band EN-DC including FR2 (>1 NR CC) + +**Editor's note:** Test applicability, Test Description in below sub-clauses requires updates to clarify number of E-UTRA carriers that will be configured during the test that will be limited to only 1 E-UTRA CC + +##### 6.5B.1.4\_1.1 Occupied bandwidth for Inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.1.1 in TS 38.521-2 [9] is incomplete for some scenarios (band, aggregated bandwidth, CA configuration, power class etc...) as indicated in its editor's note. + +###### 6.5B.1.4\_1.1.1 Test purpose + +Same test purpose as in clause 6.5.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.1.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.1.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.1. + +###### 6.5B.1.4\_1.1.4 Test description + +###### 6.5B.1.4\_1.1.4.1 Initial condition + +Same test description as in clause 6.5A.1.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.1.4\_1.1.5 Test Requirements + +Same test requirement as in clause 6.5A.1.1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.1.4\_1.2 Occupied bandwidth for Inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.1.2 in TS 38.521-2 [9] is incomplete for some scenarios (band, aggregated bandwidth, CA configuration, power class etc...) as indicated in its editor's note. + +###### 6.5B.1.4\_1.2.1 Test purpose + +Same test purpose as in clause 6.5.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.1.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.5B.1.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.1. + +###### 6.5B.1.4\_1.2.4 Test description + +###### 6.5B.1.4\_1.2.4.1 Initial condition + +Same test description as in clause 6.5A.1.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.1.4\_1.2.5 Test Requirements + +Same test requirement as in clause 6.5A.1.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.1.4\_1.3 Occupied bandwidth for Inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.1.1 in TS 38.521-2 [9] is incomplete for some scenarios (band, aggregated bandwidth, CA configuration, power class etc...) as indicated in its editor's note. + +###### 6.5B.1.4\_1.3.1 Test purpose + +Same test purpose as in clause 6.5.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.1.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.5B.1.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.1. + +###### 6.5B.1.4\_1.3.4 Test description + +###### 6.5B.1.4\_1.3.4.1 Initial condition + +Same test description as in clause 6.5A.1.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.1.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.1.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.1.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.1.4\_1.3.5 Test Requirements + +Same test requirement as in clause 6.5A.1.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.5B.1.4D Occupied bandwidth for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5D.1 in TS 38.521-2 [9] is incomplete + +##### 6.5B.1.4D.1 Test purpose + +Same test purpose as in clause 6.5D.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.1.4D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 UL CCs. + +##### 6.5B.1.4D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5D.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.1.4D.4 Test description + +###### 6.5B.1.4D.4.1 Initial conditions + +Same test description as in clause 6.5D.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.5D.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5D.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5D.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.5B.1.4D.5 Test requirement + +Same test requirement as in clause 6.5D.1.5 in TS 38.521-2 [9] for the NR carrier. + +### 6.5B.2 Out-of-band emissions for EN-DC + +#### 6.5B.2.1 Out-of-band emissions for Intra-band contiguous EN-DC + +##### 6.5B.2.1.1 Spectrum emissions mask for intra-band contiguous EN-DC + +###### 6.5B.2.1.1.1 Test purpose + +To verify that the power of any UE emissions shall not exceed specified level for the specified aggregated bandwidth for the EN-DC intra-band contiguous. + +###### 6.5B.2.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.5B.2.1.1.3 Minimum conformance requirements + +The general spectrum emission for intra-band contiguous EN-DC is specified in Table 6.5B.2.1.1.3-1. + +**Table 6.5B.2.1.1.3-1: General spectrum emission mask for intra-band contiguous EN-DC** + +| $\Delta f_{\text{oob}}$ (MHz) | Spectrum emission limit (dBm) | Measurement bandwidth | +|-------------------------------------|------------------------------------------------------------------|-----------------------| +| $\pm 0 - 1$ | $\text{Max}(\text{Round}(10 \cdot \log(0.15/\text{ENBW})), -24)$ | 30 kHz | +| $\pm 1 - 5$ | -10 | 1 MHz | +| $\pm 5 - \text{ENBW}$ | -13 | 1 MHz | +| $\pm \text{ENBW} - (\text{ENBW}+5)$ | -25 | 1 MHz | + +NOTE: ENBW refers to the aggregated channel bandwidth in MHz as defined in clause 5.3B. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.5B.2.1.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.5B.2.1.1.4 Test description + +###### 6.5B.2.1.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 6.5B.2.1.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.2.1.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | | | +|------------------------------------------------------------------------|---------|---------|---------|------------------------|-------------------------------------------------------------------|------------------------|----------------------|------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | | | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | | | | | Low range, High range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | | | | | Lowest N RB_agg , Highest N RB_agg (Note 2) | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | | | | | Lowest, Highest (NOTE 10) | | | | | +| Test Parameters | | | | | | | | | | +| Test ID | Freq | ChBw | SCS | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | | | | E-UTRA Cell | | NR Cell | | Common | +| | | | | | Modulation | RB allocation (Note 5) | Modulation | RB allocation (NOTE 1) | Power config (NOTE 8) | +| 1 | Default | Default | Default | N/A | 16QAM | Outer_Full | DFT-s-OFDM Pi/2 BPSK | Outer_Full | B | +| 2 (Note 3) | Default | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | B | +| 3 (Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 4 (Note 3) | High | | | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | A | +| 5 (Note 4) | Default | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | B | +| 6 (Note 4) | Low | | | | 16QAM | N/A | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | A | +| 7 (Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM Pi/2 BPSK | N/A | A | +| 8 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM QPSK | Outer_Full | B | +| 9 (Note 3) | Default | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | Edge_1RB_Right | B | +| 10 (Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | N/A | A | +| 11 (Note 3) | High | | | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Right | A | +| 12 (Note 4) | Default | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | Edge_1RB_Left | B | +| 13 (Note 4) | Low | | | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Left | A | +| 14 (Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | N/A | A | +| 15 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 16QAM | Outer_Full | B | +| 16 (Note 3) | Default | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | Edge_1RB_Right | B | +| 17 (Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 16QAM | N/A | A | + +| | | | | | | | | | | +|----------------|---------|--|--|--|-------|-----------------|-------------------|----------------|---| +| 18
(Note 3) | High | | | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Right | A | +| 19
(Note 4) | Default | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | Edge_1RB_Left | B | +| 20
(Note 4) | Low | | | | 16QAM | N/A | DFT-s-OFDM 16QAM | Edge_1RB_Left | A | +| 21
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 16QAM | N/A | A | +| 22 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 64QAM | Outer_Full | B | +| 23
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 64QAM | Edge_1RB_Right | B | +| 24
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 64QAM | Edge_1RB_Left | B | +| 25 | Default | | | | 16QAM | Outer_Full | DFT-s-OFDM 256QAM | Outer_Full | B | +| 26
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | DFT-s-OFDM 256QAM | Edge_1RB_Right | B | +| 27
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | DFT-s-OFDM 256QAM | Edge_1RB_Left | B | +| 28 | Default | | | | 16QAM | Outer_Full | CP-OFDM QPSK | Outer_Full | B | +| 29
(Note 3) | Default | | | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Right | B | +| 30
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM QPSK | N/A | A | +| 31
(Note 3) | High | | | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Right | A | +| 32
(Note 4) | Default | | | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | Edge_1RB_Left | B | +| 33
(Note 4) | Low | | | | 16QAM | N/A | CP-OFDM QPSK | Edge_1RB_Left | A | +| 34
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM QPSK | N/A | A | +| 35 | Default | | | | 16QAM | Outer_Full | CP-OFDM 16QAM | Outer_Full | B | +| 36
(Note 3) | Default | | | | 16QAM | Outer_1RB_Left | CP-OFDM 16QAM | Edge_1RB_Right | B | +| 37
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM 16QAM | N/A | A | +| 38
(Note 3) | High | | | | 16QAM | N/A | CP-OFDM 16QAM | Edge_1RB_Right | A | +| 39
(Note 4) | Default | | | | 16QAM | Outer_1RB_Right | CP-OFDM 16QAM | Edge_1RB_Left | B | +| 40
(Note 4) | Low | | | | 16QAM | N/A | CP-OFDM 16QAM | Edge_1RB_Left | A | + +| | | | | | | | | | | +|----------------|---------|--|--|--|-------|-----------------|-------------------|----------------|---| +| 41
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM
16QAM | N/A | A | +| 42 | Default | | | | 16QAM | Outer_Full | CP-OFDM
64QAM | Outer_Full | B | +| 43
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM
64QAM | Edge_1RB_Right | B | +| 44
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM
64QAM | Edge_1RB_Left | B | +| 45 | Default | | | | 16QAM | Outer_Full | CP-OFDM
256QAM | Outer_Full | B | +| 46
(Note 3) | Low | | | | 16QAM | Outer_1RB_Left | CP-OFDM
256QAM | Edge_1RB_Right | B | +| 47
(Note 4) | High | | | | 16QAM | Outer_1RB_Right | CP-OFDM
256QAM | Edge_1RB_Left | B | +| 48
(Note 4) | Default | | | | 16QAM | Edge_Full_Right | CP-OFDM
256QAM | Edge_Full_Left | B | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same $N_{RB\_agg}$ , select the combination to test as follows: + +- Lowest ENBW: NR component with lowest $N_{RB}$ is tested. +- Highest ENBW: NR component with highest $N_{RB}$ is tested. + +NOTE 3: Applicable when E-UTRA cell carrier frequency is lower than NR cell carrier. + +NOTE 4: Applicable when NR cell carrier frequency is lower than E-UTRA cell carrier. + +NOTE 5: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. Edge\_Full\_Right is defined as 2 RBs allocated at the right edge of the E-UTRA component. + +NOTE 6: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in FR1 + +NOTE 7: Power config as specified in Table 6.5B.2.1.2.4.3-3 (PC3) or 6.5B.2.1.2.4.3-4 (PC2). + +NOTE 8: All test points in this table must also exist in table 6.2B.2.1.4.1-1 (MPR). + +NOTE 9: Test IDs with simultaneous E-UTRA and NR UL transmission only apply for UEs indicating dualPA-Architecture. + +NOTE 10: For DC\_(n)71AA, only NR SCS of 15 kHz is tested. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.2.1.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.2.1.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5B.2.1.1.4.1-1 on E-UTRA CC and NR CC + +respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command for the UE to reach $P_{UMAX}$ level. +3. For a UE supporting dynamic power sharing, measure the mean power over all component carriers. For a UE not supporting dynamic power sharing, measure the power of each component carrier individually. The measured transmitted power shall meet the requirements in clause 6.2B.2.1.5. The period of measurement shall be at least the continuous duration of 1ms over consecutive active uplink slots For TDD, only slots consisting of only UL symbols are under test. +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5B.2.1.1.5-1 and using a rms detector. The centre frequency of the filter shall be stepped in continuous steps according to the same table. The measured power shall be recorded for each step. The measurement period shall capture the active TSs. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.5B.2.1.1.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.5B.2.1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1 with the following exceptions: + +**Table 6.5B.2.1.1.4.3-1: AdditionalSpectrumEmission for MCG** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.4.3.3-1 | | | | +|------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 0 (NS_01) | | | + +**Table 6.5B.2.1.1.4.3-2: AdditionalSpectrumEmission for SCG** + +| Derivation Path: 38.508-1 [5] clause 4.6.3, Table 4.6.3-1 | | | | +|-----------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| AdditionalSpectrumEmission | 0 (NS_01) | | | + +**Table 6.5B.2.1.1.4.3-3: PhysicalCellGroupConfig for PC3** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|----------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. | | | | +| NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.1.4.3-4: RRCConnectionReconfiguration: nr-Config-r15 for PC3** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.1.4.3-5: PhysicalCellGroupConfig for PC2** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.1.4.3-6: RRCConnectionReconfiguration: nr-Config-r15 for PC2** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time.
NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.1.4.3-7: RRCConnectionReconfiguration: tdm-PatternConfig if operating on FDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|----------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| tdm-PatternConfig-r15 ::= CHOICE{ | | | Power config A (NOTE 1) | +| setup ::= SEQUENCE { | | Apply if operating on FDD band for a UE NOT indicating support of dynamicPowerSharing in the UE-MRDC-Capability IE according to TS 38.213 [x] clause 7.6.1 | | +| subframeAssignment-r15 | sa2 | | | +| harq-Offset-r15 | 0 | | | +| } | | | | +| } | | | | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.1.4.3-8: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +###### 6.5B.2.1.1.5 Test requirements + +The power of any UE emissions shall fulfil requirements in Table 6.5B.2.1.1.5-1. + +**Table 6.5B.2.1.1.5-1: General spectrum emission mask for intra-band contiguous EN-DC** + +| $\Delta f_{\text{foob}}$ (MHz) | Spectrum emission limit (dBm) | Measurement bandwidth | +|-----------------------------------------------------------------------------------------|------------------------------------|-----------------------| +| $\pm 0 - 1$ | Max(Round(10*log(0.15/ENBW)), -24) | 30 kHz | +| $\pm 1 - 5$ | -10 + TT | 1 MHz | +| $\pm 5 - \text{ENBW}$ | -13 + TT | 1 MHz | +| $\pm \text{ENBW} - (\text{ENBW}+5)$ | -25 + TT | 1 MHz | +| NOTE: ENBW refers to the aggregated channel bandwidth in MHz as defined in clause 5.3B. | | | + +**Table 6.5B.2.1.1.5-2: Test Tolerance (Spectrum Emission Mask)** + +| $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | +|------------------------|----------------------------------------|----------------------------------------| +| 1.5 dB | 1.8 dB | 1.8 dB | + +##### 6.5B.2.1.2 Additional spectrum emissions mask for intra-band contiguous EN-DC + +###### 6.5B.2.1.2.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions under the deployment scenarios where additional requirements are specified. + +###### 6.5B.2.1.2.2 Test applicability + +This test case applies to all types of E-UTRA power class 3 and power class 2 UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.5B.2.1.2.3 Minimum conformance requirements + +###### 6.5B.2.1.2.3.1 Minimum requirement for network signalled value "NS\_35" + +For contiguous intra-band EN-DC configuration of DC\_(n)71AA when NS\_35 is indicated for the UE the requirements in table 6.5B.2.1.2.3-1 apply in the frequency ranges immediately adjacent and outside the aggregation of the said sub-blocks + +When NS\_35 is indicated in the MCG and NS\_35 is indicated in the SCG the requirements in table 6.5B.2.1.2.3.1-1 apply in the frequency ranges immediately adjacent and outside the aggregated sub-blocks of the EN-DC configuration for DC\_(n)71AA. + +**Table 6.5B.2.1.2.3.1-1: Additional requirements** + +| | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (dBm) | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|---------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.085 \text{ MHz}$ | -13 | 30 kHz | +| $0.1 \text{ MHz} \leq \Delta f < \text{ENBW}$ | $0.15 \text{ MHz} \leq f\_offset < \text{ENBW} - 0.05 \text{ MHz}$ | -13 | 100 kHz | +| $\text{ENBW} \leq \Delta f < \text{ENBW} + 5 \text{ MHz}$ | $\text{ENBW} + 0.5 \text{ MHz} \leq f\_offset < \text{ENBW} + 4.5 \text{ MHz}$ | -25 | 1 MHz | +| NOTE: ENBW is the aggregated bandwidth of an E-UTRA sub-block and an adjacent NR sub-block; there is no frequency separation between the said sub-blocks. The sub-block bandwidths include any internal guard bands. | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.1.2.1. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA overlap in time with NR.LTE and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +Exception requirements for both NR and E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that doesn't support dynamic power sharing. LTE anchor agnostic approach is not applied for this case. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +No exception requirements for NR or E-UTRA are defined for this test when transmission on E-UTRA doesn't overlap in time with NR, for a UE that supports dynamic power sharing. LTE anchor agnostic approach is not applied for this case. + +###### **6.5B.2.1.2.3.2 Minimum requirement for network signalled value "NS\_04"** + +Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. + +The Band 41/n41 SEM transition point from -13 dBm/MHz to -25 dBm/MHz is based on the emission bandwidth. The emission bandwidth is defined as the width of the signal between two points, one below the carrier centre frequency and one above the carrier centre frequency, outside of which all emissions are attenuated at least 26 dB below the transmitter power. Since the 26 dB emission bandwidth is implementation dependent, the transmission bandwidths occupied by RBs is used for the SEM. The emission bandwidth for LTE carriers is document in TS 36.101 [5], and the emission bandwidth for NR carriers is documented in TS 38.101-1 [2]. The total emission bandwidth for contiguous intra-band EN-DC is the sum of the emission bandwidth for each CC plus the guard band between contiguous CCs. + +When "NS\_04" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5B.2.1.2.3.2-1. + +**Table 6.5B.2.1.2.3.2-1: n41 SEM with NS\_04** + +| $\Delta f_{\text{OOB}}$ MHz | Spectrum emission limit (dBm)/ measurement bandwidth for each channel bandwidth | | | | | | Measurement bandwidth | +|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|--------|--------|--------|--------|----------|-----------------------| +| | 10 MHz | 15 MHz | 20 MHz | 40 MHz | 50 MHz | > 50 MHz | | +| $\pm 0 - 1$ | -18 | -20 | -21 | -24 | -25 | | 30 kHz | +| $\pm 1 - 5$ | | | -10 | | | | 1 MHz | +| $\pm 5 - X$ | | | -13 | | | | | +| $\pm X - (\text{BWChannel} + 5 \text{ MHz})$ | | | -25 | | | | | +| NOTE 1: X is defined as the sum of the emission bandwidth of the component carriers plus the guard band between contiguous CCs. | | | | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.1.2.2. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.5B.2.1.2.4 Test description + +###### 6.5B.2.1.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in test configuration table 6.2B.3.1.4.1-1 through 6.2B.3.1.4.1-2. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +Table 6.5B.2.1.2.4.1-0: E-UTRA test configuration table + +| E-UTRA Test Parameters | | | | | | +|--------------------------------------------------------------------------|-----------------------------------|------------------------|------------|---------------|--| +| E-UTRA Channel Bandwidth | E-UTRA Test Frequency (Note 1) | Downlink | Uplink | | | +| | | N/A for A-MPR testing. | Modulation | RB allocation | | +| 20 MHz | Low range and High range (Note 2) | | QPSK | 100 | | +| NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [6] clause 4.3.1 | | | | | | +| NOTE 2: NR carrier shall be the outermost carrier during test. | | | | | | + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.2.1 for SS diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. NR downlink signals are initially set up according to Annex C.0, C.1, and C.2 and uplink signals according to Annex G.0, G.1, G.2, and G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG link and NR CG link respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG link and NR CG link respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.5B.2.1.2.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.2.1.2.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 6.2B.3.1.4.1-1 on both EN-DC component carriers. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command starting from the first TPC command in this step for the UE to reach $P_{UMAX}$ level. +3. Measure the mean power over all component carriers for the EN-DC configuration, which shall meet the requirements described in table 6.5B.2.1.2.5.1-1 through to 6.5B.2.1.2.5.2-1. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to table 6.5B.2.1.2.5-1 through to 6.5B.2.1.2.5.2-1 and using a rms detector. The centre frequency of the filter shall be stepped in contiguous steps according to the same table. The measured power shall be recorded for each step. The measurement period shall capture the active time slots. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.2B.3.1.4.1-2, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.5B.2.1.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1, with the following exceptions. + +**Table 6.5B.2.1.2.4.3-1: PhysicalCellGroupConfig for PC3** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|----------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. | | | | +| NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.2.4.3-1: RRCConnectionReconfiguration: nr-Config-r15 for PC3** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|----------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power config A (NOTE 1) | +| | 20 | | Power config B (NOTE 2) | +| P-Max | 23 | | | +| | 20 | | | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. | | | | +| NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.2.4.3-3: PhysicalCellGroupConfig for PC2** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|----------------------------------------------------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | +| NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. | | | | +| NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. | | | | + +**Table 6.5B.2.1.2.4.3-4: RRCConnectionReconfiguration: nr-Config-r15 for PC2** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 26 | | Power config A (NOTE 1) | +| | 23 | | Power config B (NOTE 2) | + +NOTE 1: Applies when E-UTRA UL transmission not overlapping with NR UL transmission in time. +NOTE 2: Applies when E-UTRA UL transmission overlapping with NR UL transmission in time. + +**Table 6.5B.2.1.2.4.3-5: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +6.5B.2.1.2.4.3.1 Message contents exceptions for network signalled value "NS\_35" + +For "NS\_35" see A-MPR test case in table 6.2B.3.1.4.3.2-1 and table 6.2B.3.1.4.3.2-2. + +6.5B.2.1.2.4.3.2 Message contents exceptions for network signalled value "NS\_04" + +For "NS\_04" see A-MPR test case in table 6.2B.3.1.4.3.1-1 and table 6.2B.3.1.4.3.1-2. + +6.5B.2.1.2.5 Test requirement + +**6.5B.2.1.2.5-1: Test Tolerance (Additional Spectrum Emission Mask)** + +| $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 4.2\text{GHz}$ | $4.2\text{GHz} < f \leq 6.0\text{GHz}$ | +|------------------------|----------------------------------------|----------------------------------------| +| 1.5 dB | 1.8 dB | 1.8 dB | + +6.5B.2.1.2.5.1 Test requirement for network signalled value "NS\_35" + +When "NS\_35" is indicated in the cell measured UE mean power in the channel bandwidth, derived in step 3, shall fulfil requirements in table 6.2B.3.1.5.1-1, and the power of any UE shall not exceed the described values in table 6.5B.2.1.2.5.1-1. The requirements in the table apply in the frequency ranges immediately adjacent and outside the aggregation of the sub-blocks. + +**Table 6.5B.2.1.2.5.1-1: Additional requirements for "NS\_35"** + +| $\Delta f_{\text{foob}}$ | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Minimum requirement [dBm] | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|---------------------------|-----------------------| +| $0\text{ MHz} \leq \Delta f < 0.1\text{ MHz}$ | $0.015\text{ MHz} \leq f_{\text{offset}} < 0.085\text{ MHz}$ | -13+TT | 30 kHz | +| $0.1\text{ MHz} \leq \Delta f < \text{ENBW}$ | $0.15\text{ MHz} \leq f_{\text{offset}} < \text{ENBW} - 0.05\text{ MHz}$ | -13+TT | 100 kHz | +| $\text{ENBW} \leq \Delta f < \text{ENBW} + 5\text{ MHz}$ | $\text{ENBW} + 0.5\text{ MHz} \leq f_{\text{offset}} < \text{ENBW} + 4.5\text{ MHz}$ | -25+TT | 1 MHz | +| NOTE: ENBW is the aggregated bandwidth of an E-UTRA sub-block and an adjacent NR sub-block; there is no frequency separation between the said sub-blocks. The sub-block bandwidths include any internal guard bands. | | | | + +6.5B.2.1.2.5.2 Test requirement for network signalled value "NS\_04" + +When "NS\_04" is indicated in the cell measured UE mean power in the channel bandwidth, derived in step 3, shall fulfil requirements in tables 6.2B.3.1.5.2-1, and the power of any UE shall not exceed the described values in table + +6.5B.2.1.2.5.2-1. The requirements in the table apply in the frequency ranges immediately adjacent and outside the aggregation of the sub-blocks. + +**Table 6.5B.2.1.2.5.2-1: Additional requirements for n41 SEM with NS\_04** + +| $\Delta f_{\text{foob}}$
MHz | Spectrum emission limit (dBm)/ measurement bandwidth
for each channel bandwidth | | | | | | Measurement
bandwidth | | | | +|----------------------------------------------|------------------------------------------------------------------------------------|-----------|-----------|-----------|-----------|-------------|--------------------------|--|--|--| +| | 10
MHz | 15
MHz | 20
MHz | 40
MHz | 50
MHz | > 50
MHz | | | | | +| $\pm 0 - 1$ | -18+TT | -20+TT | -21+TT | -24+TT | -25+TT | | 30 kHz | | | | +| $\pm 1 - 5$ | -10+TT | | | | | | 1 MHz | | | | +| $\pm 5 - X$ | -13+TT | | | | | | | | | | +| $\pm X - (\text{BWChannel} + 5 \text{ MHz})$ | -25+TT | | | | | | | | | | + +NOTE 1: X is defined as the sum of the emission bandwidth of the component carriers plus the guard band between contiguous CCs. + +##### 6.5B.2.1.3 Adjacent channel leakage ratio for intra-band contiguous EN-DC + +###### 6.5B.2.1.3.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to adjacent channels in terms of Adjacent Channel Leakage Power Ratio (ACLR). + +###### 6.5B.2.1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.5B.2.1.3.3 Minimum conformance requirements + +For EN-DC operation with an E-UTRA sub-block immediately adjacent to an NR sub-block, the ACLR is defined as the ratio of the filtered mean power centred on the aggregated sub-block bandwidth ENBW to the filtered mean power centred on an adjacent bandwidth of the same size ENBW at nominal channel spacing. The UE shall meet the ACLR minimum requirement EN-DCACLR specified in Table 6.5B.2.1.3.3-1 with ENBW the sum of the sub-block bandwidths. + +The assigned channel power and adjacent channel power are measured with rectangular filters with measurement bandwidths specified in 6.5B.2.1.3.3-1. + +**Table 6.5B.2.1.3.3-1: ACLR for intra-band EN-DC (contiguous sub-blocks)** + +| Parameter | Unit | Value | +|---------------------------------------------------------------------------------------------------|------|--------------------| +| EN-DC ACLR for PC3 | dBc | 30 | +| EN-DC ACLR for PC2 | dBc | 31 | +| Measurement bandwidth of EN-DC channel | | 1.00*ENBW | +| Measurement bandwidth of adjacent channel | | 0.95*ENBW | +| Frequency offset of adjacent channel | | ENBW
/
-ENBW | +| NOTE 1: ENBW is the aggregated bandwidth in MHz as defined in clause 5.3B. | | | +| NOTE 2: The frequency offset is that in between the centre frequencies of the measurement filters | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.1.3. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.5B.2.1.3.4 Test description + +###### 6.5B.2.1.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in test configuration tables defined in section 6.2B.2.1.4.1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.5B.2.1.3.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.2.1.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to test configuration tables defined in section 6.2B.2.1.4.1 on both EN-DC component carriers. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200ms for the UE to reach $P_{UMAX}$ level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode according to the test configuration, which shall meet the requirements in clause 6.2B.2.1.5 as appropriate. The period of the measurement shall be at least the continuous duration of 1ms over consecutive active uplink slots. For TDD, only slots consisting of only UL symbols are under test. +4. Measure the filtered mean power of the transmitted signal centred on the aggregated sub-block ENBW with a measurement filter of bandwidth according to test configuration tables defined in section 6.2B.2.1.4.1 and using a rms detector. The period of the measurement shall be at least the continuous duration of 1ms over consecutive active uplink slots For TDD, only slots consisting of only UL symbols are under test. +5. Measure the filtered mean power of the first adjacent channel on both lower and upper side of the assigned NR + E-UTRA channel, respectively with a frequency offset and measurement filter of bandwidth according to test configuration tables defined in section 6.2B.2.1.4.1 and using a rms detector. + +- Calculate the ratios of the power between the values measured in step 4 over step 5 for lower and upper side respectively. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration tables defined in section 6.2B.2.1.4.1, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.5B.2.1.3.4.3 Message contents + +Same message contents as in clause 6.2B.2.1.4.3. + +###### 6.5B.2.1.3.5 Test requirement + +The measured adjacent channel power ratio, derived in step 6, shall be higher than the limits in Table 6.5B.2.1.3.5-1. + +**Table 6.5B.2.1.3.5-1: ACLR requirement for intra-band EN-DC (contiguous sub-blocks)** + +| | Power class 2 | Power class 3 | +|-------------------------------------------------------------------------------------------|---------------|---------------| +| NR ACLR | 31 - TT dBc | 30 - TT dBc | +| NOTE 1: TT for each frequency and channel bandwidth is specified in Table 6.5B.2.1.3.5-2. | | | + +**Table 6.5B.2.1.3.5-2: Test Tolerance** + +| | $f \leq 4.0\text{GHz}$ | $4.0\text{GHz} < f \leq 6.0\text{GHz}$ | +|-------------------------|------------------------|----------------------------------------| +| BW $\leq 100\text{MHz}$ | 0.8 dB | 1.0 dB | + +#### 6.5B.2.2 Out-of-band emissions for Intra-band non-contiguous EN-DC + +##### 6.5B.2.2.1 Spectrum emissions mask for intra-band non-contiguous EN-DC + +###### 6.5B.2.2.1.1 Test purpose + +To verify that the power of any UE emissions shall not exceed specified level for the specified channel bandwidth. + +###### 6.5B.2.2.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.5B.2.2.1.3 Minimum conformance requirements + +The spectral emission mask for intra-band non-contiguous EN-DC is a composite of the emission mask for each CC with the level set to the maximum value from each mask for each frequency outside of the transmission bandwidth of either carrier. A composite spectrum emission mask is a combination of individual CC spectrum emissions masks. Where two masks overlap the most relaxed limit is used. Composite spectrum emission mask applies to frequencies up to $\pm \Delta f_{\text{foob}}$ starting from the edges of the sub-blocks. If for some frequency an individual CC spectrum emission mask overlaps with the bandwidth of another CC then the emission mask does not apply for that frequency. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.2.1. + +The spectral emission mask for intra-band non-contiguous EN-DC is a composite of the emission mask for each CC with the level set to the maximum value from each mask and therefore LTE anchor agnostic approach is not applied. + +###### 6.5B.2.2.1.4 Test description + +###### 6.5B.2.2.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in TS 38.508-1 [6] clause 4.3.1.4.3, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in TS 38.508-1 [6] clause 4.3.1.4.3 and are shown in Table 6.5B.2.2.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.2.2.1.4.1-1: Test Configuration Table** + +| Initial Conditions and Test Parameters | | +|------------------------------------------------------------------------|--------| +| Same as defined in Table 6.2B.2.2.4.1-1 with the following exceptions. | | +| Test Environment as specified in TS 38.508-1 [5] subclause 4.1 | Normal | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.3.2.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.2.2.1.4.2 Test Procedure + +1. For NR carrier, SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5B.2.2.1.4.1-1. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. For E-UTRA carrier, SS sends uplink scheduling information via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.5B.2.2.1.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +3. Send continuously uplink power control "up" commands to the UE for NR and E-UTRA carrier until the UE transmits at its $P_{UMAX}$ level; allow at least 200 ms from the first TPC command starting in this step for the UE to reach $P_{UMAX}$ level. +4. For a UE supporting dynamic power sharing, measure the mean power over all component carriers. For a UE not supporting dynamic power sharing, measure the power of each component carrier individually. The measured transmitted power shall meet the requirements in clause 6.2B.2.2.5. The period of the measurement shall be at least the continuous duration of one active sub-frame (1ms). For TDD slots with transient periods are not under test. +5. Measure the power of the transmitted signal with a measurement filter of bandwidths according to clause 6.5B.2.2.1.5 and using a rms detector. The centre frequency of the filter shall be stepped in continuous steps according to the same table. The measured power shall be recorded for each step. The measurement period shall + +capture the active TSs. If for some frequency an individual CC spectrum emission mask overlaps with the bandwidth of another CC then the emission mask does not apply for that frequency. + +NOTE 1: When switching to DFT-s-OFDM waveform, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +###### 6.5B.2.2.1.4.3 Message Content + +Same message contents as in clause 6.2B.2.2.4.3. + +###### 6.5B.2.2.1.5 Test requirement + +-For NR carrier frequency masks not overlapping with E-UTRA carrier frequency masks, the power of any UE emission shall fulfil requirements in Table 6.5.2.2.5-1 defined in TS 38.521-1 [8]. + +-For E-UTRA carrier frequency masks not overlapping with NR carrier frequency masks, the power of any UE emission shall fulfil requirements in Table 6.6.2.1.5-1 or 6.6.2.1.5-2 in TS 36.521-1 [10], as applicable. + +-For NR carrier frequency masks overlapping with E-UTRA carrier frequency masks, the most relaxed limit is used between requirements in Table 6.5.2.2.5-1 defined in TS 38.521-1 [8] and Table 6.6.2.1.5-1 or 6.6.2.1.5-2 in TS 36.521-1 [10], as applicable. + +##### 6.5B.2.2.2 Additional Spectrum emissions mask for intra-band non-contiguous EN-DC + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- For $W_{gap} < \text{NR } \Delta f_{OOB} + \text{E-UTRA } \Delta f_{OOB}$ , test description and test requirements are FFS. + +###### 6.5B.2.2.2.1 Test purpose + +Same test purpose as in clause 6.5.2.3 in TS 38.521-1 [8] for the NR carrier. + +###### 6.5B.2.2.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.5B.2.2.2.3 Minimum conformance requirements + +The spectral emission mask for intra-band non-contiguous EN-DC is a composite of the emission mask for each CC with the level set to the maximum value from each mask for each frequency outside of the transmission bandwidth of either carrier. A composite spectrum emission mask is a combination of individual CC spectrum emissions masks. Where two masks overlap the most relaxed limit is used. Composite spectrum emission mask applies to frequencies up to $\pm \Delta f_{OOB}$ starting from the edges of the sub-blocks. If for some frequency an individual CC spectrum emission mask overlaps with the bandwidth of another CC then the emission mask does not apply for that frequency. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.2.2. + +No exception requirements applicable to NR or E-UTRA when $W_{gap} > \text{NR } \Delta f_{OOB} + \text{E-UTRA } \Delta f_{OOB}$ . LTE anchor agnostic approach is applied when $W_{gap} > \text{NR } \Delta f_{OOB} + \text{E-UTRA } \Delta f_{OOB}$ . + +Exception requirements for both NR and E-UTRA are defined for this test when $W_{gap} < \text{NR } \Delta f_{OOB} + \text{E-UTRA } \Delta f_{OOB}$ and therefore LTE anchor agnostic approach is not applied when $W_{gap} < \text{NR } \Delta f_{OOB} + \text{E-UTRA } \Delta f_{OOB}$ . + +###### 6.5B.2.2.2.4 Test description + +For $W_{gap} > \text{NR } \Delta f_{OOB} + \text{E-UTRA } \Delta f_{OOB}$ : + +Same test description as in clause 6.5.2.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.2.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.2.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.5.2.3.4.2 in TS 38.521-1 [8] with the following steps exception: + +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode according to the test configuration. The period of the measurement shall be at least the continuous duration of 1ms over consecutive active uplink slots. For TDD, only slots consisting of only UL symbols are under test. + +For $W_{gap} < NR \Delta f_{OOB} + E\text{-UTRA } \Delta f_{OOB}$ : + +FFS. + +###### 6.5B.2.2.2.4.3 Message Content + +Message contents are according to TS 36.508-1 [11] clause 4.6 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.5B.2.2.2.4.3-1: *RRConnectionReconfiguration: nr-Config-r15* when $W_{gap} < NR \Delta f_{OOB} + E\text{-UTRA } \Delta f_{OOB}$** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 6.5B.2.2.2.4.3-2: *PhysicalCellGroupConfig* when $W_{gap} < NR \Delta f_{OOB} + E\text{-UTRA } \Delta f_{OOB}$** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 6.5B.2.2.2.4.3-3: *SystemInformationBlockType1: tdd-Config* if E-UTRA on TDD band when $W_{gap} < NR \Delta f_{OOB} + E\text{-UTRA } \Delta f_{OOB}$** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT := SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | sa2 | | | +| specialSubframePatterns | ssp7 | | | +| } | | | | + +###### 6.5B.2.2.2.5 Test requirement + +For $W_{\text{gap}} > \text{NR } \Delta f_{\text{OOB}} + \text{E-UTRA } \Delta f_{\text{OOB}}$ : + +Power of any UE emission shall fulfil requirements in Table 6.5.2.3.5-1 defined in TS 38.521-1 [8] for the NR carrier. + +For $W_{\text{gap}} < \text{NR } \Delta f_{\text{OOB}} + \text{E-UTRA } \Delta f_{\text{OOB}}$ : + +FFS. + +##### 6.5B.2.2.3 Adjacent channel leakage ratio for intra-band non-contiguous EN-DC + +###### 6.5B.2.2.3.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to adjacent channels in terms of Adjacent Channel Leakage power Ratio (ACLR). + +###### 6.5B.2.2.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +###### 6.5B.2.2.3.3 Minimum conformance requirements + +For intra-band non-contiguous EN-DC, the EN-DC Adjacent Channel Leakage power Ratio (EN-DCACLR) is the ratio of the sum of the filtered mean powers centred on the assigned E-UTRA and NR sub-block frequencies to the filtered mean power centred on an adjacent channel frequency at nominal channel spacing. In case the sub-block gap bandwidth $W_{\text{gap}}$ is smaller than an E-UTRA or NR sub-block bandwidth, no EN-DCACLR requirement is set for the corresponding sub-block for the gap. The assigned EN-DC sub-block power and adjacent channel power are measured with rectangular filters with measurement bandwidths specified in TS 36.101 [5] for the E-UTRA sub-block, and TS 38.101-1 [2] for the NR sub-block. If the measured adjacent channel power is greater than $-50\text{dBm}$ then the EN-DCACLR shall be higher than the value specified in for E-UTRAACLR and NRACLR. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.2.3. + +Adjacent Channel Leakage power Ratio must be measured for both NR and E-UTRA and therefore LTE anchor agnostic approach is not applied. + +###### 6.5B.2.2.3.4 Test description + +###### 6.5B.2.2.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in TS 38.508-1 [6] clause 4.3.1.4.3, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in TS 38.508-1 [6] clause 4.3.1.4.3 and are shown in Table 6.5B.2.2.3.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.2.2.3.4.1-1: Test Configuration Table** + +| Initial Conditions and Test Parameters | +|-----------------------------------------| +| Same as defined in Table 6.2B.2.2.4.1-1 | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2.1 for UE diagram. + +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.3.2.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.2.2.3.4.2 Test Procedure + +1. For NR carrier, SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for *C\_RNTI* to schedule the UL RMC according to Table 6.5B.2.2.3.4.1-1. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. For E-UTRA carrier, SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for *C\_RNTI* to schedule the UL RMC according to Table 6.5B.2.2.3.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +3. Send continuously power control “up” commands to the UE for NR and E-UTRA until the UE transmits at $P_{\text{UMAX}}$ level. Allow at least 200ms for the UE to reach $P_{\text{UMAX}}$ level. +4. Measure the mean power of the UE in the channel bandwidth of the radio access mode according to the test configuration, which shall meet the requirements in clause 6.2B.2.2.5 as appropriate. The period of the measurement shall be at least the continuous duration of 1ms over consecutive active uplink slots. For TDD, only slots consisting of only UL symbols are under test. +5. Measure the rectangular filtered mean power for the assigned NR channel using a rms detector. +6. Measure the rectangular filtered mean power of the first NR adjacent channel on both lower and upper side of the assigned NR channel using a rms detector, respectively. Skip the measurement within the $W_{\text{gap}}$ in case $W_{\text{gap}} < \text{NR sub-block bandwidth}$ . +7. Calculate the ratios of the power between the values measured in step 4 over step 5 for lower and upper NR $ACL_{\text{R}}$ , respectively. +8. Measure the rectangular filtered mean power for E-UTRA channel using a rms detector. +9. Measure the rectangular filtered mean power of the first E-UTRA adjacent channel on both lower and upper side of the E-UTRA channel using a rms detector, respectively. Skip the measurement within the $W_{\text{gap}}$ in case $W_{\text{gap}} < \text{E-UTRA sub-block bandwidth}$ . +10. Calculate the ratios of the power between the values measured in step 7 over step 8 for lower and upper E-UTRA $ACL_{\text{R}}$ , respectively. + +NOTE 1: When switching to DFT-s-OFDM waveform, send an NR RRCReconfiguration message according to TS 38.508-1 [6] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with *TRANSFORM\_PRECODER\_ENABLED* condition. + +###### 6.5B.2.2.3.4.3 Message Content + +Same message contents as in clause 6.2B.2.2.4.3. + +###### 6.5B.2.2.3.5 Test requirement + +For NR ACLR, if the measured adjacent channel power is greater than –50 dBm then the measured NR ACLR shall be higher than the limits in Table 6.5.2.4.1.5-2 defined in clause 6.5.2.4.1.5 in TS 38.521-1 [8] for the NR carrier. + +For E-UTRA ACLR, if the measured adjacent channel power is greater than –50 dBm then the measured E-UTRA ACLR shall be higher than the limits in Table 6.6.2.3.5.1-1 defined in clause 6.6.2.3.5 in TS 36.521-1 [10] for the E-UTRA carrier. + +#### 6.5B.2.3 Out-of-band emissions for Inter-band EN-DC within FR1 + +##### 6.5B.2.3.1 Spectrum emissions mask for Inter-band EN-DC within FR1 (1 NR CC) + +###### 6.5B.2.3.1.1 Test purpose + +Same test purpose as in clause 6.5.2.2 in TS 38.521-1 [8] for the NR carrier. + +###### 6.5B.2.3.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.5B.2.3.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.2.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.5B.2.3.1.4 Test description + +Same test description as in clause 6.5.2.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.2.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.5B.2.3.1.5 Test requirement + +Power of any UE emission shall fulfil requirements in Table 6.5.2.2.5-1 defined in TS 38.521-1 [8] for the NR carrier.6.5B.2.3.2. + +##### 6.5B.2.3.2 Additional Spectrum emissions mask for Inter-band EN-DC within FR1 (1 NR CC) + +###### 6.5B.2.3.2.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-1 [8] for the NR carrier. + +###### 6.5B.2.3.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.5B.2.3.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.5B.2.3.2.4 Test description + +Same test description as in clause 6.5.2.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.2.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.3.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.5B.2.3.2.5 Test requirement + +Power of any UE emission shall fulfil requirements in applicable table from Table 6.5.2.3.5-1 to Table 6.5.2.3.5.2-1 defined in TS 38.521-1 [8] for the NR carrier. + +##### 6.5B.2.3.3 Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.5B.2.3.3.1 NR - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.5B.2.3.3.1.1 Test purpose + +Same test purpose as in clause 6.5.2.4.1.1 in TS 38.521-1 [8]. + +###### 6.5B.2.3.3.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.5B.2.3.3.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.4.1.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied + +###### 6.5B.2.3.3.1.4 Test description + +Same test description as in clause 6.5.2.4.1.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.2.4.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.4.1.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.5B.2.3.3.1.5 Test requirement + +Same test requirement as in clause 6.5.2.4.1.5 in TS 38.521-1 [8]. + +###### 6.5B.2.3.3.2 UTRA - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) + +###### 6.5B.2.3.3.2.1 Test purpose + +Same test purpose as in clause 6.5.2.4.2.1 in TS 38.521-1 [8]. + +###### 6.5B.2.3.3.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +###### 6.5B.2.3.3.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.4.2.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied + +###### 6.5B.2.3.3.2.4 Test description + +Same test description as in clause 6.5.2.4.2.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.2.4.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.4.2.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.5B.2.3.3.2.5 Test requirement + +Same test requirement as in clause 6.5.2.4.2.5 in TS 38.521-1 [8]. + +#### 6.5B.2.3a Out-of-band emissions for Inter-band NE-DC within FR1 + +##### 6.5B.2.3a.1 Spectrum emissions mask for Inter-band NE-DC within FR1 + +No exception requirements applicable to NR or LTE. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.5.2.2 and 6.5A.2.2 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.6.2.1 and 6.6.2.1A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +##### 6.5B.2.3a.2 Additional Spectrum emissions mask for Inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.5.2.3 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.6.2.2 and 6.6.2.2A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +##### 6.5B.2.3a.3 Adjacent channel leakage ratio for inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.5.2.4 and 6.5A.2.4 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.6.2.3 and 6.6.2.3A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +#### 6.5B.2.4 Out-of-band emissions for Inter-band EN-DC including FR2 + +##### 6.5B.2.4.1 Spectrum emissions mask for Inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- Measurement Uncertainties and Test Tolerances are FFS for power class 1 FR2b, 2, and 4. + +###### 6.5B.2.4.1.1 Test purpose + +Same test purpose as in clause 6.5.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.5B.2.4.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.5B.2.4.1.4 Test description + +###### 6.5B.2.4.1.4.1 Initial conditions + +Same test description as in clause 6.5.2.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.5.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.1.5 Test requirement + +Same test requirement as in clause 6.5.2.1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.2.4.1a Spectrum emissions mask with Power Boost for Inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5.2.1\_1 in TS 38.521-2 is incomplete for power class 1, 2 and 4. + +###### 6.5B.2.4.1a.1 Test purpose + +Same test purpose as in clause 6.5.2.1\_1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.1a.2 Test applicability + +This test case applies to all types of NR UE release 16 and forward supporting *mpr-PowerBoost-FR2-r16* UE capability, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.5B.2.4.1a.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.1\_1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.5B.2.4.1a.4 Test description + +Same test description as in clause 6.5.2.1\_1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.5.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2.4\_1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.2.1\_1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.1a.5 Test requirement + +Same test requirement as in clause 6.5.2.1\_1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.2.4.1\_1 Spectrum emissions mask for Inter-band EN-DC including FR2 (>1 NR CC) + +**Editor's note:** Test applicability, Test Description in below sub-clauses requires updates to clarify number of E-UTRA carriers that will be configured during the test + +###### 6.5B.2.4.1\_1.1 Spectrum emissions mask for Inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.2.1.1 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. + +###### 6.5B.2.4.1\_1.1.1 Test purpose + +Same test purpose as in clause 6.5.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.1\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.2.4.1\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +###### 6.5B.2.4.1\_1.1.4 Test description + +###### 6.5B.2.4.1\_1.1.4.1 Initial condition + +Same test description as in clause 6.5A.2.1.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.1\_1.1.5 Test Requirements + +Same test requirement as in clause 6.5A.2.1.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.2.4.1\_1.2 Spectrum emissions mask for Inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.2.1.2 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. + +###### 6.5B.2.4.1\_1.2.1 Test purpose + +Same test purpose as in clause 6.5.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.1\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.5B.2.4.1\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +###### 6.5B.2.4.1\_1.2.4 Test description + +###### 6.5B.2.4.1\_1.2.4.1 Initial condition + +Same test description as in clause 6.5A.2.1.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.1\_1.2.5 Test Requirements + +Same test requirement as in clause 6.5A.2.1.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.2.4.1\_1.3 Spectrum emissions mask for Inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.2.1.3 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. + +###### 6.5B.2.4.1\_1.3.1 Test purpose + +Same test purpose as in clause 6.5.2.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.1\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.5B.2.4.1\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.1.4. + +###### 6.5B.2.4.1\_1.3.4 Test description + +###### 6.5B.2.4.1\_1.3.4.1 Initial condition + +Same test description as in clause 6.5A.2.1.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.1.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.1.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.1.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.1\_1.3.5 Test Requirements + +Same test requirement as in clause 6.5A.2.1.3.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.2.4.1D Spectrum emissions mask for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5D.2.1 in TS 38.521-2 [9] is incomplete + +###### 6.5B.2.4.1D.1 Test purpose + +Same test purpose as in clause 6.5D.2.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.1D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2. + +###### 6.5B.2.4.1D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5D.2.1 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.2B.2.4. + +###### 6.5B.2.4.1D.4 Test description + +Same test description as in clause [6.5D.2.1] in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause [6.5D.2.1] in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +[Step 6] of Initial conditions as in clause [6.5D.2.1] in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. + +###### 6.5B.2.4.1D.5 Test Requirement + +Same test requirement as in clause 6.5D.2.1.5 of TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.2.4.3 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5.2.3 in TS 38.521-2 [9] is incomplete for PC2 and PC4. +- The referred test case 6.5.2.3 in TS 38.521-2 [9] is incomplete for aggregated BW > 400MHz. + +###### 6.5B.2.4.3.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.5B.2.4.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 6.5B.2.4.3.4 Test description + +###### 6.5B.2.4.3.4.1 Initial conditions + +Same test description as in clause 6.5.2.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. For Initial conditions as in clause 6.5.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.2.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3.5 Test requirement + +Same test requirement as in clause 6.5.2.3.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.2.4.3\_1 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (>1 NR CC) + +**Editor's note:** Test applicability, Test Description in below sub-clauses requires updates to clarify number of E-UTRA carriers that will be configured during the test + +###### 6.5B.2.4.3\_1.1 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.2.2.1 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. + +###### 6.5B.2.4.3\_1.1.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.2.4.3\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.5B.2.4.3\_1.1.4 Test description + +###### 6.5B.2.4.3\_1.1.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.1.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.2.4.3\_1.2 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.2.2.2 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. + +###### 6.5B.2.4.3\_1.2.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.5B.2.4.3\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.5B.2.4.3\_1.2.4 Test description + +###### 6.5B.2.4.3\_1.2.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.2.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.2.4.3\_1.3 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.2.2.3 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. + +###### 6.5B.2.4.3\_1.3.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.5B.2.4.3\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.2.4. + +###### 6.5B.2.4.3\_1.3.4 Test description + +###### 6.5B.2.4.3\_1.3.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.3.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.3.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.2.4.3\_1.4 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note:** The test case is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.2.2.4 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.2.4.3\_1.4.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.5B.2.4.3\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.4. + +###### 6.5B.2.4.3\_1.4.4 Test description + +###### 6.5B.2.4.3\_1.4.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.4.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.4.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.4.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.2.4.3\_1.5 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note: The test case is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.2.2.4 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.2.4.3\_1.5.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.5B.2.4.3\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.4. + +###### 6.5B.2.4.3\_1.5.4 Test description + +###### 6.5B.2.4.3\_1.5.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.5.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.5.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.5.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.2.4.3\_1.6 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note: The test case is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.2.2.4 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.2.4.3\_1.6.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.2.4.3\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.5B.2.4.3\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.4. + +###### 6.5B.2.4.3\_1.6.4 Test description + +###### 6.5B.2.4.3\_1.6.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.6.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.6.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.6.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.2.4.3\_1.7 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note: The test case is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.2.2.4 in TS 38.521-2 [9] is incomplete for intra-band contiguous CA supporting aggregated BW > 400MHz are TBD. +- Measurement Uncertainties and Test Tolerances is incomplete. + +##### 6.5B.2.4.3\_1.7.1 Test purpose + +Same test purpose as in clause 6.5.2.3.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.2.4.3\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.5B.2.4.3\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.2.3.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or *LTE*. *LTE* anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.2.4. + +###### 6.5B.2.4.3\_1.7.4 Test description + +###### 6.5B.2.4.3\_1.7.4.1 Initial condition + +Same test description as in clause 6.5A.2.2.7.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.2.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.2.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4.3\_1.7.5 Test Requirements + +Same test requirement as in clause 6.5A.2.2.7.5 in TS 38.521-2 [9] for the *NR* carrier. + +#### 6.5B.2.4D.3 Adjacent channel leakage ratio for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5D.2.2 in TS 38.521-2 [9] is incomplete + +##### 6.5B.2.4D.3.1 Test purpose + +Same test purpose as in clause 6.5D.2.2 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.2.4D.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.2.4D.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5D.2.2 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.2B.2.4. + +##### 6.5B.2.4D.3.4 Test description + +Same test description as in clause 6.5D.2.2 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5D.2.2 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +[Step 6] of Initial conditions as in clause 6.5D.2.2 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. + +Same test procedure as in clause 6.5D.2.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.2.4D.3.5 Test Requirement + +Same test requirement as in clause 6.5D.2.2 of TS 38.521-2 [9] for the NR carrier. + +### 6.5B.3 Spurious emissions for EN-DC + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, intermodulation products and frequency conversion products, but exclude out of band emissions. The spurious emission limits are specified in terms of general requirements in line with SM.329 [3] and *NR* operating band requirement to address UE co-existence. + +To improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +#### 6.5B.3.1 Spurious Emissions for intra-band contiguous EN-DC + +##### 6.5B.3.1.1 General spurious emissions for intra-band contiguous EN-DC + +###### 6.5B.3.1.1.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions. + +###### 6.5B.3.1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC. + +###### 6.5B.3.1.1.3 Minimum conformance requirements + +The general spurious emissions requirements specified in clause 6.6.3.1 of TS 36.101 [5] and clause 6.5.3.1 of TS 38.101-1 [2] apply beyond any frequencies for which the out-of-band emissions requirements in clause 6.5B.2.1 of TS 38.101-3 [4] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.1.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.3.1.1.4 Test description + +Same test description as in clause 6.5.3.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 6.5B.3.1.1.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Low range, Mid range, High range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_scg is tested for Lowest N RB_agg and Highest N RB_agg , respectively. | | + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths are specified in Table 4.6-1 except for the parameters specified in Table 6.5B.3.1.1.4-1. + +For Initial conditions as in clause 6.5.3.1.4 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1 The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 6.5B.3.1.1.4-1. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +- 4.1. The UL Reference Measurement channels are set according to Table 6.5B.3.1.1.4-1. + +Step 6 of Initial conditions as in clause 6.5.3.1.4 in TS 38.521-1 [8] is replaced by the following three steps: + +- 6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +- 7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +- 8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.5.3.1.4 in TS 38.521-1 [8]. + +###### 6.5B.3.1.1.5 Test Requirement + +The measured average power of spurious emission, derived in step 5, shall not exceed the described value in Table 6.5B.3.1.1.5-1. + +Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than $\Delta f_{\text{OOB}}$ (MHz) from the edge of the channel bandwidth shown in Table 6.5.3.1.3-1 of TS 38.521-1 [8] for NR carrier, and Table 6.6.3.1.3-1 of TS 36.521-1[10] for E-UTRA carrier. + +- NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +**Table 6.5B.3.1.1.5-1: General spurious emissions test requirements** + +| Frequency Range | Maximum Level | Measurement bandwidth | NOTE | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| $9 \text{ kHz} \leq f < 150 \text{ kHz}$ | -36 dBm | 1 kHz | | +| $150 \text{ kHz} \leq f < 30 \text{ MHz}$ | -36 dBm | 10 kHz | | +| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$ | -36 dBm | 100 kHz | | +| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ | -30 dBm | 1 MHz | 4 | +| | -25 dBm | 1 MHz | 3 | +| 12.75 GHz $\leq f <$ 5th harmonic of the upper frequency edge of the UL operating band in GHz | -30 dBm | 1 MHz | 1 | +| $12.75 \text{ GHz} < f < 26 \text{ GHz}$ | -30 dBm | 1 MHz | 2 | +| NOTE 1: Applies for Band that the upper frequency edge of the UL Band more than 2.69 GHz. | | | | +| NOTE 2: Applies for Band that the upper frequency edge of the UL Band more than 5.2 GHz. | | | | +| NOTE 3: Applies for Band n41, CA configurations including Band n41, and EN-DC configurations that include n41 specified in clause 5.2B of TS 36.101 [5] when NS_04 is signalled. | | | | +| NOTE 4: Does not apply for Band n41, CA configurations including Band n41, and EN-DC configurations that include n41 specified in subclause 5.2B of TS 38.101-3 [4] when NS_04 is signalled. | | | | + +##### 6.5B.3.1.2 Spurious emission band UE co-existence for intra-band contiguous EN-DC + +##### 6.5B.3.1.2.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions for band UE co-existence for intra-band contiguous EN-DC. + +###### 6.5B.3.1.2.2 Test applicability + +This test case applies to all types of NR UE release 15 and forward supporting intra-band contiguous EN-DC. + +###### 6.5B.3.1.2.3 Minimum conformance requirements + +This clause specifies the requirements for the specified EN-DC configurations for coexistence with protected bands. + +The requirements in Tables 6.5B.3.1.2.3-1 and 6.5B.3.1.2.3-1a apply on each component carrier with all component carriers are active. + +**Table 6.5B.3.1.2.3-1: Requirements for intra band contiguous EN-DC** + +| EN-DC Configuration | Spurious emission | | | | | | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|-------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_(n)71 | E-UTRA Band 4, 5, 12, 13, 14, 17, 24, 26, 30, 48, 66 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Band 2, 25, 41, 70
NR Band n77 5 | F DL_low | - | F DL_high | -50 | 1 2 | +| | E-UTRA Band 29 | F DL_low | - | F DL_high | -38 | 1 3 | +| | E-UTRA Band 71 | F DL_low | - | F DL_high | -50 | 1 3 | +| DC_(n)41 | E-UTRA Band 1, 2, 3, 4, 5, 8, 10, 11, 12, 13, 14, 17, 18, 19, 21, 24, 25, 26, 27, 28, 29, 30, 34, 39, 42, 44, 45, 48, 50, 51, 66, 70, 71, 73, 74
NR Band n77, n78 | F DL_low | - | F DL_high | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 4 | +| | NR Band n79 | F DL_low | - | F DL_high | -50 | 1 2 | + +NOTE 1: FDL\_low and FDL\_high refer to each frequency band specified in Table 5.5-1 in TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2]. + +NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of (2MHz + N x LCRB x 180kHz), where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. + +NOTE 3: These requirements also apply for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1, Table 6.6.3.1A-1 in TS 36.101 [5] or in Table 6.5.3.1-1 in TS 38.101-1 [2] from the edge of the channel bandwidth. + +NOTE 4: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz. + +NOTE 5: Only applies to NR UE release 16 and forward supporting intra-band contiguous EN-DC. + +**Table 6.5B.3.1.2.3-1a: Requirements for intra band contiguous EN-DC in Rel-18** + +| EN-DC Configuration | Spurious emission | | | | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|-------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_(n)71 | E-UTRA Band 4, 5, 12, 13, 14, 17, 24, 26, 30, 48, 54 66 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Band 2, 25, 41, 70
NR Band n77 5 | F DL_low | - | F DL_high | -50 | 1 2 | +| | E-UTRA Band 29 | F DL_low | - | F DL_high | -38 | 1 3 | +| | E-UTRA Band 71 | F DL_low | - | F DL_high | -50 | 1 3 | +| DC_(n)41 | E-UTRA Band 1, 2, 3, 4, 5, 8, 10, 11, 12, 13, 14, 17, 18, 19, 21, 24, 25, 26, 27, 28, 29, 30, 34, 39, 42, 44, 45, 48, 50, 51, 54 66, 70, 71, 73, 74
NR Band n77, n78 | F DL_low | - | F DL_high | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 4 | +| | NR Band n79 | F DL_low | - | F DL_high | -50 | 1 2 | + +NOTE 1: FDL\_low and FDL\_high refer to each frequency band specified in Table 5.5-1 in TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2]. + +NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2\text{MHz} + N \times L_{\text{CRB}} \times 180\text{kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. + +NOTE 3: These requirements also apply for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1, Table 6.6.3.1A-1 in TS 36.101 [5] or in Table 6.5.3.1-1 in TS 38.101-1 [2] from the edge of the channel bandwidth. + +NOTE 4: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz. + +NOTE 5: Only applies to NR UE release 16 and forward supporting intra-band contiguous EN-DC. + +NOTE: To simplify the above Table, E-UTRA band numbers are listed for bands which are specified only for E-UTRA operation or both E-UTRA and NR operation. NR band numbers are listed for bands which are specified only for NR operation. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.1.2. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included, and E-UTRA measurements are performed. + +###### 6.5B.3.1.2.4 Test description + +###### 6.5B.3.1.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.2, and the channel bandwidth combination for E-UTRA and NR component carriers shall follow the value specified in Table 5.3B.1.2-1. All these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 6.5B.3.1.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexe A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.3.1.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------|------------------------|--------------|------------------------|--| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Low range, High range | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | Lowest and Highest N RB_agg (NOTE 3) | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | | | | +| Test Parameters | | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | E-UTRA Cell | | NR Cell | | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | | +| 1 | N/A for Spurious emission. | QPSK | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Right | | +| 2 | | QPSK | Outer_Full | CP-OFDM QPSK | Outer_Full | | +| NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. | | | | | | | +| NOTE 2: Outer_Full defined as the transmission bandwidth configuration N RB per channel bandwidth for the E-UTRA component as indicated in TS 36.521-1 [10] Table 5.4.2-1. Outer_1RB_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Outer_1RB_Right defined as 1 RB allocated at the right edge of the E-UTRA component. | | | | | | | +| NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same aggregated channel BW, only the combination with the highest NR BW is tested. | | | | | | | +| NOTE 4: The test configuration applies to intra-band contiguous EN-DC indicating support of dual simultaneous UL as defined in clause 5.5B.2. | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. E-UTRA downlink signals are initially set up according to Annex C0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. +4. NR downlink signals are initially set up according to Annex C.0, C.1 and C.2, and uplink signals according to Annex G.0, G.1, G.2, G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG and NR CG, respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG, respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.5B.3.1.2.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.3.1.2.4.2 Test Procedure + +1. E-UTRA SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.5B.3.1.2.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. NR SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5B.3.1.2.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. + +3. Both NR and E-UTRA SS send continuously uplink power control "up" commands in the uplink scheduling information to the UE until the UE transmits at $P_{\text{UMAX}}$ level; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5B.3.1.2.3-1. The centre frequency of the filter shall be stepped in contiguous steps according to Table 6.5B.3.1.2.3-1. The measured power shall be verified for each step. The measurement period shall capture the active time slots. During measurement the spectrum analyser shall be set to 'Detector' = RMS. + +###### 6.5B.3.1.2.4.3 Message Contents + +Message contents are according to TS 36.508 [11] clause 4.6 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions: + +**Table 6.5B.3.1.2.4.3-1: *RRCConnectionReconfiguration: nr-Config-r15*** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 6.5B.3.1.2.4.3-2: *PhysicalCellGroupConfig*** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 6.5B.3.1.2.4.3-3: *SystemInformationBlockType1: tdd-Config if operating on TDD band*** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | | +|-------------------------------------------------|--------------|-----------------------|-----------|--| +| Information Element | Value/remark | Comment | Condition | | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | | +| subframeAssignment | sa2 | | | | +| specialSubframePatterns | ssp7 | | | | +| } | | | | | + +###### 6.5B.3.1.2.5 Test Requirement + +Test requirements for Spurious Emissions UE Co-existence for intra-band contiguous EN-DC are the same as the minimum requirements described in clause 6.5B.3.1.2.3 minimum requirements and are not repeated in this clause. + +The requirements for the UE are release specific and can be found in Tables 6.5B.3.1.2.3-1 to 6.5B.3.1.2.3-1a. If the UE support a band, which is not defined in the table corresponding UE's release, the requirements for this band are taken from the table of earliest release where requirements for this band are defined. + +#### 6.5B.3.2 Spurious Emissions for intra-band non-contiguous EN-DC + +##### 6.5B.3.2.1 General spurious emissions for Intra-band non-contiguous EN-DC + +##### 6.5B.3.2.1.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions. + +###### 6.5B.3.2.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward supporting intra-band non-contiguous EN-DC. + +##### 6.5B.3.2.1.3 Minimum conformance requirements + +The general spurious emissions requirements specified in clause 6.6.3.1 of TS 36.521-1 [10] and clause 6.5.3.1 of TS 38.521-1 [8] apply beyond any frequencies for which the out-of-band emissions requirements in clause 6.5B.2.2 of TS 38.101-3 [4] apply. If for some frequency an individual CC spurious emission requirement overlaps with the general spectrum emission mask or the bandwidth of another CC then it does not apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.2.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.3.2.1.4 Test description + +Same test description as in clause 6.5.3.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 6.5B.3.2.1.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Low with maxWgap
High with maxWgap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested for Lowest N RB_agg and Highest N RB_agg , respectively. | | + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths are specified in Table 4.6-1 except for the parameters specified in Table 6.5B.3.2.1.4-1. + +For Initial conditions as in clause 6.5.3.1.4 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3 with E-UTRA channel bandwidth and test frequencies defined in Table 6.5B.3.2.1.4-1. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Same test procedure as in clause 6.5.3.1.4.2 in TS 38.521-1 [8]. + +###### 6.5B.3.2.1.5 Test Requirement + +Same test requirement as in clause 6.5B.3.1.1.5. + +##### 6.5B.3.2.2 Spurious emission band UE co-existence for intra-band non-contiguous EN-DC + +###### 6.5B.3.2.2.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions for band UE co-existence for intra-band non-contiguous EN-DC. + +###### 6.5B.3.2.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward supporting intra-band non-contiguous EN-DC. + +###### 6.5B.3.2.2.3 Minimum conformance requirements + +This clause specifies the requirements for the specified EN-DC configurations for co-existence with protected bands. + +The requirements in Tables 6.5B.3.2.2.3-1 and 6.5B.3.2.2.3-1a apply with all component carriers are active. + +**Table 6.5B.3.2.2.3-1: Requirements for intra-band non-contiguous EN-DC** + +| EN-DC Configuration | Spurious emission | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| ... | | | | | | | | +| DC_41A_n41A | E-UTRA Band 1, 2, 3, 4, 5, 8, 10, 11, 12, 13, 14, 17, 18, 19, 21, 24, 25, 26, 27, 28, 29, 34, 39, 42, 44, 45, 48, 50, 51, 66, 70, 71, 73, 74
NR Band n77, n78 and n79 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | E-UTRA Band 30, 40 | F DL_low | - | F DL_high | -40 | 1 | | +| ... | | | | | | | | +|

NOTE 1: FDL_low and FDL_high refer to each E-UTRA frequency band specified in Table 5.5-1 in TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2].

NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2nd, 3rd, 4th, or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of (2MHz + N x LCRB x 180kHz), where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.

NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz.

| | | | | | | | + +**Table 6.5B.3.2.2.3-1a: Requirements for intra-band non-contiguous EN-DC in Rel-18** + +| EN-DC Configuration | Spurious emission | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|-------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| ... | | | | | | | +| DC_41A_n41A | E-UTRA Band 1, 2, 3, 4, 5, 8, 10, 11, 12, 13, 14, 17, 18, 19, 21, 24, 25, 26, 27, 28, 29, 34, 39, 42, 44, 45, 48, 50, 51, 54, 66, 70, 71, 73, 74
NR Band n77, n78 and n79 | F DL_low | - | F DL_high | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | E-UTRA Band 30, 40 | F DL_low | - | F DL_high | -40 | 1 | +| ... | | | | | | | +| NOTE 1: F DL_low and F DL_high refer to each E-UTRA frequency band specified in Table 5.5-1 in TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2]. | | | | | | | +| NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2 nd , 3 rd , 4 th , or 5 th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2\text{MHz} + N \times L_{\text{CRB}} \times 180\text{kHz})$ , where N is 2, 3, 4, 5 for the 2 nd , 3 rd , 4 th or 5 th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. | | | | | | | +| NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz. | | | | | | | + +NOTE: To simplify the above Table, E-UTRA band numbers are listed for bands which are specified only for EUTRA operation or both E-UTRA and NR operation. NR band numbers are listed for bands which are specified only for NR operation. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.2.2. + +Exception requirements are applicable for NR but not for E-UTRA within this test. LTE anchor agnostic approach is not applied. E-UTRA configuration is included. + +###### 6.5B.3.2.2.4 Test description + +###### 6.5B.3.2.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.3, and the channel bandwidth combination for E-UTRA and NR component carriers shall follow the value specified in Table 5.3B.1.3-1. All these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.3 and are shown in Table 6.5B.3.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexe A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.3.2.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------|------------------------|-----------------|------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Low with maxWgap
High with maxWgap | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1 | Lowest and Highest N RB_agg (NOTE 3) | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | | | +| Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | +| 1 | N/A for Spurious emission. | QPSK | Outer_1RB_Left | CP-OFDM
QPSK | Edge_1RB_Right | +| 2 | | QPSK | Outer_Full | CP-OFDM
QPSK | Outer_Full | +| NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8].
NOTE 2: Outer_Full defined as the transmission bandwidth configuration N RB per channel bandwidth for the E-UTRA component as indicated in TS 36.521-1 [10] Table 5.4.2-1. Outer_1RB_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Outer_1RB_Right defined as 1 RB allocated at the right edge of the E-UTRA component.
NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same aggregated channel BW, only the combination with the highest NR BW is tested.
NOTE 4: The test configuration applies to intra-band non-contiguous EN-DC indicating support of dual simultaneous UL as defined in clause 5.5B.3. | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for SS diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. E-UTRA downlink signals are initially set up according to Annex C.0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. +4. NR downlink signals are initially set up according to Annex C.0, C.1 and C.2, and uplink signals according to Annex G.0, G.1, G.2, G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B and TS 38.521-1 [8] Annex B for E-UTRA link and NR link respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.5B.3.2.2.4.3. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.3.2.2.4.2 Test Procedure + +1. E-UTRA SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.5B.3.2.2.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. NR SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5B.3.2.2.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. + +3. Send continuously uplink power control "up" commands to the UE for both NR and E-UTRA carriers until the UE transmits at its $P_{\text{MAX}}$ level; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{MAX}}$ level. +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5B.3.2.2.3-1. The centre frequency of the filter shall be stepped in contiguous steps according to the same table. The measured power shall be verified for each step. The measurement period shall capture the active time slots. During measurement the spectrum analyser shall be set to 'Detector' = RMS. + +###### 6.5B.3.2.2.4.3 Message Contents + +Message contents are according to TS 36.508 [11] clause 4.6 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.5B.3.2.2.4.3-1: *RRConnectionReconfiguration: nr-Config-r15*** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 6.5B.3.2.2.4.3-2: *PhysicalCellGroupConfig*** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 6.5B.3.2.2.4.3-3: *SystemInformationBlockType1: tdd-Config if operating on TDD band*** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | | +|-------------------------------------------------|--------------|-----------------------|-----------|--| +| Information Element | Value/remark | Comment | Condition | | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | | +| subframeAssignment | sa2 | | | | +| specialSubframePatterns | ssp7 | | | | +| } | | | | | + +###### 6.5B.3.2.2.5 Test Requirement + +Test requirements for Spurious Emissions UE Co-existence for intra-band non-contiguous EN-DC are the same as the minimum requirements described in clause 6.5B.3.2.2.3 and are not repeated in this clause. + +The requirements for the UE are release specific and can be found in Tables 6.5B.3.2.2.3-1 to 6.5B.3.2.2.3-1a. If the UE support a band, which is not defined in the table corresponding UE's release, the requirements for this band are taken from the table of earliest release where requirements for this band are defined. + +#### 6.5B.3.3 Spurious Emissions for Inter-band EN-DC within FR1 + +##### 6.5B.3.3.1 General spurious emissions for Inter-band EN-DC within FR1 + +##### 6.5B.3.3.1.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions. + +###### 6.5B.3.3.1.2 Test applicability + +This test case applies to all types of NR UE release 15 and forward supporting inter-band EN-DC. + +##### 6.5B.3.3.1.3 Minimum conformance requirements + +The general spurious emissions requirements specified in subclause 6.6.3.1 of TS 36.101 [5], subclause 6.5.3.1 of TS 38.101-1 [2] and TS 38.101-2 [3] apply for each component carrier. For the case of inter-band EN-DC with a single carrier per cell group, the general spurious emissions requirements also apply with both downlink carrier and both uplink carriers active. Limits on configured maximum output power for the uplink according to subclause 6.2B.4 apply. + +NOTE: The general spurious emission requirements with both uplink carriers active are allowed to be verified for only a single inter-band EN-DC configuration per NR band. Furthermore, the requirements are allowed to be verified by measuring spurious emissions at the specific frequencies where second and third order intermodulation products generated by the two transmitted carriers can occur. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.3.1. Exception requirements applicable for both NR and LTE, therefore LTE anchor agnostic approach is not applied. + +##### 6.5B.3.3.1.4 Test description + +###### 6.5B.3.3.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, DC configuration specified in Table 5.5B.4.1-1 and test channel bandwidths specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1, and sub-carrier spacing based on NR operating bands specified in TS 38.521-1 [8] clause 5.3. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration, and are shown in Table 6.5B.3.3.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexe A, clause A.2.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A, clause A.2.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A, clause A.2 for NR RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 6.5B.3.3.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|------------------------|--------------|------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Low range for PCC and SCC
High range for PCC and SCC | | | | | +| Test EN-DC channel bandwidth as specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1 | 5 MHz for E-UTRA CC and Lowest for NR CC
Highest for E-UTRA CC and Highest for NR CC | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | | | +| Test Parameters | | | | | | +| Test ID | Downlink Configuration | EN-DC Uplink Configuration | | | | +| | | E-UTRA Cell | | NR Cell | | +| | | Modulation | RB allocation (NOTE 2) | Modulation | RB allocation (NOTE 1) | +| 1 | N/A for Spurious emission. | QPSK | Outer_1RB_Left | CP-OFDM QPSK | Edge_1RB_Left | +| 2 | | QPSK | Outer_1RB_Right | CP-OFDM QPSK | Edge_1RB_Right | +| 3 | | QPSK | Outer_Full | CP-OFDM QPSK | Outer_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. +NOTE 2: Outer\_Full defined as the transmission bandwidth configuration $N_{RB}$ per channel bandwidth for the E-UTRA component as indicated in TS 36.521-1 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. +NOTE 3: Only applicable to UEs not supporting UE capability *singleUL-Transmission*. +NOTE 4: Only one EN-DC combination per FR1 band is tested for each EN-DC configuration as defined in clause 5.5B.4. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for SS diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. E-UTRA downlink signals are initially set up according to Annex C.0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. +4. NR downlink signals are initially set up according to Annex C.0, C.1 and C.2, and uplink signals according to Annex G.0, G.1, G.2, G.3.0 of TS 38.521-1 [8]. +5. The UL Reference Measurement channels are set for E-UTRA CG and NR CG respectively. +6. Propagation conditions are set according to TS 36.521-1 [10] Annex B and TS 38.521-1 [8] Annex B for E-UTRA link and NR link respectively. +7. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.5B.3.3.1.4.3. +8. For both E-UTRA and NR UL uplink carriers active when both bands are TDD, ensure E-UTRA UL transmission overlaps with NR UL transmission in time by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.3.3.1.4.2 Test procedure + +1. E-UTRA SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.5B.3.3.1.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. + +2. NR SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5B.3.3.1.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +3. Send continuously uplink power control "up" commands to the UE for both NR and E-UTRA carriers until the UE transmits at its $P_{\text{UMAX}}$ level; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5B.3.3.1.5-1 (for EN-DC configurations listed in Table 6.5B.3.3.1.5-1) or Table 6.5.3.1.5-1 in TS 38.521-1 [8] (for EN-DC configurations not listed in Table 6.5B.3.3.1.5-1). The centre frequency of the filter shall be stepped in contiguous steps according to the same table. The measured power shall be verified for each step. The measurement period shall capture the active time slots. During measurement the spectrum analyser shall be set to 'Detector' = RMS. +5. For UE operating on EN-DC configuration with Band n41, redo the test for frequency range $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$ with the message content in step 7 of initial conditions with exceptions defined in Table 6.5B.3.3.1.4.3-4. + +In addition to test configuration and test procedure above, EN-DC only capable UEs and UEs not supporting NR/5GC mode in the tested band need to be tested according to LTE anchor agnostic below for EN-DC configurations listed in Table 6.5B.3.3.1.5-1. + +Same test description as in clause 6.5.3.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.3.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.1.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.5B.3.3.1.4.3 Message Contents + +Message contents are according to TS 36.508 [11] clause 4.6 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.5B.3.3.1.4.3-1: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | Sa2 | | | +| specialSubframePatterns | Ssp7 | | | +| } | | | | + +**Table 6.5B3.3.1.4.3-1a: Void** + +**Table 6.5B.3.3.1.4.3-2: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +**Table 6.5B.3.3.1.4.3-3: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +Exception for step 5 in test procedure: + +**Table 6.5B.3.3.1.4.3-4: Message contents** + +| Derivation Path: TS 38.508-1 [5], Table 4.6.3-1 | | | | +|-------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| additionalSpectrumEmission | 1 (NS_04) | | | + +###### 6.5B.3.3.1.5 Test Requirement + +For EN-DC configurations listed in Table 6.5B.3.3.1.5-1, the corresponding test requirements of the same table apply and are required to be tested with both LTE and NR carriers active. + +For EN-DC configurations not listed in Table 6.5B.3.3.1.5-1, the test requirements in Table 6.5.3.1.5-1 in TS 38.521-1[8] shall apply and are required to be tested with both LTE and NR carriers active. + +For EN-DC only capable devices, for EN-DC configurations listed in Table 6.5B.3.3.1.5-1 test requirements for NR carrier are the same as Table 6.5.3.1.5-1 in TS 38.521-1 [8] and are tested with anchor agnostic approach. + +**Table 6.5B.3.3.1.5-1: General spurious emissions test requirements** + +| Frequency Range | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| Test requirements for DC_1A_n3A configuration | | | | +| 135 MHz $\leq f \leq 270$ MHz | -36 dBm | 100 kHz | | +| 1440 MHz $\leq f \leq 1650$ MHz
2055 MHz $\leq f \leq 2250$ MHz
3630 MHz $\leq f \leq 3765$ MHz
5340 MHz $\leq f \leq 5745$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n5A configuration | | | | +| 222 MHz $\leq f \leq 332$ MHz | -36 dBm | 100 kHz | | +| 1071 MHz $\leq f \leq 1156$ MHz
2744 MHz $\leq f \leq 2829$ MHz
2991 MHz $\leq f \leq 3136$ MHz
3568 MHz $\leq f \leq 3678$ MHz
4664 MHz $\leq f \leq 4809$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n7A configuration | | | | +| 520 MHz $\leq f \leq 650$ MHz | -36 dBm | 100 kHz | | +| 1270 MHz $\leq f \leq 1460$ MHz
3020 MHz $\leq f \leq 3220$ MHz
4420 MHz $\leq f \leq 4550$ MHz
6340 MHz $\leq f \leq 6530$ MHz
6920 MHz $\leq f \leq 7120$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n8A configuration | | | | +| 90 MHz $\leq f \leq 220$ MHz | -36 dBm | 100 kHz | | +| 1005 MHz $\leq f \leq 1100$ MHz
2800 MHz $\leq f \leq 2895$ MHz
2925 MHz $\leq f \leq 3080$ MHz
3680 MHz $\leq f \leq 3810$ MHz
4720 MHz $\leq f \leq 4875$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n28A configuration | | | | +| 424 MHz $\leq f \leq 574$ MHz | -36 dBm | 100 kHz | | +| 1172 MHz $\leq f \leq 1277$ MHz
2623 MHz $\leq f \leq 2728$ MHz
3092 MHz $\leq f \leq 3257$ MHz
3326 MHz $\leq f \leq 3476$ MHz
4543 MHz $\leq f \leq 4708$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n41A configuration | | | | +| 516 MHz $\leq f \leq 770$ MHz | -36 dBm | 100 kHz | | +| 1150 MHz $\leq f \leq 1464$ MHz
3012 MHz $\leq f \leq 3460$ MHz
4416 MHz $\leq f \leq 4670$ MHz
6336 MHz $\leq f \leq 6650$ MHz
6912 MHz $\leq f \leq 7360$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n77A Configuration | | | | +| 360 MHz $\leq f \leq 660$ MHz | -36 dBm | 100 kHz | | +| 1320 MHz $\leq f \leq 2280$ MHz
4620 MHz $\leq f \leq 6480$ MHz
7140 MHz $\leq f \leq 8160$ MHz
8520 MHz $\leq f \leq 10380$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n78A Configuration | | | | +| 40 MHz $\leq f \leq 660$ MHz | -36 dBm | 100 kHz | | +| 1320 MHz $\leq f \leq 1880$ MHz
4620 MHz $\leq f \leq 5780$ MHz
7140 MHz $\leq f \leq 7760$ MHz
8520 MHz $\leq f \leq 9580$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_1A_n79A Configuration | | | | +| 440 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1160$ MHz
2420 MHz $\leq f \leq 3080$ MHz
6320 MHz $\leq f \leq 8080$ MHz
8240 MHz $\leq f \leq 8960$ MHz
10720 MHz $\leq f \leq 11980$ MHz | -30 dBm | 1 MHz | | + +| Test requirements for DC_2A_n5A Configuration | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|---| +| 152 MHz $\leq f \leq 262$ MHz | -36 dBm | 100 kHz | | +| 1001 MHz $\leq f \leq 1086$ MHz
2674 MHz $\leq f \leq 2759$ MHz
2851 MHz $\leq f \leq 2996$ MHz
3498 MHz $\leq f \leq 3608$ MHz
4524 MHz $\leq f \leq 4669$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_2A_n41A Configuration | | | | +| 586 MHz $\leq f \leq 840$ MHz | -36 dBm | 100 kHz | | +| 1010 MHz $\leq f \leq 1324$ MHz
3082 MHz $\leq f \leq 3530$ MHz | -30 dBm | 1 MHz | 2 | +| 4346 MHz $\leq f \leq 4600$ MHz
6196 MHz $\leq f \leq 6510$ MHz
6842 MHz $\leq f \leq 7290$ MHz | -25 dBm | 1 MHz | 1 | +| Test requirements for DC_2A_n71A Configuration | | | | +| 454 MHz $\leq f \leq 584$ MHz | -36 dBm | 100 kHz | | +| 1152 MHz $\leq f \leq 1247$ MHz
2513 MHz $\leq f \leq 2608$ MHz
3002 MHz $\leq f \leq 3157$ MHz
3176 MHz $\leq f \leq 3306$ MHz
4363 MHz $\leq f \leq 4518$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_2A_n77A Configuration | | | | +| 500 MHz $\leq f \leq 520$ MHz | -36 dBm | 100 kHz | | +| 1390 MHz $\leq f \leq 2350$ MHz
4690 MHz $\leq f \leq 6550$ MHz
7000 MHz $\leq f \leq 8020$ MHz
8450 MHz $\leq f \leq 10310$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_3A_n1A Configuration | | | | +| 135 MHz $\leq f \leq 270$ MHz | -36 dBm | 100 kHz | | +| 1440 MHz $\leq f \leq 1650$ MHz
2055 MHz $\leq f \leq 2250$ MHz
3630 MHz $\leq f \leq 3765$ MHz
5340 MHz $\leq f \leq 5745$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_3A_n5A Configuration | | | | +| 12 MHz $\leq f \leq 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 137$ MHz
861 MHz $\leq f \leq 961$ MHz | -36 dBm | 100 kHz | | +| 2534 MHz $\leq f \leq 2746$ MHz
3358 MHz $\leq f \leq 3483$ MHz
4244 MHz $\leq f \leq 4419$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_3A_n7A Configuration | | | | +| 715 MHz $\leq f < 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1070$ MHz
3215 MHz $\leq f \leq 3430$ MHz
4210 MHz $\leq f \leq 4355$ MHz
5920 MHz $\leq f \leq 6140$ MHz
6710 MHz $\leq f \leq 6925$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_3A_n8A Configuration | | | | +| 25 MHz $\leq f \leq 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 120$ MHz
795 MHz $\leq f \leq 905$ MHz | -36 dBm | 100 kHz | | +| 2505 MHz $\leq f \leq 2700$ MHz
3470 MHz $\leq f \leq 3615$ MHz
4300 MHz $\leq f \leq 4485$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_3A_n28A Configuration | | | | +| 214 MHz $\leq f \leq 379$ MHz
962 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1082$ MHz
2413 MHz $\leq f \leq 2533$ MHz
2672 MHz $\leq f \leq 2867$ MHz
3116 MHz $\leq f \leq 3281$ MHz
4123 MHz $\leq f \leq 4318$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_3A_n41A Configuration | | | | +| 711 MHz $\leq f < 1000$ MHz | -36 dBm | 100 kHz | | + +| | | | | +|-------------------------------------------------------|---------|---------|---| +| 1000MHz $\leq f \leq$ 1074 MHz | -30 dBm | 1 MHz | 2 | +| 3207MHz $\leq f \leq$ 3670 MHz | | | | +| 4206MHz $\leq f \leq$ 4475 MHz | -25 dBm | 1 MHz | 1 | +| 5916MHz $\leq f \leq$ 6260 MHz | | | | +| 6702MHz $\leq f \leq$ 7165 MHz | | | | +| Test requirements for DC_3A_n77A Configuration | | | | +| 270 MHz $\leq f \leq$ 780 MHz | -36 dBm | 100 kHz | | +| 1515 MHz $\leq f \leq$ 2490 MHz | | | | +| 4815 MHz $\leq f \leq$ 6690 MHz | -30 dBm | 1 MHz | | +| 6720 MHz $\leq f \leq$ 7770 MHz | | | | +| 8310 MHz $\leq f \leq$ 10185 MHz | | | | +| Test requirements for DC_3A_n78A Configuration | | | | +| 270 MHz $\leq f \leq$ 380 MHz | -36 dBm | 100 kHz | | +| 1515 MHz $\leq f \leq$ 2090 MHz | | | | +| 4815 MHz $\leq f \leq$ 5890 MHz | -30 dBm | 1 MHz | | +| 6720 MHz $\leq f \leq$ 7370 MHz | | | | +| 8310 MHz $\leq f \leq$ 9385 MHz | | | | +| Test requirements for DC_3A_n79A Configuration | | | | +| 830 MHz $\leq f \leq$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1580 MHz | | | | +| 2615 MHz $\leq f \leq$ 3290 MHz | | | | +| 6110 MHz $\leq f \leq$ 6785 MHz | -30 dBm | 1 MHz | | +| 7015 MHz $\leq f \leq$ 8570 MHz | | | | +| 10510 MHz $\leq f \leq$ 11785 MHz | | | | +| Test requirements for DC_5A_n2A Configuration | | | | +| 152 MHz $\leq f \leq$ 262 MHz | -36 dBm | 100 kHz | | +| 1001 MHz $\leq f \leq$ 1086 MHz | | | | +| 2674 MHz $\leq f \leq$ 2759 MHz | | | | +| 2851 MHz $\leq f \leq$ 2996 MHz | -30 dBm | 1 MHz | | +| 3498 MHz $\leq f \leq$ 3608 MHz | | | | +| 4524 MHz $\leq f \leq$ 4669 MHz | | | | +| Test requirements for DC_5A_n66A Configuration | | | | +| 12 MHz $\leq f \leq$ 30 MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq$ 132 MHz | | | | +| 861 MHz $\leq f \leq$ 956 MHz | -36 dBm | 100 kHz | | +| 2534 MHz $\leq f \leq$ 2736 MHz | | | | +| 3358 MHz $\leq f \leq$ 3478 MHz | -30 dBm | 1 MHz | | +| 4244 MHz $\leq f \leq$ 4409 MHz | | | | +| Test requirements for DC_5A_n77A Configuration | | | | +| 1602 MHz $\leq f \leq$ 3376 MHz | | | | +| 4124 MHz $\leq f \leq$ 9249 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_5A_n78A Configuration | | | | +| 1602 MHz $\leq f \leq$ 2152 MHz | | | | +| 2451 MHz $\leq f \leq$ 2976 MHz | | | | +| 4124 MHz $\leq f \leq$ 4649 MHz | | | | +| 4948 MHz $\leq f \leq$ 5498 MHz | -30 dBm | 1 MHz | | +| 5751 MHz $\leq f \leq$ 6776 MHz | | | | +| 7424 MHz $\leq f \leq$ 8449 MHz | | | | +| Test requirements for DC_7A_n1A Configuration | | | | +| 520 MHz $\leq f \leq$ 650 MHz | -36 dBm | 100 kHz | | +| 1270 MHz $\leq f \leq$ 1460 MHz | | | | +| 3020 MHz $\leq f \leq$ 3220 MHz | | | | +| 4420 MHz $\leq f \leq$ 4550 MHz | -30 dBm | 1 MHz | | +| 6340 MHz $\leq f \leq$ 6530 MHz | | | | +| 6920 MHz $\leq f \leq$ 7120 MHz | | | | +| Test requirements for DC_7A_n3A Configuration | | | | +| 715 MHz $\leq f <$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1070 MHz | | | | +| 3215 MHz $\leq f \leq$ 3430 MHz | | | | +| 4210 MHz $\leq f \leq$ 4355 MHz | -30 dBm | 1 MHz | | +| 5920 MHz $\leq f \leq$ 6140 MHz | | | | +| 6710 MHz $\leq f \leq$ 6925 MHz | | | | +| Test requirements for DC_7A_n5A Configuration | | | | +| 802 MHz $\leq f \leq$ 922 MHz | -36 dBm | 100 kHz | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|---| +| 1651 MHz $\leq f \leq 1746$ MHz
3324 MHz $\leq f \leq 3419$ MHz
4148 MHz $\leq f \leq 4316$ MHz
5824 MHz $\leq f \leq 5989$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_7A_n8A Configuration | | | | +| 670 MHz $\leq f \leq 810$ MHz | -36 dBm | 100 kHz | | +| 1585 MHz $\leq f \leq 1690$ MHz
3380 MHz $\leq f \leq 3485$ MHz
4085 MHz $\leq f \leq 4400$ MHz
5880 MHz $\leq f \leq 6055$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_7A_n28A Configuration | | | | +| 1004 MHz $\leq f \leq 1164$ MHz
1752 MHz $\leq f \leq 1867$ MHz
3203 MHz $\leq f \leq 3318$ MHz
3906 MHz $\leq f \leq 4066$ MHz
4252 MHz $\leq f \leq 4437$ MHz
5703 MHz $\leq f \leq 5888$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_7A_n78A Configuration | | | | +| 730 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1840$ MHz
4030 MHz $\leq f \leq 5100$ MHz
5800 MHz $\leq f \leq 6370$ MHz
8300 MHz $\leq f \leq 8940$ MHz
9100 MHz $\leq f \leq 10170$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_8A_n1A Configuration | | | | +| 90 MHz $\leq f \leq 220$ MHz | -36 dBm | 100 kHz | | +| 1005 MHz $\leq f \leq 1100$ MHz
2800 MHz $\leq f \leq 2895$ MHz
2925 MHz $\leq f \leq 3080$ MHz
3680 MHz $\leq f \leq 3810$ MHz
4720 MHz $\leq f \leq 4875$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_8A_n3A Configuration | | | | +| 25 MHz $\leq f < 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 120$ MHz
795 MHz $\leq f \leq 905$ MHz | -36 dBm | 100 kHz | | +| 2505 MHz $\leq f \leq 2700$ MHz
3470 MHz $\leq f \leq 3615$ MHz
4300 MHz $\leq f \leq 4485$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_8A_n20A Configuration | | | | +| 18 MHz $\leq f < 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 83$ MHz
749 MHz $\leq f \leq 844$ MHz
898 MHz $\leq f \leq 998$ MHz | -36 dBm | 100 kHz | | +| 1712 MHz $\leq f \leq 1777$ MHz
2544 MHz $\leq f \leq 2692$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_8A_n28A Configuration | | | | +| 132 MHz $\leq f \leq 212$ MHz
491 MHz $\leq f \leq 616$ MHz | -36 dBm | 100 kHz | | +| 1012 MHz $\leq f \leq 1127$ MHz
1583 MHz $\leq f \leq 1663$ MHz
2286 MHz $\leq f \leq 2411$ MHz
2463 MHz $\leq f \leq 2578$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_8A_n41A Configuration | | | | +| 666 MHz $\leq f \leq 930$ MHz | -36 dBm | 100 kHz | | +| 1581 MHz $\leq f \leq 1810$ MHz | -30 dBm | 1 MHz | 2 | +| 3376 MHz $\leq f \leq 3605$ MHz
4077 MHz $\leq f \leq 4520$ MHz
5872 MHz $\leq f \leq 6295$ MHz | -25 dBm | 1 MHz | 1 | +| Test requirements for DC_8A_n77A Configuration | | | | +| 1470 MHz $\leq f \leq 3320$ MHz
4180 MHz $\leq f \leq 9315$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_8A_n78A Configuration | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|--| +| 1470 MHz $\leq f \leq$ 2040 MHz
2385 MHz $\leq f \leq$ 2920 MHz
4180 MHz $\leq f \leq$ 4715 MHz
5060 MHz $\leq f \leq$ 5630 MHz
5685 MHz $\leq f \leq$ 6720 MHz
7480 MHz $\leq f \leq$ 8515 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_11A_n77A Configuration | | | | +| 404.2 MHz $\leq f \leq$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1344.2 MHz
1852.1 MHz $\leq f \leq$ 2772.1 MHz
4727.9 MHz $\leq f \leq$ 7095.8 MHz
8027.9 MHz $\leq f \leq$ 9847.9 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_11A_n78A Configuration | | | | +| 404.2 MHz $\leq f \leq$ 944.2 MHz | -36 dBm | 100 kHz | | +| 1852.1 MHz $\leq f \leq$ 2372.1 MHz
4727.9 MHz $\leq f \leq$ 6695.8 MHz
8027.9 MHz $\leq f \leq$ 9047.9 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_11A_n79A Configuration | | | | +| 1504.2 MHz $\leq f \leq$ 2144.2 MHz
2952.1 MHz $\leq f \leq$ 3572.1 MHz
5827.9 MHz $\leq f \leq$ 6447.9 MHz
7255.8 MHz $\leq f \leq$ 8572.1 MHz
10227.9 MHz $\leq f \leq$ 11447.9 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_12A_n2A Configuration | | | | +| 418 MHz $\leq f \leq$ 512 MHz | -36 dBm | 100 kHz | | +| 1134 MHz $\leq f \leq$ 1211 MHz
2549 MHz $\leq f \leq$ 2626 MHz
2984 MHz $\leq f \leq$ 3121 MHz
3248 MHz $\leq f \leq$ 3342 MHz
4399 MHz $\leq f \leq$ 4536 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_12A_n66A Configuration | | | | +| 278 MHz $\leq f \leq$ 382 MHz
994 MHz $\leq f <$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1081 MHz
2409 MHz $\leq f \leq$ 2496 MHz
2704 MHz $\leq f \leq$ 2861 MHz
3108 MHz $\leq f \leq$ 3212 MHz
4119 MHz $\leq f \leq$ 4276 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_12A_n77A Configuration | | | | +| 1868 MHz $\leq f \leq$ 3501 MHz
3999 MHz $\leq f \leq$ 5632 MHz
5884 MHz $\leq f \leq$ 9116 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_12A_n78A Configuration | | | | +| 1868 MHz $\leq f \leq$ 2402 MHz
2584 MHz $\leq f \leq$ 3101 MHz
3999 MHz $\leq f \leq$ 4516 MHz
4698 MHz $\leq f \leq$ 5232 MHz
5884 MHz $\leq f \leq$ 6901 MHz
7299 MHz $\leq f \leq$ 8316 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_13A_n2A Configuration | | | | +| 276 MHz $\leq f \leq$ 356 MHz | -36 dBm | 100 kHz | | +| 1063 MHz $\leq f \leq$ 1133 MHz
2627 MHz $\leq f \leq$ 2697 MHz
2913 MHz $\leq f \leq$ 3043 MHz
3404 MHz $\leq f \leq$ 3484 MHz
4477 MHz $\leq f \leq$ 4607 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_13A_n66A Configuration | | | | +| 136 MHz $\leq f \leq$ 226 MHz
923 MHz $\leq f \leq$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1003 MHz
2487 MHz $\leq f \leq$ 2567 MHz
2633 MHz $\leq f \leq$ 2783 MHz
3264 MHz $\leq f \leq$ 3354 MHz
4197 MHz $\leq f \leq$ 4347 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_13A_n77A Configuration | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|--| +| 1726 MHz $\leq f \leq$ 3423 MHz
4077 MHz $\leq f \leq$ 5774 MHz
5813 MHz $\leq f \leq$ 9187 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_14A_n2A Configuration | | | | +| 254 MHz $\leq f \leq$ 334 MHz | -36 dBm | 100 kHz | | +| 1052 MHz $\leq f \leq$ 1122 MHz
2638 MHz $\leq f \leq$ 2708 MHz
2902 MHz $\leq f \leq$ 3032 MHz
3426 MHz $\leq f \leq$ 3506 MHz
4488 MHz $\leq f \leq$ 4618 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_14A_n66A Configuration | | | | +| 114 MHz $\leq f \leq$ 204 MHz
912 MHz $\leq f \leq$ 992 MHz | -36 dBm | 100 kHz | | +| 2498 MHz $\leq f \leq$ 2578 MHz
2622 MHz $\leq f \leq$ 2772 MHz
3286 MHz $\leq f \leq$ 3376 MHz
4208 MHz $\leq f \leq$ 4358 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_14A_n77A Configuration | | | | +| 1704 MHz $\leq f \leq$ 3412 MHz
4088 MHz $\leq f \leq$ 5796 MHz
5808 MHz $\leq f \leq$ 9198 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_18A_n77A Configuration | | | | +| 1640 MHz $\leq f \leq$ 3385 MHz
4115 MHz $\leq f \leq$ 5860 MHz
5770 MHz $\leq f \leq$ 9230 MHz | -30dBm | 1MHz | | +| Test requirements for DC_18A_n78A Configuration | | | | +| 1640 MHz $\leq f \leq$ 2170 MHz
2470 MHz $\leq f \leq$ 2985 MHz
4115 MHz $\leq f \leq$ 4630 MHz
4930 MHz $\leq f \leq$ 5460 MHz
5770 MHz $\leq f \leq$ 6785 MHz
7415 MHz $\leq f \leq$ 8430 MHz | -30dBm | 1MHz | | +| Test requirements for DC_19A_n1A Configuration | | | | +| 230 MHz $\leq f \leq$ 320 MHz | -36 dBm | 100 kHz | | +| 1075 MHz $\leq f \leq$ 1150 MHz
2750 MHz $\leq f \leq$ 2825 MHz
2995 MHz $\leq f \leq$ 3130 MHz
3580 MHz $\leq f \leq$ 3670 MHz
4670 MHz $\leq f \leq$ 4805 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_19A_n77A Configuration | | | | +| 1610 MHz $\leq f \leq$ 3370 MHz
4130 MHz $\leq f \leq$ 5890 MHz
5755 MHz $\leq f \leq$ 9245 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_19A_n78A Configuration | | | | +| 1610 MHz $\leq f \leq$ 2140 MHz
2455 MHz $\leq f \leq$ 2970 MHz
4130 MHz $\leq f \leq$ 4645 MHz
4960 MHz $\leq f \leq$ 5490 MHz
5755 MHz $\leq f \leq$ 6770 MHz
7430 MHz $\leq f \leq$ 8445 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_19A_n79A Configuration | | | | +| 2710 MHz $\leq f \leq$ 3340 MHz
3555 MHz $\leq f \leq$ 4170 MHz
5230 MHz $\leq f \leq$ 5845 MHz
6060 MHz $\leq f \leq$ 6690 MHz
7955 MHz $\leq f \leq$ 9170 MHz
9630 MHz $\leq f \leq$ 10845 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_20A_n1A Configuration | | | | +| 196 MHz $\leq f \leq$ 316 MHz | -36 dBm | 100 kHz | | +| 1058 MHz $\leq f \leq$ 1148 MHz
2752 MHz $\leq f \leq$ 2842 MHz
2978 MHz $\leq f \leq$ 3128 MHz
3584 MHz $\leq f \leq$ 3704 MHz
4672 MHz $\leq f \leq$ 4822 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_20A_n3A Configuration | | | | +| 14 MHz $\leq f <$ 30 MHz | -36 dBm | 10 kHz | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|---| +| 30 MHz $\leq f \leq 121$ MHz
848 MHz $\leq f \leq 953$ MHz | -36 dBm | 100 kHz | | +| 2542 MHz $\leq f \leq 2738$ MHz
3374 MHz $\leq f \leq 3509$ MHz
4252 MHz $\leq f \leq 4432$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_20A_n7A Configuration | | | | +| 776 MHz $\leq f \leq 906$ MHz | -36 dBm | 100 kHz | | +| 1638 MHz $\leq f \leq 1738$ MHz
3332 MHz $\leq f \leq 3432$ MHz
4138 MHz $\leq f \leq 4308$ MHz
5832 MHz $\leq f \leq 6002$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_20A_n8A Configuration | | | | +| 18 MHz $\leq f < 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 83$ MHz
749 MHz $\leq f \leq 844$ MHz
898 MHz $\leq f \leq 998$ MHz | -36 dBm | 100 kHz | | +| 1712 MHz $\leq f \leq 1777$ MHz
2544 MHz $\leq f \leq 2692$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_20A_n28A Configuration | | | | +| 84 MHz $\leq f \leq 159$ MHz
544 MHz $\leq f \leq 664$ MHz
916 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1021$ MHz
1535 MHz $\leq f \leq 1610$ MHz
2238 MHz $\leq f \leq 2358$ MHz
2367 MHz $\leq f \leq 2472$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_20A_n78A Configuration | | | | +| 1576 MHz $\leq f \leq 2136$ MHz
2438 MHz $\leq f \leq 2968$ MHz
4132 MHz $\leq f \leq 4662$ MHz
4964 MHz $\leq f \leq 5524$ MHz
5738 MHz $\leq f \leq 6768$ MHz
7432 MHz $\leq f \leq 8462$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_21A_n1A Configuration | | | | +| 457.1 MHz $\leq f \leq 532.1$ MHz
915.8 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 2377.1 MHz $\leq f \leq 2512.1$ MHz
3367.9 MHz $\leq f \leq 3442.9$ MHz
4815.8 MHz $\leq f \leq 4905.8$ MHz
5287.9 MHz $\leq f \leq 5422.9$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_21A_n28A Configuration | | | | +| 6.9 MHz $\leq f \leq 28.1$ MHz | -36 dBm | 10 kHz | | +| 709.9 MHz $\leq f \leq 734.9$ MHz | -36 dBm | 100 kHz | | +| 2157.8 MHz $\leq f \leq 2200.9$ MHz
2903.9 MHz $\leq f \leq 2938.9$ MHz
3623.8 MHz $\leq f \leq 3663.8$ MHz | -30 dBm | 1 MHz | 4 | +| Test requirements for DC_21A_n77A Configuration | | | | +| 374.2 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1304.2$ MHz
1837.1 MHz $\leq f \leq 2752.1$ MHz
4747.9 MHz $\leq f \leq 7125.8$ MHz
8047.9 MHz $\leq f \leq 9862.9$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_21A_n78A Configuration | | | | +| 374.2 MHz $\leq f \leq 904.2$ MHz | -36 dBm | 100 kHz | | +| 1837.1 MHz $\leq f \leq 2352.1$ MHz
4747.9 MHz $\leq f \leq 6152.1$ MHz
6195.8 MHz $\leq f \leq 6725.8$ MHz
8047.9 MHz $\leq f \leq 9062.9$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_21A_n79A Configuration | | | | +| 1474.2 MHz $\leq f \leq 2104.2$ MHz
2937.1 MHz $\leq f \leq 3552.1$ MHz
5847.9 MHz $\leq f \leq 6462.9$ MHz
7295.8 MHz $\leq f \leq 8552.1$ MHz
10247.9 MHz $\leq f \leq 11462.9$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_25A_n41A Configuration | | | | +| 581 MHz $\leq f \leq 840$ MHz | -36 dBm | 100 kHz | | + +| | | | | +|--------------------------------------------------------|---------|---------|---| +| 1010 MHz $\leq f \leq$ 1334 MHz | -30 dBm | 1 MHz | 2 | +| 3077 MHz $\leq f \leq$ 3530 MHz | | | | +| 4346 MHz $\leq f \leq$ 4605 MHz | -25 dBm | 1 MHz | 1 | +| 6196 MHz $\leq f \leq$ 6520 MHz | | | | +| 6842 MHz $\leq f \leq$ 7295 MHz | | | | +| Test requirements for DC_26A_n41A Configuration | | | | +| 798 MHz $\leq f <$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1062 MHz | -30 dBm | 1 MHz | 2 | +| 1647 MHz $\leq f \leq$ 1876 MHz | | | | +| 3310 MHz $\leq f \leq$ 3539 MHz | -25 dBm | 1 MHz | 1 | +| 4124 MHz $\leq f \leq$ 4566 MHz | | | | +| 5806 MHz $\leq f \leq$ 6229 MHz | | | | +| Test requirements for DC_26A_n77A Configuration | | | | +| 1602 MHz $\leq f \leq$ 3386 MHz | | | | +| 4114 MHz $\leq f \leq$ 5898 MHz | -30 dBm | 1 MHz | | +| 5751 MHz $\leq f \leq$ 9249 MHz | | | | +| Test requirements for DC_26A_n78A Configuration | | | | +| 1602 MHz $\leq f \leq$ 2172 MHz | | | | +| 2451 MHz $\leq f \leq$ 2986 MHz | | | | +| 4114 MHz $\leq f \leq$ 4649 MHz | -30 dBm | 1 MHz | | +| 4928 MHz $\leq f \leq$ 5498 MHz | | | | +| 5751 MHz $\leq f \leq$ 6786 MHz | | | | +| 7414 MHz $\leq f \leq$ 8449 MHz | | | | +| Test requirements for DC_26A_n79A Configuration | | | | +| 2702 MHz $\leq f \leq$ 3372 MHz | | | | +| 3551 MHz $\leq f \leq$ 4186 MHz | | | | +| 5214 MHz $\leq f \leq$ 5849 MHz | -30 dBm | 1 MHz | | +| 6028 MHz $\leq f \leq$ 6698 MHz | | | | +| 7951 MHz $\leq f \leq$ 9186 MHz | | | | +| 9614 MHz $\leq f \leq$ 10849 MHz | | | | +| Test requirements for DC_28A_n3A Configuration | | | | +| 214 MHz $\leq f \leq$ 379 MHz | | | | +| 962 MHz $\leq f <$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1082 MHz | | | | +| 2413 MHz $\leq f \leq$ 2533 MHz | | | | +| 2672 MHz $\leq f \leq$ 2867 MHz | -30 dBm | 1 MHz | | +| 3116 MHz $\leq f \leq$ 3281 MHz | | | | +| 4123 MHz $\leq f \leq$ 4318 MHz | | | | +| Test requirements for DC_28A_n5A Configuration | | | | +| 76 MHz $\leq f \leq$ 146 MHz | | | | +| 557 MHz $\leq f \leq$ 672 MHz | -36 dBm | 100 kHz | | +| 900 MHz $\leq f \leq$ 995 MHz | | | | +| 1527 MHz $\leq f \leq$ 1597 MHz | | | | +| 2230 MHz $\leq f \leq$ 2345 MHz | -30 dBm | 1 MHz | | +| 2351 MHz $\leq f \leq$ 2446 MHz | | | | +| Test requirements for DC_28A_n7A Configuration | | | | +| 1004 MHz $\leq f \leq$ 1164 MHz | | | | +| 1752 MHz $\leq f \leq$ 1867 MHz | | | | +| 3203 MHz $\leq f \leq$ 3318 MHz | | | | +| 3906 MHz $\leq f \leq$ 4066 MHz | -30 dBm | 1 MHz | | +| 4252 MHz $\leq f \leq$ 4437 MHz | | | | +| 5703 MHz $\leq f \leq$ 5888 MHz | | | | +| Test requirements for DC_28A_n77A Configuration | | | | +| 1804 MHz $\leq f \leq$ 3497 MHz | | | | +| 4003 MHz $\leq f \leq$ 5696 MHz | -30 dBm | 1 MHz | | +| 5852 MHz $\leq f \leq$ 9148 MHz | | | | +| Test requirements for DC_28A_n78A Configuration | | | | +| 1804 MHz $\leq f \leq$ 2394 MHz | | | | +| 2552 MHz $\leq f \leq$ 3097 MHz | | | | +| 4003 MHz $\leq f \leq$ 4548 MHz | | | | +| 4706 MHz $\leq f \leq$ 5296 MHz | -30 dBm | 1 MHz | | +| 5852 MHz $\leq f \leq$ 6897 MHz | | | | +| 7303 MHz $\leq f \leq$ 8348 MHz | | | | +| Test requirements for DC_28A_n79A Configuration | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|---| +| 2904 MHz $\leq f \leq$ 3594 MHz
3652 MHz $\leq f \leq$ 4297 MHz
5103 MHz $\leq f \leq$ 5748 MHz
5806 MHz $\leq f \leq$ 6496 MHz
8052 MHz $\leq f \leq$ 9297 MHz
9503 MHz $\leq f \leq$ 10748 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_30A_n2A Configuration | | | | +| 395 MHz $\leq f <$ 465 MHz | -36 dBm | 100 kHz | | +| 1385 MHz $\leq f \leq$ 1515 MHz
2700 MHz $\leq f \leq$ 2780 MHz
4155 MHz $\leq f \leq$ 4225 MHz
6005 MHz $\leq f \leq$ 6135 MHz
6460 MHz $\leq f \leq$ 6540 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_30A_n5A Configuration | | | | +| 607 MHz $\leq f \leq$ 667 MHz | -36 dBm | 100 kHz | | +| 1456 MHz $\leq f \leq$ 1491 MHz
3129 MHz $\leq f \leq$ 3164 MHz
3761 MHz $\leq f \leq$ 3806 MHz
3953 MHz $\leq f \leq$ 4013 MHz
5434 MHz $\leq f \leq$ 5479 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_30A_n77A Configuration | | | | +| 410 MHz $\leq f <$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1895 MHz
4285 MHz $\leq f \leq$ 5615 MHz
7910 MHz $\leq f \leq$ 8830 MHz
8905 MHz $\leq f \leq$ 10715 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_39A_n41A Configuration | | | | +| 576 MHz $\leq f <$ 810 MHz | -36 dBm | 100 kHz | | +| 1070 MHz $\leq f \leq$ 1344 MHz | -30 dBm | 1 MHz | 2 | +| 3072 MHz $\leq f \leq$ 3500 MHz
4376 MHz $\leq f \leq$ 4610 MHz
6256 MHz $\leq f \leq$ 6530 MHz
6872 MHz $\leq f \leq$ 7300 MHz | -25 dBm | 1 MHz | 1 | +| Test requirements for DC_39A_n79A Configuration | | | | +| 560 MHz $\leq f \leq$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1240 MHz
2480 MHz $\leq f \leq$ 3120 MHz
6280 MHz $\leq f \leq$ 8120 MHz
8160 MHz $\leq f \leq$ 8840 MHz
10680 MHz $\leq f \leq$ 11920 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_40A_n1A Configuration | | | | +| 320 MHz $\leq f \leq$ 480 MHz | -36 dBm | 100 kHz | | +| 1440 MHz $\leq f \leq$ 1660 MHz
2620 MHz $\leq f \leq$ 2880 MHz
4220 MHz $\leq f \leq$ 4380 MHz
6140 MHz $\leq f \leq$ 6360 MHz
6520 MHz $\leq f \leq$ 6780 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_40A_n41A Configuration | | | | +| 96 MHz $\leq f <$ 390 MHz | -36 dBm | 100 kHz | | +| 1910 MHz $\leq f \leq$ 2304 MHz | -30 dBm | 1 MHz | 2 | +| 2592 MHz $\leq f \leq$ 3080 MHz
4796 MHz $\leq f \leq$ 5090 MHz
7096 MHz $\leq f \leq$ 7780 MHz | -25 dBm | 1 MHz | 1 | +| Test requirements for DC_40A_n78A Configuration | | | | +| 800 MHz $\leq f \leq$ 1000 MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq$ 1500 MHz
4200 MHz $\leq f \leq$ 5300 MHz
5600 MHz $\leq f \leq$ 6200 MHz
7900 MHz $\leq f \leq$ 8600 MHz
8900 MHz $\leq f \leq$ 10000 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_40A_n79A Configuration | | | | +| 2000 MHz $\leq f \leq$ 2700 MHz
6400 MHz $\leq f \leq$ 7700 MHz
9000 MHz $\leq f \leq$ 9800 MHz
11100 MHz $\leq f \leq$ 12400 MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_41A_n28A Configuration | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|---| +| 1000 MHz $\leq f \leq 1284$ MHz
1748 MHz $\leq f \leq 1987$ MHz
3199 MHz $\leq f \leq 3438$ MHz
3902 MHz $\leq f \leq 4186$ MHz
4244 MHz $\leq f \leq 4677$ MHz
5695 MHz $\leq f \leq 6128$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_41A n77A Configuration | | | | +| 610 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 2080$ MHz
3910 MHz $\leq f \leq 6890$ MHz
8292 MHz $\leq f \leq 11090$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_41A n78A Configuration | | | | +| 610 MHz $\leq f \leq 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 2080$ MHz
3910 MHz $\leq f \leq 5104$ MHz
5796 MHz $\leq f \leq 6490$ MHz
8292 MHz $\leq f \leq 10290$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_41A n79A Configuration | | | | +| 8 MHz $\leq f \leq 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 980$ MHz | -36 dBm | 100 kHz | | +| 1710 MHz $\leq f \leq 2504$ MHz
6110 MHz $\leq f \leq 7690$ MHz
9392 MHz $\leq f \leq 10380$ MHz
11296 MHz $\leq f \leq 12690$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_42A n77A Configuration | | | | +| 300 MHz $\leq f \leq 800$ MHz | -36 dBm | 100 kHz | | +| 2600 MHz $\leq f \leq 5000$ MHz
6700 MHz $\leq f \leq 7800$ MHz
10000 MHz $\leq f \leq 12000$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_48A n5A Configuration | | | | +| 1852 MHz $\leq f \leq 2052$ MHz
2701 MHz $\leq f \leq 2876$ MHz
4374 MHz $\leq f \leq 4549$ MHz
5198 MHz $\leq f \leq 5398$ MHz
6251 MHz $\leq f \leq 6576$ MHz
7924 MHz $\leq f \leq 8249$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_48A n66A Configuration | | | | +| 10 MHz $\leq f < 30$ MHz | -36 dBm | 10 KHz | | +| 30 MHz $\leq f \leq 280$ MHz | -36 dBm | 100 KHz | | +| 1770 MHz $\leq f \leq 1990$ MHz
5260 MHz $\leq f \leq 5690$ MHz
6970 MHz $\leq f \leq 7260$ MHz
8810 MHz $\leq f \leq 9180$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_66A n5A Configuration | | | | +| 12 MHz $\leq f \leq 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f \leq 132$ MHz
861 MHz $\leq f \leq 956$ MHz | -36 dBm | 100 kHz | | +| 2534 MHz $\leq f \leq 2736$ MHz
3358 MHz $\leq f \leq 3478$ MHz
4244 MHz $\leq f \leq 4409$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_66A n41A Configuration | | | | +| 716 MHz $\leq f < 1000$ MHz | -36 dBm | 100 kHz | | +| 1000 MHz $\leq f \leq 1064$ MHz
3212 MHz $\leq f \leq 3670$ MHz
4206 MHz $\leq f \leq 4470$ MHz
5916 MHz $\leq f \leq 6250$ MHz
6702 MHz $\leq f \leq 7160$ MHz | -30 dBm | 1 MHz | 2 | +| | -25 dBm | 1 MHz | 1 | +| Test requirements for DC_66A n71A Configuration | | | | +| 314 MHz $\leq f \leq 454$ MHz | -36 dBm | 100 kHz | | +| 1102 MHz $\leq f \leq 1117$ MHz
2373 MHz $\leq f \leq 2478$ MHz
2722 MHz $\leq f \leq 2897$ MHz
3036 MHz $\leq f \leq 3176$ MHz
4083 MHz $\leq f \leq 4258$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_66A n77A Configuration | | | | +| 260MHz $\leq f \leq 780$ MHz | -36 dBm | 100 kHz | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|--| +| 1520 MHz $\leq f \leq 2490$ MHz
5010 MHz $\leq f \leq 6690$ MHz
6720 MHz $\leq f \leq 7760$ MHz
8310 MHz $\leq f \leq 10180$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_66A_n78A Configuration | | | | +| 260 MHz $\leq f \leq 380$ MHz | -36 dBm | 100 kHz | | +| 1520 MHz $\leq f \leq 2090$ MHz
4820 MHz $\leq f \leq 5890$ MHz
6720 MHz $\leq f \leq 7360$ MHz
8310 MHz $\leq f \leq 9380$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_71A_n2A Configuration | | | | +| 454 MHz $\leq f \leq 584$ MHz | -36 dBm | 100 kHz | | +| 1152 MHz $\leq f \leq 1247$ MHz
2513 MHz $\leq f \leq 2608$ MHz
3002 MHz $\leq f \leq 3157$ MHz
3176 MHz $\leq f \leq 3306$ MHz
4363 MHz $\leq f \leq 4518$ MHz | -30 dBm | 1 MHz | | +| Test requirements for DC_71A_n66A Configuration | | | | +| 314 MHz $\leq f \leq 454$ MHz | -36 dBm | 100 kHz | | +| 1012 MHz $\leq f \leq 1117$ MHz
2373 MHz $\leq f \leq 2478$ MHz
2722 MHz $\leq f \leq 2897$ MHz
3036 MHz $\leq f \leq 3176$ MHz
4083 MHz $\leq f \leq 4258$ MHz | -30 dBm | 1 MHz | | +| NOTE 1: Applies for Band n41, CA configurations including Band n41, and EN-DC configurations that include n41 specified in clause 5.2B of TS 36.101 [5] when NS_04 is signalled.
NOTE 2: Does not apply for Band n41, CA configurations including Band n41, and EN-DC configurations that include n41 specified in subclause 5.2B of TS 38.101-3 [4] when NS_04 is signalled. | | | | + +##### 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 + +*Editor's note: The default and additional test configuration is analysed based on the assumption that only intermodulation products need to be tested. The band combinations without TP analysis in TR 38.905 are incomplete.* + +##### 6.5B.3.3.2.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions for band UE co-existence for inter-band EN-DC. + +##### 6.5B.3.3.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward supporting inter-band EN-DC. + +##### 6.5B.3.3.2.3 Minimum conformance requirements + +This clause specifies the additional requirements for the specified uplink EN-DC, for coexistence with protected bands with the single CC uplink assigned to E-UTRA and NR bands for the specified uplink carrier aggregation configurations in Table 6.5B.3.3.2.1-1. The requirements in Tables 6.5B.3.3.2.3-1 to 6.5B.3.3.2.3-4 apply on each component carrier with all component carriers are active. + +NOTE: For inter-band EN\_DC with the uplink assigned to one LTE band and one NR band, the requirements in Tables 6.5B.3.3.2.3-1 to 6.5B.3.3.2.3-4 could be verified by measuring spurious emissions at the specific frequencies where second and third order intermodulation products generated by the two transmitted carriers can occur; in that case, the requirements for remaining applicable frequencies in Table 6.5B.3.3.2.3-1 to 6.5B.3.3.2.3-4 and in 6.5.3.2 of [2] and clause 6.6.3.2 of [4] would be considered to be verified by the measurements verifying the uplink single carrier UE to UE co-existence requirements. + +**Table 6.5B.3.3.2.3-1: Spurious emission band UE co-existence limits Rel-15** + +| EN-DC Configuration | Spurious emission | | | | | | +|---------------------|----------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|------------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_1_n28 | E-UTRA Band 5, 7, 8, 18, 19, 20, 26, 27, 31, 38, 40, 41, 72, 73
NR band n79 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Band 1, 22, 32, 42, 43, 50, 51, 52, 65, 74, 75, 76
NR band n77, n78 | F DL_low | - | F DL_high | -50 | 1 2 | +| | E-UTRA band n3, n34 | F DL_low | - | F DL_high | -50 | 1 5 | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 9, 11 | +| | E-UTRA Band 1, 65 | F DL_low | - | F DL_high | -50 | 1 9, 10 | +| | Frequency range | 470 | - | 694 | -42 | 8 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 5 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 5, 7, 16 | +| DC_1_n77 | E-UTRA Band 1, 3, 5, 7, 8, 11, 18, 19, 20, 21, 26, 28, 34, 40, 41, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 5, 7, 16 | +| DC_1_n78 | E-UTRA Band 1, 3, 5, 7, 8, 11, 18, 19, 20, 21, 26, 28, 34, 40, 41, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 5, 7, 16 | +| DC_1_n79 | E-UTRA Band 1, 3, 5, 7, 8, 11, 18, 19, 21, 26, 28, 34, 40, 41, 42, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 5, 7, 16 | +| DC_2_n5 | E-UTRA Bands 4, 5, 12, 13, 14, 17, 24, 26, 28, 29, 30, 42, 48, 50, 51, 66, 70, 71, 74, 85 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Bands 2, 25 | F DL_low | - | F DL_high | -50 | 1 2 | +| | E-UTRA Band 41, 43, 53 | F DL_low | - | F DL_high | -50 | 1 2 | +| DC_2_n66 | E-UTRA Bands 4, 5, 12, 13, 14, 17, 24, 26, 27, 28, 29, 30, 41, 50, 51, 66, 70, 71, 74, 85 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Bands 2, 25 | F DL_low | - | F DL_high | -50 | 1 5 | +| | E-UTRA Bands 42, 48 | F DL_low | - | F DL_high | -50 | 1 2 | +| DC_2_n71 | E-UTRA Band 4, 5, 12, 13, 14, 17, 24, 26, 29, 30, 48, 66 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Band 2, 25, 41, 70 | F DL_low | - | F DL_high | -50 | 1 2 | +| | E-UTRA Band n71 | F DL_low | - | F DL_high | -50 | 1 5 | +| DC_2_n78 | E-UTRA Band 4, 5, 12, 13, 14, 17, 24, 26, 27, 28, 29, 30, 41, 50, 51, 66, 70, 71, 74, 85 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Band 2, 25 | F DL_low | - | F DL_high | -50 | 1 2 | +| DC_3_n7 | E-UTRA Band 1, 5, 7, 8, 20, 26, 27, 28, 31, 32, 33, 34, 40, 43, 44, 50, 51, 65, 67, 72, 74, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA band 3 | F DL_low | - | F DL_high | -50 | 1 5 | +| | E-UTRA band 22, 42 | F DL_low | - | F DL_high | -50 | 1 2 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 5, 6, 7 | + +| | | | | | | | | +|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------|---|----------------------|-------|-----|---------| +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_3_n8 | E-UTRA Band 1, 11, 20, 21, 28, 31, 32, 33, 34, 38, 39, 40, 45, 50, 51, 65, 67, 68, 69, 72, 73, 74, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA band 3, 8 | F DL_low | - | F DL_high | -50 | 1 | 2, 5 | +| | E-UTRA band 7, 22, 41, 42, 43, 52 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | NR Band n77, n78, n79 | | | | | | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n28 | E-UTRA Band 1, 42, 43, 50, 51, 65, 74, 75, 76
NR band n77, n78, n79 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA band 1 | F DL_low | - | F DL_high | -50 | 1 | 9, 11 | +| | E-UTRA band 3 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| | E-UTRA Band 5, 7, 8, 18, 19, 20, 26, 27, 31, 34, 38, 40, 41, 72 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 9, 10 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 13 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_3_n77 | E-UTRA Band 1, 3, 5, 7, 8, 11, 18, 19, 20, 21, 26, 28, 34, 39, 40, 41, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n78
DC_3_n80_ULS
UP-TDM_n78 | E-UTRA Band 1, 3, 5, 7, 8, 11, 18, 19, 20, 21, 26, 28, 34, 39, 40, 41, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n79 | E-UTRA Band 1, 3, 5, 8, 11, 18, 19, 21, 28, 34, 39, 40, 41, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 42 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_5_n66 | E-UTRA Band 1, 2, 3, 4, 5, 6, 7, 8, 12, 13, 14, 17, 24, 25, 28, 29, 30, 34, 38, 40, 43, 45, 50, 51, 65, 66, 70, 71, 85 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 26 | 859 | - | 869 | -27 | 1 | | +| | E-UTRA Band 41, 42, 48, 52 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_5_n78 | E-UTRA Band 1, 2, 3, 4, 5, 7, 8, 12, 13, 14, 17, 24, 25, 28, 29, 30, 31, 34, 38, 40, 45, 65, 66, 70 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 26 | 859 | - | 869 | -27 | 1 | | +| | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2, 7 | +| DC_7_n28 | E-UTRA Band 2, 3, 5, 7, 8, 20, 26, 27, 31, 34, 40, 72 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 1, 4, 42, 43, 50, 65, 66, 74, 75, 76
NR band n78 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA band 1 | F DL_low | - | F DL_high | -50 | 1 | 9, 10 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n78 | E-UTRA Band 1, 2, 3, 4, 5, 7, 8, 11, 18, 19, 20, 21, 26, 27, 28, 31, 32, 33, 34, 40, 50, 51, 65, 66, 67, 68, 72, 74, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | + +| | | | | | | | | +|-----------|-------------------------------------------------------------------------------------------------------|---------------------|---|----------------------|-----|-----|---------------------| +| DC_8_n77 | E-UTRA Band 1, 20, 28, 31, 32, 33, 34, 38, 39, 40, 44, 45, 50, 51, 65, 67, 68, 69, 72, 73, 74, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA band 3, 7, 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 8 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 12 | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_8_n78 | E-UTRA Band 1, 20, 28, 34, 39, 40, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 3, 7, 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 8 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 12 | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_11_n77 | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_11_n78 | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_11_n79 | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 42, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_12_n66 | E-UTRA Band 2, 5, 13, 14, 17, 25, 26, 27, 30, 41, 71, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Bands 4, 48, 50, 51, 66, 70 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 12, 85 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| DC_19_n77 | E-UTRA Band 1, 3, 11, 21, 28, 34, 40, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n78 | E-UTRA Band 1, 3, 11, 21, 28, 34, 40, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n79 | E-UTRA Band 1, 3, 11, 21, 28, 34, 40, 42, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_20_n28 | E-UTRA Band 3, 7, 8, 31, 34 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 1, 22, 32, 38, 42, 43, 65, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | NR Band n78 | | | | | | | +| DC_20_n78 | E-UTRA Band 1, 3, 7, 8, 31, 32, 33, 34, 40, 50, 51, 65, 67, 68, 72, 74, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | F DL_low | +| | E-UTRA Band 20 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| | E-UTRA Band 38, 69 | F DL_low | - | F DL_high | -50 | 1 | 2 | + +| | | | | | | | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------|---|----------------------|-----|-----|-------| +| DC_21_n77 | E-UTRA Band 1, 3, 18, 19, 21, 28, 34, 40, 42, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n78 | E-UTRA Band 1, 3, 18, 19, 21, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n79 | E-UTRA Band 1, 3, 18, 19, 21, 28, 34, 42, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_25_n41 | E-UTRA band 4, 5, 12, 13, 14, 17, 24, 26, 27, 28, 29, 30, 42, 45, 66, 70, 71 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 48 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA/NR Band 2, 25 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| DC_26_n41 | E-UTRA/NR Band 1, 2, 3, 4, 5, 11, 12, 13, 14, 17, 18, 19, 21, 24, 25, 26, 29, 30, 31, 34, 39, 42, 43, 48, 50, 51, 65, 66, 70, 71, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| DC_26_n77 | E-UTRA Band 1, 3, 5, 11, 18, 19, 21, 26, 34, 39, 40, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | 2 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n78 | E-UTRA Band 1, 3, 5, 11, 18, 19, 21, 26, 34, 39, 40, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | 2 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n79 | E-UTRA Band 1, 3, 5, 11, 18, 19, 21, 26, 34, 39, 40, 42, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | 2 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_28_n77 | E-UTRA Band 3, 5, 7, 8, 18, 19, 20, 26, 34, 39, 40, 41 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 1, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 1 | F DL_low | - | F DL_high | -50 | 1 | 9, 11 | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 9, 10 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | + +| | | | | | | | | +|-----------|----------------------------------------------------------------------------------------------------------------------------|---------------------|---|----------------------|-------|-----|-------| +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n78 | E-UTRA Band 3, 5, 7, 8, 18, 19, 20, 26, 34, 39, 40, 41 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 1, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 1 | F DL_low | - | F DL_high | -50 | 1 | 9, 11 | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 9, 10 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n79 | E-UTRA Band 3, 5, 8, 18, 19, 34, 39, 40, 41 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 1, 42, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 1 | F DL_low | - | F DL_high | -50 | 1 | 9, 11 | +| | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 9, 10 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_30_n5 | E-UTRA Band 2, 4, 5, 7, 12, 13, 14, 17, 24, 25, 26, 29, 30, 38, 48, 66, 70, 71, 85 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 41, 48, 52 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_38_n78 | N/A | | | | | | | +| DC_39_n79 | E-UTRA Band 1, 8, 28, 34, 40, 41, 44, 45 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1805 | - | 1855 | -40 | 1 | 18 | +| | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 18 | +| DC_41_n77 | E-UTRA Band 1, 3, 5, 8, 11, 18, 19, 21, 26, 28, 33, 34, 39, 40, 44, 45, 73, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n78 | E-UTRA Band 1, 3, 5, 8, 11, 18, 19, 21, 26, 28, 34, 39, 40, 44, 45, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n79 | E-UTRA Band 1, 3, 5, 8, 11, 18, 19, 21, 26, 28, 34, 40, 42, 44, 45, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_42_n77 | N/A | | | | | | | +| DC_42_n78 | N/A | | | | | | | +| DC_42_n79 | N/A | | | | | | | +| DC_66_n5 | E-UTRA Band 1, 2, 3, 4, 5, 6, 7, 8, 12, 13, 14, 17, 24, 25, 26, 28, 29, 30, 34, 38, 40, 43, 45, 50, 51, 65, 66, 70, 71, 85 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 41, 42, 48, 52 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_66_n71 | E-UTRA Band 4, 5, 13, 14, 17, 24, 26, 27, 29, 30, 43, 50, 51, 66, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 2, 7, 22, 25, 41, 42, 48, 70 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | E-UTRA Band 71 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| DC_66_n78 | E-UTRA Band 1, 3, 5, 7, 8, 20, 26, 28, 34, 39, 40, 41, 65 | F DL_low | - | F DL_high | -50 | 1 | | + +| | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | $F_{DL\_low}$ and $F_{DL\_high}$ refer to each frequency band specified in Table 5.5-1 of TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2]. | +| NOTE 2: | As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2 nd , 3 rd , 4 th or 5 th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2\text{MHz} + N \times L_{CRB} \times 180\text{kHz})$ , where N is 2, 3, 4, 5 for the 2 nd , 3 rd , 4 th or 5 th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. | +| NOTE 3: | Applicable when co-existence with PHS system operating in 1884.5 -1915.7MHz. | +| NOTE 4: | Void. | +| NOTE 5: | These requirements also apply for the frequency ranges that are less than $F_{OOb}$ (MHz) in Table 6.6.3.1-1, Table 6.6.3.1A-1 in TS 36.101 [5] or in Table 6.5.3.1-1 in TS 38.101-1 [2] from the edge of the channel bandwidth. | +| NOTE 6: | This requirement is applicable for any channel bandwidths within the range 2500 - 2570 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2560.5 - 2562.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2552 - 2560 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | +| NOTE 7: | For these adjacent bands, the emission limit could imply risk of harmful interference to UE(s) operating in the protected operating band. | +| NOTE 8: | Void | +| NOTE 9: | Applicable when the assigned E-UTRA carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz. | +| NOTE 10: | As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 2nd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 2nd harmonic totally or partially overlaps the measurement bandwidth (MBW). | +| NOTE 11: | As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3rd harmonic totally or partially overlaps the measurement bandwidth (MBW). | +| NOTE 12: | This requirement is applicable only for the following cases:
A: for carriers of 5 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is within the range $902.5 \text{ MHz} \leq F_c < 907.5 \text{ MHz}$ with an uplink transmission bandwidth less than or equal to 20 RB;
B: for carriers of 5 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is within the range $907.5 \text{ MHz} \leq F_c \leq 912.5 \text{ MHz}$ without any restriction on uplink transmission bandwidth.
C: for carriers of 10 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is $F_c = 910 \text{ MHz}$ with an uplink transmission bandwidth less than or equal to 32 RB with $RB_{start} > 3$ . | +| NOTE 13: | Void. | +| NOTE 14: | This requirement is applicable for 5 and 10 MHz E-UTRA channel bandwidth allocated within 718-728MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with $RB_{start} > 1$ and $RB_{start} < 48$ . | +| NOTE 15: | Void. | +| NOTE 16: | This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 - 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | +| NOTE 17: | This requirement is applicable in the case of a 10 MHz E-UTRA carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies. | +| NOTE 18: | This requirement is only applicable for E-UTRA carriers with bandwidth confined within 1885 - 1920 MHz (requirement for carriers with at least 1RB confined within 1880 - 1885 MHz is not specified). This requirement applies for an uplink transmission bandwidth less than or equal to 54 RB for E-UTRA carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1892.5 - 1894.5 MHz and for E-UTRA carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1895 - 1903 MHz. | +| NOTE 19: | Void. | + +**Table 6.5B.3.3.2.3-2: Spurious emission band UE co-existence limits Rel-16** + +| EN-DC Configuration | Spurious emission | | | | | +|---------------------|-------------------|-----------------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | Maximum Level (dBm) | MBW (MHz) | NOTE | + +| | | | | | | | | +|----------------------------|-----------------|--------|---|--------|-------|-----|----------| +| DC_1_n3 | Frequency range | 1880 | | 1895 | -40 | 1 | 5,16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n7 | Frequency range | 1880 | | 1895 | -40 | 1 | 5,16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_1_n8 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n77 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_1_n78 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_1_n79 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_3_n1 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5,16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_3_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_3_n28 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 13 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_3_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n80_ULS
UP-TDM_n78 | | | | | | | | +| DC_3_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_7_n1 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5,16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7,16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7,16 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n3 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n5 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 7, 6 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 7, 6 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 14 | +| DC_7_n8 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n28 | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | + +| | | | | | | | | +|-----------|-----------------|--------|---|--------|-------|-------------|----------| +| DC_7_n66 | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n78 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_8_n1 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_8_n3 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| DC_8_n20 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_8_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9, 12 | +| DC_8_n41 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_8_n77 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_8_n78 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_11_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_11_n78 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_11_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_12_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_13_n2 | Frequency range | 769 | - | 775 | -35 | 0.006
25 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.006
25 | 5 | +| DC_13_n66 | Frequency range | 769 | - | 775 | -35 | 0.006
25 | 5 | +| | Frequency range | 799 | - | 803 | -35 | 0.006
25 | 5 | +| DC_14_n2 | Frequency range | 769 | - | 775 | -35 | 0.006
25 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.006
25 | 5 | +| DC_14_n66 | Frequency range | 769 | - | 775 | -35 | 0.006
25 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.006
25 | 5 | + +| | | | | | | | | +|-----------|-----------------|--------|---|--------|-------|-----|---------| +| DC_19_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n78 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_20_n1 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_20_n3 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_21_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n78 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| DC_26_n77 | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | 2 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n78 | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | 2 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n79 | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_28_n3 | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| DC_28_n7 | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_28_n77 | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | + +| | | | | | | | | +|-----------|-----------------|--------|---|--------|-------|-----|----------| +| DC_28_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_28_n79 | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_39_n41 | Frequency range | 1805 | - | 1855 | -40 | 1 | 5 | +| | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 5, 7, 19 | +| DC_39_n79 | Frequency range | 1805 | - | 1855 | -40 | 1 | 18 | +| | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 18 | +| DC_40_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_48_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | + +- NOTE 1: $F_{DL\_low}$ and $F_{DL\_high}$ refer to each frequency band specified in Table 5.5-1 in TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2]. +- NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{CRB} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. +- NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz +- NOTE 4: Void. +- NOTE 5: These requirements also apply for the frequency ranges that are less than $F_{OOb}$ (MHz) in Table 6.6.3.1-1, Table 6.6.3.1A-1 in TS 36.101 [5] or in Table 6.5.3.1-1 in TS 38.101-1 [2] from the edge of the channel bandwidth. +- NOTE 6: This requirement is applicable for any channel bandwidths within the range 2500 - 2570 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2560.5 - 2562.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2552 - 2560 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. +- NOTE 7: For these adjacent bands, the emission limit could imply risk of harmful interference to UE(s) operating in the protected operating band. +- NOTE 8: This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 - 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink +- NOTE 9: Applicable when the assigned E-UTRA or NR carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz. +- NOTE 10: As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 2nd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 2nd harmonic totally or partially overlaps the measurement bandwidth (MBW). +- NOTE 11: As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3rd harmonic totally or partially overlaps the measurement bandwidth (MBW). +- NOTE 12: This requirement is applicable only for the following cases: A: for carriers of 5 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is within the range $902.5 \text{ MHz} \leq F_c < 907.5 \text{ MHz}$ with an uplink transmission bandwidth less than or equal to 20 RB; B: for carriers of 5 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is within the range $907.5 \text{ MHz} \leq F_c \leq 912.5 \text{ MHz}$ without any restriction on uplink transmission bandwidth; C: for carriers of 10 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is $F_c = 910 \text{ MHz}$ with an uplink transmission bandwidth less than or equal to 32 RB with $RB_{start} > 3$ . +- NOTE 13: Void. +- NOTE 14: This requirement is applicable for 5 and 10 MHz E-UTRA or NR channel bandwidth allocated within 718-728MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with $RB_{start} > 1$ and $RB_{start} < 48$ . +- NOTE 15: Void. +- NOTE 16: This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 - 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. +- NOTE 17: This requirement is applicable in the case of a 10 MHz E-UTRA or NR carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies. +- NOTE 18: This requirement is only applicable for E-UTRA carriers with bandwidth confined within 1885 - 1920 MHz (requirement for carriers with at least 1RB confined within 1880 - 1885 MHz is not specified). This requirement applies for an uplink transmission bandwidth less than or equal to 54 RB for E-UTRA carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1892.5 - 1894.5 MHz and for E-UTRA carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1895 - 1903 MHz. +- NOTE 19: Void. +- NOTE 20: Void. +- NOTE 21: Void. +- NOTE 22: This requirement is applicable for power class 3 UE for any channel bandwidths within the range 2570 - 2615 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2605.5 - 2607.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2597 - 2605 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. + +**Table 6.5B.3.3.2.3-3: Spurious emission band UE co-existence limits Rel-17** + +| EN-DC Configuration | Spurious emission | | | | | | | +|------------------------|-------------------|-----------------------|---|--------|---------------------|-----------|-------------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_1_n3 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 67 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n7 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_1_n8 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n41 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 8, 20 | +| DC_1_n77 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_1_n78 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_1_n79 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_2_n7 | Frequency range | 2570 | - | 2575 | 1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_3_n1 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_3_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| rrrrrrrrrrrr | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_3_n8 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n28 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 13 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_3_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n80_ULSUP-TDM_n78 | | | | | | | | +| DC_3_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_5_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 7, 6 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 7, 6 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 14 | +| DC_5_n30 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_5_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_7_n1 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | + +| EN-DC Configuration | Spurious emission | | | | | | | +|---------------------|-------------------|-----------------------|---|--------|---------------------|-----------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n2 | Frequency range | 2570 | - | 2575 | 1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n3 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n5 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 7, 6 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 7, 6 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 14 | +| DC_7_n8 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n28 | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n66 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n71 | Frequency range | 2570 | - | 2575 | 1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n77 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n78 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n80 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_8_n1 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_8_n3 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| DC_8_n20 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_8_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9, 12 | +| DC_8_n41 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_8_n77 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_8_n78 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_11_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | + +| EN-DC
Configuration | Spurious emission | | | | | | | +|------------------------|-------------------|-----------------------|---|--------|------------------------|--------------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level
(dBm) | MBW
(MHz) | NOTE | +| DC_11_n78 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_11_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_12_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_12_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_13_n2 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_13_n5 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_13_n7 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_13_n48 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_13_n66 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 803 | -35 | 0.00625 | 5 | +| DC_13_n71 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_13_n77 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_14_n2 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_14_n30 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_14_n77 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_14_n66 | Frequency range | 769 | - | 775 | -35 | 0.00625 | 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 | 5 | +| DC_18_n3 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_18_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n1 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n78 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | + +| EN-DC
Configuration | Spurious emission | | | | | | | +|-------------------------------------------------------|-------------------|-----------------------|---|--------|---------------------|-----------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_19_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_20_n1 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_20_n3 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_20A_91A_ULSU
P-TDM,
DC_20A_92A_ULSU
P-TDM | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_21_n1 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| DC_21_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n78 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n79 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| DC_26_n77 | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n78 | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_26_n79 | Frequency range | 703 | - | 799 | -50 | 1 | | +| | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_28_n3 | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | + +| EN-DC
Configuration | Spurious emission | | | | | | | +|------------------------------------------|-------------------|-----------------------|---|--------|------------------------|--------------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level
(dBm) | MBW
(MHz) | NOTE | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| DC_28_n7 | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_28_n41
DC_28_n83_ULSUP-
TDM_n41 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n77 | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n78 | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n79 | Frequency range | 758 | - | 773 | -32 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_39_n40 | Frequency range | 1805 | - | 1855 | -40 | 1 | 18 | +| | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 5, 7, 18 | +| DC_39_n41 | Frequency range | 1805 | - | 1855 | -40 | 1 | 5 | +| | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 5, 7, 19 | +| DC_39_n79 | Frequency range | 1805 | - | 1855 | -40 | 1 | 18 | +| | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 18 | +| DC_40_n1 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_41_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_42_n1 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_42_n3 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_48_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_66_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_66_n38 | Frequency range | 2620 | - | 2645 | -15.5 | 5 | 5, 7, 22 | +| | Frequency range | 2645 | - | 2690 | -40 | 1 | 5, 22 | + + + +**Table 6.5B.3.3.2.3-4: Spurious emission band UE co-existence limits Rel-18** + +| EN-DC Configuration | Spurious emission | | | | | | | +|------------------------|-------------------|-----------------------|---|--------|---------------------|-----------|-------------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_1_n3 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 67 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n7 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_1_n8 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_1_n41 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 8, 20 | +| DC_1_n77 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_1_n78 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_1_n79 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 8 | +| DC_2_n7 | Frequency range | 2570 | - | 2575 | 1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_3_n1 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_3_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_3_n8 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n28 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 13 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_3_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n80_ULSUP-TDM_n78 | | | | | | | | +| DC_3_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_5_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 7, 6 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 7, 6 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 14 | +| DC_5_n30 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_5_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_7_n1 | Frequency range | 1880 | | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | | 1915 | -15.5 | 5 | 5, 7, 16 | + +| EN-DC Configuration | Spurious emission | | | | | | | +|---------------------|-------------------|-----------------------|---|--------|---------------------|-----------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n2 | Frequency range | 2570 | - | 2575 | 1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n3 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n5 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 7, 6 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 7, 6 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 14 | +| DC_7_n8 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n28 | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n66 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n71 | Frequency range | 2570 | - | 2575 | 1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n77 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n78 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_7_n80 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| DC_8_n1 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_8_n3 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| DC_8_n20 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_8_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9, 12 | +| DC_8_n41 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_8_n77 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_8_n78 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_11_n77 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | + +| EN-DC Configuration | Spurious emission | | | | | | +|---------------------|-------------------|-----------------------|---|---------------------|-----------|------------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_11_n78 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_11_n79 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_12_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 5, 6 | +| DC_12_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| DC_13_n2 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_13_n5 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_13_n7 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 5, 6 | +| DC_13_n48 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_13_n66 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 803 | -35 | 0.00625 5 | +| DC_13_n71 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_13_n77 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| DC_14_n2 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_14_n30 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_14_n77 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_14_n66 | Frequency range | 769 | - | 775 | -35 | 0.00625 5 | +| | Frequency range | 799 | - | 805 | -35 | 0.00625 5 | +| DC_18_n79 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_18_n3 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_18_n79 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_19_n1 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 5, 7, 16 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_19_n77 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | + +| EN-DC Configuration | Spurious emission | | | | | | +|-------------------------------------------------|-------------------|-----------------------|---|---------------------|-----------|------------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_19_n78 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_19_n79 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_20_n1 | Frequency range | 758 | - | 788 | -50 | 1 | +| DC_20_n3 | Frequency range | 758 | - | 788 | -50 | 1 | +| DC_20A_91A_ULSU P-TDM,
DC_20A_92A_ULSU P-TDM | Frequency range | 758 | - | 788 | -50 | 1 | +| DC_21_n1 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1880 | - | 1895 | -40 | 1 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 5, 7, 16 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_21_n28 | Frequency range | 470 | - | 694 | -42 | 8 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | +| | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3, 9 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| DC_21_n77 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_21_n78 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_21_n79 | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_26_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 703 | - | 799 | -50 | 1 | +| | Frequency range | 799 | - | 803 | -40 | 1 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | +| DC_26_n77 | Frequency range | 703 | - | 799 | -50 | 1 | +| | Frequency range | 799 | - | 803 | -40 | 1 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_26_n78 | Frequency range | 703 | - | 799 | -50 | 1 | +| | Frequency range | 799 | - | 803 | -40 | 1 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | +| DC_26_n79 | Frequency range | 703 | - | 799 | -50 | 1 | +| | Frequency range | 799 | - | 803 | -40 | 1 5 | +| | Frequency range | 945 | - | 960 | -50 | 1 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3 | +| | Frequency range | 2545 | - | 2575 | -50 | 1 | + +| EN-DC
Configuration | Spurious emission | | | | | | | +|------------------------------------------|-------------------|-----------------------|---|--------|---------------------|-----------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_28_n3 | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n5 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| DC_28_n7 | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | +| | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| DC_28_n41
DC_28_n83_ULSUP-
TDM_n41 | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| DC_28_n77 | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| DC_28_n78 | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 758 | - | 773 | -32 | 1 | | +| DC_28_n79 | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| | Frequency range | 1805 | - | 1855 | -40 | 1 | 18 | +| DC_39_n40 | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 5, 7, 18 | +| | Frequency range | 1805 | - | 1855 | -40 | 1 | 5 | +| DC_39_n41 | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 5, 7, 19 | +| | Frequency range | 1805 | - | 1855 | -40 | 1 | 18 | +| DC_39_n79 | Frequency range | 1855 | - | 1880 | -15.5 | 5 | 18 | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n1 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n41 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_40_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n28 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| | Frequency range | 662 | - | 694 | -26.2 | 6 | 5 | +| | Frequency range | 758 | - | 773 | -32 | 1 | 5 | +| | Frequency range | 773 | - | 803 | -50 | 1 | | +| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_41_n77 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n78 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n79 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_42_n1 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 16 | +| | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 16 | +| | Frequency range | 1915 | - | 1920 | +1.6 | 5 | 5, 7, 16 | +| DC_42_n3 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_48_n5 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_66_n7 | Frequency range | 2570 | - | 2575 | +1.6 | 5 | 5, 6, 7 | +| | Frequency range | 2575 | - | 2595 | -15.5 | 5 | 5, 6, 7 | +| | Frequency range | 2595 | - | 2620 | -40 | 1 | 5, 6 | + +| EN-DC
Configuration | Spurious emission | | | | | | | +|------------------------|-------------------|-----------------------|---|------|---------------------|-----------|----------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| DC_66_n38 | Frequency range | 2620 | - | 2645 | -15.5 | 5 | 5, 7, 22 | +| | Frequency range | 2645 | - | 2690 | -40 | 1 | 5, 22 | + +| EN-DC
Configuration | Spurious emission | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | Maximum Level (dBm) | MBW (MHz) | NOTE | +| NOTE 1: $F_{DL\_low}$ and $F_{DL\_high}$ refer to each frequency band specified in Table 5.5-1 in TS 36.101 [4] or in Table 5.2-1 in TS 38.101-1 [2]. | | | | | | +| NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [4] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2 nd , 3 rd , 4 th or 5 th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{CRB} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2 nd , 3 rd , 4 th or 5 th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. | | | | | | +| NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz | | | | | | +| NOTE 4: Void | | | | | | +| NOTE 5: These requirements also apply for the frequency ranges that are less than $F_{O\text{OB}}$ (MHz) in Table 6.6.3.1-1, Table 6.6.3.1A-1 in TS 36.101 [4] or in Table 6.5.3.1-1 in TS 38.101-1 [2] from the edge of the channel bandwidth. | | | | | | +| NOTE 6: This requirement is applicable for any channel bandwidths within the range 2500 - 2570 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2560.5 - 2562.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2552 - 2560 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | | | | | | +| NOTE 7: For these adjacent bands, the emission limit could imply risk of harmful interference to UE(s) operating in the protected operating band. | | | | | | +| NOTE 8: This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 - 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink | | | | | | +| NOTE 9: Applicable when the assigned E-UTRA or NR carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz. | | | | | | +| NOTE 10: As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 2 nd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 2nd harmonic totally or partially overlaps the measurement bandwidth (MBW). | | | | | | +| NOTE 11: As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3 rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3 rd harmonic totally or partially overlaps the measurement bandwidth (MBW). | | | | | | +| NOTE 12: This requirement is applicable only for the following cases: A: for carriers of 5 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is within the range $902.5 \text{ MHz} \leq F_c < 907.5 \text{ MHz}$ with an uplink transmission bandwidth less than or equal to 20 RB; B: for carriers of 5 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is within the range $907.5 \text{ MHz} \leq F_c \leq 912.5 \text{ MHz}$ without any restriction on uplink transmission bandwidth; C: for carriers of 10 MHz channel bandwidth when carrier centre frequency ( $F_c$ ) is $F_c = 910 \text{ MHz}$ with an uplink transmission bandwidth less than or equal to 32 RB with $RB_{start} > 3$ . | | | | | | +| NOTE 13: Void | | | | | | +| NOTE 14: This requirement is applicable for 5 and 10 MHz E-UTRA or NR channel bandwidth allocated within 718-728MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with $RB_{start} > 1$ and $RB_{start} < 48$ . | | | | | | +| NOTE 15: Void | | | | | | +| NOTE 16: This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 - 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | | | | | | +| NOTE 17: This requirement is applicable in the case of a 10 MHz E-UTRA or NR carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies. | | | | | | +| NOTE 18: This requirement is only applicable for E-UTRA carriers with bandwidth confined within 1885 - 1920 MHz (requirement for carriers with at least 1RB confined within 1880 - 1885 MHz is not specified). This requirement applies for an uplink transmission bandwidth less than or equal to 54 RB for E-UTRA carriers of 15 MHz bandwidth when carrier center frequency is within the range 1892.5 - 1894.5 MHz and for E-UTRA carriers of 20 MHz bandwidth when carrier center frequency is within the range 1895 - 1903 MHz. | | | | | | +| NOTE 19: Void | | | | | | +| NOTE 20: Void | | | | | | +| NOTE 21: Void | | | | | | +| NOTE 22: This requirement is applicable for power class 3 UE for any channel bandwidths within the range 2570 - 2615 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2605.5 - 2607.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2597 - 2605 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | | | | | | + +NOTE: To simplify the above Tables, E-UTRA band numbers are listed for bands which are specified only for E-UTRA operation or both E-UTRA and NR operation. NR band numbers are listed for bands which are specified only for NR operation. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.3.2. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 6.5B.3.3.2.4 Test description + +###### 6.5B.3.3.2.4.1 Initial conditions + +Same initial conditions as described in clause 6.5B.3.1.2.4.1 with the following exceptions: + +- Instead of Table 6.5B.3.1.2.4.1-1 --> use Table 6.5B.3.3.2.4.1-1. + +**Table 6.5B.3.3.2.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-------|------|-------|----------------------------------------|----------------------------------------|--------------------------|---------------------------|---------------------|--------------------------|-------------------------------------------------------------------|--|--|--|--| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | | | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | For test frequencies refer to "Range" columns. | | | | | | | | | | | | | | | +| Test EN-DC channel bandwidth as specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1 | Refer to "NR N RB " and "E-UTRA N RB " columns | | | | | | | | | | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | | | | | | | | | | | | | +| Test Parameters for DC Configurations | | | | | | | | | | | | | | | | +| ID | DC Configuration / N RB_agg | | | | DL Allocation | | UL Allocation (Note 1,2) | | | | | | | | | +| | DC Configuration | | | | E-UTRA Ch BW/N RB | NR Ch BW/N RB | CC MOD E-UTRA/NR | E-UTRA & NR RB allocation | CC MOD E-UTRA/NR | | | | | | | +| | E-UTRA | | NR | | | | | | | | E-UTRA & NR allocations (L CRB @ RB start ) | | | | | +| | Band | Range | Band | Range | | | | | | | | | | | | +| Default Test Settings for a DC_XA_nYA Configuration | | | | | | | | | | | | | | | | +| 1 | X | Low | nY | Low | Highest Ch BW /Highest N RB | Highest Ch BW /Highest N RB | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | | 1@0 | | | | | +| 2 | X | High | nY | High | Highest Ch BW /Highest N RB | Highest Ch BW /Highest N RB | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@RB max
x | 1@RB max
x | | | | | +| Test Setting for DC_1A_n3A Configuration | | | | | | | | | | | | | | | | +| 1 | 1 | Low | n3 | Low | 10/50 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | | 1@0 | | | | | +| 2 | 1 | High | n3 | Mid | 10/50 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@0 | | | | | +| Test Setting for DC_1A_n5A Configuration | | | | | | | | | | | | | | | | +| 1 | 1 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | | 1@0 | | | | | +| 2 | 1 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | | | | | +| Test Setting for DC_1A_n7A Configuration | | | | | | | | | | | | | | | | +| 1 | 1 | High | n7 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | | | | | +| 2 | 1 | High | n7 | Mid | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@14 | | | | | +| Test Setting for DC_1A_n8A Configuration | | | | | | | | | | | | | | | | +| 1 | 1 | Low | n8 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | | 1@0 | | | | | +| Test Setting for DC_1A_n28A Configuration | | | | | | | | | | | | | | | | +| 1 | 1 | Low | n28 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | | 1@0 | | | | | + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 2 | 1 | Low | n28 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 1 | High | n28 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | + +###### **Test Setting for DC\_1A\_n41A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 1 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@250 | +| 2 | 1 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 3 | 1 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 4 | 1 | High | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@247 | +| 5 | 1 | High | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 6 | 1 | High | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@85 | +| 7 | 1 | High | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | + +###### **Test Setting for DC\_1A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|---------|-------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 1 | High | n77 | High | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@0 | +| 2 | 1 | Low | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 3 | 1 | Low | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 4 | 1 | Low | n77 | NOTE 18 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 5 | 1 | Low | n77 | NOTE 18 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 6 | 1 | Low | n77 | NOTE 18 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 7 | 1 | Low | n77 | NOTE 18 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +| 8 | 1 | Low | n77 | NOTE 18 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +|-------------------------------------------|---|------|-----|---------|--------|---------|-------------------|----|---------------------|------|-------| +| Test Setting for DC_1A_n78A Configuration | | | | | | | | | | | | +| 1 | 1 | High | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 2 | 1 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 3 | 1 | Low | n78 | Note 8 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_1A_n79A Configuration | | | | | | | | | | | | +| 1 | 1 | Low | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@172 | +| 2 | 1 | High | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 3 | 1 | High | n79 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 4 | 1 | Low | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@201 | +| 5 | 1 | High | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| Test Setting for DC_2A_n41A Configuration | | | | | | | | | | | | +| 1 | 2 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 2 | 2 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@30 | +| 3 | 2 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@62 | +| 4 | 2 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@209 | +| 5 | 2 | High | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 6 | 2 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_2A_n48A Configuration | | | | | | | | | | | | + +| | | | | | | | | | | | | +|---|---|------|-----|-----|--------|---------|----------------------|----|---------------------------|------|------| +| 1 | 2 | High | n48 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@88 | +|---|---|------|-----|-----|--------|---------|----------------------|----|---------------------------|------|------| + +###### **Test Setting for DC\_2A\_n66A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 2 | Low | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 2 | High | n66 | High | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@215 | +| 3 | 2 | High | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 4 | 2 | High | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 5 | 2 | High | n66 | High | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@215 | + +###### **Test Setting for DC\_2A\_n71A Configuration** + +| | | | | | | | | | | | | +|---|---|-----|-----|-----|--------|--------|----------------------|----|---------------------------|-----|-----| +| 1 | 2 | Low | n71 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +|---|---|-----|-----|-----|--------|--------|----------------------|----|---------------------------|-----|-----| + +###### **Test Setting for DC\_2A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|---------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 2 | Low | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 2 | 2 | High | n77 | Note 27 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@200 | +| 3 | 2 | High | n77 | Note 27 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 4 | 2 | Low | n77 | Note 27 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@200 | + +###### **Test Setting for DC\_2A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 2 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 2 | 2 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 3 | 2 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 4 | 2 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | + +###### **Test Settings for DC\_3A\_n1A Configuration** + +| | | | | | | | | | | | | +|---|---|-----|----|------|--------|--------|-------------------|----|---------------------|------|-------| +| 1 | 3 | Low | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 3 | Low | n1 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | + +###### **Test Setting for DC\_3A\_n5A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|------|--------|--------|-------------------|----|---------------------|------|-------| +| 1 | 3 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@77 | +| 2 | 3 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | +| 3 | 3 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 4 | 3 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 5 | 3 | High | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | + +###### **Test Setting for DC\_3A\_n7A Configuration** + +| | | | | | | | | | | | | +|---|---|-----|----|------|--------|-------|-------------------|----|---------------------|------|------| +| 1 | 3 | Low | n7 | High | 20/100 | 10/52 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@47 | 1@51 | +| 2 | 3 | Mid | n7 | High | 20/100 | 10/52 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@51 | +| 3 | 3 | Low | n7 | Low | 20/100 | 10/52 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@51 | +| 4 | 3 | Mid | n7 | Low | 20/100 | 10/52 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 5 | 3 | Low | n7 | High | 20/100 | 10/52 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@51 | + +###### **Test Setting for DC\_3A\_n8A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|------|--------|--------|-------------------|----|---------------------|-------------|--------------| +| 1 | 3 | Low | n8 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 3 | High | n8 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | +| 3 | 3 | Low | n8 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@105 | + +###### **Test Settings for DC\_3A\_n28A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|--------|-------------------|----|---------------------|------|-------| +| 1 | 3 | Low | n28 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 3 | Low | n28 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@105 | +| 3 | 3 | High | n28 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | + +###### **Test Settings for DC\_3A\_n41A Configuration** + +| | | | | | | | | | | | | +|---|---|--------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 3 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 3 | High | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 3 | 3 | Mid | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 4 | 3 | Note 4 | n41 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@272 | + +###### **Test Setting for DC\_3A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|---------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 3 | Low | n77 | NOTE 19 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 3 | Low | n77 | NOTE 19 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 3 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 4 | 3 | Low | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@75 | +| 5 | 3 | Low | n77 | NOTE 19 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 3 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 7 | 3 | High | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | + +###### **Test Setting for DC\_3A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 3 | High | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +|---|---|------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| + +| | | | | | | | | | | | | +|---|---|------|-----|-----|--------|---------|----------------------|----|---------------------------|------|-------| +| 2 | 3 | High | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 3 | 3 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | + +###### **Test Settings for DC\_3A\_n79A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 3 | High | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 2 | 3 | High | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 3 | 3 | Low | n79 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 4 | 3 | High | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@134 | +| 5 | 3 | Low | n79 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@66 | + +###### **Test Settings for DC\_5A\_n2A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|------|-------|--------|------|----|---------------------------|------|--------------| +| 1 | 5 | Low | n2 | Low | 10/50 | 20/106 | QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 5 | High | n2 | High | 10/50 | 20/106 | QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@105 | + +###### **Test Settings for DC\_5A\_n66A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|-------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 5 | High | n66 | Mid | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@0 | +| 2 | 5 | High | n66 | High | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@215 | +| 3 | 5 | Low | n66 | Low | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@215 | +| 4 | 5 | High | n66 | Low | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@0 | + +###### **Test Setting for DC\_5A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|-----|-------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 5 | High | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@0 | +| 2 | 5 | Low | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | + +| | | | | | | | | | | | | +|---|---|------|-----|---------|-------|---------|-------------------|----|---------------------|------|-------| +| 3 | 5 | Low | n77 | Note 28 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@272 | +| 4 | 5 | Low | n77 | Note 28 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 5 | 5 | Low | n77 | Note 28 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 5 | Low | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 7 | 5 | High | n77 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@272 | +| 8 | 5 | High | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@140 | + +###### **Test Setting for DC\_5A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|-------|---------|-------------------|----|---------------------|------|-------| +| 1 | 5 | Low | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 2 | 5 | Low | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 3 | 5 | Low | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 4 | 5 | High | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@29 | +| 5 | 5 | Low | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | + +###### **Test Setting for DC\_7A\_n1A Configuration** + +| | | | | | | | | | | | | +|---|---|-----|----|------|--------|--------|-------------------|----|---------------------|------|-------| +| 1 | 7 | Low | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 7 | Low | n1 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@105 | +| 3 | 7 | Mid | n1 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@22 | 1@105 | + +###### **Test Setting for DC\_7A\_n3A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|-----|--------|--------|-------------------|----|---------------------|------|------| +| 1 | 7 | High | n3 | Low | 20/100 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@77 | +|---|---|------|----|-----|--------|--------|-------------------|----|---------------------|------|------| + +| | | | | | | | | | | | | +|---|---|------|----|------|--------|--------|----------------------|----|---------------------------|------|------| +| 2 | 7 | Low | n3 | Low | 20/100 | 30/160 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@59 | +| 3 | 7 | High | n3 | High | 20/100 | 30/160 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@86 | +| 4 | 7 | High | n3 | Low | 10/50 | 5/25 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@0 | +| 5 | 7 | High | n3 | Low | 20/100 | 30/160 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 6 | 7 | Low | n3 | Mid | 20/100 | 30/160 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@66 | + +###### **Test Setting for DC\_7A\_n5A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 7 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 2 | 7 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_7A\_n8A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|-----|--------|--------|----------------------|----|---------------------------|-------------|--------------| +| 1 | 7 | High | n8 | Mid | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 2 | 7 | High | n8 | Mid | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 3 | 7 | Low | n8 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_7A\_n28A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 7 | High | n28 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +|---|---|------|-----|------|--------|--------|----------------------|----|---------------------------|------|-------| + +###### **Test Setting for DC\_7A\_n66A Configuration** + +| | | | | | | | | | | | | +|---|---|-----|-----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 7 | Low | n66 | High | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@215 | +| 2 | 7 | Low | n66 | High | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 7 | Mid | n66 | High | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@50 | 1@215 | +| 4 | 7 | Low | n66 | High | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@215 | + +| | | | | | | | | | | | | +|---|---|------|-----|-----|--------|--------|-------------------|----|---------------------|------|-----| +| 5 | 7 | Mid | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 6 | 7 | High | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | + +###### **Test Setting for DC\_7A\_n78A Configuration** + +| | | | | | | | | | | | | +|----|---|------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 7 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 7 | Mid | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 3 | 7 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@196 | +| 4 | 7 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 5 | 7 | High | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@77 | 1@0 | +| 6 | 7 | Mid | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 7 | 7 | High | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 8 | 7 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 9 | 7 | High | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 10 | 7 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@165 | + +###### **Test Settings for DC\_8A\_n1A Configuration** + +| | | | | | | | | | | | | +|---|---|-----|----|-----|-------|--------|-------------------|----|---------------------|-----|-----| +| 1 | 8 | Low | n1 | Low | 10/50 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +|---|---|-----|----|-----|-------|--------|-------------------|----|---------------------|-----|-----| + +###### **Test Settings for DC\_8A\_n3A Configuration** + +| | | | | | | | | | | | | +|---|---|------|----|-----|-------|--------|-------------------|----|---------------------|------|-------| +| 1 | 8 | High | n3 | Low | 10/50 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@0 | +| 2 | 8 | Low | n3 | Low | 10/50 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@159 | + +| | | | | | | | | | | | | +|---|---|------|----|------|-------|--------|----------------------|----|---------------------------|------|-------| +| 3 | 8 | High | n3 | High | 10/50 | 30/160 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@159 | +|---|---|------|----|------|-------|--------|----------------------|----|---------------------------|------|-------| + +###### **Test Settings for DC\_8A\_n20A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|-------|--------|----------------------|----|---------------------------|-------------|-------| +| 1 | 8 | High | n20 | Low | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@12 | +| 2 | 8 | High | n20 | High | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@105 | +| 3 | 8 | Low | n20 | Low | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +###### **Test Settings for DC\_8A\_n28A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|-------|--------|----------------------|----|---------------------------|-------------|--------------| +| 1 | 8 | High | n28 | High | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@105 | +| 2 | 8 | Low | n28 | Low | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | + +###### **Test Settings for DC\_8A\_n41A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|-------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 8 | Low | n41 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 8 | Low | n41 | High | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 3 | 8 | Low | n41 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 4 | 8 | High | n41 | High | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@272 | +| 5 | 8 | Low | n41 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@155 | + +###### **Test Settings for DC\_8A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|--------|-------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 8 | Low | n77 | Note 9 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 8 | High | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@37 | +| 3 | 8 | High | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@97 | +| 4 | 8 | Low | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@211 | + +| | | | | | | | | | | | | +|----|---|------|-----|--------|-------|---------|-------------------|----|---------------------|------|-------| +| 5 | 8 | Low | n77 | Note 9 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 8 | High | n77 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@272 | +| 7 | 8 | High | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@0 | +| 8 | 8 | Low | n77 | Note 9 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 9 | 8 | High | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@85 | +| 10 | 8 | Low | n77 | Note 9 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@0 | + +###### **Test Settings for DC\_8A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|---|------|-----|------|-------|---------|-------------------|----|---------------------|------|-------| +| 1 | 8 | High | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@272 | +| 2 | 8 | High | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 8 | Low | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@272 | +| 4 | 8 | High | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 5 | 8 | High | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@0 | +| 6 | 8 | Mid | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@25 | 1@0 | + +###### **Test Settings for DC\_11A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|----|-----|-----|---------|-------|---------|-------------------|----|---------------------|-----|-------| +| 1 | 11 | Low | n77 | Note 10 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 11 | Low | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 11 | Low | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@63 | +| 4 | 11 | Low | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@104 | + +| | | | | | | | | | | | | +|----|----|-----|-----|---------|-------|---------|-------------------|----|---------------------|-----|------| +| 5 | 11 | Low | n77 | Note 10 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 11 | Low | n77 | Note 10 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 7 | 11 | Low | n77 | Note 10 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 8 | 11 | Low | n77 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@75 | +| 9 | 11 | Low | n77 | Note 10 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 10 | 11 | Low | n77 | Note 10 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | + +###### **Test Settings for DC\_11A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|----|-----|-----|---------|-------|---------|-------------------|----|---------------------|-----|-------| +| 1 | 11 | Low | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@184 | +| 2 | 11 | Low | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 11 | Low | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@63 | +| 4 | 11 | Low | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@104 | +| 5 | 11 | Low | n78 | Note 11 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 11 | Low | n78 | Note 11 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 7 | 11 | Low | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@75 | + +###### **Test Settings for DC\_11A\_n79A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|-------|---------|-------------------|----|---------------------|------|-------| +| 1 | 11 | Low | n79 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 2 | 11 | Low | n79 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@132 | +| 3 | 11 | High | n79 | High | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@30 | + +| | | | | | | | | | | | | +|---------------------------------------------------|----|------|-----|---------|-------|---------|----------------------|----|---------------------------|------|-------| +| 4 | 11 | Low | n79 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| Test Setting for DC_12A_n2A Configuration | | | | | | | | | | | | +| 1 | 12 | HIGH | n2 | HIGH | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@105 | +| Test Setting for DC_12A_n66A Configuration | | | | | | | | | | | | +| 1 | 12 | Low | n66 | Low | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 12 | High | n66 | High | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@215 | +| 3 | 12 | Low | n66 | High | 10/50 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@215 | +| Test Setting for DC_12A_n78A Configuration | | | | | | | | | | | | +| 1 | 12 | Low | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 12 | High | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@272 | +| 3 | 12 | Low | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@136 | +| Test Setting for DC_13A_n2A Configuration | | | | | | | | | | | | +| 1 | 13 | Low | n2 | Low | 10/50 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| Test Setting for DC_13A_n77A Configuration | | | | | | | | | | | | +| 1 | 13 | Mid | n77 | Note 29 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@272 | +| 2 | 13 | Mid | n77 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@0 | +| 3 | 13 | Mid | n77 | Note 29 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@210 | +| 4 | 13 | Low | n77 | Note 29 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 5 | 13 | Low | n77 | Note 29 | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 6 | 13 | High | n77 | HIGH | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@272 | + +| | | | | | | | | | | | | +|---------------------------------------------------|----|------|-----|---------|-------|---------|-------------------|----|---------------------|------|-------| +| 7 | 13 | Low | n77 | LOW | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_14A_n2A Configuration | | | | | | | | | | | | +| 1 | 14 | Low | n2 | Low | 10/50 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_14A_n66A Configuration | | | | | | | | | | | | +| 1 | 14 | Low | n66 | Low | 10/50 | 40/216 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 14 | High | n66 | High | 10/50 | 40/216 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@215 | +| Test Setting for DC_19A_n1A Configuration | | | | | | | | | | | | +| 1 | 19 | Low | n1 | Low | 15/75 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_19A_n77A Configuration | | | | | | | | | | | | +| 1 | 19 | Low | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 2 | 19 | Low | n77 | Note 26 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 19 | High | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@0 | +| 4 | 19 | Low | n77 | Note 26 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 5 | 19 | Low | n77 | Note 26 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 19 | Low | n77 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 7 | 19 | Low | n77 | Note 26 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_19A_n78A Configuration | | | | | | | | | | | | +| 1 | 19 | High | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@272 | +| 2 | 19 | Low | n78 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 19 | High | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@0 | + +| | | | | | | | | | | | | +|---------------------------------------------------|----|------|-----|---------|--------|---------|-------------------|----|---------------------|-------------|--------------| +| 4 | 19 | Low | n78 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@165 | +| 5 | 19 | Low | n78 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 6 | 19 | Low | n78 | Note 17 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_19A_n79A Configuration | | | | | | | | | | | | +| 1 | 19 | Low | n79 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_20A_n1A Configuration | | | | | | | | | | | | +| 1 | 20 | Low | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 20 | High | n1 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | +| Test Setting for DC_20A_n3A Configuration | | | | | | | | | | | | +| 1 | 20 | Low | n3 | Low | 20/100 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 20 | High | n3 | High | 20/100 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@159 | +| 3 | 20 | Low | n3 | High | 20/100 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@159 | +| Test Setting for DC_20A_n7A Configuration | | | | | | | | | | | | +| 1 | 20 | High | n7 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 2 | 20 | High | n7 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | +| 3 | 20 | Low | n7 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 4 | 20 | High | n7 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_20A_n8A Configuration | | | | | | | | | | | | +| 1 | 20 | Low | n8 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 20 | High | n8 | High | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | + +| | | | | | | | | | | | | +|---------------------------------------------------|----|------|-----|------------|--------|---------|----------------------|----|---------------------------|-------------|--------------| +| 3 | 20 | Low | n8 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | +| Test Setting for DC_20A_n28A Configuration | | | | | | | | | | | | +| 1 | 20 | Low | n28 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | +| Test Setting for DC_20A_n78A Configuration | | | | | | | | | | | | +| 1 | 20 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 2 | 20 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 20 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@205 | +| 4 | 20 | High | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@104 | +| 5 | 20 | Low | n78 | Note
24 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| Test Setting for DC_21A_n1A Configuration | | | | | | | | | | | | +| 1 | 21 | Low | n1 | Low | 15/75 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 21 | High | n1 | High | 15/75 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@74 | 1@105 | +| 3 | 21 | Low | n1 | Low | 15/75 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | +| Test Setting for DC_21A_n28A Configuration | | | | | | | | | | | | +| 1 | 21 | Low | n28 | Low | 15/75 | 5/25 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| Test Setting for DC_21A_n77A Configuration | | | | | | | | | | | | +| 1 | 21 | Low | n77 | Note
21 | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 21 | Low | n77 | Low | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 21 | Low | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@174 | +| 4 | 21 | Low | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@215 | + +| | | | | | | | | | | | | +|----|----|------|-----|---------|-------|---------|----------------------|----|---------------------------|------|-------| +| 5 | 21 | High | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@74 | 1@0 | +| 6 | 21 | Low | n77 | Note 21 | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 7 | 21 | Low | n77 | Note 21 | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 8 | 21 | Low | n77 | Low | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@130 | +| 9 | 21 | Low | n77 | Note 21 | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 10 | 21 | High | n77 | High | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@74 | 1@0 | + +###### **Test Setting for DC\_21A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|---------|-------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 21 | Low | n78 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 2 | 21 | Low | n78 | Low | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 21 | High | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@74 | 1@272 | +| 4 | 21 | Low | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@215 | +| 5 | 21 | High | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@74 | 1@0 | +| 6 | 21 | Low | n78 | Note 20 | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 7 | 21 | Low | n78 | Low | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@130 | + +###### **Test Setting for DC\_21A\_n79A Configuration** + +| | | | | | | | | | | | | +|---|----|-----|-----|------|-------|---------|----------------------|----|---------------------------|-----|-------| +| 1 | 21 | Low | n79 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 2 | 21 | Low | n79 | Low | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 21 | Low | n79 | High | 15/75 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@38 | + +| | | | | | | | | | | | | +|---|----|-----|-----|---------|-------|---------|-------------------|----|---------------------|-----|-----| +| 4 | 21 | Low | n79 | Note 22 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +|---|----|-----|-----|---------|-------|---------|-------------------|----|---------------------|-----|-----| + +###### **Test Setting for DC\_25A\_n41A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 25 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 2 | 25 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@30 | +| 3 | 25 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@62 | +| 4 | 25 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@209 | +| 5 | 25 | High | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 6 | 25 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_25A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|----|-----|-----|---------|--------|---------|-------------------|----|---------------------|-----|-------| +| 1 | 25 | Low | n77 | Note 34 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@200 | +|---|----|-----|-----|---------|--------|---------|-------------------|----|---------------------|-----|-------| + +###### **Test Setting for DC\_26A\_n41A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|-------|---------|-------------------|----|---------------------|------|-------| +| 1 | 26 | High | n41 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@272 | +| 2 | 26 | Low | n41 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@12 | +| 3 | 26 | Low | n41 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@41 | +| 4 | 26 | High | n41 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@0 | +| 5 | 26 | Low | n41 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@232 | +| 6 | 26 | High | n41 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@25 | + +###### **Test Setting for DC\_26A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|----|-----|-----|-----|-------|---------|-------------------|----|---------------------|-----|-------| +| 1 | 26 | Low | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +|---|----|-----|-----|-----|-------|---------|-------------------|----|---------------------|-----|-------| + +| | | | | | | | | | | | | +|---|----|------|-----|---------|-------|---------|-------------------|----|---------------------|------|-------| +| 2 | 26 | Low | n77 | NOTE 25 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 26 | High | n77 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@34 | +| 4 | 26 | Low | n77 | NOTE 25 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 5 | 26 | Low | n77 | NOTE 25 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 6 | 26 | Low | n77 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@201 | +| 7 | 26 | Low | n77 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 8 | 26 | Low | n77 | NOTE 25 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_26A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|---------|-------|---------|-------------------|----|---------------------|------|-------| +| 1 | 26 | Low | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 2 | 26 | Low | n78 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 26 | High | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@74 | 1@34 | +| 4 | 26 | Low | n78 | Mid | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@78 | +| 5 | 26 | Low | n78 | Low | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@201 | +| 6 | 26 | Low | n78 | Note 13 | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_26A\_n79A Configuration** + +N/A (Note 14) + +###### **Test Setting for DC\_28A\_n3A Configuration** + +| | | | | | | | | | | | | +|---|----|------|----|------|--------|--------|-------------------|----|---------------------|------|-------| +| 1 | 28 | Low | n3 | Low | 20/100 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 28 | High | n3 | High | 20/100 | 30/160 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@159 | + +| | | | | | | | | | | | | +|---|----|------|----|-----|--------|--------|----------------------|----|---------------------------|------|-----| +| 3 | 28 | High | n3 | Low | 20/100 | 30/160 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +|---|----|------|----|-----|--------|--------|----------------------|----|---------------------------|------|-----| + +###### **Test Setting for DC\_28A\_n5A Configuration** + +| | | | | | | | | | | | | +|---|----|------|----|------|--------|--------|----------------------|----|---------------------------|-------------|------------| +| 1 | 28 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 2 | 28 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 28 | High | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | + +###### **Test Setting for DC\_28A\_n7A Configuration** + +| | | | | | | | | | | | | +|---|----|------|----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 28 | High | n7 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +|---|----|------|----|------|--------|--------|----------------------|----|---------------------------|------|-------| + +###### **Test Setting for DC\_28A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 28 | High | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 2 | 28 | Low | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@158 | +| 3 | 28 | High | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@130 | +| 4 | 28 | Low | n77 | Note
23 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 5 | 28 | Low | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 6 | 28 | Low | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 7 | 28 | Low | n77 | Note
23 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_28A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|-------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 28 | Low | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 28 | High | n78 | High | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@272 | +| 3 | 28 | Mid | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@49 | 1@272 | + +| | | | | | | | | | | | | +|----------------------------------------------------|----|------|-----|---------|--------|---------|-------------------|----|---------------------|------|-------| +| 4 | 28 | High | n78 | Low | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@190 | +| 5 | 28 | High | n78 | Mid | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Setting for DC_28A_n79A Configuration | | | | | | | | | | | | +| 1 | 28 | High | n79 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| Test Setting for DC_30A_n5A Configuration | | | | | | | | | | | | +| 1 | 30 | High | n5 | High | 10/50 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@105 | +| Test Setting for DC_30A_n77A Configuration | | | | | | | | | | | | +| 1 | 30 | High | n77 | Note 35 | 10/50 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@100 | +| Test Settings for DC_39A_n41A Configuration | | | | | | | | | | | | +| 1 | 39 | High | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| Test Settings for DC_39A_n79A Configuration | | | | | | | | | | | | +| 1 | 39 | Low | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@146 | +| 2 | 39 | Low | n79 | Note 5 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| Test Settings for DC_40A_n1A Configuration | | | | | | | | | | | | +| 1 | 40 | Low | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 40 | High | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@105 | +| 3 | 40 | High | n1 | Mid | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@56 | +| 4 | 40 | High | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@77 | +| 5 | 40 | High | n1 | Low | 20/100 | 20/106 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@39 | +| Test Settings for DC_40A_n41A Configuration | | | | | | | | | | | | +| 1 | 40 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | + +| | | | | | | | | | | | | +|---|----|------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| +| 2 | 40 | High | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 3 | 40 | Mid | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@50 | 1@272 | +| 4 | 40 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | + +###### **Test Settings for DC\_40A\_n78A Configuration** + +| | | | | | | | | | | | | +|----|----|------|-----|------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 40 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@79 | +| 2 | 40 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@110 | +| 3 | 40 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 4 | 40 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@234 | +| 5 | 40 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@29 | +| 6 | 40 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@50 | +| 7 | 40 | Low | n78 | High | 15/75 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | +| 8 | 40 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 9 | 40 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@110 | +| 10 | 40 | Low | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@155 | +| 11 | 40 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@183 | +| 12 | 40 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@272 | + +###### **Test Settings for DC\_40A\_n79A Configuration** + +| | | | | | | | | | | | | +|---|----|-----|-----|-----|--------|--------|-------------------|----|---------------------|-----|--------------| +| 1 | 40 | Low | n79 | Low | 20/100 | 50/270 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@269 | +|---|----|-----|-----|-----|--------|--------|-------------------|----|---------------------|-----|--------------| + +| | | | | | | | | | | | | +|---|----|------|-----|------|--------|--------|-------------------|----|---------------------|------|--------------| +| 2 | 40 | High | n79 | Low | 20/100 | 50/270 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 3 | 40 | High | n79 | High | 20/100 | 50/270 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@269 | + +###### **Test Settings for DC\_41A\_n28A Configuration** + +| | | | | | | | | | | | | +|---|----|---------|-----|------|--------|-------|-------------------|----|---------------------|------|------| +| 1 | 41 | High | n28 | Low | 20/100 | 15/79 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 41 | Note 33 | n28 | High | 5/25 | 15/79 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@78 | +| 3 | 41 | Mid | n28 | Low | 10/50 | 15/79 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@49 | 1@78 | + +###### **Test Settings for DC\_41A\_n77A Configuration** + +| | | | | | | | | | | | | +|----|----|------|-----|---------|--------|---------|-------------------|----|---------------------|------|-------| +| 1 | 41 | Mid | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 2 | 41 | Low | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@185 | +| 3 | 41 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@57 | +| 4 | 41 | Low | n77 | Note 15 | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@0 | +| 5 | 41 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | +| 6 | 41 | High | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@201 | +| 7 | 41 | Mid | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@46 | +| 8 | 41 | Low | n77 | Low | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@214 | +| 9 | 41 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@0 | 1@29 | +| 10 | 41 | High | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@272 | +| 11 | 41 | Mid | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM QPSK | NA | QPSK / CP-OFDM QPSK | 1@99 | 1@0 | + +| | | | | | | | | | | | | +|--------|----|------|-----|------------|--------|---------|--------------------------|----|-------------------------------|------|-------| +| 1
2 | 41 | Low | n77 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@0 | +| 1
3 | 41 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@272 | +| 1
4 | 41 | Mid | n77 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@0 | +| 1
5 | 41 | High | n77 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@161 | +| 1
6 | 41 | High | n77 | High | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@122 | +| 1
7 | 41 | Mid | n77 | Mid | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@27 | +| 1
8 | 41 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@240 | +| 1
9 | 41 | Mid | n77 | Note
15 | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@125 | + +###### **Test Settings for DC\_41A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|-----|--------|---------|--------------------------|----|-------------------------------|------|-------| +| 1 | 41 | High | n78 | Mid | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@0 | +| 2 | 41 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@185 | +| 3 | 41 | High | n78 | Mid | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@272 | +| 4 | 41 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@0 | +| 5 | 41 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@0 | 1@214 | +| 6 | 41 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@69 | +| 7 | 41 | Low | n78 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@0 | +| 8 | 41 | High | n78 | Low | 20/100 | 100/273 | QPSK/CP-
OFDM
QPSK | NA | QPSK /
CP-
OFDM
QPSK | 1@99 | 1@161 | + +| | | | | | | | | | | | | +|----|----|-----|-----|-----|--------|---------|----------------------|----|---------------------------|------|------| +| 9 | 41 | Mid | n78 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 10 | 41 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@98 | + +###### **Test Settings for DC\_41A\_n79A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 41 | Low | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 41 | High | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 3 | 41 | High | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@188 | +| 4 | 41 | High | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@93 | +| 5 | 41 | Mid | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 6 | 41 | High | n79 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@151 | +| 7 | 41 | High | n79 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 8 | 41 | Low | n79 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +###### **Test Setting for DC\_42A\_n77A Configuration** + +N/A (Note 14) + +###### **Test Settings for DC\_48A\_n5A Configuration** + +| | | | | | | | | | | | | +|---|----|------|----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 48 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | +| 2 | 48 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 3 | 48 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +###### **Test Settings for DC\_48A\_n66A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|-----|--------|--------|----------------------|----|---------------------------|-----|-----| +| 1 | 48 | High | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +|---|----|------|-----|-----|--------|--------|----------------------|----|---------------------------|-----|-----| + +###### **Test Settings for DC\_66A\_n2A Configuration** + +| | | | | | | | | | | | | +|---|----|------|----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 66 | Low | n2 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 66 | High | n2 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 3 | 66 | Low | n2 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | +| 4 | 66 | Low | n2 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@105 | +| 5 | 66 | Low | n2 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@46 | + +###### **Test Settings for DC\_66A\_n5A Configuration** + +| | | | | | | | | | | | | +|---|----|------|----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 66 | Low | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 2 | 66 | High | n5 | High | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@105 | +| 3 | 66 | Low | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | +| 4 | 66 | High | n5 | Low | 20/100 | 20/106 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | + +###### **Test Settings for DC\_66A\_n41A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 66 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 2 | 66 | Low | n41 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | +| 3 | 66 | High | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@59 | +| 4 | 66 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@248 | +| 5 | 66 | High | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@89 | +| 6 | 66 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@218 | +| 7 | 66 | High | n41 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | + +| | | | | | | | | | | | | +|----|----|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 8 | 66 | Low | n41 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@186 | +| 9 | 66 | Low | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@203 | +| 10 | 66 | High | n41 | Low | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@0 | + +###### **Test Settings for DC\_66A\_n71A Configuration** + +N/A (Note 14) + +###### **Test Setting for DC\_66A\_n77A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|---------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 66 | High | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 2 | 66 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@110 | +| 3 | 66 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@166 | +| 4 | 66 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@220 | +| 5 | 66 | High | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@100 | +| 6 | 66 | High | n77 | Note 30 | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | +| 7 | 66 | High | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@50 | +| 8 | 66 | Low | n77 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@196 | +| 9 | 66 | Low | n77 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@47 | + +###### **Test Settings for DC\_66A\_n78A Configuration** + +| | | | | | | | | | | | | +|---|----|------|-----|------|--------|---------|----------------------|----|---------------------------|------|-------| +| 1 | 66 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@143 | +| 2 | 66 | High | n78 | High | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@99 | 1@272 | +| 3 | 66 | Low | n78 | Mid | 20/100 | 100/273 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@272 | + +###### **Test Settings for DC\_71A\_n2A Configuration** + +| | | | | | | | | | | | | +|----------------------------------------------------|----|------|-----|------|--------|--------|----------------------|----|---------------------------|------|-------| +| 1 | 71 | HIGH | n2 | HIGH | 20/100 | 20/106 | CP-OFDM
QPSK | NA | CP-OFDM
QPSK | 1@99 | 1@105 | +| Test Settings for DC_71A_n66A Configuration | | | | | | | | | | | | +| 1 | 71 | Low | n66 | Low | 20/100 | 40/216 | QPSK/CP-OFDM
QPSK | NA | QPSK /
CP-OFDM
QPSK | 1@0 | 1@0 | + +- Note 1: Use DC Configuration – specific test points if present in the table, otherwise use test points from matching Group Test Settings, if present in the table. Otherwise use the Default Test Settings test points. +- Note 2: X, nY correspond to the different bands in the DC Configuration. E.g. for DC\_1A\_n3A, X=1, nY=n3. +- Note 3: Void. +- Note 4: Test Point ID 4 for DC\_3A\_n41A have the centre carrier frequency of 1773 MHz in Band 3 (EARFCN=19830). +- Note 5: Test Point ID 4 for DC\_39A\_n79A has the centre carrier frequency of 4649.96 MHz in Band 79 (NR ARFCN=709998). +- Note 6: Void. +- Note 7: Void. +- Note 8: Test Point ID 3 for DC\_1A\_n78A has the centre carrier frequency of 3473.43 MHz in Band 78 (NR ARFCN=631562). +- Note 9: Test Point ID 1 for DC\_8A\_n77A has the centre carrier frequency of 3950.13 MHz in Band n77 (NR ARFCN=663342). Test Point ID 5 has the centre carrier frequency of 3524.55 MHz in Band n77 (NR ARFCN=634970). Test Point ID 8 has the centre carrier frequency of 3584.55 MHz in Band n77 (NR ARFCN=638970). Test Point ID 10 has centre carrier frequency of 3500 MHz in Band n77 (NR ARFCN=633333). +- Note 10: Test Point ID 1 for DC\_11A\_n77A has the centre carrier frequency of 3617.43 MHz in Band n77 (NR ARFCN=641162). Test Point ID 5 has the centre carrier frequency of 3686.43 MHz in Band n77 (NR ARFCN=645762). Test Point ID 6 has the centre carrier frequency of 3494.94 MHz in Band n77 (NR ARFCN=632996). Test Point ID 7 has the centre carrier frequency of 3858.42 MHz in Band n77 (NR ARFCN=657228). Test Point ID 9 has the centre carrier frequency of 4037.43 MHz in Band n77 (NR ARFCN=669162). Test Point ID 10 has the centre carrier frequency of 4097.43 MHz in Band n77 (NR ARFCN=673162). +- Note 11: Test Point ID 5 for DC\_11A\_n78A has the centre carrier frequency of 3686.43 MHz in Band n78 (NR ARFCN=645762). Test Point ID 6 has the centre carrier frequency of 3494.94 MHz in Band n78 (NR ARFCN=632996). +- Note 12: Void. +- Note 13: Test Point ID 6 for DC\_26A\_n78A has the centre carrier frequency of 3483.78 MHz in Band n78 (NR ARFCN=632252). +- Note 14: Test case not applicable for the EN-DC configuration as no IM products occurs in the protected bands. For EN-DC only capable devices, the test requirements as in clause 6.5.3.2.5 in TS 38.521-1 [8] is needed. +- Note 15: Test Point ID 4 for DC\_41A\_n77A has the centre carrier frequency of 3488.55 MHz in Band n77 (NR ARFCN=632570). Test Point ID 19 has the centre carrier frequency of 3500 MHz in Band n77 (NR ARFCN=633333). +- Note 16: Void. +- Note 17: Test Point ID 6 for DC\_19A\_n78A has the centre carrier frequency of 3499.8 MHz in Band n78 (NR ARFCN=633320). +- Note 18: Test Point ID 4 for DC\_1A\_n77A has the centre carrier frequency of 3472.95 MHz in Band n77 (NR ARFCN=631530). Test Point ID 5 has the centre carrier frequency of 3987.03 MHz in Band n77 (NR ARFCN=665802). Test Point ID 6 has the centre carrier frequency of 3857.04 MHz in Band n77 (NR ARFCN=657136). Test Point ID 7 has the centre carrier frequency of 3874.53 MHz in Band n77 (NR ARFCN=658302). Test Point ID 8 has the centre carrier frequency of 3887.04 MHz in Band n77 (NR ARFCN=659136). +- Note 19: Test Point ID 1 for DC\_3A\_n77A has the centre carrier frequency of 3900.03 MHz in Band n77 (NR ARFCN=660002). Test Point ID 2 has the centre carrier frequency of 3602.55 MHz in Band n77 (NR ARFCN=640170). Test Point ID 5 has the centre carrier frequency of 3660.15 MHz in Band n77 (NR ARFCN=644010). +- Note 20: Test Point ID 6 for DC\_21A\_n78A has the centre carrier frequency of 3515.19 MHz in Band n78 (NR ARFCN=634346). +- Note 21: Test Point ID 1 for DC\_21A\_n77A has the centre carrier frequency of 3637.68 MHz in Band n77 (NR ARFCN=642512). Test Point ID 6 has the centre carrier frequency of 3515.19 MHz in Band n77 (NR ARFCN=634346). Test Point ID 7 has the centre carrier frequency of 3898.92 MHz in Band n77 (NR ARFCN=659928). Test Point ID 9 has the centre carrier frequency of 4057.68 MHz in Band n77 (NR ARFCN=670512). +- Note 22: Test Point ID 4 for DC\_21A\_n79A has the centre carrier frequency of 4846.53 MHz in Band n79 (NR ARFCN=723102). +- Note 23: Test Point ID 4 for DC\_28A\_n77A has the centre carrier frequency of 3474.63 MHz in Band n77 (NR ARFCN=631642). Test Point ID 7 for have the centre carrier frequency of 3597.12 MHz in Band n77 (NR ARFCN=639808). +- Note 24: Test Point ID 5 for DC\_20A\_n78A has the centre carrier frequency of 3477.03 MHz in Band n78 (NR ARFCN=631802). +- Note 25: Test Point ID 2 for DC\_26A\_n77A has the centre carrier frequency of 3521.13 MHz in Band n77 (NR ARFCN=634742). Test Point ID 4 has the centre carrier frequency of 3578.73 MHz in Band n77 (NR ARFCN=638582). Test Point ID 5 has the centre carrier frequency of 4028.64 MHz in Band n77 (NR ARFCN=668576). Test Point ID 8 has the centre carrier frequency of 3483.78 MHz in Band n77 (NR ARFCN=632252). +- Note 26: Test Point ID 2 for DC\_19A\_n77A has the centre carrier frequency of 3553.14 MHz in Band n77 (NR ARFCN=636876). Test Point ID 4 has the centre carrier frequency of 4060.62 MHz in Band n77 (NR ARFCN=670708). Test Point ID 5 has the centre carrier frequency of 3610.74 MHz in Band n77 (NR + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ARFCN=640716). Test Point ID 7 has the centre carrier frequency of 3499.8 MHz in Band n77 (NR ARFCN=633320). | +| Note 27: | Test Point ID 2 for DC_2A_n77A has the centre carrier frequency of 3900 MHz in Band n77 (NR ARFCN=660000). Test Point ID 3 has the centre carrier frequency of 4000 MHz in Band n77 (NR ARFCN=666667). Test Point ID 4 has the centre frequency of 3500 MHz in Band n77 (NR ARFCN=633333). | +| Note 28: | Test Point ID 3 for DC_5A_n77A has the centre carrier frequency of 4000 MHz in Band n77 (NR ARFCN=666667). Test Point ID 4 has the centre carrier frequency of 3600 MHz in Band n77 (NR ARFCN=640000). Test Point ID 5 has the centre carrier frequency of 3658.14 MHz in Band n77 (NR ARFCN=643876). | +| Note 29: | Test Point ID 1 for DC_13A_n77A has the centre carrier frequency of 3500 MHz in Band n77 (NR ARFCN=633333). Test Point ID 3 has the centre carrier frequency of 3880 MHz in Band n77 (NR ARFCN=658668). Test Point ID 4 has the centre carrier frequency of 3611.64 MHz in Band n77 (NR ARFCN=640776). Test Point ID 5 has the centre carrier frequency of 3504.24 MHz in Band n77 (NR ARFCN=633616). | +| Note 30: | Test Point ID 6 for DC_66A_n77A has the centre carrier frequency of 3900 MHz in Band n77 (NR ARFCN=660000). | +| Note 31: | Test Point ID 2 for DC_18A_n77A have the centre carrier frequency of 3441,39 MHz in Band n77 (NR ARFCN=649400). Test Point ID 3 and 5 for DC_18A_n77A have the centre carrier frequency of 3602,55 MHz in Band n77 (NR ARFCN=640170). Test Point ID 4 for DC_18A_n77A have the centre carrier frequency of 4049,76 MHz in Band n77 (NR ARFCN=669984). | +| Note 32: | Test Point ID 2 for DC_18A_n78A have the centre carrier frequency of 3441,39 MHz in Band n78 (NR ARFCN=629400). Test Point ID 3 for DC_18A_n78A have the centre carrier frequency of 3602,55 MHz in Band n78 (NR ARFCN=640170). | +| Note 33: | Test Point ID 2 for DC_41A_n28 A and Band 41 is defined as a carrier with CBW=5MHz and centre frequency at 2660.1MHz (NR ARFCN=532020). | +| Note 34: | Test Point ID 1 for DC_25A_n77A has the centre frequency of 3500 MHz in Band n77 (NR ARFCN=633333) | +| Note 35: | Test Point ID 1 for DC_30A_n77A has the centre carrier frequency of 4000 MHz in Band n77 (NR ARFCN=666667). | + +Additional step 9 when both bands are TDD: + +8. For both E-UTRA and NR UL uplink carriers active when both bands are TDD, ensure E-UTRA UL transmission overlaps with NR UL transmission in time by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.3.3.2.4.2 Test Procedure + +Same test procedure as described in clause 6.5B.3.1.2.4.2 with the following exceptions: + +Instead of Table 6.5B.3.1.2.3-1 --> use Table 6.5B.3.3.2.5-1. + +In addition to test configurations above, EN-DC only capable UEs and UEs not supporting NR/5GC mode in the tested band needs to be tested according to LTE anchor agnostic approach below. + +Same test description as in clause 6.5.3.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.3.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 6.5B.3.3.2.4.3 Message Contents + +Message contents are according to TS 36.508 [11] clause 4.6 and TS 38.508-1 [6] clause 4.6.1 with the following exceptions. + +**Table 6.5B.3.3.2.4.3-1: SystemInformationBlockType1: tdd-Config if E-UTRA on TDD band** + +| Derivation Path: TS 36.508 [11], Table 4.6.3-23 | | | | +|-------------------------------------------------|--------------|-----------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| TDD-Config-DEFAULT ::= SEQUENCE { | | Operating on TDD band | | +| subframeAssignment | Sa2 | | | +| specialSubframePatterns | Ssp7 | | | +| } | | | | + +**Table 6.5B.3.3.2.4.3-1a: Void** + +**Table 6.5B.3.3.2.4.3-2: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +**Table 6.5B.3.3.2.4.3-3: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +###### 6.5B.3.3.2.5 Test Requirement + +Test requirements for Spurious Emissions UE Co-existence when both LTE and NR carriers are required to be active are release specific and can be found in Table 6.5B.3.3.2.5-1 If the UE support a band combination from a later release, the requirements for this band combination are taken from the table of earliest release where requirements for this band combination are defined. + +Test requirements for EN-DC only capable devices when using LTE anchor agnostic approach can be found in clause 6.5.3.2.5 in TS 38.521-1 [8]. + +For inter-band EN\_DC with the uplink assigned to one LTE band and one NR band, the test requirements in Table 6.5B.3.3.2.5-1 can be verified by measuring spurious emissions at the specific frequencies where second and third order intermodulation products generated by the two transmitted carriers can occur. + +**Table 6.5B.3.3.2.5-1: Requirements for inter-band within FR1 according to UE NR release** + +| EN-DC Configuration | Release | Spurious emission | | | | | +|---------------------|---------|-------------------|-----------------------|---------------------|-----------|------| +| | | Protected band | Frequency range (MHz) | Maximum Level (dBm) | MBW (MHz) | NOTE | + +| | | | | | | | | | +|----------|--------------------------------------|---------------------------------------------------|---------------------|---|----------------------|-------|-----|---------| +| DC_1_n28 | Rel-15 | E-UTRA Band 7, 31, 41, 72, 73
NR Band n79 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 42, 52
NR Band n77, n78 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | Rel-15
Rel-16 | Frequency range | 470 | - | 694 | -42 | 8 | 5, 17 | +| | Rel-17
Rel-18 | Frequency range | 470 | - | 710 | -26.2 | 6 | 14 | +| DC_1_n77 | Rel-15 | E-UTRA Band 1, 3, 11, 21, 34, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| | | Frequency range | 1895 | - | 1915 | -15.5 | 5 | 5, 7, 8 | +| | | Frequency range | 1915 | - | 1920 | 1.6 | 5 | 5, 7, 8 | +| DC_1_n78 | Rel-15 | E-UTRA Band 3, 11, 21, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1880 | - | 1895 | -40 | 1 | 5, 8 | +| DC_1_n79 | Rel-15 | E-UTRA Band 5, 7, 8, 18, 19, 26, 28, 41 | F DL_low | - | F DL_high | -50 | 1 | | +| DC_2_n5 | Rel-15 | E-UTRA Band 42, 48 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 41, 43 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_2_n66 | Rel-15 | E-UTRA Band 4, 10, 24, 50, 66, 70, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 2, 25 | F DL_low | - | F DL_high | -50 | 1 | 5 | +| | | E-UTRA Band 42, 48 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_2_n71 | Rel-15 | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_2_n78 | Rel-15 | E-UTRA Band 24, 50, 51, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 2, 25 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_3_n7 | Rel-15 | E-UTRA Band 5, 8, 20, 26, 27, 28, 44, 67 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 42 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_3_n8 | Rel-15 | E-UTRA Band 20, 28, 38, 69 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 7, 22, 41, 42, 43 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | | NR band n77, n78, n79 | | | | | | | +| DC_3_n28 | Rel-15 | NR band n77 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | | E-UTRA Band 7, 41 | F DL_low | - | F DL_high | -50 | 1 | | +| DC_3_n77 | Rel-15 | E-UTRA Band 1, 3, 28, 34, 39, 40, 65, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n78 | Rel-15 | E-UTRA Band 3, 34, 39 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_3_n79 | Rel-15 | E-UTRA Band 5, 8, 11, 18, 19, 21, 41, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| DC_5_n66 | Rel-15 | E-UTRA Band 5, 6, 7, 8, 38 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 26 | 859 | - | 869 | -27 | 1 | | +| | | E-UTRA Band 41, 42, 52 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_5_n77 | Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_5_n78 | Rel-15 | E-UTRA Band 1, 2, 3, 4, 7, 25, 34, 38, 65, 66, 70 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2, 7 | + +| | | | | | | | | | +|-----------|--------------------------------------|-------------------------------------------------------------------------------------|---------------------|---|----------------------|-----|-----|-------| +| DC_7_n28 | Rel-15 | E-UTRA Band 3 | F DL_low | - | F DL_high | -50 | 1 | | +| | | NR band n78 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_7_n78 | Rel-15 | E-UTRA Band 3, 5, 8, 11, 18, 19, 20, 21, 26, 27, 28, 32, 50, 51, 67, 68, 74, 75, 76 | F DL_low | - | F DL_high | -50 | 1 | | +| DC_8_n3 | Rel-16
Rel-17
Rel-18 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| DC_8_n20 | Rel-16
Rel-17
Rel-18 | Frequency range | 758 | - | 788 | -50 | 1 | | +| DC_8_n28 | Rel-16
Rel-17
Rel-18 | Frequency range | 491 | - | 616 | -42 | 8 | 5, 17 | +| DC_8_n41 | Rel-16
Rel-17
Rel-18 | Frequency range | 860 | - | 890 | -40 | 1 | 5, 12 | +| DC_8_n77 | Rel-15 | E-UTRA Band 1, 32, 33, 34, 38, 39, 40, 50, 65, 69, 74, 75 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA band 3, 7, 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 12 | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_8_n78 | Rel-15 | E-UTRA band 34, 39, 40, 74 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 3, 7, 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | | E-UTRA Band 11, 21 | F DL_low | - | F DL_high | -50 | 1 | 12 | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 12 | +| DC_11_n77 | Rel-15
r | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | | Frequency range | 2595 | - | 2645 | -50 | 1 | | + +| | | | | | | | | | +|-----------|--------------------------------------|--------------------------------------------|---------------------|---|----------------------|-----|-----|---| +| DC_11_n78 | Rel-15 | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_11_n79 | Rel-15 | E-UTRA Band 1, 3, 34, 42, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_12_n66 | Rel-15 | E-UTRA Band 41,53 | F DL_low | - | F DL_high | -50 | 1 | | +| | | NR Band n77 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| DC_12_n78 | Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_19_n77 | Rel-15 | E-UTRA Band 1, 3, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Rel-17
Rel-18 | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n78 | Rel-15 | E-UTRA Band 1, 3, 34, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Rel-17
Rel-18 | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_19_n79 | Rel-15 | E-UTRA Band 42 | F DL_low | - | F DL_high | -50 | 1 | | +| DC_21_n77 | Rel-15 | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 945 | - | 960 | -50 | 1 | | +| | | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_21_n78 | Rel-15 | E-UTRA Band 1, 3, 18, 19, 28, 34, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_21_n79 | Rel-15 | E-UTRA Band 3, 21, 34, 42 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_25_n41 | Rel-15 | E-UTRA Band 12, 13, 14, 17, 28, 29, 42, 71 | F DL_low | - | F DL_high | -50 | 1 | | +| DC_26_n41 | Rel-15 | E-UTRA Band 3, 5, 18, 19, 26, 42 | F DL_low | - | F DL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 799 | - | 803 | -40 | 1 | 5 | +| | | Frequency range | 945 | - | 960 | -50 | 1 | | +| DC_26_n77 | Rel-15 | E-UTRA Band 1, 3, 34, 39, 40, 65 | F DL_low | - | F DL_high | -50 | 1 | | +| | | E-UTRA Band 41 | F DL_low | - | F DL_high | -50 | 1 | 2 | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | | Frequency range | 2545 | - | 2575 | -50 | 1 | | +| | | Frequency range | 2595 | - | 2645 | -50 | 1 | | + +| | | | | | | | | | +|-----------|--------------------------------------|---------------------------------------------------------------------|---------|---|----------|-------|-----|-------| +| DC_28_n5 | Rel-16 | Frequency range | 557 | - | 672 | -42 | 8 | 5, 17 | +| | Rel-17 | Frequency range | 557 | - | 672 | -26.2 | 6 | 14 | +| | Rel-18 | Frequency range | 662 | - | 672 | -26.2 | 6 | 5 | +| DC_26_n78 | Rel-16 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| | Rel-17 | Frequency range | 2545 | - | 2575 | -50 | 1 | 2 | +| | Rel-18 | Frequency range | 2595 | - | 2645 | -50 | 1 | | +| DC_28_n77 | Rel-15 | E-UTRA Band 3, 7, 34, 39, 40, 41 | FDL_low | - | FDL_high | -50 | 1 | | +| | | E-UTRA Band 1, 65 | FDL_low | - | FDL_high | -50 | 1 | 2 | +| | | E-UTRA Band 1 | FDL_low | - | FDL_high | -50 | 1 | 9, 11 | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 9 | +| DC_28_n78 | Rel-15 | E-UTRA Band 3, 7, 34, 39, 40, 41 | FDL_low | - | FDL_high | -50 | 1 | | +| | | E-UTRA Band 1, 65 | FDL_low | - | FDL_high | -50 | 1 | 2 | +| | | E-UTRA Band 1 | FDL_low | - | FDL_high | -50 | 1 | 9, 11 | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_28_n79 | Rel-15 | E-UTRA Band 42 | FDL_low | - | FDL_high | -50 | 1 | 2 | +| DC_30_n5 | Rel-15 | E-UTRA Band 71 | FDL_low | - | FDL_high | -50 | 1 | | +| DC_39_n41 | Rel-15 | E-UTRA Band 42, 44 | FDL_low | - | FDL_high | -50 | 1 | | +| | | NR Band n77, n78, n79 | FDL_low | - | FDL_high | -50 | 1 | 2 | +| DC_39_n79 | Rel-15 | E-UTRA Band 8, 28, 41, 44 | FDL_low | - | FDL_high | -50 | 1 | | +| DC_40_n41 | Rel-15 | Bands 1, 34, 39, 65 | FDL_low | - | FDL_high | -50 | 1 | | +| | | NR Band n79 | FDL_low | - | FDL_high | -50 | 1 | 2 | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 19 | +| DC_41_n28 | Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 1 | 3, 9 | +| DC_41_n77 | Rel-15 | E-UTRA Band 3, 5, 8, 11, 18, 19, 21, 26, 28, 33, 34, 39, 44, 45, 74 | FDL_low | - | FDL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n78 | Rel-15 | E-UTRA Band 3, 5, 8, 11, 18, 19, 21, 26, 28, 34, 39, 44, 45, 74 | FDL_low | - | FDL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_41_n79 | Rel-15 | E-UTRA Band 1, 3, 5, 8, 18, 19, 26, 28, 34, 40, 44, 65 | FDL_low | - | FDL_high | -50 | 1 | | +| | Rel-15
Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_48_n5 | Rel-16
Rel-17
Rel-18 | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3 | +| DC_66_n5 | Rel-15 | E-UTRA Band 5, 6, 7, 8, 26, 38 | FDL_low | - | FDL_high | -50 | 1 | | +| | | E-UTRA Band 41, 42, 52 | FDL_low | - | FDL_high | -50 | 1 | 2 | + +| | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------|---------------------|---|----------------------|-----|---| +| DC_66_n78 | Rel-15 | E-UTRA Band 3, 34, 39 | F DL_low | - | F DL_high | -50 | 1 | +| NOTE 1: F DL_low and F DL_high refer to each frequency band specified in Table 5.5-1 of TS 36.101 [5] or in Table 5.2-1 in TS 38.101-1 [2]. | | | | | | | | +| NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.6.3.1-2 in TS 36.101 [5] and Table 6.5.3.1-2 in TS 38.101-1 [2] are permitted for each assigned carrier used in the measurement due to 2 nd , 3 rd , 4 th or 5 th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of (2MHz + N x L CRB x 180kHz), where N is 2, 3, 4, 5 for the 2 nd , 3 rd , 4 th or 5 th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. | | | | | | | | +| NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 -1915.7MHz | | | | | | | | +| NOTE 4: Void. | | | | | | | | +| NOTE 5: These requirements also apply for the frequency ranges that are less than F OOB (MHz) in Table 6.6.3.1-1, Table 6.6.3.1A-1in TS 36.101 [5] or in Table 6.5.3.1-1 in TS 38.101-1 [2] from the edge of the channel bandwidth. | | | | | | | | +| NOTE 6: This requirement is applicable for any channel bandwidths within the range 2500 - 2570 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2560.5 - 2562.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2552 - 2560 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | | | | | | | | +| NOTE 7: For these adjacent bands, the emission limit could imply risk of harmful interference to UE(s) operating in the protected operating band. | | | | | | | | +| NOTE 8: This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 – 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink. | | | | | | | | +| NOTE 9: Applicable when the assigned E-UTRA or NR carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz. | | | | | | | | +| NOTE 10: As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 2nd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 2nd harmonic totally or partially overlaps the measurement bandwidth (MBW). | | | | | | | | +| NOTE 11: As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3rd harmonic totally or partially overlaps the measurement bandwidth (MBW). | | | | | | | | +| NOTE 12: This requirement is applicable only for the following cases:
A: for carriers of 5 MHz channel bandwidth when carrier centre frequency (Fc) is within the range 902.5 MHz ≤ Fc < 907.5 MHz with an uplink transmission bandwidth less than or equal to 20 RB;
B: for carriers of 5 MHz channel bandwidth when carrier centre frequency (Fc) is within the range 907.5 MHz ≤ Fc ≤ 912.5 MHz without any restriction on uplink transmission bandwidth;
C: for carriers of 10 MHz channel bandwidth when carrier centre frequency (Fc) is Fc = 910 MHz with an uplink transmission bandwidth less than or equal to 32 RB with RBstart > 3. | | | | | | | | +| NOTE 13: Void. | | | | | | | | +| NOTE 14: This requirement is applicable for 5 and 10 MHz E-UTRA or NR channel bandwidth allocated within 718-728MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with RBstart > 1 and RBstart < 48. | | | | | | | | +| NOTE 15: Void. | | | | | | | | +| NOTE 16: This requirement is applicable for any channel bandwidths within the range 1920 - 1980 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1927.5 - 1929.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1930 - 1938 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | | | | | | | | +| NOTE 17: This requirement is applicable in the case of a 10 MHz E-UTRA carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies. | | | | | | | | +| NOTE 18: This requirement is only applicable for E-UTRA carriers with bandwidth confined within 1885 - 1920 MHz (requirement for carriers with at least 1RB confined within 1880 - 1885 MHz is not specified). This requirement applies for an uplink transmission bandwidth less than or equal to 54 RB for E-UTRA carriers of 15 MHz bandwidth when carrier centre frequency is within the range 1892.5 - 1894.5 MHz and for E-UTRA carriers of 20 MHz bandwidth when carrier centre frequency is within the range 1895 - 1903 MHz. | | | | | | | | +| NOTE 19: Void. | | | | | | | | +| NOTE 20: Void. | | | | | | | | +| NOTE 21: Void. | | | | | | | | +| NOTE 22: This requirement is applicable for power class 3 UE for any channel bandwidths within the range 2570 - 2615 MHz with the following restriction: for carriers of 15 MHz bandwidth when carrier centre frequency is within the range 2605.5 - 2607.5 MHz and for carriers of 20 MHz bandwidth when carrier centre frequency is within the range 2597 - 2605 MHz the requirement is applicable only for an uplink transmission bandwidth less than or equal to 54 RB. | | | | | | | | + +**Table 6.5B.3.3.2.5-2: Void** + +**Table 6.5B.3.3.2.5-3: Void** + +#### 6.5B.3.3a Inter-band NE-DC within FR1 + +##### 6.5B.3.3a.1 General Spurious Emissions for Inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.5.3.1 and 6.5A.3.1 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.6.3.1 and 6.6.3.1A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +##### 6.5B.3.3a.2 Spurious emission band UE co-existence for Inter-band NE-DC within FR1 + +FFS + +#### 6.5B.3.4 Spurious Emissions for Inter-band including FR2 + +**Editor's note: This clause is complete for Band n257, n258, n260 and n261. The following aspects are either missing or not yet determined:** + +- **The referred test case 6.5.3 in TS 38.521-2 [9] is incomplete for frequency above 80 GHz.** + +##### 6.5B.3.4.1 General Spurious Emissions for Inter-band including FR2 (1 NR CC) + +**Editor's Note:** + +- **This clause is complete for Band n257, n258, n260 and n261 and for power class 1 and 3.** +- **For n259, measurement uncertainty is TBD in the range $80 \text{ GHz} < f \leq 87 \text{ GHz}$ . Up to 80GHz, for n259 and PC3 this clause is complete.** + +##### 6.5B.3.4.1.1 Test purpose + +Same test purpose as in clause 6.5.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.3.4.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.5B.3.4.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4. + +##### 6.5B.3.4.1.4 Test description + +###### 6.5B.3.4.1.4.1 Initial conditions + +Same test description as in clause 6.5.3.1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.3.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.3.1.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1.5 Test requirement + +Same test requirement as in clause 6.5.3.1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.3.4.1a General Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) + +**Editor's note: This clause is complete for Band n257, n258, n260 and n261 for PC1 and PC3. The following aspects of the clause are for future consideration:** + +- For n259, measurement uncertainty is TBD in the range $80 \text{ GHz} < f \leq 87 \text{ GHz}$ . Up to 80GHz, for n259 and PC3 this clause is complete. + +###### 6.5B.3.4.1a.1 Test purpose + +Same test purpose as in clause 6.5.3.1\_1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1a.2 Test applicability + +This test case applies to all types of NR UE release 16 and forward supporting *mpr-PowerBoost-FR2-r16* UE capability, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.5B.3.4.1a.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.1\_1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4. + +###### 6.5B.3.4.1a.4 Test description + +Same test description as in clause 6.5.3.1\_1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.3.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2.4\_1.4 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.3.1.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1a.5 Test requirement + +Same test requirement as in clause 6.5.3.1\_1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.3.4.1\_1 General Spurious emissions for Inter-band EN-DC including FR2 (>1 NR CC) + +###### 6.5B.3.4.1\_1.1 General Spurious emissions for Inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.1 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 + +###### 6.5B.3.4.1\_1.1.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.3.4.1\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.3.4. + +###### 6.5B.3.4.1\_1.1.4 Test description + +###### 6.5B.3.4.1\_1.1.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.1.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.1\_1.2 General Spurious emissions for Inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.2 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 + +###### 6.5B.3.4.1\_1.2.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.5B.3.4.1\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.3.4. + +###### 6.5B.3.4.1\_1.2.4 Test description + +###### 6.5B.3.4.1\_1.2.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.2.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.1\_1.3 General Spurious emissions for Inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.3 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 + +###### 6.5B.3.4.1\_1.3.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.5B.3.4.1\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.3.4. + +###### 6.5B.3.4.1\_1.3.4 Test description + +###### 6.5B.3.4.1\_1.3.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.3.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.3.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.1\_1.4 General Spurious emissions for Inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.4 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.3.4.1\_1.4.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.5B.3.4.1\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4. + +###### 6.5B.3.4.1\_1.4.4 Test description + +###### 6.5B.3.4.1\_1.4.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.4.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.4.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.4.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.1\_1.5 General Spurious emissions for Inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.5 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.3.4.1\_1.5.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.5B.3.4.1\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4. + +###### 6.5B.3.4.1\_1.5.4 Test description + +###### 6.5B.3.4.1\_1.5.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.5.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.5.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.5.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.1\_1.6 General Spurious emissions for Inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.6 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.3.4.1\_1.6.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.5B.3.4.1\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4. + +###### 6.5B.3.4.1\_1.6.4 Test description + +###### 6.5B.3.4.1\_1.6.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.6.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.6.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.6.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.1\_1.7 General Spurious emissions for Inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 6.5A.3.1.7 in TS 38.521-2 [9] is incomplete for: + - Bands other than n257, n258, n260 and n261 + - Power classes 1, 2 and 4 +- Measurement Uncertainties and Test Tolerances is incomplete. + +###### 6.5B.3.4.1\_1.7.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.1\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.5B.3.4.1\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4. + +###### 6.5B.3.4.1\_1.7.4 Test description + +###### 6.5B.3.4.1\_1.7.4.1 Initial condition + +Same test description as in clause 6.5A.3.1.7.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.1.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.1.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1\_1.7.5 Test Requirements + +Same test requirement as in clause 6.5A.3.1.7.5 in TS 38.521-2 [9] for the *NR* carrier. + +#### 6.5B.3.4.1D General Spurious Emissions for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 6.5D.3 in TS 38.521-2 [9] is incomplete + +##### 6.5B.3.4.1D.1 Test purpose + +Same test purpose as in clause 6.5D.3.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.3.4.1D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2. + +##### 6.5B.3.4.1D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5D.3.1 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.5B.3.4. + +##### 6.5B.3.4.1D.4 Test Description + +Same test description as in clause 6.5D.3.1 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.5D.3.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5D.3.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1D.5 Test Requirement + +Same test requirement as specified in clause 6.5D.3.1.5 of TS 38.521-2 [9] for the NR carrier(s). + +##### 6.5B.3.4.2 Spurious emission band UE co-existence for Inter-band including FR2 (1 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5.3.2 in TS 38.521-2 [9] is incomplete for PC2 and PC4. + +##### 6.5B.3.4.2.1 Test purpose + +Same test purpose as in clause 6.5.3.2.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.5B.3.4.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.2.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4.1. + +###### 6.5B.3.4.2.4 Test description + +Same Test description as in clause 6.5.3.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.5.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.3.2.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2.5 Test requirement + +Same Test requirement as in clause 6.5.3.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.3.4.2.a Spurious emission band UE co-existence with Power Boost for Inter-band including FR2 (1 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5.3.2\_1 in TS 38.521-2 [9] is incomplete for PC2 and PC4. + +###### 6.5B.3.4.2.a.1 Test purpose + +Same test purpose as in clause 6.5.3.2\_1.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2.a.2 Test applicability + +This test case applies to all types of NR UE release 16 and forward supporting *mpr-PowerBoost-FR2-r16* UE capability, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +###### 6.5B.3.4.2.a.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.2\_1.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.4.1. + +###### 6.5B.3.4.2.a.4 Test description + +Same Test description as in clause 6.5.3.2\_1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.5.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2.4\_1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.3.2\_1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2.a.5 Test requirement + +Same Test requirement as in clause 6.5.3.2\_1.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.3.4.2\_1 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (>1 NR CC) + +###### 6.5B.3.4.2\_1.1 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.1 in TS 38.521-2 [9] is incomplete for: + - Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 + - MU and TT for Power classes 1, 2 and 4 + +###### 6.5B.3.4.2\_1.1.1 Test purpose + +Same test purpose as in clause 6.5.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.3.4.2\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.3.2. + +###### 6.5B.3.4.2\_1.1.4 Test description + +###### 6.5B.3.4.2\_1.1.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.1.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.2 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.2 in TS 38.521-2 [9] is incomplete for: + - Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 + - MU and TT for Power classes 1, 2 and 4 + +###### 6.5B.3.4.2\_1.2.1 Test purpose + +Same test purpose as in clause 6.5.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.5B.3.4.2\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.3.4. + +###### 6.5B.3.4.2\_1.2.4 Test description + +###### 6.5B.3.4.2\_1.2.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.2.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.3 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.3 in TS 38.521-2 [9] is incomplete for: + - Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 + - MU and TT for Power classes 1, 2 and 4 + +###### 6.5B.3.4.2\_1.3.1 Test purpose + +Same test purpose as in clause 6.5.3.1 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR UL CCs. + +###### 6.5B.3.4.2\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.4B.3.4. + +###### 6.5B.3.4.2\_1.3.4 Test description + +###### 6.5B.3.4.2\_1.3.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.3.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.3.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.4 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.4 in TS 38.521-2 [9] is incomplete for: + - Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 + - MU and TT for Power classes 1, 2 and 4 + - Annex F MU, TT tables need to add new rows to include these test cases + +###### 6.5B.3.4.2\_1.4.1 Test purpose + +Same test purpose as in clause 6.5.3.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.2\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR UL CCs. + +###### 6.5B.3.4.2\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.2.0 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.1. + +###### 6.5B.3.4.2\_1.4.4 Test description + +###### 6.5B.3.4.2\_1.4.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.4.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.4.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.3.4.2\_1.5 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.5 in TS 38.521-2 [9] is incomplete for: + - Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 + - MU and TT for Power classes 1, 2 and 4 + - Annex F MU, TT tables need to add new rows to include these test cases + +###### 6.5B.3.4.2\_1.5.1 Test purpose + +Same test purpose as in clause 6.5.3.2 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.3.4.2\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 6 NR UL CCs. + +###### 6.5B.3.4.2\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.2.0 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.1. + +###### 6.5B.3.4.2\_1.5.4 Test description + +###### 6.5B.3.4.2\_1.5.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.5.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.5.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.6 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.6 in TS 38.521-2 [9] is incomplete for: +- Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 +- MU and TT for Power classes 1, 2 and 4 + - Annex F MU, TT tables need to add new rows to include these test cases + +###### 6.5B.3.4.2\_1.6.1 Test purpose + +Same test purpose as in clause 6.5.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 7 NR UL CCs. + +###### 6.5B.3.4.2\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.2.0 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.1. + +###### 6.5B.3.4.2\_1.6.4 Test description + +###### 6.5B.3.4.2\_1.6.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.6.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.6.5 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.7 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The referred test case 6.5A.3.2.7 in TS 38.521-2 [9] is incomplete for: +- Testability and relaxation of the requirement for Bands other than n257, n258, n260 and n261 +- MU and TT for Power classes 1, 2 and 4 +- Annex F MU, TT tables need to add new rows to include these test cases + +###### 6.5B.3.4.2\_1.7.1 Test purpose + +Same test purpose as in clause 6.5.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 8 NR UL CCs. + +###### 6.5B.3.4.2\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.2.0 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.3.1. + +###### 6.5B.3.4.2\_1.7.4 Test description + +###### 6.5B.3.4.2\_1.7.4.1 Initial condition + +Same test description as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.2.1.4 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.2\_1.7.5 Test Requirements + +Same test requirement as in clause 6.5A.3.2.7.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.3.4.2D Spurious emission band UE co-existence for inter-band EN-DC including FR2 for UL MIMO + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 6.5D.3 in TS 38.521-2 [9] is incomplete + +###### 6.5B.3.4.2D.1 Test purpose + +Same test purpose as in clause 6.5D.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +###### 6.5B.3.4.2D.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC FR2. + +###### 6.5B.3.4.2D.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5D.3.2 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to *NR* or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.5B.3.4. + +###### 6.5B.3.4.1D.4 Test Description + +Same test description as in clause 6.5D.3.2 in TS 38.521-2 [9] for the *NR* carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 6.5D.3.2 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5D.3.2 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.3.4.1D.5 Test Requirement + +Same test requirement as specified in clause 6.5D.3.2.5 of TS 38.521-2 [9] for the NR carrier(s). + +#### 6.5B.3.5 Spurious emissions for Inter-band including FR1 and FR2 + +##### 6.5B.3.5.1 General Spurious Emissions for Inter-band including FR1 and FR2 + +###### 6.5B.3.5.1.1 Test purpose + +Same test purpose as in clause 6.5.3 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.5.3 in TS 38.521-2 [9] for NR FR2 carrier(s). + +###### 6.5B.3.5.1.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for spurious emissions apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.5B.3. + +##### 6.5B.3.5.2 Spurious emission band UE co-existence for Inter-band including FR1 and FR2 + +###### 6.5B.3.5.2.1 Test purpose + +Same test purpose as in clause 6.5.3 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 6.5.3 in TS 38.521-2 [9] for NR FR2 carrier(s). + +###### 6.5B.3.5.2.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for spurious emissions apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 6.5B.3. + +### 6.5B.4 Additional Spurious Emissions for EN-DC + +#### 6.5B.4.1 Additional Spurious Emissions for Intra-band contiguous EN-DC + +##### 6.5B.4.1.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions under the deployment scenarios where additional requirements are specified. + +##### 6.5B.4.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward supporting intra-band contiguous EN-DC. + +##### 6.5B.4.1.3 Minimum conformance requirements + +These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +###### 6.5B.4.1.3.1 Minimum requirement (network signalled value "NS\_04") + +When "NS 04" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5B.4.1.3.1-1. This requirement also applies for the frequency ranges that are less than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1.3-1 of TS 38.521-1 [8] from the edge of the channel bandwidth. + +**Table 6.5B.4.1.3.1-1: Additional requirements** + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit (dBm) | Measurement bandwidth | +|------------------------|---------------------------------------------------|----------------------------------------------------------------------------------------| +| $2495 \leq f < 2496$ | -13 | 1% of Channel BW for contiguous BW up to 100 MHz,
1 MHz for contiguous BW > 100 MHz | +| $2490.5 \leq f < 2495$ | -13 | 1 MHz | +| $0 < f < 2490.5$ | -25 | 1 MHz | + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4.1.1. + +Exception requirements for both NR and E-UTRA are defined for this test. LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included, and E-UTRA measurements are performed. + +##### 6.5B.4.1.4 Test description + +###### 6.5B.4.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on EN-DC operating bands specified in 5.3B.1.2. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing are shown in Table 6.5B.4.1.4.1-1 for both E-UTRA and NR. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2 for NR. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C and in TS 38.521-1 [8] Annex C2 for LTE link and NR link respectively. + +**Table 6.5B.4.1.4.1-1: EN-DC test configuration table for NS\_04** + +| Initial Conditions | | | | | | | | +|------------------------------------------------------------------------|-------------------------------------------------------------------|------------------------|----------------------------|------------------------|-----------------|------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Low range, High range | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 | Lowest N RB_agg , Highest N RB_agg (Note 2) | | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | | | | | +| Test Parameters | | | | | | | | +| Test ID | Freq | Downlink Configuration | EN-DC Uplink Configuration | | | | | +| | | | E-UTRA Cell | | NR Cell | | Common | +| | | | Modulation | RB allocation (Note 5) | Modulation | RB allocation (Note 1) | Power config (Note 6) | +| 1 | Default | | 16QAM | Outer_Full | DFT-s-OFDM QPSK | Outer_Full | B | +| 2 (Note 3) | Default | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | Edge_1RB_Right | B | +| 3 (Note 3) | Low | | 16QAM | Outer_1RB_Left | DFT-s-OFDM QPSK | N/A | A | +| 4 (Note 3) | High | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Right | A | +| 5 (Note 4) | Default | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | Edge_1RB_Left | B | +| 6 (Note 4) | Low | | 16QAM | N/A | DFT-s-OFDM QPSK | Edge_1RB_Left | A | +| 7 (Note 4) | High | | 16QAM | Outer_1RB_Right | DFT-s-OFDM QPSK | N/A | A | +| 8 | Default | | 16QAM | Outer_Full | CP-OFDM 256QAM | Outer_Full | B | +| 9 (Note 3) | Low | | 16QAM | Outer_1RB_Left | CP-OFDM 256QAM | Edge_1RB_Right | B | +| 10 (Note 4) | High | | 16QAM | Outer_1RB_Right | CP-OFDM 256QAM | Edge_1RB_Left | B | +| 11 (Note 4) | Default | | 16QAM | Edge_Full_Right | CP-OFDM 256QAM | Edge_Full_Left | B | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 in TS 38.521-1 [8]. + +NOTE 2: If the UE supports multiple CC combinations in the EN-DC configuration with the same NRB\_agg, select the combination to test as follows: + +- Lowest ENBW: NR component with lowest NRB is tested. +- Highest ENBW: NR component with highest NRB is tested. + +NOTE 3: Applicable when E-UTRA cell carrier frequency is lower than NR cell carrier. + +NOTE 4: Applicable when NR cell carrier frequency is lower than E-UTRA cell carrier. + +NOTE 5: Outer\_Full defined as the transmission bandwidth configuration NRB per channel bandwidth for the E-UTRA component as indicated in TS 36.521-1 [10] Table 5.4.2-1. Outer\_1RB\_Left defined as 1 RB allocated at the left edge of the E-UTRA component. Outer\_1RB\_Right defined as 1 RB allocated at the right edge of the E-UTRA component. + +NOTE 6: Power config as specified in Table 6.2B.3.1.4.3-1 to 6.2B.3.1.4.3-2 (PC3) or Table 6.2B.3.1.4.3-3 to 6.2B.3.1.4.3-4 (PC2). + +NOTE 7: Test IDs with simultaneous E-UTRA and NR UL transmission only apply for UEs indicating dualPA-Architecture. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for SS diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +4. E-UTRA downlink signals are initially set up according to Annex C0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. +5. NR downlink signals are initially set up according to Annex C.0, C.1 and C.2, and uplink signals according to Annex G.0, G.1, G.2, G.3.0 of TS 38.521-1 [8]. + +6. The UL Reference Measurement channels are set according to Table 6.5B.4.1.4.1-1. +7. NR propagation conditions are set according to B.0 of TS 38.521-1 [8]. E-UTRA propagation conditions are set according to B.0 of TS 36.521-1 [10]. +8. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.5B.4.1.4.3. +9. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.4.1.4.2 Test Procedure + +1. E-UTRA SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 for C\_RNTI to schedule the UL RMC according to Table 6.5B.4.1.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. NR SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5B.4.1.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +3. Send continuously uplink power control "up" commands to the UE for both NR and E-UTRA carriers until the UE transmits at its $P_{\text{UMAX}}$ level; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +4. Measure the mean power of each component carriers for the EN-DC configuration, which shall meet the requirements described in 6.2B.3.1.5.2 depending on NS-values. The period of the measurement shall be at least the continuous duration of one sub-frame. +5. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5B.4.1.3.1-1. The centre frequency of the filter shall be stepped in contiguous steps according to the same table. The measured power shall be recorded for each step. The measurement period shall capture the active time slots. During measurement the spectrum analyser shall be set to 'Detector' = RMS. + +###### 6.5B.4.1.4.3 Message Contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 with the following exceptions for each network signalled value. + +###### 6.5B.4.1.4.3.1 Message contents exceptions for network signalled value "NS\_04" + +1. Information element additionalSpectrumEmission is set to NS\_04. This can be set in *SIB1* as part of the cell broadcast message. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.5B.4.1.4.3.1-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement for "NS\_04"** + +| Derivation Path: TS 38.508-1 [6] clause 4.6.3, Table 4.6.3-1 | | | | +|--------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| additionalSpectrumEmission | 1 (NS_04) | | | + +**Table 6.5B.4.1.4.3.1-2: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +**Table 6.5B.4.1.4.3.1-3: *PhysicalCellGroupConfig*** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|--------------------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE AND simultaneous E-UTRA and NR transmission | +| | 20 | | Power Class 3 UE AND simultaneous E-UTRA and NR transmission | + +##### 6.5B.4.1.5 Test Requirement + +Test requirements for additional spurious emissions for intra-band contiguous EN-DC are the same as the minimum requirements described in clause 6.5B.4.1.3 and are not repeated in this clause. + +#### 6.5B.4.2 Additional Spurious Emissions for Intra-band non-contiguous EN-DC + +##### 6.5B.4.2.1 Test purpose + +Same minimum conformance requirements as in clause 6.5B.4.1.1. + +##### 6.5B.4.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC. + +##### 6.5B.4.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5B.4.1.3. + +##### 6.5B.4.2.4 Test description + +###### 6.5B.4.2.4.1 Initial conditions + +Same initial conditions as described in clause 6.5B.4.1.4.1 for both E-UTRA and NR carriers with the following exception: + +1. For each EN-DC combination specified in Table 5.3B.1.3-1, channel spacing between NR and E-UTRA is specified according to clause 5.4B.1. +2. Set up the NR and E-UTRA test frequencies so that NR carrier is located at the lower frequency side as specified in Table 5.3B.1.3-1. Repeat each testing with E-UTRA carrier frequency is located at the lower side as specified in Table 5.3B.1.3-1. +3. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 6.5B.4.2.4.2 Test Procedure + +Same test procedure as described in clause 6.5B.4.1.4.2. + +###### 6.5B.4.2.4.3 Message Contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 with the following exceptions for each network signalled value. + +###### 6.5B.4.2.4.3.1 Message contents exceptions for network signalled value "NS\_04" + +1. Information element *additionalSpectrumEmission* is set to NS\_04. This can be set in *SIB1* as part of the cell broadcast message. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.5B.4.2.4.3.1-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement for "NS\_04"** + +| Derivation Path: TS 38.508-1 [6] clause 4.6.3, Table 4.6.3-1 | | | | +|--------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| additionalSpectrumEmission | 1 (NS_04) | | | + +##### 6.5B.4.2.5 Test Requirement + +Test requirements for Spurious Emissions for intra-band non-contiguous EN-DC are the same as the minimum requirements described in 6.5B.4.2.3 and are not repeated in this clause. + +#### 6.5B.4.3 Additional Spurious Emissions for Inter-band EN-DC within FR1 (1 NR CC) + +##### 6.5B.4.3.1 Test purpose + +Same test purpose as in clause 6.5.3.3.1 in TS 38.521-1 [8] for the NR carrier. + +##### 6.5B.4.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward supporting inter-band EN-DC within FR1 with 1 NR UL. + +##### 6.5B.4.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 6.5B.4.3.4 Test description + +Same test description as in clause 6.5.3.3.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.3.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.3.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Same test procedure as in clause 6.5.3.3.4.2 in TS 38.521-1 [8]. + +##### 6.5B.4.3.5 Test Requirement + +Same test requirement as in clause 6.5.3.3.5 in TS 38.521-1 [8] for the NR carrier. + +#### 6.5B.4.4 Additional Spurious Emissions for Inter-band including FR2 (1 NR CC) + +Editor's note: This clause is complete for Band n257 and n258 and power class 3. The following aspects are either missing or not yet determined: + +- The referred test case 6.5.3.3 in TS 38.521-2 [9] is incomplete for frequency above 80 GHz. + +##### 6.5B.4.4.1 Test purpose + +Same test purpose as in clause 6.5.3.3.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.4.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.5B.4.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4.5. + +##### 6.5B.4.4.4 Test description + +Same test description as in clause 6.5.3.3.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.3.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.3.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.3.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.5B.4.4.5 Test requirement + +Same test requirement as in clause 6.5.3.3.5 in TS 38.521-2 [9] for the NR carrier. + +#### 6.5B.4.4a Additional Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) + +Editor's note: This clause is complete for Band n257 and n258 and PC3. The following aspects are either missing or not yet determined: + +- The referred test case 6.5.3.3\_1 in TS 38.521-2 [9] is incomplete for frequency above 80 GHz. + +##### 6.5B.4.4a.1 Test purpose + +Same test purpose as in clause 6.5.3.3\_1.1 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.4.4a.2 Test applicability + +This test case applies to all types of NR UE release 16 and forward supporting *mpr-PowerBoost-FR2-r16* UE capability, supporting inter-band EN-DC including FR2 with 1 NR UL CC. + +##### 6.5B.4.4a.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5.3.3\_1.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4.5. + +##### 6.5B.4.4a.4 Test description + +Same test description as in clause 6.5.3.3\_1.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. + +For Initial conditions as in clause 6.5.3.3\_1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.2.4\_1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5.3.3\_1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 6.5B.4.4a.5 Test requirement + +Same test requirement as in clause 6.5.3.3\_1.5 in TS 38.521-2 [9] for the NR carrier. + +##### 6.5B.4.4\_1 Additional Spurious Emissions for Inter-band including FR2 (>1 NR CC) + +###### 6.5B.4.4\_1.1 Additional Spurious Emissions for Inter-band including FR2 (2 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The testability of this test case is pending further analysis on relaxation of the requirement for band other than n257, n258, n260 and n261. +- Test procedure only includes the testing of smartphone and is FFS for laptop and FWA. +- For a transition period until RAN#99, the stability and repeatability of test procedure with PHR (variant b) for Rel-15 UEs is under evaluation. + +###### 6.5B.4.4\_1.1.1 Test purpose + +Same test purpose as in clause 6.5A.3.3.1.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.4.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.4.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.3.0 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4.5. + +###### 6.5B.4.4\_1.1.4 Test description + +###### 6.5B.4.4\_1.1.4.1 Initial condition + +Same test description as in clause 6.5A.3.3.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.3.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.3.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.4.4\_1.1.5 Test Requirements + +Same test requirement as in clause 6.5A.3.3.1.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.4.4\_1.2 Additional Spurious Emissions for Inter-band including FR2 (3 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The testability of this test case is pending further analysis on relaxation of the requirement for band other than n257, n258, n260 and n261. +- Test procedure only includes the testing of smartphone and is FFS for laptop and FWA. + +- For a transition period until RAN#99, the stability and repeatability of test procedure with PHR (variant b) for Rel-15 UEs is under evaluation. + +###### 6.5B.4.4\_1.2.1 Test purpose + +Same test purpose as in clause 6.5A.3.3.2.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.4.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR UL CCs. + +###### 6.5B.4.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.3.0 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4.5. + +###### 6.5B.4.4\_1.2.4 Test description + +###### 6.5B.4.4\_1.2.4.1 Initial condition + +Same test description as in clause 6.5A.3.3.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.3.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.3.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.4.4\_1.2.5 Test Requirements + +Same test requirement as in clause 6.5A.3.3.2.5 in TS 38.521-2 [9] for the *NR* carrier. + +##### 6.5B.4.4\_1.3 Additional Spurious Emissions for Inter-band including FR2 (4 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The testability of this test case is pending further analysis on relaxation of the requirement for band other than n257, n258, n260 and n261. +- Test procedure only includes the testing of smartphone and is FFS for laptop and FWA. +- For a transition period until RAN#99, the stability and repeatability of test procedure with PHR (variant b) for Rel-15 UEs is under evaluation. + +###### 6.5B.4.4\_1.3.1 Test purpose + +Same test purpose as in clause 6.5A.3.3.3.1 in TS 38.521-2 [9] for the NR carrier. + +###### 6.5B.4.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR UL CCs. + +###### 6.5B.4.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.5A.3.3.0 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5B.4.5. + +###### 6.5B.4.4\_1.3.4 Test description + +###### 6.5B.4.4\_1.3.4.1 Initial condition + +Same test description as in clause 6.5A.3.3.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For Initial conditions as in clause 6.5A.3.3.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5A.3.3.3.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.5A.3.3.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 6.5B.4.4\_1.3.5 Test Requirements + +Same test requirement as in clause 6.5A.3.3.3.5 in TS 38.521-2 [9] for the *NR* carrier. + +### 6.5B.5 Transmit intermodulation + +#### 6.5B.5.1 Transmit intermodulation for Intra-band contiguous EN-DC + +No test case details are specified. No transmit intermodulation requirements are applied for intra band contiguous EN DC unless otherwise stated as in clause TS 38.101-3 [4] clause 6.5B.5.1. + +#### 6.5B.5.2 Transmit intermodulation for Intra-band non-contiguous EN-DC + +No test case details are specified. No transmit intermodulation requirements are applied for intra band contiguous EN DC unless otherwise stated as in clause TS 38.101-3 [4] clause 6.5B.5.2. + +#### 6.5B.5.3 Transmit intermodulation for Inter-band EN-DC within FR1 (1 NR CC) + +##### 6.5B.5.3.1 Test purpose + +Same test purpose as in clause 6.5.4 in TS 38.521-1 [8] for the NR carrier. + +##### 6.5B.5.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR UL. + +##### 6.5B.5.3.3 Minimum conformance requirements + +The transmit intermodulation requirement specified in clauses 6.7.1 and 6.7.1A of TS 36.101 [5] and clauses 6.5.4 and 6.5A.4 of TS 38.101-1 [2] apply for each component carrier in E-UTRA bands and NR bands, respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this measurement is TS 38.101-3 [4] clause 6.5B.5.3. + +##### 6.5B.5.3.4 Test description + +Same test description as in clause 6.5.4.4 in TS 38.521-1 [8] for the NR carrier with the following exception: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 6.5.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.5.4.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Same test procedure as in clause 6.5.4.4.2 in TS 38.521-1 [8]. + +##### 6.5B.5.3.5 Test Requirement + +The ratio derived in step 6 and 8, shall not exceed the described value in Table 6.5.4.5-1 defined in TS 38.521-1 [8]. + +#### 6.5B.5.3a Transmit Intermodulation for Inter-band NE-DC within FR1 + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 6.5.4 and 6.5A.4 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 6.7 and 6.7A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +#### 6.5B.5.4 Transmit intermodulation for Inter-band EN-DC including FR2 + +#### 6.5B.5.5 Transmit intermodulation for Inter-band EN-DC including both FR1 and FR2 + +## 6.5E Output RF spectrum emissions for V2X operation in FR1 + +### 6.5E.1 Occupied bandwidth for V2X + +#### 6.5E.1.0 Minimum conformance requirements + +For intra-band V2X, the occupied bandwidth specified in clause 6.6.1G in TS 36.101 [5] and specified in clause 6.5E.1 in TS 38.101-1 [2] apply for each frequency range respectively. + +For the inter-band concurrent NR V2X operation, the requirements specified in subclause 6.6.1 of TS 36.101 [5] shall apply for the E-UTRA uplink in licensed band and the requirements specified in subclause 6.5E.1 of TS 38.101-1 [2] shall apply for the sidelink in NR Band n47. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5E.1. + +#### 6.5E.1.1 Occupied bandwidth for intra-band V2X + +##### 6.5E.1.1.1 Test purpose + +Same test purpose as in clause 6.5E.1 in TS 38.521-1 [8]. + +##### 6.5E.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.5E.1.0. The requirements in this test case can be well covered in clause 6.6.1G of TS 36.521-1 [10] and clause 6.5E.1 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.5E.1.2 Occupied bandwidth for inter-band V2X + +##### 6.5E.1.2.1 Test purpose + +Same test purpose as in clause 6.5E.1 in TS 38.521-1 [8]. + +##### 6.5E.1.2.2 Test applicability + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.6.1 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.5E.1 of TS 38.521-1 [8] and don't need to be tested again. + +### 6.5E.2 Out of band emission for V2X + +#### 6.5E.2.0 Minimum conformance requirements + +For intra-band V2X, out-of-band emissions specified in clause 6.6.2G in TS 36.101 [5] and specified in clause 6.5E.2 in TS 38.101-1 [2] apply for each frequency range respectively. + +For the inter-band concurrent NR V2X operation, the general SEM/additional SEM requirements and ACLR specified in subclause 6.6.2 of TS 36.101 [5] shall apply for the E-UTRA uplink in licensed band and the general SEM/additional SEM and ACLR requirements specified in subclause 6.5E.2 of TS 38.101-1 [2] shall apply for the sidelink in NR Band n47. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5E.2. + +#### 6.5E.2.1 Out of band emission for intra-band V2X + +##### 6.5E.2.1.1 Test purpose + +Same test purpose as in clause 6.5E.2 in TS 38.521-1 [8]. + +##### 6.5E.2.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.5E.2.0. The requirements in this test case can be well covered in clause 6.6.2G of TS 36.521-1 [10] and clause 6.5E.2 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.5E.2.2 Out of band emission for inter-band V2X + +##### 6.5E.2.2.1 Test purpose + +Same test purpose as in clause 6.5E.2 in TS 38.521-1 [8]. + +##### 6.5E.2.2.2 Test applicability + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.6.2 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.5E.2 of TS 38.521-1 [8] and don't need to be tested again. + +### 6.5E.3 Spurious emissions for V2X + +#### 6.5E.3.1 General spurious emissions for V2X + +##### 6.5E.3.1.0 Minimum conformance requirements + +For intra-band V2X, the general spurious emissions requirements specified in clause 6.6.3.1 of TS 36.101 [5] and clause 6.5E.3.1 of TS 38.101-1 [2] apply for each frequency range respectively. + +For inter-band V2X, the general spurious emissions requirements specified in clause 6.6.3.1 of TS 36.101 [5] and clause 6.5E.3.1 of TS 38.101-1 [2] apply for each frequency range respectively. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5E.3. + +##### 6.5E.3.1.1 General spurious emissions for intra-band V2X + +###### 6.5E.3.1.1.1 Test purpose + +Same test purpose as in clause 6.5E.3.1 in TS 38.521-1 [8]. + +###### 6.5E.3.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.5E.3.1.0. The requirements in this test case can be well covered in clause 6.6.3.1 of TS 36.521-1 [10] and clause 6.5E.3.1 of TS 38.521-1 [8] and don't need to be tested again. + +##### 6.5E.3.1.2 General spurious emissions for inter-band V2X + +###### 6.5E.3.1.2.1 Test purpose + +Same test purpose as in clause 6.5E.3.1 in TS 38.521-1 [8]. + +###### 6.5E.3.1.2.2 Test applicability + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.6.3.1 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.5E.3.1 of TS 38.521-1 [8] and don't need to be tested again. + +### 6.5E.4 Transmit intermodulation for V2X + +#### 6.5E.4.0 Minimum conformance requirements + +For intra-band V2X, transmit intermodulation requirements specified in clause 6.7G.1 of TS 36.101 [5] and clause 6.5E.4 of TS 38.101-1 [2] apply for each frequency range respectively. + +For inter-band concurrent NR V2X operation, the requirements specified in subclause 6.7.1 of TS 36.101 [5] shall apply for the E-UTRA uplink in licensed band and the requirements specified in subclause 6.5E.4 of TS 38.101-1 [2] shall apply for the sidelink in NR Band n47. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.5E.4. + +#### 6.5E.4.1 Transmit intermodulation for intra-band V2X + +##### 6.5E.4.1.1 Test purpose + +Same test purpose as in clause 6.5E.4.1 in TS 38.521-1 [8]. + +##### 6.5E.4.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. Given only single switched SL is supported as per clause 6.5E.4.1. The requirements in this test case can be well covered in clause 6.7G.1 of TS 36.521-1 [10] and clause 6.5E.4.1 of TS 38.521-1 [8] and don't need to be tested again. + +#### 6.5E.4.2 Transmit intermodulation for inter-band V2X + +##### 6.5E.4.2.1 Test purpose + +Same test purpose as in clause 6.5E.4.2 in TS 38.521-1 [8]. + +##### 6.5E.4.2.2 Test applicability + +For inter-band V2X operation, no exception requirements are specified for the E-UTRA/NR Uu carrier and E-UTRA/NR SL carrier. + +For inter-band V2X configuration with E-UTRA Uu and NR sidelink, the requirements in this test case can be well covered in clause 6.7.1 of TS 36.521-1 [10] for E-UTRA Uu carrier and clause 6.5E.4.2 of TS 38.521-1 [8] and don't need to be tested again. + +## 6.6B Beam Correspondence for EN-DC + +### 6.6B.4 Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The associated standalone test 6.6.1 in TS 38.521-2 [9] is incomplete for band n259. + +#### 6.6B.4.1 Test purpose + +Same test purpose as in clause 6.6.1.1 in TS 38.521-2 [9] for the *NR* carrier. + +#### 6.6B.4.2 Test applicability + +This test case applies to all types of E-UTRA-NR Power Class 3 UE release 15, supporting inter-band EN-DC including FR2 with 1 NR UL CC that do not support beam correspondence without UL beam sweeping. + +This test case applies to all types of E-UTRA-NR Power Class 3 UE release 16 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC that do not support SSB-based or CSI-RS based enhanced beam correspondence and do not support beam correspondence without UL beam sweeping. + +#### 6.6B.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.6.1.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.6B.4. + +#### 6.6B.4.4 Test description + +Same test description as in clause 6.6.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.6.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of initial conditions as in clause 6.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +#### 6.6B.4.5 Test requirements + +Same test requirement as in clause 6.6.1.5 in TS 38.521-2 [9] for the NR carrier. + +### 6.6B.5 Enhanced Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The associated standalone test 6.6.2 in TS 38.521-2 [9] is incomplete. + +#### 6.6B.5.1 Test purpose + +Same test purpose as in clause 6.6.2.1 in TS 38.521-2 [9] for the NR carrier. + +#### 6.6B.5.2 Test applicability + +This test case applies to all types of E-UTRA-NR Power Class 3 UE release 16 and forward, supporting inter-band EN-DC including FR2 with 1 NR UL CC and support either CSI-RS or SSB based beam correspondence and do not support beam correspondence without UL beam sweeping. + +#### 6.6B.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 6.6.2.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 6.6B.5. + +#### 6.6B.5.4 Test Procedure + +Same test description as in clause 6.6.2.5 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 6.6.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of initial conditions as in clause 6.3.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 6.3.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +#### 6.6B.5.5 Test Requirements + +Same test requirement as in clause 6.6.2.5 in TS 38.521-2 [9] for the NR carrier. + +# --- 7 Receiver characteristics + +## 7.1 General + +**Editor's note:** Test configurations/environments that require new spherical scan shall be included in test procedure clause and identifying such scenarios is currently FFS and owned by RAN5. + +Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the UE for the bands operating on frequency range 1 and over the air of the UE for the bands operating on frequency range 2. The requirements for frequency range 1 and frequency range 2 can be verified separately. For the carrier in frequency range 1, requirements can be verified with NR FR2 link disabled. For the carrier in frequency range 2, requirements can be verified in OTA mode with E-UTRA connecting to the network by OTA without calibration. + +For NR FR2 Rx test cases the identified beam peak direction can be stored and reused for a device under test in various configurations/environments for the full duration of device testing as long as beam peak direction is the same. + +The requirements defined in this clause are the extra requirements compared with the single carrier requirements defined in TS 38.521-1 [8] and TS 38.521-2 [9]. + +Unless otherwise stated, the UL and DL reference measurement channels are the same with the configurations specified in TS 38.521-1 [8] and TS 38.521-2 [9]. + +Unless otherwise stated, requirements for NR receiver written in TS 38.521-1 [8] and TS 38.521-2 [9] apply and are assumed anchor agnostic. Requirements are verified under conditions where anchor resources do not interfere NR operation. + +For intra-band EN-DC, the output power is configured as follows: + +- One E-UTRA uplink carrier with the output power set to 29dB below $P_{\text{CMAX\_L,c}}$ and the NR band whose downlink is being tested has its uplink carrier output power set to 4dB below $P_{\text{CMAX\_L,fc}}$ . +- One NR uplink carrier with the output power set to 29dB below $P_{\text{CMAX\_L,fc}}$ and the E-UTRA band whose downlink is being tested has its uplink carrier output power set to 4 dB below $P_{\text{CMAX\_L,c}}$ . + +For the additional requirements for intra-band non-contiguous EN-DC of two sub-blocks, an in-gap test refers to the case when the interfering signal is located at a negative offset with respect to the assigned lowest channel frequency of the highest sub-block and located at a positive offset with respect to the assigned highest channel frequency of the lowest sub-block. + +For the additional requirements for intra-band non-contiguous EN-DC of two sub-blocks, an out-of-gap test refers to the case when the interfering signal(s) is (are) located at a positive offset with respect to the assigned channel frequency of the highest carrier frequency or located at a negative offset with respect to the assigned channel frequency of the lowest carrier frequency. + +For the additional requirements for intra-band non-contiguous EN-DC of two sub-blocks with channel bandwidth larger than or equal to 5 MHz, the existing adjacent channel selectivity requirements, in-band blocking requirements (for each case), and narrow band blocking requirements apply for in-gap tests only if the corresponding interferer frequency offsets with respect to the two measured carriers satisfy the following condition in relation to the sub-block gap size $W_{\text{gap}}$ for at least one of the E-UTRA or NR sub-blocks, so that the interferer frequency position does not change the nature of the core requirement tested: + +$$W_{\text{gap}} \geq 2 \cdot |F_{\text{Interferer}}(\text{offset})| - BW_{\text{Channel}}$$ + +For the E-UTRA sub-block, the $F_{\text{Interferer}}(\text{offset})$ , for a sub-block with a single component carrier is the interferer frequency offset with respect to carrier as specified in clause 7.5.1, clause 7.6.1 and clause 7.6.3 for the respective requirement in TS 36.521 [10] and $BW_{\text{Channel}}$ . $F_{\text{Interferer}}(\text{offset})$ for the E-UTRA sub-block with two or more contiguous component carriers is the interference frequency offset with respect to the carrier adjacent to the gap is specified in clause 7.5.1A, 7.6.1A and 7.6.3A in TS 36.521 [10]. + +For the NR sub-block, the $F_{\text{Interferer}}(\text{offset})$ , for a sub-block with a single component carrier is the interferer frequency offset with respect to carrier as specified in clause 7.5, clause 7.6.2 and clause 7.6.4 for the respective requirement in TS 38.521-1 [8] and $BW_{\text{Channel}}$ . + +The interferer frequency offsets for adjacent channel selectivity, each in-band blocking case and narrow- band blocking shall be tested separately with a single in-gap interferer at a time. + +Unless otherwise stated, Channel Bandwidth shall be prioritized in the selecting of test points. Subcarrier spacing shall be selected after Test Channel Bandwidth is selected. + +For conformance testing involving FR2 test cases in this specification, the UE under test shall be pre-configured with UL Tx diversity schemes disabled to account for single polarization System Simulator (SS) in the test environment. The UE under test may transmit with dual polarization. + +7.2 Void + +7.3 Void + +## 7.3A Reference sensitivity for CA without EN-DC + +### 7.3A.1 General + +For NR CA operation NR single carrier and CA operation of REFSENS requirements defined in TS 38.101-1 [2] and TS 38.101-2 [3] apply to all downlink bands part of NR CA configurations listed in Table 5.2A.1-1 unless sensitivity degradation is allowed as defined in clause 7.3A in TS 38.101-3 [4]. + +A UE which supports inter-band NR CA configuration is allowed to apply each sensitivity degradation for FR1 specified in clause 7.3A.2 TS 38.101-1 [2] and for FR2 specified in clause 7.3A.2 of TS 38.101-2 [3] independently. + +### 7.3A.2 Reference sensitivity power level for CA without EN-DC + +#### 7.3A.2.1 Test purpose + +Same test purpose as in clause 7.3.2 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 7.3.2 in TS 38.521-2 [9] for NR FR2 carrier(s). + +#### 7.3A.2.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for receiver sensitivity power level apply and are tested in TS 38.521-1 [8] clauses 7.3 and 7.3A and TS 38.521-2 [9] clauses 7.3 and 7.3A. + +#### 7.3A.3 $\Delta R_{IB,c}$ for CA without EN-DC + +For the UE which supports inter-band NR CA configuration, the minimum requirement for reference sensitivity in clause 7.3.2 in TS 38.101-1 [2] and clause 7.3.2, 7.3A.2 in TS 38.101-2 [3] shall be increased by the amount given in $\Delta R_{IB,c}$ in Tables below. Unless otherwise stated, $\Delta R_{IB,c}$ is set to zero. + +In case the UE supports more than one of band combinations for CA, SUL or DC, and an operating band belongs to more than one band combinations then + +- When the operating band frequency range is $\leq 1$ GHz, the applicable additional $\Delta R_{IB,c}$ shall be the average value for all band combinations defined in clause 7.3A, 7.3B, 7.3C in TS 38.101-1 [2] and 7.3A, 7.3B in TS 38.101-3 [4], truncated to one decimal place that apply for that operating band among the supported band combinations. In case there is a harmonic relation between low band UL and high band DL, then the maximum $\Delta R_{IB,c}$ among the different supported band combinations involving such band shall be applied +- When the operating band frequency range is $> 1$ GHz, the applicable additional $\Delta R_{IB,c}$ shall be the maximum value for all band combinations defined in clause 7.3A, 7.3B, 7.3C in TS 38.101-1 [2] and 7.3A, 7.3B in TS 38.101-3 [4] for the applicable operating bands. + +#### 7.3A.3.1 $\Delta R_{IB,c}$ for Inter-band CA between FR1 and FR2 without EN-DC + +Unless otherwise stated, $\Delta R_{IB,c}$ for NR FR1 band and FR2 band of inter-band CA defined in table 5.5A.1-1 is set to zero. + +#### 7.3A.4 Void + +## 7.3B Reference sensitivity level for DC + +### 7.3B.1 General + +For EN-DC, E-UTRA and NR single carrier, CA, and MIMO operation of REFSENS requirements defined in TS 38.101-1 [2], TS 38.101-2 [3] and TS 36.101 [5] apply to all downlink bands of EN-DC configurations listed in clause 5.5B, unless sensitivity degradation exception is allowed in this clause of this specification, clause 7.3 in TS 38.101-1 [2], clause 7.3 in TS 38.101-2 [3] or clause 7.3 in TS 36.101 [5]. Allowed exceptions specified in this clause of the specification, clause 7.3 in TS 38.101-1 [2], clause 7.3 in TS 38.101-2 [3] or clause 7.3 in TS 36.101 [4] also apply to any higher order EN-DC configuration combination containing one of the band combinations that exception is allowed for. Reference sensitivity exceptions are specified by applying maximum sensitivity degradation (MSD) into applicable REFSENS requirement. EN-DC REFSENS requirements shall be met for NR uplink transmissions using QPSK DFT-s-OFDM waveforms as defined in clause 7.3.2 in TS 38.101-1 [2]. Unless otherwise specified UL allocation uses the lowest SCS allowable for a given channel BW. Limits on configured maximum output power for the uplink according to subclause 6.2B.4 shall apply. + +In case of interband EN-DC the receiver REFSENS requirements in this clause do not apply for 1.4 and 3 MHz E-UTRA carriers. For the case of inter-band EN-DC with a single carrier per cell group and multi-carrier per cell group, in addition to the E-UTRA and NR single carrier, CA, and MIMO operation of REFSENS requirements defined in TS 38.101-1 [2], TS 38.101-2 [3], and TS 36.101 [5], the REFSENS requirements specified therein also apply with both downlink carriers and both uplink carriers active unless sensitivity exceptions are allowed in this clause of this specification, clause 7.3 in TS 38.101-1 [2] or clause 7.3 in TS 36.101 [5]. + +For reference sensitivity exception test points where the specified carrier frequency does not correspond to a valid NR-ARFCN, the closest NR-ARFCN as specified in TS 38.101-1 [2] clause 5.4.2 applies. + +For operations with 4 Rx antenna ports in an E-UTRA band or an NR band, the MSD in the applicable bands shall be increased by the absolute value of $\Delta R_{IB,4R}$ in Table 7.3.1-1a of TS 36.101[5] for the E-UTRA band or in Table 7.3.2-2 of TS 38.101-1 [2] for the NR band when $MSD > 0$ . + +NOTE: For inter-band EN-DC, the reference sensitivity requirement with both uplink carriers active is allowed to be verified for only a single inter-band EN-DC configuration per NR band. + +### 7.3B.2 Reference sensitivity for EN-DC + +#### 7.3B.2.0 Minimum Conformance Requirements of Reference sensitivity for EN-DC + +##### 7.3B.2.0.1 Intra-band contiguous EN-DC + +For intra-band contiguous EN-DC configurations, the reference sensitivity power level REFSENS is the minimum mean power applied to each one of the UE antenna ports at which the throughput for the carrier(s) of the E-UTRA and NR CGs shall meet or exceed the requirements for the specified E-UTRA and NR reference measurement channels. The reference sensitivity requirements apply with all uplink carriers and all downlink carriers active for EN-DC configuration and Uplink EN-DC configuration listed in Table 5.5B.2-1 and Table 5.5B.3-1, as supported by the UE. For EN-DC configurations where uplink is not available in either the MCG or the SCG or for EN-DC configurations where the UE only supports single uplink operation, reference sensitivity requirements apply with single uplink transmission. The downlink carrier(s) from the cell group with uplink shall be configured closer to the uplink operating band than any of the downlink carriers from the cell group without uplink. + +Sensitivity degradation is allowed for Intra-band contiguous EN-DC configurations listed in Table 7.3B.2.0.1-1, the reference sensitivity is defined only for the specific uplink and downlink test points which are specified in Table 7.3B.2.0.1-1 and E-UTRA and NR single carrier requirements do not apply. + +**Table 7.3B.2.0.1-1: Reference sensitivity (MSD) for intra-band contiguous EN-DC** + +| EN-DC configuration/channel allocations/MSD | | | | | | | | +|---------------------------------------------|----------------|---------------------------|-------------------------|-----------------------------------|---------------------------|----------|-------------| +| EN-DC configuration | E-UTRA/NR band | F c (UL) (MHz) | Channel bandwidth (MHz) | UL allocation (L CRB ) | F c (DL) (MHz) | MSD (dB) | Duplex mode | +| DC_(n)71AA | 71 | 665.5 | 5 | 5 (RB end = 24) | 619.5 | 0 | FDD | +| | n71 | 675.5 | 15 | 15 (RB start = 0) | 629.5 | 1.8 | | +| DC_(n)71AA | 71 | 670.5 | 15 | 15 (RB end = 74) | 624.5 | 0 | | +| | n71 | 680.5 | 5 | 5 (RB start = 0) | 634.5 | 1.6 | | +| DC_(n)71AA | 71 | 668 | 10 | 10 (RB end = 49) | 622 | 0 | | +| | n71 | 678 | 10 | 10 (RB start = 0) | 632 | 1.7 | | +| DC_(n)71AA | 71 | 668 | 10 | 10 (RB start = 0) | 622 | 17.2 | | +| | n71 | 678 | 10 | 10 (RB end = 51) | 632 | 29.4 | | +| DC_(n)71AA | 71 | 665.5 | 5 | 5 (RB end = 24) | 619.5 | 0 | | +| | n71 | 675.5 | 151 | 15 (RB start = 0) | 6321 | 2.5 | | +| DC_(n)71AA | 71 | 670.5 | 15 | 15 (RB end = 74) | 624.5 | 0 | FDD | +| | n71 | 680.5 | 51 | 5 (RB start = 0) | 6371 | 2.2 | | +| DC_(n)71AA | 71 | 668 | 10 | 10 (RB end = 49) | 622 | 0 | | +| | n71 | 678 | 101 | 10 (RB start = 0) | 634.51 | 2.5 | | +| DC_(n)71AA | 71 | 668 | 10 | 10 (RB start = 0) | 622 | 17.2 | | +| | n71 | 678 | 101 | 10 (RB end = 51) | 634.51 | 29.1 | | + +NOTE 1: In accordance to BCS1, the NR uplink bandwidth is specified as in this table, but the corresponding NR downlink bandwidth is 5 MHz larger. +NOTE 2: The transmitters powers shall be set to PUMAX, as defined in TS 38.101-1 [2], TS 38.101-2 [3], and TS 36.101 [5], with additional limits on configured maximum output power for the uplink according to subclause 6.2B.4. + +##### 7.3B.2.0.2 Intra-band non-contiguous EN-DC + +For intra-band non-contiguous EN-DC configurations, the reference sensitivity power level REFSENS is the minimum mean power applied to each one of the UE antenna ports at which the throughput for the carrier(s) of the E-UTRA and NR CGs shall meet or exceed the requirements for the specified E-UTRA and NR reference measurement channels. + +For DC\_3A\_n3A intra-band non-contiguous EN-DC combination, only single switched UL is supported in rel.15, therefore, no MSD is specified and E-UTRA and NR single carrier requirements apply. + +##### 7.3B.2.0.3 Inter-band EN-DC within FR1 + +Reference sensitivity exceptions are specified for the condition when there is uplink transmission only in the aggressor band. + +###### 7.3B.2.0.3.1 Reference sensitivity exceptions due to UL harmonic interference for EN-DC in NR FR1 + +Sensitivity degradation is allowed for a band if it is impacted by UL harmonic interference from another band part of the same EN-DC configuration. Reference sensitivity exceptions for the victim band (high) are specified in Table 7.3B.2.0.3.1-1 with uplink configuration of the aggressor band (low) specified in Table 7.3B.2.0.3.1-2. + +**Table 7.3B.2.0.3.1-1: Reference sensitivity exceptions (MSD) due to UL harmonic for EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band / MSD | | | | | | | | | | | | | | | +|---------------------------------------------------------------------|-----------------------------------------|------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------| +| UL band | DL band | 5 MHz (dB) | 10 MHz (dB) | 15 MHz (dB) | 20 MHz (dB) | 25 MHz (dB) | 30 MHz (dB) | 40 MHz (dB) | 50 MHz (dB) | 60 MHz (dB) | 70 MHz (dB) | 80 MHz (dB) | 90 MHz (dB) | 100 MHz (dB) | +| 1, 3 | n77 2, 13 | | 23.9 | 22.1 | 20.9 | | | 17.9 | 16.8 | 16.0 | | 14.8 | 14.3 | 13.8 | +| | n77 3 | | 1.1 | 0.8 | 0.3 | | | | | | | | | | +| 2 | n77 2, 13 | | 23.9 | 22.1 | 20.9 | 19.8 | 19.0 | 17.9 | 16.8 | 16.0 | 15.5 | 14.8 | 14.3 | 13.8 | +| | n77 3 | | 1.1 | 0.8 | 0.3 | 0.1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | n78 2, 13 | | 23.9 | 22.1 | 20.9 | | | 17.9 | 16.8 | 16.0 | | 14.8 | 14.3 | 13.8 | +| | n78 3 | | 1.1 | 0.8 | 0.3 | | | | | | | | | | +| 3 | n78 2, 13 | | 23.9 | 22.1 | 20.9 | | | 17.9 | 16.8 | 16.0 | | 14.8 | 14.3 | 13.8 | +| | n78 3 | | 1.1 | 0.8 | 0.3 | | | | | | | | | | +| 5 | n78 6, 7 | | 10.5 | 8.9 | 7.8 | | | 5.4 | 4.2 | 3.5 | | 2.3 | 2.1 | 1.4 | +| 5 | n77 6, 7, 17 | | 10.5 | 8.9 | 7.8 | 7.2 | 6.5 | 5.1 | 4.2 | 3.5 | 2.8 | 2.3 | 2.1 | 1.4 | +| | n77 4, 5, 17 | | 10.4 | 8.9 | 7.8 | 6.7 | 6 | 4.7 | 3.7 | 3 | 2.3 | 1.7 | 1.2 | 0.7 | +| 8 | n41 8, 9 | | 13 | 11.3 | 10.1 | | 8.3 | 7.0 | 6.1 | 5.5 | | 4.3 | 3.9 | 3.5 | +| 8 | n77 6, 7 | | 10.8 | 9.1 | 8 | | | 5.1 | 4.2 | 3.5 | | 2.3 | 2.1 | 1.4 | +| | n78 6, 7 | | | | | | | | | | | | | | +| 8 | n79 4, 5 | | | | | | | 6.8 | 6.2 | 5.6 | | 4.9 | | 4.4 | +| 12 | n66 8, 9, 10 | 10 | 7.5 | 6.2 | 5.5 | | | 2.4 | | | | | | | +| 12 | n77 5 | | 10.4 | 8.9 | 7.8 | 6.7 | 5.7 | 4.7 | 3.7 | 3 | 2.3 | 1.7 | 1.2 | 0.7 | +| 12 | n78 4, 5 | | 10.4 | 8.9 | 7.8 | 7.1 | 6.5 | 4.7 | 3.7 | 3 | 2.3 | 1.7 | 1.2 | 0.7 | +| 13 | n77 4, 5 | | 10.4 | 8.9 | 7.8 | 6.7 | 5.7 | 4.7 | 3.7 | 3 | 2.3 | 1.7 | 1.2 | 0.7 | +| 14 | n77 4, 5 | | 10.4 | 8.9 | 7.8 | 6.7 | 5.7 | 4.7 | 3.7 | 3 | 2.3 | 1.7 | 1.2 | 0.7 | +| 18, 19 | n77 4, 5 | | 10.4 | 8.9 | 7.8 | | | 4.7 | 3.7 | 3 | | 1.7 | 1.2 | 0.7 | +| | n78 4, 5 | | | | | | | | | | | | | | +| 28 | n51 2, 13 | 27.8 | | | | | | | | | | | | | +| | n51 3 | 1.9 | | | | | | | | | | | | | +| 28 | n77 4, 5 n78 4, 5 | | 10.4 | 8.9 | 7.8 | | | 4.7 | 3.7 | 3 | | 1.7 | 1.2 | 0.7 | +| 20 | n77 6, 7 | | 10.8 | 9.1 | 8 | | | 6 | 4.0 | 3.2 | | 2.0 | 1.5 | 1.0 | +| | n78 6, 7 | | | | | | | | | | | | | | +| n28 | 21 16 | N/A | N/A | N/A | | | | | | | | | | | +| 26 | n41 8, 9 | | 10.3 | 8.4 | 7.4 | | | 5 | 4.3 | 3.9 | | 3.1 | 2.7 | | +| 26 | n77 6, 7 | | 10.8 | 9.1 | 8 | | | 6 | 4.0 | 3.2 | | 2.0 | 1.5 | 1.0 | +| | n78 6, 7 | | | | | | | | | | | | | | +| n28 | 1 8, 9, 10 | 10.2 | 7.6 | 6.2 | 5.3 | | | | | | | | | | +| 71 | n2 11 | 4.6 | 1.0 | 0.7 | 0.6 | | | | | | | | | | +| | n2 12 | 1.7 | 1.0 | 0.7 | 0.6 | | | | | | | | | | +| n71 | 2 11 | 4.6 | 1.0 | 0.7 | 0.6 | | | | | | | | | | +| | 2 12 | 1.7 | 1.0 | 0.7 | 0.6 | | | | | | | | | | +| n71 | 7 6, 7 | 14.6 | 11.7 | 10.1 | 9 | | | | | | | | | | +| 66 | n77 2, 13 | | 23.9 | 22.1 | 20.9 | 19.8 | 19.0 | 17.9 | 16.8 | 16.0 | 15.3 | 14.8 | 14.3 | 13.8 | +| | n77 3 | | 1.1 | 0.8 | 0.3 | 0.1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 66 | n78 2, 13 | | 23.9 | 22.1 | 20.9 | | | 17.9 | 16.8 | 16.0 | | 14.8 | 14.3 | 13.8 | +| | n78 3 | | 1.1 | 0.8 | 0.3 | | | | | | | | | | +| n66 | 48 2, 13 | 27.3 | 24.4 | 22.4 | 21.2 | | | | | | | | | | +| | 48 3 | 1.9 | 1.4 | 0.9 | 0.4 | | | | | | | | | | + +NOTE 1: Void. + +NOTE 2: The requirements should be verified for UL EARFCN or NR ARFCN of the aggressor (lower) band (superscript LB) such + +that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the lower band. + +- NOTE 3: The requirements are only applicable to channel bandwidths no larger than 20 MHz and with a carrier frequency at MHz offset from in the victim (higher band) with $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ , where and are the channel bandwidths configured in the aggressor (lower) and victim (higher) bands in MHz, respectively. +- NOTE 4: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (lower) band for which the 5th transmitter harmonic is within the downlink transmission bandwidth of a victim (higher) band. +- NOTE 5: The requirements should be verified for UL EARFCN of the aggressor (lower) band (superscript LB) such that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the lower band. +- NOTE 6: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (lower) band for which the 4th transmitter harmonic is within the downlink transmission bandwidth of a victim (higher) band. +- NOTE 7: The requirements should be verified for UL EARFCN of the aggressor (lower) band (superscript LB) such that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the lower band. +- NOTE 8: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of a low band for which the 3rd transmitter harmonic is within the downlink transmission bandwidth of a high band. +- NOTE 9 The requirements should be verified for UL EARFCN of the aggressor (lower) band (superscript LB) such that $f_{UL}^{LB} = \lceil f_{DL}^{HB} / 0.3 \rceil 0.1$ in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with $f_{DL}^{HB}$ the carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the low band. +- NOTE 10: Applicable for the operations with 2 or 4 antenna ports supported in the band with carrier aggregation configured. +- NOTE 11: These requirements apply when the lower edge frequency of the 5 MHz uplink channel in Band 71 is located at or below 668 MHz and the downlink channel in Band 2 is located with its upper edge at 1990 MHz. +- NOTE 12: These requirements apply when the lower edge frequency of the 10 MHz, 15 MHz, or 20 MHz uplink channel in Band 71 is located at or below 668 MHz and the downlink channel in Band 2 is located with its upper edge at 1990 MHz. +- NOTE 13: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (lower) band for which the 2nd transmitter harmonic is within the downlink transmission bandwidth of a victim (higher) band and a range $\Delta F_{HD}$ above and below the edge of this downlink transmission bandwidth. The value $\Delta F_{HD}$ depends on the EN-DC band combination: $\Delta F_{HD} = 10$ MHz for DC\_1\_n77, DC\_2\_n48, DC\_2\_n77, DC\_48\_n66, DC\_66\_n48, DC\_66\_n77, DC\_3\_n77, DC\_3\_n78, DC\_66\_n78, and DC\_25\_n77. +- NOTE 14: No requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the low band for which the 2nd transmitter harmonic is within the downlink transmission bandwidth of the high band. The reference sensitivity for all active downlink component carriers is only verified when this is not the case (the requirements specified in clause 7.3.1 from TS 36.101-1 apply unless otherwise specified). +- NOTE 15: MSD test point can be chosen according to supported BW and lowest SCS supported by the UE. +- NOTE 16: The frequency range in band n28 is restricted for this band combination to 728 - 738 MHz for the UL. This band is subject to 2nd harmonic fall in B21 also which MSD is not specified. +- NOTE 17: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +**Table 7.3B.2.0.3.1-2: Uplink configuration for reference sensitivity exceptions due to UL harmonic interference for EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band / UL RB allocation of the aggressor band | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------|-----------------|-----------------------|--------------------------------------|-----------------------------------|-----------------------------------|--------------------------------------|---------------------------------------|---------------------------------------|---------------------------------------|---------------------------------------|----------------------------|---------------------------------------|---------------------------------------|----------------------------|----------------------------------------| +| UL band | DL band | SC S of UL band (kHz) | 5 MHz (L CR B) | 10 MHz (L CRB ) | 15 MHz (L CRB ) | 20 MHz (L CRB ) | 25 MHz (L CR B) | 30 MHz (L CR B) | 40 MHz (L CR B) | 50 MHz (L CR B) | 60 MHz (L CRB ) | 70 MHz (L CR B) | 80 MHz (L CR B) | 90 MHz (L CRB ) | 100 MHz (L CR B) | +| 1 | n77 | 15 | | 25 | 36 | 50 | | | 100 | 100 | 100 | | 100 | 100 | 100 | +| 2 | n77 | 15 | | 25 | 36 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | +| 2 | n78 | 15 | | 25 | 36 | 50 | | | 50 | 50 | 50 | | 50 | 50 | 50 | +| 3 | n77 | 15 | | 25 | 36 | 50 | | | 50 | 50 | 50 | | 50 | 50 | 50 | +| 3 | n78 | 15 | | 25 | 36 | 50 | | | 50 | 50 | 50 | | 50 | 50 | 50 | +| 5 | n77 | 15 | | 16 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | +| 5 | n78 | 15 | 8 | 16 | 25 | 25 | | | 25 | | | | | | | +| 8 | n41 | 15 | | 16 | 25 | 25 | | 25 | 25 | 25 | 25 | | 25 | 25 | 25 | +| 8 | n77
n78 | 15 | | 16 | 25 | 25 | | | 25 | 25 | 25 | | 25 | 25 | 25 | +| 8 | n79 | 15 | | | | | | | 25 | 25 | 25 | | 25 | | 25 | +| 12 | n66 | 15 | 8 | 16 | 20 | 20 | | | 20 | | | | | | | +| 12 | n77 | 15 | | 10 | 15 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | +| 12 | n78 | 15 | | 10 | 15 | 20 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | 25 | +| 13 | n77 | 15 | | 15 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | +| 14 | n77 | 15 | | 15 | 15 | 15 | 15 | 15 | 15 | 15 | 15 | 15 | 15 | 15 | 15 | +| 18 | n77
,
n78 | 15 | | 16 | 25 | 25 | | | 25 | 25 | 25 | | 25 | 25 | 25 | +| 19 | n77
,
n78 | 15 | | 16 | 25 | 25 | | | 25 | 25 | 25 | | 25 | | 25 | +| 20 | n77
n78 | 15 | | 16 | 25 | 25 1 ,
25 2 | | | 25 | 25 | 25 | | 25 | 25 | 25 | +| 26 | n41 | 15 | | 16 | 25 | 25 | | | 25 | 25 | | | | | | +| 26 | n77
n78 | 15 | | 16 | 25 | 25 | | | 25 | 25 | 25 | | 25 | 25 | 25 | +| n28 | 1 | 15 | 8 | 16 | 25 | 25 | | | | | | | | | | +| 28 | n51 | 15 | 12 | | | | | | | | | | | | | +| 28 | n77
n78 | 15 | | 10 | -15 | 20 | | | 25 | 25 | 25 | | 25 | 25 | 25 | +| 66 | n77 | 15 | | 25 | 36 | 50 | 64 | 80 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | +| 66 | n78 | 15 | | 25 | 36 | 50 | | | 100 | 100 | 100 | | 100 | 100 | 100 | +| n66 | 48 | 15 | 12 | 25 | 36 | 50 | | | | | | | | | | +| 71 | n2 | 15 | 25 4
8 5 | 25 4
8 5 | 20 4
8 5 | 20 4
8 5 | | | | | | | | | | +| n71 | 2 | 15 | 25 4
8 5 | 25 4
8 5 | 20 4
8 5 | 20 4
8 5 | | | | | | | | | | +| n71 | 7 | 15 | 8 | 16 | 25 | 25 | | | | | | | | | | + +NOTE 1: The UL configuration applies regardless of the channel bandwidth of the UL band unless the UL resource blocks exceed that specified in Table 7.3.1-2 in TS 36.101 [5] or Table 7.3.2-3 in TS 38.101-1 [2] for the uplink bandwidth in which case the allocation according to Table 7.3.1-2 in TS 36.101 [5] or Table 7.3.2-3 in TS 38.101-1 [2] applies. + +NOTE 2: Void. + +NOTE 3: Unless stated otherwise, UL resource blocks shall be centred within the transmission bandwidth configuration for the channel bandwidth. + +| | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 4: | These requirements apply when the lower edge frequency of the 5 MHz uplink channel in Band 71 is located at or below 668 MHz and the downlink channel in Band 2 is located with its upper edge at 1990 MHz. | +| NOTE 5: | These requirements apply when the lower edge frequency of the 10 MHz, 15 MHz, or 20 MHz uplink channel in Band 71 is located at or below 668 MHz and the downlink channel in Band 2 is located with its upper edge at 1990 MHz. | +| NOTE 6: | If the aggressor band is NR band, the test SCS and UL RB can be adjusted according to supported BW and lowest SCS supported by the UE. | + +**Table 7.3B.2.0.3.1-3: Reference sensitivity QPSK PREFSENS (EN-DC with n46)** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band / MSD | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------| +| UL band | DL band | 5 MHz (dB) | 10 MHz (dB) | 15 MHz (dB) | 20 MHz (dB) | 25 MHz (dB) | 40 MHz (dB) | 50 MHz (dB) | 60 MHz (dB) | 80 MHz (dB) | 90 MHz (dB) | 100 MHz (dB) | +| n46 | 48 2,4 | 22.6 | 19.5 | 17.8 | 16.6 | | | | | | | | +| NOTE 1: FFS | | | | | | | | | | | | | +| NOTE 2: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (higher) band and when the frequency range of relative higher band's uplink channel bandwidth or uplink 1 st adjacent channel bandwidth is fully or partially overlapped with the downlink transmission bandwidth of a victim (lower) band. | | | | | | | | | | | | | +| NOTE 3: FFS | | | | | | | | | | | | | +| NOTE 4: The requirements should be verified for UL NR-ARFCN of the aggressor (high) band (superscript HB) such that in MHz and with carrier frequency in the victim (lower) band in MHz and the channel bandwidth configured in the higher band. | | | | | | | | | | | | | + +**Table 7.3B.2.0.3.1-4: n46 Reference sensitivity measurement exclusion region in MHz** + +FFS + +**Table 7.3B.2.0.3.1-5: Uplink configuration for reference sensitivity exceptions due to receiver harmonic mixing for EN-DC paring with n46** + +| E-UTRA or NR Band / SCS / Channel bandwidth of the affected DL band / UL RB allocation of the aggressor band | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------|---------|----------------------|---------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|-----------------------------| +| UL band | DL band | SCS of UL band (kHz) | 5 MHz (L CRB ) | 10 MHz (L CRB ) | 15 MHz (L CRB ) | 20 MHz (L CRB ) | 25 MHz (L CRB ) | 40 MHz (L CRB ) | 50 MHz (L CRB ) | 60 MHz (L CRB ) | 80 MHz (L CRB ) | 90 MHz (L CRB ) | 100 MHz (L CRB ) | +| n46 | 48 | 15 | 12 | 25 | 36 | 50 | | | | | | | | + +###### **7.3B.2.0.3.2 Reference sensitivity exceptions due to receiver harmonic mixing for EN-DC in NR FR1** + +Sensitivity degradation is allowed for a band if it is impacted by receiver harmonic mixing due to another band part of the same EN-DC configuration. Reference sensitivity exceptions for the victim band (low) are specified in Table 7.3B.2.0.3.2-1 with uplink configuration of the aggressor band (high) specified in Table 7.3B.2.0.3.2-2. + +**Table 7.3B.2.0.3.2-1: Reference sensitivity exceptions (MSD) due to receiver harmonic mixing for EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band / MSD | | | | | | | | | | | | | +|---------------------------------------------------------------------|------------------|------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------| +| UL band | DL band | 5 MHz (dB) | 10 MHz (dB) | 15 MHz (dB) | 20 MHz (dB) | 25 MHz (dB) | 40 MHz (dB) | 50 MHz (dB) | 60 MHz (dB) | 80 MHz (dB) | 90 MHz (dB) | 100 MHz (dB) | +| 2 | n71 4 | 26.8 | 23.6 | 21.2 | 15.6 | | | | | | | | +| n2 | 71 4 | 26.8 | 23.6 | 21.2 | 15.6 | | | | | | | | +| n41 | 26 4 | 24.3 | 24.3 | 22.5 | N/A | | | | | | | | +| n77 | 2 | 6.1 | 5.0 | 4.0 | 3.7 | | | | | | | | +| n77 | 3 | 5.7 | 4.0 | 3.0 | 2.7 | | | | | | | | +| n77 | 12 2 | 31 | 28 | | | | | | | | | | +| n77 | 13 2 | 31 | 28 | | | | | | | | | | +| n77 | 14 2 | 31 | 28 | | | | | | | | | | +| n78 | 3 | 5.7 | 4.0 | 3.0 | 2.7 | | | | | | | | +| n77 | 41 8 | 10.4 | 10.4 | 10.4 | 10.4 | | | | | | | | +| n77 | 28 2 | 28 | 25 | 23.2 | 22 | | | | | | | | +| n78 | 41 8 | 10.4 | 10.4 | 10.4 | 10.4 | | | | | | | | +| n79 | 11 4 | 39.3 | 36.3 | 34.5 | | | | | | | | | +| n79 | 19 2 | 29.5 | 26.5 | 24.7 | | | | | | | | | +| n79 | 21 4 | 39.3 | 36.3 | 34.5 | | | | | | | | | +| n79 | 26 2 | 27 | 24 | 22.2 | | | | | | | | | + +NOTE 1: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (higher) band for which the mixing product due to harmonic of victim (lower) band LO with leakage of aggressor (higher) band is within the downlink transmission bandwidth of a victim (lower) band. + +NOTE 2: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 3: Void. + +NOTE 4: The requirements should be verified for DL EARFCN or NR-ARFCN of the victim (lower) band (superscript + +LB) such that $f_{DL}^{LB} = \left\lceil f_{UL}^{HB} / 0.3 \right\rceil 0.1$ with the DL carrier frequency in the lower band and in MHz and the UL carrier frequency in the higher band, both in MHz. + +NOTE 5: Void. + +NOTE 6: Void. + +NOTE 7: Void. + +NOTE 8: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 9: No requirements apply for the case that there is at least one individual RE within the uplink transmission bandwidth of the relative higher band and when the frequency range of relative higher band's uplink channel bandwidth or uplink 1st adjacent channel bandwidth is fully or partially overlapped with the 3 times of the frequency range of the relative lower band's downlink channel bandwidth. The reference sensitivity is only verified when this is not the case + +NOTE 10: MSD test point can be chosen according to supported BW and lowest SCS supported by the UE. + +NOTE 11: The MSD test points cannot be verified for the band combination in US due to the Band n77 frequency range restriction. + +**Table 7.3B.2.0.3.2-1a: Reference sensitivity exceptions (MSD) due to receiver harmonic mixing for PC2 EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band / MSD | | | | | | | | | | | | | +|---------------------------------------------------------------------|-----------------|------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------| +| UL band | DL band | 5 MHz (dB) | 10 MHz (dB) | 15 MHz (dB) | 20 MHz (dB) | 25 MHz (dB) | 40 MHz (dB) | 50 MHz (dB) | 60 MHz (dB) | 80 MHz (dB) | 90 MHz (dB) | 100 MHz (dB) | +| n77 | 2 | 9.1 | 8.0 | 7.0 | 6.7 | | | | | | | | +| n77 | 12 1 | 34 | 31 | | | | | | | | | | +| n77 | 13 1 | 34 | 31 | | | | | | | | | | +| n77 | 14 1 | 34 | 31 | | | | | | | | | | +| n79 | 19 1 | 32.5 | 29.5 | 27.7 | | | | | | | | | +| n79 | 21 4 | 42.3 | 39.3 | 37.5 | | | | | | | | | + +NOTE 1: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 2: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +NOTE 3: Void. + +NOTE 4: The requirements should be verified for DL EARFCN or NR-ARFCN of the victim (lower) band (superscript LB) such that $f_{DL}^{LB} = \left\lfloor f_{UL}^{HB} / 0.3 \right\rfloor 0.1$ with the DL carrier frequency in the lower band and in MHz and the UL carrier frequency in the higher band, both in MHz. + +**Table 7.3B.2.0.3.2-2: Uplink configuration for reference sensitivity exceptions due to receiver harmonic mixing for EN-DC in NR FR1** + +| E-UTRA or NR Band / SCS / Channel bandwidth of the affected DL band / UL RB allocation of the aggressor band | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------|---------|----------------------|---------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|-----------------------------| +| UL band | DL band | SCS of UL band (kHz) | 5 MHz (L CRB ) | 10 MHz (L CRB ) | 15 MHz (L CRB ) | 20 MHz (L CRB ) | 25 MHz (L CRB ) | 40 MHz (L CRB ) | 50 MHz (L CRB ) | 60 MHz (L CRB ) | 80 MHz (L CRB ) | 90 MHz (L CRB ) | 100 MHz (L CRB ) | +| 2 | n71 | 15 | 25 | 50 | 50 | 50 | | | | | | | | +| n2 | 71 | 15 | 25 | 50 | 50 | 50 | | | | | | | | +| n41 | 26 | 15 | 25 | 50 | 75 | | | | | | | | | +| n77 | 2 | 15 | 25 | 50 | 75 | 100 | | | | | | | | +| n77 | 3 | 15 | 25 | 50 | 75 | 100 | | | | | | | | +| n77 | 12 | 15 | 25 | 50 | | | | | | | | | | +| n77 | 13 | 15 | 25 | 50 | | | | | | | | | | +| n77 | 14 | 15 | 25 | 50 | | | | | | | | | | +| n78 | 3 | 15 | 25 | 50 | 75 | 100 | | | | | | | | +| n77 | 28 | 15 | 25 | 50 | 75 | 100 | | | | | | | | +| n77 | 41 | 15 | 12 | 25 | 36 | 50 | | | | | | | | +| n78 | 41 | 15 | 12 | 25 | 36 | 50 | | | | | | | | +| n79 | 11 | 15 | 25 | 50 | 75 | | | | | | | | | +| n79 | 19 | 15 | 25 | 50 | 75 | | | | | | | | | +| n79 | 21 | 15 | 25 | 50 | 75 | | | | | | | | | +| n79 | 26 | 15 | 25 | 50 | 75 | | | | | | | | | + +NOTE 1: Void. + +NOTE 2: Void. + +NOTE 3: The UL configuration applies regardless of the channel bandwidth of the UL band. UL resource blocks allocation in the table shall be further limited to that specified in Table 7.3.1-2 in TS 36.101 [5] or Table 7.3.2-3 in TS 38.101-1[2]. + +NOTE 4: Unless otherwise stated, the UL resource blocks allocation is applied at the centre of the channel bandwidth. The note applies to the entire table. + +NOTE 5: If the aggressor band is NR band, the test SCS and UL RB can be adjusted according to supported BW and lowest SCS supported by the UE. + +7.3B.2.0.3.3 Void + +7.3B.2.0.3.4 Reference sensitivity exceptions due to cross band isolation for EN-DC in NR FR1 + +Sensitivity degradation is allowed for a band if it is impacted by UL of another band part of the same EN-DC configuration due to cross band isolation issues. Reference sensitivity exceptions for the victim band are specified in Table 7.3B.2.0.3.4-1, Table 7.3B.2.0.3.4-1a with uplink configuration of the aggressor band specified in Table 7.3B.2.0.3.4-2. + +**Table 7.3B.2.0.3.4-1: Reference sensitivity exceptions (MSD) due to cross band isolation for PC3 EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band /MSD | | | | | | | | | | | | | | +|--------------------------------------------------------------------|-----------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------| +| UL band | DL band | 5 MHz (dBm) | 10 MHz (dB) | 15 MHz (dB) | 20 MHz (dB) | 25 MHz (dB) | 30 MHz (dB) | 40 MHz (dB) | 50 MHz (dB) | 60 MHz (dB) | 80 MHz (dB) | 90 MHz (dB) | 100 MHz (dB) | +| n1 5 | 3 | 3 | 2.3 | 2 | 1.8 | | | | | | | | | +| 1 5 | n3 | 3 | 2.2 | 1.9 | 1.7 | 1.6 | 1.5 | [1.4] | | | | | | +| 1 | n40 | 6.6 | 6.6 | 6.6 | 6.6 | 6.6 | 6.6 | 6.6 | 6.6 | 6.6 | 6.6 | | | +| 1 | n41 | | 6.1 | 6.1 | 6.1 | | 6.1 | 6.1 | 6.1 | 6.1 | 6.1 | 6.1 | 6.1 | +| 3 | n41 | | 0.7 | 0.7 | 0.7 | | [0.7] | 0.7 | 0.7 | 0.7 | 0.7 | 0.7 | 0.7 | +| n5 | 28 | 4.5 | 3 | 2.2 | 0.3 | | | | | | | | | +| n40 | 1 | 8.3 | 8.3 | 8.3 | 8.3 | | | | | | | | | +| n41 | 1 | 9.1 | 9.1 | 9.1 | 9.1 | | | | | | | | | +| n41 | 2 | 0.6 | 0.6 | 0.6 | 0.6 | | | | | | | | | +| n41 | 3 | 0.6 | 0.6 | 0.6 | 0.6 | | | | | | | | | +| n41 | 25 | 0.6 | 0.6 | 0.6 | 0.6 | | | | | | | | | +| n77 | 41 1 | 4.5 | 4.5 | 4.5 | 4.5 | | | | | | | | | +| n41 | 66 1 | 3.5 | 3.5 | 3.5 | 3.5 | | | | | | | | | +| 41 | n77 | | 8.3 | 8.3 | 8.3 | | | 6.3 | 5.3 | 4.5 | 4.0 | 3.9 | 3.8 | +| 3 | n51 | 6.4 | | | | | | | | | | | | +| 30 | n66 | 8.3 | 8.3 | 8.3 | 8.3 | | | 8.3 | | | | | | +| n78 | 7 1 | 4.5 | 4.5 | 4.5 | 4.5 | | | | | | | | | +| n78 | 38 | 3.3 | 3.3 | 3.3 | 3.3 | | | | | | | | | +| n78 | 41 1 | 4.5 | 4.5 | 4.5 | 4.5 | | | | | | | | | +| n78 | 46 | | | | 7 | | | | | | | | | +| 41 | n78 | | 8.3 | 8.3 | 8.3 | | | 6.3 | 5.3 | 4.5 | 4.0 | 3.9 | 3.8 | +| n79 | 42 4 | 2.8 | 2.8 | 2.8 | 2.8 | | | | | | | | | +| 48 | n46 | - | - | - | 7 | - | - | 5.7 | - | 5.1 | 4.7 | - | - | +| n46 | 48 | 13.3 | 10.4 | 8.8 | 7.8 | - | - | 7.8 | 7 | 6.5 | 5.7 | 5.4 | 5.1 | + +NOTE 1: Applicable only when harmonic mixing MSD for this combination is not applied. + +NOTE 2: The B41 requirements are modified by -0.5dB when carrier frequency of the assigned E-UTRA channel bandwidth is within 2515 – 2690 MHz. + +NOTE 3: These requirements apply when the uplink is active in Band n1, n84 and the separation between the lower edge of the uplink channel in Band n1, n84 and the upper edge of the downlink channel in Band 3 is < 60 MHz. For each channel bandwidth in Band 3, the requirement applies regardless of channel bandwidth in Band n1, n84. + +NOTE 4: The DL victim band should be configured using the lowest SCS that is compatible with the highest CBW for which an MSD is specified. + +NOTE 5: MSD test point can be chosen according to supported BW and lowest SCS supported by the UE. + +NOTE 6: The requirements only apply for UEs supporting inter-band DC\_42\_n79 ENDC with simultaneous Rx/Tx capability. Simultaneous Rx/Tx capability does not apply for UEs supporting band 42 with a n77 implementation only. These restrictions are applicable to related higher order configurations. + +**Table 7.3B.2.0.3.4-1a: Reference sensitivity exceptions (MSD) due to cross band isolation for PC2 EN-DC in NR FR1** + +| UL band | DL band | E-UTRA or NR Band / Channel bandwidth of the affected DL band / MSD | | | | | | | | | | | | +|---------|---------|---------------------------------------------------------------------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------| +| | | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 90 MHz | 100 MHz | +| | | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | (dB) | +| 3 | n41 | | 0.7 | 0.7 | 0.7 | | | 0.7 | 0.7 | 0.7 | 0.7 | 0.7 | 0.7 | +| n41 | 3 | 2.3 | 2.3 | 2.3 | 2.3 | | | | | | | | | + +**Table 7.3B.2.0.3.4-2: Uplink configuration for reference sensitivity exceptions due to cross band isolation for PC3 EN-DC in NR FR1** + +| E-UTRA or NR Band / SCS / Channel bandwidth of the affected DL band / UL RB allocation of the aggressor band | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------|---------|----------------------|---------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|-----------------------------| +| UL band | DL band | SCS of UL band (kHz) | 5 MHz (L CRB ) | 10 MHz (L CRB ) | 15 MHz (L CRB ) | 20 MHz (L CRB ) | 25 MHz (L CRB ) | 30 MHz (L CRB ) | 40 MHz (L CRB ) | 50 MHz (L CRB ) | 60 MHz (L CRB ) | 80 MHz (L CRB ) | 90 MHz (L CRB ) | 100 MHz (L CRB ) | +| n1 | 3 | 15 | 25 | 25 | 25 | 25 | | | | | | | | | +| 1 | n3 | 15 | 25 | 25 | 25 | 25 | 25 | 25 | [25] | | | | | | +| 1 | n40 | 15 | 25 | 50 | 75 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | +| 1 | n41 | 15 | | 100 | 100 | 100 | | 100 | 100 | 100 | 100 | 100 | 100 | 100 | +| 3 | n41 | 15 | | 50 | 50 | 50 | | [50] | 50 | 50 | 50 | 50 | 50 | 50 | +| n5 | 28 | 15 | 25 | 25 | 20 | 20 | | | | | | | | | +| n40 | 1 | 15 | 25 | 50 | 75 | 100 | | | | | | | | | +| n41 | 1 | 30 | 128 | 128 | 128 | 128 | | | | | | | | | +| n41 | 2 | 30 | 160 | 160 | 160 | 160 | | | | | | | | | +| n41 | 3 | 30 | 160 | 160 | 160 | 160 | | | | | | | | | +| n41 | 25 | 30 | 160 | 160 | 160 | 160 | | | | | | | | | +| n77 | 41 | 30 | 270 | 270 | 270 | 270 | | | | | | | | | +| n41 | 66 | 30 | 128 | 128 | 128 | 128 | | | | | | | | | +| 41 | n77 | 15 | | 100 | 100 | 100 | | | 100 | 100 | 100 | 100 | 100 | 100 | +| 3 | n51 | 15 | 25 | | | | | | | | | | | | +| 30 | n66 | 15 | 25 | 25 | 25 | 25 | | | 25 | | | | | | +| n78 | 7 | 30 | 270 | 270 | 270 | 270 | | | | | | | | | +| n78 | 38 | 30 | 270 | 270 | 270 | 270 | | | | | | | | | +| n78 | 41 | 30 | 270 | 270 | 270 | 270 | | | | | | | | | +| n78 | 46 | 30 | | | | 270 | | | | | | | | | +| 41 | n78 | 15 | | 100 | 100 | 100 | | | 100 | 100 | 100 | 100 | 100 | 100 | +| n79 | 42 | 30 | 270 4 | 270 4 | 270 4 | 270 4 | | | | | | | | | +| 48 | n46 | 15 | | | | 216 | | | 216 | | 216 | 216 | | | +| n46 | 48 | 30 | 216 | 216 | 216 | 216 | | | 216 | 216 | 216 | 216 | 216 | 216 | + +NOTE 1: The UL configuration applies regardless of the channel bandwidth of the UL band. UL resource blocks allocation in the table shall be further limited to that specified in Table 7.3.1-2 in TS 36.101 [5] or Table 7.3.2-3 in TS 38.101-1 [2]. + +NOTE 2: The UL resource blocks shall be located as close as possible to the downlink operating band but confined within the transmission bandwidth configuration for the channel bandwidth. + +NOTE 3: When the maximum UL RB allocation "LCRB" value is less than the maximum transmission bandwidth configuration "NRB" defined in Table 5.3.2-1 in 38.101-1 [2] for the specified UL band SCS, the UL band should be configured using the lowest CBW that is compatible with the maximum specified LCRB value. + +NOTE 4: If the aggressor band is NR band, the test SCS and UL RB can be adjusted according to supported BW and lowest SCS supported by the UE. + +NOTE 5: The requirements only apply for UEs supporting inter-band ENDC with simultaneous Rx/Tx capability. Simultaneous Rx/Tx capability does not apply for UEs supporting band 42 with a n77 implementation only. These restrictions are applicable to related higher order configurations. + +7.3B.2.0.3.5 MSD for intermodulation interference due to dual uplink operation for EN-DC in NR FR1 + +7.3B.2.0.3.5.0 General + +For EN-DC configurations in NR FR1 the UE may indicate capability of not supporting simultaneous dual uplink operation due to possible intermodulation interference overlapping in frequency to its own primary downlink channel bandwidth if + +- the intermodulation order is 2; +- the intermodulation order is 3 when both operating bands are between 450 MHz – 960 MHz or between 1427 MHz – 2690 MHz + +In the case for EN-DC configurations in NR FR1 for which the intermodulation products caused by dual uplink operation do not interfere with its own primary downlink channel bandwidth as defined in Annex M the UE is mandated to operate in dual and triple uplink mode. + +For EN-DC configurations in NR FR1 with uplink and downlink assigned to E-UTRA and NR FR1 bands given in Table 7.3B.2.0.3.5.1-1, Table 7.3B.2.0.3.5.1-1a, Table 7.3B.2.0.3.5.2-0 and Table 7.3B.2.0.3.5.2-1 the reference sensitivity is defined only for the specific uplink and downlink test points specified in Table 7.3B.2.0.3.5.1-1, Table 7.3B.2.0.3.5.1-1a, Table 7.3B.2.0.3.5.2-0 and Table 7.3B.2.0.3.5.2-1. For these test points the reference sensitivity levels specified in clause 7.3.1 in TS 36.101 [5] and 7.3.2 of TS 38.101-1 [2] for the corresponding channel bandwidths or in clause 7.3.1 of TS 36.101 [5] are relaxed by the amount of the parameter MSD given in Table 7.3B.2.0.3.5.1-1, Table 7.3B.2.0.3.5.1-1a, Table 7.3B.2.0.3.5.2-0 and Table 7.3B.2.0.3.5.2-1. + +The throughput on each of the CGs shall be $\geq 95\%$ of the maximum throughput of the respective reference measurement channels as specified in Annex A of TS 38.101-1 [2] and Annex A of TS 36.101 [5], with parameters specified in Table 7.3B.2.0.3.5.1-1, Table 7.3B.2.0.3.5.1-1a, Table 7.3B.2.0.3.5.2-0 and Table 7.3B.2.0.3.5.2-1 with dual UL transmissions overlapping in time unless otherwise stated. + +7.3B.2.0.3.5.1 MSD test points for intermodulation interference due to dual uplink operation for PC3 EN-DC in NR FR1 involving two bands + +**Table 7.3B.2.0.3.5.1-1: MSD test points for PCell due to dual uplink operation for PC3 EN-DC in NR FR1 (two bands)** + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | +|-------------------------------------------------------------------------|------------------|-------------------------|----------------|---------------------|-------------------------|-------------------|-------------------| +| EN-DC Configuration | EUTRA or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | +| DC_1_n3 | 1 | 1950 | 5 | 25 | 2140 | 23 | IMD3 | +| | n3 | 1760 | 5 | 25 | 1855 | N/A | N/A | +| DC_1A_n8A | 1 | 1965 | 5 | 25 | 2155 | 6.0 | IMD4 | +| | n8 | 887.5 | 5 | 25 | 932.5 | N/A | N/A | +| DC_1A_n77A
DC_1A_SUL_n77A-n84A | 1 | 1950 | 5 | 25 | 2140 | 29.8 | IMD2 3 | +| | n77, n78 | 4090 | 10 | 50 | 4090 | N/A | N/A | +| DC_1A_n77A
DC_1A-SUL_n77A-n84A
DC_1A_n78A,
DC_1A_SUL_n78A-n84A | 1 | 1950 | 5 | 25 | 2140 | 8.0 | IMD4 3 | +| | n77, n78 | 3710 | 10 | 50 | 3710 | N/A | N/A | +| DC_2A_n66A | 2 | 1855 | 5 | 25 | 1935 | 20 | IMD3 | +| | n66 | 1775 | 5 | 25 | 2175 | N/A | N/A | +| | 2 | 1883.3 | 5 | 25 | 1963.3 | N/A | N/A | +| | n66 | 1750 | 5 | 25 | 2150 | 4 | IMD5 | +| DC_2A_n77A
DC_2A_n77(2A)
DC_2A-2A_n77A
DC_2A-2A_n77(2A) | 2 | 1855 | 5 | 25 | 1935 | 26 | IMD2 | +| | n77 | 3790 | 10 | 50 | 3790 | N/A | N/A | +| | 2 | 1900 | 5 | 25 | 1980 | 8.0 | IMD4 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | +| | 2 | 1885 | 5 | 25 | 1965 | 5 | IMD5 | +| | n77 | 3810 | 10 | 50 | 3810 | N/A | N/A | +| DC_2A_n78A | 2 | 1855 | 5 | 25 | 1935 | 26 | IMD2 3 | +| | n78 | 3790 | 10 | 50 | 3790 | N/A | N/A | +| | 2 | 1885 | 5 | 25 | 1965 | 8.0 | IMD4 3 | +| | n78 | 3690 | 10 | 50 | 3690 | N/A | N/A | +| DC_3_n1 | 3 | 1760 | 5 | 25 | 1855 | N/A | N/A | +| | n1 | 1950 | 5 | 25 | 2140 | 23 | IMD3 | +| DC_3_n5 | 3 | 1771 | 10 | 50 | 1866 | 4 | IMD4 | +| | n5 | 838 | 5 | 25 | 883 | N/A | N/A | +| | 3 | 1721 | 10 | 50 | 1816 | N/A | N/A | +| | n5 | 838 | 5 | 25 | 883 | 24 | IMD2 3 | +| DC_3A_n7A | 3 | 1730 | 5 | 25 | 1825 | N/A | N/A | +| DC_3C_n7A | n7 | 2535 | 10 | 50 | 2655 | 10.2 5 | IMD4 | +| DC_3A_n8A | n8 | 900 | 5 | 25 | 945 | 8 | IMD4 3 | +| | 3 | 1755 | 10 | 50 | 1850 | N/A | N/A | +| | n8 | 897.5 | 5 | 25 | 942.5 | N/A | N/A | +| | 3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | IMD5 | +| DC_3A_n41A | 3 | 1740 | 5 | 25 | 1835 | 8.2 | IMD4 | +| DC_3C_n41A | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | IMD4 | +| DC_3A_SUL_n41A-n80A,
DC_3C_SUL_n41A-n80A | 3 | 1740 | 5 | 25 | 1835 | 8.2 | IMD4 | +| | n41 | 2657.5 | 10 | 52 | 2657.5 | N/A | N/A | +| DC_3A_n77A | 3 | 1740 | 5 | 25 | 1835 | 26 | IMD2 3 | + +| | | | | | | | | +|------------------------------------|----------|--------|----|----|--------|------|-------------------| +| DC_3A_SUL_n77A-n80A | | | | | | | | +| DC_3A_n78A | | | | | | | | +| DC_3A-SUL_n78A-n80A,
DC_3C_n78A | n77, n78 | 3575 | 10 | 50 | 3575 | N/A | N/A | +| DC_3A_n77A | 3 | 1765 | 5 | 25 | 1860 | 8.0 | IMD4 3 | +| DC_3A_SUL_n77A-n80A,
DC_3A_n78A | | | | | | | | +| DC_3A-SUL_n78A-n80A,
DC_3C_n78A | n77, n78 | 3435 | 10 | 50 | 3435 | N/A | N/A | +| DC_5A_n66A | 5 | 838 | 5 | 25 | 883 | 30 | IMD2 3 | +| | n66 | 1721 | 5 | 25 | 2121 | N/A | N/A | +| DC_5A_n78A | 5 | 844 | 5 | 25 | 889 | 8.3 | IMD4 | +| | n78 | 3421 | 10 | 50 | 3421 | N/A | N/A | +| DC_5A_n77A 8 | 5 | 844 | 5 | 25 | 889 | 8.3 | IMD4 | +| DC_5A_n77(2A) 8 | n77 | 3421 | 10 | 50 | 3421 | N/A | N/A | +| | 5 | 826.5 | 5 | 25 | 871.5 | 5.5 | IMD5 | +| | n77 | 4177.5 | 10 | 50 | 4177.5 | N/A | N/A | +| DC_7_n3 | 7 | 2535 | 10 | 50 | 2655 | 13 | IMD4 | +| | n3 | 1730 | 5 | 25 | 1825 | N/A | N/A | +| DC_7_n5 | 7 | 2547 | 10 | 50 | 2667 | N/A | N/A | +| | n5 | 834 | 5 | 25 | 879 | 12 | IMD3 3 | +| DC_7A_n66A | 7 | 2535 | 10 | 50 | 2655 | 15 | IMD4 | +| 4DC_7A-7A_n66A
DC_7C_n66A | n66 | 1730 | 5 | 25 | 2130 | N/A | N/A | +| DC_7A_n77A | 7 | 2540 | 5 | 25 | 2660 | 7.1 | IMD4 | +| | n77 | 3870 | 10 | 50 | 3870 | N/A | N/A | +| DC_8A_n1A | 8 | 887.5 | 5 | 25 | 932.5 | N/A | N/A | +| | n1 | 1965 | 5 | 25 | 2155 | 6 | IMD4 | +| DC_8A_n3A | 8 | 900 | 5 | 25 | 945 | 8 | IMD4 3 | +| | n3 | 1755 | 10 | 50 | 1850 | N/A | N/A | +| | 8 | 897.5 | 5 | 25 | 942.5 | N/A | N/A | +| | n3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | IMD5 | +| DC_8A_n20A | n20 | 849.5 | 5 | 25 | 808.5 | 25 | IMD3 3 | +| | 8 | 890.5 | 5 | 25 | 935.5 | N/A | N/A | +| | n20 | 847.5 | 5 | 25 | 806.5 | N/A | N/A | +| | 8 | 892.5 | 5 | 25 | 937.5 | 25 | IMD3 3 | +| DC_8A_n41A | 8 | 882.5 | 5 | 25 | 927.5 | 12.1 | IMD3 3 | +| | n41 | 2685 | 10 | 50 | 2685 | N/A | N/A | +| DC_8A_SUL_n41A-n81A | 8 | 882.5 | 5 | 25 | 927.5 | 12.1 | IMD3 3 | +| | n41 | 2685 | 10 | 52 | 2685 | N/A | N/A | +| DC_8A_n77A | 8 | 897.5 | 5 | 25 | 942.5 | 8.3 | IMD4 | +| DC_8A_n78A | | | | | | | | +| DC_8A-n79C,
DC_8A-SUL_n78A-n81A | n77, n78 | 3635 | 10 | 50 | 3635 | N/A | H4 | +| DC_12A_n77A | 12 | 702 | 5 | 20 | 732 | 5.5 | IMD5 | +| DC_12A_n77(2A) | n77 | 3540 | 10 | 50 | 3540 | N/A | N/A | +| DC_12_n78 | 12 | 710 | 5 | 25 | 740 | 5.5 | IMD5 | +| | n78 | 3580 | 10 | 50 | 3580 | N/A | N/A | +| DC_13A_n77A | 13 | 784.5 | 5 | 20 | 753.5 | 5.5 | IMD5 | +| | n77 | 3891.5 | 10 | 50 | 3891.5 | N/A | N/A | +| DC_14A_n77A | 14 | 795.5 | 5 | 15 | 765.5 | 5.5 | IMD5 | + +| | | | | | | | | +|------------------------------------------------------|-------------|--------|-----|-----|--------|------|-------------------| +| DC_14A_n77(2A) | n77 | 3947.5 | 10 | 50 | 3947.5 | N/A | N/A | +| DC_20A_n3A | 20 | 840 | 5 | 25 | 799 | N/A | N/A | +| | n3 | 1775 | 5 | 25 | 1870 | 4 | IMD4 | +| | 20 | 847 | 5 | 25 | 806 | 9 | IMD4 | +| | n3 | 1735 | 5 | 25 | 1830 | N/A | N/A | +| DC_8A_n79A | 8 | 897.5 | 5 | 25 | 942.5 | 4.8 | IMD5 | +| DC_8A-SUL_n79A-n81A | n79 | 4532.5 | 40 | 216 | 4532.5 | N/A | N/A | +| DC_18A_n77A
DC_18A_n78A | 18 | N/A | N/A | N/A | N/A | N/A | IMD4 | +| | n77,
n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_12A_n77A | 12 | 702 | 5 | 20 | 732 | 5.5 | IMD5 | +| | n77 | 3540 | 10 | 50 | 3540 | N/A | N/A | +| DC_19A_n78A | 19 | N/A | N/A | N/A | N/A | N/A | IMD4 | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_20_n7 | 20 | 851 | 5 | 25 | 810 | 12 | IMD3 3 | +| | n7 | 2512 | 10 | 50 | 2632 | N/A | N/A | +| DC_20A_n8A | 20 | 849.5 | 5 | 25 | 808.5 | 21 | IMD3 | +| | n8 | 892.5 | 5 | 25 | 937.5 | 21 | IMD3 | +| DC_20A_n77A
DC_20A_n78A,
DC_20A-SUL_n78A-n82A | 20 | 850 | 5 | 25 | 809 | 11 | IMD4 | +| | n77, n78 | 3359 | 10 | 50 | 3359 | N/A | N/A | +| DC_20A_n77A | 20 | 840 | 5 | 25 | 799 | 6.5 | IMD5 4 | +| | n77 | 4159 | 10 | 50 | 4159 | N/A | N/A | +| DC_21A_n28A 7 | 21 | 1450.4 | 5 | 25 | 1498.4 | 2.5 | IMD5 | +| | n28 | 735.5 | 5 | 25 | 790.5 | N/A | N/A | +| DC_21A_n79A | 21 | 1457.5 | 5 | 25 | 1505.5 | 18.4 | IMD3 | +| | n79 | 4420.5 | 40 | 216 | 4420.5 | N/A | N/A | +| DC_26A_n41A | 26 | 839 | 5 | 25 | 884 | 15.6 | IMD3 | +| | n41 | 2562 | 10 | 50 | 2562 | N/A | N/A | +| DC_28A_n51A | 28 | 742.3 | 5 | 25 | 797.3 | 5 | IMD 4 | +| | n51 | 1429.5 | 5 | 25 | 1429.5 | N/A | N/A | +| DC_25A_n77A
DC_25A-25A_n77A | 25 | 1855 | 5 | 25 | 1935 | 26 | IMD2 | +| | n77 | 3790 | 10 | 50 | 3790 | N/A | N/A | +| | 25 | 1900 | 5 | 25 | 1980 | 8 | IMD4 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | +| | 25 | 1885 | 5 | 25 | 1965 | 5 | IMD5 | +| | n77 | 3810 | 10 | 50 | 3810 | N/A | N/A | +| DC_26A_n77A,
DC_26A_n78A | 26 | 836.5 | 5 | 25 | 881.5 | 11.1 | IMD4 | +| | n77, n78 | 3391 | 10 | 50 | 3391 | N/A | N/A | +| DC_28A_n77A,
DC_28A_n78A,
DC_28A-SUL_n78A-n83A | 28 | 705.5 | 5 | 25 | 760.5 | 5.5 | IMD5 | +| | n77, n78 | 3582.5 | 10 | 50 | 3582.5 | N/A | N/A | +| DC_30A_n77A
DC_30A_n77(2A) | 30 | 705.5 | 5 | 25 | 760.5 | 5.5 | IMD5 | +| | n77 | 3582.5 | 10 | 50 | 3582.5 | N/A | N/A | +| DC_48A_n66A | 48 | 3630 | 20 | 100 | 3630 | N/A | N/A | +| | n66 | 1715 | 5 | 25 | 2115 | 4 | IMD5 | +| DC_66A_n2A | 66 | 1775 | 5 | 25 | 2175 | N/A | N/A | +| | n2 | 1855 | 5 | 25 | 1935 | 20 | IMD3 | +| | 66 | 1750 | 5 | 25 | 2150 | 4 | IMD5 | +| | n2 | 1883.3 | 5 | 25 | 1963.3 | N/A | N/A | +| DC_66A_n5A | n5 | 838 | 5 | 25 | 883 | 30 | IMD2 3 | +| | 66 | 1721 | 5 | 25 | 2121 | N/A | N/A | +| | 66 | 1775 | 5 | 25 | 2175 | N/A | N/A | +| | n25 | 1855 | 5 | 25 | 1935 | 20 | IMD3 | + +| | | | | | | | | +|-----------------------------------------------------------------------------------------------|-----|--------|----|----|--------|------|------| +| DC_66A_n25A | 66 | 1712.5 | 5 | 25 | 2112.5 | 23 | IMD3 | +| | n25 | 1912.5 | 5 | 25 | 1992.5 | N/A | N/A | +| | 66 | 1750 | 5 | 25 | 2150 | 4 | IMD5 | +| | n25 | 1883.3 | 5 | 25 | 1963.3 | N/A | N/A | +| DC_66A_n71A | 66 | 1750 | 5 | 25 | 2150 | 5 | IMD4 | +| | n71 | 675 | 5 | 25 | 629 | N/A | N/A | +| DC_66A_n77A
DC_66A_n77(2A)
DC_66A-66A_n77A
DC_66A-66A_n77(2A)
DC_66A-66A-66A_n77A | 66 | 1775 | 5 | 25 | 2175 | 31.0 | IMD2 | +| | n77 | 3950 | 10 | 50 | 3950 | N/A | N/A | +| | 66 | 1760 | 5 | 25 | 2160 | 5.0 | IMD5 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | +| DC_66A_n78A | 66 | 1730 | 5 | 25 | 2130 | 5.0 | IMD5 | +| | n78 | 3660 | 5 | 50 | 3660 | N/A | N/A | +| DC_71A_n66A | 71 | 675 | 5 | 25 | 629 | N/A | N/A | +| | n66 | 1750 | 5 | 25 | 2150 | 5 | IMD4 | + +NOTE 1: E-UTRA carrier shall be set to $\min(+20 \text{ dBm}, P_{\text{CMAX\_L\_E-UTRA,c}})$ and NR carrier shall be set to $\min(+20 \text{ dBm}, P_{\text{CMAX\_L\_f,c,NR}})$ as defined in clause 6.2B.4.1.3. + +NOTE 2: $\text{RB}_{\text{START}} = 0$ + +NOTE 3: This band is subject to IMD5 also which MSD is not specified. + +NOTE 4: Void + +NOTE 5: Void. + +NOTE 6: For NR band, UL/DL BW and UL $L_{\text{CRB}}$ can be adjusted according to the supported BW and lowest SCS supported by the UE. + +NOTE 7: The frequency range in band n28 is restricted for this band combination to 728 - 738 MHz for the UL and 783 - 793 MHz for the DL. This band is subject to IMD2, IMD4 and IMD5 fall in n28 also which MSD is not specified. In addition, this band is subject to IMD4 fall in B21 also which MSD is not specified. + +NOTE 8: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +**Table 7.3B.2.0.3.5.1-1a: MSD test points for PCell due to dual uplink operation for PC2 EN-DC in NR FR1 (two bands)** + +| NR or E-UTRA Band / Channel bandwidth / $N_{\text{RB}}$ / MSD | | | | | | | | +|---------------------------------------------------------------|------------------|----------------|----------------|---------------------|----------------|----------|-------------------| +| EN-DC Configuration | EUTRA or NR band | UL $F_c$ (MHz) | UL/DL BW (MHz) | UL $L_{\text{CRB}}$ | DL $F_c$ (MHz) | MSD (dB) | IMD order | +| DC_1A_n78A | 1 | 1950 | 5 | 25 | 2140 | 17.8 | IMD4 | +| | n78 | 3710 | 10 | 50 | 3710 | N/A | N/A | +| DC_3A_n41A | 3 | 1740 | 5 | 25 | 1835 | 18.4 | IMD4 | +| | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | N/A | +| DC_3A_n78A | 3 | 1740 | 5 | 25 | 1835 | 31.9 | IMD2 | +| | n78 | 3575 | 10 | 50 | 3575 | N/A | N/A | +| | 3 | 1765 | 5 | 25 | 1860 | 18.5 | IMD4 | +| | n78 | 3435 | 10 | 50 | 3435 | N/A | N/A | +| DC_2A_n77A
DC_2A-2A_n77A
DC_2A_n77C
DC_2A-2A_n77C | 2 | 1855 | 5 | 25 | 1935 | 32.10 | IMD2 | +| | n77 | 3790 | 10 | 50 | 3790 | N/A | N/A | +| | 2 | 1900 | 5 | 25 | 1980 | 19.10 | IMD4 1 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | +|----------------------------------------------------------------------------------------------------------------|------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------| +| EN-DC Configuration | EUTRA or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | +| DC_5A_n77A 3
DC_5A_n77C 3 | 5 | 844 | 5 | 25 | 889 | 18.60 | IMD4 1 | +| | n77 | 3421 | 10 | 50 | 3421 | N/A | N/A | +| DC_12A_n77A | 12 | 702 | 5 | 20 | 732 | 11.7 | IMD5 | +| | n77 | 3540 | 10 | 50 | 3540 | N/A | N/A | +| DC_13A_n77A
DC_13A_n77C | 13 | 782 | 5 | 20 | 751 | 15.37 | IMD5 | +| | n77 | 3879 | 10 | 50 | 3879 | N/A | N/A | +| DC_14A_n77A | 14 | 795.5 | 5 | 15 | 765.5 | 11.7 | IMD5 | +| | n77 | 3947.5 | 10 | 50 | 3947.5 | N/A | N/A | +| DC_21A_n79A | 21 | 1457.5 | 5 | 25 | 1505.5 | 33.4 | IMD3 | +| | n79 | 4420.5 | 10 | 50 | 4420.5 | N/A | N/A | +| DC_30A_n77A | 30 | 2310 | 5 | 25 | 2355 | 17.6 | IMD4 | +| | n77 | 3487.5 | 10 | 50 | 3487.5 | N/A | N/A | +| DC_66A_n77A
DC_66A-66A_n77A
DC_66A-66A-66A_n77A
DC_66A_n77C
DC_66A-66A_n77C
DC_66A-66A-66A_n77C | 66 | 1775 | 5 | 25 | 2175 | 34.33 | IMD2 | +| | n77 | 3950 | 10 | 50 | 3950 | N/A | N/A | +| | 66 | 1760 | 5 | 25 | 2160 | 11.27 | IMD5 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | + +NOTE 1: This band is subject to IMD5 also which MSD is not specified. +NOTE 2: Void. +NOTE 3: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. +NOTE 4: E-UTRA carrier shall be set to min(+23 dBm, PCMAX\_L\_E-UTRA,c) and NR carrier shall be set to min(+23 dBm, PCMAX\_L,f,c,NR) as defined in clause 6.2B.4.1.3. + +7.3B.2.0.3.5.2 MSD test points for intermodulation interference due to dual uplink operation for EN-DC in NR FR1 involving three bands + +**Table 7.3B.2.0.3.5.2-0: MSD test points for PCell due to dual uplink operation for EN-DC in NR FR1 (three bands)** + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | | +|---------------------------------------------------------------|---------------|-------------------------|----------------|--------------------------------|-------------------------|----------|--|-----------| +| EN-DC Configuration | EUTRA/NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | | IMD order | +| DC_66A_(n)71AA | 66 | 1750 | 5 | 25 | 2150 | 5 | | IMD4 | +| | n71 | 678 | 10 | 10
(RB start =0) | 632 | N/A | | N/A | + +NOTE 1: For NR band, UL/DL BW and UL LCRB can be adjusted according to the supported BW and lowest SCS supported by the UE. +NOTE 2: E-UTRA carrier shall be set to min(+20 dBm, PCMAX\_L\_E-UTRA,c) and NR carrier shall be set to min(+20 dBm, PCMAX\_L,f,c,NR) as defined in clause 6.2B.4.1.3. + +Editor's Note: + +- In 38.101-3 (V18.3.0) Table 7.3B.2.3.5.2-1 (MSD test points for Scell due to dual uplink operation for EN-DC in NR FR1 (three bands)), ENDC band combination DC\_2A-13A\_n77A, and DC\_2A-66A\_n77A have UL/DL bandwidth 5 MHz for n77, while there is no bandwidth definition of 5MHz for n77 in 38.101-1 (V18.3.0) Table 5.3.5-1 (Channel bandwidths for each NR band). Therefore in following Table 7.3B.2.0.3.5.2-1 corresponding cases, n77 UL/DL bandwidth of 10 MHz and UL $C_{LRB}$ of 50 are used instead. + +**Table 7.3B.2.0.3.5.2-1: MSD test points for Scell due to dual uplink operation for EN-DC in NR FR1 (three bands)** + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-----------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| DC_1A-3A_n28A | 1 | 1975 | 5 | 25 | 2165 | N/A | N/A | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| | 3 | 1723.5 | 5 | 25 | 1818.5 | 4.0 | IMD5 | +| | 3 | 1780 | 5 | 25 | 1875 | N/A | N/A | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| | 1 | 1949 | 5 | 25 | 2139 | 11.0 | IMD4 | +| DC_1A-7A_n28A | 1 | 1935 | 5 | 25 | 2125 | N/A | N/A | +| | n28 | 718 | 5 | 25 | 773 | N/A | N/A | +| | 7 | 2533 | 10 | 50 | 2653 | 30.0 | IMD2 | +| DC_1A-3A_n77A | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 3 | 1712.5 | 5 | 25 | 1807.5 | 31.5 | IMD2 | +| | n77 | 3757.5 | 10 | 50 | 3757.5 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 3 | 1775 | 5 | 25 | 1870 | 8.5 | IMD4 | +| | n77 | 3980 | 10 | 50 | 3980 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | 31.0 | IMD2 | +| | 3 | 1775 | 5 | 25 | 1870 | N/A | N/A | +| | n77 | 3915 | 10 | 50 | 3915 | N/A | N/A | +| DC_1A-3A_n78A
DC_1A-3C_n78A | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 3 | 1712.5 | 5 | 25 | 1807.5 | 31.2 | IMD2 | +| | n78 | 3757.5 | 10 | 50 | 3757.5 | N/A | N/A | +| | 1 | 1935 | 5 | 25 | 2125 | 2.8 | IMD5 | +| | 3 | 1775 | 5 | 25 | 1870 | N/A | N/A | +| | n78 | 3725 | 10 | 50 | 3725 | N/A | N/A | +| DC_1A-5A_n78A | 1 | 1932 | 5 | 25 | 2122 | 18.1 | IMD3 | +| | 5 | 829 | 5 | 25 | 874 | N/A | N/A | +| | n78 | 3780 | 10 | 50 | 3780 | N/A | N/A | +| | 1 | 1975 | 5 | 25 | 2165 | N/A | N/A | +| | 5 | 840 | 5 | 25 | 885 | 3.1 | IMD5 | +| | n78 | 3405 | 10 | 50 | 3405 | N/A | N/A | +| DC_1A-7A_n78A | 1 | 1977.5 | 5 | 25 | 2167.5 | N/A | N/A | +| | 7 | 2507.5 | 5 | 25 | 2627.5 | 9.1 | IMD4 | +| | n78 | 3305 | 10 | 50 | 3305 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | 8.7 | IMD4 | +| | 7 | 2510 | 10 | 50 | 2630 | N/A | N/A | +| | n78 | 3580 | 10 | 50 | 3580 | N/A | N/A | +| DC_1A_n7A-n78A | 1 | 1977.5 | 5 | 25 | 2167.5 | N/A | N/A | +| | n7 | 2507.5 | 5 | 25 | 2627.5 | 9.1 | IMD4 | +| | n78 | 3305 | 10 | 50 | 3305 | N/A | N/A | +| | 1 | 1970 | 5 | 25 | 2160 | N/A | N/A | +| | n7 | 2520 | 5 | 25 | 2640 | N/A | N/A | +| | n78 | 3390 | 10 | 50 | 3390 | 10.1 | IMD4 | +| DC_1A-3A_n79A | 1 | 1950 | 5 | 25 | 2140 | 3.6 | IMD5 | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-----------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | 3 | 1750 | 5 | 25 | 1845 | N/A | N/A | +| | n79 | 4860 | 40 | 216 | 4860 | N/A | N/A | +| DC_1A-8A_n78A | 1 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 8 | N/A | N/A | N/A | N/A | N/A | IMD5 | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 1 | 1945 | 5 | 25 | 2135 | N/A | N/A | +| | 8 | 900 | 5 | 25 | 945 | N/A | N/A | +| | n78 | 3745 | 10 | 52 | 3745 | 14.9 | IMD3 | +| | 1 | 1940 | 5 | 25 | 2130 | N/A | N/A | +| | 8 | 895 | 5 | 25 | 940 | 3.3 | IMD5 | +| | n78 | 3380 | 10 | 52 | 3330 | N/A | N/A | +| DC_1A-18A_n77A | 1 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 18 | N/A | N/A | N/A | N/A | N/A | IMD5 | +| | n77 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 1 | 1930 | 5 | 25 | 2120 | 16.4 | IMD3 | +| | 18 | 825 | 5 | 25 | 870 | N/A | N/A | +| | n77 | 3770 | 10 | 50 | 3770 | N/A | N/A | +| DC_1A-18A_n78A | 1 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 18 | N/A | N/A | N/A | N/A | N/A | IMD5 | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 1 | 1930 | 5 | 25 | 2120 | 16.4 | IMD3 | +| | 18 | 819 | 5 | 25 | 864 | N/A | N/A | +| | n78 | 3758 | 10 | 50 | 3758 | N/A | N/A | +| DC_1A-18A_n79A | 1 | 1935 | 5 | 25 | 2125 | N/A | N/A | +| | 18 | 822.5 | 5 | 25 | 867.5 | 18.3 | IMD3 | +| | n79 | 4737.5 | 40 | 216 | 4737.5 | N/A | N/A | +| | 1 | 1930 | 5 | 25 | 2120 | N/A | N/A | +| | 18 | 820 | 5 | 25 | 865 | 8.9 | IMD4 | +| | n79 | 4925 | 40 | 216 | 4925 | N/A | N/A | +| | 1 | 1935 | 5 | 25 | 2125 | 8.1 | IMD4 | +| | 18 | 822.5 | 5 | 25 | 867.5 | N/A | N/A | +| | n79 | 4592.5 | 40 | 216 | 4592.5 | N/A | N/A | +| DC_1A-19A_n77A
DC_1A-19A_n78A | 1 | 1940 | 5 | 25 | 2130 | 17.8 | IMD3 | +| | 19 | 832.5 | 5 | 25 | 877.5 | N/A | N/A | +| | n77, n78 | 3795 | 10 | 50 | 3795 | N/A | N/A | +| | 1 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 19 | N/A | N/A | N/A | N/A | N/A | IMD5 | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_1A-19A_n79A | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 19 | 837.5 | 5 | 25 | 882.5 | 18.3 | IMD3 | +| | n79 | 4782.5 | 40 | 216 | 4782.5 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | 8.1 | IMD4 | +| | 19 | 837.5 | 5 | 25 | 882.5 | N/A | N/A | +| | n79 | 4652.5 | 40 | 216 | 4652.5 | N/A | N/A | +| DC_1A-20A_n8A | 1 | 1925 | 5 | 25 | 2115 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-----------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | n8 | 910 | 5 | 25 | 955 | N/A | N/A | +| | 20 | 846 | 5 | 25 | 805 | 11.5 | IMD4 | +| DC_1A-20A_n78A | 1 | 1930 | 5 | 25 | 2120 | 20.3 | IMD3 | +| | 20 | 835 | 5 | 25 | 794 | N/A | N/A | +| | n78 | 3790 | 10 | 50 | 3790 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 20 | 851 | 5 | 25 | 810 | 3.0 | IMD5 | +| | n78 | 3330 | 10 | 50 | 3330 | N/A | N/A | +| DC_1A-21A_n77A
DC_1A-21A_n78A | 1 | 1964.6 | 5 | 25 | 2154.6 | 30.6 | IMD2 | +| | 21 | 1450.4 | 5 | 25 | 1498.4 | N/A | N/A | +| | n77, n78 | 3605 | 10 | 50 | 3605 | N/A | N/A | +| | 1 | N/A | 5 | N/A | 2154.6 | 3.6 | IMD5 | +| | 21 | 1450.4 | 5 | 25 | 1498.4 | N/A | N/A | +| | n78 | 3647 | 10 | 50 | 3647 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 21 | N/A | 5 | N/A | 1500 | 31.5 | IMD2 | +| | n78 | 3450 | 10 | 50 | 3450 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 21 | 1452 | 5 | 25 | 1500 | 2.9 | IMD5 | +| DC_1A-21A_n79A | n77, n78 | 3675 | 10 | 50 | 3675 | N/A | N/A | +| | 1 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 21 | N/A | N/A | N/A | N/A | N/A | IMD4 | +| DC_1A-28A_n3A | n79 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| | n3 | 1780 | 5 | 25 | 1875 | N/A | N/A | +| DC_1A-28A_n78A | 1 | 1949 | 5 | 25 | 2139 | 11.0 | IMD4 | +| | 1 | 1960 | 5 | 25 | 2150 | 15.7 | IMD3 | +| | 28 | 740 | 5 | 25 | 795 | N/A | N/A | +| | n78 | 3630 | 10 | 50 | 3630 | N/A | N/A | +| | 1 | 1970 | 5 | 25 | 2160 | N/A | N/A | +| | 28 | 739 | 5 | 25 | 794 | 4.2 | IMD5 | +| DC_1A_n28A-n78A | n78 | 3352 | 10 | 50 | 3352 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | n28 | 733 | 5 | 25 | 788 | N/A | N/A | +| | n78 | 3416 | 10 | 50 | 3416 | 15.7 | IMD3 | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | n78 | 3320 | 10 | 50 | 3320 | N/A | N/A | +| DC_1A-28A_n79A | n28 | 735 | 5 | 25 | 790 | 3.3 | IMD5 | +| | 1 | 1930 | 5 | 25 | 2120 | N/A | N/A | +| | 28 | 733 | 5 | 25 | 788 | 15.2 | IMD3 | +| | n79 | 4648 | 40 | 216 | 4648 | N/A | N/A | +| | 1 | 1925 | 5 | 25 | 2115 | N/A | N/A | +| | 28 | 740 | 5 | 25 | 795 | 10.0 | IMD4 | +| | n79 | 4980 | 40 | 216 | 4980 | N/A | N/A | +| | 1 | 1977.5 | 5 | 25 | 2167.5 | 1.2 | IMD4 | +| | 28 | 745.5 | 5 | 25 | 800.5 | N/A | N/A | +| | n79 | 4420 | 40 | 216 | 4420 | N/A | N/A | +| | 1 | 1935 | 5 | 25 | 2125 | 4.5 | IMD5 | +| DC_1A-41A_n28A | 28 | 718 | 5 | 25 | 773 | N/A | N/A | +| | n79 | 4807 | 40 | 216 | 4807 | N/A | N/A | +| DC_1A-41A_n28A | 1 | 1935 | 5 | 25 | 2125 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-----------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | n28 | 718 | 5 | 25 | 773 | N/A | N/A | +| | 41 | 2653 | 10 | 50 | 2653 | 30 | IMD2 | +| DC_1A-41A_n77A | 1 | 1970 | 5 | 25 | 2160 | N/A | N/A | +| | n77 | 3400 | 10 | 50 | 3400 | N/A | | +| | 41 | 2510 | 5 | 25 | 2510 | 11.0 | IMD4 | +| | 1 | 1950 | 5 | 25 | 2140 | 9.3 | IMD4 | +| | n77 | 3710 | 10 | 50 | 3710 | N/A | N/A | +| | 41 | 2640 | 5 | 25 | 2640 | N/A | N/A | +| | 1 | 1930 | 5 | 25 | 2120 | N/A | N/A | +| | n77 | 4150 | 10 | 50 | 4150 | N/A | | +| | 41 | 2510 | 5 | 25 | 2510 | 3.6 | IMD5 | +| DC_1A-41A_n78A | 1 | 1950 | 5 | 25 | 2140 | 9.3 | IMD4 | +| | 41 | 2640 | 5 | 25 | 2640 | N/A | N/A | +| | n78 | 3710 | 10 | 50 | 3710 | N/A | N/A | +| | 1 | 1975 | 5 | 25 | 2165 | N/A | N/A | +| | 41 | 2515 | 5 | 25 | 2515 | 12 | IMD4 | +| | n78 | 3410 | 10 | 50 | 3410 | N/A | N/A | +| | 1 | 1955 | 5 | 25 | 2145 | 8.7 | IMD4 | +| | 41 | 2507.5 | 10 | 50 | 2507.5 | N/A | N/A | +| | n78 | 3580 | 10 | 50 | 3580 | N/A | N/A | +| DC_1A-42A_n79A | 1 | 1977.5 | 5 | 25 | 2167.5 | N/A | N/A | +| | n79 | 4420 | 40 | 216 | 4420 | N/A | N/A | +| | 42 | 3490 | 5 | 25 | 3490 | 4.8 | IMD5 | +| | 42 | 3402.5 | 5 | 25 | 3402.5 | N/A | N/A | +| | n79 | 4640 | 40 | 216 | 4640 | N/A | N/A | +| | 1 | 1975 | 5 | 25 | 2165 | 15.5 | IMD3 | +| | 42 | 3450 | 5 | 25 | 3450 | N/A | N/A | +| | n79 | 4520 | 40 | 216 | 4520 | N/A | N/A | +| | 1 | 1950 | 5 | 25 | 2140 | 9.3 | IMD4 | +| DC_1A_n78A-n79A | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | n78 | 3410 | 10 | 50 | 3410 | N/A | N/A | +| | n79 | 4870 | 40 | 216 | 4870 | 15.9 | IMD3 | +| | 1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | n79 | 4670 | 40 | 216 | 4670 | N/A | N/A | +| | n78 | 3490 | 10 | 50 | 3490 | 4.6 | IMD5 | +| DC_2A_n5A-n77A | 2 | 1880 | 5 | 25 | 1960 | N/A | N/A | +| | n5 | 830 | 5 | 25 | 875 | N/A | N/A | +| | n77 | N/A | 10 | N/A | 3540 | 16.0 | IMD3 | +| DC_2A-12A_n66A | 2 | N/A | N/A | N/A | N/A | N/A | IMD4 | +| | 12 | N/A | N/A | N/A | N/A | N/A | N/A | +| | n66 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_2A-13A_n77A | 2 | N/A | 5 | N/A | 1944 | 16.0 | IMD3 | +| | 13 | 783 | 5 | 25 | 752 | N/A | N/A | +| | n77 | 3510 | 10 | 50 | 3510 | N/A | N/A | +| DC_2A-14A_n66A | 2 | 1874 | 5 | 25 | 1954 | 7.2 | IMD4 | +| | 14 | 793 | 5 | 25 | 763 | N/A | N/A | +| | 66 | 1770 | 5 | 25 | 2170 | N/A | N/A | +| DC_2A-66A_n5A | 2 | 1900 | 5 | 25 | 1980 | N/A | N/A | +| | 66 | 1740 | 5 | 25 | 2140 | 7.2 | IMD4 | +| | n5 | 830 | 5 | 25 | 875 | N/A | N/A | +| DC_2A-66A_n41A | 2 | 1860 | 5 | 25 | 1940 | 22.6 | IMD4 | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-------------------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | 66 | 1715 | 5 | 25 | 2115 | N/A | N/A | +| | n41 | 2685 | 5 | 25 | 2685 | N/A | N/A | +| DC_2A-66A_n77A | 2 | 1855 | 5 | 25 | 1935 | N/A | N/A | +| | 66 | N/A | 5 | N/A | 2115 | 29.2 | IMD2 | +| | n77 | 3970 | 10 | 50 | 3970 | N/A | N/A | +| | 2 | 1880 | 5 | 25 | 1960 | M/A | N/A | +| | 66 | N/A | 5 | N/A | 2140 | 10.4 | IMD4 | +| | n77 | 3500 | 10 | 50 | 3500 | N/A | N/A | +| | 2 | 1885 | 5 | 25 | 1965 | M/A | N/A | +| | 66 | N/A | 5 | N/A | 2175 | 4.0 | IMD5 | +| | n77 | 3915 | 10 | 50 | 3915 | N/A | N/A | +| | 2 | N/A | 5 | N/A | 1960 | 32.1 | IMD2 | +| | 66 | 1760 | 5 | 25 | 2160 | N/A | N/A | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | +| DC_3A-5A_n78A | 3 | N/A | N/A | N/A | N/A | N/A | IMD3 | +| | 5 | N/A | N/A | N/A | N/A | N/A | N/A | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_3A-7A_n5A | 3 | 1780 | 10 | 50 | 1875 | N/A | N/A | +| | 7 | 2505 | 10 | 50 | 2625 | 30.0 | IMD2 x | +| | n5 | 845 | 5 | 25 | 890 | N/A | N/A | +| DC_3A-7A_n28A
DC_3C-7A_n28A | 3 | 1712.5 | 5 | 25 | 1807.5 | N/A | N/A | +| | n28 | 743 | 5 | 25 | 798 | N/A | N/A | +| | 7 | 2562 | 10 | 50 | 2682 | 16.9 | IMD3 | +| | 7 | 2543 | 10 | 50 | 2663 | N/A | N/A | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| | 3 | 1737.5 | 5 | 25 | 1832.5 | 26.0 | IMD2 | +| DC_3A-7A_n78A
DC_3C-7A_n78A | 3 | 1725 | 5 | 25 | 1820 | 17.6 | IMD3 | +| | 7 | 2565 | 5 | 25 | 2685 | N/A | N/A | +| | n78 | 3310 | 10 | 50 | 3310 | N/A | N/A | +| | 3 | 1725 | 5 | 25 | 1820 | 8.6 | IMD4 | +| | 7 | 2565 | 5 | 25 | 2685 | N/A | N/A | +| | n78 | 3475 | 10 | 50 | 3475 | N/A | N/A | +| DC_3A-8A_n78A | 8 | 910 | 5 | 25 | 955 | N/A | N/A | +| | n78 | 3640 | 10 | 50 | 3640 | N/A | N/A | +| | 3 | 1725 | 5 | 25 | 1820 | 16.5 | IMD3 | +| | | | | | | | | +| | | | | | | | | +| | | | | | | | | +| DC_3A-18A_n77A
DC_3A-18A_n78A | 3 | N/A | N/A | N/A | N/A | N/A | IMD3 | +| | 18 | N/A | N/A | N/A | N/A | N/A | N/A | +| | n77, n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_3A-19A_n78A | 3 | N/A | N/A | N/A | N/A | N/A | IMD3 | +| | 19 | N/A | N/A | N/A | N/A | N/A | N/A | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_3A-19A_n79A | 3 | 1775 | 5 | 25 | 1870 | N/A | N/A | +| | 19 | 840 | 5 | 25 | 885 | [18.5] | IMD3 | +| | n79 | 4435 | 40 | 216 | 4435 | N/A | N/A | +| | 3 | 1782.5 | 5 | 25 | 1877.5 | 0.2 | IMD4 | +| | 19 | 842.5 | 5 | 25 | 887.5 | N/A | N/A | +| | n79 | 4420 | 40 | 216 | 4420 | N/A | N/A | +| DC_3A-20A_n28A | 20 | 852 | 5 | 25 | 811 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-----------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| DC_3C-20A_n28A | n28 | 728 | 5 | 25 | 783 | N/A | N/A | +| | 3 | 1733 | 5 | 25 | 1828 | 9.4 | IMD4 | +| DC_3A_n20A-n78A | 3 | 1730 | 5 | 25 | 1825 | N/A | N/A | +| | n20 | 845 | 5 | 25 | 804 | N/A | N/A | +| | n78 | 3420 | 10 | 50 | 3420 | 16.1 | IMD3 | +| DC_3A-20A_n78A | 3 | 1725 | 5 | 25 | 1820 | 17.3 | IMD3 | +| | 20 | 845 | 5 | 25 | 804 | N/A | N/A | +| | n78 | 3510 | 10 | 50 | 3510 | N/A | N/A | +| DC_3A-21A_n77A
DC_3A-21A_n78A | 3 | 1767.5 | 5 | 25 | 1862.5 | N/A | N/A | +| | 21 | 1459.5 | 5 | 25 | 1507.5 | 8.8 | IMD4 | +| | n77, n78 | 3795 | 10 | 50 | 3795 | N/A | N/A | +| | 3 | N/A | 5 | N/A | 1862.5 | 30.8 | IMD2 | +| | 21 | 1459.5 | 5 | 25 | 1507.5 | N/A | N/A | +| | n78 | 3322 | 10 | 50 | 3322 | N/A | N/A | +| DC_3A-21A_n77A | 3 | 1771.6 | 5 | 25 | 1866.6 | 3.4 | IMD5 | +| | 21 | 1450.4 | 5 | 25 | 1498.4 | N/A | N/A | +| | n77 | 3935 | 10 | 50 | 3935 | N/A | N/A | +| DC_3A-21A_n79A | 3 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 21 | N/A | N/A | N/A | N/A | N/A | IMD3 | +| | n79 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 3 | 1774.2 | 5 | 25 | 1869.2 | 17.8 | IMD3 | +| | 21 | 1450.4 | 5 | 25 | 1498.4 | N/A | N/A | +| | n79 | 4770 | 40 | 216 | 4770 | N/A | N/A | +| DC_3A-28A_n77A | 3 | 1712.5 | 5 | 25 | 1807.5 | N/A | N/A | +| | 28 | 715 | 5 | 25 | 770 | 15.3 | IMD3 | +| | n77 | 4195 | 10 | 50 | 4195 | N/A | N/A | +| | 3 | 1755 | 5 | 25 | 1850 | 17.0 | IMD3 | +| | 28 | 735 | 5 | 25 | 790 | N/A | N/A | +| | n77 | 3320 | 10 | 50 | 3320 | N/A | N/A | +| DC_3A-28A_n78A | 3 | 1775 | 5 | 25 | 1870 | 17.3 | IMD3 | +| | 28 | 740 | 5 | 25 | 760 | N/A | N/A | +| | n78 | 3350 | 10 | 25 | 3350 | N/A | N/A | +| DC_3A-28A_n79A | 3 | 1770 | 5 | 25 | 1865 | N/A | N/A | +| | 28 | 725 | 5 | 25 | 780 | 10.3 | IMD4 | +| | n79 | 4530 | 40 | 216 | 4530 | N/A | N/A | +| | 3 | 1775 | 5 | 25 | 1870 | 5.7 | IMD5 | +| | 28 | 725 | 5 | 25 | 780 | N/A | N/A | +| | n79 | 4770 | 40 | 216 | 4770 | N/A | N/A | +| DC_3A_n28A-n78A | 3 | 1750 | 5 | 25 | 1845 | N/A | N/A | +| | n28 | 743 | 5 | 25 | 798 | N/A | N/A | +| | n78 | 3764 | 10 | 50 | 3764 | 4.5 | IMD5 | +| DC_3A-40A_n1A | n1 | 1950 | 5 | 25 | 2140 | N/A | N/A | +| | 3 | 1735 | 5 | 25 | 1830 | N/A | N/A | +| | 40 | 2380 | 5 | 25 | 2380 | 8.0 | IMD5 | +| DC_3A-41A_n28A | 41 | 2543 | 10 | 50 | 2543 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|-------------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|------------------------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| DC_3A-41C_n28A | n28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| | 3 | 1737.5 | 5 | 25 | 1832.5 | 26 | IMD2 | +| | 3 | 1780 | 5 | 25 | 1875 | N/A | N/A | +| | n28 | 738 | 5 | 25 | 793 | N/A | N/A | +| | 41 | 2518 | 5 | 25 | 2518 | 27.4 | IMD2 | +| | 3 | 1715 | 5 | 25 | 1810 | N/A | N/A | +| | n28 | 743 | 5 | 25 | 798 | N/A | N/A | +| | 41 | 2687 | 5 | 25 | 2687 | 15.9 | IMD3 | +| DC_3A-41A_n77A
DC_3A-41C_n77A
DC_3A-41A_n77(2A) | 3 | 1720 | 5 | 25 | 1815 | N/A | N/A | +| | n77 | 3900 | 10 | 50 | 3900 | N/A | N/A | +| | 41 | 2640 | 5 | 25 | 2640 | 5.3 | IMD5 | +| | 41 | 2620 | 5 | 25 | 2620 | N/A | N/A | +| | n77 | 3400 | 10 | 50 | 3400 | N/A | N/A | +| | 3 | 1745 | 5 | 25 | 1840 | 16.4 | IMD3 | +| DC_3A-41A_n78A | 41 | 2620 | 5 | 25 | 2620 | N/A | N/A | +| | n78 | 3400 | 10 | 50 | 3400 | N/A | N/A | +| | 3 | 1745 | 5 | 25 | 1840 | 16.4 | IMD3 | +| DC_3A_n78A-n79A | 3 | 1770 | 5 | 25 | 1865 | N/A | N/A | +| | n78 | 3340 | 10 | 50 | 3340 | N/A | N/A | +| | n79 | 4910 | 40 | 216 | 4910 | 16.3 | IMD3 | +| | 3 | 1770 | 5 | 25 | 1865 | N/A | N/A | +| | n79 | 4510 | 40 | 216 | 4510 | N/A | N/A | +| | n78 | 3710 | 10 | 50 | 3710 | 4.2 | IMD5 | +| DC_3A-SUL_n78A-n82A | 3 | 1775 | 5 | 25 | 1870 | 4 | IMD4 | +| | n82 | 840 | 5 | 25 | | N/A | N/A | +| DC_3A-21A_n79A | 3 | 1774.2 | 5 | 25 | 1869.2 | 17.8 | IMD3 | +| | 21 | 1450.4 | 5 | 25 | 1498.4 | N/A | N/A | +| | n79 | 4770 | 40 | 216 | 4770 | N/A | N/A | +| DC_5A-7A_n78A | 5 | 844 | 5 | 25 | 889 | N/A | N/A | +| | 7 | 2525 | 5 | 25 | 2645 | 30.1 | IMD2 | +| | n78 | 3489 | 10 | 50 | 3489 | N/A | N/A | +| | 5 | 834 | 5 | 25 | 879 | 30.2 | IMD2 | +| | 7 | 2550 | 5 | 25 | 2670 | N/A | N/A | +| | n78 | 3429 | 10 | 50 | 3429 | N/A | N/A | +| | 5 | 830 | 5 | 25 | 875 | 3.3 | IMD5 | +| | 7 | 2525 | 5 | 25 | 2645 | N/A | N/A | +| | n78 | 3350 | 10 | 50 | 3350 | N/A | N/A | +| DC_5A-41A_n79A | 5 | 835 | 5 | 25 | 880 | 23.9 | IMD3 | +| | 41 | 2665 | 5 | 25 | 2665 | N/A | N/A | +| | n79 | 4450 | 40 | 216 | 4450 | N/A | N/A | +| | 5 | 826.5 | 5 | 25 | 871.5 | N/A | N/A | +| | 41 | 2517.5 | 5 | 25 | 2517.5 | 1.8 | IMD4 | +| | n79 | 4980 | 40 | 216 | 4980 | N/A | N/A | +| DC_7A-8A_n3A | n3 | 1735 | 5 | 25 | 1830 | N/A | N/A | +| | 7 | 2530 | 10 | 50 | 2650 | N/A | N/A | +| | 8 | 895 | 5 | 25 | 940 | 18.0 | IMD3 | +| | n3 | 1780 | 5 | 25 | 1875 | N/A | N/A | +| | 8 | 890 | 5 | 25 | 935 | N/A | N/A | +| | 7 | 2550 | 10 | 50 | 2670 | 29.0 | IMD2+IMD3 4 | +| DC_7A-20A_n1A | 7 | 2510 | 10 | 50 | 2630 | N/A | N/A | +| | 20 | 841 | 10 | 50 | 800 | 4.5 | IMD5 | +| | n1 | 1940 | 5 | 25 | 2130 | N/A | N/A | +| DC_7A-20A_n3A | 7 | 2543 | 10 | 50 | 2663 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-------------------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | 20 | 847 | 10 | 20 | 806 | 10.5 | IMD2 | +| | n3 | 1737 | 5 | 25 | 1832 | N/A | N/A | +| | 7 | 2510 | 10 | 50 | 2630 | 26.0 | IMD2 1 | +| | 20 | 855 | 5 | 25 | 814 | N/A | N/A | +| | n3 | 1775 | 10 | 50 | 1870 | N/A | N/A | +| DC_7A-20A_n8A | 7 | 2565 | 5 | 25 | 2685 | N/A | N/A | +| | n8 | 885 | 5 | 25 | 930 | N/A | N/A | +| | 20 | 836 | 5 | 25 | 795 | 17.4 | IMD3 | +| | 7 | 2520 | 5 | 25 | 2640 | 21.1 | IMD3 | +| | n8 | 900 | 5 | 25 | 945 | N/A | N/A | +| | 20 | 840 | 5 | 25 | 799 | N/A | N/A | +| | 7 | 2504 | 5 | 25 | 2624 | 18.8 | IMD3 | +| | n8 | 910 | 5 | 25 | 955 | N/A | N/A | +| | 20 | 857 | 5 | 25 | 816 | N/A | N/A | +| DC_7A-20A_n28A | 20 | 842 | 5 | 25 | 801 | N/A | N/A | +| | n28 | 728 | 5 | 25 | 783 | N/A | N/A | +| | 7 | 2520 | 10 | 50 | 2640 | 5.9 | IMD5 | +| DC_7A-20A_n78A | 7 | 2560 | 5 | 25 | 2680 | N/A | N/A | +| | 20 | 851 | 5 | 25 | 810 | 30.5 | IMD2 | +| | n78 | 3370 | 10 | 50 | 3370 | N/A | N/A | +| | 7 | 2560 | 5 | 25 | 2680 | N/A | N/A | +| | 20 | 851 | 5 | 25 | 810 | 3.0 | IMD5 | +| | n78 | 3435 | 10 | 50 | 3435 | N/A | N/A | +| | 7 | 2555 | 5 | 25 | 2675 | 30.8 | IMD2 | +| | 20 | 845 | 5 | 25 | 804 | N/A | N/A | +| | n78 | 3520 | 10 | 50 | 3520 | N/A | N/A | +| DC_7A-28A_n3A | 7 | 2543 | 5 | 25 | 2663 | N/A | N/A | +| | 28 | 741 | 5 | 25 | 796.0 | 20.0 | IMD2 | +| | n3 | 1747 | 5 | 25 | 1842 | N/A | N/A | +| | 7 | 2540 | 5 | 25 | 2685 | 18 | IMD3 | +| | 28 | 745 | 5 | 25 | 800 | N/A | N/A | +| | n3 | 1715 | 5 | 25 | 1810 | N/A | N/A | +| DC_7A-28A_n5A
DC_7C-28A_n5A | 7 | 2540 | 5 | 25 | 2725 | N/A | N/A | +| | 28 | 721 | 5 | 25 | 776 | 4.4 | IMD5 | +| | n5 | 829 | 5 | 25 | 854 | N/A | N/A | +| | 7 | 2510 | 5 | 25 | 2630 | 5.9 | IMD5 | +| | 28 | 730 | 5 | 25 | 785 | N/A | N/A | +| | n5 | 840 | 5 | 25 | 874 | N/A | N/A | +| DC_7A-28A_n78A | 7 | 2570 | 5 | 25 | 2670 | N/A | N/A | +| | 28 | 720 | 5 | 25 | 780 | 8.3 | IMD2 | +| | n78 | 3350 | 10 | 50 | 3421 | N/A | N/A | +| | 7 | 2570 | 5 | 25 | 2670 | N/A | N/A | +| | 28 | 720 | 5 | 25 | 790 | 3.0 | IMD5 | +| | n78 | 3460 | 10 | 50 | 3421 | N/A | N/A | +| | 7 | 2570 | 5 | 25 | 2650 | 30.5 | IMD2 | +| | 28 | 740 | 5 | 25 | 768 | N/A | N/A | +| | n78 | 3390 | 10 | 50 | 3421 | N/A | N/A | +| DC_7A_n28A-n78A | 7 | 2565 | 5 | 25 | 2685 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|------------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| DC_7C_n28A-n78A | n28 | 745 | 5 | 25 | 800 | N/A | N/A | +| | n78 | 3310 | 10 | 50 | 3310 | 29.7 | IMD2 | +| | 7 | 2565 | 5 | 25 | 2685 | N/A | N/A | +| | n78 | 3365 | 10 | 50 | 3365 | N/A | N/A | +| | n28 | 745 | 5 | 25 | 800 | 28.8 | IMD2 | +| DC_7A-46A_n78A 6 | 7 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 46 | N/A | N/A | N/A | N/A | N/A | IMD2, IMD5 | +| | n78 | N/A | N/A | N/A | N/A | N/A | N/A | +| DC_13A_n2A-n77A | 13 | 782 | 5 | 25 | 751 | N/A | N/A | +| | n2 | 1896 | 5 | 25 | 1976 | N/A | N/A | +| | n77 | N/A | 10 | N/A | 3460 | 17.3 | IMD3 | +| | 13 | 782 | 5 | 25 | 751 | N/A | N/A | +| | n2 | N/A | 5 | N/A | 1960 | 16.0 | IMD3 | +| | n77 | 3524 | 10 | 50 | 3524 | N/A | N/A | +| DC_13A-66A_n2A | 13 | 782 | 5 | 25 | 751 | N/A | N/A | +| | 66 | N/A | 5 | N/A | 2156 | 7.2 | IMD4 | +| | n2 | 1860 | 5 | 25 | 1940 | N/A | N/A | +| DC_13A-66A_n77A | 13 | 782 | 5 | 25 | 751 | N/A | N/A | +| | 66 | N/A | 5 | N/A | 2156 | 17.1 | IMD3 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | +| DC_14A-66A_n2A | 14 | 793 | 5 | 25 | 763 | N/A | N/A | +| DC_14A-66A-66A_n2A | 66 | 1762 | 5 | 25 | 2162 | 7.6 | IMD4 | +| | n2 | 1874 | 5 | 25 | 1954 | N/A | N/A | +| DC_18A-28A_n78A | 18 | 819 | 5 | 25 | 864 | 3.8 | IMD5 | +| | 28 | 723 | 5 | 25 | 778 | N/A | N/A | +| | n78 | 3756 | 10 | 50 | 3756 | N/A | N/A | +| DC_18A-41A_n3A
DC_18A-41C_n3A | 18 | 820 | 5 | 25 | 865 | N/A | N/A | +| | n3 | 1725 | 5 | 25 | 1820 | N/A | N/A | +| | 41 | 2630 | 5 | 25 | 2630 | 16.0 | IMD3 | +| | 18 | 820 | 5 | 25 | 865 | 28.9 | IMD2 | +| | n3 | 1765 | 5 | 25 | 1820 | N/A | N/A | +| | 41 | 2630 | 5 | 25 | 2630 | N/A | N/A | +| DC_18A-41A_n77A
DC_18A-41C_n77A | 18 | 820 | 5 | 25 | 865 | 3.4 | IMD5 | +| | n77 | 3527.5 | 10 | 50 | 3527.5 | N/A | N/A | +| | 41 | 2640 | 5 | 25 | 2640 | N/A | N/A | +| DC_18A-41A_n78A
DC_18A-41C_n78A | 18 | 820 | 5 | 25 | 865 | 3.4 | IMD5 | +| | n78 | 3527.5 | 10 | 50 | 3527.5 | N/A | N/A | +| | 41 | 2640 | 5 | 25 | 2640 | N/A | N/A | +| DC_19A-21A_n77A
DC_19A-21A_n78A | 19 | 837.5 | 5 | 25 | 882.5 | 18.7 | IMD3 | +| | 21 | 1450.4 | 5 | 25 | 1498.4 | N/A | N/A | +| | n77, n78 | 3783.3 | 10 | 50 | 3783.3 | N/A | N/A | +| DC_19A-21A_n77A | 19 | 837.5 | 5 | 25 | 882.5 | N/A | N/A | +| | 21 | 1454.5 | 5 | 25 | 1502.5 | 9.0 | IMD4 | +| | n77 | 4015 | 10 | 50 | 4015 | N/A | N/A | +| DC_19A-21A_n79A | 19 | N/A | N/A | N/A | N/A | N/A | IMD5 | +| | 21 | N/A | N/A | N/A | N/A | N/A | N/A | +| | n79 | N/A | N/A | N/A | N/A | N/A | N/A | +| | 19 | 837.5 | 5 | 25 | 882.2 | N/A | N/A | +| | 21 | 1452 | 5 | 25 | 1500 | 3.8 | IMD5 | +| | n79 | 4850 | 40 | 216 | 4850 | N/A | N/A | +| DC_20A_n3A-n78A | 20 | 845 | 5 | 25 | 804 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-----------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | n3 | 1730 | 5 | 25 | 1825 | N/A | N/A | +| | n78 | 3420 | 10 | 50 | 3420 | 16.1 | IMD3 | +| | 20 | 845 | 5 | 25 | 804 | N/A | N/A | +| | n3 | 1765 | 5 | 25 | 1860 | 15.7 | IMD3 | +| | n78 | 3550 | 10 | 50 | 3550 | N/A | N/A | +| DC_21A-28A_n77A | 21 | 1452 | 5 | 25 | 1500 | N/A | N/A | +| | 28 | 730.5 | 5 | 25 | 785.5 | 16.9 | IMD3 | +| | n77 | 3689.5 | 10 | 50 | 3689.5 | N/A | N/A | +| | 21 | 1450.5 | 5 | 25 | 1498.5 | 9.9 | IMD4 | +| | 28 | 730.5 | 5 | 25 | 785.5 | N/A | N/A | +| | n77 | 3690 | 10 | 50 | 3690 | N/A | N/A | +| DC_21A-28A_n79A | 21 | 1450 | 5 | 25 | 1498 | 5.2 | IMD5 | +| | 28 | 730.5 | 5 | 25 | 785.5 | N/A | N/A | +| | n79 | 4420 | 40 | 216 | 4420 | N/A | N/A | +| DC_28A_n7A-n78A | 28 | 745 | 5 | 25 | 800 | N/A | N/A | +| | n7 | 2565 | 5 | 25 | 2685 | N/A | N/A | +| | n78 | 3310 | 10 | 50 | 3310 | 29.7 | IMD2 | +| | 28 | 740 | 5 | 25 | 795 | N/A | N/A | +| | n7 | 2530 | 5 | 25 | 2650 | 30.5 | IMD2 | +| | n78 | 3390 | 10 | 50 | 3390 | N/A | N/A | +| DC_28A-42A_n79A | 28 | 730 | 5 | 25 | 785 | N/A | N/A | +| | 42 | 3420 | 5 | 25 | 3420 | 15.3 | IMD3 | +| | n79 | 4880 | 40 | 216 | 4880 | N/A | N/A | +| | 28 | 745 | 5 | 25 | 800 | 16.2 | IMD2 | +| | 42 | 3597.5 | 5 | 25 | 3597.5 | N/A | N/A | +| | n79 | 4420 | 40 | 216 | 4420 | N/A | N/A | +| DC_19A_n78A-n79A | 19 | 835 | 5 | 25 | 880 | N/A | N/A | +| | n78 | 3680 | 10 | 50 | 3680 | N/A | N/A | +| | n79 | 4515 | 40 | 216 | 4515 | 29.3 | IMD2 | +| | 19 | 835 | 5 | 25 | 880 | N/A | N/A | +| | n79 | 4550 | 40 | 216 | 4550 | N/A | N/A | +| | n78 | 3715 | 10 | 50 | 3715 | 28.8 | IMD2 | +| DC_20A_n28A-n78A
DC_20A_SUL_n78A-n83A | 20 | 857 | 5 | 25 | 816 | N/A | N/A | +| | n28, n83 | 743 | 5 | 25 | 798 | N/A | N/A | +| | n78 | 3314 | 10 | 50 | 3314 | 8.7 | IMD4 | +| | 20 | 837 | 5 | 25 | 796 | N/A | N/A | +| | n78 | 3310 | 10 | 50 | 3310 | N/A | N/A | +| | n28 | 744 | 5 | 25 | 799 | 9.4 | IMD4 | +| DC_21A_n78A-n79A | 21 | 1453 | 5 | 25 | 1501 | N/A | N/A | + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|---------------|-------------|----------------|---------------------|-------------|----------|-------------------| +| EN-DC Configuration | EUTRA/NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL L CRB | DL Fc (MHz) | MSD (dB) | IMD order | +| | n78 | 3420 | 10 | 50 | 3420 | N/A | N/A | +| | n79 | 4873 | 40 | 216 | 4873 | 30.1 | IMD2 | +| | 21 | 1453 | 5 | 25 | 1501 | N/A | N/A | +| | n79 | 4940 | 40 | 216 | 4940 | N/A | N/A | +| | n78 | 3487 | 10 | 50 | 3487 | 29.8 | IMD2 | +| DC_66A_n2A-n77A | n2 | N/A | 5 | N/A | 1960 | 32.1 | IMD2 | +| | 66 | 1760 | 5 | 25 | 2160 | N/A | N/A | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | +| DC_66A_n5A-n77A | 66 | 1770 | 5 | 25 | 2170 | N/A | N/A | +| | n5 | 845 | 5 | 25 | 890 | N/A | N/A | +| | n77 | N/A | 10 | N/A | 3460 | 16.6 | IMD3 9 | + +NOTE 1: For NR band, UL/DL BW and UL LCRB can be adjusted according to the supported BW and lowest SCS supported by the UE. + +NOTE 2: E-UTRA carrier shall be set to min(+20 dBm, PCMAX\_L\_E-UTRA,c) and NR carrier shall be set to min(+20 dBm, PCMAX\_L,f,c,NR) as defined in clause 6.2B.4.1.3. + +NOTE 3: This band is subject to IMD3 also which MSD is not specified. + +NOTE 4: This MSD requirement apply with both IMD2 and IMD3 products should be generated. + +NOTE 5 to NOTE 8: FFS + +NOTE 9: This band is subject to IMD4 also which MSD is not specified. + +7.3B.2.0.3.5.3 Void + +7.3B.2.0.3a Inter-band NE-DC within FR1 + +Reference sensitivity exceptions are specified for the condition when there is uplink transmission only in the aggressor band. This subclause addresses directly only NE-DC configurations that don't have a corresponding specified EN-DC configuration or specific NE-DC exceptions. + +7.3B.2.0.3a.1 Reference sensitivity exceptions due to UL harmonic interference for NE-DC in NR FR1 + +Sensitivity degradation is allowed for a band if it is impacted by UL harmonic interference from another band part of the same NE-DC configuration. For the NE-DC configurations that have an EN-DC defined configuration, the reference sensitivity exceptions for the victim band (high) are specified in Table 7.3B.2.3.1-1 with uplink configuration of the aggressor band (low) specified in Table 7.3B.2.3.1-2 are applicable. + +7.3B.2.0.4 Inter-band EN-DC including FR2 + +7.3B.2.0.4.1 Void + +7.3B.2.0.5 Inter-band EN-DC including both FR1 and FR2 + +7.3B.2.0.5.1 Reference sensitivity exceptions due to UL harmonic interference for EN-DC including both FR1 and FR2 + +For inter-band EN-DC of E-UTRA and NR in both FR1 and FR2, the UE is allowed to apply each sensitivity degradation for EN-DC in FR1 specified in clause 7.3B.2.3 TS 38.101-3 and for EN-DC including FR2 specified in clause 7.3B.2.3 of TS 38.101-3 independently. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.3B.2. + +#### 7.3B.2.1 Reference sensitivity for Intra-band Contiguous EN-DC (2 CCs) + +Editor's note: MSD test point selection is based on core spec requirement and shall be added to TP analysis to TS 38.905 [7]. + +##### 7.3B.2.1.1 Test purpose + +To verify the ability of UE that support intra-band contiguous EN-DC configurations to receive data with a given average throughput for a specified reference measurement channel, under conditions of low signal level, ideal propagation and no added noise. A UE unable to meet the throughput requirement under these conditions will decrease the effective coverage area. + +##### 7.3B.2.1.2 Test applicability + +This test applies to all types of NR UE release 15 and forward supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.3B.2.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.3B.2.0. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 7.3B.2.1.4 Test description + +###### 7.3B.2.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B, and the channel bandwidth combination for E-UTRA and NR component carriers shall follow the value specified in Table 5.3B.1.2-1. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2, and are shown in Table 7.3B.2.1.4.1-1 for DC\_(n)71AA and Table 7.3B.2.1.4.1-2 for intra-band contiguous EN-DC other than DC\_(n)71AA. + +The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 for E-UTRA RMC, and in TS 38.521-1 [8] Annex A.2 and A.3 for NR RMC respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.3B.2.1.4.1-1: Test configurations table for EN-DC configurations affected by Reference sensitivity exceptions** + +| Initial Conditions | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----------------------------------------------|----------------------|-----------------------------------|------------------------------------------------|-------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | +| NR Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508 [11] clause 4.3.1 | Specified below | | | | | | | +| E-UTRA Test Channel Bandwidths as specified in TS 36.508 [11] clause 4.3.1 | Specified below | | | | | | | +| NR Test Channel Bandwidths as specified in TS 38.508-1 [6] clause 4.3.1 | Specified below | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | | | +| Network signalling value | NS_01 by default, exceptions listed in Table 7.3.3-3 in TS 36.521-1 [10], dependent on PCC Band | | | | | | | +| NR/E-UTRA Test Parameters | | | | | | | | +| Downlink Configuration | | | | Uplink Configuration | | | | +| NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| CP-OFDM
QPSK | Full RB (NOTE 1) | QPSK | Full RB | DFT-s-OFDM
QPSK | | QPSK | | +| Test Point configurations | | | | | | | | +| Test Settings for DC_(n)71AA for dual UL UE | | | | | | | | +| Test ID | E-UTRA/NR band | F c (UL) (MHz)
N UL | UL Channel BW (MHz) | UL allocation (L CRB ) | F c (DL) (MHz)
N DL | Duplex mode | | +| 1 | 71 | 665.5MHz,
E UL = 133147 | 5 | 5@19 | 619.5 MHz
E DL = 68611 | FDD | | +| | n71 | 675.5
N UL = 135100 | 15 | 15@0 | 629.5
N DL = 125900 | | | +| 2 | 71 | 670.5
E UL = 133197 | 15 | 15@59 | 624.5
E DL = 68661 | | | +| | n71 | 680.5
N UL = 136100 | 5 | 5@0 | 634.5
N DL = 126900 | | | +| 3 | 71 | 668
E UL = 133172 | 10 | 10@39 | 622
E DL = 68636 | | | +| | n71 | 678
N UL = 135600 | 10 | 10@0 | 632
N DL = 126400 | | | +| 4 | 71 | 668
E UL = 133172 | 10 | 10@0 | 622
E DL = 68636 | | | +| | n71 | 678
N UL = 135600 | 10 | 10@41 | 632
N DL = 126400 | | | +| 5 | 71 | 665.5
E UL = 133147 | 5 | 5@19 | 619.5
E DL = 68611 | | | +| | n71 | 675.5
N UL = 135100 | 15 3 | 15@0 | 632 3
N UL = 126400 | | | +| 6 | 71 | 670.5
E UL = 133197 | 15 | 15@59 | 624.5
E DL = 68661 | | | +| | n71 | 680.5
N UL = 136100 | 5 3 | 5@0 | 637 3
N UL = 127400 | | | +| 7 | 71 | 668
E UL = 133172 | 10 | 10@39 | 622
E DL = 68636 | | | +| | n71 | 678
N UL = 135600 | 10 3 | 10@0 | 634.5 3
N UL = 126900 | | | +| 8 | 71 | 668 | 10 | 10@0 | 622 | | | + +| | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------|-----------------|------------|------------------------------------------------|-----| +| | | E UL = 133172 | | | E DL = 68636 | | +| | n71 | 678
N UL = 135600 | 10 3 | 10@41 | 634.5 3
N UL = 126900 | | +| Test Settings for DC_(n)71AA for single UL UE | | | | | | | +| 1 | 71 | default | Highest | 0 | default | FDD | +| | n71 | default | Highest | REFSENS_NR | default | | +|

NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8].

NOTE 2: Test Channel Bandwidths are checked separately for each E-UTRA band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1.

NOTE 3: In accordance to BCS1, the NR uplink bandwidth is specified as in this table, but the corresponding NR downlink bandwidth is 5 MHz larger.

NOTE 4: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected.

NOTE 5: REFSENS_NR refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.2.4.1-3 of TS 38.521-1 [8].

| | | | | | | + +**Table 7.3B.2.1.4.1-2: Test configurations table for EN-DC configurations not affected by Reference sensitivity exceptions, EN-DC configuration other than DC\_(n)71AA** + +| Initial Conditions | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--------------------------------------|------------------------|-------------------------------------------------------------------------------------------------|--------------|--------------------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| NR Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1,
E-UTRA Test Frequencies as specified in TS 36.508 [11] clause 4.3.1 | | | | | Low range, High range | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE. | | | | | Refer to "NR N RB " and "E-UTRA N RB " columns | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | | | | | Lowest supported SCS | | | | +| Network signalling value | | | | | NS_01 by default, exceptions listed in Table 7.3.3-3 in TS 36.521-1 [10], dependent on PCC Band | | | | +| Test Parameters for DC Configurations | | | | | | | | | +| ID | PCC – E-UTRA | | | | SCG -NR | | | | +| | Band | Range | N RB | | Band | Range | N RB | | +| | UL MOD | DL MOD | CH BW | DLalloc / UL alloc | UL MOD | DL MOD | UL/DL Ch BW | DLalloc / UL alloc | +| Test Settings for a DC_(n)XAA Configuration (Intra-band contiguous EN-DC) – Note 2 | | | | | | | | | +| 1
(Note 4) | X | default | | | nX | default | | | +| | QPSK | QPSK | Highest N RB_agg (Note 6) | All RBs / REFESENS_LTE | DFT-s-OFDM QPSK | CP-OFDM QPSK | Highest N RB_agg (Note 6) | All RBs / REFESENS_NR | +| 2
(Note 5) | X | default | | | nX | default | | | +| | N/A | QPSK | Highest N RB | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | Highest N RB | All RBs / REFESENS_NR | +| Note 1: | REFSENS_NR and REFESENS_LTE refer to the single carrier Uplink RB allocation for reference sensitivity according to Table 7.3.2.4.1-3 of TS 38.521-1 [8] and Table 7.3.4.1-1 of TS 36.521 [10] for NR and E-UTRA CC respectively. | | | | | | | | +| Note 2: | Not LTE anchor agnostic configuration due to exception requirement for intra-band contiguous CA in clause 7.4B, 7.5B, 7.6B.2, 7.6B.3, 7.6B.4, 7.7B, 7.8B, 7.9B test cases | | | | | | | | +| Note 3: | In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. | | | | | | | | +| Note 4: | Test point for UE supporting dual UL. | | | | | | | | +| Note 5: | Test point for UE supporting single UL. | | | | | | | | +| Note 6: | If the UE supports multiple CC combinations in the EN-DC configuration with the same N RB_agg , select the combination to test as follows:
- Lowest ENBW: NR component with lowest N RB is tested.
- Highest ENBW: NR component with highest N RB is tested. | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2.1 for UE diagram. +2. The parameter settings for NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +4. NR downlink signals are initially set up according to Annex C.0, C.1, C.2, C.3.1, and uplink signals according to Annex G.0, G.1, G.2, and G.3.1 of TS 38.521-1 [8]. +5. E-UTRA downlink signals are initially set up according to Annex C0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. + +6. The DL and UL Reference Measurement channels for NR are set according to Table 7.3B.2.1.4.1-1 and Table 7.3B.2.1.4.1-2. +7. The DL and UL Reference Measurement channels for E-UTRA are set according to Table 7.3B.2.1.4.1-1 and Table 7.3B.2.1.4.1-2. +8. NR propagation conditions are set according to Annex B.0 of TS 38.521-1 [8]. +9. E-UTRA propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +10. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters *Connectivity* EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.3B.2.1.4.3. +11. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 7.3B.2.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.3B.2.1.4.1-1 and Table 7.3B.2.1.4.1-2 on the E-UTRA CC and NR CC. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.3B.2.3.4.1-1 on both EN-DC component carriers. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. For test points in Table 7.3B.2.1.4.1-1, set the Downlink signal level to the appropriate REFSENS value defined in Table 7.3B.2.1.5-1. For test points in Table 7.3B.2.1.4.1-2, set the Downlink signal level to the appropriate REFSENS value defined in TS 38.521-1 [8], Table 7.3.3-1 for NR band and TS 36.521-1 [10] Table 7.3.3-1 for E-UTRA band. Send continuously uplink power control "up" commands in the uplink scheduling information to both carriers to ensure the UE transmits PUMAX level for at least the duration of the Throughput measurement. +4. Measure the average throughput of both NR and E-UTRA for a duration sufficient to achieve statistical significance according to Annex H.2 of TS 38.521-1 [8] for NR band, and Annex G.2 of TS 36.521-1 [10] for EUTRA band. + +###### 7.3B.2.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +Message contents exceptions are according to TS 36.521-1 [10] clause 7.3.4.3 for each network signalling value. + +##### 7.3B.2.1.5 Test requirement + +For intra-band contiguous EN-DC configurations DC\_(n)71AA with dual UL, the throughput of each CG shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 with reference receive power level specified in Table 7.3B.2.1.5-1. + +Reference sensitivity test requirements for EN-DC configurations other than DC\_(n)71AA with dual UL UE, are specified in Table 7.3.5-1 in TS 36.521-1 [10] for the LTE CC, and Table 7.3.2.5-1 in TS 38.521-1 [8] for the NR CC. + +**Table 7.3B.2.1.5-1: Reference sensitivity for intra-band DC\_(n)71AA with dual UL** + +| EN-DC | E-UTRA/
NR band | SCS
(kHz) | Channel
BW
(MHz) | Ref
sensitivity
(dBm) | Note | Duplex
mode | | +|------------|--------------------|--------------|------------------------|-----------------------------|--------|----------------|--| +| DC_(n)71AA | 71 | N/A | 5 | -96.5 | Note 1 | FDD | | +| | n71 | 15 | 15 | -89.8 +TT | | | | +| | 71 | N/A | 15 | -91.3 | Note 2 | | | +| | n71 | 15 | 5 | -95.6 +TT | | | | +| | 71 | N/A | 10 | -93.5 | Note 3 | | | +| | n71 | 15 | 10 | -92.3 +TT | | | | +| | 71 | N/A | 10 | -76.3 | Note 4 | | | +| | n71 | 15 | 10 | -64.6 +TT | | | | +| | 71 | N/A | 5 | -96.5 | Note 5 | | | +| | n71 | 15 | 15 9 | -89.1 +TT | | | | +| | 71 | N/A | 15 | -91.3 | Note 6 | | | +| | n71 | 15 | 5 9 | -95.0 +TT | | | | +| | 71 | N/A | 10 | -93.5 | Note 7 | | | +| | n71 | 15 | 10 9 | -91.5 +TT | | | | +| | 71 | N/A | 10 | -76.3 | Note 8 | | | +| | n71 | 15 | 10 9 | -64.9 +TT | | | | + +NOTE 1: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 1. +NOTE 2: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 2. +NOTE 3: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 3. +NOTE 4: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 4. +NOTE 5: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 5. +NOTE 6: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 6. +NOTE 7: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 7. +NOTE 8: For test configuration specified by Table 7.3B.2.1.4.1-1 Test ID 8. +NOTE 9: In accordance to BCS1, the NR uplink bandwidth is specified as in this table, but the corresponding NR downlink bandwidth is 5 MHz larger. + +**Table 7.3B.2.1.5-2: Test Tolerance (TT) for NR RX sensitivity level** + +| $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 6.0\text{ GHz}$ | +|------------------------|-----------------------------------------| +| 0.7 dB | 1.0 dB | + +#### 7.3B.2.2 Reference sensitivity for Intra-band non-contiguous EN-DC (2 CCs) + +Editor's note: No test case details specified due to no confirmed industry interest for intra-band non-contiguous EN-DC combinations (removed at RAN5 #97). + +#### 7.3B.2.3 Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs) + +##### 7.3B.2.3.1 Test purpose + +Same as in clause 7.3B.2.1.1. + +##### 7.3B.2.3.2 Test applicability + +This test applies to all types of NR UE release 15 and forward supporting inter-band EN-DC within FR1 with 2 DL CCs. + +##### 7.3B.2.3.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.3B.2.0. + +For exception requirements applicable for both NR and LTE, LTE anchor agnostic approach is not applied. + +For non-exception requirements applicable to NR, LTE anchor agnostic approach is applied. + +##### 7.3B.2.3.4 Test description + +###### 7.3B.2.3.4.1 Void + +###### 7.3B.2.3.4.2 Test description + +###### 7.3B.2.3.4.2.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths based on EN-DC operating bands specified in clause 5.5B, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration, and are shown in Table 7.3B.2.3.4.2.1-0 to Table 7.3B.2.3.4.2.1-6. + +The details of the uplink and downlink reference measurement channels (RMCs) are specified in TS 36.521-1 [10] Annex A.2 and A.3 for E-UTRA RMC, and in TS 38.521-1 [8] Annex A.2 and A.3 for NR RMC respectively. The details of the OCN patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG, respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG, respectively. + +For configurations without any reference sensitivity exception, in a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. For configurations with reference sensitivity exception, in an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. + +**Table 7.3B.2.3.4.2.1-0: Void** + +Table 7.3B.2.3.4.2.1-1: Void + +Table 7.3B.2.3.4.2.1-2\_1: Void + +Table 7.3B.2.3.4.2.1-2\_2: Void + +Table 7.3B.2.3.4.2.1-2\_3: Void + +Table 7.3B.2.3.4.2.1-2\_4: Void + +Table 7.3B.2.3.4.2.1-2\_5: Void + +Table 7.3B.2.3.4.2.1-2\_6: Void + +Table 7.3B.2.3.4.2.1-2\_7: Void + +Table 7.3B.2.3.4.2.1-2\_8: Void + +Table 7.3B.2.3.4.2.1-2\_9: Void + +Table 7.3B.2.3.4.2.1-2\_11: Void + +Table 7.3B.2.3.4.2.1-2\_12: Void + +Table 7.3B.2.3.4.2.1-2\_13: Void + +Table 7.3B.2.3.4.2.1-2\_14: Void + +Table 7.3B.2.3.4.2.1-2\_15: Void + +Table 7.3B.2.3.4.2.1-2\_16: Void + +Table 7.3B.2.3.4.2.1-2\_17: Void + +Table 7.3B.2.3.4.2.1-2\_18: Void + +Table 7.3B.2.3.4.2.1-2\_19: Void + +Table 7.3B.2.3.4.2.1-2\_20: Void + +Table 7.3B.2.3.4.2.1-2\_21: Void + +Table 7.3B.2.3.4.2.1-2\_22: Void + +**Table 7.3B.2.3.4.2.1-2\_23: Void** + +**Table 7.3B.2.3.4.2.1-4: Void** + +**Table 7.3B.2.3.4.2.1-4a: Void** + +**Table 7.3B.2.3.4.2.1-4b: Void** + +**Table 7.3B.2.3.4.2.1-4c: Void** + +**Table 7.3B.2.3.4.2.1-4d: Void** + +**Table 7.3B.2.3.4.2.1-4e: Void** + +**Table 7.3B.2.3.4.2.1-4f: Void** + +**Table 7.3B.2.3.4.2.1-4g: Void** + +**Table 7.3B.2.3.4.2.1-4h: Void** + +**Table 7.3B.2.3.4.2.1-4i: Void** + +**Table 7.3B.2.3.4.2.1-4j: Void** + +**Table 7.3B.2.3.4.2.1-4k: Void** + +**Table 7.3B.2.3.4.2.1-4l: Void** + +**Table 7.3B.2.3.4.2.1-4m: Void** + +**Table 7.3B.2.3.4.2.1-4n: Void** + +**Table 7.3B.2.3.4.2.1-5: Void** + +**Table 7.3B.2.3.4.2.1-6: Test Configuration Table for EN-DC configurations affected by Reference sensitivity exceptions (two bands)** + +| Initial Conditions | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|---------------------------|-----------------|---------------------|-----------------------|---------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | | +| NR Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1,
E-UTRA Test Frequencies as specified in TS 36.508 [11] clause 4.3.1 | For test frequencies refer to "Range" columns. | | | | | | | | +| Test EN-DC channel bandwidth as specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1. | Refer to "NR N RB " and "E-UTRA N RB " columns | | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest supported SCS | | | | | | | | +| Network signalling value | NS_01 by default
Unless given by Table 7.3.3-3 in TS 36.521-1 [10] for the E-UTRA band and Table 7.3.2.3-4 in TS 38.521-1 [8] for the NR band. | | | | | | | | +| Test Parameters for DC Configurations | | | | | | | | | +| ID | PCC – E-UTRA | | | | SCG -NR | | | | +| | Band | Range | NRB | | Band | Range | NRB | | +| | UL MOD | DL MOD | CH BW | DLalloc / UL alloc | UL MOD | DL MOD | UL/DL Ch BW | DLalloc / UL alloc | +| Test Settings for a DC_1A_n3A Configuration | | | | | | | | | +| 1 2,11 | 1 | Mid | | | n3 | Mid | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFESENS_ENDC_3 | N/A | CP-OFDM QPSK | 40 MHz | All RBs / 0 | +| 2 4,10 | 1 | UL 1950 / DL 2140 | | | n3 | UL 1760 / DL 1855 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | +| 3 6 | 1 | Low | | | n3 | High | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFESENS_ENDC_3 | N/A | CP-OFDM QPSK | 40 MHz | All RBs / 0 | +| Test Settings for a DC_1A_n8A Configuration | | | | | | | | | +| 1 4 | 1 | UL 1965 / DL 2155 | | | n8 | UL 887.5 / DL 932.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | +| Test Settings for a DC_1A_n28A Configuration | | | | | | | | | +| 1 3 | 1 | UL 1950 / DL 2140 | | | n28 | UL 713.3 / DL 768.3 | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFESENS_ENDC_1 | +| 2 8 | 1 | UL 1970 / DL 2160 | | | n28 | UL 708 / DL 763 | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFESENS_ENDC_1 | +| Test Settings for a DC_1A_n41A Configuration | | | | | | | | | +| 1 6 | 1 | High | | | n41 | Low | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFESENS_ENDC_3 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 6 | 1 | High | | | n41 | Low | | | +| | QPS | QPSK | 20 MHz | All RBs / 0 | DFT-s- | CP-OFDM | 50 MHz | All RBs / | + +| | | | | | | | | | +|-----------------------------------------------------|----------|------------------------|--------|---------------------------------|------------------------|-------------------|------------|---------------------------------| +| | K | | | | OFDM
QPSK | QPSK | | REFSENS_ENDC_
3 | +| Test Settings for a DC_1A_n77A Configuration | | | | | | | | | +| 1 3 | 1 | UL 1950/
DL 2140 | | | n77 | UL/DL 3900 | | | +| | QPS
K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_
1 | N/A | CP-OFDM
QPSK | 100
MHz | All RBs / 0 | +| 2 3 | 1 | UL 1950/
DL 2140 | | | n77 | UL/DL 3870 | | | +| | QPS
K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_
1 | N/A | CP-OFDM
QPSK | 20 MHz | All RBs / 0 | +| 3 4 | 1 | UL 1950/
DL 2140 | | | n77 | UL/DL
4090.005 | | | +| | QPS
K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | N/A | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_
4 | +| 4 4 | 1 | UL 1950/
DL 2140 | | | n77 | UL/DL
3709.995 | | | +| | QPS
K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | N/A | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_
4 | +| Test Settings for a DC_1A_n78A Configuration | | | | | | | | | +| 1 4 | 1 | UL 1950 /
DL 2140 | | | n78 | UL/DL
3709.995 | | | +| | QPS
K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_
4 | +| Test Settings for a DC_2A_n41A Configuration | | | | | | | | | +| 1 6 | 2 | High | | | n41 | Low | | | +| | N/A | QPSK | 20 MHz | All RBs /
REFSENS_LTE | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 100
MHz | All RBs /
REFSENS_ENDC_
3 | +| Test Settings for a DC_2A_n66A Configuration | | | | | | | | | +| 1 4 | 2 | UL 1855 /
DL 1935 | | | n66 | DL 2175 | | | +| | QPS
K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | +| 2 4 | 2 | UL 1883.3
/DL1963.3 | | | n66 | DL 2150 | | | +| | QPS
K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
4 | +| Test Settings for a DC_2A_n71A Configuration | | | | | | | | | +| 1 3 | 2 | DL 1980
MHZ | | | n71 | UL 665.5
MHz | | | +| | QPS
K | QPSK | 20 MHz | All RBs / 0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_
1 | +| 2 3 | 2 | DL1980
MHZ | | | n71 | UL 673 MHz | | | +| | QPS
K | QPSK | 20 MHz | All RBs / 0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_
1 | +| 3 5 | 2 | UL 1881
MHZ | | | n71 | Low | | | + +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_2 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20 MHz | All RBs / 0 | +|-----------------------------------------------------|-------|-----------------|--------|-----------------------------|-----------------|----------------|---------|-----------------------------| +| Test Settings for a DC_2A_n77A Configuration | | | | | | | | | +| 1 3 | 2 | UL 1860 | | | n77 | UL/DL 3720 | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 2 | UL 1860 | | | n77 | UL/DL 3690.005 | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 20 MHz | All RBs / 0 | +| 3 8 | 2 | UL 1860 | | | n77 | UL/DL 3850.005 | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 10 MHz | All RBs / 0 | +| 4 5 | 2 | DL Mid | | | n77 | UL/DL 3920.01 | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 4a 9 | 2 | DL Mid | | | n77 | UL/DL Mid | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 5 4 | 2 | UL 1855/DL 1935 | | | n77 | UL/DL 3790.005 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| 6 4 | 2 | UL 1900/DL 1980 | | | n77 | UL/DL 3720 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| 7 4 | 2 | UL 1885/DL 1965 | | | n77 | UL/DL 3810 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_2A_n78A Configuration | | | | | | | | | +| 1 3 | 2 | UL 1870 | | | n78 | UL/DL 3740.01 | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 2 | UL 1885 | | | n78 | UL/DL 3739.995 | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 20 MHz | All RBs / 0 | +| 3 4 | 2 | UL 1855/DL 1935 | | | n78 | UL/DL 3790.005 | | | + +| | | | | | | | | | +|-----------------------------------------------------|-------|-----------------------|--------|---------------------------|-----------------|---------------------|---------|---------------------------| +| | QPS K | QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | +| 4 4 | 2 | UL 1885/ DL 1965 | | | n78 | UL/DL 3690 | | | +| | QPS K | QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | +| Test Settings for a DC_3A_n1A Configuration | | | | | | | | | +| 1 11 | 3 | Mid | | | n1 | Mid | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 50 MHz | All RBs / REFSENS_ENDC_ 3 | +| 2 6 | 3 | High | | | n1 | Low | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 50 MHz | All RBs / REFSENS_ENDC_ 3 | +| 3 4 | 3 | UL 1760 / DL 1855 | | | n1 | UL 1950 / DL 2140 | | | +| | QPS K | QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | +| Test Settings for a DC_3A_n5A Configuration | | | | | | | | | +| 1 4 | 3 | UL 1771 / DL 1866 | | | n5 | UL 838 / DL 883 | | | +| | QPS K | QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | +| 2 4 | 3 | UL 1721 / DL 1816 | | | n5 | UL 838 / DL 883 | | | +| | QPS K | QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | +| Test Settings for a DC_3A_n7A Configuration | | | | | | | | | +| 1 4 | 3 | UL 1730 / DL 1825 | | | n7 | UL 2535 / DL 2655 | | | +| | QPS K | QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | +| Test Settings for a DC_3A_n8A Configuration | | | | | | | | | +| 1 4 | 3 | UL 1755 / DL 1850 | | | n8 | UL 900 / DL 945 | | | +| | QPS K | QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | +| 2 4 | 3 | UL 1747.5 / DL 1842.5 | | | n8 | UL 897.5 / DL 942.5 | | | +| | QPS K | QPSK | 10 MHz | All RBs / REFSENS_ENDC_ 4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_ 4 | +| Test Settings for a DC_3A_n41A Configuration | | | | | | | | | +| 1 6 | 3 | High | | | n41 | Low | | | +| | QPS K | QPSK | 20 MHz | All RBs / REFSENS_ENDC_ 3 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 6 | 3 | High | | | n41 | Low | | | + +| | | | | | | | | | +|--------------------|------|-------------------|--------|---------------------------|-----------------|--------------|--------|---------------------------| +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 50 MHz | All RBs / REFESENS_ENDC_3 | +| 3 4, 10 | 3 | UL 1740 / DL 1835 | | | n41 | UL/DL 2657.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFESENS_ENDC_4 | + +###### **Test Settings for DC\_3A\_n77A and DC\_3A\_n78A Configurations** + +| | | | | | | | | | +|----------------|------|-------------------|--------|---------------------------|-----------------|----------------|---------|---------------------------| +| 1 3 | 3 | Mid | | | n78 | UL/DL 3495 | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFESENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 3 | Mid | | | n78 | UL/DL 3525 | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFESENS_ENDC_1 | N/A | CP-OFDM QPSK | 20 MHz | All RBs / 0 | +| 3 5 | 3 | Mid | | | n78 | UL/DL 3685.005 | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20 MHz | All RBs / REFESENS_ENDC_2 | +| 3 9 | 3 | Low | | | n78 | High | | | +| | QPSK | QPSK | 20 MHz | All RBs/0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20 MHz | All RBs / REFESENS_ENDC_2 | +| 4 4 | 3 | UL 1740 / DL 1835 | | | n78 | UL/DL 3574.995 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFESENS_ENDC_4 | +| 5 4 | 3 | UL 1765 / DL 1860 | | | n78 | UL/DL 3435 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFESENS_ENDC_4 | + +###### **Test Settings for a DC\_5A\_n66A Configuration** + +| | | | | | | | | | +|----------------|------|----------------|-------|---------------------------|-----|------------------|-------|---------------------------| +| 1 4 | 5 | UL 838/ DL 883 | | | n66 | UL 1721/ DL 2121 | | | +| | QPSK | N/A | 5 MHz | All RBs / REFESENS_ENDC_4 | N/A | CP-OFDM QPSK | 5 MHz | All RBs / REFESENS_ENDC_4 | + +###### **Test Settings for a DC\_5A\_n77A Configuration** + +| | | | | | | | | | +|----------------|------|--------------------|--------|---------------------------|-----|---------------|---------|-------------| +| 1 3 | 5 | UL 837.5 | | | n77 | UL/DL 3350.01 | | | +| | QPSK | QPSK | 10 MHz | All RBs / REFESENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 5 | UL 829 | | | n77 | UL/DL 4145.01 | | | +| | QPSK | QPSK | 10 MHz | All RBs / REFESENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 3 8 | 5 | UL Mid (836.5 MHz) | | | n77 | UL/DL Mid | | | + +| | | | | | | | | | +|-----------------------------------------------------|------|-------------------------|--------|-----------------------------|--------------------|-------------------|---------|-----------------------------| +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 4 4, 13 | 5 | UL
844/DL
889 | | | n77 | UL/DL
3421.005 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| 5 4, 13 | 5 | UL
826.5/DL
871.5 | | | n77 | UL/DL
4177.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for DC_5A_n78A Configuration | | | | | | | | | +| 1 3 | 5 | UL 840 | | | n78 | UL/DL 3360 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 5 | UL 840 | | | n78 | UL/DL
3560.01 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 3 4 | 5 | UL
844/DL
889 | | | n78 | UL/DL
3421.005 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_7A_n3A Configuration | | | | | | | | | +| 1 4 | 7 | DL 2655 | | | n3 | DL 1825 | | | +| | QPSK | N/A | 10 MHz | N/A | N/A | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_7A_n5A Configuration | | | | | | | | | +| 1 4 | 7 | DL 2667 | | | n5 | DL 879 | | | +| | QPSK | N/A | 10 MHz | N/A | N/A | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_7A_n66A Configuration | | | | | | | | | +| 1 4 | 7 | DL 2655 | | | n66 | DL 2130 | | | +| | QPSK | | 10 MHz | N/A | N/A | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_7A_n71A Configuration | | | | | | | | | +| 1 3 | 7 | DL 2672 | | | n71 | UL/ 668 | | | +| | QPSK | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_1 | +| 2 8 | 7 | DL 2630 | | | n71 | UL 668 | | | +| | QPSK | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_1 | +| Test Settings for a DC_7A_n77A Configuration | | | | | | | | | +| 1 4 | 7 | DL 2660 | | | N77 | DL 3870 | | | + +| | | | | | | | | | +|-------------------------------------------------------------------|------|-------------------------|--------|--------------------------|-----------------|---------------------|---------|--------------------------| +| | QPSK | | 5 MHz | N/A | N/A | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_4 | +| Test Settings for a DC_7A_n78A Configuration | | | | | | | | | +| 1 6 | 7 | High | | | n78 | Low | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFSENS_ENDC_3 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| Test Settings for a DC_8A_n1A Configuration | | | | | | | | | +| 1 4 | 8 | DL 932.5 | | | n1 | DL 2155 | | | +| | QPSK | N/A | 5 MHz | N/A | N/A | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_4 | +| Test Settings for a DC_8A_n3A Configuration | | | | | | | | | +| 1 4 | 8 | DL 945 | | | n3 | DL 1850 | | | +| | QPSK | N/A | 5 MHz | N/A | N/A | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_4 | +| 2 4 | 8 | DL 942.5 | | | n3 | DL 1842.5 | | | +| | QPSK | N/A | 5 MHz | N/A | N/A | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_4 | +| Test Settings for a DC_8A_n20A Configuration | | | | | | | | | +| 1 4 | 8 | UL 890.5 / DL 935.5 | | | n20 | UL 849.5 / DL 808.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_4 | +| 2 4 | 8 | UL 892.5 / DL 937.5 | | | n20 | UL 847.5 / DL 806.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSENS_ENDC_4 | +| Test Settings for a DC_8A_n41A Configuration | | | | | | | | | +| 1 3 | 8 | UL 885 / DL 942.5 MHz | | | n41 | UL / DL 2655 MHz | | | +| | QPSK | QPSK | 10 MHz | All RBs / REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 60 MHz | All RBs / 0 | +| 2 8 | 8 | UL 885 / DL 942.5 MHz | | | n41 | UL / DL 2546 MHz | | | +| | QPSK | QPSK | 10 MHz | All RBs / REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 60 MHz | All RBs / 0 | +| 3 4 | 8 | UL 882.5 / DL 927.5 MHz | | | n41 | UL / DL 2685MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSENS_ENDC_4 | +| Test Settings for DC_8A_n77A and DC_8A_n78A Configurations | | | | | | | | | +| 1 3 | 8 | Mid | | | n77 | UL/DL 3590.01 | | | + +| | | | | | | | | | +|--------------------------------------------------------------------|------|---------------|--------|-----------------------------|--------------------|---------------------|---------|-----------------------------| +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 8 | Mid | | | n77 | UL/DL
3520.005 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 3 4 | 8 | UL 897.5 | | | n77 | UL/DL
3634.995 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_11A_n79A Configuration | | | | | | | | | +| 1 5 | 11 | Mid | | | n79 | UL/DL
4457.7 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 2 9 | 11 | Mid | | | n79 | UL/DL
4512.69 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| Test Settings for a DC_12A_n66A Configuration | | | | | | | | | +| 1 3 | 12 | UL 710 | | | n66 | UL 1730
/DL 2130 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 40 MHz | All RBs / 0 | +| 2 8 | 12 | UL 710 | | | n66 | UL 1770
/DL 2170 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 40 MHz | All RBs / 0 | +| Test Settings for a DC_12A_n77A Configuration (PC2 and PC3) | | | | | | | | | +| 1 3 | 12 | Mid | | | n77 | UL/DL
3537.495 | | | +| | QPSK | QPSK | 10MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 12 | Mid | | | n77 | UL/DL 3351 | | | +| | QPSK | QPSK | 10MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 3 5 | 12 | Mid | | | n77 | UL/DL
3687.495 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 4 9 | 12 | Mid | | | n77 | UL/DL 3750 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 5 4 | 12 | UL 702/DL 732 | | | n77 | UL/DL 3540 | | | + +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +|--------------------------------------------------------------------|-------|-------------------|--------|-----------------------------|-----------------|----------------|---------|-----------------------------| +| Test Settings for a DC_12A_n78A Configuration | | | | | | | | | +| 1 3 | 12 | UL 707/DL 737 MHz | | | n78 | UL/DL 3535 MHz | | | +| | QPS K | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 12 | UL 707/DL 737 MHz | | | n78 | UL/DL 3750 MHz | | | +| | QPS K | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 3 4,10 | 12 | UL 710/DL 740 MHz | | | n78 | UL/DL 3580 MHz | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_13A_n77A Configuration | | | | | | | | | +| 1 3 | 13 | UL Mid | | | n77 | UL/DL 3909.99 | | | +| | QPS K | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 13 | UL Mid | | | n77 | UL/DL Mid | | | +| | QPS K | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 3 5 | 13 | DL Mid | | | n77 | UL/DL 3755 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 4 9 | 13 | DL Mid | | | n77 | UL/DL 3850 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 5 4 | 13 | UL 784.5/DL 753.5 | | | n77 | UL/DL 3891.495 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_14A_n77A Configuration (PC2 and PC3) | | | | | | | | | +| 1 3 | 14 | Mid | | | n77 | UL/DL 3964.995 | | | +| | QPS K | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 1 8 | 14 | Mid | | | n77 | UL/DL 3350.1 | | | + +| | | | | | | | | | +|--------------------------------------------------------------------|------|-------------------------|--------|-----------------------------|--------------------|----------------------|---------|-----------------------------| +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 5 | 14 | Mid | | | n77 | UL/DL
3814.995 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 2 9 | 14 | Mid | | | n77 | UL/DL
3350.01 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_ENDC_2 | +| 3 4 | 14 | UL
795.5/DL
765.5 | | | n77 | UL/DL
3947.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_4 | +| Test Settings for a DC_18A_n77A Configuration | | | | | | | | | +| 1 3 | 18 | UL 820 | | | n77 | UL/DL 4100 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 40 MHz | All RBs / 0 | +| 2 8 | 18 | UL 820 | | | n77 | UL/DL 4000 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 40 MHz | All RBs / 0 | +| Test Settings for a DC_19A_n77A Configuration | | | | | | | | | +| 1 3 | 19 | UL 835 | | | n77 | UL/DL 4175 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 40 MHz | All RBs / 0 | +| 2 8 | 19 | UL 835 | | | n77 | UL/DL 4100 | | | +| | QPSK | QPSK | 10 MHz | All RBs /
REFSENS_ENDC_1 | N/A | CP-OFDM
QPSK | 40 MHz | All RBs / 0 | +| Test Settings for a DC_19A_n79A Configuration (PC2 and PC3) | | | | | | | | | +| 1 5 | 19 | DL 884 | | | n79 | UL/DL 4420 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 40 MHz | All RBs /
REFSENS_ENDC_2 | +| 2 9 | 19 | DL 884 | | | n79 | UL/DL
4445.025 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 40 MHz | All RBs /
REFSENS_ENDC_2 | +| Test Settings for a DC_20A_n3A Configuration | | | | | | | | | +| 1 4 | 20 | UL 840 /
DL 799 | | | n3 | UL 1775 /
DL 1870 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_4 | +| 2 4 | 20 | UL 847 /
DL 806 | | | n3 | UL 1735 /
DL 1830 | | | + +| | | | | | | | | | +|--------------------------------------------------------------------|-------|-----------------------------|--------|------------------------------|------------------------|------------------------|---------|------------------------------| +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | +| Test Settings for a DC_20A_n7A Configuration | | | | | | | | | +| 1 4 | 20 | UL 851 /
DL 810 | | | n7 | UL 2512 /
DL 2632 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_ 4 | +| Test Settings for a DC_20A_n8A Configuration | | | | | | | | | +| 1 4 | 20 | UL 849.5 /
DL 808.5 | | | n8 | UL 892.5 /
DL 937.5 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | +| Test Settings for a DC_20A_n78A Configuration | | | | | | | | | +| 1 8 | 20 | Mid | | | n78 | Mid | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_ 1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 20 | Mid | | | n78 | UL/DL
3387.99 | | | +| | QPS K | QPSK | 20 MHz | All RBs /
REFSENS_ENDC_ 1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 3 4 | 20 | UL 850 /
DL 809 | | | n78 | UL/DL
3358.995 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_ 4 | +| Test Settings for a DC_21A_n28A Configuration | | | | | | | | | +| 1 4 | 21 | UL
1457.5 /
DL 1505.5 | | | n28 | UL 713 / DL
780.5 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_ENDC_ 4 | +| Test Settings for a DC_21A_n79A Configuration (PC2 and PC3) | | | | | | | | | +| 1 5 | 21 | DL 1503.4 | | | n79 | UL/DL
4510.2 | | | +| | N/A | QPSK | 15 MHz | All RBs / 0 | DFT-s-
OFDM
QPSK | QPSK | 100 MHz | All RBs /
REFSENS_ENDC_ 2 | +| 2 9 | 21 | DL 1503.4 | | | n79 | UL/DL 4800 | | | +| | N/A | QPSK | 15 MHz | All RBs / 0 | DFT-s-
OFDM
QPSK | QPSK | 100 MHz | All RBs /
REFSENS_ENDC_ 2 | +| 3 4 | 21 | UL
1457.5 /
DL 1505.5 | | | n79 | UL/DL
4420.5 | | | +| | QPS K | QPSK | 5 MHz | All RBs /
REFSENS_ENDC_ 4 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 40 MHz | All RBs /
REFSENS_ENDC_ 4 | +| Test Settings for a DC_25A_n41A Configuration | | | | | | | | | +| 1 6 | 25 | High | | | n41 | Low | | | + +| | | | | | | | | | +|----------------|------|------|--------|-------------|--------------|--------------|---------|----------------------------| +| | QPSK | QPSK | 10 MHz | All RBs / 0 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_EN DC_3 | +| 2 6 | 25 | High | | | n41 | Low | | | +| | QPSK | QPSK | 15 MHz | All RBs / 0 | N/A | QPSK | 100 MHz | All RBs / REFSSENS_EN DC_3 | +| | | | | | | | | | +| 3 6 | 25 | High | | | n41 | Mid | | | +| | QPSK | QPSK | 20 MHz | All RBs / 0 | CP-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_EN DC_3 | + +###### **Test Settings for a DC\_26A\_n41A Configuration** + +| | | | | | | | | | +|----------------|------|----------|--------|----------------------------|--------------|--------------|---------|----------------------------| +| 1 3 | 26 | High | | | n41 | UL/DL 2524.5 | | | +| | QPSK | QPSK | 15 MHz | All RBs / REFSSENS_END C_1 | N/A | CP-OFDM QPSK | 50 MHz | All RBs / 0 | +| 2 8 | 26 | High | | | n41 | UL/DL 2572 | | | +| | QPSK | QPSK | 15 MHz | All RBs / REFSSENS_END C_1 | N/A | QPSK | 50 MHz | All RBs / 0 | +| 3 4 | 26 | UL 839 | | | n41 | UL/DL 2562 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSSENS_END C_4 | CP-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSSENS_EN DC_4 | +| 4 5 | 26 | DL 886.6 | | | n41 | UL/DL 2660 | | | +| | QPSK | QPSK | 15 MHz | All RBs / REFSSENS_LTE | CP-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_EN DC_2 | + +###### **Test Settings for a DC\_26A\_n77A/DC\_26A\_n78A Configuration** + +| | | | | | | | | | +|----------------|------|----------|--------|----------------------------|--------------|----------------|---------|----------------------------| +| 1 3 | 26 | High | | | n77/n78 | UL/DL 3366 | | | +| | QPSK | QPSK | 15 MHz | All RBs / REFSSENS_END C_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 26 | High | | | n77/n78 | UL/DL 3446.01 | | | +| | QPSK | QPSK | 15 MHz | All RBs / REFSSENS_END C_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 3 4 | 26 | UL 836.5 | | | n77/n78 | UL/DL 3391.005 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSSENS_END C_4 | CP-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSSENS_EN DC_4 | + +###### **Test Settings for a DC\_26A\_n79A Configuration** + +| | | | | | | | | | +|------------------|-----|------|--------|-------------|--------------|---------------|--------|----------------------------| +| 1 5 | 26 | High | | | n79 | UL/DL 4432.5 | | | +| | N/A | QPSK | 15 MHz | All RBs / 0 | CP-OFDM QPSK | CP-OFDM QPSK | 60 MHz | All RBs / REFSSENS_EN DC_2 | +| 2 2,9 | 26 | High | | | n79 | UL/DL 4470.51 | | | + +| | | | | | | | | | +|------------------------------------------------------------------------------------------------------------|-------|---------------------|--------|----------------------------|-----------------|----------------|---------|----------------------------| +| | N/A | QPSK | 15 MHz | All RBs / 0 | CP-OFDM QPSK | CP-OFDM QPSK | 60 MHz | All RBs / REFSSENS_EN DC_2 | +| Test Settings for a DC_28A_n5A Configuration | | | | | | | | | +| 1 6 | 28 | High | | | n5 | Low | | | +| | QPS K | QPSK | 20MHz | All RBs / REFSSENS_END C_3 | N/A | CP-OFDM QPSK | 20 MHz | All RBs / 0 | +| Test Settings for a DC_28A_n77A/DC_28A_n78A Configuration
(Test ID 4 only apply to DC_28A_n77A) | | | | | | | | | +| 1 3 | 28 | Low | | | n77/n78 | UL/DL 3540 | | | +| | QPS K | QPSK | 10 MHz | All RBs / REFSSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 2 8 | 28 | Low | | | n77/n78 | Low | | | +| | QPS K | QPSK | 10 MHz | All RBs / REFSSENS_ENDC_1 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | +| 3 4 | 28 | UL 705.5 / DL 760.5 | | | n77/n78 | UL/DL 3582.495 | | | +| | QPS K | QPSK | 5 MHz | All RBs / REFSSENS_ENDC_4 | CP-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSSENS_END C_4 | +| 4 5 | 28 | Low | | | n77 | UL/DL 3815.01 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | CP-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_END C_2 | +| Test Settings for a DC_30A_n66A Configuration | | | | | | | | | +| 1 6 | 30 | Low | | | n66 | High | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / REFSSENS_EN DC_3 | +| Test Settings for a DC_30A_n77A Configuration (PC2 and PC3) | | | | | | | | | +| 1 4 | 30 | UL 2310 | | | n77 | UL/DL 3487.5 | | | +| | QPS K | QPSK | 5 MHz | All RBs / REFSSENS_END C_4 | CP-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSSENS_EN DC_4 | +| Test Settings for a DC_38A_n78A Configuration | | | | | | | | | +| 1 6 | 38 | DL High | | | n78 | UL Low | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20 MHz | All RBs / REFSSENS_EN DC_3 | +| Test Settings for a DC_40A_n78A Configuration | | | | | | | | | +| 1 5 | 40 | Mid | | | n78 | UL/DL 3525 | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20 MHz | All RBs / REFSSENS_EN DC_2 | +| 2 9 | 40 | Low | | | n78 | Mid | | | +| | QPS K | QPSK | 20 MHz | All RBs / REFSSENS_END C_2 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_EN DC_2 | +| Test Settings for a DC_41A_n77A/DC_41A_n78A Configuration | | | | | | | | | +| 1 5 | 41 | Low | | | n77/n78 | UL/DL 3750 | | | + +| | | | | | | | | | +|----------------|------|------|--------|----------------------------|-----------------|--------------|---------|----------------------------| +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_EN DC_2 | +| 2 6 | 41 | High | | | n77/n78 | Low | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 100 MHz | All RBs / REFSSENS_EN DC_3 | +| 3 6 | 41 | High | | | n77/n78 | Low | | | +| | QPSK | QPSK | 20MHz | All RBs / REFSSENS_END C_3 | N/A | CP-OFDM QPSK | 100 MHz | All RBs / 0 | + +###### **Test Settings for a DC\_48A\_n66A Configuration** + +| | | | | | | | | | +|----------------|------|------------|--------|----------------------------|-----------------|-------------------|--------|----------------------------| +| 1 3 | 48 | UL/DL 3555 | | | n66 | UL 1760 MHZ | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / REFSSENS_EN DC_1 | +| 2 3 | 48 | UL/DL 3565 | | | n66 | UL 1770 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / REFSSENS_EN DC_1 | +| 3 8 | 48 | UL/DL 3600 | | | n66 | UL1760 | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / REFSSENS_EN DC_1 | +| 4 4 | 48 | UL/DL 3630 | | | n66 | UL 1715 / DL 2115 | | | +| | QPSK | QPSK | 20 MHz | All RBs / REFSSENS_END C_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSSENS_EN DC_4 | + +###### **Test Settings for a DC\_66A\_n2A Configuration** + +| | | | | | | | | | +|--------------------|------|------------------|-------|----------------------------|-----------------|-----------------------|-------|----------------------------| +| 1 4, 10 | 66 | UL1775 / DL2175 | | | n2 | UL 1855 / DL 1935 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSSENS_END C_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSSENS_EN DC_4 | +| 2 4, 10 | 66 | UL 1750/ DL 2150 | | | n2 | UL 1883.3 / DL 1963.3 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSSENS_END C_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSSENS_EN DC_4 | + +###### **Test Settings for a DC\_66A\_n5A Configuration** + +| | | | | | | | | | +|----------------|------|------------------|-------|----------------------------|-----------------|----------------|-------|----------------------------| +| 1 4 | 66 | UL 1721/ DL 2121 | | | n5 | UL 838/ DL 883 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSSENS_END C_4 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / REFSSENS_EN DC_4 | + +###### **Test Settings for a DC\_66A\_n25A Configuration** + +| | | | | | | | | | +|----------------|------|------------------|-------|------------------------|------------|------------------|-------|-----------------------| +| 1 4 | 66 | UL 1775/ DL 2175 | | | n25 | UL 1855/ DL 1935 | | | +| | QPSK | QPSK | 5 MHz | All RBs / REFSSENS_END | DFT-s-OFDM | CP-OFDM | 5 MHz | All RBs / REFSSENS_EN | + +| | | | | | | | | | +|--------------------------------------------------------------------|------|-------------------------|--------|---------------------------------|--------------------|-------------------------|---------|---------------------------------| +| | | | | C_4 | QPSK | QPSK | | DC_4 | +| 2 4 | 66 | UL 1712.5/
DL 2112.5 | | | n25 | UL 1912.5/
DL 1992.5 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_EN
DC_4 | +| 3 4 | 66 | UL 1750/
DL 2150 | | | n25 | UL 1883.3/
DL 1963.3 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_EN
DC_4 | +| Test Settings for a DC_66A_n41A Configuration (PC2 and PC3) | | | | | | | | | +| 1 6 | 66 | High | | | n41 | Low | | | +| | N/A | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 100 MHz | All RBs /
REFSENS_EN
DC_3 | +| Test Settings for a DC_66A_n71A Configuration | | | | | | | | | +| 1 4 | 66 | UL 1750/
DL 2150 | | | n71 | UL 675/
DL 629 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_EN
DC_4 | +| Test Settings for a DC_66A_n77A Configuration | | | | | | | | | +| 1 3 | 66 | UL 1720 | | | n77 | UL/DL
3440.01 | | | +| | QPSK | QPSK | 20 | All RBs /
REFSENS_END
C_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 66 | UL 1720 | | | n77 | UL/DL 3410 | | | +| | QPSK | QPSK | 20 | All RBs /
REFSENS_END
C_1 | N/A | CP-OFDM
QPSK | 20 MHz | All RBs / 0 | +| 3 8 | 66 | UL Mid | | | n77 | UL/DL Mid | | | +| | QPSK | QPSK | 20 | All RBs /
REFSENS_END
C_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 4 4 | 66 | UL 1775/
DL 2175 | | | n77 | UL/DL
3949.995 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_EN
DC_4 | +| 5 4 | 66 | UL
1760 /
DL 2160 | | | n77 | UL/DL 3720 | | | +| | QPSK | QPSK | 5 MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_EN
DC_4 | +| Test Settings for a DC_66A_n78A Configuration | | | | | | | | | +| 1 3 | 66 | UL 1755 | | | n78 | UL/DL 3510 | | | +| | QPSK | QPSK | 20 MHz | All RBs /
REFSENS_END
C_1 | N/A | CP-OFDM
QPSK | 100 MHz | All RBs / 0 | +| 2 3 | 66 | UL 1755 | | | n78 | UL/DL 3480 | | | +| | QPSK | QPSK | 20 MHz | All RBs / | N/A | CP-OFDM | 20 MHz | All RBs / 0 | + +| | | | | | | | | | +|----------------------------------------------------|------|--------------------|----------|---------------------------------|--------------------|--------------------|--------|---------------------------------| +| | | | | REFSENS_END
C_1 | | QPSK | | | +| 3 4 | 66 | UL 1730/
DL2130 | | | n78 | UL/DL 3660 | | | +| | QPSK | QPSK | 5
MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
REFSENS_EN
DC_4 | +| Test Settings for DC_71A_n2A Configuration | | | | | | | | | +| 1 3 | 71 | UL 665.5 | | | n2 | DL 1987.5 | | | +| | QPSK | QPSK | 5MHz | All RBs /
REFSENS_END
C_1 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs / 0 | +| 2 3 | 71 | UL 673 | | | n2 | DL1980 | | | +| | QPSK | QPSK | 20 MHz | All RBs /
REFSENS_END
C_1 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 20 MHz | All RBs / 0 | +| 3 5 | 71 | Low | | | n2 | UL 1881 | | | +| | QPSK | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 20 MHz | All RBs /
REFSENS_EN
DC_2 | +| 4 9 | 71 | High | | | n2 | UL 1881 | | | +| | QPSK | QPSK | 20 MHz | All RBs / 0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 20 MHz | All RBs /
REFSENS_EN
DC_2 | +| Test Settings for DC_71A_n66A Configuration | | | | | | | | | +| 1 4 | 71 | UL 675/
DL 629 | | | n66 | UL1750/
DL 2150 | | | +| | QPSK | QPSK | 5
MHz | All RBs /
REFSENS_END
C_4 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
REFSENS_EN
DC_4 | + +NOTE 1: REFSSENS\_LTE refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.3-2 of TS 36.521-1 [10]. +REFSENS\_NR refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.2.4.1-3 of TS 38.521-1 [8]. +REFSENS\_ENDC\_1 refers to the Uplink RB allocation for reference sensitivity exceptions due to UL harmonic interference according to table 7.3B.2.0.3.1-2. +REFSENS\_ENDC\_2 refers to the Uplink RB allocation for reference sensitivity exceptions due to receiver harmonic mixing according to table 7.3B.2.0.3.2-2. +REFSENS\_ENDC\_3 refers to the Uplink RB allocation for reference sensitivity exceptions due to cross band isolation according to table 7.3B.2.0.3.4-2. +REFSENS\_ENDC\_4 refers to the Uplink RB allocation for reference sensitivity exceptions due to dual uplink operation for ENDC according to table 7.3B.2.0.3.5.1-1 for PC3 and table 7.3B.2.0.3.5.1-1a for PC2. + +NOTE 2: Void + +NOTE 3: Test ID with UL harmonic exception + +NOTE 4: Test ID with 2UL intermodulation exception + +NOTE 5: Test ID with UL receiver harmonic mixing + +NOTE 6: Test ID with UL cross band isolation + +NOTE 7: Void + +NOTE 8: Test ID with UL harmonic exception avoided + +NOTE 9: Test ID with UL receiving harmonic mixing exception avoided + +NOTE 10: Only applicable to UEs not supporting UE capability *singleUL-Transmission*. + +NOTE 11: Test ID with Cross band isolation exception avoided, which is only applicable to DC\_1\_n3, DC\_3\_n1 and DC\_3\_n84. + +NOTE 12: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. + +NOTE 13: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +NOTE 14: If the NR frequency does not match to a valid NR-ARFCN, apply the closest NR frequency with a valid NR-ARFCN. + +NOTE 15: The test points are executed only when UEs support simultaneous Rx/Tx capability as indicated in Table A.4.3.2B.2.3.1-2 of TS 38.508-2. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +4. NR downlink signals are initially set up according to Annex C.0, C.1, C.2, C.3.1, and uplink signals according to Annex G.0, G.1, G.2, and G.3.1 of TS 38.521-1 [8]. +5. E-UTRA downlink signals are initially set up according to Annex C.0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. +6. The DL and UL Reference Measurement channels are set according to Tables 7.3B.2.3.4.2.1-0 to 7.3B.2.3.4.2.1-6 for E-UTRA CG and NR CG. +7. NR propagation conditions are set according to Annex B.0 of TS 38.521-1 [8]. E-UTRA propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +8. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.3B.2.3.4.2.3. +9. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. Step 9 only applicable to the test configuration in Table 7.3B.2.3.4.2.1-0. + +###### 7.3B.2.3.4.2.2 Test procedure + +For test points in Table 7.3B.2.3.4.2.1-6: + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.3B.2.3.4.2.1-6 on the E-UTRA CC and NR CC. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.3B.2.3.4.2.1-6 on the E-UTRA CC and NR CC. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level for the E-UTRA CC and NR CC to the appropriate REFSENS value defined in Tables 7.3B.2.3.5-1 to 7.3B.2.3.5-4. Send continuously uplink power control "up" commands in the uplink scheduling information to both carriers to ensure the UE transmits PUMAX level for at least the duration of the Throughput measurement. +4. Measure the average throughput of both NR and E-UTRA for a duration sufficient to achieve statistical significance according to Annex H.2 of TS 38.521-1 [8] for NR band, and Annex G.2 of TS 36.521-1 [10] for EUTRA band. + +Non-exception requirements are tested according to LTE anchor agnostic below. + +Same test description as in clause 7.3.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.3.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.3.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.3B.2.3.4.2.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents exceptions for E-UTRA band are according to TS 36.521-1 [10] clause 7.3.4.3 for each network signalling value. Message contents exceptions for NR band are according to TS 38.521-1 [8] clause 7.3.2.4.3 for each network signalling value. + +For test points with NOTE 4 in Table 7.3B.2.3.4.2.1-6, the following message exception applies: + +**Table 7.3B.2.3.4.2.3-1: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 7.3B.2.3.4.2.3-2: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +###### 7.3B.2.3.5 Test requirement + +For inter-band EN-DC configurations affected by reference sensitivity exceptions, when test points without NOTE 8, 9 and 11 in Table 7.3B.2.3.4.2.1-6 are tested, the throughput of each CG shall be $\geq 95\%$ of the maximum throughput for the reference receive power level specified in Table 7.3B.2.3.5-1, Table 7.3B.2.3.5-2, Table 7.3B.2.3.5-3, Table 7.3B.2.3.5-3a, Table 7.3B.2.3.5-4 and Table 7.3B.2.3.5-5 for MSDs due to uplink harmonic, harmonic mixing, cross band isolation for PC3 EN-DC, cross band isolation for PC2 EN-DC, dual uplinks for PC3 EN-DC and dual uplink operation for PC2 EN-DC, respectively. For a given EN-DC combo, if more than one category of MSD applies, UE shall pass all requirement. + +For test points with NOTE 8, 9 or 11 in Table 7.3B.2.3.4.2.1-6, reference sensitivity test requirements are specified in Table 7.3.2.5-1 in TS 38.521-1 [8] for the NR CC, and Table 7.3.5-1 in TS 36.521-1 [10] for E-UTRA CC. + +For non- exception requirements (LTE anchor agnostic approach) of all EN-DC configurations, test requirements for NR carrier are the same as 7.3.2.5 in TS 38.521-1 [8]. + +For the UE which supports inter-band EN-DC, the minimum requirement for reference sensitivity in Table 7.3.2.5-1 of TS 38.521-1 [8] for NR band and Table 7.3.5-1 of TS 36.521-1 [10] for EUTRA band, shall be increased by the amount given in $\Delta R_{IB,c}$ defined in clause 7.3B.3.3 for the applicable two, three, four and five bands operation. + +**Table 7.3B.2.3.5-1: Reference sensitivity due to UL harmonic for EN-DC in NR FR1** + +| UL band | DL band | SCS (kHz ) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 40 MHz (dBm) | 50 MHz (dBm) | 60 MHz (dBm) | 80 MHz (dBm) | 90 MHz (dBm) | +|---------|--------------------------------|------------|-------------|----------------------------|----------------------------|----------------------------|--------------|--------------|----------------------------|----------------------------|-----------------------------|----------------------------|----------------------------| +| 1, 3 | n77 2 | 15 | | -71.4
+TT | -71.4
+TT | -71.3 +TT | | | -71.2
+TT | -71.3
+TT | | | | +| | | 30 | | -71.7
+TT | -71.5
+TT | -71.5 +TT | | | -71.3
+TT | -71.4
+TT | -71.4
+TT | -71.3
+TT | -71.3
+TT | +| | | 60 | | -72.1
+TT | -71.8
+TT | -71.7 +TT | | | -71.5
+TT | -71.5
+TT | -71.5
+TT | -71.4
+TT | -71.4
+TT | +| | n77 3 | 15 | | -94.2
+TT | -92.7
+TT | -91.9 +TT | | | | | | | | +| | | 30 | | -94.5
+TT | -92.8
+TT | -92.1 +TT | | | | | | | | +| | | 60 | | -94.9
+TT | -93.1
+TT | -92.3 +TT | | | | | | | | +| 2 | n77 2 13 | 15 | | -71.4
+TT | -71.4
+TT | -71.3 +TT | | | -71.2
+TT | -71.3
+TT | | | | +| | | 30 | | -71.7
+TT | -71.5
+TT | -71.5 +TT | | | -71.3
+TT | -71.4
+TT | -71.4
+TT | -71.3
+TT | -71.3
+TT | +| | | 60 | | -72.1
+TT | -71.8
+TT | -71.7 +TT | | | -71.5
+TT | -71.5
+TT | -71.5
+TT | -71.4
+TT | -71.4
+TT | +| | n77 3 | 15 | | -94.2
+TT | -92.7
+TT | -91.9 +TT | | | | | | | | +| | | 30 | | -94.5
+TT | -92.8
+TT | -92.1 +TT | | | | | | | | +| | | 60 | | -94.9
+TT | -93.1
+TT | -92.3 +TT | | | | | | | | +| 2 | n78 2 | 15 | | -71.9+T
T | -71.9
+TT | -71.8 +TT | | | -71.7
+TT | -71.8
+TT | | | | +| | | 30 | | -72.2
+TT | -72.0
+TT | -72.0 +TT | | | -71.8
+TT | -71.9
+TT | -71.9
+TT | -71.8
+TT | -71.8
+TT | +| | | 60 | | -72.6
+TT | -72.3
+TT | -72.2 +TT | | | -72.0
+TT | -72.0
+TT | -72.0
+TT | -71.9
+TT | -71.9
+TT | +| 2 | n78 3 | 15 | | -94.7
+TT | -93.2
+TT | -92.4 +TT | | | | | | | | +| | | 30 | | -94.9
+TT | -93.3
+TT | -92.6 +TT | | | | | | | | +| | | 60 | | --95.4
+TT | -93.6
+TT | -92.8 +TT | | | | | | | | +| 3 | n78 2 | 15 | | -71.9
+TT | -71.9
+TT | -71.8 +TT | | | -71.7
+TT | -71.8
+TT | | | | +| | | | | -74.1
+TT 15 | -74.1
+TT 15 | -74.0
+TT 15 | | | -73.9
+TT 15 | -74.0
+TT 15 | | | | +| | | 30 | | -72.2
+TT | -72.0
+TT | -72.0 +TT | | | -71.8
+TT | -71.9
+TT | -71.9
+TT | -71.8
+TT | -71.8
+TT | +| | | | | -74.4
+TT 15 | -74.2
+TT 15 | -74.2
+TT 15 | | | -74.0
+TT 15 | -74.1
+TT 15 | --74.1
+TT 15 | -74.0
+TT 15 | -74.0
+TT 15 | +| | | 60 | | -72.6
+TT | -72.3
+TT | -72.2 +TT | | | -72.0
+TT | -72.0
+TT | -72.0
+TT | -71.9
+TT | -71.9
+TT | +| | | | | -74.8
+TT 15 | -74.5
+TT 15 | -74.4
+TT 15 | | | -74.2
+TT 15 | -74.2
+TT 15 | -74.2
+TT 15 | -74.1
+TT 15 | -74.1
+TT 15 | +| | n78 3 | 15 | | -94.7
+TT | -93.2
+TT | -92.4 +TT | | | | | | | | +| | | | | -96.9
+TT 15 | -95.4
+TT 15 | -94.6
+TT 15 | | | | | | | | +| | | 30 | | -95.0
+TT | -93.3
+TT | -92.6 +TT | | | | | | | | +| | | | | -97.2 | -95.5 | -94.8 | | | | | | | | + +| | | | | | | | | | | | | | | +|----|------------------------------------------|----|--------------|----------------------------|----------------------------|----------------------------|----------|----------|--------------|------------------|------------------|--------------|------------------| +| | | | | +TT 15 | +TT 15 | +TT 15 | | | | | | | | +| | | 60 | | -95.4
+TT | -93.6
+TT | -92.8 +TT | | | | | | | | +| | | | | -97.6
+TT 15 | -95.8
+TT 15 | -95.0
+TT 15 | | | | | | | | +| 5 | n78 | 15 | | -84.2
+TT | -84.4
+TT | | | | -84.2
+TT | -84.4
+TT | | | | +| | | 30 | | -84.3
+TT | -84.5
+TT | -84.4 +TT | | | -84.3
+TT | -84.5
+TT | -84.4
+TT | -84.3
+TT | -84.0
+TT | +| | | 60 | | -84.5
+TT | -84.6
+TT | -84.5 +TT | | | -84.5
+TT | -84.6
+TT | -84.5
+TT | -84.4
+TT | -84.1
+TT | +| 8 | n77 6,7
n78 6,7 | 15 | | -84.5
+TT | -84.4
+TT | -84.2 +TT | | | -84.0
+TT | -83.9
+TT | | | | +| | | 30 | | -84.8
+TT | -84.5
+TT | -84.4 +TT | | | -84.1
+TT | -84.0
+TT | -83.9
+TT | -83.8
+TT | -83.5
+TT | +| | | 60 | | -85.2
+TT | -84.8
+TT | -84.6 +TT | | | -84.3
+TT | -84.1
+TT | -84.0
+TT | -83.9
+TT | -83.6
+TT | +| 8 | n41 | 15 | | -81.8
+TT | -81.7
+TT | -81.7 +TT | | | -81.6
+TT | -81.5
+TT | | | | +| | | 30 | | -82.1
+TT | -81.8
+TT | -81.9 +TT | | | -81.7
+TT | -81.6
+TT | -81.4
+TT | -81.3
+TT | -81.2
+TT | +| | | 60 | | -82.5
+TT | -82.1
+TT | -81.1 +TT | | | -81.9
+TT | -81.7
+TT | -81.6
+TT | -81.3
+TT | -81.2
+TT | +| 12 | n66 | 15 | -89.5
+TT | -88.8
+TT | -88.3
+TT | -87.8 +TT | | | -87.7
+TT | | | | | +| | | 30 | | -89.1
+TT | -88.4
+TT | -88.0 +TT | | | -87.8
+TT | | | | | +| | | 60 | | -89.5
+TT | -88.7
+TT | -88.2 +TT | | | -87.9
+TT | | | | | +| 12 | n77 4,
5 | 15 | | -84.9
+TT | -84.6
+TT | -84.4
+TT | | | -84.4
+TT | -84.
4
+TT | | | | +| | | 30 | | -85.2
+TT | -84.7
+TT | -84.6
+TT | | | -84.5
+TT | -84.
5
+TT | -84.
4
+TT | -84.4
+TT | -84.
4
+TT | +| | | 60 | | -85.6
+TT | -85
+TT | -84.8
+TT | | | -84.7
+TT | -84.
6
+TT | -84.
5
+TT | -84.5
+TT | -84.
5
+TT | +| 12 | n78 | 15 | | -85.4
+TT | -85.1
+TT | -84.9 +TT | -84.6+TT | -84.4+TT | -84.9
+TT | -84.9
+TT | | | | +| | | 30 | | -85.7
+TT | -85.2
+TT | -85.1 +TT | -84.7+TT | -84.5+TT | -85.0
+TT | -85.0
+TT | -84.9
+TT | -84.9
+TT | -84.9
+TT | +| | | 60 | | -86.1
+TT | -85.5
+TT | -85.3 +TT | -84.9+TT | -84.6+TT | -85.2
+TT | -85.1
+TT | -85.0
+TT | -85.0
+TT | -85.0
+TT | +| 13 | n77 4,
5 | 15 | | -84.9
+TT | -84.6
+TT | -84.4
+TT | | | -84.4
+TT | -84.
4
+TT | | | | + +| | | | | | | | | | | | | | | +|-----------|------------------------------------------|----|--------------|--------------|---------------|---------------|--|--------------|--------------|------------------|------------------|--------------|------------------| +| | | 30 | | -85.2
+TT | -84.7
+TT | -84.6
+TT | | | -84.5
+TT | -84.
5
+TT | -84.
4
+TT | -84.4
+TT | -84.
4
+TT | +| | | 60 | | -85.6
+TT | -85
+TT | -84.8
+TT | | | -84.7
+TT | -84.
6
+TT | -84.
5
+TT | -84.5
+TT | -84.
5
+TT | +| 14 | n77 4.5 5 | 15 | | -84.9
+TT | -84.6
+TT | -84.4
+TT | | | -84.4
+TT | -84.
4
+TT | | | | +| | | 30 | | -85.2
+TT | -84.7
+TT | -84.6
+TT | | | -84.5
+TT | -84.
5
+TT | -84.
4
+TT | -84.4
+TT | -84.
4
+TT | +| | | 60 | | -85.6
+TT | -85
+TT | -84.8
+TT | | | -84.7
+TT | -84.
6
+TT | -84.
5
+TT | -84.5
+TT | -84.
5
+TT | +| 18,
19 | n77 4.5
n78 4.5 | 15 | | -84.9
+TT | -84.6
+TT | -84.4 +TT | | | -84.4
+TT | -84.4
+TT | | | | +| | | 30 | | -85.2
+TT | -84.7
+TT | -84.6 +TT | | | -84.5
+TT | -84.5
+TT | -84.4
+TT | -84.4
+TT | -84.4
+TT | +| | | 60 | | -85.6
+TT | -85.0
+TT | -84.8 +TT | | | -84.7
+TT | -84.6
+TT | -84.5
+TT | -84.5
+TT | -84.5
+TT | +| 21 | n28 | 15 | -96.0
+TT | -93.0
+TT | -91.0
+TT | -88.3 +TT | | -76.0
+TT | | | | | | +| | | 30 | | -93.1
+TT | -91.1
+TT | -89.5 +TT | | -76.1
+TT | | | | | | +| 28 | n77 4.5
n78 4.5 | 15 | | -84.9
+TT | -84.6
+TT | -84.4 +TT | | | -84.4
+TT | -84.4
+TT | | | | +| | | 30 | | -85.2
+TT | -84.7
+TT | -84.6 +TT | | | -84.5
+TT | -84.5
+TT | -84.4
+TT | -84.4
+TT | -84.4
+TT | +| | | 60 | | -85.6
+TT | -85.0
+TT | -84.8 +TT | | | -84.7
+TT | -84.6
+TT | -84.5
+TT | -84.5
+TT | -84.5
+TT | +| 20 | n77 6.7
n78 6.7 | 15 | | -84.5
+TT | -84.4
+TT | -84.2 +TT | | | -83.1
+TT | | | | | +| | | 30 | | -84.8
+TT | -84.5
+TT | -84.4 +TT | | | -83.2
+TT | | | | | +| | | 60 | | -85.2
+TT | -84.8
+TT | -84.6 +TT | | | -83.4
+TT | | | | | +| 26 | n41 | 15 | | -84.5
+TT | -84.6
+TT | -84.4 +TT | | | -83.6
+TT | -83.3
+TT | 3.9
+TT | 3.1
+TT | 2.7
+TT | +| | | 30 | | -84.8
+TT | -84.7
+TT | -84.6 +TT | | | -83.7
+TT | -83.4
+TT | -83.0
+TT | -82.5
+TT | -82.4
+TT | +| | | 60 | | -85.2
+TT | -85.0
+TT | -84.8 +TT | | | -83.9
+TT | -83.5
+TT | -83.2
+TT | -82.5
+TT | -82.4
+TT | +| 26 | n77 6.7
n78 6.7 | 15 | | -85.0
+TT | -84.9
+TT | -84.7 +TT | | | -83.6
+TT | -84.6
+TT | | | | +| | | 30 | | -85.3
+TT | -85.0+T
T | -84.9 +TT | | | -83.7
+TT | -84.7
+TT | -84.7
+TT | -84.6
+TT | -84.6
+TT | +| | | 60 | | -85.7
+TT | --85.3
+TT | --85.1
+TT | | | -83.9
+TT | -84.8
+TT | -84.8
+TT | -84.7
+TT | -84.7
+TT | +| 26 | n77 4.5 | 15 | | -84.9
+TT | -84.6
+TT | -84.4 +TT | | | -84.4
+TT | -84.4
+TT | | | | + +| | | | | | | | | | | | | | | +|-----|--------------------------------|-----|------------------|--------------|--------------|--------------|--|--|--------------|------------------|------------------|--------------|------------------| +| | | 30 | | -85.2
+TT | -84.7
+TT | -84.6 +TT | | | -84.5
+TT | -84.5
+TT | -84.4
+TT | -84.4
+TT | -85.6
+TT | +| | | 60 | | -85.6
+TT | -85.0
+TT | -84.8 +TT | | | -84.7
+TT | -84.6
+TT | -84.5
+TT | -84.5
+TT | -85.7
+TT | +| n28 | 1 8,9,10 | N/A | -89.1 | -88.7 | -88.3 | -88.0 | | | | | | | | +| 71 | n2 11 | 15 | -93.
4
+TT | -93.8
+TT | -92.3
+TT | -91.2
+TT | | | | | | | | +| | | 30 | | -94.1
+TT | -92.4
+TT | -91.4
+TT | | | | | | | | +| | | 60 | | -94.5
+TT | -92.7
+TT | -91.6
+TT | | | | | | | | +| 71 | n2 12 | 15 | -96.
3
+TT | -93.8
+TT | -92.3
+TT | -91.2
+TT | | | | | | | | +| | | 30 | | -94.1
+TT | -92.4
+TT | -91.4
+TT | | | | | | | | +| | | 60 | | -94.5
+TT | -92.7
+TT | -91.6
+TT | | | | | | | | +| n71 | 2 11 | N/A | -92.7 | -93.3 | -91.8 | -90.7 | | | | | | | | +| n71 | 2 12 | N/A | -95.6 | -93.3 | -91.8 | -90.7 | | | | | | | | +| n71 | 7 | N/A | -82.7 | -82.6 | -82.4 | -82.3 | | | | | | | | +| 66 | n77 2 13 | 15 | | -71.4
+TT | -71.4
+TT | -71.3
+TT | | | -71.2
+TT | -71.
3
+TT | | | | +| | | 30 | | -71.7
+TT | -71.5
+TT | -71.5
+TT | | | -71.3
+TT | -71.
4
+TT | -71.
4
+TT | -71.3
+TT | -71.
3
+TT | +| | | 60 | | -72.1
+TT | -71.8
+TT | -71.7
+TT | | | -71.5
+TT | -71.
5
+TT | -71.
5
+TT | -71.4
+TT | -71.
4
+TT | +| | n77 3 | 15 | | -94.2
+TT | -92.7
+TT | -91.9
+TT | | | | | | | | +| | | 30 | | -94.5
+TT | -92.8
+TT | -92.1
+TT | | | | | | | | +| | | 60 | | -94.9
+TT | -93.1
+TT | -92.3
+TT | | | | | | | | +| 66 | n78 2 | 15 | | -71.9
+TT | -71.9
+TT | -71.8 +TT | | | -71.7
+TT | -71.8
+TT | | | | +| | | 30 | | -72.2+TT | -72.0
+TT | -72.0 +TT | | | -71.8
+TT | -71.9
+TT | -71.9
+TT | -71.8
+TT | -71.8
+TT | +| | | 60 | | -72.6
+TT | -72.3
+TT | -72.2 +TT | | | -72.0
+TT | -72.0
+TT | -72.0
+TT | -71.9
+TT | -71.9
+TT | +| | n78 3 | 15 | | -94.7
+TT | -93.2
+TT | -92.4 +TT | | | | | | | | + +| | | | | | | | | | | | | | | +|-----|---------------------|-----|-------|--------------|--------------|-----------|--|--|--|--|--|--|--| +| | | 30 | | -95.0
+TT | -93.3
+TT | -92.6 +TT | | | | | | | | +| | | 60 | | -95.4
+TT | -93.6
+TT | -92.8 +TT | | | | | | | | +| n66 | 48 2, 13 | N/A | -70.7 | -70.6 | -70.8 | -70.8 | | | | | | | | +| n66 | 48 3 | N/A | -96.1 | -93.6 | -92.3 | -91.6 | | | | | | | | + +NOTE 1: Void. + +NOTE 2: The requirements should be verified for UL EARFCN or NR ARFCN of the aggressor (lower) band (superscript LB) such that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the lower band. + +NOTE 3: The requirements are only applicable to channel bandwidths no larger than 20 MHz and with a carrier frequency at MHz offset from in the victim (higher) band with $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ , where $f_{UL}^{LB}$ and the channel bandwidth configured in the aggressor (lower) and victim (higher) bands in MHz, respectively. + +NOTE 4: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (lower) band for which the 5th transmitter harmonic is within the downlink transmission bandwidth of a victim (higher) band. + +NOTE 5: The requirements should be verified for UL EARFCN of the aggressor (lower) band (superscript LB) such that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the lower band. + +NOTE 6: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (lower) band for which the 4th transmitter harmonic is within the downlink transmission bandwidth of a victim (higher) band. + +NOTE 7: The requirements should be verified for UL EARFCN of the aggressor (lower) band (superscript LB) such that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with carrier frequency in the victim (higher) band in MHz and the channel bandwidth configured in the lower band. + +NOTE 8: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of a low band for which the 3rd transmitter harmonic is within the downlink transmission bandwidth of a high band. + +NOTE 9: The requirements should be verified for UL EARFCN of a low band (superscript LB) such that in MHz and $F_{UL\_low}^{LB} + BW_{Channel}^{LB} / 2 \leq f_{UL}^{LB} \leq F_{UL\_high}^{LB} - BW_{Channel}^{LB} / 2$ with the carrier frequency of a high band in MHz and the channel bandwidth configured in the low band. + +NOTE 10: Applicable for the operations with 2 or 4 antenna ports supported in the band with carrier aggregation configured. + +NOTE 11: These requirements apply when the lower edge frequency of the 5 MHz uplink channel in Band 71 is located at or below 668 MHz and the downlink channel in Band 2 is located with its upper edge at 1990 MHz. + +NOTE 12: These requirements apply when the lower edge frequency of the 10 MHz, 15 MHz, or 20 MHz uplink channel in Band 71 is located at or below 668 MHz and the downlink channel in Band 2 is located with its upper edge at 1990 MHz. + +NOTE 13: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (lower) band for which the 2nd transmitter harmonic is within the downlink transmission bandwidth of a victim (higher) band within a range $\Delta F_{HD}$ above and below the edge of this downlink transmission bandwidth. The value $\Delta F_{HD}$ depends on the EN-DC band combination: $\Delta F_{HD} = 10$ MHz for DC\_1\_n77, DC\_2\_n48, DC\_2\_n77, DC\_42\_n3, DC\_48\_n25, DC\_48\_n66, DC\_66\_n48, DC\_66\_n77, DC\_3\_n77, DC\_3\_n78, DC\_11\_n28 and DC\_28\_n50, DC\_28\_n51, DC\_66\_n78, DC\_25\_n77, DC\_25\_n78. + +NOTE 14: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 15: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +NOTE 16: Void + +NOTE 17: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +**Table 7.3B.2.3.5-1a: Test Tolerance (TT) for RX sensitivity level** + +| $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 6.0\text{ GHz}$ | +|------------------------|-----------------------------------------| +| 0.7 dB | 1.0 dB | + +Reference sensitivity exceptions due to receiver harmonic mixing for EN-DC in NR FR1, are specified in Table 7.3B.2.3.5-2 with uplink configuration specified in Table 7.3B.2.3.4.2.1-3a to Table 7.3B.2.3.4.2.1-3k for each specific EN-DC combination scenario. + +**Table 7.3B.2.3.5-2: Reference sensitivity due to receiver harmonic mixing for PC3 EN-DC in NR FR1** + +| UL band | DL band | SCS (kHz) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 40 MHz (dBm) | 50 MHz (dBm) | 60 MHz (dBm) | 80 MHz (dBm) | 90 MHz (dBm) | 100 MHz (dBm) | +|---------|------------------|-----------|---------------------|---------------------|---------------------|---------------------|--------------|--------------|--------------|--------------|--------------|--------------|---------------| +| 2 | n71 4 | 15 | -70.4
+TT | -70.4
+TT | -70.4
+TT | -70.4
+TT | | | | | | | | +| | | 30 | | -70.7
+TT | -70.7
+TT | -71.8
+TT | | | | | | | | +| | | 60 | | -72.4
+TT | -72.7
+TT | -77.0
+TT | | | | | | | | +| n2 | 71 | N/A | -69.7 | -69.9 | -70.1 | -71.2 | | | | | | | | +| n41 | 26 4 | N/A | -72.5 | -69.5 | -69.5 | N/A | | | | | | | | +| n77 | 2 | N/A | -91.2 | -89.3 | -88.5 | -87.6 | | | | | | | | +| | | | -93.9 10 | -92 10 | -91.2 10 | -90.3 10 | | | | | | | | +| n77 | 13 | N/A | | -65.3 | -65.3 | | | | | | | | | +| n77 | 12 | N/A | -65.3 | -65.3 | | | | | | | | | | +| n77 | 41 8 | N/A | -86.9 | -83.9 | -82.1 | -80.9 | N/A | N/A | N/A | N/A | N/A | N/A | | +| n77 | 14 | N/A | -65.3 | -65.3 | | | | | | | | | | +| n77 | 28 2 | N/A | -69.8 | -69.8 | -69.8 | -68.3 | | | | | | | | +| n78 | 3 | N/A | -90.6 | -89.3 | -88.5 | -87.6 | | | | | | | | +| | | | -93.3 10 | -92.0 10 | -91.2 10 | -90.3 10 | | | | | | | | +| n78 | 40 | N/A | -86.9 | -83.9 | -82.1 | -80.9 | | | | | | | | +| n78 | 41 8 | N/A | -86.9 | -83.9 | -82.1 | -80.9 | N/A | N/A | N/A | N/A | N/A | N/A | | +| n79 | 19 2 | N/A | -69.8 | -69.8 | -69.8 | | | | | | | | | +| n79 | 21 4 | N/A | -60.0 | -60.0 | -60.0 | | | | | | | | | +| n79 | 26 2 | N/A | -69.8 | -69.8 | -69.8 | N/A | N/A | N/A | N/A | N/A | N/A | | N/A | + +NOTE 1: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (higher) band for which the mixing product due to harmonic of victim (lower) band LO with leakage of aggressor (higher) band is within the downlink transmission bandwidth of a victim (lower) band. + +NOTE 2: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 3: Void. + +NOTE 4: The requirements should be verified for DL EARFCN or NR-ARFCN of the victim (lower) band (superscript LB) such that $f_{DL}^{LB} = \lceil f_{UL}^{HB} / 0.3 \rceil 0.1$ with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 5: Void. + +NOTE 6: Void. + +NOTE 7: The requirements should be verified for DL EARFCN of the victim (higher) band (superscript HB) such that with the DL carrier frequency in the higher band and the UL carrier frequency in the lower band, both in MHz. + +NOTE 8: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 9: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 10: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +**Table 7.3B.2.3.5-2a: Reference sensitivity due to receiver harmonic mixing for PC2 EN-DC in NR FR11** + +| UL band | DL band | SCS (kHz) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 40 MHz (dBm) | 50 MHz (dBm) | 60 MHz (dBm) | 80 MHz (dBm) | 90 MHz (dBm) | 100 MHz (dBm) | +|---------|-----------------|-----------|---------------------|-------------------|---------------------|---------------------|--------------|--------------|--------------|--------------|--------------|--------------|---------------| +| n77 | 2 | N/A | -88.2 | -86.3 | -85.5 | -84.6 | | | | | | | | +| | | | -90.9 10 | -89 10 | -88.2 10 | -87.3 10 | | | | | | | | +| n77 | 13 2 | N/A | | -62.3 | -62.3 | | | | | | | | | +| n77 | 12 | N/A | -65.3 | -65.3 | | | | | | | | | | +| n77 | 14 | N/A | -65.3 | -65.3 | | | | | | | | | | +| n79 | 19 2 | N/A | -66.8 | -66.8 | -66.8 | | | | | | | | | +| n79 | 21 4 | N/A | -57.0 | -57.0 | -57.0 | | | | | | | | | + +NOTE 1: These requirements apply when there is at least one individual RE within the uplink transmission bandwidth of the aggressor (higher) band for which the mixing product due to harmonic of victim (lower) band LO with leakage of aggressor (higher) band is within the downlink transmission bandwidth of a victim (lower) band. + +NOTE 2: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 3: Void. + +NOTE 4: The requirements should be verified for DL EARFCN or NR-ARFCN of the victim (lower) band (superscript LB) such that $f_{DL}^{LB} = \lfloor f_{UL}^{HB} / 0.3 \rfloor 0.1$ with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 5: Void. + +NOTE 6: Void. + +NOTE 7: The requirements should be verified for DL EARFCN of the victim (higher) band (superscript HB) such that with the DL carrier frequency in the higher band and the UL carrier frequency in the lower band, both in MHz. + +NOTE 8: The requirements should be verified for DL EARFCN of the victim (lower) band (superscript LB) such that with the DL carrier frequency in the lower band and the UL carrier frequency in the higher band, both in MHz. + +NOTE 9: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 10: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +Reference sensitivity exceptions due to cross band isolation for EN-DC in NR FR1, are specified in Table 7.3B.2.3.5-3 with uplink configuration specified in Table 7.3B.2.3.4.2.1-4a to Table 7.3B.2.3.4.2.1-4n. + +**Table 7.3B.2.3.5-3: Reference sensitivity exceptions due to cross band isolation for PC3 EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band | | | | | | | | | | | | | | | | +|---------------------------------------------------------------|------------------|-----------|--------------|---------------------------|---------------------------|-------------------------|--------------|---------------------------|---------------------------|---------------------------|---------------------------|--------------|---------------------------|---------------------------|---------------------------| +| UL band | DL band | SCS (kHz) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 40 MHz (dBm) | 50 MHz (dBm) | 60 MHz (dBm) | 70 MHz (dBm) | 80 MHz (dBm) | 90 MHz (dBm) | 100 MHz (dBm) | +| n1 | 3 | N/A | -93.3 | -91 | -89.5 | -88.5 | | | | | | | | | | +| 1 | n3 | 15 | -94
+TT | -91.6
+TT | -90.1
+TT | -89.1
+TT | -88.1
+TT | -87.4
+TT | -86.2
+TT | | | | | | | +| 1 | n41 | 30 | | -89.0
+TT | -87.0
+TT | -85.9
+TT | | -83.9
+TT | -82.6
+TT | -81.6
+TT | -80.8
+TT | | -79.5
+TT | -79.0
+TT | -78.6
+TT | +| 3 | n41 | 30 | | -94.4
+TT | -92.4
+TT | -91.3
+TT | | -89.3
+TT | -88.0
+TT | -87
+TT | -86.2
+TT | | -84.9
+TT | -84.4
+TT | -84.0
+TT | +| | | | | -97.1
+TT 4 | -95.1
+TT 4 | -94
+TT 4 | | -92.0
+TT 4 | -90.7
+TT 4 | -89.7
+TT 4 | -88.9
+TT 4 | | -87.6
+TT 4 | -87.1
+TT 4 | -86.7
+TT 4 | +| n5 | 28 | 15 | -93.3 | -91.8 | -90.8 | -90 | | | | | | | | | | +| n41 | 1 | 15 | -90.2 | -87.2 | -85.4 | -84.2 | | | | | | | | | | +| n41 | 2 | N/A | -96.7 | -93.7 | -91.9 | -90.7 | | | | | | | | | | +| n41 | 3 | N/A | 3 | n41 | 30 | 3 | | | | | | | | | | +| n41 | 25 | N/A | -95.2 | -92.2 | -90.4 | -89.2 | | | | | | | | | | +| n77 | 41 1 | N/A | -92.8 | -89.8 | -88.0 | -86.8 | | | | | | | | | | +| n41 | 66 | N/A | -95.3 | -92.3 | -90.5 | -89.3 | | | | | | | | | | +| n41 | n77 3 | 30 | | -87.3
+TT | -85.3
+TT | -84.1
+TT | | | -82.9
+TT | -82.9
+TT | -82.9
+TT | | -82.1
+TT | -81.7
+TT | -81.3
+TT | +| n30 | n66 | 15 | -91.2
+TT | -88.0
+TT | -86.2
+TT | -85.0
+TT | | | | -81.8
+TT | | | | | | +| n78 | 7 1 | N/A | -93.5 | -90.5 | -88.7 | -87.5 | | | | | | | | | | +| n78 | 38 | N/A | -96.7 | -93.7 | -91.9 | -90.7 | | | | | | | | | | +| n78 | 41 1 | N/A | -92.8 | -89.8 | -88.0 | -86.8 | | | | | | | | | | +| n41 | n78 | 30 | | -87.8
+TT | -85.8
+TT | -84.6
+TT | | | -83.4
+TT | -83.4
+TT | -83.4
+TT | | -82.6
+TT | -82.2
+TT | -81.8
+TT | + +NOTE 1: Applicable only when harmonic mixing MSD for this combination is not applied. + +NOTE 2: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 3: The requirement is modified by -0.5 dB when the assigned UE channel bandwidth is confined within 3300 - 3800 MHz. + +NOTE 4: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +**Table 7.3B.2.3.5-3a: Reference sensitivity exceptions due to cross band isolation for PC2 EN-DC in NR FR1** + +| E-UTRA or NR Band / Channel bandwidth of the affected DL band | | | | | | | | | | | | | | | | +|---------------------------------------------------------------|---------|-----------|--------------------|---------------------------|---------------------------|---------------------------|--------------|---------------------------|---------------------------|---------------------------|---------------------------|--------------|---------------------------|---------------------------|---------------------------| +| UL band | DL band | SCS (kHz) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 40 MHz (dBm) | 50 MHz (dBm) | 60 MHz (dBm) | 70 MHz (dBm) | 80 MHz (dBm) | 90 MHz (dBm) | 100 MHz (dBm) | +| 3 | n41 | 30 | | -94.4
+TT 3 | -92.4
+TT | -91.3
+TT | | -89.3
+TT | -88.0
+TT | -87.0
+TT | -86.2
+TT | | -84.9
+TT | -84.4
+TT | -84.0
+TT | +| | | | | -97.1
+TT 3 | -95.1
+TT 3 | -94.1
+TT 3 | | -92.0
+TT 3 | -90.7
+TT 3 | -89.7
+TT 3 | -88.9
+TT 3 | | -87.6
+TT 3 | -87.1
+TT 3 | -86.7
+TT 3 | +| n41 | 3 | N/A | -94.0 | -91.0 | -89.2 | -88.0 | | | | | | | | | | +| | | | -96.7 3 | -93.7 3 | -91.9 3 | -90.7 3 | | | | | | | | | | + +NOTE 1: Applicable only when harmonic mixing MSD for this combination is not applied. + +NOTE 2: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 3: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +Reference sensitivity exceptions due to dual uplink operation for EN-DC in NR FR1, are specified in Table 7.3B.2.3.5-4 with uplink configuration specified in Table 7.3B.2.3.4.2.1-6. + +**Table 7.3B.2.3.5-4: Reference sensitivity exceptions due to dual uplink operation for PC3 EN-DC in NR FR1 (two bands)** + +| NR or E-UTRA Band / Channel bandwidth | | | | | | | | | | +|---------------------------------------------------------------------------------------|------------------|-----------|--------------------|--------------|--------------|--------------|--------------|-------------------|-------------| +| EN-DC Configuration | EUTRA or NR band | SCS (kHz) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 40 MHz (dBm) | IMD order | Duplex mode | +| DC_1A_n3A | 1 | N/A | [-76.3] | - | - | - | - | IMD3 | FDD | +| | n3 | 15 | REFSENS | - | - | - | - | N/A | TDD | +| DC_1A_n8A | 1 | N/A | -93.3 | - | - | - | - | IMD4 | FDD | +| | n8 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_1A_n77A | 1 | N/A | -69.5 | - | - | - | - | IMD2 3 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_1A_n77A | 1 | N/A | -91.3 | - | - | - | - | IMD4- | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_1A_n78A | 1 | N/A | -91.3 | - | - | - | - | IMD4 | FDD | +| | n78 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_2A_n66A | 2 | N/A | -77.3 | - | - | - | - | IMD3 | | +| | n66 | 15 | REFSENS | - | - | - | - | N/A | | +| DC_2A_n66A | 2 | N/A | REFSENS | - | - | - | - | N/A | | +| | n66 | 15 | -95.5 +TT | - | - | - | - | IMD5 | | +| DC_2A_n77A
DC_2A_n77(2A)
DC_2A-2A_n77A
DC_2A_n77(2A)
DC_2A-2A_n77(
2A) | 2 | N/A | -71.3 | - | - | - | - | IMD2 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| | 2 | N/A | -89.3 | - | - | - | - | IMD4 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| | 2 | N/A | -92.3 | - | - | - | - | IMD5 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_2A_n78A | 2 | N/A | -71.3 7 | - | - | - | - | IMD2 3 | FDD | +| | n78 | 15 | - | REFSENS | - | - | - | - | TDD | +| DC_2A_n78A | 2 | N/A | -89.3 7 | - | - | - | - | N/A | FDD | +| | n78 | 15 | - | REFSENS | - | - | - | IMD4 3 | TDD | +| DC_3A_n1A | 3 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n1 | 15 | -74.0+TT | - | - | - | - | IMD3 | FDD | +| DC_3A_n5A | 3 | N/A | - | -89.3 | - | - | - | IMD4 | FDD | +| | n5 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| | 3 | N/A | - | REFSENS | - | - | - | N/A | FDD | +| | n5 | 15 | -74.0+TT | - | - | - | - | IMD23 | FDD | +| DC_3A_n7A | 3 | N/A | REFSENS | - | - | - | - | - | | +| | n7 | 15 | - | -84.6 | - | - | - | - | | + +| | | | | +TT 5 | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-----|--------------------|------------------|---|----|---|-------------------|-----| +| DC_3A_n8A | 3 | N/A | - | REFSEN
S | - | - | - | N/A | FDD | +| | n8 | 15 | -88.3 | - | - | - | - | IMD4 3 | FDD | +| | 3 | N/A | - | -86.9 | - | - | - | IMD5 | FDD | +| | n8 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_3A_n41A | 3 | N/A | -88.1 | - | - | - | - | IMD4 | FDD | +| | | | -90.8 7 | - | - | - | - | | | +| DC_3A_n77A,
DC_3A_n77(2A),
DC_3A_SUL_n7
7A-n80A,
DC_3A_n78A,
DC_3A_SUL_n7
8A-n80A,
DC_3A_n78(2A),
DC_3C_n78A
DC_3C_n78(2A) | 3 | N/A | -70.3 | - | - | - | - | IMD2 3 | FDD | +| | | | -70.6 7 | - | - | - | - | | | +| | n77, n78 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_3A_n77A,
DC_3A_n77(2A),
DC_3C_n77A,
DC_3C_n77(2A),
DC_3A_SUL_n7
7A-n80A,
DC_3A_n78A,
DC_3A_SUL_n7
8A-n80A,
DC_3A_n78(2A),
DC_3C_n78A
DC_3C_n78(2A) | 3 | N/A | -88.3 | - | - | - | - | IMD4 3 | FDD | +| | | | -88.3 7 | - | - | - | - | | | +| | n77, n78 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_5A_n66A | 5 | N/A | -67.3 | - | - | - | - | IMD2 3 | FDD | +| | n66 | | REFSENS | - | - | - | - | N/A | FDD | +| DC_5A_n77A 8e | 5 | N/A | -89 | - | - | - | - | IMD4 | FDD | +| | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| | 5 | N/A | -91.8 | - | - | - | - | IMD5 | FDD | +| | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_5A_n78A | 5 | N/A | -89.0 | - | - | - | - | IMD4 | FDD | +| | n78 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_7A_n3A | 7 | N/A | - | -81.3 | - | - | - | IMD4 | FDD | +| | n3 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_7A_n5A | 7 | N/A | | REFSEN
S | - | - | - | N/A | FDD | +| | n5 | 15 | -86.0+TT | - | - | - | - | IMD3 3 | FDD | +| DC_7A_n66A | 7 | N/A | - | -79.3 | - | - | - | IMD4 | FDD | +| | n66 | 15 | REFSENS | - | - | - | - | N/A | TDD | +| DC_7A_n77A | 7 | N/A | -90.2 | - | - | - | - | IMD4 | FDD | +| | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_8A_n1A | 8 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n1 | 15 | -94.0 + TT | - | - | -- | - | IMD4 | FDD | +| DC_8A_n3A | 8 | N/A | -88.3 | - | - | - | - | IMD4 3 | FDD | + +| | | | | | | | | | | +|---------------------------------------|----------|-----|-----------|-------------|---|---|-------------|-------------------|-----| +| | n3 | 15 | - | REFSEN
S | - | - | - | N/A | FDD | +| | 8 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n3 | 15 | - | -87.4+ TT | - | - | - | IMD5 | FDD | +| DC_8A_n20A | n20 | 15 | -71.3 | - | - | - | - | IMD3 | FDD | +| | 8 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n20 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| | 8 | N/A | -71.3 | - | - | - | - | IMD3 | FDD | +| DC_8A_n41A | 8 | N/A | -84.2 | - | - | - | - | IMD3 3 | FDD | +| | n41 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_8A_n77A | 8 | N/A | -88.0 | - | - | - | - | IMD4 | FDD | +| DC_8A_n78A
DC_8A-
SUL_n78A-n81A | n77, n78 | 15 | - | REFSEN
S | - | - | - | H4 | TDD | +| DC_12A_n77A | 12 | N/A | -90.8 | - | - | - | - | IMD5 | FDD | +| DC_12A_n77(2A
) | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_12_n78 | 12 | N/A | -90.8 | - | - | - | - | IMD5 | FDD | +| | n78 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_13A_n77A | 13 | N/A | -90.8 | - | - | - | - | IMD5 | FDD | +| | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_14A_n77A | 14 | N/A | -90.8 | - | - | - | - | IMD5 | FDD | +| DC_14A_n77(2A) | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_20A_n3A | 20 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n3 | 15 | -93.0 +TT | - | - | - | - | IMD4 | FDD | +| | 20 | N/A | -87.3 | - | - | - | - | IMD4 | FDD | +| | n3 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_20_n7 | 20 | N/A | -84.3 | - | - | - | - | IMD3 | FDD | +| | n7 | 15 | - | REFSEN
S | - | - | - | N/A | FDD | +| DC_20_n8 | 20 | N/A | -71.3 | - | - | - | - | IMD3 | FDD | +| | n8 | 15 | -71.3 | - | - | - | - | IMD3 | FDD | +| DC_20A_n78A, | 20 | N/A | -74.6 | - | - | - | - | IMD4 4 | FDD | +| DC_20A-
SUL_n78A-n82A | n78 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_21A_n79A | 21 | N/A | -80.9 | - | - | - | - | IMD3 | FDD | +| | n79 | 15 | - | - | - | - | REFSEN
S | N/A | TDD | +| CA_28A_n77A, | 28 | N/A | -92.3 | - | - | - | - | IMD5 | FDD | +| CA_28A_n78A, | | | | | | | | | | +| DC_28A-
SUL_n78A-n83A | n77, n78 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_30A_n77A | 30 | N/A | -92.8 | - | - | - | - | IMD3 | FDD | +| DC_30A_n77(2A
) | n77 | 15 | - | REFSEN
S | - | - | - | N/A | TDD | +| DC_48A_n66A | 48 | N/A | - | REFSEN
S | - | - | - | N/A | TDD | +| | n66 | 15 | -95.5 +TT | - | - | - | - | IMD5 | FDD | +| DC_66A_n2A | 66 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n2 | 15 | -78.0+TT | - | - | - | - | IMD3 | FDD | +| | 66 | N/A | -94.8 | - | - | - | - | IMD5 | FDD | +| | n2 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_66A_n5A | 66 | N/A | -68.8 | - | - | - | - | IMD2 3 | FDD | + +| | | | | | | | | | | +|------------------------------------------------------------------------------------|-----|-----|-----------|---------|---|---|---|------|-----| +| | n5 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_66A_n25A | 66 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n25 | 15 | -76.5+TT | - | - | - | - | IMD3 | FDD | +| | 66 | N/A | -75.8 | - | - | - | - | IMD3 | FDD | +| | n25 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| | 66 | N/A | -94.8 | - | - | - | - | IMD5 | FDD | +| | n25 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_66A_n71A | 66 | N/A | -93.8 | - | - | - | - | IMD4 | FDD | +| | n71 | 15 | REFSENS | - | - | - | - | N/A | FDD | +| DC_66A_n77A
DC_66A_n77(2A
)
DC_66A-66A_n7
7A
DC_66A-66A_n7
7(2A) | 66 | N/A | -67.8 | - | - | - | - | IMD2 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| | 66 | N/A | -93.8 | - | - | - | - | IMD5 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_66A_n78A | 66 | N/A | -93.8 | - | - | - | - | IMD5 | FDD | +| | n78 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_71A_n66A | 71 | N/A | REFSENS | - | - | - | - | N/A | FDD | +| | n66 | 15 | -94.5 +TT | - | - | - | - | IMD4 | FDD | + +NOTE 1: E-UTRA carrier shall be set to min(+20 dBm, PCMAX\_L\_E-UTRA,c) and NR carrier shall be set to min(+20 dBm, PCMAX\_L,f,CNR) as defined in clause 6.2B.4.1.3. + +NOTE 2: RBSTART = 0 + +NOTE 3: This band is subject to IMD5 also which MSD is not specified. + +NOTE 4: The symbol "REFSENS" in this table refers to the reference sensitivity values for single carrier specified in Table 7.3.5-1 of TS 36.521-1 [10] for 2 antenna port E-UTRA band, Table 7.3\_1.5-1 of TS 36.521-1 [10] for 4 antenna port E-UTRA band, Table 7.3.2.5-1 for 2 antenna port NR band and Table 7.3.2.5-2 for 4 antenna port NR band. + +NOTE 5: Void + +NOTE 6: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 7: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +NOTE 8: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +**Table 7.3B.2.3.5-5: Reference sensitivity exceptions due to dual uplink operation for PC2 EN-DC in NR FR1 (two bands)** + +| NR or E-UTRA Band / Channel bandwidth | | | | | | | | | | +|------------------------------------------------------------|------------------|-----------|---------------------|--------------|--------------|--------------|--------------|-------------------|-------------| +| EN-DC Configuration | EUTRA or NR band | SCS (kHz) | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 40 MHz (dBm) | IMD order) | Duplex mode | +| DC_1A_n78A | 1 | N/A | REFSENS-17.8 | - | - | - | - | IMD4 | | +| | n78 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_2A_n77A
DC_2A-2A_n77A
DC_2A_n77C
DC_2A-2A_n77C | 2 | N/A | -65.2 | - | - | - | - | IMD2 | FDD | +| | | | -65.15 7 | | | | | | | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| | 2 | N/A | -78.2 | - | - | - | - | IMD4 9 | FDD | +| | | | -78.15 7 | | | | | | | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_3A_n41A | 3 | N/A | -77.9 | - | - | - | - | IMD4 | FDD | +| | | | -80.6 7 | - | - | - | - | | | +| | n41 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_3A_n78A | 3 | N/A | -64.4 | - | - | - | - | IMD2 | FDD | +| | | | -67.1 7 | - | - | - | - | | | +| | n78 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_3A_n78A | 3 | N/A | -77.8 | - | - | - | - | IMD4 | FDD | +| | | | -80.5 7 | - | - | - | - | | | +| | n78 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_5A_n77A 8 | 5 | N/A | -78.7 | - | - | - | - | IMD4 9 | FDD | +| DC_5A_n77C 8 | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_12A_n77A | 12 | N/A | -84.6 | - | - | - | - | IMD5 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_13A_n77A | 13 | N/A | -80.93 | - | - | - | - | IMD5 | FDD | +| DC_13A_n77C | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_14A_n77A | 14 | N/A | -84.6 | - | - | - | - | IMD5 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_21A_n79A | 21 | N/A | -65.9 | - | - | - | - | IMD3 | FDD | +| | n79 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_30A_n77A | 30 | N/A | -81.4 | - | - | - | - | IMD4 | FDD | +| | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| DC_66A_n77A | 66 | N/A | -64.47 | - | - | - | - | IMD2 | FDD | + +| | | | | | | | | | | +|---------------------|-----|-----|--------|---------|---|---|---|------|-----| +| DC_66A-66A_n77A | n77 | 15 | - | REFSENS | - | - | - | N/A | TDD | +| | 66 | N/A | -87.53 | - | - | - | - | IMD5 | FDD | +| DC_66A-66A-66A_n77A | | | | | | | | | TDD | +| DC_66A_n77C | | | | | | | | | | +| DC_66A-66A_n77C | n77 | 15 | - | REFSENS | - | - | - | N/A | | +| DC_66A-66A-66A_n77C | | | | | | | | | | + +NOTE 1: Both of the transmitters shall be set min(+20 dBm, PCMAX\_L,c) as defined in clause 6.2.5A. In case Single UL is allowed and the UE only indicates support of "Single UL" the output power of the active UL shall be set at PCMAX\_L,c or set to the maximum output power according to the UE power scaling capability. + +NOTE 2: RBSTART = 0 + +NOTE 3: This band is subject to IMD5 also which MSD is not specified. + +NOTE 4: The symbol "REFSENS" in this table refers to the reference sensitivity values for single carrier specified in Table 7.3.5-1 of TS 36.521-1 [10] for 2 antenna port E-UTRA band, Table 7.3\_1.5-1 of TS 36.521-1 [10] for 4 antenna port E-UTRA band, Table 7.3.2.5-1 for 2 antenna port NR band and Table 7.3.2.5-2 for 4 antenna port NR band. + +NOTE 5: For UEs only indicating support of Single UL, this requirement is verified with non-simultaneous uplink transmissions on the E-UTRA and NR CGs. + +NOTE 6: TT is the same as defined in Table 7.3B.2.3.5-1a. + +NOTE 7: Applicable only if operation with 4 antenna ports is supported in the band with EN-DC configured. + +NOTE 8: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. + +NOTE 9: This band is subject to IMD5 also which MSD is not specified. + +##### 7.3B.2.3\_1 Reference sensitivity for EN-DC within FR1 (>2 CCs) + +###### 7.3B.2.3\_1.1 Reference sensitivity for EN-DC within FR1 (3 CCs) + +**Editor's note:** The test requirements section of this test case contains some EN-DC configurations that have no test points defined meaning these cannot be tested. + +**Editor's note:** For EN-DC configurations with >1NR CC, test points in Table 7.3B.2.3\_1.1.4.1-0 only need to be tested if the configuration is a max NR CC of the UE, where detailed execution rules are FFS. + +###### 7.3B.2.3\_1.1.1 Test purpose + +To verify the ability of UE that support EN-DC configurations to receive data with a given average throughput for a specified reference measurement channel, under conditions of low signal level, ideal propagation and no added noise when no CA exceptions are allowed and single carrier requirements apply whenever possible. A UE unable to meet the throughput requirement under these conditions will decrease the effective coverage area. + +###### 7.3B.2.3\_1.1.2 Test applicability + +This test applies to all types of NR UE release 15 and forward supporting 3CC EN-DC. + +###### 7.3B.2.3\_1.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.3B.2.0 + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 7.3B.2.3\_1.1.4 Test description + +###### 7.3B.2.3\_1.1.4.1 Initial conditions + +Same initial conditions as in clause 7.3B.2.3.4.1 with following exceptions: + +The initial test configurations for E-UTRA band and NR band consist of environmental conditions, test frequencies, and channel bandwidths and RB allocations for exceptional test scenarios are specified in Table 7.3B.2.3\_1.1.4.1-0 and 7.3B.2.3\_1.1.4.1-1. + +**Table 7.3B.2.3\_1.1.4.1-0: Test Configuration Table for all EN-DC configurations for FR1 non-exception requirements** + +| Initial Conditions | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | +| NR Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1,
E-UTRA Test Frequencies as specified in TS 36.508 [11] clause 4.3.1 | DC_XA_nYA-nZA
Mid range for MCG and SCG

DC_XA_nYC:
Mid range for XA
Low range, High Range for nXC

DC_(n)XCA:
Low range, High Range

DC_XA_nY(2A):
TBD | | | +| NR Test Channel Bandwidths as specified in TS 38.508-1 [6] clause 4.3.1
E-UTRA Test Channel Bandwidths as specified in TS 36.508 [11] clause 4.3.1. | Refer to "NR N RB " and "E-UTRA N RB " columns | | | +| Network signalling value | NS_01 by default, exceptions listed in Table 7.3.3-3, dependent on PCC Band | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | +| Test Parameters for DC Configurations | | | | +| ID | PCC – E-UTRA | SCC1 – EUTRA/NR | SCG -NR | + +| Band | Range | N RB | | Band | Range | N RB | | Band | Range | N RB | | | +|--------------------------------------------------------------------------------------------------------------------|--------|-----------------|----------------------|-----------------------|--------|-----------------|----------------------------------------------------------|-------------|-----------------|-----------------|------------------|----------------------| +| UL MOD | DL MOD | CH BW | DLalloc/
UL alloc | UL MOD | DL MOD | UL/DL Ch BW | DLalloc/
ULalloc | UL MOD | DL MOD | UL/DL Ch BW | DLalloc/UL alloc | | +| Test Settings for a DC_(n)XCA Configuration (Intra-band contiguous EN-DC with LTE CA)– Note 2 | | | | | | | | | | | | | +| 1 | X | default | Highest | All RBs / REFSENS_LTE | X | default | Highest | All RBs / 0 | nX | default | Highest | All RBs / REFSENS_NR | +| | QPSK | QPSK | | | N/A | QPSK | | | DFT-s-OFDM QPSK | CP-OFDM QPSK | | | +| Test Settings for a DC_XC_nXA Configuration (Intra-band non-contiguous EN-DC with LTE CA)– Note 3 | | | | | | | | | | | | | +| | | | | | | | No test required, LTE 1CC fallback is tested in 7.3B.2.2 | | | | | | +| Test Settings for a DC_XA-XA_nXA/ DC_XA_(n)XAA Configuration (Intra-band non-contiguous EN-DC with LTE CA)– Note 3 | | | | | | | | | | | | | +| | | | | | | | No test required, LTE 1CC fallback is tested in 7.3B.2.2 | | | | | | +| Test Settings for a DC_XA_nYC Configuration (Inter-band EN-DC with NR CA, 2 bands) – Note 1,5 | | | | | | | | | | | | | +| 1 | X | default | 5 MHz | 0/0 | nY | default | Highest | All RBs / 0 | nY | default | Highest | All RBs / REFSENS_NR | +| | N/A | N/A | | | N/A | CP-OFDM QPSK | | | DFT-s-OFDM QPSK | CP-OFDM QPSK | | | +| Test Settings for a DC_XA_nY(2A) Configuration (Inter-band EN-DC with NR CA, 2 bands) – Note 1,5 | | | | | | | | | | | | | +| 1 | X | default | 5 MHz | 0/0 | nY | default | Highest | All RBs / 0 | nY | default | Highest | All RBs / REFSENS_NR | +| | N/A | N/A | | | N/A | CP-OFDM QPSK | | | DFT-s-OFDM QPSK | CP-OFDM QPSK | | | +| Test Settings for a DC_XC_nYA, DC_XA-XA_nYA Configuration (Inter-band EN-DC with LTE CA, 2 bands) – Note 3 | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------|-----|-----|-------|-----|-----------------|--------------|---------|----------------------|----------------------------------------------------------|--------------|---------|----------------------|--|--| +| | | | | | | | | | No test required, LTE 1CC fallback is tested in 7.3B.2.3 | | | | | | +| Default Test Settings for a DC_XA-YA_nZA Configuration (Inter-band EN-DC with LTE CA, 3 bands) – Note 3 | | | | | | | | | | | | | | | +| | | | | | | | | | No test required, LTE 1CC fallback is tested in 7.3B.2.3 | | | | | | +| Default Test Settings for a DC_XA_nYA-nZA Configuration (Inter-band EN-DC with NR CA, 3 bands) – Note 1, 5 | | | | | | | | | | | | | | | +| 1 | X | Mid | 5 MHz | 0/0 | nY | default | Highest | All RBs / 0 | nZ | default | Highest | All RBs / REFSENS_NR | | | +| | N/A | N/A | | | N/A | CP-OFDM QPSK | | | DFT-s-OFDM QPSK | CP-OFDM QPSK | | | | | +| 2 | X | Mid | 5 MHz | 0/0 | nY | default | Highest | All RBs / REFSENS_NR | nZ | default | Highest | All RBs / 0 | | | +| | N/A | N/A | | | DFT-s-OFDM QPSK | CP-OFDM QPSK | | | N/A | CP-OFDM QPSK | | | | | + +Note 1: LTE anchor agnostic configuration + Note 2: Not LTE anchor agnostic configuration due to exception requirement for intra-band contiguous CA in clause 7.4B, 7.5B, 7.6B.2, 7.6B.3, 7.6B.4, 7.7B, 7.8B, 7.9B test cases + Note 3: LTE anchor agnostic configuration with LTE CA where LTE CA fallback to 1CC is sufficient to test + Note 4: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. + Note 5: For UE supporting multiple EN-DC configurations with the same NR CA combination, only one EN-DC configuration is tested. + Note 6: REFSENS\_LTE refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.3-2 of TS 36.521-1 [10]. + REFSENS\_NR refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.2.4.1-3 of TS 38.521-1 [8]. + +**Table 7.3B.2.3\_1.1.4.1-1: Test Configuration Table for EN-DC configurations affected by Reference sensitivity exceptions** + +| Initial Conditions | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | +| NR Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1,
E-UTRA Test Frequencies as specified in TS 36.508 [11] clause 4.3.1 | EN-DC configurations containing the following band combinations:
20-n78: Mid in band 20 and Mid in band 78. | | | +| NR Test Channel Bandwidths as specified in TS 38.508-1 [6] clause 4.3.1
E-UTRA Test Channel Bandwidths as specified in TS 36.508 [11] clause 4.3.1. | Refer to "NR N RB " and "E-UTRA N RB " columns | | | +| Network signalling value | NS_01 by default, exceptions listed in Table 7.3.3-3, dependent on PCC Band | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest SCS per Channel Bandwidth | | | +| Test Parameters for DC Configurations | | | | +| ID | PCC – E-UTRA | SCC1 – EUTRA/NR | CG -NR | + +| | Band | Range | N RB | | Band | Range | N RB | | Band | Range | N RB | | +|---------------------------------------------------------------------------------------------------------------------------|--------|-----------------------|-----------------|-------------------|--------|---------------|----------------------------------------------------------|------------------|--------|-------------------------|-----------------|-------------------| +| | UL MOD | DL MOD | CH BW | DLalloc/ UL alloc | UL MOD | DL MOD | UL/DL Ch BW | DLalloc/ ULalloc | UL MOD | DL MOD | UL/DL Ch BW | DLalloc/ UL alloc | +| Default Test Settings for a DC_XA_nYC, DC_XA_nY(2A) Configuration (Inter-band EN-DC with NR CA, 2 bands) – Note 7 | | | | | | | | | | | | | +| | | | | | | | No test required, NR 1CC fallback is tested in 7.3B.2.3 | | | | | | +| Default Test Settings for a DC_XC_nYA, DC_XA-XA_nYA Configuration (Inter-band EN-DC with LTE CA, 2 bands) – Note 4 | | | | | | | | | | | | | +| | | | | | | | No test required, LTE 1CC fallback is tested in 7.3B.2.3 | | | | | | +| Default Test Settings for a DC_XA-YA_nZA Configuration (Inter-band EN-DC with LTE CA, 3 bands) – Note 4 | | | | | | | | | | | | | +| | | | | | | | No test required, LTE 1CC fallback is tested in 7.3B.2.3 | | | | | | +| Default Test Settings for a DC_XA_nYA-nZA Configuration (Inter-band EN-DC with NR CA, 3 bands) – Note 7 | | | | | | | | | | | | | +| | | | | | | | No test required, NR 1CC fallback is tested in 7.3B.2.3 | | | | | | +| Test Settings for DC_1A-3A_n28A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1975 / DL 2165 MHz | | | 3 | DL 1818.5 MHz | | | n28 | UL 710.5 / DL 765.5 MHz | | | + +| | | | | | | | | | | | | | +|--------------------------------------------------------|------|-----------------------|-------|-------------------|------|---------------------------|--------|-------------------|-----------------|-------------------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 3 | UL 1780 / DL 1875 MHz | | | 1 | DL 2139 MHz | | | n28 | UL 710.5 / DL 765.5 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_1A-7A_n28A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1935 / DL 2125 MHz | | | 7 | DL 2653 MHz | | | n28 | UL 718 / DL 773 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_1A-3A_n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1950 / DL 2140 MHz | | | 3 | DL 1807.5 MHz | | | n77 | 3757.5 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 1 | UL 1950 / DL 2140 MHz | | | 3 | DL 1870 MHz | | | n77 | 3980 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 3 | 1 | DL 2140 MHz | | | 3 | UL 1775 MHz / DL 1870 MHz | | | n77 | 3915 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-3A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1950 / DL 2140 | | | 3 | DL 1807.5 MHz | | | n78 | 3757.5 MHz | | | + +| | | | | | | | | | | | | | +|--|--|-----|--|--|--|--|--|--|--|--|--|--| +| | | MHz | | | | | | | | | | | +|--|--|-----|--|--|--|--|--|--|--|--|--|--| + +| | | | | | | | | | | | | | +|---------------------------------------------------------------|------|------------------------------------|-------|----------------------|------|-----------------------------|-------|----------------------|--------------------|-----------------|--------|----------------------| +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| 2 | 1 | DL 2125
MHz | | | 3 | UL 1775 /
DL 1870
MHz | | | n78 | 3725 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| Test Settings for DC_1A-3A_n79A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | DL 2140
MHz | | | 3 | UL 1750 /
DL 1845
MHz | | | n79 | 4860 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 40 MHz | All RBs /
All RBs | +| Test Settings for DC_1A-5A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | DL 2122
MHz | | | 5 | UL 829 / DL
874 MHz | | | n78 | 3780 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| 2 | 1 | UL 1975 /
DL 2165
MHz | | | 5 | DL 885 MHz | | | n78 | 3405 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| Test Settings for DC_1A-7A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL
1977.5 /
DL 2167.5
MHz | | | 7 | DL 2627.5
MHz | | | n78 | 3305 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| 2 | 1 | DL 2140
MHz | | | 7 | UL 2510 /
DL 2630
MHz | | | n78 | 3580 MHz | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------|------|-----------------------|-------|-------------------|------|-------------------------|-------|-------------------|-----------------|---------------------|--------|-------------------| +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 10MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-18A_n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | DL 2120 MHz | | | 18 | UL 825 / DL 870 MHz | | | n77 | 3770 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-19A_n79A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1950 / DL 2140 MHz | | | 19 | DL 882.5 MHz | | | n79 | 4782.5 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / All RBs | +| 2 | 1 | DL 2140 MHz | | | 19 | UL 837.5 / DL 882.5 MHz | | | n79 | 4652.5 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / All RBs | +| Test Settings for DC_1A-20A_n8A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1925 / DL 2115 MHz | | | 20 | DL 805 MHz | | | n8 | UL 910 / DL 955 MHz | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------|------|-----------------------|-------|-------------------|------|---------------------------|-------|-------------------|-----------------|--------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_1A-20A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | DL 2120 MHz | | | 20 | UL 835 / DL 794 MHz | | | n78 | 3790 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 1 | UL 1950 / DL 2140 MHz | | | 20 | DL 810 MHz | | | n78 | 3330 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-21A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 1 | DL 2154.6 MHz | | | 21 | UL 1450.4 / DL 1498.4 MHz | | | n78 | 3605 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 1 | DL 2154.6 MHz | | | 21 | UL 1450.4 / DL 1498.4 MHz | | | n78 | 3647 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 3 | 1 | UL 1950 / DL 2140 MHz | | | 21 | DL 1500 MHz | | | n78 | 3450 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 4 | 1 | UL 1950 / DL 2140 MHz | | | 21 | DL 1500 MHz | | | n78 | 3675 MHz | | | + +| | | | | | | | | | | | | | +|---------------------------------------------------|------|-----------------------|-------|-------------------|------|-------------------------|--------|-------------------|-----------------|-----------------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-28A_n3A – Note 3 | | | | | | | | | | | | | +| 1 | 1 | DL 2139 MHz | | | 28 | UL 710.5 / DL 765.5 MHz | | | n3 | UL 1780 / DL 1875 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_1A_n28A-n78A – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1950 / DL 2140 MHz | | | n78 | 3416 MHz | | | n28 | UL 733 / DL 788 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 1 | UL 1950 / DL 2140 MHz | | | n28 | DL 790 MHz | | | n78 | 3320 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-28A_n78A – Note 3 | | | | | | | | | | | | | +| 1 | 28 | UL 740 / DL 795 MHz | | | 1 | DL 2150 MHz | | | n78 | 3630 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 1 | UL 1970 / DL 2160 | | | 28 | DL 794 MHz | | | n78 | 3352 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-41A_n77A – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1970 / DL 2160 MHz | | | 41 | 2510 MHz | | | n77 | 3400 MHz | | | + +| | | | | | | | | | | | | | +|--------------------------------------------------|------|---------------------------|-------|-------------------|------|---------------------|--------|-------------------|-----------------|---------------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 1 | DL 2140 MHz | | | 41 | 2640 MHz | | | n77 | 3710 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 3 | 1 | UL 1930 / DL 2120 MHz | | | 41 | 2510 MHz | | | n77 | 4150 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_1A-41A_n28A – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1935 / DL 2125 MHz | | | 41 | 2653 MHz | | | n28 | UL 718 / DL 773 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_1A-42A_n79A – Note 3 | | | | | | | | | | | | | +| 1 | 1 | UL 1977.5 / DL 2167.5 MHz | | | 42 | DL 3490 MHz | | | n79 | | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / All RBs | +| Test Settings for DC_2A_n5A-n77A – Note 3 | | | | | | | | | | | | | +| 1 | 2 | UL 1880 / DL 1960 MHz | | | n5 | UL 830 / DL 875 MHz | | | n77 | 3540 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 10 MHz | All RBs / 0 | +| Test Settings for DC_2A-13A_n77A – Note 3 | | | | | | | | | | | | | +| 1 | 2 | DL 1944 MHz | | | 13 | UL 783 / DL 752 MHz | | | n77 | 3510 MHz | | | + +| | | | | | | | | | | | | | +|--------------------------------------------------|------|-----------------------|-------|-------------------|------|-----------------------|-------|-------------------|-----------------|---------------------|--------|-------------------| +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_2A-66A_n5A – Note 3 | | | | | | | | | | | | | +| 1 | 2 | UL 1900 / DL 1980 MHz | | | 66 | UL 1740 / DL 2140 MHz | | | n5 | UL 830 / DL 875 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | QPSK | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_2A-66A_n41A – Note 3 | | | | | | | | | | | | | +| 1 | 2 | UL 1860 / DL 1940 MHz | | | 66 | UL 1715 / DL 2115 MHz | | | n41 | 2685 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_2A-66A_n77A – Note 3 | | | | | | | | | | | | | +| 1 | 2 | UL 1855 / DL 1935 MHz | | | 66 | DL 2115 MHz | | | n77 | 3970 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 2 | UL 1880 / DL 1960 MHz | | | 66 | DL 2140 MHz | | | n77 | 3500 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 3 | 2 | UL 1860 / DL 1940 MHz | | | 66 | DL 2175 MHz | | | n77 | 3915 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 4 | 2 | DL 1960 MHz | | | 66 | UL 1760 / DL 2160 MHz | | | n77 | 3720 MHz | | | + +| | | | | | | | | | | | | | +|------------------------------------------------|------|----------------------|--------|-------------------|------|-------------|--------|-------------------|-----------------|---------------------|--------|-------------------| +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_3A-7A_n5A – Note 3 | | | | | | | | | | | | | +| 1 | 3 | UL 1780/ DL 1875 MHz | | | 7 | DL 2625 MHz | | | n5 | UL 845 / DL 890 MHz | | | +| | QPSK | QPSK | 10 MHz | All RBs / All RBs | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_3A-7A_n8A – Note 3 | | | | | | | | | | | | | +| 1 | 3 | UL 1780/ DL 1875 MHz | | | 7 | DL 2670 MHz | | | n8 | UL 890 / DL 935 MHz | | | + +| QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 10 MHz | All RBs /
0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
All RBs | | +|---------------------------------------------------------|------|---------------------------------|----------------------|-------|---------------------|-----------------------------|----------------|------------------------|-------------------------------|----------------------|------------------------|------------------------| +| Test Settings for DC_3A-7A_n28A – Note 3 | | | | | | | | | | | | | +| 1 | 3 | UL 1712.5 /
DL 1807.5
MHz | | 7 | DL
2682
MHz | | | n28 | UL 743 /
DL 798
MHz | | | | +| | | QPSK | QPSK | | 5 MHz | All RBs /
All RBs | N/A | | QPSK | 10 MHz | All RBs / 0 | DFT-s-
OFDM
QPSK | +| 2 | 7 | UL 2543 /
DL 2663
MHz | | 3 | DL
1832.5
MHz | | | n28 | UL 710.5 /
DL 765.5
MHz | | | | +| | | QPSK | QPSK | | 10 MHz | All RBs /
All RBs | N/A | | QPSK | 5 MHz | All RBs / 0 | DFT-s-
OFDM
QPSK | +| Test Settings for DC_3A-7A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1820
MHz | | | 7 | UL 2565 /
DL 2685
MHz | | | n78 | 3310 MHz | | | +| | | N/A | QPSK | 5 MHz | | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | +| 2 | 3 | DL 1820
MHz | | | 7 | UL 2565 /
DL 2685
MHz | | | n78 | 3475 MHz | | | +| | | N/A | QPSK | 5 MHz | | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | +| Test Settings for DC_3A-8A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1820
MHz | | | 8 | UL 910 / DL
955 MHz | | | n78 | 3640 MHz | | | +| | | N/A | QPSK | 5 MHz | | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | +| Test Settings for DC_3A-19A_n79A Configuration – Note 3 | | | | | | | | | | | | | + +| | | | | | | | | | | | | | +|--------------------------------------------------------|------|--------------------------|-------|----------------------|------|----------------------------|-------|----------------------|------------------------|------------------------|--------|----------------------| +| 1 | 3 | UL 1775 /
DL 1870 MHz | | | 19 | DL 885 MHz | | | n79 | 4435 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 40 MHz | All RBs /
All RBs | +| 2 | 3 | DL 1877.5 MHz | | | 19 | UL 842.5 /
DL 887.5 MHz | | | n79 | 4420 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 40 MHz | All RBs /
All RBs | +| Test Settings for DC_3A-20A_n8A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1860 MHz | | | 20 | UL 840 MHz /
DL 799 | | | n8 | UL 900 / DL
945 MHz | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------|------|------------------------------|----------------------|-------------------|------------------------------|-------|----------------|--------------------|---------------------|--------------|----------------------|-------------------| +| N/A | QPSK | 5 MHz | All RBs /
All RBs | QPSK | QPSK | 5 MHz | All RBs /
0 | DFT-s-OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
All RBs | | +| Test Settings for DC_3A-20A_n28A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1828 MHz | | 20 | UL 852 / DL 811 MHz | | | n28 | UL 728 / DL 783 MHz | | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_3A-20A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1820 MHz | | 20 | UL 845 / DL 804 MHz | | | n78 | 3510 MHz | | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_3A-21A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | UL 1767.5 /
DL 1862.5 MHz | | 21 | DL 1507.5 MHz | | | n78 | 3795 MHz | | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 3 | DL 1862.5 | | 21 | UL 1459.5 /
DL 1507.5 MHz | | | n78 | 3322 MHz | | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_3A-21A_n79A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1869.2 MHz | | 21 | UL 1450.4 /
DL 1498.4 MHz | | | n79 | 4770 MHz | | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40 MHz | All RBs / All RBs | +| Test Settings for DC_3A-28A_n78A Configuration – Note 3 | | | | | | | | | | | | | + +| | | | | | | | | | | | | | +|------------------------------------------------------------------|------|-----------------------|-------|-------------------|-----|-----------------------|--------|-------------|-----------------|-----------------------|--------|-------------------| +| 1 | 28 | UL 740 / DL 760 MHz | | | 3 | UL 1775 / DL 1870 MHz | | | n78 | 3350 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_3A_n28A-n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | UL 1750 / DL 1845 MHz | | | n78 | 3764 MHz | | | n28 | UL 743 / DL 798 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_3A-40A_n1A Configuration – Note 3, 6 | | | | | | | | | | | | | +| 1 | 3 | UL 1735 / DL 1830 MHz | | | 40 | DL 2380 MHz | | | n1A | UL 1950 / DL 2140 MHz | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------|------|-----------------------|-------|-------------------|------|----------|--------|-------------------|-----------------|-------------------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_3A-41A_n28A – Note 3 | | | | | | | | | | | | | +| 1 | 3 | DL 1832.5 MHz | | | 41 | 2543 MHz | | | n28 | UL 710.5 / DL 765.5 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 10 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 3 | UL 1780 / DL 1875 MHz | | | 41 | 2518 MHz | | | n28 | UL 738 / DL 793 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 3 | 3 | UL 1715 / DL 1810 MHz | | | 41 | 2687 MHz | | | n28 | UL 743 / DL 798 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | QPSK | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_3A-41A_n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 3 | UL 1720 / DL 1815 MHz | | | 41 | 2640 MHz | | | n77 | 3900 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 3 | DL 1840 MHz | | | 41 | 2620 MHz | | | n77 | 3400 MHz | | | + +| | | | | | | | | | | | | | +|---------------------------------------------------------------|------|-----------------------|--------|-------------------|------|-----------------------|-------|-------------------|-----------------|-----------------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / 0 | N/A | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_5A-7A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 5 | UL 844 / DL 889 MHz | | | 7 | DL 2645 MHz | | | n78 | 3489 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 5 | DL 879 MHz | | | 7 | UL 2550 / DL 2670 MHz | | | n78 | 3429 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 3 | 5 | DL 875 MHz | | | 7 | UL 2525 / DL 2645 MHz | | | n78 | 3350 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_7A-8A_n3A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2530 / DL 2650 MHz | | | 8 | DL 940 MHz | | | n3 | UL 1735 / DL 1830 MHz | | | +| | QPSK | QPSK | 10 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 7 | DL 2670 MHz | | | 8 | UL 890 / DL 935 MHz | | | n3 | UL 1780 / DL 1875 MHz | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_7A-20A_n1A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2510 / DL 2630 MHz | | | 20 | 800 MHz | | | n1 | UL 1940 / DL 2130 MHz | | | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------|------|-----------------------|--------|-------------------|------|---------------------|--------|-------------------|-----------------|-----------------------|--------|-------------------| +| | N/A | QPSK | 10 MHz | All RBs / 0 | QPSK | QPSK | 10 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_7A-20A_n3A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2543 / DL 2663 MHz | | | 20 | DL 806 MHz | | | n3 | UL 1737 / DL 1832 MHz | | | +| | QPSK | QPSK | 10 MHz | All RBs / All RBs | N/A | QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 7 | DL 2630 MHz | | | 20 | UL 855 / DL 896 MHz | | | n3 | UL 1775 / DL 1870 MHz | | | +| | N/A | QPSK | 10 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_7A-20A_n8A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2565 / DL 2685 MHz | | | 20 | DL 795 MHz | | | n8 | UL 885 / DL 930 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 7 | DL 2640 MHz | | | 20 | UL 840 / DL 799 MHz | | | n8 | UL 900 / DL 945 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 3 | 7 | DL 2624 MHz | | | 20 | UL 857 / DL 816 MHz | | | n8 | UL 910 / DL 955 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_7A-20A_n28A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 20 | UL 842 / DL 801 MHz | | | 7 | DL 2640 MHz | | | n28 | UL 728 / DL 783 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / | N/A | QPSK | 10 MHz | All RBs / | DFT-s- | CP-OFDM | 5 MHz | All RBs / | + +| | | | | | | | | | | | | | +|----------------------------------------------------------------|------|--------------------------|-------|----------------------|------|------------------------|-------|----------------------|------------------------|------------------------|--------|----------------------| +| | | | | All RBs | | | | 0 | OFDM
QPSK | QPSK | | All RBs | +| Test Settings for DC_7A-20A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2560 /
DL 2680 MHz | | | 20 | DL 810 MHz | | | n78 | 3370 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| 2 | 7 | UL 2560 /
DL 2680 MHz | | | 20 | DL 810 MHz | | | n78 | 3435 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| 3 | 7 | DL 2675 MHz | | | 20 | UL 845 / DL
804 MHz | | | n78 | 3520 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| Test Settings for DC_7A-28A_n3A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2543 /
DL 2663 MHz | | | 28 | DL 796 MHz | | | n3 | 1842 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
All RBs | +| 2 | 7 | DL 2685 MHz | | | 28 | UL 745 / DL
800 MHz | | | n3 | 1810 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
All RBs | +| Test Settings for DC_7A-28A_n5A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 7 | UL 2540 /
DL 2660 MHz | | | 28 | DL 776 MHz | | | n5 | UL 829 / DL
874 MHz | | | + +| | | | | | | | | | | | | | +|---|------|-------------|-------|-------------------|------|---------------------|-------|-------------------|-----------------|---------------------|-------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 7 | DL 2630 MHz | | | 28 | UL 730 / DL 785 MHz | | | n5 | UL 840 / DL 874 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | + +###### **Test Settings for DC\_7A-28A\_n78A Configuration – Note 3** + +| | | | | | | | | | | | | | +|---|------|---------------------------|-------|-------------------|------|---------------------|-------|-------------------|-----------------|--------------|--------|-------------------| +| 1 | 7 | UL 2567.5 / DL 2687.5 MHz | | | 28 | DL 782.5 MHz | | | n78 | 3350 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 2 | 7 | UL 2567.5 / DL 2687.5 MHz | | | 28 | DL 782.5 MHz | | | n78 | 3460 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| 3 | 7 | DL 2650 MHz | | | 28 | UL 740 / DL 795 MHz | | | n78 | 3390 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5 MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | + +###### **Test Settings for DC\_7A\_n28A-n78A Configuration – Note 3** + +| | | | | | | | | | | | | | +|---|------|----------------------|-------|-------------------|-----|--------------|--------|-------------|-----------------|---------------------|--------|-------------------| +| 1 | 7 | UL 2565/ DL 2685 MHz | | | n78 | 3310 MHz | | | n28 | UL 745 / DL 800 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 7 | UL 2565/ DL 2685 MHz | | | n28 | DL 800 MHz | | | n78 | 3365 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / | N/A | CP-OFDM | 5 MHz | All RBs / | DFT-s- | CP-OFDM | 10 MHz | All RBs / | + +| | | | | | | | | | | | | | +|-----------------------------------------------------------------|------|---------------------------|-------|----------------------|------|-----------------------------|-------|----------------------|------------------------|--------------------------|--------|----------------------| +| | | | | All RBs | | QPSK | | 0 | OFDM
QPSK | QPSK | | All RBs | +| Test Settings for DC_2A-14A_n66A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 2 | DL 1954
MHz | | | 14 | UL 793 / DL
763 MHz | | | n66 | UL 1770 / DL
2170 MHz | | | +| | N/A | QPSK | 5 MHz | All RBs /
0 | QPSK | QPSK | 5 MHz | All RBs /
All RBs | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
All RBs | +| Test Settings for DC_13A_n2A-n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 13 | UL 782 /
DL 751
MHz | | | n2 | UL 1896 /
DL 1976
MHz | | | n77 | 3460 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | CP-OFDM
QPSK | 10 MHz | All RBs / 0 | +| 2 | 13 | UL 782 /
DL 751
MHz | | | n2 | DL 1960
MHz | | | n77 | 3524 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | QPSK | QPSK | 5 MHz | All RBs /
0 | CP-
OFDM
QPSK | CP-OFDM
QPSK | 10 MHz | All RBs /
All RBs | +| Test Settings for DC_13A-66A_n2A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 13 | UL 782 /
DL 751
MHz | | | 66 | DL 2156
MHz | | | n2 | UL 1860 / DL
1940 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs /
All RBs | N/A | QPSK | 5 MHz | All RBs /
0 | DFT-s-
OFDM
QPSK | CP-OFDM
QPSK | 5 MHz | All RBs /
All RBs | +| Test Settings for DC_13A-66A_n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 13 | UL 782 /
DL 751
MHz | | | 66 | DL 2156
MHz | | | n77 | 3720 MHz | | | + +| | | | | | | | | | | | | | +|-----------------------------------------------------------------|------|------------|-------|-------------------|------|-----------------------|-------|-------------------|-----------------|-----------------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_14A-66A_n2A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 14 | DL 763 MHz | | | 66 | UL 1762 / DL 2162 MHz | | | n2 | UL 1874 / DL 1954 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| Test Settings for DC_18A-41A_n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 18 | DL 865 MHz | | | 41 | 2640 MHz | | | n77 | 3527.5 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10MHz | All RBs / All RBs | +| Test Settings for DC_18A-41A_n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 18 | DL 865 MHz | | | 41 | 2640 MHz | | | n78 | 3527.5 MHz | | | + +| | | | | | | | | | | | | | +|------------------------------------------------------------------|------|-------------------------|-------|-------------------|-----------------|---------------------|-------|---------------------------|-----------------|-----------------------|-------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / 0 | QPSK | QPSK | 5MHz | All RBs / All RBs | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10MHz | All RBs / All RBs | +| Test Settings for DC_19A-21A_n79A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 19 | UL 837.5 / DL 882.2 MHz | | | 21 | DL 1500 MHz | | | n79 | 4850 | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 40MHz | All RBs / All RBs | +| Test Settings for DC_20A_n28A-n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 20 | UL 857 / DL 816 MHz | | | n78 | 3314 MHz | | | n28 | UL 743 / DL 798 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 10MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 20 | UL 837 / DL 796 MHz | | | n28 | UL 744 / DL 799 MHz | | | n78 | 3310 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 5MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10MHz | All RBs / All RBs | +| Test Settings for DC_20A_n28A-n75A Configuration | | | | | | | | | | | | | +| 1 | 20 | Mid | | | n28 | High | | | n75 | DL 1476MHz | | | +| | QPSK | QPSK | 20MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20MHz | All RBs / REFSEN S_ENDC_1 | N/A | CP-OFDM QPSK | 20MHz | All RBs / N/A | +| 2 N
ote
8 | 20 | Mid | | | n28 | Low | | | n75 | High | | | +| | QPSK | QPSK | 20MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 20MHz | All RBs / REFSEN S_ENDC_1 | N/A | CP-OFDM QPSK | 20MHz | All RBs / N/A | +| Test Settings for DC_28A_n7A-n78A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 28 | UL 745 / DL 8005 MHz | | | n78 | 3310 MHz | | | n7 | UL 2565 / DL 2685 MHz | | | + +| | | | | | | | | | | | | | +|-----------------------------------------------------------------|------|-----------------------|-------|-------------------|-----|---------------------|--------|-------------|-----------------|--------------|--------|-------------------| +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 10 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 5 MHz | All RBs / All RBs | +| 2 | 28 | UL 745 / DL 8005 MHz | | | n7 | DL 2650 MHz | | | n78 | 3390 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | CP-OFDM QPSK | 5 MHz | All RBs / 0 | DFT-s-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_66A_n2A-n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 66 | UL 1760 / DL 2160 MHz | | | n2 | DL 1960 MHz | | | n77 | 3720 MHz | | | +| | QPSK | QPSK | 5 MHz | All RBs / All RBs | N/A | QPSK | 5 MHz | All RBs / 0 | CP-OFDM QPSK | CP-OFDM QPSK | 10 MHz | All RBs / All RBs | +| Test Settings for DC_66A_n5A-n77A Configuration – Note 3 | | | | | | | | | | | | | +| 1 | 66 | UL 1770 / DL 2170 MHz | | | n5 | UL 845 / DL 890 MHz | | | n77 | 3460 MHz | | | + + + +###### 7.3B.2.3\_1.1.4.2 Test procedure + +Same as in clause 7.3B.2.3.4.2. + +###### 7.3B.2.3\_1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents exceptions for E-UTRA band are according to TS 36.521-1 [10] clause 7.3.4.3 for each network signalling value. Message contents exceptions for NR band are according to TS 38.521-1 [8] clause 7.3.2.4.3 for each network signalling value. + +For test points with Note 3 in Table 7.3B.2.3\_1.1.4.1-1, the following message exception applies: + +**Table 7.3B.2.3.4.2.3-1: RRCConnectionReconfiguration: nr-Config-r15** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-MaxEUTRA-r15 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +**Table 7.3B.2.3.4.2.3-2: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6] Table 4.6.3-106 | | | | +|--------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 2 UE | +| | 20 | | Power Class 3 UE | + +###### 7.3B.2.3\_1.1.5 Test requirement + +Reference sensitivity test requirements for EN-DC configurations affected by 3 band 2UL intermodulation interference, are specified in Table 7.3B.2.3\_1.1.5-1 and Table 7.3B.2.3\_1.1.5-2 with uplink configuration specified in Table 7.3B.2.3\_1.1.4.1-1. + +Reference sensitivity test requirements for test points in Table 7.3B.2.3\_1.1.4.1-1, are specified in Table 7.3.2.5-1 in TS 38.521-1 [8] for the NR CC. + +**Table 7.3B.2.3\_1.1.5-1: Reference sensitivity exceptions for Scell due to dual uplink operation for EN-DC in NR FR1 (three bands)** + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sin
U
alloy | +|--------------------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|--------------|-------------------| +| DC_1A-3A_n28A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | | N/A | | +| | | 3 | N/A | -92.3 | - | - | - | | IMD5 | | +| | 2 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | | N/A | | +| | | 1 | N/A | -88.3 | - | - | - | | IMD4 | | +| DC_1A-7A_n28A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | | N/A | | +| | | 7 | N/A | - | -64.3 | - | - | | IMD2 | | +| DC_1A-3A_n77A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 3 | N/A | -64.8 | - | - | - | | IMD2 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 3 | N/A | -87.8 | - | - | - | | IMD4 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 1 | N/A | -68.3 | - | - | - | FDD | IMD2 | | +| | | 3 | N/A | REFSENS | - | - | - | | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-3A_n78A
DC_1A-3C_n78A | 1 | 1 | N/A | -91.0 | - | - | - | FDD | IMD4 | | +| | | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 3 | N/A | -65.1 | - | - | - | | IMD2 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 1 | N/A | -96.5 | - | - | - | FDD | IMD5 | | +| | | 3 | N/A | REFSENS | - | - | - | | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-3A_n79A | 1 | 1 | N/A | -95.7 | - | - | - | FDD | IMD5 | | +| | | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| DC_1A-5A_n78A | 1 | 1 | N/A | -91.0 | - | - | - | FDD | IMD4 | | +| | | 5 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 5 | N/A | -89.0 | - | - | - | FDD | IMD4 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 1 | N/A | -81.2 | - | - | - | FDD | IMD3 | | +| | | 5 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 4 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| DC_1A-7A_n78A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 7 | N/A | -88.2 | - | - | - | FDD | IMD4 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | -90.6 | - | - | - | FDD | IMD4 | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sim
U
alloy | +|---------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|--------------|-------------------| +| | | 7 | N/A | - | REFSENS | - | | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-18A_n77A | 1 | 1 | N/A | -82.9 | - | - | - | FDD | IMD3 | | +| | | 18 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-19A_n79A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 19 | N/A | -81.0 | - | - | - | FDD | IMD3 | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| | 2 | 1 | N/A | -91.2 | - | - | - | FDD | IMD4 | | +| | | 19 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| DC_1A-20A_n8A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 20 | N/A | -87.8 | - | - | - | FDD | IMD4 | | +| | | n8 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_1A-20A_n78A | 1 | 1 | N/A | -79.0 | - | - | - | FDD | IMD3 | | +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-20A_n78A | 2 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 20 | N/A | -93.3 | - | - | - | FDD | IMD5 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| ee | 1 | 1 | N/A | -68.7 | - | - | - | FDD | IMD2 | | +| | | 21 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | -95.7 | - | - | - | FDD | IMD5 | | +| | | 21 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 21 | N/A | -67.8 | - | - | - | FDD | IMD2 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 4 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 21 | N/A | -96.4 | - | - | - | FDD | IMD5 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-28A_n3A | 1 | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n3 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | 1 | N/A | -88.3 | - | - | - | FDD | IMD4 | | +| DC_1A_n28A-n78A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | -79.1 | - | - | TDD | IMD3 | | +| | 2 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | n28 | 15 | -94.5 | - | - | - | FDD | IMD5 | | +| DC_1A-28A_n78A | 1 | 1 | N/A | -83.6 | - | - | - | FDD | IMD3 | | +| | | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 28 | N/A | -93.6 | - | - | - | FDD | IMD5 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sin
U
alloy | +|---------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|--------------|-------------------| +| DC_1A-41A_n28A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 41 | N/A | - | -64.3 | - | - | TDD | IMD2 | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_1A-41A_n77A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 41 | N/A | -86.3 | - | - | - | TDD | IMD4 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 1 | N/A | -90.0 | - | - | - | FDD | IMD4 | | +| | | 41 | N/A | REFSENS | - | - | - | TDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 41 | N/A | -93.7 | - | - | - | TDD | IMD5 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_1A-42A_n79A | 1 | 1 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| | | 42 | N/A | -93.2 | - | - | - | TDD | IMD5 | | +| DC_2A_n5A-n77A | 1 | 2 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n5 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | -78.3 | - | - | TDD | IMD3 | | +| DC_2A-13A_n77A | 1 | 2 | N/A | -81.3 | - | - | - | FDD | IMD3 | | +| | | 13 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_2A-14A_n66A | 1 | 2 | N/A | -90.1 | - | - | - | FDD | IMD4 | | +| | | 14 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n66 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_2A-66A_n5A | 1 | 2 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 66 | N/A | -91.6 | - | - | - | FDD | IMD4 | | +| | | n5 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_2A-66A_n41A | 1 | 2 | N/A | -74.4 | - | - | - | FDD | IMD4 | | +| | | 66 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n41 | 15 | REFSENS | - | - | - | TDD | N/A | | +| DC_2A-66A_n77A | 1 | 2 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 66 | N/A | -69.6 | - | - | - | FDD | IMD2 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 2 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 66 | N/A | -88.4 | - | - | - | FDD | IMD4 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 2 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 66 | N/A | -94.8 | - | - | - | FDD | IMD5 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 4 | 2 | N/A | -65.2 | - | - | - | FDD | IMD2 | | +| | | 66 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_3A-5A_n78A | 1 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 5 | N/A | -89.0 | - | - | - | FDD | IMD4 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | 2 | 3 | N/A | -70.3 | - | - | FDD | IMD2 | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sim
U
allow | +|-------------------------------------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-------------------|----------------|--------------------|-------------------| +| | 3 | 5 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | 3 | N/A | -88.3 | - | - | - | FDD | IMD4 | | +| | | | | [TBD] | | | 10.7 5 | | | | +| DC_3A-7A_n5A | 1 | 3 | N/A | - | REFSENS | - | - | FDD | N/A | | +| | | 7 | N/A | - | - 64.3 | - | - | FDD | IMD2 xx | | +| | | n5 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_3A-7A_n28A | 1 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | | N/A | | +| | | 7 | N/A | - | -77.4 | - | - | | IMD3 | | +| | 2 | 7 | N/A | - | REFSENS | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | | N/A | | +| | | 3 | N/A | -70.3 | - | - | - | | IMD2 | | +| DC_3A-7A_n78A
DC_3C-7A_n78A
DC_3C-7C_n78A | 1 | 3 | N/A | -78.7 | - | - | - | FDD | IMD3 | | +| | | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 3 | N/A | -87.7 | - | - | - | FDD | IMD4 | | +| | | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_3A-8A_n78A | 1 | 3 | N/A | -79.8 | - | - | - | FDD | IMD3 | | +| | | 8 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_3A-19A_n79A | 1 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 19 | N/A | -80.8 | - | - | - | FDD | IMD3 | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| | 2 | 3 | N/A | -96.1 | - | - | - | FDD | IMD4 | | +| | | 19 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| DC_3A-20A_n28A | 1 | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | 3 | N/A | -86.9 | - | - | - | FDD | IMD4 | | +| DC_3A-20A_n78A | 1 | 3 | N/A | -79.0 | - | - | - | FDD | IMD3 | | +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_3A-21A_n78A | 1 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 21 | N/A | -90.5 | - | - | - | FDD | IMD4 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 3 | N/A | -65.5 | - | - | - | FDD | IMD2 | | +| | | 21 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_3A-21A_n79A | 1 | 3 | N/A | -78.5 | - | - | - | FDD | IMD3 | | +| | | 21 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| DC_3A_n28A-n78A | 1 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sin
U
allov | +|-------------------------------------------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|-----------------------------|-------------------| +| | | n78 | 15 | - | -90.3 | - | - | TDD | IMD5 | | +| DC_3A-28A_n78A | 1 | 3 | N/A | -79 | - | - | - | FDD | IMD3 | | +| | | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_3A-40A_n1A | 1 | n1 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 40 | N/A | -91.3 | - | - | - | TDD | IMD5 | | +| DC_3A-41A_n28A | 1 | 3 | N/A | -70.3 | - | - | - | FDD | IMD2 | | +| | | 41 | N/A | REFSENS | - | - | - | TDD | N/A | | +| | | n28 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 41 | N/A | -69.9 | - | - | - | TDD | IMD2 | | +| | | n28 | 15 | REFSENS | - | - | - | TDD | N/A | | +| | 3 | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 41 | N/A | -81.4 | - | - | - | TDD | IMD3 | | +| DC_3A-41A_n77A
DC_3A-41C_n77A
DC_3A-41A_n77(2A) | 1 | n28 | 15 | REFSENS | - | - | - | TDD | N/A | | +| | | 3 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 41 | N/A | -92 | - | - | - | TDD | IMD5 | | +| | | 41 | N/A | REFSENS | - | - | - | TDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_5A-7A_n78A | 1 | 3 | N/A | -79.9 | - | - | - | FDD | IMD3 | | +| | | 5 | N/A | -89.0 | - | - | - | FDD | IMD4 | | +| | | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | 2 | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | 5 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 7 | N/A | -67.2 | - | - | - | FDD | N/A | | +| | 3 | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | 5 | N/A | -67.1 | - | - | - | FDD | IMD2 | | +| | | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | 4 | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_7A-8A_n3A | 1 | 5 | N/A | -94.0 | - | - | - | FDD | IMD5 | | +| | | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 7 | N/A | - | -65.3 | - | - | FDD | IMD2+
IMD3 YY | | +| | | 8 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n3 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_7A-20A_n1A | 1 | 7 | N/A | - | REFSENS | - | - | FDD | N/A | | +| | | 8 | N/A | -78.3 | - | - | - | FDD | IMD3 | | +| | | n3 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_7A-20A_n3A | 1 | 20 | N/A | - | -88.8 | - | - | FDD | IMD5 | | +| | | n1 | - | REFSENS | - | - | - | FDD | N/A | | +| | | 7 | N/A | - | REFSENS | - | - | FDD | N/A | | +| | 2 | 20 | N/A | - | -82.8 | - | - | FDD | IMD2 | | +| | | n3 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | 7 | N/A | - | -68.3 | - | - | FDD | IMD2 | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sin
U
allov | +|---------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|--------------|-------------------| +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n3 | 15 | - | REFSENS | - | - | FDD | N/A | | +| DC_7A-20A_n8A | 1 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 20 | N/A | -78.9 | - | - | - | FDD | IMD3 | | +| | | n8 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | 2 | 7 | N/A | -76.2 | - | - | - | FDD | IMD3 | | +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n8 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | 3 | 7 | N/A | -78.5 | - | - | - | FDD | IMD3 | | +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n8 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_7A-20A_n28A | 1 | 7 | N/A | - | -91.4 | - | - | FDD | IMD5 | | +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_7A-20A_n78A | 1 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 20 | N/A | -65.8 | - | - | - | FDD | IMD2 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 20 | N/A | -93.3 | - | - | - | FDD | IMD5 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 7 | N/A | -66.5 | - | - | - | FDD | IMD2 | | +| | | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_7A-28A_n3A | 1 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 28 | N/A | -77.8 | - | - | - | FDD | IMD2 | | +| | | n3 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | 2 | 7 | N/A | -79.3 | - | - | - | FDD | IMD3 | | +| | | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n3 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_7A-28A_n5A | 1 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 28 | N/A | -93.4 | - | - | - | FDD | IMD5 | | +| | | n5 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | 2 | 7 | N/A | -91.9 | - | - | - | FDD | IMD5 | | +| | | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n5 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_7A-28A_n78A | 1 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 28 | N/A | -89.5 | - | - | - | FDD | IMD2 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 2 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 28 | N/A | -94.8 | - | - | - | FDD | IMD5 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | 3 | 7 | N/A | -66.8 | - | - | - | FDD | IMD2 | | +| | | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_7A_n28A-n78A | 1 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | -65.1 | - | - | TDD | IMD2 | | +| | 2 | 7 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | -69.0 | - | - | - | FDD | IMD2 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Sin
U
alloy | +|------------------------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|--------------|-------------------| +| DC_13A_n2A-n77A | 1 | 13 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n2 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | -77 | - | - | TDD | IMD3 | | +| | 2 | 13 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n2 | 15 | -81 | - | - | - | FDD | IMD3 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_13A-66A_n2A | 1 | 13 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 66 | N/A | -91.3 | - | - | - | FDD | IMD4 | | +| | | n2 | 15 | REFSENS | - | - | - | FDD | N/A | | +| DC_13A-66A_n77A | 1 | 13 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 66 | N/A | -81.4 | - | - | - | FDD | IMD3 | | +| | | n77 | 15 | - | REFSENS | - | - | FDD | N/A | | +| DC_18A-41A_n77A
DC_18A-41C_n77A | 1 | 18 | N/A | -95.9 | - | - | - | FDD | IMD5 | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | 41 | N/A | REFSENS | - | - | - | TDD | N/A | | +| DC_18A-41A_n78A
DC_18A-41C_n78A | 1 | 18 | N/A | -95.9 | - | - | - | FDD | IMD5 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | 41 | N/A | REFSENS | - | - | - | TDD | N/A | | +| DC_19A-21A_n79A | 1 | 19 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | 21 | N/A | -95.5 | - | - | - | FDD | IMD5 | | +| | | n79 | 15 | - | - | - | REFSENS | TDD | N/A | | +| DC_20A_n28A-n78A | 1 | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n28 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | -86.1 | - | - | TDD | IMD4 | | +| | 2 | 20 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| | | n28 | 15 | -89.1+TT | - | - | - | FDD | IMD4 | | +| DC_28A_n7A-n78A | 1 | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n7 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n78 | 15 | - | -65.1 | - | - | TDD | IMD2 | | +| | 2 | 28 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n7 | 15 | -66.8 | - | - | - | FDD | IMD2 | | +| | | n78 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_14A-66A_n2A | 1 | 14 | N/A | REFSENS | - | - | - | FDD | N/A | | + +| EN-DC Configuration | Test ID | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Single
UL
allowed | +|---------------------|---------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|-------------------|-------------------------| +| DC_66A_n2A-n77A | 1 | 66 | N/A | -91.2 | - | - | - | FDD | IMD4 | | +| | | n2 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n2 | 15 | -65.2 | - | - | - | FDD | IMD2 | | +| | | 66 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | REFSENS | - | - | TDD | N/A | | +| DC_66A_n5A-n77A | 1 | 66 | N/A | REFSENS | - | - | - | FDD | N/A | | +| | | n5 | 15 | REFSENS | - | - | - | FDD | N/A | | +| | | n77 | 15 | - | -77.7 | - | - | TDD | IMD3 9 | | + +NOTE 1: E-UTRA carrier shall be set to min(+20 dBm, $P_{\text{CMAX\_L\_E-UTRA,c}}$ ) and NR carrier shall be set to min(+20 dBm, $P_{\text{CMAX\_L,f,c,NR}}$ ) as defined in clause 6.2B.4.1.3. + +NOTE 2: $\text{RB}_{\text{START}} = 0$ + +NOTE 3: Void + +NOTE 4: This band is subject to IMD5 also which MSD is not specified. + +NOTE 5: The symbol "REFSENS" in this table refers to the reference sensitivity values for single carrier specified in Table 7.3.5-1 of TS 36.521-1 [10] for 2 antenna port E-UTRA band, Table 7.3\_1.5-1 of TS 36.521-1 [10] for 4 antenna port E-UTRA band, Table 7.3.2.5-1 for 2 antenna port NR band and Table 7.3.2.5-2 for 4 antenna port NR band. + +NOTE 6: No requirements apply when there is at least one individual RE within the intermodulation generated by the dual uplink is within the downlink transmission bandwidth of the Band 46. The reference sensitivity should only be verified when this is not the case (the requirements for Band 46 specified in the CA\_7A-46A in clause 7.3.1 of TS 36.101 [5] apply). + +NOTE 7: This band is subject to IMD3 also which MSD is not specified. + +NOTE 8: This MSD requirement apply with both IMD2 and IMD3 products should be generated. + +NOTE 9: This band is subject to IMD4 also which MSD is not specified. + +**Table 7.3B.2.3\_1.1.5-2: Reference sensitivity exceptions for Scell due to dual uplink operation for EN-DC in NR FR1 (two bands)** + +| EN-DC
Configuration | EUTRA/
NR band | SCS
(kHz) | 5 MHz
(dBm) | 10 MHz
(dBm) | 20 MHz
(dBm) | 40 MHz
(dBm) | Duplex
mode | IMD
order | Single
UL
allowed | +|------------------------|-------------------|--------------|----------------|-----------------|-----------------|-----------------|----------------|--------------|-------------------------| +| FFS | FFS | FFS | FFS | FFS | FFS | FFS | FFS | FFS | FFS | + +NOTE 1: Both of the transmitters shall be set min (+20 dBm, $P_{\text{CMAX\_L,c}}$ ) as defined in clause 6.2.5A. In case Single UL is allowed and the UE only indicates support of "Single UL" the output power of the active UL shall be set at $P_{\text{CMAX\_L,c}}$ or set to the maximum output power according to the UE power scaling capability. + +NOTE 2: $\text{RB}_{\text{START}} = 0$ + +Test tolerance is the same as given in Table 7.3B.2.3.5-2. + +###### 7.3B.2.3\_1.2 Reference sensitivity for EN-DC within FR1 (4 CCs) + +###### 7.3B.2.3\_1.2.1 Test purpose + +Same as in clause 7.3B.2.3.1. + +###### 7.3B.2.3\_1.2.2 Test applicability + +This test applies to all types of NR UE release 15 and forward supporting 4 CCs EN-DC. + +###### 7.3B.2.3\_1.2.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.3B.2.0. + +For EN-DC combinations with no exception requirements applicable to NR or E-UTRA, LTE anchor agnostic approach is applied. + +For EN-DC combinations with exceptional requirements, LTE anchor agnostic approach is not applied. + +###### 7.3B.2.3\_1.2.4 Test description + +###### 7.3B.2.3\_1.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations for E-UTRA consist of the test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1, with the exception that the E-UTRA channel bandwidth is the lowest supported value in Table 5.3B.1.3-1 for the EN-DC non-contiguous configuration under test. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.5B.2-1. The 4CC EN-DC configurations listed in table 7.3B.2.3\_1.2.4.1-0 shall not be tested according to TR 38.905 [7] test point analysis. The other 4CC configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Tables 7.3B.2.3.4.2.1-0 to 7.3B.2.3.4.2.1-1 for NR band. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [8] Annex C2. + +**Table 7.3B.2.3\_1.2.4.1-0: 4CC EN-DC configurations that shall not be tested** + +| EN-DC type | E-UTRA CA | NR CA | Notation | +|-----------------------------------------------------|-----------------|----------------|--------------------------------------------------------------------| +| Intra-band non-contiguous EN-DC (1 band) | Yes (cont) | No | DC_XD_nXA | +| Inter-band EN-DC | Yes (non-cont) | No | Note 4 | +| | Yes (all types) | No | DC_XD_nYA,
DC_XA-YC_nZA,
DC_XA-XA-YA_nZA,
DC_XA-YA-ZA_nRA | +| | Yes (all types) | Yes (cont) | DC_XC_nYC,
DC_XA-XA_nYC,
DC_XA-YA_nYC | +| | | Yes (non-cont) | DC_XC_nY(2A),
DC_XA-YA_nY(2A) | +| | | Yes (inter) | DC_XC_nYA-nZA,
DC_XA-XA_nYA-nZA,
DC_XA-YA_nZA-nRA | +| Inter-band + Intra-band contiguous EN-DC (2-3 band) | Yes | No | DC_XA-YA_(n)ZAA,
DC_XC_(n)YAA | +| | Yes | Yes | DC_(n)XCA-nYA | +| Intra-band non contiguous EN-DC (2-3 band) | Yes | No | DC_XA-YA-ZA_nZA | +| | Yes | Yes | DC_XA-YA_nYA-nZA | + +NOTE 1: X, Y and Z in this table correspond to different bands i.e. X != Y != Z. + +NOTE 2: The table apply to all band numbers, i.e. all values of X, Y and Z defined in TS38.101-3 + +NOTE 3: The band combinations with difference appearance order of bands/sub-blocks in the band combination string are not distinguished. E.g. DC\_YA-(n)XAA represents the set of DC\_YA-(n)XAA and DC\_(n)XAA-YA. + +NOTE 4: No such config in TS 38.101-3 [7] V16.5.0x + +**Table 7.3B.2.3\_1.2.4.1-1: Test Configuration Table for all EN-DC configurations for FR1 non-exception requirements** + +| Initial Conditions | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|------------|------|-----|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------|-------------|----------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | | | | | DC_(n)XDA:
Low range, High Range

DC_XA_nYA-nZC:
Mid range for X and nY
Low range, High Range for nY

DC_XA_nY(2A)-nZA:
Mid range for X, nY, nZ | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | | | | | Refer to "NR N RB " and "E-UTRA N RB " columns | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | | | | | Lowest SCS per Channel Bandwidth | | | | | +| Network signalling value | | | | | NS_01 by default
Unless given by Table 7.3.3-3 in TS 36.521-1 [10] for the E-UTRA band and Table 7.3.2.3-4 in TS 38.521-1 [8] for the NR band. | | | | | +| Test Parameters for EN-DC Configurations | | | | | | | | | | +| ID | CC (NOTE1) | Band | SCS | N RB | Range/Wgap | UL MOD | DL MOD | UL Alloc | DL Alloc | +| Default Test Settings for a DC_(n)XDA Configuration – Note 5 | | | | | | | | | | +| 1 (Note 6) | PCC(M) | X | | Highest N RB | default | QPSK | QPSK | REFSENS_LTE | All RBs | +| | SCC1(M) | X | | Highest N RB | Default | N/A | QPSK | N/A | All RBs | +| | SCC2(M) | X | | Highest N RB | Default | N/A | QPSK | N/A | All RBs | +| | PCC(S) | nX | | Highest N RB | default | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS_NR | All RBs | +| 2 (Note 7) | PCC(M) | X | | Highest N RB | default | N/A | QPSK | 0 | All RBs | +| | SCC1(M) | X | | Highest N RB | Default | N/A | QPSK | N/A | All RBs | +| | SCC2(M) | X | | Highest N RB | Default | N/A | QPSK | N/A | All RBs | +| | PCC(S) | nX | | Highest N RB | default | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS_NR | All RBs | +| Default Test Settings for a DC_XA_nY(2A)-nZA Configuration – Note 4 | | | | | | | | | | +| 1 | PCC(M) | X | | 5 MHz | default | N/A | QPSK | 0 | All RBs | +| | SCC1(S) | nY | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | SCC2(S) | nZ | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | PCC(S) | nY | | Highest N RB | default | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS_NR | All RBs | +| 2 | PCC(M) | X | | 5 MHz | default | N/A | QPSK | 0 | All RBs | +| | SCC1(S) | nY | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | SCC2(S) | nY | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | PCC(S) | nZ | | Highest N RB | default | DFT-s-OFDM | CP-OFDM | REFSENS_NR | All | + +| | | | | | | QPSK | QPSK | | RBs | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----|--|-------------------------|---------|-----------------|--------------|------------|---------| +| Default Test Settings for a DC_XA_nYA-nZC Configuration- Note 4 | | | | | | | | | | +| 1 | PCC(M) | X | | 5 MHz | default | N/A | QPSK | 0 | All RBs | +| | SCC1(S) | nZ | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | SCC2(S) | nZ | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | PCC(S) | nY | | Highest N RB | default | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS_NR | All RBs | +| 2 | PCC(M) | X | | 5 MHz | default | N/A | QPSK | 0 | All RBs | +| | SCC1(S) | nZ | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | SCC2(S) | nY | | Highest N RB | default | N/A | QPSK | N/A | All RBs | +| | PCC(S) | nZ | | Highest N RB | default | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS | All RBs | +| NOTE 1: (M) and (S) indicate MCG and SCG respectively. | | | | | | | | | | +| NOTE 2: X, Y and Z in this table correspond to different bands i.e. X != Y != Z. | | | | | | | | | | +| NOTE 3: The band combinations with difference appearance order of bands/sub-blocks in the band combination string are not distinguished. E.g. DC_YA-(n)XAA represents the set of DC_YA-(n)XAA and DC_(n)XAA-YA. | | | | | | | | | | +| NOTE 4: LTE anchor agnostic configuration | | | | | | | | | | +| NOTE 5: Not LTE anchor agnostic configuration due to exception requirement for intra-band contiguous CA in clause 7.4B, 7.5B, 7.6B.2, 7.6B.3, 7.6B.4, 7.7B, 7.8B, 7.9B test cases | | | | | | | | | | +| NOTE 6: Test point for UE supporting dual UL | | | | | | | | | | +| NOTE 7: Test point for UE supporting single UL | | | | | | | | | | +| NOTE 8: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. | | | | | | | | | | +| NOTE 9: UE supporting multiple EN-DC configurations with the same NR CA combination, only one EN-DC configuration is tested. | | | | | | | | | | +| NOTE 10: REFSENS_LTE refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.3-2 of TS 36.521-1 [10].
REFSENS_NR refers to the single carrier Uplink RB allocation for reference sensitivity according to table 7.3.2.4.1-3 of TS 38.521-1 [8]. | | | | | | | | | | + +For 4CC EN-DC configurations affected by exceptions, exception testing can be covered by 2CC or 3CC fallback configurations. No exception test points are needed in this test case. + +###### Table 7.3B.2.3\_1.2.4.1-2: Void + +###### Table 7.3B.2.3\_1.2.4.1-3: Void + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +4. NR downlink signals are initially set up according to Annex C.0, C.1, C.2, C.3.1, and uplink signals according to Annex G.0, G.1, G.2, and G.3.1 of TS 38.521-1 [8]. +5. E-UTRA downlink signals are initially set up according to Annex C.0, C.1 and C.3.0, and uplink signals according to Annex H.1 and H.3.0 of TS 36.521-1 [10]. + +6. The DL and UL Reference Measurement channels are set according to Tables 7.3B.2.3.4.2.1-0 to 7.3B.2.3.4.2.1-6 for E-UTRA CG and NR CG. +7. NR propagation conditions are set according to Annex B.0 of TS 38.521-1 [8]. E-UTRA propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +8. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.3B.2.3\_1.2.4.3. +9. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.3B.2.3\_1.2.4.2 Test procedure + +1. NR SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.3B.2.3\_1.2.4.2.1-1 on the NR CC. The NR SS sends downlink MAC padding bits on the DL RMC. +2. NR SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.3B.2.3\_1.2.4.2.1-1. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the appropriate REFSENS value defined in TS 38.521-1 [8], Table 7.3.2.5-1 for NR band. Send continuously uplink power control "up" commands in the uplink scheduling information to NR carrier to ensure the UE transmits PUMAX level for at least the duration of the Throughput measurement. +4. Measure the average throughput of the NR carrier for a duration sufficient to achieve statistical significance according to Annex H.2 of TS 38.521-1 [8] for NR band. + +###### 7.3B.2.3\_1.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents exceptions for E-UTRA band are according to TS 36.521-1 [10] clause 7.3.4.3 for each network signalling value. Message contents exceptions for NR band are according to TS 38.521-1 [8] clause 7.3.2.4.3 for each network signalling value. + +###### 7.3B.2.3\_1.2.5 Test Requirement + +Reference sensitivity test requirements for EN-DC configurations are specified in Table 7.3.5-1 in TS 36.521-1 [10] for the LTE CC, and Table 7.3.2.5-1 in TS 38.521-1 [8] for the NR CC. + +###### **Table 7.3B.2.3\_1.2.5-1: Reference sensitivity exceptions for Scell due to dual uplink operation for EN-DC in NR FR1 (two bands)** + +FFS + +###### **Table 7.3B.2.3\_1.2.5-2: Reference sensitivity exceptions for Scell due to dual uplink operation for EN-DC in NR FR1 (three bands)** + +FFS + +###### 7.3B.2.3\_1.3 Reference sensitivity for EN-DC within FR1 (5 CCs) + +###### 7.3B.2.3\_1.3.1 Test purpose + +Same as in clause 7.3B.2.3.1. + +###### 7.3B.2.3\_1.3.2 Test applicability + +This test applies to all types of NR UE release 15 and forward supporting 5 CCs inter-band EN-DC. + +###### 7.3B.2.3\_1.3.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.3B.2.0 + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 7.3B.2.3\_1.3.4 Test description + +###### 7.3B.2.3\_1.3.4.1 Initial conditions + +Same initial conditions as in clause 7.3B.2.3.4.1 with following exceptions: + +The initial test configurations for E-UTRA band and NR band consist of environmental conditions, test frequencies, and channel bandwidths and RB allocations for exceptional test scenarios are specified in Table 7.3B.2.3\_1.3.4.1-1 and Table 7.3B.2.3\_1.3.4.1-2 + +**Table 7.3B.2.3\_1.3.4.1-1: Test Configuration Table Reference sensitivity exceptions due to dual uplink operation for EN-DC in NR FR1 (four bands)** + +| Initial Conditions | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|------|--------|-------------------------|-------------|-----------------|--------------|----------|----------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | For test frequencies refer to "Range" columns. For mapping within Band refer to "CC" columns | | | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Refer to "N RB " column | | | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Refer to "SCS" column | | | | | | | | | +| Network signalling value | NS_01 by default, exceptions listed in Table 7.3.3-3, dependent on PCC Band | | | | | | | | | +| Test Parameters for EN-DC Configurations | | | | | | | | | | +| ID | CC (NOTE1) | Band | SCS | N RB | Range/ Wgap | UL MOD | DL MOD | UL Alloc | DL Alloc | +| Default Test Settings for a DC_XA-YA_ZC_nRA Configuration | | | | | | | | | | +| 1 | PCC(M) | X | N/A | Highest N RB | Mid | QPSK | QPSK | REFSENS | All RBs | +| | SCC1(M) | Y | N/A | Highest N RB | Mid | N/A | QPSK | N/A | All RBs | +| | SCC2(M) | Z | N/A | Highest N RB | Mid | N/A | QPSK | N/A | All RBs | +| | SCC3(M) | Z | N/A | Highest N RB | Mid | N/A | QPSK | N/A | All RBs | +| | PCC(S) | R | 15 kHz | Highest N RB | Mid | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS | All RBs | + +NOTE 1: (M) and (S) indicate MCG and SCG respectively. +NOTE 2: X, Y and Z in this table correspond to different bands i.e. X != Y != Z +NOTE 3: The band combinations with difference appearance order of bands/sub-blocks in the band combination string are not distinguished. E.g. DC\_YA-(n)XAA represents the set of DC\_YA-(n)XAA and DC\_(n)XAA-YA + +**Table 7.3B.2.3\_1.3.4.1-2: Test Configuration Table Reference sensitivity exceptions due to dual uplink operation for EN-DC in NR FR1 (five bands)** + +| Initial Conditions | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|------------|------|--------|-------------------------|----------------------------------------------------------------------------------------------|-----------------|--------------|----------|----------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | | | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | | | | | For test frequencies refer to "Range" columns. For mapping within Band refer to "CC" columns | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | | | | | Refer to "N RB " column | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | | | | | Refer to "SCS" column | | | | | +| Network signalling value | | | | | NS_01 by default, exceptions listed in Table 7.3.3-3, dependent on PCC Band | | | | | +| Test Parameters for EN-DC Configurations | | | | | | | | | | +| ID | CC (NOTE1) | Band | SCS | N RB | Range/Wgap | UL MOD | DL MOD | UL Alloc | DL Alloc | +| Default Test Settings for a DC_XA-YA-ZA-SA_nRA Configuration | | | | | | | | | | +| 1 | PCC(M) | X | N/A | Highest N RB | Mid | QPSK | QPSK | REFSENS | All RBs | +| | SCC1(M) | Y | N/A | Highest N RB | Mid | N/A | QPSK | N/A | All RBs | +| | SCC2(M) | Z | N/A | Highest N RB | Mid | N/A | QPSK | N/A | All RBs | +| | SCC3(M) | S | N/A | Highest N RB | Mid | N/A | QPSK | N/A | All RBs | +| | PCC(S) | R | 15 kHz | Highest N RB | Mid | DFT-s-OFDM QPSK | CP-OFDM QPSK | REFSENS | All RBs | + +NOTE 1: (M) and (S) indicate MCG and SCG respectively. +NOTE 2: X, Y and Z in this table correspond to different E-UTRA bands i.e. X != Y != Z, R corresponds to NR band. +NOTE 3: For inter-band EN-DC 4CCs configuration with four bands, if there is no additional exceptional test point is defined besides the requirement for default uplink EN-DC configurations defined in Table 5.5B.4.3-1, testing for 4CC with four band can be skipped. + +###### 7.3B.2.3\_1.3.4.2 Test procedure + +Same as in clause 7.3B.2.3.4.2. + +###### 7.3B.2.3\_1.3.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6. + +###### 7.3B.2.3\_1.3.5 Test requirement + +For inter-band EN-DC configurations, the throughput of each CG shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 with reference receive power level specified in Tables Table 7.3.2.5-1 in TS 38.521-1 [8] and parameters specified Tables 7.3.2.4.1-1, Tables 7.3.2.4.1-2 and Tables 7.3.2.4.1-3 in TS 38.521-1 [8] for NR band. + +Each EN-DC combination defined in Table 5.5B.4.3-1 shall be tested in anchor-agnostic mode as described in this clause. If a test point is overlapped with uplink EN-DC combo MSD test points, the requirement with MSD shall apply. + +For the UE which supports inter-band EN-DC, the minimum requirement for reference sensitivity in Table 7.3.2.5-1 of TS 38.521-1 [8] for NR band and Table 7.3.5-1 of TS 36.521-1 [10] for EUTRA band, shall be increased by the amount given in $\Delta R_{RB,e}$ defined in clause 7.3B.3.3 for the applicable for two, three, four and five bands operation. + +Reference sensitivity exceptions for intermodulation interference due to dual uplink operation for EN-DC in NR FR1, are specified in Table 7.3B.2.3\_1.3.5-1 for four bands and Table 7.3B.2.3\_1.3.5-2 for five bands with uplink configuration specified in Table 7.3B.2.3\_1.3.4.1-1 for four bands and 7.3B.2.3\_1.3.4.1-2 for five bands, respectively. + +For a given inter-band EN-DC 5CCs configuration defined in Table 5.5B.4.3-1 and Table 5.5B.4.4-1, if there is no additional exceptional test point is defined besides the requirement for default uplink EN-DC configurations defined in Table 5.5B.4.3-1 and Table 5.5B.4.4-1, the test requirement for default fallback uplink EN-DC configurations defined in Table 5.5B.4.3-1 applies. + +###### **Table 7.3B.2.3\_1.3.5-1 Reference sensitivity exceptions for Scell due to dual uplink operation for EN-DC in NR FR1 (four bands)** + +TBD + +###### **Table 7.3B.2.3\_1.3.5-2 Reference sensitivity exceptions for Scell due to dual uplink operation for EN-DC in NR FR1 (five bands)** + +TBD + +##### **7.3B.2.3\_1.4 Reference sensitivity for EN-DC within FR1 (6 CCs)** + +TBD + +#### **7.3B.2.4 Reference sensitivity for Inter-band EN-DC including FR2 (1 NR CC)** + +**Editor's note: The following aspects are either missing or not yet determined:** + +- Measurement Uncertainties and Test Tolerances are FFS for power class 2 and 4. + +##### **7.3B.2.4.1 Test purpose** + +Same test purpose as in clause 7.3.2.1 in TS 38.521-2 [9] for the NR carrier. + +##### **7.3B.2.4.2 Test applicability** + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR DL CC. + +##### **7.3B.2.4.3 Minimum conformance requirements** + +Same minimum conformance requirements as in clause 7.3B.2.0.4 TS 3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.3B.2.4. + +##### **7.3B.2.4.4 Test description** + +###### **7.3B.2.4.4.1 Initial conditions** + +Same test description as in clause 7.3.2.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 7.3.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.3.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 7.3.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 7.3B.2.4.5 Test requirement + +Same test requirement as in clause 7.3.2.5 in TS 38.521-2 [9] for the NR carrier. + +##### 7.3B.2.4\_1 Reference sensitivity for Inter-band EN-DC including FR2 (>1 NR CC) + +###### 7.3B.2.4\_1.1 Reference sensitivity for Inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- Measurement Uncertainties and Test Tolerances for intra-band contiguous CA supporting aggregated BW > 400MHz and for intra-band non-contiguous CA are TBD. +- Measurement Uncertainties and Test Tolerances are FFS for power class 1, 2 and 4. +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.1.1 Test purpose + +Same test purpose as in clause 7.3B.2.4.1. + +###### 7.3B.2.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 2 NR DL CCs in either intra-band contiguous or intra-band non-contiguous configuration. + +###### 7.3B.2.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.1. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.1.4 Test description + +For inter-band EN-DC including FR2 UE configured as 2 NR DL CCs and 1 LTE DL CC, the test description of 2DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.1.4 in TS 38.521-2 [9] with the exceptions described below. + +###### 7.3B.2.4\_1.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.5.1, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-2 [9] clause 5.3A and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2 or clause 5.4.2A. All valid configurations shall be tested with applicable test parameters for inter-band EN-DC including FR2 configuration specified in clause 5.5B.5, and the configuration for NR carrier are shown in TS 38.521-2 [9] Table 7.3A.2.1.4.1-1. + +For Initial conditions as in clause 7.3A.2.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are configured as per clause 4.7 with parameters set according to Table 4.7-1 and propagation conditions set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.3A.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +###### 7.3B.2.4\_1.1.4.2 Test Procedure + +Same test procedure as in clause 7.3A.2.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 7.3B.2.4\_1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1. + +###### 7.3B.2.4\_1.1.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +###### 7.3B.2.4\_1.2 Reference sensitivity for Inter-band EN-DC including FR2 (3 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- Measurement Uncertainties and Test Tolerances for intra-band contiguous CA supporting aggregated BW > 400MHz and for intra-band non-contiguous CA are TBD. +- Measurement Uncertainties and Test Tolerances are FFS for power class 1, 2 and 4. +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.2.1 Test purpose + +Same test purpose as in clause 7.3B.2.4\_1.1.1. + +###### 7.3B.2.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 3 NR DL CCs in either intra-band contiguous or intra-band non-contiguous configuration. + +###### 7.3B.2.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.2.4\_1.1.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.2.4 Test description + +For inter-band EN-DC including FR2 UE configured as 3 NR DL CCs and 1 LTE DL CC, the test description of 3DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.2.4 in TS 38.521-2 [9], with the exceptions described in clause 7.3B.2.4\_1.1.4.1 and clause 7.3B.2.4\_1.1.4.2. + +###### 7.3B.2.4\_1.2.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +##### 7.3B.2.4\_1.3 Reference sensitivity for Inter-band EN-DC including FR2 (4 NR CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- Measurement Uncertainties and Test Tolerances for intra-band contiguous CA supporting aggregated BW > 400MHz and for intra-band non-contiguous CA are TBD. +- Measurement Uncertainties and Test Tolerances are FFS for power class 1, 2 and 4. +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.3.1 Test purpose + +Same test purpose as in clause 7.3B.2.4\_1.1.1. + +###### 7.3B.2.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 4 NR DL CCs in either intra-band contiguous or intra-band non-contiguous configuration. + +###### 7.3B.2.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.2.4\_1.1.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.3.4 Test description + +For inter-band EN-DC including FR2 UE configured as 4 NR DL CCs and 1 LTE DL CC, the test description of 4DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.3.4 in TS 38.521-2 [9], with the exceptions described in clause 7.3B.2.4\_1.1.4.1 and clause 7.3B.2.4\_1.1.4.2. + +###### 7.3B.2.4\_1.3.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +###### 7.3B.2.4\_1.4 Reference sensitivity for Inter-band EN-DC including FR2 (5 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- Measurement Uncertainties and Test Tolerances are FFS. +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.4.1 Test purpose + +Same test purpose as in clause 7.3B.2.4\_1.1.1. + +###### 7.3B.2.4\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 5 NR DL CCs in either intra-band contiguous or intra-band non-contiguous configuration. + +###### 7.3B.2.4\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.2.4\_1.1.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.4.4 Test description + +For inter-band EN-DC including FR2 configured as 5 NR DL CCs and 1 LTE DL CC, the test description of 5DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.4.4 in TS 38.521-2 [9], with the exceptions described in clause 7.3B.2.4\_1.1.4.1 and clause 7.3B.2.4\_1.1.4.2. + +###### 7.3B.2.4\_1.4.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +##### 7.3B.2.4\_1.5 Reference sensitivity for Inter-band EN-DC including FR2 (6 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- Measurement Uncertainties and Test Tolerances are FFS. + +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.5.1 Test purpose + +Same test purpose as in clause 7.3B.2.4\_1.1.1. + +###### 7.3B.2.4\_1.5.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 6 NR DL CCs in either intra-band contiguous or intra-band non-contiguous configuration. + +###### 7.3B.2.4\_1.5.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.2.4\_1.1.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.5.4 Test description + +For inter-band EN-DC including FR2 configured as 6 NR DL CCs and 1 LTE DL CC, the test description of 6DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.5.4 in TS 38.521-2 [9], with the exceptions described in clause 7.3B.2.4\_1.1.4.1 and clause 7.3B.2.4\_1.1.4.2. + +###### 7.3B.2.4\_1.5.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +##### 7.3B.2.4\_1.6 Reference sensitivity for Inter-band EN-DC including FR2 (7 NR CCs) + +**Editor's note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- Measurement Uncertainties and Test Tolerances are FFS. +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.6.1 Test purpose + +Same test purpose as in clause 7.3B.2.4\_1.1.1. + +###### 7.3B.2.4\_1.6.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 7 NR DL CCs in either intra-band contiguous or intra-band non-contiguous configuration. + +###### 7.3B.2.4\_1.6.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.2.4\_1.1.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.6.4 Test description + +For inter-band EN-DC including FR2 configured as 7 NR DL CCs and 1 LTE DL CC, the test description of 7DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.6.4 in TS 38.521-2 [9], with the exceptions described in clause 7.3B.2.4\_1.1.4.1 and clause 7.3B.2.4\_1.1.4.2. + +###### 7.3B.2.4\_1.6.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +##### 7.3B.2.4\_1.7 Reference sensitivity for Inter-band EN-DC including FR2 (8 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- Measurement Uncertainties and Test Tolerances are FFS. +- In case of frequency separation larger than 800 MHz and in case the device manufacturer does not explicitly declare that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes, according to Table A.4.3.9-6 in 38.508-2, following aspect of beam peak search procedures for CA is FFS: RB allocation, power level, channel bandwidth configuration, per CC approach or all CC combined approach, etc +- Testing of extreme conditions for FR2 is FFS. + +###### 7.3B.2.4\_1.7.1 Test purpose + +Same test purpose as in clause 7.3B.2.4\_1.1.1. + +###### 7.3B.2.4\_1.7.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC including FR2 with 8 NR DL CCs in intra-band contiguous configuration. + +###### 7.3B.2.4\_1.7.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3B.2.4\_1.1.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.3B.2.4\_1.7.4 Test description + +For inter-band EN-DC including FR2 configured as 8 NR DL CCs and 1 LTE DL CC, the test description of 8DL FR2 CA for reference sensitivity is the same as in corresponding clause of clause 7.3A.2.7.4 in TS 38.521-2 [9], with the exceptions described in clause 7.3B.2.4\_1.1.4.1 and clause 7.3B.2.4\_1.1.4.2. + +###### 7.3B.2.4\_1.7.5 Test requirement + +For each NR component carrier, the test requirement is the same as in clause 7.3A.2.1.5 in TS 38.521-2 [9]. + +#### 7.3B.2.4D Reference sensitivity for inter-band EN-DC including FR2 for UL MIMO + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach can be applied and only NR carriers need to be tested. + +No test case details are specified. Given UE's Rx performance would not be impacted by the Tx configuration in NR FR2 TDD bands, the requirements in this test case can be well covered in 7.3B.2.4 and 7.3B.2.4\_1 and don't need to be tested again. + +#### 7.3B.2.5 Reference sensitivity for Inter-band EN-DC including FR1 and FR2 (3 CCs) + +##### 7.3B.2.5.1 Test purpose + +Same test purpose as in 7.3B.2 in TS 38.521-1 [8] for NR FR1 carrier(s) and 7.3.2 in TS 38.521-2 [9] for NR FR2 carrier(s). + +##### 7.3B.2.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for reference sensitivity apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.3B. + +#### 7.3B.2.5D Reference sensitivity for inter-band EN-DC including FR1 and FR2 for UL MIMO + +##### 7.3B.2.5D.1 Test purpose + +Same test purpose as in clause 7.3D in TS 38.521-1 [8] for NR FR1 carrier and 7.3D in TS 38.521-2 [9] for NR FR2 carrier. + +##### 7.3B.2.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for reference sensitivity apply and are tested as part of the EN-DC within FR1 as in clause 7.3 in TS 38.521-1 [8] and EN-DC within FR2 as in clause 7.3 in TS 38.521-2 [9]. + +#### 7.3B.2.6 Void + +### 7.3B.3 $\Delta R_{IB,c}$ $\Delta R_{IBNC}$ for EN-DC + +#### 7.3B.3.0 General + +For the UE which supports inter-band EN-DC or NE-DC configuration, the minimum requirement for reference sensitivity in Table 7.3.1-1 and Table 7.3.1-1a in TS 36.101 [5], clause 7.3.2, 7.3A.2, 7.3C.2 in TS 38.101-1 [2] and clause 7.3.2, 7.3A.2 in TS 38.101-2 [3] shall be increased by the amount given in $\Delta R_{IB,c}$ $\Delta R_{IBNC}$ in Tables below where unless otherwise stated, the same $\Delta R_{IB,c}$ , $\Delta R_{IBNC}$ are applicable to NR band(s) part for DC configurations which have the same NR operating band combination. Unless otherwise stated, $\Delta R_{IB,c}$ or $\Delta R_{IBNC}$ is set to zero. + +In case the UE supports more than one of band combinations for CA, SUL or DC, and an operating band belongs to more than one band combinations then + +- When the operating band frequency range is $\leq 1$ GHz, the applicable additional $\Delta R_{IB,c}$ shall be the average value for all band combinations defined in clause 7.3A, 7.3B, 7.3C in TS 38.101-1 [2] and 7.3A, 7.3B in TS 38.101-3 [4], truncated to one decimal place that apply for that operating band among the supported band combinations. In case there is a harmonic relation between low band UL and high band DL, then the maximum $\Delta R_{IB,c}$ among the different supported band combinations involving such band shall be applied. +- When the operating band frequency range is $> 1$ GHz, the applicable additional $\Delta R_{IB,c}$ shall be the maximum value for all band combinations defined in clause 7.3A, 7.3B, 7.3C in TS 38.101-1 [2] and 7.3A, 7.3B in TS 38.101-3 [4] for the applicable operating bands. + +Unless $\Delta R_{IB,c}$ is specified for the NE-DC configuration, the specified $\Delta R_{IB,c}$ for the EN-DC configuration including same bands as the corresponding NE-DC configuration is applicable for the NE-DC configuration. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.3B.3. + +#### 7.3B.3.1 Reference sensitivity $\Delta R_{IB,c}$ for Intra-band Contiguous EN-DC + +FFS + +#### 7.3B.3.2 Reference sensitivity $\Delta R_{IB,c}$ for Intra-band non-contiguous EN-DC + +**Table 7.3B.3.2-1: Intra-band non-contiguous EN-DC with one uplink configuration on E-UTRA for reference sensitivity** + +| DC configuration | Aggregated channel bandwidth (LTE+NR) | | $W_{gap}$ / (MHz) | UL E-UTRA allocation | $\Delta R_{IBNC}$ (dB) | Duplex mode | +|------------------|---------------------------------------|----|-------------------|----------------------|------------------------|-------------| +| | E-UTRA | NR | | | | | +| | | | | | | | + +7.3B.3.3 $\Delta R_{IB,c}$ for Inter-band EN-DC within FR1 + +7.3B.3.3.1 $\Delta R_{IB,c}$ for EN-DC in two bands + +**Table 7.3B.3.3.1-1: $\Delta R_{IB,c}$ due to EN-DC(two bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta R_{B,c}$ (dB) | +|--------------------------------|-------------------|-----------------------| +| DC_1_n28 | n28 | 0.2 | +| DC_1_n41 | 1 | 0 | +| | n41 | 0 | +| DC_1_n77 | 1 | 0.2 | +| | n77 | 0.5 | +| DC_1_n78 | n78 | 0.5 | +| DC_2_n66 | 2 | 0.3 | +| | n66 | 0.3 | +| DC_2_n77 | 2 | 0.2 | +| DC_2-2_n77 | n77 | 0.5 | +| DC_2_n78 | 2 | 0.2 | +| | n78 | 0.5 | +| DC_3_n41 | n41 | 0 3 | +| | | 0.5 4 | +| DC_3_n77 | 3 | 0.2 | +| | n77 | 0.5 | +| DC_3_n78 | 3 | 0.2 | +| | n78 | 0.5 | +| DC_5_n78 | 5 | 0.2 | +| | n78 | 0.5 | +| DC_7_n8 | n8 | 0.2 | +| DC_7_n66 | 7 | 0.5 | +| | n66 | 0.5 | +| DC_7_n71 | n71 | 0.2 | +| DC_7_n77 | n77 | 0.5 | +| DC_7_n78, DC_7-7_n78 | n78 | 0.5 | +| DC_8_n77 | 8 | 0.2 | +| | n77 | 0.5 | +| DC_8_n78 | 8 | 0.2 | +| | n78 | 0.5 | +| DC_11_n77 | n77 | 0.5 | +| DC_11_n78 | n78 | 0.5 | +| DC_12_n5 | 12 | 0.3 | +| | n5 | 0.5 | +| DC_12_n66 | 12 | 0.5 | +| DC_12_n77 | 12 | 0.2 | +| | n77 | 0.5 | +| DC_12_n78 | 12 | 0.2 | +| | n78 | 0.5 | +| DC_14_n77 | 14 | 0.2 | +| | n77 | 0.5 | +| DC_18_n77 | n77 | 0.5 | +| DC_19_n77 | n77 | 0.5 | +| DC_19_n78 | n78 | 0.5 | +| DC_20_n78 | n78 | 0.5 | +| DC_21_n77 | n77 | 0.5 | +| DC_21_n78 | n78 | 0.5 | +| DC_25_n41 | n41 | 0 1 | +| | | 0.5 2 | +| DC_26_n77 | n77 | 0.5 | +| DC_26_n78 | n78 | 0.5 | +| DC_28_n51 | n51 | 0.2 | +| DC_28_n77 | 28 | 0.2 | +| | n77 | 0.5 | +| DC_28_n78 | 28 | 0.2 | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|-----|------------------| +| | n78 | 0.5 | +| DC_30_n66 | 30 | 0.5 | +| | n66 | 0.4 | +| DC_30_n77 | n77 | 0.5 | +| DC_38_n78 | 38 | 0.4 | +| | n78 | 0.5 | +| DC_39_n41 | 39 | 0.2 | +| | n41 | 0.2 | +| DC_39_n79 | n79 | 0.5 | +| DC_40_n78 | 40 | 0.4 5 | +| | n78 | 0.5 5 | +| DC_40_n79 | n79 | 0.5 | +| DC_41_n28 | 41 | 0 | +| | n28 | 0 | +| DC_41_n77 | n77 | 0.5 | +| DC_41_n78 | n78 | 0.5 | +| DC_41_n79 | n79 | 0.5 | +| DC_48_n66 | 48 | 0.5 | +| | n66 | 0.2 | +| DC_66_n2 | 66 | 0.3 | +| | n2 | 0.3 | +| DC_66_n25 | 66 | 0.3 | +| | n25 | 0.3 | +| DC_66_n41 | 66 | 0.5 | +| | n41 | 0.5 1 | +| | | 1 2 | +| DC_66_n77 | 66 | 0.2 | +| DC_66-66_n77 | n77 | 0.5 | +| DC_66_n78 | 66 | 0.2 | +| | n78 | 0.5 | +| NOTE 1: The requirement is applied for UE transmitting on the frequency range of 2545-2690MHz. | | | +| NOTE 2: The requirement is applied for UE transmitting on the frequency range of 2496-2545MHz. | | | +| NOTE 3: Applicable for the frequency range of 2515-2690 MHz. | | | +| NOTE 4: Applicable for the frequency range of 2496-2515 MHz. | | | +| NOTE 5: Only applicable for UE supporting inter-band carrier aggregation with uplink in one E-UTRA band and without simultaneous Rx/Tx. | | | + +##### 7.3B.3.3.2 $\Delta R_{\text{IB,c}}$ for EN-DC in three bands + +**Table 7.3B.3.3.2-1: $\Delta R_{\text{IB,c}}$ due to EN-DC (three bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta R_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1-3_n28 | n28 | 0.2 | +| DC_1-3_n41 | n41 | 0 3 | +| DC_1-3_n77 | 1 | 0.2 | +| | 3 | 0.2 | +| | n77 | 0.5 | +| DC_1-3_n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | n78 | 0.5 | +| DC_1_n3-n78 | 1 | 0.2 | +| | n3 | 0.2 | +| | n78 | 0.5 | +| DC_1-3_n79 | n79 | 0.5 | +| DC_1-5_n78 | 1 | 0.2 | +| | 5 | 0.2 | +| | n78 | 0.5 | +| DC_1-7_n28 | n28 | 0.2 | +| DC_1-7_n78 | 1 | 0.2 | +| | 7 or n7 | 0.2 | +| | n78 | 0.5 | +| | 8 | 0.2 | +| | n77 | 0.5 | +| DC_1-8_n78 | 8 | 0.2 | +| | n78 | 0.5 | +| DC_1-18_n77 | n77 | 0.5 | +| DC_1-19_n77 | n77 | 0.5 | +| DC_1-19_n78 | n78 | 0.5 | +| DC_1-19_n79 | 1 | 0.3 | +| | 19 | 0.3 | +| DC_1-20_n28 | 20 | 0.2 | +| | n28 | 0.2 | +| DC_1-20_n78 | n78 | 0.5 | +| DC_1-21_n77 | n77 | 0.5 | +| DC_1-21_n78 | 1 | 0.2 | +| | n78 | 0.5 | +| DC_1-28_n78 | 28 or n28 | 0.2 | +| DC_1_n28-n78 | n78 | 0.5 | +| DC_1_n28-n79 | 1 | 0.3 | +| | 28 | 0.3 | +| DC_1-41_n28 | n28 | 0.2 | +| DC_1-41_n41 | 1 | 0 | +| | 41 | 0 | +| | n41 | 0 | +| DC_1-41_n77 | n77 | 0.5 | +| DC_1-41_n78 | n78 | 0.5 | +| DC_1-42_n77 | 1 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_1-42_n78 | 1 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_1-42_n79 | 42 | 0.5 | +| DC_1_n77-n79 | 1 | 0.2 | +| | n77 | 0.5 | +| DC_1_n78-n79 | n78 | 0.5 | +| DC_2-5_n66 | 2 | 0.3 | + +| | | | +|-----------------------------------------------------------------------------|---------|------------------| +| | n66 | 0.3 | +| | n71 | 0.2 | +| DC_2_n5-n77 | 2 | 0.2 | +| | n77 | 0.5 | +| DC_2-13_n66
DC_2-2-13_n66 | 2 | 0.3 | +| | n66 | 0.3 | +| DC_2-13_n77 | 2 | 0.2 | +| | 13 | 0.2 | +| | n77 | 0.5 | +| DC_2-29_n260 | 2 | 0 | +| DC_2-14_n66
DC_2-2-14_n66 | 2 | 0.3 | +| | n66 | 0.3 | +| DC_2-30_n5, DC_2-2-30_n5 | 2 | 0.4 | +| | 30 | 0.5 | +| DC_2-30_n66 | 2 | 0.4 | +| | 30 | 0.5 | +| | n66 | 0.4 | +| DC_2-66_n5
DC_2A-2A-66A_n5A
DC_2-66-66_n5
DC_2A-2A-66A-66A_n5
A | 2 | 0.3 | +| | | | +| | 66 | 0.3 | +| | | | +| DC_2-66_n41 | 2 | 0.3 | +| | 66 | 0.5 | +| | | 0.5 1 | +| | n41 | 1 2 | +| DC_2-66_n71B | 2 | 0.3 | +| | 66 | 0.3 | +| DC_2-66_n77 | 2 | 0.3 | +| | 66 | 0.3 | +| | n77 | 0.5 | +| DC_2-66_n78 | 2 | 0.3 | +| | 66 | 0.3 | +| | n78 | 0.5 | +| DC_3_n1-n77 | 3 | 0.2 | +| | n1 | 0.2 | +| | n77 | 0.5 | +| DC_3_n1-n78 | 3 | 0.2 | +| | n1 | 0.2 | +| | n78 | 0.5 | +| DC_3-5_n78 | 3 | 0.2 | +| | 5 | 0.2 | +| | n78 | 0.5 | +| DC_3-7_n8 | n8 | 0.2 | +| DC_3-7_n78
DC_3-7-7_n78 | 3 | 0.2 | +| | 7 or n7 | 0.2 | +| | n78 | 0.5 | +| DC_3-8_n28 | 8 | 0.2 | +| | n28 | 0.1 | +| DC_3-8_n78 | 3 | 0.2 | +| | 8 | 0.2 | +| | n78 | 0.5 | +| DC_3-18_n77 | 3 | 0.2 | +| | n77 | 0.5 | +| DC_3-18_n78 | 3 | 0.2 | +| | n78 | 0.5 | +| DC_3-19_n77 | 3 | 0.2 | + +| | | | +|--------------|-----|----------------------------------| +| | n77 | 0.5 | +| DC_3-19_n78 | 3 | 0.2 | +| | n78 | 0.5 | +| DC_3-20_n28 | 20 | 0.1 | +| | n28 | 0.1 | +| DC_3-20_n78 | 3 | 0.2 | +| | n78 | 0.5 | +| DC_3-21_n77 | 3 | 0.3 | +| | 21 | 0.5 | +| | n77 | 0.5 | +| DC_3-21_n78 | 3 | 0.3 | +| | 21 | 0.5 | +| | n78 | 0.5 | +| DC_3-21_n79 | 3 | 0.3 | +| | 21 | 0.5 | +| | 28 | 0.1 | +| | n5 | 0.1 | +| | n41 | 0 1 /0.5 2 | +| DC_3-28_n78 | 3 | 0.2 | +| DC_3_n28-n78 | n78 | 0.5 | +| DC_3-41_n28 | 3 | 0 | +| | 41 | 0 1 /0.5 2 | +| | n28 | 0 | +| DC_3-41_n41 | 41 | 0 3 | +| | | 0.5 4 | +| | n41 | 0 3 | +| | | 0.5 4 | +| DC_3-41_n77 | 3 | 0.2 | +| | 41 | 0 1 | +| | n77 | 0.5 | +| DC_3-42_n77 | 3 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_3-42_n78 | 3 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_3-42_n79 | 3 | 0.2 | +| | 42 | 0.5 | +| DC_3_n77-n79 | 3 | 0.2 | +| | n77 | 0.5 | +| DC_3_n78-n79 | 3 | 0.2 | +| | n78 | 0.5 | +| DC_5-7_n78 | 5 | 0.2 | +| | 7 | 0.2 | +| | n78 | 0.5 2 | +| DC_5-30_n66 | 30 | 0.5 | +| | n66 | 0.4 | +| DC_7_n1-n78 | 7 | 0.2 | +| | n1 | 0.2 | +| | n78 | 0.5 | +| DC_7-8_n3 | 8 | 0.2 | +| DC_7-20_n28 | 20 | 0.2 | +| | | | + +| | | | +|----------------|-----|-----| +| | n28 | 0.2 | +| DC_7-20_n78 | n78 | 0.5 | +| DC_7-28_n78 | n78 | 0.5 | +| DC_7_n28-n78 | n78 | 0.5 | +| DC_13_n2-n77 | n2 | 0.2 | +| | n77 | 0.5 | +| DC_13-66_n2 | 66 | 0.3 | +| | n2 | 0.3 | +| DC_13-66_n77 | 13 | 0.3 | +| | 66 | 0.3 | +| | n77 | 0.5 | +| DC_14-66_n2 | 66 | 0.3 | +| DC_14-66-66_n2 | n2 | 0.3 | +| DC_18-41_n77 | n77 | 0.5 | +| DC_18-41_n78 | n78 | 0.5 | +| DC_19-21_n77 | n77 | 0.5 | +| DC_19-21_n78 | n78 | 0.5 | +| DC_19-42_n77 | 42 | 0.5 | +| | n77 | 0.5 | +| DC_19-42_n78 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_19-42_n79 | 42 | 0.5 | +| DC_19_n77-n79 | n77 | 0.5 | +| DC_19_n78-n79 | n78 | 0.5 | +| DC_20_n3-n78 | n3 | 0.2 | +| | n78 | 0.5 | +| DC_20_n28-n78 | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_20-38_n78 | 38 | 0.4 | +| | n78 | 0.5 | +| DC_20_n76-n78 | n78 | 0.5 | +| DC_21-42_n77 | 42 | 0.5 | +| | n77 | 0.5 | +| DC_21-42_n78 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_21-42_n79 | 42 | 0.5 | +| DC_21_n77-n79 | n77 | 0.5 | +| DC_21_n78-n79 | n78 | 0.5 | +| DC_28_n7-n78 | n78 | 0.5 | +| DC_28-41_n78 | 28 | 0.2 | +| | n78 | 0.5 | +| | n79 | 0.5 | +| DC_28-42_n78 | 28 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_66_n5 | 66 | 0.4 | +| | n5 | 0.5 | +| DC_41-42_n78 | 42 | 0.5 | +| | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------|-----|-----| +| | n78 | 0.5 | +| DC_66_n2-n77 | 66 | 0.3 | +| | n2 | 0.3 | +| | n77 | 0.5 | +| | | | +| DC_66_n5-n77 | 66 | 0.2 | +| | n77 | 0.5 | +| NOTE 1: The requirement is applied for UE transmitting on the frequency range of 2545-2690MHz. | | | +| NOTE 2: The requirement is applied for UE transmitting on the frequency range of 2496-2545MHz. | | | +| NOTE 3: The requirement is applied for UE transmitting on the frequency range of 2515 – 2690 MHz. | | | +| NOTE 4: The requirement is applied for UE transmitting on the frequency range of 2496 – 2515 MHz. | | | +| NOTE 5: Only applicable for UE supporting inter-band carrier aggregation with uplink in one NR band and without simultaneous Rx/Tx. | | | + +##### 7.3B.3.3.3 $\Delta R_{IB,c}$ for EN-DC in four bands + +**Table 7.3B.3.3.3-1: $\Delta R_{IB,c}$ due to EN-DC (four bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta R_{IB,c}$ (dB) | +|---------------------------------|-------------------|------------------------| +| DC_1-3-7_n28 | n28 | 0.2 | +| DC_1-3-7_n78 | 1 | 0.3 | +| | 3 | 0.3 | +| | 7 or n7 | 0.3 | +| | n78 | 0.5 | +| DC_1-3-8_n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 8 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-19_n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-20_n28 | 20 | 0.2 | +| | n28 | 0.2 | +| DC_1-3-20_n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-21_n77 | 1 | 0.2 | +| | 3 | 0.3 | +| | 21 | 0.5 | +| | n77 | 0.5 | +| DC_1-3-21_n78 | 1 | 0.2 | +| | 3 | 0.3 | +| | 21 | 0.5 | +| | n78 | 0.5 | +| DC_1-3-21_n79 | 3 | 0.3 | +| | 21 | 0.5 | +| DC_1-3-28_n78
DC_1-3_n28-n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 28 or n28 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-42_n78 | 1 | 0.2 | + +| | | | +|--------------------|-----|-----| +| | 3 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_1-3-42_n79 | 1 | 0.2 | +| | 3 | 0.2 | +| | 42 | 0.5 | +| DC_1-3_n77-n79 | 1 | 0.2 | +| | 3 | 0.2 | +| | n77 | 0.5 | +| DC_1-3_n78-n79 | 1 | 0.2 | +| | 3 | 0.2 | +| | n78 | 0.5 | +| DC_1-3_SUL_n78-n80 | 1 | 0.2 | +| | 3 | 0.2 | +| | n78 | 0.5 | +| DC_1-7-20_n28 | 20 | 0.2 | +| | n28 | 0.2 | +| DC_1-7-20_n78 | 1 | 0.2 | +| | 7 | 0.2 | +| | 20 | 0.2 | +| | n78 | 0.5 | +| DC_1-7-28_n78 | 1 | 0.2 | +| | 7 | 0.2 | +| | 28 | 0.2 | +| | n78 | 0.5 | +| DC_1-7_n28-n78 | 1 | 0.2 | +| | 7 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_1-19-42_n77 | 1 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_1-19-42_n78 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_1-19-42_n79 | 42 | 0.5 | +| DC_1-19_n77-n79 | 1 | 0.3 | +| | 19 | 0.3 | +| | n77 | 0.5 | +| DC_1-19_n78-n79 | 1 | 0.3 | +| | 19 | 0.3 | +| | n78 | 0.5 | +| DC_1-20_n28-n78 | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_1-21-42_n77 | 1 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_1-21-42_n78 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_1-21-42_n79 | 42 | 0.5 | +| DC_1-21_n77-n79 | n77 | 0.5 | +| DC_1-21_n78-n79 | n78 | 0.5 | +| DC_1-42_n77-n79 | 1 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_1-42_n78-n79 | 1 | 0.2 | +| | | | + +| | | | +|------------------------------------|-----------|-----| +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_2-7-13_n66 | 2 | 0.3 | +| | 7 | 0.5 | +| | n66 | 0.5 | +| DC_2-7-66_n66
DC_2-7-7-66_n66 | 2 | 0.3 | +| | 7 | 0.5 | +| | 66 | 0.5 | +| | n66 | | +| DC_2-7-66_n78
DC_2-7-7-66_n78 | 2 | 0.6 | +| | 7 | 0.5 | +| | 66 | 0.6 | +| | n78 | 0.8 | +| DC_2-13-66_n77 | 2 | 0.3 | +| | 66 | 0.3 | +| | n77 | 0.5 | +| DC_2-14-66_n2
DC_2-14-66-66_n2 | 2 | 0.3 | +| | 66 | 0.3 | +| | n2 | 0.3 | +| DC_2-14-66_n66
DC_2-2-14-66_n66 | 2 | 0.3 | +| | 66 | 0.3 | +| | n66 | 0.3 | +| DC_2-30-66_n5 | 2 | 0.4 | +| | 30 | 0.5 | +| | 66 | 0.4 | +| DC_2-66_n5-n77 | 2 | 0.3 | +| | 66 | 0.3 | +| | n77 | 0.5 | +| DC_2-66-(n)71 | 2 | 0.3 | +| | 66 | 0.3 | +| DC_3-7_n1-n78 | 3 | 0.3 | +| | 7 | 0.3 | +| | n1 | 0.3 | +| | n78 | 0.5 | +| DC_3-7-20_n28 | 20 | 0.2 | +| | n28 | 0.1 | +| DC_3-7-20_n78 | 3 | 0.2 | +| | 7 | 0.2 | +| | n78 | 0.5 | +| DC_3-7-28_n78
DC_3-7_n28-n78 | 3 | 0.2 | +| | 7 | 0.2 | +| | 28 or n28 | 0.2 | +| | n78 | 0.5 | +| DC_3-19-21_n78 | 3 | 0.3 | +| | 21 | 0.5 | +| | n78 | 0.5 | +| DC_3-19-21_n79 | 3 | 0.3 | +| | 21 | 0.5 | +| DC_3-19-42_n77 | 3 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_3-19-42_n78 | 3 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_3-19-42_n79 | 3 | 0.2 | +| | 42 | 0.5 | +| DC_3-19_n78-n79 | 3 | 0.2 | + +| | | | +|------------------|-----|----------------------------------| +| | n78 | 0.5 | +| DC_3-20_n28-n78 | 3 | 0.2 | +| | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_3-21_n77-n79 | 3 | 0.3 | +| | 21 | 0.5 | +| | n77 | 0.5 | +| DC_3-21_n78-n79 | 3 | 0.3 | +| | 21 | 0.5 | +| | n78 | 0.5 | +| DC_3-41-42_n77 | 3 | 0.5 | +| | 41 | 0 1 /0.5 2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_3-41-42_n78 | 3 | 0.5 | +| | 41 | 0 1 /0.5 2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_3-41-42_n79 | 3 | 0.5 | +| | 41 | 0 1 /0.5 2 | +| | 42 | 0.5 | +| DC_3-42_n77-n79 | 3 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_3-42_n78-n79 | 3 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_7-20_n28-n78 | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_12-30-66_n260 | 12 | 0.5 | +| | 30 | 0.5 | +| | 66 | 0.4 | +| DC_13-66_n2-n77 | 66 | 0.2 | +| | n2 | 0.2 | +| | n77 | 0.5 | +| DC_19-21-42_n77 | 42 | 0.5 | +| | n77 | 0.5 | +| DC_19-21-42_n78 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_19-21-42_n79 | 42 | 0.5 | +| DC_19-21_n77-n79 | n77 | 0.5 | +| DC_19-21_n78-n79 | n78 | 0.5 | +| DC_19-42_n77-n79 | 42 | 0.5 | +| | n77 | 0.5 | +| DC_19-42_n78-n79 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_21-42_n77-n79 | 42 | 0.5 | +| | n77 | 0.5 | +| DC_21-42_n78-n79 | 42 | 0.5 | +| | | | + +| | n78 | 0.5 | +|---------|-------------------------------------------------------------------------------------------|-----| +| NOTE 1: | The requirement is applied for UE transmitting on the frequency range of 2545 - 2690 MHz. | | +| NOTE 2: | The requirement is applied for UE transmitting on the frequency range of 2496 - 2545 MHz. | | +| NOTE 3: | The requirement is applied for UE transmitting on the frequency range of 2515 - 2690 MHz. | | +| NOTE 4: | The requirement is applied for UE transmitting on the frequency range of 2496 - 2515 MHz. | | +| | | | + +##### 7.3B.3.3.4 $\Delta R_{\text{IB,c}}$ for EN-DC in five bands + +**Table 7.3B.3.3.4-1: $\Delta R_{\text{IB,c}}$ due to EN-DC (five bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta R_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1-3-7-20_n28 | 20 | 0.2 | +| | n28 | 0.2 | +| DC_1-3-7-20_n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 7 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-7-28_n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 7 | 0.2 | +| | 28 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-7_n28-n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 7 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-19-42_n79 | 1 | 0.2 | +| | 3 | 0.2 | +| | 42 | 0.5 | +| DC_1-3-20_n28-n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_1-3-21-42_n78 | 1 | 0.2 | +| | 3 | 0.3 | +| | 21 | 0.5 | +| | 42 | 0.5 | +| | n78 | 0.2 | +| DC_1-3-21-42_n79 | 1 | 0.2 | +| | 3 | 0.3 | +| | 21 | 0.5 | +| | 42 | 0.5 | +| | n79 | 0.0 | +| DC_1-7-20_n28-n78 | 1 | 0.2 | +| | 7 | 0.2 | +| | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | +| DC_1-19-21-42_n78 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_1-19-21-42_n79 | 42 | 0.5 | +| DC_1-19-42_n77-n79 | 1 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_1-19-42_n78-n79 | 42 | 0.5 | +| | n78 | 0.5 | +| DC_1-21-42_n77-n79 | 1 | 0.2 | +| | 21 | 0.2 | +| | 42 | 0.5 | +| | n77 | 0.5 | +| DC_1-21-42_n78-n79 | 21 | 0.2 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_3-7-20_n28-n78 | 3 | 0.2 | + +| | | | +|---------------------|-----|-----| +| | 7 | 0.2 | +| | 20 | 0.2 | +| | n28 | 0.2 | +| DC_3-19-21-42_n78 | 3 | 0.3 | +| | 21 | 0.5 | +| | 42 | 0.5 | +| | n78 | 0.5 | +| DC_3-19-21-42_n79 | 3 | 0.3 | +| | 21 | 0.5 | +| | 42 | 0.5 | +| DC_19-21-42_n77-n79 | 42 | 0.5 | +| | n77 | 0.5 | +| DC_19-21-42_n78-n79 | 42 | 0.5 | +| | n78 | 0.5 | + +NOTE 1: The requirement is applied for UE transmitting on the frequency range of 2545 – 2690 MHz. + +NOTE 2: The requirement is applied for UE transmitting on the frequency range of 2496 – 2545 MHz. + +##### 7.3B.3.3.5 $\Delta R_{IB,c}$ for EN-DC six bands + +**Table 7.3B.3.3.5-1: $\Delta R_{IB,c}$ due to EN-DC (six bands)** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta R_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_1-3-7-20_n28-n78 | 1 | 0.2 | +| | 3 | 0.2 | +| | 7 | 0.2 | +| | 20 | 0.2 | +| | n28 | 0.2 | +| | n78 | 0.5 | + +#### 7.3B.3.3a $\Delta R_{IB,c}$ for Inter-band NE-DC within FR1 + +Unless $\Delta R_{IB,c}$ is specified in this clause, the value of $\Delta R_{IB,c}$ for the correspondingly specified EN-DC configuration in clause 7.3B.3.3 is applicable. + +#### 7.3B.3.4 Reference sensitivity for $\Delta R_{IB,c}$ Inter-band EN-DC including FR2 + +The $\Delta R_{IB,c}$ for NR FR2 band of inter-band CA defined in tables 5.5B.5.1-1 to 5.5B.5.5-1 is set to zero. + +#### 7.3B.3.5 Reference sensitivity for $\Delta R_{IB,c}$ Inter-band EN-DC including both FR1 and FR2 + +The $\Delta R_{IB,c}$ for NR FR2 band of inter-band CA defined in tables 5.5B.6.2-1 to 5.5B.6.5-1 is set to zero and $\Delta R_{IB,c}$ for constituent E-UTRA and NR FR1 bands is the same as those for the corresponding inter band EN-DC configuration without the NR FR2 bands specified in 7.3B.3.3. + +#### 7.3B.4 EIS Spherical Coverage for Inter-band EN-DC including FR2 (1 NR CC) + +Editor's note: The following aspects are either missing or not yet determined: + +- Measurement Uncertainties and Test Tolerances are FFS for power class 2 and 4. + +#### 7.3B.4.1 Test purpose + +Same test purpose as in clause 7.3.4.1 in TS 38.521-2 [9] for the NR carrier. + +#### 7.3B.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR DL CC. + +#### 7.3B.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.3.4.3 in TS 38.521-2 [9] for the NR carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-2 [9] clause 7.3.4. + +#### 7.3B.4.4 Test description + +##### 7.3B.4.4.1 Initial conditions + +Same test description as in clause 7.3.4.4 in TS 38.521-2 [9] for the NR carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1. For Initial conditions as in clause 7.3.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.3.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 7.3.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +#### 7.3B.4.5 Test requirement + +Same test requirement as in clause 7.3.4.5 in TS 38.521-2 [9] for the NR carrier. + +## 7.4 Void + +## 7.4A Maximum Input Level for CA + +### 7.4A.1 Test purpose + +Same test purpose as in clause 7.4 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 7.4 in TS 38.521-2 [9] for NR FR2 carrier(s). + +### 7.4A.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for maximum input level apply and are tested in TS 38.521-1 [8] clause 7.4 and 7.4A and TS 38.521-2 [9] clauses 7.4 and 7.4A. + +## 7.4B Maximum Input Level for DC + +### 7.4B.0 Minimum conformance requirement + +#### 7.4B.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC maximum input level requirement and parameters are defined in Table 7.4B.0.1-1. + +**Table 7.4B.0.1-1: Maximum Input** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| Power in Largest CC, E-UTRA or NR, dBm | $X^1$ | +| Power in each other CC, dBm | $X^1 - 10 \cdot \log_{10}(N_x \text{SCS}_x / N_y \text{SCS}_y)$ | +| NOTE 1: Power in Largest E-UTRA or NR bandwidth CC, listed in Table 7.4-1 [2]
NOTE 2: $N_x$ , $\text{SCS}_x$ is the number of RB's and Sub carrier spacing in the largest carrier bandwidth and could be LTE or NR carrier
NOTE 3: $N_y$ , $\text{SCS}_y$ is the number of RB's in any other carrier.
NOTE 4: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L}}$ at the minimum uplink configuration specified in Table 7.3.2-3 [2] with $P_{\text{CMAX\_L}}$ as defined in clause 6.2B.4.
NOTE 5: For E-UTRA carrier, the transmitter shall be set to 29dB below $P_{\text{CMAX\_L}}$ at the minimum uplink configuration specified in Table 7.3.1-2 [5] with $P_{\text{CMAX\_L}}$ as defined in clause 6.2B.4. | | + +#### 7.4B.0.2 Intra-band non-contiguous EN-DC + +For the E-UTRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.4.1 for single carrier operation and in clause 7.4.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.4 in TS 38.101-1 [2]. + +#### 7.4B.0.3 Inter-band EN-DC within FR1 + +Maximum input level requirement for E-UTRA single carrier and CA operation specified in clauses 7.4.1 and 7.4.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.4 and 7.4A of TS 38.101-1 [2] apply. + +#### 7.4B.0.4 Inter-band EN-DC including FR2 + +Maximum input level requirement for E-UTRA single carrier and CA operation specified in clauses 7.4.1 and 7.4.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.4 and 7.4A of TS 38.101-2 [3] apply. + +#### 7.4B.0.5 Inter-band EN-DC including both FR1 and FR2 + +Maximum input level requirement for E-UTRA single carrier and CA operation specified in clauses 7.4.1 and 7.4.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.4 and 7.4A of TS 38.101-1 [2] and TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.4B. + +### 7.4B.1 Maximum Input Level for Intra-Band Contiguous EN-DC (2 CCs) + +#### 7.4B.1.1 Test purpose + +Maximum input level for intra-band contiguous EN-DC tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, under conditions of high signal level, ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area near to an e-NodeB or a gNB. + +#### 7.4B.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.4B.1.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.1 for the intra-band contiguous EN-DC maximum input level requirement. + +Exception requirements are defined for this test, therefore LTE agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +The normative reference for this requirement is TS 38.101-3 [4] Clause 7.4B.1. + +#### 7.4B.1.4 Test Description + +##### 7.4B.1.4.1 Initial Condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in table 5.5B.2-1, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each intra-band contiguous EN-DC configuration specified in clause 5.3B.1.2, and are shown in table 7.4B.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A.2 for E-UTRA RMC for FDD, and TS 38.521-1 [8] Annex A.2 for NR RMC Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.4B.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------|--------------------------|-----------------------------|-----------------------------|-------------------------|--------------------------|-----------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | Mid range | | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 5) | | | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest | | | | | | | | +| Test Parameters for Intra-band Contiguous EN-DC Configuration | | | | | | | | | +| Downlink Configuration | | | | | Uplink Configuration | | | | +| Test ID | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| 1 | CP-OFDM 64QAM | Full RB (NOTE 1) | CP-OFDM 64QAM | Full RB | DFT-s-OFDM QPSK | NOTE 2 | QPSK | NOTE 3 | +| 2 | CP-OFDM 256QAM | Full RB (NOTE 1) | CP-OFDM 256QAM | Full RB | DFT-s-OFDM QPSK | NOTE 2 | QPSK | NOTE 3 | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Same RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 3: Same RB allocation shall be used per the E-UTRA band and channel BW as specified in Table 7.3.3-2 of TS 36.521 [10]. + +NOTE 4: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. + +NOTE 5: If the UE supports multiple CC combinations in the EN-DC configuration with the same NRB\_agg, select the combination to test as follows: +- Lowest ENBW: NR component with lowest NRB is tested. +- Highest ENBW: NR component with highest NRB is tested. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.1 for SS diagram and A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0, C.1, C.2, C.3.1 and TS 38.521-1 [8] Annex C.0, C.1, C.2, C.3.1 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H.0, H.1, H.2, H.3.1 and TS 38.521-1 [8] Annex G.0, G.1, G.2, G.3.1 for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are TS 36.521-1 [10] Annex A.2 and TS 38.521-1 [8] Annex A.2 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.4B.1.4.3. + +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +##### 7.4B.1.4.2 Test Procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Tables 7.4B.1.4.1 on the E-UTRA CC and NR CC. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.4B.1.4.1-1 on the E-UTRA CC and NR CC. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. SS sets the Downlink signal level for the E-UTRA CC and NR CC to the value defined in Table 7.4B.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(MU + \text{Uplink power control window size})$ dB of the target power level in Table 7.4B.1.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Measure the average throughput for each component carrier for duration sufficient to achieve statistical significance according to Annex H.2 in TS 38.521-1 [8] for NR band, and Annex G.2 of TS 36.521-1 [10] for EUTRA band. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +**Table 7.4B.1.4.2-1: Void** + +##### 7.4B.1.4.3 Message Contents + +Message contents are according to TS 36.508-1 [11] clause 4.6.1 and TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +#### 7.4B.1.5 Test Requirement + +The throughput measurement of each CC derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels with parameters specified in Table 7.4B.1.5-1 + +**Table 7.4B.1.5-1: Maximum input level requirement for each CC** + +| Channel bandwidth of Largest BW CC | Rx Parameter | | | | +|------------------------------------|-------------------------|---------------------------------------------------------|-------------------------|---------------------------------------------------------| +| | Power in the Largest CC | Power in the other CC | Power in the Largest CC | Power in the other CC | +| 5 MHz | -25 2 -TT | $-25^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -27 3 -TT | $-27^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 10 MHz | -25 2 -TT | $-25^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -27 3 -TT | $-27^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 15 MHz | -25 2 -TT | $-25^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -27 3 -TT | $-27^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 20 MHz | -25 2 -TT | $-25^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -27 3 -TT | $-27^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 25 MHz | -24 2 -TT | $-24^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -26 3 -TT | $-26^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 30 MHz | -23 2 -TT | $-23^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -25 3 -TT | $-25^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 40 MHz | -22 2 -TT | $-22^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -24 3 -TT | $-24^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 50 MHz | -21 2 -TT | $-21^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -23 3 -TT | $-23^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 60 MHz | -20 2 -TT | $-20^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -22 3 -TT | $-22^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 80 MHz | -20 2 -TT | $-20^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -22 3 -TT | $-22^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 90 MHz | -20 2 -TT | $-20^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -22 3 -TT | $-22^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | +| 100 MHz | -20 2 -TT | $-20^2 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | -22 3 -TT | $-22^3 - 10 \cdot \log_{10}(N_x SCS_x / N_y SCS_y)$ -TT | + +NOTE 1: $N_x$ , $SCS_x$ is the number of RB's and Sub carrier spacing in the largest carrier bandwidth and could be LTE or NR carrier. + +NOTE 2: Reference measurement channel refers to Clauses A.3.2.3 or A.3.3.3 in TS 38.521-1 [8] for 64-QAM NR Carrier, and to Tables A.3.2-3, A.3.2-4 for 64QAM in TS 36.521-1 [10] for E-UTRA Carrier. + +NOTE 3: Reference measurement channel refers to Clauses A.3.2.4 or A.3.3.4 in TS 38.521-1 [8] for 256QAM NR Carrier, and Tables A.3.2-5, A.3.2-6 in TS 36.521-1 [10] for 256QAM E-UTRA Carrier. + +NOTE 4: $N_y$ , $SCS_y$ is the number of RB's in any other carrier + +NOTE 5: For NR carrier, the transmitter shall be set to 4dB below PCMAX\_L at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with PCMAX\_L as defined in clause 6.2B.4. + +NOTE 6: For E-UTRA carrier, the transmitter shall be set to 29dB below PCMAX\_L at the minimum uplink configuration specified in Table 7.3.1-2 in TS 38.101-3 [4] with PCMAX\_L as defined in clause 6.2B.4 for single carrier. + +NOTE 7: TT for each frequency is specified in Table 7.4B.1.5-2 + +**Table 7.4B.1.5-2: Test Tolerance (Maximum input level)** + +| $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 6.0\text{GHz}$ | +|------------------------|----------------------------------------| +| 0.7 dB | 1.0 dB | + +### 7.4B.2 Maximum Input Level for Intra-Band Non-Contiguous EN-DC (2 CCs) + +#### 7.4B.2.1 Test purpose + +Maximum input level for intra-band non-contiguous EN-DC tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, under conditions of high signal level, ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area near to an e-NodeB or a gNB. + +#### 7.4B.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.4B.2.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.2 for the intra-band non-contiguous EN-DC maximum input level requirement. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.4B.2, and TS 38.101-1 [2] clause 7.4, and TS 38.101-2 [3] clauses 7.4 and 7.4A + +No exception requirements for E-UTRA CG and NR CG, LTE agnostic approach applies. + +#### 7.4B.2.4 Test Description + +Same test description as in clause 7.4.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions in the initial test configuration. + +- The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.3, all of these configurations shall be tested with applicable test parameters for each intra-band non-contiguous EN-DC configuration specified in clause 5.3B.1.3, and are shown in table 7.4B.2.4.1-1. + +**Table 7.4B.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------|-------------------|----------------------|----------------------|------------------|-------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 | MaxWGap for intra-band non-contiguous EN-DC | | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1 across bandwidth combination sets supported by the UE | Lowest, Mid, Highest of Channel BW for NR CC | | | | | | | | +| Test SCS for the NR cell as specified in TS 38.521-1 [8] Table 5.3.5-1 | Lowest | | | | | | | | +| Test Parameters for EN-DC Configuration | | | | | | | | | +| Downlink Configuration | | | | | Uplink Configuration | | | | +| Test ID | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| 1 | CP-OFDM 64QAM | NOTE 1 | NOTE 2 | NOTE 2 | DFT-s-OFDM QPSK | NOTE 1 | NOTE 2 | NOTE 2 | +| 2 | CP-OFDM 256QAM | NOTE 1 | NOTE 2 | NOTE 2 | DFT-s-OFDM QPSK | NOTE 1 | NOTE 2 | NOTE 2 | +| NOTE 1: Same RB allocation shall be used per modulation as specified in Table 7.4.4.1-1 of TS 38.521-1 [8].
NOTE 2: Modulation and RB allocation for E-UTRA CC refers to the Table 4.6-2.
NOTE 3: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected. | | | | | | | | | + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.6-1 with the exception that + +- E-UTRA test frequency are specified in Table 7.4B.2.4.1-1 based on intra-band non-contiguous EN-DC configuration specified in clause 5.3B.1.3. + +For Initial conditions as in clause 7.4.4.1 in TS 38.521-1 [8] with the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 6.4.1.4.1 in TS 38.521-1 [8] is replaced by the following three steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +#### 7.4B.2.5 Test Requirement + +Same test requirement as in clause 7.4.5 in TS 38.521-1 [8] for NR carrier. + +### 7.4B.3 Maximum Input Level for Inter-band EN-DC within FR1 (1 NR CC) + +#### 7.4B.3.1 Test purpose + +Same test purpose as in clause 7.4.1 in TS 38.521-1 [8] for the NR carrier. + +#### 7.4B.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR DL CC. + +#### 7.4B.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.4.3 in TS 38.521-1 [8] for the NR carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.4B.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.4B.3.4 Test Description + +Same test description as in clause 7.4.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.4.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.4.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +#### 7.4B.3.5 Test Requirement + +Same test requirement as in clause 7.4.5 in TS 38.521-1 [8] for the NR carrier. + +#### 7.4B.3\_1 Maximum Input Level for EN-DC within FR1 (>2 CCs) + +##### 7.4B.3\_1.1 Maximum Input Level for EN-DC within FR1 (3 CCs) + +Editor's note: The following aspects are either missing or not yet determined: + +- Only inter-band EN-DC and intra-band non-contiguous EN-DC within FR1 are considered. Testing of intra-band contiguous EN-DC is FFS. + +###### 7.4B.3\_1.1.1 Test purpose + +Same test purpose as in clause 7.4B.3.1. + +###### 7.4B.3\_1.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band or intra-band non-contiguous EN-DC within FR1 with 2 NR DL CCs and one or more E-UTRA DL CC(s). + +###### 7.4B.3\_1.1.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.2 for the intra-band non-contiguous EN-DC and Clause 7.4B.0.3 for the inter-band EN-DC within FR1 maximum input level requirement. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.4B.3\_1.1.4 Test Description + +Same test description as in clause 7.4A.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.4A.1.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. + +3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.4A.1.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.4B.3\_1.1.5 Test Requirement + +Same test requirement as specified in TS 38.521-1 [8] clause 7.4A.1.5 for the NR carrier(s). + +##### 7.4B.3\_1.2 Maximum Input Level for EN-DC within FR1 (4 CCs) + +Editor's note: The following aspects are either missing or not yet determined: + +- Only inter-band EN-DC and intra-band non-contiguous EN-DC within FR1 are considered. Testing of intra-band contiguous EN-DC is FFS. + +###### 7.4B.3\_1.2.1 Test purpose + +Same test purpose as in clause 7.4B.3.1. + +###### 7.4B.3\_1.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band or intra-band non-contiguous EN-DC within FR1 with 3 NR DL CCs and one or more E-UTRA DL CC(s). + +###### 7.4B.3\_1.2.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.2 for the intra-band non-contiguous EN-DC and 7.4B.0.3 for the inter-band EN-DC within FR1 maximum input level requirement. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.4B.3\_1.2.4 Test Description + +Same test description as in clause 7.4A.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.4A.2.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.4A.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.4B.3\_1.2.5 Test Requirement + +Same test requirement as specified in TS 38.521-1 [8] clause 7.4A.2.5 for the NR carriers. + +##### 7.4B.3\_1.3 Maximum Input Level for EN-DC within FR1 (5 CCs) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- Only inter-band EN-DC and intra-band non-contiguous EN-DC within FR1 are considered. Testing of intra-band contiguous EN-DC is FFS. + +###### 7.4B.3\_1.3.1 Test purpose + +Same test purpose as in clause 7.4B.3.1. + +###### 7.4B.3\_1.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band or intra-band non-contiguous EN-DC within FR1 with 4 NR DL CCs and one or more E-UTRA DL CC(s). + +###### 7.4B.3\_1.3.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.2 for the intra-band non-contiguous EN-DC and Clause 7.4B.0.3 for the inter-band EN-DC within FR1 maximum input level requirement. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.4B.3\_1.3.4 Test Description + +Same test description as in clause 7.4A.3.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.4A.3.4.1 in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. + +3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.4A.3.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.4B.3\_1.3.5 Test Requirement + +Same test requirement as specified in TS 38.521-1 [8] clause 7.4A.3.5 for the NR carrier(s). + +##### 7.4B.3\_1.4 Maximum Input Level for EN-DC within FR1 (6 CCs) + +**Editor's note:** The test case in this clause is incomplete, the following aspects are either missing or not yet determined: + +- Only inter-band EN-DC and intra-band non-contiguous EN-DC within FR1 are considered. Testing of intra-band contiguous EN-DC is FFS. +- The referred test case 7.4A.4 in TS 38.521-1 [8] is incomplete. + +###### 7.4B.3\_1.4.1 Test purpose + +Same test purpose as in clause 7.4B.3.1. + +###### 7.4B.3\_1.4.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band or intra-band non-contiguous EN-DC within FR1 with 5 NR DL CCs and one or more E-UTRA DL CC(s). + +7.4B.3\_1.4.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.2 for the intra-band non-contiguous EN-DC and Clause 7.4B.0.3 for the inter-band EN-DC within FR1 maximum input level requirement. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.4B.3\_1.4.4 Test Description + +Same test description as in clause [7.4A.4.4] in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause [7.4A.4.4.1] in TS 38.521-1 [8], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for the cell are set up according to TS 36.508 [11] subclause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause [7.4A.4.4.1] in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 7.4B.3\_1.4.5 Test Requirement + +Same test requirement as specified in TS 38.521-1 [8] clause [7.4A.4.5] for the NR carrier(s). + +### 7.4B.3a Maximum Input Level for inter-band NE-DC within FR1 (2 CCs) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 7.4 and 7.4A of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 7.4 and 7.4A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +### 7.4B.4 Maximum Input Level for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The referred test case 7.4 in TS 38.521-2 is incomplete. + +#### 7.4B.4.1 Test purpose + +Same test purpose as in clause 7.4 in TS 38.521-2 [9] for the *NR* carrier. + +#### 7.4B.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR DL CC. + +The minimum conformance requirements of NR FR2 carrier in this test case are not testable due to maximum input level unachievable in IFF OTA test setup. Other test setups have not been analysed. Thus the test case will not be tested as part of UE conformance testing. + +NOTE: As a result TC 7.4B.4 has not been included in the test case applicability table 4.1.3-1, TS 38.522. This does not preclude the test from being used for R&D or other purposes if deemed useful to all types of NR UE release 15 and forward. + +#### 7.4B.4.3 Minimum conformance requirements + +Refer to Clause 7.4B.0.4 for the inter-band EN-DC including FR2 maximum input level requirement. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.4B.4.4 Test description + +Same test description as in clause 7.4.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 7.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 7.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +#### 7.4B.4.5 Test requirement + +Same test requirement as in clause 7.4.5 in TS 38.521-2 [9] for the *NR* carrier. + +#### 7.4B.4\_1 Maximum Input Level for inter-band EN-DC including FR2 (>1 NR CC) + +##### 7.4B.4\_1.1 Maximum Input Level for Inter-Band EN-DC including FR2 (2 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 7.4A.1 in TS 38.521-2 is incomplete. + +###### 7.4B.4\_1.1.1 Test purpose + +Same test purpose as in clause 7.4 in TS 38.521-2 [9] for the NR carrier. + +###### 7.4B.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR DL CCs. + +The minimum conformance requirements of NR FR2 carrier in this test case are not testable due to maximum input level unachievable in IFF OTA test setup. Other test setups have not been analysed. Thus the test case will not be tested as part of UE conformance testing. + +NOTE: As a result TC 7.4B.4\_1.1 has not been included in the test case applicability table 4.1.3-1, TS 38.522. This does not preclude the test from being used for R&D or other purposes if deemed useful to all types of NR UE release 15 and forward. + +###### 7.4B.4\_1.1.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.4B.4.3. + +###### 7.4B.4\_1.1.4 Test description + +Same test description as in 7.4A.1.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in 7.4A.1.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS36.521-1 [10]. + +Step 6 of Initial conditions as in 7.4A.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in 7.4A.1.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 7.4B.4\_1.1.5 Test Requirements + +Same test requirement as in 7.4A.1.5 in TS 38.521-2 [9] for the *NR* carrier(s). + +##### 7.4B.4\_1.2 Maximum Input Level for Inter-Band EN-DC including FR2 (3 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 7.4A.1 and 7.4A.2 in TS 38.521-2 is incomplete. + +###### 7.4B.4\_1.2.1 Test purpose + +Same test purpose as in clause 7.4 in TS 38.521-2 [9] for the *NR* carrier. + +###### 7.4B.4\_1.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 3 NR DL CCs. + +The minimum conformance requirements of NR FR2 carrier in this test case are not testable due to maximum input level unachievable in IFF OTA test setup. Other test setups have not been analysed. Thus the test case will not be tested as part of UE conformance testing. + +NOTE: As a result TC 7.4B.4\_1.2 has not been included in the test case applicability table 4.1.3-1, TS 38.522. This does not preclude the test from being used for R&D or other purposes if deemed useful to all types of NR UE release 15 and forward. + +###### 7.4B.4\_1.2.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.4B.4.3. + +###### 7.4B.4\_1.2.4 Test description + +Same test description as in 7.4A.2.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 7.4A.2.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS36.521-1 [10]. + +Step 6 of Initial conditions as in 7.4A.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in 7.4A.2.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 7.4B.4\_1.2.5 Test Requirements + +Same test requirement as in clause 7.4A.2.5 in TS 38.521-2 [9] for the *NR* carrier(s). + +##### 7.4B.4\_1.3 Maximum Input Level for Inter-Band EN-DC including FR2 (4 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 7.4A.1, 7.4A.2 and 7.4A.3 in TS 38.521-2 is incomplete. + +###### 7.4B.4\_1.3.1 Test purpose + +Same test purpose as in clause 7.4 in TS 38.521-2 [9] for the *NR* carrier. + +###### 7.4B.4\_1.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 4 NR DL CCs. + +The minimum conformance requirements of NR FR2 carrier in this test case are not testable due to maximum input level unachievable in IFF OTA test setup. Other test setups have not been analysed. Thus the test case will not be tested as part of UE conformance testing. + +**NOTE:** As a result TC 7.4B.4\_1.3 has not been included in the test case applicability table 4.1.3-1, TS 38.522. This does not preclude the test from being used for R&D or other purposes if deemed useful to all types of NR UE release 15 and forward. + +###### 7.4B.4\_1.3.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.4B.4.3. + +###### 7.4B.4\_1.3.4 Test description + +Same test description as in 7.4A.3.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in 7.4A.3.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. + - 3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS36.521-1 [10]. +- Step 6 of Initial conditions as in 7.4A.3.4.1 in TS 38.521-2 [9] is replaced by: +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in 7.4A.3.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 7.4B.4\_1.2.5 Test Requirements + +Same test requirement as in 7.4A.3.5 in TS 38.521-2 [9] for the *NR* carrier(s). + +##### 7.4B.4\_1.4 Maximum Input Level for Inter-Band EN-DC including FR2 (5 NR CCs) + +**Editor's note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- The referred test case 7.4A.4 in TS 38.521-2 is incomplete. + +###### 7.4B.4\_1.4.1 Test purpose + +Same test purpose as in clause 7.4 in TS 38.521-2 [9] for the *NR* carrier. + +###### 7.4B.4\_1.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 5 NR DL CCs. + +The minimum conformance requirements of NR FR2 carrier in this test case are not testable due to maximum input level unachievable in IFF OTA test setup. Other test setups have not been analysed. Thus the test case will not be tested as part of UE conformance testing. + +**NOTE:** As a result TC 7.4B.4\_1.4 has not been included in the test case applicability table 4.1.3-1, TS 38.522. This does not preclude the test from being used for R&D or other purposes if deemed useful to all types of NR UE release 15 and forward. + +###### 7.4B.4\_1.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.4B.4.3. + +###### 7.4B.4\_1.4.4 Test description + +Same test description as in 7.4A.4.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in 7.4A.4.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +2.1 The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] subclause 4.4.3. + +3.1 The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.4A.4.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 7.4A.4.4.2 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set TimeAlignmentTimerDedicated IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 7.4B.4\_1.4.5 Test Requirements + +Same test requirement as in 7.4A.4.5 in TS 38.521-2 [9] for the *NR* carrier(s). + +### 7.4B.4D Maximum Input Level for inter-band EN-DC including FR2 for UL MIMO + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach can be applied and only NR carriers need to be tested. + +No test case details are specified. Given UE's Rx performance would not be impacted by the Tx configuration in NR FR2 TDD bands, the requirements in this test case can be well covered in 7.4B.4 and 7.4B.4\_1 and don't need to be tested again. + +### 7.4B.5 Maximum Input Level for inter-band EN-DC including both FR1 and FR2 + +#### 7.4B.5.1 Test purpose + +Same test purpose as in clause 7.4.1 in TS 38.521-1 [8] for NR FR1 carrier and 7.4.1 in TS 38.521-2 [9] for NR FR2 carrier. + +#### 7.4B.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum input level apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.4B. + +### 7.4B.5D Maximum Input Level for inter-band EN-DC including FR1 and FR2 for UL MIMO + +#### 7.4B.5D.1 Test purpose + +Same test purpose as in clause 7.4D.1 in TS 38.521-1 [8] for NR FR1 carrier and 7.4D.1 in TS 38.521-2 [9] for NR FR2 carrier. + +#### 7.4B.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for maximum input level apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.4B. + +## 7.5 Void + +## 7.5A Adjacent Channel Selectivity for CA + +### 7.5A.0 Test purpose + +Same test purpose as in clauses 7.5 and 7.5A in TS 38.521-1 [8] for NR FR1 carrier(s) and clauses 7.5 and 7.5A in TS 38.521-2 [9] for NR FR2 carrier(s). + +### 7.5A.1 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for adjacent channel selectivity apply and are tested in clauses 7.5 and 7.5A in TS 38.521-1 [8] and clauses 7.5 and 7.5A in TS 38.521-2 [9]. + +## 7.5B Adjacent channel selectivity for DC + +### 7.5B.0 Minimum Conformance Requirements + +#### 7.5B.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC ACS requirement and parameters are defined for test case 1 in Table 7.5B.0.1-1 and for test case 2 in Table 7.5B.0.1-2. + +**Table 7.5B.0.1-1: ACS test case 1** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------------|--------------------------|---------------------------| +| ACS, dB | X 1 | 19.2 | 18.5 | 17.9 | +| P interferer , dBm | P i 2 | Aggregated power + 17.7 dB | Aggregated power + 17 dB | Aggregated power + 16.4dB | +| P w in Transmission BW configuration, per CC, dBm | REFSENS +14dB | | | | +| NOTE 1: X is ACS level at the specified EN-DC aggregated Bandwidth from Table 7.5.1A-1 in TS 36.101 [5]
NOTE 2: P i is from Table 7.5.1A-2 in TS 36.101 [5]
NOTE 3: Jammer BW and offset is from Table 7.5.1A-2 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier
NOTE 4: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c,NR at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with P CMAX_L,f,c,NR as defined in clause 6.2B.4 from TS 38.101-3 [4].
NOTE 5: For E-UTRA carrier, the transmitter shall be set to 4dB below P CMAX_L_E-UTRA,c at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with P CMAX_L_E-UTRA,c as defined in clause 6.2B.4 from TS 38.101-3 [4] for single carrier. | | | | | + +**Table 7.5B.0.1-2: ACS test case 2** + +| EN-DC Aggregated Bandwidth, ENBW, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------------------------------------------| +| P w in Transmission Bandwidth Configuration, perCC, dBm | P w 1 | -42.7
+10log 10 (N RB,c /N RB_agg ) | -42
+10log 10 (N RB,c /N RB_agg ) | -41.4
+10log 10 (N RB,c /N RB_agg ) | +| P interferer , dBm | -25 | | | | +| NOTE 1: P w is wanted signal power level at the specified EN-DC aggregated Bandwidth from Table 7.5.1A-3 in TS 36.101 [5]
NOTE 2: Jammer BW and offset is from Table 7.5.1A-3 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier
NOTE 3: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c,NR at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with P CMAX_L,f,c,NR as defined in clause 6.2B.4 from TS 38.101-3 [4].
NOTE 4: For E-UTRA carrier, the transmitter shall be set to 29dB below P CMAX_L,E-UTRA,c at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with P CMAX_L,E-UTRA,c as defined in clause 6.2B.4 from TS 38.101-3 [4] for single carrier. | | | | | + +#### 7.5B.0.2 Intra-band non-contiguous EN-DC + +For the E-UTRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.5.1 for single carrier operation and in clause 7.5.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.5 in TS 38.101-1 [2]. + +The blocker configuration is defined in the general clause 7.1 in TS 38.101-3 [4]. + +#### 7.5B.0.3 Inter-band EN-DC within FR1 + +Adjacent channel selectivity requirement for E-UTRA single carrier and CA operation specified in clauses 7.5.1 and 7.5.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.5 and 7.5A of TS 38.101-1 [2] apply. + +#### 7.5B.0.3a Inter-band NE-DC within FR1 + +Adjacent channel selectivity requirement for E-UTRA single carrier and CA operation specified in subclauses 7.5.1 and 7.5.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in subclauses 7.5 and 7.5A of TS 38.101-1 [2] apply. + +#### 7.5B.0.4 Inter-band EN-DC including FR2 + +Adjacent channel selectivity requirement for E-UTRA single carrier and CA operation specified in clauses 7.5.1 and 7.5.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.5 and 7.5A of TS 38.101-2 [3] apply. + +##### 7.5B.0.4a Inter-band NE-DC including FR2 + +Adjacent channel selectivity requirement for E-UTRA single carrier and CA operation specified in clauses 7.5.1 and 7.5.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.5 and 7.5A of TS 38.101-2 [3] apply. + +#### 7.5B.0.5 Inter-band EN-DC including both FR1 and FR2 + +Adjacent channel selectivity requirement for E-UTRA single carrier and CA operation specified in clauses 7.5.1 and 7.5.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.5 and 7.5A of TS 38.101-1 [2] and TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.5B.1, 7.5B.2, 7.5B.3, 7.5B.3a, 7.5B.4, 7.5B.4a, and 7.5B.5. + +### 7.5B.1 Adjacent Channel Selectivity for intra-band contiguous EN-DC (2 CCs) + +#### 7.5B.1.1 Test purpose + +Adjacent channel selectivity (ACS) is a measure of a receiver's ability to receive an NR and E-UTRA signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent channel(s). + +#### 7.5B.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.5B.1.3 Minimum conformance requirements + +Refer to Clause 7.5B.0.1 for the intra-band contiguous EN-DC in FR1. + +Exception requirements are applicable for NR, therefore LTE anchor agnostic approach is not applied. E-UTRA test points are defined and measurements performed over the aggregated EN-DC bandwidth. + +#### 7.5B.1.4 Test description + +##### 7.5B.1.4.1 Initial Condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in table 5.5B.2-1, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each intra-band contiguous EN-DC configuration specified in clause 5.5B.2, and are shown in Table 7.5B.1.4.1-1. + +In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2 for E-UTRA RMC for TDD, TS 36.521-1 [10] Annex A.2 for E-UTRA RMC for FDD, TS 38.521-1 [8] Annex A.2 for NR UL RMC and TS 38.521-1 [8] Annex A.3 for NR DL RMC. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.5B.1.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------|--------------------------|-----------------------------|-----------------------------|-------------------------|--------------------------|-----------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest supported SCS | | | | | | | | +| NR/E-UTRA Test Parameters | | | | | | | | | +| | Downlink Configuration | | | | Uplink Configuration | | | | +| Test ID | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| 1 | CP-OFDM QPSK | Full RB (NOTE 1) | QPSK | Full RB | DFT-s-OFDM QPSK | REFSENS_NR | QPSK | REFSENS_LTE | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB\_agg, only the combination with the highest NRB\_scg is tested. + +NOTE 4: REFSENS\_NR and REFSENS\_LTE refer to Uplink configuration in Table 7.3.2.4.1-1 in TS 38.521-1 [8] and Table 7.3.4.1-1 in TS 36.521 [10] for NR and E-UTRA CC respectively. + +NOTE 5: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in A.3.1.1 for SS diagram and A.3.2 for UE diagram in TS 38.508-1 [6]. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are TS 36.521-1 [10] Annex A.2 and TS 38.521-1 [8] Annex A.2 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.5B.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +##### 7.5B.1.4.2 Test Procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.5B.1.4.1-1 on the E-UTRA CC and NR CC, respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.5B.1.4.1-1 on the E-UTRA CC and NR CC. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. + +3. Set the Downlink signal level to the value as defined in Table 7.5B.0.1-1 (Case 1). For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.5B.0.1-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the Interferer signal level to the value as defined in Table 7.5B.0.1-1 (Case 1) and frequency below the aggregated component carriers, using a modulated interferer bandwidth as defined in Annex D. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2 in TS 38.521-1 [8] for NR band, and Annex G.2 of TS 36.521-1 [10] for EUTRA band. +6. Repeat steps from 3 to 5, using an interfering signal above the aggregated component carriers in Case 1 at step 4. +7. Set the Downlink signal level to the value as defined in Table 7.5B.0.1-2 (Case 2). For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.5B.0.1-2 for at least the duration of the Throughput measurement, where MU and Uplink power control window size are defined above. +8. Set the Interferer signal level to the value as defined in Table 7.5B.0.1-2 (Case 2) and frequency below the aggregated component carriers, using a modulated interferer bandwidth as defined in Annex D. +9. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2 in TS 38.521-1 [8] for NR band, and Annex G.2 of TS 36.521-1 [10] for EUTRA band. +10. Repeat steps from 7 to 9, using an interfering signal above the aggregated component carriers in Case 2 at step 8. +11. Repeat for applicable channel bandwidths and operating band combinations in both Case 1 and Case 2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +##### 7.5B.1.4.3 Message Contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition **TRANSFORM\_PRECODER\_ENABLED** + +Message contents exceptions are according to TS 36.521-1 [10] clause 7.3.4.3 for each network signalling value.. + +#### 7.5B.1.5 Test requirement + +The throughput measurement of each CG derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively under the conditions specified in Table 7.5B.0.1-1, and also under the conditions specified in Table 7.5B.0.1-2. + +### 7.5B.2 Adjacent Channel Selectivity for intra-band non-contiguous EN-DC (2 CCs) + +#### 7.5B.2.1 Test purpose + +Same test purpose as clause 7.5B.1.1 + +#### 7.5B.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.5B.2.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.5B.0.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.5B.2.4 Test description + +Same test description as in subclause 7.5.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 7.5B.2.4.1-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different DC bandwidth classes | Low with maxWgap, High with maxWgap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.3-1 across bandwidth combination sets supported by the UE | Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_scg is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 7.5B.2.4.1-1. + +For initial conditions as in clause 7.5.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +- On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.5.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +- Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. +- When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Step 3 of Test procedure as in clause 7.6.2.4.2 in TS 38.521-1 [8] shall treat the in-gap tests as below: For intra-band non-contiguous EN-DC of two sub-blocks with channel bandwidth larger than or equal to 5 MHz, the existing requirements apply for in-gap tests only if the corresponding interferer frequency offsets satisfy the following condition in relation to the sub-block gap size $W_{gap}$ , so that the interferer frequency position does not change the nature of the core requirement tested: + +$$W_{gap} \geq 2 \cdot |F_{Interferer}(\text{offset})| - BW_{Channel}$$ + +Same test procedure as specified in clause 7.5.4.2 in TS 38.521-1 [8]. + +#### 7.5B.2.5 Test requirement + +Same test requirement as specified in TS 38.521-1 [8] Clause 7.5.5. + +### 7.5B.3 Adjacent Channel Selectivity for inter-band EN-DC within FR1 (1 NR CC) + +#### 7.5B.3.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +#### 7.5B.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR DL CC. + +#### 7.5B.3.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.5B.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.5B.3.4 Test description + +Same test description as in clause 7.5.4.2 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.5.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.5.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.5.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +#### 7.5B.3.5 Test requirement + +Same test requirement as specified in TS 38.521-1 [8] Clause 7.5.5. + +#### 7.5B.3\_1 Adjacent Channel Selectivity for EN-DC within FR1 (>2 CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The ACS for EN-DC within FR1 (2 NR CCs) test cases below cover only inter-band and intra-band non-contiguous EN-DC. Testing of intra-band contiguous EN-DC is FFS. + +##### 7.5B.3\_1.1 Adjacent Channel Selectivity for EN-DC within FR1 (2 NR CCs) + +###### 7.5B.3\_1.1.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +###### 7.5B.3\_1.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous or inter-band EN-DC within FR1 with 2 NR DL CCs. + +###### 7.5B.3\_1.1.3 Minimum conformance requirements + +The minimum conformance requirements for intra-band non-contiguous or inter-band EN-DC within FR1 are defined in clause 7.5B.0.2 and 7.5B.0.3 respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.5B.3\_1.1.4 Test description + +Same test description as in clause 7.5A.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.5A.1.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.5.4.1 or 7.5A.1.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.5A.1.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.5B.3\_1.1.5 Test requirement + +Same test requirement as specified in TS 38.521-1 [8] Clause 7.5A.1.5 for the NR carrier(s). + +##### 7.5B.3\_1.2 Adjacent Channel Selectivity for EN-DC within FR1 (3 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The ACS for EN-DC within FR1 (3 NR CCs) test cases below cover only inter-band and intra-band non-contiguous EN-DC. Testing of intra-band contiguous EN-DC is FFS. + +###### 7.5B.3\_1.2.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +###### 7.5B.3\_1.2.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous or inter-band EN-DC within FR1 with 3 NR DL CCs. + +###### 7.5B.3\_1.2.3 Minimum conformance requirements + +The minimum conformance requirements for intra-band non-contiguous and inter-band EN-DC within FR1 are defined in clause 7.5B.0.2 and 7.5B.0.3 respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.5B.3\_1.2.4 Test description + +Same test description as in clause 7.5A.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.5A.2.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.5A.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.5A.2.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.5B.3\_1.2.5 Test requirement + +Same test requirement as specified in TS 38.521-1 [8] Clause 7.5A.2.5 for the NR carrier(s). + +##### 7.5B.3\_1.3 Adjacent Channel Selectivity for EN-DC within FR1 (4 NR CCs) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- The ACS for EN-DC within FR1 (4 NR CCs) test cases below cover only inter-band and intra-band non-contiguous EN-DC. Testing of intra-band contiguous EN-DC is FFS. + +###### 7.5B.3\_1.3.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +###### 7.5B.3\_1.3.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous or inter-band EN-DC within FR1 with 4 NR DL CCs. + +###### 7.5B.3\_1.3.3 Minimum conformance requirements + +The minimum conformance requirements for intra-band non-contiguous and inter-band EN-DC within FR1 are defined in clause 7.5B.0.2 and 7.5B.0.3 respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.5B.3\_1.3.4 Test description + +Same test description as in clause 7.5A.3.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel + +bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.5A.3.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.5A.3.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.5A.3.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.5B.3\_1.3.5 Test requirement + +Same test requirement as specified in TS 38.521-1 [8] Clause 7.5A.3.5 for the NR carriers. + +##### 7.5B.3\_1.4 Adjacent Channel Selectivity for EN-DC within FR1 (5 NR CCs) + +**Editor's note: The test cases in this clause are incomplete. The following aspects are either missing or not yet determined:** + +- The ACS for EN-DC within FR1 (5 NR CCs) test cases below cover only inter-band and intra-band non-contiguous EN-DC. Testing of intra-band contiguous EN-DC is FFS. +- The referred clauses [7.5A.4.4], [7.5A.4.4.1] and [7.5A.4.5] have not been defined in TS 38.521-1 [8] yet. + +###### 7.5B.3\_1.4.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +###### 7.5B.3\_1.4.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous or inter-band EN-DC within FR1 with 5 NR DL CCs. + +###### 7.5B.3\_1.4.3 Minimum conformance requirements + +The minimum conformance requirements for intra-band non-contiguous and inter-band EN-DC within FR1 are defined in clause 7.5B.0.2 and 7.5B.0.3 respectively. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.5B.3\_1.4.4 Test description + +Same test description as in clause [7.5A.4.4] in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause [7.5A.4.4.1] in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause [7.5A.4.4.1] in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause [7.5A.4.4.1] in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.5B.3\_1.4.5 Test requirement + +Same test requirement as specified in TS 38.521-1 [8] Clause [7.5A.4.5] for the NR carriers. + +### 7.5B.3a Adjacent Channel Selectivity for inter-band NE-DC within FR1 (2 CCs) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 7.5 and 7.5A of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 7.5 and 7.5A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +### 7.5B.4 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note:** Following aspects are either missing or not yet determined: + +- Measurement Uncertainty is FFS for power classes other than 1, 3 and 5. +- The minimum conformance requirements for Case 2 in this test case are not testable due to maximum input level unachievable in IFF OTA test setup. Other test setups have not been analysed. + +#### 7.5B.4.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +#### 7.5B.4.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR DL CC. + +#### 7.5B.4.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.5B.0.4. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.5B.4.4 Test description + +##### 7.5B.4.4.1 Initial Condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.5.1, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-2 [9] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each inter-band EN-DC + +including FR2 configuration specified in clause 5.5B.5.1, and the configuration for NR carrier are shown in TS 38.521-2 [9] Table 7.5.4.1-1. + +For initial conditions as in clause 7.5.4.1 in TS 38.521-2 [9], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +Step 6 of initial conditions as in clause 7.5.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +##### 7.5B.4.4.2 Test Procedure + +Same test procedure as specified in clause 7.5.4.2 in TS 38.521-2 [9] with the following exceptions for E-UTRA anchor + +On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +##### 7.5B.4.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1. + +#### 7.5B.4.5 Test requirement + +Same test requirement as specified in clause 7.5.5 of TS 38.521-2 [9] for the NR carrier(s). + +#### 7.5B.4\_1 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (>1 NR CC) + +##### 7.5B.4\_1.1 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note:** This test case is not complete. Following aspects are either missing or not yet determined: + +- Working assumption: to avoid LTE CA testing in inter-band EN-DC including FR2 and only PCC band is configured. +- MU and TT are FFS. +- [Table 7.5A.1.4.1-1] in TS 38.521-2 [9] where the configuration for NR CA carriers are shown is FFS. +- [clause 7.5A.1.4.1] in TS 38.521-2 [9] where the initial conditions for NR CA is FFS. +- [clause 7.5A.1.4.2] in TS 38.521-2 [9] where the test procedure for NR CA is FFS. +- [Clause 7.5A.1.5] in TS 38.521-2 [9] where the test requirements for NR CA is FFS. +- [Clause 7.5A.1.4] in TS 38.521-2 [9] where the test description for NR CA is FFS. +- How to choose the LTE anchor when LTE CA is implemented is FFS. + +###### 7.5B.4\_1.1.1 Test purpose + +Same test purpose as in clause 7.5B.1.1. + +###### 7.5B.4\_1.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 2 NR DL CCs. + +###### 7.5B.4\_1.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.5B.0.4. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.5B.4\_1.1.4 Test description + +For inter-band EN-DC including FR2 UE configured as "2 NR DL CCs and 1 LTE DL CC", the test description of 2DL FR2 CA for adjacent channel selectivity is the same as in corresponding clause 7.5A.1.4 in TS 38.521-2 [9] for FR2 with the exceptions described below. + +###### 7.5B.4\_1.1.4.1 Initial Condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.5.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-2 [9] clause 5.3A and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each inter-band EN-DC including FR2 configuration specified in clause 5.5B.5.2, and the configuration for NR carriers are shown in TS 38.521-2 [9] [Table 7.5A.1.4.1-1]. + +For initial conditions as in [clause 7.5A.1.4.1] in TS 38.521-2 [9], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +Step 6 of initial conditions as in [clause 7.5A.1.4.1] in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +###### 7.5B.4\_1.1.4.2 Test Procedure + +Same test procedure as specified in [clause 7.5A.1.4.2] in TS 38.521-2 [9] with the following exceptions for E-UTRA anchor + +On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +###### 7.5B.4\_1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6.1. + +###### 7.5B.4\_1.1.5 Test requirement + +Same test requirement as specified in TS 38.521-2 [9] [Clause 7.5A.1.5]. + +7.5B.4\_1.2 Void + +7.5B.4\_1.3 Void + +7.5B.4\_1.4 Void + +### 7.5B.4D Adjacent Channel Selectivity for inter-band EN-DC including FR2 for UL MIMO + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach can be applied and only NR carriers need to be tested. + +No test case details are specified. Given UE's Rx performance would not be impacted by the Tx configuration in NR FR2 TDD bands, the requirements in this test case can be well covered in 7.5B.4 and 7.5B.4\_1 and don't need to be tested again. + +### 7.5B.5 Adjacent Channel Selectivity for inter-band EN-DC including both FR1 and FR2 + +7.5B.5.1 Test purpose + +Same test purpose as in 7.5.1 in TS 38.521-1 [8] for NR FR1 carrier and 7.5.1 in TS 38.521-2 [9] for NR FR2 carrier. + +7.5B.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for adjacent channel selectivity apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.5B. + +### 7.5B.5D Adjacent Channel Selectivity for inter-band EN-DC including FR1 and FR2 for UL MIMO + +7.5B.5D.1 Test purpose + +Same test purpose as in 7.5D in TS 38.521-1 [8] for NR FR1 carrier and 7.5D in TS 38.521-2 [9] for NR FR2 carrier. + +7.5B.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for adjacent channel selectivity apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.5B. + +## 7.6 Void + +## 7.6A Blocking characteristics for CA + +7.6A.1 Test purpose + +Same test purpose as in clause 7.6 in TS 38.521-1 [8] for NR FR1 carrier(s) and clause 7.6 in TS 38.521-2 [9] for NR FR2 carrier(s). + +### 7.6A.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The NR/5GC requirements for blocking characteristics apply and are tested in TS 38.521-1 [8] clause 7.6 and 7.6A and TS 38.521-2 [9] clauses 7.6 and 7.6A. + +## 7.6B Blocking characteristics for DC + +### 7.6B.1 General + +The blocking characteristic for EN-DC in FR1 is a measure of the receiver's ability of an UE that support EN-DC in FR1 to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occur. + +### 7.6B.2 Inband blocking for DC + +#### 7.6B.2.0 Minimum Conformance Requirements + +##### 7.6B.2.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC in-band blocking requirement and parameters are defined in Table 7.6B.2.0.1-1. + +**Table 7.6B.2.0.1-1: In-band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------|------------|------------| +| P w in Transmission Bandwidth Configuration, per CC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | P w 1 | 16.8 | 17.5 | 18 | +| NOTE 1: P w is wanted signal power level at the specified EN-DC aggregated Bandwidth from Table 7.6.1.1A-1 in TS 36.101 [5].
NOTE 2: Interferer values are specified from Table 7.6.1.1A-2 in TS 36.101 [5].
NOTE 3: Jammer BW and offset is from Table 7.6.1.1A-1 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier.
NOTE 4: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c,NR at the minimum uplink configuration specified in Table 7.3.2-3 [2] with P CMAX_L,f,c,NR as defined in clause 6.2B.4.
NOTE 5: For E-UTRA carrier, the transmitter shall be set to 29dB below P CMAX_L,E-UTRA,c at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with P CMAX_L,E-UTRA,c as defined in clause 6.2B.4 for single carrier. | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.2.1. + +##### 7.6B.2.0.2 Intra-band non-contiguous EN-DC + +For the E-TRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.6.1.1 for single carrier operation and in clause 7.6.1.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.6.2 in TS 38.101-1 [2]. + +The blocker configuration is defined in the general clause 7.1. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.2.2. + +##### 7.6B.2.0.3 Inter-band EN-DC within FR1 + +Inband blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.1.1 and 7.6.1.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.2 and 7.6A.2 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.2.3. + +###### 7.6B.2.0.3a Inter-band NE-DC within FR1 + +Inband blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.1.1 and 7.6.1.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.2 and 7.6A.2 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.2.3a. + +##### 7.6B.2.0.4 Inter-band EN-DC including FR2 + +Inband blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.1.1 and 7.6.1.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.2 and 7.6A.2 of TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.2.4. + +##### 7.6B.2.0.5 Inter-band EN-DC including both FR1 and FR2 + +Inband blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.1.1 and 7.6.1.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.2 and 7.6A.2 of TS 38.101-1 [2] and TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.2.5. + +#### 7.6B.2.1 Inband blocking for intra-band contiguous EN-DC (2 CCs) + +##### 7.6B.2.1.1 Test Purpose + +In-band blocking is defined for an unwanted interfering signal falling into the range from 15MHz below to 15MHz above the UE receive band, at which the relative throughput shall meet or exceed the requirement for the specified measurement channels. The lack of in-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +##### 7.6B.2.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.6B.2.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6 B.2.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 7.6B.2.1.4 Test Description + +###### 7.6 B.2.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.2.1.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.2.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------------|-----------------------------|-----------------------------|-------------------------|--------------------------|-----------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | | | +| NR/E-UTRA Test Parameters | | | | | | | | +| Downlink Configuration | | | | Uplink Configuration | | | | +| NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| CP-OFDM
QPSK | Full RB
(NOTE 1) | QPSK | Full RB | DFT-s-OFDM
QPSK | REFSENS | QPSK | REFSENS | +| NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. | | | | | | | | +| NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. | | | | | | | | +| NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | | | | | | | +| NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. | | | | | | | | +| NOTE 5: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.1 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.2.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 7.6B.2.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.2.1.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.2.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.2.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(MU + \text{Uplink power control window size})$ dB of the target power level in Table 7.6B.2.1.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the signal generator for an interfering signal below the aggregated component carriers in Case 1 according to Table 7.6B.2.1.5-1. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers in Case 1 at step 4. +7. Repeat steps from 4 to 6, using interfering signals in Case 2 at steps 4 and 6. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.2.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +##### 7.6B.2.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.6B.2.1.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.6B.2.1.5-1: In-band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------|------------|------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | Pw 1 | 16.8 | 17.5 | 18 | +| NOTE 1: Pw is wanted signal power level at the specified EN-DC aggregated Bandwidth from Table 7.6.1.1A-1 in TS 36.101 [5].
NOTE 2: Interferer values are specified from Table 7.6.1.1A-2 in TS 36.101 [5].
NOTE 3: Jammer BW and offset is from Table 7.6.1.1A-1 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier.
NOTE 4: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c,NR at the minimum uplink configuration specified in TS 38.101-1 [2], Table 7.3.2-3 with P CMAX_L,f,c,NR as defined in clause 6.2B.4.
NOTE 5: For E-UTRA carrier, the transmitter shall be set to 29dB below P CMAX_L,E-UTRA,c at the minimum uplink configuration specified in TS 36.101 [5], Table 7.3.1-2 with P CMAX_L,E-UTRA,c as defined in clause 6.2B.4 for single carrier. | | | | | + +**Table 7.6B.2.1.5-2: Void** + +**Table 7.6B.2.1.5-3: Void** + +#### 7.6B.2.2 Inband blocking for intra-band non-contiguous EN-DC (2 CCs) + +##### 7.6B.2.2.1 Test Purpose + +Same test purpose as in clause 7.6.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.6B.2.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.6B.2.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.2.0.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.6B.2.2.4 Test Description + +Same test description as in clause 7.6.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 7.6B.2.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | High range with maxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1 except for the parameters specified in Table 7.6B.2.2.4-1. + +For Initial conditions as in clause 7.6.2.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add steps 7 and 8 to Initial conditions in clause 7.6.2.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Step 3 of Test procedure as in clause 7.6.2.4.2 in TS 38.521-1 [8] shall treat the in-gap tests as below: For intra-band non-contiguous EN-DC of two sub-blocks with channel bandwidth larger than or equal to 5 MHz, the existing requirements apply for in-gap tests only if the corresponding interferer frequency offsets satisfy the following condition in relation to the sub-block gap size $W_{\text{gap}}$ , so that the interferer frequency position does not change the nature of the core requirement tested: + +$$W_{\text{gap}} \geq 2 \cdot |F_{\text{Interferer}}(\text{offset})| - BW_{\text{Channel}}$$ + +Step 4 of Test procedure as in clause 7.6.2.4.2 in TS 38.521-1 [8] is replaced by: + +4. Set the downlink signal level for NR CC according to the Table 7.6.2.5-1 or 7.6.2.5-3 in TS 38.521-1 [8] as appropriate. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of ( $P_{\text{CMAX\_L,e}}$ - 29dB) for E-UTRA CC, and of 4dB below $P_{\text{CMAX\_L,f,c}}$ for NR CC for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +##### 7.6B.2.2.5 Test Requirement + +Same test requirement as in clause 7.6.2.5 in TS 38.521-1 [8]. + +#### 7.6B.2.3 Inband blocking for inter-band EN-DC within FR1 (1 NR CC) + +##### 7.6B.2.3.1 Test Purpose + +Same test purpose as in clause 7.6.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.6B.2.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR DL CC. + +##### 7.6B.2.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.2.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.6B.2.3.4 Test Description + +Same test description as in clause 7.6.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6.2.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6.2.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 7.6B.2.3.5 Test Requirement + +Same test requirement as in clause 7.6.2.5 in TS 38.521-1 [8]. + +##### 7.6B.2.3\_1 Inband blocking for EN-DC within FR1 (>2 CCs) + +###### 7.6B.2.3\_1.1 Inband blocking for EN-DC within FR1 (3 CCs) + +###### 7.6B.2.3\_1.1.1 Test Purpose + +For intra-band contiguous EN-DC within FR1 with 3 DL CCs: In-band blocking is defined for an unwanted interfering signal falling into the range from 15MHz below to 15MHz above the UE receive band, at which the relative throughput shall meet or exceed the requirement for the specified measurement channels. The lack of in-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +For inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs): Same test purpose as in clause 7.6A.2.1.1 in TS 38.521-1 [8]. + +###### 7.6B.2.3\_1.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC within FR1 with 3 DL CCs or inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs). + +###### 7.6B.2.3\_1.1.3 Minimum Conformance Requirements + +For intra-band contiguous EN-DC within FR1 with 3 DL CCs: The minimum conformance requirements are defined in clause 7.6 B.2.0.1. Exception requirements for both NR and E-UTRA are defined and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +For inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs): The minimum conformance requirements are defined in clause 7.6B.2.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.6B.2.3\_1.1.4 Test Description + +###### 7.6B.2.3\_1.1.4.1 Intra-band contiguous EN-DC within FR1 with 3 DL CCs + +###### 7.6B.2.3\_1.1.4.1.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.2.3\_1.1.4.1.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.2.3\_1.1.4.1.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------------|------------------|------------------------------------|--------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| PCC – E-UTRA | | SCC – EUTRA | | NR | | +| UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | +| QPSK/QPSK | REFSENS/Full RB | NA/QPSK | NA/Full RB | DFT-s-OFDM
QPSK/CP-OFDM
QPSK | REFSENS/Full RB (NOTE 1) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB\_agg, only the combination with the highest NRB\_SCG is tested. + +NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. + +NOTE 5: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.1 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. + +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.2.3\_1.1.4.1.3. + +###### 7.6B.2.3\_1.1.4.1.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.2.3\_1.1.4.1.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.2.3\_1.1.4.1.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.2.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -*MU* to -(*MU* + Uplink power control window size) dB of the target power level in Table 7.6B.2.1.5-1 + ( $10\log(S\_LCRB/N_{RB\_alloc})$ ) for NR CC, ( $10\log(P\_LCRB/N_{RB\_alloc})$ ) for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - *MU* is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency *f* and the channel bandwidth *BW* + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the signal generator for an interfering signal below the aggregated component carriers in Case 1 according to Table 7.6B.2.1.5-1. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers in Case 1 at step 4. +7. Repeat steps from 4 to 6, using interfering signals in Case 2 at steps 4 and 6. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.2.3\_1.1.4.1.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +###### 7.6B.2.3\_1.1.4.2 Inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs) + +Same test description as in clause 7.6A.2.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6A.2.1.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.2.1.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.2.1.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.6B.2.3\_1.1.5 Test Requirement + +For intra-band contiguous EN-DC within FR1 with 3 DL CCs: Same test requirement as in clause 7.6B.2.1.5. + +For inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs): Same test requirement as in clause 7.6A.2.1.5 in TS 38.521-1 [8]. + +###### 7.6B.2.3\_1.2 Inband blocking for EN-DC within FR1 (4 CCs) + +###### 7.6B.2.3\_1.2.1 Test Purpose + +For intra-band contiguous EN-DC within FR1 with 4 DL CCs: In-band blocking is defined for an unwanted interfering signal falling into the range from 15MHz below to 15MHz above the UE receive band, at which the relative throughput shall meet or exceed the requirement for the specified measurement channels. The lack of in-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +For inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs): Same test purpose as in clause 7.6A.2.2.1 in TS 38.521-1 [8]. + +###### 7.6B.2.3\_1.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC within FR1 with 4 DL CCs or inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs). + +###### 7.6B.2.3\_1.2.3 Minimum Conformance Requirements + +For intra-band contiguous EN-DC within FR1 with 4 DL CCs: The minimum conformance requirements are defined in clause 7.6 B.2.0.1. Exception requirements for both NR and E-UTRA are defined and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +For inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs): The minimum conformance requirements are defined in clause 7.6B.2.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.6B.2.3\_1.2.4 Test Description + +###### 7.6B.2.3\_1.2.4.1 Intra-band contiguous EN-DC within FR1 with 4 DL CCs + +###### 7.6B.2.3\_1.2.4.1.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.2.3\_1.2.4.1.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.2.3\_1.2.4.1.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------|------------------|------------------------------------|--------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| PCC – E-UTRA | | SCC1 – EUTRA and SCC2 – EUTRA | | NR | | +| UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | +| QPSK/QPSK | REFSENS/Full RB | NA/QPSK | NA/Full RB | DFT-s-OFDM
QPSK/CP-OFDM
QPSK | REFSENS/Full RB (NOTE 1) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB\_agg, only the combination with the highest NRB\_SCG is tested. + +NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. + +NOTE 5: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.1 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. + +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.2.3\_1.2.4.1.3. + +###### 7.6B.2.3\_1.2.4.1.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.2.3\_1.2.4.1.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.2.3\_1.2.4.1.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.2.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of the target power level in Table 7.6B.2.1.5-1 + ( $[10\log(S\_LCRB/N_{RB\_alloc})]$ for NR CC, $[10\log(P\_LCRB/N_{RB\_alloc})]$ for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency *f* and the channel bandwidth *BW* + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the signal generator for an interfering signal below the aggregated component carriers in Case 1 according to Table 7.6B.2.1.5-1. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers in Case 1 at step 4. +7. Repeat steps from 4 to 6, using interfering signals in Case 2 at steps 4 and 6. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.2.3\_1.2.4.1.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition **TRANSFORM\_PRECODER\_ENABLED**. + +###### 7.6B.2.3\_1.2.4.2 Inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs) + +Same test description as in clause 7.6A.2.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6A.2.2.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.2.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.2.2.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.6B.2.3\_1.2.5 Test Requirement + +For intra-band contiguous EN-DC within FR1 with 4 DL CCs: Same test requirement as in clause 7.6B.2.1.5. + +For inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs): Same test requirement as in clause 7.6A.2.2.5 in TS 38.521-1 [8]. + +###### 7.6B.2.3\_1.3 Inband blocking for EN-DC within FR1 (5 CCs) + +###### 7.6B.2.3\_1.3.1 Test Purpose + +Same test purpose as in clause 7.6B.2.3.1. + +###### 7.6B.2.3\_1.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 16 and forward, supporting inter-band EN-DC within FR1 with 5 DL CCs (4 NR DL CCs). + +###### 7.6B.2.3\_1.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.2.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.6B.2.3\_1.3.4 Test Description + +Same test description as in clause 7.6A.2.3.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6A.2.3.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.2.3.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.2.3.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.6B.2.3\_1.3.5 Test Requirement + +Same test requirement as in clause 7.6A.2.3.5 in TS 38.521-1 [8]. + +###### 7.6B.2.3\_1.4 Void + +##### 7.6B.2.3a In-band blocking for inter-band NE-DC within FR1 (2 CCs) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 7.6.2 and 7.6A.2 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 7.6.1 and 7.6.1A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +#### 7.6B.2.4 Inband blocking for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note: The following aspects are either missing or not yet determined:** + +- Measurement uncertainty is FFS for power classes other than 1, 3 and 5. + +##### 7.6B.2.4.1 Test Purpose + +Same test purpose as in clause 7.6.2.1 in TS 38.521-2 [9] for the NR carrier. + +##### 7.6B.2.4.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR DL CC. + +##### 7.6B.2.4.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.2.0.4. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.6B.2.4.4 Test Description + +Same test description as in clause 7.6.2.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 7.6.2.4.1 in TS 38.521-2 [9], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6.2.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6.2.4.1 in TS 38.521-2 [9] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.7. + +##### 7.6B.2.4.5 Test Requirement + +Same test requirement as in clause 7.6.2.5 in TS 38.521-2 [9]. + +#### 7.6B.2.4\_1 Inband blocking for inter-band EN-DC including FR2 (>1 NR CC) + +###### 7.6B.2.4\_1.1 Inband blocking for inter-band EN-DC including FR2 (2 NR CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- The referred test case 7.6A.2.1 in TS 38.521-2 is incomplete. + +###### 7.6B.2.4\_1.1.1 Test Purpose + +Same test purpose as in clause 7.6B.2.4.1. + +###### 7.6B.2.4\_1.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 and FR2 inter-band 2DL CA. + +###### 7.6B.2.4\_1.1.3 Minimum Conformance Requirements + +Same minimum conformance requirements as in clause 7.4B.2.4.3 + +###### 7.6B.2.4\_1.1.4 Test Description + +Same test description as in clause 7.6A.2.1.4 in TS 38.521-2 [9] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.7-1. + +For Initial conditions as in clause 7.6A.2.1.4.1 in TS 38.521-2 [9], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.2.1.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.2.1.4.1 in TS 38.521-2 [9] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.7. + +###### 7.6B.2.4\_1.1.5 Test Requirement + +Same test requirement as in clause 7.6A.2.1.5 in TS 38.521-2 [9]. + +##### 7.6B.2.4\_1.2 Void + +##### 7.6B.2.4\_1.3 Void + +##### 7.6B.2.4\_1.4 Void + +#### 7.6B.2.4D Inband blocking for inter-band EN-DC including FR2 for UL MIMO + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach can be applied and only NR carriers need to be tested. + +No test case details are specified. Given UE's Rx performance would not be impacted by the Tx configuration in NR FR2 TDD bands, the requirements in this test case can be well covered in clauses 7.6B.2.4 and 7.6B.2.4\_1, and don't need to be tested again. + +#### 7.6B.2.5 Inband blocking for inter-band EN-DC including both FR1 and FR2 + +##### 7.6B.2.5.1 Test purpose + +Same test purpose as in clause 7.6.2.1 in TS 38.521-1 [8] for NR FR1 carrier and clause 7.6.2.1 in TS 38.521-2 [9] for NR FR2 carrier. + +##### 7.6B.2.5.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for Inband blocking apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.6B.2. + +#### 7.6B.2.5D Inband blocking for inter-band EN-DC including FR1 and FR2 for UL MIMO + +##### 7.6B.2.5D.1 Test purpose + +Same test purpose as in clause 7.6D.2 in TS 38.521-1 [8] for NR FR1 carrier and clause 7.6D in TS 38.521-2 [9] for NR FR2 carrier. + +##### 7.6B.2.5D.2 Test applicability + +The requirements in this test are not testable due to issues with combined testing of NR FR1 and E-UTRA in conducted mode with NR FR2 in radiated mode. Therefore, the conducted and radiated requirements are tested separately. + +No test case details are specified. The EN-DC requirements for Inband blocking apply and are tested as part of the EN-DC within FR1 and EN-DC including FR2 test cases in clause 7.6B.2. + +### 7.6B.3 Out-of-band blocking for DC + +#### 7.6B.3.0 Minimum Conformance Requirements + +##### 7.6B.3.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC out-of-band requirement and parameters are defined in Table 7.6B.3.0.1-1. + +**Table 7.6B.3.0.1-1: Out-of-band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|--------------------------------------------------------|----------------------------------------------|------------|------------|------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Interferer values and offsets are specified from Table 7.6.2.1A-2 in TS 36.101 [5]. For inter-band combinations where the intra-band requirements are applicable, in which the E-UTRA band is a subset of an NR-only band, the NR band interferer values and offsets specified from Table 7.6A.3-2 in TS 38.101-1 [2] apply to both E-UTRA and NR carriers. | +| NOTE 2: | For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,f,c,NR}}$ at the minimum uplink configuration specified in Table 7.3.2-3 [2] with $P_{\text{CMAX\_L,f,c,NR}}$ as defined in clause 6.2B.4. | +| NOTE 3: | For E-UTRA carrier, the transmitter shall be set to 29dB below $P_{\text{CMAX\_L,E-UTRA,c}}$ at the minimum uplink configuration specified in Table 7.3.1-2 [5] with $P_{\text{CMAX\_L,E-UTRA,c}}$ as defined in clause 6.2B.4 for single carrier. | + +For Table 7.6.2.1A-2 from TS 36.101 [4] in frequency range 1, 2 and 3, up to $\max(24, 6 \cdot \lceil N_{\text{RB}} / 6 \rceil)$ exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.7B.1 Spurious response are applicable. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.3.1. + +##### 7.6B.3.0.2 Intra-band non-contiguous EN-DC + +For the E-UTRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.6.2.1 for single carrier operation and in clause 7.6.2.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.6.3 in TS 38.101-1 [2]. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.3.2. + +##### 7.6B.3.0.3 Inter-band EN-DC within FR1 + +Out-of-band blocking requirements for E-UTRA single carrier and CA operation specified in clauses 7.6.2.1 and 7.6.2.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.3 and 7.6A.3 of TS 38.101-1 [2] apply for lowest level EN-DC fallbacks (two bands) in clause 5.5B.4.1 with following conditions: + +- one E-UTRA uplink carrier with the output power set to 4dB below $P_{\text{CMAX\_L,c}}$ and the NR band whose downlink is being tested has its uplink carrier output power set to 29 dB below $P_{\text{CMAX\_L,f,c}}$ . +- one NR uplink carrier with the output power set to 4dB below $P_{\text{CMAX\_L,f,c}}$ on the NR band with both E-UTRA and NR downlinks being tested with E-UTRA output power set to 29 dB below $P_{\text{CMAX\_L,c}}$ . + +If CW interferer falls in a gap between $F_{\text{DL\_high}}$ of the E-UTRA or NR band and $F_{\text{DL\_low}}$ of the NR or EUTRA band, where the corresponding OOB ranges 1 and 2 overlap, then the lower level interferer limit of the overlapping OOB ranges applies. + +If $F_{\text{DL\_high}}$ of the lower E-UTRA or NR band is greater than or equal to the $F_{\text{DL\_low}}$ of the upper NR or E-UTRA band as in overlapping RX frequency ranges, then the OOB range shall start from the $F_{\text{DL\_low}}$ of the lower E-UTRA or NR band, and from the $F_{\text{DL\_high}}$ of the upper NR or E-UTRA band. + +For EN-DC combination listed in Table 7.6B.3.0.3-1 under the first test condition above, exceptions to the requirement specified in Table 7.6B.3.0.3-2 are allowed when the second order intermodulation product of the lower frequency band UL carrier and the CW interfering signal fully or partially overlaps with the higher frequency band DL carrier. + +**Table 7.6B.3.0.3-1: EN-DC combination with exceptions allowed** + +| EN-DC combination | +|-------------------| +| DC_5_n78 | +| DC_8_n77 | +| DC_8_n78 | +| DC_11_n77 | +| DC_18_n77 | +| DC_18_n78 | +| DC_18_n79 | +| DC_19_n77 | +| DC_19_n78 | +| DC_19_n79 | +| DC_20_n78 | +| DC_21_n77 | +| DC_26_n77 | +| DC_26_n78 | +| DC_26_n79 | +| DC_28_n77 | +| DC_28_n78 | +| DC_28_n79 | + +**Table 7.6B.3.0.3-2: Exceptions allowed** + +| Parameter | Unit | Level | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------| +| P Interferer (CW) | dBm | -44 1 | +| NOTE 1: The requirement applies when $ f_{Interferer} \pm f_{UL}^{LB} - f_{DL}^{HB} \leq (BW_{UL}^{LB} + BW_{DL}^{HB})/2$ , where $f_{UL}^{LB}$ and $f_{DL}^{HB}$ are the carrier frequencies for lower frequency band UL and higher frequency band DL, respectively. $BW_{UL}^{LB}$ and $BW_{DL}^{HB}$ are the channel bandwidths configured for lower frequency band UL carrier and higher frequency band DL carrier in MHz, respectively. | | | + +For each of the two test cases in clauses 7.6.2.1 and 7.6.2.1A of [5] and for NR single carrier and CA operation specified in clauses 7.6.3 and 7.6A.3 of TS 38.101-1 [2] for all interferer frequency ranges a maximum of + +$$\lfloor \max \{24.6 \cdot \lceil n \cdot N_{RB} / 6 \rceil\} / \min \{\lfloor n \cdot N_{RB} / 10 \rfloor, 5\} \rfloor$$ + +exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a step size of $\min \{\lfloor CBW / 2 \rfloor, 5\}$ MHz with $N_{RB}$ the number of resource blocks in the downlink transmission bandwidth configuration, $CBW$ the bandwidth of the frequency channel in MHz and $n = 1, 2, 3$ for SCS = 15, 30, 60 kHz, respectively. For these exceptions, the requirements in clause 7.7 apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.3.3. + +##### 7.6B.3.0.3a Inter-band NE-DC within FR1 + +Out-of-band blocking requirements for E-UTRA single carrier and CA operation specified in clauses 7.6.2.1 and 7.6.2.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.3 and 7.6A.3 of TS 38.101-1 [2] apply for lowest level NE-DC fallbacks (two bands) in clause 5.5B.4a.1 with following conditions: + +- one E-UTRA uplink carrier with the output power set to 4 dB below $P_{CMAX\_L,c}$ and the NR band whose downlink is being tested has its uplink carrier output power set to 29 dB below $P_{CMAX\_L,fc}$ . +- one NR uplink carrier with the output power set to 4 dB below $P_{CMAX\_L,fc}$ on the NR band with both E-UTRA and NR downlinks being tested with E-UTRA output power set to 29 dB below $P_{CMAX\_L,c}$ . + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.3.3a. + +##### 7.6B.3.0.4 Inter-band EN-DC including FR2 + +Out-of-band blocking requirements specified for E-UTRA single carrier and CA operation specified in clauses 7.6.2.1 and 7.6.2.1A of TS 36.101 [5] apply for lowest level EN-DC fallbacks (two bands) in clause 5.5B.5.1 with only E-UTRA UL with output power as in TS 36.101 [5] (4dB below $P_{\text{CMAX\_L}}$ ). + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.3.4. + +##### 7.6B.3.0.5 Inter-band EN-DC including both FR1 and FR2 + +Out-of-band blocking requirements specified for E-UTRA single carrier and CA operation specified in clauses 7.6.2.1 and 7.6.2.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.3 and 7.6A.3 of TS 38.101-1 [2] apply for lowest level EN-DC fallbacks (three bands) in clause 5.5B.6.2 with only E-UTRA UL with output power as in TS 36.101 [5] (4dB below $P_{\text{CMAX\_L}}$ ). + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.3.5. + +#### 7.6B.3.1 Out-of-band blocking for intra-band contiguous EN-DC (2 CCs) + +##### 7.6B.3.1.1 Test Purpose + +Out-of-band band blocking is defined for an unwanted CW interfering signal falling more than 15 MHz below or above the UE receive band, at which a given average throughput shall meet or exceed the requirement for the specified measurement channels. + +For the first 15 MHz below or above the UE receive band the appropriate in-band blocking or adjacent channel selectivity in clause 7.6B.2.1 and clause 7.5B.1 shall be applied. + +The lack of out-of-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +##### 7.6B.3.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.6B.3.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.3.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 7.6B.3.1.4 Test Description + +###### 7.6B.3.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.3.1.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.3.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------|----------------------|----------------------|------------------|-------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest $N_{RB\_agg}$ (NOTE 3) | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | | | +| NR/E-UTRA Test Parameters | | | | | | | | +| Downlink Configuration | | | | Uplink Configuration | | | | +| NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| CP-OFDM QPSK | Full RB (NOTE 1) | QPSK | Full RB | DFT-s-OFDM QPSK | REFSENS_NR | QPSK | REFSENS_LTE S | +| NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. | | | | | | | | +| NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. | | | | | | | | +| NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same $N_{RB\_agg}$ , only the combination with the highest $N_{RB\_agg}$ is tested. | | | | | | | | +| NOTE 4: REFSENS_NR and REFSENS_LTE refers to Uplink configuration in Table 7.3.2.4.1-3 in 38.521-1 [8] and Table 7.3.4.1-1 in 36.521 [10] for NR and E-UTRA CC respectively. | | | | | | | | +| NOTE 5: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.3.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 7.6B.3.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.1.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + +3. Set the Downlink signal level to the value as defined in Table 7.6B.3.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -(MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.6B.3.1.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.3.1.5-1. The frequency step size is 1MHz. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2 in TS 38.521-1 [8] for NR band, and Annex G.2 of TS 36.521-1 [10] for EUTRA band. +6. Record the frequencies for which the throughput doesn't meet the requirements. +7. Repeat steps from 4 to 6, using an interfering signal above the aggregated component carriers at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.3.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +##### 7.6B.3.1.5 Test Requirement + +Except for the spurious response frequencies recorded in step 6 of test procedure, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.6B.3.1.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +The number of spurious response frequencies recorded in step 6 of test procedure shall not exceed $\max(24, 6 \cdot \lceil N_{RB} / 6 \rceil)$ exceptions in each assigned frequency channel when measured using a 1MHz step size. For these exceptions the requirements of clause 7.7B Spurious Response are applicable. + +**Table 7.6B.3.1.5-1: Out-of-band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|--------------------------------------------------------|----------------------------------------------|------------|------------|------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | + +NOTE 1: Interferer values and offsets are specified from Table 7.6.2.1A-2 in TS 36.101 [5]. For inter-band combinations where the intra-band requirements are applicable, in which the E-UTRA band is a subset of an NR-only band, the NR band interferer values and offsets specified from Table 7.6A.3-2 in TS 38.101-1 [2] apply to both E-UTRA and NR carriers. + +NOTE 2: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,f,c,NR}}$ at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with $P_{\text{CMAX\_L,f,c,NR}}$ as defined in clause 6.2B.4. + +NOTE 3: For E-UTRA carrier, the transmitter shall be set to 29dB below $P_{\text{CMAX\_L,E-UTRA,c}}$ at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with $P_{\text{CMAX\_L,E-UTRA,c}}$ as defined in clause 6.2B.4 for single carrier. + +**Table 7.6B.3.1.5-2: Void** + +**Table 7.6B.3.1.5-3: Void** + +#### 7.6B.3.2 Out-of-band blocking for intra-band non-contiguous EN-DC (2 CCs) + +##### 7.6B.3.2.1 Test Purpose + +Same test purpose as in clause 7.6.3.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.6B.3.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.6B.3.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.3.0.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.6B.3.2.4 Test Description + +Same test description as in clause 7.6.3.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 7.6B.3.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | High range with maxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest $N_{\text{RB\_agg}}$ (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same $N_{\text{RB\_agg}}$ , only the combination with the highest $N_{\text{RB\_SCG}}$ is tested. | | + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1 except for the parameters specified in Table 7.6B.3.2.4-1. + +For Initial conditions as in clause 7.6.3.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. + +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6.3.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add steps 7 and 8 to Initial conditions in clause 7.6.3.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Step 4 of Test procedure as in clause 7.6.3.4.2 in TS 38.521-1 [8] is replaced by: + +4. Set the downlink signal level for NR CC according to the Table 7.6.3.5-1 or 7.6.3.5-3 in TS 38.521-1 [8] as appropriate. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of ( $P_{\text{CMAX\_L,fc}}$ - 29dB) for E-UTRA CC, and of 4dB below $P_{\text{CMAX\_L,fc}}$ for NR CC for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +##### 7.6B.3.2.5 Test Requirement + +Same test requirement as in clause 7.6.3.5 in TS 38.521-1 [8]. + +#### 7.6B.3.3 Out-of-band blocking for inter-band EN-DC within FR1 (2 CCs) + +##### 7.6B.3.3.1 Test Purpose + +Out-of-band band blocking is defined for an unwanted CW interfering signal falling more than 15 MHz or 3\*CBW below or above the UE receive band, at which a given average throughput shall meet or exceed the requirement for the specified measurement channels. + +For the first 15 MHz or 3\*CBW below or above the UE receive band the appropriate in-band blocking or adjacent channel selectivity in clause 7.6B.2.3 and clause 7.5B.3 shall be applied. + +The lack of out-of-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +##### 7.6B.3.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 2 DL CCs. + +##### 7.6B.3.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.3.0.3. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 7.6B.3.3.4 Test Description + +###### 7.6B.3.3.4.1 Initial Conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, DC configuration specified in clause 5.5B.4 and test channel bandwidths specified in TS 36.508 [11] clause 4.3.1 and TS 38.508-1 [6] clause 4.3.1, and sub-carrier spacing based on NR operating bands specified in TS 38.521-1 [8] clause 5.3. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration, and are shown in Table 7.6B.3.3.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) and OCNG patterns are specified in TS 36.521-1 [10] Annexe A for E-UTRA, and TS 38.521-1 [8] Annex A for NR. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C and in TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively. + +**Table 7.6B.3.3.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------|----------------------|-----------------------------|----------------------|--------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | +| NR Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1
E-UTRA Test Frequencies as specified in TS 36.508-1 [11] clause 4.3.1 | Mid range for E-UTRA and Mid range for NR (NOTE 3) | | | | | | | +| NR Test Channel Bandwidths as specified in TS 38.508-1 [6] clause 4.3.1
E-UTRA Test Channel Bandwidths as specified in TS 36.508 [11] clause 4.3.1 | Highest for E-UTRA and Highest for NR | | | | | | | +| NR Test SCS as specified in TS 38.508-1 [6] Table 5.3.5-1 | Lowest | | | | | | | +| Test Parameters | | | | | | | | +| Downlink Configuration | | | | Uplink Configuration | | | | +| E-UTRA Cell | | NR Cell | | E-UTRA Cell | | NR Cell | | +| Modulation | RB allocation | Modulation | RB allocation | Modulation | RB allocation | Modulation | RB allocation | +| QPSK | NOTE 1 | CP-OFDM
QPSK | NOTE 1 | QPSK | NOTE 1 | DFT-s-OFDM
QPSK | NOTE 1 | +| NOTE 1: The specific configuration of uplink and downlink are defined in Table 7.3B.2.3.4.2.1-1.
NOTE 2: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements.
NOTE 3: For NR band n28, 30MHz test channel bandwidth is tested with Low range test frequency.
NOTE 4: For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. + +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2 , A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.3.3.4.3. + +###### 7.6B.3.3.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.3.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.3.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.3.3.5-1, Table 7.6B.3.3.5-3, or Table 7.6B.3.3.5-5 for E-UTRA CC and NR CC respectively. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of ( $P_{CMAX\_L,c}$ - 4dB) for E-UTRA CC, and of 29 dB below $P_{CMAX\_L,f,c}$ for NR CC for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.3.3.5-4 or Table 7.6B.3.3.5-6. The frequency step size is $\min(\lfloor CBW / 2 \rfloor, 5)$ MHz. + +If CW interferer falls in a gap between $F_{DL\_high}$ of the E-UTRA or NR band and $F_{DL\_low}$ of the NR or EUTRA band, where the corresponding OOB ranges 1 and 2 in Table 7.6B.3.3.5-2 and Table 7.6B.3.3.5-4 or Table 7.6B.3.3.5-6 overlap, then the lower level interferer limit of the overlapping OOB ranges applies. CW interferer is eliminated from $F_{DL\_low} - 15\text{MHz}$ to $F_{DL\_high} + 15\text{MHz}$ of E-UTRA carrier. + +If $F_{DL\_high}$ of the lower E-UTRA or NR band is greater than or equal to the $F_{DL\_low}$ of the upper NR or E-UTRA band as in overlapping RX frequency ranges, then the OOB range shall start from the $F_{DL\_low}$ of the lower E-UTRA or NR band, and from the $F_{DL\_high}$ of the upper NR or E-UTRA band. + +For EN-DC combination listed in Table 7.6B.3.3.5-7, exceptions to the requirement specified in Table 7.6B.3.3.5-8 are allowed when the second order intermodulation product of the lower frequency band UL carrier and the CW interfering signal fully or partially overlaps with the higher frequency band DL carrier. + +5. Measure the average throughput of NR CC for a duration sufficient to achieve statistical significance according to Annex H.2. Record the frequencies for which the throughput doesn't meet the requirements. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers at step 4. +7. Set the Downlink signal level to the value as defined in Table 7.6B.3.3.5-1, Table 7.6B.3.3.5-3, or Table 7.6B.3.3.5-5 for E-UTRA CC and NR CC respectively. For NR CC and E-UTRA CC, send uplink power control + +commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(MU + \text{Uplink power control window size})$ dB of $(P_{\text{CMAX\_L,fc}} - 4\text{dB})$ for NR CC, and of 29 dB below $P_{\text{CMAX\_L,c}}$ for E-UTRA CC for at least the duration of the Throughput measurement, where: + +- MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + - For NR CC, Uplink power control window size = $1\text{dB (UE power step size)} + 0.7\text{dB (UE power step tolerance)} + (\text{Test system relative power measurement uncertainty})$ , where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = $1\text{dB (UE power step size)} + 1.0\text{dB (UE power step tolerance)} + (\text{Test system relative power measurement uncertainty})$ , where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +8. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.3.3.5-2, Table 7.6B.3.3.5-4 or Table 7.6B.3.3.5-6 for E-UTRA CC and NR CC testing respectively. The frequency step size is $\min(\lfloor CBW / 2 \rfloor, 5)$ MHz. + +If CW interferer falls in a gap between $F_{\text{DL\_high}}$ of the E-UTRA or NR band and $F_{\text{DL\_low}}$ of the NR or EUTRA band, where the corresponding OOB ranges 1 and 2 in Table 7.6B.3.3.5-2 and Table 7.6B.3.3.5-4 or Table 7.6B.3.3.5-6 overlap, then the lower level interferer limit of the overlapping OOB ranges applies. CW interferer is eliminated from $F_{\text{DL\_low}} - 15\text{MHz}$ to $F_{\text{DL\_high}} + 15\text{MHz}$ of E-UTRA and NR carriers. + +If $F_{\text{DL\_high}}$ of the lower E-UTRA or NR band is greater than or equal to the $F_{\text{DL\_low}}$ of the upper NR or E-UTRA band as in overlapping RX frequency ranges, then the OOB range shall start from the $F_{\text{DL\_low}}$ of the lower E-UTRA or NR band, and from the $F_{\text{DL\_high}}$ of the upper NR or E-UTRA band. + +9. Measure the average throughput of E-UTRA CC and NR CC respectively for a duration sufficient to achieve statistical significance according to Annex H.2. Record the frequencies for which the throughput doesn't meet the requirements. +10. Repeat steps from 8 to 9, using an interfering signal above the aggregated component carriers at step 8. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.3.3.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 with the following exceptions. + +**Table 7.6B.3.3.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | + +**Table 7.6B.3.3.4.3-2: RRCConnectionReconfiguration** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | +| } | | | | + +##### 7.6B.3.3.5 Test Requirement + +For E-UTRA bands, except for the spurious response frequencies recorded in test procedure, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 of TS 36.521-1 [10] with parameters specified in Tables 7.6B.3.3.5-1 and 7.6B.3.3.5-2. + +For NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz, except for the spurious response frequencies recorded in test procedure, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 and A.3.3 of TS 38.521-1 [8] with parameters specified in Tables 7.6B.3.3.5-3 and 7.6B.3.3.5-4. + +For NR bands with $F_{DL\_low} \geq 3300$ MHz and $F_{UL\_low} \geq 3300$ MHz, except for the spurious response frequencies recorded in test procedure, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 and A.3.3 of TS 38.521-1 [8] with parameters specified in Tables 7.6B.3.3.5-5 and 7.6B.3.3.5-6. + +If CW interferer falls in a gap between $F_{DL\_high}$ of the E-UTRA or NR band and $F_{DL\_low}$ of the NR or EUTRA band, where the corresponding OOB ranges 1 and 2 in Table 7.6B.3.3.5-2 and Table 7.6B.3.3.5-4 or Table 7.6B.3.3.5-6 overlap, then the lower level interferer limit of the overlapping OOB ranges applies. + +If $F_{DL\_high}$ of the lower E-UTRA or NR band is greater than or equal to the $F_{DL\_low}$ of the upper NR or E-UTRA band as in overlapping RX frequency ranges, then the OOB range shall start from the $F_{DL\_low}$ of the lower E-UTRA or NR band, and from the $F_{DL\_high}$ of the upper NR or E-UTRA band. + +For EN-DC combination listed in Table 7.6B.3.3.5-7 under the first test condition above, exceptions to the requirement specified in Table 7.6B.3.3.5-8 are allowed when the second order intermodulation product of the lower frequency band UL carrier and the CW interfering signal fully or partially overlaps with the higher frequency band DL carrier. + +For all interferer frequency ranges a maximum of + +$$\lfloor \max \{24, 6 \cdot \lceil n \cdot N_{RB} / 6 \rceil\} / \min \{\lceil n \cdot N_{RB} / 10 \rceil, 5\} \rfloor$$ + +exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a step size of $\min(\lfloor CBW / 2 \rfloor, 5)$ MHz with $N_{RB}$ the number of resource blocks in the downlink transmission bandwidth configuration, $CBW$ the bandwidth of the frequency channel in MHz and $n = 1, 2, 3$ for SCS = 15, 30, 60 kHz, respectively. For these exceptions, the requirements in clause 7.7B.3 apply. + +**Table 7.6B.3.3.5-1: Out-of-band blocking parameters for E-UTRA bands** + +| Rx Parameter | Units | Channel bandwidth | | | | | | +|-----------------------------------------------|-------|--------------------------------------------------|-------|-------|--------|--------|--------| +| | | 1.4 MHz | 3 MHz | 5 MHz | 10 MHz | 15 MHz | 20 MHz | +| Power in Transmission Bandwidth Configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | | +| | | 6 | 6 | 6 | 6 | 7 | 9 | + +Note 1: The reference measurement channel is specified in Annex A.3.2 of TS 36.521-1 [10] with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex A.5.1.1/A.5.2.1 of TS 36.521-1 [10]. + +Note 2: The REFSENS power level is specified in Table 7.3.3-1 of TS 36.521-1 [10] for two and four antenna ports, respectively. + +**Table 7.6B.3.3.5-2: Out of band blocking for E-UTRA bands** + +| E-UTRA band | Parameter | Units | Frequency | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------|--------------------------------------------|--------------------------------------------|-----------------------------------|------------------------------| +| | | | range 1 | range 2 | range 3 | range 4 | +| | $P_{Interferer}$ | dBm | -44 | -30 | -15 | -15 | +| 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 30, 31, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42 (Note 3), 43 (Note 3), 44, 45, 53, 65, 66, 68, 70, 71, 72, 73, 74 | $F_{Interferer}$ (CW) | MHz | $F_{DL\_low} - 15$ to $F_{DL\_low} - 60$ | $F_{DL\_low} - 60$ to $F_{DL\_low} - 85$ | $F_{DL\_low} - 85$ to 1 MHz | - | +| | | | $F_{DL\_high} + 15$ to $F_{DL\_high} + 60$ | $F_{DL\_high} + 60$ to $F_{DL\_high} + 85$ | $F_{DL\_high} + 85$ to +12750 MHz | - | +| 2, 5, 12, 17 | $F_{Interferer}$ | MHz | - | - | - | $F_{UL\_low} - F_{UL\_high}$ | + +Note 1: Range 3 shall be tested only with the highest channel bandwidth. + +Note 2: For the UE which supports both Band 11 and Band 21 the out of blocking is FFS. + +Note 3: The power level of the interferer ( $P_{Interferer}$ ) for Range 3 shall be modified to -20 dBm for $F_{Interferer} > 2800$ MHz and $F_{Interferer} < 4400$ MHz. + +Note 4: For the UE that supports both Band 4 and Band 66, the out-of-blocking frequency range for Band 4 is defined relative to $F_{DL\_low}$ and $F_{DL\_high}$ of Band 66. + +**Table 7.6B.3.3.5-3: Out-of-band blocking parameters for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| RX parameter | Units | Channel bandwidth | | | | | +|-----------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------|---------|--------|--------|--------| +| | | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 6 | 6 | 7 | 9 | 10 | +| RX parameter | Units | Channel bandwidth | | | | | +| | | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 11 | 12 | 13 | 14 | 15 | +| RX parameter | Units | Channel bandwidth | | | | | +| | | 90 MHz | 100 MHz | | | | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 15.5 | 16 | | | | +| NOTE: The transmitter shall be at the minimum UL configuration specified in Table 7.3.2.3-3 of TS 38.521-1 [8]. | | | | | | | + +**Table 7.6B.3.3.5-4: Out of-band blocking for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| NR band | Parameter | Unit | Range 1 | Range 2 | Range 3 | +|------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------|---------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| n1, n2, n3,
n5, n7, n8,
n12, n20,
n25, n28,
n34, n38,
n39, n40,
n41, n50,
n51, n65,
n66, n70,
n71, n74,
n75, n76 | $P_{\text{interferer}}$ | dBm | -44 | -30 | -15 | +| | $F_{\text{interferer}}$ (CW) | MHz | $-60 < f - F_{DL\_low} < -15$
or
$15 < f - F_{DL\_high} < 60$ | $-85 < f - F_{DL\_low} \leq -60$
or
$60 \leq f - F_{DL\_high} < 85$ | $1 \leq f \leq F_{DL\_low} - 85$
or
$F_{DL\_high} + 85 \leq f \leq 12750$ | + +NOTE 1: The power level of the interferer ( $P_{\text{interferer}}$ ) for Range 3 shall be modified to -20 dBm for $F_{\text{interferer}} > 6000$ MHz. +NOTE 2: For band 51 the $F_{DL\_high}$ of band 50 is applied as $F_{DL\_high}$ for band 51. For band 50, the $F_{DL\_low}$ of band 51 is applied as $F_{DL\_low}$ for band 50. +NOTE 3: For band 76 the $F_{DL\_high}$ of band 75 is applied as $F_{DL\_high}$ for band 76. For band 75, the $F_{DL\_low}$ of band 76 is applied as $F_{DL\_low}$ for band 75. +NOTE 4: For UEs supporting both bands 38 and 41, the $F_{DL\_high}$ and $F_{DL\_low}$ of band 41 is applied as $F_{DL\_high}$ and $F_{DL\_low}$ for band 38. + +**Table 7.6B.3.3.5-5: Out-of-band blocking parameters for NR bands with $F_{DL\_low} \geq 3300$ MHz and $F_{UL\_low} \geq 3300$ MHz** + +| RX parameter | Units | Channel bandwidth | | | | | +|-----------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------|--------|--------|---------|--------| +| | | 10 MHz | 15 MHz | 20 MHz | 40 MHz | 50 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 6 | 7 | 9 | 9 | 9 | +| RX parameter | Units | Channel bandwidth | | | | | +| | | 60 MHz | 80 MHz | 90 MHz | 100 MHz | | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 9 | 9 | 9 | 9 | | +| NOTE: The transmitter shall be at the minimum UL configuration specified in Table 7.3.2.3-3 of TS 38.521-1 [8]. | | | | | | | + +**Table 7.6B.3.3.5-6: Out of-band blocking for NR bands with $F_{DL\_low} \geq 3300$ MHz and $F_{UL\_low} \geq 3300$ MHz** + +| NR band | Parameter | Unit | Range 1 | Range 2 | Range 3 | +|----------------------|-----------------------|------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| n77, n78
(NOTE 3) | $P_{interferer}$ | dBm | -44 | -30 | -15 | +| | $F_{interferer}$ (CW) | MHz | $-60 < f - F_{DL\_low} \leq -3CBW$
or
$3CBW \leq f - F_{DL\_high} < 60$ | $-200 < f - F_{DL\_low} \leq -MAX(60,3CBW)$
or
$MAX(60,3CBW) \leq f - F_{DL\_high} < 200$ | $1 \leq f \leq F_{DL\_low} - MAX(200,3CBW)$
or
$F_{DL\_high} + MAX(200,3CBW) \leq f \leq 12750$ | +| n79
(NOTE 4) | $F_{interferer}$ (CW) | MHz | N/A | $-150 < f - F_{DL\_low} \leq -MAX(60,3CBW)$
or
$MAX(60,3CBW) \leq f - F_{DL\_high} < 150$ | $1 \leq f \leq F_{DL\_low} - MAX(150,3CBW)$
or
$F_{DL\_high} + MAX(150,3CBW) \leq f \leq 12750$ | + +NOTE 1: The power level of the interferer ( $P_{interferer}$ ) for Range 3 shall be modified to -20 dBm for $F_{interferer} > 6000$ MHz. + +NOTE 2: CBW denotes the channel bandwidth of the wanted signal + +NOTE 3: The power level of the interferer ( $P_{interferer}$ ) for Range 3 shall be modified to -20 dBm, for $F_{interferer} > 2700$ MHz and $F_{interferer} < 4800$ MHz. For CBW $> 15$ MHz, the requirement for Range 1 is not applicable and Range 2 applies from the frequency offset of 3CBW from the band edge. For CBW larger than 60 MHz, the requirement for Range 2 is not applicable and Range 3 applies from the frequency offset of 3CBW from the band edge. + +NOTE 4: The power level of the interferer ( $P_{interferer}$ ) for Range 3 shall be modified to -20 dBm, for $F_{interferer} > 3650$ MHz and $F_{interferer} < 5750$ MHz. For CBW $\geq 40$ MHz, the requirement for Range 2 is not applicable and Range 3 applies from the frequency offset of 3CBW from the band edge. + +**Table 7.6B.3.3.5-7: EN-DC combination with exceptions allowed** + +| EN-DC combination | +|-------------------| +| DC_5_n78 | +| DC_8_n77 | +| DC_8_n78 | +| DC_11_n77 | +| DC_18_n77 | +| DC_18_n78 | +| DC_18_n79 | +| DC_19_n77 | +| DC_19_n78 | +| DC_19_n79 | +| DC_20_n78 | +| DC_21_n77 | +| DC_26_n77 | +| DC_26_n78 | +| DC_26_n79 | +| DC_28_n77 | +| DC_28_n78 | +| DC_28_n79 | + +**Table 7.6B.3.3.5-8: Exceptions allowed** + +| Parameter | Unit | Level | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------| +| $P_{\text{interferer}}$ (CW) | dBm | -44 1 | +| NOTE 1: The requirement applies when $ f_{\text{interferer}} \pm f_{UL}^{LB} - f_{DL}^{HB} \leq (BW_{UL}^{LB} + BW_{DL}^{HB})/2$ , where $f_{UL}^{LB}$ and $f_{DL}^{HB}$ are the carrier frequencies for lower frequency band UL and higher frequency band DL, respectively. $BW_{UL}^{LB}$ and $BW_{DL}^{HB}$ are the channel bandwidths configured for lower frequency band UL carrier and higher frequency band DL carrier in MHz, respectively. | | | + +#### 7.6B.3.3\_1 Out-of-band blocking for EN-DC within FR1 (>2 CCs) + +##### 7.6B.3.3\_1.1 Out-of-band blocking for EN-DC within FR1 (3 CCs) + +###### 7.6B.3.3\_1.1.1 Test Purpose + +Out-of-band band blocking is defined for an unwanted CW interfering signal falling more than 15 MHz below or above the UE receive band, at which a given average throughput shall meet or exceed the requirement for the specified measurement channels. + +For the first 15 MHz below or above the UE receive band the appropriate in-band blocking or adjacent channel selectivity in clause 7.6B.2.1 and clause 7.5B.1 shall be applied. + +The lack of out-of-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +###### 7.6B.3.3\_1.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC within FR1 with 3 DL CCs. + +###### 7.6B.3.3\_1.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.3.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 7.6B.3.3\_1.1.4 Test Description + +###### 7.6B.3.3\_1.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.3.3\_1.1.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.3.3\_1.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|------------------------------------|--------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest $N_{RB\_agg}$ (NOTE 3) | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| PCC – E-UTRA | | SCC – EUTRA | | NR | | +| UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | +| QPSK/QPSK | REFSENS/Full RB | NA/QPSK | NA/Full RB | DFT-s-OFDM
QPSK/CP-OFDM
QPSK | REFSENS/Full RB (NOTE 1) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same $N_{RB\_agg}$ , only the combination with the highest $N_{RB\_SCG}$ is tested. + +NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. + +NOTE 5: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.3.3\_1.1.4.3. + +###### 7.6B.3.3\_1.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for *C\_RNTI* to transmit the DL RMC according to Table 7.6B.3.3\_1.1.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for *C\_RNTI* to schedule the UL RMC according to Table 7.6B.3.3\_1.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + +3. Set the Downlink signal level to the value as defined in Table 7.6B.3.3\_1.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.6B.3.3\_1.1.5-1 + ( $\lceil 10\log(S\_LCRB/N_{RB\_alloc}) \rceil$ for NR CC, $\lceil 10\log(P\_LCRB/N_{RB\_alloc}) \rceil$ for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.3.3\_1.1.5-1. The frequency step size is 1MHz. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.3.3\_1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED with the following exceptions. + +**Table 7.6B.3.3\_1.1.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | + +**Table 7.6B.3.3\_1.1.4.3-2: RRCConnectionReconfiguration** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|---------------------------------------|--------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE AND pc_dynamicPower Sharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPower Sharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPower Sharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPower Sharing | +| } | | | | + +###### 7.6B.3.3\_1.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.6B.3.3\_1.1.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.6B.3.3\_1.1.5-1: Out-of-band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $>100, \leq 120$ | $>120, \leq 140$ | $>140, \leq 160$ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------|------------------|------------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | +|

NOTE 1: Interferer values and offsets are specified from Table 7.6.2.1A-2 in TS 36.101 [5]. For inter-band combinations where the intra-band requirements are applicable, in which the E-UTRA band is a subset of an NR-only band, the NR band interferer values and offsets specified from Table 7.6A.3-2 in TS 38.101-1 [2] apply to both E-UTRA and NR carriers.

NOTE 2: For NR carrier, the transmitter shall be set to 4dB below P_{\text{CMAX\_L,f,c,NR}} at the minimum uplink configuration specified in Table 7.3.2-3 in TS 8.101-1 [2] with P_{\text{CMAX\_L,f,c,NR}} as defined in clause 6.2B.4.

NOTE 3: For E-UTRA carrier, the transmitter shall be set to 4dB below P_{\text{CMAX\_L\_E-UTRA,c}} at the minimum uplink configuration specified in Table 7.3.1-2in TS 36.101 [5] with P_{\text{CMAX\_L\_E-UTRA,c}} as defined in clause 6.2B.4 for single carrier.

| | | | | + +##### 7.6B.3.3\_1.2 Out-of-band blocking for EN-DC within FR1 (4 CCs) + +###### 7.6B.3.3\_1.2.1 Test Purpose + +Out-of-band band blocking is defined for an unwanted CW interfering signal falling more than 15 MHz below or above the UE receive band, at which a given average throughput shall meet or exceed the requirement for the specified measurement channels. + +For the first 15 MHz below or above the UE receive band the appropriate in-band blocking or adjacent channel selectivity in clause 7.6B.2.1 and clause 7.5B.1 shall be applied. + +The lack of out-of-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +###### 7.6B.3.3\_1.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC within FR1 with 4 DL CCs. + +###### 7.6B.3.3\_1.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.3.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 7.6B.3.3\_1.2.4 Test Description + +###### 7.6B.3.3\_1.2.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.3.3\_1.2.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.3.3\_1.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------|-------------------------|------------------------------------|-----------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest $N_{RB\_agg}$ (NOTE 3) | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| PCC – E-UTRA | | SCC1 – EUTRA and SCC2 – EUTRA | | NR | | +| UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | +| QPSK/QPSK | REFSENS/Full RB | NA/QPSK | NA/Full RB | DFT-s-OFDM
QPSK/CP-OFDM
QPSK | REFSENS/Full RB
(NOTE 1) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same $N_{RB\_agg}$ , only the combination with the highest $N_{RB\_SCG}$ is tested. + +NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. + +NOTE 5: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2 , A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.3.3\_1.2.4.3. + +###### 7.6B.3.3\_1.2.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.3\_1.2.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.3\_1.2.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.3.3\_1.2.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power + +measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of the target power level in Table 7.6B.3.3\_1.2.5-1 + ( $10\log(S\_LCRB/N_{RB\_alloc})$ ) for NR CC, $[10\log(P\_LCRB/N_{RB\_alloc})]$ for E-UTRA CC) for at least the duration of the Throughput measurement, where: + +- MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.3.3\_1.2.5-1. The frequency step size is 1MHz. + 5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. + 6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.3.3\_1.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED with the following exceptions. + +**Table 7.6B.3.3\_1.2.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | + +**Table 7.6B.3.3\_1.2.4.3-2: RRCConnectionReconfiguration** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|--------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE AND pc_dynamicPower Sharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPower Sharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPower Sharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPower Sharing | +| } | | | | + +###### 7.6B.3.3\_1.2.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.6B.3.3\_1.2.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.6B.3.3\_1.2.5-1: Out-of-band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $>100, \leq 120$ | $>120, \leq 140$ | $>140, \leq 160$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------|------------------|------------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | +|

NOTE 1: Interferer values and offsets are specified from Table 7.6.2.1A-2 in TS 36.101 [5]. For inter-band combinations where the intra-band requirements are applicable, in which the E-UTRA band is a subset of an NR-only band, the NR band interferer values and offsets specified from Table 7.6A.3-2 in TS 38.101-1 [2] apply to both E-UTRA and NR carriers.

NOTE 2: For NR carrier, the transmitter shall be set to 4dB below P_{\text{CMAX\_L,f,c,NR}} at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with P_{\text{CMAX\_L,f,c,NR}} as defined in clause 6.2B.4.

NOTE 3: For E-UTRA carrier, the transmitter shall be set to 4dB below P_{\text{CMAX\_L\_E-UTRA,c}} at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with P_{\text{CMAX\_L\_E-UTRA,c}} as defined in clause 6.2B.4 for single carrier.

| | | | | + +### 7.6B.4 Narrow band blocking for DC + +#### 7.6B.4.0 Minimum Conformance Requirements + +##### 7.6B.4.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC narrow band blocking requirement and parameters are defined in Table 7.6B.4.0.1-1. + +**Table 7.6B.4.0.1-1: Narrow band blocking parameters for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $> 100, \leq 120$ | $> 120, \leq 140$ | $> 140, \leq 160$ | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-------------------|-------------------|-------------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 16 | | | | +| Puw, dBm (CW) | -55 | | | | +| NOTE 1: Jammer offset is from Table 7.6.3.1A-1 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier.
NOTE 2: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,f,c,NR}}$ at the minimum uplink configuration specified in Table 7.3.2-3 [2] with $P_{\text{CMAX\_L,f,c,NR}}$ as defined in clause 6.2B.4.
NOTE 3: For E-UTRA carrier, the transmitter shall be set to 29dB below $P_{\text{CMAX\_L,E-UTRA,c}}$ at the minimum uplink configuration specified in Table 7.3.1-2 [5] with $P_{\text{CMAX\_L,E-UTRA,c}}$ as defined in clause 6.2B.4 for single carrier.
NOTE 4: If NR carrier BW > 40 MHz, no narrow band blocking requirements apply when blocker is applied at the edge of the NR carrier. | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.4.1. + +##### 7.6B.4.0.2 Intra-band non-contiguous EN-DC + +For the E-TRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.6.3.1 for single carrier operation and in clause 7.6.3.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.6.4 in TS 38.101-1 [2]. + +The blocker configuration is defined in the general clause 7.1. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.4.2. + +##### 7.6B.4.0.3 Inter-band EN-DC within FR1 + +Narrow band blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.3.1 and 7.6.3.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.4 and 7.6A.4 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.4.3. + +##### 7.6B.4.0.3a Inter-band NE-DC within FR1 + +Narrow band blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.3.1 and 7.6.3.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.4 and 7.6A.4 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.4.3a. + +##### 7.6B.4.0.4 Inter-band EN-DC including FR2 + +Narrow band blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.3.1 and 7.6.3.1A of TS 36.101 [5] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.4.4. + +##### 7.6B.4.0.5 Inter-band EN-DC including both FR1 and FR2 + +Narrow band blocking requirement for E-UTRA single carrier and CA operation specified in clauses 7.6.3.1 and 7.6.3.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.6.4 and 7.6A.4 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6B.4.5. + +#### 7.6B.4.1 Narrow band blocking for intra-band contiguous EN-DC (2 CCs) + +##### 7.6B.4.1.1 Test Purpose + +Verifies a receiver's ability to receive EN-DC signals at its assigned channel frequencies in the presence of an unwanted narrow band CW interferer at a frequency, which is less than the nominal channel spacing. + +The lack of narrow-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +##### 7.6B.4.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.6B.4.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.4.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 7.6B.4.1.4 Test Description + +###### 7.6B.4.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.4.1.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.4.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------|----------------------|----------------------|------------------|-------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | | | +| NR/E-UTRA Test Parameters | | | | | | | | +| Downlink Configuration | | | | Uplink Configuration | | | | +| NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| CP-OFDM QPSK | Full RB (NOTE 1) | QPSK | Full RB | DFT-s-OFDM QPSK | REFSENS | QPSK | REFSENS | +| NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. | | | | | | | | +| NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. | | | | | | | | +| NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | | | | | | | +| NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. | | | | | | | | +| NOTE 5: In an E-UTRA band or FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.4.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 7.6B.4.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.4.1.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. + +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.4.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.4.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.6B.4.1.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) = 1.7dB, where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) = 2.0dB, where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.4.1.5-1. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +##### 7.6B.4.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +##### 7.6B.4.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.6B.4.1.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.6B.4.1.5-1: Narrow band blocking for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------|------------|------------|--|--|--|--| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | | | | | +| | 16 | | | | | | | | +| P uw , dBm (CW) | -55 | | | | | | | | +| NOTE 1: Jammer offset is from Table 7.6.3.1A-1 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier. | | | | | | | | | +| NOTE 2: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c,NR at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with P CMAX_L,f,c,NR as defined in clause 6.2B. | | | | | | | | | +| NOTE 3: For E-UTRA carrier, the transmitter shall be set to 29dB below P CMAX_L,E-UTRA,c at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with P CMAX_L,E-UTRA,c as defined in clause 6.2B.4 for single carrier. | | | | | | | | | +| NOTE 4: If NR carrier BW > 40 MHz, no narrow band blocking requirements apply when blocker is applied at the edge of the NR carrier. | | | | | | | | | + +**Table 7.6B.4.1.5-2: Void** + +**Table 7.6B.4.1.5-3: Void** + +#### 7.6B.4.2 Narrow band blocking for intra-band non-contiguous EN-DC (2 CCs) + +##### 7.6B.4.2.1 Test Purpose + +Same test purpose as in clause 7.6.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.6B.4.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.6B.4.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.4.0.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.6B.4.2.4 Test Description + +Same test description as in clause 7.6.4.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +**Table 7.6B.4.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | High range with maxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1 except for the parameters specified in Table 7.6B.4.2.4-1. + +For Initial conditions as in clause 7.6.4.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6.4.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add steps 7 and 8 to Initial conditions in clause 7.6.4.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. +8. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Step 3 of Test procedure as in clause 7.6.4.4.2 in TS 38.521-1 [8] shall treat the in-gap tests as below: For intra-band non-contiguous EN-DC of two sub-blocks with channel bandwidth larger than or equal to 5 MHz, the existing requirements apply for in-gap tests only if the corresponding interferer frequency offsets satisfy the following condition in relation to the sub-block gap size $W_{\text{gap}}$ , so that the interferer frequency position does not change the nature of the core requirement tested: + +$$W_{\text{gap}} \geq 2 \cdot |F_{\text{Interferer}}(\text{offset})| - BW_{\text{Channel}}$$ + +Step 4 of Test procedure as in clause 7.6.4.4.2 in TS 38.521-1 [8] is replaced by: + +4. Set the downlink signal level for NR CC according to the Table 7.6.4.5-1 in TS 38.521-1 [8] as appropriate. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as - MU to -(MU + Uplink power control window size) dB of ( $P_{\text{CMAX\_L,c}}$ - 29dB) for E-UTRA CC, and of 4dB below $P_{\text{CMAX\_L,fc}}$ for NR CC for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +##### 7.6B.4.2.5 Test Requirement + +Same test requirement as in clause 7.6.4.5 in TS 38.521-1 [8]. + +#### 7.6B.4.3 Narrow band blocking for inter-band EN-DC within FR1 (1 NR CC) + +##### 7.6B.4.3.1 Test Purpose + +Same test purpose as in clause 7.6.4.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.6B.4.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR DL CC. + +##### 7.6B.4.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.4.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.6B.4.3.4 Test Description + +Same test description as in clause 7.6.4.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6.4.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6.4.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6.4.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +##### 7.6B.4.3.5 Test Requirement + +Same test requirement as in clause 7.6.4.5 in TS 38.521-1 [8]. + +#### 7.6B.4.3\_1 Narrow band blocking for EN-DC within FR1 (>2 CCs) + +##### 7.6B.4.3\_1.1 Narrow band blocking for EN-DC within FR1 (3 CCs) + +###### 7.6B.4.3\_1.1.1 Test Purpose + +Verifies a receiver's ability to receive EN-DC signals at its assigned channel frequencies in the presence of an unwanted narrow band CW interferer at a frequency, which is less than the nominal channel spacing. + +The lack of narrow-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +###### 7.6B.4.3\_1.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC within FR1 with 3 DL CCs or inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs). + +###### 7.6B.4.3\_1.1.3 Minimum Conformance Requirements + +For intra-band contiguous EN-DC within FR1 with 3 DL CCs: The minimum conformance requirements are defined in clause 7.6B.4.0.1. Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +For inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs): The minimum conformance requirements are defined in clause 7.6B.4.0.3. No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.6B.4.3\_1.1.4 Test Description + +###### 7.6B.4.3\_1.1.4.1 Intra-band contiguous EN-DC within FR1 with 3 DL CCs + +###### 7.6B.4.3\_1.1.4.1.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.4.3\_1.1.4.1.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.4.3\_1.1.4.1.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------------|------------------|------------------------------------|--------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| PCC – E-UTRA | | SCC – EUTRA | | NR | | +| UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | +| QPSK/QPSK | REFSENS/Full RB | NA/QPSK | NA/Full RB | DFT-s-OFDM
QPSK/CP-OFDM
QPSK | REFSENS/Full RB (NOTE 1) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB\_agg, only the combination with the highest NRB\_SCG is tested. + +NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. + +NOTE 5: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. + +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.4.3\_1.1.4.1.3. + +###### 7.6B.4.3\_1.1.4.1.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.4.3\_1.1.4.1.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.4.3\_1.1.4.1.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.4.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of the target power level in Table 7.6B.4.1.5-1 + ( $[10\log(S\_LCRB/N_{RB\_alloc})]$ for NR CC, $[10\log(P\_LCRB/N_{RB\_alloc})]$ for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency *f* and the channel bandwidth *BW* + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.4.1.5-1. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.4.3\_1.1.4.1.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +###### 7.6B.4.3\_1.1.4.2 Inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs) + +Same test description as in clause 7.6.4.4 or 7.6A.4.1.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6A.4.1.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.4.1.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.4.1.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.6B.4.3\_1.1.5 Test Requirement + +For intra-band contiguous EN-DC within FR1 with 3 DL CCs: Same test requirement as in clause 7.6B.4.1.5. + +For inter-band EN-DC within FR1 with 3 DL CCs (2NR DL CCs): Same test requirement as in clause 7.6A.4.1.5 in TS 38.521-1 [8]. + +###### 7.6B.4.3\_1.2 Narrow band blocking for EN-DC within FR1 (4 CCs) + +###### 7.6B.4.3\_1.2.1 Test Purpose + +Verifies a receiver's ability to receive EN-DC signals at its assigned channel frequencies in the presence of an unwanted narrow band CW interferer at a frequency, which is less than the nominal channel spacing. + +The lack of narrow-band blocking ability will decrease the coverage area when other NodeB transmitters exist (except in the adjacent channels and spurious response). + +###### 7.6B.4.3\_1.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC within FR1 with 4 DL CCs or inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs). + +###### 7.6B.4.3\_1.2.3 Minimum Conformance Requirements + +For intra-band contiguous EN-DC within FR1 with 4 DL CCs: The minimum conformance requirements are defined in clause 7.6B.4.0.1. Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +For inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs): The minimum conformance requirements are defined in clause 7.6B.4.0.3. No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.6B.4.3\_1.2.4 Test Description + +###### 7.6B.4.3\_1.2.4.1 Intra-band contiguous EN-DC within FR1 with 4 DL CCs + +###### 7.6B.4.3\_1.2.4.1.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] + +clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in Table 7.6B.4.3\_1.2.4.1.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in Annex A.2 and A.3 respectively. The details of the OCNG patterns used are specified in TS 36.521-1 [10] Annex A.5 and in TS 38.521-1 [8] Annex A.5 for E-UTRA CG and NR CG respectively. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.6B.4.3\_1.2.4.1.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------|------------------|------------------------------------|--------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Lowest | | | | | +| NR/E-UTRA Test Parameters | | | | | | +| PCC – E-UTRA | | SCC1 – EUTRA and SCC2 – EUTRA | | NR | | +| UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | UL/DL Modulation | UL/DL allocation | +| QPSK/QPSK | REFSENS/Full RB | NA/QPSK | NA/Full RB | DFT-s-OFDM
QPSK/CP-OFDM
QPSK | REFSENS/Full RB (NOTE 1) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. + +NOTE 2: Test Channel Bandwidths are checked separately for each EN-DC band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. + +NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB\_agg, only the combination with the highest NRB\_SCG is tested. + +NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2.3-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. + +NOTE 5: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 Annex A, in Figure A.3.1.4.2 for SS diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C and TS 38.521-1 [8] Annex C for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL and DL Reference Measurement channels are TS 36.521-1 [10] Annex A.2, A.3 and TS 38.521-1 [8] Annex A.2, A.3 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 7.6B.4.3\_1.2.4.1.3. + +###### 7.6B.4.3\_1.2.4.1.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.4.3\_1.2.4.1.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.4.3\_1.2.4.1.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.6B.4.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of the target power level in Table 7.6B.4.1.5-1 + ( $[10\log(S\_LCRB/N_{RB\_alloc})]$ for NR CC, $[10\log(P\_LCRB/N_{RB\_alloc})]$ for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal below the aggregated component carriers according to Table 7.6B.4.1.5-1. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 4 to 5, using an interfering signal above the aggregated component carriers at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.6B.4.3\_1.2.4.1.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +###### 7.6B.4.3\_1.2.4.2 Inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs) + +Same test description as in clause 7.6A.4.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6A.4.2.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.4.2.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.4.2.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.6B.4.3\_1.2.5 Test Requirement + +For intra-band contiguous EN-DC within FR1 with 4 DL CCs: Same test requirement as in clause 7.6B.4.1.5. + +For inter-band EN-DC within FR1 with 4 DL CCs (3NR DL CCs): Same test requirement as in clause 7.6A.4.2.5 in TS 38.521-1 [8]. + +##### 7.6B.4.3\_1.3 Narrow band blocking for EN-DC within FR1 (5 CCs) + +###### 7.6B.4.3\_1.3.1 Test Purpose + +Same test purpose as in clause 7.6B.4.3.1. + +###### 7.6B.4.3\_1.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 16 and forward, supporting inter-band EN-DC within FR1 with 5 DL CCs (4 NR DL CCs). + +###### 7.6B.4.3\_1.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.6B.4.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.6B.4.3\_1.3.4 Test Description + +Same test description as in clause 7.6A.4.3.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.6A.4.3.4.1 in TS 38.521-1 [8], add step 2.1 and step 3.1 as follows: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.6A.4.3.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +Add step 7 to Initial conditions in clause 7.6A.4.3.4.1 in TS 38.521-1 [8] as follows: + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.6B.4.3\_1.3.5 Test Requirement + +Same test requirement as in clause 7.6A.4.3.5 in TS 38.521-1 [8]. + +###### 7.6B.4.3\_1.4 Void + +##### 7.6B.4.3a Narrow band blocking for inter-band NE-DC within FR1 (2 CCs) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 7.6.4 and 7.6A.4 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 7.6.3 and 7.6.3A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +## 7.6E Blocking characteristics for V2X in FR1 + +### 7.6E.0 Minimum conformance requirements + +For intra-band V2X operation, the blocking characteristics specified in clause 7.6.1.1G in TS 36.101 [5] and specified in clause 7.6E in TS 38.101-1 [2] apply when all SL reception CCs are activated at same time. + +For inter-band con-current NR V2X operation, the blocking characteristics requirements shall be applied per each component carrier. The in-band blocking and out of band blocking requirement specified in clause 7.6E in TS 38.101-1 [2] shall apply on NR V2X carrier and the requirement specified in clause 7.6 in TS 36.101 [5] shall apply for the E-UTRA downlink reception in licensed band while all downlink carriers are active. The requirements specified in subclause 7.6.1.1G and 7.6.2.1G of TS 36.101 [5] shall apply for the E-UTRA sidelink reception and the requirements specified in subclause 7.6 of TS 38.101-1 [2] shall apply for the NR downlink reception while all downlink carriers are active. $P_{\text{Interferer}}$ power is increased by $\Delta R_{\text{IB,c}}$ in the requirement. + +No narrow band blocking requirement applied for NR V2X carrier. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.6E. + +### 7.6E.1 In-band blocking for V2X operation + +#### 7.6E.1.1 Test purpose + +In-band blocking is defined for an unwanted interfering signal falling into the frequency range (see clause 7.6.1 and 7.6.1G of TS 36.521-1 [10] and clause 7.6.2 and 7.6E.2 of TS 38.521-1 [8]), at which the relative throughput shall meet or exceed the requirement for the specified measurement channels. + +The lack of in-band blocking ability will decrease the coverage area when other transmitters exist (except in the adjacent channels and spurious response). + +#### 7.6E.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. The requirements in this test case can be well covered in clause 7.6.1 and 7.6.1G of TS 36.521-1 [10] and clause 7.6.2 and 7.6E.2 of TS 38.521-1 [8] and don't need to be tested again. + +### 7.6E.2 Out-of-band blocking for V2X operation + +#### 7.6E.2.1 Test purpose + +Out-of-band blocking for V2X is defined for an unwanted CW interfering signal falling into the frequency range ( see clause 7.6.2 and 7.6.2G of TS 36.521-1 [10] and clause 7.6.3 and 7.6E.3 of TS 38.521-1 [8] ), at which a given average throughput shall meet or exceed the requirement for the specified measurement channels in aggregated signals. + +The lack of out-of-band blocking ability will decrease the coverage area when other transmitters exist (except in the adjacent channels and spurious response). + +#### 7.6E.2.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. The requirements in this test case can be well covered in clause 7.6.2 and 7.6.2G of TS 36.521-1 [10] and clause 7.6.3 and 7.6E.3 of TS 38.521-1 [8] and don't need to be tested again. + +## 7.7 Void + +## 7.7A Spurious response for CA + +### 7.7A.1 Test purpose + +Same test purpose as in clause 7.7 in TS 38.521-1 [8] for NR FR1 carrier(s). + +### 7.7A.2 Test applicability + +The requirements are only for FR1. Therefore, only the conducted requirements are tested. + +No test case details are specified. The NR/5GC requirements for Spurious response apply and are tested in TS 38.521-1 [8] clause 7.7 and 7.7A. + +## 7.7B Spurious response for DC + +### 7.7B.0 Minimum Conformance Requirements + +#### 7.7B.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC spurious response requirement and parameters are defined in Table 7.7B.0.1-1. + +**Table 7.7B.0.1-1: Spurious Response Parameters for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------|------------|------------| +| P w in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | +| P interferer , dBm (CW) | -44 | | | | +| NOTE 1: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c,NR at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with P CMAX_L,f,c,NR as defined in clause 6.2B.4.
NOTE 2: For E-UTRA carrier, the transmitter shall be set to 29dB below P CMAX_L,E-UTRA,c at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with P CMAX_L,E-UTRA,c as defined in clause 6.2B.4 for single carrier. | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7B.1. + +#### 7.7B.0.2 Intra-band non-contiguous EN-DC + +For the E-UTRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.7.1 for single carrier operation and in clause 7.7.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.7 in TS 38.101-1 [2]. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7B.2. + +#### 7.7B.0.3 Inter-band EN-DC within FR1 + +Spurious response requirement for E-UTRA single carrier and CA operation specified in clauses 7.7.1 and 7.7.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.7 and 7.7A of TS 38.101-1 [2] apply for lowest level EN-DC fallbacks (two bands) in clause 5.5B.4.1 with following conditions: + +- one E-UTRA uplink carrier with the output power set to 4 dB below $P_{\text{CMAX\_L,c}}$ and the NR band whose downlink is being tested has its uplink carrier output power set to 29 dB below $P_{\text{CMAX\_L,fc}}$ . +- one NR uplink carrier with the output power set to 4 dB below $P_{\text{CMAX\_L,fc}}$ on the NR band with both E-UTRA and NR downlinks being tested with E-UTRA output power set to 29 dB below $P_{\text{CMAX\_L,c}}$ . + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7B.3. + +#### 7.7B.0.3a Inter-band NE-DC within FR1 + +Spurious response requirement for E-UTRA single carrier and CA operation specified in clauses 7.7.1 and 7.7.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.7 and 7.7A of TS 38.101-1 [2] apply for lowest level NE-DC fallbacks (two bands) in clause 5.5B.4a.1 with following conditions: + +- one E-UTRA uplink carrier with the output power set to 4 dB below $P_{\text{CMAX\_L,c}}$ and the NR band whose downlink is being tested has its uplink carrier output power set to 29 dB below $P_{\text{CMAX\_L,fc}}$ . +- one NR uplink carrier with the output power set to 4 dB below $P_{\text{CMAX\_L,fc}}$ on the NR band with both E-UTRA and NR downlinks being tested with E-UTRA output power set to 29 dB below $P_{\text{CMAX\_L,c}}$ . + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7B.3a. + +#### 7.7B.0.4 Inter-band EN-DC including FR2 + +Spurious response requirement for E-UTRA single carrier and CA operation specified in clauses 7.7.1 and 7.7.1A of TS 36.101 [5] apply for lowest level EN-DC fallbacks (two bands) in clause 5.5B.5.1 with only E-UTRA UL with output power as in TS 36.101 [5] (4 dB below $P_{\text{CMAX\_L}}$ ). + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7B.4. + +#### 7.7B.0.5 Inter-band EN-DC including both FR1 and FR2 + +Spurious response requirement for E-UTRA single carrier and CA operation specified in clauses 7.7.1 and 7.7.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.7 and 7.7A of TS 38.101-1 [2] apply for lowest level EN-DC fallbacks (three bands) in clause 5.5B.6.2 with only E-UTRA UL with output power as in TS 36.101 [5] (4 dB below $P_{\text{CMAX\_L}}$ ). + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7B.5. + +### 7.7B.1 Spurious Response for intra-band contiguous EN-DC (2 CCs) + +#### 7.7B.1.1 Test Purpose + +Spurious response for EN-DC verifies the receiver's ability to receive a wanted aggregated signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in clause 7.6B.3.1 is not met. + +The lack of the spurious response ability decreases the coverage area when other unwanted interfering signal exists at any other frequency. + +#### 7.7B.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.7B.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.7B.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +#### 7.7B.1.4 Test Description + +##### 7.7B.1.4.1 Initial condition + +The initial conditions shall be the same as in clause 7.6B.3.1.4.1 in order to test spurious responses obtained in clause 7.6B.3.1 under the same conditions. + +##### 7.7B.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.1.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.7B.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.7B.1.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal according to Table 7.7B.1.5-1. The spurious frequencies are taken from records in the final step of test procedures in clause 7.6B.3.1.4.2. +5. For each spurious frequency, Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +##### 7.7B.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +#### 7.7B.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.7B.1.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.7B.1.5-1: Spurious Response for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $>100, \leq 120$ | $>120, \leq 140$ | $>140, \leq 160$ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------|------------------|------------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | +| $P_{\text{interferer}}$ , dBm (CW) | -44 | | | | +| NOTE 1: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,f,c,NR}}$ at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with $P_{\text{CMAX\_L,f,c,NR}}$ as defined in clause 6.2B.4.
NOTE 2: For E-UTRA carrier, the transmitter shall be set to 29dB below $P_{\text{CMAX\_L,E-UTRA,c}}$ at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with $P_{\text{CMAX\_L,E-UTRA,c}}$ as defined in clause 6.2B.4 for single carrier. | | | | | + +**Table 7.7B.1.5-2: Void** + +**Table 7.7B.1.5-3: Void** + +### 7.7B.2 Spurious Response for intra-band non-contiguous EN-DC (2 CCs) + +#### 7.7B.2.1 Test Purpose + +Same test purpose as in clause 7.7.1 in TS 38.521-1 [8] for the NR carrier. + +#### 7.7B.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.7B.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.7B.0.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.7B.2.4 Test Description + +Same test description as in clause 7.7.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial conditions shall be the same as the initial conditions in clause 7.6B.3.2.4 in order to test spurious responses obtained in clause 7.6B.3.2 under the same conditions. + +Step 4 of Test procedure as in clause 7.7.4.2 in TS 38.521-1 [8] is replaced by: + +- Set the downlink signal level for NR CC according to the Table 7.7.5-1 or 7.7.5-1a in TS 38.521-1 [8] as appropriate. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of $(P_{\text{CMAX\_L,c}} - 29\text{dB})$ for E-UTRA CC, and of 4dB below $P_{\text{CMAX\_L,f,c}}$ for NR CC for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + +- For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. +- For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +#### 7.7B.2.5 Test Requirement + +Same test requirement as in clause 7.7.5 in TS 38.521-1 [8]. + +### 7.7B.3 Spurious Response for inter-band EN-DC within FR1 (2 CCs) + +#### 7.7B.3.1 Test Purpose + +Spurious response is a measure of the ability of the receiver to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency for which a response is obtained, i.e. for which the out-of-band blocking limit as specified in subclause 7.6B.3.3 is not met. + +The lack of the spurious response ability decreases the coverage area when other unwanted interfering signal exists at any other frequency. + +#### 7.7B.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 2 DL CCs. + +#### 7.7B.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.7B.0.3. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +#### 7.7B.3.4 Test Description + +##### 7.7B.3.4.1 Initial Conditions + +The initial conditions shall be the same as in clause 7.6B.3.3.4.1 in order to test spurious responses obtained in clause 7.6B.3.3 under the same conditions. + +##### 7.7B.3.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.3.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.3.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.7B.3.5-1, Table 7.7B.3.5-3, or Table 7.7B.3.5-4 for E-UTRA CC and NR CC respectively. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of + +( $P_{\text{CMAX\_L,e}} - 4\text{dB}$ ) for E-UTRA CC, and of 29 dB below $P_{\text{CMAX\_L,fc}}$ for NR CC for at least the duration of the Throughput measurement, where: + +- MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal according to Table 7.7B.3.5-2. The spurious frequencies are taken from records in test procedures in clause 7.6B.3.3.4.2. + 5. For the spurious frequency, measure the average throughput of NR CC for a duration sufficient to achieve statistical significance according to Annex H.2. + 6. Set the Downlink signal level to the value as defined in Table 7.7B.3.5-1, Table 7.7B.3.5-3, or Table 7.7B.3.5-4 for E-UTRA CC and NR CC respectively. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of ( $P_{\text{CMAX\_L,fc}} - 4\text{dB}$ ) for NR CC, and of 29 dB below $P_{\text{CMAX\_L,e}}$ for E-UTRA CC for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + 7. Set the parameters of the CW signal generator for an interfering signal according to Table 7.7B.3.5-2. The spurious frequencies are taken from records in test procedures in clause 7.6B.3.3.4.2 for E-UTRA CC and NR CC testing respectively.. + 8. For the spurious frequency, measure the average throughput of E-UTRA CC and NR CC respectively for a duration sufficient to achieve statistical significance according to Annex H.2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +##### 7.7B.3.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 with the following exceptions. + +**Table 7.7B.3.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | + +**Table 7.7B.3.4.3-2: RRCConnectionReconfiguration** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | +| } | | | | + +#### 7.7B.3.5 Test Requirement + +For E-UTRA bands, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 of TS 36.521-1 [10] with parameters specified in Tables 7.7B.3.5-1 and 7.7B.3.5-2. + +For NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 and A.3.3 of TS 38.521-1 [8] with parameters specified in Tables 7.7B.3.5-3 and 7.7B.3.5-2. + +For NR bands with $F_{DL\_low} \geq 3300$ MHz and $F_{UL\_low} \geq 3300$ MHz, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 and A.3.3 of TS 38.521-1 [8] with parameters specified in Tables 7.7B.3.5-4 and 7.7B.3.5-2. + +**Table 7.7B.3.5-1: Spurious response parameters for E-UTRA bands** + +| Rx Parameter | Units | Channel bandwidth | | | | | | +|--------------|-------|-------------------|-------|-------|--------|--------|--------| +| | | 1.4 MHz | 3 MHz | 5 MHz | 10 MHz | 15 MHz | 20 MHz | +| | | | | | | | | + +| | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------------------------------------------------|---|---|---|---|---| +| Power in Transmission Bandwidth Configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | | +| | | 6 | 6 | 6 | 6 | 7 | 9 | +| Note 1: The reference measurement channel is specified in Annex A.3.2 of TS 36.521-1 [10] with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex A.5.1.1/A.5.2.1 of TS 36.521-1 [10].
Note 2: The REFSENS power level is specified in Table 7.3.3-1 of TS 36.521-1 [10] for two and four antenna ports, respectively. | | | | | | | | + +**Table 7.7B.3.5-2: Spurious Response for E-UTRA bands and NR bands** + +| Parameter | Unit | Level | +|------------------------------|------|-------------------------------| +| P Interferer (CW) | dBm | -44 | +| F Interferer | MHz | Spurious response frequencies | + +**Table 7.7B.3.5-3: Spurious response parameters for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| RX parameter | Units | Channel bandwidth | | | | | +|-----------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------|---------|--------|--------|--------| +| | | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 6 | 6 | 7 | 9 | 10 | +| RX parameter | Units | Channel bandwidth | | | | | +| | | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 11 | 12 | 13 | 14 | 15 | +| RX parameter | Units | Channel bandwidth | | | | | +| | | 90 MHz | 100 MHz | | | | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 15.5 | 16 | | | | +| NOTE: The transmitter shall be at the minimum UL configuration specified in Table 7.3.2.3-3 of TS 38.521-1 [8]. | | | | | | | + +**Table 7.7B.3.5-4: Spurious response parameters for NR bands with $F_{DL\_low} \geq 3300$ MHz and $F_{UL\_low} \geq 3300$ MHz** + +| RX parameter | Units | Channel bandwidth | | | | | +|-----------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------------|--------|--------|---------|--------| +| | | 10 MHz | 15 MHz | 20 MHz | 40 MHz | 50 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 6 | 7 | 9 | 9 | 9 | +| RX parameter | Units | Channel bandwidth | | | | | +| | | 60 MHz | 80 MHz | 90 MHz | 100 MHz | | +| Power in transmission bandwidth configuration | dBm | REFSENS + channel bandwidth specific value below | | | | | +| | dB | 9 | 9 | 9 | 9 | | +| NOTE: The transmitter shall be at the minimum UL configuration specified in Table 7.3.2.3-3 of TS 38.521-1 [8]. | | | | | | | + +#### 7.7B.3\_1 Spurious Response for EN-DC within FR1 (>2 CCs) + +##### 7.7B.3\_1.1 Spurious Response for EN-DC within FR1 (3 CCs) + +###### 7.7B.3\_1.1.1 Test Purpose + +Spurious response for EN-DC verifies the receiver's ability to receive a wanted aggregated signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in clause 7.6B.3.3\_1.1 is not met. + +The lack of the spurious response ability decreases the coverage area when other unwanted interfering signal exists at any other frequency. + +###### 7.7B.3\_1.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 3 DL CCs. + +###### 7.7B.3\_1.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.7B.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 7.7B.3\_1.1.4 Test Description + +###### 7.7B.3\_1.1.4.1 Initial condition + +The initial conditions shall be the same as in clause 7.6B.3.3\_1.1.4.1 in order to test spurious responses obtained in clause 7.6B.3.3\_1.1 under the same conditions. + +###### 7.7B.3\_1.1.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.3\_1.1.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.3\_1.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.7B.3\_1.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of the target power level in Table 7.7B.3\_1.1.5-1 + $([10\log(S\_LCRB/N_{RB\_alloc})])$ for NR CC, $[10\log(P\_LCRB/N_{RB\_alloc})]$ for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance + +is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +4. Set the parameters of the CW signal generator for an interfering signal according to Table 7.7B.3\_1.1.5-1. The spurious frequencies are taken from records in the final step of test procedures in clause 7.6B.3.3\_1.1.4.2. +5. For each spurious frequency, Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.7B.3\_1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED with the following exceptions. + +**Table 7.7B.3\_1.1.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | + +**Table 7.7B.3\_1.1.4.3-2: RRCConnectionReconfiguration** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | +| } | | | | + +###### 7.7B.3\_1.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.7B.3\_1.1.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.7B.3\_1.1.5-1: Spurious Response for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $>100, \leq 120$ | $>120, \leq 140$ | $>140, \leq 160$ | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------|------------------|------------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | +| $P_{\text{interferer}}$ , dBm (CW) | -44 | | | | +| NOTE 1: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,f,c,NR}}$ at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with $P_{\text{CMAX\_L,f,c,NR}}$ as defined in clause 6.2B.4.
NOTE 2: For E-UTRA carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L\_E-UTRA,c}}$ at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with $P_{\text{CMAX\_L\_E-UTRA,c}}$ as defined in clause 6.2B.4 for single carrier. | | | | | + +##### 7.7B.3\_1.2 Spurious Response for EN-DC within FR1 (4 CCs) + +###### 7.7B.3\_1.2.1 Test Purpose + +Spurious response for EN-DC verifies the receiver's ability to receive a wanted aggregated signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in clause 7.6B.3.3\_1.2 is not met. + +The lack of the spurious response ability decreases the coverage area when other unwanted interfering signal exists at any other frequency. + +###### 7.7B.3\_1.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 4 DL CCs. + +###### 7.7B.3\_1.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.7B.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +###### 7.7B.3\_1.2.4 Test Description + +###### 7.7B.3\_1.2.4.1 Initial condition + +The initial conditions shall be the same as in clause 7.6B.3.3\_1.2.4.1 in order to test spurious responses obtained in clause 7.6B.3.3\_1.2 under the same conditions. + +###### 7.7B.3\_1.2.4.2 Test procedure + +- SS transmits PDSCH via PDCCH DCI format 1A and PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6B.3.3\_1.2.4.1-1 on E-UTRA CC and NR CC respectively. The SS sends downlink MAC padding bits on the DL RMC. +- SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6B.3.3\_1.2.4.1-1 on E-UTRA CC and NR CC + +respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + +3. Set the Downlink signal level to the value as defined in Table 7.7B.3\_1.2.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.7B.3\_1.2.5-1 + ( [10log(S\_LCRB/NRB\_alloc)] for NR CC, [10log(P\_LCRB/NRB\_alloc)] for E-UTRA CC) for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +4. Set the parameters of the CW signal generator for an interfering signal according to Table 7.7B.3\_1.2.5-1. The spurious frequencies are taken from records in the final step of test procedures in clause 7.6B.3.3\_1.2.4.2. +5. For each spurious frequency, Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.7B.3\_1.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [6] clause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED with the following exceptions. + +**Table 7.7B.3\_1.2.4.3-1: PhysicalCellGroupConfig** + +| Derivation Path: TS 38.508-1 [6], Table 4.6.3-106 | | | | +|---------------------------------------------------|--------------|---------|-------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| p-NR-FR1 | 23 | | Power Class 3 UE AND pc_dynamicPowerSharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPowerSharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPowerSharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPowerSharing | + +**Table 7.7B.3\_1.2.4.3-2: RRCConnectionReconfiguration** + +| Derivation Path: TS 36.508 [11], Table 4.6.1-8 | | | | +|------------------------------------------------|--------------|----------------------------------------|--------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| nonCriticalExtension SEQUENCE { | | RRCConnectionReconfiguration-v1530-IEs | | +| p-MaxUE-FR1-r15 | 23 | | Power Class 3 UE AND pc_dynamicPower Sharing | +| | 20 | | Power Class 3 UE AND NOT pc_dynamicPower Sharing | +| | 26 | | Power Class 2 UE AND pc_dynamicPower Sharing | +| | 23 | | Power Class 2 UE AND NOT pc_dynamicPower Sharing | +| } | | | | + +###### 7.7B.3\_1.2.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in TS 36.521-1 [10] Annex A.3 and TS 38.521-1 [8] Annex A.3 for E-UTRA CG and NR CG respectively with parameters specified in Table 7.7B.3\_1.2.5-1 for the specified wanted signal mean power in the presence of interfering signals. + +**Table 7.7B.3\_1.2.5-1: Spurious Response for intra-band contiguous EN-DC** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $>100, \leq 120$ | $>120, \leq 140$ | $>140, \leq 160$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------|------------------|------------------| +| Pw in Transmission Bandwidth Configuration, perCC, dBm | REFSENS + Aggregated BW specific value below | | | | +| | 9 | | | | +| Pinterferer, dBm (CW) | -44 | | | | +| NOTE 1: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,f,c,NR}}$ at the minimum uplink configuration specified in Table 7.3.2-3 in TS 38.101-1 [2] with $P_{\text{CMAX\_L,f,c,NR}}$ as defined in clause 6.2B.4.
NOTE 2: For E-UTRA carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,E-UTRA,c}}$ at the minimum uplink configuration specified in Table 7.3.1-2 in TS 36.101 [5] with $P_{\text{CMAX\_L,E-UTRA,c}}$ as defined in clause 6.2B.4 for single carrier. | | | | | + +## 7.7E Spurious response for V2X in FR1 + +### 7.7E.0 Minimum conformance requirements + +For intra-band V2X operation, the spurious response specified in clause 7.7.1G in TS 36.101 [5] and specified in clause 7.7E in TS 38.101-1 [2] apply when all SL reception CCs are activated at same time. + +For the inter-band concurrent NR V2X operation, the spurious response requirements shall be applied per each component carrier. The requirements specified in subclause 7.7E of TS 38.101-1 [2] shall apply for the NR sidelink reception in Band n47 and the requirements specified in subclause 7.7.1 of TS 36.101 [5] shall apply for the E-UTRA downlink reception in licensed band while all downlink carriers are active. The requirements specified in subclause 7.7.1G of TS 36.101 [5] shall apply for the E-UTRA sidelink reception and the requirements specified in subclause 7.7 of TS 38.101-1 [2] shall apply for the NR downlink reception while all downlink carriers are active. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.7E. + +### 7.7E.1 Spurious response for V2X operation + +#### 7.7E.1.1 Test purpose + +Spurious response verifies the receiver's ability to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in sub-clause 7.6E.2 is not met. + +The lack of the spurious response ability decreases the coverage area when other unwanted interfering signal exists at any other frequency. + +#### 7.7E.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. The requirements in this test case can be well covered in clause 7.7 and 7.7G of TS 36.521-1 [10] and clause 7.7 and 7.7E of TS 38.521-1 [8] and don't need to be tested again. + +## 7.8 Void + +## 7.8B Intermodulation characteristics for DC + +### 7.8B.1 General + +### 7.8B.2 Wide band Intermodulation + +#### 7.8B.2.0 Minimum Conformance Requirements + +##### 7.8B.2.0.1 Intra-band contiguous EN-DC + +Intra-band contiguous EN-DC wide band intermodulation requirement and parameters are defined in Table 7.8B.2.0.1-1. + +**Table 7.8B.2.0.1-1: Wide band intermodulation** + +| EN-DC Aggregated Bandwidth, MHz | ≤100 | >100, ≤120 | >120, ≤140 | >140, ≤160 | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------|------------|------------|--|--|--|--| +| P w in Transmission Bandwidth Configuration, perCC, dBm | P w 1 | 16.8 | 17.5 | 18.0 | | | | | +| P interferer 1 , dBm (CW) 2 | -46 | | | | | | | | +| P interferer 2 , dBm (Modulated) 2 | -46 | | | | | | | | +| NOTE 1: P w is wanted signal power level from Table 7.8.1A-1 in TS 36.101 [5] | | | | | | | | | +| NOTE 2: Jammer BW and offsets is from Table 7.8.1A-1 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier | | | | | | | | | +| NOTE 3: For NR carrier, the transmitter shall be set to 4dB below P CMAX_L,f,c at the minimum uplink configuration specified in Table 7.3-3 with P CMAX_L,f,c as defined in clause 6.2B.4. | | | | | | | | | +| NOTE 4: For E-UTRA carrier, the transmitter shall be set to 29dB below P CMAX_L,c at the minimum uplink configuration specified in Table 7.3-1-2 with P CMAX_L,c as defined in clause 6.2B.4 for single carrier. | | | | | | | | | + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.8B.2.1. + +##### 7.8B.2.0.2 Intra-band non-contiguous EN-DC + +For the E-UTRA sub-block containing one or multiple CC's, the requirement is defined in clause 7.8.1 for single carrier operation and in clause 7.8.1A for CA in TS 36.101 [5]. + +For the NR sub-block, the requirement is defined in clause 7.8.2 in TS 38.101-1 [2]. + +The blocker configuration is defined in the general clause 7.1 and the requirement only apply for out of gap interferers. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.8B.2.2. + +##### 7.8B.2.0.3 Inter-band EN-DC within FR1 + +Wide band Intermodulation requirement for E-UTRA single carrier and CA operation specified in clauses 7.8.1 and 7.8.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.8.2 and 7.8A.2 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.8B.2.3. + +##### 7.8B.2.0.4 Inter-band EN-DC including FR2 + +Wide band Intermodulation requirement for E-UTRA single carrier and CA operation specified in clauses 7.8.1 and 7.8.1A of TS 36.101 [5] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.8B.2.4. + +##### 7.8B.2.0.5 Inter-band EN-DC including both FR1 and FR2 + +Wide band Intermodulation requirement for E-UTRA single carrier and CA operation specified in clauses 7.8.1 and 7.8.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.8.2 and 7.8A.2 of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.8B.2.5. + +#### 7.8B.2.1 Wideband Intermodulation for intra-band contiguous EN-DC (2 CCs) + +**Editor's note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- **UL Power configuration is TBD** + +##### 7.8B.2.1.1 Test Purpose + +Intermodulation response tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area when two or more interfering signals exist which have a specific frequency relationship to the wanted signal. + +##### 7.8B.2.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.8B.2.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.8B.2.0.1. + +Exception requirements for both NR and E-UTRA are defined for this test and therefore LTE anchor agnostic approach is not applied. E-UTRA test point analysis is included and E-UTRA measurements are performed. + +##### 7.8B.2.1.4 Test Description + +###### 7.8B.2.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.3B.1.2, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 7.8B.2.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.8B.2.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------|----------------------|----------------------|------------------|-------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Lowest N RB_agg , Highest N RB_agg (NOTE 3) | | | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | | | +| NR/E-UTRA Test Parameters | | | | | | | | +| Downlink Configuration | | | | Uplink Configuration | | | | +| NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | NR Modulation | NR RB allocation | E-UTRA Modulation | E-UTRA RB allocation | +| CP-OFDM
QPSK | Full RB (NOTE 1) | QPSK | Full RB | DFT-s-OFDM
QPSK | REFSENS | QPSK | REFSENS | +| NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 of TS 38.521-1 [8]. | | | | | | | | +| NOTE 2: Test Channel Bandwidths are checked separately for each E-UTRA band, which applicable channel bandwidths are specified in Table 5.3B.1.2-1. | | | | | | | | +| NOTE 3: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | | | | | | | +| NOTE 4: REFSENS refers to Uplink configuration in Table 7.3.2-3 in [8] and Table 7.3.3-2 in [10] for NR and E-UTRA CC respectively. | | | | | | | | +| NOTE 5: In an E-UTRA band or NR FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are TS 36.521-1 [10] Annex A.2 and TS 38.521-1 [8] Annex A.2 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.1.4.3. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +###### 7.8B.2.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 7.8B.2.1.4.1-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Set the Downlink signal level to the value as defined in Table 7.8B.2.1.5-1. For NR CC and E-UTRA CC, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.8B.2.1.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size. and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +3. Set the Interfering signal levels to the values as defined in Table 7.8B.2.1.5-1 and frequency below the wanted signal +4. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex G.2. +5. Repeat steps from 2 to 4, using an interfering signal above the wanted signal at step 3. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +###### 7.8B.2.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] clause 4.6 with DFT-s-OFDM condition in Table 4.6.3-118 PUSCH-Config. + +##### 7.8B.2.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 with parameters specified in Table 7.8B.2.1.5-1 for the specified wanted signal mean power in the presence of two interfering signals. + +**Table 7.8B.2.1.5-1: Wide band intermodulation** + +| EN-DC Aggregated Bandwidth, MHz | $\leq 100$ | $>100, \leq 120$ | $>120, \leq 140$ | $>140, \leq 160$ | +|------------------------------------------------------------------------------------------|-----------------------------|------------------|------------------|------------------| +| P w in Transmission Bandwidth Configuration, perCC, dBm | P w 1 | 16.8 | 17.5 | 18.0 | +| P interferer 1, dBm (CW) 2 | -46 | | | | +| P interferer 2, dBm (Modulated) 2 | -46 | | | | +| NOTE 1: P w is wanted signal power level from Table 7.8.1A-1 in TS 36.101 [5] | | | | | + +NOTE 2: Jammer BW and offsets is from Table 7.8.1A-1 in TS 36.101 [5] and is applied from the lowest edge of the lowest carrier and the highest edge of the highest carrier + +NOTE 3: For NR carrier, the transmitter shall be set to 4dB below $P_{\text{CMAX\_L,fc}}$ at the minimum uplink configuration specified in Table 7.3-3 with $P_{\text{CMAX\_L,fc}}$ as defined in clause 6.2.4 from [2]. + +NOTE 4: For E-UTRA carrier, the transmitter shall be set to 29dB below $P_{\text{CMAX\_L,c}}$ at the minimum uplink configuration specified in Table 7.3-1-2 with $P_{\text{CMAX\_L,c}}$ as defined in clause 6.2.5 for single carrier and in Table 7.3-1A-1 with $P_{\text{CMAX\_L}}$ as defined in clause 6.2.5A for LTE-CA from TS 36.101 [5]. + +**Table 7.8B.2.1.5-2: Void** + +#### 7.8B.2.2 Wideband Intermodulation for intra-band non-contiguous EN-DC (2 CCs) + +##### 7.8B.2.2.1 Test Purpose + +Same test purpose as in clause 7.8.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.8B.2.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous EN-DC in FR1 with 2 DL CCs. + +##### 7.8B.2.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.8B.2.0.2. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +##### 7.8B.2.2.4 Test Description + +Same test description as in clause 7.8.2.4 in TS 38.521-1 [8] with the following exceptions: + +**Table 7.8B.2.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | High range with maxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest $N_{\text{RB\_agg}}$ (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same $N_{\text{RB\_agg}}$ , only the combination with the highest $N_{\text{RB\_SCG}}$ is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 7.9B.2.4-1. + +For Initial conditions as in clause 7.8.2.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10].7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.8.2.4.2 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +Step 4 of Test procedure is replaced by: + +4. Set the Interfering signal levels to the values as defined in Table 7.8.2.5-1 and frequency at the out-of-gap of the sub-blocks. + +Step 6 of Test procedure is removed. + +##### 7.8B.2.2.5 Test Requirement + +Same test requirement as in clause 7.8.2.5 in TS 38.521-1 [8]. + +#### 7.8B.2.3 Wideband Intermodulation for inter-band EN-DC within FR1 (2 CCs) + +##### 7.8B.2.3.1 Test Purpose + +Same test purpose as in clause 7.8.2.1 in TS 38.521-1 [8] for the NR carrier. + +##### 7.8B.2.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 2 DL CCs. + +##### 7.8B.2.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.8B.2.0.3. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +##### 7.8B.2.3.4 Test Description + +Same test description as in clause 7.8.2.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +For band n28 / 28 used in EN-DC configurations with NOTE 8 of Table 5.5B.4.1-1, test channel bandwidth of 20MHz or more is tested with Low range test frequency. + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.8.2.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.8.2.4.2 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +##### 7.8B.2.3.5 Test Requirement + +Same test requirement as in clause 7.8.2.5 in TS 38.521-1 [8]. + +##### 7.8B.2.3\_1 Wideband Intermodulation for EN-DC within FR1 (>2 CCs) + +##### 7.8B.2.3\_1.1 Wideband Intermodulation for EN-DC within FR1 (3 CCs) + +Editor's note: The following aspects are either missing or not yet determined: + +- Test configuration for DC\_(n)XAA-nYA, DC\_XA-(n)YAA, DC\_XA-nXA-nYA, DC\_XA-YA\_nYA is missing in Table 7.8B.2.3\_1.1.4.1-1. + +###### 7.8B.2.3\_1.1.1 Test Purpose + +Intermodulation response tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area when two or more interfering signals exist which have a specific frequency relationship to the wanted signal. + +###### 7.8B.2.3\_1.1.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC within FR1 (3 CCs). + +###### 7.8B.2.3\_1.1.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.8B.2.0. + +###### 7.8B.2.3\_1.1.4 Test Description + +###### 7.8B.2.3\_1.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.2, 5.5B.3, and 5.5B.4, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.5B.2, 5.5B.3, and 5.5B.4 and are shown in table 7.8B.2.3\_1.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.8B.2.3\_1.1.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------|------------------------------|------------|-----------------------------------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB_agg | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | +| Network signalling value | NS_01 by default | | | | | +| Test Parameters for EN-DC Configurations | | | | | | +| EN-DC Configurations | Environment | Frequency | Bandwidth Combination | SCS | Other Parameter Settings | +| DC_(n)XCA | Default | Default | Default | Default | As per DC_(n)XCA in Table 7.3B.2.3_1.1.4.1-0 | +| DC_XC-nXA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.2) | +| DC_XA_XA-nXA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.2) | +| DC_XA_nYC | Default | Default | Default | Default | As per DC_XA-nYC in Table 7.3B.2.3_1.14.1-0 | +| DC_XA_nY(2A) | Default | Default | Default | Default | As per DC_XA_nY(2A) in Table 7.3B.2.3_1.14.1-0 | +| DC_XA_nYA-nZA | Default | Default | Default | Default | As per DC_XA_nYA-nZA in Table 7.3B.2.3_1.14.1-0 | +| DC_XC_nYA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3) | +| DC_XA-XA_nYA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3) | +| DC_XA-YA_nZA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3) | +| NOTE 1: Void | | | | | | +| NOTE 2: Void | | | | | | +| NOTE 3: Void | | | | | | +| NOTE 4: X, Y and Z in this table correspond to different bands i.e. X != Y != Z | | | | | | +| NOTE 5: The band combinations with difference appearance order of bands/sub-blocks in the band combination string are not distinguished. E.g. DC_YA-(n)XAA represents the set of DC_YA-(n)XAA and DC_(n)XAA-YA | | | | | | +| NOTE 6: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are TS 36.521-1 [10] Annex A.2 and TS 38.521-1 [8] Annex A.2 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.1.4.3. +7. For the E-UTRA CC(s) where anchor agnostic apply according to NOTE 1 in Table 7.3B.2.3\_1.1.4.1-0, downlink signal level and uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. Disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.8B.2.3\_1.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 7.8B.2.3\_1.1.4.2-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + 2. Set the Downlink signal level to the value as defined in Table 7.8B.2.3\_1.1.4.2-1. For E-UTRA CC and NR CC where uplink is allocated according to Table 7.8B.2.3\_1.1.4.1-1, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to - (MU + Uplink power control window size) dB of the 4dB below PCMAX\_L with PCMAX\_L as defined in clause 6.2B.4 for at least the duration of the Throughput measurement. + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. +- NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than, or no less than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. +3. Set the Interfering signal levels to the values as defined in Table 7.8B.2.3\_1.1.4.2-1 and frequency below the wanted signal. + 4. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex G, clause G.2. + 5. Repeat steps from 2 to 4, using an interfering signal above the wanted signal at step 3. + 6. Repeat steps 2 to 5 for component carriers listed in Table 7.8B.2.3\_1.1.4.2-1. + +**Table 7.8B.2.3\_1.1.4.2-1: Test repetition and measurement configuration** + +| DC configuration | Test parameters to select (NOTE 2) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| DC (n)XCA | 7.8B.2.1.5 | +| DC XA nYC | 7.8B.2.3.5 | +| DC XA nY(2A) | | +| DC XA nYA-nZA | | +| NOTE 1: Void | | +| NOTE 2: The reference for the placement of the interferer signals is the centre frequency of the carrier closest to the interferer among the carriers throughput is measured on. | | +| NOTE 3: Measure throughput on DL allocated CC. Where there are multiple rows for a single Test point ID, the test is repeated for each row. | | + +###### 7.8B.2.3\_1.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] clause 4.6 with DFT-s-OFDM condition in Table 4.6.3-118 PUSCH-Config. + +###### 7.8B.2.3\_1.1.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A, clause A.3.2 with parameters specified in Table 7.8B.2.3\_1.1.4.2-1 for the specified wanted signal mean power in the presence of two interfering signals. + +###### 7.8B.2.3\_1.2 Wideband Intermodulation for EN-DC within FR1 (4 CCs) + +###### 7.8B.2.3\_1.2.1 Test Purpose + +Intermodulation response tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area when two or more interfering signals exist which have a specific frequency relationship to the wanted signal. + +###### 7.8B.2.3\_1.2.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC within FR1 (4 CCs). + +###### 7.8B.2.3\_1.2.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.8B.2.0. + +###### 7.8B.2.3\_1.2.4 Test Description + +###### 7.8B.2.3\_1.2.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.2, 5.5B.3, and 5.5B.4, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 7.8B.2.3\_1.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.8B.2.3\_1.2.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------|------------------------------|------------|---------------------------------------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB,agg | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | +| Network signalling value | NS_01 by default | | | | | +| Test Parameters for EN-DC Configurations | | | | | | +| EN-DC Configurations | Environment | Frequency | Bandwidth Combination | SCS | Other Parameter Settings | +| DC_(n)XDA | Default | Default | Default | Default | As per DC_(n)XDA in Table 7.3B.2.3_1.2.4.1-1 | +| DC_XD_nXA | - | - | - | - | No test required (LTE 2CC fallback is tested in 7.8B.2.2) | +| DC_XA-XC_nXA | - | - | - | - | No test required (LTE 2CC fallback is tested in 7.8B.2.2) | +| DC_XA_nY(2A)-nZA | Default | Default | Default | Default | As per DC_XA_nY(2A)-nZA in Table 7.3B.2.3_1.2.4.1-1 | +| DC_XA_nYA-nZC | Default | Default | Default | Default | As per DC_XA_nYA-nZC in Table 7.3B.2.3_1.2.4.1-1 | +| DC_XD_nYA
DC_XA-YC_nZA
DC_XA-XA-YA_nZA
DC_XA-YA-ZA_nRA | - | - | - | - | No test required (LTE 2CC fallback is tested in 7.8B.2.2) | +| DC_XC_nYC
DC_XA-XA_nYC
DC_XA-YA_nYC | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.1) | +| DC_XC_nY(2A)
DC_XA-XA_nY(2A)
DC_XA-YA_nY(2A) | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.1) | +| DC_XC_nYA-nZA
DC_XA-XA_nYA-nZA
DC_XA-YA_nZA-nRA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.1) | +| DC_XA-YA_(n)ZAA
DC_XC_(n)YAA | - | - | - | - | No test required (LTE 2CC fallback is tested in 7.8B.2.2) | +| DC_(n)XCA-nYA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.1) | +| DC_XA-YA-ZA_nZA | - | - | - | - | No test required (LTE 2CC fallback is tested in 7.8B.2.2) | +| DC_XA-YA_nYA-nZA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.1) | + +NOTE 1: X, Y, Z and R in this table correspond to different bands i.e. X != Y != Z != R + +NOTE 2: The band combinations with difference appearance order of bands/sub-blocks in the band combination string are not distinguished. E.g. DC\_YA-(n)XAA represents the set of DC\_YA-(n)XAA and DC\_(n)XAA-YA + +NOTE 3: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFESENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are TS 36.521-1 [10] Annex A.2 and TS 38.521-1 [8] Annex A.2 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. + +- Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.1.4.3. +- For the E-UTRA CC(s) where anchor agnostic apply according to NOTE 4 in Table 7.3B.2.3\_1.2.4.1-1, downlink signal level and uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. Disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.8B.2.3\_1.2.4.2 Test procedure + +- SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 7.8B.2.3\_1.2.4.2-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +- Set the Downlink signal level to the value as defined in Table 7.8B.2.3\_1.2.4.2-1. For E-UTRA CC and NR CC where uplink is allocated according to Table 7.8B.2.3\_1.2.4.1-1, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to - (MU + Uplink power control window size) dB of the 4dB below PCMAX\_L with PCMAX\_L as defined in clause 6.2B.4 for at least the duration of the Throughput measurement. + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. + - For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than, or no less than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +- Set the Interfering signal levels to the values as defined in Table 7.8B.2.3\_1.2.4.2-1 and frequency below the wanted signal. +- Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex G, clause G.2. +- Repeat steps from 2 to 4, using an interfering signal above the wanted signal at step 3. +- Repeat steps 2 to 5 for component carriers listed in Table 7.8B.2.3\_1.2.4.2-1. + +**Table 7.8B.2.3\_1.2.4.2-1: Test repetition and measurement configuration** + +| DC configuration | Test parameters to select (NOTE 1) | +|------------------|------------------------------------| +| DC (n)XDA | 7.8B.2.1.5 | +| DC XA nY(2A)-nZA | 7.8B.2.3.5 | +| DC XA nYA-nZC | | + +NOTE 1: The reference for the placement of the interferer signals is the centre frequency of the carrier closest to the interferer among the carriers throughput is measured on. +NOTE 2: Measure throughput on DL allocated CC. Where there are multiple rows for a single Test point ID, the test is repeated for each row. + +###### 7.8B.2.3\_1.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] clause 4.6 with DFT-s-OFDM condition in Table 4.6.3-118 PUSCH-Config. + +###### 7.8B.2.3\_1.2.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A, clause A.3.2 with parameters specified in Table 7.8B.2.3\_1.2.4.2-1 for the specified wanted signal mean power in the presence of two interfering signals. + +###### 7.8B.2.3\_1.3 Wideband Intermodulation for EN-DC within FR1 (5 CCs) + +**Editor's note: The Table 7.8B.2.3\_1.3.4.2-1 are either missing or not yet determined.** + +###### 7.8B.2.3\_1.3.1 Test Purpose + +Intermodulation response tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area when two or more interfering signals exist which have a specific frequency relationship to the wanted signal. + +###### 7.8B.2.3\_1.3.2 Test Applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC within FR1 (5 CCs). + +###### 7.8B.2.3\_1.3.3 Minimum Conformance Requirements + +The minimum conformance requirements are defined in clause 7.8B.2.0. + +###### 7.8B.2.3\_1.3.4 Test Description + +###### 7.8B.2.3\_1.3.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies and channel bandwidths based on EN-DC operating bands specified in clause 5.5B.2, 5.5B.3, and 5.5B.4, channel bandwidths and sub-carrier spacings for the NR cell specified in TS 38.521-1 [8] clause 5.3 and channel bandwidth for the E-UTRA cell are specified in TS 36.521-1 [10] clause 5.4.2. All of these configurations shall be tested with applicable test parameters for each EN-DC configuration specified in clause 5.3B.1.2 and are shown in table 7.8B.2.3\_1.3.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 36.521-1 [10] Annex C.2 and in TS 38.521-1 [8] Annex C.2 for E-UTRA CG and NR CG respectively. + +**Table 7.8B.2.3\_1.3.4.1-1: Test configuration table** + +| Initial Conditions | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------|-----------------------|-----|---------------------------------------------------------------| +| Test Environment as specified in TS 38.508-1 [6] clause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different EN-DC bandwidth classes | Mid range | | | | | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB_agg | | | | | +| NR Test SCS as specified in Table 5.3.5-1 in TS 38.521-1 [8] | Highest | | | | | +| Network signalling value | NS_01 by default | | | | | +| Test Parameters for EN-DC Configurations | | | | | | +| EN-DC Configurations | Environment | Frequency | Bandwidth Combination | SCS | Other Parameter Settings | +| DC_XA-XA-YC_nZA | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.2) | +| DC_XA-YC_nZ(2A) | - | - | - | - | No test required (LTE 1CC fallback is tested in 7.8B.2.3_1.2) | + +NOTE 1: X, Y, Z and R in this table correspond to different bands i.e. X != Y != Z != R + +NOTE 2: The band combinations with difference appearance order of bands/sub-blocks in the band combination string are not distinguished. E.g. DC\_YA-(n)XAA represents the set of DC\_YA-(n)XAA and DC\_(n)XAA-YA + +NOTE 3: In a FR1 band where UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (TS 38.521-1 [8] Table 7.3.2.5-2) is used in the test requirements. + +1. Connect the SS to the UE antenna connectors as shown in [6] TS 38.508-1 A.3.1.2.1 for SS diagram and A.3.2 for UE diagram. +2. The parameter settings for the E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3, and the parameter settings for the NR cell are set up according to TS 38.508-1 [6] clause 4.4.3. +3. Downlink signals are initially set up according to TS 36.521-1 [10] Annex C.0 and TS 38.521-1 [8] Annex C.0 for E-UTRA CG and NR CG respectively, and uplink signals according to TS 36.521-1 [10] Annex H and TS 38.521-1 [8] Annex G for E-UTRA CG and NR CG respectively. +4. The UL Reference Measurement channels are TS 36.521-1 [10] Annex A.2 and TS 38.521-1 [8] Annex A.2 for E-UTRA CG and NR CG respectively. +5. Propagation conditions are set according to TS 36.521-1 [10] Annex B.0 and TS 38.521-1 [8] Annex B.0 for E-UTRA CG and NR CG respectively. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer *MCG* and *SCG*, Connected without release *On* according to TS 38.508-1 [6] clause 4.5. Message contents are defined in clause 6.2B.1.1.4.3. +7. For the E-UTRA CC(s) where anchor agnostic apply according to NOTE 4 in Table 7.3B.2.3\_1.2.4.1-1, downlink signal level and uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B, clause B.0 of TS 36.521-1 [10]. Disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +###### 7.8B.2.3\_1.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0 and DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to table 7.8B.2.3\_1.3.4.2-1 on E-UTRA CC and NR CC respectively. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Set the Downlink signal level to the value as defined in Table 7.8B.2.3\_1.3.4.2-1. For E-UTRA CC and NR CC where uplink is allocated according to Table 7.8B.2.3\_1.3.4.1-1, send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to - (MU + Uplink power control window size) dB of the 4dB below PCMAX\_L with PCMAX\_L as defined in clause 6.2B.4 for at least the duration of the Throughput measurement. + +- MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW. +- For NR CC, Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. +- For E-UTRA CC, Uplink power control window size = 1dB (UE power step size) + 1.0dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 36.101 [5], Table 6.3.5.2.1-1 and is 1.0dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1 of TS 36.521-1 [10]. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than, or no less than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F, clause F.4. + +3. Set the Interfering signal levels to the values as defined in Table 7.8B.2.3\_1.3.4.2-1 and frequency below the wanted signal. +4. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex G, clause G.2. +5. Repeat steps from 2 to 4, using an interfering signal above the wanted signal at step 3. +6. Repeat steps 2 to 5 for component carriers listed in Table 7.8B.2.3\_1.3.4.2-1. + +**Table 7.8B.2.3\_1.3.4.2-1: Test repetition and measurement configuration** + +FFS + +###### 7.8B.2.3\_1.3.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] clause 4.6 with DFT-s-OFDM condition in Table 4.6.3-118 PUSCH-Config. + +###### 7.8B.2.3\_1.3.5 Test Requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A, clause A.3.2 with parameters specified in Table 7.8B.2.3\_1.3.4.2-1 for the specified wanted signal mean power in the presence of two interfering signals. + +##### 7.8B.2.3\_1.4 Wideband Intermodulation for EN-DC within FR1 (6 CCs) + +TBD + +#### 7.8B.2.3a Wideband Intermodulation for inter-band NE-DC within FR1 (2 CCs) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 7.8.2 and 7.8A.2 of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 7.8.1 and 7.8.1A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +7.8B.2.4 to 7.8B.2.9 Void + +## 7.8E Intermodulation characteristics for V2X operation in FR1 + +### 7.8E.1 Wide band Intermodulation for V2X + +#### 7.8E.1.0 Minimum conformance requirements + +For intra-band V2X operation, the intermodulation characteristics specified in clause 7.8.1G in TS 36.101 [5] and specified in clause 7.8E in TS 38.101-1 [2] apply when all SL reception CCs are activated at same time. + +For inter-band NR V2X concurrent operation, the intermodulation characteristics requirements shall be applied per each component carrier. The wideband inter-modulation requirement specified in clause 7.8E in TS 38.101-1 [2] shall apply on NR V2X carrier and the requirement specified in clause 7.8.1 in TS 36.101 [5] shall apply on E-UTRA downlink reception in licensed band while all downlink carriers are active. The requirements specified in subclause 7.8.1G of TS 36.101 [5] shall apply for the E-UTRA sidelink reception and the requirements specified in subclause 7.8 of TS 38.101-1 [2] shall apply for the NR downlink reception while all downlink carriers are active. $P_{\text{Interferer}}$ power is increased by $\Delta R_{\text{IB,c}}$ in the requirement. + +#### 7.8E.1.1 Wide band Intermodulation for V2X operation + +##### 7.8E.1.1.1 Test purpose + +Intermodulation response tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area when two or more interfering signals exist which have a specific frequency relationship to the wanted signal. + +##### 7.8E.1.1.2 Test applicability + +No exception requirements applicable to NR V2X operation or E-UTRA V2X operation. The requirements in this test case can be well covered in clause 7.8.1 and 7.8.1G of TS 36.521-1 [10] and clause 7.8.2 and 7.8E.2 of TS 38.521-1 [8] and don't need to be tested again. + +## 7.9 Void + +## 7.9B Spurious emissions for DC + +### 7.9B.0 Minimum Conformance Requirements + +#### 7.9B.0.1 Intra-band contiguous EN-DC + +The requirement is defined in clause 7.9A.1 in TS 38.101-1 [2]. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.9B.1. + +#### 7.9B.0.2 Intra-band non-contiguous EN-DC + +Spurious emissions requirement for E-UTRA single carrier and CA operation specified in clauses 7.9.1 and 7.9.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.9 and 7.9A of TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.9B.2. + +#### 7.9B.0.3 Inter-band EN-DC within FR1 + +E-UTRA requirements from TS 36.101 [5] and NR requirements from TS 38.101-1 [2] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.9B.3. + +#### 7.9B.0.4 Inter-band EN-DC including FR2 + +Spurious emissions requirement for E-UTRA single carrier and CA operation specified in clauses 7.9.1 and 7.9.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clause 7.9 of TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.9B.4. + +#### 7.9B.0.5 Inter-band EN-DC including both FR1 and FR2 + +Spurious emissions requirement for E-UTRA single carrier and CA operation specified in clauses 7.9.1 and 7.9.1A of TS 36.101 [5] and for NR single carrier and CA operation specified in clauses 7.9 and 7.9A of TS 38.101-1 [2] and TS 38.101-2 [3] apply. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.9B.5. + +### 7.9B.1 Spurious Emissions for intra-band contiguous EN-DC (2 CCs) + +#### 7.9B.1.1 Test purpose + +Same test purpose as in clause 7.9.1 in TS 38.521-1 [8] for the NR carrier. + +#### 7.9B.1.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band contiguous EN-DC in FR1 with 2 DL CCs. + +#### 7.9B.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.9B.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.9B.1.4 Test description + +Same test description as in clause 7.9.4 in TS 38.521-1 [8] with the following exceptions: + +**Table 7.9B.1.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different DC bandwidth classes. | Mid range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest NRB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same NRB_agg , only the combination with the highest NRB_SCG is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 7.9B.1.4-1. + +For Initial conditions as in clause 7.9.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.9.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +#### 7.9B.1.5 Test requirement + +Same test requirement as in clause 7.9.5 in TS 38.521-1 [8]. + +### 7.9B.2 Spurious Emissions for intra-band non-contiguous EN-DC (2 CCs) + +#### 7.9B.2.1 Test purpose + +Same test purpose as in clause 7.9.1 in TS 38.521-1 [8] for the NR carrier. + +#### 7.9B.2.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting intra-band non-contiguous in FR1 with 2 DL CCs. + +#### 7.9B.2.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.9B.0.3. + +No exception requirements applicable to NR or LTE. LTE anchor agnostic approach is applied. + +#### 7.9B.2.4 Test description + +Same test description as in clause 7.9.4 in TS 38.521-1 [8] with the following exceptions: + +**Table 7.9B.2.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different DC bandwidth classes | MaxWGap | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 7.9B.2.4-1. + +For Initial conditions as in clause 7.9.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.9.4.1 in TS 38.521-1 [8] is replaced by the following two steps: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. +7. When E-UTRA and NR bands are TDD, ensure the same uplink-downlink configuration by giving SCG a delay of 3 E-UTRA subframes, or by giving MCG a delay of 2 subframes. + +#### 7.9B.2.5 Test requirement + +Same test requirement as in clause 7.9.5 in TS 38.521-1 [8]. + +### 7.9B.3 Spurious Emissions for inter-band EN-DC within FR1 (1 NR CC) + +#### 7.9B.3.1 Test purpose + +Same test purpose as in clause 7.9.1 in TS 38.521-1 [8] for the NR carrier. + +#### 7.9B.3.2 Test applicability + +This test case applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC within FR1 with 1 NR DL CC. + +#### 7.9B.3.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.9B.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +#### 7.9B.3.4 Test description + +Same test description as in clause 7.9.4 in TS 38.521-1 [8] for the NR carrier with the following exceptions: + +The initial test configurations for E-UTRA consist of test frequency based on E-UTRA operating band and test channel bandwidth as specified in Table 4.6-1. + +For Initial conditions as in clause 7.9.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.9.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +#### 7.9B.3.5 Test requirement + +Same test requirement as in clause 7.9.5 in TS 38.521-1 [8]. + +#### 7.9B.3\_1 Spurious Emissions for EN-DC within FR1 (>2 CCs) + +##### 7.9B.3\_1.1 Spurious Emissions for EN-DC within FR1 (3 CCs) + +###### 7.9B.3\_1.1.1 Test purpose + +Same test purpose as in clause 7.9B.1. + +###### 7.9B.3\_1.1.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting EN-DC within FR1 with 3CCs(1 LTE CC + 2 Inter-band NR CCs with a DL-only NR band). + +###### 7.9B.3\_1.1.3 Minimum conformance requirements + +The minimum conformance requirements are defined in clause 7.9B.0.3. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +###### 7.9B.3\_1.1.4 Test description + +Same test description as in clause 7.9.4 or 7.9.A.1.4 in TS 38.521-1 [8] with the following exceptions: + +**Table 7.9B.1.4-1: Test Configuration Table** + +| Initial Conditions | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Test Frequencies as specified in TS 38.508-1 [6] clause 4.3.1 for different DC bandwidth classes. | Mid range | +| Test EN-DC bandwidth combination as specified in Table 5.3B.1.2-1 across bandwidth combination sets supported by the UE | Highest N RB_agg (NOTE 1) | +| NOTE 1: If the UE supports multiple CC Combinations in the EN-DC Configuration with the same N RB_agg , only the combination with the highest N RB_SCG is tested. | | + +The initial test configurations for E-UTRA as specified in Table 4.6-1 except for the parameters specified in Table 7.9B.1.4-1. + +For Initial conditions as in clause 7.9.4.1 or 7.9.A.1.4.1 in TS 38.521-1 [8], the following steps are added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.6-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. +7. On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.6-1 under clause 4.6. + +Step 6 of Initial conditions as in clause 7.9.4.1 or 7.9.A.1.4.1 in TS 38.521-1 [8] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release *On* according to TS 38.508 [6] clause 4.5. + +###### 7.9B.3\_1.1.5 Test requirement + +Same test requirement as in clause 7.9.5 in TS 38.521-1 [8]. + +### 7.9B.3a Spurious Emissions for inter-band NE-DC within FR1 (2 CCs) + +No exception requirements applicable to NR or E-UTRA. + +No test case details are specified. The requirements for NR carrier(s) in this test case are tested in 7.9 and 7.9A of TS 38.521-1 [8], and the requirements for LTE carrier(s) in this test case are tested in 7.9 and 7.9A of TS 36.521-1 [10]. Neither NR carrier(s) nor LTE carrier(s) needs to be tested again. + +### 7.9B.4 Spurious Emissions for inter-band EN-DC including FR2 (1 NR CC) + +**Editor's note:** The following aspects are either missing or not yet determined: + +- The testability of this test case is pending further analysis on relaxation of the requirement for band other than n257, n258, n260 and n261. +- For n259, measurement uncertainty is TBD in the range $80\text{ GHz} < f \leq 87\text{ GHz}$ . Up to 80GHz, for n259 and PC3 this clause is complete. +- Measurement Uncertainties and Test Tolerances are FFS for power class 2, and 4. + +#### 7.9B.4.1 Test purpose + +Same test purpose as in clause 7.9.1 in TS 38.521-2 [9] for the *NR* carrier. + +#### 7.9B.4.2 Test applicability + +This test applies to all types of E-UTRA UE release 15 and forward, supporting inter-band EN-DC including FR2 with 1 NR DL CC. + +#### 7.9B.4.3 Minimum conformance requirements + +Same minimum conformance requirements as in clause 7.9.3 in TS 38.521-2 [9] for the *NR* carrier. + +No exception requirements applicable to NR or E-UTRA. LTE anchor agnostic approach is applied. + +The normative reference for this requirement is TS 38.101-3 [4] clause 7.9B.4. + +#### 7.9B.4.4 Test description + +Same test description as in clause 7.9.4 in TS 38.521-2 [9] for the *NR* carrier with the following exception: + +The initial test configurations for E-UTRA band consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA bands specified in Table 4.7-1. + +For initial conditions as in clause 7.9.4.1 in TS 38.521-2 [9], the following steps will be added to configure E-UTRA component: + +- 2.1. The parameter settings for E-UTRA cell are set up according to TS 36.508 [11] clause 4.4.3. +- 3.1. The E-UTRA downlink signal level, uplink signal level are set according to Table 4.7-1 and propagation conditions are set according to Annex B.0 of TS 36.521-1 [10]. + +Step 6 of Initial conditions as in clause 7.9.4.1 in TS 38.521-2 [9] is replaced by: + +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity EN-DC, DC bearer MCG and SCG, Connected without release On according to TS 38.508-1 [6] clause 4.5. + +Same test procedure as in clause 7.9.4.1 in TS 38.521-2 [9] with the following steps added for E-UTRA component: + +- 1.1 On the E-UTRA carrier, disable periodic and aperiodic CQI reports, disable SRS, set *TimeAlignmentTimerDedicated* IE to infinity and disable downlink and uplink scheduling, all as per Table 4.7-1 under clause 4.7. + +#### 7.9B.4.5 Test requirements + +Same test requirement as in clause 7.9.5 in TS 38.521-2 [9] for the *NR* carrier. + +### 7.9B.5 Spurious Emissions for inter-band EN-DC including both FR1 and FR2 (3 CCs) + +TBD + +# --- Annex A (normative): Measurement Channels + +Please refer to Annex A in TS 38.521-1 [8] and 38.521-2 [9] for appropriate details as needed for test cases in this test specification. EN-DC exceptions will be added. + +## --- A.1 General + +The throughput values defined in the measurement channels specified in Annex A, are calculated and are valid per datastream (codeword). For multi-stream (more than one codeword) transmissions, the throughput referenced in the minimum requirements is the sum of throughputs of all datastreams (codewords). + +The UE category entry in the definition of the reference measurement channel in Annex A is only informative and reveals the UE categories, which can support the corresponding measurement channel. Whether the measurement channel is used for testing a certain UE category or not is specified in the individual minimum requirements. + +## --- A.2 UL reference measurement channels for E-UTRA TDD Config 2 + +### A.2.1 General + +The measurement channels in the following clauses are defined to derive the requirements in clause 6 (Transmitter Characteristics) and clause 7 (Receiver Characteristics). The measurement channels represent example configurations of physical channels for different data rates. + +### A.2.2 Reference measurement channels for E-UTRA + +#### A.2.2.1 Full RB allocation + +##### A.2.2.1.1 QPSK + +**Table A.2.2.1.1-1: Reference Channels for QPSK with full RB allocation** + +| Parameter | Unit | Value | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|------|------|-------|-------|-------| +| Channel bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Uplink-Downlink Configuration (Note 2) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (Note 3) | | 7 | 7 | 7 | 7 | 7 | 7 | +| DFT-OFDM Symbols per Sub-Frame | | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Target Coding rate | | 1/3 | 1/3 | 1/3 | 1/3 | 1/5 | 1/6 | +| Payload size | | | | | | | | +| For Sub-Frame 2,7 | Bits | 600 | 1544 | 2216 | 5160 | 4392 | 4584 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks per Sub-Frame (Note 1) | | | | | | | | +| For Sub-Frame 2,7 | | 1 | 1 | 1 | 1 | 1 | 1 | +| Total number of bits per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | Bits | 1728 | 4320 | 7200 | 14400 | 21600 | 28800 | +| Total symbols per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | | 864 | 2160 | 3600 | 7200 | 10800 | 14400 | +| UE Category | | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 1 | +| Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit)
Note 2: As per Table 4.2-2 in TS 36.211 [13]
Note 3: As per Table 4.2-1 in TS 36.211 [13] | | | | | | | | + +##### A.2.2.1.2 16-QAM + +**Table A.2.2.1.2-1: Reference Channels for 16-QAM with full RB allocation** + +| Parameter | Unit | Value | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------|-------|-------|-------|-------|-------| +| Channel bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Uplink-Downlink Configuration (Note 2) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (Note 3) | | 7 | 7 | 7 | 7 | 7 | 7 | +| DFT-OFDM Symbols per Sub-Frame | | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Target Coding rate | | 3/4 | 1/2 | 1/3 | 3/4 | 1/2 | 1/3 | +| Payload size | | | | | | | | +| For Sub-Frame 2,7 | Bits | 2600 | 4264 | 4968 | 21384 | 21384 | 19848 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks per Sub-Frame (Note 1) | | | | | | | | +| For Sub-Frame 2,7 | | 1 | 1 | 1 | 4 | 4 | 4 | +| Total number of bits per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | Bits | 3456 | 8640 | 14400 | 28800 | 43200 | 57600 | +| Total symbols per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | | 864 | 2160 | 3600 | 7200 | 10800 | 14400 | +| UE Category | | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 2 | ≥ 2 | ≥ 2 | +| Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit)
Note 2: As per Table 4.2-2 in TS 36.211 [13]
Note 3: As per Table 4.2-1 in TS 36.211 [13] | | | | | | | | + +##### A.2.2.1.3 64-QAM + +**Table A.2.2.1.3-1: Reference Channels for 64-QAM with full RB allocation** + +| Parameter | Unit | Value | | | | | | +|----------------------------------------------|------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Channel bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Uplink-Downlink Configuration (Note 2) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (Note 3) | | 7 | 7 | 7 | 7 | 7 | 7 | +| DFT-OFDM Symbols per Sub-Frame | | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| Target Coding rate | | 3/4 | 3/4 | 3/4 | 3/4 | 3/4 | 3/4 | +| Payload size | | | | | | | | +| For Sub-Frame 2,7 | Bits | 3752 | 9528 | 15840 | 31704 | 46888 | 63776 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks per Sub-Frame (Note 1) | | | | | | | | +| For Sub-Frame 2,7 | | 1 | 2 | 3 | 6 | 8 | 11 | +| Total number of bits per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | Bits | 5184 | 12960 | 21600 | 43200 | 64800 | 86400 | +| Total symbols per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | | 864 | 2160 | 3600 | 7200 | 10800 | 14400 | +| UE Category (Note 4) | | 5, 8 | 5, 8 | 5, 8 | 5, 8 | 5, 8 | 5, 8 | +| UE UL Category (Note 4) | | 5, 8,
13, 14 | 5, 8,
13, 14 | 5, 8,
13, 14 | 5, 8,
13, 14 | 5, 8,
13, 14 | 5, 8,
13, 14 | + +Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) + +Note 2: As per Table 4.2-2 in TS 36.211 [13] + +Note 3: As per Table 4.2-1 in TS 36.211 [13] + +Note 4: If UE does not report UE UL category, then the applicability of reference channel is determined by UE category. If UE reports UE UL category, then the applicability of reference channel is determined by UE UL category. + +##### A.2.2.1.4 256 QAM + +**Table A.2.2.1.4-1: Reference Channels for 256 QAM with full RB allocation** + +| Parameter | Unit | Value | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|--------|--------|--------|--------|--------| +| | | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Channel bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Uplink-Downlink Configuration (Note 2) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (Note 3) | | 7 | 7 | 7 | 7 | 7 | 7 | +| DFT-OFDM Symbols per Sub-Frame | | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | +| Target Coding rate | | 3/4 | 3/4 | 3/4 | 3/4 | 3/4 | 3/4 | +| Payload size | | | | | | | | +| For Sub-Frame 2,7 | Bits | 5160 | 12960 | 21384 | 42368 | 63776 | 84760 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks per Sub-Frame (Note 1) | | | | | | | | +| For Sub-Frame 2,7 | | 1 | 3 | 4 | 8 | 11 | 15 | +| Total number of bits per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | Bits | 6912 | 17280 | 28800 | 57600 | 86400 | 115200 | +| Total symbols per Sub-Frame | | | | | | | | +| For Sub-Frame 2,7 | | 864 | 2160 | 3600 | 7200 | 10800 | | +| UE UL Category | | ≥ 15 | ≥ 15 | ≥ 15 | ≥ 15 | ≥ 15 | ≥ 15 | +| Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit)
Note 2: As per Table 4.2-2 in TS 36.211 [13]
Note 3: As per Table 4.2-1 in TS 36.211 [13] | | | | | | | | + +#### A.2.2.2 Partial RB allocation + +##### A.2.2.2.1 QPSK + +Table A.2.2.2.1-1: Reference Channels for QPSK with partial RB allocation + +| Parameter | Ch BW | Allocated RBs | UL-DL Configuration (Note 2) | Special subframe configuration (Note 3) | DFT-OFDM Symbols per Subframe | Mod'n | Target Coding rate | Payload size for Subframe 2, 7 | Transport block CRC | Number of code blocks per Subframe (Note 1) | Total number of bits per Subframe for Subframe 2, 7 | Total symbols per Subframe for Subframe 2, 7 | UE Category | +|-----------|----------|---------------|------------------------------|-----------------------------------------|-------------------------------|-------|--------------------|--------------------------------|---------------------|---------------------------------------------|-----------------------------------------------------|----------------------------------------------|-------------| +| Unit | MHz | | | | | | | Bits | Bits | | Bits | | | +| | 1.4 - 20 | 1 | 2 | 7 | 12 | QPSK | 1/3 | 72 | 24 | 1 | 288 | 144 | ≥ 1 | +| | 1.4 - 20 | 2 | 2 | 7 | 12 | QPSK | 1/3 | 176 | 24 | 1 | 576 | 288 | ≥ 1 | +| | 1.4 - 20 | 3 | 2 | 7 | 12 | QPSK | 1/3 | 256 | 24 | 1 | 864 | 432 | ≥ 1 | +| | 1.4 - 20 | 4 | 2 | 7 | 12 | QPSK | 1/3 | 392 | 24 | 1 | 1152 | 576 | ≥ 1 | +| | 1.4 - 20 | 5 | 2 | 7 | 12 | QPSK | 1/3 | 424 | 24 | 1 | 1440 | 720 | ≥ 1 | +| | 3-20 | 6 | 2 | 7 | 12 | QPSK | 1/3 | 600 | 24 | 1 | 1728 | 864 | ≥ 1 | +| | 3-20 | 8 | 2 | 7 | 12 | QPSK | 1/3 | 808 | 24 | 1 | 2304 | 1152 | ≥ 1 | +| | 3-20 | 9 | 2 | 7 | 12 | QPSK | 1/3 | 776 | 24 | 1 | 2592 | 1296 | ≥ 1 | +| | 3-20 | 10 | 2 | 7 | 12 | QPSK | 1/3 | 872 | 24 | 1 | 2880 | 1440 | ≥ 1 | +| | 3-20 | 12 | 2 | 7 | 12 | QPSK | 1/3 | 1224 | 24 | 1 | 3456 | 1728 | ≥ 1 | +| | 5-20 | 15 | 2 | 7 | 12 | QPSK | 1/3 | 1320 | 24 | 1 | 4320 | 2160 | ≥ 1 | +| | 5-20 | 16 | 2 | 7 | 12 | QPSK | 1/3 | 1384 | 24 | 1 | 4608 | 2304 | ≥ 1 | +| | 5-20 | 18 | 2 | 7 | 12 | QPSK | 1/3 | 1864 | 24 | 1 | 5184 | 2592 | ≥ 1 | +| | 5-20 | 20 | 2 | 7 | 12 | QPSK | 1/3 | 1736 | 24 | 1 | 5760 | 2880 | ≥ 1 | +| | 5-20 | 24 | 2 | 7 | 12 | QPSK | 1/3 | 2472 | 24 | 1 | 6912 | 3456 | ≥ 1 | +| | 10-20 | 25 | 2 | 7 | 12 | QPSK | 1/3 | 2216 | 24 | 1 | 7200 | 3600 | ≥ 1 | +| | 10-20 | 27 | 2 | 7 | 12 | QPSK | 1/3 | 2792 | 24 | 1 | 7776 | 3888 | ≥ 1 | +| | 10-20 | 30 | 2 | 7 | 12 | QPSK | 1/3 | 2664 | 24 | 1 | 8640 | 4320 | ≥ 1 | +| | 10-20 | 32 | 2 | 7 | 12 | QPSK | 1/3 | 2792 | 24 | 1 | 9216 | 4608 | ≥ 1 | +| | 10-20 | 36 | 2 | 7 | 12 | QPSK | 1/3 | 3752 | 24 | 1 | 10368 | 5184 | ≥ 1 | +| | 10-20 | 40 | 2 | 7 | 12 | QPSK | 1/3 | 4136 | 24 | 1 | 11520 | 5760 | ≥ 1 | +| | 10-20 | 45 | 2 | 7 | 12 | QPSK | 1/3 | 4008 | 24 | 1 | 12960 | 6480 | ≥ 1 | +| | 10-20 | 48 | 2 | 7 | 12 | QPSK | 1/3 | 4264 | 24 | 1 | 13824 | 6912 | ≥ 1 | +| | 15 - 20 | 50 | 2 | 7 | 12 | QPSK | 1/3 | 5160 | 24 | 1 | 14400 | 7200 | ≥ 1 | +| | 15 - 20 | 54 | 2 | 7 | 12 | QPSK | 1/3 | 4776 | 24 | 1 | 15552 | 7776 | ≥ 1 | +| | 15 - 20 | 60 | 2 | 7 | 12 | QPSK | 1/4 | 4264 | 24 | 1 | 17280 | 8640 | ≥ 1 | +| | 15 - 20 | 64 | 2 | 7 | 12 | QPSK | 1/4 | 4584 | 24 | 1 | 18432 | 9216 | ≥ 1 | +| | 15 - 20 | 72 | 2 | 7 | 12 | QPSK | 1/4 | 5160 | 24 | 1 | 20736 | 10368 | ≥ 1 | +| | 20 | 75 | 2 | 7 | 12 | QPSK | 1/5 | 4392 | 24 | 1 | 21600 | 10800 | ≥ 1 | +| | 20 | 80 | 2 | 7 | 12 | QPSK | 1/5 | 4776 | 24 | 1 | 23040 | 11520 | ≥ 1 | +| | 20 | 81 | 2 | 7 | 12 | QPSK | 1/5 | 4776 | 24 | 1 | 23328 | 11664 | ≥ 1 | +| | 20 | 90 | 2 | 7 | 12 | QPSK | 1/6 | 4008 | 24 | 1 | 25920 | 12960 | ≥ 1 | +| | 20 | 96 | 2 | 7 | 12 | QPSK | 1/6 | 4264 | 24 | 1 | 27648 | 13824 | ≥ 1 | + +Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) + +Note 2: As per Table 4.2-2 in TS 36.211 [13] + +Note 3: As per Table 4.2-1 in TS 36.211 [13] + + + +##### A.2.2.2.2 16-QAM + +**Table A.2.2.2.2-1: Reference Channels for 16QAM with partial RB allocation** + +| Parameter | Ch BW | Allocated RBs | UL-DL Configuration (Note 2) | Special subframe configuration (Note 3) | DFT-OFDM Symbols per Sub-Frame | Mod'n | Target Coding rate | Payload size for Sub-Frame 2, 7 | Transport block CRC | Number of code blocks per Sub-Frame (Note 1) | Total number of bits per Sub-Frame for Sub-Frame 2, 7 | Total symbols per Sub-Frame for Sub-Frame 2, 7 | UE Category | +|-----------|----------|---------------|------------------------------|-----------------------------------------|--------------------------------|-------|--------------------|---------------------------------|---------------------|----------------------------------------------|-------------------------------------------------------|------------------------------------------------|-------------| +| Unit | MHz | | | | | | | Bits | Bits | | Bits | | | +| | 1.4 - 20 | 1 | 2 | 7 | 12 | 16QAM | 3/4 | 408 | 24 | 1 | 576 | 144 | ≥ 1 | +| | 1.4 - 20 | 2 | 2 | 7 | 12 | 16QAM | 3/4 | 840 | 24 | 1 | 1152 | 288 | ≥ 1 | +| | 1.4 - 20 | 3 | 2 | 7 | 12 | 16QAM | 3/4 | 1288 | 24 | 1 | 1728 | 432 | ≥ 1 | +| | 1.4 - 20 | 4 | 2 | 7 | 12 | 16QAM | 3/4 | 1736 | 24 | 1 | 2304 | 576 | ≥ 1 | +| | 1.4 - 20 | 5 | 2 | 7 | 12 | 16QAM | 3/4 | 2152 | 24 | 1 | 2880 | 720 | ≥ 1 | +| | 3-20 | 6 | 2 | 7 | 12 | 16QAM | 3/4 | 2600 | 24 | 1 | 3456 | 864 | ≥ 1 | +| | 3-20 | 8 | 2 | 7 | 12 | 16QAM | 3/4 | 3496 | 24 | 1 | 4608 | 1152 | ≥ 1 | +| | 3-20 | 9 | 2 | 7 | 12 | 16QAM | 3/4 | 3880 | 24 | 1 | 5184 | 1296 | ≥ 1 | +| | 3-20 | 10 | 2 | 7 | 12 | 16QAM | 3/4 | 4264 | 24 | 1 | 5760 | 1440 | ≥ 1 | +| | 3-20 | 12 | 2 | 7 | 12 | 16QAM | 3/4 | 5160 | 24 | 1 | 6912 | 1728 | ≥ 1 | +| | 5-20 | 15 | 2 | 7 | 12 | 16QAM | 1/2 | 4264 | 24 | 1 | 8640 | 2160 | ≥ 1 | +| | 5-20 | 16 | 2 | 7 | 12 | 16QAM | 1/2 | 4584 | 24 | 1 | 9216 | 2304 | ≥ 1 | +| | 5-20 | 18 | 2 | 7 | 12 | 16QAM | 1/2 | 5160 | 24 | 1 | 10368 | 2592 | ≥ 1 | +| | 5-20 | 20 | 2 | 7 | 12 | 16QAM | 1/3 | 4008 | 24 | 1 | 11520 | 2880 | ≥ 1 | +| | 5-20 | 24 | 2 | 7 | 12 | 16QAM | 1/3 | 4776 | 24 | 1 | 13824 | 3456 | ≥ 1 | +| | 10-20 | 25 | 2 | 7 | 12 | 16QAM | 1/3 | 4968 | 24 | 1 | 14400 | 3600 | ≥ 1 | +| | 10-20 | 27 | 2 | 7 | 12 | 16QAM | 1/3 | 4776 | 24 | 1 | 15552 | 3888 | ≥ 1 | +| | 10-20 | 30 | 2 | 7 | 12 | 16QAM | 3/4 | 12960 | 24 | 3 | 17280 | 4320 | ≥ 2 | +| | 10-20 | 32 | 2 | 7 | 12 | 16QAM | 3/4 | 13536 | 24 | 3 | 18432 | 4608 | ≥ 2 | +| | 10-20 | 36 | 2 | 7 | 12 | 16QAM | 3/4 | 15264 | 24 | 3 | 20736 | 5184 | ≥ 2 | +| | 10-20 | 40 | 2 | 7 | 12 | 16QAM | 3/4 | 16992 | 24 | 3 | 23040 | 5760 | ≥ 2 | +| | 10-20 | 45 | 2 | 7 | 12 | 16QAM | 3/4 | 19080 | 24 | 4 | 25920 | 6480 | ≥ 2 | +| | 10-20 | 48 | 2 | 7 | 12 | 16QAM | 3/4 | 20616 | 24 | 4 | 27648 | 6912 | ≥ 2 | +| | 15 - 20 | 50 | 2 | 7 | 12 | 16QAM | 3/4 | 21384 | 24 | 4 | 28800 | 7200 | ≥ 2 | +| | 15 - 20 | 54 | 2 | 7 | 12 | 16QAM | 3/4 | 22920 | 24 | 4 | 31104 | 7776 | ≥ 2 | +| | 15 - 20 | 60 | 2 | 7 | 12 | 16QAM | 2/3 | 23688 | 24 | 4 | 34560 | 8640 | ≥ 2 | +| | 15 - 20 | 64 | 2 | 7 | 12 | 16QAM | 2/3 | 25456 | 24 | 4 | 36864 | 9216 | ≥ 2 | + +| | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----|---|---|----|-----------|-----|-------|----|---|-------|-------|-----| +| | 15 - 20 | 72 | 2 | 7 | 12 | 16QA
M | 1/2 | 20616 | 24 | 4 | 41472 | 10368 | ≥ 2 | +| | 20 | 75 | 2 | 7 | 12 | 16QA
M | 1/2 | 21384 | 24 | 4 | 43200 | 10800 | ≥ 2 | +| | 20 | 80 | 2 | 7 | 12 | 16QA
M | 1/2 | 22920 | 24 | 4 | 46080 | 11520 | ≥ 2 | +| | 20 | 81 | 2 | 7 | 12 | 16QA
M | 1/2 | 22920 | 24 | 4 | 46656 | 11664 | ≥ 2 | +| | 20 | 90 | 2 | 7 | 12 | 16QA
M | 2/5 | 20616 | 24 | 4 | 51840 | 12960 | ≥ 2 | +| | 20 | 96 | 2 | 7 | 12 | 16QA
M | 2/5 | 22152 | 24 | 4 | 55296 | 13824 | ≥ 2 | +| Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit)
Note 2: As per Table 4.2-2 in TS 36.211 [13]
Note 3: As per Table 4.2-1 in TS 36.211 [13] | | | | | | | | | | | | | | + +##### A.2.2.2.3 64-QAM + +**Table A.2.2.2.3-1: Reference Channels for 64-QAM with partial RB allocation** + +| Parameter | C
h
B
W | Allocated RBs | UL-DL Configuration (Note 2) | Special subframe configuration (Note 3) | DFT-OFDM Symbols per Sub-Frame | Mod'n | Target Coding rate | Payload size for Sub-Frame 2, 7 | Transport block CRC | Number of code blocks per Sub-Frame (Note 1) | Total number of bits per Sub-Frame for Sub 2, 7 | Total symbols per Sub-Frame for Sub-Frame 2, 7 | UE Category (Note 4) | UE UL Category (Note 4) | +|-----------|------------------|---------------|------------------------------|-----------------------------------------|--------------------------------|-------|--------------------|---------------------------------|---------------------|----------------------------------------------|-------------------------------------------------|------------------------------------------------|----------------------|-------------------------| +| Unit | M
H
Z | | | | | | | Bits | Bits | | Bits | | | | +| | 1.4 - 20 | 1 | 2 | 7 | 12 | 64QAM | 3/4 | 616 | 24 | 1 | 864 | 144 | 5,8 | 5, 8, 13, 14 | +| | 1.4 - 20 | 2 | 2 | 7 | 12 | 64QAM | 3/4 | 1256 | 24 | 1 | 1728 | 288 | 5,8 | 5, 8, 13, 14 | +| | 1.4 - 20 | 3 | 2 | 7 | 12 | 64QAM | 3/4 | 1864 | 24 | 1 | 2592 | 432 | 5,8 | 5, 8, 13, 14 | +| | 1.4 - 20 | 4 | 2 | 7 | 12 | 64QAM | 3/4 | 2536 | 24 | 1 | 3456 | 576 | 5,8 | 5, 8, 13, 14 | +| | 1.4 - 20 | 5 | 2 | 7 | 12 | 64QAM | 3/4 | 3112 | 24 | 1 | 4320 | 720 | 5,8 | 5, 8, 13, 14 | +| | 3-20 | 6 | 2 | 7 | 12 | 64QAM | 3/4 | 3752 | 24 | 1 | 5184 | 864 | 5,8 | 5, 8, 13, 14 | +| | 3-20 | 8 | 2 | 7 | 12 | 64QAM | 3/4 | 5160 | 24 | 1 | 6912 | 1152 | 5,8 | 5, 8, 13, 14 | +| | 3-20 | 9 | 2 | 7 | 12 | 64QAM | 3/4 | 5736 | 24 | 1 | 7776 | 1296 | 5,8 | 5, 8, 13, 14 | +| | 3-20 | 10 | 2 | 7 | 12 | 64QAM | 3/4 | 6200 | 24 | 2 | 8640 | 1440 | 5,8 | 5, 8, 13, 14 | +| | 3-20 | 12 | 2 | 7 | 12 | 64QAM | 3/4 | 7480 | 24 | 2 | 10368 | 1728 | 5,8 | 5, 8, 13, 14 | +| | 5-20 | 15 | 2 | 7 | 12 | 64QAM | 3/4 | 9528 | 24 | 2 | 12960 | 2160 | 5,8 | 5, 8, 13, 14 | +| | 5-20 | 16 | 2 | 7 | 12 | 64QAM | 3/4 | 10296 | 24 | 2 | 13824 | 2304 | 5,8 | 5, 8, 13, 14 | +| | 5-20 | 18 | 2 | 7 | 12 | 64QAM | 3/4 | 11448 | 24 | 2 | 15552 | 2592 | 5,8 | 5, 8, 13, 14 | +| | 5-20 | 20 | 2 | 7 | 12 | 64QAM | 3/4 | 12576 | 24 | 3 | 17280 | 2880 | 5,8 | 5, 8, 13, 14 | + +| | | | | | | | | | | | | | | | +|--|-------|----|---|---|----|--------|-----|--------|----|----|--------|-------|-----|--------------| +| | 5-20 | 24 | 2 | 7 | 12 | 64Q AM | 3/4 | 152 64 | 24 | 3 | 207 36 | 3456 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 25 | 2 | 7 | 12 | 64Q AM | 3/4 | 158 40 | 24 | 3 | 216 00 | 3600 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 27 | 2 | 7 | 12 | 64Q AM | 3/4 | 169 92 | 24 | 3 | 233 28 | 3888 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 30 | 2 | 7 | 12 | 64Q AM | 3/4 | 190 80 | 24 | 4 | 259 20 | 4320 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 32 | 2 | 7 | 12 | 64Q AM | 3/4 | 206 16 | 24 | 4 | 276 48 | 4608 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 36 | 2 | 7 | 12 | 64Q AM | 3/4 | 229 20 | 24 | 4 | 311 04 | 5184 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 40 | 2 | 7 | 12 | 64Q AM | 3/4 | 254 56 | 24 | 5 | 345 60 | 5760 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 45 | 2 | 7 | 12 | 64Q AM | 3/4 | 283 36 | 24 | 5 | 388 80 | 6480 | 5,8 | 5, 8, 13, 14 | +| | 10-20 | 48 | 2 | 7 | 12 | 64Q AM | 3/4 | 305 76 | 24 | 5 | 414 72 | 6912 | 5,8 | 5, 8, 13, 14 | +| | 15-20 | 50 | 2 | 7 | 12 | 64Q AM | 3/4 | 317 04 | 24 | 6 | 432 00 | 7200 | 5,8 | 5, 8, 13, 14 | +| | 15-20 | 54 | 2 | 7 | 12 | 64Q AM | 3/4 | 340 08 | 24 | 6 | 466 56 | 7776 | 5,8 | 5, 8, 13, 14 | +| | 15-20 | 60 | 2 | 7 | 12 | 64Q AM | 3/4 | 378 88 | 24 | 7 | 518 40 | 8640 | 5,8 | 5, 8, 13, 14 | +| | 15-20 | 64 | 2 | 7 | 12 | 64Q AM | 3/4 | 405 76 | 24 | 7 | 552 96 | 9216 | 5,8 | 5, 8, 13, 14 | +| | 15-20 | 72 | 2 | 7 | 12 | 64Q AM | 3/4 | 453 52 | 24 | 8 | 622 08 | 10368 | 5,8 | 5, 8, 13, 14 | +| | 20 | 75 | 2 | 7 | 12 | 64Q AM | 3/4 | 468 88 | 24 | 8 | 648 00 | 10800 | 5,8 | 5, 8, 13, 14 | +| | 20 | 80 | 2 | 7 | 12 | 64Q AM | 3/4 | 510 24 | 24 | 9 | 691 20 | 11520 | 5,8 | 5, 8, 13, 14 | +| | 20 | 81 | 2 | 7 | 12 | 64Q AM | 3/4 | 510 24 | 24 | 9 | 699 84 | 11664 | 5,8 | 5, 8, 13, 14 | +| | 20 | 90 | 2 | 7 | 12 | 64Q AM | 3/4 | 510 24 | 24 | 9 | 777 60 | 12960 | 5,8 | 5, 8, 13, 14 | +| | 20 | 96 | 2 | 7 | 12 | 64Q AM | 3/4 | 616 64 | 24 | 11 | 829 44 | 13824 | 5,8 | 5, 8, 13, 14 | + +Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) + +Note 2: As per Table 4.2-2 in TS 36.211 [13] + +Note 3: As per Table 4.2-1 in TS 36.211 [13] + +Note 4: If UE does not report UE UL category, then the applicability of reference channel is determined by UE category. If UE reports UE UL category, then the applicability of reference channel is determined by UE UL category + +##### A.2.2.2.4 256 QAM + +Table A.2.2.2.4-1: Reference Channels for 256 QAM with partial RB allocation + +| Parameter | Ch BW | Allocated RBs | UL-DL Configuration (Note 2) | Special Slot Configuration (Note 3) | DFT-OFDM Symbols per Sub-Frame | Mod'n | Target Coding rate | Payload size for Sub-Frame 2, 7 | Trans-port block CRC | Number of code blocks per Sub-Frame (Note 1) | Total number of bits per Sub-Frame for Sub-Frame 2, 7 | Total symbols per Sub-Frame for Sub-Frame 2, 7 | UE UL Category | +|-----------|----------|---------------|------------------------------|-------------------------------------|--------------------------------|--------|--------------------|---------------------------------|----------------------|----------------------------------------------|-------------------------------------------------------|------------------------------------------------|----------------| +| Unit | MHz | | | | | | | Bits | Bits | | Bits | | | +| | 1.4 - 20 | 1 | 2 | 7 | 12 | 256QAM | 3/4 | 840 | 24 | 1 | 1152 | 144 | ≥ 15 | +| | 1.4 - 20 | 2 | 2 | 7 | 12 | 256QAM | 3/4 | 1672 | 24 | 1 | 2304 | 288 | ≥ 15 | +| | 1.4 - 20 | 3 | 2 | 7 | 12 | 256QAM | 3/4 | 2536 | 24 | 1 | 3456 | 432 | ≥ 15 | +| | 1.4 - 20 | 4 | 2 | 7 | 12 | 256QAM | 3/4 | 3368 | 24 | 1 | 4608 | 576 | ≥ 15 | +| | 1.4 - 20 | 5 | 2 | 7 | 12 | 256QAM | 3/4 | 4264 | 24 | 1 | 5760 | 720 | ≥ 15 | +| | 3-20 | 6 | 2 | 7 | 12 | 256QAM | 3/4 | 5160 | 24 | 1 | 6912 | 864 | ≥ 15 | +| | 3-20 | 8 | 2 | 7 | 12 | 256QAM | 3/4 | 6712 | 24 | 2 | 9216 | 1152 | ≥ 15 | +| | 3-20 | 9 | 2 | 7 | 12 | 256QAM | 3/4 | 7736 | 24 | 2 | 10368 | 1296 | ≥ 15 | +| | 3-20 | 10 | 2 | 7 | 12 | 256QAM | 3/4 | 8504 | 24 | 2 | 11520 | 1440 | ≥ 15 | +| | 3-20 | 12 | 2 | 7 | 12 | 256QAM | 3/4 | 10296 | 24 | 2 | 13824 | 1728 | ≥ 15 | +| | 5-20 | 15 | 2 | 7 | 12 | 256QAM | 3/4 | 12960 | 24 | 3 | 17280 | 2160 | ≥ 15 | +| | 5-20 | 16 | 2 | 7 | 12 | 256QAM | 3/4 | 13536 | 24 | 3 | 18432 | 2304 | ≥ 15 | +| | 5-20 | 18 | 2 | 7 | 12 | 256QAM | 3/4 | 15264 | 24 | 3 | 20736 | 2592 | ≥ 15 | +| | 5-20 | 20 | 2 | 7 | 12 | 256QAM | 3/4 | 16992 | 24 | 3 | 23040 | 2880 | ≥ 15 | +| | 5-20 | 24 | 2 | 7 | 12 | 256QAM | 3/4 | 20616 | 24 | 4 | 27648 | 3456 | ≥ 15 | +| | 10-20 | 25 | 2 | 7 | 12 | 256QAM | 3/4 | 21384 | 24 | 4 | 28800 | 3600 | ≥ 15 | +| | 10-20 | 27 | 2 | 7 | 12 | 256QAM | 3/4 | 22920 | 24 | 4 | 31104 | 3888 | ≥ 15 | +| | 10-20 | 30 | 2 | 7 | 12 | 256QAM | 3/4 | 25456 | 24 | 5 | 34560 | 4320 | ≥ 15 | +| | 10-20 | 32 | 2 | 7 | 12 | 256QAM | 3/4 | 27376 | 24 | 5 | 36864 | 4608 | ≥ 15 | +| | 10-20 | 36 | 2 | 7 | 12 | 256QAM | 3/4 | 30576 | 24 | 6 | 41472 | 5184 | ≥ 15 | +| | 10-20 | 40 | 2 | 7 | 12 | 256QAM | 3/4 | 34008 | 24 | 6 | 46080 | 5760 | ≥ 15 | +| | 10-20 | 45 | 2 | 7 | 12 | 256QAM | 3/4 | 37888 | 24 | 7 | 51840 | 6480 | ≥ 15 | +| | 10-20 | 48 | 2 | 7 | 12 | 256QAM | 3/4 | 40576 | 24 | 8 | 55296 | 6912 | ≥ 15 | +| | 15 - 20 | 50 | 2 | 7 | 12 | 256QAM | 3/4 | 42368 | 24 | 8 | 57600 | 7200 | ≥ 15 | +| | 15 - 20 | 54 | 2 | 7 | 12 | 256QAM | 3/4 | 46888 | 24 | 8 | 62208 | 7776 | ≥ 15 | +| | 15 - 20 | 60 | 2 | 7 | 12 | 256QAM | 3/4 | 51024 | 24 | 9 | 69120 | 8640 | ≥ 15 | +| | 15 - 20 | 64 | 2 | 7 | 12 | 256QAM | 3/4 | 55056 | 24 | 9 | 73728 | 9216 | ≥ 15 | +| | 15 - 20 | 72 | 2 | 7 | 12 | 256QAM | 3/4 | 61664 | 24 | 11 | 82944 | 10368 | ≥ 15 | +| | 20 | 75 | 2 | 7 | 12 | 256QAM | 3/4 | 63776 | 24 | 11 | 86400 | 10800 | ≥ 15 | +| | 20 | 80 | 2 | 7 | 12 | 256QAM | 3/4 | 68808 | 24 | 12 | 92160 | 11520 | ≥ 15 | +| | 20 | 81 | 2 | 7 | 12 | 256QAM | 3/4 | 68808 | 24 | 12 | 93312 | 11664 | ≥ 15 | +| | 20 | 90 | 2 | 7 | 12 | 256QAM | 3/4 | 76208 | 24 | 13 | 103680 | 12960 | ≥ 15 | +| | 20 | 96 | 2 | 7 | 12 | 256QAM | 3/4 | 81176 | 24 | 14 | 110592 | 13824 | ≥ 15 | + +Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) + +Note 2: As per Table 4.2-2 in TS 36.211 [13] + +Note 3: As per Table 4.2-1 in TS 36.211 [13] + +## A.3 DL reference measurement channels for E-UTRA + +### A.3.1 General + +The number of available channel bits varies across the sub-frames due to PBCH and PSS/SSS overhead. The payload size per sub-frame is varied in order to keep the code rate constant throughout a frame. + +Unless otherwise stated, no user data is scheduled on subframes #5 in order to facilitate the transmission of system information blocks (SIB). + +The algorithm for determining the payload size $A$ is as follows; given a desired coding rate $R$ and radio block allocation $N_{RB}$ + +1. Calculate the number of channel bits $N_{ch}$ that can be transmitted during the first transmission of a given sub-frame. +2. Find $A$ such that the resulting coding rate is as close to $R$ as possible, that is, + +$$\min |R - (A + 24 * (N_{CB} + 1)) / N_{ch}|, \text{ where } N_{CB} = \begin{cases} 0, \text{ if } C = 1 \\ C, \text{ if } C > 1 \end{cases},$$ + +subject to + +- a) $A$ is a valid TB size according to clause 7.1.7 of TS 36.213 [6] assuming an allocation of $N_{RB}$ resource blocks. + - b) $C$ is the number of Code Blocks calculated according to clause 5.1.2 of TS 36.212 [5]. +3. If there is more than one $A$ that minimizes the equation above, then the larger value is chosen per default and the chosen code rate should not exceed 0.93. + 4. For TDD, the measurement channel is based on DL/UL configuration ratio of 3DL+DwPTS (10 OFDM symbol SSF7): 1UL. + +**Table A.3.1-1: PUCCH-ConfigDedicated-v1020-DEFAULT: Additional Configuration for LTE TDD 1CC** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.6.3-9A: PUCCH-ConfigDedicated-v1020-DEFAULT | | | | +|------------------------------------------------------------------------------------------------|--------------|---------|---------------------| +| Information Element | Value/remark | Comment | Condition | +| PUCCH-ConfigDedicated-v1020 ::= SEQUENCE { | | | | +| pucch-Format-r10 CHOICE { | | | UL_RB_all ocation=0 | +| channelSelection-r10 SEQUENCE { | | | | +| n1PUCCH-AN-CS-r10 CHOICE { | | | | +| setup SEQUENCE { | | | | +| n1PUCCH-AN-CS-List-r10 SEQUENCE{ | 2 | | | +| N1PUCCH-AN-CS-r10 | 4 | | | +| | 101 | | | +| | 102 | | | +| | 103 | | | +| | 104 | | | +| N1PUCCH-AN-CS-r10 | 4 | | | +| | 105 | | | +| | 106 | | | +| | 107 | | | +| | 108 | | | +| } | | | | +| } | | | | +| } | | | | +| } | | | | +| } | | | | + +| Condition | Explanation | +|--------------------|---------------------------------------------------------| +| UL_RB_allocation=0 | TC is tested with no or N/A UL RB allocation (no PUSCH) | + +**Table A.3.1-2: RadioResourceConfigCommonSIB-DEFAULT: Additional Configuration for LTE TDD 1CC** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.6.3-14: RadioResourceConfigCommonSIB-DEFAULT | | | | +|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---------------|--------------------| +| Information Element | Value/remark | Comment | Condition | +| RadioResourceConfigCommonSIB-DEFAULT ::=
SEQUENCE { | | | | +| uplinkPowerControlCommon-v1020 | UplinkPowerControlCommon-v1020-DEFAULT:
Additional Configuration
for LTE TDD 1CC | Table A.3.1-3 | UL_RB_allocation=0 | +| } | | | | + +| Condition | Explanation | +|--------------------|---------------------------------------------------------| +| UL_RB_allocation=0 | TC is tested with no or N/A UL RB allocation (no PUSCH) | + +**Table A.3.1-3: UplinkPowerControlCommon-v1020-DEFAULT: Additional Configuration for LTE TDD 1CC** + +| Derivation Path: 36.508 [11] clause 4.6.3, Table 4.6.3-25AA: UplinkPowerControlCommon-v1020-DEFAULT | | | | +|-----------------------------------------------------------------------------------------------------|--------------|---------|--------------------| +| Information Element | Value/remark | Comment | Condition | +| UplinkPowerControlCommon-v1020-DEFAULT ::=
SEQUENCE { | | | UL_RB_allocation=0 | +| deltaF-PUCCH-Format1bCS-r10 | deltaF1 | | | +| } | | | | + +| Condition | Explanation | +|--------------------|---------------------------------------------------------| +| UL_RB_allocation=0 | TC is tested with no or N/A UL RB allocation (no PUSCH) | + +#### A.3.1.1 QPSK + +**Table A.3.1.1-1: Fixed Reference Channel for Receiver Requirements (TDD)** + +| Parameter | Unit | Value | | | | | | +|----------------------------------------------|-----------|-------|------|------|--------|--------|--------| +| | | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Channel Bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Uplink-Downlink Configuration (NOTE 5) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (NOTE 6) | | 7 | 7 | 7 | 7 | 7 | 7 | +| Allocated subframes per Radio Frame (D+S) | | 3 | 3+2 | 3+2 | 3+2 | 3+2 | 3+2 | +| Number of HARQ Processes | Processes | 7 | 7 | 7 | 7 | 7 | 7 | +| Maximum number of HARQ transmission | | 1 | 1 | 1 | 1 | 1 | 1 | +| Modulation | | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Target coding rate | | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | +| Information Bit Payload per Sub-Frame | Bits | | | | | | | +| For Sub-Frame 3, 4, 8, 9 | | 408 | 1320 | 2216 | 4392 | 6712 | 8760 | +| For Sub-Frame 1, 6 | | N/A | 776 | 1288 | 2664 | 4008 | 5352 | +| For Sub-Frame 5 | | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | | 208 | 1064 | 1800 | 4392 | 6712 | 8760 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of Code Blocks per Sub-Frame (NOTE 4) | | | | | | | | +| For Sub-Frame 3, 4, 8, 9 | | 1 | 1 | 1 | 1 | 2 | 2 | +| For Sub-Frame 1, 6 | | N/A | 1 | 1 | 1 | 1 | 1 | +| For Sub-Frame 5 | | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | | 1 | 1 | 1 | 1 | 2 | 2 | +| Binary Channel Bits Per Sub-Frame | Bits | | | | | | | +| For Sub-Frame 3, 4, 8, 9 | | 1368 | 3780 | 6300 | 13800 | 20700 | 27600 | +| For Sub-Frame 1, 6 | | N/A | 2616 | 4456 | 9056 | 13656 | 18256 | +| For Sub-Frame 5 | | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | | 672 | 3084 | 5604 | 13104 | 20004 | 26904 | +| Max. Throughput averaged over 1 frame | kbps | 102.4 | 564 | 932 | 1965.6 | 3007.2 | 3970.4 | +| UE Category | | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 1 | ≥ 1 | + +- NOTE 1: For normal subframes(0,3,4,5,8,9), 2 symbols allocated to PDCCH for 20 MHz, 15 MHz and 10 MHz channel BW; 3 symbols allocated to PDCCH for 5 MHz and 3 MHz; 4 symbols allocated to PDCCH for 1.4 MHz. For special subframe (1&6), only 2 OFDM symbols are allocated to PDCCH for all BWs. +- NOTE 2: For 1.4MHz, no data shall be scheduled on special subframes(1&6) to avoid problems with insufficient PDCCH performance +- NOTE 3: Reference signal, Synchronization signals and PBCH allocated as per TS 36.211 [7] +- NOTE 4: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +- NOTE 5: As per Table 4.2-2 in TS 36.211 [7] +- NOTE 6: As per Table 4.2-1 in TS 36.211 [7] + +#### A.3.1.2 64-QAM + +**Table A.3.1.2-1: Fixed Reference Channel for Maximum input level for UE Categories $\geq 3$ (TDD)** + +| Parameter | Unit | Value | | | | | | +|----------------------------------------------|-----------|---------------|---------------|---------------|---------------|---------------|---------------| +| Channel bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | 12 | 12 | +| Uplink-Downlink Configuration (NOTE 5) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (NOTE 6) | | 7 | 7 | 7 | 7 | 7 | 7 | +| Allocated subframes per Radio Frame | | 2 | 3+2 | 3+2 | 3+2 | 3+2 | 3+2 | +| Modulation | | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| Target Coding Rate | | $\frac{3}{4}$ | $\frac{3}{4}$ | $\frac{3}{4}$ | $\frac{3}{4}$ | $\frac{3}{4}$ | $\frac{3}{4}$ | +| Number of HARQ Processes | Processes | 7 | 7 | 7 | 7 | 7 | 7 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | 1 | 1 | +| Information Bit Payload per Sub-Frame | | | | | | | | +| For Sub-Frames 3, 4, 8, 9 | Bits | 2984 | 8504 | 14112 | 30576 | 46888 | 61664 | +| For Sub-Frames 1,6 | Bits | N/A | 5544 | 9528 | 19848 | 30576 | 40576 | +| For Sub-Frame 5 | Bits | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | Bits | N/A | 6968 | 12576 | 30576 | 45352 | 61664 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of Code Blocks per Sub-Frame (NOTE 4) | | | | | | | | +| For Sub-Frames 3, 4, 8, 9 | | 1 | 2 | 3 | 5 | 8 | 11 | +| For Sub-Frames 1,6 | | N/A | 2 | 2 | 4 | 6 | 8 | +| For Sub-Frame 5 | | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | | N/A | 2 | 3 | 5 | 8 | 11 | +| Binary Channel Bits per Sub-Frame | | | | | | | | +| For Sub-Frames 3, 4, 8, 9 | Bits | 4104 | 11340 | 18900 | 41400 | 62100 | 82800 | +| For Sub-Frames 1,6 | | N/A | 7848 | 13368 | 27168 | 40968 | 54768 | +| For Sub-Frame 5 | Bits | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | Bits | N/A | 9252 | 16812 | 39312 | 60012 | 80712 | +| Max. Throughput averaged over 1 frame | kbps | 596.8 | 3791.2 | 6369.6 | 13910 | 20945 | 27877 | + +NOTE 1: For normal subframes(0,3,4,5,8,9), 2 symbols allocated to PDCCH for 20 MHz, 15 MHz and 10 MHz channel BW; 3 symbols allocated to PDCCH for 5 MHz and 3 MHz; 4 symbols allocated to PDCCH for 1.4 MHz. For special subframe (1&6), only 2 OFDM symbols are allocated to PDCCH for all BWs. + +NOTE 2: For 1.4MHz, no data shall be scheduled on special subframes(1&6) to avoid problems with insufficient PDCCH performance. + +NOTE 3: Reference signal, Synchronization signals and PBCH allocated as per TS 36.211 [7]. + +NOTE 4: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). + +NOTE 5: As per Table 4.2-2 in TS 36.211 [7]. + +NOTE 6: As per Table 4.2-1 in TS 36.211 [7] + +#### A.3.1.3 256-QAM + +**Table A.3.1.3-1: Fixed Reference Channel for Maximum input level for UE Categories 11/12 and UE DL categories $\geq 11$ (TDD)** + +| Parameter | Unit | Value | | | | | | +|----------------------------------------------|-----------|--------|--------|--------|---------|--------|---------| +| Channel bandwidth | MHz | 1.4 | 3 | 5 | 10 | 15 | 20 | +| Allocated resource blocks | | 6 | 15 | 25 | 50 | 75 | 100 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | 12 | 12 | +| Uplink-Downlink Configuration (NOTE 5) | | 2 | 2 | 2 | 2 | 2 | 2 | +| Special subframe configuration (NOTE 6) | | 7 | 7 | 7 | 7 | 7 | 7 | +| Allocated subframes per Radio Frame | | 2 | 3+2 | 3+2 | 3+2 | 3+2 | 3+2 | +| Modulation | | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | +| Target Coding Rate | | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 | +| Number of HARQ Processes | Processes | 7 | 7 | 7 | 7 | 7 | 7 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | 1 | 1 | +| Information Bit Payload per Sub-Frame | | | | | | | | +| For Sub-Frames 3,4,8,9 | Bits | 4392 | 12216 | 19848 | 42368 | 63776 | 84760 | +| For Sub-Frames 1,6 | Bits | N/A | 10464 | 17824 | 36224 | 54624 | 73024 | +| For Sub-Frame 5 | Bits | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | Bits | N/A | 9912 | 17568 | 42368 | 63776 | 84760 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of Code Blocks per Sub-Frame (NOTE 4) | | | | | | | | +| For Sub-Frames 3,4,8,9 | | 1 | 2 | 4 | 7 | 11 | 14 | +| For Sub-Frames 1,6 | | N/A | 2 | 3 | 6 | 9 | 13 | +| For Sub-Frame 5 | | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | | N/A | 2 | 3 | 7 | 11 | 14 | +| Binary Channel Bits per Sub-Frame | | | | | | | | +| For Sub-Frames 3,4,8,9 | Bits | 5472 | 15120 | 25200 | 55200 | 82800 | 110400 | +| For Sub-Frames 1,6 | | N/A | 8248 | 13536 | 27376 | 40576 | 55056 | +| For Sub-Frame 5 | Bits | N/A | N/A | N/A | N/A | N/A | N/A | +| For Sub-Frame 0 | Bits | N/A | 12336 | 22416 | 52416 | 80016 | 107616 | +| Max. Throughput averaged over 1 frame | kbps | 878.4 | 5570.4 | 9240 | 20049.6 | 30144 | 40503.2 | + +NOTE 1: For normal subframes(0,3,4,5,8,9), 2 symbols allocated to PDCCH for 20 MHz, 15 MHz and 10 MHz channel BW; 3 symbols allocated to PDCCH for 5 MHz and 3 MHz; 4 symbols allocated to PDCCH for 1.4 MHz. For special subframe (1&6), only 2 OFDM symbols are allocated to PDCCH for all BWs. + +NOTE 2: For 1.4MHz, no data shall be scheduled on special subframes(1&6) to avoid problems with insufficient PDCCH performance. + +NOTE 3: Reference signal, Synchronization signals and PBCH allocated as per TS 36.211 [7]. + +NOTE 4: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). + +NOTE 5: As per Table 4.2-2 in TS 36.211 [7]. + +NOTE 6: As per Table 4.2-1 in TS 36.211 [7]. + +# --- Annex B (normative): Propagation Conditions + +Please refer to Annex B in TS 38.521-1 [8] and 38.521-2 [9] for appropriate details as needed for test cases in this test specification. EN-DC exceptions will be added, + +# --- Annex C (normative): Downlink Physical Channels + +Please refer to Annex C in TS 38.521-1 [8] and 38.521-2 [9] for appropriate details as needed for test cases in this test specification. EN-DC exceptions will be added, + +# --- Annex D (normative): Characteristics of the Interfering Signal + +Please refer to Annex D in TS 38.521-1 [8] and 38.521-2 [9] for appropriate details as needed for test cases in this test specification. EN-DC exceptions will be added, + +# --- Annex E (normative): Global In-Channel Tx Test + +Please refer to Annex E in TS 38.521-1 [8] and 38.521-2 [9] for appropriate details as needed for test cases in this test specification. EN-DC exceptions will be added, + +# --- Annex F (informative): Measurement uncertainties and Test Tolerances + +## F.1 Acceptable uncertainty of Test System (normative) + +### F.1.0 General + +#### F.1.0.1 Conducted Measurements + +Same as F.1.0 in TS 38.521-1 [8]. + +#### F.1.0.2 Radiated Measurements + +Same as F.1.0 in TS 38.521-2 [9]. + +### F.1.1 Measurement of test environments + +#### F.1.1.1 Conducted Measurements + +Same as F.1.1 in TS 38.521-1 [8]. + +#### F.1.1.2 Radiated Measurements + +Same as F.1.1 in TS 38.521-2 [9]. + +### F.1.2 Measurement of transmitter + +**Table F.1.2-1: Maximum Test System Uncertainty for transmitter tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2B.1.1 UE Maximum Output Power for Intra-Band Contiguous EN-DC | $f \leq 3.0\text{GHz}$
$\pm 0.7\text{ dB}$ , $BW \leq 40\text{MHz}$
$\pm 1.4\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$

$3.0\text{GHz} < f \leq 4.2\text{GHz}$
$\pm 1.0\text{ dB}$ , $BW \leq 40\text{MHz}$
$\pm 1.6\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$

$4.2\text{GHz} < f \leq 6.0\text{GHz}$
$\pm 1.3\text{ dB}$ , $BW \leq 20\text{MHz}$
$\pm 1.5\text{ dB}$ , $20\text{MHz} < BW \leq 40\text{MHz}$
$\pm 1.6\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$ | | +| 6.2B.1.2 UE Maximum Output Power for Intra-Band Non-Contiguous EN-DC | MAX ( $MU_{\text{LTE}}$ , $MU_{\text{SA}}$ )

$MU_{\text{LTE}}$
$\pm 0.7\text{ dB}$ , $f \leq 3.0\text{GHz}$
$\pm 1.0\text{ dB}$ , $3.0\text{GHz} < f \leq 4.2\text{GHz}$

$MU_{\text{SA}}$
$f \leq 3.0\text{GHz}$
$\pm 0.7\text{ dB}$ , $BW \leq 40\text{MHz}$
$\pm 1.4\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$

$3.0\text{GHz} < f \leq 4.2\text{GHz}$
$\pm 1.0\text{ dB}$ , $BW \leq 40\text{MHz}$
$\pm 1.6\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$

$4.2\text{GHz} < f \leq 6.0\text{GHz}$
$\pm 1.3\text{ dB}$ , $BW \leq 20\text{MHz}$
$\pm 1.5\text{ dB}$ , $20\text{MHz} < BW \leq 40\text{MHz}$
$\pm 1.6\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$ | $MU_{\text{LTE}}$ is MU of LTE specified in clause 6.2.2 in TS 36.521-1 [10].

$MU_{\text{SA}}$ is MU of FR1 SA specified in clause 6.2.1 in TS 38.521-1 [8]. | +| 6.2B.1.3 UE Maximum Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) | MAX ( $MU_{\text{LTE}}$ , $MU_{\text{SA}}$ )

$MU_{\text{LTE}}$
$\pm 0.7\text{ dB}$ , $f \leq 3.0\text{GHz}$
$\pm 1.0\text{ dB}$ , $3.0\text{GHz} < f \leq 4.2\text{GHz}$

$MU_{\text{SA}}$
$f \leq 3.0\text{GHz}$
$\pm 0.7\text{ dB}$ , $BW \leq 40\text{MHz}$
$\pm 1.4\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$

$3.0\text{GHz} < f \leq 4.2\text{GHz}$
$\pm 1.0\text{ dB}$ , $BW \leq 40\text{MHz}$
$\pm 1.6\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$

$4.2\text{GHz} < f \leq 6.0\text{GHz}$
$\pm 1.3\text{ dB}$ , $BW \leq 20\text{MHz}$
$\pm 1.5\text{ dB}$ , $20\text{MHz} < BW \leq 40\text{MHz}$
$\pm 1.6\text{ dB}$ , $40\text{MHz} < BW \leq 100\text{MHz}$ | $MU_{\text{LTE}}$ is MU of LTE specified in clause 6.2.2 in TS 36.521-1 [10].

$MU_{\text{SA}}$ is MU of FR1 SA specified in clause 6.2.1 in TS 38.521-1 [8]. | +| 6.2B.1.3_1 UE Maximum Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) | Same as 6.2B.1.3 | | +| 6.2B.1.4.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP and TRP | Same as clause 6.2.1.1 in TS 38.521-2 [9] | | +| 6.2B.1.4.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - Spherical Coverage | Same as clause 6.2.1.2 in TS 38.521-2 [9] | | + +| | | | +|--------------------------------------------------------------------------------------------------------------|----------------------------------------------|--| +| 6.2B.1.4_1.1.1 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.1 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.1.2 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - Spherical Coverage | Same as clause 6.2A.1.2.1 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.2.1 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.2 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.2.2 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) -Spherical Coverage | Same as clause 6.2A.1.2.2 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.3.1 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.3 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.3.2 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) –Spherical Coverage | Same as clause 6.2A.1.2.3 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.4.1 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.4 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.4.2 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) –Spherical Coverage | Same as clause 6.2A.1.2.4 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.5.1 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.5 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.5.2 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) –Spherical Coverage | Same as clause 6.2A.1.2.5 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.6.1 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.6 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.6.2 UE
Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) –Spherical Coverage | Same as clause 6.2A.1.2.6 in TS 38.521-2 [9] | | +| 6.2B.1.4D.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO | Same as clause 6.2D.1.1 in TS 38.521-2 [9] | | +| 6.2B.1.4D.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO- Spherical coverage | Same as clause 6.2D.1.2 in TS 38.521-2 [9] | | + +| | | | +|-------------------------------------------------------------------------------------------------------|--------------------------------------------|--| +| 6.2B.2.1 UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | Same as clause 6.2B.1.1 | | +| 6.2B.2.2 UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | Same as clause 6.2B.1.2 | | +| 6.2B.2.3 UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 | Same as clause 6.2B.1.3 | | +| 6.2B.2.4 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 | Same as clause 6.2.2 in TS 38.521-2 [9] | | +| 6.2B.2.4a UE Maximum Output Power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) | Same as clause 6.2.2_1 in TS 38.521-2 [9] | | +| 6.2B.2.4_1.1 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (2 NR CCs) | Same as clause 6.2A.2.1 in TS 38.521-2 [9] | | +| 6.2B.2.4_1.2 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (3 NR CCs) | Same as clause 6.2A.2.2 in TS 38.521-2 [9] | | +| 6.2B.2.4_1.3 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (4 NR CCs) | Same as clause 6.2A.2.3 in TS 38.521-2 [9] | | +| 6.2B.3.1 UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC | Same as clause 6.2B.1.1 | | +| 6.2B.3.2 UE Additional Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | Same as clause 6.2B.1.2 | | +| 6.2B.3.3 UE Additional Maximum Output Power reduction for Inter-Band EN-DC within FR1 | Same as clause 6.2B.1.3 | | +| 6.2B.3.4 UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) | Same as clause 6.2.3 in TS 38.521-2 [9] | | +| 6.2B.4.1.1 Configured Output Power Level for Intra-Band Contiguous EN-DC | Same as clause 6.2B.1.1 | | +| 6.2B.4.1.2 Configured Output Power for Intra-Band Non-Contiguous EN-DC | Same as clause 6.2B.1.2 | | +| 6.2B.4.1.3 Configured Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) | Same as clause 6.2B.1.3 | | +| 6.2B.4.1.3_1 Configured Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) | Same as 6.2B.1.3 | | + +| | | | +|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| 6.2B.4.1.4_1 Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC) | Same as clause 6.2.4_1 in TS 38.521-2 [9] | | +| 6.3B.1.1 Minimum Output Power for intra-band contiguous EN-DC | Same as clause 6.3.1 in TS 38.521-1 [8] | | +| 6.3B.1.2 Minimum output power for intra-band non-contiguous EN-DC | Same as clause 6.3.1 in TS 38.521-1 [8] | | +| 6.3B.1.3 Minimum output power for inter-band EN-DC within FR1 | Same as clause 6.3.1 in TS 38.521-1 [8] | | +| 6.3B.1.4 Minimum Output Power for EN-DC Interband including FR2 | Same as clause 6.3.1 in TS 38.521-2 [9] | | +| 6.3B.1.4_1.1 Minimum output power for inter-band EN-DC including FR2 (3 CCs) | Same as 6.3A.1.1 in TS 38.521-2 [9] | | +| 6.3B.1.4_1.2 Minimum output power for inter-band EN-DC including FR2 (4 CCs) | Same as 6.3A.1.2 in TS 38.521-2 [9] | | +| 6.3B.1.4_1.3 Minimum output power for inter-band EN-DC including FR2 (5 CCs) | Same as 6.3A.1.3 in TS 38.521-2 [9] | | +| 6.3B.1.4D Minimum output power for inter-band EN-DC including FR2 for UL MIMO | Same as 6.3D.1 in TS 38.521-2 [9] | | +| 6.3B.2.1 Transmit OFF Power for intra-band contiguous EN-DC | Same as clause 6.3.2 in TS 38.521-1 [8] | | +| 6.3B.2.2 Transmit OFF Power for intra-band non-contiguous EN-DC | Same as clause 6.3.2 in TS 38.521-1 [8] | | +| 6.3B.2.3 Transmit OFF Power for inter-band EN-DC within FR1 | Same as clause 6.3.2 in TS 38.521-1 [8] | | +| 6.3B.2.4 Transmit OFF Power for inter-band EN-DC including FR2 | Same as clause 6.3.2 in TS 38.521-2 [9] | | +| 6.3B.2.4D Transmit OFF Power for inter-band EN-DC including FR2 for UL-MIMO | Same as 6.3D.2 in TS 38.521-2 [9] | | +| 6.3B.3.1 Tx ON/OFF time mask for intra-band contiguous EN-DC | Same as clause 6.3.3.2 in TS 38.521-1 [8] | | +| 6.3B.3_1.1 E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC | MAX (MU LTE , MU NR )

MU LTE is MU of LTE specified in clause 6.2.3 in TS 36.521-1 [10].

MU NR is MU of FR1 NR specified in clause 6.2D.2 in TS 38.521-1 [8]. | | +| 6.3B.2.4_1.1 Transmit OFF Power for Inter-band EN-DC including FR2 (3 CCs) | Same as clause 6.3A.2.1 in TS 38.521-2 [9] | | +| 6.3B.2.4_1.2 Transmit OFF Power for Inter-band EN-DC including FR2 (4 CCs) | Same as clause 6.3A.2.2 in TS 38.521-2 [9] | | +| 6.3B.2.4_1.3 Transmit OFF Power for Inter-band EN-DC including FR2 (5 CCs) | Same as clause 6.3A.2.3 in TS 38.521-2 [9] | | + +| | | | +|--------------------------------------------------------------------------------------|----------------------------------------------|--| +| 6.3B.3.2 Tx ON/OFF time mask for intra-band non-contiguous EN-DC | Same as clause 6.3.3.2 in TS 38.521-1 [8] | | +| 6.3B.3.3 Tx ON/OFF time mask for inter-band EN-DC within FR1 | Same as clause 6.3.3.2 in TS 38.521-1 [8] | | +| 6.3B.3.4 Transmit ON/OFF time mask for inter-band EN-DC including FR2 | Same as clause 6.3.3.2 in TS 38.521-2 [9] | | +| 6.3B.3.4_1.1 Transmit ON/OFF time mask for inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.3A.3.1.1 in TS 38.521-2 [9] | | +| 6.3B.4.3 PRACH Time Mask for inter-band EN-DC within FR1 | Same as clause 6.3.3.4 in TS 38.521-1 [8] | | +| 6.3B.8.1.1 Absolute power tolerance for intra-band contiguous EN-DC | Same as clause 6.3.4.2 in TS 38.521-1 [8] | | +| 6.3B.8.1.2 Absolute power tolerance for intra-band non-contiguous EN-DC | Same as clause 6.3.4.2 in TS 38.521-1 [8] | | +| 6.3B.8.1.3 Absolute power tolerance for inter-band EN-DC within FR1 | Same as clause 6.3.4.2 in TS 38.521-1 [8] | | +| 6.3B.8.1.4 Absolute power tolerance for inter-band EN-DC including FR2 | Same as clause 6.3.4.2 in TS 38.521-2 [9] | | +| 6.3B.8.2.1 Relative power tolerance for intra-band contiguous EN-DC | Same as clause 6.3.4.3 in TS 38.521-1 [8] | | +| 6.3B.8.2.2 Relative power tolerance for intra-band non-contiguous EN-DC | Same as clause 6.3.4.3 in TS 38.521-1 [8] | | +| 6.3B.8.2.3 Relative power tolerance for inter-band EN-DC within FR1 | Same as clause 6.3.4.3 in TS 38.521-1 [8] | | +| 6.3B.8.2.4 Relative power tolerance for inter-band EN-DC including FR2 | Same as clause 6.3.4.3 in TS 38.521-2 [9] | | +| 6.3B.8.3.1 Aggregate power tolerance for intra-band contiguous EN-DC | Same as clause 6.3.4.4 in TS 38.521-1 [8] | | +| 6.3B.8.3.2 Aggregate power tolerance for intra-band non-contiguous EN-DC | Same as clause 6.3.4.4 in TS 38.521-1 [8] | | +| 6.3B.8.3.3 Aggregate power tolerance for inter-band EN-DC within FR1 | Same as clause 6.3.4.4 in TS 38.521-1 [8] | | +| 6.3B.8.3.4 Aggregate power tolerance for inter-band EN-DC including FR2 | Same as clause 6.3.4.4 in TS 38.521-2 [9] | | +| 6.4B.1.1 Frequency Error for intra-band contiguous EN-DC | TBD | | +| 6.4B.1.2 Frequency Error for intra-band non-contiguous EN-DC | TBD | | +| 6.4B.1.3 Frequency Error for inter-band EN-DC within FR1 | Same as clause 6.4.1 in TS 38.521-1 [8] | | +| 6.4B.1.4 Frequency Error for inter-band EN-DC including FR2 | Same as clause 6.4.1 in TS 38.521-2 [9] | | +| 6.4B.1.4_1.1 Frequency Error for Inter-band EN-DC including FR2 (3 CCs) | Same as clause 6.4A.1.1 in TS 38.521-2 [9] | | + +| | | | +|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| 6.4B.1.4_1.2 Frequency Error for Inter-band EN-DC including FR2 (4 CCs) | Same as clause 6.4A.1.2 in TS 38.521-2 [9] | | +| 6.4B.1.4_1.3 Frequency Error for Inter-band EN-DC including FR2 (5 CCs) | Same as clause 6.4A.1.3 in TS 38.521-2 [9] | | +| 6.4B.2.1.1 Error Vector Magnitude for intra-band contiguous EN-DC | Same as clause 6.4.2.1 in TS 38.521-1 [8]
Uplink power measurement same as 6.3B.1.1. | | +| 6.4B.2.1.2 Carrier Leakage for intra-band contiguous EN-DC | Same as clause 6.4.2.2 in TS 38.521-1 [8] | | +| 6.4B.2.1.3 In-band Emissions for intra-band contiguous EN-DC | Same as clause 6.4.2.3 in TS 38.521-1 [8] for ENBW $\leq 100\text{MHz}$ .
Uplink power measurement for steps 2 and 8 same as 6.2B.1.1.
Uplink power measurement for steps 4, 6, 10, and 12 same as 6.3B.1.1. | | +| 6.4B.2.1.4 EVM Equalizer Flatness for intra-band contiguous EN-DC | Same as clause 6.4.2.4 in TS 38.521-1 [8] | | +| 6.4B.2.2.1 Error Vector Magnitude for intra-band non-contiguous EN-DC | Same as clause 6.4.2.1 in TS 38.521-1 [8]
Uplink power measurement same as 6.3B.1.2. | | +| 6.4B.2.2.2 Carrier Leakage for intra-band non-contiguous EN-DC | Same as clause 6.4.2.2 in TS 38.521-1 [8]
Uplink power measurement for step 2 and step 4 same as 6.2B.1.2.
Uplink power measurement for step 6 and step 8 same as 6.3B.1.2. | | +| 6.4B.2.2.3 In-band Emissions for intra-band non-contiguous EN-DC | Same as clause 6.4.2.3 in TS 38.521-1 [8]
Uplink power measurement for steps 2 and 8 same as 6.2B.1.2.
Uplink power measurement for steps 4, 6, 10, and 12 same as 6.3B.1.2. | | +| 6.4B.2.2.4 EVM Equalizer Flatness for intra-band non-contiguous EN-DC | Same as clause 6.4.2.4 in TS 38.521-1 [8] | | +| 6.4B.2.3.1 Error Vector Magnitude for inter-band EN-DC within FR1 | Same as clause 6.4.2.1 in TS 38.521-1 [8]
Uplink power measurement same as 6.3B.1.3. | | +| 6.4B.2.3.2 Carrier Leakage for inter-band EN-DC within FR1 | Same as clause 6.4.2.2 in TS 38.521-1 [8]
Uplink power measurement for step 2 and step 4 same as 6.2B.1.3.
Uplink power measurement for step 6 and step 8 same as 6.3B.1.3. | | +| 6.4B.2.3.3 In-band Emissions for inter-band EN-DC within FR1 | Same as clause 6.4.2.3 in TS 38.521-1 [8]
Uplink power measurement for steps 1.2, 1.4, 2.2, and 2.4 same as 6.2B.1.3.
Uplink power measurement for steps 1.6, 1.8, 2.6, and 2.8 same as 6.3B.1.3. | | +| 6.4B.2.3.4 EVM Equalizer Flatness for inter-band EN-DC within FR1 | Same as clause 6.4.2.4 in TS 38.521-1 [8] | | +| 6.4B.2.4.1 Error Vector Magnitude for inter-band EN-DC including FR2 | Same as clause 6.4.2.1 in TS 38.521-2 [9] | | +| 6.4B.2.4.1a Error Vector Magnitude with Power Boost for inter-band EN-DC including FR2 (1 NR CC) | Same as clause 6.4.2.1_1 in TS 38.521-2 [9] | | +| 6.4B.2.4.2 Carrier Leakage for inter-band EN-DC including FR2 | Same as clause 6.4.2.2 in TS 38.521-2 [9] | | +| 6.4B.2.4.3 In-band Emissions for inter-band EN-DC including FR2 | Same as clause 6.4.2.3 in TS 38.521-2 [9] | | + +| | | | +|--------------------------------------------------------------------------------------------------------|---------------------------------------------|--| +| 6.4B.2.4.4 EVM Equalizer Flatness for inter-band EN-DC including FR2 | Same as clause 6.4.2.4 in TS 38.521-2 [9] | | +| 6.4B.2.4.5 EVM spectral flatness for pi/2 BPSK modulation for inter-band EN-DC including FR2 (1 NR CC) | Same as clause 6.4.2.5 in TS 38.521-2 [9] | | +| 6.5B.1.1 Occupied bandwidth for Intra-Band Contiguous EN-DC | 1.5% of aggregated channel bandwidth | | +| 6.5B.1.2 Occupied bandwidth for Intra-Band Non-Contiguous EN-DC | Same as clause 6.5.1 in TS 38.521-1 [8] | | +| 6.5B.1.3 Occupied bandwidth for Inter-Band EN-DC within FR1 | Same as clause 6.5.1 in TS 38.521-1 [8] | | +| 6.5B.1.4 Occupied bandwidth for Inter-Band EN-DC including FR2 | Same as clause 6.5.1 in TS 38.521-2 [9] | | +| 6.5B.1.4_1.1 Occupied bandwidth for Inter-band EN-DC including FR2 (3 CCs) | TBD | | +| 6.5B.1.4_1.2 Occupied bandwidth for Inter-band EN-DC including FR2 (4 CCs) | TBD | | +| 6.5B.1.4_1.3 Occupied bandwidth for Inter-band EN-DC including FR2 (5 CCs) | TBD | | +| 6.5B.1.4D Occupied bandwidth for inter-band EN-DC including FR2 for UL MIMO | Same as clause 6.5D.1 in TS 38.521-2 [9] | | +| 6.5B.2.1.1 Spectrum emissions mask for intra-band contiguous EN-DC | Same as clause 6.5.2.2 in TS 38.521-1 [8] | | +| 6.5B.2.1.2 Additional spectrum emissions mask for intra-band contiguous EN-DC | Same as clause 6.5.2.3 in TS 38.521-1 [8] | | +| 6.5B.2.1.3 Adjacent channel leakage ratio for intra-band contiguous EN-DC | Same as clause 6.5.2.4.1 in TS 38.521-1 [8] | | +| 6.5B.2.2.1 Spectrum emissions mask for intra-band non-contiguous EN-DC | Same as clause 6.5.2.2 in TS 38.521-1 [8] | | +| 6.5B.2.2.2 Additional Spectrum emissions mask for intra-band non-contiguous EN-DC | Same as clause 6.5.2.3 in TS 38.521-1 [8] | | +| 6.5B.2.2.3 Adjacent channel leakage ratio for intra-band non-contiguous EN-DC | TBD | | +| 6.5B.2.3.1 Spectrum emissions mask for Inter-band EN-DC within FR1 | Same as clause 6.5.2.2 in TS 38.521-1 [8] | | +| 6.5B.2.3.2 Additional Spectrum emissions mask for Inter-band EN-DC within FR1 | Same as clause 6.5.2.3 in TS 38.521-1 [8] | | +| 6.5B.2.3.3.1NR - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) | Same as clause 6.5.2.4.1 in TS 38.521-1 [8] | | + +| | | | +|---------------------------------------------------------------------------------------------------|-----------------------------------------------|--| +| 6.5B.2.3.3.2 UTRA
- Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) | Same as clause 6.5.2.4.2 in TS 38.521-1 [8] | | +| 6.5B.2.4.1 Spectrum emissions mask for Inter-band EN-DC including FR2 | Same as clause 6.5.2.1 in TS 38.521-2 [9] | | +| 6.5B.2.4.1a Spectrum emissions mask with Power Boost for Inter-band EN-DC including FR2 (1 NR CC) | Same as clause 6.5.2.1.1_1 in TS 38.521-2 [9] | | +| 6.5B.2.4.1_1.1 Spectrum emissions mask for Inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.5A.2.1.1 in TS 38.521-2 [9] | | +| 6.5B.2.4.1_1.2 Spectrum emissions mask for Inter-band EN-DC including FR2 (3 NR CCs) | Same as clause 6.5A.2.1.2 in TS 38.521-2 [9] | | +| 6.5B.2.4.1_1.3 Spectrum emissions mask for Inter-band EN-DC including FR2 (4 NR CCs) | Same as clause 6.5A.2.3 in TS 38.521-2 [9] | | +| 6.5B.2.4.3 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 | Same as clause 6.5.2.3 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.1 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.5A.2.2.1 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.2 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (3 NR CCs) | Same as clause 6.5A.2.2.2 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.3 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (4 NR CCs) | Same as clause 6.5A.2.2.3 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.4 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (5 NR CCs) | Same as clause 6.5A.2.2.4 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.5 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (6 NR CCs) | Same as clause 6.5A.2.2.5 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.6 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (7 NR CCs) | Same as clause 6.5A.2.2.6 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.7 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (8 NR CCs) | Same as clause 6.5A.2.2.7 in TS 38.521-2 [9] | | +| 6.5B.3.1.1 General spurious emissions for intra-band contiguous EN-DC | Same as clause 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.1.2 Spurious emission band UE co-existence for intra-band contiguous EN-DC | Same as clause 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.2.1 General spurious emissions for Intra-band non-contiguous EN-DC | Same as clause 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.2.2 Spurious Emission band UE co-existence for intra-band non-contiguous EN-DC | Same as clause 6.5.3.1 in TS 38.521-1 [8] | | + +| | | | +|------------------------------------------------------------------------------------------------------------|----------------------------------------------|--| +| 6.5B.3.3.1 General spurious emissions for Inter-band EN-DC within FR1 | Same as clause 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 | Same as clause 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.4.1 General Spurious Emissions for Inter-band including FR2 (2 CCs) | Same as clause 6.5.3.1 in TS 38.521-2 [9] | | +| 6.5B.3.4.1a General Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.1_1 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.1 General Spurious Emissions for Inter-band including FR2 (2 NR CCs) | Same as clause 6.5A.3.1.1 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.2 General Spurious Emissions for Inter-band including FR2 (3 NR CCs) | Same as clause 6.5A.3.1.2 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.3 General Spurious Emissions for Inter-band including FR2 (4 NR CCs) | Same as clause 6.5A.3.1.3 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.4 General Spurious Emissions for Inter-band including FR2 (5 NR CCs) | Same as clause 6.5A.3.1.4 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.5 General Spurious Emissions for Inter-band including FR2 (6 NR CCs) | Same as clause 6.5A.3.1.5 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.6 General Spurious Emissions for Inter-band including FR2 (7 NR CCs) | Same as clause 6.5A.3.1.6 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.7 General Spurious Emissions for Inter-band including FR2 (8 NR CCs) | Same as clause 6.5A.3.1.7 in TS 38.521-2 [9] | | +| 6.5B.3.4.2 Spurious emission band UE co-existence for Inter-band including FR2 | Same as clause 6.5.3.2 in TS 38.521-2 [9] | | +| 6.5B.3.4.2a Spurious emission band UE co-existence with Power Boost for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.2_1 in TS 38.521-2 [9] | | +| 6.5B.3.4.2_1.1 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.5A.3.2.1 in TS 38.521-2 [9] | | +| 6.5B.3.4.2_1.2 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (3 NR CCs) | Same as clause 6.5A.3.2.2 in TS 38.521-2 [9] | | +| 6.5B.3.4.2_1.3 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (4 NR CCs) | Same as clause 6.5A.3.2.3 in TS 38.521-2 [9] | | + +| | | | +|-------------------------------------------------------------------------------------------------|----------------------------------------------|--| +| 6.5B.4.1 Additional Spurious Emissions for Intra-band contiguous EN-DC | Same as clause 6.5.3.3 in TS 38.521-1 [8] | | +| 6.5B.4.2 Additional Spurious Emissions for Intra-band non-contiguous EN-DC | Same as clause 6.5.3.3 in TS 38.521-1 [8] | | +| 6.5B.4.3 Additional Spurious Emissions for Inter-band EN-DC within FR1 | Same as clause 6.5.3.3 in TS 38.521-1 [8] | | +| 6.5B.4.4 Additional Spurious Emissions for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.3 in TS 38.521-2 [9] | | +| 6.5B.4.4a Additional Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.3_1 in TS 38.521-2 [9] | | +| 6.5B.4.4_1.1 Additional Spurious Emissions for Inter-band including FR2 (2 NR CC) | Same as clause 6.5A.3.3.1 in TS 38.521-2 [9] | | +| 6.5B.4.4_1.2 Additional Spurious Emissions for Inter-band including FR2 (3 NR CC) | Same as clause 6.5A.3.3.2 in TS 38.521-2 [9] | | +| 6.5B.4.4_1.3 Additional Spurious Emissions for Inter-band including FR2 (4 NR CC) | Same as clause 6.5A.3.3.3 in TS 38.521-2 [9] | | +| 6.5B.5.3 Transmit intermodulation for Inter-band EN-DC within FR1 | Same as clause 6.5.4.3 in TS 38.521-1 [8] | | +| 6.6B.4 Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP | Same as clause 6.6.1 in TS 38.521-2 [9] | | +| 6.6B.5 Enhanced Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP | Same as clause 6.6.2 in TS 38.521-2 [9] | | + +### F.1.3 Measurement of receiver + +**Table F.1.3-1: Maximum Test System Uncertainty for receiver tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| 7.3B.2.1 Reference sensitivity for Intra-band Contiguous EN-DC (2 CCs) | Same as clause 7.3.2 in TS 38.521-1 [8] | | +| 7.3B.2.2 Reference sensitivity for Intra-band non-contiguous EN-DC (2 CCs) | Same as clause 7.3.2 in TS 38.521-1 [8] | | +| 7.3B.2.3 Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.3.2 in TS 38.521-1 [8] | | +| 7.3B.2.3_1.1 Reference sensitivity for Inter-band EN-DC within FR1 (3 CCs) | Same as clause 7.3A.1 in TS 38.521-1 [8] | | +| 7.3B.2.4 Reference sensitivity for Inter-band EN-DC including FR2 | Same as clause 7.3.2 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.1 Reference sensitivity for Inter-band EN-DC including FR2 (3 CCs) | Same as clause 7.3A.2.1 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.2 Reference sensitivity for Inter-band EN-DC including FR2 (4 CCs) | Same as clause 7.3A.2.2 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.3 Reference sensitivity for Inter-band EN-DC including FR2 (5 CCs) | Same as clause 7.3A.2.3 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.4 Reference sensitivity for Inter-band EN-DC including FR2 (6 CCs) | Same as clause 7.3A.2.4 in TS 38.521-2 [9] | | +| 7.3B.4 EIS Spherical Coverage for Inter-band EN-DC including FR2 | Same as clause 7.3.4 in TS 38.521-2 [9] | | +| 7.4B.1 Maximum Input Level for Intra-Band Contiguous EN-DC (2 CCs) | MU for NR CC downlink power same as clause 7.4 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.1. | | +| 7.4B.2 Maximum Input Level for Intra-Band Non-Contiguous EN-DC (2 CCs) | Same as clause 7.4 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.2. | | +| 7.4B.3 Maximum Input Level for Inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.4 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.4B.3_1.1 Maximum Input Level for Inter-band EN-DC within FR1 (3 CCs) | Same as clause 7.4A.1 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.5B.1 Adjacent Channel Selectivity for intra-band contiguous EN-DC (2 CCs) | Same as clause 7.5 in TS 38.521-1 [8] for NR CC
Same as clause 7.5 in TS 36.521 [10]
Uplink power measurement same as 6.2B.1.1. | | +| 7.5B.2 Adjacent Channel Selectivity for intra-band non-contiguous EN-DC (2 CCs) | Same as clause 7.5 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.2. | | +| 7.5B.3 Adjacent Channel Selectivity for inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.5 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.5B.3_1.1 Adjacent Channel Selectivity for EN-DC within FR1 (3 CCs) | Same as clause 7.5A in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.5B.3_1.2 Adjacent Channel Selectivity for EN-DC within FR1 (4 CCs) | Same as clause 7.5A in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.5B.3_1.3 Adjacent Channel Selectivity for EN-DC within FR1 (5 CCs) | Same as clause 7.5A in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.5B.3_1.4 Adjacent Channel Selectivity for EN-DC within FR1 (6 CCs) | Same as clause 7.5A in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | + +| | | | +|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|--| +| 7.5B.4 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (2CCs) | Same as clause 7.5 in TS 38.521-2 [9] | | +| 7.5B.4_1.1 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (3 CCs) | Same as clause 7.5A in TS 38.521-2 [9] | | +| 7.5B.4_1.2 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (4 CCs) | Same as clause 7.5A in TS 38.521-2 [9] | | +| 7.5B.4_1.3 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (5 CCs) | Same as clause 7.5A in TS 38.521-2 [9] | | +| 7.5B.4_1.4 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (6 CCs) | Same as clause 7.5A in TS 38.521-2 [9] | | +| 7.6B.2.1 Inband blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | MU for NR CC downlink power same as clause 7.6.2 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.1. | | +| 7.6B.2.2 Inband blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as clause 7.6.2 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.2. | | +| 7.6B.2.3 Inband blocking for inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.6.2 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.2.3_1.1 Inband blocking for EN-DC within FR1 (3 CCs) | Same as clause 7.6A.2.1 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.2.3_1.2 Inband blocking for EN-DC within FR1 (4 CCs) | Same as clause 7.6.2 in TS 38.521-1 [8] for each component carrier.
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.2.3_1.3 Inband blocking for EN-DC within FR1 (5 CCs) | Same as clause 7.6.2 in TS 38.521-1 [8] for each component carrier.
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.2.4 Inband blocking for inter-band EN-DC including FR2 (2 CCs) | Same as 7.6.2 in TS 38.521-2 [9] | | +| 7.6B.2.4_1.1 Inband blocking for inter-band EN-DC including FR2 (3 CCs) | TBD | | +| 7.6B.2.4_1.2 Inband blocking for inter-band EN-DC including FR2 (4 CCs) | TBD | | +| 7.6B.2.4_1.3 Inband blocking for inter-band EN-DC including FR2 (5 CCs) | TBD | | +| 7.6B.2.4_1.4 Inband blocking for inter-band EN-DC including FR2 (6 CCs) | TBD | | +| 7.6B.3.1 Out-of-band blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | MU for NR CC downlink power same as clause 7.6.3 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.1. | | +| 7.6B.3.2 Out-of-band blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as clause 7.6.3 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.2. | | +| 7.6B.3.3 Out-of-band blocking for inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.6.3 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.3.3_1.1 Out-of-band blocking for EN-DC within FR1 (3 CCs) | Same as clause 7.6A.3.1 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.3. | | + +| | | | +|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|--| +| 7.6B.4.1 Narrow band blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | MU for NR CC downlink power same as clause 7.6.4 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.1. | | +| 7.6B.4.2 Narrow band blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as clause 7.6.4 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.2. | | +| 7.6B.4.3 Narrow band blocking for inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.6.4 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.4.3_1.1 Narrow band blocking for EN-DC within FR1 (3 CCs) | Same as clause 7.6A.4.1 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.4.3_1.2 Narrow band blocking for EN-DC within FR1 (4 CCs) | Same as clause 7.6.4 in TS 38.521-1 [8] for each component carrier.
Uplink power measurement same as 6.2B.1.3. | | +| 7.6B.4.3_1.3 Narrow band blocking for EN-DC within FR1 (5 CCs) | Same as clause 7.6.4 in TS 38.521-1 [8] for each component carrier.
Uplink power measurement same as 6.2B.1.3. | | +| 7.7B.1 Spurious Response for intra-band contiguous EN-DC in FR1 (2 CCs) | MU for NR CC downlink power same as clause 7.7 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.1. | | +| 7.7B.2 Spurious Response for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as clause 7.7 in TS 38.521-1 [8]
Uplink power measurement same as 6.2B.1.2. | | +| 7.7B.3 Spurious Response for inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.7 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.3. | | +| 7.7B.3_1.1 Spurious Response for EN-DC within FR1 (3 CCs) | Same as clause 7.7 in TS 38.521-1 [8] for each component carrier.
Uplink power measurement same as 6.2B.1.2. | | +| 7.7B.3_1.2 Spurious Response for EN-DC within FR1 (4 CCs) | Same as clause 7.7 in TS 38.521-1 [8] for each component carrier.
Uplink power measurement same as 6.2B.1.2. | | +| 7.8B.2.1 Wideband Intermodulation for intra-band contiguous EN-DC in FR1 | MU for NR CC downlink power same as clause 7.8.2 in TS 38.521-1 [8].
Uplink power measurement same as 6.2B.1.1. | | +| 7.8B.2.2 Wideband Intermodulation for intra-band non-contiguous EN-DC in FR1 | Same as clause 7.8.2 in TS 38.521-1 [8]
Uplink power measurement for same as 6.2B.1.2. | | +| 7.8B.2.3 Wideband Intermodulation for inter-band EN-DC in FR1 | Same as clause 7.8.2 in TS 38.521-1 [8]
Uplink power measurement for same as 6.2B.1.3. | | +| 7.8B.2.3_1.1 Wideband Intermodulation for EN-DC within FR1 (3 CCs) | Same as clause 7.8A.2.1 in TS 38.521-1 [8]
Uplink power measurement for same as 6.2B.1.3. | | +| 7.8B.2.3_1.2 Wideband Intermodulation for EN-DC within FR1 (4 CCs) | Same as clause 7.8A.2 in TS 38.521-1 [8]
Uplink power measurement for same as 6.2B.1.3. | | +| 7.8B.2.3_1.3 Wideband Intermodulation for EN-DC within FR1 (5 CCs) | Same as clause 7.8A.2 in TS 38.521-1 [8]
Uplink power measurement for same as 6.2B.1.3. | | +| 7.8B.2.3_1.4 Wideband Intermodulation for EN-DC within FR1 (6 CCs) | Same as clause 7.8A.2 in TS 38.521-1 [8]
Uplink power measurement for same as 6.2B.1.3. | | +| 7.9B.1 Spurious Emissions for intra-band contiguous EN-DC within FR1 (2 CCs) | Same as clause 7.9 in TS 38.521-1 [8] | | +| 7.9B.2 Spurious Emissions for intra-band non-contiguous EN-DC within FR1 (2 CCs) | Same as clause 7.9 in TS 38.521-1 [8] | | + +| | | | +|----------------------------------------------------------------------|------------------------------------------|--| +| 7.9B.3 Spurious Emissions for inter-band EN-DC within FR1 (2 CCs) | Same as clause 7.9 in TS 38.521-1 [8] | | +| 7.9B.3_1.1 Spurious Emissions for EN-DC within FR1 (3 CCs) | Same as clause 7.9A.1 in TS 38.521-1 [8] | | +| 7.9B.4 Spurious Emissions for inter-band EN-DC including FR2 (2 CCs) | Same as clause 7.9 in TS 38.521-2 [9] | | + +## --- F.2 Interpretation of measurement results (normative) + +TBD + +## --- F.3 Test Tolerance and Derivation of Test Requirements (informative) + +TBD + +### F.3.1 Measurement of test environments + +TBD + +### F.3.2 Measurement of transmitter + +**Table F.3.2-1: Derivation of Test Requirements (Transmitter tests)** + +| Sub clause | Test Tolerance (TT) | Formula for test requirement | +|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2B.1.1 UE Maximum Output Power for Intra-Band Contiguous EN-DC | Same as 6.2.1 in TS 38.521-1 [8] | | +| 6.2B.1.2 UE Maximum Output Power for Intra-Band Non-Contiguous EN-DC | MAX (TT LTE , TT SA )

TT LTE
0.7 dB, $f \leq 3.0\text{GHz}$
1.0 dB, $3.0\text{GHz} < f \leq 4.2\text{GHz}$

TT SA
$f \leq 3.0\text{GHz}$
0.7 dB, $BW \leq 40\text{MHz}$
1.0 dB, $40\text{MHz} < BW \leq 100\text{MHz}$
$3.0\text{GHz} < f \leq 6.0\text{GHz}$
1.0 dB, $BW \leq 100\text{MHz}$ | TT LTE is TT of LTE specified in 6.2.2 in TS 36.521-1 [10].

TT SA is TT of FR1 SA specified in 6.2.1 in TS 38.521-1 [8]. | +| 6.2B.1.3 UE Maximum Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) | MAX (TT LTE , TT SA )

TT LTE
0.7 dB, $f \leq 3.0\text{GHz}$
1.0 dB, $3.0\text{GHz} < f \leq 4.2\text{GHz}$

TT SA
$f \leq 3.0\text{GHz}$
0.7 dB, $BW \leq 40\text{MHz}$
1.0 dB, $40\text{MHz} < BW \leq 100\text{MHz}$
$3.0\text{GHz} < f \leq 6.0\text{GHz}$
1.0 dB, $BW \leq 100\text{MHz}$ | TT LTE is TT of LTE specified in 6.2.3 in TS 36.521-1 [10].

TT SA is TT of FR1 SA specified in 6.2.2 in TS 38.521-1 [8]. | +| 6.2B.1.3_1 UE Maximum Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) | Same as 6.2B.1.3 | | +| 6.2B.1.4 UE Maximum Output Power for Inter-Band EN-DC including FR2 | Same as 6.2.1 in TS 38.521-2 [9] | | +| 6.2B.1.4.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP and TR | Same as 6.2.1.1 in TS 38.521-2 [9] | | +| 6.2B.1.4.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - Spherical Coverage | Same as 6.2.1.2 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.1.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - EIRP and TRP | Same as 6.2A.1.1.1 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.1.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - Spherical Coverage | Same as 6.2A.1.2.1 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.2.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.2 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.2.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - Spherical Coverage | Same as clause 6.2A.1.2.2 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.3.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.3 in TS 38.521-2 [9] | | + +| | | | +|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------|--| +| 6.2B.1.4_1.3.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) – Spherical Coverage | Same as clause 6.2A.1.2.3 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.4.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.4 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.4.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (5 NR CCs) – Spherical Coverage | Same as clause 6.2A.1.2.4 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.5.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.5 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.5.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (6 NR CCs) – Spherical Coverage | Same as clause 6.2A.1.2.5 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.6.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) - EIRP and TRP | Same as clause 6.2A.1.1.6 in TS 38.521-2 [9] | | +| 6.2B.1.4_1.6.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 (7 NR CCs) – Spherical Coverage | Same as clause 6.2A.1.2.6 in TS 38.521-2 [9] | | +| 6.2B.1.4D.1 UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO | Same as clause 6.2D.1.1 in TS 38.521-2 [9] | | +| 6.2B.1.4D.2 UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO- Spherical coverage | Same as clause 6.2D.1.2 in TS 38.521-2 [9] | | +| 6.2B.2.1 UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | Same as 6.2.2 in TS 38.521-1 [8] | | +| 6.2B.2.2 UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | Same as 6.2B.1.2 | | +| 6.2B.2.3 UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 | Same as 6.2B.1.3 | | +| 6.2B.2.4 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 | Same as clause 6.2.2 and 6.2A.2.1 in TS 38.521-2 [9] | | +| 6.2B.2.4a UE Maximum Output Power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) | Same as clause 6.2.2_1 in TS 38.521-2 [9] | | +| 6.2B.2.4_1.1 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (2 NR CCs) | Same as clause 6.2A.2.1 in TS 38.521-2 [9] | | + +| | | | +|----------------------------------------------------------------------------------------------------|--------------------------------------------|--| +| 6.2B.2.4_1.2 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (3 NR CCs) | Same as clause 6.2A.2.2 in TS 38.521-2 [9] | | +| 6.2B.2.4_1.3 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (4 NR CCs) | Same as clause 6.2A.2.3 in TS 38.521-2 [9] | | +| 6.2B.3.1 UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC | Same as 6.2.3 in TS 38.521-1 [8] | | +| 6.2B.3.2 UE Additional Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | Same as 6.2B.1.2 | | +| 6.2B.3.3 UE Additional Maximum Output Power reduction for Inter-Band EN-DC within FR1 | Same as 6.2B.1.3 | | +| 6.2B.3.4 UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) | Same as clause 6.2.3 in TS 38.521-2 [9] | | +| 6.2B.4.1.1 Configured Output Power Level for Intra-Band Contiguous EN-DC | Same as 6.2.4 in TS 38.521-1 [8] | | +| 6.2B.4.1.2 Configured Output Power for Intra-Band Non-Contiguous EN-DC | Same as 6.2B.1.2 | | +| 6.2B.4.1.3 Configured Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) | Same as 6.2B.1.3 | | +| 6.2B.4.1.3_1 Configured Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) | Same as 6.2B.1.3 | | +| 6.2B.4.1.4_1 Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC) | Same as clause 6.2.4_1 in TS 38.521-2 [9] | | +| 6.3B.1.1 Minimum Output Power for intra-band contiguous EN-DC | Same as 6.3.1 in TS 38.521-1 [8] | | +| 6.3B.1.2 Minimum output power for intra-band non-contiguous EN-DC | Same as 6.3.1 in TS 38.521-1 [8] | | +| 6.3B.1.3 Minimum output power for inter-band EN-DC within FR1 | Same as 6.3.1 in TS 38.521-1 [8] | | +| 6.3B.1.4 Minimum Output Power for EN-DC Interband including FR2 | Same as 6.3.1 in TS 38.521-2 [9] | | +| 6.3B.1.4_1.1 Minimum output power for inter-band EN-DC including FR2 (3 CCs) | Same as 6.3A.1.1 in TS 38.521-2 [9] | | +| 6.3B.1.4_1.2 Minimum output power for inter-band EN-DC including FR2 (4 CCs) | Same as 6.3A.1.2 in TS 38.521-2 [9] | | +| 6.3B.1.4_1.3 Minimum output power for inter-band EN-DC including FR2 (5 CCs) | Same as 6.3A.1.3 in TS 38.521-2 [9] | | + +| | | | +|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| 6.3B.1.4D Minimum output power for inter-band EN-DC including FR2 for UL MIMO | Same as 6.3D.1 in TS 38.521-2 [9] | | +| 6.3B.2.1 Transmit OFF Power for intra-band contiguous EN-DC | Same as 6.3.2 in TS 38.521-1 [8] | | +| 6.3B.2.2 Transmit OFF Power for intra-band non-contiguous EN-DC | Same as 6.3.2 in TS 38.521-1 [8] | | +| 6.3B.2.3 Transmit OFF Power for inter-band EN-DC within FR1 | Same as 6.3.2 in TS 38.521-1 [8] | | +| 6.3B.2.4 Transmit OFF Power for inter-band EN-DC including FR2 | Same as 6.3.2 in TS 38.521-2 [9] | | +| 6.3B.2.4D Transmit OFF Power for inter-band EN-DC including FR2 for UL-MIMO | Same as 6.3D.2 in TS 38.521-2 [9] | | +| 6.3B.3.1 Tx ON/OFF time mask for intra-band contiguous EN-DC | Same as 6.3.3.2 in TS 38.521-1 [8] | | +| 6.3B.3_1.1 E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC | MAX (TT LTE , TT NR )

TT LTE is TT of LTE specified in clause 6.2.3 in TS 36.521-1 [10].

TT NR is TT of FR1 NR specified in clause 6.2D.2 in TS 38.521-1 [8]. | | +| 6.3B.2.4_1.1 Transmit OFF Power for Inter-band EN-DC including FR2 (3 CCs) | Same as 6.3A.2.1 in TS 38.521-2 [9] | | +| 6.3B.2.4_1.2 Transmit OFF Power for Inter-band EN-DC including FR2 (4 CCs) | Same as 6.3A.2.2 in TS 38.521-2 [9] | | +| 6.3B.2.4_1.3 Transmit OFF Power for Inter-band EN-DC including FR2 (5 CCs) | Same as 6.3A.2.3 in TS 38.521-2 [9] | | +| 6.3B.3.2 Tx ON/OFF time mask for intra-band non-contiguous EN-DC | Same as 6.3.3.2 in TS 38.521-1 [8] | | +| 6.3B.3.3 Tx ON/OFF time mask for inter-band EN-DC within FR1 | Same as 6.3.3.2 in TS 38.521-1 [8] | | +| 6.3B.3.4 Transmit ON/OFF time mask for inter-band EN-DC including FR2 | Same as 6.3.3.2 in TS 38.521-2 [9] | | +| 6.3B.3.4_1.1 Transmit ON/OFF time mask for inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.3A.3.1.1 in TS 38.521-2 [9] | | +| 6.3B.4.3 PRACH Time Mask for inter-band EN-DC within FR1 | Same as 6.3.3.4 in TS 38.521-1 [8] | | +| 6.3B.8.1.1 Absolute power tolerance for intra-band contiguous EN-DC | Same as 6.3.4.2 in TS 38.521-1 [8] | | +| 6.3B.8.1.2 Absolute power tolerance for intra-band non-contiguous EN-DC | Same as 6.3.4.2 in TS 38.521-1 [8] | | +| 6.3B.8.1.3 Absolute power tolerance for inter-band EN-DC within FR1 | Same as 6.3.4.2 in TS 38.521-1 [8] | | +| 6.3B.8.1.4 Absolute power tolerance for inter-band EN-DC including FR2 | Same as 6.3.4.2 in TS 38.521-2 [9] | | + +| | | | +|--------------------------------------------------------------------------|-------------------------------------|--| +| 6.3B.8.2.1 Relative power tolerance for intra-band contiguous EN-DC | Same as 6.3.4.3 in TS 38.521-1 [8] | | +| 6.3B.8.2.2 Relative power tolerance for intra-band non-contiguous EN-DC | Same as 6.3.4.3 in TS 38.521-1 [8] | | +| 6.3B.8.2.3 Relative power tolerance for inter-band EN-DC within FR1 | Same as 6.3.4.3 in TS 38.521-1 [8] | | +| 6.3B.8.2.4 Relative power tolerance for inter-band EN-DC including FR2 | Same as 6.3.4.3 in TS 38.521-2 [9] | | +| 6.3B.8.3.1 Aggregate power tolerance for intra-band contiguous EN-DC | Same as 6.3.4.4 in TS 38.521-1 [8] | | +| 6.3B.8.3.2 Aggregate power tolerance for intra-band non-contiguous EN-DC | Same as 6.3.4.4 in TS 38.521-1 [8] | | +| 6.3B.8.3.3 Aggregate power tolerance for inter-band EN-DC within FR1 | Same as 6.3.4.4 in TS 38.521-1 [8] | | +| 6.3B.8.3.4 Aggregate power tolerance for inter-band EN-DC including FR2 | Same as 6.3.4.4 in TS 38.521-2 [9] | | +| 6.4B.1.1 Frequency Error for intra-band contiguous EN-DC | Same as 6.4.1 in TS 38.521-1 [8] | | +| 6.4B.1.2 Frequency Error for intra-band non-contiguous EN-DC | Same as 6.4.1 in TS 38.521-1 [8] | | +| 6.4B.1.3 Frequency Error for inter-band EN-DC within FR1 | Same as 6.4.1 in TS 38.521-1 [8] | | +| 6.4B.1.4 Frequency Error for inter-band EN-DC including FR2 | Same as 6.4.1 in TS 38.521-2 [9] | | +| 6.4B.1.4_1.1 Frequency Error for Inter-band EN-DC including FR2 (3 CCs) | Same as 6.4A.1.1 in TS 38.521-2 [9] | | +| 6.4B.1.4_1.2 Frequency Error for Inter-band EN-DC including FR2 (4 CCs) | Same as 6.4A.1.2 in TS 38.521-2 [9] | | +| 6.4B.1.4_1.3 Frequency Error for Inter-band EN-DC including FR2 (5 CCs) | Same as 6.4A.1.3 in TS 38.521-2 [9] | | +| 6.4B.2.1.1 Error Vector Magnitude for intra-band contiguous EN-DC | Same as 6.4.2.1 in TS 38.521-1 [8] | | +| 6.4B.2.1.2 Carrier Leakage for intra-band contiguous EN-DC | Same as 6.4.2.2 in TS 38.521-1 [8] | | +| 6.4B.2.1.3 In-band Emissions for intra-band contiguous EN-DC | Same as 6.4.2.3 in TS 38.521-1 [8] | | +| 6.4B.2.1.4 EVM Equalizer Flatness for intra-band contiguous EN-DC | Same as 6.4.2.4 in TS 38.521-1 [8] | | +| 6.4B.2.2.1 Error Vector Magnitude for intra-band non-contiguous EN-DC | Same as 6.4.2.1 in TS 38.521-1 [8] | | +| 6.4B.2.2.2 Carrier Leakage for intra-band non-contiguous EN-DC | Same as 6.4.2.2 in TS 38.521-1 [8] | | +| 6.4B.2.2.3 In-band Emissions for intra-band non-contiguous EN-DC | Same as 6.4.2.3 in TS 38.521-1 [8] | | +| 6.4B.2.2.4 EVM Equalizer Flatness for intra-band non-contiguous EN-DC | Same as 6.4.2.4 in TS 38.521-1 [8] | | + +| | | | +|--------------------------------------------------------------------------------------------------------|---------------------------------------------|--| +| 6.4B.2.3.1 Error Vector Magnitude for inter-band EN-DC within FR1 | Same as 6.4.2.1 in TS 38.521-1 [8] | | +| 6.4B.2.3.2 Carrier Leakage for inter-band EN-DC within FR1 | Same as 6.4.2.2 in TS 38.521-1 [8] | | +| 6.4B.2.3.3 In-band Emissions for inter-band EN-DC within FR1 | Same as 6.4.2.3 in TS 38.521-1 [8] | | +| 6.4B.2.3.4 EVM Equalizer Flatness for inter-band EN-DC within FR1 | Same as 6.4.2.4 in TS 38.521-1 [8] | | +| 6.4B.2.4.1 Error Vector Magnitude for inter-band EN-DC including FR2 | Same as 6.4.2.1 in TS 38.521-2 [9] | | +| 6.4B.2.4.1a Error Vector Magnitude with Power Boost for inter-band EN-DC including FR2 (1 NR CC) | Same as clause 6.4.2.1_1 in TS 38.521-2 [9] | | +| 6.4B.2.4.2 Carrier Leakage for inter-band EN-DC including FR2 | Same as 6.4.2.2 in TS 38.521-2 [9] | | +| 6.4B.2.4.3 In-band Emissions for inter-band EN-DC including FR2 | Same as 6.4.2.3 in TS 38.521-2 [9] | | +| 6.4B.2.4.4 EVM Equalizer Flatness for inter-band EN-DC including FR2 | Same as 6.4.2.4 in TS 38.521-2 [9] | | +| 6.4B.2.4.5 EVM spectral flatness for pi/2 BPSK modulation for inter-band EN-DC including FR2 (1 NR CC) | Same as 6.4.2.5 in TS 38.521-2 [9] | | +| 6.5B.1.1 Occupied bandwidth for Intra-Band Contiguous EN-DC | Same as 6.5.1 in TS 38.521-1 [8] | | +| 6.5B.1.2 Occupied bandwidth for Intra-Band Non-Contiguous EN-DC | Same as 6.5.1 in TS 38.521-1 [8] | | +| 6.5B.1.3 Occupied bandwidth for Inter-Band EN-DC within FR1 | Same as 6.5.1 in TS 38.521-1 [8] | | +| 6.5B.1.4 Occupied bandwidth for Inter-Band EN-DC including FR2 | Same as 6.5.1 in TS 38.521-2 [9] | | +| 6.5B.1.4_1.1 Occupied bandwidth for Inter-band EN-DC including FR2 (3 CCs) | TBD | | +| 6.5B.1.4_1.2 Occupied bandwidth for Inter-band EN-DC including FR2 (4 CCs) | TBD | | +| 6.5B.1.4_1.3 Occupied bandwidth for Inter-band EN-DC including FR2 (5 CCs) | TBD | | +| 6.5B.1.4D Occupied bandwidth for inter-band EN-DC including FR2 for UL MIMO | Same as 6.5D.1 in TS 38.521-2 [9] | | +| 6.5B.2.1.1 Spectrum emissions mask for intra-band contiguous EN-DC | Same as 6.5.2.2 in TS 38.521-1 [8] | | +| 6.5B.2.1.2 Additional spectrum emissions mask for intra-band contiguous EN-DC | Same as 6.5.2.3 in TS 38.521-1 [8] | | +| 6.5B.2.1.3 Adjacent channel leakage ratio for intra-band contiguous EN-DC | Same as 6.5.2.4.1 in TS 38.521-1 [8] | | + +| | | | +|---------------------------------------------------------------------------------------------------|-----------------------------------------------|--| +| 6.5B.2.2.1 Spectrum emissions mask for intra-band non-contiguous EN-DC | Same as 6.5.2.2 in TS 38.521-1 [8] | | +| 6.5B.2.2.2 Additional Spectrum emissions mask for intra-band non-contiguous EN-DC | Same as 6.5.2.3 in TS 38.521-1 [8] | | +| 6.5B.2.2.3 Adjacent channel leakage ratio for intra-band non-contiguous EN-DC | Same as 6.5.2.4.1 in TS 38.521-1 [8] | | +| 6.5B.2.3.1 Spectrum emissions mask for Inter-band EN-DC within FR1 | Same as 6.5.2.2 in TS 38.521-1 [8] | | +| 6.5B.2.3.2 Additional Spectrum emissions mask for Inter-band EN-DC within FR1 | Same as 6.5.2.3 in TS 38.521-1 [8] | | +| 6.5B.2.3.3.1 NR - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) | Same as 6.5.2.4.1 in TS 38.521-1 [8] | | +| 6.5B.2.3.3.2 UTRA - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) | Same as 6.5.2.4.2 in TS 38.521-1 [8] | | +| 6.5B.2.4.1 Spectrum emissions mask for Inter-band EN-DC including FR2 | Same as 6.5.2.1 in TS 38.521-2 [9] | | +| 6.5B.2.4.1a Spectrum emissions mask with Power Boost for Inter-band EN-DC including FR2 (1 NR CC) | Same as clause 6.5.2.1.1_1 in TS 38.521-2 [9] | | +| 6.5B.2.4.1_1.1 Spectrum emissions mask for Inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.5A.2.1.1 in TS 38.521-2 [9] | | +| 6.5B.2.4.1_1.2 Spectrum emissions mask for Inter-band EN-DC including FR2 (3 NR CCs) | Same as clause 6.5A.2.1.2 in TS 38.521-2 [9] | | +| 6.5B.2.4.1_1.3 Spectrum emissions mask for Inter-band EN-DC including FR2 (4 NR CCs) | Same as clause 6.5A.2.3 in TS 38.521-2 [9] | | +| 6.5B.2.4.3 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 | Same as 6.5.2.3 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.1 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (3 CCs) | Same as clause 6.5A.2.2.1 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.2 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (4 CCs) | Same as clause 6.5A.2.2.2 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.3 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (5 CCs) | Same as clause 6.5A.2.2.3 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.4 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (5 NR CCs) | Same as clause 6.5A.2.2.4 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.5 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (6 NR CCs) | Same as clause 6.5A.2.2.5 in TS 38.521-2 [9] | | + +| | | | +|------------------------------------------------------------------------------------------------|----------------------------------------------|--| +| 6.5B.2.4.3_1.6 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (7 NR CCs) | Same as clause 6.5A.2.2.6 in TS 38.521-2 [9] | | +| 6.5B.2.4.3_1.7 Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (8 NR CCs) | Same as clause 6.5A.2.2.7 in TS 38.521-2 [9] | | +| 6.5B.3.1.1 General spurious emissions for intra-band contiguous EN-DC | Same as 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.1.2 Spurious emission band UE co-existence for intra-band contiguous EN-DC | Same as 6.5.3.2 in TS 38.521-1 [8] | | +| 6.5B.3.2.1 General spurious emissions for Intra-band non-contiguous EN-DC | Same as 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.2.2 Spurious Emission band UE co-existence for intra-band non-contiguous EN-DC | Same as 6.5.3.2 in TS 38.521-1 [8] | | +| 6.5B.3.3.1 General spurious emissions for Inter-band EN-DC within FR1 | Same as 6.5.3.1 in TS 38.521-1 [8] | | +| 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 | Same as 6.5.3.2 in TS 38.521-1 [8] | | +| 6.5B.3.4.1 General Spurious Emissions for Inter-band including FR2 (1 NR CC) | Same as 6.5.3.1 in TS 38.521-2 [9] | | +| 6.5B.3.4.1a General Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.1_1 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.1 General Spurious Emissions for Inter-band including FR2 (2 NR CCs) | Same as clause 6.5A.3.1.1 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.2 General Spurious Emissions for Inter-band including FR2 (3 NR CCs) | Same as clause 6.5A.3.1.2 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.3 General Spurious Emissions for Inter-band including FR2 (4 NR CCs) | Same as clause 6.5A.3.1.3 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.4 General Spurious Emissions for Inter-band including FR2 (5 NR CCs) | Same as clause 6.5A.3.1.4 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.5 General Spurious Emissions for Inter-band including FR2 (6 NR CCs) | Same as clause 6.5A.3.1.5 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.6 General Spurious Emissions for Inter-band including FR2 (7 NR CCs) | Same as clause 6.5A.3.1.6 in TS 38.521-2 [9] | | +| 6.5B.3.4.1_1.7 General Spurious Emissions for Inter-band including FR2 (8 NR CCs) | Same as clause 6.5A.3.1.7 in TS 38.521-2 [9] | | +| 6.5B.3.4.2 Spurious emission band UE co-existence for Inter-band including FR2 | Same as 6.5.3.2 in TS 38.521-2 [9] | | + +| | | | +|------------------------------------------------------------------------------------------------------------|----------------------------------------------|--| +| 6.5B.3.4.2a Spurious emission band UE co-existence with Power Boost for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.2_1 in TS 38.521-2 [9] | | +| 6.5B.3.4.2_1.1 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (2 NR CCs) | Same as clause 6.5A.3.2.1 in TS 38.521-2 [9] | | +| 6.5B.3.4.2_1.2 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (3 NR CCs) | Same as clause 6.5A.3.2.2 in TS 38.521-2 [9] | | +| 6.5B.3.4.2_1.3 Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (4 NR CCs) | Same as clause 6.5A.3.2.3 in TS 38.521-2 [9] | | +| 6.5B.4.1 Additional Spurious Emissions for Intra-band contiguous EN-DC | Same as clause 6.5.3.3 in TS 38.521-1 [8] | | +| 6.5B.4.2 Additional Spurious Emissions for Intra-band non-contiguous EN-DC | Same as clause 6.5.3.3 in TS 38.521-1 [8] | | +| 6.5B.4.3 Additional Spurious Emissions for Inter-band EN-DC within FR1 | Same as clause 6.5.3.3 in TS 38.521-1 [8] | | +| 6.5B.4.4 Additional Spurious Emissions for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.3 in TS 38.521-2 [9] | | +| 6.5B.4.4a Additional Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | Same as clause 6.5.3.3_1 in TS 38.521-2 [9] | | +| 6.5B.4.4_1.1 Additional Spurious Emissions for Inter-band including FR2 (2 NR CC) | Same as clause 6.5A.3.3.1 in TS 38.521-2 [9] | | +| 6.5B.4.4_1.2 Additional Spurious Emissions for Inter-band including FR2 (3 NR CC) | Same as clause 6.5A.3.3.2 in TS 38.521-2 [9] | | +| 6.5B.4.4_1.3 Additional Spurious Emissions for Inter-band including FR2 (4 NR CC) | Same as clause 6.5A.3.3.3 in TS 38.521-2 [9] | | +| 6.5B.5.3 Transmit intermodulation for Inter-band EN-DC within FR1 | Same as 6.5.4 in TS 38.521-1 [8] | | +| 6.6B.4 Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP | Same as clause 6.6.1 in TS 38.521-2 [9] | | +| 6.6B.5 Enhanced Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP | Same as clause 6.6.2 in TS 38.521-2 [9] | | + +### F.3.3 Measurement of receiver + +**Table F.3.3-1: Derivation of Test Requirements (Receiver tests)** + +| Sub clause | Test Tolerance (TT) | Formula for test requirement | +|---------------------------------------------------------------------------------|---------------------------------------|-------------------------------------| +| 7.3B.2.1 Reference sensitivity for Intra-band Contiguous EN-DC (2 CCs) | Same as 7.3.2 in TS 38.521-1 [8] | | +| 7.3B.2.2 Reference sensitivity for Intra-band non-contiguous EN-DC (2 CCs) | Same as 7.3.2 in TS 38.521-1 [8] | | +| 7.3B.2.3 Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs) | Same as 7.3.2 in TS 38.521-1 [8] | | +| 7.3B.2.3_1.1 Reference sensitivity for Inter-band EN-DC within FR1 (3 CCs) | Same as 7.3A.1 in TS 38.521-1 [8] | | +| 7.3B.2.4 Reference sensitivity for Inter-band EN-DC including FR2 | Same as 7.3.2 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.1 Reference sensitivity for Inter-band EN-DC including FR2 (3 CCs) | Same as 7.3A.2.1 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.2 Reference sensitivity for Inter-band EN-DC including FR2 (4 CCs) | Same as 7.3A.2.2 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.3 Reference sensitivity for Inter-band EN-DC including FR2 (5 CCs) | Same as 7.3A.2.3 in TS 38.521-2 [9] | | +| 7.3B.2.4_1.4 Reference sensitivity for Inter-band EN-DC including FR2 (6 CCs) | Same as 7.3A.2.4 in TS 38.521-2 [9] | | +| 7.3B.4 EIS Spherical Coverage for Inter-band EN-DC including FR2 | Same as 7.3.4 in TS 38.521-2 [9] | | +| 7.4B.1 Maximum Input Level for Intra-Band Contiguous EN-DC (2 CCs) | Same as 7.4 in TS 38.521-1 [8] | | +| 7.4B.2 Maximum Input Level for Intra-Band Non-Contiguous EN-DC (2 CCs) | Same as 7.4 in TS 38.521-1 [8] | | +| 7.4B.3 Maximum Input Level for Inter-band EN-DC within FR1 (2 CCs) | Same as 7.4 in TS 38.521-1 [8] | | +| 7.4B.3_1.1 Maximum Input Level for Inter-band EN-DC within FR1 (3 CCs) | Same as 7.4A.1 in TS 38.521-1 [8] | | +| 7.5B.1 Adjacent Channel Selectivity for intra-band contiguous EN-DC (2 CCs) | Same as 7.5 in TS 38.521-1 [8] | | +| 7.5B.2 Adjacent Channel Selectivity for intra-band non-contiguous EN-DC (2 CCs) | Same as 7.5 in TS 38.521-1 [8] | | +| 7.5B.3 Adjacent Channel Selectivity for inter-band EN-DC within FR1 (2 CCs) | Same as 7.5 in TS 38.521-1 [8] | | +| 7.5B.3_1.1 Adjacent Channel Selectivity for EN-DC within FR1 (3 CCs) | Same as 7.5A.1 in TS 38.521-1 [8] | | +| 7.5B.3_1.2 Adjacent Channel Selectivity for EN-DC within FR1 (4 CCs) | Same as 7.5 in TS 38.521-1 [8] | | +| 7.5B.4 Adjacent Channel Selectivity for inter-band EN-DC including FR2 (2CCs) | Same as clause 7.5 in TS 38.521-2 [9] | | +| 7.6B.2.1 Inband blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | Same as 7.6.2 in TS 38.521-1 [8] | | +| 7.6B.2.2 Inband blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as 7.6.2 in TS 38.521-1 [8] | | + +| | | | +|----------------------------------------------------------------------------------|----------------------------------|----------------------------------------------------------------------------------------| +| 7.6B.2.3 Inband blocking for inter-band EN-DC within FR1 (2 CCs) | Same as 7.6.2 in TS 38.521-1 [8] | | +| 7.6B.2.3_1.1 Inband blocking for EN-DC within FR1 (3 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.2.3_1.2 Inband blocking for EN-DC within FR1 (4 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.2.3_1.3 Inband blocking for EN-DC within FR1 (5 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.2.4 Inband blocking for inter-band EN-DC including FR2 (2 CCs) | Same as 7.6.2 in TS 38.521-2 [9] | | +| 7.6B.2.4_1.1 Inband blocking for inter-band EN-DC including FR2 (3 CCs) | 0 dB | Wanted signal power + TT
T-put limit unchanged | +| 7.6B.2.4_1.2 Inband blocking for inter-band EN-DC including FR2 (4 CCs) | 0 dB | Wanted signal power + TT
T-put limit unchanged | +| 7.6B.2.4_1.3 Inband blocking for inter-band EN-DC including FR2 (5 CCs) | 0 dB | Wanted signal power + TT
T-put limit unchanged | +| 7.6B.2.4_1.4 Inband blocking for inter-band EN-DC including FR2 (6 CCs) | 0 dB | Wanted signal power + TT
T-put limit unchanged | +| 7.6B.3.1 Out-of-band blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | Same as 7.6.3 in TS 38.521-1 [8] | | +| 7.6B.3.2 Out-of-band blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as 7.6.3 in TS 38.521-1 [8] | | +| 7.6B.3.3 Out-of-band blocking for inter-band EN-DC within FR1 (2 CCs) | Same as 7.6.3 in TS 38.521-1 [8] | | +| 7.6B.3.3_1.1 Out-of-band blocking for EN-DC within FR1 (3 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.3.3_1.2 Out-of-band blocking for EN-DC within FR1 (4 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.4.1 Narrow band blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | Same as 7.6.4 in TS 38.521-1 [8] | | +| 7.6B.4.2 Narrow band blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as 7.6.4 in TS 38.521-1 [8] | | +| 7.6B.4.3 Narrow band blocking for inter-band EN-DC within FR1 (2 CCs) | Same as 7.6.4 in TS 38.521-1 [8] | | +| 7.6B.4.3_1.1 Narrow band blocking for EN-DC within FR1 (3 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.4.3_1.2 Narrow band blocking for EN-DC within FR1 (4 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.4.3_1.3 Narrow band blocking for EN-DC within FR1 (5 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.7B.1 Spurious Response for intra-band contiguous EN-DC in FR1 (2 CCs) | Same as 7.7 in TS 38.521-1 [8] | | + +| | | | +|----------------------------------------------------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------| +| 7.7B.2 Spurious Response for intra-band non-contiguous EN-DC in FR1 (2 CCs) | Same as 7.7 in TS 38.521-1 [8] | | +| 7.7B.3 Spurious Response for inter-band EN-DC within FR1 (2 CCs) | Same as 7.7 in TS 38.521-1 [8] | | +| 7.6B.3.3_1.1 Out-of-band blocking for EN-DC within FR1 (3 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.6B.3.3_1.2 Out-of-band blocking for EN-DC within FR1 (4 CCs) | 0 dB | Wanted signal power + TT
Interferer signal power unchanged
T-put limit unchanged | +| 7.8B.2.1 Wideband Intermodulation for intra-band contiguous EN-DC in FR1 | Same as 7.8.2 in TS 38.521-1 [8] | | +| 7.8B.2.2 Wideband Intermodulation for intra-band non-contiguous EN-DC in FR1 | Same as 7.8.2 in TS 38.521-1 [8] | | +| 7.8B.2.3 Wideband Intermodulation for inter-band EN-DC in FR1 | Same as 7.8.2 in TS 38.521-1 [8] | | +| 7.8B.2.3_1.1 Wideband Intermodulation for EN-DC within FR1 (3 CCs) | Same as 7.8A.2.1 in TS 38.521-1 [8] | | +| 7.8B.2.3_1.2 Wideband Intermodulation for EN-DC within FR1 (4 CCs) | Same as 7.8A.2 in TS 38.521-1 [8] | | +| 7.8B.2.3_1.3 Wideband Intermodulation for EN-DC within FR1 (5 CCs) | Same as 7.8A.2 in TS 38.521-1 [8] | | +| 7.8B.2.3_1.4 Wideband Intermodulation for EN-DC within FR1 (6 CCs) | Same as 7.8A.2 in TS 38.521-1 [8] | | +| 7.9B.1 Spurious Emissions for intra-band contiguous EN-DC within FR1 (2 CCs) | Same as 7.9 in TS 38.521-1 [8] | | +| 7.9B.2 Spurious Emissions for intra-band non-contiguous EN-DC within FR1 (2 CCs) | Same as 7.9 in TS 38.521-1 [8] | | +| 7.9B.3 Spurious Emissions for inter-band EN-DC within FR1 (2 CCs) | Same as 7.9 in TS 38.521-1 [8] | | +| 7.9B.3_1.1 Spurious Emissions for EN-DC within FR1 (3 CCs) | Same as 7.9A.1 in TS 38.521-1 [8] | | +| 7.9B.4 Spurious Emissions for inter-band EN-DC including FR2 (2 CCs) | Same as 7.9 in TS 38.521-2 [9] | | + +## F.4 Uplink power window + +### F.4.1 Introduction + +A number of Tx and Rx Test cases set the UE uplink power to be within a defined window to ensure the test is carried out in the intended conditions. This clause gives the method for calculating the uplink power window used in Tx test cases and Rx Test cases. + +### F.4.2 Setting the power window above a requirement + +#### F.4.2.1 NR FR1 + +Information from the core requirements in TS 38.101-1 [2], TS 38.213 [19] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for $f \leq 3\text{GHz}$ and $BW \leq 40\text{MHz}$ and taking an example where the target value is 0dBm (lower end of a UE Core requirement side condition range of $0\text{ dBm} \leq \text{Output power} \leq 10\text{ dBm}$ ): + +![Diagram illustrating the 4 stages of setting the uplink power window above a requirement for NR FR1. The diagram shows the progression from the UE Core requirement (0dBm) through various uncertainty and step-size adjustments to the final Uplink power window (0dBm to +4.0dBm).](67c5b121b58d497a6de5addf4e7bd555_img.jpg) + +The diagram illustrates the process of setting the uplink power window above a requirement. It is divided into three main columns representing different stages of the process: + +- UE Core requirement on power control:** This column shows the initial requirement starting at 0dBm. It includes a "UE Core requirement side condition" at 0dBm. The "Uplink power control window, Measured value" is shown as a range from -1.7dBm to 0dBm. The "UE power step size" is 1.0dB, and the "UE Power step tolerance" is $\pm 0.7\text{dB}$ . +- Include effect of Test system uncertainty:** This column shows the addition of test system uncertainties. The "Test system relative power measurement uncertainty" is $\pm 0.7\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The "Test system absolute power measurement uncertainty at top of window" is $\pm 0.8\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The "Test system absolute power measurement uncertainty at bottom of window" is also $\pm 0.8\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The "Overall Uplink power window size" is calculated as $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.8\text{dB} + 0.8\text{dB}) = 4.0\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . +- Ensure that UE is not tested outside side condition:** This column shows the final "Uplink power window, actual value" as +0dBm to +4.0dBm for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The "Bottom of window is aligned to UL power requirement" at 0dBm. + +Diagram illustrating the 4 stages of setting the uplink power window above a requirement for NR FR1. The diagram shows the progression from the UE Core requirement (0dBm) through various uncertainty and step-size adjustments to the final Uplink power window (0dBm to +4.0dBm). + +##### UE Uplink power + +Figure F.4.2.1-1: Example NR FR1 uplink power setting to be above a requirement + +The smallest UE Power step size is defined in TS 38.213 [9] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [2] Table 6.3.4.3-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1\text{ dB}$ . + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.2.1-1. + +#### F.4.2.2 NR FR2 + +Information from the core requirements in TS 38.101-2 [3], TS 38.213 [19] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for FR2a and $P_{\text{UMAX}} \geq P > P_{\text{int}}$ and taking an example where the target value is $P_{\text{int}}$ : + +![Diagram illustrating the derivation of the uplink power window for NR FR2. It shows the progression from the UE core requirement on power control to the final uplink power window, accounting for test system uncertainties and power step sizes. The diagram includes labels for 'Uplink power control window, measured value', 'UE core requirement side condition P_int +10.4dBm', 'UE power step size 1.0dB', 'Test system absolute power measurement uncertainty at top of window: ±4.89 dB', 'Test system relative power measurement uncertainty: ±0.8 dB', 'Overall uplink power window size: (1dB+1dB+0.8dB+4.89dB+4.89dB) = 12.58dB', and 'Uplink power window, actual value: +0dB, +12.58dB'.](843c1635ec8d9d05abf22214cb262fb4_img.jpg) + +The diagram illustrates the derivation of the uplink power window for NR FR2. It shows the progression from the UE core requirement on power control to the final uplink power window, accounting for test system uncertainties and power step sizes. The diagram includes labels for 'Uplink power control window, measured value', 'UE core requirement side condition $P_{\text{int}} +10.4\text{dBm}$ ', 'UE power step size $1.0\text{dB}$ ', 'Test system absolute power measurement uncertainty at top of window: $\pm 4.89\text{ dB}$ ', 'Test system relative power measurement uncertainty: $\pm 0.8\text{ dB}$ ', 'Overall uplink power window size: $(1\text{dB}+1\text{dB}+0.8\text{dB}+4.89\text{dB}+4.89\text{dB}) = 12.58\text{dB}$ ', and 'Uplink power window, actual value: $+0\text{dB}, +12.58\text{dB}$ '. The bottom of the window is aligned to the UL power requirement $P_{\text{int}}$ . + +Diagram illustrating the derivation of the uplink power window for NR FR2. It shows the progression from the UE core requirement on power control to the final uplink power window, accounting for test system uncertainties and power step sizes. The diagram includes labels for 'Uplink power control window, measured value', 'UE core requirement side condition P\_int +10.4dBm', 'UE power step size 1.0dB', 'Test system absolute power measurement uncertainty at top of window: ±4.89 dB', 'Test system relative power measurement uncertainty: ±0.8 dB', 'Overall uplink power window size: (1dB+1dB+0.8dB+4.89dB+4.89dB) = 12.58dB', and 'Uplink power window, actual value: +0dB, +12.58dB'. + +UE uplink power + +UE uplink power setting for FR2a, $P_{\text{UMAX}} \geq P > P_{\text{int}}$ + +Figure F.4.2.2-1: Example NR FR2 uplink power setting to be above a requirement + +The smallest UE Power step size is defined in TS 38.213 [9] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-2 [3] Table 6.3.4.3-1 and Table 6.3.4.3-2, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, Guard Periods, and for a power step $\Delta P = 1\text{ dB}$ . + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.2.2-1. + +#### F.4.2.3 E-UTRA + +Information from the core requirements in TS 36.101 [5], TS 36.213 [20] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for $f \leq 3.0\text{GHz}$ and $BW \leq 40\text{MHz}$ and taking an example where the target value is 0dBm (lower end of a UE Core requirement side condition range of $0\text{dBm} \leq \text{Output power} \leq 10\text{dBm}$ ): + +![Diagram illustrating the E-UTRA uplink power setting process. It shows the derivation of the Uplink power window from the UE Core requirement (0dBm) through various tolerances and uncertainties. The final Uplink power window is +0dB to +4.3dB. The diagram includes labels for 'UE Core requirement on power control', 'Test system absolute power measurement uncertainty', 'Test system relative power measurement uncertainty', 'Uplink power control window, Measured value', 'UE Power step size 1.0dB', 'UE Power step tolerance ±1.0dB', 'Overall Uplink power window size', and 'Uplink power window, actual value'.](215e8d5e5ba38df215b55049d255b2ed_img.jpg) + +The diagram illustrates the calculation of the Uplink power window. The process starts with the UE Core requirement on power control (0dBm). The Uplink power control window, Measured value, is shown as a range of values around 0dB. The UE Power step size is 1.0dB, and the UE Power step tolerance is ±1.0dB. The Test system absolute power measurement uncertainty at the top of the window is ±0.8 dB, and at the bottom is ±0.8 dB. The Test system relative power measurement uncertainty is ±0.7 dB. The Overall Uplink power window size is calculated as (1dB + 1dB + 0.7dB + 0.8dB + 0.8dB) = 4.3dB for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The Uplink power window, actual value, is +0dB to +4.3dB for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The bottom of the window is aligned to the UL power requirement (0dBm). The diagram also includes a label 'UE Core requirement side condition' pointing to the 0dBm line. + +**UE Uplink power** + +Diagram illustrating the E-UTRA uplink power setting process. It shows the derivation of the Uplink power window from the UE Core requirement (0dBm) through various tolerances and uncertainties. The final Uplink power window is +0dB to +4.3dB. The diagram includes labels for 'UE Core requirement on power control', 'Test system absolute power measurement uncertainty', 'Test system relative power measurement uncertainty', 'Uplink power control window, Measured value', 'UE Power step size 1.0dB', 'UE Power step tolerance ±1.0dB', 'Overall Uplink power window size', and 'Uplink power window, actual value'. + +Figure F.4.2.3-1: Example E-UTRA uplink power setting to be above a requirement + +The smallest UE Power step size is defined in TS 36.213 [20] Table 5.1.1.1-2, for absolute $\delta_{\text{PUSCH}}$ . + +The UE Power step size tolerance is defined in TS 36.101 [5] Table 6.3.5.2.1-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1\text{ dB}$ . + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.2.3-1. + +### F.4.3 Setting the power window below a requirement + +#### F.4.3.1 NR FR1 + +Information from the core requirements in TS 38.101-1 [2], TS 38.213 [19] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for $f \leq 3\text{GHz}$ and $BW \leq 40\text{MHz}$ and taking an example where the target value is 4dB below $P_{\text{CMAX\_L}}$ (UE Core requirement side condition): + +![Diagram illustrating the 4 stages of setting the power window below a requirement for NR FR1. It shows the calculation of the uplink power window based on UE Core requirement side condition, UE Core requirement on power control, Test system absolute power measurement uncertainty, and Test system relative power measurement uncertainty.](d66f6b708b0f0f8717f85872afec0089_img.jpg) + +The diagram illustrates the process of setting the uplink power window for NR FR1. The vertical axis represents UE Uplink power, with a reference line for $P_{\text{CMAX\_L}}$ . The target value is set at $P_{\text{CMAX\_L}} - 4\text{dB}$ , which is the UE Core requirement side condition. The UE Core requirement on power control is shown as a range of power levels, with a 0dB reference and a -1.7dB level. The UE Power step tolerance is $\pm 0.7\text{dB}$ , and the UE power step size is $1.0\text{dB}$ . The Test system absolute power measurement uncertainty at the top of the window is $\pm 0.7\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The Test system relative power measurement uncertainty is $\pm 0.7\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The overall Uplink power window size is calculated as $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB}) = 3.8\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The top of the window is aligned to the UL power requirement. The Uplink power window, actual value, is $+0\text{dB}$ and $-3.8\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The bottom of the window is at $-3.8\text{dB}$ . The Test system absolute power measurement uncertainty at the bottom of the window is $\pm 0.7\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The diagram also includes a note: 'Ensure that UE is not tested outside side condition'. + +UE Core requirement side condition + +$P_{\text{CMAX\_L}}$ + +UE Core requirement on power control + +Include effect of Test system uncertainty + +Test system absolute power measurement uncertainty at top of window: $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ : $\pm 0.7\text{dB}$ + +Ensure that UE is not tested outside side condition + +Top of window is aligned to UL power requirement + +Uplink power control window, Measured value + +UE Power step tolerance $\pm 0.7\text{dB}$ + +0dB + +-1.7dB + +UE power step size $1.0\text{dB}$ + +Test system relative power measurement uncertainty: $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ : $\pm 0.7\text{dB}$ + +Overall Uplink power window size: $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB}) = 3.8\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ + +Uplink power window, actual value: $+0\text{dB}$ , $-3.8\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ + +Test system absolute power measurement uncertainty at bottom of window: $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ : $\pm 0.7\text{dB}$ + +UE Uplink power + +Diagram illustrating the 4 stages of setting the power window below a requirement for NR FR1. It shows the calculation of the uplink power window based on UE Core requirement side condition, UE Core requirement on power control, Test system absolute power measurement uncertainty, and Test system relative power measurement uncertainty. + +Figure F.4.3.1-1: Example NR FR1 uplink power setting to be below a requirement + +The smallest UE Power step size is defined in TS 38.213 [19] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [5] Table 6.3.4.3-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.3.1-1. + +#### F.4.3.2 NR FR2 + +Information from the core requirements in TS 38.101-2 [3], TS 38.213 [19] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for FR2a and $P_{\text{UMAX}} \geq P > P_{\text{int}}$ and taking an example where the target value is $P_{\text{UMAX}}$ : + +![Diagram illustrating the 4 stages of determining the UE uplink power window for NR FR2. The diagram shows the progression from the UE core requirement side condition (P_UMAX +21.65dBm) through power control steps, test system uncertainties, and final alignment to ensure the UE is not tested outside the core requirement side condition. The final uplink power window actual value is +0dB, -12.58dB.](2957154f4dc666a6cafb7b4d2d882910_img.jpg) + +The diagram illustrates the process of determining the UE uplink power window for NR FR2. It is divided into four main stages, each represented by a vertical column or section: + +- UE core requirement side condition:** The starting point is $P_{\text{UMAX}} +21.65\text{dBm}$ . A vertical line marks this requirement. +- UE core requirement on power control:** This section shows the power control process. It includes: + - UE power step tolerance $\pm 1.0\text{dB}$ . + - UE power step size $1.0\text{dB}$ . + - A power step of $-2.0\text{dB}$ is indicated. + - Arrows show the range of possible power levels. +- Include effect of test system uncertainty:** This section accounts for measurement uncertainties: + - Test system absolute power measurement uncertainty at top of window: $\pm 4.89\text{ dB}$ . + - Test system relative power measurement uncertainty: $\pm 0.8\text{ dB}$ . + - Test system absolute power measurement uncertainty at bottom of window: $\pm 4.89\text{ dB}$ . + - The overall uplink power window size is calculated as: $(1\text{dB} + 1\text{dB} + 0.8\text{dB} + 4.89\text{dB} + 4.89\text{dB}) = 12.58\text{dB}$ . +- Ensure that UE is not tested outside side condition:** The final stage shows the alignment of the window. + - The top of the window is aligned to the UL power requirement. + - The uplink power window, actual value, is $+0\text{dB}$ , $-12.58\text{dB}$ . + +The overall process results in an uplink power window that stays within the core requirements while accounting for power control steps and test system uncertainties. The final UE uplink power setting for FR2a, $P_{\text{UMAX}} \geq P > P_{\text{int}}$ , is shown as $+0\text{dB}$ and $-12.58\text{dB}$ . + +Diagram illustrating the 4 stages of determining the UE uplink power window for NR FR2. The diagram shows the progression from the UE core requirement side condition (P\_UMAX +21.65dBm) through power control steps, test system uncertainties, and final alignment to ensure the UE is not tested outside the core requirement side condition. The final uplink power window actual value is +0dB, -12.58dB. + +Figure F.4.3.2-1: Example NR FR2 uplink power setting to be below a requirement + +The smallest UE Power step size is defined in TS 38.213 [19] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [3] Table 6.3.4.3-1 and Table 6.3.4.3-2, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, Guard Periods, and for a power step $\Delta P = 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.3.2-1. + +#### F.4.3.3 E-UTRA + +Information from the core requirements in TS 36.101 [5], TS 36.213 [20] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for $f \leq 3.0\text{GHz}$ and $BW \leq 40\text{MHz}$ and taking an example where the target value is 4dB below PCMAX\_L (UE Core requirement side condition): + +![Diagram illustrating the E-UTRA uplink power setting process, showing the derivation of the uplink power window from the UE Core requirement side condition (PCMAX_L -4dB) through various tolerances and uncertainties.](0955cb376118079cebbd9e7b2eff2b05_img.jpg) + +The diagram illustrates the process of setting the UE uplink power to be below a requirement. It shows the derivation of the uplink power window from the UE Core requirement side condition (PCMAX\_L -4dB) through various tolerances and uncertainties. + +**UE Uplink power** + +**UE Core requirement side condition**: $P_{\text{CMAX\_L}}$ + +**UE Core requirement on power control**: $P_{\text{CMAX\_L}} - 4\text{dB}$ + +**Uplink power control window, Measured value**: The measured value is shown as a green dot at 0dB. + +**Test system absolute power measurement uncertainty at top of window**: $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ : $\pm 0.7\text{ dB}$ + +**Test system relative power measurement uncertainty**: $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ : $\pm 0.7\text{ dB}$ + +**Test system absolute power measurement uncertainty at bottom of window**: $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ : $\pm 0.7\text{ dB}$ + +**UE Power step tolerance**: $\pm 1.0\text{dB}$ + +**UE power step size**: $1.0\text{dB}$ + +**Overall Uplink power window size**: $(1\text{dB} + 1.0\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB}) = 4.1\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ + +**Ensure that UE is not tested outside side condition**: Top of window is aligned to UL power requirement + +**Uplink power window, actual value**: $+0\text{dB}$ , $-4.1\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ + +Diagram illustrating the E-UTRA uplink power setting process, showing the derivation of the uplink power window from the UE Core requirement side condition (PCMAX\_L -4dB) through various tolerances and uncertainties. + +Figure F.4.3.3-1: Example E-UTRA uplink power setting to be below a requirement + +The smallest UE Power step size is defined in TS 36.213 [20] Table 5.1.1.1-2, for absolute $\delta_{\text{PUSCH}}$ . + +The UE Power step size tolerance is defined in TS 36.101 [5] Table 6.3.5.2.1-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.3.3-1. + +### F.4.4 Setting the power window centred on a target value + +#### F.4.4.1 NR FR1 + +Information from the core requirements in TS 38.101-1 [2], TS 38.213 [19] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window centred on the target value. + +This process is shown in the diagram below, using values for $f \leq 3\text{GHz}$ and $BW \leq 40\text{MHz}$ and taking an example where the target value is $+10\text{dBm}$ : + +![Diagram illustrating the example NR FR1 uplink power setting centred on a target value. The diagram shows the derivation of the Uplink power control window from the UE Core requirement on power control, including test system uncertainties and power step sizes. The final window is centered on the UE Target value (10dBm).](9687bd5e8b62cadba093b0d1b70536cd_img.jpg) + +The diagram illustrates the process of setting the Uplink power control window for NR FR1. It starts with the **UE Core requirement on power control** and **UE Target value** (10dBm). The **Test system absolute power measurement uncertainty at top of window** is $\pm 0.8$ dB for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The **Test system relative power measurement uncertainty** is $\pm 0.7$ dB for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The **Overall Uplink power window size** is calculated as $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.8\text{dB} + 0.8\text{dB}) = 4.0\text{dB}$ for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The **UE Power step size** is $1.0$ dB. The **UE Power step tolerance** is $\pm 0.7$ dB. The **Test system absolute power measurement uncertainty at bottom of window** is $\pm 0.8$ dB for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The **Uplink power control window, Measured value** is shown as a range of values. The **Uplink power window, actual value** is $\pm 2.0$ dB for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The **Centre of window is aligned to UL power requirement**. + +Diagram illustrating the example NR FR1 uplink power setting centred on a target value. The diagram shows the derivation of the Uplink power control window from the UE Core requirement on power control, including test system uncertainties and power step sizes. The final window is centered on the UE Target value (10dBm). + +##### UE Uplink power + +Figure F.4.4.1-1: Example NR FR1 uplink power setting centred on a target value + +The smallest UE Power step size is defined in TS 38.213 [9] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [2] Table 6.3.4.3-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is centred on the target value, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.4.1-1. + +#### F.4.4.2 NR FR2 + +Information from the core requirements in TS 38.101-2 [3], TS 38.213 [19] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window centred on the target value. + +This process is shown in the diagram below, using values for FR2a and $P_{\text{UMAX}} \geq P > P_{\text{int}}$ and taking an example where the target value is +15dBm: + +![Diagram illustrating the calculation of the uplink power window for NR FR2. It shows the progression from the UE core requirement on power control to the final uplink power window, accounting for test system uncertainties and power step tolerances. The diagram includes labels for 'UE core requirement on power control', 'Include effect of test system uncertainty', and 'Ensure that UE power is centred on target value'. Key values shown include: UE target value +15dBm, Test system absolute power measurement uncertainty at top of window: ±4.89 dB, Test system relative power measurement uncertainty: ±0.8 dB, Overall uplink power window size: (1dB+1dB+0.8dB+4.89dB+4.89dB) = 12.58dB, Uplink power control window, measured value +15dBm, -2.0dB, UE power step size 1.0dB, UE power step tolerance ±1.0dB, Test system absolute power measurement uncertainty at bottom of window: ±4.89 dB, and Uplink power window, actual value: ±6.29dB. A note at the bottom right states 'Centre of window is aligned to UL power requirement'.](8d91c13d9c584af8129133d91ecb4bb9_img.jpg) + +Diagram illustrating the calculation of the uplink power window for NR FR2. It shows the progression from the UE core requirement on power control to the final uplink power window, accounting for test system uncertainties and power step tolerances. The diagram includes labels for 'UE core requirement on power control', 'Include effect of test system uncertainty', and 'Ensure that UE power is centred on target value'. Key values shown include: UE target value +15dBm, Test system absolute power measurement uncertainty at top of window: ±4.89 dB, Test system relative power measurement uncertainty: ±0.8 dB, Overall uplink power window size: (1dB+1dB+0.8dB+4.89dB+4.89dB) = 12.58dB, Uplink power control window, measured value +15dBm, -2.0dB, UE power step size 1.0dB, UE power step tolerance ±1.0dB, Test system absolute power measurement uncertainty at bottom of window: ±4.89 dB, and Uplink power window, actual value: ±6.29dB. A note at the bottom right states 'Centre of window is aligned to UL power requirement'. + +##### UE uplink power + +UE uplink power setting for FR2a, PUMAX ≥ P > Pint + +Figure F.4.4.2-1: Example NR FR2 uplink power setting centred on a target value + +The smallest UE Power step size is defined in TS 38.213 [9] Table 7.1.1-1, for absolute $\delta_{PUSCH,b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-2 [3] Table 6.3.4.3-1 and Table 6.3.4.3-2, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, Guard Periods, and for a power step $\Delta P = 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is centred on the target value, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.4.2-1. + +#### F.4.4.3 E-UTRA + +Information from the core requirements in TS 36.101 [5], TS 36.213 [20] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window centred on the target value. + +This process is shown in the diagram below, using values for $f \leq 3\text{GHz}$ and $BW \leq 40\text{MHz}$ and taking an example where the target value is -10dBm: + +![Diagram illustrating E-UTRA uplink power setting centered on a target value. It shows the relationship between UE Core requirement, Test system uncertainty, and the resulting Uplink power window. The measured value is -10dBm. The diagram includes labels for 'UE Core requirement on power control', 'Include effect of Test system uncertainty', and 'Ensure that UE power is centred on target value'. It also shows the calculation for the Overall Uplink power window size: (1dB+1dB+0.7dB+0.8dB+0.8dB) = 4.3dB for f ≤ 3.0GHz, BW ≤ 40MHz. The actual Uplink power window is ±2.15dB.](a680643d7564c58bfaae20cb643d5da7_img.jpg) + +The diagram illustrates the E-UTRA uplink power setting process. It shows a vertical scale with a measured value of -10dBm. The UE Core requirement on power control is shown as a dashed line. The Test system absolute power measurement uncertainty at the top of the window is $\pm 0.8$ dB for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The Test system relative power measurement uncertainty is $\pm 0.7$ dB for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The Overall Uplink power window size is calculated as $(1\text{dB}+1\text{dB}+0.7\text{dB}+0.8\text{dB}+0.8\text{dB}) = 4.3\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The Uplink power window, actual value, is $\pm 2.15\text{dB}$ for $f \leq 3.0\text{GHz}$ , $BW \leq 40\text{MHz}$ . The Centre of window is aligned to UL power requirement. The UE Power step size is 1.0dB, and the UE Power step tolerance is $\pm 1.0\text{dB}$ . + +Diagram illustrating E-UTRA uplink power setting centered on a target value. It shows the relationship between UE Core requirement, Test system uncertainty, and the resulting Uplink power window. The measured value is -10dBm. The diagram includes labels for 'UE Core requirement on power control', 'Include effect of Test system uncertainty', and 'Ensure that UE power is centred on target value'. It also shows the calculation for the Overall Uplink power window size: (1dB+1dB+0.7dB+0.8dB+0.8dB) = 4.3dB for f ≤ 3.0GHz, BW ≤ 40MHz. The actual Uplink power window is ±2.15dB. + +##### UE Uplink power + +Figure F.4.4.3-1: Example E-UTRA uplink power setting centred on a target value + +The smallest UE Power step size is defined in TS 36.213 [20] Table 5.1.1.1-2, for absolute $\delta_{\text{PUSCH}}$ . + +The UE Power step size tolerance is defined in TS 36.101 [5] Table 6.3.5.2.1-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is centred on the target value, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.4.3-1. + +# --- Annex G (normative): Uplink Physical Channels + +Please refer to Annex G in TS 38.521-1 [8] and TS 38.521-2 [9] for appropriate details as needed for test cases in this test specification. EN-DC exceptions will be added, + +# --- Annex H (normative): Statistical Testing + +Editor's Note: + +- Further investigate the technical details behind this statistical method to ensure that this is applicable for FR2 radiated test cases. + +## H.1 General + +This annex specifies mapping throughput to error ratio, pass fail limits and pass fail decision rules that are needed for measuring average throughput for a duration sufficient to achieve statistical significance for testing receiver characteristics. + +## H.2 Statistical testing of receiver characteristics + +### H.2.1 General + +The test of receiver characteristics is twofold. + +1. A signal or a combination of signals is offered to the RX port(s) of the receiver. +2. The ability of the receiver to demodulate /decode this signal is verified by measuring the throughput. + +In (2) is the statistical aspect of the test and is treated here. + +The minimum requirement for all receiver tests is >95% of the maximum throughput. + +All receiver tests are performed in static propagation conditions. No fading conditions are applied. + +### H.2.2 Mapping throughput to error ratio + +- a) The measured information bit throughput $R$ is defined as the sum (in kilobits) of the information bit payloads successfully received during the test interval, divided by the duration of the test interval (in seconds). +- b) In measurement practice the UE indicates successfully received information bit payload by signalling an ACK to the SS. +If payload is received, but damaged and cannot be decoded, the UE signals a NACK. +- c) Only the ACK and NACK signals, not the data bits received, are accessible to the SS. +The number of bits is known in the SS from knowledge of what payload was sent. +- d) For the reference measurement channel, applied for testing, the number of bits is different in different slots, however in a radio frame it is fixed during one test. +- e) The time in the measurement interval is composed of successfully received slots (ACK), unsuccessfully received slots (NACK) and no reception at all (DTX-slots). +- f) DTX-slots may occur regularly according the applicable reference measurement channel (regDTX). +In real live networks this is the time when other UEs are served. In TDD these are the UL and special slots. regDTX vary from test to test but are fixed within the test. +- g) Additional DTX-slots occur statistically when the UE is not responding ACK or NACK where it should. (statDTX) +This may happen when the UE was not expecting data or decided that the data were not intended for it. + +The pass / fail decision is done by observing the: + +- number of NACKs + +- number of ACKs and +- number of statDTXs (regDTX is implicitly known to the SS) + +The ratio $(\text{NACK} + \text{statDTX}) / (\text{NACK} + \text{statDTX} + \text{ACK})$ is the Error Ratio (ER). Taking into account the time consumed by the ACK, NACK, and DTX-TTIs (regular and statistical), ER can be mapped unambiguously to throughput for any single reference measurement channel test. + +### H.2.3 Design of the test + +The test is defined by the following design principles (see clause H.x, Theory...): + +1. The early decision concept is applied. +2. A second limit is introduced: Bad DUT factor $M > 1$ +3. To decide the test pass: + - Supplier risk is applied based on the Bad DUT quality + - To decide the test fail + - Customer Risk is applied based on the specified DUT quality + +The test is defined by the following parameters: + +1. Limit ER = 0.05 (Throughput limit = 95%) +2. Bad DUT factor $M = 1.5$ (selectivity) +3. Confidence level CL = 95% (for specified DUT and Bad DUT-quality) + +### H.2.4 Numerical definition of the pass fail limits + +**Table H.2.4-1: pass fail limits** + +| ne | ns p | ns f | ne | ns p | ns f | ne | ns p | ns f | ne | ns p | ns f | +|----|-----------------|-----------------|----|-----------------|-----------------|-----|-----------------|-----------------|--------------------|-----------------|-----------------| +| 0 | 67 | NA | 39 | 763 | 500 | 78 | 1366 | 1148 | 117 | 1951 | 1828 | +| 1 | 95 | NA | 40 | 778 | 516 | 79 | 1381 | 1166 | 118 | 1965 | 1845 | +| 2 | 119 | NA | 41 | 794 | 532 | 80 | 1396 | 1183 | 119 | 1980 | 1863 | +| 3 | 141 | NA | 42 | 810 | 548 | 81 | 1412 | 1200 | 120 | 1995 | 1881 | +| 4 | 162 | NA | 43 | 826 | 564 | 82 | 1427 | 1217 | 121 | 2010 | 1899 | +| 5 | 183 | NA | 44 | 842 | 580 | 83 | 1442 | 1234 | 122 | 2025 | 1916 | +| 6 | 202 | NA | 45 | 858 | 596 | 84 | 1457 | 1252 | 123 | 2039 | 1934 | +| 7 | 222 | NA | 46 | 873 | 612 | 85 | 1472 | 1269 | 124 | 2054 | 1952 | +| 8 | 241 | NA | 47 | 889 | 629 | 86 | 1487 | 1286 | 125 | 2069 | 1969 | +| 9 | 259 | NA | 48 | 905 | 645 | 87 | 1502 | 1303 | 126 | 2084 | 1987 | +| 10 | 278 | 76 | 49 | 920 | 661 | 88 | 1517 | 1321 | 127 | 2099 | 2005 | +| 11 | 296 | 88 | 50 | 936 | 678 | 89 | 1532 | 1338 | 128 | 2113 | 2023 | +| 12 | 314 | 100 | 51 | 952 | 694 | 90 | 1547 | 1355 | 129 | 2128 | 2040 | +| 13 | 332 | 113 | 52 | 967 | 711 | 91 | 1562 | 1373 | 130 | 2143 | 2058 | +| 14 | 349 | 126 | 53 | 983 | 727 | 92 | 1577 | 1390 | 131 | 2158 | 2076 | +| 15 | 367 | 140 | 54 | 998 | 744 | 93 | 1592 | 1407 | 132 | 2172 | 2094 | +| 16 | 384 | 153 | 55 | 1014 | 760 | 94 | 1607 | 1425 | 133 | 2187 | 2111 | +| 17 | 401 | 167 | 56 | 1029 | 777 | 95 | 1623 | 1442 | 134 | 2202 | 2129 | +| 18 | 418 | 181 | 57 | 1045 | 793 | 96 | 1637 | 1459 | 135 | 2217 | 2147 | +| 19 | 435 | 195 | 58 | 1060 | 810 | 97 | 1652 | 1477 | 136 | 2231 | 2165 | +| 20 | 452 | 209 | 59 | 1076 | 827 | 98 | 1667 | 1494 | 137 | 2246 | 2183 | +| 21 | 469 | 224 | 60 | 1091 | 844 | 99 | 1682 | 1512 | 138 | 2261 | 2201 | +| 22 | 486 | 238 | 61 | 1106 | 860 | 100 | 1697 | 1529 | 139 | 2275 | 2218 | +| 23 | 503 | 253 | 62 | 1122 | 877 | 101 | 1712 | 1547 | 140 | 2290 | 2236 | +| 24 | 519 | 268 | 63 | 1137 | 894 | 102 | 1727 | 1564 | 141 | 2305 | 2254 | +| 25 | 536 | 283 | 64 | 1153 | 911 | 103 | 1742 | 1582 | 142 | 2320 | 2272 | +| 26 | 552 | 298 | 65 | 1168 | 928 | 104 | 1757 | 1599 | 143 | 2334 | 2290 | +| 27 | 569 | 313 | 66 | 1183 | 944 | 105 | 1772 | 1617 | 144 | 2349 | 2308 | +| 28 | 585 | 328 | 67 | 1199 | 961 | 106 | 1787 | 1634 | 145 | 2364 | 2326 | +| 29 | 602 | 343 | 68 | 1214 | 978 | 107 | 1802 | 1652 | 146 | 2378 | 2344 | +| 30 | 618 | 359 | 69 | 1229 | 995 | 108 | 1817 | 1669 | 147 | 2393 | 2361 | +| 31 | 634 | 374 | 70 | 1244 | 1012 | 109 | 1832 | 1687 | 148 | 2408 | 2379 | +| 32 | 650 | 389 | 71 | 1260 | 1029 | 110 | 1847 | 1704 | 149 | 2422 | 2397 | +| 33 | 667 | 405 | 72 | 1275 | 1046 | 111 | 1861 | 1722 | 150 | 2437 | 2415 | +| 34 | 683 | 421 | 73 | 1290 | 1063 | 112 | 1876 | 1740 | 151 | 2452 | 2433 | +| 35 | 699 | 436 | 74 | 1305 | 1080 | 113 | 1891 | 1757 | 152 | 2466 | 2451 | +| 36 | 715 | 452 | 75 | 1321 | 1097 | 114 | 1906 | 1775 | 153*) | NA | 2469 | +| 37 | 731 | 468 | 76 | 1336 | 1114 | 115 | 1921 | 1793 | | | | +| 38 | 747 | 484 | 77 | 1351 | 1131 | 116 | 1936 | 1810 | *) note 2 in H.2.5 | | | + +NOTE 1: The first column is the number of errors (ne = number of NACK + statDTX) + +NOTE 2: The second column is the number of samples for the pass limit (nsp, ns=Number of Samples= number of NACK + statDTX + ACK) + +NOTE 3: The third column is the number of samples for the fail limit (nsf) + +### H.2.5 Pass fail decision rules + +The pass fail decision rules apply for a single test, comprising one component in the test vector. The over all Pass /Fail conditions are defined in clause H.2.6 and H.2A.6 + +Having observed 0 errors, pass the test at 67+ samples, otherwise continue + +Having observed 1 error, pass the test at 95+ otherwise continue + +Having observed 2 errors, pass the test at 119+ samples, fail the test at 2- samples, otherwise continue +Etc. etc. + +Having observed 151 errors, pass the test at 2452+ samples, fail the test at 2433- samples, otherwise continue + +Having observed 152 errors, pass the test at 2466+ samples, fail the test at 2451- samples. + +Where x+ means: x or more, x- means x or less + +NOTE 1: an ideal DUT passes after 67 samples. The maximum test time is 2466 samples. + +NOTE 2: It is allowed to deviate from the early decision concept by postponing the decision (pass/fail or continue). Postponing the decision to or beyond the end of Table H.2.4-1 requires a pass fail decision against the test limit: pass the DUT for $ER < 0.0618$ , otherwise fail. + +--- + +Annex I (normative): +Void + +# --- Annex J (normative): + +## Test applicability per permitted test method + +Please refer to Annex J in TS 38.521-1 [8] and 38.521-2 [9] for appropriate details as needed for test cases in this test specification. Exceptions for EN-DC may be added as needed. + +# --- Annex K (normative): EIRP, TRP, and EIS measurement procedures + +Please refer to Annex K in 38.521-2 [9] for appropriate details as needed for test cases in this test specification. +Exceptions for EN-DC may be added as needed. + +--- + +Annex L (normative): +Void + +# --- Annex M (normative): Dual uplink interferer + +UE is mandated to support operation in dual and triple uplink mode for EN-DC configuration in NR FR1 listed in Table 5.5B.2-1, Table 5.5B.3-1, and Table 5.5B.4.1-1 and indicated by column single uplink allowed, Table 7.3B.2.0.3.5.1-1, Table 7.3B.2.0.3.5.2-0, Table 7.3B.2.0.3.5.2-1 or NE-DC configuration in NR FR1 listed in Table 5.5B.4a.1-1 and indicated by column single uplink allowed if the intermodulation products caused by the dual uplink operation do not interfere with its own primary downlink transmission channel bandwidth. For intermodulation products falling into LTE secondary downlink channel bandwidth, UE single UL capability is not considered. + +Formula for determining if the EN-DC in NR FR1 configuration with dual uplink operation interferes with its own downlink reception. + +Interference bandwidth: $IBW = |a| * CBW1 + |b| * CBW2$ + +- $|a| + |b| = 2$ (or 3) +- CBW1 and CBW2 are the transmission bandwidth configurations of the UL channels + +Center frequency of IBW: $fIBW = |a * f1 + b * f2|$ + +- f1 and f2 are center frequency of the transmission bandwidth configurations of each UL channel + +The range of IMD 2 (or 3): $[fIBW - IBW/2, fIBW + IBW/2]$ + +NOTE 1: UE shall be able to apply operations which are configured by RRC reconfiguration and corresponding HARQ timing on the transmission bandwidth. + +NOTE 2: For identified difficult band combination, during two adjacent RRC reconfiguration, the changing of transmission bandwidth should not introduce IM2 and IM3, which will result in UE changing from 2Tx to 1Tx. Otherwise, UE behavior is not specified. + +For DC\_3A\_n3A intra-band non-contiguous EN-DC combination, only single switched UL is supported in Rel-15. + +For DC\_2A\_n2A, DC\_66A\_n66A intra-band non-contiguous EN-DC combination, only single switched UL is supported. + +# --- Annex N (normative): Modified MPR behaviour + +Editor's note: The *modifiedMPRbehavior* is given in the Annex H.1 of TS 38.101-3. + +## --- N.1 Indication of modified MPR behaviour + +This annex contains the definitions of the bits in the field *modifiedMPRbehavior* indicated in the IE RF-Parameters [13] by a UE supporting an MPR or A-MPR modified in a later release of this specification. *modifiedMPRbehavior* is indicated in TS 36.211 [13] by an 8-bit bitmap per NR band. + +**Table N.1-1: Definitions of the bits in the field *modifiedMPRbehavior*** + +| NR Band | Index of field
(bit number) | Definition
(description of the supported functionality if indicator set to one) | Notes | +|---------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| n41 | 0 (leftmost bit) | - EN-DC contiguous intraband MPR as defined in clause 6.2B.2.1 of 38.101-3 v15.5.0 | - This bit may be set to 1 by a UE supporting DC_(n)41AA UE EN-DC | +| | 1 | - EN-DC non-contiguous intraband MPR as defined in clause 6.2B.2.2 of 38.101-3 v15.5.0 | - This bit may be set to 1 by a UE supporting DC_41A_n41A EN-DC | +| | 2 | - EN-DC contiguous and non-contiguous intraband MPR and A-MPR as defined in 38.101-3 v16.4.0. If this bit is not set the UE uses Rel-15 MPR or A-MPR for EN-DC contiguous and non-contiguous intraband MPR and A-MPR | -This bit may be set to 1 by a UE supporting DC_(n)41AA or DC_41A_n41A EN-DC | +| n71 | 0 (leftmost bit) | - EN-DC contiguous intraband MPR as defined in clause 6.2B.2.1 of 38.101-3 v15.5.0 | - This bit may be set to 1 by a UE supporting DC_(n)71AA UE EN-DC | + +--- + +Annex O (informative): +Change history + +| Change history | | | | | | | | +|----------------|--------------------|-----------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-08 | RAN5#76 | R5-174710 | - | - | - | Draft skeleton | 0.0.1 | +| 2018-01 | RAN5#1-5G-NR Adhoc | R5-180086 | - | - | - | TP to add clause 6.2B.3.3 UE A-MPR intra-band EN-DC to 38.521-3 | 0.1.0 | +| 2018-01 | RAN5#1-5G-NR Adhoc | R5-180087 | - | - | - | TP to add clause 6.5B.2.1.2 Additional Spectrum emissions mask (contiguous sub-blocks) for intra-band EN-DC to 38.521-3 | 0.1.0 | +| 2018-02 | RAN5#78 | R5-181509 | - | - | - | Updated 38.521-3 for new Annex A Dual uplink interferer information | 0.2.0 | +| 2018-02 | RAN5#78 | R5-181690 | - | - | - | Updated 38.521-3 for channel bandwidth information | 0.2.0 | +| 2018-03 | RAN5#2-5G-NR Adhoc | R5-181760 | - | - | - | Draft TS 38.521-3 0.3.0 | 0.3.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182035 | - | - | - | 5G-NR Text Proposal to add spurious emissions test case to 38.521-3 | 0.4.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182016 | - | - | - | TP for new test case: 6.5B.2.1.3, Adjacent channel leakage ratio for intra-band contiguous EN-DC | 0.4.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182017 | - | - | - | TP to update clause 6.2B.3.1 UE A-MPR intra-band EN-DC to 38.521-3 | 0.4.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182018 | - | - | - | TP to update clause 6.5B.2.1.2 Additional spectrum emission mask to 38.521-3 | 0.4.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-181807 | - | - | - | Update to Operating bands of 38.521-3 | 0.4.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-181808 | - | - | - | Update to clause 3 and clause 4 of 38.521-3 | 0.4.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-181828 | - | - | - | Updated 38.521-3 for channel bandwidth information with new structure | 0.4.0 | +| 2018-07 | RAN5#79 | R5-183961 | - | - | - | 5G_FR1_EN_DC_RF_sensitivity_for_DC | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183962 | - | - | - | Introduction of TC 6.2B.1.3 for EN-DC | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183949 | - | - | - | Statistical Testing Annex for 38.521-3 | 0.5.0 | +| 2018-07 | RAN5#79 | R5-182995 | - | - | - | Corrections annex for EIRP and TRP metric definition in TS 38.521-3 | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183707 | - | - | - | TP for updating test case 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183708 | - | - | - | Updated clause 5.5B Configuration for DC to 38.521-3 | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183709 | - | - | - | TP to add Occupied BW EN-DC test case | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183710 | - | - | - | TP to add SEM EN-DC test case | 0.5.0 | +| 2018-07 | RAN5#79 | R5-183711 | - | - | - | TP to add ACLR EN-DC test case | 0.5.0 | +| 2018-09 | RAN5#80 | R5-185563 | - | - | - | FR2_StoreTxRxBeamPeakCoordinates_38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185520 | - | - | - | Addition of TRx MU and TT in TS 38.521-3 Annex | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185503 | - | - | - | Add Clause 7.5B.1 into TS 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185504 | - | - | - | Add Clause 7.5B.2 into TS 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185505 | - | - | - | Add Clause 7.5B.3 into TS 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184579 | - | - | - | Updated EN-DC configuration information in clause 5 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184580 | - | - | - | TIB value add for EN-DC band in 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184671 | - | - | - | Update of References in clause 2 of 38.521-3 spec | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184672 | - | - | - | Updates to Operating Bands in clause 5.2 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184737 | - | - | - | Dual uplink interferer updated to 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184737 | - | - | - | Dual uplink interferer updated to 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185332 | - | - | - | Addition of 6.2B.4.1.1 Configured OP for Intra-Band Contiguous EN-DC | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185333 | - | - | - | Addition of 6.2B.4.1.2 Configured OP for Intra-Band Non-Contiguous EN-DC | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185507 | - | - | - | Addition of 6.2B.4.1.3 Configured OP for Inter-Band within FR1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185198 | - | - | - | Addition of 6.2B.4.1.4 Configured OP for Inter-Band EN-DC including FR2 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185199 | - | - | - | Addition of 6.2B.4.1.5 Configured OP for Inter-Band EN-DC including both FR1 and FR2 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185469 | - | - | - | TP for updating test case 6.2B.3.1 UE AMR for Intra-band contiguous EN-DC | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185470 | - | - | - | TP for updating test case 6.2B.3.2 UE AMR for Intra-band non-contiguous EN-DC | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185200 | - | - | - | TP for updating test case 6.5B.2.1.2 Additional spectrum emission mask for intra-band contiguous EN-DC | 1.0.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| 2018-09 | RAN5#80 | R5-185556 | - | - | - | FR2 UE BeamlockInvoke 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185472 | - | - | - | Update of TC 6.2B.1.1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185473 | - | - | - | Introduction of TC 6.2B.1.2 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185474 | - | - | - | Update of 6.2B.1.3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185201 | - | - | - | Introduction of TC 7.4B.1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185202 | - | - | - | Introduction of 7.4B.2 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185203 | - | - | - | Introduction of 7.4B.3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185479 | - | - | - | Update Occupied Bandwidth for interband EN-DC within FR1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185480 | - | - | - | Update SEM interband EN-DC within FR1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185481 | - | - | - | Update ACLR for interband EN-DC within FR1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185204 | - | - | - | 5G NR_EN_DC with FR1_Text update for RX sensitivity | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185205 | - | - | - | 5G NR_EN_DC with FR1_Text proposal for TX Spurious emission | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185422 | - | - | - | Alignment of Annex numbering with core spec | 1.0.0 | +| 2018-09 | RAN5#80 | R5-184897 | - | - | - | Updates to Channel Arrangement clause in 38.521-3 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185206 | - | - | - | Addition of TC6.3B.1.1 Minimum Output power for intra-band contiguous EN-DC | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185207 | - | - | - | Addition of TC6.3B.1.2 Minimum output power for intra-band non-contiguous EN-DC | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185208 | - | - | - | Addition of TC6.3B.1.3 Minimum output power for inter-band EN-DC within FR1 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185351 | - | - | - | Update across EN-DC RF test cases in TS 38.521-3 | 1.0.0 | +| 2018-09 | RAN#81 | - | - | - | - | raised to v15.0.0 with editorial changes only | 15.0.0 | +| 2018-12 | RAN#82 | R5-186503 | 0033 | - | F | FR2 Spurious Emission test case updates | 15.1.0 | +| 2018-12 | RAN#82 | R5-186506 | 0034 | - | F | Update Text on Store Beam Peak Coordinate | 15.1.0 | +| 2018-12 | RAN#82 | R5-186507 | 0035 | - | F | 38.521-3 Applicability Rules | 15.1.0 | +| 2018-12 | RAN#82 | R5-186601 | 0039 | - | F | 5G NR_EN_DC with FR1_Text update for Intra-Band Contiguous RX sensitivity | 15.1.0 | +| 2018-12 | RAN#82 | R5-186602 | 0040 | - | F | 5G NR_Text update for TX spurious emission intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-186608 | 0042 | - | F | Spurious emission band UE co-existence for Inter-band EN-DC within FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186672 | 0044 | - | F | Updating test case 6.2B.3.1 Additional Maximum Output Power reduction for Intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-186673 | 0045 | - | F | Updating test case 6.5B.2.1.2 Additional spectrum emissions mask for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-186681 | 0046 | - | F | Updates to EN-DC test case 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-186684 | 0047 | - | F | Updates to test case 6.2B.2.3, UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186788 | 0049 | - | F | Minor update OBW, SEM and ACLR inter-band FR1 test cases | 15.1.0 | +| 2018-12 | RAN#82 | R5-187153 | 0061 | - | F | Updated EN-DC configuration information in clause 5 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187371 | 0076 | - | F | Addition of TC6.3B.2.1 Transmit OFF Power for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187372 | 0077 | - | F | Addition of TC6.3B.2.3 Transmit OFF Power for inter-band EN-DC within FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187373 | 0078 | - | F | Addition of TC6.3B.2.2 Transmit OFF Power for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187552 | 0083 | - | F | Updates to TS 38.521-3 common sections 1-4 to align with core spec | 15.1.0 | +| 2018-12 | RAN#82 | R5-187559 | 0084 | - | F | Updates to TS 38.521-3 clause 5 to align with core spec | 15.1.0 | +| 2018-12 | RAN#82 | R5-187562 | 0085 | - | F | Update to TC6.5B.3.2.1 - General Spurious Emissions for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187563 | 0086 | - | F | Update to 7.3B.2.2 - REFSENS for Intra-band Non-Contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187565 | 0087 | - | F | Updates to TS 38.521-3 clause 4 with LTE anchor details | 15.1.0 | +| 2018-12 | RAN#82 | R5-187614 | 0094 | - | F | Updates to EN-DC test case 6.2B.2.2, UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187816 | 0048 | 1 | F | Adding test case 6.2B.2.4, UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187819 | 0053 | 1 | F | Update general parameter Connection without release in initial conditions in TS 38.521-3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187820 | 0043 | 1 | F | Updates to test case 6.5B.2.1.3, Adjacent channel leakage ratio for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187821 | 0052 | 1 | F | Addition OBW intraband non contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187822 | 0055 | 1 | F | Introduction of New test case 6.4B.2.2.1 Error Vector Magnitude for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187823 | 0056 | 1 | F | Introduction of New test case 6.4B.2.2.2 Carrier Leakage for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187825 | 0058 | 1 | F | Introduction of New test case 6.4B.2.3.1 Error Vector Magnitude for inter-band EN-DC within FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187826 | 0059 | 1 | F | Introduction of New test case 6.4B.2.3.2 Carrier Leakage for inter-band EN-DC within FR1 | 15.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | RAN#82 | R5-187827 | 0060 | 1 | F | Introduction of New test case 6.4B.2.3.3 In-band Emissions for inter-band EN-DC within FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187828 | 0070 | 1 | F | Introduction of Error Vector Magnitude for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187829 | 0071 | 1 | F | Introduction of Carrier Leakage for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187831 | 0088 | 1 | F | FR2 General Spurious Emission test case update | 15.1.0 | +| 2018-12 | RAN#82 | R5-187832 | 0089 | 1 | F | FR2 Reference Sensitivity test case update | 15.1.0 | +| 2018-12 | RAN#82 | R5-187833 | 0092 | 1 | F | Updates to clause 7.3B.3.4 in TS 38.521-3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187834 | 0090 | 1 | F | Updates to sections 1-4 in TS 38.521-3 to align with core spec | 15.1.0 | +| 2018-12 | RAN#82 | R5-187835 | 0091 | 1 | F | Updates to Clause 5 in TS 38.521-3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187913 | 0067 | 1 | F | Addition of notes to clarify test point selection into general clause of TS 38.521-3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188012 | 0057 | 1 | F | Introduction of New test case 6.4B.2.2.3 In-band Emissions for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188013 | 0050 | 1 | F | Addition OBW intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188014 | 0051 | 1 | F | Addition SEM intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188015 | 0064 | 1 | F | Additional Spurious Emissions for Intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188016 | 0065 | 1 | F | Additional Spurious Emissions for Intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188017 | 0066 | 1 | F | Additional Spurious emission for inter-band EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188018 | 0068 | 1 | F | Spurious emission band UE co-existence for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188019 | 0072 | 1 | F | Introduction of In-band Emissions for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188020 | 0073 | 1 | F | Addition of TC6.3B.3.1 Tx ON/OFF time mask for intra-band contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188021 | 0074 | 1 | F | Addition of TC6.3B.3.2 Tx ON/OFF time mask for intra-band non-contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188022 | 0075 | 1 | F | Addition of TC6.3B.3.3 Tx ON/OFF time mask for inter-band EN-DC within FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188023 | 0080 | 1 | F | Update of test case 6.5B.2.1.2 Additional spectrum emission mask for intra-band contiguous EN-DC for NS_04 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188024 | 0081 | 1 | F | Update of test case 6.2B.3.1 UE A-MPR for Intra-band contiguous EN-DC for NS_04 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188025 | 0038 | 1 | F | Update Clause 7.5B.3 in TS 38.521-3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188026 | 0041 | 1 | F | 5G NR EN DC with FR1 Text update for Inter-Band RX sensitivity | 15.1.0 | +| 2018-12 | RAN#82 | R5-188027 | 0082 | 1 | F | Update TC 7.4B.3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188028 | 0036 | 1 | F | Updates of MU in TS 38.521-3 Annex F during RAN5#81 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188029 | 0037 | 1 | F | Updates of TT in TS 38.521-3 Annex F during RAN5#81 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188039 | 0093 | 1 | F | LTE Anchor Link configuration for FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188219 | 0062 | 1 | F | Introduction of receiver spurious emission tests for FR1 inter-band EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188220 | 0063 | 1 | F | Introduction of wideband intermodulation tests for FR1 inter-band EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188221 | 0054 | 1 | F | LTE TDD configuration for UE Tx test in EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-188222 | 0069 | 1 | F | Core alignment CR to capture TS 38.101-3 updates during RAN4#89 | 15.1.0 | +| 2019-03 | RAN#83 | R5-191057 | 0165 | - | F | Introduction of TC 7.5B.0 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191157 | 0174 | - | F | Updated EN-DC configuration information in clause 5 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191231 | 0175 | - | F | Adding missing reference to 38.521-3 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191336 | 0176 | - | F | Updates to EN-DC test case 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-191339 | 0177 | - | F | Updates to EN-DC test case 6.2B.2.2, UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-191340 | 0178 | - | F | Adding test case 6.5A.2.3, Adjacent channel leakage ratio for CA without EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-191510 | 0183 | - | F | Shared Risk clarification in TS 38.521-3 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191637 | 0193 | - | F | Updates of TT in TS 38.521-3 Annex F during RAN5#NR4 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191845 | 0200 | - | F | Text update for 7.3B.3 deltaRIB,c deltaRIBNC for EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-191867 | 0205 | - | F | Addition of 7.3B.2.0 Reference sensitivity Minimum Conformance Requirements for EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192004 | 0215 | - | F | Update of TC 6.2B.1.1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192005 | 0216 | - | F | Update of TC 6.2B.1.2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192006 | 0217 | - | F | Update of TC 6.2B.1.3 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192176 | 0224 | - | F | TIB,c updated for CA and EN-DC cases | 15.2.0 | +| 2019-03 | RAN#83 | R5-192177 | 0225 | - | F | Updated to Annex M Dual uplink interferer | 15.2.0 | +| 2019-03 | RAN#83 | R5-192206 | 0228 | - | F | 38.521-3 Common clause updates to clarify leverage across architecture options | 15.2.0 | +| 2019-03 | RAN#83 | R5-192207 | 0229 | - | F | Formatting updates and index correction in TS 38.521-3 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192208 | 0230 | - | F | 38.521-1 Common clause updates to clarify leverage across architecture options | 15.2.0 | +| 2019-03 | RAN#83 | R5-192209 | 0231 | - | F | 38.521-2 Common clause updates to clarify leverage across architecture options | 15.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | RAN#83 | R5-192242 | 0237 | - | F | Update of test case 6.2B.3.1 UE A-MPR for Intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192243 | 0238 | - | F | Update of test case 6.2B.3.4 UE A-MPR for Inter-Band EN-DC including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192244 | 0239 | - | F | Update of test case 6.5B.2.1.2 UE Additional spectrum emissions mask for intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192423 | 0157 | 1 | F | Update of TC 7.5B.1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192424 | 0159 | 1 | F | Introduction of TC 7.5B.4 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192425 | 0166 | 1 | F | Update of TC 7.5B.3 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192427 | 0180 | 1 | F | Introduction of NSA FR1 7.6B.2.1 Inband blocking for intra-band contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192428 | 0182 | 1 | F | Introduction of NSA FR1 7.6B.2.3 Inband blocking for inter-band EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192429 | 0184 | 1 | F | Introduction of NSA FR1 7.6B.3.1 Out-of-band blocking for intra-band contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192430 | 0185 | 1 | F | Introduction of NSA FR1 7.6B.3.2 Out-of-band blocking for intra-band non-contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192431 | 0186 | 1 | F | Introduction of NSA FR1 7.6B.3.3 Out-of-band blocking for inter-band EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192432 | 0187 | 1 | F | Introduction of NSA FR1 7.6B.4.1 Narrow band blocking for intra-band contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192433 | 0188 | 1 | F | Introduction of NSA FR1 7.6B.4.2 Narrow band blocking for intra-band non-contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192434 | 0189 | 1 | F | Introduction of NSA FR1 7.6B.4.3 Narrow band blocking for inter-band EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192435 | 0190 | 1 | F | Introduction of NSA FR1 7.7B.1 Spurious Response for intra-band contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192436 | 0191 | 1 | F | Introduction of NSA FR1 7.7B.2 Spurious Response for intra-band non-contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192437 | 0192 | 1 | F | Introduction of NSA FR1 7.7B.3 Spurious Response for inter-band EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192438 | 0207 | 1 | F | Text Update for 7.3B.2.2 Reference sensitivity for Intra-band non-contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192439 | 0234 | 1 | F | TS 38.521-3 corrections and clean-up to TC categories within Clause 7 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192440 | 0179 | 1 | F | Editorial: Band combinations for Inter-band CA between FR1 and FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192441 | 0232 | 1 | F | TS 38.521-3 clause 5 updates to align with core specification | 15.2.0 | +| 2019-03 | RAN#83 | R5-192442 | 0195 | 1 | F | Addition of TC6.3B.4.3 PRACH Time Mask for inter-band EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192443 | 0220 | 1 | F | Update of EN-DC 6.2B.4.1.3 Configured transmitted power inter-band within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192445 | 0233 | 1 | F | TS 38.521-3 corrections and clean-up to TC categories within Clause 6 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192453 | 0198 | 1 | F | FR2 NSA Spurious Emission Coexistence test case | 15.2.0 | +| 2019-03 | RAN#83 | R5-192454 | 0199 | 1 | F | FR2 NSA Frequency Error test case | 15.2.0 | +| 2019-03 | RAN#83 | R5-192455 | 0221 | 1 | F | Addition of transmit modulation quality test cases for inter-band EN-DC including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192456 | 0222 | 1 | F | Introduction 6.5B.1.4 OBW interband EN-DC including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192457 | 0223 | 1 | F | Introduction 6.5B.2.4.1 SEM interband EN-DC including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192458 | 0226 | 1 | F | Introduction 6.5B.2.4.3 ACLR interband EN-DC including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192459 | 0236 | 1 | F | Addition of TC6.3B.1.4 - Minimum Output Power for EN-DC Interband including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192535 | 0194 | 1 | F | Clean up of occupied bandwidth for EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192600 | 0196 | 1 | F | Addition of TC6.3B.4.1 PRACH Time Mask for intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192601 | 0197 | 1 | F | Addition of TC6.3B.4.2 PRACH Time Mask for intra-band non-contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192603 | 0201 | 1 | F | Text Update for 6.5B.3.2 Spurious Emissions for intra-band non-contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192604 | 0202 | 1 | F | Text Update for 6.5B.3.1 Spurious Emissions for intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192605 | 0203 | 1 | F | Text Update for 6.5B.3.3 Spurious Emissions for Inter-band EN-DC within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192606 | 0204 | 1 | F | Text Update for 6.5B.4 Additional Spurious Emissions for EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192607 | 0209 | 1 | F | Update to Carrier Leakage for intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192608 | 0210 | 1 | F | Introduction of Error Vector Magnitude for intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192609 | 0211 | 1 | F | Update to In-band Emissions for intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192610 | 0227 | 1 | F | Clarification on UL slots in OBW, SEM and ACLR in TS 38.521-3 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192611 | 0158 | 1 | F | Update of TC 7.5B.2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192617 | 0167 | 1 | F | Introducing Wideband Intermodulation for intra-band EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192618 | 0168 | 1 | F | Introducing receiver spurious emission for intra-band EN-DC in FR1 | 15.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | RAN#83 | R5-192619 | 0181 | 1 | F | Introduction of NSA FR1 7.6B.2.2 Inband blocking for intra-band non-contiguous EN-DC in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192620 | 0206 | 1 | F | Text Update for 7.3B.2.1 Reference sensitivity for Intra-band Contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192622 | 0170 | 1 | F | Updates of MU in TS 38.521-3 Annex F during RAN5#82 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192623 | 0171 | 1 | F | Updates of TT in TS 38.521-3 Annex F during RAN5#82 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192626 | 0214 | 1 | F | Update of TC 7.4B.2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192681 | 0235 | 1 | F | Addition of TC6.2B.1.4 - Max Output Power for EN-DC Interband including FR2 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192689 | 0218 | 1 | F | Update of 6.2B.4.1.1 Configured output power Intra-band contiguous EN-DC | 15.2.0 | +| 2019-03 | RAN#83 | R5-192690 | 0219 | 1 | F | Update of EN-DC 6.2B.4.1.2 Configured transmitted power Intra-band non-contiguous | 15.2.0 | +| 2019-03 | RAN#83 | R5-192844 | 0213 | 2 | F | Update of TC 7.4B.1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192847 | 0212 | 1 | F | Addition of 7.4B.0 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192863 | 0172 | 1 | F | Introduction of TxIM (inter-band EN-DC within FR1) | 15.2.0 | +| 2019-03 | RAN#83 | - | - | - | - | Editorial correction of references to TS 38.508-1 clause 4.6 tables | 15.2.0 | +| 2019-06 | RAN#84 | R5-193539 | 0294 | - | F | Adding missing reference in 38.521-3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193546 | 0295 | - | F | Updates to 6.2B.2.3, UE Maximum Output power reduction for inter-band EN-DC within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193547 | 0296 | - | F | Adding test case 6.2B.2.5, UE Maximum Output power reduction for inter-band EN-DC including both FR1 and FR2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193548 | 0297 | - | F | Update of test case 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193714 | 0309 | - | F | Update of Clause 5.5B Configuration for DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193719 | 0311 | - | F | Update of TC 7.5B.2 ACS for intra-band non-contiguous 2CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193720 | 0312 | - | F | Update of TC 7.5B.3 ACS for inter-band FR1 2CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193722 | 0314 | - | F | Update of TC 7.5B.4.1 ACS for inter-band FR2 2CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193724 | 0316 | - | F | Introduction of TC 7.5B.4.3 ACS for inter-band FR2 4CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193725 | 0317 | - | F | Introduction of TC 7.5B.4.4 ACS for inter-band FR2 5CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193726 | 0318 | - | F | Introduction of TC 7.5B.4.5 ACS for inter-band FR2 6CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193727 | 0319 | - | F | Introduction of TC 7.5B.5 inter-band FR1 FR2 3CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-193886 | 0320 | - | F | Introduction of NSA FR2 7.6B.2.4.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193888 | 0322 | - | F | Update of NSA FR1 7.6B.2.0 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193896 | 0324 | - | F | Update of NSA FR1 7.6B.2.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193899 | 0326 | - | F | Update of NSA FR1 7.6B.3.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193900 | 0327 | - | F | Update of NSA FR1 7.6B.3.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193901 | 0328 | - | F | Update of NSA FR1 7.6B.4.0 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193902 | 0329 | - | F | Update of NSA FR1 7.6B.4.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193903 | 0330 | - | F | Update of NSA FR1 7.6B.4.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193904 | 0331 | - | F | Update of NSA FR1 7.7B.0 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193905 | 0332 | - | F | Update of NSA FR1 7.7B.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193906 | 0333 | - | F | Update of NSA FR1 7.7B.2 | 15.3.0 | +| | | | | | | | | +| | | | | | | | | +| 2019-06 | RAN#84 | R5-193947 | 0343 | - | F | Removing invalid test IDs from test case 6.5B.2.1.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194016 | 0344 | - | F | 38.521-3 Annex re-alignment | 15.3.0 | +| | | | | | | | | +| 2019-06 | RAN#84 | R5-194128 | 0347 | - | F | Addition SEM intraband non-contiguous EN-DC in TS 38.521-3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194129 | 0348 | - | F | Addition ACLR intraband non-contiguous EN-DC in TS 38.521-3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194164 | 0351 | - | F | Update of test case 6.2B.3.1 UE A-MPR for Intra-band contiguous EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194166 | 0353 | - | F | Update of test case 6.2B.3.3 UE A-MPR for Inter-Band EN-DC within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194317 | 0359 | - | F | Text Update for 7.3B.2.3 Reference sensitivity for Inter-band EN-DC within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194318 | 0360 | - | F | Text Update for 7.3B.2.1 Ref sensitivity for Intra-band Contiguous EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194319 | 0361 | - | F | Text Update for 6.5B.4 Additional Spurious Emissions for EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194320 | 0362 | - | F | Text Update for 7.3B.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194374 | 0366 | - | F | Text Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band EN-DC within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194375 | 0367 | - | F | Text Update for 7.3B.2.2 Ref sensitivity for Intra-band Non-Contiguous EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194376 | 0368 | - | F | Text Update for 7.3B.2.0 Min Requirements of Ref sensitivity for EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194400 | 0372 | - | F | Update to Carrier Leakage and In-band Emissions for intra-band contiguous EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194463 | 0378 | - | F | Update to 6.2.3 A-MPR FR2 NSA | 15.3.0 | +| 2019-06 | RAN#84 | R5-194484 | 0380 | - | F | Update EN-DC Transmit modulation quality test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-194621 | 0381 | - | F | Update of transmit modulation quality test cases for inter-band EN-DC including FR2 | 15.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | R5-194706 | 0382 | - | F | TS 38.521-3 clause 5 updates to align with core specification | 15.3.0 | +| 2019-06 | RAN#84 | R5-194707 | 0383 | - | F | TS 38.521-3 updates across clause 6 test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-194708 | 0384 | - | F | TS 38.521-3 updates across clause 7 test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-194725 | 0388 | - | F | Update to clarify number of LTE CCs config for anchor agnostic EN-DC RF tests | 15.3.0 | +| 2019-06 | RAN#84 | R5-194934 | 0334 | 1 | F | Update of NSA FR1 RF 6.2B.1.1 MOP | 15.3.0 | +| 2019-06 | RAN#84 | R5-194935 | 0335 | 1 | F | Update of NSA FR1 RF 6.2B.1.2 MOP | 15.3.0 | +| 2019-06 | RAN#84 | R5-194936 | 0337 | 1 | F | Update of NSA FR1 RF 7.4B.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194937 | 0338 | 1 | F | Update of NSA FR1 RF 7.4B.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194938 | 0298 | 1 | F | Adding test case 6.5A.2.2, Additional Spectrum emissions mask for CA without EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194941 | 0350 | 1 | F | Introduction of New test case 6.4B.2.3.4 EVM Equalizer Flatness for inter-band EN-DC within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194942 | 0373 | 1 | F | Update of test case 6.2A.2.1, UE maximum output power reduction for inter-band NR CA between FR1 and FR2 without EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194943 | 0374 | 1 | F | Update of 6.2B.3.1 A-MPR Intra-band contiguous for NS_35 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194944 | 0375 | 1 | F | Update of 6.2B.3.2 A-MPR for Intra-band non-contiguous with additional test frequencies | 15.3.0 | +| 2019-06 | RAN#84 | R5-194945 | 0376 | 1 | F | Correction of editorial note in 6.5B.2.1.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194946 | 0377 | 1 | F | Update to 6.2.3 A-MPR FR1 and FR2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194947 | 0389 | 1 | F | Updates to E-UTRA, FR1,FR2 IW tests in line with agreed way forward | 15.3.0 | +| 2019-06 | RAN#84 | R5-194948 | 0369 | 1 | F | Addition of msg content in TC 6.3B.4.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194949 | 0370 | 1 | F | Addition of msg content in TC 6.3B.4.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194950 | 0371 | 1 | F | Addition of msg content in TC 6.3B.4.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194951 | 0310 | 1 | F | Update of TC 7.5B.0 ACS for EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-194952 | 0321 | 1 | F | Introduction of NSA FR2 7.6B.2.5 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194953 | 0323 | 1 | F | Update of NSA FR1 7.6B.2.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194954 | 0363 | 1 | F | Updated to EN-DC band and TIB information | 15.3.0 | +| 2019-06 | RAN#84 | R5-194955 | 0385 | 1 | F | TS 38.521-3 clause 5 updates to align with core specification | 15.3.0 | +| 2019-06 | RAN#84 | R5-194975 | 0315 | 1 | F | Introduction of TC 7.5B.4.2 ACS for inter-band FR2 3CC | 15.3.0 | +| 2019-06 | RAN#84 | R5-195046 | 0356 | 1 | F | Update to Wideband Intermodulation for EN-DC in FR1- 2CCs | 15.3.0 | +| 2019-06 | RAN#84 | R5-195047 | 0379 | 1 | F | Update to 6.2.3 A-MPR FR1 and FR2 NSA | 15.3.0 | +| 2019-06 | RAN#84 | R5-195049 | 0357 | 1 | F | Correction to 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195050 | 0358 | 1 | F | Introducing Wideband Intermodulation for EN-DC including FR1 - 3 CCs | 15.3.0 | +| 2019-06 | RAN#84 | R5-195051 | 0391 | - | F | Update of 6.5B.3.3.2 spurious co-existence inter-band EN-DC FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195091 | 0392 | 1 | F | Update of EN-DC ON ON time mask test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-195162 | 0349 | 1 | F | Introduction of New test case 6.4B.2.2.4 EVM Equalizer Flatness for intra-band non-contiguous EN-DC | 15.3.0 | +| 2019-06 | RAN#84 | R5-195163 | 0364 | 1 | F | Clean up FR2 Inter-band EN-DC test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-195164 | 0390 | 1 | F | Update to UE Maximum Output Power for Inter-Band EN-DC within FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195165 | 0325 | 1 | F | Update of NSA FR1 7.6B.3.0 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195411 | 0386 | 1 | F | TS 38.521-3 updates across clause 6 test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-195412 | 0387 | 1 | F | TS 38.521-3 updates across clause 7 test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-195419 | 0393 | 1 | F | EN-DC implementation of FR2 UL demod OTA tests using single pol Rx TE | 15.3.0 | +| 2019-06 | RAN#84 | R5-195436 | 0336 | 1 | F | Update of NSA FR1 RF 6.2B.1.3 MOP | 15.3.0 | +| 2019-06 | RAN#84 | R5-195437 | 0299 | 1 | F | Updates of MU and TT in TS 38.521-3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195446 | 0394 | 1 | F | Introduction of Tx test cases for FR2 NSA UL CA | 15.3.0 | +| 2019-06 | RAN#84 | R5-193922 | 0340 | - | F | Update of 6.2B.1.3 MOP inter-band adding Rel-16 EN-DC configurations | 16.0.0 | +| 2019-06 | RAN#84 | R5-193923 | 0341 | - | F | Update of 7.3B.2.3 REFSENS inter-band adding Rel-16 EN-DC configurations | 16.0.0 | +| 2019-06 | RAN#84 | R5-194059 | 0345 | - | F | Update of general sections adding Rel-16 EN-DC configurations, Editorial | 16.0.0 | +| 2019-06 | RAN#84 | R5-195054 | 0342 | 1 | F | Update of 6.5B.3.3.2 spurious co-existence inter-band adding Rel-16 EN-DC configurations | 16.0.0 | +| 2019-09 | RAN#85 | R5-197441 | 0397 | 1 | F | Correction of test case numbering for UL CA | 16.1.0 | +| 2019-09 | RAN#85 | R5-197346 | 0398 | 1 | F | Update of UE A_MPR intra band contiguous EN DC test case in 6.2B.3.1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197347 | 0399 | 1 | F | Update of UE A_MPR intra band non contiguous EN DC test case in 6.2B.3.2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197348 | 0401 | 1 | F | Addition of test case 6.5B.2.1.2 Additional Spectrum emissions mask for intra band contiguous EN DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197349 | 0402 | 1 | F | Addition of test case 6.5B.2.2.2 Additional Spectrum emissions mask for intra band non contiguous EN DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197350 | 0403 | 1 | F | Addition of test case 6.5B.2.3.2 Additional Spectrum emissions mask for Inter band EN DC within FR1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197561 | 0404 | 1 | F | Refsens test case updates | 16.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------|--------| +| 2019-09 | RAN#85 | R5-197351 | 0405 | 1 | F | Spurious test case updates | 16.1.0 | +| 2019-09 | RAN#85 | R5-197331 | 0406 | 1 | F | Correction to ACLR inter-band EN-DC FR1 test case | 16.1.0 | +| 2019-09 | RAN#85 | R5-196160 | 0407 | - | F | Clean up test cases 6.4B.2.2 Transmit Modulation Quality | 16.1.0 | +| 2019-09 | RAN#85 | R5-196161 | 0408 | - | F | Update to Annex F for Tx modulation quality test cases | 16.1.0 | +| 2019-09 | RAN#85 | R5-196200 | 0409 | - | F | Correction of uplink power setting for NSA transmitter test cases | 16.1.0 | +| 2019-09 | RAN#85 | R5-197516 | 0410 | 1 | F | Correction of uplink power setting for NSA receiver test cases | 16.1.0 | +| 2019-09 | RAN#85 | R5-196241 | 0411 | - | F | Correction to FR1 Transmit OFF Power | 16.1.0 | +| 2019-09 | RAN#85 | R5-197646 | 0412 | 1 | F | Correction to NR power control in FR1 Out-of-band blocking | 16.1.0 | +| 2019-09 | RAN#85 | R5-197352 | 0414 | 1 | F | Correction to FR1 PRACH time mask for EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197353 | 0415 | 1 | F | Correction of NR uplink RB allocation for FR1 Inter-Band EN-DC MOP | 16.1.0 | +| 2019-09 | RAN#85 | R5-196290 | 0416 | - | F | Add Annex F.4 Uplink Power window explanation for interworking test cases | 16.1.0 | +| 2019-09 | RAN#85 | R5-196296 | 0417 | - | F | Addition of Clause 7.5A in TS 38.521-3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197549 | 0418 | 1 | F | Update of 6.2B.1.1 MOP for Intra-band contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197550 | 0419 | 1 | F | Update of 6.2B.1.2 MOP for Intra-band non-contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-196446 | 0421 | - | F | Editorial update of general sections adding Rel-16 EN-DC configurations | 16.1.0 | +| 2019-09 | RAN#85 | R5-196449 | 0422 | - | F | Correction to description of Table 4.5.1-2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197354 | 0423 | 1 | F | Update for 6.5B.3.1.2 Spurious emission band UE co-existence for intra-band contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197553 | 0424 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197333 | 0425 | 1 | F | Update for 7.3B.2.0 Minimum Conformance Requirements of Reference sensitivity for EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197636 | 0426 | 2 | F | Update for 7.3B.2.3 Ref sensitivity for Inter-band EN-DC within FR1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197359 | 0427 | 1 | F | Update for 7.3B.2.1 Reference sensitivity for Intra-band Contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197334 | 0428 | 1 | F | Update for 7.3B.3.2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197335 | 0429 | 1 | F | Update for 7.3B.3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197337 | 0430 | 1 | F | Update for 7.3B.3.3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197338 | 0431 | 1 | F | Updated to EN-DC band information | 16.1.0 | +| 2019-09 | RAN#85 | R5-197336 | 0433 | 1 | F | Update of TCs in 7.6B and 7.7B | 16.1.0 | +| 2019-09 | RAN#85 | R5-197554 | 0434 | 1 | F | Updates to 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197555 | 0435 | 1 | F | Update of TC 6.3B.1.1 Minimum Output Power for intra-band contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197556 | 0436 | 1 | F | Update of TC 6.3B.1.2 Minimum output power for intra-band non-contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197340 | 0437 | 1 | F | Update of TC 6.3B.2.1 Transmit OFF Power for intra-band contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197341 | 0438 | 1 | F | Update of TC 6.3B.2.2 Transmit OFF Power for intra-band non-contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197342 | 0440 | 1 | F | Update of TC 6.4B.1.1 Frequency error for Intra-band contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197557 | 0441 | 1 | F | Update of TC 6.4B.1.2 Frequency error for Intra-band non-contiguous EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-197343 | 0442 | 1 | F | Update of TC 6.4B.1.3 Frequency error for Inter-band EN-DC within FR1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197647 | 0443 | 1 | F | Correction to 7.8B.2.6 Wideband Intermodulation for EN-DC including FR1 - 3 CCs | 16.1.0 | +| 2019-09 | RAN#85 | R5-197562 | 0448 | 1 | F | Corrections to Reference sensitivity for EN-DC | 16.1.0 | +| 2019-09 | RAN#85 | R5-196842 | 0449 | - | F | Editorial corrections to Additional Spurious Emission test case | 16.1.0 | +| 2019-09 | RAN#85 | R5-197360 | 0450 | 1 | F | Correction to test case 7.4B.3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197558 | 0452 | 1 | F | Correction to EN-DC Spurious Emissions | 16.1.0 | +| 2019-09 | RAN#85 | R5-197345 | 0456 | 1 | F | Update OBW EN-DC FR2 test case | 16.1.0 | +| 2019-09 | RAN#85 | R5-197339 | 0457 | 1 | F | TS 38.521-3 Section 5 updates to align with core specification (Covered by CR0431R1) | 16.1.0 | +| 2019-09 | RAN#85 | R5-197542 | 0458 | 1 | F | TS 38.521-3 updates across section 6 test cases | 16.1.0 | +| 2019-09 | RAN#85 | R5-197563 | 0459 | 1 | F | TS 38.521-3 updates across section 7 test cases | 16.1.0 | +| 2019-09 | RAN#85 | R5-197559 | 0460 | 1 | F | Updates to 6.2B.2.4, UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-196946 | 0461 | - | F | Corrections on UE maximum output power for DC in 38.521-3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197332 | 0462 | 1 | F | Corrections on Minimum conformance requirements of A-MPR in 38.521-3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-196948 | 0463 | - | F | Corrections on clause 5 in 38.521-3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-196949 | 0464 | - | F | Corrections on clause 2-4 in 38.521-3 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197633 | 0465 | - | F | Removing test points for CP-OFDM PI/2 BPSK in test case 6.5B.2.1.1 | 16.1.0 | +| 2019-12 | RAN#86 | R5-197940 | 0472 | - | F | Addition of 6.2B.1.5 MOP for Inter-Band EN-DC including FR1 and FR2 | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------|--------| +| 2019-12 | RAN#86 | R5-197944 | 0475 | - | F | Update of 6.2B.4.1.4 configured transmitted power for Inter-Band EN-DC including FR2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-197945 | 0476 | - | F | Update of 6.2B.4.1.5 configured transmitted power for Inter-Band EN-DC including FR1 and FR2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-197946 | 0477 | - | F | Addition of 7.4A Maximum Input Level for FR1-FR2 CA | 16.2.0 | +| 2019-12 | RAN#86 | R5-197949 | 0480 | - | F | Addition of 7.4B.5 Maximum Input Level for inter-band EN-DC including FR1 and FR2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198045 | 0485 | - | F | Update of TC 7.5B.0 ACS for EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-198046 | 0486 | - | F | Update of TC 7.5B.1 ACS for intra-band contiguous EN-DC 2CCs | 16.2.0 | +| 2019-12 | RAN#86 | R5-198172 | 0488 | - | F | Updating incorrect note in test procedure | 16.2.0 | +| 2019-12 | RAN#86 | R5-198280 | 0490 | - | F | Introduction of New TC 6.4B.2.1.4 EVM Equalizer Flatness for intra-band contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-198403 | 0501 | - | F | Correction to TC 6.4B.1.3 test description | 16.2.0 | +| 2019-12 | RAN#86 | R5-198404 | 0502 | - | F | Correction to Additional Spurious Emissions for Inter-band EN-DC within FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198406 | 0504 | - | F | Correction to Spurious emission band UE co-existence for Inter-band within FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198537 | 0509 | - | F | Updates to 6.2B.3.1, UE A-MPR for Intra-band Contig EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-198538 | 0510 | - | F | Updates to 6.2B.3.2, UE A-MPR for Intra-band Non-Contig EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-198539 | 0511 | - | F | Updates to 6.5B.2.1.2, Additional spectrum emission mask for intra-band Contig EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-198559 | 0512 | - | F | Updated to EN-DC band information Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198637 | 0513 | - | F | Updated to EN-DC General clause and band information Rel-15 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198685 | 0515 | - | F | Update single allowed info and MPR test description to EN-DC configuration in 38.521-3 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198686 | 0516 | - | F | Corrections on delta TIB for EN-DC configurations in 38.521-3 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198722 | 0519 | - | F | Update for 7.3B.1 General | 16.2.0 | +| 2019-12 | RAN#86 | R5-198734 | 0523 | - | F | Update for 6.5B.3.3.1 General spurious emissions for Inter-band EN-DC within FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198735 | 0524 | - | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199088 | 0466 | 1 | F | Updates of MU and TT in TS 38.521-3 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199342 | 0483 | 1 | F | Updates to test case 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199343 | 0487 | 1 | F | Editorial correction of test description in TC 6.4B.2.3.3 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199344 | 0478 | 1 | F | Addition of 7.4B.3 Maximum Input Level for inter-band EN-DC within FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199345 | 0491 | 1 | F | Update of minimum conformance requirements of 7.6B.3 and editorial correction in 7.6B and 7.7B | 16.2.0 | +| 2019-12 | RAN#86 | R5-199346 | 0492 | 1 | F | Addition of 7.6A Blocking Characteristics for CA | 16.2.0 | +| 2019-12 | RAN#86 | R5-199347 | 0493 | 1 | F | Addition of 7.6B.2.3_1 Inband blocking for EN-DC within FR1 (>2 CCs) | 16.2.0 | +| 2019-12 | RAN#86 | R5-199348 | 0495 | 1 | F | Addition of 7.6B.4.3_1 Narrow band blocking for EN-DC within FR1 (>2 CCs) | 16.2.0 | +| 2019-12 | RAN#86 | R5-199349 | 0468 | 1 | F | Add Uplink Power window explanation when centred on a target | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2019-12 | RAN#86 | R5-199350 | 0489 | 1 | F | Correction and addition of uplink power measurement MUs for NSA FR1 TCs | 16.2.0 | +| 2019-12 | RAN#86 | R5-199351 | 0508 | 1 | F | Addition of MU and TT for NSA 7.6B.2.3_1, 7.6B.2.4, 7.6B.2.4_1 and 7.6B.4.3_1 TCs in F.1.3 and F.3.3 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199352 | 0529 | 1 | F | TS 38.521-3 Section 1-5 and Annex updates to align with core specification | 16.2.0 | +| 2019-12 | RAN#86 | R5-199377 | 0471 | 1 | F | Update of 6.2B.1.4 MOP for Inter-Band EN-DC including FR2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199378 | 0479 | 1 | F | Addition of 7.4B.4 Maximum Input Level for inter-band EN-DC including FR2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199413 | 0482 | 1 | F | Addition of 2A-7A-7A-66A_n66A | 16.2.0 | +| 2019-12 | RAN#86 | R5-199498 | 0500 | 1 | F | Correction to minimum output power for intra-band EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199506 | 0496 | 1 | F | Removal of 7.7A Spurious Response for CA | 16.2.0 | +| 2019-12 | RAN#86 | R5-199508 | 0484 | 1 | F | Updates to test case 6.2B.2.2, UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199514 | 0469 | 1 | F | Update of 6.2B.1.1 MOP for Intra-Band contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199518 | 0467 | 1 | F | Updates of test procedure for MOP and co-existence tests | 16.2.0 | +| 2019-12 | RAN#86 | R5-199519 | 0517 | 1 | F | Update for 6.5B.3.1.1 General spurious emissions for intra-band contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199520 | 0518 | 1 | F | Update for 6.5B.3.2.1 General spurious emissions for Intra-band non-contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199521 | 0527 | 1 | F | Update for Additional Spurious Emissions for Intra-band contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199522 | 0530 | 1 | F | TS 38.521-3 updates across section 6 test cases | 16.2.0 | +| 2019-12 | RAN#86 | R5-199523 | 0526 | 1 | F | Update for 7.3B.2.0 Minimum Conformance Requirements of Reference sensitivity for EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199524 | 0531 | 1 | F | TS 38.521-3 updates across section 7 test cases | 16.2.0 | +| 2019-12 | RAN#86 | R5-199543 | 0520 | 1 | F | Correction of E-UTRA Mid channel bandwidth | 16.2.0 | +| 2019-12 | RAN#86 | R5-199546 | 0498 | 1 | F | Corrections to DC Config and dual UL interferer | 16.2.0 | +| 2019-12 | RAN#86 | R5-199547 | 0499 | 1 | F | Corrections to EN-DC and NE-DC Configurations | 16.2.0 | +| 2019-12 | RAN#86 | R5-199566 | 0494 | 1 | F | Addition of 7.6B.2.4_1 Inband blocking for inter-band EN-DC including FR2 (>2 CCs) | 16.2.0 | +| 2019-12 | RAN#86 | R5-199567 | 0522 | 1 | F | Update to test case 7.3B.2.3 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199568 | 0525 | 1 | F | Update for 7.3B.2.3 Reference sensitivity for Inter-band EN-DC within FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199569 | 0528 | 1 | F | Update 4.5 Applicability and test coverage rules | 16.2.0 | +| 2020-03 | RAN#87 | R5-200351 | 0538 | - | F | Updated to EN-DC band information Rel-16 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200446 | 0549 | - | F | Correction to FR1 EN-DC Spurious Test Case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200448 | 0551 | - | F | Correction to LTE specialSubframePatterns in Maximum Output Power Test Case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200449 | 0552 | - | F | Correction to tdm-PatternConfig in FR1 EN-DC Maximum Output Power Test Case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200599 | 0553 | - | F | Update of 6.2B.1.3 on inter-band EN-DC MOP in 38.521-3 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200651 | 0558 | - | F | Updates to 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| 2020-03 | RAN#87 | R5-200653 | 0559 | - | F | Updates to 6.2B.2.2, UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200657 | 0560 | - | F | Updates to 6.2B.2.3 and 6.2B.3.3 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200668 | 0561 | - | F | Correction of reference clause for 7.3B.2.3 Reference Sensitivity Test Procedure | 16.3.0 | +| 2020-03 | RAN#87 | R5-200670 | 0563 | - | F | Update reference in Test Requirement section of 6.5B.4.3.5 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200728 | 0568 | - | F | Correction of test cases in 7.6B.2 Inband blocking for DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200730 | 0569 | - | F | Correction to reference table number for TC 6.2B.2.3 and TC 6.2B.2.4 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200731 | 0570 | - | F | Correction of test cases in 7.6B.3 Out-of-band blocking for DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200732 | 0571 | - | F | Correction of test cases in 7.6B.4 Narrow band blocking for DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200733 | 0572 | - | F | Correction of test cases in 7.7B Spurious response for DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200776 | 0576 | - | F | TS 38.521-3 Section 1-5 and Annex updates to align with core specification | 16.3.0 | +| 2020-03 | RAN#87 | R5-200801 | 0577 | - | F | Update of Non-Standalone FR2 A-MPR test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200814 | 0579 | - | F | Correction to Test Case 6.5B.3.3.2 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200913 | 0534 | 1 | F | Update of Clause 4 in TS 38.521-3 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200925 | 0541 | 1 | F | Adding common uplink configuration of E-UTRA carrier for EN-DC testing | 16.3.0 | +| 2020-03 | RAN#87 | R5-200926 | 0543 | 1 | F | Updating configured output power for inter-band EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200927 | 0545 | 1 | F | Updating configured output power for intra-band contiguous EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200928 | 0547 | 1 | F | Updating configured output power for intra-band non-contiguous EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200929 | 0567 | 1 | F | Core spec alignment of EN-DC MOP and configured output power | 16.3.0 | +| 2020-03 | RAN#87 | R5-200963 | 0536 | 1 | F | Update of TC 7.5B.2 ACS for intra-band non-contiguous EN-DC 2CCs | 16.3.0 | +| 2020-03 | RAN#87 | R5-200964 | 0535 | 1 | F | Update of TC 7.5B.1 ACS for intra-band contiguous EN-DC 2CCs | 16.3.0 | +| 2020-03 | RAN#87 | R5-200982 | 0557 | 1 | F | Updates to 6.5B.2.1.3, Adjacent channel leakage ratio for intra-band contiguous EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200983 | 0575 | 1 | F | Corrections to 6.2B.3.1, UE A_MPR for Intra-band Contig EN_DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200984 | 0533 | 1 | F | Addition of Clause 7.5B.0.3a | 16.3.0 | +| 2020-03 | RAN#87 | R5-200995 | 0578 | 1 | F | Correction of Reference Sensitivity Test Case 7.3B.2.3 | 16.3.0 | +| 2020-03 | RAN#87 | R5-201019 | 0555 | 1 | F | Update of general sections on EN-DC configurations in 38.521-3 | 16.3.0 | +| 2020-03 | RAN#87 | R5-201055 | 0542 | 1 | F | Updating MOP for inter-band EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-201066 | 0564 | 1 | F | Add TX test for Rel16_DC_2_n41 and 66_n41 | 16.3.0 | +| 2020-03 | RAN#87 | R5-201067 | 0565 | 1 | F | Add RX test for Rel16_DC_2_n41 and 66_n41 | 16.3.0 | +| 2020-03 | RAN#87 | R5-201165 | 0574 | 1 | F | Correction of REFSENS for inter-band EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-201187 | 0548 | 1 | F | Addition of a few R16 EN-DC configurations | 16.3.0 | +| 2020-03 | RAN#87 | R5-201193 | 0532 | 1 | F | Updates of MU and TT in TS 38.521-3 | 16.3.0 | +| 2020-03 | RAN#87 | R5-201198 | 0556 | 1 | F | Correcting usage of modifiedMPR-Behaviour | 16.3.0 | +| 2020-06 | RAN#88 | R5-201721 | 0587 | - | F | Update Annex F.4 Uplink Power window explanation | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | R5-201855 | 0594 | - | F | Update of 6.2B.1.3 MOP for inter-band EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-201859 | 0596 | - | F | Updating A-SE to align test points with A-MPR | 16.4.0 | +| 2020-06 | RAN#88 | R5-201870 | 0598 | - | F | Update of test configuration in 6.5B.3.3.2 for UE co-existence | 16.4.0 | +| 2020-06 | RAN#88 | R5-201942 | 0605 | - | F | Updated to EN-DC Rel-16 band information in clause 5 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202032 | 0611 | - | F | Correction of Initial condition for OOB intra-band contiguous EN-DC 2 CCs in FR1 in TC 7.6B.3.1 R15 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202293 | 0626 | - | F | Correction to 7.3B.2.3 test configuration for EN-DC 26_n79 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202294 | 0627 | - | F | Correction to Frequency error for Intra-band contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202295 | 0628 | - | F | Correction to PRACH configuration for intra-band EN-DC tests | 16.4.0 | +| 2020-06 | RAN#88 | R5-202393 | 0630 | - | F | Addition of Intra-band non-contiguous EN-DC combination | 16.4.0 | +| 2020-06 | RAN#88 | R5-202421 | 0633 | - | F | Update Uplink power control window size for NSA TX TCs | 16.4.0 | +| 2020-06 | RAN#88 | R5-202429 | 0637 | - | F | Update for 7.3A.3 for CA without EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202475 | 0638 | - | F | TS 38.521-3 Section 1-5 and Annex updates to align with core specification | 16.4.0 | +| 2020-06 | RAN#88 | R5-202725 | 0585 | 1 | F | Correction on the channel bandwidth to use in section 6.5B.3.3 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202726 | 0586 | 1 | F | Setting p-MaxEUTRA to avoid limiting NR power in section 6.5B | 16.4.0 | +| 2020-06 | RAN#88 | R5-202727 | 0590 | 1 | F | Correction to TC 6.2B.4.1.3 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202728 | 0595 | 1 | F | Updating 6.2B.4.x configured output power test cases for FR1 EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202729 | 0614 | 1 | F | correction 6.3B.1.3 to include anchor agnostic approach applies | 16.4.0 | +| 2020-06 | RAN#88 | R5-202730 | 0616 | 1 | F | Clarification of disabling Tx diversity for FR2 UE for NSA FR2 testing | 16.4.0 | +| 2020-06 | RAN#88 | R5-202731 | 0618 | 1 | F | Updation of 6.5B.3.3.1 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202732 | 0639 | 1 | F | Addition of UL-MIMO EN-DC tests in Clause 6 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202733 | 0641 | 1 | F | Common updates across tests in Clause 6 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202734 | 0640 | 1 | F | Addition of UL-MIMO EN-DC tests in Clause 7 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202735 | 0642 | 1 | F | Common updates across tests in Clause 7 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202782 | 0635 | 1 | F | Update Rx TC for 5 Rel_16_DC_combos | 16.4.0 | +| 2020-06 | RAN#88 | R5-202809 | 0632 | 1 | F | Receiver characteristics testing update to 38.521-3 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202829 | 0601 | 1 | F | Addition of 6.2B.1.5D UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 for UL-MIMO | 16.4.0 | +| 2020-06 | RAN#88 | R5-202830 | 0602 | 1 | F | Addition of 6.2B.5.1.1 Configured Output Power Level for Inter-band NR-DC between FR1 and FR2 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202901 | 0631 | 1 | F | Power control for EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202902 | 0588 | 1 | F | Updated structure for RefSens for EN-DC within FR1 more than 2CCs | 16.4.0 | +| 2020-06 | RAN#88 | R5-202903 | 0597 | 1 | F | Updating REFSSENS for 1A_n78A and 3A_n78A | 16.4.0 | +| 2020-06 | RAN#88 | R5-202904 | 0613 | 1 | F | Introduction of Rx test cases for EN-DC within FR1 3CCs | 16.4.0 | +| 2020-06 | RAN#88 | R5-202905 | 0629 | 1 | F | Update to NSA FR2 Receiver Spurious Emission Test Case | 16.4.0 | +| 2020-06 | RAN#88 | R5-202906 | 0636 | 1 | F | Add 7.3B.2.3_1.2 Reference sensitivity for EN-DC within FR1v - 4 CCs | 16.4.0 | +| 2020-06 | RAN#88 | R5-202907 | 0624 | 1 | F | Updates of FR2 MU and TT in TS 38.521-3 | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | R5-202925 | 0634 | 1 | F | Update Tx TC for 5 Rel_16_DC_combos | 16.4.0 | +| 2020-06 | RAN#88 | R5-202934 | 0604 | 1 | F | Addition of TDD-TDD PC2 inter-band EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202945 | 0592 | 1 | F | Updating 6.2B.1.1 MOP for intra-band contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202946 | 0593 | 1 | F | Updating 6.2B.1.2 MOP for intra-band non-contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202947 | 0606 | 1 | F | Updates to 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202948 | 0607 | 1 | F | Updates to 6.5B.2.1.1, Spectrum emissions mask for intra-band contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202949 | 0608 | 1 | F | Updates to 6.5B.2.1.3, Adjacent channel leakage ratio for intra-band contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202959 | 0620 | 1 | F | Updates of Tx test cases for EN-DC including FR2 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202964 | 0622 | 1 | F | Update to configured output power relaxation due to inter-band EN-DC in 38.521-3 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202965 | 0623 | 1 | F | Update to REFSENS relaxation due to inter-band EN-DC in 38.521-3 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202991 | 0609 | 1 | F | Completion of TC 7.6B.3.3 OOB Inter-band EN-DC 2CCs within FR1 R15 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202992 | 0610 | 1 | F | Completion of TC 7.7B.3 Spurious Response Inter-band EN-DC 2CCs within FR1 R15 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202993 | 0612 | 1 | F | Alignment of requirements in 7.6B and 7.7B with core spec for Intra-band contiguous EN-DC in FR1 R15 | 16.4.0 | +| 2020-09 | RAN#89 | R5-203227 | 0644 | - | F | Adding receiver requirements for Rel-16 inter-band EN-DC FR1 band combinations | 16.5.0 | +| 2020-09 | RAN#89 | R5-203294 | 0645 | - | F | Correction of MU definition for test case 6.5B.2.1.3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203295 | 0646 | - | F | definition of MU and TT for test case 6.3B.4.3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203296 | 0647 | - | F | definition of MU and TT for test case 6.5B.4.3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203297 | 0648 | - | F | Definition of MU and TT for test case 7.3B.2.4 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203492 | 0650 | - | F | In-band Blocking FR2 MU updates in 38.521-3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203515 | 0651 | - | F | Editorial correction of test case 6.5B.3.3.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203637 | 0655 | - | F | Introduction of additional Rel-16 EN-DC inter-band configurations to EN-DC MOP test case 6.2B.1.3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203753 | 0660 | - | F | Update test procedure to 6.5B.3.3.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203763 | 0661 | - | F | Editorial correction of referenced clause (6.2.3) in test case 6.2B.2.1.2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203872 | 0668 | - | F | Adding RRCConnectionReconfiguration Table for E-UTRA on FDD band and UE does not support dynamic power sharing in 6.5B.3.3.1 and 6.5B.3.3.2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203907 | 0669 | - | F | Corrections on delta RIB due to Rel-16 EN-DC configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-203941 | 0674 | - | F | Addition of the test description to apply LTE agnostic approach in 7.4B.2 MIL | 16.5.0 | +| 2020-09 | RAN#89 | R5-203960 | 0680 | - | F | Correction to additional test points for spurious emission UE co-existence for a few Rel-15 inter-band EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-203973 | 0684 | - | F | Cleaning up of delta_TIB | 16.5.0 | +| 2020-09 | RAN#89 | R5-204154 | 0693 | - | F | Updated to Annex M for EN-DC Rel-16 configuration requirement | 16.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | RAN#89 | R5-204170 | 0697 | - | F | Update for TC 7.5B.0 Minimum Conformance Requirements of ACS for DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204176 | 0703 | - | F | Update for TC 7.5B.4 ACS for inter-band EN-DC including FR2 2CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204177 | 0704 | - | F | Update for TC 7.5B.4_1.1 ACS for inter-band EN-DC including FR2 3CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204178 | 0705 | - | F | Update for TC 7.5B.4_1.2 ACS for inter-band EN-DC including FR2 4CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204179 | 0706 | - | F | Update for TC 7.5B.4_1.3 ACS for inter-band EN-DC including FR2 5CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204180 | 0707 | - | F | Update for TC 7.5B.4_1.4 ACS for inter-band EN-DC including FR2 6CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204198 | 0713 | - | F | Update for 7.3B.2.0 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204199 | 0714 | - | F | Update for Spurious Emissions for intra-band EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204209 | 0717 | - | F | Update Uplink power control window size for NSA RX TCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204210 | 0718 | - | F | Update Tx TC for Rel-16 DC combos | 16.5.0 | +| 2020-09 | RAN#89 | R5-204250 | 0721 | - | F | FR2 Minimum output power measurement period definition | 16.5.0 | +| 2020-09 | RAN#89 | R5-204296 | 0726 | - | F | Addition of test case 6.4B.2.4.1D | 16.5.0 | +| 2020-09 | RAN#89 | R5-204297 | 0727 | - | F | Addition of test case 6.4B.2.4.2D | 16.5.0 | +| 2020-09 | RAN#89 | R5-204298 | 0728 | - | F | Addition of test case 6.4B.2.4.3D | 16.5.0 | +| 2020-09 | RAN#89 | R5-204299 | 0729 | - | F | Addition of test case 6.4B.2.4.4D | 16.5.0 | +| 2020-09 | RAN#89 | R5-204310 | 0730 | - | F | Update of test case 6.2B.3.1 UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204313 | 0733 | - | F | TS 38.521-3 Section 1-5 and Annex updates to align with core specification | 16.5.0 | +| 2020-09 | RAN#89 | R5-204322 | 0736 | - | F | Update for TC 7.5B.5 ACS for inter-band EN-DC including both FR1 and FR2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204349 | 0738 | - | F | Editorial correction of Rx spurious emissions for FR1 EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204705 | 0739 | - | F | Addition of test configuration for 71AA in 6.2B.1.1 MOP | 16.5.0 | +| 2020-09 | RAN#89 | R5-204707 | 0740 | - | F | Addition of MOP testing for DC_28A_n3A in 6.2B.1.3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204719 | 0715 | 1 | F | Update for 7.3B.2.3_1.3 Reference sensitivity for EN-DC within FR1 5CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204724 | 0662 | 1 | F | Updated to clause 6 for EN-DC Rel-16 band requirement | 16.5.0 | +| 2020-09 | RAN#89 | R5-204766 | 0665 | 1 | F | Spurious inter-band EN-DC FR2 UL MIMO test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-204767 | 0673 | 1 | F | Addition of test requirement of dropped NR carrier for non-DPS UE in 6.2B.4.x | 16.5.0 | +| 2020-09 | RAN#89 | R5-204768 | 0678 | 1 | F | Addition of additional test points for spurious emission UE co-existence for a few Rel-15 inter-band EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204769 | 0723 | 1 | F | Editorial correction to EN-DC co-existence requirements | 16.5.0 | +| 2020-09 | RAN#89 | R5-204770 | 0664 | 1 | F | FR2 RefSens inter-band EN-DC UL MIMO test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-204771 | 0670 | 1 | F | Update of 7.3B.3.3 for REFSSENS relaxation due to inter-band EN-DC within FR1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204772 | 0676 | 1 | F | Addition of new test case 7.4B.5D MIL for inter-band EN-DC including FR1 and FR2 for UL-MIMO | 16.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | RAN#89 | R5-204773 | 0709 | 1 | F | Addition of TC 7.5B.5D ACS for inter-band EN-DC including FR1 and FR2 for UL-MIMO | 16.5.0 | +| 2020-09 | RAN#89 | R5-204809 | 0643 | 1 | F | Adding transmitter requirements for Rel-16 inter-band EN-DC FR1 band combinations | 16.5.0 | +| 2020-09 | RAN#89 | R5-204810 | 0654 | 1 | F | Editorial correction to spurious emission test case 6.5B.3.3.2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204811 | 0656 | 1 | F | Introduction of dTIBc for additional Rel-16 EN-DC inter-band configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-204812 | 0657 | 1 | F | Introduction of Rel-16 EN-DC configuration DC_40A_n1A to spurious emission test case 6.5B.3.3.2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204813 | 0658 | 1 | F | Introduction of Rel-16 EN-DC configuration DC_40A_n78A to spurious emission test case 6.5B.3.3.2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204814 | 0679 | 1 | F | Addition of additional test points for spurious emission UE co-existence for a few Rel-16 inter-band EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204815 | 0694 | 1 | F | Updated to clause 6 for EN-DC Rel-16 configuration test requirement | 16.5.0 | +| 2020-09 | RAN#89 | R5-204816 | 0692 | 1 | F | Updated to EN-DC Rel-16 Configuration information in clause 5 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204840 | 0696 | 1 | F | Updated to EN-DC general clauses for NRSL eV2X | 16.5.0 | +| 2020-09 | RAN#89 | R5-204866 | 0689 | 1 | F | CR to update MU and TT in 38.521-3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204867 | 0716 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204869 | 0649 | 1 | F | Adjacent Channel Selectivity FR2 MU and TT updates in 38.521-3 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204924 | 0666 | 1 | F | Update of Test applicability for some Inter-Band EN-DC including FR2 TCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204925 | 0687 | 1 | F | Clean up complete status for EN-DC test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-204926 | 0731 | 1 | F | Addition of pending UL-MIMO tests (FR2) in Clause 6 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204928 | 0681 | 1 | F | Update of NSA Rx test cases for 4Rx UEs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204929 | 0700 | 1 | F | Addition of TC 7.5B.3_1.2 ACS for EN-DC within FR1 4CC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204930 | 0711 | 1 | F | Addition of TC 7.6B.2.5D Inband blocking for inter-band EN-DC including FR1 and FR2 for UL-MIMO | 16.5.0 | +| 2020-09 | RAN#89 | R5-204931 | 0712 | 1 | F | Update for 7.3B.2.3 Ref sense for Inter-band EN-DC within FR1-2 CCs | 16.5.0 | +| 2020-09 | RAN#89 | R5-204932 | 0719 | 1 | F | Re-organization of EN-DC refsens test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-204957 | 0695 | 1 | F | Updated to clause 7 for EN-DC Rel-16 configuration test requirement | 16.5.0 | +| 2020-09 | RAN#89 | R5-204958 | 0737 | 1 | F | Add Rx TC for 2Rel 16 DC combos | 16.5.0 | +| 2020-09 | RAN#89 | R5-205005 | 0741 | - | F | Update of OOB and Spurious Response of Inter-band EN-DC within FR1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-205006 | 0690 | 1 | F | Update Refsense exceptions for EN-DC including n78 | 16.5.0 | +| 2020-12 | RAN#90 | R5-205489 | 0749 | - | F | Correction to Reference Sensitivity for Inter-band EN-DC | 16.6.0 | +| 2020-12 | RAN#90 | R5-205500 | 0750 | - | F | Minor correction of section 6.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205501 | 0751 | - | F | Correction of spec style in section 7.6B and 7.7B and correction of table number in 7.6B.3.3.4.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205502 | 0752 | - | F | Addition of intra-band contiguous EN-DC testing and update of inter-band EN-DC testing for 7.6B.2.3_1.1 Inband blocking for EN-DC within FR1 3 CCs | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | RAN#90 | R5-205503 | 0753 | - | F | Addition of intra-band contiguous EN-DC testing and update of inter-band EN-DC testing for 7.6B.2.3_1.2 Inband blocking for EN-DC within FR1 4 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205505 | 0755 | - | F | Addition of new test case 7.6B.3.3_1.1 Out-of-band blocking for EN-DC within FR1 3 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205506 | 0756 | - | F | Addition of new test case 7.6B.3.3_1.2 Out-of-band blocking for EN-DC within FR1 4 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205507 | 0757 | - | F | Addition of intra-band contiguous EN-DC testing and update of inter-band EN-DC testing for 7.6B.4.3_1.1 Narrow band blocking for EN-DC within FR1 3 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205508 | 0758 | - | F | Addition of intra-band contiguous EN-DC testing and update of inter-band EN-DC testing for 7.6B.4.3_1.2 Narrow band blocking for EN-DC within FR1 4 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205510 | 0760 | - | F | Addition of new test case 7.7B.3_1.1 Spurious Response for EN-DC within FR1 3 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205511 | 0761 | - | F | Addition of new test case 7.7B.3_1.2 Spurious Response for EN-DC within FR1 4 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205515 | 0763 | - | F | Correction of section 7.1 and update of 7.6B.3.0.3A and 7.7B.0.3A as per RAN4 spec | 16.6.0 | +| 2020-12 | RAN#90 | R5-205516 | 0764 | - | F | Correction of uplink power and in gap test requirement for 7.6B.2.2, 7.6B.3.2, 7.6B.4.2 and 7.7B.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205534 | 0768 | - | F | Editorial, removing duplication of text in test case | 16.6.0 | +| 2020-12 | RAN#90 | R5-205568 | 0776 | - | F | Introduction of DC_3A-40A_n1A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-205678 | 0778 | - | F | Addition of Clause 7.5B.4D ACS for inter-band EN-DC including FR2 for UL-MIMO | 16.6.0 | +| 2020-12 | RAN#90 | R5-205679 | 0779 | - | F | Addition of Clause 7.6B.2.4D Inband blocking for inter-band EN-DC including FR2 for UL-MIMO | 16.6.0 | +| 2020-12 | RAN#90 | R5-205696 | 0782 | - | F | Editorial correction to EN-DC test cases 6.5B.2.3 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205775 | 0785 | - | F | Adding delta TIB for a few Rel-16 inter-band EN-DC configurations within FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205776 | 0786 | - | F | Adding refsens exceptions for DC_3_n78 due to receiver harmonic mixing | 16.6.0 | +| 2020-12 | RAN#90 | R5-205778 | 0788 | - | F | Adding delta RIB for DC_2-7-66_n78 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205784 | 0790 | - | F | Update of UE co-existence spurious emissions for Rel-16 inter-band EN-DC DC_13_n66 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205788 | 0792 | - | F | Correction to UE co-existence spurious emissions for inter-band EN-DC within FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205803 | 0793 | - | F | Introduction of New TC 6.4B.2.4.2_1.1 Carrier Leakage for inter-band EN-DC including FR2 with 3 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205804 | 0794 | - | F | Introduction of New TC 6.4B.2.4.2_1.2 Carrier Leakage for inter-band EN-DC including FR2 with 4 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205806 | 0795 | - | F | Introduction of New TC 6.4B.2.4.2_1.3 Carrier Leakage for inter-band EN-DC including FR2 with 5 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-205855 | 0798 | - | F | Correction of channel bandwidth for EN-DC MOP TC 6.2B.1.3 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205911 | 0803 | - | F | Introduction of DC_3A-20A_n78A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-205934 | 0805 | - | F | Update of DC_1A-7A_n78A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-205935 | 0806 | - | F | Update DC_7A-20A_n78A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-205994 | 0808 | - | F | Updates to Reference sensitivity for EN-DC within FR1 3CC | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | RAN#90 | R5-206018 | 0811 | - | F | Correction of 7.3B.3.3 for delta RIB with inter-band EN-DC configurations | 16.6.0 | +| 2020-12 | RAN#90 | R5-206029 | 0813 | - | F | Update spurious emission band UE co-existence for DC_2_n41 and DC_66_n41 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206236 | 0832 | - | F | Correction to Rel-16 EN-DC configuration DC_40A_n1A and DC_40A_n78 in spurious emission test case 6.5B.3.3.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206237 | 0833 | - | F | Introduction of Rel-16 EN-DC configuration DC_1A_n3A to spurious emission test case 6.5B.3.3.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206238 | 0834 | - | F | Introduction of Rel-16 EN-DC configuration DC_20A_n3A to spurious emission test case 6.5B.3.3.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206255 | 0835 | - | F | Update for 6.5B.3.2.2 Spurious emission band UE co-existence for intra-band non-contiguous EN-DC | 16.6.0 | +| 2020-12 | RAN#90 | R5-206648 | 0766 | 1 | F | Addition of TC6.3B.1.4D Minimum output power for inter-band EN-DC including FR2 for UL-MIMO | 16.6.0 | +| 2020-12 | RAN#90 | R5-206649 | 0767 | 1 | F | Addition of TC6.3B.3.4 Transmit ON/OFF time mask for inter-band EN-DC including FR2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206650 | 0777 | 1 | F | Update on Transmit OFF power for EN-DC including FR2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206651 | 0789 | 1 | F | Update of UE co-existence spurious emissions for a few Rel-15 inter-band EN-DC configurations | 16.6.0 | +| 2020-12 | RAN#90 | R5-206652 | 0796 | 1 | F | Addition of 6.5B.2.4D.3 Adjacent channel leakage ratio for inter-band EN-DC including FR2 for UL-MIMO | 16.6.0 | +| 2020-12 | RAN#90 | R5-206653 | 0799 | 1 | F | Update of 6.2B.1.4_1 MOP for Inter-Band EN-DC including FR2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206654 | 0821 | 1 | F | Update for 6.5B.3.1.2 Spurious emission band UE co-existence for intra-band contiguous EN-DC | 16.6.0 | +| 2020-12 | RAN#90 | R5-206655 | 0822 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Inter-band within FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206656 | 0780 | 1 | F | Update for Clause F.1.3 Measurement of receiver | 16.6.0 | +| 2020-12 | RAN#90 | R5-206657 | 0810 | 1 | F | Correction of 7.3B.3.3 for allowed reference sensitivity relaxation | 16.6.0 | +| 2020-12 | RAN#90 | R5-206658 | 0819 | 1 | F | Update the interferer range for OOB and Spurious Response of Inter-band EN-DC within FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206659 | 0823 | 1 | F | Update for 7.3B.2.0 Minimum Conformance Requirements of Reference sensitivity for EN-DC | 16.6.0 | +| 2020-12 | RAN#90 | R5-206660 | 0826 | 1 | F | Editor's notes updates for FR1 inter-band 3CC DL CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206661 | 0762 | 1 | F | Addition of measurement uncertainties and test tolerance for blocking test cases for EN-DC within FR1 with 3CCs, 4CCs and 5CCs and correction of some spec styles | 16.6.0 | +| 2020-12 | RAN#90 | R5-206662 | 0817 | 1 | F | 6.4B.2.1.1 Error Vector Magnitude for intra-band contiguous EN DC Measurement Uncertainty update | 16.6.0 | +| 2020-12 | RAN#90 | R5-206663 | 0818 | 1 | F | 6.4B.2.1.2 Carrier Leakage for intra-band contiguous EN-DC Measurement Uncertainty update | 16.6.0 | +| 2020-12 | RAN#90 | R5-206664 | 0820 | 1 | F | FR1 Intra-band CA General Tx ON OFF time mask measurement uncertainties and test tolerances corrections | 16.6.0 | +| 2020-12 | RAN#90 | R5-206665 | 0836 | 1 | F | TS 38.521-3 Section 1-5 and Annex updates to align with core specification | 16.6.0 | +| 2020-12 | RAN#90 | R5-206720 | 0742 | 1 | F | Introduction of New test case 6.3B.1.4_1.1 Minimum output power for inter-band EN-DC including FR2 - 3 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206721 | 0743 | 1 | F | Introduction of New test case 6.3B.1.4_1.2 Minimum output power for inter-band EN-DC including FR2 - 4 CCs | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | RAN#90 | R5-206722 | 0744 | 1 | F | Introduction of New test case 6.3B.1.4_1.3 Minimum output power for inter-band EN-DC including FR2 - 5 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206723 | 0745 | 1 | F | Introduction of New test case 6.4B.2.4.1_1.1 Error Vector Magnitude for inter-band EN-DC including FR2 - 3 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206724 | 0746 | 1 | F | Introduction of New test case 6.4B.2.4.1_1.2 Error Vector Magnitude for inter-band EN-DC including FR2 - 4 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206725 | 0747 | 1 | F | Introduction of New test case 6.4B.2.4.1_1.3 Error Vector Magnitude for inter-band EN-DC including FR2 - 5 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206727 | 0787 | 1 | F | Adding refsens exceptions for DC_3_n1 due to cross band isolation | 16.6.0 | +| 2020-12 | RAN#90 | R5-206728 | 0783 | 1 | F | Update to EN-DC R16 Configuration information in clause 5 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206772 | 0781 | 1 | F | Addition of PC2 Tx requirements for DC_3A_n41A | 16.6.0 | +| 2020-12 | RAN#90 | R5-206773 | 0801 | 1 | F | Addition of PC2 Tx requirements for DC_3A_n78A | 16.6.0 | +| 2020-12 | RAN#90 | R5-206784 | 0802 | 1 | F | Updating Rel-16 EN-DC PC2 MOP to add UE power class capability for NR part | 16.6.0 | +| 2020-12 | RAN#90 | R5-206827 | 0829 | 1 | F | Minimum output power editor's notes | 16.6.0 | +| 2020-12 | RAN#90 | R5-206828 | 0828 | 1 | F | Update FR2 TRx MU and TT in 38.521-3 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206869 | 0809 | 1 | F | Updates to Reference sensitivity for EN-DC within FR1 4CC re-structuring test configuration tables | 16.6.0 | +| 2020-12 | RAN#90 | R5-206870 | 0825 | 1 | F | Measurement uncertainties and test tolerances updates for FR1 inter-band 3CC DL CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206883 | 0772 | 1 | F | Introduction of DC_3A_n1A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206884 | 0773 | 1 | F | Introduction of DC_1A_n3A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206885 | 0774 | 1 | F | Introduction of DC_20A_n3A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206886 | 0775 | 1 | F | Introduction of DC_40A_n78A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206902 | 0769 | 1 | F | Moving test configurations table for EN-DC 20_n78 to a general test configuration table for 2CC reference sensitivity exceptions | 16.6.0 | +| 2020-12 | RAN#90 | R5-206903 | 0770 | 1 | F | Introduction of DC_1A_n78A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206904 | 0771 | 1 | F | Introduction of DC_3A_n78A to reference sensitivity test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206913 | 0754 | 1 | F | Update of 7.6B.2.3_1.3 Inband blocking for EN-DC within FR1 5 CCs and removal of 7.6B.2.3_1.4 Inband blocking for EN-DC within FR1 6 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206914 | 0759 | 1 | F | Update of 7.6B.4.3_1.3 Narrow band blocking for EN-DC within FR1 5 CCs and removal of 7.6B.4.3_1.4 Narrow band blocking for EN-DC within FR1 6 CCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206915 | 0807 | 1 | F | Updates to Reference sensitivity for EN-DC within FR1 2CC for UE supporting single UL | 16.6.0 | +| 2020-12 | RAN#90 | R5-206916 | 0827 | 1 | F | Update for 7.3B.3.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206918 | 0804 | 1 | F | Addition of PC2 Rx requirements for DC_3A_n41A | 16.6.0 | +| 2020-12 | RAN#90 | R5-206919 | 0814 | 1 | F | Addition of PC2 ENDC DC_3A_n78A into TC7.3B.2.3 | 16.6.0 | +| 2021-03 | RAN#91 | R5-210093 | 0842 | - | F | Introduction of DC_7A-20A_n3A to reference sensitivity test | 16.7.0 | +| 2021-03 | RAN#91 | R5-210301 | 0847 | - | F | Completion of OBW intra-band non-contiguous test 6.5B.1.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210302 | 0848 | - | B | Addition of new test case 6.5B.1.4D OBW for inter-band EN-DC FR2 UL MIMO | 16.7.0 | +| 2021-03 | RAN#91 | R5-210387 | 0857 | - | F | Correction to EN-DC OoB emissions | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91 | R5-210415 | 0858 | - | F | Addition of new test case 6.4B.2.4.3_1.1 In-band Emissions for inter-band EN-DC including FR2 with 3 CCs | 16.7.0 | +| 2021-03 | RAN#91 | R5-210416 | 0859 | - | F | Addition of new test case 6.4B.2.4.3_1.2 In-band Emissions for inter-band EN-DC including FR2 with 4 CCs | 16.7.0 | +| 2021-03 | RAN#91 | R5-210417 | 0860 | - | F | Addition of new test case 6.4B.2.4.3_1.3 In-band Emissions for inter-band EN-DC including FR2 with 5 CCs | 16.7.0 | +| 2021-03 | RAN#91 | R5-210497 | 0861 | - | F | Correction of test frequencies for NR band n28 30MHz test channel bandwidth of 6.2B.1.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210498 | 0862 | - | F | Addition of editor note to the incomplete test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210499 | 0863 | - | F | Correction of test applicability of 6.5B.5.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210500 | 0864 | - | F | Correction of test configuration tables in section 6 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210501 | 0865 | - | F | Completion of 7.6B.2.3_1.3 Inband blocking for EN-DC within FR1 5 CCs | 16.7.0 | +| 2021-03 | RAN#91 | R5-210502 | 0866 | - | F | Correction of test frequencies for NR band n28 30MHz test channel bandwidth of 7.6B.3.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210548 | 0872 | - | F | Default message exceptions for LTE carriers in EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-210725 | 0874 | - | F | Omitting of NSA Rx cases with UL-MIMO on TDD bands | 16.7.0 | +| 2021-03 | RAN#91 | R5-210909 | 0882 | - | F | Editorial correction to test case 6.2B.4.1.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210943 | 0883 | - | F | Adding delta TIB and delta RIB for DC_2-7-7-66_n78 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210989 | 0889 | - | F | Update for 7.3B.2.0 Minimum Conformance Requirements of Reference sensitivity for EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211005 | 0893 | - | F | Update to EN-DC R16 Configuration information in clause 5 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211010 | 0895 | - | F | Update of reference sensitivity for intra-band contiguous EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211014 | 0899 | - | F | Adding in-gap tests to ACS for intra-band non-contiguous EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211017 | 0901 | - | F | Update of test coverage for reference sensitivity for 3CC EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211020 | 0902 | - | F | Adding EN-DC configurations DC_1A-28A_n3A and DC_7A-28A_n3A to clause 5.5B.4.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211099 | 0917 | - | F | Correction to editors note about number of E-UTRA carriers | 16.7.0 | +| 2021-03 | RAN#91 | R5-211111 | 0921 | - | F | Corrections to subclauses in 38.521-3 with appropriate subclause level and heading styles | 16.7.0 | +| 2021-03 | RAN#91 | R5-211125 | 0922 | - | F | Update of 5.3B for UE channel bandwidth for EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211240 | 0934 | - | F | Introduction of DC_7A-20A_n1A to reference sensitivity test | 16.7.0 | +| 2021-03 | RAN#91 | R5-211241 | 0935 | - | F | Introduction of DC_7A-28A_n3A to reference sensitivity test | 16.7.0 | +| 2021-03 | RAN#91 | R5-211694 | 0844 | 1 | F | Spectrum emissions mask for intra-band non-contiguous EN-DC Test Definition | 16.7.0 | +| 2021-03 | RAN#91 | R5-211695 | 0849 | 1 | F | ACLR for intra-band non-contiguous EN-DC Test Definition | 16.7.0 | +| 2021-03 | RAN#91 | R5-211696 | 0856 | 1 | F | Update Test description of 6.5B.1.1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211697 | 0871 | 1 | F | EN-DC FR2 UL CA Frequency error test cases update | 16.7.0 | +| 2021-03 | RAN#91 | R5-211698 | 0876 | 1 | F | Correction of test requirements for EN-DC configured output power | 16.7.0 | +| 2021-03 | RAN#91 | R5-211699 | 0906 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_8A_n77A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211700 | 0907 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_11A_n77A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91 | R5-211701 | 0908 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_11A_n78A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211702 | 0909 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_11A_n79A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211703 | 0910 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_25A_n41A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211704 | 0911 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_26A_n41A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211705 | 0912 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_26A_n77A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211706 | 0913 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_26A_n78A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211707 | 0914 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_26A_n79A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211708 | 0915 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_41A_n77A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211709 | 0916 | 1 | F | Introduction of Rel-15 EN-DC configuration DC_41A_n78A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211710 | 0853 | 1 | F | Correction of MSD test point on Table 7.3B.2.0.3.5.2-1 DC_1A-8A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211711 | 0854 | 1 | F | Update of 7.3B.2.3_1.1 RefSens DC_3A-8A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211712 | 0855 | 1 | F | Addition of new test case 7.3B.4 for EIS Spherical Coverage | 16.7.0 | +| 2021-03 | RAN#91 | R5-211713 | 0867 | 1 | F | Editorial correction for errors in 7.6B.4.3_1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211714 | 0868 | 1 | F | Correction of test configuration tables in section 7 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211715 | 0877 | 1 | F | Clarification of tested Rx antenna numbers on E-UTRA band | 16.7.0 | +| 2021-03 | RAN#91 | R5-211766 | 0837 | 1 | F | Introduction of Rel-16 EN-DC configuration DC_7A_n3A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211767 | 0838 | 1 | F | Introduction of Rel-16 EN-DC configuration DC_8A_n3A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211768 | 0839 | 1 | F | Introduction of Rel-16 EN-DC configuration DC_20A_n1A to spurious emission test case 6.5B.3.3.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211769 | 0887 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence_Rel16 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211770 | 0903 | 1 | F | Adding Delta TIB,c for DC_1A-28A_n3A, DC_7A-20A_n1A and DC_7A-28A_n3A to clause 6.2B.4.2.3.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211771 | 0840 | 1 | F | Introduction of DC_7A_n3A to reference sensitivity test | 16.7.0 | +| 2021-03 | RAN#91 | R5-211772 | 0841 | 1 | F | Introduction of DC_8A_n1A and DC_8A_n3A to reference sensitivity test | 16.7.0 | +| 2021-03 | RAN#91 | R5-211773 | 0869 | 1 | F | Adding Inter-band EN-DC combination within FR1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211840 | 0878 | 1 | F | Updating Rel-16 EN-DC PC2 MOP to include powerClassNRPart-r16 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211841 | 0879 | 1 | F | Updating Rel-16 EN-DC PC2 MPR to include powerClassNRPart-r16 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211842 | 0880 | 1 | F | Updating Rel-16 EN-DC PC2 A-MPR to include powerClassNRPart-r16 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211843 | 0881 | 1 | F | Updating Rel-16 EN-DC PC2 configured output power to include powerClassNRPart-r16 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211852 | 0888 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91 | R5-211854 | 0890 | 1 | F | Correction to EN-DC Wideband Intermodulation tests | 16.7.0 | +| 2021-03 | RAN#91 | R5-211870 | 0843 | 1 | F | Editorial addition of editors notes in 6.3B.8.1.4, 6.3B.8.2.4 and 6.3B.8.3.4 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211871 | 0875 | 1 | F | Correcting EN-DC A-MPR test requirements for non-overlapping test points | 16.7.0 | +| 2021-03 | RAN#91 | R5-211872 | 0886 | 1 | F | Correction to the TDM pattern configuration for EN-DC Tx test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211873 | 0918 | 1 | F | Correction to MOP and MPR test procedures for PC2 in TC 6.2B.1.3 and 6.2B.2.1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211874 | 0845 | 1 | F | Correction of LTE frequency for 19-n79 combo in 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211875 | 0870 | 1 | F | Update to EN-DC Reference Sensitivity | 16.7.0 | +| 2021-03 | RAN#91 | R5-211876 | 0896 | 1 | F | Update of reference sensitivity for intra-band non-contiguous EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211877 | 0897 | 1 | F | Update of reference sensitivity for inter-band 2CC EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211878 | 0898 | 1 | F | Correction to refsens test requirements for DC_1A-7A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211879 | 0900 | 1 | F | Update of test configuration for inter-band 2CC EN-DC configurations affected by reference sensitivity exceptions | 16.7.0 | +| 2021-03 | RAN#91 | R5-211880 | 0924 | 1 | F | Update of 2CC refsens test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211881 | 0925 | 1 | F | Update of 3CC refsens test case 7.3B.2.3_1.1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211882 | 0926 | 1 | F | Correction of configurations not to be tested in 4CC refsens test case 7.3B.2.3_1.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211883 | 0927 | 1 | F | Addition of DC_8A_n77A in test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211884 | 0928 | 1 | F | Addition of DC_11A_n79A in test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211885 | 0929 | 1 | F | Addition of DC_26A_n41A in test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211886 | 0930 | 1 | F | Addition of DC_26A_n77A and DC_26A_n78A in test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211887 | 0931 | 1 | F | Addition of DC_26A_n79A in test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211888 | 0932 | 1 | F | Addition of DC_41A_n77A and DC_41A_n78A in test case 7.3B.2.3 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211905 | 0933 | 1 | F | Introduction of DC_1A-28A_n3A to reference sensitivity test | 16.7.0 | +| 2021-03 | RAN#91 | R5-211926 | 0851 | 1 | F | MU definition for UE MOP for Inter-Band EN-DC including FR2 (3CCs) | 16.7.0 | +| 2021-03 | RAN#91 | R5-211927 | 0852 | 1 | F | MU and TT definition for REFSENS EN-DC including FR2 up to 5CCs | 16.7.0 | +| 2021-03 | RAN#91 | R5-211928 | 0920 | 1 | F | Update FR2 MU and TT in 38.521-3 | 16.7.0 | +| 2021-03 | RAN#91 | - | - | - | - | Administrative release upgrade to match the release of TS 38.508-1, TS 38.508-2 and TS 38.521-1 which were upgraded at RAN#91 to Rel-17 due to Rel-17 relevant CRs | 17.0.0 | +| 2021-06 | RAN#92 | R5-212345 | 0944 | - | F | Define MU and TT for test case 7.9B.3_1.1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212349 | 0948 | - | F | Update MU and TT in 38.521-3 for Transmit OFF Power FR2 CA tests | 17.1.0 | +| 2021-06 | RAN#92 | R5-212350 | 0949 | - | F | ACS and IBB - FR2 MU definition in 38.521-3 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212531 | 0954 | - | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Rel 16 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212646 | 0976 | - | F | Correcting test case title in 6.5B.2.2.2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212734 | 0977 | - | F | Update UL-MIMO to UL MIMO in clause 6 to align with other specs | 17.1.0 | +| 2021-06 | RAN#92 | R5-212735 | 0978 | - | F | Update UL-MIMO to UL MIMO in clause 7 to align with other specs | 17.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | RAN#92 | R5-212736 | 0979 | - | F | Update UL-MIMO to UL MIMO in Common and Annexes to align with other specs | 17.1.0 | +| 2021-06 | RAN#92 | R5-212749 | 0983 | - | F | Update to EN-DC R15 common section | 17.1.0 | +| 2021-06 | RAN#92 | R5-212824 | 0986 | - | F | Correction of 6.2B.1.2 for test of UE maximum output power for intra-band non-contiguous EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-212825 | 0987 | - | F | Correction of 6.2B.1.3 for test of UE maximum output power for EN-DC within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212867 | 0992 | - | F | Correction of the section order in 7.9B | 17.1.0 | +| 2021-06 | RAN#92 | R5-212869 | 0994 | - | F | Unify the SCS definitions in the test configuration tables | 17.1.0 | +| 2021-06 | RAN#92 | R5-212976 | 0996 | - | F | Updating H.2.2 for NR NSA testing | 17.1.0 | +| 2021-06 | RAN#92 | R5-213018 | 0998 | - | F | Update of E-UTRA TDD configuration for overlapping UL transmission | 17.1.0 | +| 2021-06 | RAN#92 | R5-213019 | 0999 | - | F | Update of TDM pattern configuration in EN-DC MOP and A-MPR cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-213020 | 1000 | - | F | Update of EN-DC Tx cases to enable DFT-s-OFDM modulation for NR uplink carrier | 17.1.0 | +| 2021-06 | RAN#92 | R5-213045 | 1006 | - | F | Correction to reference sensitivity for DC_41A_n77A and DC_41A_n78A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213046 | 1007 | - | F | Correction to reference sensitivity for a few Rel-16 EN-DC combinations | 17.1.0 | +| 2021-06 | RAN#92 | R5-213047 | 1008 | - | F | Correction to test description in 7.3B.2 refsens for EN-DC within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213048 | 1009 | - | F | Update of test requirements for exception avoiding test points in 7.3B.2.3 refsens for inter-band EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-213059 | 1011 | - | F | Update of 6.4B.2.2.3 In-band Emissions for intra-band non-contiguous EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-213060 | 1012 | - | F | Correction of 7.4B.3.1 Maximum Input Level for EN-DC within FR1 with more than 2 CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-213200 | 1015 | - | F | Correction to EN-DC FR1 TC6.3B.1.1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213377 | 1028 | - | F | Correcting test procedure and test requirement for MPR Intra-Band Contiguous EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-213843 | 0971 | 1 | F | Correction of power control in 38.521-3 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213844 | 1020 | 1 | F | FR2 Inter-band Carrier Aggregation Minimum Output power updates | 17.1.0 | +| 2021-06 | RAN#92 | R5-213845 | 1010 | 1 | F | Adding refsens testing per band for all inter-band 2CC EN-DC FR1 non-exception requirements | 17.1.0 | +| 2021-06 | RAN#92 | R5-213846 | 1019 | 1 | F | Measurement uncertainties and test tolerances for FR2 Inter-band Carrier Aggregation Minimum Output power | 17.1.0 | +| 2021-06 | RAN#92 | R5-213905 | 0947 | 1 | F | Update 6.2B.1.1 according to core requirements | 17.1.0 | +| 2021-06 | RAN#92 | R5-213906 | 0952 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Rel 15 DC_2A_n71A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213907 | 0955 | 1 | F | Update for 6.5B.3.3.2 for Rel 15 requirement | 17.1.0 | +| 2021-06 | RAN#92 | R5-213908 | 0975 | 1 | F | References to voided clause 5.2B.2 corrected | 17.1.0 | +| 2021-06 | RAN#92 | R5-213909 | 0990 | 1 | F | Removal of test cases in 6.3B.2.4_1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213910 | 0997 | 1 | F | Correction of test frequencies for NR band n28 30MHz test channel bandwidth in 6.2B.4.1.3 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213911 | 1001 | 1 | F | Update of EN-DC Tx test cases with LTE anchor agnostic approach applied | 17.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------|--------| +| 2021-06 | RAN#92 | R5-213912 | 1023 | 1 | F | Updates to Frequency Error for Inter-band EN-DC including FR2 (>2 CCs) | 17.1.0 | +| 2021-06 | RAN#92 | R5-213913 | 1025 | 1 | F | Addition of missing EN-DC Beam Correspondence requirements | 17.1.0 | +| 2021-06 | RAN#92 | R5-213914 | 0963 | 1 | F | Addition of 7.5B.3_1.3 ACS for EN-DC within FR1 5 CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-213915 | 0964 | 1 | F | Addition of 7.5B.3_1.4 ACS for EN-DC within FR1 6 CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-213916 | 0973 | 1 | F | Update of FR1 EN-DC intermodulation with 4CC in TC 7.8B.2.3_1.2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213917 | 1029 | 1 | F | Correction to EN-DC Rx test case and format | 17.1.0 | +| 2021-06 | RAN#92 | R5-213918 | 0967 | 1 | F | Update of Annex F.1.3 for ACS for EN-DC within FR1 5CCs and 6CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-213973 | 0942 | 1 | F | Correction to EN-DC configuration DC_7A_n3A spurious emission test requirement | 17.1.0 | +| 2021-06 | RAN#92 | R5-213974 | 0953 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for Rel 16 DC_66A_n2A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213975 | 0988 | 1 | F | Update of 6.5B.3.3 for spurious emission for DC_2_n41 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213976 | 0956 | 1 | F | Correction for DC_7A-20A_n3A reference sensitivity test | 17.1.0 | +| 2021-06 | RAN#92 | R5-214008 | 1018 | 1 | F | Update of PC2 ENDC DC_3A-n78A into 38.521-3 TC7.3B.2.3 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214030 | 1014 | 1 | F | Addition of PC2 ENDC DC_1A-n78A into 38.521-3 TC7.3B.2.3 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214041 | 0972 | 1 | F | Correction of ON OFF time mask in 38.521-3 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214052 | 0993 | 1 | F | Correction of for further study notes about FR2 ETC testing | 17.1.0 | +| 2021-06 | RAN#92 | R5-214053 | 1002 | 1 | F | Correction to UE co-existence spurious emissions for intra-band contiguous EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-214054 | 1003 | 1 | F | Correction to UE co-existence spurious emissions for intra-band non-contiguous EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-214055 | 1004 | 1 | F | Correction to test configuration for general spurious emissions for inter-band EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-214056 | 1005 | 1 | F | Updating test requirements for general spurious emissions for inter-band EN-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-214057 | 1024 | 1 | F | Update of Spurious emission band UE co-existence test case | 17.1.0 | +| 2021-06 | RAN#92 | R5-214072 | 0950 | 1 | F | Update of 6.5B.3.3.2 for Rel-16 combo DC_14A_n2A and DC_14A_n66A | 17.1.0 | +| 2021-06 | RAN#92 | R5-214079 | 0958 | 1 | F | Update of Applicability for Tx inter-band EN-DC including FR2 under R15 WI | 17.1.0 | +| 2021-06 | RAN#92 | R5-214080 | 0974 | 1 | F | Editor's note for Wgap can be removed in 6.5B.4.2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214081 | 0980 | 1 | F | Update of applicability for EN-DC Tx tests within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214082 | 0959 | 1 | F | Update of Applicability for Rx inter-band EN-DC including FR2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214083 | 0961 | 1 | F | Correction of 7.5B.3_1.1 ACS for EN-DC within FR1 3 CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-214084 | 0962 | 1 | F | Correction of 7.5B.3_1.2 ACS for EN-DC within FR1 4 CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-214085 | 0966 | 1 | F | Update of Applicability for 7.5B.3 ACS for inter-band EN-DC within FR1 2 CCs | 17.1.0 | +| 2021-06 | RAN#92 | R5-214086 | 0981 | 1 | F | Update of applicability for EN-DC Rx tests within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214087 | 0982 | 1 | F | Correction to EN-DC inter-band FR2 test cases 7.3B.2.4_1.x | 17.1.0 | +| 2021-06 | RAN#92 | R5-214094 | 0957 | 1 | F | Update of Applicability for Tx inter-band EN-DC including FR2 under R16 WI | 17.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------|--------| +| 2021-06 | RAN#92 | R5-214095 | 0984 | 1 | F | Update to EN-DC R16 common section | 17.1.0 | +| 2021-09 | RAN#93 | R5-214188 | 1030 | - | F | Update of R17 CADC configurations into TS38.521-3 clause 5 | 17.2.0 | +| 2021-09 | RAN#93 | R5-214280 | 1032 | - | F | Introduction of Rel-15 EN-DC DC_1A_n77A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214281 | 1033 | - | F | Introduction of Rel-15 EN-DC DC_1A_n79A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214282 | 1034 | - | F | Introduction of Rel-15 EN-DC DC_3A_n28A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214283 | 1035 | - | F | Introduction of Rel-15 EN-DC DC_3A_n77A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214290 | 1042 | - | F | Introduction of Rel-15 EN-DC DC_21A_n77A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214291 | 1043 | - | F | Introduction of Rel-15 EN-DC DC_21A_n78A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214292 | 1044 | - | F | Introduction of Rel-15 EN-DC DC_21A_n79A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214293 | 1045 | - | F | Introduction of Rel-15 EN-DC DC_28A_n77A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214296 | 1048 | - | F | Introduction of Rel-15 EN-DC DC_42A_n77A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214298 | 1050 | - | F | Update of Rel-15 EN-DC DC_3A_n79A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214299 | 1051 | - | F | Update of Rel-15 EN-DC DC_5A_n66A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214301 | 1053 | - | F | Update of Rel-15 EN-DC DC_7A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214302 | 1054 | - | F | Update of Rel-15 EN-DC DC_11A_n77A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214303 | 1055 | - | F | Update of Rel-15 EN-DC DC_11A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214304 | 1056 | - | F | Update of Rel-15 EN-DC DC_11A_n79A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214307 | 1059 | - | F | Update of Rel-15 EN-DC DC_26A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214308 | 1060 | - | F | Update of Rel-15 EN-DC DC_39A_n79A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214309 | 1061 | - | F | Update of Rel-15 EN-DC DC_41A_n77A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214310 | 1062 | - | F | Update of Rel-15 EN-DC DC_41A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214311 | 1063 | - | F | Update of Rel-15 EN-DC DC_41A_n79A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214312 | 1064 | - | F | Update of Rel-15 EN-DC DC_66A_n5A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214313 | 1065 | - | F | Update of Rel-15 EN-DC DC_66A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214318 | 1067 | - | F | Update of Rel-16 EN-DC DC_40A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214384 | 1070 | - | F | Update clause 7 for R17 DC RX characteristics in TS 38.521-3 | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-214481 | 1071 | - | F | Update of Applicability and Titles for ACS for EN-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-214483 | 1072 | - | F | Clarification on NSA Option 3 Tx test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214484 | 1073 | - | F | Clarification on NSA Option 3 Rx test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214846 | 1094 | - | F | Correction to EN-DC receiver spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215047 | 1096 | - | F | Correcting references in EN-DC TX test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215061 | 1098 | - | F | Update of REFSENS for inter-band EN-DC 2CC adding DC_28A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215062 | 1099 | - | F | Update of REFSENS for inter-band EN-DC 3CC adding DC_1A-28A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215063 | 1100 | - | F | Update of REFSENS for inter-band EN-DC 3CC adding DC_3A-28A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215194 | 1108 | - | F | Correction to 6.2B.2.1 MPR for intra-band contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215195 | 1109 | - | F | Correction to 6.2B.2.2 MPR for intra-band non-contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215209 | 1113 | - | F | Correction to 6.5B.2.1.1 SEM for intra-band contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215210 | 1114 | - | F | Correction to 6.5B.2.1.3 ACLR for intra-band contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215223 | 1118 | - | F | Correction to 6.5B.3.1.2 and 6.5B.3.2.2 UE co-existence spurious emissions | 17.2.0 | +| 2021-09 | RAN#93 | R5-215228 | 1119 | - | F | Correction to 6.4B.2 in-band emission for intra-band contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215230 | 1120 | - | F | Addition of test case body to 6.5B.5 transmit intermodulation | 17.2.0 | +| 2021-09 | RAN#93 | R5-215232 | 1122 | - | F | Addition of reference sensitivity testing for DC_1A_n28A-n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215233 | 1123 | - | F | Addition of reference sensitivity testing for DC_1A-3A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215234 | 1124 | - | F | Addition of reference sensitivity testing for DC_1A-7A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215235 | 1125 | - | F | Addition of reference sensitivity testing for DC_3A-7A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215254 | 1126 | - | F | Update of reference sensitivity test requirements for DC_41A_n77A and DC_41A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215255 | 1127 | - | F | Correction to reference sensitivity test configuration for 3CC EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215257 | 1129 | - | F | Update of reference sensitivity test coverage for 4CC EN-DC configurations | 17.2.0 | +| 2021-09 | RAN#93 | R5-215266 | 1130 | - | F | Added refsens deltaRIB test case for EN-DC including FR1 and FR2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215292 | 1135 | - | F | Updating 7.3B.2.3 REFSENS testing for DC_3A-20A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215294 | 1136 | - | F | Updating 7.3B.2.3 REFSENS testing for DC_7A-20A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215296 | 1137 | - | F | Editorial correction to clause 7.3B.2.0.3 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215323 | 1138 | - | F | Correction of power control in 38.521-3 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215337 | 1140 | - | F | Correction of test CBW for n28 in 6.2B.1.3 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215376 | 1142 | - | F | Update to EN-DC R15 common section | 17.2.0 | +| 2021-09 | RAN#93 | R5-215378 | 1144 | - | F | Update to EN-DC R17 common section | 17.2.0 | +| 2021-09 | RAN#93 | R5-215379 | 1145 | - | F | Update of R15 EN-DC Tx tests | 17.2.0 | +| 2021-09 | RAN#93 | R5-215380 | 1146 | - | F | Update of applicability and title for R16 EN-DC Tx tests | 17.2.0 | +| 2021-09 | RAN#93 | R5-215381 | 1147 | - | F | Updated to title of clause 6.5B.5.x | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-215460 | 1155 | - | F | Correction of 5.4B.1 for channel spacing for intra-band EN-DC carriers | 17.2.0 | +| 2021-09 | RAN#93 | R5-215521 | 1160 | - | F | Updates to Editors note for spurious emission CA test case | 17.2.0 | +| 2021-09 | RAN#93 | R5-215668 | 1179 | - | F | Correcting references in EN-DC RX test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215673 | 1180 | - | F | EN-DC including FR2 DL CA up to 8 NR CCs REFSENS measurement uncertainties | 17.2.0 | +| 2021-09 | RAN#93 | R5-215804 | 1181 | - | F | Update of 6.5B.2.3 out of band emissions for inter-band EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215832 | 1162 | 1 | F | EN-DC including FR2 DL CA up to 8 NR CCs REFSENS test cases addition | 17.2.0 | +| 2021-09 | RAN#93 | R5-215833 | 1169 | 1 | F | Measurement Uncertainties and test tolerances for NSA FR2 CA Maximum Output Power and Spectrum Emission Mask | 17.2.0 | +| 2021-09 | RAN#93 | R5-215864 | 1038 | 1 | F | Introduction of Rel-15 EN-DC DC_19A_n78A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215865 | 1039 | 1 | F | Introduction of Rel-15 EN-DC DC_19A_n79A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215866 | 1041 | 1 | F | Introduction of Rel-15 EN-DC DC_20A_n78A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215867 | 1047 | 1 | F | Introduction of Rel-15 EN-DC DC_28A_n79A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215868 | 1052 | 1 | F | Update of Rel-15 EN-DC DC_5A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215869 | 1057 | 1 | F | Update of Rel-15 EN-DC DC_25A_n41A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215870 | 1069 | 1 | F | Clarification of SA and NSA support in the UE | 17.2.0 | +| 2021-09 | RAN#93 | R5-215871 | 1074 | 1 | F | Addition of 6.4B.1.3A Frequency Error for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215872 | 1075 | 1 | F | Addition of 6.4B.2.3A.1 Error Vector Magnitude for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215873 | 1076 | 1 | F | Addition of 6.4B.2.3A.2 Carrier Leakage for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215874 | 1077 | 1 | F | Addition of 6.4B.2.3A.3 In-band Emissions for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215875 | 1079 | 1 | F | Addition of 6.5B.2.3A.1 Spectrum emissions mask for Inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215876 | 1080 | 1 | F | Addition of 6.5B.2.3A.2 Additional Spectrum emissions mask for Inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215877 | 1081 | 1 | F | Addition of 6.5B.2.3A.3 Adjacent channel leakage ratio for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215878 | 1082 | 1 | F | Addition of 6.5B.3.3A.1 General Spurious Emissions for Inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215879 | 1084 | 1 | F | Addition of 6.5B.5.3A Transmit Intermodulation for Inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215880 | 1095 | 1 | F | Editorial correction to test applicability in 6.2B.1.4_1.1.1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215881 | 1097 | 1 | F | Addition of spurious emission for DC 1A_n78A and 20A_n78A and 28A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215882 | 1104 | 1 | F | Addition of TC6.3B.2.4D Transmit OFF Power for inter-band EN-DC including FR2 for UL-MIMO | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-215883 | 1106 | 1 | F | Addition of TC6.3B.3.4D Transmit ON/OFF time mask for inter-band EN-DC including FR2 for UL-MIMO | 17.2.0 | +| 2021-09 | RAN#93 | R5-215884 | 1107 | 1 | F | Addition of TC6.3B.4.4 PRACH Time Mask for inter-band EN-DC including FR2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215885 | 1110 | 1 | F | Update of test applicability for 6.2B.2 MPR and 6.2B.3 A-MPR for inter-band EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215886 | 1121 | 1 | F | Update of MOP requirements for DC_3A_n3A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215887 | 1131 | 1 | F | Updated EN-DC spur emissions including FR2 editor notes | 17.2.0 | +| 2021-09 | RAN#93 | R5-215888 | 1156 | 1 | F | Addition of test case 6.4B.2.4.5 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215889 | 1167 | 1 | F | Message content updates for intra-band contiguous EN-DC additional spectrum emission mask test | 17.2.0 | +| 2021-09 | RAN#93 | R5-215890 | 1168 | 1 | F | Message contents addition for intra-band non-contiguous EN-DC SEM, A-SEM and ACLR test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215891 | 1086 | 1 | F | Addition of 7.4B.3A Maximum Input Level for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215892 | 1087 | 1 | F | Addition of 7.5B.3A ACS for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215893 | 1088 | 1 | F | Addition of 7.6B.2.3A In-band blocking for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215894 | 1089 | 1 | F | Addition of 7.6B.4.3A Narrow band blocking for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215895 | 1090 | 1 | F | Addition of 7.8B.2.3A Wide band Intermodulation for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215896 | 1091 | 1 | F | Addition of 7.9B.3A Spurious Emissions for inter-band NE-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215897 | 1093 | 1 | F | Addition of 7.5B.0.4a Inter-band NE-DC including FR2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215898 | 1133 | 1 | F | Updating 7.3B.2.3 REFSENS testing for DC_3A_n28A-n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215899 | 1134 | 1 | F | Updating 7.3B.2.3 REFSENS testing for DC_7A_n28A-n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215900 | 1141 | 1 | F | Editors note correction to reference sensitivity for inter-band EN-DC including FR2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215926 | 1161 | 1 | F | Spurious co-existence corrections for band combo DC_8_n41 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215927 | 1173 | 1 | F | Update for 6.5B.3.3.1 for Rel 16 combos | 17.2.0 | +| 2021-09 | RAN#93 | R5-215928 | 1143 | 1 | F | Update to EN-DC R16 common section | 17.2.0 | +| 2021-09 | RAN#93 | R5-216007 | 1031 | 1 | F | Introduction of Rel-15 EN-DC DC_1A_n28A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-216008 | 1036 | 1 | F | Introduction of Rel-15 EN-DC DC_7A_n28A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-216009 | 1040 | 1 | F | Introduction of Rel-15 EN-DC DC_20A_n28A to spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-216010 | 1058 | 1 | F | Update of Rel-15 EN-DC DC_26A_n77A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-216011 | 1111 | 1 | F | Cleanup for TS 38.521-3 spurious emission for UE co-existence table for Rel-15 | 17.2.0 | +| 2021-09 | RAN#93 | R5-216012 | 1112 | 1 | F | Cleanup for TS 38.521-3 spurious emission for UE co-existence table Rel-16 | 17.2.0 | +| 2021-09 | RAN#93 | R5-216013 | 1170 | 1 | F | Update for 6.5B.3.3.1 for Rel 15 combos | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-216015 | 1117 | 1 | F | Update of general spurious emissions test requirements for Rel-16 inter-band EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-216016 | 1154 | 1 | F | Update of 6.5B.3.3.2.3 for the requirements of spurious emission band UE co-existence limits for Rel-16 | 17.2.0 | +| 2021-09 | RAN#93 | R5-216038 | 1049 | 1 | F | Update of Rel-15 EN-DC DC_1A_n78A in spurious emission test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-216039 | 1182 | 1 | F | Addition of cl 6.2B.1.3A for RF | 17.2.0 | +| 2021-09 | RAN#93 | R5-216093 | 1132 | 1 | F | Updated editors note to indicate missing LO retrieval RRC framework | 17.2.0 | +| 2021-09 | RAN#93 | R5-216094 | 1128 | 1 | F | Update of reference sensitivity test coverage for 3CC EN-DC configurations | 17.2.0 | +| 2021-09 | RAN#93 | R5-216095 | 1178 | 1 | F | Update to Rel.15 EN-DC FR2 Band Combination Tables | 17.2.0 | +| 2021-09 | RAN#93 | R5-216108 | 1171 | 1 | F | Update for reference sensitivity for DC_48A_n66A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216119 | 1115 | 1 | F | Correction to 6.5B.2.2.1 SEM for intra-band non-contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-216120 | 1116 | 1 | F | Correction to 6.5B.2.2.3 ACLR for intra-band non-contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-216131 | 1159 | 1 | F | Spurious co-existence core requirement updates for Dual connectivity including band n28 and other core requirement alignments | 17.2.0 | +| 2021-12 | RAN#94 | R5-216518 | 1184 | - | F | 6.5B.2.2.1 SEM IBNC update as per TP analysis update | 17.3.0 | +| 2021-12 | RAN#94 | R5-216519 | 1185 | - | F | 6.5B.2.2.3 ACLR IBNC update as per TP analysis update | 17.3.0 | +| 2021-12 | RAN#94 | R5-216919 | 1189 | - | F | Addition of TC6.4B.1.4D Frequency error for inter-band EN-DC including FR2 for UL-MIMO | 17.3.0 | +| 2021-12 | RAN#94 | R5-217094 | 1191 | - | F | Update of Reference Sensitivity Test Cases for EN-DC with FR2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217116 | 1192 | - | F | FR2 EN-DC Refsens 6 to 8 NR CCs - Editorial correction | 17.3.0 | +| 2021-12 | RAN#94 | R5-217117 | 1193 | - | F | UL modulation correction in 7.3B.2.3_1.1 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217176 | 1195 | - | F | Adding Power Class 1.5 for LTE Band 41 and NR Band n41 to Annex N.1 Indication of modified MPR behaviour | 17.3.0 | +| 2021-12 | RAN#94 | R5-217232 | 1199 | - | F | Tx Spurious emission-Editorial corrections | 17.3.0 | +| 2021-12 | RAN#94 | R5-217295 | 1202 | - | F | Update of 6.5B.2.1.1 SEM test configuration for intra-band contiguous EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-217296 | 1203 | - | F | Update of 6.2B.2.1 MPR for intra-band contiguous EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-217300 | 1204 | - | F | Addition of reference sensitivity testing for DC_20A_n28A-n78A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217305 | 1206 | - | F | Addition of 4Rx reference sensitivity test requirements for DC_3A_n41A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217382 | 1211 | - | F | Addition of 6.2E.1.1 MOP for intra-band contiguous V2X operation | 17.3.0 | +| 2021-12 | RAN#94 | R5-217383 | 1212 | - | F | Addition of 6.2E.1.2 MOP for intra-band non-contiguous V2X operation | 17.3.0 | +| 2021-12 | RAN#94 | R5-217384 | 1213 | - | F | Addition of 6.2E.1.3.1 MOP for inter-band E-UTRA Uu and NR Sidelink operation | 17.3.0 | +| 2021-12 | RAN#94 | R5-217385 | 1214 | - | F | Addition of 6.2E.1.3.2 MOP for inter-band NR Uu and E-UTRA V2X Sidelink operation | 17.3.0 | +| 2021-12 | RAN#94 | R5-217386 | 1215 | - | F | Addition of 6.2E.2.1 MPR for intra-band V2X operation | 17.3.0 | +| 2021-12 | RAN#94 | R5-217387 | 1216 | - | F | Addition of 6.2E.2.2.1 MPR for inter-band E-UTRA Uu and NR Sidelink operation | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------|--------| +| 2021-12 | RAN#94 | R5-217388 | 1217 | - | F | Addition of 6.2E.2.2.2 MPR for inter-band NR Uu and E-UTRA V2X Sidelink operation | 17.3.0 | +| 2021-12 | RAN#94 | R5-217389 | 1218 | - | F | Addition of 6.3E Output power dynamics for V2X | 17.3.0 | +| 2021-12 | RAN#94 | R5-217428 | 1220 | - | F | Correction to note of DC_1_n3 and DC_3_n1 in 6.5B.3.3.2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217554 | 1228 | - | F | Correction of Reference Sensitivity for DC_28A_n41A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217562 | 1229 | - | F | Update of modulation quality for inter-band EN-DC with FR2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217610 | 1230 | - | F | Correction to 5G V2X common sections | 17.3.0 | +| 2021-12 | RAN#94 | R5-217615 | 1231 | - | F | Addition of R15 EN-DC configurations in clause 5 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217616 | 1232 | - | F | Correction to EN-DC Tx test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-217617 | 1233 | - | F | Correction to title and test applicability to EN-DC Rx test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-217705 | 1237 | - | F | 38.521-3 Beam correspondence Measurement Uncertainties | 17.3.0 | +| 2021-12 | RAN#94 | R5-217720 | 1238 | - | F | Introduction of EN-DC FR2 Beam Correspondence Test Case | 17.3.0 | +| 2021-12 | RAN#94 | R5-217724 | 1239 | - | F | Update to Rel.17 EN-DC FR2 Band Combination Tables | 17.3.0 | +| 2021-12 | RAN#94 | R5-217726 | 1241 | - | F | Update to Rel.15 EN-DC FR2 Band Combination Tables | 17.3.0 | +| 2021-12 | RAN#94 | R5-217740 | 1242 | - | F | Correction to DC_1A_n79A spurious emission test case 6.5B.3.3.2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217741 | 1243 | - | F | Correction of spurious emission test case 6.5B.3.3.2 for DC_5A-n66A, DC_25A-n41A and DC_19A_n77A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218211 | 1250 | - | F | Adding new test case spurious UE coex for inter-band EN-DC including FR2 and editors note updates | 17.3.0 | +| 2021-12 | RAN#94 | R5-218243 | 1207 | 1 | F | Update of 6.5B.3.3.1 general spurious emissions test requirements for inter-band EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-218244 | 1205 | 1 | F | Addition of 4Rx reference sensitivity test requirements for DC_3A_n78A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218245 | 1221 | 1 | F | Correction to test configuration of DC_41A_n78A in 7.3B.2.3 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218246 | 1188 | 1 | F | Handling of fallbacks for FR2 CA for EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-218247 | 1210 | 1 | F | Correction of clause 4 for minimum requirements and test applicability rules | 17.3.0 | +| 2021-12 | RAN#94 | R5-218271 | 1197 | 1 | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence | 17.3.0 | +| 2021-12 | RAN#94 | R5-218273 | 1249 | 1 | F | Adding RX requirements for Rel-16 FR1 EN-DC band combinations | 17.3.0 | +| 2021-12 | RAN#94 | R5-218274 | 1234 | 1 | F | Addition of R16 EN-DC configurations in clause 5 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218275 | 1240 | 1 | F | Update to Rel.16 EN-DC FR2 Band Combination Tables | 17.3.0 | +| 2021-12 | RAN#94 | R5-218293 | 1208 | 1 | F | Adding UL switching time mask test for inter-band EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-218433 | 1183 | 1 | F | 6.2B.2.2 MPR IBNC update as per TP analysis update | 17.3.0 | +| 2021-12 | RAN#94 | R5-218434 | 1236 | 1 | F | Update of test case 6.2B.3.4 EN-DC A-MPR for FR2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218455 | 1200 | 1 | F | Update for EN_DC reference sensitivity_r16 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218472 | 1227 | 1 | F | Updating 6.2B.1.3 UE Maximum Output Power for Rel-17 NR inter-band EN-DC configurations | 17.3.0 | +| 2021-12 | RAN#94 | R5-218473 | 1226 | 1 | F | Updating Rel-17 NR inter-band EN-DC configurations | 17.3.0 | +| 2021-12 | RAN#94 | R5-218485 | 1225 | 1 | F | Clarification on cl 4.5.1 test coverage across 5G NR architecture options for RF | 17.3.0 | +| 2022-03 | RAN#95 | R5-220063 | 1251 | - | F | Correction of Test applicability of 6.2B.2.3 | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | RAN#95 | R5-220068 | 1254 | - | F | Correction of test config table for 6.3B.3_1.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220069 | 1255 | - | F | Correction of reference section numbers in 6.4B.2.4.5.4.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220070 | 1256 | - | F | Correction of Editor Note and reference section numbers in 6.5B.3.4.2_1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220087 | 1257 | - | F | Introduction of new V2X test cases in 7.6E | 17.4.0 | +| 2022-03 | RAN#95 | R5-220088 | 1258 | - | F | Introduction of new V2X test cases in 7.7E | 17.4.0 | +| 2022-03 | RAN#95 | R5-220089 | 1259 | - | F | Introduction of new V2X test cases in 7.8E | 17.4.0 | +| 2022-03 | RAN#95 | R5-220260 | 1260 | - | F | FR1 NSA IBC - ACLR clean up to leverage MPR test definition | 17.4.0 | +| 2022-03 | RAN#95 | R5-220275 | 1261 | - | F | Clarifications on 5G NR connectivity options for RF FR1 and FR2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220314 | 1264 | - | F | Introduction of Output power requirements for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-220315 | 1265 | - | F | Introduction of General Spurious emissions requirements for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-220322 | 1267 | - | F | Adding Reference sensitivity exceptions and MSD test points for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-220323 | 1268 | - | F | Adding reference sensitivity requirements for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-220369 | 1270 | - | F | Update general spurious emissions 6.5B.3.3.1 for 4 Rel-17 ENDC combos | 17.4.0 | +| 2022-03 | RAN#95 | R5-220371 | 1271 | - | F | Update for 6.5B.3.3.2 Spurious emission band UE co-existence for 4 Rel-17 combos | 17.4.0 | +| 2022-03 | RAN#95 | R5-220380 | 1273 | - | F | Introduction of DC_1A-n5A reference sensitivity test requirements | 17.4.0 | +| 2022-03 | RAN#95 | R5-220382 | 1274 | - | F | Introduction of DC_3A-n5A reference sensitivity test requirements | 17.4.0 | +| 2022-03 | RAN#95 | R5-220384 | 1275 | - | F | Introduction of DC_7A-n5A reference sensitivity test requirements | 17.4.0 | +| 2022-03 | RAN#95 | R5-220387 | 1276 | - | F | Introduction of DC_7A-n78A reference sensitivity test requirements | 17.4.0 | +| 2022-03 | RAN#95 | R5-220390 | 1277 | - | F | Introduction of DC_28A_n7A-n78A reference sensitivity test requirements | 17.4.0 | +| 2022-03 | RAN#95 | R5-220431 | 1280 | - | F | Update to R16 Configuration for DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220432 | 1281 | - | F | Update to R17 Configuration for DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220538 | 1282 | - | F | Correction on test requirements for TC 6.5B.3.3.2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220539 | 1283 | - | F | Addition of 6.4E.1 Frequency error for V2X | 17.4.0 | +| 2022-03 | RAN#95 | R5-220540 | 1284 | - | F | Addition of 6.4E.2.1 Error Vector Magnitude for V2X | 17.4.0 | +| 2022-03 | RAN#95 | R5-220655 | 1286 | - | F | Adding RIB,c for Inter-band NE-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221698 | 1289 | 1 | F | Updating on 6.5B.3.3.2 Spurious emission for UE co-existence for inter-band within FR1 including n1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220759 | 1290 | - | F | Introduction of maximum output power test requirements for DC_1A_n5A, DC_1A_n7A, DC_3A_n5A, DC_7A_n5A and DC_28A_n7A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220766 | 1291 | - | F | Update Tx test cases for DC_n28A_3A, DC_n28A_3C, DC_n28A_39A, DC_n28A_39C | 17.4.0 | +| 2022-03 | RAN#95 | R5-220896 | 1296 | - | F | Definition of MTSU for 7.6B.3.3_1.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220902 | 1298 | - | F | Correction to measurement timing for EN-DC combination with FDD and TDD | 17.4.0 | +| 2022-03 | RAN#95 | R5-220904 | 1299 | - | F | Correction to test frequency of EN-DC 28_n51 in 7.3B.2.3 | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------|--------| +| 2022-03 | RAN#95 | R5-220961 | 1301 | - | F | Addition of common uplink configuration for E-UTRA intra-band contiguous CA | 17.4.0 | +| 2022-03 | RAN#95 | R5-220967 | 1305 | - | F | Update of 6.2B.1.3 Maximum Output Power for Inter-Band EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220968 | 1306 | - | F | Update of 6.2B.4.1.3 Configured Output Power for Inter-Band EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220976 | 1308 | - | F | Correction to reference sensitivity for intra-band contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220977 | 1309 | - | F | Correction to Maximum Input Level for intra-band contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220978 | 1310 | - | F | Correction to Adjacent Channel Selectivity for intra-band contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220979 | 1311 | - | F | Update of Adjacent Channel Selectivity for intra-band non-contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220980 | 1312 | - | F | Correction to out-of-band blocking for intra-band contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220981 | 1313 | - | F | Update of Annex F for Adjacent Channel Selectivity for intra-band EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221053 | 1314 | - | F | Correction of 6.2B.1.1 for intra-band contiguous EN-DC maximum output power | 17.4.0 | +| 2022-03 | RAN#95 | R5-221170 | 1316 | - | F | Addition of 6.2B.2.3a MPR for inter-band NE-DC within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221171 | 1317 | - | F | Addition of 6.4B.2.3a.4 EVM Equalizer Flatness for inter-band NE-DC within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221172 | 1318 | - | F | Addition of 6.2B.4.2.3a TIB,c for Inter-band NE-DC within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221268 | 1323 | - | F | Update of E-UTRA configuration | 17.4.0 | +| 2022-03 | RAN#95 | R5-221317 | 1326 | - | F | Update for 6.5B.4.2 Additional Spurious Emissions for Intra-band non-contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221321 | 1327 | - | F | Update for reference sensitivity for EN_DC_r15 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221325 | 1328 | - | F | Editorial Update for 6.2B.4.2.3.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221329 | 1330 | - | F | Update Ref sense for r16 DC combos | 17.4.0 | +| 2022-03 | RAN#95 | R5-221337 | 1332 | - | F | Addition of PC2 ENDC 4 combos into 38.521-3 TC7.3B.2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221693 | 1252 | 1 | F | Correction of Test applicability of 6.2B.3.3 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221694 | 1253 | 1 | F | Correction of 6.5B.2.3.3 to include 6.5.2.4.2 of 38.521-1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221695 | 1262 | 1 | F | Update MOP for inter-band NE-DC within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221696 | 1269 | 1 | F | FR2 NSA EVM test case editor notes update | 17.4.0 | +| 2022-03 | RAN#95 | R5-221697 | 1287 | 1 | F | Clarification on clause number of NE-DC for Tx test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-221699 | 1293 | 1 | F | Correction of ON OFF time mask for inter-band EN-DC including FR2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221700 | 1294 | 1 | F | Definition of MTSU and TT for Intra-band EN-DC additional spurious emissions test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-221701 | 1295 | 1 | F | Correction to test procedure of FR1 EN-DC Spurious test for EN-DC only capable UE | 17.4.0 | +| 2022-03 | RAN#95 | R5-221702 | 1324 | 1 | F | Editorial correction for 6.5B.3.3 Spurious emission | 17.4.0 | +| 2022-03 | RAN#95 | R5-221703 | 1288 | 1 | F | Clarification on clause number of NE-DC for Rx test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-221704 | 1331 | 1 | F | Update for 7.3B.2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221705 | 1278 | 1 | F | Regrouping DC Configuration in clause 5 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221706 | 1315 | 1 | F | Update of 3.2 and 3.3 on symbols and abbreviations | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | RAN#95 | R5-221767 | 1266 | 1 | F | Introduction of Spurious emissions band UE co-existence requirements for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-221768 | 1297 | 1 | F | Correction to test requirement of DC_xxA_n41A in 6.5B.3.3.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221769 | 1300 | 1 | F | Correction of General Spurious emissions requirements for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-221770 | 1320 | 1 | F | Introduction of DC_1A_n5A, DC_1A_n7A, DC_3A_n5A, DC_7A_n5A, DC_28A_n7A to general spurious emission test case | 17.4.0 | +| 2022-03 | RAN#95 | R5-221771 | 1321 | 1 | F | Introduction of DC_1A_n5A, DC_1A_n7A, DC_3A_n5A, DC_7A_n5A, DC_28A_n7A to UE co-existence spurious emission test case | 17.4.0 | +| 2022-03 | RAN#95 | R5-221772 | 1322 | 1 | F | Addition of new CADC MPR TC 6.2B.2.4_1.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221773 | 1329 | 1 | F | Update for 7.3B.2.0 Min Requirements of Ref sensitivity for EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221883 | 1272 | 1 | F | Update Tx TC for 4 Rel-17 combos | 17.4.0 | +| 2022-03 | RAN#95 | R5-221884 | 1325 | 1 | F | Update Rx Requirements for 4 Rel-17 ENDC combos | 17.4.0 | +| 2022-03 | RAN#95 | R5-221885 | 1333 | 1 | F | MSD test configurations modification for US inter-band EN-DC combinations with n77 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221886 | 1285 | 1 | F | Update NE-DC configurations for DC_n28A_3A, DC_n28A_3C, DC_n28A_39A, DC_n28A_39C | 17.4.0 | +| 2022-03 | RAN#95 | R5-221892 | 1292 | 1 | F | Update of MOP TC for PC2 ENDC configurations | 17.4.0 | +| 2022-03 | RAN#95 | R5-221908 | 1302 | 1 | F | Addition of new test case 6.2B.1.3_1 for Maximum Output Power for inter-band EN-DC with 3 uplink | 17.4.0 | +| 2022-03 | RAN#95 | R5-221909 | 1303 | 1 | F | Addition of new test case 6.2B.4.1.3_1 for Configured Output Power for inter-band EN-DC with 3 uplink | 17.4.0 | +| 2022-03 | RAN#95 | R5-221910 | 1304 | 1 | F | Addition of annex F for test cases for EN-DC configurations with 3 uplink | 17.4.0 | +| 2022-03 | RAN#95 | R5-221931 | 1307 | 1 | F | Addition of transmit power configuration for EN-DC reference sensitivity | 17.4.0 | +| 2022-06 | RAN#96 | R5-222192 | 1335 | - | F | Correction of minimum requirement and test requirement of 6.2B.1.3 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222194 | 1337 | - | F | Correction of reference section numbers in 6.4E and title of 6.4E.2.1.2 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222195 | 1338 | - | F | Correction of test requirement of 6.2B.2.1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222196 | 1339 | - | F | Separation of 6.2B.1.4D into two test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-222197 | 1340 | - | F | Correction of clause numbers in 6.2B.1.3a | 17.5.0 | +| 2022-06 | RAN#96 | R5-222344 | 1353 | - | F | 6.6B.4 Beam Correspondence test case editor note update | 17.5.0 | +| 2022-06 | RAN#96 | R5-222345 | 1354 | - | F | MU and TT definition and clean up in 38.521-3 annex F | 17.5.0 | +| 2022-06 | RAN#96 | R5-222421 | 1355 | - | F | Addition of 6.5E.1 Occupied bandwidth for V2X | 17.5.0 | +| 2022-06 | RAN#96 | R5-222422 | 1356 | - | F | Addition of 6.5E.2 Out of band emission for V2X | 17.5.0 | +| 2022-06 | RAN#96 | R5-222473 | 1359 | - | F | Addition Delta TIB,c for FR1 EN-DC | 17.5.0 | +| 2022-06 | RAN#96 | R5-222484 | 1362 | - | F | Editorial correction in 6.2B.4.1.3 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222486 | 1363 | - | F | Correction about test configuration in 6.5B.3.3.2 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222487 | 1364 | - | F | Correction to title of 7.6B.2.4 and editorial correction for Rx test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-222543 | 1365 | - | F | Correction of Refsens CA test case | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-06 | RAN#96 | R5-222700 | 1367 | - | F | Editorial correction to EN-DC test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-222702 | 1368 | - | F | Update to R15 common part and DC configurations in clause 5 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222703 | 1369 | - | F | Update to R16 Configuration for DC | 17.5.0 | +| 2022-06 | RAN#96 | R5-222743 | 1379 | - | F | Update for 7.3B.2.0 Min Requirements of Ref sensitivity for EN-DC | 17.5.0 | +| 2022-06 | RAN#96 | R5-222748 | 1381 | - | F | Update 6.5B.3.3.2 for R17 DC_14_n2 and DC_14_n66 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222829 | 1382 | - | F | Update of 6.2B.1.3_1 UE Maximum Output Power for inter-Band EN-DC with 2 E-UTRA CCs and 1 NR CC | 17.5.0 | +| 2022-06 | RAN#96 | R5-222830 | 1383 | - | F | Update of 6.2B.4.1.3_1 Configured Output Power for inter-Band EN-DC with 2 E-UTRA CCs and 1 NR CC | 17.5.0 | +| 2022-06 | RAN#96 | R5-222884 | 1386 | - | F | Addition of 6.4E.2.3 In-band emissions for V2X | 17.5.0 | +| 2022-06 | RAN#96 | R5-223061 | 1387 | - | F | Addition of 6.5B.3.3.1 requirements for NR inter-band EN-DC configurations including n1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223231 | 1389 | - | F | Correction to 6.2B.1.3 for UE capability IE for inter-band EN-DC UE maximum output power | 17.5.0 | +| 2022-06 | RAN#96 | R5-223245 | 1391 | - | F | Add delta RIBc for inter-band DC_28A_n7A-n78A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223658 | 1341 | 1 | F | Introduction of Output power requirements for DC_1A_n8A, DC_7A_n8A and DC_8A_n28A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223659 | 1342 | 1 | F | Introduction of Allowed maximum configured output power relaxation for DC_1_n5, DC_1_n8, DC_3_n5, DC_7_n5, DC_7_n8 and DC_8_n28 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223660 | 1343 | 1 | F | Introduction of General Spurious emissions requirements for DC_1A_n8A, DC_7A_n8A, DC_8A_n28A and DC_20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223661 | 1344 | 1 | F | Introduction of Spurious emissions band UE co-existence limits Rel-16 for DC_1A_n8A, DC_7A_n8A, DC_8A_n28A and DC_20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223662 | 1345 | 1 | F | Introduction of Spurious emissions band UE co-existence Test description for DC_1A_n8A, DC_7A_n5A, DC_7A_n8A, DC_8A_n28A and DC_20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223663 | 1346 | 1 | F | Introduction of Spurious emissions band UE co-existence Rel-16 Test requirements for DC_1A_n8A, DC_7A_n8A, DC_8A_n28A and DC_20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223664 | 1366 | 1 | F | Addition of new CADC MOP TC | 17.5.0 | +| 2022-06 | RAN#96 | R5-223665 | 1371 | 1 | F | Addition of ACLR Test Case for Inter-band EN-DC including FR2 5 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223666 | 1372 | 1 | F | Addition of ACLR Test Case for Inter-band EN-DC including FR2 6 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223667 | 1373 | 1 | F | Addition of ACLR Test Case for Inter-band EN-DC including FR2 7 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223668 | 1374 | 1 | F | Addition of ACLR Test Case for Inter-band EN-DC including FR2 8 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223669 | 1375 | 1 | F | Addition of General Spurious Emissions Test Case for Inter-band EN-DC including FR2 5 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223670 | 1376 | 1 | F | Addition of General Spurious Emissions Test Case for Inter-band EN-DC including FR2 6 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223671 | 1377 | 1 | F | Addition of General Spurious Emissions Test Case for Inter-band EN-DC including FR2 7 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223672 | 1378 | 1 | F | Addition of General Spurious Emissions Test Case for Inter-band EN-DC including FR2 8 NR CCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223673 | 1380 | 1 | F | Update 6.5B.3.3.2 for R16 DC_14_n2 and DC_14_n66 | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------|--------| +| 2022-06 | RAN#96 | R5-223674 | 1390 | 1 | F | Add delta TIBc for inter-band DC_28A_n7A-n78A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223675 | 1393 | 1 | F | Introduction of Allowed reference sensitivity relaxation for DC_3A-8A_n28A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223676 | 1347 | 1 | F | Introduction of DC_1A-20A_n8A reference sensitivity test requirements | 17.5.0 | +| 2022-06 | RAN#96 | R5-223677 | 1348 | 1 | F | Introduction of DC_3A-7A_n5A reference sensitivity test requirements | 17.5.0 | +| 2022-06 | RAN#96 | R5-223678 | 1349 | 1 | F | Introduction of DC_7A-8A_n3A reference sensitivity test requirements | 17.5.0 | +| 2022-06 | RAN#96 | R5-223679 | 1350 | 1 | F | Introduction of DC_7A-20A_n8A reference sensitivity test requirements | 17.5.0 | +| 2022-06 | RAN#96 | R5-223680 | 1351 | 1 | F | Introduction of DC_7A-28A_n5A reference sensitivity test requirements | 17.5.0 | +| 2022-06 | RAN#96 | R5-223681 | 1360 | 1 | F | Addition Minimum Conformance Requests of REFSSENS for FR1 EN-DC | 17.5.0 | +| 2022-06 | RAN#96 | R5-223703 | 1385 | 1 | F | Addition of 6.4E.2.2 Carrier leakage for V2X | 17.5.0 | +| 2022-06 | RAN#96 | R5-223744 | 1370 | 1 | F | Update to R17 Configuration for DC | 17.5.0 | +| 2022-06 | RAN#96 | R5-223833 | 1336 | 1 | F | Correction of Transmitter power test requirements for EN-DC within FR1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223834 | 1357 | 1 | F | Editorial correction for 6.3B.8 Power control for EN-DC | 17.5.0 | +| 2022-06 | RAN#96 | R5-223835 | 1358 | 1 | F | Clarifications on Common Uplink Configuration updates | 17.5.0 | +| 2022-06 | RAN#96 | R5-223836 | 1384 | 1 | F | Adding missing configurations in SE co-ex Rel-17 table | 17.5.0 | +| 2022-09 | RAN#97 | R5-224152 | 1398 | - | F | Introduction of Allowed maximum configured output power relaxation for DC_3_n8 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224153 | 1399 | - | F | Introduction of General Spurious emissions requirements for DC_3A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224154 | 1400 | - | F | Introduction of Spurious emissions band UE co-existence limits Rel-16 for DC_3A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224156 | 1402 | - | F | Introduction of Spurious emissions band UE co-existence Rel-16 Test requirements for DC_3A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224159 | 1403 | - | F | Introduction of DC_3A-7A-20A_n8A reference sensitivity 2-band fallback test requirements | 17.6.0 | +| 2022-09 | RAN#97 | R5-224160 | 1404 | - | F | Introduction of DC_3A-7A-20A_n8A reference sensitivity 3-band fallback test requirements | 17.6.0 | +| 2022-09 | RAN#97 | R5-224161 | 1405 | - | F | Introduction of Allowed reference sensitivity relaxation for DC_3A-7A-20A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224308 | 1408 | - | F | FR2 NSA EVM test case editor notes update | 17.6.0 | +| 2022-09 | RAN#97 | R5-224437 | 1412 | - | F | Addition of new CADC MOP TC | 17.6.0 | +| 2022-09 | RAN#97 | R5-224622 | 1413 | - | F | Addition of test requirement for E-UTRA cell of PC2 UE in 6.2B.4.1 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224626 | 1414 | - | F | Correction to test frequency definition for DC combination including n28 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224629 | 1415 | - | F | Correction to E-UTRA output power in intra-band contiguous EN-DC Rx test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224653 | 1417 | - | F | Correction of reference to test configuration table for intra band contiguous EN-DC test case | 17.6.0 | +| 2022-09 | RAN#97 | R5-224809 | 1418 | - | F | Editorial correction for 6.2B.1.3 Maximum output power for Inter-band EN-DC within FR1 | 17.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-09 | RAN#97 | R5-224936 | 1423 | - | F | Corrections on test configuration table in spurious emission band UE co-existence for Rel-15 inter-band EN-DC configuration | 17.6.0 | +| 2022-09 | RAN#97 | R5-224939 | 1425 | - | F | Introduction of DC_2A-66A_n41A reference sensitivity test requirements | 17.6.0 | +| 2022-09 | RAN#97 | R5-224942 | 1426 | - | F | Corrections on general spurious emission test requirements for DC_2A_n5A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224943 | 1427 | - | F | Update of Rel-16 EN-DC configuration DC_2A_n41A in spurious emission test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224946 | 1428 | - | F | Update of DC_8A_n41A, DC_3A_n41A, DC_25A_n41A, DC_26A_n41A, DC_39A_n41A and DC_40A_n41A in spurious emission test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224950 | 1429 | - | F | Update of Rel-16 EN-DC configuration DC_48A_n5A in spurious emission test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224952 | 1430 | - | F | Update of Rel-16 EN-DC configuration DC_48A_n66A in spurious emission test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224954 | 1431 | - | F | Update of Rel-16 EN-DC configuration DC_66A_n41A in spurious emission test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225000 | 1434 | - | F | Update to R16 Configuration for DC | 17.6.0 | +| 2022-09 | RAN#97 | R5-225001 | 1435 | - | F | Update to R17 Configuration for DC | 17.6.0 | +| 2022-09 | RAN#97 | R5-225005 | 1436 | - | F | Editorial correction to reference table ID to TC6.2B.1.3 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225006 | 1437 | - | F | Update to test case 6.5B.3.3.2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225031 | 1438 | - | F | Add EN-DC Enhanced Beam Correspondence Test Case | 17.6.0 | +| 2022-09 | RAN#97 | R5-225661 | 1394 | 1 | F | New test case addition: 6.2B.4.1.4_1 Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC). | 17.6.0 | +| 2022-09 | RAN#97 | R5-225662 | 1395 | 1 | F | Measurement uncertainties and test tolerances for test case 6.2B.4.1.4_1 Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC) | 17.6.0 | +| 2022-09 | RAN#97 | R5-225668 | 1409 | 1 | F | PC1 MU - General Editor notes update in 38.521-3 FR2 Rx tests | 17.6.0 | +| 2022-09 | RAN#97 | R5-225669 | 1396 | 1 | F | Rel-15 Beam correspondence test tolerance definition | 17.6.0 | +| 2022-09 | RAN#97 | R5-225678 | 1410 | 1 | F | Update of FR2 5CC to 8CCs Transmission Test Cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225705 | 1397 | 1 | F | Introduction of Output power requirements for DC_3A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225706 | 1401 | 1 | F | Introduction of Spurious emissions band UE co-existence Test description for DC_3A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225707 | 1419 | 1 | F | Update 6.5B.3.3.2 for DC_5A_n2A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225708 | 1424 | 1 | F | Corrections on test configuration table in spurious emission band UE co-existence for Rel-16 inter-band EN-DC configuration | 17.6.0 | +| 2022-09 | RAN#97 | R5-225709 | 1421 | 1 | F | Update for reference sensitivity for DC_48A_n66A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225736 | 1422 | 1 | F | Update for reference sensitivity for DC_5A_n77A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225799 | 1406 | 1 | F | Correction of Power Class 2 test requirements in 6.2B.1.3.5 for Interband EN-DC FDD and TDD Duplex-mode | 17.6.0 | +| 2022-09 | RAN#97 | R5-225800 | 1411 | 1 | F | Replacing the word LTE by E-UTRA in description of exception requirement | 17.6.0 | +| 2022-09 | RAN#97 | R5-225801 | 1439 | 1 | F | Removal of brackets for DCI format for Tx test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225802 | 1445 | 1 | F | Introduction of test section for UL MIMO EN-DC MPR with FR1 and FR2 | 17.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-09 | RAN#97 | R5-225803 | 1446 | 1 | F | Introduction of test section for UL MIMO EN-DC A-MPR with FR1 and FR2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225804 | 1447 | 1 | F | Introduction of test case for UL MIMO EN-DC MPR in FR2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225805 | 1448 | 1 | F | Introduction of test case for UL MIMO EN-DC A-MPR in FR2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225806 | 1449 | 1 | F | P-MaxUE-FR1-r15 correction for PC2 ENDC test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225807 | 1420 | 1 | F | Update for ref sensitivity for R15_combos | 17.6.0 | +| 2022-09 | RAN#97 | R5-225808 | 1441 | 1 | F | Correction of reference sensitivity test case | 17.6.0 | +| 2022-09 | RAN#97 | R5-225881 | 1440 | 1 | F | Addition of new test case additional spurious for FR2 | 17.6.0 | +| 2022-12 | RAN#98 | R5-226296 | 1451 | | F | Move 6.5B.4.4 which is in front of 6.5B.3.5 to be after 6.5B.4.3 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226297 | 1452 | | F | Clause styles and clause number correction in 6.6B.5 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226480 | 1454 | | F | Introduction of reference sensitivity for three bands within FR1 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226744 | 1462 | | F | Clean-up pending R15 configurations in clause 5.3 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226746 | 1464 | | F | Clean-up pending R16 configurations in clause 5 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226747 | 1465 | | F | Clean-up pending R17 configurations in clause 5 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226749 | 1467 | | F | Clean-up pending R16 configurations in clause 6 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226750 | 1468 | | F | Clean-up pending R17 configurations in clause 6 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226751 | 1469 | | F | Clean-up pending R15 configurations in clause 7 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226752 | 1470 | | F | Clean-up pending R16 configurations in clause 7 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226754 | 1471 | | F | Editorial correction to the wording used for NR FRx | 17.7.0 | +| 2022-12 | RAN#98 | R5-226761 | 1472 | | F | Editorial correction to editor note of completed TC6.3B.1.4_1.x minimum output power for EN-DC FR2 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226815 | 1473 | | F | Update of FR2 Test Case 6.4B.2.4.4 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226886 | 1474 | | F | New test case addition: 6.4B.2.4.1a Error Vector Magnitude with Power Boost for inter-band EN-DC including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-226887 | 1475 | | F | New test case addition: 6.5B.2.4.1a Spectrum emissions mask with Power Boost for Inter-band EN-DC including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-226888 | 1476 | | F | New test case addition: 6.5B.3.4.1a General Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-226889 | 1477 | | F | New test case addition: 6.5B.3.4.2a Spurious emission band UE co-existence with Power Boost for Inter-band including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-226890 | 1478 | | F | New test case addition: 6.5B.4.4a Additional Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-226939 | 1479 | | F | New test case addition: 6.2B.2.4a UE maximum output power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-226941 | 1480 | | F | Measurement uncertainties and test tolerances for mpr-PowerBoost tests 6.4B.2.4.1a, 6.5B.2.4.1a, 6.5B.3.4.1a, 6.5B.3.4.2a and 6.5B.4.4a | 17.7.0 | +| 2022-12 | RAN#98 | R5-226994 | 1481 | | F | Measurement uncertainties and test tolerances for test 6.2B.2.4a UE maximum output power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) | 17.7.0 | +| 2022-12 | RAN#98 | R5-227085 | 1495 | | F | Correction to test description of 6.2B.1.4D.1 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227284 | 1498 | | F | Corrections on reference sensitivity test requirements for EN-DC configurations | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98 | R5-227285 | 1499 | | F | Corrections on reference sensitivity test requirements on TT for DC_28A_n7A-n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227286 | 1500 | | F | Corrections on reference sensitivity test requirements on TT for R15 EN-DC configurations | 17.7.0 | +| 2022-12 | RAN#98 | R5-227287 | 1501 | | F | Corrections on REFSEN for inter-band CA configurations | 17.7.0 | +| 2022-12 | RAN#98 | R5-227289 | 1503 | | F | Corrections on test configuration table in spurious emission band UE co-existence for Rel-17 inter-band EN-DC configuration | 17.7.0 | +| 2022-12 | RAN#98 | R5-227290 | 1504 | | F | Corrections on general description for MSD test frequencies | 17.7.0 | +| 2022-12 | RAN#98 | R5-227786 | 1456 | 1 | F | 7.3B.2 cleaning up_R16 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227787 | 1466 | 1 | F | Clean-up pending R15 configurations in clause 6 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227788 | 1458 | 1 | F | Update Ref sense for R15 combos | 17.7.0 | +| 2022-12 | RAN#98 | R5-227789 | 1507 | 1 | F | Updated to clause 5 for simultaneous RxTx clarification | 17.7.0 | +| 2022-12 | RAN#98 | R5-227790 | 1453 | 1 | F | Update some frequency selections in test configuration table | 17.7.0 | +| 2022-12 | RAN#98 | R5-227791 | 1482 | 1 | F | Addition of new test case 6.3B.1.4_1.4 Minimum output power for inter-band EN-DC including FR2 - 5 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227792 | 1483 | 1 | F | Addition of new test case 6.3B.1.4_1.5 Minimum output power for inter-band EN-DC including FR2 - 6 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227793 | 1484 | 1 | F | Addition of new test case 6.3B.1.4_1.6 Minimum output power for inter-band EN-DC including FR2 - 7 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227794 | 1485 | 1 | F | Addition of new test case 6.3B.1.4_1.7 Minimum output power for inter-band EN-DC including FR2 - 8 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227795 | 1486 | 1 | F | Addition of new test case 6.4B.2.4.1_1.4 Error Vector Magnitude for inter-band EN-DC including FR2 - 5 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227796 | 1487 | 1 | F | Addition of new test case 6.4B.2.4.1_1.5 Error Vector Magnitude for inter-band EN-DC including FR2 - 6 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227797 | 1488 | 1 | F | Addition of new test case 6.4B.2.4.1_1.6 Error Vector Magnitude for inter-band EN-DC including FR2 - 7 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227798 | 1489 | 1 | F | Addition of new test case 6.4B.2.4.1_1.7 Error Vector Magnitude for inter-band EN-DC including FR2 - 8 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227799 | 1490 | 1 | F | Addition of new test case 6.4B.2.4.2_1.4 Carrier Leakage for inter-band EN-DC including FR2 - 5 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227800 | 1491 | 1 | F | Addition of new test case 6.4B.2.4.2_1.5 Carrier Leakage for inter-band EN-DC including FR2 - 6 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227801 | 1492 | 1 | F | Addition of new test case 6.4B.2.4.2_1.6 Carrier Leakage for inter-band EN-DC including FR2 - 7 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227802 | 1493 | 1 | F | Addition of new test case 6.4B.2.4.2_1.7 Carrier Leakage for inter-band EN-DC including FR2 - 8 NR CCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-227803 | 1455 | 1 | F | Introduction of spurious emissions test cases for 18A_n77A and 18A_n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227804 | 1497 | 1 | F | Corrections on MOP band edge relaxation for intra-band contiguous and non-contiguous EN-DC band combinations | 17.7.0 | +| 2022-12 | RAN#98 | R5-227952 | 1508 | 1 | F | Updates to EN-DC Enhanced Beam Corr test 6.6B.5 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227966 | 1450 | 1 | F | PC1 FR2 - Editor notes updates in 38.521-3 | 17.7.0 | +| 2022-12 | RAN#98 | R5-228032 | 1496 | 1 | F | Additions to the clarification on intra-band contiguous and non-contiguous EN-DC configurations | 17.7.0 | +| 2022-12 | RAN#98 | R5-228046 | 1461 | 1 | F | Clean-up pending R15 configurations in clause 5.2 | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98 | R5-228047 | 1463 | 1 | F | Clean-up pending R15 configurations in clause 5.5 | 17.7.0 | +| 2023-03 | RAN#99 | R5-230181 | 1511 | - | F | Missing MU and TT in annex F for Spurious co-existence EN-DC FR2 CA tests | 17.8.0 | +| 2023-03 | RAN#99 | R5-230246 | 1527 | - | F | Addition of reference sensitivity for new EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230313 | 1532 | - | F | Editorial - missing reference to 38.101 in section 7.3B | 17.8.0 | +| 2023-03 | RAN#99 | R5-230568 | 1534 | - | F | Correction of test tolerance for Tx power test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-230569 | 1535 | - | F | Move 6.4B.2.4.4D to be after 6.4B.2.4.4 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230570 | 1536 | - | F | Move 6.5B.4.4a to be after 6.5B.4.4 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230571 | 1537 | - | F | Editorial correction for content style in 6.6B.5.5 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230573 | 1539 | - | F | Addition of F.1.0 and F.1.1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230574 | 1540 | - | F | Addition of 6.2B.2.1 in F.3.2 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230659 | 1541 | - | F | Addition of 6.5E.3.1 General Spurious emissions for V2X | 17.8.0 | +| 2023-03 | RAN#99 | R5-230883 | 1544 | - | F | Update Configured Output Power Level for inter-band EN-DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-230892 | 1545 | - | F | Update 6.2B.4.2.3.1 for DC_71A_n66A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230893 | 1546 | - | F | Update 6.2B.4.2.3.1 for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230895 | 1547 | - | F | Update 6.2B.1.3 for R17 combo DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230899 | 1548 | - | F | Update for reference sensitivity for DC_48A_n66A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230901 | 1550 | - | F | Remove pending combo from 7.2B.2.3 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230906 | 1554 | - | F | Update ref sense min requirement for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230907 | 1555 | - | F | Update ref sense min requirement for DC_71A_n66A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230940 | 1560 | - | F | Correction to reference sensitivity test configuration for DC_1A_n28A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230941 | 1561 | - | F | Correction to reference sensitivity test configuration for DC_8A_n41A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230943 | 1563 | - | F | Addition of reference sensitivity for DC_2A-66A_n5A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230948 | 1564 | - | F | Correction to reference sensitivity requirements for EN-DC with 4 Rx support | 17.8.0 | +| 2023-03 | RAN#99 | R5-230949 | 1565 | - | F | Correction to NR test SCS for DC_(n)71AA across clause 6 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230959 | 1567 | - | F | Update 6.2B.1.3 for R16 combos DC_71A_n66A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230978 | 1569 | - | F | Correction to the MOP measurement for simultaneous transmission | 17.8.0 | +| 2023-03 | RAN#99 | R5-231058 | 1573 | - | F | Introduction of reference sensitivity for 21A_n28A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231180 | 1576 | - | F | Add editors note to TC6.2B.3.4D with incomplete state | 17.8.0 | +| 2023-03 | RAN#99 | R5-231182 | 1578 | - | F | Update to R16 Configuration for DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231294 | 1583 | - | F | Corrections on test requirements for reference sensitivity exceptions for DC_7A-20A_n1A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231301 | 1584 | - | F | Correction of maximum output power test case | 17.8.0 | +| 2023-03 | RAN#99 | R5-231312 | 1586 | - | F | Update of 7.3B.2.3 Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs) for DC_25A_n41A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231670 | 1585 | 1 | F | Editorial correction of E-UTRA reference for FR2 test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231671 | 1526 | 1 | F | Addition of delta TIBc for new EN-DC comb within FR1 | 17.8.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | RAN#99 | R5-231672 | 1523 | 1 | F | Addition of delta TIBc for new 3CC EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231673 | 1524 | 1 | F | Addition of reference sensitivity for new 3CC EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231674 | 1542 | 1 | F | Addition of MOP and spurious emissions for new 2CC EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231675 | 1543 | 1 | F | Updating spurious coex for inter-band EN-DC CA to add 5 to 8 CCs | 17.8.0 | +| 2023-03 | RAN#99 | R5-231676 | 1558 | 1 | F | Update Tx spurious co-exist for DC_71A_n66A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231677 | 1559 | 1 | F | General SE for DC_71A_n66A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231678 | 1549 | 1 | F | Remove pending combo from 7.2B.2.3 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231679 | 1552 | 1 | F | Update 7.3B.2.3 for DC_71A_n66A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231680 | 1556 | 1 | F | Update Tx spurious co-exist for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231681 | 1557 | 1 | F | General SE for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231682 | 1553 | 1 | F | Update 7.3B.2.3 for DC_71_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231684 | 1562 | 1 | F | Correction to reference sensitivity test configuration for DC_12A_n78A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231685 | 1579 | 1 | F | Update to R17 Configuration for DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231686 | 1577 | 1 | F | Update to R15 Configuration for DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231687 | 1572 | 1 | F | Introduction of spurious emissions test cases for 21A_n28A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231688 | 1574 | 1 | F | Introduction of DC_28A_n78A PC2 MOP test requirements | 17.8.0 | +| 2023-03 | RAN#99 | R5-231689 | 1529 | 1 | F | Updates for Table 7.3B.2.3.4.2.1-6 due to frequency selections in test configuration table partly non-implementable | 17.8.0 | +| 2023-03 | RAN#99 | R5-231690 | 1520 | 1 | F | Update of MOP TC for PC2 ENDC configurations | 17.8.0 | +| 2023-03 | RAN#99 | R5-231691 | 1521 | 1 | F | Addition of PC2 ENDC combo into 38.521-3 TC 7.3B.2 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231692 | 1587 | 1 | F | Introduction of EIRP with UL-Gaps test for EN-DC with FR2 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231693 | 1568 | 1 | F | Correction to time offset for TDD intra-band EN-DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231694 | 1582 | 1 | F | Corrections on reference sensitivity for configuration DC_66A_n41A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231695 | 1580 | 1 | F | Corrections on applicability of minimum requirements for intra-band EN-DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231783 | 1519 | 1 | F | Update of editors note for PC1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231840 | 1509 | 1 | F | Update switching time mask for UL tx switching for EN-DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231847 | 1510 | 1 | F | PC1 FR2 - Editor notes updates in 38.521-3 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231860 | 1551 | 1 | F | Ref sensitivity correction for DC_1A_n77A and DC_21_n79A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231864 | 1566 | 1 | F | Update of EN-DC reference sensitivity to handle simultaneous Rx/Tx capability | 17.8.0 | +| 2023-03 | RAN#99 | R5-231876 | 1570 | 1 | F | Clarification on power class of LTE band in 6.2B.4.1.3 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231887 | 1538 | 1 | F | Correction of referenced clause numbers in 7.5B.4_1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231892 | 1528 | 1 | F | Corrections of test requirement tables for spurious emission for UE co-existence for EN-DC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231965 | 1581 | 1 | F | Corrections on intra-band EN-DC configuration for DC_n41 | 17.8.0 | +| 2023-06 | RAN#100 | R5-232349 | 1594 | - | F | Editorial update Tx spurious co-existence for DC_71A_n2A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232365 | 1596 | - | F | Correction to spurious emissions test cases for 21A_n28A | 17.9.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|---------| +| 2023-06 | RAN#100 | R5-232383 | 1598 | - | F | Correction of the DC_28A_n78A PC2 MOP test requirements | 17.9.0 | +| 2023-06 | RAN#100 | R5-232514 | 1601 | - | F | Update the Initial Conditions of four 6.2B.x TCs | 17.9.0 | +| 2023-06 | RAN#100 | R5-232609 | 1603 | - | F | Update Ref sense for DC_7A_n66A DC_7A_n71A DC_7A_n77A and DC_66A_n25A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232623 | 1604 | - | F | Adding SE Coex Inter band ENDC FR2 UL-MIMO test case | 17.9.0 | +| 2023-06 | RAN#100 | R5-232700 | 1605 | - | F | Addition of 6.5E.4 Transmit intermodulation for V2X | 17.9.0 | +| 2023-06 | RAN#100 | R5-232754 | 1607 | - | F | Correction to test ID for PC2 fallback PC3 testing | 17.9.0 | +| 2023-06 | RAN#100 | R5-232772 | 1608 | - | F | Addition of reference sensitivity for 21A_n28A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232840 | 1610 | - | F | Update of PC2 UE configured output power for inter-band EN-DC configurations | 17.9.0 | +| 2023-06 | RAN#100 | R5-232841 | 1611 | - | F | Update of PC2 UE maximum output power for inter-band EN-DC configurations | 17.9.0 | +| 2023-06 | RAN#100 | R5-233001 | 1612 | - | F | Correction to reference of RMC for E-UTRA TDD in FR1 EN-DC test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233002 | 1613 | - | F | Correction to 6.2B.4.1.3 and editorial correction to Tx test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233025 | 1615 | - | F | Adding time delay to intra-band EN-DC test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233157 | 1617 | - | F | Update 7.3B.3.3.1 for R16 DC combos | 17.9.0 | +| 2023-06 | RAN#100 | R5-233168 | 1618 | - | F | Addition of Additional Spurious Emissions FR2 CA test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233175 | 1619 | - | F | Update of in-band blocking for CA test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233182 | 1620 | - | F | Update to R15 Configuration for DC | 17.9.0 | +| 2023-06 | RAN#100 | R5-233183 | 1621 | - | F | Update to R16 Configuration for DC | 17.9.0 | +| 2023-06 | RAN#100 | R5-233190 | 1623 | - | F | Additional editors note to Power Boost relevant test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233520 | 1602 | 1 | F | Update Ref sense for DC_38A_n78A, DC_18A_n77A and DC_19A_n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233545 | 1616 | 1 | F | Clarification of spurious emission testing configuration - Part 3 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233563 | 1599 | 1 | F | Addition of new CADC MOP TC | 17.9.0 | +| 2023-06 | RAN#100 | R5-233564 | 1600 | 1 | F | Addition of new CADC TC 6.3B.3.4_1.1 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233576 | 1625 | 1 | F | Corrections on test requirements for MSD due to dual uplink for EN-DC | 17.9.0 | +| 2023-06 | RAN#100 | R5-233577 | 1624 | 1 | F | Corrections on higher power class indication for EN-DC configuration | 17.9.0 | +| 2023-06 | RAN#100 | R5-233638 | 1589 | 1 | F | FR2 MUs - Editor notes updates in 38.521-3 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233703 | 1590 | 1 | F | Update PC2 MSD minimum requirements and test requirements for DC_2A_n77A, DC_13A_n77A, and DC_66A_n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233724 | 1595 | 1 | F | NSA beam correspondence test applicability inconsistent with SA test | 17.9.0 | +| 2023-06 | RAN#100 | R5-233725 | 1606 | 1 | F | Correction to 6.2B.4.1.3 configured output power for EN-DC | 17.9.0 | +| 2023-09 | RAN#101 | R5-234040 | 1629 | - | F | Correction to ref sense configuration for DC_71A_n2A | 17.10.0 | +| 2023-09 | RAN#101 | R5-234054 | 1632 | - | F | Update 6.2B.4.2.3.1 for DC_48A_n46 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234055 | 1633 | - | F | Update 6.2B.1.3 for DC_48A_n46A | 17.10.0 | +| 2023-09 | RAN#101 | R5-234057 | 1634 | - | F | Update Ch5 for DC_48A_n46A | 17.10.0 | +| 2023-09 | RAN#101 | R5-234117 | 1637 | - | F | Correction of reference sensitivity test point for DC_48A_n66A | 17.10.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|---------| +| 2023-09 | RAN#101 | R5-234182 | 1642 | - | F | Correction for NSA band combo DC_7A_n71A in 7.3B.2.3 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234185 | 1645 | - | F | Correction for NSA band combos DC_19A_n77A and DC_1A_n77A in 7.3B.2.3 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234227 | 1646 | - | F | Update the Initial Conditions of 6.3B.x and 6.4B.x TCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-234564 | 1647 | - | F | Update to R15 Configuration for DC | 17.10.0 | +| 2023-09 | RAN#101 | R5-234777 | 1651 | - | F | Addition of new test case 6.4B.2.4.3_1.4 In-band Emissions for inter-band EN-DC including FR2 (5 NR CCs) | 17.10.0 | +| 2023-09 | RAN#101 | R5-234778 | 1652 | - | F | Addition of new test case 6.4B.2.4.3_1.5 In-band Emissions for inter-band EN-DC including FR2 (6 NR CCs) | 17.10.0 | +| 2023-09 | RAN#101 | R5-234790 | 1653 | - | F | Update of higher power limit requirements for inter-band EN-DC | 17.10.0 | +| 2023-09 | RAN#101 | R5-234912 | 1655 | - | F | Correction to message exception in EVM test case for intra-band EN-DC | 17.10.0 | +| 2023-09 | RAN#101 | R5-234913 | 1656 | - | F | Editorial correction to Reference sensitivity for EN-DC | 17.10.0 | +| 2023-09 | RAN#101 | R5-235069 | 1658 | - | F | Correction to referred clause number of CADC MOP TCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-235141 | 1661 | - | F | Correction of Refsens FR1 EN-DC | 17.10.0 | +| 2023-09 | RAN#101 | R5-235148 | 1663 | - | F | Editorial correction of Refsens for Rel-16 configuration | 17.10.0 | +| 2023-09 | RAN#101 | R5-235202 | 1664 | - | F | Correction to title of 6.2B.1.4D.1 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235203 | 1665 | - | F | Updated to editors note for EN-DC FR2 TC completion status | 17.10.0 | +| 2023-09 | RAN#101 | R5-235623 | 1662 | 1 | F | Editorial correction of UE co-existence Inter-band FR1 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235672 | 1643 | 1 | F | Correction for NSA band combo DC_14A_n77A in 7.3B.2.3 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235673 | 1659 | 1 | F | Corrections on cross-band isolation MSD for the more than 2 bands configuration | 17.10.0 | +| 2023-09 | RAN#101 | R5-235674 | 1660 | 1 | F | Corrections on test requirements for MSD due to dual uplink for R15 EN-DC configurations | 17.10.0 | +| 2023-09 | RAN#101 | R5-235675 | 1648 | 1 | F | Update to R16 Configuration for DC | 17.10.0 | +| 2023-09 | RAN#101 | R5-235676 | 1630 | 1 | F | Update 7.3B.2.0 for DC_48A_n46A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235677 | 1666 | 1 | F | Update of EIRP with UL-Gaps test for EN-DC with FR2 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235750 | 1628 | 1 | F | FR2 MUs - Editor notes updates in 38.521-3 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235820 | 1657 | 1 | F | Addition of new CADC MOP TC for 8 NR CCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-235870 | 1654 | 1 | F | Clarification of unwanted emission testing configuration - Part 3 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235958 | 1636 | 1 | F | Correction of 7.3B.2.3 for exception and no exception requirements | 17.10.0 | +| 2023-09 | RAN#101 | R5-235959 | 1638 | 1 | F | Correction of 6.5B.3.3.1 for exception and non-exception requirements | 17.10.0 | +| 2023-09 | RAN#101 | R5-235960 | 1639 | 1 | F | Correction of requirements of Spurious emissions for UE co-existence of intra band ENDC | 17.10.0 | +| 2023-09 | RAN#101 | R5-235961 | 1640 | 1 | F | Correction of 6.5B.3.3.2 for exception and non-exception requirements | 17.10.0 | +| 2023-09 | RAN#101 | R5-234097 | 1635 | - | F | Introduction of DC for n78 and n79 PC2 MOP test requirements | 18.0.0 | +| 2023-09 | RAN#101 | R5-235618 | 1650 | 1 | F | Updates to spurious emissions UE coexistence test cases as part of introduction of LTE Band 54 | 18.0.0 | +| 2023-12 | RAN#102 | R5-236067 | 1667 | | F | FR2 MUs - Editor notes updates for Tx test cases in 38.521-3 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236328 | 1672 | | F | Missing notes for DC_1A_n41A test IDs in 7.3B.2.3 test configuration table | 18.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-12 | RAN#102 | R5-236339 | 1676 | | F | Defined MU and TT for EUTRA and NR UL Switching test case 6.3B.3_1.1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236340 | 1677 | | F | Editorial correction in test procedure of NSA ACLR test 6.5B.2.1.3 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236351 | 1679 | | F | Addition of max power requirements for several EN-DC combos | 18.1.0 | +| 2023-12 | RAN#102 | R5-236352 | 1680 | | F | Addition of spurious emissions test for several EN-DC combos | 18.1.0 | +| 2023-12 | RAN#102 | R5-236369 | 1681 | | F | Update minimum requirements for additional ENDC configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-236370 | 1682 | | F | Update test configurations and test requirements for additional three band ENDC configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-236461 | 1685 | | F | New addition of RF Rel-16 Test Case 6.2B.2.4_1.2 UE Maximum Output power reduction for inter-band EN-DC including FR2 (3 NR CCs) | 18.1.0 | +| 2023-12 | RAN#102 | R5-236467 | 1687 | | F | Addition of new test case 6.4B.2.4.3_1.6 In-band Emissions for inter-band EN-DC including FR2 (7 NR CCs) | 18.1.0 | +| 2023-12 | RAN#102 | R5-236468 | 1688 | | F | Addition of new test case 6.4B.2.4.3_1.7 In-band Emissions for inter-band EN-DC including FR2 (8 NR CCs) | 18.1.0 | +| 2023-12 | RAN#102 | R5-236502 | 1691 | | F | Addition of REFSENS for 2CC EN-DC for n79 in PC2 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236545 | 1693 | | F | Update to R15 common section | 18.1.0 | +| 2023-12 | RAN#102 | R5-236661 | 1697 | | F | Updating FR2 MOP for 5UL-8UL CA test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236816 | 1702 | | F | Correction to DL RMC for TDD E-UTRA | 18.1.0 | +| 2023-12 | RAN#102 | R5-236846 | 1704 | | F | New addition of RF Rel-16 Test Case 6.2B.2.4_1.3 UE Maximum Output power reduction for inter-band EN-DC including FR2 (4 NR CCs) | 18.1.0 | +| 2023-12 | RAN#102 | R5-236946 | 1705 | | F | Corrections to 7.3A.3 and 7.3B.3 on delta RIB value for CA and DC in REFSENS requirement | 18.1.0 | +| 2023-12 | RAN#102 | R5-237261 | 1709 | | F | Editorial correction of FR2 spurious emissions test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237636 | 1690 | 1 | F | Update of REFSENS for 3CC EN-DC for n78 and n79 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237663 | 1694 | 1 | F | Update to R16 Configuration for DC | 18.1.0 | +| 2023-12 | RAN#102 | R5-237664 | 1678 | 1 | F | Addition of reference sensitivity test for several EN-DC combos | 18.1.0 | +| 2023-12 | RAN#102 | R5-237665 | 1695 | 1 | F | Update to R17 Configuration for DC | 18.1.0 | +| 2023-12 | RAN#102 | R5-237666 | 1700 | 1 | F | Correction to test condition for test frequency restriction of DC_xA_n28A | 18.1.0 | +| 2023-12 | RAN#102 | R5-237667 | 1711 | | F | Correction to message contents in Rx test cases for inter-band EN-DC with FR1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237668 | 1708 | 1 | F | Correction of Refsens EN-DC within FR1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237669 | 1710 | 1 | F | Update to Table 7.3B.2.3.4.2.1-6: Test Configuration Table for EN-DC configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-237732 | 1707 | 1 | F | Editors notes update in FR2 UL MIMO test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237733 | 1668 | 1 | F | FR2 MUs - Editor notes updates for Rx test cases in 38.521-3 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237784 | 1689 | 1 | F | Adding DeltaTIB for DC_1-3-7-28_n78 and DC_1-7_28-n78 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237862 | 1706 | 1 | F | Corrections to spurious emissions co-existence for 2 UL Inter-band CA (38.521-3) | 18.1.0 | +| 2023-12 | RAN#102 | R5-237955 | 1692 | 1 | F | Correction to 6.5B.3.3.2 | 18.1.0 | +| 2024-01 | RAN#102 | - | - | - | - | removed R5-237963 entry from history table | 18.1.1 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38521-5/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-18/38_series/38521-5/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29e80c6f781b91a39467beb6012a9fd4c4ee8bbf --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da7c3c9620cda6c45ab7631c40e5a68b6427d1f30b1f4b0e9cc48d1aff70b83d +size 64760 diff --git a/marked/Rel-18/38_series/38521-5/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Rel-18/38_series/38521-5/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84500a61a488f63b8b919fc35b65550229918812 --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da6fd19d1276b72318ea3a3ac68a16eabc67054eac4e1acba99d3470d93b63af +size 32438 diff --git a/marked/Rel-18/38_series/38521-5/2e83263cd91cb4bcdc0ad2973f715412_img.jpg b/marked/Rel-18/38_series/38521-5/2e83263cd91cb4bcdc0ad2973f715412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43694c662a6a62f741912c2e921fc95c5fc6f3a4 --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/2e83263cd91cb4bcdc0ad2973f715412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48c51a186efc7c9b0ed0a39919eba23269ad3ae282c5e71917c54919056bd010 +size 117963 diff --git a/marked/Rel-18/38_series/38521-5/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-18/38_series/38521-5/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b40e1fa7caf9768c0f5ca2ecc025dfee0ab052f --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9de0dbe2087768d7a02289b71fd8fd69fff65131da686b843484d3ea84ca78cd +size 32843 diff --git a/marked/Rel-18/38_series/38521-5/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38521-5/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c070a1827973ed629772fae49b1862a377d0952d --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34b3c855bc158b5b6b78bef19bdeef0520fe773db21a9cbf59dffd8c9a85449d +size 9471 diff --git a/marked/Rel-18/38_series/38521-5/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38521-5/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a959b16e364a9d6ec9143358710b3fab4d0b9d3 --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3625a05f6c777b8ea57f7505c6437e88483436350491889bcb7dfa0d67c4f667 +size 5735 diff --git a/marked/Rel-18/38_series/38521-5/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg b/marked/Rel-18/38_series/38521-5/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b99de4c1dae18f8086585851c7a7f939eccb8d --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82875d4aabd45572aa5e87d9e0a8ffa111907ade218e008231dbe934d2c254a5 +size 102310 diff --git a/marked/Rel-18/38_series/38521-5/bbbb412b1ea8a6ca30ec4b4e7d08fd58_img.jpg b/marked/Rel-18/38_series/38521-5/bbbb412b1ea8a6ca30ec4b4e7d08fd58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59a975dc772b08a05746d518c6f8a226e9f20253 --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/bbbb412b1ea8a6ca30ec4b4e7d08fd58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cebb10bde1b7ec584621aca8175d70c3851f0b6f6eb3bac152b8612114f2d7c +size 105822 diff --git a/marked/Rel-18/38_series/38521-5/raw.md b/marked/Rel-18/38_series/38521-5/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6c7f0da0f024dba4353bfc26d617dd7a7b9c96b7 --- /dev/null +++ b/marked/Rel-18/38_series/38521-5/raw.md @@ -0,0 +1,5159 @@ + + +# 3GPP TS 38.521-5 V18.0.0 (2023-12) + +*Technical Specification* + +**3rd Generation Partnership Project; +Technical Specification Group Radio Access Network; +NR; +User Equipment (UE) conformance specification; +Radio transmission and reception; +Part 5: Satellite access Radio Frequency (RF) and performance +(Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text are three red curved lines representing signal waves. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions of terms, symbols and abbreviations ..... | 11 | +| 3.1 Terms..... | 11 | +| 3.2 Symbols..... | 12 | +| 3.3 Abbreviations ..... | 12 | +| 4 General ..... | 13 | +| 4.1 Relationship between minimum requirements and test requirements..... | 13 | +| 4.2 Applicability of minimum requirements ..... | 14 | +| 4.3 Specification suffix information..... | 14 | +| 4.4 Relationship with core specifications..... | 14 | +| 5 Operating bands and channel arrangement ..... | 14 | +| 5.1 General ..... | 14 | +| 5.2 Operating bands..... | 15 | +| 5.2.1 General ..... | 15 | +| 5.2.2 Operating bands with conducted requirements ..... | 15 | +| 5.2.3 reserved (for radiated requirements)..... | 15 | +| 5.3 UE channel bandwidth ..... | 15 | +| 5.3.1 General ..... | 15 | +| 5.3.2 Maximum transmission bandwidth configuration..... | 16 | +| 5.3.3 Minimum guardband and transmission bandwidth configuration..... | 16 | +| 5.3.4 RB alignment..... | 17 | +| 5.3.5 UE channel bandwidth per operating band..... | 17 | +| 5.4 Channel arrangement..... | 18 | +| 5.4.1 Channel spacing..... | 18 | +| 5.4.1.1 Channel spacing for adjacent NTN satellite carriers ..... | 18 | +| 5.4.2 Channel raster ..... | 18 | +| 5.4.2.1 NR-ARFCN and channel raster ..... | 18 | +| 5.4.2.2 Channel raster to resource element mapping ..... | 18 | +| 5.4.2.3 Channel raster entries for each operating band..... | 18 | +| 5.4.3 Synchronization raster ..... | 19 | +| 5.4.3.1 Synchronization raster and numbering ..... | 19 | +| 5.4.3.2 Synchronization raster to synchronization block resource element mapping..... | 19 | +| 5.4.3.3 Synchronization raster entries for each operating band..... | 19 | +| 5.4.4 TX-RX frequency separation..... | 19 | +| 6 Transmitter characteristics ..... | 20 | +| 6.1 General ..... | 20 | +| 6.2 Transmitter power ..... | 21 | +| 6.2.1 UE maximum output power ..... | 21 | +| 6.2.1.1 Test purpose..... | 21 | +| 6.2.1.2 Test applicability..... | 21 | +| 6.2.1.3 Minimum conformance requirements..... | 21 | +| 6.2.1.4 Test description..... | 21 | +| 6.2.1.4.1 Initial conditions..... | 21 | +| 6.2.1.4.2 Test procedure ..... | 22 | +| 6.2.1.4.3 Message contents..... | 22 | +| 6.2.1.5 Test requirement ..... | 23 | +| 6.2.2 UE maximum output power reduction ..... | 23 | +| 6.2.2.1 Test purpose..... | 23 | +| 6.2.2.2 Test applicability..... | 23 | +| 6.2.2.3 Minimum conformance requirements..... | 23 | +| 6.2.2.4 Test description..... | 24 | + +| | | | +|-----------|----------------------------------------------------|----| +| 6.2.2.4.1 | Initial conditions..... | 24 | +| 6.2.2.4.2 | Test procedure..... | 26 | +| 6.2.2.4.3 | Message contents..... | 26 | +| 6.2.2.5 | Test requirement..... | 27 | +| 6.2.3 | UE additional maximum output power reduction ..... | 28 | +| 6.2.3.1 | Test purpose..... | 28 | +| 6.2.3.2 | Test applicability..... | 28 | +| 6.2.3.3 | Minimum conformance requirements..... | 28 | +| 6.2.3.3.1 | General ..... | 28 | +| 6.2.3.4 | Test description..... | 30 | +| 6.2.3.4.1 | Initial conditions..... | 30 | +| 6.2.3.4.2 | Test procedure..... | 35 | +| 6.2.3.4.3 | Message contents..... | 35 | +| 6.2.3.5 | Test requirement..... | 36 | +| 6.2.4 | Configured transmitted power..... | 38 | +| 6.2.4.1 | Test purpose..... | 38 | +| 6.2.4.2 | Test applicability..... | 38 | +| 6.2.4.3 | Minimum conformance requirements..... | 39 | +| 6.2.4.4 | Test description..... | 39 | +| 6.2.4.4.1 | Initial condition ..... | 39 | +| 6.2.4.4.2 | Test procedure..... | 40 | +| 6.2.4.4.3 | Message contents..... | 40 | +| 6.2.4.5 | Test requirement..... | 41 | +| 6.3 | Output power dynamics ..... | 41 | +| 6.3.1 | Minimum output power..... | 41 | +| 6.3.1.1 | Test purpose..... | 41 | +| 6.3.1.2 | Test applicability..... | 42 | +| 6.3.1.3 | Minimum conformance requirements..... | 42 | +| 6.3.1.4 | Test description..... | 42 | +| 6.3.1.4.1 | Initial condition ..... | 42 | +| 6.3.1.4.2 | Test procedure..... | 43 | +| 6.3.1.4.3 | Message contents..... | 43 | +| 6.3.1.5 | Test requirement..... | 43 | +| 6.3.2 | Transmit OFF power ..... | 43 | +| 6.3.2.1 | Test purpose..... | 44 | +| 6.3.2.2 | Test applicability..... | 44 | +| 6.3.2.3 | Minimum conformance requirements..... | 44 | +| 6.3.2.4 | Test description..... | 44 | +| 6.3.2.5 | Test requirement..... | 44 | +| 6.3.3 | Transmit on/off time mask ..... | 44 | +| 6.3.3.1 | Test purpose..... | 45 | +| 6.3.3.2 | Test applicability..... | 45 | +| 6.3.3.3 | Minimum conformance requirements..... | 45 | +| 6.3.3.4 | Test description..... | 45 | +| 6.3.3.4.1 | Initial conditions..... | 45 | +| 6.3.3.4.2 | Test procedure..... | 46 | +| 6.3.3.4.3 | Message contents..... | 47 | +| 6.3.3.5 | Test requirement..... | 47 | +| 6.4 | Transmit signal quality..... | 48 | +| 6.4.1 | Frequency error ..... | 48 | +| 6.4.1.1 | Test purpose..... | 48 | +| 6.4.1.2 | Test applicability..... | 48 | +| 6.4.1.3 | Minimum conformance requirements..... | 48 | +| 6.4.1.4 | Test description..... | 49 | +| 6.4.1.4.1 | Initial condition ..... | 49 | +| 6.4.1.4.2 | Test procedure..... | 49 | +| 6.4.1.4.3 | Message contents..... | 50 | +| 6.4.1.5 | Test requirement..... | 53 | +| 6.5 | Output RF spectrum emissions ..... | 53 | +| 6.5.1 | Occupied bandwidth..... | 53 | +| 6.5.2 | Out of band emission..... | 53 | + +| | | | +|-----------|----------------------------------------------|----| +| 6.5.2.1 | [to be updated] ..... | 53 | +| 6.5.2.2 | Spectrum emission mask ..... | 53 | +| 6.5.2.2.1 | Test purpose ..... | 53 | +| 6.5.2.2.2 | Test applicability ..... | 54 | +| 6.5.2.2.3 | Minimum conformance requirements ..... | 54 | +| 6.5.2.2.4 | Test description ..... | 54 | +| 6.5.2.2.5 | Test requirement..... | 56 | +| 6.5.2.3 | [to be updated] ..... | 57 | +| 6.5.2.4 | Adjacent channel leakage ratio ..... | 57 | +| 6.5.2.4.0 | General ..... | 57 | +| 6.5.2.4.1 | NR Adjacent channel leakage ratio ..... | 57 | +| 6.5.2.4.2 | UTRA Adjacent channel leakage ratio..... | 60 | +| 6.5.3 | Spurious emission..... | 62 | +| 6.5.3.0 | General..... | 62 | +| 6.5.3.1 | General spurious emissions ..... | 62 | +| 6.5.3.1.1 | Test purpose ..... | 63 | +| 6.5.3.1.2 | Test applicability ..... | 63 | +| 6.5.3.1.3 | Minimum conformance requirements ..... | 63 | +| 6.5.3.1.4 | Test description ..... | 63 | +| 6.5.3.1.5 | Test requirement..... | 64 | +| 6.5.3.2 | Spurious emissions for UE co-existence ..... | 65 | +| 6.5.3.2.1 | Test purpose ..... | 65 | +| 6.5.3.2.2 | Test applicability ..... | 65 | +| 6.5.3.2.3 | Minimum conformance requirements ..... | 65 | +| 6.5.3.2.4 | Test description ..... | 66 | +| 6.5.3.1.5 | Test requirement..... | 67 | +| 6.5.3.3 | Additional Spurious emissions ..... | 68 | +| 6.5.3.3.1 | Test purpose ..... | 68 | +| 6.5.3.3.2 | Test applicability ..... | 68 | +| 6.5.3.3.3 | Minimum conformance requirements ..... | 68 | +| 6.5.3.3.4 | Test description ..... | 69 | +| 6.5.3.3.5 | Test requirement..... | 70 | +| 6.5.4 | Transmit intermodulation ..... | 71 | +| 6.5.4.1 | Test purpose..... | 71 | +| 6.5.4.2 | Test applicability..... | 71 | +| 6.5.4.3 | Minimum conformance requirements..... | 71 | +| 6.5.4.4 | Test description..... | 72 | +| 6.5.4.4.1 | Initial conditions..... | 72 | +| 6.5.4.4.2 | Test procedure..... | 73 | +| 6.5.4.4.3 | Message contents..... | 73 | +| 6.5.4.5 | Test requirement ..... | 73 | +| 7 | Receiver characteristics..... | 74 | +| 7.1 | General ..... | 74 | +| 7.2 | Diversity characteristics ..... | 74 | +| 7.3 | Reference sensitivity ..... | 74 | +| 7.3.1 | General ..... | 74 | +| 7.3.2 | Reference sensitivity power level..... | 74 | +| 7.3.2.1 | Test purpose..... | 74 | +| 7.3.2.2 | Test applicability..... | 74 | +| 7.3.2.3 | Minimum conformance requirements..... | 75 | +| 7.3.2.4 | Test description..... | 75 | +| 7.3.2.4.1 | Initial conditions..... | 75 | +| 7.3.2.4.2 | Test procedure..... | 77 | +| 7.3.2.4.3 | Message contents..... | 77 | +| 7.3.2.5 | Test requirement ..... | 77 | +| 7.4 | Maximum input level ..... | 79 | +| 7.4.1 | Test purpose..... | 79 | +| 7.4.2 | Test applicability ..... | 79 | +| 7.4.3 | Minimum conformance requirements ..... | 79 | +| 7.4.4 | Test description ..... | 79 | + +| | | | +|-----------|-----------------------------------------------------------------------|----| +| 7.4.4.1 | Initial conditions ..... | 79 | +| 7.4.4.2 | Test procedure..... | 80 | +| 7.4.4.3 | Message contents ..... | 81 | +| 7.4.5 | Test requirement..... | 81 | +| 7.5 | Adjacent channel selectivity..... | 81 | +| 7.5.1 | Test purpose..... | 81 | +| 7.5.2 | Test applicability ..... | 81 | +| 7.5.3 | Minimum conformance requirements ..... | 82 | +| 7.5.4 | Test description ..... | 83 | +| 7.5.4.1 | Initial conditions ..... | 83 | +| 7.5.4.2 | Test procedure..... | 83 | +| 7.5.4.3 | Message contents ..... | 84 | +| 7.5.5 | Test requirement..... | 84 | +| 7.6 | Blocking characteristics ..... | 85 | +| 7.6.1 | General ..... | 85 | +| 7.6.2 | In-band blocking..... | 86 | +| 7.6.3 | Out of Band Blocking..... | 86 | +| 7.6.3.1 | Test purpose..... | 86 | +| 7.6.3.2 | Test applicability..... | 86 | +| 7.6.3.3 | Minimum conformance requirements..... | 86 | +| 7.6.3.4 | Test description..... | 87 | +| 7.6.3.4.1 | Initial conditions..... | 87 | +| 7.6.3.4.2 | Test procedure..... | 88 | +| 7.6.3.4.3 | Message contents..... | 88 | +| 7.6.3.5 | Test requirement ..... | 88 | +| 7.6.4 | Narrow band blocking ..... | 88 | +| 7.7 | Spurious response..... | 88 | +| 7.7.1 | Test Purpose ..... | 88 | +| 7.7.2 | Test Applicability ..... | 88 | +| 7.7.3 | Minimum Conformance Requirements ..... | 88 | +| 7.7.4 | Test Description..... | 89 | +| 7.7.4.1 | Initial Conditions ..... | 89 | +| 7.7.4.2 | Test Procedure ..... | 89 | +| 7.7.4.3 | Message Contents ..... | 90 | +| 7.7.5 | Test Requirement..... | 90 | +| 7.8 | Intermodulation characteristics ..... | 90 | +| 7.8.1 | General ..... | 90 | +| 7.8.2 | Wide band Intermodulation ..... | 91 | +| 7.8.2.1 | Test purpose..... | 91 | +| 7.8.2.2 | Test applicability..... | 91 | +| 7.8.2.3 | Minimum conformance requirements..... | 91 | +| 7.8.2.4 | Test description..... | 92 | +| 7.8.2.4.1 | Initial conditions..... | 92 | +| 7.8.2.4.2 | Test procedure..... | 92 | +| 7.8.2.4.3 | Message contents..... | 93 | +| 7.8.2.5 | Test requirement ..... | 93 | +| 7.9 | Spurious emissions..... | 94 | +| 7.9.1 | Test purpose..... | 94 | +| 7.9.2 | Test applicability ..... | 94 | +| 7.9.3 | Minimum conformance requirements ..... | 94 | +| 7.9.4 | Test description ..... | 95 | +| 7.9.4.1 | Initial conditions ..... | 95 | +| 7.9.4.2 | Test procedure..... | 96 | +| 7.9.4.3 | Message contents ..... | 96 | +| 7.9.5 | Test requirement..... | 96 | +| 8 | Conducted performance requirements ..... | 96 | +| 8.0 | General ..... | 96 | +| 8.1.1 | Relationship between minimum requirements and test requirements ..... | 96 | +| 8.1.2 | Applicability of minimum requirements ..... | 97 | +| 8.1.3 | Conducted requirements..... | 97 | + +| | | | +|-----------------------------------------------------------------------------|------------------------------------------------------------------------|------------| +| 8.1.3.1 | Introduction..... | 97 | +| 8.1.3.2 | Reference point..... | 97 | +| 8.1.3.3 | SNR definition ..... | 97 | +| 8.1.3.4 | Noc..... | 98 | +| 8.1.3.4.1 | Introduction ..... | 98 | +| 8.1.3.4.2 | Noc for NR operating bands in FR1..... | 98 | +| 8.2 | Demodulation performance requirements..... | 98 | +| 8.2.1 | General ..... | 98 | +| 8.2.1.1 | Applicability of requirements ..... | 98 | +| 8.2.1.1.1 | General ..... | 98 | +| 8.2.1.1.2 | Applicability of requirements for optional UE features..... | 98 | +| 8.2.1.2.0 | PDSCH demodulation requirements..... | 99 | +| 8.2.1.2.1 | 1RX requirements ..... | 102 | +| 8.2.1.2.2 | 2RX requirements ..... | 102 | +| Annex A: (normative): Measurement channels..... | | 107 | +| A.1 | General..... | 107 | +| A.1.1 | Throughput definition ..... | 107 | +| A.2 | UL reference measurement channels ..... | 107 | +| A.3 | DL reference measurement channels ..... | 107 | +| A.3.1 | General ..... | 107 | +| A.3.2 | Reference measurement channels for PDSCH performance requirements..... | 107 | +| A.3.2.0 | General ..... | 107 | +| A.3.2.1 | FDD ..... | 108 | +| A.3.2.1.1 | Reference measurement channels for SCS 15 kHz FR1..... | 108 | +| A.4 | Testing related to Satellite Access ..... | 110 | +| A.4.1 | General ..... | 110 | +| A.4.2 | Test condition for transmitter characteristics..... | 110 | +| A.4.3 | Test condition for receiver characteristics ..... | 110 | +| A.4.4 | Test condition for performance requirements ..... | 110 | +| Annex B: (normative): Propagation conditions..... | | 111 | +| B.0 | No interference..... | 111 | +| B.1 | Static propagation condition ..... | 111 | +| B.1.1 | UE Receiver with 1Rx..... | 111 | +| B.1.2 | UE Receiver with 2Rx..... | 111 | +| B.2 | Multi-path fading propagation conditions..... | 111 | +| B.2.0 | General ..... | 111 | +| B.2.1 | Delay profiles ..... | 112 | +| B.2.2 | Combinations of channel model parameters ..... | 112 | +| B.2.3 | MIMO Channel Correlation Matrices ..... | 112 | +| B.2.3.0 | General ..... | 112 | +| B.2.3.1 | MIMO Correlation Matrices using Uniform Linear Array (ULA)..... | 113 | +| B.2.3.1.0 | General ..... | 113 | +| B.2.3.1.1 | Definition of MIMO Correlation Matrices ..... | 113 | +| B.2.3.1.2 | MIMO Correlation Matrices at High, Medium and Low Level ..... | 113 | +| Annex C (normative): Downlink physical channels..... | | 114 | +| C.1 | General..... | 114 | +| C.2 | Setup (Conducted)..... | 114 | +| C.3 | Connection (Conducted) ..... | 114 | +| C.3.0 | General ..... | 114 | +| C.3.1 | Measurement of Performance requirements ..... | 114 | +| Annex D (normative): Characteristics of the interfering signal ..... | | 116 | + +| | | | +|--------------------------------------------------------------------------------|---------------------------------------------------------------------------|------------| +| D.1 | General..... | 116 | +| D.2 | Interference signals ..... | 116 | +| Annex F (normative): Measurement uncertainties and Test Tolerances..... | | 117 | +| F.1 | Acceptable uncertainty of Test System (normative)..... | 117 | +| F.1.0 | General ..... | 117 | +| F.1.1 | Measurement of test environments ..... | 117 | +| F.1.2 | Measurement of transmitter ..... | 117 | +| F.1.3 | Measurement of receiver..... | 118 | +| F.2 | Interpretation of measurement results (normative)..... | 118 | +| F.3 | Test Tolerance and Derivation of Test Requirements (informative) ..... | 119 | +| F.3.0 | General ..... | 119 | +| F.3.1 | Measurement of test environments ..... | 119 | +| F.3.2 | Measurement of transmitter ..... | 119 | +| F.3.3 | Measurement of receiver..... | 119 | +| F.4 | Uplink power window..... | 120 | +| F.4.1 | Introduction ..... | 120 | +| F.4.2 | Setting the power window above a requirement ..... | 120 | +| F.4.3 | Setting the power window below a requirement..... | 121 | +| F.4.4 | Setting the power window centred on a target value ..... | 122 | +| Annex H (normative): Statistical Testing..... | | 124 | +| H.1 | General..... | 124 | +| H.2 | Statistical testing of receiver characteristics ..... | 124 | +| H.2.1 | General ..... | 124 | +| H.2.2 | Mapping throughput to error ratio..... | 124 | +| H.2.3 | Design of the test..... | 125 | +| H.2.4 | Numerical definition of the pass fail limits..... | 126 | +| H.2.5 | Pass fail decision rules ..... | 126 | +| H.2.6 | Theory to derive the pass fail limits (Informative) ..... | 127 | +| H.2.6.1 | Numerical definition of the pass-fail limits ..... | 127 | +| H.2.6.2 | Simulation to derive the pass-fail limits for testing 95% throughput..... | 128 | +| Annex I (informative): Change history ..... | | 129 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +## 1 Scope + +The present document specifies the measurement procedures for the conformance test of the NR User Equipment (UE) supporting satellite access operation that contains RF and Performance requirements. + +--- + +## 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone". +- [3] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [4] 3GPP TS 38.108: "NR; Satellite Node radio transmission and reception" +- [5] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [6] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [7] 3GPP TS 38.213: "NR; Physical layer procedures for control" +- [8] 3GPP TS 38.331: " Radio Resource Control (RRC) protocol specification". +- [9] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2". +- [10] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [11] 3GPP TS 38.101-5: "NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements" +- [12] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment ". +- [13] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities". + +--- + +## 3 Definitions of terms, symbols and abbreviations + +### 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Geosynchronous Earth Orbit:** Earth-centered orbit at approximately 35786 kilometres above Earth's surface and synchronised with Earth's rotation. A geostationary orbit is a non-inclined geosynchronous orbit, i.e. in the Earth's equator plane. + +**Low Earth Orbit:** Orbit around the Earth with an altitude between 300 km, and 1500 km. + +**Non-terrestrial networks:** Networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station. + +**Satellite:** A space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), or Geostationary Earth Orbit (GEO). + +**Satellite Access Node:** see definition in TS 38.108 [4]. + +**UE transmission bandwidth configuration:** Set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| $\Delta F_{\text{Global}}$ | Granularity of the global frequency raster | +| $\Delta F_{\text{Raster}}$ | Band dependent channel raster granularity | +| $BW_{\text{Channel}}$ | Channel bandwidth | +| $BW_{\text{interferer}}$ | Bandwidth of the interferer | +| $F_{\text{DL\_low}}$ | The lowest frequency of the downlink operating band | +| $F_{\text{DL\_high}}$ | The highest frequency of the downlink operating band | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL\_high}}$ | The highest frequency of the uplink operating band | +| $F_{\text{Interferer}}$ | Frequency of the interferer | +| $F_{\text{Interferer}}(\text{offset})$ | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | +| $F_{\text{Ioffset}}$ | Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) | +| $F_{\text{OOB}}$ | The boundary between the NR out of band emission and spurious emission domains | +| $F_{\text{REF}}$ | RF reference frequency | +| $F_{\text{REF-Offs}}$ | Offset used for calculating $F_{\text{REF}}$ | +| $F_{\text{uw}}(\text{offset})$ | The frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the interferer | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{\text{REF-Offs}}$ | Offset used for calculating $N_{\text{REF}}$ | +| $P_{\text{Interferer}}$ | Modulated mean power of the interferer | +| $P_{\text{uw}}$ | Power of an unwanted DL signal | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------------|----------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| A-MPR | Additional Maximum Power Reduction | +| BW | Bandwidth | +| BWP | Bandwidth Part | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| DTX | Discontinuous Transmission | + +| | | +|----------|------------------------------------------------------------------------| +| EIRP | Equivalent Isotropically Radiated Power | +| EVM | Error Vector Magnitude | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GEO | Geosynchronous Earth Orbit | +| GSCN | Global Synchronization Channel Number | +| IBB | In-band Blocking | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LEO | Low Earth Orbiting | +| MBW | Measurement bandwidth defined for the protected band | +| MEO | Medium Earth Orbiting | +| MOP | Maximum Output Power | +| MPR | Allowed maximum power reduction | +| MSD | Maximum Sensitivity Degradation | +| NGEO | Non-Geostationary Earth Orbiting | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NS | Network Signalling | +| NTN | Non-Terrestrial Network | +| OCNG | OFDMA Channel Noise Generator | +| OOB | Out-of-band | +| PRB | Physical Resource Block | +| QAM | Quadrature Amplitude Modulation | +| RAN | Radio Access Network | +| RE | Resource Element | +| REFSENS | REference SENSitivity | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RSRP | Reference Signal Receive Power | +| RSRQ | Reference Signal Receive Quality | +| RX | Receiver | +| SAN | Satellite Access Node | +| SC | Single Carrier | +| SCS | Subcarrier spacing | +| SEM | Spectrum Emission Mask | +| SNR | Signal-to-Noise Ratio | +| SRS | Sounding Reference Symbol | +| SS | Synchronization Symbol | +| TN | Terrestrial Network | +| TX | Transmitter | +| TxD | Tx Diversity | +| UE | User Equipment | + +## 4 General + +### 4.1 Relationship between minimum requirements and test requirements + +TS 38.101-5 [11] is a Single-RAT specification for satellite NR UE, covering RF characteristics and minimum performance requirements. Conformance to the TS 38.101-5 [11] is demonstrated by fulfilling the test requirements specified in the present document. + +The Minimum Requirements given in TS 38.101-5 [11] makes no allowance for measurement uncertainty (MU). The present document defines test tolerances (TT). These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +The measurement results returned by the test system are compared - without any modification - against the test requirements as defined by the various levels of "shared risk" principle as described below. + +- a) Core specification value is not relaxed by any relaxation value ( $TT=0$ ). For each single measurement, the probability of a borderline good UE being judged as FAIL equals the probability of a borderline bad UE being judged as PASS. + - Test tolerances equal to 0 ( $TT=0$ ) are considered in this specification. +- b) Core specification value is relaxed by a relaxation value ( $TT>0$ ). For each single measurement, the probability of a borderline bad UE being judged as PASS is greater than the probability of a borderline good UE being judged as FAIL. + - Test tolerances lower than measurement uncertainty and greater than 0 ( $0 < TT < MU$ ) are considered in this specification. + - Test tolerances up to measurement uncertainty ( $TT = MU$ ) are considered in this specification which is also known as "Never fail a good DUT" principle. +- c) Core specification value is tightened by a stringent value ( $TT<0$ ). For each single measurement, the probability of a borderline good UE being judged as FAIL is greater than the probability of a borderline bad UE being judged as PASS. + +Test tolerances lower than 0 ( $TT<0$ ) are not considered in this specification.. + +The "Never fail a good DUT" and the "Shared Risk" principles are defined in Recommendation ITU-R M.1545 [3]. + +## 4.2 Applicability of minimum requirements + +The applicability of each requirement is described under clauses 6.1, 7.1, 8.1 of TS 38.101-5 [11]. + +The conducted minimum requirements specified in the present document shall be met in all applicable scenarios for FR1. + +The spurious emissions power requirements are for the long-term average of the power. For the purpose of reducing measurement uncertainty, it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal. + +## 4.3 Specification suffix information + +Specification suffix information is not defined for the time being in Release 17. + +## 4.4 Relationship with core specifications + +TS 38.101-5 [11] specifies the minimum RF and performance requirements for NR User Equipment (UE) operating in a Non-Terrestrial Network. TS 38.108 [4] specifies the minimum RF and performance requirements of Satellite Access Node (SAN). + +--- + +# 5 Operating bands and channel arrangement + +## 5.1 General + +The channel arrangements presented in this clause are based on the operating bands and channel bandwidths defined in the present release of specifications. + +NOTE: Other operating bands and channel bandwidths may be considered in future Releases. + +Requirements throughout the RF specifications are in many cases defined separately for different frequency ranges (FR). The frequency ranges in which NTN satellite can operate according to this version of the specification are identified as described in Table 5.1-1. + +Table 5.1-1: Definition of frequency ranges + +| Frequency range designation | Corresponding frequency range | +|-----------------------------|-------------------------------| +| FR1 | 410 MHz – 7,125 MHz | + +The present specification covers FR1 operating bands. + +## 5.2 Operating bands + +### 5.2.1 General + +NTN satellite covers FR1 operating bands in the present specification. + +### 5.2.2 Operating bands with conducted requirements + +NTN satellite is designed to operate in the operating bands defined in Table 5.2.2-1. + +Table 5.2.2-1: NTN satellite bands in FR1 + +| NTN satellite operating band | Uplink (UL) operating band
Satellite Access Node receive / UE transmit
$F_{UL,low} - F_{UL,high}$ | Downlink (DL) operating band
Satellite Access Node transmit / UE receive
$F_{DL,low} - F_{DL,high}$ | Duplex mode | +|------------------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------| +| n256 | 1,980 MHz – 2,010 MHz | 2,170 MHz – 2,200 MHz | FDD | +| n255 | 1,626.5 MHz – 1,660.5 MHz | 1,525 MHz – 1,559 MHz | FDD | + +NOTE: NTN satellite bands are numbered in descending order from n256. + +### 5.2.3 reserved (for radiated requirements) + +[To be updated] + +## 5.3 UE channel bandwidth + +### 5.3.1 General + +The UE channel bandwidth supports a single RF carrier in the uplink or downlink at the UE. From a SAN perspective, different UE channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs connected to the SAN. + +From a UE perspective, the UE is configured with one or more BWP / carriers, each with its own UE channel bandwidth. The UE does not need to be aware of the SAN channel bandwidth or how the SAN allocates bandwidth to different UEs. + +The placement of the UE channel bandwidth for each UE carrier is flexible but can only be completely within the SAN channel bandwidth. + +The relationship between the channel bandwidth, the guardband and the maximum transmission bandwidth configuration is shown in Figure 5.3.1-1. + +![Figure 5.3.1-1: Definition of the channel bandwidth and the maximum transmission bandwidth configuration for one channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside, a dashed vertical line on the left marks the start of 'Active Resource Blocks', represented by a group of blue vertical rectangles. A double-headed arrow over these blocks is labeled 'Transmission Bandwidth [RB]'. To the right of the blue blocks, a single vertical rectangle is labeled 'Resource Block'. A double-headed arrow below the axis, spanning from the left channel edge to the start of the active blocks, is labeled 'Guardband, can be asymmetric'. Another double-headed arrow spans from the end of the active blocks to the right channel edge.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 5.3.1-1: Definition of the channel bandwidth and the maximum transmission bandwidth configuration for one channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside, a dashed vertical line on the left marks the start of 'Active Resource Blocks', represented by a group of blue vertical rectangles. A double-headed arrow over these blocks is labeled 'Transmission Bandwidth [RB]'. To the right of the blue blocks, a single vertical rectangle is labeled 'Resource Block'. A double-headed arrow below the axis, spanning from the left channel edge to the start of the active blocks, is labeled 'Guardband, can be asymmetric'. Another double-headed arrow spans from the end of the active blocks to the right channel edge. + +Figure 5.3.1-1: Definition of the channel bandwidth and the maximum transmission bandwidth configuration for one channel + +### 5.3.2 Maximum transmission bandwidth configuration + +The maximum transmission bandwidth configuration $N_{RB}$ for each UE channel bandwidth and subcarrier spacing is specified in Table 5.3.2-1. + +Table 5.3.2-1: Maximum transmission bandwidth configuration $N_{RB}$ + +| SCS (kHz) | 5 | 10 | 15 | 20 | +|-----------|----------|----------|----------|----------| +| | MHz | MHz | MHz | MHz | +| | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | +| 15 | 25 | 52 | 79 | 106 | +| 30 | 11 | 24 | 38 | 51 | +| 60 | N/A | 11 | 18 | 24 | + +### 5.3.3 Minimum guardband and transmission bandwidth configuration + +The minimum guardband for each UE channel bandwidth and SCS is specified in Table 5.3.3-1, + +Table 5.3.3-1: Minimum guardband for each UE channel bandwidth and SCS (kHz) + +| SCS (kHz) | 5 | 10 | 15 | 20 | +|-----------|-------|-------|-------|-------| +| | MHz | MHz | MHz | MHz | +| 15 | 242.5 | 312.5 | 382.5 | 452.5 | +| 30 | 505 | 665 | 645 | 805 | +| 60 | N/A | 1,010 | 990 | 1,330 | + +NOTE: The minimum guardbands have been calculated using the following equation: $(BW_{Channel} \times 1,000 \text{ (kHz)} - N_{RB} \times SCS \times 12) / 2 - SCS/2$ , where $N_{RB}$ are from Table 5.3.2-1. + +Figure 5.3.3-1: Void + +The number of RBs configured in any channel bandwidth shall ensure that the minimum guardband specified in this clause is met. + +![Figure 5.3.3-2: UE PRB utilization diagram. It shows a horizontal axis labeled 'f' representing frequency. A rectangular block represents the 'UE channel BW'. Inside this block, there are two dashed vertical lines near the edges, with a label 'Minimum guardband' and arrows pointing to them. Below the block, a double-headed arrow indicates the 'UE channel BW'. To the right of the block, a label 'All PRBs falling within UE channel bandwidth not covering the minimum guardband can be used' has an arrow pointing into the block.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +17 + +Figure 5.3.3-2: UE PRB utilization diagram. It shows a horizontal axis labeled 'f' representing frequency. A rectangular block represents the 'UE channel BW'. Inside this block, there are two dashed vertical lines near the edges, with a label 'Minimum guardband' and arrows pointing to them. Below the block, a double-headed arrow indicates the 'UE channel BW'. To the right of the block, a label 'All PRBs falling within UE channel bandwidth not covering the minimum guardband can be used' has an arrow pointing into the block. + +**Figure 5.3.3-2: UE PRB utilization** + +In the case that multiple numerologies are multiplexed in the same symbol, the minimum guard band on each side of the carrier is the guard band applied at the configured SAN channel bandwidth for the numerology that is transmitted/received immediately adjacent to the guard band. + +![Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies diagram. It shows a horizontal axis. A central rectangular block is divided into two parts labeled 'Numerology X' and 'Numerology Y'. Above this block is a double-headed arrow labeled 'SAN channel BW'. At the left and right edges of the SAN channel BW, there are dashed vertical lines. Below the left dashed line is a label 'Guardband defined for numerology X when transmitted across full SAN channel BW' with an arrow pointing to the line. Similarly, below the right dashed line is a label 'Guardband defined for numerology Y when transmitted across full SAN channel BW' with an arrow pointing to the line.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies diagram. It shows a horizontal axis. A central rectangular block is divided into two parts labeled 'Numerology X' and 'Numerology Y'. Above this block is a double-headed arrow labeled 'SAN channel BW'. At the left and right edges of the SAN channel BW, there are dashed vertical lines. Below the left dashed line is a label 'Guardband defined for numerology X when transmitted across full SAN channel BW' with an arrow pointing to the line. Similarly, below the right dashed line is a label 'Guardband defined for numerology Y when transmitted across full SAN channel BW' with an arrow pointing to the line. + +**Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies** + +NOTE: Figure 5.3.3-2 is not intended to imply the size of any guard between the two numerologies. Inter-numerology guard band within the carrier is implementation dependent. + +### 5.3.4 RB alignment + +The RB alignment refers to NR RB alignments as specified in 3GPP TS 38.101-1 [5] clause 5.3.4. + +### 5.3.5 UE channel bandwidth per operating band + +The requirements in this specification apply to the combination of channel bandwidths, SCS and operating bands shown in Table 5.3.5-1. The transmission bandwidth configuration in Table 5.3.2-1 shall be supported for each of the specified channel bandwidths. The channel bandwidths are specified for both the TX and RX path. + +**Table 5.3.5-1: Channel bandwidths for each NTN satellite band** + +| NTN satellite band | SCS kHz | UE Channel bandwidth (MHz) | | | | +|--------------------|---------|----------------------------|----|----|----| +| | | 5 | 10 | 15 | 20 | +| n256 | 15 | 5 | 10 | 15 | 20 | +| | 30 | | 10 | 15 | 20 | +| | 60 | | 10 | 15 | 20 | +| n255 | 15 | 5 | 10 | 15 | 20 | +| | 30 | | 10 | 15 | 20 | +| | 60 | | 10 | 15 | 20 | + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +#### 5.4.1.1 Channel spacing for adjacent NTN satellite carriers + +The channel spacing for adjacent NTN satellite carriers refers to the NR channel spacing as specified in TS 38.101-1 [5] clause 5.4.1.1. + +### 5.4.2 Channel raster + +#### 5.4.2.1 NR-ARFCN and channel raster + +The global frequency channel raster defines a set of RF reference frequencies $F_{REF}$ . The RF reference frequency is used in signalling to identify the position of RF channels, SS blocks and other elements. + +The global frequency raster is defined for all frequencies from 0 to 100 GHz. The granularity of the global frequency raster is $\Delta F_{Global}$ . + +RF reference frequencies are designated by an NR Absolute Radio Frequency Channel Number (NR-ARFCN) in the range (0...2016666) on the global frequency raster. The relation between the NR-ARFCN and the RF reference frequency $F_{REF}$ in MHz is given by the following equation, where $F_{REF-Offs}$ and $N_{REF-Offs}$ are given in Table 5.4.2.1-1 and $N_{REF}$ is the NR-ARFCN. + +$$F_{REF} = F_{REF-Offs} + \Delta F_{Global} (N_{REF} - N_{REF-Offs})$$ + +**Table 5.4.2.1-1: NR-ARFCN parameters for the global frequency raster** + +| Frequency range (MHz) | $\Delta F_{Global}$ (kHz) | $F_{REF-Offs}$ (MHz) | $N_{REF-Offs}$ | Range of $N_{REF}$ | +|-----------------------|---------------------------|----------------------|----------------|--------------------| +| 0 – 3,000 | 5 | 0 | 0 | 0 – 599,999 | + +The channel raster defines a subset of RF reference frequencies that can be used to identify the RF channel position in the uplink and downlink. The RF reference frequency for an RF channel maps to a resource element on the carrier. For each operating band, a subset of frequencies from the global frequency raster are applicable for that band and forms a channel raster with a granularity $\Delta F_{Raster}$ , which may be equal to or larger than $\Delta F_{Global}$ . + +The mapping between the channel raster and corresponding resource element is given in clause 5.4.2.2. The applicable entries for each operating band are defined in clause 5.4.2.3. + +#### 5.4.2.2 Channel raster to resource element mapping + +The mapping between the RF reference frequency on the channel raster and the corresponding resource element refers to the NR requirements specified in 3GPP TS 38.101-1 [5] clause 5.4.2.2. + +#### 5.4.2.3 Channel raster entries for each operating band + +The RF channel positions on the channel raster in each NTN satellite operating band are given through the applicable NR-ARFCN in Table 5.4.2.3-1, using the channel raster to resource element mapping in clause 5.4.2.2. + +For NTN satellite operating bands with 100 kHz channel raster, $\Delta F_{Raster} = 20 \times \Delta F_{Global}$ . In this case every 20th NR-ARFCN within the operating band are applicable for the channel raster within the operating band and the step size for the channel raster in Table 5.4.2.3-1 is given as <20>. + +Table 5.4.2.3-1: Applicable NR-ARFCN per operating band + +| NTN satellite operating band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink Range of $N_{\text{REF}}$ (First – – Last) | Downlink Range of $N_{\text{REF}}$ (First – – Last) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------| +| n256 | 100 | 396,000 – <20> – 402,000 | 434,000 – <20> – 440,000 | +| n255 | 100 | 325,300 – <20> – 332,100 | 305,000 – <20> – 311,800 | +| NOTE: The channel numbers that designate carrier frequencies so close to the operating band edges that the carrier extends beyond the operating band edge shall not be used. | | | | + +## 5.4.3 Synchronization raster + +### 5.4.3.1 Synchronization raster and numbering + +The synchronization raster indicates the frequency positions of the synchronization block that can be used by the UE for system acquisition when explicit signalling of the synchronization block position is not present. + +A global synchronization raster is defined for all frequencies. The frequency position of the SS block is defined as $SS_{\text{REF}}$ with corresponding number GSCN. The parameters defining the $SS_{\text{REF}}$ and GSCN for all the frequency ranges are in Table 5.4.3.1-1. + +The resource element corresponding to the SS block reference frequency $SS_{\text{REF}}$ is given in clause 5.4.3.2. The synchronization raster and the subcarrier spacing of the synchronization block is defined separately for each band. + +Table 5.4.3.1-1: GSCN parameters for the global frequency raster + +| Frequency range | SS Block frequency position $SS_{\text{REF}}$ | GSCN | Range of GSCN | +|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------|---------------| +| 0 – 3,000 MHz | $N * 1,200 \text{ kHz} + M * 50 \text{ kHz}$ ,
$N=1:2,499, M \in \{1,3,5\}^1$ | $3N + (M-3)/2$ | 2 – 7,498 | +| NOTE: The default value for operating bands with which only support SCS spaced channel raster(s) is $M=3$ . | | | | + +### 5.4.3.2 Synchronization raster to synchronization block resource element mapping + +The mapping between the synchronization raster and the corresponding resource element of the SS block refers to 3GPP TS 38.101-1 [5] clause 5.4.3.2. + +### 5.4.3.3 Synchronization raster entries for each operating band + +The synchronization raster for each band is given in Table 5.4.3.3-1. The distance between applicable GSCN entries is given by the indicated in Table 5.4.3.3-1. + +Table 5.4.3.3-1: Applicable SS raster entries per operating band + +| NTN satellite operating band | SS Block SCS | SS Block pattern 1 | Range of GSCN (First – – Last) | +|-------------------------------------------------------------------------|--------------|-------------------------------|--------------------------------------------| +| n256 | 15 kHz | Case A | 5,429 – <1> – 5,494 | +| n255 | 15 kHz | Case A | 3,818 – <1> – 3,892 | +| | 30 kHz | Case B | 3,824 – <1> – 3,886 | +| NOTE : SS Block pattern is defined in clause 4.1 in 3GPP TS 38.213 [7]. | | | | + +## 5.4.4 TX–RX frequency separation + +The default TX channel (carrier centre frequency) to RX channel (carrier centre frequency) separation for operating bands is specified in Table 5.4.4-1. + +Table 5.4.4-1: UE TX-RX frequency separation + +| NTN Satellite Operating Band | TX – RX carrier centre frequency separation | +|------------------------------|---------------------------------------------| +| n256 | 190 MHz | +| n255 | -101.5 MHz | + +## 6 Transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the transmitter characteristics are specified at the antenna connector of the UE with a single or multiple transmit antenna(s). For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. Handheld power class 3 UE is assumed in Release 17 for satellite access. + +All requirements in this clause are applicable to devices supporting GSO and/or NGSO satellites. + +Unless otherwise stated, Channel Bandwidth shall be prioritized in the selecting of test points. Subcarrier spacing shall be selected after Test Channel Bandwidth is selected. + +Uplink RB allocations given in Table 6.1-1 are used throughout this clause, unless otherwise stated by the test case. + +Table 6.1-1: Common uplink configuration + +| Channel Bandwidth | SCS(kHz) | OFDM | RB allocation | | | | | | | | +|-------------------|----------|-------|----------------|-----------------|---------------|----------------|------------|--------------------|----------------|-----------------| +| | | | Edge_Full_Left | Edge_Full_Right | Edge_1RB_Left | Edge_1RB_Right | Outer_Full | Inner_Full | Inner_1RB_Left | Inner_1RB_Right | +| 5MHz | 15 | DFT-s | 2@0 | 2@23 | 1@0 | 1@24 | 25@0 | 12@6 | 1@1 | 1@23 | +| | | CP | 2@0 | 2@23 | 1@0 | 1@24 | 25@0 | 13@6 | 1@1 | 1@23 | +| | 30 | DFT-s | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| | | CP | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| | 60 | DFT-s | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| | | CP | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| 10MHz | 15 | DFT-s | 2@0 | 2@50 | 1@0 | 1@51 | 50@0 | 25@12 | 1@1 | 1@50 | +| | | CP | 2@0 | 2@50 | 1@0 | 1@51 | 52@0 | 26@13 | 1@1 | 1@50 | +| | 30 | DFT-s | 2@0 | 2@22 | 1@0 | 1@23 | 24@0 | 12@6 | 1@1 | 1@22 | +| | | CP | 2@0 | 2@22 | 1@0 | 1@23 | 24@0 | 12@6 | 1@1 | 1@22 | +| | 60 | DFT-s | 2@0 | 2@9 | 1@0 | 1@10 | 10@0 | 5@2 1 | 1@1 | 1@9 | +| | | CP | 2@0 | 2@9 | 1@0 | 1@10 | 11@0 | 5@2 1 | 1@1 | 1@9 | +| 15MHz | 15 | DFT-s | 2@0 | 2@77 | 1@0 | 1@78 | 75@0 | 36@18 | 1@1 | 1@77 | +| | | CP | 2@0 | 2@77 | 1@0 | 1@78 | 79@0 | 39@19 1 | 1@1 | 1@77 | +| | 30 | DFT-s | 2@0 | 2@36 | 1@0 | 1@37 | 36@0 | 18@9 | 1@1 | 1@36 | +| | | CP | 2@0 | 2@36 | 1@0 | 1@37 | 38@0 | 19@9 | 1@1 | 1@36 | +| | 60 | DFT-s | 2@0 | 2@16 | 1@0 | 1@17 | 18@0 | 9@4 | 1@1 | 1@16 | +| | | CP | 2@0 | 2@16 | 1@0 | 1@17 | 18@0 | 9@4 | 1@1 | 1@16 | +| 20MHz | 15 | DFT-s | 2@0 | 2@104 | 1@0 | 1@105 | 100@0 | 50@25 | 1@1 | 1@104 | +| | | CP | 2@0 | 2@104 | 1@0 | 1@105 | 106@0 | 53@26 | 1@1 | 1@104 | +| | 30 | DFT-s | 2@0 | 2@49 | 1@0 | 1@50 | 50@0 | 25@12 | 1@1 | 1@49 | +| | | CP | 2@0 | 2@49 | 1@0 | 1@50 | 51@0 | 25@12 1 | 1@1 | 1@49 | +| | 60 | DFT-s | 2@0 | 2@22 | 1@0 | 1@23 | 24@0 | 12@6 | 1@1 | 1@22 | +| | | CP | 2@0 | 2@22 | 1@0 | 1@23 | 24@0 | 12@6 | 1@1 | 1@22 | + +NOTE 1: The allocated RB number $L_{CRB}$ is $\text{ceil}(N_{RB}/2) - 1$ in order to meet Inner RB allocation definition ( $RB_{Start,Low} \leq RB_{Start} \leq RB_{Start,High}$ ) described in subclause 6.2.2 of TS 38.101-1 [5]. + +## 6.2 Transmitter power + +### 6.2.1 UE maximum output power + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated +- Verification of UE frequency pre-compensation is to be updated + +#### 6.2.1.1 Test purpose + +To verify that the error of the UE maximum output power does not exceed the range prescribed by the specified nominal maximum output power and tolerance. + +An excess maximum output power has the possibility to interfere to other channels or other systems. A small maximum output power decreases the coverage area. + +#### 6.2.1.2 Test applicability + +This test case applies to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +#### 6.2.1.3 Minimum conformance requirements + +The following UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth of NR carrier unless otherwise stated. The period of measurement shall be at least one sub frame (1 ms). + +**Table 6.2.1.3-1: UE Power Class** + +| NR satellite band | Class 3 (dBm) | Tolerance (dB) | +|-------------------------------------------------------------------------------------------------------------|---------------|----------------| +| n256 | 23 | ±2 | +| n255 | 23 | ±2 | +| NOTE 1: $P_{\text{PowerClass}}$ is the maximum UE power specified without taking into account the tolerance | | | +| NOTE 2: Power class 3 is default power class unless otherwise stated | | | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.2.1. + +#### 6.2.1.4 Test description + +##### 6.2.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.2.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +Table 6.2.1.4.1-1: Test Configuration Table + +| | | Initial Conditions | | +|--------------------------------------------------------------------------|----------------------------------------|------------------------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | | Low range, Mid range, High range | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | | Lowest, Mid, Highest | | +| Test SCS as specified in Table 5.3.5-1 | | Lowest, Highest | | +| | | Test Parameters | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | N/A for maximum output power test case | Modulation (NOTE 2) | RB allocation (NOTE 1) | +| 1 | | DFT-s-OFDM Pi/2 BPSK | Inner Full | +| 2 | | DFT-s-OFDM Pi/2 BPSK | Inner 1RB Left | +| 3 | | DFT-s-OFDM Pi/2 BPSK | Inner 1RB Right | +| 4 | | DFT-s-OFDM QPSK | Inner Full | +| 5 | | DFT-s-OFDM QPSK | Inner 1RB Left | +| 6 | | DFT-s-OFDM QPSK | Inner 1RB Right | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1. + +NOTE 2: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports half Pi BPSK in FR1. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] Annex C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] Annex G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.1.4.1-1. +5. Propagation conditions are set according to Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.1.4.3. + +#### 6.2.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.2.1.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in every uplink scheduling information to the UE; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode. The period of measurement shall be at least the continuous duration of one active sub-frame (1 ms) and in the uplink symbols. For TDD symbols with transient periods are not under test. + +#### 6.2.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 and 5.4 with the following exceptions. + +Table 6.2.1.4.3-1: *PUSCH-Config* + +| | +|-----------------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|-----------------------------------------------------------------------------------------------------| + +## 6.2.1.5 Test requirement + +The maximum output power, derived in step 3 shall be within the range prescribed by the nominal maximum output power and tolerance in Table 6.2.1.5-1 for Power Class 3. + +Table 6.2.1.5-1: Maximum Output Power test requirement for Power Class 3 + +| NR satellite band | Class 3 (dBm) | Tolerance (dB) | +|-------------------------------------------------------------------------------------------------------------|---------------|----------------| +| N256 | 23 | $\pm 2 \pm TT$ | +| N255 | 23 | $\pm 2 \pm TT$ | +| NOTE 1: $P_{\text{PowerClass}}$ is the maximum UE power specified without taking into account the tolerance | | | +| NOTE 2: Power class 3 is default power class unless otherwise stated | | | +| NOTE 3: TT for each frequency and channel bandwidth is specified in Table 6.2.1.5-2 | | | + +Table 6.2.1.5-2: Test Tolerance (UE maximum output power) + +[to be updated] + +## 6.2.2 UE maximum output power reduction + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access is to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated +- Verification of UE frequency pre-compensation is to be updated + +### 6.2.2.1 Test purpose + +The number of RB identified in Table 6.2.2.3-1 is based on meeting the requirements for adjacent channel leakage ratio and the maximum power reduction (MPR) due to Cubic Metric (CM). + +### 6.2.2.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +NOTE: Test execution is not necessary if TS 38.521-5 clause 6.5.2.4.1 is executed. + +### 6.2.2.3 Minimum conformance requirements + +UE is allowed to reduce the maximum output power due to higher order modulations and transmit bandwidth configurations. For UE power class 3, the allowed maximum power reduction (MPR) is defined in Table 6.2.2.3-1 for channel bandwidths $\leq 100$ MHz. The $\Delta\text{MPR}$ is set to zero. + +The allowed MPR for SRS, PUCCH formats 0, 1, 3 and 4, and PRACH shall be as specified for QPSK modulated DFT-s-OFDM of equivalent RB allocation. The allowed MPR for PUCCH format 2 shall be as specified for QPSK modulated CP-OFDM of equivalent RB allocation. + +Table 6.2.2.3-1: Maximum power reduction (MPR) for power class 3 + +| Modulation | | MPR (dB) | | | +|------------|-------------------------------------|---------------------|----------------------|----------------------| +| | | Edge RB allocations | Outer RB allocations | Inner RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 0.5$ | | 0 | +| | Pi/2 BPSK
w Pi/2
BPSK
DMRS | $\leq 0.5$ | 0 | | +| | QPSK | $\leq 1$ | | 0 | +| | 16 QAM | $\leq 2$ | | $\leq 1$ | +| | 64 QAM | $\leq 2.5$ | | | +| | 256 QAM | $\leq 4.5$ | | | +| CP-OFDM | QPSK | $\leq 3$ | | $\leq 1.5$ | +| | 16 QAM | $\leq 3$ | | $\leq 2$ | +| | 64 QAM | $\leq 3.5$ | | | +| | 256 QAM | $\leq 6.5$ | | | + +RB allocation ranges for Outer and Inner RB allocations are specified in TS 38.521-1 [2] 6.2.2.3. + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.2.2. + +## 6.2.2.4 Test description + +### 6.2.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Table 6.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +Table 6.2.2.4.1-1: Test Configuration Table for power class 3 (contiguous allocation) + +| | | | Initial Conditions | | +|--------------------------------------------------------------------------|---------|-------------------------------------------------|---------------------------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | | | Low range, High range | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | | | Lowest, Highest | | +| Test SCS as specified in Table 5.3.5-1 | | | Lowest, Highest | | +| Test Parameters for Channel Bandwidths | | | | | +| Test ID | Freq | Downlink Configuration | Uplink Configuration | | +| | | | Modulation (NOTE 2) | RB allocation (NOTE 1) | +| 1 | Default | N/A for Maximum Power Reduction (MPR) test case | DFT-s-OFDM Pi/2 BPSK | Inner Full | +| 2 | Low | | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | +| 3 | High | | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | +| 4 | Default | | DFT-s-OFDM Pi/2 BPSK | Outer Full | +| 5 | Default | | DFT-s-OFDM QPSK | Inner Full | +| 6 | Low | | DFT-s-OFDM QPSK | Edge_1RB_Left | +| 7 | High | | DFT-s-OFDM QPSK | Edge_1RB_Right | +| 8 | Default | | DFT-s-OFDM QPSK | Outer Full | +| 9 | Default | | DFT-s-OFDM 16 QAM | Inner Full | +| 10 | Low | | DFT-s-OFDM 16 QAM | Edge_1RB_Left | +| 11 | High | | DFT-s-OFDM 16 QAM | Edge_1RB_Right | +| 12 | Default | | DFT-s-OFDM 16 QAM | Outer Full | +| 13 | Low | | DFT-s-OFDM 64 QAM | Edge_1RB_Left | +| 14 | High | | DFT-s-OFDM 64 QAM | Edge_1RB_Right | +| 15 | Default | | DFT-s-OFDM 64 QAM | Outer Full | +| 16 | Low | | DFT-s-OFDM 256 QAM | Edge_1RB_Left | +| 17 | High | | DFT-s-OFDM 256 QAM | Edge_1RB_Right | +| 18 | Default | | DFT-s-OFDM 256 QAM | Outer Full | +| 19 | Default | | CP-OFDM QPSK | Inner Full | +| 20 | Low | | CP-OFDM QPSK | Edge_1RB_Left | +| 21 | High | | CP-OFDM QPSK | Edge_1RB_Right | +| 22 | Default | | CP-OFDM QPSK | Outer Full | +| 23 | Default | | CP-OFDM 16 QAM | Inner Full | +| 24 | Low | | CP-OFDM 16 QAM | Edge_1RB_Left | +| 25 | High | | CP-OFDM 16 QAM | Edge_1RB_Right | +| 26 | Default | | CP-OFDM 16 QAM | Outer Full | +| 27 | Low | | CP-OFDM 64 QAM | Edge_1RB_Left | +| 28 | High | | CP-OFDM 64 QAM | Edge_1RB_Right | +| 29 | Default | | CP-OFDM 64 QAM | Outer Full | +| 30 | Low | | CP-OFDM 256 QAM | Edge_1RB_Left | +| 31 | High | | CP-OFDM 256 QAM | Edge_1RB_Right | +| 32 | Default | | CP-OFDM 256 QAM | Outer Full | +| 33 3 | Low | | DFT-s-OFDM Pi/2 BPSK w Pi/2 BPSK DMRS | Edge_1RB_Left | +| 34 3 | High | | DFT-s-OFDM Pi/2 BPSK w Pi/2 BPSK DMRS | Edge_1RB_Right | +| 35 3 | Default | | DFT-s-OFDM Pi/2 BPSK w Pi/2 BPSK DMRS | Outer Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1. + +NOTE 2: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports Pi/2 BPSK in FR1. + +NOTE 3: Applicable to UEs indicating support for UE capability *lowPAPR-DMRS-PUSCHwithPrecoding-r16*. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.2.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] Annex C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.2.4.1-1. + +5. Propagation conditions are set according to TS 38.521-1 [2] Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.2.4.3. + +#### 6.2.2.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.2.2.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in every uplink scheduling information to the UE; allow at least 200 ms for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode. The period of measurement shall be at least the continuous duration of 1 ms over consecutive active uplink slots. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.2.2.4.1-1, send an NR RRCReconfiguration message according to TS 38.508-1 [12] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +#### 6.2.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 and 5.4 with the following exceptions: + +**Table 6.2.2.4.3-1: PUSCH-Config** + +| Derivation Path: TS 38.508-1 [12] subclause 4.6.3 Table 4.6.3-118 PUSCH-Config | | | | +|--------------------------------------------------------------------------------|-------------------------|---------|------------------------------| +| Information Element | Value/remark | Comment | Condition | +| PUSCH-Config ::= SEQUENCE { | | | | +| resourceAllocation | resourceAllocationType0 | | Almost contiguous allocation | +| | resourceAllocationType1 | | Contiguous allocation | +| } | | | | + +**Table 6.2.2.4.3-2: DMRS-UplinkConfig (Test ID 37 - 39 in Table 6.2.2.4.1-1)** + +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-51 | | | | +|---------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| DMRS-UplinkConfig ::= SEQUENCE { | | | | +| transformPrecodingEnabled SEQUENCE { | | | | +| dmrs-UplinkTransformPrecoding-r16 | | | | +| SEQUENCE { | | | | +| pi2BPSK-ScramblingID0 | Not present | | | +| pi2BPSK-ScramblingID1 | Not present | | | +| } | | | | +| } | | | | +| } | | | | + +Table 6.2.2.4.3-3: ServingCellConfig + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-167 | | | | +|---------------------------------------------------|--------------|---------|-----------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| ServingCellConfig ::= SEQUENCE { | | | | +| uplinkConfig SEQUENCE { | | | | +| powerBoostPi2BPSK | 1 | | Test IDs where NOTE 3 in Table 6.2.2.4.1-1 applies. | +| | 0 | | Test IDs where NOTE 4 in Table 6.2.2.4.1-1 applies. | +| } | | | | +| } | | | | + +## 6.2.2.5 Test requirement + +The maximum output power, derived in step 3 shall be within the range prescribed by the nominal maximum output power and tolerance in Table 6.2.2.5-1. + +Table 6.2.2.5-1: UE MPR test requirements for power class 3 (contiguous allocation) + +| Test ID | P PowerClass (dBm) | ΔP PowerClass (dB) | MPR (dB) | ΔT C,c (dB) | P CMAX_L,f,c (dBm) | T(P CMAX_L,f,c ) (dB) | T L,c (dB) | Upper limit (dBm) | Lower limit (dBm) | +|---------|-------------------------------|-------------------------------|----------|------------------------|-------------------------------|----------------------------------|-----------------------|-------------------|-------------------| +| 1 | 23 | 0 | 0 | 0 | 23.0 | 2.0 | 2 | 25.0 + TT | 21.0 - TT | +| 2 | 23 | 0 | 0.5 | 0 | 22.5 | 2.0 | 2 | 25.0 + TT | 20.5 - TT | +| 3 | 23 | 0 | 0.5 | 0 | 22.5 | 2.0 | 2 | 25.0 + TT | 20.5 - TT | +| 4 | 23 | 0 | 0.5 | 0 | 22.5 | 2.0 | 2 | 25.0 + TT | 20.5 - TT | +| 5 | 23 | 0 | 0 | 0 | 23.0 | 2.0 | 2 | 25.0 + TT | 21.0 - TT | +| 6 | 23 | 0 | 1 | 0 | 22.0 | 2.0 | 2 | 25.0 + TT | 20.0 - TT | +| 7 | 23 | 0 | 1 | 0 | 22.0 | 2.0 | 2 | 25.0 + TT | 20.0 - TT | +| 8 | 23 | 0 | 1 | 0 | 22.0 | 2.0 | 2 | 25.0 + TT | 20.0 - TT | +| 9 | 23 | 0 | 1 | 0 | 22.0 | 2.0 | 2 | 25.0 + TT | 20.0 - TT | +| 10 | 23 | 0 | 2 | 0 | 21.0 | 2.0 | 2 | 25.0 + TT | 19.0 - TT | +| 11 | 23 | 0 | 2 | 0 | 21.0 | 2.0 | 2 | 25.0 + TT | 19.0 - TT | +| 12 | 23 | 0 | 2 | 0 | 21.0 | 2.0 | 2 | 25.0 + TT | 19.0 - TT | +| 13 | 23 | 0 | 2.5 | 0 | 20.5 | 2.5 | 2 | 25.0 + TT | 18.0 - TT | +| 14 | 23 | 0 | 2.5 | 0 | 20.5 | 2.5 | 2 | 25.0 + TT | 18.0 - TT | +| 15 | 23 | 0 | 2.5 | 0 | 20.5 | 2.5 | 2 | 25.0 + TT | 18.0 - TT | +| 16 | 23 | 0 | 4.5 | 0 | 18.5 | 4.0 | 2 | 25.0 + TT | 14.5 - TT | +| 17 | 23 | 0 | 4.5 | 0 | 18.5 | 4.0 | 2 | 25.0 + TT | 14.5 - TT | +| 18 | 23 | 0 | 4.5 | 0 | 18.5 | 4.0 | 2 | 25.0 + TT | 14.5 - TT | +| 19 | 23 | 0 | 1.5 | 0 | 21.5 | 2.0 | 2 | 25.0 + TT | 19.5 - TT | +| 20 | 23 | 0 | 3 | 0 | 20.0 | 2.5 | 2 | 25.0 + TT | 17.5 - TT | +| 21 | 23 | 0 | 3 | 0 | 20.0 | 2.5 | 2 | 25.0 + TT | 17.5 - TT | +| 22 | 23 | 0 | 3 | 0 | 20.0 | 2.5 | 2 | 25.0 + TT | 17.5 - TT | +| 23 | 23 | 0 | 2 | 0 | 21.0 | 2.0 | 2 | 25.0 + TT | 19.0 - TT | +| 24 | 23 | 0 | 3 | 0 | 20.0 | 2.5 | 2 | 25.0 + TT | 17.5 - TT | +| 25 | 23 | 0 | 3 | 0 | 20.0 | 2.5 | 2 | 25.0 + TT | 17.5 - TT | +| 26 | 23 | 0 | 3 | 0 | 20.0 | 2.5 | 2 | 25.0 + TT | 17.5 - TT | +| 27 | 23 | 0 | 3.5 | 0 | 19.5 | 3.5 | 2 | 25.0 + TT | 16.0 - TT | +| 28 | 23 | 0 | 3.5 | 0 | 19.5 | 3.5 | 2 | 25.0 + TT | 16.0 - TT | +| 29 | 23 | 0 | 3.5 | 0 | 19.5 | 3.5 | 2 | 25.0 + TT | 16.0 - TT | +| 30 | 23 | 0 | 6.5 | 0 | 16.5 | 5.0 | 2 | 25.0 + TT | 11.5 - TT | +| 31 | 23 | 0 | 6.5 | 0 | 16.5 | 5.0 | 2 | 25.0 + TT | 11.5 - TT | +| 32 | 23 | 0 | 6.5 | 0 | 16.5 | 5.0 | 2 | 25.0 + TT | 11.5 - TT | +| 33 | 23 | 0 | 0.5 | 0 | 22.5 | 2.0 | 2 | 25.0 + TT | 20.5 - TT | +| 34 | 23 | 0 | 0.5 | 0 | 22.5 | 2.0 | 2 | 25.0 + TT | 20.5 - TT | +| 35 | 23 | 0 | 0 | 0 | 23 | 2.0 | 2 | 25.0 + TT | 21.0 - TT | + +NOTE 1: PPowerClass is the maximum UE power specified without taking into account the tolerance. + +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2.2.5-2. + +Table 6.2.2.5-2: Test Tolerance (Maximum Power Reduction (MPR)) + +[to be updated] + +## 6.2.3 UE additional maximum output power reduction + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +### 6.2.3.1 Test purpose + +Additional emission requirements can be signalled by the network. Each additional emission requirement is associated with a unique network signalling (NS) value indicated in RRC signalling by an NR frequency band number of the applicable operating band and an associated value in the field *additionalSpectrumEmission*. Throughout this specification, the notion of indication or signalling of an NS value refers to the corresponding indication of an NR satellite band number of the applicable operating band, the IE field *freqBandIndicatorNR* and an associated value of *additionalSpectrumEmission* in the relevant RRC information elements [8]. + +To meet the additional requirements, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in Table 6.2.1.3-1. Unless stated otherwise, the total reduction to UE maximum output power is $\max(\text{MPR}, \text{A-MPR})$ where MPR is defined in clause 6.2.2. Outer and inner allocation notation used in clause 6.2.3 is defined in clause 6.2.2. In absence of modulation and waveform types the A-MPR applies to all modulation and waveform types. + +### 6.2.3.2 Test applicability + +[to be updated] + +### 6.2.3.3 Minimum conformance requirements + +#### 6.2.3.3.1 General + +Table 6.2.3.3.1-1 specifies the additional requirements with their associated network signalling values and the allowed A-MPR and applicable operating band(s) for each NS value. The mapping of NR satellite band numbers and values of the *additionalSpectrumEmission* to network signalling labels is specified in Table 6.2.3.3.1-2. + +Table 6.2.3.3.1-1: Additional maximum power reduction (A-MPR) + +| Network signalling label | Requirements (clause) | NR satellite Band | Channel bandwidth (MHz) | Resources blocks ( $N_{\text{RB}}$ ) | A-MPR (dB) | +|--------------------------|------------------------------------|-------------------|-------------------------|------------------------------------------|------------------------------------------------------| +| NS_01 | | Table 5.2.2-1 | 5, 10, 15, 20 | Table 5.3.2-1 | N/A | +| NS_24 | 6.5.3.3.13 in 3GPP TS 38.101-1 [5] | n256 | 5, 10, 15, 20 | Table 6.2.3.15-1 in 3GPP TS 38.101-1 [5] | Clause 6.2.3.15 in 3GPP TS 38.101-1 [5] 2 | +| NS_02N | 6.5.3.3.2 | n255 | 5, 10, 15, 20 | | N/A | +| NS_100 | 6.5.2.4.2 in 3GPP TS 38.101-1 [5] | n256 1 | | | Table 6.2.3.1-2 in 3GPP TS 38.101-1 [5] | + +NOTE 1: This NS can be signalled for NR bands that have UTRA services deployed. + +NOTE 2: A-MPR for the upper 5 MHz of the band is not specified, and therefore shall be used as a guard band. + +[The NS\_01 label with the field *additionalPmax* [8] absent is default for all NTN satellite bands.] + +**Table 6.2.3.3.1-2: Mapping of network signalling label** + +| NR satellite band | Value of additionalSpectrumEmission | | | | | | | | +|-------------------|-------------------------------------|--------|--------|---|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| n256 | NS_01 | NS_24 | NS_100 | | | | | | +| n255 | NS_01 | NS_02N | | | | | | | + +NOTE: *additionalSpectrumEmission* corresponds to an information element of the same name defined in clause 6.3.2 of 3GPP TS 38.331 [8]. + +**Table 6.2.3.3.1-3: A-MPR for NS\_100 (UTRA protection)** + +| Modulation/Waveform | | Outer (dB) | +|---------------------|-----------|------------| +| DFT-s-OFDM | Pi/2 BPSK | $\leq 2$ | +| | QPSK | $\leq 2$ | +| | 16 QAM | $\leq 2.5$ | +| | 64 QAM | $\leq 3$ | +| | 256 QAM | $\leq 4.5$ | +| CP-OFDM | QPSK | $\leq 4$ | +| | 16 QAM | $\leq 4$ | +| | 64 QAM | $\leq 4$ | +| | 256 QAM | $\leq 6.5$ | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.2.3.1. + +### 6.2.3.3.2 A-MPR for NS\_24 + +**Table 6.2.3.3.2-1: A-MPR regions for NS\_24** + +| Channel Bandwidth, MHz | Carrier Centre Frequency, Fc, MHz | Region A | | Region B | | Region C | | +|------------------------|-----------------------------------|-------------------|------------------|-------------------|------------------|-----------------------------|------------------| +| | | Rbend*12 *SCS MHz | LCRB*12 *SCS MHz | Rbend*12* SCS MHz | LCRB*12 *SCS MHz | Rbend*12* SCS MHz | LCRB*12 *SCS MHz | +| 5MHz | Fc=1,992.5 | | $>3.24$ | | | | | +| 5MHz | Fc=1,997.5 | | $>3.24$ | | | | | +| 5MHz | Fc=2,002.5 | | $>2.16$ | $>3.78$ | $\leq 1.98$ | $\leq 3.6$ | $\leq 1.98$ | +| 10MHz | Fc=1,985 | $>5.4$ | | | | | | +| 10MHz | Fc=1,995 | | $>4.5$ | $>7.56$ | $\leq 4.32$ | $\leq 7.38$ | $\leq 4.32$ | +| 10MHz | Fc=2,000 | $>6.84$ | | $<2.88$ | | $\geq 3.06$
$\leq 6.66$ | $>1.44$ | +| 15MHz | Fc=1,987.5 | | $>7.02$ | $>11.52$ | $\leq 6.84$ | $\leq 11.34$ | $\leq 6.84$ | +| 15MHz | Fc=1,997.5 | $>9.36$ | | $<3.6$ | | $\geq 3.78$
$\leq 9.18$ | $>1.44$ | +| 20MHz | Fc=1,990 | $>13.5$ | | $<4.5$ | | $\geq 4.68$
$\leq 13.32$ | $>2.16$ | +| 20MHz | Fc=1,995 | $>12.6$ | | $<5.4$ | | $\geq 5.58$
$\leq 12.42$ | $>1.44$ | + +NOTE 1: The A-MPR values are listed in Table 6.2.3.3.2-2. +NOTE 2: For any undefined region, MPR applies + +Table 6.2.3.3.2-2: A-MPR for NS\_24 + +| Modulation/Waveform | | Outer (dB) | Inner (dB) | +|---------------------|--------------|------------|------------| +| DFT-s-OFDM | PI/2
BPSK | $\leq 1.5$ | N/A | +| | QPSK | $\leq 2$ | | +| | 16
QAM | $\leq 3$ | | +| | 64
QAM | $\leq 3.5$ | | +| | 256
QAM | $\leq 5.5$ | | +| CP-OFDM | QPSK | $\leq 4$ | | +| | 16
QAM | $\leq 4$ | | +| | 64
QAM | $\leq 4.5$ | | +| | 256
QAM | $\leq 7.5$ | | + +## 6.2.3.4 Test description + +### 6.2.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Tables 6.2.3.4.1-1 to 6.2.3.4.1-30. The details of the uplink reference measurement channels (RMCs) are specified in clause A.2. Configurations of PDSCH and PDCCH before measurement are specified in clause C.2. + +Table 6.2.3.4.1-1: Test Configuration table for NS\_100 + +| Initial Conditions | | | | | | | | +|--------------------------------------------------------------------------|---------|---------|---------|--------------------------|----------------------|------------------------|-----------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | | | | | | | Normal | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | | | | | | | Low range, High range | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | | | | | | | Lowest, Highest | +| Test SCS as specified in Table 5.3.5-1 | | | | | | | Lowest, Highest | +| A-MPR test parameters for NS_100 | | | | | | | | +| Test ID | Freq | ChBw | SCS | Downlink Configuration | Uplink Configuration | | | +| | | | | | Modulation (Note 2) | RB allocation (Note 1) | | +| 1 | Low | Default | Default | N/A for A-MPR test cases | DFT-s OFDM | PI/2 BPSK | Edge_1RB_Left | +| 2 | High | Default | Default | | | PI/2 BPSK | Edge_1RB_Right | +| 3 | Default | Default | Default | | | PI/2 BPSK | Outer_Full | +| 4 | Low | Default | Default | | | QPSK | Edge_1RB_Left | +| 5 | High | Default | Default | | | QPSK | Edge_1RB_Right | +| 6 | Default | Default | Default | | | QPSK | Outer_Full | +| 7 | Low | Default | Default | | | 16 QAM | Edge_1RB_Left | +| 8 | High | Default | Default | | | 16 QAM | Edge_1RB_Right | +| 9 | Default | Default | Default | | | 16 QAM | Outer_Full | +| 10 | Low | Default | Default | | | 64 QAM | Edge_1RB_Left | +| 11 | High | Default | Default | | | 64 QAM | Edge_1RB_Right | +| 12 | Default | Default | Default | | | 64 QAM | Outer_Full | +| 13 | Low | Default | Default | | | 256 QAM | Edge_1RB_Left | +| 14 | High | Default | Default | | | 256 QAM | Edge_1RB_Right | +| 15 | Default | Default | Default | | | 256 QAM | Outer_Full | +| 16 | Low | Default | Default | | CP-s OFDM | QPSK | Edge_1RB_Left | +| 17 | High | Default | Default | | | QPSK | Edge_1RB_Right | +| 18 | Default | Default | Default | | | QPSK | Outer_Full | +| 19 | Low | Default | Default | | | 16 QAM | Edge_1RB_Left | +| 20 | High | Default | Default | | | 16 QAM | Edge_1RB_Right | +| 21 | Default | Default | Default | | | 16 QAM | Outer_Full | +| 22 | Low | Default | Default | | | 64 QAM | Edge_1RB_Left | +| 23 | High | Default | Default | | | 64 QAM | Edge_1RB_Right | +| 24 | Default | Default | Default | | | 64 QAM | Outer_Full | +| 25 | Low | Default | Default | | | 256 QAM | Edge_1RB_Left | +| 26 | High | Default | Default | | | 256 QAM | Edge_1RB_Right | +| 27 | Default | Default | Default | | | 256 QAM | Outer_Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 unless otherwise stated in this table. + +NOTE 2: DFT-s-OFDM PI/2 BPSK test applies only for UEs which supports half Pi BPSK in FR1. + +Table 6.2.3.4.1-2: Test Configuration table for NS\_24 + +| Initial Conditions | | | | | | | | | +|--------------------------------------------------------------------------|----------------------|------------|---------|------------------------|------------------------|------------------------|-------------------------------------------------------------------------------|----------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | | | | | | | Normal | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | | | | | | | Refer to uplink carrier centre frequency (F c ) in test parameters | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | | | | | | | Refer to test parameters (5, 10, 15, 20 MHz) | | +| Test SCS as specified in Table 5.3.5-1 | | | | | | | Lowest | | +| A-MPR test parameters for NS_24 | | | | | | | | | +| Test ID | F c (MHz) | ChBw (MHz) | SCS | Downlink Configuration | Uplink Configuration | | | | +| | | | | | Modulation (NOTE 2, 3) | RB allocation (Note 1) | | | +| | | | | | | Region A | Region B | Region C | +| 1 | 1,992.5 | 5 | Default | DFT-s OFDM | PI/2 BPSK | Outer_Full | N/A | N/A | +| 2 | 1,992.5 | 5 | Default | | QPSK | Outer_Full | N/A | N/A | +| 3 | 1,992.5 | 5 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 4 | 1,992.5 | 5 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 5 | 1,992.5 | 5 | Default | | 256 QAM | Outer_Full | N/A | N/A | + +| | | | | | | | | | +|-------|---------|----|---------|-----------------------|-----------|----------------|----------------|---------------| +| 6 | 1,997.5 | 5 | Default | N/A for A-MPR testing | PI/2 BPSK | Outer_Full | N/A | N/A | +| 7 | 1,997.5 | 5 | Default | | QPSK | Outer_Full | N/A | N/A | +| 8 | 1,997.5 | 5 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 9 | 1,997.5 | 5 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 10 | 1,997.5 | 5 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 11-13 | 2,002.5 | 5 | Default | | PI/2 BPSK | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 14-16 | 2,002.5 | 5 | Default | | QPSK | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 17-19 | 2,002.5 | 5 | Default | | 16 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 20-22 | 2,002.5 | 5 | Default | | 64 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 23-25 | 2,002.5 | 5 | Default | | 256 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 26 | 1,985 | 10 | Default | | PI/2 BPSK | Edge_1RB_Right | N/A | N/A | +| 27 | 1,985 | 10 | Default | | QPSK | Edge_1RB_Right | N/A | N/A | +| 28 | 1,985 | 10 | Default | | 16 QAM | Edge_1RB_Right | N/A | N/A | +| 29 | 1,985 | 10 | Default | | 64 QAM | Edge_1RB_Right | N/A | N/A | +| 30 | 1,985 | 10 | Default | | 256 QAM | Edge_1RB_Right | N/A | N/A | +| 31 | 1,985 | 10 | Default | | PI/2 BPSK | Outer_Full | N/A | N/A | +| 32 | 1,985 | 10 | Default | | QPSK | Outer_Full | N/A | N/A | +| 33 | 1,985 | 10 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 34 | 1,985 | 10 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 35 | 1,985 | 10 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 36-38 | 1,995 | 10 | Default | | PI/2 BPSK | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 39-41 | 1,995 | 10 | Default | | QPSK | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 42-44 | 1,995 | 10 | Default | | 16 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 45-47 | 1,995 | 10 | Default | | 64 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 48-50 | 1,995 | 10 | Default | | 256 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 51-53 | 2,000 | 10 | Default | | PI/2 BPSK | Edge_1RB_Right | Edge_1RB_Left | 36@0 | +| 54-56 | 2,000 | 10 | Default | | QPSK | Edge_1RB_Right | Edge_1RB_Left | 36@0 | +| 57-59 | 2,000 | 10 | Default | | 16 QAM | Edge_1RB_Right | Edge_1RB_Left | 36@0 | +| 60-62 | 2,000 | 10 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 36@0 | +| 63-65 | 2,000 | 10 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 36@0 | + +| | | | | | | | | | +|---------|---------|----|---------|--|-----------|----------------|----------------|---------------| +| 66 | 2,000 | 10 | Default | | PI/2 BPSK | Outer_Full | N/A | N/A | +| 67 | 2,000 | 10 | Default | | QPSK | Outer_Full | N/A | N/A | +| 68 | 2,000 | 10 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 69 | 2,000 | 10 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 70 | 2,000 | 10 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 71-73 | 1,987.5 | 15 | Default | | PI/2 BPSK | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 74-76 | 1,987.5 | 15 | Default | | QPSK | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 77-79 | 1,987.5 | 15 | Default | | 16 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 80-82 | 1,987.5 | 15 | Default | | 64 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 83-85 | 1,987.5 | 15 | Default | | 256 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 86-88 | 1,997.5 | 15 | Default | | PI/2 BPSK | Edge_1RB_Right | Edge_1RB_Left | 50@0 | +| 89-91 | 1,997.5 | 15 | Default | | QPSK | Edge_1RB_Right | Edge_1RB_Left | 50@0 | +| 92-94 | 1,997.5 | 15 | Default | | 16 QAM | Edge_1RB_Right | Edge_1RB_Left | 50@0 | +| 95-97 | 1,997.5 | 15 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 50@0 | +| 98-100 | 1,997.5 | 15 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 50@0 | +| 101 | 1,997.5 | 15 | Default | | PI/2 BPSK | Outer_Full | N/A | N/A | +| 102 | 1,997.5 | 15 | Default | | QPSK | Outer_Full | N/A | N/A | +| 103 | 1,997.5 | 15 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 104 | 1,997.5 | 15 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 105 | 1,997.5 | 15 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 106-108 | 1,990 | 20 | Default | | PI/2 BPSK | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 109-111 | 1,990 | 20 | Default | | QPSK | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 112-114 | 1,990 | 20 | Default | | 16 QAM | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 115-117 | 1,990 | 20 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 118-120 | 1,990 | 20 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 121 | 1,990 | 20 | Default | | PI/2 BPSK | Outer_Full | N/A | N/A | +| 122 | 1,990 | 20 | Default | | QPSK | Outer_Full | N/A | N/A | +| 123 | 1,990 | 20 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 124 | 1,990 | 20 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 125 | 1,990 | 20 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 126-128 | 1,995 | 20 | Default | | PI/2 BPSK | Edge_1RB_Right | Edge_1RB_Left | 69@0 | +| 129-131 | 1,995 | 20 | Default | | QPSK | Edge_1RB_Right | Edge_1RB_Left | 69@0 | +| 132-134 | 1,995 | 20 | Default | | 16 QAM | Edge_1RB_Right | Edge_1RB_Left | 69@0 | +| 135-137 | 1,995 | 20 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 69@0 | +| 138-140 | 1,995 | 20 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 69@0 | +| 141 | 1,995 | 20 | Default | | PI/2 BPSK | Outer_Full | N/A | N/A | +| 142 | 1,995 | 20 | Default | | QPSK | Outer_Full | N/A | N/A | +| 143 | 1,995 | 20 | Default | | 16 QAM | Outer_Full | N/A | N/A | +| 144 | 1,995 | 20 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 145 | 1,995 | 20 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 146-147 | 1,992.5 | 5 | Default | | QPSK | Outer_Full | N/A | N/A | +| | | | | | 16 QAM | Outer_Full | N/A | N/A | + +| | | | | | | | | | +|---------|---------|----|---------|--------------------------|----------------|----------------|----------------|---------------| +| 148 | 1,992.5 | 5 | Default | 64 QAM | Outer_Full | N/A | N/A | | +| 149 | 1,992.5 | 5 | Default | 256 QAM | Outer_Full | N/A | N/A | | +| 150-151 | 1,997.5 | 5 | Default | QPSK
16 QAM | Outer_Full | N/A | N/A | | +| 152 | 1,997.5 | 5 | Default | 64 QAM | Outer_Full | N/A | N/A | | +| 153 | 1,997.5 | 5 | Default | 256 QAM | Outer_Full | N/A | N/A | | +| 154-159 | 2,002.5 | 5 | Default | N/A for A-MPR
testing | QPSK
16 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 160-162 | 2,002.5 | 5 | Default | | 64 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 163-165 | 2,002.5 | 5 | Default | | 256 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 166-167 | 1,985 | 10 | Default | | QPSK
16 QAM | Edge_1RB_Right | N/A | N/A | +| 168 | 1,985 | 10 | Default | | 64 QAM | Edge_1RB_Right | N/A | N/A | +| 169 | 1,985 | 10 | Default | | 256 QAM | Edge_1RB_Right | N/A | N/A | +| 170-171 | 1,985 | 10 | Default | | QPSK
16 QAM | Outer_Full | N/A | N/A | +| 172 | 1,985 | 10 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 173 | 1,985 | 10 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 174-179 | 1,995 | 10 | Default | | QPSK
16 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 180-182 | 1,995 | 10 | Default | | 64 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 183-185 | 1,995 | 10 | Default | | 256 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 186-191 | 2,000 | 10 | Default | | QPSK
16 QAM | Edge_1RB_Right | Edge_1RB_Left | 37@0 | +| 192-194 | 2,000 | 10 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 37@0 | +| 195-197 | 2,000 | 10 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 37@0 | +| 198-199 | 2,000 | 10 | Default | | QPSK
16 QAM | Outer_Full | N/A | N/A | +| 200 | 2,000 | 10 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 201 | 2,000 | 10 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 202-207 | 1,987.5 | 15 | Default | | QPSK
16 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 208-210 | 1,987.5 | 15 | Default | | 64 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 211-213 | 1,987.5 | 15 | Default | | 256 QAM | Outer_Full | Edge_1RB_Right | Edge_1RB_Left | +| 214-219 | 1,997.5 | 15 | Default | | QPSK
16 QAM | Edge_1RB_Right | Edge_1RB_Left | 51@0 | +| 220-222 | 1,997.5 | 15 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 51@0 | +| 223-225 | 1,997.5 | 15 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 51@0 | +| 226-227 | 1,997.5 | 15 | Default | | QPSK
16 QAM | Outer_Full | N/A | N/A | +| 228 | 1,997.5 | 15 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 229 | 1,997.5 | 15 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 230-235 | 1,990 | 20 | Default | | QPSK
16 QAM | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 236-238 | 1,990 | 20 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 239-241 | 1,990 | 20 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 74@0 | +| 242-243 | 1,990 | 20 | Default | | QPSK
16 QAM | Outer_Full | N/A | N/A | +| 244 | 1,990 | 20 | Default | | 64 QAM | Outer_Full | N/A | N/A | +| 245 | 1,990 | 20 | Default | | 256 QAM | Outer_Full | N/A | N/A | +| 246-251 | 1,995 | 20 | Default | | QPSK
16 QAM | Edge_1RB_Right | Edge_1RB_Left | 69@0 | +| 252-254 | 1,995 | 20 | Default | | 64 QAM | Edge_1RB_Right | Edge_1RB_Left | 69@0 | + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------|---------|----|---------|--|----------------|----------------|---------------|------|--|--|--|--| +| 255-257 | 1,995 | 20 | Default | | 256 QAM | Edge_1RB_Right | Edge_1RB_Left | 69@0 | | | | | +| 258-259 | 1,995 | 20 | Default | | QPSK
16 QAM | Outer_Full | N/A | N/A | | | | | +| 260 | 1,995 | 20 | Default | | 64 QAM | Outer_Full | N/A | N/A | | | | | +| 261 | 1,995 | 20 | Default | | 256 QAM | Outer_Full | N/A | N/A | | | | | +| 262 | 1,992.5 | 5 | Default | | QPSK | Edge_1RB_Right | N/A | N/A | | | | | +| 263 | 1,997.5 | 5 | Default | | 16 QAM | Edge_1RB_Right | N/A | N/A | | | | | +| 264 | 1,985 | 10 | Default | | QPSK | Edge_1RB_Left | N/A | N/A | | | | | +| NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 unless otherwise stated in this table. | | | | | | | | | | | | | +| NOTE 2: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports half Pi BPSK in FR1. | | | | | | | | | | | | | +| NOTE 3: In test IDs with multiple modulations, each UL Modulation shall be tested separately against Range A, B, and C. | | | | | | | | | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to Annex C.0, C.1, C.2 and uplink signals according to Annex G.0, G.1, G.2 and G.3.0. +4. The UL Reference Measurement channels are set according to the applicable table from Table 6.2.3.4.1-1 to Table 6.2.3.4.1-2. +5. Propagation conditions are set according to Annex B.0. +6. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.3.4.3. + +#### 6.2.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to the applicable table from Table 6.2.3.4.1-1 to Table 6.2.3.4.1-2. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE Allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode. The period of measurement shall be at least the continuous duration one sub-frame (1 ms). + +NOTE: When switching to DFT-s-OFDM waveform, as specified in the test configuration Table 6.2.3.4.1-1 to Table 6.2.3.4.1-2, send an NR RRCReconfiguration message according to TS 38.508-1 [12] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +#### 6.2.3.4.3 Message contents + +##### 6.2.3.4.3.1 Message contents exceptions for network signalling value "NS\_100" + +1. Information element additionalSpectrumEmission is set to NS\_100. This can be set in the *SIB1* as part of the cell broadcast message. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.2.3.4.3.1-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement for "NS\_100"** + +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-1 | | | | +|--------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| additionalSpectrumEmission | 2 (NS_100) | | | + +#### 6.2.3.4.3.2 Message contents exceptions for network signalling value "NS\_24" + +- Information element additionalSpectrumEmission is set to NS\_24. This can be set in the *SIB1* as part of the cell broadcast message. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.2.3.4.3.2-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement for "NS\_24"** + +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-1 | | | | +|--------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| additionalSpectrumEmission | 1 (NS_24) | | | + +#### 6.2.3.5 Test requirement + +The maximum output power, derived in step 3 shall be within the range prescribed by the nominal maximum output power and tolerance in the applicable Table from table 6.2.3.5-1 to Table 6.2.3.5-2. The allowed A-MPR values specified in Table 6.2.3.3.1-1 are in addition to the allowed MPR requirements specified in clause 6.2.2. For the UE maximum output power modified by MPR and/or A-MPR, the power limits specified in Table 6.2.1.3-1 apply. + +**Table 6.2.3.5-1: Test Tolerance (UE additional maximum output power reduction)** + +[to be updated] + +**Table 6.2.3.5-2: UE Power Class 3 test requirements (NS\_100) for n256** + +| Test ID | P PowerClass (dBm) | MPR (dB) | A-MPR (dB) | ΔT C,c (dB) | P CMAX_L,c (dBm) | T(P CMAX_L,c ) (dB) | T L,c (dB) | Upper limit (dBm) | Lower limit (dBm) | +|---------|-------------------------------|----------|------------|------------------------|-----------------------------|--------------------------------|-----------------------|-------------------|-------------------| +| 1, 2 | 23 | 0.5 | 2 | 0 | 21 | 2 | 2 | 25+TT | 19-TT | +| 3 | 23 | 0.5 | 2 | 0 | 21 | 2 | 2 | 25+TT | 19-TT | +| 4, 5 | 23 | 1 | 2 | 0 | 21 | 2 | 2 | 25+TT | 19-TT | +| 6 | 23 | 1 | 2 | 0 | 21 | 2 | 2 | 25+TT | 19-TT | +| 7, 8 | 23 | 2 | 2.5 | 0 | 20.5 | 2.5 | 2 | 25+TT | 18-TT | +| 9 | 23 | 2 | 2.5 | 0 | 20.5 | 2.5 | 2 | 25+TT | 18-TT | +| 10, 11 | 23 | 2.5 | 3 | 0 | 20 | 2.5 | 2 | 25+TT | 17.5-TT | +| 12 | 23 | 2.5 | 3 | 0 | 20 | 2.5 | 2 | 25+TT | 17.5-TT | +| 13, 14 | 23 | 4.5 | 4.5 | 0 | 18.5 | 4 | 2 | 25+TT | 14.5-TT | +| 15 | 23 | 4.5 | 4.5 | 0 | 18.5 | 4 | 2 | 25+TT | 14.5-TT | +| 16, 17 | 23 | 3 | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 18 | 23 | 3 | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 19, 20 | 23 | 3 | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 21 | 23 | 3 | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 22, 23 | 23 | 3.5 | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 24 | 23 | 3.5 | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 25, 26 | 23 | 6.5 | 6.5 | 0 | 16.5 | 5 | 2 | 25+TT | 11.5-TT | +| 27 | 23 | 6.5 | 6.5 | 0 | 16.5 | 5 | 2 | 25+TT | 11.5-TT | + +NOTE 1: PPowerClass is the maximum UE power specified without taking into account the tolerance. + +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2.3.5-0. + +Table 6.2.3.5-3: UE Power Class 3 test requirements (NS\_24) for n256 + +| Test ID | P PowerClass (dBm) | MPR (dB) | A-MPR (dB) | ΔT C,c (dB) | P CMAX_L,c (dBm) | T(P CMAX_L,c ) (dB) | T L,c (dB) | Upper limit (dBm) | Lower limit (dBm) | +|----------------------------------------------------------------------------------------|-------------------------------|----------|------------|------------------------|-----------------------------|--------------------------------|-----------------------|-------------------|-------------------| +| 1, 6, 11-13, 26, 31, 36-38, 51-53, 66, 71-73, 86-88, 101, 106-108, 121, 126-128, 141 | 23 | N/A | 1.5 | 0 | 21.5 | 2 | 2 | 25+TT | 19.5-TT | +| 2, 7, 14-16, 27, 32, 39-41, 54-56, 67, 74-76, 89-91, 102, 109-111, 122, 129-131, 142 | 23 | N/A | 2.0 | 0 | 21 | 2 | 2 | 25+TT | 19-TT | +| 3, 8, 17-19, 28, 33, 42-44, 57-59, 68, 77-79, 92-94, 103, 112-114, 123, 132-134, 143 | 23 | N/A | 3.0 | 0 | 20 | 2.5 | 2 | 25+TT | 17.5-TT | +| 4, 9, 20-22, 29, 34, 45-47, 60-62, 69, 80-82, 95-97, 104, 115-117, 124, 135-137, 144 | 23 | N/A | 3.5 | 0 | 19.5 | 3.5 | 2 | 25+TT | 16-TT | +| 5, 10, 23-25, 30, 35, 48-50, 63-65, 70, 83-85, 98-100, 105, 118-120, 125, 138-140, 145 | 23 | N/A | 5.5 | 0 | 17.5 | 5 | 2 | 25+TT | 12.5-TT | + +| Test ID | P PowerClass (dBm) | MPR (dB) | A-MPR (dB) | ΔT C,c (dB) | P CMAX_L,c (dBm) | T(P CMAX_L,c ) (dB) | T L,c (dB) | Upper limit (dBm) | Lower limit (dBm) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|----------|------------|------------------------|-----------------------------|--------------------------------|-----------------------|-------------------|-------------------| +| 146-147,
150-151,
154-159,
166-167,
170-171,
174-179,
186-191,
198-199,
202-207,
214-219,
226-227,
230-235,
242-243,
246-251,
258-259,
262-264 | 23 | N/A | 4 | 0 | 19 | 3.5 | 2 | 25+TT | 15.5-TT | +| 148, 152,
160-162,
168, 172,
180-182,
192-194,
200, 208-
210, 220-
222, 228,
236-238,
244, 252-
254, 260 | 23 | N/A | 4.5 | 0 | 18.5 | 4 | 2 | 25+TT | 14.5-TT | +| 149, 153,
163-165,
169, 173,
183-185,
195-197,
201, 211-
213, 223-
225, 229,
239-241,
245, 255-
257, 261 | 23 | N/A | 7.5 | 0 | 15.5 | 5 | 2 | 25+TT | 10.5-TT | + +NOTE 1: PPowerClass is the maximum UE power specified without taking into account the tolerance. +NOTE 2: TT for each frequency and channel bandwidth is specified in Table 6.2.3.5-1. + +## 6.2.4 Configured transmitted power + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +### 6.2.4.1 Test purpose + +To verify the measured UE configured maximum output power PUMAX,fc is within the specified bounds. + +### 6.2.4.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 6.2.4.3 Minimum conformance requirements + +The requirements for configured transmitted power defined in subclause 6.2.4 of 3GPP TS 38.521-1 [2] clause 6.2.4 shall apply to NTN satellite UE. + +The normative reference for this requirement is TS 38.101-1 [5] clause 6.2.4. + +### 6.2.4.4 Test description + +#### 6.2.4.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.2.4.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in clause A.2. Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 6.2.4.4.1-1: Test Configuration Table** + +| | | Initial Conditions | | +|--------------------------------------------------------------------------|-------------------------------|------------------------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | | Mid range | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | | Lowest, Mid, Highest | | +| Test SCS as specified in Table 5.3.5-1 | | Lowest | | +| Test Parameters for Channel Bandwidths | | | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | N/A | Modulation (NOTE 2) | RB allocation (NOTE 1) | +| 1 | | DFT-s-OFDM Pi/2 BPSK | Inner Full | +| 2 | | DFT-s-OFDM QPSK | Inner Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1. +NOTE 2: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports half Pi BPSK. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to Annex C.0, C.1, C.2, and uplink signals according to Annex G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.4.4.1-1. +5. Propagation conditions are set according to Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.4.4.3. + +#### 6.2.4.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.2.4.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in every uplink scheduling information to the UE; allow at least 200 ms starting from the first TPC command in this step to ensure that the UE reaches the Pmax level of the test point. +3. Measure the mean power of the UE in the channel bandwidth for each test point in table 6.2.4.5-1 according to the test configuration from table 6.2.4.4.1-1. The period of measurement shall be at least the continuous duration of one active slot and in the uplink symbols. For TDD slots with transient periods are not under test. + +#### 6.2.4.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 with the following exceptions: + +**Table 6.2.4.4.3-0: *PUSCH-Config*** + +| | +|-----------------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|-----------------------------------------------------------------------------------------------------| + +**Table 6.2.4.4.3-1: FrequencyInfoUL-SIB: Test point 1** + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-62 FrequencyInfoUL-SIB | | | | +|----------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-Max | -10 | | | + +**Table 6.2.4.4.3-2: FrequencyInfoUL-SIB: Test point 2** + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-62 FrequencyInfoUL-SIB | | | | +|----------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-Max | 10 | | | + +**Table 6.2.4.4.3-3: FrequencyInfoUL-SIB: Test point 3** + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-62 FrequencyInfoUL-SIB | | | | +|----------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-Max | 15 | | | + +**Table 6.2.4.4.3-4: FrequencyInfoUL-SIB: Test point 4** + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-62 FrequencyInfoUL-SIB | | | | +|----------------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| p-Max | 20 | | | + +Table 6.2.4.4.3-5: ServingCellConfig + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-167 | | | | +|---------------------------------------------------|--------------|---------|--------------| +| Information Element | Value/remark | Comment | Condition | +| ServingCellConfig ::= SEQUENCE { | | | | +| uplinkConfig SEQUENCE { | | | | +| powerBoostPi2BPSK | 0 | | Test ID 1, 2 | +| } | | | | +| } | | | | + +## 6.2.4.5 Test requirement + +The maximum output power measured shall not exceed the values specified in Table 6.2.4.5-1. + +Table 6.2.4.5-1: PCMAX configured UE output power for Test ID 1,2 + +| | Maximum output power | +|---------------------------------------|----------------------| +| Measured UE output power test point 1 | -10 dBm $\pm$ (7+TT) | +| Measured UE output power test point 2 | 10 dBm $\pm$ (6+TT) | +| Measured UE output power test point 3 | 15 dBm $\pm$ (5+TT) | +| Measured UE output power test point 4 | Note 3 | + +NOTE 1: TT for each frequency and channel bandwidth is specified in Table 6.2.4.5-2. +NOTE 2: Power class 3 is default power class unless otherwise stated. +NOTE 3: The maximum output power shall be within the range in Table 6.2.4.5-1a. + +Table 6.2.4.5-1a: Measured UE output power test point 4 for Test ID 1,2 + +| NR band | Tolerance (dB) | +|--------------------------------------------------------------------------------------|-----------------------| +| n256 | 20 dBm $\pm$ (2.5+TT) | +| n255 | 20 dBm $\pm$ (2.5+TT) | +| NOTE 1: TT for each frequency and channel bandwidth is specified in Table 6.2.4.5-2. | | + +Table 6.2.4.5-2: Test Tolerance (Configured transmitted power) + +[to be updated] + +## 6.3 Output power dynamics + +### 6.3.1 Minimum output power + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated + +#### 6.3.1.1 Test purpose + +To verify the UE's ability to transmit with a broadband output power below the value specified in the test requirement when the power is set to a minimum value. + +### 6.3.1.2 Test applicability + +This test case applies to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 6.3.1.3 Minimum conformance requirements + +The minimum controlled output power of the UE is defined as the power in the channel bandwidth for all transmit bandwidth configurations (resource blocks), when the power is set to a minimum value. + +The minimum output power is defined as the mean power in at least one sub-frame 1 ms. The minimum output power shall not exceed the values specified in Table 6.3.1.3-1. + +**Table 6.3.1.3-1: Minimum output power** + +| Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|-------------------------|----------------------------|-----------------------------| +| 5 | -40 | 4.515 | +| 10 | -40 | 9.375 | +| 15 | -40 | 14.235 | +| 20 | -40 | 19.095 | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.3.1. + +### 6.3.1.4 Test description + +#### 6.3.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in table 6.3.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 6.3.1.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | +|--------------------------------------------------------------------------|----------------------------------------|----------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Low range, Mid range, High range | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Lowest, Mid, Highest | | | +| Test SCS as specified in Table 5.3.5-1 | Highest | | | +| Test Parameters for Channel Bandwidths | | | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | N/A for minimum output power test case | Modulation | RB allocation (NOTE 1) | +| 1 | | DFT-s-OFDM QPSK | Outer Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to clauses C.0, C.1, C.2, and uplink signals according to clauses G.0, G.1, G.2, G.3.0. + +4. The UL Reference Measurement Channel is set according to Table 6.3.1.4.1-1. +5. Propagation conditions are set according to Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.3.1.4.3. + +#### 6.3.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.3.1.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "down" commands in every uplink scheduling information to the UE; allow at least 200 ms starting from the first TPC command in this step to ensure that the UE transmits at its minimum output power. +3. Measure the mean power of the UE in the associated measurement channel bandwidth specified in Table 6.3.1.5-1 for the specific channel bandwidth under test. The period of measurement shall be at least the continuous duration of one active sub-frame (1 ms) and in the uplink symbols. For TDD symbols with transient periods are not under test. + +#### 6.3.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 with following exception. + +**Table 6.3.1.4.3-1: PUSCH-Config** + +| | +|----------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|----------------------------------------------------------------------------------------------| + +#### 6.3.1.5 Test requirement + +The minimum output power, derived in step 3 shall not exceed the values specified in Table 6.3.1.5-1. + +**Table 6.3.1.5-1: Minimum output power** + +| Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|-------------------------------------------------------------------------------------|----------------------------|-----------------------------| +| 5 | -40+TT | 4.515 | +| 10 | -40+TT | 9.375 | +| 15 | -40+TT | 14.235 | +| 20 | -40+TT | 19.095 | +| NOTE 1: TT for each frequency and channel bandwidth is specified in Table 6.3.1.5-2 | | | + +**Table 6.3.1.5-2: Test Tolerance (Minimum output power)** + +| | $f \leq 3.0\text{GHz}$ | +|------------------------|------------------------| +| BW $\leq 40\text{MHz}$ | 1 dB | + +#### 6.3.2 Transmit OFF power + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending + +### 6.3.2.1 Test purpose + +To verify that the UE transmit OFF power is lower than the value specified in the test requirement. + +An excess Transmit OFF power potentially increases the Rise Over Thermal (RoT) and therefore reduces the cell coverage area for other UEs. + +### 6.3.2.2 Test applicability + +This test case applies to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 6.3.2.3 Minimum conformance requirements + +Transmit OFF power is defined as the mean power in the channel bandwidth when the transmitter is OFF. The transmitter is considered OFF when the UE is not allowed to transmit on any of its ports. + +The Transmit OFF power is defined as the mean power in a duration of at least one sub-frame (1 ms) excluding any transient periods. The Transmit OFF power shall not exceed the values specified in Table 6.3.2.3-1. + +**Table 6.3.2.3-1: Transmit OFF power** + +| | | | +|------------------------------|-------|-----------------------------------| +| Channel bandwidth | (MHz) | 5, 10, 15, 20 | +| REF_SCS | (kHz) | 15 | +| Transmit OFF power | (dBm) | -50 | +| Measurement bandwidth | (MHz) | $MBW=REF\_SCS*(12*N_{RB}+1)/1000$ | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.3.2. + +### 6.3.2.4 Test description + +This test is covered by clause 6.3.3 Transmit ON/OFF time mask. + +### 6.3.2.5 Test requirement + +The minimum output power, derived in step 3 shall not exceed the values specified in Table 6.3.2.5-1. + +**Table 6.3.1.5-1: Minimum output power** + +| Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|--------------------------------|-----------------------------------|------------------------------------| +| 5 | -50+TT | 4.515 | +| 10 | -50+TT | 9.375 | +| 15 | -50+TT | 14.235 | +| 20 | -50+TT | 19.095 | + +NOTE 1: TT for each frequency and channel bandwidth is specified in Table 6.3.2.5-2 + +**Table 6.3.1.5-2: Test Tolerance (Transmit OFF power)** + +| | | +|------------|-------------------| +| | f ≤ 3.0GHz | +| BW ≤ 40MHz | 1.5 dB | + +### 6.3.3 Transmit on/off time mask + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access is to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +### 6.3.3.1 Test purpose + +To verify that the general ON/OFF time mask meets the requirements given in 6.3.3.2.5. + +The transmit power time mask for transmit ON/OFF defines the transient period(s) allowed between transmit OFF power as defined in sub-clause 6.3.2 and transmit ON power symbols (transmit ON/OFF) + +Transmission of the wrong power increases interference to other channels or increases transmission errors in the uplink channel. + +### 6.3.3.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 6.3.3.3 Minimum conformance requirements + +The requirements for transmit ON/OFF time mask defined in 3GPP TS 38.101-1 [5] clause 6.3.3 shall apply for NTN satellite UE. + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.2.2. + +### 6.3.3.4 Test description + +#### 6.3.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Table 6.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +**Table 6.2.2.4.1-1: Test Configuration Table for power class 3** + +| | | Initial Conditions | | +|--------------------------------------------------------------------------|----------------------------------------|-------------------------------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | | Low range, Mid range, High range (NOTE 2) | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | | Lowest, Mid, Highest | | +| Test SCS as specified in Table 5.3.5-1 | | Lowest, Highest | | +| Test Parameters for Channel Bandwidths | | | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | N/A for minimum output power test case | Modulation | RB allocation (NOTE 1) | +| 1 | | DFT-s-OFDM QPSK | Inner Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1. +NOTE 2: For NR band n28, 30MHz test channel bandwidth is tested with Low range and High range test frequencies. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.2.4.1-1. +5. Propagation conditions are set according to TS 38.521-1 [2] Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State [to be updated] with generic procedure parameters [12], Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.2.4.3. + +#### 6.3.3.4.2 Test procedure + +1. SS sends uplink scheduling information via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.3.3.2.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. The UL assignment is such that the UE transmits on slots 8 for 15 kHz SCS, on slots 8 and 18 for 30 kHz SCS and on slots 17 and 37 for 60 kHz SCS. +2. Send continuously uplink power control "up" commands in every uplink scheduling information to the UE; allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +3. ON power sub test: + - 3.1. Measure the output power of the UE PUSCH transmission during one slot. +4. OFF power sub test: + - 4.1. Measure the UE transmission OFF power during the slot prior to the PUSCH transmission, excluding a transient period of 10 $\mu\text{s}$ in the end of the slot. + - 4.2. Measure the UE transmission OFF power during the slot following the PUSCH transmission, excluding a transient period of 10 $\mu\text{s}$ at the beginning of the slot. + +## 6.3.3.4.3 Message contents + +Message contents are according to TS 38.508-1 [5] subclauses 4.6 and 5.4 with the following exceptions: + +**Table 6.3.3.4.3-1: PUSCH-TimeDomainResourceAllocationList** + +| Derivation Path: TS 38.508-1 [5], Table 4.6.3-122 | | | | +|-------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Information Element | Value/remark | Comment | Condition | +| PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF { | 2 entries | | | +| PUSCH-TimeDomainResourceAllocation[1] SEQUENCE { | | | | +| k2 | 4 | | FR1_15kHz,
FR1_30kHz | +| | 6 | | FR1_60kHz | +| mappingType | typeA | | | +| startSymbolAndLength | 27 | Start symbol(S)=0,
Length(L)=14 | | +| } | | | | +| PUSCH-TimeDomainResourceAllocation[2] SEQUENCE { | | addressed by
Msg3 PUSCH time
resource allocation
field of the Random
Access Response
acc. to TS 38.213
[7] Table 8.2-1. | | +| k2 | 2 | K 2 + Δ=4 acc. to TS
38.214 [21] Table
6.1.2.1.1-5
(NOTE 1) | FR1_15kHz | +| | 6 | K 2 + Δ=9 acc. to TS
38.214 [21] Table
6.1.2.1.1-5
(NOTE 1) | FR1_30kHz | +| mappingType | typeA | | | +| startSymbolAndLength | 27 | Start symbol(S)=0,
Length(L)=14 | | +| } | | | | +| } | | | | + +NOTE 1: Values are chosen so that first slot of a TDD-UL-DL slot configuration period can be used for the Random Access Response and the last slot (of the same or another period) for the corresponding Msg3. + +| Condition | Explanation | +|-----------|--------------------------------------------------| +| FR1_15kHz | FR1 is used under the test. SCS is set to 15kHz. | +| FR1_30kHz | FR1 is used under the test. SCS is set to 30kHz. | +| FR1_60kHz | FR1 is used under the test. SCS is set to 60kHz. | + +**Table 6.3.3.4.3-2: PUSCH-Config** + +| | +|----------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|----------------------------------------------------------------------------------------------| + +**Table 6.3.3.2.4.3-7: P-Max** + +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-89 | | | | +|---------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| P-Max | 23 | | | + +## 6.3.3.5 Test requirement + +The requirement for the power measured in steps 2, 3 and 4 of the test procedure shall not exceed the values specified in Table 6.3.3.5-1. + +Table 6.3.3.5-1: General ON/OFF time mask + +| | Channel bandwidth / minimum output power / measurement bandwidth | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------|----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|----------|----------|----------|----------|----------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| +| | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 35 MHz | 40 MHz | 45 MHz | 50 MHz | 60 MHz | 70 MHz | 80 MHz | 90 MHz | 100 MHz | | | | | | | | | | | | | | | | +| Transmit OFF power | $\leq -50+TT$ dBm | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Transmission OFF Measurement bandwidth | [4.51 5] | [9.37 5] | [14.23 5] | [19.09 5] | [23.95 5] | [28.81 5] | [33.85 5] | [38.89 5] | [43.57 5] | [48.61 5] | [58.3 5] | [68.0 7] | [78.1 5] | [88.2 3] | [98.3 1] | | | | | | | | | | | | | | | | +| Transmit ON power | Same as Table 6.2.1.5-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE 1: TT for each frequency and channel bandwidth of OFF power is specified in Table 6.3.3.2.5-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| NOTE 2: TT for each frequency and channel bandwidth of ON power is specified in Table 6.2.1.5-3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Table 6.3.3.2.5-2: Test Tolerance for OFF power + +| | | +|---------------------------------------------------------------------------------------------------|------------------------| +| The test tolerance for frequency range and channel bandwidth applicable to NTN is provided below. | $f \leq 3.0\text{GHz}$ | +| $BW \leq 40\text{MHz}$ | [to be updated] | + +## 6.4 Transmit signal quality + +### 6.4.1 Frequency error + +**Editor's Note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- Verification of UE frequency pre-compensation is to be updated + +#### 6.4.1.1 Test purpose + +This test verifies the ability of both, the receiver and the transmitter, to process frequency correctly. + +Receiver: to extract the correct frequency from the stimulus signal, offered by the System simulator, under ideal propagation conditions and low level. + +Transmitter: to derive the correct modulated carrier frequency from the results, gained by the receiver. + +#### 6.4.1.2 Test applicability + +This test case applies to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +#### 6.4.1.3 Minimum conformance requirements + +The NTN satellite UE basic measurement interval of modulated carrier frequency is 1 UL slot. The NTN satellite UE pre-compensates the uplink modulated carrier frequency by the estimated Doppler shift according to 3GPP TS 38.300 [9] clause 16.14.2. The mean value of basic measurements of NTN UE modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 ms of cumulated measurement intervals compared to ideally pre-compensated reference uplink carrier frequency. + +[NOTE: The ideally pre-compensated reference uplink carrier frequency consists of the UL carrier frequency signalled to the UE by SAN and UL pre-compensated Doppler frequency shift. For the test case, the location of the UE is explicitly provided to the UE from the test equipment.] + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.4.1. + +#### 6.4.1.4 Test description + +##### 6.4.1.4.1 Initial condition + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in table 6.4.1.4.1-1. The details of the uplink and downlink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annex A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 Annex C.2. + +**Table 6.4.1.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | | +|--------------------------------------------------------------------------|------------------------------------|----------------------|-----------------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Mid range | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Highest | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | | +| Test Parameters | | | | | +| | Downlink Configuration | | Uplink Configuration | | +| Test ID | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM QPSK | Full RB (NOTE 1) | DFT-s-OFDM QPSK | REFSENS (NOTE 2) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2 +NOTE 2: REFSENS refers to Table 7.3.2.4.1-3 which defines uplink RB configuration and start RB location for each SCS, channel BW and NR band. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, in Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to clauses C.0, C.1, C.2, and uplink signals according to clauses G.0, G.1, G.2, G.3.0. +4. The DL and UL Reference Measurement channels are set according to Table 6.4.1.4.1-1. +5. Propagation conditions are set according to Annex B.0. + +##### 6.4.1.4.2 Test procedure + +1. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +2. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508 [12] table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +3. Deactivate UE prediction of satellite trajectory by any preconfigured means +4. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity NR, Connected without release On, Test Mode On and Test Loop Function On according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.4.1.4.3. +5. SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 6.4.1.4.1-1. The SS sends downlink MAC padding bits on the DL RMC. + +6. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.4.1.4.1-1. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +7. Set the Downlink signal level to the appropriate REFSENS value defined in Table 7.3.2.5-1. Send continuously uplink power control "up" commands to the UE in every uplink scheduling information to the UE so that the UE transmits at $P_{\text{UMAX}}$ level for the duration of the test. Allow at least 200 ms starting from the first TPC command in this step for the UE to reach $P_{\text{UMAX}}$ level. +8. Measure the Frequency Error using Global In-Channel Tx-Test (Annex E). For TDD, only slots consisting of only UL symbols are under test. +9. For UEs supporting DSS, repeat steps 1~4 on the applicable bands as specified in Clause 5.4.2.1 with message contents being according to TS 38.508-1 [12] subclause 4.6 ensuring Table 4.6.3-61 and Table 4.6.3-62 with condition DSS. +- 10 Repeat from test procedure steps 1-9 with ephemeris values for maximum positive Doppler for GSO if UE supports only GSO or both GSO and NGSO satellites and for NGSO (LEO-600) if UE supports only NGSO satellites replacing ephemeris in step 2 by corresponding tables in clause 6.4A.1.4.3. Test system shall send same SIB19 information during the duration of this frequency error measurement. +- 11 Repeat from test procedure steps 1-9 with ephemeris values for maximum negative Doppler for GSO if UE supports only GSO or both GSO and NGSO satellites and for NGSO (LEO-600) if UE supports only NGSO satellites replacing ephemeris in step 2 by corresponding tables in clause 6.4A.1.4.3. Test system shall send same SIB19 information during the duration of each frequency error measurement. +- 12 Repeat from test procedure steps 1-8 with ephemeris values for half of maximum positive Doppler if UE supports only GSO or both GSO and NGSO satellites and for NGSO (LEO-600) if UE supports only NGSO satellites replacing ephemeris in step 2 by corresponding tables in clause 6.4A.1.4.3. Test system shall send same SIB19 information during the duration of this frequency error measurement. +- 13 In case the UE supports both GSO and NGSO satellites, repeat test procedure steps 10-13 for NGSO (LEO-600). + +#### 6.4.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 and subclause 5.6.2.1 with the following exceptions + +**Table 6.4.1.4.3-1a: EphemerisInfo- NR NTN Ephemeris Information for GSO satellites (maximum positive Doppler)** + +| Derivation Path: TS 38.598-1, Table 4.6.3-56C | | | | +|-----------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| EphemerisInfo-r17 ::= CHOICE { | | | | +| positionVelocity-r17 SEQUENCE { | | | | +| positionX-r17 | -17104941 | | | +| positionY-r17 | 27550229 | | | +| positionZ-r17 | -607219 | | | +| velocityVX-r17 | 258 | | | +| velocityVY-r17 | 299 | | | +| velocityVZ-r17 | 6277 | | | +| } | | | | +| } | | | | + +NOTE 1: Satellite-UE elevation angle equal to 26.15 degrees, one-way delay equal to 129.93 ms and Doppler equal to 0.17 ppm + +**Table 6.4.1.4.3-1b: EphemerisInfo- NR NTN Ephemeris Information for NGSO (LEO-600) satellites (maximum positive Doppler)** + +| Derivation Path: TS 38.598-1, Table 4.6.3-56C | | | | +|-----------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| EphemerisInfo-r17 ::= CHOICE { | | | | +| positionVelocity-r17 SEQUENCE { | | | | +| positionX-r17 | -2717617 | | | +| positionY-r17 | 4550419 | | | +| positionZ-r17 | 852799 | | | +| velocityVX-r17 | 6164 | | | +| velocityVY-r17 | -19424 | | | +| velocityVZ-r17 | 124281 | | | +| } | | | | +| } | | | | + +NOTE 1: Satellite-UE elevation angle equal to 10 degrees, one-way delay equal to 6.44 ms and Doppler equal to 22.65 ppm. + +**Table 6.4.1.4.3-2a: EphemerisInfo -NR NTN Ephemeris Information for GSO satellites (maximum negative Doppler)** + +| Derivation Path: TS 38.598-1, Table 4.6.3-56C | | | | +|-----------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| EphemerisInfo-r17 ::= CHOICE { | | | | +| positionVelocity-r17 SEQUENCE { | | | | +| positionX-r17 | -17061001 | | | +| positionY-r17 | 27582763 | | | +| positionZ-r17 | -276165 | | | +| velocityVX-r17 | 361 | | | +| velocityVY-r17 | 160 | | | +| velocityVZ-r17 | -6335 | | | +| } | | | | +| } | | | | + +NOTE 1: Satellite-UE elevation angle equal to 26.78 degrees, one-way delay equal to 129.74 ms and Doppler equal to -0.17 ppm. + +**Table 6.4.1.4.3-2b: EphemerisInfo -NR NTN NTN Ephemeris Information for NGSO (LEO-600) satellites (maximum negative Doppler)** + +| Derivation Path: TS 38.598-1, Table 4.6.3-56C | | | | +|-----------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| EphemerisInfo-r17 ::= CHOICE { | | | | +| positionVelocity-r17 SEQUENCE { | | | | +| positionX-r17 | -2199272 | | | +| positionY-r17 | 3404229 | | | +| positionZ-r17 | 3535794 | | | +| velocityVX-r17 | 35394 | | | +| velocityVY-r17 | -74414 | | | +| velocityVZ-r17 | 94682 | | | +| } | | | | +| } | | | | + +NOTE 1: Satellite-UE elevation angle equal to 169.97 degrees, one-way delay equal to 6.60 ms and Doppler equal to -22.62 ppm. + +**Table 6.4.1.4.3-3a: EphemerisInfo -NR NTN Ephemeris Information for GSO satellites (maximum positive Doppler/2)** + +| Derivation Path: TS 38.598-1, Table 4.6.3-56C | | | | +|-----------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| EphemerisInfo-r17 ::= CHOICE { | | | | +| positionVelocity-r17 SEQUENCE { | | | | +| positionX-r17 | -17062164 | | | +| positionY-r17 | 27354696 | | | +| positionZ-r17 | -3544856 | | | +| velocityVX-r17 | -360 | | | +| velocityVY-r17 | 164 | | | +| velocityVZ-r17 | 2993 | | | +| } | | | | +| } | | | | + +NOTE 1: Satellite-UE elevation angle equal to 20.61 degrees, one-way delay equal to 131.70 ms and Doppler equal to -0.085 ppm. + +**Table 6.4.1.4.3-3b: EphemerisInfo -NR NTN Ephemeris Information for NGSO (LEO-600) satellites (maximum positive Doppler/2)** + +| Derivation Path: TS 38.598-1, Table 4.6.3-56C | | | | +|-----------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| EphemerisInfo-r17 ::= CHOICE { | | | | +| positionVelocity-r17 SEQUENCE { | | | | +| positionX-r17 | -2592823 | | | +| positionY-r17 | 4245650 | | | +| positionZ-r17 | 2024520 | | | +| velocityVX-r17 | 19359 | | | +| velocityVY-r17 | -43278 | | | +| velocityVZ-r17 | 116553 | | | +| } | | | | +| } | | | | + +NOTE 1: Satellite-UE elevation angle equal to 60.25 degrees, one-way delay equal to 2.30 ms and Doppler equal to 11.29 ppm. + +#### 6.4.1.5 Test requirement + +The frequency error $\Delta f$ shall fulfil the test requirement: + +$$|\Delta f| \leq (0.1 \text{ PPM} + [15 \text{ Hz}])$$ + +The above requirement shall be verified for at least two cases of which one has zero Doppler conditions. + +### 6.5 Output RF spectrum emissions + +[to be updated] + +#### 6.5.1 Occupied bandwidth + +[to be updated] + +#### 6.5.2 Out of band emission + +##### 6.5.2.1 [to be updated] + +##### 6.5.2.2 Spectrum emission mask + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access is to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +##### 6.5.2.2.1 Test purpose + +To verify that the power of any UE emission shall not exceed specified level for the specified channel bandwidth + +#### 6.5.2.2.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +#### 6.5.2.2.3 Minimum conformance requirements + +The spectrum emission mask of the UE applies to frequencies ( $\Delta f_{\text{OOB}}$ ) starting from the $\pm$ edge of the assigned NR channel bandwidth. For frequencies offset greater than $\Delta f_{\text{OOB}}$ , the spurious requirements in clause 6.5.3 are applicable. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +The power of any UE emission shall not exceed the levels specified in Table 6.5.2.3-1 for the specified channel bandwidth. + +**Table 6.5.2.3-1: General NR spectrum emission mask** + +| $\Delta f_{\text{OOB}}$
(MHz) | Channel bandwidth (MHz) / Spectrum emission limit
(dBm) | | Measurement bandwidth | +|-----------------------------------------------------------------|------------------------------------------------------------|------------|-----------------------| +| | 5 | 10, 15, 20 | | +| $\pm 0-1$ | -13 | -13 | 1 % of channel BW | +| $\pm 1-5$ | -10 | -10 | | +| $\pm 5-6$ | -13 | | | +| $\pm 6-10$ | -25 | | 1 MHz | +| $\pm 5-\text{BW}_{\text{Channel}}$ | | -13 | | +| $\pm \text{BW}_{\text{Channel}}-(\text{BW}_{\text{Channel}}+5)$ | | -25 | | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.5.2.2. + +#### 6.5.2.2.4 Test description + +##### 6.5.2.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Table 6.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +**Table 6.2.2.4.1-1: Test Configuration Table for power class 3 (contiguous allocation)** + +| Default Conditions | | | | | | +|--------------------------------------------------------------------------|-----------------------|------|-----|------------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal | | | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Low range, High range | | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Lowest, Highest | | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest, Highest | | | | | +| Test Parameters for Channel Bandwidths | | | | | | +| Test ID | Freq | ChBw | SCS | Downlink Configuration | Uplink Configuration | + +| | | Default | Default | N/A for Spectrum Emission Mask test case | Modulation (NOTE 2) | RB allocation (NOTE 1) | +|----------------|---------|---------|---------|------------------------------------------|----------------------|------------------------| +| 4 4 | Low | | | | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Left | +| 5 4 | High | | | | DFT-s-OFDM Pi/2 BPSK | Edge_1RB_Right | +| 6 4 | Default | | | | DFT-s-OFDM Pi/2 BPSK | Outer_Full | +| 7 | Low | | | | DFT-s-OFDM QPSK | Edger_1RB_Left | +| 8 | High | | | | DFT-s-OFDM QPSK | Edge_1RB_Right | +| 9 | Default | | | | DFT-s-OFDM QPSK | Outer_Full | +| 10 | Low | | | | DFT-s-OFDM 16 QAM | Edge_1RB_Left | +| 11 | High | | | | DFT-s-OFDM 16 QAM | Edge_1RB_Right | +| 12 | Default | | | | DFT-s-OFDM 16 QAM | Outer_Full | +| 13 | Low | | | | DFT-s-OFDM 64 QAM | Edge_1RB_Left | +| 14 | High | | | | DFT-s-OFDM 64 QAM | Edge_1RB_Right | +| 15 | Default | | | | DFT-s-OFDM 64 QAM | Outer_Full | +| 19 | Low | | | | CP-OFDM QPSK | Edge_1RB_Left | +| 20 | High | | | | CP-OFDM QPSK | Edge_1RB_Right | +| 21 | Default | | | | CP-OFDM QPSK | Outer_Full | +| 22 | Low | | | | CP-OFDM 16 QAM | Edge_1RB_Left | +| 23 | High | | | | CP-OFDM 16 QAM | Edge_1RB_Right | +| 24 | Default | | | | CP-OFDM 16 QAM | Outer_Full | +| 25 | Low | | | | CP-OFDM 64 QAM | Edge_1RB_Left | +| 26 | High | | | | CP-OFDM 64 QAM | Edge_1RB_Right | +| 27 | Default | | | | CP-OFDM 64 QAM | Outer_Full | +| 28 | Low | | | | CP-OFDM 256 QAM | Edge_1RB_Left | +| 29 | High | | | | CP-OFDM 256 QAM | Edge_1RB_Right | +| 30 | Default | | | | CP-OFDM 256 QAM | Outer_Full | + +NOTE 1: The specific configuration of each RF allocation is defined in Table 6.1-1. + +NOTE 2: DFT-s-OFDM Pi/2 BPSK test applies only for UEs which supports half Pi BPSK in FR1. + +NOTE 3: VOID + +NOTE 4: UE operating in FDD mode, or in TDD mode in bands other than n40, n41, n77, n78 and n79, or in TDD mode the IE *powerBoostPi2BPSK* is set to 0 for bands n40, n41, n77, n78 and n79. + +NOTE 5: For Power Class 3 testing, UE operating in FDD mode, or in TDD mode in bands other than n40, n41, n77, n78 and n79, or in TDD mode the IE *powerBoostPi2BPSK* is set to 0 for bands n40, n41, n77, n78 and n79. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. + +3. Downlink signals are initially set up according to TS 38.521-1 [2] Annex C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] Annex G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.2.4.1-1. +5. Propagation conditions are set according to TS 38.521-1 [2] Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State [to be updated] with generic procedure parameters [to be updated], Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.2.4.3. + +#### 6.5.2.2.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5.2.2.4.1-1, Table 6.5.2.2.4.1-2, Table 6.5.2.2.4.1-2a and Table 6.5.2.2.4.1-3. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously power control "up" commands to the UE until the UE transmits at PUMAX level. Allow at least 200 ms for the UE to reach PUMAX level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode according to the test configuration, which shall meet the requirements described in Tables 6.2.2.5-1 to 6.2.2.5-9. The period of the measurement shall be at least the continuous duration of 1 ms over consecutive active uplink slots. For TDD, only slots consisting of only UL symbols are under test. +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to table 6.5.2.2.5-1. The centre frequency of the filter shall be stepped in continuous steps according to the same table. The measured power shall be recorded for each step. The measurement period shall capture the active TSs. + +NOTE 1: When switching to DFT-s-OFDM waveform, as specified in the test configuration table 6.5.2.2.4.1-1, table 6.5.2.2.4.1-2, and table 6.5.2.2.4.1-2a, send an NR RRCReconfiguration message according to TS 38.508-1 [12] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +#### 6.5.2.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [to be updated] subclause 4.6 and 5.4 with the following exceptions: + +**Table 6.5.2.2.4.3-1: PUSCH-Config** + +| Derivation Path: TS 38.508-1 [12] subclause 4.6.3 Table 4.6.3-118 PUSCH-Config | | | | +|--------------------------------------------------------------------------------|-------------------------|---------|------------------------------| +| Information Element | Value/remark | Comment | Condition | +| PUSCH-Config ::= SEQUENCE { | | | | +| resourceAllocation | resourceAllocationType0 | | Almost contiguous allocation | +| | resourceAllocationType1 | | | +| } | | | | + +#### 6.5.2.2.5 Test requirement + +The measured UE mean power in the channel bandwidth, derived in step 3, shall fulfil requirements in Tables 6.2.2.5-1, and the power of any UE emission shall fulfil requirements in Table 6.5.2.2.5-1. + +Table 6.5.2.2.5-1: General NR spectrum emission mask + +| $\Delta f_{\text{OOB}}$
(MHz) | Channel bandwidth (MHz) / Spectrum emission limit
(dBm) | | Measurement bandwidth | +|-----------------------------------------------------------------|------------------------------------------------------------|------------|-----------------------| +| | 5 | 10, 15, 20 | | +| $\pm 0-1$ | -13+TT | -13+TT | 1 % of channel BW | +| $\pm 1-5$ | -10+TT | -10+TT | 1 MHz | +| $\pm 5-6$ | -13+TT | | | +| $\pm 6-10$ | -25+TT | | | +| $\pm 5\text{-BW}_{\text{Channel}}$ | | -13+TT | | +| $\pm \text{BW}_{\text{Channel}}\text{-(BW}_{\text{Channel}}+5)$ | | -25+TT | | + +Table 6.5.2.2.5-2: Test Tolerance (Spectrum Emission Mask) + +## [to be updated] + +NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +## 6.5.2.3 [to be updated] + +## 6.5.2.4 Adjacent channel leakage ratio + +## 6.5.2.4.0 General + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +To improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +## 6.5.2.4.1 NR Adjacent channel leakage ratio + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access is to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +## 6.5.2.4.1.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to adjacent channels in terms of Adjacent Channel Leakage power Ratio (ACLR). + +## 6.5.2.4.1.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +## 6.5.2.4.1.3 Minimum conformance requirements + +NR Adjacent Channel Leakage power Ratio (NRACLR) is the ratio of the filtered mean power centred on the assigned NR channel frequency to the filtered mean power centred on an adjacent NR channel frequency at nominal channel spacing. + +The assigned NR channel power and adjacent NR channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.5.2.4.1-1. + +If the measured adjacent channel power is greater than -50 dBm then the NRACLR shall be higher than the value specified in Table 6.5.2.4.1-2. + +**Table 6.5.2.4.1-1: NR ACLR measurement bandwidth** + +| | | | +|--------------------------------------|-------|---------------------------------------------| +| Channel bandwidth | (MHz) | 5,10,15,20 | +| REF_SCS | (kHz) | 15 | +| NR ACLR measurement bandwidth | (MHz) | $MBW = REF\_SCS * (12 * N_{RB} + 1) / 1000$ | + +**Table 6.5.2.4.1-2: NR ACLR requirement** + +| | | +|----------------|----------------------| +| | Power class 3 | +| NR ACLR | 30 dB | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.5.2.4.1. + +## 6.5.2.4.1.4 Test description + +## 6.5.2.4.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Table 6.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +**Table 6.2.2.4.1-1: VOID** + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.2.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.2.4.1-1. +5. Propagation conditions are set according to TS 38.521-1 [2] Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. + +8. Ensure the UE is in State [to be updated] with generic procedure parameters according to TS 38.508-1 [12] clause [to be updated], Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.2.4.3. + +#### 6.5.2.4.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to the test configuration tables in clause 6.2.2.4.1T. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously power control "up" commands to the UE until the UE transmits at $P_{\text{UMAX}}$ level. Allow at least 200 ms for the UE to reach $P_{\text{UMAX}}$ level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode according to the test configuration, as measured in step 3 of 6.2.2.4.2, which shall meet the requirements described in clause 6.2.2.5 as appropriate. +4. Measure the rectangular filtered mean power for the assigned NR channel. +5. Measure the rectangular filtered mean power of the first NR adjacent channel on both lower and upper side of the assigned NR channel, respectively. +6. Calculate the ratios of the power between the values measured in step 4 over step 5 for lower and upper NR ACLR, respectively. + +NOTE: When switching to DFT-s-OFDM waveform, as specified in the test configuration tables in clause 6.2.2.4.1, send an NR RRCReconfiguration message according to TS 38.508-1 [12] clause 4.6.3 Table 4.6.3-118 PUSCH-Config with TRANSFORM\_PRECODER\_ENABLED condition. + +#### 6.5.2.4.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 and 5.4 with the following exceptions: + +**Table 6.5.2.4.1.4.3-1: *P-Max* (Step 7)** + +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-89 | | | | +|---------------------------------------------------|--------------|---------|------------------| +| Information Element | Value/remark | Comment | Condition | +| P-Max | 23 | | PC2 UE or PC1 UE | + +**Table 6.5.2.4.1.4.3-1a: Void** + +**Table 6.5.2.4.1.4.3-2: *PUSCH-Config*** + +| Derivation Path: TS 38.508-1 [12] subclause 4.6.3 Table 4.6.3-118 PUSCH-Config | | | | +|--------------------------------------------------------------------------------|-------------------------|---------|------------------------------| +| Information Element | Value/remark | Comment | Condition | +| PUSCH-Config ::= SEQUENCE { | | | | +| resourceAllocation | resourceAllocationType0 | | Almost contiguous allocation | +| | resourceAllocationType1 | | Contiguous allocation | +| } | | | | + +Table 6.5.2.4.1.4.3-3: DMRS-UplinkConfig (Test ID 33-35 in Table 6.2.2.4.1-1) + +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-51 | | | | +|---------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| DMRS-UplinkConfig ::= SEQUENCE { | | | | +| transformPrecodingEnabled SEQUENCE { | | | | +| dmrs-UplinkTransformPrecoding-r16 { | | | | +| Setup SEQUENCE { | | | | +| pi2BPSK-ScramblingID0 | Not present | | | +| pi2BPSK-ScramblingID1 | Not present | | | +| } | | | | +| } | | | | +| } | | | | +| } | | | | + +Table 6.5.2.4.1.4.3-4: ServingCellConfig + +| Derivation Path: TS 38.508-1 [12] Table 4.6.3-167 | | | | +|---------------------------------------------------|--------------|---------|-----------------------------------------------------| +| Information Element | Value/remark | Comment | Condition | +| ServingCellConfig ::= SEQUENCE { | | | | +| uplinkConfig SEQUENCE { | | | | +| powerBoostPi2BPSK | 1 | | Test IDs where NOTE 3 in Table 6.2.2.4.1-1 applies. | +| | 0 | | Test IDs where NOTE 4 in Table 6.2.2.4.1-1 applies. | +| } | | | | +| } | | | | + +#### 6.5.2.4.1.5 Test requirement + +The measured UE mean power in the channel bandwidth, derived in step 3, shall fulfil requirements in clause 6.2.2.5 as appropriate, and if the measured adjacent channel power is greater than $-50$ dBm then the measured NR ACLR, derived in step 6, shall be higher than the limits in Table 6.5.2.4.1.5-2. + +The measured UE mean power in the channel bandwidth, derived in step 7, shall fulfil power class 3 requirements in Tables 6.2.2.5-1 and 6.2.2.5-3 as appropriate, and if the measured adjacent channel power is greater than $-50$ dBm then the measured NR ACLR, derived in step 7, shall be higher than the power class 3 limits in Table 6.5.2.4.1.5-2. + +Table 6.5.2.4.1.5-1: NR ACLR measurement bandwidth + +| | | | +|-------------------------------|-------|---------------------------------------------| +| Channel bandwidth | (MHz) | 5, 10, 15, 20 | +| REF_SCS | (kHz) | 15 | +| NR ACLR measurement bandwidth | (MHz) | $MBW = REF\_SCS * (12 * N_{RB} + 1) / 1000$ | + +Table 6.5.2.4.1.5-2: NR ACLR requirement + +| | | +|---------|---------------| +| | Power class 3 | +| NR ACLR | 30 - TT dB | + +Table 6.5.2.4.1.5-3: Test Tolerance (NR ACLR) + +[to be updated] + +#### 6.5.2.4.2 UTRA Adjacent channel leakage ratio + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access is to be updated +- Message exceptions specific to satellite access is to be updated +- Test Points analysis is to be updated +- Test configuration is to be updated +- Annex F MU/TT is to be updated + +#### 6.5.2.4.2.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to adjacent channels in terms of Adjacent Channel Leakage power Ratio (ACLR). + +#### 6.5.2.4.2.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +#### 6.5.2.4.2.3 Minimum conformance requirements + +UTRA adjacent channel leakage power ratio (UTRAACLR) is the ratio of the filtered mean power centred on the assigned NR channel frequency to the filtered mean power centred on an adjacent(s) UTRA channel frequency. + +UTRAACLR is specified for the first adjacent UTRA channel (UTRAACLR1) which center frequency is $\pm 2.5$ MHz from NR channel edge and for the 2nd adjacent UTRA channel (UTRAACLR2) which center frequency is $\pm 7.5$ MHz from NR channel edge. + +The UTRA channel power is measured with a RRC filter with roll-off factor $\alpha = 0.22$ and bandwidth of 3.84 MHz. The assigned NR channel power is measured with a rectangular filter with measurement bandwidth specified in Table 6.5.2.4.1-1. + +If the measured adjacent channel power is greater than $-50$ dBm then the UTRAACLR1 and UTRAACLR2 shall be higher than the value specified in Table 6.5.2.4.2-1. + +**Table 6.5.2.4.2-1: UTRA ACLR requirement** + +| | Power class 3 | +|-----------------------|---------------| +| UTRA ACLR1 | 33 dB | +| UTRA ACLR2 | 36 dB | + +UTRA ACLR requirement is applicable when signalled by the network with network signalling value indicated by the field *additionalSpectrumEmission*. + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.5.2.4.2. + +#### 6.5.2.4.2.4 Test description + +##### 6.5.2.4.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Table 6.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +**Table 6.2.2.4.2-1: Test Configuration Table for power class 3****[to be updated]** + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [to be updated] Annex A, Figure A.3.1.2.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [to be updated] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.2.4.1-1. +5. Propagation conditions are set according to TS 38.521-1 [2] Annex B.0. +6. Ensure the UE is in State [to be updated] with generic procedure parameters [to be updated], Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [to be updated] clause 4.5. Message contents are defined in clause 6.2.2.4.3. + +#### 6.5.2.4.2.4.2 Test procedure + +[to be updated] + +#### 6.5.2.4.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [to be updated] subclause 4.6 and 5.4 with the following exceptions: + +[to be updated] + +#### 6.5.2.4.2.5 Test requirement + +[to be updated] + +### 6.5.3 Spurious emission + +#### 6.5.3.0 General + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, intermodulation products and frequency conversion products, but exclude out of band emissions unless otherwise stated. The spurious emission limits are specified in terms of general requirements in line with SM.329 [to be updated] and NTN operating band requirement to address UE co-existence. + +To improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +#### 6.5.3.1 General spurious emissions + +**Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated + +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +#### 6.5.3.1.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions. + +#### 6.5.3.1.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +#### 6.5.3.1.3 Minimum conformance requirements + +Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1.3-1 from the edge of the channel bandwidth. The spurious emission limits in Table 6.5.3.1.3-2 apply for all transmitter band configurations ( $N_{\text{RB}}$ ) and channel bandwidths. + +**Table 6.5.3.1.3-1: Boundary between NR out of band and general spurious emission domain** + +| Channel bandwidth | OOB boundary $F_{\text{OOB}}$ (MHz) | +|-----------------------|-------------------------------------| +| $BW_{\text{Channel}}$ | $BW_{\text{Channel}} + 5$ | + +**Table 6.5.3.1.3-2: Requirement for general spurious emissions limits** + +| Frequency Range | Maximum Level | Measurement bandwidth | NOTE | +|-------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| $9 \text{ kHz} \leq f < 150 \text{ kHz}$ | -36 dBm | 1 kHz | | +| $150 \text{ kHz} \leq f < 30 \text{ MHz}$ | -36 dBm | 10 kHz | | +| $30 \text{ MHz} \leq f < 1,000 \text{ MHz}$ | -36 dBm | 100 kHz | | +| $1 \text{ GHz} \leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the UL operating band in GHz | -30 dBm | 1 MHz | | + +The normative reference for this requirement is TS 38.101-5 [11] subclause 6.5.3.1 + +#### 6.5.3.1.4 Test description + +##### 6.5.3.1.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in Table 6.5.3.1.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in [to be updated]. Configurations of PDSCH and PDCCH before measurement are specified in [to be updated]. + +Table 6.5.3.1.4.1-1: Test Configuration Table + +| Initial Conditions | | | | +|---------------------------------------------------------------------------|------------------------------------|-----------------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1. | Normal | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1. | Low range, Mid range, High range | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1. | Lowest, Mid, Highest | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | +| Test Parameters | | | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | | Modulation | RB allocation (NOTE 1) | +| 1 | N/A for Spurious Emissions testing | CP-OFDM QPSK | OuterFull | +| 2 | | CP-OFDM QPSK | Edge_1RB_Left | +| 3 | | CP-OFDM QPSK | Edge_1RB_Right | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 Common UL configuration. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure [to be updated] for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to Annex [to be updated] +4. The UL Reference Measurement channels are set according to Table 6.5.3.1.4.1-1. +5. Propagation conditions are set according to Annex [to be updated]. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.5.3.1.4.3. + +#### 6.5.3.1.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5.3.1.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE until the UE transmits at PMAX level. +3. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5.3.1.5-1. The centre frequency of the filter shall be stepped in contiguous steps according to Table 6.5.3.1.5-1. The measured power shall be verified for each step. The measurement period shall capture the active time slots. + +#### 6.5.3.1.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 with below exceptions. + +[to be updated] + +#### 6.5.3.1.5 Test requirement + +This clause specifies the requirements for the specified NR band for Transmitter Spurious emissions requirement with frequency range as indicated in Table 6.5.3.1.5-1. + +Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1.3-1 from the edge of the channel bandwidth. The spurious emission limits in Table 6.5.3.1.5-1 apply for all transmitter band configurations ( $N_{\text{RB}}$ ) and channel bandwidths. + +The measured average power of spurious emission, derived in step 3, shall not exceed the described value in Table 6.5.3.1.5-1. + +**Table 6.5.3.1.5-1: General spurious emissions test requirements** + +| frequency Range | Maximum Level | Measurement bandwidth | NOTE | +|-------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| $9 \text{ kHz} \leq f < 150 \text{ kHz}$ | -36 dBm | 1 kHz | | +| $150 \text{ kHz} \leq f < 30 \text{ MHz}$ | -36 dBm | 10 kHz | | +| $30 \text{ MHz} \leq f < 1,000 \text{ MHz}$ | -36 dBm | 100 kHz | | +| $1 \text{ GHz} \leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the UL operating band in GHz | -30 dBm | 1 MHz | | + +## 6.5.3.2 Spurious emissions for UE co-existence + +*Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined:* + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +### 6.5.3.2.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to co-existing systems for the specified bands which has specific requirements in terms of transmitter spurious emissions. + +### 6.5.3.2.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 6.5.3.2.3 Minimum conformance requirements + +This clause specifies the requirements for NR NTN satellite bands for UE coexistence with protected bands. + +Table 6.5.3.2.3-1: Requirements for spurious emissions for UE co-existence + +| NR NTN satellite Band | Spurious emission for UE co-existence | | | | | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|------| +| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| n255 | NR Band n1, n2, n3, n5, n7, n8, n12, n13, n14, n18, n20, n24, n25, n26, n28, n29, n30, n34, n38, n39, n40, n41, n48, n50, n51, n53, n65, n66, n67, n70, n71, n74, n75, n76, n85, n90, n91, n92, n93, n94, n100, n101 | F DL_low | - | F DL_high | -50 | 1 | +| | NR Band n77, n78, n79 | F DL_low | - | F DL_high | -50 | 1 2 | +| n256 | NR Band n1, n3, n5, n7, n8, n12, n13, n14, n18, n20, n24, n26, n28, n29, n30, n38, n39, n40, n41, n48, n50, n51, n53, n65, n66, n67, n71, n74, n75, n76, n78, n79, n85, n90, n91, n92, n93, n94, n101, n100, n101 | F DL_low | - | F DL_high | -50 | 1 | +| | E-UTRA Band 33, 35, 54 | F DL_low | - | F DL_high | -50 | 1 | +| | NR Band n77 | F DL_low | - | F DL_high | -50 | 1 2 | +| | NR Band n2, n25, n70 | F DL_low | - | F DL_high | NA | NA 3 | + +NOTE 1: The protected NR or E-UTRA bands are specified in clause 5.2 from 3GPP TS 38.101-1 [5] or 3GPP TS 36.101 [10]. FDL\_low and FDL\_high refer to each frequency band specified in Table 5.2.2-1 in 3GPP TS 38.101-1 [5] or 3GPP TS 36.101 [10]. + +NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1.3-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of (2 MHz + N x LCRB x RBsize kHz), where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. + +NOTE 3: The co-existence between n256 and band n2, n25 and n70 is subject to regional/national regulation. + +The normative reference for this requirement is TS 38.101-5 [11] subclause 6.5.3.2. + +## 6.5.3.2.4 Test description + +### 6.5.3.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in Table 6.5.3.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in [to be updated]. Configurations of PDSCH and PDCCH before measurement are specified in [to be updated]. + +Table 6.5.3.2.4.1-1: Test Configuration Table + +| Initial Conditions | | | | +|---------------------------------------------------------------------------|----------------------------------|----------------------|------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1. | Normal | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1. | Low range, Mid range, High range | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1. | Lowest, Mid, Highest | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | +| Test Parameters | | | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | N/A | Modulation | RB allocation (NOTE 1) | +| 1 | | CP-OFDM QPSK | Outer_Full | +| 2 | | CP-OFDM QPSK | Edge_1RB_Left | +| 3 | | CP-OFDM QPSK | Edge_1RB_Right | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1 Common UL configuration. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 12 Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 12 subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1 and C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement channels are set according to Table 6.5.3.2.4.1-1. +5. Propagation conditions are set according to Annex B.0 in TS 38.521-1 [2]. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 12 clause 4.5. Message contents are defined in clause 6.5.3.2.4.3. + +#### 6.5.3.2.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5.3.2.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE until the UE transmits at $P_{\text{UMAX}}$ level. +3. Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.5.3.2.3-1. The centre frequency of the filter shall be stepped in contiguous steps according to Table 6.5.3.2.3-1. The measured power shall be verified for each step. The measurement period shall capture the active time slots. + +#### 6.5.3.2.4.3 Message contents + +Message contents are according to TS 38.508-1[12] subclause 4.6. + +#### 6.5.3.1.5 Test requirement + +Test requirements for Spurious Emissions UE Co-existence are the same as the minimum requirements and are not repeated in this clause. + +Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than $F_{\text{OOB}}$ (MHz) in Tables 6.5.3.1.3-1 from the edge of the channel bandwidth. The spurious emission limits in Tables 6.5.3.2.3-1 apply for all transmitter band configurations (NRB) and channel bandwidths. + +The measured average power of spurious emission, derived in step 3, shall not exceed the described value in Table 6.5.3.2.3-1. + +### 6.5.3.3 Additional Spurious emissions + +**Editor's Note:** This clause is incomplete. The following aspects are either missing or not yet determined: + +- Test configuration is to be updated +- Annex F MU/TT is to be updated +- Relative power TC Table 6.3.4.3.3-1 is to be updated + +#### 6.5.3.3.1 Test purpose + +To verify that UE transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions under the deployment scenarios where additional requirements are specified. + +#### 6.5.3.3.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +#### 6.5.3.3.3 Minimum conformance requirements + +These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. + +The normative reference for this requirement is TS 38.101-5 [11] subclause 6.5.3.3. + +##### 6.5.3.3.3.1 Minimum conformance requirements (network signalling value "NS\_02N") + +When "NS\_02N" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.3.3.1-1. This requirement also applies for the frequency ranges that are less than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1.3-1 from the edge of the channel bandwidth. + +**Table 6.5.3.3.3.1-1: Additional requirements for "NS\_02N"** + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit 1 (dBm) | Measurement bandwidth | NOTE | +|-------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------|--------------------------------------------------------------| +| | 5 MHz, 10 MHz, 15 MHz, 20 MHz | | | +| $1,559 \leq f \leq 1,605$ | -50 | 700 Hz | Averaged over any 2 millisecond active transmission interval | +| $1,605 \leq f \leq 1,610$ | $-50 + 24/5 (f-1605)$ | 700Hz | | +| $1,559 \leq f \leq 1,605$ | -40 | 1MHz | Averaged over any 2 millisecond active transmission interval | +| $1,605 \leq f \leq 1,610$ | $-40 + 24/5 (f-1605)$ | 1MHz | | +| NOTE: The EIRP requirement in regulation is converted to conducted requirement using a 0 dBi antenna. | | | | + +### 6.5.3.3.4 Test description + +#### 6.5.3.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All these configurations shall be tested with applicable test parameters for each channel bandwidth and sub-carrier spacing, are shown in Tables 6.5.3.3.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 Annex C.2. + +**Table 6.5.3.3.4.1-1: Test Configuration Table** + +**[to be updated]** + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1 and C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement channels are set according to Table 6.5.3.3.4.1-1. +5. Propagation conditions are set according to Annex B.0 in TS 38.521-1 [2]. +6. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +7. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508 [12] table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +8. Deactivate UE prediction of satellite trajectory by any preconfigured means. + +#### 6.5.3.3.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5.3.3.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE until the UE transmits at $P_{\text{UMAX}}$ level. +3. Measure the mean power of the UE in the channel bandwidth of the radio access mode according to the test configuration in Tables 6.5.3.3.4.1-1, which shall meet the requirements in clause 6.5.3.3.5 with allowed A-MPR values specified in 6.2.3.5. The measured power shall be verified for each step. The measurement period shall capture the active time slots. +4. Measure the power of the transmitted signal with a measurement filter of bandwidths according to clauses 6.5.3.3.3.1. The centre frequency of the filter shall be stepped in contiguous steps according to the same table. During measurement the spectrum analyser shall be set to 'Detector' = RMS. For NS\_02N the additional spurious emissions requirement shall be verified with UE transmission power obtained by sending uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(\text{MU} + \text{Uplink power control window size})$ dB of the target power level 15 dBm for at least the duration of the additional spurious emissions measurement, where: + +- MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW. +- Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in [Table 6.3.4.3.3-1] and is [0.7dB] for 1dB power step size, and the Test system relative power measurement uncertainty is specified for test case 6.3.4.3 in Table F.1.2-1. + +#### 6.5.3.3.4.3 Message contents + +Message contents for SIB19 are according to TS 38.508-1 [12] clause 5.6.2.1 with following exceptions: + +##### 6.5.3.3.4.3.1 Message contents exceptions (network signalling value "NS\_02N") + +Message contents are according to TS 38.508-1 [12] subclause 4.6, with the following exceptions: + +1. Information element additionalSpectrumEmission is set to NS\_02N. This can be set in *SIB1* as part of the cell broadcast message. This exception indicates that the UE shall meet the additional spurious emission requirement for a specific deployment scenario. + +**Table 6.5.3.3.4.3.1-1: AdditionalSpectrumEmission: Additional spurious emissions test requirement for "NS\_02N"** + +| Derivation Path: TS 38.508-1 [12] clause 4.6.3, Table 4.6.3-1 | | | | +|---------------------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| additionalSpectrumEmission | 1 (NS_02N) | | | + +#### 6.5.3.3.5 Test requirement + +This clause specifies the requirements for the specified NR band for an additional spectrum emission requirement with protected bands as indicated from Table 6.5.3.3.5.1. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +##### 6.5.3.3.5.1 Test requirement (network signalling value "NS\_02N") + +When "NS\_02N" is indicated in the cell, + +The power of any UE emission shall not exceed the levels specified in Table 6.5.3.3.5.1-1. This requirement also applies for the frequency ranges that are less than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1.3-1 from the edge of the channel bandwidth. + +Table 6.5.3.3.5.1-1: Additional requirements for "NS\_02N" + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit 1 (dBm) | Measurement bandwidth | NOTE | +|---------------------------|----------------------------------------------------------------|-----------------------|--------------------------------------------------------------| +| | 5 MHz, 10 MHz, 15 MHz, 20 MHz | | | +| $1,559 \leq f \leq 1,605$ | -50 | 700 Hz | Averaged over any 2-millisecond active transmission interval | +| $1,605 \leq f \leq 1,610$ | $-50 + 24/5 (f - 1605)$ | 700Hz | | +| $1,559 \leq f \leq 1,605$ | -40 | 1MHz | Averaged over any 2-millisecond active transmission interval | +| $1,605 \leq f \leq 1,610$ | $-40 + 24/5 (f - 1605)$ | 1MHz | | + +NOTE: The EIRP requirement in regulation is converted to conducted requirement using a 0 dBi antenna. + +## 6.5.4 Transmit intermodulation + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated +- Annex F MU/TT is to be updated + +### 6.5.4.1 Test purpose + +To verify that the UE transmit intermodulation does not exceed the described value in the test requirement. + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +### 6.5.4.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 6.5.4.3 Minimum conformance requirements + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +UE transmit intermodulation is defined by the ratio of the mean power of the wanted signal to the mean power of the intermodulation product when an interfering CW signal is added at a level below the wanted signal at each transmitter antenna port with the other antenna port(s) if any terminated. Both the wanted signal power and the intermodulation product power are measured through NR rectangular filter with measurement bandwidth shown in Table 6.5.4.3-1. + +The requirement of transmit intermodulation is specified in Table 6.5.4.3-1. + +**Table 6.5.4.3-1: Transmit Intermodulation** + +| | | | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| Wanted signal channel bandwidth | $BW_{\text{Channel}}$ | | +| Interference signal frequency offset from channel center | $BW_{\text{Channel}}$ | $2*BW_{\text{Channel}}$ | +| Interference CW signal level | -40 dBc | | +| Intermodulation product | < -29 dBc | < -35 dBc | +| Measurement bandwidth | The maximum transmission bandwidth configuration among the different SCS's for the channel BW as defined in Table 6.5.2.4.1-1 | | +| Measurement offset from channel center | $BW_{\text{Channel}}$ and $2*BW_{\text{Channel}}$ | $2*BW_{\text{Channel}}$ and $4*BW_{\text{Channel}}$ | + +The normative reference for this requirement is TS 38.101-5 [11] clause 6.5.4. + +## 6.5.4.4 Test description + +### 6.5.4.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, and are shown in table 6.5.4.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in Annexes A.2. Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 6.5.4.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | +|--------------------------------------------------------------------------|--------------------------------------------|-----------------------------|-------------------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Mid range | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Mid, Highest | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest, Highest | | | +| Test Parameters | | | | +| Test ID | Downlink Configuration | Uplink Configuration | | +| | N/A for transmit intermodulation test case | Modulation | | +| 1 | | DFT-s-OFDM PI/2 BPSK | RB allocation (NOTE 1) | +| 2 | | DFT-s-OFDM QPSK | Inner Full | + +NOTE 1: The specific configuration of each RB allocation is defined in Table 6.1-1. + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, in Figure A.3.1.3.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to clauses C.0, C.1, C.2, and uplink signals according to clauses G.0, G.1, G.2, G.3.0 in TS 38.521-1 [2]. +4. The UL Reference Measurement channels are set according to Table 6.5.4.4.1-1. +5. Propagation conditions are set according to Annex B.0 in TS 38.521-1 [2]. + +6. Ensure the UE is in State RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.5.4.4.3. + +#### 6.5.4.4.2 Test procedure + +1. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 6.5.4.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +2. Send continuously uplink power control "up" commands to the UE until the UE transmits at its $P_{UMAX}$ level. +3. Measure the rectangular filtered mean power of the UE. For TDD, only slots consisting of only UL symbols are under test for the wanted signal and for the intermodulation product. +4. Set the interference signal frequency below the UL carrier frequency using the first offset in table 6.5.4.5-1. +5. Set the interference CW signal level according to table 6.5.4.5-1. +6. Search the intermodulation product signals below and above the UL carrier frequency, then measure the rectangular filtered mean power of transmitting intermodulation for both signals, and calculate the ratios with the power measured in step 3. +7. Set the interference signal frequency above the UL carrier frequency using the first offset in table 6.5.4.5-1. +8. Search the intermodulation product signals below and above the UL carrier frequency, then measure the rectangular filtered mean power of transmitting intermodulation for both signals, and calculate the ratios with the power measured in step 3. +9. Repeat the measurement using the second offset in table 6.5.4.5-1. + +#### 6.5.4.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 with the following exception: + +**Table 6.5.4.4.3-1: PUSCH-Config** + +| | +|-----------------------------------------------------------------------------------------------------| +| Derivation Path: TS 38.508-1 [12], Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED | +|-----------------------------------------------------------------------------------------------------| + +#### 6.5.4.5 Test requirement + +The ratio derived in step 6 and 8, shall not exceed the described value in table 6.5.4.5-1. + +**Table 6.5.4.5-1: Transmit Intermodulation** + +| | | | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| Wanted signal channel bandwidth | $BW_{Channel}$ | | +| Interference signal frequency offset from channel center | $BW_{Channel}$ | $2*BW_{Channel}$ | +| Interference CW signal level | -40 dBc | | +| Intermodulation product | < -29 dBc | < -35 dBc | +| Measurement bandwidth | The maximum transmission bandwidth configuration among the different SCS's for the channel BW as defined in Table 6.5.2.4.1-1 | | +| Measurement offset from channel center | $BW_{Channel}$ and $2*BW_{Channel}$ | $2*BW_{Channel}$ and $4*BW_{Channel}$ | +| NOTE: | The test requirements do not apply when the interfering signal overlaps with the channel bandwidth of the downlink signal. | | + +## 7 Receiver characteristics + +### 7.1 General + +Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the UE. For UE(s) with an integral antenna only, a reference antenna(s) with a gain of 0 dBi is assumed for each antenna port(s). UE with an integral antenna(s) may be taken into account by converting these power levels into field strength requirements, assuming a 0 dBi gain antenna. For UEs with more than one receiver antenna connector, identical interfering signals shall be applied to each receiver antenna port if more than one of these is used (diversity). + +The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective clauses below. + +With the exception of clause 7.3, the requirements shall be verified with the network signalling value NS\_01 configured in Table [to be updated]. + +All requirements in this clause are applicable to devices supporting GSO and/or NGSO satellites. + +All the parameters in clause 7 are defined using the UL reference measurement channels specified in 3GPP TS 38.101-1 [5] Annex A.2.2, the DL reference measurement channels specified in 3GPP TS 38.101-1 [5] Annex A.3.2 and using the set-up specified in 3GPP TS 38.101-1 [5] Annex C.3.1. + +### 7.2 Diversity characteristics + +The UE is required to be equipped with a minimum of two RX antenna ports in all operating bands. + +The UE shall be verified with two RX antenna ports in all supported frequency bands. + +The above rules apply for all clauses with the exception of clause 7.9. + +### 7.3 Reference sensitivity + +#### 7.3.1 General + +The reference sensitivity power level REFSENS is the minimum mean power applied to each one of the UE antenna ports for all UE categories, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. + +In later clauses of Clause 7 where the value of REFSENS is used as a reference to set the corresponding requirement. In all bands, the UE shall be verified against those requirements by applying the REFSENS value in Table 7.3.2.3-1. + +#### 7.3.2 Reference sensitivity power level + +**Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined:** + +**- Annex F MU/TT is to be updated** + +##### 7.3.2.1 Test purpose + +The test purpose is to verify the ability of the UE to receive data with a given average throughput for a specified reference measurement channel, under conditions of low signal level, ideal propagation and no added noise. + +##### 7.3.2.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 7.3.2.3 Minimum conformance requirements + +The throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in Annex A3.2.2 of 3GPP TS 38.101-1 [5], with parameters specified in Table 7.3.2.3-1. + +**Table 7.3.2.3-1: Two antenna port reference sensitivity QPSK PREFSENS for FDD bands** + +| Operating band / SCS / Channel bandwidth | | | | | | | | | | | | +|------------------------------------------|---------|-------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------| +| Operating Band | SCS kHz | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 35 MHz (dBm) | 40 MHz (dBm) | 45 MHz (dBm) | 50 MHz (dBm) | +| n256 | 15 | -99.5 | -96.3 | -94.5 | -93.8 | | | | | | | +| | 30 | | -96.6 | -94.6 | -94.0 | | | | | | | +| | 60 | | -97.0 | -94.9 | -94.2 | | | | | | | +| n255 | 15 | -100.0 | -96.8 | -95.0 | -93.8 | | | | | | | +| | 30 | | -97.1 | -95.1 | -94.0 | | | | | | | +| | 60 | | -97.5 | -95.4 | -94.2 | | | | | | | + +NOTE : The transmitter shall be set to $P_{UMAX}$ as defined in clause 6.2.4 of 3GPP TS 38.101-1 [5]. + +The reference receiver sensitivity (REFSENS) requirement specified in Table 7.3.2.3-1 shall be met with uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.3-2. + +less than or equal to that specified in Table 7.3.2.3-2. + +**Table 7.3.2.3-2: Uplink configuration for reference sensitivity** + +| Operating band / SCS (kHz) / Channel bandwidth (MHz) / Duplex mode | | | | | | | +|--------------------------------------------------------------------|-----|----|----|----|------|-------------| +| Operating Band | SCS | 5 | 10 | 15 | 20 | Duplex Mode | +| n256 | 15 | 25 | 50 | 75 | 100 | FDD | +| | 30 | | 24 | 36 | 50 | | +| | 60 | | 10 | 18 | 24 | | +| n255 | 15 | 25 | 50 | 75 | [75] | FDD | +| | 30 | | 24 | 36 | [36] | | +| | 60 | | 10 | 18 | [18] | | + +NOTE: UL resource blocks shall be located as close as possible to the downlink operating band but confined within the transmission bandwidth configuration for the channel bandwidth (Table 5.3.2-1 of 3GPP TS 38.101-1 [5]). + +The minimum requirements specified in Table 7.3.2.3-1 shall be verified with the network signalling value NS\_01 (Table 6.2.3.1-1 of 3GPP TS 38.101-1 [5]) configured. + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.3.2. + +### 7.3.2.4 Test description + +#### 7.3.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, and channel bandwidths based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each channel bandwidth, and are shown in Table 7.3.2.4.1-1, Table 7.3.2.4.1-2, and Table 7.3.2.4.1-3. The details of the uplink reference measurement channels (RMCs) are specified in Annex A.2.2 of TS 38.521-1 [2]. Configurations of PDSCH and PDCCH before measurement are specified in Annex [to be updated]. + +Table 7.3.2.4.1-1: Test Configuration Table + +| Initial Conditions | | | | | +|--------------------------------------------------------------------------|------------------------------------|------------------|----------------------|------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Low range, Mid range, High range | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Lowest, Mid, Highest | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | | +| Test Parameters | | | | | +| Test ID | Downlink Configuration | | Uplink Configuration | | +| | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM
QPSK | Full RB (NOTE 1) | DFT-s-OFDM QPSK | REFSENS (NOTE 2) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2. +NOTE 2: REFSENS refers to Table 7.3.2.4.1-3 which defines uplink RB configuration and start RB location for each SCS, channel BW and NR band. + +Table 7.3.2.4.1-2: Downlink Configuration of each RB allocation + +| Channel Bandwidth | SCS(kHz) | LCRBmax | Outer RB allocation / Normal RB allocation | +|-------------------|----------|---------|--------------------------------------------| +| 5MHz | 15 | 25 | 25@0 | +| | 30 | 11 | 11@0 | +| | 60 | N/A | N/A | +| 10MHz | 15 | 52 | 52@0 | +| | 30 | 24 | 24@0 | +| | 60 | 11 | 11@0 | +| 15MHz | 15 | 79 | 79@0 | +| | 30 | 38 | 38@0 | +| | 60 | 18 | 18@0 | +| 20MHz | 15 | 106 | 106@0 | +| | 30 | 51 | 51@0 | +| | 60 | 24 | 24@0 | + +NOTE: Test Channel Bandwidths are checked separately for each NR band, the applicable channel bandwidths are specified in Table 5.3.5-1. + +Table 7.3.2.4.1-3: Uplink configuration for reference sensitivity, LCRB @ RBstart format + +| Operating Band | SCS kHz | 5 MHz | 10 MHz | 15 MHz | 20 MHz | +|----------------|---------|-------------------|--------|--------|--------| +| n256 | 15 | 25@0 | 50@0 | 75@0 | 100@0 | +| | 30 | | 24@0 | 36@0 | 50@0 | +| | 60 | | 10@0 | 18@0 | 24@0 | +| n255 | 15 | 25@0 | 50@0 | 75@0 | [75@0] | +| | 30 | 10@1 1 | 24@0 | 36@0 | [36@0] | +| | 60 | | 10@0 | 18@0 | [18@0] | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 12 subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1 and C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL and Reference Measurement Channel is set according to Table 7.3.2.4.1-1, Table 7.3.2.4.1-2, and Table 7.3.2.4.1-3. +5. Propagation conditions are set according to Annex B.0. in TS 38.521-1 [2]. + +6. Ensure the UE is in State RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 7.3.2.4.3. + +#### 7.3.2.4.2 Test procedure. + +1. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +2. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508 [12] table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +3. Deactivate UE prediction of satellite trajectory by any preconfigured means. +4. SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.3.2.4.1-1. The SS sends downlink MAC padding bits on the DL RMC. +5. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Tables 7.3.2.4.1-1. Since the UE has no payload data to send, the UE transmits uplink MAC padding bits on the UL RMC. +6. Set the Downlink signal level to the appropriate REFSSENS value defined in Table 7.3.2.5-1 if 2Rx antennas connected or Table 7.3.2.5-2 if 4Rx antennas connected. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE to ensure the UE transmits PUMAX level for at least the duration of the Throughput measurement. +7. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex [to be updated]. + +#### 7.3.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents are according to TS 38.508-1[12] subclause 4.6 with the following exceptions for each network signalling value. + +SIB19 message contents according to TS 38.508-1 [12] clause 5.6.2.1 + +##### 7.3.2.4.3.1 Message contents exceptions (network signalled value "NS\_01") + +Message contents according to TS 38.508-1 [12] subclause 4.6 can be used without exceptions. + +#### 7.3.2.5 Test requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex [to be updated] with reference receive power level specified in Tables 7.3.2.5-1 and parameters specified Tables 7.3.2.4.1-1, Tables 7.3.2.4.1-2 and Tables 7.3.2.4.1-3. + +Table 7.3.2.5-1: Two antenna port Reference sensitivity QPSK $P_{\text{REFSENS}}$ for FDD bands for PC3 + +| Operating Band | SCS kHz | Operating band / SCS / Channel bandwidth / Duplex-mode | | | | | | | | | | Duplex Mode | +|----------------|---------|--------------------------------------------------------|------------------------|------------------------|------------------------|--------------|--------------|--------------|--------------|--------------|--------------|-------------| +| | | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 35 MHz (dBm) | 40 MHz (dBm) | 45 MHz (dBm) | 50 MHz (dBm) | | +| n256 | 15 | -99.5 +TT | -96.3 +TT | -94.5 +TT | -93.8 +TT | | | | | | | FDD | +| | 30 | | -96.6 +TT | -94.6 +TT | -94.0 +TT | | | | | | | | +| | 60 | | -97.0 +TT | -94.9 +TT | -94.2 +TT | | | | | | | | +| n255 | 15 | -100.0 +TT | -96.8 +TT | -95.0 +TT | -93.8 +TT | | | | | | | FDD | +| | 30 | | -97.1 +TT | -95.1 +TT | -94.0 +TT | | | | | | | | +| | 60 | | -97.5 +TT | -95.4 +TT | -94.2 +TT | | | | | | | | +| | 30 | | -96.6 3 +TT | -94.6 3 +TT | -93.5 3 +TT | | | | | | | | +| | 60 | | -97.0 3 +TT | -94.9 3 +TT | -93.7 3 +TT | | | | | | | | + +NOTE 1: Four Rx antenna ports shall be the baseline for this operating band except for two Rx vehicular UE. Four Rx antenna ports for RedCap UE is not supported for this operating band. + +NOTE 2: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in subclause 6.2.4 + +NOTE 3: 3 indicates that the requirement is modified by -0.5 dB when the assigned NR channel bandwidth is confined within 1475.9-1510.9 MHz. + +NOTE 4: Void + +NOTE 5: Void + +NOTE 6: TT for each frequency and channel bandwidth is specified in Table 7.3.2.5-3. + +**Table 7.3.2.5-2: Test Tolerance (TT) for RX sensitivity level** + +| $f \leq 3.0\text{GHz}$ | $3.0\text{GHz} < f \leq 6.0\text{ GHz}$ | +|------------------------|-----------------------------------------| +| [X dB] | [Y dB] | + +## 7.4 Maximum input level + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access are to be updated +- Message exceptions specific to satellite access is to be updated + +### 7.4.1 Test purpose + +Maximum input level tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, under conditions of high signal level, ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area near to a g-NodeB. + +### 7.4.2 Test applicability + +This test case applies to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 7.4.3 Minimum conformance requirements + +Maximum input level is defined as the maximum mean power received at the UE antenna port, at which the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel. The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.3.2 and A.3.3 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.4.3-1. + +**Table 7.4.3-1: Maximum input level** + +| Rx Parameter | Units | Channel bandwidth (MHz) | +|------------------------------------------------------------|-------|-------------------------| +| | | 5, 10, 15, 20 | +| Power in Transmission Bandwidth Configuration 3 | dBm | -40 2 | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{\text{CMAX\_L,f,c}}$ at the minimum uplink configuration specified in Table 7.3.2-2 with $P_{\text{CMAX\_L,f,c}}$ as defined in clause 6.2.4. + +NOTE 2: Reference measurement channel is A.3.2.3 or A.3.3.3 for 64 QAM. + +NOTE 3: Power in transmission bandwidth configuration value is rounded to the nearest 0.5dB value. + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.4. + +### 7.4.4 Test description + +#### 7.4.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in table 7.4.4.1-1. The details of the uplink and downlink reference measurement channels (RMC) are specified in Annexes A.2 and A.3. The details of the OCNG patterns used are specified in Annex A.5. Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 7.4.4.1-1: Test Configuration Table** + +| Initial Conditions | | | | +|-----------------------------------------------------------------------------------------------|----------------------|-----------------------------|---------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Mid range | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Lowest, Mid, Highest | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | +| Test Parameters for Channel Bandwidths | | | | +| Downlink Configuration | | Uplink Configuration | | +| Modulation | RB allocation | Modulation | RB allocation | +| CP-OFDM 64 QAM | NOTE 1 | DFT-s-OFDM QPSK | NOTE 2 | +| NOTE 1: The specific configuration of downlink RB allocation is defined in Table 7.3.2.4.1-2. | | | | +| NOTE 2: The specific configuration of uplink RB allocation is defined in Table 7.3.2.4.1-3. | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.1.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to clauses C.0, C.1, C.2, and C.3.1, and uplink signals according to clauses G.0, G.1, G.2, and G.3.1. +4. The DL and UL Reference Measurement Channels are set according to Table 7.4.4.1-1. +5. Propagation conditions are set according to Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 7.4.4.3. + +#### 7.4.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.4.4.1-1. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Tables 7.4.4.1-1. Since the UE has no payload data and no loopback data to send, the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.4.5-1. Send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.4.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + +- Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [5], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified for test case 6.3.4.3 in Table F.1.2-1. + - For UEs supporting Tx diversity, the transmit power is measured as the sum of the output power from both UE antenna connectors. +4. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2 +- NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F.4.3. + +#### 7.4.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED. + +### 7.4.5 Test requirement + +The throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 and A.3.3 with parameters specified in Tables 7.4.5-1. + +**Table 7.4.5-1: Maximum input level** + +| Rx Parameter | Units | Channel bandwidth (MHz) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------| +| | | 5, 10, 15, 20 | +| Power in Transmission Bandwidth Configuration | dBm | $-40^2$ - TT | +| NOTE 1: The transmitter shall be set to 4 dB below $P_{\text{CMAX\_L,f,c}}$ at the minimum uplink configuration specified in Table 7.3.2-3 with $P_{\text{CMAX\_L,f,c}}$ as defined in clause 6.2.4. | | | +| NOTE 2: Reference measurement channel is A.3.2.3 or A.3.3.3 for 64 QAM. | | | + +**Table 7.4.5-2: Test Tolerance (Maximum input level)** + +| | +|------------------------| +| $f \leq 3.0\text{GHz}$ | +| 0.7 dB | + +## 7.5 Adjacent channel selectivity + +### 7.5.1 Test purpose + +Adjacent channel selectivity (ACS) is a measure of a receiver's ability to receive an NR signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent channel(s). + +### 7.5.2 Test applicability + +This test case applies to all types of NR UE release 17 and forward that support satellite access operation. + +### 7.5.3 Minimum conformance requirements + +In Release 17, only frequency bands below 2.7GHz are considered. The NR satellite UE shall fulfil the minimum requirements specified in Table 7.5.3-1 for NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz. These requirements apply for all values of an adjacent channel interferer in case 1 and for any SCS specified for the channel bandwidth of the wanted signal. The lower and upper range of test parameters are chosen as in Table 7.5.3-2 and Table 7.5.3-3 for verification of the requirements specified in Table 7.5.3-1. For these test parameters, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1/A.5.2.1). + +**Table 7.5.3-1: ACS for NR satellite bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|--------------|-------|-------------------------|----|----| +| | | 5, 10 | 15 | 20 | +| ACS | dB | 33 | 30 | 27 | + +**Table 7.5.3-2: Test parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, case 1** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|-----------------------------------------------|-------|----------------------------------------------------------|-------------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration | dBm | REFSENS + 14 dB | | | +| $P_{interferer}^4$ | dBm | REFSENS + 45.5 dB | REFSENS + 42.5 dB | REFSENS + 39.5 | +| $BW_{interferer}$ | MHz | 5 | | | +| $F_{interferer} \text{ (offset)}^2$ | MHz | $BW_{Channel}/2 + 2.5$
/
$-(BW_{Channel}/2 + 2.5)$ | | | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: The absolute value of the interferer offset $F_{interferer} \text{ (offset)}$ shall be further adjusted to $(\lceil |F_{interferer}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 3: The interferer consists of the NR interferer RMC specified in 3GPP TS 38.101-1 [5] Annexes A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1. + +NOTE 4: $P_{interferer}$ shall be rounded to the next higher 0.5dB value. + +**Table 7.5.3-3: Test parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, case 2** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|-----------------------------------------------|-------|----------------------------------------------------------|-------|-------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration | dBm | -71.5 | -68.5 | -65.5 | +| $P_{interferer}$ | dBm | -40 | | | +| $BW_{interferer}$ | MHz | 5 | | | +| $F_{interferer} \text{ (offset)}$ | MHz | $BW_{Channel}/2 + 2.5$
/
$-(BW_{Channel}/2 + 2.5)$ | | | + +NOTE 1: The transmitter shall be set to 24 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: The absolute value of the interferer offset $F_{interferer} \text{ (offset)}$ shall be further adjusted to $(\lceil |F_{interferer}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 3: The interferer consists of the NR interferer RMC specified in 3GPP TS 38.101-1 [5] Annexes A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1. + +NOTE 4: $P_{interferer}$ shall be rounded to the next higher 0.5dB value. + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.5. + +## 7.5.4 Test description + +### 7.5.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in Table 7.5.4.1-1. The details of the uplink and downlink reference measurement channels (RMC) are specified in Annexes A.2 and A.3. Configuration of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 7.5.4.1-1: Test Configuration Table** + +| Default Conditions | | | | | +|---------------------------------------------------------------------------------------------|-------------------------------|----------------------|-----------------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal | | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Mid range | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Lowest, Mid, Highest | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | | +| Test Parameters | | | | | +| | Downlink Configuration | | Uplink Configuration | | +| Test ID | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM QPSK | NOTE 1 | DFT-s-OFDM QPSK | NOTE 1 | +| NOTE 1: The specific configuration of uplink and downlink are defined in Table 7.3.2.4.1-1. | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, in Figure A.3.1.4.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to clauses C.1, C.2, C.3.1, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.1. +4. The DL and UL Reference Measurement channels are set according to Table 7.5.4.1-1. +5. Propagation conditions are set according to Annex B.0. +6. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +7. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508 [12] Table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and Table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +8. Deactivate UE prediction of satellite trajectory by any preconfigured means. +9. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity *NR*, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 7.5.4.3. + +### 7.5.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.5.4.1-1. The SS sends downlink MAC padding bits on the DL RMC. + +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.5.4.1-1. Since the UL has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. +3. Set the Downlink signal level to the value as defined in Table 7.5.5-2 as appropriate (Case 1). Send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.5.5-2 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. + - Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [5], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified in Table F.1.2-1. +- For UEs supporting Tx diversity, the transmit power is measured as the sum of the output power from both UE antenna connectors. +4. Set the Interferer signal level to the value as defined in Table 7.5.5-2 as appropriate (Case 1) and frequency below the wanted signal, using a modulated interferer bandwidth as defined in Annex D. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H. +6. Repeat steps from 3 to 5, using an interfering signal above the wanted signal in Case 1 at step 4. +7. Set the Downlink signal level to the value as defined in Table 7.5.5-3 as appropriate (Case 2). Send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.5.5-3 for at least the duration of the Throughput measurement, where MU and Uplink power control window size are defined above. +8. Set the Interferer signal level to the value as defined in Table 7.5.5-3 as appropriate (Case 2) and frequency below the wanted signal, using a modulated interferer bandwidth as defined in Annex D. +9. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H. +10. Repeat steps from 7 to 9, using an interfering signal above the wanted signal in Case 2 at step 8. +11. Repeat for applicable channel bandwidths and operating band combinations in both Case 1 and Case 2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F.4.3. + +#### 7.5.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents are according to TS 38.508-1[12] subclause 4.6 with the following exceptions for each network signalling value. + +SIB19 message contents according to TS 38.508-1 [12] clause 5.6.2.1. + +#### 7.5.5 Test requirement + +For NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, the throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in [Annexes + +A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1 with parameters specified in Tables 7.5.5-2 and 7.5.5-3. + +**Table 7.5.5-1: ACS for NR satellite bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|--------------|-------|-------------------------|----|----| +| | | 5, 10 | 15 | 20 | +| ACS | dB | 33 | 30 | 27 | + +**Table 7.5.5-2: Test parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, case 1** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|-----------------------------------------------|-------|----------------------------------------------------------|-------------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration | dBm | REFSENS + 14 dB | | | +| $P_{interferer}^4$ | dBm | REFSENS + 45.5 dB | REFSENS + 42.5 dB | REFSENS + 39.5 | +| $BW_{interferer}$ | MHz | 5 | | | +| $F_{interferer} \text{ (offset)}^2$ | MHz | $BW_{Channel}/2 + 2.5$
/
$-(BW_{Channel}/2 + 2.5)$ | | | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{MAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{MAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: The absolute value of the interferer offset $F_{interferer} \text{ (offset)}$ shall be further adjusted to $(\lceil |F_{interferer}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 3: The interferer consists of the NR interferer RMC specified in 3GPP TS 38.101-1 [5] clause A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1. + +NOTE 4: $P_{interferer}$ shall be rounded to the next higher 0.5dB value. + +**Table 7.5.5-3: Test parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, case 2** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|-----------------------------------------------|-------|----------------------------------------------------------|-------|-------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration | dBm | -71.5 | -68.5 | -65.5 | +| $P_{interferer}$ | dBm | -40 | | | +| $BW_{interferer}$ | MHz | 5 | | | +| $F_{interferer} \text{ (offset)}$ | MHz | $BW_{Channel}/2 + 2.5$
/
$-(BW_{Channel}/2 + 2.5)$ | | | + +NOTE 1: The transmitter shall be set to 24 dB below $P_{MAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{MAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: The absolute value of the interferer offset $F_{interferer} \text{ (offset)}$ shall be further adjusted to $(\lceil |F_{interferer}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 3: The interferer consists of the NR interferer RMC specified in 3GPP TS 38.101-1 [5] clause A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] clause A.5.1.1. + +NOTE 4: $P_{interferer}$ shall be rounded to the next higher 0.5 dB value. + +## 7.6 Blocking characteristics + +### 7.6.1 General + +The blocking characteristic is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the + +adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occurs. + +## 7.6.2 In-band blocking + +[to be updated] + +## 7.6.3 Out of Band Blocking + +Editor's Note: This clause is incomplete. The following aspects are either missing or not yet determined: + +- Addition to applicability spec is pending +- Initial condition and call setup procedure to support NR satellite access is to be updated +- Message exceptions specific to satellite access is to be updated +- Test Points analysis is to be updated +- Test configuration is to be updated +- Annex F MU/TT is to be updated + +### 7.6.3.1 Test purpose + +Out-of-band band blocking is defined for an unwanted CW interfering signal falling outside a frequency range 15 MHz below or above the UE receive band, with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, or falling outside a frequency range up to $3 \cdot BW_{Channel}$ below or from $3 \cdot BW_{Channel}$ above the UE receive band, with $F_{DL\_low} \geq 3,300$ MHz and $F_{UL\_low} \geq 3,300$ MHz, at which a given average throughput shall meet or exceed the requirement for the specified measurement channels. + +### 7.6.3.2 Test applicability + +The requirements of this test apply to all types of NR Power Class 3 UE release 17 and forward that support satellite access operation. + +### 7.6.3.3 Minimum conformance requirements + +For NR satellite bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz out-of-band band blocking is defined for an unwanted CW interfering signal falling outside a frequency range 15 MHz below or above the UE receive band. + +The throughput of the wanted signal shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] clauses A.2.2, A.3.2 and A.3.3 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in clauses A.5.1.1/A.5.2.1) with parameters specified in Table 7.6.3-1 and Table 7.6.3-2. The relative throughput requirement shall be met for any SCS specified for the channel bandwidth of the wanted signal. + +**Table 7.6.3-1: Out-of-band blocking parameters for NR satellite bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------|----------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration 2 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | REFSENS + 9 dB | +| NOTE 1: The transmitter shall be set to 4 dB below $P_{MAX\_L,fc}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{MAX\_L,fc}$ defined in clause 6.2.4. | | | | | +| NOTE 2: Power in transmission bandwidth configuration shall be rounded to the next higher 0.5dB value. | | | | | + +**Table 7.6.3-2: Out of-band blocking for NR satellite bands with +FDL\_high < 2,700 MHz and FUL\_high < 2,700 MHz** + +| Operating Band | Parameter | Unit | Range 1 | Range 2 | Range 3 | +|-------------------|------------------------------|------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| | P interferer | dBm | -44 | -30 | -15 | +| n255 | F interferer (CW) | MHz | -60 < f - F DL_low < -15
or
15 < f - F DL_high < 60 | -85 < f - F DL_low ≤ -60
or
60 ≤ f - F DL_high < 85 | 1 ≤ f ≤ F DL_low - 85
or
F DL_high + 85 ≤ f ≤ 12750 | +| n256 1 | F interferer (CW) | MHz | -100 < f - F DL_low < -15
or
15 < f - F DL_high < 60 | -145 < f - F DL_low ≤ -100
or
60 ≤ f - F DL_high < 85 | 1 ≤ f ≤ F DL_low - 145
or
F DL_high + 85 ≤ f ≤ 12750 | + +NOTE 1: Band n256 lower frequency ranges are modified to enable specific implementations void +NOTE 2: void +NOTE 3: void +NOTE 4: void + +For interferer frequencies across ranges 1, 2 and 3 in Table 7.6.3-1, a maximum of + +$$\lfloor \max \{24.6 \cdot \lceil n \cdot N_{RB} / 6 \rceil\} / \min \{\lceil n \cdot N_{RB} / 10 \rceil, 5\} \rfloor$$ + +exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a step size of $\min(\lceil BW_{channel} / 2 \rceil, 5)$ MHz with $N_{RB}$ the number of resource blocks in the downlink transmission bandwidth configuration, $BW_{Channel}$ the bandwidth of the frequency channel in MHz and $n = 1, 2, 3$ for SCS = 15, 30, 60 kHz, respectively. For these exceptions, the requirements in clause 7.7 apply. + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.6.3. + +### 7.6.3.4 Test description + +#### 7.6.3.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, channel bandwidths and sub-carrier spacing based on NR operating bands specified in table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of test channel bandwidth and sub-carrier spacing, and are shown in Table 6.2.2.4.1-1. The details of the uplink reference measurement channels (RMCs) are specified in TS 38.521-1 [2] clause A.2. Configurations of PDSCH and PDCCH before measurement are specified in TS 38.521-1 [2] Annex C.2. + +**Table 7.6.3.4.1-1: Test Configuration Table for power class 3** + +**[to be updated]** + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, Figure A.3.1.2.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to TS 38.521-1 [2] clauses C.0, C.1, C.2, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.0. +4. The UL Reference Measurement Channel is set according to Table 6.2.2.4.1-1. +5. Propagation conditions are set according to TS 38.521-1 [2] Annex B.0. +6. UE location according to TS 38.508-1 [12] clause [to be updated] is provided to the UE through AT commands or any other preconfigured means. + +7. Test equipment shall emulate Zero Doppler conditions in service link and Common TA delay according to SIB19 configuration in TS 38.508-1 [12]. +8. Ensure the UE is in State [to be updated] with generic procedure parameters [to be updated], Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 6.2.2.4.3. + +#### 7.6.3.4.2 Test procedure + +[to be updated] + +#### 7.6.3.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] subclause 4.6 and 5.4 with the following exceptions: + +[to be updated] + +#### 7.6.3.5 Test requirement + +[to be updated] + +### 7.6.4 Narrow band blocking + +[to be updated] + +## 7.7 Spurious response + +### 7.7.1 Test Purpose + +Spurious response is a measure of the ability of the receiver to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency for which a response is obtained, i.e. for which the out-of-band blocking limit as specified in subclause 7.6.3 is not met. + +The lack of the spurious response ability decreases the coverage area when other unwanted interfering signal exists at any other frequency. + +### 7.7.2 Test Applicability + +This test case applies to all types of NR UE release 17 and forward that support satellite access operation. + +### 7.7.3 Minimum Conformance Requirements + +The throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1) with parameters for the wanted signal as specified in Table 7.7.3-1 for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz and for the interferer as specified in Table 7.7.3-2. The relative throughput requirement shall be met for any SCS specified for the channel bandwidth of the wanted signal. + +**Table 7.7.3-1: Spurious response parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|------------------------------------------------------------|-------|-------------------------|----------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration 2 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | REFSENS + 9 dB | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{CMAX\_L,fc}$ at the minimum UL configuration specified in Table 7.3.2.3-3 with $P_{CMAX\_L,fc}$ defined in clause 6.2.4. + +NOTE 2: Power in transmission bandwidth configuration value is rounded to the next higher 0.5dB value. + +**Table 7.7.3-2: Spurious response** + +| Parameter | Unit | Level | +|-----------------------|------|-------------------------------| +| $P_{Interferer}$ (CW) | dBm | -44 | +| $F_{Interferer}$ | MHz | Spurious response frequencies | + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.7. + +## 7.7.4 Test Description + +### 7.7.4.1 Initial Conditions + +The initial conditions shall be the same as in clause 7.6.3.4.1 in order to test spurious responses obtained in clause 7.6.3 under the same conditions. + +### 7.7.4.2 Test Procedure + +- SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.6.3.4.1-1. The SS sends downlink MAC padding bits on the DL RMC. +- SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.6.3.4.1-1. Since the UE has no payload and no loopback data to send, the UE transmits uplink MAC padding bits on the UL RMC. +- Set the parameters of the CW signal generator for an interfering signal according to Table 7.7.5-2. The spurious frequencies are taken from records in the final step of test procedures in clause 7.6.3.4.2. +- Set the downlink signal level according to the Table 7.7.5-1. Send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as $-(MU + \text{Uplink power control window size})$ dB of the target power level in Table 7.7.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency $f$ and the channel bandwidth BW + - Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [5], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified for test case 6.3.4.3 in Table F.1.2-1. + - For UEs supporting Tx diversity, the transmit power is measured as the sum of the output power from both UE antenna connectors. +- For the spurious frequency, measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F.4.3. + +### 7.7.4.3 Message Contents + +Message contents are according to TS 38.508-1 [12] clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents are according to TS 38.508-1[12] subclause 4.6 with the following exceptions for each network signalling value. + +SIB19 message contents according to TS 38.508-1 [12] clause 5.6.2.1. Message contents are according to TS 38.508-1 [12] clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents are according to TS 38.508-1[12] subclause 4.6 with the following exceptions for each network signalling value. + +SIB19 message contents according to TS 38.508-1 [12] clause 5.6.2.1. + +## 7.7.5 Test Requirement + +The throughput measurement derived in test procedure shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 with parameters for the wanted signal as specified in Table 7.7.5-1 for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz and for the interferer as specified in Table 7.7.5-2. + +**Table 7.7.5-1: Spurious response parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|------------------------------------------------------------|-------|-------------------------|----------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration 2 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | REFSENS + 9 dB | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{CMAX\_L,fc}$ at the minimum UL configuration specified in Table 7.3.2.3-3 with $P_{CMAX\_L,fc}$ defined in clause 6.2.4. + +NOTE 2: Power in transmission bandwidth configuration value is rounded to the next higher 0.5dB value. + +**Table 7.7.5-2: Spurious response** + +| Parameter | Unit | Level | +|-----------------------|------|-------------------------------| +| $P_{Interferer}$ (CW) | dBm | -44 | +| $F_{Interferer}$ | MHz | Spurious response frequencies | + +## 7.8 Intermodulation characteristics + +### 7.8.1 General + +Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal. + +## 7.8.2 Wide band Intermodulation + +### 7.8.2.1 Test purpose + +Intermodulation response tests the UE's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise. + +A UE unable to meet the throughput requirement under these conditions will decrease the coverage area when two or more interfering signals exist which have a specific frequency relationship to the wanted signal. + +### 7.8.2.2 Test applicability + +This test case applies to all types of NR UE release 17 and forward that support satellite access operation. + +### 7.8.2.3 Minimum conformance requirements + +The wide band intermodulation requirement is defined using a CW carrier and modulated NR signal as interferer 1 and interferer 2 respectively. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1) with parameters specified in Table 7.8.2.3-1 for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz. The relative throughput requirement shall be met for any SCS specified for the channel bandwidth of the wanted signal. + +**Table 7.8.2.3-1: Wide band intermodulation parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| Rx parameter | Units | Channel bandwidth (MHz) | | | +|--------------------------------------------------------------------|-------|---------------------------------------------------------|----------------|---------------------------------------------------| +| | | 5, 10 | 15 | 20 | +| $P_w$ in Transmission Bandwidth Configuration, per CC 5 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | $REFSENS + (9 + 10\log_{10}(BW_{Channel}/20))$ dB | +| $P_{Interferer 1}$ (CW) | dBm | -46 | | | +| $P_{Interferer 2}$ (Modulated) | dBm | -46 | | | +| $BW_{Interferer 2}$ | MHz | 5 | | | +| $F_{Interferer 1}$ (Offset) | MHz | $-BW_{channel}/2 - 7.5$
/
$+BW_{channel}/2 + 7.5$ | | | +| $F_{Interferer 2}$ (Offset) | MHz | $2*F_{Interferer 1}$ | | | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{MAX\_L,f,c}$ at the minimum UL configuration specified in Table 7.3.2.3-3 with $P_{MAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: Reference measurement channel is specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1). + +NOTE 3: The modulated interferer consists of the Reference measurement channel specified in 3GPP TS 38.101-1 [5] Annex A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1 and 15 kHz SCS. + +NOTE 4: The $F_{Interferer 1}$ (offset) is the frequency separation of the centre frequency of the carrier closest to the interferer and the centre frequency of the CW interferer and $F_{Interferer 2}$ (offset) is the frequency separation of the centre frequency of the carrier closest to the interferer and the centre frequency of the modulated interferer. + +NOTE 5: $10\log_{10}(x)$ is rounded to the next higher 0.5dB value. + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.8. + +## 7.8.2.4 Test description + +### 7.8.2.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in Table 7.8.2.4.1-1. The details of the uplink and downlink reference measurement channels (RMC) are specified in Annexes A.2 and A.3. Configuration of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 7.8.2.4.1-1: Test Configuration Table** + +| Default Conditions | | | | | +|---------------------------------------------------------------------------------------------|-------------------------------|----------------------|-----------------------------|----------------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal | | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Mid range | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Lowest, Mid, Highest | | | | +| Test SCS as specified in Table 5.3.5-1 | Highest | | | | +| Test Parameters | | | | | +| | Downlink Configuration | | Uplink Configuration | | +| Test ID | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM QPSK | NOTE 1 | DFT-s-OFDM QPSK | NOTE 1 | +| NOTE 1: The specific configuration of uplink and downlink are defined in Table 7.3.2.4.1-1. | | | | | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, in Figure A.3.1.4.3 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to clauses C.0, C.1, C.2, C.3.1, and uplink signals according to TS 38.521-1 [2] clauses G.0, G.1, G.2, G.3.1. +4. The DL and UL Reference Measurement channels are set according to Table 7.8.2.4.1-1. +5. Propagation conditions are set according to Annex B.0. +6. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +7. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508 [12] Table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and Table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +8. Deactivate UE prediction of satellite trajectory by any preconfigured means. +9. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity NR, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 7.8.2.4.3. + +### 7.8.2.4.2 Test procedure + +1. SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Table 7.8.2.4.1-1. The SS sends downlink MAC padding bits on the DL RMC. +2. SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0\_1 for C\_RNTI to schedule the UL RMC according to Table 7.8.2.4.1-1. Since the UE has no payload and no loopback data to send the UE sends uplink MAC padding bits on the UL RMC. + +3. Set the Downlink signal level to the value as defined in Table 7.8.2.5-1. Send uplink power control commands to the UE using 1dB power step size to ensure that the UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 7.8.2.5-1 for at least the duration of the Throughput measurement, where: + - MU is the test system uplink power measurement uncertainty and is specified in Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW + - Uplink power control window size = 1dB (UE power step size) + 0.7dB (UE power step tolerance) + (Test system relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [5], Table 6.3.4.3-1 and is 0.7dB for 1dB power step size, and the Test system relative power measurement uncertainty is specified for test case 6.3.4.3 in Table F.1.2-1. + - For UEs supporting Tx diversity, the transmit power is measured as the sum of the output power from both UE antenna connectors. +4. Set the Interfering signal levels to the values as defined in Table 7.8.2.5-1 and frequency below the wanted signal. +5. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex H.2. +6. Repeat steps from 3 to 5, using an interfering signal above the wanted signal at step 4. + +NOTE: The purpose of the Uplink power control window is to ensure that the actual UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual UE Uplink power window is illustrated in Annex F.4.3. + +#### 7.8.2.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents are according to TS 38.508-1[12] subclause 4.6 with the following exceptions for each network signalling value. + +SIB19 message contents according to TS 38.508-1 [12] clause 5.6.2.1. + +#### 7.8.2.5 Test requirement + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.3.2 with parameters specified in Table 7.8.2.5-1 for the specified wanted signal mean power in the presence of two interfering signals. + +**Table 7.8.2.5-1: Wide band intermodulation parameters for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| Rx parameter | Units | Channel bandwidth (MHz) | | | +|--------------------------------------------------------------------|-------|---------------------------------------------------------|----------------|---------------------------------------------------| +| | | 5, 10 | 15 | 20 | +| $P_w$ in Transmission Bandwidth Configuration, per CC 5 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | $REFSENS + (9 + 10\log_{10}(BW_{Channel}/20))$ dB | +| $P_{Interferer\ 1}$ (CW) | dBm | -46 | | | +| $P_{Interferer\ 2}$ (Modulated) | dBm | -46 | | | +| $BW_{Interferer\ 2}$ | MHz | 5 | | | +| $F_{Interferer\ 1}$ (Offset) | MHz | $-BW_{channel}/2 - 7.5$
/
$+BW_{channel}/2 + 7.5$ | | | +| $F_{Interferer\ 2}$ (Offset) | MHz | $2*F_{Interferer\ 1}$ | | | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in Table 7.3.2.3-3 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: Reference measurement channel is specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1). + +NOTE 3: The modulated interferer consists of the Reference measurement channel specified in 3GPP TS 38.101-1 [5] Annexes A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1 and 15 kHz SCS. + +NOTE 4: The $F_{Interferer\ 1}$ (offset) is the frequency separation of the centre frequency of the carrier closest to the interferer and the centre frequency of the CW interferer and $F_{Interferer\ 2}$ (offset) is the frequency separation of the centre frequency of the carrier closest to the interferer and the centre frequency of the modulated interferer. + +NOTE 5: $10\log_{10}(x)$ is rounded to the next higher 0.5dB value. + +## 7.9 Spurious emissions + +### 7.9.1 Test purpose + +The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the UE antenna connector. + +Test verifies the UE's spurious emissions meet the requirements described in clause 7.9.3. + +Excess spurious emissions increase the interference to other systems. + +### 7.9.2 Test applicability + +This test case applies to all types of NR UE release 17 and forward that support satellite access operation. + +### 7.9.3 Minimum conformance requirements + +The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the UE antenna connector. + +The power of any narrow band CW spurious emission shall not exceed the maximum level specified in Table 7.9.3-1 + +**Table 7.9.3-1: General receiver spurious emission requirements** + +| Frequency range | Measurement bandwidth | Maximum level | NOTE | +|-------------------------------|-----------------------|---------------|------| +| 30 MHz $\leq f < 1$ GHz | 100 kHz | -57 dBm | | +| 1 GHz $\leq f \leq 12.75$ GHz | 1 MHz | -47 dBm | | + +NOTE: Unused PDCCH resources are padded with resource element groups with power level given by PDCCH as defined in Annex C.3.1. + +The normative reference for this requirement is TS 38.101-5 [11] clause 7.9. + +## 7.9.4 Test description + +### 7.9.4.1 Initial conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1. All of these configurations shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, are shown in Table 7.9.4.1-1. The details of the uplink and downlink reference measurement channels (RMC) are specified in Annexes A.2 and A.3. Configuration of PDSCH and PDCCH before measurement are specified in Annex C.2. + +**Table 7.9.4.1-1: Test Configuration Table** + +| Default Conditions | | | | | +|--------------------------------------------------------------------------|----------------------------------|---------------|----------------------|---------------| +| Test Environment as specified in TS 38.508-1 [12] subclause 4.1 | Normal | | | | +| Test Frequencies as specified in TS 38.508-1 [12] subclause 4.3.1 | Low range, Mid range, High range | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [12] subclause 4.3.1 | Highest | | | | +| Test SCS as specified in Table 5.3.5-1 | Highest | | | | +| Test Parameters | | | | | +| | Downlink Configuration | | Uplink Configuration | | +| Test ID | Modulation | RB allocation | Modulation | RB allocation | +| 1 | N/A | 0 | N/A | 0 | + +1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, in Figure A.3.1.5.1 for TE diagram and clause A.3.2 for UE diagram. +2. The parameter settings for the cell are set up according to TS 38.508-1 [12] subclause 4.4.3. +3. Downlink signals are initially set up according to Annex C.1, C.2, C.3.1, and uplink signals according to TS 38.521-1 [2] Annex G.0, G.1, G.2, G.3.1. +4. The DL and UL Reference Measurement channels are set according to Table 7.9.4.1-1. +5. Propagation conditions are set according to [Annex B.0]. +6. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +7. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508 [12] Table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and Table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +8. Deactivate UE prediction of satellite trajectory by any preconfigured means. +9. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity NR, Connected without release *On*, Test Mode *On* and Test Loop Function *On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 7.9.4.3. + +### 7.9.4.2 Test procedure + +1. Sweep the spectrum analyser (or equivalent equipment) over a frequency range and measure the average power of spurious emission. +2. Repeat step 1 for all NR Rx antennas of the UE. + +### 7.9.4.3 Message contents + +Message contents are according to TS 38.508-1 [12] clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM\_PRECODER\_ENABLED for NR band. + +Message contents are according to TS 38.508-1[12] subclause 4.6 with the following exceptions for each network signalling value. + +SIB19 message contents according to TS 38.508-1 [12] clause 5.6.2.1. + +## 7.9.5 Test requirement + +The measured spurious emissions derived in step 1), shall not exceed the maximum level specified in Table 7.9.5-1. + +**Table 7.9.5-1: General receiver spurious emission requirements** + +| Frequency range | Measurement bandwidth | Maximum level | NOTE | +|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------|------| +| $30 \text{ MHz} \leq f < 1 \text{ GHz}$ | 100 kHz | -57 dBm | | +| $1 \text{ GHz} \leq f \leq 12.75 \text{ GHz}$ | 1 MHz | -47 dBm | | +| NOTE: | Unused PDCCH resources are padded with resource element groups with power level given by PDCCH as defined in Annex C.3.1. | | | + +# 8 Conducted performance requirements + +## 8.0 General + +[to be updated] + +### 8.1.1 Relationship between minimum requirements and test requirements + +TS 38.101-5 is a Single-RAT and interwork specification for NR UE, covering minimum performance requirements of both conducted and radiated requirements. Conformance to 38.101-5 is demonstrated by fulfilling the test requirements specified in the present document. + +The Minimum Requirements given in TS 38.101-5 make no allowances for measurement uncertainty (MU). The present document defines test tolerances (TT). These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in 38.101-4 to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +The measurement results returned by the test system are compared – without any modification – against the test requirements as defined by various level of "Shared Risk" principle as described below. + +- a) Core specification value is not relaxed by any relaxation value ( $TT=0$ ). For each single measurement, the probability of a borderline good UE being judged as FAIL equals the probability of a borderline bad UE being judged as PASS. + - Test tolerances equal to 0 ( $TT=0$ ) are considered in this specification. +- b) Core specification value is relaxed by a relaxation value ( $TT>0$ ). For each single measurement, the probability of a borderline bad UE being judged as PASS is greater than the probability of a borderline good UE being judged as FAIL. + +- Test tolerances lower than measurement uncertainty and greater than 0 ( $0 < TT < MU$ ) are considered in this specification. + - Test tolerances high up to measurement uncertainty ( $TT = MU$ ) are considered in this specification which is also known as "Never fail a good DUT" principle. +- c) Core specification value is tightened by a stringent value ( $TT < 0$ ). For each single measurement, the probability of a borderline good UE being judged as FAIL is greater than the probability of a borderline bad UE being judged as PASS. + +Test tolerances lower than 0 ( $TT < 0$ ) are not considered in this specification. + +The "Never fail a good DUT" and the "Shared Risk" principles are defined in Recommendation ITU-R M.1545. + +## 8.1.2 Applicability of minimum requirements + +The conducted minimum requirements specified in the present document shall be met in all applicable scenarios for FR1. The interwork minimum requirement specified in the present document shall be met in all applicable scenarios for NR interworking operation. + +All minimum performance requirements defined in Clause 8 are applicable to NR/5GC, EN-DC and NE-DC unless otherwise explicitly stated. + +Unless otherwise stated, all minimum performance requirements defined in Clause 8 are applicable to UE power class 3 only. + +## 8.1.3 Conducted requirements + +### 8.1.3.1 Introduction + +The requirements are defined for the following modes: + +- Mode 1: Conditions with external noise source + - Wanted signal with power level $E_s$ is transmitted. + - External white noise source with power spectral density $N_{oc}$ is used. + - $E_s$ and $N_{oc}$ levels are selected to achieve target SNR as described in Clause 8.1.3.3. + +### 8.1.3.2 Reference point + +The reference point for SNR, $E_s$ and $N_{oc}$ of DL signal is the UE antenna connector or connectors. + +### 8.1.3.3 SNR definition + +For Mode 1 conditions conducted UE demodulation and CSI requirements the SNR is defined as: + +$$SNR = \frac{\sum_{j=1}^{N_{RX}} E_s^{(j)}}{\sum_{j=1}^{N_{RX}} N_{oc}^{(j)}}$$ + +Where + +- $N_{RX}$ denotes the number of receiver antenna connectors and the superscript receiver antenna connector $j$ . +- The above SNR definition assumes that the REs are not precoded, and does not account for any gain which can be associated to the precoding operation. +- Unless otherwise stated, the SNR refers to the SSS wanted signal. +- The downlink SSS transmit power is defined as the linear average over the power contributions in [W] of all resource elements that carry the SSS within the operating system bandwidth. + +- The power ratio of other wanted signals to the SSS is defined in clause C.3.1. + +#### 8.1.3.4 Noc + +##### 8.1.3.4.1 Introduction + +This clause describes the Noc power level for Mode 1 conditions conducted testing of demodulation and CSI requirements. + +##### 8.1.3.4.2 Noc for NR operating bands in FR1 + +The Noc power spectrum density shall be larger or equal to the minimum Noc power level for each operating band supported by the UE as defined in clause 8.1.3.4.2.1. + +Unless otherwise stated, a fixed Noc power level of -145 dBm/Hz shall be used for all operating bands. + +##### 8.1.3.4.2.1 Derivation of Noc values for NR operating bands in FR1 + +The minimum Noc power level for an operating band, subcarrier spacing and channel bandwidth is derived based on the following equation: + +$$Noc_{Band\_X, SCS\_Y, CBW\_Z} = REFSENS_{Band\_X, SCS\_Y, CBW\_Z} - 10 \cdot \log_{10}(12 \cdot SCS\_Y \cdot nPRB) + D - SNR_{REFSENS} + \Delta_{thermal}$$ + +where + +- $REFSENS_{Band\_X, SCS\_Y, CBW\_Z}$ is the REFSENS value in dBm for Band X, SCS Y and CBW Z specified in Table 7.3.2-1 of TS 38.101-5 [11] +- 12 is the number of subcarriers in a PRB +- SCS Y is the subcarrier spacing associated with the REFSENS value +- nPRB is the maximum number of PRB for SCS Y and CBW Z associated with the REFSENS value, and is specified in Table 5.3.2-1 of TS 38.101-5 [11] +- D is diversity gain equal to 3 dB +- $SNR_{REFSENS} = -1$ dB is the SNR used for simulation of REFSENS +- $\Delta_{thermal}$ is the amount of dB that the wanted noise is set above UE thermal noise, giving a defined rise in total noise. $\Delta_{thermal} = 16$ dB, giving a rise in total noise of 0.1dB, regarded as insignificant. + +The calculated Noc value for the baseline of Band n256, 15 kHz SCS, 10 MHz CBW is -146.5 dBm/Hz. An allowance of 1.5 dB is made for future bands, giving an Noc power level of -145 dBm/Hz. + +## 8.2 Demodulation performance requirements + +### 8.2.1 General + +#### 8.2.1.1 Applicability of requirements + +##### 8.2.1.1.1 General + +The minimum performance requirements are applicable to all FR1 operating bands defined in clause 5.2. + +If same test is listed for different UE features/capabilities in Clause 8.2.1.1.2, then this test shall apply for UEs which support all corresponding UE features/capabilities. + +##### 8.2.1.1.2 Applicability of requirements for optional UE features + +The performance requirements in Table 8.2.1.1.2-1 shall apply for UEs which support optional UE features only. + +Table 8.2.1.1.2-1: Requirements applicability for optional UE features + +| UE feature/capability 13] | Test type | | Test list | Applicability notes | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| | | | | | +| NR NTN access (nonTerrestrialNetwork-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-1, Test 1-2, Test 1-3, Test 1-4) | | +| NR NTN scenario support (ntn-ScenarioSupport-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-1, Test 1-2, Test 1-3, Test 1-4) | The requirements apply only when ntn-ScenarioSupport-r17 is "ngso" or is not included. | +| Increasing the number of HARQ processes (max-HARQ-ProcessNumber-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-3) | | +| Disabled HARQ feedback for downlink transmission (harq-FeedbackDisabled-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-4) | | +| NOTE: For UE supporting NR NTN access (nonTerrestrialNetwork-r17), the requirements in TS 38.101-4 [6] also applies to UE according to applicability rules in TS 38.101-4 [6] Clause 5.1, 6.1, 7.1 and 8.1 | | | | | + +#### 8.2.1.2.0 PDSCH demodulation requirements + +The parameters specified in Table 8.2.1.2.0-1 are valid for all PDSCH tests unless otherwise stated. + +**Table 8.2.1.2.0-1: Common test parameters** + +| Parameter | Unit | Value | +|--------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDSCH transmission scheme | | Transmission scheme 1 | +| Carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 2) | RBs 0 | +| | Subcarrier spacing | kHz 15 | +| DL BWP configuration #1 | Cyclic prefix | Normal | +| | RB offset | RBs 0 | +| | Number of contiguous PRB | PRBs Maximum transmission bandwidth configuration as specified in clause 5.3.2 of TS 38.101-1 [5] for tested channel bandwidth and subcarrier spacing | +| Common serving cell parameters | Physical Cell ID | 0 | +| | SSB position in burst | First SSB in Slot #0 | +| | SSB periodicity | ms 20 | +| PDCCH configuration | Slots for PDCCH monitoring | Each slot | +| | Symbols with PDCCH | Symbols 0, 1 | +| | Number of PRBs in CORESET | Table 5.2-2 of 38.101-4 for tested channel bandwidth and subcarrier spacing | +| | Number of PDCCH candidates and aggregation levels | 1/AL8 | +| | CCE-to-REG mapping type | Non-interleaved | +| | DCI format | 1_1 | +| | TCI state | TCI state #1 | +| | PDCCH & PDCCH DMRS Precoding configuration | Single Panel Type I, Random per slot with equal probability of each applicable $i_1, i_2$ combination, and with REG bundling granularity for number of Tx larger than 1 | +| Cross carrier scheduling | | Not configured | +| CSI-RS for tracking | First subcarrier index in the PRB used for CSI-RS | $k_0=0$ for CSI-RS resource 1,2,3,4 | +| | First OFDM symbol in the PRB used for CSI-RS | $l_0 = 6$ for CSI-RS resource 1 and 3
$l_0 = 10$ for CSI-RS resource 2 and 4 | +| | Number of CSI-RS ports (X) | 1 for CSI-RS resource 1,2,3,4 | +| | CDM Type | 'No CDM' for CSI-RS resource 1,2,3,4 | +| | Density (p) | 3 for CSI-RS resource 1,2,3,4 | +| | CSI-RS periodicity | Slots 15 kHz SCS: 20 for CSI-RS resource 1,2,3,4 | +| | CSI-RS offset | Slots 15 kHz SCS:
10 for CSI-RS resource 1 and 2
11 for CSI-RS resource 3 and 4 | +| | Frequency Occupation | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| | QCL info | TCI state #0 | +| NZP CSI-RS for CSI acquisition | Row index (Note 3) | 3 for 2 CSI-RS ports and 5 for 4 CSI-RS ports | +| | First subcarrier index in the PRB used for CSI-RS | $k_0 = 0$ | +| | First OFDM symbol in the PRB used for CSI-RS | $l_0 = 12$ | +| | Number of CSI-RS ports (X) | Same as number of transmit antenna | +| | CDM Type | 'No CDM' for 1 transmit antenna
'FD-CDM2' for 2 and 4 transmit antenna | +| | Density (p) | 1 | +| | CSI-RS periodicity | Slots 15 kHz SCS: 20 | +| | CSI-RS offset | Slots 0 | +| | Frequency Occupation | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| | QCL info | TCI state #1 | +| ZP CSI-RS for CSI acquisition | Row index (Note 3) | 5 | +| | First subcarrier index in the PRB used for CSI-RS | $k_0 = 4$ | +| | First OFDM symbol in the PRB used for CSI-RS | $l_0 = 12$ | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Number of CSI-RS ports (X) | | 4 | +| | CDM Type | | 'FD-CDM2' | +| | Density (p) | | 1 | +| | CSI-RS periodicity | Slots | 15 kHz SCS: 20 | +| | CSI-RS offset | Slots | 0 | +| | Frequency Occupation | | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| PDSCH DMRS configuration | Antenna ports indexes | | {1000} for Rank 1 tests | +| | Position of the first DMRS for PDSCH mapping type A | | 2 | +| | Number of PDSCH DMRS CDM group(s) without data | | 1 for Rank 1 | +| TCI state #0 | Type 1 QCL information | SSB index | SSB #0 | +| | | QCL Type | Type C | +| | Type 2 QCL information | SSB index | N/A | +| | | QCL Type | N/A | +| TCI state #1 | Type 1 QCL information | CSI-RS resource | CSI-RS resource 1 from 'CSI-RS for tracking' configuration | +| | | QCL Type | Type A | +| | Type 2 QCL information | CSI-RS resource | N/A | +| | | QCL Type | N/A | +| PT-RS configuration | | | PT-RS is not configured | +| Maximum number of code block groups for ACK/NACK feedback | | | 1 | +| Maximum number of HARQ transmission | | | 4 | +| HARQ ACK/NACK bundling | | | Multiplexed | +| Redundancy version coding sequence | | | {0,2,3,1} | +| PDSCH & PDSCH DMRS Precoding configuration | | | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination, and with PRB bundling granularity | +| Symbols for all unused REs | | | OP.1 FDD as defined in Annex A.5.1.1 of 38.101-4 | +| Physical signals, channels mapping and precoding | | | As specified in Annex B.4.1 of 38.101-4 | +| NOTE 1: UE assumes that the TCI state for the PDSCH is identical to the TCI state applied for the PDCCH transmission. | | | | +| NOTE 2: Point A coincides with minimum guard band as specified in Table 5.3.3-1 from TS 38.101-1 [5] for tested channel bandwidth and subcarrier spacing. | | | | +| NOTE 3: Refer to Table 7.4.1.5.3-1 in [9] | | | | + +#### 8.2.1.2.2.1 1RX requirements + +[to be updated] + +#### 8.2.1.2.2 2RX requirements + +##### 8.2.1.2.2.1 FDD + +###### 8.2.1.2.2.1.1 Minimum requirements for PDSCH Mapping Type A + +The performance requirements are specified in Table 8.2.1.2.2.1.1-3 with the addition of test parameters in Table 8.2.1.2.2.1.1-2 and the downlink physical channel setup according to Annex A.3. + +The test purposes are specified in Table 8.2.1.2.2.1.1-1. + +**Table 8.2.1.2.2.1.1-1: Tests purpose** + +| Purpose | Test index | +|---------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Verify the PDSCH mapping Type A normal performance under 2 receive antenna conditions and with different channel models and MCS | 1-1, 1-2, 1-3, 1-4 | + +Table 8.2.1.2.2.1.1-2: Test parameters + +| Parameter | Unit | Value | +|--------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Duplex mode | | FDD | +| Active DL BWP index | | 1 | +| PDSCH configuration | Mapping type | Type A | +| | k0 | 0 | +| | Starting symbol (S) | 2 | +| | Length (L) | 12 | +| | PDSCH aggregation factor | 1 | +| | PRB bundling type | Static | +| | PRB bundling size | 2 | +| | Resource allocation type | Type 0 | +| | RBG size | Config2 | +| | VRB-to-PRB mapping type | Non-interleaved | +| PDSCH DMRS configuration | DMRS Type | Type 1 | +| | Number of additional DMRS | 1 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | 1 | +| CSI-RS for tracking | CSI-RS periodicity | Slots 20 for CSI-RS resource 1,2,3,4. | +| | CSI-RS offset | Slots 10 for CSI-RS resource 1 and 2
11 for CSI-RS resource 3 and 4. | +| Number of HARQ Processes | | 16 for Test 1-1, Test 1-2
32 for Test 1-3
4 with feedback disabled, 12 with feedback enabled in 16 HARQ processes with re-Tx disable for all HARQ for Test 1-4 in which 4 disabled processes are randomly select at test configuration | +| The number of slots between PDSCH and corresponding HARQ-ACK information | | 10 for Test 1-1, Test 1-2, Test 1-3
N/A for Test 1-4 | +| Maximum number of HARQ transmission | | 4 for Test 1-1, Test 1-2, Test 1-3
Disabled for all HARQ processes for Test 1-4 | + +Table 8.2.1.2.2.1.1-3: Minimum performance for Rank 1 + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 1-1 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDL100-200 | 1x2, ULA Low | 70 | 0.3 | +| 1-2 | R.PDSCH.1-2.1 FDD | 10 / 15 | 16QAM, 0.48 | NTN-TDL5-200 | 1x2, ULA Low | 70 | 7.6 | +| 1-3 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDL5-200 | 1x2, ULA Low | 70 | -0.4 | +| 1-4 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDL100-200 | 1x2, ULA Low | 70 | 1.1 | + +The normative reference for this requirement is TS 38.101-5 [11] clause 8.2.1.2.2. + +#### 8.2.1.2.2.1.1\_1 2Rx FDD FR1 PDSCH Mapping Type A for Satellite Access + +**Editor's Note:** This test cases is incomplete in following aspects: + +- Annex F MU/TT analysis +- Annex G Minimum test time + +##### 8.2.1.2.2.1.1\_1.1 Test Purpose + +Verify the PDSCH mapping Type A normal performance under 2 receive antenna conditions and with different channel models and MCS for NTN capable UE receiving signal from earth based gNB via a satellite access node. + +##### 8.2.1.2.2.1.1\_1.2 Test Applicability + +This test applies to all types of NTN UE release 17 and forward supporting satellite access. + +##### 8.2.1.2.2.1.1\_1.3 Test Description + +###### 8.2.1.2.2.1.1\_1.3.1 Initial Conditions + +Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state. + +The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1 and Table 5.3.6-1 of 38.521-1 [2]. + +Configurations of PDSCH and PDCCH before measurement are specified in Annex C. + +Test Environment: Normal, as defined in TS 38.508-1 [12] clause 4.1. + +Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [12] clause 5.2.2. + +1. Connect the SS, the faders and AWGN noise source to the UE antenna connectors as shown in TS 38.508-1 [12] Annex A, in Figure A.3.1.7.1 for TE diagram and clause A.3.2.2 for UE diagram. +2. The parameter settings for the cell are set up according to Table 5.2-1 and Table 5.2.2.1.1.0-2 as appropriate. +3. Downlink signals for NR cell are initially set up according to clauses C.0, C.1, C.2 and uplink signals according to clauses G.0, G.1, G.2, G.3.1 of TS 38.521-1 [2]. +4. Propagation conditions are set according to Annex B.0. +5. Ensure the UE is in state RRC\_CONNECTED with generic procedure parameters Connectivity NR for NR/5GC with *Connected without Release On, Test Mode On* according to TS 38.508-1 [12] clause 4.5. Message contents are defined in clause 8.2.1.2.2.1.1\_1.3.3. + +###### 8.2.1.2.2.1.1\_1.3.2 Test procedure + +1. UE location according to TS 38.508-1 [12] clause 5.6.1 is provided to the UE through any preconfigured means. +2. Test equipment shall emulate the signal with doppler and delay according to ephemeris defined in TS 38.508[12] table 5.6.2.1-1 for GSO if UE supports only GSO or both GSO and NGSO satellites and table 5.6.2.1-3 for NGSO (LEO-1200) if UE supports only NGSO satellites. Test system shall send same SIB19 information during the duration of the test as defined in TS 38.508-1 [12] clause 5.6.3.1. +3. Deactivate UE prediction of satellite trajectory by any preconfigured means. +4. SS transmits PDSCH via PDCCH DCI format 1\_1 for C\_RNTI to transmit the DL RMC according to Tables Table 8.2.1.2.2.1.1-3. The SS sends downlink MAC padding bits on the DL RMC. +5. Set the parameters of the bandwidth, MCS, reference channel, the propagation condition, the correlation matrix and the SNR according to Table 8.2.1.2.2.1.1-2 and Table 8.2.1.2.2.1.1-3 as appropriate. + +6. Measure the average throughput for a duration sufficient to achieve statistical significance according to Annex G clause G.1.5. Count the number of NACKs, ACKs and statDTXs on the UL during each subtest and decide pass or fail according to [Annex G]. +4. Repeat steps from 1 to 3 for each subtest in Table 8.2.1.2.2.1.1-3 as appropriate. + +#### 8.2.1.2.2.1.1\_1.3.3 Message contents + +Message contents are according to TS 38.508-1 [12] clauses 4.6.1 and 5.4.2. + +SIB19 contents as TS 38.508-1 [12] clause 5.6.2.1. + +**Table 8.2.1.2.2.1.1\_1.3.3-1: DMRS-DownlinkConfig** + +| Derivation Path: TS 38.508-1 [6], Table 5.4.2.0-24 | | | | +|----------------------------------------------------|--------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| DMRS-DownlinkConfig ::= SEQUENCE { | | | | +| dmrs-AdditionalPosition | Pos1 | | | +| } | | | | + +**Table 8.2.1.2.2.1.1\_1.3.3-2: PDSCH-ServingCellConfig** + +| Derivation Path: TS 38.508-1 [6], Table 5.4.2.0-25 | | | | +|----------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PDSCH-ServingCellConfig ::= SEQUENCE { | | | | +| nrofHARQ-ProcessesForPDSCH | n16 | Test 1-1, Test 1-2 | | +| | n32 | Test 1-3 | | +| | | Test 1-4
4 with feedback disabled, 12 with feedback enabled in 16 HARQ processes with re-Tx disable for all HARQ for Test 1-4 in which 4 disabled processes are randomly select at test configuration | | +| } | | | | + +**Table 8.2.1.2.2.1.1\_1.3.3-3: CSI-ResourcePeriodicityAndOffset for CSI Tracking** + +| Derivation Path: TS 38.508-1 [6], Table 5.4.2.0-9 | | | | +|---------------------------------------------------|------------------------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| CSI-ResourcePeriodicityAndOffset ::= CHOICE { | | | | +| slots20 | 10 (for CSI-RS resources 1 and 2)
11 (for CSI-RS resources 3 and 4) | | | +| } | | | | + +#### 8.2.1.2.2.1.1\_1.3.4 Test requirement + +Table 8.2.1.2.2.1.1-2 and Table 8.2.1.2.2.1.1-3 define the primary level settings. + +The fraction of maximum throughput percentage for the downlink reference measurement channels specified in Annex A 3.2.1.1 for each throughput test shall meet or exceed the specified value in Table 8.2.1.2.2.1.1\_1.3.4-1 for the specified SNR including test tolerances for all throughput tests. + +Table 8.2.1.2.2.1.1\_1.3.4-1: Minimum performance for Rank 1 + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|-----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 1-1 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDLA100-200 | 1x2, ULA Low | 70 | 0.3 + TT | +| 1-2 | R.PDSCH.1-2.1 FDD | 10 / 15 | 16QAM, 0.48 | NTN-TDLC5-200 | 1x2, ULA Low | 70 | 7.6 + TT | +| 1-3 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDLC5-200 | 1x2, ULA Low | 70 | -0.4 + TT | +| 1-4 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDLA100-200 | 1x2, ULA Low | 70* | 1.1 + TT | + +--- + +## Annex A: (normative): Measurement channels + +### A.1 General + +#### A.1.1 Throughput definition + +The throughput values defined in the measurement channels specified in Annex A, are calculated and are valid per codeword. For multi-codeword transmissions, the throughput referenced in the minimum requirements is the sum of throughputs of all codewords. + +--- + +### A.2 UL reference measurement channels + +[to be updated] + +--- + +### A.3 DL reference measurement channels + +#### A.3.1 General + +The transport block size (TBS) determination procedure is described in clause 5.1.3.2 of TS 38.214 [12]. + +Unless otherwise stated, no user data is scheduled on slot #0 within 20 ms in order to avoid SSB and PDSCH transmissions in one slot and simplify test configuration. + +#### A.3.2 Reference measurement channels for PDSCH performance requirements + +##### A.3.2.0 General + +For PDSCH reference channels if more than one Code Block is present, an additional CRC sequence of $L = 24$ Bits is attached to each Code Block (otherwise $L = 0$ Bit). + +## A.3.2.1 FDD + +### A.3.2.1.1 Reference measurement channels for SCS 15 kHz FR1 + +**Table A.3.2.1.1-1: PDSCH Reference Channel for FDD (QPSK)** + +| Parameter | Unit | Value | | | | | +|----------------------------------------|-------|-------------------|--|--|--|--| +| Reference channel | | R.PDSCH.1-1.1 FDD | | | | | +| Channel bandwidth | MHz | 10 | | | | | +| Subcarrier spacing | kHz | 15 | | | | | +| Number of allocated resource blocks | PRBs | 52 | | | | | +| Number of consecutive PDSCH symbols | | 12 | | | | | +| Allocated slots per 2 frames | Slots | 19 | | | | | +| MCS table | | 64QAM | | | | | +| MCS index | | 4 | | | | | +| Modulation | | QPSK | | | | | +| Target Coding Rate | | 0.30 | | | | | +| Number of MIMO layers | | 1 | | | | | +| Number of DMRS REs | | 18 | | | | | +| Overhead for TBS determination | | 0 | | | | | +| Information Bit Payload per Slot | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | +| For Slots i = 1, ..., 19 | Bits | 3,904 | | | | | +| Transport block CRC per Slot | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | +| For Slots i = 1, ..., 19 | Bits | 24 | | | | | +| Number of Code Blocks per Slot | | | | | | | +| For Slot i = 0 | CBs | N/A | | | | | +| For Slots i = 1, ..., 19 | CBs | 1 | | | | | +| Binary Channel Bits Per Slot | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | +| For Slots i = 10, 11 | Bits | 12,480 | | | | | +| For Slots i = 1, ..., 9, 12, ..., 19 | Bits | 13,104 | | | | | +| Max. Throughput averaged over 2 frames | Mbps | 3.709 | | | | | + +NOTE 1: SS/PBCH block is transmitted in slot #0 with periodicity 20 ms + +NOTE 2: Slot i is slot index per 2 frames + +Table A.3.2.1.1-2: PDSCH Reference Channel for FDD (16QAM) + +| Parameter | Unit | Value | | | | | | +|----------------------------------------|-------|-------------------|--|--|--|--|--| +| Reference channel | | R.PDSCH.1-2.1 FDD | | | | | | +| Channel bandwidth | MHz | 10 | | | | | | +| Subcarrier spacing | kHz | 15 | | | | | | +| Number of allocated resource blocks | PRBs | 52 | | | | | | +| Number of consecutive PDSCH symbols | | 12 | | | | | | +| Allocated slots per 2 frames | Slots | 19 | | | | | | +| MCS table | | 64QAM | | | | | | +| MCS index | | 13 | | | | | | +| Modulation | | 16QAM | | | | | | +| Target Coding Rate | | 0.48 | | | | | | +| Number of MIMO layers | | 1 | | | | | | +| Number of DMRS REs | | 12 | | | | | | +| Overhead for TBS determination | | 0 | | | | | | +| Information Bit Payload per Slot | | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | | +| For Slots i = 1, ..., 19 | Bits | 13,064 | | | | | | +| Transport block CRC per Slot | | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | | +| For Slots i = 1, ..., 19 | Bits | 24 | | | | | | +| Number of Code Blocks per Slot | | | | | | | | +| For Slot i = 0 | CBs | N/A | | | | | | +| For Slots i = 1, ..., 19 | CBs | 2 | | | | | | +| Binary Channel Bits Per Slot | | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | | +| For Slots i = 10, 11 | Bits | 26,208 | | | | | | +| For Slots i = 1, ..., 9, 12, ..., 19 | Bits | 27,456 | | | | | | +| Max. Throughput averaged over 2 frames | Mbps | 12.411 | | | | | | + +NOTE 1: SS/PBCH block is transmitted in slot #0 with periodicity 20 ms + +NOTE 2: Slot i is slot index per 2 frames + +## A.4 Testing related to Satellite Access + +### A.4.1 General + +The following test conditions should be maintained for Satellite Access when test equipment emulates the snapshot of the satellite link channel. + +- The same ephemeris info will be maintained during each test. +- A set of ephemeris information are pre-defined for each satellite corresponding to respective epoch times in TS 38.508-1 [12]. +- The range of the selected constant delay shift is as follows: + - For NGSO an altitude of 600 km and 1200 km on a circular orbit are considered. The range of the one-way delay between UE and satellite is from 2ms (lowest value for LEO orbit 600km) to 6.67 ms (highest value for LEO orbit 1200 km). + - For GSO the range of the one-way delay from UE to satellite is within 119.375 ms to 128.79 ms. +- Constant delay value is derived from ephemeris info (SIB19) and UE location associated to zero Doppler or non-zero Doppler value under test. + +### A.4.2 Test condition for transmitter characteristics + +All requirements in clause 6 for transmitter characteristics, other than frequency error in clause 6.4.1 shall be verified when Doppler conditions are set to zero and delay conditions are set to constant for all types of satellites. + +Frequency error requirement in clause 6.4.1 shall be verified for at least two cases: one with zero Doppler condition and the other one with a constant Doppler shift where the range of the absolute value of Doppler is greater than zero and up to [0.93] ppm if the IE field ntn-ScenarioSupport-r17 is present and indicated as GSO and up to 24 ppm if the IE field ntn-ScenarioSupport-r17 is present and indicated as NGSO or only the IE field nonTerrestrialNetwork-r17 is present. The delay condition is a constant. + +### A.4.3 Test condition for receiver characteristics + +All requirements in clause 7 for receiver characteristics shall be verified when Doppler conditions are set to zero and delay conditions are set to constant for all types of satellites. + +### A.4.4 Test condition for performance requirements + +All requirements in clause 8 for performance requirements shall be verified when Doppler conditions related to satellite motion for DL in service link are set to zero and delay conditions are set to constant for all types of NGSO satellites. + +The one-way delay between UE and satellite for NGSO at an altitude of 600 km is 2 ms. + +--- + +## Annex B: (normative): Propagation conditions + +### B.0 No interference + +The downlink connection between the System Simulator and the UE is without Additive White Gaussian Noise, and has no fading or multipath effects. + +--- + +### B.1 Static propagation condition + +#### B.1.1 UE Receiver with 1Rx + +For 2 port transmission the channel matrix is defined in the frequency domain by + +$$\mathbf{H} = \begin{bmatrix} 1 & 1 \end{bmatrix}.$$ + +#### B.1.2 UE Receiver with 2Rx + +For 1 port transmission the channel matrix is defined in the frequency domain by + +$$\mathbf{H} = \begin{bmatrix} 1 \\ 1 \end{bmatrix}.$$ + +For 2 port transmission the channel matrix is defined in the frequency domain by + +$$\mathbf{H} = \begin{bmatrix} 1 & j \\ 1 & -j \end{bmatrix}.$$ + +--- + +### B.2 Multi-path fading propagation conditions + +#### B.2.0 General + +The multipath propagation conditions consist of several parts: + +- A delay profile in the form of a "tapped delay-line", characterized by a number of taps at fixed positions on a sampling grid. The profile can be further characterized by the r.m.s. delay spread and the maximum delay spanned by the taps. +- A combination of channel model parameters that include the Delay profile and the Doppler spectrum that is characterized by a classical spectrum shape and a maximum Doppler frequency. + +Initial channel matrix for LOS component of NTN-TDL-C channel model is equal to channel matrix of Static propagation conditions in Clause B.1. + +## B.2.1 Delay profiles + +The delay profiles are derived from the TR 38.811 [x] NTN-TDL models for the desired delay spread and tap resolution. After scaling the normalized delay spread values for each tap by the desired RMS delay spread, the tap delays are quantized to a delay resolution of 5ns by rounding to the nearest multiple of the delay resolution. + +**Table B.2.1-1: Delay profiles for NR NTN channel models** + +| Type | Model | Delay spread (r.m.s.) | Delay resolution | +|------|-------------|-----------------------|------------------| +| NLOS | NTN-TDLA100 | 100 ns | 5 ns | +| LOS | NTN-TDLC5 | 5 ns | 5 ns | + +**Table B.2.1-2: NTN-TDLA100 (DS = 100 ns)** + +| Tap # | Delay [ns] | Power [dB] | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | 0 | Rayleigh | +| 2 | 110 | -4.7 | Rayleigh | +| 3 | 285 | -6.5 | Rayleigh | + +**Table B.2.1-3: NTN-TDLC5 (DS = 5 ns)** + +| Tap # | Delay [ns] | Power [dB] | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -0.6 | LOS path | +| | 0 | -8.9 | Rayleigh | +| 2 | 60 | -21.5 | Rayleigh | + +NOTE 1: Tap #1 follows a Rician distribution. + +## B.2.2 Combinations of channel model parameters + +The propagation conditions used for the performance measurements in multi-path fading environment are indicated as a combination of a channel model name and a maximum Doppler frequency, i.e., NTN-TDLA-, or NTN-TDLC- where '' indicates the desired delay spread and '' indicates the maximum Doppler frequency (Hz). + +Table B.2.2-1 show the propagation conditions that are used for the performance measurements in multi-path fading environment for NLOS and LOS propagation conditions. + +**Table B.2.2-1: Channel model parameters for NTN** + +| Combination name | Model | Maximum Doppler frequency | +|------------------|-------------|---------------------------| +| NTN-TDLA100-200 | NTN-TDLA100 | 200 Hz | +| NTN-TDLC5-200 | NTN-TDLC5 | 200 Hz | + +## B.2.3 MIMO Channel Correlation Matrices + +### B.2.3.0 General + +The MIMO channel correlation matrices defined in clause B.2.3 apply for the antenna configuration using uniform linear arrays at both gNB and UE. + +### B.2.3.1 MIMO Correlation Matrices using Uniform Linear Array (ULA) + +#### B.2.3.1.0 General + +The MIMO channel correlation matrices defined in clause B.2.3.1.1 apply for the antenna configuration using uniform linear array (ULA) at both gNB and UE. + +#### B.2.3.1.1 Definition of MIMO Correlation Matrices + +Table B.2.3.1.1-1 defines the correlation matrix for the gNB. + +**Table B.2.3.1.1-1: gNB correlation matrix** + +| | One antenna | Two antennas | +|-----------------|---------------|----------------------------------------------------------------------| +| gNB Correlation | $R_{gNB} = 1$ | $R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | + +Table B.2.3.1.1-2 defines the correlation matrix for the UE: + +**Table B.2.3.1.1-2: UE correlation matrix** + +| | One antenna | Two antennas | +|----------------|--------------|-------------------------------------------------------------------| +| UE Correlation | $R_{UE} = 1$ | $R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$ | + +Table B.2.3.1.1-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in Table B.2.3.1.1-3 defines the spatial correlation between the antennas at the gNB and UE. + +**Table B.2.3.1.1-3: $R_{spat}$ correlation matrices** + +| | | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{spat} = R_{UE} = \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix}$ | +| 2x1 case | $R_{spat} = R_{gNB} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$ | +| 2x2 case | $R_{spat} = R_{gNB} \otimes R_{UE} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix} \otimes \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix} = \begin{bmatrix} 1 & \beta & \alpha & \alpha\beta \\ \beta^* & 1 & \alpha\beta^* & \alpha \\ \alpha^* & \alpha^*\beta & 1 & \beta \\ \alpha^*\beta^* & \alpha^* & \beta^* & 1 \end{bmatrix}$ | + +#### B.2.3.1.2 MIMO Correlation Matrices at High, Medium and Low Level + +The $\alpha$ and $\beta$ for different correlation types are given in Table B.2.3.1.2-1. + +**Table B.2.3.1.2-1: The $\alpha$ and $\beta$ parameters for ULA MIMO correlation matrices** + +| Correlation Model | $\alpha$ | $\beta$ | +|-------------------|----------|---------| +| Low correlation | 0 | 0 | + +The correlation matrices low correlation are defined in Table B.2.3.1.2-2 below. + +**Table B.2.3.1.2-2: MIMO correlation matrices for low correlation** + +| | | +|--------------------------------------------------|-----------------| +| 1x2 case | $R_{low} = I_2$ | +| 2x1 case | $R_{low} = I_2$ | +| 2x2 case | $R_{low} = I_4$ | +| NOTE: $I_d$ is the $d \times d$ identity matrix. | | + +## Annex C (normative): Downlink physical channels + +### C.1 General + +This annex specifies the downlink physical channels that are needed for setting a connection and channels that are needed during a connection. + +### C.2 Setup (Conducted) + +Table C.2-1 describes the downlink Physical Channels that are required for connection set up. + +**Table C.2-1: Downlink Physical Channels required for connection set-up** + +| Physical Channel | +|------------------| +| PBCH | +| SSS | +| PSS | +| PDCCH | +| PDSCH | +| PBCH DMRS | +| PDCCH DMRS | +| PDSCH DMRS | +| CSI-RS | + +### C.3 Connection (Conducted) + +#### C.3.0 General + +The following clauses, describes the downlink Physical Channels that are transmitted during a connection i.e., when measurements are done. + +#### C.3.1 Measurement of Performance requirements + +Table C.3.1-1 is applicable for measurements in which uniform RS-to-EPRE boosting for all downlink physical channels, unless otherwise stated. + +**Table C.3.1-1: Downlink Physical Channels transmitted during a connection (FDD and TDD)** + +| Parameter | Unit | Value (Note 2) | +|-----------------------------------|------|-----------------------------------| +| SSS transmit power | W | Test specific | +| EPRE ratio of PSS to SSS | dB | 0 | +| EPRE ratio of PBCH to SSS | dB | 0 | +| EPRE ratio of PBCH to PBCH DMRS | dB | 0 | +| EPRE ratio of PDCCH to SSS | dB | 0 | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | 0 | +| EPRE ratio of PDSCH to SSS | dB | 0 | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | Test specific (Note 1) | +| EPRE ratio of CSI-RS to SSS | dB | $-10 \cdot \log_{10}(L)$ (Note 3) | +| EPRE ratio of OCN to SSS | dB | 0 | +| EPRE ratio of PDCCH OCN to SSS | dB | 0 | +| EPRE ratio of LTE CRS to NR SSS | dB | 0 (Note 4) | + +NOTE 1: Value is derived from Table 4.1-1 in TS 38.214 [12] based on "Number of DM-RS CDM groups without data" and "DMRS Type" parameters specified for each test. + +NOTE 2: The value is the energy of per RE for a single antenna port before pre-coding. + +NOTE 3: $L \in \{1, 2, 4, 8\}$ is the CDM group size of NZP CSI-RS specified for each test. + +NOTE 4: It is only applicable to LTE-NR coexistence tests. + +## Annex D (normative): Characteristics of the interfering signal + +### D.1 General + +Some RF performance requirements for the NR UE receiver are defined with interfering signals present in addition to the wanted signal. + +For NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz, a modulated 5 MHz full bandwidth NR down link signal, and in some cases an additional CW signal, are used as interfering signal. And for some cases an additional CW signal is used. + +### D.2 Interference signals + +Table D.2-1 describes the modulated interferer for different channel bandwidth options for NR band lower than 2700 MHz. + +**Table D.2-1: Description of modulated NR interferer +for NR bands with $F_{DL\_high} < 2,700$ MHz and $F_{UL\_high} < 2,700$ MHz** + +| | Channel bandwidth | | | | +|------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------|--------|--------| +| | 5 MHz | 10MHz | 15 MHz | 20 MHz | +| RB | NOTE 1 | | | | +| $BW_{Interferer}$ | 5 MHz | | | | +| NOTE 1: The RB configured for interfering signal is the same as maximum RB number defined in Table 5.3.2-1 for each sub-carrier spacing. | | | | | + +## Annex F (normative): Measurement uncertainties and Test Tolerances + +### F.1 Acceptable uncertainty of Test System (normative) + +#### F.1.0 General + +The maximum acceptable uncertainty of the Test System is specified below for each test, where appropriate. The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified range, and the equipment under test to be measured with an uncertainty not exceeding the specified values. All ranges and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95 % of the performance of a population of test equipment. + +For RF tests it should be noted that the uncertainties in clause F.1 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System. + +The downlink signal uncertainties apply at each receiver antenna connector. + +#### F.1.1 Measurement of test environments + +The measurement accuracy of the UE test environments defined in TS 38.508-1 [12] subclause 4.1, Test environments shall be + +- Pressure $\pm 5$ kPa. +- Temperature $\pm 2$ degrees. +- Relative Humidity $\pm 5$ %. +- DC Voltage $\pm 1.0$ %. +- AC Voltage $\pm 1.5$ %. +- Vibration 10 %. +- Vibration frequency 0.1 Hz. + +The above values shall apply unless the test environment is otherwise controlled and the specification for the control of the test environment specifies the uncertainty for the parameter. + +#### F.1.2 Measurement of transmitter + +**Table F.1.2-1: Maximum Test System Uncertainty for transmitter tests** + +| Subclause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------|---------------------------------------------------------------------------|---------------------------------------| +| 6.3.1 Minimum output power | Same as clause 6.3.1 in TS 38.521-1 [2] for FDD band with $f \leq 3$ GHz. | | +| 6.3.2 Transmit OFF power | Same as clause 6.3.2 in TS 38.521-1 [2] for FDD band with $f \leq 3$ GHz. | | + +## F.1.3 Measurement of receiver + +**Table F.1.3-1: Maximum Test System Uncertainty for receiver tests** + +| Subclause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------| +| 7.4 Maximum input level | Same as clause 7.4 in TS 38.521-1 [2] for FDD band with $f \leq 3$ GHz. | | +| 7.5 Adjacent channel selectivity
7.5 Adjacent channel selectivity | Same as clause 7.5 in TS 38.521-1 [2] for FDD band with " $f \leq 3.0$ GHz". | Same as clause 7.5 in TS 38.521-1 [2]". | +| 7.6.2 In-band blocking | Same as clause 7.6.2 in TS 38.521-1 [2] for FDD band with " $f \leq 3.0$ GHz". | Same as clause 7.6.2 in TS 38.521-1 [2]". | +| 7.6.3 Out of Band Blocking | Same as clause 7.6.3 in TS 38.521-1 [2] for FDD band with " $f \leq 3.0$ GHz". | Same as clause 7.6.3 in TS 38.521-1 [2]". | +| 7.6.4 Narrow band blocking | Same as clause 7.6.4 in TS 38.521-1 [2] for FDD band with " $f \leq 3.0$ GHz". | Same as clause 7.6.4 in TS 38.521-1 [2]". | +| 7.7 Spurious response | Same as clause 7.6.3. | Same as clause 7.6.3. | +| 7.8.2 Wide band Intermodulation | Same as clause 7.8.2 in TS 38.521-1 [2] for FDD band with " $f \leq 3.0$ GHz". | Same as clause 7.8.2 in TS 38.521-1 [2]". | +| 7.9 Spurious emissions | Same as clause 7.8.2 in TS 38.521-1 [2] with " $f \leq 12.75$ GHz" | | + +## F.2 Interpretation of measurement results (normative) + +The measurement results returned by the Test System are compared – without any modification – against the Test Requirements. The Test Requirement is defined as a threshold considered in a test to assess compliance of the device; it might be either equal ("Shared Risk" principle) or relaxed ("Never fail a good DUT" principle) compared to the corresponding core specification value by an amount defined in Annex F.3 as Test Tolerance. + +The "Shared Risk" and the "Never fail a good DUT" principles are defined in Recommendation ITU-R M.1545. + +The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report. + +The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in clause F.1 of the present document. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause F.1, it is still permitted to use this apparatus provided that an adjustment is made value as follows: + +Any additional uncertainty in the Test System over and above that specified in clause F.1 shall be used to tighten the Test Requirement, making the test harder to pass. For some tests, for example receiver tests, this may require modification of stimulus signals. This procedure will ensure that a Test System not compliant with clause F.1 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with clause F.1 had been used. + +## F.3 Test Tolerance and Derivation of Test Requirements (informative) + +### F.3.0 General + +The Test Requirements in the present document have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances defined in this clause. When the Test Tolerance is zero, the Test Requirement will be the same as the Minimum Requirement. When the Test Tolerance is non-zero, the Test + +Requirements will differ from the Minimum Requirements, and the formula used for the relaxation is given in this clause. + +The Test Tolerances are derived from Test System uncertainties, regulatory requirements and criticality to system performance. As a result, the Test Tolerances may sometimes be set to zero. + +The test tolerances should not be modified for any reason e.g. to take account of commonly known test system errors (such as mismatch, cable loss, etc.). + +The downlink Test Tolerances apply at each receiver antenna connector. + +## F.3.1 Measurement of test environments + +The UE test environments are set to the values defined in TS 38.508-1 subclause 4.1, without any relaxation. The applied Test Tolerance is therefore zero. + +## F.3.2 Measurement of transmitter + +**Table F.3.2-1: Derivation of Test Requirements (Transmitter tests)** + +| Sub clause | Test Tolerance (TT) | Formula for test requirement | +|----------------------------|---------------------------------------------------------------------------|------------------------------| +| 6.3.1 Minimum output power | Same as clause 6.3.1 in TS 38.521-1 [2] for FDD band with $f \leq 3$ GHz. | Minimum requirement + TT | +| 6.3.2 Transmit OFF power | Same as clause 6.3.2 in TS 38.521-1 [2] for FDD band with $f \leq 3$ GHz. | Minimum requirement + TT | + +## F.3.3 Measurement of receiver + +**Table F.3.3-1: Derivation of Test Requirements (Receiver tests)** + +| Sub clause | Test Tolerance (TT) | Formula for test requirement | +|----------------------------------|-------------------------------------------------------------------------|-------------------------------------------| +| 7.4 Maximum input level | Same as clause 7.4 in TS 38.521-1 [2] for FDD band with $f \leq 3$ GHz. | Maximum input level - TT | +| 7.5 Adjacent channel selectivity | Same as clause 7.5 in TS 38.521-1 [2]". | Same as clause 7.5 in TS 38.521-1 [2]". | +| 7.6.2 In-band blocking | Same as clause 7.6.2 in TS 38.521-1 [2]". | Same as clause 7.6.2 in TS 38.521-1 [2]". | +| 7.6.3 Out of Band Blocking | Same as clause 7.6.3 in TS 38.521-1 [2]". | Same as clause 7.6.3 in TS 38.521-1 [2]". | +| 7.6.4 Narrow band blocking | Same as clause 7.6.4 in TS 38.521-1 [2]". | Same as clause 7.6.4 in TS 38.521-1 [2]". | +| 7.7 Spurious response | Same as clause 7.6.3. | Same as clause 7.6.3. | +| 7.8.2 Wide band Intermodulation | Same as clause 7.8.2 in TS 38.521-1 [2]". | Same as clause 7.8.2 in TS 38.521-1 [2]". | +| 7.9 Spurious emissions | Same as clause 7.9 in TS 38.521-1 [2]". | Same as clause 7.9 in TS 38.521-1 [2]". | + +## F.4 Uplink power window + +### F.4.1 Introduction + +A number of Tx and Rx Test cases set the UE uplink power to be within a defined window to ensure the test is carried out in the intended conditions. This clause gives the method for calculating the uplink power window used in Tx test cases and Rx Test cases. + +## F.4.2 Setting the power window above a requirement + +Information from the core requirements in TS 38.101-1 [5], TS 38.213 [7] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for $f \leq 3.0$ GHz and $BW \leq 40$ MHz and taking an example where the target value is 0dBm (lower end of a UE Core requirement side condition range of $0 \text{ dBm} \leq \text{Output power} \leq 10 \text{ dBm}$ ): + +![Figure F.4.2-1: Example uplink power setting to be above a requirement. The diagram illustrates the calculation of the uplink power window based on UE core requirements, test system uncertainties, and power step tolerances.](8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg) + +The diagram shows the derivation of the uplink power window. The vertical axis represents power in dBm, with a reference line at 0dBm. The 'UE Core requirement side condition' is indicated by a dashed line at 0dBm. The 'Uplink power control window, Measured value' is shown as a range of power levels. The 'UE power step size' is 1.0dB, and the 'UE Power step tolerance' is $\pm 0.7$ dB. The 'Test system absolute power measurement uncertainty at top of window' is $\pm 0.8$ dB for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The 'Test system relative power measurement uncertainty' is $\pm 0.7$ dB for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The 'Overall Uplink power window size' is calculated as $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.8\text{dB} + 0.8\text{dB}) = 4.0\text{dB}$ for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The 'Uplink power window, actual value' is $+0\text{dB}, +4.0\text{dB}$ for $f \leq 3.0$ GHz, $BW \leq 40$ MHz. The 'Bottom of window is aligned to UL power requirement'. + +Figure F.4.2-1: Example uplink power setting to be above a requirement. The diagram illustrates the calculation of the uplink power window based on UE core requirements, test system uncertainties, and power step tolerances. + +### UE Uplink power + +Figure F.4.2-1: Example uplink power setting to be above a requirement + +The smallest UE Power step size is defined in TS 38.213 [7] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [5] Table 6.3.4.3-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.2-1. + +## F.4.3 Setting the power window below a requirement + +Information from the core requirements in TS 38.101-1 [5], TS 38.213 [7] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window to ensure UE is not tested outside Core requirements. + +This process is shown in the diagram below, using values for $f \leq 3.0\text{ GHz}$ and $BW \leq 40\text{ MHz}$ and taking an example where the target value is 4 dB below PCMAX\_L (UE Core requirement side condition): + +![Diagram illustrating the setting of the uplink power window below a requirement. The vertical axis represents UE Uplink power. The top reference is PCMAX_L. The UE Core requirement side condition is PCMAX_L - 4dB. The diagram shows the derivation of the uplink power control window (Measured value) from the UE Core requirement on power control (0dB) and UE Power step tolerance (±0.7dB). The overall uplink power window size is calculated as (1dB + 0.7dB + 0.7dB + 0.7dB + 0.7dB) = 3.8dB for f ≤ 3.0GHz, BW ≤ 40MHz. The top of the window is aligned to the UL power requirement (PCMAX_L - 4dB). The actual uplink power window values are +0dB and -3.8dB for f ≤ 3.0GHz, BW ≤ 40MHz. The diagram also includes test system absolute power measurement uncertainty at the top and bottom of the window (±0.7 dB) and test system relative power measurement uncertainty (±0.7 dB).](2e83263cd91cb4bcdc0ad2973f715412_img.jpg) + +The diagram illustrates the process of setting the uplink power window. The vertical axis represents UE Uplink power. The top reference is $P_{\text{CMAX\_L}}$ . The UE Core requirement side condition is $P_{\text{CMAX\_L}} - 4\text{dB}$ . The diagram shows the derivation of the uplink power control window (Measured value) from the UE Core requirement on power control (0dB) and UE Power step tolerance ( $\pm 0.7\text{dB}$ ). The overall uplink power window size is calculated as $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.7\text{dB}) = 3.8\text{dB}$ for $f \leq 3.0\text{ GHz}$ , $BW \leq 40\text{ MHz}$ . The top of the window is aligned to the UL power requirement ( $P_{\text{CMAX\_L}} - 4\text{dB}$ ). The actual uplink power window values are $+0\text{dB}$ and $-3.8\text{dB}$ for $f \leq 3.0\text{ GHz}$ , $BW \leq 40\text{ MHz}$ . The diagram also includes test system absolute power measurement uncertainty at the top and bottom of the window ( $\pm 0.7\text{ dB}$ ) and test system relative power measurement uncertainty ( $\pm 0.7\text{ dB}$ ). + +Diagram illustrating the setting of the uplink power window below a requirement. The vertical axis represents UE Uplink power. The top reference is PCMAX\_L. The UE Core requirement side condition is PCMAX\_L - 4dB. The diagram shows the derivation of the uplink power control window (Measured value) from the UE Core requirement on power control (0dB) and UE Power step tolerance (±0.7dB). The overall uplink power window size is calculated as (1dB + 0.7dB + 0.7dB + 0.7dB + 0.7dB) = 3.8dB for f ≤ 3.0GHz, BW ≤ 40MHz. The top of the window is aligned to the UL power requirement (PCMAX\_L - 4dB). The actual uplink power window values are +0dB and -3.8dB for f ≤ 3.0GHz, BW ≤ 40MHz. The diagram also includes test system absolute power measurement uncertainty at the top and bottom of the window (±0.7 dB) and test system relative power measurement uncertainty (±0.7 dB). + +Figure F.4.3-1: Example uplink power setting to be below a requirement + +The smallest UE Power step size is defined in TS 38.213 [7] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [5] Table 6.3.4.3-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is within the Uplink power window, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.3-1. + +## F.4.4 Setting the power window centred on a target value + +Information from the core requirements in TS 38.101-1 [5], TS 38.213 [7] and the uncertainties in Annex F applicable to the Test case are used to derive the uplink power window. There are 4 stages: + +- Find the uplink power target value. +- Determine how closely the uplink power can be set to the target value. +- Include the effect of test system uncertainty. +- Position the Uplink power window centred on the target value. + +This process is shown in the diagram below, using values for $f \leq 3$ GHz and $BW \leq 40$ MHz and taking an example where the target value is +10 dBm: + +![Diagram illustrating the setting of the power window centred on a target value for UE Uplink power. The diagram shows the calculation of the overall uplink power window size based on UE core requirements, test system uncertainties, and power step tolerance. The target value is 10dBm. The overall window size is calculated as (1dB + 0.7dB + 0.7dB + 0.8dB + 0.8dB) = 4.0dB. The actual window value is ±2.0dB. The center of the window is aligned to the UL power requirement.](bbbb412b1ea8a6ca30ec4b4e7d08fd58_img.jpg) + +The diagram illustrates the process of setting the power window for UE Uplink power. It shows the following components and calculations: + +- UE Target value:** 10dBm +- UE Core requirement on power control:** 0dB +- Test system relative power measurement uncertainty:** $[f \leq 3.0\text{GHz}, BW \leq 40\text{MHz}] \pm 0.7\text{ dB}$ +- Test system absolute power measurement uncertainty at top of window:** $f \leq 3.0\text{GHz}, BW \leq 40\text{MHz}: \pm 0.8\text{ dB}$ +- UE Power step size:** 1.0dB +- UE Power step tolerance:** $\pm 0.7\text{dB}$ +- Test system absolute power measurement uncertainty at bottom of window:** $f \leq 3.0\text{GHz}, BW \leq 40\text{MHz}: \pm 0.8\text{ dB}$ +- Overall Uplink power window size:** $(1\text{dB} + 0.7\text{dB} + 0.7\text{dB} + 0.8\text{dB} + 0.8\text{dB}) = 4.0\text{dB}$ for $f \leq 3.0\text{GHz}, BW \leq 40\text{MHz}$ +- Uplink power window, actual value:** $\pm 2.0\text{dB}$ for $f \leq 3.0\text{GHz}, BW \leq 40\text{MHz}$ +- Centre of window is aligned to UL power requirement** + +Diagram illustrating the setting of the power window centred on a target value for UE Uplink power. The diagram shows the calculation of the overall uplink power window size based on UE core requirements, test system uncertainties, and power step tolerance. The target value is 10dBm. The overall window size is calculated as (1dB + 0.7dB + 0.7dB + 0.8dB + 0.8dB) = 4.0dB. The actual window value is ±2.0dB. The center of the window is aligned to the UL power requirement. + +### UE Uplink power + +Figure F.4.4-1: Example NR FR1 uplink power setting centred on a target value + +The smallest UE Power step size is defined in TS 38.213 [7] Table 7.1.1-1, for absolute $\delta_{\text{PUSCH},b,f,c}$ . + +The UE Power step size tolerance is defined in TS 38.101-1 [5] Table 6.3.4.3-1, for PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, DwPTS fields or Guard Periods, and for a power step $\Delta P \leq 1$ dB. + +The Test system uncertainties are defined in Annex F of the present document. + +To ensure that the actual UE uplink power is centred on the target value, UE uplink power measured by the test system should remain within the smaller Uplink power control window shown in Figure F.4.4-1. + +--- + +## Annex H (normative): Statistical Testing + +### H.1 General + +This annex specifies mapping throughput to error ratio, pass fail limits and pass fail decision rules that are needed for measuring average throughput for a duration sufficient to achieve statistical significance for testing receiver characteristics. + +--- + +### H.2 Statistical testing of receiver characteristics + +#### H.2.1 General + +The test of receiver characteristics is twofold. + +1. A signal or a combination of signals is offered to the RX port(s) of the receiver. +2. The ability of the receiver to demodulate /decode this signal is verified by measuring the throughput. + +In (2) is the statistical aspect of the test and is treated here. + +The minimum requirement for all receiver tests is $> 95$ % of the maximum throughput. + +All receiver tests are performed in static propagation conditions. No fading conditions are applied. + +#### H.2.2 Mapping throughput to error ratio + +- a) The measured information bit throughput $R$ is defined as the sum (in kilobits) of the information bit payloads successfully received during the test interval, divided by the duration of the test interval (in seconds). +- b) In measurement practice the UE indicates successfully received information bit payload by signalling an ACK to the SS. +If payload is received, but damaged and cannot be decoded, the UE signals a NACK. +- c) Only the ACK and NACK signals, not the data bits received, are accessible to the SS. +The number of bits is known in the SS from knowledge of what payload was sent. +- d) For the reference measurement channel, applied for testing, the number of bits is different in different slots, however in a radio frame it is fixed during one test. +- e) The time in the measurement interval is composed of successfully received slots (ACK), unsuccessfully received slots (NACK) and no reception at all (DTX-slots). +- f) DTX-slots may occur regularly according the applicable reference measurement channel (regDTX). +In real live networks this is the time when other UEs are served. In TDD these are the UL and special slots. +regDTX vary from test to test but are fixed within the test. +- g) Additional DTX-slots occur statistically when the UE is not responding ACK or NACK where it should. +(statDTX) +This may happen when the UE was not expecting data or decided that the data were not intended for it. + +The pass / fail decision is done by observing the: + +- number of NACKs; +- number of ACKs; and +- number of statDTXs (regDTX is implicitly known to the SS). + +The ratio $(\text{NACK} + \text{statDTX}) / (\text{NACK} + \text{statDTX} + \text{ACK})$ is the Error Ratio (ER). Taking into account the time consumed by the ACK, NACK, and DTX-TTIs (regular and statistical), ER can be mapped unambiguously to throughput for any single reference measurement channel test. + +## H.2.3 Design of the test + +The test is defined by the following design principles (see clause H.2.6, Theory....): + +1. The early decision concept is applied. +2. A second limit is introduced: Bad DUT factor $M > 1$ +3. To decide the test pass: + +Supplier risk is applied based on the Bad DUT quality + +To decide the test fail + +Customer Risk is applied based on the specified DUT quality + +The test is defined by the following parameters: + +1. Limit ER = 0.05 (Throughput limit = 95%) +2. Bad DUT factor $M = 1.5$ (selectivity) +3. Confidence level CL = 95% (for specified DUT and Bad DUT-quality) + +## H.2.4 Numerical definition of the pass fail limits + +Table H.2.4-1: pass fail limits + +| ne | ns p | ns f | ne | ns p | ns f | ne | ns p | ns f | ne | ns p | ns f | +|----|-----------------|-----------------|----|-----------------|-----------------|-----|-----------------|-----------------|--------------------|-----------------|-----------------| +| 0 | 67 | NA | 37 | 715 | 477 | 74 | 1290 | 1093 | 111 | 1847 | 1739 | +| 1 | 67 | NA | 38 | 731 | 493 | 75 | 1306 | 1110 | 112 | 1862 | 1756 | +| 2 | 95 | NA | 39 | 747 | 509 | 76 | 1321 | 1128 | 113 | 1877 | 1774 | +| 3 | 119 | NA | 40 | 763 | 525 | 77 | 1336 | 1145 | 114 | 1891 | 1792 | +| 4 | 141 | NA | 41 | 779 | 541 | 78 | 1351 | 1162 | 115 | 1906 | 1809 | +| 5 | 162 | NA | 42 | 795 | 557 | 79 | 1366 | 1179 | 116 | 1921 | 1827 | +| 6 | 183 | NA | 43 | 810 | 573 | 80 | 1382 | 1197 | 117 | 1936 | 1845 | +| 7 | 203 | NA | 44 | 826 | 590 | 81 | 1397 | 1214 | 118 | 1951 | 1863 | +| 8 | 222 | NA | 45 | 842 | 606 | 82 | 1412 | 1231 | 119 | 1966 | 1880 | +| 9 | 241 | 67 | 46 | 858 | 622 | 83 | 1427 | 1248 | 120 | 1981 | 1898 | +| 10 | 259 | 80 | 47 | 873 | 639 | 84 | 1442 | 1266 | 121 | 1995 | 1916 | +| 11 | 278 | 92 | 48 | 889 | 655 | 85 | 1457 | 1283 | 122 | 2010 | 1934 | +| 12 | 296 | 105 | 49 | 905 | 672 | 86 | 1472 | 1300 | 123 | 2025 | 1951 | +| 13 | 314 | 118 | 50 | 920 | 688 | 87 | 1487 | 1318 | 124 | 2040 | 1969 | +| 14 | 332 | 131 | 51 | 936 | 705 | 88 | 1503 | 1335 | 125 | 2055 | 1987 | +| 15 | 349 | 145 | 52 | 952 | 721 | 89 | 1518 | 1353 | 126 | 2069 | 2005 | +| 16 | 367 | 159 | 53 | 967 | 738 | 90 | 1533 | 1370 | 127 | 2084 | 2023 | +| 17 | 384 | 173 | 54 | 983 | 755 | 91 | 1548 | 1387 | 128 | 2099 | 2041 | +| 18 | 401 | 187 | 55 | 998 | 771 | 92 | 1563 | 1405 | 129 | 2114 | 2058 | +| 19 | 419 | 201 | 56 | 1014 | 788 | 93 | 1578 | 1422 | 130 | 2128 | 2076 | +| 20 | 436 | 216 | 57 | 1029 | 805 | 94 | 1593 | 1440 | 131 | 2143 | 2094 | +| 21 | 453 | 230 | 58 | 1045 | 822 | 95 | 1608 | 1457 | 132 | 2158 | 2112 | +| 22 | 469 | 245 | 59 | 1060 | 838 | 96 | 1623 | 1475 | 133 | 2173 | 2130 | +| 23 | 486 | 260 | 60 | 1076 | 855 | 97 | 1638 | 1492 | 134 | 2187 | 2148 | +| 24 | 503 | 275 | 61 | 1091 | 872 | 98 | 1653 | 1510 | 135 | 2202 | 2166 | +| 25 | 520 | 290 | 62 | 1107 | 889 | 99 | 1668 | 1527 | 136 | 2217 | 2183 | +| 26 | 536 | 305 | 63 | 1122 | 906 | 100 | 1683 | 1545 | 137 | 2232 | 2201 | +| 27 | 553 | 320 | 64 | 1137 | 923 | 101 | 1698 | 1562 | 138 | 2246 | 2219 | +| 28 | 569 | 335 | 65 | 1153 | 940 | 102 | 1713 | 1580 | 139 | 2261 | 2237 | +| 29 | 585 | 351 | 66 | 1168 | 957 | 103 | 1728 | 1598 | 140 | 2276 | 2255 | +| 30 | 602 | 366 | 67 | 1184 | 974 | 104 | 1742 | 1615 | 141 | 2291 | 2273 | +| 31 | 618 | 382 | 68 | 1199 | 991 | 105 | 1757 | 1633 | 142 | 2305 | 2291 | +| 32 | 634 | 398 | 69 | 1214 | 1008 | 106 | 1772 | 1650 | 143 | 2320 | 2309 | +| 33 | 651 | 413 | 70 | 1229 | 1025 | 107 | 1787 | 1668 | 144 | 2335 | 2327 | +| 34 | 667 | 429 | 71 | 1245 | 1042 | 108 | 1802 | 1686 | 145 | 2349 | 2345 | +| 35 | 683 | 445 | 72 | 1260 | 1059 | 109 | 1817 | 1703 | 146 | 2364 | 2363 | +| 36 | 699 | 461 | 73 | 1275 | 1076 | 110 | 1832 | 1721 | *) note 2 in H.2.5 | | | + +NOTE 1: The first column is the number of errors (ne = number of NACK + statDTX). + +NOTE 2: The second column is the number of samples for the pass limit (nsp, ns=Number of Samples= number of NACK + statDTX + ACK). + +NOTE 3: The third column is the number of samples for the fail limit (nsf). + +NOTE 4: The UE could be decided as early pass/fail when at least 67 samples are received. The nsf is set to NA for ne less than 9. + +## H.2.5 Pass fail decision rules + +The pass fail decision rules apply for a single measurement. A test case is passed only when all the measurements in the test case are passed. + +Having observed 0 errors, pass the test at 67+ samples, otherwise continue + +Having observed 1 error, pass the test at 95+ otherwise continue + +Having observed 2 errors, pass the test at 119+ samples, otherwise continue + +etc. + +Having observed 14645 errors, pass the test at 23642349+ samples, fail the test at 2345- samples, otherwise continue + +Having observed 152 errors, pass the test at + samples, fail the test at 2363- samples. + +Where x+ means: x or more, x- means x or less. + +NOTE 1: An ideal DUT passes after 67 samples. The maximum test time is 2364 samples. + +NOTE 2: It is allowed to deviate from the early decision concept by postponing the decision (pass/fail or continue). Postponing the decision to or beyond the end of Table H.2.4-1 requires a pass fail decision against the test limit: pass the DUT for $ER < 0.0618$ , otherwise fail. + +## H.2.6 Theory to derive the pass fail limits (Informative) + +**Editor's note:** This clause of the Annex H is for information only and it describes the background theory and information for statistical testing. + +### H.2.6.1 Numerical definition of the pass-fail limits + +A statistical test is characterized by test time, selectivity and confidence level. The outcome of the statistical test is a decision. This decision may be correct, i.e., DUTs whose throughput is less than 95% maximum throughput being declared to fail, and DUTs whose throughput is higher or equal to 95% being declared to pass, or in-correct with opposite decision. The Confidence Level (CL) describes the probability that the decision is a correct one. The complement is the wrong decision probability (risk) $D = 1 - CL$ . + +As described in H.2.2, the measurement of throughput could be mapped to ER (Error Ratio). When testing ER, transport blocks or "samples" are observed and the number of correctly and erroneously received blocks are recorded. For a "standard" test, a pre-defined number of samples are observed, and a pass/fail decision is made based on the number of observed errors being above/below a threshold. This threshold is based on the targeted throughput or BLER and the design target CL. There is always some risk of a statistical variation leading to an incorrect pass/fail decision. The greater the number of samples that are recorded, the lower is the risk of such an error. The number of samples that are observed in a standard test is dimensioned to achieve an acceptable low risk of error (i.e., an acceptable high confidence level) for DUTs that just meet the specified limit. + +The standard test works well where the target ER level is relatively high and confidence level relatively low (both are chosen to be on a comparable order of magnitude). However, for relatively low ER testing the length of time required for observing sufficient samples to achieve a 95% confidence level is excessive. In many cases, the DUTs will in fact have a much lower true ER level than the target ER level, (in which case, the number of samples needed to achieve high confidence that the true ER level is lower than the limit is much smaller). On the other hand, a bad DUT which is expected to fail the requirement might have a much higher true ER level (in which case, errors occur more frequently and it can be demonstrated that the DUT is above the target ER limit with fewer samples). + +To avoid long test time, an alternative test method called early pass/fail is adopted. With the early pass/fail, each time a block error is encountered, a decision is made on whether the DUT can be passed/failed with 95% CL or the test needs to continue until another error is encountered. In the case of very good DUTs, the test can also be passed, when the number of samples permissible for one error event is reached and no error event is recorded. Pass/Fail is decided based on the total number of observed samples and errors, and a statistical calculation based on an inverse binomial cumulative distribution. The calculation involves one parameter, one variable and the result: + +- Parameter: d (per step decision probability). +- Variable: ne (number of observed errors). +- Result: ns (number of expected samples for pass/fail, depending on which one is calculated). + +The per step decision probability risk, d, expresses the probability of making an incorrect pass/fail decision in the current step (i.e., for the current decision coordinate). d is determined by simulation such that the overall risk of making a wrong decision over all steps of each test of a large number of tests on a large number of DUTs that exactly meet the target ER limit is $D = 5\%$ (and hence the CL 95%). + +It should be noted that d is determined separately considering early pass and early fail testing. + +For a marginal DUT (i.e., a DUT almost exactly meeting the target ER level), the unmodified early pass/early fail approach is unable to distinguish whether the DUT has just passed or just failed the BLER ( $\epsilon \rightarrow 0$ ), and can thus terminate with an "undecided" result. To avoid this undecided result and provide selectivity, a so-called "bad device factor" (M) is introduced into the early pass calculation. This factor biases the decision towards avoiding failing good DUT. + +## H.2.6.2 Simulation to derive the pass-fail limits for testing 95% throughput + +As per the description in clause H.2.2, the 95% throughput measurement is mapped to ER=0.05, where ER is $(\text{NACK} + \text{statDTX})/(\text{NACK} + \text{statDTX} + \text{ACK})$ . + +The binomial distribution and its inverse are used to design the pass and fail limits. Note that this method is not unique and that other methods exist. + +$$\text{fail}(ne, d_f) := \frac{ne}{ns_f} = \frac{ne}{(ne + \text{qnbinom}(d_f, ne, ER))}$$ + +$$\text{pass}(ne, cl_p, M) := \frac{ne}{ns_p} = \frac{ne}{(ne + \text{qnbinom}(cl_p, ne, ER \cdot M))}$$ + +Where + +- $\text{fail}(..)$ is the error ratio for the fail limit. +- $\text{pass}(..)$ is the error ratio for the pass limit. +- ER is the specified error ratio 5%. +- ne is the number of bad results. This is the variable in both equations. +- M is the Bad DUT factor $M=1.5$ . +- $d_f$ is the wrong decision probability of a single (ne, ns) co-ordinate for the fail limit. It is found by simulation to be $d_f = 0.006$ . +- $cl_p$ is the confidence level of a single (ne, ns) co-ordinate for the pass limit. It is found by simulation to be $cl_p = 0.9945$ . +- $\text{qnbinom}(..)$ : The inverse cumulative function of the negative binomial distribution. + +The simulation works as follows: + +- A large population of limit DUTs with true ER = 0.05 is decided against the pass and fail limits. +- $cl_p$ and $d_f$ are tuned such that CL (95 %) of the population passes and D (5 %) of the population fails. +- A population of Bad DUTs with true ER = $M \cdot 0.05$ is decided against the same pass and fail limits. +- $cl_p$ and $d_f$ are tuned such that CL (95 %) of the population fails and D (5 %) of the population passes. +- The number of DUTs decrease during the simulation, as the decided DUTs leave the population. That number decreases with an approximately exponential characteristics. After 146 bad results all DUTs of the population are decided. + +NOTE: The exponential decrease of the population is an optimal design goal for the decision co-ordinates (ne, ns), which can be achieved with other formulas or methods as well. + +## Annex I (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----|--------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-11 | RAN5#97 | R5-226639 | - | - | - | TP to add clause 1-3 to TS 38.521-5 | 0.0.0 | +| 2022-11 | RAN5#97 | R5-226640 | - | - | - | TP to add clause 4 to TS 38.521-5 | 0.0.0 | +| 2022-11 | RAN5#97 | R5-226641 | - | - | - | TP to add clause 5 to TS 38.521-5 | 0.0.0 | +| 2022-11 | RAN5#97 | R5-227885 | - | - | - | Text proposal for section 6, 6.1 and 6.2.1 in TS 38.521-5 | 0.0.0 | +| 2022-11 | RAN5#97 | R5-227886 | - | - | - | Text proposal for section 6.2.2 in TS 38.521-5 | 0.0.0 | +| 2023-03 | RAN5#98 | R5-231738 | - | - | - | Definition of NTN minimum output power test case 6.3.1 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231739 | - | - | - | Definition of NTN transmit OFF power test case 6.3.2 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231740 | - | - | - | Introduction of new test case 7.9 Spurious emissions and addition of main structure of section 7 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231741 | - | - | - | Introduction of general sections for demodulation performance test cases for NTN capable UEs | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231742 | - | - | - | Introduction of demodulation performance test cases for NTN capable UEs | 0.0.1 | +| 2023-03 | RAN5#98 | R5-230877 | - | - | - | Introduction of 6.5.3.1 for TS38.521-5 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-230878 | - | - | - | Introduction of 7.1 7.2 and 7.3 for TS38.521-5 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-230879 | - | - | - | Introduction of 6.5.3.2 for TS38.521-5 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231854 | - | - | - | Text configurations and requirements for section 6.2.1 and 6.2.2 | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231367 | - | - | - | Introduction of NTN TC 6.3.3 on Tx on-off time mask | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231368 | - | - | - | Introduction of NTN TC 6.5.2.2 on Spectrum emission mask | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231369 | - | - | - | Introduction of NTN TC 6.5.2.4 on ACLR | 0.0.1 | +| 2023-03 | RAN5#98 | R5-231383 | - | - | - | Introduction of NTN TC 7.6.3 on out of band blocking | 0.0.1 | +| 2023-06 | RAN5#99 | R5-232346 | - | - | - | Definition of NTN maximum input level test case 7.4 | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233567 | - | - | - | Introduction of new test case 7.5 Adjacent channel selectivity | 0.1.0 | +| 2023-06 | RAN5#99 | R5-232372 | - | - | - | Correction of referenced Annexes for test case 7.9 Spurious emissions | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233568 | - | - | - | Introduction of new Annexes | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233569 | - | - | - | Introduction of NTN AMPR tests | 0.1.0 | +| 2023-06 | RAN5#99 | R5-232519 | - | - | - | Introduction of NTN configured transmission power tests | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233570 | - | - | - | TP to add 2Rx PDSCH mapping type A test case for NTN UE | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233158 | - | - | - | Update General SE for NTN | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233571 | - | - | - | Updates to NTN TC 6.3.3 on Tx on-off time mask | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233572 | - | - | - | Updates to NTN TC 6.5.2.2 on Spectrum emission mask | 0.1.0 | +| 2023-06 | RAN5#99 | R5-233573 | - | - | - | Updates to NTN TC 6.5.2.4 on ACLR | 0.1.0 | +| 2023-09 | RAN5#100 | R5-235824 | - | - | - | MU and TT definition for NR NTN Min power and Off power test cases | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235825 | - | - | - | MU and TT definition for NR NTN Maximum Input level test case | 1.0.0 | +| 2023-09 | RAN5#100 | R5-234627 | - | - | - | NTN AMPR test configurations and requirements | 1.0.0 | +| 2023-09 | RAN5#100 | R5-234628 | - | - | - | Editorial change to move 6.2.4 in 38.521-5 | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235866 | - | - | - | Update Ref sensitivity for NTN | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235826 | - | - | - | Update TX Intermodulation for NTN | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235827 | - | - | - | Update TX Spur co-exist for NTN | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235456 | - | - | - | Clarifications to 38.521-5 | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235186 | - | - | - | Initial conditions update for multiple test cases | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235679 | - | - | - | Updates to NTN TC 6.3.3 on Tx on-off time mask | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235683 | - | - | - | Updates to NTN TC 6.5.2.2 on Spectrum emission mask | 1.0.0 | +| 2023-09 | RAN5#100 | R5-235681 | - | - | - | Updates to NTN TC 6.5.2.4 on ACLR | 1.0.0 | +| 2023-12 | RAN5#101 | R5-237874 | - | - | - | Addition of test configuration and error correction for 7.5 Adjacent channel selectivity | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237834 | - | - | - | Introduction of new test cases 7.7 Spurious response | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237835 | - | - | - | Introduction of new test cases 7.8 Intermodulation characteristics | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237836 | - | - | - | Addition of test configuration and error correction for 7.9 Spurious emissions | 1.1.0 | +| 2023-12 | RAN5#101 | R5-236147 | - | - | - | Introduction of Annex B.0 | 1.1.0 | +| 2023-12 | RAN5#101 | R5-236148 | - | - | - | Introduction of Annex D Characteristics of the interfering signal | 1.1.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN5#101 | R5-236149 | - | - | - | Introduction of measurement uncertainties and test tolerances for test cases from 7.5 to 7.9 | 1.1.0 | +| 2023-12 | RAN5#101 | R5-236150 | - | - | - | Introduction of Annex F.4 Uplink power window | 1.1.0 | +| 2023-12 | RAN5#101 | R5-236151 | - | - | - | Introduction of Annex H Statistical Testing | 1.1.0 | +| 2023-12 | RAN5#101 | R5-236291 | - | - | - | Further clarification on NR NTN conformance requirement specifications | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237690 | - | - | - | Adding Additional Spurious Emission TC for NTN | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237875 | - | - | - | Adding Frequency Error TC for NTN | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237864 | - | - | - | Core requirements alignment for NR NTN test cases | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237876 | - | - | - | Update to Refsens test case 7.3.2 for NTN | 1.1.0 | +| 2023-12 | RAN5#101 | R5-237877 | - | - | - | Update to PDSCH demodulation test cases for NTN | 1.1.0 | +| 2023-12 | RAN#102 | RP-233928 | - | - | - | presented at RAN#102 for approval | 2.0.0 | +| 2023-12 | RAN#102 | - | - | - | - | put under revision control as v17.0.0 with small editorial changes | 17.0.0 | +| 2023-12 | RAN#102 | RP-232785 | 0001 | - | F | Updates to spurious emissions UE coexistence test cases as part of introduction of Band 54 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38522/raw.md b/marked/Rel-18/38_series/38522/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f502c0ab7feefecef513c9b2214a445393d4b601 --- /dev/null +++ b/marked/Rel-18/38_series/38522/raw.md @@ -0,0 +1,4470 @@ + + +# 3GPP TS 38.522 V18.1.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) conformance specification; Applicability of radio transmission, radio reception and radio resource management test cases (Release 18)** --- + +Keywords +5GS, UE, terminal, testing + +**3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +# --- Contents + +| | | | +|---------------------------------------------------|----------------------------------------------------------------------------------------------|------------| +| 1 | Scope..... | 5 | +| 2 | References..... | 5 | +| 3 | Definitions, symbols and abbreviations..... | 6 | +| 3.1 | Definitions..... | 6 | +| 3.2 | Symbols..... | 7 | +| 3.3 | Abbreviations..... | 7 | +| 4 | Recommended test case applicability..... | 8 | +| 4.0 | Test case conditions and selection criteria..... | 9 | +| 4.0 | Test case conditions and selection criteria..... | 9 | +| 4.1 | RF conformance test cases..... | 27 | +| 4.1.1 | FR1 standalone conformance test cases..... | 28 | +| 4.1.2 | FR2 standalone conformance test cases..... | 48 | +| 4.1.3 | NR interworking between NR FR1 and NR FR2 and between NR and LTE conformance test cases..... | 67 | +| 4.1.4 | Performance conformance test cases..... | 103 | +| 4.2 | RRM conformance test cases..... | 120 | +| Annex A (informative): Change history..... | | 191 | + +## **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +The present document is one part of a multi-part Technical Specification (TS) covering the New Radio (NR) User Equipment (UE) conformance specification, which is divided in the following parts: + +3GPP TS 38.521-1 [1]: NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone; + +3GPP TS 38.521-2 [2]: NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone; + +3GPP TS 38.521-3 [3]: NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios; + +3GPP TS 38.521-4 [4]: NR; User Equipment conformance specification; Radio transmission and reception; Part 4: Performance; + +**3GPP TS 38.522: NR; User Equipment (UE) conformance specification; Applicability of RF and RRM test cases;** + +3GPP TS 38.533 [5]: NR; User Equipment (UE) conformance specification; Radio resource management; + +# --- 1 Scope + +The present document specifies the recommended applicability statement and completion status for the test cases included in 3GPP TS 38.521-1 [1], TS 38.521-2 [2], TS 38.521-3 [3], TS 38.521-4 [4] and TS 38.533 [5]. These applicability statements are based on the features implemented in the UE. + +Special conformance testing functions can be found in 3GPP TS 38.509 [6] and the common test environments are included in 3GPP TS 38.508-1 [7]. Common implementation conformance statement (ICS) proforma can be found in 3GPP TS 38.508-2 [8]. + +The present document is valid for UE implemented according to 3GPP releases starting from Release 15 up to the Release indicated on the cover page of the present document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document unless the context in which the reference is made suggests a different Release is relevant (information on the applicable release in a particular context can be found in e.g. test case title, description or applicability, message description or content). +- [1] 3GPP TS 38.521-1: NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone +- [2] 3GPP TS 38.521-2: NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone +- [3] 3GPP TS 38.521-3: NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios +- [4] 3GPP TS 38.521-4: NR; User Equipment conformance specification; Radio transmission and reception; Part 4: Performance +- [5] 3GPP TS 38.533: NR; User Equipment (UE) conformance specification; Radio resource management +- [6] 3GPP TS 38.509: 5GS; Special conformance testing functions for User Equipment (UE) +- [7] 3GPP TS 38.508-1: 5GS; User Equipment (UE) conformance specification; Part 1: Common test environment +- [8] 3GPP TS 38.508-2: 5GS; User Equipment (UE) conformance specification; Part 2: Common Implementation Conformance Statement (ICS) proforma +- [9] 3GPP TR 21.905: Vocabulary for 3GPP Specifications +- [10] 3GPP TS 36.521-2: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Implementation Conformance Statement (ICS) + +[11] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [9] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [9]. + +**DL\_nCC:** DL\_nCC(*table\_index*) includes all supported *n*-carrier CA/DC configurations in Table *table\_index* in TS 38.508-2 [8]. + +**DL\_NR\_nCC:** DL\_NR\_nCC(*table\_index*) includes all supported DC configurations with *n*-carrier NR DL CA configuration in Table *table\_index* in TS 38.508-2 [8]. + +**EIRP(Link=Link angle, Meas=Link angle):** measurement of the UE such that the link angle is aligned with the measurement angle. EIRP (indicator to be measured) can be replaced by EIS, Frequency, EVM, carrier Leakage, In-band emission and OBW. Beam peak search grids, TX beam peak direction, and RX beam peak direction can be selected to describe Link. + +**EIRP(Link=Link angle, Meas=beam peak direction):** measurement of the EIRP of the UE such that the measurement angle is aligned with the beam peak direction within an acceptable measurement error uncertainty. + +**Implementation Conformance Statement (ICS):** statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented + +**ICS proforma:** document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS + +**Implementation extra Information for Testing (IXIT):** A statement made by a supplier or implementer of an UEUT which contains or references all of the information (in addition to that given in the ICS) related to the UEUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the UEUT + +**Inter-band carrier aggregation:** Carrier aggregation of component carriers in different operating bands. + +NOTE: Carriers aggregated in each band can be contiguous or non-contiguous. + +**Intra-band contiguous carrier aggregation:** Contiguous carriers aggregated in the same operating band. + +**Intra-band non-contiguous carrier aggregation:** Non-contiguous carriers aggregated in the same operating band. + +**IXIT proforma:** A document, in the form of a questionnaire, which when completed for an UEUT becomes an IXIT + +**Protocol Implementation Conformance Statement (PICS):** An ICS for an implementation or system claimed to conform to a given protocol specification + +**Protocol Implementation eXtra Information for Testing (PIXIT):** An IXIT related to testing for conformance to a given protocol specification + +**Static conformance review:** A review of the extent to which the static conformance requirements are claimed to be supported by the UEUT, by comparing the answers in the ICS(s) with the static conformance requirements expressed in the relevant specification(s) + +**TRP(Link=Link angle):** measurement of the TRP of the UE such that the measurement angle is aligned with the beam peak direction within an acceptable measurement uncertainty. TX beam peak direction and RX beam peak direction can be selected to describe Link. + +NOTE: For requirements based on EIRP/EIS, the radiated interface boundary is associated to the far-field region + +**UL:** $UL(table\_index)$ includes all supported CA Configurations where at least one UL CA configuration was declared in column "Supported CA Bandwidth Class(es) in UL" in Table *table\_index* in TS 38.508-2 [8]. + +**UL\_nCC:** $UL\_nCC(table\_index)$ includes all supported CA Configurations where at least one *n*-carrier UL CA configuration was declared in column "Supported CA Bandwidth Class(es) in UL" in Table *table\_index* in TS 38.508-2 [8]. + +**UL\_NR\_nCC:** $UL\_NR\_nCC(table\_index)$ includes all supported DC Configurations where at least one DC configuration with *n*-carrier NR UL CA configuration was declared in column "Supported EN-DC Bandwidth Class(es) in UL" in Table *table\_index* in TS 38.508-2 [8]. + +**ULTxSwitching:** $ULTxSwitching(table\_index)$ includes all supported CA/DC/SUL Configurations where at least one uplink band pair was declared in column "Supported ULTxSwitching Band Pair" in Table *table\_index* in TS 38.508-2 [8]. + +## 3.2 Symbols + +No specific symbols have been identified so far. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [9] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [9]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-------------------------------------------| +| 5GS | 5G System | +| ACLR | Adjacent Channel Leakage Ratio | +| AWGN | Additive White Gaussian Noise | +| BFD | Beam Failure Detection | +| BPSK | Binary Phase Shift Keying | +| BWP | Bandwidth Part | +| CA | Carrier Aggregation | +| CBW | Channel Bandwidth | +| CC | Component Carrier | +| CCA | Clear Channel Assessment | +| CMR | Channel Measurement Resource | +| CQI | Channel Quality Indicator | +| CSI | Channel State Information | +| CSI-RS | CSI Reference Signal | +| DAPS | Dual Active Protocol Stack | +| DC | Dual Connectivity | +| DCI | Downlink Control Information | +| DL | Downlink | +| DRX | Discontinuous Reception | +| EIRP | Effective Isotropic Radiated Power | +| E-UTRA | Evolved UTRA | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| EN-DC | E-UTRA/NR Dual Connectivity | +| FR1 | Frequency Range 1 (410 MHz - 7125 MHz) | +| FR2 | Frequency Range 2 (24250 MHz - 52600 MHz) | +| HST | High Speed Train | +| ICS | Implementation Conformance Statement | + +| | | +|------------|-----------------------------------------------------------------------------------------------------| +| IMR | Interference Measurement Resource | +| IXIT | Implementation eXtra Information for Testing | +| L1 | Layer 1 | +| L1-RSRP | Layer 1 RSRP | +| L1 SL-RSRP | Layer 1 Sidelink RSRP which corresponds to PSCCH-RSRP and/or PSSCH-RSRP | +| MAC | Medium Access Control | +| MCG | Master Cell Group | +| MPR | Allowed maximum power reduction | +| NR | New Radio | +| NSA | Non-Standalone, a mode of operation where operation of another radio is assisted with another radio | +| PCell | Primary Cell | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PIXIT | Protocol Implementation eXtra Information for Testing | +| PMI | Pre-coding Matrix Indicator | +| PRACH | Physical Random Access Channel | +| PSCell | Primary SCG Cell | +| QAM | Quadrature Amplitude Modulation | +| RF | Radio Frequency | +| RLM | Radio Link Monitoring | +| RRC | Radio Resource Control | +| RRM | Radio Resource Management | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| SA | Standalone | +| SC | Single Carrier | +| SCC | Secondary Component Carrier | +| SCell | Secondary Cell | +| SCG | Secondary Cell Group | +| SCS | System Conformance Statement / Subcarrier Spacing | +| SDL | Supplementary Downlink | +| SFN | System Frame Number | +| SFTD | SFN and Frame Timing Difference | +| SINR | Signal to Interference plus Noise Ratio | +| SL | Sidelink | +| SL-MIMO | Sidelink-Multiple Antenna Transmission | +| SRS | Sounding Reference Signal | +| SRS-RSRP | Sounding Reference Signal based Reference Signal Received Power | +| SSB | Synchronization Signal Block | +| SS-RSRP | Synchronization Signal based RSRP | +| SS-RSRQ | Synchronization Signal based RSRQ | +| SS-SINR | Synchronization Signal based SINR | +| SUL | Supplementary UpLink | +| TC | Test Case | +| TDD | Time Division Duplex | +| TRP | Total Radiated Power | +| TxD | Tx Diversity | +| UEUT | User Equipment Under Test | +| UL | Uplink | +| ULFPTx | Uplink Full Power Transmission | +| UL MIMO | Uplink Multiple Antenna transmission | +| UTRA | UMTS Terrestrial Radio Access | +| V2X | Vehicle to Everything | + +# 4 Recommended test case applicability + +The applicability of each individual test is identified in the tables 4.1.1-1 / 4.1.2-1 / 4.1.3-1 / 4.1.4-1 / 4.2-1 / 4.2-2 / 4.2-3 / 4.2-4 / 4.2-5 / 4.2-6 / 4.2-7 / 4.2-8 / 4.2-9 / 4.2-10. This is just a recommendation based on the purpose for which the test case was written. + +The applicability of every test is formally expressed by the use of Boolean expressions that are based on parameters (ICS). The parameters (ICS) included in TS 38.508-2 [8] are used in the test case applicability condition without reference. Parameters (ICS) specified in TS 36.521-2 [10] shall be referred with proper reference. + +Selection criteria of tested bands and tested CA configurations for each applicable test is formally expressed using group theory based on parameters (ICS) included in annex A of TS 38.508-2 [8] without reference. + +Additional information related to the Test Case (TC), e.g. affecting its dynamic behaviour or its execution may be provided as well. + +The columns in tables 4.1.1-1 / 4.1.2-1 / 4.1.3-1 / 4.1.4-1 / 4.2-1 / 4.2-2 / 4.2-3 / 4.2-4 / 4.2-5 / 4.2-6 / 4.2-7 / 4.2-8 / 4.2-9 / 4.2-10 have the following meaning: + +## Clause + +The clause column indicates the clause number in TS 38.521-1 [1], TS 38.521-2 [2], TS 38.521-3 [3], TS 38.521-4 [4] and TS 38.533 [5] that contains the test body. + +## TC Title + +The TC Title column describes the name of the test and contains the clause title of the clause in TS 38.521-1 [1], TS 38.521-2 [2], TS 38.521-3 [3], TS 38.521-4 [4] and TS 38.533 [5] that contains the test body. + +## Release + +The release column indicates the earliest release from which each test case is applicable. It may also indicate a range of releases or a single release to which a test case is applicable. + +## Applicability - Condition + +The following notations are used for the applicability column: + +- | | | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R | recommended - the test case is recommended to all terminals supporting NR | +| O | optional - the test case is optional | +| N/A | not applicable - in the given context, the test case is not recommended. | +| C i | conditional - the test is recommended ("R") or not ("N/A") depending on the support of other items. "i" is an integer identifying a unique conditional status expression which is defined in Table 4.0-1. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." is used to avoid ambiguities. | + +## Applicability - Comment + +This comment column contains a verbal description of the condition included in the applicability column. + +## Tested Bands / CA/DC Configurations Selection + +This column defines a set of bands / CA/DC Configurations the test is to be run for, if the test is applicable. If the set is empty, the test is considered as not applicable. + +The following notations are used in the tested bands selection column: + +| | | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Di | Derive the set based on Band Selection Criteria Di defined in table 4.0-2. | +| Ei | Derive the set based on CA/DC Configurations Selection Criteria Ei defined in table 4.0-3. | +| TBD | Band selection not defined at this time, in the meantime test all Bands / CA/DC Configurations | +| Text | For more complex selection criteria, or if the criteria are already specified somewhere else in the spec, text reference to the clause is given. | + +### Branch + +This column contains indication if the test case may perform differently depending on the UE capabilities. + +NOTE 1: Void. + +NOTE 2: Void. + +## Additional Information + +This column contains indication if the test case may perform differently depending on the UE capabilities and the measurement execution. + +This column also contains indication of the completion status of the test case. + +## 4.0 Test case conditions and selection criteria + +For the purposes of the present document, the applicability of conformance test cases conditions given in Table 4.0-1 apply. The tested bands selection criteria given in Table 4.0-2 apply. The tested CA/DC configuration selection criteria given in Table 4.0-3 apply. The ICS proformas used in Table 4.0-1, Table 4.0-2 and Table 4.0-3 are defined in TS 38.508-2 [8] unless otherwise stated. + +**Table 4.0-1: Applicability of conformance test cases conditions** + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------| +| C001 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 THEN R ELSE N/A | +| C001a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.1-7/3 AND NOT A.4.3.2-1/84 THEN R ELSE N/A | +| C001b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C001c | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.3.1-2/2e OR A.4.3.1-2/12) THEN R ELSE N/A | +| C001d | Void | +| C001e | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C001f | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND (A.4.3.11-1/1 OR A.4.3.11-1/3) THEN R ELSE N/A | +| C001g | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.3.1-7/5 OR ((A.4.3.1-7/2 OR A.4.3.1-7/3) AND A.4.3.2-1/84)) THEN R ELSE N/A | +| C001h | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND NOT A.4.3.2-1/84 THEN R ELSE N/A | +| C001i | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/2 THEN R ELSE N/A | +| C001j | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/3 THEN R ELSE N/A | +| C001k | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/4 THEN R ELSE N/A | +| C001l | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND NOT A.4.3.2-1/84 AND NOT A.4.3.12-1/2 THEN R ELSE N/A | +| C001m | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.4-1/16 THEN R ELSE N/A | +| C002 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-2/3 OR A.4.1-2/5) THEN R ELSE N/A | +| C003 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/14 THEN R ELSE N/A | +| C003a | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/14 THEN R ELSE N/A | +| C003b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.3.2-1/58 OR A.4.3.2-1/59 OR A.4.3.2-1/60) THEN R ELSE N/A | +| C004 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-2/1 THEN R ELSE N/A | +| C004a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2B.1.0a.1-2/1 THEN R ELSE N/A | +| C005 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-4A/5 AND A.4.1-2/4 AND A.4.3.2A.1-1/1 AND A.4.1-3/1 THEN R ELSE N/A | +| C006 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 THEN R ELSE N/A | +| C006a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C006b | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/31a THEN R ELSE N/A | +| C006c | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C006d | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/2 THEN R ELSE N/A | +| C006e | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/3 THEN R ELSE N/A | +| C006f | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/4 THEN R ELSE N/A | +| C006g | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/5 THEN R ELSE N/A | +| C006h | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/6 THEN R ELSE N/A | +| C006i | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-1/7 THEN R ELSE N/A | +| C006j | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND NOT (A.4.3.2-1/22A OR A.4.3.2-1/22B) THEN R ELSE N/A | +| C006k | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.3.2-1/22A OR A.4.3.2-1/22B) THEN R ELSE N/A | +| C006l | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6/56A THEN R ELSE N/A | +| C006m | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/56 AND 4.3.2-1/78 THEN R ELSE N/A | +| C006n | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.3.2-1/130 OR A.4.3.2-1/131) THEN R ELSE N/A | +| C006o | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/25A THEN R ELSE N/A | +| C006p | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.1-4A/7 AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C006w | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/38 THEN R ELSE N/A | +| C007 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/22 THEN R ELSE N/A | + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------| +| C008 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND NOT (A.4.3.2-1/22) AND NOT (A.4.3.2-1/22A OR A.4.3.2-1/22B) THEN R ELSE N/A | +| C008a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND NOT (A.4.3.2-1/22) AND (A.4.3.2-1/22A OR A.4.3.2-1/22B) THEN R ELSE N/A | +| C009 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/1 AND A.4.3.2B.2.0-2/1 THEN R ELSE N/A | +| C009a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/1 AND A.4.3.2B.2.0-1/1 THEN R ELSE N/A | +| C009z | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/1 AND A.4.3.2B.2.0-2/1 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C010 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/2 AND A.4.3.2B.2.0-2/1 THEN R ELSE N/A | +| C010a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/2 AND A.4.3.2B.2.0-1/1 THEN R ELSE N/A | +| C010z | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/2 AND A.4.3.2B.2.0-2/1 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C011 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-2/1 THEN R ELSE N/A | +| C011a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-1/1 THEN R ELSE N/A | +| C011b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-2A/1 THEN R ELSE N/A | +| C011c | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-1A/1 THEN R ELSE N/A | +| C011d | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-2/2 AND A.4.3.2B.2.0-2A/1 THEN R ELSE N/A | +| C011z | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-2A/1 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C012 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2/1 THEN R ELSE N/A | +| C012a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-1A/1 THEN R ELSE N/A | +| C012b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | +| C012c | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/3 THEN R ELSE N/A | +| C012d | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/4 THEN R ELSE N/A | +| C012e | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | +| C012f | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2/1 AND A.4.3.2-1/31a THEN R ELSE N/A | +| C012g | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-1A/3 THEN R ELSE N/A | +| C012h | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-1A/4 THEN R ELSE N/A | +| C012i | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/5 THEN R ELSE N/A | +| C012j | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/6 THEN R ELSE N/A | +| C012k | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/7 THEN R ELSE N/A | +| C012l | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/8 THEN R ELSE N/A | +| C012m | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/2 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C012n | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/3 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C012o | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/4 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C012p | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2/1 AND A.4.3.2-1/14 THEN R ELSE N/A | +| C012q | IF A.4.1-1/2 AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/1 AND A.4.3.2-1/25A THEN R ELSE N/A | +| C012w | IF A.4.1-1/2 AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/1 AND A.4.3.2-1/38 THEN R ELSE N/A | +| C012z | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.1-4/4 AND A.4.3.2B.2.0-2A/1 AND A.4.3.2-1/25 THEN R ELSE N/A | +| C013 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (A.4.1-4/3 OR A.4.1-4/4) THEN R ELSE N/A | +| C014 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/4) THEN R ELSE N/A | +| C015 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C015b | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/6 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C015c | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/66 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C015d | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.9-1/3 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | + +| | | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C015x | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.9-1/1 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C015y | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/33 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C016 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C016b | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/6 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C016c | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/66 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C016d | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.9-1/3 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C016x | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.9-1/1 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C016y | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/20 AND A.4.3.2-1/33 AND A.4.3.2-1/68 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C017 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C017b | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) AND A.4.3.2-1/6 THEN R ELSE N/A | +| C017c | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) AND A.4.3.2-1/66 THEN R ELSE N/A | +| C017d | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2 AND A.4.3.9-1/3 THEN R ELSE N/A | +| C017g | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/1 AND (NOT A.4.3.9-1/2 AND (A.4.3.1-7a/2 OR A.4.3.1-7a/3)) THEN R ELSE N/A | +| C017h | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/2 AND (NOT A.4.3.9-1/2 AND (A.4.3.1-7a/2 OR A.4.3.1-7a/3)) THEN R ELSE N/A | +| C017i | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2A.1-1/3 AND (NOT A.4.3.9-1/2 AND (A.4.3.1-7a/2 OR A.4.3.1-7a/3)) THEN R ELSE N/A | +| C017j | Void | +| C017x | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) AND A.4.3.9-1/1 THEN R ELSE N/A | +| C017y | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) AND A.4.3.2-1/33 THEN R ELSE N/A | +| C017z | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.2-1/33 THEN R ELSE N/A | +| C018 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND 4.3.2-1/9 THEN R ELSE N/A | +| C019 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C019b | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.2-1/6 THEN R ELSE N/A | +| C019c | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.2-1/66 THEN R ELSE N/A | +| C019d | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND (A.4.3.9-4b/38 OR A.4.3.9-4b/41 OR A.4.3.9-4b/48 OR A.4.3.9-4b/77 OR A.4.3.9-4b/78 OR A.4.3.9-4b/79) OR (A.4.3.9-4b/34 OR A.4.3.9-4b/39 OR A.4.3.9-4b/40)) AND A.4.3.9-1/3 THEN R ELSE N/A | +| C019x | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.9-1/1 THEN R ELSE N/A | +| C019y | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.11-1/2 THEN R ELSE N/A | +| C020 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) THEN R ELSE N/A | +| C021 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 THEN R ELSE N/A | +| C021a | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C021b | IF A.4.1-1/1 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 THEN R ELSE N/A | +| C021c | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.11-1/6 THEN R ELSE N/A | +| C021d | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.11-1/7 THEN R ELSE N/A | + +| | | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C021e | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.6-1/79 THEN R ELSE N/A | +| C022 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 THEN R ELSE N/A | +| C022a | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C022b | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6/56A THEN R ELSE N/A | +| C022e | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.6-1/79 THEN R ELSE N/A | +| C022m | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/56 AND 4.3.2-1/78 THEN R ELSE N/A | +| C022n | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND (A.4.3.2-1/130 OR A.4.3.2-1/131) THEN R ELSE N/A | +| C023 | IF A.4.1-4/5 AND A.4.1-3/2 THEN R ELSE N/A | +| C023a | IF A.4.1-4/5 AND A.4.1-3/2 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C024 | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 THEN R ELSE N/A | +| C025 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 THEN R ELSE N/A | +| C025a | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C025b | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND (A.4.3.11-1/1 OR A.4.3.11-1/4) THEN R ELSE N/A | +| C025c | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.5-1/1 AND (A.4.3.11-1/1 OR A.4.3.11-1/4) THEN R ELSE N/A | +| C025d | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.11-1/5 THEN R ELSE N/A | +| C025e | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.11-1/5 THEN R ELSE N/A | +| C025f | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.1-2/7 AND A.4.3.6-1/61 THEN R ELSE N/A | +| C025g | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.1-2/8 AND A.4.3.6-1/62 THEN R ELSE N/A | +| C026 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND 4.3.6-1/11 THEN R ELSE N/A | +| C027 | Void | +| C028 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND 4.3.6-1/11 THEN R ELSE N/A | +| C029 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND 4.3.2-1/9 THEN R ELSE N/A | +| C030 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/9 THEN R ELSE N/A | +| C030a | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/9 THEN R ELSE N/A | +| C031 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C031a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/1 AND A.4.3.6-1/54 THEN R ELSE N/A | +| C031b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/3 AND A.4.1-4/7 AND A.4.3.6-1/55 THEN R ELSE N/A | +| C031c | IF (A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.1-4A/6 AND A.4.3.2A.1-1/1) THEN R ELSE N/A | +| C032 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND (A.4.1-2/3 OR A.4.1-2/5) THEN R ELSE N/A | +| C033 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/2 THEN R ELSE N/A | +| C034 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/6 THEN R ELSE N/A | +| C035 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/6 THEN R ELSE N/A | +| C036 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/3 THEN R ELSE N/A | +| C037 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/41 THEN R ELSE N/A | +| C037a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/41 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C037b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.6-1/79 THEN R ELSE N/A | +| C038 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.3.6-1/41 THEN R ELSE N/A | +| C038a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.3.6-1/41 AND A.4.3.5-1/1 THEN R ELSE N/A | + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C039 | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4/5 OR A.4.1-4/7) AND A.4.1-5/1 AND A.4.3.6-1/41 THEN R ELSE N/A | +| C040 | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.3.6-1/41 THEN R ELSE N/A | +| C041 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 THEN R ELSE N/A | +| C041a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C041b | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C042 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.3.2-1/34 AND A.4.3.6-1/41 THEN R ELSE N/A | +| C042a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C042b | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C043 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND (A.4.3.6-1/43 OR A.4.3.6-1/44) THEN R ELSE N/A | +| C043a | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/34 AND A.4.3.6-1/41a AND A.4.3.5-1/1 THEN R ELSE N/A | +| C044 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/42 THEN R ELSE N/A | +| C045 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.3.2B.2.0-1/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) THEN R ELSE N/A | +| C046 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.3.2B.2.0-1/3 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 ) THEN R ELSE N/A | +| C047 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.3.2B.2.0-1/4 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) THEN R ELSE N/A | +| C048 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.3.2B.2.0-1/2 AND A.4.1-4/1 THEN R ELSE N/A | +| C049 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND A.4.3.2B.2.0-1/3 AND A.4.1-4/1 THEN R ELSE N/A | +| C050 | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.1-7/3 AND A.4.3.2-1/36 AND NOT A.4.3.2-1/84 THEN R ELSE N/A | +| C051 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-4A/5 AND A.4.3.2A.1-2/1 AND A.4.3.2-1/37 THEN R ELSE N/A | +| C051a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-4A/5 AND A.4.3.2A.1-2/1 AND A.4.3.2-1/37 AND A.4.3.6-1/80 THEN R ELSE N/A | +| C051b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-4A/5 AND A.4.3.2A.1-2/1 AND A.4.3.2-1/127 THEN R ELSE N/A | +| C051c | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-4A/5 AND A.4.3.2A.1-2/1 AND A.4.3.2-1/127 AND A.4.3.6-1/80 THEN R ELSE N/A | +| C051d | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/5) AND A.4.3.2A.1-2/2 AND A.4.3.2-1/37 THEN R ELSE N/A | +| C051e | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/5) AND A.4.3.2A.1-2/2 AND A.4.3.2-1/37 AND A.4.3.6-1/80 THEN R ELSE N/A | +| C051f | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/5) AND A.4.3.2A.1-2/2 AND A.4.3.2-1/127 THEN R ELSE N/A | +| C051g | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/5) AND A.4.3.2A.1-2/2 AND A.4.3.2-1/127 AND A.4.3.6-1/80 THEN R ELSE N/A | +| C052 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.3.11-1/1 OR A.4.3.11-1/3) THEN R ELSE N/A | +| C052a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.11-1/8 THEN R ELSE N/A | +| C052b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.11-1/6 THEN R ELSE N/A | +| C052c | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.11-1/7 THEN R ELSE N/A | +| C053 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/1 THEN R ELSE N/A | +| C054 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/2 THEN R ELSE N/A | +| C055 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/3 THEN R ELSE N/A | + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C056 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/4 THEN R ELSE N/A | +| C057 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/5 THEN R ELSE N/A | +| C058 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/6 THEN R ELSE N/A | +| C059 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4) AND A.4.3.2A.1-2/7 THEN R ELSE N/A | +| C060 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/14 THEN R ELSE N/A | +| C061 | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) THEN R ELSE N/A | +| C061a | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2A.1-1 THEN R ELSE N/A | +| C061b | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2A.1-2 THEN R ELSE N/A | +| C062c | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.9-1/1 THEN R ELSE N/A | +| C063 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND (A.4.1-4/3 OR A.4.1-4/2) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | +| C064 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND (A.4.1-4/3 OR A.4.1-4/2) AND A.4.3.2B.2.0-1A/3 THEN R ELSE N/A | +| C064a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND (A.4.1-4/3 OR A.4.1-4/2) AND A.4.3.2B.2.0-1A/4 THEN R ELSE N/A | +| C064b | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/2 AND (A.4.1-4/3 OR A.4.1-4/2) AND A.4.3.2B.2.0-1A/5 THEN R ELSE N/A | +| C065 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND (A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) THEN R ELSE N/A | +| C065a | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND (A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C065b | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND (A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) THEN R ELSE N/A | +| C065c | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND (A.4.3.2-1/42b OR A.4.3.2-1/43b) THEN R ELSE N/A | +| C065d | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND (A.4.3.2-1/24B OR A.4.3.2-1/24C) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C066 | IF A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) THEN R ELSE N/A | +| C066a | IF A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C066b | IF A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) THEN R ELSE N/A | +| C066c | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/2 AND (A.4.3.2-1/42b OR A.4.3.2-1/43b) THEN R ELSE N/A | +| C066d | IF A.4.1-2/7 AND A.4.1-3/1 AND (A.4.3.2-1/24B OR A.4.3.2-1/24C) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C066e | IF A.4.1-2/7 AND A.4.1-3/1 AND (A.4.3.2-1/24B OR A.4.3.2-1/24C) AND A.4.3.2A.1-1/2 THEN R ELSE N/A | +| C067 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.1-3/2 THEN R ELSE N/A | +| C068 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND [10] A.4.6-1/1 AND A.4.1-3/2 THEN R ELSE N/A | +| C069 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/6 THEN R ELSE N/A | +| C070 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/41 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C071 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/41 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C072 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/41 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C073 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/41 AND A.4.3.1-7a/3 THEN R ELSE N/A | + +| | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C074 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/39 AND A.4.3.2-1/40 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C075 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/39 AND A.4.3.2-1/40 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C076 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/39 AND A.4.3.2-1/40 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C077 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/39 AND A.4.3.2-1/40 AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C078 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-2/3 OR A.4.1-2/5) AND A.4.1-4A/1 AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C079 | IF A.4.1-1/3 AND A.4.1-2/7 THEN R ELSE N/A | +| C079a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-1/3 AND A.4.1-2/7 THEN R ELSE N/A | +| C080 | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND A.4.1-1/2 AND A.4.1-2/8 THEN R ELSE N/A | +| C080a | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND A.4.1-1/2 AND A.4.1-2/8 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C081 | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND (A.4.1-3/2 OR A.4.1-3/5) AND (A.4.3.6-1/46 OR A.4.3.6-1/47) THEN R ELSE N/A | +| C081a | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND (A.4.1-3/2 OR A.4.1-3/5) AND ([10]A.4.4-1a/5 OR [10]A.4.4-1b/5) AND (A.4.3.6-1/46 OR A.4.3.6-1/47) THEN R ELSE N/A | +| C082 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/63 AND A.4.3.2-1/65 THEN R ELSE N/A | +| C082a | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/63 AND A.4.3.2-1/65 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C083 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 THEN R ELSE N/A | +| C083a | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C084 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/63 AND A.4.3.2-1/65 THEN R ELSE N/A | +| C084a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/63 AND A.4.3.2-1/65 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C085 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 THEN R ELSE N/A | +| C085a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C086 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-2/7 THEN R ELSE N/A | +| C086a | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-2/7 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C087 | Void | +| C088 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND NOT A.4.3.1-7a/2 AND A.4.3.5-1/1 AND A.4.3.5-1/5 THEN R ELSE N/A | +| C089 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) AND A.4.3.5-1/1 AND A.4.3.5-1/5 THEN R ELSE N/A | +| C090 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND NOT A.4.3.1-7a/3 AND A.4.3.5-1/1 AND A.4.3.5-1/5 THEN R ELSE N/A | +| C091 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.5-1/1 AND A.4.3.5-1/5 THEN R ELSE N/A | +| C092 | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.5-1/1 AND A.4.3.5-1/5 THEN R ELSE N/A | +| C093 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/45 THEN R ELSE N/A | +| C094 | IF ((A.4.1-1/1 AND A.4.1-1/1) OR (A.4.1-1/1 AND A.4.1-1/2) OR (A.4.1-1/2 AND A.4.1-1/1) OR (A.4.1-1/2 AND A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.6-1/45 THEN R ELSE N/A | +| C095 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6-1/45 THEN R ELSE N/A | +| C095a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6-1/54 AND A.4.3.7-1/19 AND A.4.4-1/16 THEN R ELSE N/A | +| C096 | IF ((A.4.1-1/1 OR A.4.1-1/2) AND [10] A.4.1-1/3) THEN R ELSE N/A | + +| | | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C097 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-2/7 AND A.4.1-3/2 AND A.4.3.5-1/1 AND (A.4.3.11-1/1 OR A.4.3.11-1/3) THEN R ELSE N/A | +| C098 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.5-1/1 AND (A.4.3.11-1/1 OR A.4.3.11-1/3) THEN R ELSE N/A THEN R ELSE N/A | +| C099 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.11-1/2 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C100 | IF A.4.1-1/3 AND A.4.1-2/7 AND A.4.3.10-1/3 THEN R ELSE N/A | +| C101 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/9 THEN R ELSE N/A | +| C102 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/16 THEN R ELSE N/A | +| C103 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.8-1/15 AND A.4.3.8-1/18 THEN R ELSE N/A | +| C104 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.8-1/17 AND A.4.3.8-1/18 THEN R ELSE N/A | +| C105 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/11 THEN R ELSE N/A | +| C106 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.8-1/11 THEN R ELSE N/A | +| C107 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/15 THEN R ELSE N/A | +| C108 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/17 THEN R ELSE N/A | +| C109 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/15 AND A.4.3.8-1/18 THEN R ELSE N/A | +| C110 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.8-1/17 AND A.4.3.8-1/18 THEN R ELSE N/A | +| C111 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/31 AND A.4.3.2-1/57 AND NOT A.4.3.2-1/84 THEN R ELSE N/A | +| C112 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/31 AND A.4.3.2-1/57 AND (A.4.1-2/3 OR A.4.1-2/5) THEN R ELSE N/A | +| C113 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/53 AND A.4.3.2-1/56 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C113a | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/53 AND A.4.3.2-1/56 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C113b | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/53 AND A.4.3.2-1/56 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C113c | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/53 AND A.4.3.2-1/56 AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C114 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/54 AND A.4.3.2-1/56 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C114a | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/54 AND A.4.3.2-1/56 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C114b | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/54 AND A.4.3.2-1/56 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C114c | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/54 AND A.4.3.2-1/56 AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C115 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/55 AND A.4.3.2-1/56 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C115a | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/55 AND A.4.3.2-1/56 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C115b | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/55 AND A.4.3.2-1/56 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C115c | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/55 AND A.4.3.2-1/56 AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C116 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/61 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C117 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/61 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C118 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/61 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C119 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/61 AND A.4.3.1-7a/3 THEN R ELSE N/A | + +| | | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C120 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/12 AND A.4.3.2-1/39 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C121 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/62 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C122 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/12 AND A.4.3.2-1/39 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C123 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/62 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C124 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/12 AND A.4.3.2-1/39 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C125 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/12 AND A.4.3.2-1/39 AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C126 | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) and A.4.3.2-1/3 THEN R ELSE N/A | +| C126a | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/2 AND A.4.1-4/3 AND A.4.3.2B.2.0-2A/1 AND A.4.3.2-1/37 THEN R ELSE N/A | +| C127 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.11-1/2 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C127a | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2A.1-1/1 AND A.4.3.11-1/2 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) OR (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C128 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/67 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C129 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/67 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C130 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/67 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C131 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/67 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C132 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A THEN R ELSE N/A | +| C133 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/74 THEN R ELSE N/A THEN R ELSE N/A | +| C134 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/71 AND A.4.3.2-1/72 THEN R ELSE N/A THEN R ELSE N/A | +| C135 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | +| C136 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.2-1/73 THEN R ELSE N/A | +| C137 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.2-1/71 AND A.4.3.2-1/75 THEN R ELSE N/A | +| C138 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | +| C139 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/74 THEN R ELSE N/A | +| C140 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/71 AND A.4.3.2-1/72 THEN R ELSE N/A | +| C141 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | +| C141a | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | +| C141b | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | +| C142 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.2-1/73 THEN R ELSE N/A | +| C142a | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/74 THEN R ELSE N/A | +| C143 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.2-1/71 AND A.4.3.2-1/75 THEN R ELSE N/A | +| C143a | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/71 AND A.4.3.2-1/75 THEN R ELSE N/A | +| C144 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | + +| | | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C144a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/71 AND A.4.3.2-1/76 THEN R ELSE N/A | +| C145 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/74 THEN R ELSE N/A | +| C145a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.2-1/73 THEN R ELSE N/A | +| C146 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/71 AND A.4.3.2-1/72 THEN R ELSE N/A | +| C146a | IF A.4.1-1/1 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.2-1/71 AND A.4.3.2-1/75 THEN R ELSE N/A | +| C147 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/64 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C148 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.2-1/64 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C149 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/64 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C150 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.2-1/64 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C151 | Void | +| C152 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND A.4.3.1-7a/1 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C152a | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND A.4.3.2A.1-1/1 AND A.4.3.1-7a/1 AND NOT A.4.3.1-7a/2 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C152b | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND A.4.3.11-1/2 AND A.4.3.1-7a/1 AND NOT A.4.3.1-7a/2 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C153 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C154 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C154a | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND A.4.3.2A.1-1/1 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) OR (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C155 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/56 AND A.4.3.2-1/78 AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C156 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/79 AND NOT A.4.3.2-1/84 THEN R ELSE N/A | +| C157 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/46 THEN R ELSE N/A | +| C158 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/46 THEN R ELSE N/A | +| C159 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/46 THEN R ELSE N/A | +| C160 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/46 THEN R ELSE N/A | +| C161 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/41a THEN R ELSE N/A | +| C162 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/41a AND A.4.3.5-1/1 THEN R ELSE N/A | +| C163 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.6-1/41a AND A.4.3.2-1/34 THEN R ELSE N/A | +| C164 | IF (A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1) AND A.4.3.6-1/41a THEN R ELSE N/A | +| C165 | IF (A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1) AND A.4.3.6-1/41a AND A.4.3.5-1/1 THEN R ELSE N/A | +| C166 | IF (A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1) AND A.4.3.6-1/41a AND A.4.3.2-1/34 THEN R ELSE N/A | +| C167 | IF (A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1) AND A.4.3.6-1/41a AND A.4.3.6-1/41a AND A.4.3.2-1/34 THEN R ELSE N/A | +| C168 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/42 THEN R ELSE N/A | +| C169 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/62 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C170 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/62 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C171 | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/12 AND A.4.3.2-1/39 THEN R ELSE N/A | +| C172 | IF A.4.1-1/2 AND A.4.1-2/8 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/6 THEN R ELSE N/A | +| C173 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C174 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.2-1/77 THEN R ELSE N/A | + +| | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C175 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C176 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.2-1/77 THEN R ELSE N/A | +| C177 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 THEN R ELSE N/A | +| C177a | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C177b | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C177c | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C177d | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C178 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-2/3 OR A.4.1-2/5) AND A.4.3.2-1/37 THEN R ELSE N/A | +| C179 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-2/3 OR A.4.1-2/5) AND (A.4.3.2-1/14) THEN R ELSE N/A | +| C179a | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-2/3 OR A.4.1-2/5) AND A.4.3.2-1/14 THEN R ELSE N/A | +| C180 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND (A.4.1-4A/3 OR A.4.1-4A/4 OR A.4.1-4A/6) AND A.4.1-3/2 THEN R ELSE N/A | +| C181 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C182 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C183 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C184 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C185 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND 4.3.2-1/9 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C186 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND 4.3.2-1/9 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C187 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/46 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C188 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/46 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C189 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C190 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C191 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/63 AND A.4.3.2-1/65 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C192 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/63 AND A.4.3.2-1/65 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C193 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C194 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C195 | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C196 | IF A.4.1-1/1 AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C197 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 THEN R ELSE N/A | +| C198 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.12-1/2 THEN R ELSE N/A | +| C199 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.12-1/2 THEN R ELSE N/A | +| C200 | IF (A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND NOT A.4.3.1-7a/2) AND A.4.3.2-1/104 THEN R ELSE N/A | +| C201 | IF (A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND NOT A.4.3.1-7a/3) AND A.4.3.2-1/105 THEN R ELSE N/A | + +| | | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C202 | IF (A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2)) AND A.4.3.2-1/106 THEN R ELSE N/A | +| C203 | IF (A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) AND A.4.3.2-1/107 THEN R ELSE N/A | +| C204 | IF ((A.4.1-3/1 AND A.4.3.2-2/3 AND A.4.3.2-2/6 AND A.4.3.2-2/7) OR ((A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3)) AND A.4.1-1/2 AND (A.4.3.2-2/8 OR A.4.3.2/9) AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C205 | IF ((A.4.1-3/1 AND A.4.3.2-2/3 AND A.4.3.2-2/6 AND A.4.3.2-2/7) OR ((A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3)) AND A.4.1-1/2 AND (A.4.3.2-2/8 OR A.4.3.2/9) AND A.4.3.1-7a/3 THEN R ELSE N/A | +| C206 | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10 AND A.4.3.2-2/12) OR (A.4.3.2-2/9 AND A.4.3.2-2/11 AND A.4.3.2-2/13)) THEN R ELSE N/A | +| C206a | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10 AND A.4.3.2-2/12) OR (A.4.3.2-2/9 AND A.4.3.2-2/11 AND A.4.3.2-2/13)) AND A.4.3.5-1/1 THEN R ELSE N/A | +| C206b | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10 AND A.4.3.2-2/12 AND A.4.3.2-2/14) OR (A.4.3.2-2/9 AND A.4.3.2-2/11 AND A.4.3.2-2/13 AND A.4.3.2-2/15)) THEN R ELSE N/A | +| C206c | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10 AND A.4.3.2-2/12 AND A.4.3.2-2/14) OR (A.4.3.2-2/9 AND A.4.3.2-2/11 AND A.4.3.2-2/13 AND A.4.3.2-2/15)) AND A.4.3.5-1/1 THEN R ELSE N/A | +| C207 | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10) OR (A.4.3.2-2/9 AND A.4.3.2-2/11)) AND (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) THEN R ELSE N/A | +| C207a | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10) OR (A.4.3.2-2/9 AND A.4.3.2-2/11)) AND (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C207b | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10) OR (A.4.3.2-2/9 AND A.4.3.2-2/11)) AND (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a) THEN R ELSE N/A | +| C207c | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND ((A.4.3.2-2/8 AND A.4.3.2-2/10) OR (A.4.3.2-2/9 AND A.4.3.2-2/11)) THEN R ELSE N/A | +| C207d | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND (A.4.3.2-2/10 OR A.4.3.2-2/11) THEN R ELSE N/A | +| C207e | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND (A.4.3.2-2/10 OR A.4.3.2-2/11) AND A.4.3.5-1/1 THEN R ELSE N/A | +| C207f | IF A.4.1-1/2 AND A.4.1-2/7 AND A.4.1-3/2 AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.3.2-2/2 AND A.4.3.2-2/6 AND (A.4.3.2-2/10 OR A.4.3.2-2/11) AND A.4.3.2-2/20 THEN R ELSE N/A | +| C208 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.3.12-1/8 THEN R ELSE N/A | +| C209 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.3.12-1/8 THEN R ELSE N/A | +| C210 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.3.12-1/8 THEN R ELSE N/A | +| C211 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.3.12-1/8 THEN R ELSE N/A | +| C212 | IF A.4.3.2-1/109 OR A.4.3.7-1/49 THEN R ELSE N/A | +| C213 | IF A.4.3.2-1/108 OR A.4.3.7-1/49 THEN R ELSE N/A | +| C214 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/4 THEN R ELSE N/A | +| C215 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 THEN R ELSE N/A | + +| | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C216 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/4 THEN R ELSE N/A | +| C217 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 THEN R ELSE N/A | +| C218 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND Table A.4.3.1-7a/4 THEN R ELSE N/A | +| C219 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND Table A.4.3.1-7a/1 THEN R ELSE N/A | +| C220 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.5-1/1 AND Table A.4.3.1-7a/4 THEN R ELSE N/A | +| C221 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/41 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.5-1/1 AND Table A.4.3.1-7a/1 THEN R ELSE N/A | +| C222 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/4 THEN R ELSE N/A | +| C223 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 THEN R ELSE N/A | +| C224 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND 4.3.2-1/9 THEN R ELSE N/A | +| C225 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.2-1/46 THEN R ELSE N/A | +| C226 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.2-1/63 AND A.4.3.2-1/65 THEN R ELSE N/A | +| C227 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.6-1/41a THEN R ELSE N/A | +| C228 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.2-1/64 AND A.4.3.2-1/65 AND A.4.3.6-1/41a AND A.4.3.5-1/1 THEN R ELSE N/A | +| C229 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/41a AND A.4.3.5-1/1 AND A.4.3.2-1/34 THEN R ELSE N/A | +| C230 | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND (A.4.1-1/1 OR A.4.1-1/2 OR A.4.3.12-1/5) AND A.4.1-3/1 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 AND (NOT A.4.3.6-1/2) THEN R ELSE N/A | +| C231 | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND (A.4.1-1/1 OR A.4.1-1/2 OR A.4.3.12-1/5) AND A.4.1-3/1 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 AND A.4.3.6-1/2 AND A.4.3.6-1/11 THEN R ELSE N/A | +| C232 | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND (A.4.1-1/1 OR A.4.1-1/2 OR A.4.3.12-1/5) AND A.4.1-3/1 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 AND (NOT A.4.3.6-1/2) AND A.4.3.5-1/1 THEN R ELSE N/A | +| C233 | IF ([10]A.4.1-1/1 OR [10]A.4.1-1/2) AND (A.4.1-1/1 OR A.4.1-1/2 OR A.4.3.12-1/5) AND A.4.1-3/1 AND A.4.3.12-1/2 AND Table A.4.3.1-7a/1 AND A.4.3.6-1/2 AND A.4.3.6-1/11 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C234 | IF [10]A.4.1-1/1 OR [10]A.4.1-1/2) AND A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND (NOT A.4.3.6-1/2) THEN R ELSE N/A | +| C235 | IF [10]A.4.1-1/1 OR [10]A.4.1-1/2) AND A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/2 THEN R ELSE N/A | +| C236 | IF [10]A.4.1-1/1 OR [10]A.4.1-1/2) AND A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND (NOT A.4.3.6-1/2) AND A.4.3.5-1/1 THEN R ELSE N/A | +| C237 | IF [10]A.4.1-1/1 OR [10]A.4.1-1/2) AND A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/2 AND A.4.3.5-1/1 THEN R ELSE N/A | +| C238 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/41a AND A.4.3.2-1/34 THEN R ELSE N/A | +| C239 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.12-1/8 THEN R ELSE N/A | +| C240 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.11-1/10 THEN R ELSE N/A | +| C240a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.11-1/10 AND A.4.3.11-1/9 THEN R ELSE N/A | +| C241 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2A.1-1/1 AND A.4.3.5-1/13 THEN R ELSE N/A | +| C242 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND (A.4.1-4A/3 OR A.4.1-4A/4 OR A.4.1-4A/6) AND A.4.1-3/2 AND A.4.3.2B.2.0-1A/2 AND A.4.3.5-1/12 THEN R ELSE N/A | +| C243 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.1-3/2 AND A.4.3.2B.2.0-1A/2 AND A.4.3.5-1/12 THEN R ELSE N/A | +| C244 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/1 AND A.4.3.5-1/13 THEN R ELSE N/A | +| C245 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/119 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | + +| | | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C246 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/120 AND NOT A.4.3.1-7a/2 THEN R ELSE N/A | +| C247 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/119 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C248 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/120 AND NOT A.4.3.1-7a/3 THEN R ELSE N/A | +| C249 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/119 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C250 | IF A.4.1-1/1 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/120 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/2) THEN R ELSE N/A | +| C251 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/119 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C252 | IF A.4.1-1/2 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.2-1/120 AND (NOT A.4.3.9-1/2 AND A.4.3.1-7a/3) THEN R ELSE N/A | +| C253 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.6-1/68 AND A.4.3.6-1/72 AND (NOT A.4.3.6-1/70) THEN R ELSE N/A | +| C254 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND A.4.3.6-1/68 AND A.4.3.6-1/72 AND A.4.3.6-1/70 THEN R ELSE N/A | +| C255 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/68 AND A.4.3.6-1/72 AND (NOT A.4.3.6-1/70) THEN R ELSE N/A | +| C256 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND A.4.3.6-1/68 AND A.4.3.6-1/72 AND A.4.3.6-1/70 THEN R ELSE N/A | +| C257 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-5/1 AND A.4.3.6-1/66 AND A.4.3.6-1/69 THEN R ELSE N/A | +| C258 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/1 AND A.4.3.6-1/68 AND A.4.3.6-1/72 THEN R ELSE N/A | +| C259 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND A.4.3.6-1/73 THEN R ELSE N/A | +| C260 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND A.4.3.6-1/74 THEN R ELSE N/A | +| C261 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.1-7a/1 AND NOT A.4.3.1-7a/2 AND NOT A.4.3.1-7a/3 AND A.4.3.2A.1-1/1 THEN R ELSE N/A | +| C262 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.1-7a/1 AND NOT A.4.3.1-7a/2 AND NOT A.4.3.1-7a/3 AND A.4.3.2A.1-1/2 THEN R ELSE N/A | +| C263 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND (A.4.1-3/1 OR A.4.1-3/2 OR A.4.1-3/3 OR A.4.1-3/5) AND A.4.3.1-7a/1 AND NOT A.4.3.1-7a/2 AND NOT A.4.3.1-7a/3 AND A.4.3.2A.1-1/3 THEN R ELSE N/A | +| C264 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/63 THEN R ELSE N/A | +| C265 | IF ((A.4.1-1/1 AND [10]A.4.1-1/1) OR (A.4.1-1/1 AND [10]A.4.1-1/2) OR (A.4.1-1/2 AND [10]A.4.1-1/1) OR (A.4.1-1/2 AND [10]A.4.1-1/2)) AND A.4.1-3/1 AND A.4.3.6-1/63 AND A.4.3.6-1/65 THEN R ELSE N/A | +| C266 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/63 AND A.4.3.6-1/67 THEN R ELSE N/A | +| C267 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.1-3/2 AND A.4.3.2B.2.0-1A/2 AND A.4.3.2-1/128 THEN R ELSE N/A | +| C268 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3) AND A.4.1-3/2 AND A.4.3.2-1/129 THEN R ELSE N/A | +| C268a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/2 AND A.4.1-4A/4 AND A.4.3.2-1/129 THEN R ELSE N/A | +| C268b | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.1-4/6 AND A.4.3.2-1/130 THEN R ELSE N/A | +| C269 | IF A.4.1-1/2 AND A.4.1-4/5 AND A.4.1-3/2 AND A.4.3.2B.2.0-1A/2 AND A.4.3.2-1/128 THEN R ELSE N/A | +| C270 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND (A.4.1-4A/1 OR A.4.1-4A/2 OR A.4.1-4A/5) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/128 THEN R ELSE N/A | +| C271 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.1-4A/3 AND A.4.3.2A.1-1/1 AND A.4.3.2-1/128 THEN R ELSE N/A | +| C271a | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.1-4A/6 AND A.4.3.2A.1-1/1 AND A.4.3.2-1/128 THEN R ELSE N/A | +| C272 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/63 AND A.4.3.2-1/65 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | + +| | | +|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C273 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/63 AND A.4.3.2-1/65 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C274 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C275 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND (A.4.3.2-1/24 OR A.4.3.2-1/24A) AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C276 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | +| C277 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND ((A.4.3.2-1/42 OR A.4.3.2-1/43 OR A.4.3.2-1/44) OR (A.4.3.2-1/42a OR A.4.3.2-1/43a OR A.4.3.2-1/44a)) AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | +| C278 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/123 AND A.4.3.2-1/122 THEN R ELSE N/A | +| C279 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/124 AND A.4.3.2-1/122 THEN R ELSE N/A | +| C280 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/124 AND A.4.3.2-1/125 AND A.4.3.2-1/126 THEN R ELSE N/A | +| C281 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/123 AND A.4.3.2-1/122 THEN R ELSE N/A | +| C282 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/124 AND A.4.3.2-1/122 THEN R ELSE N/A | +| C283 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/124 AND A.4.3.2-1/125 AND A.4.3.2-1/126 THEN R ELSE N/A | +| C284 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.1-4/6 AND A.4.3.2-1/132 | +| C285 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.1-4A/1 AND A.4.3.2-1/14 AND A.4.3.2A.1-2/1 THEN R ELSE N/A | +| C286 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.6-1/81 THEN R ELSE N/A | +| C287 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.6-1/81 THEN R ELSE N/A | +| C288 | IF (A.4.1-1/1 OR A.4.1-1/2) AND (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2B.2.0-1A/12 AND A.4.3.2-1/132 129 THEN R ELSE N/A | +| C289 | IF (A.4.1-1/2) AND A.4.1-4/4 AND A.4.1-3/2 AND A.4.3.2B.2.0-1A/1 AND A.4.3.2-1/132 THEN R ELSE N/A | +| C290 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41a AND (A.4.3.2-1/42b OR A.4.3.2-1/43b OR A.4.3.2-1/44b) AND A.4.3.6-1/73 THEN R ELSE N/A | +| C291 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41a AND (A.4.3.2-1/42b OR A.4.3.2-1/43b OR A.4.3.2-1/44b) AND A.4.3.6-1/74 THEN R ELSE N/A | +| C292 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6-1/63 THEN R ELSE N/A | +| C293 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6-1/63 AND A.4.3.6-1/67 THEN R ELSE N/A | +| C294 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/34 AND A.4.3.6-1/41a AND A.4.3.6-1/68 AND A.4.3.6-1/70 AND A.4.3.6-1/72 THEN R ELSE N/A | +| C295 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6-1/68 AND NOT A.4.3.6-1/70 AND A.4.3.6-1/72 THEN R ELSE N/A | +| C296 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.6-1/68 AND A.4.3.6-1/70 AND A.4.3.6-1/72 THEN R ELSE N/A | +| C297 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND (A.4.1-4A/3 OR A.4.1-4A/4 OR A.4.1-4A/6) AND A.4.3.2A.1-1/1 AND A.4.3.6-1/68 AND A.4.3.6-1/72 THEN R ELSE N/A | +| C298 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.3.6-1/81 THEN R ELSE N/A | +| C299 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.3.6-1/81 THEN R ELSE N/A | +| C300 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.4-1/16 THEN R ELSE N/A | +| C301 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.4-1/16 THEN R ELSE N/A | +| C302 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.3.6-1/8a THEN R ELSE N/A | +| C303 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.3.6-1/8a THEN R ELSE N/A | + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------| +| C304 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.3.6-1/7a THEN R ELSE N/A | +| C305 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.3.6-1/7a THEN R ELSE N/A | +| C306 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 AND A.4.3.6-1/6 THEN R ELSE N/A | +| C307 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 AND A.4.3.6-1/6 THEN R ELSE N/A | +| C308 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.4-1/16 THEN R ELSE N/A | +| C309 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/41a THEN R ELSE N/A | +| C310 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/41a AND A.4.3.5-1/1 THEN R ELSE N/A | +| C311 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.2-1/56 AND 4.3.2-1/78 THEN R ELSE N/A | +| C312 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.6-1/8a THEN R ELSE N/A | +| NOTE 1: | Cxxxx applicability is defined for enhanced type 1 receiver for NR related tests (A.4.3.9-1/1). | +| NOTE 2: | Cxxxy applicability is defined for alternative additional DMRS position for co-existence with LTE CRS related tests (A.4.3.2-1/20). | +| NOTE 3: | Cxxxz applicability is defined for modified MPR behaviour related test (A.4.3.2-1/25). | +| NOTE 4: | Cxxxw applicability is defined for mpr Power Boost related test (A.4.3.2-1/38). | + +Table 4.0-2: Tested Bands Selection Criteria + +| Code | Tested Bands Selection Criteria | Comment | +|------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| D001 | A.4.3.1-1 OR A.4.3.1-2 | All supported FDD or TDD FR1 bands | +| D002 | Void | | +| D003 | A.4.3.1-5 | All supported FR1 SUL Bands | +| D004 | {n1, n2, n3, n5, n7, n8, n12, n14, n20, n25, n28, n30, n34, n38, n39, n40, n41, n50, n51, n65, n66, n70, n71, n74, n75, n76} | All supported bands among n1, n2, n3, n5, n7, n8, n12, n14, n20, n25, n28, n30, n34, n38, n39, n40, n41, n50, n51, n65, n66, n70, n71, n74, n75, n76 | +| D005 | A.4.3.1-3 | All supported FR2 Bands | +| D006 | Void | | +| D007 | Void | | +| D008 | ANY((A.4.3.1-1) AND 10MHz) | Any FDD FR1 band within the set supporting 10 MHz UE Channel BW | +| D009 | ANY((A.4.3.1-2) AND 20MHz) | Any TDD FR1 band within the set supporting 20 MHz UE Channel BW | +| D010 | ANY((A.4.3.1-2) AND 40MHz) | Any TDD FR1 band within the set supporting 40 MHz UE Channel BW | +| D011 | A.4.3.9-4a OR A.4.3.9-4b | All supported 4 Rx antenna ports Bands | +| D012 | A.4.3.9-12 AND FDD | All supported FDD FR1 band with UL MIMO capabilities | +| D013 | ANY((A.4.3.1-3) AND 50MHz) | Any TDD FR2 band within the set supporting 50 MHz UE Channel BW | +| D014 | ANY((A.4.3.1-3) AND 100MHz) | Any TDD FR2 band within the set supporting 100 MHz UE Channel BW | +| D015 | ANY((A.4.3.1-3) AND 200MHz) | Any TDD FR2 band within the set supporting 200 MHz UE Channel BW | +| D016 | A.4.3.1-9 | All supported FR1 sidelink bands | +| D017 | {n40, n41, n77, n78, n79} | All supported TDD bands among n40, n41, n77, n78, n79 | +| D018 | A.4.3.1-2/2e OR A.4.3.1-2/12 | All supported FR1 Bands for operation with shared spectrum channel access | +| D019 | {n34, n38, n39, n48, n90} AND 10MHz | All supported TDD FR1 bands among n34, n38, n39, n48, n90 supporting 10MHz UE Channel BW | +| D020 | Void | | +| D021 | Void | | +| D022 | A.4.3.9-12 AND NOT A.4.3.1-5 | All supported FDD or TDD FR1 Bands with UL MIMO capabilities | +| D023 | A.4.3.9-13 | All supported FR2 Bands with UL MIMO capabilities | +| D024 | A.4.3.9-12 AND A.4.3.1-5 | All supported FR1 Bands with UL MIMO capabilities and SUL bands | +| D025 | {n46, n96, n102} AND CCA | All supported TDD FR1 bands with CCA | +| D026 | Void | | +| D027 | {n255, n256} AND Satellite Access | All supported FR1 bands with Satellite Access | + +NOTE 1: Band Selection is based on set theory. For each feature, item number shall correspond to the Band number. The result is the set of bands for which the test shall be conducted. The following operators are used: + +AND: Set intersection ( $\cap$ ). {n1,n2} AND {n2,n3} = {n2} + +OR: Set union ( $\cup$ ). {n1,n2} OR {n2,n3} = {n1,n2,n3} + +NOT: Set complement ( $\setminus$ ), full set being all bands. NOT{n1} = {All bands except n1} + +Also note that this is set without repetitions so {n1} AND {n1} = {n1} + +The following basic sets are used: + +- {n1,n2}: Explicitly given band set +- 10MHz: All bands supporting 10 MHz +- FDD: All bands in FDD mode + +**Table 4.0-3: Tested CA/DC Configuration Selection Criteria** + +| Code | Tested CA/DC Configuration Selection Criteria | Comment | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| E001 | DL_2CC(A.4.3.2A.2.1-3) AND A.4.3.2B.2.0-1/1 AND NOT UL(A.4.3.2A.2.1-2) | All supported intra-band contiguous CA Configurations with 2 carriers in DL but no CA in UL | +| E002 | DL_2CC(A.4.3.2A.4.1-3) AND A.4.3.2B.2.0-1/1 AND NOT UL(A.4.3.2A.4.1-2) | All supported inter-band CA Configurations with 2 carriers in DL but no CA in UL | +| E003 | UL_2CC(A.4.3.2B.2.1-2) AND A.4.3.2B.2.0-2/1 | All supported Intra-band contiguous EN-DC configurations in FR1 (2UL CCs) | +| E003a | DL_2CC(A.4.3.2B.2.1-2) AND A.4.3.2B.2.0-1/1 | All supported Intra-band contiguous EN-DC configurations in FR1 (2DL CCs) | +| E004 | UL_2CC(A.4.3.2B.2.2-2) AND A.4.3.2B.2.0-2/1 | All supported Intra-band non-contiguous EN-DC configurations in FR1 (2UL CCs) | +| E004a | DL_2CC(A.4.3.2B.2.2-2) AND A.4.3.2B.2.0-1/1 | All supported Intra-band non-contiguous EN-DC configurations in FR1 (2DL CCs) | +| E005 | UL_2CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-2/1 | All supported Inter-band EN-DC configurations within FR1 (2UL CCs) | +| E005a | DL_2CC(A.4.3.2B.2.3.1-2) OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2 AND A.4.3.2B.2.0-1/1 | All supported Inter-band EN-DC configurations within FR1 (2DL CCs) | +| E005b | UL_NR_1CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-2A/1 | All supported Inter-band EN-DC configurations within FR1 with 1 UL NR CC and one or more LTE UL CC(s) | +| E005c | DL_NR_1CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1A/1 | All supported Inter-band EN-DC configurations within FR1 with 1 DL NR CC and one or more LTE DL CC(s) | +| E005d | A.4.3.2B.2.3.1-3 | All supported PC2 Inter-band EN-DC configurations within FR1 | +| E005z | UL_3CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-2/2 AND A.4.3.2B.2.0-2A/1 | All supported Inter-band EN-DC configurations within FR1 (2UL E-UTRA CCs, 1UL NR CC) | +| E006 | DL_3CC(A.4.3.2B.2.1-2 OR A.4.3.2B.2.2-2 OR A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1/2 | All supported EN-DC configurations within FR1 (3DL CCs) | +| E007 | DL_4CC(A.4.3.2B.2.1-2 OR A.4.3.2B.2.2-2 OR A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1/3 | All supported EN-DC configurations within FR1 (4DL CCs) | +| E008 | DL_5CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1/4 | All supported EN-DC configurations within FR1 (5DL CCs) | +| E009 | DL_6CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1/5 | All supported EN-DC configurations within FR1 (6DL CCs) | +| E010 | UL_NR_1CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2A/1 | All supported Inter-band EN-DC configurations including FR2 (1UL NR CC) | +| E010a | DL_NR_1CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1A /1 | All supported Inter-band EN-DC configurations including FR2 (1DL NR CC) | +| E011 | UL_NR_2CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/2 AND A.4.3.2B.2.0-2A/2 | All supported Inter-band EN-DC configurations including FR2 (2UL NR CCs) | +| E011a | DL_NR_2CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/2 AND A.4.3.2B.2.0-1A/2 | All supported Inter-band EN-DC configurations including FR2 (2DL NR CCs) | + +| | | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| E012 | UL_NR_3CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/3 AND NR_A.4.3.2B.2.0-2A/3 | All supported Inter-band EN-DC configurations including FR2 (3UL NR CCs) | +| E012a | DL_NR_3CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/3 AND A.4.3.2B.2.0-1A/3 | All supported Inter-band EN-DC configurations including FR2 (3DL NR CCs) | +| E013 | UL_NR_4CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/4 AND A.4.3.2B.2.0-2A/4 | All supported Inter-band EN-DC configurations including FR2 (4UL NR CCs) | +| E013a | DL_NR_4CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/4 AND A.4.3.2B.2.0-1A/4 | All supported Inter-band EN-DC configurations including FR2 (4DL NR CCs) | +| E014 | DL_NR_5CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/5 AND A.4.3.2B.2.0-1A/5 | All supported Inter-band EN-DC configurations including FR2 (5DL NR CCs) | +| E014a | UL_NR_5CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/4 AND A.4.3.2B.2.0-2A/5 | All supported Inter-band EN-DC configurations including FR2 (5UL NR CCs) | +| E015 | UL_2CC(A.4.3.2A.2.1-3 OR A.4.3.2A.3.1-3 OR A.4.3.2A.4.1-3 OR A.4.3.2A.4.2-3) AND A.4.3.2A.1-2/1 | All supported FR1 2UL CA configurations | +| E015a | A.4.3.2A.4.1-4 | All supported PC2 Inter-band CA configurations within FR1 | +| E015b | A.4.3.2B.1.0-2 AND A.4.3.2B.1.0a.1-2/1 | All supported FR1 2UL NR-DC configurations | +| E016 | DL_2CC(A.4.3.2A.2.1-3 OR A.4.3.2A.3.1-3 OR A.4.3.2A.4.1-3) AND A.4.3.2A.1-1/1 | All supported FR1 2DL CA configurations | +| E017 | DL_3CC(A.4.3.2A.2.1-3 OR A.4.3.2A.3.1-3 OR A.4.3.2A.4.1-3 OR A.4.3.2A.4.2-3) AND A.4.3.2A.1-1/2 | All supported FR1 3DL CA configurations | +| E018 | DL_4CC(A.4.3.2A.2.1-3 OR A.4.3.2A.3.1-3 OR A.4.3.2A.4.1-3 OR A.4.3.2A.4.2-3) AND A.4.3.2A.1-1/3 | All supported FR1 4DL CA configurations | +| E018a | DL_5CC(A.4.3.2A.2.1-3 OR A.4.3.2A.3.1-3 OR A.4.3.2A.4.1-3 OR A.4.3.2A.4.2-3) AND A.4.3.2A.1-1/4 | All supported FR1 5DL CA configurations | +| E019 | ULTxSwitching(A.4.3.2A.4.1-3) | All supported FR1 2UL CA configurations with 1Tx-2Tx ULTxSwitching capability | +| E019a | 2Tx_ULTxSwitching(A.4.3.2A.4.1-3) | All supported FR1 2UL CA configurations with 2Tx-2Tx ULTxSwitching capability | +| E020 | UL_2CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-2/1 | All supported FR2 2UL CA configurations | +| E021 | UL_3CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-2/2 | All supported FR2 3UL CA configurations | +| E022 | UL_4CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-2/3 | All supported FR2 4UL CA configurations | +| E023 | UL_5CC(A.4.3.2A.2.2-3) AND A.4.3.2A.1-2/4 | All supported FR2 5UL CA configurations | +| E024 | UL_6CC(A.4.3.2A.2.2-3) AND A.4.3.2A.1-2/5 | All supported FR2 6UL CA configurations | +| E025 | UL_7CC(A.4.3.2A.2.2-3) AND A.4.3.2A.1-2/6 | All supported FR2 7UL CA configurations | +| E026 | UL_8CC(A.4.3.2A.2.2-3) AND A.4.3.2A.1-2/7 | All supported FR2 8UL CA configurations | +| E027 | DL_NR_2CC(A.4.3.2B.2.2-2) AND A.4.3.2B.2.0-1A/2 | All supported Intra-band non-contiguous EN-DC configurations in FR1 (2DL NR CCs) | +| E028 | DL_NR_3CC(A.4.3.2B.2.2-2) AND A.4.3.2B.2.0-1A/3 | All supported Intra-band non-contiguous EN-DC configurations in FR1 (3DL NR CCs) | +| E028a | DL_NR_4CC(A.4.3.2B.2.2-2) AND A.4.3.2B.2.0-1A/4 | All supported Intra-band non-contiguous EN-DC configurations in FR1 (4DL NR CCs) | +| E028b | DL_NR_5CC(A.4.3.2B.2.2-2) AND A.4.3.2B.2.0-1A/5 | All supported Intra-band non-contiguous EN-DC configurations in FR1 (5DL NR CCs) | + +| | | | +|-------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| E029 | DL_NR_2CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1A/2 | All supported Inter-band EN-DC configurations within FR1 (2DL NR CCs) | +| E030 | DL_NR_3CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1A/3 | All supported Inter-band EN-DC configurations within FR1 (3DL NR CCs) | +| E030a | DL_NR_4CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1A/4 | All supported Inter-band EN-DC configurations within FR1 (4DL NR CCs) | +| E030b | DL_NR_5CC(A.4.3.2B.2.3.1-2 OR A.4.3.2B.2.3.2-2 OR A.4.3.2B.2.3.3-2 OR A.4.3.2B.2.3.4-2 OR A.4.3.2B.2.3.5-2) AND A.4.3.2B.2.0-1A/5 | All supported Inter-band EN-DC configurations within FR1 (5DL NR CCs) | +| E031 | A.4.3.2C.3-2 | All supported FR1 intra-band contiguous 2DL CA with SUL in uplink Configurations | +| E031b | ULTxSwitching(A.4.3.2B.2.3.1-2) | All supported FR1 2UL inter-band EN-DC configurations with ULTxSwitching capability | +| E032 | DL_2CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/1 | All supported FR2 2DL CA configurations | +| E033 | DL_3CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/2 | All supported FR2 3DL CA configurations | +| E034 | DL_4CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/3 | All supported FR2 4DL CA configurations | +| E035 | DL_5CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/4 | All supported FR2 5DL CA configurations | +| E036 | DL_6CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/5 | All supported FR2 6DL CA configurations | +| E037 | DL_7CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/6 | All supported FR2 7DL CA configurations | +| E038 | DL_8CC(A.4.3.2A.2.2-3 OR A.4.3.2A.3.2-3 OR A.4.3.2A.3.2-3a) AND A.4.3.2A.1-1/7 | All supported FR2 8DL CA configurations | +| E039 | UL_NR_6CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/4 AND A.4.3.2B.2.0-2A/6 | All supported Inter-band EN-DC configurations including FR2 (6UL NR CCs) | +| E039a | DL_NR_6CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/5 AND A.4.3.2B.2.0-1A/5 | All supported Inter-band EN-DC configurations including FR2 (6DL NR CCs) | +| E040 | UL_NR_7CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/4 AND A.4.3.2B.2.0-2A/7 | All supported Inter-band EN-DC configurations including FR2 (7UL NR CCs) | +| E040a | DL_NR_7CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/5 AND A.4.3.2B.2.0-1A/7 | All supported Inter-band EN-DC configurations including FR2 (7DL NR CCs) | +| E041 | UL_NR_8CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2/4 AND A.4.3.2B.2.0-2A/8 | All supported Inter-band EN-DC configurations including FR2 (8UL NR CCs) | +| E041a | DL_NR_8CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-1/5 AND A.4.3.2B.2.0-1A/8 | All supported Inter-band EN-DC configurations including FR2 (8DL NR CCs) | +| E042 | Table A.4.3.2A.2.1-3a | All supported FR1 intra-band contiguous CA configuration with UL MIMO capabilities | +| E043 | UL_NR_1CC(A.4.3.2B.2.3.6-2 OR A.4.3.2B.2.3.7-2 OR A.4.3.2B.2.3.8-2 OR A.4.3.2B.2.3.9-2) AND A.4.3.2B.2.0-2A/1 AND A.4.3.9-13 | All supported Inter-band EN-DC configurations including FR2 (1UL NR CC) and UL MIMO | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | UL( table_index ) includes all supported CA Configurations where at least one UL CA configuration was declared in column "Supported CA Bandwidth Class(es) in UL" in Table table_index in TS 38.508-2 [8]. | +| NOTE 2: | UL_ n CC( table_index ) includes all supported CA or DC Configurations where at least one n -carrier UL CA or DC configuration was declared in column "Supported CA Bandwidth Class(es) in UL" or "Supported EN-DC Bandwidth Class(es) in UL" in Table table_index in TS 38.508-2 [8]. | +| NOTE 3: | UL_NR_ n CC( table_index ) includes all supported DC Configurations where at least one DC configuration with n -carrier NR UL CA configuration was declared in column "Supported EN-DC Bandwidth Class(es) in UL" in Table table_index in TS 38.508-2 [8]. | +| NOTE 4: | DL_ n CC( table_index ) includes all supported n -carrier CA/DC Configurations in Table table_index in TS 38.508-2 [8]. | +| NOTE 5: | DL_NR_ n CC( table_index ) includes all supported DC Configurations with n -carrier NR DL CA configuration in Table table_index in TS 38.508-2 [8]. | +| NOTE 6: | ULTxSwitching( table_index ) includes all supported CA/DC/SUL Configurations where at least one uplink band pair was declared in column "Supported ULTxSwitching Band Pair" in Table table_index in TS 38.508-2 [8]. 2Tx_ULTxSwitching( table_index ) includes all supported CA/DC/SUL Configurations where at least one uplink band pair was declared in column "Supported 2Tx-2Tx ULTxSwitching Band Pair" in Table table_index in TS 38.508-2 [8]. | + +Table 4.0-4: Test Selection Criteria for RRM + +| Code | Tested Bands Selection Criteria | Comment | +|------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| F001 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/9 THEN R ELSE N/A | UEs supporting EN-DC FR1 AND CSI-RS based PRACH | +| F002 | IF (A.4.1-4/1 OR A.4.1-4/2 OR A.4.1-4/3 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 THEN R ELSE N/A | UEs supporting EN-DC FR1 and long DRX cycle | +| F003 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.2-1/9 THEN R ELSE N/A | UEs supporting EN-DC FR2 and CSI-RS based PRACH | +| F004 | IF (A.4.1-4/4 OR A.4.1-4/5) AND A.4.1-3/2 AND A.4.3.5-1/1 THEN R ELSE N/A | UEs supporting EN-DC FR2 and long DRX cycle | +| F005 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND A.4.3.2-1/9 THEN R ELSE N/A | UEs supporting 5GS NR SA FR1 and CSI-RS based PRACH | +| F006 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 THEN R ELSE N/A | UEs supporting 5GS NR SA FR1 and long DRX cycle | +| F007 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.2-1/9 THEN R ELSE N/A | UEs supporting 5GS NR SA FR2 and CSI-RS based PRACH | +| F008 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.5-1/1 THEN R ELSE N/A | UEs supporting 5GS NR SA FR2 and long DRX cycle | +| F009 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND A.4.3.2-1/9 AND A.4.3.12-1/2 AND A.4.3.1-7a/4 THEN R ELSE N/A | 1Rx RedCap UEs supporting 5GS NR SA FR1 and CSI-RS based PRACH | +| F010 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-3/1 AND A.4.3.2-1/9 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | 2Rx RedCap UEs supporting 5GS NR SA FR1 and CSI-RS based PRACH | +| F011 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.2-1/46 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | +| F012 | IF (A.4.1-1/1 OR A.4.1-1/2) AND A.4.1-2/7 AND A.4.1-3/1 AND A.4.3.5-1/1 AND A.4.3.12-1/2 AND A.4.3.1-7a/1 THEN R ELSE N/A | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | +| F013 | IF A.4.1-1/2 AND A.4.1-2/8 AND A.4.1-3/1 AND A.4.3.12-1/2 AND A.4.3.2-1/9 THEN R ELSE N/A | RedCap UEs supporting 5GS NR SA FR2 and CSI-RS based PRACH | + +## 4.1 RF conformance test cases + +NOTE: To determine applicability of a test case, supported CBW and SCS in the *RF-Parameters* IE (see TS 38.331 [11]) which conveys RF related capabilities for NR operation is taken into account. + +### 4.1.1 FR1 standalone conformance test cases + +**Table 4.1.1-1: Applicability of RF SA FR1 conformance test cases, ref. TS 38.521-1 [1]** + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|---------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6 | Transmitter Characteristics | | | | | | | +| 6.2.1 | UE maximum output power | Rel-15 | C001l | UEs supporting 5GS FR1 not supporting txDiversity-r16 and not supporting RedCap | D001 | PC1
PC2
PC3 | | +| 6.2.2 | UE maximum output power reduction | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | PC1
PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5.2.4.1 is executed.
Skip TC 6.2.2 if UE supports NSA and TS 38.521-3 TC 6.2B.2.3 or 6.5B.2.3.3.1 has been executed. | +| 6.2.3 | UE additional maximum output power reduction | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | PC1
PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5.2.3, 6.5.2.4.2 and 6.5.3.3 are executed.
Skip TC 6.2.3 if UE supports NSA and TS 38.521-3 TC 6.2B.3.3 has been executed or TS 38.521-3 TCs 6.5B.2.3.2, 6.5B.2.3.3.2 and 6.5B.4.3 have been executed. | +| 6.2.4 | Configured transmitted power | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | PC1
PC2
PC3 | | +| 6.2A.1.1 | UE maximum output power for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015
E015a | Inter-band CA:
PC2, PC3 | | +| 6.2A.2.1 | UE maximum output power reduction for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015
E015a | Inter-band CA:
PC2, PC3
Intra-band contiguous CA: | Test execution is not necessary if TS 38.521-1 TC 6.5A.2.4.1.1 is executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|-----------------------------------------------------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC2, PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|--------------------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2A.3.1 | UE additional maximum output power reduction for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015
E015a | Inter-band CA:
PC2, PC3
Intra-band contiguous CA:
PC2, PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5A.2.3 and 6.5A.3.3 are executed. | +| 6.2A.4.1 | Configured transmitted power for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015
E015a | Inter-band CA:
PC2, PC3
Intra-band contiguous CA:
PC2, PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | +| 6.2B.1.1 | UE maximum output power for NR-DC | Rel-16 | C004a | UEs supporting 5GS FR1 and NR-DC | E015b | | | +| 6.2B.2.1 | UE maximum output power reduction for NR-DC | Rel-16 | C004a | UEs supporting 5GS FR1 and NR-DC | E015b | | Test execution is not necessary if TS 38.521-1 TC 6.5B.2.4 is executed. | +| 6.2B.3.1 | UE additional maximum output power reduction for NR-DC | Rel-16 | C004a | UEs supporting 5GS FR1 and NR-DC | E015b | | Test execution is not necessary if TS 38.521-1 TC 6.5B.2.3 and 6.5B.3.3 are executed. | +| 6.2B.4.1 | Configured transmitted power level for NR-DC | Rel-16 | C004a | UEs supporting 5GS FR1 and NR-DC | E015b | | | +| 6.2C.1 | Configured transmitted power for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.2C.3 | UE maximum output power for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.2C.4 | UE maximum output power reduction for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2
Test execution is not necessary if TS 38.521-1 TC 6.5C.2.4.1 is executed. | +| 6.2C.5 | UE additional maximum output power reduction for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|-------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------|------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2D.1 | UE maximum output power for UL MIMO | Rel-15 | N/A | No test point applicable to Rel-15 UE | D022 | PC1.5
PC2
PC3 | | +| | | Rel-16 | C003b | UEs supporting 5GS FR1 and ULFPTx | | | | +| 6.2D.1_1 | UE maximum output power for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.2D.2 | UE maximum output power reduction for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | PC1.5
PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5D.2.4.1 is executed. | +| | | Rel-16 | C003b | UEs supporting 5GS FR1 and ULFPTx | | | | +| 6.2D.2_1 | UE maximum output power reduction for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | Test execution is not necessary if TS 38.521-1 TC 6.5D.2.4.1_1 is executed. | +| 6.2D.3 | UE additional maximum output power reduction for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | PC1.5 (NOTE 1)
PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5D.2.3, 6.5D.2.4.2 and 6.5D.3.3 are executed. | +| | | Rel-16 | C003b | UEs supporting 5GS FR1 and ULFPTx | | | | +| 6.2D.3_1 | UE additional maximum output power reduction for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.2D.4 | Configured transmitted power for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | PC1.5
PC2
PC3 | | +| | | Rel-16 | C003b | UEs supporting 5GS FR1 and ULFPTx | | | | +| 6.2D.4_1 | Configured transmitted power for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.2E.2.1 | UE maximum output power reduction for V2X / non- | Rel-16 | C079 | UEs supporting 5GS FR1 and NR | D016 | | Test execution is not | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------------------|---------|---------------|----------|------------------------------------------|--------|-----------------------------------------------------| +| | | | Condition | Comment | | | | +| | concurrent operation | | | sidelink | | | necessary if TS 38.521-1 TC 6.5E.2.4.1 is executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|--------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|---------------------|---------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2E.2.2 | UE maximum output power reduction for V2X / concurrent operation | FFS | FFS | FFS | FFS | | | +| 6.2F.1 | UE maximum output power for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 6.2F.2 | UE maximum output power reduction for shared spectrum access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.2F.3 | UE additional maximum output power reduction for shared spectrum access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 6.2F.4 | Configured transmitted power for shared spectrum access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.2G.1 | UE maximum output power for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.2G.2 | UE maximum output power reduction for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5G.2.3.1 is executed. | +| 6.2G.3 | UE additional maximum output power reduction for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5G.2.2 and 6.5G.3.3 are executed. | +| 6.2G.4 | Configured transmitted power for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.2H.1.1 | UE maximum output power for intra-band UL contiguous CA with UL MIMO | Rel-15 | C285 | UEs supporting 5GS FR1 and intra-band contiguous CA (2UL CA) and MIMO. | E042 | PC2
PC3 | Test execution is not necessary if TS 38.521-1 TC 6.5H.1.2.3 is executed. | +| 6.2H.1.2 | UE maximum output power reduction for intra-band UL contiguous CA with UL MIMO | Rel-15 | C285 | UEs supporting 5GS FR1 and intra-band contiguous CA (2UL CA) | E042 | PC2
PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|-----------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | and MIMO. | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|---------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------|------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2H.1.4 | Configured transmitted power for intra-band UL contiguous CA with UL MIMO | Rel-15 | C285 | UEs supporting 5GS FR1 and intra-band contiguous CA (2UL CA) and MIMO. | E042 | PC2
PC3 | | +| 6.2I.1 | UE maximum output power for RedCap | Rel-17 | C177 | RedCap UEs supporting 5GS FR1 | D001 | | | +| 6.2I.2 | Void | | | | | | | +| 6.2I.3 | Void | | | | | | | +| 6.2I.4 | Void | | | | | | | +| 6.3.1 | Minimum output power | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | | +| 6.3.3.2 | General ON/OFF time mask | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.3.3.2 if UE supports NSA and TS 38.521-3 TC 6.3B.3.1 or 6.3B.3.2 or 6.3B.3.3 has been executed. | +| 6.3.3.4 | PRACH time mask | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.3.3.4 if UE supports NSA and TS 38.521-3 TC 6.3B.4.1 or 6.3B.4.2 or 6.3B.4.3 has been executed. | +| 6.3.3.6 | SRS time mask | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | | +| 6.3.4.2 | Absolute power tolerance | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | | +| 6.3.4.3 | Relative power tolerance | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | | +| 6.3.4.4 | Aggregate power tolerance | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | | +| 6.3A.1.1 | Minimum output power for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | | | +| 6.3A.3.1 | Transmit ON/OFF time mask for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | | | +| 6.3A.3.2 | Time mask for switching between two uplink carriers | Rel-16 | C051 | UEs supporting 5GS FR1 and Inter-band CA (2UL CA) and dynamic 1Tx-2Tx UL Tx switching | E019 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| 6.3A.3.3 | Time mask for switching between two uplink carriers with two transmit antenna connectors | Rel-17 | C051b | UEs supporting 5GS FR1 and Inter-band CA (2UL CA) and dynamic 2Tx-2Tx UL Tx switching | E019a | | | +| 6.3A.4.1.1 | Absolute power tolerance for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | | | +| 6.3A.4.2.1 | Relative power tolerance for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | | | +| 6.3A.4.3.1 | Aggregate power tolerance for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | | | +| 6.3C.1 | Minimum output power for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.3C.3.1 | General transmit ON/OFF time mask for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.3C.3.2 | General transmit ON/OFF time mask for switching between two uplink carriers | Rel-16 | C178 | UEs supporting 5GS FR1 and SUL and dynamic UL Tx switching | D003 | | NOTE 2 | +| 6.3C.4.1 | Absolute power tolerance for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.3C.4.2 | Relative power tolerance for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.3C.4.3 | Aggregate power tolerance for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.3D.1 | Minimum output power for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.3D.1_1 | Minimum output power for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.3D.3 | Transmit ON/OFF time mask for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.3D.3_1 | Transmit ON/OFF time mask for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.3D.4.1 | Absolute power tolerance for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.3D.4.1_1 | Absolute power tolerance for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.3D.4.2 | Relative power tolerance for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.3D.4.2_1 | Relative power tolerance for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.3D.4.3 | Aggregate power tolerance for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|---------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.3D.4.3_1 | Aggregate power tolerance for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.3E.1.1 | Minimum output power for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | | +| 6.3E.1.1D | Minimum output power for V2X / non-concurrent operation / SL-MIMO | Rel-16 | C100 | UEs supporting 5GS FR1 and NR sidelink and SL-MIMO | D016 | | NOTE 1 | +| 6.3F.1 | Minimum output power | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.3F.4.2 | Absolute power tolerance for shared spectrum access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.3G.1 | Minimum output power for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3G.3.1 | General ON/OFF time mask for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3G.3.2 | PRACH time mask for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3G.3.3 | SRS time mask for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3G.4.1 | Absolute power tolerance for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3G.4.2 | Relative power tolerance for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3G.4.3 | Aggregate power tolerance for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.3H.1.1 | Minimum output power for intra-band UL contiguous | Rel-15 | C285 | UEs supporting 5GS FR1 and | E042 | PC2 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|-----------------|---------|---------------|---------------------------------------------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | CA with UL MIMO | | | intra-band contiguous CA (2UL CA) and MIMO. | | PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------|------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3H.1.3 | Transmit ON/OFF time mask for intra-band UL contiguous CA with UL MIMO | Rel-15 | C285 | UEs supporting 5GS FR1 and intra-band contiguous CA (2UL CA) and MIMO. | E042 | PC2
PC3 | | +| 6.4.1 | Frequency error | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.4.1 if UE supports NSA and TS 38.521-3 TC 6.4B.1.1 or 6.4B.1.2 or 6.4B.1.3 has been executed. | +| 6.4.2.1 | Error vector magnitude | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.4.2.1 if UE supports NSA and TS 38.521-3 TC 6.4B.2.1.1 or 6.4B.2.2.1 or 6.4B.2.3.1 has been executed. | +| 6.4.2.1a | Error Vector Magnitude including symbols with transient period | Rel-16 | C156 | UEs supporting 5GS FR1 AND Band supporting enhancedUL-TransientPeriod and not supporting txDiversity-r16 | D001 | | NOTE 1 | +| 6.4.2.2 | Carrier leakage | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.4.2.2 if UE supports NSA and TS 38.521-3 TC 6.4B.2.1.2 or 6.4B.2.2.2 or 6.4B.2.3.2 has been executed. | +| 6.4.2.3 | In-band emissions | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.4.2.3 if UE supports NSA and TS 38.521-3 TC 6.4B.2.2.3 or 6.4B.2.3.3 has been executed. | +| 6.4.2.4 | EVM equalizer spectrum flatness | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.4.2.4 if UE supports NSA and TS 38.521-3 TC 6.4B.2.1.4 or 6.4B.2.2.4 or 6.4B.2.3.4 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4.2.5 | EVM equalizer spectrum flatness for Pi/2 BPSK | Rel-15 | C050 | UEs supporting 5GS FR1 Power Class 3 and pi/2-BPSK modulation scheme for power boosting in FR1 and not supporting txDiversity-r16 | D017 | PC3 | | +| | | Rel-16 | C111 | UEs supporting 5GS FR1 and pi/2-BPSK modulation scheme and low PAPR DMRS and not supporting txDiversity-r16 | D001 | | | +| 6.4.2.6 | Phase continuity requirements for DMRS bundling | Rel17 | FFS | UEs supporting 5GS FR1 and DMRS bundling | D005 | | NOTE 1
Skip TC 6.4.2.6 if UE supports NSA and TS 38.521-3 TC [TBD] has been executed. | +| 6.4A.1.1 | Frequency error for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | +| 6.4A.2.1.1 | Error vector magnitude for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | +| 6.4A.2.2.1 | Carrier leakage for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|-----------------------------------------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | Intra-band non-contiguous CA:
PC3 (NOTE 1) | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.4A.2.3.1 | In-band emissions for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | +| 6.4C.1 | Frequency error for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.4C.2.1 | Error vector magnitude for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.4C.2.2 | Carrier leakage for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.4C.2.3 | In-band emissions for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.4C.2.4 | EVM equalizer spectrum flatness for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.4C.2.5 | EVM equalizer spectrum flatness for Pi/2 BPSK for SUL | Rel-16 | C112 | UEs supporting 5GS FR1 and SUL and pi/2-BPSK modulation scheme and low PAPR DMRS | D003 | | NOTE 2 | +| 6.4D.1 | Frequency error for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.4D.1_1 | Frequency error for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.4D.2.1 | Error vector magnitude for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.4D.2.1_1 | Error Vector Magnitude for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.4D.2.2 | Carrier leakage for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.4D.2.2_1 | Carrier leakage for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.4D.2.3 | In-band emissions for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.4D.2.3_1 | In-band emissions for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.4D.2.4 | EVM equalizer spectrum flatness for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|-------------|---------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|---------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.4D.2.4_1 | EVM equalizer spectrum flatness for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.4D.3 | Time alignment error for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.4D.3_1 | Time alignment error for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.4D.4 | Requirements for coherent UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4E.2.2.1 | Error Vector Magnitude for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | NOTE 1 | +| 6.4E.2.2.1D | Error Vector Magnitude for V2X / non-concurrent operation / SL-MIMO | Rel-16 | C100 | UEs supporting 5GS FR1 and NR sidelink and SL-MIMO | D016 | | NOTE 1 | +| 6.4E.2.4.1 | In-band emissions for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | NOTE 1 | +| 6.4E.2.4.1D | In-band emissions for V2X / non-concurrent operation / SL-MIMO | Rel-16 | C100 | UEs supporting 5GS FR1 and NR sidelink and SL-MIMO | D016 | | NOTE 1 | +| 6.4F.1 | Frequency error | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.4F.2.1 | Error Vector Magnitude | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.4F.2.2 | Carrier leakage | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.4G.1 | Frequency error for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.4G.2.1 | Error vector magnitude for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.4G.2.2 | Carrier leakage for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.4G.2.3 | In-band emissions for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and and | D001 | PC1.5 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|----------------------------|------------------------------------------|------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | supporting txDiversity-r16 | | PC2
PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|-----------|--------------------------------------------------|---------|---------------|-----------------------------------------------------------|------------------------------------------|---------------------|---------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4G.2.4 | EVM equalizer spectrum flatness for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5.1 | Occupied bandwidth | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.5.1 if UE supports NSA and TS 38.521-3 TC 6.5B.1.2 or 6.5B.1.3 has been executed. | +| 6.5.2.2 | Spectrum emission mask | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | PC1
PC2
PC3 | Skip TC 6.5.2.2 if UE supports NSA and TS 38.521-3 TC 6.5B.2.2.1 or 6.5B.2.3.1 has been executed. | +| 6.5.2.3 | Additional spectrum emission mask | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | PC1
PC2
PC3 | Skip TC 6.5.2.3 if UE supports NSA and TS 38.521-3 TC 6.5B.2.3.2 has been executed. | +| 6.5.2.4.1 | NR ACLR | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | PC1
PC2
PC3 | Skip TC 6.5.2.4.1 if UE supports NSA and TS 38.521-3 TC 6.5B.2.3.3.1 has been executed. | +| 6.5.2.4.2 | UTRA ACLR | Rel-15 | C001a | UEs supporting 5GS FR1 PC3 not supporting txDiversity-r16 | D001 | | Skip TC 6.5.2.4.2 if UE supports NSA and TS 38.521-3 TC 6.5B.2.3.3.2 has been executed. | +| 6.5.3.1 | General spurious emissions | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.5.3.1 if UE supports NSA and TS 38.521-3 TC 6.5B.3.1.1 or 6.5B.3.2.1 has been executed. | +| 6.5.3.2 | Spurious emissions for UE co-existence | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------------|---------------------------------------------------|---------|---------------|-------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5.3.3 | Additional spurious emissions | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.5.3.3 if UE supports NSA and TS 38.521-3 TC 6.5B.4.3 has been executed. | +| 6.5.4 | Transmit intermodulation | Rel-15 | C001h | UEs supporting 5GS FR1 not supporting txDiversity-r16 | D001 | | Skip TC 6.5.4 if UE supports NSA and TS 38.521-3 TC 6.5B.5.3 has been executed. | +| 6.5A.1.1 | Occupied bandwidth for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | +| 6.5A.2.2.1 | Spectrum emission mask for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015
E015a | Inter-band CA:
PC2, PC3
Intra-band contiguous CA:
PC2, PC3 | | +| 6.5A.2.3.1 | Additional spectrum emission mask for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Intra-band contiguous CA:
PC2, PC3 | | +| 6.5A.2.4.1.1 | NR ACLR for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015
E015a | Inter-band CA:
PC2, PC3
Intra-band contiguous CA:
PC2, PC3 | | +| 6.5A.2.4.2.1 | UTRA ACLR for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3 | | +| 6.5A.3.1.1 | General spurious emissions for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA: | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|----------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC2, PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------|---------|---------------|-----------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.5A.3.2.1 | Spurious emissions for UE co-existence for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC2, PC3 | | +| 6.5A.3.3.1 | Additional spurious emissions for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Intra-band contiguous CA:
PC2, PC3 | | +| 6.5A.4.1 | Transmit intermodulation for CA (2UL CA) | Rel-15 | C004 | UEs supporting 5GS FR1 and CA (2UL CA) | E015 | Inter-band CA:
PC3
Intra-band contiguous CA:
PC3
Intra-band non-contiguous CA:
PC3 (NOTE 1) | | +| 6.5C.1 | Occupied bandwidth for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.2.2 | Spectrum emission mask for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.2.3 | Additional spectrum emission mask for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.2.4.1 | NR ACLR for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.2.4.2 | UTRA ACLR for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.3.1 | General spurious emissions for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.3.2 | Spurious emissions for UE co-existence for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.3.3 | Additional spurious emissions for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5C.4 | Transmit intermodulation for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | NOTE 2 | +| 6.5D.1 | Occupied bandwidth for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.1_2 | Occupied bandwidth for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.5D.2.2 | Spectrum emission mask for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| | | Rel-16 | C003b | UEs supporting 5GS FR1 and ULFPTx | | | | +| 6.5D.2.2_1 | Spectrum emission mask for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL | D024 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|-------------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | and UL MIMO | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------------|-------------------------------------------------------------------|-------------|---------------|-----------------------------------------------------------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| 6.5D.2.3 | Additional spectrum emission mask for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.2.4.1 | NR ACLR for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| | | Rel-16 | C003b | UEs supporting 5GS FR1 and ULFPTx | | | | +| 6.5D.2.4.1_1 | NR ACLR for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.5D.2.4.2 | UTRA ACLR for UL MIMO | Rel-15y | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.2.4.2_1 | UTRA ACLR for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.5D.3.1 | General spurious emissions for UL MIMO | Rel-15 only | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.3.2 | Spurious emissions for UE co-existence for UL MIMO | Rel-15 only | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.3.3 | Additional spurious emissions for UL MIMO | Rel-15 only | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.3_1.1 | General spurious emissions for UL MIMO (Rel-16 onward) | Rel-16 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.3_1.2 | Spurious emission for UE co-existence for UL MIMO (Rel-16 onward) | Rel-16 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.3_1.3 | Additional spurious emissions for UL MIMO (Rel-16 onward) | Rel-16 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.3_2.1 | General spurious emissions for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.5D.3_2.2 | Spurious emissions for UE co-existence for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.5D.3_2.3 | Additional spurious emissions for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 6.5D.4 | Transmit intermodulation for UL MIMO | Rel-15 | C003 | UEs supporting 5GS FR1 and 2-layer codebook based UL MIMO | D022 | | | +| 6.5D.4_1 | Transmit intermodulation for SUL with UL MIMO | Rel-17 | C179 | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|----------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|---------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.5E.2.2.1 | Spectrum emission mask for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | | +| 6.5E.2.3.1 | Additional Spectrum emission mask for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | NOTE 1 | +| 6.5E.2.4.1 | Adjacent channel leakage ratio for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | | +| 6.5E.3.2.1 | Spurious emissions for UE co-existence for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | NOTE 1 | +| 6.5E.3.3.1 | Additional spurious emissions requirements for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | NOTE 1 | +| 6.5F.1 | Occupied bandwidth for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.5F.2.2 | Spectrum emission mask for operation with shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 6.5F.2.4 | Adjacent channel leakage ratio for operation with shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 6.5F.2.4.2 | Shared spectrum channel access ACLR with additional requirement for NS_29 | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.5F.3.1 | General spurious emissions | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.5F.4 | Transmit intermodulation for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | NOTE 1 | +| 6.5G.1 | Occupied bandwidth for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5G.2.1 | Spectrum emission mask for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------|------------------------------------------|--------------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.5G.2.2 | Additional spectrum emission mask for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5G.2.3.1 | NR ACLR for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5G.2.3.2 | UTRA ACLR for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC3 | | +| 6.5G.3.1 | General spurious emissions for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5G.3.2 | Spurious emissions for UE co-existence for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5G.3.3 | Additional spurious emissions for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5G.4 | Transmit intermodulation for Tx Diversity | Rel-15 | C001g | UEs supporting 5GS FR1 and supporting txDiversity-r16 | D001 | PC1.5
PC2
PC3 | | +| 6.5H.1.2.1 | Spectrum emission mask for intra-band UL contiguous CA for UL MIMO | Rel-15 | C285 | UEs supporting 5GS FR1 and intra-band contiguous CA (2UL CA) and MIMO. | E042 | PC2
PC3 | | +| 6.5H.1.2.3 | NR ACLR for intra-band UL contiguous CA for UL MIMO | Rel-15 | C285 | UEs supporting 5GS FR1 and intra-band contiguous CA (2UL CA) and MIMO. | E042 | PC2
PC3 | | +| 7 | Receiver Characteristics | | | | | | | +| 7.3.2 | Reference sensitivity power level | Rel-15 | C001h | UEs supporting 5GS FR1 and not supporting RedCap | D001 | 2Rx
4Rx
PC2
PC3 | | +| 7.3A.1 | Reference sensitivity power level for 2DL CA without exception | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | PC2
PC3 | | +| 7.3A.1_1 | Reference sensitivity power level for 2DL CA | Rel-15 | C031 | UEs supporting 5GS FR1 and CA | E016 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|------------|---------|---------------|----------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | exceptions | | | (2DL CA) | E015a | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|-----------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|--------|---------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.3A.2 | Reference sensitivity power level for 3DL CA without exceptions | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.3A.2_1 | Reference sensitivity power level for 3DL CA exceptions | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.3A.3 | Reference sensitivity power level for 4DL CA | FFS | C036 | UEs supporting 5GS FR1 and CA (4DL CA) | E018 | | NOTE 1 | +| 7.3C.2 | Reference sensitivity power level for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | | +| 7.3D.2 | Reference sensitivity power level for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.3D.2_1 | Reference sensitivity power level for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.3E.2 | Reference sensitivity for V2X / non-concurrent operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | NOTE 1 | +| 7.3F.2 | Reference sensitivity for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 7.3I.2 | Reference sensitivity power level for RedCap | Rel-17 | C177 | RedCap UEs supporting 5GS FR1 | D001 | | | +| 7.4 | Maximum input level | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | Skip TC 7.4 if UE supports NSA and TS 38.521-3 TC 7.4B.2 or 7.4B.3 has been executed. | +| 7.4A.1 | Maximum input level for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | | | +| 7.4A.2 | Maximum input level for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.4A.3 | Maximum input level for CA (4DL CA) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.4D | Maximum input level for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.4D_1 | Maximum input level for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.5 | Adjacent channel selectivity | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | NOTE 1
Skip TC 7.5 if UE supports NSA and TS | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------|-------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 38.521-3 TC 7.5B.2 or 7.5B.3 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|-----------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.5A.1 | Adjacent channel selectivity for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | | | +| 7.5A.2 | Adjacent channel selectivity for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.5A.3 | Adjacent channel selectivity for CA (4DL CA) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.5D | Adjacent channel selectivity for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.5D_1 | Adjacent channel selectivity for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.5F.1 | Adjacent channel selectivity for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 7.6.2 | In-band blocking | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | Skip TC 7.6.2 if UE supports NSA and TS 38.521-3 TC 7.6B.2.2 or 7.6B.2.3 has been executed. | +| 7.6.3 | Out-of-band blocking | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | | +| 7.6.4 | Narrow band blocking | Rel-15 | C001 | UEs supporting 5GS FR1 | D004 | | Skip TC 7.6.4 if UE supports NSA and TS 38.521-3 TC 7.6B.4.2 or 7.6B.4.3 has been executed. | +| 7.6A.2.1 | In-band blocking for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | | | +| 7.6A.2.2 | In-band blocking for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.6A.2.3 | In-band blocking for CA (4DL CA) | Rel-16 | C036 | UEs supporting 5GS FR1 and CA (4DL CA) | E018 | | NOTE 1
Skip TC 7.6A.2.3 if UE supports NSA and TS 38.521-3 TC 7.6B.2.3_1.3 has been executed. | +| 7.6A.3.1 | Out-of-band blocking for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA | E016 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|----------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | (2DL CA) | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|-----------------------------------------------------|---------|---------------|----------------------------------------------------------------------|------------------------------------------|--------|----------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.6A.3.2 | Out-of-band blocking for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.6A.3.3 | Out-of-band blocking for CA (4DL CA) | Rel-16 | C036 | UEs supporting 5GS FR1 and CA (4DL CA) | E018 | | | +| 7.6A.4.1 | Narrow band blocking for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | | | +| 7.6A.4.2 | Narrow band blocking for CA (3DL CA) | Rel-16 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.6A.4.3 | Narrow band blocking for CA (4DL CA) | Rel-16 | C036 | UEs supporting 5GS FR1 and CA (4DL CA) | E018 | | Skip TC 7.6A.4.3 if UE supports NSA and TS 38.521-3 TC 7.6B.4.3_1.3 has been executed. | +| 7.6C.2 | In-band blocking for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | | +| 7.6C.2_1 | Inband Blocking for SUL with DL CA | Rel-17 | C078 | UEs supporting 5GS FR1 and SUL and intra-band contiguous CA (2DL CA) | E031 | | | +| 7.6C.3 | Out-of-band blocking for SUL | Rel-15 | C002 | UEs supporting 5GS FR1 and SUL | D003 | | | +| 7.6C.3_1 | Out-of-band blocking for SUL with DL CA | Rel-17 | C078 | UEs supporting 5GS FR1 and SUL and intra-band contiguous CA (2DL CA) | E031 | | | +| 7.6D.2 | In-band blocking for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.6D.2_1 | In-band blocking for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.6D.3 | Out-of-band blocking for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.6D.3_1 | Out-of-band blocking for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.6D.4 | Narrow band blocking for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.6D.4_1 | Void | | | | | | | +| 7.6F.2.1 | In-band blocking for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum | D018 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|----------------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | channel access | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|--------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------|------------------------------------------|--------|---------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.6F.3.1 | Out-of-band blocking for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 7.7 | Spurious response | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | | +| 7.7A.1 | Spurious response for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | | | +| 7.7A.2 | Spurious response for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.7A.3 | Spurious response for CA (4DL CA) | Rel-16 | FFS | UEs supporting 5GS FR1 and CA (4DL CA) | FFS | | NOTE 1 | +| 7.7D | Spurious response for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.7D_1 | Spurious response for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.7F.1 | Spurious response for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum channel access | D018 | | | +| 7.8.2 | Wide band Intermodulation | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | Skip TC 7.8.2 if UE supports NSA and TS 38.521-3 TC 7.8B.2.2 or 7.8B.2.3 has been executed. | +| 7.8A.2.1 | Wide band Intermodulation for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | | | +| 7.8A.2.2 | Wide band Intermodulation for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | | | +| 7.8A.2.3 | Wide band Intermodulation for CA (4DL CA) | Rel-16 | C036 | UEs supporting 5GS FR1 and CA (4DL CA) | E018 | | | +| 7.8D.2 | Wide band Intermodulation for UL MIMO | Rel-15 | C003a | UEs supporting 5GS FDD FR1 and UL MIMO | D012 | | | +| 7.8D.2_1 | Wide band Intermodulation for SUL with UL MIMO | Rel-17 | C179a | UEs supporting 5GS FR1 and SUL and UL MIMO | D024 | | | +| 7.8F.2 | Wide band Intermodulation for shared spectrum channel access | Rel-16 | C001c | UEs supporting 5GS FR1 and operation with shared spectrum | D018 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------|---------------|------------------------------------------------------------------|------------------------------------------|--------|-------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | channel access | | | | +| 7.9 | Spurious emissions | Rel-15 | C001 | UEs supporting 5GS FR1 | D001 | | Skip TC 7.9 if UE supports NSA and TS 38.521-3 TC 7.9B.1 or 7.9B.2 or 7.9B.3 has been executed. | +| 7.9A.1 | Spurious emissions for CA (2DL CA) | Rel-15 | C005 | UEs supporting 5GS FR1 and inter-band 2DL CA with a DL-only band | E002 | | | +| NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.521-1.
NOTE 2: The test case is optional for Rel-17 RedCap UE implementing SUL. | | | | | | | | + +**Table 4.1.1-1a: Void** + +**Table 4.1.1-1b: Void** + +**Table 4.1.1-1c: Void** + +### 4.1.2 FR2 standalone conformance test cases + +**Table 4.1.2-1: Applicability of RF SA FR2 conformance test cases, ref. TS 38.521-2 [2]** + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|-----------|------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6 | Transmitter Characteristics | | | | | | | +| 6.2.1.1 | UE maximum output power - EIRP and TRP | Rel-15 | C006j | Release 15 UEs supporting 5GS FR2 and Release 16 and forward UEs supporting 5GS FR2 and not supporting either CSI-RS or SSB based enhanced Beam Correspondence | D005 | PC1
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2.1.1 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4.1 has been executed. | +| 6.2.1.2 | UE maximum output power - Spherical coverage | Rel-15 | C006j | Release 15 UEs supporting 5GS FR2 and Release 16 and forward UEs supporting 5GS FR2 and not supporting either CSI-RS or SSB based enhanced Beam Correspondence | D005 | PC1
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2.1.2 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4.2 has been executed. | +| 6.2.1.1_1 | UE maximum output power - EIRP and TRP (Rel16 and forward) | Rel-16 | C006k | Release 16 and forward UEs supporting 5GS FR2 and supporting either SSB-based or CSI-RS based enhanced beam correspondence | D005 | PC3 | Skip TC 6.2.1.1_1 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4.1 has been executed. | +| 6.2.1.2_1 | UE maximum output power - Spherical coverage (Rel16 and forward) | Rel-16 | C006k | Release 16 and forward UEs supporting 5GS FR2 and supporting either SSB-based or CSI-RS based enhanced beam correspondence | D005 | PC3 | Skip TC 6.2.1.2_1 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4.2 has been executed. | +| 6.2.2 | UE maximum output power reduction | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2.2 if UE supports NSA and TS 38.521-3 TC 6.2B.2.4 has been executed.
Skip TC 6.2.2 for PC3 UE of Rel-15 and Rel-16 supporting modifiedMPRbehaviour bit 0 or PC3 UE of Rel-17, if TC 6.2.2_1 has been executed. | +| 6.2.2_1 | UE maximum output power reduction enhancements | Rel-15 | C006o | UEs supporting 5GS FR2 and | D005 | PC3 | Skip TC 6.2.2_1 if UE | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|-----------------------------------------------|------------------------------------------|--------|--------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | Rel-16 | | supporting modifiedMPRbehaviour bit 0. | | | supports NSA and TS 38.521-3 TC 6.2B.2.4a has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------------|---------|---------------|----------------------------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | Rel-17 | C006 | UEs supporting 5GS FR2 | | | | +| 6.2.3 | UE maximum output power with additional requirements | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2.3 if UE supports NSA and TS 38.521-3 TC 6.2B.3.4 has been executed. | +| 6.2.4_1 | Configured transmitted power with Power Boost | Rel-16 | C006w | UEs supporting 5GS FR2 and mpr-PowerBoost-FR2-r16 | D005 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2.4_1 if UE supports NSA and TS 38.521-3 TC 6.2B.4.1.4_1 has been executed. | +| 6.2A.1.1.1 | UE maximum output power - EIRP and TRP for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.1.1.1 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4_1.1.1 has been executed. | +| 6.2A.1.1.2 | UE maximum output power - EIRP and TRP for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.1.1.2 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4_1.2.1 has been executed. | +| 6.2A.1.1.3 | UE maximum output power - EIRP and TRP for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.1.1.3 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4_1.3.1 has been executed. | +| 6.2A.1.2.1 | UE maximum output power - Spherical coverage for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.1.2.1 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4_1.1.2 has been executed. | +| 6.2A.1.2.2 | UE maximum output power - Spherical coverage for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.1.2.2 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4_1.2.2 has | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2A.1.2.3 | UE maximum output power - Spherical coverage for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.1.2.3 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4_1.3.2 has been executed. | +| 6.2A.2.1 | UE maximum output power reduction for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2A.2.1 if UE supports NSA and TS 38.521-3 TC 6.2B.2.4_1.1 has been executed. | +| 6.2D.1.1 | UE maximum output power - EIRP and TRP for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL-MIMO | D023 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2D.1.1 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4D.1 has been executed. | +| 6.2D.1.2 | UE maximum output power - Spherical coverage for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL-MIMO | D023 | PC1 (NOTE 1)
PC2
PC3 (NOTE 1)
PC4 (NOTE 1) | Skip TC 6.2D.1.2 if UE supports NSA and TS 38.521-3 TC 6.2B.1.4D.2 has been executed. | +| 6.2.5 | UE Maximum Output Power – EIRP with UL Gaps | Rel-17 | FFS | FFS | FFS | | NOTE 1 | +| 6.3.1 | Minimum output power | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3.1 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4 has been executed. | +| 6.3.2 | Transmit OFF power | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | | +| 6.3.3.2 | General ON/OFF time mask | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.3.3.2 if UE supports NSA and TS 38.521-3 TC 6.3B.3.4 has been executed. | +| 6.3.3.4 | PRACH time mask | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | NOTE 1 | +| 6.3.4.2 | Absolute power tolerance | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.3.4.2 if UE supports NSA and TS 38.521-3 TC 6.3B.8.1.4 has been | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|--------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3.4.3 | Relative power tolerance | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | NOTE 1 | +| 6.3.4.4 | Aggregate power tolerance | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.3.4.2 if UE supports NSA and TS 38.521-3 TC 6.3B.8.3.4 has been executed. | +| 6.3A.1.1 | Minimum output power for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3A.1.1 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.1 has been executed. | +| 6.3A.1.2 | Minimum output power for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3A.1.2 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.2 has been executed. | +| 6.3A.1.3 | Minimum output power for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3A.1.3 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.3 has been executed. | +| 6.3A.1.4 | Minimum output power for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3A.1.4 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.4 has been executed. | +| 6.3A.1.5 | Minimum output power for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3A.1.5 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.5 has been executed. | +| 6.3A.1.6 | Minimum output power for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3 | Skip TC 6.3A.1.6 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.6 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC4 (NOTE 1) | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3A.1.7 | Minimum output power for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3A.1.7 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4_1.7 has been executed. | +| 6.3A.2.1 | Void | | | | | | | +| 6.3A.2.2 | Void | | | | | | | +| 6.3A.2.3 | Void | | | | | | | +| 6.3A.3.1.1 | General ON/OFF time mask for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | NOTE 1 | +| 6.3A.4.2.1 | Absolute power tolerance for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | NOTE 1 | +| 6.3A.4.2.2 | Absolute power tolerance for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | | NOTE 1 | +| 6.3A.4.2.3 | Absolute power tolerance for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | | NOTE 1 | +| 6.3A.4.2.4 | Absolute power tolerance for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | | NOTE 1 | +| 6.3A.4.2.5 | Absolute power tolerance for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | | NOTE 1 | +| 6.3A.4.2.6 | Absolute power tolerance for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | | NOTE 1 | +| 6.3A.4.2.7 | Absolute power tolerance for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | | NOTE 1 | +| 6.3A.4.4.1 | Aggregate power tolerance for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | NOTE 1 | +| 6.3A.4.4.2 | Aggregate power tolerance for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | | NOTE 1 | +| 6.3A.4.4.3 | Aggregate power tolerance for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | | NOTE 1 | +| 6.3A.4.4.4 | Aggregate power tolerance for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | | NOTE 1 | +| 6.3A.4.4.5 | Aggregate power tolerance for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-------------------------------------------|---------|---------------|---------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3A.4.4.6 | Aggregate power tolerance for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | | NOTE 1 | +| 6.3A.4.4.7 | Aggregate power tolerance for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | | NOTE 1 | +| 6.3D.1 | Minimum output power for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.3D.1 if UE supports NSA and TS 38.521-3 TC 6.3B.1.4D has been executed. | +| 6.3D.2 | Transmit OFF power for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | Skip TC 6.3D.2 if UE supports NSA and TS 38.521-3 TC 6.3B.2.4D has been executed. | +| 6.3D.3.1 | General ON/OFF time mask for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.3D.3.4 | Void | | | | | | | +| 6.4.1 | Frequency error | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.4.1 if UE supports NSA and TS 38.521-3 TC 6.4B.1.4 has been executed. | +| 6.4.2.1 | Error vector magnitude | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1
PC2
PC3
PC4 | NOTE 1
Skip TC 6.4.2.1 if UE supports NSA and TS 38.521-3 TC 6.4B.2.4.1 has been executed. | +| 6.4.2.1_1 | Error vector magnitude with Power Boost | Rel-16 | C006w | UEs supporting 5GS FR2 and supporting mpr-PowerBoost-FR2-r16 | D005 | PC1
PC2
PC3
PC4 | NOTE 1
Skip TC 6.4.2.1_1 if UE supports NSA and TS 38.521-3 TC 6.4B.2.4.1a has been executed. | +| 6.4.2.2 | Carrier leakage | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1 (NOTE 1) | Skip TC 6.4.2.2 if UE | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|-------------------------------------|------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | supports NSA and TS
38.521-3 TC
6.4B.2.4.2 has been
executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-------------------------------------------------|---------|---------------|-------------------------------------------------|------------------------------------------|--------------------------|-----------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4.2.3 | In-band emissions | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1
PC2
PC3
PC4 | NOTE 1
Skip TC 6.4.2.3 if UE supports NSA and TS 38.521-3 TC 6.4B.2.4.3 has been executed. | +| 6.4.2.4 | EVM equalizer spectrum flatness | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | NOTE 1
Skip TC 6.4.2.4 if UE supports NSA and TS 38.521-3 TC 6.4B.2.4.4 has been executed. | +| 6.4.2.5 | EVM spectral flatness for pi/2 BPSK modulation | Rel-15 | C006b | UEs supporting 5GS FR2 and pi/2 BPSK modulation | D005 | | NOTE 1
Skip TC 6.4.2.5 if UE supports NSA and TS 38.521-3 TC 6.4B.2.4.5 has been executed. | +| 6.4.2.6 | Phase continuity requirements for DMRS bundling | Rel17 | FFS | UEs supporting 5GS FR2 and DMRS bundling | D005 | | NOTE 1 | +| 6.4A.1.1 | Frequency error for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | NOTE 1 | +| 6.4A.1.2 | Frequency error for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | | NOTE 1 | +| 6.4A.1.3 | Frequency error for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | | NOTE 1 | +| 6.4A.2.1.1 | Error vector magnitude for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.1.2 | Error vector magnitude for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.1.3 | Error vector magnitude for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA | E022 | PC1 | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|----------|------------------------------------------|-------------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | (4UL CA) | | PC2
PC3
PC4 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|----------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|--------------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.4A.2.1.4 | Error vector magnitude for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.1.5 | Error vector magnitude for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.1.6 | Error vector magnitude for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.1.7 | Error vector magnitude for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.2.1 | Carrier leakage for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.2.2 | Carrier leakage for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.2.3 | Carrier leakage for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.2.4 | Carrier leakage for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.2.5 | Carrier leakage for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | PC1
PC2 | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC3
PC4 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|-----------------------------------|---------|---------------|----------------------------------------|------------------------------------------|--------------------------|------------------------| +| | | | Condition | Comment | | | | +| 6.4A.2.2.6 | Carrier leakage for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.2.7 | Carrier leakage for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.1 | In-band emissions for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 CA (2UL CA) | E020 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.2 | In-band emissions for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.3 | In-band emissions for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.4 | In-band emissions for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.5 | In-band emissions for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.6 | In-band emissions for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 6.4A.2.3.7 | In-band emissions for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | PC1
PC2 | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC3
PC4 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|-----------|-------------------------------------------------|---------|---------------|---------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4D.1 | Frequency error for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.4D.3 | Time alignment error for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.5.1 | Occupied bandwidth | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.5.1 if UE supports NSA and TS 38.521-3 TC 6.5B.1.4 has been executed. | +| 6.5.2.1 | Spectrum Emission Mask | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.5.2.1 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.1 has been executed. | +| 6.5.2.1_1 | Spectrum Emission Mask with Power Boost | Rel-16 | C006w | UEs supporting 5GS FR2 and supporting mpr-PowerBoost-FR2-r16 | D005 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5.2.1_1 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.1a has been executed. | +| 6.5.2.3 | Adjacent channel leakage ratio | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.5.2.3 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.3 has been executed. | +| 6.5.3.1 | Transmitter Spurious emissions | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.5.3.1 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1 has been executed. | +| 6.5.3.1_1 | Transmitter Spurious emissions with Power Boost | Rel-16 | C006w | UEs supporting 5GS FR2 and supporting mpr-PowerBoost-FR2-r16 | D005 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5.3.1_1 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1a has been executed. | +| 6.5.3.2 | Spurious emission band UE co-existence | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.5.3.2 if UE supports NSA and TS | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------|----------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 38.521-3 TC
6.5B.3.4.2 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|-----------|---------------------------------------------------------|---------|---------------|---------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5.3.2_1 | Spurious emission band UE co-existence with Power Boost | Rel-16 | C006w | UEs supporting 5GS FR2 and supporting mpr-PowerBoost-FR2-r16 | D005 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5.3.2_1 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2a has been executed. | +| 6.5.3.3 | Additional spurious emissions | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 6.5.3.3 if UE supports NSA and TS 38.521-3 TC 6.5B.4.4 has been executed. | +| 6.5.3.3_1 | Additional spurious emissions with Power Boost | Rel-16 | C006w | UEs supporting 5GS FR2 and supporting mpr-PowerBoost-FR2-r16 | D005 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5.3.3_1 if UE supports NSA and TS 38.521-3 TC 6.5B.4.4a has been executed. | +| 6.5A.1.1 | Occupied bandwidth for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | NOTE 1
Skip TC 6.5A.1.1 if UE supports NSA and TS 38.521-3 TC 6.5B.1.4_1.1 has been executed. | +| 6.5A.1.2 | Occupied bandwidth for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | | NOTE 1
Skip TC 6.5A.1.2 if UE supports NSA and TS 38.521-3 TC 6.5B.1.4_1.2 has been executed. | +| 6.5A.1.3 | Occupied bandwidth for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | | NOTE 1
Skip TC 6.5A.1.3 if UE supports NSA and TS 38.521-3 TC 6.5B.1.4_1.3 has been executed. | +| 6.5A.1.4 | Occupied bandwidth for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|--------|------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5A.1.5 | Occupied bandwidth for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | | NOTE 1 | +| 6.5A.1.6 | Occupied bandwidth for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | | NOTE 1 | +| 6.5A.1.7 | Occupied bandwidth for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | | NOTE 1 | +| 6.5A.2.1.1 | Spectrum Emission Mask for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | Skip TC 6.5A.2.1.1 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.1_1.1 has been executed. | +| 6.5A.2.1.2 | Spectrum Emission Mask for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | | NOTE 1
Skip TC 6.5A.2.1.2 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.1_1.2 has been executed. | +| 6.5A.2.1.3 | Spectrum Emission Mask for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | | NOTE 1
Skip TC 6.5A.2.1.3 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.1_1.3 has been executed. | +| 6.5A.2.1.4 | Spectrum Emission Mask for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | | NOTE 1 | +| 6.5A.2.1.5 | Spectrum Emission Mask for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | | NOTE 1 | +| 6.5A.2.1.6 | Spectrum Emission Mask for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | | NOTE 1 | +| 6.5A.2.1.7 | Spectrum Emission Mask for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | | NOTE 1 | +| 6.5A.2.2.1 | Adjacent channel leakage ratio for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | | Skip TC 6.5A.2.2.1 if UE supports NSA and TS 38.521-3 TC | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------|-----------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 6.5B.2.4.3_1.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5A.2.2.2 | Adjacent channel leakage ratio for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | | Skip TC 6.5A.2.2.2 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.3_1.2 has been executed. | +| 6.5A.2.2.3 | Adjacent channel leakage ratio for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | | Skip TC 6.5A.2.2.3 if UE supports NSA and TS 38.521-3 TC 6.5B.2.4.3_1.3 has been executed. | +| 6.5A.2.2.4 | Adjacent channel leakage ratio for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | | NOTE 1 | +| 6.5A.2.2.5 | Adjacent channel leakage ratio for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | | NOTE 1 | +| 6.5A.2.2.6 | Adjacent channel leakage ratio for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | | NOTE 1 | +| 6.5A.2.2.7 | Adjacent channel leakage ratio for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | | NOTE 1 | +| 6.5A.3.1.1 | General spurious emissions for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 and CA (2UL CA) | E020 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.1.1 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1_1.1 has been executed. | +| 6.5A.3.1.2 | General spurious emissions for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.1.2 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1_1.2 has been executed. | +| 6.5A.3.1.3 | General spurious emissions for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.1.3 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1_1.3 has been executed. | +| 6.5A.3.1.4 | General spurious emissions for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | PC1 (NOTE 1) | Skip TC 6.5A.3.1.4 if UE supports NSA and | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|-------------------------------------|--------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | TS 38.521-3 TC
6.5B.3.4.1_1.4 has
been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5A.3.1.5 | General spurious emissions for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.1.5 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1_1.5 has been executed. | +| 6.5A.3.1.6 | General spurious emissions for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.1.6 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1_1.6 has been executed. | +| 6.5A.3.1.7 | General spurious emissions for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.1.7 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.1_1.7 has been executed. | +| 6.5A.3.2.1 | Spurious emission band UE co-existence for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 CA (2UL CA) | E020 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.1 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.1 has been executed. | +| 6.5A.3.2.2 | Spurious emission band UE co-existence for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.2 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.2 has been executed. | +| 6.5A.3.2.3 | Spurious emission band UE co-existence for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.3 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.3 has been executed. | +| 6.5A.3.2.4 | Spurious emission band UE co-existence for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.4 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.4 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5A.3.2.5 | Spurious emission band UE co-existence for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.5 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.5 has been executed. | +| 6.5A.3.2.6 | Spurious emission band UE co-existence for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.6 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.6 has been executed. | +| 6.5A.3.2.7 | Spurious emission band UE co-existence for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.5A.3.2.7 if UE supports NSA and TS 38.521-3 TC 6.5B.3.4.2_1.7 has been executed. | +| 6.5A.3.3.1 | Additional spurious emissions for CA (2UL CA) | Rel-15 | C053 | UEs supporting 5GS FR2 CA (2UL CA) | E020 | PC1 | Skip TC 6.5A.3.3.1 if UE supports NSA and TS 38.521-3 TC 6.5B.4.4.1_1.1 has been executed. | +| 6.5A.3.3.2 | Additional spurious emissions for CA (3UL CA) | Rel-15 | C054 | UEs supporting 5GS FR2 and CA (3UL CA) | E021 | PC1 | Skip TC 6.5A.3.3.2 if UE supports NSA and TS 38.521-3 TC 6.5B.4.4.1_1.2 has been executed. | +| 6.5A.3.3.3 | Additional spurious emissions for CA (4UL CA) | Rel-15 | C055 | UEs supporting 5GS FR2 and CA (4UL CA) | E022 | PC1 | Skip TC 6.5A.3.3.3 if UE supports NSA and TS 38.521-3 TC 6.5B.4.4.3_1.3 has been executed. | +| 6.5A.3.3.4 | Additional spurious emissions for CA (5UL CA) | Rel-15 | C056 | UEs supporting 5GS FR2 and CA (5UL CA) | E023 | | NOTE 1 | +| 6.5A.3.3.5 | Additional spurious emissions for CA (6UL CA) | Rel-15 | C057 | UEs supporting 5GS FR2 and CA (6UL CA) | E024 | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|------------|----------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|----------------------------|-------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5A.3.3.6 | Additional spurious emissions for CA (7UL CA) | Rel-15 | C058 | UEs supporting 5GS FR2 and CA (7UL CA) | E025 | | NOTE 1 | +| 6.5A.3.3.7 | Additional spurious emissions for CA (8UL CA) | Rel-15 | C059 | UEs supporting 5GS FR2 and CA (8UL CA) | E026 | | NOTE 1 | +| 6.5D.1 | Occupied bandwidth for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.5D.2.1 | Spectrum Emission Mask for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.5D.2.2 | Adjacent channel leakage ratio for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.5D.3.1 | Transmitter Spurious emissions for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.5D.3.2 | Spurious emission band UE co-existence for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.5D.3.3 | Additional spurious emissions for UL MIMO | Rel-15 | C060 | UEs supporting 5GS FR2 and UL MIMO | D023 | | NOTE 1 | +| 6.6.1 | Beam correspondence - EIRP | Rel-15 | C008 | Release 15 UEs supporting 5GS FR2 and not beam correspondence without UL beam sweeping and release 16 and forward UEs that do not support SSB-based or CSI-RS based enhanced beam correspondence and do not support enhanced beam correspondence without UL beam sweeping | D005 | PC3 | Skip TC 6.6.1 if UE supports NSA and TS 38.521-3 TC 6.6B.4 has been executed. | +| 6.6.2 | Enhanced Beam correspondence - EIRP | Rel-16 | C008a | UEs supporting 5GS FR2 and support either CSI-RS or SSB based beam correspondence and do not support beam correspondence without UL beam sweeping | D005 | PC3 | Skip TC 6.6.2 if UE supports NSA and TS 38.521-3 TC 6.6B.5 has been executed. | +| 7 | Receiver Characteristics | | | | | | | +| 7.3.2 | Reference sensitivity power level | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1
PC2 (NOTE 1)
PC3 | Skip TC 7.3.2 if UE supports NSA and TS 38.521-3 TC 7.3B.2.4 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|--------------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC4 (NOTE 1) | has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|---------------------------------------------------|---------|---------------|----------------------------------------|------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.3A.2.1 | Reference sensitivity power level for CA (2DL CA) | Rel-15 | C006c | UEs supporting 5GS FR2 and CA (2DL CA) | E032 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 7.3A.2.1 if UE supports NSA and TS 38.521-3 TC
7.3B.2.4_1.1 has been executed | +| 7.3A.2.2 | Reference sensitivity power level for CA (3DL CA) | Rel-15 | C006d | UEs supporting 5GS FR2 and CA (3DL CA) | E033 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 7.3A.2.2 if UE supports NSA and TS 38.521-3 TC
7.3B.2.4_1.2 has been executed | +| 7.3A.2.3 | Reference sensitivity power level for CA (4DL CA) | Rel-15 | C006e | UEs supporting 5GS FR2 and CA (4DL CA) | E034 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 7.3A.2.3 if UE supports NSA and TS 38.521-3 TC
7.3B.2.4_1.3 has been executed | +| 7.3A.2.4 | Reference sensitivity power level for CA (5DL CA) | Rel-15 | C006f | UEs supporting 5GS FR2 and CA (5DL CA) | E035 | PC1
PC2
PC3
PC4 | NOTE 1
Skip TC 7.3A.2.4 if UE supports NSA and TS 38.521-3 TC
7.3B.2.4_1.4 has been executed | +| 7.3A.2.5 | Reference sensitivity power level for CA (6DL CA) | Rel-15 | C006g | UEs supporting 5GS FR2 and CA (6DL CA) | E036 | PC1
PC2
PC3
PC4 | NOTE 1
Skip TC 7.3A.2.5 if UE supports NSA and TS 38.521-3 TC
7.3B.2.4_1.5 has been executed | +| 7.3A.2.6 | Reference sensitivity power level for CA (7DL CA) | Rel-15 | C006h | UEs supporting 5GS FR2 and CA (7DL CA) | E037 | PC1
PC2
PC3
PC4 | NOTE 1
Skip TC 7.3A.2.6 if UE supports NSA and TS 38.521-3 TC
7.3B.2.4_1.6 has been executed | +| 7.3A.2.7 | Reference sensitivity power level for CA (8DL CA) | Rel-15 | C006i | UEs supporting 5GS FR2 and CA (8DL CA) | E038 | PC1
PC2 | NOTE 1
Skip TC 7.3A.2.7 if UE | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|------------------------------------------|------------|-------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC3
PC4 | supports NSA and TS
38.521-3 TC
7.3B.2.4_1.7 has been
executed | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|---------------------------------------------------|---------|---------------|-------------------------------------------|------------------------------------------|--------------------------|-------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.3A.3.1 | EIS spherical coverage for Inter-band CA (2DL CA) | Rel-16 | C006c | UEs supporting 5GS FR2 and CA (2DL CA) | E032 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3A.3.2 | EIS spherical coverage for Inter-band CA (3DL CA) | Rel-16 | C006d | UEs supporting 5GS FR2 and CA (3DL CA) | E033 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3A.3.3 | EIS spherical coverage for Inter-band CA (4DL CA) | Rel-16 | C006e | UEs supporting 5GS FR2 and CA (4DL CA) | E034 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3A.3.4 | EIS spherical coverage for CA (5DL CA) | Rel-16 | C006f | UEs supporting 5GS FR2 and CA (5DL CA) | E035 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3A.3.5 | EIS spherical coverage for CA (6DL CA) | Rel-16 | C006g | UEs supporting 5GS FR2 and CA (6DL CA) | E036 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3A.3.6 | EIS spherical coverage for CA (7DL CA) | Rel-16 | C006h | UEs supporting 5GS FR2 and CA (7DL CA) | E037 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3A.3.7 | EIS spherical coverage for CA (8DL CA) | Rel-16 | C006i | UEs supporting 5GS FR2 and CA (8DL CA) | E038 | PC1
PC2
PC3
PC4 | NOTE 1 | +| 7.3.4 | EIS spherical coverage | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | PC1
PC2
PC3
PC4 | Skip TC 7.3.4 if UE supports NSA and TS 38.521-3 TC 7.3B.4 has been executed. | +| 7.4 | Maximum input level | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|--------|-------------------------------------|---------|---------------|-------------------------------------------|------------------------------------------|--------|---------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.4A.1 | Maximum input level for CA (2DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.4A.2 | Maximum input level for CA (3DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.4A.3 | Maximum input level for CA (4DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.4A.4 | Maximum input level for CA (5DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.4A.5 | Maximum input level for CA (6DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.4A.6 | Maximum input level for CA (7DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.4A.7 | Maximum input level for CA (8DL CA) | Rel-15 | N/A | not recommended due to testability issues | N/A | | NOTE 1 | +| 7.5 | Adjacent channel selectivity | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 7.5 if UE supports NSA and TS 38.521-3 TC 7.5B.4 has been executed. | +| 7.6.2 | In-band blocking | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 7.6.2 if UE supports NSA and TS 38.521-3 TC 7.6B.2.4 has been executed. | +| 7.9 | Spurious emissions | Rel-15 | C006 | UEs supporting 5GS FR2 | D005 | | Skip TC 7.9 if UE supports NSA and TS 38.521-3 TC 7.9B.4 has been executed. | + +NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band/CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.521-2. + +NOTE 2: Void. + +NOTE 3: Void. + +NOTE 4: Void. + +**Table 4.1.2-1a: Void** + +**Table 4.1.2-1b: Void** + +**Table 4.1.2-1c: Void** + +### 4.1.3 NR interworking between NR FR1 and NR FR2 and between NR and LTE conformance test cases + +**Table 4.1.3-1: Applicability of RF EN-DC FR1 and FR2 conformance test cases, ref. TS 38.521-3 [3]** + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|--------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6 | Transmitter characteristics | | | | | | | +| 6.2B | Transmitter power for DC | | | | | | | +| 6.2B.1.1 | UE Maximum Output Power for Intra-Band Contiguous EN-DC | Rel-15 | C009 | UEs supporting Intra-Band Contiguous EN-DC (2UL CCs) | E003 | | | +| 6.2B.1.2 | UE Maximum Output Power for Intra-Band Non-Contiguous EN-DC | Rel-15 | C010 | UEs supporting Intra-Band non-contiguous EN-DC (2UL CCs) | E004 | | | +| 6.2B.1.3 | UE Maximum Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) | Rel-15 | C011 | UEs supporting Inter-Band EN-DC within FR1 (2UL CCs) | E005
E005d | PC3
PC2 | | +| 6.2B.1.3_1 | UE Maximum Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) | Rel-16 | C011d | UEs supporting Inter-Band EN-DC within FR1 (2UL E-UTRA CCs, 1UL NR CC) | E005z | PC3 | | +| 6.2B.1.4.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP and TRP | Rel-15 | C012 | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC | E010 | PC1
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.2B.1.4.1 if UE supports SA and TSC 38.521-2 TC 6.2.1.1 has been executed. | +| 6.2B.1.4.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - Spherical Coverage | Rel-15 | C012 | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC | E010 | PC1
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.2B.1.4.2 if UE supports SA and TSC 38.521-2 TC 6.2.1.2 has been executed. | +| 6.2B.1.4_1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.2B.1.4_1.1.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - EIRP and TRP | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.2B.1.4_1.1.1 if UE supports SA and TS 38.521-2 TC 6.2A.1.1.1 has been executed. | +| 6.2B.1.4_1.1.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 NR CCs) - Spherical Coverage | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | PC1 (NOTE 1)
PC2 (NOTE 1) | NOTE 5
Skip TC | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|---------------------|--------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | PC3
PC4 (NOTE 1) | 6.2B.1.4_1.1.2 if UE supports SA and TS 38.521-2 TC
6.2A.1.2.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|----------------|--------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2B.1.4_1.2.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - EIRP and TRP | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC
6.2B.1.4_1.2.1 if UE supports SA and TS 38.521-2 TC
6.2A.1.1.2 has been executed. | +| 6.2B.1.4_1.2.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (3 NR CCs) - Spherical Coverage | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC
6.2B.1.4_1.2.2 if UE supports SA and TS 38.521-2 TC
6.2A.1.2.2 has been executed. | +| 6.2B.1.4_1.3.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) - EIRP and TRP | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC
6.2B.1.4_1.3.1 if UE supports SA and TS 38.521-2 TC
6.2A.1.1.3 has been executed. | +| 6.2B.1.4_1.3.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (4 NR CCs) - Spherical Coverage | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC
6.2B.1.4_1.3.2 if UE supports SA and TS 38.521-2 TC
6.2A.1.2.3 has been executed. | +| 6.2B.1.4D.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 for UL MIMO - EIRP and TRP | Rel-15 | C012p | UEs supporting Inter-Band EN-DC including FR2 and UL MIMO | E043 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.2B.1.4D.1 if UE supports SA and TS 38.521-2 TC
6.2D.1.1 has been executed. | +| 6.2B.1.4D.2 | UE Maximum Output Power for Inter-Band EN-DC | Rel-15 | C012p | UEs supporting Inter-Band EN-DC | E043 | PC1 (NOTE 1) | NOTE 5 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|------------------------------------------------|---------|---------------|---------------------------|---------------------------------------------|-------------------------------------|--------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | including FR2 for UL MIMO - Spherical Coverage | | | including FR2 and UL MIMO | | PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | Skip TC 6.2B.1.4D.2 if UE supports SA and TS 38.521-2 TC 6.2D.1.2 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-----------|---------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2B.1.6 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (1 NR CC) - EIRP with UL Gaps | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 and Uplink Gaps | E011 | PC1
PC2
PC3
PC4 | NOTE 1
NOTE 5
Skip TC 6.2B.1.6 if UE supports SA and TS 38.521-2 TC 6.2.5 has been executed. | +| 6.2B.2.1 | UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | Rel-15 | C009 | UEs supporting Intra-Band Contiguous EN-DC (2UL CCs) | E003 | | Test execution is not necessary if TS 38.521-3 TC 6.5B.2.1.3 is executed. | +| 6.2B.2.2 | UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | Rel-15 | C010 | UEs supporting Intra-Band non-contiguous EN-DC (2UL CCs) | E004 | | Test execution is not necessary if TS 38.521-3 TC 6.5B.2.2.3 has been executed. | +| 6.2B.2.3 | UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 (1 NR CC) | Rel-15 | C011 | UEs supporting Inter-Band EN-DC within FR1 with 1 NR UL CC | E005b | PC3
PC2 | NOTE 5
Test execution is not necessary if TS 38.521-3 TC 6.5B.2.3.3.1 is executed.
Skip TC 6.2B.2.3 if UE supports SA and TS 38.521-1 TC 6.2.2 or 6.5.2.4.1 has been executed. | +| 6.2B.2.4 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) | Rel-15 | C012z | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC and modified MPR behaviour | E010 | | NOTE 1
NOTE 5
Skip TC 6.2B.2.4 if UE supports SA and TS 38.521-2 TC 6.2.2 has been executed. | +| 6.2B.2.4a | UE maximum output power reduction enhancements for Inter-Band EN-DC including FR2 (1 NR CC) | Rel-16 | C012q | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC and | E010 | PC3 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|-------------------------------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | modified MPR behaviour bit 0. | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|-------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------|---------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2B.2.4_1 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.2B.2.4_1.1 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012m | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 1
NOTE 5
Skip TC 6.2B.2.4_1.1 if UE supports SA and TS 38.521-2 TC 6.2A.2.1 has been executed. | +| 6.2B.2.4_1.2 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012n | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 1
NOTE 5
Skip TC 6.2B.2.4_1.1 if UE supports SA and TS 38.521-2 TC 6.2A.2.2 has been executed. | +| 6.2B.2.4_1.3 | UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012o | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 1
NOTE 5
Skip TC 6.2B.2.4_1.1 if UE supports SA and TS 38.521-2 TC 6.2A.2.3 has been executed. | +| 6.2B.3.1 | UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC | Rel-15 | C009z | UEs supporting Intra-Band Contiguous EN-DC (2UL CCs) and modified MPR behaviour | E003 | | | +| 6.2B.3.2 | UE Additional Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | Rel-15 | FFS | FFS | FFS | | NOTE 1 | +| 6.2B.3.3 | UE Additional Maximum Output power reduction for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011z | UEs supporting Inter-Band EN-DC within FR1 with 1 NR UL CC and modified MPR behaviour | E005b | PC3
PC2 | NOTE 5
Test execution is not necessary if TS 38.521-3 TCs | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 6.5B.2.3.2,
6.5B.2.3.3.2 and
6.5B.4.3 are executed.
Skip TC 6.2B.3.3 if UE
supports SA and TS
38.521-1 TC 6.2.3 has
been executed, or TS
38.521-1 TCs 6.5.2.3,
6.5.2.4.2 and 6.5.3.3
have been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------------|-------------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.2B.3.4 | UE Additional Maximum Output Power reduction for Inter-Band EN-DC including FR2 (1 NR CC) | Rel-15 | C012z | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC and modified MPR behaviour | E010 | PC3
PC2 | NOTE 5
Skip TC 6.2B.3.4 if UE supports SA and TS 38.521-2 TC 6.2.3 has been executed. | +| 6.2B.4.1.1 | Configured Output Power Level for Intra-Band Contiguous EN-DC | Rel-15 | C009 | UEs supporting Intra-Band Contiguous EN-DC (2UL CCs) | E003 | | | +| 6.2B.4.1.2 | Configured Output Power for Intra-Band Non-Contiguous EN-DC | Rel-15 | C010 | UEs supporting Intra-Band Non-Contiguous EN-DC (2UL CCs) | E004 | | | +| 6.2B.4.1.3 | Configured Output Power for Inter-Band EN-DC within FR1 (1 E-UTRA CC, 1 NR CC) | Rel-15 | C011 | UEs supporting Inter-Band EN-DC within FR1 (2UL CCs) | E005 | | | +| 6.2B.4.1.3_1 | Configured Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CCs, 1 NR CC) | Rel-16 | C011d | UEs supporting Inter-Band EN-DC within FR1 (2UL E-UTRA CCs, 1UL NR CC) | E005z | PC3 | | +| 6.2B.4.1.4 | Configured Output Power for Inter-Band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC | E010 | | | +| 6.2B.4.1.4_1 | Configured Output Power with Power Boost for Inter-Band EN-DC including FR2 (1 NR CC) | Rel-16 | C012w | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC and mpr-PowerBoost-FR2-r16 | E010 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.2B.4.1.4_1 if UE supports NSA and TS 38.521-2 TC 6.2.4_1 has been executed. | +| 6.3B | Output power dynamics for DC | | | | | | | +| 6.3B.1.1 | Minimum Output power for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.3B.1.2 | Minimum output power for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.3B.1.2 if UE supports SA and TS 38.521-1 TC 6.3.1 has been executed. | +| 6.3B.1.3 | Minimum output power for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.1.3 if UE supports SA and TS 38.521-1 TC 6.3.1 has | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3B.1.4 | Minimum Output Power for EN-DC Interband including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.3B.1.4 if UE supports SA and TS 38.521-2 TC 6.3.1 has been executed. | +| 6.3B.1.4_1 | Minimum output power for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.3B.1.4_1.1 | Minimum output power for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC 6.3B.1.4_1.1 if UE supports SA and TS 38.521-2 TC 6.3A.1.1 has been executed. | +| 6.3B.1.4_1.2 | Minimum output power for inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 5
Skip TC 6.3B.1.4_1.2 if UE supports SA and TS 38.521-2 TC 6.3A.1.2 has been executed. | +| 6.3B.1.4_1.3 | Minimum output power for inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 5
Skip TC 6.3B.1.4_1.3 if UE supports SA and TS 38.521-2 TC 6.3A.1.3 has been executed. | +| 6.3B.1.4D | Minimum output power for inter-band EN-DC including FR2 for UL MIMO | Rel-15 | C012p | UEs supporting inter-band EN-DC including FR2 and UL MIMO | E043 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.3B.1.4D if UE supports SA and TS 38.521-2 TC 6.3D.1 has been executed. | +| 6.3B.2.4 | Transmit OFF Power for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC | E005 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|-----------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3B.2.4_1 | Void | | | | | | | +| 6.3B.2.4D | Transmit OFF Power for inter-band EN-DC including FR2 for UL-MIMO | Rel-15 | C012p | UEs supporting inter-band EN-DC including FR2 and UL MIMO | E043 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.3B.2.4D if UE supports SA and TS 38.521-2 TC 6.3D.2 has been executed. | +| 6.3B.3.1 | Transmit ON/OFF time mask for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.3B.3.1 if UE supports SA and TS 38.521-1 TC 6.3.3.2 has been executed. | +| 6.3B.3.2 | Transmit ON/OFF time mask for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.3B.3.2 if UE supports SA and TS 38.521-1 TC 6.3.3.2 has been executed. | +| 6.3B.3.3 | Transmit ON/OFF time mask for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.3.3 if UE supports SA and TS 38.521-1 TC 6.3.3.2 has been executed. | +| 6.3B.3.4 | Transmit ON/OFF time mask for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.3B.3.4 if UE supports SA and TS 38.521-2 TC 6.3.3.2 has been executed. | +| 6.3B.3.4_1 | Transmit ON/OFF time mask for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.3B.3.4_1.1 | Transmit ON/OFF time mask for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012b | UEs supporting inter-band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC 6.3B.3.4_1.1 if UE supports SA and TS 38.521-2 TC 6.3A.3.1.1 has been | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|------------|--------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------|---------------------------------------------|--------|------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3B.3_1.1 | E-UTRA and NR switching time mask for switching between two uplink carriers for inter-band EN-DC | Rel-16 | C126a | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC and dynamic UL Tx switching | E031b | | NOTE 1 | +| 6.3B.4.1 | PRACH time mask for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.3B.4.1 if UE supports SA and TS 38.521-1 TC 6.3.3.4 has been executed. | +| 6.3B.4.2 | PRACH Time Mask for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.3B.4.2 if UE supports SA and TS 38.521-1 TC 6.3.3.4 has been executed. | +| 6.3B.4.3 | PRACH Time Mask for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.4.3 if UE supports SA and TS 38.521-1 TC 6.3.3.4 has been executed. | +| 6.3B.4.4 | PRACH Time Mask for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC | E010 | | NOTE 1
NOTE 5
Skip TC 6.3B.4.4 if UE supports SA and TS 38.521-2 TC 6.3.3.4 has been executed. | +| 6.3B.8.1.1 | Absolute Power Tolerance for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2 UL CCs) | E003 | | NOTE 5
Skip TC 6.3B.8.1.1 if UE supports SA and TS 38.521-1 TC 6.3.4.2 has been executed. | +| 6.3B.8.1.2 | Absolute Power Tolerance for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2 UL CCs) | E004 | | NOTE 5
Skip TC 6.3B.8.1.2 if UE supports SA and TS 38.521-1 TC 6.3.4.2 has been | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|------------|-----------------------------------------------------------------------|---------|---------------|------------------------------------------------------------|---------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3B.8.1.3 | Absolute Power Tolerance for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.8.1.3 if UE supports SA and TS 38.521-1 TC 6.3.4.2 has been executed. | +| 6.3B.8.1.4 | Absolute Power Tolerance for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.8.1.4 if UE supports SA and TS 38.521-2 TC 6.3.4.2 has been executed. | +| 6.3B.8.2.1 | Relative Power Tolerance for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2 UL CCs) | E003 | | NOTE 5
Skip TC 6.3B.8.2.1 if UE supports SA and TS 38.521-1 TC 6.3.4.3 has been executed. | +| 6.3B.8.2.2 | Relative Power Tolerance for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2 UL CCs) | E004 | | NOTE 5
Skip TC 6.3B.8.2.2 if UE supports SA and TS 38.521-1 TC 6.3.4.3 has been executed. | +| 6.3B.8.2.3 | Relative Power Tolerance for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.8.2.3 if UE supports SA and TS 38.521-1 TC 6.3.4.3 has been executed. | +| 6.3B.8.2.4 | Relative Power Tolerance for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | FFS | FFS | FFS | | NOTE 1 | +| 6.3B.8.3.1 | Aggregate Power Tolerance for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2 UL CCs) | E003 | | NOTE 5
Skip TC 6.3B.8.3.1 if UE supports SA and | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|-------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | TS 38.521-1 TC 6.3.4.4 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------|------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------|---------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.3B.8.3.2 | Aggregate Power Tolerance for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2 UL CCs) | E004 | | NOTE 5
Skip TC 6.3B.8.3.2 if UE supports SA and TS 38.521-1 TC 6.3.4.4 has been executed. | +| 6.3B.8.3.3 | Aggregate Power Tolerance for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.8.3.3 if UE supports SA and TS 38.521-1 TC 6.3.4.4 has been executed. | +| 6.3B.8.3.4 | Aggregate Power Tolerance for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.3B.8.3.4 if UE supports SA and TS 38.521-2 TC 6.3.4.4 has been executed. | +| 6.4B | Transmit Signal Quality for DC | | | | | | | +| 6.4B.1.1 | Frequency Error for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting Intra-Band Contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.4B.1.1 if UE supports SA and TS 38.521-1 TC 6.4.1 has been executed. | +| 6.4B.1.2 | Frequency Error for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.4B.1.2 if UE supports SA and TS 38.521-1 TC 6.4.1 has been executed. | +| 6.4B.1.3 | Frequency error for Inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.4B.1.3 if UE supports SA and TS 38.521-1 TC 6.4.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|-------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|--------|-------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4B.1.4 | Frequency Error for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-Band EN-DC including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.4B.1.4 if UE supports SA and TS 38.521-2 TC 6.4.1 has been executed. | +| 6.4B.1.4_1 | Frequency Error for Inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.4B.1.4_1.1 | Frequency Error for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC 6.4B.1.4_1.1 if UE supports SA and TS 38.521-2 TC 6.4A.1.1 has been executed. | +| 6.4B.1.4_1.2 | Frequency Error for inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 5
Skip TC 6.4B.1.4_1.2 if UE supports SA and TS 38.521-2 TC 6.4A.1.2 has been executed. | +| 6.4B.1.4_1.3 | Frequency Error for inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 5
Skip TC 6.4B.1.4_1.3 if UE supports SA and TS 38.521-2 TC 6.4A.1.3 has been executed. | +| 6.4B.2.1.1 | Error Vector Magnitude for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.4B.2.1.1 if UE supports SA and TS 38.521-1 TC 6.4.2.1 has been executed. | +| 6.4B.2.1.2 | Carrier Leakage for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.4B.2.1.2 if UE supports SA and TS 38.521-1 TC | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|----------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 6.4.2.2 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|------------|------------------------------------------------------------------|---------|---------------|------------------------------------------------------------|---------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4B.2.1.3 | In-band Emissions for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.4B.2.1.4 | EVM Equalizer Flatness for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.4B.2.1.4 if UE supports SA and TS 38.521-1 TC 6.4.2.4 has been executed. | +| 6.4B.2.2.1 | Error Vector Magnitude for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.4B.2.2.1 if UE supports SA and TS 38.521-1 TC 6.4.2.1 has been executed. | +| 6.4B.2.2.2 | Carrier Leakage for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.4B.2.2.2 if UE supports SA and TS 38.521-1 TC 6.4.2.2 has been executed. | +| 6.4B.2.2.3 | In-band Emissions for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.4B.2.2.3 if UE supports SA and TS 38.521-1 TC 6.4.2.3 has been executed. | +| 6.4B.2.2.4 | EVM Equalizer Flatness for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.4B.2.2.4 if UE supports SA and TS 38.521-1 TC 6.4.2.4 has been executed. | +| 6.4B.2.3.1 | Error Vector Magnitude for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.4B.2.3.1 if UE supports SA and | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|-------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | TS 38.521-1 TC 6.4.2.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|--------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4B.2.3.2 | Carrier Leakage for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.4B.2.3.2 if UE supports SA and TS 38.521-1 TC 6.4.2.2 has been executed. | +| 6.4B.2.3.3 | In-band Emissions for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.4B.2.3.3 if UE supports SA and TS 38.521-1 TC 6.4.2.3 has been executed. | +| 6.4B.2.3.4 | EVM Equalizer Flatness for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.4B.2.3.4 if UE supports SA and TS 38.521-1 TC 6.4.2.4 has been executed. | +| 6.4B.2.4.1 | Error Vector Magnitude for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 1
NOTE 5
Skip TC 6.4B.2.4.1 if UE supports SA and TS 38.521-2 TC 6.4.2.1 has been executed. | +| 6.4B.2.4.1a | Error Vector Magnitude with Power Boost for inter-band EN-DC including FR2 (1 NR CC) | Rel-16 | C012w | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC and mpr-PowerBoost-FR2-r16 | E010 | PC1
PC2
PC3
PC4 | NOTE 1
NOTE 5
Skip TC 6.4B.2.4.1a if UE supports SA and TS 38.521-2 TC 6.4.2.1_1 has been executed. | +| 6.4B.2.4.1_1 | Error Vector Magnitude for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.4B.2.4.1_1.1 | Error Vector Magnitude for inter-band EN-DC | Rel-15 | FFS | FFS | FFS | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|--------------------------|---------|---------------|---------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | including FR2 (2 NR CCs) | | | | | | NOTE 5
Skip TC
6.4B.2.4.1_1.1 if UE supports SA and TS 38.521-2 TC
6.4A.2.1.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|-------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------|---------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4B.2.4.1_1.2 | Error Vector Magnitude for inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC
6.4B.2.4.1_1.2 if UE supports SA and TS 38.521-2 TC
6.4A.2.1.2 has been executed. | +| 6.4B.2.4.1_1.3 | Error Vector Magnitude for inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC
6.4B.2.4.1_1.3 if UE supports SA and TS 38.521-2 TC
6.4A.2.1.3 has been executed. | +| 6.4B.2.4.1D | Error Vector Magnitude for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.2 | Carrier Leakage for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.4B.2.4.2 if UE supports SA and TS 38.521-2 TC
6.4.2.2 has been executed. | +| 6.4B.2.4.2_1 | Carrier Leakage for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.4B.2.4.2_1.1 | Carrier Leakage for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC
6.4B.2.4.2_1.1 if UE supports SA and TS 38.521-2 TC
6.4A.2.2.1 has been executed. | +| 6.4B.2.4.2_1.2 | Carrier Leakage for inter-band EN-DC including FR2 | Rel-15 | FFS | FFS | FFS | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|------------|---------|---------------|---------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | (3 NR CCs) | | | | | | NOTE 5
Skip TC
6.4B.2.4.2_1.2 if UE supports SA and TS 38.521-2 TC
6.4A.2.2.2 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|---------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------|---------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4B.2.4.2_1.3 | Carrier Leakage for inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC 6.4B.2.4.2_1.3 if UE supports SA and TS 38.521-2 TC 6.4A.2.2.3 has been executed. | +| 6.4B.2.4.2D | Carrier Leakage for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.3 | In-band Emissions for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 1
NOTE 5
Skip TC 6.4B.2.4.3 if UE supports SA and TS 38.521-2 TC 6.4.2.3 has been executed. | +| 6.4B.2.4.3D | In-band Emissions for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.3_1 | In-band Emissions for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.4B.2.4.3_1.1 | In-band Emissions for inter-band EN-DC including FR2 (2 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.3_1.2 | In-band Emissions for inter-band EN-DC including FR2 (3 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.3_1.3 | In-band Emissions for inter-band EN-DC including FR2 (4 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.4 | EVM Equalizer Flatness for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 1
NOTE 5
Skip TC 6.4B.2.4.4 if UE supports SA and TS 38.521-2 TC 6.4.2.4 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|---------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------|---------------------------------------------|--------|--------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.4B.2.4.4D | EVM Equalizer Flatness for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.4B.2.4.5 | EVM spectral flatness for pi/2 BPSK modulation for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012f | UEs supporting Inter-band including FR2 with 1 NR UL CC and pi/2 BPSK modulation | E010 | | NOTE 1
NOTE 5
Skip TC 6.4B.2.4.5 if UE supports SA and TS 38.521-2 TC 6.4.2.5 has been executed. | +| 6.5B | Output RF spectrum emissions for DC | | | | | | | +| 6.5B.1.1 | Occupied bandwidth for Intra-Band Contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 1 | +| 6.5B.1.2 | Occupied bandwidth for Intra-Band Non-Contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 1
NOTE 5
Skip TC 6.5B.1.2 if UE supports SA and TS 38.521-1 TC 6.5.1 has been executed. | +| 6.5B.1.3 | Occupied bandwidth for Inter-Band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.1.3 if UE supports SA and TS 38.521-1 TC 6.5.1 has been executed. | +| 6.5B.1.4 | Occupied bandwidth for Inter-Band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.5B.1.4 if UE supports SA and TS 38.521-2 TC 6.5.1 has been executed. | +| 6.5B.1.4D | Occupied bandwidth for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.5B.1.4_1 | Occupied bandwidth for Inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.5B.1.4_1.1 | Occupied bandwidth for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|---------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | Skip TC 6.5B.1.4_1.1 if UE supports SA and TS 38.521-2 TC 6.5A.1.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------------|------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.1.4_1.2 | Occupied bandwidth for inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC 6.5B.1.4_1.2 if UE supports SA and TS 38.521-2 TC 6.5A.1.2 has been executed. | +| 6.5B.1.4_1.3 | Occupied bandwidth for inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC 6.5B.1.4_1.3 if UE supports SA and TS 38.521-2 TC 6.5A.1.3 has been executed. | +| 6.5B.2.1.1 | Spectrum emissions mask for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.5B.2.1.2 | Additional spectrum emissions mask for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.5B.2.1.3 | Adjacent channel leakage ratio for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.5B.2.2.1 | Spectrum emissions mask for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | | +| 6.5B.2.2.2 | Additional Spectrum emissions mask for intra-band non-contiguous EN-DC | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.5B.2.2.3 | Adjacent channel leakage ratio for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | | +| 6.5B.2.3.1 | Spectrum emissions mask for Inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting Inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.2.3.1 if UE supports SA and TS 38.521-1 TC 6.5.2.2 has been executed. | +| 6.5B.2.3.2 | Additional Spectrum emissions mask for Inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting Inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.2.3.2 if UE supports SA and | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|-------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | TS 38.521-1 TC 6.5.2.3 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|---------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.2.3.3.1 | NR - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting Inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.2.3.3.1 if UE supports SA and TS 38.521-1 TC 6.5.2.4.1 has been executed. | +| 6.5B.2.3.3.2 | UTRA - Adjacent channel leakage ratio for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting Inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.2.3.3.2 if UE supports SA and TS 38.521-1 TC 6.5.2.4.2 has been executed. | +| 6.5B.2.4.1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.5B.2.4.1 if UE supports SA and TS 38.521-2 TC 6.5.2.1 has been executed. | +| 6.5B.2.4.1a | Spectrum emissions mask with Power Boost for Inter-band EN-DC including FR2 (1 NR CC) | Rel-16 | C012w | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC and mpr-PowerBoost-FR2-r16 | E010 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.5B.2.4.1a if UE supports SA and TS 38.521-2 TC 6.5.2.1_1 has been executed. | +| 6.5B.2.4.1_1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.5B.2.4.1_1.1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC 6.5B.2.4.1_1.1 if UE supports SA and TS 38.521-2 TC 6.5A.2.1.1 has been executed. | +| 6.5B.2.4.1_1.2 | Spectrum emissions mask for Inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 5
Skip TC | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|--------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 6.5B.2.4.1_1.2 if UE supports SA and TS 38.521-2 TC
6.5A.2.1.2 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|----------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.2.4.1_1.3 | Spectrum emissions mask for Inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 5
Skip TC 6.5B.2.4.1_1.3 if UE supports SA and TS 38.521-2 TC 6.5A.2.1.3 has been executed. | +| 6.5B.2.4.3 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.5B.2.4.3 if UE supports SA and TS 38.521-2 TC 6.5.2.3 has been executed. | +| 6.5B.2.4.3_1 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.5B.2.4.3_1.1 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC 6.5B.2.4.3_1.1 if UE supports SA and TS 38.521-2 TC 6.5A.2.2.1 has been executed. | +| 6.5B.2.4.3_1.2 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 5
Skip TC 6.5B.2.4.3_1.2 if UE supports SA and TS 38.521-2 TC 6.5A.2.2.2 has been executed. | +| 6.5B.2.4.3_1.3 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 5
Skip TC 6.5B.2.4.3_1.3 if UE supports SA and TS 38.521-2 TC 6.5A.2.2.3 has been | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|----------------|-------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.2.4.3_1.4 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (5 NR CCs) | Rel-15 | C012i | UEs supporting Inter-Band EN-DC including FR2 with 5 NR UL CCs | E014a | | NOTE 1
NOTE 5
Skip TC
6.5B.2.4.3_1.4 if UE supports SA and TS 38.521-2 TC
6.5A.2.2.4 has been executed. | +| 6.5B.2.4.3_1.5 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (6 NR CCs) | Rel-15 | C012j | UEs supporting Inter-Band EN-DC including FR2 with 6 NR UL CCs | E039 | | NOTE 1
NOTE 5
Skip TC
6.5B.2.4.3_1.5 if UE supports SA and TS 38.521-2 TC
6.5A.2.2.5 has been executed. | +| 6.5B.2.4.3_1.6 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (7 NR CCs) | Rel-15 | C012k | UEs supporting Inter-Band EN-DC including FR2 with 7 NR UL CCs | E040 | | NOTE 1
NOTE 5
Skip TC
6.5B.2.4.3_1.6 if UE supports SA and TS 38.521-2 TC
6.5A.2.2.6 has been executed. | +| 6.5B.2.4.3_1.7 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (8 NR CCs) | Rel-15 | C012l | UEs supporting Inter-Band EN-DC including FR2 with 8 NR UL CCs | E041 | | NOTE 1
NOTE 5
Skip TC
6.5B.2.4.3_1.7 if UE supports SA and TS 38.521-2 TC
6.5A.2.2.7 has been executed. | +| 6.5B.2.4D.3 | Adjacent channel leakage ratio for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.5B.3.1.1 | General spurious emissions for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | NOTE 5
Skip TC 6.5B.3.1.1 if | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|--------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | UE supports SA and TS 38.521-1 TC 6.5.3.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|------------|----------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------|---------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.3.1.2 | Spurious emission band UE co-existence for intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.5B.3.2.1 | General spurious emissions for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 5
Skip TC 6.5B.3.2.1 if UE supports SA and TS 38.521-1 TC 6.5.3.1 has been executed. | +| 6.5B.3.2.2 | Spurious emission band UE co-existence for intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | | +| 6.5B.3.3.1 | General spurious emissions for Inter-band EN-DC within FR1 | Rel-15 | C011 | UEs supporting Inter-band EN-DC within FR1 (2UL CCs) | E005 | | Test only one EN-DC combination per 5G NR band.
Skip LTE anchor agnostic approach testing in TC 6.5B.3.3.1 if UE supports SA and TS 38.521-1 TC 6.5.3.1 has been executed. | +| 6.5B.3.3.2 | Spurious emission band UE co-existence for Inter-band within FR1 | Rel-15 | C011 | UEs supporting Inter-band EN-DC within FR1 (2UL CCs) | E005 | | For LTE anchor agnostic approach testing in TC 6.5B.3.3.2:
1. NOTE 5 applied.
2. Skip the testing if UE supports SA and TS 38.521-1 TC 6.5.3.2 has been executed. | +| 6.5B.3.4.1 | General Spurious Emissions for Inter-band including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.5B.3.4.1 if UE supports SA and TS 38.521-2 TC 6.5.3.1 has been | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.3.4.1a | General Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | Rel-16 | C012w | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC and mpr-PowerBoost-FR2-r16 | E010 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.5B.3.4.1a if UE supports SA and TS 38.521-2 TC 6.5.3.1_1 has been executed. | +| 6.5B.3.4.1_1 | General Spurious emissions for Inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 6.5B.3.4.1_1.1 | General Spurious Emissions for Inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC 6.5B.3.4.1_1.1 if UE supports SA and TS 38.521-2 TC 6.5A.3.1.1 has been executed. | +| 6.5B.3.4.1_1.2 | General Spurious Emissions for Inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 5
Skip TC 6.5B.3.4.1_1.2 if UE supports SA and TS 38.521-2 TC 6.5A.3.1.2 has been executed. | +| 6.5B.3.4.1_1.3 | General Spurious Emissions for Inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 5
Skip TC 6.5B.3.4.1_1.3 if UE supports SA and TS 38.521-2 TC 6.5A.3.1.3 has been executed. | +| 6.5B.3.4.1_1.4 | General Spurious Emissions for Inter-band EN-DC including FR2 (5 NR CCs) | Rel-15 | C012i | UEs supporting Inter-Band EN-DC including FR2 with 5 NR UL CCs | E014a | | NOTE 5
Skip TC 6.5B.3.4.1_1.4 if UE supports SA and TS 38.521-2 TC 6.5A.3.1.4 has been | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|----------------|------------------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.3.4.1_1.5 | General Spurious Emissions for Inter-band EN-DC including FR2 (6 NR CCs) | Rel-15 | C012j | UEs supporting Inter-Band EN-DC including FR2 with 6 NR UL CCs | E039 | | NOTE 5
Skip TC
6.5B.3.4.1_1.5 if UE supports SA and TS 38.521-2 TC
6.5A.3.1.5 has been executed. | +| 6.5B.3.4.1_1.6 | General Spurious Emissions for Inter-band EN-DC including FR2 (7 NR CCs) | Rel-15 | C012k | UEs supporting Inter-Band EN-DC including FR2 with 7 NR UL CCs | E040 | | NOTE 5
Skip TC
6.5B.3.4.1_1.6 if UE supports SA and TS 38.521-2 TC
6.5A.3.1.6 has been executed. | +| 6.5B.3.4.1_1.7 | General Spurious Emissions for Inter-band EN-DC including FR2 (8 NR CCs) | Rel-15 | C012l | UEs supporting Inter-Band EN-DC including FR2 with 8 NR UL CCs | E041 | | NOTE 5
Skip TC
6.5B.3.4.1_1.7 if UE supports SA and TS 38.521-2 TC
6.5A.3.1.7 has been executed. | +| 6.5B.3.4.1D | General Spurious Emissions for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 6.5B.3.4.2 | Spurious emission band UE co-existence for Inter-band including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.5B.3.4.2 if UE supports SA and TS 38.521-2 TC
6.5.3.2 has been executed. | +| 6.5B.3.4.2a | Spurious emission band UE co-existence with Power Boost for Inter-band including FR2 (1 NR CC) | Rel-16 | C012w | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC and mpr-PowerBoost-FR2-r16 | E010 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.5B.3.4.2a if UE supports SA and TS 38.521-2 TC
6.5.3.2_1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|---------------------|------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.3.4.2_1 | Spurious emission band UE co-existence for Inter-band including FR2 (>1 NR CC) | | | | | | | +| 6.5B.3.4.2_1.1 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (2NR CCs) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | | NOTE 5
Skip TC
6.5B.3.4.2_1.1 if UE supports SA and TS 38.521-2 TC
6.5A.3.2.1 has been executed. | +| 6.5B.3.4.2_1.2 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (3NR CCs) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | | NOTE 5
Skip TC
6.5B.3.4.2_1.2 if UE supports SA and TS 38.521-2 TC
6.5A.3.2.2 has been executed. | +| 6.5B.3.4.2_1.3 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (4NR CCs) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | | NOTE 5
Skip TC
6.5B.3.4.2_1.3 if UE supports SA and TS 38.521-2 TC
6.5A.3.2.3 has been executed. | +| 6.5B.3.4.2_1.4 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (5 NR CCs) | Rel-15 | C012i | UEs supporting Inter-Band EN-DC including FR2 with 5 NR UL CCs | E014a | | NOTE 5
Skip TC
6.5B.3.4.2_1.4 if UE supports SA and TS 38.521-2 TC
6.5A.3.2.4 has been executed. | +| 6.5B.3.4.2_1.5 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (6 NR CCs) | Rel-15 | C012j | UEs supporting Inter-Band EN-DC including FR2 with 6 NR UL CCs | E039 | | NOTE 5
Skip TC
6.5B.3.4.2_1.5 if UE supports SA and TS 38.521-2 TC | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|-------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 6.5A.3.2.5 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|----------------|---------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.3.4.2_1.6 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (7 NR CCs) | Rel-15 | C012k | UEs supporting Inter-Band EN-DC including FR2 with 7 NR UL CCs | E040 | | NOTE 5
Skip TC 6.5B.3.4.2_1.6 if UE supports SA and TS 38.521-2 TC 6.5A.3.2.6 has been executed. | +| 6.5B.3.4.2_1.7 | Spurious emission band UE co-existence for Inter-band EN-DC including FR2 (8 NR CCs) | Rel-15 | C012l | UEs supporting Inter-Band EN-DC including FR2 with 8 NR UL CCs | E041 | | NOTE 5
Skip TC 6.5B.3.4.2_1.7 if UE supports SA and TS 38.521-2 TC 6.5A.3.2.7 has been executed. | +| 6.5B.4.1 | Additional Spurious Emissions for Intra-band contiguous EN-DC | Rel-15 | C009 | UEs supporting intra-band contiguous EN-DC (2UL CCs) | E003 | | | +| 6.5B.4.2 | Additional Spurious Emissions for Intra-band non-contiguous EN-DC | Rel-15 | C010 | UEs supporting intra-band non-contiguous EN-DC (2UL CCs) | E004 | | NOTE 1 | +| 6.5B.4.3 | Additional Spurious Emissions for Inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.4.3 if UE supports SA and TS 38.521-1 TC 6.5.3.3 has been executed. | +| 6.5B.4.4 | Additional Spurious Emissions for Inter-band including FR2 (1 NR CC) | Rel-15 | C012 | UEs supporting Inter-band including FR2 with 1 NR UL CC | E010 | | NOTE 5
Skip TC 6.5B.4.4 if UE supports SA and TS 38.521-2 TC 6.5.3.3 has been executed. | +| 6.5B.4.4a | Additional Spurious Emissions with Power Boost for Inter-band including FR2 (1 NR CC) | Rel-16 | C012w | UEs supporting inter-band EN-DC including FR2 with 1 NR UL CC and mpr-PowerBoost-FR2-r16 | E010 | PC1 (NOTE 1)
PC2 (NOTE 1)
PC3
PC4 (NOTE 1) | NOTE 5
Skip TC 6.5B.4.4a if UE supports SA and TS 38.521-2 TC 6.5.3.3_1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|---------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|--------|---------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.5B.4.4_1 | Additional Spurious Emissions for Inter-band including FR2 (>1 NR CC) | | | | | | | +| 6.5B.4.4_1.1 | Additional Spurious Emissions for Inter-band including FR2 (2 NR CC) | Rel-15 | C012b | UEs supporting Inter-Band EN-DC including FR2 with 2 NR UL CCs | E011 | PC1 | NOTE 5
Skip TC 6.5B.4.4_1.1 if UE supports SA and TS 38.521-2 TC 6.5A.3.3.1 has been executed. | +| 6.5B.4.4_1.2 | Additional Spurious Emissions for Inter-band including FR2 (3 NR CC) | Rel-15 | C012c | UEs supporting Inter-Band EN-DC including FR2 with 3 NR UL CCs | E012 | PC1 | NOTE 5
Skip TC 6.5B.4.4_1.2 if UE supports SA and TS 38.521-2 TC 6.5A.3.3.2 has been executed. | +| 6.5B.4.4_1.3 | Additional Spurious Emissions for Inter-band including FR2 (4 NR CC) | Rel-15 | C012d | UEs supporting Inter-Band EN-DC including FR2 with 4 NR UL CCs | E013 | PC1 | NOTE 5
Skip TC 6.5B.4.4_1.3 if UE supports SA and TS 38.521-2 TC 6.5A.3.3.3 has been executed. | +| 6.5B.5.3 | Transmit Intermodulation for Inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011b | UEs supporting Inter-band EN-DC within FR1 with 1 NR UL CC | E005b | | NOTE 5
Skip TC 6.5B.5.3 if UE supports SA and TS 38.521-1 TC 6.5.4 has been executed. | +| 6.6B.4 | Beam Correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP | Rel-15 | C011b | UEs supporting Inter-band EN-DC within FR2 with 1 NR UL CC and not beam correspondence without UL beam sweeping and release 16 and forward UEs that do not support SSB-based or CSI-RS based enhanced beam correspondence and do not support enhanced beam | E005b | | NOTE 1
NOTE 5
Skip TC 6.6B.4 if UE supports SA and TS 38.521-2 TC 6.6.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|-----------------------------------------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | correspondence without UL beam sweeping | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|----------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 6.6B.5 | Enhanced Beam correspondence for inter-band EN-DC including FR2 (1 NR CC) - EIRP | Rel-16 | C011b | UEs supporting Inter-band EN-DC within FR2 with 1 NR UL CC and support either CSI-RS or SSB based beam correspondence and do not support beam correspondence without UL beam sweeping | E005b | | NOTE 1
NOTE 5
Skip TC 6.6B.5 if UE supports SA and TS 38.521-2 TC 6.6.2 has been executed. | +| 7 | Receiver Characteristics | | | | | | | +| 7.3B | Reference sensitivity level for DC | | | | | | | +| 7.3B.2.1 | Reference sensitivity for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting intra-band contiguous EN-DC (2DL CCs) | E003a | | | +| 7.3B.2.2 | Reference sensitivity for Intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting intra-band non-contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.3B.2.2 if UE supports SA and TS 38.521-1 TC 7.3.2 has been executed. | +| 7.3B.2.3 | Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs) | Rel-15 | C011a | UEs supporting inter-band EN-DC within FR1 (2DL CCs) | E005a
E005d | PC2
PC3 | For LTE anchor agnostic approach testing in TC 7.3B.2.3:
1. NOTE 5 applied.
2. Skip the testing if UE supports SA and TS 38.521-1 TC 7.3.2 has been executed. | +| 7.3B.2.3_1 | Reference sensitivity for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.3B.2.3_1.1 | Reference sensitivity for EN-DC within FR1 (3 CCs) | Rel-15 | C045 | UEs supporting EN-DC within FR1 (3DL CCs) | E006 | | | +| 7.3B.2.3_1.2 | Reference sensitivity for EN-DC within FR1 (4 CCs) | Rel-15 | C046 | UEs supporting EN-DC within FR1 (4DL CCs) | E007 | | | +| 7.3B.2.3_1.3 | Reference sensitivity for EN-DC within FR1 (5 CCs) | Rel-15 | C047 | UEs supporting EN-DC within FR1 (5DL CCs) | E008 | | | +| 7.3B.2.4 | Reference sensitivity for Inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012a | UEs supporting inter-band EN-DC including FR2 with 1 NR DL CC | E010a | | NOTE 5
Skip TC 7.3B.2.4 if UE supports SA and TS | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|--------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 38.521-2 TC 7.3.2 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|-------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.3B.2.4_1 | Reference sensitivity for Inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 7.3B.2.4_1.1 | Reference sensitivity for Inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | C012e | UEs supporting inter-band EN-DC including FR2 with 2 NR DL CCs | E011a | | NOTE 5
Skip TC 7.3B.2.4_1.1 if UE supports SA and TS 38.521-2 TC 7.3A.2.1 has been executed. | +| 7.3B.2.4_1.2 | Reference sensitivity for Inter-band EN-DC including FR2 (3 NR CCs) | Rel-15 | C012g | UEs supporting inter-band EN-DC including FR2 with 3 NR DL CCs | E012a | | NOTE 5
Skip TC 7.3B.2.4_1.2 if UE supports SA and TS 38.521-2 TC 7.3A.2.2 has been executed. | +| 7.3B.2.4_1.3 | Reference sensitivity for Inter-band EN-DC including FR2 (4 NR CCs) | Rel-15 | C012h | UEs supporting inter-band EN-DC including FR2 with 4 NR DL CCs | E013a | | NOTE 5
Skip TC 7.3B.2.4_1.3 if UE supports SA and TS 38.521-2 TC 7.3A.2.3 has been executed. | +| 7.3B.2.4_1.4 | Reference sensitivity for Inter-band EN-DC including FR2 (5 NR CCs) | Rel-15 | FFS | UEs supporting inter-band EN-DC including FR2 with 5 NR DL CCs | FFS | | NOTE 1
NOTE 5
Skip TC 7.3B.2.4_1.4 if UE supports SA and TS 38.521-2 TC 7.3A.2.4 has been executed. | +| 7.3B.2.4_1.5 | Reference sensitivity for Inter-band EN-DC including FR2 (6 NR CCs) | Rel-15 | FFS | UEs supporting inter-band EN-DC including FR2 with 6 NR DL CCs | FFS | | NOTE 1
NOTE 5
Skip TC 7.3B.2.4_1.5 if UE supports SA and TS 38.521-2 TC 7.3A.2.5 has been executed. | +| 7.3B.2.4_1.6 | Reference sensitivity for Inter-band EN-DC including | Rel-15 | FFS | UEs supporting inter-band EN-DC | FFS | | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------------|---------|---------------|--------------------------------|---------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | FR2 (7 NR CCs) | | | including FR2 with 7 NR DL CCs | | | NOTE 5
Skip TC 7.3B.2.4_1.6
if UE supports SA and
TS 38.521-2 TC
7.3A.2.6 has been
executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-----------------|----------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.3B.2.4_1.7 | Reference sensitivity for Inter-band EN-DC including FR2 (8 NR CCs) | Rel-15 | FFS | UEs supporting inter-band EN-DC including FR2 with 8 NR DL CCs | FFS | | NOTE 1
NOTE 5
Skip TC 7.3B.2.4_1.7 if UE supports SA and TS 38.521-2 TC 7.3A.2.7 has been executed. | +| 7.3B.2.4D | Reference sensitivity for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.3B.4 | EIS Spherical Coverage for Inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012a | UEs supporting inter-band EN-DC including FR2 with 1 NR DL CC | E010a | | NOTE 5
Skip TC 7.3B.4 if UE supports SA and TS 38.521-2 TC 7.3.4 has been executed. | +| 7.4B | Maximum Input Level for DC | | | | | | | +| 7.4B.1 | Maximum Input Level for Intra-Band Contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | | +| 7.4B.2 | Maximum Input Level for Intra-Band Non-Contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band Non-Contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.4B.2 if UE supports SA and TS 38.521-1 TC 7.4 has been executed | +| 7.4B.3 | Maximum Input Level for Inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011c | UEs supporting Inter-band EN-DC within FR1 with 1 NR DL CC | E005c | | NOTE 5
Skip TC 7.4B.3 if UE supports SA and TS 38.521-1 TC 7.4 has been executed. | +| 7.4B.3_1 | Maximum Input Level for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.4B.3_1.1 | Maximum Input Level for EN-DC within FR1 (3 CCs) | Rel-15 | C045 | UEs supporting EN-DC within FR1 (3DL CCs) | E006 | | | +| 7.4B.3_1.2 | Maximum Input Level for EN-DC within FR1 (4 CCs) | Rel-15 | C046 | UEs supporting EN-DC within FR1 (4DL CCs) | E007 | | | +| 7.4B.3_1.3 | Maximum Input Level for EN-DC within FR1 (5 CCs) | Rel-15 | C047 | UEs supporting EN-DC within FR1 | E008 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|-----------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | | | | (5DL CCs) | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-----------------|-----------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------|---------------------------------------------|--------|------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.4B.3_1.4 | Maximum Input Level for EN-DC within FR1 (6 CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1 | +| 7.4B.4 | Maximum Input Level for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012a | UEs supporting Inter-band including FR2 with 1 NR DL CC | E010a | | NOTE 1
NOTE 5
Skip TC 7.4B.4 if UE supports SA and TS 38.521-2 TC 7.4 has been executed. | +| 7.4B.4_1 | Maximum Input Level for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 7.4B.4_1.1 | Maximum Input Level for inter-band EN-DC including FR2 (2 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.4B.4_1.2 | Maximum Input Level for inter-band EN-DC including FR2 (3 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.4B.4_1.3 | Maximum Input Level for inter-band EN-DC including FR2 (4 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.4B.4_1.4 | Maximum Input Level for inter-band EN-DC including FR2 (5 NR CCs) | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.4B.4D | Maximum Input Level for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.5B | Adjacent channel selectivity for DC | | | | | | | +| 7.5B.1 | Adjacent Channel Selectivity for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting intra-band contiguous EN-DC (2DL CCs) | E003a | | NOTE 1 | +| 7.5B.2 | Adjacent Channel Selectivity for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting intra-band non-contiguous EN-DC (2DL CCs) | E004a | | NOTE 1
NOTE 5
Skip TC 7.5B.2 if UE supports SA and TS 38.521-1 TC 7.5 has been executed. | +| 7.5B.3 | Adjacent Channel Selectivity for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011c | UEs supporting inter-band EN-DC within FR1 with 1 NR DL CCs and one or more LTE DL CC(s) | E005c | | NOTE 5
Skip TC 7.5B.3 if UE supports SA and TS 38.521-1 TC 7.5 has been executed. | +| 7.5B.3_1 | Adjacent Channel Selectivity for EN-DC within | | | | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|--------------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | FR1 (>2 CCs) | | | | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-----------------|--------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------|---------------------------------------------|--------|-------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.5B.3_1.1 | Adjacent Channel Selectivity for EN-DC within FR1 (2 NR CCs) | Rel-15 | C063 | UEs supporting inter-band or intra-band non-contiguous EN-DC within FR1 with 2 NR DL CCs | E027
E029 | | NOTE 5
Skip TC 7.5B.3_1.1 if UE supports SA and TS 38.521-1 TC 7.5A.1 has been executed. | +| 7.5B.3_1.2 | Adjacent Channel Selectivity for EN-DC within FR1 (3 NR CCs) | Rel-15 | C064 | UEs supporting inter-band or intra-band non-contiguous EN-DC within FR1 with 3 NR DL CCs | E028
E030 | | NOTE 5
Skip TC 7.5B.3_1.2 if UE supports SA and TS 38.521-1 TC 7.5A.2 has been executed. | +| 7.5B.3_1.3 | Adjacent Channel Selectivity for EN-DC within FR1 (4 NR CCs) | Rel-15 | C064a | UEs supporting intra-band non-contiguous EN-DC within FR1 with 4 NR DL CCs | E028a
E030a | | NOTE 5
Skip TC 7.5B.3_1.3 if UE supports SA and TS 38.521-1 TC 7.5A.3 has been executed. | +| 7.5B.3_1.4 | Adjacent Channel Selectivity for EN-DC within FR1 (5 NR CCs) | Rel-15 | C064b | UEs supporting intra-band non-contiguous EN-DC within FR1 with 5 NR DL CCs | E028b
E030b | | NOTE 1
NOTE 5
Skip TC 7.5B.3_1.4 if UE supports SA and TS 38.521-1 TC 7.5A.4 has been executed. | +| 7.5B.4 | Adjacent Channel Selectivity for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC 7.5B.4 if UE supports SA and TS 38.521-2 TC 7.5 has been executed. | +| 7.5B.4_1 | Adjacent Channel Selectivity for inter-band EN-DC including FR2 (>1 NR CC) | | | | | | | +| 7.5B.4_1.1 | Adjacent Channel Selectivity for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5 | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|-----------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | Skip TC 7.5B.4_1.1 if UE supports SA and TS 38.521-2 TC 7.5A.1 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|-----------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------|---------------------------------------------|--------|------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.5B.4_1.2 | Void | | | | | | | +| 7.5B.4_1.3 | Void | | | | | | | +| 7.5B.4_1.4 | Void | | | | | | | +| 7.5B.4D | Adjacent Channel Selectivity for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.6B | Blocking characteristics for DC | | | | | | | +| 7.6B.2.1 | Inband blocking for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | | +| 7.6B.2.2 | Inband blocking for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band Non-Contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.6B.2.2 if UE supports SA and TS 38.521-1 TC 7.6.2 has been executed. | +| 7.6B.2.3 | Inband blocking for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011c | UEs supporting Inter-band EN-DC within FR1 with 1 NR DL CC | E005c | | NOTE 5
Skip TC 7.6B.2.3 if UE supports SA and TS 38.521-1 TC 7.6.2 has been executed. | +| 7.6B.2.3_1 | Inband blocking for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.6B.2.3_1.1 | Inband blocking for EN-DC within FR1 (3 CCs) | Rel-15 | C045 | UEs supporting EN-DC within FR1 (3DL CCs) | E006 | | | +| 7.6B.2.3_1.2 | Inband blocking for EN-DC within FR1 (4 CCs) | Rel-16 | C046 | UEs supporting EN-DC within FR1 (4DL CCs) | E007 | | | +| 7.6B.2.3_1.3 | Inband blocking for EN-DC within FR1 (5 CCs) | Rel-16 | C047 | UEs supporting EN-DC within FR1 (5DL CCs) | E008 | | Skip TC 7.6B.2.3_1.3 if UE supports SA and TS 38.521-1 TC 7.6A.2.3 has been executed. | +| 7.6B.2.4 | Inband blocking for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012a | UEs supporting Inter-band EN-DC including FR2 with 1 NR DL CC | E010a | | NOTE 5
Skip TC 7.6B.2.4 if UE supports SA and TS 38.521-2 TC 7.6.2 has been executed. | +| 7.6B.2.4_1 | Inband blocking for inter-band EN-DC including | | | | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------------|---------|---------------|---------|---------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| | FR2 (>1 NR CC) | | | | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------|---------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.6B.2.4_1.1 | Inband blocking for inter-band EN-DC including FR2 (2 NR CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1
NOTE 5
Skip TC 7.6B.2.4_1.1 if UE supports SA and TS 38.521-2 TC 7.6A.2.1 has been executed. | +| 7.6B.2.4_1.2 | Void | | | | | | | +| 7.6B.2.4_1.3 | Void | | | | | | | +| 7.6B.2.4_1.4 | Void | | | | | | | +| 7.6B.2.4D | Inband blocking for inter-band EN-DC including FR2 for UL MIMO | FFS | FFS | FFS | FFS | | NOTE 1 | +| 7.6B.3.1 | Out-of-band blocking for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | | +| 7.6B.3.2 | Out-of-band blocking for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band Non-Contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.6B.3.2 if UE supports SA and TS 38.521-1 TC 7.6.3 has been executed. | +| 7.6B.3.3 | Out-of-band blocking for inter-band EN-DC within FR1 (2 CCs) | Rel-15 | C011a | UEs supporting Inter-band EN-DC within FR1 (2DL CCs) | E005a | | | +| 7.6B.3.3_1 | Out-of-band blocking for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.6B.3.3_1.1 | Out-of-band blocking for EN-DC within FR1 (3 CCs) | Rel-15 | C048 | UEs supporting intra-band contiguous EN-DC within FR1 with 3 DL CCs | E006 | | | +| 7.6B.3.3_1.2 | Out-of-band blocking for EN-DC within FR1 (4 CCs) | Rel-16 | C049 | UEs supporting intra-band contiguous EN-DC within FR1 with 4 DL CCs | E007 | | | +| 7.6B.4.1 | Narrow band blocking for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | | +| 7.6B.4.2 | Narrow band blocking for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band Non-Contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.6B.4.2 if UE supports SA and TS | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------|----------|---------|---------------|---------|---------------------------------------------|--------|--------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | 38.521-1 TC 7.6.4 has been executed. | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|----------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------|---------------------------------------------|--------|------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.6B.4.3 | Narrow band blocking for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011c | UEs supporting Inter-band EN-DC within FR1 with 1 NR DL CC | E005c | | NOTE 5
Skip TC 7.6B.4.3 if UE supports SA and TS 38.521-1 TC 7.6.4 has been executed. | +| 7.6B.4.3_1 | Narrow band blocking for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.6B.4.3_1.1 | Narrow band blocking for EN-DC within FR1 (3 CCs) | Rel-15 | C045 | UEs supporting EN-DC within FR1 (3DL CCs) | E006 | | | +| 7.6B.4.3_1.2 | Narrow band blocking for EN-DC within FR1 (4 CCs) | Rel-16 | C046 | UEs supporting EN-DC within FR1 (4DL CCs) | E007 | | | +| 7.6B.4.3_1.3 | Narrow band blocking for EN-DC within FR1 (5 CCs) | Rel-16 | C047 | UEs supporting EN-DC within FR1 (5DL CCs) | E008 | | Skip TC 7.6B.4.3_1.3 if UE supports SA and TS 38.521-1 TC 7.6A.4.3 has been executed. | +| 7.7B | Spurious response for DC | | | | | | | +| 7.7B.1 | Spurious Response for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | | +| 7.7B.2 | Spurious Response for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band Non-Contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.7B.2 if UE supports SA and TS 38.521-1 TC 7.7 has been executed. | +| 7.7B.3 | Spurious Response for inter-band EN-DC within FR1 (2 CCs) | Rel-15 | C011a | UEs supporting Inter-band EN-DC within FR1 (2DL CCs) | E005a | | | +| 7.7B.3_1 | Spurious Response for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.7B.3_1.1 | Spurious Response for EN-DC within FR1 (3 CCs) | Rel-15 | C048 | UEs supporting intra-band contiguous EN-DC within FR1 with 3 DL CCs | E006 | | | +| 7.7B.3_1.2 | Spurious Response for EN-DC within FR1 (4 CCs) | Rel-16 | C049 | UEs supporting intra-band contiguous EN-DC within FR1 with 4 DL CCs | E007 | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|-------------------|----------------------------------------------------------------------|---------|---------------|------------------------------------------------------------|---------------------------------------------|--------|------------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| 7.8B | Intermodulation characteristics for DC | | | | | | | +| 7.8B.2.1 | Wideband Intermodulation for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | NOTE 1 | +| 7.8B.2.2 | Wideband Intermodulation for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band non-contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.8B.2.2 if UE supports SA and TS 38.521-1 TC 7.8.2 has been executed. | +| 7.8B.2.3 | Wideband Intermodulation for inter-band EN-DC within FR1 (2 CCs) | Rel-15 | C011a | UEs supporting inter-band EN-DC within FR1 (2DL CCs) | E005c | | NOTE 5
Skip TC 7.8B.2.3 if UE supports SA and TS 38.521-1 TC 7.8.2 has been executed. | +| 7.8B.2.3_1 | Wideband Intermodulation for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.8B.2.3_1.1 | Wideband Intermodulation for EN-DC within FR1 (3 CCs) | Rel-15 | C045 | UEs supporting EN-DC within FR1 (3DL CCs) | E006 | | | +| 7.8B.2.3_1.2 | Wideband Intermodulation for EN-DC within FR1 (4 CCs) | Rel-15 | C046 | UEs supporting EN-DC within FR1 (4DL CCs) | E007 | | | +| 7.8B.2.3_1.3 | Wideband Intermodulation for EN-DC within FR1 (5 CCs) | Rel-15 | FFS | FFS | FFS | | NOTE 1 | +| 7.9B | Spurious emissions for DC | | | | | | | +| 7.9B.1 | Spurious Emissions for intra-band contiguous EN-DC (2 CCs) | Rel-15 | C009a | UEs supporting Intra-Band Contiguous EN-DC (2DL CCs) | E003a | | NOTE 5
Skip TC 7.9B.1 if UE supports SA and TS 38.521-1 TC 7.9 has been executed. | +| 7.9B.2 | Spurious Emissions for intra-band non-contiguous EN-DC (2 CCs) | Rel-15 | C010a | UEs supporting Intra-Band non-contiguous EN-DC (2DL CCs) | E004a | | NOTE 5
Skip TC 7.9B.2 if UE supports SA and TS 38.521-1 TC 7.9 has been executed. | +| 7.9B.3 | Spurious Emissions for inter-band EN-DC within FR1 (1 NR CC) | Rel-15 | C011c | UEs supporting inter-band EN-DC within FR1 with 1 NR DL CC | E005c | | NOTE 5
Skip TC 7.9B.3 if UE | + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA/DC-Configurations Selection | Branch | Additional Information | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------|---------------------------------------------|--------|-------------------------------------------------------------------------------------| +| | | | Condition | Comment | | | | +| | | | | | | | supports SA and TS 38.521-1 TC 7.9 has been executed. | +| 7.9B.3_1 | Spurious Emissions for EN-DC within FR1 (>2 CCs) | | | | | | | +| 7.9B.3_1.1 | Spurious Emissions for EN-DC within FR1 (3 CCs) | Rel-15 | C048 | UEs supporting EN-DC within FR1 with 1 LTE DL CC and 2 inter-band NR DL CCs with DL-only NR band | E006 | | | +| 7.9B.4 | Spurious Emissions for inter-band EN-DC including FR2 (1 NR CC) | Rel-15 | C012a | UEs supporting Inter-band including FR2 with 1 NR DL CC | E010a | | NOTE5
Skip TC 7.9B.4 if UE supports SA and TS 38.521-2 TC 7.9 has been executed. | +| NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.521-3. | | | | | | | | +| NOTE 2: Void. | | | | | | | | +| NOTE 3: Void. | | | | | | | | +| NOTE 4: Void. | | | | | | | | +| NOTE 5: Test only one EN-DC combination per 5G NR band as LTE anchor agnostic approach is applied. | | | | | | | | + +Table 4.1.3-1a: Void + +Table 4.1.3-1b: Void + +Table 4.1.3-1c: Void + +### 4.1.4 Performance conformance test cases + +**Table 4.1.4-1: Applicability of performance test cases, ref. TS 38.521-4 [4]** + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5 | Demodulation performance requirements (Conducted requirements) | | | | | | +| 5.2 | PDSCH demodulation requirements | | | | | | +| 5.2.1.1.1 | 1Rx FDD FR1 PDSCH performance for RedCap | Rel-17 | C177a | RedCap UEs supporting 5GS FDD FR1 and 1Rx UE capability | D008 | NOTE 1 | +| 5.2.1.2.1 | 1Rx TDD FR1 PDSCH performance for RedCap | Rel-17 | C177c | RedCap UEs supporting 5GS TDD FR1 and 1Rx UE capability | D009 | | +| 5.2.2.1.1_1 | 2Rx FDD FR1 PDSCH mapping Type A performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.1_2 | 2Rx FDD FR1 PDSCH mapping Type A performance - 2x2 MIMO with enhanced receiver type 1 for both SA and NSA | Rel-15 | C015x | UEs supporting 5GS FDD FR1 and Enhanced Receiver Type 1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.1_3 | 2Rx FDD FR1 PDSCH mapping Type A performance - 2x2 MIMO with baseline receiver for DL1024QAM for both SA and NSA | Rel-17 | C200 | UEs supporting 5GS FDD FR1 and DL1024Qam but not supporting FDD bands with 4Rx UE capability | D008 | NOTE 1 | +| 5.2.2.1.2_1 | 2Rx FDD FR1 PDSCH mapping Type A and CSI-RS overlapped with PDSCH performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.3_1 | 2Rx FDD FR1 PDSCH mapping Type B performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C015b | UEs supporting 5GS FDD FR1 and PDSCH mapping Type B but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.4_1 | 2Rx FDD FR1 PDSCH Mapping Type A and LTE-NR coexistence performance - 4x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C015y | UEs supporting 5GS FDD FR1 and additional DMRS for coexistence with LTE CRS but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.5_1 | 2Rx FDD FR1 PDSCH 0.001% BLER performance - 1x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C074 | UEs supporting 5GS FDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ , but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.6_1 | 2Rx FDD FR1 PDSCH repetitions over multiple slots performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C120 | UEs supporting 5GS FDD FR1 and aggregationFactorDL > 1 for PDSCH repetition multislots and alternative | D008 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|----------|---------|---------------|-------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | | | | 64QAM MCS table for PDSCH but not supporting FDD bands with 4Rx UE capability | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------------------------------------------| +| | | | Condition | Comment | | | +| 5.2.2.1.7_1 | 2Rx FDD FR1 PDSCH Mapping Type B and UE processing capability 2 performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C116 | UEs supporting 5GS FDD FR1 and PDSCH processing capability 2 and PDSCH mapping type B, but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.8_1 | 2Rx FDD FR1 PDSCH pre-emption performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C121 | UEs supporting 5GS FDD FR1 and PDSCH pre-emption indication but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.9_1 | 2Rx FDD FR1 HST-SFN performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C099 | UEs supporting 5GS FDD FR1 and enhanced demodulation processing for HST-SFN joint transmission scheme but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.10_1 | 2Rx FDD FR1 HST-DPS performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C152 | UEs supporting 5GS FDD FR1 and number of active TCI states per BWP per CC but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.11_1 | 2Rx FDD FR1 PDSCH Single-DCI based SDM scheme performance - 2x2 MIMO for both SA and NSA | Rel-16 | C070 | UEs supporting 5GS FDD FR1 and single DCI based spatial division multiplexing scheme, but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.12_1 | 2Rx FDD FR1 PDSCH Multiple-DCI based transmission scheme performance - 2x2 MIMO for both SA and NSA | Rel-16 | C113 | UEs supporting 5GS FDD FR1 and multi-DCI based multi-TRP, but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.13_1 | 2Rx FDD FR1 PDSCH Single-DCI based FDM scheme A performance - 2x2 MIMO for both SA and NSA | Rel-16 | C114 | UEs supporting 5GS FDD FR1 and single DCI based FDMSchemeA, but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.14_1 | 2Rx FDD FR1 PDSCH Single-DCI based Inter-slot TDM scheme performance - 2x2 MIMO for both SA and NSA | Rel-16 | C115 | UEs supporting 5GS FDD FR1 and single-DCI based inter-slot TDM, but not supporting FDD bands with 4Rx UE capability | D008 | Test execution not necessary if 5.2.2.1.6_1 is executed. | +| 5.2.2.1.15_1 | 2Rx FDD FR1 PDSCH with inter-cell interference - 2x2 MIMO for both SA and NSA | Rel-15 | C015d | UEs supporting 5GS FDD FR1 and MMSE-IRC receiver but not | D008 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|----------|---------|---------------|---------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | | | | supporting FDD bands with 4Rx UE capability | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------| +| | | | Condition | Comment | | | +| 5.2.2.1.16_1 | 2Rx FDD FR1 for PDSCH with intra cell inter user interference performance – 2x2 MIMO for both NSA and SA | Rel-15 | C015d | UEs supporting 5GS FDD FR1 and MMSE-IRC receiver but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.2.2.1.17 | 2Rx FDD FR1 PDSCH performance for RedCap | Rel-17 | C177b | RedCap UEs supporting 5GS FDD FR1 and 2Rx UE capability | D008 | NOTE 1 | +| 5.2.2.1.20 | 2Rx FDD FR1 PDSCH HST-SFN Scheme A performance - 2x2 MIMO for both SA and NSA | Rel-17 | C245 | UEs supporting 5GS FDD FR1 and SFN scheme A for PDCCH scheduling SFN Scheme A PDSCH, but not supporting FDD bands with 4Rx UE capability | D008 | NOTE 1 | +| 5.2.2.1.21 | 2Rx FDD FR1 PDSCH HST-SFN Scheme B performance - 2x2 MIMO for both SA and NSA | Rel-17 | C246 | UEs supporting 5GS FDD FR1 and SFN scheme B for PDCCH scheduling SFN Scheme B PDSCH, but not supporting FDD bands with 4Rx UE capability | D008 | NOTE 1
Test execution is not necessary if TC 5.2.2.1.20 is executed. | +| 5.2.2.2.1_1 | 2Rx TDD FR1 PDSCH mapping Type A performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D009
D010 | | +| 5.2.2.2.1_2 | 2Rx TDD FR1 PDSCH mapping Type A performance - 2x2 MIMO with enhanced receiver type 1 for both SA and NSA | Rel-15 | C016x | UEs supporting 5GS TDD FR1 and Enhanced Receiver Type 1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.1_3 | 2Rx TDD FR1 PDSCH mapping Type A performance - 2x2 MIMO with baseline receiver for DL1024QAM for both SA and NSA | Rel-17 | C201 | UEs supporting 5GS TDD FR1 and DL 1024QAM | D010 | NOTE 1 | +| 5.2.2.2.2_1 | 2Rx TDD FR1 PDSCH mapping Type A and CSI-RS overlapped with PDSCH performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.3_1 | 2Rx TDD FR1 PDSCH mapping Type B performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C016b | UEs supporting 5GS TDD FR1 and PDSCH mapping Type B but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.4_1 | 2Rx TDD FR1 PDSCH Mapping Type A and LTE-NR coexistence performance - 4x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C016y | UEs supporting 5GS TDD FR1 and additional DMRS for coexistence with LTE CRS but not supporting TDD | D019 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|----------|---------|---------------|------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | | | | bands with 4Rx UE capability | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5.2.2.2.5_1 | 2Rx TDD FR1 PDSCH 0.001% BLER performance - 1x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C075 | UEs supporting 5GS TDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ , but not supporting TDD bands with 4Rx UE capability | D009 | | +| 5.2.2.2.6_1 | 2Rx TDD FR1 PDSCH repetitions over multiple slots performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C122 | UEs supporting 5GS TDD FR1 and aggregationFactorDL > 1 for PDSCH repetition multislots and alternative 64QAM MCS table for PDSCH but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.7_1 | 2Rx TDD FR1 PDSCH Mapping Type B and UE processing capability 2 performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C117 | UEs supporting 5GS TDD FR1 and PDSCH processing capability 2 and PDSCH mapping type B, but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.8_1 | 2Rx TDD FR1 PDSCH pre-emption performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-16 | C123 | UEs supporting 5GS TDD FR1 and PDSCH pre-emption indication but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.9_1 | 2Rx TDD FR1 HST-SFN performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.10_1 | 2Rx TDD FR1 HST-DPS performance - 2x2 MIMO with baseline receiver for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.11_1 | 2Rx TDD FR1 PDSCH Single-DCI based SDM scheme performance - 2x2 MIMO for both SA and NSA | Rel-16 | C071 | UEs supporting 5GS TDD FR1 and single DCI based spatial division multiplexing scheme, but not supporting TDD bands with 4Rx UE capability | D009 | | +| 5.2.2.2.12_1 | 2Rx TDD FR1 PDSCH Multiple-DCI based transmission scheme performance - 2x2 MIMO for both SA and NSA | Rel-16 | C113a | UEs supporting 5GS TDD FR1 and multi-DCI based multi-TRP, but not supporting TDD bands with 4Rx UE capability | D009 | | +| 5.2.2.2.13_1 | 2Rx TDD FR1 PDSCH Single-DCI based FDM scheme A performance - 2x2 MIMO for both SA and | Rel-16 | C114a | UEs supporting 5GS TDD FR1 and single DCI based FDMSchemeA, but | D009 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|----------|---------|---------------|-------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | NSA | | | not supporting TDD bands with 4Rx UE capability | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------| +| | | | Condition | Comment | | | +| 5.2.2.2.14_1 | 2Rx TDD FR1 PDSCH Single-DCI based Inter-slot TDM scheme performance - 2x2 MIMO for both SA and NSA | Rel-16 | C115a | UEs supporting 5GS TDD FR1 and single-DCI based inter-slot TDM, but not supporting TDD bands with 4Rx UE capability | D009 | Test execution not necessary if 5.2.2.2.6_1 is executed. | +| 5.2.2.2.15 | 2Rx TDD FR1 PDSCH mapping type A performance on band with shared spectrum access | Rel-16 | C204 | UEs supporting 5GS TDD FR1 and NR-U | D025 | NOTE 1 | +| 5.2.2.2.16_1 | 2Rx TDD FR1 for PDSCH with inter-cell interference performance – 2x2 MIMO for both NSA and SA | Rel-15 | C016d | UEs supporting 5GS TDD FR1 and MMSE-IRC receiver but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.17_1 | 2Rx TDD FR1 for PDSCH with intra cell inter user interference performance – 2x2 MIMO for both NSA and SA | Rel-15 | C016d | UEs supporting 5GS TDD FR1 and MMSE-IRC receiver but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.2.2.2.18 | 2Rx TDD FR1 PDSCH performance for RedCap | Rel-17 | C177b | RedCap UEs supporting 5GS TDD FR1 and 2Rx UE capability | D009 | NOTE 1 | +| 5.2.2.2.21 | 2Rx TDD FR1 PDSCH HST-SFN Scheme A performance - 2x2 MIMO for both SA and NSA | Rel-17 | C247 | UEs supporting 5GS TDD FR1 and SFN scheme A for PDCCH scheduling SFN Scheme A PDSCH, but not supporting TDD bands with 4Rx UE capability | D010 | NOTE 1 | +| 5.2.2.2.22 | 2Rx TDD FR1 PDSCH HST-SFN Scheme B performance - 2x2 MIMO for both SA and NSA | Rel-17 | C248 | UEs supporting 5GS TDD FR1 and SFN scheme B for PDCCH scheduling SFN Scheme B PDSCH, but not supporting TDD bands with 4Rx UE capability | D010 | NOTE 1
Test execution is not necessary if TC 5.2.2.2.21 is executed. | +| 5.2.3.1.1_1 | 4Rx FDD FR1 PDSCH mapping Type A performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 5.2.3.1.1_2 | 4Rx FDD FR1 PDSCH mapping Type A performance - 4x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 5.2.3.1.1_4 | 4Rx FDD FR1 PDSCH mapping Type A performance - 4x4 MIMO with enhanced receiver type 1 for both SA and NSA | Rel-15 | C017x | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and Enhanced Receiver Type 1 | D008 | | +| 5.2.3.1.1_5 | 4Rx FDD FR1 PDSCH mapping Type A performance - 2x4 MIMO with baseline receiver for DL1024QAM for both SA and NSA | Rel-17 | C202 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and DL1024QAM | D008 | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5.2.3.1.2_1 | 4Rx FDD FR1 PDSCH mapping Type A and CSI-RS overlapped with PDSCH performance - 4x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 5.2.3.1.3_1 | 4Rx FDD FR1 PDSCH mapping Type B performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C017b | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and PDSCH mapping Type B | D008
D011 | | +| 5.2.3.1.4_1 | 4Rx FDD FR1 PDSCH Mapping Type A and LTE-NR coexistence performance - 4x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C017y | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and LTE-NR coexistence | D008 | | +| 5.2.3.1.5_1 | 4Rx FDD FR1 PDSCH 0.001% BLER performance - 1x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C076 | UEs supporting 5GS FDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ and 4Rx antenna ports | D008 | | +| 5.2.3.1.6_1 | 4Rx FDD FR1 PDSCH repetitions over multiple slots performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C124 | UEs supporting 5GS FDD FR1 and aggregationFactorDL > 1 for PDSCH repetition multislots and alternative 64QAM MCS table for PDSCH and 4Rx antenna ports | D008 | | +| 5.2.3.1.7_1 | 4Rx FDD FR1 PDSCH Mapping Type B and UE processing capability 2 performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C118 | UEs supporting 5GS FDD FR1 and PDSCH processing capability 2 and PDSCH mapping type B and 4Rx antenna ports | D008 | | +| 5.2.3.1.8_1 | 4Rx FDD FR1 PDSCH pre-emption performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C169 | UEs supporting 5GS FDD FR1 and PDSCH pre-emption indication and 4Rx antenna ports | D008 | | +| 5.2.3.1.9_1 | 4Rx FDD FR1 HST-SFN performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C127 | UEs supporting 5GS FDD FR1 and enhanced demodulation processing for HST-SFN joint transmission scheme and 4Rx antenna ports | D008 | | +| 5.2.3.1.10_1 | 4Rx FDD FR1 HST-DPS performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C154 | UEs supporting 5GS FDD FR1 and number of active TCI states per BWP per CC and 4Rx antenna ports | D008 | | +| 5.2.3.1.11_1 | 4Rx FDD FR1 PDSCH Single-DCI based SDM scheme performance - 2x4 MIMO for both SA and NSA | Rel-16 | C072 | UEs supporting 5GS FDD FR1 and single DCI based spatial division multiplexing scheme and 4Rx antenna ports | D008 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------| +| | | | Condition | Comment | | | +| 5.2.3.1.12_1 | 4Rx FDD FR1 PDSCH Multiple-DCI based transmission scheme performance - 2x4 MIMO for both SA and NSA | Rel-16 | C113b | UEs supporting 5GS FDD FR1 and multi-DCI based multi-TRP and 4Rx antenna ports | D008 | | +| 5.2.3.1.13_1 | 4Rx FDD FR1 PDSCH Single-DCI based FDM scheme A performance - 2x4 MIMO for both SA and NSA | Rel-16 | C114b | UEs supporting 5GS FDD FR1 and single DCI based FDMSchemeA and 4Rx antenna ports | D008 | | +| 5.2.3.1.14_1 | 4Rx FDD FR1 PDSCH Single-DCI based Inter-slot TDM scheme performance - 2x4 MIMO for both SA and NSA | Rel-16 | C115b | UEs supporting 5GS FDD FR1 and single-DCI based inter-slot TDM and 4Rx antenna ports | D008 | Test execution not necessary if 5.2.3.1.6_1 is executed. | +| 5.2.3.1.15_1 | 4Rx FDD FR1 PDSCH with inter-cell interference - 2x4 MIMO for both SA and NSA | Rel-15 | C017d | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and MMSE-IRC receiver | D008 | | +| 5.2.3.1.16_1 | 4Rx FDD FR1 for PDSCH with intra cell inter user interference performance – 2x4 and 4x4 MIMO for both NSA and SA | Rel-15 | C017d | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and MMSE-IRC receiver | D008 | | +| 5.2.3.1.19 | 4Rx FDD FR1 PDSCH HST-SFN Scheme A performance - 2x4 MIMO for both SA and NSA | Rel-17 | C249 | UEs supporting 5GS FDD FR1 and SFN scheme A for PDCCH scheduling SFN Scheme A PDSCH, and 4Rx antenna ports | D008 | NOTE 1 | +| 5.2.3.1.20 | 4Rx FDD FR1 PDSCH HST-SFN Scheme B performance - 2x4 MIMO for both SA and NSA | Rel-17 | C250 | UEs supporting 5GS FDD FR1 and SFN scheme B for PDCCH scheduling SFN Scheme B PDSCH, and 4Rx antenna ports | D008 | NOTE 1
Test execution is not necessary if TC 5.2.3.1.19 is executed. | +| 5.2.3.2.1_1 | 4Rx TDD FR1 PDSCH mapping Type A performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D009
D010 | | +| 5.2.3.2.1_2 | 4Rx TDD FR1 PDSCH mapping Type A performance - 4x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 5.2.3.2.1_4 | 4Rx TDD FR1 PDSCH mapping Type A performance - 4x4 MIMO with enhanced receiver type 1 for both SA and NSA | Rel-15 | C019x | UEs supporting 5GS TDD FR1 and Enhanced Receiver Type 1 and 4Rx antenna ports | D010 | | +| 5.2.3.2.1_5 | 4Rx TDD FR1 PDSCH mapping Type A performance - 2x4 MIMO with baseline receiver for DL1024QAM for both SA and NSA | Rel-17 | C203 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and DL 1024QAM | D010 | NOTE 1 | +| 5.2.3.2.2_1 | 4Rx TDD FR1 PDSCH mapping Type A and CSI-RS overlapped with PDSCH performance - 2x4 MIMO with | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D009
D010 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|---------------------------------------|---------|---------------|---------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | baseline receiver for both SA and NSA | | | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5.2.3.2.3_1 | 4Rx TDD FR1 PDSCH mapping Type B performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C019b | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and PDSCH mapping Type B | D009
D011 | | +| 5.2.3.2.4_1 | 4Rx TDD FR1 PDSCH Mapping Type A and LTE-NR coexistence performance - 4x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C017z | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and LTE-NR coexistence | D009 | | +| 5.2.3.2.5_1 | 4Rx TDD FR1 PDSCH 0.001% BLER performance - 1x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C077 | UEs supporting 5GS TDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ and 4Rx antenna ports | D009 | | +| 5.2.3.2.6_1 | 4Rx TDD FR1 PDSCH repetitions over multiple slots performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C125 | UEs supporting 5GS TDD FR1 and aggregationFactorDL > 1 for PDSCH repetition multislots and alternative 64QAM MCS table for PDSCH and 4Rx antenna ports | D010 | | +| 5.2.3.2.7_1 | 4Rx TDD FR1 PDSCH Mapping Type B and UE processing capability 2 performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C119 | UEs supporting 5GS TDD FR1 and PDSCH processing capability 2 and PDSCH mapping type B and 4Rx antenna ports | D010 | | +| 5.2.3.2.8_1 | 4Rx TDD FR1 PDSCH pre-emption performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-16 | C170 | UEs supporting 5GS TDD FR1 and PDSCH pre-emption indication and 4Rx antenna ports | D010 | | +| 5.2.3.2.9_1 | 4Rx TDD FR1 HST-SFN performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C019y | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and enhanced demodulation processing for HST-SFN joint transmission scheme | D010
D011 | | +| 5.2.3.2.10_1 | 4Rx TDD FR1 HST DPS performance - 2x4 MIMO with baseline receiver for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010
D011 | NOTE 1 | +| 5.2.3.2.11_1 | 4Rx TDD FR1 PDSCH Single-DCI based SDM scheme performance - 2x4 MIMO for both SA and NSA | Rel-16 | C073 | UEs supporting 5GS TDD FR1 and single DCI based spatial division multiplexing scheme and 4Rx antenna ports | D009 | | +| 5.2.3.2.12_1 | 4Rx TDD FR1 PDSCH Multiple-DCI based transmission scheme performance - 2x4 MIMO for both SA and NSA | Rel-16 | C113c | UEs supporting 5GS TDD FR1 and multi-DCI based multi-TRP and 4Rx antenna ports | D009 | | +| 5.2.3.2.13_1 | 4Rx TDD FR1 PDSCH Single-DCI based FDM | Rel-16 | C114c | UEs supporting 5GS TDD FR1 and | D009 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|-----------------------------------------------------|---------|---------------|---------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | scheme A performance - 2x4 MIMO for both SA and NSA | | | single DCI based FDMSchemeA and 4Rx antenna ports | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------|----------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------| +| | | | Condition | Comment | | | +| 5.2.3.2.14_1 | 4Rx TDD FR1 PDSCH Single-DCI based Inter-slot TDM scheme performance - 2x4 MIMO for both SA and NSA | Rel-16 | C115c | UEs supporting 5GS TDD FR1 and single-DCI based inter-slot TDM and 4Rx antenna ports | D009 | Test execution not necessary if 5.2.3.2.6_1 is executed. | +| 5.2.3.2.15 | 4Rx TDD FR1 PDSCH mapping type A performance on band with shared spectrum access | Rel-16 | C205 | UEs supporting 5GS FDD FR1 and NR-U | D025 | NOTE 1 | +| 5.2.3.2.16_1 | 4Rx TDD FR1 for PDSCH with inter-cell interference performance – 2x4 MIMO for both NSA and SA | Rel-15 | C019d | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and MMSE-IRC receiver | D010 | | +| 5.2.3.2.17_1 | 4Rx TDD FR1 for PDSCH with intra cell inter user interference performance – 2x4 MIMO for both NSA and SA | Rel-15 | C019d | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and MMSE-IRC receiver | D010 | | +| 5.2.3.2.20 | 4Rx TDD FR1 PDSCH HST-SFN Scheme A performance - 2x4 MIMO for both SA and NSA | Rel-17 | C251 | UEs supporting 5GS TDD FR1 and SFN scheme A for PDCCH scheduling SFN Scheme A PDSCH, and 4Rx antenna ports | D010 | NOTE 1 | +| 5.2.3.2.21 | 4Rx TDD FR1 PDSCH HST-SFN Scheme B performance - 2x4 MIMO for both SA and NSA | Rel-17 | C252 | UEs supporting 5GS TDD FR1 and SFN scheme B for PDCCH scheduling SFN Scheme B PDSCH, and 4Rx antenna ports | D010 | NOTE 1
Test execution is not necessary if TC 5.2.3.2.20 is executed. | +| 5.2A.2.1.1 | 2Rx Normal PDSCH Demodulation Performance for CA (2DL CA) for both SA and NSA | Rel-15 | C261 | UEs supporting 5GS FR1 AND 2DL CA but not supporting 4Rx UE capability on any CCs | E016 | | +| 5.2A.2.1.2 | 2Rx Normal PDSCH Demodulation Performance for CA (3DL CA) for both SA and NSA | Rel-15 | C262 | UEs supporting 5GS FR1 AND 3DL CA but not supporting 4Rx UE capability on any CCs | E017 | | +| 5.2A.2.1.3 | 2Rx Normal PDSCH Demodulation Performance for CA (4DL CA) for both SA and NSA | Rel-15 | C263 | UEs supporting 5GS FR1 AND 4DL CA but not supporting 4Rx UE capability on any CCs | E018 | | +| 5.2A.2.2.1 | 2Rx PDSCH Demodulation Performance for CA with power imbalance (2DL CA) | Rel-15 | C261 | UEs supporting 5GS FR1 AND 2DL CA but not supporting 4Rx UE capability on any CCs | E003a | | +| 5.2A.2.2.2 | 2Rx PDSCH Demodulation Performance for CA with power imbalance (3DL CA) | Rel-15 | FFS | UEs supporting 5GS FR1 AND 3DL CA but not supporting 4Rx UE capability on any CCs | E033 | NOTE 1 | +| 5.2A.2.2.3 | 2Rx PDSCH Demodulation Performance for CA with | Rel-15 | FFS | UEs supporting 5GS FR1 and 4D | E034 | NOTE 1 | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|--------------------------|---------|---------------|------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | power imbalance (4DL CA) | | | LCA but not supporting 4Rx UE capability on any 4CCs | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|-------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5.2A.2.3 | 2Rx TDD FR1 PDSCH mapping type A performance of Scell on band with shared spectrum access | Rel-16 | C204 | UEs supporting 5GS TDD FR1 and NR-U | D025 | NOTE 1 | +| 5.2A.2.4.1 | 2RX PDSCH Demodulation Performance for HST-SFN CA | Rel-16 | C152b | UEs supporting 5GS FR1 AND enhanced demodulation processing for carrier aggregation for HST-SFN joint transmission but not supporting 4Rx UE capability on any CCs | E016 | | +| 5.2A.2.5.1 | 2RX PDSCH Demodulation Performance for HST-DPS CA | Rel-15 | C152a | UEs supporting 5GS FR1 AND 2DL CA AND number of active TCI | E016 | | +| 5.2A.3.1.1 | 4Rx Normal PDSCH Demodulation Performance for CA (2DL CA) | Rel-15 | C017g | UEs supporting 5GS FR1 AND 2DL CA AND supporting 4Rx antenna ports on all CCs | E016 | | +| 5.2A.3.1.2 | 4Rx Normal PDSCH Demodulation Performance for CA (3DL CA) | Rel-15 | C017h | UEs supporting 5GS FR1 AND 3DL CA AND supporting 4Rx antenna ports on all CCs | E017 | | +| 5.2A.3.1.3 | 4Rx Normal PDSCH Demodulation Performance for CA (4DL CA) | Rel-15 | C017i | UEs supporting 5GS FR1 AND 4DL CA AND supporting 4Rx antenna ports on all CCs | E018 | | +| 5.2A.3.2.1 | 4Rx PDSCH Demodulation Performance for CA with power imbalance (2DL CA) | Rel-15 | C017g | UEs supporting 5GS FR1 AND 2DL CA AND supporting 4Rx antenna ports on all CCs | E003a | | +| 5.2A.3.3 | 4Rx TDD FR1 PDSCH mapping type A performance of Scell on band with shared spectrum access | Rel-16 | C2054 | UEs supporting 5GS TDD FR1 and NR-U | D025 | NOTE 1 | +| 5.2A.3.4.1 | 4RX PDSCH Demodulation Performance for HST-SFN CA | Rel-16 | C127a | UEs supporting 5GS FR1 AND enhanced demodulation processing for carrier aggregation for HST-SFN joint transmission AND supporting 4Rx TDD and FDD UE capability on any CCs | E016 | | +| 5.2A.3.5.1 | 4RX PDSCH Demodulation Performance for HST-DPS CA | Rel-15 | C154a | UEs supporting 5GS FR1 AND 2DL CA AND number of active TCI AND supporting 4Rx TDD and FDD UE capability on any CCs | E016 | | +| 5.2A.3A.1.1 | 2Rx-4Rx Normal PDSCH Demodulation Performance for CA (2DL CA) | Rel-15 | C017g | UEs supporting 5GS FR1 and 2DL CA AND supporting 4Rx UE capability on some of the CCs | E016 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|----------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5.2A.3A.1.2 | 2Rx-4Rx Normal PDSCH Demodulation Performance for CA (3DL CA) | Rel-15 | C017h | UEs supporting 5GS FR1 and 3DL CA AND supporting 4Rx UE capability on some of the CCs | E017 | | +| 5.2A.3A.1.3 | 2Rx-4Rx Normal PDSCH Demodulation Performance for CA (4DL CA) | Rel-15 | C017i | UEs supporting 5GS FR1 and 4DL CA AND supporting 4Rx UE capability on some of the CCs | E018 | | +| 5.3.1.1.1 | 1Rx FDD FR1 PDCCH performance for RedCap | Rel-17 | C177a | RedCap UEs supporting 5GS FDD FR1 and 1Rx UE capability | D008 | | +| 5.3.2.1.1 | 2Rx FDD FR1 PDCCH 1 Tx antenna performance for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.3.2.1.2 | 2Rx FDD FR1 PDCCH 2 Tx antenna performance for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.3.2.1.3 | 2Rx FDD FR1 PDCCH 1 Tx antenna performance for power saving | Rel-16 | C088 | UEs supporting 5GS FDD FR1 and Long DRX Cycle and DRX adaptation but not supporting FDD bands with 4Rx UE capability | D008 | | +| 5.3.2.1.4 | 2Rx FDD FR1 PDCCH performance for RedCap | Rel-17 | C177b | RedCap UEs supporting 5GS FDD FR1 and 2Rx UE capability | D008 | | +| 5.3.2.2.1 | 2Rx TDD FR1 PDCCH 1 Tx antenna performance for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.3.2.2.2 | 2Rx TDD FR1 PDCCH 2 Tx antenna performance for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.3.2.2.3 | 2Rx TDD FR1 PDCCH 1 Tx antenna performance for power saving | Rel-16 | C089 | UEs supporting 5GS TDD FR1 and Long DRX Cycle and DRX adaptation but not supporting TDD bands with 4Rx UE capability | D010 | | +| 5.3.2.2.4 | 2Rx TDD FR1 PDCCH performance for RedCap | Rel-17 | C177d | RedCap UEs supporting 5GS TDD FR1 and 2Rx UE capability | D009 | | +| 5.3.3.1.1 | 4Rx FDD FR1 PDCCH 1 Tx antenna performance for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 5.3.3.1.2 | 4Rx FDD FR1 PDCCH 2 Tx antenna performance for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|--------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 5.3.3.1.3 | 4Rx FDD FR1 PDCCH 1 Tx antenna performance for power saving | Rel-16 | C090 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports and Long DRX Cycle and DRX adaptation | D008 | | +| 5.3.3.2.1 | 4Rx TDD FR1 PDCCH 1 Tx antenna performance for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 5.3.3.2.2 | 4Rx TDD FR1 PDCCH 2 Tx antenna performance for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 5.3.3.2.3 | 4Rx TDD FR1 PDCCH 1 Tx antenna performance for power saving | Rel-16 | C091 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports and Long DRX Cycle and DRX adaptation | D010 | | +| 5.5.1 | FR1 Sustained downlink data rate performance for single carrier | Rel-15 | C001 | UEs supporting 5GS FDD FR1 or TDD FR1 (SA) | D008
D009
D010 | | +| 5.5A.1.1 | FR1 SDR performance for CA (2DL CA) | Rel-15 | C001e | UEs supporting 5GS FDD FR1 or TDD FR1 (SA) and supporting 2DL CA | E016 | | +| 5.5A.1.2 | FR1 SDR performance for CA (3DL CA) | Rel-15 | C001i | UEs supporting 5GS FDD FR1 or TDD FR1 (SA) and supporting 3DL CA | E017 | | +| 5.5A.1.3 | FR1 SDR performance for CA (4DL CA) | Rel-15 | C001j | UEs supporting 5GS FDD FR1 or TDD FR1 (SA) and supporting 4DL CA | E018 | | +| 5.5A.1.4 | FR1 SDR performance for CA (5DL CA) | Rel-15 | C001k | UEs supporting 5GS FDD FR1 or TDD FR1 (SA) and supporting 5DL CA | E019 | | +| 6 | CSI reporting requirements (Conducted requirements) | | | | | | +| 6.2.1.1.1.1 | 1Rx FDD FR1 periodic CQI reporting under AWGN conditions for RedCap | Rel-17 | C177a | RedCap UEs supporting 5GS FDD FR1 and 1Rx UE capability | D008 | | +| 6.2.1.2.1.1 | 1Rx TDD FR1 periodic CQI reporting under AWGN conditions for RedCap | Rel-17 | C177c | RedCap UEs supporting 5GS TDD FR1 and 1Rx UE capability | D009 | | +| 6.2.1.2.2.1 | 1Rx TDD FR1 periodic wideband CQI reporting under fading conditions for RedCap | Rel-17 | C177c | RedCap UEs supporting 5GS TDD FR1 and 1Rx UE capability | D009 | | +| 6.2.2.1.1.1 | 2Rx FDD FR1 periodic CQI reporting under AWGN conditions for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|-------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 6.2.2.1.1.2 | 2Rx FDD FR1 periodic CQI reporting with Table 3 under AWGN conditions for both SA and NSA | Rel-16 | C074 | UEs supporting 5GS FDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ , but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.2.2.1.1.4 | 2Rx FDD FR1 periodic CQI reporting under AWGN conditions for RedCap for SA | Rel-17 | C177b | RedCap UEs supporting 5GS FDD FR1 and 2Rx UE capability | D008 | | +| 6.2.2.1.2.1 | 2Rx FDD FR1 periodic wideband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.2.2.1.2.2 | 2Rx FDD FR1 aperiodic subband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.2.2.1.2.3 | 2Rx FDD FR1 Wideband CQI reporting with inter-cell interference | Rel-15 | C015d | UEs supporting 5GS FDD FR1 and MMSE-IRC receiver but not supporting FDD bands with 4Rx UE capability | D008 | NOTE 1. | +| 6.2.2.2.1.1 | 2Rx TDD FR1 periodic CQI reporting under AWGN conditions for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.2.2.2.1.2 | 2Rx TDD FR1 periodic CQI reporting with Table 3 under AWGN conditions for both SA and NSA | Rel-16 | C075 | UEs supporting 5GS TDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ , but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.2.2.2.1.5 | 2Rx TDD FR1 periodic CQI reporting under AWGN conditions for RedCap | Rel-17 | C177d | RedCap UEs supporting 5GS TDD FR1 and 2Rx UE capability | D009 | | +| 6.2.2.2.2.1 | 2Rx TDD FR1 periodic wideband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.2.2.2.2.2 | 2Rx TDD FR1 aperiodic subband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.2.3.1.1.1 | 4Rx FDD FR1 periodic CQI reporting under AWGN conditions for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 6.2.2.2.2.4 | 2Rx TDD FR1 periodic wideband CQI reporting under | Rel-17 | C177d | RedCap UEs supporting 5GS TDD | D009 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|------------------------------|---------|---------------|---------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | fading conditions for RedCap | | | FR1 and 2Rx UE capability | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|-------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------------------------------| +| | | | Condition | Comment | | | +| 6.2.3.1.1.2 | 4Rx FDD FR1 periodic CQI reporting with Table 3 under AWGN conditions for both SA and NSA | Rel-16 | C076 | UEs supporting 5GS FDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ and 4Rx antenna ports | D008 | | +| 6.2.3.1.2.1 | 4Rx FDD FR1 periodic wideband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 6.2.3.1.2.2 | 4Rx FDD FR1 aperiodic subband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008 | | +| 6.2.3.2.1.1 | 4Rx TDD FR1 periodic CQI reporting under AWGN conditions for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 6.2.3.2.1.2 | 4Rx TDD FR1 periodic CQI reporting with Table 3 under AWGN conditions for both SA and NSA | Rel-16 | C077 | UEs supporting 5GS TDD FR1 and alternative 64QAM MCS table for PDSCH and CQI table with target BLER of $10^{-5}$ and 4Rx antenna ports | D010 | | +| 6.2.3.2.2.1 | 4Rx TDD FR1 periodic wideband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 6.2.3.2.2.2 | 4Rx TDD FR1 aperiodic subband CQI reporting under fading conditions for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 6.2A.3.1.1 | CQI reporting accuracy under AWGN conditions for CA (2DL CA) | Rel-15 | C031 | UEs supporting 5GS FR1 and CA (2DL CA) | E016 | Test execution not necessary if 6.2A.3.1.2 is executed. | +| 6.2A.3.1.2 | CQI reporting accuracy under AWGN conditions for CA (3DL CA) | Rel-15 | C033 | UEs supporting 5GS FR1 and CA (3DL CA) | E017 | Test execution not necessary if 6.2A.3.1.3 is executed. | +| 6.2A.3.1.3 | CQI reporting accuracy under AWGN conditions for CA (4DL CA) | Rel-15 | C036 | UEs supporting 5GS FR1 and CA (4DL CA) | E018 | | +| 6.3.2.1.1 | 2Rx FDD FR1 Single PMI with 4TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.3.2.1.2 | 2Rx FDD FR1 Single PMI with 8TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.3.2.1.3 | 2Rx FDD FR1 Multiple PMI with 16Tx Type I – SinglePanel Codebook for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.3.2.1.4 | 2Rx FDD FR1 Single PMI with 32Tx TypeI – | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not | D008 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------|------------------------------------------|---------|---------------|---------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| | SinglePanel Codebook for both SA and NSA | | | supporting FDD bands with 4Rx UE capability | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-----------|--------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 6.3.2.1.5 | 2Rx FDD FR1 Multiple PMI with 16Tx TypeII codebook for both SA and NSA | Rel-15 | C015c | UEs supporting 5GS FDD FR1 and supporting Type II codebook but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.3.2.1.6 | 2Rx FDD FR1 Multiple PMI with 16Tx Enhanced TypeII codebook for both SA and NSA | Rel-16 | C128 | UEs supporting 5GS FDD FR1 and Enhanced Type II codebook with at least 16 ports per CSI-RS resource, but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.3.2.2.1 | 2Rx TDD FR1 Single PMI with 4TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.3.2.2.2 | 2Rx TDD FR1 Single PMI with 8TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.3.2.2.3 | 2Rx TDD FR1 Multiple PMI with 16Tx TypeI - SinglePanel codebook for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.3.2.2.4 | 2Rx TDD FR1 Single PMI with 32Tx TypeI - SinglePanel codebook for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.3.2.2.5 | 2Rx TDD FR1 Multiple PMI with 16Tx TypeII codebook for both SA and NSA | Rel-15 | C016c | UEs supporting 5GS TDD FR1 and supporting Type II codebook but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.3.2.2.6 | 2Rx TDD FR1 Multiple PMI with 16Tx Enhanced TypeII codebook for both SA and NSA | Rel-16 | C129 | UEs supporting 5GS TDD FR1 and Enhanced Type II codebook with at least 16 ports per CSI-RS resource, but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.3.3.1.1 | 4Rx FDD FR1 Single PMI with 4TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008
D011 | | +| 6.3.3.1.2 | 4Rx FDD FR1 Single PMI with 8TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008
D011 | | +| 6.3.3.1.3 | 4Rx FDD FR1 Multiple PMI with 16Tx Type I – SinglePanel Codebook for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008
D011 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-----------|-------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 6.3.3.1.4 | 4Rx FDD FR1 Single PMI with 32Tx Type1 – SinglePanel Codebook for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008
D011 | | +| 6.3.3.1.5 | 4Rx FDD FR1 Multiple PMI with 16Tx TypeII codebook for both SA and NSA | Rel-15 | C017c | UEs supporting 5GS FDD FR1 and supporting Type II codebook and 4Rx antenna ports | D008
D011 | | +| 6.3.3.1.6 | 4Rx FDD FR1 Multiple PMI with 16Tx Enhanced TypeII codebook for both SA and NSA | Rel-16 | C130 | UEs supporting 5GS FDD FR1 and Enhanced Type II codebook with at least 16 ports per CSI-RS resource, and 4Rx antenna ports | D008
D011 | | +| 6.3.3.2.1 | 4Rx TDD FR1 Single PMI with 4TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D010
D011 | | +| 6.3.3.2.2 | 4Rx TDD FR1 Single PMI with 8TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D010
D011 | | +| 6.3.3.2.3 | 4Rx TDD FR1 Multiple PMI with 16Tx Type1 - SinglePanel codebook for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 6.3.3.2.4 | 4Rx TDD FR1 Single PMI with 32Tx Type1 - SinglePanel codebook for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010 | | +| 6.3.3.2.5 | 4Rx TDD FR1 Multiple PMI with 16Tx TypeII codebook for both SA and NSA | Rel-15 | C019c | UEs supporting 5GS TDD FR1 and supporting Type II codebook and 4Rx antenna ports | D010 | | +| 6.3.3.2.6 | 4Rx TDD FR1 Multiple PMI with 16Tx Enhanced TypeII codebook for both SA and NSA | Rel-16 | C131 | UEs supporting 5GS TDD FR1 and Enhanced Type II codebook with at least 16 ports per CSI-RS resource, and 4Rx antenna ports | D010 | | +| 6.4.2.1_1 | 2Rx FDD FR1 RI reporting for both SA and NSA | Rel-15 | C015 | UEs supporting 5GS FDD FR1 but not supporting FDD bands with 4Rx UE capability | D008 | | +| 6.4.2.1.1 | 2Rx FDD FR1 RI reporting for RedCap | Rel-17 | C177b | RedCap UEs supporting 5GS FDD FR1 and 2Rx UE capability | D008 | | +| 6.4.2.2_1 | 2Rx TDD FR1 RI reporting for both SA and NSA | Rel-15 | C016 | UEs supporting 5GS TDD FR1 but not supporting TDD bands with 4Rx UE capability | D010 | | +| 6.4.2.2.1 | 2Rx TDD FR1 RI reporting for RedCap | Rel-17 | C177d | RedCap UEs supporting 5GS TDD FR1 and 2Rx UE capability | D009 | | +| 6.4.3.1_1 | 4Rx FDD FR1 RI reporting for both SA and NSA | Rel-15 | C017 | UEs supporting 5GS FDD FR1 and 4Rx antenna ports | D008
D011 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|-------------|---------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 6.4.3.2_1 | 4Rx TDD FR1 RI reporting for both SA and NSA | Rel-15 | C019 | UEs supporting 5GS TDD FR1 and 4Rx antenna ports | D010
D011 | | +| 7 | Demodulation performance requirements (Radiated requirements) | | | | | | +| 7.2.2.2.1_1 | 2Rx TDD FR2 PDSCH mapping Type A performance - 2x2 MIMO with baseline receiver for SA and NSA | Rel-15 | C061 | UEs supporting 5GS TDD FR2 | D013
D014
D015 | | +| 7.2.2.2.1_2 | 2Rx TDD FR2 PDSCH mapping Type A performance - 2x2 MIMO with enhanced type 1 receiver for SA and NSA | Rel-15 | C062c | UEs supporting 5GS TDD FR2 and Enhanced Receiver Type 1 | D014 | | +| 7.2.2.2.1_3 | 2Rx TDD FR2 PDSCH mapping Type A performance - 2x2 MIMO with 256QAM for SA and NSA (Rel-16 and forward) | Rel-16 | C126 | UEs supporting 5GS TDD FR2 and PDSCH 256QAM for FR2 | D013 | | +| 7.2.2.2.2_1 | 2Rx TDD FR2 PDSCH repetitions over multiple slots - 2x2 MIMO with baseline receiver for SA and NSA | Rel-16 | C171 | UEs supporting 5GS TDD FR2 and alternative 64QAM MCS table for PDSCH and aggregationFactorDL > 1 for PDSCH repetition multislots | D014 | | +| 7.2.2.2.3_1 | 2Rx TDD FR2 PDSCH mapping Type B performance - 2x2 MIMO with baseline receiver for SA and NSA | Rel-16 | C172 | UEs supporting 5GS TDD FR2 and aggregationFactorDL > 1 for PDSCH repetition multislots | D014 | | +| 7.2A.2.1 | 2Rx TDD FR2 CA requirements for normal PDSCH Demodulation Performance for both SA and NSA (2DLCA) | Rel-15 | C061a | UEs supporting 5GS TDD FR2 AND 2DL CA | E032 | | +| 7.2A.2.2 | 2Rx TDD FR2 CA requirements for normal PDSCH Demodulation Performance for both SA and NSA (3DLCA) | Rel-15 | C061b | UEs supporting 5GS TDD FR2 AND 3DL CA | E033 | | +| 7.3.2.2.1 | 2Rx TDD FR2 PDCCH 1 Tx antenna performance for both SA and NSA | Rel-15 | C061 | UEs supporting 5GS TDD FR2 | D014 | | +| 7.3.2.2.2 | 2Rx TDD FR2 PDCCH 2 Tx antenna performance for both SA and NSA | Rel-15 | C061 | UEs supporting 5GS TDD FR2 | D014 | | +| 7.3.2.2.3 | 2Rx TDD FR2 PDCCH 1 Tx antenna performance for power saving | Rel-16 | C092 | UEs supporting 5GS TDD FR2 and Long DRX Cycle and DRX adaptation | D014 | | +| 7.5.1 | FR2 Sustained downlink data rate performance for single carrier | Rel-15 | C061 | UEs supporting 5GS TDD FR2 | D014 | | +| 7.5.1.1 | FR2 SDR performance for CA (2DL CA) | Rel-15 | C061a | UEs supporting 5GS TDD FR2 and CA (2DL CA) | E032 | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|---------------|-------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------|------------------------|-----------------------------------------------------------------------------------| +| | | | Condition | Comment | | | +| 7.5.1.2 | FR2 SDR performance for CA (3DL CA) | Rel-15 | C061b | UEs supporting 5GS TDD FR2 and CA (3DL CA) | E033 | NOTE 1 | +| 7.5.1.3 | FR2 SDR performance for CA (4DL CA) | Rel-15 | TBD | UEs supporting 5GS TDD FR2 and CA (4DL CA) | E034 | NOTE 1 | +| 7.5.1.4 | FR2 SDR performance for CA (5DL CA) | Rel-15 | TBD | UEs supporting 5GS TDD FR2 and CA (5DL CA) | E035 | NOTE 1 | +| 7.5.1.5 | FR2 SDR performance for CA (6DL CA) | Rel-15 | TBD | UEs supporting 5GS TDD FR2 and CA (6DL CA) | E036 | NOTE 1 | +| 7.5.1.6 | FR2 SDR performance for CA (7DL CA) | Rel-15 | TBD | UEs supporting 5GS TDD FR2 and CA (7DL CA) | E037 | NOTE 1 | +| 7.5.1.7 | FR2 SDR performance for CA (8DL CA) | Rel-15 | TBD | UEs supporting 5GS TDD FR2 and CA (8DL CA) | E038 | | +| 8 | CSI reporting requirements (Radiated requirements) | | | | | | +| 8.2.2.2.1.1 | 2Rx TDD FR2 periodic wideband CQI reporting under AWGN performance for both SA and NSA | Rel-15 | C061 | UEs supporting 5GS TDD FR2 | D014 | | +| 8.2.2.2.2.1 | 2Rx TDD FR2 aperiodic wideband CQI reporting under fading performance for both SA and NSA | Rel-15 | C061F | UEs supporting 5GS TDD FR2 | D014 | Skip TC 8.2.2.2.2.1 if TS 38.521-4 TC 8.2.2.2.2.1_1 has been executed and passed. | +| 8.2.2.2.2.1_1 | 2Rx TDD FR2 aperiodic CQI wideband reporting under fading performance for both SA and NSA – 256QAM (Rel-16 and forward) | Rel-16 | C126 | UEs supporting 5GS TDD FR2 and DL 256QAM | D013 | NOTE 1 | +| 8.2A.3.1.1 | 2Rx CQI reporting accuracy under AWGN conditions for CA (2DL CA) | Rel-15 | C006c | UEs supporting 5GS FR2 and CA (2DL CA) | E032 | Test execution not necessary if 8.2A.3.1.2 is executed. | +| 8.2A.3.1.2 | 2Rx CQI reporting accuracy under AWGN conditions for CA (3DL CA) | Rel-15 | C006d | UEs supporting 5GS FR2 and CA (3DL CA) | E033 | Test execution not necessary if 8.2A.3.1.3 is executed. | +| 8.2A.3.1.3 | 2Rx CQI reporting accuracy under AWGN conditions for CA (4DL CA) | Rel-15 | C006e | UEs supporting 5GS FR2 and CA (4DL CA) | E034 | | +| 8.3.2.2.1 | 2Rx TDD FR2 Single PMI with 2TX TypeI-SinglePanel codebook for both SA and NSA | Rel-15 | C061 | UEs supporting 5GS TDD FR2 | D014 | | +| 8.4.2.2.1 | 2Rx TDD FR2 RI reporting for both SA and NSA | FFS | FFS | FFS | FFS | NOTE 1 | +| 9 | Demodulation performance requirements for interworking | | | | | | + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|---------|---------------|---------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 9.4B.1.1 | Sustained downlink data rate performance for EN-DC within FR1 | Rel-15 | C020 | UEs supporting 5GS FDD FR1 or TDD FR1 (NSA) | D008
D009
D010 | | +| 9.4B.1.2 | Sustained downlink data rate performance for EN-DC including FR2 NR carrier | FFS | FFS | FFS | FFS | NOTE 1 | +| 10 | CSI reporting requirements for interworking | | | | | | +| 11 | V2X requirements | | | | | | +| 11.1.2.1.1_1 | 2Rx FR1 PSSCH performance - single active PSSCH link | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| 11.1.3.1.1_1 | 2Rx FR1 PSCCH performance - single active PSSCH link | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| 11.1.5.1.1_1 | 2Rx FR1 PSCCH performance - single active PSSCH link | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| 11.1.6.1.1_1 | 2Rx FR1 Power imbalance performance - two active PSSCH link | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| 11.1.7.1.1_1 | 2Rx FR1 HARQ buffer soft combining performance - maximum number of HARQ processes | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| 11.1.8.1.1_1 | 2Rx FR1 PSCCH decoding capability - maximum number of received PSCCHs | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| 11.1.9.1.1_1 | 2Rx FR1 PSFCH decoding capability - maximum number of received PSFCHs | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | D016 | | +| NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.521-4. | | | | | | | +| NOTE 2: Void. | | | | | | | +| NOTE 3: Void. | | | | | | | + +Table 4.1.4-1a: Void + +Table 4.1.4-1b: Void + +Table 4.1.4-1c: Void + +## 4.2 RRM conformance test cases + +**Table 4.2-1: Applicability of RRM EN-DC FR1 conformance test cases, ref. TS 38.533 [5]** + +| TC Title | Release | Applicability | | Additional Information | Brand | +|-------------------------------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------|-------------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| CONNECTED state mobility | | | | | | +| connection mobility control | | | | | | +| access | | | | | | +| R1 contention based random access | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.3.2.2.1 has been executed. | 2Rx
4Rx | +| R1 non-contention based random access | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.3.2.2.2 has been executed. | 2Rx
4Rx | +| R1 2-step contention based random access | Rel-16 | C157 | UEs supporting EN-DC FR1 and 2-step RACH | Test execution not necessary if test 6.3.2.2.3 has been executed. | 2Rx
4Rx | +| R1 2-step non-contention based random | Rel-16 | C158 | UEs supporting EN-DC FR1 and 2-step RACH | Test execution not necessary if test 6.3.2.2.4 has been executed. | 2Rx
4Rx | +| | | | | | | +| Transmit Timing | | | | | | +| R1 UE transmit timing accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.4.1.1 has been executed. | 2Rx
4Rx | +| Timing accuracy | | | | | | +| Timing advance | | | | | | +| R1 timing advance adjustment accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.4.3.1 has been executed. | 2Rx
4Rx | +| | | | | | | +| Radio link characteristics | | | | | | +| Radio link monitoring | | | | | | +| R1 radio link monitoring out-of-sync test for non-configured with SSB-based RLM RS in non-DRX | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.5.1.1 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for non-configured with SSB-based RLM RS in non-DRX | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.5.1.2 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring out-of-sync test for non-configured with SSB-based RLM RS in DRX | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.5.1.3 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for non-configured with SSB-based RLM RS in DRX | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.5.1.4 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring out-of-sync test for non-configured with CSI-RS-based RLM RS in non-DRX | Rel-15 | C038 | UEs supporting EN-DC FR1 and CSI-RS-based RLM | Test execution not necessary if test 6.5.1.5 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for non-configured with CSI-RS-based RLM RS in non-DRX | Rel-15 | C038 | UEs supporting EN-DC FR1 and CSI-RS-based RLM | Test execution not necessary if test 6.5.1.6 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring out-of-sync test for non-configured with CSI-RS-based RLM RS in DRX | Rel-15 | C038a | UEs supporting EN-DC FR1, CSI-RS-based RLM and long DRX cycle | Test execution not necessary if test 6.5.1.7 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for non-configured with CSI-RS-based RLM RS in DRX | Rel-15 | C038a | UEs supporting EN-DC FR1, CSI-RS-based RLM and long DRX cycle | Test execution not necessary if test 6.5.1.8 has been executed. | 2Rx
4Rx | +| R1 Radio Link Monitoring Out-of-sync Test for non-configured with SSB-based RLM RS for UE relaxed measurement criterion | Rel-17 | C021e | UEs supporting EN-DC FR1, long DRX cycle and RLM relaxed measurements | | 2Rx
4Rx | +| | | | | | | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|--------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| R1 interruptions at transitions between active and inactive during DRX in synchronous EN-DC | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | | 2Rx
4Rx | +| R1 interruptions at transitions between active and inactive during DRX in asynchronous EN-DC | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | | 2Rx
4Rx | +| R1 interruptions during measurements on secondary NR SCC in synchronous EN-DC | Rel-15 | C067 | UEs supporting EN-DC FR1 and 2DL CA in NR | | 2Rx
4Rx | +| R1 interruptions during measurements on secondary NR SCC in asynchronous EN-DC | Rel-15 | C067 | UEs supporting EN-DC FR1 and 2DL CA in NR | | 2Rx
4Rx | +| R1 interruptions during measurements on secondary E-UTRAN SCC in synchronous EN-DC | Rel-15 | C068 | UEs supporting EN-DC FR1 and 2DL CA in E-UTRA | | 2Rx
4Rx | +| R1 interruptions during measurements on secondary E-UTRAN SCC in asynchronous EN-DC | Rel-15 | C068 | UEs supporting EN-DC FR1 and 2DL CA in E-UTRA | | 2Rx
4Rx | +| R1 interruptions due to RRM and RLM/BFD measurements on deactivated NR PSCell | Rel-17 | C288 | UEs supporting EN-DC FR1 and activation and deactivation on SCG | | 2Rx
4Rx | +| SCell activation and deactivation delay | | | | | | +| R1 SCell activation and deactivation of known SCell in non-DRX for 160ms SCell measurement cycle | Rel-15 | C067 | UEs supporting EN-DC FR1 and 2DL CA in NR | | 2Rx
4Rx | +| R1 SCell activation and deactivation of known SCell in non-DRX for 640ms SCell measurement cycle | Rel-15 | C067 | UEs supporting EN-DC FR1 and 2DL CA in NR | | 2Rx
4Rx | +| R1 SCell activation and deactivation of unknown SCell in non-DRX | Rel-15 | C067 | UEs supporting EN-DC FR1 and 2DL CA in NR | | 2Rx
4Rx | +| R1 direct SCell activation at SCell addition of unknown SCell | Rel-16 | C243 | UEs supporting EN-DC FR1 and 2DL CA in NR and direct SCell activation | | 2Rx
4Rx | +| R1 fast SCell Activation of known SCell in non-DRX for 160ms SCell measurement cycle | Rel-17 | C267 | UEs supporting EN-DC FR1 and 2DL CA in NR and fast SCell activation | NOTE 1 | 2Rx
4Rx | +| R1 fast SCell Activation of known SCell for 640ms SCell measurement cycle | Rel-17 | C267 | UEs supporting EN-DC FR1 and 2DL CA in NR and fast SCell activation | NOTE 1 | 2Rx
4Rx | +| Carrier RRC reconfiguration delay | | | | | | +| R1 UE UL carrier RRC reconfiguration delay | Rel-15 | C032 | UEs supporting EN-DC FR1 and SUL | Test execution not necessary if test 6.5.4.1 has been executed. | 2Rx
4Rx | +| Beam failure detection and link recovery procedures | | | | | | +| R1 SSB-based beam failure detection and link recovery in non-DRX | Rel-15 | C082 | UEs supporting EN-DC FR1 and link recovery | Test execution not necessary if test 6.5.5.1 has been executed. | 2Rx
4Rx | +| R1 SSB-based beam failure detection and link recovery in DRX | Rel-15 | C082a | UEs supporting EN-DC FR1 and long DRX cycle and link recovery | Test execution not necessary if test 6.5.5.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based beam failure detection and link recovery in non-DRX | Rel-15 | C083 | UEs supporting EN-DC FR1 and CSI-RS-based RLM and link recovery | Test execution not necessary if test 6.5.5.3 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based beam failure detection and link recovery in DRX | Rel-15 | C083a | UEs supporting EN-DC FR1 and long DRX cycle and CSI-RS-based RLM and link recovery | Test execution not necessary if test 6.5.5.4 has been executed. | 2Rx
4Rx | +| R1 SCell CSI-RS-based beam failure detection and SSB-based link recovery in non-DRX | Rel-16 | C175 | UEs supporting EN-DC FR1 and CSI-RS-based RLM and SSB link recovery | Test execution not necessary if test 6.5.5.5 has been executed. | 2Rx
4Rx | +| R1 SCell CSI-RS-based beam failure detection and SSB-based link recovery in DRX | Rel-16 | C176 | UEs supporting EN-DC FR1 and long DRX cycle and CSI-RS-based RLM and SSB link recovery | Test execution not necessary if test 6.5.5.6 has been executed. | 2Rx
4Rx | +| BWP switch delay | | | | | | +| DCI and timer-based active BWP switch | | | | | | +| R1 DCI-based DL active BWP switch in non-synchronous EN-DC | Rel-15 | C065 | UEs supporting EN-DC FR1 and (DCI and timer based active BWP | | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|----------|---------|---------------|--------------------------------------------------------------------------------------|------------------------|-------| +| | | Condition | Comment | | | +| | | | switching delay Type1 or Type2) and
(Support of BWP adaptation upto2 or
upto4) | | | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| R1 DCI-based DL active BWP switch with non-DRX in synchronous EN-DC | Rel-15 | C065a | UEs supporting EN-DC FR1 and (DCI and timer based active BWP switching delay Type1 or Type2) and (Support of BWP adaptation upto2 or upto4) and 2DL CA | | 2Rx
4Rx | +| Red active BWP switch | | | | | | +| R1 RRC-based DL active BWP switch in non-synchronous EN-DC | Rel-15 | C065b | UEs supporting EN-DC FR1 and (Support of BWP adaptation upto2 or upto4) | | 2Rx
4Rx | +| Synchronous DCI-based and Timer-based Active Switch on multiple CCs | | | | | | +| Synchronous E-UTRAN – NR PSCell FR1 DL active switch in non-DRX in EN-DC on multiple CCs | Rel-16 | C065d | UEs supporting EN-DC FR1, incremental delay for DCI and timer based active BWP switching on multiple CCs simultaneously and 2DL CA | NOTE 1 | 2Rx
4Rx | +| Synchronous RRC-based Active BWP Switch on CCs | | | | | | +| Synchronous NR – NR PSCell FR1 DL active BWP switch in synchronous EN-DC on multiple CCs | Rel-16 | C065d | UEs supporting EN-DC FR1, incremental delay for DCI and timer based active BWP switching on multiple CCs simultaneously and 2DL CA | NOTE 1 | 2Rx
4Rx | +| Cell addition and release delay | | | | | | +| R1 cell addition and release delay of known | Rel-15 | C021 | UEs supporting EN-DC FR1 | | 2Rx
4Rx | +| Switching | | | | | | +| R1 interruptions at switching between two carriers | Rel-16 | C126a | UEs supporting EN-DC and dynamic UL Tx switching in case of inter-band EN-DC | | 2Rx
4Rx | +| Activation and deactivation delay | | | | | | +| R1 PSCell activation and deactivation delay | Rel-17 | C288 | UEs supporting EN-DC FR1 and activation and deactivation on SCG | | 2Rx
4Rx | +| Conditional PSCell addition and release delay (FR1) | | | | | | +| R1 Addition and Release Delay of PSCell | Rel-17 | C268 | UEs supporting EN-DC FR1 and conditional PSCell addition in EN-DC | NOTE 1 | 2Rx
4Rx | +| Measurement procedures | | | | | | +| Frequency measurements | | | | | | +| R1 event-triggered reporting without gap in FR1 | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.6.1.1 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting without gap in FR1 | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.6.1.2 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting with gap in non-DRX | Rel-15 | C042 | UEs supporting EN-DC FR1 and CSI-RS-based RLM and BWP operation without bandwidth restriction | Test execution not necessary if test 6.6.1.3 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting with gap in DRX | Rel-15 | C042a | UEs supporting EN-DC FR1, CSI-RS-based RLM, BWP operation without bandwidth restriction and long DRX cycle | Test execution not necessary if test 6.6.1.4 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting without gap in FR1 with SSB time index detection | Rel-15 | C021b | UEs supporting EN-DC FDD FR1 | Test execution not necessary if test 6.6.1.5 has been executed. | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|----------|---------|---------------|---------|------------------------|-------| +| | | Condition | Comment | | | +| | | | | has been executed. | 4Rx | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|----------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| R1 event-triggered reporting with gap in non-SSB time index detection | Rel-15 | C042b | UEs supporting EN-DC FDD FR1 and CSI-RS based RLM and BWP operation without bandwidth restriction | Test execution not necessary if test 6.6.1.6 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting without gap in UE configured with highSpeedMeasFlag-r16 | Rel-15 | C097 | UEs supporting EN-DC FR1 and long DRX cycle and measurement enhancements in HST | Test execution not necessary if test 6.6.1.7 has been executed. | 2Rx
4Rx | +| R1 event triggered reporting cell without SSB detection in DRX for UE configured with edMeasCA-Scell-r17 | Rel-16 | C021c | UEs supporting EN-DC FR1 and CA measurement enhancements in HST | Test execution not necessary if test 6.6.1.8 has been executed. | 2Rx
4Rx | +| Inter-frequency measurements | | | | | | +| R1-FR1 event-triggered reporting in non-DRX | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.6.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 event-triggered reporting in DRX | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.6.2.2 has been executed. | 2Rx
4Rx | +| R1-FR1 event-triggered reporting in non-DRX time index detection | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.6.2.5 has been executed. | 2Rx
4Rx | +| R1-FR1 event-triggered reporting in DRX with time index detection | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.6.2.6 has been executed. | 2Rx
4Rx | +| R1-FR1 event triggered reporting without SSB detection in DRX for UE configured with edMeasInterFreq-r17 | Rel-16 | C021d | UEs supporting EN-DC FR1 and inter-frequency measurement enhancements in HST | Test execution not necessary if test 6.6.2.12 has been executed. | 2Rx
4Rx | +| L1-RSRP for beam reporting | | | | | | +| R1 SSB-based L1-RSRP measurement in FR1 | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.6.4.1 has been executed. | 2Rx
4Rx | +| R1 SSB-based L1-RSRP measurement in FR1 | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.6.4.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based L1-RSRP measurement in FR1 | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.6.4.3 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based L1-RSRP measurement in FR1 | Rel-15 | C021a | UEs supporting EN-DC FR1 and long DRX cycle | Test execution not necessary if test 6.6.4.4 has been executed. | 2Rx
4Rx | +| R1 SSB-based L1-RSRP measurement in FR1 for UE configured with highSpeedMeasFlag-r16 | Rel-15 | C098 | UEs supporting EN-DC FR1, long DRX cycle and intra-NR measurement enhancement in HST | Test execution not necessary if test 6.6.4.5 has been executed. | 2Rx
4Rx | +| L1-SINR for beam reporting | | | | | | +| R1 CSI-RS based CMR and no dedicated IMR L1-SINR measurement in non-DRX | Rel-16 | C141 | UEs supporting EN-DC FR1 and L1-SINR measurement based on CSI-RS as CMR without dedicated IMR configured | | 2Rx
4Rx | +| R1 SSB based CMR and dedicated IMR L1-SINR measurement in DRX | Rel-16 | C142 | UEs supporting EN-DC FR1 and long DRX cycle and L1-SINR measurement based on SSB as CMR and dedicated CSI-IM as IMR | | 2Rx
4Rx | +| R1 CSI-RS based CMR and dedicated IMR L1-SINR measurement in DRX | Rel-16 | C143 | UEs supporting EN-DC FR1 and long DRX cycle and L1-SINR measurement based on CSI-RS as CMR and dedicated CSI-RS as IMR | | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|-------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| Measurement performance requirements | | | | | | +| P | | | | | | +| Frequency measurements | | | | | | +| R1 SS-RSRP absolute measurement | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.1.1.1 has been executed. | 2Rx
4Rx | +| R1 SS-RSRP relative measurement accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.1.1.2 has been executed. | 2Rx
4Rx | +| Frequency measurements | | | | | | +| R1-FR1 SS-RSRP absolute measurement | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.1.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-RSRP relative measurement | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.1.2.2 has been executed. | 2Rx
4Rx | +| Q | | | | | | +| R1 SS-RSRQ measurement accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-RSRQ absolute measurement | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.2.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-RSRQ relative measurement | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.2.2.2 has been executed. | 2Rx
4Rx | +| S | | | | | | +| R1 SS-SINR measurement accuracy | Rel-15 | C035 | UEs supporting EN-DC FR1 and SS-SINR-meas | Test execution not necessary if test 6.7.3.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-SINR absolute measurement | Rel-15 | C035 | UEs supporting EN-DC FR1 and SS-SINR-meas | Test execution not necessary if test 6.7.3.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-SINR relative measurement | Rel-15 | C035 | UEs supporting EN-DC FR1 and SS-SINR-meas | Test execution not necessary if test 6.7.3.2.2 has been executed. | 2Rx
4Rx | +| P | | | | | | +| R1 SSB-based L1-RSRP absolute measurement accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.4.1.1 has been executed. | 2Rx
4Rx | +| R1 SSB-based L1-RSRP relative measurement accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.4.1.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based L1-RSRP absolute measurement accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.4.2.1 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based L1-RSRP relative measurement accuracy | Rel-15 | C021 | UEs supporting EN-DC FR1 | Test execution not necessary if test 6.7.4.2.2 has been executed. | 2Rx
4Rx | +| R | | | | | | +| R1 SFTD measurement accuracy | Rel-15 | C043 | UEs supporting EN-DC FR1 and SFTD measurements between E-UTRA Pcell and NR PSCell | | 2Rx
4Rx | +| C | | | | | | +| R1 CSI-RS based CMR and no dedicated | Rel-16 | C135 | UEs supporting EN-DC FR1 and L1- | Test execution not | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|------------------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| configured and CSI-RS resource set with off L1-SINR absolute measurement accuracy | | | SINR-measurement based on CSI-RS as CMR without dedicated IMR configured | necessary if test 6.7.9.1.1 has been executed. | 4Rx | +| R1 CSI-RS based CMR and no dedicated configured and CSI-RS resource set with off L1-SINR relative measurement accuracy | Rel-16 | C135 | UEs supporting EN-DC FR1 and L1-SINR-measurement based on CSI-RS as CMR without dedicated IMR configured | Test execution not necessary if test 6.7.9.1.2 has been executed. | 2Rx
4Rx | +| R1 SSB based CMR and dedicated IMR L1-absolute measurement accuracy | Rel-16 | C136 | UEs supporting EN-DC FR1 and L1-SINR-measurement based on SSB as CMR and dedicated CSI-IM as IMR | Test execution not necessary if test 6.7.9.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based CMR and dedicated IMR absolute measurement accuracy | Rel-16 | C137 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | Test execution not necessary if test 6.7.9.3.1 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based CMR and dedicated IMR relative measurement accuracy | Rel-16 | C137 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | Test execution not necessary if test 6.7.9.3.2 has been executed. | 2Rx
4Rx | +| with all NR cells in FR1 | | | | | | +| g characteristics | | | | | | +| PSCell addition | | | | | | +| R1 addition and release delay of known | Rel-15 | FFS | FFS | NOTE 1 | 2Rx
4Rx | + +branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. +to the corresponding Sub-Test as defined in TS 38.533 [5]. + +Table 4.2-1a: Void + +**Table 4.2-2: Applicability of RRM EN-DC FR2 conformance test cases, ref. TS 38.533 [5]** + +| TC Title | Release | Applicability | | Additional Information | Brand | +|--------------------------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------|------------------------|-------| +| | | Condition | Comment | | | +| CONNECTED state mobility | | | | | | +| connection mobility control | | | | | | +| random access | | | | | | +| FR2 contention based random access | Rel-16 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 non-contention based random access | Rel-16 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 2-step contention based random access | Rel-16 | C158 | UEs supporting EN-DC FR2 and 2-step RACH | NOTE 1 | 2Rx | +| FR2 2-step non-contention based random | Rel-16 | C158 | UEs supporting EN-DC FR2 and 2-step RACH | NOTE 1 | 2Rx | +| transmit timing | | | | | | +| FR2 UE transmit timing accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| power accuracy | | | | | | +| timing advance | | | | | | +| FR2 timing advance adjustment accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| radio link characteristics | | | | | | +| radio link monitoring | | | | | | +| FR2 radio link monitoring out-of-sync test for cell configured with SSB-based RLM RS in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | NOTE 1 | 2Rx | +| FR2 radio link monitoring in-sync test for cell configured with SSB-based RLM RS in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | NOTE 1 | 2Rx | +| FR2 radio link monitoring out-of-sync test for cell configured with SSB-based RLM RS in DRX | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 radio link monitoring in-sync test for cell configured with SSB-based RLM RS in DRX | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 radio link monitoring out-of-sync test for cell configured with CSI-RS-based RLM RS in non-DRX | Rel-15 | C161 | UEs supporting EN-DC FR2 and CSI-RS based RLM | NOTE 1 | 2Rx | +| FR2 radio link monitoring in-sync test for cell configured with CSI-RS-based RLM RS in non-DRX | Rel-15 | C161 | UEs supporting EN-DC FR2 and CSI-RS based RLM | NOTE 1 | 2Rx | +| FR2 radio link monitoring out-of-sync test for cell configured with CSI-RS-based RLM RS in DRX | Rel-15 | C162 | UEs supporting EN-DC FR2, CSI-RS-based RLM and long DRX cycle | | 2Rx | +| FR2 radio link monitoring in-sync test for cell configured with CSI-RS-based RLM RS in DRX | Rel-15 | C162 | UEs supporting EN-DC FR2, CSI-RS-based RLM and long DRX cycle | | 2Rx | +| FR2 radio link monitoring UE scheduling occasions | Rel-15 | C022n | UEs supporting EN-DC FR2 and PDCCH monitoring in any symbol of the slot (with or without span gap) | NOTE 1 | 2Rx | +| FR2 Radio Link Monitoring Out-of-sync Test for cell configured with SSB-based RLM RS for UE with relaxed measurement criterion | Rel-17 | C022e | UEs supporting EN-DC FR2, long DRX cycle and RLM relaxed measurements | | 2Rx | +| power control | | | | | | +| FR2 interruptions at transitions between active and inactive during DRX in synchronous EN-DC | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 interruptions at transitions between active and inactive during DRX in asynchronous EN-DC | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|---------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------|------------------------|-------| +| | | Condition | Comment | | | +| FR2 interruptions during measurements on connected NR SCC in synchronous EN-DC | Rel-15 | C180 | UEs supporting EN-DC FR2 and 2DL CA in NR | | 2Rx | +| FR2 interruptions during measurements on connected NR SCC in asynchronous EN-DC | Rel-15 | C180 | UEs supporting EN-DC FR2 and 2DL CA in NR | | 2Rx | +| FR2 interruptions during measurements on connected E-UTRAN SCC in synchronous EN-DC | FFS | FFS | FFS | NOTE 1 | 2Rx | +| FR2 interruptions during measurements on connected E-UTRAN SCC in asynchronous EN-DC | FFS | FFS | FFS | NOTE 1 | 2Rx | +| Activation and deactivation delay | | | | | | +| FR2 SCell activation and deactivation intra-band non-DRX | Rel-15 | C180 | UEs supporting EN-DC FR2 and 2DL CA in NR | | 2Rx | +| FR2 direct SCell activation at SCell addition of SCell | Rel-16 | C242 | UEs supporting EN-DC FR2 and 2DL CA in NR and direct SCell activation | | 2Rx | +| FR2 fast SCell Activation of SCell in FR2 intra-band | Rel-17 | C269 | UEs supporting EN-DC FR2 and 2DL CA in NR and direct SCell activation | NOTE 1 | 2Rx | +| FR2 Addition and Release Delay of NR PSCell | Rel-17 | C268a | UEs supporting EN-DC FR2 and conditional PSCell addition in EN-DC | NOTE 1 | 2Rx | +| Carrier RRC reconfiguration delay | | | | | | +| Failure detection and link recovery procedures | | | | | | +| FR2 SSB-based beam failure detection and recovery in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 SSB-based beam failure detection and recovery in DRX | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 CSI-RS-based beam failure detection and recovery in non-DRX | Rel-15 | C161 | UEs supporting EN-DC FR2 and CSI-RS-based RLM | | 2Rx | +| FR2 CSI-RS-based beam failure detection and recovery in DRX | Rel-15 | C162 | UEs supporting EN-DC FR2 and long DRX cycle and CSI-RS-based RLM | | 2Rx | +| FR2 scheduling available restriction during beam failure detection and link recovery in DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 CSI-RS-based BFD and LR for SCell in DRX | Rel-16 | C149 | UEs supporting EN-DC FR2 and CSI-RS based BFR on SCell | | 2Rx | +| FR2 SCell CSI-RS-based beam failure detection and link recovery in DRX | Rel-16 | C150 | UEs supporting EN-DC FR2 and long DRX cycle and CSI-RS based BFR on SCell | | 2Rx | +| FR2 SSB-based beam failure detection and recovery in DRX mode for UE fulfilling relaxed requirement criterion | Rel-17 | FFS | UEs supporting EN-DC FR2 and long DRX cycle and BFD relaxation criteria bfd-Relaxation-r17 | | 2Rx | +| BWP switch delay | | | | | | +| Timer-based active BWP switch | | | | | | +| FR2 DCI-based DL active BWP switch in non-synchronous EN-DC | FFS | FFS | FFS | NOTE 1 | 2Rx | +| FR2 DCI-based DL active BWP switch with non-DRX in synchronous EN-DC | Rel-15 | N/A | Not recommended due to LTE – FR2 testability issue | NOTE 1 | 2Rx | +| Timer-based active BWP switch | | | | | | +| FR2 RRC-based DL active BWP switch in non-synchronous EN-DC | Rel-15 | C065c | UEs supporting EN-DC FR2 and (Support of BWP adaptation upto2 or upto4) | | 2Rx | +| TCI state switch delay | | | | | | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------| +| | | Condition | Comment | | | +| FR2 MAC-CE based active TCI state switch | Rel-15 | C022m | UEs supporting EN-DC FR2, maximum number of active TCI states per BWP greater than 1, and maximum number of simultaneously trackable TRS resource sets per CC greater than 1 | NOTE 1 | 2Rx | +| FR2 RRC based active TCI state switch | Rel-15 | C022m | UEs supporting EN-DC FR2, maximum number of active TCI states per BWP greater than 1, and maximum number of simultaneously trackable TRS resource sets per CC greater than 1 | NOTE 1 | 2Rx | +| TCI state switch delay | | | | | | +| FR2 MAC-CE based active joint TCI state | Rel-17 | C278 | UEs supporting EN-DC FR2, and unified TCI state operation with joint DL/UL TCI update for intra-cell beam management | NOTE 1 | 2Rx | +| activation and deactivation delay | | | | | | +| FR2 PSCell activation and deactivation delay | Rel-17 | C289 | UEs supporting EN-DC FR2 and activation and deactivation on SCG | | 2Rx | +| FR2 MAC-CE based active uplink TCI state | Rel-17 | C279 | UEs supporting EN-DC FR2, and unified TCI state operation with separate DL/UL TCI update for intra-cell beam management | NOTE 1 | 2Rx | +| FR2 MAC-CE based active downlink TCI state | | C280 | UEs supporting EN-DC FR2, and unified TCI state operation with separate DL/UL TCI update for intra-cell beam management, and supporting RRC configuration of additional PCI different from serving cell associated with the TCI state and/or QCL-info, and unified TCI with separate DL/UL TCI update for inter-cell beam management | NOTE 1 | 2Rx | +| Measurement procedures | | | | | | +| Frequency measurements | | | | | | +| FR2 event-triggered reporting without gap in X | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 event-triggered reporting without gap in | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 event-triggered reporting with gap in non- | Rel-15 | C163 | UEs supporting EN-DC FR2, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | +| FR2 event-triggered reporting with gap in DRX | Rel-15 | C043a | UEs supporting EN-DC FR2, long DRX cycle, CSI-RS based RLM and BWP operation without BW restriction | | 2Rx | +| Frequency measurements | | | | | | +| FR2-FR2 event-triggered reporting in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2-FR2 event-triggered reporting in DRX | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2-FR2 event-triggered reporting in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| B time index detection | | | | | | +| FR2-FR2 event-triggered reporting in DRX with | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| e index detection | | | | | | + +| TC Title | Release | Applicability | | Additional Information | Brand | +|------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------|------------------------|-------| +| | | Condition | Comment | | | +| FR1-FR2 event-triggered reporting in non-DRX | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| FR1-FR2 event-triggered reporting in DRX | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| FR1-FR2 event-triggered reporting in non-DRX with time index detection | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| FR1-FR2 event-triggered reporting in DRX with time index detection | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| FR2 measurement for beam reporting | | | | | | +| FR2 SSB-based L1-RSRP measurement in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 SSB-based L1-RSRP measurement in DRX | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 CSI-RS-based L1-RSRP measurement in non-DRX | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 CSI-RS-based L1-RSRP measurement in DRX | Rel-15 | C022a | UEs supporting EN-DC FR2 and long DRX cycle | | 2Rx | +| FR2 SRS-RSRP measurement in non-DRX | Rel-16 | C022b | UEs supporting EN-DC FR2 and SRS-RSRP measurements | | 2Rx | +| FR2 measurement for beam reporting | | | | | | +| FR2 CSI-RS based CMR and no dedicated IMR measurement in DRX | Rel-16 | C141a | UEs supporting EN-DC FR2 and long DRX cycle and L1-SINR measurement based on CSI-RS as CMR without dedicated IMR configured | | 2Rx | +| FR2 SSB based CMR and dedicated IMR L1-RSRP measurement in non-DRX | Rel-16 | C142a | UEs supporting EN-DC FR2 and L1-SINR measurement based on SSB as CMR and dedicated CSI-RS as IMR | | 2Rx | +| FR2 CSI-RS based CMR and dedicated IMR L1-RSRP measurement in non-DRX | Rel-16 | C143a | UEs supporting EN-DC FR2 and L1-SINR measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | | 2Rx | +| FR2 measurement performance requirements | | | | | | +| FR2 SS-RSRP | | | | | | +| FR2 SS-RSRP measurement accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2-FR2 SS-RSRP measurement accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR1-FR2 SS-RSRP measurement accuracy | Rel-15 | N/A | Not recommended due to E-UTRA/FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| FR2 SS-RSRQ | | | | | | +| FR2 SS-RSRQ measurement accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2-FR2 SS-RSRQ measurement accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 SS-SINR | | | | | | +| FR2 SS-SINR measurement accuracy | Rel-15 | C069 | UEs supporting EN-DC FR2 and SS-SINR-meas | | 2Rx | +| FR2-FR2 SS-SINR measurement accuracy | Rel-15 | C069 | UEs supporting EN-DC FR2 and SS-SINR-meas | | 2Rx | +| FR2 L1-RSRP | | | | | | +| FR2 SSB based L1-RSRP measurement accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 CSI-RS based L1-RSRP measurement accuracy | Rel-15 | C022 | UEs supporting EN-DC FR2 | | 2Rx | +| FR2 SRS-RSRP measurement accuracy | Rel-16 | C022b | UEs supporting EN-DC FR2 and SRS-RSRP measurements | | 2Rx | +| FR2 measurement for beam reporting | | | | | | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------|------------------------|--------| +| | | Condition | Comment | | | +| FR2 CSI-RS based CMR and no dedicated configured and CSI-RS resource set with off L1-SINR measurement accuracy | Rel-16 | C141b | UEs supporting EN-DC FR2 and L1-SINR measurement based on CSI-RS as CMR without dedicated IMR configured | | 2Rx | +| FR2 SSB based CMR and dedicated IMR L1-absolute measurement accuracy | Rel-16 | C142a | UEs supporting EN-DC FR2 and L1-SINR measurement based on SSB as CMR and dedicated CSI-RS as IMR | | 2Rx | +| FR2 CSI-RS based CMR and dedicated IMR measurement accuracy | Rel-16 | C143a | UEs supporting EN-DC FR2 and L1-SINR measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | | 2Rx | + +Test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. + +Table 4.2-2a: Void + +**Table 4.2-3: Applicability of RRM NR SA FR1 conformance test cases, ref. TS 38.533 [5]** + +| TC Title | Release | Applicability | | Additional Information | Branch | | | | +|------------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------|------------------------|------------|--|--|--| +| | | Condition | Comment | | | | | | +| INACTIVE state mobility | | | | | | | | | +| Cell re-selection | | | | | | | | | +| NR cell re-selection | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | | | +| NR-FR1 cell re-selection | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | | | +| NR cell re-selection for UE fulfilling low relaxed measurement criterion | Rel-16 | C093 | UEs supporting 5GS NR SA FR1 and relaxed RRM measurement | | 2Rx
4Rx | | | | +| NR cell re-selection for UE fulfilling not-at-cell edge relaxed measurement criterion | Rel-16 | C093 | UEs supporting 5GS NR SA FR1 and relaxed RRM measurement | | 2Rx
4Rx | | | | +| NR-FR1 cell re-selection for UE fulfilling low relaxed measurement criterion | Rel-16 | C093 | UEs supporting 5GS NR SA FR1 and relaxed RRM measurement | | 2Rx
4Rx | | | | +| NR-FR1 cell re-selection for UE fulfilling not-at-cell edge relaxed measurement criterion | Rel-16 | C093 | UEs supporting 5GS NR SA FR1 and relaxed RRM measurement | | 2Rx
4Rx | | | | +| NR cell re-selection for UE configured with speedMeasFlag-r16 | Rel-15 | C052 | UEs supporting 5GS NR SA FR1 and measurement enhancements in HST | | 2Rx
4Rx | | | | +| NR-FR1 Cell reselection for UE configured with speedMeasInterFreq-r17 | Rel-16 | C052a | UEs supporting 5GS NR SA FR1 and inter-freq measurement enhancements in HST | | 2Rx
4Rx | | | | +| CONNECTED state mobility | | | | | | | | | +| Cell re-selection | | | | | | | | | +| NR – E-UTRA cell re-selection to higher priority | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | | | +| NR – E-UTRA cell re-selection to lower priority | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | | | +| NR – E-UTRA cell re-selection to lower priority for UE fulfilling low mobility relaxed measurement criterion | Rel-16 | C094 | UEs supporting 5GS NR SA FR1 and E-UTRA and relaxed RRM measurement | | 2Rx
4Rx | | | | +| NR – E-UTRA cell re-selection to lower priority for UE fulfilling not-at-cell edge relaxed measurement criterion | Rel-16 | C094 | UEs supporting 5GS NR SA FR1 and E-UTRA and relaxed RRM measurement | | 2Rx
4Rx | | | | +| NR – E-UTRA cell re-selection to lower priority for UE configured with highSpeedMeasFlag- | Rel-15 | C025b | UEs supporting 5GS NR SA FR1 and E-UTRA and E-UTRA inter-RAT measurement enhancements in HST | | 2Rx
4Rx | | | | +| ACTIVE state mobility | | | | | | | | | +| NR Configured Grant based Small Data Transmissions (CG-SDT) | Rel-17 | C001m | UEs supporting 5GS NR SA FR1, CG-SDT and long DRX cycle | | 2Rx
4Rx | | | | +| CONNECTED state mobility | | | | | | | | | +| Handover | | | | | | | | | +| NR handover with known target cell | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | | | +| NR handover with unknown target cell | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | | | +| NR-FR1 handover with unknown target cell | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | | | +| NR – E-UTRA handover with known target cell | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | | | +| NR – E-UTRA handover with unknown target | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | | | +| NR – UTRAN FDD handover with known | Rel-16 | C096 | UEs supporting 5GS NR SA FR1 and UTRAN FDD | | 2Rx
4Rx | | | | +| NR synchronous DAPS handover | Rel-16 | C101 | UEs supporting 5GS NR SA FR1 and intra-frequency DAPS handover | | 2Rx
4Rx | | | | +| NR asynchronous DAPS handover | Rel-16 | C102 | UEs supporting 5GS NR SA FR1 and intra-frequency async DAPS handover | | 2Rx
4Rx | | | | + +| TC Title | Release | Applicability | | Additional Information | Branch | | +|-----------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------|--| +| | | Condition | Comment | | | | +| R1 Intra-band inter-frequency synchronous handover | Rel-16 | C107 | UEs supporting 5GS NR SA FR1 and inter-frequency DAPS handover | | 2Rx
4Rx | | +| R1 Intra-band inter-frequency asynchronous handover | Rel-16 | C108 | UEs supporting 5GS NR SA FR1 and inter-frequency async DAPS handover | | 2Rx
4Rx | | +| R1 Inter-band inter-frequency synchronous handover | Rel-16 | C107 | UEs supporting 5GS NR SA FR1 and inter-frequency DAPS handover | For test configuration 1, 2, 4, 5, 9 | 2Rx
4Rx | | +| | | C109 | UEs supporting 5GS NR SA FR1 and inter-frequency DAPS handover and supporting different SCSs in source Pcell and inter-frequency target Pcell | For test configuration 3, 6, 7, 8 | 2Rx
4Rx | | +| R1 Inter-band inter-frequency asynchronous handover | Rel-16 | C108 | UEs supporting 5GS NR SA FR1 and inter-frequency async DAPS handover | For test configuration 1, 2, 4, 5, 9 | 2Rx
4Rx | | +| | | C110 | UEs supporting 5GS NR SA FR1 and inter-frequency async DAPS handover and supporting different SCSs in source Pcell and inter-frequency target Pcell | For test configuration 3, 6, 7, 8 | 2Rx
4Rx | | +| Connection mobility control | | | | | | | +| Re-establishment | | | | | | | +| R1 RRC re-establishment | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | +| R1 - FR1 RRC re-establishment | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | +| R1 RRC re-establishment without serving cell | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | +| Access | | | | | | | +| R1 contention based random access | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.3.2.2.1 has been executed. | 2Rx
4Rx | | +| R1 non-contention based random access | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.3.2.2.2 has been executed. | 2Rx
4Rx | | +| R1 2-step contention based random access | Rel-16 | C159 | UEs supporting 5GS NR SA FR1 and 2-step RACH | Test execution not necessary if test 4.3.2.2.3 has been executed. | 2Rx
4Rx | | +| R1 2-step non-contention based random | Rel-16 | C159 | UEs supporting 5GS NR SA FR1 and 2-step RACH | Test execution not necessary if test 4.3.2.2.4 has been executed. | 2Rx
4Rx | | +| Connection release with redirection | | | | | | | +| R1 RRC connection release with redirection | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | | +| R1 - E-UTRA RRC connection release with redirection | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | +| Conditional handover | | | | | | | +| R1 conditional handover | Rel-16 | C105 | UEs supporting 5GS NR SA FR1 and Conditional handover | | 2Rx
4Rx | | +| R1-FR1 conditional handover | Rel-16 | C105 | UEs supporting 5GS NR SA FR1 and Conditional handover | | 2Rx
4Rx | | +| Transmit timing | | | | | | | +| R1 UE transmit timing accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not | 2Rx | | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------|---------|---------------|---------|----------------------------------------------|--------| +| | | Condition | Comment | | | +| | | | | necessary if test 4.4.1.1 has been executed. | 4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|-----------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| accuracy | | | | | | +| advance | | | | | | +| R1 timing advance adjustment accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.4.3.1 has been executed. | 2Rx
4Rx | +| g characteristics | | | | | | +| nk Monitoring | | | | | | +| R1 radio link monitoring out-of-sync test for configured with SSB-based RLM RS in non-DRX | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.5.1.1 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for PCell d with SSB-based RLM RS in non-DRX mode | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.5.1.2 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring out-of-sync test for configured with SSB-based RLM RS in DRX | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.5.1.3 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for PCell d with SSB-based RLM RS in DRX mode | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.5.1.4 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring out-of-sync test for configured with CSI-RS-based RLM RS in non-le | Rel-15 | C037 | UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM | Test execution not necessary if test 4.5.1.5 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for PCell d with CSI-RS-based RLM RS in non-DRX | Rel-15 | C037 | UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM | Test execution not necessary if test 4.5.1.6 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring out-of-sync test for configured with CSI-RS-based RLM RS in DRX | Rel-15 | C037a | UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and long DRX cycle | Test execution not necessary if test 4.5.1.7 has been executed. | 2Rx
4Rx | +| R1 radio link monitoring in-sync test for PCell d with CSI-RS-based RLM RS in DRX mode | Rel-15 | C037a | UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and long DRX cycle | Test execution not necessary if test 4.5.1.8 has been executed. | 2Rx
4Rx | +| adio link monitoring out-of-sync Test for PCell d with CSI-RS-based RLM for UE fulfilling measurement criterion | Rel-17 | C037b | UEs supporting 5GS NR SA FR1 and long DRX cycle and CSI-RS-based RLM and RLM relaxation criteria rlm-Relaxation-r17 | | 2Rx
4Rx | +| ion | | | | | | +| R1 interruptions during measurements on ed NR SCC | Rel-15 | C031 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) | | 2Rx
4Rx | +| ivation and deactivation delay | | | | | | +| R1 SCell activation and deactivation of known non-DRX for 160ms SCell measurement cycle | Rel-15 | C031 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) | | 2Rx
4Rx | +| R1 SCell activation and deactivation of known non-DRX for 640ms SCell measurement cycle | Rel-15 | C031 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) | | 2Rx
4Rx | +| R1 SCell activation and deactivation of SCell in non-DRX | Rel-15 | C031 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) | | 2Rx
4Rx | +| R1 direct SCell activation at SCell addition of Cell | Rel-16 | C244 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) and direct SCell activation | | 2Rx
4Rx | +| R1 direct SCell activation at handover with Cell | Rel-16 | C244 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) and direct SCell activation | | 2Rx
4Rx | +| R1 fast SCell Activation of known SCell in for 160ms SCell measurement cycle | Rel-17 | C270 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) and fast SCell activation | NOTE 1 | 2Rx
4Rx | +| R1 fast SCell Activation of known SCell in for 640ms SCell measurement cycle | Rel-17 | C270 | UEs supporting 5GS NR SA FR1 and CA (2DL CA) and fast SCell activation | NOTE 1 | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|---------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| Carrier RRC reconfiguration delay | | | | | | +| R1 UE UL carrier RRC reconfiguration delay | Rel-15 | C002 | UEs supporting 5GS NR SA FR1 and SUL | Test execution not necessary if test 4.5.4.1 has been executed. | 2Rx
4Rx | +| Recovery procedures | | | | | | +| R1 SSB-based beam failure detection and recovery in non-DRX | Rel-15 | C084 | UEs supporting 5GS NR SA FR1 and link recovery | Test execution not necessary if test 4.5.5.1 has been executed. | 2Rx
4Rx | +| R1 SSB-based beam failure detection and recovery in DRX | Rel-15 | C084a | UEs supporting 5GS NR SA FR1 and long DRX cycle and link recovery | Test execution not necessary if test 4.5.5.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based beam failure detection and recovery in non-DRX | Rel-15 | C085 | UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM and link recovery | Test execution not necessary if test 4.5.5.3 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based beam failure detection and recovery in DRX | Rel-15 | C085a | UEs supporting 5GS NR SA FR1 and long DRX cycle and CSI-RS-based RLM and link recovery | Test execution not necessary if test 4.5.5.4 has been executed. | 2Rx
4Rx | +| R1 Scell CSI-RS-based beam failure and SSB-based link recovery in non-DRX | Rel-16 | C173 | UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM and SSB-based link recovery on Scell | Test execution not necessary if test 4.5.5.5 has been executed. | 2Rx
4Rx | +| R1 Scell CSI-RS-based beam failure and SSB-based link recovery in DRX | Rel-16 | C174 | UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM and SSB-based link recovery on Scell and long DRX cycle | Test execution not necessary if test 4.5.5.6 has been executed. | 2Rx
4Rx | +| BWP switch delay | | | | | | +| DCI and timer-based active BWP switch | | | | | | +| R1-FR1 DCI-based DL active BWP switch in | Rel-15 | C066a | UEs supporting 5GS NR SA FR1 and (DCI and timer based active BWP switching delay type1 or type2) and (Support of BWP adaptation upto2 or upto4) and 2DL CA | | 2Rx
4Rx | +| R1 DCI-based DL active BWP switch in non- | Rel-15 | C066 | UEs supporting 5GS NR SA FR1 and (DCI and timer based active BWP switching delay type1 or type2) and (Support of BWP adaptation upto2 or upto4) | | 2Rx
4Rx | +| DCI-based active BWP switch | | | | | | +| R1 RRC-based DL active BWP switch in non- | Rel-15 | C066b | UEs supporting 5GS NR SA FR1 and (Support of BWP adaptation upto2 or upto4) | | 2Rx
4Rx | +| Simultaneous DCI-based and Timer-based Active BWP Switch on multiple CCs | | | | | | +| R1-FR1 DCI-based DL active BWP switch in | Rel-16 | C066e | UEs supporting 5GS NR SA FR1, incremental delay for DCI and timer based active BWP switching on multiple CCs and 3DL CA | NOTE 1 | 2Rx
4Rx | +| Simultaneous RRC-based Active BWP Switch on multiple CCs | | | | | | +| Simultaneous RRC-based BWP switch on multiple CCs | Rel-16 | C066d | UEs supporting 5GS NR SA FR1, incremental delay for DCI and timer based active BWP switching on multiple CCs and 2DL CA | NOTE 1 | 2Rx
4Rx | +| Uplink interruptions at switching between two uplink | | | | | | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|-----------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| R1 DL Interruptions at switching between two carriers in FDD-TDD CA | Rel-16 | C051 | UEs supporting 5GS NR SA FR1 and Inter-band CA (2UL CA) and dynamic UL Tx switching | | 2Rx
4Rx | +| R1 DL Interruptions at switching between two carriers in TDD-TDD CA | Rel-16 | C051a | UEs supporting 5GS NR SA FR1 and Inter-band CA (2UL CA) and dynamic UL Tx switching | | 2Rx
4Rx | +| R1 DL interruptions at switching between two carriers in TDD-TDD CA | Rel-17 | C051c | UEs supporting 5GS NR SA FR1 and Inter-band CA (2UL CA) and dynamic UL Tx switching | | 2Rx
4Rx | +| R1 DL interruptions at switching between two bands in TDD-TDD CA | Rel-17 | C051e | UEs supporting 5GS NR SA FR1 and Inter-band/intra-band CA (3UL CA) and dynamic UL Tx switching | | 2Rx
4Rx | +| R1 DL interruptions at switching between two bands with two transmit antenna connectors in CA | Rel-17 | C051f | UEs supporting 5GS NR SA FR1 and Inter-band/intra-band CA (3UL CA) and dynamic UL Tx switching | | 2Rx
4Rx | +| R1 DL interruptions at switching between two bands with two transmit antenna connectors in CA | Rel-17 | C051g | UEs supporting 5GS NR SA FR1 and Inter-band/intra-band CA (3UL CA) and dynamic UL Tx switching | | 2Rx
4Rx | +| Specific CBW change | | | | | | +| Specific CBW change on PCell in FR1 in non-DRX | Rel-16 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | +| Measurement procedures | | | | | | +| Frequency measurements | | | | | | +| R1 event-triggered reporting without gap in | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.6.1.1 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting without gap in | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.6.1.2 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting with gap in non- | Rel-15 | C041 | UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM and BWP operation without bandwidth restriction | Test execution not necessary if test 4.6.1.3 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting with gap in DRX | Rel-15 | C041a | UEs supporting 5GS NR SA FR1, CSI-RS-based RLM, BWP operation without bandwidth restriction and long DRX cycle | Test execution not necessary if test 4.6.1.4 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting without gap in with SSB index reading | Rel-15 | C024 | UEs supporting 5GS NR FDD SA FR1 | Test execution not necessary if test 4.6.1.5 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting with gap in non-SSB index reading | Rel-15 | C041b | UEs supporting 5GS NR FDD SA FR1 and CSI-RS-based RLM and BWP operation without bandwidth restriction | Test execution not necessary if test 4.6.1.6 has been executed. | 2Rx
4Rx | +| R1 event-triggered reporting without gap in UE configured with highSpeedMeasFlag-r16 | Rel-15 | C052 | UEs supporting 5GS NR SA FR1 and measurement enhancements in HST | Test execution not necessary if test 4.6.1.7 has been executed. | 2Rx
4Rx | +| R1 event triggered reporting without gap in UE configured with highSpeedMeasCA-Scell- | Rel-16 | C052b | UEs supporting 5GS NR SA FR1 and CA measurement enhancements in HST | Test execution not necessary if test 4.6.1.8 has been executed. | 2Rx
4Rx | +| Frequency measurements | | | | | | +| R1-FR1 event-triggered reporting in non-DRX | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.6.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 event-triggered reporting in DRX | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.6.2.2 has been executed. | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------|---------|---------------|---------|------------------------|--------| +| | | Condition | Comment | | | +| | | | | has been executed. | 4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|-----------------------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| R1-FR1 event-triggered reporting in non-DRX time index detection | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.6.2.5 has been executed. | 2Rx
4Rx | +| R1-FR1 event-triggered reporting in DRX with index detection | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.6.2.6 has been executed. | 2Rx
4Rx | +| R1-FR1 event triggered reporting tests with mandatory gap pattern | Rel-16 | C001 | UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx
4Rx | +| R1-FR1 event triggered reporting tests for out gap when DRX is used | Rel-16 | C287 | UEs supporting 5GS NR SA FR1 and long DRX cycle and inter-frequency SSB based measurements without measurement gaps | NOTE 1 | 2Rx
4Rx | +| R1-FR1 event triggered reporting tests for out gap when DRX is not used | Rel-16 | C286 | UEs supporting 5GS NR SA FR1 and inter-frequency SSB based measurements without measurement gaps | NOTE 1 | 2Rx
4Rx | +| R1-FR1 event triggered reporting tests for SB time index detection in DRX for UE configured with highSpeedMeasInterFreq-r17 | Rel-16 | C052c | UEs supporting 5GS NR SA FR1 and inter-freq measurement enhancements in HST | Test execution not necessary if test 4.6.2.9 has been executed. | 2Rx
4Rx | +| Inter-RAT measurements | | | | | | +| R1 – E-UTRAN event-triggered reporting in | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRAN | | 2Rx
4Rx | +| R1 – E-UTRAN event-triggered reporting in | Rel-15 | C025a | UEs supporting 5GS NR SA FR1, E-UTRAN and long DRX cycle | | 2Rx
4Rx | +| R1 – E-UTRAN event-triggered reporting in UE configured with highSpeedMeasFlag-r16 | Rel-15 | C025c | UEs supporting 5GS NR SA FR1 and E-UTRAN, long DRX cycle and E-UTRA inter-RAT measurement enhancements in HST | | 2Rx
4Rx | +| Inter-RAT measurement for beam reporting | | | | | | +| R1 SSB-based L1-RSRP measurement in | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.6.4.1 has been executed. | 2Rx
4Rx | +| R1 SSB-based L1-RSRP measurement in | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.6.4.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based L1-RSRP measurement in | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.6.4.3 has been executed. | 2Rx
4Rx | +| R1 CSI-RS-based L1-RSRP measurement in | Rel-15 | C001b | UEs supporting 5GS NR SA FR1 and long DRX cycle | Test execution not necessary if test 4.6.4.4 has been executed. | 2Rx
4Rx | +| R1 SSB-based L1-RSRP measurement in UE configured with highSpeedMeasFlag-r16 | Rel-15 | C001f | UEs supporting 5GS NR SA FR1, long DRX cycle and intra-NR measurement enhancements in HST | Test execution not necessary if test 4.6.4.5 has been executed. | 2Rx
4Rx | +| Inter-RAT measurement for beam reporting | | | | | | +| R1 – UTRAN event-triggered reporting in non- | Rel-16 | C096 | UEs supporting 5GS NR SA FR1 and UTRAN FDD | | 2Rx
4Rx | +| Inter-RAT measurement for beam reporting | | | | | | +| R1 CSI-RS based CMR and no dedicated IMR measurement in DRX | Rel-16 | C144 | UEs supporting 5GS NR SA FR1 and long DRX cycle and L1-SINR measurement based on CSI-RS as CMR without dedicated IMR configured | | 2Rx
4Rx | +| R1 SSB based CMR and dedicated IMR L1-RSRP measurement in non-DRX | Rel-16 | C145 | UEs supporting 5GS NR SA FR1 and L1-SINR measurement based on SSB as CMR and dedicated CSI-RS as | | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------|---------|---------------|---------|------------------------|--------| +| | | Condition | Comment | | | +| | | | IMR | | | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|-------------------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| | | Condition | Comment | | | +| R1 CSI-RS based CMR and dedicated IMR measurement in non-DRX | Rel-16 | C146 | UEs supporting 5GS NR SA FR1 and L1-SINR measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | | 2Rx
4Rx | +| e CA/DC Measurements | | | | | | +| R1 Idle mode CA/DC measurement for FR1 | Rel-16 | C031a | UEs supporting 5GS NR SA FR1 and CA (2DL CA) and NR SSB measurements in RRC_IDLE/RRC_INACTIVE | | | +| e inter-RAT CA/DC Measurements | | | | | | +| R1 Idle Mode measurements of inter-RAT CA cells for early reporting | Rel-16 | C031b | UEs supporting NE-DC FR1 and E-UTRA measurements in RRC_IDLE/RRC_INACTIVE | | | +| event triggered reporting tests with Pre-MG | | | | | | +| R1 event triggered reporting tests with bus activation/deactivation Pre-MG | Rel-17 | C259 | UEs supporting 5GS NR SA FR1, BWP adaptation of at least 2 BWPs, BWP operation without bandwidth restriction, DCI and timer-based active BWP switching delay Type1 or Type2, CSI-RS-based RLM and preconfiguredUE-AutonomousMeasGap-r17 | | 2Rx
4Rx | +| R1 event triggered reporting tests with pre-d measurement gaps and network-controlled /deactivation | Rel-17 | C260 | UEs supporting 5GS NR SA FR1, BWP adaptation of at least 2 BWPs, BWP operation without bandwidth restriction, DCI and timer-based active BWP switching delay Type1 or Type2, CSI-RS-based RLM and preconfiguredNW-ControlledMeasGap-r17 | | 2Rx
4Rx | +| event triggered reporting tests with concurrent | | | | | | +| R1 event-triggered reporting for concurrent -overlap with SSB-based measurements in -frequency layers | Rel-17 | C264 | UEs supporting 5GS NR SA FR1 and more than 1 per-UE measurement gap configurations | | 2Rx
4Rx | +| R1 event-triggered reporting for concurrent tially-overlap with SSB-based measurements -er-frequency layers | Rel-17 | C264 | UEs supporting 5GS NR SA FR1 and more than 1 per-UE measurement gap configurations | | 2Rx
4Rx | +| R1 NR - E-UTRAN and NR FR1 concurrent gered reporting in non-DRX in FR1 | Rel-17 | C265 | UEs supporting 5GS NR SA FR1 and E-UTRA and more than 1 per-UE measurement gap configurations and the configurations of E-UTRAN measurement objectives associated with more than 1 concurrent measurement gaps | | 2Rx
4Rx | +| R1 event triggered reporting tests for PRS measurement in FR1 without SSB time index when DRX is not used | Rel-17 | C266 | UEs supporting 5GS NR SA FR1 and more than 1 per-UE measurement gap configurations and two independent measurement gap configurations for FR1 and FR2 for PRS measurement | | 2Rx
4Rx | +| event triggered reporting tests with NCSG | | | | | | +| R1 event-triggered reporting tests with NCSG -h-DRX in FR1 | Rel-17 | C253 | UEs supporting 5GS NR SA FR1, CSI-RS-based RLM, BWP operation without bandwidth restriction, NR only NCSG patterns and reporting of | For sub-test 1 | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| | | Condition | Comment | | | +| | | | NCSG requirement information but don't support per-FR NCSG | | | +| | | C254 | UEs supporting 5GS NR SA FR1, CSI-RS-based RLM, BWP operation without bandwidth restriction, per-FR NCSG, reporting of NCSG requirement information and NR only NCSG patterns | For sub-test 2 | 2Rx
4Rx | +| FR1 event-triggered reporting tests for FR1 NCSG for inter-frequency measurement | Rel-17 | C255 | UEs supporting 5GS NR SA FR1, NR only NCSG patterns and reporting of NCSG requirement information but don't support per-FR NCSG | For sub-test 1 | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|-------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| | | C256 | UEs supporting 5GS NR SA FR1, per-FR NCSG, reporting of NCSG requirement information and NR only NCSG patterns | For sub-test 2 | 2Rx
4Rx | +| R1 NR - E-UTRAN event-triggered reporting RX in FR1 with NCSG | Rel-17 | C257 | UEs supporting 5GS NR SA FR1, E-UTRAN, reporting of NCSG requirement information for E-UTRA and NCSG patterns | | 2Rx
4Rx | +| R1 Event triggered reporting on SCC with Red SCell test with per-UE NCSG under non- | Rel-17 | C258 | UEs supporting 5GS NR SA FR1, CA (2DL CA), reporting of NCSG requirement information and NR only NCSG patterns | | 2Rx
4Rx | +| RTT time difference measurement for position delay compensation | | | | | | +| RTT time difference measurement with PRS for Rx-Tx PDC in FR1 SA | Rel-17 | C212 | UEs supporting 5GS NR SA FR1 and RTT-based PDC for Rx-Tx measurement with PRS | | 2Rx | +| RTT time difference measurement for position delay compensation with TRS | | | | | | +| RTT time difference measurement with TRS for Rx-Tx PDC in FR1 SA | Rel-17 | C213 | UEs supporting 5GS NR SA FR1 and RTT-based PDC for Rx-Tx measurement with TRS | | 2Rx | +| Measurement performance requirements | | | | | | +| Frequency measurements | | | | | | +| R1 SS-RSRP absolute measurement | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.1.1.1 has been executed. | 2Rx
4Rx | +| R1 SS-RSRP relative measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.1.1.2 has been executed. | 2Rx
4Rx | +| Frequency measurements | | | | | | +| R1-FR1 SS-RSRP absolute measurement | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.1.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-RSRP relative measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.1.2.2 has been executed. | 2Rx
4Rx | +| QoS measurements | | | | | | +| R1 SS-RSRQ measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-RSRQ absolute measurement | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.2.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-RSRQ relative measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.2.2.2 has been executed. | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------| +| | | Condition | Comment | | | +| R1 SS-SINR measurement accuracy | Rel-15 | C034 | UEs supporting 5GS NR SA FR1 and SS-SINR-meas | Test execution not necessary if test 4.7.3.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-SINR absolute measurement | Rel-15 | C034 | UEs supporting 5GS NR SA FR1 and SS-SINR-meas | Test execution not necessary if test 4.7.3.2.1 has been executed. | 2Rx
4Rx | +| R1-FR1 SS-SINR relative measurement | Rel-15 | C034 | UEs supporting 5GS NR SA FR1 and SS-SINR-meas | Test execution not necessary if test 4.7.3.2.2 has been executed. | 2Rx
4Rx | +| for beam reporting | | | | | | +| R1 SSB based L1-RSRP absolute measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.4.1.1 has been executed. | 2Rx
4Rx | +| R1 SSB based L1-RSRP relative measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.4.1.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based L1-RSRP absolute measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.4.2.1 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based L1-RSRP relative measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | Test execution not necessary if test 4.7.4.2.2 has been executed. | 2Rx
4Rx | +| RSRP | | | | | | +| R1 – E-UTRAN RSRP absolute measurement | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | +| RSRQ | | | | | | +| R1 – E-UTRAN RSRQ absolute measurement accuracy | Rel-15 | C001 | UEs supporting 5GS NR SA FR1 | | 2Rx
4Rx | +| RS-SINR | | | | | | +| R1 – E-UTRAN RS-SINR absolute measurement accuracy | Rel-15 | C168 | UEs supporting 5GS NR SA FR1 and E-UTRA RS-SINR measurements | | 2Rx
4Rx | +| | | | | | | +| R1 CSI-RS based CMR and no dedicated configured and CSI-RS resource set with off L1-SINR absolute measurement accuracy | Rel-16 | C132 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on CSI-RS as CMR without dedicated IMR configured | Test execution not necessary if test 4.7.7.1.1 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based CMR and no dedicated configured and CSI-RS resource set with off L1-SINR relative measurement accuracy | Rel-16 | C132 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on CSI-RS as CMR without dedicated IMR configured | Test execution not necessary if test 4.7.7.1.2 has been executed. | 2Rx
4Rx | +| R1 SSB based CMR and dedicated IMR L1-absolute measurement accuracy | Rel-16 | C133 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on SSB as CMR and dedicated CSI-IM as IMR | Test execution not necessary if test 4.7.7.2 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based CMR and dedicated IMR absolute measurement accuracy | Rel-16 | C134 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | Test execution not necessary if test 4.7.7.3.1 has been executed. | 2Rx
4Rx | +| R1 CSI-RS based CMR and dedicated IMR relative measurement accuracy | Rel-16 | C134 | UEs supporting 5GS NR SA FR1 and L1-SINR-measurement based on CSI- | Test execution not necessary if test | 2Rx
4Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------|---------|---------------|---------------------------------------|------------------------------|--------| +| | | Condition | Comment | | | +| | | | RS as CMR and dedicated CSI-IM as IMR | 4.7.7.3.2 has been executed. | | + +branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. + +to the corresponding Sub-Test as defined in TS 38.533 [5]. + +TS 38.533 [5] clause 6 only apply to FR1 non-RedCap UEs. For FR1 RedCap UEs, Test cases in TS 38.533 [5] clause 16 apply. + +**Table 4.2-3a: Void** + +**Table 4.2-4: Applicability of RRM NR SA FR2 conformance test cases, ref. TS 38.533 [5]** + +| TC Title | Release | Applicability | | Additional Information | Branch | +|---------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------|------------------------|--------| +| | | Condition | Comment | | | +| UE state mobility | | | | | | +| Cell re-selection | | | | | | +| NR cell re-selection | FFS | FFS | FFS | | 2Rx | +| NR-FR2 cell re-selection | FFS | FFS | FFS | | 2Rx | +| NR cell re-selection for UE fulfilling low relaxed measurement criterion | Rel-16 | C095 | UEs supporting 5GS NR SA FR2 and relaxed RRM measurement | | 2Rx | +| NR cell re-selection for UE fulfilling not-at-relaxed measurement criterion | Rel-16 | C095 | UEs supporting 5GS NR SA FR2 and relaxed RRM measurement | | 2Rx | +| NR-FR2 cell re-selection for UE fulfilling low relaxed measurement criterion | Rel-16 | C095 | UEs supporting 5GS NR SA FR2 and relaxed RRM measurement | | 2Rx | +| NR-FR2 cell re-selection for UE fulfilling not-at-relaxed measurement criterion | Rel-16 | C095 | UEs supporting 5GS NR SA FR2 and relaxed RRM measurement | | 2Rx | +| NR cell re-selection for power class 6 UE with highSpeedMeasFlagFR2-r17 | Rel-17 | C240 | UEs supporting 5GS NR SA FR2 and intra-frequency RRC_IDLE measurements in HST | NOTE 1 | 2Rx | +| ACTIVE state mobility | | | | | | +| Data Transmission | | | | | | +| Configuration for CG-SDT in FR2 | Rel-17 | C095a | UEs supporting 5GS NR SA FR2 and TA Validation for CG-SDT in FR2 | NOTE 1 | 2Rx | +| CONNECTED state mobility | | | | | | +| Handover | | | | | | +| NR-FR2 synchronous DAPS handover | Rel-16 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| NR-FR2 asynchronous DAPS handover | Rel-16 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| Connection mobility control | | | | | | +| RRC re-establishment | | | | | | +| NR RRC re-establishment | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| NR - FR2 RRC re-establishment | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| NR RRC re-establishment without serving cell | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | +| Random access | | | | | | +| NR contention based random access | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | +| NR non-contention based random access | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | +| NR 2-step non-contention based random access | Rel-16 | C160 | UEs supporting 5GS NR SA FR2 and 2-step RACH | NOTE 1 | 2Rx | +| Connection release with redirection | | | | | | +| NR-FR2 RRC connection release with redirection | FFS | FFS | FFS | | 2Rx | +| Conditional Handover | | | | | | +| NR conditional handover | Rel-16 | C106 | UEs supporting 5GS NR SA FR2 and conditional handover | | 2Rx | +| NR-FR2 conditional handover | Rel-16 | C106 | UEs supporting 5GS NR SA FR2 and conditional handover | NOTE 1 | 2Rx | +| Timing advance | | | | | | +| UE transmit timing accuracy | | | | | | +| NR UE transmit timing accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| Timing advance adjustment accuracy | | | | | | +| NR timing advance adjustment accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| Link characteristics | | | | | | +| Link Monitoring | | | | | | +| Link Monitoring Out-of-sync Test for FR2 PCell with SSBbased RLM RS in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------|------------------------|--------| +| | | Condition | Comment | | | +| Radio Link Monitoring In-sync Test for FR2 PCell configured with SSB-based RLM RS in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | +| Radio Link Monitoring Out-of-sync Test for FR2 PCell configured with SSB-based RLM RS in DRX mode | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| Radio Link Monitoring In-sync Test for FR2 PCell configured with SSB-based RLM RS in DRX mode | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| FR2 Radio Link Monitoring Out-of-sync Test configured with CSI-RS-based RLM RS in non-DRX mode | Rel-15 | C164 | UEs supporting 5GS NR SA FR2 and CSI-RS based RLM | NOTE 1 | 2Rx | +| FR2 Radio Link Monitoring In-sync Test for PCell configured with CSI-RS-based RLM in non-DRX mode | Rel-15 | C164 | UEs supporting 5GS NR SA FR2 and CSI-RS based RLM | NOTE 1 | 2Rx | +| FR2 Radio Link Monitoring Out-of-sync Test for PCell configured with CSI-RS-based RLM RS in DRX mode | Rel-15 | C165 | UEs supporting 5GS NR SA FR2 and CSI-RS based RLM and long DRX cycle | | 2Rx | +| FR2 Radio Link Monitoring In-sync Test for PCell configured with CSI-RS-based RLM in DRX mode | Rel-15 | C165 | UEs supporting 5GS NR SA FR2 and CSI-RS based RLM and long DRX cycle | | 2Rx | +| FR2 radio link monitoring UE scheduling | Rel-15 | C006n | UEs supporting 5GS NR SA FR2 and PDCCH monitoring in any symbol of the slot (with or without span gap) | NOTE 1 | 2Rx | +| Section | | | | | | +| FR2 interruptions during measurements on connected NR SCC | Rel-15 | C006b | UEs supporting 5GS NR SA FR2 and 2DL CA in NR | | 2Rx | +| Activation and deactivation delay | | | | | | +| FR2-FR2 intra-band SCell activation and deactivation delay | FFS | FFS | FFS | NOTE 1 | 2Rx | +| FR1-FR2 inter-band SCell activation and deactivation delay | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| Activation and deactivation for SCell in FR2 configured in non-DRX | Rel-17 | C031c | UEs supporting 5GS NR SA FR2 and 2DL CA in NR | | 2Rx | +| FR2 direct SCell activation at SCell addition of PCell | Rel-16 | C241 | UEs supporting 5GS NR SA FR2 and 2DL CA in NR and direct SCell activation | | 2Rx | +| FR2 direct SCell activation at handover with PCell | Rel-16 | C241 | UEs supporting 5GS NR SA FR2 and 2DL CA in NR and direct SCell activation | | 2Rx | +| FR2 SCell Activation for SCell in FR2 intra-band configured in non-DRX | Rel-17 | C271 | UEs supporting 5GS NR SA intra-band FR2 and 2DL CA in NR and fast SCell activation | NOTE 1 | 2Rx | +| FR2 SCell Activation for known SCell in FR2 configured in non-DRX | Rel-17 | C271a | UEs supporting 5GS NR SA inter-band FR2 and 2DL CA in NR and fast SCell activation | NOTE 1 | 2Rx | +| Failure detection and link recovery | | | | | | +| Resumes | | | | | | +| FR2 SSB-based beam failure detection and recovery in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| FR2 SSB-based beam failure detection and recovery in DRX | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| FR2 CSI-RS-based beam failure detection and recovery in non-DRX | Rel-15 | C164 | UEs supporting 5GS NR SA FR2 and CSI-RS based RLM | | 2Rx | +| FR2 CSI-RS-based beam failure detection and recovery in DRX | Rel-15 | C165 | UEs supporting 5GS NR SA FR2, long DRX cycle and CSI-RS based RLM | | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|-------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------| +| | | Condition | Comment | | | +| R2 scheduling availability restriction during beam failure detection and link recovery RX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| R2 Scell CSI-RS-based beam failure and link recovery in non-DRX | Rel-16 | C147 | UEs supporting 5GS NR SA FR2 and CSI-RS based BFR on Scell | | 2Rx | +| R2 Scell CSI-RS-based beam failure and link recovery in DRX | Rel-16 | C148 | UEs supporting 5GS NR SA FR2 and long DRX cycle and CSI-RS based BFR on Scell | | 2Rx | +| BWP switch delay | | | | | | +| Frequency measurements | | | | | | +| R2 DCI-based DL active BWP switch in non- | FFS | FFS | FFS | NOTE 1 | 2Rx | +| R1-FR2 DCI-based DL active BWP switch in | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| R2 DCI-based DL active BWP switch in non- | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | +| Active BWP switch | | | | | | +| R2 RRC-based DL active BWP switch in | FFS | FFS | FFS | NOTE 1 | 2Rx | +| Addition and release delay | | | | | | +| R2 addition and release delay of known | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| R2 addition and release delay of unknown | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| TCI state switch delay | | | | | | +| R2 MAC-CE based active TCI state switch | | | | | | +| Cell FR2 MAC-CE based active TCI state for a known TCI state | Rel-15 | C006m | UEs supporting 5GS NR SA FR2, maximum number of active TCI states per BWP greater than 1, and maximum number of simultaneously trackable TRS resource sets per CC greater than 1 | | 2Rx | +| R2 RRC based active TCI state switch | | | | | | +| Cell FR2 RRC based active TCI state switch for a known TCI state | Rel-15 | C006m | UEs supporting 5GS NR SA FR2, maximum number of active TCI states per BWP greater than 1, and maximum number of simultaneously trackable TRS resource sets per CC greater than 1 | | 2Rx | +| HST based active TCI state switch for HST scenario | | | | | | +| Cell FR2 HST active TCI state switch for a known TCI state | Rel-17 | C240a | UEs supporting 5GS NR SA FR2 and one-shot large UL timing adjustment in HST | NOTE 1 | 2Rx | +| Carrier RRC reconfiguration delay | | | | | | +| Carrier RRC reconfiguration delay | Rel-17 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| Inter-band PSCell addition and release delay | | | | | | +| Inter-band PSCell addition and Release Delay of PSCell | Rel-17 | C268b | UEs supporting Inter-band NR-DC between FR1 and FR2 and conditional PSCell addition in NR-DC | | | +| Joint TCI state switch delay | | | | | | +| R2 MAC-CE based active joint TCI state | Rel-17 | C281 | UEs supporting 5GS NR SA FR2, and unified TCI state operation with joint DL/UL TCI update for intra-cell beam management | NOTE 1 | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|------------------------------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------| +| | | Condition | Comment | | | +| R2 MAC-CE based active uplink TCI state | Rel-17 | C282 | UEs supporting 5GS NR SA FR2, and unified TCI state operation with separate DL/UL TCI update for intra-cell beam management | NOTE 1 | 2Rx | +| R2 MAC-CE based active downlink TCI state | Rel-17 | C283 | UEs supporting 5GS NR SA FR2, and supporting RRC configuration of additional PCI different from serving cell associated with the TCI state and/or QCL-info, and unified TCI with separate DL/UL TCI update for inter-cell beam management | NOTE 1 | 2Rx | +| R2 PSCell RACH-less based Activation and Deactivation for FR1+FR2 inter-band with target FR2 | Rel-17 | C284 | UEs supporting Inter-band NR-DC between FR1 and FR2 and activation and deactivation on SCG in NR-DC | | | +| Measurement procedures | | | | | | +| Intra-frequency measurements | | | | | | +| R2 event-triggered reporting without gap in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| R2 event-triggered reporting without gap in DRX | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| R2 event-triggered reporting with gap in non-DRX | Rel-15 | C166 | UEs supporting 5GS NR SA FR2, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | +| R2 event-triggered reporting with gap in DRX | Rel-15 | C167 | UEs supporting 5GS NR SA FR2 and long DRX cycle, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | +| R2 event-triggered reporting without gap in non-DRX for UE configured with intraFreqMeasFlagFR2-r17 | Rel-17 | C240 | UEs supporting 5GS NR SA FR2 and intra-frequency measurements in HST | NOTE 1 | 2Rx | +| Intra-frequency measurements | | | | | | +| R2-FR2 event-triggered reporting in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| R2-FR2 event-triggered reporting in DRX | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| R2-FR2 event-triggered reporting in non-DRX with SSB time index detection | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| R2-FR2 event-triggered reporting in DRX with SSB time index detection | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| R1-FR2 event-triggered reporting in non-DRX | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| R1-FR2 event-triggered reporting in DRX | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| R1-FR2 event-triggered reporting in non-DRX with SSB time index detection | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| R1-FR2 event-triggered reporting in DRX with SSB time index detection | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| Beam reporting | | | | | | +| R2 SSB-based L1-RSRP measurement in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| R2 SSB-based L1-RSRP measurement in DRX | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| R2 CSI-RS-based L1-RSRP measurement in non-DRX | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|--------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------| +| | | Condition | Comment | | | +| R2 CSI-RS-based L1-RSRP measurement | Rel-15 | C006a | UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | +| R2 Inter-cell SSB based L1-RSRP measurements on FR2 SCell when DRX is not used | Rel-17 | C006p | UEs supporting 5GS NR SA FR2 and Inter-band CA (2UL CA) | NOTE 1 | 2Rx | +| R2 SSB based L1-RSRP measurement test X is used for power class 6 UE configured SpeedMeasFlagFR2-r17 | Rel-17 | C240 | power class 6 UEs supporting 5GS NR SA FR2 configured and HST intra-frequency measurements | NOTE 1 | 2Rx | +| R2 SRS-RSRP measurement in non-DRX | Rel-16 | C006l | UEs supporting 5GS NR SA FR2 and SRS-RSRP measurements | | 2Rx | +| measurement for beam reporting | | | | | | +| R2 CSI-RS based CMR and no dedicated SINR measurement in non-DRX | Rel-16 | C144a | UEs supporting 5GS NR SA FR2 and L1-SINR measurement based on CSI-RS as CMR without dedicated IMR configured | | 2Rx
4Rx | +| R2 SSB based CMR and dedicated IMR L1-measurement in DRX | Rel-16 | C145a | UEs supporting 5GS NR SA FR2 and long DRX cycle and L1-SINR measurement based on SSB as CMR and dedicated CSI-IM as IMR | | 2Rx
4Rx | +| R2 CSI-RS based CMR and dedicated IMR measurement in DRX | Rel-16 | C146a | UEs supporting 5GS NR SA FR2 and long DRX cycle and L1-SINR measurement based on CSI-RS as CMR and dedicated CSI-RS as IMR | | 2Rx
4Rx | +| time difference measurements for PDC | | | | | | +| R2 UE Rx-Tx time difference measurement with propagation delay compensation using PRS | Rel-17 | C212 | UEs supporting 5GS NR SA FR2 and RTT-based PDC for Rx-Tx measurement with PRS | | 2Rx | +| R2 UE Rx-Tx time difference measurement with propagation delay compensation using TRS | Rel-17 | C213 | UEs supporting 5GS NR SA FR2 and RTT-based PDC for Rx-Tx measurement with TRS | NOTE 1 | 2Rx | +| event triggered reporting tests with Pre-MG | | | | | | +| R2 Intra-frequency measurement test with event triggered reporting tests: with autonomous activation/deactivation of Pre-MG in FR2 | Rel-17 | C290 | UEs supporting 5GS NR SA FR2, BWP adaptation of at least 2 BWPs, BWP operation without bandwidth restriction, DCI and timer-based active BWP switching delay Type1 or Type2, CSI-RS-based RLM and preconfiguredUE-AutonomousMeasGap-r17 | NOTE 1 | 2RX | +| R2 Intra-frequency measurement test with event triggered reporting tests: with network-controlled activation/deactivation of Pre-MG in FR2 | Rel-17 | C291 | UEs supporting 5GS NR SA FR2, BWP adaptation of at least 2 BWPs, BWP operation without bandwidth restriction, DCI and timer-based active BWP switching delay Type1 or Type2, CSI-RS-based RLM and preconfiguredNW-ControlledMeasGap-r17 | NOTE 1 | 2RX | +| event triggered reporting tests with measurement gaps | | | | | | +| R2 event triggered reporting tests For FR2 non-overlapping concurrent MGs for SSB intra-frequency measurements | Rel-17 | C292 | UEs supporting 5GS NR SA FR2 and more than 1 per-UE measurement gap configurations | NOTE 1 | 2RX | +| R2 event triggered reporting tests For FR2 current measurement gaps without SSB time detection when DRX is not used (PCell in FR2) | Rel-17 | C292 | UEs supporting 5GS NR SA FR2 and more than 1 per-UE measurement gap configurations | NOTE 1 | 2RX | +| R2 event triggered reporting tests for FR2 measurement gap with partially overlapping scenario for | Rel-17 | C293 | UEs supporting 5GS NR SA FR2 and more than 1 per-UE measurement | NOTE 1 | 2RX | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|---------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------|------------------------|--------| +| | | Condition | Comment | | | +| ed measurements and PRS-based
ment | | | gap configurations and two independent measurement gap configurations for FR1 and FR2 for PRS measurement | | | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|--------------------------------------------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------| +| | | Condition | Comment | | | +| Event triggered reporting tests with NCSG | | | | | | +| FR2 event triggered reporting test with per-UE under non-DRX | Rel-17 | C294 | UEs supporting 5GS NR SA FR2, CSI-RS-based RLM, BWP operation without bandwidth restriction, per-FR NCSG, reporting of NCSG requirement information and NR only NCSG patterns | NOTE 1 | 2RX | +| FR2 event triggered reporting tests on inter-frequency measurement with NCSG for FR2 when not used (PCell in FR2) | Rel-17 | C295 | UEs supporting 5GS NR SA FR2, reporting of NCSG requirement information and NR only NCSG patterns but not supporting ncsg-MeasGapPerFR-r17 | For sub-test 1
NOTE 1 | 2RX | +| | | C296 | UEs supporting 5GS NR SA FR2, per-FR NCSG, reporting of NCSG requirement information and NR only NCSG patterns | For sub-test 2
NOTE 1 | 2RX | +| FR2 Event triggered reporting test on inter-frequency Scell measurement via NCSG in FR2 in connected state | Rel-17 | C297 | UEs supporting 5GS NR SA FR2, CA (2DL CA), reporting of NCSG requirement information and NR only NCSG patterns | NOTE 1 | 2RX | +| Measurement performance requirements | | | | | | +| P | | | | | | +| FR2 SS-RSRP measurement accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| FR2-FR2 SS-RSRP measurement accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| Frequency measurements between FR1 and FR2 | | | | | | +| FR1-FR2 SS-RSRP measurement accuracy | Rel-15 | N/A | Not recommended due to FR1 – FR2 testability issue | NOTE 1 | 2Rx | +| Q | | | | | | +| FR2 SS-RSRQ measurement accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| FR2-FR2 SS-RSRQ measurement accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| R | | | | | | +| FR2 SS-SINR measurement accuracy | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| FR2-FR2 SS-SINR measurement accuracy | Rel-16 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| Requirements for beam reporting | | | | | | +| FR2 SSB based L1-RSRP measurement | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| FR2 CSI-RS based L1-RSRP measurement | Rel-15 | C006 | UEs supporting 5GS NR SA FR2 | | 2Rx | +| S | | | | | | +| FR2 SRS-RSRP measurement accuracy | Rel-16 | C006i | UEs supporting 5GS NR SA FR2 and SRS-RSRP measurements | | 2Rx | +| T | | | | | | +| FR2 CSI-RS based CMR and no dedicated IMR configured and CSI-RS resource set with no offset L1-SINR measurement accuracy | Rel-16 | C138 | UEs supporting 5GS NR SA FR2 and L1-SINR-measurement based on CSI-RS as CMR without dedicated IMR configured | | 2Rx | +| FR2 SSB based CMR and dedicated IMR L1-RSRP measurement accuracy | Rel-16 | C139 | UEs supporting 5GS NR SA FR2 and L1-SINR-measurement based on SSB as CMR and dedicated CSI-IM as IMR | | 2Rx | +| FR2 CSI-RS based CMR and dedicated IMR measurement accuracy | Rel-16 | C140 | UEs supporting 5GS NR SA FR2 and L1-SINR-measurement based on CSI-RS as CMR and dedicated CSI-IM as IMR | | 2Rx | + +| TC Title | Release | Applicability | | Additional Information | Branch | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|---------|------------------------|--------|--|--|--| +| | | Condition | Comment | | | | | | +| /branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. | | | | | | | | | +| TS 38.533 [5] clause 7 only apply to FR2 non-RedCap UEs. For FR2 RedCap UEs, Test cases in TS 38.533 [5] clause 17 apply. | | | | | | | | | + +Table 4.2-4a: Void + +**Table 4.2-5: Applicability of E-UTRA – NR Inter-RAT conformance test cases, ref. TS 38.533 [5]** + +| TC Title | Release | Applicability | | Additional Information | Branch | | | | +|------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------|------------------------|------------|--|--|--| +| | | Condition | Comment | | | | | | +| UE state mobility | | | | | | | | | +| Cell re-selection | | | | | | | | | +| – NR FR1 cell re-selection to higher priority cell | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | | | +| – NR FR1 Cell reselection to lower priority cell in FR1 for UE configured with SpeedInterRAT-NR-r16 | Rel-15 | C025d | UEs supporting 5GS NR SA FR1 and E-UTRAN and NR inter-RAT measurement enhancement in HST | | 2Rx
4Rx | | | | +| NR Inter-RAT Early Measurement | | | | | | | | | +| – NR FR1 Early Measurement Reporting | Rel-16 | C025f | UEs supporting 5GS NR SA FR1 and E-UTRA and NR FR1 SSB measurements in RRC_IDLE/RRC_INACTIVE | NOTE 1 | 2Rx
4Rx | | | | +| – NR FR2 Early Measurement Reporting | Rel-16 | N/A | not recommended due to E-UTRA/FR1 – FR2 testability issue | NOTE 1 | 2Rx
4Rx | | | | +| CONNECTED state mobility | | | | | | | | | +| Cell handover | | | | | | | | | +| – NR FR1 handover with known target cell | Rel-15 | C025 | UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx
4Rx | | | | +| Measurement procedures | | | | | | | | | +| Measurement delay | | | | | | | | | +| – NR FR1 SFTD measurement delay in non-DRX | Rel-15 | C081 | UEs supporting EN-DC and E-UTRA and SFTD measurements between E-UTRA Pcell and NR neighbour cell | | 2Rx
4Rx | | | | +| – NR FR1 SFTD measurement delay in DRX | Rel-15 | C081a | UEs supporting EN-DC and E-UTRA and long DRX cycle and SFTD measurements between E-UTRA Pcell and NR neighbour cell | | 2Rx
4Rx | | | | +| Event-triggered measurements | | | | | | | | | +| Event-triggered reporting of a NR FR1 neighbour cell without SSB time index detection in non-DRX | Rel-15 | C086 | UEs supporting E-UTRA and NR FR1 measurement | | 2Rx
4Rx | | | | +| Event-triggered reporting of a NR FR1 neighbour cell without SSB time index detection in DRX | Rel-15 | C086a | UEs supporting E-UTRA and NR FR1 measurement and long DRX cycle | | 2Rx
4Rx | | | | +| Event-triggered reporting of a NR FR1 neighbour cell with SSB time index detection in non-DRX | Rel-15 | C086 | UEs supporting E-UTRA and NR FR1 measurement | | 2Rx
4Rx | | | | +| Event-triggered reporting of a NR FR1 neighbour cell with SSB time index detection in DRX | Rel-15 | C086a | UEs supporting E-UTRA and NR FR1 measurement and long DRX cycle | | 2Rx
4Rx | | | | +| Event-triggered reporting of a NR FR2 neighbour cell without SSB time index detection in non-DRX | Rel-15 | N/A | not recommended due to E-UTRA – FR2 testability issue | | 2Rx | | | | +| Event-triggered reporting of a NR FR2 neighbour cell without SSB time index detection in DRX | Rel-15 | N/A | not recommended due to E-UTRA – FR2 testability issue | | 2Rx | | | | +| Event-triggered reporting of a NR FR2 neighbour cell with SSB time index detection in non-DRX | Rel-15 | N/A | not recommended due to E-UTRA – FR2 testability issue | | 2Rx | | | | +| Event-triggered reporting of a NR FR2 neighbour cell with SSB time index detection in DRX | Rel-15 | N/A | not recommended due to E-UTRA – FR2 testability issue | | 2Rx | | | | +| Event-triggered reporting of a NR FR1 neighbour cell with SSB time index detection in DRX configured with highSpeedInterRAT-NR-r16 | Rel-15 | C025e | UEs supporting 5GS NR SA FR1 and E-UTRAN, long DRX cycle and NR inter-RAT measurement | | 2Rx
4Rx | | | | + +| TC Title | Release | Applicability | | Additional Information | Branch | +|----------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------|------------------------|------------| +| | | Condition | Comment | | | +| | | | enhancement in HST | | | +| Measurement performance requirements | | | | | | +| Measurement accuracy | | | | | | +| - NR FR1 SFTD measurement accuracy | Rel-15 | C081 | UEs supporting EN-DC and E-UTRA and SFTD measurements between E-UTRA Pcell and NR neighbour cell | NOTE 1 | 2Rx
4Rx | +| T | | | | | | +| S | | | | | | +| SS-RSRP absolute measurement accuracy FR1 neighbour cell | Rel-15 | C086 | UEs supporting E-UTRA and NR FR1 measurement | | 2Rx
4Rx | +| SS-RSRP absolute measurement accuracy FR2 neighbour cell | Rel-15 | C080 | UEs supporting E-UTRA and NR FR2 measurement | | 2Rx | +| Q | | | | | | +| SS-RSRQ absolute measurement accuracy FR1 neighbour cell | Rel-15 | C086 | UEs supporting E-UTRA and NR FR1 measurement | | 2Rx
4Rx | +| SS-RSRQ absolute measurement accuracy FR2 neighbour cell | Rel-15 | C080 | UEs supporting E-UTRA and NR FR2 measurement | | 2Rx | +| | | | | | | +| SS-SINR absolute measurement accuracy FR1 neighbour cell | Rel-15 | C086 | UEs supporting E-UTRA and NR FR1 measurement | | 2Rx
4Rx | +| SS-SINR absolute measurement accuracy FR2 neighbour cell | Rel-15 | C080 | UEs supporting E-UTRA and NR FR2 measurement | | 2Rx | + +Branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the bonding test case section in 38.533. + +TS 38.533 [5] clause 8 only apply to non-RedCap UEs. For RedCap UEs, Test cases in TS 38.533 [5] clause 18 apply. + +Table 4.2-6: Applicability of NR sidelink FR1 conformance test cases, ref. TS 38.533 [5] + +| TC Title | Release | Applicability | | Additional Information | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------|------------------------|----| +| | | Condition | Comment | | | +| UE transmit timing | | | | | | +| NR SA FR1 UE transmit timing accuracy for GNSS as synchronization reference source | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| NR SA FR1 UE transmit timing accuracy for SyncRef UE as synchronization reference source | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| NR SA FR1 UE transmit timing accuracy for FR1 NR cell as synchronization reference source | Rel-16 | C079a | UE supporting 5GS FR1 and NR Uu and NR sidelink. | NOTE 1 | 2F | +| Initiation/Cease of S-SSB transmission | | | | | | +| NR SA FR1 initiation/cease of S-SSB transmission for FR1 NR cell as synchronization reference source | Rel-16 | C079a | UE supporting 5GS FR1 and NR Uu and NR sidelink. | NOTE 1 | 2F | +| NR SA FR1 initiation/cease of S-SSB transmission for SyncRef UE as synchronization reference source | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| Synchronization reference selection/reselection | | | | | | +| NR SA FR1 synchronization reference selection/reselection for GNSS configured as the highest priority synchronization reference source | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| NR SA FR1 synchronization reference selection/reselection for FR1 NR Cell configured as the highest priority synchronization reference source | Rel-16 | C079a | UE supporting 5GS FR1 and NR Uu and NR sidelink. | NOTE 1 | 2F | +| L1 SL-RSRP measurements | | | | | | +| NR SA FR1 L1 SL-RSRP measurement for autonomous resource selection/reselection | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| NR SA FR1 L1 SL-RSRP measurement for resource pre-emption | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| NR SA FR1 L1 SL-RSRP measurement for resource re-evaluation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| Congestion control measurement | | | | | | +| NR SA FR1 congestion control measurement for concurrent operation | Rel-16 | C079a | UE supporting 5GS FR1 and NR Uu and NR sidelink. | NOTE 1 | 2F | +| NR SA FR1 congestion control measurement for PC5-only operation | Rel-16 | C079 | UEs supporting 5GS FR1 and NR sidelink | NOTE 1 | 2F | +| Interruption | | | | | | +| NR SA FR1 interruption to WAN due to NR sidelink communication | Rel-16 | C079a | UE supporting 5GS FR1 and NR Uu and NR sidelink. | NOTE 1 | 2F | + +test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. + +**Table 4.2-7: Applicability of RRM NR SA FR1 conformance test cases for RedCap, ref. TS 38.533 [5]** + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.1 | RRC_IDLE state mobility for RedCap | | | | | | | +| 16.1.1 | NR cell re-selection | | | | | | | +| 16.1.1.1 | NR SA FR1 Cell reselection to FR1 intra-frequency NR case for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.1.1.2 | NR SA FR1 Cell reselection to FR1 intra-frequency NR case for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.1.1.3 | NR SA FR1-FR1 Cell reselection to FR1 inter-frequency NR case for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.1.1.4 | NR SA FR1-FR1 Cell reselection to FR1 inter-frequency NR case for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.1.1.5 | NR SA FR1 Cell reselection to FR1 intra-frequency NR case for UE fulfilling stationary relaxed measurement criterion for 1 Rx UE | Rel-17 | C208 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and relaxed RRM measurements | | 1Rx | | +| 16.1.1.6 | NR SA FR1 Cell reselection to FR1 intra-frequency NR case for UE fulfilling stationary relaxed measurement criterion for 2 Rx UE | Rel-17 | C209 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and relaxed RRM measurements | | 2Rx | | +| 16.1.1.7 | NR SA FR1-FR1 Cell reselection to FR1 inter-frequency NR case for UE fulfilling stationary relaxed measurement criterion for 1 Rx UE | Rel-17 | C208 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and relaxed RRM measurements | | 1Rx | | +| 16.1.1.8 | NR SA FR1-FR1 Cell reselection to FR1 inter-frequency NR case for UE fulfilling stationary relaxed measurement criterion for 2 Rx UE | Rel-17 | C209 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and relaxed RRM measurements | | 2Rx | | +| 16.1.2 | NR - E-UTRA cell re-selection | | | | | | | +| 16.1.2.1 | NR SA FR1 - E-UTRA Cell reselection to higher priority E-UTRA for 1RX | Rel-17 | C181 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 1Rx | | +| 16.1.2.2 | NR SA FR1 - E-UTRA Cell reselection to higher priority E-UTRA for 2RX | Rel-17 | C182 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx | | +| 16.1.2.3 | NR SA FR1 - E-UTRA Cell reselection to lower priority E-UTRA for 1RX | Rel-17 | C181 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 1Rx | | +| 16.1.2.4 | NR SA FR1 - E-UTRA Cell | Rel-17 | C182 | 2Rx RedCap UEs | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|----------------------------------------------|---------|---------------|-------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | reselection to lower priority E-UTRA for 2RX | | | supporting 5GS NR SA FR1 and E-UTRA | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.1.2.5 | NR SA FR1 - E-UTRA Cell reselection to lower priority E-UTRA for UE fulfilling stationary relaxed measurement criterion for 1 Rx UE | Rel-17 | C210 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA and relaxed RRM measurements | | 1Rx | | +| 16.1.2.6 | NR SA FR1 - E-UTRA Cell reselection to lower priority E-UTRA for UE fulfilling stationary relaxed measurement criterion for 2 Rx UE | Rel-17 | C211 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA and relaxed RRM measurements | | 2Rx | | +| 16.2 | RRC_INACTIVE state mobility for RedCap | | | | | | | +| 16.2.1 | Configured Grant based Small Data Transmissions for RedCap | | | | | | | +| 16.2.1.1 | NR SA FR1 CG-SDT for 1Rx UE | Rel-17 | C300 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and CG-based small data transmission | NOTE 1 | 1Rx | | +| 16.2.1.2 | NR SA FR1 CG-SDT for 2Rx UE | Rel-17 | C301 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and CG-based small data transmission | NOTE 1 | 2Rx | | +| 16.3 | RRC_CONNECTED state mobility for RedCap | | | | | | | +| 16.3.1 | Handover for RedCap | | | | | | | +| 16.3.1.1 | NR SA FR1 Intra-frequency handover from FR1 to FR1 with known target cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.1.2 | NR SA FR1 Intra-frequency handover from FR1 to FR1 with known target cell for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.1.3 | NR SA FR1 Intra-frequency handover from FR1 to FR1 with unknown target cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.1.4 | NR SA FR1 Intra-frequency handover from FR1 to FR1 with unknown target cell for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.1.5 | NR SA FR1-FR1 Inter-frequency handover from FR1 to FR1 with unknown target cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.1.6 | NR SA FR1-FR1 Inter-frequency handover from | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|-------------------------------------------------|---------|---------------|---------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | FR1 to FR1 with unknown target cell for 2 Rx UE | | | SA FR1 | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|-------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.3.1.7 | NR - E-UTRA handover for 1Rx UE | Rel-17 | C181 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 1Rx | | +| 16.3.1.8 | NR - E-UTRA handover for 2Rx UE | Rel-17 | C182 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx | | +| 16.3.1.9 | NR - E-UTRA handover with unknown target cell for 1 Rx UE | Rel-17 | C181 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 1Rx | | +| 16.3.1.10 | NR - E-UTRA handover with unknown target cell for 2 Rx UE | Rel-17 | C182 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx | | +| 16.3.2 | RRC connection mobility control for RedCap | | | | | | | +| 16.3.2.1 | RRC re-establishment for RedCap | | | | | | | +| 16.3.2.1.1 | NR SA FR1 Intra-frequency RRC Re-establishment in FR1 for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.2.1.2 | NR SA FR1 Intra-frequency RRC Re-establishment in FR1 for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.2.1.3 | NR SA FR1-FR1 Inter-frequency RRC Re-establishment in FR1 for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.2.1.4 | NR SA FR1-FR1 Inter-frequency RRC Re-establishment in FR1 for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.2.1.5 | NR SA FR1 Intra-frequency RRC Re-establishment in FR1 for 1 Rx UE without serving cell timing | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.2.1.6 | NR SA FR1 Intra-frequency RRC Re-establishment in FR1 for 2 Rx UE without serving cell timing | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.2.2 | Random access for RedCap | | | | | | | +| 16.3.2.2.1 | NR SA FR1 4-step RA type contention based random access test in FR1 for NR standalone for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.2.2.2 | NR SA FR1 4-step RA type contention based random access test in FR1 for NR standalone for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.2.2.3 | NR SA FR1 4-step RA type non-contention based random access test in FR1 for NR standalone for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | Subtest 2: F009 | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|-------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.3.2.2.4 | NR SA FR1 4-step RA type non-contention based random access test in FR1 for NR standalone for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | Subtest 2: F010 | +| 16.3.2.2.5 | NR SA FR1 2-step RA type contention based random access test in FR1 for NR standalone for 1 Rx UE | Rel-17 | C187 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and 2-step RACH | | 1Rx | | +| 16.3.2.2.6 | NR SA FR1 2-step RA type contention based random access test in FR1 for NR standalone for 2 Rx UE | Rel-17 | C188 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and 2-step RACH | | 2Rx | | +| 16.3.2.2.7 | NR SA FR1 2-step RA type non-contention based test in FR1 for NR standalone for 1 RX UE | Rel-17 | C187 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and 2-step RACH | | 1Rx | | +| 16.3.2.2.8 | NR SA FR1 2-step RA type non-contention based test in FR1 for NR standalone for 2 RX UE | Rel-17 | C188 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and 2-step RACH | | 2Rx | | +| 16.3.2.3 | RRC connection release with redirection for RedCap | | | | | | | +| 16.3.2.3.1 | NR SA FR1-FR1 Redirection from NR in FR1 to NR in FR1 for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.3.2.3.2 | NR SA FR1-FR1 Redirection from NR in FR1 to NR in FR1 for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.3.2.3.3 | NR SA FR1-FR1 Redirection from NR in FR1 to E-UTRAN for 1 Rx UE | Rel-17 | C181 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 1Rx | | +| 16.3.2.3.4 | NR SA FR1-FR1 Redirection from NR in FR1 to E-UTRAN for 2 Rx UE | Rel-17 | C182 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 2Rx | | +| 16.4 | Timing for RedCap | | | | | | | +| 16.4.1 | UE transmit timing for RedCap | | | | | | | +| 16.4.1.1 | NR SA FR1 NR UE Transmit Timing Test for FR1 for 1Rx RedCap UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | Subtest 2: F011 | +| 16.4.1.2 | NR SA FR1 NR UE Transmit Timing Test for FR1 for 2Rx RedCap UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | Subtest 2: F012 | +| 16.4.2 | UE timer accuracy for RedCap | | | | | | | +| 16.4.3 | Timing advance for RedCap | | | | | | | +| 16.4.3.1 | NR SA FR1 SA FR1 timing advance adjustment accuracy for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.4.3.2 | NR SA FR1 SA FR1 timing | Rel-17 | C184 | 2Rx RedCap UEs | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|-----------------------------------------|---------|---------------|--------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | advance adjustment accuracy for 2 Rx UE | | | supporting 5GS NR SA FR1 | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|-----------------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.5 | Signalling characteristics for RedCap | | | | | | | +| 16.5.1 | Radio Link Monitoring for RedCap | | | | | | | +| 16.5.1.1 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.5.1.2 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.5.1.3 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.5.1.4 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.5.1.5 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in DRX mode for 1 Rx UE | Rel-17 | C188 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.5.1.6 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in DRX mode for 2 Rx UE | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 2Rx | | +| 16.5.1.7 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with SSB-based RLM RS in DRX mode for 1 Rx UE | Rel-17 | C188 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.5.1.8 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with SSB-based RLM RS in DRX mode for 2 Rx UE | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 2Rx | | +| 16.5.1.9 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode for 1 Rx UE | Rel-17 | C214 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM | | 1Rx | | +| 16.5.1.10 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with CSI-RS-based RLM in | Rel-17 | C215 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|--------------------------|---------|---------------|---------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | non-DRX mode for 2 Rx UE | | | | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.5.1.11 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode for 1 Rx UE | Rel-17 | C214 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM | | 1Rx | | +| 16.5.1.12 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode for 2 Rx UE | Rel-17 | C215 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and CSI-RS-based RLM | | 2Rx | | +| 16.5.1.13 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with CSI-RS-based RLM in DRX mode for 1 Rx UE | Rel-17 | C216 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and long DRX cycle | | 1Rx | | +| 16.5.1.14 | NR SA FR1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with CSI-RS-based RLM in DRX mode for 2 Rx UE | Rel-17 | C217 | 2Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and long DRX cycle | | 2Rx | | +| 16.5.1.15 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with CSI-RS-based RLM in DRX mode for 1 Rx UE | Rel-17 | C216 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and long DRX cycle | | 1Rx | | +| 16.5.1.16 | NR SA FR1 Radio Link Monitoring In-sync Test for FR1 PCell configured with CSI-RS-based RLM in DRX mode for 2 Rx UE | Rel-17 | C217 | 2Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and long DRX cycle | | 2Rx | | +| 16.5.2 | Beam Failure Detection and Link recovery procedures for RedCap | | | | | | | +| 16.5.2.1 | NR SA FR1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with SSB-based BFD and LR in non-DRX mode for 1 Rx UE | Rel-17 | C191 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and link recovery | | 1Rx | | +| 16.5.2.2 | NR SA FR1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with SSB-based BFD and LR in non-DRX mode for 2 Rx UE | Rel-17 | C192 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and link recovery | | 2Rx | | +| 16.5.2.3 | NR SA FR1 SSB-based beam failure detection and link recovery in DRX mode for 1 Rx UE | Rel-17 | C272 | 1Rx RedCap UEs supporting 5GS NR SA FR1, SSB-based RLM, long DRX cycle and link recovery | | 1Rx | | +| 16.5.2.4 | NR SA FR1 SSB-based beam failure detection and link recovery in DRX mode | Rel-17 | C273 | 2Rx RedCap UEs supporting 5GS NR SA FR1, SSB-based | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|-------------|---------|---------------|---------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | for 2 Rx UE | | | RLM, long DRX cycle and link recovery | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.5.2.5 | NR SA FR1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with CSI-RS-based BFD and LR in non-DRX mode for 1 Rx UE | Rel-17 | C218 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and link recovery | | 1Rx | | +| 16.5.2.6 | NR SA FR1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with CSI-RS-based BFD and LR in non-DRX mode for 2 Rx UE | Rel-17 | C219 | 2Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and link recovery | | 2Rx | | +| 16.5.2.7 | NR SA FR1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with CSI-RS-based BFD and LR in DRX mode for 1 Rx UE | Rel-17 | C220 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM, long DRX cycle and link recovery | | 1Rx | | +| 16.5.2.8 | NR SA FR1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with CSI-RS-based BFD and LR in DRX mode for 2 Rx UE | Rel-17 | C221 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM, long DRX cycle and link recovery | | 2Rx | | +| 16.5.3 | Active BWP switch delay for RedCap | | | | | | | +| 16.5.3.1 | DCI-based and time-based active BWP switch for RedCap | | | | | | | +| 16.5.3.1.1 | NR SA FR1 DCI-based DL active BWP switch in non-DRX for 1 Rx UE | Rel-17 | C274 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and (DCI and timer based active BWP switching delay type1 or type2) and (Support of BWP adaptation upto2 or upto4) | | 1Rx | | +| 16.5.3.1.2 | NR SA FR1 DCI-based DL active BWP switch in non-DRX for 2 Rx UE | Rel-17 | C275 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and (DCI and timer based active BWP switching delay type1 or type2) and (Support of BWP adaptation upto2 or upto4) | | 2Rx | | +| 16.5.3.2 | RRC-based active BWP switch for RedCap | | | | | | | +| 16.5.3.2.1 | NR SA FR1 RRC-based DL active BWP switch in non-DRX for 1 Rx UE | Rel-17 | C276 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and (Support of BWP adaptation | | 1Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|----------|---------|---------------|-----------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | | | | upto2 or upto4) | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|--------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.5.3.2.2 | NR SA FR1 RRC-based DL active BWP switch in non-DRX for 2 Rx UE | Rel-17 | C277 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and (Support of BWP adaptation upto2 or upto4) | | 2Rx | | +| 16.5.4 | UE specific CBW change for RedCap | | | | | | | +| 16.5.4.1 | NR SA FR1 UE specific CBW change on PCell in non-DRX for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.5.4.2 | NR SA FR1 UE specific CBW change on PCell in non-DRX for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6 | Measurement procedure for RedCap | | | | | | | +| 16.6.1 | Intra-frequency Measurements for RedCap | | | | | | | +| 16.6.1.1 | NR SA FR1 Event triggered reporting tests without gap under non-DRX for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.1.2 | NR SA FR1 Event triggered reporting tests without gap under non-DRX for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6.1.3 | NR SA FR1 Event triggered reporting tests without gap under DRX for 1 Rx UE | Rel-17 | C189 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.6.1.4 | NR SA FR1 Event triggered reporting tests without gap under DRX for 2 Rx UE | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 2Rx | | +| 16.6.1.5 | NR SA FR1 Event triggered reporting tests with per-UE gaps under non-DRX for 1 Rx UE | Rel-17 | C222 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 1Rx | | +| 16.6.1.6 | NR SA FR1 Event triggered reporting tests with per-UE gaps under non-DRX for 2 Rx UE | Rel-17 | C223 | 2Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | | +| 16.6.1.7 | NR SA FR1 Event triggered reporting tests with per-UE gaps under DRX for 1 Rx UE | Rel-17 | C193 | 1Rx RedCap UEs supporting 5GS NR SA FR1, CSI-RS-based RLM, BWP operation without bandwidth restriction and long DRX cycle | | 1Rx | | +| 16.6.1.8 | NR SA FR1 Event triggered reporting tests with per-UE | Rel-17 | C194 | 2Rx RedCap UEs supporting 5GS NR | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|----------------------------|---------|---------------|------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | gaps under DRX for 2 Rx UE | | | SA FR1, CSI-RS-based RLM, BWP operation without bandwidth restriction and long DRX cycle | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|----------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.6.1.9 | NR SA FR1 Event triggered reporting tests without gap under non-DRX with SSB index reading for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.1.10 | NR SA FR1 Event triggered reporting tests without gap under non-DRX with SSB index reading for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6.1.11 | NR SA FR1 Event triggered reporting tests with per-UE gaps under non-DRX with SSB index reading for 1 Rx UE | Rel-17 | C195 | 1Rx RedCap UEs supporting 5GS NR FDD SA FR1 and CSI-RS-based RLM and BWP operation without bandwidth restriction | | 1Rx | | +| 16.6.1.12 | NR SA FR1 Event triggered reporting tests with per-UE gaps under non-DRX with SSB index reading for 2 Rx UE | Rel-17 | C196 | 2Rx RedCap UEs supporting 5GS NR FDD SA FR1 and CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | | +| 16.6.2 | Inter-frequency measurements for RedCap | | | | | | | +| 16.6.2.1 | NR SA FR1-FR1 Event triggered reporting tests for FR1 without SSB time index detection when DRX is used for 1 Rx UE | Rel-17 | C189 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.6.2.2 | NR SA FR1-FR1 Event triggered reporting tests for FR1 without SSB time index detection when DRX is used for 2 Rx UE | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 2Rx | | +| 16.6.2.3 | NR SA FR1-FR1 Event triggered reporting tests for FR1 without SSB time index detection when DRX is used for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.2.4 | NR SA FR1-FR1 Event triggered reporting tests for FR1 without SSB time index detection when DRX is used for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6.2.5 | NR SA FR1-FR1 Event triggered reporting tests for FR1 with SSB time index detection when DRX is not used for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.2.6 | NR SA FR1-FR1 Event triggered reporting tests for FR1 with SSB time index | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|--------------------------------------------|---------|---------------|---------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | detection when DRX is not used for 2 Rx UE | | | | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|------------------------------------------------------------------------------------------------------------------|---------|---------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.6.2.7 | NR SA FR1-FR1 Event triggered reporting tests for FR1 with SSB time index detection when DRX is used for 1 Rx UE | Rel-17 | C189 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.6.2.8 | NR SA FR1-FR1 Event triggered reporting tests for FR1 with SSB time index detection when DRX is used for 2 Rx UE | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 2Rx | | +| 16.6.2.9 | NR SA FR1-FR1 Event triggered reporting tests with additional mandatory gap pattern for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.2.10 | NR SA FR1-FR1 Event triggered reporting tests with additional mandatory gap pattern for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6.2.11 | NR SA FR1-FR1 Event triggered reporting tests for FR1 when DRX is used for 1 Rx UE | Rel-17 | C298 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle and inter-frequency SSB based measurements without measurement gaps | | 1Rx | | +| 16.6.2.12 | NR SA FR1-FR1 Event triggered reporting tests for FR1 when DRX is used for 2 Rx UE | Rel-17 | C299 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle and inter-frequency SSB based measurements without measurement gaps | | 2Rx | | +| 16.6.3 | Inter-RAT measurements for RedCap | | | | | | | +| 16.6.4 | L1-RSRP measurement for beam reporting for RedCap | | | | | | | +| 16.6.4.1 | NR SA FR1 SSB based L1-RSRP measurement when DRX is not used for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.4.2 | NR SA FR1 SSB based L1-RSRP measurement when DRX is not used for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6.4.3 | NR SA FR1 SSB based L1-RSRP measurement when DRX is used for 1 Rx UE | Rel-17 | C189 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.6.4.4 | NR SA FR1 SSB based L1-RSRP measurement when | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|-------------------------|---------|---------------|---------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | DRX is used for 2 Rx UE | | | SA FR1 and long DRX cycle | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|-------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.6.4.5 | NR SA FR1 CSI-RS based L1-RSRP measurement when DRX is not used for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | | 1Rx | | +| 16.6.4.6 | NR SA FR1 CSI-RS based L1-RSRP measurement when DRX is not used for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | | 2Rx | | +| 16.6.4.7 | NR SA FR1 CSI-RS based L1-RSRP measurement when DRX is used for 1 Rx UE | Rel-17 | C189 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 1Rx | | +| 16.6.4.8 | NR SA FR1 CSI-RS based L1-RSRP measurement when DRX is used for 2 Rx UE | Rel-17 | C190 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and long DRX cycle | | 2Rx | | +| 16.6.5 | NR measurements with autonomous gaps | | | | | | | +| 16.6.5.1 | NR SA FR1 intra-frequency CGI identification of NR neighbour cell in FR1 for 1 Rx UE | Rel-17 | C302 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and NR CGI reading using autonomous gap | | 1Rx | | +| 16.6.5.2 | NR SA FR1 intra-frequency CGI identification of NR neighbour cell in FR1 for 2 Rx UE | Rel-17 | C303 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and NR CGI reading using autonomous gap | | 2Rx | | +| 16.6.5.3 | NR SA FR1 Identification of a new CGI of inter-RAT E-UTRA cell using autonomous gaps in NR SA for 1 Rx UE | Rel-17 | C304 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and EUTRA CGI reading using autonomous gap | NOTE 1 | 1Rx | | +| 16.6.5.4 | NR SA FR1 Identification of a new CGI of inter-RAT E-UTRA cell using autonomous gaps in NR SA for 2 Rx UE | Rel-17 | C305 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and EUTRA CGI reading using autonomous gap | NOTE 1 | 2Rx | | +| 16.7 | Measurement Performance requirements for RedCap | | | | | | | +| 16.7.1 | SS-RSRP | | | | | | | +| 16.7.2 | SS-RSRQ | | | | | | | +| 16.7.2.3.1 | NR SA FR1-FR1 Inter-frequency absolute measurement accuracy with FR1 serving cell and FR1 target cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.2.3.2 | NR SA FR1-FR1 Inter-frequency relative measurement accuracy with FR1 serving cell and FR1 target cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|-------------------------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.7.2.4.1 | NR SA FR1-FR1 Inter-frequency absolute measurement accuracy with FR1 serving cell and FR1 target cell for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| 16.7.2.4.2 | NR SA FR1-FR1 Inter-frequency relative measurement accuracy with FR1 serving cell and FR1 target cell for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| 16.7.3 | SS-SINR | | | | | | | +| 16.7.3.1 | NR SA FR1 Intra-frequency measurement accuracy with FR1 serving cell and FR1 target cell for 1 Rx UE | Rel-17 | C306 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and SS-SINR measurement | NOTE 1 | 1Rx | | +| 16.7.3.2 | NR SA FR1 Intra-frequency measurement accuracy with FR1 serving cell and FR1 target cell for 2 Rx UE | Rel-17 | C307 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and SS-SINR measurement | NOTE 1 | 2Rx | | +| 16.7.3.3.1 | NR SA FR1-FR1 Inter-frequency absolute measurement accuracy with FR1 serving cell and FR1 target cell for 1 Rx UE | Rel-17 | C306 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and SS-SINR measurement | NOTE 1 | 1Rx | | +| 16.7.3.3.2 | NR SA FR1-FR1 Inter-frequency relative measurement accuracy with FR1 serving cell and FR1 target cell for 1 Rx UE | Rel-17 | C306 | 1Rx RedCap UEs supporting 5GS NR SA FR1 and SS-SINR measurement | NOTE 1 | 1Rx | | +| 16.7.3.4.1 | NR SA FR1-FR1 Inter-frequency absolute measurement accuracy with FR1 serving cell and FR1 target cell for 2 Rx UE | Rel-17 | C307 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and SS-SINR measurement | NOTE 1 | 2Rx | | +| 16.7.3.4.2 | NR SA FR1-FR1 Inter-frequency relative measurement accuracy with FR1 serving cell and FR1 target cell for 2 Rx UE | Rel-17 | C307 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and SS-SINR measurement | NOTE 1 | 2Rx | | +| 16.7.4 | L1-RSRP measurement for beam reporting | | | | | | | +| 16.7.4.1.1 | NR SA FR1 SSB based L1-RSRP absolute measurement for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.4.1.2 | NR SA FR1 SSB based L1-RSRP relative measurement for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.4.2.1 | NR SA FR1 SSB based L1-RSRP absolute measurement for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| 16.7.4.2.2 | NR SA FR1 SSB based L1-RSRP relative measurement for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 16.7.4.3.1 | NR SA FR1 CSI-RS based L1-RSRP absolute measurement on resource set with repetition off for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.4.3.2 | NR SA FR1 CSI-RS based L1-RSRP relative measurement on resource set with repetition off for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.4.4.1 | NR SA FR1 CSI-RS based L1-RSRP absolute measurement on resource set with repetition off for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| 16.7.4.4.2 | NR SA FR1 CSI-RS based L1-RSRP relative measurement on resource set with repetition off for 2 Rx U | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| 16.7.5 | E-UTRAN RSRP | | | | | | | +| 16.7.5.1 | NR SA FR1 - E-UTRA Measurement accuracy with FR1 serving cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.5.2 | NR SA FR1 - E-UTRA Measurement accuracy with FR1 serving cell for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| 16.7.6 | E-UTRAN RSRQ | | | | | | | +| 16.7.6.1 | NR SA FR1 - E-UTRA Measurement accuracy with FR1 serving cell for 1 Rx UE | Rel-17 | C183 | 1Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 1Rx | | +| 16.7.6.2 | NR SA FR1 - E-UTRA Measurement accuracy with FR1 serving cell for 2 Rx UE | Rel-17 | C184 | 2Rx RedCap UEs supporting 5GS NR SA FR1 | NOTE 1 | 2Rx | | +| NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533.
NOTE 2: Test X refers to the corresponding Sub-Test as defined in TS 38.533 [5]. | | | | | | | | + +**Table 4.2-8: Applicability of RRM NR SA FR2 conformance test cases for RedCap, ref. TS 38.533 [5]** + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 17.1 | RRC_IDLE state mobility for RedCap | | | | | | | +| 17.1 | NR cell re-selection | | | | | | | +| 17.1.1.1 | NR SA FR2 Cell reselection to FR2 intra-frequency NR case for 2 Rx | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.1.1.2 | NR SA FR2-FR2 Cell reselection to FR2 inter-frequency NR case | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.1.1.3 | NR SA FR2 Cell reselection to FR2 intra-frequency NR case for UE fulfilling stationary relaxed measurement criterion for 2 Rx UE | Rel-17 | C239 | RedCap UEs supporting 5GS NR SA FR2 and Rel-17 relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE | | 2Rx | | +| 17.1.1.4 | NR SA FR2-FR2 Cell reselection to FR2 inter-frequency NR case for UE fulfilling stationary mobility relaxed measurement criterion for 2 Rx UE | Rel-17 | C239 | RedCap UEs supporting 5GS NR SA FR2 and Rel-17 relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE | | 2Rx | | +| 17.2 | RRC_INACTIVE state mobility for RedCap | | | | | | | +| 17.2.1 | Configured Grant based Small Data Transmissions for RedCap | | | | | | | +| 17.2.1.1 | NR SA FR2 TA validation for CG-SDT for 2 Rx | Rel-17 | C308 | RedCap UEs supporting 5GS NR SA FR2 and CG-based small data transmission | NOTE 1 | 2Rx | | +| 17.3 | RRC_CONNECTED state mobility for RedCap | | | | | | | +| 17.3.1 | Handover for RedCap | | | | | | | +| 17.3.1.1 | NR SA FR2 Intra-frequency handover from FR2 to FR2; unknown target cell for 2 Rx | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.3.1.2 | NR SA FR2-FR2 Inter-frequency handover from FR2 to FR2; unknown target cell for 2 Rx | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.3.2 | RRC connection mobility control for RedCap | | | | | | | +| 17.3.2.1 | RRC re-establishment for RedCap | | | | | | | +| 17.3.2.1.1 | NR SA FR2 Intra-frequency RRC Re-establishment in FR2 | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.3.2.1.2 | NR SA FR2-FR2 Inter-frequency RRC Re-establishment in FR2 | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.3.2.1.3 | NR SA FR2 Intra-frequency RRC Re-establishment in FR2 without serving cell timing | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.3.2.2 | Random Access for RedCap | | | | | | | +| 17.3.2.2.1 | NR SA FR2 4-step RA type contention based random | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|--------------------------------------|---------|---------------|---------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | access test in FR2 for NR Standalone | | | FR2 | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|-----------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 17.3.2.2.2 | NR SA FR2 4-step RA type non-contention based random access test in FR2 for NR Standalone | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | Subtest 2: F013 | +| 17.3.2.2.3 | NR SA FR2 2-step RA type contention based random access test in FR2 for NR Standalone | Rel-17 | C225 | RedCap UEs supporting 5GS NR SA FR2 and 2-step RACH | NOTE 1 | 2Rx | | +| 17.3.2.2.4 | NR SA FR2 2-step RA type non-contention based random access test in FR2 for NR Standalone | Rel-17 | C225 | RedCap UEs supporting 5GS NR SA FR2 and 2-step RACH | NOTE 1 | 2Rx | | +| 17.3.2.3 | SA: RRC Connection Release with Redirection for RedCap | | | | | | | +| 17.3.2.3.1 | NR SA FR2-FR2 Redirection from NR in FR2 to NR in FR2 | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.4 | Timing for RedCap | | | | | | | +| 17.4.1 | UE transmit timing for RedCap | | | | | | | +| 17.4.1.1 | NR SA FR2 NR UE Transmit Timing Test for FR2 | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.4.2 | UE timer accuracy for RedCap | | | | | | | +| 17.4.3 | Timing advance for RedCap | | | | | | | +| 17.4.3.1 | NR SA FR2 SA FR2 timing advance adjustment accuracy | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.5 | Signalling characteristics for RedCap | | | | | | | +| 17.5.1 | Radio Link Monitoring for RedCap | | | | | | | +| 17.5.1.1 | NR SA FR2 Radio Link Monitoring Out-of-sync Test for FR2 PCell configured with SSB-based RLM RS in non-DRX mode | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.5.1.2 | NR SA FR2 Radio Link Monitoring In-sync Test for FR2 PCell configured with SSB-based RLM RS in non-DRX mode | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.5.1.4 | NR SA FR2 Radio Link Monitoring In-sync Test for FR2 PCell configured with SSB-based RLM RS in DRX mode | Rel-17 | C198 | RedCap UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | | +| 17.5.1.5 | NR SA FR2 Radio Link Monitoring Out-of-sync Test for FR2 PCell configured with CSI-RS-based RLM in non-DRX mode | Rel-17 | C309 | RedCap UEs supporting 5GS NR SA FR2 and CSI-RS-based RLM | NOTE 1 | 2Rx | | +| 17.5.1.6 | NR SA FR2 Radio Link Monitoring In-sync Test for FR2 PCell configured with CSI-RS-based RLM in non-DRX mode | Rel-17 | C309 | RedCap UEs supporting 5GS NR SA FR2 and CSI-RS-based RLM | NOTE 1 | 2Rx | | +| 17.5.1.7 | NR SA FR2 Radio Link Monitoring Out-of-sync Test | Rel-17 | C310 | RedCap UEs supporting 5GS NR SA | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|------------------------------------------------------------|---------|---------------|---------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | for FR2 PCell configured with CSI-RS-based RLM in DRX mode | | | FR2 and CSI-RS-based RLM and long DRX cycle | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 17.5.1.8 | NR SA FR2 Radio Link Monitoring In-sync Test for FR2 PCell configured with CSI-RS-based RLM in DRX mode | Rel-17 | C310 | RedCap UEs supporting 5GS NR SA FR2 and CSI-RS-based RLM and long DRX cycle | NOTE 1 | 2Rx | | +| 17.5.1.9 | NR SA FR2 UE Radio Link Monitoring Scheduling Restrictions on FR2 | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | NOTE 1 | 2Rx | | +| 17.5.2 | Beam Failure Detection and Link recovery procedures for RedCap | | | | | | | +| 17.5.2.3 | NR SA FR2 Beam Failure Detection and Link Recovery Test for FR2 PCell configured with CSI-RS-based BFD and LR in non-DRX mode | Rel-17 | C227 | RedCap UEs supporting 5GS NR SA FR2, CSI-RS based RLM and link recovery | | 2Rx | | +| 17.5.2.4 | NR SA FR2 Beam Failure Detection and Link Recovery Test for FR2 PCell configured with CSI-RS-based BFD and LR in DRX mode | Rel-17 | C228 | RedCap UEs supporting 5GS NR SA FR2, long DRX cycle, CSI-RS based RLM and link recovery | | 2Rx | | +| 17.5.2.5 | NR SA FR2 Scheduling availability restriction during Beam Failure Detection and Link Recovery for FR2 PCell configured with SSB-based BFD and LR in non-DRX mode | Rel-17 | C226 | RedCap UEs supporting 5GS NR SA FR2 and SSB based link recovery | | 2Rx | | +| 17.5.3 | Active BWP switch for RedCap | | | | | | | +| 17.5.4 | Active TCI state switch delay for RedCap | | | | | | | +| 17.5.4.1 | MAC-CE based active TCI state switch for RedCap | | | | | | | +| 17.5.4.1.1 | NR SA FR2 NR PCell FR2 active TCI state switch for a known TCI state | Rel-17 | C311 | RedCap UEs supporting 5GS NR SA FR2, maximum number of active TCI states per BWP greater than 1, and maximum number of simultaneously trackable TRS resource sets per CC greater than 1 | NOTE 1 | 2Rx | | +| 17.5.4.2 | RRP based active TCI state switch for RedCap | | | | | | | +| 17.5.4.2.1 | NR SA FR2 NR PCell FR2 active TCI state switch for a known TCI state | Rel-17 | C311 | RedCap UEs supporting 5GS NR SA FR2, maximum number of active TCI states per BWP greater than 1, and maximum number of simultaneously trackable TRS resource sets per CC greater than 1 | NOTE 1 | 2Rx | | +| 17.6 | Measurement procedure for RedCap | | | | | | | +| 17.6.1 | Intra-frequency Measurements for RedCap | | | | | | | +| 17.6.1.1 | NR SA FR2 Event triggered reporting test without gap | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA | | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | under non-DRX | | | FR2 | | | | +| 17.6.1.2 | NR SA FR2 Event triggered reporting test without gap under DRX | Rel-17 | C198 | RedCap UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | | +| 17.6.1.3 | NR SA FR2 Event triggered reporting test with per-UE gaps under non-DRX | Rel-17 | C238 | RedCap UEs supporting 5GS NR SA FR2, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | | +| 17.6.1.4 | NR SA FR2 Event triggered reporting test with per-UE gaps under DRX | Rel-17 | C229 | RedCap UEs supporting 5GS NR SA FR2, long DRX cycle, CSI-RS-based RLM and BWP operation without bandwidth restriction | | 2Rx | | +| 17.6.3 | L1-RSRP measurement for beam reporting for RedCap | | | | | | | +| 17.6.3.1 | NR SA FR2 SSB based L1-RSRP measurement when DRX is not used | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.6.3.2 | NR SA FR2 SSB based L1-RSRP measurement when DRX is used | Rel-17 | C198 | RedCap UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | | +| 17.6.3.3 | NR SA FR2 CSI-RS based L1-RSRP measurement when DRX is not used | Rel-17 | C197 | RedCap UEs supporting 5GS NR SA FR2 | | 2Rx | | +| 17.6.3.4 | NR SA FR2 CSI-RS based L1-RSRP measurement when DRX is used | Rel-17 | C198 | RedCap UEs supporting 5GS NR SA FR2 and long DRX cycle | | 2Rx | | +| 17.6.4 | NR Measurements with autonomous gaps for RedCap | | | | | | | +| 17.6.4.1 | NR SA FR2 Interfrequency CGI reporting in autonomous gaps test (PCell in FR2) | Rel-17 | C312 | RedCap UEs supporting 5GS NR SA FR2 and NR CGI reading using autonomous gap | NOTE 1 | 2Rx | | +| NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. | | | | | | | | + +**Table 4.2-9: Applicability of E-UTRA – NR Inter-RAT conformance test cases for RedCap, ref. TS 38.533 [5]** + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|------------------------------------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 18.1 | RRC_IDLE state mobility for RedCap | | | | | | | +| 18.1.1 | Inter-RAT NR cell re-selection | | | | | | | +| 18.1.1.1 | E-UTRA - NR SA FR1 E-UTRA Cell reselection to higher priority NR target Cell in FR1 | Rel-17 | TBD | | NOTE 1 | 2Rx | | +| 18.2 | RRC_CONNECTED state mobility for RedCap | | | | | | | +| 18.2.1 | Inter-RAT cell handover for RedCap | | | | | | | +| 18.2.1.1 | E-UTRA - NR SA FR1 E-UTRAN - NR handover in FR1 | Rel-17 | C182 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 2RX | | +| 18.2.2 | RRC connection release with redirection for RedCap | | | | | | | +| 18.2.2.1 | E-UTRA - NR SA FR1 Redirection from E-UTRA to NR SA FR1 for redcap UE | Rel-17 | C182 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA | | 2RX | | +| 18.3 | Measurement procedure for RedCap | | | | | | | +| 18.3.1 | E-UTRA - NR Measurements for RedCap | | | | | | | +| 18.3.1.1 | E-UTRA - NR SA FR1 Event triggered reporting tests for FR1 without SSB time index detection when DRX is not used | Rel-17 | C230 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA but don't support per-FR gap | For sub-test 1 | 2RX | | +| | | | C231 | 2Rx RedCap UEs supporting 5GS NR SA FR1, E-UTRA, per-FR gap and gap pattern #4 | For sub-test 2 | 2RX | | +| 18.3.1.2 | E-UTRA - NR SA FR1 Event triggered reporting tests for FR1 without SSB time index detection when DRX is used | Rel-17 | C232 | 2Rx RedCap UEs supporting 5GS NR SA FR1, E-UTRA and long DRX cycle but don't support per-FR gap | For sub-test 1,2 | 2RX | | +| | | | C233 | 2Rx RedCap UEs supporting 5GS NR SA FR1, E-UTRA, long DRX cycle, per-FR gap and gap pattern #4 | For sub-test 3,4 | 2RX | | +| 18.3.1.3 | E-UTRA - NR SA FR1 Event triggered reporting tests for FR1 with SSB time index detection when DRX is not used | Rel-17 | C230 | 2Rx RedCap UEs supporting 5GS NR SA FR1 and E-UTRA but don't support per-FR gap | For sub-test 1 | 2RX | | +| | | | C231 | 2Rx RedCap UEs supporting 5GS NR SA FR1, E-UTRA, per-FR gap and gap pattern #4 | For sub-test 2 | 2RX | | +| 18.3.1.4 | E-UTRA - NR SA FR1 Event triggered reporting tests for FR1 with SSB time index detection when DRX is used | Rel-17 | C232 | 2Rx RedCap UEs supporting 5GS NR SA FR1, E-UTRA and long DRX cycle but don't support per-FR gap | For sub-test 1,2 | 2RX | | +| | | | C233 | 2Rx RedCap UEs supporting 5GS | For sub-test 3,4 | 2RX | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|---------|---------------|------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | | | | NR SA FR1, E-UTRA, long DRX cycle, per-FR gap and gap pattern #4 | | | | +| 18.3.1.5 | E-UTRA - NR SA FR2 Event triggered reporting tests for FR2 without SSB time index detection when DRX is not used | Rel-17 | N/A | not recommended due to E-UTRA – FR2 testability issue | NOTE 1 | 2RX | | +| 18.3.1.6 | E-UTRA - NR SA FR2 Event triggered reporting tests for FR2 without SSB time index detection when DRX is used | Rel-17 | N/A | not recommended due to E-UTRA – FR2 testability issue | NOTE 1 | 2RX | | +| 18.3.1.7 | E-UTRA - NR SA FR2 Event triggered reporting tests for FR2 with SSB time index detection when DRX is not used | Rel-17 | N/A | not recommended due to E-UTRA – FR2 testability issue | NOTE 1 | 2RX | | +| 18.3.1.8 | E-UTRA - NR SA FR2 Event triggered reporting tests for FR2 with SSB time index detection when DRX is used | Rel-17 | N/A | not recommended due to E-UTRA – FR2 testability issue | NOTE 1 | 2RX | | +| NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. | | | | | | | | + +**Table 4.2-10: Applicability of NR-U test cases, ref. TS 38.533 [5]** + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 10.3 | Signalling characteristics | | | | | | | +| 10.3.1 | Radio link monitoring | | | | | | | +| 10.3.1.2 | EN-DC FR1 Radio link monitoring out-of-sync test for PSCell under CCA configured with SSB-based RLM RS in non-DRX mode | Rel-16 | C206 | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL and RLM) in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.3.1.3 | EN-DC FR1 Radio link monitoring in-sync test for PSCell under CCA configured with SSB-based RLM RS in non-DRX mode | Rel-16 | C206 | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL and RLM) in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.3.1.4 | EN-DC FR1 Radio link monitoring out-of-sync test for PSCell under CCA configured with SSB-based RLM RS in DRX mode | Rel-16 | C206a | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL and RLM) in dynamic channel access or in semi-static channel access and long DRX | NOTE 1 | 2Rx | | +| 10.3.1.5 | EN-DC FR1 Radio link monitoring in-sync test for PSCell under CCA configured with SSB-based RLM RS in DRX mode | Rel-16 | C206a | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL and RLM) in dynamic channel access or in semi-static channel access and long DRX | NOTE 1 | 2Rx | | +| 10.3.4 | Beam failure detection and link recovery procedures | | | UE supporting 5GS FR1 and NR-U | | | | +| 10.3.4.1 | EN-DC FR1 EN-DC Beam Failure Detection and Link Recovery Test for FR1 PSCell under CCA configured with SSB-based BFD and LR in non-DRX mode | Rel-16 | C206b | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL, RLM and BFR/CBD) in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.3.4.2 | EN-DC FR1 EN-DC Beam Failure Detection and Link Recovery Test for FR1 PSCell under CCA configured with SSB-based BFD and LR in DRX mode | Rel-16 | C206c | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|----------|---------|---------------|----------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | | | | (RRM, UL, RLM and BFR/CBD) in dynamic channel access or in semi-static channel access and long DRX | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-----------------|-----------------------------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 10.3.5 | Active BWP switching | | | | | | | +| 10.3.5.2 | DCI-based and timer-based active BWP switch | | | | | | | +| 10.3.5.2.1 | EN-DC FR1 DCI-based DL active BWP switch in non-DRX in synchronous EN-DC under CCA | Rel-16 | C207 | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL) in dynamic channel access or in semi-static channel access and (DCI and timer based active BWP switching delay Type1 or Type2) and (Support of BWP adaptation upto2 or upto4) | NOTE 1
Test execution not necessary if test 10.3.5.2.2 has been executed. | 2Rx | | +| 10.3.5.2.2 | EN-DC FR1 DCI-based DL active BWP switch with SCell in non-DRX in synchronous EN-DC under CCA | Rel-16 | C207a | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL) in dynamic channel access or in semi-static channel access and (DCI and timer based active BWP switching delay Type1 or Type2) and (Support of BWP adaptation upto2 or upto4) and 2DL CA | NOTE 1 | 2Rx | | +| 10.3.5.3 | RRC-based Active BWP Switch | | | | | | | +| 10.3.5.3.1 | EN-DC FR1 RRC-based DL active BWP switch in non-DRX in synchronous EN-DC under CCA | Rel-16 | C207b | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL) in dynamic channel access or in semi-static channel access and (Support of BWP adaptation upto2 or upto4) | NOTE 1 | 2Rx | | +| 10.3.6 | PSCell addition and release delay | | | | | | | +| 10.3.6.1 | Addition and Release Delay of known NR PSCell on the carrier under CCA | Rel-16 | C207c | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and (RRM, UL) in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|---------------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 10.4 | Measurement Procedures | | | | | | | +| 10.4.1 | Intra-Frequency Measurements | | | | | | | +| 10.4.1.1 | EN-DC FR1 Event-triggered reporting tests on PSCC without gaps under non-DRX and CCA | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.4.1.2 | EN-DC FR1 Event-triggered reporting tests on PSCC without gaps under DRX and CCA | Rel-16 | C207e | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and long DRX cycle | NOTE 1 | 2Rx | | +| 10.4.1.3 | EN-DC FR1 Event-triggered reporting tests on PSCC with per-UE gaps under non-DRX and CCA | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.4.1.4 | EN-DC FR1 Event-triggered reporting tests on PSCC with per-UE gaps under DRX and CCA | Rel-16 | C207e | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and long DRX cycle | NOTE 1 | 2Rx | | +| 10.4.2 | Inter-Frequency Measurements | | | | | | | +| 10.4.2.1 | Void | Rel-16 | FFS | | NOTE 1 | 2Rx | | +| 10.4.2.2 | Void | Rel-16 | FFS | | NOTE 1 | 2Rx | | +| 10.4.2.3 | EN-DC FR1-FR1 Event-triggered reporting for FR1 cell with CCA without SSB time index detection when DRX is not used | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.4.2.4 | EN-DC FR1-FR1 Event triggered reporting for FR1 cell with CCA without SSB time index detection when | Rel-16 | C207e | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|--------|-------------|---------|---------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | DRX is used | | | acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and long DRX cycle | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|-------------|------------------------------------------------------------------------------------------------------------------|---------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 10.4.2.5 | EN-DC FR1-FR1 Event-triggered reporting for FR1 cell with CCA with SSB time index detection when DRX is not used | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.4.2.6 | EN-DC FR1-FR1 Event triggered reporting for FR1 cell with CCA with SSB time index detection when DRX is used | Rel-16 | C207e | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and long DRX cycle | NOTE 1 | 2Rx | | +| 10.4.2.7 | EN-DC FR1-FR1 Event-triggered reporting for FR1 cell without SSB time index detection when DRX is not used | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.4.2.8 | EN-DC FR1-FR1 Event triggered reporting for FR1 cell without SSB time index detection when DRX is used | Rel-16 | C207e | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and long DRX cycle | NOTE 1 | 2Rx | | +| 10.4.2.9 | EN-DC FR1-FR1 Event-triggered reporting for FR1 cell with SSB time index detection when DRX is not used | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.4.2.10 | EN-DC FR1-FR1 Event triggered reporting for FR1 cell with SSB time index detection when DRX is used | Rel-16 | C207e | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and long DRX cycle | NOTE 1 | 2Rx | | +| 10.5 | Measurement Performance | | | | | | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|---------------|--------------------------------------------------------------------------------------------------------|---------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| 10.5.1 | SS-RSRP | | | | | | | +| 10.5.1.1 | EN-DC FR1 intra-frequency SS-RSRP measurement accuracy on a CCA serving cell | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.5.1.2 | EN-DC FR1-FR1 inter-frequency SS-RSRP measurement accuracy with CCA serving cell and CCA target cell | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.5.2 | SS-RSRQ | | | | | | | +| 10.5.2.1 | EN-DC FR1 intra-frequency SS-RSRQ measurement accuracy with serving cell and target cell under CCA | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.5.2.2 | EN-DC FR1-FR1 inter-frequency SS-RSRQ measurement accuracy with serving cell and target cell under CCA | Rel-16 | C207d | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access | NOTE 1 | 2Rx | | +| 10.5.3 | SS-SINR | | | | | | | +| 10.5.3.1 | EN-DC FR1 intra-frequency SS-SINR measurement accuracy on PSCC under CCA | Rel-16 | C207f | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and RRM measurements in dynamic channel access or in semi-static channel access and SS-SINR measurements on shared spectrum | NOTE 1 | 2Rx | | +| 10.5.3.2 | EN-DC FR1-FR1 inter-frequency SS-SINR measurement accuracy on PSCC under CCA | Rel-16 | C207f | UE supporting EN-DC TDD FR1 and NR-U (scenario B) and MIB acquisition on shared spectrum and | NOTE 1 | 2Rx | | + +| Clause | TC Title | Release | Applicability | | Additional Information | Branch | Test Selection Criteria | +|----------|-------------------------------------------------------------------------|---------|---------------|-------------------------------------------------------------------------------------------------------------------------|------------------------|--------|-------------------------| +| | | | Condition | Comment | | | | +| | | | | RRM measurements in dynamic channel access or in semi-static channel access and SS-SINR measurements on shared spectrum | | | | +| 10.5.3.3 | EN-DC FR1 intra-frequency SS-SINR measurement accuracy on SCC under CCA | Rel-16 | FFS | FFS | NOTE 1 | 2Rx | | + +NOTE 1: The test case/branch is incomplete for any Band/CA/DC Configuration but has basic test configurations already. NOTE 1 can be removed only when the test case/branch is complete for at least one Band / CA/DC Configuration for at least one feature included in the test case/branch. Detailed completion status can be found in the corresponding test case section in 38.533. + +## 4.3 RF conformance test cases for Satellite Access + +NOTE: To determine applicability of a test case, supported CBW and SCS in the *RF-Parameters* IE (see TS 38.331 [11]) which conveys RF related capabilities for NR operation is taken into account. + +### 4.3.1 FR1 standalone conformance test cases for Satellite Access + +Table 4.3.1-1: Applicability of RF SA FR1 conformance test cases, ref. TS 38.521-5 [TBD] + +| Clause | TC Title | Release | Applicability | | Tested Bands/CA-Configurations Selection | Branch | Additional Information | +|----------|------------------------------------|---------|---------------|----------------------------------------------------|------------------------------------------|--------|------------------------| +| | | | Condition | Comment | | | | +| 6 | Transmitter Characteristics | | | | | | | +| 6.2.1 | UE maximum output power | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 6.4.1 | Frequency error | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 6.5.3.3 | Additional Spurious emissions | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 7 | Receiver Characteristics | | | | | | | +| 7.3.2 | Reference sensitivity power level | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 7.5 | Adjacent channel selectivity | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 7.7 | Spurious response | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 7.8 | Intermodulation characteristics | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | +| 7.9 | Spurious emission | Rel-17 | FFS | UEs supporting 5GS FR1 supporting satellite access | D027 | PC3 | NOTE 1 | + +Note 1: Some aspect of the test case is incomplete. + +### 4.3.2 Performance conformance test cases for Satellite Access + +Table 4.3.2-1: Applicability of performance test cases, ref. TS 38.521-5 [TBD] + +| Clause | TC Title | Release | Applicability | | Tested Bands Selection | Additional Information | +|---------------------|-------------------------------------------------------|---------|---------------|-------------------------------------------------|------------------------|------------------------| +| | | | Condition | Comment | | | +| 8 | Conducted performance requirements | | | | | | +| 8.2 | Demodulation performance requirements | | | | | | +| 8.2.1.2.2.1.1
_1 | 2Rx FDD FR1 PDSCH Mapping Type A for Satellite Access | Rel-17 | FFS | UEs supporting 5GS FDD FR1 and satellite access | D027 | NOTE 1 | + +Note 1: Some aspect of the test case is incomplete. + +# --- Annex A (informative): Change history + +### Release 16 + +| Change history | | | | | | | | +|----------------|--------------------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-08 | RAN5#76 | R5-173911 | - | - | - | Draft skeleton | 0.0.1 | +| 2018-01 | RAN5#1-5G-NR Adhoc | R5-180107 | - | - | - | Updated after RAN5#1-5G-NR Adhoc:
- Foreword, scope, references, definitions, symbols and abbreviations, recommended test case applicability updated
- clause 4.1.1, 4.1.2, 4.1.3 and 4.1.4 added
- change history added | 0.1.0 | +| 2018-03 | RAN5 #78 | R5-181687 | - | - | - | TP for Clause 4.1.1 Range 1 standalone conformance test cases | 0.2.0 | +| 2018-03 | RAN5 #78 | R5-181688 | - | - | - | TP for Clause 4.1.2 Range 2 standalone conformance test cases | 0.2.0 | +| 2018-03 | RAN5 #78 | R5-181689 | - | - | - | TP for Clause 4.1.3 NR interworking between NR range1 and NR range2 and between NR and LTE conformance test cases | 0.2.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182013 | - | - | - | TP for Clause 3 Definitions, symbols and abbreviations | 0.3.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182047 | - | - | - | TP for Clause 4 Recommended test case applicability | 0.3.0 | +| 2018-08 | RAN5#80 | R5-185209 | - | - | - | TP for Clause 4.1.1 of TS 38.522 | 1.0.1 | +| 2018-08 | RAN5#80 | R5-185210 | - | - | - | TP for Clause 4.1.2 of TS 38.522 | 1.0.1 | +| 2018-08 | RAN5#80 | R5-185211 | - | - | - | TP for Clause 4.1.3 of TS 38.522 | 1.0.1 | +| 2018-09 | RAN#81 | - | - | - | - | raised to v15.0.0 with editorial changes only | 15.0.0 | +| 2018-12 | RAN#82 | R5-186501 | 0013 | - | F | Applicability rules implementation in 38.522 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188223 | 0015 | - | F | Applicability for RRM NR tests | 15.1.0 | +| 2018-12 | RAN#82 | R5-187566 | 0016 | - | F | Update note in section 4.1 to include CBW and SCS in RF test applicability | 15.1.0 | +| 2018-12 | RAN#82 | R5-187849 | 0014 | 1 | F | Adding applicability for new 38.521-1 CA TCs | 15.1.0 | +| 2018-12 | RAN#82 | R5-187881 | 0008 | 1 | F | Update Clause 1 Scope of TS 38.522 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187884 | 0011 | 1 | F | TP for Clause 4.1.2 of TS 38.522 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187922 | 0017 | - | F | Removing FR2 test case 7.4 from TS 38.522 due to testability issue | 15.1.0 | +| 2019-01 | RAN#82 | R5-187882 | 0009 | 1 | F | Update Clause 3 of TS 38.522 | 15.1.1 | +| 2019-01 | RAN#82 | R5-187883 | 0010 | 1 | F | TP for Clause 4.1.1 of TS 38.522 | 15.1.1 | +| 2019-01 | RAN#82 | R5-187885 | 0012 | 1 | F | TP for Clause 4.1.3 of TS 38.522 | 15.1.1 | +| 2019-03 | RAN#83 | R5-191722 | 0021 | - | F | addition of applicability for BFD and measurement | 15.2.0 | +| 2019-03 | RAN#83 | R5-192507 | 0020 | 1 | F | TP for TS 38.522 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192508 | 0022 | 1 | F | Addition of RRM Test Cases Applicability | 15.2.0 | +| 2019-06 | RAN#84 | R5-195444 | 0027 | 1 | F | TP for TS 38.522 | 15.3.0 | +| 2019-06 | RAN#84 | - | - | - | - | Administrative release upgrade to match the release of 3GPP TS 38.508-1 and TS 38.521-1 which were upgraded at RAN#84 to Rel-16 due to Rel-16 relevant CR(s) | 16.0.0 | +| 2019-06 | RAN#84 | - | - | - | - | Addition of missing Table part of R5-195444 and part of a note. | 16.0.1 | +| 2019-06 | RAN#84 | - | - | - | - | Formatted big tables to landscape | 16.0.2 | +| 2019-09 | RAN#85 | R5-197650 | 0030 | 1 | - | TP for TS 38.522 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197650 | 0030 | 1 | - | Added missing changes of R5-197650 | 16.1.1 | +| 2019-12 | RAN#86 | R5-199089 | 0032 | 2 | - | TP for TS 38.522 | 16.2.0 | +| 2020-03 | RAN#87 | R5-201036 | 0033 | 1 | F | TP and format updated for TS 38.522 | 16.3.0 | +| 2020-06 | RAN#88 | R5-202958 | 0040 | 1 | F | R16 TDD ENDC PC2 TP for TS 38.522 | 16.4.0 | +| 2020-06 | RAN#88 | R5-203114 | 0037 | 2 | F | TP updated to applicability table | 16.4.0 | +| 2020-09 | RAN#89 | R5-204098 | 0046 | - | F | Correct applicability EN-DC event-triggered inter-frequency tests | 16.5.0 | +| 2020-09 | RAN#89 | R5-204099 | 0047 | - | F | Correct applicability NR SA event-triggered inter-frequency tests | 16.5.0 | +| 2020-09 | RAN#89 | R5-204939 | 0043 | 1 | F | TP for TS 38.522 | 16.5.0 | + +### Release 16 + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | RAN#89 | R5-204940 | 0044 | 1 | F | Correction of 38.522 | 16.5.0 | +| 2020-12 | RAN#90 | R5-206905 | 0051 | 1 | F | Update to applicability spec for 5G test cases | 16.6.0 | +| 2021-03 | RAN#91 | R5-210506 | 0055 | - | F | Correction of applicability definitions for long DRX cycle related test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210792 | 0058 | - | F | Adding the test applicability of RF test cases for eMIMO | 16.7.0 | +| 2021-03 | RAN#91 | R5-211158 | 0060 | - | F | Addition of applicability new test case 6.3.2.1.3 in TS 38.521-4 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211159 | 0061 | - | F | Addition of applicability new test case 6.3.3.1.3 in TS 38.521-4 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211610 | 0067 | - | F | Applicability of Error Vector Magnitude for V2X for non-concurrent operation | 16.7.0 | +| 2021-03 | RAN#91 | R5-211720 | 0054 | 1 | F | Correction of applicability definitions for PUSCH HalfPi BPSK related test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211853 | 0059 | 1 | F | Update to applicability spec for 5G test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211913 | 0057 | 1 | F | Adding test applicability for switching test case | 16.7.0 | +| 2021-03 | RAN#91 | R5-211917 | 0066 | 1 | F | Addition of new RRM test cases to the applicability table in 4.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211918 | 0068 | 1 | F | Applicability for RRM NR HST test case 6.1.1.7 and 6.6.1.7 | 16.7.0 | +| 2021-03 | RAN#91 | - | - | - | - | Administrative release upgrade to match the release of TS 38.508-1, TS 38.508-2 and TS 38.521-1 which were upgraded at RAN#91 to Rel-17 due to Rel-17 relevant CRs | 17.0.0 | +| 2021-06 | RAN#92 | R5-212078 | 0069 | - | F | Addition of applicability for new test case 6.3.2.1.4 and 6.3.3.1.4 in TS 38.521-4 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212932 | 0075 | - | F | Addition of test applicability for V2X RF test cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-212939 | 0076 | - | F | Adding test applicability for eMIMO demod test cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-212948 | 0077 | - | F | Adding test applicability for URLLC demod test cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-213095 | 0078 | - | F | Adding test applicability for new test cases introduced in R17 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214006 | 0074 | 1 | F | Addition of new V2X test cases to the applicability table in 4.1.1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214089 | 0073 | 1 | F | Update to applicability spec for 5G test cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-214096 | 0071 | 1 | F | Update of Applicability for Inter-band EN-DC Including FR2 | 17.1.0 | +| 2021-09 | RAN#93 | R5-214480 | 0081 | - | F | 38.522 Jumbo CR for R16 CADC configurations | 17.2.0 | +| 2021-09 | RAN#93 | R5-214534 | 0082 | - | F | Addition of applicability for FR2 DL 256QAM demodulation test case | 17.2.0 | +| 2021-09 | RAN#93 | R5-214571 | 0083 | - | F | Adding test applicability for UE power saving test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-214609 | 0084 | - | F | Correction of condition C30 C37 C37a C41 C41a and introduction of condition C37b and C37c | 17.2.0 | +| 2021-09 | RAN#93 | R5-214834 | 0085 | - | F | Applicability for 5G-SRVCC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215033 | 0092 | - | F | Addition of applicability for NR HST TCs | 17.2.0 | +| 2021-09 | RAN#93 | R5-215045 | 0093 | - | F | Addition of R16 FDD-TDD PC2 inter-band EN-DC baseline implementation capabilities into 38.522 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215079 | 0095 | - | F | Addition of test applicability for V2X test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215245 | 0099 | - | F | Addition of test applicability for RRM test case 6.6.4.5 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215399 | 0102 | - | F | Add 2-Step PRACH test cases to Applicability spec | 17.2.0 | +| 2021-09 | RAN#93 | R5-215411 | 0103 | - | F | Correction of RRM HST test cases applicability | 17.2.0 | +| 2021-09 | RAN#93 | R5-215931 | 0090 | 1 | F | Addition of applicability for Mob_Enh TCs | 17.2.0 | + +### Release 16 + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-215935 | 0096 | 1 | F | Adding test applicability for eMIMO test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215960 | 0098 | 1 | F | Addition of applicability of URLLC demod test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215981 | 0086 | 1 | F | FR2 standalone RF conformance test case applicability | 17.2.0 | +| 2021-09 | RAN#93 | R5-216077 | 0097 | 1 | F | Test applicability for FR2 256QAM CQI reporting | 17.2.0 | +| 2021-09 | RAN#93 | R5-216097 | 0101 | 1 | F | Update to applicability spec for 5G test cases | 17.2.0 | +| 2021-12 | RAN#94 | R5-216539 | 0105 | - | F | Addition of applicability for HST test case 5.2.3.1.9_1 | 17.3.0 | +| 2021-12 | RAN#94 | R5-216540 | 0106 | - | F | Addition of applicability for HST test case 5.2.3.1.10_1 | 17.3.0 | +| 2021-12 | RAN#94 | R5-216784 | 0109 | - | F | Correction to Test Bands Selection Criteria for performance test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-216852 | 0110 | - | F | Correction to applicability of RLM TCs | 17.3.0 | +| 2021-12 | RAN#94 | R5-216870 | 0111 | - | F | Correction to applicability of Mob_enh RRM TCs | 17.3.0 | +| 2021-12 | RAN#94 | R5-216911 | 0112 | - | F | Correction to applicability of HST TCs | 17.3.0 | +| 2021-12 | RAN#94 | R5-217219 | 0114 | - | F | Correct of condition for RRM Test Cases with BWP switch | 17.3.0 | +| 2021-12 | RAN#94 | R5-217319 | 0116 | - | F | Addition of applicability for new type II PMI reporting test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-217349 | 0118 | - | F | Update of 3.1 for definitions of CA and DC configurations | 17.3.0 | +| 2021-12 | RAN#94 | R5-217381 | 0120 | - | F | Addition of test applicability for URLLC test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-217529 | 0122 | - | F | Jumbo CR for updating applicability of NR perf enh WI test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-217568 | 0123 | - | F | Correction of RRM HST test cases applicability | 17.3.0 | +| 2021-12 | RAN#94 | R5-217569 | 0124 | - | F | Correction of RRM test cases applicability - Note 1 removal | 17.3.0 | +| 2021-12 | RAN#94 | R5-217597 | 0125 | - | F | Update applicability for Tx modulation quality test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-217729 | 0129 | - | F | 38.522 applicability updates for Rel. 16 FR2 RF enhancements | 17.3.0 | +| 2021-12 | RAN#94 | R5-218249 | 0115 | 1 | F | Update of MPR applicability for intra-band contiguous EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-218370 | 0107 | 1 | F | Addition of content for FR2 standalone RF conformance test case applicability | 17.3.0 | +| 2021-12 | RAN#94 | R5-218371 | 0128 | 1 | F | NR U test case applicability | 17.3.0 | +| 2021-12 | RAN#94 | R5-218390 | 0108 | 1 | F | Addition of Power Class 1.5 into applicability of RF SA FR1 conformance test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-218437 | 0113 | 1 | F | 6.2B.2.2 MPR IBNC EN-DC applicability correction if 6.5B.2.2.3 ACLR IBNC EN-DC is executed | 17.3.0 | +| 2021-12 | RAN#94 | R5-218438 | 0127 | 1 | F | Update to applicability spec for 5G test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-218460 | 0117 | 1 | F | Adding test applicability for switching time mask for inter-band EN-DC | 17.3.0 | +| 2021-12 | RAN#94 | R5-218463 | 0119 | 1 | F | Addition of test applicability e-MIMO test cases | 17.3.0 | +| 2022-03 | RAN#95 | R5-220041 | 0131 | - | F | Addition of the TDD DSS NR bands n34, n39 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220163 | 0133 | - | F | Add 2-Step RACH test cases to Applicability spec | 17.4.0 | +| 2022-03 | RAN#95 | R5-220166 | 0134 | - | F | Update of RRM test case applicability - Note 1 removal | 17.4.0 | +| 2022-03 | RAN#95 | R5-220663 | 0140 | - | F | Update of HST Demod test case applicability - Note 1 removal | 17.4.0 | +| 2022-03 | RAN#95 | R5-220673 | 0142 | - | F | Correcting applicability of HST test cases in 38.522 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220757 | 0143 | - | F | Addition of new performance enhancement test case in 38.522 | 17.4.0 | + +###### Release 16 + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | RAN#95 | R5-220787 | 0144 | - | F | Update to test applicability for V2X test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-220823 | 0145 | - | F | Update to test applicability for URLLC test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-220965 | 0147 | - | F | Addition of applicability for test cases for EN-DC with 3 uplink | 17.4.0 | +| 2022-03 | RAN#95 | R5-221004 | 0149 | - | F | Correction to applicability of FR2 intra-frequency measurement without DRX and BFD TCs | 17.4.0 | +| 2022-03 | RAN#95 | R5-221048 | 0150 | - | F | Correction of 4.0 for tested DC configuration selection criteria | 17.4.0 | +| 2022-03 | RAN#95 | R5-221213 | 0152 | - | F | Addition of applicability for CADC MPR TC 6.2B.2.4_1.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221295 | 0154 | - | F | Correction of RRM test cases applicability - Note 1 removal | 17.4.0 | +| 2022-03 | RAN#95 | R5-221296 | 0155 | - | F | Addition of Idle Mode CA/DC Measurements test cases applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221371 | 0158 | - | F | Adding new HST test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-221711 | 0132 | 1 | F | Correction of Additional Information for 6.2.2, 6.2.3 and 6.5.2.4.1 of 38.521-1 and 6.2B.2.3 and 6.2B.3.3 of 38.521-3 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221712 | 0139 | 1 | F | Correction to Applicability and Additional information for EN-DC TC and RRM TC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221797 | 0153 | 1 | F | Addition of FR1 DL Interruptions test cases applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221831 | 0146 | 1 | F | Addition of test applicability for UE Enhancements on MIMO | 17.4.0 | +| 2022-03 | RAN#95 | R5-221832 | 0148 | 1 | F | Addition of test applicability for L1-SINR measurement cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-221849 | 0130 | 1 | F | Updated the Test case conditions and selection criteria for TDD DSS NR bands n38, n48, n90 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221850 | 0137 | 1 | F | Addition of FR1 CA CQI test cases applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221851 | 0138 | 1 | F | Addition of FR2 CA CQI test cases applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221852 | 0151 | 1 | F | Applicability of NR perf enh WI test cases | 17.4.0 | +| 2022-03 | RAN#95 | R5-221858 | 0135 | 1 | F | Correction of HST test case applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221891 | 0136 | 1 | F | Correction of FR2 standalone Enhanced Beam correspondence - EIRP RF conformance test case applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221913 | 0156 | 1 | F | New EVM test case applicability | 17.4.0 | +| 2022-06 | RAN#96 | R5-222190 | 0159 | - | F | Correction of test applicability for 6.4.2.5 of 38.521-1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222191 | 0160 | - | F | Separation of 6.2B.1.4D of 38.521-3 into two test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-222562 | 0162 | - | F | Addition of applicability for CADC MOP TC | 17.5.0 | +| 2022-06 | RAN#96 | R5-222631 | 0164 | - | F | Addition of test applicability for NR SL Demod TCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-222632 | 0165 | - | F | Addition of test applicability for NR SL RRM TCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-222736 | 0169 | - | F | Add 7.5F.1 and 7.6F.2 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222914 | 0172 | - | F | Removing test case 6.5D.1_1 Occupied bandwidth for UL MIMO (Rel-16 onward) from 38.522 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222992 | 0176 | - | F | Removal of NOTE1 for test case 5.2.2.2.9_1, 5.2.2.2.10_1, 5.2.3.2.9_1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222994 | 0177 | - | F | Update of applicability of FR2 performance test | 17.5.0 | +| 2022-06 | RAN#96 | R5-223123 | 0181 | - | F | Test case 6.3.2.2.3, 6.3.2.2.4 and 6.3.3.2.3 in 38.522 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223701 | 0189 | 1 | F | Correction of FR1 DL Interruptions test cases applicability | 17.5.0 | +| 2022-06 | RAN#96 | R5-223706 | 0178 | 1 | F | Addition of test applicability for eMIMO test cases | 17.5.0 | + +### Release 16 + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-06 | RAN#96 | R5-223720 | 0163 | 1 | F | Applicability update for NR perf enh WI test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-223725 | 0166 | 1 | F | Correction to applicability of HST RRM TCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223753 | 0179 | 1 | F | 38.522 applicability updates for Rel.16 FR2 RF enhancements | 17.5.0 | +| 2022-06 | RAN#96 | R5-223783 | 0170 | 1 | F | Jumbo Applicability CR for NR_RF_TxD WI | 17.5.0 | +| 2022-06 | RAN#96 | R5-223791 | 0171 | 1 | F | Addition of test applicability for RedCap test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-223842 | 0161 | 1 | F | Correction to applicability for 6.2D.1.1 and 6.2D.1.2 of 38.521-2 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223843 | 0167 | 1 | F | Correction to test bands selection criteria for UL MIMO capabilities | 17.5.0 | +| 2022-06 | RAN#96 | R5-223844 | 0168 | 1 | F | Correction to applicability of 5G test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-223845 | 0180 | 1 | F | Correction on test condition for FR2 DL 256QAM test cases | 17.5.0 | +| 2022-06 | RAN#96 | R5-223846 | 0185 | 1 | F | Addition to 3.3 for new abbreviations in TS 38.522 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223847 | 0186 | 1 | F | Correction to 4.0 on Tested CA DC configuration selection criteria for E005a, E010 and E010a | 17.5.0 | +| 2022-06 | RAN#96 | R5-223848 | 0187 | 1 | F | Editorial correction to A.4.0 for Tested bands selection criteria | 17.5.0 | +| 2022-06 | RAN#96 | R5-223849 | 0188 | 1 | F | Update of applicability of FR2 RF test cases | 17.5.0 | +| 2022-09 | RAN#97 | R5-223968 | 0190 | - | F | Applicability for 5.7.1.3 and 7.7.1.3 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224381 | 0199 | - | F | Update of clause and description for eMIMO RRM Test Cases according to WP updated | 17.6.0 | +| 2022-09 | RAN#97 | R5-224438 | 0200 | - | F | Addition of applicability for CADC MOP TC | 17.6.0 | +| 2022-09 | RAN#97 | R5-224504 | 0201 | - | F | Correction to applicability of NR SL Demod TCs | 17.6.0 | +| 2022-09 | RAN#97 | R5-224634 | 0202 | - | F | Correction to applicability of C097 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224839 | 0205 | - | F | Update to test applicability of CA test cases to support PC2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224903 | 0206 | - | F | Update applicability for NR-U test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224968 | 0207 | - | F | Editorial, putting C003a and C003b in correct order | 17.6.0 | +| 2022-09 | RAN#97 | R5-224998 | 0208 | - | F | Correction to applicability of 5G test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225077 | 0209 | - | F | Adding new test condition and applicability for new test case 6.3C.3.2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225710 | 0197 | 1 | F | Addition of test applicability for FR2 EN-DC TX Test Cases 5CC to 8CCs | 17.6.0 | +| 2022-09 | RAN#97 | R5-225724 | 0203 | 1 | F | Addition of test applicability for eMIMO test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225747 | 0191 | 1 | F | Applicability for 2-step RACH test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225752 | 0196 | 1 | F | Update of inter-band CA PC2 test applicability | 17.6.0 | +| 2022-09 | RAN#97 | R5-225755 | 0210 | 1 | F | Adding applicability for new SUL and UL MIMO test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225764 | 0194 | 1 | F | Correction of Applicability of conformance test cases conditions, Tested Bands Selection Criteria and Branch for the TxD test cases in 38.521-1 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225765 | 0204 | 1 | F | Addition of test applicability for TxD test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225814 | 0192 | 1 | F | Correction of Applicability of conformance test cases conditions and Tested Bands Selection Criteria for the R15 test cases in 38.521-1 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225882 | 0211 | 1 | F | Addition of test case for additional spurious for FR2 | 17.6.0 | + +###### Release 16 + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98 | R5-225949 | 0213 | | F | Adding applicability statements for UEs supporting 5GS FR1 and NR-DC | 17.7.0 | +| 2022-12 | RAN#98 | R5-226112 | 0214 | | F | Addition of applicability for RedCap RRM TCs | 17.7.0 | +| 2022-12 | RAN#98 | R5-226335 | 0215 | | F | Update to R16 NR CADC configuration test cases applicability | 17.7.0 | +| 2022-12 | RAN#98 | R5-226702 | 0223 | | F | Addition of applicability for RedCap demod test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-226764 | 0226 | | F | Correction to title of TC7.8F.2 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226795 | 0227 | | F | Update applicability for performance test case 5.2.3.2.9_1 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226936 | 0231 | | F | Adding applicability for new test cases for SUL with UL MIMO | 17.7.0 | +| 2022-12 | RAN#98 | R5-226942 | 0232 | | F | Applicability for new Rel-16 FR2 RF requirements enhancements test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227117 | 0233 | | F | Update of test applicability for RedCap test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227248 | 0235 | | F | Completion of test case 7.2.2.2.1_3 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227383 | 0237 | | F | Applicability spec updates related to rel16 FR2 RF enhancements | 17.7.0 | +| 2022-12 | RAN#98 | R5-227871 | 0234 | 1 | F | Addition of CA_DC enhancements test cases applicability | 17.7.0 | +| 2022-12 | RAN#98 | R5-227872 | 0221 | 1 | F | Applicability spec update for DL1024QAM test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227874 | 0230 | 1 | F | Update to test applicability of SUL test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227876 | 0224 | 1 | F | Add applicability of 6.4F.2.2 and 6.5F.4 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227877 | 0236 | 1 | F | Addition of test applicability for NR-U Demod and RRM test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227878 | 0218 | 1 | F | Update to R16 NR perf enh test cases applicability | 17.7.0 | +| 2022-12 | RAN#98 | R5-227879 | 0219 | 1 | F | Applicability of NSA CA test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-228030 | 0217 | 1 | F | Update to R17 NR HST FR1 enh test cases applicability | 17.7.0 | +| 2022-12 | RAN#98 | R5-228040 | 0229 | 1 | F | Updating test applicability for TxD test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-228049 | 0225 | 1 | F | Correction to applicability of 5G test cases | 17.7.0 | +| 2023-03 | RAN#99 | R5-230416 | 0240 | - | F | Update to R17 NR HST FR1 enh test cases applicability | 17.8.0 | +| 2023-03 | RAN#99 | R5-230458 | 0244 | - | F | Addition of Applicability for RedCap RRM TCs | 17.8.0 | +| 2023-03 | RAN#99 | R5-230526 | 0245 | - | F | Addition of Applicability for RRM enhancement TCs | 17.8.0 | +| 2023-03 | RAN#99 | R5-230576 | 0246 | - | F | Editorial correction for Applicability Comment of 6.2G.3 and 6.2G.4 in 4.1.1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230667 | 0249 | - | F | Addition of applicabilities for NR-U test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-230679 | 0251 | - | F | Addition of applicability for RedCap demod test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231091 | 0258 | - | F | Adding applicability for new test cases for SUL with UL MIMO | 17.8.0 | +| 2023-03 | RAN#99 | R5-231658 | 0267 | - | F | Correction of test case title of 7.6D.2_1 and 7.8D.2_1 of 38.521-1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231806 | 0241 | 1 | F | Addition of applicability for DC_CA test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231808 | 0238 | 1 | F | Update to R16 NR CADC configuration test cases applicability | 17.8.0 | +| 2023-03 | RAN#99 | R5-231809 | 0263 | 1 | F | Update 38.522 for 7.3A.3 Reference sensitivity power level for 4DL CA | 17.8.0 | +| 2023-03 | RAN#99 | R5-231810 | 0265 | 1 | F | Addition of applicability for FR2 RF phase continuity test | 17.8.0 | +| 2023-03 | RAN#99 | R5-231812 | 0242 | 1 | F | Add applicability of new test cases for gap enhancement | 17.8.0 | + +###### Release 16 + +| | | | | | | | | +|---------|---------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | RAN#99 | R5-231814 | 0260 | 1 | F | Correction of applicability of the RedCap test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231815 | 0256 | 1 | F | Adding test applicability for CA test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231816 | 0248 | 1 | F | Adding applicability statement for UE UL carrier RRC reconfiguration delay for FR2 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231817 | 0266 | 1 | F | Applicability updates to FR2 RF tests | 17.8.0 | +| 2023-03 | RAN#99 | R5-231818 | 0247 | 1 | F | Adding applicability statements for UEs supporting TA Validation for CG-SDT in FR2 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231819 | 0254 | 1 | F | Introduction of abbreviation of CCA and clarification on FR1 band selection with CCA | 17.8.0 | +| 2023-03 | RAN#99 | R5-231821 | 0259 | 1 | F | Additional information note correction for RRM test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231878 | 0252 | 1 | F | Addition of applicability for 5GS FR1 and FR2 PDC IloT Test Cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231888 | 0261 | 1 | F | Correction to applicability of 5G test cases | 17.8.0 | +| 2023-03 | RAN#99 | R5-231894 | 0255 | 1 | F | Update to BWP adaptation applicability conditions | 17.8.0 | +| 2023-03 | RAN#99 | R5-231973 | 0262 | 2 | F | Update test condition for 7.3.2 and 6.2.x | 17.8.0 | +| 2023-06 | RAN#100 | R5-232129 | 0269 | - | F | Adding applicability statement for SCell Activation and deactivation for SCell in FR2 inter-band in non-DRX | 17.9.0 | +| 2023-06 | RAN#100 | R5-232274 | 0272 | - | F | Adding applicability UE Rx-Tx time difference measurement for propagation delay compensation using TRS in FR2 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232458 | 0273 | - | F | Correction to applicability of RedCap RRM TCs | 17.9.0 | +| 2023-06 | RAN#100 | R5-232578 | 0275 | - | F | Addition of applicability for RedCap demod test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-232580 | 0276 | - | F | Addition of applicability for test case 6.5F.2.4.2 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232742 | 0278 | - | F | Addition of test applicability for SUL test cases with UL MIMO | 17.9.0 | +| 2023-06 | RAN#100 | R5-232756 | 0279 | - | F | Correction to test applicability for UL MIMO test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-232812 | 0283 | - | F | Update to R17 NR HST FR1 enh test cases applicability | 17.9.0 | +| 2023-06 | RAN#100 | R5-232834 | 0284 | - | F | Adding applicability for MMSE-IRC test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-232928 | 0287 | - | F | Applicability of FR2 RedCap reselection test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233032 | 0289 | - | F | Update to test applicability of beam correspondence | 17.9.0 | +| 2023-06 | RAN#100 | R5-233253 | 0298 | - | F | Applicability updates to FR2 RF tests | 17.9.0 | +| 2023-06 | RAN#100 | R5-233506 | 0270 | 1 | F | Addition of applicability for 5GS HST FR2 test case | 17.9.0 | +| 2023-06 | RAN#100 | R5-233685 | 0296 | 1 | F | Update to handle the test case applicability with different branches | 17.9.0 | +| 2023-06 | RAN#100 | R5-233686 | 0271 | 1 | F | Completion of applicability for DC_CA test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233687 | 0297 | 1 | F | Addition of applicability for FR2 RF phase continuity test | 17.9.0 | +| 2023-06 | RAN#100 | R5-233689 | 0291 | 1 | F | Addition of applicability for NR feMIMO test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233690 | 0268 | 1 | F | Add applicability of new test cases for gap enhancement- Pre-MG and NCSG | 17.9.0 | +| 2023-06 | RAN#100 | R5-233691 | 0277 | 1 | F | Update to RRM applicability rules and test optimization - 38.522 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233692 | 0280 | 1 | F | Correction to applicability for performance test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233693 | 0299 | 1 | F | Applicability update for FR2 TCI state switch tests | 17.9.0 | +| 2023-06 | RAN#100 | R5-233710 | 0274 | 1 | F | Update of eMG case applicabilities | 17.9.0 | + +###### Release 16 + +| | | | | | | | | +|---------|---------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|---------| +| 2023-06 | RAN#100 | R5-233715 | 0290 | 1 | F | Update to test applicability of SUL test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233727 | 0293 | 1 | F | Update of applicability for FR2 CA test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233728 | 0295 | 1 | F | Correction to applicability of 5G test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233731 | 0285 | 1 | F | Applicability update for CLI test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233736 | 0281 | 1 | F | Update to R16 NR CADC configuration test cases applicability | 17.9.0 | +| 2023-06 | RAN#100 | R5-233778 | 0294 | 1 | F | Update applicability for in-band blocking FR2 CA test cases | 17.9.0 | +| 2023-09 | RAN#101 | R5-234067 | 0300 | - | F | Adding applicability rules for the remaining MMSE-IRC test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234188 | 0302 | - | F | Set branch column to PC3 for Rel-15 in FR1 test case 6.4.2.5 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234335 | 0303 | - | F | Addition of applicability for 5GS HST FR2 7.1.1.7 test case | 17.10.0 | +| 2023-09 | RAN#101 | R5-234359 | 0306 | - | F | Adding applicability statement for NR SA FR2 SSB based Inter-cell L1-RSRP measurement in non-DRX test case | 17.10.0 | +| 2023-09 | RAN#101 | R5-234368 | 0307 | - | F | Addition of applicability for MRDC test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234427 | 0309 | - | F | Addition of applicability for RRM enh TCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-234433 | 0310 | - | F | Correction to applicability for SFTD TCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-234624 | 0312 | - | F | Update of applicability for MG enhancements cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234667 | 0315 | - | F | Update to applicability for RedCap RLM, BFR and BWP switch test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234673 | 0316 | - | F | Update to applicability of stationary idle mode RedCap tests | 17.10.0 | +| 2023-09 | RAN#101 | R5-234675 | 0317 | - | F | Applicability update for RRM FR2 test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234679 | 0318 | - | F | Update to applicability for FR2 TCI state switch tests | 17.10.0 | +| 2023-09 | RAN#101 | R5-234690 | 0319 | - | F | Adding applicability statements for RRM test cases 16.6.7.1 and 16.6.7.2 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234711 | 0320 | - | F | Update of applicability for inter-band PC2 CA test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234735 | 0322 | - | F | Update to R17 NR CADC configuration test cases applicability | 17.10.0 | +| 2023-09 | RAN#101 | R5-234826 | 0325 | - | F | Updates of applicability for RedCap demod test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234862 | 0327 | - | F | Addition of applicability for test cases of unified TCI state | 17.10.0 | +| 2023-09 | RAN#101 | R5-234931 | 0328 | - | F | Addition of new NR-U test case 6.2F.2 in 38.522 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235039 | 0329 | - | F | Removing NOTE 1 for test case 6.5D.2.2_1 in table 4.1.1-1 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235105 | 0331 | - | F | Addition applicability for Power saving Enh test cases 6.5.1.9 and 5.5.5.9 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235220 | 0334 | - | F | Update to applicability for FR2 RF phase continuity test | 17.10.0 | +| 2023-09 | RAN#101 | R5-235797 | 0321 | 1 | F | Update to R16 NR CADC configuration test cases applicability | 17.10.0 | +| 2023-09 | RAN#101 | R5-235798 | 0314 | 1 | F | Update to NR-U test applicability | 17.10.0 | +| 2023-09 | RAN#101 | R5-235799 | 0308 | 1 | F | Correction to applicability for RedCap RRM TCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-235800 | 0313 | 1 | F | Update to applicability for power savings tests | 17.10.0 | +| 2023-09 | RAN#101 | R5-235801 | 0305 | 1 | F | Adding applicability statement for NR SA FR1 DL interruptions at | 17.10.0 | + +###### Release 16 + +| | | | | | | | | +|---------|---------|-----------|------|---|---|------------------------------------------------------------------------------------------|---------| +| | | | | | | switching between two uplink carriers test cases | | +| 2023-09 | RAN#101 | R5-235802 | 0326 | 1 | F | Addition of test applicability for 2Tx switching | 17.10.0 | +| 2023-09 | RAN#101 | R5-235803 | 0311 | 1 | F | Update to applicability of 5G test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-235804 | 0333 | 1 | F | Corrections on the note for operator NOT in Table 4.0-2 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235962 | 0301 | 1 | F | Correction of Additional Information for 6.5B.3.3.1, 6.5B.3.3.2 and 7.3B.2.3 of 38.521-3 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234751 | 0324 | - | F | Update of RF UL MIMO test case applicability | 18.0.0 | +| 2023-12 | RAN#102 | R5-236503 | 0340 | - | F | Adding applicability for newly introduced NR-U test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236516 | 0341 | - | F | Adding applicability for newly introduced RedCap test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236631 | 0343 | - | F | Updating to test applicability of URLLC test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236875 | 0349 | - | F | Addition of test applicability for MR-DC enhancement test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236912 | 0350 | - | F | Addition of applicability of FR1 CA with UL MIMO test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237024 | 0352 | - | F | Applicability of RRM enhancement test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237217 | 0361 | - | F | Update on 6.5.1.9 applicability | 18.1.0 | +| 2023-12 | RAN#102 | R5-237259 | 0363 | - | F | Applicability update for FR2 UL MIMO test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237301 | 0365 | - | F | Removal of NOTE 1 from applicability of FR1 CA with UL Tx switching test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237469 | 0364 | 2 | F | Update to applicability spec for NTN test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237772 | 0356 | 1 | F | Addition of test applicability and condition for RRM MR-DC Rel-17 Test Cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237773 | 0344 | 1 | F | Update to R16 NR CADC configuration test cases applicability | 18.1.0 | +| 2023-12 | RAN#102 | R5-237774 | 0362 | 1 | F | Applicability updates for Phase continuity tests | 18.1.0 | +| 2023-12 | RAN#102 | R5-237775 | 0336 | 1 | F | Addition of applicability of HST FR2 test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237776 | 0335 | 1 | F | Update of applicability for MG enhancements TC | 18.1.0 | +| 2023-12 | RAN#102 | R5-237777 | 0342 | 1 | F | Correction to applicability of 5G test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237778 | 0351 | 1 | F | Applicability of RedCap test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237779 | 0354 | 1 | F | Updating FR1 test case branches for intra-band UL CA testing | 18.1.0 | +| 2023-12 | RAN#102 | R5-237780 | 0357 | 1 | F | Update to FR1 SDT test case applicability | 18.1.0 | +| 2023-12 | RAN#102 | R5-237781 | 0358 | 1 | F | Applicability update for NR-U RRM test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237782 | 0360 | 1 | F | Addition of Test Selection Criteria for RRM | 18.1.0 | +| 2023-12 | RAN#102 | R5-237913 | 0347 | 1 | F | Correction to applicability for RedCap RRM TCs | 18.1.0 | +| 2023-12 | RAN#102 | R5-237933 | 0338 | 1 | F | Addition of MMSE-IRC CQI reporting test applicability rule | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38751/031e354d9de9563c9f650e3e4fcba16d_img.jpg b/marked/Rel-18/38_series/38751/031e354d9de9563c9f650e3e4fcba16d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a72d3e069ef2121c7282c97ea6ac0620d0986f1b --- /dev/null +++ b/marked/Rel-18/38_series/38751/031e354d9de9563c9f650e3e4fcba16d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92d2f98bc69dd358fd5b89176f0c7137698a2170b24c103ecf8a00ef7b0723e1 +size 14573 diff --git a/marked/Rel-18/38_series/38751/068b3a3247570c4b78342a943f15de9e_img.jpg b/marked/Rel-18/38_series/38751/068b3a3247570c4b78342a943f15de9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95894a8f84ef8d36f80c9e031b5f37868dbeaa65 --- /dev/null +++ b/marked/Rel-18/38_series/38751/068b3a3247570c4b78342a943f15de9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddfefdb5fe03fa67cab8a1ddc3f1009e5caa522271697ce43e6fef7deeb60924 +size 44261 diff --git a/marked/Rel-18/38_series/38751/0ffcb27a48f875e32f7b268421957e34_img.jpg b/marked/Rel-18/38_series/38751/0ffcb27a48f875e32f7b268421957e34_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3101c5d0b3b06a36038a09da53df0c074d4dade6 --- /dev/null +++ b/marked/Rel-18/38_series/38751/0ffcb27a48f875e32f7b268421957e34_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46164fc708580b5839582c0b8744ee0d369169f500532e991283dbfb9e0ebb5c +size 6128 diff --git a/marked/Rel-18/38_series/38751/14cd2c0744fd9e2b8ae8d9665248a411_img.jpg b/marked/Rel-18/38_series/38751/14cd2c0744fd9e2b8ae8d9665248a411_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d6f353586719bec020344bd0654f2da129a5a4b --- /dev/null +++ b/marked/Rel-18/38_series/38751/14cd2c0744fd9e2b8ae8d9665248a411_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ba5c0a1f4816aed7287ef5ec15f4a445cf972ba052a77e153a85c8996c0c767 +size 20910 diff --git a/marked/Rel-18/38_series/38751/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-18/38_series/38751/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0703e29435ec7d2e06dc665ec73eaf39cdc77b18 --- /dev/null +++ b/marked/Rel-18/38_series/38751/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:071c8d351907986d2271b85ca3ceb2800d5fe3039fabccdd17850fc7920467c8 +size 23393 diff --git a/marked/Rel-18/38_series/38751/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-18/38_series/38751/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b07563b515afc8e820d34fedd2448296cc84d70 --- /dev/null +++ b/marked/Rel-18/38_series/38751/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40ab946b223fc2e5648e1549fd0db50452125dd74b8999193537797139360ab5 +size 90112 diff --git a/marked/Rel-18/38_series/38751/23816aaa8e6defc50fc888da62fd59cc_img.jpg b/marked/Rel-18/38_series/38751/23816aaa8e6defc50fc888da62fd59cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..416ead79dfb67f9ba23d1224c0031b3420eaab00 --- /dev/null +++ b/marked/Rel-18/38_series/38751/23816aaa8e6defc50fc888da62fd59cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3ee15820d48be90ad0a52af1d3a7b5c283926018cae00539d95c0ddd1cdc53a +size 80139 diff --git a/marked/Rel-18/38_series/38751/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-18/38_series/38751/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c136d0cc543ab41454f4db47bd559efc5d1175 --- /dev/null +++ b/marked/Rel-18/38_series/38751/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db4b6c5aa50171a27412e5b92551f7b097e171d645c8bd3d7163ca6509c0d329 +size 99336 diff --git a/marked/Rel-18/38_series/38751/367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg b/marked/Rel-18/38_series/38751/367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c64109773b011c8ce997df0714e778a03573cf6 --- /dev/null +++ b/marked/Rel-18/38_series/38751/367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a840b7b396dd60a36744f58e0c0f2880d0d8ada94c914f06c60a3c2735d5580 +size 22409 diff --git a/marked/Rel-18/38_series/38751/3a310163273edcf70c19269a06d0cdf2_img.jpg b/marked/Rel-18/38_series/38751/3a310163273edcf70c19269a06d0cdf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79ebc993252e624fd800da97d300cfccdfe96580 --- /dev/null +++ b/marked/Rel-18/38_series/38751/3a310163273edcf70c19269a06d0cdf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:863845e48f9aa2a0342f758dde0fdaa81235c670369ce1240cded827667ad1cb +size 44185 diff --git a/marked/Rel-18/38_series/38751/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg b/marked/Rel-18/38_series/38751/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7c171168726fe83f16b0fee81c135f10e685d7c --- /dev/null +++ b/marked/Rel-18/38_series/38751/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cd8d56958c2fd04b5479e743322b6285ff1c9819a798921f119fd14d895a949 +size 117323 diff --git a/marked/Rel-18/38_series/38751/475caf31ae90b878f12d651b689cc9d1_img.jpg b/marked/Rel-18/38_series/38751/475caf31ae90b878f12d651b689cc9d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9d81f3e05fd3a3585bafbb9ce40f986b7dc56aa --- /dev/null +++ b/marked/Rel-18/38_series/38751/475caf31ae90b878f12d651b689cc9d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6f55e8d956fdb18abd5de9e641a309fdddaebcf2f1da0a76c1cab1a9cbf8fd2 +size 21617 diff --git a/marked/Rel-18/38_series/38751/4936add03827ef5a51439c28ec878506_img.jpg b/marked/Rel-18/38_series/38751/4936add03827ef5a51439c28ec878506_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0092aca792fa414cf983fbbebe00208f3eecd71 --- /dev/null +++ b/marked/Rel-18/38_series/38751/4936add03827ef5a51439c28ec878506_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ba416ba70f96071e7ee92425027d94d3fa659077fe151e533c0c139ab5c898a +size 15177 diff --git a/marked/Rel-18/38_series/38751/4bff5f22997753bcf1997c715118012d_img.jpg b/marked/Rel-18/38_series/38751/4bff5f22997753bcf1997c715118012d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de17b558ae6ea9c0688ebc0e8bdac9294cedf3cf --- /dev/null +++ b/marked/Rel-18/38_series/38751/4bff5f22997753bcf1997c715118012d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:114bd473cce7a844f9ba911ee8909b9602c2e83612b8c5bf146b93a3c642d4e0 +size 43851 diff --git a/marked/Rel-18/38_series/38751/4f90ddf705239c0ca535c91179212420_img.jpg b/marked/Rel-18/38_series/38751/4f90ddf705239c0ca535c91179212420_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8d31f38eecd1cf359169b3780ea36dc917418a5 --- /dev/null +++ b/marked/Rel-18/38_series/38751/4f90ddf705239c0ca535c91179212420_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5a88534ab77be9b7a4bb799595a829de91d34403b4b4f6d412f2873eb6d8e3a +size 53761 diff --git a/marked/Rel-18/38_series/38751/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-18/38_series/38751/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..219fc5d53b7ca41f827887326983ba2fa1f78f4d --- /dev/null +++ b/marked/Rel-18/38_series/38751/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35eea579732aec54b75bdc5326c3a3fcba23b5c41ec14478e810f4562e554cce +size 46469 diff --git a/marked/Rel-18/38_series/38751/555996c5b2c9b5333629d95b83d1cb73_img.jpg b/marked/Rel-18/38_series/38751/555996c5b2c9b5333629d95b83d1cb73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b1218d2a000bcc355a6e7a4cbf1feff0a779ebe --- /dev/null +++ b/marked/Rel-18/38_series/38751/555996c5b2c9b5333629d95b83d1cb73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22d0c1bed93917f316fe1d25fe267df289662e3fc19d02d15e4da5274059b7df +size 11663 diff --git a/marked/Rel-18/38_series/38751/5a2d10b858b621236f708a5f5fa1ed88_img.jpg b/marked/Rel-18/38_series/38751/5a2d10b858b621236f708a5f5fa1ed88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15397577c79241cbe0e716d19db4dad393513ea3 --- /dev/null +++ b/marked/Rel-18/38_series/38751/5a2d10b858b621236f708a5f5fa1ed88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37a774f477daabfd856d0f3f67b26e28414d1fb257009342db715801d54820d3 +size 30625 diff --git a/marked/Rel-18/38_series/38751/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38751/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94559a5a83f0d4f9feee986e650222570f054fa7 --- /dev/null +++ b/marked/Rel-18/38_series/38751/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63953f8d8a6a9a0c4d35be421cf5220c7e0b03017e9e796219f4c3eea4d66887 +size 9603 diff --git a/marked/Rel-18/38_series/38751/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38751/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..147f18f4756c015cd3adb7c56a77de093f7d54f9 --- /dev/null +++ b/marked/Rel-18/38_series/38751/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0127493ca1cce9955211f3330bce898cd0ee4353daf527792d032b226fc0cb10 +size 5800 diff --git a/marked/Rel-18/38_series/38751/6a842e59ecf31b0d6f6721ac4e76f160_img.jpg b/marked/Rel-18/38_series/38751/6a842e59ecf31b0d6f6721ac4e76f160_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e87c05ab1e36b1c29be977537aafa9c3fb2bd6ec --- /dev/null +++ b/marked/Rel-18/38_series/38751/6a842e59ecf31b0d6f6721ac4e76f160_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4460a8ac09fc7482a1c70df1afca1f009e483f8ef1981642f5d89b91957d1bd7 +size 22946 diff --git a/marked/Rel-18/38_series/38751/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-18/38_series/38751/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c97c64c0a3ab9caabc88d7f8f96a6965173be27e --- /dev/null +++ b/marked/Rel-18/38_series/38751/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:395044f9b9abdc87cf765d8b5a16f08d5d426a013c5a4deb8f0c2773827f0494 +size 62779 diff --git a/marked/Rel-18/38_series/38751/6f1d6debd3f3eada4104f0302c912672_img.jpg b/marked/Rel-18/38_series/38751/6f1d6debd3f3eada4104f0302c912672_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64b65fbe47078410a3fade3bc80640a989b8034c --- /dev/null +++ b/marked/Rel-18/38_series/38751/6f1d6debd3f3eada4104f0302c912672_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4d01f48018d6987bf0e96d1a354d9933648519a925a585d34004ff264a4b03a +size 68167 diff --git a/marked/Rel-18/38_series/38751/6fe536731996880570f251da168376cf_img.jpg b/marked/Rel-18/38_series/38751/6fe536731996880570f251da168376cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..183b7fd0a346598867a51aaf358f881b8159247a --- /dev/null +++ b/marked/Rel-18/38_series/38751/6fe536731996880570f251da168376cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:579f97f986d72f3e4743c4c981a558761557e887543affb805dc04e58504f976 +size 74912 diff --git a/marked/Rel-18/38_series/38751/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-18/38_series/38751/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc9c6a91a90865abf6d841aa6634401ba2206abe --- /dev/null +++ b/marked/Rel-18/38_series/38751/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61f6742c6ddc4dc6db632d962fbfb7eef18c4d8cc47e31d43502c0514d159991 +size 66197 diff --git a/marked/Rel-18/38_series/38751/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-18/38_series/38751/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d243e4d5c6acff9c761400ee54b4e147db0cc51d --- /dev/null +++ b/marked/Rel-18/38_series/38751/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0563484421f30e967df9da3332c6a800949fc426e114363a33eade28baa8a862 +size 68623 diff --git a/marked/Rel-18/38_series/38751/77a781dfb114c3e2b399f876f1808cfd_img.jpg b/marked/Rel-18/38_series/38751/77a781dfb114c3e2b399f876f1808cfd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7415676051f18631a4a4e308c98212ae6d0c7df7 --- /dev/null +++ b/marked/Rel-18/38_series/38751/77a781dfb114c3e2b399f876f1808cfd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37ad51569ce01bec500e8c82baaf786c0418efd588d3bcd161aacb1b3ebc17df +size 119106 diff --git a/marked/Rel-18/38_series/38751/7c25323df7c76559bef6d25840be5262_img.jpg b/marked/Rel-18/38_series/38751/7c25323df7c76559bef6d25840be5262_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d57429fda9581ad311497164cc1af0d7acaf452 --- /dev/null +++ b/marked/Rel-18/38_series/38751/7c25323df7c76559bef6d25840be5262_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9ff07bb10a64eec693a5d8afc3dbfc78af091815eaea071ac8f403e4d3d475f +size 24535 diff --git a/marked/Rel-18/38_series/38751/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-18/38_series/38751/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8e32c0910aa8b52e86190344530ea1fea203488 --- /dev/null +++ b/marked/Rel-18/38_series/38751/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40e0c3cc2896c81d91048c9221c866d4825bb7a4fe76e2a4ce3425682f9b719e +size 47549 diff --git a/marked/Rel-18/38_series/38751/8a4275b35551f2ec9825a1aa442c0db1_img.jpg b/marked/Rel-18/38_series/38751/8a4275b35551f2ec9825a1aa442c0db1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..817d645004e052c3a04d6278bbfa89748f0c84d8 --- /dev/null +++ b/marked/Rel-18/38_series/38751/8a4275b35551f2ec9825a1aa442c0db1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24a1ca8d75d6517f292abc674b86b0325460ff9bfa4f79f1dd1e1c2e3937be21 +size 68473 diff --git a/marked/Rel-18/38_series/38751/8b06b57a6331adbe608b9c79baa2198e_img.jpg b/marked/Rel-18/38_series/38751/8b06b57a6331adbe608b9c79baa2198e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c84f34b4597c227f62308ee5f49652f1636d072f --- /dev/null +++ b/marked/Rel-18/38_series/38751/8b06b57a6331adbe608b9c79baa2198e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ce597b3de77417b3c04596bd9ac635f081d9cd55779f5790b95a1682cfc6468 +size 20861 diff --git a/marked/Rel-18/38_series/38751/8ba0063bcb9cdac03f1c4497526f1898_img.jpg b/marked/Rel-18/38_series/38751/8ba0063bcb9cdac03f1c4497526f1898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01ac728ee8da1c7549003e6fe3ae38c7dde9488a --- /dev/null +++ b/marked/Rel-18/38_series/38751/8ba0063bcb9cdac03f1c4497526f1898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2eb5a4422c19f12f592cf8da784603ebe72b057dabb28f33bbcf4fa70e2c25b +size 35321 diff --git a/marked/Rel-18/38_series/38751/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg b/marked/Rel-18/38_series/38751/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63f59fdbe6cae110e5524c1a4f5a8c58151e3460 --- /dev/null +++ b/marked/Rel-18/38_series/38751/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5a7bf5ab940a6265fb163b8a36780831fd25d57388acf7650eb4b1a74dcda6 +size 105090 diff --git a/marked/Rel-18/38_series/38751/954cd5620367df7dda5b7e9335a91234_img.jpg b/marked/Rel-18/38_series/38751/954cd5620367df7dda5b7e9335a91234_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e2ed38bee65ebd1334491683817edf6c3b478e --- /dev/null +++ b/marked/Rel-18/38_series/38751/954cd5620367df7dda5b7e9335a91234_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ed84da37a8adbd758dd216887e49c6278b2a87c55ee052f2a3d1595040e020c +size 25782 diff --git a/marked/Rel-18/38_series/38751/9f6e8230f2fab5fb10cba96fec859743_img.jpg b/marked/Rel-18/38_series/38751/9f6e8230f2fab5fb10cba96fec859743_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0e39d7d53f3ae47526ca7f258fb8a36b3f09d4a --- /dev/null +++ b/marked/Rel-18/38_series/38751/9f6e8230f2fab5fb10cba96fec859743_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:836e5ccc970812150d77f616b1f9dc2678e638f305345bc4dddbeabb2c30e07c +size 4269 diff --git a/marked/Rel-18/38_series/38751/a1545557e366b6302109d13360b199c3_img.jpg b/marked/Rel-18/38_series/38751/a1545557e366b6302109d13360b199c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7855be42a170672d71e31a8310d81507272b4329 --- /dev/null +++ b/marked/Rel-18/38_series/38751/a1545557e366b6302109d13360b199c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db91317df0651eb14840cd0aa70255e08b574a383207743b80f429989156edb8 +size 70671 diff --git a/marked/Rel-18/38_series/38751/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-18/38_series/38751/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce7753c0e6ea70925bf4a09a77de7247292246ca --- /dev/null +++ b/marked/Rel-18/38_series/38751/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9180cc3bff87f158d87109e113be8755d41efb256631302f97f305fcb06c25d +size 29339 diff --git a/marked/Rel-18/38_series/38751/b5c525e7df912952586920ac3d3e4c57_img.jpg b/marked/Rel-18/38_series/38751/b5c525e7df912952586920ac3d3e4c57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2dfea27865e55c774a6af85ff9e8fab1d92a8f5 --- /dev/null +++ b/marked/Rel-18/38_series/38751/b5c525e7df912952586920ac3d3e4c57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e302fe13b4b1798f164af600cf9b7b35353bc3d86d22c1dc92d4d1a79eaeec1 +size 33800 diff --git a/marked/Rel-18/38_series/38751/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-18/38_series/38751/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0dd4b944f48ae19e985aed949b6dbec2c372780 --- /dev/null +++ b/marked/Rel-18/38_series/38751/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ca086ecd38b8a08f15ab540eb3f86de419faa958e2e4187495b2f9616ae44ed +size 115820 diff --git a/marked/Rel-18/38_series/38751/c3ee41c6d46565ab4198d0a9c69108c5_img.jpg b/marked/Rel-18/38_series/38751/c3ee41c6d46565ab4198d0a9c69108c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fabff8923cfa9a24fcac1214d4aa728596211813 --- /dev/null +++ b/marked/Rel-18/38_series/38751/c3ee41c6d46565ab4198d0a9c69108c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f517c11c9279a45126f00c064f4ee40bdfae3d6fc436ca42f5b790e84abf720 +size 4185 diff --git a/marked/Rel-18/38_series/38751/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg b/marked/Rel-18/38_series/38751/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a539f8054d969633310cdad02ccdd7cbd16630cd --- /dev/null +++ b/marked/Rel-18/38_series/38751/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf5ebef6835bd50f8bc0c785d6891f4f8df76ae161525fc70b44903d8db80315 +size 33576 diff --git a/marked/Rel-18/38_series/38751/cd3eda8aa6ed827f9f1dfd9c906fbd98_img.jpg b/marked/Rel-18/38_series/38751/cd3eda8aa6ed827f9f1dfd9c906fbd98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16181a00b08e3397821e833b68b5d858c6d9c92f --- /dev/null +++ b/marked/Rel-18/38_series/38751/cd3eda8aa6ed827f9f1dfd9c906fbd98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:487962d87f0dbc48a712c54444f27042a39b2f0811500795ea68fdf64b30ab1c +size 11775 diff --git a/marked/Rel-18/38_series/38751/d2adade462af578f17e01b2a65b53c12_img.jpg b/marked/Rel-18/38_series/38751/d2adade462af578f17e01b2a65b53c12_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ea30ec010788698be120e514e4b37ce0e62f7a7 --- /dev/null +++ b/marked/Rel-18/38_series/38751/d2adade462af578f17e01b2a65b53c12_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f6de85706463bd8d03b73153ba1b09f5817d80ae008c9841439ec4856b10e86 +size 32684 diff --git a/marked/Rel-18/38_series/38751/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-18/38_series/38751/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b57f812bb6f3fda0c8ab4871a457512d5e61ed98 --- /dev/null +++ b/marked/Rel-18/38_series/38751/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5928191ed1ab272c5b1b6a0b58d9e14a4268fbc01c0a149fc764bac543bbb262 +size 11033 diff --git a/marked/Rel-18/38_series/38751/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-18/38_series/38751/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..058c8b1243adb5de30764b259a06ad94a255b24d --- /dev/null +++ b/marked/Rel-18/38_series/38751/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7d7e671c1345662ec273ea0caa69a67de8b9eff8ff15b5d68f7d3a020a5dcb1 +size 17756 diff --git a/marked/Rel-18/38_series/38751/dedb7f33ecb6f34c107951e75ceee9fd_img.jpg b/marked/Rel-18/38_series/38751/dedb7f33ecb6f34c107951e75ceee9fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..480249b95ba557420f20ac5a0ee326281683e799 --- /dev/null +++ b/marked/Rel-18/38_series/38751/dedb7f33ecb6f34c107951e75ceee9fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:009f6c8a08ac8b8c100605f9f3d0ad12f4abeb22604553e075b0ee3ab2e00b0e +size 22691 diff --git a/marked/Rel-18/38_series/38751/e51f9764097b236acbf8f544491dd24f_img.jpg b/marked/Rel-18/38_series/38751/e51f9764097b236acbf8f544491dd24f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3be165a52f8e6bb550339e227fab8fb7b3efbe37 --- /dev/null +++ b/marked/Rel-18/38_series/38751/e51f9764097b236acbf8f544491dd24f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3374612edfb12378a734d9f72fe7e7f3970327361efc900e21cdd99f86e253f +size 14333 diff --git a/marked/Rel-18/38_series/38751/e97d663314aff9c29bf8971323e6539e_img.jpg b/marked/Rel-18/38_series/38751/e97d663314aff9c29bf8971323e6539e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b473a757c9a9ee14ed0e6c32b6d41e11025841 --- /dev/null +++ b/marked/Rel-18/38_series/38751/e97d663314aff9c29bf8971323e6539e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15ba94d387a4439f42c3b88207e4e1ded5f221504c94efda8f6d532cf84dcc2d +size 46201 diff --git a/marked/Rel-18/38_series/38751/ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg b/marked/Rel-18/38_series/38751/ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47c8b29bd77e6fa79ac8bfce006eeac60b065798 --- /dev/null +++ b/marked/Rel-18/38_series/38751/ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30f97ff69618ed53c45aa885b2e213ebbd4935a9a869c06932866f9df3312d79 +size 37841 diff --git a/marked/Rel-18/38_series/38751/ed4ead5d57191d85eee9880ec32c4628_img.jpg b/marked/Rel-18/38_series/38751/ed4ead5d57191d85eee9880ec32c4628_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b91da34fecbc6c695f88c1ae3590bb7c70005cb7 --- /dev/null +++ b/marked/Rel-18/38_series/38751/ed4ead5d57191d85eee9880ec32c4628_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db1a6c187b1ed98eab308d43979ee6492ee8f6d781db0e246b3850ffc4ffdc31 +size 85581 diff --git a/marked/Rel-18/38_series/38751/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg b/marked/Rel-18/38_series/38751/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..245a129b97c49df55a33dca60dd368564d9d5399 --- /dev/null +++ b/marked/Rel-18/38_series/38751/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a100d9070372d7f6dc11b95eb20bfd6b26a3e5a17db473147560b04517ed15af +size 32768 diff --git a/marked/Rel-18/38_series/38751/f23ef4369fb548107b5533354d0aeee4_img.jpg b/marked/Rel-18/38_series/38751/f23ef4369fb548107b5533354d0aeee4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab4242b57e7d31da1bcebad33db23d216b86ba11 --- /dev/null +++ b/marked/Rel-18/38_series/38751/f23ef4369fb548107b5533354d0aeee4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cf0df56705118872ef52447cb1295e358ff9648598d6228aa010d5f3542cbc4 +size 9194 diff --git a/marked/Rel-18/38_series/38751/f880daa1cde4b71fcbaff2df81803a65_img.jpg b/marked/Rel-18/38_series/38751/f880daa1cde4b71fcbaff2df81803a65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f8d444971678b8d7fa86c49d049b8b02930f060 --- /dev/null +++ b/marked/Rel-18/38_series/38751/f880daa1cde4b71fcbaff2df81803a65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:137a4fc32f0c9d159004dd8dc933ce4cae102ba536377713c2b9a845e774e0ab +size 24652 diff --git a/marked/Rel-18/38_series/38751/f9473b6393648eb91fe2c266f711aebd_img.jpg b/marked/Rel-18/38_series/38751/f9473b6393648eb91fe2c266f711aebd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8414395f256ac8d227db45c519216ea74add629 --- /dev/null +++ b/marked/Rel-18/38_series/38751/f9473b6393648eb91fe2c266f711aebd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:817984c60bdf881a8f5378b6681c581024a81077f4a8a23200e06b07ac6df583 +size 7232 diff --git a/marked/Rel-18/38_series/38751/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/38_series/38751/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..055afda291a9596bfe60d3273704e63b3a9e63a5 --- /dev/null +++ b/marked/Rel-18/38_series/38751/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c88f2d5fcf2a8f6037f5438563706f3d4b5a58d24ceb6d16ea33db5d4d83f921 +size 98265 diff --git a/marked/Rel-18/38_series/38751/raw.md b/marked/Rel-18/38_series/38751/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ebd2f54a85d8bccc826067212a8b18ffd31da08e --- /dev/null +++ b/marked/Rel-18/38_series/38751/raw.md @@ -0,0 +1,1740 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) RF and demodulation requirements for NR frequency range 2 (FR2) multi-Rx chain DL reception; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------|-----------| +| Foreword ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions of terms, symbols and abbreviations ..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Background..... | 10 | +| 5 System assumptions ..... | 11 | +| 5.1 Constraint of test system ..... | 11 | +| 5.1.1 Source/Probe locations ..... | 11 | +| 5.1.2 Test point distribution..... | 11 | +| 5.2 Requirement applicability ..... | 12 | +| 5.3 Reference measurement channel..... | 13 | +| 6 UE RF requirement ..... | 16 | +| 6.1 Requirement concept..... | 16 | +| 6.1.1 General ..... | 16 | +| 6.1.2 Understanding of “panel” ..... | 16 | +| 6.1.3 Requirement metric ..... | 16 | +| 6.1.3.1 General..... | 16 | +| 6.1.3.2 Overall probability based on evaluation over the whole sphere ..... | 17 | +| 6.1.3.2.1 Probability expression..... | 17 | +| 6.1.3.2.2 OR combining ..... | 19 | +| 6.1.3.2.3 Arithmetic mean combining..... | 19 | +| 6.1.3.3 Overall probability based on weight per TRP pair ..... | 19 | +| 6.1.3.4 Summary ..... | 20 | +| 6.2 Simulation methodology ..... | 20 | +| 6.2.1 Simulation assumption ..... | 20 | +| 6.2.1 Simulation procedure..... | 21 | +| 6.3 Requirement design..... | 22 | +| 6.3.1 DL power..... | 22 | +| 6.3.2 Inter-beam interference..... | 23 | +| 6.3.2.1 Standalone antenna array configuration (Ideal Case)..... | 24 | +| 6.3.2.2 Realistic formfactor smart-phone (Practical Case)..... | 25 | +| 6.3.2.3 Summary ..... | 27 | +| 6.3.3 $\pm$ AoA separation..... | 28 | +| 6.3.4 UE orientation ..... | 30 | +| 6.3.5 AoA pairs for enhanced positioners ..... | 31 | +| 6.3.6 DL polarization combination..... | 32 | +| 6.3.7 NTC vs. ETC ..... | 37 | +| 6.3.8 Consideration of AoA separation ..... | 38 | +| 6.3.8.1 Candidate AoA separation ..... | 38 | +| 6.3.8.2 1AoA vs 2 AoA ..... | 38 | +| 6.3.8.3 Specified vs declared ..... | 39 | +| 7 Conclusion ..... | 40 | +| Annex A: Simulation results | 41 | +| A.1 General ..... | 41 | +| A.2 AoA offset distribution with system simulation ..... | 41 | +| A.3 Requirement applicability for sDCI and mDCI ..... | 43 | +| A.4 Evaluation of EIS-based requirement ..... | 44 | + +| | | | +|-----|-------------------------------------------------------|----| +| A.5 | Impact of UE orientation..... | 44 | +| A.6 | Impact of gain imbalance between antenna module ..... | 48 | +| A.7 | Test time estimates ..... | 52 | +| A.8 | Simulation campaign for requirement design ..... | 53 | + +# Annex B: Change history 56 + +| | | | +|-----------|---------------------------------------------------------------------|----| +| 1 | Scope..... | 7 | +| 2 | References..... | 7 | +| 3 | Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 | Terms..... | 8 | +| 3.2 | Symbols..... | 8 | +| 3.3 | Abbreviations ..... | 8 | +| 4 | Background ..... | 9 | +| 5 | System assumptions ..... | 10 | +| 5.1 | Constraint of test system ..... | 10 | +| 5.1.1 | Source/Probe locations ..... | 10 | +| 5.1.2 | Test point distribution..... | 10 | +| 5.2 | Requirement applicability ..... | 11 | +| 5.3 | Reference measurement channel..... | 12 | +| 6 | UE RF requirement..... | 15 | +| 6.1 | Requirement concept..... | 15 | +| 6.1.1 | General ..... | 15 | +| 6.1.2 | Understanding of “panel” ..... | 15 | +| 6.1.3 | Requirement metric ..... | 15 | +| 6.1.3.1 | General..... | 15 | +| 6.1.3.2 | Overall probability based on evaluation over the whole sphere ..... | 16 | +| 6.1.3.2.1 | Probability expression..... | 16 | +| 6.1.3.2.2 | OR combining ..... | 18 | +| 6.1.3.2.3 | Arithmetic mean combining..... | 18 | +| 6.1.3.3 | Overall probability based on weight per TRP pair ..... | 18 | +| 6.1.3.4 | Summary ..... | 19 | +| 6.2 | Simulation methodology ..... | 19 | +| 6.2.1 | Simulation assumption ..... | 19 | +| 6.2.1 | Simulation procedure..... | 20 | +| 6.3 | Requirement design..... | 21 | +| 6.3.1 | DL power..... | 21 | +| 6.3.2 | Inter-beam interference..... | 22 | +| 6.3.2.1 | Standalone antenna array configuration (Ideal Case)..... | 23 | +| 6.3.2.2 | Realistic formfactor smart-phone (Practical Case)..... | 24 | +| 6.3.2.3 | Summary ..... | 26 | +| 6.3.3 | $\pm$ AoA separation..... | 27 | +| 6.3.4 | UE orientation ..... | 29 | +| 6.3.5 | AoA pairs for enhanced positioners ..... | 29 | +| 6.3.6 | DL polarization combination..... | 31 | +| 6.3.7 | NTC vs. ETC ..... | 36 | +| 6.3.8 | Consideration of AoA separation ..... | 37 | +| 6.3.8.1 | Candidate AoA separation ..... | 37 | +| 6.3.8.2 | 1AoA vs 2 AoA ..... | 37 | +| 6.3.8.3 | Specified vs declared ..... | 38 | +| 7 | Conclusion ..... | 39 | + +# Annex A: Simulation results 40 + +| | | | +|-----|------------------------------------------------------|----| +| A.1 | General ..... | 40 | +| A.2 | AoA offset distribution with system simulation ..... | 40 | +| A.3 | Requirement applicability for sDCI and mDCI ..... | 42 | +| A.4 | Evaluation of EIS-based requirement ..... | 43 | + +A.5 Impact of UE orientation..... 43 +A.6 Impact of gain imbalance between antenna module ..... 48 +A.7 Test time estimates ..... 51 +A.8 Simulation campaign for requirement design ..... 52 +**Annex B: Change history 54** + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The objectives for NR frequency range 2 (FR2) multi-Rx chain DL reception from RF perspective are as follows. + +- Introduce necessary requirement(s) for enhanced FR2-1 UEs with simultaneous DL reception with two different QCL TypeD RSs on single component carrier with up to 4 layer DL MIMO +- Enhanced RF requirements: + - Specify RF requirements, mainly spherical coverage requirements, for devices with simultaneous reception from different directions with different QCL TypeD RSs + - The legacy spherical coverage requirement for reception from a single direction will be kept + - PC3 will be prioritized, other power classes should be considered after the PC3 requirements framework is finalized + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 38.871: "Study on NR frequency range 2 (FR2) Over-the-Air (OTA) testing enhancements". +- [3] R4-2219852, System Parameter Assumptions for Multi AoA Rx Testing, Keysight Technologies +- [4] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities". +- [5] R4-2217731, WF on FR2 UE RF requirements for 2AoA DL Rx, vivo +- [6] R4-2218755, Further views on multi-Rx chain DL reception in FR2, Sony, Ericsson +- [7] R4-2300709, On UE RF requirements for 2AoA FR2 DL MIMO, Qualcomm Incorporated[8] +R4-2305750, Further views on multi-Rx chain DL reception in FR2, Sony, Ericsson +- [9] RP-231452, Revised WID: Requirement for NR frequency range 2 (FR2) multi-Rx chain DL reception, Qualcomm +- [10] R4-2307232, Discussion on System parameter assumption, UE architecture and conditions of UE RF requirements, Nokia, Nokia Shanghai Bell +- [11] R4-2218042, On UE RF requirements for 2AoA FR2 DL MIMO, Qualcomm +- [12] R4-2300146, Discussion for FR2 multi-Rx FOM, Murata Manufacturing Co., Ltd. +- [13] R4-2300949, Discussion on UE RF requirements for simultaneous DL, LG Electronics +- [14] R4-2301572, Evaluation on UE requirement of multi-Rx DL reception, vivo + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|-------------------------------------------| +| AoA | Angle of Arrival | +| DUT | Device Under Test | +| MTRP | Multiple Transmission and Reception Point | +| DCI | Downlink control information | +| DL | Downlink | +| RSRP | Reference signal received power | +| SINR | Signal-to-noise and interference ratio | + +# 4 Background + +The existing Rel-15 NR FR2 minimum UE requirements are defined with an assumption that UE is equipped with a single antenna panel or two antenna panels but only capable to perform DL reception using a single RX beam/chain reception. Furthermore, the UE performance requirements are limited for DL MIMO rank 1 and 2. In FR2, 4-layer MIMO reception requires beam reception from at least two directions. Although this is supported by the MIMO features since Rel-15, no performance requirements have yet been specified. This is important for high-rate MIMO in FR2, as well as for FR2 HST scenarios. + +During Rel-16 and Rel-17, the support of NR FR2 CA with IBM (Independent Beam Management) with simultaneous DL reception on different component carriers from the co-located and non-co-located TRPs was defined. The IBM concept implies a UE is capable of DL simultaneous reception on different UE panels/chains using separate beams on different component carriers and requires improved UE baseband and RF capabilities (multiple baseband chains and support of multiple antenna panels). + +Several enhancements to enable efficient and robust DL multi-TRP/panel operation were introduced in the Rel-16 NR eMIMO WI. For instance, DL transmission schemes with simultaneous and non-simultaneous multi-beam reception from multiple TRPs/panels were introduced. The simultaneous reception may require support of simultaneous multi-panel operation with several independent RX beams/chains at the UE side. As part of this item, a new FR2 UE capability for simultaneous multi-beam reception was introduced (simultaneousReceptionDiffTypeD-r16). However, no RF, RRM or performance requirements were defined in Rel-16 and Rel-17 for FR2 UEs with simultaneousReceptionDiffTypeD-r16 capability. + +Enhanced NR FR2 UEs with multi-beam simultaneous reception and multiple RX chains can provide a meaningful performance improvement in FR2 improving both demodulation performance (4-layer DL MIMO), RRM performance and improve RF spherical coverage. This work item aims to introduce the requirements for UEs capable of multi-beam/chain simultaneous DL reception on a single component carrier to achieve improved RF, RRM and UE demodulation performance. + +Different implementation scenarios could be considered at the UE. Single-TCI reception on different beams has been supported by the RAN1 specifications since Rel-15 via the Type I codebook, which could be achieved at the UE with either a single panel or multiple panels. Alternatively, dual TCI operation can be combined with the Rel-17 mTRP framework even if the base station is actually deployed as a single TRP. + +This WI therefore provides the requirements for both single and dual TCI assumptions to specify requirements for reception of 4-layer downlink MIMO with simultaneous reception at the UE from two different directions. + +# 5 System assumptions + +## 5.1 Constraint of test system + +The RF requirement and its test system have a close relationship for multi-Rx UE, and RF Requirement discussions need to consider testability issue so that the defined requirement can be properly verified. 5.1.1 and 5.1.2 record the discussion in RF session and more details on test system can be found in [2]. + +### 5.1.1 Source/Probe locations + +In theory, the UE performance can only be fully realized when any AoA pair on the sphere is tested, but considering the test complexity and time, a test system with full degrees of freedom for 2 active AoA is not pursued in R18, and some intermediate solutions have been proposed: + +- Option 1: One Fixed AoA1 (e.g. Peak) + Full set AoA2. +- Option 2: Multiple AoA1 + Full set AoA2. +- Option 3: Fixed offset between the two AoAs, both probes swept simultaneously. + +Both option 1 and option 2 also require a test system with full degree of freedom because the separation between 2AoA still need to be variable, so the fixed relative AoA separation is considered as baseline for test setup and requirement design as show in Figure 5.1.1-1. For option 3, there are two variants: the first one uses the legacy positioner with 2 axes (either distributed or otherwise), and the second one uses an enhanced positioner with 3 degrees of freedom (3-axis positioner). + +![Figure 5.1.1-1: Illustration for fixed relative AoA separation. The diagram shows a spherical coordinate system with a Device Under Test (DUT) at the center. A blue probe is fixed at AoA1 on the x-axis. A red probe is at AoA2, with its position indicated by a red arrow. The DUT is shown as a rectangular box with a yellow circular arrow indicating rotation. The sphere is represented by a grid of latitude and longitude lines.](475caf31ae90b878f12d651b689cc9d1_img.jpg) + +Figure 5.1.1-1: Illustration for fixed relative AoA separation. The diagram shows a spherical coordinate system with a Device Under Test (DUT) at the center. A blue probe is fixed at AoA1 on the x-axis. A red probe is at AoA2, with its position indicated by a red arrow. The DUT is shown as a rectangular box with a yellow circular arrow indicating rotation. The sphere is represented by a grid of latitude and longitude lines. + +Figure 5.1.1-1 Illustration for fixed relative AoA separation + +### 5.1.2 Test point distribution + +In [3], the DL directions perceived by DUT is analysed. Due to the lack of full degree of freedom in the test system, when the probe is aligned with different axis, the test point distribution will also be different. Table 5.1.2-1 show the case when AoA separation is $60^\circ$ as an example. + +Table 5.1.2-1 DL direction perceived by the DUT from two different system configurations when the AoA separation is $60^\circ$ + +| | Probes in the xz plane | Probes in the yz plane | +|--|------------------------|------------------------| +|--|------------------------|------------------------| + +| | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration | Diagram of a test system with a spherical coordinate system. A probe is at P0. The sphere has grid points at P60, P120, and P150. The sphere is mounted on a base with a vertical axis. | Diagram of a test system with a spherical coordinate system. A probe is at P0. The sphere has grid points at P60, P120, and P150. The sphere is mounted on a base with a vertical axis. | +| Constant-step | 3D plot of a sphere with a constant-step grid. The grid points are blue dots on a gray sphere. The sphere has a coordinate system with X, Y, and Z axes. | 3D plot of a sphere with a constant-step grid. The grid points are blue dots on a gray sphere. The sphere has a coordinate system with X, Y, and Z axes. | +| Constant-density | 3D plot of a sphere with a constant-density grid. The grid points are blue dots on a gray sphere. The sphere has a coordinate system with X, Y, and Z axes. | 3D plot of a sphere with a constant-density grid. The grid points are blue dots on a gray sphere. The sphere has a coordinate system with X, Y, and Z axes. | + +It is evident that no matter whether a constant-step or constant-density grid is used, when AoA1 traverse all test grid, the distribution of AoA2 will become irregular, when the probes are located in yz plane in the example test system above. Also evident is that for probe in the xz plane in the example system and a constant step-size grid, the regularity of the grid is preserved for both sources. Consequently, TE sources/probes that lie in the plane of constant phi with respect to the coordinate system defined by the positioner axes and a constant-step grid is considered as the primary configuration for test setup and requirement discussion. + +## 5.2 Requirement applicability + +For DL mTRP, there are two basic schemes are designed – single-DCI and multi-DCI, which are indicated by optional capabilities as shown below [4]. + +Table 5.2-1 Capabilities for multi-Rx UE + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| singleDCI-SDM-scheme-r16
Indicates whether the UE supports single DCI based spatial division multiplexing scheme. | +| multiDCI-MultiTRP-r16
Indicates whether the UE supports multi-DCI based multi-TRP PDSCH/PUSCH operation and support of fully/partially overlapping PDSCHs in time and non-overlapping in frequency. | +| ... | +| overlapPDSCHsFullyFreqTime-r16
Indicates the maximal number of PDSCH scrambling sequences per serving cell when the UE supports PDSCHs with fully overlapping Resource Elements. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 . | +| ... | +| overlapPDSCHsInTimePartiallyFreq-r16
Indicates whether the UE supports PDSCHs with partially overlapping Resource Elements. The UE that indicates support of this feature shall support overlapPDSCHsFullyFreqTime-r16 . | + +Figure 5.2-1 illustrates the difference between multiple DCI and single DCI, and Table 5.2-2 summarizes different characteristics of single DCI and multi-DCI respectively. + +![Figure 5.2-1: illustration of multiple DCI and single DCI. The diagram shows two scenarios of downlink transmission from two TRPs (TRP1 and TRP2) to a UE. In the 'multiple DCI' scenario (left), TRP1 sends DCI1 (blue) and Data1 (red), while TRP2 sends DCI2 (blue) and Data2 (red). In the 'single DCI' scenario (right), TRP1 sends DCI (blue) and Data1 (red), while TRP2 sends Data2 (red) only. A legend indicates that red arrows represent DL Data and blue arrows represent DL Control.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` + +graph LR + subgraph "Multiple DCI" + TRP1_M[TRP1] -- "DCI1 (Control)" --> UE_M[UE] + TRP1_M -- "Data1 (Data)" --> UE_M + TRP2_M[TRP2] -- "DCI2 (Control)" --> UE_M + TRP2_M -- "Data2 (Data)" --> UE_M + end + subgraph "Single DCI" + TRP1_S[TRP1] -- "DCI (Control)" --> UE_S[UE] + TRP1_S -- "Data1 (Data)" --> UE_S + TRP2_S[TRP2] -- "Data2 (Data)" --> UE_S + end + +``` + +Figure 5.2-1: illustration of multiple DCI and single DCI. The diagram shows two scenarios of downlink transmission from two TRPs (TRP1 and TRP2) to a UE. In the 'multiple DCI' scenario (left), TRP1 sends DCI1 (blue) and Data1 (red), while TRP2 sends DCI2 (blue) and Data2 (red). In the 'single DCI' scenario (right), TRP1 sends DCI (blue) and Data1 (red), while TRP2 sends Data2 (red) only. A legend indicates that red arrows represent DL Data and blue arrows represent DL Control. + +Figure 5.2-1: illustration of multiple DCI and single DCI + +Table 5.2-2: Comparison between single DCI and multiple DCI + +| Single DCI | Multi-DCI | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
  • ● Single transport block split across both TRPs. Allows true 4x4 demod because of single TB
  • ● common MCS, RB allocation
  • ● At the Tx side, each 2-port TRP is enabled for NCJT with up to 4L (non-coherent joint transmission).
|
  • ● Separate transport blocks
  • ● Independent MCS, RB allocations for each TRP (i.e spatial multiplexing is not guaranteed)
  • ● ‘PDSCH’ is structured as 2 parallel PDSCH channels, each with up to rank 2 – each layer pair shows up as interference to the other. It is up to UE implementation whether it can do joint 4L demod.
| + +The performance of UEs supporting single-DCI and multi-DCI may be different but considering the requirement only guarantee the minimum performance and unified requirement is friendly to verification, the RF requirement is defined based on that multi-DCI with understanding that UE supporting single-DCI can also meet the requirement. The requirement applicability can be further explained as: + +- The same requirement shall be applied to the UEs supporting either of the following two capability combinations: + - UE capabilities “multiDCI-MultiTRP-r16” and “overlapPDSCHsFullyFreqTime-r16”. + - UE capabilities “multiDCI-MultiTRP-r16” and “overlapPDSCHsInTimePartiallyFreq-r16”. +- No need to discuss and define the RF requirement for the UEs only supporting “multiDCI-MultiTRP-r16”. + +## 5.3 Reference measurement channel + +UE RF requirements for Multi-RX DL are specified for simultaneous Multi-RX chain DL reception from different directions for FR2-1 UE supporting up to 4 layers. RAN4 has agreed that UE RF requirements for simultaneous reception from different directions shall be based on single-layer reception for each DL direction with dual TCI + +configuration, i.e., total 2 layers for both directions. Existing Reference Measurement Channel (RMC) for UE RF requirement is limited to 1 layer, thus it is necessary to specify new RMC for 2 layer scenario for UE RF. + +Depending on the DCI schemes the UE supports, RMC may be different. + +For multi-DCI, transport blocks are separated for receptions from different directions, therefore throughput for each layer could be separately obtained. From the perspective of each TRP, the legacy RMC can be reused; + +For single DCI, transport block is split across both TRPs for single DCI, therefore only an overall throughput of the 2 layer reception can be obtained. The legacy RMC can not be reused and a new RMC is needed. + +RAN4 achieves following conclusion: + +- For the UE supporting multi-DCI, the RMC of the single carrier can be reused for each layer, which is specified in Annex A.3.3.2-1 and A.3.3.2-2 of TS 38.101-2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1 of TS 38.101-2); +- For the UE supporting single DCI, the RMC is shown as Table 5.3-1 and Table 5.3-2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1 of TS 38.101-2) + +**Table 5.3-1: Fixed Reference Channel for Receiver Requirements (SCS 60 kHz, TDD)** + +| Parameter | Unit | Value | | | +|------------------------------------------------------------------------------------------------|------|--------|--|---------------| +| Channel bandwidth | MHz | 50 | | 100 200 | +| Subcarrier spacing configuration $\mu$ | | 2 | | 2 | +| Allocated resource blocks | | 66 | | 132 264 | +| Subcarriers per resource block | | 12 | | 12 | +| Allocated slots per Frame | | 23 | | 23 | +| MCS index | | 4 | | 4 | +| Modulation | | QPSK | | QPSK | +| Target Coding Rate | | 1/3 | | 1/3 | +| Maximum number of HARQ transmissions | | 1 | | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from $\{0, \dots, 79\}$ (NOTE 5) | Bits | N/A | | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from $\{1, \dots, 79\}$ (NOTE 6) | Bits | 8456 | | 16896 33816 | +| Transport block CRC | Bits | 24 | | 24 | +| LDPC base graph | | 1 | | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from $\{0, \dots, 79\}$ (NOTE 5) | CBs | N/A | | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from $\{1, \dots, 79\}$ (NOTE 6) | CBs | 1 | | 2 2 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from $\{0, \dots, 79\}$ (NOTE 5) | Bits | N/A | | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from $\{1, \dots, 79\}$ (NOTE 6) | Bits | 28512 | | 57024 114048 | +| Max. Throughput averaged over 1 frame | Mbps | 19.449 | | 38.861 77.777 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 8) = \{3,4,5,6,7\}$ for i from $\{0, \dots, 79\}$ together with the TDD UL-DL configuration specified in A2.3. +NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 8) = \{0,1,2\}$ for i from $\{0, \dots, 79\}$ together with the TDD UL-DL configuration specified in A2.3. + +**Table 5.3-2: Fixed Reference Channel for Receiver Requirements (SCS 120 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|--------|--------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | 400 | +| Subcarrier spacing configuration $\mu$ | | 3 | 3 | 3 | 3 | +| Allocated resource blocks | | 32 | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame | | 47 | 47 | 47 | 47 | +| MCS index | | 4 | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0, ..., 159} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1, ..., 159} (NOTE 6) | Bits | 4096 | 8456 | 16896 | 33816 | +| Transport block CRC | Bits | 16 | 24 | 24 | 24 | +| LDPC base graph | | 2 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0, ..., 159} (NOTE 5) | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1, ..., 159} (NOTE 6) | CBs | 1 | 1 | 2 | 2 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0, ..., 159} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1, ..., 159} (NOTE 6) | Bits | 13824 | 28512 | 57024 | 114048 | +| Max. Throughput averaged over 1 frame | Mbps | 19.660 | 40.589 | 81.101 | 162.317 | +| NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. | | | | | | +| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). | | | | | | +| NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms | | | | | | +| NOTE 4: Slot i is slot index per 2 frames | | | | | | +| NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 16) = \{7, \dots, 15\}$ for i from {0, ..., 159} together with the TDD UL-DL configuration specified in A2.3. | | | | | | +| NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 16) = \{0, \dots, 6\}$ for i from {0, ..., 159} together with the TDD UL-DL configuration specified in A2.3. | | | | | | + +# 6 UE RF requirement + +## 6.1 Requirement concept + +### 6.1.1 General + +The requirement concept is mainly categorized into two types in the discussion. One is based on 2AoA directional sensitivity statistics, which is similar to the legacy REFSENS and spherical coverage, e.g., “joint” sensitivity, sensitivity tolerance, new CCDF formula, etc., and the details of proposals can be found in [5]. The most critical problem with this approach is that when two AoAs need to search for sensitivity simultaneously, the test complexity rises significantly. Another is based on the functionality verification under 2AoAs with a fixed DL power level [6], and the merit of this approach is that it can reduce the test overhead, but the concern is that such simplification may not reasonably validate UE performance. In [7], the simulation results to compare these two approaches above are provided. + +**Table 6.1.1 Simulation results for PC3 UE under different requirement concept** + +| AoA separation (deg) | Modules on opposite faces | | Modules on adjacent faces | | +|----------------------|------------------------------------------------------|-----------------------------------------|------------------------------------------------------|-----------------------------------------| +| | Coverage fraction ‘M’ for functionality verification | Coverage fraction from sensitivity CCDF | Coverage fraction ‘M’ for functionality verification | Coverage fraction from sensitivity CCDF | +| 150 | 49.4 % | 49.4 % | 25.2 % | 25.3 % | +| 120 | 49.4 % | 49.2 % | 35.6 % | 36.0 % | +| 90 | 35.2 % | 35.6 % | 33.7 % | 34.0 % | +| 60 | 2.5 % | 2.5 % | 25.5 % | 27.3 % | + +The results show that there is good correlation between the coverages predicted by the two methods. To alleviate the test overhead for multi-Rx UE, the functionality verification with fixed DL power is agreed as requirement concept. + +### 6.1.2 Understanding of “panel” + +The terminology “panel” appears often in FR2 RF discussion but there is never a clear interpretation, and the reason is that this term is closely related to the UE implementation and behaviour. To avoid put unnecessary restriction on UE design, the “panel” will be not referenced in both final RF requirement and test configuration. However, from RF requirement design perspective, a clear meaning of “panel” is very helpful for the discussion, and the following logical “panel” definition is used which is only focus on its behaviour rather than physical implementation. + +“Panel” is defined as a group of antenna element that controls beam independently and has the following attributes + +- Within a panel, one beam can be selected and used for DL reception. +- Across different panels, multiple beams (each selected per panel) may be used for DL reception. +- ‘Beam’ is assumed to mean spatial filter associated with reception. +- A physical panel with dual polarization is assumed as two “panels”. + +### 6.1.3 Requirement metric + +#### 6.1.3.1 General + +Two similar proposals were made along with the respective mathematical framework. Both aim to capture the probability of supporting 2 AoA reception for a given AoA separation but differ in the weighting assigned to the outcomes of all tested pairs. One method aims to capture the overall probability based on evaluation over the entire sphere, while the other limits evaluation to some subset of AoA pairs. + +#### 6.1.3.2 Overall probability based on evaluation over the whole sphere + +##### 6.1.3.2.1 Probability expression + +The ideal metric for the requirement is the probability of supporting 2AoA reception when the 2 AoAs are randomly selected. This is the general case, assuming no TE constraints. To this end, a regional probability metric is first established to capture the probability of a UE to support 2TRP Rx, given a fixed (regional) location of one of the TRPs (from the UE's perspective). The sample space for this probability is the collection of all AoA pairs formed from TRP2 locations that cover the entire sphere (blue surface in the 'ideal case' in figure 6.1.3.2-1) and a given TRP1 location (white star in the 'ideal case' in figure 6.1.3.2-1). + +![A blue circle representing a sphere, with a white star in the upper-left quadrant representing the fixed TRP1 location.](c3ee41c6d46565ab4198d0a9c69108c5_img.jpg) + +A blue circle representing a sphere, with a white star in the upper-left quadrant representing the fixed TRP1 location. + +*Ideal case: Each TRP is presented to the UE at any random location (white star). The UE is evaluated when second TRP is moved across all locations on the test sphere (blue surface)* + +**Figure 6.1.3.2-1: 'Regional Probability' sample space for the general AoA pair case** + +Specifically, for the fixed TRP ('TRP1') at some AoA $(\theta_1, \phi_1)$ , the regional probability is evaluated as a spatial average of the pass/fail outcomes for all locations of TRP2.: + +$$P_{regional,general}(\theta_1, \phi_1) = \frac{\oint\oint PF(\theta_1, \phi_1, \theta_2, \phi_2) dS_2}{\oint\oint dS_2}$$ + +Where: + +- The AoA of the fixed TRP ('TRP1') is $(\theta_1, \phi_1)$ . +- The AoA of the TRP paired with the fixed TRP ('TRP2') is $(\theta_2, \phi_2)$ . +- $PF(\theta_1, \phi_1, \theta_2, \phi_2)$ is the pass/fail outcome (1/0 respectively) of the 2TRP functionality test under the agreed UERF test conditions. +- $dS_2$ is the elemental area associated with the AoA of TRP2 + +An overall probability that a UE can support 2TRP operation when the TRPs are positioned randomly around the UE can be defined by taking a spatial average of the regional probability over all possible positions of the fixed TRP on the sphere: + +$$P_{overall,general} = \frac{\oint\oint P_{regional,general}(\theta_1, \phi_1) dS_1}{\oint\oint dS_1}$$ + +This expression can be re-written as: + +$$P_{overall,general} = \frac{\oint\oint \oint\oint PF(\theta_1, \phi_1, \theta_2, \phi_2) dS_2 dS_1}{\oint\oint dS_1 \cdot \oint\oint dS_2}$$ + +While this overall probability was derived by arbitrarily choosing a TRP whose location was fixed for the regional probability, the final expression is symmetric for both TRPs. We can therefore conclude that the choice of the specific TRP to use as the 'fixed TRP' for the calculation is not significant, at least for the general case where there are no restrictions on availability of test AoA pairs. + +The regional probability formulation above is now modified for discrete sampling on for a lat-long (constant step-size grid). The expression for constrained probability becomes a weighted sum over all sample points: + +$$P_{regional,general}(\theta_1, \phi_1) = \sum_{\theta_2} \sum_{\phi_2} \{PF(\theta_1, \phi_1, \theta_2, \phi_2) \cdot AW(\theta_2)\}$$ + +Where: + +- $AW(\theta_x)$ are the area weights associated with the entire sample space of grid points where TRPx can be located. +In this case, the weights would be the discretized version of $\frac{dS_2}{\phi dS_2}$ , or $\frac{\Delta S_2}{S}$ + +The overall probability can similarly be discretized as: + +$$P_{overall,general} = \sum_{\theta_1} \sum_{\varphi_1} \{P_{regional,general}(\theta_1, \varphi_1) \cdot AW(\theta_1)\}$$ + +Where AW shares the same meaning as defined above. + +This formulation highlights that if the regional probability can be established for every point on the sphere, it is possible to define an overall probability for the UE. It further highlights that it is possible to decouple the grid used to define the regional probabilities and the grids used by the paired TRP directions to compute the regional probabilities. + +![Flowchart showing the general method for calculating overall probability: Choose some spherical grid -> At each grid point (theta, phi) calculate the probability of supporting 2TRP DL for a second AoA (Regional Probability) -> Calculate spatial average of regional probabilities (Overall Probability to support 2TRP DL)](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +``` + +graph TD + A[Choose some spherical grid] --> B["At each grid point (θ,φ) +calculate the probability of +supporting 2TRP DL for a +second AoA +(Regional Probability)"] + B --> C["Calculate spatial average of +regional probabilities +(Overall Probability to +support 2TRP DL)"] + +``` + +Flowchart showing the general method for calculating overall probability: Choose some spherical grid -> At each grid point (theta, phi) calculate the probability of supporting 2TRP DL for a second AoA (Regional Probability) -> Calculate spatial average of regional probabilities (Overall Probability to support 2TRP DL) + +To modify the formulation above to reflect TE constraints where each grid point (blue star in figure 2.1.3-1) is paired with just 2 unique grid points (green stars in figure 6.1.3.2-2) the equation for the metric can be rewritten as: + +$$P_{overall,constrained} = \sum_{\theta_1} \sum_{\varphi_1} \{P_{regional,constrained}(\theta_1, \varphi_1) \cdot AW(\theta_1)\}$$ + +Where the regional constrained probability calculated at each grid point is modified to depend on a reduced set of test AoA pairs. + +![Diagram of a sphere showing a blue star (TRP1) and an orange circle representing possible TRP2 locations. Two green stars mark the intersection points of the circle and a plane passing through the sphere's center and the TRP1 location.](f9473b6393648eb91fe2c266f711aebd_img.jpg) + +Diagram of a sphere showing a blue star (TRP1) and an orange circle representing possible TRP2 locations. Two green stars mark the intersection points of the circle and a plane passing through the sphere's center and the TRP1 location. + +*The orange circle represents the set of all TRP2 locations that are separated from the TRP1 location (blue star) by some fixed AoA separation.* + +*The two locations (green stars) that the paired TRP (TRP2) can assume in the TE correspond to the intersection of the circle of possible paired TRP locations and the projection of the plane containing the UE and sources on the test sphere.* + +**Figure 6.1.3.2-2: ‘Constrained Regional Probability’ sample space for the case constrained by practical TE considerations** + +There are multiple ways to quantify this constrained regional probability, described in subsections below. + +##### 6.1.3.2.2 OR combining + +In this method, the constrained regional probability for each point is considered '1' if that point is successful in at least one of the AoA pairs it participates in. This strategy represents the 'OR combining' method. + +$$P_{regional,constrained}(\theta_1, \varphi_1) = \mathbf{OR}\{PF(AoA_{pair\#1}), PF(AoA_{pair\#2})\}$$ + +##### 6.1.3.2.3 Arithmetic mean combining + +Note that mathematical formulation of the regional probability in the general case shows it to be a weighted sum of all P/F outcomes. The area weights are those associated with the entire sample space of grid points that contribute to the weighted sum. When the entire sample domain for the constrained regional probability consists only of 2 sample points, the weights for each sample in that sample space equal 0.5. The arithmetic mean method for a small number of equidistant points is therefore consistent with the general formulation for regional probability: + +$$P_{regional,constrained}(\theta_1, \varphi_1) = \left\{ \frac{PF(AoA_{pair\#1}) + PF(AoA_{pair\#2})}{2} \right\}$$ + +#### 6.1.3.3 Overall probability based on weight per TRP pair + +Recall that if the AoAs of the two TRPs can be arbitrary values rather than with a fixed offset in between, a full double surface integral needs to be performed to sweep through all the possible combinations of AoA1( $\theta_1, \varphi_1$ ) and AoA2( $\theta_2, \varphi_2$ ) to calculate the probability $P$ that the device can successfully connect to two TRPs + +$$P = \frac{f}{f_{total}} \quad (6.1.3.3-1)$$ + +where + +$$f = \oint_{S1,S2} F(\theta_1, \varphi_1, \theta_2, \varphi_2) \sin \theta_2 d\theta_2 d\varphi_2 \sin \theta_1 d\theta_1 d\varphi_1 \quad (6.1.3.3-2)$$ + +$$f_{total} = \oint_{S1,S2} \sin \theta_1 d\theta_1 d\varphi_1 \sin \theta_2 d\theta_2 d\varphi_2 = (4\pi)^2 \quad (6.1.3.3-3)$$ + +$F(\theta_1, \varphi_1, \theta_2, \varphi_2) = 1$ if both panels have SINR larger than -1 dB; otherwise, it equals 0. In this case, it can be observed that the corresponding weight factor for each TRP pair should be $\sin \theta_1 * \sin \theta_2$ . + +Now consider that only a fixed offset would be applied to between AoA1 and AoA2, the same weight factor can still be used if we see this as a subset of the full double surface integral. However, since a constant offset between AoA1 and AoA2 needs to be applied (e.g., AoA2 = AoA1 + offset), a Dirac delta function needs to be plugged into the integral $\delta(AoA2 - (AoA1 + offset))$ , so that we only count the AoA pairs which has the required offset. + +Assuming a case that the offset is only applied to $\theta$ plane, e.g., $\theta_2 = \theta_1 + c$ , $\varphi_2 = \varphi_1$ , where $c$ is a constant offset, the integral of $f$ in 6.1.3.3-2 becomes $\hat{f}$ as below. Please note that since $\theta_2$ is from $0^\circ$ to $180^\circ$ , $\theta_1 + c$ needs to be wrapped within the same range. + +$$\hat{f} = \oint_{S1,S2} F(\theta_1, \varphi_1, \theta_2, \varphi_2) \delta(\theta_2 - (\theta_1 + c)) \delta(\varphi_2 - \varphi_1) \sin \theta_2 d\theta_2 d\varphi_2 \sin \theta_1 d\theta_1 d\varphi_1 \quad (6.1.3.3-4)$$ + +by integral over $\theta_2$ and $\varphi_2$ , the double surface integral will be degraded to a single surface integral, as shown in 6.1.3.3-5. The detail of derivation can be found in the appendix. + +$$\hat{f} = \oint_{S_1} F(\theta_1, \varphi_1, \theta_1 + c, \varphi_1) \sin \theta_1 \sin(\theta_1 + c) d\theta_1 d\varphi_1 \quad (6.1.3.3-5)$$ + +Moreover, to correctly calculate the probability, the total weight $\hat{f}_{total}$ (assuming all test points can pass the SINR threshold -1dB) also needs to be correctly computed as well. For a completed double surface integral, the total weight $f_{total}$ equals $(4\pi)^2$ . However, for the subset that has a fixed offset between AoA1 and AoA2, the total weight $\hat{f}_{total}$ varies with the AoA offset values, which are shown in Figure 6.1.3.3-1. The value is computed numerically with the integral below but with constraint that $\theta_1 + c$ should be wrapped within the range from $[0^\circ, 180^\circ]$ . + +$$\hat{f}_{total} = \oint_{S_1} \sin \theta_1 \sin(\theta_1 + c) d\theta_1 d\varphi_1 \quad (6.1.3.3-6)$$ + +![Figure 6.1.3.3-1: A line graph showing the total weight (y-axis, ranging from 6 to 10) versus offset (x-axis, ranging from -180 to 180 degrees). The curve is periodic, showing a minimum weight of approximately 6.4 at offsets of -90 and 90 degrees, and a maximum weight of approximately 9.8 at offsets of 0 and 180 degrees.](ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg) + +| Offset (degrees) | Total Weight | +|------------------|--------------| +| -180 | ~9.8 | +| -150 | ~8.5 | +| -120 | ~7.2 | +| -90 | ~6.4 | +| -60 | ~7.2 | +| -30 | ~8.5 | +| 0 | ~9.8 | +| 30 | ~8.5 | +| 60 | ~7.2 | +| 90 | ~6.4 | +| 120 | ~7.2 | +| 150 | ~8.5 | +| 180 | ~9.8 | + +Figure 6.1.3.3-1: A line graph showing the total weight (y-axis, ranging from 6 to 10) versus offset (x-axis, ranging from -180 to 180 degrees). The curve is periodic, showing a minimum weight of approximately 6.4 at offsets of -90 and 90 degrees, and a maximum weight of approximately 9.8 at offsets of 0 and 180 degrees. + +Figure 6.1.3.3-1 The total weight $\hat{f}_{total}$ with different AoA offset values + +With $\hat{f}$ and $\hat{f}_{total}$ , the percentage of spherical coverage can be computed. As the results are weighted per TRP pair, the + offset and -offset pairs will be treated as two pairs or samples. The coverage probability $\hat{P}$ can be computed as: + +$$\hat{P} = \frac{\oint_{S_1} [F(\theta_1, \varphi_1, \theta_1 + c, \varphi_1) \sin \theta_1 \sin(\theta_1 + c) + F(\theta_1, \varphi_1, \theta_1 - c, \varphi_1) \sin \theta_1 \sin(\theta_1 - c)] d\theta_1 d\varphi_1}{\oint_{S_1} [\sin \theta_1 \sin(\theta_1 + c) + \sin \theta_1 \sin(\theta_1 - c)] d\theta_1 d\varphi_1}$$ + +#### 6.1.3.4 Summary + +After considering the Pros and Cons of different methods, RAN4 agreed to use overall probability with arithmetic mean combining as the metric for this feature. + +## 6.2 Simulation methodology + +### 6.2.1 Simulation assumption + +Based on the requirement concept in 6.1.1, the simulation assumptions are agreed as shown in Table 6.2.1. + +**Table 6.2.1 Simulation assumptions** + +| | Simulation assumption | Note | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------| +| # of antenna module | 2 , dual polarized | | +| array of element antenna in each antenna module | 4x1 | | +| Antenna location (front, back, top-side, left-side, right-side, bottom-side) | combination of the lists (e.g., left and right, Right and Top, Left and top, .etc.) | Two antenna modules located at same side is not precluded | + +### 6.2.1 Simulation procedure + +The details of simulation procedure are described below: + +1. For one UE implementation + 2. For one UE orientation + 3. Run EM simulation to obtain per-beam antenna gain patterns + - Constant step size is suggested $\leq 5^\circ$ + - Performance difference between V/H element can be considered + - Normalize antenna gain to align with the gain drop between peak EIS and spherical coverage in current spec + - Other calibration method also can be used. + 4. For one angular separation + 5. For one test grid point in 3D scan + - Select beam based on RSRP (or SINR) + - 5.1 Calculate SINR of AoA+ and AoA- respectively + - $\text{SINR} = P\_signal / (\text{Noise} + P\_interf)$ + +Where the $P\_signal$ is the power of wanted signal and the $P\_interf$ is the power of interference, $\text{Noise(dBm)} = -174 + 10 \cdot \log_{10}(\text{CBW}) + \text{NF}$ , CBW is channel bandwidth, NF =10 + - 5.2 If $\text{SINR} \geq -1$ , PASS, otherwise, FAIL + - 5.3a OR combining the results of AoA+ and AoA- + - 5.3b No logic combination of the results of AoA+ and AoA-, but treat them as two separate points (e.g., arithmetic mean) + - Other methods for +/- offset data are not precluded + - Companies are encouraging to provide analysis on the pros and cons for each “combination” method + - 5.4 Add weighting (sin $\theta$ or Clenshaw-Curtis Quadrature) + 6. Repeat for other test grid point + 7. Calculate the spherical coverage percentage + 8. Repeat for other angular separation + 9. Repeat for other UE orientations +10. Repeat for other UE implementations + +A noteworthy point is the calibration in step 3, and the intention is to minimize the difference between companies in simulation campaign. The following options were discussed to accommodate simulation data that is typically much better than the standard: + +**Option 1:** Adjust the beam shape or scale the antenna gain to make UE align with both peak EIS and spherical coverage. + +**Option 2:** Adjust the fixed DL power to align with real UE spherical coverage power level, e.g., if the spherical coverage in spec is -74.4 dBm with 10.9 dB gain drop and the UE only have 6 dB gain drop, then the fixed DL power need to be adjusted to -79.3 in the simulation. + +**Option 3:** Meet any one calibration condition as long as the other condition is met or exceeded. Two examples: + +- If a UE only has 6 dB drop from peak to 50th %ile, but the standards requirement for that parameter is 11 dB, the proposed calibration condition would be to align the peak direction to the REFSSENS condition. +- If a UE has 15 dB drop from peak to 50th %ile, but the standards requirement for that parameter is 11 dB, the proposed calibration conditions would be to align the 50th %ile direction to the spherical coverage EIS condition. + +The intention of calibration is to ensure that simulation results are comparable across all companies when performance of antenna module or other detailed simulation setup are different, so there should be a datum line existing after the calibration is performed. Based on this principle, both option 1 and option 2 can be used as calibration method, and then overall probability of PC3 UE will not exceed the 50% for any UE under any AoA offset. + +## 6.3 Requirement design + +### 6.3.1 DL power + +From the beginning of the discussion on how to design the requirement, it has been recognized that given a UE implementation, UE two-AoA reception performance, i.e., the two-AoA coverage probability, depends not only the AoA offset between the two AoAs, but also the DL power from the two TRPs. + +While in the real field, the DL power level from the two TRPs are likely to be different, a fixed DL power level was chosen to facilitate the requirement definition and testing, as it avoids many complexities in clearly quantifying the UE performance of the two AoAs, especially in the sDCI case. Furthermore, with varying power levels, the testing overhead is expected to increase as multiple power levels need to be tested. + +As for the exact DL power level, there were several proposals: + +Option 1: Use different DL power levels for the two AoAs. + +To ensure not to degrade the coverage compared with single DL reception, the spherical coverage requirement of 50th %-tile of the CCDF of EIS measured for one of the DL directions should be equal or close to the legacy requirement. DL power level for the other DL direction can be relaxed with respect to the AoA separation. + +Option 2: Both DL powers are higher than legacy spherical coverage requirement + +Since the two-AoA spherical coverage requirements for simultaneous multi-Rx chain DL reception cannot meet the legacy spherical coverage requirements for the single direction considering the mutual interference between the beams from two AoAs, and simultaneously choosing best Rx beam peak direction from two AoAs for all possible AoAs separation pairs cannot be guaranteed, it is proposed to define Z dBm tolerance for simultaneous multi-Rx chain DL reception. + +In addition, some relaxation compared to the legacy spherical coverage EIS level is proposed to account for polarization impairments in commercial UEs that are not fully reflected in simulation. + +Option 3: Both DL powers are same as the legacy spherical coverage requirement EIS level + +This option argues that the legacy spherical coverage EIS level should be reused as the DL power in the requirement, based on which the two-AoA coverage probability can be derived accordingly. + +In the end, the EIS level of the legacy spherical coverage requirement, e.g., specified in Table 7.3.4.3-1: EIS spherical coverage for power class 3 in TS 38.101-2, is chosen. Under this DL power level, the two-AoA coverage probability is derived. + +### 6.3.2 Inter-beam interference + +The simulation requirement for multi-Rx RF is being defined based on the minimum signal-to-interference-and-noise ratio (SINR) of the AoA1 and AoA2, and is significantly affected by the inter-beam interference. An example of inter-beam interference observed at the UE in a multi-TRP DL transmission scenario is shown in Figure 6.3.2-1 which demonstrates that the signal (S2) transmitted from TRP2 creates interference to the UE antenna panel receiving the signal (S1) transmitted from TRP1; $h_{11}$ ( $h_{12}$ ) is the path gain/loss of the channel between the TRP1 (TRP2) and the UE, and $P\_h_{11}$ ( $P\_h_{12}$ ) is the corresponding power. + +![Figure 6.3.2-1: UE beam radiation pattern example for wanted signal from AoA1 and interference from AoA2. The diagram shows a UE with three antenna panels. A top panel is receiving signal S1 from TRP1 (Delta AoA). A side panel is receiving signal S2 from TRP2. The top panel's gain is labeled h11 and its power is P_h11. The side panel's gain is labeled h12 and its power is P_h12. The UE is shown with a 'Single pol' label for each TRP.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +Figure 6.3.2-1: UE beam radiation pattern example for wanted signal from AoA1 and interference from AoA2. The diagram shows a UE with three antenna panels. A top panel is receiving signal S1 from TRP1 (Delta AoA). A side panel is receiving signal S2 from TRP2. The top panel's gain is labeled h11 and its power is P\_h11. The side panel's gain is labeled h12 and its power is P\_h12. The UE is shown with a 'Single pol' label for each TRP. + +**Figure 6.3.2-1: UE beam radiation pattern example for wanted signal from AoA1 and interference from AoA2** + +To study the effect of inter-beam interference in multi-TRP DL transmission, a UE equipped with three antenna arrays/modules/panels (each on its top, left and right surfaces) is assumed where each antenna array can steer the beam in seven different directions as shown in Figure 6.3.2-2, namely: + +1. Beam set for Antenna Array #1 (7 beams shown in variation of blue color), +2. Beam set for Antenna Array #2 (7 beams shown in variation of green color), +3. Beam set for Antenna Array #3 (7 beams shown in variation of red color), + +![Figure 6.3.2-2: FR2 UE with 3 antenna panels with 7 beams for each panel. The diagram shows a UE with three antenna panels. The top panel has 7 blue beams labeled 'Array 1 Beam 1' through 'Array 1 Beam 7'. The left panel has 7 red beams labeled 'Array 2 Beam 1' through 'Array 2 Beam 7'. The right panel has 7 green beams labeled 'Array 3 Beam 1' through 'Array 3 Beam 7'. The UE is shown with a 'Single pol' label for each TRP.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +Figure 6.3.2-2: FR2 UE with 3 antenna panels with 7 beams for each panel. The diagram shows a UE with three antenna panels. The top panel has 7 blue beams labeled 'Array 1 Beam 1' through 'Array 1 Beam 7'. The left panel has 7 red beams labeled 'Array 2 Beam 1' through 'Array 2 Beam 7'. The right panel has 7 green beams labeled 'Array 3 Beam 1' through 'Array 3 Beam 7'. The UE is shown with a 'Single pol' label for each TRP. + +**Figure 6.3.2-2: FR2 UE with 3 antenna panels with 7 beams for each panel** + +where the description of 7 beams selected from any beam set (group) is provided in Table 6.3.2-1. + +**Table 6.3.2-1: Beam index and description for a UE antenna panel** + +| Beam Index | Description | +|------------|-------------------------------------| +| Beam 1 | -45° with respect to Boresight Beam | +| Beam 2 | -30° with respect to Boresight Beam | +| Beam 3 | -15° with respect to Boresight Beam | +| Beam 4 | Boresight Beam | +| Beam 5 | +15° with respect to Boresight Beam | +| Beam 6 | +30° with respect to Boresight Beam | +| Beam 7 | +45° with respect to Boresight Beam | + +#### 6.3.2.1 Standalone antenna array configuration (Ideal Case) + +Figure 6.3.2.1-1 shows the standalone configuration with 1x4 UE antenna arrays and angular range over which each one of the 21 beams (7 beams on each of the three antenna modules) is dominant and has the highest RSRP over the other beams and Figure 6.3.2.1-2 shows the example UE beam radiation pattern receiving the desired signal from the direction of AoA1 on the main lobe and the interference signal from the direction of AoA2 on the side lobe. + +![Figure 6.3.2.1-1: (a) Standalone antenna array configuration, (b) Angular range for dominant beams. (a) shows three antenna arrays: Array #1 at the Top, Array #2 at the Right, and Array #3 at the Left Side, each with a 3D radiation pattern. (b) is a polar plot titled 'Dominant Beam Range' showing the angular coverage of the beams, with a color scale from 1 to 21.](f1c3ae01c82d4410b559fad6174a2f1a_img.jpg) + +Figure 6.3.2.1-1: (a) Standalone antenna array configuration, (b) Angular range for dominant beams. (a) shows three antenna arrays: Array #1 at the Top, Array #2 at the Right, and Array #3 at the Left Side, each with a 3D radiation pattern. (b) is a polar plot titled 'Dominant Beam Range' showing the angular coverage of the beams, with a color scale from 1 to 21. + +**Figure 6.3.2.1-1: (a) Standalone antenna array configuration, (b) Angular range for dominant beams**![Figure 6.3.2.1-2: UE beam radiation pattern for AoA1 and interference from AoA2. This is a line graph titled '2D cut (Front) radiation Patterns' showing Antenna Gain [dB] on the y-axis (from -25 to 10) versus Azimuth [deg] on the x-axis (from -100 to 200). It features two curves: a red curve with a 'Green Circle' at approximately 0 degrees (AoA1) and a 'Red Circle' at approximately 90 degrees (AoA2), and a blue curve representing the interference pattern.](367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg) + +Figure 6.3.2.1-2: UE beam radiation pattern for AoA1 and interference from AoA2. This is a line graph titled '2D cut (Front) radiation Patterns' showing Antenna Gain [dB] on the y-axis (from -25 to 10) versus Azimuth [deg] on the x-axis (from -100 to 200). It features two curves: a red curve with a 'Green Circle' at approximately 0 degrees (AoA1) and a 'Red Circle' at approximately 90 degrees (AoA2), and a blue curve representing the interference pattern. + +**Figure 6.3.2.1-2: UE beam radiation pattern for AoA1 and interference from AoA2** + +Considering AoA offset of 90° and the beam radiation patterns of two panels, one in red and one in blue, receive the signals from two TRPs are shown in Figure 6.3.2.1-2, 'Green Circle' and 'Red Circle' on the red beam radiation pattern will denote the received power of the wanted signal from one TRP and the interference signals (e.g. AoA1) from the other TRP (e.g., AoA2), and subsequently the signal-to-interference-ratio (SIR) can be defined as the ratio of the antenna gain values corresponding to the 'Green Circle' to that of the 'Red Circle'. In general, this interference power/gain is due to the sidelobe of the beam radiation pattern receives the unwanted signal from the other AoA. + +Next, the CCDF plot of SIR of AoA1 is presented for the case when Array #1's Boresight beam is used for the reception of the wanted signal from TRP1, whereas one of the 14 beams of Array #2/Array #3 is used for the reception of the wanted signal from AoA2. + +![Figure 6.3.2.1-3: CCDF of AoA1's SIR. This is a line graph showing the Complementary Cumulative Distribution Function (CCDF) of the Signal-to-Interference Ratio (SIR) for a dominant beam (DB) in the presence of 14 other beams. The x-axis represents the Signal to Interference [dB] from 0 to 40. The y-axis represents the CCDF [%] from 0 to 100. There are 14 curves, each representing a different beam configuration: Array 2-Beam 4, Array 2-Beam 3, Array 2-Beam 2, Array 2-Beam 1, Array 2-Beam 5, Array 2-Beam 6, Array 2-Beam 7, Array 3-Beam 4, Array 3-Beam 3, Array 3-Beam 2, Array 3-Beam 1, Array 3-Beam 5, Array 3-Beam 6, and Array 3-Beam 7. The curves show that as the SIR increases, the CCDF decreases. The curves for Array 2-Beam 7 and Array 3-Beam 7 are the leftmost, indicating the lowest SIR values for a given CCDF level, while the curves for Array 2-Beam 4 and Array 3-Beam 4 are the rightmost, indicating the highest SIR values.](a1545557e366b6302109d13360b199c3_img.jpg) + +CCDF of the Signal to Interference Level Between a Dominant Beam (DB) and 14 other Beams on other panels, for the Angular Domain (5.2 %) where that DB has the highest gain value + +Figure 6.3.2.1-3: CCDF of AoA1's SIR. This is a line graph showing the Complementary Cumulative Distribution Function (CCDF) of the Signal-to-Interference Ratio (SIR) for a dominant beam (DB) in the presence of 14 other beams. The x-axis represents the Signal to Interference [dB] from 0 to 40. The y-axis represents the CCDF [%] from 0 to 100. There are 14 curves, each representing a different beam configuration: Array 2-Beam 4, Array 2-Beam 3, Array 2-Beam 2, Array 2-Beam 1, Array 2-Beam 5, Array 2-Beam 6, Array 2-Beam 7, Array 3-Beam 4, Array 3-Beam 3, Array 3-Beam 2, Array 3-Beam 1, Array 3-Beam 5, Array 3-Beam 6, and Array 3-Beam 7. The curves show that as the SIR increases, the CCDF decreases. The curves for Array 2-Beam 7 and Array 3-Beam 7 are the leftmost, indicating the lowest SIR values for a given CCDF level, while the curves for Array 2-Beam 4 and Array 3-Beam 4 are the rightmost, indicating the highest SIR values. + +Figure 6.3.2.1-3: CCDF of AoA1's SIR + +To evaluate the CCDF, the antenna radiation pattern with $1^\circ$ resolution in azimuth and elevation domain is used providing 65160 constant step size grid points and then 2500 points are selected to approximate an uniform density grid. These selected points are then sorted in a descending order and are plotted as the CCDF curves. + +The legend ‘*Array x-Beam y*’ where $x \in \{2,3\}$ and $y \in \{1,2,3,4,5,6,7\}$ to be interpreted as described in Figure 6.3.2-2 and Table 6.3.2-1. Figure 6.3.2.1-3 shows the CCDF of SIR of AoA1 for the case when the antenna panels are configured in a standalone fashion as shown in Figure 6.3.2.1-1(a) and the interference signal coming from AoA2 direction aligns with the direction of one of the 14 beams of Array#2 and Array#3 and hence creates different interference scenarios to the signal received at ‘Array 1-Beam 4’, resulting in different CCDF curves in Figure 6.3.2.1-3. + +From Figure 6.3.2.1-3, the SIR values corresponding to the 50th percentile of the CCDF curves is shown in Table 6.3.2.1-1 where it is worth noting that the interference from the TRP2 signals arriving from the AoA2 direction becomes significant when the angular separation between AoA1 and AoA2 is low. + +Table 6.3.2.1-1: SIR at 50-percentile of CCDF of Figure 6.3.2.1-3 + +| Beam Index (Array 2/Array 3) | SIR at 50-percentile of CCDF (dB) | +|------------------------------|-----------------------------------| +| Beam 7 | 10 | +| Beam 6 | 17 | +| Beam 5 | 21 | +| Beam 4 | 24 | +| Beam 3 | 24 | +| Beam 2 | 26 | +| Beam 1 | 26 | + +#### 6.3.2.2 Realistic formfactor smart-phone (Practical Case) + +The electromagnetic simulations of a realistic smartphone Mechanical Computer Aided Design (M-CAD) assumes that front and rear surfaces of the smartphone are made up of glass, chassis is metallic and frame is made up of plastic (see Figure 6.3.2.2-1 and Table 6.3.2.2-1 below for more details). Furthermore, the UE is assumed to have one antenna array/module/panel on each of its left, top, and right surfaces; each antenna module is a standalone uniform linear array of four single polarized antenna elements placed half a wavelength apart from each other. + +![Figure 6.3.2.2-1: Details of a realistic smartphone M-CAD. The image shows two views of a smartphone model. The left view is a cross-section showing internal layers: Front Glass, Plastic Frame, Metal Chassis, Rear Glass, and Substrate. The right view shows the external antenna arrays: Antenna Array#1 at the Top, Antenna Array#2 at the Right Side, and Antenna Array#3 at the Left Side.](5a2d10b858b621236f708a5f5fa1ed88_img.jpg) + +Figure 6.3.2.2-1: Details of a realistic smartphone M-CAD. The image shows two views of a smartphone model. The left view is a cross-section showing internal layers: Front Glass, Plastic Frame, Metal Chassis, Rear Glass, and Substrate. The right view shows the external antenna arrays: Antenna Array#1 at the Top, Antenna Array#2 at the Right Side, and Antenna Array#3 at the Left Side. + +Figure 6.3.2.2-1: Details of a realistic smartphone M-CAD + +Table 6.3.2.2-1: Material parameters for electromagnetic simulations + +| Material parameters @ 28 GHz | Dielectric Constant | Loss tangent | Conductivity | +|------------------------------|---------------------|--------------|--------------| +| Glass | 5.75 | 0.0036 | - | +| Plastic | 2.9 | 0.0075 | - | +| Substrate | 3.55 | 0.0027 | - | +| Chassis | - | - | 5.8e7 S/m | + +![Figure 6.3.2.2-2: Angular range for dominant beams of a realistic formfactor smart-phone UE. This is a polar plot showing the angular range for 21 dominant beams. The X-axis and Y-axis range from -40 to 40. A color bar on the right indicates the beam index from 1 to 21. The plot shows various colored regions representing the angular coverage of each beam.](f880daa1cde4b71fcbaff2df81803a65_img.jpg) + +Figure 6.3.2.2-2: Angular range for dominant beams of a realistic formfactor smart-phone UE. This is a polar plot showing the angular range for 21 dominant beams. The X-axis and Y-axis range from -40 to 40. A color bar on the right indicates the beam index from 1 to 21. The plot shows various colored regions representing the angular coverage of each beam. + +Figure 6.3.2.2-2: Angular range for dominant beams of a realistic formfactor smart-phone UE + +Figure 6.3.2.2-2 shows the angular range over which each one of the 21 beams of a realistic formfactor smart-phone UE is dominant. Similar to Section 6.3.2.1, the assumption is that the boresight beam of Antenna Array #1 is the dominant beam used for receiving the signals from AoA1 whereas the AoA2's dominant beam must be selected from the remaining 14 beams of Antenna Array #2 and #3. Next, the plot of CCDF of SIR of AoA1 for a realistic formfactor smart-phone UE is presented. + +![Figure 6.3.2.2-3: CCDF of AoA1's SIR for a realistic formfactor smart-phone UE. The plot shows the Complementary Cumulative Distribution Function (CCDF) of the Signal to Interference Ratio (SIR) in dB for 14 different beam pairs (Array 2-Beam 1 to 7 and Array 3-Beam 1 to 7). The x-axis represents the Signal to Interference Ratio [dB] from 0 to 40, and the y-axis represents the CCDF [%] from 0 to 100. The curves show that the performance of Array 2-Beam 7 and Array 3-Beam 7 is the worst, while the performance of Array 2-Beam 1 and Array 3-Beam 1 is the best. The curves for Array 2-Beam 5 and Array 3-Beam 5, and Array 2-Beam 6 and Array 3-Beam 6, are higher than those for Array 2-Beam 7 and Array 3-Beam 7.](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +Figure 6.3.2.2-3: CCDF of AoA1's SIR for a realistic formfactor smart-phone UE. The plot shows the Complementary Cumulative Distribution Function (CCDF) of the Signal to Interference Ratio (SIR) in dB for 14 different beam pairs (Array 2-Beam 1 to 7 and Array 3-Beam 1 to 7). The x-axis represents the Signal to Interference Ratio [dB] from 0 to 40, and the y-axis represents the CCDF [%] from 0 to 100. The curves show that the performance of Array 2-Beam 7 and Array 3-Beam 7 is the worst, while the performance of Array 2-Beam 1 and Array 3-Beam 1 is the best. The curves for Array 2-Beam 5 and Array 3-Beam 5, and Array 2-Beam 6 and Array 3-Beam 6, are higher than those for Array 2-Beam 7 and Array 3-Beam 7. + +**Figure 6.3.2.2-3: CCDF of AoA1's SIR for a realistic formfactor smart-phone UE** + +In Figure 6.3.2.2-3, it is observed that due to the change of the beam shapes caused by the surrounding components in the real mobile phone, the difference of CCDF of SIR become less compared with those based on the analysis of the ideal beams in Figure 6.3.2.1-3. However, it is again observed that the performance of Array 2-Beam 7 and Array 3-Beam 7 is worst compared to the other 12 beams of Array 2 and Array 3 as the CCDF curves for these two beams is relatively located in the leftmost region. Furthermore, the SIRs corresponding to 'Array 2-Beam 5'/'Array 3-Beam 5' and 'Array 2-Beam 6'/'Array 3-Beam 6' are higher compared with that of 'Array 2-Beam 7'/'Array 3-Beam 7'. This is aligned with the previous results that the SIR increases as the angular separation between AoAs increases. + +**Table 6.3.2.2-2: SIR at 50-percentile of CCDF of Figure 6.3.2.2-3** + +| Beam Index (Array 2/Array 3) | SIR at 50-percentile of CCDF (dB) | +|------------------------------|-----------------------------------| +| Beam 7 | 13 | +| Beam 6 | 15.5 | +| Beam 5 | 16 | +| Beam 4 | 17.5 | +| Beam 3 | 17.5 | +| Beam 2 | 18 | +| Beam 1 | 16 | + +The SIR values corresponding to the 50th percentile of the CCDF curves of Figure 6.3.2.2-3 is shown in Table 6.3.2.2-2. It is also observed from Table 6.3.2.1-1 and Table 6.3.2.2-2 that there is a significant difference (up to 16 dB in the ideal case and up to 5 dB in the practical case) between the SIR at 50-percentile of CCDF (dB) for different AoA offset scenarios. + +The spherical coverage is worse if the AoA offset is small and spherical coverage becomes better if the AoA offset is larger which share the same trends. However, in Figure 6.3.2.2-3, it is observed that the plots corresponding to 'Array 2-Beam 1' and 'Array 3-Beam 1' (shown in brown colour) shows that the beam with largest AoA separation might not be the best beam in all the cases. The intuitive reasoning behind this is that depending on the beam pattern, the gain of the side lobe of the beam receiving signals from AoA1 might be large or small in the direction of AoA2 which is illustrated in the Figure 6.3.2-1. + +#### 6.3.2.3 Summary + +The important observations of inter-beam interference study can be summarized as follows: + +1. For small AoA offset scenario, the effect of inter-beam interference will be large. +2. With increasing AoA offset, the effect of inter-beam interference reduces. +3. The largest AoA offset scenario might not have lowest inter-beam interference due to the significant side lobe gain of the UE beam radiation pattern at that AoA offset. + +4. The UE beam radiation pattern, gain of the side lobes, AoA offset will have a direct impact on the inter-beam interference effect. + +### 6.3.3 $\pm$ AoA separation + +Due to the constraint of test system, the set of possible paired TRP locations for each test point reduces to 2 points, as show in Figure 6.3.3-1 + +![Figure 6.3.3-1: Progressive test limitations due to practical considerations. The diagram shows three spheres representing test spheres. The top sphere is labeled 'Ideal case: Each TRP is presented to the UE at any random location (white star). The UE is evaluated when second TRP is moved across all locations on the test sphere (blue surface)'. The middle sphere is labeled 'Fixed AoA separation case: Each TRP is presented to the UE at any random location (star). The UE is evaluated when second TRP is some fixed AoA separation from the first TRP (orange arc)'. The bottom sphere is labeled 'Practical implementation of TE with fixed AoA separation: Each AoA of one TRP is paired with 2 possible AoAs for the second TRP (green stars)'.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +Figure 6.3.3-1: Progressive test limitations due to practical considerations. The diagram shows three spheres representing test spheres. The top sphere is labeled 'Ideal case: Each TRP is presented to the UE at any random location (white star). The UE is evaluated when second TRP is moved across all locations on the test sphere (blue surface)'. The middle sphere is labeled 'Fixed AoA separation case: Each TRP is presented to the UE at any random location (star). The UE is evaluated when second TRP is some fixed AoA separation from the first TRP (orange arc)'. The bottom sphere is labeled 'Practical implementation of TE with fixed AoA separation: Each AoA of one TRP is paired with 2 possible AoAs for the second TRP (green stars)'. + +Figure 6.3.3-1 Progressive test limitations due to practical considerations + +A corollary is that given the agreed test system constraints, a complete test implies every AoA for each TRP is paired with 2 AoAs associated with the other TRP. Unfortunately, a simple 2TRP scan like legacy practice under fixed AoA separation does not exercise the UE with all AoA pairs the TE can produce. The post processed data (CCDF of sensitivity, relative to REFSENS) collected from the 2TRP scan shows bias for the following conditions: + +1. A pair of UEs that have mirror image coverage patterns can show different statistics for the coverage of the two TRPs. See left sub-figure in figure 6.3.3-2. (Mirror image UEs: UE with modules in the top + left faces versus a UE with modules in the top + right faces) +2. A given UE can register different statistics for a TRP depending on whether the second TRP is introduced at a positive or negative AoA separation See right sub-figure in figure 6.3.3-2. + +![Figure 6.3.3-2: Impact of not exercising the UE over all possible AoA pairs. The figure contains two line graphs. The left graph is titled 'Sens CCDF over coverage areas 120deg AoAsep, R=0' and shows three curves: TRP1 (red), TRP2 (blue), and legacy (grey). The right graph is also titled 'Sens CCDF over coverage areas 120deg AoAsep, R=0' and shows three curves: TRP1 +AoAsep (red circles), TRP1 -AoAsep (red circles), and legacy (grey). Both graphs plot Sens CCDF (y-axis, 0 to 1) against dB (x-axis, 0 to 15).](d2adade462af578f17e01b2a65b53c12_img.jpg) + +Figure 6.3.3-2: Impact of not exercising the UE over all possible AoA pairs. The figure contains two line graphs. The left graph is titled 'Sens CCDF over coverage areas 120deg AoAsep, R=0' and shows three curves: TRP1 (red), TRP2 (blue), and legacy (grey). The right graph is also titled 'Sens CCDF over coverage areas 120deg AoAsep, R=0' and shows three curves: TRP1 +AoAsep (red circles), TRP1 -AoAsep (red circles), and legacy (grey). Both graphs plot Sens CCDF (y-axis, 0 to 1) against dB (x-axis, 0 to 15). + +Figure 6.3.3-2: Impact of not exercising the UE over all possible AoA pairs + +To dig deeper into why a UE with symmetric behaviour for both TRPs should exhibit different post-processed data associated with each TRP, it is useful to study the grid quality in further detail. Figure 6.3.3-3 graphically shows the + +TRP coverage patterns with the 2TRP scan identified in the previous section. The grids covered by both TRPs are identical, but each location for each TRP only shows one paired AoA. + +![Figure 6.3.3-3: Missing AoA pairs in the 2TRP scan. The figure consists of two 3D plots of a sphere with grid points (blue dots) and associated AoA directions (red segments). The left plot represents TRP1 and the right plot represents TRP2. Each grid point has only one red segment, indicating a missing AoA pair. The red segments point in opposite directions for the same region of the sphere for the two TRPs. Annotations explain that blue dots are grid point locations from the UE's perspective, and for each grid point of one TRP, the companion AoA is along the direction of the red segments. Two observations are noted: Obs. 1 states that each AoA has only one paired AoA (one red segment per grid point); Obs. 2 states that the paired AoAs point in opposite directions for the same region for the two TRPs.](23816aaa8e6defc50fc888da62fd59cc_img.jpg) + +*Blue dots are grid point locations of a TRP during the scan, from the UE's perspective. TRP1 to the left, TRP2 to the right* + +*For each grid point location of one TRP, the companion AoA associated with the other TRP is along the direction indicated by the red segments.* + +*Obs. 1: For each TRP, each AoA has only one paired AoA associated with the other TRP (just one red segment is attached to each grid point)* + +*Obs. 2: The paired AoAs point in opposite directions for the same region of the test sphere for the 2 TRPs* + +Figure 6.3.3-3: Missing AoA pairs in the 2TRP scan. The figure consists of two 3D plots of a sphere with grid points (blue dots) and associated AoA directions (red segments). The left plot represents TRP1 and the right plot represents TRP2. Each grid point has only one red segment, indicating a missing AoA pair. The red segments point in opposite directions for the same region of the sphere for the two TRPs. Annotations explain that blue dots are grid point locations from the UE's perspective, and for each grid point of one TRP, the companion AoA is along the direction of the red segments. Two observations are noted: Obs. 1 states that each AoA has only one paired AoA (one red segment per grid point); Obs. 2 states that the paired AoAs point in opposite directions for the same region for the two TRPs. + +**Figure 6.3.3-3 Missing AoA pairs in the 2TRP scan** + +As evident from the observations in the figure, there are missing AoA test pairs (only one red segment attached to each grid point). Fortunately, for this scan, the omission of test AoA pairs is complementary across the two TRPs. In other words, if the locations of TRP1 and TRP2 are interchanged and the scan repeated (i.e. complementary scan), the missing AoA pairs get tested and none of the previously tested AoA pairs gets re-tested. The combined data set from both scans has neither omitted AoA pairs, nor repeated pairs. The grid statistics as well as the impact of performing this complementary scan on the UE described earlier is shown in figure 6.3.3-4. Applying this improved scan to example UE completes the 2 TRP data set. The data set shows 'improved' statistics, but these are based merely on added AoA test directions from the complementary scan, rather than a genuine improvement at the UE. + +![Figure 6.3.3-4: Complementary pair version of 2TRP scan. The figure contains three sub-plots. Top: A 3D sphere plot showing a grid of points with two red segments attached to each point, representing AoA pairs. Bottom-left: A Sens CCDF plot over coverage areas 120deg AoAsep, R=0, comparing TRP1, TRP2, and legacy. Bottom-right: A Sens CCDF plot over coverage areas 120deg AoAsep, R=0, comparing TRP1 +AoA, TRP2 +AoA, TRP1 -AoA, TRP2 -AoA, TRP1 legacy, and TRP2 legacy. Annotations explain the grid pattern and the improved performance after adding missing AoA pairs.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +Obs. 1: After complementary pair scan, for each TRP, each AoA has two paired AoAs associated with the other TRP (note 2 red segments attached to each grid point) + +Grid and pair AoA patterns look identical for both TRPs for the complementary pair version of the 2TRP scan + +Sens CCDF over coverage areas 120deg AoAsep, R=0 + +TRP sensitivity statistics prior to complementary pair scan + +Sens CCDF over coverage areas 120deg AoAsep, R=0 + +TRP sensitivity statistics after complementary pair scan shows 'improved performance' after addition of data missing AoA pairs + +Figure 6.3.3-4: Complementary pair version of 2TRP scan. The figure contains three sub-plots. Top: A 3D sphere plot showing a grid of points with two red segments attached to each point, representing AoA pairs. Bottom-left: A Sens CCDF plot over coverage areas 120deg AoAsep, R=0, comparing TRP1, TRP2, and legacy. Bottom-right: A Sens CCDF plot over coverage areas 120deg AoAsep, R=0, comparing TRP1 +AoA, TRP2 +AoA, TRP1 -AoA, TRP2 -AoA, TRP1 legacy, and TRP2 legacy. Annotations explain the grid pattern and the improved performance after adding missing AoA pairs. + +**Figure 6.3.3-4: Complementary pair version of 2TRP scan** + +Based on the analysis above, both +AoA offset and -AoA offset for each test point shall be considered in requirement evaluation. This arrangement is equivalent to the complementary scan technique. + +### 6.3.4 UE orientation + +For the legacy 1AoA UE RF requirement and test for FR2, various UE alignment options (referred as orientations in this TR from these points onwards) are allowed as illustrated in the Figures in the Tables J.2-1 through J.2-3 of TS 38.101-2 Annex J. In theory, the test results with different UE orientations should be the same without considering the measurement grid uncertainty, because the 3D scan of 1AoA test is sampling UE's sphere with test 'point'. However, the 3D scan of 2AoA test is sampling UE's sphere with test 'vector' corresponding to AoA pair. Different UE orientations will lead to different test 'vector' even at the same test point, and thus different 2AoA performance is expected. + +Companies' simulation results as provided in Annex A show that different UE orientations lead to significantly different 2AoA spherical coverage performance. Depending on different UE implementations, no standardized UE orientation could be found suitable for 2AoA performance test. RAN4 has agreed to specify the 2AoA spherical coverage performance in implementation agnostic manner, the most feasible way is to adopt the declaration approach. + +Based on the theoretical analysis and simulation results, RAN4 achieves following conclusion: + +1. UE requirement applies to UE declared orientation(s). +2. The UE RF requirement is derived assuming each UE is evaluated in the orientation that yields the best metric value. +3. All the candidate orientations discussed in this section for UE to choose from correspond to the 'Alignment Options' in Annex J (J.2) of TS 38.101-2. + +### 6.3.5 AoA pairs for enhanced positioners + +During investigation of projected UE performance with the legacy positioner, it became evident that different overall probabilities are calculated for the same UE, depending on its orientation in the positioner. See figure 6.3.5-3. + +The difference can be traced back to the agreed TE constraints that only tests the UE for AoA pairs that lie along longitudes in the reference coordinate system defined by positioner axes. See figure 6.3.5-1. + +![Figure 6.3.5-1: A spherical coordinate system diagram showing a grid of red dots representing grid point locations. Blue arrows indicate the direction of AoA pairs along the longitudes of the UE spherical reference coordinate system.](4936add03827ef5a51439c28ec878506_img.jpg) + +Figure 6.3.5-1: A spherical coordinate system diagram showing a grid of red dots representing grid point locations. Blue arrows indicate the direction of AoA pairs along the longitudes of the UE spherical reference coordinate system. + +*Red dots are grid point locations where the regional probability is calculated.* + +**For each grid point location, the companion AoA associated with the other TRP is along the direction indicated by the blue arrows.** + +**Figure 6.3.5-1: AoA pairs lie along longitudes of the UE spherical reference coordinate system with the agreed TE.** + +This bias problem can be resolved by including AoA pairs that are not limited to the same longitude as is the case for the agreed TE, see figure 6.3.5-2. + +One possibility is to average 2TRP performance data in the TE across multiple different orientations of the UE in the positioner. This method has been adopted successfully in the past for single TRP scenarios, but this method may not be suitable for 2TRP scenarios (where 2 directions are involved at one time): + +1. The primary problem is inability to include at each grid point, ‘AoA pairs that are not limited to the same longitude’. The legacy positioner does not retain the same grid for all orientation possibilities. +2. A further problem is that even if the UE faces are pointing as desired, the actual module coverage directions may not be well centered around the respective face normals. Such UEs would face additional challenges with a procedure that introduces bias. At a minimum it would complicate the requirement derivation process. + +A better and more precise approach would be to diversify the collection of AoA pairs used to calculate regional probability at each grid point. This can be achieved by modify the agreed TE concept to use a 3-axis positioner rather than the legacy 2-axis positioner. Figure 6.3.5-2 shows the intended effect of the added degree of freedom from the UE’s perspective. Recall that the legacy 2-axis positioner in combination with a complementary sweep or +/-AoAsep scan is only able to pair each grid point to AoAs along the blue arrows, respectively. The 3-axis positioner is intended to allow each grid point to be additionally paired with AoAs along the green arrows. + +*Blue arrows – directions of paired AoAs with 2-axis positioner and complementary scan.* + +*Green arrows – necessary additional directions of paired AoAs to reduce bias.* + +![Figure 6.3.5-2 (left): A diagram showing a grid point with blue arrows indicating the directions of paired AoAs for a 2-axis positioner and green arrows indicating the necessary additional directions for a 3-axis positioner to reduce bias.](9f6e8230f2fab5fb10cba96fec859743_img.jpg) + +Figure 6.3.5-2 (left): A diagram showing a grid point with blue arrows indicating the directions of paired AoAs for a 2-axis positioner and green arrows indicating the necessary additional directions for a 3-axis positioner to reduce bias. + +*The orange circle represents the set of all AoAs that are separated from the evaluation grid location by some fixed AoA separation.* + +*The intent is to sample the outcomes in spatially uniform directions to reduce bias.* + +![Figure 6.3.5-2 (right): A diagram showing an orange circle representing the set of all AoAs separated from a grid point by a fixed AoA separation. Blue and green arrows indicate the directions of paired AoAs.](0ffcb27a48f875e32f7b268421957e34_img.jpg) + +Figure 6.3.5-2 (right): A diagram showing an orange circle representing the set of all AoAs separated from a grid point by a fixed AoA separation. Blue and green arrows indicate the directions of paired AoAs. + +**Figure 6.3.5-2: Scheme to combat bias introduced by AoA pairs limited to lie along longitudes of agreed grid.** + +Referring to the mathematical formulation of overall probability, for the 3-axis positioner, the regional probability at each grid point can be determined from outcomes of a configurable number of AoA pairs that are spatially well distributed (6 shown) rather than just the two pairs that lie along the longitude associated with the grid point. The overall probability can be calculated from the regional probabilities over the sphere. The mathematical formulation also highlights the dissociation of the grid points where the regional probabilities are calculated from the locations of the paired AoAs for each grid point. Since multiple runs are no longer required to generate multiple AoA pairs at each point, the 2TRP scan can be simplified for the 3-axis positioner by dropping the requirement for enhancements such as the complementary pair sweep or combining data from +AoAsep and -AoAsep scans. + +Figures 6.3.5-3 shows the impact on calculated overall probability to support 2TRP DL of using a 3-axis positioner as described above to reduce bias for an example UE. The performance projections use a 5-degree step size and 6 AoA pairs per grid point (i.e. 6 stops for the roll motor at each grid point). Also assumed is a scan strategy that ensures neither source is blocked. It is evident that the projected performance trends are largely robust to UE orientation in the 3-axis positioner. Note however that due to non-zero size of any positioning mechanism, some declaration must be instituted so the UE is not oriented in way that it is partially blocked by the mechanism. Fortunately, this ‘UE alignment option’ is already established and recorded in TR38.810, Annex C, and can be retained for this feature. + +![Four line graphs showing TE constrained overall 2TRP probability (%) vs AoA Sep (deg) for 2-axis and 3-axis positioners. The top two graphs show the 2-axis positioner results, with a significant bias (lower probability) for the 'mean combining' case compared to the 'OR combining' case. The bottom two graphs show the 3-axis positioner results, where the bias is removed, and both 'OR combining' and 'mean combining' cases show similar, higher probabilities. A central label 'Positioner upgrade' with arrows indicates the transition from the 2-axis to the 3-axis positioner.](8fd97886a32c3ac7abb08aba9f7f231b_img.jpg) + +Bias from using a legacy 2-axis positioner. + +Positioner upgrade + +The figure consists of four subplots arranged in a 2x2 grid, showing the 'TE constrained overall 2TRP probability (%)' on the y-axis (ranging from 0 to 50) against 'AoA Sep (deg)' on the x-axis (ranging from 60 to 180). The top-left plot is titled 'Position comparison, OR combining' and the top-right is 'Position comparison, mean combining'. The bottom-left is '3D positioner, OR combining' and the bottom-right is '3D positioner, mean combining'. Each plot contains multiple data series for different UE orientations: FrontTop HH, FrontTop VV, FrontBot HH, FrontBot VV, FrontLeft HH, FrontLeft VV, TopRight HH, TopRight VV, TopLeft HH, and TopLeft VV. In the 2-axis positioner plots (top), the 'mean combining' case shows a significant drop in probability (bias) compared to the 'OR combining' case. In the 3-axis positioner plots (bottom), the bias is removed, and both cases show similar, higher probabilities. A central label 'Positioner upgrade' with arrows indicates the transition from the 2-axis to the 3-axis positioner. + +Four line graphs showing TE constrained overall 2TRP probability (%) vs AoA Sep (deg) for 2-axis and 3-axis positioners. The top two graphs show the 2-axis positioner results, with a significant bias (lower probability) for the 'mean combining' case compared to the 'OR combining' case. The bottom two graphs show the 3-axis positioner results, where the bias is removed, and both 'OR combining' and 'mean combining' cases show similar, higher probabilities. A central label 'Positioner upgrade' with arrows indicates the transition from the 2-axis to the 3-axis positioner. + +Figure 6.3.5-3: Bias removal using a 3-axis positioner. + +Due to pragmatic considerations, this positioner enhancement is not pursued for this WI. + +### 6.3.6 DL polarization combination + +There are four different DL polarization combinations, i.e., $(\text{TRP1}_\theta, \text{TRP2}_\theta)$ , $(\text{TRP1}_\phi, \text{TRP2}_\phi)$ , $(\text{TRP1}_\theta, \text{TRP2}_\phi)$ or $(\text{TRP1}_\phi, \text{TRP2}_\theta)$ . It is known that the UE performance can differ if the same polarization or orthogonal polarization is adopted by the two probes in testing. With the same polarization, a higher correlation between the two DL data streams can be expected, especially when the AoA offset is small, representing the worst-case performance. + +In deciding which combination to use for verification, there are two main considerations. First, the requirements should be derived based on the worst-case polarization match at the UE, and should apply for any combination of DL polarizations from each TRP. Second, there is a need to minimize the testing overhead while ensuring good testing coverage. + +In the two-AoA simulations, the worst-case polarization match between the 2 TRPs is assumed. In other words, the transmitted signal from one TRP is considered interference without any polarization isolation at the UE when decoding the transmitted signal from the other TRP. + +It was also pointed out that the radiation pattern of V-pol and H-pol of an antenna module is not exactly same, and when metal blockage exist, the difference may be amplified due to the reflection as shown in the Figure below. In practical UE design, to avoid severe blockage, the metal frame near the antenna module can be removed and replaced by other materials, but the V/H element may still suffer from different loss, which still lead to difference between V-pol and H-pol. + +![Figure 6.3.6-1: The radiation pattern of a pair of V/H element in 1x4 antenna module. The figure consists of three parts: two 3D surface plots on the left showing the radiation patterns for V-pol and H-pol, and a 2D polar plot on the right showing the Farfield Realized Gain Abs (Phi=90) for both polarizations. The 3D plots show the gain distribution in the Theta and Phi directions. The 2D plot shows the gain in dBi versus Theta (Degree) for Phi=90, with two curves: farfield (f=28)H (green) and farfield (f=28)V (red).](6fe536731996880570f251da168376cf_img.jpg) + +Figure 6.3.6-1: The radiation pattern of a pair of V/H element in 1x4 antenna module. The figure consists of three parts: two 3D surface plots on the left showing the radiation patterns for V-pol and H-pol, and a 2D polar plot on the right showing the Farfield Realized Gain Abs (Phi=90) for both polarizations. The 3D plots show the gain distribution in the Theta and Phi directions. The 2D plot shows the gain in dBi versus Theta (Degree) for Phi=90, with two curves: farfield (f=28)H (green) and farfield (f=28)V (red). + +**Figure 6.3.6-1 The radiation pattern of a pair of V/H element in 1x4 antenna module** + +If the gain difference exists between V-pol and H-pol, for each receiver branch, the projection from $\theta$ and $\phi$ should be calculated, and the following procedure to calculate received signal can be used: + +Step-1: Extract the antenna gain in $\theta$ direction and $\phi$ direction in module reference system when only V-elements are activated, i.e., $G_{V,\theta M}(\theta_M, \phi_M)$ and $G_{V,\phi M}(\theta_M, \phi_M)$ + +Step-2: Extract the antenna gain in $\theta$ direction and $\phi$ direction in module reference system when only H-elements are activated, i.e., $G_{H,\theta M}(\theta_M, \phi_M)$ and $G_{H,\phi M}(\theta_M, \phi_M)$ + +![Figure 6.3.6-2: Illustration of antenna gain in theta direction and phi direction. The figure shows two 3D diagrams of an antenna module. The left diagram illustrates the gain in the theta direction, with labels G_{V,\theta M}(\theta_M, \phi_M) and G_{H,\theta M}(\theta_M, \phi_M). The right diagram illustrates the gain in the phi direction, with labels G_{V,\phi M}(\theta_M, \phi_M) and G_{H,\phi M}(\theta_M, \phi_M). Both diagrams show the antenna module in a global coordinate system (x_global, y_global, z_global) and a local coordinate system (x', y', z').](8b06b57a6331adbe608b9c79baa2198e_img.jpg) + +Figure 6.3.6-2: Illustration of antenna gain in theta direction and phi direction. The figure shows two 3D diagrams of an antenna module. The left diagram illustrates the gain in the theta direction, with labels G\_{V,\theta M}(\theta\_M, \phi\_M) and G\_{H,\theta M}(\theta\_M, \phi\_M). The right diagram illustrates the gain in the phi direction, with labels G\_{V,\phi M}(\theta\_M, \phi\_M) and G\_{H,\phi M}(\theta\_M, \phi\_M). Both diagrams show the antenna module in a global coordinate system (x\_global, y\_global, z\_global) and a local coordinate system (x', y', z'). + +**Figure 6.3.6-2 illustration of antenna gain in $\theta$ direction and $\phi$ direction** + +Step-3: For the DL signal from each TRP in the TE coordinate system, transform the TRP location into the module reference system, e.g., for antenna module#1, $AoA1(\theta_1, \phi_1) \rightarrow AoA1(\theta_{1M\#1}, \phi_{1M\#1})$ , $AoA2(\theta_2, \phi_2) \rightarrow AoA1(\theta_{2M\#1}, \phi_{2M\#1})$ and for antenna module#2, $AoA1(\theta_1, \phi_1) \rightarrow AoA1(\theta_{1M\#2}, \phi_{1M\#2})$ , $AoA2(\theta_2, \phi_2) \rightarrow AoA1(\theta_{2M\#2}, \phi_{2M\#2})$ + +![Figure 6.3.6-3 illustration of coordinate system transformation. The diagram shows a 3D coordinate system with global axes (X_global, Y_global, Z_global) and local axes (X_local, Y_local, Z_local) for a rectangular module. Two antenna modules, labeled 'Module #1' and 'Module #2', are shown. Arrows indicate the transformation of angles from a global reference system to the local module reference systems. For Module #1, angles are labeled as AoA1(theta_1, phi_1) and AoA2(theta_2, phi_2) transforming to AoA1(theta_1M#1, phi_1M#1) and AoA1(theta_2M#1, phi_2M#1). For Module #2, angles are labeled as AoA1(theta_1, phi_1) and AoA2(theta_2, phi_2) transforming to AoA1(theta_1M#2, phi_1M#2) and AoA1(theta_2M#2, phi_2M#2).](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Figure 6.3.6-3 illustration of coordinate system transformation. The diagram shows a 3D coordinate system with global axes (X\_global, Y\_global, Z\_global) and local axes (X\_local, Y\_local, Z\_local) for a rectangular module. Two antenna modules, labeled 'Module #1' and 'Module #2', are shown. Arrows indicate the transformation of angles from a global reference system to the local module reference systems. For Module #1, angles are labeled as AoA1(theta\_1, phi\_1) and AoA2(theta\_2, phi\_2) transforming to AoA1(theta\_1M#1, phi\_1M#1) and AoA1(theta\_2M#1, phi\_2M#1). For Module #2, angles are labeled as AoA1(theta\_1, phi\_1) and AoA2(theta\_2, phi\_2) transforming to AoA1(theta\_1M#2, phi\_1M#2) and AoA1(theta\_2M#2, phi\_2M#2). + +**Figure 6.3.6-3 illustration of coordinate system transformation** + +Step-4: The received signal for each antenna module (after MRC of rank1 DL) can be calculated when DL signal polarization is ( $\theta$ , $\theta$ ), e.g., the received signal from AoA1 by antenna module#1 is: + +$$s_{1,\theta M\#1} = \left( G_{V,\theta M}(\theta_M, \phi_M) + G_{H,\theta M}(\theta_M, \phi_M) \right), \text{ where } \theta_M = \theta_{1M\#1}, \phi_M = \phi_{1M\#1}$$ + +The received signal from AoA1 by antenna module#2 is: + +$$s_{1,\theta M\#2} = \left( G_{V,\phi M}(\theta_M, \phi_M) + G_{H,\phi M}(\theta_M, \phi_M) \right), \text{ where } \theta_M = \theta_{1M\#2}, \phi_M = \phi_{1M\#2}$$ + +Step-5: The received signal for each antenna module (after MRC of rank1 DL) can be calculated when DL signal polarization is ( $\phi$ , $\phi$ ), e.g., the received signal from AoA1 by antenna module#1 is: + +$$s_{1,\phi M\#1} = \left( G_{V,\phi M}(\theta_M, \phi_M) + G_{H,\phi M}(\theta_M, \phi_M) \right), \text{ where } \theta_M = \theta_{1M\#1}, \phi_M = \phi_{1M\#1}$$ + +The received signal from AoA1 by antenna module#2 is: + +$$s_{1,\phi M\#2} = \left( G_{V,\phi M}(\theta_M, \phi_M) + G_{H,\phi M}(\theta_M, \phi_M) \right), \text{ where } \theta_M = \theta_{1M\#2}, \phi_M = \phi_{1M\#2}$$ + +The whole formula is shown in Table below: + +**Table 6.3.6-1 The formula for received signal** + +| θθ DL | Module #1 | Module #2 | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| Signal level(*) | $s_{\theta M\#1} = G_{V,\theta M}(\theta_M, \phi_M) + G_{H,\theta M}(\theta_M, \phi_M)$ | $s_{\theta M\#2} = G_{V,\phi M}(\theta_M, \phi_M) + G_{H,\phi M}(\theta_M, \phi_M)$ | +| TRP1 location transformed to module reference system | $\theta_M = \theta_{1M\#1}, \phi_M = \phi_{1M\#1}$ | $\theta_M = \theta_{1M\#2}, \phi_M = \phi_{1M\#2}$ | +| TRP 2 location transformed to module reference system | $\theta_M = \theta_{2M\#1}, \phi_M = \phi_{2M\#1}$ | $\theta_M = \theta_{2M\#2}, \phi_M = \phi_{2M\#2}$ | + +| $\phi\phi$ DL | Module #1 | Module #2 | +|-------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| Signal level(*) | $s_{\phi M\#1} = G_{V,\phi M}(\theta_M, \phi_M) + G_{H,\phi M}(\theta_M, \phi_M)$ | $s_{\phi M\#2} = G_{V,\phi M}(\theta_M, \phi_M) + G_{H,\phi M}(\theta_M, \phi_M)$ | +| TRP1 location transformed to module reference system | $\theta_M = \theta_{1M\#1}, \phi_M = \phi_{1M\#1}$ | $\theta_M = \theta_{1M\#2}, \phi_M = \phi_{1M\#2}$ | +| TRP 2 location transformed to module reference system | $\theta_M = \theta_{2M\#1}, \phi_M = \phi_{2M\#1}$ | $\theta_M = \theta_{2M\#2}, \phi_M = \phi_{2M\#2}$ | + +(\*For simplicity, the DL signal in formula is normalized to 1) + +The method above is a simplified one compared to the realistic MRC implementation at UE receiver, in figure 6.3.6-4, a simulation is performed to compare UE performance projections using the method above against a more realistic LMMSE type demodulation for two orientations of the UE. The UE model is a '4-component type' described in Table 6.3.6-1. The MMSE solver assumed RSRP-based beam selection and a noise covariance matrix that depends on both, the uncorrelated thermal noise of the receiver and the correlated noise from the interferer. Channel estimation is genie type based on knowledge 4 component antenna gains and AWGN assumption. + +![Figure 6.3.6-4: UE performance difference between LMMSE vs RAN4 simplified SINR estimation. The figure contains three line graphs showing the percentage probability to support 2 AoA versus AoA separation (deg) for different UE orientations: Adjacent faces, Opposite faces, and Same face. Each graph compares LeftRight orientation1, LeftRight orientation2, and their respective MMSE performance. The performance is generally higher for MMSE, especially in the Adjacent faces scenario.](ed4ead5d57191d85eee9880ec32c4628_img.jpg) + +The figure consists of three subplots showing the percentage probability to support 2 AoA as a function of AoA separation (deg) for different UE orientations. The x-axis ranges from 0 to 180 degrees, and the y-axis ranges from 0 to 60%. + +- Adj. faces, arithmetic mean:** This plot shows performance for adjacent faces. The curves for LeftRight orientation1 and LeftRight orientation2 are relatively flat, starting around 12% at 60 degrees and slightly decreasing to around 10% at 160 degrees. The MMSE curves for both orientations show a slight increase, peaking around 18% at 120 degrees before decreasing to around 15% at 160 degrees. +- Opp. faces, arithmetic mean:** This plot shows performance for opposite faces. Both orientation1 and orientation2 curves show a significant increase in probability as AoA separation increases, starting around 5% at 60 degrees and reaching approximately 38% at 160 degrees. The MMSE curves follow a similar trend, starting around 2% at 60 degrees and reaching approximately 35% at 160 degrees. +- Same face, arithmetic mean:** This plot shows performance for the same face. The curves for FrontFront orientation1 and FrontFront orientation2 are relatively flat, starting around 18% at 60 degrees and slightly decreasing to around 10% at 160 degrees. The MMSE curves for both orientations show a slight increase, peaking around 20% at 120 degrees before decreasing to around 15% at 160 degrees. + +Figure 6.3.6-4: UE performance difference between LMMSE vs RAN4 simplified SINR estimation. The figure contains three line graphs showing the percentage probability to support 2 AoA versus AoA separation (deg) for different UE orientations: Adjacent faces, Opposite faces, and Same face. Each graph compares LeftRight orientation1, LeftRight orientation2, and their respective MMSE performance. The performance is generally higher for MMSE, especially in the Adjacent faces scenario. + +Figure 6.3.6-4: UE performance difference between LMMSE vs RAN4 simplified SINR estimation + +Some observations are listed below: + +1. For UEs with modules on opposite faces, there is not much difference between the simplified RAN4 SINR method and the LMMSE-based method. The similarity is expected since this type of UE does not have significant overlap of coverage areas, so SINR tends to be noise limited. +2. For UEs with modules on adjacent faces, there can be significant overlap in coverage. Some AoA pairs (specifically those with lower AoA offsets) are interference limited. For these scenarios, MMSE can help significantly because of polarization mismatch in the general case between the 2 rank1 DLs. + +3. The characteristic of the MMSE based receiver to help in interference limited cases becomes clear for a UE with modules on the same face. This type of UE has a lot of spatial overlap and therefore strong interference for low AoA offsets. The MMSE based receiver performs better than the RAN4 SINR calculation estimate for narrow AoA offsets where interference limited cases become more dominant. + +To further investigate how the gain imbalance will impact on the UE performance under the method above, Figure 6.3.6-5 show the overall probability performance gap between $\theta\theta$ DL and $\phi\phi$ DL, and three implementations are considered: Implementation#1 is 2 panels in the same side, Implementation#1 is 2 panels in the adjacent side, Implementation#3 is 2 panels in the opposite side. The X dB additional gain difference is added to V pattern and H pattern separately, i.e., $+X/2$ dB to V pattern and $-X/2$ dB to H pattern. Both the results of OR combining and arithmetic mean are provided. + +![Figure 6.3.6-5: Performance gap between θθ DL and φφ DL. The figure consists of six subplots arranged in a 3x2 grid. The rows represent three different implementations: Implementation#1 (2 panels in the same side), Implementation#2 (2 panels in the adjacent side), and Implementation#3 (2 panels in the opposite side). The columns represent two combining methods: OR combining (left column) and arithmetic mean combining (right column). Each subplot shows the 'performance gap' on the y-axis against the 'AoA offset' on the x-axis (ranging from 30 to 180). Three data series are plotted in each subplot: 'baseline' (blue line with circles), '3dB additional imbalance' (orange line with squares), and '10dB additional imbalance' (grey line with triangles). In all cases, the performance gap increases with AoA offset, peaking around 120-150 degrees. The 10dB imbalance case consistently shows the highest performance gap, followed by the 3dB imbalance case, and then the baseline case. The performance gap is generally higher for the arithmetic mean combining method compared to the OR combining method.](4349d5e2b079af7d2e45e10a3b8235e9_img.jpg) + +Figure 6.3.6-5: Performance gap between θθ DL and φφ DL. The figure consists of six subplots arranged in a 3x2 grid. The rows represent three different implementations: Implementation#1 (2 panels in the same side), Implementation#2 (2 panels in the adjacent side), and Implementation#3 (2 panels in the opposite side). The columns represent two combining methods: OR combining (left column) and arithmetic mean combining (right column). Each subplot shows the 'performance gap' on the y-axis against the 'AoA offset' on the x-axis (ranging from 30 to 180). Three data series are plotted in each subplot: 'baseline' (blue line with circles), '3dB additional imbalance' (orange line with squares), and '10dB additional imbalance' (grey line with triangles). In all cases, the performance gap increases with AoA offset, peaking around 120-150 degrees. The 10dB imbalance case consistently shows the highest performance gap, followed by the 3dB imbalance case, and then the baseline case. The performance gap is generally higher for the arithmetic mean combining method compared to the OR combining method. + +**Figure 6.3.6-5 Performance gap between $\theta\theta$ DL and $\phi\phi$ DL** + +The results show that when gain difference increase, the performance gap is not always enlarged since the gain difference will affect the received signal in both V branch and H branch and how the performance gap changes depending on panels location, AoA offset, etc. To reduce the performance gap between different polarization of DL polarization, one possible way is to construct final results by averaging the performance between $\theta\theta$ DL and $\phi\phi$ DL. Figure 6.3.6-6 shows that how the gain difference impact on the results after average. + +![Figure 6.3.6-6: Overall probability under different gain imbalance after average. The figure consists of six line graphs arranged in a 3x2 grid. The left column shows 'OR combining' results for Implementation #1, #2, and #3. The right column shows 'arithmetic mean combining' results for Implementation #1, #2, and #3. Each graph plots 'Overall probability' (y-axis) against 'AoA offset' (x-axis) from 30 to 180. Three data series are shown in each graph: 'baseline' (blue line with circles), '3dB additional imbalance' (orange line with squares), and '10dB additional imbalance' (grey line with diamonds). In all cases, the overall probability generally decreases as AoA offset increases, though some implementations show a peak around 90 degrees offset.](bf30e154f82662d212f21fccdfa2980f_img.jpg) + +Figure 6.3.6-6: Overall probability under different gain imbalance after average. The figure consists of six line graphs arranged in a 3x2 grid. The left column shows 'OR combining' results for Implementation #1, #2, and #3. The right column shows 'arithmetic mean combining' results for Implementation #1, #2, and #3. Each graph plots 'Overall probability' (y-axis) against 'AoA offset' (x-axis) from 30 to 180. Three data series are shown in each graph: 'baseline' (blue line with circles), '3dB additional imbalance' (orange line with squares), and '10dB additional imbalance' (grey line with diamonds). In all cases, the overall probability generally decreases as AoA offset increases, though some implementations show a peak around 90 degrees offset. + +**Figure 6.3.6-6 Overall probability under different gain imbalance after average** + +Compared to the performance gap between different DL polarizations, the performance change under different additional gain difference is smaller after average. We can also find that there is no conclusive relationship between gain imbalance and UE performance. + +In the end, the UE RF requirement is defined as the average (arithmetic mean) of the metric values for two DL polarization test conditions: the first condition is when the DL polarizations at both TRPs are ‘ $\theta\theta$ ’ and the second condition is when they are ‘ $\phi\phi$ ’. + +$$N\% = \frac{N_1\%(AoA_{1\theta}, AoA_{2\theta}) + N_2\%(AoA_{1\phi}, AoA_{2\phi})}{2}$$ + +Where ‘ $N\%_{(\dots)}$ ’ is the metric value for the requirement for the DL pols specified in the subscripts. + +### 6.3.7 NTC vs. ETC + +During the Rel-15 discussion when the legacy single-AoA spherical coverage requirement was specified, the verification conditions were captured as part of the requirement in TS 38.101-2 as a note, i.e., Note 2 in Table 7.3.4.3-1. + +Table 7.3.4.3-1: EIS spherical coverage for power class 3 + +| Operating band | EIS at 50 th %-tile CCDF (dBm) / Channel bandwidth | | | | | | | +|----------------|---------------------------------------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -77.4 | -74.4 | -71.4 | -68.4 | N.A | N.A | N.A | +| n258 | -77.4 | -74.4 | -71.4 | -68.4 | N.A | N.A | N.A | +| n259 | -71.9 | -68.9 | -65.9 | -62.9 | N.A | N.A | N.A | +| n260 | -73.1 | -70.1 | -67.1 | -64.1 | N.A | N.A | N.A | +| n261 | -77.4 | -74.4 | -71.4 | -68.4 | N.A | N.A | N.A | +| n262 | -69.7 | -66.7 | -63.7 | -60.7 | N.A | N.A | N.A | +| n263 | N.A | -66.2 | N.A | -60.2 | -57.2 | -54.2 | -53.2 | + +NOTE 1: The transmitter shall be set to $P_{MAX}$ as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. + +When it comes to the two-AoA spherical coverage requirement, the same issue emerged whether the requirement shall be verified under normal temperature conditions (NTC) but not under extreme temperature conditions (ETC). + +As the legacy spherical coverage requirement are required to be verified under NTC only, and the DL fixed power level for the two-AoA requirement is directly reused from the legacy spherical coverage requirement, it is reasonable to consider only the NTC condition for verifying the two-AoA requirement. There are two options on how to specify the multi-RX spherical coverage requirement with respect to NTC vs. ETC: + +- Option 1: Keep core requirement wording for the multi-RX spherical coverage requirement consistent with that of the legacy requirement, i.e., with a similar note as NOTE 2 in 38.101-2 Table 7.3.4.3-1, i.e., “The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1.” +- Option 2: Do not use the note in the multi-RX spherical coverage requirement, and RAN4 agrees the requirement shall be verified under NTC only. Also, RAN4 ask RAN5 to verify it for NTC only. + +The argument for Option 2 is usually RAN4 core requirements are specified independent of the verification conditions and such a convention should be preserved. The way the legacy requirement is specified is considered an exception, and there is a desire to avoid such exceptions. Furthermore, RAN4 has agreed to ask RAN5 to verify the requirement only under NTC. In this way, the RAN4 convention is kept, and no additional work is required to derive the appropriate core requirement for ETC. + +In the end, Option 2 is agreed upon. + +### 6.3.8 Consideration of AoA separation + +#### 6.3.8.1 Candidate AoA separation + +To reveal whether, in real networks, a multi-Rx UE has a clear tendency for the angle between TRPs that can be accessed, system level simulation is performed and the results are recorded in Annex A.2. The conclusion is that UE can access to TRP pairs only if the channel conditions are good enough, and there are no obvious preferred AoA separation. For simplicity while taking into account the constraints of the test system, 30°, 60°, 90°, 120°, 150° are agreed as the candidate AoA separations for requirement design. + +#### 6.3.8.2 1AoA vs 2 AoA + +How many AoA separations are needed to meet the requirement at the same time is the first problem to be solved. A popular option is to verify at least two AoA separations, one from [30°, 60°, 90°] and another one from [120°, 150°], and the intention is to get a full picture of UE performance. + +As the simulation results shown in Annex A.8, when AoA separation changes, different UE implementation will show different trends, e.g., For the case that panels in opposite side, UE performance become better when the AoA separation is larger, but when panels in same side, UE performance will be worse with the increase of AoA separation. Due to the different trends, if two different AoA separations need to meet the requirements simultaneously, to accommodate different UE implementation, the requirement for each AoA separation will always be gated by the implementation that + +has the worst performance. To avoid such restriction, RAN4 agree that only 1AoA separation from all candidates need to be verified. + +#### 6.3.8.3 Specified vs declared + +Another problem is that which AoA separation should be selected from the candidates and two options are raised during the discussion. One is to only specify one AoA separation in the specification, e.g., 90°, and with this approach, the worst performance across different placement of antenna modules should be used as requirement to accommodate different implementations. Another approach is to allow UE to declare its preferred AoA separation and the requirement for each AoA separation from candidates needs to be introduced in specification. Using this approach, the requirement will be linked to the UE implementation to show the best performance that one UE may achieved while avoiding put unnecessary restriction on UE implementation. The rules to construct the requirement is agreed as below: + +- Three types of reference UE implementation (two panels on the **same** side, two panels on the **adjacent** side and two panels on the **opposite** side) will be used to determine the core requirement: + +If the AoA offset would be declared by UE + +| AoA offset (degrees) | 30° | 60° | 90° | 120° | 150° | +|----------------------|------|------|----------|----------|----------| +| Reference UE | same | same | adjacent | opposite | opposite | + +If the AoA offset would be specified in the standard. + +| AoA offset (degrees) | 30° | 60° | 90° | 120° | 150° | +|----------------------|--------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------| +| Reference UE | Min (same, adjacent, opposite) | Min (same, adjacent, opposite ) | Min (same, adjacent, opposite ) | Min (same, adjacent, opposite ) | Min (same, adjacent, opposite ) | + +To better show UE performance under this feature, RAN4 agreed that the AoA separation to be verified can be declared by UE. + +# 7 Conclusion + +Based on the results in A.8, the average value for each AoA separation after taking out outlier are shown in below: + +**Table 7-1 average value based on the simulation results across companies** + +| | 30° | 60° | 90° | 120° | 150° | +|------------------------------|------|------|------|------|------| +| Qualcomm Incorporated | | 10.3 | 17.1 | 23.9 | 37.6 | +| Apple | | | 12.3 | 25.6 | 36.0 | +| LG Electronics | 9.4 | 6.5 | 12.5 | 19.2 | 20.0 | +| Samsung | 17.0 | 12.0 | 11.0 | 17.0 | 23.0 | +| Sony Ericsson | 26.9 | 21.6 | 16.2 | 24.8 | 33.0 | +| vivo | 21.9 | 14.5 | 11.9 | 18.6 | 24.3 | +| OPPO | 28.9 | 23.0 | 18.1 | 19.9 | 32.7 | +| Huawei, HiSilicon | 20.0 | 14.4 | 14.9 | 17.4 | 21.7 | +| Average | 20.7 | 14.6 | 14.3 | 20.8 | 28.5 | + +For the small AoA separation, a few companies have concern on the higher interference power level which may burden on Rx chain performance. To accommodate this concern, some margins are reserved for 30°, 60°, 90°, and the following table is agreed as final requirements: + +**Table 7-2: Multi-Rx requirement for power class 3** + +| AoA separation (degrees) | Probability (%) | +|--------------------------|-----------------| +| 30 | 18.5 | +| 60 | 13.5 | +| 90 | 12.5 | +| 120 | 20.5 | +| 150 | 28.5 | + +# Annex A: Simulation results + +## A.1 General + +This Annex intends to capture the simulation results and analysis during FR2 multi-Rx DL reception discussion that are helpful in understanding the development of the RF requirement. + +## A.2 AoA offset distribution with system simulation + +### Background + +As the RF requirement serves as a metric for UE's two-AoA spherical coverage performance. Since the AoA offset is varied in the real network, it is helpful to know how the AoA offset between two AoAs is distributed in real network in different scenarios, which can provide guidance on whether the range of AoA offset can be narrowed down and the requirement can be targeted for some common AoA offsets. + +#### R4-2218166 + +To understand if the angular difference between the two AoAs observed in a typical multi-TRP deployment scenario exhibits any pattern, we conduct simulation based on the system simulation assumptions in A.2 in TR 38.802. We simulate the following mTRP scenario as shown below. In particular, the inter-macro TRP distance is 200m, in each cell (hexagon), three micro TRPs are randomly dropped within each dashed circle (i.e., cluster) around the center of the circle (within 20m), following some minimum distance rules (such as the minimum distance between two micro TRPs is 40m, the minimum distance between a micro TRP to a macro TRP is 10m, etc.). UEs are randomly dropped in the cluster ( $R = 50\text{m}$ ). UE is assumed to have two back-to-back panels (pointing to opposite directions), with $4 \times 1$ antenna elements each. Details of other simulation parameters such as power can be found in Table A.2.1-1 in TR 38.802 corresponding to the Dense urban scenario. + +![Figure A.2.1-3: Cell layout for dense urban (3 Micro TRPs per Macro TRP). The diagram shows a hexagonal grid of cells. Each cell contains a Macro TRP at its center and three Micro TRPs clustered around it. A dashed circle of radius R represents the area where UEs are dropped. A zoomed-in view of one cell shows the Macro TRP at the center, three Micro TRPs within a dashed circle of radius R, and the distance D_micro-TRPs between two Micro TRPs. A legend indicates: Micro TRP (small antenna icon), R: radius of UE dropping within a cluster, D_micro-TRPs: distance between the micro TRPs, and Macro TRP (large antenna icon).](e97d663314aff9c29bf8971323e6539e_img.jpg) + +Figure A.2.1-3: Cell layout for dense urban (3 Micro TRPs per Macro TRP). The diagram shows a hexagonal grid of cells. Each cell contains a Macro TRP at its center and three Micro TRPs clustered around it. A dashed circle of radius R represents the area where UEs are dropped. A zoomed-in view of one cell shows the Macro TRP at the center, three Micro TRPs within a dashed circle of radius R, and the distance D\_micro-TRPs between two Micro TRPs. A legend indicates: Micro TRP (small antenna icon), R: radius of UE dropping within a cluster, D\_micro-TRPs: distance between the micro TRPs, and Macro TRP (large antenna icon). + +NOTE: Micro TRPs refers to micro TRP centers + +Figure A.2.1-3: Cell layout for dense urban (3 Micro TRPs per Macro TRP) + +The analysis methodology for these simulations is as follows: + +1. Assume each site (macro & micro TRP), in the modeled network is a potential point for the mTRP connection +2. Calculate RSRP between each site, taking into account BS gain in the link direction, UE gain in the link direction, and path loss + +3. Associate TRP1 and TRP2 according to max. RSRP and also according to one of the following panel mapping assumptions: + - No restriction on panel mapping (i.e., two beams with best RSRP can be mapped to the same panel)OR + - Best panel mapping (i.e., one AoA is mapped to the best beam/panel, and the other AoA is mapped to the best beam from the remaining panel) +4. Calculate AoA1 and AoA2 to these TRPs from the UE perspective +5. Evaluate the distribution of AoA1 - AoA2 ( $\Delta$ AoA) + +Results are shown in Figures 1 and 2 below. + +- It can be seen from Fig. A.2-1 that with unrestricted panel mapping, the distribution of $\Delta$ AoA is nearly uniform. In -other words, it takes values from 0 to 180 degrees with equal probability. +- In Fig. A.2-2, with best panel mapping restriction, it can be observed that for 95% of the UEs, $\Delta$ AoA > 60 degrees. +- We note the results depend in general on the UE antenna panel assumptions as well as the power levels of the macro and micro nodes. We welcome other companies to share results for comparison. + +![Figure A.2-1: CDF of |Δ AoA| from UE perspective (180 wrap). The plot shows a nearly linear relationship between the CDF (y-axis, 0 to 1) and the angle in degrees (x-axis, 0 to 180), indicating a uniform distribution.](031e354d9de9563c9f650e3e4fcba16d_img.jpg) + +The figure is a line graph titled "CDF of |Δ AoA| from UE perspective (180 wrap)". The y-axis is labeled "CDF" and ranges from 0 to 1. The x-axis ranges from 0 to 180 degrees with major ticks every 15 degrees. A single blue curve starts at (0,0) and rises almost perfectly straight to (180,1), indicating a uniform distribution of the angle difference. + +Figure A.2-1: CDF of |Δ AoA| from UE perspective (180 wrap). The plot shows a nearly linear relationship between the CDF (y-axis, 0 to 1) and the angle in degrees (x-axis, 0 to 180), indicating a uniform distribution. + +**Figure A.2-1: Distribution of $\Delta$ AoA with unrestricted panel mapping** + +![Figure A.2-2: CDF of |Δ AoA| from UE perspective (180 wrap). The plot shows a curve that is flat near zero for small angles and then rises steeply, indicating that most angle differences are large (greater than 60 degrees).](e51f9764097b236acbf8f544491dd24f_img.jpg) + +The figure is a line graph titled "CDF of |Δ AoA| from UE perspective (180 wrap)". The y-axis is labeled "CDF" and ranges from 0 to 1. The x-axis ranges from 0 to 180 degrees with major ticks every 15 degrees. A single blue curve starts at (0,0), remains very close to the x-axis until about 45 degrees, and then curves sharply upwards to reach (180,1). This indicates that the majority of the angle differences are concentrated in the upper range of possible values. + +Figure A.2-2: CDF of |Δ AoA| from UE perspective (180 wrap). The plot shows a curve that is flat near zero for small angles and then rises steeply, indicating that most angle differences are large (greater than 60 degrees). + +**Figure A.2-2: Distribution of $\Delta$ AoA with best panel mapping restriction** + +R4-2301573 + +To further figure out the AoA separation distribution in the dedicated deployment, we perform a simulation and 2 deployments are considered, as shown in Figure A.2-3: + +![Figure A.2-3: Indoor and Dense Urban (Macro only) deployment. The left diagram shows a 120m by 50m rectangular area with three red circles representing indoor clusters. Each circle contains four TRPs (blue dots). The distance between the centers of adjacent circles is 20m. The distance from the left and right edges of the area to the centers of the first and last circles is 10m. The distance from the top and bottom edges to the centers of the circles is 15m. The right diagram shows a hexagonal grid representing a dense urban deployment. The hexagons are colored and numbered: 0 (yellow), 1 (green), 2 (blue), and 3 (orange). The colors repeat in a pattern across the grid.](8269648391c59363ea61243864a2adf7_img.jpg) + +Figure A.2-3: Indoor and Dense Urban (Macro only) deployment. The left diagram shows a 120m by 50m rectangular area with three red circles representing indoor clusters. Each circle contains four TRPs (blue dots). The distance between the centers of adjacent circles is 20m. The distance from the left and right edges of the area to the centers of the first and last circles is 10m. The distance from the top and bottom edges to the centers of the circles is 15m. The right diagram shows a hexagonal grid representing a dense urban deployment. The hexagons are colored and numbered: 0 (yellow), 1 (green), 2 (blue), and 3 (orange). The colors repeat in a pattern across the grid. + +Figure A.2-3 Indoor and Dense Urban (Macro only) deployment + +For indoor scenario, 4 TRPs within the red circle are combined as a cluster, and UE can access any two of them. For Dense Urban, the TRPs with the same color can collaborate. Other simulation assumptions are mainly from TR38.802, and the results are shown in Figure A.2-4. + +![Figure A.2-4: AoA separation distribution in indoor and Dense urban. The figure contains two histograms. The left histogram, titled 'Indoor Hotspot', shows the 'UE number during simulation' on the y-axis (0 to 1200) against 'AoA separation' on the x-axis (0 to 180). The distribution is roughly bell-shaped, peaking at approximately 1100 UEs for an AoA separation of 80-100. The right histogram, titled 'Dense Urban', shows the 'UE number during simulation' on the y-axis (0 to 30) against 'AoA separation' on the x-axis (0 to 180). The distribution is skewed, with the highest number of UEs (approximately 27) at an AoA separation of 120-140.](4f90ddf705239c0ca535c91179212420_img.jpg) + +Figure A.2-4: AoA separation distribution in indoor and Dense urban. The figure contains two histograms. The left histogram, titled 'Indoor Hotspot', shows the 'UE number during simulation' on the y-axis (0 to 1200) against 'AoA separation' on the x-axis (0 to 180). The distribution is roughly bell-shaped, peaking at approximately 1100 UEs for an AoA separation of 80-100. The right histogram, titled 'Dense Urban', shows the 'UE number during simulation' on the y-axis (0 to 30) against 'AoA separation' on the x-axis (0 to 180). The distribution is skewed, with the highest number of UEs (approximately 27) at an AoA separation of 120-140. + +Figure A.2-4 AoA separation distribution in indoor and Dense urban + +Unfortunately, it is hard to further narrow down the AoA separation range based on the results, as we have already mentioned in the previous meeting, UE can access the TRP if the channel condition is acceptable and the AoA separation varies due to the UE location, channel condition changes, and we cannot get a so-called minimum or maximum threshold based on the simulation results. + +## A.3 Requirement applicability for sDCI and mDCI + +### Background + +It is preferable to define a single set of requirements for both sDCI and mDCI, and the following part provides the analysis of whether it is feasible under functionality-based requirement. + +#### R4-2308232 + +When both AoAs use the same fixed DL power level, due to the antenna gain and inter-beam interference being different for the signal from 2 AoA, the SINR at baseband for 2 layers are different, which means using the same fixed DL power will bring power imbalance artificially. + +For multi-DCI UE, each layer can be decoded separately and we can get the throughput of each layer, so the power imbalance doesn't matter and the -1 dB criterion above to judge each test point from a pair of AoA is still reasonable. However, things become different for sDCI UE because the 2 layers of sDCI UE share one transmission block and we can only get a total throughput of 2-layer MIMO, and there is no doubt that the power imbalance will affect this total + +throughput, and simply using -1dB as the criterion for each test point does not make sense anymore. Figure A.3-1 shows that how power imbalance will affect the throughput of sDCI UE. + +![Figure A.3-1: Impact of power imbalance for sDCI UE. This is a line graph showing Throughput (Y-axis, scaled by 10^7) versus SINR2 /dB (X-axis, ranging from -5 to 10). Six curves are plotted for different SINR1 values: -1, -2, -3, -4, -5, and -6 dB. A horizontal dashed line at approximately 3.05 on the Y-axis represents the 95% RMC threshold. The curves show that as SINR1 becomes more negative (increasing power imbalance), the throughput decreases. However, for SINR1 values of -1, -2, and -3 dB, the throughput reaches the 95% RMC threshold as SINR2 increases. For SINR1 = -4, -5, and -6 dB, the throughput remains below the 95% RMC threshold even at high SINR2 values.](ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg) + +Figure A.3-1: Impact of power imbalance for sDCI UE. This is a line graph showing Throughput (Y-axis, scaled by 10^7) versus SINR2 /dB (X-axis, ranging from -5 to 10). Six curves are plotted for different SINR1 values: -1, -2, -3, -4, -5, and -6 dB. A horizontal dashed line at approximately 3.05 on the Y-axis represents the 95% RMC threshold. The curves show that as SINR1 becomes more negative (increasing power imbalance), the throughput decreases. However, for SINR1 values of -1, -2, and -3 dB, the throughput reaches the 95% RMC threshold as SINR2 increases. For SINR1 = -4, -5, and -6 dB, the throughput remains below the 95% RMC threshold even at high SINR2 values. + +**Figure A.3-1 impact of power imbalance for sDCI UE** + +In the simulation, the SINR1 and SINR2 represent the SINR value from 2AoA. Obviously, due to the power imbalance, even though one of SINRs is less than -1 dB, the total throughput still can achieve 95% RMC and pass the test. + +Does raising or lowering the power of one of the AoA can help with this problem? The answer is NO. Simply changing the power level cannot remove the power imbalance, and the only way to solve this issue is for each test point, the DL power should be changed, but this scheme is too complicated from both the verification and evaluation perspectives. + +As a compromise, we can only focus on that whether the sDCI UE can pass the same requirement as mDCI under power imbalance. In Figure A.3-1, the simulation shows that when both SINRs is larger than -1 dB, the total throughput still can be larger than 95% RMC, which means the -1 dB in simulation still can ensure the AoA pair can pass the test. The only omission here is that cases where either SINR1 or SINR2 is less than <-1 dB and UE can still pass the test are accounted for in the requirement. As we mention above, even though we realize this omission, it is hard to be verified or evaluated. So we think it is enough to confirm the same requirement can be applied to both sDCI and mDCI UEs under the current evaluation method. + +## A.4 Evaluation of EIS-based requirement + +### Background + +A sensitivity-based requirement was a possible way during the discussion, but was eventually discarded due to its complexity. The related evaluation can be found in [11][12][13][14]. + +## A.5 Impact of UE orientation + +### Background + +As mentioned in Clause 6.3.4, it is identified that UE has different performance under different UE orientation due to the test system constrains, and the following part capture the evaluations. + +R4-2304824 + +Our simulation results shown in section 2.1.3 gather simulation data for all angular separation values, for 3 typical UE orientations, for 3 different panel placement implementations, respectively. Those data are visualized in Figure A.6-1 for convenience of comparison. From the figure, it can be observed that different panel placement implementations show obvious different trend in angular separation preference, thus it is not proper to specify requirements for both small angular separation and large angular separation. + +Different UE orientations also impact performance a lot. From Figure A.5-1 (a) and (c), it can be observed that there is even orientation showing bad performance for every angular separation from 30° to 180°, thus it is not proper to specify requirements for all UE orientations. + +![Line graph titled '2AoA coverage for different UE orientation' showing coverage percentages for three orientations across angular separations of 30, 60, 90, 120, 150, and 180 degrees. The graph includes a legend for orientation_1 (blue), orientation_2 (red), and orientation_3 (green). A side diagram shows Module1 (Vertical) and Module2 (Horizontal) panel placements.](3a310163273edcf70c19269a06d0cdf2_img.jpg) + +The graph shows the 2AoA coverage for three different UE orientations across various angular separations. The y-axis represents the coverage percentage from 0% to 50% in 5% increments. The x-axis shows angular separations of 30, 60, 90, 120, 150, and 180 degrees. Orientation 2 (red) shows the highest coverage, peaking at 30% at 90 degrees. Orientation 3 (green) follows, peaking at approximately 23% at 90 degrees. Orientation 1 (blue) shows the lowest coverage, dropping to near 0% at 90 and 120 degrees. The side diagram illustrates Module1 as a vertical panel and Module2 as a horizontal panel. + +| Angular Separation (°) | orientation_1 (%) | orientation_2 (%) | orientation_3 (%) | +|------------------------|-------------------|-------------------|-------------------| +| 30 | 10 | 11 | 11 | +| 60 | 8 | 23 | 19 | +| 90 | 2 | 30 | 23 | +| 120 | 1 | 23 | 21 | +| 150 | 2 | 15 | 15 | +| 180 | 0 | 8 | 8 | + +Line graph titled '2AoA coverage for different UE orientation' showing coverage percentages for three orientations across angular separations of 30, 60, 90, 120, 150, and 180 degrees. The graph includes a legend for orientation\_1 (blue), orientation\_2 (red), and orientation\_3 (green). A side diagram shows Module1 (Vertical) and Module2 (Horizontal) panel placements. + +a. simulation results of Right + Back panel placement + +![Line graph titled '2AoA coverage for different UE orientation' showing coverage percentages for three orientations across angular separations of 30, 60, 90, 120, 150, and 180 degrees. The graph includes a legend for orientation_1 (blue), orientation_2 (red), and orientation_3 (green). A side diagram shows Module1 (Vertical) and Module2 (Vertical) panel placements.](4bff5f22997753bcf1997c715118012d_img.jpg) + +The graph shows the 2AoA coverage for three different UE orientations across various angular separations. The y-axis represents the coverage percentage from 0% to 50% in 5% increments. The x-axis shows angular separations of 30, 60, 90, 120, 150, and 180 degrees. Orientation 2 (red) shows the highest coverage, increasing to about 43% at 150 degrees. Orientation 3 (green) follows, increasing to about 43% at 150 degrees. Orientation 1 (blue) shows the lowest coverage, increasing to about 42% at 150 degrees. The side diagram illustrates Module1 as a vertical panel and Module2 as a vertical panel. + +| Angular Separation (°) | orientation_1 (%) | orientation_2 (%) | orientation_3 (%) | +|------------------------|-------------------|-------------------|-------------------| +| 30 | 0 | 0 | 0 | +| 60 | 1 | 4 | 2 | +| 90 | 6 | 23 | 14 | +| 120 | 29 | 41 | 36 | +| 150 | 42 | 43 | 43 | +| 180 | 44 | 44 | 44 | + +Line graph titled '2AoA coverage for different UE orientation' showing coverage percentages for three orientations across angular separations of 30, 60, 90, 120, 150, and 180 degrees. The graph includes a legend for orientation\_1 (blue), orientation\_2 (red), and orientation\_3 (green). A side diagram shows Module1 (Vertical) and Module2 (Vertical) panel placements. + +b. simulation results of Left + Right panel placement + +![Line graph titled '2AoA coverage for different UE orientation' showing coverage percentages for three orientations across angles 30 to 180. Includes a legend for orientation_1, orientation_2, and orientation_3, and a side diagram showing Module1 and Module2 vertical placement.](068b3a3247570c4b78342a943f15de9e_img.jpg) + +The figure is a line graph titled "2AoA coverage for different UE orientation". The y-axis represents coverage percentage from 0% to 50% in 5% increments. The x-axis represents angles from 30 to 180 in 30-degree increments. Three data series are plotted: orientation\_1 (blue line with circles), orientation\_2 (red line with circles), and orientation\_3 (green line with circles). To the right of the graph is a diagram of a vertical rectangle representing a UE, divided into "Module2 (Vertical)" at the top and "Module1 (Vertical)" at the bottom. Three blue circles are shown above the rectangle, representing different antenna configurations. + +| Angle | orientation_1 (%) | orientation_2 (%) | orientation_3 (%) | +|-------|-------------------|-------------------|-------------------| +| 30 | 28 | 13 | 7 | +| 60 | 27 | 21 | 6 | +| 90 | 11 | 20 | 4 | +| 120 | 2 | 9 | 2 | +| 150 | 1 | 2 | 1 | +| 180 | 1 | 1 | 1 | + +Line graph titled '2AoA coverage for different UE orientation' showing coverage percentages for three orientations across angles 30 to 180. Includes a legend for orientation\_1, orientation\_2, and orientation\_3, and a side diagram showing Module1 and Module2 vertical placement. + +c. simulation results of Left + Left panel placement + +Figure A.5-1 Visualization of our simulation results + +R4-2305098 + +The simulation results for different UE orientations are shown in Figure A.5-2 and the post-processing rules that mentioned in previous part are used. + +![Three line graphs showing spherical coverage (N%) vs AoA offset for different module orientations: same side, back-to-back, and adjacent side. Each graph includes data for Top, Bottom, Left, Right, Front, and Back orientations.](77a781dfb114c3e2b399f876f1808cfd_img.jpg) + +**Spherical coverage when modules are same side** + +| AoA offset | Top | Bottom | Left | Right | Front | Back | +|------------|------|--------|------|-------|-------|------| +| 30 | 36.0 | 21.0 | 21.0 | 21.0 | 21.0 | 21.0 | +| 60 | 21.0 | 27.0 | 31.0 | 31.0 | 27.0 | 27.0 | +| 90 | 10.0 | 28.0 | 30.0 | 30.0 | 28.0 | 28.0 | +| 120 | 20.0 | 32.0 | 35.0 | 35.0 | 32.0 | 32.0 | +| 150 | 30.0 | 38.0 | 38.0 | 38.0 | 30.0 | 30.0 | + +**Spherical coverage when modules are back-to-back** + +| AoA offset | Top | Bottom | Left | Right | Front | Back | +|------------|------|--------|------|-------|-------|------| +| 30 | 21.0 | 18.0 | 11.0 | 11.0 | 11.0 | 11.0 | +| 60 | 13.0 | 30.0 | 25.0 | 25.0 | 13.0 | 13.0 | +| 90 | 6.0 | 30.0 | 21.0 | 21.0 | 17.0 | 17.0 | +| 120 | 24.0 | 29.0 | 18.0 | 18.0 | 16.0 | 16.0 | +| 150 | 28.0 | 34.0 | 22.0 | 22.0 | 20.0 | 20.0 | + +**Spherical coverage when modules are adjacent side** + +| AoA offset | Top | Bottom | Left | Right | Front | Back | +|------------|------|--------|------|-------|-------|------| +| 30 | 15.0 | 15.0 | 13.0 | 13.0 | 15.0 | 15.0 | +| 60 | 19.0 | 25.0 | 20.0 | 20.0 | 25.0 | 25.0 | +| 90 | 15.0 | 25.0 | 22.0 | 22.0 | 25.0 | 25.0 | +| 120 | 21.0 | 21.0 | 18.0 | 18.0 | 21.0 | 21.0 | +| 150 | 17.0 | 21.0 | 16.0 | 16.0 | 21.0 | 21.0 | + +Three line graphs showing spherical coverage (N%) vs AoA offset for different module orientations: same side, back-to-back, and adjacent side. Each graph includes data for Top, Bottom, Left, Right, Front, and Back orientations. + +Figure A.5-2 N% for different orientations + +Some curves are totally overlapped is because the model itself has symmetry. When metal blockage exists, the EM field will be scattered due to the reflection, and it is hard to summarize a rule between N% and AoA offset. The UE orientation also led to different results although the AoA offset is same, and the reason here is that the relative position between AoA pair and UE will be changed under different UE orientation. + +#### R4-2304603 + +To evaluate the impact of different choices on module orientations relative to the UE reference coordinate system, a UE with 2 identical modules housed in adjacent faces was used. Each module comprised a 4x1 dual polarized element array. The coverage pattern is shown in figure A.5-3. Annex C has details on the module orientation in the UE reference coordinate system. Module locations were grouped into two categories. + +- In the first category, one module pattern covered the polar region of the reference coordinate system. Examples: Front+Bottom, Front+Top, Front+Right +- In the second category, both modules cover equatorial regions (away from polar regions). Examples: Top+Left, Top+Right + +![Figure A.5-3: Coverage pattern of example UE with modules on adjacent faces. The figure shows a 3D visualization of a user equipment (UE) with two antenna modules. The coverage is represented by a color map on the surface of the UE, ranging from blue (-30 dB) to red (0 dB). A color bar on the right indicates the gain levels. The UE is shown in a coordinate system with x, y, and z axes, and azimuth (az) and elevation (el) angles are indicated.](6a842e59ecf31b0d6f6721ac4e76f160_img.jpg) + +Figure A.5-3: Coverage pattern of example UE with modules on adjacent faces. The figure shows a 3D visualization of a user equipment (UE) with two antenna modules. The coverage is represented by a color map on the surface of the UE, ranging from blue (-30 dB) to red (0 dB). A color bar on the right indicates the gain levels. The UE is shown in a coordinate system with x, y, and z axes, and azimuth (az) and elevation (el) angles are indicated. + +Figure A.5-3: Coverage pattern of example UE with modules on adjacent faces + +The list in each category is not exhaustive but deemed sufficient to capture characteristic trends. + +Figures A.5-4 and A.5-5 shows a comparison of overall probability to support 2TRP DL for the example UE chosen for the UE positioning study. Category 1 orientations are captured in cool colors (blues and greens), and category 2 orientations are captured in warm colors (reds). + +![Figure A.5-4: OR combining method. This is a line graph showing the 'TE constrained overall 2TRP probability (%)' on the y-axis (0 to 50) against 'AoA Sep (deg)' on the x-axis (60 to 180). It compares various module orientations. Category 1 orientations (FrontTop HH, FrontTop VV, FrontBot HH, FrontBot VV, FrontLeft HH, FrontLeft VV) show higher probabilities, peaking around 35% at 120 degrees. Category 2 orientations (TopRight HH, TopRight VV, TopLeft HH, TopLeft VV) show lower probabilities, peaking around 15% at 150 degrees. Solid lines represent H-scanning and dashed lines represent V-scanning for each orientation.](8ba0063bcb9cdac03f1c4497526f1898_img.jpg) + +Figure A.5-4: OR combining method. This is a line graph showing the 'TE constrained overall 2TRP probability (%)' on the y-axis (0 to 50) against 'AoA Sep (deg)' on the x-axis (60 to 180). It compares various module orientations. Category 1 orientations (FrontTop HH, FrontTop VV, FrontBot HH, FrontBot VV, FrontLeft HH, FrontLeft VV) show higher probabilities, peaking around 35% at 120 degrees. Category 2 orientations (TopRight HH, TopRight VV, TopLeft HH, TopLeft VV) show lower probabilities, peaking around 15% at 150 degrees. Solid lines represent H-scanning and dashed lines represent V-scanning for each orientation. + +Figure A.5-4: OR combining method + +![Figure A.5-5: mean combining method. This is a line graph showing the 'TE constrained overall 2TRP probability (%)' on the y-axis (0 to 50) against 'AoA Sep (deg)' on the x-axis (60 to 180). It compares the same module orientations as Figure A.5-4. The probabilities are generally lower than in the OR combining method, with Category 1 orientations peaking around 18% and Category 2 orientations peaking around 12%.](b5c525e7df912952586920ac3d3e4c57_img.jpg) + +Figure A.5-5: mean combining method. This is a line graph showing the 'TE constrained overall 2TRP probability (%)' on the y-axis (0 to 50) against 'AoA Sep (deg)' on the x-axis (60 to 180). It compares the same module orientations as Figure A.5-4. The probabilities are generally lower than in the OR combining method, with Category 1 orientations peaking around 18% and Category 2 orientations peaking around 12%. + +Figure A.5-5: mean combining method + +Here too, the dashed and solid trends for any one color track closely. This suggests that module orientation (H-scanning or V-scanning) seems to make a relatively small difference in the projected overall probability result for a UE with modules on adjacent faces. + +## A.6 Impact of gain imbalance between antenna module + +### Background + +For a real UE, the performance of panels may not be exactly same. The following part show how the gain imbalance impacts the functionality-based requirement. + +#### R4-2307482 + +The simulation of the pass ratio over the whole sphere is performed by considering different antenna module performances, different UE orientations, and different antenna module combinations. + +- Antenna module performance + - Case 1: antenna module#1 and antenna module#2 are assumed to have the same performance gain + - Case 2: antenna module#1 is assumed to have a 3dB lower performance gain than antenna module#2 + - Case 3: antenna module#2 is assumed to have a 3dB lower performance gain than antenna module#1 + - UE orientation + - Z-axis oriented + - Y-axis oriented + - X-axis oriented +- Probes are located in the xz plane in [2] +- Antenna module combination + - left-side & right-side combination + - left-side & top-side combination + +![Diagram of a User Equipment (UE) model on a stand, showing antenna modules and probe locations. The UE is a sphere with a grid. Probes are labeled P0, P60, P120, and P150. Arrows indicate rotation around the Z-axis and Y-axis. A small inset shows a probe with a directional arrow.](555996c5b2c9b5333629d95b83d1cb73_img.jpg) + +Diagram of a User Equipment (UE) model on a stand, showing antenna modules and probe locations. The UE is a sphere with a grid. Probes are labeled P0, P60, P120, and P150. Arrows indicate rotation around the Z-axis and Y-axis. A small inset shows a probe with a directional arrow. + +Figure A.6-1, Figure A.6-2, and Figure A.6-3 show the results of the pass ratio of both OR combining and averaging for Case1, Case2, and Case3, respectively. + +![Two line graphs showing Pass Ratio (%) vs AOA Offset for Case 1. (a) OR combining: Y-axis 0-70, X-axis 20-180. (b) Averaging: Y-axis 0-70, X-axis 20-180. Both graphs show data for Zaxis(left/right), Yaxis(left/right), Xaxis(left/right), and Averaged(left/right) combinations. In (a), Yaxis(left/right) increases to ~65% at 180 offset. In (b), Yaxis(left/right) increases to ~65% at 180 offset. Other combinations remain relatively flat between 20% and 40%.](6f1d6debd3f3eada4104f0302c912672_img.jpg) + +(a). OR combining +(b) Averaging + +Two line graphs showing Pass Ratio (%) vs AOA Offset for Case 1. (a) OR combining: Y-axis 0-70, X-axis 20-180. (b) Averaging: Y-axis 0-70, X-axis 20-180. Both graphs show data for Zaxis(left/right), Yaxis(left/right), Xaxis(left/right), and Averaged(left/right) combinations. In (a), Yaxis(left/right) increases to ~65% at 180 offset. In (b), Yaxis(left/right) increases to ~65% at 180 offset. Other combinations remain relatively flat between 20% and 40%. + +Figure A.6-1: Pass Ratio of both 'OR combining' and 'averaging' for Case 1. + +![Figure A.6-2: Pass Ratio of both 'OR combining' and 'averaging' for Case 2. (a) OR combining: Pass Ratio (%) vs AOA Offset (20 to 180). (b) Averaging: Pass Ratio (%) vs AOA Offset (20 to 180). Both plots show performance for Zaxis, Yaxis, and Xaxis (left/right and left/top) configurations.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +Figure A.6-2 consists of two line graphs, (a) and (b), showing the Pass Ratio (%) versus AOA Offset (20 to 180) for Case 2. Both graphs compare 'OR combining' and 'Averaging' methods across various antenna configurations: Zaxis(left/right), Yaxis(left/right), Xaxis(left/right), Avgel(left/right), Zaxis(left/top), Yaxis(left/top), Xaxis(left/top), and Avgel(left/top). In both cases, the Yaxis(left/right) configuration (blue solid line with circles) shows the highest pass ratio, increasing from approximately 15% at 20 degrees to about 55% at 180 degrees. The Xaxis(left/right) configuration (black solid line with circles) shows a peak pass ratio of about 30% at 120 degrees before dropping to near 0% at 180 degrees. The 'OR combining' method generally achieves higher pass ratios than the 'Averaging' method across most configurations and offsets. + +Figure A.6-2: Pass Ratio of both 'OR combining' and 'averaging' for Case 2. (a) OR combining: Pass Ratio (%) vs AOA Offset (20 to 180). (b) Averaging: Pass Ratio (%) vs AOA Offset (20 to 180). Both plots show performance for Zaxis, Yaxis, and Xaxis (left/right and left/top) configurations. + +Figure A.6-2: Pass Ratio of both 'OR combining' and 'averaging' for Case 2. + +![Figure A.6-3: Pass Ratio of both 'OR combining' and 'averaging' for Case 3. (a) OR combining: Pass Ratio (%) vs AOA Offset (20 to 180). (b) Averaging: Pass Ratio (%) vs AOA Offset (20 to 180). Both plots show performance for Zaxis, Yaxis, and Xaxis (left/right and left/top) configurations.](8a4275b35551f2ec9825a1aa442c0db1_img.jpg) + +Figure A.6-3 consists of two line graphs, (a) and (b), showing the Pass Ratio (%) versus AOA Offset (20 to 180) for Case 3. The graphs compare 'OR combining' and 'Averaging' methods across the same antenna configurations as in Figure A.6-2. In this case, the Yaxis(left/right) configuration (blue solid line with circles) shows a more gradual increase in pass ratio, reaching about 55% at 180 degrees. The Xaxis(left/right) configuration (black solid line with circles) peaks at about 30% at 120 degrees and drops to about 10% at 180 degrees. The 'OR combining' method again generally outperforms the 'Averaging' method. + +Figure A.6-3: Pass Ratio of both 'OR combining' and 'averaging' for Case 3. (a) OR combining: Pass Ratio (%) vs AOA Offset (20 to 180). (b) Averaging: Pass Ratio (%) vs AOA Offset (20 to 180). Both plots show performance for Zaxis, Yaxis, and Xaxis (left/right and left/top) configurations. + +Figure A.6-3: Pass Ratio of both 'OR combining' and 'averaging' for Case 3. + +R4-2309284 + +Sometimes it is preferable to use actual module coverage data, but in conjunction with the spherical coverage calibration condition, we may end up with an over-specified set of boundary conditions. (i.e cannot meet both REFSENS and spherical coverage gain drop at the same time.). In these cases, the baseline assumption in a previous WF suggests to 'scale antenna gain', see excerpt below (figure 2.4-1). + +## 2.6 UE implementations to study for requirement derivation + +Simulation guidelines for UEs that do not align with both peak EIS and spherical coverage in current spec: + +**Option 1:** Adjust the beam shape or scale the antenna gain to make UE align with both peak EIS and spherical coverage. + +There are several ways to achieve this scaling: the first method would apply to both modules equally (symmetric scaling of gains in way to 'tune' the spherical coverage gain drop), and the second method would reduce the gain of one of the modules relative to the other (asymmetric scaling). Asymmetric scaling makes the sensitivity worse for one module over the other, so it can impact the probability metric significantly, see tables below. + +![Antenna gain CDF plot for equal modules. X-axis is 'Gain drop [dB]' from -30 to 0. Y-axis is 'Antenna gain CDF, normalized to peak gain' from 0 to 1. A blue curve rises from left to right. A data point is marked at X: -11.955, Y: 0.561266. 3D spherical plot showing module coverage for equal modules. Two symmetrical lobes (red/yellow) are shown on a 3D grid. A color bar on the right indicates gain from 0 to -30 dB. Line graph showing % Probability to support metric vs AoA separation (deg). Red line: symm. modules. Blue line: asymm. scaling. X-axis: 0 to 180. Y-axis: 0 to 60. Antenna gain CDF plot for asymmetric scaled modules. X-axis is 'Gain drop [dB]' from -30 to 0. Y-axis is 'Antenna gain CDF, normalized to peak gain' from 0 to 1. A blue curve rises from left to right. A data point is marked at X: -10.865, Y: 0.488704. 3D spherical plot showing module coverage for asymmetric scaled modules. One lobe is significantly smaller than the other. A color bar on the right indicates gain from 0 to -25 dB.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +| Left and Right modules,
legacy antenna gain | Module coverage relative to
positioner centric grid (*) | Probability to support 2 TRP DL (option 1
metric [1]+ OR combining) | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------|--------------------|----|---|---|----|----|----|-----|----|----|-----|----|----|-----|----|----|-----|----|----|-----|----|----| +|

Equal modules

| |

UE with modules on opp. sides

Estimated data for Probability to support 2 TRP DL
AoA separation (deg) symm. modules (%) asymm. scaling (%)
6000
801510
1002815
1204220
1404824
1605022
1805018
| AoA separation (deg) | symm. modules (%) | asymm. scaling (%) | 60 | 0 | 0 | 80 | 15 | 10 | 100 | 28 | 15 | 120 | 42 | 20 | 140 | 48 | 24 | 160 | 50 | 22 | 180 | 50 | 18 | +| AoA separation (deg) | symm. modules (%) | | asymm. scaling (%) | | | | | | | | | | | | | | | | | | | | | | | | +| 60 | 0 | 0 | | | | | | | | | | | | | | | | | | | | | | | | | +| 80 | 15 | 10 | | | | | | | | | | | | | | | | | | | | | | | | | +| 100 | 28 | 15 | | | | | | | | | | | | | | | | | | | | | | | | | +| 120 | 42 | 20 | | | | | | | | | | | | | | | | | | | | | | | | | +| 140 | 48 | 24 | | | | | | | | | | | | | | | | | | | | | | | | | +| 160 | 50 | 22 | | | | | | | | | | | | | | | | | | | | | | | | | +| 180 | 50 | 18 | | | | | | | | | | | | | | | | | | | | | | | | | +|

Asymm. scaled modules
(9.0 dB reduction in one)

| | | | | | | | | | | | | | | | | | | | | | | | | | | + +Antenna gain CDF plot for equal modules. X-axis is 'Gain drop [dB]' from -30 to 0. Y-axis is 'Antenna gain CDF, normalized to peak gain' from 0 to 1. A blue curve rises from left to right. A data point is marked at X: -11.955, Y: 0.561266. 3D spherical plot showing module coverage for equal modules. Two symmetrical lobes (red/yellow) are shown on a 3D grid. A color bar on the right indicates gain from 0 to -30 dB. Line graph showing % Probability to support metric vs AoA separation (deg). Red line: symm. modules. Blue line: asymm. scaling. X-axis: 0 to 180. Y-axis: 0 to 60. Antenna gain CDF plot for asymmetric scaled modules. X-axis is 'Gain drop [dB]' from -30 to 0. Y-axis is 'Antenna gain CDF, normalized to peak gain' from 0 to 1. A blue curve rises from left to right. A data point is marked at X: -10.865, Y: 0.488704. 3D spherical plot showing module coverage for asymmetric scaled modules. One lobe is significantly smaller than the other. A color bar on the right indicates gain from 0 to -25 dB. + +![Antenna gain CDF, normalized to peak gain for equal modules. The curve shows a gain drop of -11.055 dB at a CDF of 0.95296. Module coverage relative to positioner centric grid for equal modules. A 3D plot showing a red sphere with green and blue ellipsoids representing coverage areas. A color bar on the right indicates gain values from 0 to -30 dB. Probability to support 2 TRP DL (option 1 metric [1]+ OR combining) for UE with modules on adjacent sides. The graph shows two curves: 'symm. modules' (red) and 'asymm. scaling' (blue). The red curve peaks at approximately 35% probability at 120 degrees AoA separation, while the blue curve remains relatively flat around 20%. Antenna gain CDF, normalized to peak gain for asymmetric modules. The curve shows a gain drop of -10.865 dB at a CDF of 0.48074. Module coverage relative to positioner centric grid for asymmetric modules. A 3D plot similar to the one above but with a more elongated coverage area. A color bar on the right indicates gain values from 0 to -30 dB.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +| Left and Front modules, legacy antenna gain | Module coverage relative to positioner centric grid (*) | Probability to support 2 TRP DL (option 1 metric [1]+ OR combining) | +|------------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------------------| +| Equal modules
| | | +| Asymm. scaled modules (7.5 dB reduction in one)
| | | + +Antenna gain CDF, normalized to peak gain for equal modules. The curve shows a gain drop of -11.055 dB at a CDF of 0.95296. Module coverage relative to positioner centric grid for equal modules. A 3D plot showing a red sphere with green and blue ellipsoids representing coverage areas. A color bar on the right indicates gain values from 0 to -30 dB. Probability to support 2 TRP DL (option 1 metric [1]+ OR combining) for UE with modules on adjacent sides. The graph shows two curves: 'symm. modules' (red) and 'asymm. scaling' (blue). The red curve peaks at approximately 35% probability at 120 degrees AoA separation, while the blue curve remains relatively flat around 20%. Antenna gain CDF, normalized to peak gain for asymmetric modules. The curve shows a gain drop of -10.865 dB at a CDF of 0.48074. Module coverage relative to positioner centric grid for asymmetric modules. A 3D plot similar to the one above but with a more elongated coverage area. A color bar on the right indicates gain values from 0 to -30 dB. + +Note that all the UEs above are calibrated to legacy spherical coverage, but the probability metrics can be vastly different between UEs with equal modules and UEs with asymmetric modules. This difference may be tolerable for small differences (2 dB or less) across modules, but this type of implementation is not suitable for 2 TRP reception if the asymmetric gain split is larger across the modules. Larger gain splits become necessary if the individual module + +## A.7 Test time estimates + +### Background + +Test time is an important aspect to be considered in search of the proper requirement concept. The following part provide the estimation for EIS-based requirement and functionality-based requirement. + +#### R4-2302522 + +In the previous sections it was shown that the test time for the multi-AoA DL spherical test depends on various aspects, e.g., + +- number of AoA2 probes +- number of polarization combinations (AoA1q, AoA2q), (AoA1q, AoA2f), (AoA1f, AoA2q), (AoA1f, AoA2f) +- single-DCI vs multi-DCI schemes +- parametric vs non-parametric test approach + +The summary of test time estimates is tabulated in Table A.7-1. Big differences in terms of test time/test efforts can be observed; as expected, the non-parametric test approach yields the lowest test time. + +Table A.7-1: Overview of Approximate Test Times + +| Power Class | Grid Type | Test Approach | Minimum Number of Spherical Coverage Test Points N | Number of Polarization Combinations P | Number of AoA2 Probes M | Effort/Test Time for multi-AoA DL spherical coverage test [min] | | Notes | | +|-------------|--------------------|----------------------------------------|-----------------------------------------------------------|----------------------------------------------|--------------------------------|-----------------------------------------------------------------|------|---------------------------------------------------------------|--| +| | | | | | | Min | Max | | | +| PC1/PC3 | constant-step size | Parametric single-DCI | 312 | 4 | 4 | 1331 | 1799 | Min/Max test time depends on Joint 2 AoA Sensitivity approach | | +| | | | | | 3 | 1248 | 1716 | | | +| | | | | | 2 | 1165 | 1633 | | | +| | | | | 2 | 4 | 666 | 900 | | | +| | | | | | 3 | 624 | 858 | | | +| | | | | | 2 | 582 | 816 | | | +| PC1/PC3 | constant-step size | Parametric multi-DCI | 312 | any | 4 | 666 | | N/A | | +| | | | | | 3 | 624 | | | | +| | | | | | 2 | 582 | | | | +| PC1/PC3 | constant-step size | Non-Parametric single-DCI or multi-DCI | 312 | 4 | 4 | 21 | 333 | Min/Max depends on early Pass | | +| | | | | | 3 | 21 | 250 | | | +| | | | | | 2 | 21 | 166 | | | +| | | | | 2 | 4 | 21 | 166 | | | +| | | | | | 3 | 21 | 125 | | | +| | | | | | 2 | 21 | 83 | | | + +Given the large difference in test time, feedback from industry is requested whether the test approach for multi-AoA spherical coverage should be based on a parametric test (as legacy spherical coverage test case) or on a non-parametric test. + +## A.8 Simulation campaign for requirement design + +### Background + +This section summarizes the simulation results from companies for final RF requirement, and the results for 3 typical UE implementations and 2 candidate combining methods are provided. + +Table A.8-1 Overall probability with OR combining + +| OR combining | Panels in adjacent faces | | | | | | +|-----------------------|--------------------------|------|------|------|------|------| +| | 30 | 60 | 90 | 120 | 150 | 180 | +| Qualcomm Incorporated | | 23.7 | 33.6 | 35.4 | 26.6 | | +| Apple | 13.7 | 22.5 | 24.4 | 21.7 | 16.6 | 12.0 | +| LG Electronics | 8.2 | 16.3 | 24.9 | 24.5 | 28.2 | 28.6 | +| Samsung-metal | 8.0 | 17.0 | 21.0 | 15.0 | 7.0 | 1.0 | +| Samsung-plastic | 13.0 | 21.0 | 23.0 | 22.0 | 16.0 | 10.0 | +| Sony, Ericsson | 11.6 | 23.2 | 33.0 | 32.0 | 27.0 | 13.6 | +| vivo-metal | 12.3 | 17.6 | 18.5 | 17.2 | 16.2 | 8.8 | +| vivo-plastic | 11.1 | 20.2 | 23.0 | 19.7 | 15.5 | 7.7 | +| OPPO | 13.5 | 26.6 | 36.1 | 28.0 | 17.0 | 5.9 | +| Huawei, HiSilicon | 18.0 | 30.6 | 35.7 | 30.9 | 17.3 | 6.3 | + +| OR combining | Panels in opposite faces | | | | | | +|-----------------------|--------------------------|------|------|------|------|------| +| | 30 | 60 | 90 | 120 | 150 | 180 | +| Qualcomm Incorporated | | 7.0 | 22.0 | 40.9 | 48.4 | | +| Apple | 0.1 | 9.6 | 27.0 | 45.6 | 49.4 | 48.1 | +| LG Electronics | 0.0 | 3.3 | 19.6 | 38.4 | 39.9 | 46.3 | +| Samsung-metal | 0.0 | 4.0 | 19.0 | 35.0 | 37.0 | 29.0 | +| Samsung-plastic | 0.0 | 4.0 | 22.0 | 41.0 | 44.0 | 44.0 | +| Sony, Ericsson | 1.5 | 7.6 | 24.9 | 47.1 | 47.1 | 38.1 | +| vivo-metal | 17.8 | 20.6 | 19.6 | 16.7 | 21.7 | 17.2 | +| vivo-plastic | 3.6 | 9.8 | 23.0 | 35.0 | 38.2 | 28.3 | +| OPPO | 14.2 | 13.4 | 20.5 | 36.3 | 46.1 | 39.4 | +| Huawei, HiSilicon | 7.8 | 18.4 | 34.4 | 45.2 | 42.5 | 22.6 | + +| OR combining | Panels in same faces | | | | | | +|-----------------------|----------------------|------|------|------|------|------| +| | 30 | 60 | 90 | 120 | 150 | 180 | +| Qualcomm Incorporated | | 20.6 | 37.5 | 31.4 | 17.3 | | +| LG Electronics | 18.8 | 13.0 | 21.5 | 6.6 | 0.0 | 0.0 | +| Samsung-metal | 23.0 | 23.0 | 9.0 | 1.0 | 0.0 | 0.0 | +| Samsung-plastic | 28.0 | 26.0 | 18.0 | 8.0 | 6.0 | 2.0 | +| Sony, Ericsson | 41.5 | 37.1 | 32.1 | 29.5 | 27.2 | 18.6 | +| vivo-metal | 23.5 | 17.0 | 17.8 | 20.1 | 19.3 | 10.0 | +| vivo-plastic | 32.6 | 27.1 | 25.2 | 20.6 | 16.1 | 10.7 | +| OPPO | 41.2 | 39.4 | 31.2 | 21.5 | 16.2 | 11.8 | +| Huawei, HiSilicon | 20.5 | 29.2 | 35.4 | 31.0 | 16.6 | 4.3 | + +Table A.8-2 Overall probability with arithmetic mean combining + +| Arithmetic mean | Panels in adjacent faces | | | | | | +|-----------------------|--------------------------|------|------|------|------|------| +| | 30 | 60 | 90 | 120 | 150 | 180 | +| Qualcomm Incorporated | | 12.8 | 17.1 | 17.8 | 15.9 | | +| Apple | 8.6 | 12.5 | 12.3 | 11.6 | 10.7 | 11.7 | +| LG Electronics | 4.1 | 8.1 | 12.5 | 12.3 | 14.1 | 14.3 | +| Samsung-metal | 4.0 | 9.0 | 11.0 | 7.0 | 4.0 | 1.0 | +| Samsung-plastic | 7.0 | 11.0 | 12.0 | 11.0 | 9.0 | 10.0 | +| Sony, Ericsson | 5.8 | 11.6 | 16.6 | 16.0 | 14.6 | 13.6 | +| vivo-metal | 7.0 | 9.5 | 9.8 | 9.3 | 9.3 | 8.8 | +| vivo-plastic | 6.1 | 11.3 | 11.9 | 10.3 | 8.9 | 7.7 | +| OPPO | 6.8 | 13.5 | 18.1 | 14.0 | 8.6 | 5.9 | +| Huawei, HiSilicon | 10.7 | 16.5 | 18.0 | 15.5 | 8.6 | 6.3 | +| Nokia | 12.0 | 31.0 | 35.0 | 35.0 | 30.0 | | + +| Arithmetic mean | Panels in opposite faces | | | | | | +|-----------------------|--------------------------|------|------|------|------|------| +| | 30 | 60 | 90 | 120 | 150 | 180 | +| Qualcomm Incorporated | | 3.5 | 11 | 23.9 | 37.6 | | +| Apple | 0.0 | 4.8 | 13.5 | 25.6 | 36.0 | 47.5 | +| LG Electronics | 0.0 | 1.7 | 9.8 | 19.2 | 20.0 | 23.0 | +| Samsung-metal | 0.0 | 2.0 | 10.0 | 17.0 | 23.0 | 29.0 | +| Samsung-plastic | 0.0 | 2.0 | 11.0 | 21.0 | 27.0 | 44.0 | +| Sony, Ericsson | 0.7 | 3.8 | 12.7 | 24.8 | 33.0 | 38.1 | +| vivo-metal | 10.7 | 12.4 | 10.9 | 9.5 | 12.9 | 17.2 | +| vivo-plastic | 1.9 | 5.0 | 12.0 | 18.6 | 24.3 | 28.3 | +| OPPO | 7.1 | 6.7 | 10.3 | 19.9 | 32.7 | 39.3 | +| Huawei, HiSilicon | 4.0 | 9.6 | 17.2 | 25.1 | 25.3 | 22.6 | +| Nokia | 7.0 | 20.0 | 33.0 | 41.0 | 47.0 | | + +| Arithmetic mean | Panels in same faces | | | | | | +|-----------------------|----------------------|------|------|------|------|------| +| | 30 | 60 | 90 | 120 | 150 | 180 | +| Qualcomm Incorporated | | 10.3 | 18.8 | 15.7 | 8.7 | | +| LG Electronics | 9.4 | 6.5 | 10.7 | 3.3 | 0.0 | 0.0 | +| Samsung-metal | 17.0 | 12.0 | 5.0 | 1.0 | 0.0 | 0.0 | +| Samsung-plastic | 20.0 | 15.0 | 9.0 | 4.0 | 3.0 | 2.0 | +| Sony, Ericsson | 26.9 | 21.6 | 17.6 | 16.0 | 17.6 | 18.6 | +| vivo-metal | 14.5 | 9.3 | 10.0 | 12.2 | 11.2 | 10.0 | +| vivo-plastic | 21.9 | 14.5 | 12.8 | 10.5 | 9.2 | 10.7 | +| OPPO | 28.9 | 23.0 | 16.3 | 10.8 | 9.3 | 11.6 | +| Huawei, HiSilicon | 12.4 | 15.8 | 17.8 | 15.5 | 8.3 | 4.3 | +| Nokia | 10.0 | 28.0 | 37.0 | 28.0 | 30.0 | | + +# Annex B: Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 08/2023 | RAN4#108 | R4-2311863 | | | TR skeleton for UE RF requirements for NR frequency range 2 multi-Rx chain DL reception | N/A | 0.0.1 | +| 08/2023 | RAN4#108 | R4-2314883 | | | R4-2311333 TP on DL power for TR 38.751
R4-2311334 TP on DL polarization combination for TR 38.751
R4-2314924 Text proposal to Multi-RX DL TR 38.751 on RMC and UE orientation
R4-2314667 TP to TR 38.751 on system assumption and UE RF requirement
R4-2314925 TP to TR 38.751 on inter-beam interference in multi-Rx DL reception | 0.0.1 | 0.1.0 | +| 09/2023 | RAN#101 | RP-231925 | | | For information | 0.1.0 | 1.0.0 | +| 10/2023 | RAN4#108bis | R4-2315086 | | | R4-2317592 TP to 38.751 on collection of simulation results | 1.0.0 | 1.1.0 | +| 11/2023 | RAN4#109 | R4-2318501 | | | R4-2321723 TP on NTC vs. ETC for TR 38.751
R4-2321724 TP on Annex :Simulation results for TR 38.751
R4-2321725 TP to 38.751 on further evaluation of gain difference between V-pol and H-pol
R4-2321726 TP to 38.751 on RF requirement construction | 1.1.0 | 1.2.0 | +| 12/2023 | RAN#102 | RP-233175 | | | For approval | 1.2.0 | 2.0.0 | +| 12/2023 | RAN#102 | RP-234019 | | | Approved with updated TR title | 2.0.0 | 2.0.1 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38786/02c999e5846341813b658e446e9a6fda_img.jpg b/marked/Rel-18/38_series/38786/02c999e5846341813b658e446e9a6fda_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54c21288af91351491cbc047054b8ebd40fc1fd3 --- /dev/null +++ b/marked/Rel-18/38_series/38786/02c999e5846341813b658e446e9a6fda_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1776e9f2758fdf587e0353390d3a70eddded12b80f3b2000c89839a2e664d5c6 +size 40566 diff --git a/marked/Rel-18/38_series/38786/0aa15f5c9c3edae230985491199cfe8b_img.jpg b/marked/Rel-18/38_series/38786/0aa15f5c9c3edae230985491199cfe8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb0a349bceabc71d1bee58980c81c9e6458dd2d --- /dev/null +++ b/marked/Rel-18/38_series/38786/0aa15f5c9c3edae230985491199cfe8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68494b1aa78718213f77a33900c14924d5ba917887de0a605ed9a2827ca2dbd4 +size 60203 diff --git a/marked/Rel-18/38_series/38786/123e1675d910a1beab564c5fec9548e2_img.jpg b/marked/Rel-18/38_series/38786/123e1675d910a1beab564c5fec9548e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2007559ae6e2dadd3cae8a8653d5debacac8bfd --- /dev/null +++ b/marked/Rel-18/38_series/38786/123e1675d910a1beab564c5fec9548e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d09ea0a6b785b20c386ef1002d35120cd7365ad50f0fe7a3548163d20811d68c +size 82975 diff --git a/marked/Rel-18/38_series/38786/17858cb897c937df4988696bb6686c44_img.jpg b/marked/Rel-18/38_series/38786/17858cb897c937df4988696bb6686c44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b4c13a13f0e3e6637c827641cfaa5081da3c999 --- /dev/null +++ b/marked/Rel-18/38_series/38786/17858cb897c937df4988696bb6686c44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09eb8a26677488e1e5e5b2c278c2662e3c3700bc67c84443d794baa38b3d01a1 +size 61856 diff --git a/marked/Rel-18/38_series/38786/198d076da025c516aec8122a6ab7db20_img.jpg b/marked/Rel-18/38_series/38786/198d076da025c516aec8122a6ab7db20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12cf110d78a8393e52507d025f7ebcc4961ede74 --- /dev/null +++ b/marked/Rel-18/38_series/38786/198d076da025c516aec8122a6ab7db20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e31f5274964e1dee77b4b0ef8870533f4861b84d1608edf6caa021aa4626327 +size 66835 diff --git a/marked/Rel-18/38_series/38786/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-18/38_series/38786/201de44da5d99899a8cf58eac2fa7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39175dd9cf5056958b251228fb207ef04d512ded --- /dev/null +++ b/marked/Rel-18/38_series/38786/201de44da5d99899a8cf58eac2fa7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3948c9a9da01cb3fd2d8f5eb3a89e465596a29e1963ad989aa7b61e7fc1bd555 +size 62633 diff --git a/marked/Rel-18/38_series/38786/3b1633ab47237ea4abb37cb4f715d183_img.jpg b/marked/Rel-18/38_series/38786/3b1633ab47237ea4abb37cb4f715d183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41b00296f000578db09671ec71b3c10d752944b5 --- /dev/null +++ b/marked/Rel-18/38_series/38786/3b1633ab47237ea4abb37cb4f715d183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c0fda7e99cc4e3810d9c1ee6aaf34f1807176118757e8c642c5eeaa5dcb2cf0 +size 31009 diff --git a/marked/Rel-18/38_series/38786/411bc48fd105531df2c427c06acd6aaa_img.jpg b/marked/Rel-18/38_series/38786/411bc48fd105531df2c427c06acd6aaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad60cfd02e2e0199bc61041a96ee01818936a882 --- /dev/null +++ b/marked/Rel-18/38_series/38786/411bc48fd105531df2c427c06acd6aaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f29dcf03b150bca0f7c1d8699c84e2340f78278f352f1dd71cfb53cf6301b0f7 +size 41031 diff --git a/marked/Rel-18/38_series/38786/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg b/marked/Rel-18/38_series/38786/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453c430c6fd11e8ce2a6891fd1933f4b943b5d14 --- /dev/null +++ b/marked/Rel-18/38_series/38786/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15ee849ef026825dd497cfa04d274a480be06a692551e2ae47c76469944625e9 +size 88410 diff --git a/marked/Rel-18/38_series/38786/449d2799e97657d8fa5897b2e74a88bd_img.jpg b/marked/Rel-18/38_series/38786/449d2799e97657d8fa5897b2e74a88bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..050cccabbbfb574737067ad192b01f3124d51dee --- /dev/null +++ b/marked/Rel-18/38_series/38786/449d2799e97657d8fa5897b2e74a88bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc92b04680b30503bf0a6824150b638bdb1df2fd62457498c8298ea070639484 +size 84269 diff --git a/marked/Rel-18/38_series/38786/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg b/marked/Rel-18/38_series/38786/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e14ab6fdfbcdea1570e012d18144de4146c80139 --- /dev/null +++ b/marked/Rel-18/38_series/38786/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b49572000582c4d07e762ed16c45a488700a7748d7f4afe06df44a219a124409 +size 66281 diff --git a/marked/Rel-18/38_series/38786/4895f9f74a63a7069cb8236fda8ff984_img.jpg b/marked/Rel-18/38_series/38786/4895f9f74a63a7069cb8236fda8ff984_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c2e7f97c27199b0afb71bf2793b67486327659 --- /dev/null +++ b/marked/Rel-18/38_series/38786/4895f9f74a63a7069cb8236fda8ff984_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ebcfbf04acff23a89782cfda8c2940e864ac473170e63cbcfb7a250b2a2a7c +size 86300 diff --git a/marked/Rel-18/38_series/38786/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38786/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d1b04506f396d8ec194dad62506625c2a100312 --- /dev/null +++ b/marked/Rel-18/38_series/38786/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec1128a8a92b1b5e4aec7885988588d7f46a7de83b950366dfc4c9337b6d9354 +size 9391 diff --git a/marked/Rel-18/38_series/38786/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38786/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ce88982e7dd937afce6da464b5e172b906ed782 --- /dev/null +++ b/marked/Rel-18/38_series/38786/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9a68bb85970ee997749f33b7ab385185c895fae82415191227b217c1c358457 +size 5727 diff --git a/marked/Rel-18/38_series/38786/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-18/38_series/38786/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1c2b626ad2c6ebd18e1bf578fee42e9df16e14b --- /dev/null +++ b/marked/Rel-18/38_series/38786/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba400a5f44170510da534f405a5fd0fee17b60ae07ca29c4c8e9e89e729912f6 +size 115992 diff --git a/marked/Rel-18/38_series/38786/730b6615db6d402580db1024a7f4e163_img.jpg b/marked/Rel-18/38_series/38786/730b6615db6d402580db1024a7f4e163_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e25800313f4682daa0d0efa2fe2509a8159a9293 --- /dev/null +++ b/marked/Rel-18/38_series/38786/730b6615db6d402580db1024a7f4e163_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e53336989491bfbfa00230f1118b05db4ba488d1485f5a7adae18cf947575f8a +size 125966 diff --git a/marked/Rel-18/38_series/38786/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-18/38_series/38786/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecda2dff418eee185f649e3510de1a6694b4547a --- /dev/null +++ b/marked/Rel-18/38_series/38786/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f13eb52decf31e094967c76d752513294fbec5332134755429d0f78243f82b6 +size 59172 diff --git a/marked/Rel-18/38_series/38786/7f16ae750ce9a533b0bd301dd986355e_img.jpg b/marked/Rel-18/38_series/38786/7f16ae750ce9a533b0bd301dd986355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea2062a67eddfeabd8601d45a03d3c1ef93bad15 --- /dev/null +++ b/marked/Rel-18/38_series/38786/7f16ae750ce9a533b0bd301dd986355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17bddac4fc1a503b01a94347ef182c81feb6bd6065581f467cab54dc9c432922 +size 33127 diff --git a/marked/Rel-18/38_series/38786/7f228001c8c028ac077fb5def89326e8_img.jpg b/marked/Rel-18/38_series/38786/7f228001c8c028ac077fb5def89326e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f61391f495423b5b092b1a7df368a8d7107644f --- /dev/null +++ b/marked/Rel-18/38_series/38786/7f228001c8c028ac077fb5def89326e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:230cd21f1ec99329343512ecd87ffa2d4658f53d17d5eea311db3f223afc62db +size 42131 diff --git a/marked/Rel-18/38_series/38786/808fbf3058e19e39757a0a84c7796059_img.jpg b/marked/Rel-18/38_series/38786/808fbf3058e19e39757a0a84c7796059_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dabd79eff35eabc80ab3bd9a7646dc4ef6509432 --- /dev/null +++ b/marked/Rel-18/38_series/38786/808fbf3058e19e39757a0a84c7796059_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe407d65f328d4b602b259724e39010190da5c8b0068ae42b89d5fb17a5f3f98 +size 96919 diff --git a/marked/Rel-18/38_series/38786/84b564808c370adacae8a814707fb071_img.jpg b/marked/Rel-18/38_series/38786/84b564808c370adacae8a814707fb071_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdca1b67889cc59dfea405fbe006c213f078c6a2 --- /dev/null +++ b/marked/Rel-18/38_series/38786/84b564808c370adacae8a814707fb071_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6085a5b18f6dff180306b3e7a54c4ab0ade0533b1998ecbd9fc21dd64e339cfc +size 75008 diff --git a/marked/Rel-18/38_series/38786/8b8084b35a85fbded65b73409354c3eb_img.jpg b/marked/Rel-18/38_series/38786/8b8084b35a85fbded65b73409354c3eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e42f39c9bcf85ca129aae0c3d0f089726ae30d5 --- /dev/null +++ b/marked/Rel-18/38_series/38786/8b8084b35a85fbded65b73409354c3eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b132661b292487c71e61d1bbc0326cc3ed8f3b4cf57524ad46522aa3da5c0a57 +size 78828 diff --git a/marked/Rel-18/38_series/38786/8e6c3e68ec4b938b0f85a21c61d226df_img.jpg b/marked/Rel-18/38_series/38786/8e6c3e68ec4b938b0f85a21c61d226df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adb37ddab7de2cf8a8eb3420bacceaa13e950575 --- /dev/null +++ b/marked/Rel-18/38_series/38786/8e6c3e68ec4b938b0f85a21c61d226df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aa402a553bb3c00dd33cb1c187ebef45aa1876deecb13c6c2329f692783089d +size 69969 diff --git a/marked/Rel-18/38_series/38786/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg b/marked/Rel-18/38_series/38786/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d51f2e3bee461935a39595d0b7f7c8785451006 --- /dev/null +++ b/marked/Rel-18/38_series/38786/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781556ca1fd9bd03ecf4ff386bb98160ea3f123899516d47cce6dae3cb06922e +size 72805 diff --git a/marked/Rel-18/38_series/38786/953203b3208524d293d4a65c0569324c_img.jpg b/marked/Rel-18/38_series/38786/953203b3208524d293d4a65c0569324c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b7570f64804ffa1dc7a7ba76e0c7206dbca4153 --- /dev/null +++ b/marked/Rel-18/38_series/38786/953203b3208524d293d4a65c0569324c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc819105d0b717087190b9d5c069fe306d911ec3ae607b04dd4e4f25babe6012 +size 28718 diff --git a/marked/Rel-18/38_series/38786/95eeda47ebbb12822a07b8791a9a34fa_img.jpg b/marked/Rel-18/38_series/38786/95eeda47ebbb12822a07b8791a9a34fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b3dd6430ff9d511ce5acf789c30205d5ed24a27 --- /dev/null +++ b/marked/Rel-18/38_series/38786/95eeda47ebbb12822a07b8791a9a34fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ff1366c63b0dace1cd3432451172005d169a6349697c5625ebeed60ee57a719 +size 6291 diff --git a/marked/Rel-18/38_series/38786/9e4179ffe4701bec67534299c4935049_img.jpg b/marked/Rel-18/38_series/38786/9e4179ffe4701bec67534299c4935049_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c5d39d6cadd375a525f7740388a788783887c66 --- /dev/null +++ b/marked/Rel-18/38_series/38786/9e4179ffe4701bec67534299c4935049_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71beae1d58fa261a663add2841cd3e24aa43ee8c740d526b83e8fcd50034bfc4 +size 67229 diff --git a/marked/Rel-18/38_series/38786/a2b0b8d868ec4ee43d7d3f0961a12b5e_img.jpg b/marked/Rel-18/38_series/38786/a2b0b8d868ec4ee43d7d3f0961a12b5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4890f01599cb4479373712bc5d37a0123b128ab --- /dev/null +++ b/marked/Rel-18/38_series/38786/a2b0b8d868ec4ee43d7d3f0961a12b5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fcf9d57117e23d28cf41ea9f57d2815e5c8c76057bee71a9a1e6fb513bd3047 +size 40239 diff --git a/marked/Rel-18/38_series/38786/a52ceaa1a0038c4e12cf866ad1ddd6bb_img.jpg b/marked/Rel-18/38_series/38786/a52ceaa1a0038c4e12cf866ad1ddd6bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..164b86011cd9b42d4be32cf49acc0d271b0f86ff --- /dev/null +++ b/marked/Rel-18/38_series/38786/a52ceaa1a0038c4e12cf866ad1ddd6bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa059bb16096072dd9bc45a0b4ea91dc347cadd137b728aa3a836f8d78e68114 +size 38563 diff --git a/marked/Rel-18/38_series/38786/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-18/38_series/38786/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9018d82f39041a9c7c445b0694328402bfa1aeb --- /dev/null +++ b/marked/Rel-18/38_series/38786/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4de26040de3f33aa5381752f20d60af5bbc3bd51e0887728db886c63d9348781 +size 64759 diff --git a/marked/Rel-18/38_series/38786/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg b/marked/Rel-18/38_series/38786/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27c8241fbf62ba656f2a0402f974afd20b5f6f02 --- /dev/null +++ b/marked/Rel-18/38_series/38786/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b5e000d5abc8c99aac9011a5a05c0320f75550a38c0fd757f9860bb3229ab66 +size 76017 diff --git a/marked/Rel-18/38_series/38786/ad406eca7668ea7128dba19ec32a22ac_img.jpg b/marked/Rel-18/38_series/38786/ad406eca7668ea7128dba19ec32a22ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c62a0f9058dc578afc8251edd87e61844881f2e --- /dev/null +++ b/marked/Rel-18/38_series/38786/ad406eca7668ea7128dba19ec32a22ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53ed99b14b988d9096a4a58db1d7639c49ce293b102ed538bb1b023af0662334 +size 65668 diff --git a/marked/Rel-18/38_series/38786/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg b/marked/Rel-18/38_series/38786/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c48eea0e801943c28f965d8c82690f47c34dad8d --- /dev/null +++ b/marked/Rel-18/38_series/38786/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9279a903f1b5cbd9cfb809214e85efe05bbf2a2cb319bc9d291f27dd0c772594 +size 121511 diff --git a/marked/Rel-18/38_series/38786/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg b/marked/Rel-18/38_series/38786/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..192bb1e7f2d02d141d794c4b39a1375649349330 --- /dev/null +++ b/marked/Rel-18/38_series/38786/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f0f7170710f7cb33a82ae26baa779aeb8d97ed3b9ae58a987037baa5be2cece +size 65206 diff --git a/marked/Rel-18/38_series/38786/be2d9105109f6a87907ab68cb88548d9_img.jpg b/marked/Rel-18/38_series/38786/be2d9105109f6a87907ab68cb88548d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa2e669dbcb60c1f360994241690f0c0b4731ea6 --- /dev/null +++ b/marked/Rel-18/38_series/38786/be2d9105109f6a87907ab68cb88548d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f11dee2017aed4f51fda6bc84e9af7d5664cd67e26bbd9eef7ff776c1c121510 +size 74187 diff --git a/marked/Rel-18/38_series/38786/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-18/38_series/38786/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8113a854b37b127052afbd3123c1fd374cd4f715 --- /dev/null +++ b/marked/Rel-18/38_series/38786/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b40b548c8686f5238aff90bcf8b915bbacaee3477ffa35799f21324e3cb90251 +size 70218 diff --git a/marked/Rel-18/38_series/38786/c2813655160a6d83a32289b367a84d1b_img.jpg b/marked/Rel-18/38_series/38786/c2813655160a6d83a32289b367a84d1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5494d3a288b0318d3caccc3dc2e50874ed57dc0a --- /dev/null +++ b/marked/Rel-18/38_series/38786/c2813655160a6d83a32289b367a84d1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52f988b9aa0deee53830f7ce8a96f1cc18231d48e2c470c0f18070d87fa89580 +size 40151 diff --git a/marked/Rel-18/38_series/38786/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg b/marked/Rel-18/38_series/38786/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9c8d9c840a905af513f669b46423a6c9e6f3b27 --- /dev/null +++ b/marked/Rel-18/38_series/38786/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:199fee69cfd5b8fef556303634dceb3e95658c135bf450bd5b352bc676c0f384 +size 97863 diff --git a/marked/Rel-18/38_series/38786/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-18/38_series/38786/c53adc66eab40abd5f8b9107d950ad04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da40abf99a5dbeccf0034a855fba161d3c976729 --- /dev/null +++ b/marked/Rel-18/38_series/38786/c53adc66eab40abd5f8b9107d950ad04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3562259eeb3cb1f10a8aad116c520fcb281ccd803a37c5826c345d604220788 +size 71891 diff --git a/marked/Rel-18/38_series/38786/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38786/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a619a922b8297d617e9ae2ac8337af6c26d1442e --- /dev/null +++ b/marked/Rel-18/38_series/38786/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a85ddd4f8633d9aba9b4fb2bd55f8afe634df264b5afd98a347665e7e719624b +size 62737 diff --git a/marked/Rel-18/38_series/38786/c742b64169a38a7f3f990172019878c8_img.jpg b/marked/Rel-18/38_series/38786/c742b64169a38a7f3f990172019878c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6cb92bff28932d8f008a03ace7fd7621c77d811 --- /dev/null +++ b/marked/Rel-18/38_series/38786/c742b64169a38a7f3f990172019878c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cb75aa7da3c861faa7f1f390ff43549cc05adb236d6b423b5f56217b5fe7887 +size 83428 diff --git a/marked/Rel-18/38_series/38786/d461c6341beba90844ef785469cd757f_img.jpg b/marked/Rel-18/38_series/38786/d461c6341beba90844ef785469cd757f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bacae3da57d7e78a82a13102498d6bffcbfc7a81 --- /dev/null +++ b/marked/Rel-18/38_series/38786/d461c6341beba90844ef785469cd757f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d0fedcd8f26336da1358c798a217078645af97ddcb40da9cf56a8d84cff87d4 +size 69895 diff --git a/marked/Rel-18/38_series/38786/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/marked/Rel-18/38_series/38786/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..364d27d4f550684d3f92dccbae953ddae0748c5e --- /dev/null +++ b/marked/Rel-18/38_series/38786/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0b1bb11fea2730d7356fe1c07504e78e54ed95eb0e04d70ca9146fa9609d9c8 +size 32999 diff --git a/marked/Rel-18/38_series/38786/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-18/38_series/38786/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1915555b14addc795c6bb9fef7165cb14145c7c2 --- /dev/null +++ b/marked/Rel-18/38_series/38786/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bca5a01e5804cdd44e779c1b627a5d6d1d532194dc06953ce2bb20c8c60a70c +size 63543 diff --git a/marked/Rel-18/38_series/38786/eec47775133f5c3b02d42ab8f85599ce_img.jpg b/marked/Rel-18/38_series/38786/eec47775133f5c3b02d42ab8f85599ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eefe6658e85fd289712ed0c6b740b0029a0d67be --- /dev/null +++ b/marked/Rel-18/38_series/38786/eec47775133f5c3b02d42ab8f85599ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0a80bb498cf11160098ccb73d152183ffcea128368543bf5111ac3e273d1d18 +size 121973 diff --git a/marked/Rel-18/38_series/38786/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg b/marked/Rel-18/38_series/38786/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f241fd387b901b559cd3f7dba69752634f856a10 --- /dev/null +++ b/marked/Rel-18/38_series/38786/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:777c37da87c87af11d7ab2c20a1aa126f8632281b163b9758471a69e299a629d +size 203467 diff --git a/marked/Rel-18/38_series/38786/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-18/38_series/38786/f455955c4bc84005728b4138f19098dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5b3a8c8af3ee0f9dad8be5be43ce5830698a1a6 --- /dev/null +++ b/marked/Rel-18/38_series/38786/f455955c4bc84005728b4138f19098dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4544ca1114be0652b13c0f6721cfe213dff4a6dbf22226a51091ff6b4981046 +size 119210 diff --git a/marked/Rel-18/38_series/38786/f78e0a777a9c5dc76cda197cbee0f206_img.jpg b/marked/Rel-18/38_series/38786/f78e0a777a9c5dc76cda197cbee0f206_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..493ceb792c9e9575dc12d09d7f4b34cb901d6d34 --- /dev/null +++ b/marked/Rel-18/38_series/38786/f78e0a777a9c5dc76cda197cbee0f206_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43ce5817ddd8ddc0ceff6b4b8a2bfde23341f4b1ccc8a966b61c3c9f4309026e +size 84173 diff --git a/marked/Rel-18/38_series/38786/fa8c6c258373e37982dca686af4c0101_img.jpg b/marked/Rel-18/38_series/38786/fa8c6c258373e37982dca686af4c0101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cf6e51952f62a42b0faea27548e473012e6093d --- /dev/null +++ b/marked/Rel-18/38_series/38786/fa8c6c258373e37982dca686af4c0101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40f12c2f21dfd910fd622255a9f4d0a91a9bb0fec21cc8b3e21c447a05601100 +size 88849 diff --git a/marked/Rel-18/38_series/38786/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/38_series/38786/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ec53818869ede63b755985e023c0d8ce82d3d34 --- /dev/null +++ b/marked/Rel-18/38_series/38786/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a84cdb75958c279871e4fd1af50f08c880f4080372641b28cf24dd0b69396982 +size 74644 diff --git a/marked/Rel-18/38_series/38786/raw.md b/marked/Rel-18/38_series/38786/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e214b5702a2463e4a47a62721bc93f90b0b2c7a9 --- /dev/null +++ b/marked/Rel-18/38_series/38786/raw.md @@ -0,0 +1,5724 @@ + + +# 3GPP TR 38.786 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR Sidelink evolution; User Equipment (UE) radio transmission and reception; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations..... | 10 | +| 4 Background..... | 11 | +| 5 Operating bands and channel arrangement for SL evolution..... | 11 | +| 5.1 Operating bands..... | 11 | +| 5.1.1 Operating bands for single carrier operation in unlicensed band..... | 11 | +| 5.1.2 Operating band combinations for inter-band concurrent operation..... | 12 | +| 5.1.3 Operating band combinations for NR SL CA operation..... | 12 | +| 5.2 Channel bandwidth..... | 12 | +| 5.2.1 Channel bandwidth for single carrier operation in unlicensed band..... | 12 | +| 5.2.2 Channel bandwidth for inter-band concurrent operation..... | 13 | +| 5.2.3 Channel bandwidth for NR SL CA operation..... | 13 | +| 5.3 Channel arrangement..... | 13 | +| 5.3.1 Channel spacing..... | 13 | +| 5.3.2 Channel raster..... | 14 | +| 5.3.3 Synchronization raster..... | 14 | +| 6 Transmitter characteristics for NR SL evolution..... | 14 | +| 6.1 Tx requirements for NR SL single carrier operation in unlicensed band..... | 14 | +| 6.1.1 Maximum output power for NR SL-U..... | 14 | +| 6.1.2 UE maximum output power reduction for NR SL-U..... | 15 | +| 6.1.2.1 MPR for SL-U operation in single CC..... | 18 | +| 6.1.2.1.1 MPR for simultaneous PSSCH/PSCCH transmission..... | 18 | +| 6.1.2.1.2 MPR for S-SSB transmission..... | 30 | +| 6.1.2.1.3 MPR for PSFCH transmission..... | 37 | +| 6.1.3 UE additional maximum output power reduction for NR SL-U..... | 43 | +| 6.1.3.1 A-MPR for SL-U with NS_28..... | 44 | +| 6.1.3.1.1 A-MPR for simultaneous PSSCH/PSCCH transmission..... | 44 | +| 6.1.3.1.2 A-MPR for S-SSB transmission..... | 44 | +| 6.1.3.1.3 A-MPR for PSFCH transmission..... | 44 | +| 6.1.3.2 A-MPR for SL-U with NS_29..... | 44 | +| 6.1.3.2.1 A-MPR for simultaneous PSSCH/PSCCH transmission..... | 44 | +| 6.1.3.2.2 A-MPR for S-SSB transmission..... | 44 | +| 6.1.3.2.3 A-MPR for PSFCH transmission..... | 44 | +| 6.1.3.3 A-MPR for SL-U with NS_30..... | 44 | +| 6.1.3.3.1 A-MPR for simultaneous PSSCH/PSCCH transmission..... | 44 | +| 6.1.3.3.2 A-MPR for S-SSB transmission..... | 45 | +| 6.1.3.3.3 A-MPR for PSFCH transmission..... | 45 | +| 6.1.3.4 A-MPR for SL-U with NS_31..... | 45 | +| 6.1.3.4.1 A-MPR for simultaneous PSSCH/PSCCH transmission..... | 45 | +| 6.1.3.4.2 A-MPR for S-SSB transmission..... | 51 | +| 6.1.3.4.3 A-MPR for PSFCH transmission..... | 55 | +| 6.1.3.5 A-MPR for SL-U with NS_53..... | 57 | +| 6.1.3.5.1 A-MPR for simultaneous PSSCH/PSCCH transmission..... | 57 | +| 6.1.3.5.1.3 Qualcomm's simulation results (R4-2316791)..... | 62 | +| 6.1.3.5.2 A-MPR for S-SSB transmission..... | 62 | +| 6.1.3.5.3 A-MPR for PSFCH transmission..... | 65 | +| 6.1.3.6 A-MPR for SL-U with NS_54..... | 67 | +| 6.1.3.6.1 A-MPR for simultaneous PSSCH/PSCCH transmission..... | 67 | +| 6.1.3.6.2 A-MPR for S-SSB transmission..... | 67 | +| 6.1.3.6.3 A-MPR for PSFCH transmission..... | 67 | + +| | | | +|-------------|----------------------------------------------------------------------------------------|-----| +| 6.1.3.7 | A-MPR for SL-U with NS_58..... | 67 | +| 6.1.3.7.1 | A-MPR for simultaneous PSSCH/PSCCH transmission..... | 67 | +| 6.1.3.7.2 | A-MPR for S-SSB transmission..... | 72 | +| 6.1.3.7.3 | A-MPR for PSFCH transmission..... | 76 | +| 6.1.3.7.3.1 | LG Electronics' simulation results (R4-2315542 and R4-2321771)..... | 76 | +| 6.1.3.8 | A-MPR for SL-U with NS_59..... | 78 | +| 6.1.3.8.1 | A-MPR for simultaneous PSSCH/PSCCH transmission..... | 78 | +| 6.1.3.8.2 | A-MPR for S-SSB transmission..... | 78 | +| 6.1.3.8.3 | A-MPR for PSFCH transmission..... | 78 | +| 6.1.3.9 | A-MPR for SL-U with NS_60..... | 78 | +| 6.1.3.9.1 | A-MPR for simultaneous PSSCH/PSCCH transmission..... | 78 | +| 6.1.3.9.2 | A-MPR for S-SSB transmission..... | 83 | +| 6.1.3.9.3 | A-MPR for PSFCH transmission..... | 86 | +| 6.1.3.10 | A-MPR for SL-U with NS_61..... | 88 | +| 6.1.3.10.1 | A-MPR for simultaneous PSSCH/PSCCH transmission..... | 88 | +| 6.1.3.10.2 | A-MPR for S-SSB transmission..... | 93 | +| 6.1.3.10.3 | A-MPR for PSFCH transmission..... | 97 | +| 6.1.4 | Configured transmitted power for NR SL-U..... | 99 | +| 6.1.5 | Minimum output power for NR SL-U..... | 99 | +| 6.1.6 | Transmit OFF power for NR SL-U..... | 99 | +| 6.1.7 | ON/OFF time mask for NR SL-U..... | 99 | +| 6.1.8 | Power control for NR SL-U..... | 100 | +| 6.1.9 | Transmit signal quality for NR SL-U..... | 100 | +| 6.1.9.1 | Frequency Error..... | 100 | +| 6.1.9.2 | EVM..... | 100 | +| 6.1.9.3 | Carrier Leakage..... | 101 | +| 6.1.9.4 | Equalizer spectrum flatness..... | 101 | +| 6.1.9.5 | In-band Emission..... | 101 | +| 6.1.10 | Spectrum emission mask for NR SL-U..... | 101 | +| 6.1.10.1 | Occupied Bandwidth..... | 101 | +| 6.1.10.2 | SEM..... | 101 | +| 6.1.10.3 | A-SEM..... | 101 | +| 6.1.11 | ACLR requirements for NR SL-U..... | 101 | +| 6.1.12 | Spurious emissions for NR SL-U..... | 101 | +| 6.1.13 | Spurious emission band UE co-existence for NR SL-U..... | 102 | +| 6.1.14 | Transmit intermodulation for NR SL-U..... | 102 | +| 6.2 | Tx requirements for inter-band con-current operation..... | 102 | +| 6.2.1 | Maximum output power for inter-band con-current operation..... | 102 | +| 6.2.2 | UE maximum output power reduction for inter-band con-current operation..... | 102 | +| 6.2.3 | UE additional maximum output power reduction for inter-band con-current operation..... | 102 | +| 6.2.4 | Configured transmitted power for inter-band con-current operation..... | 103 | +| 6.2.5 | Minimum output power for inter-band con-current operation..... | 103 | +| 6.2.6 | Transmit OFF power for inter-band con-current operation..... | 104 | +| 6.2.7 | ON/OFF time mask for inter-band con-current operation..... | 104 | +| 6.2.8 | Power control for inter-band con-current operation..... | 104 | +| 6.2.9 | Transmit signal quality for inter-band con-current operation..... | 104 | +| 6.2.10 | Spectrum emission mask for inter-band con-current operation..... | 104 | +| 6.2.11 | ACLR requirements for inter-band con-current operation..... | 104 | +| 6.2.12 | Spurious emissions for inter-band con-current operation..... | 104 | +| 6.2.13 | Spurious emission band UE co-existence for inter-band con-current operation..... | 104 | +| 6.2.14 | Transmit intermodulation for inter-band con-current operation..... | 105 | +| 6.3 | Tx requirements for NR SL CA operation..... | 105 | +| 6.3.1 | Maximum output power for NR SL CA operation..... | 105 | +| 6.3.2 | UE maximum output power reduction for NR SL CA operation..... | 105 | +| 6.3.2.1 | MPR for NR SL CA operation..... | 105 | +| 6.3.2.1.1 | MPR for simultaneous PSSCH/PSCCH transmission..... | 105 | +| 6.3.2.1.2 | MPR for PSFCH transmission..... | 116 | +| 6.3.2.1.3 | MPR for S-SSB transmission..... | 123 | +| 6.3.3 | UE additional maximum output power reduction for NR SL CA operation..... | 125 | +| 6.3.3.1 | A-MPR for NR SL CA operation..... | 126 | +| 6.3.3.1.1 | A-MPR for Intra-band contiguous SL CA operation..... | 126 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------|-----| +| 6.3.3.1.2 | LGE's A-MPR simulation results for SLCA_NS_52..... | 126 | +| 6.3.4 | Configured transmitted power for NR SL CA operation..... | 127 | +| 6.3.5 | Minimum output power for NR SL CA operation..... | 127 | +| 6.3.6 | Transmit OFF power for NR SL CA operation..... | 128 | +| 6.3.7 | ON/OFF time mask for NR SL CA operation..... | 128 | +| 6.3.8 | Power control for NR SL CA operation..... | 128 | +| 6.3.9 | Transmit signal quality for NR SL CA operation..... | 128 | +| 6.3.9.1 | Frequency Error..... | 128 | +| 6.3.9.2 | EVM..... | 128 | +| 6.3.9.3 | Carrier Leakage..... | 128 | +| 6.3.9.4 | In-band Emission..... | 129 | +| 6.3.10 | Spectrum emission mask for NR SL CA operation..... | 129 | +| 6.3.10.1 | Occupied Bandwidth..... | 129 | +| 6.3.10.2 | SEM..... | 129 | +| 6.3.10.3 | A-SEM..... | 129 | +| 6.3.11 | ACLR requirements for NR SL CA operation..... | 129 | +| 6.3.12 | Spurious emissions for NR SL CA operation..... | 129 | +| 6.3.13 | Spurious emission band UE co-existence for NR SL CA operation..... | 129 | +| 6.3.14 | Transmit intermodulation for NR SL CA operation..... | 130 | +| 7 | Receiver characteristics for NR SL evolution..... | 130 | +| 7.1 | Rx requirements for NR SL single carrier operation in unlicensed bands..... | 130 | +| 7.1.1 | Reference sensitivity power level for NR SL-U..... | 130 | +| 7.1.2 | Maximum input level for NR SL-U..... | 132 | +| 7.1.3 | Adjacent Channel Selectivity for NR SL-U..... | 132 | +| 7.1.4 | Blocking characteristics for NR SL-U..... | 133 | +| 7.1.4.1 | In Band Blocking..... | 133 | +| 7.1.4.2 | Out of Band Blocking..... | 133 | +| 7.1.4.3 | Narrow Band Blocking..... | 134 | +| 7.1.5 | Spurious response for NR SL-U..... | 134 | +| 7.1.6 | Intermodulation characteristics for NR SL-U..... | 134 | +| 7.2 | Rx requirements for inter-band con-current operation..... | 134 | +| 7.2.1 | Reference sensitivity power level for inter-band con-current operation..... | 134 | +| 7.2.2 | Maximum input level for inter-band con-current operation..... | 134 | +| 7.2.3 | Adjacent Channel Selectivity for inter-band con-current operation..... | 134 | +| 7.2.4 | Blocking characteristics for inter-band con-current operation..... | 135 | +| 7.2.5 | Spurious response for inter-band con-current operation..... | 135 | +| 7.2.6 | Intermodulation characteristics for inter-band con-current operation..... | 135 | +| 7.3 | Rx requirements for NR SL CA operation..... | 135 | +| 7.3.1 | Reference sensitivity power level for NR SL CA operation..... | 135 | +| 7.3.2 | Maximum input level for NR SL CA operation..... | 135 | +| 7.3.3 | Adjacent Channel Selectivity for NR SL CA operation..... | 135 | +| 7.3.4 | Blocking characteristics for NR SL CA operation..... | 136 | +| 7.3.4.1 | In-band blocking..... | 136 | +| 7.3.4.2 | Out-of-band blocking..... | 137 | +| 7.3.5 | Spurious response for NR SL CA operation..... | 137 | +| 7.3.6 | Intermodulation characteristics for NR SL CA operation..... | 138 | +| 8 | Co-channel coexistence between LTE Sidelink and NR Sidelink..... | 138 | +| 8.1 | Configured transmitted power for V2X UE supporting co-channel coexistence with LTE SL..... | 138 | +| 8.2 | Relative slot power tolerance for V2X UE supporting co-channel coexistence with LTE SL..... | 139 | + +| | | +|--------------------------------|------------| +| Annex A: Change history | 140 | +|--------------------------------|------------| + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document is a technical report for NR sidelink evolution services in Rel-18. The purpose is to specify radio solutions that are necessary for NR to support sidelink services working on unlicensed spectrums. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 30.007: "Guideline on WI/SI for new Operating Bands". +- [3] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Con-current operation:** *The simultaneous transmission and reception of sidelink and Uu interfaces, irrespective of TDM mode and FDM mode, while operation is agnostic of the service used on each interface.* + +**Inter-band con-current operation:** *Operation of NR Uu carrier and NR Sidelink carrier in different operating bands.* + +**NR SL CA operation:** *Aggregation of two or more NR Sidelink component carriers in order to support wider transmission bandwidths.* + +**Intra-band SL CA UE:** *UE that supports NR SL CA operation in a single band* + +**NR SL inter-band con-current operating Band:** *Band combinations of NR Uu carrier and NR Sidelink carrier in different operating bands.* + +**NR SL-U UE:** *UE that supports NR Sidelink operation in unlicensed bands (e.g. n46, n96, n102).* + +**PC5:** *The interface for sidelink transmission.* + +**PC3/PC5 UE:** *UE that supports Power class 3 or Power class 5* + +**UE transmission bandwidth configuration:** *Set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE.* + +**Wideband operation:** *For a UE that supports shared spectrum channel access, wideband operation refers to operation within a channel larger than 20 MHz in which intra-cell guard bands may be configured to distinguish individual RB-sets* + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\Delta F^{\text{Global}}$ | Granularity of the global frequency raster | +| $\Delta F^{\text{Raster}}$ | Band dependent channel raster granularity | +| $\Delta f_{\text{OOB}}$ | $\Delta$ Frequency of Out Of Band emission | +| $\Delta P^{\text{PowerClass}}$ | Adjustment to maximum output power for a given power class | +| $\Delta_{\text{RB}}$ | The starting frequency offset between the allocated RB and the measured non-allocated RB | +| $\Delta R_{\text{IB},c}$ | Allowed reference sensitivity relaxation due to support for inter-band CA operation, for serving cell $c$ | +| $\Delta_{\text{Shift}}$ | Channel raster offset | +| $\Delta T_{\text{C}}$ | Allowed operating band edge transmission power relaxation | +| $\Delta T_{\text{C},c}$ | Allowed operating band edge transmission power relaxation for serving cell $c$ | +| $\Delta L_{\text{CRB}}$ | Difference RB size between NR Uu RMC and NR SL RMC | +| $BW^{\text{Channel}}$ | Channel bandwidth | +| $BW^{\text{interferer}}$ | Bandwidth of the interferer | +| $BW^{\text{channel CA}}$ | The aggregated channel bandwidth of the wanted signal | +| $F_{\text{C}}$ | RF reference frequency on the channel raster | +| $F_{\text{DL\_low}}$ | The lowest frequency of the downlink operating band | +| $F_{\text{DL\_high}}$ | The highest frequency of the downlink operating band | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | +| $F_{\text{UL\_high}}$ | The highest frequency of the uplink operating band | +| $F_{\text{Interferer}}$ (offset) | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | +| $F_{\text{Interferer}}$ | Frequency of the interferer | +| $F_{\text{Ioffset}}$ | Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) | +| $F_{\text{offset}}$ | Frequency offset from $F_{\text{C\_high}}$ to the higher edge or $F_{\text{C\_low}}$ to the lower edge . | +| $F_{\text{OOB}}$ | The boundary between the NR out of band emission and spurious emission domains | +| $F_{\text{uw}}$ (offset) | The frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the interferer | +| $G_{\text{post connector}}$ | The supported post antenna connector gain | +| $L_{\text{CRB}}$ | Transmission bandwidth which represents the length of a contiguous resource block allocation expressed in units of resources blocks | +| Max() | The largest of given numbers | +| Min() | The smallest of given numbers | +| | Physical resource block number | +| $NR_{\text{ACL}}$ | NR ACLR | +| $NR\_SL_{\text{REFSENS}}$ | The REFSENS value defined for NR SL | +| $NR\_Uu_{\text{REFSENS}}$ | The REFSENS value defined for NR Uu | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks | +| $N_{\text{RB\_agg}}$ | The number of the aggregated RBs within the fully allocated aggregated channel bandwidth for carrier 1 to $j$ , where $\mu$ is defined in TS 38.211 | +| $N_{\text{RB},c}$ | The transmission bandwidth configuration of component carrier $c$ , expressed in units of resource blocks for carrier $j$ , where $\mu$ is defined in TS 38.211 | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{\text{REF-Offs}}$ | Offset used for calculating $N_{\text{REF}}$ | +| $NF_{\text{V2X}}$ | Noise figure for V2X | +| $P_{\text{CMAX}}$ | The configured maximum UE output power | +| $P_{\text{CMAX},c}$ | The configured maximum UE output power for serving cell $c$ | +| $P_{\text{CMAX},f,c}$ | The configured maximum UE output power for carrier $f$ of serving cell $c$ in each slot | +| $P_{\text{EMAX}}$ | Maximum allowed UE output power signalled by higher layers | +| $P_{\text{EMAX},c}$ | Maximum allowed UE output power signalled by higher layers for serving cell $c$ | +| $P_{\text{Interferer}}$ | Modulated mean power of the interferer | +| $P_{\text{largest BW}}$ | Power of the largest transmission bandwidth configuration of the component carriers in the bandwidth combination | +| $P^{\text{PowerClass}}$ | $P^{\text{PowerClass}}$ is the nominal UE power (i.e., no tolerance) | +| $P\text{-MPR}_c$ | Power Management Maximum Power Reduction for serving cell $c$ | +| $P_{\text{RB}}$ | The transmitted power per allocated RB, measured in dBm | +| $P_{\text{UMAX}}$ | The measured configured maximum UE output power | + +| | | +|--------------------|------------------------------------------------------------------------------------------------------------------------------| +| $P_{uw}$ | Power of an unwanted DL signal | +| $P_w$ | Power of a wanted DL signal | +| $P_{REFSENS\_V2X}$ | The REFSENS power for V2X | +| $P_{REFSENS\_SL}$ | The REFSENS power for Sidelink | +| $RB_{start}$ | Indicates the lowest RB index of transmitted resource blocks | +| $RB_{end}$ | Indicates the highest RB index of transmitted resource blocks | +| $RX\_BW$ | The bandwidth for receiving | +| $REFSENS_{V2X}$ | REFSENS value defined for V2X | +| $SNR_{V2X}$ | Signal-to-Noise Ratio for V2X | +| $T(P_{CMAX,f,c})$ | Tolerance for applicable values of $P_{CMAX,f,c}$ for configured maximum UE output power for carrier $f$ of serving cell $c$ | +| $SS_{REF}$ | SS block reference frequency position | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------------|---------------------------------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AGC | Automatic Gain Control | +| A-MPR | Additional Maximum Power Reduction | +| BLER | BLOCK Error Rate | +| BS | Base Station | +| CBW | Channel Bandwidth | +| CC | Component Carriers | +| CDF | Cumulative Distribution Function | +| CP-OFDM | Cyclic Prefix-OFDM | +| C-IMD | [Counter Intermodulation Distortion] | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DMRS | Demodulation Reference SignalEIRP Equivalent Isotropically Radiated Power | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| FDM | Frequency Division Multiplexing | +| FR1 | Frequency Range 1 | +| FR2 | Frequency Range 2 | +| HD | Half Duplex | +| IM | Implementation Margin | +| ITS | Intelligent Transportation SystemLTE Long Term Evolution | +| LBT | Listen before Talk | +| MPR | Maximum Power Reduction | +| NF | Noise Figure | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| OLPC | Open Loop Power Control | +| PC | Power Control | +| PRB | Physical Resource Block | +| ProSe | Proximity-based Services | +| PSBCH | Physical Sidelink Broadcast CHannel | +| PSCCH | Physical Sidelink Control CHannel | +| PSFCH | Physical Sidelink Feedback CHannel | +| PSSCH | Physical Sidelink Shared CHannelREFSENS Reference Sensitivity | +| RF | Radio Frequency | +| SCS | Sub-Carrier Spacing | +| SINR | Signal to Interference plus Noise Ratio | +| SL | Sidelink | +| SL-U | Sidelink at unlicensed band | +| SNR | Signal-to-Noise Ratio | +| S-SSB | Sidelink Synchronization Signal Block | + +| | | +|-----|----------------------------| +| SEM | Spectrum emission mask | +| TDD | Time Division Duplex | +| TDM | Time Division Multiplexing | +| UE | User Equipment | +| UL | Uplink | +| V2V | Vehicle to Vehicle | +| V2X | Vehicle to Everything | + +# 4 Background + +In Rel-16, sidelink communication was developed in RAN mainly to support advanced V2X applications. In Rel-17, SA2 studied and standardized Proximity based service including public safety and commercial related service. As part of Rel-17, power saving solutions (e.g., partial sensing, DRX) and inter-UE coordination have been developed in RAN1 and RAN2 to improve power consumption for battery limited terminals and reliability of sidelink transmissions. + +Although NR sidelink was initially developed for V2X applications, there is growing interest in the industry to expand the applicability of NR sidelink to commercial use cases. For commercial sidelink applications, two key requirements have been identified: + +- Increased sidelink data rate +- Support of new carrier frequencies for sidelink + +Increased sidelink data rate is motivated by applications such as sensor information (video) sharing between vehicles with high degree of driving automation. Commercial use cases could require data rates in excess of what is possible in Rel-17. Increased data rate can be achieved with the support of sidelink carrier aggregation and sidelink over unlicensed spectrum. Furthermore, by enhancing the FR2 sidelink operation, increased data rate can be more efficiently supported on FR2. While the support of new carrier frequencies and larger bandwidths would also allow to improve its data rate, the main benefit would come from making sidelink more applicable for a wider range of applications. More specifically, with the support of unlicensed spectrum and the enhancement in FR2, sidelink will be in a better position to be implemented in commercial devices since utilization of the ITS band is limited to ITS safety related applications. + +Another aspect to consider is the V2X deployment scenario where both LTE V2X and NR V2X devices are to coexist in the same frequency channel. For the two different types of devices to coexist while using a common carrier frequency, it is important that there is mechanism to efficiently utilize resource allocation by the two technologies without negatively impacting the operation of each technology. This requirement was also mentioned as part of the input from 5G Automotive Association to the Rel-18 RAN Workshop. + +# 5 Operating bands and channel arrangement for SL evolution + +## 5.1 Operating bands + +### 5.1.1 Operating bands for single carrier operation in unlicensed band + +NR Sidelink is designed to operate in the unlicensed operating bands in FR1 defined in Table 5.1.1-1. + +**Table 5.1.1-1. NR SL-U operating bands in FR1** + +| NR SL-U operating band | Sidelink (SL) Transmission operating band | Sidelink (SL) Reception operating band | Duplex Mode | Interface | +|------------------------|-------------------------------------------|----------------------------------------|-------------|-----------| +| | $F_{UL\_low} - F_{UL\_high}$ | $F_{DL\_low} - F_{DL\_high}$ | | | +| | | | | | + +| | | | | | +|--------|---------------------|---------------------|----|-----| +| n461 | 5150 MHz – 5925 MHz | 5150 MHz – 5925 MHz | HD | PC5 | +| n961,2 | 5925 MHz – 7125 MHz | 5925 MHz – 7125 MHz | HD | PC5 | +| n1021 | 5925 MHz – 6425 MHz | 5925 MHz – 6425 MHz | HD | PC5 | + +NOTE 1: Direct connection between client devices and between vehicular devices in the shared spectrum bands or portions of the shared spectrum bands is subject to country-specific conditions and can be prohibited per region-specific regulatory rules, e.g., in USA and Canada. + +During the NR SL-U development RAN4 identified at least following regional and country specific restrictions for direct connection between the devices within the targeted un-licensed bands (n46, n96 and n102). + +1. Client devices are prohibited from connecting directly to another client device in the frequency range 5850 – 5895 MHz and 5925 – 7125 MHz in USA, and in the frequency range 5925 – 7125 MHz in Canada per regulatory rules. Direct connection between client devices in the shared spectrum band is subject to region-specific regulatory rules. +2. For band n96 in USA, SL-U operation is excluded for vehicular UEs. + +### 5.1.2 Operating band combinations for inter-band con-current operation + +It has been agreed to use n78@licensed band + n46@unlicensed band as the example band combination for Uu@Licensed and SL@Un-licensed. + +The below inter-band con-current operation has been agreed not to be supported in Rel-18. + +- Uu@Un-licensed and SL@Un-licensed +- Uu@Un-licensed and SL@licensed +- Intra-band SL@Un-licensed + +NR SL operation is designed to operate concurrently with NR uplink/downlink on the operating band combinations listed in Table 5.1.2-1. + +**Table 5.1.2-1 Band combinations of inter-band con-current operating bands** + +| NR SL inter-band con-current operating Band | NR Band | Interface | +|---------------------------------------------|---------|-----------| +| SL_n78-n46 | n78 | Uu | +| | n46 | PC5 | + +### 5.1.3 Operating band combinations for NR SL CA operation + +NR SL CA operation is designed to operate in the operating bands in FR1 defined in Table 5.1.3-1. + +**Table 5.1.3-1: Intra-band contiguous CA operating bands for SL CA in FR1** + +| NR SL CA Band | NR Band | Interface | +|---------------|---------|-----------| +| SL_n47 | n47 | PC5 | + +## 5.2 Channel bandwidth + +### 5.2.1 Channel bandwidth for single carrier operation in unlicensed band + +Channel bandwidths defined for NR SL-U operating bands are in Table 5.2.1-1. + +**Table 5.2.1-1 NR SL-U channel bandwidth** + +| NR SL-U Operating Band | SCS kHz | SL-U band /channel bandwidth | | | | | | | | | | +|------------------------|---------|------------------------------|--------|--------|--------|--------|--------|--------|--------|------------------|--| +| | | 10 MHz | 20 MHz | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 90 MHz | 100 MHz | | +| n46 | 15 | | 20 | | 40 | | | | | | | +| | 30 | | 20 | | 40 | | 60 | 80 | | 100 1 | | +| | 60 | | 20 | | 40 | | 60 | 80 | | 100 1 | | +| n96 | 15 | | 20 | | 40 | | | | | | | +| | 30 | | 20 | | 40 | | 60 | 80 | | 100 1 | | +| | 60 | | 20 | | 40 | | 60 | 80 | | 100 1 | | +| n102 | 15 | | 20 | | 40 | | | | | | | +| | 30 | | 20 | | 40 | | 60 | 80 | | 100 1 | | +| | 60 | | 20 | | 40 | | 60 | 80 | | 100 1 | | + +NOTE 1: This UE channel bandwidth is optional in this release of the specification. + +Support for 10MHz channel bandwidth is not defined for NR SL-U single carrier operation in bands n46, n96 and n102. + +### 5.2.2 Channel bandwidth for inter-band con-current operation + +It has been agreed to apply each channel bandwidth that is supported in a band for Uu and a band for SL-U. + +For NR SL inter-band con-current operation in FR1, the NR channel bandwidths and SL channel bandwidths for each operating band are specified in Table 5.2.2-1. + +**Table 5.2.2-1: Inter-band con-current operation configurations** + +| NR SL inter-band con-current operating configuration | NR Band | Interface | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|------------------------------------------------------|---------|-----------|-------------------------------------------------|---------------------------| +| SL_n78A-n46A | n78 | Uu | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 0 | +| | n46 | PC5 | 20, 40, 60, 80, 100 2 | | + +NOTE 1: The SCS of each channel bandwidth for NR band refers to Table 5.3.5-1 in TS38.101-1. + +NOTE 2: This UE channel bandwidth is optional in this release of the specification. + +### 5.2.3 Channel bandwidth for NR SL CA operation + +For NR SL CA operation, the SL CA channel bandwidths for each operating band is specified in Table 5.2.3-1. + +**Table 5.2.3-1: Intra-band contiguous CA operating bands for SL CA in FR1** + +| Sidelink CA configuration / Bandwidth combination set | | | | | | | | +|-------------------------------------------------------|------------------------------------|-------------------------------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|------------------------------------|---------------------------| +| Sidelink CA configuration | Sidelink CA configuration n for TX | Component carriers in order of increasing carrier frequency | | | | Maximum aggregated bandwidth [MHz] | Bandwidth combination set | +| | | Channel bandwidths for carrier [MHz] | Channel bandwidths for carrier [MHz] | Channel bandwidths for carrier [MHz] | Channel bandwidths for carrier [MHz] | | | +| SL_n47B | SL_n47B | 10 | 10, 20,30 | | | 70 | 0 | +| | | 20 | 20,30 | | | | | +| | | 30 | 30,40 | | | | | + +## 5.3 Channel arrangement + +### 5.3.1 Channel spacing + +The general requirements in clause 5.4.1 of TS 38.101-1 are applied for NR SL-U. + +### 5.3.2 Channel raster + +The general requirements in clause 5.4.2 of TS 38.101-1 are applied for SL-U. + +NR-ARFCN and channel raster requirements in 5.4.2.1 of TS 38.101-1 are applied for NR SL-U with following exception: + +- 7.5kHz frequency raster shift, which can be used in NR V2X in band n47 is not defined for NR SL-U operation in bands n46, n96, n102. +- Channel raster entries for each operating band requirements in clause 5.4.2.3 of TS 38.101 are applied for NR SL-U with following exception: Channel raster points for 10MHz CBW in band n46 as defined in Table 5.4.2.3-2 are not applicable for NR SL-U. + +The mapping between the RF reference frequency on the channel raster and the corresponding resource element is given in Table 5.3.2-1 and can be used to identify the RF channel position. The mapping depends on the total number of RBs that are allocated in the channel and applies to both Tx and Rx for SL. The mapping must apply to at least one numerology supported by the UE. + +**Table 5.3.2-1: Channel raster to resource element mapping** + +| | $N_{RB} \bmod 2 = 0$ | $N_{RB} \bmod 2 = 1$ | +|--------------------------------|----------------------|----------------------| +| Resource element index | 0 | 6 | +| Physical resource block number | | | + +### 5.3.3 Synchronization raster + +There is no synchronization raster definition for NR sidelink unlicensed bands n46, n96, n102. + +# 6 Transmitter characteristics for NR SL evolution + +## 6.1 Tx requirements for NR SL single carrier operation in unlicensed band + +### 6.1.1 Maximum output power for NR SL-U + +The SL-U UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth in unlicensed bands. The period of measurement shall be at least one sub frame (1ms). + +**Table 6.1.1-1: SL-U UE Power Class** + +| NR band | Class 1 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | Class 5 (dBm) | Tolerance (dB) | +|---------|---------------|----------------|---------------|----------------|---------------|----------------|---------------|----------------| +| n46 | | | | | | | 20 | +2/-3 | +| n96 | | | | | | | 20 | +2/-3 | +| n102 | | | | | | | 20 | +2/-3 | + +NOTE 1: $P_{PowerClass}$ is the maximum UE power specified without taking into account the tolerance + +NOTE 2: Power class 5 is the default power class unless otherwise stated. + +The SL-U UE shall meet the following additional requirements for maximum mean transmission power density specified in Table 6.2F.1-2 in TS38.101-1 when NS is signalled and when transmission overlaps with any portion of the specified frequency range. In case transmission overlaps multiple frequency ranges, the lowest power density requirement applies. + +**Table 6.1.1-2: Additional requirements for transmit power density** + +| NR Band | NS value | Channel bandwidth (MHz) | Frequency range (MHz) | Maximum mean power density (dBm/MHz) | +|---------|----------|-------------------------|-----------------------|--------------------------------------| +| n46 | NS_31 | 20 | 5150 - 5230 | 10 | +| | | | 5250 - 5350 | | +| | | | 5470 - 5725 | | +| | | | 5725 - 5850 | | +| | | 40 | 5230 - 5250 | 4 | +| | | | 5150 - 5230 | | +| | | | 5250 - 5350 | | +| | | | 5470 - 5725 | | +| | | 60, 80 | 5725 - 5850 | 4 | +| | | | 5230 - 5250 | | +| n96 | NS_53 | 20, 40, 60, 80, 100 | 5925 - 7125 | -1 | +| | NS_60 | 20, 40, 60, 80, 100 | 5925 - 7125 | 2 | +| | NS_61 | 20, 40, 60, 80 | 5925 - 6425 | 1 | +| n102 | NS_58 | 20, 40, 60, 80, 100 | 5945 - 6425 | 10 | + +### 6.1.2 UE maximum output power reduction for NR SL-U + +The following assumption can serve as a starting point for MPR simulation assumptions that are considered to derive MPR requirements for SL-U operation. + +- Basic RF parameters for MPR of single carrier SL-U UE + - Waveforms: CP-OFDM for SL-U + - Supported CBW: 20/40/60/80/100MHz. + - Modulation: QPSK/16-QAM/64-QAM/256-QAM + - SCS: 15/30kHz + - C-IMD: 45dBc or 60dBc + - EVM and impairments + +| Modulation | SystemEVM | PA only | Image | | +|------------|-----------|---------|-------|--| +| QPSK | 17.5% | 10% | 34dB | | +| 16QAM | 12.5% | 8% | 34dB | | +| 64QAM | 8% | 4% | 34dB | | +| 256QAM | 3.5% | 1.8% | 34dB | | + +- IBE and impairment exceptions are same as NR-U +- Reuse IBE mask from TS38.101-1 Table 6.4F.2.3-1 +- Image/carrier exceptions position and specific test according to interlaces. +- ACLR: 27dBc for both PC3/PC5 UE with NR MBW +- SEM according to 38.101-1 clause 6.5F.2.2 as well as Table 6.1.2-4 +- PA calibration & PA configuration: + +- Power class 5 (single PA): 1dB MPR and DFT-s-OFDM QPSK 100RB3 20MHz waveform with 27dB ACLR +- MPR table format can be reused the MPR format of NR-U according to each transmitted channel e.g.PSSCH/PSCCH transmission, PSFCH transmission and PSBCH transmission if any issue is not seen.. +- The MPR will be applied to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. +- Follow the RB interlaced allocation based on Table 6.2F.2-1 and Table 6.2F.2-2 in TS38.101-1. Also refer the interlaced allocations with uplink resource allocation type 2 as specified in TS 38.214. FFS on the inter-laced RB allocation for PSFCH, and on the repeated RB allocation for S-SSB by RAN1 + +For SL-U in single CC operation, the simultaneous transmission of PSCCH and PSSCH in the same sub-frame is supported and the following constraints in Table 6.1.2-1 can be assumed. + +**Table 6.1.2-1: SL-U operation's MPR simulation assumptions** + +| Items | Assumption | +|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Allowed sub-channel sizes | Support {10, 12, 15, 20, 25, 50, 75, 100} PRBs for possible sub-channel size. | +| Allowed $L_{CRB}$ allocation | 10,12,15,20,24,25,30,36,40,45,48,50,60,70,72,75,80,84,90,96,100,105,108,110,120,125,130,132,135,140,144,150,156,160,165,168,170,175,180,190,192,195,200,204,210,216,220,225,228,230,240,250,252,255,260,264,270
The Allowed $L_{CRB}$ will be decided by the supported SCS. | +| Regarding PSCCH / PSSCH multiplexing |

For 3-symbol PSCCH

Image: Diagram showing a 14-symbol slot (SL symbol index 0 to 13). Symbols 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 are shown. Symbols 3, 4, 5 are highlighted in blue and labeled 'PSCCH'. Symbols 0, 1, 2 are orange. Symbols 6, 7, 8, 9, 10, 11, 12, 13 are green. Symbols 10, 11, 12 are also highlighted in blue and labeled 'PSCCH'.

| +| PSCCH size | 10RB*3 Symbols | +| PSD offset of X dB between PSCCH and PSSCH | 0dB | + +For simultaneous transmission of PSFCH transmission for SL-U operation, RAN4 assumed as follow + +**Table 6.1.2-2: SL-U UE's MPR simulation assumptions for PSFCH transmission** + +| Items | Assumption | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Modulation for PSSCH | QPSK | +| PSFCH | ZC sequence | +| Structure of Slot | Baseline is to follow RAN1 agreements | +| RB allocation |
  • - Power per RB is same in PSFCH for all users
  • - Total power is 20dBm
  • - Single RB-set and multiple RB-sets will be considered based on RAN1 decision.
    • For single RB-set, RAN4 consider interlacing RBs for PSFCH
    • For multiple RB-sets, RAN4 considers both contiguous RB sets and non-contiguous RB sets.
  • - N gap from RBstart to RBend of interlaced transmission should meet at least 80% of channel bandwidth in a single RB-set , Ngap = RBend – RBstart .
  • - For common interlaced RB allocation, P\_common \leq P\_dedicated
  • - RB allocation method as NR SL legacy RB allocation is also considered.
| + +For S-SSB transmission for SL-U operation, RAN4 assumed as follow + +**Table 6.1.2-3: SL-U UE's MPR simulation assumptions for S-SSB transmission** + +| Items | Assumption | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Modulation for PSBCH | QPSK | +| S-PSS | M-sequence | +| S-SSS | Golden-sequence | +| S-SSB structure | Diagram of S-SSB structure showing a sequence of blocks: PSBCH, S-PSS, S-PSS, S-SSS, S-SSS, followed by seven PSBCH blocks, and a GAP block. | +| RB allocation |
  • - Single RB-set and multiple RB-sets will be considered based on RAN1 decision. For single RB set, the 11RB will be repeated N time in a RB set. For the multiple RB-sets, RAN4 consider both contiguous RB sets and non-contiguous RB sets.
  • - N gap from RBstart to RBend of repeated S-SSB transmission should meet at least 80% of channel bandwidth. in a single RB-set ,N_{gap} = RB_{end} - RB_{start}.
| + +For MPR and A-MPR for SL-U wideband operation, RAN4 assumed in-carrier SEM as follows. + +In the case of non-transmitted 20 MHz channel(s) on the edges of an assigned channel bandwidth the spectrum emission mask for operation with shared spectrum channel access, specified in Table 6.5F.2.2.0-1, is applied by using the total bandwidth of the remaining transmitted channels. The spectrum emission mask for non-transmitted channels is floored at -28dBr inside the assigned channel bandwidth and continues at same level until the channel bandwidth mask is intercepted, i.e. until $\Delta f_{OOB}$ , as defined in 38.101-1 Clause 6.5F.2.2.0, equals $BW_{Channel} / 2$ . When $\Delta f_{OOB} > BW_{Channel} / 2$ requirements in clause 6.5F.2.2.0 apply. + +The In-Carrier SEM in gap between transmitted channels is defined in Table 6.1.2-4 and some examples are shown in Figure 6.1.2-1. + +The relative power of any UE emission shall not exceed the most stringent levels given by the spectrum emission mask for operation with shared spectrum channel access with full channel bandwidth and the spectrum emission mask for non-transmitted channels with the channel bandwidth of the transmitted channels in the case of non-transmitted channels at the edge of an assigned channel bandwidth or spectrum emission mask defined for gaps between the transmitted channels. + +An exception to the spectrum emission mask for non-transmitted channels allows a single 2 MHz bandwidth to extend to -28 dBc relative to total transmit power, or -20 dBm, whichever is the greatest. + +**Table 6.1.2-4: In-Carrier SEM in gap between transmitted channels for SL-U wideband operation** + +| | | | | 0 | 1 | 10 | 20 | 30 | MHz | +|-----|----------------------------------|----|----|---|-----|-----|-----|----|-----| +| | | | | 0 | -20 | -23 | | | dBr | +| 60 | 101 | 40 | 20 | 0 | -20 | -23 | | | dBr | +| 80 | 1101
1011 | 60 | 20 | 0 | -20 | -23 | | | dBr | +| | 1001 | 40 | 40 | 0 | -20 | -25 | -25 | | dBr | +| 100 | 10100
01010
00101 | 40 | 20 | 0 | -20 | -23 | | | dBr | +| | 10110
11010
01101
01011 | 60 | 20 | 0 | -20 | -23 | | | dBr | +| | 10111
11011 | 80 | 20 | 0 | -20 | -23 | | | dBr | + +| | | | | | | | | | | +|----------------|----|----------------------------|---|-----|-----|-----|-----|--|-----| +| 11001
10011 | 60 | 40
(adjacent from '11') | 0 | -20 | | | -25 | | dBr | +| | 60 | 40
(adjacent from '1') | 0 | -20 | -25 | | | | dBr | +| 10001 | 40 | 60 | 0 | -20 | -25 | -25 | -25 | | dBr | + +![Figure 6.1.2-1: In-Carrier SEM in gap between transmitted channels for SL-U wideband operation. The figure contains eight subplots showing Carrier SEM (solid line) and In-Carrier SEM (dashed line) for various carrier and bandwidth configurations. The subplots are arranged in a 4x2 grid. The left column shows scenarios with 80MHz and 100MHz carriers with varying total transmit bandwidths (40MHz, 60MHz, 80MHz). The right column shows scenarios with 80MHz and 100MHz carriers with 20MHz, 40MHz, and 60MHz in-carrier gaps. Each plot shows the power spectral density (dBr) versus frequency (Freq), with the carrier center frequency (fc) and bandwidth (BWChannel) indicated. The In-Carrier SEM is shown in the gaps between transmitted channels, with values of -20, -25, and -28 dBr indicated.](ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg) + +Figure 6.1.2-1: In-Carrier SEM in gap between transmitted channels for SL-U wideband operation. The figure contains eight subplots showing Carrier SEM (solid line) and In-Carrier SEM (dashed line) for various carrier and bandwidth configurations. The subplots are arranged in a 4x2 grid. The left column shows scenarios with 80MHz and 100MHz carriers with varying total transmit bandwidths (40MHz, 60MHz, 80MHz). The right column shows scenarios with 80MHz and 100MHz carriers with 20MHz, 40MHz, and 60MHz in-carrier gaps. Each plot shows the power spectral density (dBr) versus frequency (Freq), with the carrier center frequency (fc) and bandwidth (BWChannel) indicated. The In-Carrier SEM is shown in the gaps between transmitted channels, with values of -20, -25, and -28 dBr indicated. + +Figure 6.1.2-1: In-Carrier SEM in gap between transmitted channels for SL-U wideband operation + +#### 6.1.2.1 MPR for SL-U operation in single CC + +##### 6.1.2.1.1 MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.2.1.1.1 LG Electronics' simulation results (R4-2315542) + +The following simulation scenarios are considered as Table 6.1.2.1.1-1. + +Table 6.1.2.1.1.1-1: SL-U PSSCH/PSCCH MPR/A-MPR simulation scenarios + +| | Scenario | Waveform | BW | RB Setup | SCS | +|-------------------------------------|----------|----------|-----|-------------------|-----| +| Full Allocation | 1 | CP-OFDM | 20 | 105RB0 | 15 | +| | 2 | CP-OFDM | 20 | 50RB0 | 30 | +| | 3 | CP-OFDM | 40 | 216RB0 | 15 | +| | 4 | CP-OFDM | 60 | 160RB0 | 30 | +| | 5 | CP-OFDM | 80 | 216RB0 | 30 | +| | 6 | CP-OFDM | 100 | 270RB0 | 30 | +| Interlaced Allocation (Interlace_0) | 7 | CP-OFDM | 20 | 1 RB0 every 10RBs | 15 | +| | 8 | CP-OFDM | 20 | 1RB0 every 5RBs | 30 | +| | 9 | CP-OFDM | 40 | 1RB0 every 10RBs | 15 | +| | 10 | CP-OFDM | 60 | 1RB0 every 5RBs | 30 | +| | 11 | CP-OFDM | 80 | 1RB0 every 5RBs | 30 | +| | 12 | CP-OFDM | 100 | 1RB0 every 5RBs | 30 | +| Wide band Full operation | 13 | CP-OFDM | 40 | Bitmap 10 | 15 | +| | 14 | CP-OFDM | 60 | Bitmap 100 | 30 | +| | 15 | CP-OFDM | 60 | Bitmap 110 | 30 | +| | 16 | CP-OFDM | 60 | Bitmap 010 | 30 | +| | 17 | CP-OFDM | 80 | Bitmap 1000 | 30 | +| | 18 | CP-OFDM | 80 | Bitmap 1100 | 30 | +| | 19 | CP-OFDM | 80 | Bitmap 1110 | 30 | +| | 20 | CP-OFDM | 80 | Bitmap 0100 | 30 | +| | 21 | CP-OFDM | 80 | Bitmap 0110 | 30 | +| | 22 | CP-OFDM | 100 | Bitmap 10000 | 30 | +| | 23 | CP-OFDM | 100 | Bitmap 11000 | 30 | +| | 24 | CP-OFDM | 100 | Bitmap 11100 | 30 | +| | 25 | CP-OFDM | 100 | Bitmap 11110 | 30 | +| | 26 | CP-OFDM | 100 | Bitmap 01000 | 30 | +| | 27 | CP-OFDM | 100 | Bitmap 01100 | 30 | +| | 28 | CP-OFDM | 100 | Bitmap 01110 | 30 | +| | 29 | CP-OFDM | 100 | Bitmap 00100 | 30 | +| Wide band | 30 | CP-OFDM | 40 | Bitmap 10 | 15 | + +| | | | | | | +|------------------------------------|----|---------|-----|--------------|----| +| Interlaced Operation (Interlace_0) | 31 | CP-OFDM | 60 | Bitmap 100 | 30 | +| | 32 | CP-OFDM | 60 | Bitmap 110 | 30 | +| | 33 | CP-OFDM | 60 | Bitmap 010 | 30 | +| | 34 | CP-OFDM | 80 | Bitmap 1000 | 30 | +| | 35 | CP-OFDM | 80 | Bitmap 1100 | 30 | +| | 36 | CP-OFDM | 80 | Bitmap 1110 | 30 | +| | 37 | CP-OFDM | 80 | Bitmap 0100 | 30 | +| | 38 | CP-OFDM | 80 | Bitmap 0110 | 30 | +| | 39 | CP-OFDM | 100 | Bitmap 10000 | 30 | +| | 40 | CP-OFDM | 100 | Bitmap 11000 | 30 | +| | 41 | CP-OFDM | 100 | Bitmap 11100 | 30 | +| | 42 | CP-OFDM | 100 | Bitmap 11110 | 30 | +| | 43 | CP-OFDM | 100 | Bitmap 01000 | 30 | +| | 44 | CP-OFDM | 100 | Bitmap 01100 | 30 | +| | 45 | CP-OFDM | 100 | Bitmap 01110 | 30 | +| | 46 | CP-OFDM | 100 | Bitmap 00100 | 30 | + +Here, for RB set, ‘105RB0’ means that RB starts at RB index ‘0’ and transmitted RB size is 105 RB. And, Bitmap ‘1’ means the corresponding RB set is transmitted, and ‘0’ means the corresponding RB set is not transmitted for wide band operation. + +Table 6.1.2.1.1.1-2 shows the all possible bitmap of sub-band configuration for wide band operation. The wide band operation can be aggregated with multiple of 20MHz based sub-band. For the SL-U PSSCH/PSCCH MPR simulation, only contiguous RB set bitmaps are considered. + +**Table 6.1.2.1.1.1-2: All possible RB set Bitmap of sub-band configuration** + +| | Contiguous RB sets Bit map | Non-contiguous RB sets Bit map | +|--------|---------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| 20MHz | N/A | N/A | +| 40MHz | 11, 10, 01 | N/A | +| 60MHz | 111, 110, 011, 100, 001, 010 | 101 | +| 80MHz | 1111, 1110, 0111, 1100, 0011, 1000, 0001, 0110, 0100, 0010 | 1001, 1101, 1011, 1010, 0101 | +| 100MHz | 11111, 11110, 01111, 11100, 00111, 11000, 00011, 10000, 00001, 01110, 01100, 00110, 01000, 00010, 00100 | 10001, 11011, 11010, 01011, 11001, 10011, 10101, 10110, 01101, 10100, 00101, 10010, 01001, 01010, 11101, 10111 | + +Table 6.1.2.1.1.1-3 and Figure 6.1.2.1.1.1-1 show the MPR simulation results for the scenarios. + +Table 6.1.2.1.1.1-3: PSSCH/PSCCH MPR simulation results for SL-U power class 5 + +| | | | | | | | | | | | | | | | | | | | | | | +|---------|------------|------|------|------|------|------|------|------|------|------|------|------|------|-----|-----|-----|-----|-----|-----|--|--| +| '20MHz' | Scenario # | #1 | #7 | #2 | #8 | | | | | | | | | | | | | | | | | +| | 'QPSK' | 2.48 | 2.83 | 2.15 | 2.49 | | | | | | | | | | | | | | | | | +| | '16QAM' | 2.48 | 2.83 | 2.16 | 2.50 | | | | | | | | | | | | | | | | | +| | '64QAM' | 2.82 | 2.83 | 3.18 | 2.50 | | | | | | | | | | | | | | | | | +| | '256QAM' | 5.88 | 5.08 | 5.89 | 5.49 | | | | | | | | | | | | | | | | | +| '40MHz' | Scenario # | #3 | #9 | #13 | #30 | | | | | | | | | | | | | | | | | +| | 'QPSK' | 2.48 | 2.48 | 2.81 | 2.81 | | | | | | | | | | | | | | | | | +| | '16QAM' | 2.48 | 2.48 | 2.81 | 2.82 | | | | | | | | | | | | | | | | | +| | '64QAM' | 2.82 | 2.48 | 2.81 | 2.82 | | | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.47 | 5.07 | | | | | | | | | | | | | | | | | +| | Scenario # | #4 | #10 | #14 | #31 | #15 | #32 | #16 | #33 | | | | | | | | | | | | | +| '60MHz' | 'QPSK' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.47 | 2.13 | 0.00 | | | | | | | | | | | | | +| | '16QAM' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.47 | 2.13 | 0.36 | | | | | | | | | | | | | +| | '64QAM' | 3.17 | 2.48 | 3.17 | 2.47 | 3.16 | 2.47 | 3.16 | 2.45 | | | | | | | | | | | | | +| | '256QAM' | 5.88 | 5.07 | 5.47 | 5.07 | 5.88 | 5.07 | 5.88 | 5.46 | | | | | | | | | | | | | +| | Scenario # | #5 | #11 | #17 | #34 | #18 | #35 | #19 | #36 | #20 | #37 | #21 | #38 | | | | | | | | | +| '80MHz' | 'QPSK' | 2.48 | 2.48 | 2.14 | 2.15 | 2.47 | 2.47 | 2.47 | 2.47 | 2.46 | 0.00 | 2.13 | 0.00 | | | | | | | | | +| | '16QAM' | 2.48 | 2.48 | 2.14 | 2.15 | 2.47 | 2.47 | 2.47 | 2.47 | 2.46 | 0.10 | 2.13 | 0.63 | | | | | | | | | +| | '64QAM' | 2.82 | 2.48 | 3.17 | 2.15 | 2.81 | 2.48 | 3.16 | 2.48 | 3.15 | 2.12 | 3.16 | 2.46 | | | | | | | | | +| | '256QAM' | 5.47 | 5.06 | 5.47 | 5.07 | 5.47 | 5.07 | 5.88 | 5.07 | 5.46 | 5.05 | 5.88 | 5.06 | | | | | | | | | +| | Scenario # | #6 | #12 | #22 | #39 | #23 | #40 | #24 | #41 | #25 | #42 | #26 | #43 | #27 | #44 | #28 | #45 | #29 | #46 | | | + +| | | | | | | | | | | | | | | | | | | | | +|--|----------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| | 'QPSK' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.48 | 2.47 | 2.47 | 2.47 | 2.47 | 2.13 | 0.00 | 2.46 | 0.00 | 2.46 | 0.13 | 2.13 | 0.00 | +| | '16QAM' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.48 | 2.47 | 2.47 | 2.47 | 2.47 | 2.13 | 0.35 | 2.46 | 0.63 | 2.47 | 0.64 | 2.13 | 0.10 | +| | '64QAM' | 3.16 | 2.48 | 3.17 | 2.48 | 3.17 | 2.47 | 3.16 | 2.47 | 2.81 | 2.47 | 3.16 | 2.13 | 3.16 | 2.46 | 3.16 | 2.47 | 3.15 | 2.12 | +| | '256QAM' | 5.88 | 5.06 | 5.47 | 5.08 | 5.47 | 5.06 | 5.47 | 5.07 | 5.47 | 5.06 | 5.47 | 5.06 | 5.47 | 5.06 | 5.47 | 5.06 | 5.46 | 5.06 | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 7. The x-axis is 'Test Scenario #' ranging from 1 to 46. Data points are shown for four modulation schemes: QPSK (red circles), 16QAM (blue asterisks), 64QAM (magenta diamonds), and 256QAM (grey triangles). 256QAM points are clustered between 5 and 6 dB. 64QAM points are mostly between 2.5 and 3.5 dB. QPSK points are mostly around 2.5 dB, with some drops to 0.5 dB at scenarios 33, 37, 38, 43, 44, 45. 16QAM points are mostly around 2.5 dB, with some drops to 0.5 dB at scenarios 33, 37, 38, 43, 44, 45, 46.](c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg) + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 7. The x-axis is 'Test Scenario #' ranging from 1 to 46. Data points are shown for four modulation schemes: QPSK (red circles), 16QAM (blue asterisks), 64QAM (magenta diamonds), and 256QAM (grey triangles). 256QAM points are clustered between 5 and 6 dB. 64QAM points are mostly between 2.5 and 3.5 dB. QPSK points are mostly around 2.5 dB, with some drops to 0.5 dB at scenarios 33, 37, 38, 43, 44, 45. 16QAM points are mostly around 2.5 dB, with some drops to 0.5 dB at scenarios 33, 37, 38, 43, 44, 45, 46. + +Figure 6.1.2.1.1.1-1: PSSCH/PSCCH MPR simulation results for SL-U power class 5 + +Considering the inner RB set bitmaps and the outer RB set bitmaps on top of the Full/Partial RB allocation, the PSSCH/PSCCH MPR for SL-U power class 5 can be proposed as Table 6.1.2.1.1.1-4 based on the simulation results. + +**Table 6.1.2.1.1.1-4 Maximum power reduction (MPR) for SL-U UE power class 5** + +| Pre-coding | Modulation | RB Allocation | | | | | +|------------|------------|-----------------------------------------|---------------------------|-----------------------------------------|---------------------------|---------------------------------------------| +| | | Outer RB set configuration 5 | | Inner RB set configuration 5 | | Exception for 100MHz Full 4 (dB) | +| | | Full 2 (dB) | Partial 3 (dB) | Full 2 (dB) | Partial 3 (dB) | | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 3.5 | ≤ 3.5 | ≤ 1.5 | ≤ 4.5 | +| | 16 QAM | ≤ 4.0 | ≤ 4.0 | ≤ 4.0 | ≤ 3.0 | ≤ 4.5 | +| | 64 QAM | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | | +| | 256 QAM | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. +NOTE 2: The MPR for Full RB allocation applies to all RB's in all transmitted 20 MHz or larger channels that are fully allocated or all RB's in all transmitted sub-bands for wideband operation that are fully allocated excluding the wideband configurations of Table 6.2F.2-2. +NOTE 3: The MPR for Partial RB allocation applies to interlaced allocations with uplink resource allocation type 2 as specified in TS 38.214 [10] or transmitted sub-bands for wideband operation are transmitted according to the wideband configurations of Table 6.2F.2-2. +NOTE 4: Exception for 100MHz Full RB allocation MPR applies when all RB's in all sub-bands for 100MHz wideband operation are fully allocated and sub-bands are transmitted according to the wideband configurations of Table 6.2F.2-2. +NOTE 5: Contiguous outer sub-band configuration and contiguous inner sub-band configuration in Table 6.1.2.1.1.1-5 apply. + +**Table 6.1.2.1.1.1-5: Outer/Inner sub-band configuration for SL-U wideband operation** + +| Wideband operation channel bandwidth (MHz) | Contiguous sub-band configuration | | Non-contiguous sub-band configuration | | +|--------------------------------------------|---------------------------------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------|-------| +| | Outer | Inner | Outer | Inner | +| 40 | 11, 10, 01 | N/A | N/A | N/A | +| 60 | 111, 110, 011, 100, 001 | 010 | 101 | N/A | +| 80 | 1111, 1110, 0111, 1100, 0011, 1000, 0001 | 0110, 0100, 0010 | 1101, 1011, 1010, 0101, 1001 | N/A | +| 100 | 11111, 11110, 01111, 11100, 00111, 11000, 00011, 10000, 00001 | 01110, 01100, 00110, 01000, 00010, 00100 | 11011, 11010, 01011, 11001, 10011, 10101, 10110, 01101, 10100, 00101, 10010, 01001, 11101, 10111, 10001 | 01010 | + +NOTE 1: The sub-band configuration is represented as a bitmap where '1' indicates that a sub-band is transmitted and '0' indicates a sub-band is not transmitted. The bitmap is ordered with MSB mapped to the lowest frequency sub-band and LSB mapped to highest frequency sub-band within the wideband channel. + +###### 6.1.2.1.1.2 OPPO's simulation results (R4-2316119) + +With the agreement above, the simulation cases are updated with 60kHz deleted. For each case, the QPSK, 16QAM, 64QAM and 256QAM will be simulated. + +Table 6.1.2.1.1.2-1 simulation cases + +| | case | Waveform | BW | RB Setup | SCS | +|----------------------------------------------|------|----------|-----|-------------------|-----| +| Full Allocation Single CC | 1 | CP-OFDM | 20 | 105RB0 | 15 | +| | 2 | CP-OFDM | 20 | 50RB0 | 30 | +| | 3 | CP-OFDM | 40 | 216RB0 | 15 | +| | 4 | CP-OFDM | 40 | 105RB0 | 30 | +| | 5 | CP-OFDM | 60 | 160RB0 | 30 | +| | 6 | CP-OFDM | 80 | 216RB0 | 30 | +| | 7 | CP-OFDM | 100 | 270RB0 | 30 | +| Interlaced Allocation Single CC | 8 | CP-OFDM | 20 | 1 RB0 every 10RBs | 15 | +| | 9 | CP-OFDM | 20 | 1RB0 every 5RBs | 30 | +| | 10 | CP-OFDM | 40 | 1RB0 every 10RBs | 15 | +| | 11 | CP-OFDM | 40 | 1RB0 every 5RBs | 30 | +| | 12 | CP-OFDM | 60 | 1RB0 every 5RBs | 30 | +| | 13 | CP-OFDM | 80 | 1RB0 every 5RBs | 30 | +| | 14 | CP-OFDM | 100 | 1RB0 every 5RBs | 30 | +| Wide band operation contiguous RB allocation | 15 | CP-OFDM | 40 | Bitmap 10 | 30 | +| | 16 | CP-OFDM | 60 | Bitmap 100 | 30 | +| | 17 | CP-OFDM | 60 | Bitmap 110 | 30 | +| | 18 | CP-OFDM | 60 | Bitmap 010 | 30 | +| | 19 | CP-OFDM | 80 | Bitmap 1000 | 30 | +| | 20 | CP-OFDM | 80 | Bitmap 1100 | 30 | +| | 21 | CP-OFDM | 80 | Bitmap 1110 | 30 | +| | 22 | CP-OFDM | 80 | Bitmap 0100 | 30 | +| | 23 | CP-OFDM | 80 | Bitmap 0110 | 30 | +| | 24 | CP-OFDM | 100 | Bitmap 10000 | 30 | +| | 25 | CP-OFDM | 100 | Bitmap 11000 | 30 | +| | 26 | CP-OFDM | 100 | Bitmap 11100 | 30 | +| | 27 | CP-OFDM | 100 | Bitmap 11110 | 30 | +| | 28 | CP-OFDM | 100 | Bitmap 01000 | 30 | +| | 29 | CP-OFDM | 100 | Bitmap 01100 | 30 | +| | 30 | CP-OFDM | 100 | Bitmap 01110 | 30 | +| | 31 | CP-OFDM | 100 | Bitmap 00100 | 30 | +| Wide band operation Interlaced RB allocation | 32 | CP-OFDM | 40 | Bitmap 10 | 30 | +| | 33 | CP-OFDM | 60 | Bitmap 100 | 30 | +| | 34 | CP-OFDM | 60 | Bitmap 110 | 30 | +| | 35 | CP-OFDM | 60 | Bitmap 010 | 30 | +| | 36 | CP-OFDM | 80 | Bitmap 1000 | 30 | +| | 37 | CP-OFDM | 80 | Bitmap 1100 | 30 | +| | 38 | CP-OFDM | 80 | Bitmap 1110 | 30 | +| | 39 | CP-OFDM | 80 | Bitmap 0100 | 30 | +| | 40 | CP-OFDM | 80 | Bitmap 0110 | 30 | +| | 41 | CP-OFDM | 100 | Bitmap 10000 | 30 | +| | 42 | CP-OFDM | 100 | Bitmap 11000 | 30 | +| | 43 | CP-OFDM | 100 | Bitmap 11100 | 30 | +| | 44 | CP-OFDM | 100 | Bitmap 11110 | 30 | +| | 45 | CP-OFDM | 100 | Bitmap 01000 | 30 | +| | 46 | CP-OFDM | 100 | Bitmap 01100 | 30 | +| | 47 | CP-OFDM | 100 | Bitmap 01110 | 30 | +| | 48 | CP-OFDM | 100 | Bitmap 00100 | 30 | + +Corresponding MPR results are shown as below for case 1 to 14: + +Table 6.1.2.1.1.2-2 MPR for single CC + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 3.2 | 3.1 | 3.2 | 3.2 | 3.2 | 3.2 | 3.2 | 3.4 | 3.1 | 3.3 | 3.2 | 3.2 | 3.3 | 3.2 | +| 16QAM | 3.7 | 3.6 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 3.4 | 3.1 | 3.3 | 3.2 | 3.2 | 3.3 | 3.2 | +| 64QAM | 5.0 | 5.2 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 4.1 | 4.3 | 4.1 | 4.4 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 6.6 | 7.5 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +Table 6.1.2.1.1.2-3 MPR for Wideband operation + +| | Bitmap | 10 | 100 | 1000 | 10000 | 010 | 0100 | 01000 | 00100 | 110 | 1100 | 11000 | 01100 | 011000 | 11100 | 111000 | 01110 | 11110 | +|------------|--------|-----|-----|------|-------|-----|------|-------|-------|-----|------|-------|-------|--------|-------|--------|-------|-------| +| Contiguous | QPSK | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | +| | 16QAM | 3.5 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.7 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.7 | 3.6 | +| | 64QAM | 5.1 | 5.1 | 4.8 | 5.2 | 4.7 | 5.1 | 4.9 | 5.1 | 4.9 | 5.1 | 4.7 | 4.8 | 5.0 | 5.1 | 4.8 | 5.0 | 5.2 | +| | 256QAM | 7.4 | 7.5 | 7.7 | 8.5 | 7.3 | 7.4 | 8.0 | 7.5 | 8.5 | 7.4 | 7.3 | 7.6 | 8.0 | 7.4 | 7.7 | 8.5 | 8.5 | +| Interlaced | QPSK | 2.6 | 2.6 | 2.7 | 2.8 | 2.6 | 2.6 | 2.6 | 2.6 | 2.6 | 2.6 | 2.7 | 2.7 | 2.7 | 2.6 | 2.7 | 2.8 | 2.6 | +| | 16QAM | 2.9 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 3.0 | 2.8 | 2.9 | 3.0 | 3.0 | 2.8 | +| | 64QAM | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.0 | 4.1 | 4.2 | 4.1 | 4.1 | +| | 256QAM | 6.5 | 6.6 | 6.8 | 6.6 | 6.8 | 6.6 | 6.7 | 6.6 | 6.8 | 6.6 | 6.8 | 6.7 | 6.6 | 6.6 | 6.8 | 6.7 | 6.5 | + +![Scatter plot titled 'Single CC MPR' showing MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 cases. The plot compares Contiguous (solid lines) and Interlaced (dashed lines) operation. The y-axis ranges from 0.0 to 10.0. The x-axis represents cases 1 to 14. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](a52ceaa1a0038c4e12cf866ad1ddd6bb_img.jpg) + +| Case | Modulation | Contiguous MPR | Interlaced MPR | +|------|------------|----------------|----------------| +| 1 | QPSK | 3.2 | 2.6 | +| 1 | 16QAM | 3.7 | 2.9 | +| 1 | 64QAM | 5.0 | 4.1 | +| 1 | 256QAM | 8.8 | 6.5 | +| 2 | QPSK | 3.1 | 2.6 | +| 2 | 16QAM | 3.6 | 2.9 | +| 2 | 64QAM | 5.2 | 4.1 | +| 2 | 256QAM | 8.6 | 6.6 | +| 3 | QPSK | 3.2 | 2.7 | +| 3 | 16QAM | 3.7 | 3.0 | +| 3 | 64QAM | 5.1 | 4.2 | +| 3 | 256QAM | 8.6 | 6.8 | +| 4 | QPSK | 3.2 | 2.8 | +| 4 | 16QAM | 3.7 | 2.9 | +| 4 | 64QAM | 5.0 | 4.1 | +| 4 | 256QAM | 8.8 | 6.6 | +| 5 | QPSK | 3.2 | 2.6 | +| 5 | 16QAM | 3.7 | 3.0 | +| 5 | 64QAM | 5.2 | 4.2 | +| 5 | 256QAM | 8.6 | 6.8 | +| 6 | QPSK | 3.2 | 2.6 | +| 6 | 16QAM | 3.7 | 2.9 | +| 6 | 64QAM | 5.1 | 4.1 | +| 6 | 256QAM | 8.5 | 6.6 | +| 7 | QPSK | 3.2 | 2.6 | +| 7 | 16QAM | 3.6 | 2.6 | +| 7 | 64QAM | 5.1 | 4.1 | +| 7 | 256QAM | 8.7 | 6.7 | +| 8 | QPSK | 3.4 | 2.6 | +| 8 | 16QAM | 3.4 | 2.6 | +| 8 | 64QAM | 4.1 | 2.6 | +| 8 | 256QAM | 6.6 | 6.6 | +| 9 | QPSK | 3.1 | 2.6 | +| 9 | 16QAM | 3.1 | 2.6 | +| 9 | 64QAM | 4.3 | 2.6 | +| 9 | 256QAM | 7.5 | 6.6 | +| 10 | QPSK | 3.3 | 2.7 | +| 10 | 16QAM | 3.3 | 2.7 | +| 10 | 64QAM | 4.1 | 2.7 | +| 10 | 256QAM | 7.6 | 6.8 | +| 11 | QPSK | 3.2 | 2.7 | +| 11 | 16QAM | 3.2 | 2.7 | +| 11 | 64QAM | 4.4 | 2.7 | +| 11 | 256QAM | 7.9 | 6.7 | +| 12 | QPSK | 3.2 | 2.6 | +| 12 | 16QAM | 3.2 | 2.6 | +| 12 | 64QAM | 4.1 | 2.6 | +| 12 | 256QAM | 6.6 | 6.6 | +| 13 | QPSK | 3.3 | 2.7 | +| 13 | 16QAM | 3.3 | 2.7 | +| 13 | 64QAM | 3.9 | 2.7 | +| 13 | 256QAM | 6.5 | 6.8 | +| 14 | QPSK | 3.2 | 2.6 | +| 14 | 16QAM | 3.2 | 2.6 | +| 14 | 64QAM | 4.0 | 2.6 | +| 14 | 256QAM | 6.8 | 6.5 | + +Scatter plot titled 'Single CC MPR' showing MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 cases. The plot compares Contiguous (solid lines) and Interlaced (dashed lines) operation. The y-axis ranges from 0.0 to 10.0. The x-axis represents cases 1 to 14. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.2.1.1.2-1, Contiguous and Interlaced Single CC MPR + +![Figure 6.1.2.1.1.2-2: Wideband MPR plot showing MPR values for cases 15 to 48 across four modulation schemes: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). The y-axis ranges from 0.0 to 9.0. The plot shows that for cases 15, 16, 17, 19, 20, 22, 24, 25, 26, 28, and 29, the MPR values for 256QAM are around 8.0 dB, while for other cases they are around 7.0 dB. The other modulation schemes show lower MPR values, generally between 2.5 and 5.5 dB.](c17eaf807acd5faec68da19dd16929be_img.jpg) + +Figure 6.1.2.1.1.2-2: Wideband MPR plot showing MPR values for cases 15 to 48 across four modulation schemes: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). The y-axis ranges from 0.0 to 9.0. The plot shows that for cases 15, 16, 17, 19, 20, 22, 24, 25, 26, 28, and 29, the MPR values for 256QAM are around 8.0 dB, while for other cases they are around 7.0 dB. The other modulation schemes show lower MPR values, generally between 2.5 and 5.5 dB. + +**Figure 6.1.2.1.1.2-2, Contiguous and Interlaced Wideband MPR** + +The case 15, 16, 17, 19, 20, 22, 24, 25, 26, 28, 29 can apply 8dB limit while the rest of the cases should apply 9dB limit. + +So the exception bitmap can be listed as below: + +**Table 6.1.2.1.1.2-4 exception cases mapping to bitmap** + +| | | | | | +|----|---------|-----|--------------|----| +| 15 | CP-OFDM | 40 | Bitmap 10 | 30 | +| 16 | CP-OFDM | 60 | Bitmap 100 | 30 | +| 17 | CP-OFDM | 60 | Bitmap 110 | 30 | +| 19 | CP-OFDM | 80 | Bitmap 1000 | 30 | +| 20 | CP-OFDM | 80 | Bitmap 1100 | 30 | +| 22 | CP-OFDM | 80 | Bitmap 0100 | 30 | +| 24 | CP-OFDM | 100 | Bitmap 10000 | 30 | +| 25 | CP-OFDM | 100 | Bitmap 11000 | 30 | +| 26 | CP-OFDM | 100 | Bitmap 11100 | 30 | +| 28 | CP-OFDM | 100 | Bitmap 01000 | 30 | +| 29 | CP-OFDM | 100 | Bitmap 01100 | 30 | + +The Exception MPR mapping for wideband operation is proposed as below: + +**Table 6.1.2.1.1.2-5: Exception bitmap mapping** + +| Wideband operation channel bandwidth (MHz) | Sub-band configuration exceptions | +|--------------------------------------------|----------------------------------------------------------------------| +| 40 | 10, 01 | +| 60 | 110, 011 | +| 80 | 1000, 1100, 0100, 0010, 0011, 0001 | +| 100 | 10000, 11000, 11100, 01000, 01100, 00110, 00010, 00111, 00011, 00001 | + +###### **6.1.2.1.1.3 Huawei’s simulation results (R4-2315226)** + +Referring to the simulation cases listed in Table 6.1.2.1.1.3-1, the MPR value are shown in Table -2 and Table -3 for below. + +Table 6.1.2.1.1.3-1 Simulation cases for SL-U + +| | case | Waveform | BW | RB Setup | SCS | +|---------------------------------|------|----------|-----|-------------------|-----| +| Full Allocation Single CC | 1 | CP-OFDM | 20 | 105RB0 | 15 | +| | 2 | CP-OFDM | 20 | 50RB0 | 30 | +| | 3 | CP-OFDM | 40 | 216RB0 | 15 | +| | 4 | CP-OFDM | 60 | 160RB0 | 30 | +| | 5 | CP-OFDM | 80 | 216RB0 | 30 | +| | 6 | CP-OFDM | 100 | 270RB0 | 30 | +| Interlaced Allocation Single CC | 7 | CP-OFDM | 20 | 1 RB0 every 10RBs | 15 | +| | 8 | CP-OFDM | 20 | 1RB0 every 5RBs | 30 | +| | 9 | CP-OFDM | 40 | 1RB0 every 10RBs | 15 | +| | 10 | CP-OFDM | 60 | 1RB0 every 5RBs | 30 | +| | 11 | CP-OFDM | 80 | 1RB0 every 5RBs | 30 | +| | 12 | CP-OFDM | 100 | 1RB0 every 5RBs | 30 | +| Wide band operation | 13 | CP-OFDM | 40 | Bitmap 10 | 15 | +| | 14 | CP-OFDM | 60 | Bitmap 100 | 30 | +| | 15 | CP-OFDM | 60 | Bitmap 110 | 30 | +| | 16 | CP-OFDM | 80 | Bitmap 1000 | 30 | +| | 17 | CP-OFDM | 80 | Bitmap 1100 | 30 | +| | 18 | CP-OFDM | 80 | Bitmap 1110 | 30 | +| | 19 | CP-OFDM | 80 | Bitmap 0100 | 30 | +| | 20 | CP-OFDM | 80 | Bitmap 0110 | 30 | +| | 21 | CP-OFDM | 100 | Bitmap 10000 | 30 | +| | 22 | CP-OFDM | 100 | Bitmap 11000 | 30 | +| | 23 | CP-OFDM | 100 | Bitmap 11100 | 30 | +| | 24 | CP-OFDM | 100 | Bitmap 11110 | 30 | +| | 25 | CP-OFDM | 100 | Bitmap 01000 | 30 | +| | 26 | CP-OFDM | 100 | Bitmap 01100 | 30 | +| | 27 | CP-OFDM | 100 | Bitmap 01110 | 30 | +| | 28 | CP-OFDM | 100 | Bitmap 00100 | 30 | + +Table 6.1.2.1.1.3-2 Maximum power reduction (MPR) for SL-U with Full Allocation + +| Modulation | Case: Bandwidth/SCS | | | | | | +|------------|---------------------|-----------|-----------|-----------|-----------|------------| +| | 20MHz/15k | 20MHz/30k | 40MHz/15k | 60MHz/30k | 80MHz/30k | 100MHz/30k | +| QPSK | 4.0 | 3.8 | 4.1 | 4.0 | 4.0 | 4.1 | +| 16 QAM | 4.1 | 3.9 | 4.1 | 4.1 | 3.8 | 4.2 | +| 64 QAM | 6.1 | 6.1 | 6.1 | 6.1 | 6.1 | 6.1 | +| 256 QAM | 7.5 | 7.7 | 7.6 | 7.8 | 7.5 | 7.9 | + +Table 6.1.2.1.1.3-3 Maximum power reduction (MPR) for SL-U with Interlaced Allocation + +| Modulation | Case: Bandwidth/SCS | | | | | | +|------------|---------------------|-----------|-----------|-----------|-----------|------------| +| | 20MHz/15k | 20MHz/30k | 40MHz/15k | 60MHz/30k | 80MHz/30k | 100MHz/30k | +| QPSK | 4.0 | 4.1 | 4.0 | 4.1 | 4.1 | 4.1 | +| 16 QAM | 4.1 | 4.2 | 4.2 | 4.1 | 4.2 | 4.2 | +| 64 QAM | 5.8 | 5.9 | 5.7 | 5.6 | 5.9 | 6.1 | +| 256 QAM | 7.0 | 7.3 | 7.1 | 7.4 | 7.7 | 7.4 | + +Table 6.1.2.1.1.3-4 Maximum power reduction (MPR) for SL-U with Wide band operation + +| Modulation | Case: Bandwidth/Bitmap pattern | | | | | | | | | | | | +|------------|--------------------------------|-------|-----|-------|------|------|--------|-------|-------|-------|-------|-------| +| | 40MHz | 60MHz | | 80MHz | | | 100MHz | | | | | | +| | 10 | 100 | 110 | 1000 | 1110 | 0110 | 10000 | 11110 | 01000 | 01100 | 01110 | 00100 | +| QPSK | 4.0 | 3.7 | 3.9 | 3.8 | 4.0 | 3.8 | 3.9 | 4.1 | 3.0 | 3.2 | 3.9 | 3.4 | +| 16 QAM | 4.0 | 3.9 | 4.1 | 3.9 | 4.1 | 3.9 | 3.9 | 4.2 | 3.7 | 3.8 | 4.0 | 3.7 | +| 64 QAM | 5.1 | 5.1 | 5.5 | 5.2 | 5.7 | 5.7 | 5.1 | 5.8 | 5.4 | 6.0 | 5.9 | 5.5 | +| 256 QAM | 6.4 | 6.8 | 6.9 | 6.3 | 7.0 | 7.1 | 6.5 | 7.3 | 6.7 | 7.4 | 7.3 | 7.0 | + +**Table 6.1.2.1.1.3-5: Proposed MPR for SL-U with single CC** + +| Precoding | Modulation | Full | Partial | +|-----------|------------|-------|---------| +| CP-OFDM | QPSK | ≤ 4.1 | ≤ 4.1 | +| | 16 QAM | ≤ 4.2 | ≤ 4.2 | +| | 64 QAM | ≤ 6.1 | ≤ 6.1 | +| | 256 QAM | ≤ 8.0 | ≤ 7.7 | + +6.1.2.1.1.4 + +Qualcomm's simulation results (R4-2316791) + +**Table 6.1.2.1.1.4-1: Power class 5 PSSCH/PSCCH MPR simulation results** + +| | cas e | Precoding | BW | RB Setup | SCS | QPSK and 16QAM MPR | 64 QAM MPR | 256 QAM MPR | +|----------------------------------------|-------|-----------|-----|-------------------|-----|--------------------|------------|-------------| +| Full Allocation Single CC | 1 | CP-OFDM | 20 | 105RB0 | 15 | 3.5 | 3.8 | 6.2 | +| | 2 | CP-OFDM | 20 | 50RB0 | 30 | 3.5 | 3.8 | 6.0 | +| | 3 | CP-OFDM | 40 | 216RB0 | 15 | 3.6 | 3.7 | 6.0 | +| | 4 | CP-OFDM | 60 | 160RB0 | 30 | 3.5 | 3.6 | 6.0 | +| | 5 | CP-OFDM | 80 | 216RB0 | 30 | 3.6 | 3.7 | 6.2 | +| | 6 | CP-OFDM | 100 | 270RB0 | 30 | | | | +| Interlaced Allocation Single CC | 7 | CP-OFDM | 20 | 1 RB0 every 10RBs | 15 | 3.5 | 3.7 | 6.2 | +| | 8 | CP-OFDM | 20 | 1RB0 every 5RBs | 30 | 3.6 | 3.7 | 6.1 | +| | 9 | CP-OFDM | 40 | 1RB0 every 10RBs | 15 | 3.6 | 3.9 | 6.4 | +| | 10 | CP-OFDM | 60 | 1RB0 every 5RBs | 30 | 3.5 | 3.7 | 6.3 | +| | 11 | CP-OFDM | 80 | 1RB0 every 5RBs | 30 | 3.7 | 3.9 | 6.5 | +| | 12 | CP-OFDM | 100 | 1RB0 every 5RBs | 30 | 3.6 | 4.1 | 6.6 | +| Wide band Full operation | 13 | CP-OFDM | 40 | Bitmap 10 | 15 | 3.6 | 3.7 | 6.0 | +| | 14 | CP-OFDM | 60 | Bitmap 100 | 30 | 3.1 | 3.6 | 6.0 | +| | 15 | CP-OFDM | 60 | Bitmap 110 | 30 | 3.3 | 3.7 | 6.0 | +| | 16 | CP-OFDM | 80 | Bitmap 1000 | 30 | 3.1 | 3.6 | 6.0 | +| | 17 | CP-OFDM | 80 | Bitmap 1100 | 30 | 3.3 | 3.7 | 6.0 | +| | 18 | CP-OFDM | 80 | Bitmap 1110 | 30 | 3.4 | 3.6 | 6.0 | +| | 19 | CP-OFDM | 80 | Bitmap 0100 | 30 | 1.3 | 3.6 | 6.0 | +| | 20 | CP-OFDM | 80 | Bitmap 0110 | 30 | 1.3 | 3.5 | 5.9 | +| | 21 | CP-OFDM | 100 | Bitmap 10000 | 30 | 3.1 | 3.6 | 6.0 | +| | 22 | CP-OFDM | 100 | Bitmap 11000 | 30 | 3.3 | 3.7 | 6.0 | +| | 23 | CP-OFDM | 100 | Bitmap 11100 | 30 | 3.4 | 3.6 | 6.0 | +| | 24 | CP-OFDM | 100 | Bitmap 11110 | 30 | 3.4 | 3.7 | 6.2 | +| | 25 | CP-OFDM | 100 | Bitmap 01000 | 30 | | | | +| | 26 | CP-OFDM | 100 | Bitmap 01100 | 30 | 1.4 | 3.5 | 5.9 | +| | 27 | CP-OFDM | 100 | Bitmap 01110 | 30 | 1.5 | 3.8 | 6.5 | +| | 28 | CP-OFDM | 100 | Bitmap 00100 | 30 | | | | +| Wide band Interlaced operation | 29 | CP-OFDM | 40 | Bitmap 10 | 15 | 3.5 | 3.7 | 6.0 | +| | 30 | CP-OFDM | 60 | Bitmap 100 | 30 | 3.2 | 3.8 | 6.1 | +| | 31 | CP-OFDM | 60 | Bitmap 110 | 30 | 3.5 | 4.0 | 6.6 | +| | 32 | CP-OFDM | 80 | Bitmap 1000 | 30 | 3.2 | 3.8 | 6.1 | +| | 33 | CP-OFDM | 80 | Bitmap 1100 | 30 | 3.5 | 4.0 | 6.6 | +| | 34 | CP-OFDM | 80 | Bitmap 1110 | 30 | 3.5 | 4.0 | 6.6 | +| | 35 | CP-OFDM | 80 | Bitmap 0100 | 30 | 1.4 | 3.8 | 6.1 | +| | 36 | CP-OFDM | 80 | Bitmap 0110 | 30 | 1.6 | 4.0 | 6.5 | +| | 37 | CP-OFDM | 100 | Bitmap 10000 | 30 | 3.2 | 3.8 | 6.1 | +| | 38 | CP-OFDM | 100 | Bitmap 11000 | 30 | 3.5 | 4.1 | 6.6 | +| | 39 | CP-OFDM | 100 | Bitmap 11100 | 30 | 3.5 | 4.0 | 6.6 | +| | 40 | CP-OFDM | 100 | Bitmap 11110 | 30 | 3.6 | 3.9 | 6.5 | +| | 41 | CP-OFDM | 100 | Bitmap 01000 | 30 | 1.4 | 3.8 | 6.1 | + +| | | | | | | | | | +|--|----|---------|-----|--------------|----|-----|-----|-----| +| | 42 | CP-OFDM | 100 | Bitmap 01100 | 30 | 1.6 | 4.0 | 6.5 | +| | 43 | CP-OFDM | 100 | Bitmap 01110 | 30 | 1.6 | 4.0 | 6.6 | +| | 44 | CP-OFDM | 100 | Bitmap 00100 | 30 | | | | + +The power class 5 PSSCH/PSCCH simulation results in the table should be considered in the discussion of MPR requirements. + +###### 6.1.2.1.1.5 Xiaomi's simulation results (R4-2315440) + +Table 6.1.2.1.1.5-1 and Figure 6.1.2.1.1.5-1 show the MPR values for different modulations for PSCCH and PSSCH in single CC operation with full allocation: + +**Table 6.1.2.1.1.5-1 MPR for PSCCH and PSSCH in single CC operation** + +| | case | Waveform | BW | RB Setup | SCS | MPR | | | | +|--------------------------------------|------|----------|-----|----------|-----|------|-------|-------|--------| +| | | | | | | QPSK | 16QAM | 64QAM | 256QAM | +| Full Allocation
Single CC | 1 | CP-OFDM | 20 | 105RB0 | 15 | 3.2 | 3.4 | 5.1 | 14 | +| | 2 | CP-OFDM | 20 | 50RB0 | 30 | 3.2 | 3.5 | 5.5 | 14.5 | +| | 3 | CP-OFDM | 40 | 216RB0 | 15 | 3.5 | 3.5 | 5.1 | 14 | +| | 4 | CP-OFDM | 60 | 160RB0 | 30 | 3.3 | 3.5 | 5.5 | 14.2 | +| | 5 | CP-OFDM | 80 | 216RB0 | 30 | 3.2 | 3.5 | 5.1 | 14 | +| | 6 | CP-OFDM | 100 | 270RB0 | 30 | 3.5 | 3.5 | 5.5 | 14.2 | + +![Figure 6.1.2.1.1.5-1: Contiguous Single CC MPR. A scatter plot showing MPR values for different modulations (QPSK, 16QAM, 64QAM, 256QAM) across various bandwidths and RB setups. The y-axis is labeled 'CE/ 표준' and the x-axis is labeled 'CE/ 표준'. The legend indicates: QPSK (blue circle), 16QAM (orange circle), 64QAM (grey circle), and 256QAM (yellow circle).](953203b3208524d293d4a65c0569324c_img.jpg) + +Figure 6.1.2.1.1.5-1: Contiguous Single CC MPR. A scatter plot showing MPR values for different modulations (QPSK, 16QAM, 64QAM, 256QAM) across various bandwidths and RB setups. The y-axis is labeled 'CE/ 표준' and the x-axis is labeled 'CE/ 표준'. The legend indicates: QPSK (blue circle), 16QAM (orange circle), 64QAM (grey circle), and 256QAM (yellow circle). + +**Figure 6.1.2.1.1.5-1 MPR for PSCCH and PSSCH in single CC operation with full allocation** + +Based on above simulation results for full allocation in single CC, we proposed: + +The MPR of full allocation for PC5 SL-U shall be as below table 6.1.2.1.1.5-2. + +**Table 6.1.2.1.1.5-2 Proposed MPR for PSCCH and PSSCH in single CC operation.** + +| Pre-coding | Modulation | RB Allocation | +|------------|------------|---------------| +| | | Full (dB) | +| CP-OFDM | QPSK | 4 | +| | 16 QAM | 4 | +| | 64 QAM | 6 | +| | 256 QAM | 14 | + +##### 6.1.2.1.2 MPR for S-SSB transmission + +###### 6.1.2.1.2.1 LG Electronics' simulation results (R4-2315542) + +Tx Power for multiple S-SSBs + +The equal power per each S-SSB is assumed for MPR and A-MPR simulation. + +For S-SSB MPR/A-MPR, the following simulation scenarios of Table 6.1.2.1.2.1-1 are considered. + +Table 6.1.2.1.2.1-1: SL-U S-SSB MPR/A-MPR simulation scenarios + +| Sub-band RB sets | Scenario | Bitmap | S-SSB {11RBs}xN repeated RB location index | N
(Repeated#
) | SCS(kHz) | +|------------------|----------|--------|--------------------------------------------|----------------------|----------| +|------------------|----------|--------|--------------------------------------------|----------------------|----------| + +| | | | | | | +|-----------|---|---|-----------------------------|---|----| +| 1 (20MHz) | 1 | 1 | {0 11 22 33 44 55 66 77 88} | 9 | 15 | +| | 2 | 1 | {0 23 46 69 92} | 5 | 15 | + +| | | | | | | +|------------|----|-------|--------------------------------------------------------------------------|----|----| +| | 3 | 1 | {0 95} | 2 | 15 | +| | 4 | 1 | {0 11 22 33} | 4 | 30 | +| | 5 | 1 | {0 39} | 2 | 30 | +| 2 (40MHz) | 6 | 11 | {0 11 22 33 44 55 66 77 88 111 122 133 144 155 166 177 188 199} | 18 | 15 | +| | 7 | 11 | {0 23 46 69 92 111 134 157 180 203} | 10 | 15 | +| | 8 | 11 | {0 94 111 205} | 4 | 15 | +| | 9 | 10 | {0 11 22 33 44 55 66 77 88} | 9 | 15 | +| | 10 | 10 | {0 23 46 69 92 } | 5 | 15 | +| | 11 | 10 | {0 94} | 2 | 15 | +| 3 (60MHz) | 12 | 111 | {0 11 22 33 56 67 78 89 112 123 134 145} | 12 | 30 | +| | 13 | 111 | {0 38 56 94 112 150} | 6 | 30 | +| | 14 | 110 | {0 11 22 33 56 67 78 89} | 8 | 30 | +| | 15 | 110 | {0 38 56 94 } | 4 | 30 | +| | 16 | 100 | {0 11 22 33} | 4 | 30 | +| | 17 | 100 | {0 38} | 2 | 30 | +| | 18 | 010 | {56 67 78 89 } | 4 | 30 | +| | 19 | 010 | {56 94} | 2 | 30 | +| | 20 | 101 | {0 11 22 33 112 123 134 145} | 8 | 30 | +| | 21 | 101 | {0 38 112 150} | 4 | 30 | +| 4 (80MHz) | 22 | 1111 | {0 11 22 33 56 67 78 89 111 122 133 144 167 178 189 200} | 16 | 30 | +| | 23 | 1111 | {0 38 56 94 111 149 167 205} | 8 | 30 | +| | 24 | 1110 | {0 11 22 33 56 67 78 89 111 122 133 144} | 12 | 30 | +| | 25 | 1110 | {0 38 56 94 111 149 } | 6 | 30 | +| | 26 | 1100 | {0 11 22 33 56 67 78 89} | 8 | 30 | +| | 27 | 1100 | {0 38 56 94} | 4 | | +| | 28 | 1000 | {0 11 22 33} | 4 | 30 | +| | 29 | 1000 | {0 38} | 2 | 30 | +| | 30 | 0110 | {56 67 78 89 111 122 133 144} | 8 | 30 | +| | 31 | 0110 | {56 94 111 49} | 4 | 30 | +| | 32 | 0100 | {56 67 78 89} | 4 | 30 | +| | 33 | 0100 | {56 94} | 2 | 30 | +| | 34 | 1101 | {0 11 22 33 56 67 78 89 167 178 189 200} | 12 | 30 | +| | 35 | 1101 | {0 38 56 94 167 205} | 6 | 30 | +| | 36 | 1010 | {0 11 22 33 111 122 133 144} | 8 | 30 | +| | 37 | 1010 | {0 38 111 149} | 4 | 30 | +| | 38 | 1001 | {0 11 22 33 167 178 189 200} | 8 | 30 | +| | 39 | 1001 | {0 38 167 205} | 4 | 30 | +| 5 (100MHz) | 40 | 11111 | {0 11 22 33 56 67 78 89 112 123 134 145 167 178 189 200 223 234 245 256} | 20 | 30 | +| | 41 | 11111 | {0 38 56 94 112 148 167 205 223 261} | 10 | 30 | +| | 42 | 11110 | {0 11 22 33 56 67 78 89 112 123 134 145 167 178 189 200} | 16 | 30 | +| | 43 | 11110 | {0 38 56 94 112 148 167 205} | 8 | 30 | +| | 44 | 11100 | {0 11 22 33 56 67 78 89 112 123 134 145} | 12 | 30 | +| | 45 | 11100 | {0 38 56 94 112 148} | 6 | 30 | +| | 46 | 11000 | {0 11 22 33 56 67 78 89} | 8 | 30 | +| | 47 | 11000 | {0 38 56 94} | 4 | 30 | +| | 48 | 10000 | {0 11 22 33} | 4 | 30 | +| | 49 | 10000 | {0 38} | 2 | 30 | +| | 50 | 01110 | {56 67 78 89 112 123 134 145 167 178 189 200} | 12 | 30 | +| | 51 | 01110 | {56 94 112 148 167 205} | 6 | 30 | +| | 52 | 01100 | {56 67 78 89 112 123 134 145} | 8 | 30 | +| | 53 | 01100 | {56 94 112 148} | 4 | 30 | +| | 54 | 01000 | {56 67 78 89} | 4 | 30 | + +| | | | | | +|----|-------|----------------------------------------------------------|----|----| +| 55 | 01000 | {56 94} | 2 | 30 | +| 56 | 00100 | {112 123 134 145} | 4 | 30 | +| 57 | 00100 | {112 148} | 2 | 40 | +| 58 | 11011 | {0 11 22 33 56 67 78 89 167 178 189 200 223 234 245 256} | 16 | 30 | +| 59 | 11011 | {0 38 56 94 167 205 223 261} | 8 | 30 | +| 60 | 11010 | {0 11 22 33 56 67 78 89 167 178 189 200} | 12 | 30 | +| 61 | 11010 | {0 38 56 94 167 205} | 6 | 30 | +| 62 | 11001 | {0 11 22 33 56 67 78 89 223 234 245 256} | 12 | 30 | +| 63 | 11001 | {0 38 56 94 223 261} | 6 | 30 | +| 64 | 10101 | {0 11 22 33 112 123 134 145 223 234 245 256} | 12 | 30 | +| 65 | 10101 | {0 38 112 148 223 261} | 6 | 30 | +| 66 | 10110 | {0 11 22 33 112 123 134 145 167 178 189 200} | 12 | 30 | +| 67 | 10110 | {0 38 112 148 167 205} | 6 | 30 | +| 68 | 10100 | {0 11 22 33 112 123 134 145} | 8 | 30 | +| 69 | 10100 | {0 38 112 148} | 4 | 30 | +| 70 | 10010 | {0 11 22 33 167 178 189 200} | 8 | 30 | +| 71 | 10010 | {0 38 167 205} | 4 | 30 | +| 72 | 10001 | {0 11 22 33 223 234 245 256} | 8 | 30 | +| 73 | 10001 | {0 38 223 261} | 4 | 30 | +| 74 | 01010 | {56 67 78 89 167 178 189 200} | 8 | 30 | +| 75 | 01010 | {56 94 167 205} | 4 | 30 | +| 76 | 11101 | {0 11 22 33 56 67 78 89 112 123 134 145 223 234 245 256} | 16 | 30 | +| 77 | 11101 | {0 38 56 94 112 148 223 261} | 8 | 30 | + +Here, for S-SSB {11RBs}xN repeated RB location index, '0' means that {11RB} start RB index = 0. And, Bitmap '1' means the corresponding RB set is transmitted, and '0' means the corresponding RB set is not transmitted for wide band operation. + +Table 6.1.2.1.2.1-2 and Figure 6.1.2.1.2.1-1 show the MPR simulation results for the scenarios. + +Table 6.1.2.1.2.1-2: S-SSB MPR simulation results for SL-U power class 5 + +| Scenario # | #1 | #2 | #3 | #4 | #5 | | | | | | | | | | | +|------------|-------|------|-------|------|------|------|------|------|------|------|------|------|------|------|------| +| '20MHz' | 9.24 | 6.62 | 3.98 | 5.69 | 3.92 | | | | | | | | | | | +| Scenario # | #6 | #7 | #8 | #9 | #10 | #11 | | | | | | | | | | +| '40MHz' | 11.17 | 8.63 | 5.56 | 9.02 | 6.95 | 3.94 | | | | | | | | | | +| Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | | | | | +| '60MHz' | 9.29 | 6.72 | 7.87 | 5.31 | 5.57 | 3.94 | 4.54 | 3.52 | 7.67 | 5.49 | | | | | | +| Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | +| '80MHz' | 10.34 | 6.86 | 8.81 | 5.60 | 7.67 | 5.38 | 5.68 | 4.06 | 6.11 | 4.12 | 4.42 | 3.52 | 8.92 | 5.97 | 7.55 | +| Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | +| '100MHz' | 11.15 | 6.75 | 10.18 | 5.56 | 9.44 | 5.91 | 7.75 | 5.22 | 5.79 | 3.91 | 6.02 | 3.44 | 5.60 | 3.35 | 4.43 | +| Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | #71 | #72 | #73 | #74 | +| '100MHz' | 9.18 | 6.32 | 8.95 | 6.04 | 8.61 | 4.98 | 9.08 | 4.99 | 7.67 | 5.10 | 7.87 | 5.45 | 7.62 | 5.41 | 6.90 | + +![Scatter plot showing Tx Power Back Off [dB] vs Test Scenario # for 20MHz, 40MHz, and 60MHz. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 1 to 18. Data points are categorized by color and shape: red circles for 20MHz (scenarios 1-5), blue asterisks for 40MHz (scenarios 6-11), and pink diamonds for 60MHz (scenarios 12-18).](a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +| Test Scenario # | Back off [dB] | Bandwidth | +|-----------------|---------------|-----------| +| 1 | 9.24 | 20MHz | +| 2 | 6.62 | 20MHz | +| 3 | 3.98 | 20MHz | +| 4 | 5.69 | 20MHz | +| 5 | 3.92 | 20MHz | +| 6 | 11.17 | 40MHz | +| 7 | 8.63 | 40MHz | +| 8 | 5.56 | 40MHz | +| 9 | 9.02 | 40MHz | +| 10 | 6.95 | 40MHz | +| 11 | 3.94 | 40MHz | +| 12 | 9.29 | 60MHz | +| 13 | 6.72 | 60MHz | +| 14 | 7.87 | 60MHz | +| 15 | 5.31 | 60MHz | +| 16 | 5.57 | 60MHz | +| 17 | 3.94 | 60MHz | +| 18 | 4.54 | 60MHz | + +Scatter plot showing Tx Power Back Off [dB] vs Test Scenario # for 20MHz, 40MHz, and 60MHz. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 1 to 18. Data points are categorized by color and shape: red circles for 20MHz (scenarios 1-5), blue asterisks for 40MHz (scenarios 6-11), and pink diamonds for 60MHz (scenarios 12-18). + +a. 20MHz, 40MHz, and 60MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 40MHz bandwidth. The y-axis ranges from 0 to 11 dB, and the x-axis ranges from 22 to 37 scenarios. Data points are represented by right-pointing triangles.](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 22 | 10.5 | +| 23 | 7.0 | +| 24 | 9.0 | +| 25 | 5.8 | +| 26 | 7.8 | +| 27 | 5.5 | +| 28 | 5.8 | +| 29 | 4.2 | +| 30 | 6.2 | +| 31 | 4.2 | +| 32 | 4.5 | +| 33 | 3.8 | +| 34 | 9.0 | +| 35 | 6.0 | +| 36 | 7.8 | +| 37 | 5.2 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 40MHz bandwidth. The y-axis ranges from 0 to 11 dB, and the x-axis ranges from 22 to 37 scenarios. Data points are represented by right-pointing triangles. + +b. 80MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 40 to 74 scenarios. Data points are represented by red upward-pointing triangles.](4349d5e2b079af7d2e45e10a3b8235e9_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 40 | 11.2 | +| 41 | 6.8 | +| 42 | 10.2 | +| 43 | 5.8 | +| 44 | 9.5 | +| 45 | 6.0 | +| 46 | 7.8 | +| 47 | 5.2 | +| 48 | 6.0 | +| 49 | 4.0 | +| 50 | 6.0 | +| 51 | 3.5 | +| 52 | 5.8 | +| 53 | 3.5 | +| 54 | 4.5 | +| 55 | 3.5 | +| 56 | 4.5 | +| 57 | 3.5 | +| 58 | 10.2 | +| 59 | 7.0 | +| 60 | 9.2 | +| 61 | 6.2 | +| 62 | 9.0 | +| 63 | 6.0 | +| 64 | 8.8 | +| 65 | 5.0 | +| 66 | 9.2 | +| 67 | 5.0 | +| 68 | 7.8 | +| 69 | 5.2 | +| 70 | 8.0 | +| 71 | 5.5 | +| 72 | 7.8 | +| 73 | 5.5 | +| 74 | 7.0 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 40 to 74 scenarios. Data points are represented by red upward-pointing triangles. + +c. 100MHz + +Figure 6.1.2.1.2.1-2: S-SSB MPR simulation results for SL-U power class 5 + +Table 6.1.2.1.2.1-3 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration and the number of S-SSB repetition per RB set. + +**Table 6.1.2.1.2.1-3 : S-SSB MPR simulation results for SL-U power class 5** + +| | RB Allocation | | | | +|---------------------------------|----------------------------|------|----------------------------|------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous sub-band RB sets | 11.17 | 6.86 | 6.11 | 4.12 | +| Non-contiguous sub-band RB sets | 10.68 | 7.03 | 6.90 | 4.60 | + +The S-SSB MPR for SL-U power class 5 can be proposed as Table 6.1.2.1.2.1-4 or Table 6.1.2.1.2.1-5 based on the simulation results when considering implementation margin. + +**Table 6.1.2.1.2.1-4 : S-SSB MPR for SL-U UE power class 5** + +| | RB Allocation | | | | +|-------------------------------------------------------------------------------------------|----------------------------|------------|----------------------------|------------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous sub-band RB sets | $\leq 13.5$ | $\leq 9.5$ | $\leq 8.5$ | $\leq 6.5$ | +| Non-contiguous sub-band RB sets | $\leq 13.5$ | $\leq 9.5$ | $\leq 9.5$ | $\leq 7.0$ | +| NOTE 1: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. | | | | | + +**Table 6.1.2.1.2.1-5 : S-SSB MPR for SL-U UE power class 5** + +| | RB Allocation | | | | +|-------------------------------------------------------------------------------------------|----------------------------|------------|----------------------------|------------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous/Non-contiguous sub-band RB sets | $\leq 13.5$ | $\leq 9.5$ | $\leq 9.5$ | $\leq 7.0$ | +| NOTE 1: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. | | | | | + +###### 6.1.2.1.2.2 Huawei simulation results (R4-2319500) + +The evaluation scenarios and MPR results for PSFCH are illustrated in Table 6.1.2.1.2.2-1 + +**Table 6.1.2.1.2.2-1 Evaluation scenarios and MPR for SSB on shared spectrum** + +| Case | BW/SCS | RB_length/ RB_start | S-SSB repetition | MPR | +|------|--------------|---------------------|------------------|------| +| 1 | 20MHz/ 30kHz | 44RB0 | 4 | 7.8 | +| 2 | | 44RB3 | 4 | 7.3 | +| 3 | 20MHz/ 15kHz | 88RB0 | 8 | 10.7 | +| 4 | | 88RB8 | 8 | 10.1 | + +![Figure 6.1.2.1.2.2-1 PSD and SEM for Case 1. The left plot shows the Power Spectral Density (PSD) in dB versus Frequency in MHz, with a peak power around 0 MHz. The right plot shows the Spectral Emission Mask (SEM) in dB/MBW versus Frequency in MHz, comparing the SEM specification (red lines) with the measurement (blue line).](771c18f874d31c59c3b8c4e247be16ca_img.jpg) + +Figure 6.1.2.1.2.2-1 PSD and SEM for Case 1. The left plot shows the Power Spectral Density (PSD) in dB versus Frequency in MHz, with a peak power around 0 MHz. The right plot shows the Spectral Emission Mask (SEM) in dB/MBW versus Frequency in MHz, comparing the SEM specification (red lines) with the measurement (blue line). + +Figure 6.1.2.1.2.2-1 PSD and SEM for Case 1 + +![Figure 6.1.2.1.2.2-2 PSD and SEM for Case 4. The left plot shows the Power Spectral Density (PSD) in dB versus Frequency in MHz, with a peak power around 0 MHz. The right plot shows the Spectral Emission Mask (SEM) in dB/MBW versus Frequency in MHz, comparing the SEM specification (red lines) with the measurement (blue line).](0aa15f5c9c3edae230985491199cfe8b_img.jpg) + +Figure 6.1.2.1.2.2-2 PSD and SEM for Case 4. The left plot shows the Power Spectral Density (PSD) in dB versus Frequency in MHz, with a peak power around 0 MHz. The right plot shows the Spectral Emission Mask (SEM) in dB/MBW versus Frequency in MHz, comparing the SEM specification (red lines) with the measurement (blue line). + +Figure 6.1.2.1.2.2-2 PSD and SEM for Case 4 + +According to the simulation evaluation, we propose the MPR for S-SSB on shared spectrum to be 11dB taken margin into consideration. + +##### 6.1.2.1.3 MPR for PSFCH transmission + +###### 6.1.2.1.3.1 LG Electronics' simulation results (R4-2315542 and R4-2321771) + +For PSFCH MPR/A-MPR, the following simulation scenarios of Table 6.1.2.1.3.1-1 are considered based on Alt 1-1b. + +Table 6.1.2.1.3.1-1: SL-U PSFCH MPR/A-MPR simulation scenarios + +| Sub-band RB sets | Scenario | Bitmap | PSFCH RB location index | SCS(kHz) | +|------------------|----------|--------|-----------------------------------------------------------------------------------------------------------------|----------| +| 1 (20MHz) | 1 | 1 | {0 10 20 30 40 50 60 70 80 90 100 104} | 15 | +| | 2 | 1 | {0 5 10 15 20 25 30 35 40 45 49} | 30 | +| 2 (40MHz) | 3 | 11 | {0 10 20 30 40 50 60 70 80 90 100 104 111 121 131 141 151 161 171 181 191 201 211 215} | 15 | +| | 4 | 10 | {0 10 20 30 40 50 60 70 80 90 100 104} | 15 | +| 3 (60MHz) | 5 | 111 | {0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161} | 30 | +| | 6 | 110 | {0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105} | 30 | +| | 7 | 100 | {0 5 10 15 20 25 30 35 40 45 49} | 30 | +| | 8 | 010 | {56 61 66 71 76 81 86 91 96 101 105} | 30 | +| | 9 | 101 | {0 5 10 15 20 25 30 35 40 45 49 112 117 122 127 132 137} | 30 | + +| | | | | | +|------------|----|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| | | | 142 147 152 157 161} | | +| 4 (80MHz) | 10 | 1111 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 111 116 121 126 131 136 141 146 151 156 160 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 11 | 1110 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 111 116 121 126 131 136 141 146 151 156 160} | 30 | +| | 12 | 1100 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105} | 30 | +| | 13 | 1000 | { 0 5 10 15 20 25 30 35 40 45 49} | 30 | +| | 14 | 0110 | { 56 61 66 71 76 81 86 91 96 101 105 111 116 121 126 131 136 141 146 151 156 160} | 30 | +| | 15 | 0100 | { 56 61 66 71 76 81 86 91 96 101 105} | 30 | +| | 16 | 1101 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 17 | 1010 | { 0 5 10 15 20 25 30 35 40 45 49 111 116 121 126 131 136 141 146 151 156 160} | 30 | +| | 18 | 1001 | { 0 5 10 15 20 25 30 35 40 45 49 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| 5 (100MHz) | 19 | 11111 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161 167 172 177 182 187 192 197 202 207 212 216 223 228 233 238 243 248 253 258 263 268 272} | 30 | +| | 20 | 11110 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 21 | 11100 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161} | 30 | +| | 22 | 11000 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105} | 30 | +| | 23 | 10000 | { 0 5 10 15 20 25 30 35 40 45 49} | 30 | +| | 24 | 01110 | { 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 25 | 01100 | { 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161} | 30 | +| | 26 | 01000 | { 56 61 66 71 76 81 86 91 96 101 105} | 30 | +| | 27 | 00100 | { 112 117 122 127 132 137 142 147 152 157 161} | 30 | +| | 28 | 11011 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 167 172 177 182 187 192 197 202 207 212 216 223 228 233 238 243 248 253 258 263 268 272} | 30 | +| | 29 | 11010 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 30 | 11001 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 223 228 233 238 243 248 253 258 263 268 272} | 30 | +| | 31 | 10101 | { 0 5 10 15 20 25 30 35 40 45 49 112 117 122 127 132 137 142 147 152 157 161 223 228 233 238 243 248 253 258 263 268 272} | 30 | +| | 32 | 10110 | { 0 5 10 15 20 25 30 35 40 45 49 112 117 122 127 132 137 142 147 152 157 161 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 33 | 10100 | { 0 5 10 15 20 25 30 35 40 45 49 112 117 122 127 132 137 142 147 152 157 161} | 30 | +| | 34 | 10010 | { 0 5 10 15 20 25 30 35 40 45 49 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 35 | 10001 | { 0 5 10 15 20 25 30 35 40 45 49 223 228 233 238 243 248 253 258 263 268 272} | 30 | +| | 36 | 01010 | { 56 61 66 71 76 81 86 91 96 101 105 167 172 177 182 187 192 197 202 207 212 216} | 30 | +| | 37 | 11101 | { 0 5 10 15 20 25 30 35 40 45 49 56 61 66 71 76 81 86 91 96 101 105 112 117 122 127 132 137 142 147 152 157 161 223 228 233 238 243 248 253 258 263 268 272} | 30 | + +Here, for PSFCH RB location index, '0' means that RB index = 0. And, Bitmap '1' means the corresponding RB set is transmitted, and '0' means the corresponding RB set is not transmitted for wide band operation. + +Table 6.1.2.1.3.1-2 shows the MPR simulation results for the scenarios. + + + +| Scenario # | #1 | #2 | | | | | | | | | | | | | | | | | | +|------------|------|------|------|------|------|------|-------|------|------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| '20MHz' | 7.98 | 7.60 | | | | | | | | | | | | | | | | | | +| Scenario # | #3 | #4 | | | | | | | | | | | | | | | | | | +| '40MHz' | 9.39 | 7.94 | | | | | | | | | | | | | | | | | | +| Scenario # | #5 | #6 | #7 | #8 | #9 | | | | | | | | | | | | | | | +| '60MHz' | 9.65 | 9.05 | 7.67 | 7.43 | 9.31 | | | | | | | | | | | | | | | +| Scenario # | #10 | #11 | #12 | #13 | #14 | #15 | #16 | #17 | #18 | | | | | | | | | | | +| '80MHz' | 9.43 | 9.83 | 9.09 | 7.57 | 9.04 | 7.35 | 11.51 | 9.39 | 9.32 | | | | | | | | | | | +| Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | +| '100MHz' | 9.55 | | | | | | | | | | | | | | | | | | | + +Table 6.1.2.1.3.1-2: PSFCH MPR simulation results for SL-U power class 5 + +Table 6.1.2.1.3.1-3 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.2.1.3.1-3 : PSFCH MPR simulation results for SL-U power class 5** + +| | RB Allocation | | +|---------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 5 | Inner RB set configuration 5 | +| Contiguous sub-band RB sets | 9.83 | 9.04 | +| Non-contiguous sub-band RB sets | 11.51 | 9.22 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the PSFCH MPR for SL-U power class 5 can be proposed as Table 6.1.2.1.3.1-4 or Table 6.1.2.1.3.1-5 based on the simulation results when considering implementation margin. + +**Table 6.1.2.1.3.1-5 PSFCH MPR for SL-U UE power class 5** + +| | RB Allocation | | +|---------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 2 | Inner RB set configuration 2 | +| Contiguous sub-band RB sets | $\leq 11.5$ | $\leq 10.0$ | +| Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.0$ | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. + +**Table 6.1.2.1.3.1-6 PSFCH MPR for SL-U UE power class 5** + +| | RB Allocation | | +|--------------------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 2 | Inner RB set configuration 2 | +| Contiguous/Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.0$ | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. + +###### 6.1.2.1.3.2 Huawei simulation results (R4-2319500) + +The evaluation scenarios and MPR results for PSFCH are illustrated in Table 6.1.2.1.3.2-1 + +**Table 6.1.2.1.3.2-1 Evaluation scenarios and MPR for PSFCH on shared spectrum** + +| Case | BW/SCS | Common interlaced RB allocation/ RB index | Dedicated RB allocation/ RB index | MPR | +|------|--------|-------------------------------------------|-----------------------------------|-----| +| 1 | 20MHz/ | {1,6,11,16,21,26,31,36,41,46} | {50} | 10 | +| 2 | 30kHz | {1,6,11,16,21,26,31,36,41,46} | {48,49,50} | 9.7 | +| 3 | 20MHz/ | {1, 11, 21, 31, 41,51,61,71,81,91,101} | {105} | 10 | +| 4 | 15kHz | {1, 11, 21, 31, 41,51,61,71,81,91,101} | {103, 104,105} | 10 | + +![Figure 6.1.2.1.3.2-1 PSD and SEM for Case 1. The left plot shows the Power Spectral Density (PSD) in dB versus Frequency (MHz) from -60 to 60 MHz, with power levels ranging from -100 dB to 0 dB. The right plot shows the Spectral Emission Mask (SEM) in dB/MBW versus Frequency (MHz) from -40 to 40 MHz, comparing SEM specifications (red lines) with measurement results (blue line).](a85105fd544c64ef624aa45c72378647_img.jpg) + +Figure 6.1.2.1.3.2-1 PSD and SEM for Case 1. The left plot shows the Power Spectral Density (PSD) in dB versus Frequency (MHz) from -60 to 60 MHz, with power levels ranging from -100 dB to 0 dB. The right plot shows the Spectral Emission Mask (SEM) in dB/MBW versus Frequency (MHz) from -40 to 40 MHz, comparing SEM specifications (red lines) with measurement results (blue line). + +Figure 6.1.2.1.3.2-1 PSD and SEM for Case 1 + +![Figure 6.1.2.1.3.2-2 PSD and SEM for Case 3. The left plot shows the PSD in dB versus Frequency (MHz) from -60 to 60 MHz, with power levels ranging from -80 dB to 0 dB. The right plot shows the SEM in dB/MBW versus Frequency (MHz) from -40 to 40 MHz, comparing SEM specifications (red lines) with measurement results (blue line).](b30a71a63c0093c8f54a2a57b1f601bb_img.jpg) + +Figure 6.1.2.1.3.2-2 PSD and SEM for Case 3. The left plot shows the PSD in dB versus Frequency (MHz) from -60 to 60 MHz, with power levels ranging from -80 dB to 0 dB. The right plot shows the SEM in dB/MBW versus Frequency (MHz) from -40 to 40 MHz, comparing SEM specifications (red lines) with measurement results (blue line). + +Figure 6.1.2.1.3.2-2 PSD and SEM for Case 3 + +###### 6.1.2.1.2.2a Huawei's simulation results (R4-2319501) + +The updated scenarios with $P\_common < P\_dedicated$ is as follows. + +Table 6.1.2.1.2.2a-1 Evaluation scenarios and MPR for PSFCH on shared spectrum + +| Case | BW/SCS | Common interlaced RB allocation/ RB index | Dedicated RB allocation/ RB index | $P\_dedicated/P\_common$ (ratio/dB) | MPR | +|------|-----------------|-------------------------------------------|-----------------------------------|-------------------------------------|-----| +| 1 | 20MHz/
30kHz | {1,6,11,16,21,26,31,36,41,46} | {50} | 0dB | 10 | +| 2 | | | | 3dB | 9.5 | +| 3 | | | | 6dB | 9.1 | +| 4 | | {1,6,11,16,21,26,31,36,41,46} | {48,49,50} | 0dB | 9.7 | +| 5 | | | | 3dB | 9.5 | +| 6 | | | | 6dB | 9.1 | +| 7 | 20MHz/
15kHz | {1, 11, 21, 31, 41,51,61,71,81,91,101} | {105} | 0dB | 10 | +| 8 | | | | 3dB | 9.6 | +| 9 | | | | 6dB | 9.1 | +| 10 | | {1, 11, 21, 31, 41,51,61,71,81,91,101} | {103, 104,105} | 0dB | 10 | +| 11 | | | | 3dB | 9.6 | +| 12 | | | | 6dB | 9.1 | + +![Figure 6.1.2.1.2.2a-1: PSD and SEM for Case 1. The figure contains two plots. The left plot, titled 'PSD', shows Power(dB) on the y-axis (from -100 to 0) versus Freq(MHz) on the x-axis (from -60 to 60). The right plot shows Power(dB/MBW) on the y-axis (from -50 to 0) versus Freq(MHz) on the x-axis (from -40 to 40). This right plot includes three data series: 'SEM spec' (red line), 'SEM spec' (red line), and 'Measurement' (blue line). The measurement data shows a peak power density around 0 MHz, while the SEM spec lines define the regulatory limits.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +Figure 6.1.2.1.2.2a-1: PSD and SEM for Case 1. The figure contains two plots. The left plot, titled 'PSD', shows Power(dB) on the y-axis (from -100 to 0) versus Freq(MHz) on the x-axis (from -60 to 60). The right plot shows Power(dB/MBW) on the y-axis (from -50 to 0) versus Freq(MHz) on the x-axis (from -40 to 40). This right plot includes three data series: 'SEM spec' (red line), 'SEM spec' (red line), and 'Measurement' (blue line). The measurement data shows a peak power density around 0 MHz, while the SEM spec lines define the regulatory limits. + +**Figure 6.1.2.1.2.2a-1 PSD and SEM for Case 1**![Figure 6.1.2.1.2.2a-2: PSD for Case 3 and case 4. The figure contains two side-by-side plots, both titled 'PSD'. The left plot shows Power(dB) on the y-axis (from -120 to 20) versus Freq(MHz) on the x-axis (from -60 to 60). The right plot shows Power(dB) on the y-axis (from -120 to 20) versus Freq(MHz) on the x-axis (from -60 to 60). Both plots display the measured power spectral density for Case 3 and Case 4 respectively, showing similar peak power levels around 0 MHz.](198d076da025c516aec8122a6ab7db20_img.jpg) + +Figure 6.1.2.1.2.2a-2: PSD for Case 3 and case 4. The figure contains two side-by-side plots, both titled 'PSD'. The left plot shows Power(dB) on the y-axis (from -120 to 20) versus Freq(MHz) on the x-axis (from -60 to 60). The right plot shows Power(dB) on the y-axis (from -120 to 20) versus Freq(MHz) on the x-axis (from -60 to 60). Both plots display the measured power spectral density for Case 3 and Case 4 respectively, showing similar peak power levels around 0 MHz. + +**Figure 6.1.2.1.2.2a-2 PSD for Case 3 and case 4** + +### 6.1.3 UE additional maximum output power reduction for NR SL-U + +Based on the NR-U agreement for the additional spectrum emission mask in clause 6.5F.2.3 in TS38.101-1, RAN4 do not consider the additional spectrum emission mask. + +For the additional spurious emission requirements for SL-U, RAN4 will consider the NR-U additional spurious emission requirements in clause 6.5F.3.3 in TS38.101-1. + +To derive A-MPR requirements for SL-U operation in single CC, RAN4 will assume the basic simulation parameters and assumptions in section 6.1.2 and the additional spurious emission requirements in clause 6.5F.3.3 in TS38.101-1 will be considered. + +#### 6.1.3.1 A-MPR for SL-U with NS\_28 + +##### 6.1.3.1.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.3.1.1.1 Qualcomm's simulation results (R4-2316791) + +**Table 6.1.3.1.1.1-1: Simulation results for NS\_28 Allocation Full and partial allocations.** + +| NS_28 A-MPR | 20M | 20M | 40M | 40M | 60M | 60M | 80M | 80M | +|-------------|------|---------|------|---------|------|---------|------|---------| +| | Full | Partial | Full | Partial | Full | Partial | Full | Partial | +| QPSK | ≤8.0 | ≤8.1 | ≤7.7 | ≤8.0 | ≤7.1 | ≤7.8 | ≤6.9 | ≤7.8 | +| 16 QAM | ≤8.0 | ≤8.3 | ≤7.4 | ≤8.3 | ≤7.3 | ≤8.1 | ≤6.9 | ≤8.1 | +| 64 QAM | ≤8.1 | ≤8.7 | ≤7.4 | ≤8.7 | ≤7.3 | ≤8.2 | ≤7.0 | ≤8.2 | +| 256 QAM | ≤8.2 | ≤8.8 | ≤7.4 | ≤8.8 | ≤7.3 | ≤8.2 | ≤7.1 | ≤8.1 | + +The power class 5 PSSCH A-MPR in the tables should be considered in the discussion of MPR requirements. + +##### 6.1.3.1.2 A-MPR for S-SSB transmission + +##### 6.1.3.1.3 A-MPR for PSFCH transmission + +#### 6.1.3.2 A-MPR for SL-U with NS\_29 + +##### 6.1.3.2.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +##### 6.1.3.2.2 A-MPR for S-SSB transmission + +##### 6.1.3.2.3 A-MPR for PSFCH transmission + +#### 6.1.3.3 A-MPR for SL-U with NS\_30 + +##### 6.1.3.3.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.3.3.1.1 Qualcomm's simulation results (R4-2316791) + +**Table 6.1.3.3.1.1-1: Simulation results for NS\_30 Allocation Note 2 Full and partial allocations.** + +| NS_30 A-MPR Allocation Note2 | 20M | 20M | 40M | 40M | 60M | 60M | 80M | 80M | +|------------------------------|-------|---------|-------|---------|------|---------|------|---------| +| | Full | Partial | Full | Partial | Full | Partial | Full | Partial | +| QPSK | ≤10.7 | ≤10.9 | ≤10.4 | ≤11.0 | ≤9.3 | ≤10.3 | ≤9.1 | ≤10.4 | +| 16 QAM | ≤10.8 | ≤9.0 | ≤10.1 | ≤11.1 | ≤9.6 | ≤10.5 | ≤9.2 | ≤10.5 | +| 64 QAM | ≤10.9 | ≤11.4 | ≤10.1 | ≤11.4 | ≤9.6 | ≤10.6 | ≤9.3 | ≤10.6 | +| 256 QAM | ≤11.0 | ≤11.5 | ≤10.0 | ≤11.5 | ≤9.7 | ≤10.6 | ≤9.4 | ≤10.5 | + +**Table 6.1.3.3.1.1-2: Simulation results for NS\_30 Allocation Note 3 Full and partial allocations.** + +| NS_30 A-MPR Allocation Note3 | 20M | 20M | 40M | 40M | +|------------------------------|------|---------|------|---------| +| | Full | Partial | Full | Partial | +| QPSK | ≤8.3 | ≤8.4 | ≤5.9 | ≤6.2 | +| 16 QAM | ≤8.1 | ≤8.7 | ≤5.8 | ≤6.3 | +| 64 QAM | ≤8.3 | ≤9.0 | ≤5.8 | ≤6.3 | +| 256 QAM | ≤8.4 | ≤8.9 | ≤5.8 | ≤6.3 | + +The power class 5 PSSCH A-MPR in the tables should be considered in the discussion of MPR requirements. + +- 6.1.3.3.2 A-MPR for S-SSB transmission +- 6.1.3.3.3 A-MPR for PSFCH transmission +- 6.1.3.4 A-MPR for SL-U with NS\_31 + - 6.1.3.4.1 A-MPR for simultaneous PSSCH/PSCCH transmission + - 6.1.3.4.1.1 LG Electronics' simulation results (R4-2315542) + +Table 6.1.3.4.1.1-6 and Figure 6.1.3.4.1.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.4.1.1-1: NS\_31-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +| | | | | | | | | | | | | | | | | | | | | +|----------|------------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| '20MHz' | Scenario # | #1 | #7 | #2 | #8 | | | | | | | | | | | | | | | +| | 'QPSK' | 4.67 | 5.08 | 4.67 | 5.08 | | | | | | | | | | | | | | | +| | '16QAM' | 4.67 | 5.08 | 4.67 | 5.08 | | | | | | | | | | | | | | | +| | '64QAM' | 4.67 | 5.07 | 4.67 | 5.08 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.89 | 5.49 | | | | | | | | | | | | | | | +| '40MHz' | Scenario # | #3 | #9 | #13 | #30 | | | | | | | | | | | | | | | +| | 'QPSK' | 4.28 | 4.67 | 4.66 | 5.07 | | | | | | | | | | | | | | | +| | '16QAM' | 4.28 | 4.67 | 4.67 | 5.07 | | | | | | | | | | | | | | | +| | '64QAM' | 3.90 | 4.67 | 4.67 | 5.08 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.47 | 5.07 | | | | | | | | | | | | | | | +| '60MHz' | Scenario # | #4 | #10 | #14 | #31 | #15 | #32 | #16 | #33 | | | | | | | | | | | +| | 'QPSK' | 3.90 | 4.28 | 4.67 | 5.89 | 4.28 | 4.67 | 3.16 | 5.88 | | | | | | | | | | | +| | '16QAM' | 3.90 | 4.28 | 4.67 | 5.89 | 4.28 | 4.67 | 3.16 | 5.88 | | | | | | | | | | | +| | '64QAM' | 3.90 | 4.29 | 4.66 | 5.89 | 4.27 | 4.67 | 3.15 | 5.88 | | | | | | | | | | | +| | '256QAM' | 5.88 | 5.07 | 5.47 | 5.89 | 5.88 | 5.07 | 5.88 | 5.87 | | | | | | | | | | | +| '80MHz' | Scenario # | #5 | #11 | #17 | #34 | #18 | #35 | #19 | #36 | #20 | #37 | #21 | #38 | | | | | | | +| | 'QPSK' | 3.53 | 4.28 | 4.67 | 5.89 | 4.28 | 4.67 | 3.89 | 4.28 | 3.16 | 5.88 | 1.81 | 2.81 | | | | | | | +| | '16QAM' | 3.53 | 4.28 | 4.67 | 5.90 | 4.28 | 4.67 | 3.90 | 4.28 | 3.16 | 5.87 | 1.81 | 2.80 | | | | | | | +| | '64QAM' | 3.53 | 4.28 | 4.67 | 5.89 | 4.28 | 4.67 | 3.90 | 4.28 | 3.16 | 5.88 | 3.16 | 2.80 | | | | | | | +| | '256QAM' | 5.47 | 5.06 | 5.47 | 5.90 | 5.47 | 5.07 | 5.47 | 5.07 | 5.46 | 5.87 | 5.88 | 5.06 | | | | | | | +| '100MHz' | Scenario # | #6 | #12 | #22 | #39 | #23 | #40 | #24 | #41 | #25 | #42 | #26 | #43 | #27 | #44 | #28 | #45 | #29 | #46 | +| | 'QPSK' | 3.17 | 3.90 | 4.66 | 5.89 | 4.27 | 4.67 | 3.89 | 4.28 | 3.53 | 4.28 | 3.16 | 5.88 | 1.81 | 2.80 | 2.47 | 3.16 | 3.16 | 5.88 | +| | '16QAM' | 3.17 | 3.90 | 4.66 | 5.89 | 4.28 | 4.67 | 3.90 | 4.28 | 3.52 | 4.28 | 3.15 | 5.88 | 1.81 | 2.80 | 2.47 | 3.16 | 3.51 | 5.88 | +| | '64QAM' | 3.17 | 3.90 | 4.67 | 5.89 | 4.27 | 4.67 | 3.89 | 4.28 | 3.53 | 4.28 | 3.52 | 5.88 | 3.15 | 2.80 | 3.16 | 3.16 | 3.52 | 5.88 | +| | '256QAM' | 5.88 | 5.06 | 5.47 | 5.88 | 5.47 | 5.07 | 5.88 | 5.06 | 5.88 | 5.06 | 5.46 | 5.88 | 5.88 | 5.06 | 5.88 | 5.06 | 5.88 | 5.88 | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 7. The x-axis is 'Test Scenario #' from 1 to 46. Data points are shown for QPSK (circle), 16QAM (asterisk), 64QAM (diamond), and 256QAM (triangle).](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +The figure is a scatter plot titled "Tx Power Back Off for 1Tx Power class 5 SL-U". The y-axis is labeled "back off[dB]" and ranges from 0 to 7 in increments of 0.5. The x-axis is labeled "Test Scenario #" and ranges from 1 to 46. The plot shows data points for four different modulation schemes: QPSK (represented by a circle), 16QAM (represented by an asterisk), 64QAM (represented by a diamond), and 256QAM (represented by a triangle). The data points are scattered across the plot, with most values falling between 2.5 dB and 6.5 dB. The 256QAM data points are generally higher than the others, while the 64QAM data points are generally lower. + +| Test Scenario # | QPSK [dB] | 16QAM [dB] | 64QAM [dB] | 256QAM [dB] | +|-----------------|-----------|------------|------------|-------------| +| 1 | 4.8 | 4.8 | 4.8 | 5.5 | +| 2 | 4.8 | 4.8 | 4.8 | 5.5 | +| 3 | 4.4 | 4.4 | 4.0 | 5.5 | +| 4 | 4.0 | 4.0 | 4.0 | 5.5 | +| 5 | 3.6 | 3.6 | 3.6 | 5.5 | +| 6 | 3.2 | 3.2 | 3.2 | 5.5 | +| 7 | 5.1 | 5.1 | 5.1 | 5.1 | +| 8 | 5.1 | 5.1 | 5.1 | 5.1 | +| 9 | 4.7 | 4.7 | 4.7 | 5.2 | +| 10 | 4.3 | 4.3 | 4.3 | 5.1 | +| 11 | 4.3 | 4.3 | 4.3 | 5.1 | +| 12 | 3.9 | 3.9 | 3.9 | 5.1 | +| 13 | 4.7 | 4.7 | 4.7 | 5.5 | +| 14 | 4.7 | 4.7 | 4.7 | 5.5 | +| 15 | 4.3 | 4.3 | 4.3 | 5.5 | +| 16 | 3.6 | 3.6 | 3.6 | 5.5 | +| 17 | 4.7 | 4.7 | 4.7 | 5.5 | +| 18 | 4.3 | 4.3 | 4.3 | 5.5 | +| 19 | 3.9 | 3.9 | 3.9 | 5.5 | +| 20 | 3.6 | 3.6 | 3.6 | 5.5 | +| 21 | 2.2 | 2.2 | 3.2 | 5.5 | +| 22 | 4.7 | 4.7 | 4.7 | 5.5 | +| 23 | 4.3 | 4.3 | 4.3 | 5.5 | +| 24 | 3.9 | 3.9 | 3.9 | 5.5 | +| 25 | 3.6 | 3.6 | 3.6 | 5.5 | +| 26 | 3.6 | 3.6 | 3.6 | 5.5 | +| 27 | 2.5 | 2.5 | 3.2 | 5.5 | +| 28 | 2.5 | 2.5 | 2.9 | 5.5 | +| 29 | 3.6 | 3.6 | 3.6 | 5.9 | +| 30 | 5.1 | 5.1 | 5.1 | 5.1 | +| 31 | 6.3 | 6.3 | 6.3 | 6.3 | +| 32 | 4.7 | 4.7 | 4.7 | 5.1 | +| 33 | 6.3 | 6.3 | 6.3 | 6.3 | +| 34 | 6.3 | 6.3 | 6.3 | 6.3 | +| 35 | 4.7 | 4.7 | 4.7 | 5.1 | +| 36 | 4.3 | 4.3 | 4.3 | 5.1 | +| 37 | 6.3 | 6.3 | 6.3 | 6.3 | +| 38 | 3.2 | 3.2 | 3.2 | 5.1 | +| 39 | 6.3 | 6.3 | 6.3 | 6.3 | +| 40 | 4.7 | 4.7 | 4.7 | 5.1 | +| 41 | 4.3 | 4.3 | 4.3 | 5.1 | +| 42 | 4.3 | 4.3 | 4.3 | 5.1 | +| 43 | 6.3 | 6.3 | 6.3 | 6.3 | +| 44 | 2.8 | 3.2 | 3.2 | 5.1 | +| 45 | 3.2 | 3.2 | 3.2 | 5.1 | +| 46 | 6.3 | 6.3 | 6.3 | 6.3 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 7. The x-axis is 'Test Scenario #' from 1 to 46. Data points are shown for QPSK (circle), 16QAM (asterisk), 64QAM (diamond), and 256QAM (triangle). + +Figure 6.1.3.4.1.1-1: NS\_31-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.4.1.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration and Full/Partial RB allocation. + +**Table 6.1.3.4.1.1-2 : NS\_31-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| Pre-coding | Modulation | RB Allocation | | | | +|------------|------------|----------------------------|--------------|----------------------------|--------------| +| | | Outer RB set configuration | | Inner RB set configuration | | +| | | Full (dB) | Partial (dB) | Full(dB) | Partial (dB) | +| CP-OFDM | QPSK | 4.67 | 6.32 | 3.52 | 6.30 | +| | 16 QAM | 4.68 | 6.32 | 3.52 | 6.30 | +| | 64 QAM | 4.67 | 6.32 | 3.52 | 6.30 | +| | 256 QAM | 5.48 | 6.32 | 5.88 | 6.30 | + +The inner RB set configuration needs to be considered when defining the SL-U A-MPR requirements. + +Based on the results, Table 6.1.3.4.1.1-3 can be considered for NS\_31 A-MPR for SL-U UE power class 5. + +**Table 6.1.3.4.1.1-3. NS\_31 additional maximum power reduction (A-MPR) for SL-U UE power class 5** + +| Pre-coding | Modulation | RB Allocation (Note 4) | | | | RB Allocation (Note 3) | | +|------------|------------|-----------------------------------------|--------------|-----------------------------------------|--------------|------------------------|--| +| | | Outer RB set configuration 5 | | Inner RB set configuration 5 | | | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | | | +| CP-OFDM | QPSK | ≤ 5.5 | ≤ 6.5 | ≤ 4.5 | ≤ 6.5 | Follow SL-U MPR table | | +| | 16 QAM | ≤ 5.5 | ≤ 7.0 | ≤ 4.5 | ≤ 7.0 | | | +| | 64 QAM | ≤ 5.5 | ≤ 7.0 | ≤ 4.5 | ≤ 7.0 | | | +| | 256 QAM | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | | | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. +NOTE 2: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated or when not all transmitted sub-bands for wideband operation are transmitted. +NOTE 3: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to 5180, 5200, 5220, 5280, 5300, 5320, 5500, 5520, 5540, 5560, 5580, 5600, 5620, 5640, 5660, 5680, 5745, 5765, 5785, and 5805 MHz. +NOTE 4: Applicable for all valid channels and bandwidths other than those enumerated in NOTE 3. +NOTE 5: Contiguous outer sub-band configuration and contiguous inner sub-band configuration in Table 6.1.2.1.1.1-5 apply. + +###### 6.1.3.4.1.2 OPPO's simulation results (R4-2316119) + +For PSD = 10dBm/MHz: + +**Table 6.1.3.4.1.2-1 A-MPR for single CC PSD=10 dBm/MHz** + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 4.4 | 4.4 | 3.5 | 3.5 | 3.2 | 3.2 | 3.2 | 4.5 | 4.6 | 3.5 | 3.5 | 3.2 | 3.3 | 3.2 | +| 16QAM | 4.4 | 4.4 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 4.5 | 4.6 | 3.5 | 3.5 | 3.2 | 3.3 | 3.2 | +| 64QAM | 5.0 | 5.2 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 4.5 | 4.6 | 4.1 | 4.4 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 6.6 | 7.5 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +**Table 6.1.3.4.1.2-2 A-MPR for Wideband operation PSD=10 dBm/MHz** + +| | | | | | | | | | | | | | | | | | | +|--------|----|-----|-----|-----|------|------|------|------|------|------|------|------|------|------|------|------|------| +| Bitmap | 10 | 100 | 110 | 010 | 1100 | 1000 | 1110 | 0100 | 0110 | 1000 | 1100 | 1110 | 1100 | 0100 | 0110 | 0110 | 0010 | +|--------|----|-----|-----|-----|------|------|------|------|------|------|------|------|------|------|------|------|------| + +| | | | | | | | | | | | | | | | | | | | +|------------------------|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| Co
ntig
uou
s | QPSK | 3.5 | 3.0 | 3.0 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | +| | 16QAM | 3.5 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.7 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.7 | 3.6 | +| | 64QAM | 5.1 | 5.1 | 4.8 | 5.2 | 4.7 | 5.1 | 4.9 | 5.1 | 4.9 | 5.1 | 4.7 | 4.8 | 5.0 | 5.1 | 4.8 | 5.0 | 5.2 | +| | 256QAM | 7.4 | 7.5 | 7.7 | 8.5 | 7.3 | 7.4 | 8.0 | 7.5 | 8.5 | 7.4 | 7.3 | 7.6 | 8.0 | 7.4 | 7.7 | 8.5 | 8.5 | +| Inte
rlac
e | QPSK | 3.7 | 3.1 | 3.1 | 2.8 | 2.7 | 2.8 | 2.6 | 2.6 | 2.6 | 2.6 | 2.7 | 2.7 | 2.7 | 2.6 | 2.7 | 2.8 | 2.6 | +| | 16QAM | 3.7 | 3.1 | 3.1 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 3.0 | 2.8 | 2.9 | 3.0 | 3.0 | 2.8 | +| | 64QAM | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.0 | 4.1 | 4.2 | 4.1 | 4.1 | +| | 256QAM | 6.5 | 6.6 | 6.8 | 6.6 | 6.8 | 6.6 | 6.7 | 6.6 | 6.8 | 6.6 | 6.8 | 6.7 | 6.6 | 6.6 | 6.8 | 6.7 | 6.5 | + +For PSD = 7dBm/MHz: + +**Table 6.1.3.4.1.2-3 A-MPR for single CC PSD=7 dBm/MHz** + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 4.4 | 4.4 | 3.5 | 3.5 | 3.2 | 3.2 | 3.2 | 4.5 | 4.6 | 3.5 | 3.5 | 3.2 | 3.3 | 3.2 | +| 16QAM | 4.4 | 4.4 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 4.5 | 4.6 | 3.5 | 3.5 | 3.2 | 3.3 | 3.2 | +| 64QAM | 5.0 | 5.2 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 4.5 | 4.6 | 4.1 | 4.4 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 6.6 | 7.5 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +**Table 6.1.3.4.1.2-4 A-MPR for Wideband operation PSD=7 dBm/MHz** + +| | Bitmap | 10 | 10 | 11 | 01 | 11 | 10 | 11 | 01 | 01 | 10 | 11 | 11 | 01 | 01 | 01 | 00 | +|------------------------|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | | | 0 | 0 | 0 | 00 | 00 | 10 | 00 | 10 | 00 | 10 | 0 | 00 | 10 | 11 | 10 | +| Co
ntig
uou
s | QPSK | 3.5 | 3.0 | 3.0 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | +| | 16QAM | 3.5 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.7 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.6 | +| | 64QAM | 5.1 | 5.1 | 4.8 | 5.2 | 4.7 | 5.1 | 4.9 | 5.1 | 4.9 | 5.1 | 4.7 | 4.8 | 5.0 | 5.1 | 4.8 | 5.2 | +| | 256QAM | 7.4 | 7.5 | 7.7 | 8.5 | 7.3 | 7.4 | 8.0 | 7.5 | 8.5 | 7.4 | 7.3 | 7.6 | 8.0 | 7.4 | 7.7 | 8.5 | +| Inte
rlac
e | QPSK | 3.7 | 3.1 | 3.1 | 3.0 | 2.7 | 2.9 | 2.6 | 2.9 | 2.6 | 2.9 | 2.7 | 2.7 | 2.7 | 2.9 | 2.7 | 3.0 | +| | 16QAM | 3.7 | 3.1 | 3.1 | 3.0 | 3.0 | 3.0 | 3.0 | 3.0 | 3.0 | 3.0 | 3.0 | 2.8 | 3.0 | 3.0 | 3.0 | 3.0 | +| | 64QAM | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.0 | 4.1 | 4.2 | 4.1 | +| | 256QAM | 6.5 | 6.6 | 6.8 | 6.6 | 6.8 | 6.6 | 6.7 | 6.6 | 6.8 | 6.6 | 6.8 | 6.7 | 6.6 | 6.6 | 6.8 | 6.5 | + +For PSD = 4dBm/MHz: + +Table 6.1.3.4.1.2-5 A-MPR for single CC PSD=4 dBm/MHz + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 4.4 | 4.4 | 3.5 | 3.5 | 3.2 | 3.2 | 3.2 | 5.6 | 4.6 | 3.5 | 3.5 | 3.2 | 3.3 | 3.2 | +| 16QAM | 4.4 | 4.4 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 5.7 | 4.6 | 3.5 | 3.5 | 3.2 | 3.3 | 3.2 | +| 64QAM | 5.0 | 5.2 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 5.7 | 4.6 | 4.1 | 4.4 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 6.6 | 7.5 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +Table 6.1.3.4.1.2-6 A-MPR for NS\_02S Wideband operation PSD=4 dBm/MHz + +| | Bitmap | 10 | 100 | 110 | 010 | 1100 | 1000 | 1110 | 0100 | 0110 | 10000 | 11000 | 11100 | 11110 | 01000 | 01100 | 01110 | 00100 | +|------------|--------|-----|-----|-----|-----|------|------|------|------|------|-------|-------|-------|-------|-------|-------|-------|-------| +| Contiguous | QPSK | 3.5 | 3.5 | 3.0 | 3.6 | 2.8 | 3.5 | 2.8 | 3.5 | 2.8 | 3.5 | 2.8 | 2.8 | 2.8 | 3.5 | 2.8 | 2.8 | 3.6 | +| | 16QAM | 3.5 | 3.5 | 3.6 | 3.6 | 3.6 | 3.5 | 3.6 | 3.5 | 3.7 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.7 | 3.6 | +| | 64QAM | 5.1 | 5.1 | 4.8 | 5.2 | 4.7 | 5.1 | 4.9 | 5.1 | 4.9 | 5.1 | 4.7 | 4.8 | 5.0 | 5.1 | 4.8 | 5.0 | 5.2 | +| | 256QAM | 7.4 | 7.5 | 7.7 | 8.5 | 7.3 | 7.4 | 8.0 | 7.5 | 8.5 | 7.4 | 7.3 | 7.6 | 8.0 | 7.4 | 7.7 | 8.5 | 8.5 | +| Interlace | QPSK | 5.9 | 5.9 | 3.1 | 6.0 | 2.9 | 5.9 | 2.6 | 5.9 | 2.9 | 5.9 | 2.9 | 2.7 | 2.7 | 5.9 | 3.0 | 2.8 | 6.0 | +| | 16QAM | 6.0 | 6.0 | 3.1 | 6.0 | 3.0 | 6.0 | 3.0 | 6.0 | 3.0 | 5.9 | 3.0 | 3.0 | 2.8 | 6.0 | 3.0 | 3.0 | 6.0 | +| | 64QAM | 6.0 | 6.0 | 4.2 | 6.0 | 4.2 | 5.9 | 4.1 | 5.9 | 4.2 | 5.9 | 4.2 | 4.1 | 4.0 | 6.0 | 4.2 | 4.1 | 5.9 | +| | 256QAM | 6.5 | 6.6 | 6.8 | 6.6 | 6.8 | 6.6 | 6.7 | 6.6 | 6.8 | 6.6 | 6.8 | 6.7 | 6.6 | 6.6 | 6.8 | 6.7 | 6.5 | + +From the table 6.1.3.4.1.2-1 to table 6.1.3.4.1.2-6 above, it can be found that even though the PSD requirement is different from 10 to 7 to 4 dBm/MHz, the A-MPR simulation result for both single CC and wide-band operation are the same. The reason here is that the PSD requirement is not the dominate factor and it is the SEM and EVM for some of the 256QAM. The figure 6.1.3.4.1.2-1 and figure 6.1.3.4.1.2-2 below show the A-MPR. + +![Scatter plot titled 'NS_02S Single CC A-MPR' showing A-MPR values for different modulation schemes across 14 cases. The y-axis ranges from 0.0 to 10.0. The x-axis represents cases 1 to 14. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](a2b0b8d868ec4ee43d7d3f0961a12b5e_img.jpg) + +| Case | QPSK | 16QAM | 64QAM | 256QAM | +|------|------|-------|-------|--------| +| 1 | 4.4 | 4.4 | 5.0 | 8.8 | +| 2 | 4.4 | 4.4 | 5.2 | 8.6 | +| 3 | 3.5 | 3.7 | 5.1 | 8.6 | +| 4 | 3.5 | 3.7 | 5.0 | 8.8 | +| 5 | 3.2 | 3.7 | 5.2 | 8.6 | +| 6 | 3.2 | 3.7 | 5.1 | 8.5 | +| 7 | 3.2 | 3.6 | 5.1 | 8.7 | +| 8 | 5.6 | 5.7 | 5.7 | 6.6 | +| 9 | 4.6 | 4.6 | 4.6 | 7.5 | +| 10 | 3.5 | 3.5 | 4.1 | 7.6 | +| 11 | 3.5 | 3.5 | 4.4 | 7.9 | +| 12 | 3.2 | 3.2 | 4.1 | 6.6 | +| 13 | 3.3 | 3.3 | 3.9 | 6.5 | +| 14 | 3.2 | 3.2 | 4.0 | 6.8 | + +Scatter plot titled 'NS\_02S Single CC A-MPR' showing A-MPR values for different modulation schemes across 14 cases. The y-axis ranges from 0.0 to 10.0. The x-axis represents cases 1 to 14. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.4.1.2-1 Single CC A-MPR + +![Scatter plot titled 'NS_02S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across various subcarriers (15 to 48). The y-axis represents A-MPR from 0.0 to 9.0. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +Scatter plot titled 'NS\_02S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across various subcarriers (15 to 48). The y-axis represents A-MPR from 0.0 to 9.0. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.4.1.2-2 Wideband A-MPR + +Note : NS\_02S is equal to NS\_31. + +###### 6.1.3.4.1.3 Qualcomm’s simulation results (R4-2316791) + +We performed simulations for the full and partial allocations and computed the A-MPR for NS\_31. The results are shown in the tables below. + +Table 6.1.3.4.1.3: Simulation results for NS\_31 Full and partial allocations. + +| NS_31 A-MPR | 20M | | 40M | | 60M | | 80M | | +|-------------|-------|---------|-------|---------|-------|---------|-------|---------| +| | Full | Partial | Full | Partial | Full | Partial | Full | Partial | +| QPSK | ≤ 5.2 | ≤ 5.7 | ≤ 8.3 | ≤ 8.6 | ≤ 8.0 | NA | ≤ 8.0 | ≤ 8.1 | +| 16 QAM | ≤ 5.6 | ≤ 5.8 | ≤ 8.0 | ≤ 9.0 | ≤ 8.0 | NA | ≤ 8.0 | ≤ 8.3 | +| 64 QAM | ≤ 5.5 | ≤ 6.0 | ≤ 8.0 | ≤ 9.3 | ≤ 8.1 | NA | ≤ 8.1 | ≤ 8.5 | +| 256 QAM | ≤ 5.6 | ≤ 5.9 | ≤ 8.0 | ≤ 9.5 | ≤ 8.0 | NA | ≤ 8.0 | ≤ 8.5 | + +The power class 5 PSSCH A-MPR in the table should be considered in the discussion of MPR requirements. + +##### 6.1.3.4.2 A-MPR for S-SSB transmission + +###### 6.1.3.4.2.1 LG Electronics’ simulation results (R4-2315542) + +For NS\_31, Table 6.1.3.4.2.1-1 and Figure 6.1.3.4.2.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.4.2.1-1: NS\_31-S-SSB A-MPR simulation results for SL-U power class 5 + +| Scenario # | #1 | #2 | #3 | #4 | #5 | | | | | | | | | | | | | | | | +|------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|-------|------|------|------| +| '20MHz' | 9.43 | 7.90 | 6.82 | 6.81 | 6.08 | | | | | | | | | | | | | | | | +| Scenario # | #6 | #7 | #8 | #9 | #10 | #11 | | | | | | | | | | | | | | | +| '40MHz' | 11.05 | 8.92 | 7.45 | 9.20 | 8.17 | 7.11 | | | | | | | | | | | | | | | +| Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | | | | | | | | | | +| '60MHz' | 9.36 | 7.58 | 8.19 | 6.46 | 6.69 | 7.21 | 4.76 | 7.20 | 8.18 | 6.79 | | | | | | | | | | | +| Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | | | +| '80MHz' | 9.92 | 7.41 | 8.95 | 6.78 | 7.97 | 6.48 | 6.89 | 7.19 | 5.98 | 4.31 | 4.61 | 7.12 | 9.04 | 6.62 | 7.85 | 6.61 | 7.79 | 6.47 | | | +| Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | #55 | #56 | #57 | #58 | #59 | +| '100MHz' | 10.91 | 7.19 | 9.59 | 6.61 | 9.54 | 6.67 | 7.99 | 6.53 | 6.80 | 7.20 | 6.12 | 4.95 | 5.66 | 4.09 | 4.70 | 7.28 | 4.56 | 7.16 | 9.97 | 7.47 | +| Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | #71 | #72 | #73 | #74 | #75 | #76 | #77 | | | +| '100MHz' | 8.85 | 6.62 | 9.14 | 6.54 | 8.62 | 6.08 | 8.80 | 5.83 | 8.04 | 6.48 | 7.86 | 6.46 | 8.13 | 6.49 | 7.49 | 6.35 | 10.15 | 6.31 | | | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 12. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are shown for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds).](8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg) + +| Test Scenario # | 20MHz back off [dB] | 40MHz back off [dB] | 60MHz back off [dB] | +|-----------------|---------------------|---------------------|---------------------| +| 1 | 9.43 | | | +| 2 | 7.90 | | | +| 3 | 6.82 | | | +| 4 | 6.81 | | | +| 5 | 6.08 | | | +| 6 | | 11.05 | | +| 7 | | 8.92 | | +| 8 | | 7.45 | | +| 9 | | 9.20 | | +| 10 | | 8.17 | | +| 11 | | 7.21 | | +| 12 | | | 9.36 | +| 13 | | | 7.58 | +| 14 | | | 8.19 | +| 15 | | | 6.46 | +| 16 | | | 6.69 | +| 17 | | | 7.21 | +| 18 | | | 4.76 | +| 19 | | | 7.20 | +| 20 | | | 8.18 | +| 21 | | | 6.79 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 12. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are shown for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds). + +a. 20MHz, 40MHz, and 60MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 10.5 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by right-pointing triangles.](201de44da5d99899a8cf58eac2fa7bc9_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +80MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 22 | 10.0 | +| 23 | 7.5 | +| 24 | 9.0 | +| 25 | 6.8 | +| 26 | 8.0 | +| 27 | 6.5 | +| 28 | 7.0 | +| 29 | 7.2 | +| 30 | 6.0 | +| 31 | 4.5 | +| 32 | 4.8 | +| 33 | 7.2 | +| 34 | 9.0 | +| 35 | 6.5 | +| 36 | 7.8 | +| 37 | 6.5 | +| 38 | 7.8 | +| 39 | 6.5 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 10.5 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by right-pointing triangles. + +b. 80MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz bandwidth. The y-axis ranges from 0 to 11.5 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by upward-pointing triangles.](449d2799e97657d8fa5897b2e74a88bd_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +100MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 40 | 11.0 | +| 41 | 7.0 | +| 42 | 9.5 | +| 43 | 6.5 | +| 44 | 9.5 | +| 45 | 6.5 | +| 46 | 7.8 | +| 47 | 6.5 | +| 48 | 6.8 | +| 49 | 7.2 | +| 50 | 5.8 | +| 51 | 4.8 | +| 52 | 5.5 | +| 53 | 4.2 | +| 54 | 4.8 | +| 55 | 7.2 | +| 56 | 4.5 | +| 57 | 7.0 | +| 58 | 10.2 | +| 59 | 7.5 | +| 60 | 8.5 | +| 61 | 6.5 | +| 62 | 8.8 | +| 63 | 6.5 | +| 64 | 8.2 | +| 65 | 5.8 | +| 66 | 8.2 | +| 67 | 5.5 | +| 68 | 7.8 | +| 69 | 6.2 | +| 70 | 7.8 | +| 71 | 6.2 | +| 72 | 7.8 | +| 73 | 6.2 | +| 74 | 7.5 | +| 75 | 6.0 | +| 76 | 10.2 | +| 77 | 6.0 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz bandwidth. The y-axis ranges from 0 to 11.5 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by upward-pointing triangles. + +c. 100MHz + +Figure 6.1.3.4.2.1-13: NS\_31-S-SSB A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.4.2.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.4.2.1-2 : NS\_31 S-SSB A-MPR simulation results for SL-U power class 5** + +| | RB Allocation | | | | +|---------------------------------|----------------------------|------|----------------------------|------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous sub-band RB sets | 11.05 | 7.58 | 6.12 | 7.28 | +| Non-contiguous sub-band RB sets | 10.15 | 7.47 | 7.49 | 6.35 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the S-SSB A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.4.2.1-3 or Table 6.1.3.4.2.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.4.2.1-3: NS\_31 S-SSB A-MPR for SL-U UE power class 5** + +| | RB Allocation | | | | +|---------------------------------|----------------------------|-------------|----------------------------|-------------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous sub-band RB sets | $\leq 13.5$ | $\leq 10.0$ | $\leq 10.0$ | $\leq 10.0$ | +| Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.0$ | $\leq 10.0$ | $\leq 9.0$ | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to 5180, 5200, 5220, 5280, 5300, 5320, 5500, 5520, 5540, 5560, 5580, 5600, 5620, 5640, 5660, 5680, 5745, 5765, 5785, and 5805 MHz. +NOTE 3: Applicable for all valid channels and bandwidths other than those enumerated in NOTE 2. + +**Table 6.1.3.4.2.1-4: NS\_31 S-SSB A-MPR for SL-U UE power class 5** + +| | RB Allocation | | | | +|--------------------------------------------|----------------------------|-------------|----------------------------|-------------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous/Non-contiguous sub-band RB sets | $\leq 13.5$ | $\leq 10.0$ | $\leq 10.0$ | $\leq 10.0$ | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to 5180, 5200, 5220, 5280, 5300, 5320, 5500, 5520, 5540, 5560, 5580, 5600, 5620, 5640, 5660, 5680, 5745, 5765, 5785, and 5805 MHz. +NOTE 3: Applicable for all valid channels and bandwidths other than those enumerated in NOTE 2. + +##### 6.1.3.4.3 A-MPR for PSFCH transmission + +###### 6.1.3.4.3.1 LG Electronics' simulation results (R4-2315542 and R4-2321771) + +For NS\_31, Table 6.1.3.4.3.1-1 shows the A-MPR simulation results for the scenarios. + +**Table 6.1.3.4.3.1-1: NS\_31-PSFCH A-MPR simulation results for SL-U power class 5** + +| | | | | | | | | | | | | | | | | | | | | +|-------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| +| Scenario # | #1 | #2 | | | | | | | | | | | | | | | | | | +| '20MHz' | 8.38 | 8.31 | | | | | | | | | | | | | | | | | | +| Scenario # | #3 | #4 | | | | | | | | | | | | | | | | | | +| '40MHz' | 9.34 | 8.38 | | | | | | | | | | | | | | | | | | +| Scenario # | #5 | #6 | #7 | #8 | #9 | | | | | | | | | | | | | | | +| '60MHz' | 9.65 | 9.05 | 8.27 | 6.51 | 8.96 | | | | | | | | | | | | | | | +| Scenario # | #10 | #11 | #12 | #13 | #14 | #15 | #16 | #17 | #18 | | | | | | | | | | | +| '80MHz' | 9.43 | 9.83 | 9.05 | 8.28 | 8.56 | 6.86 | 9.82 | 9.00 | 8.95 | | | | | | | | | | | +| Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | +| '100MHz' | 9.55 | | | | | | | | | | | | | | | | | | | + +Table 6.1.3.4.3.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.4.3.1-2 : NS\_31 PSFCH A-MPR simulation results for SL-U power class 5** + +| | RB Allocation | | +|---------------------------------|----------------------------|----------------------------| +| | Outer RB set configuration | Inner RB set configuration | +| Contiguous sub-band RB sets | 9.83 | 8.56 | +| Non-contiguous sub-band RB sets | 9.82 | 9.63 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the PSFCH A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.4.3.1-3 or Table 6.1.3.4.3.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.4.3.1-3 NS\_31 PSFCH A-MPR for SL-U UE power class 5** + +| | RB Allocation | | +|---------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 2 | Inner RB set configuration 2 | +| Contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.5$ | +| Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 11.5$ | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. +NOTE 3: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to 5180, 5200, 5220, 5280, 5300, 5320, 5500, 5520, 5540, 5560, 5580, 5600, 5620, 5640, 5660, 5680, 5745, 5765, 5785, and 5805 MHz. +NOTE 4: Applicable for all valid channels and bandwidths other than those enumerated in NOTE 3. + +**Table 6.1.3.4.3.1-4 NS\_31 PSFCH A-MPR for SL-U UE power class 5** + +| | RB Allocation | | +|--------------------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 2 | Inner RB set configuration 2 | +| Contiguous/Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 11.5$ | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. +NOTE 3: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to 5180, 5200, 5220, 5280, 5300, 5320, 5500, 5520, 5540, 5560, 5580, 5600, 5620, 5640, 5660, 5680, 5745, 5765, 5785, and 5805 MHz. +NOTE 4: Applicable for all valid channels and bandwidths other than those enumerated in NOTE 3. + +#### 6.1.3.5 A-MPR for SL-U with NS\_53 + +##### 6.1.3.5.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.3.5.1.1 LG Electronics' simulation results (R4-2315542) + +For NS\_53, Table 6.1.3.5.1.1-9 and Figure 6.1.3.5.1.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.5.1.1-1: NS\_53-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +| | | | | | | | | | | | | | | | | | | | | +|----------|------------|------|-------|------|-------|------|------|------|-------|------|-------|------|-------|------|------|------|------|------|-------| +| '20MHz' | Scenario # | #1 | #7 | #2 | #8 | | | | | | | | | | | | | | | +| | 'QPSK' | 8.50 | 10.84 | 8.51 | 10.85 | | | | | | | | | | | | | | | +| | '16QAM' | 8.50 | 10.84 | 8.51 | 10.84 | | | | | | | | | | | | | | | +| | '64QAM' | 8.50 | 10.84 | 8.51 | 10.84 | | | | | | | | | | | | | | | +| | '256QAM' | 8.50 | 10.83 | 8.51 | 10.84 | | | | | | | | | | | | | | | +| '40MHz' | Scenario # | #3 | #9 | #13 | #30 | | | | | | | | | | | | | | | +| | 'QPSK' | 5.47 | 7.61 | 8.50 | 10.83 | | | | | | | | | | | | | | | +| | '16QAM' | 5.47 | 8.06 | 8.50 | 10.83 | | | | | | | | | | | | | | | +| | '64QAM' | 5.47 | 8.06 | 8.50 | 10.83 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 8.05 | 8.50 | 10.83 | | | | | | | | | | | | | | | +| '60MHz' | Scenario # | #4 | #10 | #14 | #31 | #15 | #32 | #16 | #33 | | | | | | | | | | | +| | 'QPSK' | 3.90 | 5.89 | 8.51 | 11.31 | 5.47 | 8.06 | 8.50 | 11.29 | | | | | | | | | | | +| | '16QAM' | 3.90 | 5.89 | 8.51 | 11.32 | 5.47 | 8.06 | 8.50 | 11.30 | | | | | | | | | | | +| | '64QAM' | 3.90 | 6.31 | 8.96 | 11.30 | 5.47 | 8.06 | 8.50 | 11.29 | | | | | | | | | | | +| | '256QAM' | 5.47 | 6.30 | 8.96 | 11.31 | 5.47 | 8.06 | 8.50 | 11.29 | | | | | | | | | | | +| '80MHz' | Scenario # | #5 | #11 | #17 | #34 | #18 | #35 | #19 | #36 | #20 | #37 | #21 | #38 | | | | | | | +| | 'QPSK' | 2.82 | 4.67 | 8.50 | 11.30 | 5.47 | 8.06 | 3.53 | 6.31 | 8.50 | 11.29 | 5.47 | 8.05 | | | | | | | +| | '16QAM' | 2.82 | 4.67 | 8.50 | 11.31 | 5.47 | 8.05 | 3.53 | 6.31 | 8.50 | 11.29 | 5.47 | 8.05 | | | | | | | +| | '64QAM' | 2.82 | 4.67 | 8.51 | 11.30 | 5.47 | 8.06 | 3.53 | 6.30 | 8.96 | 11.29 | 5.47 | 8.05 | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 8.96 | 11.31 | 5.47 | 8.06 | 5.47 | 6.31 | 8.50 | 11.29 | 5.47 | 8.05 | | | | | | | +| '100MHz' | Scenario # | #6 | #12 | #22 | #39 | #23 | #40 | #24 | #41 | #25 | #42 | #26 | #43 | #27 | #44 | #28 | #45 | #29 | #46 | +| | 'QPSK' | 3.17 | 3.90 | 8.50 | 11.30 | 5.47 | 8.06 | 3.52 | 6.30 | 2.47 | 4.67 | 8.50 | 11.30 | 5.47 | 8.05 | 3.52 | 5.88 | 8.50 | 11.30 | +| | '16QAM' | 3.17 | 3.90 | 8.50 | 11.32 | 5.47 | 8.06 | 3.52 | 6.31 | 2.47 | 5.06 | 8.50 | 11.29 | 5.47 | 8.05 | 3.52 | 6.30 | 8.96 | 11.30 | +| | '64QAM' | 3.17 | 3.90 | 8.96 | 11.31 | 5.47 | 8.06 | 3.53 | 6.31 | 2.81 | 4.67 | 8.50 | 11.29 | 5.47 | 8.05 | 3.52 | 5.88 | 8.96 | 11.29 | +| | '256QAM' | 5.47 | 5.07 | 8.51 | 11.32 | 5.47 | 8.06 | 5.47 | 6.30 | 5.47 | 5.06 | 8.50 | 11.30 | 5.46 | 8.05 | 5.47 | 6.30 | 8.96 | 11.29 | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 12. The x-axis is 'Test Scenario #' from 1 to 46. Data points for QPSK (red circle), 16QAM (blue asterisk), 64QAM (magenta diamond), and 256QAM (grey triangle) are plotted. The plot shows varying back-off values across scenarios, with 256QAM generally requiring lower back-off than other modulations in some scenarios.](730b6615db6d402580db1024a7f4e163_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +Legend: + +- QPSK (Red Circle) +- 16QAM (Blue Asterisk) +- 64QAM (Magenta Diamond) +- 256QAM (Grey Triangle) + +| Test Scenario # | QPSK [dB] | 16QAM [dB] | 64QAM [dB] | 256QAM [dB] | +|-----------------|-----------|------------|------------|-------------| +| 1 | 8.2 | 8.2 | 8.2 | 8.2 | +| 2 | 8.2 | 8.2 | 8.2 | 8.2 | +| 3 | 5.2 | 5.2 | 5.2 | 5.2 | +| 4 | 3.8 | 3.8 | 3.8 | 5.2 | +| 5 | 2.5 | 2.5 | 2.5 | 5.2 | +| 6 | 2.8 | 2.8 | 2.8 | 5.2 | +| 7 | 10.5 | 10.5 | 10.5 | 10.5 | +| 8 | 10.5 | 10.5 | 10.5 | 10.5 | +| 9 | 7.2 | 7.8 | 7.8 | 7.8 | +| 10 | 5.8 | 5.8 | 5.8 | 6.2 | +| 11 | 4.2 | 4.2 | 4.2 | 4.8 | +| 12 | 3.8 | 3.8 | 3.8 | 4.8 | +| 13 | 8.2 | 8.2 | 8.2 | 8.2 | +| 14 | 8.8 | 8.8 | 8.8 | 8.8 | +| 15 | 5.2 | 5.2 | 5.2 | 5.2 | +| 16 | 8.2 | 8.2 | 8.2 | 8.2 | +| 17 | 8.2 | 8.2 | 8.2 | 8.8 | +| 18 | 5.2 | 5.2 | 5.2 | 5.2 | +| 19 | 3.2 | 3.2 | 3.2 | 5.2 | +| 20 | 8.2 | 8.2 | 8.8 | 8.2 | +| 21 | 5.2 | 5.2 | 5.2 | 5.2 | +| 22 | 8.2 | 8.2 | 8.8 | 8.2 | +| 23 | 5.2 | 5.2 | 5.2 | 5.2 | +| 24 | 3.2 | 3.2 | 3.2 | 5.2 | +| 25 | 2.2 | 2.2 | 2.8 | 5.2 | +| 26 | 8.2 | 8.2 | 8.2 | 8.2 | +| 27 | 5.2 | 5.2 | 5.2 | 5.2 | +| 28 | 3.2 | 3.2 | 3.2 | 5.2 | +| 29 | 8.2 | 8.2 | 8.2 | 8.8 | +| 30 | 10.5 | 10.5 | 10.5 | 10.5 | +| 31 | 11.2 | 11.2 | 11.2 | 11.2 | +| 32 | 7.8 | 7.8 | 7.8 | 7.8 | +| 33 | 11.2 | 11.2 | 11.2 | 11.2 | +| 34 | 11.2 | 11.2 | 11.2 | 11.2 | +| 35 | 7.8 | 7.8 | 7.8 | 7.8 | +| 36 | 6.2 | 6.2 | 6.2 | 6.2 | +| 37 | 11.2 | 11.2 | 11.2 | 11.2 | +| 38 | 11.2 | 11.2 | 11.2 | 11.2 | +| 39 | 7.8 | 7.8 | 7.8 | 7.8 | +| 40 | 7.8 | 7.8 | 7.8 | 7.8 | +| 41 | 6.2 | 6.2 | 6.2 | 6.2 | +| 42 | 4.2 | 4.8 | 4.8 | 4.8 | +| 43 | 11.2 | 11.2 | 11.2 | 11.2 | +| 44 | 7.8 | 7.8 | 7.8 | 7.8 | +| 45 | 5.8 | 6.2 | 6.2 | 6.2 | +| 46 | 11.2 | 11.2 | 11.2 | 11.2 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 12. The x-axis is 'Test Scenario #' from 1 to 46. Data points for QPSK (red circle), 16QAM (blue asterisk), 64QAM (magenta diamond), and 256QAM (grey triangle) are plotted. The plot shows varying back-off values across scenarios, with 256QAM generally requiring lower back-off than other modulations in some scenarios. + +Figure 6.1.3.5.1.1-1: NS\_53-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.5.1.1-2 shows the maximum value of simulation results considering Full/Partial RB allocation. + +**Table 6.1.3.5.1.1-2 : NS\_53-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| CP-OFDM | QPSK | 8.51 | 11.31 | 5.47 | 8.06 | 3.90 | 6.31 | 2.82 | 4.67 | 3.17 | 3.90 | +| | 16 QAM | 8.96 | 11.32 | 5.47 | 8.06 | 3.90 | 6.31 | 2.82 | 5.06 | 3.17 | 3.90 | +| | 64 QAM | 8.96 | 11.31 | 5.47 | 8.06 | 3.90 | 6.31 | 2.82 | 4.67 | 3.17 | 3.90 | +| | 256 QAM | 8.96 | 11.32 | 5.47 | 8.06 | 5.47 | 6.31 | 5.47 | 5.07 | 5.47 | 5.07 | + +Table 6.1.3.5.1.1-3 can be considered for NS\_53 A-MPR for SL-U UE power class 5. + +**Table 6.1.3.5.1.1-3. NS\_53 additional maximum power reduction (A-MPR) for SL-U UE power class 5** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| CP-OFDM | QPSK | ≤ 9.0 | ≤ 12.0 | ≤ 6.5 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 4.0 | ≤ 5.5 | ≤ 4.0 | ≤ 4.5 | +| | 16 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.5 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 4.0 | ≤ 5.5 | ≤ 4.0 | ≤ 4.5 | +| | 64 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.5 | ≤ 8.5 | ≤ 5.5 | ≤ 6.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 7.0 | ≤ 8.5 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. + +NOTE 2: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +###### 6.1.3.5.1.2 OPPO's simulation results (R4-2316119) + +Case 1,2,8,9 are for 20MHz; 3,4,10,11 are for 40MHz; 5,12 are for 60MHz; 6,13 are for 80MHz and 7,14 are for 100MHz. + +**Table 6.1.3.5.1.2-1 A-MPR for single CC** + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|---------------|-----|-----|-----|-----|-----|-----|-----|-----|------|-----|-----|-----|-----|-----| +| QPSK | 8.4 | 8.6 | 5.4 | 5.5 | 3.8 | 3.2 | 3.2 | 9.8 | 10.9 | 6.6 | 7.8 | 6.0 | 4.5 | 3.9 | +| 16QAM | 8.4 | 8.6 | 5.4 | 5.6 | 3.9 | 3.9 | 3.8 | 9.8 | 10.9 | 6.6 | 7.8 | 6.0 | 4.5 | 3.9 | +| 64QAM | 8.3 | 8.5 | 5.5 | 5.4 | 5.6 | 5.5 | 5.5 | 9.8 | 10.9 | 6.7 | 7.8 | 6.1 | 4.6 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 9.8 | 10.9 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +Table 6.1.3.5.1.2-2 A-MPR for Wideband + +| | Bitmap | 10 | 100 | 010 | 1000 | 0100 | 10000 | 01000 | 00100 | 110 | 1100 | 0110 | 11000 | 01100 | 1110 | 11100 | 01110 | 11110 | +|------------|--------|------|------|------|------|------|-------|-------|-------|-----|------|------|-------|-------|------|-------|-------|-------| +| Contiguous | QPSK | 8.5 | 8.5 | 8.6 | 8.5 | 8.5 | 8.5 | 8.5 | 8.6 | 5.8 | 5.5 | 5.5 | 5.5 | 5.8 | 4.0 | 4.0 | 4.0 | 2.8 | +| | 16QAM | 8.5 | 8.5 | 8.6 | 8.5 | 8.5 | 8.5 | 8.5 | 8.6 | 5.8 | 5.6 | 5.6 | 5.6 | 5.7 | 4.0 | 4.0 | 4.0 | 3.6 | +| | 64QAM | 8.5 | 8.5 | 8.6 | 8.5 | 8.5 | 8.5 | 8.5 | 8.5 | 5.8 | 5.5 | 5.5 | 5.5 | 5.7 | 4.9 | 4.8 | 5.0 | 5.0 | +| | 256QAM | 8.5 | 8.5 | 8.6 | 8.5 | 8.6 | 8.6 | 8.5 | 8.6 | 7.7 | 7.3 | 7.3 | 7.3 | 8.5 | 8.0 | 7.6 | 8.5 | 8.0 | +| Interlace | QPSK | 10.9 | 10.9 | 11.0 | 10.9 | 10.9 | 10.9 | 10.9 | 11.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 6.2 | 6.4 | 6.4 | 5.1 | +| | 16QAM | 11.0 | 11.0 | 11.0 | 11.0 | 11.0 | 11.0 | 11.0 | 11.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 6.3 | 6.5 | 6.3 | 5.1 | +| | 64QAM | 11.0 | 11.0 | 11.0 | 10.9 | 11.0 | 10.9 | 11.0 | 10.9 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 6.3 | 6.4 | 6.3 | 5.2 | +| | 256QAM | 11.0 | 11.0 | 11.0 | 10.9 | 11.0 | 10.9 | 11.0 | 11.0 | 8.1 | 8.0 | 8.0 | 8.0 | 8.0 | 6.7 | 6.7 | 6.7 | 6.6 | + +![Scatter plot titled 'NS_03S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 subcarriers. The y-axis represents A-MPR from 0 to 12. The x-axis represents subcarriers from 1 to 14. Data points are colored by modulation: blue for QPSK, orange for 16QAM, grey for 64QAM, and yellow for 256QAM.](411bc48fd105531df2c427c06acd6aaa_img.jpg) + +| Subcarrier | QPSK | 16QAM | 64QAM | 256QAM | +|------------|------|-------|-------|--------| +| 1 | 8.5 | | | 8.5 | +| 2 | 8.5 | | | | +| 3 | 5.5 | | | 8.5 | +| 4 | 5.5 | 5.5 | | 8.5 | +| 5 | 4.0 | | 5.5 | 8.5 | +| 6 | 3.5 | 4.0 | 5.5 | 8.5 | +| 7 | 3.5 | 4.0 | 5.5 | 8.5 | +| 8 | 10.0 | | | | +| 9 | 11.0 | | | | +| 10 | 6.5 | | | 7.5 | +| 11 | 8.0 | | | 8.0 | +| 12 | 6.0 | | | 6.5 | +| 13 | 4.5 | | | 6.5 | +| 14 | 4.0 | | | 6.5 | + +Scatter plot titled 'NS\_03S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 subcarriers. The y-axis represents A-MPR from 0 to 12. The x-axis represents subcarriers from 1 to 14. Data points are colored by modulation: blue for QPSK, orange for 16QAM, grey for 64QAM, and yellow for 256QAM. + +Figure 6.1.3.5.1.2-1 Single CC A-MPR + +![Scatter plot titled 'NS_03S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across various subcarriers (15 to 48).](e0113695dbf148bf5ec34354e544414b_img.jpg) + +The figure is a scatter plot titled "NS\_03S Wideband A-MPR". The x-axis represents subcarriers from 15 to 48. The y-axis represents the A-MPR value from 0 to 12. The legend indicates four modulation schemes: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). The data points show that for most subcarriers, the A-MPR is around 8-9 for QPSK and 256QAM, and around 6 for 16QAM and 64QAM. There is a significant increase in A-MPR for all schemes between subcarriers 32 and 39, reaching values between 10 and 11. + +Scatter plot titled 'NS\_03S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across various subcarriers (15 to 48). + +Figure 6.1.3.5.1.2-2 Wide-band A-MPR + +6.1.3.5.1.3 Qualcomm's simulation results (R4-2316791) + +Table 6.1.3.5.1.3-1: Simulation results for NS\_53 Full and partial allocations. + +| NS_53 A-MPR | 20M | | 40M | | 60M | | 80M | | +|-------------|------|---------|------|---------|------|---------|------|---------| +| | Full | Partial | Full | Partial | Full | Partial | Full | Partial | +| QPSK | ≤7.5 | ≤7.6 | ≤7.0 | ≤7.3 | ≤6.7 | ≤7.4 | ≤6.4 | ≤7.4 | +| 16 QAM | ≤7.5 | ≤7.8 | ≤6.9 | ≤7.4 | ≤6.8 | ≤7.6 | ≤6.4 | ≤7.6 | +| 64 QAM | ≤7.5 | ≤8.0 | ≤7.0 | ≤7.6 | ≤6.8 | ≤7.8 | ≤6.5 | ≤7.8 | +| 256 QAM | ≤7.5 | ≤8.0 | ≤7.0 | ≤7.5 | ≤6.8 | ≤7.7 | ≤6.6 | ≤7.7 | + +The power class 5 PSSCH A-MPR in the table should be considered in the discussion of MPR requirements. + +##### 6.1.3.5.2 A-MPR for S-SSB transmission + +6.1.3.5.2.1 LG Electronics' simulation results (R4-2315542) + +For NS\_53, Table 6.1.3.5.2.1-1 and Figure 6.1.3.5.2.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.5.2.1-1: NS\_53-S-SSB A-MPR simulation results for SL-U power class 5 + +| Scenario # | #1 | #2 | #3 | #4 | #5 | | | | | | | | | | | | | | | | +|------------|-------|-------|-------|------|-------|-------|------|-------|------|-------|------|-------|------|------|------|-------|-------|-------|-------|------| +| '20MHz' | 9.43 | 11.16 | 15.09 | 9.13 | 12.21 | | | | | | | | | | | | | | | | +| Scenario # | #6 | #7 | #8 | #9 | #10 | #11 | | | | | | | | | | | | | | | +| '40MHz' | 11.05 | 8.92 | 12.11 | 9.20 | 11.24 | 15.09 | | | | | | | | | | | | | | | +| Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | | | | | | | | | | +| '60MHz' | 9.36 | 7.58 | 8.19 | 9.19 | 9.12 | 12.22 | 9.09 | 12.22 | 8.18 | 9.12 | | | | | | | | | | | +| Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | | | +| '80MHz' | 9.92 | 7.32 | 8.95 | 7.43 | 7.99 | 9.19 | 9.19 | 12.23 | 6.36 | 9.21 | 9.22 | 12.13 | 9.03 | 7.47 | 8.09 | 9.10 | 8.31 | 9.20 | | | +| Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | #55 | #56 | #57 | #58 | #59 | +| '100MHz' | 11.13 | 7.20 | 9.76 | 6.37 | 9.55 | 7.44 | 8.15 | 9.21 | 9.24 | 12.28 | 6.04 | 7.38 | 6.28 | 9.18 | 9.22 | 12.19 | 9.13 | 12.22 | 10.26 | 7.48 | +| Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | #71 | #72 | #73 | #74 | #75 | #76 | #77 | | | +| '100MHz' | 9.47 | 7.36 | 8.74 | 7.40 | 8.46 | 7.45 | 8.90 | 7.44 | 8.10 | 9.19 | 8.09 | 9.14 | 8.08 | 9.29 | 7.62 | 9.18 | 10.07 | 6.45 | | | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 15. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds).](fa8c6c258373e37982dca686af4c0101_img.jpg) + +| Test Scenario # | 20MHz back off [dB] | 40MHz back off [dB] | 60MHz back off [dB] | +|-----------------|---------------------|---------------------|---------------------| +| 1 | 9.43 | | | +| 2 | 11.16 | | | +| 3 | 15.09 | | | +| 4 | 9.13 | | | +| 5 | 12.21 | | | +| 6 | | 11.05 | | +| 7 | | 8.92 | | +| 8 | | 12.11 | | +| 9 | | 9.20 | | +| 10 | | 11.24 | | +| 11 | | 15.09 | | +| 12 | | | 9.36 | +| 13 | | | 7.58 | +| 14 | | | 8.19 | +| 15 | | | 9.19 | +| 16 | | | 9.12 | +| 17 | | | | +| 18 | | | | +| 19 | | | | +| 20 | | | | +| 21 | | | | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 15. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds). + +a. 20MHz, 40MHz, and 60MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by open triangles.](c742b64169a38a7f3f990172019878c8_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +80MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 23 | 7 | +| 24 | 8.5 | +| 25 | 7 | +| 26 | 7.5 | +| 27 | 8.5 | +| 28 | 8.5 | +| 29 | 11 | +| 30 | 6 | +| 31 | 8.5 | +| 32 | 8.5 | +| 33 | 11 | +| 34 | 8.5 | +| 35 | 7 | +| 36 | 7.5 | +| 37 | 8.5 | +| 38 | 8 | +| 39 | 9 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by open triangles. + +b. 80MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by open triangles.](808fbf3058e19e39757a0a84c7796059_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +100MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 40 | 10.5 | +| 41 | 7 | +| 42 | 9 | +| 43 | 6 | +| 44 | 9 | +| 45 | 7 | +| 46 | 8 | +| 47 | 9 | +| 48 | 9 | +| 49 | 11.5 | +| 50 | 6 | +| 51 | 7 | +| 52 | 6 | +| 53 | 9 | +| 54 | 9 | +| 55 | 11.5 | +| 56 | 9 | +| 57 | 11.5 | +| 58 | 10 | +| 59 | 7 | +| 60 | 9 | +| 61 | 7 | +| 62 | 8 | +| 63 | 7 | +| 64 | 8 | +| 65 | 7 | +| 66 | 9 | +| 67 | 7 | +| 68 | 8 | +| 69 | 9 | +| 70 | 8 | +| 71 | 9 | +| 72 | 8 | +| 73 | 9 | +| 74 | 7 | +| 75 | 9 | +| 76 | 10 | +| 77 | 6 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by open triangles. + +c. 100MHz + +Figure 6.1.3.5.2.1-1: NS\_53 S-SSB A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.5.2.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.5.2.1-2 : NS\_53 S-SSB A-MPR simulation results for SL-U power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|-----------------------------|---------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous | 11.16 | 15.09 | 11.05 | 15.09 | 9.36 | 12.22 | 9.92 | 12.23 | 11.13 | 11.13 | +| Non-contiguous | - | - | - | - | 8.18 | 9.12 | 9.03 | 9.20 | 10.26 | 9.29 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the S-SSB A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.5.2.1-3 or Table 6.1.3.5.2.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.5.2.1-3: NS\_53 S-SSB A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation / (dB) | | | | | | | | | | +|-----------------------------|----------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous | ≤13.5 | ≤17.5 | ≤13.5 | ≤17.5 | ≤13.5 | ≤14.5 | ≤13.5 | ≤14.5 | ≤13.5 | ≤13.5 | +| Non-contiguous | N/A | N/A | N/A | N/A | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +**Table 6.1.3.5.2.1-4: NS\_53 S-SSB A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|-----------------------------|---------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous/Non-contiguous | ≤13.5 | ≤17.5 | ≤13.5 | ≤17.5 | ≤13.5 | ≤14.5 | ≤13.5 | ≤14.5 | ≤13.5 | ≤13.5 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +##### 6.1.3.5.3 A-MPR for PSFCH transmission + +###### 6.1.3.5.3.1 LG Electronics' simulation results (R4-2315542 and R4-2321771) + +For NS\_53, Table 6.1.3.5.3.1-1 shows the A-MPR simulation results for the scenarios. + +**Table 6.1.3.5.3.1-1: NS\_53-PSFCH A-MPR simulation results for SL-U power class 5** + +| Scenario # | #1 | #2 | | | | | | | | | | | | | | | | | | +|------------|------|------|------|------|------|------|------|------|------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| '20MHz' | 7.98 | 7.60 | | | | | | | | | | | | | | | | | | +| Scenario # | #3 | #4 | | | | | | | | | | | | | | | | | | +| '40MHz' | 9.32 | 7.94 | | | | | | | | | | | | | | | | | | +| Scenario # | #5 | #6 | #7 | #8 | #9 | | | | | | | | | | | | | | | +| '60MHz' | 9.65 | 9.05 | 7.67 | 6.51 | 8.96 | | | | | | | | | | | | | | | +| Scenario # | #10 | #11 | #12 | #13 | #14 | #15 | #16 | #17 | #18 | | | | | | | | | | | +| '80MHz' | 9.43 | 9.83 | 9.01 | 7.57 | 8.56 | 6.86 | 9.82 | 9.00 | 8.95 | | | | | | | | | | | +| Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | +| '100MHz' | 9.55 | | | | | | | | | | | | | | | | | | | + +Table 6.1.3.5.3.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.5.3.1-2 : NS\_53 PSFCH A-MPR simulation results for SL-U power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|----------------------|---------------------------------------------------------|-------|-------|-------|--------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous | 7.98 | 9.32 | 9.83 | 9.43 | 9.55 | +| Non-contiguous | N/A | 9.0 | 9.82 | 9.63 | N/A | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the PSFCH A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.5.3.1-3 or Table 6.1.3.5.3.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.5.3.1-3 NS\_53 PSFCH A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|----------------------|---------------------------------------------------------|-------------|-------------|-------------|-------------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | +| Non-contiguous | N/A | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | N/A | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +**Table 6.1.3.5.3.1-4 NS\_53 PSFCH A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|---------------------------|---------------------------------------------------------|-------------|-------------|-------------|-------------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous/Non-contiguous | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +#### 6.1.3.6 A-MPR for SL-U with NS\_54 + +##### 6.1.3.6.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +##### 6.1.3.6.2 A-MPR for S-SSB transmission + +##### 6.1.3.6.3 A-MPR for PSFCH transmission + +#### 6.1.3.7 A-MPR for SL-U with NS\_58 + +##### 6.1.3.7.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.3.7.1.1 LG Electronics' simulation results (R4-2315542) + +For NS\_58, Table 6.1.3.7.1.1-1 and Figure 6.1.3.7.1.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.7.1.1-1: NS\_58-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +| | | | | | | | | | | | | | | | | | | | | +|----------|------------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| '20MHz' | Scenario # | #1 | #7 | #2 | #8 | | | | | | | | | | | | | | | +| | 'QPSK' | 2.48 | 2.83 | 2.15 | 2.50 | | | | | | | | | | | | | | | +| | '16QAM' | 2.48 | 2.83 | 2.15 | 2.49 | | | | | | | | | | | | | | | +| | '64QAM' | 2.82 | 2.83 | 3.18 | 2.49 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.48 | 5.09 | | | | | | | | | | | | | | | +| '40MHz' | Scenario # | #3 | #9 | #13 | #30 | | | | | | | | | | | | | | | +| | 'QPSK' | 2.48 | 2.82 | 2.81 | 2.82 | | | | | | | | | | | | | | | +| | '16QAM' | 2.48 | 2.82 | 2.81 | 2.82 | | | | | | | | | | | | | | | +| | '64QAM' | 2.82 | 2.82 | 2.81 | 2.82 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.47 | 5.07 | | | | | | | | | | | | | | | +| '60MHz' | Scenario # | #4 | #10 | #14 | #31 | #15 | #32 | #16 | #33 | | | | | | | | | | | +| | 'QPSK' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.48 | 2.13 | 0.10 | | | | | | | | | | | +| | '16QAM' | 2.48 | 2.48 | 2.14 | 2.47 | 2.47 | 2.47 | 2.13 | 0.36 | | | | | | | | | | | +| | '64QAM' | 3.17 | 2.48 | 3.16 | 2.48 | 3.16 | 2.48 | 3.16 | 2.12 | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.47 | 5.08 | 5.47 | 5.07 | 5.88 | 5.06 | | | | | | | | | | | +| '80MHz' | Scenario # | #5 | #11 | #17 | #34 | #18 | #35 | #19 | #36 | #20 | #37 | #21 | #38 | | | | | | | +| | 'QPSK' | 2.48 | 2.48 | 2.14 | 2.15 | 2.47 | 2.48 | 2.47 | 2.48 | 2.46 | 0.10 | 2.13 | 0.00 | | | | | | | +| | '16QAM' | 2.48 | 2.48 | 2.14 | 2.15 | 2.47 | 2.47 | 2.47 | 2.48 | 2.46 | 0.36 | 2.13 | 0.37 | | | | | | | +| | '64QAM' | 2.82 | 2.48 | 3.16 | 2.15 | 2.81 | 2.48 | 3.16 | 2.48 | 3.16 | 2.12 | 3.16 | 2.46 | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.47 | 5.07 | 5.47 | 5.06 | 5.47 | 5.07 | 5.46 | 5.06 | 5.47 | 5.06 | | | | | | | +| '100MHz' | Scenario # | #6 | #12 | #22 | #39 | #23 | #40 | #24 | #41 | #25 | #42 | #26 | #43 | #27 | #44 | #28 | #45 | #29 | #46 | +| | 'QPSK' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.48 | 2.47 | 2.48 | 2.47 | 2.47 | 2.13 | 0.10 | 2.46 | 0.00 | 2.47 | 1.20 | 2.13 | 0.10 | +| | '16QAM' | 2.48 | 2.48 | 2.14 | 2.48 | 2.47 | 2.48 | 2.47 | 2.47 | 2.47 | 2.48 | 2.13 | 0.36 | 2.46 | 0.63 | 2.47 | 1.20 | 2.13 | 0.36 | +| | '64QAM' | 2.82 | 2.48 | 3.17 | 2.48 | 3.16 | 2.47 | 3.16 | 2.47 | 2.81 | 2.48 | 3.15 | 2.12 | 3.16 | 2.46 | 3.16 | 2.47 | 3.16 | 2.12 | +| | '256QAM' | 5.47 | 5.06 | 5.47 | 5.07 | 5.47 | 5.07 | 5.47 | 5.06 | 5.47 | 5.06 | 5.46 | 5.06 | 5.46 | 5.06 | 5.47 | 5.06 | 5.46 | 5.05 | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 6.5. The x-axis is 'Test Scenario #' from 1 to 46. Data series for QPSK (red circles), 16QAM (blue asterisks), 64QAM (magenta diamonds), and 256QAM (black triangles) are plotted. 256QAM stays around 5.5 dB, while others fluctuate between 0.5 and 3.5 dB.](f455955c4bc84005728b4138f19098dc_img.jpg) + +The figure is a scatter plot titled "Tx Power Back Off for 1Tx Power class 5 SL-U". The y-axis is labeled "back off[dB]" and ranges from 0 to 6.5 in increments of 0.5. The x-axis is labeled "Test Scenario #" and ranges from 1 to 46. There are four data series: QPSK (red circles), 16QAM (blue asterisks), 64QAM (magenta diamonds), and 256QAM (black triangles). The 256QAM series is relatively flat, staying around 5.5 dB. The 64QAM series fluctuates between approximately 2.2 dB and 3.3 dB. The 16QAM series fluctuates between approximately 0.4 dB and 2.9 dB. The QPSK series has the lowest values, mostly between 0.1 dB and 2.9 dB, with some outliers at 0.1 dB for scenarios 33, 35, 36, 43, and 44. + +| Test Scenario # | QPSK [dB] | 16QAM [dB] | 64QAM [dB] | 256QAM [dB] | +|-----------------|-----------|------------|------------|-------------| +| 1 | 2.5 | 2.5 | 2.8 | 5.5 | +| 2 | 2.2 | 2.2 | 3.3 | 5.5 | +| 3 | 2.5 | 2.5 | 2.8 | 5.5 | +| 4 | 2.5 | 2.5 | 2.8 | 5.5 | +| 5 | 2.5 | 2.5 | 2.8 | 5.5 | +| 6 | 2.8 | 2.8 | 2.8 | 5.5 | +| 7 | 2.5 | 2.5 | 2.5 | 5.1 | +| 8 | 2.5 | 2.5 | 2.5 | 5.1 | +| 9 | 2.8 | 2.8 | 2.8 | 5.1 | +| 10 | 2.5 | 2.5 | 2.5 | 5.1 | +| 11 | 2.5 | 2.5 | 2.5 | 5.1 | +| 12 | 2.5 | 2.5 | 2.5 | 5.1 | +| 13 | 2.8 | 2.8 | 2.8 | 5.5 | +| 14 | 2.2 | 2.2 | 3.3 | 5.5 | +| 15 | 2.5 | 2.5 | 3.3 | 5.5 | +| 16 | 2.2 | 2.2 | 3.3 | 5.5 | +| 17 | 2.2 | 2.2 | 3.3 | 5.5 | +| 18 | 2.5 | 2.5 | 2.8 | 5.5 | +| 19 | 2.5 | 2.5 | 3.3 | 5.5 | +| 20 | 2.5 | 2.5 | 3.3 | 5.5 | +| 21 | 2.2 | 2.2 | 3.3 | 5.5 | +| 22 | 2.2 | 2.2 | 3.3 | 5.5 | +| 23 | 2.5 | 2.5 | 3.3 | 5.5 | +| 24 | 2.5 | 2.5 | 3.3 | 5.5 | +| 25 | 2.5 | 2.5 | 2.8 | 5.5 | +| 26 | 2.2 | 2.2 | 2.2 | 5.5 | +| 27 | 2.5 | 2.5 | 2.5 | 5.5 | +| 28 | 2.5 | 2.5 | 2.5 | 5.5 | +| 29 | 2.2 | 2.2 | 2.2 | 5.5 | +| 30 | 2.8 | 2.8 | 2.8 | 5.5 | +| 31 | 2.5 | 2.5 | 2.5 | 5.1 | +| 32 | 2.5 | 2.5 | 2.5 | 5.1 | +| 33 | 0.1 | 0.4 | 2.2 | 5.1 | +| 34 | 2.2 | 2.2 | 2.2 | 5.1 | +| 35 | 0.1 | 0.4 | 2.2 | 5.1 | +| 36 | 0.1 | 0.4 | 2.2 | 5.1 | +| 37 | 2.5 | 2.5 | 2.5 | 5.1 | +| 38 | 2.5 | 2.5 | 2.5 | 5.1 | +| 39 | 2.5 | 2.5 | 2.5 | 5.1 | +| 40 | 2.5 | 2.5 | 2.5 | 5.1 | +| 41 | 2.5 | 2.5 | 2.5 | 5.1 | +| 42 | 2.5 | 2.5 | 2.5 | 5.1 | +| 43 | 0.1 | 0.4 | 2.2 | 5.1 | +| 44 | 0.1 | 0.7 | 2.5 | 5.1 | +| 45 | 1.3 | 1.3 | 2.5 | 5.1 | +| 46 | 0.1 | 0.4 | 2.2 | 5.1 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 6.5. The x-axis is 'Test Scenario #' from 1 to 46. Data series for QPSK (red circles), 16QAM (blue asterisks), 64QAM (magenta diamonds), and 256QAM (black triangles) are plotted. 256QAM stays around 5.5 dB, while others fluctuate between 0.5 and 3.5 dB. + +Figure 6.1.3.7.1.1-2: NS\_58-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.7.1.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration and Full/Partial RB allocation. + +**Table 6.1.3.7.1.1-2 : NS\_58-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| Pre-coding | Modulation | RB Allocation | | | | +|------------|------------|----------------------------|--------------|----------------------------|--------------| +| | | Outer RB set configuration | | Inner RB set configuration | | +| | | Full (dB) | Partial (dB) | Full(dB) | Partial (dB) | +| CP-OFDM | QPSK | 2.81 | 2.83 | 2.47 | 1.20 | +| | 16 QAM | 2.81 | 2.83 | 2.47 | 1.20 | +| | 64 QAM | 3.18 | 2.83 | 3.16 | 2.47 | +| | 256 QAM | 5.48 | 5.09 | 5.88 | 5.06 | + +The inner RB set configuration needs to be considered when defining the SL-U A-MPR requirements. + +Based on the results, Table 6.1.3.7.1.1-3 can be considered for NS\_58 A-MPR for SL-U UE power class 5. + +**Table 6.1.3.7.1.1-3. NS\_58 additional maximum power reduction (A-MPR) for SL-U UE power class 5** + +| Pre-coding | Modulation | RB Allocation (Note 4) | | | | +|------------|------------|-----------------------------------------|---------------------------|-----------------------------------------|---------------------------| +| | | Outer RB set configuration 5 | | Inner RB set configuration 5 | | +| | | Full (dB) 2 | Partial (dB) 3 | Full (dB) 2 | Partial (dB) 3 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 4.5 | ≤ 3.5 | ≤ 2.5 | +| | 16 QAM | ≤ 4.0 | ≤ 4.5 | ≤ 4.0 | ≤ 3.0 | +| | 64 QAM | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. + +NOTE 2: The A-MPR for Full RB allocation applies to all RB's in all transmitted 20 MHz or larger channels that are fully allocated or all RB's in all transmitted sub-bands for wideband operation that are fully allocated excluding the wideband configurations of Table 6.2F.2-2. + +NOTE 3: The A-MPR for Partial RB allocation applies to interlaced allocations with uplink resource allocation type 2 as specified in TS 38.214 [10] or transmitted sub-bands for wideband operation are transmitted according to the wideband configurations of Table 6.2F.2-2. + +NOTE 4: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, and 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR applies. + +NOTE 5: Contiguous outer sub-band configuration and contiguous inner sub-band configuration in Table 6.1.2.1.1.1-5 apply. + +###### **6.1.3.7.1.2**                      **OPPO's simulation results (R4-2316119)** + +The A-MPR requirement is captured in sub-clause 6.2F.3.10 and the requirement is differentiated by different channel bandwidth as captured below: + +**Table 6.1.3.7.1.2-1 A-MPR for single CC** + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|---------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 5.4 | 5.6 | 3.5 | 3.5 | 3.2 | 3.2 | 3.2 | 6.7 | 8.0 | 3.5 | 4.7 | 3.2 | 3.3 | 3.2 | +| 16QAM | 5.4 | 5.7 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 6.8 | 8.0 | 3.5 | 4.8 | 3.2 | 3.3 | 3.2 | +| 64QAM | 5.3 | 5.6 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 6.8 | 8.0 | 4.1 | 4.7 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 7.9 | 8.0 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +Table 6.1.3.7.1.2-2 A-MPR for wideband + +| | Bitmap | 10 | 100 | 010 | 1000 | 0100 | 10000 | 01000 | 00100 | 110 | 1100 | 0110 | 11000 | 01100 | 1110 | 11100 | 01110 | 11110 | +|------------|--------|-----|-----|-----|------|------|-------|-------|-------|-----|------|------|-------|-------|------|-------|-------|-------| +| Contiguous | QPSK | 5.5 | 5.5 | 5.6 | 5.5 | 5.5 | 5.5 | 5.5 | 5.6 | 3.0 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | +| | 16QAM | 5.5 | 5.5 | 5.6 | 5.5 | 5.5 | 5.5 | 5.5 | 5.6 | 3.6 | 3.6 | 3.7 | 3.6 | 3.6 | 3.6 | 3.5 | 3.7 | 3.6 | +| | 64QAM | 5.5 | 5.5 | 5.6 | 5.5 | 5.5 | 5.5 | 5.5 | 5.6 | 4.8 | 4.7 | 4.9 | 4.7 | 4.8 | 4.9 | 4.8 | 5.0 | 5.0 | +| | 256QAM | 7.4 | 7.5 | 8.5 | 7.4 | 7.5 | 7.4 | 7.4 | 8.5 | 7.7 | 7.3 | 8.5 | 7.3 | 7.7 | 8.0 | 7.6 | 8.5 | 8.0 | +| Interlace | QPSK | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 5.0 | 5.0 | 5.0 | 5.0 | 5.0 | 3.1 | 3.3 | 3.4 | 2.7 | +| | 16QAM | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 5.1 | 5.0 | 5.0 | 5.0 | 5.1 | 3.2 | 3.5 | 3.3 | 2.8 | +| | 64QAM | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 5.1 | 5.1 | 5.1 | 5.1 | 5.1 | 4.1 | 4.1 | 4.1 | 4.0 | +| | 256QAM | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 8.0 | 6.8 | 6.8 | 6.8 | 6.8 | 6.8 | 6.7 | 6.7 | 6.7 | 6.6 | + +![Scatter plot titled 'NS_04S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 subcarriers. The y-axis represents A-MPR from 0.0 to 10.0. The x-axis represents subcarriers from 1 to 14. Data points are colored by modulation: blue for QPSK, orange for 16QAM, grey for 64QAM, and yellow for 256QAM.](02c999e5846341813b658e446e9a6fda_img.jpg) + +| Subcarrier | QPSK | 16QAM | 64QAM | 256QAM | +|------------|------|-------|-------|--------| +| 1 | 5.5 | | | 8.8 | +| 2 | 5.8 | | | 8.7 | +| 3 | 3.5 | 3.8 | 5.0 | 8.7 | +| 4 | 3.5 | 3.8 | 5.0 | 8.8 | +| 5 | 3.3 | 3.8 | 5.2 | 8.7 | +| 6 | 3.3 | 3.8 | 5.0 | 8.6 | +| 7 | 3.3 | 3.8 | 5.2 | 8.8 | +| 8 | 6.8 | | | 7.8 | +| 9 | 8.0 | | | | +| 10 | 3.5 | | 4.0 | 7.5 | +| 11 | 4.8 | | | 7.8 | +| 12 | 3.3 | | 4.0 | 6.5 | +| 13 | 3.3 | | 4.0 | 6.5 | +| 14 | 3.3 | | 4.0 | 6.8 | + +Scatter plot titled 'NS\_04S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 subcarriers. The y-axis represents A-MPR from 0.0 to 10.0. The x-axis represents subcarriers from 1 to 14. Data points are colored by modulation: blue for QPSK, orange for 16QAM, grey for 64QAM, and yellow for 256QAM. + +Figure 6.1.3.7.1.2-1 Single CC A-MPR + +![Scatter plot titled 'NS_04S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 48 subcarriers. The y-axis represents A-MPR from 0 to 9, and the x-axis represents subcarriers from 14 to 48. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](9e4179ffe4701bec67534299c4935049_img.jpg) + +Scatter plot titled 'NS\_04S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 48 subcarriers. The y-axis represents A-MPR from 0 to 9, and the x-axis represents subcarriers from 14 to 48. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.7.1.2-2 Wideband CC A-MPR + +6.1.3.7.1.3 Qualcomm’s simulation results (R4-2316791) + +Table 6.1.3.7.1.3-1: Simulation results for NS\_58 Full and partial allocations. + +| NS_58 A-MPR | 20M | 20M | 40M | 40M | 60M | 60M | 80M | 80M | +|-------------|------|---------|------|---------|------|---------|------|---------| +| | Full | Partial | Full | Partial | Full | Partial | Full | Partial | +| QPSK | ≤5.2 | ≤5.4 | ≤5.9 | ≤6.0 | ≤5.6 | ≤5.8 | ≤5.4 | ≤5.7 | +| 16 QAM | ≤5.3 | ≤5.6 | ≤5.8 | ≤6.2 | ≤5.7 | ≤5.9 | ≤5.6 | ≤5.8 | +| 64 QAM | ≤5.3 | ≤5.8 | ≤5.8 | ≤6.2 | ≤5.6 | ≤5.9 | ≤5.6 | ≤5.8 | +| 256 QAM | ≤5.4 | ≤5.8 | ≤5.8 | ≤6.2 | ≤5.7 | ≤5.9 | ≤5.6 | ≤5.8 | + +The power class 5 PSSCH A-MPR in the table should be considered in the discussion of MPR requirements. + +##### 6.1.3.7.2 A-MPR for S-SSB transmission + +6.1.3.7.2.1 LG Electronics’ simulation results (R4-2315542) + +For NS\_58, Table 6.1.3.7.2.1-1 and Figure 6.1.3.7.2.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.7.2.1-1: NS\_58-S-SSB A-MPR simulation results for SL-U power class 5 + +| | | | | | | | | | | | | | | | | | | | | | | +|-------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|--| +| Scenario # | #1 | #2 | #3 | #4 | #5 | | | | | | | | | | | | | | | | | +| '20MHz' | 9.43 | 7.90 | 6.82 | 6.81 | 6.08 | | | | | | | | | | | | | | | | | +| Scenario # | #6 | #7 | #8 | #9 | #10 | #11 | | | | | | | | | | | | | | | | +| '40MHz' | 11.05 | 8.92 | 7.45 | 9.20 | 8.17 | 7.11 | | | | | | | | | | | | | | | | +| Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | | | | | | | | | | | +| '60MHz' | 9.36 | 7.58 | 8.19 | 6.46 | 6.69 | 7.21 | 4.76 | 7.20 | 8.18 | 6.79 | | | | | | | | | | | | +| Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | | | | +| '80MHz' | 9.92 | 7.41 | 8.95 | 6.78 | 7.97 | 6.48 | 6.89 | 7.19 | 5.98 | 4.31 | 4.61 | 7.12 | 9.04 | 6.62 | 7.85 | 6.61 | 7.79 | 6.47 | | | | +| Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | #55 | #56 | #57 | #58 | #59 | | +| '100MHz' | 10.91 | 7.19 | 9.59 | 6.61 | 9.54 | 6.67 | 7.99 | 6.53 | 6.80 | 7.20 | 6.12 | 4.95 | 5.66 | 4.09 | 4.70 | 7.28 | 4.56 | 7.16 | 9.97 | 7.47 | | +| Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | #71 | #72 | #73 | #74 | #75 | #76 | #77 | | | | +| '100MHz' | 8.85 | 6.62 | 9.14 | 6.54 | 8.62 | 6.08 | 8.80 | 5.83 | 8.04 | 6.48 | 7.86 | 6.46 | 8.13 | 6.49 | 7.49 | 6.35 | 10.15 | 6.31 | | | | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 11.5. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds).](ad406eca7668ea7128dba19ec32a22ac_img.jpg) + +| Test Scenario # | 20MHz back off [dB] | 40MHz back off [dB] | 60MHz back off [dB] | +|-----------------|---------------------|---------------------|---------------------| +| 1 | 9.43 | | | +| 2 | 6.82 | | | +| 3 | 5.50 | | | +| 4 | 5.80 | | | +| 5 | 4.50 | | | +| 6 | | 11.05 | | +| 7 | | 8.92 | | +| 8 | | 7.45 | | +| 9 | | 9.20 | | +| 10 | | 8.17 | | +| 11 | | 7.11 | | +| 12 | | | 9.36 | +| 13 | | | 7.58 | +| 14 | | | 8.19 | +| 15 | | | 6.46 | +| 16 | | | 6.69 | +| 17 | | | 7.21 | +| 18 | | | 4.76 | +| 19 | | | 7.20 | +| 20 | | | 8.18 | +| 21 | | | 6.79 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 11.5. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds). + +a. 20MHz, 40MHz, and 60MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz. The y-axis ranges from 0 to 11 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by open triangles.](449dd9d482c5b47f1c013ce3e18b09e6_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +80MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 22 | 10.5 | +| 23 | 7.0 | +| 24 | 8.8 | +| 25 | 5.8 | +| 26 | 7.8 | +| 27 | 5.5 | +| 28 | 5.8 | +| 29 | 4.8 | +| 30 | 6.2 | +| 31 | 4.2 | +| 32 | 4.5 | +| 33 | 3.5 | +| 34 | 8.8 | +| 35 | 6.2 | +| 36 | 7.8 | +| 37 | 5.2 | +| 38 | 7.8 | +| 39 | 5.5 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz. The y-axis ranges from 0 to 11 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by open triangles. + +b. 80MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz. The y-axis ranges from 0 to 11.5 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by open triangles.](123e1675d910a1beab564c5fec9548e2_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +100MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 40 | 11.0 | +| 41 | 7.0 | +| 42 | 9.8 | +| 43 | 6.0 | +| 44 | 9.5 | +| 45 | 6.0 | +| 46 | 7.8 | +| 47 | 5.5 | +| 48 | 6.0 | +| 49 | 4.8 | +| 50 | 6.2 | +| 51 | 3.2 | +| 52 | 5.5 | +| 53 | 3.0 | +| 54 | 4.8 | +| 55 | 3.5 | +| 56 | 4.5 | +| 57 | 3.5 | +| 58 | 10.0 | +| 59 | 7.2 | +| 60 | 8.8 | +| 61 | 6.2 | +| 62 | 8.8 | +| 63 | 6.2 | +| 64 | 8.2 | +| 65 | 5.2 | +| 66 | 9.2 | +| 67 | 5.0 | +| 68 | 7.8 | +| 69 | 5.0 | +| 70 | 7.8 | +| 71 | 5.5 | +| 72 | 7.8 | +| 73 | 5.8 | +| 74 | 7.2 | +| 75 | 5.0 | +| 76 | 9.2 | +| 77 | 6.2 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz. The y-axis ranges from 0 to 11.5 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by open triangles. + +c. 100MHz + +Figure 6.1.3.7.2.1-1: NS\_58-S-SSB A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.7.2.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.7.2.1-2 : NS\_58 S-SSB A-MPR simulation results for SL-U power class 5** + +| | RB Allocation | | | | +|---------------------------------|----------------------------|------|----------------------------|------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous sub-band RB sets | 10.91 | 6.86 | 6.11 | 3.98 | +| Non-contiguous sub-band RB sets | 9.94 | 7.22 | 6.93 | 4.82 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the S-SSB A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.7.2.1-3 or Table 6.1.3.7.2.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.7.2.1-3: NS\_58 S-SSB A-MPR for SL-U UE power class 5** + +| | RB Allocation | | | | +|---------------------------------|----------------------------|-------------|----------------------------|------------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous sub-band RB sets | $\leq 13.5$ | $\leq 9.5$ | $\leq 8.5$ | $\leq 6.5$ | +| Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.0$ | $\leq 9.5$ | $\leq 7.5$ | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, and 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR applies. + +**Table 6.1.3.7.2.1-4: NS\_58 S-SSB A-MPR for SL-U UE power class 5** + +| | RB Allocation | | | | +|--------------------------------------------|----------------------------|-------------|----------------------------|------------| +| | Outer RB set configuration | | Inner RB set configuration | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | +| Contiguous/Non-contiguous sub-band RB sets | $\leq 13.5$ | $\leq 10.0$ | $\leq 9.5$ | $\leq 7.5$ | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, and 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR applies. + +##### 6.1.3.7.3 A-MPR for PSFCH transmission + +###### 6.1.3.7.3.1 LG Electronics' simulation results (R4-2315542 and R4-2321771) + +For NS\_58, Table 6.1.3.7.3.1-1 shows the A-MPR simulation results for the scenarios. + +Table 6.1.3.7.3.1-1: NS\_58-PSFCH A-MPR simulation results for SL-U power class 5 + +| | | | | | | | | | | | | | | | | | | | | +|-------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| +| Scenario # | #1 | #2 | | | | | | | | | | | | | | | | | | +| '20MHz' | 7.98 | 7.60 | | | | | | | | | | | | | | | | | | +| Scenario # | #3 | #4 | | | | | | | | | | | | | | | | | | +| '40MHz' | 9.32 | 7.94 | | | | | | | | | | | | | | | | | | +| Scenario # | #5 | #6 | #7 | #8 | #9 | | | | | | | | | | | | | | | +| '60MHz' | 9.65 | 9.05 | 7.67 | 6.51 | 8.96 | | | | | | | | | | | | | | | +| Scenario # | #10 | #11 | #12 | #13 | #14 | #15 | #16 | #17 | #18 | | | | | | | | | | | +| '80MHz' | 9.43 | 9.83 | 9.01 | 7.57 | 8.56 | 6.86 | 9.82 | 9.00 | 8.95 | | | | | | | | | | | +| Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | +| '100MHz' | 9.55 | | | | | | | | | | | | | | | | | | | + +Table 6.1.3.7.3.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.7.3.1-2 : NS\_58 PSFCH A-MPR simulation results for SL-U power class 5** + +| | RB Allocation | | +|---------------------------------|----------------------------|----------------------------| +| | Outer RB set configuration | Inner RB set configuration | +| Contiguous sub-band RB sets | 9.83 | 8.56 | +| Non-contiguous sub-band RB sets | 9.82 | 8.08 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the PSFCH A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.7.3.1-3 or Table 6.1.3.7.3.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.7.3.1-3 NS\_58 PSFCH A-MPR for SL-U UE power class 5** + +| | RB Allocation | | +|---------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 2 | Inner RB set configuration 2 | +| Contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.5$ | +| Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.0$ | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. +NOTE 3: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, and 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR applies. + +**Table 6.1.3.7.3.1-4 NS\_58 PSFCH A-MPR for SL-U UE power class 5** + +| | RB Allocation | | +|--------------------------------------------|-----------------------------------------|-----------------------------------------| +| | Outer RB set configuration 2 | Inner RB set configuration 2 | +| Contiguous/Non-contiguous sub-band RB sets | $\leq 12.5$ | $\leq 10.5$ | + +NOTE 1: The MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. +NOTE 2: Outer sub-band configuration and inner sub-band configuration in Table 2-5 apply. +NOTE 3: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, and 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR applies. + +#### 6.1.3.8 A-MPR for SL-U with NS\_59 + +##### 6.1.3.8.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +##### 6.1.3.8.2 A-MPR for S-SSB transmission + +##### 6.1.3.8.3 A-MPR for PSFCH transmission + +#### 6.1.3.9 A-MPR for SL-U with NS\_60 + +##### 6.1.3.9.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.3.9.1.1 LG Electronics' simulation results (R4-2315542) + +For NS\_60, Table 6.1.3.9.1.1-1 and Figure 6.1.3.9.1.1-1 show the A-MPR simulation results for the scenarios. + +**Table 6.1.3.9.1.1-1: NS\_60-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| | | | | | | | | | | | | | | | | | | | | +|----------|------------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| '20MHz' | Scenario # | #1 | #7 | #2 | #8 | | | | | | | | | | | | | | | +| | 'QPSK' | 5.47 | 7.62 | 5.89 | 7.63 | | | | | | | | | | | | | | | +| | '16QAM' | 5.47 | 8.07 | 5.89 | 8.07 | | | | | | | | | | | | | | | +| | '64QAM' | 5.47 | 8.06 | 5.89 | 7.63 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 8.06 | 5.89 | 8.07 | | | | | | | | | | | | | | | +| '40MHz' | Scenario # | #3 | #9 | #13 | #30 | | | | | | | | | | | | | | | +| | 'QPSK' | 2.48 | 4.67 | 5.47 | 7.62 | | | | | | | | | | | | | | | +| | '16QAM' | 2.48 | 4.67 | 5.47 | 8.06 | | | | | | | | | | | | | | | +| | '64QAM' | 2.82 | 4.68 | 5.47 | 8.07 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.47 | 8.05 | | | | | | | | | | | | | | | +| '60MHz' | Scenario # | #4 | #10 | #14 | #31 | #15 | #32 | #16 | #33 | | | | | | | | | | | +| | 'QPSK' | 3.90 | 4.28 | 5.88 | 8.07 | 2.47 | 5.07 | 5.88 | 8.05 | | | | | | | | | | | +| | '16QAM' | 3.90 | 4.28 | 5.88 | 8.07 | 2.47 | 5.07 | 5.88 | 8.05 | | | | | | | | | | | +| | '64QAM' | 3.90 | 4.28 | 5.88 | 8.52 | 2.82 | 5.06 | 5.88 | 8.05 | | | | | | | | | | | +| | '256QAM' | 5.88 | 5.48 | 5.89 | 8.07 | 5.47 | 5.07 | 5.88 | 8.04 | | | | | | | | | | | +| '80MHz' | Scenario # | #5 | #11 | #17 | #34 | #18 | #35 | #19 | #36 | #20 | #37 | #21 | #38 | | | | | | | +| | 'QPSK' | 2.82 | 3.53 | 5.88 | 8.06 | 2.47 | 5.07 | 2.81 | 3.53 | 5.88 | 8.05 | 2.46 | 5.06 | | | | | | | +| | '16QAM' | 2.82 | 3.53 | 5.88 | 8.06 | 2.47 | 5.07 | 2.81 | 3.53 | 5.88 | 8.49 | 2.46 | 5.06 | | | | | | | +| | '64QAM' | 2.82 | 3.53 | 5.89 | 8.06 | 2.81 | 5.07 | 3.16 | 3.53 | 5.88 | 8.05 | 3.16 | 5.06 | | | | | | | +| | '256QAM' | 5.47 | 5.07 | 5.88 | 8.06 | 5.47 | 5.07 | 5.47 | 5.07 | 5.88 | 8.51 | 5.46 | 5.06 | | | | | | | +| '100MHz' | Scenario # | #6 | #12 | #22 | #39 | #23 | #40 | #24 | #41 | #25 | #42 | #26 | #43 | #27 | #44 | #28 | #45 | #29 | #46 | +| | 'QPSK' | 3.17 | 3.90 | 5.89 | 8.07 | 2.47 | 5.07 | 2.47 | 3.16 | 2.47 | 3.17 | 5.88 | 8.04 | 2.46 | 5.05 | 2.47 | 3.16 | 5.88 | 8.05 | +| | '16QAM' | 3.17 | 3.90 | 5.88 | 8.51 | 2.47 | 5.07 | 2.47 | 3.17 | 2.47 | 3.17 | 5.88 | 8.49 | 2.46 | 5.05 | 2.46 | 3.16 | 5.88 | 8.05 | +| | '64QAM' | 3.17 | 3.90 | 5.88 | 8.51 | 2.81 | 5.06 | 3.16 | 3.16 | 2.81 | 3.17 | 5.47 | 8.05 | 3.16 | 5.05 | 3.16 | 3.16 | 5.88 | 8.05 | +| | '256QAM' | 5.47 | 5.06 | 5.89 | 8.52 | 5.47 | 5.07 | 5.47 | 5.06 | 5.47 | 5.06 | 5.88 | 8.05 | 5.47 | 5.06 | 5.47 | 5.46 | 5.88 | 8.05 | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 9.5. The x-axis is 'Test Scenario #' from 1 to 50. Data series for QPSK (red circle), 16QAM (blue asterisk), 64QAM (green diamond), and 256QAM (black triangle) are plotted.](b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg) + +The figure is a scatter plot titled "Tx Power Back Off for 1Tx Power class 5 SL-U". The y-axis is labeled "back off[dB]" and ranges from 0 to 9.5 in increments of 0.5. The x-axis is labeled "Test Scenario #" and ranges from 1 to 50. There are four data series: QPSK (red circles), 16QAM (blue asterisks), 64QAM (green diamonds), and 256QAM (black triangles). The plot shows the back off required for each modulation scheme across 50 test scenarios. Generally, higher-order modulations require higher back off values. QPSK and 16QAM often show similar back off values, while 64QAM and 256QAM show more variation and generally higher back off requirements in many scenarios. + +| Test Scenario # | QPSK [dB] | 16QAM [dB] | 64QAM [dB] | 256QAM [dB] | +|-----------------|-----------|------------|------------|-------------| +| 1 | 5.5 | 5.5 | 5.5 | 5.5 | +| 2 | 5.5 | 5.5 | 5.5 | 5.5 | +| 3 | 2.5 | 2.5 | 2.8 | 5.5 | +| 4 | 2.8 | 2.8 | 3.8 | 5.5 | +| 5 | 3.2 | 3.2 | 3.2 | 5.5 | +| 6 | 7.5 | 7.5 | 7.5 | 5.5 | +| 7 | 7.5 | 7.5 | 7.5 | 5.5 | +| 8 | 4.8 | 4.8 | 4.8 | 5.5 | +| 9 | 4.2 | 4.2 | 4.2 | 5.5 | +| 10 | 3.5 | 3.5 | 3.5 | 5.5 | +| 11 | 3.8 | 3.8 | 3.8 | 5.5 | +| 12 | 5.5 | 5.5 | 5.5 | 5.5 | +| 13 | 5.8 | 5.8 | 5.8 | 5.5 | +| 14 | 5.5 | 5.5 | 5.5 | 5.5 | +| 15 | 2.5 | 2.5 | 2.8 | 5.5 | +| 16 | 5.8 | 5.8 | 5.8 | 5.5 | +| 17 | 5.8 | 5.8 | 5.8 | 5.5 | +| 18 | 2.5 | 2.5 | 2.8 | 5.5 | +| 19 | 2.8 | 2.8 | 3.2 | 5.5 | +| 20 | 5.8 | 5.8 | 5.8 | 5.5 | +| 21 | 5.8 | 5.8 | 5.8 | 5.5 | +| 22 | 5.8 | 5.8 | 5.8 | 5.5 | +| 23 | 2.5 | 2.5 | 2.8 | 5.5 | +| 24 | 2.5 | 2.5 | 2.8 | 5.5 | +| 25 | 2.5 | 2.5 | 2.8 | 5.5 | +| 26 | 5.8 | 5.8 | 5.8 | 5.5 | +| 27 | 5.5 | 5.5 | 5.5 | 5.5 | +| 28 | 5.5 | 5.5 | 5.5 | 5.5 | +| 29 | 5.8 | 5.8 | 5.8 | 5.5 | +| 30 | 5.8 | 5.8 | 5.8 | 5.5 | +| 31 | 5.5 | 5.5 | 5.5 | 5.5 | +| 32 | 5.5 | 5.5 | 5.5 | 5.5 | +| 33 | 5.5 | 5.5 | 5.5 | 5.5 | +| 34 | 5.5 | 5.5 | 5.5 | 5.5 | +| 35 | 5.5 | 5.5 | 5.5 | 5.5 | +| 36 | 5.5 | 5.5 | 5.5 | 5.5 | +| 37 | 5.5 | 5.5 | 5.5 | 5.5 | +| 38 | 5.5 | 5.5 | 5.5 | 5.5 | +| 39 | 5.5 | 5.5 | 5.5 | 5.5 | +| 40 | 5.5 | 5.5 | 5.5 | 5.5 | +| 41 | 5.5 | 5.5 | 5.5 | 5.5 | +| 42 | 5.5 | 5.5 | 5.5 | 5.5 | +| 43 | 5.5 | 5.5 | 5.5 | 5.5 | +| 44 | 5.5 | 5.5 | 5.5 | 5.5 | +| 45 | 5.5 | 5.5 | 5.5 | 5.5 | +| 46 | 5.5 | 5.5 | 5.5 | 5.5 | +| 47 | 5.5 | 5.5 | 5.5 | 5.5 | +| 48 | 5.5 | 5.5 | 5.5 | 5.5 | +| 49 | 5.5 | 5.5 | 5.5 | 5.5 | +| 50 | 5.5 | 5.5 | 5.5 | 5.5 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 9.5. The x-axis is 'Test Scenario #' from 1 to 50. Data series for QPSK (red circle), 16QAM (blue asterisk), 64QAM (green diamond), and 256QAM (black triangle) are plotted. + +Figure 6.1.3.9.1.1-1: NS\_60-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.9.1.1-2 shows the maximum value of simulation results considering Full/Partial RB allocation. + +**Table 6.1.3.9.1.1-2 : NS\_60-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| CP-OFDM | QPSK | 5.89 | 8.07 | 2.48 | 5.07 | 3.90 | 4.28 | 2.82 | 3.53 | 3.17 | 3.90 | +| | 16 QAM | 5.89 | 8.51 | 2.48 | 5.07 | 3.90 | 4.28 | 2.82 | 3.53 | 3.17 | 3.90 | +| | 64 QAM | 5.89 | 8.52 | 3.16 | 5.07 | 3.90 | 4.28 | 2.82 | 3.53 | 3.17 | 3.90 | +| | 256 QAM | 5.89 | 8.52 | 5.47 | 5.07 | 5.88 | 5.48 | 5.47 | 5.07 | 5.47 | 5.06 | + +Based on the results, Table 6.1.3.9.1.1-3 can be considered for NS\_60 A-MPR for SL-U UE power class 5. + +**Table 6.1.3.9.1.1-3. NS\_60 additional maximum power reduction (A-MPR) for SL-U UE power class 5** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| CP-OFDM | QPSK | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.0 | ≤ 5.5 | ≤ 4.5 | ≤ 5.5 | ≤ 4.5 | ≤ 5.5 | +| | 16 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.0 | ≤ 5.5 | ≤ 4.5 | ≤ 5.5 | ≤ 4.5 | ≤ 5.5 | +| | 64 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 7.0 | ≤ 8.5 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. +NOTE 2: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies + +###### 6.1.3.9.1.2 + +OPPO's simulation results (R4-2316119) + +The A-MPR requirement is captured in sub-clause 6.2F.3.10 and the requirement is differentiated by different channel bandwidth as captured below: + +**Table 6.1.3.9.1.1-1 A-MPR for single CC** + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|---------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 6.4 | 6.6 | 3.4 | 3.5 | 3.5 | 3.5 | 3.5 | 7.8 | 8.9 | 4.5 | 5.8 | 4.0 | 3.6 | 3.5 | +| 16QAM | 6.4 | 6.7 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 7.8 | 9.0 | 4.5 | 5.8 | 4.0 | 3.6 | 3.5 | +| 64QAM | 6.3 | 6.6 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 7.8 | 9.0 | 4.6 | 5.8 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 7.9 | 9.0 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +Table 6.1.3.9.1.1-2 A-MPR for wideband + +| | Bitmap | 10 | 100 | 010 | 1000 | 0100 | 10000 | 01000 | 00100 | 110 | 1100 | 0110 | 11000 | 01100 | 1110 | 11100 | 01110 | 11110 | +|------------|--------|-----|-----|-----|------|------|-------|-------|-------|-----|------|------|-------|-------|------|-------|-------|-------| +| Contiguous | QPSK | 6.5 | 6.5 | 6.6 | 6.5 | 6.5 | 6.5 | 6.5 | 6.6 | 3.7 | 3.5 | 3.7 | 3.5 | 3.7 | 3.0 | 2.8 | 2.8 | 3.2 | +| | 16QAM | 6.5 | 6.5 | 6.6 | 6.5 | 6.6 | 6.5 | 6.5 | 6.7 | 3.7 | 3.6 | 3.7 | 3.6 | 3.7 | 3.6 | 3.5 | 3.7 | 3.6 | +| | 64QAM | 6.6 | 6.5 | 6.6 | 6.6 | 6.5 | 6.6 | 6.6 | 6.6 | 4.8 | 4.7 | 4.9 | 4.7 | 4.8 | 4.9 | 4.8 | 5.0 | 5.0 | +| | 256QAM | 7.4 | 7.5 | 8.5 | 7.4 | 7.5 | 7.4 | 7.4 | 8.5 | 7.7 | 7.3 | 8.5 | 7.3 | 7.7 | 8.0 | 7.6 | 8.5 | 8.0 | +| Interlace | QPSK | 8.9 | 9.0 | 9.0 | 9.0 | 8.9 | 9.0 | 8.9 | 9.0 | 6.0 | 5.9 | 5.9 | 5.9 | 6.0 | 4.2 | 4.4 | 4.4 | 3.2 | +| | 16QAM | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 6.0 | 6.0 | 5.9 | 6.0 | 6.0 | 4.3 | 4.5 | 4.3 | 3.3 | +| | 64QAM | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 6.0 | 6.0 | 6.0 | 6.0 | 6.0 | 4.3 | 4.4 | 4.3 | 4.0 | +| | 256QAM | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 9.0 | 6.8 | 6.8 | 6.8 | 6.8 | 6.8 | 6.7 | 6.7 | 6.7 | 6.6 | + +![Scatter plot titled 'NS_05S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 contiguous carriers. The y-axis ranges from 0.0 to 10.0. The x-axis represents carrier indices from 1 to 14. Data points are colored by modulation: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](c2813655160a6d83a32289b367a84d1b_img.jpg) + +| Carrier Index | QPSK | 16QAM | 64QAM | 256QAM | +|---------------|------|-------|-------|--------| +| 1 | 6.5 | | | 8.5 | +| 2 | 6.5 | 6.5 | | 8.5 | +| 3 | 3.5 | 3.5 | 5.0 | 8.5 | +| 4 | 3.5 | 3.5 | 5.0 | 8.5 | +| 5 | 3.5 | 3.5 | 5.0 | 8.5 | +| 6 | 3.5 | 3.5 | 5.0 | 8.5 | +| 7 | 3.5 | 3.5 | 5.0 | 8.5 | +| 8 | 7.5 | 7.5 | | 7.5 | +| 9 | 8.5 | 8.5 | | 8.5 | +| 10 | 4.5 | 4.5 | | 7.5 | +| 11 | 5.5 | 5.5 | | 7.5 | +| 12 | 4.0 | 4.0 | | 6.5 | +| 13 | 3.5 | 3.5 | 4.0 | 6.5 | +| 14 | 3.5 | 3.5 | 4.0 | 6.5 | + +Scatter plot titled 'NS\_05S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 contiguous carriers. The y-axis ranges from 0.0 to 10.0. The x-axis represents carrier indices from 1 to 14. Data points are colored by modulation: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.9.1.1-1 Single CC A-MPR + +![Scatter plot titled 'NS_05S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 34 interlaced carriers (indices 15-48). The y-axis ranges from 0 to 10. The x-axis represents carrier indices from 15 to 48. Data points are colored by modulation: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](17858cb897c937df4988696bb6686c44_img.jpg) + +| Carrier Index | QPSK | 16QAM | 64QAM | 256QAM | +|---------------|------|-------|-------|--------| +| 15 | 6.5 | | | 7.5 | +| 16 | 6.5 | | | 7.5 | +| 17 | 6.5 | | | 8.5 | +| 18 | 6.5 | | | 7.5 | +| 19 | 6.5 | | | 7.5 | +| 20 | 6.5 | | | 7.5 | +| 21 | 6.5 | | | 7.5 | +| 22 | 6.5 | | | 8.5 | +| 23 | 3.5 | 3.5 | 5.0 | 7.5 | +| 24 | 3.5 | 3.5 | 5.0 | 7.5 | +| 25 | 3.5 | 3.5 | 5.0 | 8.5 | +| 26 | 3.5 | 3.5 | 5.0 | 7.5 | +| 27 | 3.5 | 3.5 | 5.0 | 7.5 | +| 28 | 3.5 | 3.5 | 5.0 | 8.0 | +| 29 | 3.5 | 3.5 | 5.0 | 7.5 | +| 30 | 3.5 | 3.5 | 5.0 | 8.5 | +| 31 | 3.5 | 3.5 | 5.0 | 8.0 | +| 32 | 8.5 | 8.5 | | | +| 33 | 8.5 | 8.5 | | | +| 34 | 8.5 | 8.5 | | | +| 35 | 8.5 | 8.5 | | | +| 36 | 8.5 | 8.5 | | | +| 37 | 8.5 | 8.5 | | | +| 38 | 8.5 | 8.5 | | | +| 39 | 8.5 | 8.5 | | | +| 40 | 6.0 | 6.0 | | 6.5 | +| 41 | 6.0 | 6.0 | | 6.5 | +| 42 | 6.0 | 6.0 | | 6.5 | +| 43 | 6.0 | 6.0 | | 6.5 | +| 44 | 6.0 | 6.0 | | 6.5 | +| 45 | 4.0 | 4.0 | | 6.5 | +| 46 | 4.0 | 4.0 | | 6.5 | +| 47 | 4.0 | 4.0 | | 6.5 | +| 48 | 3.0 | 3.0 | 4.0 | 6.5 | + +Scatter plot titled 'NS\_05S Wideband A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 34 interlaced carriers (indices 15-48). The y-axis ranges from 0 to 10. The x-axis represents carrier indices from 15 to 48. Data points are colored by modulation: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.9.1.1-2 Wideband A-MPR + +Note : NS\_05S is equal to NS\_60. + +###### 6.1.3.9.1.3 Qualcomm's simulation results (R4-2316791) + +**Table 6.1.3.9.1.3-1: Simulation results for NS\_60 Full and partial allocations.** + +| NS_53
A-MPR | 20M | 20M | 40M | 40M | 60M | 60M | 80M | 80M | +|----------------|------|---------|------|---------|------|---------|------|---------| +| | Full | Partial | Full | Partial | Full | Partial | Full | Partial | +| QPSK | ≤7.5 | ≤7.6 | ≤7.0 | ≤7.3 | ≤6.7 | ≤7.4 | ≤6.4 | ≤7.4 | +| 16 QAM | ≤7.5 | ≤7.8 | ≤6.9 | ≤7.4 | ≤6.8 | ≤7.6 | ≤6.4 | ≤7.6 | +| 64 QAM | ≤7.5 | ≤8.0 | ≤7.0 | ≤7.6 | ≤6.8 | ≤7.8 | ≤6.5 | ≤7.8 | +| 256 QAM | ≤7.5 | ≤8.0 | ≤7.0 | ≤7.5 | ≤6.8 | ≤7.7 | ≤6.6 | ≤7.7 | + +The power class 5 PSSCH A-MPR in the table should be considered in the discussion of MPR requirements. + +##### 6.1.3.9.2 A-MPR for S-SSB transmission + +###### 6.1.3.9.2.1 LG Electronics' simulation results (R4-2315542) + +For NS\_60, Table 6.1.3.9.2.1-1 and Figure 6.1.3.9.2.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.9.2.1-1: NS\_60-S-SSB A-MPR simulation results for SL-U power class 5 + +| Scenario # | #1 | #2 | #3 | #4 | #5 | | | | | | | | | | | | | | | +|------------|-------|------|-------|------|------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------------| +| '20MHz' | 9.24 | 8.17 | 12.15 | 6.16 | 9.19 | | | | | | | | | | | | | | | +| Scenario # | #6 | #7 | #8 | #9 | #10 | #11 | | | | | | | | | | | | | | +| '40MHz' | 11.31 | 8.63 | 9.09 | 9.02 | 8.17 | 12.15 | | | | | | | | | | | | | | +| Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | | | | | | | | | +| '60MHz' | 9.29 | 7.05 | 7.87 | 6.15 | 6.20 | 9.21 | 6.20 | 9.21 | 7.67 | 6.25 | | | | | | | | | | +| Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | | +| '80MHz' | 10.34 | 6.86 | 8.81 | 5.70 | 7.67 | 6.08 | 6.19 | 9.19 | 6.11 | 6.15 | 6.23 | 9.09 | 8.92 | 6.11 | 7.97 | 6.13 | 7.51 | 6.23 | | +| Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | #55 | #56 | #57 | #58 #59 | +| '100MHz' | 10.92 | 6.67 | 9.86 | 5.49 | 9.44 | 5.56 | 7.59 | 6.17 | 6.22 | 9.19 | 5.89 | 4.50 | 5.39 | 6.18 | 6.21 | 9.20 | 6.14 | 9.18 | 10.54 7.21 | +| Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | #71 | #72 | #73 | #74 | #75 | #76 | #77 | | +| '100MHz' | 9.60 | 6.16 | 8.72 | 6.14 | 8.26 | 5.82 | 9.16 | 5.30 | 7.74 | 6.16 | 7.76 | 6.05 | 7.72 | 6.12 | 7.20 | 6.22 | 9.94 | 6.23 | | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 13. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds).](84b564808c370adacae8a814707fb071_img.jpg) + +| Test Scenario # | 20MHz back off [dB] | 40MHz back off [dB] | 60MHz back off [dB] | +|-----------------|---------------------|---------------------|---------------------| +| 1 | 9.24 | | | +| 2 | 8.17 | | | +| 3 | 12.15 | | | +| 4 | 6.16 | | | +| 5 | 9.19 | | | +| 6 | | 11.31 | | +| 7 | | 8.63 | | +| 8 | | 9.09 | | +| 9 | | 9.02 | | +| 10 | | 8.17 | | +| 11 | | 12.15 | | +| 12 | | | 9.29 | +| 13 | | | 7.05 | +| 14 | | | 7.87 | +| 15 | | | 6.15 | +| 16 | | | 6.20 | +| 17 | | | 9.21 | +| 18 | | | 6.20 | +| 19 | | | 9.21 | +| 20 | | | 7.67 | +| 21 | | | 6.25 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 13. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds). + +a. 20MHz, 40MHz, and 60MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' for 80MHz bandwidth. The y-axis is 'back off[dB]' from 0 to 11. The x-axis is 'Test Scenario #' from 22 to 39. Data points are blue triangles.](d461c6341beba90844ef785469cd757f_img.jpg) + +This scatter plot shows the transmit power back-off in dB for 1Tx Power class 5 SL-U at an 80MHz bandwidth across various test scenarios. The y-axis represents the back-off in dB, ranging from 0 to 11 in 0.5 dB increments. The x-axis represents the test scenario number, ranging from 22 to 39. The data points, represented by blue triangles, show a peak back-off of approximately 10.5 dB at scenario 22, which then fluctuates between 5.5 dB and 9.5 dB for the remaining scenarios. + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 22 | 10.5 | +| 23 | 7.0 | +| 24 | 8.8 | +| 25 | 5.5 | +| 26 | 7.8 | +| 27 | 6.0 | +| 28 | 6.0 | +| 29 | 9.5 | +| 30 | 6.0 | +| 31 | 6.0 | +| 32 | 6.0 | +| 33 | 9.2 | +| 34 | 9.0 | +| 35 | 6.0 | +| 36 | 8.0 | +| 37 | 6.0 | +| 38 | 7.5 | +| 39 | 6.0 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' for 80MHz bandwidth. The y-axis is 'back off[dB]' from 0 to 11. The x-axis is 'Test Scenario #' from 22 to 39. Data points are blue triangles. + +b. 80MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' for 100MHz bandwidth. The y-axis is 'back off[dB]' from 0 to 11.5. The x-axis is 'Test Scenario #' from 40 to 77. Data points are red triangles.](f78e0a777a9c5dc76cda197cbee0f206_img.jpg) + +This scatter plot shows the transmit power back-off in dB for 1Tx Power class 5 SL-U at a 100MHz bandwidth across various test scenarios. The y-axis represents the back-off in dB, ranging from 0 to 11.5 in 0.5 dB increments. The x-axis represents the test scenario number, ranging from 40 to 77. The data points, represented by red triangles, show a peak back-off of approximately 11.2 dB at scenario 40, with values generally fluctuating between 4.5 dB and 10.8 dB. + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 40 | 11.2 | +| 41 | 6.5 | +| 42 | 10.2 | +| 43 | 5.5 | +| 44 | 9.5 | +| 45 | 5.5 | +| 46 | 7.2 | +| 47 | 6.0 | +| 48 | 6.0 | +| 49 | 9.2 | +| 50 | 5.8 | +| 51 | 4.5 | +| 52 | 5.5 | +| 53 | 6.0 | +| 54 | 6.0 | +| 55 | 9.2 | +| 56 | 6.0 | +| 57 | 9.2 | +| 58 | 10.8 | +| 59 | 7.2 | +| 60 | 9.5 | +| 61 | 6.0 | +| 62 | 8.2 | +| 63 | 6.0 | +| 64 | 8.0 | +| 65 | 5.8 | +| 66 | 9.2 | +| 67 | 5.2 | +| 68 | 7.5 | +| 69 | 6.0 | +| 70 | 7.5 | +| 71 | 6.0 | +| 72 | 7.5 | +| 73 | 6.0 | +| 74 | 7.2 | +| 75 | 6.0 | +| 76 | 10.2 | +| 77 | 6.0 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' for 100MHz bandwidth. The y-axis is 'back off[dB]' from 0 to 11.5. The x-axis is 'Test Scenario #' from 40 to 77. Data points are red triangles. + +c. 100MHz + +Figure 6.1.3.9.2.1-1: NS\_60 S-SSB A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.9.2.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.9.2.1-2 : NS\_60 S-SSB A-MPR simulation results for SL-U power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|-----------------------------|---------------------------------------------------------|-------|-------|-------|-------|------|-------|------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous | 9.24 | 12.15 | 11.31 | 12.15 | 9.29 | 9.21 | 10.34 | 9.19 | 10.92 | 10.92 | +| Non-contiguous | - | - | - | - | 7.67 | 6.25 | 8.92 | 6.23 | 10.54 | 7.21 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the S-SSB A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.9.2.1-3 or Table 6.1.3.9.2.1-4 based on the simulation results when considering implementation margin. + +**Table 2-66: NS\_60 S-SSB A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation / (dB) | | | | | | | | | | +|-----------------------------|----------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous | ≤13.5 | ≤14.5 | ≤13.5 | ≤14.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | +| Non-contiguous | N/A | N/A | N/A | N/A | ≤10.0 | ≤9.0 | ≤11.5 | ≤9.0 | ≤13.0 | ≤10.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +**Table 2-67: NS\_60 S-SSB A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|-----------------------------|---------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous/Non-contiguous | ≤13.5 | ≤14.5 | ≤13.5 | ≤14.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +##### 6.1.3.9.3 A-MPR for PSFCH transmission + +###### 6.1.3.9.3.1 LG Electronics' simulation results (R4-2315542 and R4-2321771) + +For NS\_60, Table 6.1.3.9.3.1-1 shows the A-MPR simulation results for the scenarios. + +Table 6.1.3.9.3.1-1: NS\_60-PSFCH A-MPR simulation results for SL-U power class 5 + +| Scenario # | #1 | #2 | | | | | | | | | | | | | | | | | | +|------------|------|------|------|------|------|------|------|------|------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| '20MHz' | 8.40 | 7.83 | | | | | | | | | | | | | | | | | | +| Scenario # | #3 | #4 | | | | | | | | | | | | | | | | | | +| '40MHz' | 9.32 | 7.94 | | | | | | | | | | | | | | | | | | +| Scenario # | #5 | #6 | #7 | #8 | #9 | | | | | | | | | | | | | | | +| '60MHz' | 9.65 | 9.05 | 7.78 | 7.76 | 8.96 | | | | | | | | | | | | | | | +| Scenario # | #10 | #11 | #12 | #13 | #14 | #15 | #16 | #17 | #18 | | | | | | | | | | | +| '80MHz' | 9.43 | 9.83 | 9.01 | 7.71 | 8.56 | 7.61 | 9.82 | 9.00 | 8.95 | | | | | | | | | | | +| Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | +| '100MHz' | 9.55 | | | | | | | | | | | | | | | | | | | + +Table 6.1.3.9.3.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.9.3.1-2 : NS\_60 PSFCH A-MPR simulation results for SL-U power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|----------------------|---------------------------------------------------------|-------|-------|-------|--------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous | 8.40 | 9.32 | 9.83 | 9.43 | 9.55 | +| Non-contiguous | N/A | 9.63 | 9.82 | 8.34 | N/A | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the PSFCH A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.9.3.1-3 or Table 6.1.3.9.3.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.9.3.1-3 NS\_60 PSFCH A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|----------------------|---------------------------------------------------------|-------|-------|-------|--------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | +| Non-contiguous | N/A | ≤12.5 | ≤12.5 | ≤12.5 | N/A | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +**Table 6.1.3.9.3.1-4 NS\_60 PSFCH A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|---------------------------|---------------------------------------------------------|-------|-------|-------|--------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous/Non-contiguous | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | ≤12.5 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +#### 6.1.3.10 A-MPR for SL-U with NS\_61 + +##### 6.1.3.10.1 A-MPR for simultaneous PSSCH/PSCCH transmission + +###### 6.1.3.10.1.1 LG Electronics' simulation results (R4-2315542) + +For NS\_61, Table 6.1.3.10.1.1-1 and Figure 6.1.3.10.1.1-1 show the A-MPR simulation results for the scenarios. + +**Table 6.1.3.10.1.1-1: NS\_61-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| | | | | | | | | | | | | | | | | | | | | +|----------|------------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| '20MHz' | Scenario # | #1 | #7 | #2 | #8 | | | | | | | | | | | | | | | +| | 'QPSK' | 6.31 | 8.98 | 6.73 | 8.97 | | | | | | | | | | | | | | | +| | '16QAM' | 6.30 | 8.97 | 6.74 | 8.98 | | | | | | | | | | | | | | | +| | '64QAM' | 6.31 | 8.98 | 6.74 | 8.97 | | | | | | | | | | | | | | | +| | '256QAM' | 6.31 | 8.98 | 6.74 | 8.98 | | | | | | | | | | | | | | | +| '40MHz' | Scenario # | #3 | #9 | #13 | #30 | | | | | | | | | | | | | | | +| | 'QPSK' | 4.66 | 5.89 | 6.30 | 8.97 | | | | | | | | | | | | | | | +| | '16QAM' | 4.67 | 5.89 | 6.30 | 8.97 | | | | | | | | | | | | | | | +| | '64QAM' | 4.67 | 5.89 | 6.30 | 8.97 | | | | | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.89 | 6.30 | 8.97 | | | | | | | | | | | | | | | +| '60MHz' | Scenario # | #4 | #10 | #14 | #31 | #15 | #32 | #16 | #33 | | | | | | | | | | | +| | 'QPSK' | 5.06 | 5.47 | 6.73 | 9.44 | 4.67 | 5.89 | 6.73 | 8.95 | | | | | | | | | | | +| | '16QAM' | 5.07 | 5.47 | 6.73 | 9.43 | 4.67 | 5.89 | 6.73 | 9.41 | | | | | | | | | | | +| | '64QAM' | 5.07 | 5.47 | 6.73 | 9.43 | 4.67 | 5.89 | 6.73 | 9.42 | | | | | | | | | | | +| | '256QAM' | 5.47 | 5.47 | 6.73 | 9.43 | 5.47 | 5.88 | 6.73 | 9.42 | | | | | | | | | | | +| '80MHz' | Scenario # | #5 | #11 | #17 | #34 | #18 | #35 | #19 | #36 | #20 | #37 | #21 | #38 | | | | | | | +| | 'QPSK' | 4.67 | 5.47 | 6.74 | 9.44 | 4.67 | 5.89 | 5.06 | 5.47 | 6.73 | 9.42 | 3.52 | 5.88 | | | | | | | +| | '16QAM' | 4.67 | 5.47 | 6.73 | 9.43 | 4.66 | 5.89 | 5.06 | 5.47 | 6.73 | 9.42 | 3.52 | 5.88 | | | | | | | +| | '64QAM' | 4.67 | 5.47 | 6.73 | 9.43 | 4.67 | 5.89 | 4.67 | 5.47 | 6.73 | 9.42 | 3.52 | 5.88 | | | | | | | +| | '256QAM' | 5.47 | 5.47 | 6.73 | 9.43 | 5.47 | 5.89 | 5.47 | 5.47 | 6.73 | 9.42 | 5.47 | 5.88 | | | | | | | +| '100MHz' | Scenario # | #6 | #12 | #22 | #39 | #23 | #40 | #24 | #41 | #25 | #42 | #26 | #43 | #27 | #44 | #28 | #45 | #29 | #46 | +| | 'QPSK' | 4.67 | 5.47 | 6.73 | 9.43 | 4.67 | 5.89 | 4.66 | 5.47 | 4.66 | 5.47 | 6.73 | 9.42 | 3.52 | 5.88 | 2.81 | 3.89 | 6.73 | 8.96 | +| | '16QAM' | 4.67 | 5.47 | 6.73 | 9.43 | 4.66 | 5.89 | 5.06 | 5.47 | 4.67 | 5.47 | 6.73 | 9.42 | 3.52 | 5.88 | 2.81 | 3.89 | 6.73 | 9.41 | +| | '64QAM' | 4.67 | 5.47 | 6.74 | 9.44 | 4.67 | 6.30 | 4.66 | 5.47 | 4.66 | 5.47 | 6.73 | 9.42 | 3.52 | 5.88 | 3.16 | 3.89 | 6.73 | 9.42 | +| | '256QAM' | 5.47 | 5.47 | 6.73 | 9.43 | 5.47 | 6.31 | 5.47 | 5.47 | 5.47 | 5.47 | 6.73 | 9.42 | 5.47 | 5.88 | 5.47 | 5.47 | 6.73 | 9.41 | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 10. The x-axis is 'Test Scenario #' from 1 to 46. Data points for QPSK (red circle), 16QAM (blue asterisk), 64QAM (green diamond), and 256QAM (black triangle) are plotted. Most points are between 4.5 and 9.5 dB, with some outliers reaching 10 dB.](eec47775133f5c3b02d42ab8f85599ce_img.jpg) + +The figure is a scatter plot titled "Tx Power Back Off for 1Tx Power class 5 SL-U". The y-axis is labeled "back off[dB]" and ranges from 0 to 10 in increments of 0.5. The x-axis is labeled "Test Scenario #" and ranges from 1 to 46. The plot shows data points for four different modulation schemes: QPSK (represented by a red circle), 16QAM (represented by a blue asterisk), 64QAM (represented by a green diamond), and 256QAM (represented by a black triangle). The data points are scattered across the plot, with most values between 4.5 dB and 9.5 dB. There are several points at 10 dB, particularly for 256QAM and QPSK. The legend is located in the bottom right corner of the plot area. + +| Test Scenario # | QPSK [dB] | 16QAM [dB] | 64QAM [dB] | 256QAM [dB] | +|-----------------|-----------|------------|------------|-------------| +| 1 | | | | 6.5 | +| 2 | | | | 6.5 | +| 3 | 4.5 | 4.5 | 4.5 | 5.5 | +| 4 | 5.0 | 5.0 | 5.0 | 5.5 | +| 5 | 4.5 | 4.5 | 4.5 | 5.5 | +| 6 | 4.5 | 4.5 | 4.5 | 5.5 | +| 7 | | | | 9.0 | +| 8 | | | | 9.0 | +| 9 | | | | 5.5 | +| 10 | | | | 5.5 | +| 11 | | | | 5.5 | +| 12 | | | | 5.5 | +| 13 | | | | 6.0 | +| 14 | | | | 6.5 | +| 15 | 4.5 | 4.5 | 4.5 | 5.5 | +| 16 | | | | 6.5 | +| 17 | | | | 6.5 | +| 18 | 4.5 | 4.5 | 4.5 | 5.5 | +| 19 | 5.0 | 5.0 | 5.0 | 5.5 | +| 20 | | | | 6.5 | +| 21 | 3.5 | 3.5 | 3.5 | 5.5 | +| 22 | | | | 6.5 | +| 23 | | | | 5.5 | +| 24 | 5.0 | 5.0 | 5.0 | 5.5 | +| 25 | 4.5 | 4.5 | 4.5 | 5.5 | +| 26 | | | | 6.5 | +| 27 | | | | 5.5 | +| 28 | | | | 5.5 | +| 29 | | | | 6.5 | +| 30 | | | | 9.0 | +| 31 | | | | 9.5 | +| 32 | | | | 9.5 | +| 33 | 9.0 | 9.0 | 9.0 | 9.5 | +| 34 | | | | 9.5 | +| 35 | | | | 5.5 | +| 36 | | | | 5.5 | +| 37 | | | | 5.5 | +| 38 | | | | 9.5 | +| 39 | | | | 9.5 | +| 40 | | | | 6.0 | +| 41 | | | | 5.5 | +| 42 | | | | 5.5 | +| 43 | | | | 9.5 | +| 44 | | | | 5.5 | +| 45 | | | | 5.5 | +| 46 | 9.0 | 9.0 | 9.0 | 9.5 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' from 0 to 10. The x-axis is 'Test Scenario #' from 1 to 46. Data points for QPSK (red circle), 16QAM (blue asterisk), 64QAM (green diamond), and 256QAM (black triangle) are plotted. Most points are between 4.5 and 9.5 dB, with some outliers reaching 10 dB. + +Figure 6.1.3.10.1.1-1: NS\_61-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.10.1.1-2 shows the maximum value of simulation results considering Full/Partial RB allocation. + +**Table 6.1.3.10.1.1-2 : NS\_61-PSSCH/PSCCH A-MPR simulation results for SL-U power class 5** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| CP-OFDM | QPSK | 6.74 | 9.44 | 4.67 | 5.89 | 5.06 | 5.47 | 4.67 | 5.47 | 4.67 | 5.47 | +| | 16 QAM | 6.74 | 9.43 | 4.67 | 5.89 | 5.07 | 5.47 | 4.67 | 5.47 | 4.67 | 5.47 | +| | 64 QAM | 6.74 | 9.44 | 4.67 | 6.30 | 5.07 | 5.47 | 4.67 | 5.47 | 4.67 | 5.47 | +| | 256 QAM | 6.74 | 9.43 | 5.47 | 6.31 | 5.47 | 5.47 | 5.47 | 5.47 | 5.47 | 5.47 | + +For NS\_61, the maximum output power is limited with 14dBm. Therefore, basically, A-MPR should be met with the following equation considering power class 5, 20dBm. + +$$\text{NS\_61 A-MPR} = \max\{\text{Table 6.1.3.10.1.1-2} + \text{implementation margin, 6 dB}\}.$$ + +Based on the results, Table 6.1.3.10.1.1-3 can be considered for NS\_61 A-MPR for SL-U UE power class 5. + +**Table 6.1.3.10.1.1-3. NS\_61 additional maximum power reduction (A-MPR) for SL-U UE power class 5** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| CP-OFDM | QPSK | ≤ 7.5 | ≤ 10.0 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 16 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 64 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 256 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. +NOTE 2: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies + +###### 6.1.3.10.1.2 + +###### OPPO's simulation results (R4-2316119) + +The A-MPR requirement is captured in sub-clause 6.2F.3.10 and the requirement is differentiated by different channel bandwidth as captured below: + +**Table 6.1.3.10.1.1-1 A-MPR for single CC** + +| case | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | +|--------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| QPSK | 3.2 | 3.1 | 3.2 | 3.2 | 3.2 | 3.2 | 3.2 | 3.2 | 3.1 | 3.3 | 3.2 | 3.2 | 3.3 | 3.2 | +| 16QAM | 3.7 | 3.6 | 3.7 | 3.7 | 3.7 | 3.7 | 3.6 | 3.2 | 3.1 | 3.3 | 3.2 | 3.2 | 3.3 | 3.2 | +| 64QAM | 5.0 | 5.2 | 5.1 | 5.0 | 5.2 | 5.1 | 5.1 | 4.4 | 4.3 | 4.1 | 4.4 | 4.1 | 3.9 | 4.0 | +| 256QAM | 8.8 | 8.6 | 8.6 | 8.8 | 8.6 | 8.5 | 8.7 | 7.9 | 7.5 | 7.6 | 7.9 | 6.6 | 6.5 | 6.8 | + +The wide-band operation simulation result is further provided below: + +Table 6.1.3.10.1.1-2 A-MPR for wideband + +| | Bitmap | 10 | 100 | 110 | 010 | 1100 | 1000 | 1110 | 0100 | 0110 | 10000 | 11000 | 11100 | 11110 | 01000 | 01100 | 01110 | 00100 | +|------------|--------|-----|-----|-----|-----|------|------|------|------|------|-------|-------|-------|-------|-------|-------|-------|-------| +| Contiguous | QPSK | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | 2.8 | +| | 16QAM | 3.5 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.7 | 3.5 | 3.6 | 3.5 | 3.6 | 3.5 | 3.6 | 3.7 | 3.6 | +| | 64QAM | 5.1 | 5.1 | 4.8 | 5.2 | 4.7 | 5.1 | 4.9 | 5.1 | 4.9 | 5.1 | 4.7 | 4.8 | 5.0 | 5.1 | 4.8 | 5.0 | 5.2 | +| | 256QAM | 7.4 | 7.5 | 7.7 | 8.5 | 7.3 | 7.4 | 8.0 | 7.5 | 8.5 | 7.4 | 7.3 | 7.6 | 8.0 | 7.4 | 7.7 | 8.5 | 8.5 | +| Interlace | QPSK | 2.6 | 2.6 | 2.7 | 2.8 | 2.6 | 2.6 | 2.6 | 2.6 | 2.6 | 2.6 | 2.7 | 2.7 | 2.7 | 2.6 | 2.7 | 2.8 | 2.6 | +| | 16QAM | 2.9 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 2.9 | 3.0 | 3.0 | 2.8 | 2.9 | 3.0 | 3.0 | 2.8 | +| | 64QAM | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.1 | 4.1 | 4.2 | 4.1 | 4.2 | 4.1 | 4.0 | 4.1 | 4.2 | 4.1 | 4.1 | +| | 256QAM | 6.5 | 6.6 | 6.8 | 6.6 | 6.8 | 6.6 | 6.7 | 6.6 | 6.8 | 6.6 | 6.8 | 6.7 | 6.6 | 6.6 | 6.8 | 6.7 | 6.5 | + +![Scatter plot titled 'NS_06S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 subcarriers. The y-axis ranges from 0.0 to 10.0. The x-axis represents subcarriers 1 through 14. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](7f228001c8c028ac077fb5def89326e8_img.jpg) + +| Subcarrier | QPSK | 16QAM | 64QAM | 256QAM | +|------------|------|-------|-------|--------| +| 1 | 3.2 | 3.8 | 5.0 | 8.8 | +| 2 | 3.1 | 3.7 | 5.3 | 8.6 | +| 3 | 3.2 | 3.8 | 5.1 | 8.6 | +| 4 | 3.2 | 3.8 | 5.0 | 8.8 | +| 5 | 3.2 | 3.8 | 5.3 | 8.6 | +| 6 | 3.2 | 3.8 | 5.1 | 8.6 | +| 7 | 3.2 | 3.8 | 5.3 | 8.8 | +| 8 | 3.2 | 3.8 | 4.4 | 8.0 | +| 9 | 3.1 | 3.7 | 4.3 | 7.6 | +| 10 | 3.2 | 3.8 | 4.2 | 7.7 | +| 11 | 3.2 | 3.8 | 4.4 | 7.9 | +| 12 | 3.2 | 3.8 | 4.1 | 6.6 | +| 13 | 3.2 | 3.8 | 4.0 | 6.5 | +| 14 | 3.2 | 3.8 | 4.1 | 6.8 | + +Scatter plot titled 'NS\_06S Single CC A-MPR' showing A-MPR values for different modulation schemes (QPSK, 16QAM, 64QAM, 256QAM) across 14 subcarriers. The y-axis ranges from 0.0 to 10.0. The x-axis represents subcarriers 1 through 14. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.10.1.1-1 Single CC A-MPR + +![Scatter plot titled 'NS_06S WidebandA-MPR' showing A-MPR values for 34 scenarios across four modulation schemes: QPSK, 16QAM, 64QAM, and 256QAM. The y-axis ranges from 0.0 to 9.0. The x-axis is labeled 1 to 34. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow).](8e6c3e68ec4b938b0f85a21c61d226df_img.jpg) + +| Scenario | QPSK | 16QAM | 64QAM | 256QAM | +|----------|------|-------|-------|--------| +| 1 | 2.8 | 3.5 | 5.0 | 7.5 | +| 2 | 2.8 | 3.5 | 5.0 | 7.5 | +| 3 | 2.8 | 3.5 | 4.8 | 7.8 | +| 4 | 2.8 | 3.5 | 5.2 | 8.5 | +| 5 | 2.8 | 3.5 | 4.8 | 7.5 | +| 6 | 2.8 | 3.5 | 5.0 | 7.5 | +| 7 | 2.8 | 3.5 | 4.8 | 8.0 | +| 8 | 2.8 | 3.5 | 5.0 | 7.5 | +| 9 | 2.8 | 3.5 | 4.8 | 8.5 | +| 10 | 2.8 | 3.5 | 5.0 | 7.5 | +| 11 | 2.8 | 3.5 | 4.8 | 7.5 | +| 12 | 2.8 | 3.5 | 4.8 | 7.8 | +| 13 | 2.8 | 3.5 | 5.0 | 8.0 | +| 14 | 2.8 | 3.5 | 5.0 | 7.5 | +| 15 | 2.8 | 3.5 | 4.8 | 7.8 | +| 16 | 2.8 | 3.5 | 4.8 | 8.5 | +| 17 | 2.8 | 3.5 | 5.2 | 8.5 | +| 18 | 2.8 | 3.0 | 4.0 | 6.5 | +| 19 | 2.8 | 3.0 | 4.0 | 6.5 | +| 20 | 2.8 | 3.0 | 4.2 | 6.8 | +| 21 | 2.8 | 3.0 | 4.0 | 6.5 | +| 22 | 2.8 | 3.0 | 4.2 | 6.8 | +| 23 | 2.8 | 3.0 | 4.0 | 6.5 | +| 24 | 2.8 | 3.0 | 4.0 | 6.5 | +| 25 | 2.8 | 3.0 | 4.0 | 6.5 | +| 26 | 2.8 | 3.0 | 4.2 | 6.8 | +| 27 | 2.8 | 3.0 | 4.0 | 6.5 | +| 28 | 2.8 | 3.0 | 4.2 | 6.8 | +| 29 | 2.8 | 3.0 | 4.0 | 6.5 | +| 30 | 2.8 | 3.0 | 4.0 | 6.5 | +| 31 | 2.8 | 3.0 | 4.0 | 6.5 | +| 32 | 2.8 | 3.0 | 4.2 | 6.8 | +| 33 | 2.8 | 3.0 | 4.0 | 6.5 | +| 34 | 2.8 | 3.0 | 4.0 | 6.5 | + +Scatter plot titled 'NS\_06S WidebandA-MPR' showing A-MPR values for 34 scenarios across four modulation schemes: QPSK, 16QAM, 64QAM, and 256QAM. The y-axis ranges from 0.0 to 9.0. The x-axis is labeled 1 to 34. The legend indicates: QPSK (blue), 16QAM (orange), 64QAM (grey), and 256QAM (yellow). + +Figure 6.1.3.10.1.1-2 Wideband A-MPR + +##### 6.1.3.10.2 A-MPR for S-SSB transmission + +###### 6.1.3.10.2.1 LG Electronics' simulation results (R4-2315542) + +For NS\_61, Table 6.1.3.10.2.1-1 and Figure 6.1.3.10.2.1-1 show the A-MPR simulation results for the scenarios. + +Table 6.1.3.10.2.1-1: NS\_61-S-SSB A-MPR simulation results for SL-U power class 5 + +| Scenario # | #1 | #2 | #3 | #4 | #5 | | | | | | | | | | | | | | | +|------------|-------|------|-------|------|-------|-------|------|-------|------|-------|------|-------|------|------|------|-------|-------|-------|------------| +| '20MHz' | 9.24 | 9.14 | 13.08 | 7.15 | 10.19 | | | | | | | | | | | | | | | +| Scenario # | #6 | #7 | #8 | #9 | #10 | #11 | | | | | | | | | | | | | | +| '40MHz' | 11.18 | 9.58 | 10.10 | 9.02 | 9.23 | 13.09 | | | | | | | | | | | | | | +| Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | | | | | | | | | +| '60MHz' | 9.84 | 7.13 | 8.68 | 7.13 | 7.13 | 10.21 | 7.12 | 10.20 | 8.88 | 7.69 | | | | | | | | | | +| Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | | +| '80MHz' | 10.20 | 8.27 | 9.35 | 6.64 | 8.49 | 7.23 | 7.20 | 10.22 | 5.69 | 7.14 | 7.21 | 10.21 | 9.98 | 7.65 | 9.34 | 7.52 | 9.37 | 7.37 | | +| Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | #55 | #56 | #57 | #58 #59 | +| '100MHz' | 11.00 | 8.15 | 10.53 | 7.12 | 9.82 | 6.71 | 8.24 | 7.20 | 7.14 | 10.13 | 5.89 | 5.43 | 5.38 | 7.07 | 7.21 | 10.23 | 7.22 | 10.11 | 10.29 8.04 | +| Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | #71 | #72 | #73 | #74 | #75 | #76 | #77 | | +| '100MHz' | 9.71 | 7.67 | 9.11 | 7.74 | 9.93 | 7.32 | 9.09 | 6.12 | 9.01 | 7.48 | 8.77 | 7.30 | 9.14 | 7.23 | 8.29 | 7.18 | 10.66 | 7.41 | | + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 14. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds).](8b8084b35a85fbded65b73409354c3eb_img.jpg) + +| Test Scenario # | 20MHz back off [dB] | 40MHz back off [dB] | 60MHz back off [dB] | +|-----------------|---------------------|---------------------|---------------------| +| 1 | 9.24 | | | +| 2 | 9.14 | | | +| 3 | 13.08 | | | +| 4 | 7.15 | | | +| 5 | 10.19 | | | +| 6 | | 11.18 | | +| 7 | | 9.58 | | +| 8 | | 10.10 | | +| 9 | | 9.02 | | +| 10 | | 9.23 | | +| 11 | | 13.09 | | +| 12 | | | 9.84 | +| 13 | | | 7.13 | +| 14 | | | 8.68 | +| 15 | | | 7.13 | +| 16 | | | 7.13 | +| 17 | | | 10.21 | +| 18 | | | 7.12 | +| 19 | | | 10.20 | +| 20 | | | 8.88 | +| 21 | | | 7.69 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U'. The y-axis is 'back off[dB]' ranging from 0 to 14. The x-axis is 'Test Scenario #' ranging from 1 to 21. Data points are plotted for 20MHz (red circles), 40MHz (blue asterisks), and 60MHz (purple diamonds). + +a. 20MHz, 40MHz, and 60MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 11 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by right-pointing triangles.](be2d9105109f6a87907ab68cb88548d9_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +80MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 22 | 10.5 | +| 23 | 8.5 | +| 24 | 9.5 | +| 25 | 6.5 | +| 26 | 8.5 | +| 27 | 7.5 | +| 28 | 7.5 | +| 29 | 10.5 | +| 30 | 5.5 | +| 31 | 7.5 | +| 32 | 7.5 | +| 33 | 10.5 | +| 34 | 10.5 | +| 35 | 8.0 | +| 36 | 9.5 | +| 37 | 8.0 | +| 38 | 9.5 | +| 39 | 7.5 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 80MHz bandwidth. The y-axis ranges from 0 to 11 dB, and the x-axis ranges from 22 to 39 scenarios. Data points are represented by right-pointing triangles. + +b. 80MHz + +![Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by upward-pointing triangles.](4895f9f74a63a7069cb8236fda8ff984_img.jpg) + +Tx Power Back Off for 1Tx Power class 5 SL-U + +back off[dB] + +Test Scenario # + +100MHz + +| Test Scenario # | back off[dB] | +|-----------------|--------------| +| 40 | 11.5 | +| 41 | 8.5 | +| 42 | 10.5 | +| 43 | 7.5 | +| 44 | 10.0 | +| 45 | 7.0 | +| 46 | 8.5 | +| 47 | 7.5 | +| 48 | 7.5 | +| 49 | 10.5 | +| 50 | 5.5 | +| 51 | 5.0 | +| 52 | 5.0 | +| 53 | 7.5 | +| 54 | 7.5 | +| 55 | 10.5 | +| 56 | 7.5 | +| 57 | 10.5 | +| 58 | 10.5 | +| 59 | 8.5 | +| 60 | 10.0 | +| 61 | 8.0 | +| 62 | 9.5 | +| 63 | 8.0 | +| 64 | 10.5 | +| 65 | 7.5 | +| 66 | 9.5 | +| 67 | 6.0 | +| 68 | 9.5 | +| 69 | 8.0 | +| 70 | 9.0 | +| 71 | 7.5 | +| 72 | 9.5 | +| 73 | 7.5 | +| 74 | 8.5 | +| 75 | 7.5 | +| 76 | 11.5 | +| 77 | 8.0 | + +Scatter plot titled 'Tx Power Back Off for 1Tx Power class 5 SL-U' showing back off [dB] vs Test Scenario # for 100MHz bandwidth. The y-axis ranges from 0 to 12 dB, and the x-axis ranges from 40 to 77 scenarios. Data points are represented by upward-pointing triangles. + +c. 100MHz + +Figure 6.1.3.10.2.1-1: NS\_61 S-SSB A-MPR simulation results for SL-U power class 5 + +Table 6.1.3.10.2.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.10.2.1-2 : NS\_61 S-SSB A-MPR simulation results for SL-U power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|-----------------------------|---------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous | 9.24 | 13.08 | 11.18 | 13.09 | 9.84 | 10.21 | 10.20 | 10.22 | 11.00 | 11.00 | +| Non-contiguous | - | - | - | - | 8.88 | 7.69 | 9.98 | 7.65 | 10.66 | 8.04 | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the S-SSB A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.10.2.1-3 or Table 6.1.3.10.2.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.10.2.1-3: NS\_61 S-SSB A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation / (dB) | | | | | | | | | | +|-----------------------------|----------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous | ≤13.5 | ≤15.5 | ≤13.5 | ≤15.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | +| Non-contiguous | N/A | N/A | N/A | N/A | ≤11.5 | ≤11.0 | ≤12.5 | ≤11.0 | ≤13.0 | ≤11.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +**Table 6.1.3.10.2.1-4: NS\_61 S-SSB A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|-----------------------------|---------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|--------|-------| +| | 20MHz | | 40MHz | | 60MHz | | 80MHz | | 100MHz | | +| # of S-SSB repetition/RBset | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | > 2 | 2 | +| Contiguous/Non-contiguous | ≤13.5 | ≤15.5 | ≤13.5 | ≤15.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | ≤13.5 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +##### 6.1.3.10.3 A-MPR for PSFCH transmission + +###### 6.1.3.10.3.1 LG Electronics' simulation results (R4-2315542 and R4-2321771) + +For NS\_61, Table 6.1.3.10.3.1-1 shows the A-MPR simulation results for the scenarios. + +**Table 6.1.3.10.3.1-1: NS\_61-PSFCH A-MPR simulation results for SL-U power class 5** + +| | | | | | | | | | | | | | | | | | | | | +|-------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| +| Scenario # | #1 | #2 | | | | | | | | | | | | | | | | | | +| '20MHz' | 8.28 | 8.71 | | | | | | | | | | | | | | | | | | +| Scenario # | #3 | #4 | | | | | | | | | | | | | | | | | | +| '40MHz' | 10.21 | 8.28 | | | | | | | | | | | | | | | | | | +| Scenario # | #5 | #6 | #7 | #8 | #9 | | | | | | | | | | | | | | | +| '60MHz' | 10.63 | 9.76 | 8.68 | 8.62 | 9.55 | | | | | | | | | | | | | | | +| Scenario # | #10 | #11 | #12 | #13 | #14 | #15 | #16 | #17 | #18 | | | | | | | | | | | +| '80MHz' | 10.19 | 10.69 | 9.74 | 8.72 | 8.56 | 8.73 | 10.50 | 9.56 | 9.56 | | | | | | | | | | | +| Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | +| '100MHz' | 10.29 | | | | | | | | | | | | | | | | | | | + +Table 6.1.3.10.3.1-2 shows the maximum value of simulation results considering combinations of Outer/Inner sub-band configuration. + +**Table 6.1.3.10.3.1-2 : NS\_61 PSFCH A-MPR simulation results for SL-U power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|----------------------|---------------------------------------------------------|-------|-------|-------|--------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous | 8.73 | 10.21 | 10.69 | 10.19 | 10.29 | +| Non-contiguous | N/A | 9.56 | 10.50 | 9.94 | N/A | + +Considering the inner RB set bitmaps and the outer RB set bitmaps, the PSFCH A-MPR for SL-U power class 5 can be proposed as Table 6.1.3.10.3.1-3 or Table 6.1.3.10.3.1-4 based on the simulation results when considering implementation margin. + +**Table 6.1.3.10.3.1-3 NS\_61 PSFCH A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|----------------------|---------------------------------------------------------|-------------|-------------|-------------|-------------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | +| Non-contiguous | N/A | $\leq 11.5$ | $\leq 12.5$ | $\leq 12.5$ | N/A | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +**Table 6.1.3.10.3.1-4 NS\_61 PSFCH A-MPR for SL-U UE power class 5** + +| RB set configuration | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | +|---------------------------|---------------------------------------------------------|-------------|-------------|-------------|-------------| +| | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | +| Contiguous/Non-contiguous | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously or non-contiguously allocated in the channel. + +### 6.1.4 Configured transmitted power for NR SL-U + +The configured transmitted power for NR-U is defined in clause 6.2F.4 of TS 38.101-1 and the normal NR requirement in clause 6.2.4 of TS 38.101-1 apply. For NR V2X, $P_{CMAX}$ is defined for PSSCH/PSCCH, S-SSB and PSFCH in clause 6.2E.4 specifically. + +It has been agreed to reuse the NR V2X Configured transmitted power requirements in 38.101-1 clause 6.2E.4 for NR SL-U. + +### 6.1.5 Minimum output power for NR SL-U + +The Minimum output power of NR-U is defined in clause 6.3F.1 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC minimum requirements in 38.101-1 clause 6.3.1 for NR SL-U. + +### 6.1.6 Transmit OFF power for NR SL-U + +The Transmit OFF power of NR-U is defined in clause 6.3F.2 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC minimum requirements in 38.101-1 clause 6.3.2 for NR SL-U. + +### 6.1.7 ON/OFF time mask for NR SL-U + +Definition of ON/OFF time mask can be divided into two parts. First part defines the transition from OFF to ON and the second part transition from ON to OFF. For the ON to OFF part, it was agreed that 10us transient period is located inside the guard period. For the OFF to ON part at the beginning of the transmission, whether to put the whole 15 us transient period inside the CP-E or to reuse the NR-U mask that only put 10us inside the CP-E was discussed and following this discussion, and information from RAN1 that 16us or 25us LBT time preceding the CP-E already includes 5us ramp-up time, it was agreed to reuse the NR-U approach where first 5us of the OFF to ON transient period is located before the CP-E. + +ON/OFF masks for NR SL-U PSSCH and PSCCH and S-SSB that are in line with the above agreements are shown in figures below. + +![Figure 6.1.7-1: General ON/OFF time mask for SL-U PSSCH and PSCCH. The diagram shows a sequence of slots: N0 Slot, CP-E, N+1 Slot (incl. transmission gap), Guard Period, and N+2 Slot. Key timing points are marked: 'End of OFF Power Requirement' at the start of N0 Slot, 'Start of N+1 power' at the start of CP-E, 'End of N+1 power' at the end of N+1 Slot, and 'Start of OFF power requirement' at the start of N+2 Slot. Transient periods of 5us and 10us are indicated between these points.](da06747b80ea0d71593cbbd4c2ea89aa_img.jpg) + +Figure 6.1.7-1: General ON/OFF time mask for SL-U PSSCH and PSCCH. The diagram shows a sequence of slots: N0 Slot, CP-E, N+1 Slot (incl. transmission gap), Guard Period, and N+2 Slot. Key timing points are marked: 'End of OFF Power Requirement' at the start of N0 Slot, 'Start of N+1 power' at the start of CP-E, 'End of N+1 power' at the end of N+1 Slot, and 'Start of OFF power requirement' at the start of N+2 Slot. Transient periods of 5us and 10us are indicated between these points. + +**Figure 6.1.7-1 General ON/OFF time mask for SL-U PSSCH and PSCCH** + +![Figure 6.1.7-2: ON/OFF time mask for SL-U S-SSB. The diagram shows a sequence of slots: N0 Slot, CP-E, PSBCH, S-PSS, S-PSS, S-SSS, S-SSS, PSBCH, Guard Period, and N+2 Slot. The middle section is labeled N+1 Slot. Key timing points are marked: 'End of OFF Power Requirement' at the start of N0 Slot, 'Start of ON power for N+1 slot with S-SSB' at the start of CP-E, 'End of ON power for N+1 slot with S-SSB' at the end of PSBCH, and 'Start of OFF power requirement' at the start of N+2 Slot. Transient periods of 5us and 10us are indicated between these points.](7f16ae750ce9a533b0bd301dd986355e_img.jpg) + +Figure 6.1.7-2: ON/OFF time mask for SL-U S-SSB. The diagram shows a sequence of slots: N0 Slot, CP-E, PSBCH, S-PSS, S-PSS, S-SSS, S-SSS, PSBCH, Guard Period, and N+2 Slot. The middle section is labeled N+1 Slot. Key timing points are marked: 'End of OFF Power Requirement' at the start of N0 Slot, 'Start of ON power for N+1 slot with S-SSB' at the start of CP-E, 'End of ON power for N+1 slot with S-SSB' at the end of PSBCH, and 'Start of OFF power requirement' at the start of N+2 Slot. Transient periods of 5us and 10us are indicated between these points. + +**Figure 6.1.7-2 ON/OFF time mask for SL-U S-SSB** + +### 6.1.8 Power control for NR SL-U + +The power control of NR-U is defined in clause 6.3F.4 of TS 38.101-1 and the power control of NR V2X is defined in clause 6.3E.4. Since only absolute power control requirement is defined for NR V2X, it has been agreed that only absolute power control requirement is defined for NR SL-U. + +During the NR-U discussion it was agreed that absolute requirement applies at the start of a contiguous transmission or non-contiguous transmission with a transmission gap larger than 40 ms. Gap duration of 40ms is larger than 20ms, which is defined in generic requirements in Clause 6.3.4.2. of TS 38.101-1. This extension of gap duration is in line with eLAA requirement in 36.101 and is defined to maintain power control accuracy over longer periods of no transmission due to the uncertainty introduced by LBT. Therefore NR SL-U can reuse NR-U absolute power control requirement as defined in Clause 6.3F.4.2. + +### 6.1.9 Transmit signal quality for NR SL-U + +#### 6.1.9.1 Frequency Error + +The Frequency error for NR-U is defined in clause 6.4F.1 of TS 38.101-1 and the normal NR requirement in clause 6.4.1 of TS 38.101-1 apply. For NR V2X, frequency error is defined in clause 6.4E.1 as $\pm 0.1$ PPM accuracy observed over a period of 1 ms against GNSS.” + +It has been agreed to reuse the NR V2X Frequency error requirements in 38.101-1 clause 6.4E.1 for NR SL-U. + +#### 6.1.9.2 EVM + +The EVM of NR-U is defined in clause 6.4F.2 of TS 38.101-1 and the normal NR requirement in clause 6.4.2.1 of TS 38.101-1 apply. For NR V2X, EVM is defined in clause 6.4E.2.2 with other than the Pi/2-BPSK modulation, which is not supported for NR V2X. + +It has been agreed to reuse the NR V2X EVM requirements in 38.101-1 clause 6.4E.2.2 for NR SL-U. + +- For NR V2X the EVM requirements in clause 6.4.2.1 are valid for PSCCH, PSSCH and PSBCH physical channels with other than pi/2-BPSK modulation, which is not supported for NR V2X, and excluding the guard symbol at the end of transmitted slots + +#### 6.1.9.3 Carrier Leakage + +The Carrier Leakage of NR-U is defined in clause 6.4.2.2 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC carrier leakage requirements in 38.101-1 clause 6.4.2.2 for NR SL-U. + +#### 6.1.9.4 Equalizer spectrum flatness + +The Equalizer spectrum flatness of NR-U is referred to clause 6.4.2.4 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC Equalizer spectrum flatness requirements in 38.101-1 clause 6.4.2.4 for NR SL-U. + +#### 6.1.9.5 In-band Emission + +The In-band Emission of NR-U is defined in clause 6.4F.2.3 of TS 38.101-1. For NR V2X, In-band Emission is defined in clause 6.4E.2.4 where normal NR requirement of clause 6.4.2.3 apply. + +It has been agreed to reuse the NR-U In-band emission requirements in 38.101-1 Table 6.4F.2.3-1 for NR SL-U. Minimum requirements for in-band emissions for NR SL-U PSCCH, PSSCH and PSBCH transmissions over the measurement interval that takes into account guard period at the end of the transmit slot. + +### 6.1.10 Spectrum emission mask for NR SL-U + +#### 6.1.10.1 Occupied Bandwidth + +The Occupied Bandwidth of NR-U is defined in clause 6.5.1 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC Occupied Bandwidth requirements in 38.101-1 clause 6.5.1 for NR SL-U. + +#### 6.1.10.2 SEM + +The SEM of NR-U is defined in clause 6.5F.2.2 of TS 38.101-1. For NR V2X, In-band Emission is defined in clause 6.5E.2.2 where normal NR requirement of clause 6.5.2.2 apply. + +It has been agreed to reuse the NR-U SEM requirements in 38.101-1 Table 6.4F.2.3-1 for NR SL-U. + +#### 6.1.10.3 A-SEM + +Additional spectrum emission mask requirements are not defined for NR-U. + +It is agreed not to define A-SEM requirements for NR SL-U when operating in bands n46, n96 and n102. + +### 6.1.11 ACLR requirements for NR SL-U + +The ACLR of NR-U is defined in clause 6.5F.2.4 of TS 38.101-1. For NR V2X, ACLR is defined in clause 6.5E.2.4 where normal NR requirement of clause 6.5.2.4 apply. The ACLR requirement was optimized for operation in un-licensed band during the development of the NR-U requirements. + +It has been agreed to reuse the NR-U ACLR requirements in 38.101-1 clause 6.5F.2.4 for NR SL-U. + +### 6.1.12 Spurious emissions for NR SL-U + +The general spurious emission of NR-U is defined in clause 6.5.3.1 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC general spurious emission requirements in 38.101-1 clause 6.5.3.1 for NR SL-U. + +The additional spurious emission of NR-U is defined in clause 6.5F.3.3 of TS 38.101-1 with different NS values for different bands. + +It has been agreed to reuse the NR-U single CC minimum requirements in TS 38.101-1 clause 6.5F.3.3 for NR SL-U. + +### 6.1.13 Spurious emission band UE co-existence for NR SL-U + +UE coexistence requirements are not defined for NR-U. + +It has been agreed not to define UE coexistence spurious emission requirements for NR SL-U when operating in bands n46, n96 and n102 in case of non-concurrent operation. + +### 6.1.14 Transmit intermodulation for NR SL-U + +The Transmit intermodulation of NR-U is defined in clause 6.5.4 of TS 38.101-1 and the normal NR requirement apply, which is the same for NR V2X. + +It has been agreed to reuse the NR single CC Transmit intermodulation requirements in 38.101-1 clause 6.5.4 for NR SL-U. + +## 6.2 Tx requirements for inter-band con-current operation + +It has been agreed to consider the functionality and requirements of single carrier SL-U operation as a basis of SL-U and the functionality and requirements of single carrier Uu operation as a basis of Uu in con-current operation. + +### 6.2.1 Maximum output power for inter-band con-current operation + +It has been agreed to target the following power classes. + +- Power class 3 Uu@Licensed + Power class 5 SL@Un-licensed +- Power class 3 Uu@Licensed + Power class 3 SL@Un-licensed can be considered as 2nd priority if Power class 3 SL is agreed in a single carrier at unlicensed band + +For Power class 2 for Uu@Licensed for inter-band concurrent operation, it is not considered in Rel-18. + +RAN4 agreed to define maximum output power for each operating band and there is no total power class for SL-U con-current band combination. + +**Table 6.2.1: NR UE Power Class for inter band SL-U con-current combination** + +| NR SL con-current operating band Configuration | NR band | Class 1 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | Class 4 (dBm) | Tolerance (dB) | Class 5 (dBm) | Tolerance (dB) | +|------------------------------------------------|---------|---------------|----------------|---------------|----------------|---------------|----------------|---------------|----------------|---------------|----------------| +| SL_n78-n46 | n78 | | | | | 23 | +2/-3 | | | | | +| | n46 | | | | | | | | | 20 | +2/-3 | + +NOTE 1: For the con-current band combinations, the simultaneous transmission and reception of sidelink and Uu interfaces can be supported while operation is agnostic of the service used on each interface. + +NOTE 2: $P_{\text{PowerClass}}$ is the maximum output power specified without taking into account the tolerance for each operating band. + +NOTE 3: For inter-band con-current operation, the aggregation power apply to the total transmitted power over all component carriers (per UE). + +### 6.2.2 UE maximum output power reduction for inter-band con-current operation + +It has been agreed to refer to the existing requirement for NR Uu and refer to the SL-U requirement if specified. + +For the inter-band con-current operation, the allowed maximum power reduction (MPR) for the maximum output power shall be applied per each component carrier. The MPR requirements in TS 38.101-1 clause 6.2.2 apply for NR Uu operation in licensed band, and the MPR requirements in clause X apply for NR sidelink operation in unlicensed band. + +### 6.2.3 UE additional maximum output power reduction for inter-band con-current operation + +It has been agreed to refer to the existing requirement for NR Uu and refer to the SL-U requirement if specified. + +For the inter-band con-current operation, the allowed additional maximum power reduction (A-MPR) for the maximum output power shall be applied per each component carrier. The A-MPR requirements in clause 6.2.3 apply for NR Uu operation in licensed band, and the A-MPR requirements in clause X apply for NR sidelink operation in unlicensed band. + +### 6.2.4 Configured transmitted power for inter-band con-current operation + +It has been agreed to + +consider the existing requirement for NR V2X con-current operation (6.2E.4.2 in TS38.101-1) as starting point + +reuse the existing delta Tib of CA\_n46-n78 for inter-band concurrent operation in Rel-18 + +When a UE is configured for simultaneous NR sidelink and NR uplink transmissions for inter-band con-current operation, the UE is allowed to set its configured maximum output power $P_{\text{CMAX},c,\text{NR}}$ and $P_{\text{CMAX},c,\text{SL}}$ for the configured NR uplink carrier and the configured NR SL carrier, respectively, and its total configured maximum output power $P_{\text{CMAX},c}$ . + +The configured maximum output power $P_{\text{CMAX},c,\text{NR}}(p)$ in slot $p$ for the configured NR uplink carrier shall be set within the bounds: + +$$P_{\text{CMAX\_L},c,\text{NR}}(p) \leq P_{\text{CMAX},c,\text{NR}}(p) \leq P_{\text{CMAX\_H},c,\text{NR}}(p)$$ + +where $P_{\text{CMAX\_L},c,\text{NR}}$ and $P_{\text{CMAX\_H},c,\text{NR}}$ are the limit as specified in TS 38.101-1 clause 6.2E.4.1. + +The configured maximum output power $P_{\text{CMAX},c,\text{SL}}(q)$ in slot $q$ for the configured NR SL carrier shall be set within the bounds: + +$$P_{\text{CMAX},c,\text{SL}}(q) \leq P_{\text{CMAX\_H},c,\text{SL}}(q)$$ + +where $P_{\text{CMAX\_H},c,\text{SL}}$ is the limit as specified in TS 38.101-1 clause 6.2E.4. + +The total UE configured maximum output power $P_{\text{CMAX}}(p,q)$ in a slot $p$ of NR uplink carrier and a slot $q$ of NR sidelink that overlap in time shall be set within the following bounds for synchronous and asynchronous operation unless stated otherwise: + +$$P_{\text{CMAX\_L}}(p,q) \leq P_{\text{CMAX}}(p,q) \leq P_{\text{CMAX\_H}}(p,q)$$ + +with + +$$P_{\text{CMAX\_L}}(p,q) = P_{\text{CMAX\_L},c,\text{NR}}(p)$$ + +$$P_{\text{CMAX\_H}}(p,q) = 10 \log_{10} [p_{\text{CMAX\_H},c,\text{NR}}(p) + p_{\text{CMAX\_H},c,\text{SL}}(q)]$$ + +where $p_{\text{CMAX\_H},c,\text{SL}}$ and $p_{\text{CMAX\_H},c,\text{NR}}$ are the limits $P_{\text{CMAX\_H},c,\text{SL}}(q)$ and $P_{\text{CMAX\_H},c,\text{NR}}(p)$ expressed in linear scale. + +The measured total maximum output power $P_{\text{UMAX}}$ over both the NR uplink and NR SL carriers is + +$$P_{\text{UMAX}} = 10 \log_{10} [p_{\text{UMAX},c,\text{NR}} + p_{\text{UMAX},c,\text{SL}}],$$ + +where $p_{\text{UMAX},c,\text{NR}}$ denotes the measured output power of serving cell $c$ for the configured NR uplink carrier, and $p_{\text{UMAX},c,\text{SL}}$ denotes the measured output power for the configured NR SL carrier expressed in linear scale. + +When a UE is configured for synchronous NR sidelink and uplink transmissions, + +$$P_{\text{CMAX\_L}}(p,q) - T_{\text{LOW}}(P_{\text{CMAX\_L}}(p,q)) \leq P_{\text{UMAX}} \leq P_{\text{CMAX\_H}}(p,q) + T_{\text{HIGH}}(P_{\text{CMAX\_H}}(p,q))$$ + +where $P_{\text{CMAX\_L}}(p,q)$ and $P_{\text{CMAX\_H}}(p,q)$ are the limits for the pair $(p,q)$ and with the tolerances $T_{\text{LOW}}(P_{\text{CMAX}})$ and $T_{\text{HIGH}}(P_{\text{CMAX}})$ for applicable values of $P_{\text{CMAX}}$ specified in Table 6.2E.4.1-1.. $P_{\text{CMAX\_L}}$ may be modified for any overlapping portion of slots $(p,q)$ and $(p+1,q+1)$ . + +### 6.2.5 Minimum output power for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +For the inter-band con-current operation, the requirements specified in TS 38.101-1 clause 6.3.1 shall apply for NR Uu operation in licensed band and the requirements specified in clause X shall apply for NR sidelink operation in unlicensed band. + +### 6.2.6 Transmit OFF power for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +For the inter-band con-current operation, the requirements specified in TS 38.101-1 clause 6.3.2 shall apply for NR Uu operation in licensed band and the requirements specified in clause X shall apply for NR sidelink operation in unlicensed band + +### 6.2.7 ON/OFF time mask for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +### 6.2.8 Power control for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +For the inter-band con-current operation, the requirements specified in TS 38.101-1 clause 6.3.4 shall apply for NR Uu operation in licensed band and the requirements specified in clause X shall apply for NR sidelink operation in unlicensed band + +### 6.2.9 Transmit signal quality for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +### 6.2.10 Spectrum emission mask for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +For the inter-band con-current operation, the general/additional SEM requirements specified in TS 38.101-1 clause 6.5.2 shall apply for NR Uu operation in licensed band and the general/additional SEM requirements specified in clause X shall apply for NR sidelink operation in unlicensed band. + +### 6.2.11 ACLR requirements for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +For the inter-band con-current operation, the ACLR requirement specified in clause TS 38.101-1 6.5.2.4 shall apply for NR Uu operation in licensed band and the ACLR requirement specified in clause X shall apply for NR sidelink operation in unlicensed band. + +### 6.2.12 Spurious emissions for inter-band con-current operation + +The general spurious emission is not needed for inter-band con-current operation as the NR SL only defines spurious emission for non-current case. + +### 6.2.13 Spurious emission band UE co-existence for inter-band con-current operation + +It has been agreed to reuse the inter band CA\_n46-n78 co-existence requirement for con-current operation with Uu@78 + SL@n46. + +### 6.2.14 Transmit intermodulation for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +For the inter-band con-current operation, the requirements specified in TS 38.101-1 clause 6.5.4 shall apply for NR Uu operation in licensed band and the requirements specified in clause X shall apply for NR sidelink operation in unlicensed band. + +## 6.3 Tx requirements for NR SL CA operation + +### 6.3.1 Maximum output power for NR SL CA operation + +For the intra-band SL CA operation, the following NR SL CA UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth. The period of measurement shall be at least one sub frame (1ms). + +**Table 6.3.1-1: NR SL CA UE Power Class** + +| NR SL CA band Configuration | Class 1 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | Class 4 (dBm) | Tolerance (dB) | +|-----------------------------|---------------|----------------|---------------|----------------|---------------|--------------------|---------------|----------------| +| SL_n47B | | | | | 23 | +2/-3 3 | | | + +NOTE 1: $P_{\text{PowerClass}}$ is the maximum UE power specified without taking into account the tolerance + +NOTE 2: For intra-band SL CA UE, the maximum power requirement apply to the total transmitted power over all component carriers (per UE). + +NOTE 3: 3 refers to the transmission bandwidths (Figure 5.6-1 in TS38.101-1) confined within $F_{\text{UL\_low}}$ and $F_{\text{UL\_low}} + 4$ MHz or $F_{\text{UL\_high}} - 4$ MHz and $F_{\text{UL\_high}}$ , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB + +### 6.3.2 UE maximum output power reduction for NR SL CA operation + +For basic parameters, reuse the simulation assumptions in TR38.785 (Rel-17 enhanced NR sidelink). Other constraints for PSCCH/PSSCH/PSFCH/S-SSB can be assumed based on current RAN1's agreement. + +**Table 6.3.2 Simulation assumption for NR SL CA operation** + +| | | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Center frequency | 5.9GHz | +| Bandwidth | per CC: 10/20/30/40MHz
Aggregated CBW: Table 5.2.3-1 (up to 70MHz CBW) | +| Maximum output power for aggregated CBW | 23dBm | +| Numerology | 15 kHz/30kHz/60kHz | +| Modulation per CC | QPSK/16QAM/64QAM/256QAM | +| Waveform | CP-OFDM | +| Carrier leakage | 34dBc | +| IQ image | 25dBc | +| CIM3 | 60dBc | +| PA calibration | PA calibrated to deliver 30dBc ACLR for a fully allocated RBs in 20MHz QPSK DFT- S-OFDM waveform at 1 dB MPR.
This is based to share PA between LTE V2X and NR V2X at 5.9GHz as worst case. | + +#### 6.3.2.1 MPR for NR SL CA operation + +##### 6.3.2.1.1 MPR for simultaneous PSSCH/PSCCH transmission + +For SL intra-band contiguous CA of PSCCH and PSSCH simultaneous transmission with contiguous RB allocation, specify MPR in Table 6.3.2.1.1-1. + +**Table 6.3.2.1.1-1: MPR for power class 3 SL CA [with contiguous RB allocation]** + +| Modulation | | MPR for bandwidth class B(dB) | | +|------------|--------|-------------------------------|-------| +| | | inner | outer | +| CP-OFDM | QPSK | ≤ 3.0 | ≤ 5.0 | +| | 16QAM | ≤ 3.0 | ≤ 5.0 | +| | 64QAM | ≤ 4.5 | ≤ 5.0 | +| | 256QAM | ≤ 6.5 | 7.0 | + +The contiguous allocation rule for SL intra-band contiguous CA refers to that for NR intra-band contiguous CA in 6.2A.2.1 in TS38.101-1. + +[For SL intra-band contiguous CA of PSCCH and PSSCH simultaneous transmission with non-contiguous RB allocation, specify MPR in Table 6.3.2.1.1-2. + +**Table 6.3.2.1.1-2: MPR for power class 3 SL CA with non-contiguous RB allocation** + +[TBA] + +The non-contiguous allocation rule for SL intra-band contiguous CA refers to that for NR intra-band contiguous CA in 6.2A.2.1 in TS38.101-1.] + +###### 6.3.2.1.1.1 Huawei's simulation results (R4-2315227) + +Referring to the updated MPR simulation assumption, we use the following simulation scenarios in Table . + +**Table 6.3.2.1.1.1-1 SLCA PSSCH/PSCCH MPR simulation scenarios** + +| Scenario | Aggregated CBW | Subcarrier spacing | Waveform | Modulation | +|----------|----------------|--------------------|----------|-------------------------| +| 1 | 10MHz + 10MHz | 15kHz+15kHz | CP-OFDM | QPSK/16QAM/64QAM/256QAM | +| 2 | 10MHz + 10MHz | 30kHz+30kHz | CP-OFDM | QPSK/16QAM/64QAM/256QAM | +| 3 | 30MHz + 40MHz | 30kHz+30kHz | CP-OFDM | QPSK/16QAM/64QAM/256QAM | +| 4 | 20MHz + 20MHz | 30kHz+30kHz | CP-OFDM | QPSK/16QAM/64QAM/256QAM | + +The simulation results for the scenarios listed in are illustrated below, and the evaluation figures are shown in the Annex with Figure 1 – Figure 4. + +**Table 6.3.2.1.1.1-2 SLCA PSSCH/PSCCH MPR simulation scenarios** + +| Modulation | 10MHz + 10MHz / 30kHz+30kHz | | 10MHz + 10MHz / 15kHz+15kHz | | 30MHz + 40MHz / 30kHz+30kHz | | 20MHz + 20MHz / 30kHz+30kHz | | +|------------|-----------------------------|-------|-----------------------------|-------|-----------------------------|-------|-----------------------------|-------| +| | inner | outer | inner | outer | inner | outer | inner | outer | +| QPSK | 1.8 | 2.9 | 1.9 | 3.1 | 1.7 | 3.0 | 1.8 | 3.2 | +| 16QAM | 2.3 | 2.9 | 2.2 | 3.0 | 2.5 | 3.2 | 2.3 | 3.2 | +| 64QAM | 3.3 | 3.9 | 3.3 | 4.0 | 3.4 | 4.0 | 3.4 | 4.0 | +| 256QAM | 5.2 | 6.3 | 5.3 | 6.4 | 5.4 | 6.4 | 5.5 | 5.4 | + +###### 6.3.2.1.1.2 LGE's simulation results (R4-2315532) + +For Contiguous RB allocation of SL contiguous CA + +The following simulation scenarios are considered as Table 6.3.2.1.1.2-1 for Contiguous RB allocations. + +**Table 6.3.2.1.1.2-1: SLCA PSSCH/PSCCH MPR simulation scenarios (Contiguous RB allocation)** + +| Aggregate d CBW | Scenario | CC1 | CC2 | Inner/Outer RB allocation | SCS | +|-----------------|----------|--------|--------|---------------------------|-----| +| 10MHz + 10MHz | 1 | 10RB42 | 10RB0 | Inner | 15 | +| | 2 | 10RB42 | 12RB0 | Inner | 15 | +| | 3 | 10RB42 | 15RB0 | Inner | 15 | +| | 4 | 10RB42 | 25RB0 | Inner | 15 | +| | 5 | 10RB42 | 30RB0 | Inner | 15 | +| | 6 | 10RB42 | 36RB0 | Outer | 15 | +| | 7 | 10RB42 | 50RB0 | Outer | 15 | +| | 8 | 12RB40 | 36RB0 | Outer | 15 | +| | 9 | 25RB27 | 36RB0 | Outer | 15 | +| | 10 | 40RB12 | 40RB0 | Outer | 15 | +| | 11 | 50RB2 | 50RB0 | Outer | 15 | +| 20MHz + 30MHz | 12 | 10RB41 | 10RB0 | Inner | 30 | +| | 13 | 10RB41 | 12RB0 | Inner | 30 | +| | 14 | 10RB41 | 25RB0 | Inner | 30 | +| | 15 | 10RB41 | 30RB0 | Inner | 30 | +| | 16 | 10RB41 | 48RB0 | Inner | 30 | +| | 17 | 10RB41 | 50RB0 | Outer | 30 | +| | 18 | 25RB26 | 36RB0 | Outer | 30 | +| | 19 | 36RB15 | 36RB0 | Outer | 30 | +| | 20 | 40RB11 | 40RB0 | Outer | 30 | +| | 21 | 50RB1 | 75RB0 | Outer | 30 | +| 20MHz + 40MHz | 22 | 10RB41 | 10RB0 | Inner | 30 | +| | 23 | 10RB41 | 25RB0 | Inner | 30 | +| | 24 | 10RB41 | 36RB0 | Inner | 30 | +| | 25 | 10RB41 | 48RB0 | Inner | 30 | +| | 26 | 10RB41 | 60RB0 | Inner | 30 | +| | 27 | 10RB41 | 70RB0 | Outer | 30 | +| | 28 | 25RB26 | 36RB0 | Outer | 30 | +| | 29 | 36RB15 | 70RB0 | Outer | 30 | +| | 30 | 40RB11 | 90RB0 | Outer | 30 | +| | 31 | 50RB1 | 105RB0 | Outer | 30 | +| 30MHz + 40MHz | 32 | 10RB68 | 10RB0 | Inner | 30 | +| | 33 | 10RB68 | 25RB0 | Inner | 30 | +| | 34 | 10RB68 | 36RB0 | Inner | 30 | +| | 35 | 10RB68 | 48RB0 | Inner | 30 | +| | 36 | 10RB68 | 60RB0 | Inner | 30 | +| | 37 | 10RB68 | 70RB0 | Outer | 30 | +| | 38 | 10RB68 | 105RB0 | Outer | 30 | +| | 39 | 25RB53 | 70RB0 | Outer | 30 | +| | 40 | 36RB42 | 90RB0 | Outer | 30 | +| | 41 | 40RB38 | 90RB0 | Outer | 30 | +| | 42 | 75RB3 | 105RB0 | Outer | 30 | +| 20MHz + 20MHz | 43 | 10RB41 | 10RB0 | Inner | 30 | +| | 44 | 10RB41 | 12RB0 | Inner | 30 | +| | 45 | 10RB41 | 15RB0 | Inner | 30 | +| | 45 | 10RB41 | 25RB0 | Inner | 30 | +| | 46 | 10RB41 | 30RB0 | Inner | 30 | +| | 47 | 10RB41 | 36RB0 | Outer | 30 | +| | 48 | 10RB41 | 50RB0 | Outer | 30 | +| | 49 | 12RB39 | 36RB0 | Outer | 30 | +| | 50 | 25RB26 | 36RB0 | Outer | 30 | +| | 51 | 40RB11 | 40RB0 | Outer | 30 | +| | 52 | 50RB1 | 50RB0 | Outer | 30 | +| 10MHz + 30MHz | 53 | 10RB41 | 10RB0 | Inner | 30 | +| | 54 | 10RB41 | 12RB0 | Inner | 30 | + +| | | | | | | +|--|----|--------|-------|-------|----| +| | 55 | 10RB41 | 15RB0 | Inner | 30 | +| | 56 | 10RB41 | 20RB0 | Inner | 30 | +| | 57 | 10RB41 | 25RB0 | Outer | 30 | +| | 58 | 10RB41 | 50RB0 | Outer | 30 | +| | 59 | 10RB41 | 75RB0 | Outer | 30 | +| | 60 | 12RB12 | 36RB0 | Outer | 30 | +| | 61 | 15RB9 | 60RB0 | Outer | 30 | +| | 62 | 20RB4 | 75RB0 | Outer | | +| | 63 | 24RB0 | 75RB0 | Outer | 30 | + +Table 6.3.2.1.1.2-1-2 and Figure 6.3.2.1.1.2-1 show PSSCH/PSCCH MPR simulation results. + +Table 6.3.2.1.1.2-2: PSSCH/PSCCH MPR simulation results for SL Contiguous CA with Contiguous RB allocations + +| | | | | | | | | | | | | | +|---------------|------------|------|------|------|------|------|------|------|------|------|------|------| +| '10MHz+10MHz' | Scenario # | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9 | #10 | #11 | +| | 'QPSK' | 0.13 | 0.13 | 0.14 | 0.13 | 0.13 | 0.95 | 2.70 | 1.27 | 1.60 | 2.32 | 3.09 | +| | '16QAM' | 1.27 | 0.96 | 1.27 | 0.95 | 0.95 | 0.96 | 2.69 | 1.27 | 1.60 | 2.32 | 3.09 | +| | '64QAM' | 2.31 | 2.31 | 2.31 | 2.31 | 2.30 | 2.31 | 2.69 | 2.31 | 2.31 | 2.32 | 3.09 | +| | '256QAM' | 4.36 | 3.92 | 3.93 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | +| '20MHz+30MHz' | Scenario # | #12 | #13 | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | | +| | 'QPSK' | 0.37 | 0.65 | 1.26 | 0.96 | 0.67 | 0.95 | 0.96 | 1.95 | 2.31 | 3.09 | | +| | '16QAM' | 0.66 | 0.94 | 0.95 | 0.95 | 1.27 | 1.27 | 1.27 | 1.95 | 2.31 | 3.09 | | +| | '64QAM' | 1.93 | 1.93 | 2.31 | 2.31 | 2.31 | 2.31 | 2.31 | 2.31 | 2.31 | 3.09 | | +| | '256QAM' | 3.91 | 3.91 | 3.92 | 3.92 | 3.92 | 3.92 | 3.91 | 3.92 | 3.92 | 3.92 | | +| '20MHz+40MHz' | Scenario # | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | | +| | 'QPSK' | 0.00 | 0.00 | 0.00 | 0.13 | 0.13 | 0.39 | 0.66 | 1.95 | 2.31 | 3.09 | | +| | '16QAM' | 0.65 | 0.95 | 0.96 | 0.95 | 0.96 | 0.96 | 0.95 | 1.94 | 2.31 | 3.09 | | +| | '64QAM' | 1.93 | 1.94 | 2.30 | 2.31 | 2.31 | 2.31 | 2.30 | 2.31 | 2.31 | 3.09 | | +| | '256QAM' | 3.49 | 3.91 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | | +| '30MHz+40MHz' | Scenario # | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | #40 | #41 | #43 | +| | 'QPSK' | 0.00 | 0.00 | 0.00 | 0.12 | 0.13 | 0.66 | 3.09 | 1.27 | 2.69 | 2.69 | 3.09 | +| | '16QAM' | 0.64 | 0.95 | 0.95 | 0.95 | 1.27 | 1.27 | 3.09 | 1.27 | 2.69 | 2.69 | 3.09 | +| | '64QAM' | 1.93 | 2.30 | 2.30 | 2.30 | 2.30 | 2.30 | 3.09 | 2.31 | 2.69 | 2.69 | 3.09 | +| | '256QAM' | 3.49 | 3.91 | 3.91 | 3.91 | 4.35 | 3.92 | 4.36 | 3.92 | 4.36 | 3.92 | 4.35 | +| '20MHz+20MHz' | Scenario # | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | #52 | #53 | #54 | +| | 'QPSK' | 0.00 | 0.00 | 0.00 | 0.00 | 0.13 | 1.26 | 3.09 | 1.59 | 1.94 | 2.31 | 3.09 | +| | '16QAM' | 0.65 | 0.95 | 0.95 | 0.95 | 0.95 | 1.27 | 3.09 | 1.59 | 1.95 | 2.32 | 3.09 | +| | '64QAM' | 1.93 | 1.93 | 1.94 | 2.30 | 2.31 | 2.31 | 3.08 | 2.31 | 2.31 | 2.31 | 3.09 | +| | '256QAM' | 3.91 | 3.91 | 3.92 | 3.91 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | +| '10MHz+' | Scenario # | #55 | #56 | #57 | #58 | #59 | #60 | #61 | #62 | #63 | #64 | #65 | + +| | | | | | | | | | | | | | +|----------------|-----------------|------|------|------|------|------|------|------|------|------|------|------| +| '30MHz' | 'QPSK' | 0.00 | 0.00 | 0.00 | 0.38 | 0.66 | 1.60 | 2.69 | 1.60 | 2.31 | 2.70 | 3.09 | +| | '16QAM' | 0.65 | 0.94 | 0.65 | 0.94 | 0.95 | 1.60 | 2.69 | 1.60 | 2.31 | 2.70 | 3.09 | +| | '64QAM' | 1.93 | 1.94 | 1.95 | 1.94 | 2.31 | 2.30 | 2.69 | 2.31 | 2.31 | 2.70 | 3.09 | +| | '256QAM' | 3.92 | 3.91 | 3.91 | 3.92 | 3.92 | 3.92 | 4.36 | 3.92 | 3.92 | 3.92 | 3.92 | + +Table 6.3.2.1.1.2-3 shows the maximum value of simulation results for SL Contiguous CA with Contiguous RB allocations considering Inner RB allocation and Outer RB allocation as NR uplink Contiguous CA. + +**Table 6.3.2.1.1.2-3: PSSCH/PSCCH MPR simulation results for SL Contiguous CA with Contiguous RB allocations** + +| Modulation | | MPR for bandwidth class B(dB) | | +|------------|--------|-------------------------------|-------| +| | | inner | outer | +| CP-OFDM | QPSK | 0.38 | 3.09 | +| | 16QAM | 1.27 | 3.09 | +| | 64QAM | 2.31 | 3.09 | +| | 256QAM | 4.36 | 4.36 | + +The MPR can be proposed as Table 6.3.2.1.1.2-4 based on the simulation results when considering implementation margin. + +**Table 6.3.2.1.1.2-4: PSSCH/PSCCH MPR simulation results for SL Contiguous CA with Contiguous RB allocations** + +| Modulation | | MPR for bandwidth class B(dB) | | +|------------|--------|-------------------------------|------------| +| | | inner | outer | +| CP-OFDM | QPSK | $\leq 3.0$ | $\leq 5.0$ | +| | 16QAM | $\leq 3.0$ | $\leq 5.0$ | +| | 64QAM | $\leq 4.5$ | $\leq 5.0$ | +| | 256QAM | $\leq 7.0$ | $\leq 7.0$ | + +For Non-contiguous RB allocation of SL contiguous CA + +The following test scenarios are considered as Table 6.3.2.1.1.2-5 for Non-contiguous RB allocations. + +Table 6.3.2.1.1.2-5: SL contiguous CA MPR test scenarios (Non-contiguous RB allocation) + +| Aggregated CBW | Scenario | CC1 | CC2 | Inner/Outer1/
Outer2 RB
allocation | SCS | +|------------------|----------|--------|--------|------------------------------------------|-----| +| 10MHz +
10MHz | 1 | 10RB0 | 10RB42 | Outer2 | 15 | +| | 2 | 10RB18 | 10RB22 | Outer2 | 15 | +| | 3 | 10RB19 | 10RB22 | Outer2 | 15 | +| | 4 | 10RB27 | 10RB14 | Outer2 | 15 | +| | 5 | 10RB33 | 10RB7 | Outer1 | 15 | +| | 6 | 10RB34 | 10RB7 | Outer1 | 15 | +| | 7 | 10RB42 | 10RB1 | Inner | 15 | +| | 8 | 25RB0 | 25RB27 | Outer2 | 15 | +| | 9 | 25RB19 | 25RB8 | Outer2 | 15 | +| | 10 | 25RB20 | 25RB8 | Outer2 | 15 | +| | 11 | 25RB27 | 25RB1 | Outer1 | 15 | +| | 12 | 30RB0 | 30RB22 | Outer2 | 15 | +| | 13 | 30RB19 | 30RB3 | Outer2 | 15 | +| | 14 | 30RB19 | 30RB2 | Outer2 | 15 | +| | 15 | 30RB22 | 30RB1 | Outer1 | 15 | +| | 16 | 50RB1 | 50RB0 | Outer2 | 15 | +| 20MHz +
30MHz | 17 | 10RB0 | 10RB68 | Outer2 | 30 | +| | 18 | 10RB15 | 10RB32 | Outer2 | 30 | +| | 19 | 10RB15 | 10RB31 | Outer2 | 30 | +| | 20 | 10RB32 | 10RB10 | Outer1 | 30 | +| | 21 | 10RB34 | 10RB9 | Outer1 | 30 | +| | 22 | 10RB34 | 10RB8 | Outer1 | 30 | +| | 23 | 10RB41 | 10RB1 | Inner | 30 | +| | 24 | 25RB0 | 25RB53 | Outer2 | 30 | +| | 25 | 25RB20 | 25RB25 | Outer2 | 30 | +| | 26 | 25RB21 | 25RB25 | Outer2 | 30 | +| | 27 | 25RB26 | 25RB1 | Outer1 | 30 | +| | 28 | 30RB0 | 30RB48 | Outer2 | 30 | +| | 29 | 30RB15 | 30RB12 | Outer2 | 30 | +| | 30 | 30RB15 | 30RB11 | Outer2 | 30 | +| | 31 | 30RB21 | 30RB1 | Outer1 | 30 | +| | 32 | 50RB0 | 50RB28 | Outer2 | 30 | +| | 33 | 50RB0 | 50RB0 | Outer2 | 30 | +| | 34 | 50RB0 | 78RB0 | Outer2 | 30 | +| 20MHz +
40MHz | 35 | 10RB0 | 10RB96 | Outer2 | 30 | +| | 36 | 10RB4 | 10RB30 | Outer2 | 30 | +| | 37 | 10RB5 | 10RB30 | Outer2 | 30 | +| | 38 | 10RB37 | 10RB15 | Outer1 | 30 | +| | 39 | 10RB38 | 10RB15 | Inner | 30 | +| | 40 | 10RB41 | 10RB1 | Inner | 30 | +| | 41 | 25RB0 | 25RB81 | Outer2 | 30 | +| | 42 | 25RB20 | 25RB38 | Outer2 | 30 | +| | 43 | 25RB20 | 25RB37 | Outer2 | 30 | +| | 44 | 25RB26 | 25RB1 | Outer1 | 30 | +| | 45 | 30RB0 | 30RB76 | Outer2 | 30 | +| | 46 | 30RB15 | 30RB26 | Outer2 | 30 | +| | 47 | 30RB15 | 30RB25 | Outer2 | 30 | +| | 48 | 30RB21 | 30RB1 | Outer1 | 30 | +| | 49 | 50RB0 | 50RB56 | Outer2 | 30 | +| | 50 | 50RB0 | 50RB0 | Outer2 | 30 | +| | 51 | 50RB0 | 105RB0 | Outer2 | 30 | +| 30MHz + | 52 | 10RB0 | 10RB96 | Outer2 | 30 | + +| | | | | | | +|---------------|-----|--------|--------|--------|----| +| 40MHz | 53 | 10RB13 | 10RB30 | Outer2 | 30 | +| | 54 | 10RB14 | 10RB30 | Outer1 | 30 | +| | 55 | 10RB50 | 10RB15 | Outer1 | 30 | +| | 56 | 10RB51 | 10RB15 | Inner | 30 | +| | 57 | 10RB68 | 10RB1 | Inner | 30 | +| | 58 | 25RB0 | 25RB81 | Outer2 | 30 | +| | 59 | 25RB28 | 25RB37 | Outer2 | 30 | +| | 60 | 25RB28 | 25RB36 | Outer1 | 30 | +| | 61 | 25RB51 | 25RB1 | Outer1 | 30 | +| | 62 | 25RB52 | 25RB1 | Inner | 30 | +| | 63 | 30RB0 | 30RB76 | Outer2 | 30 | +| | 64 | 30RB24 | 30RB26 | Outer2 | 30 | +| | 65 | 30RB24 | 30RB25 | Outer1 | 30 | +| | 66 | 30RB48 | 30RB1 | Outer1 | 30 | +| | 67 | 75RB0 | 50RB56 | Outer2 | 30 | +| | 68 | 75RB0 | 50RB0 | Outer2 | 30 | +| | 69 | 75RB0 | 105RB0 | Outer2 | 30 | +| 20MHz + 20MHz | 70 | 10RB0 | 10RB41 | Outer2 | 30 | +| | 71 | 10RB17 | 10RB22 | Outer2 | 30 | +| | 72 | 10RB18 | 10RB22 | Outer1 | 30 | +| | 73 | 10RB27 | 10RB14 | Outer1 | 30 | +| | 74 | 10RB33 | 10RB7 | Outer1 | 30 | +| | 75 | 10RB34 | 10RB7 | Inner | 30 | +| | 76 | 10RB41 | 10RB1 | Inner | 30 | +| | 77 | 25RB0 | 25RB26 | Outer2 | 30 | +| | 78 | 25RB18 | 25RB8 | Outer2 | 30 | +| | 79 | 25RB19 | 25RB8 | Outer1 | 30 | +| | 80 | 25RB26 | 25RB1 | Outer1 | 30 | +| | 81 | 30RB0 | 30RB21 | Outer2 | 30 | +| | 82 | 30RB18 | 30RB3 | Outer1 | 30 | +| | 83 | 30RB18 | 30RB2 | Outer1 | 30 | +| | 84 | 30RB21 | 30RB1 | Outer2 | 30 | +| | 85 | 50RB0 | 50RB0 | Outer2 | 30 | +| 10MHz + 30MHz | 86 | 10RB0 | 10RB68 | Outer2 | 30 | +| | 87 | 10RB6 | 10RB32 | Outer2 | 30 | +| | 88 | 10RB6 | 10RB31 | Outer1 | 30 | +| | 89 | 10RB14 | 10RB10 | Outer1 | 30 | +| | 90 | 10RB14 | 10RB1 | Outer1 | 30 | +| | 91 | 10RB0 | 12RB53 | Outer2 | 30 | +| | 92 | 10RB3 | 12RB25 | Outer2 | 30 | +| | 93 | 25RB4 | 12RB25 | Outer1 | 30 | +| | 94 | 25RB12 | 12RB1 | Outer1 | 30 | +| | 95 | 25RB0 | 30RB48 | Outer2 | 30 | +| | 96 | 25RB3 | 30RB7 | Outer2 | 30 | +| | 97 | 30RB3 | 30RB6 | Outer1 | 30 | +| | 98 | 30RB12 | 30RB1 | Outer1 | 30 | +| | 99 | 30RB0 | 50RB28 | Outer2 | 30 | +| | 100 | 30RB0 | 50RB1 | Outer2 | 30 | +| | 101 | 50RB0 | 75RB1 | Outer2 | 30 | + +Table 6.3.2.1.1.2-6 and Figure 6.3.2.1.1.2-2 show PSSCH/PSCCH MPR simulation results. + +Table 6.3.2.1.1.2-6: PSSCH/PSCCH MPR simulation results for SL Contiguous CA with Non-contiguous RB allocations + +| | | | | | | | | | | | | | | | | | | | | +|---------------|------------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| '10MHz+10MHz' | Scenario # | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9 | #10 | #11 | #12 | #13 | #14 | #15 | #16 | | | +| | 'QPSK' | 6.67 | 3.09 | 2.69 | 2.33 | 0.00 | 0.00 | 0.14 | 4.81 | 2.32 | 2.32 | 0.14 | 4.81 | 1.95 | 1.95 | 1.28 | 3.09 | | | +| | '16QAM' | 6.67 | 2.70 | 3.10 | 2.70 | 0.95 | 0.97 | 0.96 | 5.26 | 2.32 | 2.32 | 0.96 | 4.81 | 1.95 | 1.95 | 1.28 | 3.09 | | | +| | '64QAM' | 6.67 | 2.69 | 3.09 | 2.32 | 1.94 | 2.31 | 2.31 | 5.26 | 2.31 | 2.32 | 2.31 | 4.81 | 1.95 | 1.95 | 2.32 | 3.09 | | | +| | '256QAM' | 7.15 | 3.92 | 3.93 | 3.93 | 3.92 | 3.92 | 3.93 | 4.81 | 3.92 | 3.92 | 3.92 | 4.81 | 3.92 | 3.92 | 3.92 | 3.92 | | | +| '20MHz+30MHz' | Scenario # | #17 | #18 | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | #30 | #31 | #32 | #33 | #34 | +| | 'QPSK' | 5.27 | 2.69 | 2.69 | 0.00 | 0.00 | 0.00 | 0.00 | 3.50 | 2.69 | 2.69 | 0.38 | 3.10 | 2.69 | 2.69 | 1.27 | 3.10 | 3.09 | 3.09 | +| | '16QAM' | 5.27 | 2.70 | 2.69 | 0.66 | 0.66 | 0.65 | 0.66 | 3.50 | 2.70 | 2.69 | 0.96 | 3.09 | 2.69 | 2.69 | 1.27 | 3.09 | 3.09 | 3.09 | +| | '64QAM' | 5.27 | 2.69 | 2.70 | 1.93 | 1.94 | 1.93 | 1.93 | 3.51 | 2.69 | 2.69 | 2.31 | 3.09 | 2.69 | 2.69 | 2.31 | 3.09 | 3.09 | 3.09 | +| | '256QAM' | 5.26 | 3.50 | 3.49 | 3.48 | 3.91 | 3.49 | 3.49 | 3.50 | 3.50 | 3.49 | 3.91 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | +| '20MHz+40MHz' | Scenario # | #35 | #36 | #37 | #38 | #39 | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | #49 | #50 | #51 | | +| | 'QPSK' | 5.28 | 3.09 | 3.08 | 0.00 | 0.00 | 0.00 | 3.09 | 2.69 | 2.69 | 0.66 | 3.09 | 2.69 | 2.69 | 1.60 | 3.10 | 3.09 | 3.09 | | +| | '16QAM' | 5.26 | 3.08 | 3.08 | 0.65 | 0.65 | 0.65 | 3.09 | 2.69 | 2.69 | 0.95 | 3.10 | 2.69 | 2.69 | 1.60 | 3.09 | 3.09 | 3.09 | | +| | '64QAM' | 5.27 | 3.09 | 3.09 | 1.94 | 1.94 | 1.94 | 3.09 | 2.69 | 2.69 | 1.94 | 3.09 | 2.69 | 2.69 | 2.31 | 3.10 | 3.09 | 3.09 | | +| | '256QAM' | 5.27 | 3.49 | 3.49 | 3.49 | 3.48 | 3.49 | 3.50 | 3.49 | 3.49 | 3.91 | 3.92 | 3.50 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | | +| '30MHz+40MHz' | Scenario # | #52 | #53 | #54 | #55 | #56 | #57 | #58 | #59 | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | +| | 'QPSK' | 5.27 | 2.69 | 2.69 | 0.00 | 0.00 | 0.00 | 3.09 | 2.69 | 2.69 | 0.00 | 0.00 | 3.09 | 2.69 | 2.69 | 0.00 | 3.09 | 3.09 | 3.09 | +| | '16QAM' | 5.26 | 2.69 | 2.69 | 0.65 | 0.65 | 0.65 | 3.10 | 2.69 | 2.69 | 0.95 | 0.94 | 3.09 | 2.69 | 2.69 | 0.95 | 3.09 | 3.09 | 3.09 | +| | '64QAM' | 5.26 | 2.69 | 2.68 | 1.93 | 1.93 | 1.93 | 3.09 | 2.69 | 2.69 | 1.94 | 1.94 | 3.09 | 2.69 | 2.69 | 2.30 | 3.09 | 3.09 | 3.09 | +| | '256QAM' | 5.27 | 3.48 | 3.49 | 3.48 | 3.49 | 3.49 | 3.50 | 3.49 | 3.49 | 3.91 | 3.91 | 3.92 | 3.92 | 3.92 | 3.91 | 3.92 | 3.92 | 4.36 | +| '20MHz+20MHz' | Scenario # | #70 | #71 | #72 | #73 | #74 | #75 | #76 | #77 | #78 | #79 | #80 | #81 | #82 | #84 | #84 | #85 | | | +| | 'QPSK' | 5.27 | 2.69 | 2.69 | 2.68 | 0.00 | 0.00 | 0.00 | 3.50 | 2.31 | 2.31 | 0.39 | 3.09 | 1.95 | 1.95 | 1.60 | 3.09 | | | +| | '16QAM' | 5.27 | 2.69 | 2.69 | 2.69 | 0.65 | 0.65 | 0.65 | 3.50 | 2.31 | 2.31 | 0.95 | 3.09 | 1.95 | 1.95 | 1.60 | 3.10 | | | +| | '64QAM' | 5.26 | 2.69 | 2.69 | 2.68 | 1.93 | 1.94 | 1.93 | 3.50 | 2.31 | 2.31 | 1.94 | 3.09 | 1.95 | 1.95 | 2.31 | 3.09 | | | +| | '256QAM' | 5.27 | 3.49 | 3.49 | 3.49 | 3.49 | 3.49 | 3.49 | 3.50 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | 3.92 | | | +| '10MHz+' | Scenario # | #86 | #87 | #88 | #89 | #90 | #91 | #92 | #93 | #94 | #95 | #96 | #97 | #98 | #99 | #100 | #101 | | | + +| | | | | | | | | | | | | | | | | | | +|---------|----------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| '30MHz' | 'QPSK' | 5.27 | 2.69 | 2.69 | 1.94 | 0.00 | 4.81 | 3.08 | 3.09 | 0.66 | 3.50 | 2.69 | 2.69 | 1.59 | 3.09 | 3.09 | 3.09 | +| | '16QAM' | 5.26 | 2.69 | 2.69 | 1.93 | 0.66 | 4.81 | 3.09 | 3.09 | 0.66 | 3.51 | 2.69 | 2.69 | 1.59 | 3.09 | 3.09 | 3.09 | +| | '64QAM' | 5.27 | 3.09 | 2.68 | 1.94 | 1.93 | 4.81 | 3.08 | 3.08 | 1.94 | 3.51 | 2.69 | 2.69 | 2.30 | 3.09 | 3.09 | 3.09 | +| | '256QAM' | 5.27 | 3.49 | 3.49 | 3.49 | 3.49 | 4.81 | 3.49 | 3.92 | 3.92 | 3.50 | 3.50 | 3.92 | 3.92 | 3.93 | 3.93 | 3.92 | + +Table 6.3.2.1.1.2-7 shows the maximum value of simulation results for SL Contiguous CA with Non-contiguous RB allocations considering Inner RB allocation and Outer RB allocation as NR uplink Contiguous CA. + +**Table 6.3.2.1.1.2-7 : PSSCH/PSCCH MPR simulation results for SL Contiguous CA with Non-contiguous RB allocations** + +| Modulation | | MPR for bandwidth class B(dB) | | | +|------------|--------|-------------------------------|--------|--------| +| | | Inner | Outer1 | Outer2 | +| CP-OFDM | QPSK | 0.13 | 3.09 | 6.68 | +| | 16QAM | 0.96 | 3.09 | 6.67 | +| | 64QAM | 2.31 | 3.10 | 6.67 | +| | 256QAM | 4.35 | 3.93 | 6.67 | + +The MPR can be proposed as Table 6.3.2.1.1.2-8 based on the simulation results when considering implementation margin. + +**Table 6.3.2.1.1.2-8 PSSCH/PSCCH MPR simulation results for SL Contiguous CA with Non-contiguous RB allocations** + +| Modulation | | MPR for bandwidth class B(dB) | | | +|------------|--------|-------------------------------|------------|------------| +| | | Inner | Outer1 | Outer2 | +| CP-OFDM | QPSK | $\leq 3.0$ | $\leq 5.0$ | $\leq 9.5$ | +| | 16QAM | $\leq 3.0$ | $\leq 5.0$ | $\leq 9.5$ | +| | 64QAM | $\leq 4.5$ | $\leq 5.0$ | $\leq 9.5$ | +| | 256QAM | $\leq 7.0$ | $\leq 7.0$ | $\leq 9.5$ | + +##### 6.3.2.1.2 MPR for PSFCH transmission + +For SL intra-band CA of PSFCH with single RB transmission on each carrier, the required MPR are specified as follow. + +$$\begin{aligned} \text{MPR\_PSFCH\_SLCA} &= 2.5; & 0 < R \leq 0.3 \\ &= 7.5; & 0.3 < R \leq 0.5 \\ &= 12; & 0.5 < R \leq 1 \end{aligned}$$ + +Where, + +R is the ratio of the gap bandwidth between the two PSFCH transmitted on the two intra-band carrier by the total bandwidth of the two carrier. + +###### 6.3.2.1.2.1 Huawei's simulation results (R4-2319504) + +The evaluation scenarios and MPR results for SL CA PSFCH are illustrated in the following table. + +**Table 6.3.2.1.2.1-1: PSFCH MPR simulation results for SL Contiguous CA** + +| $0 < R \leq 0.6$ | $0.6 < R \leq 1.0$ | +|------------------|--------------------| +| 6.0 | 11.0 | + +**Table 6.3.2.1.2.1-1: Evaluation scenarios and MPR for SL CA PSFCH** + +| Case | Aggregated BW/SCS/
RB number per BW | PSFCH RB on CC1+CC2/
RB index/ ( $N_{RB1}+N_{RB2}$ ) | Gap Ratio[2]
$((N_{RB1}+N_{RB2}) \cdot SCS \cdot 12 + (GB_1 + GB_2)) / (BW_1 + BW_2 - (GB_1 + GB_2))$ | MPR | +|------|----------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----| +| 1 | 10MHz+10MHz /
30kHz/
24 | 23+0 (1+1) | 0.11 | 0 | +| 2 | | 23+2 (1+3) | 0.15 | 0 | +| 3 | | 23+4 | 0.19 | 0 | +| 4 | | 23+6 | 0.23 | 0 | +| 5 | | 23+8 | 0.26 | 0 | +| 6 | | 23+10 | 0.30 | 0.5 | +| 7 | | 23+12 | 0.34 | 0.6 | +| 8 | | 23+14 | 0.38 | 3.5 | +| 9 | | 23+16 | 0.42 | 3.5 | +| 10 | | 23+18 | 0.46 | 3.5 | +| 11 | | 23+20 | 0.5 | 3.6 | +| 12 | | 23+22 | 0.53 | 3.9 | +| 13 | | 0+0 | 0.55 | 5.5 | +| 14 | | 0+2 | 0.59 | 5.6 | +| 15 | | 0+4 | 0.63 | 5.4 | + +| | | | | | +|----|-----------------------------|--------------|------|------| +| 16 | | 0+6 | 0.67 | 5.2 | +| 17 | | 0+8 | 0.7 | 5.7 | +| 18 | | 0+10 | 0.75 | 5.6 | +| 19 | | 0+12 | 0.78 | 9.1 | +| 20 | | 0+14 | 0.82 | 10.2 | +| 21 | | 0+16 | 0.86 | 10.2 | +| 22 | | 0+18 | 0.9 | 10.2 | +| 23 | | 0+20 | 0.93 | 10.2 | +| 24 | | 0+22 | 0.98 | 10.2 | +| 25 | | 0+23 | 1 | 10.3 | +| 26 | 20MHz+20MHz/
30kHz
51 | 50+0 (1+1) | 0.06 | 0 | +| 27 | | 50+5 (1+6) | 0.11 | 0 | +| 28 | | 50+10 (1+11) | 0.15 | 0 | +| 29 | | 50+15 (1+16) | 0.2 | 0 | +| 30 | | 50+20 (1+21) | 0.25 | 0.5 | +| 31 | | 50+25 (1+26) | 0.3 | 0.8 | +| 32 | | 50+30 (1+31) | 0.34 | 3.4 | +| 33 | | 50+35 (1+36) | 0.39 | 3.4 | +| 34 | | 50+40 (1+41) | 0.44 | 3.4 | +| 35 | | 50+45 (1+46) | 0.48 | 4.1 | +| 36 | | 0+0 (51+1) | 0.53 | 5.4 | +| 37 | | 0+5 (51+6) | 0.58 | 5.7 | +| 38 | | 0+10 (51+11) | 0.62 | 5.7 | +| 39 | | 0+15 (51+16) | 0.67 | 9.8 | +| 40 | | 0+20 (51+21) | 0.72 | 10 | +| 41 | | 0+25 (51+26) | 0.76 | 10.2 | +| 42 | | 0+30 (51+31) | 0.81 | 10.2 | +| 43 | | 0+35 (51+36) | 0.86 | 10.2 | +| 44 | | 0+40 (51+41) | 0.9 | 10.3 | +| 45 | | 0+45 (51+46) | 0.95 | 10.3 | +| 46 | | 0+50 (51+51) | 1.0 | 10.3 | + +###### 6.3.2.1.2.2 LGE's simulation results (R4-2315532) + +The following simulation scenarios are considered as Table 6.3.2.1.2.2-1 for SL contiguous CA. + +Table 6.3.2.1.2.2-1: SL contiguous CA MPR test scenarios + +| Aggregate d CBW | Scenario | CC1 | CC2 | R = $\frac{N_{Gap}}{(N_{RB1}+N_{RB2}+N_{GBchannel\_CC1}+N_{GBchannel\_CC2})}$ | SCS | +|-----------------|----------|-------|--------|-------------------------------------------------------------------------------|-----| +| 10MHz + 10MHz | 1 | 1RB0 | - | | 15 | +| | 2 | 1RB51 | - | | 15 | +| | 3 | 1RB0 | 1RB0 | 0.5255 | 15 | +| | 4 | 1RB0 | 1RB10 | 0.6185 | 15 | +| | 5 | 1RB0 | 1RB20 | 0.7116 | 15 | +| | 6 | 1RB0 | 1RB30 | 0.8046 | 15 | +| | 7 | 1RB0 | 1RB40 | 0.8976 | 15 | +| | 8 | 1RB0 | 1RB51 | 1.0 | 15 | +| | 9 | 1RB10 | 1RB0 | 0.4324 | 15 | +| | 10 | 1RB20 | 1RB0 | 0.3394 | 15 | +| | 11 | 1RB30 | 1RB0 | 0.2463 | 15 | +| | 12 | 1RB40 | 1RB0 | 0.1533 | | +| | 13 | 1RB51 | 1RB0 | 0.0509 | 15 | +| 20MHz + 30MHz | 14 | 1RB0 | - | | 30 | +| | 15 | 1RB50 | - | | 30 | +| | 16 | 1RB0 | 1RB0 | 0.4248 | 30 | +| | 17 | 1RB0 | 1RB10 | 0.4995 | 30 | +| | 18 | 1RB0 | 1RB20 | 0.5742 | 30 | +| | 19 | 1RB0 | 1RB30 | 0.6489 | 30 | +| | 20 | 1RB0 | 1RB40 | 0.7236 | 30 | +| | 21 | 1RB0 | 1RB50 | 0.7983 | 30 | +| | 22 | 1RB0 | 1RB60 | 0.8730 | 30 | +| | 23 | 1RB0 | 1RB70 | 0.9477 | 30 | +| | 24 | 1RB0 | 1RB77 | 1.0 | 30 | +| | 25 | 1RB10 | 1RB0 | 0.3501 | 30 | +| | 26 | 1RB20 | 1RB0 | 0.2754 | 30 | +| | 27 | 1RB30 | 1RB0 | 0.2007 | 30 | +| | 28 | 1RB40 | 1RB0 | 0.1260 | 30 | +| | 29 | 1RB50 | 1RB0 | 0.0513 | 30 | +| 20MHz + 40MHz | 30 | 1RB0 | - | | 30 | +| | 31 | 1RB50 | - | | 30 | +| | 32 | 1RB0 | 1RB0 | 0.3509 | 30 | +| | 33 | 1RB0 | 1RB10 | 0.4127 | 30 | +| | 34 | 1RB0 | 1RB20 | 0.4745 | 30 | +| | 35 | 1RB0 | 1RB30 | 0.5363 | 30 | +| | 36 | 1RB0 | 1RB40 | 0.5981 | 30 | +| | 37 | 1RB0 | 1RB50 | 0.6600 | 30 | +| | 38 | 1RB0 | 1RB60 | 0.7218 | 30 | +| | 39 | 1RB0 | 1RB70 | 0.7836 | 30 | +| | 40 | 1RB0 | 1RB80 | 0.8454 | 30 | +| | 41 | 1RB0 | 1RB90 | 0.9073 | 30 | +| | 42 | 1RB0 | 1RB100 | 0.9691 | 30 | +| | 43 | 1RB0 | 1RB105 | 1.0 | 30 | +| | 44 | 1RB10 | 1RB0 | 0.2890 | 30 | +| | 45 | 1RB20 | 1RB0 | 0.2272 | 30 | +| | 46 | 1RB30 | 1RB0 | 0.1654 | 30 | +| | 47 | 1RB40 | 1RB0 | 0.1036 | 30 | +| | 48 | 1RB50 | 1RB0 | 0.0417 | 30 | +| 30MHz + | 49 | 1RB0 | - | | 30 | + +| | | | | | | +|------------------|----|-------|--------|--------|----| +| 40MHz | 50 | 1RB77 | - | | 30 | +| | 51 | 1RB0 | 1RB0 | 0.4449 | 30 | +| | 52 | 1RB0 | 1RB10 | 0.4977 | 30 | +| | 53 | 1RB0 | 1RB20 | 0.5506 | 30 | +| | 54 | 1RB0 | 1RB30 | 0.6035 | 30 | +| | 55 | 1RB0 | 1RB40 | 0.6563 | 30 | +| | 56 | 1RB0 | 1RB50 | 0.7092 | 30 | +| | 57 | 1RB0 | 1RB60 | 0.7621 | 30 | +| | 58 | 1RB0 | 1RB70 | 0.8150 | 30 | +| | 59 | 1RB0 | 1RB80 | 0.8678 | 30 | +| | 60 | 1RB0 | 1RB90 | 0.9207 | 30 | +| | 61 | 1RB0 | 1RB100 | 0.9736 | 30 | +| | 62 | 1RB0 | 1RB105 | 1.0000 | 30 | +| | 63 | 1RB10 | 1RB0 | 0.3920 | 30 | +| | 64 | 1RB20 | 1RB0 | 0.3391 | 30 | +| | 65 | 1RB30 | 1RB0 | 0.2862 | 30 | +| | 66 | 1RB40 | 1RB0 | 0.2334 | 30 | +| | 67 | 1RB50 | 1RB0 | 0.1805 | 30 | +| | 68 | 1RB60 | 1RB0 | 0.1276 | 30 | +| | 69 | 1RB70 | 1RB0 | 0.0748 | 30 | +| | 70 | 1RB77 | 1RB0 | 0.0377 | 30 | +| 20MHz +
20MHz | 71 | 1RB0 | - | | 30 | +| | 72 | 1RB51 | - | | 30 | +| | 73 | 1RB0 | 1RB0 | 0.5304 | 30 | +| | 74 | 1RB0 | 1RB10 | 0.6243 | 30 | +| | 75 | 1RB0 | 1RB20 | 0.7182 | 30 | +| | 76 | 1RB0 | 1RB30 | 0.8122 | 30 | +| | 77 | 1RB0 | 1RB40 | 0.9061 | 30 | +| | 78 | 1RB0 | 1RB50 | 1.0 | 30 | +| | 79 | 1RB10 | 1RB0 | 0.4365 | 30 | +| | 80 | 1RB20 | 1RB0 | 0.3426 | 30 | +| | 81 | 1RB30 | 1RB0 | 0.2486 | 30 | +| | 82 | 1RB40 | 1RB0 | 0.1547 | 30 | +| | 83 | 1RB50 | 1RB0 | 0.0608 | 30 | +| 10MHz +
30MHz | 84 | 1RB0 | - | | 30 | +| | 85 | 1RB23 | - | | 30 | +| | 86 | 1RB0 | 1RB0 | 0.2768 | 30 | +| | 87 | 1RB0 | 1RB10 | 0.3707 | 30 | +| | 88 | 1RB0 | 1RB20 | 0.4646 | 30 | +| | 89 | 1RB0 | 1RB30 | 0.5586 | 30 | +| | 90 | 1RB0 | 1RB40 | 0.6525 | 30 | +| | 91 | 1RB0 | 1RB50 | 0.7464 | 30 | +| | 92 | 1RB0 | 1RB60 | 0.8403 | 30 | +| | 93 | 1RB0 | 1RB70 | 0.9343 | 30 | +| | 94 | 1RB0 | 1RB77 | 1.0 | 30 | +| | 95 | 1RB10 | 1RB0 | 0.1829 | 30 | +| | 96 | 1RB20 | 1RB0 | 0.0890 | 30 | +| | 97 | 1RB23 | 1RB0 | 0.0608 | 30 | + +Here, the aggregated CA bandwidth is CA bandwidth class B which is composed of 2 CCs (CC1 + CC2). The ratio of $N_{Gap}/(N_{RB1}+N_{RB2}+ N_{GBchannel\_CC1}+ N_{GBchannel\_CC2})$ is considered. + +$$R = N_{Gap}/(N_{RB1}+N_{RB2}+ N_{GBchannel\_CC1}+ N_{GBchannel\_CC2})$$ + +$N_{Gap}$ is the gap RB amount from CC1 $RB_{start}$ to CC2 $RB_{end}$ for SL contiguous CA when a single PSFCH or contiguous and non-contiguous allocation simultaneous PSFCHs is transmitted in each CC. + +$N_{GBchannel\_CC1}$ and $N_{GBchannel\_CC2}$ is the number of RB which corresponds to the minimum guardbands for CC1 and CC2, respectively, which have been calculated using the following equation: + +$$N_{GBchannel} = GB_{channel} / (SCS \times 12)$$ + +$$GB_{channel} = (BW_{Channel} - N_{RB} \times SCS \times 12) / 2 - SCS/2,$$ + +where $N_{RB}$ are from Table 5.3.2-1 in TS38.101-1, and $BW_{Channel}$ is the channel bandwidth for each CC. + +Figure 6.3.2.1.2.2-1 shows $N_{Gap}$ , $N_{RB1}$ , $N_{RB2}$ , $N_{GBchannel\_CC1}$ , and $N_{GBchannel\_CC2}$ . + +![Figure 6.3.2.1.2.2-1: Parameters related to Ratio of R. The diagram illustrates the frequency domain representation of two component carriers (CC1 and CC2) with their respective bandwidths (BW_channel_CC1 and BW_channel_CC2), resource block counts (N_RB1 and N_RB2), and guardband parameters (N_Gap, N_GBchannel_CC1, N_GBchannel_CC2). PSFCH(1RB) blocks are shown at the edges of each carrier.](3b1633ab47237ea4abb37cb4f715d183_img.jpg) + +The diagram shows two component carriers, CC1 and CC2, in the frequency domain. CC1 is represented by a yellow block and CC2 by an orange block. The total bandwidth of CC1 is labeled $BW_{channel\_CC1}$ and the total bandwidth of CC2 is labeled $BW_{channel\_CC2}$ . The number of resource blocks (RBs) for CC1 is $N_{RB1}$ and for CC2 is $N_{RB2}$ . The gap between the two carriers is labeled $N_{Gap}$ . The minimum guardband for CC1 is labeled $N_{GBchannel\_CC1}$ and for CC2 is labeled $N_{GBchannel\_CC2}$ . PSFCH(1RB) blocks are shown at the edges of each carrier, indicated by yellow and orange blocks at the ends of the carriers. + +Figure 6.3.2.1.2.2-1: Parameters related to Ratio of R. The diagram illustrates the frequency domain representation of two component carriers (CC1 and CC2) with their respective bandwidths (BW\_channel\_CC1 and BW\_channel\_CC2), resource block counts (N\_RB1 and N\_RB2), and guardband parameters (N\_Gap, N\_GBchannel\_CC1, N\_GBchannel\_CC2). PSFCH(1RB) blocks are shown at the edges of each carrier. + +**Figure 6.3.2.1.2.2-1: Parameters related to Ratio of R** + +Table 6.3.2.1.2.2-2 and Figure 6.3.2.1.2.2-2 show the PSFCH MPR simulation results. + +Table 6.3.2.1.2.2-2: PSFCH MPR simulation results for SL Contiguous CA + +| | | | | | | | | | | | | | | | | | | +|---------------|------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|------|------|------|------|------| +| '10MHz+10MHz' | Scenario # | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9 | #10 | #11 | #12 | #13 | | | | +| | R | - | - | 0.53 | 0.62 | 0.71 | 0.80 | 0.90 | 1.00 | 0.43 | 0.34 | 0.25 | 0.15 | 0.05 | | | | +| | | 2.66 | 0.00 | 6.91 | 6.91 | 11.14 | 11.14 | 10.68 | 10.70 | 2.04 | 0.84 | 0.00 | 0.00 | 0.00 | | | | +| '20MHz+30MHz' | Scenario # | #14 | #15 | #16 | #17 | #18 | #19 | #20 | #21 | #22 | #23 | #24 | #25 | #26 | #27 | #28 | #29 | +| | R | - | - | 0.42 | 0.50 | 0.57 | 0.65 | 0.72 | 0.80 | 0.87 | 0.95 | 1.00 | 0.35 | 0.28 | 0.20 | 0.13 | 0.05 | +| | | 1.59 | 0.00 | 6.37 | 5.88 | 5.40 | 10.63 | 11.08 | 10.63 | 10.63 | 10.17 | 10.18 | 2.04 | 0.84 | 0.00 | 0.00 | 0.00 | +| '20MHz+40MHz' | Scenario # | #30 | #31 | #32 | #33 | #34 | #35 | #36 | #37 | #38 | #39 | | | | | | | +| | R | - | - | 0.35 | 0.41 | 0.47 | 0.54 | 0.60 | 0.66 | 0.72 | 0.78 | | | | | | | +| | | 2.58 | 0.00 | 1.68 | 6.39 | 5.90 | 5.90 | 11.10 | 10.64 | 10.18 | 9.71 | | | | | | | +| | Scenario # | #40 | #41 | #42 | #43 | #44 | #45 | #46 | #47 | #48 | | | | | | | | +| | R | 0.85 | 0.91 | 0.97 | 1.00 | 0.29 | 0.23 | 0.17 | 0.10 | 0.04 | | | | | | | | +| | | 10.64 | 11.10 | 10.64 | 10.65 | 1.22 | 0.84 | 0.00 | 0.00 | 0.00 | | | | | | | | +| '30MHz+40MHz' | Scenario # | #49 | #50 | #51 | #52 | #53 | #54 | #55 | #56 | #57 | #58 | #59 | | | | | | +| | R | - | - | 0.44 | 0.50 | 0.55 | 0.60 | 0.66 | 0.71 | 0.76 | 0.82 | 0.87 | | | | | | +| | | 3.15 | 0.00 | 5.45 | 6.42 | 5.94 | 11.14 | 10.68 | 9.75 | 10.68 | 10.68 | 11.14 | | | | | | +| | Scenario # | #60 | #61 | #62 | #63 | #64 | #65 | #66 | #67 | #68 | #69 | #70 | | | | | | +| | R | 0.92 | 0.97 | 1.00 | 0.39 | 0.34 | 0.29 | 0.23 | 0.18 | 0.13 | 0.07 | 0.04 | | | | | | +| | | 10.68 | 10.22 | 11.16 | 2.04 | 2.04 | 1.21 | 1.21 | 0.00 | 0.00 | 0.00 | 0.00 | | | | | | +| '20MHz+20MHz' | Scenario # | #71 | #72 | #73 | #74 | #75 | #76 | #77 | #78 | #79 | #80 | #81 | #82 | #83 | | | | +| | R | - | - | 0.53 | 0.62 | 0.72 | 0.81 | 0.91 | 1.00 | 0.44 | 0.34 | 0.25 | 0.15 | 0.06 | | | | +| | | 2.66 | 0.00 | 6.43 | 10.68 | 10.68 | 11.14 | 10.68 | 10.70 | 2.48 | 0.84 | 0.00 | 0.00 | 0.00 | | | | +| '10MHz+30MHz' | Scenario # | #84 | #85 | #86 | #87 | #88 | #89 | #90 | #91 | #92 | #93 | #94 | #95 | #96 | #97 | | | +| | R | - | - | 0.28 | 0.37 | 0.46 | 0.56 | 0.65 | 0.75 | 0.84 | 0.93 | 1.00 | 0.18 | 0.09 | 0.06 | | | +| | | 2.66 | 0.00 | 1.31 | 2.14 | 5.45 | 5.45 | 10.22 | 11.14 | 10.68 | 10.22 | 10.70 | 0.84 | 0.00 | 0.00 | | | + +Table 6.3.2.1.2.2-3 shows the maximum value of simulation results for SL Contiguous CA considering the ratio of R. + +$$R = N_{\text{Gap}} / (N_{\text{RB1}} + N_{\text{RB2}} + N_{\text{GBchannel\_CC1}} + N_{\text{GBchannel\_CC2}})$$ + +**Table 6.3.2.1.2.2-3 : PSFCH MPR simulation results for SL Contiguous CA** + +| MPR for ratio (R) in bandwidth class B(dB) | | | +|--------------------------------------------|----------------------|---------------------| +| $R \leq 0.33$ | $0.33 < R \leq 0.55$ | $0.55 < R \leq 1.0$ | +| 1.31 | 6.91 | 11.16 | + +The MPR can be proposed as Table 6.3.2.1.2.2-4 based on the simulation results when considering implementation margin. + +**Table 6.3.2.1.2.2-4 PSFCH MPR simulation results for SL Contiguous CA** + +| MPR for ratio (R) in bandwidth class B(dB) | | | +|------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------| +| $R \leq 0.33$ | $0.33 < R \leq 0.55$ | $0.55 < R \leq 1.0$ | +| 3.5 | 9.0 | 13.0 | +| Here, $R = N_{\text{Gap}} / (N_{\text{RB1}} + N_{\text{RB2}} + N_{\text{GBchannel\_CC1}} + N_{\text{GBchannel\_CC2}})$ | | | + +### 6.3.2.1.3 MPR for S-SSB transmission + +When single S-SSB is transmitted on intra-band contiguous carriers, required MPR for single cell V2X in Table 6.2E.2.2-2 is reused. For two S-SSB transmissions on intra-band contiguous carriers, the required MPR are specified as follow. + +**Table 6.3.2.1.3-1: MPR for two S-SSB transmissions on intra-band contiguous carriers for power class 3** + +| MPR for bandwidth class B(dB) | | | +|-------------------------------|--------|--------| +| Inner | Outer1 | Outer2 | +| 3.5 | 9.0 | 13.0 | + +#### 6.3.2.1.3.1 LGE's simulation results (R4-2315532) + +The following simulation scenarios are considered as Table 6.3.2.1.3.1-1 for SL contiguous CA. + +**Table 6.3.2.1.3.1-1: SL contiguous CA MPR test scenarios** + +| Aggregated CBW | Scenario | CC1 | CC2 | Inner/Outer1/
Outer2 RB allocation | SCS | +|----------------|----------|--------|--------|---------------------------------------|-----| +| 10MHz + 10MHz | 1 | 11RB0 | 11RB41 | Outer2 | 15 | +| | 2 | 11RB18 | 11RB22 | Outer2 | 15 | +| | 3 | 11RB20 | 11RB22 | Outer1 | 15 | +| | 4 | 11RB33 | 11RB17 | Outer1 | 15 | +| | 5 | 11RB35 | 11RB7 | Inner | 15 | +| | 6 | 11RB41 | 11RB0 | Inner | 15 | +| 20MHz + 30MHz | 7 | 11RB0 | 11RB67 | Outer2 | 30 | +| | 8 | 11RB15 | 11RB32 | Outer2 | 30 | +| | 9 | 11RB15 | 11RB30 | Outer1 | 30 | +| | 10 | 11RB33 | 11RB7 | Outer1 | 30 | +| | 11 | 11RB34 | 11RB7 | Inner | 30 | +| | 12 | 11RB40 | 11RB0 | Inner | 30 | +| 20MHz + 40MHz | 13 | 11RB0 | 11RB95 | Outer2 | 30 | +| | 14 | 11RB4 | 11RB30 | Outer2 | 30 | +| | 15 | 11RB15 | 11RB30 | Outer1 | 30 | +| | 16 | 11RB33 | 11RB7 | Outer1 | 30 | +| | 17 | 11RB34 | 11RB7 | Inner | 30 | +| | 18 | 11RB40 | 11RB0 | Inner | 30 | +| 30MHz + 40MHz | 19 | 11RB0 | 11RB95 | Outer2 | 30 | +| | 20 | 11RB4 | 11RB30 | Outer2 | 30 | +| | 21 | 11RB15 | 11RB30 | Outer1 | 30 | +| | 22 | 11RB47 | 11RB7 | Outer1 | 30 | +| | 23 | 11RB48 | 11RB7 | Inner | 30 | +| | 24 | 11RB67 | 11RB0 | Inner | 30 | +| 20MHz + 20MHz | 25 | 11RB0 | 11RB40 | Outer2 | 30 | +| | 26 | 11RB4 | 11RB30 | Outer2 | 30 | +| | 27 | 11RB28 | 11RB7 | Outer1 | 30 | +| | 28 | 11RB33 | 11RB7 | Outer1 | 30 | +| | 29 | 11RB34 | 11RB0 | Inner | 30 | +| | 30 | 11RB40 | 11RB0 | Inner | 30 | +| 10MHz + 30MHz | 31 | 11RB0 | 11RB67 | Outer2 | 30 | +| | 32 | 11RB7 | 11RB32 | Outer2 | 30 | +| | 33 | 11RB7 | 11RB31 | Outer1 | 30 | +| | 34 | 11RB13 | 11RB1 | Outer1 | 30 | +| | 35 | 11RB13 | 11RB0 | Inner | 30 | + +Table 6.3.2.1.3.1-2 and Figure 6.3.2.1.3.1-1 show the S-SSB MPR simulation results. + +**Table 6.3.2.1.3.1-2: S-SSB MPR simulation results for SL Contiguous CA** + +| | | | | | | | | +|---------------|-------------------|------------|------------|------------|------------|------------|------------| +| '10MHz+10MHz' | Scenario # | #1 | #2 | #3 | #4 | #5 | #6 | +| | | 10.21 | 6.30 | 6.20 | 1.25 | 1.08 | 1.50 | +| '20MHz+30MHz' | Scenario # | #7 | #8 | #9 | #10 | #11 | #12 | +| | | 8.20 | 4.52 | 4.38 | 1.14 | 1.09 | 1.46 | +| '20MHz+40MHz' | Scenario # | #13 | #14 | #15 | #16 | #17 | #18 | +| | | 8.08 | 4.50 | 4.62 | 1.23 | 1.06 | 1.25 | +| '30MHz+40MHz' | Scenario # | #19 | #20 | #21 | #22 | #23 | #24 | +| | | 8.06 | 7.84 | 4.19 | 1.07 | 1.10 | 1.70 | +| '20MHz+20MHz' | Scenario # | #25 | #26 | #27 | #28 | #29 | #30 | +| | | 8.20 | 8.04 | 4.40 | 1.25 | 1.15 | 1.51 | +| '10MHz+30MHz' | Scenario # | #31 | #32 | #33 | #34 | #35 | | +| | | 8.20 | 4.24 | 4.50 | 1.55 | 1.52 | | + +Table 6.3.2.1.3.1-3 shows the maximum value of simulation results for SL Contiguous CA considering Inner, Outer1, and Outer 2 RB allocation ranges. + +**Table 6.3.2.1.3.1-3: S-SSB MPR simulation results for SL Contiguous CA** + +| MPR for bandwidth class B(dB) | | | +|--------------------------------------|---------------|---------------| +| Inner | Outer1 | Outer2 | +| 1.70 | 6.20 | 10.21 | + +The MPR can be proposed as Table 6.3.2.1.3.1-4 based on the simulation results when considering implementation margin. + +**Table 6.3.2.1.3.1-4 S-SSB MPR simulation results for SL Contiguous CA** + +| MPR for bandwidth class B(dB) | | | +|--------------------------------------|---------------|---------------| +| Inner | Outer1 | Outer2 | +| 3.5 | 9.0 | 13.0 | + +### 6.3.3 UE additional maximum output power reduction for NR SL CA operation + +For the additional emission limits in Europe in ITS spectrum, RAN4 already defined the regulatory requirements in TS38.101-1. The ETSI regulation shall be considered to derive the A-MPR requirements for NR SL CA UE. For the US related regulatory requirements will be studied after final FCC announcement for the additional emission limits in US. + +To derive A-MPR requirements for SL CA operation in ITS spectrum, RAN4 will assume the basic simulation parameters and assumptions in section 6.3.2 and the additional spectrum emission mask in Table 6.5E.2.3.1-1 and additional spurious emission requirements in Table 6.5E.3.4.2-1 and Table 6.5E.3.4.2-2 in TS38.101-1 will be considered when NS\_33 is configured from the pre-configured radio parameters in the geometrical region or indicated in the cell. + +#### 6.3.3.1 A-MPR for NR SL CA operation + +##### 6.3.3.1.1 A-MPR for Intra-band contiguous SL CA operation + +##### 6.3.3.1.2 LGE's A-MPR simulation results for SLCA\_NS\_52 + +**Table 6.3.3.1.2-0: SLCA\_NS\_52' for SL intra-band C-CA A-MPR** + +| Sidelink CA | Value of additionalSpectrumEmission | +|--------------------|--------------------------------------------| +|--------------------|--------------------------------------------| + +| operating band | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +|------------------------------------------------------------------------------------------------------------------------------|------------|---|------------|---|---|---|---|---| +| SL_n47 | SLCA_NS_01 | | SLCA_NS_52 | | | | | | +| NOTE: additionalSpectrumEmission corresponds to an information element of the same name defined in clause 6.3.2 of TS 38.331 | | | | | | | | | + +For SL intra-band contiguous CA of PSCCH and PSSCH simultaneous transmission with contiguous RB allocation, the allowed A-MPR for the maximum output power are specified in Table 6.3.3.1.2-1. + +**Table 6.3.3.1.2-1: A-MPR for power class 3 SL CA with contiguous RB allocation** + +| Modulation | | A-MPR for bandwidth class B(dB) | | +|------------|--------|---------------------------------|------------| +| | | inner | outer | +| CP-OFDM | QPSK | $\leq 7.0$ | $\leq 8.5$ | +| | 16QAM | $\leq 7.0$ | $\leq 8.5$ | +| | 64QAM | $\leq 7.0$ | $\leq 8.5$ | +| | 256QAM | $\leq 7.0$ | $\leq 8.5$ | + +The contiguous allocation rule of inner and outer for SL intra-band contiguous CA refers to that for NR intra-band contiguous CA in 6.2A.2.1 in TS38.101-1. + +For SL intra-band contiguous CA of PSCCH and PSSCH simultaneous transmission with non-contiguous RB allocation, the allowed A-MPR for the maximum output power are specified in Table 6.3.3.1.2-2. + +**Table 6.3.3.1.2-2: A-MPR for power class 3 SL CA with non-contiguous RB allocation** + +| Modulation | | MPR for bandwidth class B(dB) | | | +|------------|--------|-------------------------------|------------|-------------| +| | | Inner | Outer1 | Outer2 | +| CP-OFDM | QPSK | $\leq 3.0$ | $\leq 8.0$ | $\leq 13.5$ | +| | 16QAM | $\leq 3.0$ | $\leq 8.0$ | $\leq 13.5$ | +| | 64QAM | $\leq 4.5$ | $\leq 8.0$ | $\leq 13.5$ | +| | 256QAM | $\leq 7.0$ | $\leq 8.0$ | $\leq 13.5$ | + +The non-contiguous allocation rule of inner, outer1, and outer2 for SL intra-band contiguous CA refers to that for NR intra-band contiguous CA in 6.2A.2.1 in TS38.101-1. + +For SL intra-band contiguous CA of PSFCH transmission, the allowed A-MPR for the maximum output power are specified in Table 6.3.3.1.2-3. + +**Table 6.3.3.1.2-3: A-MPR for PSFCH transmission for power class 3 SL CA** + +| MPR for ratio (R) in bandwidth class B(dB) | | | +|--------------------------------------------|---------------------|---------------------| +| $R \leq 0.1$ | $0.1 < R \leq 0.55$ | $0.55 < R \leq 1.0$ | +| $\leq 4.0$ | $\leq 17.0$ | $\leq 19.0$ | + +In Table 6.3.3.1.2-3, R is defined in 6.3.2.1.2. + +For SL intra-band contiguous CA of S-SSB transmission, the allowed A-MPR for the maximum output power are specified in Table 6.3.3.1.2-4. + +**Table 6.3.3.1.2-4: A-MPR for S-SSB transmission for power class 3 SL CA** + +| MPR for bandwidth class B(dB) | | | +|-------------------------------|-------------|-------------| +| Inner | Outer1 | Outer2 | +| $\leq 9.0$ | $\leq 13.0$ | $\leq 16.5$ | + +The non-contiguous allocation rule of inner, outer1, and outer2 for SL intra-band contiguous CA refers to that for NR intra-band contiguous CA in 6.2A.2.1 in TS38.101-1. + +### 6.3.4 Configured transmitted power for NR SL CA operation + +For intra-band contiguous SL CA operation, $MPR_c = MPR$ and $A-MPR_c = A-MPR$ with $MPR$ and $A-MPR$ specified in subclause 6.3.2 and subclause 6.3.4 respectively. There is one power management term for the UE, denoted $P-MPR$ , and $P-MPR_c = P-MPR$ . $P_{CMAX,c}$ is calculated under the assumption that the transmit power is increased by the same amount in dB on all component carriers. + +The total configured maximum output power $P_{CMAX}$ shall be set within the following bounds: + +$$P_{CMAX\_L} \leq P_{CMAX} \leq P_{CMAX\_H}$$ + +For SL transmission of intra-band contiguous CA when same slot pattern is used in all aggregated component carriers. + +$$P_{CMAX\_L} = \text{MIN} \{ 10 \log_{10} \sum p_{EMAX,c} - \Delta T_c, P_{PowerClass, SL\_CA} - \text{MAX}(\text{MAX}(MPR, A-MPR) + \Delta T_{IB,c} + \Delta T_c, P-MPR), P_{Regulatory}, P_{EMAX, CA} \}$$ + +$$P_{CMAX\_H} = \text{MIN} \{ 10 \log_{10} \sum p_{EMAX,c}, P_{PowerClass, SL\_CA}, P_{Regulatory}, P_{EMAX, CA} \}$$ + +where + +- For the total transmitted power $P_{CMAX,PSSCH/PSCCH}$ , $P_{EMAX,CA}$ is the value given by [the sum of IE *sl-maxTransPower* from each CC or new IE for maximum transmitted power of SL CA], defined by TS 38.331; +- $P_{PowerClass, SL\_CA}$ is the maximum UE power specified in Table 6.3.1-1 without taking into account the tolerance; +- $MPR$ and $A-MPR$ are specified in subclause 6.3.2 and subclause 6.3.3 respectively; +- $\Delta T_{IB,c}$ and $P-MPR$ are specified in clause 6.2.4 in TS38.101-1; +- $\Delta T_c$ is the highest value $\Delta T_{c,c}$ among all component carriers $c$ in the subframe over both timeslots. $\Delta T_{c,c} = 1.5$ dB when NOTE 3 in Table 6.2.1-1 in TS38.101-1 applies, otherwise $\Delta T_{c,c} = 0$ dB; +- $P_{Regulatory} = 10 - G_{post\ connector}$ dBm when V2X UE is within the protected zone in ETSI TS 102 792 of CEN DSRC tolling system and operating in Band n47; $P_{Regulatory} = 33 - G_{post\ connector}$ dBm otherwise. + +The maximum output power $P_{CMAX,PSSCH}$ and $P_{CMAX,PSCCH}$ are derived from $P_{CMAX,c}$ based on 0dB PSD offset between PSSCH and PSCCH. + +For intra-band SL CA operation, when at least one different numerology/slot pattern is used in aggregated cells, the same requirement as specified in clause 6.2E.4.3 in TS38.101-1 shall be applied. + +The measured configured maximum output power $P_{UMAX,c}$ for sidelink CA operation, when at least one slot has a different transmission numerology or slot pattern, the same requirement as specified in clause 6.2E.4.3 in TS38.101-1 shall be applied. + +### 6.3.5 Minimum output power for NR SL CA operation + +For SL intra-band contiguous CA, the minimum output power requirement as specified in table 6.3.5-1 shall be applied per component carrier. + +**Table 6.3.5-1: Minimum output power** + +| Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|-------------------------|----------------------------|------------------------------------------| +| 10 | -30 | MBW=REF_SCS*(12*N RB +1)/1000 | +| 20 | -30 | | +| 30 | -28.2 | | +| 40 | -27 | | + +### 6.3.6 Transmit OFF power for NR SL CA operation + +For SL intra-band contiguous CA, the transmit OFF power requirement as specified in Table 6.3.6-1 shall be applied per component carrier. + +**Table 6.3.6-1: Transmit OFF power** + +| Channel bandwidth (MHz) | Transmit OFF power (dBm) | Measurement bandwidth (MHz) | +|-------------------------|--------------------------|------------------------------------------| +| 10 | -50 | MBW=REF_SCS*(12*N RB +1)/1000 | +| 20 | -50 | | +| 30 | -50 | | +| 40 | -50 | | + +### 6.3.7 ON/OFF time mask for NR SL CA operation + +For SL intra-band contiguous CA, the SL ON/OFF time masks specified in clause 6.3E.3.2, 6.3E.3.3 and 6.3E.3.4 in TS38.101-1 are applicable for each component carrier during the ON power period and the transient periods. The OFF period shall only be applicable for each component carrier when all the component carriers are OFF. + +Additionally, RAN4 can define the switching ON/OFF time mask between NR SL CA and NR SL single carrier operation as like fallback mode. In the case, the ON/OFF time mask in figure 6.3E.3.4-2 in TS38.101-1 for different carriers can be reused. + +### 6.3.8 Power control for NR SL CA operation + +For SL intra-band contiguous CA, the power control requirement as specified in clause 6.3E.4.2 in TS38.101-1 shall be applied per component carrier. + +### 6.3.9 Transmit signal quality for NR SL CA operation + +#### 6.3.9.1 Frequency Error + +For SL intra-band contiguous CA, $\pm 0.1$ PPM observed over a period of 1 ms will be applied per CC compared to the absolute frequency in case of using GNSS synchronization source. The same requirements will be applied to all SL synchronous reference sources (the gNB or V2X synchronization reference UE). + +#### 6.3.9.2 EVM + +For SL intra-band contiguous CA, the EVM requirement as specified in clause 6.4E.2.2 in TS38.101-1 shall be applied per component carrier. + +#### 6.3.9.3 Carrier Leakage + +For SL intra-band contiguous CA, the carrier leakage requirement as specified in clause 6.4E.2.3 in TS38.101-1 shall be applied per component carrier when only one SL transmission carrier is activated in a time. + +#### 6.3.9.4 In-band Emission + +For SL intra-band contiguous CA, the In-band emission requirement as specified in clause 6.4E.2.4 in TS38.101-1 shall be applied to the SL aggregated transmission bandwidth. This is same as NR intra-band CA UE. + +### 6.3.10 Spectrum emission mask for NR SL CA operation + +#### 6.3.10.1 Occupied Bandwidth + +For SL intra-band contiguous CA, the occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the aggregated CBW. The occupied bandwidth shall be less than the aggregated channel bandwidth. + +### 6.3.10.2 SEM + +For SL intra-band contiguous CA, the SEM requirement for NR intra-band contiguous CA as specified in clause 6.5A.2.2.1 in TS38.101-1 shall be applied to the aggregated channel bandwidth with SL CA bandwidth class B. + +### 6.3.10.3 A-SEM + +For SL intra-band contiguous CA, RAN4 does not need to consider the A-SEM in Europe since the A-SEM in Table 6.5E.2.3.1-1 in TS38.101-1 is only applied for the 10MHz CBW in Europe. + +For the US region, RAN4 can reuse NS\_52, the details can be further discussed with the final A-SEM or A-SE requirements from FCC. + +## 6.3.11 ACLR requirements for NR SL CA operation + +For SL intra-band contiguous CA, the general NR CA ACLR requirements for CA Bandwidth Class B specified in subclause 6.5A.2.4.1.1 in TS38.101-1 shall be applied to the aggregated channel bandwidth with SL CA bandwidth class B. + +## 6.3.12 Spurious emissions for NR SL CA operation + +For SL intra-band contiguous CA, the general NR CA general SE for CA Bandwidth specified in subclause 6.5A.3.1 in TS38.101-1 shall be applied to the aggregated channel bandwidth with SL CA bandwidth class B. + +## 6.3.13 Spurious emission band UE co-existence for NR SL CA operation + +For SL intra-band contiguous CA, the protection operating band lists for n47 transmission was defined in Table 6.5.3.2-1 in TS38.101-1 which shall be applied to NR SL intra-band contiguous CA UE. + +**Table 6.3.13-1: Requirements for spurious emissions for UE co-existence** + +| NR Band | Spurious emission for UE co-existence | | | | | | | +|---------|-----------------------------------------------------------------------------------|-----------------------|---|----------------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| n47B | E-UTRA Band 1, 3, 5, 7, 8, 22, 26, 28, 34, 39, 40, 41, 42, 44, 45, 65, 68, 72, 73 | F DL_low | - | F DL_high | -50 | 1 | | +| | NR Band n71, n77, n78, n79 | F DL_low | - | F DL_high | -50 | 1 | | + +Also, RAN4 already defined the additional SE requirements as specified in clause 6.5E.3.4 in TS38.101-1 by the European Regulation which shall be considered to derive the A-MPR requirements with NS\_33 as follows. + +**Table 6.3.13-2: Additional requirements for "NS\_33"** + +| Protected band | | Frequency range (MHz) | | Maximum Level (EIRP 2 ) | MBW (MHz) | NOTE | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------|------|------------------------------------|-----------|------| +| Frequency range | 5925 | - | 5950 | -30 | 1 | 1 | +| Frequency range | 5815 | - | 5855 | -30 | 1 | 3 | +| NOTE 1: In the frequency range x-5950MHz, SE requirement of -30dBm/MHz should be applied; where x = max (5925, f c + 15), where f c is the channel centre frequency. | | | | | | | +| NOTE 2: The EIRP requirement is converted to conducted requirement depend on the supported post antenna connector gain G post connector declared by the UE following the principle described in annex I in [11]. | | | | | | | +| NOTE 3: Resolution BW is 10% of the measurement BW and the result should be integrated to achieve the measurement bandwidth. The sweep time shall be set larger than (symbol length)*(number of points in sweep) to improve the measurement accuracy. | | | | | | | + +Furthermore, when "NS\_33" is configured from pre-configured radio parameters or the cell, and the indication from upper layers has indicated that the UE is within the protection zone of CEN DSRC devices or HDR DSRC devices, the power of any NR V2X UE emission shall fulfil either one of the two sets of conditions. + +**Table 6.3.13-3: Requirements for spurious emissions to protect CEN DSRC for V2X UE** + +| | Maximum Transmission Power (dBm EIRP 1 ) | Emission Limit in Frequency Range 5795-5815 (dBm/MHz EIRP 1 ) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------| +| Condition 1 | 10 | -65 | +| Condition 2 | 10 | -45 | +| NOTE 1: The EIRP requirement is converted to conducted requirement depend on the supported post antenna connector gain $G_{\text{post connector}}$ declared by the UE following the principle described in annex I in [11]. | | | + +## 6.3.14 Transmit intermodulation for NR SL CA operation + +For SL intra-band contiguous CA, the general NR CA Transmit Intermodulation requirements for CA Bandwidth Class B specified in clause 6.5A.4.2.1 in TS38.101-1 shall be applied to the aggregated channel bandwidth with SL CA bandwidth class B. + +# 7 Receiver characteristics for NR SL evolution + +## 7.1 Rx requirements for NR SL single carrier operation in unlicensed bands + +### 7.1.1 Reference sensitivity power level for NR SL-U + +Background information for NR V2X reference sensitivity requirement has been captured in the TR 38.886 as captured below and can be reused for NR SL-U + +The reference sensitivity power level REFSENS is the minimum mean power applied to the UE antenna connector at which the throughput shall meet or exceed 95% of the maximum throughput of the reference measurement channels. + +The V2X UE REFSENS is defined by the following equation: + +$$\text{REFSENS}_{\text{V2X}} = kTB + \text{SNR}_{\text{V2X}} + 10\log_{10}(L_{\text{CRB}} * \text{SCS} * 12 / \text{RX\_BW}) + (\text{NF}_{\text{V2X}} + \text{IM}) - \text{Diversity gain}$$ + +Where + +- $kTB$ : Thermal noise level is $[-174\text{dBm}(kT) + 10 * \log_{10}(\text{RX BW})]\text{dBm}$ . +- NF: Noise figure. 13 dB is used for LAA and can be reused for NR V2X requirements. Assumed NF is $9\text{dB} < 3\text{GHz}$ , NF is $10\text{dB} \geq 3\text{GHz}$ (e.g B42, n77, n78, n79...) at licensed bands at FR1. +- IM: 2.5 dB is assumed. When the number of RB size equal to or less than 24RBs, 0.5dB additional relaxation is allowed. +- Target SNR: -0.5 dB +- Diversity gain: 3dB + +For NR-U, the following equations in table below are used to calculate the REFSENS requirement and it can be further re-used in NR SL-U in bands n46, n96 and n102, while taking account that for NR-U target SNR of -1dB was used and therefore the REFSENS values in table below are 0.5dB higher than with NR SL-U target SNR of 0.5dB. + +**Table 7.1.1-1 REFSSENS for NR-U** + +| Operating band / SCS / Channel bandwidth / REFSSENS | | | | | +|-----------------------------------------------------|---------|-------------------------|-----------------------------------|-------------| +| Operating band | SCS kHz | Channel bandwidth (MHz) | REFSENS (dBm) | Duplex Mode | +| n46 | 15 | 20, 40 | $-89.7 + 10\log_{10}(N_{RB}/106)$ | HD | +| | 30 | 20, 40, 60, 80, 100 | $-89.9 + 10\log_{10}(N_{RB}/51)$ | | +| | 60 | 20, 40, 60, 80, 100 | $-90.1 + 10\log_{10}(N_{RB}/24)$ | | +| n96, n102 | 15 | 20, 40 | $-89.2 + 10\log_{10}(N_{RB}/106)$ | HD | +| | 30 | 20, 40, 60, 80, 100 | $-89.4 + 10\log_{10}(N_{RB}/51)$ | | +| | 60 | 20, 40, 60, 80, 100 | $-89.6 + 10\log_{10}(N_{RB}/24)$ | | + +NOTE 1: The REFSSENS value is rounded to the nearest number down to one decimal point. "NRB" in REFSSENS formula is the RB configuration for SL-U REFSSENS as shown in table 7.1.1-1. + +For the NR-U REFESENS requirement, the RB configuration for larger than 20MHz is considered as wideband operation and hence all intra-cell guard bands between sub-bands should be filled. In this case, the full RB allocation of NR is used to define the reference sensitivity requirement. However, for V2X, specific RB allocation using the sub-channels based on the RAN2 specification TS 38.331 is used as captured below: + +``` + +SL-ResourcePool-r16 ::= SEQUENCE { + sl-PSCCH-Config-r16 SetupRelease { SL-PSCCH-Config-r16 } OPTIONAL, -- Need M + sl-PSSCH-Config-r16 SetupRelease { SL-PSSCH-Config-r16 } OPTIONAL, -- Need M + sl-PSFCH-Config-r16 SetupRelease { SL-PSFCH-Config-r16 } OPTIONAL, -- Need M + sl-SyncAllowed-r16 SL-SyncAllowed-r16 OPTIONAL, -- Need M + sl-SubchannelSize-r16 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100} OPTIONAL, -- Need M +} + +``` + +Following the TS 38.331 definitions Table 7.1.1-2 shows the RB configuration for NR SL-U reference sensitivity requirement. + +**Table 7.1.1-2 NR SL-U RB configurations for REFSSENS** + +| NR SL-U Band | SCS kHz | NR band / SCS / Channel bandwidth / Duplex mode | | | | | Duplex Mode | +|--------------|---------|-------------------------------------------------|-------|-------|-------|--------|-------------| +| | | 20MHz | 40MHz | 60MHz | 80MHz | 100MHz | | +| n46 | 15 | 105 | 216 | | | | HD | +| | 30 | 50 | 105 | 160 | 216 | 270 | | +| | 60 | 24 | 50 | 75 | 105 | 135 | | +| n96 | 15 | 105 | 216 | | | | HD | +| | 30 | 50 | 105 | 160 | 216 | 270 | | +| | 60 | 24 | 50 | 75 | 105 | 135 | | +| n102 | 15 | 105 | 216 | | | | HD | +| | 30 | 50 | 105 | 160 | 216 | 270 | | +| | 60 | 24 | 50 | 75 | 105 | 135 | | + +With the agreed SNR and RB configuration as above, the REFSENS requirement for NR SL-U is shown in Table 7.1.1-3. + +**Table 7.1.1-3 REFSSENS for SL-U** + +| Operating band / SCS / Channel bandwidth / REFSSENS | | | | | +|-----------------------------------------------------|---------|-------------------------|-----------------------------------|-------------| +| Operating band | SCS kHz | Channel bandwidth (MHz) | REFSENS (dBm) | Duplex Mode | +| n46 | 15 | 20, 40 | $-89.2 + 10\log_{10}(N_{RB}/105)$ | HD | +| | 30 | 20, 40, 60, 80, 100 | $-89.4 + 10\log_{10}(N_{RB}/50)$ | | +| | 60 | 20, 40, 60, 80, 100 | $-89.6 + 10\log_{10}(N_{RB}/24)$ | | +| n96, n102 | 15 | 20, 40 | $-88.7 + 10\log_{10}(N_{RB}/105)$ | HD | +| | 30 | 20, 40, 60, 80, 100 | $-88.9 + 10\log_{10}(N_{RB}/50)$ | | +| | 60 | 20, 40, 60, 80, 100 | $-89.1 + 10\log_{10}(N_{RB}/24)$ | | + +NOTE 1: The REFSSENS value is rounded to the nearest number down to one decimal point. "NRB" in REFSSENS formula is the RB configuration for NR SL-U REFSSENS as shown in table 7.1.1-2 + +## 7.1.2 Maximum input level for NR SL-U + +The Maximum input level for NR-U is defined in clause 7.4 of TS 38.101-1. For NR V2X, Maximum input level is defined in clause 7.4E.1. The NRV2X Sidelink requirement only covers up to 40MHz and the minimum requirement is the same as NR-U. + +It has been agreed to reuse the NRU Maximum input level requirements in TS 38.101-1 clause 7.4 for NR SL-U. + +## 7.1.3 Adjacent Channel Selectivity for NR SL-U + +For the ACS requirement, the ACS for NR-U was defined for bands above 3.3GHz considering the unlicensed bands of n46, n96, n102 are all high bands. However, the requirement format is different from NR single CC which can be found below, i.e. the ACS is adjusted according to the CBW while the NR single CC is fixed as 33dB for bands above 3.3GHz. The ACS requirement has been extensively discussed in NR-U WI with various views considering the difference of ACLR, ACIR impacts, and comparison with WIFI system, and coexistence with LAA, and the final value is a compromised outcome. + +**Table 7.5F.1-1: ACS for shared spectrum channel access bands** + +| RX parameter | Units | Channel bandwidth | +|------------------------------------------------------------|-------|-----------------------------------------------------| +| | | 20, 40, 60, 80, 100 MHz | +| ACS | dB | $24 - 10\log_{10}(\text{BW}_{\text{Channel}} / 20)$ | +| NOTE1: ACS value is rounded to the next higher 0.5dB value | | | + +**Table 7.5F.1-2: Test parameters for shared spectrum channel access bands** + +| RX parameter | Units | Channel bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------| +| | | 20, 40, 60, 80, 100 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + 14 dB | +| $P_{\text{interferer}}$ | dBm | $\text{REFSENS} + 36.5 \text{ dB} - 10\log_{10}(\text{BW}_{\text{Channel}} / 20) \text{ dB}$ | +| $\text{BW}_{\text{interferer}}$ | MHz | 20 | +| $F_{\text{interferer}}$ (offset) | MHz | 20 / -20 | +| NOTE 1: The transmitter shall be set to 4 dB below $P_{\text{CMAX\_L,f,c}}$ at the minimum UL configuration specified in Table 7.3.2-3 with $P_{\text{CMAX\_L,f,c}}$ defined in clause 6.2.4.
NOTE 2: The absolute value of the interferer offset $F_{\text{interferer}}$ (offset) shall be further adjusted to $(\lceil F_{\text{interferer}} / \text{SCS} \rceil + 0.5) \text{ SCS}$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with an SCS equal to that of the wanted signal.
NOTE 3: The interferer consists of the RMC specified in Annexes A.3.2.2 and A.3.3.2 with one sided dynamic OCNNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1. | | | + +### ACS Requirement for NR-U + +Furthermore, for NR normal requirement, there are two test cases for ACS as case 1 and case 2. During the NR-U discussion, the case 2 was considered not necessary for operation in unlicensed bands. It has been agreed to reuse NR-U ACS requirement for NR SL-U using the NR SL-U RMC, as discussed in general part. + +## 7.1.4 Blocking characteristics for NR SL-U + +### 7.1.4.1 In Band Blocking + +The in band blocking requirement for NR V2X is captured in clause 7.6E.2.1 and for NR-U it is captured in clause 7.F.2.1. The transmission power is the same for 20 and 40MHz and the difference is the bandwidth of interferer. The 10MHz as smallest CBW for NR V2X is used as $\text{BW}_{\text{interferer}}$ and corresponding offset frequency is decided. In NR SL-U, 10MHz is not supported and 20MHz is supported as the smallest CBW for single CC. + +**Table 7.6E.2.1-1: In-band blocking parameters for NR V2X** + +| RX parameter | Units | Channel bandwidth | | | | +|---------------------------------------------------------------------------------------------------------------------|-------|-------------------------------------------------------------------|--------|--------|--------| +| | | 10 MHz | 20 MHz | 30 MHz | 40 MHz | +| Power in transmission bandwidth configuration | dBm | P REFSENS_V2X + channel bandwidth specific value below | | | | +| | dB | 6 | 9 | 11 | 12 | +| BW interferer | MHz | 10 | | | | +| F offset , case 1 | MHz | 15 | | | | +| F offset , case 2 | MHz | 25 | | | | +| NOTE 1: The interferer is QPSK modulated PUSCH containing data and reference symbols. Normal cyclic prefix is used. | | | | | | + +**Table 7.6F.2.1-1: In-band blocking parameters for shared access bands** + +| RX parameter | Units | Channel bandwidth | +|-----------------------------------------------|-------|---------------------------------------------------------------------| +| | | 20, 40, 60, 80, 100 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + 9 dB + 10log 10 (BW channel /20) dB | +| BW interferer | MHz | 20 | +| F offset , case 1 | MHz | 30 | +| F offset , case 2 | MHz | ≥ 50 | + +In this case, the NR-U IBB can be reused for NR SL-U. + +### 7.1.4.2 Out of Band Blocking + +The NR sidelink OBB requirement is reused from LTE sidelink and hence different power level for the transmission power based on different bandwidth. For NR-U OBB requirement, it is based on the NR normal requirement since there is no Wi-Fi corresponding requirement. Further modification has applied for range 3 considering the shallower frequency response of the band filter at high frequencies. In this case, the NR-U requirement can be reused for NR SL-U. + +**Table 7.6E.3.1-1: Out-of-band blocking parameters for NR V2X** + +| RX parameter | Units | Channel bandwidth | | | | | +|------------------------------------------------------|-------|-------------------------------------------------------------------|--------|--------|--------|--------| +| | | 5 MHz 2 | 10 MHz | 20 MHz | 30 MHz | 40 MHz | +| Power in transmission bandwidth configuration | dBm | P REFSENS_V2X + channel bandwidth specific value below | | | | | +| | dB | 6 | 6 | 9 | 11 | 12 | +| NOTE 1: Reference measurement channel is A.7.2. | | | | | | | +| NOTE 2: The CBW is only applicable for PS UE in n14. | | | | | | | + +**Table 7.6F.3.1-1: Out-of-band blocking parameters for shared access bands** + +| RX parameter | Units | Channel bandwidth | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------| +| | | 20, 40, 60, 80, 100 MHz | +| Power in transmission bandwidth configuration | dBm | REFSENS + 9 dB | +| NOTE 1: The transmitter shall be set to 4 dB below P CMAX_L,f,c at the minimum UL configuration specified in Table 7.3.2-3 with P CMAX_L,f,c defined in clause 6.2.4. | | | + +### 7.1.4.3 Narrow Band Blocking + +Narrow band blocking was introduced in NR single CC to mimic the potential interference coming from narrow band systems, but such system is not existing in the targeting unlicensed spectrum and therefore the Narrow Band Blocking requirements are not defined for NR-U. + +It has been agreed not to define Narrow Band Blocking requirements for NR SL-U. + +### 7.1.5 Spurious response for NR SL-U + +The NR sidelink spurious response requirement is reused from LTE sidelink and hence different power level for the transmission power based on different bandwidth is used. For NR SL-U operation in unlicensed bands, the NR-U requirement can be reused. + +### 7.1.6 Intermodulation characteristics for NR SL-U + +The NR sidelink Intermodulation requirement is reused from LTE sidelink and hence different power level for the transmission power based on different bandwidth is used. For NR SL-U operation in unlicensed bands, the NR-U requirement can be reused. + +## 7.2 Rx requirements for inter-band con-current operation + +### 7.2.1 Reference sensitivity power level for inter-band con-current operation + +It has been agreed to + +reuse the existing CA\_n46-n78 MSD requirements of the power class 5 in the aggressor band n46 for MSD of the inter-band concurrent operation. + +reuse the existing delta Rib of CA\_n46-n78 for inter-band concurrent operation in Rel-18 + +### 7.2.2 Maximum input level for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +### 7.2.3 Adjacent Channel Selectivity for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +### 7.2.4 Blocking characteristics for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +### 7.2.5 Spurious response for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +### 7.2.6 Intermodulation characteristics for inter-band con-current operation + +It has been agreed to reuse NR uu and SL-U requirements for each band if an issue is not identified. + +## 7.3 Rx requirements for NR SL CA operation + +### 7.3.1 Reference sensitivity power level for NR SL CA operation + +For intra-band contiguous CA operation, the reference sensitivity requirement specified in Table 7.3E.2-1 in TS38.101-1 shall apply for each component carrier with all carriers active. The requirement is applied for each carrier reception when 2 carrier transmissions are activated at the same time. + +### 7.3.2 Maximum input level for NR SL CA operation + +For the RX RF requirements of NR SL CA UE, the following maximum input level requirements shall be applied to the SL CA bandwidth class B. + +**Table 7.3.2-1 Maximum input levels for NR SL CA UE** + +| Rx Parameter | Units | SL CA Bandwidth Class | | +|----------------------------------------------------------|-------|-----------------------|--------------------------------------------------------------------| +| | | A | B | +| Power in largest Transmission Bandwidth Configuration CC | dBm | | $-25 + 10\log_{10}(\text{BW}_{\text{Channel}}/20)^{\text{Note 1}}$ | +| | | | $-27 + 10\log_{10}(\text{BW}_{\text{Channel}}/20)^{\text{Note 2}}$ | + +NOTE 1: Reference measurement channel is A.7.2.x for 64 QAM. +NOTE 2: Reference measurement channel is A.7.2.x for 256 QAM. +NOTE 3: $10\log_{10}(x)$ is rounded to the nearest 0.5dB + +### 7.3.3 Adjacent Channel Selectivity for NR SL CA operation + +In NR V2X UE, RAN4 follows the NR ACS requirements $< 2700\text{MHz}$ for single carrier in n47 since to align with LTE V2X UE requirements. So RAN4 can reuse the principle as follows. + +For intra-band contiguous SL CA operation, the UE shall fulfil the minimum requirement specified in Table 7.3.3-1 to Table 7.3.3-3 where the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.7.2 in TS38.101-1. + +**Table 7.3.3-1 ACS for NR SL CA UE** + +| Rx Parameter | Units | SL CA bandwidth class | +|--------------|-------|-----------------------| +| | | B | +| ACS | dB | 20.0 | + +**Table 7.3.3-2 Test parameters for intra-band contiguous SL CA UE, case 1** + +| Rx Parameter | Units | SL CA bandwidth class | +|----------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------| +| | | B | +| Pw in Transmission Bandwidth Configuration, per CC | dBm | $P_{\text{REFSENS\_SL}} + 14 \text{ dB}$ | +| $P_{\text{Interferer}}$ | dBm | Aggregated power + 18.5 dB | +| $BW_{\text{Interferer}}$ | MHz | 10 | +| $F_{\text{Interferer}}$ (offset) | MHz | $5 + \text{Aggregated BW}_{\text{Channel}}/2$
/
$-(5 + \text{Aggregated BW}_{\text{Channel}}/2)$ | + +NOTE 1: The interferer is QPSK modulated PUSCH containing data and reference symbols. Normal cyclic prefix is used. +NOTE 2: The absolute value of the interferer offset $F_{\text{Interferer}}$ (offset) shall be further adjusted to MHz with SCS the sub-carrier spacing of the carrier closest to the interferer in MHz. The interferer is an NR signal with 15 kHz SCS. + +**Table 7.3.3-3 Test parameters for intra-band contiguous SL CA UE, case 2** + +| Rx Parameter | Units | SL CA Bandwidth Class | +|----------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------| +| | | B | +| Pw in Transmission Bandwidth Configuration, per CC | dBm | $-43.5 + 10\log(N_{RB,c}/N_{RB,agg})$ | +| $P_{Interferer}$ | dBm | -25 | +| $BW_{Interferer}$ | MHz | 10 | +| $F_{Interferer}$ (offset) | MHz | $5 + \text{Aggregated BW}_{\text{Channel}}/2$
/
$-(5 + \text{Aggregated BW}_{\text{Channel}}/2)$ | + +NOTE 1: The interferer is QPSK modulated PUSCH containing data and reference symbols. Normal cyclic prefix is used. + +NOTE 2: The absolute value of the interferer offset $F_{Interferer}$ (offset) shall be further adjusted to MHz with SCS the sub-carrier spacing of the carrier closest to the interferer in MHz. The interferer is an NR signal with 15 kHz SCS. + +## 7.3.4 Blocking characteristics for NR SL CA operation + +### 7.3.4.1 In-band blocking + +For intra-band contiguous SL CA operation, the UE shall fulfil the minimum requirement specified in Table 7.3.4.1-1 to Table 7.3.4.1-2 where the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.7.2 in TS38.101-1. + +**Table 7.3.4.1-1 In-band blocking parameters for intra-band contiguous SL CA UE** + +| Rx Parameter | Units | SL CA bandwidth class | +|----------------------------------------------------|-------|---------------------------------------------------------------------------------| +| | | B | +| Pw in Transmission Bandwidth Configuration, per CC | dBm | $P_{\text{REFSENS\_SL}} + \text{NR SL CA bandwidth class specific value below}$ | +| | dB | 16.0 | +| $BW_{Interferer}$ | MHz | 10 | +| $F_{\text{Ioffset, case 1}}$ | MHz | 15 | +| $F_{\text{Ioffset, case 2}}$ | MHz | 25 | + +NOTE 1: The interferer is QPSK modulated PUSCH containing data and reference symbols. Normal cyclic prefix is used. + +**Table 7.3.4.1-2 In-band blocking for intra-band contiguous SL CA UE** + +| NR SL CA band | Parameter | Unit | Case 1 | Case 2 | +|---------------|---------------------------|------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| | $P_{Interferer}$ | dBm | -44 | -44 | +| SL_n47B | $F_{Interferer}$ (offset) | MHz | $- BW_{\text{channel CA}}/2 - F_{\text{Ioffset, case 1}}$
&
$+ BW_{\text{channel CA}}/2 + F_{\text{Ioffset, case 1}}$ | $\leq - BW_{\text{channel CA}}/2 - F_{\text{Ioffset, case 2}}$
&
$\geq + BW_{\text{channel CA}}/2 + F_{\text{Ioffset, case 2}}$ | +| | $F_{Interferer}$ (Range) | MHz | NOTE 2 | $F_{\text{DL\_low}} - 30$
to
$F_{\text{DL\_high}} + 30$ | + +NOTE 1: For certain bands, the unwanted modulated interfering signal may not fall inside the UE receive band, but within the first 30 MHz below or above the UE receive band + +NOTE 2: For each carrier frequency the requirement is valid for two frequencies: +a. the carrier frequency - $BW_{\text{channel CA}}/2 - F_{\text{Ioffset, case 1}}$ and +b. the carrier frequency + $BW_{\text{channel CA}}/2 + F_{\text{Ioffset, case 1}}$ + +NOTE 3: $BW_{\text{channel CA}}$ denotes the aggregated channel bandwidth of the wanted signal + +### 7.3.4.2 Out-of-band blocking + +For intra-band contiguous SL CA operation, the UE throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.7.2 with parameters specified in Tables 7.3.4.2-1 and 7.3.4.2-2. + +For Table 7.3.4.2-2 in frequency range 1, 2 and 3, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.3.5 spurious response are applicable. + +**Table 7.3.4.2-1: Out-of-band blocking parameters for intra-band contiguous SL CA UE** + +| Rx Parameter | Units | SL CA Bandwidth Class | | | | | +|----------------------------------------------------|-------|------------------------------------------------------------------------------|--|--|--|--| +| | | B | | | | | +| Pw in Transmission Bandwidth Configuration, per CC | dBm | $P_{\text{REFSENS\_SL}} + \text{SL CA Bandwidth Class specific value below}$ | | | | | +| | | 9 | | | | | + +**Table 7.3.4.2-2: Out of band blocking for intra-band contiguous SL CA UE** + +| NR SL CA band | Parameter | Units | Frequency | | | +|---------------|------------------------------|-------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| | | | Range 1 | Range 2 | Range 3 | +| | $P_{\text{interferer}}$ | dBm | -44 | -30 | -15 | +| V2X_47B | $F_{\text{interferer}}$ (CW) | MHz | $-60 < f - F_{\text{DL\_low}} < -30$
or
$30 < f - F_{\text{DL\_high}} < 60$ | $-85 < f - F_{\text{DL\_low}} \leq -60$
or
$60 \leq f - F_{\text{DL\_high}} < 85$ | $1 \leq f \leq F_{\text{DL\_low}} - 85$
or
$F_{\text{DL\_high}} + 85 \leq f \leq 12750$ | + +NOTE 1: The power level of the interferer ( $P_{\text{interferer}}$ ) for Range 3 shall be modified to -20 dBm for $F_{\text{interferer}} > 6000$ MHz. +NOTE 2: The requirement is applied for multi-carrier intra-band con-current receptions when 2 carrier transmissions are activated at the same time. + +### 7.3.5 Spurious response for NR SL CA operation + +For intra-band contiguous SL CA operation, the UE throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.7.2 with parameters specified in Table 7.3.5-1 and Table 7.3.5-2. + +**Table 7.3.5-1: Spurious response parameters for intra-band contiguous SL CA UE** + +| Rx Parameter | Units | SL CA Bandwidth Class | | | | | +|----------------------------------------------------|-------|------------------------------------------------------------------------------|--|--|--|--| +| | | B | | | | | +| Pw in Transmission Bandwidth Configuration, per CC | dBm | $P_{\text{REFSENS\_SL}} + \text{SL CA Bandwidth Class specific value below}$ | | | | | +| | | 9 | | | | | + +NOTE 1: The requirement is applied for multi-carrier intra-band con-current receptions when 2 carrier transmissions are activated at the same time. +NOTE 2: Reference measurement channel is A.7.2 + +**Tables 7.3.5-2: Spurious response for intra-band contiguous SL CA UE** + +| Parameter | Unit | Level | +|-----------------------------------------------------------------------------------------------------------------------------------------------------|------|-------------------------------| +| $P_{\text{interferer}}$ (CW) | dBm | -44 | +| $F_{\text{interferer}}$ | MHz | Spurious response frequencies | +| NOTE 1: The requirement is applied for multi-carrier intra-band con-current receptions when 2 carrier transmissions are activated at the same time. | | | + +### 7.3.6 Intermodulation characteristics for NR SL CA operation + +For intra-band contiguous SL CA operation, the UE throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A.7.2 with parameters specified in Table 7.3.6-1 for the specified wanted signal mean power in the presence of two interfering signals. + +**Table 7.3.6-1: Wide band intermodulation for intra-band contiguous SL CA UE** + +| Rx parameter | Units | SL CA Bandwidth Class | | | | | +|----------------------------------------------------------------|-------|----------------------------------------------------------------------|--|--|--|--| +| | | B | | | | | +| P w in Transmission Bandwidth Configuration, per CC | dBm | P REFSENS_SL + SL CA Bandwidth Class specific value below | | | | | +| | | 9 | | | | | +| P Interferer 1 (CW) | dBm | -46 | | | | | +| P Interferer 2 (Modulated) | dBm | -46 | | | | | +| BW Interferer 2 | MHz | 10 | | | | | +| F Interferer 1 (Offset) | MHz | -F offset -15 | | | | | +| | | / | | | | | +| F Interferer 2 (Offset) | MHz | + F offset +15 | | | | | +| | | 2*F Interferer 1 | | | | | + +NOTE 1: The requirement is applied for multi-carrier intra-band concurrent receptions when 2 carrier transmissions are activated at the same time. + +NOTE 2: The FInterferer 1 (offset) is the frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the CW interferer and FInterferer 2 (offset) is the frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the modulated interferer. + +## 8 Co-channel coexistence between LTE Sidelink and NR Sidelink + +### 8.1 Configured transmitted power for V2X UE supporting co-channel coexistence with LTE SL + +For the measured configured maximum output power PUMAX,c for NR V2X sidelink transmissions non-concurrent with NR uplink transmissions, the same requirement as in clause 6.2.4 shall be applied. When NR V2X UE is configured to co-channel coexistence operation with LTE V2X and NR SCS is configured to 30kHz, the evaluation period for PUMAX,c for NR V2X sidelink is the first slot of NR SL slots overlapping with an LTE SL subframe. + +When NR V2X UE is configured to co-channel coexistence operation with LTE V2X and NR SCS is configured to 30kHz, the PCMAX,f,c tolerances in Table 6.2.4-1 are relaxed by 1dB i.e. T(PCMAX,f,c) = T(PCMAX,f,c) +1 (dB). + +### 8.2 Relative slot power tolerance for V2X UE supporting co-channel coexistence with LTE SL + +Relative slot power tolerance is defined for NR V2X supporting co-channel coexistence to ensure the RX performance of the LTE V2X UE operating within the same channel. This requirement applies only to transmissions with 30kHz SCS. + +The relative slot power tolerance for V2X UE supporting co-channel coexistence with LTE SL is the ability of the NR V2X UE operating with 30kHz SCS to control the output power of transmitted slots during PSCCH/PSSCH transmission consisting of two slots overlapping with an LTE SL subframe (500us). The reference slot is the 1st slot overlapping with LTE SL subframe and target slot is the subsequent NR SL slot overlapping with the LTE SL subframe. The measurement period is one NR SL slot with guard symbol omitted. + +The power of the target slot must not exceed the power of the reference slot by more than relative slot power tolerance of +1 dB. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38854/010f64870d9b7d9e04dc4059b1cf5f45_img.jpg b/marked/Rel-18/38_series/38854/010f64870d9b7d9e04dc4059b1cf5f45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcda336dd29814bf79655e5ef61bff31b013e8be --- /dev/null +++ b/marked/Rel-18/38_series/38854/010f64870d9b7d9e04dc4059b1cf5f45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c98e229c39aeb01af3691b08c377572261f9cf4643d94f803c9982a08f976cc7 +size 102033 diff --git a/marked/Rel-18/38_series/38854/03b9c04a0552e519e849210b8e2bf596_img.jpg b/marked/Rel-18/38_series/38854/03b9c04a0552e519e849210b8e2bf596_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6963f1386e1328322f5ecd61f0ad52967292aadd --- /dev/null +++ b/marked/Rel-18/38_series/38854/03b9c04a0552e519e849210b8e2bf596_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8072dea823c8ee01728b80544be89708860e2674d841a766657482515ec9e617 +size 65726 diff --git a/marked/Rel-18/38_series/38854/0577e933d8cc3e958649f0bc343fa804_img.jpg b/marked/Rel-18/38_series/38854/0577e933d8cc3e958649f0bc343fa804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3da0731dc1ad32299292d193ff20bd0e75e8a38 --- /dev/null +++ b/marked/Rel-18/38_series/38854/0577e933d8cc3e958649f0bc343fa804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3772d1aca61f5e708923d2b5f272730af4ca95a43c0e5fbfa59b74be82dd4595 +size 56764 diff --git a/marked/Rel-18/38_series/38854/068b3a3247570c4b78342a943f15de9e_img.jpg b/marked/Rel-18/38_series/38854/068b3a3247570c4b78342a943f15de9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c18627744db50b4ef92c9041e67ce0fb9d40ab0d --- /dev/null +++ b/marked/Rel-18/38_series/38854/068b3a3247570c4b78342a943f15de9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad3b4ef12b841b7f5d9ea074707eb2ca12f3114154e0ed2a08c0c93d5a9b534e +size 38327 diff --git a/marked/Rel-18/38_series/38854/0829927e13d750d95334585b41a1403d_img.jpg b/marked/Rel-18/38_series/38854/0829927e13d750d95334585b41a1403d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..668d84e976168e910511f9d9e2d32a04156cb159 --- /dev/null +++ b/marked/Rel-18/38_series/38854/0829927e13d750d95334585b41a1403d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0888f5e1d3c642fca7d97ff00aef44fc2c1a7bb1addb01c967e7ac0463411ed9 +size 57613 diff --git a/marked/Rel-18/38_series/38854/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-18/38_series/38854/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc3310b578dc579103e50787f5fd2c5a3e477783 --- /dev/null +++ b/marked/Rel-18/38_series/38854/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a21a6a8baada8f4602f3148fe1494557622cd3eba06120afd2293c94d2cc4bc +size 113875 diff --git a/marked/Rel-18/38_series/38854/09b5a76dd3d981abcc585df1314ef30a_img.jpg b/marked/Rel-18/38_series/38854/09b5a76dd3d981abcc585df1314ef30a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6be522b28598ceab18f2f913cc8f8d844f97c03c --- /dev/null +++ b/marked/Rel-18/38_series/38854/09b5a76dd3d981abcc585df1314ef30a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73de6bf2c76227ee6ad14f8c92ecb30c5e21edb5eb36aa5fd97fc2e13d5c3685 +size 35553 diff --git a/marked/Rel-18/38_series/38854/0a21b415410e479aa4b83cae918f6272_img.jpg b/marked/Rel-18/38_series/38854/0a21b415410e479aa4b83cae918f6272_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a5e39ba2d5c7bfed21c60117639fc09d8b082e5 --- /dev/null +++ b/marked/Rel-18/38_series/38854/0a21b415410e479aa4b83cae918f6272_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:287c17d294fe13224dbc910c790a3d967fd9ba8c63def9743e6d581ab9abac09 +size 30469 diff --git a/marked/Rel-18/38_series/38854/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-18/38_series/38854/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89849955a23e94f78c68c5648067618892a4b66a --- /dev/null +++ b/marked/Rel-18/38_series/38854/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48a222955d0d1812cf2e9830ac68a4e1e0be46697511d2478edc5550ed9166fd +size 39358 diff --git a/marked/Rel-18/38_series/38854/0e32ab25c356a3b09f57f8011afd5ac8_img.jpg b/marked/Rel-18/38_series/38854/0e32ab25c356a3b09f57f8011afd5ac8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7112726f267c449854dc7cec81cea240cab3f9e5 --- /dev/null +++ b/marked/Rel-18/38_series/38854/0e32ab25c356a3b09f57f8011afd5ac8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb5bda68f144ee9f07c5801f8fe571b605c373a77047b7d149618a15f7ee65b5 +size 66901 diff --git a/marked/Rel-18/38_series/38854/11e75fa5726229212e831adbab1c9890_img.jpg b/marked/Rel-18/38_series/38854/11e75fa5726229212e831adbab1c9890_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cda17f8e670b3854cc5b670485e8724196a9eb15 --- /dev/null +++ b/marked/Rel-18/38_series/38854/11e75fa5726229212e831adbab1c9890_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37d0190a75fcf693002f30b56e65aa8b00fef3ec3a542facc66d8f2b80175861 +size 53548 diff --git a/marked/Rel-18/38_series/38854/12b521317c2c8ea33a1382d83e2b76be_img.jpg b/marked/Rel-18/38_series/38854/12b521317c2c8ea33a1382d83e2b76be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b75f4a2986b3bf1f3178e7095777e4666f350e3 --- /dev/null +++ b/marked/Rel-18/38_series/38854/12b521317c2c8ea33a1382d83e2b76be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d501c8d5d2c0cf44bd12a9ae44be77692e55d2bf3656220bb39e509404156a9 +size 35030 diff --git a/marked/Rel-18/38_series/38854/16f235bb59e360d10bb35e523d3946b2_img.jpg b/marked/Rel-18/38_series/38854/16f235bb59e360d10bb35e523d3946b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54be17513749f607549c6b65deba6d077ab291dc --- /dev/null +++ b/marked/Rel-18/38_series/38854/16f235bb59e360d10bb35e523d3946b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e01df845802dc7addc4cc6665e5be4c25ad805b4fb1abdc3ccc7a65010bbb3e +size 35139 diff --git a/marked/Rel-18/38_series/38854/19a878abbd7068d98e7d54341c8d897c_img.jpg b/marked/Rel-18/38_series/38854/19a878abbd7068d98e7d54341c8d897c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cae7517fab887147d69bc73851ec630768d95eb9 --- /dev/null +++ b/marked/Rel-18/38_series/38854/19a878abbd7068d98e7d54341c8d897c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24eacdf28f0b137358e741293f96d690561d06155e0beddd0316c744a0d5fdab +size 43325 diff --git a/marked/Rel-18/38_series/38854/19e9097c72fbcb33376cec8aa00d3186_img.jpg b/marked/Rel-18/38_series/38854/19e9097c72fbcb33376cec8aa00d3186_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af36583abf97f855fb946a8314b6e131257f110e --- /dev/null +++ b/marked/Rel-18/38_series/38854/19e9097c72fbcb33376cec8aa00d3186_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70508ee1130bc391a0c4b5345b204a3f33d2c91ba745f0f6e9820cf36c4dd884 +size 32527 diff --git a/marked/Rel-18/38_series/38854/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-18/38_series/38854/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b16b7142ea92765fe4db18635c889153b4324b2f --- /dev/null +++ b/marked/Rel-18/38_series/38854/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0383ee991dc4d0bef8be1b86f7fb1a374104ec47ee3bad82f2c60b5d754cdd25 +size 152753 diff --git a/marked/Rel-18/38_series/38854/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-18/38_series/38854/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd2929fa7193e5a0396666fc112ad651189657fa --- /dev/null +++ b/marked/Rel-18/38_series/38854/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17b22045b78f2a55fba4e09c076f4e3cd508c1c0dd58d35be4088467dd0666af +size 17664 diff --git a/marked/Rel-18/38_series/38854/1da66f5fec34c001912c84a9abf145d7_img.jpg b/marked/Rel-18/38_series/38854/1da66f5fec34c001912c84a9abf145d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85bc621e7482c16d4e661f4b109cf8f0e6cd072c --- /dev/null +++ b/marked/Rel-18/38_series/38854/1da66f5fec34c001912c84a9abf145d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3420e4d102f967b2a276fbcf0d73b55e522575f13644aa2d883576dfe4230805 +size 80161 diff --git a/marked/Rel-18/38_series/38854/20938559c8eb02f499e31059759fea6d_img.jpg b/marked/Rel-18/38_series/38854/20938559c8eb02f499e31059759fea6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acaabaedc72ed0985d6dc4207c855195a2d73850 --- /dev/null +++ b/marked/Rel-18/38_series/38854/20938559c8eb02f499e31059759fea6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50f6cb2c7077245acbead2ee12ef3e877ec8ba85151f13c790043b58a968fdda +size 31234 diff --git a/marked/Rel-18/38_series/38854/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-18/38_series/38854/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6db2214e4603d31a2395dc6db8d7c225f6c04927 --- /dev/null +++ b/marked/Rel-18/38_series/38854/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e59a261b43e6a4957532fd57ff021a34ada169d2e2139f4704716ef14cf38f47 +size 114372 diff --git a/marked/Rel-18/38_series/38854/21282638f01b60bb72acf07272e24942_img.jpg b/marked/Rel-18/38_series/38854/21282638f01b60bb72acf07272e24942_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bafd59f865ec57f03409b724ce2bef42ac9c82c --- /dev/null +++ b/marked/Rel-18/38_series/38854/21282638f01b60bb72acf07272e24942_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d46868d6fed7c75f2650985fb18b80d053c2a46b04d32e67d1596e20cd8f0775 +size 54505 diff --git a/marked/Rel-18/38_series/38854/215e8d5e5ba38df215b55049d255b2ed_img.jpg b/marked/Rel-18/38_series/38854/215e8d5e5ba38df215b55049d255b2ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e69b64c9c30f33b78f142434bf0bb8190c369c47 --- /dev/null +++ b/marked/Rel-18/38_series/38854/215e8d5e5ba38df215b55049d255b2ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:660797176d861969853f9a6de4c405f2b3c182dbba88219bab2ce150c295bd4c +size 55513 diff --git a/marked/Rel-18/38_series/38854/2303c01c42eb5b45539e6b0324701ee1_img.jpg b/marked/Rel-18/38_series/38854/2303c01c42eb5b45539e6b0324701ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6fd6896fa69942b4c3c461f543c35da40dbd98f --- /dev/null +++ b/marked/Rel-18/38_series/38854/2303c01c42eb5b45539e6b0324701ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f25e1ee9770a7b9f5fd5e8a87f8bfcc29107b6f02c30acf395ab027912f0a7b8 +size 39280 diff --git a/marked/Rel-18/38_series/38854/24b08adae8325d6d47100c2949505f87_img.jpg b/marked/Rel-18/38_series/38854/24b08adae8325d6d47100c2949505f87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8194bd00fd185fd8aa70aa2095c4af9a197e661d --- /dev/null +++ b/marked/Rel-18/38_series/38854/24b08adae8325d6d47100c2949505f87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c434869ba7af8181c1993cec489586cfe2f119888b5ff49dbc18e75f41bb5df6 +size 39448 diff --git a/marked/Rel-18/38_series/38854/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/38_series/38854/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a76dc830e20652b1a01406882539914b93c0e69 --- /dev/null +++ b/marked/Rel-18/38_series/38854/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b2d7d38c2533eaea20a6d324b2b696125c717c364675021272bdc947ef9aacd +size 21722 diff --git a/marked/Rel-18/38_series/38854/28639a75145506e46966c11c1b995dd2_img.jpg b/marked/Rel-18/38_series/38854/28639a75145506e46966c11c1b995dd2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4f55a185083849d952d21dfa27ba7cf773bf3c0 --- /dev/null +++ b/marked/Rel-18/38_series/38854/28639a75145506e46966c11c1b995dd2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22d7bdbd61e50f7bb77c92c3dff04ea52bca41d84a614a87e4ecf34dd12032d0 +size 63203 diff --git a/marked/Rel-18/38_series/38854/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-18/38_series/38854/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e52b0a1b6a918eab8e487e562fc7016931eaecf8 --- /dev/null +++ b/marked/Rel-18/38_series/38854/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfabfd60f6265b1f213fc78ae7b30ed2d17d63cc20ffe507babca104e2e2f011 +size 43778 diff --git a/marked/Rel-18/38_series/38854/31c1877b2b8a3479b473e01d9856b689_img.jpg b/marked/Rel-18/38_series/38854/31c1877b2b8a3479b473e01d9856b689_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a164ad3f497a95a7f499f1bfc75163f4379f85b --- /dev/null +++ b/marked/Rel-18/38_series/38854/31c1877b2b8a3479b473e01d9856b689_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c05e56c5bd49cc7882667a1371e018f04484b07b0c8bca506f86ed617c668b83 +size 55288 diff --git a/marked/Rel-18/38_series/38854/33f2363ca24f377ba159c98c722f4746_img.jpg b/marked/Rel-18/38_series/38854/33f2363ca24f377ba159c98c722f4746_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c664f1a966299da19347eeaf6480bd12fd83407 --- /dev/null +++ b/marked/Rel-18/38_series/38854/33f2363ca24f377ba159c98c722f4746_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd92ee0bfe8615dba3ceef26afe69530764816e325588f6ab8c1ac6dad97ac8c +size 60671 diff --git a/marked/Rel-18/38_series/38854/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg b/marked/Rel-18/38_series/38854/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb5bfb15b133e3631bb647695a5ee06654eee7f6 --- /dev/null +++ b/marked/Rel-18/38_series/38854/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce8bc833d40b340adabb0b45e4eb2b5c1016cfc1e6390813f9d8954224ed18c3 +size 24296 diff --git a/marked/Rel-18/38_series/38854/375a2a2390ed2a98edcfe0dff7c82dd0_img.jpg b/marked/Rel-18/38_series/38854/375a2a2390ed2a98edcfe0dff7c82dd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15bdaa0611bed15153ddca1ad5f3ba95ce8d58b1 --- /dev/null +++ b/marked/Rel-18/38_series/38854/375a2a2390ed2a98edcfe0dff7c82dd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dcc62a897e1211b045a097236df73e540261233a463763c5f2dcacbcedfb23d +size 71117 diff --git a/marked/Rel-18/38_series/38854/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-18/38_series/38854/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ead6a5ad6b3c62f981b5cebbab7a150b2c1bd9 --- /dev/null +++ b/marked/Rel-18/38_series/38854/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1268489f1f068f4b025db9d3a84f37b0be260b9cd458ad9efd7f7f597eb7db7a +size 79762 diff --git a/marked/Rel-18/38_series/38854/3881b390d52f27a35faedfc170916c86_img.jpg b/marked/Rel-18/38_series/38854/3881b390d52f27a35faedfc170916c86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3184834032afab1ed4c4a2b7fe36cf74c3fefc7 --- /dev/null +++ b/marked/Rel-18/38_series/38854/3881b390d52f27a35faedfc170916c86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc53864ba1cccc1627a95b38a7bc68902741c0fadff01e1db42af23953149734 +size 50419 diff --git a/marked/Rel-18/38_series/38854/390120de4fe440c42fea8154fcaad334_img.jpg b/marked/Rel-18/38_series/38854/390120de4fe440c42fea8154fcaad334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0384b52849c0b8bdf9ab09c34bbac6c933420758 --- /dev/null +++ b/marked/Rel-18/38_series/38854/390120de4fe440c42fea8154fcaad334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b188f95f6516c6d1b8fd12682bd9831c73daeed1330fad3564886d68ebcd2bca +size 9593 diff --git a/marked/Rel-18/38_series/38854/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-18/38_series/38854/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13a8c6dcbd510c0dd863230ef030ebd3adc49536 --- /dev/null +++ b/marked/Rel-18/38_series/38854/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a98a7bc44b29cd0b3dcf20f857aed6cd3ab1b2896e328436a1bdff9efebbd91f +size 29792 diff --git a/marked/Rel-18/38_series/38854/396daa13ed7c232dff88770f1bf11cd7_img.jpg b/marked/Rel-18/38_series/38854/396daa13ed7c232dff88770f1bf11cd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ea52b6c57e85ccdf26bd7a15b388bf5797b6075 --- /dev/null +++ b/marked/Rel-18/38_series/38854/396daa13ed7c232dff88770f1bf11cd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9947901776eba87267b1d195ec2174a6d1d95e0174f20719966abc4a4ed26d7e +size 71027 diff --git a/marked/Rel-18/38_series/38854/3a1f7b7faea911108b9f2ec50c4dfffe_img.jpg b/marked/Rel-18/38_series/38854/3a1f7b7faea911108b9f2ec50c4dfffe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39e35f3146f1c0aad55d3380982139c045568596 --- /dev/null +++ b/marked/Rel-18/38_series/38854/3a1f7b7faea911108b9f2ec50c4dfffe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c49e3a35dd0d8b780911a513b77529af8622d772a46089cb48d00ba0395d708 +size 56877 diff --git a/marked/Rel-18/38_series/38854/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-18/38_series/38854/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfbf16c9d861f43d091c802e87df00d547aa1cd7 --- /dev/null +++ b/marked/Rel-18/38_series/38854/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8b945eee940d9fdae6c83bcce4d5b6e648b0eb1b6efaa8301ef0ef6f550559e +size 23183 diff --git a/marked/Rel-18/38_series/38854/3cde6c4c2ef7528574b0dbbc1b3e23aa_img.jpg b/marked/Rel-18/38_series/38854/3cde6c4c2ef7528574b0dbbc1b3e23aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7e474f904543d318a4850f891fb473671b0ef12 --- /dev/null +++ b/marked/Rel-18/38_series/38854/3cde6c4c2ef7528574b0dbbc1b3e23aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6046b5d39480ab39f77ce8acf3de82b9254bdc16d66511a4a1a39ab76d633e91 +size 28682 diff --git a/marked/Rel-18/38_series/38854/3d6f4088e319484d4e81fb68cd8520a3_img.jpg b/marked/Rel-18/38_series/38854/3d6f4088e319484d4e81fb68cd8520a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1902a6d8828e709af31baf1e3c2e887c26052c58 --- /dev/null +++ b/marked/Rel-18/38_series/38854/3d6f4088e319484d4e81fb68cd8520a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8f7554245b644bdc758b2558e2e206304dabae5dc38b62e464a5ebea8ec2e8e +size 58861 diff --git a/marked/Rel-18/38_series/38854/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-18/38_series/38854/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..322910ae62bf182dd167967ac75e985f91bc0603 --- /dev/null +++ b/marked/Rel-18/38_series/38854/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:743aa11caa9ea27e06400336b941cd9e4aa5dc320b4c6f75271c5349c8a5f432 +size 45426 diff --git a/marked/Rel-18/38_series/38854/4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg b/marked/Rel-18/38_series/38854/4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83806a624ba70a09667fb32187069467da558538 --- /dev/null +++ b/marked/Rel-18/38_series/38854/4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8988bb797ce537bfdc282eada15a435cbe17e5c335c8aa3373755d533f008bd0 +size 42156 diff --git a/marked/Rel-18/38_series/38854/426efb7efdc753a13f2fa16f7bff9429_img.jpg b/marked/Rel-18/38_series/38854/426efb7efdc753a13f2fa16f7bff9429_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b20411b49059149ac32d78fcd4bfc5aeadab76f --- /dev/null +++ b/marked/Rel-18/38_series/38854/426efb7efdc753a13f2fa16f7bff9429_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f32f2c08160de64a3fb26c394dc2e15411690dc73c18954e9288b3fdd5acce8 +size 38153 diff --git a/marked/Rel-18/38_series/38854/4310445b53967f25efe7be819014c8ae_img.jpg b/marked/Rel-18/38_series/38854/4310445b53967f25efe7be819014c8ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c8c486d578a70c5315584ae24719c670d62350c --- /dev/null +++ b/marked/Rel-18/38_series/38854/4310445b53967f25efe7be819014c8ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79533511e8f34c05b57c0e63dcc26f2656860b1af79a1412bcbbc094d4cb0418 +size 52917 diff --git a/marked/Rel-18/38_series/38854/4750bc46c043ee2e9d4524c36d9a54a1_img.jpg b/marked/Rel-18/38_series/38854/4750bc46c043ee2e9d4524c36d9a54a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da11afe5ea2d143fbf2089bd068ee288b53e0f2c --- /dev/null +++ b/marked/Rel-18/38_series/38854/4750bc46c043ee2e9d4524c36d9a54a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a42bda8cdac15d59bd76c89968ea55d7b03bda7f5cfe7f7d5c5b2e2c02ec614f +size 33460 diff --git a/marked/Rel-18/38_series/38854/48fc91e19c1a9b6674b120fbdd89b203_img.jpg b/marked/Rel-18/38_series/38854/48fc91e19c1a9b6674b120fbdd89b203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75270d494f5c075d795cb197c0012cf30ce00e95 --- /dev/null +++ b/marked/Rel-18/38_series/38854/48fc91e19c1a9b6674b120fbdd89b203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c2c1af4d93c268efe71e291d52d06d7ec42d089f9ee59faebeaf88aabef5829 +size 36470 diff --git a/marked/Rel-18/38_series/38854/4927d63a43414d4dece73d18f3869d7c_img.jpg b/marked/Rel-18/38_series/38854/4927d63a43414d4dece73d18f3869d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e246f60c0e4fa830174e060108176b604d740cbf --- /dev/null +++ b/marked/Rel-18/38_series/38854/4927d63a43414d4dece73d18f3869d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e465e32ecbb382d6c5e3ee6ec616536cd4adc5b1235156d5d757f7850057f62 +size 62318 diff --git a/marked/Rel-18/38_series/38854/4b0f6b9fffe1f9b12f0db27b76e617ca_img.jpg b/marked/Rel-18/38_series/38854/4b0f6b9fffe1f9b12f0db27b76e617ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..102482538bd224bc352e535d92318df6e0a2eddf --- /dev/null +++ b/marked/Rel-18/38_series/38854/4b0f6b9fffe1f9b12f0db27b76e617ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c8e19fa3a17bd98c00835358ba38f5e07071809c9c5035ff052ad6f6bff334a +size 52084 diff --git a/marked/Rel-18/38_series/38854/4bdefd2be27926822b4c23a83c1ea32c_img.jpg b/marked/Rel-18/38_series/38854/4bdefd2be27926822b4c23a83c1ea32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8582abb762eb6856245a6da19b2286e1ec26f872 --- /dev/null +++ b/marked/Rel-18/38_series/38854/4bdefd2be27926822b4c23a83c1ea32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88ba98fbadd43dd6cbee9dc5de2d3c094886d09948bc4e26056b2ab07038e41e +size 62116 diff --git a/marked/Rel-18/38_series/38854/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-18/38_series/38854/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4878bbc306beb61c5c6f92904e97ed026fa7507 --- /dev/null +++ b/marked/Rel-18/38_series/38854/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0855655029866a8fca52b65517760924b09bebc557edb402577d0979c981083a +size 95842 diff --git a/marked/Rel-18/38_series/38854/5011c5ead95d8bfb47fd0faa5158ff4f_img.jpg b/marked/Rel-18/38_series/38854/5011c5ead95d8bfb47fd0faa5158ff4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c3952cfb23ad03dadd27c1249cb05a8df34e463 --- /dev/null +++ b/marked/Rel-18/38_series/38854/5011c5ead95d8bfb47fd0faa5158ff4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85daaef7711153888eb7ff02deff4ddeabf5348e8f984cc9049ce5252a53e9b1 +size 58550 diff --git a/marked/Rel-18/38_series/38854/509a054727400bc6d424bb2a559b8cfc_img.jpg b/marked/Rel-18/38_series/38854/509a054727400bc6d424bb2a559b8cfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..126ef73c537f6415ddc7afa3b31f8c0a04631675 --- /dev/null +++ b/marked/Rel-18/38_series/38854/509a054727400bc6d424bb2a559b8cfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abd5e303c3a0b8d01b40eec431dfb54caa9c316254837033eb455740e88f9f6c +size 63630 diff --git a/marked/Rel-18/38_series/38854/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-18/38_series/38854/516d9f1866cc2e359a35fb1d8c046454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..122a19fbb18fc6fa1803586e4393aedda24bd369 --- /dev/null +++ b/marked/Rel-18/38_series/38854/516d9f1866cc2e359a35fb1d8c046454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6747be76e1ca8929f2443e689e1d1ebc12fcc8e0904236f24bbaa277be5d361 +size 123290 diff --git a/marked/Rel-18/38_series/38854/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38854/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a429c5e7b19269a5003df52e57777d644a12258 --- /dev/null +++ b/marked/Rel-18/38_series/38854/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cdeceb73c7310c74c829c688f8cb6c4517a15ef6033afa5c0ee63099a12d611 +size 53213 diff --git a/marked/Rel-18/38_series/38854/53f4e16be332aa0952e18cbb5259c31c_img.jpg b/marked/Rel-18/38_series/38854/53f4e16be332aa0952e18cbb5259c31c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b05dc20597ed2a374cee2d6a4446c5b104e5d2f2 --- /dev/null +++ b/marked/Rel-18/38_series/38854/53f4e16be332aa0952e18cbb5259c31c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf18277eb8b9e6af5c7996abe6e94c0064ef90bb4c4b271ffb40b3622d2255b6 +size 35075 diff --git a/marked/Rel-18/38_series/38854/57261b803cf2db0e8feca169cb2c416b_img.jpg b/marked/Rel-18/38_series/38854/57261b803cf2db0e8feca169cb2c416b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea7c5d2129594b4ead0eb23d9312aab9e80f6617 --- /dev/null +++ b/marked/Rel-18/38_series/38854/57261b803cf2db0e8feca169cb2c416b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32e8877f7f598c8e8c5813309324ca43297b04f29c1013be30bb5f39287b1648 +size 73868 diff --git a/marked/Rel-18/38_series/38854/578d2763eaf3edf3f1bd6657455ad54a_img.jpg b/marked/Rel-18/38_series/38854/578d2763eaf3edf3f1bd6657455ad54a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec71ccd66e89a3fcca01243fa14db7548fbcafcc --- /dev/null +++ b/marked/Rel-18/38_series/38854/578d2763eaf3edf3f1bd6657455ad54a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbf96b296de26fcfb96c89aaa07c6c874949f3f3d11d3b328837c1841f40555e +size 58472 diff --git a/marked/Rel-18/38_series/38854/5b2bbe84f2201cedd3fb338e43a0655c_img.jpg b/marked/Rel-18/38_series/38854/5b2bbe84f2201cedd3fb338e43a0655c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54949b2a49541a385b38c36f35b99db1c8bb16b9 --- /dev/null +++ b/marked/Rel-18/38_series/38854/5b2bbe84f2201cedd3fb338e43a0655c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29a790a80ee5dc3f37b068fc6ef9e18c35d10a4c80f2bc1cf5b0d58efdf84a20 +size 32077 diff --git a/marked/Rel-18/38_series/38854/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg b/marked/Rel-18/38_series/38854/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08c3980f994d1663d555ee313238defffdc8f1b2 --- /dev/null +++ b/marked/Rel-18/38_series/38854/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:965ec2f7d2f48ffee3361ac42ed0969255610e46160ec2594805739e70cb8f46 +size 69412 diff --git a/marked/Rel-18/38_series/38854/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg b/marked/Rel-18/38_series/38854/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bca37dfa41a1129dae6d63f233e2dba953c605ec --- /dev/null +++ b/marked/Rel-18/38_series/38854/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26df7e9ccd7df1d834771c33783c78001fb9a19764a4af32df7e1c1b8a5bf62e +size 67270 diff --git a/marked/Rel-18/38_series/38854/5e7b93195badf89e1fb645ae53d619bb_img.jpg b/marked/Rel-18/38_series/38854/5e7b93195badf89e1fb645ae53d619bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..819a7e520137bc41fdbd5fa203c1f720f0d171f6 --- /dev/null +++ b/marked/Rel-18/38_series/38854/5e7b93195badf89e1fb645ae53d619bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adc5dc3114eb3d7da66f9d50c30f95326f343a0b94074fdc3d3e89c678f80c6f +size 30064 diff --git a/marked/Rel-18/38_series/38854/5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg b/marked/Rel-18/38_series/38854/5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a25cff0ea942836d0a4f3a25333951567980f71 --- /dev/null +++ b/marked/Rel-18/38_series/38854/5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2276b73c8400642b3531f7f244f05d0220fbc60d7ac7423ecb15946120a7af65 +size 65322 diff --git a/marked/Rel-18/38_series/38854/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38854/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fccf0613771993cc8441e1190fdf133e635cb08c --- /dev/null +++ b/marked/Rel-18/38_series/38854/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a73354e61aefa8ec9aa9d1288c4436fe1898df6956588dc9bc1743f97aa44325 +size 5621 diff --git a/marked/Rel-18/38_series/38854/607a666ece1fb3bad30cbe1e61ea0cc6_img.jpg b/marked/Rel-18/38_series/38854/607a666ece1fb3bad30cbe1e61ea0cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1281045c58222fbaabba1aeedee0567fde552624 --- /dev/null +++ b/marked/Rel-18/38_series/38854/607a666ece1fb3bad30cbe1e61ea0cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bb963e7b40758f0f1bb52dce280d2656a33a9942b1b70f48bcbe6cf7187746c +size 60036 diff --git a/marked/Rel-18/38_series/38854/609dff0a56be2ded8c960a3672afa937_img.jpg b/marked/Rel-18/38_series/38854/609dff0a56be2ded8c960a3672afa937_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c94e3487afe7ee25c33bc61e4bebf4228c4448e --- /dev/null +++ b/marked/Rel-18/38_series/38854/609dff0a56be2ded8c960a3672afa937_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9687bdc4f8db998dc74cdbfe06ec61f4d3b392dbe580d70c1faa5d63af844506 +size 27722 diff --git a/marked/Rel-18/38_series/38854/6381dcd91bf4636842734ec95bbd75d4_img.jpg b/marked/Rel-18/38_series/38854/6381dcd91bf4636842734ec95bbd75d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..830bd0971a311f9772872ff4937999ef29f5735b --- /dev/null +++ b/marked/Rel-18/38_series/38854/6381dcd91bf4636842734ec95bbd75d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98adb41c2c082f30de6a312c9e326d2930b5b37fd72a2b4ac78a957239a11251 +size 68680 diff --git a/marked/Rel-18/38_series/38854/63c666b05041841b01fdef9fa4153ff7_img.jpg b/marked/Rel-18/38_series/38854/63c666b05041841b01fdef9fa4153ff7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3ba8372ade50b87b57d086e4c6f11507c88d360 --- /dev/null +++ b/marked/Rel-18/38_series/38854/63c666b05041841b01fdef9fa4153ff7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ee23af1c752a3a06514c3f2edfd5e366485ddbcd06aa4e3e614d6a03081648e +size 51911 diff --git a/marked/Rel-18/38_series/38854/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/Rel-18/38_series/38854/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f6c1a68f641208d2f28f37fddb0cba3459e7f7a --- /dev/null +++ b/marked/Rel-18/38_series/38854/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6e27154b5084464782dc08c0a741e1d763d6a1871b59e6f1b76090a12a2bf17 +size 25668 diff --git a/marked/Rel-18/38_series/38854/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg b/marked/Rel-18/38_series/38854/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..400d3112aab19dd16ccaa76c373feaa3f28f46d1 --- /dev/null +++ b/marked/Rel-18/38_series/38854/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f53a4b61939aac5ae86119dc964d59695ef1d991e8f4310fde697b1fedc7a1f4 +size 111188 diff --git a/marked/Rel-18/38_series/38854/6752cee124f693bc4cebc66180f4f91f_img.jpg b/marked/Rel-18/38_series/38854/6752cee124f693bc4cebc66180f4f91f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5226b3b34d155d993548f88c454910cfe34a54ac --- /dev/null +++ b/marked/Rel-18/38_series/38854/6752cee124f693bc4cebc66180f4f91f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d887c3044aa636469ee30adf1aa9a7976fd4cdf17f60d7b970871476bf1ee36d +size 45945 diff --git a/marked/Rel-18/38_series/38854/68d47da43cdd5782cac97f784b52c270_img.jpg b/marked/Rel-18/38_series/38854/68d47da43cdd5782cac97f784b52c270_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00c3423dc38586ddf2dc0c9a68e189168300e165 --- /dev/null +++ b/marked/Rel-18/38_series/38854/68d47da43cdd5782cac97f784b52c270_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c11b2a2f08a153830df9cfe9b1e2587e26df83fd4d53d1522739670cd88bbbba +size 57046 diff --git a/marked/Rel-18/38_series/38854/6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg b/marked/Rel-18/38_series/38854/6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb892f6a6a83d34de0470c682e07653393d4eeb --- /dev/null +++ b/marked/Rel-18/38_series/38854/6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95f84c9e5b8628d3a6415b3145ef4e0566a7b77dc52eb7995b96bc0364202449 +size 37424 diff --git a/marked/Rel-18/38_series/38854/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg b/marked/Rel-18/38_series/38854/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..791efbbe0048151a410fe8484732f1cf54c6394c --- /dev/null +++ b/marked/Rel-18/38_series/38854/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:094ab43345ce485e68c88de8e693c382c348e273903483db1d67ad5e074965c3 +size 23533 diff --git a/marked/Rel-18/38_series/38854/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-18/38_series/38854/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..209ff8876ffe1dd34e655b092b4846a0659e378a --- /dev/null +++ b/marked/Rel-18/38_series/38854/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38bdd9a8b757b234c9cf2a7081d12ab043bd36d3d252ec2e71eb0d47def5da37 +size 35219 diff --git a/marked/Rel-18/38_series/38854/70546cb98239089866510133c7fbc169_img.jpg b/marked/Rel-18/38_series/38854/70546cb98239089866510133c7fbc169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c78f43eb49f72c7bcf1570a089fc2c02731ce8 --- /dev/null +++ b/marked/Rel-18/38_series/38854/70546cb98239089866510133c7fbc169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ef9ed572f2f2bd4d1caf01d36d082f2625c907b4b9f5a239ca7d6230600a7ba +size 28109 diff --git a/marked/Rel-18/38_series/38854/72f8f68566ae1c43d361dd4b990b5631_img.jpg b/marked/Rel-18/38_series/38854/72f8f68566ae1c43d361dd4b990b5631_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51ddd7087e77eff01a7922200c1e212732541833 --- /dev/null +++ b/marked/Rel-18/38_series/38854/72f8f68566ae1c43d361dd4b990b5631_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38c558cda767c599cb43f31ed88c53abe74c4646827444d5b46fbf71ccb5ab62 +size 27435 diff --git a/marked/Rel-18/38_series/38854/730b6615db6d402580db1024a7f4e163_img.jpg b/marked/Rel-18/38_series/38854/730b6615db6d402580db1024a7f4e163_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42ed97254ab7434d4971d550ebaadf8a464a5f98 --- /dev/null +++ b/marked/Rel-18/38_series/38854/730b6615db6d402580db1024a7f4e163_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0186e491057ead8bcea740b595e455e87f8358222e90af4bc895141a53380fd8 +size 55412 diff --git a/marked/Rel-18/38_series/38854/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Rel-18/38_series/38854/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ea507bcae78fcace294edba5783e8f600852af0 --- /dev/null +++ b/marked/Rel-18/38_series/38854/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0b3ad6c9a8ae0fb58c02e1432e1be9ec187ac945186fff5d82181f1e1349b7c +size 27481 diff --git a/marked/Rel-18/38_series/38854/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-18/38_series/38854/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b67c01051bbfbf37604be366234fbdb075ef826b --- /dev/null +++ b/marked/Rel-18/38_series/38854/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0611c46c43b57854e582033141b22b50cf042b3f053dc1813530102b3179323f +size 45657 diff --git a/marked/Rel-18/38_series/38854/761bcf76a08d183518129d697fbeba5b_img.jpg b/marked/Rel-18/38_series/38854/761bcf76a08d183518129d697fbeba5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0382bfac1a29ea72890a302fac2d14e86c7404fd --- /dev/null +++ b/marked/Rel-18/38_series/38854/761bcf76a08d183518129d697fbeba5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7155a56c63ab6adcec854f4ae3bf02aed87679e5fb4293219c35932f687494a4 +size 29694 diff --git a/marked/Rel-18/38_series/38854/77a781dfb114c3e2b399f876f1808cfd_img.jpg b/marked/Rel-18/38_series/38854/77a781dfb114c3e2b399f876f1808cfd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..030307dc15a116c6faac8784ac66a64e7966d052 --- /dev/null +++ b/marked/Rel-18/38_series/38854/77a781dfb114c3e2b399f876f1808cfd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cc5f5945038f828f3e6e56469e3eb88775dfe66be9ddc13def36e59d3924559 +size 35005 diff --git a/marked/Rel-18/38_series/38854/7a0281fac8690d8894ef1cb92d1a7704_img.jpg b/marked/Rel-18/38_series/38854/7a0281fac8690d8894ef1cb92d1a7704_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c304b8394e7716fe81876c0a7d7e80ad7a658cd3 --- /dev/null +++ b/marked/Rel-18/38_series/38854/7a0281fac8690d8894ef1cb92d1a7704_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73aca02ec75ec21463cdd94fbee0ebc6b683b1e2d15daad3f90853b92616146b +size 28738 diff --git a/marked/Rel-18/38_series/38854/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/Rel-18/38_series/38854/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef300564c2db94ba35c963b8914a32d082f0e9ef --- /dev/null +++ b/marked/Rel-18/38_series/38854/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30d20dad79e7837ef082c3ad1e1b5e1354ddbb2c228d020382ca1293772c6dea +size 30912 diff --git a/marked/Rel-18/38_series/38854/7b96fce298a23fd76a01ff6c176c1059_img.jpg b/marked/Rel-18/38_series/38854/7b96fce298a23fd76a01ff6c176c1059_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea7d46ab0f1f492dc6d2a55f0d791bf68ca64665 --- /dev/null +++ b/marked/Rel-18/38_series/38854/7b96fce298a23fd76a01ff6c176c1059_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1d519deed4f98a3b4cabc70b353f8ec4e6561e5a4b5189a92fbbe91ca067ed7 +size 78819 diff --git a/marked/Rel-18/38_series/38854/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38854/7c0a9511fa02b6c2c125ff5be465186e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e2be10dfef003e10afe7b594d90418df31f4e2b --- /dev/null +++ b/marked/Rel-18/38_series/38854/7c0a9511fa02b6c2c125ff5be465186e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb12efbd49776fbdd1831993a1359e7fd7afde92fba1de6ea2d55eda6a95fa79 +size 77837 diff --git a/marked/Rel-18/38_series/38854/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-18/38_series/38854/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a96b86142b822805655ff48a9eafa13dcc59956 --- /dev/null +++ b/marked/Rel-18/38_series/38854/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ed2090e8ebb134e1083251b53858a1836fdd5c11e36590e29c39e95549a49b6 +size 43159 diff --git a/marked/Rel-18/38_series/38854/7cc979afbbf5fb1dedf0ddcbcf0044b7_img.jpg b/marked/Rel-18/38_series/38854/7cc979afbbf5fb1dedf0ddcbcf0044b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e21b605cbdbc8748247213a0794408c0ed6f001 --- /dev/null +++ b/marked/Rel-18/38_series/38854/7cc979afbbf5fb1dedf0ddcbcf0044b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17c150e4832735741863113ca0f9c2e52c820ebee72ac3cc6b60c2b5641ad4cd +size 55657 diff --git a/marked/Rel-18/38_series/38854/7d4b12c72fdecde31d1c594d7ce11eee_img.jpg b/marked/Rel-18/38_series/38854/7d4b12c72fdecde31d1c594d7ce11eee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77436c4272230058650943da814d05804525e3d9 --- /dev/null +++ b/marked/Rel-18/38_series/38854/7d4b12c72fdecde31d1c594d7ce11eee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b1498247afab7015beeb7154f5189108dc5f8a0bc4e783a0478bd790f0424e4 +size 60995 diff --git a/marked/Rel-18/38_series/38854/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-18/38_series/38854/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43c849290d31e22bfef802cdce06b9da59727acc --- /dev/null +++ b/marked/Rel-18/38_series/38854/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3775d05d0f511b2548e2d012e2db78dd793cdc1f9ae8276edb30f361e617daa1 +size 23316 diff --git a/marked/Rel-18/38_series/38854/8026dfc35d27b22be0b88bb64d835759_img.jpg b/marked/Rel-18/38_series/38854/8026dfc35d27b22be0b88bb64d835759_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..813516dd039d39664d1a079a8353f00375fff4e8 --- /dev/null +++ b/marked/Rel-18/38_series/38854/8026dfc35d27b22be0b88bb64d835759_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd449ce58c05c3de0f8bcc3abdcdc460e7d68f719282d7df3e239dc2bc278d61 +size 32767 diff --git a/marked/Rel-18/38_series/38854/835ebc0e9ec15eea8eadc15448249226_img.jpg b/marked/Rel-18/38_series/38854/835ebc0e9ec15eea8eadc15448249226_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8cfdcec7099c01384b635bce4c255706c9e7ad1 --- /dev/null +++ b/marked/Rel-18/38_series/38854/835ebc0e9ec15eea8eadc15448249226_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26309acf8493b8bb7aec521df50fa45eb0c85f4135cadf492cf123ce4796650d +size 70214 diff --git a/marked/Rel-18/38_series/38854/856421a17b9d40f97b994ca38151fb9a_img.jpg b/marked/Rel-18/38_series/38854/856421a17b9d40f97b994ca38151fb9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8702292c4e248d04f98b6f2a55787936ffc87fc5 --- /dev/null +++ b/marked/Rel-18/38_series/38854/856421a17b9d40f97b994ca38151fb9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:651d928de2ce3a40c829f5a12ee438182cc9a3d2bbdd100a766ec3bb491b75ff +size 35380 diff --git a/marked/Rel-18/38_series/38854/85b10db535b22e64c7d37f362705ddbf_img.jpg b/marked/Rel-18/38_series/38854/85b10db535b22e64c7d37f362705ddbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b730c9fdde580af789900f136b680b58fefdd8f9 --- /dev/null +++ b/marked/Rel-18/38_series/38854/85b10db535b22e64c7d37f362705ddbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fbc9ff45a4e23d5359a805fadeb24b9f23614866832a839b6fe5a988621f6da +size 34419 diff --git a/marked/Rel-18/38_series/38854/86c32700ca76b0bc4154f5d9e07aab0e_img.jpg b/marked/Rel-18/38_series/38854/86c32700ca76b0bc4154f5d9e07aab0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c8b70bd93d42bed5ab23d49194675c5ca433421 --- /dev/null +++ b/marked/Rel-18/38_series/38854/86c32700ca76b0bc4154f5d9e07aab0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb127484934139df86fb5092cb13abecd6b6146d6b4636019c5c739fb32ca38 +size 73896 diff --git a/marked/Rel-18/38_series/38854/89d2e4c002294cf6ffee801e84670cc5_img.jpg b/marked/Rel-18/38_series/38854/89d2e4c002294cf6ffee801e84670cc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbaf72dd0f6b4efec7fcede230d030e111bad19b --- /dev/null +++ b/marked/Rel-18/38_series/38854/89d2e4c002294cf6ffee801e84670cc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5fb064c549930fab927163c416906f3e6b13f1b16e428d88b30f7e34d343854 +size 90508 diff --git a/marked/Rel-18/38_series/38854/8a4275b35551f2ec9825a1aa442c0db1_img.jpg b/marked/Rel-18/38_series/38854/8a4275b35551f2ec9825a1aa442c0db1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10bc24d2d0dcd9ae0a17d9eeb5848470e4962815 --- /dev/null +++ b/marked/Rel-18/38_series/38854/8a4275b35551f2ec9825a1aa442c0db1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:544ca9581f8d1986ad7709f2f3a1d5993b8881a42edcd28ea2ab1db9d5565b07 +size 42244 diff --git a/marked/Rel-18/38_series/38854/8e21461e0c9384ec60322bedb1b1ab17_img.jpg b/marked/Rel-18/38_series/38854/8e21461e0c9384ec60322bedb1b1ab17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d394a724b0b3e8bcc7d0606721e06b37c33be28 --- /dev/null +++ b/marked/Rel-18/38_series/38854/8e21461e0c9384ec60322bedb1b1ab17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e50cd8b7ac97e48873faca0d7f8d7622fda534d641999dac369d7c2b20622cf2 +size 52485 diff --git a/marked/Rel-18/38_series/38854/8e6c3e68ec4b938b0f85a21c61d226df_img.jpg b/marked/Rel-18/38_series/38854/8e6c3e68ec4b938b0f85a21c61d226df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc8c5b9315da9bd2be59364e95ebe9bfc37c524f --- /dev/null +++ b/marked/Rel-18/38_series/38854/8e6c3e68ec4b938b0f85a21c61d226df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03bb7691a683ec8e198a8f11780627c8ca2c151415e565323577387b0daa4224 +size 51415 diff --git a/marked/Rel-18/38_series/38854/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg b/marked/Rel-18/38_series/38854/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a5e659ec03ab8056bb6b4ff3fa109790100b5b9 --- /dev/null +++ b/marked/Rel-18/38_series/38854/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6f4b641eeec2b8db41c3068329ea563c135e165efed20137fbbabade5e1cd76 +size 42608 diff --git a/marked/Rel-18/38_series/38854/8f7b458d3cc18ca96924473839d68ae6_img.jpg b/marked/Rel-18/38_series/38854/8f7b458d3cc18ca96924473839d68ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50358d95ccfe740c7bdd362249a1ddfdcf01f5fb --- /dev/null +++ b/marked/Rel-18/38_series/38854/8f7b458d3cc18ca96924473839d68ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fbb93af40407e99b1c201c327ddfd27a031f3b541ed799be6f55c095794e6d7 +size 44183 diff --git a/marked/Rel-18/38_series/38854/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg b/marked/Rel-18/38_series/38854/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2685dd21b2132b209e7aad9abf369873f2af5fe4 --- /dev/null +++ b/marked/Rel-18/38_series/38854/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70cc83a5b2ba738b7f942b4700e10bb47f9b16a4e82e13eb62a9f6f1f79ec1b8 +size 55628 diff --git a/marked/Rel-18/38_series/38854/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/Rel-18/38_series/38854/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7acf92541822cf70933198cd558a7775feb6104c --- /dev/null +++ b/marked/Rel-18/38_series/38854/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:225435e7e73d179580353052becd07f88fa07c68ed618b034ea8d30bb0310e16 +size 21002 diff --git a/marked/Rel-18/38_series/38854/968957e79781017e2926107f764b6042_img.jpg b/marked/Rel-18/38_series/38854/968957e79781017e2926107f764b6042_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eacb9f199d3eb5a9463d8db656f5fdfe7ad59fc2 --- /dev/null +++ b/marked/Rel-18/38_series/38854/968957e79781017e2926107f764b6042_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fb9bc548d4ccbbee4f5ef487ecec3dffa8b5297ba5ea2de1278cab2ffc6ac8f +size 38660 diff --git a/marked/Rel-18/38_series/38854/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-18/38_series/38854/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1abfdd46625073578cfe37b60314e3e9fe9511b --- /dev/null +++ b/marked/Rel-18/38_series/38854/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cd89e2aab68f8b1331a8b355fd943580951a3ee37d7598e9c24c847bf9a9509 +size 46965 diff --git a/marked/Rel-18/38_series/38854/993d36ea4a6a2610f938b1fb97e7c34a_img.jpg b/marked/Rel-18/38_series/38854/993d36ea4a6a2610f938b1fb97e7c34a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5a126a4d02d5f5657249cf18ff5c37cf64d4512 --- /dev/null +++ b/marked/Rel-18/38_series/38854/993d36ea4a6a2610f938b1fb97e7c34a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fc5cc7639aa734beba6195e24926934169351a1781020517ea378e4418fff99 +size 27896 diff --git a/marked/Rel-18/38_series/38854/99b769aeac0b78472f4cb81be7836f3b_img.jpg b/marked/Rel-18/38_series/38854/99b769aeac0b78472f4cb81be7836f3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d61bad0538143932bff73d39267d79218df6b99 --- /dev/null +++ b/marked/Rel-18/38_series/38854/99b769aeac0b78472f4cb81be7836f3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b430fe3bb39f4b5b3cf16d61bfffeee97e51461e364a40c567152ebc92b78bfe +size 32805 diff --git a/marked/Rel-18/38_series/38854/9b00c87003f634db9c30ca1d94fd932d_img.jpg b/marked/Rel-18/38_series/38854/9b00c87003f634db9c30ca1d94fd932d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30679f8d30275f4288b1e193e52136d767a0d436 --- /dev/null +++ b/marked/Rel-18/38_series/38854/9b00c87003f634db9c30ca1d94fd932d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb28bce22330878c88f67b82c06e5cd8d898366d8321780e09e374f92252d273 +size 64348 diff --git a/marked/Rel-18/38_series/38854/9c888dd6588358989047de6ced8b2bdb_img.jpg b/marked/Rel-18/38_series/38854/9c888dd6588358989047de6ced8b2bdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b90462aef1ccbc7dc1485f2a2ea58fbaf27ab7d --- /dev/null +++ b/marked/Rel-18/38_series/38854/9c888dd6588358989047de6ced8b2bdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88a077e210cc7905d2c7d53d9f74a8a49cffb15b9aee0a6fa159bcbe1ad2fa29 +size 52628 diff --git a/marked/Rel-18/38_series/38854/9e4179ffe4701bec67534299c4935049_img.jpg b/marked/Rel-18/38_series/38854/9e4179ffe4701bec67534299c4935049_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..878bfa13943d53f2e307685c7cd9b4137844173a --- /dev/null +++ b/marked/Rel-18/38_series/38854/9e4179ffe4701bec67534299c4935049_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba4641e989c61b78339f1ecb3f01c32caba63839628d3f5c273016a759e98c08 +size 29159 diff --git a/marked/Rel-18/38_series/38854/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg b/marked/Rel-18/38_series/38854/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20cccef26bd6d165b7af618cd0706cebaaa735e6 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5048b869ceb049d8de0dbf042b23b35c36e6312e5a8efcef59290b198c3d6032 +size 34763 diff --git a/marked/Rel-18/38_series/38854/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-18/38_series/38854/a289b64f80c6df506c0c55d553fc4496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4736c16f92db2ca34909cdcb30acb23f8c518b1 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a289b64f80c6df506c0c55d553fc4496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a69a76ccf875e235f6a2239b684d072c2421c91df25b46e4c56c95416a2c9f80 +size 65884 diff --git a/marked/Rel-18/38_series/38854/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-18/38_series/38854/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40f45f977617348c75c6aa0e23823fb4905cea74 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab41a60564e34cb50060611b8cbfd0992704c0f07b769e01c2fe320fff05421e +size 19289 diff --git a/marked/Rel-18/38_series/38854/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38854/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6ebb82e8fc93515b9a9ed621d454600e6c1f728 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a7d78aed9cbcb2d1111460750ae0c95c11d4b1b199b29e5798711e27d29e133 +size 32146 diff --git a/marked/Rel-18/38_series/38854/a346e19f92f1699e3f96432c0464c957_img.jpg b/marked/Rel-18/38_series/38854/a346e19f92f1699e3f96432c0464c957_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b48995ea0d82bb4fad7bee677acc895c779351e3 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a346e19f92f1699e3f96432c0464c957_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91f492ef82275b3fa4f405a8ac9c5bc106059ca4f221ae16a5849a503808ad03 +size 62838 diff --git a/marked/Rel-18/38_series/38854/a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg b/marked/Rel-18/38_series/38854/a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a97c0a1611c589f28c0adadd9afba978afeb7f65 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e49e2cdff462173a7e8b38530b9cc41c48a7b4fbb7d99b9ab831ae851bef73a +size 74204 diff --git a/marked/Rel-18/38_series/38854/a7e667227af01b0bd7f81d42ebae5c07_img.jpg b/marked/Rel-18/38_series/38854/a7e667227af01b0bd7f81d42ebae5c07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e49ac2468dc2344b39c2a6a14f59b884f3a5f00d --- /dev/null +++ b/marked/Rel-18/38_series/38854/a7e667227af01b0bd7f81d42ebae5c07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e83b0014ca2bc83daaac2a849e175aba08480353ddd91eb1fb3b4c393d70ae6 +size 34077 diff --git a/marked/Rel-18/38_series/38854/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-18/38_series/38854/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c83f4ee96fc171661378b1462505a004966ff62e --- /dev/null +++ b/marked/Rel-18/38_series/38854/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e93d142f948e6bdf2a89f4daf33f77b48d62eac48f87cd4ed69daade606bdef +size 38019 diff --git a/marked/Rel-18/38_series/38854/a96c7e19f53f2350db97a90738a6fb51_img.jpg b/marked/Rel-18/38_series/38854/a96c7e19f53f2350db97a90738a6fb51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ab1cbc89c06267997ea89a29293151c7170dcd2 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a96c7e19f53f2350db97a90738a6fb51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4061aeccee2877aaec73aeae1e9a6916da38b48c6fb5561202dd7c58a6685487 +size 42327 diff --git a/marked/Rel-18/38_series/38854/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg b/marked/Rel-18/38_series/38854/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8c77f4962d1a5ea9d4fdc85a8b9df4d658dd629 --- /dev/null +++ b/marked/Rel-18/38_series/38854/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e314a62a697a84c7b79cc9ea51476123c75b726f8bb11d84b9ec469ebae3bc7 +size 46208 diff --git a/marked/Rel-18/38_series/38854/b07036873d6afa06a24ea45f9f323810_img.jpg b/marked/Rel-18/38_series/38854/b07036873d6afa06a24ea45f9f323810_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff03b9ed3edba39a838d9d639dd3d2de576ad951 --- /dev/null +++ b/marked/Rel-18/38_series/38854/b07036873d6afa06a24ea45f9f323810_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a669781843b7ea53320b331505d3416bf34a7a2c0a9d4ac8091a4fb8e9b83195 +size 57701 diff --git a/marked/Rel-18/38_series/38854/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg b/marked/Rel-18/38_series/38854/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3eaf828cc5a0621e528f1fcd74e0d47d0e2eeff --- /dev/null +++ b/marked/Rel-18/38_series/38854/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bbb09f1c8c8a6b2d65f8a6663daa5eae5784b39131def84f6938e6299a418b9 +size 41756 diff --git a/marked/Rel-18/38_series/38854/b48758ac44730c1eba0b83ec3429e063_img.jpg b/marked/Rel-18/38_series/38854/b48758ac44730c1eba0b83ec3429e063_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f8209f793be880ac035a45e997798b873868f29 --- /dev/null +++ b/marked/Rel-18/38_series/38854/b48758ac44730c1eba0b83ec3429e063_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a87f6ff07fe7f49206df18ad00ac813461c0a12f233d3303efed71598feab60b +size 43518 diff --git a/marked/Rel-18/38_series/38854/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg b/marked/Rel-18/38_series/38854/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..877f60884138e3cd388a68f3b1a1a2a9ac22884c --- /dev/null +++ b/marked/Rel-18/38_series/38854/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aca12fe97e54b76153e8816281ffb89b7c77ad42a7cf2571f881dd027e1bf1f2 +size 54910 diff --git a/marked/Rel-18/38_series/38854/b5cf6e10fd65716d44c985f7c90ae2cb_img.jpg b/marked/Rel-18/38_series/38854/b5cf6e10fd65716d44c985f7c90ae2cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdd9fb5e8228274186e40ff65d9d2f9fab97bd12 --- /dev/null +++ b/marked/Rel-18/38_series/38854/b5cf6e10fd65716d44c985f7c90ae2cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c59be20687fdf5370dda112d31beeef51bfa96e0411c9df51744f0745c6a0a7 +size 50653 diff --git a/marked/Rel-18/38_series/38854/b71190d39f5e641548d0f091e94e663d_img.jpg b/marked/Rel-18/38_series/38854/b71190d39f5e641548d0f091e94e663d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..451654ce3ba8979a10d32bcea36ab839def7fa54 --- /dev/null +++ b/marked/Rel-18/38_series/38854/b71190d39f5e641548d0f091e94e663d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b79d3ebc6044bb233df268850626c088dbadd76a8e845a763f9e8dca85adc631 +size 52429 diff --git a/marked/Rel-18/38_series/38854/b7197f070e527f304350831936352031_img.jpg b/marked/Rel-18/38_series/38854/b7197f070e527f304350831936352031_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec7306fbcdebba1b9ce2d0482a01b8199d4c425a --- /dev/null +++ b/marked/Rel-18/38_series/38854/b7197f070e527f304350831936352031_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99603bef7d9b0b94e76bcd6161d74ec214fd2a5e1f34bb92a95634a28b23ecf8 +size 81616 diff --git a/marked/Rel-18/38_series/38854/b7b9fb0d8504e5e0dc06d2f930fc2444_img.jpg b/marked/Rel-18/38_series/38854/b7b9fb0d8504e5e0dc06d2f930fc2444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68004cc3d73cdd2158d9b5b38eb593cb3edb1b4c --- /dev/null +++ b/marked/Rel-18/38_series/38854/b7b9fb0d8504e5e0dc06d2f930fc2444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d45ca0b824dd17cfdcc6c6ce994f92f654573349dcf3b99846473d4e80c091d +size 50857 diff --git a/marked/Rel-18/38_series/38854/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg b/marked/Rel-18/38_series/38854/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64909891a4502ca12dc334010070b6f23e38ce69 --- /dev/null +++ b/marked/Rel-18/38_series/38854/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d6ac88f775671b7ca036acf4b1a3d8985445455103b98746c37a3c940a8b89c +size 66368 diff --git a/marked/Rel-18/38_series/38854/be2d9105109f6a87907ab68cb88548d9_img.jpg b/marked/Rel-18/38_series/38854/be2d9105109f6a87907ab68cb88548d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07fe457296f7be32d8813e68dcd73cd791890f40 --- /dev/null +++ b/marked/Rel-18/38_series/38854/be2d9105109f6a87907ab68cb88548d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df87d79ae0b72013e8c0c2097d58296b142201b52f81ea9d06c1cddf34f47308 +size 30456 diff --git a/marked/Rel-18/38_series/38854/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-18/38_series/38854/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8099ca3fb279818bd126e115b891f09ade7bcc2a --- /dev/null +++ b/marked/Rel-18/38_series/38854/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:628c94cef33ddda33ee489cd343cc143a5881578b5eace2d99b8b79f74bfdaa5 +size 101728 diff --git a/marked/Rel-18/38_series/38854/c41f93a5e921782a4d8e7705f52f74b5_img.jpg b/marked/Rel-18/38_series/38854/c41f93a5e921782a4d8e7705f52f74b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bd572cf101e399289b95e8d45bae1253f5c2036 --- /dev/null +++ b/marked/Rel-18/38_series/38854/c41f93a5e921782a4d8e7705f52f74b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:849041c2b08a143bb97eab81d8e32adb5dd082af649f49762dad7ef3858e7728 +size 72146 diff --git a/marked/Rel-18/38_series/38854/c5424b117a719524c619938e97c4cb1f_img.jpg b/marked/Rel-18/38_series/38854/c5424b117a719524c619938e97c4cb1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3577d0fc995a4173c2b531e20f06026cc43dc65 --- /dev/null +++ b/marked/Rel-18/38_series/38854/c5424b117a719524c619938e97c4cb1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3049ced6fc9baebc3b009f065dd7e6a36f88726b34b99be413a06bd1841ddfbb +size 148542 diff --git a/marked/Rel-18/38_series/38854/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38854/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7324a5ba76c114334c220c4079aeaea27a8e29f --- /dev/null +++ b/marked/Rel-18/38_series/38854/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b88e5aeb7ba1a847e9843c2ecc11faa42b4f835877ad266fb09c578eb76b51b +size 35227 diff --git a/marked/Rel-18/38_series/38854/c742b64169a38a7f3f990172019878c8_img.jpg b/marked/Rel-18/38_series/38854/c742b64169a38a7f3f990172019878c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d51c45457824f2b8c469c15dffa73d5806fe9f7 --- /dev/null +++ b/marked/Rel-18/38_series/38854/c742b64169a38a7f3f990172019878c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0bbd3f45ddb011e5dbd2a6ca1c40a31f3876c4bb5246f00727c057f9419b073 +size 33100 diff --git a/marked/Rel-18/38_series/38854/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg b/marked/Rel-18/38_series/38854/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d2a8a9c3cfca339ba0a614039210f22db7e9f07 --- /dev/null +++ b/marked/Rel-18/38_series/38854/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cbf93e2ca728765a212247828d5f169d83e249d63ba4842be46b56f0697ff77 +size 83406 diff --git a/marked/Rel-18/38_series/38854/cc12ad6eea1541843baea43ae833b856_img.jpg b/marked/Rel-18/38_series/38854/cc12ad6eea1541843baea43ae833b856_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b6d8534eb5aaf591f0d49f630070b6661860270 --- /dev/null +++ b/marked/Rel-18/38_series/38854/cc12ad6eea1541843baea43ae833b856_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75f42f30ef8c422ac1a335a9e70935d077c7dac119dc437d5d1c8e37c8eff5fd +size 27304 diff --git a/marked/Rel-18/38_series/38854/cfc852835f2d91bea8dc074568937e22_img.jpg b/marked/Rel-18/38_series/38854/cfc852835f2d91bea8dc074568937e22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c6a2cda375288ef3b85f8e5bddd8e48cbcc5a29 --- /dev/null +++ b/marked/Rel-18/38_series/38854/cfc852835f2d91bea8dc074568937e22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd55e7c4c87d528c43d60c74a48ec1a8b95d2c065f5f842ea91e46d9a761c7e3 +size 104133 diff --git a/marked/Rel-18/38_series/38854/d0c2bd517f31d89b01136a1847bcdf33_img.jpg b/marked/Rel-18/38_series/38854/d0c2bd517f31d89b01136a1847bcdf33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87990de2a6f0015a669dc779d8cf4d511ae1b426 --- /dev/null +++ b/marked/Rel-18/38_series/38854/d0c2bd517f31d89b01136a1847bcdf33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:991087451c8b7a172fa4ad562d8a67ce9ee8c11d33386e4bf1b88433afc34ff2 +size 26589 diff --git a/marked/Rel-18/38_series/38854/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-18/38_series/38854/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fb168980667bc9d79c4d229a5c5f27a1933cf19 --- /dev/null +++ b/marked/Rel-18/38_series/38854/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:188ea2cf2b9adec27ba5dbd44f4ba7e2c8ceeb8177ca53973adad4d0f624f8fb +size 21904 diff --git a/marked/Rel-18/38_series/38854/d461c6341beba90844ef785469cd757f_img.jpg b/marked/Rel-18/38_series/38854/d461c6341beba90844ef785469cd757f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f58e9d96f9324f2836811f3065f4c28101f45d20 --- /dev/null +++ b/marked/Rel-18/38_series/38854/d461c6341beba90844ef785469cd757f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de7bf3fd33f186b356f5b5782ebea9a5f169a14510c68ae2ff16b7ff9515a907 +size 69581 diff --git a/marked/Rel-18/38_series/38854/d94a0100320109c1b9cd75c1054c7b95_img.jpg b/marked/Rel-18/38_series/38854/d94a0100320109c1b9cd75c1054c7b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3c2d541675134e96d11df081ce24e540ab622ed --- /dev/null +++ b/marked/Rel-18/38_series/38854/d94a0100320109c1b9cd75c1054c7b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4295aa734b95d0a5835716beb464a5e157f50587835228c1e4f38a24dc9a116d +size 70232 diff --git a/marked/Rel-18/38_series/38854/d989d8766a23d5e409031f1ceae6572b_img.jpg b/marked/Rel-18/38_series/38854/d989d8766a23d5e409031f1ceae6572b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c770c73548ac44e70749aa03676daad382e00ad1 --- /dev/null +++ b/marked/Rel-18/38_series/38854/d989d8766a23d5e409031f1ceae6572b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e9000466c3390abdec51be110bb3c284ccc6eeaccdb7f5da7647295dd6a7da2 +size 24299 diff --git a/marked/Rel-18/38_series/38854/ddfefccc6c2fcfadf4e398109548faf8_img.jpg b/marked/Rel-18/38_series/38854/ddfefccc6c2fcfadf4e398109548faf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b190754d411bcea0a112850ec85e5d679c40d7d8 --- /dev/null +++ b/marked/Rel-18/38_series/38854/ddfefccc6c2fcfadf4e398109548faf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d03fbe7b0d46f7968338eebb41398189e83e3269ee97c45cd63d2038f6d58068 +size 69397 diff --git a/marked/Rel-18/38_series/38854/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-18/38_series/38854/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99d299c20ac768c092b33f6cd23867ca1ca74c28 --- /dev/null +++ b/marked/Rel-18/38_series/38854/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56113e32986d47d2bbc524d8f555d8be5e47e5614272cb9de329c30244f5ed27 +size 29849 diff --git a/marked/Rel-18/38_series/38854/e046996962d6740cf050a5640e0c6b40_img.jpg b/marked/Rel-18/38_series/38854/e046996962d6740cf050a5640e0c6b40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f3ccc5f6f567d65450f14b7f1c8d158676900ed --- /dev/null +++ b/marked/Rel-18/38_series/38854/e046996962d6740cf050a5640e0c6b40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85ae22c1f6cbf308491cc954957b2d3919d76dfd0e7f48ffb6aedd5482c37215 +size 48232 diff --git a/marked/Rel-18/38_series/38854/e0740204d7aa33697c8f2d59c4cca51b_img.jpg b/marked/Rel-18/38_series/38854/e0740204d7aa33697c8f2d59c4cca51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9681677bd5146d89475decf80460e62ebc7922ba --- /dev/null +++ b/marked/Rel-18/38_series/38854/e0740204d7aa33697c8f2d59c4cca51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2363a8286dfead8821b4d9d76b53829b76e2f0f05487ffa48d3d1c62f5c77ed4 +size 59013 diff --git a/marked/Rel-18/38_series/38854/e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg b/marked/Rel-18/38_series/38854/e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2ff0a1529d9733a5d84404d61ba0fa275332708 --- /dev/null +++ b/marked/Rel-18/38_series/38854/e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0c37aa3286428c6ffdaee5a665ab6e270cb0fd3ec89e0b863d4c75f9ac6f58c +size 55695 diff --git a/marked/Rel-18/38_series/38854/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-18/38_series/38854/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca62b3b22064da5789e4eeffb7ca8bdab9e41ae8 --- /dev/null +++ b/marked/Rel-18/38_series/38854/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e8bceb77338dc8860de0a8212975cc9e7f616de481a994d2e7a2427ac585e9c +size 51723 diff --git a/marked/Rel-18/38_series/38854/e466e4c4fb08567a109bb959a765225c_img.jpg b/marked/Rel-18/38_series/38854/e466e4c4fb08567a109bb959a765225c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ee1a99d3074c2c77bdb468ac3d82ec690c6baf5 --- /dev/null +++ b/marked/Rel-18/38_series/38854/e466e4c4fb08567a109bb959a765225c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:225acbc1a34437d52c1be42fff43d47f61c294d4f94b06decc5fcffff5402c46 +size 31458 diff --git a/marked/Rel-18/38_series/38854/e91633da5160c8af51a4ace6d3347f53_img.jpg b/marked/Rel-18/38_series/38854/e91633da5160c8af51a4ace6d3347f53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b9b0c085595567101c0d41b532aded221653bb4 --- /dev/null +++ b/marked/Rel-18/38_series/38854/e91633da5160c8af51a4ace6d3347f53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cc838dc67faac772a688c35e0061b0232e94060e1d0eda17e86e876c0bd766f +size 54846 diff --git a/marked/Rel-18/38_series/38854/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-18/38_series/38854/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e4ba972c2559d6daae6d8031d0ab2236902ebb --- /dev/null +++ b/marked/Rel-18/38_series/38854/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f382258de64a5333f95e40f0be99f3f665d30adb63a0bb6e09b43e2e5097ebfe +size 29817 diff --git a/marked/Rel-18/38_series/38854/ead8d1841c351608343c98f30e5f3f07_img.jpg b/marked/Rel-18/38_series/38854/ead8d1841c351608343c98f30e5f3f07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9596f116b2ab9bb32d619886aa389a6dceb7be5f --- /dev/null +++ b/marked/Rel-18/38_series/38854/ead8d1841c351608343c98f30e5f3f07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:589c2bb18dffb272f9d67317e3ad7972339fc568e1b76573db5de9e71d8c499d +size 58910 diff --git a/marked/Rel-18/38_series/38854/ebb7b22e39bc5c9aab718fe98c50d90a_img.jpg b/marked/Rel-18/38_series/38854/ebb7b22e39bc5c9aab718fe98c50d90a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff0dc8af1029d801f9a5a0f96ac24d2d887573b6 --- /dev/null +++ b/marked/Rel-18/38_series/38854/ebb7b22e39bc5c9aab718fe98c50d90a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27f2de78eacc5193116099bd6f6a5ddeef093c9fe7fff6d975be64bf600c4cf0 +size 52809 diff --git a/marked/Rel-18/38_series/38854/ee8536b235eb6aad21e2048fd5308900_img.jpg b/marked/Rel-18/38_series/38854/ee8536b235eb6aad21e2048fd5308900_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b54618c1708d3188fe0a864abb5a34eafa1b3a05 --- /dev/null +++ b/marked/Rel-18/38_series/38854/ee8536b235eb6aad21e2048fd5308900_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9cd6ddfc5d260c7f2401744525b966447344c8070975f98d2199a4dadc50396 +size 33975 diff --git a/marked/Rel-18/38_series/38854/eec47775133f5c3b02d42ab8f85599ce_img.jpg b/marked/Rel-18/38_series/38854/eec47775133f5c3b02d42ab8f85599ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96de6a02adb97d4d901554eb80acb307defa9cf8 --- /dev/null +++ b/marked/Rel-18/38_series/38854/eec47775133f5c3b02d42ab8f85599ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dfa5ce7eedb75db66738b6e7b2a24b9f276cc8b1fccb4b5f97302ad620c8fd1 +size 61526 diff --git a/marked/Rel-18/38_series/38854/f22e617a7aef13de5ffd8e390bfda1c3_img.jpg b/marked/Rel-18/38_series/38854/f22e617a7aef13de5ffd8e390bfda1c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98e27b767229715db6244c736d0f3c89f441a0a1 --- /dev/null +++ b/marked/Rel-18/38_series/38854/f22e617a7aef13de5ffd8e390bfda1c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bc5e75f79071ca0705e856b74adcc4bb68e5c311f169ee0c03d5d350ea5afa4 +size 31352 diff --git a/marked/Rel-18/38_series/38854/f356ce635bbbc30c7b6db50ecdb5dab4_img.jpg b/marked/Rel-18/38_series/38854/f356ce635bbbc30c7b6db50ecdb5dab4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e0350252f26d2d4c08c7c2a9dd0da9ac045fb07 --- /dev/null +++ b/marked/Rel-18/38_series/38854/f356ce635bbbc30c7b6db50ecdb5dab4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94fc2fc7863429a02270ff5d72f399789510b280f3a93ebc453aa378b9c68458 +size 27779 diff --git a/marked/Rel-18/38_series/38854/f59dafee4c3bbc563111e5b1b6048c3d_img.jpg b/marked/Rel-18/38_series/38854/f59dafee4c3bbc563111e5b1b6048c3d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cb3ab0d5778ec90d5061aad0378c70b227fd303 --- /dev/null +++ b/marked/Rel-18/38_series/38854/f59dafee4c3bbc563111e5b1b6048c3d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:808b23450970617ea7989bb8262e0a346e4244b935fff44666284cd2911b0989 +size 45890 diff --git a/marked/Rel-18/38_series/38854/f618f0a44c7807c81c70cf7ec2e5e717_img.jpg b/marked/Rel-18/38_series/38854/f618f0a44c7807c81c70cf7ec2e5e717_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc8c9367346d64d467aeaa64375d793d32f1c63e --- /dev/null +++ b/marked/Rel-18/38_series/38854/f618f0a44c7807c81c70cf7ec2e5e717_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cfaa61e2f5039c800d3b833de558905c812dcae17cdaa5f05076054f74a717b +size 23886 diff --git a/marked/Rel-18/38_series/38854/f68421f5d184c116a7061977a9057e63_img.jpg b/marked/Rel-18/38_series/38854/f68421f5d184c116a7061977a9057e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20b55d59599fe10769e555c97609f7d6547be4e4 --- /dev/null +++ b/marked/Rel-18/38_series/38854/f68421f5d184c116a7061977a9057e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b7fb7c129e8c4138c2c7f9155a60cdd7002b3e6868b3afd5e66946516677c18 +size 80201 diff --git a/marked/Rel-18/38_series/38854/f88c98ece93f791a5eb0a524ccc85b54_img.jpg b/marked/Rel-18/38_series/38854/f88c98ece93f791a5eb0a524ccc85b54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1311bc71ff2db920d04569cf5238be09699628b --- /dev/null +++ b/marked/Rel-18/38_series/38854/f88c98ece93f791a5eb0a524ccc85b54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef01e40250ee9725bb0a9ef1c4f36c5aa2aab4ba27e5a5eb4057dc57d79ba866 +size 49699 diff --git a/marked/Rel-18/38_series/38854/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/38_series/38854/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d544cbbd27dda1a45738e28602c336f7e6037009 --- /dev/null +++ b/marked/Rel-18/38_series/38854/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d10a91d3b562f0fd62010fbe8f8cd27e3f8e3d079153ca91216f8e78f91140f6 +size 42304 diff --git a/marked/Rel-18/38_series/38854/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38854/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c8bc62e8071a23a47656f4a186a06b6228bce3f --- /dev/null +++ b/marked/Rel-18/38_series/38854/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0551c68a6742af015ffa96e326f8f592f3a5d361c81714e59794944b709259b +size 33916 diff --git a/marked/Rel-18/38_series/38854/ff3417b75213b8688e6504a21220b430_img.jpg b/marked/Rel-18/38_series/38854/ff3417b75213b8688e6504a21220b430_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00efaa9168a7fe5f1c7a4cfaa0779d0dae2e4b19 --- /dev/null +++ b/marked/Rel-18/38_series/38854/ff3417b75213b8688e6504a21220b430_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7de3c26bab497341720af770f7bcbfe633cc3cb8a738dbc7f0963bd88248a1e5 +size 13327 diff --git a/marked/Rel-18/38_series/38854/raw.md b/marked/Rel-18/38_series/38854/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a158d11966065a92b133609ec0633fba2476ae58 --- /dev/null +++ b/marked/Rel-18/38_series/38854/raw.md @@ -0,0 +1,4563 @@ + + +# 3GPP TR 38.854 V18.0.0 (2023-09) + +*Technical Report* + +**3rd Generation Partnership Project; +Technical Specification Group Radio Access Network; +NR;** + +**NR support for high speed train scenario in frequency range 2 +(FR2) +(Release 18)** + +![5G Advanced logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](390120de4fe440c42fea8154fcaad334_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms, symbols and abbreviations..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Introduction..... | 9 | +| 5 FR2 HST deployment scenario ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 HST scenario and RRH parameters ..... | 12 | +| 5.2.1 Unidirectional deployments..... | 12 | +| 5.2.2 Bidirectional deployment ..... | 14 | +| 5.2.3 RRH Parameters ..... | 17 | +| 5.3 Train roof-mounted high-power CPE parameters..... | 18 | +| 5.3.0 Introduction ..... | 18 | +| 5.3.1 Number of panels per CPE ..... | 18 | +| 5.3.2 Placement of CPE panel(s)..... | 19 | +| 5.3.3 Number of CPE devices ..... | 19 | +| 6 FR2 high speed feasibility evaluation..... | 19 | +| 6.1 Evaluation Parameters..... | 19 | +| 6.1.1 RRH antenna array parameters for evaluation ..... | 19 | +| 6.1.2 RRH antenna element parameters for evaluation..... | 20 | +| 6.1.3 CPE antenna array parameters for evaluation ..... | 20 | +| 6.1.4 CPE antenna element parameters for evaluation..... | 20 | +| 6.2 Channel model for FR2 HST ..... | 21 | +| 6.2.1 Pathloss model used for link budget evaluation..... | 21 | +| 6.2.2 Channel modelling for performance requirements ..... | 23 | +| 6.3 FR2 Feasibility Evaluation..... | 27 | +| 6.3.1 Idle/inactive mode ..... | 27 | +| 6.3.2 Connected mode ..... | 27 | +| 6.3.2.1 Number of Rx beams ..... | 27 | +| 6.3.2.1.1 Scenario-A..... | 28 | +| 6.3.2.1.2 Scenario-B ..... | 29 | +| 6.3.3 Link Performance and Throughput Performance ..... | 33 | +| 6.3.3.1 Link Performance Evaluation from Samsung..... | 33 | +| 6.3.3.1.1 Scenario-A, Uni-directional RRH Deployment ..... | 33 | +| 6.3.3.1.2 Scenario-A, Bi-directional RRH Deployment ..... | 35 | +| 6.3.3.1.3 Scenario-B, Uni-directional RRH Deployment ..... | 37 | +| 6.3.3.1.4 Scenario-B, Bi-directional RRH Deployment..... | 37 | +| 6.3.3.2 Link performance Evaluation from Huawei ..... | 37 | +| 6.3.3.2.1 Scenario A ..... | 37 | +| 6.3.3.2.1.1 Scenario A, Bi-directional ..... | 37 | +| 6.3.3.2.1.2 Scenario A, Uni-directional..... | 38 | +| 6.3.3.2.2 Scenario B ..... | 39 | +| 6.3.3.2.2.1 Scenario B, Bi-directional ..... | 40 | +| 6.3.3.2.2.2 Scenario B, Uni-directional..... | 43 | +| 6.3.3.3 Link level performance from Ericsson ..... | 44 | +| 6.3.3.3.1 Scenario-A, Uni-directional RRH Deployment ..... | 44 | +| 6.3.3.3.2 Scenario-A, Bi-directional RRH Deployment ..... | 47 | +| 6.3.3.3.3 Scenario-B, Uni-directional RRH Deployment ..... | 47 | +| 6.3.3.3.4 Scenario-B, Bi-directional RRH Deployment..... | 50 | +| 6.3.3.4 Throughput Performance from Nokia..... | 51 | + +| | | | +|---------------------------------------------------|----------------------------------------------------------------|------------| +| 6.3.4 | Mobility Performance..... | 55 | +| 6.3.4.1 | System-level evaluation of mobility performance by Nokia ..... | 56 | +| 6.3.4.1.1 | Legacy RRM requirement mobility performance ..... | 56 | +| 6.3.4.1.1.1 | Uni-directional Scenario-A without DPS ..... | 57 | +| 6.3.4.1.1.2 | Uni-directional Scenario-A with DPS ..... | 60 | +| 6.3.4.1.1.3 | Uni-directional Scenario-B without DPS ..... | 62 | +| 6.3.4.1.1.4 | Uni-directional Scenario-B with DPS ..... | 64 | +| 6.3.4.1.1.5 | Bi-directional Scenario-B without DPS ..... | 66 | +| 6.3.4.1.1.6 | Bi-directional Scenario-B with DPS ..... | 68 | +| 6.3.4.1.1.7 | Bi-directional Scenario-A without DPS ..... | 70 | +| 6.3.4.1.1.8 | Bi-directional Scenario-A with DPS ..... | 72 | +| 6.3.4.1.2 | Enhanced RRM requirement mobility performance ..... | 73 | +| 6.3.4.1.2.1 | Uni-directional Scenario-A without DPS ..... | 76 | +| 6.3.4.1.2.2 | Uni-directional Scenario-A with DPS ..... | 78 | +| 6.3.4.1.2.3 | Uni-directional Scenario-B without DPS ..... | 80 | +| 6.3.4.1.2.4 | Uni-directional Scenario-B with DPS ..... | 82 | +| 6.3.4.1.2.5 | Bi-directional Scenario-B without DPS ..... | 84 | +| 6.3.4.1.2.6 | Bi-directional Scenario-B with DPS ..... | 86 | +| 6.3.4.1.2.7 | Bi-directional Scenario-A without DPS ..... | 87 | +| 6.3.4.1.2.8 | Bi-directional Scenario-A with DPS ..... | 90 | +| 6.3.4.1.2.9 | Uni-directional Tunnel scenario without DPS ..... | 92 | +| 6.3.4.1.2.10 | Uni-directional Tunnel scenario with DPS..... | 94 | +| 6.3.4.1.2.11 | Transition at the tunnel entrance/exit without DPS..... | 96 | +| 6.3.4.1.2.11.1 | Transition from open-space Scenario-A to the Tunnel..... | 98 | +| 6.3.4.1.2.12.1 | Transition from open-space Scenario-B to the Tunnel..... | 99 | +| 6.3.4.1.3 | Conclusions on mobility performance ..... | 100 | +| 6.3.5 | Receive time difference..... | 103 | +| 6.3.6 | Maximum supported Doppler frequency..... | 103 | +| 6.3.7 | Maximum supported Speed..... | 103 | +| 6.3.8 | Beam dwelling time..... | 104 | +| 6.3.8.1 | Simulation results ..... | 104 | +| 6.3.8.2 | Beam coverage analysis..... | 109 | +| 7 | Identified RAN4 requirements..... | 112 | +| 7.1 | CPE RF core requirements ..... | 112 | +| 7.1.1 | Minimum Peak EIRP ..... | 114 | +| 7.1.2 | Beam Correspondence..... | 115 | +| 7.2 | RRM requirements ..... | 116 | +| 7.2.1 | Idle/inactive mode ..... | 117 | +| 7.2.2 | Connected mode ..... | 117 | +| 7.2.2.1 | UE UL transmit timing ..... | 121 | +| 7.2.2.1.1 | Random Access based timing adjustment..... | 121 | +| 7.3 | Demodulation performance requirements..... | 122 | +| 7.3.1 | UE demodulation requirements ..... | 123 | +| 7.3.2 | BS demodulation requirements ..... | 134 | +| 8 | Conclusion ..... | 141 | +| Annex A (informative): Change history..... | | 142 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document is a technical report for Rel-17 NR support for high speed train scenario in FR2. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] C.A. Balanis: "Antenna theory: design and analysis ", Wiley, 2005. + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +# --- 4 Introduction + +5G NR operating in millimeter wave bands (i.e., Frequency Range 2) is recognized as the technology capable of providing ultra-high data-rate transmission, thanks to the availability of enormous amount of bandwidth in FR2 and the advanced 5G NR design for FR2 beamforming-based operation. Inspired by the successful commercial FR2 deployment globally, more potential 5G NR deployment scenarios in FR2 draw attentions from the industry. Among those scenarios identified, high speed train (HST) scenario has the special importance, because of the fast expanding HST systems worldwide deployed and the great demands of high-speed connections from passengers and HST special services. This triggers the new and challenging demand for 5G NR FR2 HST scenario. + +In existing study and work items led by 3GPP RAN4 (for either LTE or NR), high speed train scenarios under consideration has the operating bands up to 3.5GHz, however no existing works studied the more challenging millimeter wave frequency range 2, in which Doppler shift and Doppler spread will be further severe (e.g., for 240km/h with 28GHz, the Doppler shift is about 6.22kHz) and more challenging to radio resource management. Specifically, the existing FR2 RRM and demodulation requirements has not yet taken into account the impact of high speed in the above-mentioned scenario, where the channel model and mobility scenario need further study and the demodulation, measurement, mobility and beam management related requirements require to be further specified. + +It should be noted that user equipment considered in 5G NR FR2 HST scenario is vehicle-roof mounted customer-premises equipment (CPE), which are expected to communicate with track-side deployed gNBs for the backhaul link and to further provide on-board broadband connections to user terminals and/or for other train-specific demands as access link. + +This work will specify NR UE RF requirements, UE RRM requirements and BS/UE performance requirements for high speed train scenario with up to 350km/h in Rel-17. + +# 5 FR2 HST deployment scenario + +Following section include the agreed FR2 HST deployment specific investigated options and agreements. + +## 5.1 General + +This section includes the agreed scenario and RRH parameters to be used in the investigated FR2 HST deployments. It captures the agreement and conclusions made during the work on FR2 HST deployment scenario and related aspects. Following figure 5.1-1 illustrates the definition of the different used D-values. + +![Figure 5.1-1: Illustration of the D-values used on RAN4 work. The diagram shows a high-speed train (UE) moving along a track with velocity v. The train is equipped with an RRH (Radio Remote Head) and a UE (User Equipment). The RRH is connected to a BBU (Baseband Unit) via a backhaul link. The UE is connected to the RRH via an access link. The diagram defines several distance parameters: D_t (track width), D_s (station spacing), D_UE_height (UE height), D_RRH_height (RRH height), and D_min (minimum distance).](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg) + +The diagram illustrates a high-speed train (UE) moving along a track with velocity $v$ . The train is equipped with an RRH (Radio Remote Head) and a UE (User Equipment). The RRH is connected to a BBU (Baseband Unit) via a backhaul link. The UE is connected to the RRH via an access link. The diagram defines several distance parameters: $D_t$ (track width), $D_s$ (station spacing), $D_{UE\_height}$ (UE height), $D_{RRH\_height}$ (RRH height), and $D_{min}$ (minimum distance). The BBU is shown both above and below the track, connected to the RRH. The UE is shown on the train, with a beam directed towards the RRH. + +Figure 5.1-1: Illustration of the D-values used on RAN4 work. The diagram shows a high-speed train (UE) moving along a track with velocity v. The train is equipped with an RRH (Radio Remote Head) and a UE (User Equipment). The RRH is connected to a BBU (Baseband Unit) via a backhaul link. The UE is connected to the RRH via an access link. The diagram defines several distance parameters: D\_t (track width), D\_s (station spacing), D\_UE\_height (UE height), D\_RRH\_height (RRH height), and D\_min (minimum distance). + +Figure 5.1-1 Illustration of the D-values used on RAN4 work. + +General deployment parameters: + +RAN4 will at least consider the following general deployment for open-space scenarios: + +- $D_s$ and $D_{min}$ : Take the 5 scenarios in table 5.1-1 as basic assumption; and +- Scenario 1 and 4 shall be considered with high priority; and +- $D_{min}$ for [5m, 20, 30 and 50 meters] if found to be necessary; and +- $D_{RRH\_height}$ : 15m as basic assumption, [10,20m] if found to be necessary; and +- $D_{UE\_height}$ : 5m. + +| Scenario | D s (meter) | D min (meter) | +|----------|------------------------|--------------------------| +| 1 | 800 | 10 | +| 2 | 700 | 10 | +| 3 | 500 | 10 | +| 4 | 700 | 150 | +| 5 | 200 | 30 | + +RAN4 will at least consider the following assumptions for the deployment in the tunnel scenario: + +- Ds and DUE\_height are considered similar as in open-space deployment in Scenario 2 and 4, i.e., Ds=700m and DUE\_height=5m; and +- Dmin and DRRH\_height are constrained by the tunnel (e.g, dimension, shape, etc), and shall be smaller than values for open space scenario; +- Dmin: 1m; and +- DRRH\_height: 5.3m for one-track tunnel and 7.4m for two-track tunnel as the baseline assumption. The one-track tunnel shall be considered with higher priority. + +### Sub-Carrier Spacing (SCS): + +It is still open which SCS options to consider. The options are: + +- Option-1: SCS = 120kHz; and +- Option-2: Consider both SCS = 120kHz and 60kHz. + +Concerning the transmissions schemes following schemes were discussed in distinguished: + +- JT: Joint Transmission scheme applied for all channel (SSB, TRS, PDCCH, PDSCH) – Full SFN; and +- DPS: Dynamic Point Selection based on the Rel-15 beam management (BM) principles; and +- Multi-DCI based Multi-TRP transmission based on the Rel-15 eMIMO principles. + +Among these the following down selection has been agreed: + +- For Rel-17 WI discussion, FR2 HST transmission schemes which are not compatible with Rel-15/16 NR are precluded; and +- For Rel-17 WI discussion, Joint transmission (JT) used for FR2 HST, only full SFN is considered; and +- For Rel-17 WI discussion, Multi-DCI based multi-TRP transmission is precluded. + +RAN4 primarily consider HST FR2 deployment with + +- One train moving over one railway track in one direction. RAN4 focuses on 1 direction 1 train. If this opposite direction is completely symmetric, the 1 direction study can apply directly; and +- RRHs are located on one side of the track. + +Dedicated network for roof-mounted CPE: + +- RAN4 to assume that in HST FR2 Scenario A, only high-speed CPEs installed on the roof of the train can be present in the network. + +RAN4 did comparison between unidirectional and bi-directional RRH deployments for Scenario-A and concluded that from signal strength and beam coverage perspective the bi-directional deployment will not provide significant throughput improvement compared to unidirectional deployment. This conclusion is based on the deployment scenario analysis. RAN4 will only consider unidirectional deployments for Scenario-A. Bi-directional deployment can be considered if the feasibility issue of unidirectional deployment is identified. + +RAN4 assume that FR2 HST with CPEs is operated as dedicated network. Hence, assumption in RAN4 is that in HST FR2 Scenario A and B, only high-speed CPEs installed on the roof of the train can be present in the network. There is no need to differentiate roof-mounted CPE from other FR2 UEs in HST FR2 scenario. + +RAN4 will not consider curvature when defining the requirements. + +RAN4 assumed that uni-directional and bi-directional RRH deployments can be considered for tunnel scenario, in which single-panel reception UE and DPS transition scheme shall have higher priority. RAN4 also agreed that multi-panel reception may also be considered in the HST FR2 tunnel scenario to alleviate potential mobility issues that may occur inside the tunnel. + +## 5.2 HST scenario and RRH parameters + +RAN4 will investigate both unidirectional and bidirectional deployment scenarios for FR2 HST. + +The exact understanding and definition of HST still needs further discussion based on the following interpretations: + +- HST Interpretation-1: All RRHs under one BBU transmit the same signal (SFN). + - Selected RRH(s) for TX, depending on DPS Tx mode is used or not. +- HST Interpretation-2: All RRHs under one BBU in the same cell ID, but for different TCI. +- Other interpretation is not precluded. + +For full SFN JT and unidirectional RRH deployment, only consider following scenario: + +- The setting with only one TCI state transmission. + +The value of $D_{s\_offset}$ implicitly limit the RRH beam direction, so there is no need to introduce additional restriction on RRH beam's possible range of angle on azimuthal plane. + +### 5.2.1 Unidirectional deployments + +For the unidirectional scenario RAN4 will consider SFN scenario. Hence, one panel per RRH pointed to the same direction for all RRHs (figure 5.2.1-1). + +![Figure 5.2.1-1: HST scenario with one panel per RRH pointing to the same direction for all RRHs. The diagram shows a high-speed train (UE) moving to the right with velocity v. Above the train, RRH1, RRH2, and RRH3 are deployed. Below the train, another set of RRH1, RRH2, and RRH3 are deployed. A BBU is connected to the RRHs. The diagram includes various distance and height parameters: D_T (track width), h_k (height of RRH above track), h_1 (height of UE), D_k (distance between RRHs), D_k^* (distance between RRHs and UE), D_s (distance between BBU and RRHs), and D_min (minimum distance between RRH and UE).](ee8536b235eb6aad21e2048fd5308900_img.jpg) + +Figure 5.2.1-1: HST scenario with one panel per RRH pointing to the same direction for all RRHs. The diagram shows a high-speed train (UE) moving to the right with velocity v. Above the train, RRH1, RRH2, and RRH3 are deployed. Below the train, another set of RRH1, RRH2, and RRH3 are deployed. A BBU is connected to the RRHs. The diagram includes various distance and height parameters: D\_T (track width), h\_k (height of RRH above track), h\_1 (height of UE), D\_k (distance between RRHs), D\_k^\* (distance between RRHs and UE), D\_s (distance between BBU and RRHs), and D\_min (minimum distance between RRH and UE). + +**Figure 5.2.1-1 HST scenario with one panel per RRH pointing to the same direction for all RRHs** + +For the unidirectional scenario the following unidirectional deployment scenario in table 5.2-1 will be prioritized: + +**Table 5.2-1: Assumed deployment parameters for unidirectional scenario.** + +| Parameter | Value | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ds and Dmin | Scenario 2: Ds = 700m and Dmin = 10m
Scenario 4: Ds = 700m and Dmin = 150m
Tunnel scenario: Ds=700m and Dmin = 1m | +| RRH height | Scenario 2 and 4: 15m
Tunnel Scenario: 5.3m Note 1 | +| Number of RRH sites per BBU | 4 | +| Number of RRH panels per RRH sites | 1 (i.e. unidirectional) Note 2 | +| Number of analog beams per RRH panel | 1 or 2 Note 3 | +| RRH panel orientation | Option 1: RRH panel boresight pointed to the railway at the direction of Ds (projection of the neighboring RRH on the railway).
Option 2: other options not precluded | +| Analog beam orientation | Based on companies' selection for better performance | +| Note 1: | RRH height for single track railway tunnel. For two-track railway tunnel, RRH height is 7.4m | +| Note 2: | For JT for all channels, 1 beam per RRH panel is considered. | +| Note 3: | For DPS, 1 or 2 analog beams per RRH panel can be considered. | + +Number of Beam for unidirectional RRH deployment, Scenario 2: + +- For scenario 2, unidirectional, RRH parameter: 1 beam per RRH panel; and +- For scenario 2, unidirectional, UE parameter: + - a) 1 beam per panel; and + - b) 2 panels assumed to be implemented in the UE side; and + - c) Only the one active panel per UE can be used for Tx and Rx; and FFS whether another panel can be used for beam search + +RRH switching point for unidirectional RRH deployment, Scenario 2, figure 5.2.1-2: + +- RRH switching point is where the UE switches from the source RRH beam to the target RRH beam based on maximizing SNR among detected beams. + +![Diagram illustrating RRH switching points for unidirectional RRH deployment. It shows four RRH sites (RRH1, RRH2, RRH3, RRH4) along a railway. The distance between adjacent RRHs is Ds. The distance from the railway to the RRH is Dmin. The diagram shows the UE moving from left to right. Switching points are indicated where the UE switches from one RRH to the next. The first switching point is labeled 'Switch to RRH1' and is located at a distance Ds_offset from RRH1. Subsequent switching points are labeled 'Switch to RRH2' and 'Switch to RRH3'. The serving ranges for RRH1, RRH2, and RRH3 are also indicated.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +Diagram illustrating RRH switching points for unidirectional RRH deployment. It shows four RRH sites (RRH1, RRH2, RRH3, RRH4) along a railway. The distance between adjacent RRHs is Ds. The distance from the railway to the RRH is Dmin. The diagram shows the UE moving from left to right. Switching points are indicated where the UE switches from one RRH to the next. The first switching point is labeled 'Switch to RRH1' and is located at a distance Ds\_offset from RRH1. Subsequent switching points are labeled 'Switch to RRH2' and 'Switch to RRH3'. The serving ranges for RRH1, RRH2, and RRH3 are also indicated. + +**Figure 5.2.1-2: RRH switching point for unidirectional RRH deployment.** + +Number of Beam for unidirectional RRH deployment, Scenario 4: + +- For scenario 4, unidirectional, RRH parameter: + - a) 1 beam per RRH panel; or + - b) 2 beams per RRH panel; or + +- c) 3 beams per RRH panel; or +- d) 4 beams per RRH panel. + +Note that uneven separation between beams can be considered. + +RAN4 agreed that at least 2 beams per RRH panel is considered. Other options are not precluded, and it is FFS whether there are benefits of implementing more beams per RRH panel. + +- For scenario 4, unidirectional, UE parameter: + - a) 1 beam per UE panel; or + - b) 2 beams per UE panel; or + - c) 7 beams per UE panel. + +RAN4 assumes 2 panels to be implemented in the UE side. Only the one active panel per UE can be used for Tx and Rx; and FFS whether another panel can be used for beam search. + +RAN4 decided that at least option a) of having 1 beam per panel is considered. Other options are not precluded, and it is FFS whether there are benefits of implementing more beams per UE panel. + +Number of Beam for unidirectional RRH deployment in Tunnel scenario shall follow similar setting as in Scenario 2: + +- For Tunnel scenario, unidirectional, RRH parameter: 1 beam per RRH panel; and +- For Tunnel scenario, unidirectional, UE parameter: + - a) 1 beam per panel; and + - b) 2 panels assumed to be implemented in the UE side; and + - c) Only the one active panel per UE can be used for Tx and Rx; and FFS whether another panel can be used for beam search + +RRH switching point for unidirectional RRH deployment, Tunnel scenario, Figure 5.2.1-2 with $D_{s\_offset}$ could be shorter than that in Scenario 2. + +### 5.2.2 Bidirectional deployment + +For the bidirectional scenario RAN4 will consider SFN scenario where there is one panel per RRH with signals to opposite directions along the track (figure 5.2.2-1). + +![Diagram of HST scenario with one panel per RRH. It shows a high-speed train (UE) moving along a track. Above the track are four Base Band Units (BBUs) connected to Remote Radio Heads (RRHs). The RRHs are labeled RRH1 and RRH2. The diagram includes various parameters: h_k (height of RRH), h_1 (height of UE), D_T (distance between RRHs), D_s = D_R (switching point distance), and D_min (minimum distance). The UE is shown with a velocity v and an angle theta. The RRHs are shown with beams directed towards the UE.](426efb7efdc753a13f2fa16f7bff9429_img.jpg) + +Diagram of HST scenario with one panel per RRH. It shows a high-speed train (UE) moving along a track. Above the track are four Base Band Units (BBUs) connected to Remote Radio Heads (RRHs). The RRHs are labeled RRH1 and RRH2. The diagram includes various parameters: h\_k (height of RRH), h\_1 (height of UE), D\_T (distance between RRHs), D\_s = D\_R (switching point distance), and D\_min (minimum distance). The UE is shown with a velocity v and an angle theta. The RRHs are shown with beams directed towards the UE. + +Figure 5.2.2-1 HST scenario with one panel per RRH + +Additionally, also SFN scenario where there are two panels per RRH (figure 5.2.2-2). + +![Figure 5.2.2-2: HST scenario with two panels per RRH. The diagram shows a high-speed train (UE) moving at velocity v along a railway. Two RRH sites are shown, each with two panels (RRH1, RRH2 on the left; RRH3, RRH4 on the right). Each RRH panel is connected to a BBU. Key parameters include: D_T (distance between RRH sites), D_k (distance from BBU to RRH panel), h_k (height of RRH panel), h_l (height of UE), D_s* (distance between RRH panels on the same site), D_s (distance between RRH sites), and D_min (minimum distance from railway to RRH panel).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 5.2.2-2: HST scenario with two panels per RRH. The diagram shows a high-speed train (UE) moving at velocity v along a railway. Two RRH sites are shown, each with two panels (RRH1, RRH2 on the left; RRH3, RRH4 on the right). Each RRH panel is connected to a BBU. Key parameters include: D\_T (distance between RRH sites), D\_k (distance from BBU to RRH panel), h\_k (height of RRH panel), h\_l (height of UE), D\_s\* (distance between RRH panels on the same site), D\_s (distance between RRH sites), and D\_min (minimum distance from railway to RRH panel). + +Figure 5.2.2-2 HST scenario with two panels per RRH + +For the bi-directional scenario the following bi-directional deployment scenario in table 5.2-2 will be studied: + +Table 5.2-2: Assumed deployment parameters for bi-directional scenario. + +| Parameter | Value | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ds and Dmin | Scenario 2: Ds = 700m and Dmin = 10m
Scenario 4: Ds = 700m and Dmin = 150m
Tunnel scenario: Ds=700m and Dmin=1m | +| RRH height | Scenario 2 and 4: 15m
Tunnel Scenario: 5.3m | +| Number of RRH sites per BBU | 4 | +| Number of RRH panels per RRH sites | 2 (i.e. bi-directional) | +| Number of analog beams per RRH panel | 1, 2 or 4 | +| RRH panel orientation | Option 1: RRH panel boresight pointed to the railway in the middle point between 2 RRHs.
Option 2: RRH panel boresight pointed to the railway at the distance of Ds (projection of the neighboring RRH on the railway). Other options not precluded. | +| Analog beam orientation | Based on companies' selection for better performance | + +Candidate schemes for bi-directional deployment for further analysis, scenario 2: + +![Figure 5.2.2-3: Connecting to 2nd-Nearest RRH. The diagram shows three RRH sites (RRH1, RRH2, RRH3) with two panels each (RRH-panel1, RRH-panel2). A train (UE) is moving along the railway. The diagram illustrates the connection of UE-panel1 and UE-panel2 to the 2nd-nearest RRH panels. Key parameters include: Ds (distance between RRH sites), Dmin (minimum distance from railway to RRH panel), and UE panel switch distances (0Ds, 0.5Ds, Ds, 1.5Ds, 2Ds).](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +Figure 5.2.2-3: Connecting to 2nd-Nearest RRH. The diagram shows three RRH sites (RRH1, RRH2, RRH3) with two panels each (RRH-panel1, RRH-panel2). A train (UE) is moving along the railway. The diagram illustrates the connection of UE-panel1 and UE-panel2 to the 2nd-nearest RRH panels. Key parameters include: Ds (distance between RRH sites), Dmin (minimum distance from railway to RRH panel), and UE panel switch distances (0Ds, 0.5Ds, Ds, 1.5Ds, 2Ds). + +Figure 5.2.2-3: Connecting to 2nd-Nearest RRH + +![Figure 5.2.2-4: Scheme-2: Connecting to Nearest RRH except Coverage Hole. This diagram shows a network with three RRHs (RRH1, RRH2, RRH3) and five User Equipment (UE) units. RRH1 has two panels, RRH2 has one, and RRH3 has one. Each UE has two panels. Green lines represent active connections between UE panels and RRH panels. Blue lines represent potential or alternative connections. Red double-headed arrows indicate 'UE panel switch' points at each UE. Horizontal distances are marked as Ds between RRHs and Dmin for vertical distances. The horizontal distance between adjacent UEs is labeled as Ds/2.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 5.2.2-4: Scheme-2: Connecting to Nearest RRH except Coverage Hole. This diagram shows a network with three RRHs (RRH1, RRH2, RRH3) and five User Equipment (UE) units. RRH1 has two panels, RRH2 has one, and RRH3 has one. Each UE has two panels. Green lines represent active connections between UE panels and RRH panels. Blue lines represent potential or alternative connections. Red double-headed arrows indicate 'UE panel switch' points at each UE. Horizontal distances are marked as Ds between RRHs and Dmin for vertical distances. The horizontal distance between adjacent UEs is labeled as Ds/2. + +Figure 5.2.2-4: Scheme-2: Connecting to Nearest RRH except Coverage Hole + +For Scenario 2 bi-directional RRH deployment: + +- [Scheme 1 under bi-directional scenario is feasible without coverage hole issue, and no propagation delay jump between switching points]; +- Scheme-2 can be used as starting points for further analysis. + +Number of beams for bi-directional RRH deployment, Scenario 2: + +- For scenario 2, bi-directional, RRH parameter: 1 beam per RRH panel, two panels in opposite directions; and +- For scenario 2, bi-directional, UE parameter: 1 beam per UE panel (i.e., 2 beams per UE). + +Candidate schemes for bi-directional deployment for further analysis, for scenario 4: + +![Figure 5.2.2-5: Connecting to 2nd-Nearest RRH. This diagram shows three RRHs (RRH1, RRH2, RRH3) and four UEs. RRH1 and RRH3 have two panels each, while RRH2 has one. Green lines show connections from UE panels to the 2nd-nearest RRH. Horizontal distances between RRHs are Ds, and vertical distances are Dmin. Below the UEs, 'UE panel switch' points are marked with distances: 0Ds, 0.5Ds, Ds, 1.5Ds, and 2Ds.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +Figure 5.2.2-5: Connecting to 2nd-Nearest RRH. This diagram shows three RRHs (RRH1, RRH2, RRH3) and four UEs. RRH1 and RRH3 have two panels each, while RRH2 has one. Green lines show connections from UE panels to the 2nd-nearest RRH. Horizontal distances between RRHs are Ds, and vertical distances are Dmin. Below the UEs, 'UE panel switch' points are marked with distances: 0Ds, 0.5Ds, Ds, 1.5Ds, and 2Ds. + +Figure 5.2.2-5: Connecting to 2nd-Nearest RRH + +![Figure 5.2.2-67: Scheme-2: Connecting to Nearest RRH except Coverage Hole. This diagram is similar to Figure 5.2.2-4 but shows a different connection scheme. It features three RRHs and five UEs. Connections are shown with green and blue lines. Red double-headed arrows indicate 'UE panel switch' points. Horizontal distances between UEs are marked as Ds/2, and vertical distances as Dmin.](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +Figure 5.2.2-67: Scheme-2: Connecting to Nearest RRH except Coverage Hole. This diagram is similar to Figure 5.2.2-4 but shows a different connection scheme. It features three RRHs and five UEs. Connections are shown with green and blue lines. Red double-headed arrows indicate 'UE panel switch' points. Horizontal distances between UEs are marked as Ds/2, and vertical distances as Dmin. + +Figure 5.2.2-67: Scheme-2: Connecting to Nearest RRH except Coverage Hole + +![Figure 5.2.2-7: Scheme-3: Connecting to Nearest RRH except the area under the RRH. The diagram shows three RRHs (Radio Remote Heads) positioned above a horizontal line representing a tunnel. Each RRH has two beams, labeled SSB#0 (red) and SSB#1 (green), directed towards the tunnel. The beams from the left RRH are labeled SSB#3 (green) and SSB#2 (red). The beams from the middle RRH are labeled SSB#3 (green) and SSB#2 (red). The beams from the right RRH are labeled SSB#0 (red) and SSB#1 (green). The beams are shown as lines connecting the RRHs to the tunnel, with the area under each RRH excluded from coverage.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 5.2.2-7: Scheme-3: Connecting to Nearest RRH except the area under the RRH. The diagram shows three RRHs (Radio Remote Heads) positioned above a horizontal line representing a tunnel. Each RRH has two beams, labeled SSB#0 (red) and SSB#1 (green), directed towards the tunnel. The beams from the left RRH are labeled SSB#3 (green) and SSB#2 (red). The beams from the middle RRH are labeled SSB#3 (green) and SSB#2 (red). The beams from the right RRH are labeled SSB#0 (red) and SSB#1 (green). The beams are shown as lines connecting the RRHs to the tunnel, with the area under each RRH excluded from coverage. + +**Figure 5.2.2-7: Scheme-3: Connecting to Nearest RRH except the area under the RRH** + +For Scenario 4 bi-directional RRH deployment: the schemes above can be used as starting points for further analysis. + +Number of beams for bi-directional RRH deployment, Scenario 4: + +- For scenario B, bi-directional, RRH parameter: + - a) 1 beam per RRH panel; or + - b) 2 beams per RRH panel; or + - c) 3 beams per RRH panel; or + - d) 4 beams per RRH panel. + +Note that uneven separation between beams can be considered. + +RAN4 agreed that at least 2 beams per RRH panel is considered. Other options are not precluded, and it is FFS whether there are benefits of implementing more beams per RRH panel. + +- For scenario 4, bi-directional, UE parameter: + - a) 1 beam per UE panel; or + - b) 2 beams per UE panel; or + - c) 7 beams per UE panel. + +RAN4 assumes 2 panels to be implemented in the UE side. Only the one active panel per UE can be used for Tx and Rx; and FFS whether another panel can be used for beam search. + +RAN4 decided that at least option a) of having 1 beam per panel is considered. Other options are not precluded, and it is FFS whether there are benefits of implementing more beams per UE panel. + +Number of beams for bi-directional RRH deployment in Tunnel scenario shall be similar to Scenario 2 setting: + +- For Tunnel scenario, bi-directional, RRH parameter: 1 beam per RRH panel, two panels in opposite directions; and +- For Tunnel scenario, bi-directional, UE parameter: 1 beam per UE panel (i.e., 2 beams per UE). + +For bi-directional RRH deployment, DPS transmission scheme shall be considered. + +### 5.2.3 RRH Parameters + +The detailed RRH parameters are still under discussion in RAN4 and following options have been agreed for potential down selection: + +Number of RRH sites per BBU: + +- [1 to 4] RRHs sites per BBU; and + +- Other values are not precluded. + +Number of Analog Beams per panel in RRH: + +- [1,2,4] analogue beam(s) per panel in RRH; and +- Other values are not precluded. + +SSB index to Beam Mapping. The impact of following options for SSB index to Beam mapping is FFS: + +- 1) Option 1: + - a) All RRHs (connected to one BBU with fiber) share the same cell ID; and + - b) All RRHs under the same cell use the same set of SSB indexes, e.g., all RRHs use SSB-0 to SSB-3. +- 2) Option 2: + - a) All RRHs (connected to one BBU with fiber) share the same cell ID; and + - b) RRHs under the same cell use the different sets of SSB indexes, e.g., RRH-1 uses SSB-0 to SSB-3, RRH-2 uses SSB-4 to SSB-7. + +When DPS is used as transmission scheme, SSB index to Beam Mapping used in the discussion for this WI is as follows: + +RRHs under the same cell use different sets of SSB indexes, e.g., RRH-1 uses SSB-0 to SSB-3, RRH-2 uses SSB-4 to SSB-7, etc. + +RAN4 discussed the aspect of potential handover problem due to sudden RX signal increase of the target cell. RAN4 thinks that this can be alleviated by DPS transmission scheme with carefully allocated SSB-index among neighboring cells to avoid inter-cell interference. + +Concerning RRH antenna array orientation the impact of following options for RRH antenna array orientation is FFS: + +- Option 1: RRH panel boresight pointed to the railway in the middle point between 2 RRHs; or +- Option 2: RRH panel boresight pointed to the railway at the distance of $D_s$ (projection of the neighbouring RRH on the railway); or +- Other option is not precluded. + +Related to RRH/UE boresight direction of Antenna Panel and beam direction, RAN4 may not need to specify RRH/UE boresight direction of antenna panel and beam direction for deployment scenario study, but left for companies' choice: + +- RRH/UE boresight direction of antenna panel and beam direction information can be provided by individual company to accompany their deployment scenario analysis result, which can be captured in TR. + +## 5.3 Train roof-mounted high-power CPE parameters + +## 5.3.0 Introduction + +NOTE: Single panel, i.e. only one active antenna panel at a time, as baseline antenna assumption + +### 5.3.1 Number of panels per CPE + +The number of panels per CPE was open and for discussion. Concerning the number of panels per CPE following will be considered: + +- 2 panels per CPE each for both for TX and RX. Each panel points in opposite directions. + +For the bi-directional Operation for Two Panels in the CPE following is considered: + +- Follow the Rel-15/16 principle of “only one active Rx/Tx panel at a time”. + +### 5.3.2 Placement of CPE panel(s) + +UE antenna panel(s) for forward and backward directions: + +- RAN4 to consider CPE to be equipped with two panels pointed forward and backward along the track. + +UE boresight direction of Antenna Panel and beam direction, RAN4 may not need to specify RRH/UE boresight direction of antenna panel and beam direction for deployment scenario study, but left for companies’ choice: + +- RRH/UE boresight direction of antenna panel and beam direction information can be provided by individual company to accompany their deployment scenario analysis result, which can be captured in TR. + +### 5.3.3 Number of CPE devices + +Number of CPE devices per train/carriage: + +- RAN4 requirement can be defined based on the baseline of 1 CPE device per train. + +# 6 FR2 high speed feasibility evaluation + +This section will include the evaluation parameters and channel model used in the FR2 HST and used for evaluating the feasibility FR2 HST. + +## 6.1 Evaluation Parameters + +### 6.1.1 RRH antenna array parameters for evaluation + +RAN4 will perform FR2 HST feasibility study based on following RRH antenna array parameters in table 6.1.1.1 for evaluation: + +**Table 6.1.1.1** + +| Parameter | Urban Macro 30 GHz | +|-------------|--------------------| +| $A_m$ | 30 | +| $SLA_y$ | 30 | +| $j_{3dB}$ | 90 | +| $Q_{3dB}$ | 90 | +| $G_{e,max}$ | 5.5 | +| $L_E$ | 1.8 | +| $P$ | 2 | +| $d_y$ | $0.5\lambda$ | +| $d_h$ | $0.5\lambda$ | + +Antenna array configuration options were considered: + +- Option-1: $[M_g, N_g, M, N, P] = [1, 1, 4, 8, 2]$ ; and +- Option-2: $[M_g, N_g, M, N, P] = [1, 1, 8, 8, 2]$ ; and +- Option-3: $[M_g, N_g, M, N, P] = [1, 1, 8, 16, 2]$ . + +RAN4 also agreed that other options are not precluded. RRH Antenna Element Assumption for RRH side following option is assumed: + +- Option-2: [Mg, Ng, M, N, P] = [1, 1, 8, 8, 2]. + +RF session can trigger relevant discussion on RF requirements taking above agreements into account. + +### 6.1.2 RRH antenna element parameters for evaluation + +RAN4 agreed to use the following RAN1 assumptions in table 6.1.2.1 for BS evaluation as baseline, while other assumptions are not precluded: + +**Table 6.1.2.1: BS evaluation parameters.** + +| | | | +|-------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Radiation power pattern of a single antenna element for TRP | Vertical cut of the radiation power pattern (dB) | $A_{\text{dB}}''(\theta'', \phi'' = 0^\circ) = -\min \left\{ 12 \left( \frac{\theta'' - 90^\circ}{\theta_{3\text{dB}}} \right)^2, SLA_V \right\}$ with $\theta_{3\text{dB}} = [65^\circ]$ , $SLA_V = 30 \text{ dB}$ and $\theta'' \in [0^\circ, 180^\circ]$ | +| | Horizontal cut of the radiation power pattern (dB) | $A_{\text{dB}}''(\theta'' = 90^\circ, \phi'') = -\min \left\{ 12 \left( \frac{\phi''}{\phi_{3\text{dB}}} \right)^2, A_{\text{max}} \right\}$ with $\phi_{3\text{dB}} = [65^\circ]$ , $A_{\text{max}} = 30 \text{ dB}$ and $\phi'' \in [-180^\circ, 180^\circ]$ | +| | 3D radiation power pattern (dB) | $A_{\text{dB}}''(\theta'', \phi'') = -\min \left\{ -(A_{\text{dB}}''(\theta'', \phi'' = 0^\circ) + A_{\text{dB}}''(\theta'' = 90^\circ, \phi'')), A_{\text{max}} \right\}$ | +| | Maximum directional gain of an antenna element $G_{E,\text{max}}$ | [8] dBi | + +### 6.1.3 CPE antenna array parameters for evaluation + +RAN4 will perform the FR2 HST feasibility study based on following CPE antenna array parameters for evaluation: + +- RAN1 assumption: 2 ports: [Mg, Ng, M, N, P] = [1, 1, 2, 4, 2]; and +- PC4 assumption: 2 ports: [Mg, Ng, M, N, P] = [1, 1, 4, 4, 2]. + +RAN4 also agreed that other options are not precluded. + +UE Antenna Element Assumption: on UE side: + +- Option 1: N=4, M=4 with 2 polarizations as starting point, and other options not precluded pending on further discussion. + +RF session can trigger relevant discussion on RF requirements taking above agreements into account. + +### 6.1.4 CPE antenna element parameters for evaluation + +RAN4 use the following RAN1 assumption for CPE antenna element parameters evaluation in table 6.1.4.1 as baseline: + +**Table 6.1.4.1: CPE antenna element parameters.** + +| Parameter | Values | +|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Antenna element radiation pattern in $\theta''$ dim (dB) | $A_{E,V}(\theta'') = -\min \left[ 12 \left( \frac{\theta'' - 90^\circ}{\theta_{3dB}} \right)^2, SLA_V \right], \theta_{3dB} = 90^\circ, SLA_V = 25$ | +| Antenna element radiation pattern in $\phi''$ dim (dB) | $A_{E,H}(\phi'') = -\min \left[ 12 \left( \frac{\phi''}{\phi_{3dB}} \right)^2, A_m \right], \phi_{3dB} = 90^\circ, A_m = 25$ | +| Combining method for 3D antenna element pattern (dB) | $A''(\theta'', \phi'') = -\min \left\{ [A_{E,V}(\theta'') + A_{E,H}(\phi'')]_f, A_m \right\}$ | +| Maximum directional gain of an antenna element $G_{E,max}$ | 5dBi | + +## 6.2 Channel model for FR2 HST + +This section collects the channel model information used for FR2 HST feasibility evaluation and provides the analysis on channel modelling for performance requirements. + +### 6.2.1 Pathloss model used for link budget evaluation + +#### Pathloss model for open-space deployments: + +To have the link budget analysis for the proposed FR2 HST deployment scenarios, the accurate large-scale pathloss model is one of the prerequisites. The following large scale pathloss models are proposed to be considered as candidate options: + +- Option-1: TR38.901 RMa LoS (baseline option); or +- Option-2: free space model; or +- Option-3: TR38.901 UMa LoS. + +TS38.901 RMa LoS pathloss model will be used for link budget evaluation at least for scenario 2 in table 5.1-1. + +RAN4 to choose TS38.901 RMa LoS pathloss model also for the evaluation of Scenario 4 in table 5.1-1. + +For the purpose of demonstrating and validating which large scale channel modeling is suitable for FR2 HST, the analysis has been provided based on the practical field measurement. Specifically, based upon the conditions provided in the Table 6.2.1-1, the practical field testing on a train along a typical railway has been conducted to obtain measurement data at the frequency of 28GHz, as illustrated in the Figure 6.2.1-1. + +**Table 6.2.1-1 Parameters for practical field measurement for typical high speed train scenario** + +| Parameter name | Configuration value | +|-------------------------|---------------------| +| Minimum TX-RX distance | 60 m | +| Maximum TX-RX distance | 550 m | +| Distance granularity | 1 m | +| Center frequency | 28 GHz | +| TX antenna height | 5 m | +| RX antenna height | 3 m | +| Parameter $h_E$ in 3GPP | 1 m | + +![Figure 6.2.1-1: Illustration of practical field measurement conducted for typical high speed train scenario. The figure consists of three parts: the top left shows a transmitter (Tx) on a truck at 5m height; the top right shows a receiver (Rx) on a truck at 3m height; the bottom part shows the Rx path along a railway track with the Tx at the end.](63c666b05041841b01fdef9fa4153ff7_img.jpg) + +Figure 6.2.1-1: Illustration of practical field measurement conducted for typical high speed train scenario. The figure consists of three parts: the top left shows a transmitter (Tx) on a truck at 5m height; the top right shows a receiver (Rx) on a truck at 3m height; the bottom part shows the Rx path along a railway track with the Tx at the end. + +**Figure 6.2.1-1 Illustration of practical field measurement conducted for typical high speed train scenario** + +By having the analysis based on the measurement data obtained from the measurement campaign as above described, the comparison among measurement results and pathloss models (i.e., the three options of RMa LOS, UMa LOS and free space model) is demonstrated in Figure 6.2.1-2 and accompanying Table 6.2.1-2 in which the numerical results are contained. + +![Figure 6.2.1-2: Comparison of measurement data and pathloss models for FR2 HST. This is a scatter plot with three fitted lines. The x-axis is 'Distance in m' ranging from 50 to 550. The y-axis is 'Path loss in dB' ranging from 85 to 130. The legend indicates: black dots for 'HSR measured result', a cyan line for 'Free Space', a red line for 'RMa LOS 38901', and a blue line for 'UMa LOS 38901'. All three lines show a similar upward trend, starting around 95 dB at 50m and reaching approximately 118 dB at 550m. The measured data points are scattered around these lines.](ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg) + +Figure 6.2.1-2: Comparison of measurement data and pathloss models for FR2 HST. This is a scatter plot with three fitted lines. The x-axis is 'Distance in m' ranging from 50 to 550. The y-axis is 'Path loss in dB' ranging from 85 to 130. The legend indicates: black dots for 'HSR measured result', a cyan line for 'Free Space', a red line for 'RMa LOS 38901', and a blue line for 'UMa LOS 38901'. All three lines show a similar upward trend, starting around 95 dB at 50m and reaching approximately 118 dB at 550m. The measured data points are scattered around these lines. + +**Figure 6.2.1-2 Comparison of measurement data and pathloss models for FR2 HST** + +By leveraging the numerical results in terms of the root mean square error (RMSE), mean error and standard deviation (Std), it has been demonstrated that for the evaluated range there is no significant difference from three different pathloss LoS models, and the field measurement also validate that LoS model can reflect the practical FR2 HST channel condition compared with NLoS models. By further investigating three LoS models' similarity from measurement data, it has been demonstrated that RMa LoS model can achieve the lowest value of RMSE and best mean error with reasonable standard deviation. + +**Table 6.2.1-2 Numerical comparison of measurement data and pathloss models for FR2 HST** + +| | RMSE | Mean Error | Std | +|------------------|---------|------------|--------| +| Free space model | 4.5212 | -0.74819 | 4.4634 | +| RMa LoS model | 4.4716 | 0.13552 | 4.4741 | +| UMa LoS model | 4.4974 | -0.3428 | 4.4889 | +| RMa NLoS model | 35.1499 | 34.4667 | 6.9036 | +| UMa NLoS model | 26.5 | 25.692 | 6.5006 | + +Based upon the above analysis on the measurement data from the typical railway environment for 28GHz, it has been demonstrated that TS38.901 RMa LoS model is an accurate large-scale pathloss model and it is agreed that TS38.901 RMa LoS pathloss model is adopted to be used for link budget evaluation at least for Scenario-A. + +Editor Note: FFS pathloss model and Scenario-B. + +#### Pathloss and channel model for tunnel deployments + +If $D_{\text{RRH\_height}} > D_{\text{DUE\_height}}$ and assuming that there are no obstacles between the RRH and CPE, then LoS paths should always exist for the propagation inside the tunnel. Note that, different to open-space scenarios, contribution of the scattering and reflection paths in the received signal power are expected to be more significant in the tunnel propagation due to the impact of waveguiding effects. Nevertheless, since the beamforming is used in HST FR2 deployment, and in addition to the fact that the LoS path has shortest travel distance compared to scattering and reflection, the strong LoS path assumption should remain valid in the HST FR2 tunnel deployment scenario, and thus the LoS pathloss model can be used for the link budget analysis. + +TS38.901 RMa LoS model, which is considered in open-space link budget analysis, can be reused in tunnel scenario. On the other hand, it is also worth noting that RMa LoS model does not capture the effects of rich reflection and scattering that likely exist in the tunnel propagation. From this viewpoint, other pathloss model such as TS38.901 UMa LoS and UMi street canyon LoS channel model might be more relevant for link budget study in the tunnel scenario as those models somewhat included the impact of reflection and scattering propagation in the pathloss. + +As mentioned above, the LoS condition can be considered for most of the areas between the serving RRH and neighboring ones. However, there may be exception in the area under the serving RRH where the serving beam cannot provide coverage directly. Different to the open space scenarios, channel condition w.r.t. the serving RRH in its shadow area is likely NLoS in tunnel due to the rich of the diffuse reflection paths. Nevertheless, from the mobility performance perspective, the impact of such NLoS condition on the HST FR2 deployments may be minor. More specifically, the signal level of the NLoS paths may be rather low as the result of high-order reflections. In addition, the shadow area under the RRH is small in tunnel scenario, which is few meters from the RRH since $D_{\text{RRH\_height}}$ is close to $D_{\text{DUE\_height}}$ . For example, given the deployment parameters for single-track railway, the NLoS region could be within the radius of 5 meters from the BS, for which the train takes 50 ms to travel. This means that network may not be able to react timely to the measurement report, if available, for this NLoS area. Therefore, the impact of NLoS propagation under the RRH on the mobility performance, if exists, can be negligible. + +Ray-tracing simulation results conducted in RAN4 studies [R4-2219289] and [R4-2302152] demonstrated that pathloss model in tunnel might have similar characteristics compared to urban open space scenarios; and pathloss at locations under the Tx is lower than that in open-space scenario; and multi-path components (MPCs) extensively exist but delay spread is small making MPCs indistinguishable from each other. These observations confirm the analysis that LoS propagation model can be used in the tunnel. + +### 6.2.2 Channel modelling for performance requirements + +Based on WID as follows, RAN4 is tasked to further study the channel model for FR2 HST, where the key question needs to be answer: + +- Whether or not single-tap per RRH channel model is assumed in UL direction; and +- Whether single- or multi-tap model is assumed in DL direction. + +Compared with the FR1 counterpart, the major difference of having analog beamforming in FR2 should be considered in determining channel model for performance requirement. Depending on whether or not joint transmission is allowed + +for FR2 HST, it could be possible to have multiple taps from neighboring RRHs, while if only DPS is allowed single tap model should be employed. + +Furthermore, whether or not the single tap is accurate enough for a single TX-RX link in FR2 HST scenario has been studied. Specifically, a measurement-data-calibrated FR2 HST ray-tracing model is used to simulate various paths of LoS and reflected path for a practical railway scenario. As required by WID, the UE is mounted on top of the driver's cabin of the train in the simulation. And the traveling length is 2000 m, with a sampling distance of 20 m, thus making 200 snapshots (UE locations) be simulated. + +![Illustrative setup for FR2 HST ray-tracing simulation showing a train (UE) moving along a track with four RRHs (RRH1, RRH2, RRH3, RRH4) positioned at 500m intervals. The UE moving direction is indicated by a large blue arrow, and the entire length is 2000 m. The UE is mounted on top of the driver's cabin.](4b0f6b9fffe1f9b12f0db27b76e617ca_img.jpg) + +The diagram illustrates a 3D perspective view of a high-speed train (UE) on a railway track. The train is white with a red stripe. A blue circle on the front of the train is labeled 'UE (Initial position)'. A large blue arrow pointing along the track is labeled 'UE moving direction' and 'The entire length is 2000 m'. Four red circles representing RRHs are positioned along the track, labeled RRH4, RRH3, RRH2, and RRH1 from left to right. Horizontal distance lines indicate 500.00 m intervals between each RRH. Vertical dimension lines show a height of 20.00 m for the RRHs and 2.5 m for the train's height. + +Illustrative setup for FR2 HST ray-tracing simulation showing a train (UE) moving along a track with four RRHs (RRH1, RRH2, RRH3, RRH4) positioned at 500m intervals. The UE moving direction is indicated by a large blue arrow, and the entire length is 2000 m. The UE is mounted on top of the driver's cabin. + +**Figure 6.2.2-1 Illustrative of the setup for FR2 HST ray-tracing simulation** + +For each given UE location, the received signals from 4 RRHs are simulated by using the ray-tracing model. Numerically, it has been demonstrated that all simulated snapshots have the ratio of received non-first-tap power over total received power smaller than 0.01, or in other words, in all snapshots, the first tap can contain more than 99% of the energy, which validate the single-tap assumption from a single TX-RX link in FR2 HST. + +![Figure 6.2.2-2: CDF of the ratio of non-first-tap power over total power. The plot shows the Cumulative Distribution Function (CDF) on the y-axis (0 to 1) against the Ratio of Non-First-Tap Power over Total Power on the x-axis (logarithmic scale from 10^-10 to 10^0). Four curves are shown: RRH1 (solid blue), RRH2 (solid orange), RRH3 (solid yellow), and RRH4 (dashed purple). All curves show a sharp increase in CDF between 10^-5 and 10^-4, reaching near 1.0 by 10^-3. RRH4 has the lowest CDF for ratios between 10^-10 and 10^-5, while RRH1, RRH2, and RRH3 are nearly identical and higher than RRH4 in that range.](a289b64f80c6df506c0c55d553fc4496_img.jpg) + +Figure 6.2.2-2: CDF of the ratio of non-first-tap power over total power. The plot shows the Cumulative Distribution Function (CDF) on the y-axis (0 to 1) against the Ratio of Non-First-Tap Power over Total Power on the x-axis (logarithmic scale from 10^-10 to 10^0). Four curves are shown: RRH1 (solid blue), RRH2 (solid orange), RRH3 (solid yellow), and RRH4 (dashed purple). All curves show a sharp increase in CDF between 10^-5 and 10^-4, reaching near 1.0 by 10^-3. RRH4 has the lowest CDF for ratios between 10^-10 and 10^-5, while RRH1, RRH2, and RRH3 are nearly identical and higher than RRH4 in that range. + +**Figure 6.2.2-2 CDF of the ratio of non-first-tap power over total power** + +Based on measurement-data-calibrated ray-tracing modeling at 28GHz for typical railway environment, it has been validated that the single-tap is accurate enough to represent a single TX-RX link for FR2 HST. Therefore, it is agreed that for channel modelling for performance requirement, the single-tap can be assumed for a single TX-RX link at least for Scenario-A. + +Editor Note: FFS multi-tap models are needed for SFN and other scenarios and FFS channel model for Scenario-B. + +For channel modelling for performance requirement evaluation: + +- Single-tap can be assumed for a single TX-RX link at least for scenario 2 in table 5.1-1. + +RAN4 agreed that for both uplink and downlink the cosine of angle $\theta(t)$ used in Doppler shift in channel model is applied. This applies for: + +- A particular uni-directional deployment scenario; and +- A particular bi-directional deployment scenario. + +The single tap propagation model can be assumed for each single Tx-Rx link for both scenario 2 and scenario 4 in table 5.1-1 + +RAN4 agreed that the uplink and downlink channel model in uni-directional deployments one channel model (either toward to serving beam or away from serving beam) is applied for demodulation requirement even if UE can travel in two directions in practice. + +RAN4 will use the following HST-DPS channel model as a starting point for FR2 HST uni-directional RRH deployment: + +- UE is moving towards the serving beam +- The cosine of angle $\theta(t)$ used in Doppler shift $f_s(t) = f_d \cos \theta(t)$ is provided as + +$$- \cos \theta(t) = \frac{D_{s\_offset} + D_s - vt}{\sqrt{D_{min}^2 + (D_{s\_offset} + D_s - vt)^2}}, \quad 0 < t \leq \frac{D_s}{v} \quad (1)$$ + +$$- \cos \theta(t) = \cos \theta \left( t \bmod \left( \frac{D_s}{v} \right) \right), \quad t > D_s/v \quad (2)$$ + +Where: + +$$- 0 \leq D_{s\_offset} < D_s \quad (3)$$ + +The $D_{s\_offset}$ value for introducing performance requirements is 10m and 100m for Scenarios A and B, respectively. The $D_{s\_offset}$ value has no restriction concerning deployments and the value is only used for developing the demodulation requirements. The $D_{s\_offset}$ is derived from the worst case based on analysis of deployment scenarios. Note, demodulation simulation assumptions should cover at least one Doppler shift jump region. + +RAN4 decided regarding the HST FR2 channel model in bi-directional deployment to use option 2 with DPS based channel model as starting point and based on this RAN4 agreed to use the following cosine values for the different schemes 2a – 2c below. Of the options RAN4 agreed to apply channel modelling as option 2a for FR2 HST Bi-directional RRH deployment: + +Option 2(a): To match Bi-directional deployment Scheme-1: UE connect to 2nd-nearest RRH): + +$$- \cos \theta(t) = \frac{D_s - vt}{\sqrt{D_{min}^2 + (D_s - vt)^2}}, \quad 0 < t \leq (0.5 * D_s)/v \quad (4)$$ + +$$- \cos \theta(t) = -\frac{vt}{\sqrt{D_{min}^2 + (vt)^2}}, \quad (0.5 * D_s)/v < t \leq D_s/v \quad (5)$$ + +$$- \cos \theta \left( t \bmod \left( \frac{D_s}{v} \right) \right), \quad t > D_s/v \quad (6)$$ + +Option 2(b): based on Scheme-2 for Bidirectional RRH Deployment: + +$$- \cos \theta(t) = \frac{-(D_s + vt)}{\sqrt{D_{min}^2 + (D_s + vt)^2}}, \quad 0 \leq t < D_{s\_offset}/v, \quad (7)$$ + +$$- \cos \theta(t) = \frac{D_s - vt}{\sqrt{D_{min}^2 + (D_s - vt)^2}}, \quad 0.5 * D_s/v \leq t < (D_s - D_{s\_offset})/v \quad (8)$$ + +$$- \cos \theta(t) = \frac{-vt}{\sqrt{D_{min}^2 + (-vt)^2}}, \quad (D_s - D_{s\_offset})/v \leq t < D_s/v \quad (9)$$ + +$$- \cos \theta(t) = \cos \theta(t \bmod(D_s/v)), \quad t > D_s/v \quad (10)$$ + +$$- D_{s\_offset} = 100m \text{ (The } D_{s\_offset} \text{ is derived from the worst case based on analysis of deployment scenarios)}$$ + +Option 2(c): based on Scheme-3 for Bidirectional RRH Deployment: + +$$- \cos \theta(t) = \frac{D_s - vt}{\sqrt{D_{min}^2 + (D_s - vt)^2}}, \quad 0 < t \leq A_{offset}/v \quad (11)$$ + +$$- \cos \theta(t) = -\frac{vt}{\sqrt{D_{min}^2 + (vt)^2}}, \quad A_{offset}/v < t \leq (0.5 * D_s)/v \quad (12)$$ + +$$- \cos \theta(t) = \frac{D_s - vt}{\sqrt{D_{min}^2 + (D_s - vt)^2}}, \quad (0.5 * D_s)/v < t \leq B_{offset}/v \quad (13)$$ + +$$- \cos \theta(t) = -\frac{vt}{\sqrt{D_{min}^2 + (vt)^2}}, \quad B_{offset}/v < t \leq (D_s)/v \quad (14)$$ + +$$- \cos \theta \left( t \bmod \left( \frac{D_s}{v} \right) \right), \quad t > D_s/v \quad (15)$$ + +$$- A_{offset} < (0.5 * D_s) < B_{offset} < D_s \quad (16)$$ + +RAN4 agrees to use DPS channel model for both uni-directional and bi-directional for performance requirements. + +It was agreed that TCI switching belongs RRM scope, and there is no need to model and consider this in demodulation requirements. Demodulation requirements will not verify the PDSCH performance during TCI switching period. No propagation delay and delay jump modelling in channel model for DL PDSCH demodulation. + +## 6.3 FR2 Feasibility Evaluation + +RAN4 perform feasibility study on FR2 HST scenario, by at least considering following aspects: + +- 1) The feasibility of a deployment based the beam dwelling time and measurement period framework: + - a) How many beams/SSBs per RRH can be deployed (given other deployment parameters such as $D_{\min}$ , $D_s$ , speed etc) while maintain mobility performance with FR2 BM mechanism?; and + - b) How much beam refinement is needed to achieve coverage and mobility? + - How much beam overlapping area is needed (given other deployment parameters such as $D_{\min}$ , $D_s$ , speed etc.) to ensure beam refinement procedure can be executed successfully? +- 2) Study throughput performance and mobility performance: + - a) More number of analogue beams and sharper beam may provide better link budget performance but more challenging on mobility performance. +- 3) Receive timing difference. +- 4) Maximum supported Doppler shift for both UL and DL and maximum supported UE speed. + +Other feasibility study is not precluded. + +For evaluating the maximum supported speed following numerology will be considered: + +- For FR2 HST evaluations and possible performance requirements definition, RAN4 only consider 120kHz SCS as baseline assumption. + +### 6.3.1 Idle/inactive mode + +### 6.3.2 Connected mode + +#### 6.3.2.1 Number of Rx beams + +RAN4 discussed the Rx beam number for RRM requirements definition and agreed to define two sets of enhanced RRM requirements in terms of the number of Rx beams (i.e., Rx beam sweeping scaling factor) per UE: + +- Set 1: 2 Rx beams +- Set 2: 6 Rx beams + +Set 1 is more relevant to the deployments where the RRHs are located next to the railway track, e.g., like in Scenario-A with $D_{\min} = 10\text{m}$ . Whereas, Set 2 can be used in the scenarios where RRHs are further away from the track, e.g., like Scenario-B with $D_{\min} = 150\text{m}$ . + +The analysis below is based on the system-level simulations carried out following the assumptions and parameters from Table 6.3.8.1-1. + +It was found out that in priority scenarios additional beams oriented upwards (i.e., up from the horizontal plane parallel to the railways track) do not provide meaningful performance gains. Therefore, the analysis below is focusing only on the beams with different orientations in the horizontal plane. + +Following the antenna panel parameters from the Section 6.1, the half-power width for the RRH boresight beam is around 12.6 degrees (8x8 panel). Whereas the half-power width of the UE boresight beam is around 26 degrees (4x4 panel). + +##### 6.3.2.1.1 Scenario-A + +The considered deployment is uni-directional Scenario-A where the train is traveling in the direction opposite to the serving beam as presented in Figure 6.3.2.1.1-1. It is assumed that the RRH panel is oriented towards the projection of the following RRH on the railway track, and only one beam is used per RRH panel. The UE panel boresight is parallel to the railway track. + +![Figure 6.3.2.1.1-1: HST FR2 Uni-directional deployment diagram. The diagram shows a railway track with three RRH panels (RRH1, RRH2, RRH3) and a CPE (CPE) on a train. RRH1 is at position 3850, RRH2 at 4550, and RRH3 at 5250. The CPE is moving towards RRH3, as indicated by a black arrow labeled 'Train movement'. Each RRH has a blue beam pointing towards the next RRH. An inset box titled 'CPE beam orientation' shows a diagram of the CPE with beams at 70°, 90° (boresight), and 110°.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +Figure 6.3.2.1.1-1: HST FR2 Uni-directional deployment diagram. The diagram shows a railway track with three RRH panels (RRH1, RRH2, RRH3) and a CPE (CPE) on a train. RRH1 is at position 3850, RRH2 at 4550, and RRH3 at 5250. The CPE is moving towards RRH3, as indicated by a black arrow labeled 'Train movement'. Each RRH has a blue beam pointing towards the next RRH. An inset box titled 'CPE beam orientation' shows a diagram of the CPE with beams at 70°, 90° (boresight), and 110°. + +**Figure 6.3.2.1.1-1: HST FR2 Uni-directional deployment, the train is moving towards the serving beam.** + +In Figure 6.3.2.1.1-2, simulation results (cumulative distribution function of SINR) are shown when only one Rx beam with fixed orientation is configured at the UE. It can be seen that the beam co-oriented with the UE panel's boresight (RxBeams1-90) provides the highest SINR. + +![Figure 6.3.2.1.1-2: CDF of SINR for different orientations of a single Rx beam. The graph plots the Cumulative Distribution Function (CDF) on the y-axis (0 to 1) against the SINR [dB] on the x-axis (-10 to 60). Multiple curves are shown for different Rx beam orientations: RxBeams1-60 (solid blue), RxBeams1-70 (solid orange), RxBeams1-75 (solid yellow), RxBeams1-80 (solid purple), RxBeams1-85 (solid green), RxBeams1-90 (solid light blue), RxBeams1-100 (dashed red), RxBeams1-120 (dashed blue), and RxBeams1-150 (dashed orange). The RxBeams1-90 curve is the leftmost, indicating the highest SINR performance, reaching a CDF of 1 at approximately 40 dB.](b07036873d6afa06a24ea45f9f323810_img.jpg) + +Figure 6.3.2.1.1-2: CDF of SINR for different orientations of a single Rx beam. The graph plots the Cumulative Distribution Function (CDF) on the y-axis (0 to 1) against the SINR [dB] on the x-axis (-10 to 60). Multiple curves are shown for different Rx beam orientations: RxBeams1-60 (solid blue), RxBeams1-70 (solid orange), RxBeams1-75 (solid yellow), RxBeams1-80 (solid purple), RxBeams1-85 (solid green), RxBeams1-90 (solid light blue), RxBeams1-100 (dashed red), RxBeams1-120 (dashed blue), and RxBeams1-150 (dashed orange). The RxBeams1-90 curve is the leftmost, indicating the highest SINR performance, reaching a CDF of 1 at approximately 40 dB. + +**Figure 6.3.2.1.1-2: CDF of SINR for different orientations of a single Rx beam.** + +Next, a scenario where multiple Rx beams can be used at the UE side is considered. In Figure 6.3.2.1.1-3, it is demonstrated that no gain from using more than one boresight beam (i.e., the beam 90) is observed even if all of the additional beams are oriented towards the RRH. + +![Figure 6.3.2.1.1-3: CDF of SINR for different number of Rx beams. The plot shows the Cumulative Distribution Function (CDF) of SINR [dB] on the x-axis (ranging from 20 to 60) against the CDF on the y-axis (ranging from 0 to 1). Four curves are shown: RxBeams1-90 (blue), RxBeams2-9080 (orange), RxBeams3-908070 (yellow), and RxBeams4-90807060 (purple). All curves are nearly identical, starting at 0 CDF at 20 dB and reaching 1 CDF at 60 dB.](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +Figure 6.3.2.1.1-3: CDF of SINR for different number of Rx beams. The plot shows the Cumulative Distribution Function (CDF) of SINR [dB] on the x-axis (ranging from 20 to 60) against the CDF on the y-axis (ranging from 0 to 1). Four curves are shown: RxBeams1-90 (blue), RxBeams2-9080 (orange), RxBeams3-908070 (yellow), and RxBeams4-90807060 (purple). All curves are nearly identical, starting at 0 CDF at 20 dB and reaching 1 CDF at 60 dB. + +Figure 6.3.2.1.1-3: CDF of SINR for different number of Rx beams. + +##### 6.3.2.1.2 Scenario-B + +A scheme of uni-directional deployments in HST FR2 Scenario-B is shown in Figure 6.3.2.1.2-1. We also indicate the orientation of Tx beams at RRH and Rx beams at CPE used in the simulations. + +![Figure 6.3.2.1.2-1: The schemes of uni- and bi-directional deployments in HST FR2 Scenario-B with the orientation of Tx and Rx beams. The diagram is divided into three parts. The top-left part shows 'RRH beam orientation' with a panel boresight at 0°, and two other beams at -20° and -40°. The top-right part shows 'CPE beam orientation' with beams at 70°, 90°, and 110°. The bottom part shows a 'Uni-directional deployment' scheme with three RRHs (RRH1, RRH2, RRH3) and a CPE. RRH1 is at 3850, RRH2 at 4550, and RRH3 at 5250. The CPE is located between RRH2 and RRH3, with an arrow indicating 'Train movement' to the right.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Figure 6.3.2.1.2-1: The schemes of uni- and bi-directional deployments in HST FR2 Scenario-B with the orientation of Tx and Rx beams. The diagram is divided into three parts. The top-left part shows 'RRH beam orientation' with a panel boresight at 0°, and two other beams at -20° and -40°. The top-right part shows 'CPE beam orientation' with beams at 70°, 90°, and 110°. The bottom part shows a 'Uni-directional deployment' scheme with three RRHs (RRH1, RRH2, RRH3) and a CPE. RRH1 is at 3850, RRH2 at 4550, and RRH3 at 5250. The CPE is located between RRH2 and RRH3, with an arrow indicating 'Train movement' to the right. + +Figure 6.3.2.1.2-1: The schemes of uni- and bi-directional deployments in HST FR2 Scenario-B with the orientation of Tx and Rx beams. + +From Figure 6.3.2.1.2-2 it can be noticed that increasing the number of Tx beams on RRH side provides very minor gain in HST FR2 uni-directional Scenario-B if only one Rx beam is used. Indeed, in this case, the CPE stays mostly in the coverage area of the boresight Tx beam, and additional beams are not used much. + +![SINR CDF plot for different Tx beam configurations.](85b10db535b22e64c7d37f362705ddbf_img.jpg) + +The figure is a line graph showing the SINR CDF for three different Tx beam configurations. The x-axis is labeled 'SINR [dB]' and ranges from 10 to 50. The y-axis is labeled 'CDF' and ranges from 0 to 1. The legend indicates three series: RRHBeams1, RxBeams1-90 (blue line); RRHBeams2, RxBeams1-90 (orange line); and RRHBeams4, RxBeams1-90 (yellow line). All three curves are nearly perfectly overlaid, showing a sharp increase in CDF between 25 dB and 45 dB, reaching a CDF of 1 at approximately 48 dB. + +| SINR [dB] | RRHBeams1, RxBeams1-90 (CDF) | RRHBeams2, RxBeams1-90 (CDF) | RRHBeams4, RxBeams1-90 (CDF) | +|-----------|------------------------------|------------------------------|------------------------------| +| 10 | 0.00 | 0.00 | 0.00 | +| 15 | 0.00 | 0.00 | 0.00 | +| 20 | 0.00 | 0.00 | 0.00 | +| 25 | 0.02 | 0.02 | 0.02 | +| 30 | 0.15 | 0.15 | 0.15 | +| 35 | 0.45 | 0.45 | 0.45 | +| 40 | 0.80 | 0.80 | 0.80 | +| 45 | 0.95 | 0.95 | 0.95 | +| 50 | 1.00 | 1.00 | 1.00 | + +SINR CDF plot for different Tx beam configurations. + +**Figure 6.3.2.1.2-2: SINR CDF in uni-directional Scenario-B for different number of Tx beams when only one Rx beam parallel to the track is used.** + +Firstly, the scenario where one boresight Tx beam is used at the RRH and one Rx beam is used at the UE is considered. Different UE Rx beams directions are compared in Figure 6.3.2.1.2-3. The results demonstrate that Rx beam orientation has a significant impact on performance. For example, wrong orientation of Rx beam (e.g., to the other side from the RRH) results in the significant loss of performance. It was also found that Rx beam oriented 10-15 degrees from the UE panel boresight towards the RRH (i.e., RxBeams1-80, RxBeams1-75) provide best performance in Scenario-B. + +![Figure 6.3.2.1.2-3: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B for different orientations of Rx beams.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +The figure consists of two vertically stacked plots. The top plot shows L1-RSRP [dB] on the y-axis (ranging from -105 to -60) against X-Coordinate [m] on the x-axis (ranging from 6600 to 8400). It displays multiple colored lines representing different Rx beam orientations: RxBeams1-60, RxBeams1-70, RxBeams1-75, RxBeams1-80, RxBeams1-85, RxBeams1-90, RxBeams1-100, RxBeams1-120, and RxBeams1-150. The bottom plot shows the CDF on the y-axis (ranging from 0 to 1) against SINR [dB] on the x-axis (ranging from 0 to 50). It displays the same set of Rx beam orientations, with solid lines for RxBeams1-60 through RxBeams1-90, and dashed lines for RxBeams1-100, RxBeams1-120, and RxBeams1-150. + +Figure 6.3.2.1.2-3: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B for different orientations of Rx beams. + +**Figure 6.3.2.1.2-3: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B for different orientations of Rx beams.** + +Next, it is studied how the performance depends on the orientation of one Rx beam when multiple Tx beams are used. These results are shown in Figure 6.3.2.1.2-4. Like in Figure 6.3.2.1.2-2, one can observe that adding more Tx beams when only one Rx beam parallel to the track is used does not provide significant gain. However, if we orient the Rx beam more towards the RRH, then in the areas next to the RRH the received signal power can be significantly increased. + +![Figure 6.3.2.1.2-4: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B with multiple Tx beams and for different orientations of Rx beam.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +The figure consists of two vertically stacked plots. The top plot shows L1-RSRP [dB] on the y-axis (ranging from -85 to -55) against X-Coordinate [m] on the x-axis (ranging from 6600 to 8400). It displays eight traces representing different combinations of Tx beams (1, 2, or 4) and Rx beam orientations (60, 70, or 90 degrees). The traces show significant fluctuations in signal strength across the coordinate range. The bottom plot shows the CDF on the y-axis (ranging from 0 to 1) against SINR [dB] on the x-axis (ranging from 0 to 60). It displays the same eight traces, showing the cumulative distribution of the SINR. The curves for 4RRHBears with 90-degree Rx beam orientation (green and light blue) show the highest SINR values, reaching a CDF of 1 around 50 dB. The curves for 1RRHBear with 90-degree Rx beam orientation (blue) show the lowest SINR values, reaching a CDF of 1 around 55 dB. + +Figure 6.3.2.1.2-4: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B with multiple Tx beams and for different orientations of Rx beam. + +**Figure 6.3.2.1.2-4: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B with multiple Tx beams and for different orientations of Rx beam.** + +Finally, the scenario where multiple (four) Tx and multiple (up to four) Rx beams are configured together is analyzed (Figure 6.3.2.1.2-5). It is shown that the correct choice of Rx beams improves the received signal strength in the areas where the coverage of additional Tx beams is present. The median value of the SINR can be increased for around 4 dB. One can also notice that the use of 2 and 3 Rx beams provide significant gains, whereas the gain from more additional beams (e.g., 4 in total) is not significant. + +![Figure 6.3.2.1.2-5: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B with four Tx and multiple Rx beams. The top plot shows L1-RSRP [dB] vs X-Coordinate [m] for four Rx beam configurations: RxBeams1-90, RxBeams2-9080, RxBeams3-908070, and RxBeams4-90807060. The bottom plot shows the CDF vs SINR [dB] for the same four Rx beam configurations.](4dfe30ac5a87d018364a0ac42ea533fe_img.jpg) + +The figure consists of two vertically stacked plots. The top plot displays L1-RSRP [dB] on the y-axis (ranging from -80 to -62) against X-Coordinate [m] on the x-axis (ranging from 6600 to 8400). It shows four fluctuating lines representing different Rx beam configurations: RxBeams1-90 (blue), RxBeams2-9080 (orange), RxBeams3-908070 (yellow), and RxBeams4-90807060 (purple). The bottom plot displays the CDF on the y-axis (ranging from 0 to 1) against SINR [dB] on the x-axis (ranging from 10 to 60). It shows four S-shaped curves for the same Rx beam configurations, with RxBeams1-90 (blue) reaching a CDF of 1 at a lower SINR value compared to the others. + +Figure 6.3.2.1.2-5: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B with four Tx and multiple Rx beams. The top plot shows L1-RSRP [dB] vs X-Coordinate [m] for four Rx beam configurations: RxBeams1-90, RxBeams2-9080, RxBeams3-908070, and RxBeams4-90807060. The bottom plot shows the CDF vs SINR [dB] for the same four Rx beam configurations. + +Figure 6.3.2.1.2-5: L1-RSRP traces of serving RRH (top) and SINR CDFs (bottom) in uni-directional Scenario-B with four Tx and multiple Rx beams. + +### 6.3.3 Link Performance and Throughput Performance + +Based on the evaluation parameters provided in clause 6.1 and channel modeling provided in clause 6.2, companies are provided evaluation results by examining the link performance and throughput performance. In the following sub-section, companies' evaluation results are provided for information, which are used as the technical basis to derive the conclusion. + +#### 6.3.3.1 Link Performance Evaluation from Samsung + +For Scenario-A, uni-directional and bi-directional deployment, Samsung provide the evaluation in the contributions R4-2110234 and R4-2113170 respectively. + +##### 6.3.3.1.1 Scenario-A, Uni-directional RRH Deployment + +As provided in clause 6.2 for the detailed simulation assumption and the detailed beam configuration in Table 6.3.3.1.1-1, it has been shown that with 1 beam per RRH panel and 1 beam per UE panel, the link budget performance is satisfactory, in terms of at least ~30dB margin over FR2 PC4 REFSENS requirement and at least ~21dB margin over FR2 PC4 spherical coverage requirement, as illustrated in following figure. Even considering 31dBm for TX power is a + +bit optimistic assumption for 8x8 panel configuration (e.g., with per element $P_{out} = 12\text{dBm}$ and 3dB polarization gain, 8x8 panel can achieve $12 + 10\log(64) + 3 = 34\text{dBm}$ without considering any implementation margin), the cellular coverage should still be satisfactory with implementation margin considered. + +![Figure 6.3.3.1.1-1: RX power without UE RX beamforming, Scenario-A, Uni-directional. The graph shows RX Power (dBm) on the y-axis (from -130 to -50) versus Location (meter) on the x-axis (from 0 to 2000). Three curves are plotted: RRH-1, beam-1 (black), RRH-2, beam-1 (red), and CPE-PC4 REFSSENS -94dBm@100M (blue horizontal line). The RRH-1 curve starts at -50 dBm at 0m and decreases to about -85 dBm at 2000m. The RRH-2 curve starts at -95 dBm at 0m, peaks at -85 dBm at 600m, and then drops sharply to -125 dBm at 700m. The RRH-3 and RRH-4 locations are marked at 1400m and 2000m respectively.](5bf611979ab0126ebd219a1c6eda6b1e_img.jpg) + +Figure 6.3.3.1.1-1: RX power without UE RX beamforming, Scenario-A, Uni-directional. The graph shows RX Power (dBm) on the y-axis (from -130 to -50) versus Location (meter) on the x-axis (from 0 to 2000). Three curves are plotted: RRH-1, beam-1 (black), RRH-2, beam-1 (red), and CPE-PC4 REFSSENS -94dBm@100M (blue horizontal line). The RRH-1 curve starts at -50 dBm at 0m and decreases to about -85 dBm at 2000m. The RRH-2 curve starts at -95 dBm at 0m, peaks at -85 dBm at 600m, and then drops sharply to -125 dBm at 700m. The RRH-3 and RRH-4 locations are marked at 1400m and 2000m respectively. + +**Figure 6.3.3.1.1-1 RX power without UE RX beamforming, Scenario-A, Uni-directional** + +Next, we take UE RX beamforming gain into account, and assume 1 beam per panel (which is existing agreement in R4-2106100). For simplicity, it is assumed that UE boresight direction is opposite to RRH boresight direction (i.e., the largest UE beamforming gain is achieved when UE is located at the projection point of the neighboring RRH on the railway). It is shown in the following figure, with UE RX beamforming gain into account, the received signal power after RX beamforming is no less than $-50\text{dBm}$ even for the nearest coverage point (which is corresponding to least RX beamforming gain around 15dB), which also should be regarded as satisfactory link performance. + +![Figure 6.3.3.1.1-2: RX power with UE RX beamforming, Scenario-A, Uni-directional. The graph shows RX Power (dBm) on the y-axis (from -130 to -40) versus Location (meter) on the x-axis (from 0 to 2000). Two curves are plotted: RRH-1beam-1, UEbeam1 (black) and RRH-2beam-1, UEbeam1 (red). The RRH-1 curve starts at -40 dBm at 0m and decreases to about -60 dBm at 2000m. The RRH-2 curve starts at -80 dBm at 0m, peaks at -70 dBm at 600m, and then drops sharply to -125 dBm at 700m. The RRH-1, RRH-2, RRH-3, and RRH-4 locations are marked at 0m, 700m, 1400m, and 2000m respectively.](5e16d3613b74558acc74ff6d7fd75fa9_img.jpg) + +Figure 6.3.3.1.1-2: RX power with UE RX beamforming, Scenario-A, Uni-directional. The graph shows RX Power (dBm) on the y-axis (from -130 to -40) versus Location (meter) on the x-axis (from 0 to 2000). Two curves are plotted: RRH-1beam-1, UEbeam1 (black) and RRH-2beam-1, UEbeam1 (red). The RRH-1 curve starts at -40 dBm at 0m and decreases to about -60 dBm at 2000m. The RRH-2 curve starts at -80 dBm at 0m, peaks at -70 dBm at 600m, and then drops sharply to -125 dBm at 700m. The RRH-1, RRH-2, RRH-3, and RRH-4 locations are marked at 0m, 700m, 1400m, and 2000m respectively. + +**Figure 6.3.3.1.1-2 RX power with UE RX beamforming, Scenario-A, Uni-directional** + +The evaluation and analysis above is based on the parameters provided in clause 6.1, while some of additional used assumptions are summarized in the below Table: + +**Table 6.3.3.1.1-1 Additional Assumptions for Uni-directional RRH Deployment Link Performance Evaluation** + +| Parameter | Value | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Channel parameters | | +| Carrier frequency | 30 GHz | +| Propagation model | RMa LoS | +| RRH parameters | | +| RRH Tx Power | 31 dBm | +| RRH antenna array model | $[M_g, N_g, M, N, P]=[1, 1, 8, 8, 2]$ | +| RRH panel orientation | Option-1: RRH panel boresight pointed to the railway at the distance of $D_s$ (projection of the neighboring RRH on the railway)
- Azimuth angle: 0.8 degree
- Down-tilting: 1.2 degree | +| Number of RRH panels per RRH sites | 1 (i.e., uni-directional) | +| Number of Analog Beams per RRH | 1 | +| Analog Beam orientation | boresight direction as RRH panel orientation | +| UE parameters | | +| UE antenna array model | $[M_g, N_g, M, N, P]=[1, 1, 4, 4, 2]$
5dBi per element antenna gain | +| UE panel orientation | Direction is opposite to RRH boresight direction
(Note: RRH boresight direction for Scenario-A: Azimuth angle: 0.8 degree
Down-tilting: 1.2 degree) | +| Number of Beams per UE panel | 1 | + +##### 6.3.3.1.2 Scenario-A, Bi-directional RRH Deployment + +Two candidate schemes for Bi-directional deployment for Scenario-A are discussed, and the illustration of two scheme are captured in WF R4-2106100 for information, i.e., + +- Scheme-1: Connecting to 2nd-Nearest RRH; +- Scheme-2: Connecting to Nearest RRH except Coverage Hole. + +![Diagram of Scheme-1: Connecting to 2nd-Nearest RRH. It shows three RRH panels (RRH1, RRH2, RRH3) spaced at distance Ds. A UE is shown moving from left to right. The UE connects to RRH1 at 0Ds, then switches to RRH2 at 0.5Ds, then to RRH3 at 1.5Ds, and finally to RRH2 again at 2Ds. The minimum distance from the RRH panels to the UE is Dmin.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +Diagram of Scheme-1: Connecting to 2nd-Nearest RRH. It shows three RRH panels (RRH1, RRH2, RRH3) spaced at distance Ds. A UE is shown moving from left to right. The UE connects to RRH1 at 0Ds, then switches to RRH2 at 0.5Ds, then to RRH3 at 1.5Ds, and finally to RRH2 again at 2Ds. The minimum distance from the RRH panels to the UE is Dmin. + +Scheme-1: Connecting to 2nd-Nearest RRH + +![Diagram of Scheme-2: Connecting to Nearest RRH except Coverage Hole. It shows three RRH panels (RRH1, RRH2, RRH3) spaced at distance Ds. A UE is shown moving from left to right. The UE connects to RRH1 at 0Ds, then switches to RRH2 at 0.5Ds, then to RRH3 at 1.5Ds, and finally to RRH2 again at 2Ds. The minimum distance from the RRH panels to the UE is Dmin. The diagram also shows the UE panel switch points at 0Ds, 0.5Ds, 1.5Ds, and 2Ds.](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +Diagram of Scheme-2: Connecting to Nearest RRH except Coverage Hole. It shows three RRH panels (RRH1, RRH2, RRH3) spaced at distance Ds. A UE is shown moving from left to right. The UE connects to RRH1 at 0Ds, then switches to RRH2 at 0.5Ds, then to RRH3 at 1.5Ds, and finally to RRH2 again at 2Ds. The minimum distance from the RRH panels to the UE is Dmin. The diagram also shows the UE panel switch points at 0Ds, 0.5Ds, 1.5Ds, and 2Ds. + +Scheme-2: Connecting to Nearest RRH except Coverage Hole + +**Figure 6.3.3.1.2-1 Illustration of Scheme-1 and 2 for bi-directional deployment** + +Accordingly the link performance of scheme-1 and scheme-2 are provided in the following two figures respectively. + +![Figure 6.3.3.1.2-2: RX power with UE RX beamforming for Scheme-1, Scenario-A, Bi-directional. The graph plots Rx Power (dBm) on the y-axis (ranging from -130 to -50) against Location (meter) on the x-axis (ranging from 0 to 2000). The plot title is 'RxPower w UE beamforming [RRH M=8 N=8 beamtheta=0deg beamphi=0deg]'. Vertical blue lines mark the positions of RRH1, RRH2, RRH3, and RRH4. Horizontal brackets indicate distances of Ds/2 between RRHs. Small black arrows labeled 'p1' and 'p2' indicate UE panel orientations. The legend includes: RRH2p2beam1,UEp1 (blue line); RRH1p1beam1,UEp2 (black line); RRH3p2beam1,UEp1 (cyan line); RRH2p1beam1,UEp2 (red line); RRH4p2beam1,UEp1 (green line); and RRH3p1beam1,UEp2 (yellow line). The curves show periodic power peaks as the UE moves past each RRH.](b9d879f357d5f15fac9ea8585b87d0a2_img.jpg) + +Figure 6.3.3.1.2-2: RX power with UE RX beamforming for Scheme-1, Scenario-A, Bi-directional. The graph plots Rx Power (dBm) on the y-axis (ranging from -130 to -50) against Location (meter) on the x-axis (ranging from 0 to 2000). The plot title is 'RxPower w UE beamforming [RRH M=8 N=8 beamtheta=0deg beamphi=0deg]'. Vertical blue lines mark the positions of RRH1, RRH2, RRH3, and RRH4. Horizontal brackets indicate distances of Ds/2 between RRHs. Small black arrows labeled 'p1' and 'p2' indicate UE panel orientations. The legend includes: RRH2p2beam1,UEp1 (blue line); RRH1p1beam1,UEp2 (black line); RRH3p2beam1,UEp1 (cyan line); RRH2p1beam1,UEp2 (red line); RRH4p2beam1,UEp1 (green line); and RRH3p1beam1,UEp2 (yellow line). The curves show periodic power peaks as the UE moves past each RRH. + +**Figure 6.3.3.1.2-2 RX power with UE RX beamforming for Scheme-1, Scenario-A, Bi-directional** + +![Figure 6.3.3.1.2-3: RX power with UE RX beamforming for Scheme-2, Scenario-A, Bi-directional. The graph plots Rx Power (dBm) on the y-axis (ranging from -90 to -30) against Location (meter) on the x-axis (ranging from 0 to 2000). The plot title is 'RxPower w UE beamforming [RRH M=8 N=8 beamtheta=0 -1.3deg beamphi=0 -0.8deg]'. Vertical blue lines mark RRH2 and RRH3. Brackets indicate Ds/2 spacing. A text label 'UE Rx panel switch' points to a transition point between panel p2 and p1. The legend includes: RRH1p1b1,UEp2 (black line); RRH2p2b1,UEp1 (blue line); RRH1p1b2,UEp2 (black line); RRH2p1b1,UEp2 (red line); RRH3p2b1,UEp1 (cyan line); and RRH1p1b2,UEp2 (red line). The power curves show sharp transitions corresponding to beam and panel switching.](d94a0100320109c1b9cd75c1054c7b95_img.jpg) + +Figure 6.3.3.1.2-3: RX power with UE RX beamforming for Scheme-2, Scenario-A, Bi-directional. The graph plots Rx Power (dBm) on the y-axis (ranging from -90 to -30) against Location (meter) on the x-axis (ranging from 0 to 2000). The plot title is 'RxPower w UE beamforming [RRH M=8 N=8 beamtheta=0 -1.3deg beamphi=0 -0.8deg]'. Vertical blue lines mark RRH2 and RRH3. Brackets indicate Ds/2 spacing. A text label 'UE Rx panel switch' points to a transition point between panel p2 and p1. The legend includes: RRH1p1b1,UEp2 (black line); RRH2p2b1,UEp1 (blue line); RRH1p1b2,UEp2 (black line); RRH2p1b1,UEp2 (red line); RRH3p2b1,UEp1 (cyan line); and RRH1p1b2,UEp2 (red line). The power curves show sharp transitions corresponding to beam and panel switching. + +**Figure 6.3.3.1.2-3 RX power with UE RX beamforming for Scheme-2, Scenario-A, Bi-directional** + +The evaluation and analysis above is based on the parameters provided in clause 6.1, while some of additional used assumptions and the detailed beam configuration in Table 6.3.3.1.2-1 are summarized in the below Table: + +**Table 6.3.3.1.2-1 Additional Assumptions for Bi-directional RRH Deployment Link Performance Evaluation** + +| Parameter | Value | +|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Channel parameters | | +| Carrier frequency | 30 GHz | +| Propagation model | RMa LoS | +| RRH parameters | | +| RRH Tx Power | 31 dBm | +| RRH antenna array model | [Mg, Ng, M, N, P]=[1, 1, 8, 8, 2] | +| RRH panel orientation | Option-1: RRH panel boresight pointed to the railway in the middle point between 2 RRHs
Scenario-A: Azimuth angle: 1.6 degree
Down-titling: 2.5 degree | +| Number of RRH panels per RRH sites | 2 (i.e., Bi-directional) | +| Number of Analog Beams per RRH | 1 | +| Analog Beam orientation | boresight direction as RRH panel orientation | +| UE parameters | | +| UE antenna array model | [Mg, Ng, M, N, P]=[1, 1, 4, 4, 2]
5dBi per element antenna gain | +| UE panel orientation | Direction is opposite to RRH boresight direction
(Note: RRH boresight direction for Scenario-A: Azimuth angle: 1.6 degree Down-titling: 2.5 degree) | +| Number of Beams per UE panel | 1 | + +##### 6.3.3.1.3 Scenario-B, Uni-directional RRH Deployment + +*Editor Notes: TBA.* + +##### 6.3.3.1.4 Scenario-B, Bi-directional RRH Deployment + +*Editor Notes: TBA.* + +#### 6.3.3.2 Link performance Evaluation from Huawei + +##### 6.3.3.2.1 Scenario A + +For Scenario-A, uni-directional and bi-directional deployment, Huawei provide the evaluation in the contributions R4-2119021 based on simulation assumption as shown in clause 6.1 and Table 6.3.3.2.1-1. + +**Table 6.3.3.2.1-1 Simulation assumption for Scenario-A** + +| Parameter | Value | +|-------------------|--------------------------------------------------------------------| +| Carrier frequency | 30GHz | +| Ds | 700m | +| Dmin | 10m | +| RRH Tx power | 47dBm | +| RRH height | 15m | +| RRH antenna array | [Mg, Ng, M, N, P]=[1, 1, 8, 8, 2] | +| Path Loss | RMa LoS | +| UE antenna height | 5m | +| UE antenna array | [Mg, Ng, M, N, P]=[1, 1, 4, 4, 2] | +| UE noise figure | 10dB | +| ILs | 13 dB | +| SNR | 18.6dB (i.e. FR2 Test 2-6, 64QAM CR=0.43 and Rank2 in TS 38.101-4) | + +###### 6.3.3.2.1.1 Scenario A, Bi-directional + +There are two schemes for Bi-directional deployment. Considering very small Dmin, the angle between RRH-UE line and the railway can be negligible, so only Scheme-1 is for further analysis. + +![Figure 6.3.3.2.1.1-1: Scheme-1 for Bi-directional deployment. The diagram shows three RRH panels (RRH1, RRH2, RRH3) and four UE panels (UE-panel1, UE-panel2, UE-panel3, UE-panel4) along a railway. RRH panels are at distance Ds from the railway. UE panels are at distance Dmin from the railway. The diagram illustrates the beam coverage and switching points for the UE panels. The switching points are labeled: UE panel switch 0s, UE panel switch 0.50s, UE panel switch Ds, UE panel switch 1.50s, and UE panel switch 20s.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Figure 6.3.3.2.1.1-1: Scheme-1 for Bi-directional deployment. The diagram shows three RRH panels (RRH1, RRH2, RRH3) and four UE panels (UE-panel1, UE-panel2, UE-panel3, UE-panel4) along a railway. RRH panels are at distance Ds from the railway. UE panels are at distance Dmin from the railway. The diagram illustrates the beam coverage and switching points for the UE panels. The switching points are labeled: UE panel switch 0s, UE panel switch 0.50s, UE panel switch Ds, UE panel switch 1.50s, and UE panel switch 20s. + +Figure 6.3.3.2.1.1-1 Scheme-1 for Bi-directional deployment + +For Scheme-1, 1 beam per RRH panel and 6 beam per UE panel is selected. Note that a single RRH panel or UE panel refers to the antenna configuration in Table 6.3.3.2.1-1. The RRH panel boresight is pointed to the railway at the distance of $D_s$ , the beam is pointed to the railway at the distance of $D_s$ . When the UE is at the distance of $D_s$ , the UE panel boresight is point to RRH panel boresight rightly. The link budget analysis is shown as Figure 6.3.3.2.1.1-2 below. + +![Figure 6.3.3.2.1.1-2: Link budget for Scheme-1. The graph shows the link budget remaining in dB versus distance in meters. The y-axis ranges from 20 to 34 dB, and the x-axis ranges from 0 to 1400 meters. The plot shows a periodic pattern of peaks and troughs, with peaks around 34 dB and troughs around 20 dB. The peaks occur at approximately 100m, 600m, 800m, and 1300m. The troughs occur at approximately 350m, 700m, and 1050m. The title of the graph is 'Bi-directional 4RRH 1beam 700/10 phi=[0]'.](010f64870d9b7d9e04dc4059b1cf5f45_img.jpg) + +Figure 6.3.3.2.1.1-2: Link budget for Scheme-1. The graph shows the link budget remaining in dB versus distance in meters. The y-axis ranges from 20 to 34 dB, and the x-axis ranges from 0 to 1400 meters. The plot shows a periodic pattern of peaks and troughs, with peaks around 34 dB and troughs around 20 dB. The peaks occur at approximately 100m, 600m, 800m, and 1300m. The troughs occur at approximately 350m, 700m, and 1050m. The title of the graph is 'Bi-directional 4RRH 1beam 700/10 phi=[0]'. + +Figure 6.3.3.2.1.1-2 Link budget for Scheme-1 + +For Scheme-1, the power of side-lobes for different beams change rapidly when UE is near to the RRH and the minimum time duration for the best beam with same beam index can be far less than 160 ms that is the L1-RSRP measurement period for HST FR2 scenario. It is a great challenge for the UE to ensure the performance not to degrade in such location. UE can use different strategy by implementation, such as select the best beam as per RSRP measurement result or directly switch the UE beam point to the main-lobe beam transmission from the next RRH. For the former one, the best beam may be unavailable with high probability once UE beam switching has been performed. + +###### 6.3.3.2.1.2 Scenario A, Uni-directional + +For Uni-directional deployment, 1 beam per RRH panel and 2 beam per UE panel is selected. Note that a single RRH panel or UE panel refers to the antenna configuration in Table 6.3.3.2.1-1. The RRH panel boresight is pointed to the railway at the distance of $D_s$ , the beam is pointed to 0 degrees. When the UE is at the distance of $D_s$ , the UE panel boresight is point to RRH panel boresight rightly. The link budget analysis is shown as Figure 6.3.3.2.1.2-1 below. + +![Figure 6.3.3.2.1.2-1: Link budget for Uni-directional deployment. The graph shows 'Link budget remaining/dB' on the y-axis (ranging from 20 to 34) versus 'Distance/m' on the x-axis (ranging from 0 to 1400). The plot title is 'Uni-directional 4RRH 1beam 700/10 phi=[0]'. The curve shows two main peaks around 600m and 1300m, with a sharp dip in between at approximately 700m. A small grey square marker is placed on the curve at approximately 650m distance and 25dB link budget.](bf30e154f82662d212f21fccdfa2980f_img.jpg) + +Figure 6.3.3.2.1.2-1: Link budget for Uni-directional deployment. The graph shows 'Link budget remaining/dB' on the y-axis (ranging from 20 to 34) versus 'Distance/m' on the x-axis (ranging from 0 to 1400). The plot title is 'Uni-directional 4RRH 1beam 700/10 phi=[0]'. The curve shows two main peaks around 600m and 1300m, with a sharp dip in between at approximately 700m. A small grey square marker is placed on the curve at approximately 650m distance and 25dB link budget. + +**Figure 6.3.3.2.1.2-1 Link budget for Uni-directional deployment** + +The link budget remaining and the minimum beam dwelling time for Uni-directional deployment is shown as Table 6.3.3.2.1.2-1 below. + +**Table 6.3.3.2.1.2-1 Link budget remaining and minimum beam dwelling time** + +| link budget remaining[dB] | minimum beam dwelling time[s] | Beam switching point[m] | +|---------------------------|-------------------------------|-------------------------| +| 19.2 | 7.20 | 50 | + +##### 6.3.3.2.2 Scenario B + +For Scenario-B, uni-directional and bi-directional deployment, Huawei provide the evaluation in the contributions R4-2119022 based on simulation assumption as shown in clause 6.1 and Table 6.3.3.2.2-1. + +**Table 6.3.3.2.2-1 Simulation assumption for Scenario-B** + +| Parameter | Value | +|-------------------|--------------------------------------------------------------------| +| Carrier frequency | 30GHz | +| Ds | 700m | +| Dmin | 150m | +| RRH Tx power | 47dBm | +| RRH height | 15m | +| RRH antenna array | [Mg, Ng, M, N, P]=[1, 1, 8, 8, 2] | +| Path Loss | RMa LoS | +| UE antenna height | 5m | +| UE antenna array | [Mg, Ng, M, N, P]=[1, 1, 4, 4, 2] | +| UE noise figure | 10dB | +| ILs | 13 dB | +| SNR | 18.6dB (i.e. FR2 Test 2-6, 64QAM CR=0.43 and Rank2 in TS 38.101-4) | + +###### 6.3.3.2.2.1 Scenario B, Bi-directional + +There are four schemes for Bi-directional deployment are for further analysis. + +![Figure 6.3.3.2.2.1-1 Candidate schemes for Bi-directional deployment. The figure contains three sub-diagrams: a) Scheme-1, b) Scheme-2, and c) Scheme-3. Schemes a) and b) show RRH panels (RRH1, RRH2, RRH3) and UE panels (UE-panel1, UE-panel2) connected via switches with distances Ds and Dmin. Schemes a), b), and c) show beam configurations (SSB#0, SSB#1, SSB#2, SSB#3) on a railway track.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +The diagram illustrates three candidate schemes for bi-directional deployment. Schemes a) and b) show a network of RRH panels (RRH1, RRH2, RRH3) and UE panels (UE-panel1, UE-panel2) connected via switches. Distances $D_s$ and $D_{min}$ are indicated. Schemes a), b), and c) show beam configurations (SSB#0, SSB#1, SSB#2, SSB#3) on a railway track. + +Figure 6.3.3.2.2.1-1 Candidate schemes for Bi-directional deployment. The figure contains three sub-diagrams: a) Scheme-1, b) Scheme-2, and c) Scheme-3. Schemes a) and b) show RRH panels (RRH1, RRH2, RRH3) and UE panels (UE-panel1, UE-panel2) connected via switches with distances Ds and Dmin. Schemes a), b), and c) show beam configurations (SSB#0, SSB#1, SSB#2, SSB#3) on a railway track. + +Figure 6.3.3.2.2.1-1 Candidate schemes for Bi-directional deployment + +For Scheme-1, 1 beam per RRH panel and 6 beam per UE panel is selected. Note that a single RRH panel or UE panel refers to the antenna configuration in Table 6.3.3.2.2-1. The RRH panel boresight is pointed to the railway at the distance of $D_s$ , the beam is pointed to the railway at the distance of $D_s$ . When the UE is at the distance of $D_s$ , the UE panel boresight is point to RRH panel boresight rightly. The link budget analysis is shown as Figure 6.3.3.2.2.1-2 below. + +![Line graph showing Link budget remaining/dB vs Distance/m for Bi-directional 4RRH 1beam 700/150 phi=[0]. The y-axis ranges from 14 to 22 dB, and the x-axis ranges from 0 to 1400 m. The curve shows periodic peaks and troughs, with peaks around 200m, 550m, 850m, and 1250m, and troughs around 350m and 1050m.](673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg) + +Bi-directional 4RRH 1beam 700/150 phi=[0] + +| Distance/m | Link budget remaining/dB | +|------------|--------------------------| +| 0 | 20.0 | +| 200 | 21.2 | +| 350 | 14.5 | +| 550 | 21.2 | +| 700 | 19.8 | +| 850 | 21.2 | +| 1050 | 14.5 | +| 1250 | 21.2 | +| 1400 | 20.0 | + +Line graph showing Link budget remaining/dB vs Distance/m for Bi-directional 4RRH 1beam 700/150 phi=[0]. The y-axis ranges from 14 to 22 dB, and the x-axis ranges from 0 to 1400 m. The curve shows periodic peaks and troughs, with peaks around 200m, 550m, 850m, and 1250m, and troughs around 350m and 1050m. + +**Figure 6.3.3.2.2.1-2 Link budget for Scheme-1** + +For Scheme-2, 1 beam for one RRH panel and 2 beams for another RRH panel and 6 beam per UE panel is selected. Note that a single RRH panel or UE panel refers to the antenna configuration in Table 6.3.3.2.2-1. The RRH panel boresight is pointed to the railway at the distance of $D_s$ , the beam is pointed to 0 and 10 degrees. When the UE is at the distance of $D_s$ , the UE panel boresight is point to RRH panel boresight rightly. The link budget analysis is shown as Figure 6.3.3.2.2.1-3 below. + +![Line graph showing Link budget remaining/dB vs Distance/m for Scheme-2. The y-axis ranges from 17 to 24 dB, and the x-axis ranges from 0 to 1400 m. The curve shows two main peaks around 350m and 1050m, with a significant dip around 850m.](cfc852835f2d91bea8dc074568937e22_img.jpg) + +Bi-directional 4RRH 1,2beam 700/150 phi=[0] [0 10] + +| Distance/m | Link budget remaining/dB | +|------------|--------------------------| +| 0 | 19.8 | +| 100 | 18.8 | +| 150 | 17.8 | +| 200 | 19.5 | +| 300 | 23.0 | +| 350 | 23.5 | +| 400 | 23.2 | +| 500 | 20.8 | +| 600 | 21.0 | +| 700 | 20.0 | +| 800 | 18.5 | +| 850 | 17.8 | +| 900 | 19.5 | +| 1000 | 23.0 | +| 1050 | 23.5 | +| 1100 | 23.2 | +| 1200 | 20.8 | +| 1300 | 21.0 | +| 1400 | 19.8 | + +Line graph showing Link budget remaining/dB vs Distance/m for Scheme-2. The y-axis ranges from 17 to 24 dB, and the x-axis ranges from 0 to 1400 m. The curve shows two main peaks around 350m and 1050m, with a significant dip around 850m. + +Figure 6.3.3.2.2.1-3 Link budget for Scheme-2 + +For Scheme-3, 2 beam per RRH panel and 6 beam per UE panel is selected. The RRH panel boresight is pointed to the railway at the distance of $D_s$ , the beam is pointed to 0 and 10 degrees. When the UE is at the distance of $D_s$ , the UE panel boresight is point to RRH panel boresight rightly. The link budget analysis is shown as Figure 6.3.3.2.2.1-4 below. + +![Line graph showing Link budget remaining/dB vs Distance/m for Scheme-3. The y-axis ranges from 19 to 24 dB, and the x-axis ranges from 0 to 1400 m. The curve shows periodic peaks and dips, with major peaks around 350m, 1050m, and 1350m reaching approximately 23.5 dB, and major dips around 700m and 1400m reaching approximately 19.8 dB.](516d9f1866cc2e359a35fb1d8c046454_img.jpg) + +Bi-directional 4RRH 2beam 700/150 phi=[0 10] + +Line graph showing Link budget remaining/dB vs Distance/m for Scheme-3. The y-axis ranges from 19 to 24 dB, and the x-axis ranges from 0 to 1400 m. The curve shows periodic peaks and dips, with major peaks around 350m, 1050m, and 1350m reaching approximately 23.5 dB, and major dips around 700m and 1400m reaching approximately 19.8 dB. + +**Figure 6.3.3.2.2.1-4 Link budget for Scheme-3** + +The link budget remaining and the minimum beam dwelling time for three schemes are shown as Table 6.3.3.2.2.1-1 below. + +**Table 6.3.3.2.2.1-1 Link budget remaining and minimum beam dwelling time** + +| | link budget remaining[dB] | Minimum beam dwelling time[s] | Beam switching point[m] | +|----------|---------------------------|-------------------------------|-------------------------| +| Scheme-1 | 14.3 | 3.60 | [0,350] | +| Scheme-2 | 17.7 | 2.06 | [150, 350, 500] | +| Scheme-3 | 19.8 | 1.54 | [0, 200, 350, 500] | + +###### 6.3.3.2.2.2 Scenario B, Uni-directional + +For Uni-directional deployment, 2 beams per RRH panel and 6 beam per UE panel is selected. The RRH panel boresight is pointed to the railway at the distance of $D_s$ , the beam is pointed to 0 and 10 degrees. When the UE is at the distance of $D_s$ , the UE panel boresight is point to RRH panel boresight rightly. The link budget analysis is shown as Figure 6.3.3.2.2.2-1 below. + +![Figure 6.3.3.2.2.2-1: Link budget for Uni-directional deployment. The graph shows 'Link budget remaining/dB' on the y-axis (ranging from 15 to 24) versus 'Distance/m' on the x-axis (ranging from 0 to 1400). The curve starts at approximately 20 dB at 0m, rises to a peak of about 23.5 dB at 350m, then drops sharply to a minimum of about 16 dB at 450m. It then rises to another peak of about 23.5 dB at 1050m, drops again to a minimum of about 16 dB at 1150m, and finally rises to about 20 dB at 1400m. The beam switching points are indicated at 200m and 450m.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +Uni-directional 4RRH 2beam 700/150 phi=[0 10] + +Figure 6.3.3.2.2.2-1: Link budget for Uni-directional deployment. The graph shows 'Link budget remaining/dB' on the y-axis (ranging from 15 to 24) versus 'Distance/m' on the x-axis (ranging from 0 to 1400). The curve starts at approximately 20 dB at 0m, rises to a peak of about 23.5 dB at 350m, then drops sharply to a minimum of about 16 dB at 450m. It then rises to another peak of about 23.5 dB at 1050m, drops again to a minimum of about 16 dB at 1150m, and finally rises to about 20 dB at 1400m. The beam switching points are indicated at 200m and 450m. + +**Figure 6.3.3.2.2.2-1 Link budget for Uni-directional deployment** + +The link budget remaining and the minimum beam dwelling time for Uni-directional deployment is shown as Table 6.3.3.2.2.2-1 below. + +**Table 6.3.3.2.2.2-1 Link budget remaining and minimum beam dwelling time** + +| link budget remaining[dB] | minimum beam dwelling time[s] | Beam switching point[m] | +|---------------------------|-------------------------------|-------------------------| +| 15.8 | 2.57 | [200, 450] | + +#### 6.3.3.3 Link level performance from Ericsson + +For scenario A and B, uni- and bi-directional scenarios, Ericsson provided evaluation in contributions R4-2104679 and R4-2104680. The analysis has been performed using the antenna array configurations in sections 6.1.1 and 6.1.3. + +##### 6.3.3.3.1 Scenario-A, Uni-directional RRH Deployment + +For this scenario, it was assumed that the RRH is positioned such that the antenna(s) face directly along the track; i.e. a zero degree steered beam is parallel to the track (in both azimuth and elevation). The UE on the train is positioned such that its antenna(s) point directly along the track. + +Zero beam steering was assumed, and so the RRH beam points along the track (but is 10m away from the track) and the UE beam points along the track. + +These assumptions are not fully optimal, but they are sufficient to demonstrate that a single TX and a single RX beam is sufficient. + +The antenna radiation patterns in azimuth for the UE and RRH are depicted in figure 6.3.3.3.1-1. The array is symmetrical in both axes, so the elevation patterns are the same as the azimuth patterns. + +![Figure 6.3.3.1-1: RRH and UE antenna radiation patterns in azimuth. The figure contains two side-by-side plots. The left plot, titled 'BS Azimuth', shows the Gain (dB) versus Angle wrt boresight (degree) for a Base Station (BS). The gain is highest at 0 degrees (approx. 15 dB) and decreases as the angle increases, with a sharp null at 90 degrees. The right plot, titled 'UE Azimuth', shows the Gain (dB) versus Angle wrt boresight (degree) for a User Equipment (UE). The gain is highest at 0 degrees (approx. 10 dB) and decreases as the angle increases, with a sharp null at 90 degrees.](a85105fd544c64ef624aa45c72378647_img.jpg) + +Figure 6.3.3.1-1: RRH and UE antenna radiation patterns in azimuth. The figure contains two side-by-side plots. The left plot, titled 'BS Azimuth', shows the Gain (dB) versus Angle wrt boresight (degree) for a Base Station (BS). The gain is highest at 0 degrees (approx. 15 dB) and decreases as the angle increases, with a sharp null at 90 degrees. The right plot, titled 'UE Azimuth', shows the Gain (dB) versus Angle wrt boresight (degree) for a User Equipment (UE). The gain is highest at 0 degrees (approx. 10 dB) and decreases as the angle increases, with a sharp null at 90 degrees. + +**Figure 6.3.3.1-1: RRH and UE antenna radiation patterns in azimuth (Elevation patterns are the same)** + +The most critical link for coverage is the uplink. Thus, the uplink was modelled considering 23dBm transmitter power for the UE. For a train mounted UE, this may be an underestimate for the power. + +The coverage pattern for the single TX / RX beam is depicted in figure 6.3.3.1-3. A uni-directional deployment is considered in which the RRH antenna is pointing in the direction of movement of the train and the UE antenna away from the direction of movement of the train. The x axis represents the distance along the track from the point on the track that is closest to the RRH. (That implies, at zero on the x axis the UE on the side is parallel to the RRH which is 10m away from the side of the track). The y axis represents UL SNR assuming 10dB noise figure at the RRH + +![Figure 6.3.3.1-2: Unidirectional deployment scenario. The diagram shows a horizontal track with a train moving from left to right, indicated by an arrow labeled 'Train direction of travel'. On the left, an RRH antenna is shown pointing forward (to the right), labeled 'RRH antenna pointing forward'. On the train, a UE antenna is shown pointing backward (to the left), labeled 'UE antenna pointing backward'. The track has two vertical dashed lines indicating positions: X=0 at the RRH location and X=700m at a second RRH location.](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +Figure 6.3.3.1-2: Unidirectional deployment scenario. The diagram shows a horizontal track with a train moving from left to right, indicated by an arrow labeled 'Train direction of travel'. On the left, an RRH antenna is shown pointing forward (to the right), labeled 'RRH antenna pointing forward'. On the train, a UE antenna is shown pointing backward (to the left), labeled 'UE antenna pointing backward'. The track has two vertical dashed lines indicating positions: X=0 at the RRH location and X=700m at a second RRH location. + +**Figure 6.3.3.1-2: Unidirectional deployment scenario** + +As can be seen in the figure, good coverage is obtained when the train is further than 60-70m along the track from the RRH. Furthermore, the SNR remains good from 700-800m; i.e. the SNR from the RRH at position zero on the track is still good as the UE passes the next RRH (located at 700m along the track) + +![Figure 6.3.3.3.1-3: UL SNR for single TX and single RX beam. A line graph titled 'Single beam coverage' showing UL SNR on the y-axis (ranging from -20 to 40) versus Distance along track from RRH (m) on the x-axis (ranging from 0 to 900). The curve starts at -20 dB at 0m, rises sharply to a peak of approximately 32 dB at 100m, and then gradually declines to about 18 dB at 800m.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +| Distance along track from RRH (m) | UL SNR (dB) | +|-----------------------------------|-------------| +| 0 | -20 | +| 100 | 32 | +| 200 | 28 | +| 300 | 25 | +| 400 | 22 | +| 500 | 20 | +| 600 | 18 | +| 700 | 17 | +| 800 | 16 | + +Figure 6.3.3.3.1-3: UL SNR for single TX and single RX beam. A line graph titled 'Single beam coverage' showing UL SNR on the y-axis (ranging from -20 to 40) versus Distance along track from RRH (m) on the x-axis (ranging from 0 to 900). The curve starts at -20 dB at 0m, rises sharply to a peak of approximately 32 dB at 100m, and then gradually declines to about 18 dB at 800m. + +Figure 6.3.3.3.1-3: UL SNR for single TX and single RX beam + +Using DPS, the UE can switch RRH after travelling around 60-70m along the track from RRH2 in the figure. Assuming that this is the case, then the SNR observed when travelling along the track is as depicted in figure 4. For downlink, the SNR will be greater. + +![Figure 6.3.3.3.1-4: UL SNR assuming single TX/RX beam and DPS switching between RRH. A line graph titled '1 beam, switch RRH' showing UL SNR on the y-axis (ranging from -20 to 40) versus Distance of UE along track (m) on the x-axis (ranging from 0 to 900). The curve shows a dip at 200m, labeled 'Switch serving RRH'. Annotations indicate coverage from RRH 1 (up to 200m) and RRH 2 (starting at 200m). The SNR peaks at approximately 32 dB at 100m and declines to about 18 dB at 800m.](8f7b458d3cc18ca96924473839d68ae6_img.jpg) + +| Distance of UE along track (m) | UL SNR (dB) | +|--------------------------------|-------------| +| 0 | 20 | +| 100 | 32 | +| 200 | 20 | +| 300 | 25 | +| 400 | 22 | +| 500 | 20 | +| 600 | 18 | +| 700 | 17 | +| 800 | 16 | + +Figure 6.3.3.3.1-4: UL SNR assuming single TX/RX beam and DPS switching between RRH. A line graph titled '1 beam, switch RRH' showing UL SNR on the y-axis (ranging from -20 to 40) versus Distance of UE along track (m) on the x-axis (ranging from 0 to 900). The curve shows a dip at 200m, labeled 'Switch serving RRH'. Annotations indicate coverage from RRH 1 (up to 200m) and RRH 2 (starting at 200m). The SNR peaks at approximately 32 dB at 100m and declines to about 18 dB at 800m. + +Figure 6.3.3.3.1-4: UL SNR assuming single TX/RX beam and DPS switching between RRH + +Based on this analysis, we observe that in scenario 1, in a uni-directional deployment it is sufficient to operate with a single TX beam and a single RX beam. + +##### 6.3.3.3.2 Scenario-A, Bi-directional RRH Deployment + +Uni-directional deployment in Scenario A provides very good coverage. Bi-directional deployment would require connection to the second nearest basestation when the UE would be within around 50m from a basestation due to the + +large azimuth angle to the nearest RRH at that point. Thus, bi-directional deployment would require double the antenna infrastructure at basestations with no coverage or capacity gain. + +If RRH are equipped with two antenna, improved throughput can be obtained by operating each direction as an independent uni-directional UE. In a future release, multi-antenna single UE operation may also be introduced. + +##### 6.3.3.3.3 Scenario-B, Uni-directional RRH Deployment + +To consider the number of beams and coverage, a deployment has been analyzed considering scenario B. The RRH antennas are rotated by 13 degrees towards the track, whilst the UE antenna points parallel to the track. Up to 3 RRH beams and up to 2 UE beams are considered. Uplink SNR is considered for depicting the coverage of the beams, since UL SNR is the most critical scenario. DL SNR will be larger than UL SNR. + +The x axis represents the distance along the track from the point on the track that is closest to the RRH. (That implies, at zero on the x axis the UE on the side is parallel to the RRH, which is 150m away from the side of the track). The y axis represents UL SNR assuming 10dB noise figure at the RRH and 23dBm UE TRP. + +![Figure 6.3.3.3.3-1: Coverage of RRH beam 1 + UE beam 1. A line graph titled 'Beam 1 coverage' showing UI SNR (dB) on the y-axis (ranging from -20 to 25) versus Distance along track from RRH (m) on the x-axis (ranging from 0 to 1400). The curve shows a sharp rise from -20 dB at 0m to a peak of approximately 21 dB at 500m, followed by a gradual decline to about 11 dB at 1400m. There are small oscillations between 0m and 200m.](e046996962d6740cf050a5640e0c6b40_img.jpg) + +| Distance along track from RRH (m) | UI SNR (dB) | +|-----------------------------------|-------------| +| 0 | -20 | +| 100 | -10 | +| 200 | 5 | +| 300 | 15 | +| 400 | 20 | +| 500 | 21 | +| 600 | 20 | +| 800 | 18 | +| 1000 | 15 | +| 1200 | 13 | +| 1400 | 11 | + +Figure 6.3.3.3.3-1: Coverage of RRH beam 1 + UE beam 1. A line graph titled 'Beam 1 coverage' showing UI SNR (dB) on the y-axis (ranging from -20 to 25) versus Distance along track from RRH (m) on the x-axis (ranging from 0 to 1400). The curve shows a sharp rise from -20 dB at 0m to a peak of approximately 21 dB at 500m, followed by a gradual decline to about 11 dB at 1400m. There are small oscillations between 0m and 200m. + +Figure 6.3.3.3.3-1: Coverage of RRH beam 1 + UE beam 1 + +![Figure 6.3.3.3.3-2: Beam 2 coverage plot showing UL SNR (dB) vs Distance of UE along track from RRH (m).](068b3a3247570c4b78342a943f15de9e_img.jpg) + +The plot titled "Beam 2 coverage" shows the UL SNR (dB) on the y-axis (0 to 25) against the Distance of UE along track from RRH (m) on the x-axis (0 to 1200). The curve starts at 0 dB at 200m, rises to a peak of approximately 22 dB at 300m, and then declines to 0 dB at 600m. A second, lower curve segment starts at 0 dB at 700m, rises to a peak of approximately 3 dB at 900m, and then declines to 0 dB at 1100m. + +| Distance (m) | UL SNR (dB) | +|--------------|-------------| +| 200 | 0 | +| 300 | 22 | +| 400 | 18 | +| 500 | 10 | +| 600 | 0 | +| 700 | 0 | +| 800 | 2 | +| 900 | 3 | +| 1000 | 2 | +| 1100 | 0 | + +Figure 6.3.3.3.3-2: Beam 2 coverage plot showing UL SNR (dB) vs Distance of UE along track from RRH (m). + +Figure 6.3.3.3.3-2: Coverage of RRH beam 2 + UE beam 1 + +![Figure 6.3.3.3.3-3: Beam 3 coverage plot showing UL SNR (dB) vs Distance of UE along track from RRH (m).](a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg) + +The plot titled "Beam 3" shows the UL SNR (dB) on the y-axis (0 to 30) against the Distance of UE along track from RRH (m) on the x-axis (0 to 600). The curve starts at 0 dB at 100m, rises to a peak of approximately 26 dB at 150m, and then declines to 0 dB at 300m. A second, lower curve segment starts at 0 dB at 300m, rises to a peak of approximately 5 dB at 350m, and then declines to 0 dB at 450m. + +| Distance (m) | UL SNR (dB) | +|--------------|-------------| +| 100 | 0 | +| 150 | 26 | +| 200 | 22 | +| 250 | 15 | +| 300 | 0 | +| 350 | 5 | +| 400 | 3 | +| 450 | 0 | + +Figure 6.3.3.3.3-3: Beam 3 coverage plot showing UL SNR (dB) vs Distance of UE along track from RRH (m). + +Figure 6.3.3.3.3-3: Coverage of RRH beam 3 + UE beam 2 + +Figure 6.3.3.3.3-1 indicates that the first RRH beam can provide coverage from around 300-400m along the track to around 1km along the track. This means that the RRH can provide coverage to a point well beyond the following RRH. Figures 6.3.3.3.3-2 and 6.3.3.3.3-3 indicate that the remaining beams can provide coverage closer to the RRH. + +There is little point in providing more beams. Beam 3 provides coverage from around 100-150m from the RRH. Closer to the RRH, beam 1 from the previous RRH is able to provide coverage. Further beams closer to the RRH would be narrow in coverage and do not improve SNR. + +Figure 6.3.3.3.3-4 indicates the SNR if a single TX/RX beam (beam 1) is used and coverage close to the RRH is provided from the previous/next RRH. The figure indicates that good UL SNR of above 15dB (DL SNR will be larger than this) can be provided along the length of the track with one TX and one RX beam. + +![Figure 6.3.3.3.3-4: Coverage provided from next and previous RRH with 1 beam per RRH and UE antenna. The graph shows UI SNR (dB) on the y-axis (0 to 25) versus Distance along track (m) on the x-axis (0 to 700). The curve starts at approximately 19.5 dB at 0m, fluctuates slightly, reaches a minimum of about 14 dB at 350m, and then rises to a peak of about 21 dB at 500m before slightly decreasing to 19.5 dB at 700m.](77a781dfb114c3e2b399f876f1808cfd_img.jpg) + +Figure 6.3.3.3.3-4 is a line graph showing the UI SNR (dB) on the y-axis (ranging from 0 to 25) versus the Distance along track (m) on the x-axis (ranging from 0 to 700). The curve starts at approximately 19.5 dB at 0m, fluctuates slightly, reaches a minimum of about 14 dB at 350m, and then rises to a peak of about 21 dB at 500m before slightly decreasing to 19.5 dB at 700m. + +| Distance along track (m) | UI SNR (dB) | +|--------------------------|-------------| +| 0 | 19.5 | +| 100 | 18.5 | +| 200 | 17.5 | +| 300 | 16.5 | +| 350 | 14.0 | +| 400 | 18.5 | +| 500 | 21.0 | +| 600 | 20.5 | +| 700 | 19.5 | + +Figure 6.3.3.3.3-4: Coverage provided from next and previous RRH with 1 beam per RRH and UE antenna. The graph shows UI SNR (dB) on the y-axis (0 to 25) versus Distance along track (m) on the x-axis (0 to 700). The curve starts at approximately 19.5 dB at 0m, fluctuates slightly, reaches a minimum of about 14 dB at 350m, and then rises to a peak of about 21 dB at 500m before slightly decreasing to 19.5 dB at 700m. + +**Figure 6.3.3.3.3-4: Coverage provided from next and previous RRH with 1 beam per RRH and UE antenna.** + +Figure 6.3.3.3.3-5 depicts the coverage obtained with 3 beams per RRH antenna and 2 beams per UE antenna, considering both the current and previous RRH. The figure shows that the lowest SNR level can be improved a few dB compared to the single beam case. + +![Figure 6.3.3.3.3-5: Coverage provided from next and previous RRH with 3 beams per RRH antenna and 2 beams per UE antenna. The graph shows UI SNR (dB) on the y-axis (0 to 30) versus Distance along track (m) on the x-axis (0 to 700). The curve starts at approximately 19.5 dB at 0m, rises to a peak of about 26 dB at 150m, dips to about 18 dB at 250m, and then stabilizes around 20 dB from 500m to 700m.](48fc91e19c1a9b6674b120fbdd89b203_img.jpg) + +Figure 6.3.3.3.3-5 is a line graph titled "Combined coverage 3 beams and previous BS". The y-axis represents UI SNR (dB) from 0 to 30, and the x-axis represents Distance along track (m) from 0 to 700. The curve starts at approximately 19.5 dB at 0m, rises to a peak of about 26 dB at 150m, dips to about 18 dB at 250m, and then stabilizes around 20 dB from 500m to 700m. + +| Distance along track (m) | UI SNR (dB) | +|--------------------------|-------------| +| 0 | 19.5 | +| 100 | 18.0 | +| 150 | 26.0 | +| 200 | 23.0 | +| 250 | 18.0 | +| 300 | 22.0 | +| 400 | 18.5 | +| 500 | 20.5 | +| 600 | 20.5 | +| 700 | 19.5 | + +Figure 6.3.3.3.3-5: Coverage provided from next and previous RRH with 3 beams per RRH antenna and 2 beams per UE antenna. The graph shows UI SNR (dB) on the y-axis (0 to 30) versus Distance along track (m) on the x-axis (0 to 700). The curve starts at approximately 19.5 dB at 0m, rises to a peak of about 26 dB at 150m, dips to about 18 dB at 250m, and then stabilizes around 20 dB from 500m to 700m. + +**Figure 6.3.3.3.3-5: Coverage provided from next and previous RRH with 3 beams per RRH antenna and 2 beams per UE antenna.** + +Thus, we observe that it is perfectly feasible to assume just one beam per antenna also for scenario B as long as the RRH antenna is oriented slightly towards the track. There is some scope for further optimization if 3 RRH / 2 UE beams are considered. Also, allowing for more beams offers more robustness for covering track curves. + +##### 6.3.3.3.4 Scenario-B, Bi-directional RRH Deployment + +For bi-directional deployment, half of the distance along the track would be covered by one RRH and the other half by the following RRH + +![Diagram of bi-directional RRH deployment scenario showing RRH panels at X=0 and X=700m, and a UE panel in the middle pointing in both directions.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg) + +The diagram illustrates a bi-directional RRH deployment scenario. A horizontal line represents the track. At the left end, labeled $X=0$ , there is an RRH panel pointing in both directions. At the right end, labeled $X=700\text{m}$ , there is another RRH panel pointing in both directions. In the center of the track, a UE panel is shown, also pointing in both directions. Above the track, an arrow indicates the 'Train direction of travel' to the right. + +Diagram of bi-directional RRH deployment scenario showing RRH panels at X=0 and X=700m, and a UE panel in the middle pointing in both directions. + +Figure 6.3.3.3.4-1: Bi-directional deployment scenario + +The figure below depicts the achievable coverage using 3 beams at the RRH and 3 beams at the UE, with the RRH and UE antennas pointed parallel to the track. After 350m along the track, coverage would be provided by the next RRH. To avoid a break in coverage close to the RRH, the next nearest RRH should be used to serve the UE when it is close in to a RRH. + +![Graph showing UL SNR (dB) vs Distance of UE along track (m) for a 3 beam scenario.](856421a17b9d40f97b994ca38151fb9a_img.jpg) + +The graph shows the UL SNR (dB) on the y-axis (ranging from 0 to 35) versus the Distance of UE along track (m) on the x-axis (ranging from 0 to 350). The curve starts at 0 dB at 0m, rises to a peak of approximately 30 dB at 50m, then drops to a minimum of about 17 dB at 100m. It then rises to a plateau of approximately 24 dB between 150m and 250m, before gradually decreasing to about 20 dB at 350m. The title of the graph is '3 beam'. + +| Distance of UE along track (m) | UL SNR (dB) | +|--------------------------------|-------------| +| 0 | 0 | +| 50 | 30 | +| 100 | 17 | +| 150 | 24 | +| 200 | 23 | +| 250 | 24 | +| 300 | 22 | +| 350 | 20 | + +Graph showing UL SNR (dB) vs Distance of UE along track (m) for a 3 beam scenario. + +Figure 6.3.3.3.4-2: UL SNR with 3 beams per UE and RRH in each direction with DPS switching between beams and RRH + +#### 6.3.3.4 Throughput Performance from Nokia + +The throughput CDFs are obtained from fully dynamic system-level simulations, which were carried out to evaluate RRM requirements and mobility performance under high-speed train scenarios in FR2. Simulations were performed with train speed 350 km/h in both uni-directional Scenario-A and -B. In bi-directional case only throughput results for Scenario-B are covered. 50MHz channel bandwidth is assumed. + +The results include “non-SFN and non-DPS” (i.e., without DPS) transmission scheme analysis corresponding to L3-mobility based on the traditional HO procedure. In these simulations, it is assumed that each BBU has only one RRH corresponding to a more challenging mobility scenario due to longer delays. Alternatively, simulation results for Dynamic Point Selection (DPS) deployments assume that all RRHs are connected to the same BBU, i.e., the mobility is based on L1 measurements and is provided by beam management procedures instead of HO. + +On the RRH side, the number of Tx beams is chosen according to the deployment, i.e., only 1 Tx beam in Scenario-A, and 1 or 2 Tx beams in Scenario-B. + +The simulation assumptions and parameters for the evaluation of mobility performance are shown in Table 6.3.8.1-1 6.3.4.1.1-1 and 6.3.4.1.2-1 without DRX. + +Throughput statistics are shown in figures 6.3.3.4-1, 6.3.3.4-2, 6.3.3.4-3, 6.3.3.4-4, 6.3.3.4-5, 6.3.3.4-6, 6.3.3.4-7 and 6.3.3.4-8. The used metric is windowed user (CPE) throughput where each sample represents average throughput over 100 ms window of the CPE. The maximum achievable CPE throughput in this scenario setting with 50 MHz and maximum modulation 64QAM is about 300 Mbps when there is only one CPE served by a cell at a time. Both the performance with enhanced RRM requirements (Req: Enhanced) and legacy RRM requirements (Req: Legacy) are shown in the figures. + +The results demonstrate that in the investigated uni-directional scenarios maximum throughput is achieved over 90% of the time. The reason for such a high performance is that there is only one CPE in the simulated area at a time creating very favorable interference conditions. Propagation condition is fully LOS, which causes the coverage area of a RRH to be long along the track. Also, mobility performance (see 6.3.4.1) in non-DRX case is sufficient to keep CPE most of the time in the cell and beam with good signal conditions. In the uni-directional scenario where train is traveling to opposite direction than RRH beams are pointing to the throughput performance tends to be lower than in the cases where train is traveling to the same direction as RRH beams are pointing to. The reason for this is in the mobility performance that is clearly better in the same direction case. However, enhanced requirements clearly also improve the throughput performance of the opposite direction case. The throughputs in DPS deployment are higher than without DPS in all uni-directional cases. + +In the bi-directional scenarios maximum throughputs are achieved more seldom i.e., 40-60% of the window samples. One reason, why throughput in bi-directional Scenario-B is not optimal might be because UE is not connected to the closest RRH but to the next closest one, e.g., like it is shown in Figure 5.2.2-3. Bi-directional scenarios are also affected by more frequent handovers and beam switches compared to uni-directional scenarios, which can cause small breaks in data transmission affecting throughput for some of the sampled windows. However, also bi-directional scenario throughput performance gets better when enhanced RRM requirements are applied, despite the lower number of Rx beam options in use compared to legacy RRM requirements. The delay in switching to a better cell or beam gets lower with enhanced requirements. The throughputs in DPS deployment are higher than without DPS in all bi-directional cases. + +![CDF plot of windowed user throughput for Scenario A without DPS. The plot shows four curves: RRHDir:Same, Req:Enhanced (solid blue); RRHDir:Opposite, Req:Enhanced (solid red); RRHDir:Same, Req:Legacy (dashed blue); and RRHDir:Opposite, Req:Legacy (dashed red). The x-axis is 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis is 'CDF' from 0.0 to 1.0. All curves are near zero until about 250,000 kbps, where they jump to 1.0. The dashed red curve is slightly higher than the others in the 0-250,000 kbps range.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +Windowed user throughput (Scenario:A-unidir, non-DPS, RRHBeams:1) + +CDF + +Windowed user throughput (100 ms window) [kbps] + +Legend: + +- RRHDir:Same, Req:Enhanced, +- RRHDir:Opposite, Req:Enhanced, +- RRHDir:Same, Req:Legacy, +- RRHDir:Opposite, Req:Legacy, + +CDF plot of windowed user throughput for Scenario A without DPS. The plot shows four curves: RRHDir:Same, Req:Enhanced (solid blue); RRHDir:Opposite, Req:Enhanced (solid red); RRHDir:Same, Req:Legacy (dashed blue); and RRHDir:Opposite, Req:Legacy (dashed red). The x-axis is 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis is 'CDF' from 0.0 to 1.0. All curves are near zero until about 250,000 kbps, where they jump to 1.0. The dashed red curve is slightly higher than the others in the 0-250,000 kbps range. + +Figure 6.3.3.4-1: Windowed user throughput in uni-directional Scenario-A without DPS + +![CDF plot of windowed user throughput for Scenario A with DPS. The plot shows four curves: Req:Enhanced, RRHDir:Same (solid blue); Req:Enhanced, RRHDir:Opposite (solid red); Req:Legacy, RRHDir:Same (dashed blue); and Req:Legacy, RRHDir:Opposite (dashed red). The x-axis is 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis is 'CDF' from 0.0 to 1.0. All curves are near zero until about 250,000 kbps, where they jump to 1.0. The dashed red curve is slightly higher than the others in the 0-250,000 kbps range.](8a4275b35551f2ec9825a1aa442c0db1_img.jpg) + +Windowed user throughput (Scenario:A-unidir, DPS, RRHBeams:1) + +CDF + +Windowed user throughput (100 ms window) [kbps] + +Legend: + +- Req:Enhanced, RRHDir:Same, +- Req:Enhanced, RRHDir:Opposite, +- Req:Legacy, RRHDir:Same, +- Req:Legacy, RRHDir:Opposite, + +CDF plot of windowed user throughput for Scenario A with DPS. The plot shows four curves: Req:Enhanced, RRHDir:Same (solid blue); Req:Enhanced, RRHDir:Opposite (solid red); Req:Legacy, RRHDir:Same (dashed blue); and Req:Legacy, RRHDir:Opposite (dashed red). The x-axis is 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis is 'CDF' from 0.0 to 1.0. All curves are near zero until about 250,000 kbps, where they jump to 1.0. The dashed red curve is slightly higher than the others in the 0-250,000 kbps range. + +Figure 6.3.3.4-2: Windowed user throughput in uni-directional Scenario-A with DPS + +![CDF plot of Windowed user throughput for Scenario-B-unidir, non-DPS, RRHBeams:1. The plot shows four curves: RRHDir:Same, Req:Enhanced (solid blue); RRHDir:Opposite, Req:Enhanced (solid red); RRHDir:Same, Req:Legacy (dashed blue); and RRHDir:Opposite, Req:Legacy (dashed red). The x-axis represents 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis represents 'CDF' from 0.0 to 1.0. All curves remain near zero until approximately 250,000 kbps, where they all rise sharply to a CDF of 1.0 at 300,000 kbps.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +Windowed user throughput (Scenario:B-unidir, non-DPS, RRHBeams:1) + +CDF + +Windowed user throughput (100 ms window) [kbps] + +RRHDir:Same, Req:Enhanced, +RRHDir:Opposite, Req:Enhanced, +RRHDir:Same, Req:Legacy, +RRHDir:Opposite, Req:Legacy, + +CDF plot of Windowed user throughput for Scenario-B-unidir, non-DPS, RRHBeams:1. The plot shows four curves: RRHDir:Same, Req:Enhanced (solid blue); RRHDir:Opposite, Req:Enhanced (solid red); RRHDir:Same, Req:Legacy (dashed blue); and RRHDir:Opposite, Req:Legacy (dashed red). The x-axis represents 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis represents 'CDF' from 0.0 to 1.0. All curves remain near zero until approximately 250,000 kbps, where they all rise sharply to a CDF of 1.0 at 300,000 kbps. + +Figure 6.3.3.4-3: Windowed user throughput in uni-directional Scenario-B without DPS (RRHBeams:1) + +![CDF plot of Windowed user throughput for Scenario-B-unidir, DPS, RRHBeams:1. The plot shows four curves: RRHDir:Same, Req:Enhanced (solid blue); RRHDir:Opposite, Req:Enhanced (solid red); RRHDir:Same, Req:Legacy (dashed blue); and RRHDir:Opposite, Req:Legacy (dashed red). The x-axis represents 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis represents 'CDF' from 0.0 to 1.0. All curves remain near zero until approximately 250,000 kbps, where they all rise sharply to a CDF of 1.0 at 300,000 kbps.](4134b40f9161ec8fcd3c28bdb48f80b0_img.jpg) + +Windowed user throughput (Scenario:B-unidir, DPS, RRHBeams:1) + +CDF + +Windowed user throughput (100 ms window) [kbps] + +RRHDir:Same, Req:Enhanced, +RRHDir:Opposite, Req:Enhanced, +RRHDir:Same, Req:Legacy, +RRHDir:Opposite, Req:Legacy, + +CDF plot of Windowed user throughput for Scenario-B-unidir, DPS, RRHBeams:1. The plot shows four curves: RRHDir:Same, Req:Enhanced (solid blue); RRHDir:Opposite, Req:Enhanced (solid red); RRHDir:Same, Req:Legacy (dashed blue); and RRHDir:Opposite, Req:Legacy (dashed red). The x-axis represents 'Windowed user throughput (100 ms window) [kbps]' from 0 to 300,000. The y-axis represents 'CDF' from 0.0 to 1.0. All curves remain near zero until approximately 250,000 kbps, where they all rise sharply to a CDF of 1.0 at 300,000 kbps. + +Figure 6.3.3.4-4: Windowed user throughput in uni-directional Scenario-B with DPS (RRHBeams:1) + +![CDF plot of Windowed user throughput for Scenario-B-unidir, non-DPS, RRHBeams:2. The plot compares four configurations: RRHDir:Same, Req:Enhanced; RRHDir:Opposite, Req:Enhanced; RRHDir:Same, Req:Legacy; and RRHDir:Opposite, Req:Legacy. The x-axis represents Windowed user throughput (100 ms window) [kbps] from 0 to 300,000. The y-axis represents CDF from 0.0 to 1.0. All curves show a sharp increase in CDF starting around 250,000 kbps, reaching 1.0 at approximately 300,000 kbps.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +Windowed user throughput (Scenario:B-unidir, non-DPS, RRHBeams:2) + +CDF + +Windowed user throughput (100 ms window) [kbps] + +Legend: + +- RRHDir:Same, Req:Enhanced, +- RRHDir:Opposite, Req:Enhanced, +- RRHDir:Same, Req:Legacy, +- RRHDir:Opposite, Req:Legacy, + +CDF plot of Windowed user throughput for Scenario-B-unidir, non-DPS, RRHBeams:2. The plot compares four configurations: RRHDir:Same, Req:Enhanced; RRHDir:Opposite, Req:Enhanced; RRHDir:Same, Req:Legacy; and RRHDir:Opposite, Req:Legacy. The x-axis represents Windowed user throughput (100 ms window) [kbps] from 0 to 300,000. The y-axis represents CDF from 0.0 to 1.0. All curves show a sharp increase in CDF starting around 250,000 kbps, reaching 1.0 at approximately 300,000 kbps. + +Figure 6.3.3.4-5: Windowed user throughput in uni-directional Scenario-B without DPS (RRHBeams:2) + +![CDF plot of Windowed user throughput for Scenario-B-unidir, DPS, RRHBeams:2. The plot compares the same four configurations as the previous figure. The x-axis represents Windowed user throughput (100 ms window) [kbps] from 0 to 300,000. The y-axis represents CDF from 0.0 to 1.0. The curves show a similar sharp increase in CDF starting around 250,000 kbps, reaching 1.0 at approximately 300,000 kbps, indicating similar performance with DPS enabled.](a96c7e19f53f2350db97a90738a6fb51_img.jpg) + +Windowed user throughput (Scenario:B-unidir, DPS, RRHBeams:2) + +CDF + +Windowed user throughput (100 ms window) [kbps] + +Legend: + +- RRHDir:Same, Req:Enhanced, +- RRHDir:Opposite, Req:Enhanced, +- RRHDir:Same, Req:Legacy, +- RRHDir:Opposite, Req:Legacy, + +CDF plot of Windowed user throughput for Scenario-B-unidir, DPS, RRHBeams:2. The plot compares the same four configurations as the previous figure. The x-axis represents Windowed user throughput (100 ms window) [kbps] from 0 to 300,000. The y-axis represents CDF from 0.0 to 1.0. The curves show a similar sharp increase in CDF starting around 250,000 kbps, reaching 1.0 at approximately 300,000 kbps, indicating similar performance with DPS enabled. + +Figure 6.3.3.4-6: Windowed user throughput in uni-directional Scenario-B with DPS (RRHBeams:2) + +![Figure 6.3.3.4-7: Windowed user throughput in bi-directional Scenario-B without DPS. The graph shows the Cumulative Distribution Function (CDF) of windowed user throughput (100 ms window) in kbps for four scenarios: RRHBeams:1, Req:Enhanced (solid blue line); RRHBeams:2, Req:Enhanced (solid red line); RRHBeams:1, Req:Legacy (dashed blue line); and RRHBeams:2, Req:Legacy (dashed red line). The x-axis ranges from 0 to 300,000 kbps, and the y-axis ranges from 0.0 to 1.0. The curves show that the 'Enhanced' requirement scenarios achieve higher throughput than the 'Legacy' requirement scenarios, and the 'RRHBeams:1' scenarios achieve higher throughput than the 'RRHBeams:2' scenarios.](6752cee124f693bc4cebc66180f4f91f_img.jpg) + +Figure 6.3.3.4-7: Windowed user throughput in bi-directional Scenario-B without DPS. The graph shows the Cumulative Distribution Function (CDF) of windowed user throughput (100 ms window) in kbps for four scenarios: RRHBeams:1, Req:Enhanced (solid blue line); RRHBeams:2, Req:Enhanced (solid red line); RRHBeams:1, Req:Legacy (dashed blue line); and RRHBeams:2, Req:Legacy (dashed red line). The x-axis ranges from 0 to 300,000 kbps, and the y-axis ranges from 0.0 to 1.0. The curves show that the 'Enhanced' requirement scenarios achieve higher throughput than the 'Legacy' requirement scenarios, and the 'RRHBeams:1' scenarios achieve higher throughput than the 'RRHBeams:2' scenarios. + +Figure 6.3.3.4-7: Windowed user throughput in bi-directional Scenario-B without DPS + +![Figure 6.3.3.4-8: Windowed user throughput in bi-directional Scenario-B with DPS. The graph shows the Cumulative Distribution Function (CDF) of windowed user throughput (100 ms window) in kbps for the same four scenarios as Figure 6.3.3.4-7. The x-axis ranges from 0 to 300,000 kbps, and the y-axis ranges from 0.0 to 1.0. The curves show that the 'Enhanced' requirement scenarios achieve higher throughput than the 'Legacy' requirement scenarios, and the 'RRHBeams:1' scenarios achieve higher throughput than the 'RRHBeams:2' scenarios. The overall throughput levels are similar to those in Figure 6.3.3.4-7, indicating that the DPS feature does not significantly improve the windowed user throughput in this scenario.](8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg) + +Figure 6.3.3.4-8: Windowed user throughput in bi-directional Scenario-B with DPS. The graph shows the Cumulative Distribution Function (CDF) of windowed user throughput (100 ms window) in kbps for the same four scenarios as Figure 6.3.3.4-7. The x-axis ranges from 0 to 300,000 kbps, and the y-axis ranges from 0.0 to 1.0. The curves show that the 'Enhanced' requirement scenarios achieve higher throughput than the 'Legacy' requirement scenarios, and the 'RRHBeams:1' scenarios achieve higher throughput than the 'RRHBeams:2' scenarios. The overall throughput levels are similar to those in Figure 6.3.3.4-7, indicating that the DPS feature does not significantly improve the windowed user throughput in this scenario. + +Figure 6.3.3.4-8: Windowed user throughput in bi-directional Scenario-B with DPS + +### 6.3.4 Mobility Performance + +RAN4 discussed the RX beam number for RRM requirements definition and agreed to define two set of requirements for Scenario A and Scenario B in terms of number of RX beams per UE: + +- Scenario A: [2] RX beams for all scenarios. +- Scenario B: [6] RX beams for all scenarios. + +NOTE: if there is insignificant difference between Scenario A and B requirements, then further discussion on unified requirements can take place + +For RRC CONNECTED mode requirements for DRX (based on GtW): + +- Define requirements for the short DRX configurations ( $\leq [80]$ ms). + +Handover: + +- Existing FR2 requirement should be applicable to the HST FR2 deployments when the target cell is known. + +Requirements on inter-frequency measurements: + +- Do not define inter-frequency measurements requirements for FR2 HST. + +Requirements on inter-RAT measurements: + +- Do not define inter-RAT measurements requirements for FR2 HST. + +Measurement procedures: + +- 1) Cell identification - PSS/SSS detection: + - Option1: The Cell identification - PSS/SSS detection requirements shall be enhanced. +- 2) Cell identification - Intra-frequency measurements: + - Option 1: The intra-frequency measurement requirement shall be enhanced. +- 3) Restriction on SMTC periodicity: + - Restriction on SMTC periodicity configuration are preferred in FR2 HST. +- 4) CSI-RS based L3 measurements: + - The analysis of the requirements to be de-prioritized. + +L1 measurements: + +- The L1 measurements shall be enhanced. + +#### 6.3.4.1 System-level evaluation of mobility performance by Nokia + +The simulation results are obtained from fully dynamic system-level simulations, which were carried out to evaluate RRM requirements and mobility performance under high-speed train scenarios in FR2. Simulations were performed with train speed 350 km/h in both uni- and bi-directional Scenario-A and -B. + +The results include “non-SFN and non-DPS” (i.e., without DPS) transmission scheme analysis corresponding to L3-mobility based on the traditional HO procedure. In these simulations, it is assumed that each BBU has only one RRH creating a more challenging mobility scenario due to longer delays. Alternatively, simulation results for Dynamic Point Selection (DPS) deployments assume that all RRHs are connected to the same BBU, i.e., the mobility is based on L1 measurements and is provided by beam management procedures instead of HO. + +Additionally, different settings are considered for DRX configurations in CONNECTED mode, including DRX disabled and DRX cycles of 40, 80, and 160 ms. + +On the RRH side, the number of Tx beams is chosen according to the deployment, i.e., only 1 Tx beam in Scenario-A, and 1 or 2 Tx beams in Scenario-B. + +Non-ideal PDCCH model is used with Aggregation Level (AL) 16. + +The simulation assumptions and parameters for the evaluation of mobility performance are shown in Table 6.3.8.1-1. The differences from these parameters are explicitly described in the sections below. + +##### 6.3.4.1.1 Legacy RRM requirement mobility performance + +In the sub-sections below the mobility performance results in HST FR2 deployments based on legacy, i.e., not enhanced, FR2 requirements are presented. + +In Table 6.3.4.1.1-1, we show parameters that are different from the ones presented in Table 6.3.8.1-1. + +**Table 6.3.4.1.1-1: Legacy simulation assumptions for mobility performance evaluation.** + +| Parameter | Value | +|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of beams per CPE panel | Enhanced requirements:
Uni-directional Scenario-A:
1 Rx beam (scaling factor 8 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
Rx beam is oriented parallel to the railway track towards the serving Tx beam.
Uni-directional Scenario-B:
8 Rx beams (scaling factor 8 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
Rx beam orientations (90 degrees is boresight of antenna panel): 55, 65, 75, 85, 95, 105, 115, 125 degrees (only first three are usable for RRHs north from track to be comparable with bi-directional case)
Bi-directional Scenario-B:
4 Rx beams (scaling factor 8 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
Rx beam orientations (90 degrees is boresight of antenna panel): 55, 65, 75, 85 degrees
Bi-directional Scenario-A:
1 Rx beam per panel (scaling factor 8 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
Two Rx beams of the CPE are oriented parallel to the railway track in opposite directions. | +| DRX | DRX disabled (DRX 0), 40, 80, 160 ms cycles | +| RRC measurement period
L1 RSRP measurement period | N=8 assumed in scaling
DRX 0: 480 ms
DRX 40: 1440 ms
DRX 80: 2880 ms
DRX 160: 5760 ms | +| Cell detection delay (T PSS/SSS_sync_intra ) | N = 8 is assumed in scaling
DRX 0: 600 ms
DRX 40: 1440 ms
DRX 80: 2880 ms
DRX 160: 5760 ms | +| RLM assumptions | N=8 assumed in scaling
T Evaluate_out_CSI-RS : 600, 3600, 7200, 14400 ms (DRX 0, 40, 80, 160)
T Evaluate_in_CSI-RS : 300, 1800, 3600, 7200 ms (DRX 0, 40, 80, 160) | +| BFD assumptions | N=8 assumed in scaling
T Evaluate_BFD_CSI-RS : 300, 1800, 3600, 7200 ms (DRX 0, 40, 80, 160) | +| PDCCH model | Non-ideal PDCCH model with AL16 | + +###### 6.3.4.1.1.1 Uni-directional Scenario-A without DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-A without DPS for both the case when train is traveling into same direction (Dir:Same in legends) as RRH beam are pointing to and into opposite direction (Dir:Opposite in legends). Figure 6.3.4.1.1-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. Ping-pong handover is observed when two handovers happen back and forth between two same cells in one second. It is observed that handover and ping-pong rates are the highest without DRX and gradually decrease when DRX cycle is increased. Significant drop in successful handovers is observed when train travels to opposite direction than RRH beams are pointed to and DRX is used. Ping-pongs are not observed in the cases with DRX configured. + +![Two bar charts showing handover and ping-pong handover rates for different DRX cycles and directions.](b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Handover rate per CPE per second (Scenario:A-unidir)', shows the handover rate (HO/CPE/s) for DRX cycles of 0, 40, 80, and 160 ms. The right chart, titled 'Ping-pong handover rate (Scenario:A-unidir)', shows the ping-pong handover rate (PP/HO \* 100 [%]) for the same DRX cycles. Both charts compare 'Dir:Same' (blue bars) and 'Dir:Opposite' (red bars). + +| DRX [ms] | HO/CPE/s (Dir:Same) | HO/CPE/s (Dir:Opposite) | PP/HO * 100 [%] (Dir:Same) | PP/HO * 100 [%] (Dir:Opposite) | +|----------|---------------------|-------------------------|----------------------------|--------------------------------| +| 0 | 0.15 | 0.15 | 4.0 | 3.3 | +| 40 | 0.14 | 0.04 | 0.0 | 0.0 | +| 80 | 0.14 | 0.01 | 0.0 | 0.0 | +| 160 | 0.13 | 0.01 | 0.0 | 0.0 | + +Two bar charts showing handover and ping-pong handover rates for different DRX cycles and directions. + +Figure 6.3.4.1.1.1-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.1.1-2 shows average time-of-stay in cell (RRH). It is observed that without DRX the time-of-stay in RRH is slightly lower than the time train with 350 km/h speed takes to travel the distance of one Ds of 700 meters (about 7.2 seconds). This result is due to ping-pongs observed in Figure 6.3.4.1.1.1-1. With DRX cycles 80-160 ms the time-of-stay increases to over 7 seconds. + +![Bar chart showing time-of-stay in cell for different DRX cycles and directions.](20938559c8eb02f499e31059759fea6d_img.jpg) + +The chart, titled 'Time-of-stay in cell (Scenario:A-unidir)', shows the time-of-stay in cell (ToS in cell [ms]) for DRX cycles of 0, 40, 80, and 160 ms. It compares 'Dir:Same' (blue bars) and 'Dir:Opposite' (red bars). + +| DRX [ms] | ToS in cell [ms] (Dir:Same) | ToS in cell [ms] (Dir:Opposite) | +|----------|-----------------------------|---------------------------------| +| 0 | 6500 | 6500 | +| 40 | 7000 | 7000 | +| 80 | 7200 | 7200 | +| 160 | 7500 | 7500 | + +Bar chart showing time-of-stay in cell for different DRX cycles and directions. + +Figure 6.3.4.1.1.1-2 Time-of-stay in cell + +Figure 6.3.4.1.1.1-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. Time-of-outage percentage per call includes all the sources of outage combined. This consists of handover execution time, the time it takes to perform radio link failure related procedures from observing radio link problem until re-establishment of connection and the time below -8 dB SINR conditions are observed in the simulation even prior to radio link problem can be detected based on filtering. It is observed from the results that significant outage is detected only in case train travels to opposite direction than RRHs are pointing to and DRX is used. + +![Two bar charts showing time-of-outage percentage and average time-of-outage duration for different DRX values and directions.](e91633da5160c8af51a4ace6d3347f53_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Time-of-outage percentage per call (Scenario:A-unidir)', shows the percentage of time the call is in outage for DRX values of 0, 40, 80, and 160 ms. The right chart, titled 'Average time-of-outage duration due to low SINR (Scenario:A-unidir)', shows the average duration in milliseconds for the same DRX values. Both charts compare 'Dir:Same' (blue bars) and 'Dir:Opposite' (red bars). + +| DRX [ms] | Time-of-outage percentage per call [%] (Dir:Same) | Time-of-outage percentage per call [%] (Dir:Opposite) | Average time-of-outage duration [ms] (Dir:Same) | Average time-of-outage duration [ms] (Dir:Opposite) | +|----------|---------------------------------------------------|-------------------------------------------------------|-------------------------------------------------|-----------------------------------------------------| +| 0 | ~0 | ~2 | ~0 | ~10 | +| 40 | ~0 | ~40 | ~0 | ~120 | +| 80 | ~0 | ~60 | ~0 | ~220 | +| 160 | ~0 | ~72 | ~0 | ~350 | + +Two bar charts showing time-of-outage percentage and average time-of-outage duration for different DRX values and directions. + +Figure 6.3.4.1.1.1-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.1.1-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). The results show that failure rate is very high in case train is traveling to opposite direction than RRH beams are pointing to and DRX is used in case of legacy RRM requirements. DRX 40 ms causes about 70% failure rate and DRX 80-160 ms causes even higher number of problems with over 80% failure rate in this scenario. No failures are observed when train is traveling into same direct as RRH beams are pointing to. + +![Bar chart showing inter-cell mobility failure rate for different DRX values and directions.](cc12ad6eea1541843baea43ae833b856_img.jpg) + +The chart, titled 'Inter-cell mobility failure rate (Scenario:A-unidir)', shows the failure rate percentage for DRX values of 0, 40, 80, and 160 ms. It compares 'Dir:Same' (blue bars) and 'Dir:Opposite' (red bars). The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF) \* 100 [%]. + +| DRX [ms] | Failure rate [%] (Dir:Same) | Failure rate [%] (Dir:Opposite) | +|----------|-----------------------------|---------------------------------| +| 0 | ~0 | ~2 | +| 40 | ~0 | ~70 | +| 80 | ~0 | ~88 | +| 160 | ~0 | ~88 | + +Bar chart showing inter-cell mobility failure rate for different DRX values and directions. + +Figure 6.3.4.1.1.1-4 Mobility failure rate + +Figure 6.3.4.1.2.1-5 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance except in the cases with DRX 40-160 ms and train traveling to opposite direction. + +![Figure 6.3.4.1.1.1-5: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160 ms) and directions (Same, Opposite) in Scenario-A-unidir. The x-axis ranges from 0 to 60 dB, and the y-axis ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The 'Dir:Same' curves are generally higher than the 'Dir:Opposite' curves for the same DRX cycle.](3881b390d52f27a35faedfc170916c86_img.jpg) + +Figure 6.3.4.1.1.1-5: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160 ms) and directions (Same, Opposite) in Scenario-A-unidir. The x-axis ranges from 0 to 60 dB, and the y-axis ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The 'Dir:Same' curves are generally higher than the 'Dir:Opposite' curves for the same DRX cycle. + +Figure 6.3.4.1.1.1-5 SINR distributions + +###### 6.3.4.1.1.2 Uni-directional Scenario-A with DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-A with DPS. Some of the observed statistics are of different type than in the section without DPS. Figure 6.3.4.1.1.2-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. Beam ping-pong is observed when two beam switches happen back and forth between two same beams in one second. Practically in Scenario-A with just one Tx beam per RRH this means ping-pongs between RRHs. In DPS case the same trend is observed in beam switches as with handovers in non-DPS case, without DRX the rates are the highest and gradually rates decrease when longer DRX cycles are used. The differences between the rates in train travel direction are rather low except in the case with DRX cycle 160 ms where beam switch rate drops significantly when train is traveling to opposite direction. + +![Figure 6.3.4.1.1.2-1: Beam switch and beam ping-pong rates. Two bar charts are shown. The left chart, 'Beam switch rate per CPE per second (Scenario:A-unidir)', shows rates for DRX cycles 0, 40, 80, and 160 ms for 'Dir:Same' (blue) and 'Dir:Opposite' (red). The right chart, 'Beam ping-pong rate (Scenario:A-unidir)', shows the percentage of ping-pong beam switches for the same DRX cycles and directions. In both charts, the 'Dir:Same' rates are generally higher than the 'Dir:Opposite' rates, especially for DRX cycles of 40 ms and above.](ead8d1841c351608343c98f30e5f3f07_img.jpg) + +Figure 6.3.4.1.1.2-1: Beam switch and beam ping-pong rates. Two bar charts are shown. The left chart, 'Beam switch rate per CPE per second (Scenario:A-unidir)', shows rates for DRX cycles 0, 40, 80, and 160 ms for 'Dir:Same' (blue) and 'Dir:Opposite' (red). The right chart, 'Beam ping-pong rate (Scenario:A-unidir)', shows the percentage of ping-pong beam switches for the same DRX cycles and directions. In both charts, the 'Dir:Same' rates are generally higher than the 'Dir:Opposite' rates, especially for DRX cycles of 40 ms and above. + +Figure 6.3.4.1.1.2-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.1.2-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. Similar trend is observed here as without DPS that the time-of-outage rates are very low when train is traveling to the same direction as RRH beams are pointing to and none of the outages are caused by low SINR. In the opposite direction time-of-outage starts to increase significantly when DRX cycles are 40 ms or longer. However, time-of-outage is significantly lower than without DPS due to lower delay when switching to different RRH location. Regardless of this the case of DRX cycle 160 ms has very significant time-of-outage in the opposite direction. + +![Two bar charts showing time-of-outage metrics for Scenario A-unidir. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. Both charts compare 'Dir:Same' (blue) and 'Dir:Opposite' (red) for DRX values of 0, 40, 80, and 160 ms.](730b6615db6d402580db1024a7f4e163_img.jpg) + +**Time-of-outage percentage per call (Scenario:A-unidir)** + +| DRX [ms] | Dir:Same [%] | Dir:Opposite [%] | +|----------|--------------|------------------| +| 0 | 0 | 0 | +| 40 | 0 | ~5 | +| 80 | ~1 | ~15 | +| 160 | ~1 | ~68 | + +**Average time-of-outage duration due to low SINR (Scenario:A-unidir)** + +| DRX [ms] | Dir:Same [ms] | Dir:Opposite [ms] | +|----------|---------------|-------------------| +| 0 | 0 | ~15 | +| 40 | 0 | ~65 | +| 80 | 0 | ~115 | +| 160 | 0 | ~240 | + +Two bar charts showing time-of-outage metrics for Scenario A-unidir. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. Both charts compare 'Dir:Same' (blue) and 'Dir:Opposite' (red) for DRX values of 0, 40, 80, and 160 ms. + +**Figure 6.3.4.1.1.2-2 Time-of-outage per call and time-of-outage duration due to low SINR** + +Figure 6.3.4.1.1.2-3 shows beam failure indication rate as percentage of BFIs per beam switches. Similar trend is observed without DPS that no failures happen among the studied DRX cycles when train is traveling to same direction as RRH beams are pointing to. In case of opposite direction, the failure indication rates are very high even with short DRX when legacy performance requirements are used with scaling factor 8. + +![Bar chart showing 'Beam failure indication rate (Scenario:A-unidir)' as a percentage of BFIs per beam switches. It compares 'Dir:Same' (blue) and 'Dir:Opposite' (red) for DRX values of 0, 40, 80, and 160 ms.](d0c2bd517f31d89b01136a1847bcdf33_img.jpg) + +**Beam failure indication rate (Scenario:A-unidir)** + +| DRX [ms] | Dir:Same [%] | Dir:Opposite [%] | +|----------|--------------|------------------| +| 0 | 0 | ~18 | +| 40 | 0 | ~82 | +| 80 | 0 | 100 | +| 160 | 0 | 100 | + +Bar chart showing 'Beam failure indication rate (Scenario:A-unidir)' as a percentage of BFIs per beam switches. It compares 'Dir:Same' (blue) and 'Dir:Opposite' (red) for DRX values of 0, 40, 80, and 160 ms. + +**Figure 6.3.4.1.1.2-3 Beam failure indication rate** + +Figure 6.3.4.1.1.2-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance except in the cases with DRX 40-160 ms and train traveling to opposite direction. However, the amount of low SINR samples below 0 dB are less common in cases of DRX 40-80 ms when DPS is used. + +![Figure 6.3.4.1.1.2-4: SINR distributions (Scenario:A-unidir). This is a cumulative distribution function (CDF) plot showing the SINR [dB] on the x-axis (ranging from -10 to 60) and the CDF on the y-axis (ranging from 0.0 to 1.0). The plot compares eight scenarios: DRX:0, Dir:Same (solid blue line); DRX:40, Dir:Same (solid red line); DRX:80, Dir:Same (solid green line); DRX:160, Dir:Same (solid cyan line); DRX:0, Dir:Opposite (dashed blue line); DRX:40, Dir:Opposite (dashed red line); DRX:80, Dir:Opposite (dashed green line); and DRX:160, Dir:Opposite (dashed cyan line). The 'Dir:Same' curves show a sharp increase in CDF starting around 30 dB SINR, while the 'Dir:Opposite' curves show a more gradual increase, with the DRX:160, Dir:Opposite curve being the highest at lower SINR values.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg) + +Figure 6.3.4.1.1.2-4: SINR distributions (Scenario:A-unidir). This is a cumulative distribution function (CDF) plot showing the SINR [dB] on the x-axis (ranging from -10 to 60) and the CDF on the y-axis (ranging from 0.0 to 1.0). The plot compares eight scenarios: DRX:0, Dir:Same (solid blue line); DRX:40, Dir:Same (solid red line); DRX:80, Dir:Same (solid green line); DRX:160, Dir:Same (solid cyan line); DRX:0, Dir:Opposite (dashed blue line); DRX:40, Dir:Opposite (dashed red line); DRX:80, Dir:Opposite (dashed green line); and DRX:160, Dir:Opposite (dashed cyan line). The 'Dir:Same' curves show a sharp increase in CDF starting around 30 dB SINR, while the 'Dir:Opposite' curves show a more gradual increase, with the DRX:160, Dir:Opposite curve being the highest at lower SINR values. + +Figure 6.3.4.1.1.2-4 SINR distributions + +###### 6.3.4.1.1.3 Uni-directional Scenario-B without DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-B without DPS. Also, comparison between 1 and 2 beams per RRH is included in this section. Figure 6.3.4.1.1.3-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. It is observed that without DRX the handover rate is the highest and it drops when DRX cycle 40 ms is used but remains at approximately same level with all simulated DRX cycles. This indicates that there is more time to perform handover in Scenario-B than in Scenario-A particularly when comparing the cases when train is traveling to opposite direction than the RRH beams are pointing to. It is also observed that without DRX there are higher handover and ping-pong rates with 1 beam per RRH than 2 beams per RRH. + +![Figure 6.3.4.1.1.3-1: Handover and ping-pong handover rates (Scenario:B-unidir). This figure contains two bar charts. The left chart, 'Handover rate per CPE per second (Scenario:B-unidir)', shows the handover rate for four DRX cycles (0, 40, 80, 160 ms) and four configurations: Dir:Same, RRHBeams:1 (blue solid bar); Dir:Opposite, RRHBeams:1 (red solid bar); Dir:Same, RRHBeams:2 (green solid bar); and Dir:Opposite, RRHBeams:2 (cyan cross-hatched bar). The right chart, 'Ping-pong handover rate (Scenario:B-unidir)', shows the ping-pong rate as a percentage of all handovers for the same configurations. In the handover rate chart, the rates are highest at DRX:0 (around 0.18-0.19) and drop to around 0.14 at DRX:40, remaining relatively stable for DRX:80 and DRX:160. In the ping-pong rate chart, the rates are highest at DRX:0 (around 16% for Dir:Opposite, RRHBeams:1) and drop significantly for DRX:40, 80, and 160.](1da66f5fec34c001912c84a9abf145d7_img.jpg) + +Figure 6.3.4.1.1.3-1: Handover and ping-pong handover rates (Scenario:B-unidir). This figure contains two bar charts. The left chart, 'Handover rate per CPE per second (Scenario:B-unidir)', shows the handover rate for four DRX cycles (0, 40, 80, 160 ms) and four configurations: Dir:Same, RRHBeams:1 (blue solid bar); Dir:Opposite, RRHBeams:1 (red solid bar); Dir:Same, RRHBeams:2 (green solid bar); and Dir:Opposite, RRHBeams:2 (cyan cross-hatched bar). The right chart, 'Ping-pong handover rate (Scenario:B-unidir)', shows the ping-pong rate as a percentage of all handovers for the same configurations. In the handover rate chart, the rates are highest at DRX:0 (around 0.18-0.19) and drop to around 0.14 at DRX:40, remaining relatively stable for DRX:80 and DRX:160. In the ping-pong rate chart, the rates are highest at DRX:0 (around 16% for Dir:Opposite, RRHBeams:1) and drop significantly for DRX:40, 80, and 160. + +Figure 6.3.4.1.1.3-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.1.3-2 shows average time-of-stay in cell (RRH). It is observed that without DRX the time-of-stay in RRH is significantly lower than the time train with 350 km/h speed takes to travel the distance of one Ds of 700 meters (about 7.2 seconds) particularly with 1 Tx beam per RRH. This result is due to ping-pongs observed in Figure 6.3.4.1.1.3-1 in similar way as in Scenario A. Time-of-stay is relatively close among all studied DRX cycles in this scenario and close to the expected time-of-stay based on Ds. + +![Figure 6.3.4.1.1.3-2: Time-of-stay in cell (Scenario:B-unidir). A bar chart showing ToS in cell [ms] for DRX cycles 0, 40, 80, and 160. The legend indicates four configurations: Dir:Same, RRHBears:1 (blue); Dir:Opposite, RRHBears:1 (red); Dir:Same, RRHBears:2 (green); and Dir:Opposite, RRHBears:2 (cyan).](9c888dd6588358989047de6ced8b2bdb_img.jpg) + +| DRX | Dir:Same, RRHBears:1 | Dir:Opposite, RRHBears:1 | Dir:Same, RRHBears:2 | Dir:Opposite, RRHBears:2 | +|-----|----------------------|--------------------------|----------------------|--------------------------| +| 0 | ~5500 | ~5000 | ~6500 | ~6000 | +| 40 | ~7000 | ~7000 | ~7000 | ~7000 | +| 80 | ~7000 | ~7000 | ~7000 | ~7000 | +| 160 | ~7000 | ~7000 | ~7000 | ~7000 | + +Figure 6.3.4.1.1.3-2: Time-of-stay in cell (Scenario:B-unidir). A bar chart showing ToS in cell [ms] for DRX cycles 0, 40, 80, and 160. The legend indicates four configurations: Dir:Same, RRHBears:1 (blue); Dir:Opposite, RRHBears:1 (red); Dir:Same, RRHBears:2 (green); and Dir:Opposite, RRHBears:2 (cyan). + +Figure 6.3.4.1.1.3-2 Time-of-stay in cell + +Figure 6.3.4.1.1.3-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that in Scenario-B the outage rates are very low compared to Scenario-A in case where train is traveling to opposite direction. Only in case of DRX cycle 160 ms there is significant increase in time-of-outage particularly with 2 RRH beams. Beam management becomes more challenging with long DRX and scaling factor 8. + +![Figure 6.3.4.1.1.3-3: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts are shown. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. Both charts are for DRX cycles 0, 40, 80, and 160 with the same four configurations as Figure 6.3.4.1.1.3-2.](ddfefccc6c2fcfadf4e398109548faf8_img.jpg) + +| DRX | Time-of-outage percentage per call [%] | | | | Average time-of-outage duration due to low SINR [ms] | | | | +|-----|----------------------------------------|--------------------------|----------------------|--------------------------|------------------------------------------------------|--------------------------|----------------------|--------------------------| +| | Dir:Same, RRHBears:1 | Dir:Opposite, RRHBears:1 | Dir:Same, RRHBears:2 | Dir:Opposite, RRHBears:2 | Dir:Same, RRHBears:1 | Dir:Opposite, RRHBears:1 | Dir:Same, RRHBears:2 | Dir:Opposite, RRHBears:2 | +| 0 | ~0.5 | ~0.5 | ~0.5 | ~0.5 | ~0 | ~0 | ~0 | ~0 | +| 40 | ~0.5 | ~0.5 | ~0.5 | ~0.5 | ~0 | ~0 | ~0 | ~0 | +| 80 | ~0.5 | ~0.5 | ~0.5 | ~0.5 | ~0 | ~0 | ~0 | ~5 | +| 160 | ~0.5 | ~2.0 | ~0.5 | ~8.5 | ~0 | ~50 | ~0 | ~45 | + +Figure 6.3.4.1.1.3-3: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts are shown. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. Both charts are for DRX cycles 0, 40, 80, and 160 with the same four configurations as Figure 6.3.4.1.1.3-2. + +Figure 6.3.4.1.1.3-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.1.3-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). There are no failures in Scenario-B except with DRX 160 ms and train traveling to opposite direction where about 2-8 % failure rate is observed. This is very significantly lower rate of failures than in the corresponding Scenario-A case. + +![Figure 6.3.4.1.1.3-4: Bar chart showing Inter-cell mobility failure rate (Scenario:B-unidir) for different DRX values (0, 40, 80, 160) and RRB configurations. The Y-axis is (RLF+HOF)/(HO+RLF+HOF) * 100 [%]. The X-axis is DRX. The legend indicates four configurations: Dir:Same, RRB:1; Dir:Opposite, RRB:1; Dir:Same, RRB:2; and Dir:Opposite, RRB:2. Failure rates are near zero for DRX 0, 40, and 80. At DRX 160, the failure rate for Dir:Opposite, RRB:2 is approximately 8.5%, while Dir:Opposite, RRB:1 is approximately 1.5%.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +Figure 6.3.4.1.1.3-4: Bar chart showing Inter-cell mobility failure rate (Scenario:B-unidir) for different DRX values (0, 40, 80, 160) and RRB configurations. The Y-axis is (RLF+HOF)/(HO+RLF+HOF) \* 100 [%]. The X-axis is DRX. The legend indicates four configurations: Dir:Same, RRB:1; Dir:Opposite, RRB:1; Dir:Same, RRB:2; and Dir:Opposite, RRB:2. Failure rates are near zero for DRX 0, 40, and 80. At DRX 160, the failure rate for Dir:Opposite, RRB:2 is approximately 8.5%, while Dir:Opposite, RRB:1 is approximately 1.5%. + +Figure 6.3.4.1.1.3-4 Mobility failure rate + +Figure 6.3.4.1.1.3-5 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support always high mobility performance in all cases except DRX 160 ms and train traveling to opposite direction. It is also observed than without DRX and DRX 40 ms there is clear gain in SINR from having 2 beams per RRH compared to 1 beam per RRH, but when longer DRX is applied the gain is no longer observed. This is caused by the delays in selecting optimal beams with longer DRX. + +![Figure 6.3.4.1.1.3-5: Two side-by-side CDF plots of SINR [dB] for Scenario-B-unidir. The left plot is for RRB:1 and the right plot is for RRB:2. Both plots show CDF on the Y-axis (0.0 to 1.0) and SINR [dB] on the X-axis (0 to 50). The legend for both plots includes: Dir:Same, DRX:0; Dir:Same, DRX:40; Dir:Same, DRX:80; Dir:Same, DRX:160; Dir:Opposite, DRX:0; Dir:Opposite, DRX:40; Dir:Opposite, DRX:80; and Dir:Opposite, DRX:160. In the RRB:1 plot, the Dir:Same, DRX:160 curve is shifted to the left (lower SINR) compared to others. In the RRB:2 plot, the Dir:Same, DRX:160 curve is shifted to the right (higher SINR) compared to others.](03b9c04a0552e519e849210b8e2bf596_img.jpg) + +Figure 6.3.4.1.1.3-5: Two side-by-side CDF plots of SINR [dB] for Scenario-B-unidir. The left plot is for RRB:1 and the right plot is for RRB:2. Both plots show CDF on the Y-axis (0.0 to 1.0) and SINR [dB] on the X-axis (0 to 50). The legend for both plots includes: Dir:Same, DRX:0; Dir:Same, DRX:40; Dir:Same, DRX:80; Dir:Same, DRX:160; Dir:Opposite, DRX:0; Dir:Opposite, DRX:40; Dir:Opposite, DRX:80; and Dir:Opposite, DRX:160. In the RRB:1 plot, the Dir:Same, DRX:160 curve is shifted to the left (lower SINR) compared to others. In the RRB:2 plot, the Dir:Same, DRX:160 curve is shifted to the right (higher SINR) compared to others. + +Figure 6.3.4.1.1.3-5 SINR distributions + +###### 6.3.4.1.1.4 Uni-directional Scenario-B with DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-B with DPS. Figure 6.3.4.1.1.4-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. It is observed that there are clearly more beam switches with 2 beams per RRH than 1 beam per RRH. However, beam ping-pongs are less common in case of 2 beams per RRH. As observed in previous scenarios beam switch and ping-pong rates gradually decrease when DRX in used. + +![Two bar charts showing beam switch and beam ping-pong rates for different DRX cycles and beam configurations.](7b96fce298a23fd76a01ff6c176c1059_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Beam switch rate per CPE per second (Scenario:B-unidir)', shows the beam switch rate for four DRX cycles (0, 40, 80, 160 ms). The right chart, titled 'Beam ping-pong rate (Scenario:B-unidir)', shows the beam ping-pong rate for the same DRX cycles. Both charts compare four scenarios: Dir:Same, RRHBeams:1 (blue solid); Dir:Opposite, RRHBeams:1 (red solid); Dir:Same, RRHBeams:2 (green hatched); and Dir:Opposite, RRHBeams:2 (cyan hatched). + +| DRX [ms] | Beam switch rate per CPE per second | | | | Beam ping-pong rate * 100 [%] | | | | +|----------|-------------------------------------|--------------------------|----------------------|--------------------------|-------------------------------|--------------------------|----------------------|--------------------------| +| | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +| 0 | 0.19 | 0.20 | 0.31 | 0.31 | 17.5 | 20.5 | 4.0 | 3.5 | +| 40 | 0.14 | 0.14 | 0.28 | 0.28 | 1.5 | 1.5 | 0.5 | 0.5 | +| 80 | 0.14 | 0.14 | 0.27 | 0.27 | 0.5 | 0.5 | 0.5 | 0.5 | +| 160 | 0.14 | 0.14 | 0.16 | 0.16 | 0.5 | 0.5 | 0.5 | 0.5 | + +Two bar charts showing beam switch and beam ping-pong rates for different DRX cycles and beam configurations. + +Figure 6.3.4.1.1.4-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.1.4-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that time-of-outage rates are very low without DRX and DRX up to 80 ms. Particularly in cases where train is traveling to opposite direction than RRHs are pointing to the time-of-outage rates increase when DRX cycle 160 ms is applied. + +![Two bar charts showing time-of-outage percentage per call and average time-of-outage duration due to low SINR for different DRX cycles and beam configurations.](396daa13ed7c232dff88770f1bf11cd7_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Time-of-outage percentage per call (Scenario:B-unidir)', shows the percentage of calls with time-of-outage for four DRX cycles (0, 40, 80, 160 ms). The right chart, titled 'Average time-of-outage duration due to low SINR (Scenario:B-unidir)', shows the average duration of time-of-outage in milliseconds for the same DRX cycles. Both charts compare the same four scenarios as the previous figure. + +| DRX [ms] | Time-of-outage per call [%] | | | | Time-of-outage duration [ms] | | | | +|----------|-----------------------------|--------------------------|----------------------|--------------------------|------------------------------|--------------------------|----------------------|--------------------------| +| | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +| 0 | 0.1 | 0.1 | 0.1 | 0.1 | 0 | 0 | 0 | 0 | +| 40 | 0.2 | 0.2 | 0.2 | 0.2 | 0 | 0 | 0 | 7.0 | +| 80 | 0.5 | 0.5 | 0.5 | 0.5 | 0 | 9.0 | 0 | 19.0 | +| 160 | 1.0 | 5.5 | 1.0 | 10.0 | 0 | 50.0 | 0 | 50.0 | + +Two bar charts showing time-of-outage percentage per call and average time-of-outage duration due to low SINR for different DRX cycles and beam configurations. + +Figure 6.3.4.1.1.4-2 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.1.4-3 shows beam failure indication rate as percentage of BFIs per beam switches. It is observed that failure indications only happen in significant rate with DRX 160 ms and when train is traveling to opposite direction. Also, in this case the failure rate is lower than in Scenario-A. + +![Bar chart titled 'Beam failure indication rate (Scenario:B-unidir)'. The y-axis is 'BF/Beam switches * 100 [%]' ranging from 0 to 40. The x-axis is 'DRX' with values 0, 40, 80, and 160. The legend shows four series: 'Dir:Same, RRHBears:1' (blue), 'Dir:Opposite, RRHBears:1' (red), 'Dir:Same, RRHBears:2' (green), and 'Dir:Opposite, RRHBears:2' (cyan). At DRX 0 and 40, all bars are at 0. At DRX 80, 'Dir:Same, RRHBears:1' and 'Dir:Same, RRHBears:2' are at 0, while 'Dir:Opposite, RRHBears:1' and 'Dir:Opposite, RRHBears:2' are at approximately 1%. At DRX 160, 'Dir:Same, RRHBears:1' and 'Dir:Same, RRHBears:2' are at 0, 'Dir:Opposite, RRHBears:1' is at approximately 23%, and 'Dir:Opposite, RRHBears:2' is at approximately 30%.](c742b64169a38a7f3f990172019878c8_img.jpg) + +Bar chart titled 'Beam failure indication rate (Scenario:B-unidir)'. The y-axis is 'BF/Beam switches \* 100 [%]' ranging from 0 to 40. The x-axis is 'DRX' with values 0, 40, 80, and 160. The legend shows four series: 'Dir:Same, RRHBears:1' (blue), 'Dir:Opposite, RRHBears:1' (red), 'Dir:Same, RRHBears:2' (green), and 'Dir:Opposite, RRHBears:2' (cyan). At DRX 0 and 40, all bars are at 0. At DRX 80, 'Dir:Same, RRHBears:1' and 'Dir:Same, RRHBears:2' are at 0, while 'Dir:Opposite, RRHBears:1' and 'Dir:Opposite, RRHBears:2' are at approximately 1%. At DRX 160, 'Dir:Same, RRHBears:1' and 'Dir:Same, RRHBears:2' are at 0, 'Dir:Opposite, RRHBears:1' is at approximately 23%, and 'Dir:Opposite, RRHBears:2' is at approximately 30%. + +Figure 6.3.4.1.1.4-3 Beam failure indication rate + +Figure 6.3.4.1.1.4-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance except it the cases with DRX 160 ms and train traveling to opposite direction. Also, DRX 80 ms causes some significant degradation in SINR in the opposite direction, but as observed from failure rates it does not cause high number of problems. + +![Two line graphs showing SINR distributions. The left graph is for 'RRHBears:1' and the right graph is for 'RRHBears:2'. Both have 'CDF' on the y-axis (0.0 to 1.0) and 'SINR [dB]' on the x-axis (0 to 50). The legend for both shows eight series: 'Dir:Same, DRX:0' (blue solid), 'Dir:Same, DRX:40' (red solid), 'Dir:Same, DRX:80' (green solid), 'Dir:Same, DRX:160' (cyan solid), 'Dir:Opposite, DRX:0' (blue dashed), 'Dir:Opposite, DRX:40' (red dashed), 'Dir:Opposite, DRX:80' (green dashed), and 'Dir:Opposite, DRX:160' (cyan dashed). In both graphs, the 'Dir:Same' curves are clustered together, starting around 20 dB and reaching a CDF of 1.0 by 40 dB. The 'Dir:Opposite' curves are shifted to the left, starting around 10 dB and reaching a CDF of 1.0 by 30 dB. The 'Dir:Opposite, DRX:160' curve is the leftmost, indicating the lowest SINR distribution.](5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg) + +Two line graphs showing SINR distributions. The left graph is for 'RRHBears:1' and the right graph is for 'RRHBears:2'. Both have 'CDF' on the y-axis (0.0 to 1.0) and 'SINR [dB]' on the x-axis (0 to 50). The legend for both shows eight series: 'Dir:Same, DRX:0' (blue solid), 'Dir:Same, DRX:40' (red solid), 'Dir:Same, DRX:80' (green solid), 'Dir:Same, DRX:160' (cyan solid), 'Dir:Opposite, DRX:0' (blue dashed), 'Dir:Opposite, DRX:40' (red dashed), 'Dir:Opposite, DRX:80' (green dashed), and 'Dir:Opposite, DRX:160' (cyan dashed). In both graphs, the 'Dir:Same' curves are clustered together, starting around 20 dB and reaching a CDF of 1.0 by 40 dB. The 'Dir:Opposite' curves are shifted to the left, starting around 10 dB and reaching a CDF of 1.0 by 30 dB. The 'Dir:Opposite, DRX:160' curve is the leftmost, indicating the lowest SINR distribution. + +Figure 6.3.4.1.1.4-4 SINR distributions + +###### 6.3.4.1.1.5 Bi-directional Scenario-B without DPS + +This section shows system level simulation mobility performance results for bi-directional Scenario-B without DPS. Figure 6.3.4.1.1.5-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. It is observed that general levels of handover and ping-pong rates are clearly higher in bi-directional scenario than in uni-directional scenario. Uni-directional Scenario-B has maximum of about 0.2 HO/CPE/s and bi-directional has over 0.8 HO/CPE/s. Ping-pongs are much more common even with DRX in bi-directional scenario. + +![Two bar charts showing handover and ping-pong handover rates for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1, RRHBeams:2).](509a054727400bc6d424bb2a559b8cfc_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Handover rate per CPE per second (Scenario:B-bidir)', shows the handover rate (HO/CPE/s) on the y-axis (0.0 to 1.2) against DRX cycles (0, 40, 80, 160) on the x-axis. The right chart, titled 'Ping-pong handover rate (Scenario:B-bidir)', shows the ping-pong handover rate (PP/HO \* 100 [%]) on the y-axis (0 to 50) against the same DRX cycles. Both charts compare two beam configurations: RRHBeams:1 (blue bars) and RRHBeams:2 (red bars with cross-hatch). In both cases, the rates decrease as the DRX cycle increases. RRHBeams:2 consistently shows higher handover and ping-pong rates than RRHBeams:1. + +| DRX | RRHBeams:1 (HO/CPE/s) | RRHBeams:2 (HO/CPE/s) | RRHBeams:1 (PP/HO * 100 [%]) | RRHBeams:2 (PP/HO * 100 [%]) | +|-----|-----------------------|-----------------------|------------------------------|------------------------------| +| 0 | ~0.5 | ~0.85 | ~20 | ~34 | +| 40 | ~0.3 | ~0.4 | ~2 | ~8 | +| 80 | ~0.25 | ~0.3 | ~1 | ~2 | +| 160 | ~0.1 | ~0.1 | ~0 | ~0 | + +Two bar charts showing handover and ping-pong handover rates for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1, RRHBeams:2). + +Figure 6.3.4.1.1.5-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.1.5-2 shows average time-of-stay in cell (RRH). It is observed that time-of-stay is significantly affected by DRX cycle and the number of beams per RRH. Generally, time-of-stay times in bi-directional scenario are about half of the times or lower in comparison to uni-directional scenario. + +![Bar chart showing the average time-of-stay in cell (RRH) for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1, RRHBeams:2).](16f235bb59e360d10bb35e523d3946b2_img.jpg) + +The chart, titled 'Time-of-stay in cell (Scenario:B-bidir)', shows the time-of-stay in milliseconds (ToS in cell [ms]) on the y-axis (0 to 10000) against DRX cycles (0, 40, 80, 160) on the x-axis. It compares RRHBeams:1 (blue bars) and RRHBeams:2 (red bars with cross-hatch). The time-of-stay increases with the DRX cycle for both configurations, with RRHBeams:2 consistently showing a longer time-of-stay than RRHBeams:1. + +| DRX | RRHBeams:1 (ToS in cell [ms]) | RRHBeams:2 (ToS in cell [ms]) | +|-----|-------------------------------|-------------------------------| +| 0 | ~2000 | ~1200 | +| 40 | ~3500 | ~2500 | +| 80 | ~4200 | ~3500 | +| 160 | ~7500 | ~7800 | + +Bar chart showing the average time-of-stay in cell (RRH) for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1, RRHBeams:2). + +Figure 6.3.4.1.1.5-2 Time-of-stay in cell + +Figure 6.3.4.1.1.5-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that time-of-outage percentage per call is higher in bi-directional scenario than in uni-directional scenario mainly due to increased handovers. However, also in bi-directional Scenario-B clearly increased outage is only seen when DRX cycle is set to 160 ms. + +![Figure 6.3.4.1.1.5-3: Time-of-outage per call and time-of-outage duration due to low SINR. The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (%)' for DRX cycles 0, 40, 80, and 160 ms, comparing RRHBeams:1 (blue) and RRHBeams:2 (red). The right chart shows 'Average time-of-outage duration due to low SINR [ms]' for the same DRX cycles and beam configurations. Both charts show that outage percentage and duration increase with DRX cycle length, and are significantly higher for RRHBeams:2 at 160 ms DRX.](835ebc0e9ec15eea8eadc15448249226_img.jpg) + +| DRX [ms] | RRHBeams | Time-of-outage percentage per call [%] | Average time-of-outage duration due to low SINR [ms] | +|----------|------------|----------------------------------------|------------------------------------------------------| +| 0 | RRHBeams:1 | ~2 | ~18 | +| 0 | RRHBeams:2 | ~4 | ~22 | +| 40 | RRHBeams:1 | ~1 | ~18 | +| 40 | RRHBeams:2 | ~2 | ~18 | +| 80 | RRHBeams:1 | ~2 | ~22 | +| 80 | RRHBeams:2 | ~3 | ~18 | +| 160 | RRHBeams:1 | ~20 | ~62 | +| 160 | RRHBeams:2 | ~25 | ~52 | + +Figure 6.3.4.1.1.5-3: Time-of-outage per call and time-of-outage duration due to low SINR. The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (%)' for DRX cycles 0, 40, 80, and 160 ms, comparing RRHBeams:1 (blue) and RRHBeams:2 (red). The right chart shows 'Average time-of-outage duration due to low SINR [ms]' for the same DRX cycles and beam configurations. Both charts show that outage percentage and duration increase with DRX cycle length, and are significantly higher for RRHBeams:2 at 160 ms DRX. + +Figure 6.3.4.1.1.5-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.1.5-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). It is observed that significant number of failures happen only with DRX cycle 160 ms. + +![Figure 6.3.4.1.1.5-4: Mobility failure rate. The chart shows the inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events) for DRX cycles 0, 40, 80, and 160 ms, comparing RRHBeams:1 (blue) and RRHBeams:2 (red). The failure rate is near zero for DRX 0, 40, and 80 ms, but increases significantly for DRX 160 ms, reaching approximately 24% for RRHBeams:1 and 34% for RRHBeams:2.](70546cb98239089866510133c7fbc169_img.jpg) + +| DRX [ms] | RRHBeams | Inter-cell mobility failure rate (RLF+HOF)/(HO+RLF+HOF) * 100 [%] | +|----------|------------|-------------------------------------------------------------------| +| 0 | RRHBeams:1 | ~0 | +| 0 | RRHBeams:2 | ~0 | +| 40 | RRHBeams:1 | ~0 | +| 40 | RRHBeams:2 | ~0 | +| 80 | RRHBeams:1 | ~0 | +| 80 | RRHBeams:2 | ~1 | +| 160 | RRHBeams:1 | ~24 | +| 160 | RRHBeams:2 | ~34 | + +Figure 6.3.4.1.1.5-4: Mobility failure rate. The chart shows the inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events) for DRX cycles 0, 40, 80, and 160 ms, comparing RRHBeams:1 (blue) and RRHBeams:2 (red). The failure rate is near zero for DRX 0, 40, and 80 ms, but increases significantly for DRX 160 ms, reaching approximately 24% for RRHBeams:1 and 34% for RRHBeams:2. + +Figure 6.3.4.1.1.5-4 Mobility failure rate + +Figure 6.3.4.1.1.5-5 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support always high mobility performance in all cases except DRX 160 ms. It is also observed than without DRX and DRX 40 ms there is clear gain in SINR from having 2 beams per RRH compared to 1 beam per RRH, but when longer DRX is applied the gain is no longer observed. This is caused by the delays in selecting optimal beams with longer DRX. It is noted that SINR level in low SINR percentiles is lower in bi-directional scenario than uni-directional Scenario-B. Possible reasons for this include using multi-panel UE assumption 1 in bi-directional scenario where two panels per CPE are used. With this assumption only one panel can be activated at the time and used for measurements causing some additional delays in mobility and beam management. + +![Figure 6.3.4.1.1.5-5: SINR distributions for Scenario-B-bidir with 1 and 2 beams per RRH. The figure contains two line graphs showing the CDF of SINR [dB] for DRX cycles of 0, 40, 80, and 160 ms. The left graph is for RRHBeams:1 and the right graph is for RRHBeams:2. In both cases, the SINR distribution shifts to the right (higher SINR) as the DRX cycle increases.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +Figure 6.3.4.1.1.5-5: SINR distributions for Scenario-B-bidir with 1 and 2 beams per RRH. The figure contains two line graphs showing the CDF of SINR [dB] for DRX cycles of 0, 40, 80, and 160 ms. The left graph is for RRHBeams:1 and the right graph is for RRHBeams:2. In both cases, the SINR distribution shifts to the right (higher SINR) as the DRX cycle increases. + +Figure 6.3.4.1.1.5-5 SINR distributions + +###### 6.3.4.1.1.6 Bi-directional Scenario-B with DPS + +This section shows system level simulation mobility performance results for bi-directional Scenario-B with DPS. Figure 6.3.4.1.1.6-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. It is observed that DRX cycle and the number of beams per RRH have significant impact on beam switch rate by decreasing rate when DRX cycle increases. There are more beam switches with 2 beams per RRH than 1 beam per RRH as would be expected in DPS scenario. + +![Figure 6.3.4.1.1.6-1: Beam switch and beam ping-pong rates for Scenario-B-bidir with DPS. The figure contains two bar charts. The left chart shows 'Beam switch rate per CPE per second' and the right chart shows 'Beam ping-pong rate (Beam PP/Beam switches * 100 [%])'. Both charts compare RRHBeams:1 (blue) and RRHBeams:2 (red) for DRX cycles of 0, 40, 80, and 160 ms. The beam switch rate decreases as DRX cycle increases, and RRHBeams:2 consistently shows a higher beam switch rate than RRHBeams:1. The ping-pong rate is highest for DRX 0 and decreases significantly for DRX 40, 80, and 160.](6381dcd91bf4636842734ec95bbd75d4_img.jpg) + +Figure 6.3.4.1.1.6-1: Beam switch and beam ping-pong rates for Scenario-B-bidir with DPS. The figure contains two bar charts. The left chart shows 'Beam switch rate per CPE per second' and the right chart shows 'Beam ping-pong rate (Beam PP/Beam switches \* 100 [%])'. Both charts compare RRHBeams:1 (blue) and RRHBeams:2 (red) for DRX cycles of 0, 40, 80, and 160 ms. The beam switch rate decreases as DRX cycle increases, and RRHBeams:2 consistently shows a higher beam switch rate than RRHBeams:1. The ping-pong rate is highest for DRX 0 and decreases significantly for DRX 40, 80, and 160. + +Figure 6.3.4.1.1.6-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.1.6-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that the outage percentage per call is lower in DPS scenario than without DPS. This is caused by lower outage time in beam switch than handover. Only with DRX 160 ms the outage rate significantly increases from the level without DRX. This can be caused by less optimal beam selection. + +![Two bar charts comparing RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. In both cases, outage increases with DRX cycle, but RRHBeams:2 generally shows higher outage than RRHBeams:1.](7c0a9511fa02b6c2c125ff5be465186e_img.jpg) + +| DRX | RRHBeams:1 (%) | RRHBeams:2 (%) | RRHBeams:1 (ms) | RRHBeams:2 (ms) | +|-----|----------------|----------------|-----------------|-----------------| +| 0 | ~0.5 | ~0.5 | ~18 | ~23 | +| 40 | ~1.0 | ~0.8 | ~32 | ~38 | +| 80 | ~1.5 | ~1.5 | ~32 | ~36 | +| 160 | ~3.0 | ~5.0 | ~34 | ~37 | + +Two bar charts comparing RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. In both cases, outage increases with DRX cycle, but RRHBeams:2 generally shows higher outage than RRHBeams:1. + +Figure 6.3.4.1.1.6-2 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.1.6-3 shows beam failure indication rate as percentage of BFIs per beam switches. Beam failure indication are only observed with DRX with generally more problems in the case with 1 beam per RRH. + +![Bar chart showing 'Beam failure indication rate (Scenario:B-bidir)' for RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The y-axis is 'BFI/Beam switches * 100 [%]'. RRHBeams:1 shows higher failure rates than RRHBeams:2 at DRX 40 and 160.](09b5a76dd3d981abcc585df1314ef30a_img.jpg) + +| DRX | RRHBeams:1 (%) | RRHBeams:2 (%) | +|-----|----------------|----------------| +| 0 | 0 | 0 | +| 40 | ~8.5 | ~3.0 | +| 80 | ~7.8 | ~3.5 | +| 160 | ~10.5 | ~9.0 | + +Bar chart showing 'Beam failure indication rate (Scenario:B-bidir)' for RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The y-axis is 'BFI/Beam switches \* 100 [%]'. RRHBeams:1 shows higher failure rates than RRHBeams:2 at DRX 40 and 160. + +Figure 6.3.4.1.1.6-3 Beam failure indication rate + +Figure 6.3.4.1.1.6-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance in the most cases. It is also observed that 2 beams per RRH only bring gain in cases where DRX cycle is lower than 80 ms. There is loss when the highest DRX cycle is used due to the least optimal beam management when longest delays are observed. + +![Two CDF plots of SINR distribution for RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The x-axis is SINR [dB] and the y-axis is CDF. RRHBeams:2 shows better performance (higher SINR) than RRHBeams:1 at DRX 40 and 80, but worse at DRX 160.](11e75fa5726229212e831adbab1c9890_img.jpg) + +Two CDF plots of SINR distribution for RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The x-axis is SINR [dB] and the y-axis is CDF. RRHBeams:2 shows better performance (higher SINR) than RRHBeams:1 at DRX 40 and 80, but worse at DRX 160. + +Figure 6.3.4.1.1.6-4 SINR distributions + +###### 6.3.4.1.1.7 Bi-directional Scenario-A without DPS + +This section shows system-level mobility performance simulation results for bi-directional Scenario-A without DPS with legacy RRM requirements. In addition to other parameters varied in the rest of the scenarios, the results with both multi-panel assumption 1 (MPUEAssumption:as1) and 3 (MPUEAssumption:as3) are shown here. With assumption 1, only one panel at a time can perform measurements and with assumption 3 both panels can measure at the same time. + +Figure 6.3.4.1.1.7-1 shows handover rate per CPE per second and ping-pong handover rate relative to all handovers. It is observed that assumption 3 increases the number of handovers, but not always the number of ping-pongs in this scenario. When measuring with both panels at the same time the measurements are more up to date, which may reduce back-and-forth ping-pong handovers. As seen in other scenarios, longer DRX cycles significantly reduce the number of handovers. + +![Figure 6.3.4.1.1.7-1: Handover and ping-pong handover rates. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX values 0, 40, 80, and 160. The left chart shows HO/CPE/s, and the right chart shows PP/HO * 100 [%].](0829927e13d750d95334585b41a1403d_img.jpg) + +**Handover rate per CPE per second (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 | MPUEAssumption:as3 | +|-----|--------------------|--------------------| +| 0 | ~0.38 | ~0.52 | +| 40 | ~0.11 | ~0.23 | +| 80 | ~0.05 | ~0.10 | +| 160 | ~0.03 | ~0.04 | + +**Ping-pong handover rate (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 | MPUEAssumption:as3 | +|-----|--------------------|--------------------| +| 0 | ~6.8 | ~2.0 | +| 40 | ~8.5 | ~2.1 | +| 80 | ~0.0 | ~2.1 | +| 160 | ~0.0 | ~0.0 | + +Figure 6.3.4.1.1.7-1: Handover and ping-pong handover rates. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX values 0, 40, 80, and 160. The left chart shows HO/CPE/s, and the right chart shows PP/HO \* 100 [%]. + +**Figure 6.3.4.1.1.7-1 Handover and ping-pong handover rates** + +Figure 6.3.4.1.1.7-2 shows average time-of-stay in a cell. In bi-directional scenario, time-of-stay is very short without DRX due to frequent handovers. The time-of-stay is generally longer with assumption 1 due to more delays in following the best radio conditions, causing less handover to occur. Also, longer DRX cycles increase the average time-of-stay in a cell. + +![Figure 6.3.4.1.1.7-2: Time-of-stay in cell. A bar chart comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX values 0, 40, 80, and 160. The y-axis shows ToS in cell [ms].](19e9097c72fbcb33376cec8aa00d3186_img.jpg) + +**Time-of-stay in cell (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 | MPUEAssumption:as3 | +|-----|--------------------|--------------------| +| 0 | ~2500 | ~2000 | +| 40 | ~4800 | ~3000 | +| 80 | ~7000 | ~5000 | +| 160 | ~9500 | ~7000 | + +Figure 6.3.4.1.1.7-2: Time-of-stay in cell. A bar chart comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX values 0, 40, 80, and 160. The y-axis shows ToS in cell [ms]. + +**Figure 6.3.4.1.1.7-2 Time-of-stay in cell** + +Figure 6.3.4.1.1.7-3 shows time-of-outage statistics for both the total percentage of outage conditions relative to call length and average durations of outage due to low SINR level. With legacy requirements, the time-of-outage is very significant even without DRX and when multi-panel UE assumption 1 is configured. This is caused by the long delays due to legacy scaling factor 8 particularly when train is traveling towards the serving beam and quickly passing through the RRH location. + +![Figure 6.3.4.1.1.7-3: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts are shown. The left chart shows 'Time-of-outage percentage per call [%]' for DRX values 0, 40, 80, and 160. The right chart shows 'Average time-of-outage duration due to low SINR [ms]' for the same DRX values. Both charts compare MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red).](a346e19f92f1699e3f96432c0464c957_img.jpg) + +**Time-of-outage percentage per call (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 [%] | MPUEAssumption:as3 [%] | +|-----|------------------------|------------------------| +| 0 | ~15 | ~2 | +| 40 | ~45 | ~40 | +| 80 | ~45 | ~55 | +| 160 | ~45 | ~65 | + +**Average time-of-outage duration due to low SINR (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 [ms] | MPUEAssumption:as3 [ms] | +|-----|-------------------------|-------------------------| +| 0 | ~20 | ~10 | +| 40 | ~120 | ~110 | +| 80 | ~200 | ~220 | +| 160 | ~300 | ~420 | + +Figure 6.3.4.1.1.7-3: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts are shown. The left chart shows 'Time-of-outage percentage per call [%]' for DRX values 0, 40, 80, and 160. The right chart shows 'Average time-of-outage duration due to low SINR [ms]' for the same DRX values. Both charts compare MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red). + +Figure 6.3.4.1.1.7-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.1.7-4 shows mobility failure rates, and it behaves in the similar way as time-of-outage. The failure rate is high particularly with DRX, but also without DRX in cases where assumption 1 is configured. + +![Figure 6.3.4.1.1.7-4: Mobility failure rate. A bar chart showing the inter-cell mobility failure rate for DRX values 0, 40, 80, and 160. The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF) * 100 [%]. It compares MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red).](f22e617a7aef13de5ffd8e390bfda1c3_img.jpg) + +**Inter-cell mobility failure rate (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 [%] | MPUEAssumption:as3 [%] | +|-----|------------------------|------------------------| +| 0 | ~10 | ~2 | +| 40 | ~50 | ~30 | +| 80 | ~65 | ~55 | +| 160 | ~70 | ~80 | + +Figure 6.3.4.1.1.7-4: Mobility failure rate. A bar chart showing the inter-cell mobility failure rate for DRX values 0, 40, 80, and 160. The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF) \* 100 [%]. It compares MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red). + +Figure 6.3.4.1.1.7-4 Mobility failure rate + +Figure 6.3.4.1.1.7-5 shows SINR distributions for all simulated DRX cycles and multi-panel assumptions. It is observed that with legacy requirements only cases without DRX can provide fast enough mobility procedures to maintain good SINR level. However, with assumption 1, also the case without DRX has significantly degraded SINR for over 5% of the samples. + +![Figure 6.3.4.1.1.7-5: SINR distributions. A line graph showing the CDF of SINR [dB] for various DRX cycles (0, 40, 80, 160) and assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis ranges from 0.0 to 1.0 CDF. The legend indicates: DRX:0, MPUEAssumption:as1 (solid blue); DRX:0, MPUEAssumption:as3 (dashed blue); DRX:40, MPUEAssumption:as1 (solid red); DRX:40, MPUEAssumption:as3 (dashed red); DRX:80, MPUEAssumption:as1 (solid green); DRX:80, MPUEAssumption:as3 (dashed green); DRX:160, MPUEAssumption:as1 (solid cyan); DRX:160, MPUEAssumption:as3 (dashed cyan).](3a1f7b7faea911108b9f2ec50c4dfffe_img.jpg) + +Figure 6.3.4.1.1.7-5: SINR distributions. A line graph showing the CDF of SINR [dB] for various DRX cycles (0, 40, 80, 160) and assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis ranges from 0.0 to 1.0 CDF. The legend indicates: DRX:0, MPUEAssumption:as1 (solid blue); DRX:0, MPUEAssumption:as3 (dashed blue); DRX:40, MPUEAssumption:as1 (solid red); DRX:40, MPUEAssumption:as3 (dashed red); DRX:80, MPUEAssumption:as1 (solid green); DRX:80, MPUEAssumption:as3 (dashed green); DRX:160, MPUEAssumption:as1 (solid cyan); DRX:160, MPUEAssumption:as3 (dashed cyan). + +Figure 6.3.4.1.1.7-5 SINR distributions + +###### 6.3.4.1.1.8 Bi-directional Scenario-A with DPS + +This section shows system-level mobility performance simulation results for bi-directional Scenario-A with DPS with legacy requirements. + +Figure 6.3.4.1.1.8-1 shows beam switch and beam ping-pong rates. The results show that the beam switch rate is significantly higher with multi-panel assumption 3, which is inline with the results seen in 6.3.4.1.1.7 for handovers in non-DPS case. Also, longer DRX cycles decrease the number of beam switches. Ping-pong rates are much more variant depending on DRX cycle where multi-panel assumptions are rather equal except in DRX 80 ms case, where there is higher ping-pong rate with assumption 3. + +![Figure 6.3.4.1.1.8-1: Beam switch and beam ping-pong rates. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles of 0, 40, 80, and 160 ms. The left chart shows 'Beam switch rate per CPE per second' and the right chart shows 'Beam ping-pong rate (Beam switches * 100 [%])'.](9b00c87003f634db9c30ca1d94fd932d_img.jpg) + +**Figure 6.3.4.1.1.8-1 Data: Beam switch and beam ping-pong rates** + +| DRX (ms) | Beam switch rate per CPE per second (as1) | Beam switch rate per CPE per second (as3) | Beam ping-pong rate (as1) | Beam ping-pong rate (as3) | +|----------|-------------------------------------------|-------------------------------------------|---------------------------|---------------------------| +| 0 | ~0.18 | ~0.55 | ~8.5 | ~8.0 | +| 40 | ~0.15 | ~0.48 | ~0.8 | ~0.8 | +| 80 | ~0.14 | ~0.45 | ~0.5 | ~4.5 | +| 160 | ~0.14 | ~0.22 | ~0.2 | ~0.2 | + +Figure 6.3.4.1.1.8-1: Beam switch and beam ping-pong rates. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles of 0, 40, 80, and 160 ms. The left chart shows 'Beam switch rate per CPE per second' and the right chart shows 'Beam ping-pong rate (Beam switches \* 100 [%])'. + +**Figure 6.3.4.1.1.8-1 Beam switch and beam ping-pong rates** + +Figure 6.3.4.1.1.8-2 shows time-of-outage statistics with DPS. The results show that the rates generally increase with longer DRX but are lower than in non-DPS case in 6.3.4.1.1.7. Non-DRX case does not cause significant outages with either assumption 1 or 3. Due to high delays caused by legacy requirements and DRX, the time-of-outage can be high with both multi-panel assumptions when the longest DRX cycle is used. + +![Figure 6.3.4.1.1.8-2: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles of 0, 40, 80, and 160 ms. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'.](33f2363ca24f377ba159c98c722f4746_img.jpg) + +**Figure 6.3.4.1.1.8-2 Data: Time-of-outage per call and time-of-outage duration due to low SINR** + +| DRX (ms) | Time-of-outage percentage per call [%] (as1) | Time-of-outage percentage per call [%] (as3) | Average time-of-outage duration due to low SINR [ms] (as1) | Average time-of-outage duration due to low SINR [ms] (as3) | +|----------|----------------------------------------------|----------------------------------------------|------------------------------------------------------------|------------------------------------------------------------| +| 0 | ~0.1 | ~0.1 | ~0 | ~0 | +| 40 | ~0.5 | ~4.0 | ~0 | ~35 | +| 80 | ~2.0 | ~8.5 | ~185 | ~55 | +| 160 | ~15.5 | ~22.0 | ~205 | ~100 | + +Figure 6.3.4.1.1.8-2: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles of 0, 40, 80, and 160 ms. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. + +**Figure 6.3.4.1.1.8-2 Time-of-outage per call and time-of-outage duration due to low SINR** + +Figure 6.3.4.1.1.8-3 shows beam failure indication rates in DPS scenario. It is observed that beam failures are either not observed at all or almost zero without DRX depending on the multi-panel assumption. However, when DRX cycle increases the failure indication rates become high with both assumptions. + +![Figure 6.3.4.1.1.8-3: Bar chart showing Beam failure indication rate (BF/Beam switches * 100 [%]) for DRX cycles 0, 40, 80, and 160. The chart compares two multi-panel assumptions: MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red). The y-axis ranges from 0 to 80. The x-axis shows DRX values. For DRX=0, both assumptions show 0%. For DRX=40, MPUEAssumption:as3 is approximately 20% and MPUEAssumption:as1 is 0%. For DRX=80, MPUEAssumption:as3 is approximately 22% and MPUEAssumption:as1 is approximately 5%. For DRX=160, MPUEAssumption:as3 is approximately 58% and MPUEAssumption:as1 is approximately 55%.](9e4179ffe4701bec67534299c4935049_img.jpg) + +| DRX | MPUEAssumption:as1 (%) | MPUEAssumption:as3 (%) | +|-----|------------------------|------------------------| +| 0 | 0 | 0 | +| 40 | 0 | 20 | +| 80 | 5 | 22 | +| 160 | 55 | 58 | + +Figure 6.3.4.1.1.8-3: Bar chart showing Beam failure indication rate (BF/Beam switches \* 100 [%]) for DRX cycles 0, 40, 80, and 160. The chart compares two multi-panel assumptions: MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red). The y-axis ranges from 0 to 80. The x-axis shows DRX values. For DRX=0, both assumptions show 0%. For DRX=40, MPUEAssumption:as3 is approximately 20% and MPUEAssumption:as1 is 0%. For DRX=80, MPUEAssumption:as3 is approximately 22% and MPUEAssumption:as1 is approximately 5%. For DRX=160, MPUEAssumption:as3 is approximately 58% and MPUEAssumption:as1 is approximately 55%. + +Figure 6.3.4.1.1.8-3 Beam failure indication rate + +Figure 6.3.4.1.1.8-4 shows SINR distributions for all simulated DRX cycles and multi-panel assumptions. It is observed that SINR significantly degrades when mobility delays are increased with DRX cycles. The SINR difference between multi-panel assumptions is not so clear as in non-DPS case in 6.3.4.1.1.7. Assumption 3 gives gain in median and peak percentiles of the CDF particularly without DRX, but assumption 1 can be better in low percentiles of the CDF. + +![Figure 6.3.4.1.1.8-4: CDF plot of SINR [dB] for various DRX cycles (0, 40, 80, 160) and multi-panel assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis (CDF) ranges from 0.0 to 1.0. The plot shows that as DRX cycles increase, the SINR distribution shifts to the left, indicating degradation. For DRX=0, MPUEAssumption:as3 (dashed green line) shows a higher CDF than MPUEAssumption:as1 (solid blue line) at low SINR values. For DRX=160, MPUEAssumption:as1 (solid cyan line) shows a higher CDF than MPUEAssumption:as3 (dashed cyan line) at low SINR values.](68d47da43cdd5782cac97f784b52c270_img.jpg) + +Figure 6.3.4.1.1.8-4: CDF plot of SINR [dB] for various DRX cycles (0, 40, 80, 160) and multi-panel assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis (CDF) ranges from 0.0 to 1.0. The plot shows that as DRX cycles increase, the SINR distribution shifts to the left, indicating degradation. For DRX=0, MPUEAssumption:as3 (dashed green line) shows a higher CDF than MPUEAssumption:as1 (solid blue line) at low SINR values. For DRX=160, MPUEAssumption:as1 (solid cyan line) shows a higher CDF than MPUEAssumption:as3 (dashed cyan line) at low SINR values. + +Figure 6.3.4.1.1.8-4 SINR distributions + +##### 6.3.4.1.2 Enhanced RRM requirement mobility performance + +In the sub-sections below the mobility performance results in HST FR2 deployments with enhanced requirements selected according to the number of Rx beams are presented, i.e., with scaling factors 2 for Scenario-A and 6 for Scenario-B. + +In Table 6.3.4.1.2-1, we are introducing the parameters that are different in between the baseline legacy FR2 RRM requirements (assuming scaling factor 8) and enhanced HST FR2 requirements. + +**Table 6.3.4.1.2-1: Enhanced simulation assumptions for mobility performance evaluation.** + +| Parameter | Value | +|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of beams per CPE panel |

Enhanced requirements:

Uni-directional Scenario-A:

  • - 1 Rx beam (scaling factor 2 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
  • - Rx beam is oriented parallel to the railway track towards the serving Tx beam.

Uni-directional Scenario-B:

  • - 6 Rx beams (scaling factor 6 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
  • - Rx beam orientations (90 degrees is boresight of antenna panel): 65, 75, 85, 95, 105, 115 degrees (only first three are usable for RRHs north from track to be comparable with bi-directional case)

Bi-directional Scenario-B:

  • - 3 Rx beams (scaling factor 6 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
  • - Rx beam orientations (90 degrees is boresight of antenna panel): 65, 75, 85 degrees

Bi-directional Scenario-A:

  • - 1 Rx beam per panel (scaling factor 2 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations)
  • - Two Rx beams of CPE are oriented parallel to the railway in opposite directions
| +| DRX | DRX disabled (DRX 0), 40, 80, 160 ms cycles | +| RRC measurement period
L1 RSRP measurement period |

Scaling factor N=2:

DRX 0: 120 ms

DRX 40: 360 ms

DRX 80: 720 ms

DRX 160: 1440 ms

Scaling factor N = 6:

DRX 0: 360 ms

DRX 40: 1080 ms

DRX 80: 2160 ms

DRX 160: 4320 ms

| +| Cell detection delay
(T PSS/SSS_sync_intra ) |

Scaling factor N=2:

DRX 0: 600 ms

DRX 40: 600 ms

DRX 80: 720 ms

DRX 160: 1440 ms

Scaling factor N = 6:

DRX 0: 600 ms

DRX 40: 1080 ms

DRX 80: 2160 ms

DRX 160: 4320 ms

| +| RLM assumptions |

Scaling factor N=2:

TEvaluate_out_CSI-RS: 600, 3600, 720, 14400 ms (DRX 0, 40, 80, 160)

Scaling factor N = 6:

TEvaluate_out_CSI-RS: 600, 3600, 720, 14400 ms (DRX 0, 40, 80, 160)

N310: 2 samples

N311: 2 samples

Qout threshold SINR: -8 dB

Qin threshold SINR: -6 dB

| + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BFD assumptions | Scaling factor N=2:
$T_{\text{Evaluate\_BFD\_CSI-RS}}$ : 300, 1800, 3600, 7200 ms (DRX 0, 40, 80, 160)
Scaling factor N = 6:
$T_{\text{Evaluate\_BFD\_CSI-RS}}$ : 300, 1800, 3600, 7200 ms (DRX 0, 40, 80, 160) | +| PDCCH model | Non-ideal PDCCH model with AL16 | + +###### 6.3.4.1.2.1 Uni-directional Scenario-A without DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-A without DPS for both the case when train is traveling into same direction (Dir:Same in legends) as RRH beam are pointing to and into opposite direction (Dir:Opposite in legends). Figure 6.3.4.1.2.1-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. Ping-pong handover is observed when two handovers happen back and forth between two same cells in one second. It is observed that handover and ping-pong rates are the highest without DRX and gradually decrease when DRX cycle is increased. Significant drop in successful handovers is observed when train travels to opposite direction than RRH beams are pointed to and DRX cycle is increased to 160 ms. + +![Figure 6.3.4.1.2.1-1: Handover and ping-pong handover rates. Two bar charts are shown. The left chart, 'Handover rate per CPE per second (Scenario:A-unidir)', shows HO/CPE/s for DRX values 0, 40, 80, and 160. The right chart, 'Ping-pong handover rate (Scenario:A-unidir)', shows PP/HO * 100 [%] for the same DRX values. Both charts compare 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions.](0577e933d8cc3e958649f0bc343fa804_img.jpg) + +| DRX | Dir:Same HO/CPE/s | Dir:Opposite HO/CPE/s | Dir:Same PP/HO [%] | Dir:Opposite PP/HO [%] | +|-----|-------------------|-----------------------|--------------------|------------------------| +| 0 | ~0.21 | ~0.18 | ~16 | ~11 | +| 40 | ~0.16 | ~0.15 | ~5 | ~3.5 | +| 80 | ~0.14 | ~0.14 | ~1 | ~2 | +| 160 | ~0.14 | ~0.05 | ~0.5 | ~0 | + +Figure 6.3.4.1.2.1-1: Handover and ping-pong handover rates. Two bar charts are shown. The left chart, 'Handover rate per CPE per second (Scenario:A-unidir)', shows HO/CPE/s for DRX values 0, 40, 80, and 160. The right chart, 'Ping-pong handover rate (Scenario:A-unidir)', shows PP/HO \* 100 [%] for the same DRX values. Both charts compare 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions. + +Figure 6.3.4.1.2.1-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.2.1-2 shows average time-of-stay in cell (RRH). It is observed that without DRX the time-of-stay in RRH is significantly lower than the time train with 350 km/h speed takes to travel the distance of one Ds of 700 meters (about 7.2 seconds). This result is due to ping-pongs observed in Figure 6.3.4.1.2.1-1. With DRX cycles 80-160 ms the time-of-stay increases to about 7 seconds. + +![Figure 6.3.4.1.2.1-2: Time-of-stay in cell. A bar chart titled 'Time-of-stay in cell (Scenario:A-unidir)' shows ToS in cell [ms] for DRX values 0, 40, 80, and 160. It compares 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions.](8026dfc35d27b22be0b88bb64d835759_img.jpg) + +| DRX | Dir:Same ToS [ms] | Dir:Opposite ToS [ms] | +|-----|-------------------|-----------------------| +| 0 | ~5000 | ~5500 | +| 40 | ~6200 | ~6500 | +| 80 | ~7000 | ~6800 | +| 160 | ~7000 | ~7000 | + +Figure 6.3.4.1.2.1-2: Time-of-stay in cell. A bar chart titled 'Time-of-stay in cell (Scenario:A-unidir)' shows ToS in cell [ms] for DRX values 0, 40, 80, and 160. It compares 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions. + +Figure 6.3.4.1.2.1-2 Time-of-stay in cell + +Figure 6.3.4.1.2.1-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. Time-of-outage percentage per call includes all the sources of outage combined. This consists of handover execution time, the time it takes to perform radio link failure related procedures from observing radio link problem until re-establishment of connection and the time below -8 dB SINR conditions are observed in the simulation even prior to radio link problem can be detected based on filtering. It is observed from the results that significant outage is detected only in case train travels to opposite direction than RRHs are pointing to and DRX cycles are 80 ms or longer. + +![Figure 6.3.4.1.2.1-3: Time-of-outage per call and time-of-outage duration due to low SINR. The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (%)' for DRX cycles of 0, 40, 80, and 160 ms. The right chart shows 'Time-of-outage duration (ms)' for the same DRX cycles. Both charts compare 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions. In both cases, the 'Dir:Opposite' bars show significantly higher values than 'Dir:Same' for DRX 80 and 160 ms.](ebb7b22e39bc5c9aab718fe98c50d90a_img.jpg) + +| DRX (ms) | Time-of-outage percentage per call (%) [Dir:Same] | Time-of-outage percentage per call (%) [Dir:Opposite] | Average time-of-outage duration (ms) [Dir:Same] | Average time-of-outage duration (ms) [Dir:Opposite] | +|----------|---------------------------------------------------|-------------------------------------------------------|-------------------------------------------------|-----------------------------------------------------| +| 0 | ~0 | ~0 | ~0 | ~0 | +| 40 | ~0 | ~0 | ~0 | ~0 | +| 80 | ~1 | ~5 | ~0 | ~60 | +| 160 | ~1 | ~38 | ~0 | ~380 | + +Figure 6.3.4.1.2.1-3: Time-of-outage per call and time-of-outage duration due to low SINR. The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (%)' for DRX cycles of 0, 40, 80, and 160 ms. The right chart shows 'Time-of-outage duration (ms)' for the same DRX cycles. Both charts compare 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions. In both cases, the 'Dir:Opposite' bars show significantly higher values than 'Dir:Same' for DRX 80 and 160 ms. + +Figure 6.3.4.1.2.1-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.2.1-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). It is seen that similarly as significant time-of-outage rates are observed only scenario where train travels to opposite direction than RRHs are pointing to causes mobility failures among the simulated DRX cycles. DRX 80 ms causes about 7% failure rate and DRX 160 ms causes very significant problems with over 60% failure rate in this scenario. No failures are observed when train is traveling into same direct as RRH beams are pointing to. + +![Figure 6.3.4.1.2.1-4: Mobility failure rate. The chart shows the inter-cell mobility failure rate ((RLF+HOF)/(HO+RLF+HOF) * 100 [%]) for DRX cycles of 0, 40, 80, and 160 ms. It compares 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions. The 'Dir:Opposite' bars show a failure rate of approximately 7% for DRX 80 ms and over 60% for DRX 160 ms, while 'Dir:Same' remains near 0%.](35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg) + +| DRX (ms) | Mobility failure rate [%] [Dir:Same] | Mobility failure rate [%] [Dir:Opposite] | +|----------|--------------------------------------|------------------------------------------| +| 0 | ~0 | ~0 | +| 40 | ~0 | ~0 | +| 80 | ~0 | ~7 | +| 160 | ~0 | ~65 | + +Figure 6.3.4.1.2.1-4: Mobility failure rate. The chart shows the inter-cell mobility failure rate ((RLF+HOF)/(HO+RLF+HOF) \* 100 [%]) for DRX cycles of 0, 40, 80, and 160 ms. It compares 'Dir:Same' (blue) and 'Dir:Opposite' (red) directions. The 'Dir:Opposite' bars show a failure rate of approximately 7% for DRX 80 ms and over 60% for DRX 160 ms, while 'Dir:Same' remains near 0%. + +Figure 6.3.4.1.2.1-4 Mobility failure rate + +Figure 6.3.4.1.2.1-5 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance except it the cases with DRX 80-160 ms and train traveling to opposite direction. + +![Figure 6.3.4.1.2.1-5: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160 ms) and directions (Same, Opposite). The x-axis ranges from 0 to 60 dB, and the y-axis ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The 'Dir:Same' curves are generally higher than the 'Dir:Opposite' curves for the same DRX cycle.](a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg) + +Figure 6.3.4.1.2.1-5: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160 ms) and directions (Same, Opposite). The x-axis ranges from 0 to 60 dB, and the y-axis ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The 'Dir:Same' curves are generally higher than the 'Dir:Opposite' curves for the same DRX cycle. + +Figure 6.3.4.1.2.1-5 SINR distributions + +###### 6.3.4.1.2.2 Uni-directional Scenario-A with DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-A with DPS. Some of the observed statistics are of different type than in the section without DPS. Figure 6.3.4.1.2.2-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. Beam ping-pong is observed when two beam switches happen back and forth between two same beams in one second. Practically in Scenario-A with just one Tx beam per RRH this means ping-pongs between RRHs. In DPS case the same trend is observed in beam switches as with handovers in non-DPS case, without DRX the rates are the highest and gradually rates decrease when longer DRX cycles are used. The differences between the rates in train travel direction are rather low. + +![Figure 6.3.4.1.2.2-1: Beam switch and beam ping-pong rates. Two bar charts are shown. The left chart, 'Beam switch rate per CPE per second (Scenario:A-unidir)', shows rates for DRX cycles 0, 40, 80, and 160 ms for 'Dir:Same' (blue) and 'Dir:Opposite' (red). The right chart, 'Beam ping-pong rate (Scenario:A-unidir)', shows the percentage of ping-pong beam switches for the same DRX cycles and directions. Both charts show that the rates decrease as the DRX cycle increases. The 'Dir:Same' rates are slightly higher than the 'Dir:Opposite' rates.](4927d63a43414d4dece73d18f3869d7c_img.jpg) + +Figure 6.3.4.1.2.2-1: Beam switch and beam ping-pong rates. Two bar charts are shown. The left chart, 'Beam switch rate per CPE per second (Scenario:A-unidir)', shows rates for DRX cycles 0, 40, 80, and 160 ms for 'Dir:Same' (blue) and 'Dir:Opposite' (red). The right chart, 'Beam ping-pong rate (Scenario:A-unidir)', shows the percentage of ping-pong beam switches for the same DRX cycles and directions. Both charts show that the rates decrease as the DRX cycle increases. The 'Dir:Same' rates are slightly higher than the 'Dir:Opposite' rates. + +Figure 6.3.4.1.2.2-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.2.2-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. Similar trend is observed here as without DPS that the time-of-outage rates are very low when train is traveling to the same direction as RRH beams are pointing to and none of the outages are caused by low SINR. In the opposite direction time-of-outage starts to increase significantly when DRX cycles are 80 ms or longer. However, time-of-outage is significantly lower than without DPS due to lower delay when switching to different RRH location. + +![Two bar charts showing time-of-outage metrics for different DRX cycles and directions.](92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Time-of-outage percentage per call (Scenario:A-unidir)', shows the percentage of time the call is in outage for DRX cycles of 0, 40, 80, and 160 ms. The right chart, titled 'Average time-of-outage duration due to low SINR (Scenario:A-unidir)', shows the average duration in milliseconds for the same DRX cycles. Both charts compare 'Dir:Same' (blue bars) and 'Dir:Opposite' (red bars). In both cases, the outage percentage and duration are significantly higher for the 'Dir:Opposite' case, especially at DRX 160 ms. + +| DRX [ms] | Time-of-outage per call [%] (Dir:Same) | Time-of-outage per call [%] (Dir:Opposite) | Average time-of-outage duration [ms] (Dir:Same) | Average time-of-outage duration [ms] (Dir:Opposite) | +|----------|----------------------------------------|--------------------------------------------|-------------------------------------------------|-----------------------------------------------------| +| 0 | 0 | 0 | 0 | 0 | +| 40 | 0 | 0 | 0 | 0 | +| 80 | 0 | 1 | 0 | 30 | +| 160 | 0 | 5 | 0 | 85 | + +Two bar charts showing time-of-outage metrics for different DRX cycles and directions. + +Figure 6.3.4.1.2.2-2 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.2.2-3 shows beam failure indication rate as percentage of BFIs per beam switches. Similar trend is observed without DPS that no failures happen among the studied DRX cycles when train is traveling to same direction as RRH beams are pointing to. Only in case of DRX cycle 80 ms or more failures are observed with train traveling to opposite direction. + +![Bar chart showing beam failure indication rate for different DRX cycles and directions.](72f8f68566ae1c43d361dd4b990b5631_img.jpg) + +The chart, titled 'Beam failure indication rate (Scenario:A-unidir)', shows the beam failure indication rate as a percentage of beam switches for DRX cycles of 0, 40, 80, and 160 ms. It compares 'Dir:Same' (blue bars) and 'Dir:Opposite' (red bars). The failure rate is zero for 'Dir:Same' across all DRX cycles. For 'Dir:Opposite', the failure rate is near zero at 40 ms, but increases to approximately 25% at 80 ms and 33% at 160 ms. + +| DRX [ms] | BFI/Beam switches * 100 [%] (Dir:Same) | BFI/Beam switches * 100 [%] (Dir:Opposite) | +|----------|----------------------------------------|--------------------------------------------| +| 0 | 0 | 0 | +| 40 | 0 | 0 | +| 80 | 0 | 25 | +| 160 | 0 | 33 | + +Bar chart showing beam failure indication rate for different DRX cycles and directions. + +Figure 6.3.4.1.2.2-3 Beam failure indication rate + +Figure 6.3.4.1.2.2-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance except in the cases with DRX 80-160 ms and train traveling to opposite direction. However, the amount of low SINR samples below 0 dB are less common even in these cases when DPS is used. + +![Figure 6.3.4.1.2.2-4: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160 ms) and directions (Same, Opposite) in Scenario A-unidir. The x-axis ranges from 0 to 60 dB, and the y-axis ranges from 0.0 to 1.0. All curves show a sharp increase in CDF between 30 dB and 50 dB, with the DRX:0, Dir:Same case reaching a CDF of 1.0 around 50 dB.](b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg) + +Figure 6.3.4.1.2.2-4: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160 ms) and directions (Same, Opposite) in Scenario A-unidir. The x-axis ranges from 0 to 60 dB, and the y-axis ranges from 0.0 to 1.0. All curves show a sharp increase in CDF between 30 dB and 50 dB, with the DRX:0, Dir:Same case reaching a CDF of 1.0 around 50 dB. + +Figure 6.3.4.1.2.2-4 SINR distributions + +###### 6.3.4.1.2.3 Uni-directional Scenario-B without DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-B without DPS. Also, comparison between 1 and 2 beams per RRH is included in this section. Figure 6.3.4.1.2.3-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. It is observed that without DRX the handover rate is the highest and it drops when DRX cycle 40 ms is used but remains at approximately same level with all simulated DRX cycles. This indicates that there is more time to perform handover in Scenario-B than in Scenario-A particularly when comparing the cases when train is traveling to opposite direction than the RRH beams are pointing to. It is also observed that without DRX there are higher handover and ping-pong rates with 1 beam per RRH than 2 beams per RRH. + +![Figure 6.3.4.1.2.3-1: Handover and ping-pong handover rates. Two bar charts are shown. The left chart, 'Handover rate per CPE per second (Scenario:B-unidir)', shows HO/CPE/s for DRX cycles 0, 40, 80, and 160 ms. The right chart, 'Ping-pong handover rate (Scenario:B-unidir)', shows PP/HO * 100 [%] for the same DRX cycles. Both charts compare four cases: Dir:Same, RRHBeams:1 (blue solid); Dir:Opposite, RRHBeams:1 (red solid); Dir:Same, RRHBeams:2 (green solid); and Dir:Opposite, RRHBeams:2 (cyan dashed). In the handover chart, rates are highest at DRX=0 and decrease at DRX=40, then remain relatively stable. In the ping-pong chart, the ping-pong rate is highest for Dir:Opposite, RRHBeams:1 at DRX=0 (approx. 19%) and decreases significantly for other cases and DRX cycles.](b7197f070e527f304350831936352031_img.jpg) + +Figure 6.3.4.1.2.3-1: Handover and ping-pong handover rates. Two bar charts are shown. The left chart, 'Handover rate per CPE per second (Scenario:B-unidir)', shows HO/CPE/s for DRX cycles 0, 40, 80, and 160 ms. The right chart, 'Ping-pong handover rate (Scenario:B-unidir)', shows PP/HO \* 100 [%] for the same DRX cycles. Both charts compare four cases: Dir:Same, RRHBeams:1 (blue solid); Dir:Opposite, RRHBeams:1 (red solid); Dir:Same, RRHBeams:2 (green solid); and Dir:Opposite, RRHBeams:2 (cyan dashed). In the handover chart, rates are highest at DRX=0 and decrease at DRX=40, then remain relatively stable. In the ping-pong chart, the ping-pong rate is highest for Dir:Opposite, RRHBeams:1 at DRX=0 (approx. 19%) and decreases significantly for other cases and DRX cycles. + +Figure 6.3.4.1.2.3-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.2.3-2 shows average time-of-stay in cell (RRH). It is observed that without DRX the time-of-stay in RRH is significantly lower than the time train with 350 km/h speed takes to travel the distance of one $D_s$ of 700 meters (about 7.2 seconds) particularly with 1 Tx beam per RRH. This result is due to ping-pongs observed in Figure 6.3.4.1.2.3-1 in similar way as in Scenario A. Time-of-stay is relatively close with all studied DRX cycles in this scenario. + +![Bar chart titled 'Time-of-stay in cell (Scenario:B-unidir)' showing ToS in cell [ms] for different DRX values (0, 40, 80, 160) and configurations (Dir:Same, RRHBeams:1; Dir:Opposite, RRHBeams:1; Dir:Same, RRHBeams:2; Dir:Opposite, RRHBeams:2).](8e21461e0c9384ec60322bedb1b1ab17_img.jpg) + +The chart shows the Time-of-stay in cell (ToS) in milliseconds for Scenario B-unidir across four DRX values: 0, 40, 80, and 160. For each DRX value, four configurations are shown: Dir:Same, RRHBeams:1 (blue solid); Dir:Opposite, RRHBeams:1 (red solid); Dir:Same, RRHBeams:2 (green solid); and Dir:Opposite, RRHBeams:2 (cyan with 'x' pattern). At DRX 0, ToS is approximately 5000, 5200, 6200, and 5800 ms respectively. At DRX 40, 80, and 160, all configurations show a ToS of approximately 7000 ms. + +| DRX | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +|-----|----------------------|--------------------------|----------------------|--------------------------| +| 0 | ~5000 | ~5200 | ~6200 | ~5800 | +| 40 | ~7000 | ~7000 | ~7000 | ~7000 | +| 80 | ~7000 | ~7000 | ~7000 | ~7000 | +| 160 | ~7000 | ~7000 | ~7000 | ~7000 | + +Bar chart titled 'Time-of-stay in cell (Scenario:B-unidir)' showing ToS in cell [ms] for different DRX values (0, 40, 80, 160) and configurations (Dir:Same, RRHBeams:1; Dir:Opposite, RRHBeams:1; Dir:Same, RRHBeams:2; Dir:Opposite, RRHBeams:2). + +Figure 6.3.4.1.2.3-2 Time-of-stay in cell + +Figure 6.3.4.1.2.3-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that in Scenario-B the outage rates are very low compared to Scenario-A in case where train is traveling to opposite direction. + +![Two bar charts titled 'Time-of-outage percentage per call (Scenario:B-unidir)' and 'Average time-of-outage duration due to low SINR (Scenario:B-unidir)' showing outage metrics for different DRX values (0, 40, 80, 160) and configurations.](a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg) + +The figure contains two bar charts. The left chart shows the 'Time-of-outage percentage per call' for Scenario B-unidir. The right chart shows the 'Average time-of-outage duration due to low SINR' for the same scenario. Both charts use the same configurations and DRX values as the previous chart. + +**Left Chart: Time-of-outage percentage per call** + +| DRX | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +|-----|----------------------|--------------------------|----------------------|--------------------------| +| 0 | ~0.8 | ~0.8 | ~0.6 | ~0.7 | +| 40 | ~0.5 | ~0.5 | ~0.5 | ~0.5 | +| 80 | ~0.5 | ~0.5 | ~0.5 | ~0.5 | +| 160 | ~0.5 | ~0.5 | ~0.5 | ~1.5 | + +**Right Chart: Average time-of-outage duration due to low SINR** + +| DRX | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +|-----|----------------------|--------------------------|----------------------|--------------------------| +| 0 | 0 | 0 | 0 | 0 | +| 40 | 0 | 0 | 0 | 0 | +| 80 | 0 | 0 | 0 | ~7 | +| 160 | 0 | ~12 | ~5 | ~25 | + +Two bar charts titled 'Time-of-outage percentage per call (Scenario:B-unidir)' and 'Average time-of-outage duration due to low SINR (Scenario:B-unidir)' showing outage metrics for different DRX values (0, 40, 80, 160) and configurations. + +Figure 6.3.4.1.2.3-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.2.3-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). There are no failures in Scenario-B except with DRX 160 ms, train traveling to opposite direction and 2 beams per RRH where about 1 % failure rate is observed. This is very significantly lower rate of failures than in the corresponding Scenario-A case. + +![Figure 6.3.4.1.2.3-4: Mobility failure rate plot. The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF) * 100 [%] and ranges from 0.0 to 4.0. The x-axis is labeled DRX and ranges from 0 to 160. The plot title is 'Inter-cell mobility failure rate (Scenario:B-unidir)'. The legend indicates four series: Dir:Same, RRHBears:1 (blue solid line); Dir:Opposite, RRHBears:1 (red solid line); Dir:Same, RRHBears:2 (green solid line); and Dir:Opposite, RRHBears:2 (cyan solid line). All series show a failure rate near 0% until DRX 160, where the Dir:Opposite, RRHBears:2 series shows a failure rate of approximately 1.0%.](e466e4c4fb08567a109bb959a765225c_img.jpg) + +Figure 6.3.4.1.2.3-4: Mobility failure rate plot. The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF) \* 100 [%] and ranges from 0.0 to 4.0. The x-axis is labeled DRX and ranges from 0 to 160. The plot title is 'Inter-cell mobility failure rate (Scenario:B-unidir)'. The legend indicates four series: Dir:Same, RRHBears:1 (blue solid line); Dir:Opposite, RRHBears:1 (red solid line); Dir:Same, RRHBears:2 (green solid line); and Dir:Opposite, RRHBears:2 (cyan solid line). All series show a failure rate near 0% until DRX 160, where the Dir:Opposite, RRHBears:2 series shows a failure rate of approximately 1.0%. + +Figure 6.3.4.1.2.3-4 Mobility failure rate + +Figure 6.3.4.1.2.3-5 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support always high mobility performance in all cases except DRX 160 ms and train traveling to opposite direction. It is also observed than without DRX and DRX 40 ms there is clear gain in SINR from having 2 beams per RRH compared to 1 beam per RRH, but when longer DRX is applied the gain is no longer observed. This is caused by the delays in selecting optimal beams for longer DRX. + +![Figure 6.3.4.1.2.3-5: SINR distributions. Two plots are shown. The left plot is titled 'SINR distribution (Scenario:B-unidir, RRHBears:1)' and the right plot is titled 'SINR distribution (Scenario:B-unidir, RRHBears:2)'. Both plots show the CDF of SINR [dB] on the x-axis (0 to 50) and CDF on the y-axis (0.0 to 1.0). The legend for both plots includes: Dir:Same, DRX:0 (blue solid line); Dir:Same, DRX:40 (red solid line); Dir:Same, DRX:80 (green solid line); Dir:Same, DRX:160 (cyan solid line); Dir:Opposite, DRX:0 (blue dashed line); Dir:Opposite, DRX:40 (red dashed line); Dir:Opposite, DRX:80 (green dashed line); and Dir:Opposite, DRX:160 (cyan dashed line). In the RRHBears:1 plot, the Dir:Same, DRX:160 series shows a lower SINR distribution. In the RRHBears:2 plot, the Dir:Same, DRX:160 series shows a higher SINR distribution compared to the RRHBears:1 plot.](28639a75145506e46966c11c1b995dd2_img.jpg) + +Figure 6.3.4.1.2.3-5: SINR distributions. Two plots are shown. The left plot is titled 'SINR distribution (Scenario:B-unidir, RRHBears:1)' and the right plot is titled 'SINR distribution (Scenario:B-unidir, RRHBears:2)'. Both plots show the CDF of SINR [dB] on the x-axis (0 to 50) and CDF on the y-axis (0.0 to 1.0). The legend for both plots includes: Dir:Same, DRX:0 (blue solid line); Dir:Same, DRX:40 (red solid line); Dir:Same, DRX:80 (green solid line); Dir:Same, DRX:160 (cyan solid line); Dir:Opposite, DRX:0 (blue dashed line); Dir:Opposite, DRX:40 (red dashed line); Dir:Opposite, DRX:80 (green dashed line); and Dir:Opposite, DRX:160 (cyan dashed line). In the RRHBears:1 plot, the Dir:Same, DRX:160 series shows a lower SINR distribution. In the RRHBears:2 plot, the Dir:Same, DRX:160 series shows a higher SINR distribution compared to the RRHBears:1 plot. + +Figure 6.3.4.1.2.3-5 SINR distributions + +###### 6.3.4.1.2.4 Uni-directional Scenario-B with DPS + +This section shows system level simulation mobility performance results for uni-directional Scenario-B with DPS. Figure 6.3.4.1.2.4-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. It is observed that there are clearly more beam switches with 2 beams per RRH than 1 beam per RRH. However, beam ping-pongs are less common in case of 2 beams per RRH. As observed in previous scenarios beam switch and ping-pong rates gradually decrease when DRX is used. + +![Figure 6.3.4.1.2.4-1: Beam switch and beam ping-pong rates. Two bar charts showing performance metrics for different DRX cycles (0, 40, 80, 160 ms) and beam configurations (Dir:Same, RRHBeams:1; Dir:Opposite, RRHBeams:1; Dir:Same, RRHBeams:2; Dir:Opposite, RRHBeams:2).](f68421f5d184c116a7061977a9057e63_img.jpg) + +**Figure 6.3.4.1.2.4-1 Beam switch and beam ping-pong rates** + +The figure contains two bar charts. The left chart shows 'Beam switch rate per CPE per second (Scenario:B-unidir)' with values ranging from 0.0 to 0.5. The right chart shows 'Beam ping-pong rate (Scenario:B-unidir)' with values ranging from 0 to 35. Both charts compare four scenarios across four DRX cycles (0, 40, 80, 160 ms). + +| DRX | Beam switch rate per CPE per second | | | | Beam ping-pong rate | | | | +|-----|-------------------------------------|--------------------------|----------------------|--------------------------|----------------------|--------------------------|----------------------|--------------------------| +| | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +| 0 | 0.22 | 0.24 | 0.33 | 0.34 | 22 | 26 | 7 | 7 | +| 40 | 0.15 | 0.15 | 0.28 | 0.28 | 2 | 2 | 1 | 1 | +| 80 | 0.14 | 0.14 | 0.27 | 0.27 | 1 | 1 | 0 | 0 | +| 160 | 0.14 | 0.14 | 0.22 | 0.22 | 0 | 0 | 0 | 0 | + +Figure 6.3.4.1.2.4-1: Beam switch and beam ping-pong rates. Two bar charts showing performance metrics for different DRX cycles (0, 40, 80, 160 ms) and beam configurations (Dir:Same, RRHBeams:1; Dir:Opposite, RRHBeams:1; Dir:Same, RRHBeams:2; Dir:Opposite, RRHBeams:2). + +Figure 6.3.4.1.2.4-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.2.4-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that time-of-outage rates are very low without DRX and DRX up to 80 ms. Particularly in cases where train is traveling to opposite direction than RRHs are pointing to the time-of-outage rates increase when DRX cycle 160 ms is applied. + +![Figure 6.3.4.1.2.4-2: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts showing performance metrics for different DRX cycles (0, 40, 80, 160 ms) and beam configurations (Dir:Same, RRHBeams:1; Dir:Opposite, RRHBeams:1; Dir:Same, RRHBeams:2; Dir:Opposite, RRHBeams:2).](86c32700ca76b0bc4154f5d9e07aab0e_img.jpg) + +**Figure 6.3.4.1.2.4-2 Time-of-outage per call and time-of-outage duration due to low SINR** + +The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (Scenario:B-unidir)' with values ranging from 0.0 to 4.0. The right chart shows 'Average time-of-outage duration due to low SINR (Scenario:B-unidir)' with values ranging from 0 to 40 ms. Both charts compare four scenarios across four DRX cycles (0, 40, 80, 160 ms). + +| DRX | Time-of-outage percentage per call [%] | | | | Average time-of-outage duration [ms] | | | | +|-----|----------------------------------------|--------------------------|----------------------|--------------------------|--------------------------------------|--------------------------|----------------------|--------------------------| +| | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +| 0 | 0.05 | 0.05 | 0.05 | 0.05 | 0 | 0 | 0 | 0 | +| 40 | 0.1 | 0.1 | 0.1 | 0.1 | 0 | 0 | 0 | 4 | +| 80 | 0.2 | 0.2 | 0.2 | 0.2 | 0 | 8 | 0 | 8 | +| 160 | 0.6 | 1.6 | 0.6 | 2.8 | 0 | 27 | 0 | 28 | + +Figure 6.3.4.1.2.4-2: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts showing performance metrics for different DRX cycles (0, 40, 80, 160 ms) and beam configurations (Dir:Same, RRHBeams:1; Dir:Opposite, RRHBeams:1; Dir:Same, RRHBeams:2; Dir:Opposite, RRHBeams:2). + +Figure 6.3.4.1.2.4-2 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.2.4-3 shows beam failure indication rate as percentage of BFIs per beam switches. It is observed that failure indications only happen with DRX 160 ms and when train is traveling to opposite direction. Also, in this case the failure rate is lower than in Scenario-A. + +![Figure 6.3.4.1.2.4-3: Beam failure indication rate. A bar chart showing the BF/Beam switches * 100 [%] for different DRX values (0, 40, 80, 160) and RRH configurations (RRHBeams:1 and RRHBeams:2) for two directions (Same and Opposite). The chart shows that the beam failure indication rate is highest for the 'Dir:Opposite, RRHBeams:2' configuration at DRX 160, reaching approximately 18%.](5e7b93195badf89e1fb645ae53d619bb_img.jpg) + +| DRX | Dir:Same, RRHBeams:1 | Dir:Opposite, RRHBeams:1 | Dir:Same, RRHBeams:2 | Dir:Opposite, RRHBeams:2 | +|-----|----------------------|--------------------------|----------------------|--------------------------| +| 0 | 0 | 0 | 0 | 0 | +| 40 | 0 | 0 | 0 | 0 | +| 80 | 0 | 0 | 0 | 0 | +| 160 | 0 | 18 | 0 | 18 | + +Figure 6.3.4.1.2.4-3: Beam failure indication rate. A bar chart showing the BF/Beam switches \* 100 [%] for different DRX values (0, 40, 80, 160) and RRH configurations (RRHBeams:1 and RRHBeams:2) for two directions (Same and Opposite). The chart shows that the beam failure indication rate is highest for the 'Dir:Opposite, RRHBeams:2' configuration at DRX 160, reaching approximately 18%. + +Figure 6.3.4.1.2.4-3 Beam failure indication rate + +Figure 6.3.4.1.2.4-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance except it the cases with DRX 160 ms and train traveling to opposite direction. + +![Figure 6.3.4.1.2.4-4: SINR distributions. Two cumulative distribution function (CDF) plots showing the SINR distribution for Scenario-B-unidirectional with RRHBeams:1 and RRHBeams:2. The plots show that the SINR distribution is generally higher for the 'Dir:Same' configurations compared to the 'Dir:Opposite' configurations, especially for DRX 160 ms.](4bdefd2be27926822b4c23a83c1ea32c_img.jpg) + +Figure 6.3.4.1.2.4-4: SINR distributions. Two cumulative distribution function (CDF) plots showing the SINR distribution for Scenario-B-unidirectional with RRHBeams:1 and RRHBeams:2. The plots show that the SINR distribution is generally higher for the 'Dir:Same' configurations compared to the 'Dir:Opposite' configurations, especially for DRX 160 ms. + +Figure 6.3.4.1.2.4-4 SINR distributions + +###### 6.3.4.1.2.5 Bi-directional Scenario-B without DPS + +This section shows system level simulation mobility performance results for bi-directional Scenario-B without DPS. Figure 6.3.4.1.2.5-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. It is observed that general levels of handover and ping-pong rates are clearly higher in bi-directional scenario than in uni-directional scenario. Uni-directional Scenario-B as maximum of about 0.2 HO/CPE/s and bi-directional has almost 0.7 HO/CPE/s. Ping-pongs are much more common even with DRX in bi-directional scenario. + +![Two bar charts showing handover and ping-pong handover rates for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1 and RRHBeams:2).](d461c6341beba90844ef785469cd757f_img.jpg) + +The figure contains two bar charts. The left chart, titled 'Handover rate per CPE per second (Scenario:B-bidir)', shows the handover rate (HO/CPE/s) on the y-axis (0.0 to 1.0) against DRX cycles (0, 40, 80, 160) on the x-axis. The right chart, titled 'Ping-pong handover rate (Scenario:B-bidir)', shows the ping-pong handover rate (PP/HO \* 100 [%]) on the y-axis (0 to 40) against the same DRX cycles. Both charts compare two beam configurations: RRHBeams:1 (blue bars) and RRHBeams:2 (red bars with cross-hatch). + +| DRX | RRHBeams:1 (HO/CPE/s) | RRHBeams:2 (HO/CPE/s) | RRHBeams:1 (PP/HO * 100 [%]) | RRHBeams:2 (PP/HO * 100 [%]) | +|-----|-----------------------|-----------------------|------------------------------|------------------------------| +| 0 | ~0.62 | ~0.70 | ~30 | ~23 | +| 40 | ~0.40 | ~0.58 | ~11 | ~22 | +| 80 | ~0.28 | ~0.38 | ~2 | ~10 | +| 160 | ~0.22 | ~0.25 | ~4 | ~3 | + +Two bar charts showing handover and ping-pong handover rates for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1 and RRHBeams:2). + +Figure 6.3.4.1.2.5-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.2.5-2 shows average time-of-stay in cell (RRH). It is observed that time-of-stay is significantly affected by DRX cycle and the number of beams per RRH. Generally, time-of-stay times in bi-directional scenario are about half of the times or lower in comparison to uni-directional scenario. + +![Bar chart showing the average time-of-stay in cell (RRH) for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1 and RRHBeams:2).](968957e79781017e2926107f764b6042_img.jpg) + +The chart, titled 'Time-of-stay in cell (Scenario:B-bidir)', shows the time-of-stay in cell (ToS in cell [ms]) on the y-axis (0 to 6000) against DRX cycles (0, 40, 80, 160) on the x-axis. It compares two beam configurations: RRHBeams:1 (blue bars) and RRHBeams:2 (red bars with cross-hatch). + +| DRX | RRHBeams:1 (ToS in cell [ms]) | RRHBeams:2 (ToS in cell [ms]) | +|-----|-------------------------------|-------------------------------| +| 0 | ~1600 | ~1500 | +| 40 | ~2500 | ~1800 | +| 80 | ~3500 | ~2800 | +| 160 | ~4200 | ~3800 | + +Bar chart showing the average time-of-stay in cell (RRH) for Scenario B-bidir across different DRX cycles (0, 40, 80, 160) and RRH beam configurations (RRHBeams:1 and RRHBeams:2). + +Figure 6.3.4.1.2.5-2 Time-of-stay in cell + +Figure 6.3.4.1.2.5-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that time-of-outage percentage per call is higher in bi-directional scenario than in uni-directional scenario mainly due to increased handovers. However, also in bi-directional Scenario-B clearly increased outage is only seen when DRX cycle is set to 160 ms. + +![Two bar charts comparing RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The left chart shows 'Time-of-outage percentage per call (%)' and the right chart shows 'Average time-of-outage duration due to low SINR (ms)'.](57261b803cf2db0e8feca169cb2c416b_img.jpg) + +**Figure 6.3.4.1.2.5-3 Data:** + +| DRX | RRHBeams:1 (%) | RRHBeams:2 (%) | +|-----|----------------|----------------| +| 0 | ~3.0 | ~3.0 | +| 40 | ~2.0 | ~3.0 | +| 80 | ~1.5 | ~2.5 | +| 160 | ~7.5 | ~11.0 | + + + +| DRX | RRHBeams:1 (ms) | RRHBeams:2 (ms) | +|-----|-----------------|-----------------| +| 0 | ~20 | ~22 | +| 40 | ~21 | ~28 | +| 80 | ~21 | ~20 | +| 160 | ~43 | ~34 | + +Two bar charts comparing RRHBeams:1 and RRHBeams:2 across DRX cycles (0, 40, 80, 160). The left chart shows 'Time-of-outage percentage per call (%)' and the right chart shows 'Average time-of-outage duration due to low SINR (ms)'. + +**Figure 6.3.4.1.2.5-3 Time-of-outage per call and time-of-outage duration due to low SINR** + +Figure 6.3.4.1.2.5-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). It is observed that significant number of failures happen only with DRX cycle 160 ms. + +![Bar chart showing 'Inter-cell mobility failure rate (RLF + HOF) * 100 (%)' for DRX cycles 0, 40, 80, and 160, comparing RRHBeams:1 and RRHBeams:2.](f356ce635bbbc30c7b6db50ecdb5dab4_img.jpg) + +**Figure 6.3.4.1.2.5-4 Data:** + +| DRX | RRHBeams:1 (%) | RRHBeams:2 (%) | +|-----|----------------|----------------| +| 0 | ~0.5 | 0 | +| 40 | 0 | 0 | +| 80 | 0 | 0 | +| 160 | ~4.5 | ~6.0 | + +Bar chart showing 'Inter-cell mobility failure rate (RLF + HOF) \* 100 (%)' for DRX cycles 0, 40, 80, and 160, comparing RRHBeams:1 and RRHBeams:2. + +**Figure 6.3.4.1.2.5-4 Mobility failure rate** + +Figure 6.3.4.1.2.5-5 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support always high mobility performance in all cases except DRX 160 ms. It is also observed than without DRX and DRX 40 ms there is clear gain in SINR from having 2 beams per RRH compared to 1 beam per RRH, but when longer DRX is applied the gain is no longer observed. This is caused by the delays in selecting optimal beams with longer DRX. It is noted that SINR level in low SINR percentiles is lower in bi-directional scenario than uni-directional Scenario-B. Possible reasons for this include using multi-panel UE assumption 1 in bi-directional scenario where two panels per CPE are used. With this assumption only one panel can be activated at the time and used for measurements causing some additional delays in mobility and beam management. + +![Figure 6.3.4.1.2.5-5 SINR distributions. Two line graphs showing the Cumulative Distribution Function (CDF) of SINR [dB] for Scenario-B-bidir. The left graph is for RRHBeams:1 and the right graph is for RRHBeams:2. Both graphs show four curves for DRX cycles: 0 (blue), 40 (red), 80 (green), and 160 (cyan). In both cases, the CDF curves are very close to each other, indicating that the SINR distribution is relatively independent of the DRX cycle and the number of beams per RRH in this scenario.](b7b9fb0d8504e5e0dc06d2f930fc2444_img.jpg) + +Figure 6.3.4.1.2.5-5 SINR distributions. Two line graphs showing the Cumulative Distribution Function (CDF) of SINR [dB] for Scenario-B-bidir. The left graph is for RRHBeams:1 and the right graph is for RRHBeams:2. Both graphs show four curves for DRX cycles: 0 (blue), 40 (red), 80 (green), and 160 (cyan). In both cases, the CDF curves are very close to each other, indicating that the SINR distribution is relatively independent of the DRX cycle and the number of beams per RRH in this scenario. + +Figure 6.3.4.1.2.5-5 SINR distributions + +###### 6.3.4.1.2.6 Bi-directional Scenario-B with DPS + +This section shows system level simulation mobility performance results for bi-directional Scenario-B with DPS. Figure 6.3.4.1.2.6-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. It is observed that DRX cycle and the number of beams per RRH have significant impact on beam switch rate by decreasing rate when DRX cycle increases. There are more beam switches with 2 beams per RRH than 1 beam per RRH as would be expected in DPS scenario. + +![Figure 6.3.4.1.2.6-1 Beam switch and beam ping-pong rates. Two bar charts for Scenario-B-bidir. The left chart shows 'Beam switch rate per CPE per second' and the right chart shows 'Beam PP/Beam switch * 100 [%]'. Both charts compare RRHBeams:1 (blue) and RRHBeams:2 (red) for DRX cycles of 0, 40, 80, and 160. In the left chart, the beam switch rate decreases as DRX increases, and is higher for 2 beams than 1 beam. In the right chart, the ping-pong rate is highest for DRX=0 and decreases significantly for higher DRX cycles, with 2 beams generally showing a higher ping-pong rate than 1 beam.](375a2a2390ed2a98edcfe0dff7c82dd0_img.jpg) + +Figure 6.3.4.1.2.6-1 Beam switch and beam ping-pong rates. Two bar charts for Scenario-B-bidir. The left chart shows 'Beam switch rate per CPE per second' and the right chart shows 'Beam PP/Beam switch \* 100 [%]'. Both charts compare RRHBeams:1 (blue) and RRHBeams:2 (red) for DRX cycles of 0, 40, 80, and 160. In the left chart, the beam switch rate decreases as DRX increases, and is higher for 2 beams than 1 beam. In the right chart, the ping-pong rate is highest for DRX=0 and decreases significantly for higher DRX cycles, with 2 beams generally showing a higher ping-pong rate than 1 beam. + +Figure 6.3.4.1.2.6-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.2.6-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed that the outage percentage per call is lower in DPS scenario than without DPS. This is caused by lower outage time in beam switch than handover. Only with DRX 160 ms the outage rate significantly increases from the level without DRX. This can be caused by less optimal beam selection. + +![Two bar charts comparing RRHBeams:1 and RRHBeams:2 across DRX values (0, 40, 80, 160). The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. In both cases, RRHBeams:2 generally shows higher outage percentages and durations than RRHBeams:1, especially at higher DRX values.](c41f93a5e921782a4d8e7705f52f74b5_img.jpg) + +| DRX | RRHBeams:1 (%) | RRHBeams:2 (%) | RRHBeams:1 (ms) | RRHBeams:2 (ms) | +|-----|----------------|----------------|-----------------|-----------------| +| 0 | ~0.4 | ~0.4 | ~15 | ~18 | +| 40 | ~0.5 | ~0.5 | ~20 | ~28 | +| 80 | ~0.9 | ~0.8 | ~28 | ~31 | +| 160 | ~1.3 | ~2.2 | ~31 | ~35 | + +Two bar charts comparing RRHBeams:1 and RRHBeams:2 across DRX values (0, 40, 80, 160). The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. In both cases, RRHBeams:2 generally shows higher outage percentages and durations than RRHBeams:1, especially at higher DRX values. + +Figure 6.3.4.1.2.6-2 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.2.6-3 shows beam failure indication rate as percentage of BFIs per beam switches. Only in case of DRX 160 ms a significant rate of failures is observed but remaining in low rate. This indicates good performance in beam management with DPS in bi-directional Scenario-B. + +![Bar chart showing 'Beam failure indication rate (Scenario:B-bidir)' for RRHBeams:1 and RRHBeams:2 across DRX values (0, 40, 80, 160). The y-axis is 'BFI/Beam switches * 100 [%]'. Failures are only significant at DRX 160, where RRHBeams:2 has a higher rate (~1.1%) compared to RRHBeams:1 (~0.2%).](993d36ea4a6a2610f938b1fb97e7c34a_img.jpg) + +| DRX | RRHBeams:1 (%) | RRHBeams:2 (%) | +|-----|----------------|----------------| +| 0 | 0.0 | 0.0 | +| 40 | 0.0 | ~0.1 | +| 80 | 0.0 | 0.0 | +| 160 | ~0.2 | ~1.1 | + +Bar chart showing 'Beam failure indication rate (Scenario:B-bidir)' for RRHBeams:1 and RRHBeams:2 across DRX values (0, 40, 80, 160). The y-axis is 'BFI/Beam switches \* 100 [%]'. Failures are only significant at DRX 160, where RRHBeams:2 has a higher rate (~1.1%) compared to RRHBeams:1 (~0.2%). + +Figure 6.3.4.1.2.6-3 Beam failure indication rate + +Figure 6.3.4.1.2.6-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance in the most cases. It is also observed that 2 beams per RRH only bring gain in cases where DRX cycle is lower than 160 ms. There is loss when the highest DRX cycle is used due to the least optimal beam management when longest delays are observed. + +![Two CDF plots showing 'SINR distribution (Scenario:B-bidir, RRHBeams:1)' and 'SINR distribution (Scenario:B-bidir, RRHBeams:2)' for DRX values 0, 40, 80, and 160. The x-axis is SINR [dB] and the y-axis is CDF. The plots show that for lower DRX values, the SINR distribution is shifted to the right (higher SINR), indicating better performance. For DRX 160, the distribution is shifted to the left (lower SINR), indicating a loss in performance.](b5cf6e10fd65716d44c985f7c90ae2cb_img.jpg) + +Two CDF plots showing 'SINR distribution (Scenario:B-bidir, RRHBeams:1)' and 'SINR distribution (Scenario:B-bidir, RRHBeams:2)' for DRX values 0, 40, 80, and 160. The x-axis is SINR [dB] and the y-axis is CDF. The plots show that for lower DRX values, the SINR distribution is shifted to the right (higher SINR), indicating better performance. For DRX 160, the distribution is shifted to the left (lower SINR), indicating a loss in performance. + +Figure 6.3.4.1.2.6-4 SINR distributions + +###### 6.3.4.1.2.7 Bi-directional Scenario-A without DPS + +This section shows system level mobility performance simulation results for bi-directional Scenario-A without DPS with enhanced RRM requirements. In addition to other parameters varied in the rest of the scenario the results with both multi-panel assumption 1 (MPUEAssumption:as1) and 3 (MPUEAssumption:as3) are shown here. With assumption 1, only one panel at a time can perform measurements and with assumption 3 both panels can measurement at the same time. + +Figure 6.3.4.1.2.7-1 shows handover rate per CPE per second and ping-pong handover rate. It is observed that assumption 3 increases the number of handovers, but not the number of ping-pongs in this scenario. When measuring with both panels at the same time, the measurements are more up to date, which may reduce back-and-forth ping-pong handovers. As it can be seen in other scenarios, longer DRX cycles significantly reduce the number of handovers. Enhanced requirements increase the number of handovers compared to legacy requirements due to lower mobility delays from measurements. + +![Figure 6.3.4.1.2.7-1: Handover and ping-pong handover rates. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles 0, 40, 80, and 160. The left chart shows HO/CPE/s, and the right chart shows PP/HO * 100 [%].](607a666ece1fb3bad30cbe1e61ea0cc6_img.jpg) + +**Handover rate per CPE per second (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 (HO/CPE/s) | MPUEAssumption:as3 (HO/CPE/s) | +|-----|-------------------------------|-------------------------------| +| 0 | ~0.68 | ~0.70 | +| 40 | ~0.50 | ~0.52 | +| 80 | ~0.30 | ~0.50 | +| 160 | ~0.15 | ~0.20 | + +**Ping-pong handover rate (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 (PP/HO * 100 [%]) | MPUEAssumption:as3 (PP/HO * 100 [%]) | +|-----|--------------------------------------|--------------------------------------| +| 0 | ~32 | ~20 | +| 40 | ~40 | ~5 | +| 80 | ~5 | ~2 | +| 160 | ~8 | ~2 | + +Figure 6.3.4.1.2.7-1: Handover and ping-pong handover rates. Two bar charts comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles 0, 40, 80, and 160. The left chart shows HO/CPE/s, and the right chart shows PP/HO \* 100 [%]. + +**Figure 6.3.4.1.2.7-1 Handover and ping-pong handover rates** + +Figure 6.3.4.1.2.7-2 shows average time-of-stay in a cell. In bi-directional scenario, time-of-stay is very short without DRX due to frequent handovers. The time-of-stay increases with longer DRX cycles. The time-of-stay is generally shorter with enhanced requirements due to lower mobility delays compared to legacy requirements. + +![Figure 6.3.4.1.2.7-2: Time-of-stay in cell. A bar chart comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles 0, 40, 80, and 160. The Y-axis shows ToS in cell [ms].](0a21b415410e479aa4b83cae918f6272_img.jpg) + +**Time-of-stay in cell (Scenario:A-bidir)** + +| DRX | MPUEAssumption:as1 (ToS in cell [ms]) | MPUEAssumption:as3 (ToS in cell [ms]) | +|-----|---------------------------------------|---------------------------------------| +| 0 | ~1500 | ~1500 | +| 40 | ~1800 | ~2000 | +| 80 | ~2800 | ~2000 | +| 160 | ~4200 | ~3500 | + +Figure 6.3.4.1.2.7-2: Time-of-stay in cell. A bar chart comparing MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red) across DRX cycles 0, 40, 80, and 160. The Y-axis shows ToS in cell [ms]. + +**Figure 6.3.4.1.2.7-2 Time-of-stay in cell** + +Figure 6.3.4.1.2.7-3 shows time-of-outage statistics for both the total percentage of outage conditions relative to call length and average durations of outage due to low SINR level. Even with enhanced requirements the time-of-outage is very significant when multi-panel UE assumption 1 is configured and DRX is used. With longest DRX cycle, also outage with assumption 3 is high. However, the outage rates are much lower with these enhanced requirements than the legacy requirements. + +![Figure 6.3.4.1.2.7-3: Time-of-outage per call and time-of-outage duration due to low SINR. The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (Scenario:A-bidir)' with values for DRX 0, 40, 80, and 160. The right chart shows 'Average time-of-outage duration due to low SINR (Scenario:A-bidir)' with values for DRX 0, 40, 80, and 160. Both charts compare MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red).](eec47775133f5c3b02d42ab8f85599ce_img.jpg) + +**Figure 6.3.4.1.2.7-3 Data: Time-of-outage per call and time-of-outage duration due to low SINR** + +| DRX | MPUEAssumption:as1 (%) | MPUEAssumption:as3 (%) | MPUEAssumption:as1 (ms) | MPUEAssumption:as3 (ms) | +|-----|------------------------|------------------------|-------------------------|-------------------------| +| 0 | ~8 | ~3 | ~20 | ~5 | +| 40 | ~21 | ~3 | ~90 | ~10 | +| 80 | ~21 | ~4 | ~150 | ~40 | +| 160 | ~37 | ~40 | ~450 | ~410 | + +Figure 6.3.4.1.2.7-3: Time-of-outage per call and time-of-outage duration due to low SINR. The figure contains two bar charts. The left chart shows 'Time-of-outage percentage per call (Scenario:A-bidir)' with values for DRX 0, 40, 80, and 160. The right chart shows 'Average time-of-outage duration due to low SINR (Scenario:A-bidir)' with values for DRX 0, 40, 80, and 160. Both charts compare MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red). + +**Figure 6.3.4.1.2.7-3 Time-of-outage per call and time-of-outage duration due to low SINR** + +Figure 6.3.4.1.2.7-4 shows mobility failure rates, and it is observed that in the similar way as time-of-outage, the failure rate is high particularly with DRX, but also without DRX in cases where assumption 1 is configured. However, the failure rates are much lower with these enhanced requirements than the legacy requirements. + +![Figure 6.3.4.1.2.7-4: Mobility failure rate. The chart shows 'Inter-cell mobility failure rate (Scenario:A-bidir)' with values for DRX 0, 40, 80, and 160. It compares MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red).](3cde6c4c2ef7528574b0dbbc1b3e23aa_img.jpg) + +**Figure 6.3.4.1.2.7-4 Data: Mobility failure rate** + +| DRX | MPUEAssumption:as1 (%) | MPUEAssumption:as3 (%) | +|-----|------------------------|------------------------| +| 0 | ~4 | ~0 | +| 40 | ~15 | ~0 | +| 80 | ~18 | ~1 | +| 160 | ~37 | ~36 | + +Figure 6.3.4.1.2.7-4: Mobility failure rate. The chart shows 'Inter-cell mobility failure rate (Scenario:A-bidir)' with values for DRX 0, 40, 80, and 160. It compares MPUEAssumption:as1 (blue) and MPUEAssumption:as3 (red). + +**Figure 6.3.4.1.2.7-4 Mobility failure rate** + +Figure 6.3.4.1.2.7-5 shows SINR distributions for all simulated DRX cycles and multi-panel assumptions. It is observed that with enhanced requirements DRX cycles up to 80 ms with multi-panel assumption 3 can provide fast enough mobility procedures to maintain a good SINR level. Also, multi-panel assumption 1 can provide good SINR without DRX in over 95% of the samples. Higher DRX cycles have significantly degraded SINRs with assumption 1. + +![Figure 6.3.4.1.2.7-5 SINR distributions: A line graph showing the CDF of SINR [dB] for various DRX cycles (0, 40, 80, 160) and MPUE assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis (CDF) ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The MPUE assumption as3 generally shows higher SINR values than as1 for the same DRX cycle.](e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg) + +Figure 6.3.4.1.2.7-5 SINR distributions: A line graph showing the CDF of SINR [dB] for various DRX cycles (0, 40, 80, 160) and MPUE assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis (CDF) ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The MPUE assumption as3 generally shows higher SINR values than as1 for the same DRX cycle. + +Figure 6.3.4.1.2.7-5 SINR distributions + +###### 6.3.4.1.2.8 Bi-directional Scenario-A with DPS + +This section shows system level mobility performance simulation results for bi-directional Scenario-A with DPS with enhanced RRM requirements. + +Figure 6.3.4.1.2.8-1 shows beam switch and beam ping-pong rates. The results show that the beam switch rate is significantly higher with multi-panel assumption 3, except in the case without DRX where the numbers are rather equal. Also, longer DRX cycles decrease the number of beam switches. The beam switch rate is generally higher with enhanced requirements compared to legacy requirements. Ping-pong rates are quite equal between the multi-panel assumptions. + +![Figure 6.3.4.1.2.8-1 Beam switch and beam ping-pong rates: Two bar charts. The left chart shows 'Beam switch rate per CPE per second (Scenario-A-bidir)' for DRX cycles 0, 40, 80, and 160. The right chart shows 'Beam ping-pong rate (Scenario-A-bidir)' for the same DRX cycles. Both charts compare MPUE assumption as1 (blue) and MPUE assumption as3 (red). In the beam switch chart, as3 is higher than as1 for DRX 40, 80, and 160, but they are nearly equal for DRX 0. In the beam ping-pong chart, the values for as1 and as3 are very similar across all DRX cycles.](7d4b12c72fdecde31d1c594d7ce11eee_img.jpg) + +Figure 6.3.4.1.2.8-1 Beam switch and beam ping-pong rates: Two bar charts. The left chart shows 'Beam switch rate per CPE per second (Scenario-A-bidir)' for DRX cycles 0, 40, 80, and 160. The right chart shows 'Beam ping-pong rate (Scenario-A-bidir)' for the same DRX cycles. Both charts compare MPUE assumption as1 (blue) and MPUE assumption as3 (red). In the beam switch chart, as3 is higher than as1 for DRX 40, 80, and 160, but they are nearly equal for DRX 0. In the beam ping-pong chart, the values for as1 and as3 are very similar across all DRX cycles. + +Figure 6.3.4.1.2.8-1 Beam switch and beam ping-pong rates + +Figure 6.3.4.1.2.8-2 shows time-of-outage statistics with DPS. The results show generally very low outage rate with enhanced requirements up to DRX cycle 80 ms. + +![Two bar charts comparing MPUE assumptions as1 and as3 for DRX cycles 0, 40, 80, and 160 ms. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. In both cases, MPUEAssumption:as3 generally shows higher values than MPUEAssumption:as1, especially at 160 ms DRX.](31c1877b2b8a3479b473e01d9856b689_img.jpg) + +**Time-of-outage percentage per call (Scenario:A-bidir)** + +| DRX [ms] | MPUEAssumption:as1 [%] | MPUEAssumption:as3 [%] | +|----------|------------------------|------------------------| +| 0 | ~0.4 | ~0.4 | +| 40 | ~0.1 | ~0.3 | +| 80 | ~0.1 | ~0.6 | +| 160 | ~0.2 | ~3.4 | + +**Average time-of-outage duration due to low SINR (Scenario:A-bidir)** + +| DRX [ms] | MPUEAssumption:as1 [ms] | MPUEAssumption:as3 [ms] | +|----------|-------------------------|-------------------------| +| 0 | ~5 | ~5 | +| 40 | ~0 | ~5 | +| 80 | ~0 | ~10 | +| 160 | ~0 | ~35 | + +Two bar charts comparing MPUE assumptions as1 and as3 for DRX cycles 0, 40, 80, and 160 ms. The left chart shows 'Time-of-outage percentage per call [%]' and the right chart shows 'Average time-of-outage duration due to low SINR [ms]'. In both cases, MPUEAssumption:as3 generally shows higher values than MPUEAssumption:as1, especially at 160 ms DRX. + +**Figure 6.3.4.1.2.8-2 Time-of-outage per call and time-of-outage duration due to low SINR** + +Figure 6.3.4.1.2.8-3 shows beam failure indication rate with enhanced requirements. The rate is very low or zero up to DRX cycle 80 ms with both multi-panel assumptions- + +![Bar chart showing 'Beam failure indication rate (Scenario:A-bidir)' for DRX cycles 0, 40, 80, and 160 ms. The y-axis is 'BF/Beam switches * 100 [%]'. MPUEAssumption:as3 shows a significant increase at 160 ms DRX compared to MPUEAssumption:as1.](f618f0a44c7807c81c70cf7ec2e5e717_img.jpg) + +**Beam failure indication rate (Scenario:A-bidir)** + +| DRX [ms] | MPUEAssumption:as1 [%] | MPUEAssumption:as3 [%] | +|----------|------------------------|------------------------| +| 0 | ~0 | ~0 | +| 40 | ~0 | ~0 | +| 80 | ~0 | ~0.5 | +| 160 | ~0 | ~6.8 | + +Bar chart showing 'Beam failure indication rate (Scenario:A-bidir)' for DRX cycles 0, 40, 80, and 160 ms. The y-axis is 'BF/Beam switches \* 100 [%]'. MPUEAssumption:as3 shows a significant increase at 160 ms DRX compared to MPUEAssumption:as1. + +**Figure 6.3.4.1.2.8-3 Beam failure indication rate** + +Figure 6.3.4.1.2.8-4 shows SINR distributions for all simulated DRX cycles and multi-panel assumptions with enhanced requirements. It is observed that SINR levels are generally good up to DRX cycle 80 ms and the SINRs with the longest DRX cycle 160 ms are much less degraded than in the scenario with legacy requirements. The SINR difference between multi-panel assumptions is not so clear as in non-DPS case in 6.3.4.1.2.7. Assumption 3 gives gain in median and peak percentiles of the CDF particularly without DRX, but assumption 1 can be better in low percentiles. + +![Figure 6.3.4.1.2.8-4: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160) and MPUE assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The MPUE assumption 'as3' generally results in higher SINR values than 'as1' for the same DRX cycle.](8e6c3e68ec4b938b0f85a21c61d226df_img.jpg) + +Figure 6.3.4.1.2.8-4: SINR distributions. A line graph showing the Cumulative Distribution Function (CDF) of SINR [dB] for various DRX cycles (0, 40, 80, 160) and MPUE assumptions (as1, as3). The x-axis ranges from -10 to 60 dB, and the y-axis ranges from 0.0 to 1.0. The curves show that as the DRX cycle increases, the SINR distribution shifts to the right, indicating better performance. The MPUE assumption 'as3' generally results in higher SINR values than 'as1' for the same DRX cycle. + +Figure 6.3.4.1.2.8-4 SINR distributions + +###### 6.3.4.1.2.9 + +###### Uni-directional Tunnel scenario without DPS + +This section shows system level simulation mobility performance results for uni-directional tunnel scenario without DPS. Figure 6.3.4.1.2.9-1 shows successful handover rate per CPE per second and ping-pong rate as percentage of ping-pong handovers per all handovers. Similar to open space scenarios, it is observed in general that handover and ping-pong rates are the highest without DRX and gradually decrease when DRX cycle is increased. Compared to the Scenario A, the successful handover rate is significantly lower for all DRX cycles when the train travels to opposite direction than the RRH beams are pointing to. This suggests that there may not be enough time to perform the handover in the tunnel scenario when the train is moving towards the serving beam. + +![Figure 6.3.4.1.2.9-1: Handover and ping-pong handover rates. Two bar charts are shown. The left chart, 'Handover rate per CPE per second (Tunnel-unidir)', shows HO/CPE/s for DRX cycles 0, 40, 80, and 160. The right chart, 'Ping-pong handover rate (Tunnel-unidir)', shows PP/HO*100[%] for the same DRX cycles. Both charts compare 'Dir:Opposite' (red bars) and 'Dir:Same' (blue bars). In both cases, the rates are highest at DRX=0 and decrease as DRX increases. The 'Dir:Same' direction consistently shows higher handover and ping-pong rates than the 'Dir:Opposite' direction.](7cc979afbbf5fb1dedf0ddcbcf0044b7_img.jpg) + +Figure 6.3.4.1.2.9-1: Handover and ping-pong handover rates. Two bar charts are shown. The left chart, 'Handover rate per CPE per second (Tunnel-unidir)', shows HO/CPE/s for DRX cycles 0, 40, 80, and 160. The right chart, 'Ping-pong handover rate (Tunnel-unidir)', shows PP/HO\*100[%] for the same DRX cycles. Both charts compare 'Dir:Opposite' (red bars) and 'Dir:Same' (blue bars). In both cases, the rates are highest at DRX=0 and decrease as DRX increases. The 'Dir:Same' direction consistently shows higher handover and ping-pong rates than the 'Dir:Opposite' direction. + +Figure 6.3.4.1.2.9-1 Handover and ping-pong handover rates + +Figure 6.3.4.1.2.9-2 shows average time-of-stay in cell (RRH). It is observed that without DRX the time-of-stay in RRH is significantly lower than the time that the train with 350 km/h speed takes to travel the distance of one $D_s$ of 700 meters (about 7.2 seconds). Compared to Scenario A when the train is traveling to the same direction as the RRH beam are pointing to, time-of-stay with low DRX (up to 40ms) is lower. This result is due to handover and ping-pongs rate + +observed in Figure 6.3.4.1.2.1-1 which is seen high with low DRX cycles in the tunnel scenario. With DRX cycles 80-160 ms the time-of-stay increases to about 7 seconds. + +![Bar chart titled 'Time-of-stay in cell (Tunnel-unidir)' showing ToS in cell [ms] for DRX cycles 0, 40, 80, and 160. The chart compares 'Dir:Opposite' (red) and 'Dir:Same' (blue) directions. ToS increases with DRX cycles, reaching approximately 7000 ms for both directions at 160 ms DRX.](99b769aeac0b78472f4cb81be7836f3b_img.jpg) + +| DRX | Dir:Opposite, ToS in cell [ms] | Dir:Same, ToS in cell [ms] | +|-----|--------------------------------|----------------------------| +| 0 | 6000 | 4000 | +| 40 | 6500 | 5800 | +| 80 | 7000 | 6500 | +| 160 | 7200 | 7000 | + +Bar chart titled 'Time-of-stay in cell (Tunnel-unidir)' showing ToS in cell [ms] for DRX cycles 0, 40, 80, and 160. The chart compares 'Dir:Opposite' (red) and 'Dir:Same' (blue) directions. ToS increases with DRX cycles, reaching approximately 7000 ms for both directions at 160 ms DRX. + +Figure 6.3.4.1.2.9-2 Time-of-stay in cell + +Figure 6.3.4.1.2.9-3 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. It is observed from the results that significant outage is observed only in case the train travels to opposite direction than RRH beams are pointing to, even without DRX enabled. + +![Two bar charts. The left chart, 'Time-of-outage percentage per call (Tunnel-unidir)', shows percentages for DRX cycles 0, 40, 80, and 160. The right chart, 'Average time-of-outage duration due to low SINR (Tunnel-unidir)', shows durations in ms for the same DRX cycles. Both charts compare 'Dir:Opposite' (red) and 'Dir:Same' (blue) directions. Outage percentage and duration increase with DRX cycles for the opposite direction, while remaining near zero for the same direction.](3d6f4088e319484d4e81fb68cd8520a3_img.jpg) + +| DRX | Dir:Opposite, Time-of-Outage per call [%] | Dir:Same, Time-of-Outage per call [%] | Dir:Opposite, Time-of-outage duration [ms] | Dir:Same, Time-of-outage duration [ms] | +|-----|-------------------------------------------|---------------------------------------|--------------------------------------------|----------------------------------------| +| 0 | 17 | 1 | 35 | 0 | +| 40 | 20 | 1 | 100 | 0 | +| 80 | 28 | 1 | 115 | 0 | +| 160 | 40 | 1 | 155 | 0 | + +Two bar charts. The left chart, 'Time-of-outage percentage per call (Tunnel-unidir)', shows percentages for DRX cycles 0, 40, 80, and 160. The right chart, 'Average time-of-outage duration due to low SINR (Tunnel-unidir)', shows durations in ms for the same DRX cycles. Both charts compare 'Dir:Opposite' (red) and 'Dir:Same' (blue) directions. Outage percentage and duration increase with DRX cycles for the opposite direction, while remaining near zero for the same direction. + +Figure 6.3.4.1.2.9-3 Time-of-outage per call and time-of-outage duration due to low SINR + +Figure 6.3.4.1.2.9-4 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). It is seen that the failure rates are extremely high when the train travels to opposite direction than RRH beams are pointing to, i.e., the mobility failure rate is over 50% in this scenario even without DRX. No failures are observed when train is traveling to the same direction as the RRH beams orientation. + +![Bar chart titled 'Inter-cell mobility failure rate (Tunnel-unidir)' showing failure rates for DRX values 0, 40, 80, and 160. The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF)*100 [%] and ranges from 0 to 80. The x-axis is labeled DRX. Two series are shown: Dir:Opposite (red) and Dir:Same (blue).](be2d9105109f6a87907ab68cb88548d9_img.jpg) + +| DRX | Dir:Opposite (%) | Dir:Same (%) | +|-----|------------------|--------------| +| 0 | ~53 | 0 | +| 40 | ~63 | 0 | +| 80 | ~69 | 0 | +| 160 | ~69 | 0 | + +Bar chart titled 'Inter-cell mobility failure rate (Tunnel-unidir)' showing failure rates for DRX values 0, 40, 80, and 160. The y-axis is labeled (RLF+HOF)/(HO+RLF+HOF)\*100 [%] and ranges from 0 to 80. The x-axis is labeled DRX. Two series are shown: Dir:Opposite (red) and Dir:Same (blue). + +Figure 6.3.4.1.2.9-4 Mobility failure rate + +Figure 6.3.4.1.2.9-5 shows distribution of raw SINR values taken from the CQI measurements. It is observed that SINR level is high and clearly sufficient to support high mobility performance for the case where the train is traveling into same direction as RRH beams are pointing to. However, when the train travels opposite to the RRH beam pointing direction, there are areas that SINR may drop low and insufficient to support the mobility especially when the DRX increases, whereas at some areas the SINR becomes extremely good. + +![CDF plot titled 'SINR distribution (Tunnel-unidir)' showing CDF vs SINR [dB] for various DRX and direction settings. The x-axis ranges from 0 to 80 dB, and the y-axis ranges from 0.0 to 1.0. Solid lines represent Dir:Same and dashed lines represent Dir:Opposite for DRX values 0, 40, 80, and 160.](e0740204d7aa33697c8f2d59c4cca51b_img.jpg) + +CDF plot titled 'SINR distribution (Tunnel-unidir)' showing CDF vs SINR [dB] for various DRX and direction settings. The x-axis ranges from 0 to 80 dB, and the y-axis ranges from 0.0 to 1.0. Solid lines represent Dir:Same and dashed lines represent Dir:Opposite for DRX values 0, 40, 80, and 160. + +Figure 6.3.4.1.2.9-5 SINR distributions + +###### 6.3.4.1.2.10 Uni-directional Tunnel scenario with DPS + +This section shows system level simulation mobility performance results for uni-directional tunnel scenario with DPS. Figure 6.3.4.1.2.10-1 shows successful beam switch rate per CPE per second and ping-pong rate as percentage of ping-pong beam switches per all beam switches. Similar to Scenario-A, since there is just one Tx beam per RRH this means ping-pongs between RRHs. In DPS case the same trend is observed in beam switches as with handovers in non-DPS case, i.e., without DRX the rates are the highest and gradually rates decrease when longer DRX cycles are used. The differences between the rates in train travel direction are rather low. + +![Figure 6.3.4.1.2.10-1: Beam switch and beam ping-pong rates. Two bar charts comparing 'Dir:Opposite' (red) and 'Dir:Same' (blue) for DRX cycles 0, 40, 80, and 160. The left chart shows 'Beam switch rate per CPE per second (Tunnel-unidir)' and the right chart shows 'Beam ping-pong rate (Tunnel-bidir)'.](578d2763eaf3edf3f1bd6657455ad54a_img.jpg) + +**Figure 6.3.4.1.2.10-1 Data: Beam switch and beam ping-pong rates** + +| DRX | Beam switch rate (Dir:Opposite) | Beam switch rate (Dir:Same) | Beam ping-pong rate (Dir:Opposite) | Beam ping-pong rate (Dir:Same) | +|-----|---------------------------------|-----------------------------|------------------------------------|--------------------------------| +| 0 | ~0.28 | ~0.28 | ~26 | ~26 | +| 40 | ~0.17 | ~0.18 | ~6 | ~9 | +| 80 | ~0.15 | ~0.15 | ~2 | ~3 | +| 160 | ~0.14 | ~0.14 | ~0.5 | ~0.5 | + +Figure 6.3.4.1.2.10-1: Beam switch and beam ping-pong rates. Two bar charts comparing 'Dir:Opposite' (red) and 'Dir:Same' (blue) for DRX cycles 0, 40, 80, and 160. The left chart shows 'Beam switch rate per CPE per second (Tunnel-unidir)' and the right chart shows 'Beam ping-pong rate (Tunnel-bidir)'. + +**Figure 6.3.4.1.2.10-1 Beam switch and beam ping-pong rates** + +Figure 6.3.4.1.2.10-2 shows time-of-outage percentage per call (existence of CPE in the simulation) and average time-of-outage duration due to low SINR (below -8 dB) conditions. Similar trend is also observed here as without DPS that the time-of-outage rates are very low when train is traveling to the same direction as RRH beams are pointing to, whereas the outage is seen significant even without DRX enabled when train is traveling opposite to the pointing direction of the RRH beams. + +![Figure 6.3.4.1.2.10-2: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts comparing 'Dir:Opposite' (red) and 'Dir:Same' (blue) for DRX cycles 0, 40, 80, and 160. The left chart shows 'Time-of-outage percentage per call (Tunnel-unidir)' and the right chart shows 'Average time-of-outage duration due to low SINR (Tunnel-unidir)'.](21282638f01b60bb72acf07272e24942_img.jpg) + +**Figure 6.3.4.1.2.10-2 Data: Time-of-outage per call and time-of-outage duration due to low SINR** + +| DRX | Time-of-outage % (Dir:Opposite) | Time-of-outage % (Dir:Same) | Avg. Time-of-outage (ms) (Dir:Opposite) | Avg. Time-of-outage (ms) (Dir:Same) | +|-----|---------------------------------|-----------------------------|-----------------------------------------|-------------------------------------| +| 0 | ~1.5 | ~0.1 | ~32 | ~5 | +| 40 | ~4.5 | ~0.1 | ~75 | ~0.1 | +| 80 | ~7.5 | ~0.1 | ~90 | ~0.1 | +| 160 | ~16.5 | ~0.5 | ~115 | ~0.1 | + +Figure 6.3.4.1.2.10-2: Time-of-outage per call and time-of-outage duration due to low SINR. Two bar charts comparing 'Dir:Opposite' (red) and 'Dir:Same' (blue) for DRX cycles 0, 40, 80, and 160. The left chart shows 'Time-of-outage percentage per call (Tunnel-unidir)' and the right chart shows 'Average time-of-outage duration due to low SINR (Tunnel-unidir)'. + +**Figure 6.3.4.1.2.10-2 Time-of-outage per call and time-of-outage duration due to low SINR** + +Figure 6.3.4.1.2.10-3 shows beam failure indication rate (BFI) as percentage of BFIs per beam switches. Similar trend is observed without DPS that no failures happen among the studied DRX cycles when train is traveling to same direction as RRH beams are pointing to. On the other hand, significantly high failures are observed with train traveling to opposite direction. + +![Bar chart titled 'Beam failure indication rate (Tunnel-unidir)' showing the BF/Beam switches*100[%] for different DRX values (0, 40, 80, 160). The chart compares two directions: Dir:Opposite (red bars) and Dir:Same (blue bars). The y-axis ranges from 0 to 60. The x-axis is labeled DRX. The legend indicates Dir:Opposite is red and Dir:Same is blue.](d989d8766a23d5e409031f1ceae6572b_img.jpg) + +| DRX | Dir:Opposite (%) | Dir:Same (%) | +|-----|------------------|--------------| +| 0 | ~25 | 0 | +| 40 | ~35 | 0 | +| 80 | ~35 | 0 | +| 160 | ~50 | 0 | + +Bar chart titled 'Beam failure indication rate (Tunnel-unidir)' showing the BF/Beam switches\*100[%] for different DRX values (0, 40, 80, 160). The chart compares two directions: Dir:Opposite (red bars) and Dir:Same (blue bars). The y-axis ranges from 0 to 60. The x-axis is labeled DRX. The legend indicates Dir:Opposite is red and Dir:Same is blue. + +Figure 6.3.4.1.2.10-3 Beam failure indication rate + +Figure 6.3.4.1.2.10-4 shows distribution of raw SINR values taken from the CQI measurements and it is observed that SINR level is high and clearly sufficient to support high mobility performance in cases when the train is traveling to same direction, but not in opposite traveling direction case. In general, compared to non-DPS case, the probability of low SINR samples below 0 dB are lower when DPS is used compared to non-DPS case. While comparing to open space scenarios, higher SINR values can be achieved in the tunnel case. + +![CDF plot titled 'SINR distribution (Tunnel-unidir)' showing the CDF of SINR [dB] for various DRX and direction settings. The x-axis ranges from 0 to 80 dB, and the y-axis ranges from 0.0 to 1.0. The legend includes: DRX:0, Dir:Same (solid blue); DRX:40, Dir:Same (solid red); DRX:80, Dir:Same (solid green); DRX:160, Dir:Same (solid cyan); DRX:0, Dir:Opposite (dashed blue); DRX:40, Dir:Opposite (dashed red); DRX:80, Dir:Opposite (dashed green); and DRX:160, Dir:Opposite (dashed cyan).](5011c5ead95d8bfb47fd0faa5158ff4f_img.jpg) + +CDF plot titled 'SINR distribution (Tunnel-unidir)' showing the CDF of SINR [dB] for various DRX and direction settings. The x-axis ranges from 0 to 80 dB, and the y-axis ranges from 0.0 to 1.0. The legend includes: DRX:0, Dir:Same (solid blue); DRX:40, Dir:Same (solid red); DRX:80, Dir:Same (solid green); DRX:160, Dir:Same (solid cyan); DRX:0, Dir:Opposite (dashed blue); DRX:40, Dir:Opposite (dashed red); DRX:80, Dir:Opposite (dashed green); and DRX:160, Dir:Opposite (dashed cyan). + +Figure 6.3.4.1.2.10-4 SINR distributions. + +###### 6.3.4.1.2.11 Transition at the tunnel entrance/exit without DPS + +The coverage of the open-space RRHs at the tunnel entrance/exit is likely limited since the RRH beams can be blocked by the tunnel's outer wall. This is expected to have impacts to mobility performance in uni-directional deployment when the train is approaching/leaving the tunnel from/to the open space. This section demonstrates mobility performance such transition scenario. The aim is to provides insights on the impact of potential coverage issue at the tunnel entrance/exit to the mobility performance. + +![Figure 6.3.4.1.2.11-1: Coverage issue at the tunnel entrance in uni-directional deployment. The diagram shows two scenarios. In the top scenario, RRH1 is outside the tunnel, and its beam (blue) covers the entrance. RRH2 is inside the tunnel, and its beam (blue) covers the CPE/UE. In the bottom scenario, RRH3 is outside the tunnel, and its beam (red) covers the entrance. RRH2 is inside the tunnel, and its beam (red) covers the CPE/UE. The tunnel wall is shown as a horizontal line, and the CPE/UE is shown as a small rectangle inside the tunnel.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +Figure 6.3.4.1.2.11-1: Coverage issue at the tunnel entrance in uni-directional deployment. The diagram shows two scenarios. In the top scenario, RRH1 is outside the tunnel, and its beam (blue) covers the entrance. RRH2 is inside the tunnel, and its beam (blue) covers the CPE/UE. In the bottom scenario, RRH3 is outside the tunnel, and its beam (red) covers the entrance. RRH2 is inside the tunnel, and its beam (red) covers the CPE/UE. The tunnel wall is shown as a horizontal line, and the CPE/UE is shown as a small rectangle inside the tunnel. + +Figure 6.3.4.1.2.11-1 Coverage issue at the tunnel entrance in uni-directional deployment + +The assumptions and setting for the simulation are as follows. Uni-directional deployment is considered for the RRH deployed outside the tunnel (RRH1 in Figure 6.3.4.1.2.11-2). Assume that the beam's main lobe from RRH1 is pointing to the entrance/exit of the tunnel. Depending on the tunnel's dimension, the LoS paths can be seen up to $d$ [m] inside the tunnel, meaning that NLoS-only condition will exist after distance $d$ . To enable the NLoS condition, the probability of LoS [TR38.901] in the channel model is set as + +$$Pr_{LoS} = \begin{cases} 1, & d_{2D} \leq 700 + d \\ 0, & d_{2D} > 700 + d \end{cases}$$ + +Distance $d$ is given as $d=300\text{m}$ for Scenario A and $d=22.6\text{m}$ for Scenario B following the below assumption and estimation. Assume that a tunnel with dimensions: + +- width ( $w$ ) = 6m, and height ( $D_{\text{Tunnel,height}}$ ) = 5.5m +- Open space RRH: $D_{\text{RRH,height}} = 15\text{m}$ ; CPE : $D_{\text{UE,height}} = 5\text{m}$ + +It can be estimated that the coverage of RRH1's beam behind the tunnel entrance/exit in vertical and horizontal direction are 300 m and 22.1 m for Scenario A, and 14.3m and 22.6m for Scenario B, respectively (Figure 6.3.4.1.2.11-1 for the calculation). + +![Figure 6.3.4.1.2.11-2: Calculation of coverage distance d. The top diagram shows the horizontal coverage distance d, where the beam from RRH1 (height D_min) covers the tunnel entrance (width w/2) and extends to distance d inside the tunnel. The bottom diagram shows the vertical coverage distance d, where the beam from RRH1 (height H = D_RRH,height - D_UE,height) covers the tunnel entrance (height h = D_Tunnel,height - D_UE,height) and extends to distance d inside the tunnel. The horizontal distance D_s is also shown.](53f4e16be332aa0952e18cbb5259c31c_img.jpg) + +Figure 6.3.4.1.2.11-2: Calculation of coverage distance d. The top diagram shows the horizontal coverage distance d, where the beam from RRH1 (height D\_min) covers the tunnel entrance (width w/2) and extends to distance d inside the tunnel. The bottom diagram shows the vertical coverage distance d, where the beam from RRH1 (height H = D\_RRH,height - D\_UE,height) covers the tunnel entrance (height h = D\_Tunnel,height - D\_UE,height) and extends to distance d inside the tunnel. The horizontal distance D\_s is also shown. + +$$\frac{w/2}{D_{\min}} = \frac{d}{d + D_s} \Rightarrow d = \frac{w/2 \times D_s}{D_{\min} - w}$$ + +$$\text{Scenario A: } d = \frac{w/2 \times D_s}{D_{\min} - w} = \frac{3 \times 700}{10 - 3} = 300$$ + +$$\text{Scenario B: } d = \frac{w/2 \times D_s}{D_{\min} - w} = \frac{3 \times 700}{15 - 3} = 14.3$$ + +$$\frac{d}{h} = \frac{d + D}{H}$$ + +$$\Rightarrow d = \frac{h \times D}{H - h} = \frac{(D_{\text{Tunnel,Height}} - D_{\text{UE,height}}) \times \sqrt{D_s^2 + D_{\min}^2}}{D_{\text{RRH,Height}} - D_{\text{Tunnel,Height}}}$$ + +$$\text{Scenario A: } d = \frac{0.3 \times \sqrt{700^2 + 10^2}}{15 - 5.5} = 22.1$$ + +$$\text{Scenario B: } d = \frac{0.3 \times \sqrt{700^2 + 150^2}}{15 - 5.5} = 22.6$$ + +**Figure 6.3.4.1.2.11-2 Calculation of LoS coverage of RRH1's beam inside the tunnel.** + +Then, $d=300\text{m}$ for Scenario A and $d=22.6\text{m}$ for Scenario B which are probably the best possible case for the LoS channel condition at the tunnel entrance/exit. + +Only non-DPS scheme (HO-based) is considered as the assumption is that open-space RRHs belong to different cell than those in the tunnel. However, the results for DPS scheme are expected similar. Other RRM parameters for the simulation follow the enhanced settings in Table 6.3.4.1.2-1. + +The mobility robustness performances, which are measured by the time-of-outage and mobility failure rate, are presented. + +###### 6.3.4.1.2.11.1 Transition from open-space Scenario-A to the Tunnel + +This section shows the mobility performance when the train is **moving into the tunnel** from Scenario A (i.e., corresponding to when the train is traveling to the **same** direction as RRH beam is pointing to, see Figure 6.3.4.1.2.11-1-(a)), and **leaving the tunnel** to the open space (i.e., corresponding to when the train is traveling to the **opposite** direction than RRH beams are pointing to, see Figure 6.3.4.1.2.11-1-(b)). + +Figure 6.3.4.1.2.11.1-1 shows time-of-outage percentage per call (existence of CPE in the simulation). Compared to Scenario A, time-of-outage in this transition case is seen to clearly increase for both traveling directions of the train. The increase is observed more significant when the train is traveling to the opposite direction of the RRH beams orientation and with longer DRX cycles due to the limited LoS coverage. + +![Bar chart titled 'Time-of-Outage percentage per call (Scenario A to Tunnel-unidir)'. The Y-axis is 'Time-of-Outage per call [%]' from 0 to 60. The X-axis is 'DRX' with values 0, 40, 80, 160. Two series are shown: 'Dir:Opposite' (red) and 'Dir:Same' (blue).](609dff0a56be2ded8c960a3672afa937_img.jpg) + +| DRX | Dir:Opposite (%) | Dir:Same (%) | +|-----|------------------|--------------| +| 0 | ~5 | ~2 | +| 40 | ~12 | ~2 | +| 80 | ~36 | ~2 | +| 160 | ~51 | ~2 | + +Bar chart titled 'Time-of-Outage percentage per call (Scenario A to Tunnel-unidir)'. The Y-axis is 'Time-of-Outage per call [%]' from 0 to 60. The X-axis is 'DRX' with values 0, 40, 80, 160. Two series are shown: 'Dir:Opposite' (red) and 'Dir:Same' (blue). + +**Figure 6.3.4.1.2.11.1-1 Time-of-outage percentage when UE transits from Scenario A and tunnel** + +Figure 6.3.4.1.2.11.1-2 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). It is observed that the limited coverage issue does not have any impact when the train is moving same with the beam pointing direction. However, failure rate is significantly increased when the train is moving opposite to beam direction (i.e., leaving the tunnel) and becomes unacceptable when high DRX cycles are considered. + +![Figure 6.3.4.1.2.11.1-2: Bar chart showing Time-of-outage percentage per call (Scenario A to Tunnel-unidir) for DRX values 0, 40, 80, and 160. The Y-axis is (RLF+HOF)/(HO+RLF+HOF)*100 [%]. Two series are shown: Dir:Opposite (red) and Dir:Same (blue).](7a0281fac8690d8894ef1cb92d1a7704_img.jpg) + +| DRX | Dir:Opposite (%) | Dir:Same (%) | +|-----|------------------|--------------| +| 0 | ~5 | 0 | +| 40 | ~25 | 0 | +| 80 | ~80 | 0 | +| 160 | ~85 | 0 | + +Figure 6.3.4.1.2.11.1-2: Bar chart showing Time-of-outage percentage per call (Scenario A to Tunnel-unidir) for DRX values 0, 40, 80, and 160. The Y-axis is (RLF+HOF)/(HO+RLF+HOF)\*100 [%]. Two series are shown: Dir:Opposite (red) and Dir:Same (blue). + +Figure 6.3.4.1.2.11.1-2 Inter-cell mobility failure rate when UE transits between Scenario A and tunnel + +###### 6.3.4.1.2.12.1 Transition from open-space Scenario-B to the Tunnel + +This section shows the mobility performance when the train is entering/leaving the tunnel from/to Scenario B. Figure 6.3.4.1.2.11.2-1 shows time-of-outage percentage per call (existence of CPE in the simulation). Compared to Scenario B, time-of-outage is increased for both traveling directions of the train when taking into account the NLoS condition at the transition area. Longer DRX cycles result in higher time-of-outage rate. The increase is seen more significant when the train is traveling to the opposite direction than RRH beams are pointing to due to the limited LoS coverage. + +![Figure 6.3.4.1.2.11.2-1: Bar chart showing Time-of-outage percentage per call (Scenario B to Tunnel-unidir) for DRX values 0, 40, 80, and 160. The Y-axis is Time-of-Outage per call [%]. Four series are shown: Dir:Opposite, RRHbeams:1 (green), Dir:Opposite, RRHbeams:2 (cyan), Dir:Same, RRHbeams:1 (blue), and Dir:Same, RRHbeams:2 (red).](b48758ac44730c1eba0b83ec3429e063_img.jpg) + +| DRX | Dir:Opposite, RRHbeams:1 (%) | Dir:Opposite, RRHbeams:2 (%) | Dir:Same, RRHbeams:1 (%) | Dir:Same, RRHbeams:2 (%) | +|-----|------------------------------|------------------------------|--------------------------|--------------------------| +| 0 | ~2 | ~2 | ~2 | ~2 | +| 40 | ~23 | ~13 | ~2 | ~1 | +| 80 | ~10 | ~7 | ~3 | ~3 | +| 160 | ~30 | ~30 | ~14 | ~14 | + +Figure 6.3.4.1.2.11.2-1: Bar chart showing Time-of-outage percentage per call (Scenario B to Tunnel-unidir) for DRX values 0, 40, 80, and 160. The Y-axis is Time-of-Outage per call [%]. Four series are shown: Dir:Opposite, RRHbeams:1 (green), Dir:Opposite, RRHbeams:2 (cyan), Dir:Same, RRHbeams:1 (blue), and Dir:Same, RRHbeams:2 (red). + +Figure 6.3.4.1.2.11.2-1 Time-of-outage percentage when UE transits between Scenario B and tunnel + +Figure 6.3.4.1.2.11.2-2 shows inter-cell mobility failure rate (RLF + HOF percentage of all handover and failure events). When the train is moving same with the beam pointing direction, it is observed that the limited coverage issue starts making the impact to the mobility at DRX 80ms. When the train is moving opposite with the beam pointing direction, the failure rate is significantly increased especially with DRX enabled. + +![Bar chart showing Inter-cell mobility failure rate (Scenario B to Tunnel-unidir) for different DRX cycles (0, 40, 80, 160 ms) and beam configurations. The Y-axis represents the failure rate as (RLF+HOF)/(HO+RLF+HOF)*100 [%].](4750bc46c043ee2e9d4524c36d9a54a1_img.jpg) + +| DRX (ms) | Dir:Opposite, RRHbeams:1 (%) | Dir:Opposite, RRHbeams:2 (%) | Dir:Same, RRHbeams:1 (%) | Dir:Same, RRHbeams:2 (%) | +|----------|------------------------------|------------------------------|--------------------------|--------------------------| +| 0 | 0 | 0 | 0 | 0 | +| 40 | ~10 | ~5 | 0 | 0 | +| 80 | ~22 | ~15 | ~2 | ~1 | +| 160 | ~60 | ~68 | ~5 | ~3 | + +Bar chart showing Inter-cell mobility failure rate (Scenario B to Tunnel-unidir) for different DRX cycles (0, 40, 80, 160 ms) and beam configurations. The Y-axis represents the failure rate as (RLF+HOF)/(HO+RLF+HOF)\*100 [%]. + +Figure 6.3.4.1.2.11.2-2 Inter-cell mobility failure rate when UE transits between Scenario B and tunnel + +##### 6.3.4.1.3 Conclusions on mobility performance + +###### Mobility performance in open-space scenarios: + +In the previous sections (6.3.4.1.1.1, 6.3.4.1.1.2, 6.3.4.1.2.1, 6.3.4.1.2.2), it was demonstrated that HST FR2 Scenario-A deployment (Figure 6.3.4.1.3-1) where the train is travelling in the direction opposite to serving beam orientation may experience mobility challenges when DRX cycle of 40 ms is used with legacy requirements. This happens due to the very fast degradation of serving RRH signal (Figure 6.3.4.1.3-2). However, there is a significant improvement in Scenario-A from enhanced requirements compared to legacy requirements. With enhanced requirements, mobility robustness is sufficient when DRX cycle of 40 ms is used, but problems can be observed when DRX cycle is increased to 80 ms when the train is travelling in the direction opposite to serving beam orientation. + +![Diagram of HST FR2 opposite uni-directional Scenario-A showing a train (CPE/UE) moving from left to right, passing RRH1 (source) and approaching RRH2 (target).](ff3417b75213b8688e6504a21220b430_img.jpg) + +Diagram of HST FR2 opposite uni-directional Scenario-A showing a train (CPE/UE) moving from left to right, passing RRH1 (source) and approaching RRH2 (target). + +Figure 6.3.4.1.3-1: A scheme of HST FR2 opposite uni-directional Scenario-A. + +![Propagation map of the serving RRH, antenna model without back lobe, showing signal strength distribution across a grid. The color scale ranges from -70 dBm (red) to -150 dBm (blue).](5b2bbe84f2201cedd3fb338e43a0655c_img.jpg) + +Propagation map of the serving RRH, antenna model without back lobe, showing signal strength distribution across a grid. The color scale ranges from -70 dBm (red) to -150 dBm (blue). + +Figure 6.3.4.1.3-2: Propagation map of the serving RRH, antenna model without back lobe. + +The RSRP traces of the serving (RRH1) and target (RRH2) RRHs are shown in Figure 6.3.4.1.3-3 with at different zoom levels. One can observe that the signal level from target RRH get high enough already much earlier than handover happens. However, the source RRH signal drops drastically near the RRH location. In this traced case, the handover happens early enough to transmit control messages even with realistic PDCCH model. It is also obvious that even slight delays in handover initiation will cause source RRH to drop to unreachable levels (e.g., RSRP below -120 dBm). + +![Figure 6.3.4.1.3-3: Two line graphs showing RSRP (dBm) vs X-coordinate on track (m) for RRH10-source (red) and RRH11-target (blue). The left graph zooms in on the handover area (7150-7450m), showing a sharp drop in source signal near 7350m. The right graph shows a wider view (7000-8200m). Vertical dashed lines indicate A3 trigger, HO completed, and RRH10 location.](215e8d5e5ba38df215b55049d255b2ed_img.jpg) + +Figure 6.3.4.1.3-3: Two line graphs showing RSRP (dBm) vs X-coordinate on track (m) for RRH10-source (red) and RRH11-target (blue). The left graph zooms in on the handover area (7150-7450m), showing a sharp drop in source signal near 7350m. The right graph shows a wider view (7000-8200m). Vertical dashed lines indicate A3 trigger, HO completed, and RRH10 location. + +**Figure 6.3.4.1.3-3: RSRP traces of serving and target RRHs at two different scales. Vertical lines show A3 trigger coordinate, HO complete, and source RRH location.** + +Based on the simulation results and analysis presented above we can conclude that DRX cycle of 80ms shall be used with precautions in uni-directional Scenario-A. + +In sections (6.3.4.1.1.3, 6.3.4.1.1.4, 6.3.4.1.1.5, 6.3.4.1.1.6, 6.3.4.1.2.3, 6.3.4.1.2.4, 6.3.4.1.2.5, 6.3.4.1.2.6) it was demonstrated that Scenario-B mobility performance with enhanced RRM requirements in both uni-directional and bi-directional scenarios is sufficient with DRX cycles up to 80 ms. Compared to legacy RRM requirements the mobility robustness measured by mobility failure and time-of-outage rates is significantly improved with enhanced RRM requirements also in Scenario-B. + +In sections 6.3.4.1.1.7, 6.3.4.1.1.8, 6.3.4.1.2.7, 6.3.4.1.2.8, it was shown that Scenario-A with bi-directional deployment needs similar precautions for DRX cycle of 80 ms as uni-directional scenario. Also, bi-directional scenario mobility robustness is significantly improved by the enhanced RRM requirements compared to legacy RRM requirements. Multi-panel UE measurement assumption was also shown to have significant impact to mobility robustness particularly in non-DPS scenario. Having UE capability to measure both directions at the same time can benefit mobility robustness. + +###### Mobility performance in tunnel scenarios: + +As demonstrated in previous sections (6.3.4.1.2.9, 6.3.4.1.2.10), the train travelling in the direction opposite to serving beam orientation likely experiences mobility challenges. The issue is more more severe than Scenario A as it may occur even when enhanced requirements are used and without DRX enabled. The root cause of such mobility issues is similar to what has been observed in Scenario A, i.e., the sudden drop of the source RSRP level near the source RRH which is due to the close distance between the RRH locations and the track ( $D_{min}$ ). As tunnel deployment has even shorter $D_{min}$ and lower $D_{RRH,height}$ , the source signal level drops more extreme causing high probability of mobility failure even when DRX is not enabled. + +![Figure 6.3.4.1.3-4: A schematic diagram of a tunnel scenario. It shows a cross-section of a tunnel with a CPE/UE on a track. RRH1 (source) is mounted on the left wall, and RRH2 (target) is mounted on the right wall. The tunnel wall is labeled. Arrows indicate the direction of the train and the coverage areas of the RRHs.](6d442ab678ed52045444b3ccd4c0ac9e_img.jpg) + +Figure 6.3.4.1.3-4: A schematic diagram of a tunnel scenario. It shows a cross-section of a tunnel with a CPE/UE on a track. RRH1 (source) is mounted on the left wall, and RRH2 (target) is mounted on the right wall. The tunnel wall is labeled. Arrows indicate the direction of the train and the coverage areas of the RRHs. + +**Figure 6.3.4.1.3-4: A scheme of HST FR2 opposite uni-directional Tunnel scenario.** + +Figure 6.3.4.1.3-5 shows propagation map around the source RRH location (the physical features of the tunnel like reflections are not considered). Only the source RRH is considered in the pathgain + antenna gain + beam gain of the map. It is observed that there is very strong signal level along the track until the RRH location, and with the backlobe suppressed signal level drops to unusable level right after the RRH if train is moving towards east and RRH antenna is pointed towards west. + +![Figure 6.3.4.1.3-5: Propagation map of the serving RRH, antenna model without back lobe. The map shows signal strength (Pathgain + antenna gain + beam gain) in dBm across a 2D coordinate system. The X-axis ranges from 7950 to 8150 m, and the Y-axis ranges from 240 to 360 m. A color scale on the right indicates signal levels from -160 dBm (dark blue) to -60 dBm (dark red). A dashed line represents the train track, passing through the center of the map at approximately Y=300 m. The signal is strongest (red/orange) along the track before the RRH location (around X=8050 m) and drops significantly (blue) after the RRH location.](f88c98ece93f791a5eb0a524ccc85b54_img.jpg) + +Figure 6.3.4.1.3-5: Propagation map of the serving RRH, antenna model without back lobe. The map shows signal strength (Pathgain + antenna gain + beam gain) in dBm across a 2D coordinate system. The X-axis ranges from 7950 to 8150 m, and the Y-axis ranges from 240 to 360 m. A color scale on the right indicates signal levels from -160 dBm (dark blue) to -60 dBm (dark red). A dashed line represents the train track, passing through the center of the map at approximately Y=300 m. The signal is strongest (red/orange) along the track before the RRH location (around X=8050 m) and drops significantly (blue) after the RRH location. + +**Figure 6.3.4.1.3-5: Propagation map of the serving RRH, antenna model without back lobe.** + +Figure 6.3.4.1.3-6 shows the RSRP traces of the source (RRH1) and target (RRH2) RRHs. It is observed that signal level from the serving beam increases when the train is approaching the source RRH, and suddenly drops drastically when the train is about 5m from the Source RRH location. One can also see that the first A3 event is triggered when the train is right under the source RRH where there is no longer coverage from serving beam. Later, several attempts for triggering A3 events are carried out in order to make HO, but there is no successful HO achieved. This can be understandable as the signal level source RRH has dropped to unreachable level causing the loss of HO command. After staying outage for a significantly long period, the cell selection procedure is initiated to make the UE connecting to the new cell. + +![Figure 6.3.4.1.3-6: RSRP traces of source and target. The graph plots RSRP [dBm] on the Y-axis (from -180 to -40) against X-coordinate on track [m] on the X-axis (from 7850 to 8250). The red line represents the RSRP of the source RRH, which starts around -60 dBm, increases to -40 dBm at X=8050 m, and then drops sharply to -180 dBm. The blue line represents the RSRP of the best-target RRH, which starts around -80 dBm, fluctuates, and then increases to around -60 dBm after X=8050 m. Vertical dashed lines indicate key events: A3 triggers (black), new cell selection (magenta), HO completed (cyan), and the source RRH location (green dashed line at X=8050 m).](89d2e4c002294cf6ffee801e84670cc5_img.jpg) + +Figure 6.3.4.1.3-6: RSRP traces of source and target. The graph plots RSRP [dBm] on the Y-axis (from -180 to -40) against X-coordinate on track [m] on the X-axis (from 7850 to 8250). The red line represents the RSRP of the source RRH, which starts around -60 dBm, increases to -40 dBm at X=8050 m, and then drops sharply to -180 dBm. The blue line represents the RSRP of the best-target RRH, which starts around -80 dBm, fluctuates, and then increases to around -60 dBm after X=8050 m. Vertical dashed lines indicate key events: A3 triggers (black), new cell selection (magenta), HO completed (cyan), and the source RRH location (green dashed line at X=8050 m). + +**Figure 6.3.4.1.3-6: RSRP traces of source and target. Vertical lines show A3 trigger coordinate, new cell selection, and source RRH location.** + +The system simulation results in Sections (6.3.4.1.2.9 and 6.3.4.1.2.10) pointed out the mobility issue for HST FR2 happened inside the tunnel. RAN4 studies concluded that multi-panel reception, in which the UE can receive the DL signals simultaneously from two opposite directions, is a candidate solution for the considered issue, i.e., if one link is failed, the UE still has connections to the network via the other link. + +In Section 6.3.4.1.2.11, the mobility robustness was studied for the mobility at the tunnel entrance/exit. In such areas, the coverage of the RRHs outside the tunnel may be limited inside the tunnel due to the blockage of the tunnel outer surfaces. It was demonstrated that time-of-outage and inter-cell mobility failure rate both increase suggesting the potential mobility problem that may occur at the tunnel entrance/exit. Nevertheless, such issue can be resolved by deployment-based solutions, i.e., placing the open-space RRHs which is nearest to the tunnel entrance/exit closer to the railway track, e.g., the RRH2's location shown in Figure 6.3.4.1.3-7. + +![Figure 6.3.4.1.3-7: Example of a special deployment for the open-space RRH next to the tunnel entrance. The diagram shows a horizontal railway track represented by a dashed line. Above the track, three Remote Radio Heads (RRHs) are shown: RRH1 is outside the tunnel on the left, RRH2 is positioned at the tunnel entrance, and RRH3 is inside the tunnel. A CPE/UE is located on the track, moving from left to right as indicated by a large black arrow. Each RRH has a blue shaded area representing its coverage. RRH1's coverage is outside the tunnel. RRH2's coverage is at the entrance, partially inside and partially outside. RRH3's coverage is inside the tunnel. The tunnel is represented by two solid horizontal lines above the track, with a gap at the entrance where RRH2 is located.](a320e67b369bfde4a5fa360b100da55c_img.jpg) + +Figure 6.3.4.1.3-7: Example of a special deployment for the open-space RRH next to the tunnel entrance. The diagram shows a horizontal railway track represented by a dashed line. Above the track, three Remote Radio Heads (RRHs) are shown: RRH1 is outside the tunnel on the left, RRH2 is positioned at the tunnel entrance, and RRH3 is inside the tunnel. A CPE/UE is located on the track, moving from left to right as indicated by a large black arrow. Each RRH has a blue shaded area representing its coverage. RRH1's coverage is outside the tunnel. RRH2's coverage is at the entrance, partially inside and partially outside. RRH3's coverage is inside the tunnel. The tunnel is represented by two solid horizontal lines above the track, with a gap at the entrance where RRH2 is located. + +**Figure 6.3.4.1.3-7: Example of a special deployment for the open-space RRH next to the tunnel entrance.** + +### 6.3.5 Receive time difference + +Not applicable to FR2 HST + +### 6.3.6 Maximum supported Doppler frequency + +Carrier frequency for Doppler frequency calculation + +- 30GHz. + +### 6.3.7 Maximum supported Speed + +Companies' observation on Maximum Speed feasibility: + +- It is feasible to support maximum speed with 350km/h for downlink with TRS (4 symbol interval) for frequency offset tracking under unidirectional RRH deployment with 120KHz SCS. +- It is feasible to support maximum speed with 350km/h for downlink with TRS (4 symbol interval) +SSB for frequency offset tracking under unidirectional and bi-directional RRH deployment with 120KHz SCS. +- It is feasible to support maximum speed with 350km/h for downlink with TRS (4 symbol interval) + PTRS (L=1) for frequency offset tracking under bi-directional RRH deployment with 120KHz SCS. +- It is feasible to support maximum speed with 350km/h for downlink with PTRS or DMRS(1+1+1) + PTRS (L=1,K=2) configuration used for frequency offset tracking under single tap propagation conditions with 120KHz SCS. + +Configure PTRS during the PDSCH demodulation test. + +RS as baseline for frequency offset tracking to support 350km/h + +- multiple options under discussion. + +DMRS configuration for PDSCH demodulation requirement + +- Option 1: 1 DMRS; and +- Option 2: 1+1+1 DMRS. + +### 6.3.8 Beam dwelling time + +#### 6.3.8.1 Simulation results + +The system simulation assumptions for beam dwelling time are shown in table 6.3.8.1-1. The simulation results of beam dwelling time are obtained from system-level simulations which were carried out to evaluate legacy RRM requirements under high-speed train scenarios. + +**Table 6.3.8.1-1: Simulation assumptions for beam dwelling time** + +| Parameter | Value | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of sites (separate gNBs) | 12 | +| Inter-site distance (ISD, Ds) | 700 m | +| RRH distance to track (Dmin) | 10 m (Scenario A), 150 m (Scenario B) | +| RRH height (D_RRH_Height) | 15 m | +| CPE height (D_CPE_Height) | 5 m | +| Carrier frequency | 28 GHz | +| Bandwidth | 50 MHz | +| Subcarrier spacing | 120 kHz | +| Propagation and channel model | TR 38.901 RMa with LOS only | +| RRH TX output power | 31 dBm | +| RRH antenna panel | [Mg, Ng, M, N, P] = [1, 1, 8, 8, 2]
Panel is pointing towards the track at the x-axis where the next site is situated (ISD away) | +| RRH antenna panel direction in relation to train in uni-directional deployments | Opposite direction (train moves east, RRHs pointing west)
Same direction (train moves east, RRHs pointing east) | +| SSB beams per RRH | Uni-directional:
1 beam:
Pointing into the boresight of the RRH antenna panel
2 beams:
One beam is pointing into the boresight and the other beam is pointing 20 degrees towards the track from boresight
4 beams:
One beam is pointing into the boresight and the other beams are pointing 20, 40, 60 degrees towards the track from boresight

Bi-directional:
1 beam:
Pointing into the boresight of the RRH antenna panel
2 beams:
One beam is pointing into the boresight and the other beam is pointing towards the track at Ds/2
4 beams:
One beam is pointing into the boresight and the other beams are pointing towards the track at Ds/2, Ds/4, Ds/8 | +| CPE (Train) speed | 350 km/h | +| CPE antenna panel | [Mg, Ng, M, N, P] = [1, 1 or 2, 4, 4, 2]
In uni-directional case where RRHs point east CPE has one antenna panel pointing west
In bi-directional case CPE has two antenna panels pointing to 180 degrees opposite directions (west-east)
MPUE assumption: only one panel can be used at a time for measurements | +| Number of beams per CPE panel | 1 beam (even though it is 1, scaling factor 8 is assumed for RRC measurements, L1 measurements and cell detection delays in simulations) | +| Traffic | DL Full Buffer | +| Inter-cell interference | Only one train with one CPE is simulated meaning there is no inter-cell interference | +| DRX | DRX disabled (DRX 0), 40, 80, 160, 256, 320 ms cycles | +| SMTC period | 20 ms | +| Handover assumptions | Event A3 with SS-RSRP
Offset: 3 dB
Time-to-trigger: 80 ms | +| RRc measurement period
L1 RSRP measurement period | Note: N=8 assumed in scaling
DRX 0: 480 ms
DRX 40: 1440 ms
DRX 80: 2880 ms
DRX 160: 5760 ms
DRX 256: 9216 ms
DRX 320: 11520 ms | + +| | | +|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell detection delay
( $T_{PSS/SSS\_sync\_intra}$ ) | Note: N = 8 is assumed in scaling
DRX 0: 600 ms
DRX 40: 1440 ms
DRX 80: 2880 ms
DRX 160: 5760 ms
DRX 256: 9216 ms
DRX 320: 11520 ms | +| RLM assumptions | Note: N=8 assumed in scaling
$T_{Evaluate\_out\_CSI-RS}$ : 600, 3600, 7200, 14400, 23040, 28800 ms (DRX 0, 40, 80, 160, 256, 320)
$T_{Evaluate\_in\_CSI-RS}$ : 300, 1800, 3600, 7200, 11520, 14400 ms (DRX 0, 40, 80, 160, 256, 320)
N310: 2 samples
N311: 2 samples
$Q_{out}$ threshold SINR: -8 dB
$Q_{in}$ threshold SINR: -6 dB | +| BFD assumptions | Note: N=8 assumed in scaling
$T_{Evaluate\_BFD\_CSI-RS}$ : 300, 1800, 3600, 7200, 11520, 14400 ms (DRX 0, 40, 80, 160, 256, 320) | +| Simulation length | 100 seconds (20 drops of 100 seconds simulated, and statistics samples are gathered from all drops) | + +The simulation results of beam dwelling time are shown in figures 6.3.8.1-1-3 for unidirectional scenarios with a different number beams transmitted by RRH. The simulation results of beam dwelling time are shown in figures 6.3.8.1-4-6 for bidirectional scenarios with different number of beams transmitted by RRH. + +It is worth noting that the simulation results are the average beam dwelling time. In the simulation, beam dwelling time is influenced by beam coverage and beam switching rate (including hysteresis). Beam coverage is discussed in detail in clause 6.3.8.2, where ideal beam dwelling time is investigated. + +In the case of multi-beam operation cases shown in figures 6.3.8.1-2, 6.3.8.1-3, 6.3.8.1-5 and 6.3.8.1-6, it can be observed that the dwelling time of Beam 0 is the shortest because the coverage of Beam 0 is the smallest. + +![Bar chart titled 'Beam dwelling times in uni-directional scenarios with 1 beam per RRH'. The Y-axis is 'Average dwelling time [ms]' ranging from 0 to 8000. The X-axis is 'Beam 0'. Four bars represent different scenarios: Scenario A (RRHDir: Same) at ~6000 ms, Scenario A (RRHDir: Opposite) at ~6000 ms, Scenario B (RRHDir: Same) at ~4500 ms, and Scenario B (RRHDir: Opposite) at ~4500 ms.](a7e667227af01b0bd7f81d42ebae5c07_img.jpg) + +| Scenario | RRHDir | Average dwelling time [ms] | +|------------|----------|----------------------------| +| Scenario A | Same | ~6000 | +| Scenario A | Opposite | ~6000 | +| Scenario B | Same | ~4500 | +| Scenario B | Opposite | ~4500 | + +Bar chart titled 'Beam dwelling times in uni-directional scenarios with 1 beam per RRH'. The Y-axis is 'Average dwelling time [ms]' ranging from 0 to 8000. The X-axis is 'Beam 0'. Four bars represent different scenarios: Scenario A (RRHDir: Same) at ~6000 ms, Scenario A (RRHDir: Opposite) at ~6000 ms, Scenario B (RRHDir: Same) at ~4500 ms, and Scenario B (RRHDir: Opposite) at ~4500 ms. + +Figure 6.3.8.1-1: Average beam dwelling time with 1 beam per RRH for unidirectional scenarios + +![Figure 6.3.8.1-2: Beam dwelling times in uni-directional scenarios with 2 beams per RRH. The chart shows average dwelling times for Beam 0 and Beam 1 in two scenarios: RRHDir:Same and RRHDir:Opposite. An inset diagram shows the train movement and beam coverage.](2303c01c42eb5b45539e6b0324701ee1_img.jpg) + +Figure 6.3.8.1-2 is a bar chart titled "Beam dwelling times in uni-directional scenarios with 2 beams per RRH". The y-axis represents "Average dwelling time [ms]" from 0 to 6000. The x-axis shows "Beam 0" and "Beam 1". For each beam, there are two bars: a blue bar for "Scenario:B-Beams2, RRHDir:Same" and an orange bar for "Scenario:B-Beams2, RRHDir:Opposite". An inset diagram shows a train moving from left to right, with Beam 0 and Beam 1 coverage areas. The legend indicates "Train movement (RRHDir:Same)" with a right arrow and "Train movement (RRHDir:Opposite)" with a left arrow. + +| Beam | Scenario:B-Beams2, RRHDir:Same [ms] | Scenario:B-Beams2, RRHDir:Opposite [ms] | +|--------|-------------------------------------|-----------------------------------------| +| Beam 0 | 2000 | 1900 | +| Beam 1 | 3500 | 3500 | + +Figure 6.3.8.1-2: Beam dwelling times in uni-directional scenarios with 2 beams per RRH. The chart shows average dwelling times for Beam 0 and Beam 1 in two scenarios: RRHDir:Same and RRHDir:Opposite. An inset diagram shows the train movement and beam coverage. + +Figure 6.3.8.1-2: Average beam dwelling time with 2 beams per RRH for unidirectional scenarios + +![Figure 6.3.8.1-3: Beam dwelling times in uni-directional scenarios with 4 beams per RRH. The chart shows average dwelling times for Beam 0, Beam 1, Beam 2, and Beam 3 in two scenarios: RRHDir:Same and RRHDir:Opposite. An inset diagram shows the train movement and beam coverage.](19a878abbd7068d98e7d54341c8d897c_img.jpg) + +Figure 6.3.8.1-3 is a bar chart titled "Beam dwelling times in uni-directional scenarios with 4 beams per RRH". The y-axis represents "Average dwelling time [ms]" from 0 to 4000. The x-axis shows "Beam 0", "Beam 1", "Beam 2", and "Beam 3". For each beam, there are two bars: a blue bar for "Scenario:B-Beams4, RRHDir:Same" and an orange bar for "Scenario:B-Beams4, RRHDir:Opposite". An inset diagram shows a train moving from left to right, with Beam 0, Beam 1, Beam 2, and Beam 3 coverage areas. The legend indicates "Train movement (RRHDir:Same)" with a right arrow and "Train movement (RRHDir:Opposite)" with a left arrow. + +| Beam | Scenario:B-Beams4, RRHDir:Same [ms] | Scenario:B-Beams4, RRHDir:Opposite [ms] | +|--------|-------------------------------------|-----------------------------------------| +| Beam 0 | 300 | 400 | +| Beam 1 | 800 | 800 | +| Beam 2 | 1900 | 1800 | +| Beam 3 | 2800 | 2800 | + +Figure 6.3.8.1-3: Beam dwelling times in uni-directional scenarios with 4 beams per RRH. The chart shows average dwelling times for Beam 0, Beam 1, Beam 2, and Beam 3 in two scenarios: RRHDir:Same and RRHDir:Opposite. An inset diagram shows the train movement and beam coverage. + +Figure 6.3.8.1-3: Average beam dwelling time with 4 beams per RRH for unidirectional scenarios + +![Figure 6.3.8.1-4: Beam dwelling times in bi-directional scenarios with 1 beam per RRH. The chart shows average dwelling times for Beam 0 in two scenarios: RRHDir:Same and RRHDir:Opposite.](761bcf76a08d183518129d697fbeba5b_img.jpg) + +Figure 6.3.8.1-4 is a bar chart titled "Beam dwelling times in bi-directional scenarios with 1 beam per RRH". The y-axis represents "Average dwelling time [ms]" from 0 to 4000. The x-axis shows "Beam 0". For Beam 0, there are two bars: a blue bar for "Scenario:B-Beams1, RRHDir:Same" and an orange bar for "Scenario:B-Beams1, RRHDir:Opposite". + +| Beam | Scenario:B-Beams1, RRHDir:Same [ms] | Scenario:B-Beams1, RRHDir:Opposite [ms] | +|--------|-------------------------------------|-----------------------------------------| +| Beam 0 | 1600 | 1600 | + +Figure 6.3.8.1-4: Beam dwelling times in bi-directional scenarios with 1 beam per RRH. The chart shows average dwelling times for Beam 0 in two scenarios: RRHDir:Same and RRHDir:Opposite. + +Figure 6.3.8.1-4: Average beam dwelling time with 1 beam per RRH for bidirectional scenarios + +![Figure 6.3.8.1-5: Average beam dwelling time with 2 beams per RRH for bidirectional scenarios. The chart shows average dwelling times for Beam 0 and Beam 1 in two scenarios: 'Scenario:B-Beams2, RRHDir:Same' (blue) and 'Scenario:B-Beams2, RRHDir:Opposite' (orange). An inset heatmap shows the beam coverage for Beam 1 and Beam 0.](12b521317c2c8ea33a1382d83e2b76be_img.jpg) + +Figure 6.3.8.1-5 is a bar chart titled "Beam dwelling times in bi-directional scenarios with 2 beams per RRH". The y-axis represents "Average dwelling time [ms]" ranging from 0 to 3000. The x-axis shows two beams, Beam 0 and Beam 1. For each beam, there are two bars: a blue bar for "Scenario:B-Beams2, RRHDir:Same" and an orange bar for "Scenario:B-Beams2, RRHDir:Opposite". An inset heatmap shows the beam coverage for Beam 1 and Beam 0, with the y-axis labeled "Beam 1" and "Beam 0" and the x-axis labeled "0" and "0". + +| Beam | Scenario:B-Beams2, RRHDir:Same [ms] | Scenario:B-Beams2, RRHDir:Opposite [ms] | +|--------|-------------------------------------|-----------------------------------------| +| Beam 0 | 1000 | 1000 | +| Beam 1 | 1400 | 1400 | + +Figure 6.3.8.1-5: Average beam dwelling time with 2 beams per RRH for bidirectional scenarios. The chart shows average dwelling times for Beam 0 and Beam 1 in two scenarios: 'Scenario:B-Beams2, RRHDir:Same' (blue) and 'Scenario:B-Beams2, RRHDir:Opposite' (orange). An inset heatmap shows the beam coverage for Beam 1 and Beam 0. + +Figure 6.3.8.1-5: Average beam dwelling time with 2 beams per RRH for bidirectional scenarios + +![Figure 6.3.8.1-6: Average beam dwelling time with 2 beams per RRH for bidirectional scenarios. The chart shows average dwelling times for Beam 0, Beam 1, Beam 2, and Beam 3 in two scenarios: 'Scenario:B-Beams4, RRHDir:Same' (blue) and 'Scenario:B-Beams4, RRHDir:Opposite' (orange). An inset heatmap shows the beam coverage for Beam 3, Beam 2, Beam 1, and Beam 0.](24b08adae8325d6d47100c2949505f87_img.jpg) + +Figure 6.3.8.1-6 is a bar chart titled "Beam dwelling times in bi-directional scenarios with 4 beams per RRH". The y-axis represents "Average dwelling time [ms]" ranging from 0 to 2500. The x-axis shows four beams, Beam 0, Beam 1, Beam 2, and Beam 3. For each beam, there are two bars: a blue bar for "Scenario:B-Beams4, RRHDir:Same" and an orange bar for "Scenario:B-Beams4, RRHDir:Opposite". An inset heatmap shows the beam coverage for Beam 3, Beam 2, Beam 1, and Beam 0, with the y-axis labeled "Beam 3" and "Beam 2" and the x-axis labeled "2 1 0 0 1 2". + +| Beam | Scenario:B-Beams4, RRHDir:Same [ms] | Scenario:B-Beams4, RRHDir:Opposite [ms] | +|--------|-------------------------------------|-----------------------------------------| +| Beam 0 | 500 | 500 | +| Beam 1 | 900 | 900 | +| Beam 2 | 1000 | 1000 | +| Beam 3 | 950 | 900 | + +Figure 6.3.8.1-6: Average beam dwelling time with 2 beams per RRH for bidirectional scenarios. The chart shows average dwelling times for Beam 0, Beam 1, Beam 2, and Beam 3 in two scenarios: 'Scenario:B-Beams4, RRHDir:Same' (blue) and 'Scenario:B-Beams4, RRHDir:Opposite' (orange). An inset heatmap shows the beam coverage for Beam 3, Beam 2, Beam 1, and Beam 0. + +Figure 6.3.8.1-6: Average beam dwelling time with 2 beams per RRH for bidirectional scenarios + +#### 6.3.8.2 Beam coverage analysis + +In HST deployment scenarios, the footprint of an RRH beam can be represented by an ellipse as shown in figure 6.3.8.2-1. It is assumed that UE aboard an HST is moving with constant velocity $\vec{v}$ and its trajectory is a straight line. An RRH is located at the point $G(0,0,h_{RRH})$ in which its antenna array boresight for the $k$ th beam is oriented towards a point $P_k(D_{min}, y_k, h)$ which is along the trajectory of UE. + +![Figure 6.3.8.2-1: RRH beam footprint. The diagram shows a 3D coordinate system with x, y, and z axes. A base station (RRH) is located at point G(0,0,h_RRH) on the z-axis. A user equipment (UE) is at point Q(0,0,h) on the z-axis. A beam, labeled 'Beam k', is directed from G towards a point C on a horizontal plane at z=h. The beam's footprint on this plane is an ellipse centered at C. The ellipse has a semi-major axis 'a' and a semi-minor axis 'b'. The ellipse intersects a line segment labeled 'Line x = D_min, z = h' at two points, P1(D_min, y1, h) and P2(D_min, y2, h). The distance from the z-axis to the line x = D_min is labeled D_min. The angle between the z-axis and the beam axis is theta'_k. The half-angle of the beam's horizontal beamwidth is theta_HPBW/2. The angle between the beam axis and the horizontal plane is phi'_k. The angle between the beam axis and the vertical z-axis is phi_HPBW. A vector v is shown along the line x = D_min, z = h. The distance from G to Q is labeled |GQ|, and the distance from Q to C is labeled |QC|.](0e32ab25c356a3b09f57f8011afd5ac8_img.jpg) + +Figure 6.3.8.2-1: RRH beam footprint. The diagram shows a 3D coordinate system with x, y, and z axes. A base station (RRH) is located at point G(0,0,h\_RRH) on the z-axis. A user equipment (UE) is at point Q(0,0,h) on the z-axis. A beam, labeled 'Beam k', is directed from G towards a point C on a horizontal plane at z=h. The beam's footprint on this plane is an ellipse centered at C. The ellipse has a semi-major axis 'a' and a semi-minor axis 'b'. The ellipse intersects a line segment labeled 'Line x = D\_min, z = h' at two points, P1(D\_min, y1, h) and P2(D\_min, y2, h). The distance from the z-axis to the line x = D\_min is labeled D\_min. The angle between the z-axis and the beam axis is theta'\_k. The half-angle of the beam's horizontal beamwidth is theta\_HPBW/2. The angle between the beam axis and the horizontal plane is phi'\_k. The angle between the beam axis and the vertical z-axis is phi\_HPBW. A vector v is shown along the line x = D\_min, z = h. The distance from G to Q is labeled |GQ|, and the distance from Q to C is labeled |QC|. + +Figure 6.3.8.2-1: RRH beam footprint + +The ellipse centred at $C(x_c, y_c, z_c)$ can be expressed as + +$$\frac{[(x-x_c) \cos \phi_k + (y-y_c) \sin \phi_k]^2}{a^2} + \frac{[(y-y_c) \cos \phi_k - (x-x_c) \sin \phi_k]^2}{b^2} = 1, \quad z = h, 0 < h < h_{RRH}$$ + +where + +$$a = \frac{|GQ|}{2} \left[ \tan \left( \theta'_k + \frac{\theta_{HPBW}}{2} \right) - \tan \left( \theta'_k - \frac{\theta_{HPBW}}{2} \right) \right], \quad \left( \theta'_k - \frac{\theta_{HPBW}}{2} \right) < \theta'_k < \left( \theta'_k + \frac{\theta_{HPBW}}{2} \right) < 90^\circ$$ + +$$b = \frac{|GQ|}{|QC|} \sec(\theta'_c) \tan \left( \frac{\phi_{HPBW}}{2} \right)$$ + +$$x_c = \frac{|QC|}{\sqrt{1 + \left( \frac{y_k}{u} \right)^2}}, \quad y_c = \frac{y_k}{u} x_c, \quad z_c = h$$ + +From trigonometry, $|\vec{QC}|$ can be derived from the elevation HPBW $\theta_{HPBW}$ , elevation pointing angle $\theta'_k$ , semimajor axis $a$ and the magnitude of $\vec{GQ}$ as follows + +$$|\vec{QC}| = |\vec{GQ}| \tan \left( \theta'_k - \frac{\theta_{HPBW}}{2} \right) + a$$ + +In the equation of the semi-minor axis, $\theta'_c$ is the angle between the vectors $\vec{GQ}$ and $\vec{GC}$ , which can be expressed in terms of the semi-major axis $a$ , elevation HPBW $\theta_{HPBW}$ and elevation pointing angle $\theta'_k$ . + +$$\theta'_c = \tan^{-1} \left( \tan \left( \theta'_k - \frac{\theta_{HPBW}}{2} \right) + \frac{a}{|GQ|} \right)$$ + +Referring to figure 6.3.8.2-1, the segment length of the UE's trajectory covered by the footprint of beam $k$ is the line segment joining the points $P_1(D_{min}, y_1, h)$ and $P_2(D_{min}, y_2, h)$ , which are the intersection points of the ellipse with the line $x = D_{min}, z = h$ . In determining these two points, rewriting the ellipse equation as a quadratic equation for $y$ gives + +$$\alpha y^2 + \beta y + \gamma = 0$$ + +where the coefficients are + +$$\alpha = a^2 \cos^2 \phi_k + b^2 \sin^2 \phi_k$$ + +$$\beta = 2[y_c(-a^2 \cos^2 \phi_k - b^2 \sin^2 \phi_k) + (D_{min} - x_c)(b^2 \cos \phi_k \sin \phi_k - a^2 \cos \phi_k \sin \phi_k)]$$ + +$$\gamma = y_c^2(a^2 \cos^2 \phi_k + b^2 \sin^2 \phi_k) + 2y_c(D_{min} - x_c)(a^2 \cos \phi_k \sin \phi_k - b^2 \cos \phi_k \sin \phi_k) + (D_{min} - x_c)^2 a^2 \sin^2 \phi_k + (D_{min} - x_c)^2 b^2 \cos^2 \phi_k - a^2 b^2$$ + +The two solutions to the quadratic equation are + +$$y_1 = \frac{-\beta - \sqrt{\beta^2 - 4\alpha\gamma}}{2\alpha}, \quad y_2 = \frac{-\beta + \sqrt{\beta^2 - 4\alpha\gamma}}{2\alpha}$$ + +The segment length $l_k$ (in metres) of the UE's trajectory covered by beam $k$ is given by + +$$l_k = y_2 - y_1$$ + +Thus, the dwelling time $t_k$ (in seconds) for beam $k$ is defined by + +$$t_k = \frac{l_k}{|\bar{v}|}$$ + +In order to determine the width of the footprint provided by beam $k$ , it is the points of intersection of the ellipse with a straight line passing through $P_k(D_{min}, y_k, h)$ perpendicular to the line $x = D_{min}, z = h$ . The width $w_k$ (in metres) of the footprint defined by beam $k$ is expressed as + +$$w_k = x_2 - x_1$$ + +where + +$$x_1 = \frac{-\beta' - \sqrt{\beta'^2 - 4\alpha'\gamma'}}{2\alpha'}, \quad x_2 = \frac{-\beta' + \sqrt{\beta'^2 - 4\alpha'\gamma'}}{2\alpha'}$$ + +$$\alpha' = a^2 \sin^2 \phi_k + b^2 \cos^2 \phi_k$$ + +$$\beta' = 2[x_c(-a^2 \sin^2 \phi_k - b^2 \cos^2 \phi_k) + (y_k - y_c)(b^2 \cos \phi_k \sin \phi_k - a^2 \cos \phi_k \sin \phi_k)]$$ + +$$\gamma' = x_c^2(a^2 \sin^2 \phi_k + b^2 \cos^2 \phi_k) + 2x_c(y_k - y_c)(a^2 \cos \phi_k \sin \phi_k - b^2 \cos \phi_k \sin \phi_k) + (y_k - y_c)^2 a^2 \cos^2 \phi_k + (y_k - y_c)^2 b^2 \sin^2 \phi_k$$ + +Table 6.3.8.2-1 shows the coverage length, width and dwelling time for 3 beams where the boresight is pointing to different positions along the UE's trajectory for Scenario A. + +**Table 6.3.8.2-1: Beam coverage length, width and dwelling time** + +| $D_{min} = 10 \text{ m}, \theta_{HPBW} = 12.6^\circ, \phi_{HPBW} = 12.6^\circ$ | | | | | +|--------------------------------------------------------------------------------|-------------------------------|-------|-------|-------| +| Beam $k$ | $P_k(D_{min}, y_k, h)$ | $l_k$ | $w_k$ | $t_k$ | +| 0 | $P_k(D_{min}, 5D_{min}, h)$ | 57 m | 14 m | 0.6 s | +| 1 | $P_k(D_{min}, 7.5D_{min}, h)$ | 244 m | 31 m | 2.5 s | +| 2 | $P_k(D_{min}, 8.5D_{min}, h)$ | 813 m | 60 m | 8.4 s | + +As can be observed in table 6.3.8.2-1, the beam coverage length shrinks as $y_k$ decreases, resulting in non-uniform beam coverage. A beam with very short beam segment length $l_k$ is not useful for HST because the UE may not be able detect it before moving to the adjacent beam. As such, the number of useful beams per RRH can be limited, which depends on deployment scenarios. Referring to the equation of the ellipse, the beam footprint size is a function of the semimajor axis $a$ and semiminor axis $b$ . It can be observed from the equation that one key parameter that influences the magnitude of $a$ and $b$ is the elevation HPBW $\theta_{HPBW}$ and azimuth HPBW $\phi_{HPBW}$ . This means, those beams with a short segment length can be increased by widening the HPBW. However, it is important to note that antenna array directivity is inversely proportional to the HPBW; that is, a wider HPBW leads to lower antenna-array directivity. As the RRH typically employs uniform rectangular antenna arrays, the directivity $D$ can be expressed in terms of the elevation and azimuth HPBW as [2] + +$$D \approx \frac{\pi^2}{\phi_{HPBW} \theta_{HPBW}}$$ + +For Beam $k$ , if $\theta_{HPBW}$ and $\phi_{HPBW}$ are widened by a factor of $\sigma_{\theta,k}$ and $\sigma_{\phi,k}$ , respectively, the resultant directivity $D_k$ is + +$$D_k = \frac{\pi^2}{(\sigma_{\theta,k} \theta_{HPBW})(\sigma_{\phi,k} \phi_{HPBW})}$$ + +Let $D_0$ denote the original directivity of Beam 0 (where the HPBW is not widened) and dividing it by $D_k$ yields + +$$\frac{D_0}{D_k} = \sigma_{\phi,k} \sigma_{\theta,k}$$ + +As compared with $D_0$ , $D_k$ is now dropped by the product of $\sigma_{\phi,k}$ and $\sigma_{\theta,k}$ , where both terms are real numbers. In order to ensure the link budget (or performance) of Beam $k$ is not worse than Beam 0 as a consequence of using lower directivity, the product ( $\sigma_{\phi,k} \sigma_{\theta,k}$ ) should be bounded by the condition + +$$1 \leq (\sigma_{\phi,k} \sigma_{\theta,k}) \leq \left(\frac{r_0}{r_k}\right)^2, \quad r_k < r_0$$ + +where the term $\left(\frac{r_0}{r_k}\right)^2$ is the ratio of the free space path loss between Beams 0 and $k$ , and for $r_0 = |\overline{GP_0}|$ , and $r_k = |\overline{GP_k}|$ . Beam 0 serves as a baseline beam whose directivity equals the original unenlarged HPBW. When $\sigma_{\phi,k} \sigma_{\theta,k} = \left(\frac{r_0}{r_k}\right)^2$ the drop in directivity for Beam $k$ is equalized by the decrease in free space path loss with reference to Beam 0. + +Widening the HPBW of beams with a short segment length in coverage areas near to the RRH provides an alternative solution to mitigate the problem identified in clause 6.3.4.1 for unidirectional deployment scenarios, where the UE is moving in the opposite direction to the pointing direction of RRH Tx beams. It can also be used to extend coverage in areas near to RRH in bi-directional deployment scenarios, and to reduce the large propagation delay jump, which causes uplink timing issues. + +# 7 Identified RAN4 requirements + +## 7.1 CPE RF core requirements + +RAN4 will further study and discuss the CPE core requirements. + +Concerning the CPE RF requirements RAN will further discuss and select among following options for the baseline power class: + +- Baseline power class for FR2 HST: + - 1) Option-1: PC4 as baseline, and FFS PC4 requirement is applicable to FR2 HST scenario; or + - 2) Option-2: To define new PC for FR2 HST; or + - 3) Option-2a: To define new PC for FR2 HST, with PC5 requirement as baseline. + +Additionally, RAN4 will further discuss how to specify the UE RF requirements. Options listed are: + +- Option-1: Provide an applicability rule of FR2 PC4 for the train-roof-mounted UE for FR2 HST scenario, i.e., the applicable FR2 PC4 requirement set for FR2 HST scenario; or +- Option-2: Revisit the full set of UE RF requirements for FR2 PC4 UE; or +- Option-3: New RF requirement is defined for FR2 HST UE which is different from PC4, specifically, the min peak EIRP for FR2 HST UE follows the agreement for PC5(new FR2 FWA UE). + +For power class, it is agreed to introduce a new power class for FR2 HST UE (UE power class 6), by numbering as UE power class 6 and specifying UE type as 'High Speed Train Roof-Mounted UE': + +**Table 7.1-1: New power class 6 for FR2 HST UE** + +| UE Power class | UE type | +|----------------|----------------------------------| +| 1 | Fixed wireless access (FWA) UE | +| 2 | Vehicular UE | +| 3 | Handheld UE | +| 4 | High power non-handheld UE | +| 5 | Fixed wireless access (FWA) UE | +| 6 | High Speed Train Roof-Mounted UE | + +The RF requirement applicability rule (based on NW flag signalling) is not introduced. FR2 HST UE shall satisfy the relevant RF requirement, regardless of this NW flag signalling. Additionally, RAN4 define unified RF requirement for both uni- and bi-directional RRH deployment. + +It was agreed that the UE TX minimum output power and transmit signal quality for FR2 PC6 UE, RAN4 adopt the same requirement as FR2 PC5 UE for are: + +- Minimum output power, and +- Transmit signal quality + +For UE TX requirement for UL-MIMO it was agreed that similar to other power classes, RAN4 define UL-MIMO TX requirements for FR2 PC6 UE, by following the same requirement as PC6 single TX port requirement numerically. + +It was agreed that unified RF requirements for FR2 HST UE are defined except spherical coverage. RAN4 will further discuss the spherical coverage requirements: + +- Option 1: use the union of the largest spherical coverage of theta and phi to define the unified requirements +- Option 2: The unified RF requirement for FR2 HST UE is defined based on one particular scenario requiring the largest spherical coverage + +RAN4 agreed not to define core requirement for one-panel based spherical coverage requirement. + +For UE RF requirement framework, RAN4 agreed to use the assumption, that UE has two panels, i.e., back-to-back panels, which will be used to derive spherical coverage requirements. + +RAN4 will further discuss whether one panel based spherical coverage requirement will be specified and whether to mandate two panels for UE RF requirement framework. Concerning spherical coverage and the direction of the antenna panels RAN4 reached following agreements: + +- Directions of antenna panels: + - Boresight directions for forward and backward panels shall be declared by UE vendors. It is FFS whether the limitation on the boresight directions is needed. +- Coordination system to be used for requirement definition: + - Option-1: absolute coordination system + - Option 2: relative coordination system (relative to the claimed boresight direction) +- Spherical coverage x%-tile point per panel: + - Azimuth angle (i.e., phi) range to cover: + - Option-1: [-45, +45] degree relative to absolute coordination system + - Option-2: [-25, +25] degree relative to UE declared boresight direction + - Other options are not precluded + - Elevation angle (i.e., theta) range to cover: + - Option-1: [45, 90] degree relative to absolute coordination system + +- Option-2: [-10, +10] degree relative to UE declared boresight direction + +Related to spherical coverage requirement – Coordination system RAN4 agreed to use the absolute coordination system as well as the following as baseline: + +The minimum EIRP measured over the spherical coverage evaluation areas specified below is defined as the spherical coverage requirement and is found in Table 7.1-2 below. UE spherical coverage evaluation areas are found in Table 7.1-3 below, by consisting of Area-1 and Area-2, in the reference coordinate system in Annex J.1. The requirement is verified with the test metric of EIRP (Link= Spherical coverage grid, Meas=Link angle). + +**Table 7.1-2: UE spherical coverage for power class 6.** + +| Band | $\Delta\text{MB}_{\text{P,n}}$ (dB) | $\Delta\text{MB}_{\text{S,n}}$ (dB) | +|------|-------------------------------------|-------------------------------------| +| n257 | 0.7 | 0.7 | +| n258 | 0.7 | 0.7 | +| n261 | 0.7 | 0.7 | + +**Table 7.1-3: UE spherical coverage evaluation areas for power class 6.** + +| | $\theta$ range (degree) | $\theta$ range (degree) | +|--------|-------------------------|-------------------------| +| Area-1 | 90 to 60 | -37.5 to + 37.5 | +| Area-2 | 90 to 60 | 142.5 to 217.5 | + +NOTE 1: When testing power class 6 UEs, DUT orientation can be determined according to the UE spherical coverage evaluation areas, not necessarily following default alignment in Figure J.1-2 or positioning guidelines in clause J.3. + +NOTE 2: High speed train deployment is expected to be w.r.t. the reference coordination system: $\theta = 90$ (degree) corresponds to the ground plane the train is running on, and $\phi = 0$ or $180$ with $\theta = 90$ are the train track directions + +Agreement is that network signaling is provided to configure UE to follow enhanced RRM requirement Set 2. + +Evaluation on EIRP spherical coverage requirement over the above baseline for UE spherical evaluation areas is FFS. + +RAN4 agreed that for FR2 HST UE, RAN4 adopt REFSSENS requirement as PC5, that is: + +**Table 7.1-4: FR2 HST UE REFSSENS requirement.** + +| Operating Band | REFSENS (dBm) / Channel bandwidth | | | | +|----------------|-----------------------------------|---------|---------|---------| +| | 50 MHZ | 100 MHZ | 150 MHZ | 200 MHZ | +| n257 | -92.6 | -89.6 | -86.6 | -83.6 | +| n258 | -92.8 | -89.8 | -86.8 | -83.8 | +| n261 | -92.6 | -89.6 | -86.6 | -83.6 | + +NOTE 1: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in clause 6.2.4 + +### 7.1.1 Minimum Peak EIRP + +Minimum peak EIRP requirement for FR2 HST UE it is agreed to adopt 30.x dBm (similar to PC5) as baseline. + +A multi-band relaxation factor of 0.7 dB which is similar to PC5 is introduced as shown in table 7.1.1-1. + +**Table 7.1.1-1: Multi-band relaxation.** + +| Band | $\Delta\text{MB}_{\text{P,n}}$ (dB) | $\Delta\text{MB}_{\text{S,n}}$ (dB) | +|------|-------------------------------------|-------------------------------------| +| n257 | 0.7 | 0.7 | +| n258 | 0.7 | 0.7 | +| n261 | 0.7 | 0.7 | + +Concerning Spherical coverage requirement and EIRP drop from min. Peak EIRP it was agreed to allow 10dB EIRP drop (i.e., x dB lower than min. Peak EIRP requirement). + +### 7.1.2 Beam Correspondence + +For the roof mounted HST UE the Rel-15 beam correspondence apply, and the FR2 HST UE (roof-mounted UE type) shall mandatorily support *beamCorrespondenceWithoutUL-BeamSweeping*. + +No need to introduce Beam Correspondence tolerance requirement because all FR2 HST UE need mandatory support of Rel-15 BC without uplink beam sweeping. If Rel-15 Beam Correspondence feature *beamCorrespondenceWithoutUL-BeamSweeping* is mandatorily supported by FR2 HST UE, then by following PC3 BC requirement: + +- For Rel-15 Beam Correspondence capable UE, the UE shall meet the minimum peak EIRP requirement and spherical coverage requirement with its autonomously chosen UL beams and without uplink beam sweeping. Such UE is considered to have met the beam correspondence tolerance requirement. In other words, no need to introduce Beam Correspondence requirement for as Rel-15 PC3. + +FR2 HST UE support of Rel-16 feature *beamCorrespondenceSSB-based-r16* shall be mandated but the support of Rel-16 *beamCorrespondenceCSI-RS-based-r16* shall be optional. + +For FR2 HST UE, the beam correspondence support can be summarized in the following table: + +**Table 7.1.2-1: Beam correspondence support for a UE supporting FR2 HST.** + +| FR2 Power Class | Rel-15 BC Feature beamCorrespondenceWithoutUL-BeamSweeping | Rel-16 SSB based enhanced BC beamCorrespondenceSSB-based-r16 | Rel-16 CSI-RS based enhanced BC beamCorrespondenceCSI-RS-based-r16 | Requirement Applicability for (1) Minimum peak EIRP, spherical coverage requirement (2) BC Tolerance requirement | Side condition | +|-------------------|-------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| FR2 HST UE (PC X) | Supported (Mandatory) | Supported (Mandatory) | Not Supported | Meet (1) w/o UL beam sweeping BC Tolerance req. (2) is met implicitly | Side condition for SSB based enh. BC (CSI-RS not provided) | +| | | | Supported | | Side condition for CSI-RS based enh. BC (weak SSB) | + +For PC6 EIS spherical coverage requirement, the side conditions for beam correspondence requirement can be derived according by: + +- $\text{Minimum SSB\_RP} = \text{EIS spherical coverage(PC6, n259, 50MHz)} - 10 \cdot \log_{10}(\text{nrofRBs} \times 12) - \text{SNR(at Refsens)} + \text{SSB } \hat{E}_s/\text{Iot} + \Delta\text{MB}_s$ + +For EIS Spherical Coverage requirements, the text in the follow table is agreeable but the numbers in the table will be updated based on the agreements: + +**Table 7.1.2-2: EIS spherical coverage for power class 6** + +| Operating Band | Max EIS over UE spherical coverage evaluation areas (dBm) / Channel bandwidth | | | | +|----------------|-------------------------------------------------------------------------------|---------|---------|---------| +| | 50 MHZ | 100 MHZ | 200 MHZ | 400 MHZ | +| n257 | [-80.6] | [-77.6] | [-74.6] | [-71.6] | +| n258 | [-80.8] | [-77.8] | [-74.8] | [-71.8] | +| n261 | [-80.6] | [-77.6] | [-74.6] | [-71.6] | + +NOTE 1: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1 + +## 7.2 RRM requirements + +Concerning the maximum supported speed for FR2 HST RAN4 agreed to use 350kmph as a reference maximum train speed and define RRM requirements to guarantee that. + +It was agreed to add a flag to enable the UE to identify different/enhanced RRM requirements in HST FR2 deployments. FR2 HST UE has the capacity to support both unidirectional and bidirectional deployment scenarios. RAN4 agreed to introduce network assistance to inform UE on the FR2 HST deployment type (uni-directional or bi-directional). No enhanced requirement should be applied to other than PC6 UEs even when HST FR2 flags are configured. + +PC6 shall be used to identify the feature support of HST FR2 operation. + +RAN4 agreed to introduce dedicated new RRC based network signalling flag will be specified to enable/disable one shot large UL timing adjustment. Such RRC based network signalling is not limited to a particular FR2 HST deployment and/or scenarios, i.e., bi-directional scenario or uni-directional scenario. + +In Scenario A, whether the RRH position on one side or both sides of railway tracks have no impact on RRM requirements under the assumption that FR2 HST UE boresight direction (or the beam direction if there is only one beam) is parallel to the track. + +Under FR2 HST scenarios, the PSS/SSS detection is robust to deal with ISI and time differences. + +Additional need for network signalling and CPE capabilities for HST FR2 deployments continued based on the deployment options and presence of non-CPE UEs. It was agreed that it is not necessary to introduce UE capability to indicate the support of FR2 HST. + +It was also concluded that there is no need for CPE capability to change beam sweep number in uni-/bi-directional operation. + +RAN4 agreed to introduce network signaling to configure UE to follow either Set 1 or Set 2 RRM requirements. + +Concerning the number of Rx Beams from RRM perspective RAN4 agreed that related to the scope of the RRM requirements and the requirements for Scenario A and scenario B to only define two sets of enhanced RRM requirements in terms of number of RX beams (i.e. RX beam sweeping scaling factor) per UE: + +- Set 1: 2 RX beams +- Set 1: 6 RX beams + +RAN4 will introduce network signalling to configure UE to follow either Set 1 or Set 2 RRM requirements. + +Set 1 requirements are developed based on the analysis with $D_{\min} = 10\text{m}$ and $D_s = 750\text{m}$ , and the recommended applicable range of $D_{\min}$ for Set 1 requirement is $D_{\min} \leq [30]\text{ m}$ . For the deployment with a larger $D_{\min}$ , set 2 requirements are recommended to be configured by the network. + +Regarding RRM requirements for scenario A and scenario B, for uni-directional and bi-directional deployments, it was agreed that there separate requirements for uni-/bi-directional deployments will not be developed. + +For scenario B only, when considering requirements for RRH deployment on both sides of the track, the RRH positions at one/both sides of rail track doesn't have impact on 6Rx beams agreement in Scenario B (set 2). + +Concerning Lightweight network assistance signaling it will be discussed further which NWA signaling is needed: + +- Option 1: Enable network assisted signaling of SSB index and order per RRH +- Option 2: The network assistance signaling of SSB configuration shall not be introduced in Rel-17 +- Option 3: Introduce inter-RRH indication +- Option 4: Other options are not precluded + +For Inter-RRH indication RAN4 agreed not introduce explicit inter-RRH indication signalling for NR FR2 HST in Rel-17. + +### UE capabilities: + +FR2 HST UE (power class 6 UE) shall mandatorily support both Set 1 and Set 2 enhanced RRM requirements, in terms of different RX beams (i.e., RX beam sweeping scaling factor) per UE. + +It is agreed to introduce feature group x-2 “Support of one shot large UL timing adjustment” with prerequisite feature group (x-1, “Support of FR2 HST operation”). + +### 7.2.1 Idle/inactive mode + +RAN agreed for idle/inactive mode that the cell reselection requirements in IDLE/INACTIVE mode are enhanced. + +Concerning requirements for when UE is applying long DRX RAN4 agreed to apply the existing R16 requirements for when the long DRX cycles are used, i.e. above the upper bound of DRX cycle. + +HST FR2 enhanced requirement is applied to SMTC $\leq 40$ ms. SMTC periodicity is not restricted. + +RAN4 will only define enhanced requirements for DRX 320 ms and requirements for longer DRX cycles are left without changes. + +For the M2 scaling factor for short DRX the way forward is to use as baseline: $M2 = 1.5$ if SMTC periodicity $> [40]$ ms, otherwise $M2=1$ . Discussion continues whether different scaling factor is needed for scenario-B with two-side RRH. + +RAN4 defined enhanced requirements for Cell reselection in IDLE/INACTIVE mode for DRX 320 ms in HST FR2 deployments according to table: + +**Table 7.2.1-1: Cell reselection in IDLE/INACTIVE mode.** + +| DRX cycle length [s] | Scaling Factor (N1) | $T_{\text{detect,NR\_intra}}$ [s] (number of DRX cycles) | $T_{\text{measure,NR\_intra}}$ [s] (number of DRX cycles) | $T_{\text{evaluate,NR\_intra}}$ [s] (number of DRX cycles) | +|----------------------|-------------------------|----------------------------------------------------------|-----------------------------------------------------------|------------------------------------------------------------| +| 0.32 | 2 or 6 Note1 | $2.56 \times N1 \times M2$ (8 x N1 x M2) | $0.32 \times N1 \times M3$ (1 x N1 x M3) | $0.96 \times N1 \times M4$ (3 x M4) | +| 0.64 | 5 | $17.92 \times N1$ (28 x N1) | $1.28 \times N1$ (2 x N1) | $5.12 \times N1$ (8 x N1) | +| 1.28 | 4 | $32 \times N1$ (25 x N1) | $1.28 \times N1$ (1 x N1) | $6.4 \times N1$ (5 x N1) | +| 2.56 | 3 | $58.88 \times N1$ (23 x N1) | $2.56 \times N1$ (1 x N1) | $7.68 \times N1$ (3 x N1) | + +NOTE 1: N1 refers to the number of Rx beams and equals 2 for Set 1, and 6 for Set 2 + +NOTE 2: when SMTC $\leq 40$ ms, $M2 = M3 = M4 = 1$ ; and when SMTC $> 40$ ms, $M2 = 1.5$ , $M3 = M4 = 2$ + +NOTE 3: The requirement in this table shall only apply to power class 6 UE, when the network signaling [*highSpeedMeasFlag-r17*] is configured to [set1] or [set2]. + +N1 refers to the number of Rx beams and equals 2 for Set 1, and 6 for Set 2 + +### 7.2.2 Connected mode + +For connected mode mobility RAN4 agreed not to support RRC Release with Redirection in the FR2 HST scenario. + +RAN4 agreed to revise the TCI state known conditions for the FR2 HST scenario. + +Concerning requirements for when UE is applying long DRX RAN4 agreed to apply the existing R16 requirements for when the long DRX cycles are used, i.e. above the upper bound of DRX cycle. + +HST FR2 enhanced requirement is applied to SMTC $\leq 40$ ms. SMTC periodicity is not restricted. + +For handover and the criteria of known cell for FR2, the target FR2 cell is known if it has been meeting the relevant cell identification requirement during the last 5 seconds; otherwise, it is unknown. + +For RLM and BFD the current sharing factor P and PCBD can be reused for FR2 HST. + +For the Connected mode, RAN4 assumes that as baseline for developing the UE requirements, the DRX upper bound for enhanced RRM HST FR2 requirements is [80]ms + +For Handover RAN4 will not enhance requirements for HO to unknown cell. Additionally, as current, if the target cell is a known cell, then $T_{\text{search}} = 0$ ms. + +#### Deployment-related issues: + +The DRX upper bound = 80 ms applies both to Sets 1 (Scenario-A) and 2 (Scenario-B), there will be no special consideration for two-side RRH deployment for RRM requirements definition. + +For the change of RRH panel orientation in uni-directional deployments RAN4 will not define defined additional network signalling to identify to the UE a change of RRH panel orientation in uni-directional deployment. + +##### For RLM/BFD requirements: + +It was agreed that the existing 1280ms duration for known condition is applied for FR2 HST scenario. RAN4 will further study the RLM/BFD requirements for DRX $\leq 80$ ms for FR2 HST scenarios: + +- Option 1: following RX beam factor for set-1 and set-2 +- Option 2: The existing RLM/BFD requirements for DRX $\leq 80$ ms is applied + +For CSI-RS based RLM and BFD, there is no standard impact for Rel-17 FR2 HST UE (i.e., FR2 PC6 UE). + +##### For CBD requirements: + +RAN4 will not develop enhancement on CBD requirements for DRX $\leq 80$ ms. + +##### For PSS/SS and intra-frequency measurement: + +It was agreed to reuse the Rel-16 FR1 HST scaling factor M2 for FR2 HST with the same SMTC periodicity bound of 40ms unless technical issues identified + +##### For L1-RSRP measurement: + +RAN4 will reuse the Rel-16 FR1 HST scaling factor K for FR2 HST L1-RSRP measurement requirement, with the same SMTC periodicity bound of 40ms unless technical issues identified. It is also agreed to define separate sets of requirements for deployment Scenarios A and B + +**Table 7.2.2-1: L1-RSRP measurement requirements for deployment Set-1.** + +| Configuration | $T_{\text{L1-RSRP Measurement Period SSB}}$ (ms) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| non-DRX | $\max(T_{\text{Report}}, \text{ceil}(M * P * N_A) * T_{\text{SSB}})$ | +| DRX cycle $\leq 80$ ms | $\max(T_{\text{Report}}, \text{ceil}(M * P * N_A * M_2) * \max(T_{\text{DRX}}, T_{\text{SSB}}))$ | +| NOTE 1: $T_{\text{SSB}}$ = ssb-periodicityServingCell is the periodicity of the SSB-Index configured for L1-RSRP measurement. $T_{\text{DRX}}$ is the DRX cycle length. $T_{\text{Report}}$ is configured periodicity for reporting. | | +| NOTE 2: $M_2 = 1.5$ if SMTC periodicity $> 40$ ms; otherwise $M_2 = 1$ | | + +$N_A = 2$ + +**Table 7.2.2-2: L1-RSRP measurement requirements for deployment Best-2.** + +| Configuration | $T_{L1-RSRP\ Measurement\ Period\ SSB\ (ms)}$ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| non-DRX | $\max(T_{Report}, \text{ceil}(M * P * N_B) * T_{SSB})$ | +| DRX cycle $\leq 80\text{ms}$ | $\max(T_{Report}, \text{ceil}(M * P * N_B * M2) * \max(T_{DRX}, T_{SSB}))$ | +| NOTE 1: $T_{SSB}$ = ssb-periodicityServingCell is the periodicity of the SSB-Index configured for L1-RSRP measurement. $T_{DRX}$ is the DRX cycle length. $T_{Report}$ is configured periodicity for reporting. | | +| NOTE 2: $M2 = 1.5$ if SMTC periodicity $> 40\text{ ms}$ ; otherwise $M2 = 1$ | | + +$N_B = 6$ + +RAN4 is still FFS whether enhanced requirement should be applied to other than PC6 UEs even when HST FR2 flags are configured. + +#### Scheduling Restrictions: + +Concerning scheduling restriction related to large propagation delay difference caused by inter-RRH beam switching in FR2 HST: + +- Option 1: FFS the necessity of UL scheduling restriction (i.e., the UE is not expected to transmit PUCCH/PUSCH/SRS) after cross-RRH TCI state switch until the first TRS is received after the TCI state switch; or +- Option 2: RAN4 introduce scheduling restriction for the symbol before and after reference symbols used for L1-RSRP measurement and Such scheduling restriction shall be specified in clauses of L1 measurement (i.e., L1-SINR and L1-RSRP). + +It was agreed that no enhancements are needed in HO requirement. Additionally, it was agreed not to define RRC Re-establishment requirement to known cell for HST FR2. RAN4 will define RRC connection re-establishment requirement to unknown NR intra-frequency cell $T_{identify\_intra\_NR} = \max(1000\text{ ms}, 10 \times N1 \times T_{SMTC})$ when $\text{SINR} \geq -8\text{dB}$ , the value of $N1$ refers to agreed RX beam number. + +Cell detection requirements for Set 1: + +**Table 7.2.2-3: Time period for PSS/SSS detection when [flag1] is configured, (Frequency range FR2).** + +| DRX cycle | $T_{PSS/SSS\ sync\_intra}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| No DRX | $\max(600\text{ms}, \text{ceil}([6] \times K_p \times K_{layer1\_measurement}) \times \text{SMTC period})^{Note\ 1} \times \text{CSSF}_{intra}$ | +| DRX cycles $\leq 80\text{ ms}$ | $\max(600\text{ms}, \text{ceil}([6] \times M2^{Note\ 2} \times K_p \times K_{layer1\_measurement}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{intra}$ | +| $80\text{ms} < \text{DRX cycles} \leq 320\text{ms}$ | $\max(600\text{ms}, \text{ceil}(M2 \times M_{pss/sss\_sync\_w/o\_gaps} \times K_p \times K_{layer1\_measurement}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{intra}$ | +| DRX cycle $> 320\text{ms}$ | $\text{ceil}(M_{pss/sss\_sync\_w/o\_gaps} \times K_p \times K_{layer1\_measurement}) \times \text{DRX cycle} \times \text{CSSF}_{intra}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | +| NOTE 2: $M2 = 1.5$ if SMTC periodicity $> 40\text{ ms}$ ; otherwise $M2 = 1$ | | + +Cell detection requirements for Set 2: + +**Table 7.2.2-4: Time period for PSS/SSS detection when [flag2] is configured, (Frequency range FR2).** + +| e | T_{\text{PSS/SSS\_sync\_intra}} | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| No DRX | $\max(600\text{ms}, \text{ceil}([18] \times K_p \times K_{\text{layer1\_measurement}}) \times \text{SMTC period})^{\text{Note 1}} \times \text{CSSF}_{\text{intra}}$ | +| DRX cycles $\leq$ 80ms | $\max(600\text{ms}, \text{ceil}([18] \times M2^{\text{Note 2}} \times K_p \times K_{\text{layer1\_measurement}}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{\text{intra}}$ | +| 80ms $<$ DRX cycles $\leq$ 320ms | $\max(600\text{ms}, \text{ceil}(M2 \times M_{\text{pss/sss\_sync\_w/o\_gaps}} \times K_p \times K_{\text{layer1\_measurement}}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{\text{intra}}$ | +| DRX cycle $>$ 320ms | $\text{ceil}(M_{\text{pss/sss\_sync\_w/o\_gaps}} \times K_p \times K_{\text{layer1\_measurement}}) \times \text{DRX cycle} \times \text{CSSF}_{\text{intra}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | +| NOTE 2: $M2 = 1.5$ if SMTC periodicity $> 40$ ms; otherwise $M2 = 1$ | | + +Measurement period for Set-1: + +**Table 7.2.2-5: Measurement period for intra-frequency measurements without gaps when [flag1] is configured (FR2).** + +| DRX cycle | T_{\text{SSB\_measurement\_period\_intra}} | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| No DRX | $\max(400\text{ms}, \text{ceil}([6] \times K_p \times K_{\text{layer1\_measurement}}) \times \text{SMTC period})^{\text{Note 1}} \times \text{CSSF}_{\text{intra}}$ | +| DRX cycles $\leq$ 80ms | $\max(400\text{ms}, \text{ceil}([6] \times M2^{\text{Note 2}} \times K_p \times K_{\text{layer1\_measurement}}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{\text{intra}}$ | +| 80ms $<$ DRX cycles $\leq$ 320ms | $\max(400\text{ms}, \text{ceil}(M2 \times M_{\text{meas\_period\_w/o\_gaps}} \times K_p \times K_{\text{layer1\_measurement}}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{\text{intra}}$ | +| DRX cycle $>$ 320ms | $\text{ceil}(M_{\text{meas\_period\_w/o\_gaps}} \times K_p \times K_{\text{layer1\_measurement}}) \times \text{DRX cycle} \times \text{CSSF}_{\text{intra}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | +| NOTE 2: $M2 = 1.5$ if SMTC periodicity $> 40$ ms; otherwise $M2 = 1$ | | + +Measurement period for Set-2: + +**Table 7.2.2-6: Measurement period for intra-frequency measurements without gaps when [flag2] is configured (FR2).** + +| DRX cycle | T_{\text{SSB\_measurement\_period\_intra}} | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| No DRX | $\max(400\text{ms}, \text{ceil}([18] \times K_p \times K_{\text{layer1\_measurement}}) \times \text{SMTC period})^{\text{Note 1}} \times \text{CSSF}_{\text{intra}}$ | +| DRX cycles $\leq$ [80ms] | $\max(400\text{ms}, \text{ceil}([18] \times M2^{\text{Note 2}} \times K_p \times K_{\text{layer1\_measurement}}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{\text{intra}}$ | +| 80ms $<$ DRX cycles $\leq$ 320ms | $\max(400\text{ms}, \text{ceil}(M2 \times M_{\text{meas\_period\_w/o\_gaps}} \times K_p \times K_{\text{layer1\_measurement}}) \times \max(\text{SMTC period}, \text{DRX cycle})) \times \text{CSSF}_{\text{intra}}$ | +| DRX cycle $>$ 320ms | $\text{ceil}(M_{\text{meas\_period\_w/o\_gaps}} \times K_p \times K_{\text{layer1\_measurement}}) \times \text{DRX cycle} \times \text{CSSF}_{\text{intra}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | +| NOTE 2: $M2 = 1.5$ if SMTC periodicity $> 40$ ms; otherwise $M2 = 1$ | | + +RAN4 agreed to define the scaling factors factors ( $M_{\text{pss/sss\_sync\_w/o\_gaps}}$ and $M_{\text{meas\_period\_w/o\_gaps}}$ ) equal to 6 for Set 1 and [18] for Set 2. + +Define scaling factor N for no DRX and DRX cycle $\leq$ 80 ms by following the number of RX beams per UE for Set 1 and Set 2: Set 1: 2 RX beams; (2) Set 2: 6 RX beams. + +TCI switching delay: + +RAN4 will introduce additional TCI switching delay for UE to perform fine downlink timing tracking. Additionally, an additional symbol of delay during TCI switching when $T_{Ok}=0$ for PC6 UEs will be defined + +#### Uplink Spatial Relation Switch Delay: + +For the known conditions for spatial relation when associated with DL-RS, the requirement defined in Rel-16 shall be reused, and no standard impact is expected for Rel-17 FR2 HST + +#### 7.2.2.1 UE UL transmit timing + +RAN4 discussed the UE requirements related to UE transmit timing and the UE gradual timing adjustment if the necessary adjustments to be made to the UE uplink timing exceed the current adjustment rules. + +RAN4 agreed that it is up to network configuration to enable one shot large uplink timing adjustment mechanism. If one shot large uplink timing adjustment is disabled, existing uplink timing adjustment, i.e., RA based mechanism, and related existing RAN4 requirements will be applied when needed. Otherwise, RAN4 will introduce a mechanism for one shot large uplink timing adjustment for FR2 HST scenarios with UE allowed to adjust uplink timing beyond $T_q$ . + +With network signalling to enable one shot large timing adjustment UE shall apply one shot large timing adjustment on TCI switching occasion if UE measurement on DL timing difference is larger than a timing difference threshold: + +- Option 1: $9 \cdot 64 \cdot T_c = CP/2$ +- Option 2: $T_q = 4.5 \cdot 64 \cdot T_c = CP/4$ +- Option 3: Select a threshold from above options or new options, and the performance degradation due to timing error on both DL and UL to UE and network after TCI state switch is expected if network assistant signalling to inform UE on cross RRH TCI state switch is not introduced. +- Other options are not precluded + +RAN4 will further study RRM requirement, and acceptable value of residual error in UE large one-shot UL timing adjustment. RAN4 will further discuss the accuracy performance and testing issues based on conclusion of related procedures. + +##### Random Access Procedure: + +No specification change shall be introduced for the current RA procedure due to Rel-17 FR2 HST. + +##### 7.2.2.1.1 Random Access based timing adjustment + +When large one-shot UL timing adjustment procedure is disabled, i.e., when the *highSpeedLargeOneStepUL-TimingFR2-r17* flag defined in TS 38.331 is false, there is still a need to adjust UL timing of the UE to address a large difference in radio propagation delays in between the source and the target beams. + +A large jump in propagation delays is typical for inter-RRH TCI state switch in uni-directional scenarios, e.g., shown in Figure 5.2.1-2. However, RAN4 has also agreed that *highSpeedLargeOneStepUL-TimingFR2-r17* signaling is not limited to a particular FR2 HST deployment and/or scenarios, i.e., bi-directional scenario or uni-directional scenario. Therefore, network-based solution shall also be applicable for the bi-directional scenarios (e.g., shown in Figures 5.2.2-5,6,7) where the jump in propagation delays cannot be avoided either. + +Since beam management procedures were originally designed in NR Rel-15, it is generally assumed that the Tx beams are collocated, i.e., a large propagation delay difference in between the source and the target beams is not expected. Hence, TCI state change does not imply any explicit UL synchronization procedure, such as RA as a part of HO. + +The straightforward approach in the term of HST FR2 Rel-17 WI is to use already existing and standardized procedures for UL timing adjustment. Random Access (RA) towards the target TCI state provides a possibility for the network to measure the propagation delay from the RA preamble and to signal the accurate UL timing advance value with random access reply (RAR). Transmission of RA preamble itself can be triggered with the PDCCH order. + +An example of sequence diagram of the procedure is shown in Figure 7.2.2.1-1. The upper box includes the beam management related operations that are repeated periodically, such as transmission of reference signals in the UL, network-initiated and small-scale autonomous UL timing adjustments, beam/SSB measurements, detection, and + +reporting, etc. The core of the network-controlled UL timing adjustment mechanism is contained in the lower box that is executed when the NW triggers TCI state switch. + +![Sequence diagram of RA-based UL timing adjustment at TCI state switch. The diagram shows interactions between UE, RRH1, and RRH2. It is divided into two main parts: a 'Repeat' section and a 'UL timing adjustment at TCI state switch' section. The 'Repeat' section includes steps 1-9, involving user data, RSs, MAC-CE TAC, TA adjustment, SSB1, SSB2, SSB2 detection, CSI L1-RSRP report, and autonomous small TA adjustment. The 'UL timing adjustment' section includes steps 10-16, involving a decision to switch to RRH2, TCI state switch command, TCI state switching, PDCCH order DCI, RACH preamble (MSG 1), RACH response (MSG 2), and UL timing adjustment. The process concludes with resuming data transmission.](c5424b117a719524c619938e97c4cb1f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RRH1 + participant RRH2 + + Note right of RRH1: 1: Connected mode, RRH1 + + Note left of UE: Repeat + UE->>RRH1: User Data + UE->>RRH1: 2: RSs (e.g., DM-RS, SRS) + UE->>RRH1: 3: MAC-CE TAC + RRH1-->>UE: 4: TA adjustment + RRH1->>UE: 5: SSB1 + RRH2->>UE: 6: SSB2 + Note left of UE: 7: SSB2 detection and identification + UE->>RRH1: 8: CSI L1-RSRP report + Note left of UE: SSB1 and SSB2 + Note left of UE: 9: Autonomous small TA adjustment (within Tq) + + Note left of UE: UL timing adjustment at TCI state switch. + Note right of RRH1: 10: Decision to switch to RRH2 + RRH1-->>UE: 11: TCI state switch command + Note left of UE: MAC CE + Note left of UE: 12: TCI state switching + RRH2->>UE: 13: PDCCH order DCI + UE->>RRH2: 14: RACH preamble (MSG 1) + RRH2-->>UE: 15: RACH response (MSG 2) + Note left of UE: 16: UL timing adjustment + + Note right of RRH1: Resuming data transmission. + +``` + + v6.3.7 + +Sequence diagram of RA-based UL timing adjustment at TCI state switch. The diagram shows interactions between UE, RRH1, and RRH2. It is divided into two main parts: a 'Repeat' section and a 'UL timing adjustment at TCI state switch' section. The 'Repeat' section includes steps 1-9, involving user data, RSs, MAC-CE TAC, TA adjustment, SSB1, SSB2, SSB2 detection, CSI L1-RSRP report, and autonomous small TA adjustment. The 'UL timing adjustment' section includes steps 10-16, involving a decision to switch to RRH2, TCI state switch command, TCI state switching, PDCCH order DCI, RACH preamble (MSG 1), RACH response (MSG 2), and UL timing adjustment. The process concludes with resuming data transmission. + +Figure 7.2.2.1.1-1: A sequence diagram of RA-based UL timing adjustment at TCI state switch. + +## 7.3 Demodulation performance requirements + +It is feasible to support maximum speed with 350km for uplink with PTRS or DMRS+PTRS configuration used for frequency offset tracking with 120KHz SCS + +Configure PTRS during the PUSCH demodulation test + +DMRS+PTRS configuration for PUSCH demodulation requirement with single-tap channel model + +- Option 1: 1 DMRS +PTRS (L=1,K=2); or +- Option 2: 1+1 DMRS +PTRS (L=1,K=2); or + +- Option 3: 1+1+1 DMRS+PTRS(L=1, K=2). + +Agreed Simulation assumption for PDSCH requirement for FR2 HST are captured in R4-2120704. + +### 7.3.1 UE demodulation requirements + +RAN4 agreed following baseline assumption: No NWA signalling needed to differentiate the Deployment type, Intra/Inter-RRH TCI Switching type from RAN4 demodulation performance requirements perspective if no clear performance benefits identified with such new NWA signalling. + +From demodulation requirements aspect, it is agreed that there is no need to define network assistance signalling to indicate TCI state switching type or deployment type. + +RAN4 agreed not to introduce UE capability for Uni-directional and Bi-directional deployment scenario from UE demodulation aspect. + +No need to define additional signalling to indicate UE supporting of demodulation requirements for FR2 HST, if UE indicates supporting FR2 HST operation with FR2 UE power class PC6 signalling. + +Test Scope of DL requirements: + +- Only define PDSCH demodulation performance requirements in Rel-17 FR HST WI. +- Doppler frequency for PDSCH requirement in Bi-directional deployment scenario, if Bi-directional deployment scenario is introduced: + - Option 1: 9722Hz targeting 350km/h at 30GHz + - Option 2: 7000Hz with the smallest RS range of frequency offset estimation +- the maximum Doppler frequency offset for PDSCH requirement in unidirectional deployment scenario + - 9722 Hz targeting 350km/h at 30 GHz +- RAN4 decided not define PDSCH requirement with HST single-tap channel. +- RAN4 decided to define PDSCH requirement in Bi-directional scenario with Doppler Frequency as 9722Hz. + +Requirement for uni- and bi-directional RRH deployment scenarios: + +- Consider output of FR2 HST Deployment scenarios discussion whether to cover uni- and/or bi-directional RRH deployment. +- No dedicated PDSCH requirement for bidirectional Scenario A +- Introduce PDSCH requirement for unidirectional Scenario A if the feasibility of unidirectional deployment is confirmed +- Introduce PDSCH requirement in unidirectional and bidirectional for Scenario B + +Transmission schemes: + +- No PDSCH requirement with SFN joint transmission scheme in Rel-17 FR2 HST WI. +- DPS transmission schemes in uni-directional RRH deployment scenario. Introduce DPS scheme 1a and scheme 1b for PDSCH requirement in uni-directional scenario if the feasibility of uni-directional deployment is confirmed: + - Option 1: scheme 1a + - Option 2: scheme 1b + - Option 3: both scheme 1a and scheme 1b + +RAN4 define UE demodulation requirements with transmission schemes as Case 1: Uni-directional scenario A with DPS scheme 1b. + +- DPS transmission scheme in bi-directional RRH deployment scenario. Introduce DPS scheme 1a for PDSCH requirement in bi-directional scenario of scenario B: + - Option 1: scheme 1a + - Option 2: scheme 1b + - Option 3: both scheme 1a and scheme 1b + +RAN4 define UE demodulation requirements with transmission schemes as Case 2: Bi-directional scenario B with DPS scheme 1a. + +- Channel Model names for DPS transmission schemes: + - Uni-directional scenario A: HST-DPS-FR2-UNI-A + - Bi-directional scenario B: HST-DPS-FR2-BI-B +- Test applicability rule.: + - Option 1: If UE is capable of more than 1 activated TCI state, UE should pass test both case 1 and case 2, otherwise, UE should only pass test of case 2 + - Option 2: + - If UE is capable of more than 1 activated TCI state, UE should pass test both case 1 and case 2, otherwise, UE should only pass test of case 2 + - If UE passes case 1 (Uni-directional scenario A with DPS scheme 1b), the performance of Uni-directional scenario B with DPS scheme 1b are also guaranteed + +PDSCH requirement for Uni-directional scenario: + +For TCI switching scheduling it is agreed to schedule the active TCI switching for PDSCH demodulation test with the channel model assuming the Uni-directional Scenario A as follows: switch from RRH #(k-1) to RRH #k at the location of $(k-1) \cdot D_s - D_{s\_offset}$ , k=0,1,2,..., illustrated in figure 7.3.1-1 + +![Figure 7.3.1-1: TCI switching for Uni-directional Scenario A. The diagram shows a sequence of RRHs (RRH #0, RRH #1, RRH #2, ..., RRH #k-1, RRH #k, RRH #k+1) along a horizontal axis. The UE is moving from left to right. The distance between adjacent RRHs is D_s. The TCI switching occurs at a location offset from the RRH #k position by D_s_offset. The diagram illustrates the distance from the UE's starting position (at RRH #0) to the switching point for each RRH #k, which is (k-1)*D_s - D_s_offset.](f59dafee4c3bbc563111e5b1b6048c3d_img.jpg) + +The diagram illustrates the TCI switching for Uni-directional Scenario A. A horizontal axis represents the path of the UE, with markers #0, #1, #2, #k-1, #k, and #k+1. Above the axis, RRH #0, RRH #1, RRH #2, ..., RRH #k-1, RRH #k, and RRH #k+1 are shown as rectangles. Diagonal lines represent the coverage areas of the RRHs. A vertical dashed line marks the position of RRH #k. A horizontal double-headed arrow labeled $D_{s\_offset}$ indicates the offset from the RRH #k position. Below the axis, horizontal arrows indicate the distance from the UE's starting position (at RRH #0) to the switching point for each RRH #k: + + +- For RRH #1: $1 \cdot D_s - D_{s\_offset}$ +- For RRH #2: $2 \cdot D_s - D_{s\_offset}$ +- For RRH #k-1: $(k-1) \cdot D_s - D_{s\_offset}$ +- For RRH #k: $k \cdot D_s - D_{s\_offset}$ + +Figure 7.3.1-1: TCI switching for Uni-directional Scenario A. The diagram shows a sequence of RRHs (RRH #0, RRH #1, RRH #2, ..., RRH #k-1, RRH #k, RRH #k+1) along a horizontal axis. The UE is moving from left to right. The distance between adjacent RRHs is D\_s. The TCI switching occurs at a location offset from the RRH #k position by D\_s\_offset. The diagram illustrates the distance from the UE's starting position (at RRH #0) to the switching point for each RRH #k, which is (k-1)\*D\_s - D\_s\_offset. + +**Figure 7.3.1-1: TCI switching for Uni-directional Scenario A** + +The number of RRH and SSB(TRS) per Cell for test RAN4 will use infinite RRHs per Cell, configure the maximum number 4 of SSB and TRS index. Additionally, RAN4 is assuming PDSCH is not scheduled in slots #160n, n=0,1,2. + +Slot for scheduling TCI switching command is slot#57600 n (Assuming UE speed =350km/h, the UE start position (t=0) is the coverage area of the first RRH as following (option1), which is aligned the channel model used for demodulation requirement: + +![Figure 7.3.1-2: TCI switching for Uni-directional Scenario A. The diagram shows a timeline with slots #0, #1, #2, #k-1, #k, #k+1. Above the timeline are RRH #0, RRH #1, RRH #2, ..., RRH #k-1, RRH #k, RRH #k+1. A dashed vertical line at slot #1 marks 'Option 2 Start position'. A double-headed arrow labeled 'D_s_offset' is between slot #0 and the dashed line. Horizontal arrows from the dashed line indicate time intervals: '1*D_s - D_s_offset', '2*D_s - D_s_offset', '(k-1)*D_s - D_s_offset', and 'k*D_s - D_s_offset'. A double-headed arrow labeled '57600 slots' is between the dashed line and slot #k. An arrow labeled 'Option 1 Start position' points to slot #0.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +Figure 7.3.1-2: TCI switching for Uni-directional Scenario A. The diagram shows a timeline with slots #0, #1, #2, #k-1, #k, #k+1. Above the timeline are RRH #0, RRH #1, RRH #2, ..., RRH #k-1, RRH #k, RRH #k+1. A dashed vertical line at slot #1 marks 'Option 2 Start position'. A double-headed arrow labeled 'D\_s\_offset' is between slot #0 and the dashed line. Horizontal arrows from the dashed line indicate time intervals: '1\*D\_s - D\_s\_offset', '2\*D\_s - D\_s\_offset', '(k-1)\*D\_s - D\_s\_offset', and 'k\*D\_s - D\_s\_offset'. A double-headed arrow labeled '57600 slots' is between the dashed line and slot #k. An arrow labeled 'Option 1 Start position' points to slot #0. + +**Figure 7.3.1-2: TCI switching for Uni-directional Scenario A** + +PDSCH allocation time for Uni-directional scenario with DPS scheme 1b: + +RAN4 will not consider the following period after receiving MAC CE active TCI switching from the throughput statistics. RAN4 will use $T_{\text{HARQ}} + T_{\text{MAC proc}}$ as baseline, where: + +- $T_{\text{HARQ}}$ : Number of slots between PDSCH and corresponding HARQ-ACK information, $T_{\text{HARQ}} = 4$ (slots), and +- $T_{\text{MAC proc}}$ : Number of slots for MAC CE processing, $T_{\text{MAC proc}} = 24$ (slots) + +FFS the value of $T_{\text{HARQ}}$ , $T_{\text{MAC proc}}$ . + +PDSCH requirement for Bi-directional scenario: + +For TCI switching scheduling it is agreed to schedule the active TCI switching for PDSCH demodulation test with the channel model assuming the Bi-directional Scenario B as follows: + +- Switch from RRH #(k-1) to RRH #(k+1) at the location of $2k \cdot 1/2 D\_s, k=0,1,2,\dots$ +- Switch from RRH #(k+1) to RRH #k at the location of $2(k+1) \cdot 1/2 D\_s, k=0,1,2,\dots$ + +Illustrated in figure 7.3.1-2: + +![Diagram of TCI switching for Bi-directional Scenario B showing RRHs and slots with timing intervals.](b71190d39f5e641548d0f091e94e663d_img.jpg) + +The diagram illustrates the TCI switching for Bi-directional Scenario B. It shows a sequence of RRHs: RRH #0, RRH #1, RRH #2, RRH #3, ..., RRH #k-1, RRH #k, RRH #k+1. Below the RRHs, a horizontal axis represents slots, labeled with indices: #1, #0, #2, #1, #3, #2, ..., #k, #k-1, #k+1, #k, #k+2. Four horizontal arrows indicate timing intervals starting from the first RRH: + + +- $(2k-1)*0.5D_s$ +- $2k*0.5D_s$ +- $(2k+1)*0.5D_s$ +- $2*(k+1)*0.5D_s$ + +Diagram of TCI switching for Bi-directional Scenario B showing RRHs and slots with timing intervals. + +Figure 7.3.1-3: TCI switching for Bi-directional Scenario B + +For the number of RRH and SSB(TRS) per Cell for test RAN4 will assume infinite RRHs per Cell, configure the maximum number 8 of SSB and TRS index. Additionally, RAN4 will be assuming PDSCH is not scheduled in slots #160n and #160n+1, n=0, 1, 2... + +Slot for scheduling TCI switching command is slot#28800 n (Assuming UE speed =350km/h, the UE start position (t=0) is the closest area of the first RRH as following, which is aligned the channel model used for demodulation requirement: + +![Diagram of TCI switching for Bi-directional Scenario B with a start position at slot 28800.](4310445b53967f25efe7be819014c8ae_img.jpg) + +This diagram is similar to Figure 7.3.1-3 but includes a 'Start position' indicated by an upward arrow at the beginning of the timeline, aligned with a vertical dashed line. The timeline starts at '28800 slots'. The same four timing intervals are shown: + + +- $(2k-1)*0.5D_s$ +- $2k*0.5D_s$ +- $(2k+1)*0.5D_s$ +- $2*(k+1)*0.5D_s$ + +Diagram of TCI switching for Bi-directional Scenario B with a start position at slot 28800. + +Figure 7.3.1-4: TCI switching for Bi-directional Scenario B + +PDSCH allocation time for Bi-directional scenario with DPS scheme 1a + +RAN4 apply the following value for PDSCH allocation timeline for Bi-directional scenario A with DPS scheme 1a: + +- $T_{HARQ} = 4$ (slots) +- $T_{MAC\ proc} = 24$ (slots) + +- $T_{\text{TRProc}} = 16$ (slots) +- $T_{\text{SSBProc}} = 16$ (slots) +- $T_{\text{firstSSB}} = 132$ (slots) +- $T_{\text{firstTRSAterSSB}} = 66$ (slots) + +![Figure 7.3.1-4: PDSCH allocation timeline for Bi-directional scenario B with DPS scheme 1a. The diagram shows a timeline of slots with SSB and TRS transmissions. SSBs are at slots 28800/1, 28860/1, and 28960/1. TRS transmissions are at slots 28802/3, 28882/3, 28962/3, and 29042/3. Processing times are indicated: T_HARQ=4, T_MAC_proc=24, T_firstSSB=132, T_SSB_proc=16, T_firstTRSAterSSB=66, and T_TRS_proc=16. The timeline is divided into 80 (10ms) intervals. PDSCH scheduling is indicated at the end of the timeline.](6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg) + +The diagram illustrates the PDSCH allocation timeline for a bi-directional scenario. The horizontal axis represents slots, with specific slot numbers and subframe indicators (e.g., 28800/1, 28802/3) marking the positions of SSB (Synchronization Signal Block) and TRS (Tracking Reference Signal) transmissions. SSBs are shown at slots 28800/1, 28860/1, and 28960/1. TRS transmissions occur at slots 28802/3, 28882/3, 28962/3, and 29042/3. Various processing and timing intervals are labeled: $T_{\text{HARQ}}=4$ (slots between PDSCH and HARQ-ACK), $T_{\text{MAC\_proc}}=24$ (MAC CE processing), $T_{\text{firstSSB}}=132$ (slots to the first SSB), $T_{\text{SSB\_proc}}=16$ (SSB processing), $T_{\text{firstTRSAterSSB}}=66$ (slots to the first TRS after SSB), and $T_{\text{TRS\_proc}}=16$ (TRS processing). The timeline is segmented into 80 (10ms) intervals. A vertical line marks the start of PDSCH scheduling. + +Figure 7.3.1-4: PDSCH allocation timeline for Bi-directional scenario B with DPS scheme 1a. The diagram shows a timeline of slots with SSB and TRS transmissions. SSBs are at slots 28800/1, 28860/1, and 28960/1. TRS transmissions are at slots 28802/3, 28882/3, 28962/3, and 29042/3. Processing times are indicated: T\_HARQ=4, T\_MAC\_proc=24, T\_firstSSB=132, T\_SSB\_proc=16, T\_firstTRSAterSSB=66, and T\_TRS\_proc=16. The timeline is divided into 80 (10ms) intervals. PDSCH scheduling is indicated at the end of the timeline. + +Figure 7.3.1-4: PDSCH allocation timeline for Bi-directional scenario B with DPS scheme 1a + +RAN4 will not consider the following period after receiving MAC CE active TCI switching from the throughput statistics: + +- $T_{\text{HARQ}} + T_{\text{MAC\_Proc}} + T_{\text{firstSSB}} + T_{\text{SSB\_proc}} + T_{\text{firstTRSAterSSB}} + T_{\text{TRS\_proc}}$ as baseline, where: + - $T_{\text{HARQ}}$ : Number of slots between PDSCH and corresponding HARQ-ACK information + - $T_{\text{MAC\_proc}}$ : Number of slots for MAC CE processing + - $T_{\text{firstSSB}}$ is the number of slots to the first SSB transmission occasion after MAC CE command is decoded by the UE + - $T_{\text{SSB\_proc}}$ is the number of slots for SSB processing + - $T_{\text{firstTRSAterSSB}}$ is the number of slot to the first TRS transmission occasion available after $(T_{\text{firstSSB}} + T_{\text{SSB\_proc}})$ + - $T_{\text{TRS\_proc}}$ is the number of slots for TRS processing + +FFS the value of $T_{\text{HARQ}}$ , $T_{\text{MAC\_Proc}}$ , $T_{\text{firstSSB}}$ , $T_{\text{firstTRSAterSSB}}$ , $T_{\text{TRS\_proc}}$ + +SCS and BW: + +- Option 1: 120KHz with 100MHz; or +- Option 2: 120KHz with 200MHz. + +BW: + +- 200 MHz CBW is defined. + +Regarding the test setup for PDSCH RAN4 has reached following agreements: + +RS configuration: + +- 1) the assumption of RS for frequency offset tracking is up to UE implementation. The RS configuration for PDSCH requirement is FFS and options are: + - a) Configure SSB every 20ms; and + - b) Configure TRS every 10ms; and + - c) Configure PTRS with $K_{\text{PT-RS}}=2$ and $L_{\text{PT-RS}}=1$ . + +- It is agreed to configure SSB transmission period as 20ms and TRS transmission period as 10ms for FR2 HST UE PDSCH demodulation requirement test. Configuration SSB slot offset as 0 as baseline + +DMRS configuration. RAN4 has agreed: + +- 1+1+1 DMRS configuration for DPS scheme. + +UE frequency error: + +- RAN4 agreed not consider extra UE frequency error for demodulation tests in FR2 HST WI. Any impact of UE frequency error can be included in companies' impairment results when RAN4 sets the UE demodulation requirement for FR2 HST. + +PDSCH simulation assumptions: + +Simulation assumptions for results alignment and further requirements definition are summarized in Table 1. + +**Table 7.3.1-1: Simulation assumptions for results alignment and further requirements definition.** + +| Parameter | | | Value | +|--------------------------|---------------------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------| +| Carrier frequency | | | 30 GHz | +| Duplex mode | | | TDD | +| SCS | | | 120 kHz | +| CBW | | | 200 MHz | +| Antenna configuration | | | 2x2 | +| TDD pattern | | | DDDSU, S: 10D + 2G + 2U
Schedule PDSCH in special slots (Note 1) | +| PDSCH DMRS configuration | DMRS type | | Type 1 | +| | Number of additional DMRS | | 2 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | | 1 | +| PDSCH configuration | Mapping type | | Type A | +| | Starting symbol (S) | | 1 | +| | Length (L) | | 13 | +| | PRB bundling size | | 2 | +| | Resource allocation type | | Type 0 | +| | RBG size | | Config2 | +| CSI-RS for tracking | Resource set #1 | First OFDM symbol in the PRB used for CSI-RS | $l_0 = 5$ for CSI-RS resource 1 and 3
$l_0 = 9$ for CSI-RS resource 2 and 4 | +| | | CSI-RS density | 3 | +| | | CSI-RS periodicity | 80 slots for CSI-RS resource 1,2,3,4 | +| | | CSI-RS offset | 2 for CSI-RS resource 1 and 2
3 for CSI-RS resource 3 and 4 | +| | | Frequency occupation | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| | | QCL info | TCI state #2 | +| | Resource set #2 | First OFDM symbol in the PRB used for CSI-RS | $l_0 = 6$ for CSI-RS resource 5 and 7
$l_0 = 10$ for CSI-RS resource 6 and 8 | +| | | CSI-RS density | 3 | +| | | CSI-RS periodicity | 80 slots for CSI-RS resource 5,6,7,8 | +| | | CSI-RS offset | 2 for CSI-RS resource 5 and 6
3 for CSI-RS resource 7 and 8 | +| | | Frequency occupation | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| | | QCL info | TCI state #3 | +| TCI state #0 | Type 1 QCL information | CSI-RS resource | CSI-RS for resource 1 from "CSI-RS for tracking Resource set #1" configuration | +| | | QCL type | Type A | +| | Type 2 QCL information | CSI-RS resource | CSI-RS for resource 1 from "CSI-RS for tracking Resource set #1" configuration | +| | | QCL type | Type D | +| TCI state #1 | Type 1 QCL information | CSI-RS resource | CSI-RS for resource 5 from "CSI-RS for tracking Resource set #2" configuration | +| | | QCL type | Type A | +| | Type 2 QCL information | CSI-RS resource | CSI-RS for resource 5 from "CSI-RS for tracking Resource set #2" configuration | +| | | QCL type | Type D | +| TCI state #2 | Type 1 QCL information | SSB index | SSB #0 | +| | | QCL type | Type C | +| | Type 2 QCL information | SSB index | SSB #0 | +| | | QCL type | Type D | +| TCI state #3 | Type 1 QCL information | SSB index | SSB #1 | +| | | QCL type | Type C | + +| | | | | | | | +|--------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|--|--|--| +| | Type 2 QCL information | SSB index | SSB #1 | | | | +| | | QCL type | Type D | | | | +| PTRS configuration | Frequency density ( $K_{PT-RS}$ ) | | 2 | | | | +| | Time density ( $T_{PT-RS}$ ) | | 1 | | | | +| MCS and Rank | MCS 17 and Rank 2 | | | | | | +| Number of HARQ processes | 8 | | | | | | +| SSB and CSI-RS for tracking assumptions | 2 SSBs associated with 2 CSI-RS resources sets for PDSCH requirement, where SSB # ( $k \bmod 2$ ), CSI-RS (for tracking) resource set # ( $(k \bmod 2) + 1$ ), CSI-RS (for CSI acquisition) resource set # ( $(k \bmod 2) + 3$ ) and CSI-RS (for beam refinement) resource set # ( $(k \bmod 2) + 5$ ) are transmitted by $k^{\text{th}}$ RRH | | | | | | +| SSB periodicity | 20ms | | | | | | +| SSB slot offset | 0 | | | | | | +| Propagation conditions | Uni-directional Scenario A,
Bi-directional Scenario B | | | | | | +| Maximum Doppler shift | 9722 | | | | | | +| Test metric | SNR at 70% of maximum throughput | | | | | | +| NOTE 1: For further study | | | | | | | +| NOTE 2: Other remaining parameters can be found in TS 38.101-4 Table 7.2-1 and Table 7.2.2.2.1-2 | | | | | | | + +CSI-RS/TRS configuration: + +RAN4 will use TRS configuration for TRS resource set 2 with $l_0 = 4/8$ + +NZP CSI-RS resources configuration: + +In the test, configure NZP CSI-RS resources for CSI acquisition for all the TCI states so that the target TCI state is known at the active TCI switching. + +UE demodulation test: + +For Test cases definition and test applicability rule RAN4 will define UE demodulation requirements with transmission schemes with test applicable rule as: + +- 1) Case 1: Uni-directional scenario A with DPS scheme 1b. +- 2) Case 2: Bi-directional scenario B with DPS scheme 1a. +- 3) Test applicable rule + - a) If UE is capable of more than 1 activated TCI state, UE should pass test both case 1 and case 2, otherwise, UE should only pass test of case 2 +- 4) It is RAN4 common understanding that if UE passes case 1 (Uni-directional scenario A with DPS scheme 1b), the performance of Uni-directional scenario B with DPS scheme 1b are also guaranteed. + +Test setup for PDSCH allocation timeline for Uni-directional scenario: + +- 1) Step 1: Two RRHs of RRH#(2k), RRH#(2k+1) are assumed, and SSB#(2k mod 4) and SSB#((2k+1) mod 4) are transmitted for each TRPs, separately, where $k = 0, 1, 2, \dots$ + - a) UE is configured with TCI#(2k mod 4) and TCI#((2k+1) mod 4) that are associated with TRS #(2k mod 4) and TRS#((2k+1) mod 4) transmitted from RRH#(2k) and RRH#(2k+1) respectively by RRC signalling `tci-StatesToAddModList` in the `PDSCH-Config` and `tci-PresentInDCI` is not configured; + - b) All the configured TCI states are known to UE. UE is configured with NZP-CSI-RS resource for L1-RSRP measurements by RRC signalling `nzp-CSI-RS-ResourceSet` within the `CSI-ResourceConfig` and periodic CSI reporting by setting `reportConfigType` to periodic and `reportQuantity` to `cri-RSRP` (Note: reported L1-RSRP measurements are not tested) +- 2) Step 2: UE activates TCI #0 for PDCCH by “TCI State Indication for UE-specific PDCCH MAC CE”; +- 3) Step 3: PDSCH associated with TCI #0 is transmitted during the slots from 0 to $[n + T_{\text{HARQ}} + T_{\text{MAC}}]$ + +- 4) Step 4 : In slot $n$ TE start triggering TCI state switching command to TCI #1 by “TCI State Indication for UE-specific PDCCH MAC CE with MCS 4”; +- 5) Step 5: PDSCH associated with TCI #1 is transmitted in slots from $n+1 + T_{\text{HARQ}} + T_{\text{MAC}}$ to $[N]$ . +- 6) PDSCH associated with TCI#( $k \bmod 4$ ) ( $k=1$ ) is transmitted in slot from 0 to $[n + T_{\text{HARQ}} + T_{\text{MAC}}]$ +- 7) PDSCH associated with TCI #( $k \bmod 4$ ) ( $k=2, 3, \dots$ ) is transmitted in slot from $[(k-1)*n+1 + T_{\text{HARQ}} + T_{\text{MAC}}]$ to $[(k*n+1 + T_{\text{HARQ}} + T_{\text{MAC}}]$ , where $n=57600$ is the number of slots between the location of $(k-1)D_s - DS\_offset$ and the location of $(k)D_s - DS\_offset$ . And $k$ is the RRH number in the channel model. +- 8) PDCCH and PDSCH are DTXed in other slots in which throughput statistics are not considered +- 9) The output of RRM discussion regarding FR2 HST TCI state switching delay can be considered to PDSCH requirement test setup. + +Test setup for PDSCH allocation timeline for Bi-directional scenario: + +- 1) Step 1: Three RRHs of RRH#( $k-1$ ), RRH#( $k$ ), RRH#( $k+1$ ) are assumed, and SSB#( $(2(k-1)+1)\bmod 8$ ), SSB#( $(2k+1)\bmod 8$ ), and SSB#( $(2(k+1)+1)\bmod 8$ ) are transmitted from each TRPs, separately, where $k$ is the RRH number with $k=1,2,3,\dots$ , $l$ is the SSB index with $l=0,1$ + - a) UE is configured with TCI#( $(2(k-1)+1) \bmod 8$ ) ( $l=0,1$ ), TCI#( $(2k+1) \bmod 8$ ) ( $l=0,1$ ) and TCI#( $(2(k+1)+1) \bmod 8$ ) ( $l=0,1$ ) transmitted from RRH#( $k-1$ ), RRH#( $k$ ) and RRH#( $k+1$ ) respectively by RRC signalling tci-StatesToAddModList in the PDSCH-Config and tci-PresentInDCI is not configured; + - b) All the configured TCI states are known to UE. UE is configured with NZP-CSI-RS resource for L1-RSRP measurements by RRC signalling nzp-CSI-RS-ResourceSet within the CSI-ResourceConfig and periodic CSI reporting by setting reportConfigType to periodic and reportQuantity to cri-RSRP (Note: reported L1-RSRP measurements are not tested) +- 2) Step 2: TE activates TCI #2 for PDCCH by “TCI State Indication for UE-specific PDCCH MAC CE”; +- 3) Step 3: PDSCH associated with TCI #2 is transmitted during the slots from 0 to $[n + T_{\text{HARQ}} + T_{\text{MAC proc}}]$ ; +- 4) Step 4: In slot $n$ TE start triggering TCI state switching command to TCI #1 by “TCI State Indication for UE-specific PDCCH MAC CE with MCS 4”; +- 5) Step 5: PDSCH associated with TCI #1 is transmitted in slots from $n+1 + T_{\text{HARQ}} + T_{\text{MAC proc}} + T_{\text{firstSSB}} + T_{\text{SSB proc}} + T_{\text{firstTRSAfterSSB}} + T_{\text{TRS proc}}$ to $[2n+ T_{\text{HARQ}} + T_{\text{MAC proc}}]$ +- 6) Step 6: In slot $2n$ TE start triggering TCI state switching command to TCI# 4 by “TCI State Indication for UE-specific PDCCH MAC CE with MCS 4” +- 7) Step 7: PDSCH associated with TCI #4 is transmitted in slots from $[2n+1 + T_{\text{HARQ}} + T_{\text{MAC proc}} + T_{\text{firstSSB}} + T_{\text{SSB proc}} + T_{\text{firstTRSAfterSSB}} + T_{\text{TRS proc}}]$ to $[3n+T_{\text{HARQ}} + T_{\text{MAC proc}}]$ ; +- 8) PDSCH associated with TCI#( $2k \bmod 8$ ) ( $k=1$ ) is transmitted in slot from 0 to $[n+ T_{\text{HARQ}} + T_{\text{MAC proc}}]$ +- 9) PDSCH associated with TCI #( $2k \bmod 8$ ) ( $k=2,3, \dots$ ) is transmitted in slot from $[(2k-2)n + 1 + T_{\text{HARQ}} + T_{\text{MAC proc}} + T_{\text{firstSSB}} + T_{\text{SSB proc}} + T_{\text{firstTRSAfterSSB}} + T_{\text{TRS proc}}]$ to $[(2k-1)n + T_{\text{HARQ}} + T_{\text{MAC proc}}]$ +- 10) PDSCH associated with TCI #( $(2k+1)\bmod 8$ ) ( $k=0,1,2,\dots$ ) is transmitted in slot from $[(2k+1)n + 1 + T_{\text{HARQ}} + T_{\text{MAC proc}} + T_{\text{firstSSB}} + T_{\text{SSB proc}} + T_{\text{firstTRSAfterSSB}} + T_{\text{TRS proc}}]$ to $[(2(k+1)n + T_{\text{HARQ}} + T_{\text{MAC proc}})$ where $n=28800$ slots is the half of the number of slots between two RRHs. +- 11) PDCCH and PDSCH are DTXed in other slots in which throughput statistic are not considered +- 12) The output of RRM discussion regarding FR2 HST TCI state switching time line can be considered to PDSCH requirement test setup + +### 7.3.2 BS demodulation requirements + +Define manufacturer declaration, applicable to BS Type 2-O, for PUSCH additional DM-RS in FR2 HST scenario. The intention is that all combinations of pos0, pos1, and pos2 should be possible to declare. Exact wording is FFS. + +FR2 HST PUSCH requirement test shall apply only for the additional DM-RS position declared to be supported. If more than one DMRS configuration is declared to be supported, the test shall be done for the minimum number of DMRS supported. + +RAN4 will adopt the following manufacturer declaration for different additional DM-RS position support for FR2 HST: + +- Additional DM-RS position for FR2 high speed train: Declaration of supported additional DM-RS position(s) for FR2 high speed train scenario for PUSCH and UL timing adjustment, i.e., pos0, pos1, pos2, or any combination. + +Test scope of UL requirements. RAN4 will only define the following BS demodulation performance requirements in Rel-17 FR HST WI + +- PUSCH + - 1) RAN4 agreed to introduce PUSCH requirement with Doppler frequency as 19444Hz targeting 350km/h at 30GHz. + - 2) Additionally, RAN4 has agreed not introduce PUSCH requirement with Doppler frequency as 14444Hz targeting 260km/h at 30GHz, if no issue with supporting 350km/h was identified. + - 3) No dedicated PUSCH requirement for bidirectional Scenario A + - 4) Introduce PUSCH requirement for unidirectional and bidirectional Scenario B + - 5) Introduce PUSCH requirement in Uni-directional for Scenario A if the feasibility of Uni-directional deployment is confirmed. + - 6) Define only one set of requirements for PUSCH. + - 7) Define HST FR2 model based on Bi-directional scenario-B model. + - 8) No test applicability rules are needed. +- UL timing adjustment + - 1) PRACH + +Test Setup for PUSCH requirements: + +- 1) Waveform: + - a) Only CP-OFDM. +- 2) SCS&BW: + - a) Option 1: 120KHz SCS with 50MHz, 100MHz or 200MHz; and + - b) Option 2: 120KHz SCS with 100MHz; and + - c) Option 3: 120KHz SCS with 200MHz. +- 3) Antenna Configuration: + - 1) 1Tx2Rx Low. + +- 4) Resource mapping type: type B. + +- 5) Length of data symbol: + +The length of PUSCH data symbol is 10. + +- 6) MCS: + +- a) Only MCS19. + +RAN4 agreed to define PUSCH requirements with MCS(s) between MCS16-20 that is/are feasible and testable. + +It was agreed to assume a receiver with post FFT FOC. + +- 7) RS configuration: + +- a) Option 1: 1 DMRS + PTRS (L=1,K=2); and +- b) Option 2: 2 DMRS+ PTRS (L=1,K=2); and +- c) Option 3: 3 DMRS + PTRS (L=1,K=2) with Option 3a: If companies have strong concern about DMRS 1+1, create an applicability rule that only one DMRS configuration shall be tested by manufacture declaration. + +RAN4 agreed following: + +- a) Define requirement with 1 DMRS + PT\_RS (L=1, K=2) configuration + - Define FRC for 1 DMRS + PT\_RS (L=1, K=2) +- b) Define requirement based on the simulation results with 2 DMRS+ PT\_RS (L=1, K=2) configuration, but the final requirements are applicable for both 2 DMRS+ PT\_RS (L=1, K=2) and 3 DMRS + PT\_RS (L=1, K=2) + - Define FRC for 2 DMRS + PT\_RS (L=1, K=2) + - Define FRC for 3 DMRS + PT\_RS (L=1, K=2) + +- 8) CBW: + +Both 50MHz and 200MHz CBWs are defined with the test applicability rule that only one of them is tested based on BS manufacturer. + +- 9) Phase noise model: + +- a) No explicit phase noise modelling in the alignment results +- b) Realistic phase noise modelling is left up to the contributing entities +- c) The phase noise impact can be included in the impairment results, but it is left up to companies + +RAN4 agreed no explicit phase noise modelling in the alignment result. Phase noise impact can be included in the impairment results, but it is left up to companies. + +- 10) With regard to the test metric for PUSCH requirements, only 70% of the throughput is used + +**Table 7.3.2.1 Simulation assumption for PUSCH requirement** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------|-------------------------------------------|------------------------------------------------------------------------------------------------------------| +| Channel Model | | Uni-directional scenario A and B
Bi-directional scenario B
The details can be referred as R4-2115725 | +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 120kHz SCS:
3D1S1U, S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS symbols | Pos0, Pos1 and Pos2 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | {0} | +| | DM-RS sequence generation | NID=0, nSCID =0 | +| Time domain resource | PUSCH mapping type | B | +| | Start symbol index | 0 | +| | Allocation length | 10 | +| Frequency domain resource | RB assignment | 50MHz and 200MHz | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS configuration | Frequency density (KPT-RS) | 2 | +| | Time density (LPT-RS) | 1 | +| NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns | | | + +Test Setup for UL timing adjustment requirement: + +It was agreed to introduce UL timing adjustment requirements for FR2 HST. For test applicability it was agreed to share the same applicability rule with PUSCH. Additionally, it was agreed the manufacturer declaration on HST FR2 DM-RS support – UL TA – to share the same manufacturer declaration with PUSCH. + +1) Waveform: + +a) Only CP-OFDM. + +2) CBW: align CBW for UL timing adjustment and PUCH requirements. 50MHz and 200MHz CBWs are defined with the test applicability rule that only one of them is tested based on BS manufacturer. The existing PUSCH applicability rule for different channel bandwidth for UL timing adjustment requirements are: + +- For each subcarrier spacing declared to be supported, the test requirements for a specific channel bandwidth shall apply only if the BS supports it. +- Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement for the closest channel bandwidth lower than this widest supported bandwidth; the tested PRBs shall then be centered in this widest supported channel bandwidth. + +3) PUSCH resource allocation: + +- 50MHz CBW: 16RBs for each UE, Moving UE RBs: 0~15; Stationary UE RBs: 16~31 +- 200MHz CBW: 66RBs for each UE, Moving UE RBs: 0~65; Stationary UE RBs: 66~131 + +4) RS configuration: + +- a) Align RS configuration for UL timing adjustment requirement and PUSCH requirement + +RAN4 agreed following: + +- a) Define requirement with 1 DMRS + PT\_RS (L=1, K=2) configuration + - Define FRC for 1 DMRS + PT\_RS (L=1, K=2) +- b) Define requirement based on the simulation results with 2 DMRS+ PT\_RS (L=1, K=2) configuration, but the final requirements are applicable for both 2 DMRS+ PT\_RS (L=1, K=2) and 3 DMRS + PT\_RS (L=1, K=2) + - Define FRC for 2 DMRS + PT\_RS (L=1, K=2) + - Define FRC for 3 DMRS + PT\_RS (L=1, K=2) + +#### 5) PUSCH mapping type: + +- a) Type B. + +#### 6) Length of PUSCH allocation. Align with PUSCH for UL timing adjustment: + +- a) Option 1: 10; and +- b) Option 2: 9. + +#### 7) MSC, Align with PUSCH for UL timing adjustment: + +- a) Only MCS16 is used. + +#### 8) SRS bandwidth configuration: + +- a) 50MHz CBW (32RBs)~C\_SRS =9, B\_SRS =0 +- b) 200MHz CBW (132RBs)~ C\_SRS=33, B\_SRS=0 + +#### 9) SRS Transmission comb: $K_{TC}=2$ . SRS transmission in UL timing adjustment requirement is optional + +#### 10) SRS Transmission periodicity : $K_{SRS}=10$ . + +#### 11) Slots in which sounding RS is transmitted: + +- a) The last symbol in slot#3 in radio frames for 120KHz SCS. + +It was agreed that the SRS transmission location is the last symbol in slot#3 in radio frame with TDD pattern as DDDSU, S=10:2:2 + +#### 12) Test Parameters for timing offset: + +- a) Option 1: A: 1.25 us and $\Delta w$ : 1.04 s-1 corresponding to 120KHz SCS for HST FR2 UL timing adjustment requirements; and +- b) Option 2: FFS on A =2.5 us; and +- c) Other options are not precluded + +RAN4 agreed to use Option 1. + +#### 13) Test different between moving UE and stationary UE: + +- a) Option 1: $[\Delta t - (TA-31) \times 16 \times 8T_c]$ . Note: The timing different can be updated with taken into account the output of possible enhancements for timing adjustment command discussion in RRM session + +RAN4 agreed to apply the timing difference between moving UE and stationary UE as $\Delta \tau - (TA-31) \times 16 \times 8T_c$ for UL timing adjustment requirement + +- 14) The length of PUSCH data is 10 +- 15) Test Scenario: + - a) Scenario Y. +- 16) Simulation Assumption for scenario Y: + - a) Option 1. + +**Table 7.3.2.2 Simulation assumption for UL timing adjustment requirement** + +| Parameter | Value | +|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Channel Model | Follow same approach as existing PUSCH UL timing adjustment requirement demodulation requirement specified in TS 38.104 | +| UE Speed | 350 km/h | +| Waveform | CP-OFDM | +| CP Length | Normal | +| A | 1.25 $\mu$ s | +| $\Delta\omega$ | 1T2R | +| MCS | 16 | +| CBW | 50MHz and 200MHz | +| DM-RS type | Type 1 | +| Mapping type | B | +| Length of PUSCH data | 10 | +| RS configuration | 1DMRS+PT-RS(L=1,K=2)
2DMRS+PT-RS(L=1,K=2)
3DMRS+PT-RS(L=1,K=2) | +| Number of DM-RS CDM group(s) without data | 2 | +| Ratio of PUSCH EPRE to DM-RS EPRE | -3dB | +| DM-RS port | {0} | +| DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ for moving UE
$N_{ID}^0=1, n_{SCID}=1$ for stationary UE | +| PUSCH resource allocation | 50MHz: 0 to 15 RB for moving UE, 16 to 31 for stationary UE (if 100MHz)
200MHz: 0 to 65RB for moving UE, 66 to 131 for stationary UE | +| SRS resource allocation | 50MHz CBW (32RBs)~C_SRS =9, B_SRS =0
200MHz CBW (132RBs)~ C_SRS=33, B_SRS=0 | + +FRC for FR2 HST PUSCH UL timing adjustment with different RS configuration as following: + +**Table 7.3.2.3 FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos0 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR2-Ax-xx | G-FR2-Ax-xx | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | +| Modulation | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | +| Payload size (bits) | 4480 | 18432 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 4504 | 6176 | +| Total number of bits per slot with PT-RS (Note 3) | 6624 | 27324 | +| Total symbols per slot with PT-RS | 1656 | 6831 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos0, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [5]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table 7.3.2.4 FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR2-Ax-xx | G-FR2-Ax-xx | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | +| Payload size (bits) | 2976 | 16392 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 2 | +| Code block size including CRC (bits) (Note 2) | 2992 | 8232 | +| Total number of bits per slot with PT-RS (Note 3) | 5888 | 24288 | +| Total symbols per slot | 1472 | 6072 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos1, $l_0 = 0$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [5]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table 7.3.2.5 FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos2 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR2-Ax-xx | G-FR2-Ax-xx | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 7 | 7 | +| Modulation | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | +| Payload size (bits) | 3496 | 14344 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 2 | +| Code block size including CRC (bits) (Note 2) | 3512 | 7208 | +| Total number of bits per slot with PT-RS (Note 3) | 5152 | 21252 | +| Total symbols per slot | 1288 | 5313 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos0, $l_0 = 0$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [5]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +Test setup for PRACH: + +##### 1) PRACH format: + +- only C2; +- Channel +- AWGN + +##### 2) Frequency offset: + +- a) 19444Hz with 350km/h at 30GHz carrier frequency. + +#### 3) Test Preamble Configuration for Ncs. RAN4 agreed to use option 1 as baseline.: + +- a) Ncs=0 + +#### 4) Timing offset configuration: + +- a) Option 1: Reuse Rel-15 FR2 timing offset configuration for PRACH, i.e., 0.8us; and +- b) Option 2: Update the timing offset configuration based on the largest expected cell radius, i.e., derived from scenario B. Note: + - Scenario A ( $D_s=700\text{m}$ , $D_{min}=10\text{m}$ ), cell radius = 700m + - Scenario B ( $D_s=700\text{m}$ , $D_{min}=150\text{ms}$ ), cell radius = 716ms + +RAN4 decided to use one timing offset configuration. Configure the maximum timing offset (i.e., the end of the tested range) in FR2 HST testing setup equal to 4.8us: + +- Value of Timing offset: 0 +- Step of Timing offset increase: 0.48us + +#### 5) Timing error tolerance: + +- a) 0.07us for AWGN, as a default value for 120KHz SCS. + +**Table 7.3.2.3 Simulation assumption for PRACH requirement** + +| Parameters | Value | +|------------------------|--------------------------------| +| Ncs | 0 | +| Logical sequence index | 0 | +| v | 0 | +| Channel | AWGN | +| Antenna configuration | 1T2R | +| SCS | 120KHz | +| Frequency offset | 19444Hz | +| Time error tolerance | 0.07us | +| Timing offset | 4.8us with TO range 0:0.48:4.8 | + +### Requirement selection: + +Apply standard requirement selection to (post-FFT) results with outlier selection, as in Rel-15 [R4-1904713] [R4-19004714]. Choose ideal result alignment threshold as [2.5dB], and impairment threshold as [4dB]. + +# --- 8 Conclusion + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------------|------------|----|-----|-----|------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2021-04 | RAN4#98 | R4-2103240 | | | | Way forward on Deployment Scenario and UE RF Requirement for FR2 HST | | 0.0.1 | +| 2021-05 | RAN4#98bis | R4-2105794 | | | | WF on FR2 HST RRM requirements | | 0.0.1 | +| 2021-05 | RAN4#98bis | R4-2106100 | | | | WF on FR2 HST Deployment Scenario Analysis | | 0.0.1 | +| 2021-05 | RAN4#98bis | R4-2106101 | | | | Way Forward on Channel Modeling for FR2 HST | | 0.0.1 | +| 2021-05 | RAN4#98bis | R4-2106102 | | | | WF on Demodulation requirement for FR2 HST | | 0.0.1 | +| 2021-08 | RAN4#99 | R4-2107861 | | | | WF on UE RF requirement for FR2 HST | | 0.1.0 | +| 2021-08 | RAN4#99 | R4-2108660 | | | | WF on FR2 HST Deployment Scenario Analysis | | 0.1.0 | +| 2021-08 | RAN4#99 | R4-2108661 | | | | WF on Channel Modeling for FR2 HST | | 0.1.0 | +| 2021-08 | RAN4#99 | R4-2108637 | | | | WF for FR2 HST Demodulation | | 0.1.0 | +| 2021-08 | RAN4#99 | R4-2108342 | | | | WF on FR2 HST RRM requirements | | 0.1.0 | +| 2021-08 | RAN4#99 | R4-2105025 | | | | Channel modeling for FR2 HST and TP to TR 38.854 | | 0.1.0 | +| 2021-11 | RAN4#100 | R4-2114976 | | | | WF on UE RF requirement for FR2 HST | | 0.1.0 | +| 2021-11 | RAN4#100 | R4-2115725 | | | | WF on Remaining issues on FR2 HST deployment scenario and channel modeling | | 0.1.0 | +| 2021-11 | RAN4#100 | R4-2115726 | | | | WF for FR2 HST Demodulation | | 0.1.0 | +| 2021-11 | RAN4#100 | R4-2115334 | | | | WF on FR2 HST RRM requirements (part 1) | | 0.1.0 | +| 2021-11 | RAN4#100 | R4-2115335 | | | | WF on FR2 HST RRM requirements (part 2) | | 0.1.0 | +| 2021-11 | RAN4#100 | R4-2115809 | | | | TP to TR 38.854 – beam dwelling time for FR2 HST | | 0.1.0 | +| 2022-01 | RAN4#101 | R4-2120066 | | | | WF on FR2 HST UE requirements | | 0.2.0 | +| 2022-01 | RAN4#101 | R4-2120701 | | | | TP to TR 38.854 on Deployment Scenario Analysis for FR2 HST | | 0.2.0 | +| 2022-01 | RAN4#101 | R4-2120775 | | | | WF on general and UE demodulation requirement for FR2 HST | | 0.2.0 | +| 2022-01 | RAN4#101 | R4-2120703 | | | | WF on BS demodulation requirement for FR2 HST | | 0.2.0 | +| 2022-01 | RAN4#101 | R4-2120704 | | | | Simulation assumption for PDSCH requirement for FR2 HST | | 0.2.0 | +| 2022-01 | RAN4#101 | R4-2120292 | | | | WF on FR2 HST RRM requirements (part 1) | | 0.2.0 | +| 2022-01 | RAN4#101 | R4-2120416 | | | | WF on FR2 HST RRM requirements (part 2) | | 0.2.0 | +| 2022-01 | RAN4#101bis | R4-2202594 | | | | WF on FR2 HST RRM requirements (part 1) | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2202767 | | | | WF on uplink timing for FR2 HST | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2201847 | | | | TP to TR 38.854 on Mobility Performance in HST FR2 Deployment Scenarios | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2201848 | | | | TP to TR 38.854 on the Number of Rx beams | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2202270 | | | | WF on UE RF requirement for FR2 HST | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2203088 | | | | TP to TR 38.854 on Deployment Scenario Analysis for FR2 HST | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2203089 | | | | TP to TR 38.854: Coverage analysis | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2203093 | | | | WF on UE demodulation requirement for FR2 HST | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2203094 | | | | Simulation assumption for PDSCH requirement for FR2 HST | | 0.3.0 | +| 2022-01 | RAN4#101bis | R4-2203006 | | | | WF on BS demodulation requirement for FR2 HST | | 0.3.0 | +| 2022-03 | RAN4#102 | R4-2206520 | | | | WF on remaining issues for FR2 PC6 for HST Scenarios | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2206848 | | | | WF on FR2 HST RRM (part 1) | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2207230 | | | | WF on UE demodulation requirement for FR2 HST | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2207235 | | | | WF on BS demodulation requirement for FR2 HST | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2205896 | | | | TP to TR 38.854 – beam coverage for FR2 HST | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2205960 | | | | TP to TR 38.854 on Legacy RRM Requirement Mobility Performance in HST FR2 Deployment Scenarios | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2205961 | | | | TP to TR 38.854 on Analysis of Mobility Performance in HST FR2 Deployment Scenarios | | 0.4.0 | +| 2022-03 | RAN4#102 | R4-2206849 | | | | TP to TR 38.854 on the Number of Rx beams | | 0.4.0 | +| 2022-03 | RAN#95 | RP-220425 | | | | TR for 1 step approval | | 1.0.0 | +| 2022-03 | RAN#95 | RP-220918 | | | | TR for 1-step approval (with editorial changes to comply with TR rules) | | 1.0.1 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|---------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-06 | RAN#96 | RP-221681 | 0001 | | F | CR to TR 38.854 on Bi-directional Scenario-A Mobility Performance | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0002 | | F | CR to TR 38.854 on Throughput Performance in HST FR2 Scenarios | 17.1.0 | +| 2022-06 | RAN#96 | RP-221681 | 0003 | 1 | F | CR to TR 38.854 on HST FR2 RA-Based Timing Adjustment | 17.1.0 | +| 2023-06 | RAN#100 | RP-231354 | 0004 | | F | CR to TR 38.854 on HST FR2 RA-Based Timing Adjustment | 17.2.0 | +| 2023-06 | RAN#100 | RP-231354 | 0005 | | F | CR to TR 38.854 on Throughput Performance in HST FR2 Scenarios | 17.2.0 | +| 2023-09 | RAN#101 | RP-232491 | 0006 | 1 | F | [NR_HST_FR2] CR to TR 38.854 Rel-17 on UL timing adjustment in between TA | 17.3.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|-------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-09 | RAN#101 | RP-232515 | 0008 | | B | CR to TR 38.854 on HST-FR2 Enhanced Tunnel Deployment | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38863/0359ec7c5451731a6096ae08ce715586_img.jpg b/marked/Rel-18/38_series/38863/0359ec7c5451731a6096ae08ce715586_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c678d1cb30009278914f35e96617447eb2423dc0 --- /dev/null +++ b/marked/Rel-18/38_series/38863/0359ec7c5451731a6096ae08ce715586_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1db4466bfbec9d6ed102964f04e924e844d952b4a0eabaa9317c6b0315cb3ea4 +size 41235 diff --git a/marked/Rel-18/38_series/38863/0668098f95df8ed3c74c0cb82619c140_img.jpg b/marked/Rel-18/38_series/38863/0668098f95df8ed3c74c0cb82619c140_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff20c7167a5dda729b728e4f6af9c40d49a54d85 --- /dev/null +++ b/marked/Rel-18/38_series/38863/0668098f95df8ed3c74c0cb82619c140_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3a3e15aead39df1356141567413ba4db22b5c22b28533983c7bbb6459ae97ba +size 34476 diff --git a/marked/Rel-18/38_series/38863/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg b/marked/Rel-18/38_series/38863/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da9bcfa13889b7d598e2578d5c6dd88f84708c0 --- /dev/null +++ b/marked/Rel-18/38_series/38863/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d959fda60765af45ce60cbb1cfa40acbf1e6deb62b293e477bf9f26dbab0c69 +size 53257 diff --git a/marked/Rel-18/38_series/38863/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-18/38_series/38863/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b0eb186b8df04b1b6c91d6e1cea88e9cde93e7d --- /dev/null +++ b/marked/Rel-18/38_series/38863/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a130a29aa61b52a8063415935b96f9d645467a83a4e4d05c3cf23687a87b4e25 +size 38631 diff --git a/marked/Rel-18/38_series/38863/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg b/marked/Rel-18/38_series/38863/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c896a55bfa7412dec8f4659eda67d240b860ef9 --- /dev/null +++ b/marked/Rel-18/38_series/38863/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:408dd2fc08831261f3f9d755e676d711739d2d679bb1c6c2cbec0b392686037d +size 54022 diff --git a/marked/Rel-18/38_series/38863/179c2b96202f20634ec21def17c1cd86_img.jpg b/marked/Rel-18/38_series/38863/179c2b96202f20634ec21def17c1cd86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81dcc896e15379cac1ad4b6a740f7105f1e42d08 --- /dev/null +++ b/marked/Rel-18/38_series/38863/179c2b96202f20634ec21def17c1cd86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:579ff1bd3ac94970a8a77066bbe26c62e440ebae43a858f270129067ca16acbe +size 31622 diff --git a/marked/Rel-18/38_series/38863/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg b/marked/Rel-18/38_series/38863/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b7a3b6da1271f7955b12dc4dcd4615926788f1e --- /dev/null +++ b/marked/Rel-18/38_series/38863/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f74490db710c8ef7e6fd0d85d1029bf95c490e83350ab912d8f47155c405823c +size 31314 diff --git a/marked/Rel-18/38_series/38863/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-18/38_series/38863/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0bc2dce56546bc147ebfe2a48ca012be0a4e234 --- /dev/null +++ b/marked/Rel-18/38_series/38863/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4211397a3ab3b5240c87cec6fc65420fd0761af06cb08fafa0a9770a2818e3b0 +size 48314 diff --git a/marked/Rel-18/38_series/38863/2031413999bae2fee78687b844944be6_img.jpg b/marked/Rel-18/38_series/38863/2031413999bae2fee78687b844944be6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c4376e1e68f7a52fb252632acbd41b5610efa84 --- /dev/null +++ b/marked/Rel-18/38_series/38863/2031413999bae2fee78687b844944be6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d7c1afab78219d62d315dd7d05db0cd41eab99dfb20631dee029a61387c9ca8 +size 39584 diff --git a/marked/Rel-18/38_series/38863/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-18/38_series/38863/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..491f6618eb3eaf5706712814028ff770ad926b01 --- /dev/null +++ b/marked/Rel-18/38_series/38863/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ea8aa1d384b81fe20bf5aa615972809b0e599eaf70534849561536b8625d995 +size 48512 diff --git a/marked/Rel-18/38_series/38863/37a96d647a34d2c514364514c7f85f41_img.jpg b/marked/Rel-18/38_series/38863/37a96d647a34d2c514364514c7f85f41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e84ca7993945f422f4cb1dba01e47ba214ab695 --- /dev/null +++ b/marked/Rel-18/38_series/38863/37a96d647a34d2c514364514c7f85f41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:545a21f9cd9abe02dc603e61050ff700af948ffc06a789f401c728726efa2f20 +size 37853 diff --git a/marked/Rel-18/38_series/38863/3881b390d52f27a35faedfc170916c86_img.jpg b/marked/Rel-18/38_series/38863/3881b390d52f27a35faedfc170916c86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fee41d0ab7567cec5ce220e157f77f56307327d3 --- /dev/null +++ b/marked/Rel-18/38_series/38863/3881b390d52f27a35faedfc170916c86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac375015e91b5bfa11db0f8aca48b9a311d55104916f519a27cbd92a205db5f0 +size 48079 diff --git a/marked/Rel-18/38_series/38863/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-18/38_series/38863/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c06f4b360f9f78c2e140cc5a9109a8547886024b --- /dev/null +++ b/marked/Rel-18/38_series/38863/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53aaa25788c1bdbc529cec90b37c8843b2519259272f76a897db0cace9979338 +size 41981 diff --git a/marked/Rel-18/38_series/38863/41cd1b0cca77430b41ab28d088e82259_img.jpg b/marked/Rel-18/38_series/38863/41cd1b0cca77430b41ab28d088e82259_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fddf3eda490d4d0c24b0112c1340e5ee2f28785 --- /dev/null +++ b/marked/Rel-18/38_series/38863/41cd1b0cca77430b41ab28d088e82259_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f84c2c60bd84e4aca5169968e37119dc5aec6abdfa1fc08132ddeff66fef2831 +size 90266 diff --git a/marked/Rel-18/38_series/38863/4412857e90dfaa9a3df8836bcbde534b_img.jpg b/marked/Rel-18/38_series/38863/4412857e90dfaa9a3df8836bcbde534b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2db79a9b956edc9091c7e0b424c036d88026ba2c --- /dev/null +++ b/marked/Rel-18/38_series/38863/4412857e90dfaa9a3df8836bcbde534b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b6a429bb7a583289b8de0a5794ab29b3906db42794cf182fab501a819449fdb +size 65561 diff --git a/marked/Rel-18/38_series/38863/449d2799e97657d8fa5897b2e74a88bd_img.jpg b/marked/Rel-18/38_series/38863/449d2799e97657d8fa5897b2e74a88bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d23e88b955203d3a88e19a2ef86aff4b04555b94 --- /dev/null +++ b/marked/Rel-18/38_series/38863/449d2799e97657d8fa5897b2e74a88bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9df7a549c77464e5725d4be2209ef5d3865f3588320c504e71e43d11c15d737f +size 44301 diff --git a/marked/Rel-18/38_series/38863/455c842681aadb4969bd61d71f556744_img.jpg b/marked/Rel-18/38_series/38863/455c842681aadb4969bd61d71f556744_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7c0c0d178b16ac77307aaafd0bcd49cd94502ec --- /dev/null +++ b/marked/Rel-18/38_series/38863/455c842681aadb4969bd61d71f556744_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2feafa28a02cc581cce0981a3fa31081ed5708b6d2dafd0a0230a34d9a50ebc +size 36342 diff --git a/marked/Rel-18/38_series/38863/47e75dc9e83054b2dac3df8bf3e57019_img.jpg b/marked/Rel-18/38_series/38863/47e75dc9e83054b2dac3df8bf3e57019_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..add9c71c016e5a18d220440f336c03c03cecbefb --- /dev/null +++ b/marked/Rel-18/38_series/38863/47e75dc9e83054b2dac3df8bf3e57019_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28b5092f9bc62986020a88ea79e779ac21273ed408527695cd8086f78c6bb13d +size 72628 diff --git a/marked/Rel-18/38_series/38863/4908c132d4fbad657b6fc84561c43fbb_img.jpg b/marked/Rel-18/38_series/38863/4908c132d4fbad657b6fc84561c43fbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf7493497ea137a7fcd09bd3262e4424e160df77 --- /dev/null +++ b/marked/Rel-18/38_series/38863/4908c132d4fbad657b6fc84561c43fbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebcb83edc2f03a87bb14285016628c0b2ae821750f3a9f76251c830f861fe34f +size 34689 diff --git a/marked/Rel-18/38_series/38863/509a054727400bc6d424bb2a559b8cfc_img.jpg b/marked/Rel-18/38_series/38863/509a054727400bc6d424bb2a559b8cfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5df30fc91b2b9a38ea28c414fcd8de4619111b2 --- /dev/null +++ b/marked/Rel-18/38_series/38863/509a054727400bc6d424bb2a559b8cfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acba6242520b1bf40c9e9f822bc1693e47a2fabe6311f991d2256063a7ce276a +size 35178 diff --git a/marked/Rel-18/38_series/38863/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38863/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bd4871f4a1dad728369e6eb2bb56ec86b4c3b39 --- /dev/null +++ b/marked/Rel-18/38_series/38863/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ffb61f2814e4b0afe0b2524901904f19ce26e01e7b46e910daa104da78edc46 +size 43746 diff --git a/marked/Rel-18/38_series/38863/54d490f646eb3cc3b92ec4abf3030a85_img.jpg b/marked/Rel-18/38_series/38863/54d490f646eb3cc3b92ec4abf3030a85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5124103dbe56aa294c7fd08b6f4543ccddd7e18 --- /dev/null +++ b/marked/Rel-18/38_series/38863/54d490f646eb3cc3b92ec4abf3030a85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fd88f2d135763a5b1621cb9f2ca82de4bac0af778c5021b4944fb2c7be049e0 +size 38979 diff --git a/marked/Rel-18/38_series/38863/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-18/38_series/38863/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8159ecaa76bec045bfb4e853780d30b323e35f86 --- /dev/null +++ b/marked/Rel-18/38_series/38863/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72ebfe9b1149a6b3225e6b9cc0d13afb144554635c404a2dcbb3585a915ece0a +size 27028 diff --git a/marked/Rel-18/38_series/38863/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38863/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbe6ebc86e3c24d0fb1009c6b9c0b7f1946ffcf8 --- /dev/null +++ b/marked/Rel-18/38_series/38863/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a86d60bda596e5c69e30f3824e43c2f31d853e7b43175d9657186f90171b2004 +size 9689 diff --git a/marked/Rel-18/38_series/38863/61c876684d8cc2ea8784b52440318350_img.jpg b/marked/Rel-18/38_series/38863/61c876684d8cc2ea8784b52440318350_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baf923c1240650efaee472a27543d91fa221b110 --- /dev/null +++ b/marked/Rel-18/38_series/38863/61c876684d8cc2ea8784b52440318350_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fae35fb07541686c5e04fd1c40bf062aeb19b3919053678ddbd6aaf4ac27749 +size 45435 diff --git a/marked/Rel-18/38_series/38863/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38863/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daf7b632418311f0578b0d37ce5749200e19e557 --- /dev/null +++ b/marked/Rel-18/38_series/38863/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6de7729e63a4bfb363118c815b5a96e8b08bc09c23de37a220ba3255aaab7e49 +size 5658 diff --git a/marked/Rel-18/38_series/38863/6c3063f123860b89793e4fee0d6b4150_img.jpg b/marked/Rel-18/38_series/38863/6c3063f123860b89793e4fee0d6b4150_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0174baca1f78e04fdfe6f688ef9e85a1f163399d --- /dev/null +++ b/marked/Rel-18/38_series/38863/6c3063f123860b89793e4fee0d6b4150_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a4ea68daadcb04039298a04c1a0427dae5a0017cf809adef6bb2f66eda3a7d9 +size 39244 diff --git a/marked/Rel-18/38_series/38863/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-18/38_series/38863/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e101a5e391f0108e75a4fb8e0880956e1d31ea60 --- /dev/null +++ b/marked/Rel-18/38_series/38863/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e25b200b3fbec6164dc85f4a465f2a8d2fdac2651cf4274715fd6a748254f65 +size 31888 diff --git a/marked/Rel-18/38_series/38863/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-18/38_series/38863/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65db9940c3da512e18ea8aab10d7118617074b0e --- /dev/null +++ b/marked/Rel-18/38_series/38863/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56b5d71c4c233768bf4d29adfbcf1cf14959f6f3dcd5c3e2cb9b4f1630d6c612 +size 39873 diff --git a/marked/Rel-18/38_series/38863/728ce58d1dcdbbbd39b97904271326ca_img.jpg b/marked/Rel-18/38_series/38863/728ce58d1dcdbbbd39b97904271326ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44ffc619dbaf04c0de02b4190d76273ee9d6c35b --- /dev/null +++ b/marked/Rel-18/38_series/38863/728ce58d1dcdbbbd39b97904271326ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b060baa835d6eacad14ff2ac6262e43138838e29e53c031a26aeb184a9e3999 +size 75745 diff --git a/marked/Rel-18/38_series/38863/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38863/7c0a9511fa02b6c2c125ff5be465186e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80014ae064b8fc1df9fb9e58c8cf18da95cbffe6 --- /dev/null +++ b/marked/Rel-18/38_series/38863/7c0a9511fa02b6c2c125ff5be465186e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b13def90cb62dbe5e2cbf0a06e7591f380235a044b14e819b98296d98512200 +size 32885 diff --git a/marked/Rel-18/38_series/38863/812f92102114dc0fa8487e0bfc372472_img.jpg b/marked/Rel-18/38_series/38863/812f92102114dc0fa8487e0bfc372472_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12f3aa1feaa3d7d987c942e8186771ff9b916ab5 --- /dev/null +++ b/marked/Rel-18/38_series/38863/812f92102114dc0fa8487e0bfc372472_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:280e6e2f112fd3d0ebe976f0d156c0710fd0c2aad4dd1a094833d83618483e6e +size 42964 diff --git a/marked/Rel-18/38_series/38863/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg b/marked/Rel-18/38_series/38863/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0669f06831d09523bad25326cb38f98979c15b3 --- /dev/null +++ b/marked/Rel-18/38_series/38863/8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:246af89bdc8ba7066a201a7cd091d4da5249faed491fec90e61e343868c6cc25 +size 43790 diff --git a/marked/Rel-18/38_series/38863/94389c644d3c25d99db7bc6d87bf5779_img.jpg b/marked/Rel-18/38_series/38863/94389c644d3c25d99db7bc6d87bf5779_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00ac17ba7b4545eebf21daa21c9c903363deeb69 --- /dev/null +++ b/marked/Rel-18/38_series/38863/94389c644d3c25d99db7bc6d87bf5779_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f95cb951a3ca4a7a3629e5c5b25b657eb3909128d47e2eb68776193f391c5905 +size 48552 diff --git a/marked/Rel-18/38_series/38863/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg b/marked/Rel-18/38_series/38863/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d7e100002e1a272fd3aaa82c1f7a6057c3c5985 --- /dev/null +++ b/marked/Rel-18/38_series/38863/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5d2bebb50b1d3464461fd21214aa1fd740d6f88ad40bc4f718d90802f52a22b +size 83573 diff --git a/marked/Rel-18/38_series/38863/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/38_series/38863/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e119edf2b1a9abfca38a31abf5fa8552d17931d --- /dev/null +++ b/marked/Rel-18/38_series/38863/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c8f98ec7304dbe82c9d01c3cec3ba6cc73c035e4e7bb152d3e7ed922dc24603 +size 39546 diff --git a/marked/Rel-18/38_series/38863/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/Rel-18/38_series/38863/9f92854fe6ecaf47760515c891a4fccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..642d0a1969b6dd2e46b94c083b609394b4eff9e6 --- /dev/null +++ b/marked/Rel-18/38_series/38863/9f92854fe6ecaf47760515c891a4fccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18816b928ec2ffde9633588ac296f67164ac0567d7dd4cf061cb45429f9c4702 +size 33519 diff --git a/marked/Rel-18/38_series/38863/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg b/marked/Rel-18/38_series/38863/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be85f0b884e63395e30b155d8ccc1fd37147c763 --- /dev/null +++ b/marked/Rel-18/38_series/38863/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:850466dc97d51db839a47ff77952c6c8c7ccab36a5271429618f04823cc644e9 +size 39501 diff --git a/marked/Rel-18/38_series/38863/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Rel-18/38_series/38863/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..876523af754b3509092533dddc624a382b9de029 --- /dev/null +++ b/marked/Rel-18/38_series/38863/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9b7ac07f27d7c0a50b4e360103dfb9260776ef2dfe067fa868a1a05380b3f80 +size 15708 diff --git a/marked/Rel-18/38_series/38863/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-18/38_series/38863/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c96ba9998c73a9c022dd0b6359cf930a2ba44abc --- /dev/null +++ b/marked/Rel-18/38_series/38863/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b5bb4f84cf92a925625f35b55e76a1496594fa628a719a9593d5d3709cd7eeb +size 39339 diff --git a/marked/Rel-18/38_series/38863/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-18/38_series/38863/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a5f0c5d75e80cd377b5cbc47206e6ca91b3d744 --- /dev/null +++ b/marked/Rel-18/38_series/38863/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67d131b6721539de735069601341c082a63dd4648f2943ed08eaf5beea8788f8 +size 60412 diff --git a/marked/Rel-18/38_series/38863/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg b/marked/Rel-18/38_series/38863/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d4c777184401957896e0270f87b47e2c737bec1 --- /dev/null +++ b/marked/Rel-18/38_series/38863/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f11d9ae5acef951cada4ef6677c61adc3bbeee4d9798c4e43f39cfb42bac3186 +size 39898 diff --git a/marked/Rel-18/38_series/38863/b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg b/marked/Rel-18/38_series/38863/b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b1136d58df5a81e0eacd7ddc93ab050aa0c8384 --- /dev/null +++ b/marked/Rel-18/38_series/38863/b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e39f1c33cdaaadb2431d0e0141814af5f8ae95a467d89743ad497ecf8ca46e8 +size 34993 diff --git a/marked/Rel-18/38_series/38863/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg b/marked/Rel-18/38_series/38863/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..011bed514031bae11cfee252a4d7cbf4cea698c9 --- /dev/null +++ b/marked/Rel-18/38_series/38863/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9407e9b53aa15df4f3c19bcb335d92d3f0cede5647f6ce5eca8118a510e8e491 +size 36185 diff --git a/marked/Rel-18/38_series/38863/bf5785e70ae74c9228ac60009aeb677e_img.jpg b/marked/Rel-18/38_series/38863/bf5785e70ae74c9228ac60009aeb677e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..698d7e746d4a2fab72454f9dafedd0dfd314c9b0 --- /dev/null +++ b/marked/Rel-18/38_series/38863/bf5785e70ae74c9228ac60009aeb677e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13922531cc6267e0f48e0b2b66c83ea426c918fefef70b5d4862e91fcba329e4 +size 46855 diff --git a/marked/Rel-18/38_series/38863/bf5971de45ccc2d1a9e437d0f486ee08_img.jpg b/marked/Rel-18/38_series/38863/bf5971de45ccc2d1a9e437d0f486ee08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..666a478a9e02057a67031d231191d970fb0d2362 --- /dev/null +++ b/marked/Rel-18/38_series/38863/bf5971de45ccc2d1a9e437d0f486ee08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:631598fea53d829b55a2a2796371c28f25c87f2dfd244051b1576cd49810805b +size 39537 diff --git a/marked/Rel-18/38_series/38863/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38863/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59b065171bb24fb0e4bfb0bc17ec0c778d6d43b7 --- /dev/null +++ b/marked/Rel-18/38_series/38863/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b37ebd627e459107cbfd899d1077589f75f708c55981e3a78f8db0e1c0430866 +size 47991 diff --git a/marked/Rel-18/38_series/38863/c742b64169a38a7f3f990172019878c8_img.jpg b/marked/Rel-18/38_series/38863/c742b64169a38a7f3f990172019878c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cdb723419686f2cf0df278b10806d9747cf32ae --- /dev/null +++ b/marked/Rel-18/38_series/38863/c742b64169a38a7f3f990172019878c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeb4c4e7a253ee981efe7853ddd1b39ae678fba9e16a60afd18759df82dcf2d9 +size 37015 diff --git a/marked/Rel-18/38_series/38863/ca6d62cc69ec88d9b5dc227b2dac7bc9_img.jpg b/marked/Rel-18/38_series/38863/ca6d62cc69ec88d9b5dc227b2dac7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f15cf902bbf40c8d9fc8879b4d2728edcab9546 --- /dev/null +++ b/marked/Rel-18/38_series/38863/ca6d62cc69ec88d9b5dc227b2dac7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a78e5b31ac34b007334fcef11075a5c62c78121b23f45eecdd60d092e77edcf7 +size 1642 diff --git a/marked/Rel-18/38_series/38863/cc7bd229cf6c181b389c7a43184af609_img.jpg b/marked/Rel-18/38_series/38863/cc7bd229cf6c181b389c7a43184af609_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aba8ba4c4a419053df3f63b27ea4196b94ddda0 --- /dev/null +++ b/marked/Rel-18/38_series/38863/cc7bd229cf6c181b389c7a43184af609_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1c18e6772ec0e1d6e5a75edf60812634780ca477d52b5b12568fa1548465469 +size 53765 diff --git a/marked/Rel-18/38_series/38863/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/Rel-18/38_series/38863/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a04453ee962c1f2236af3da313c3eb76a353e9c --- /dev/null +++ b/marked/Rel-18/38_series/38863/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ff858025500524fee15d94bce62d37d0dd721addd3ae27296aa2c03bcfb9a24 +size 39490 diff --git a/marked/Rel-18/38_series/38863/df94f7807f02e218ee3c66b9cbd829e5_img.jpg b/marked/Rel-18/38_series/38863/df94f7807f02e218ee3c66b9cbd829e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73b9c6857a50fdfad7b98e4a1adc260fbf7034dc --- /dev/null +++ b/marked/Rel-18/38_series/38863/df94f7807f02e218ee3c66b9cbd829e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15c3faa40fed5826f6eaaaa6567c675157ca1a393bee12c266e43f2bf7605c95 +size 42347 diff --git a/marked/Rel-18/38_series/38863/e80df82d8dc91b2f758dad02fd449ebd_img.jpg b/marked/Rel-18/38_series/38863/e80df82d8dc91b2f758dad02fd449ebd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1445a3dd7a739ec774e9f144b93419965beb0951 --- /dev/null +++ b/marked/Rel-18/38_series/38863/e80df82d8dc91b2f758dad02fd449ebd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dfa4012ceb9b9bc52c37a581f34f5046db655161b77a112fff78c5f373add30 +size 34094 diff --git a/marked/Rel-18/38_series/38863/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-18/38_series/38863/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5edca93b33997087834d2f05bd4b3ed4f8c8541c --- /dev/null +++ b/marked/Rel-18/38_series/38863/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06f400235b841b8377a6a7c28845ec8d12cfaa8ebbd1da058bd8bce92b89bad4 +size 25064 diff --git a/marked/Rel-18/38_series/38863/f9d11004ac6966f27936c8d01e579313_img.jpg b/marked/Rel-18/38_series/38863/f9d11004ac6966f27936c8d01e579313_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..675cae6f347405b02f1fc7789b54ddda8bb01fba --- /dev/null +++ b/marked/Rel-18/38_series/38863/f9d11004ac6966f27936c8d01e579313_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f82d448ec4e85f9e7de633bfcc4901f1d3024f5f3184928cf205a6f1fb8da36 +size 49496 diff --git a/marked/Rel-18/38_series/38863/raw.md b/marked/Rel-18/38_series/38863/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..568219e9b6947d652495d8bc48b5d5ec3c383510 --- /dev/null +++ b/marked/Rel-18/38_series/38863/raw.md @@ -0,0 +1,3823 @@ + + +# 3GPP TR 38.863 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Solutions for NR to support non-terrestrial networks (NTN): Non-terrestrial networks (NTN) related RF and co-existence aspects (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font. Below the 'P' is a red signal wave icon, and below the entire logo is the text 'A GLOBAL INITIATIVE'. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 2 Reference ..... | 10 | +| 3 Definition of terms, symbols and abbreviations ..... | 12 | +| 3.1 Terms..... | 12 | +| 3.2 Symbols..... | 12 | +| 3.3 Abbreviations ..... | 13 | +| 4 General aspects ..... | 14 | +| 4.1 Work item objectives ..... | 14 | +| 5 Regulatory aspects ..... | 14 | +| 5.1 ITU-R ..... | 14 | +| 5.2 Regulatory aspects for NTN satellites..... | 15 | +| 5.2.1 NTN Satellite band: UL 1980–2010 MHz / DL 2170–2200 MHz..... | 15 | +| 5.2.2 NTN Satellite band: UL 1626.5–1660.5 MHz / DL 1525–1559 MHz..... | 16 | +| 5.2.3 NTN Satellite band: UL 27.5-30.0 GHz / DL 17.3-20.2 GHz ..... | 20 | +| 5.2.3.1 ITU-R..... | 20 | +| 5.2.3.2 FCC..... | 23 | +| 5.2.3.3 CEPT..... | 24 | +| 5.3 Regulatory aspects for HAPS..... | 25 | +| 6 Co-existence study ..... | 25 | +| 6.1 Co-existence simulation scenario..... | 25 | +| 6.2 Co-existence simulation assumption..... | 27 | +| 6.2.1 Network layout model ..... | 27 | +| 6.2.1.1 Co-existence between NTN satellite and TN ..... | 27 | +| 6.2.1.2 Co-existence between HAPS and TN..... | 30 | +| 6.2.1.3 Co-existence between HAPS and HAPS..... | 30 | +| 6.2.2 System parameters..... | 31 | +| 6.2.2.1 Satellite parameters..... | 31 | +| 6.2.2.2 NTN UE parameters ..... | 32 | +| 6.2.2.3 HAPS parameters..... | 33 | +| 6.2.2.4 TN parameters..... | 34 | +| 6.2.3 Antenna and beamforming pattern modelling..... | 36 | +| 6.2.3.1 Satellite and UE Antenna and beam forming pattern modelling ..... | 36 | +| 6.2.3.2 TN BS and UE antenna and beam forming pattern modelling ..... | 40 | +| 6.2.3.3 HAPS antenna model..... | 41 | +| 6.2.4 ACIR model..... | 42 | +| 6.2.5 Propagation model..... | 42 | +| 6.2.5.1 Propagation model between NTN SAN and UE ..... | 42 | +| 6.2.5.2 Propagation model between TN BS and UE ..... | 43 | +| 6.2.5.3 Propagation model between NTN SAN and TN BS..... | 43 | +| 6.2.5.4 Propagation model for HAPS ..... | 43 | +| 6.2.6 Transmission power control model ..... | 43 | +| 6.2.6.1 TN UL TPC ..... | 43 | +| 6.2.6.2 NTN UL TPC..... | 43 | +| 6.2.6.3 NTN DL TPC..... | 43 | +| 6.2.6.4 HAPS UL TPC..... | 43 | +| 6.2.6.5 HAPS DL TPC..... | 43 | +| 6.2.7 Received power model ..... | 43 | +| 6.2.8 Performance metric ..... | 44 | +| 6.2.9 Throughput ~ SNR mapping ..... | 44 | +| 6.3 Co-existence simulation methodology ..... | 44 | +| 6.3.1 Simulation procedure..... | 44 | +| 6.3.2 Methods and principle to process co-existence simulation results..... | 45 | + +| | | | +|-----------|----------------------------------------------------------|----| +| 6.4 | Co-existence simulation results..... | 46 | +| 6.4.1 | Scenario 1: 2GHz TN DL interfering NTN DL ..... | 46 | +| 6.4.2 | Scenario 2: 2GHz TN UL interfering NTN UL ..... | 49 | +| 6.4.3 | Scenario 3: 2GHz NTN DL interfering TN DL ..... | 53 | +| 6.4.3.1 | LEO Class ..... | 53 | +| 6.4.4 | Scenario 4: 2GHz NTN UL interfering TN UL ..... | 60 | +| 6.4.5 | Scenario 5: 2GHz NTN UL interfering TN DL ..... | 64 | +| 6.4.6 | Scenario 6: 2GHz TN DL interfering NTN UL ..... | 67 | +| 6.4.7 | Scenario 7: 2GHz HAPS DL interfering TN DL ..... | 69 | +| 6.4.8 | Scenario 8: 2GHz TN UL interfering HAPS UL ..... | 70 | +| 6.5 | Summary of co-existence study ..... | 71 | +| 6.5.1 | Coexistence at 2GHz ..... | 71 | +| 7 | RF requirements ..... | 73 | +| 7.1 | SAN Reference points for RF requirements ..... | 73 | +| 7.1.1 | General ..... | 73 | +| 7.1.2 | SAN type 1-C ..... | 73 | +| 7.1.3 | SAN type 1-H ..... | 73 | +| 7.1.4 | SAN type 1-O ..... | 74 | +| 7.2 | Common issues for satellite access node and NTN UE ..... | 74 | +| 7.2.1 | General ..... | 74 | +| 7.2.2 | Operating bands ..... | 74 | +| 7.2.3 | Channel bandwidth, SCS and spectral utilization ..... | 75 | +| 7.2.4 | Channel raster and sync raster ..... | 75 | +| 7.2.4.1 | Channel raster ..... | 75 | +| 7.2.4.2 | Sync raster ..... | 75 | +| 7.3 | Satellite Access Node requirements ..... | 75 | +| 7.3.1 | General ..... | 75 | +| 7.3.1.1 | SAN class ..... | 76 | +| 7.3.2 | Transmission characteristics ..... | 76 | +| 7.3.2.1 | General ..... | 76 | +| 7.3.2.2 | Conducted transmitter requirements ..... | 76 | +| 7.3.2.2.1 | SAN output power ..... | 76 | +| 7.3.2.2.2 | Output power dynamics ..... | 77 | +| 7.3.2.2.3 | Transmitted signal quality ..... | 77 | +| 7.3.2.2.4 | Unwanted emissions ..... | 78 | +| 7.3.2.2.5 | Transmitter spurious emission ..... | 80 | +| 7.3.2.3 | Radiated transmitter requirements ..... | 80 | +| 7.3.2.3.1 | Reserved ..... | 80 | +| 7.3.2.3.2 | Reserved ..... | 80 | +| 7.3.2.3.3 | Reserved ..... | 80 | +| 7.3.2.3.4 | Reserved ..... | 80 | +| 7.3.2.3.5 | Reserved ..... | 80 | +| 7.3.2.3.6 | Reserved ..... | 80 | +| 7.3.2.3.7 | Reserved ..... | 80 | +| 7.3.3 | Receiver characteristics ..... | 81 | +| 7.3.3.1 | General ..... | 81 | +| 7.3.3.2 | Conducted receiver characteristics ..... | 81 | +| 7.3.3.2.1 | Reference sensitivity level ..... | 81 | +| 7.3.3.2.2 | Dynamic range ..... | 82 | +| 7.3.3.2.3 | In-band selectivity and blocking ..... | 82 | +| 7.3.3.2.4 | Out-of-band blocking ..... | 84 | +| 7.3.3.2.5 | Receiver spurious emissions ..... | 85 | +| 7.3.3.2.6 | Receiver intermodulation ..... | 85 | +| 7.3.3.2.7 | In-channel selectivity ..... | 85 | +| 7.3.3.3 | Radiated receiver characteristics ..... | 85 | +| 7.3.3.3.1 | OTA sensitivity ..... | 85 | +| 7.3.3.3.2 | OTA reference sensitivity level ..... | 85 | +| 7.3.3.3.3 | OTA dynamic range ..... | 85 | +| 7.3.3.3.4 | OTA in-band selectivity and blocking ..... | 86 | +| 7.3.3.3.5 | OTA out-of-band blocking ..... | 86 | +| 7.3.3.3.6 | OTA receiver spurious emissions ..... | 86 | + +| | | | +|----------------------------------------------------------------------------|----------------------------------------------------------------|------------| +| 7.3.3.3.7 | OTA receiver intermodulation ..... | 87 | +| 7.3.3.3.8 | OTA in-channel selectivity ..... | 87 | +| 7.3.4 | Others ..... | 87 | +| 7.4 | NTN UE requirements ..... | 87 | +| 7.4.1 | General ..... | 87 | +| 7.4.2 | UE Transmission characteristics for satellite access ..... | 87 | +| 7.4.2.1 | General ..... | 87 | +| 7.4.2.2 | Conducted transmitter characteristics ..... | 87 | +| 7.4.2.2.1 | Maximum output power ..... | 87 | +| 7.4.2.2.2 | MPR/AMPR ..... | 87 | +| 7.4.2.2.3 | Output power dynamics ..... | 89 | +| 7.4.2.2.4 | Frequency error ..... | 89 | +| 7.4.2.2.5 | Transmit modulation quality ..... | 89 | +| 7.4.2.2.6 | Spectrum emission mask ..... | 89 | +| 7.4.2.2.7 | ACLR ..... | 89 | +| 7.4.2.2.8 | Spurious emissions ..... | 89 | +| 7.4.2.2.9 | Transmit intermodulation ..... | 90 | +| 7.4.2.2.10 | UE to UE coexistence issues between NTN and TN ..... | 90 | +| 7.4.2.3 | “Reserved” (for Radiated transmitter Characteristics) ..... | 91 | +| 7.4.3 | UE Receiver characteristics for satellite access ..... | 91 | +| 7.4.3.1 | General ..... | 91 | +| 7.4.3.2 | Conducted receiver characteristics ..... | 91 | +| 7.4.3.2.1 | General and diversity characteristics ..... | 91 | +| 7.4.3.2.2 | Reference sensitivity ..... | 92 | +| 7.4.3.2.3 | Maximum input level ..... | 92 | +| 7.4.3.2.4 | Adjacent channel selectivity ..... | 93 | +| 7.4.3.2.5 | Blocking characteristics ..... | 93 | +| 7.4.3.2.6 | Spurious response ..... | 93 | +| 7.4.3.2.7 | Intermodulation characteristics ..... | 93 | +| 7.4.3.2.8 | Rx Spurious emissions ..... | 94 | +| 7.4.3.2.9 | Void ..... | 94 | +| 7.4.3.3 | “Reserved” (for Radiated receiver characteristics) ..... | 94 | +| 7.4.4 | UE antenna characteristics for satellite access ..... | 94 | +| 7.4.4.1 | Handheld UE antenna characteristics for satellite access ..... | 94 | +| 8 | Conclusion ..... | 94 | +| Annex A: Calibration results of NTN components ..... | | 95 | +| A.1 | Calibration assumptions at 2GHz ..... | 95 | +| A.2 | Calibration results at 2GHz ..... | 95 | +| Annex B: Calibration results of TN components ..... | | 100 | +| B.1 | Calibration assumptions at 2GHz ..... | 100 | +| B.2 | Calibration results at 2GHz ..... | 101 | +| Annex C: Summary of NR-NTN co-existence study ..... | | 103 | +| Annex D: Summary of simulation results for the IoT derivation ..... | | 104 | +| Annex E Change history ..... | | 105 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document covers the RF and co-existence aspects of the work item “Solutions for NR to support non-terrestrial networks (NTN)” [2] + +The objectives for the study are the following: + +- Study and specify adjacent channel co-existence scenarios of Non-terrestrial networks (NTN). +- Study and specify needed generic RF core requirements for the network and the UE such that adjacent channel co-existence scenarios are met. + +NOTE: Satellite operation is used as complementarily to Terrestrial Network operation, and in separate location when satellite operates in an adjacent channel/band of terrestrial network. For instance, NTN satellite UE is assumed to connect and transmit to the satellite when it is outside a Terrestrial Network operating in an adjacent channel/band. The satellite beam might still overlap the terrestrial network. + +# --- 2 Reference + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP RP-213691: "Revised WID: Solutions for NR to support non-terrestrial networks (NTN)". +- [3] ITU-R Radio Regulations, 2020 Edition +- [4] ECC Decision 06(09): "Designation of the bands 1980-2010 MHz and 2170-2200 MHz for use by systems in the Mobile-Satellite Service including those supplemented by a Complementary Ground Component (CGC)", Approved 01 December 2006, Amended 05 September 2007, +- [5] 3GPP TR 38.811: "Study on New Radio (NR) to support non-terrestrial networks". +- [6] 3GPP TR 38.821: "Solutions for NR to support Non-Terrestrial Networks (NTN)". +- [7] 3GPP RP-152284: "Revised Work Item: Narrowband IoT ". +- [8] 3GPP TR 36.942: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Frequency (RF) system scenarios". + +- [9] 3GPP TR 45.820: "Cellular system support for ultra-low complexity and low throughput Internet of Things (CIoT)". +- [10] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz". +- [11] Report ITU-R M.2292: "Characteristics of terrestrial IMT-Advanced systems for frequency sharing/interference analyses". +- [12] 3GPP RP-200559: "LS on Parameters of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-23 (below 5 GHz) ". +- [13] ITU-R Annex 4.4 to Document 5D/716-E. +- [14] 3GPP TR 38.921: "Study on International Mobile Telecommunications (IMT) parameters for 6.425 - 7.025 GHz, 7.025 - 7.125 GHz and 10.0 - 10.5 GHz". +- [15] 3GPP TR 36.802: "Evolved Universal Terrestrial Radio Access (E-UTRA); NB-IOT; Technical Report for BS and UE radio transmission and reception". +- [16] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [17] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [18] 3GPP R4-2111460: "On the Rx Parameters and Rx Testing Setup for NTN gNB". +- [19] 3GPP R4-2108099: "WF on [312] NTN\_Solutions\_Part1". +- [20] FCC Online Table of Frequency Allocations, 47 C.F.R § 2.106, February 1, 2021. +- [21] FCC Order 03-15, Report and Order and Notice of Proposed Rule Making, January 29, 2003. +- [22] FCC Order 20-48, Order and Authorization, April 19, 2020. +- [23] FCC Code of Federal Regulations. +- [24] SoftBank, Loon LLC, Nokia, Ericsson, "Proposed deployment and system characteristics of HIBS in the working document towards a preliminary draft new Report ITU-R M.[HIBS-CHARACTERISTICS]," ITU WP-5D contribution, Sep. 28, 2020. +- [25] 3GPP TS 38.181: "NR; Satellite Node conformance testing". +- [26] 3GPP TS 38.108: "NR; Satellite Node radio transmission and reception". +- [27] 3GPP R4-213618: "Moderator's summary of discussion [94e-41-R17-NRNTN-RAN4Spec] ". +- [28] ERC Recommendation 74-01: "Unwanted emissions in the spurious domain". +- [29] Recommendation ITU-R SM.1541-6: "Unwanted emissions in the out-of-band domain". +- [30] Recommendation ITU-R SM.329: "Unwanted emissions in the spurious domain". +- [31] 3GPP TR 38.817-02: "General aspects for Base Station (BS) Radio Frequency (RF) for NR". +- [32] 3GPP TR 38.817-01: " General aspects for User Equipment (UE) Radio Frequency (RF) for NR". +- [33] FCC 16-89, REPORT AND ORDER AND FURTHER NOTICE OF PROPOSED RULEMAKING +- [34] FCC 20-159, REPORT AND ORDER +- [35] FCC 20-166, SECOND REPORT AND ORDER IN IB DOCKET NO. 17-95 AND REPORT AND ORDER IN IB DOCKET NO. 18-315 AND FURTHER NOTICE OF PROPOSED RULEMAKING +- [36] ECC Decision(05)01, The use of the band 27.5-29.5 GHz by the Fixed Service and uncoordinated Earth stations of the Fixed-Satellite Service (Earth-to-space) + +[37] ECC Decision(13)01, The harmonised use, free circulation and exemption from individual licensing of Earth Stations On Mobile Platforms (ESOMPs) within the frequency bands 17.3-20.2 GHz and 27.5-30.0 GHz + +# 3 Definition of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Feeder link:** Wireless link between NTN-Gateway and satellite + +**Geostationary Earth Orbit:** Circular orbit at 35,786 km above the Earth's equator and following the direction of the Earth's rotation. An object in such an orbit has an orbital period equal to the Earth's rotational period and thus appears motionless, at a fixed position in the sky, to ground observers. + +**Geosynchronous Orbit:** Earth-centered orbit at approximately 35786 kilometres above Earth's surface and synchronised with Earth's rotation. A geostationary orbit is a non-inclined geosynchronous orbit, i.e. in the Earth's equator plane. + +**Low Earth Orbit:** Orbit around the Earth with an altitude between 300 km, and 1500 km. + +**Minimum Elevation angle:** Minimum angle under which the satellite or HAPS can be seen by a UE. + +**Non-Geostationary Satellites:** Satellites (LEO and MEO) orbiting around the Earth with a period that varies approximately between 1.5 hour and 10 hours. It is necessary to have a constellation of several Non-Geostationary satellites associated with handover mechanisms to ensure a service continuity. + +**Non-terrestrial networks:** Networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station. + +**NTN-Gateway:** An earth station or gateway is located at the surface of Earth, and providing sufficient RF power and RF sensitivity for accessing to the satellite (resp. HAPS). + +**Satellite:** A space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), or Geostationary Earth Orbit (GEO). + +**Service link:** Radio link between satellite and UE + +**Transparent payload:** Payload that changes the frequency carrier of the UL/DL RF signal, filters and amplifies it before transmitting it on the DL/UL, respectively. + +**UE transmission bandwidth configuration:** Set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE. + +**User Throughput:** data rate provided to a terminal + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | | | +|----------------------------|-------------------------------------------------------------|----------------------------|--------------------------------------------| +| $\Delta F_{\text{Raster}}$ | Band dependent channel raster granularity | $\Delta F_{\text{Global}}$ | Granularity of the global frequency raster | +| $\Delta F_{\text{Raster}}$ | Band dependent channel raster granularity | | | +| $BW_{\text{Channel}}$ | Channel bandwidth | | | +| $BW_{\text{interferer}}$ | Bandwidth of the interferer | | | +| $F_{\text{DL\_low}}$ | The lowest frequency of the downlink operating band | | | +| $F_{\text{DL\_high}}$ | The highest frequency of the downlink operating band | | | +| $F_{\text{UL\_low}}$ | The lowest frequency of the uplink operating band | | | + +| | | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| $F_{UL\_high}$ | The highest frequency of the uplink operating band | +| $F_{Interferer}$ | Frequency of the interferer | +| $F_{Interferer} \text{ (offset)}$ | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | +| $F_{Ioffset}$ | Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) | +| $F_{OOB}$ | The boundary between the NR out of band emission and spurious emission domains | +| $F_{REF}$ | RF reference frequency | +| $F_{REF-offs}$ | Offset used for calculating $F_{REF}$ | +| $F_{uw} \text{ (offset)}$ | The frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the interferer | +| $N_{RB}$ | Transmission bandwidth configuration, expressed in units of resource blocks $N_{REF}$ NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{REF}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{REF-offs}$ | Offset used for calculating $N_{REF}$ | +| $P_{Interferer}$ | Modulated mean power of the interferer | +| $P_{uw}$ | Power of an unwanted DL signal | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------------|------------------------------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| A-MPR | Additional Maximum Power Reduction | +| BS | Base Station | +| BW | Bandwidth | +| BWP | Bandwidth Part | +| CG | Carrier Group | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| DTX | Discontinuous Transmission | +| EIRP | Equivalent Isotropically Radiated Power | +| EVM | Error Vector Magnitude | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| FRF | Frequency Reuse Factor | +| FSS | Fixed Satellite Services | +| FWA | Fixed Wireless Access | +| GEO | Geostationary Earth Orbiting | +| gNB | next Generation Node B | +| GW | Gateway | +| GSCN | Global Synchronization Channel Number | +| HAPS | High Altitude Platform Station | +| HIPS | HAPS as IMT Base Stations | +| IBB | In-band Blocking | +| IDFT | Inverse Discrete Fourier Transformation | +| ISL | Inter-Satellite Links | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LEO | Low Earth Orbiting | +| Mbps | Mega bit per second | +| MBW | Measurement bandwidth defined for the protected band | +| MCG | Master Cell Group | +| MEO | Medium Earth Orbiting | +| MOP | Maximum Output Power | +| MPR | Allowed maximum power reduction | +| MS | Mobile Services | +| MSD | Maximum Sensitivity Degradation | + +| | | +|----------|--------------------------------------------| +| MSS | Mobile Satellite Services | +| NGEO | Non-Geostationary Earth Orbiting | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NS | Network Signalling | +| NTN | Non-Terrestrial Network | +| OCNG | OFDMA Channel Noise Generator | +| OOB | Out-of-band | +| P-MPR | Power Management Maximum Power Reduction | +| PRB | Physical Resource Block | +| PSCCH | Physical Sidelink Control CHannel | +| PSSCH | Physical Sidelink Shared CHannel | +| QAM | Quadrature Amplitude Modulation | +| RAN | Radio Access Network | +| RE | Resource Element | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RSRP | Reference Signal Receiving Power | +| Rx | Receiver | +| SAN | Satellite Access Node | +| SC | Single Carrier | +| SCG | Secondary Cell Group | +| SCS | Subcarrier spacing | +| SEM | Spectrum Emission Mask | +| SNR | Signal-to-Noise Ratio | +| SRS | Sounding Reference Symbol | +| SS | Synchronization Symbol | +| TAE | Time Alignment Error | +| TAG | Timing Advance Group | +| Tx | Transmitter | +| TxD | Tx Diversity | +| UE | User Equipment | +| ULFPTx | Uplink Full Power Transmission | + +# --- 4 General aspects + +## 4.1 Work item objectives + +The Work item objectives are captured in [2]. + +# --- 5 Regulatory aspects + +## 5.1 ITU-R + +The following services are among those defined in the ITU-R Radio Regulations [3]: + +- Fixed (1.20): A radiocommunication service between specified fixed points. +- Fixed satellite (1.21) : A radiocommunication service between earth stations at given positions, when one or more satellites are used; the given position may be a specified fixed point or any fixed point within specified areas; in some cases this service includes satellite-to-satellite links, which may also be operated in the inter-satellite service; the fixed-satellite service may also include feeder links for other space radiocommunication services. +- Mobile (1.24): radiocommunication service between mobile and land stations, or between mobile stations (CV). + +- Mobile satellite (1.25): A radiocommunication service: + - between mobile earth stations and one or more space stations, or between space stations used by this service; or + - between mobile earth stations by means of one or more space stations. + +This service may also include feeder links necessary for its operation. + +Based on the ITU-R Radio Regulations [3], the following frequency ranges are allocated to MSS and have been identified as first candidate bands for NTN satellite operations: + +- S-band: UL: 1980–2010 MHz / DL: 2170–2200 MHz. +- L-band: UL: 1626.5-1660.5 MHz / DL: 1525-1559 MHz. + +For providing mobile services through HAPS, current ITU-R Radio Regulations [3] allow the use of frequency ranges 1885–1980 MHz, 2010-2025 MHz and 2110–2170 MHz by HAPS. Additional spectrum may be allocated for HAPS in 2023 (see clause 5.3). + +## 5.2 Regulatory aspects for NTN satellites + +### 5.2.1 NTN Satellite band: UL 1980–2010 MHz / DL 2170–2200 MHz + +The ITU-R Radio Regulations [3] specify the following service allocation for those frequency ranges, shown in Table 5.2.1-1: + +**Table 5.2.1-1: Allocation of 1980–2010 MHz and 2170–2200 MHz in the ITU-R Radio Regulations** + +| Allocation to services | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|----------| +| Region 1 | Region 2 | Region 3 | +| 2 170-2 200 | FIXED
MOBILE
MOBILE-SATELLITE (space-to-Earth) 5.351A
5.388 5.389A 5.389F | | +| 1 980-2 010 | FIXED
MOBILE
MOBILE-SATELLITE (Earth-to-space) 5.351A
5.388 5.389A 5.389B 5.389F | | +| 5.351A: For the use of the bands 1 518-1 544 MHz, 1 545-1 559 MHz, 1 610-1 645.5 MHz, 1 646.5-1 660.5 MHz, 1 668-1 675 MHz, 1 980-2 010 MHz, 2 170-2 200 MHz, 2 483.5-2 520 MHz and 2 670-2 690 MHz by the mobile satellite service, see Resolutions 212 (Rev.WRC-07)* and 225 (Rev.WRC-07)**.
* This Resolution was revised by WRC-15 and WRC-19.
** This Resolution was revised by WRC-12. | | | +| 5.388: The frequency bands 1 885-2 025 MHz and 2 110-2 200 MHz are intended for use, on a worldwide basis, by administrations wishing to implement International Mobile Telecommunications (IMT). Such use does not preclude the use of these frequency bands by other services to which they are allocated. The frequency bands should be made available for IMT in accordance with Resolution 212 (Rev.WRC-15)* (see also Resolution 223 (Rev.WRC-15)*). (WRC-15)
* This Resolution was revised by WRC-19. | | | +| 5.389A: The use of the bands 1 980-2 010 MHz and 2 170-2 200 MHz by the mobile-satellite service is subject to coordination under No. 9.11A and to the provisions of Resolution 716 (Rev.WRC-2000)**.
** This Resolution was revised by WRC-12. | | | +| 5.389B: The use of the frequency band 1 980-1 990 MHz by the mobile-satellite service shall not cause harmful interference to or constrain the development of the fixed and mobile services in Argentina, Brazil, Canada, Chile, Ecuador, the United States, Honduras, Jamaica, Mexico, Paraguay, Peru, Suriname, Trinidad and Tobago, Uruguay and Venezuela. (WRC-19) | | | +| 5.389F: In Algeria, Cape Verde, Egypt, Iran (Islamic Republic of), Mali, Syrian Arab Republic and Tunisia, the use of the frequency bands 1 980-2 010 MHz and 2 170-2 200 MHz by the mobile-satellite service shall neither cause harmful interference to the fixed and mobile services, nor hamper the development of those services prior to 1 January 2005, nor shall the former service request protection from the latter services. (WRC-19) | | | + +Following Figure 5.2.1-1 gives an overview of the NR TN bands adjacent to the NTN n256 band. + +![Figure 5.2.1-1: Adjacent TN bands to NTN band n256. The diagram shows frequency bands from 1880 MHz to 2210 MHz. On the left (UL), bands n2, n25, n39, n98 SUL, n84 SUL, n1, n65, n256, n34, and n70 are shown. On the right (DL), bands n1, n65, n256, and n66 are shown. The n256 band is highlighted in yellow, spanning from approximately 1980 MHz to 2010 MHz.](98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg) + +The figure illustrates the frequency spectrum for NTN band n256 and its adjacent terrestrial (TN) bands. The spectrum is divided into two main sections: the Uplink (UL) on the left and the Downlink (DL) on the right. The UL section shows bands n2, n25, n39, n98 SUL, n84 SUL, n1, n65, n256, n34, and n70. The DL section shows bands n1, n65, n256, and n66. The n256 band is highlighted in yellow, spanning from approximately 1980 MHz to 2010 MHz. The n1 band is shown in orange, n65 in green, n2 in blue, n25 in red, n39 in orange, n98 SUL in light blue, n84 SUL in pink, n34 in brown, and n70 in purple. The n66 band is shown in yellow. + +Figure 5.2.1-1: Adjacent TN bands to NTN band n256. The diagram shows frequency bands from 1880 MHz to 2210 MHz. On the left (UL), bands n2, n25, n39, n98 SUL, n84 SUL, n1, n65, n256, n34, and n70 are shown. On the right (DL), bands n1, n65, n256, and n66 are shown. The n256 band is highlighted in yellow, spanning from approximately 1980 MHz to 2010 MHz. + +**Figure 5.2.1-1: Adjacent TN bands to NTN band n256** + +As shown in Figure 5.2.1-1, the NTN satellite band is adjacent to NR bands n1 (FDD) and n34 (TDD). The bands need to be protected and co-existence analysis is required to determine the Adjacent Channel Interference Ratio (ACIR) and in-band power levels. + +Also, the NTN band n256 will fully be overlapped by TN NR bands n65 and partly overlapped by TN NR bands n2, n25, n70 and n66, limiting band n256 deployment accordingly to countries where n2, n25 and/or n70 are not deployed or regional regulation applies. + +Per ECC Decision 06(09) [4], n256 and Complementary Ground Component (CGC) could operate simultaneously in the upper 30 MHz portion of n65 in CEPT countries. + +### 5.2.2 NTN Satellite band: UL 1626.5–1660.5 MHz / DL 1525–1559 MHz + +The ITU-R Radio Regulations [3] specify the following service allocation for frequency ranges 1525 – 1559 MHz and 1626.5 – 1660.5 MHz as shown in Table 5.2.2-1. + +**Table 5.2.2-1: Allocation of 1525 –1559 MHz and 1626.5 – 1660.5 MHz in the ITU-R Radio Regulations** + +| Allocation to services | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Region 1 | Region 2 | Region 3 | +| 1 525-1 530
SPACE OPERATION
(space-to-Earth)
FIXED
MOBILE-SATELLITE
(space-to-Earth) 5.208B 5.351A
Earth exploration-satellite
Mobile except aeronautical mobile
5.349
5.341 5.342 5.350 5.351
5.352A 5.354 | 1 525-1 530
SPACE OPERATION
(space-to-Earth)
MOBILE-SATELLITE
(space-to-Earth) 5.208B 5.351A
Earth exploration-satellite
Fixed
Mobile 5.343

5.341 5.351 5.354 | 1 525-1 530
SPACE OPERATION
(space-to-Earth)
FIXED
MOBILE-SATELLITE
(space-to-Earth) 5.208B 5.351A
Earth exploration-satellite
Mobile 5.349

5.341 5.351 5.352A 5.354 | +| 1 530-1 535
SPACE OPERATION
(space-to-Earth)
MOBILE-SATELLITE
(space-to-Earth) 5.208B 5.351A
5.353A
Earth exploration-satellite
Fixed
Mobile except aeronautical mobile
5.341 5.342 5.351 5.354 | 1 530-1 535
SPACE OPERATION (space-to-Earth)
MOBILE-SATELLITE (space-to-Earth) 5.208B 5.351A 5.353A
Earth exploration-satellite
Fixed
Mobile 5.343

5.341 5.351 5.354 | | +| 1 535-1 559 | MOBILE-SATELLITE (space-to-Earth) 5.208B 5.351A
5.341 5.351 5.353A 5.354 5.355 5.356 5.357 5.357A 5.359 5.362A | | +| 1 626.5-1 660 | MOBILE-SATELLITE (Earth-to-space) 5.351A
5.341 5.351 5.353A 5.354 5.355 5.357A 5.359 5.362A 5.374 5.375 5.376 | | +| 1 660-1 660.5 | MOBILE-SATELLITE (Earth-to-space) 5.351A
RADIO ASTRONOMY
5.149 5.341 5.354 5.362A 5.376A | | +| The details of the notes 5.208B, 5.341, 5.342, 5.350, 5.351, 5.351A, 5.352A, 5.353A, 5.354, 5.355, 5.356, 5.357, 5.357A, 5.359, 5.362A, 5.374, 5.375 and 5.376A related to MOBILE-SATELLITE service can be found in [3]. | | | + +FCC's specifies the following service allocation for frequency ranges 1525 – 1559 MHz and 1626.5 – 1660.5 MHz in USA[20] as shown in Table 5.2.2-2. + +Table 5.2.2-2: Allocation of 1525 –1559 MHz and 1626.5 – 1660.5 MHz in the US + +| Allocation to services | | | +|------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------| +| Federal Table | Non-Federal Table | FCC Rule Part(2) | +| 1525-1535
MOBILE-SATELLITE (space-to-Earth) US315 US380
5.341 5.351 | | Satellite Communications (25)
Maritime (80) | +| 1535-1559
MOBILE-SATELLITE (space-to-Earth) US308 US309 US315 US380
5.341 5.351 5.356 | | Satellite Communications (25)
Maritime (80)
Aviation (87) | +| 1626.5-1660
MOBILE-SATELLITE (Earth-to-space) US308 US309 US315 US380
5.341 5.351 5.375 | | Satellite Communications (25)
Maritime (80)
Aviation (87) | +| 1660-1660.5
MOBILE-SATELLITE (Earth-to-space) US308 US309 US380
RADIO ASTRONOMY
5.341 5.351 US342 | | Satellite Communications (25)
Aviation (87) | + +The details of the notes 5.341, 5.351, 5.356, 5.375, US308, US309, US315 and US342 related to MOBILE-SATELLITE service can be found in [20]. + +US380 In the bands 1525-1544 MHz, 1545-1559 MHz, 1610-1645.5 MHz, 1646.5-1660.5 MHz, and 2483.5-2500 MHz, a non-Federal licensee in the mobile-satellite service (MSS) may also operate an ancillary terrestrial component in conjunction with its MSS network, subject to the Commission's rules for ancillary terrestrial components and subject to all applicable conditions and provisions of its MSS authorization. + +![Figure 5.2.2-1: Adjacent TN bands to NTN band n255. The diagram shows a frequency spectrum from 1470 MHz to 1710 MHz. On the left, various terrestrial (TN) bands are shown: n50 TD (orange), n75 DL (light green), n92 DL (green), n94 DL (purple), n74 DL (yellow), 11 DL (grey), and 21 DL (grey). In the center, the NTN band n255 is shown, which includes n255 DL (yellow), n24 DL* (light yellow), and n255 UL (yellow). To the right of n255, the NTN band n255 UL (yellow) is shown, which includes n24 UL* (light yellow) and n99 SUL* (orange). On the far right, the TN band n70 UL (blue) is shown. The diagram illustrates the frequency allocation and adjacency of these bands.](1145fc59efdc7dacc8d3c715d7ff3248_img.jpg) + +Figure 5.2.2-1: Adjacent TN bands to NTN band n255. The diagram shows a frequency spectrum from 1470 MHz to 1710 MHz. On the left, various terrestrial (TN) bands are shown: n50 TD (orange), n75 DL (light green), n92 DL (green), n94 DL (purple), n74 DL (yellow), 11 DL (grey), and 21 DL (grey). In the center, the NTN band n255 is shown, which includes n255 DL (yellow), n24 DL\* (light yellow), and n255 UL (yellow). To the right of n255, the NTN band n255 UL (yellow) is shown, which includes n24 UL\* (light yellow) and n99 SUL\* (orange). On the far right, the TN band n70 UL (blue) is shown. The diagram illustrates the frequency allocation and adjacency of these bands. + +NOTE: DL operation in band n24 is restricted to 1526-1536MHz and UL operation is restricted to 1627.5-1637.5MHz and 1646.5-1656.5MHz + +Figure 5.2.2-1: Adjacent TN bands to NTN band n255 + +As shown in Figure 5.2.2-1, the NTN satellite band is not adjacent to any TN NR or LTE bands. The edge-to-edge separation for nearest TN band, n74 DL, is 7 MHz. + +Also, the NTN band n255 fully overlaps with TN NR bands n24 and SUL NR band n99. Per note US380 in Table 5.2.2-2 simultaneous operation of n24/n99 and n255 is allowed in USA. Commission's authorization and technical rules for TN can be found in FCC Orders 03-15 [21] and 20-48 [22] respectively. Commission's technical rules for its MSS authorization can be found in FCC 47 C.F.R Part 25. + +Technical rules for NTN SAN and UEs operating in 1 to 3 GHz from FCC's 47 C.F.R. § 25.202 [23] are summarized below: + +47 C.F.R. § 25.202: + +(d) *Frequency tolerance, Earth stations.* The carrier frequency of each earth station transmitter authorized in these services shall be maintained within 0.001 percent of the reference frequency. + +(e) *Frequency tolerance, space stations.* The carrier frequency of each space station transmitter authorized in these services shall be maintained within 0.002 percent of the reference frequency. + +###### 47 C.F.R. § 25.202 (f): + +*Emission limitations.* Except for SDARS terrestrial repeaters and as provided for in paragraph (i), the mean power of emissions shall be attenuated below the mean output power of the transmitter in accordance with the schedule set forth in paragraphs (f)(1) through (f)(4) of this section. The out-of-band emissions of SDARS terrestrial repeaters shall be attenuated in accordance with the schedule set forth in paragraph (h) of this section. + +- (1) In any 4 kHz band, the center frequency of which is removed from the assigned frequency by more than 50 percent up to and including 100 percent of the authorized bandwidth: 25 dB; +- (2) In any 4 kHz band, the center frequency of which is removed from the assigned frequency by more than 100 percent up to and including 250 percent of the authorized bandwidth: 35 dB; +- (3) In any 4 kHz band, the center frequency of which is removed from the assigned frequency by more than 250 percent of the authorized bandwidth: An amount equal to 43 dB plus 10 times the logarithm (to the base 10) of the transmitter power in watts; +- (4) In any event, when an emission outside of the authorized bandwidth causes harmful interference, the Commission may, at its discretion, require greater attenuation than specified in paragraphs (f) (1), (2) and (3) of this section. + +###### 47 C.F.R. § 25.216: + +- (a) The e.i.r.p. density of emissions from mobile earth stations placed in service on or before July 21, 2002 with assigned uplink frequencies between 1610 MHz and 1660.5 MHz shall not exceed -70 dBW/MHz, averaged over any 2 millisecond active transmission interval, in the band 1559-1587.42 MHz. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth generated by such stations shall not exceed -80 dBW, averaged over any 2 millisecond active transmission interval, in that band. +- (b) The e.i.r.p. density of emissions from mobile earth stations placed in service on or before July 21, 2002 with assigned uplink frequencies between 1610 MHz and 1626.5 MHz shall not exceed -64 dBW/MHz, averaged over any 2 millisecond active transmission interval, in the band 1587.42-1605 MHz. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth generated by such stations shall not exceed -74 dBW, averaged over any 2 millisecond active transmission interval, in the 1587.42-1605 MHz band. +- (c) The e.i.r.p. density of emissions from mobile earth stations placed in service after July 21, 2002 with assigned uplink frequencies between 1610 MHz and 1660.5 MHz shall not exceed -70 dBW/MHz, averaged over any 2 millisecond active transmission interval, in the band 1559-1605 MHz. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations shall not exceed -80 dBW, averaged over any 2 millisecond active transmission interval, in the 1559-1605 MHz band. +- (d) As of January 1, 2005, the e.i.r.p. density of emissions from mobile earth stations placed in service on or before July 21, 2002 with assigned uplink frequencies between 1610 MHz and 1660.5 MHz (except Standard A and B Inmarsat terminals used as Global Maritime Distress and Safety System ship earth stations) shall not exceed -70dBW/MHz, averaged over any 2 millisecond active transmission interval, in the 1559-1605 MHz band. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations shall not exceed -80 dBW, averaged over any 2 millisecond active transmission interval, in the 1559-1605 MHz band. Standard A Inmarsat terminals used as Global Maritime Distress and Safety System ship earth stations that do not meet the e.i.r.p. density limits specified in this paragraph may continue operation until December 31, 2007. Inmarsat-B terminals manufactured more than six months after Federal Register publication of the rule changes adopted in FCC 03-283 must meet these limits. Inmarsat B terminals manufactured before then are temporarily grandfathered under the condition that no interference is caused by these terminals to aeronautical satellite radio-navigation systems. The full-compliance deadline for grandfathered Inmarsat-B terminals is December 31, 2012. +- (e) The e.i.r.p density of emissions from mobile earth stations with assigned uplink frequencies between 1990 MHz and 2025 MHz shall not exceed -70 dBW/MHz, averaged over any 2 millisecond active transmission interval, in frequencies between 1559 MHz and 1610 MHz. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations between 1559 MHz and 1605 MHz shall not exceed -80 dBW, averaged over any 2 millisecond + +active transmission interval. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations between 1605 MHz and 1610 MHz manufactured more than six months after Federal Register publication of the rule changes adopted in FCC 03-283 shall not exceed $-80$ dBW, averaged over any 2 millisecond active transmission interval. + +(f) Mobile earth stations placed in service after July 21, 2002 with assigned uplink frequencies in the 1610-1660.5 MHz band shall suppress the power density of emissions in the 1605-1610 MHz band to an extent determined by linear interpolation from $-70$ dBW/MHz at 1605 MHz to $-10$ dBW/MHz at 1610 MHz. + +(g) Mobile earth stations manufactured more than six months after Federal Register publication of the rule changes adopted in FCC 03-283 with assigned uplink frequencies in the 1610-1626.5 MHz band shall suppress the power density of emissions in the 1605-1610 MHz band-segment to an extent determined by linear interpolation from $-70$ dBW/MHz at 1605 MHz to $-10$ dBW/MHz at 1610 MHz averaged over any 2 millisecond active transmission interval. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations shall not exceed a level determined by linear interpolation from $-80$ dBW at 1605 MHz to $-20$ dBW at 1610 MHz, averaged over any 2 millisecond active transmission interval. + +(h) Mobile earth stations manufactured more than six months after Federal Register publication of the rule changes adopted in FCC 03-283 with assigned uplink frequencies in the 1626.5-1660.5 MHz band shall suppress the power density of emissions in the 1605-1610 MHz band-segment to an extent determined by linear interpolation from $-70$ dBW/MHz at 1605 MHz to $-46$ dBW/MHz at 1610 MHz, averaged over any 2 millisecond active transmission interval. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations shall not exceed a level determined by linear interpolation from $-80$ dBW at 1605 MHz to $-56$ dBW at 1610 MHz, averaged over any 2 millisecond active transmission interval. + +(i) The e.i.r.p. density of carrier-off state emissions from mobile earth stations manufactured more than six months after Federal Register publication of the rule changes adopted in FCC 03-283 with assigned uplink frequencies between 1 and 3 GHz shall not exceed $-80$ dBW/MHz in the 1559-1610 MHz band averaged over any two millisecond interval. + +(j) A Root-Mean-Square detector shall be used for all power density measurements. + +For L-band NTN satellite operation in the US, additional spectrum emission requirements in 47 C.F.R. § 25.216 (h) need to be specified for L-band NTN satellite UE. This can be captured as part of additional spurious emission requirements which allows inclusion of frequency ranges that are less than $F_{\text{OOB}}$ (MHz) from the edge of the channel bandwidth. + +### 5.2.3 NTN Satellite band: UL 27.5-30.0 GHz / DL 17.3-20.2 GHz + +#### 5.2.3.1 ITU-R + +The ITU-R Radio Regulations [3] specify the following service allocation for those frequency ranges, shown in Table 5.2.3.1-1: + +**Table 5.2.3.1-1: Allocation of 17.3-20.2 GHz and 27.5-30.0 GHz in the ITU-R Radio Regulations** + +| Allocation to services | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Region 1 | Region 2 | Region 3 | +| 17.3-17.7
FIXED-SATELLITE
(Earth-to-space) 5.516
(space-to-Earth) 5.516A 5.516B
Radiolocation
5.514 | 17.3-17.7
FIXED-SATELLITE
(Earth-to-space) 5.516
BROADCASTING-SATELLITE
Radiolocation
5.514 5.515 | 17.3-17.7
FIXED-SATELLITE
(Earth-to-space) 5.516
Radiolocation
5.514 | +| 17.7-18.1
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.484A 5.517A
(Earth-to-space) 5.516
MOBILE | 17.7-17.8
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.517 5.517A
(Earth-to-space) 5.516
BROADCASTING-SATELLITE
Mobile
5.515
17.8-18.1
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.484A 5.517A
(Earth-to-space) 5.516
MOBILE
5.519 | 17.7-18.1
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.484A 5.517A
(Earth-to-space) 5.516
MOBILE | +| 18.1-18.4 FIXED
FIXED-SATELLITE (space-to-Earth) 5.484A 5.516B 5.517A
(Earth-to-space) 5.520
MOBILE
5.519 5.521 | | | +| 18.4-18.6 FIXED
FIXED-SATELLITE (space-to-Earth) 5.484A 5.516B 5.517A
MOBILE | | | +| 18.6-18.8
EARTH EXPLORATION-SATELLITE
(passive)
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.517A 5.522B
MOBILE except aeronautical
mobile
Space research (passive)
5.522A 5.522C | 18.6-18.8
EARTH EXPLORATION-
SATELLITE (passive)
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.516B 5.517A
5.522B
MOBILE except aeronautical mobile
SPACE RESEARCH (passive)
5.522A | 18.6-18.8
EARTH EXPLORATION-SATELLITE
(passive)
FIXED
FIXED-SATELLITE
(space-to-Earth) 5.517A 5.522B
MOBILE except aeronautical
mobile
Space research (passive)
5.522A | +| 18.8-19.3 FIXED
FIXED-SATELLITE (space-to-Earth) 5.516B 5.517A 5.523A
MOBILE | | | +| 19.3-19.7 FIXED
FIXED-SATELLITE (space-to-Earth) (Earth-to-space) 5.517A 5.523B
5.523C 5.523D 5.523E
MOBILE | | | +| 19.7-20.1
FIXED-SATELLITE
(space-to-Earth) 5.484A 5.484B
5.516B 5.527A
Mobile-satellite (space-to-Earth) | 19.7-20.1
FIXED-SATELLITE
(space-to-Earth) 5.484A 5.484B
5.516B 5.527A
MOBILE-SATELLITE
(space-to-Earth)
5.524 5.525 5.526 5.527 5.528
5.529 | 19.7-20.1
FIXED-SATELLITE
(space-to-Earth) 5.484A 5.484B
5.516B 5.527A
Mobile-satellite (space-to-Earth) | +| 5.524 | 5.524 5.525 5.526 5.527 5.528
5.529 | 5.524 | +| 20.1-20.2 FIXED-SATELLITE (space-to-Earth) 5.484A 5.484B 5.516B 5.527A
MOBILE-SATELLITE (space-to-Earth)
5.524 5.525 5.526 5.527 5.528 | | | +| 27.5-28.5 FIXED 5.537A
FIXED-SATELLITE (Earth-to-space) 5.484A 5.516B 5.517A 5.539
MOBILE
5.538 5.540 | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 28.5-29.1 FIXED
FIXED-SATELLITE (Earth-to-space) 5.484A 5.516B 5.517A 5.523A 5.539
MOBILE
Earth exploration-satellite (Earth-to-space) 5.541
5.540 | | | +| 29.1-29.5 FIXED
FIXED-SATELLITE (Earth-to-space) 5.516B 5.517A 5.523C 5.523E 5.535A 5.539 5.541A
MOBILE
Earth exploration-satellite (Earth-to-space) 5.541
5.540 | | | +| 29.5-29.9
FIXED-SATELLITE
(Earth-to-space) 5.484A 5.484B
5.516B 5.527A 5.539
Earth exploration-satellite
(Earth-to-space) 5.541
Mobile-satellite (Earth-to-space)
5.540 5.542 | 29.5-29.9
FIXED-SATELLITE
(Earth-to-space) 5.484A 5.484B
5.516B 5.527A 5.539
MOBILE-SATELLITE
(Earth-to-space)
Earth exploration-satellite
(Earth-to-space) 5.541
5.525 5.526 5.527 5.529 5.540 | 29.5-29.9
FIXED-SATELLITE
(Earth-to-space) 5.484A 5.484B
5.516B 5.527A 5.539
Earth exploration-satellite
(Earth-to-space) 5.541
Mobile-satellite (Earth-to-space)
5.540 5.542 | +| 29.9-30.0 FIXED-SATELLITE (Earth-to-space) 5.484A 5.484B 5.516B 5.527A 5.539
MOBILE-SATELLITE (Earth-to-space)
Earth exploration-satellite (Earth-to-space) 5.541 5.543
5.526 5.527 5.538 5.540 5.542 | | | + +In addition: + +- WRC-15 authorized ESIM operations in 19.7-20.2 GHz (space-to-Earth) and 29.5-30.0 GHz (Earth-to-space) under certain conditions, and for GSO systems only. +- WRC-19 authorized ESIM operations in 17.7-19.7 GHz (space-to-Earth) and 27.5-29.5 GHz (Earth-to-space) under certain conditions, and for GSO systems only (Resolution 173). *Editor's note: This TR would be updated with WRC-23 outcomes (Agenda Item 1.16 on NGSO ESIM Ka band).* + +#### 5.2.3.2 FCC + +In 2016, FCC issued Report and Order FCC 16-89 [33] allocating the 27.50-28.35 GHz frequency range for terrestrial licensed mobile operations (IMT 5G). This frequency range corresponds to the 3GPP band n261. + +In 2020, FCC issued Report and Order FCC 20-159 [34] which streamlines part 25 rules that govern the licensing of satellite space and earth stations in a satellite system through a unified license. The unified licensing framework specified frequency bands which includes: + +- Space-to-Earth: + - For GSO: 18.3-18.8 GHz and 19.7-20.2 GHz + - For NGSO: 17.8-18.6 GHz, 18.8-19.4 GHz and 19.6-20.2 GHz +- Earth-to-space: + - For GSO: 28.35-29.1 GHz and 29.25-30.0 GHz. + - For NGSO: 28.35-29.1 GHz and 29.5-30.0 GHz. + +In 2020 as well, FCC issued the Report and Order FCC-20-66 [35] which facilitates the deployment of, and reduce the regulatory burdens on, Earth Stations in Motion (ESIMs). It allows ESIMs to communicate in additional frequency bands with GSO satellites operating in FSS bands and adopts rules for ESIMs to communicate with NGSO satellites in specific FSS bands. Those FSS bands include: + +- Space-to-Earth: + - For GSO: 17.8-19.4 GHz, 19.6-20.2 GHz. + +- For NGSO: 17.8-18.6 GHz, 18.8-19.4 GHz, 19.6-20.2 GHz +- Earth-to-space: + - For GSO: 28.35-29.1 GHz and 29.25-30.0 GHz. + - For NGSO: 28.4-29.1 GHz and 29.5-30.0 GHz. + +#### 5.2.3.3 CEPT + +The ECC Decision (05)01 [36] addresses the use of band 27.5-29.5GHz, regulated for Fixed Service and Fixed Satellite Service: + +- The bands 27.5-27.8285 GHz, 28.4445-28.8365 GHz and 29.4525-29.5 GHz are designated for the use of uncoordinated FSS earth stations. +- The band 28.8365-28.9485 GHz is designated for the use of uncoordinated FSS earth stations, considering, until 1 January 2020, the legacy FS systems licensed in this band in some countries before 18 March 2005. +- The bands 27.8285-28.4445 GHz and 28.9485-29.4525 GHz are designated for the use of FS systems. + +Also, this ECC Decision(05)01 states that the CEPT administrations shall not authorize the deployment of uncoordinated FSS earth stations in the bands designed for the use of FS systems. + +![Figure 5.2.3.3-1: ECC Decision(05)01 - 27.5-29.5 band segmentation. This diagram illustrates the frequency band segmentation from 27.5 GHz to 29.5 GHz. The top section shows 'Band segmentation' with 32 FS channels (numbered 1-32) and 112 MHz total width. The bottom section shows the frequency bands: 27.5 GHz to 27.8285 GHz (FSS (328.5 MHz)), 27.8285 GHz to 28.4445 GHz (No FS stations), 28.4445 GHz to 28.8365 GHz (FSS (504 MHz)), 28.8365 GHz to 28.9485 GHz (No FS stations), 28.9485 GHz to 29.4525 GHz (FSS (47.5 MHz)), and 29.4525 GHz to 29.5 GHz (No FS stations). The diagram also indicates 'FS unpaired band (112 MHz)', 'FS paired band (504 MHz)', and 'FSS (see decision 2)'.](47e75dc9e83054b2dac3df8bf3e57019_img.jpg) + +Figure 5.2.3.3-1: ECC Decision(05)01 - 27.5-29.5 band segmentation. This diagram illustrates the frequency band segmentation from 27.5 GHz to 29.5 GHz. The top section shows 'Band segmentation' with 32 FS channels (numbered 1-32) and 112 MHz total width. The bottom section shows the frequency bands: 27.5 GHz to 27.8285 GHz (FSS (328.5 MHz)), 27.8285 GHz to 28.4445 GHz (No FS stations), 28.4445 GHz to 28.8365 GHz (FSS (504 MHz)), 28.8365 GHz to 28.9485 GHz (No FS stations), 28.9485 GHz to 29.4525 GHz (FSS (47.5 MHz)), and 29.4525 GHz to 29.5 GHz (No FS stations). The diagram also indicates 'FS unpaired band (112 MHz)', 'FS paired band (504 MHz)', and 'FSS (see decision 2)'. + +Figure 5.2.3.3-1: ECC Decision(05)01 - 27.5-29.5 band segmentation + +The ECC Decision(13)01 [37] specifies the harmonized use, free circulation, and exemption from individual licensing of Earth stations on mobile platforms (ESOMPs) within the ranges 17.3-20.2 GHz and 27.5-30.0 GHz, in the portion identified for their use within the territory of operation, and under the conditions specified in Annexes 1, 2 and 3 of this ECC Decision. ESOMPs are terminals with small directional antennas for the provision of broadband communication services. The terminals may be mounted on aircraft, ships or land vehicles or may be transportable devices used in motion or at temporary halts. This ECC Decision also specifies the conditions for those ESOMP devices to operate. + +## 5.3 Regulatory aspects for HAPS + +ITU-R began to study HAPS in the 1990s initially for fixed services. The telecommunications ecosystem and technology enablers for HAPS have evolved significantly since then. At WRC-2000, the bands 1885 – 1980 MHz, 2010 – 2025 MHz and 2110 – 2170 MHz were identified for HAPS operating as IMT Base Stations, in accordance with Resolution 221 (Rev.WRC-07) [3]. With increasing interest in HAPS to offer mobile services, the WRC-19 agreed to study certain frequency bands which have been already identified for IMT below 2.7 GHz for HAPS as IMT Base Stations (HIBS). ITU-R Working Party 5D is currently studying co-existence requirements for HIBS in the additional three bands listed in Table 5.4-1 to support spectrum identification decisions in WRC-23 in accordance with Resolution 247 (WRC-19) [3]. + +NOTE: In the current ITU terminology, the use of HAPS to implement IMT (i.e. offer mobile wireless services) is referred to as “HAPS as IMT Base Stations” or HIBS. + +**Table 5.4-1: Frequencies for HAPS as IMT Base Stations (HIBS).** + +| Region | Spectrum | Remarks | +|----------------|-------------------------------------------------------------------------------|------------------------------------------| +| Region 1 and 3 | 1885 – 1980 MHz
2010 – 2025 MHz
2110 – 2170 MHz | Identified HIBS designations at WRC-2000 | +| Region 2 | 1885 – 1980 MHz 3
2110 – 2160 MHz 4 | | +| Global | 694 – 960 MHz
1710 – 1885 MHz 1
2500 – 2690 MHz 2 | Under study, for decision at WRC-23 | + +NOTE 1: 1710-1815 MHz to be used for uplink only in Region 3. +NOTE 2: 2500-2535 MHz to be used for uplink only in Region 3, except 2655--2690 MHz in Region 3). +NOTE 3: In most of Region 2 1885-1910 is used for Mobile uplink and 1930-1980 is used for Mobile downlink. In the United States, 1910-1915 and 1915-1920 are also used for Mobile uplink. +NOTE 4: In Region 2 2110-2160 is used for Mobile downlink. + +# 6 Co-existence study + +## 6.1 Co-existence simulation scenario + +Scenarios for coexistence study are listed in Table 6.1-1. + +**Table 6.1-1: Scenarios for NTN-NTN/TN co-existence** + +| FR1: 2GHz | | NTN 1,4,5 | | | | | | | +|-------------|--------------------------|----------------------|-----------|------------|--------------------|-----------|------------|------| +| | | Set 1 | | | Set 2 2 | | | HAPS | +| | | GEO 3 | LEO 600km | LEO 1200km | GEO | LEO 600km | LEO 1200km | | +| NR / NB-IoT | Rural | X | X | X | X | X | X | X | +| | Urban macro | X | X | X | X | X | X | X | +| | Dense Urban 6 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | +| HAPS | | N/A | N/A | N/A | N/A | N/A | N/A | X | + +NOTE 1: Earth Fixed beam has been considered for co-existence studies. +NOTE 2: Use Set 1 satellite antenna has been used as the starting point for co-existence studies. +NOTE 3: GEO and LEO only operate at adjacent channel. +NOTE 4: Use GEO and LEO@600km when TN is victim. +NOTE 5: The satellite-to-satellite coexistence scenarios are not in the scope of this study considering this is already addressed by ITU (ITU RR Article 9 etc.) and regional regulations (e.g. FCC rules). +NOTE 6: Dense Urban is not considered as it is expected NTN UE will connect to terrestrial networks rather than satellite networks in such scenario. + +The aggressor and victim combinations are listed in Table 6.1-2. + +**Table 6.1-2: Aggressor and victim** + +| No. | Combination | Aggressor | Victim | Notes | Study Phase | +|-----|--------------|-----------|--------|--------------------------------------------------------------------------------------|-------------| +| 1 | TN with NTN | TN DL | NTN DL | Applicable for satellite operating in e.g. S-band, for e.g. coexistence with n1 FDD. | Phase 1 | +| 2 | TN with NTN | TN UL | NTN UL | Applicable for satellite operating in e.g. S-band, for e.g. coexistence with n1 FDD. | Phase 1 | +| 3 | TN with NTN | NTN DL | TN DL | Applicable for satellite operating in e.g. S-band, for e.g. coexistence with n1 FDD. | Phase 1 | +| 4 | TN with NTN | NTN UL | TN UL | Applicable for satellite operating in e.g. S-band, for e.g. coexistence with n1 FDD. | Phase 1 | +| 5 | TN with NTN | NTN UL | TN DL | Applicable for satellite operating in S-band, for e.g. coexistence with n34 TDD. | Phase 1 | +| 6 | TN with NTN | TN DL | NTN UL | Applicable for satellite operating in S-band, for e.g. coexistence with n34 TDD. | Phase 1 | +| 7 | NTN with NTN | NTN DL | NTN DL | HAPS-HAPS | Phase 2 | +| | | NTN UL | NTN UL | HAPS-HAPS | Phase 2 | + +For further visualisation, the interference charts with respect to scenarios 1 to 6 are further represented with respect to NTN-TN coexistence scenarios in Figure 6.1-1 (scenarios 1 to 4) and Figure 6.1-2 (scenarios 5 and 6). + +![Figure 6.1-1: S-band NTN-TN adjacent band coexistence scenarios with TN in FDD mode. The diagram shows a satellite in the sky and a terrestrial (TN) cell on the ground. The TN cell contains gNBs and UEs (some labeled TN UE*). The NTN cell contains UEs (NTN UE). Arrows indicate various interference paths: I1 (NTN UE to NTN UE in DL), I2 (Satellite to NTN UE in UL), I3 (NTN UE to TN UE in DL), I4 (NTN UE to TN UE in UL), and I5 (Satellite to TN UE in UL). Frequency band diagrams show the separation between TN 5G bands and NTN 5G bands in both uplink and downlink.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +Figure 6.1-1: S-band NTN-TN adjacent band coexistence scenarios with TN in FDD mode. The diagram shows a satellite in the sky and a terrestrial (TN) cell on the ground. The TN cell contains gNBs and UEs (some labeled TN UE\*). The NTN cell contains UEs (NTN UE). Arrows indicate various interference paths: I1 (NTN UE to NTN UE in DL), I2 (Satellite to NTN UE in UL), I3 (NTN UE to TN UE in DL), I4 (NTN UE to TN UE in UL), and I5 (Satellite to TN UE in UL). Frequency band diagrams show the separation between TN 5G bands and NTN 5G bands in both uplink and downlink. + +**Figure 6.1-1: S-band NTN-TN adjacent band coexistence scenarios with TN in FDD mode** + +![Figure 6.1-2: S-band NTN-TN adjacent band coexistence scenarios with TN in TDD mode (e.g. n34). This diagram is similar to Figure 6.1-1 but focuses on scenarios I5 and I6. It shows interference from an NTN UE to a TN UE in the downlink (I5) and from a satellite to a TN UE in the uplink (I6). Frequency band diagrams illustrate the TDD frame structure and the resulting interference between TN 5G and NTN 5G bands.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +Figure 6.1-2: S-band NTN-TN adjacent band coexistence scenarios with TN in TDD mode (e.g. n34). This diagram is similar to Figure 6.1-1 but focuses on scenarios I5 and I6. It shows interference from an NTN UE to a TN UE in the downlink (I5) and from a satellite to a TN UE in the uplink (I6). Frequency band diagrams illustrate the TDD frame structure and the resulting interference between TN 5G and NTN 5G bands. + +**Figure 6.1-2: S-band NTN-TN adjacent band coexistence scenarios with TN in TDD mode (e.g. n34)** + +The frequency and bandwidth are listed in Table 6.1-3. + +**Table 6.1-3: Proposed frequency and bandwidth for co-existence study** + +| | Frequency | Bandwidth | Duplex mode | Frequency reuse factor | +|----------------|-----------|------------------------|-------------|------------------------| +| TN Rural | 2 GHz | 20MHz | FDD, TDD | 1 | +| TN Urban macro | 2 GHz | 20MHz | FDD, TDD | 1 | +| GEO | 2 GHz | 5/10/15/20 MHz for FR1 | FDD | 1, 3 1 | +| LEO | 2 GHz | 5/10/15/20 MHz for FR1 | FDD | 1, 3 1 | +| HAPS | 2 GHz | TBD | FDD | 1 | + +NOTE: Only FRF=1 has been used in co-existence studies for simplification. + +## 6.2 Co-existence simulation assumption + +### 6.2.1 Network layout model + +#### 6.2.1.1 Co-existence between NTN satellite and TN + +Cellular cell structure is considered for both NTN satellite and TN network layout. + +Referring to TR 38.811[5] Section 6.3 and Annex A, a 3D global coordinate system is considered (Earth-Centred Earth Fixed) for simulating NTN satellite beams direction and location on the earth surface. It means the NTN satellite beam location, TN randomly dropping location are generated with a set of three parameters (x,y,z). + +Deployment of NTN satellite and TN cells and UEs for co-existence study is listed in Table 6.2.1.1-1. + +NOTE: The NTN UE(s) shall be dropped at the edge of the “central 19 TN cells (cluster)”. For Case 1 (Urban scenario), an Isolation distance of 1500m as 2\*ISD is considered to reflect the NTN-TN selection algorithm at the border, assuming TN connection will always be prioritized over NTN. + +As defined in Figure 6.2.1.1-1, isolation distance is the distance between the blue-dotted line which represents TN cell boarder and the red line. No UEs deployed in the isolation region is assumed to reduce the calculation complexity. + +![Figure 6.2.1.1-1: Isolation distance for Case 1. The diagram shows a cluster of 19 hexagonal cells (blue-shaded) surrounded by a dashed blue line representing the cell border. A red circle represents the NTN UE coverage area. The distance between the cell border and the red circle is labeled 'Isolation distance'. The distance from the center of the cluster to the cell border is labeled 'Cell range'. An arrow points to the red circle with the label 'NTN UE'.](4412857e90dfaa9a3df8836bcbde534b_img.jpg) + +Figure 6.2.1.1-1: Isolation distance for Case 1. The diagram shows a cluster of 19 hexagonal cells (blue-shaded) surrounded by a dashed blue line representing the cell border. A red circle represents the NTN UE coverage area. The distance between the cell border and the red circle is labeled 'Isolation distance'. The distance from the center of the cluster to the cell border is labeled 'Cell range'. An arrow points to the red circle with the label 'NTN UE'. + +**Figure 6.2.1.1-1: Isolation distance for Case 1** + +**Table 6.2.1.1-1: Network and UE deployment** + +| No. | Combination | Aggressor | Victim | Which NTN cell/UE to observe? | Which TN/UE to observe? | Which TN cells in a TN to observe? | +|-----|-----------------------|-----------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | TN with NTN satellite | TN DL | NTN DL | NTN cell:
Observe NTN central beam for SINR, 6 adjacent beams for inter-beam interference.

NTN UE:
NTN UEs dropped at the edge of TN clusters | One cluster with 19 TN cells (57 sectors) randomly placed in the central NTN beam | All active TN clusters which has the NTN UE(s) at its edge. | +| 2 | TN with NTN satellite | TN UL | NTN UL | NTN cell:
Observe NTN central beam for SINR, 6 adjacent beams for inter-beam interference.

NTN UE:
NTN UEs dropped at the edge of TN clusters | Consider an active rate of 20% for Rural and Urban of TN. | All active TN cells in central NTN beam | +| 3 | TN with NTN satellite | NTN DL | TN DL | NTN cell:
Nadir point.

NTN UE:
NTN UEs dropped outside or at the edge of TN clusters | TN clusters randomly placed in this NTN beam | All in central NTN beam | +| | | | | NTN cell:
NTN cell with satellite at low elevation (45° for GEO and LEO, Interested companies can bring analysis and results for other values)

NTN UE:
NTN UEs dropped outside or at the edge of TN clusters | TN clusters randomly placed in this NTN beam | | +| 4 | TN with NTN satellite | NTN UL | TN UL | NTN cell:
Nadir point.

NTN UE:
NTN UEs dropped at the edge of TN clusters | TN randomly placed in this NTN beam | Option 1: All active TN clusters which has the NTN UE(s) at its edge.

Option 2: Only the TN sectors which have NTN UE(s) at their edges.

Option 1 is the baseline and it is not precluded companies can follow Option 2 to bring results | +| 5 | TN with NTN satellite | NTN UL | TN DL | NTN cell:
Nadir point

NTN UE:
NTN UEs dropped at the edge of TN clusters | TN clusters randomly placed in this NTN beam | All active TN clusters which has the NTN UE(s) at its edge | + +| No. | Combination | Aggressor | Victim | Which NTN cell/UE to observe? | Which TN/UE to observe? | Which TN cells in a TN to observe? | +|-----|-----------------------|-----------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------| +| | | | | NTN cell:
NTN cell with satellite at low elevation (45° for GEO and LEO, Interested companies can bring analysis and results for other values).

NTN UE:
NTN UEs dropped at the edge of TN clusters | TN clusters randomly placed in this NTN beam | All active TN clusters which has the NTN UE(s) at its edge. | +| 6 | TN with NTN satellite | TN DL | NTN UL | NTN cell:
Observe NTN central beam for SINR, 6 adjacent beams for inter-beam interference.

NTN cell with satellite at low elevation to be further investigated.

NTN UE:
NTN UEs dropped outside or at the edge of TN clusters | Consider the active rate of 20% for Rural and Urban of TN.
The Urban TN deployment for GEO in Case 6 is a mixture of urban and rural TN deployment. A representative percentage of urban TN could be considered for further study. | All active TN cells in central NTN beam | + +#### 6.2.1.2 Co-existence between HAPS and TN + +For simulations of HAPS and TN co-existence, a cluster of TN cells is randomly dropped in the HAPS coverage area as shown in Figure 6.2.1.2-1. The TN cell cluster consists of 19 sites, 57 sectors, with the same assumption described in clause 6.2.2.4. HAPS coverage and cell layout are described in clause 6.2.2.3. + +![Figure 6.2.1.2-1: Simulation layout between HAPS and TN. The diagram shows a HAPS Network at the top with a coverage area represented by a large hexagon. Below it, a cluster of TN cells is shown, consisting of 19 sites (grey circles) and 57 sectors (smaller hexagons). A legend on the left indicates 'HAPS area' with a large hexagon and 'TN area' with a small hexagon. A circular inset on the right provides a detailed view of the TN cell cluster, showing the 19 sites and 57 sectors.](088921fa3f5a44c8551815122517eefd_img.jpg) + +Figure 6.2.1.2-1: Simulation layout between HAPS and TN. The diagram shows a HAPS Network at the top with a coverage area represented by a large hexagon. Below it, a cluster of TN cells is shown, consisting of 19 sites (grey circles) and 57 sectors (smaller hexagons). A legend on the left indicates 'HAPS area' with a large hexagon and 'TN area' with a small hexagon. A circular inset on the right provides a detailed view of the TN cell cluster, showing the 19 sites and 57 sectors. + +Figure 6.2.1.2-1: Simulation layout between HAPS and TN + +#### 6.2.1.3 Co-existence between HAPS and HAPS + +HAPS and HAPS co-existence can be characterized by “center-to-center” inter-system distance (i.e., the distance between two coverage centers) as depicted in Figure 6.2.1.3-1. Since HAPS location is at the center of its coverage area, the inter-system distance is the separation of the two HAPS. Different inter-system distances may be simulated to evaluate the interference caused by antenna gain variation in the elevation domain. + +![Figure 6.2.1.3-1: Simulation layout between HAPS and HAPS. The diagram shows two HAPS networks, each represented by a circle containing a hexagonal grid. A dashed line labeled 'Interference link' connects the two networks. A red double-headed arrow labeled 'Coverage center' (CC) is shown between the centers of the two networks. A blue double-headed arrow labeled 'Coverage edge' (CE) is shown between the edges of the two networks. A legend below the diagram identifies the symbols: blue double-headed arrow for Coverage edge (CE), red double-headed arrow for Coverage center (CC), solid black arrow for Service link, and dashed black arrow for Interference link.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Figure 6.2.1.3-1: Simulation layout between HAPS and HAPS. The diagram shows two HAPS networks, each represented by a circle containing a hexagonal grid. A dashed line labeled 'Interference link' connects the two networks. A red double-headed arrow labeled 'Coverage center' (CC) is shown between the centers of the two networks. A blue double-headed arrow labeled 'Coverage edge' (CE) is shown between the edges of the two networks. A legend below the diagram identifies the symbols: blue double-headed arrow for Coverage edge (CE), red double-headed arrow for Coverage center (CC), solid black arrow for Service link, and dashed black arrow for Interference link. + +Figure 6.2.1.3-1: Simulation layout between HAPS and HAPS + +### 6.2.2 System parameters + +#### 6.2.2.1 Satellite parameters + +Two sets of satellite parameters are listed in Table 6.2.2.1-2 and Table 6.2.2.1-3 according to TR 38.821[6]. + +The satellite max Tx power can be calculated by the equation as below: + +$$\max Tx\ power[dBm] = EIRP\ density\left[\frac{dBW}{MHz}\right] + 30 + 10 \log_{10}(N_{RB} * SCS[MHz] * 12) - Max\ Gain[dBi]$$ + +Table 6.2.2.1-1: $N_{RB}$ configuration per BandWidth size and SCS + +| Configuration FR1 S-band | $N_{RB}$ (5MHz BW) | $N_{RB}$ (10MHz BW) | $N_{RB}$ (15MHz BW) | $N_{RB}$ (20MHz BW) | +|--------------------------|--------------------|---------------------|---------------------|---------------------| +| SCS 15 kHz | 25 | 52 | 79 | 106 | +| SCS 30 kHz | 11 | 24 | 38 | 51 | + +Table 6.2.2.1-2: Set-1 satellite parameters for co-existence study + +| | | | | | | | | | | | | | | +|---------------------------------------------------------------------|---------------|-----------------------|---------------|------------------------|---------------|------------------------|-------|-------|-------|-------|-------|-------|-------| +| Satellite orbit | GEO | | LEO-1200 | | LEO-600 | | | | | | | | | +| Satellite altitude | 35786 km | | 1200 km | | 600 km | | | | | | | | | +| Payload characteristics for DL transmissions | | | | | | | | | | | | | | +| Satellite EIRP density | 59 dBW/MHz | | 40 dBW/MHz | | 34 dBW/MHz | | | | | | | | | +| Satellite max TX power in dBm | BW (MHz) | 5 | 10 | 15 | 20 | 5 | 10 | 15 | 20 | 5 | 10 | 15 | 20 | +| | SCS 15kHz | 44.53 | 47.71 | 49.53 | 50.81 | 46.53 | 49.71 | 51.53 | 52.81 | 40.53 | 43.71 | 45.53 | 46.81 | +| | SCS 30kHz | 43.98 | 47.37 | 49.36 | 50.64 | 45.98 | 49.37 | 51.36 | 52.64 | 39.98 | 43.37 | 45.36 | 46.64 | +| Satellite Tx max Gain | 51 dBi | | 30 dBi | | 30 dBi | | | | | | | | | +| Channel bandwidth | 5/10/15/20MHz | | 5/10/15/20MHz | | 5/10/15/20MHz | | | | | | | | | +| 3dB beamwidth or HPBW (Half-Power BandWidth) of main central beam | 2GHz | 0.4011 deg | | 4.4127 deg | | 4.4127 deg | | | | | | | | +| ABS (Adjacent Beam Spacing) of adjacent beams from the central beam | | 0.3474 deg | | 3.8206 deg | | 3.8206 deg | | | | | | | | +| Satellite beam diameter | 2 GHz | 250 km | | 90 km | | 50 km | | | | | | | | +| Payload characteristics for UL transmissions | | | | | | | | | | | | | | +| G/T | | 19 dB K -1 | | 1.1 dB K -1 | | 1.1 dB K -1 | | | | | | | | +| Satellite Rx max Gain | 2 GHz | 51 dBi | | 30 dBi | | 30 dBi | | | | | | | | + +Table 6.2.2.1-3: Set-2 satellite parameters for co-existence study + +| | | | | | +|----------------------------------------------|-------|-----------------------|-------------------------|-------------------------| +| Satellite orbit | | GEO | LEO-1200 | LEO-600 | +| Satellite altitude | | 35786 km | 1200 km | 600 km | +| Payload characteristics for DL transmissions | | | | | +| Satellite EIRP density | 2GHz | 53.5 dBW/MHz | 34 dBW/MHz | 28 dBW/MHz | +| Satellite Tx max Gain | | 45.5 dBi | 24 dBi | 24 | +| Channel bandwidth | | 5/10/15/20MHz | 5/10/15/20MHz | 5/10/15/20MHz | +| 3dB beamwidth | | 0.7353 deg | 8.8320 deg | 8.8320 deg | +| Satellite beam diameter | | 450 km | 190 km | 90 km | +| Payload characteristics for UL transmissions | | | | | +| G/T | 2 GHz | 14 dB K -1 | -4.9 dB K -1 | -4.9 dB K -1 | +| Satellite Rx max Gain | | 45.5 dBi | 24 dBi | 24 dBi | + +Table 6.2.2.1-4: Other parameters for NTN satellite + +| Parameters | NTN satellite | Remark | +|----------------------------------|----------------------------------------------------|--------------| +| Carrier frequency | 2GHz | | +| The number of active UE (UL) | 9 UEs and 2RBs per UE for GEO and LEO 1 | NOTE | +| The number of active UE (DL) | 1 | Same with TN | +| Traffic model | Full buffer | | +| DL power control | NO | | +| UL power control | See Session 6.2.6.2 | | +| NTN satellite Noise Figure in dB | See Table 2.3-3-1 | | +| Handover margin | 3dB | | + +NOTE: UEs are equally splitted inside the channel bandwidth into ACIR 3 regions. Scheduled PRB position for UE1 per satellite beam should be also fully aligned to simulate the worst case for co-channel interference and this is also aligned with full buffer case. + +![Diagram illustrating the distribution of User Equipment (UE) across ACIR regions and beams. The diagram shows three ACIR regions (ACIR region 1, ACIR region 2, ACIR region 3) and multiple beams (Beam 1, Beam 2, ..., Beam 7). UE 1 and UE 2 are shown in ACIR region 1, and UE 9 is shown in ACIR region 3. A '2 RB' label indicates the bandwidth allocation for a UE. Vertical lines represent the scheduled PRB positions for each UE across the beams, showing alignment within each beam.](f2ea0f64a770b22b902820457d262265_img.jpg) + +Diagram illustrating the distribution of User Equipment (UE) across ACIR regions and beams. The diagram shows three ACIR regions (ACIR region 1, ACIR region 2, ACIR region 3) and multiple beams (Beam 1, Beam 2, ..., Beam 7). UE 1 and UE 2 are shown in ACIR region 1, and UE 9 is shown in ACIR region 3. A '2 RB' label indicates the bandwidth allocation for a UE. Vertical lines represent the scheduled PRB positions for each UE across the beams, showing alignment within each beam. + +Table 6.2.2.1-5: NTN satellite Noise Figure in dB + +| Satellite | GEO | LEO 600 | LEO 1200 | +|---------------------------|-----|---------|----------| +| G/T (dB K -1 ) | 19 | 1.1 | 1.1 | +| G_Rx (dBi) | 51 | 30 | 30 | +| NF (dB) | 7.4 | 4.3 | 4.3 | + +#### 6.2.2.2 NTN UE parameters + +NTN UE parameters are given in Table 6.2.2.2-1 + +**Table 6.2.2.2-1: NTN UE characteristics for system level simulations** + +| Characteristics | Handheld | +|--------------------------------|-------------------------------------------------| +| Frequency band | S band (i.e. 2 GHz) | +| Antenna type and configuration | (1, 1, 2) with omni-directional antenna element | +| Polarisation | Linear: +/-45°X-pol | +| Rx Antenna gain | 0 dBi per element | +| Antenna temperature | 290 K | +| Noise figure | 9 dB | +| Tx transmit power | 200 mW (23 dBm) | +| Tx antenna gain | 0 dBi per element | + +#### 6.2.2.3 HAPS parameters + +Using the antenna model in Section 6.2.3.3, HAPS deployed at 20 km altitude has a coverage radius of 100 km in a 7-cell layout. Two implementations of the layout are shown in Figure 6.2.2.3-1. The UEs in the HAPS system are assumed to be outdoor and uniformly distributed in the coverage area in the rural environment. The serving cell is selected by the strongest RSRP or least coupling loss. (Note: Calibration data show these two implementations yield similar results). HAPS system parameters for the co-existence study are listed in Table 6.2.2.3-1. + +For DL transmission, one UE is scheduled for the full bandwidth. For UL transmission, 9 UEs are scheduled, each using a bandwidth of 6 RBs. The scheduled UEs are evenly distributed in the frequency domain as shown in Figure 6.2.2.3-2. Note that the scheduled resources are aligned among different cells to model co-channel effect. Since the UE uses only part of the channel bandwidth in UL, the ACI impact may differ in the frequency domain of the adjacent channel. The ACIR model described in Section 6.2.4 should be used to model the ACI from aggressor UEs in UL, taking into account the UE's transmission bandwidth. + +![Figure 6.2.2.3-1: HAPS cell layout. (a) shows a 7-cell hexagonal layout with a central cell and six surrounding cells. A blue arrow indicates a distance of 100km from the center of the central cell to the center of an adjacent cell, and another blue arrow indicates a distance of 38km from the center of the central cell to the boundary of an adjacent cell. (b) shows a circular layout with a central orange circle of radius 18 km and an outer light blue circle of radius 100 km. The outer circle is divided into six sectors by dashed lines.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +Figure 6.2.2.3-1: HAPS cell layout. (a) shows a 7-cell hexagonal layout with a central cell and six surrounding cells. A blue arrow indicates a distance of 100km from the center of the central cell to the center of an adjacent cell, and another blue arrow indicates a distance of 38km from the center of the central cell to the boundary of an adjacent cell. (b) shows a circular layout with a central orange circle of radius 18 km and an outer light blue circle of radius 100 km. The outer circle is divided into six sectors by dashed lines. + +**Figure 6.2.2.3-1: HAPS cell layout** + +Table 6.2.2.3-1: HAPS system parameters + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| HAPS altitude | 20 Km | +| Carrier frequency | 2 GHz | +| Frequency reuse factor | 1 | +| Duplex scheme | FDD | +| Channel bandwidth | 20 MHz | +| Subcarrier spacing (SCS) | 15 KHz | +| Number of cells | 7 | +| Coverage area (7 cells combined) | A 100 Km radius circular area centered by the serving HAPS | +| Frequency reuse | 1 | +| Environment 1 | Rural | +| UE distribution | Uniformly distributed in the coverage area | +| Indoor UE percentage | 0% | +| Number of DL scheduled UEs per cell | 1 | +| Number of UL scheduled UEs per cell | 9 | +| DL scheduled bandwidth per UE | 20 MHz | +| UL scheduled bandwidth per UE | 6 RBs | +| DL power control | No | +| UL power control | See section 6.2.6.3 | +| HAPS antenna | See section 6.2.3.3 | +| HAPS noise figure | 5 dB | +| HAPS-UE pathloss model | See section 6.2.5.4 | +| HAPS UE assumption | Same as TN UE in Table 6.2.2.4-1 | +| NOTE 1: HAPS is assumed to serve UEs in the rural environment, but the co-existed TN may be in the rural or urban macro environment. | | + +![Figure 6.2.2.3-2: UL scheduled UE bandwidth allocation. The diagram shows two channel types: TN channel and HAPS channel. The TN channel is a single block divided into three segments labeled UE1, UE2, and UE3, with a bracket above indicating a total width of 35 PRBs. The HAPS channel is a wider block divided into multiple cells (Cell 1, Cell 7, and others indicated by dots). Each cell contains 9 UEs (UE1 through UE9). A bracket above the HAPS channel indicates a total width of 35 PRBs. Below the HAPS channel, a bracket indicates a width of 6 PRBs, which corresponds to the UL scheduled bandwidth per UE.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +Figure 6.2.2.3-2: UL scheduled UE bandwidth allocation. The diagram shows two channel types: TN channel and HAPS channel. The TN channel is a single block divided into three segments labeled UE1, UE2, and UE3, with a bracket above indicating a total width of 35 PRBs. The HAPS channel is a wider block divided into multiple cells (Cell 1, Cell 7, and others indicated by dots). Each cell contains 9 UEs (UE1 through UE9). A bracket above the HAPS channel indicates a total width of 35 PRBs. Below the HAPS channel, a bracket indicates a width of 6 PRBs, which corresponds to the UL scheduled bandwidth per UE. + +Figure 6.2.2.3-2: UL scheduled UE bandwidth allocation + +#### 6.2.2.4 TN parameters + +TN parameters for co-existence study are given in Table 6.2.2.4-1, 6.2.2.4-2 and 6.2.2.4-3. + +**Table 6.2.2.4-1: Simulation assumptions of TN respectively based on NB-IoT and NR** + +| | NB-IoT
standalone | NR | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Carrier frequency in GHz | 2 | 2 | +| Size of each nominal channel BW in MHz | 0.2 | 20 | +| Transmission bandwidth in MHz | 0.18 | N/A | +| Environment | Urban macro
Rural | Deployment scenario related, see Table 6.2.2.4-2. | +| Network layout | 19-sites [57 sectors] with wrap-around | 19-sites 57 sectors with wrap-around | +| Inter-site distance in meter | 500 for 2GHz band for UMA
TBD For Rural | Deployment scenario related, see Table 6.2.2.4-2 | +| System loading and activity | Full buffer 100% | See Table 6.2.1.1-1 | +| Network location | TBD | See Table 6.2.1.1-1 | +| DL subcarrier spacing | 15kHz | 15kHz | +| UL | See RP-152284[7] | OFDMA | +| DL power control | No | No | +| UL power control | TR 36.942[8] section 5.1.1.6 (set 1) by bandwidth scale, target SNR at BS is 15 dB | TR 36.942[8] | +| Frequency reuse | 1 | 1 | +| Number of scheduled UE per cell (DL) | 1 | 1 | +| Number of scheduled UE per cell (UL) | 3 for multi-tone (60kHz per UE),
12 for 15kHz single-tone,
48 for 3.75kHz single-tone | 3 | +| UE antenna height in meter | 1.5 | 1.5m | +| UE TX power in dBm | -40 to 23 | -40 to 23 | +| UE antenna gain in dBi | 0 | 0 | +| Building penetration loss | TR 45.820[9] Annex D.1 | In pathloss model, TR 38.901[10] | +| Cell selection margin in dB | 3 | 3 | +| BS-MS min distance in meters | 35 | 35 | +| BS noise figure in dB | 5 | 5 | +| UE noise figure in dB | 9 | 9 | +| BS-UE path-loss model | TR 36.942[8] macro urban | TR 38.901[10] | +| Standard deviation of BS-UE log-normal shadow fading in dB | 10 | Deployment scenario related, referring to TR 38.901[10] | +| Shadowing correlation | Inter-cell 0.5
Intra-cell 1 | Inter-cell 0.5
Intra-cell 1 | +| Link-level performance model | | See Section 6.2.8
Throughput-SINR mapping | +| UE distribution | | Uniform | +| Evaluation metrics | SINR vs ACS (as victim) | See Section 6.2.8
Throughput or SNR loss criteria | + +**Table 6.2.2.4-2: Deployment-related parameters of TN (2 GHz)** + +| | Urban Macro | Rural Macro | Remarks | +|-----------------------------|--------------------|--------------------|------------------------------------------------------------------------------------| +| ISD in meters | 750 | 7500 | | +| BS Antenna height in meters | 25 | 30 | ITU-R Report M.2292[11] | +| UE Outdoor/indoor | 100% Outdoor | | | +| UE height in meter | 1.5 | 1.5 | RP-200559 [12] 3GPP LS to ITU-R WP5D
and
ITU-R WP5D
[IMT_Parameters] [13] | + +**Table 6.2.2.4-3: ACLR/ACS for TN (2GHz)** + +| | | NR | NB-IOT | +|----|------|------------------------------|--------| +| BS | ACLR | 45 dB | 40 dB | +| | ACS | 46 dB | 46 dB | +| UE | ACLR | 30dB (ACLR1)
43dB (ACLR2) | 37 | +| | ACS | 33 | 28 | + +### 6.2.3 Antenna and beamforming pattern modelling + +#### 6.2.3.1 Satellite and UE Antenna and beam forming pattern modelling + +Satellite and UE Antenna and beam forming pattern modelling of satellite could be referred to section 6.4.1 in TR 38.811[5]. + +The following normalized antenna gain pattern, corresponding to a typical reflector antenna with a circular aperture, is considered. + +$$1 \quad \text{for } \theta = 0$$ + +$$4 \left| \frac{J_1(ka \sin \theta)}{ka \sin \theta} \right|^2 \quad \text{for } 0 < |\theta| \leq 90^\circ$$ + +where: + +- $J_1(x)$ is the Bessel function of the first kind and first order with argument 'x', where x is $ka \sin \theta$ ; +- $a$ , is the radius of the antenna's circular aperture; +- $k = 2\pi f/c$ is the wave number; +- $f$ is the frequency of operation; +- $c$ is the speed of light in a vacuum and $\theta$ is the angle measured from the bore sight of the antenna's main beam. + +Note that $ka$ equals to the number of wavelengths on the circumference of the aperture and is independent of the operating frequency. + +The antenna patterns for LEO 600km, 1200km and GEO are shown in Figure 6.2.3.1-1 and 6.2.3.1-2. + +![Figure 6.2.3.1-1: Antenna pattern for LEO 600KM and 1200KM. The graph shows the normalized antenna gain in dB versus the angle theta in degrees. The x-axis ranges from -100 to 100 degrees, and the y-axis ranges from -150 to 0 dB. The pattern shows a main lobe centered at 0 degrees with a peak gain of 0 dB, and multiple side lobes with a peak gain of approximately -50 dB. The 3dB beamwidth is indicated as 4.4127 degrees.](0668098f95df8ed3c74c0cb82619c140_img.jpg) + +Figure 6.2.3.1-1: Antenna pattern for LEO 600KM and 1200KM. The graph shows the normalized antenna gain in dB versus the angle theta in degrees. The x-axis ranges from -100 to 100 degrees, and the y-axis ranges from -150 to 0 dB. The pattern shows a main lobe centered at 0 degrees with a peak gain of 0 dB, and multiple side lobes with a peak gain of approximately -50 dB. The 3dB beamwidth is indicated as 4.4127 degrees. + +**Figure 6.2.3.1-1: Antenna pattern for LEO 600KM and 1200KM (4.4127 deg for 3dB beamwidth)** + +![Antenna pattern plot for GEO antenna aperture.](b9d879f357d5f15fac9ea8585b87d0a2_img.jpg) + +A line graph showing the antenna pattern for a GEO antenna aperture. The x-axis represents the angle in degrees, ranging from -100 to 100 with major ticks every 20 units. The y-axis represents the gain in dB, ranging from -180 to 0 with major ticks every 20 units. The plot shows a sharp, narrow main lobe centered at 0 degrees, reaching a peak gain of 0 dB. The side lobes are highly oscillatory, with a dense cluster of peaks and troughs between approximately -80 and 80 degrees. The troughs of these side lobes reach values as low as -180 dB. Outside the range of -80 to 80 degrees, the side lobes are less dense and have lower peak gains, generally staying below -80 dB. + +Antenna pattern plot for GEO antenna aperture. + +**Figure 6.2.3.1-2: Antenna pattern for antenna aperture of GEO (0.4011 deg for 3dB beamwidth)** + +The beam layout definition for a single satellite simulation in S-Band is defined in Table 6.2.3.1-1. + +**Table 6.2.3.1-1: Beam layout definition for single satellite simulation** + +| | | | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Beam layout definition |

Baseline: Hexagonal mapping of the beam bore sight directions on UV plane defined in the satellite reference frame.

Only the 3dB beam width parameters should be used. The beam diameter and beam spacing values can be computed directly from the 3 dB beam width assumptions and should be considered as informative.

| | | +| Number of beams | Baseline: 7-beam layout (i.e. 6 co-frequency beams surrounding the central beam) | | | +| UV plane illustration (extracted from [19]) |

Spherical Coordinate System

Image: Spherical coordinate system diagram showing a unit sphere with axes x, y, z. A vector from the origin to the sphere's surface is labeled 'Beam Bore sight Direction'. The angle from the z-axis is theta, and the angle from the x-axis in the xy-plane is phi.

Projection of Coordinate System On the X-Y Plane (view from above Z-axis)

Image: Projection of the spherical coordinate system onto the XY plane. It shows a unit circle with the u-axis along the x-axis and the v-axis along the y-axis. Angles phi are marked at 0, 90, 180, and 270 degrees. The direction cosines are given as u = sin theta cos phi and v = sin theta sin phi.

| | | +| UV plane convention |

U axis is defined as the perpendicular line to the satellite-earth line on the orbital plane as illustrated here after:

Image: Diagram showing a satellite in an elliptical orbit around Earth. A line labeled 'u-axis' is drawn perpendicular to the line connecting the satellite and the center of Earth.

The straight line being orthogonal to UV plane is pointing towards the Earth centre.

UV coordinates of the nadir of the reference satellite is (0,0)

| | | +| Adjacent beam spacing on UV plane |

Baseline: Adjacent beam spacing computation based on 3dB beam width of the satellite antenna pattern:

$\text{ABS}[\text{rad}] = \sqrt{3} \times \sin(\text{HPBW}[\text{degrees}]/2) \text{ or } \text{ABS}[\text{rad}] = \sqrt{3} \times \sin(\text{HPBW}[\text{rad}]/2)$

with \text{ABS}[\text{degree}] = 180/\pi \times \text{ABS}[\text{rad}] and with HPBW the Half-Power BandWidth of the main lobe from the satellite antenna pattern.

| | | +| Central beam bore sight direction definition |

Baseline:

Case 1: Central beam center is considered at nadir point

Case 2: 45° for GEO and LEO

| | | +| |

Option 1: FRF=1

Image: Diagram for Option 1: FRF=1. It shows a hexagonal grid of 7 beams (Beam #0 to #6). All beams are colored red, indicating they share the same frequency. Above the grid, a bar labeled 'system frequency bandwidth' is shown as a single red segment.

|

Option 2: FRF=3

Image: Diagram for Option 2: FRF=3. It shows a hexagonal grid of 7 beams. Beam #0 is green, Beam #1 is blue, Beam #2 is red, Beam #3 is blue, Beam #4 is red, Beam #5 is blue, and Beam #6 is red. Above the grid, a bar labeled 'system frequency bandwidth' is shown as three segments: red, green, and blue.

|

Option 3: FRF=2

Image: Diagram for Option 3: FRF=2. It shows a hexagonal grid of 7 beams. Beam #0 is red, Beam #1 is green, Beam #2 is purple, Beam #3 is blue, Beam #4 is green, Beam #5 is purple, and Beam #6 is blue. Above the grid, a bar labeled 'system frequency bandwidth' is shown as four segments: red (RHCP), green (dLH), blue (RHCP), and purple (dLH).

| +| Polarization re-use |

Option 1: Disable

Option 2: Enable

Note: Polarization re-use should apply only if circular polarization for terminal antenna is considered

| | | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| UEs outdoor/indoor distribution | 100% outdoor distribution for UEs | +| UE distribution | The cell area associated to a given beam is defined as the Voronoi cell associated with the corresponding beam centers. | +| UE configuration | S-band: Handheld | +| UE orientation | Handheld: Random | +| UE attachment | RSRP | +| NOTE 1: Typical impairment values (additional frequency error, SNR loss) due to the feeder link except for delay can be considered to be negligible. When available, specific values can be considered in the evaluation and should be reported. | | +| NOTE 2: For the calibration purpose, the ionospheric scintillation loss shall be considered equal to zero (i.e., the UEs are located between 20 and 60 degrees of latitude). | | + +#### 6.2.3.2 TN BS and UE antenna and beam forming pattern modelling + +For AAS antenna, it refers to the pattern in TR 38.921 [14]. + +**Table 6.2.3.2-1: AAS antenna parameters for 2GHz** + +| | | Rural | Macro urban | +|------|-----------------------------------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------| +| 1 | Base Station Antenna Characteristics | | | +| 1.1 | Antenna pattern | TR 38.921[14] | | +| 1.2 | Element gain (dBi) (Note 2) | 7.1 | 6.4 | +| 1.3 | Horizontal/vertical 3 dB beam width of single element (degree) | 90° for H
54° for V | 90° for H
65° for V | +| 1.4 | Horizontal/vertical front-to-back ratio (dB) | 30 for both H/V | 30 for both H/V | +| 1.5 | Antenna polarization | Linear $\pm 45^\circ$ | Linear $\pm 45^\circ$ | +| 1.6 | Antenna array configuration (Row $\times$ Column) (Note 4) | 8 $\times$ 8 elements | 8 $\times$ 8 elements | +| 1.7 | Horizontal/Vertical radiating element spacing | 0.5 of wavelength for H,
0.9 of wavelength for V | 0.5 of wavelength for H,
0.7 of wavelength for V | +| 1.8 | Array Ohmic loss (dB) (Note 2) | 2 | 2 | +| 1.9 | Conducted power (before Ohmic loss) per antenna element (dBm) (Note 3) | 25 | 25 | +| 1.10 | Base station maximum coverage angle in the horizontal plane (degrees) | 120 | 120 | +| 1.11 | Base station vertical coverage range (degrees) (Note 1) | 90-100 | 90-120 | +| 1.12 | Mechanical downtilt (degrees) | 3 | 10 | + +For non-AAS antenna, the parameters in Table 6.2.3.2-1 are used for 2GHz BS antenna pattern in the NTN system simulation. + +**Table 6.2.3.2-1: FR1 BS Non-AAS antenna pattern for 2GHz** + +| Parameter for BS | Values | | +|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Antenna vertical radiation pattern (dB) | $A_{E,V}(\theta'') = -\min \left\{ 12 \left( \frac{\theta'' - 90^\circ}{\theta_{3\text{dB}}} \right)^2, SLA_V \right\}, \theta_{3\text{dB}} = 10^\circ, SLA_V = 20\text{dB}$ | | +| Antenna horizontal radiation pattern (dB) | $A_{E,H}(\phi'') = -\min \left\{ 12 \left( \frac{\phi''}{\phi_{3\text{dB}}} \right)^2, A_m \right\}, \phi_{3\text{dB}} = 65^\circ, A_m = 20\text{dB}$ | | +| Combining method for 3D antenna pattern (dB) | $A''(\theta'', \phi'') = -\min \{ -[A_{E,V}(\theta'') + A_{E,H}(\phi'')], A_m \}$ | | +| Maximum directional gain of an antenna $G_{E,max}$ | 17 dBi | | +| Conducted power | 46 dBm | | +| Mechanical downtilt in degrees | Rural | 3 | +| | Urban | 10 | + +Only Non-AAS antenna can be used for NB-IoT. + +For UE antennas, an omni-directional radiation pattern with antenna gain 0dBi is assumed. + +#### 6.2.3.3 HAPS antenna model + +HAPS antenna model is based on the proposal for HIBS (HAPS as IMT base stations) study in ITU WP-5D [24]. The antenna array is composed of seven antenna panels (six side panels and one downward facing panel) as shown in Figure 6.2.3.3-1. Antenna elements on each panel are co-phased to form one beam in two crossed linear polarizations to serve one cell. There are a total of seven cells in two layers, one cell in the 1st layer and six cells in the 2nd layer. The antenna parameters are listed in Table 6.2.3.3-1. Note that a fixed beam in the direction of the panel boresight is formed by each panel to serve one cell. Figure 6.2.3.3-1 shows the antenna gain of the 1st layer cell and a 2nd layer cell projected on the ground. + +![Diagram of the HAPS antenna model showing seven antenna panels arranged in a hexagonal shape. The central panel is downward-facing (1st layer cell), and the six side panels are upward-facing (2nd layer cells). The diagram shows the coverage areas projected on the ground: a central red circle for the 1st layer cell and six surrounding colored ellipses (green, blue, etc.) for the 2nd layer cells. Labels include '2nd layer cell 1', '2nd layer cell 2', '2nd layer cell 3', and '1st layer cell (downward)'.](a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg) + +Diagram of the HAPS antenna model showing seven antenna panels arranged in a hexagonal shape. The central panel is downward-facing (1st layer cell), and the six side panels are upward-facing (2nd layer cells). The diagram shows the coverage areas projected on the ground: a central red circle for the 1st layer cell and six surrounding colored ellipses (green, blue, etc.) for the 2nd layer cells. Labels include '2nd layer cell 1', '2nd layer cell 2', '2nd layer cell 3', and '1st layer cell (downward)'. + +**Figure 6.2.3.3-1: HAPS antenna model** + +Table 6.2.3.3-1: HAPS antenna parameters + +| | | +|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Number of cells | 7 | +| Antenna array configuration (row x column) | 2 x 2 for 1st layer cell
4 x 2 for 2nd layer cell | +| Antenna polarization | Linear $\pm 45^\circ$ | +| Element gain 1 | 7.8 dBi | +| Element HPBW horizontal/vertical | $65^\circ$ for both H/V | +| Element front-to-back ratio horizontal/vertical | 30 dB for both H/V | +| Element spacing horizontal/vertical | 0.7 wavelength for both H/V | +| Antenna panel tilt (from the horizon) 2 | $90^\circ$ for 1st layer cell
$23^\circ$ for 2nd layer cell | +| EIPR/cell | 56.8 dBm (1st layer cell),
59.8 dBm (2nd layer cell) | +| EIRP spectral density/cell | 43.8 dBm/MHz (1st layer cell),
46.8 dBm/MHz (2nd layer cell) | +| Tx power per antenna panel | 43 dBm | +| Conducted power (before ohmic loss) per antenna element (dBm) | 34 dBm for 2 x 2 (x 2 polarizations for 1 st layer cell)
31 dBm for 4 x 2 (x 2 polarizations for 2 nd layer cell) | +| Antenna weight 3 $w_{m,n}$ | 1/2 for each of 1st layer cell element
$1/2\sqrt{2}$ for each of 2nd layer cell element | +| Polarization gain for SINR | 3 dB | +| NOTE 1: The element gain includes the Ohmic loss of 2 dB. | | +| NOTE 2: This is mechanical tilt only. | | +| NOTE 3: These antenna weights create a fixed cell beam in the antenna panel's boresight direction. | | + +![Figure 6.2.3.3-2: HAPS antenna gain (in dB) in a 100 km radius area on the ground. (a) Antenna gain of the 1st layer cell. (b) Antenna gain of a 2nd layer cell. Both plots show a circular area with a color scale from -15 dB (green) to 10 dB (red). Plot (a) shows a uniform gain distribution. Plot (b) shows a directional gain distribution with a peak at phi = 0 degrees and a color gradient indicating gain levels at phi = 30 and phi = -30 degrees.](455c842681aadb4969bd61d71f556744_img.jpg) + +Figure 6.2.3.3-2: HAPS antenna gain (in dB) in a 100 km radius area on the ground. (a) Antenna gain of the 1st layer cell. (b) Antenna gain of a 2nd layer cell. Both plots show a circular area with a color scale from -15 dB (green) to 10 dB (red). Plot (a) shows a uniform gain distribution. Plot (b) shows a directional gain distribution with a peak at phi = 0 degrees and a color gradient indicating gain levels at phi = 30 and phi = -30 degrees. + +Figure 6.2.3.3-2: HAPS antenna gain (in dB) in a 100 km radius area on the ground. (a) Antenna gain of the 1st layer cell. (b) Antenna gain of a 2nd layer cell. + +### 6.2.4 ACIR model + +ACLR modelling for TN and NTN co-existence study referring to clause 5.1.1.4.1 and 5.1.1.4.2 in TR 36.942[8] is used as baseline. The number of RBs refers to Table 6.2.2.1-4 and Table 6.2.2.4-1 respectively. + +### 6.2.5 Propagation model + +#### 6.2.5.1 Propagation model between NTN SAN and UE + +Propagation model between NTN SAN and UE should reference to section 6.6 in TR 38.811[5]. + +#### 6.2.5.2 Propagation model between TN BS and UE + +Propagation model between TN BS and UE should reference to section 7.4 in TR 38.901[10]. + +#### 6.2.5.3 Propagation model between NTN SAN and TN BS + +Propagation model between NTN SAN and TN BS should reference to TS 38.811[5] which is used for DL-UL cross link interference for S band. + +#### 6.2.5.4 Propagation model for HAPS + +Propagation model between HAPS and UE, regardless of whether the UE is connected to HAPS or TN, should reference to section 6.6 in TR 38.811[5]. + +### 6.2.6 Transmission power control model + +#### 6.2.6.1 TN UL TPC + +For uplink scenario, TPC model specified in Section 9.1 TR 36.942[8] is applied for TN with following parameters. + +$$P_t = P_{\max} \times \min \left\{ 1, \max \left[ R_{\min}, \left( \frac{CL}{CL_{x-ile}} \right)^\gamma \right] \right\}$$ + +where: + +- $P_{\max} = 23\text{dBm}$ , +- $R_{\min} = \text{TBD dB}$ , +- $CL_{x-ile}$ and $\gamma$ are set as following: + - $CL_{x-ile} = 88 + 10 \cdot \log_{10}(200/X) + 11 - Y$ , where X is UL transmission BW (MHz) and Y is the BS noise figure + - $\gamma = 1$ For uplink scenario, + +#### 6.2.6.2 NTN UL TPC + +For the coexistence study, the same TPC model of TN for NTN UL scenarios is adopted to align with UE UL power control parameters used in TR 38.821[6]. + +#### 6.2.6.3 NTN DL TPC + +For downlink scenario, no power control scheme is applied. + +#### 6.2.6.4 HAPS UL TPC + +HAPS uplink follows the TPC model in Section 6.2.6.1 with $X = 1.08$ (scheduled bandwidth 6 RBs) and $Y = 5$ (HAPS noise figure is 5 dB). + +#### 6.2.6.5 HAPS DL TPC + +For downlink scenario, no power control scheme is applied. + +### 6.2.7 Received power model + +The received power in downlink and uplink scenarios is defined as below: + +$$RX\_PWR = TX\_PWR - Path\ loss + G\_TX + G\_RX$$ + +where: + +- RX\_PWR is the received power +- TX\_PWR is the transmitted power +- G\_TX is the transmitter antenna gain (directional array gain) +- G\_RX is the receiver antenna gain (directional array gain). + +### 6.2.8 Performance metric + +For NR, the average throughput loss and 5%-ile throughput loss should be less than 5%. + +For NB-IOT, the SNR loss should refer to TR 36.802 [15]. + +For NTN, the average throughput loss and 5%-ile throughput loss should be less than 5%. + +### 6.2.9 Throughput ~ SNR mapping + +Adopt Section 5.2.7 of TR 38.803[20] as the SINR-Throughput performance metrics + +## 6.3 Co-existence simulation methodology + +### 6.3.1 Simulation procedure + +Adopt following simulation steps. + +- Step 1: Generate aggressor and victim networks. + - NTN central beam is at satellite nadir, surrounded with 6 co-frequency beams. NTN FRFs higher than 1 need to be considered. Assume one NTN aggressor as default. + - Deployment of TN network (19 cells with wraparound) refers to Table 6.2.1.1-1 +- Step 2: UE associations + - TN UE are generated randomly inside the TN network, make sure enough TN UEs are associated to each TN sectors based on coupling loss. + - Deployment of NTN UE refers to Table 6.2.1.1-1. +- Step 3: Once association is done, round robin scheduling is used. BF weights are adjusted to point to the LOS direction between BS/SAN-UE. This is done for both victim and aggressor networks. +- Step 4: Throughput is computed in the victim systems without considering ACI as below: + +$$Thput_{NO\ ACI}[bpsHz] = f(SINR_{ICI}) = f\left(\frac{S}{N+I_{ICI}}\right),$$ + +where: $I_{ICI}$ is the inter-cell interference. + +For TN-NTN SINR calculation, the satellite receiver off angle should be considered in the satellite receiver gain calculation when calculating SINR. Note that such angle is not considered in TR 38.821[6] section 6.1.3 equations. Thus those equations should be used for SINR calculation. + +- Step 5: Throughput is computed considering ACI as below: + +$$Thput_{ACI}[bpsHz] = f(SINR_{ICI+ACI}) = f\left(\frac{S}{N+I_{ICI}+I_{ACI}}\right),$$ + +where: $I_{ACI}$ is the adjacent channel interference. + +- Step 6: RF parameters are determined based on the degradation cause by ACI as below: + +$$Loss_{ACI} = 1 - \frac{Thput_{ACI}}{Thput_{SINGLE}}$$ + +To simplify the simulation of interference from TN to NTN UL in Case 2 and 6, following method can be used. Consider the active TN cells from central NTN beam for the ACI evaluation from TN to NTN UL. The scaling factor is to be discussed and determined if any in next meeting. There is a view that simplifying such coexistence simulation work for Case 2 may even not be required. + +- Step 1: to drop NTN UE per beamprint randomly; +- Step 2: to drop N clusters consisting of 57 sectors per beamprint randomly; +- Step 3: to calculate the total ACI per beam to NTN UL by following scaling factor: + +$$P_{TotalPerBam,j} = \frac{active\_TN}{N} \cdot \sum_i^N P_i$$ + +where: $active\_TN = active\_factor * round(\text{the area per beam/the area of 57 sectors})$ + $active\_factor = 20\%$ (or lower, particularly for urban scenarios) + +- Step 4: to calculate the total ACI from all beams (e.g. $M=7$ ) for NTN: + +$$P_{total} = \sum_j^M P_{TotalPerBam,j}$$ + +### 6.3.2 Methods and principle to process co-existence simulation results + +In order to process the co-existence simulation results received for all different scenarios and assumptions, the following steps are adopted: + +- Step 1: Discuss and agree on the most stringent scenario(s) for each scenario (Scenario 1, 2, 3...,6); +- Step 2: Discuss and determine the required ACIR from results of the most stringent case(s) for each scenario; +- Step 3: Use equation to derive corresponding ACLR or ACS from the agreed ACIR for each scenario + +It is noted that the averaged ACIR for the most stringent case in each scenario would be derived by taking the average among the interpolated ACIR results derived from each company's results for that case. + +Moreover, the following considerations are adopted to deal with major disputes for the selected cases' results in each scenario: + +- If the required ACIR results, from the contributor who did not participate or their results is still not well-aligned in calibration table, has a difference larger than 10 dB with most others, this result can be not considered in the discussion. +- If the required ACIR results, from one contributor, has a difference larger than 10 dB with most others, this result can be not considered in the discussion. + +The processed results by adopting above principles and methods for scenarios 1 to 7 identified in Table 6.1-2 are captured in section 6.4. It is noted that due to the space limitation, only part of the simulation results for each case are presented, and the whole results for all studied options, as listed in Table 6.1-1 and section 6.2, can be found in Annex C. + +Table 6.3.2-1: Selected option for each scenario + +| Scenario | Aggressor system | Victim system | Environment | Contributing | +|----------------|------------------|----------------|--------------------|------------------| +| 1 | TN DL | NTN GEO DL | Urban | NTN UE ACS | +| 2 | TN UL | NTN GEO UL | Urban | NTN SAN ACS | +| 3 | NTN LEO-600 DL | TN DL | Rural | NTN SAN LEO ACLR | +| | NTN GEO DL | TN DL | Rural | NTN SAN GEO ACLR | +| 4 | NTN GEO UL | TN UL | Urban | NTN UE ACLR | +| 5 | NTN GEO UL | TN DL | Rural | NTN UE ACLR | +| 6 1 | NR-TN DL | NTN LEO-600 UL | Rural 2 | NTN SAN ACS | +| | NR-TN DL | NTN GEO UL | Rural 2 | NTN SAN ACS | +| 7 | HAPS DL | TN DL | Rural | HAPS ACLR | +| 8 | TN UL | HAPS UL | Rural | HAPS ACS | + +NOTE 1: Agreed representative case for Scenario 6. + +NOTE 2 : The initial results suggested that the NR-NTN SAN would suffer more interference in urban deployment scenario. It is agreed that a more relevant environment for case 6 is a mixture of Urban and Rural environment (e.g., urban area with a 50km diameter inside a GEO beam with a 250km diameter). Further studies based on the mixed urban environment could be considered. As compromise, rural only scenario was then selected. + +## 6.4 Co-existence simulation results + +### 6.4.1 Scenario 1: 2GHz TN DL interfering NTN DL + +The co-existence results from all concerned options in this scenario were evaluated, and it has been agreed to select the NR DL equipped with both AAS and non-AAS antenna interfering the NR-NTN GEO DL that deployed in urban environment as the most stringent case. + +Table 6.4.1-1: Simulation results for average throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | +|----------|-------|-------|-------|-------|-------|-------|------|------|------|------| +| Qualcomm | 32.76 | 26.13 | 19.50 | 15.41 | 11.32 | 8.26 | 6.21 | 4.16 | 3.22 | 2.27 | +| MTK | 7.28 | 5.71 | 4.60 | 3.77 | 3.05 | 2.35 | 1.90 | 1.30 | 1.02 | 0.80 | +| ZTE | 31.76 | 24.81 | 18.95 | 14.18 | 10.47 | 7.63 | 5.50 | 3.92 | 2.79 | 1.99 | +| Ericsson | | | 4.2 | 3.0 | 2.1 | 1.5 | 1.1 | | | | +| CATT | 8.7 | 6.5 | 5.3 | 4.3 | | | | | | | +| Xiaomi | 38.11 | 31.51 | 25.56 | 20.35 | 15.94 | 12.29 | 9.36 | 7.06 | 5.29 | 3.95 | + +![Figure 6.4.1-1: Simulation results for average throughput loss - TN BS with AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (6 to 24). Six lines represent Qualcomm (orange), MTK (grey), ZTE (yellow), Ericsson (light blue), CATT (green), and Xiaomi (dark blue). All lines show a downward trend as ACIR increases. Xiaomi has the highest loss, while Ericsson and MTK have the lowest.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +| ACIR [dB] | Qualcomm | MTK | ZTE | Ericsson | CATT | Xiaomi | +|-----------|----------|-----|------|----------|------|--------| +| 6 | 32.5 | 7.5 | 31.5 | 8.5 | 8.5 | 38.5 | +| 8 | 26.0 | 5.5 | 25.0 | 6.0 | 6.5 | 31.5 | +| 10 | 19.5 | 4.5 | 19.0 | 4.0 | 5.0 | 25.5 | +| 12 | 15.5 | 4.0 | 14.5 | 3.0 | 4.5 | 20.5 | +| 14 | 11.0 | 3.5 | 10.5 | 2.5 | 4.0 | 16.0 | +| 16 | 8.0 | 2.5 | 8.0 | 2.0 | 3.5 | 12.5 | +| 18 | 6.0 | 2.0 | 6.0 | 1.5 | 3.0 | 9.5 | +| 20 | 4.5 | 1.5 | 4.5 | 1.0 | 2.5 | 7.5 | +| 22 | 3.5 | 1.0 | 3.5 | 0.8 | 2.0 | 5.5 | +| 24 | 2.5 | 0.8 | 2.5 | 0.5 | 1.5 | 4.0 | + +Figure 6.4.1-1: Simulation results for average throughput loss - TN BS with AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (6 to 24). Six lines represent Qualcomm (orange), MTK (grey), ZTE (yellow), Ericsson (light blue), CATT (green), and Xiaomi (dark blue). All lines show a downward trend as ACIR increases. Xiaomi has the highest loss, while Ericsson and MTK have the lowest. + +Figure 6.4.1-1: Simulation results for average throughput loss - TN BS with AAS antenna + +Table 6.4.1-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | +|----------|-------|-------|-------|-------|-------|-------|-------|------|------|------| +| Qualcomm | 44.68 | 27.01 | 19.33 | 11.66 | 9.31 | 6.96 | 5.20 | 4.03 | | | +| MTK | 7.38 | 4.80 | 3.09 | 1.97 | 1.26 | 0.80 | 0.50 | 0.32 | 0.20 | 0.13 | +| ZTE | 33.63 | 24.27 | 17.09 | 12.37 | 9.01 | 6.43 | 4.81 | 3.30 | 2.42 | 1.70 | +| Ericsson | 3.0 | 2.8 | 1.8 | | | | | | | | +| CATT | 13.4 | 12.7 | 11.8 | 9.33 | 8.76 | 8.18 | 7.65 | 5.83 | 4.91 | | +| Xiaomi | 65.22 | 54.94 | 44.26 | 33.58 | 24.20 | 16.78 | 11.29 | 7.43 | 4.51 | | + +![Figure 6.4.1-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (14 to 32). Six lines represent Qualcomm (orange), MTK (grey), ZTE (yellow), Ericsson (light blue), CATT (green), and Xiaomi (dark blue). All lines show a downward trend as ACIR increases. Xiaomi has the highest loss, while Ericsson and MTK have the lowest.](94389c644d3c25d99db7bc6d87bf5779_img.jpg) + +| ACIR [dB] | Qualcomm | MTK | ZTE | Ericsson | CATT | Xiaomi | +|-----------|----------|------|-------|----------|------|--------| +| 14 | 44.68 | 7.38 | 33.63 | 3.0 | 13.4 | 65.22 | +| 16 | 27.01 | 4.80 | 24.27 | 2.8 | 12.7 | 54.94 | +| 18 | 19.33 | 3.09 | 17.09 | 1.8 | 11.8 | 44.26 | +| 20 | 11.66 | 1.97 | 12.37 | | 9.33 | 33.58 | +| 22 | 9.31 | 1.26 | 9.01 | | 8.76 | 24.20 | +| 24 | 6.96 | 0.80 | 6.43 | | 8.18 | 16.78 | +| 26 | 5.20 | 0.50 | 4.81 | | 7.65 | 11.29 | +| 28 | 4.03 | 0.32 | 3.30 | | 5.83 | 7.43 | +| 30 | | 0.20 | 2.42 | | 4.91 | 4.51 | +| 32 | | 0.13 | 1.70 | | | | + +Figure 6.4.1-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (14 to 32). Six lines represent Qualcomm (orange), MTK (grey), ZTE (yellow), Ericsson (light blue), CATT (green), and Xiaomi (dark blue). All lines show a downward trend as ACIR increases. Xiaomi has the highest loss, while Ericsson and MTK have the lowest. + +Figure 6.4.1-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +**Table 6.4.1-3: Interpolated ACIR values for Scenario 1 to meet the 5% throughput loss criteria - TN BS with AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Qualcomm | Average | 19.18 | +| | 5%-tile | 26.34 | +| MTK | Average | 9.28 | +| | 5%-tile | 15.85 1 | +| ZTE | Average | 18.63 | +| | 5%-tile | 25.77 | +| Ericsson | Average | | +| | 5%-tile | 12.10 1 | +| CATT | Average | 10.6 | +| | 5%-tile | 29.80 | +| Xiaomi | Average | 22.43 | +| | 5%-tile | 29.40 | + +NOTE 1: According to the principles, these values are not treated for later process. + +**Table 6.4.1-4: Average ACIR of 5%-tile values in the above worse case for Scenario 1 - TN BS with AAS antenna** + +| | Scenario 1 | +|-----------------|------------| +| ACIR value [dB] | 27.83 | + +**Table 6.4.1-5: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | +|----------|-------|-------|-------|-------|-------|------|------|------|------|------| +| MTK | 25,91 | 20,30 | 16,17 | 12,92 | 9,97 | 8,19 | 6,76 | 5,54 | 4,32 | 3,34 | +| ZTE | 35,27 | 27,40 | 20,83 | 15,57 | 11,46 | 8,34 | 6,04 | 4,32 | 3,06 | 2,14 | +| THALES | NA | NA | NA | 13,13 | 9,54 | 6,85 | 4,86 | 3,4 | 2,3 | 1,58 | + +![Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for TN BS with non-AAS antenna. The graph plots three data series: MTK (blue line with circles), ZTE (orange line with circles), and THALES (grey line with circles). The x-axis represents ACIR [dB] from 6 to 24, and the y-axis represents Loss [%] from 0.00 to 40.00. All three series show a decreasing trend in loss as ACIR increases. ZTE starts at the highest loss (approx. 35.27% at 6 dB ACIR), followed by MTK (approx. 25.91% at 6 dB ACIR), and THALES (approx. 13.13% at 12 dB ACIR). All series converge towards a loss of approximately 1.58% at 24 dB ACIR.](37a96d647a34d2c514364514c7f85f41_img.jpg) + +| ACIR [dB] | MTK Loss [%] | ZTE Loss [%] | THALES Loss [%] | +|-----------|--------------|--------------|-----------------| +| 6 | 25.91 | 35.27 | NA | +| 8 | 20.30 | 27.40 | NA | +| 10 | 16.17 | 20.83 | NA | +| 12 | 12.92 | 15.57 | 13.13 | +| 14 | 9.97 | 11.46 | 9.54 | +| 16 | 8.19 | 8.34 | 6.85 | +| 18 | 6.76 | 6.04 | 4.86 | +| 20 | 5.54 | 4.32 | 3.4 | +| 22 | 4.32 | 3.06 | 2.3 | +| 24 | 3.34 | 2.14 | 1.58 | + +Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for TN BS with non-AAS antenna. The graph plots three data series: MTK (blue line with circles), ZTE (orange line with circles), and THALES (grey line with circles). The x-axis represents ACIR [dB] from 6 to 24, and the y-axis represents Loss [%] from 0.00 to 40.00. All three series show a decreasing trend in loss as ACIR increases. ZTE starts at the highest loss (approx. 35.27% at 6 dB ACIR), followed by MTK (approx. 25.91% at 6 dB ACIR), and THALES (approx. 13.13% at 12 dB ACIR). All series converge towards a loss of approximately 1.58% at 24 dB ACIR. + +**Figure 6.4.1-3: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +Table 6.4.1-6: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | +|----------|-------|-------|-------|-------|-------|-------|-------|------|------|------| +| MTK | 69,59 | 59,31 | 48,18 | 37,24 | 26,31 | 18,42 | 12,49 | 8,27 | 5,39 | 3,47 | +| ZTE | 37,88 | 27,97 | 20,08 | 14,18 | 9,80 | 6,65 | 4,46 | 2,78 | 1,82 | 1,24 | +| THALES | 16,36 | 14,55 | 8,64 | 7,27 | 6,36 | 5,91 | 5,45 | 5,45 | 4,55 | 1,82 | + +![Line graph showing simulation results for 5%-tile throughput loss (%) versus ACIR [dB] for three sources: MTK (blue line with circles), ZTE (orange line with circles), and THALES (grey line with circles). The x-axis ranges from 14 to 32 dB, and the y-axis ranges from 0.00 to 80.00%. All three sources show a decreasing trend in throughput loss as ACIR increases. MTK starts at approximately 70% loss at 14 dB ACIR and drops to about 3.5% at 32 dB. ZTE starts at about 38% loss and drops to about 1.2%. THALES starts at about 16% loss and drops to about 1.8%.](a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg) + +| ACIR[dB] | MTK Loss [%] | ZTE Loss [%] | THALES Loss [%] | +|----------|--------------|--------------|-----------------| +| 14 | 69,59 | 37,88 | 16,36 | +| 16 | 59,31 | 27,97 | 14,55 | +| 18 | 48,18 | 20,08 | 8,64 | +| 20 | 37,24 | 14,18 | 7,27 | +| 22 | 26,31 | 9,80 | 6,36 | +| 24 | 18,42 | 6,65 | 5,91 | +| 26 | 12,49 | 4,46 | 5,45 | +| 28 | 8,27 | 2,78 | 5,45 | +| 30 | 5,39 | 1,82 | 4,55 | +| 32 | 3,47 | 1,24 | 1,82 | + +Line graph showing simulation results for 5%-tile throughput loss (%) versus ACIR [dB] for three sources: MTK (blue line with circles), ZTE (orange line with circles), and THALES (grey line with circles). The x-axis ranges from 14 to 32 dB, and the y-axis ranges from 0.00 to 80.00%. All three sources show a decreasing trend in throughput loss as ACIR increases. MTK starts at approximately 70% loss at 14 dB ACIR and drops to about 3.5% at 32 dB. ZTE starts at about 38% loss and drops to about 1.2%. THALES starts at about 16% loss and drops to about 1.8%. + +Figure 6.4.1-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +Table 6.4.1-7: Interpolated ACIR values for Scenario 1 to meet the 5% throughput loss criteria - TN BS with non-AAS antenna + +| Source | | Interpolated ACIR[dB] | +|--------|---------|-----------------------| +| MTK | Average | 20.89 | +| | 5%-tile | 30.41 | +| ZTE | Average | 19.21 | +| | 5%-tile | 25.51 | +| Thales | Average | 17.86 | +| | 5%-tile | 29.00 | + +Table 6.4.1-8: Average ACIR of 5%-tile values in the above worse case for Scenario 1 - TN BS with non-AAS antenna + +| | Scenario 1 | +|-----------------|------------| +| ACIR value [dB] | 28.31 | + +### 6.4.2 Scenario 2: 2GHz TN UL interfering NTN UL + +The co-existence results from all concerned options in this scenario were evaluated, and it has been agreed to select the NR UL interfering the NR-NTN GEO UL that deployed in urban environment as the most stringent case. + +**Table 6.4.2-1: Simulation results for average throughput loss - TN BS with AAS antenna** + +| ACIR[dB] | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | +|----------|-------|-------|-------|-------|-------|-------|------|------|------|------| +| Qualcomm | 36.46 | 24.81 | 18.43 | 12.06 | 7.70 | 5.34 | 2.98 | | | | +| ZTE | 16.46 | 11.77 | 8.26 | 5.51 | 3.55 | 2.25 | 1.48 | 0.98 | 0.63 | 0.39 | +| MTK | 38.61 | 31.96 | 25.57 | 20.13 | 15.27 | 11.22 | 7.96 | 5.48 | 3.68 | 2.42 | +| Ericsson | | 15.6 | 10.4 | 7.2 | 4.2 | 2.9 | 1.9 | | | | +| CATT | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| Xiaomi | 41.11 | 30.58 | 21.75 | 14.92 | 9.96 | 6.53 | 4.22 | 2.70 | 1.72 | 1.09 | + +![Line graph showing average throughput loss (%) vs ACIR [dB] for various manufacturers. The graph shows that throughput loss decreases as ACIR increases. Qualcomm and MTK show the highest loss, while CATT shows zero loss across all ACIR values.](07c5a1c0fddd7da92a8427f5af840ffa_img.jpg) + +| ACIR [dB] | Qualcomm | ZTE | MTK | Ericsson | CATT | Xiaomi | +|-----------|----------|-------|-------|----------|------|--------| +| 18 | 36.46 | 16.46 | 38.61 | - | 0.00 | 41.11 | +| 20 | 24.81 | 11.77 | 31.96 | 15.6 | 0.00 | 30.58 | +| 22 | 18.43 | 8.26 | 25.57 | 10.4 | 0.00 | 21.75 | +| 24 | 12.06 | 5.51 | 20.13 | 7.2 | 0.00 | 14.92 | +| 26 | 7.70 | 3.55 | 15.27 | 4.2 | 0.00 | 9.96 | +| 28 | 5.34 | 2.25 | 11.22 | 2.9 | 0.00 | 6.53 | +| 30 | 2.98 | 1.48 | 7.96 | 1.9 | 0.00 | 4.22 | +| 32 | - | 0.98 | 5.48 | - | 0.00 | 2.70 | +| 34 | - | 0.63 | 3.68 | - | 0.00 | 1.72 | +| 36 | - | 0.39 | 2.42 | - | 0.00 | 1.09 | + +Line graph showing average throughput loss (%) vs ACIR [dB] for various manufacturers. The graph shows that throughput loss decreases as ACIR increases. Qualcomm and MTK show the highest loss, while CATT shows zero loss across all ACIR values. + +**Figure 6.4.2-1: Simulation results for average throughput loss - TN BS with AAS antenna** +**Table 6.4.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna** + +| ACIR[dB] | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | 40 | +|----------|-------|-------|-------|-------|-------|-------|-------|------|------|------| +| Qualcomm | NA | NA | NA | NA | NA | | | | | | +| ZTE | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| MTK | 68.80 | 58.62 | 47.26 | 36.43 | 26.97 | 19.13 | 13.06 | 8.68 | 5.67 | 3.67 | +| Ericsson | NA | NA | NA | NA | NA | | | | | | +| CATT | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| Xiaomi | NA | NA | NA | NA | NA | NA | NA | NA | NA | | + +![Figure 6.4.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna. The graph shows Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (22 to 40). Six data series are plotted: Qualcomm (orange), ZTE (grey), MTK (yellow), Ericsson (light blue), CATT (green), and Xiaomi (dark blue). The MTK series shows a steep downward trend, starting at approximately 36.5% loss at 28 dB ACIR and decreasing to about 4% loss at 40 dB ACIR. The other five series remain nearly flat at 0% loss across the entire ACIR range.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +Figure 6.4.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna. The graph shows Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (22 to 40). Six data series are plotted: Qualcomm (orange), ZTE (grey), MTK (yellow), Ericsson (light blue), CATT (green), and Xiaomi (dark blue). The MTK series shows a steep downward trend, starting at approximately 36.5% loss at 28 dB ACIR and decreasing to about 4% loss at 40 dB ACIR. The other five series remain nearly flat at 0% loss across the entire ACIR range. + +Figure 6.4.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +Table 6.4.2-3: Interpolated ACIR values for Scenario 2 to meet the 5% throughput loss criteria - TN BS with AAS antenna + +| Source | | Interpolated ACIR[dB] | +|-----------------------------------------------------------------------------------|---------|-----------------------| +| Qualcomm | Average | 28.29 | +| | 5%-tile | | +| ZTE | Average | 24.52 | +| | 5%-tile | | +| MTK | Average | 32.53 | +| | 5%-tile | 38.67 1 | +| Ericsson | Average | 25.47 | +| | 5%-tile | | +| CATT | Average | | +| | 5%-tile | | +| Xiaomi | Average | 29.32 | +| | 5%-tile | | +| NOTE 1: According to the principles, this value is not treated for later process. | | | + +Table 6.4.2-4: Average ACIR values in the above worse case for Scenario 2 - TN BS with AAS antenna + +| | Scenario 2 | +|-----------------|------------| +| ACIR value [dB] | 28.03 | + +Table 6.4.2-5: Simulation results for average throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | +|----------|-------|-------|-------|-------|-------|------|------|------|------|------| +| Ericsson | NA | NA | NA | NA | NA | 10,4 | 6,8 | 4,2 | 2,9 | NA | +| THALES | 14,06 | 10,74 | 7,74 | 5,53 | 3,63 | 2,37 | 1,74 | 1,11 | 0,79 | 0,47 | +| MTK | 35,49 | 29,12 | 23,27 | 18,21 | 13,81 | 9,87 | 6,92 | 4,67 | 3,11 | 2,04 | + +![Line graph showing average throughput loss [%] vs ACIR [dB] for Ericsson, THALES, and MTK. The graph shows that as ACIR increases, the throughput loss decreases for all three vendors. MTK shows the highest loss, while THALES shows the lowest loss.](9f92854fe6ecaf47760515c891a4fccc_img.jpg) + +| ACIR [dB] | Ericsson [%] | THALES [%] | MTK [%] | +|-----------|--------------|------------|---------| +| 18 | 11 | 11 | 29 | +| 20 | 8 | 8 | 23 | +| 22 | 6 | 6 | 18 | +| 24 | 4 | 4 | 14 | +| 26 | 3 | 3 | 10 | +| 28 | 2 | 2 | 7 | +| 30 | 1 | 1 | 5 | +| 32 | 1 | 1 | 3 | +| 34 | 0 | 0 | 2 | +| 36 | 0 | 0 | 1 | + +Line graph showing average throughput loss [%] vs ACIR [dB] for Ericsson, THALES, and MTK. The graph shows that as ACIR increases, the throughput loss decreases for all three vendors. MTK shows the highest loss, while THALES shows the lowest loss. + +Figure 6.4.2-3: Simulation results for average throughput loss - TN BS with non-AAS antenna + +Table 6.4.2-6: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | 40 | +|----------|-------|-------|-------|-------|-------|-------|------|------|------|------| +| Ericsson | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| THALES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| MTK | 57,18 | 45,86 | 34,92 | 25,60 | 18,05 | 12,29 | 8,15 | 5,31 | 3,42 | 2,19 | + +![Line graph showing 5%-tile throughput loss [%] vs ACIR [dB] for Ericsson, THALES, and MTK. The graph shows that as ACIR increases, the 5%-tile throughput loss decreases for all three vendors. MTK shows the highest loss, while THALES shows the lowest loss (0%).](1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg) + +| ACIR [dB] | Ericsson [%] | THALES [%] | MTK [%] | +|-----------|--------------|------------|---------| +| 22 | 0 | 0 | 57,18 | +| 24 | 0 | 0 | 45,86 | +| 26 | 0 | 0 | 34,92 | +| 28 | 0 | 0 | 25,60 | +| 30 | 0 | 0 | 18,05 | +| 32 | 0 | 0 | 12,29 | +| 34 | 0 | 0 | 8,15 | +| 36 | 0 | 0 | 5,31 | +| 38 | 0 | 0 | 3,42 | +| 40 | 0 | 0 | 2,19 | + +Line graph showing 5%-tile throughput loss [%] vs ACIR [dB] for Ericsson, THALES, and MTK. The graph shows that as ACIR increases, the 5%-tile throughput loss decreases for all three vendors. MTK shows the highest loss, while THALES shows the lowest loss (0%). + +Figure 6.4.2-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +**Table 6.4.2-7: Interpolated ACIR values for Scenario 2 to meet the 5% throughput loss criteria - TN BS with non-AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Ericsson | Average | 31.38 | +| | 5%-tile | NA | +| Thales | Average | 24.56 | +| | 5%-tile | NA | +| MTK | Average | 31.71 | +| | 5%-tile | 36.33 | + +**Table 6.4.2-8: Average ACIR values in the above worse case for Scenario 2 TN BS with non-AAS antenna** + +| | Scenario 2 | +|-----------------|------------| +| ACIR value [dB] | 29.22 | + +### 6.4.3 Scenario 3: 2GHz NTN DL interfering TN DL + +#### 6.4.3.1 LEO Class + +The co-existence results from all concerned options in this scenario were evaluated, and it has been agreed to select the NR-NTN LEO-600 DL interfering the NR DL equipped with AAS antenna that deployed in rural environment as the most stringent case for LEO class. + +**Table 6.4.3.1-1: Simulation results for average throughput loss - TN BS with AAS antenna** + +| ACIR[dB] | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | +|----------|-------|-------|-------|-------|------|------|------|------|------|------| +| Qualcomm | 21.02 | 16.68 | 12.34 | 8.94 | 6.48 | 4.03 | 2.98 | 1.93 | 1.21 | 0.84 | +| Samsung | 20.06 | 15.28 | 11.24 | 8.00 | 5.52 | 3.72 | 2.45 | 1.60 | 1.03 | 0.66 | +| MTK | 25.22 | 19.06 | 13.86 | 9.70 | 6.66 | 4.41 | 2.92 | 1.90 | 1.22 | 0.77 | +| ZTE | 16.65 | 12.34 | 8.84 | 6.15 | 4.17 | 2.77 | 1.81 | 1.17 | 0.75 | 0.48 | +| Ericsson | | | | | | 3.7 | 2.4 | 1.6 | 1.0 | | +| Huawei | | | | | 5.94 | 3.97 | 2.52 | 1.64 | 1.24 | | +| CATT | 17.3 | 12.2 | 10.1 | 8.3 | 6.6 | 4.7 | | | | | +| Xiaomi | 30.71 | 23.92 | 17.92 | 12.93 | 9.01 | 6.11 | 4.05 | 2.64 | 1.70 | 1.09 | + +![Figure 6.4.3.1-1: Line graph showing average throughput loss [%] vs ACIR [dB] for TN BS with AAS antenna. The graph shows data for Qualcomm, Samsung, MTK, ZTE, Ericsson, Huawei, CATT, and Xiaomi. Loss decreases as ACIR increases from 10 to 28 dB.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +| ACIR [dB] | Qualcomm | Samsung | MTK | ZTE | Ericsson | Huawei | CATT | Xiaomi | +|-----------|----------|---------|------|------|----------|--------|------|--------| +| 10 | 21.0 | 20.0 | 25.0 | 17.0 | - | 17.0 | 17.0 | 31.0 | +| 12 | 17.0 | 15.0 | 19.0 | 12.0 | - | 12.0 | 12.0 | 24.0 | +| 14 | 12.0 | 11.0 | 14.0 | 9.0 | - | 9.0 | 9.0 | 18.0 | +| 16 | 9.0 | 8.0 | 10.0 | 6.0 | - | 6.0 | 6.0 | 13.0 | +| 18 | 7.0 | 6.0 | 7.0 | 4.0 | - | 4.0 | 4.0 | 9.0 | +| 20 | 5.0 | 4.0 | 5.0 | 3.0 | - | 3.0 | 3.0 | 6.0 | +| 22 | 4.0 | 3.0 | 4.0 | 2.0 | - | 2.0 | 2.0 | 4.0 | +| 24 | 3.0 | 2.0 | 3.0 | 1.5 | - | 1.5 | 1.5 | 3.0 | +| 26 | 2.0 | 1.5 | 2.0 | 1.0 | - | 1.0 | 1.0 | 2.0 | +| 28 | 1.0 | 1.0 | 1.0 | 0.5 | - | 0.5 | 0.5 | 1.0 | + +Figure 6.4.3.1-1: Line graph showing average throughput loss [%] vs ACIR [dB] for TN BS with AAS antenna. The graph shows data for Qualcomm, Samsung, MTK, ZTE, Ericsson, Huawei, CATT, and Xiaomi. Loss decreases as ACIR increases from 10 to 28 dB. + +Figure 6.4.3.1-1: Simulation results for average throughput loss - TN BS with AAS antenna + +Table 6.4.3.1-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | +|----------|-------|-------|-------|-------|-------|------|------|------|------|------| +| Qualcomm | 37.78 | 28.51 | 21.12 | 13.72 | 10.16 | 6.60 | 4.18 | 2.89 | | | +| Samsung | 27.10 | 19.19 | 13.13 | 8.76 | 5.73 | 3.71 | 2.37 | 1.51 | 0.97 | 0.62 | +| MTK | 37.56 | 27.47 | 19.31 | 13.11 | 8.69 | 5.67 | 3.65 | 2.33 | 1.49 | 0.94 | +| ZTE | 16.27 | 10.85 | 7.06 | 4.59 | 2.82 | 1.91 | 1.31 | 0.88 | 0.60 | 0.39 | +| Ericsson | | | | 9.8 | 6.2 | 4.5 | 2.8 | | | | +| Huawei | | | 8.61 | 5.01 | 3.12 | 1.94 | 1.32 | | | | +| CATT | 42.07 | 32.30 | 22.43 | 15.88 | 10.74 | 7.90 | 4.40 | | | | +| Xiaomi | 38.87 | 28.90 | 20.59 | 14.15 | 9.47 | 6.22 | 4.03 | 2.59 | | | + +![Figure 6.4.3.1-2: Line graph showing average throughput loss [%] vs ACIR [dB] for TN BS with AAS antenna. The graph shows data for Qualcomm, Samsung, MTK, ZTE, Ericsson, Huawei, CATT, and Xiaomi. Loss decreases as ACIR increases from 14 to 32 dB.](cc7bd229cf6c181b389c7a43184af609_img.jpg) + +| ACIR [dB] | Qualcomm | Samsung | MTK | ZTE | Ericsson | Huawei | CATT | Xiaomi | +|-----------|----------|---------|-------|-------|----------|--------|-------|--------| +| 14 | 37.78 | 27.10 | 37.56 | 16.27 | - | - | 42.07 | 38.87 | +| 16 | 28.51 | 19.19 | 27.47 | 10.85 | - | - | 32.30 | 28.90 | +| 18 | 21.12 | 13.13 | 19.31 | 7.06 | - | 8.61 | 22.43 | 20.59 | +| 20 | 13.72 | 8.76 | 13.11 | 4.59 | 9.8 | 5.01 | 15.88 | 14.15 | +| 22 | 10.16 | 5.73 | 8.69 | 2.82 | 6.2 | 3.12 | 10.74 | 9.47 | +| 24 | 6.60 | 3.71 | 5.67 | 1.91 | 4.5 | 1.94 | 7.90 | 6.22 | +| 26 | 4.18 | 2.37 | 3.65 | 1.31 | 2.8 | 1.32 | 4.40 | 4.03 | +| 28 | 2.89 | 1.51 | 2.33 | 0.88 | - | - | - | 2.59 | +| 30 | - | 0.97 | 1.49 | 0.60 | - | - | - | - | +| 32 | - | 0.62 | 0.94 | 0.39 | - | - | - | - | + +Figure 6.4.3.1-2: Line graph showing average throughput loss [%] vs ACIR [dB] for TN BS with AAS antenna. The graph shows data for Qualcomm, Samsung, MTK, ZTE, Ericsson, Huawei, CATT, and Xiaomi. Loss decreases as ACIR increases from 14 to 32 dB. + +Figure 6.4.3.1-2: Simulation results for average throughput loss - TN BS with AAS antenna + +**Table 6.4.3.1-3: Interpolated ACIR values for Scenario 3 to meet the 5% throughput loss criteria - TN BS with AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Qualcomm | Average | 19.21 | +| | 5%-tile | 25.32 | +| Samsung | Average | 18.58 | +| | 5%-tile | 22.72 | +| MTK | Average | 19.48 | +| | 5%-tile | 24.66 | +| ZTE | Average | 17.16 | +| | 5%-tile | 19.67 | +| Ericsson | Average | | +| | 5%-tile | 23.41 | +| Huawei | Average | 18.95 | +| | 5%-tile | 20.01 | +| CATT | Average | 19.68 | +| | 5%-tile | 25.66 | +| Xiaomi | Average | 21.01 | +| | 5%-tile | 25.11 | + +**Table 6.4.3.1-4: Average ACIR of 5%-tile values in the above worse case for Scenario 3 - TN BS with AAS antenna** + +| | Scenario 3 | +|-----------------|------------| +| ACIR value [dB] | 23.32 | + +**Table 6.4.3.1-5: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | +|----------|-------|-------|-------|-------|------|------|------|------|------|------| +| Samsung | 10,42 | 7,20 | 4,86 | 3,21 | 2,09 | 1,35 | 0,86 | 0,55 | 0,35 | 0,22 | +| MTK | 27,33 | 20,75 | 15,22 | 10,59 | 7,32 | 4,81 | 3,29 | 2,16 | 1,45 | 0,93 | +| ZTE | 13,12 | 9,28 | 6,37 | 4,27 | 2,81 | 1,82 | 1,17 | 0,75 | 0,48 | 0,30 | +| THALES | NA | 15,84 | 11,43 | 7,99 | 5,43 | 3,61 | 2,35 | 1,52 | 0,97 | 0,62 | +| Ericsson | NA | NA | NA | NA | NA | 3,0 | 2,0 | 1,3 | 0,8 | 0,5 | + +![Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for TN BS with non-AAS antenna. The graph plots five data series: Samsung (blue), MTK (orange), ZTE (grey), THALES (yellow), and Ericsson (light blue). The x-axis ranges from 10 to 28 dB ACIR, and the y-axis ranges from 0.00 to 30.00% loss. All series show a decreasing trend in loss as ACIR increases. MTK starts at the highest loss (approx. 27.33% at 10 dB) and ends at the lowest (approx. 0.93% at 28 dB). Samsung starts at approx. 10.42% and ends at approx. 0.22%.](2031413999bae2fee78687b844944be6_img.jpg) + +| ACIR [dB] | Samsung (%) | MTK (%) | ZTE (%) | THALES (%) | Ericsson (%) | +|-----------|-------------|---------|---------|------------|--------------| +| 10 | 10.42 | 27.33 | 13.12 | NA | NA | +| 12 | 7.20 | 20.75 | 9.28 | 15.84 | NA | +| 14 | 4.86 | 15.22 | 6.37 | 11.43 | NA | +| 16 | 3.21 | 10.59 | 4.27 | 7.99 | NA | +| 18 | 2.09 | 7.32 | 2.81 | 5.43 | NA | +| 20 | 1.35 | 4.81 | 1.82 | 3.61 | 3.0 | +| 22 | 0.86 | 3.29 | 1.17 | 2.35 | 2.0 | +| 24 | 0.55 | 2.16 | 0.75 | 1.52 | 1.3 | +| 26 | 0.35 | 1.45 | 0.48 | 0.97 | 0.8 | +| 28 | 0.22 | 0.93 | 0.30 | 0.62 | 0.5 | + +Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for TN BS with non-AAS antenna. The graph plots five data series: Samsung (blue), MTK (orange), ZTE (grey), THALES (yellow), and Ericsson (light blue). The x-axis ranges from 10 to 28 dB ACIR, and the y-axis ranges from 0.00 to 30.00% loss. All series show a decreasing trend in loss as ACIR increases. MTK starts at the highest loss (approx. 27.33% at 10 dB) and ends at the lowest (approx. 0.93% at 28 dB). Samsung starts at approx. 10.42% and ends at approx. 0.22%. + +**Figure 6.4.3.1-3: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +**Table 6.4.3.1-6: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | +|----------|-------|-------|-------|-------|-------|------|------|------|------|------| +| Samsung | 18,31 | 12,33 | 8,12 | 5,28 | 3,40 | 2,17 | 1,38 | 0,87 | 0,55 | 0,35 | +| MTK | 39,11 | 28,66 | 20,18 | 13,63 | 9,06 | 5,92 | 3,81 | 2,44 | 1,55 | 0,98 | +| ZTE | 21,75 | 14,80 | 9,68 | 6,52 | 4,36 | 2,83 | 1,82 | 1,20 | 0,71 | 0,39 | +| THALES | 47,09 | 35,73 | 25,48 | 17,17 | 11,08 | 6,65 | 3,6 | 2,22 | 1,39 | 0,83 | +| Ericsson | NA | NA | NA | 7,2 | 4,5 | 2,9 | 1,8 | 1,2 | NA | NA | + +![Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for five manufacturers (Samsung, MTK, ZTE, THALES, Ericsson). The x-axis ranges from 10 to 28 dB ACIR, and the y-axis ranges from 0.00 to 50.00% loss. All curves show a decreasing trend as ACIR increases. THALES starts at the highest loss (~47% at 14 dB ACIR), while Samsung starts at the lowest (~18% at 14 dB ACIR). All curves converge towards 0% loss as ACIR increases beyond 26 dB.](8e8ee6d2f8a17f2da03923bc97e226d7_img.jpg) + +| ACIR [dB] | Samsung | MTK | ZTE | THALES | Ericsson | +|-----------|---------|-------|-------|--------|----------| +| 10 | 18.31 | 39.11 | 21.75 | 47.09 | - | +| 12 | 12.33 | 28.66 | 14.80 | 35.73 | - | +| 14 | 8.12 | 20.18 | 9.68 | 25.48 | - | +| 16 | 5.28 | 13.63 | 6.52 | 17.17 | - | +| 18 | 3.40 | 9.06 | 4.36 | 11.08 | 7.2 | +| 20 | 2.17 | 5.92 | 2.83 | 6.65 | 4.5 | +| 22 | 1.38 | 3.81 | 1.82 | 3.6 | 2.9 | +| 24 | 0.87 | 2.44 | 1.20 | 2.22 | 1.2 | +| 26 | 0.55 | 1.55 | 0.71 | 1.39 | - | +| 28 | 0.35 | 0.98 | 0.39 | 0.83 | - | + +Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for five manufacturers (Samsung, MTK, ZTE, THALES, Ericsson). The x-axis ranges from 10 to 28 dB ACIR, and the y-axis ranges from 0.00 to 50.00% loss. All curves show a decreasing trend as ACIR increases. THALES starts at the highest loss (~47% at 14 dB ACIR), while Samsung starts at the lowest (~18% at 14 dB ACIR). All curves converge towards 0% loss as ACIR increases beyond 26 dB. + +**Figure 6.4.3.1-4: Simulation results for average throughput loss - TN BS with non-AAS antenna****Table 6.4.3.1-7: Interpolated ACIR values for Scenario 3 LEO Class to meet the 5% throughput loss criteria - TN BS with non-AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Samsung | Average | 13.88 | +| | 5%-tile | 20.30 | +| MTK | Average | 19.85 | +| | 5%-tile | 24.87 | +| ZTE | Average | 15.3 | +| | 5%-tile | 21.41 | +| THALES | Average | 18.47 | +| | 5%-tile | 25.08 | +| Ericsson | Average | | +| | 5%-tile | 21.63 | + +**Table 6.4.3.1-8: Average ACIR of 5%-tile values in the above worse case for Scenario 3 LEO Class - TN BS with non-AAS antenna** + +| | Scenario 3 | +|-----------------|------------| +| ACIR value [dB] | 22.66 | + +#### 6.4.3.2 GEO Class + +The co-existence results from all concerned options in this scenario were evaluated, and it has been agreed to select the NR-NTN GEO DL interfering the NR DL equipped with AAS antenna that deployed in rural environment as the most stringent case for GEO class. + +Table 6.4.3.2-1: Simulation results for average throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | +|----------|-------|-------|-------|-------|-------|-------|-------|------|------|------| +| Qualcomm | 15.65 | 11.48 | 8.25 | 5.96 | 3.67 | 2.70 | 1.74 | 1.09 | | | +| Samsung | 15.14 | 11.09 | 7.86 | 5.41 | 3.63 | 2.39 | 1.55 | 1.00 | 0.64 | 0.41 | +| MTK | 20.35 | 15.03 | 10.74 | 7.33 | 4.79 | 3.15 | 2.05 | 1.32 | 0.84 | 0.53 | +| ZTE | 11.39 | 8.09 | 5.58 | 3.76 | 2.48 | 1.62 | 1.04 | 0.67 | 0.42 | 0.27 | +| Ericsson | | | | | 3.9 | 2.5 | 1.6 | 1.0 | | | +| CATT | 9.73% | 7.94% | 6.42% | 5.15% | 4.08% | 3.20% | 2.48% | | | | +| Xiaomi | 22.47 | 16.68 | 11.93 | 8.25 | 5.56 | 3.67 | 2.39 | 1.54 | 0.98 | 0.62 | + +![Line graph showing average throughput loss [%] vs ACIR [dB] for various manufacturers. The Y-axis ranges from 0.00 to 40.00 in increments of 5.00. The X-axis ranges from 2 to 20 in increments of 2. Most manufacturers show a decreasing trend in loss as ACIR increases. Qualcomm, Samsung, MTK, ZTE, and Xiaomi show higher losses at lower ACIR values, while Ericsson, CATT, and ZTE show lower losses. CATT's loss is zero for ACIR values of 2, 4, 6, 8, 10, 12, 14, 16, 18, and 20 dB.](449d2799e97657d8fa5897b2e74a88bd_img.jpg) + +| ACIR [dB] | Qualcomm | Samsung | MTK | ZTE | Ericsson | CATT | Xiaomi | +|-----------|----------|---------|-------|-------|----------|------|--------| +| 2 | 15.65 | 15.14 | 20.35 | 11.39 | | 0.00 | 22.47 | +| 4 | 11.48 | 11.09 | 15.03 | 8.09 | | 0.00 | 16.68 | +| 6 | 8.25 | 7.86 | 10.74 | 5.58 | | 0.00 | 11.93 | +| 8 | 5.96 | 5.41 | 7.33 | 3.76 | | 0.00 | 8.25 | +| 10 | 3.67 | 3.63 | 4.79 | 2.48 | 3.9 | 0.00 | 5.56 | +| 12 | 2.70 | 2.39 | 3.15 | 1.62 | 2.5 | 0.00 | 3.67 | +| 14 | 1.74 | 1.55 | 2.05 | 1.04 | 1.6 | 0.00 | 2.39 | +| 16 | 1.09 | 1.00 | 1.32 | 0.67 | 1.0 | 0.00 | 1.54 | +| 18 | | 0.64 | 0.84 | 0.42 | | 0.00 | 0.98 | +| 20 | | 0.41 | 0.53 | 0.27 | | 0.00 | 0.62 | + +Line graph showing average throughput loss [%] vs ACIR [dB] for various manufacturers. The Y-axis ranges from 0.00 to 40.00 in increments of 5.00. The X-axis ranges from 2 to 20 in increments of 2. Most manufacturers show a decreasing trend in loss as ACIR increases. Qualcomm, Samsung, MTK, ZTE, and Xiaomi show higher losses at lower ACIR values, while Ericsson, CATT, and ZTE show lower losses. CATT's loss is zero for ACIR values of 2, 4, 6, 8, 10, 12, 14, 16, 18, and 20 dB. + +Figure 6.4.3.2-1: Simulation results for average throughput loss - TN BS with AAS antenna + +Table 6.4.3.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 4 | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | +|----------|-------|-------|-------|-------|-------|------|------|------|------|------| +| Qualcomm | 35.59 | 26.64 | 19.54 | 12.44 | 9.23 | 6.02 | 3.81 | | | | +| Samsung | 26.43 | 18.68 | 12.77 | 8.49 | 5.55 | 3.58 | 2.30 | 1.46 | 0.93 | 0.59 | +| MTK | 42.08 | 31.47 | 22.53 | 15.53 | 10.41 | 6.83 | 4.43 | 2.84 | 1.81 | 1.15 | +| ZTE | 14.19 | 9.38 | 6.19 | 4.19 | 2.58 | 1.62 | 1.00 | 0.57 | 0.38 | 0.25 | +| Ericsson | | | | 8.3 | 5.6 | 3.5 | 2.2 | | | | +| CATT | 20.86 | 19.31 | 14.49 | 13.09 | 7.33 | 5.23 | 4.17 | | | | +| Xiaomi | 36.44 | 26.85 | 18.99 | 12.97 | 8.65 | 5.67 | 3.66 | 2.35 | 1.50 | | + +![Figure 6.4.3.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna. The graph shows Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (4 to 22). Seven data series are plotted: Qualcomm (orange), Samsung (grey), MTK (yellow), ZTE (light blue), Ericsson (green), CATT (dark blue), and Xiaomi (brown). All series show a decreasing trend in loss as ACIR increases. ZTE starts at approximately 14.5% loss at 4 dB ACIR and drops to near 0% at 22 dB. MTK starts at 40% loss at 4 dB and drops to about 1% at 22 dB.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +Figure 6.4.3.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna. The graph shows Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (4 to 22). Seven data series are plotted: Qualcomm (orange), Samsung (grey), MTK (yellow), ZTE (light blue), Ericsson (green), CATT (dark blue), and Xiaomi (brown). All series show a decreasing trend in loss as ACIR increases. ZTE starts at approximately 14.5% loss at 4 dB ACIR and drops to near 0% at 22 dB. MTK starts at 40% loss at 4 dB and drops to about 1% at 22 dB. + +Figure 6.4.3.2-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +Table 6.4.3.2-3: Interpolated ACIR values for Scenario 3 GEO Class to meet the 5% throughput loss criteria - TN BS with AAS antenna + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Qualcomm | Average | 8.84 | +| | 5%-tile | 14.46 | +| Samsung | Average | 8.46 | +| | 5%-tile | 12.56 | +| MTK | Average | 9.83 | +| | 5%-tile | 15.53 | +| ZTE | Average | 6.64 | +| | 5%-tile | 9.2 | +| Ericsson | Average | | +| | 5%-tile | 12.57 | +| CATT | Average | 8.28 | +| | 5%-tile | 14.43 | +| Xiaomi | Average | 10.59 | +| | 5%-tile | 14.67 | + +Table 6.4.3.2-4: Average ACIR of 5%-tile values in the above worse case for Scenario 3 GEO Class - TN BS with AAS antenna + +| | Scenario 3 GEO Class | +|-----------------|----------------------| +| ACIR value [dB] | 13.35 | + +Table 6.4.3.2-5: Simulation results for average throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16 | 18 | +|----------|-------|-------|-------|-------|------|------|------|------|------|------| +| Samsung | 10.22 | 7.04 | 4.73 | 3.12 | 2.03 | 1.31 | 0.83 | 0.53 | 0.34 | 0.21 | +| MTK | 28.38 | 21.62 | 15.91 | 11.36 | 7.76 | 5.17 | 3.37 | 2.24 | 1.34 | 0.85 | +| ZTE | 11.89 | 8.33 | 5.68 | 3.79 | 2.48 | 1.60 | 1.03 | 0.66 | 0.42 | 0.26 | +| THALES | | | | | | | 2.27 | 1.46 | 0.94 | 0.6 | +| Ericsson | | | | | | 3.2 | 2.1 | 1.3 | 0.9 | 0.5 | + +![Figure 6.4.3.2-3: Simulation results for average throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (0 to 18). Five lines represent Samsung (orange), MTK (grey), ZTE (yellow), THALES (blue), and Ericsson (green). MTK shows the highest loss, starting at ~28.5% at 0 dB ACIR and decreasing to ~0.5% at 18 dB. Samsung, ZTE, THALES, and Ericsson show lower losses, starting between 10% and 12% at 0 dB and decreasing to near 0% at 18 dB.](b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg) + +Figure 6.4.3.2-3: Simulation results for average throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 40.00) versus ACIR [dB] on the x-axis (0 to 18). Five lines represent Samsung (orange), MTK (grey), ZTE (yellow), THALES (blue), and Ericsson (green). MTK shows the highest loss, starting at ~28.5% at 0 dB ACIR and decreasing to ~0.5% at 18 dB. Samsung, ZTE, THALES, and Ericsson show lower losses, starting between 10% and 12% at 0 dB and decreasing to near 0% at 18 dB. + +Figure 6.4.3.2-3: Simulation results for average throughput loss - TN BS with non-AAS antenna + +Table 6.4.3.2-6: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | +|----------|-------|-------|-------|-------|------|------|------|------|------|------| +| Samsung | 11,97 | 7,88 | 5,11 | 3,28 | 2,09 | 1,33 | 0,85 | 0,53 | 0,34 | 0,21 | +| MTK | 31,86 | 22,83 | 15,63 | 10,47 | 6,87 | 4,45 | 2,85 | 1,82 | 1,16 | 0,73 | +| ZTE | 13,72 | 9,33 | 6,08 | 3,88 | 2,38 | 1,50 | 1,13 | 0,75 | 0,55 | 0,30 | +| THALES | | | | 9,14 | 5,54 | 3,6 | 2,22 | 1,39 | 0,83 | 0,55 | +| Ericsson | | | 9,1 | 5,9 | 4,2 | 2,8 | 1,9 | | | | + +![Figure 6.4.3.2-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 35.00) versus ACIR [dB] on the x-axis (6 to 24). Five lines represent Samsung (blue), MTK (orange), ZTE (grey), THALES (yellow), and Ericsson (light blue). MTK shows the highest loss, starting at ~32% at 6 dB ACIR and decreasing to ~1% at 24 dB. Samsung, ZTE, THALES, and Ericsson show lower losses, starting between 12% and 14% at 6 dB and decreasing to near 0% at 24 dB.](bf5971de45ccc2d1a9e437d0f486ee08_img.jpg) + +Figure 6.4.3.2-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0.00 to 35.00) versus ACIR [dB] on the x-axis (6 to 24). Five lines represent Samsung (blue), MTK (orange), ZTE (grey), THALES (yellow), and Ericsson (light blue). MTK shows the highest loss, starting at ~32% at 6 dB ACIR and decreasing to ~1% at 24 dB. Samsung, ZTE, THALES, and Ericsson show lower losses, starting between 12% and 14% at 6 dB and decreasing to near 0% at 24 dB. + +Figure 6.4.3.2-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +**Table 6.4.3.2-7: Interpolated ACIR values for Scenario 3 GEO Class to meet the 5% throughput loss criteria - TN BS with non-AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Samsung | Average | 3.77 | +| | 5%-tile | 10.12 | +| MTK | Average | 10.19 | +| | 5%-tile | 15.55 | +| ZTE | Average | 4.72 | +| | 5%-tile | 10.98 | +| THALES | Average | NA | +| | 5%-tile | 14.56 | +| Ericsson | Average | NA | +| | 5%-tile | 13.06 | + +**Table 6.4.3.2-8: Average ACIR of 5%-tile values in the above worse case for Scenario 3 GEO Class - TN BS with non-AAS antenna** + +| | Scenario 3 | +|-----------------|------------| +| ACIR value [dB] | 12.85 | + +### 6.4.4 Scenario 4: 2GHz NTN UL interfering TN UL + +The co-existence results from all concerned options in this scenario were evaluated, and it has been agreed to select the NR-NTN GEO UL interfering the NR UL equipped with both AAS and non-AAS antenna that deployed in urban environment as the most stringent case. + +**Table 6.4.4-1: Simulation results for average throughput loss - TN BS with AAS antenna** + +| ACIR[dB] | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | +|-----------------------|-------|-------|------|------|------|------|------|------|------|------| +| Qualcomm | 12.60 | 10.78 | 8.96 | 7.42 | 6.18 | 4.93 | 4.11 | 3.29 | 2.63 | 2.12 | +| Samsung | 10.83 | 8.69 | 6.92 | 5.47 | 4.30 | 3.35 | 2.60 | 2.00 | 1.53 | 1.17 | +| MTK | 12.16 | 10.25 | 8.40 | 6.66 | 5.09 | 3.75 | 2.67 | 1.84 | 1.24 | 0.82 | +| ZTE | 9.35 | 7.39 | 5.59 | 4.38 | 3.38 | 2.65 | 2.05 | 1.63 | 1.24 | 0.94 | +| Ericsson 1 | | | | | | | | 1.5 | 1.2 | 1.0 | +| CATT | 2.72 | 2.26 | 1.88 | 1.58 | | | | | | | +| Xiaomi | 10.31 | 8.30 | 6.66 | 5.34 | 4.27 | 3.42 | 2.74 | 2.19 | 1.76 | 1.41 | + +NOTE 1: This result is derived by observing the NR sector having an NR-NTN transmitting UE at its sector edge. + +![Line graph showing average throughput loss [%] vs ACIR [dB] for various vendors (Qualcomm, Samsung, MTK, ZTE, Ericsson (*), CATT, Xiaomi) with TN BS and AAS antenna. The graph shows that as ACIR increases from 10 dB to 28 dB, the throughput loss decreases for all vendors. Qualcomm and MTK show the highest loss, while CATT shows the lowest.](3881b390d52f27a35faedfc170916c86_img.jpg) + +| ACIR [dB] | Qualcomm | Samsung | MTK | ZTE | Ericsson (*) | CATT | Xiaomi | +|-----------|----------|---------|------|-----|--------------|------|--------| +| 10 | 12.5 | 10.5 | 12.5 | 9.5 | 10.5 | 2.5 | 10.5 | +| 12 | 11.0 | 9.0 | 11.0 | 8.0 | 9.0 | 2.0 | 9.0 | +| 14 | 9.5 | 7.5 | 9.5 | 6.5 | 7.5 | 1.5 | 7.5 | +| 16 | 8.0 | 6.0 | 8.0 | 5.0 | 6.0 | 1.0 | 6.0 | +| 18 | 7.0 | 5.0 | 7.0 | 4.0 | 5.0 | - | 5.0 | +| 20 | 6.0 | 4.0 | 6.0 | 3.0 | 4.0 | - | 4.0 | +| 22 | 5.0 | 3.0 | 5.0 | 2.0 | 3.0 | - | 3.0 | +| 24 | 4.0 | 2.0 | 4.0 | 1.0 | 2.0 | - | 2.0 | +| 26 | 3.0 | 1.0 | 3.0 | 0.5 | 1.0 | - | 1.0 | +| 28 | 2.0 | 0.5 | 2.0 | 0.2 | 0.5 | - | 0.5 | + +Line graph showing average throughput loss [%] vs ACIR [dB] for various vendors (Qualcomm, Samsung, MTK, ZTE, Ericsson (\*), CATT, Xiaomi) with TN BS and AAS antenna. The graph shows that as ACIR increases from 10 dB to 28 dB, the throughput loss decreases for all vendors. Qualcomm and MTK show the highest loss, while CATT shows the lowest. + +Figure 6.4.4-1: Simulation results for average throughput loss - TN BS with AAS antenna + +Table 6.4.4-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | +|-----------------------|-------|-------|-------|-------|------|------|------|------|------|------| +| Qualcomm | 24.62 | 20.07 | 15.53 | 12.02 | 9.55 | 7.08 | 5.83 | 4.58 | | | +| Samsung | 16.71 | 12.55 | 9.44 | 7.15 | 5.47 | 4.19 | 3.19 | 2.44 | 1.86 | 1.41 | +| MTK | 20.91 | 14.93 | 10.33 | 6.95 | 4.59 | 2.98 | 1.92 | 1.23 | 0.78 | 0.49 | +| ZTE | 11.43 | 8.86 | 7.23 | 6.23 | 4.71 | 3.34 | 2.66 | 1.47 | 0.87 | 0.75 | +| Ericsson 1 | | | 7.9 | 7.1 | 4.8 | 4.6 | 0.5 | 0.5 | | | +| CATT | 8.83 | 7.49 | 5.57 | 4.10 | 3.44 | 2.95 | | | | | +| Xiaomi | 16.47 | 11.96 | 8.45 | 5.79 | 3.88 | 2.55 | 1.66 | 1.07 | | | + +NOTE 1: This result is derived by observing the NR sector having an NR-NTN transmitting UE at its sector edge. + +![Line graph showing 5%-tile throughput loss [%] vs ACIR [dB] for various vendors (Qualcomm, Samsung, MTK, ZTE, Ericsson (*), CATT, Xiaomi) with TN BS and AAS antenna. The graph shows that as ACIR increases from 20 dB to 38 dB, the 5%-tile throughput loss decreases for all vendors. Qualcomm shows the highest loss, while CATT and Ericsson show the lowest.](f9d11004ac6966f27936c8d01e579313_img.jpg) + +| ACIR [dB] | Qualcomm | Samsung | MTK | ZTE | Ericsson (*) | CATT | Xiaomi | +|-----------|----------|---------|-------|-------|--------------|------|--------| +| 20 | 24.62 | 16.71 | 20.91 | 11.43 | - | 8.83 | 16.47 | +| 22 | 20.07 | 12.55 | 14.93 | 8.86 | - | 7.49 | 11.96 | +| 24 | 15.53 | 9.44 | 10.33 | 7.23 | 7.9 | 5.57 | 8.45 | +| 26 | 12.02 | 7.15 | 6.95 | 6.23 | 7.1 | 4.10 | 5.79 | +| 28 | 9.55 | 5.47 | 4.59 | 4.71 | 4.8 | 3.44 | 3.88 | +| 30 | 7.08 | 4.19 | 2.98 | 3.34 | 4.6 | 2.95 | 2.55 | +| 32 | 5.83 | 3.19 | 1.92 | 2.66 | 0.5 | - | 1.66 | +| 34 | 4.58 | 2.44 | 1.23 | 1.47 | 0.5 | - | 1.07 | +| 36 | - | 1.86 | 0.78 | 0.87 | - | - | - | +| 38 | - | 1.41 | 0.49 | 0.75 | - | - | - | + +Line graph showing 5%-tile throughput loss [%] vs ACIR [dB] for various vendors (Qualcomm, Samsung, MTK, ZTE, Ericsson (\*), CATT, Xiaomi) with TN BS and AAS antenna. The graph shows that as ACIR increases from 20 dB to 38 dB, the 5%-tile throughput loss decreases for all vendors. Qualcomm shows the highest loss, while CATT and Ericsson show the lowest. + +Figure 6.4.4-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +**Table 6.4.4-3: Interpolated ACIR values for Scenario 4 to meet the 5% throughput loss criteria - TN BS with AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|-------------|---------|-----------------------| +| Qualcomm | Average | 19.89 | +| | 5%-tile | 33.33 | +| Samsung | Average | 16.80 | +| | 5%-tile | 28.73 | +| MTK | Average | 18.13 | +| | 5%-tile | 27.65 | +| ZTE | Average | 14.98 | +| | 5%-tile | 27.62 | +| Ericsson(*) | Average | | +| | 5%-tile | 27.83 | +| CATT | Average | 3.69 | +| | 5%-tile | 24.78 | +| Xiaomi | Average | 16.64 | +| | 5%-tile | 26.83 | + +**Table 6.4.4-4: Average ACIR of 5%-tile values in the above worse case for Scenario 4 - TN BS with AAS antenna** + +| | Scenario 4 | +|-----------------|------------| +| ACIR value [dB] | 28.11 | + +**Table 6.4.4-5: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | +|-----------------------|-------|------|------|------|------|------|------|------|------|------| +| Samsung | 10,85 | 8,39 | 6,50 | 5,06 | 3,96 | 3,11 | 2,43 | 1,88 | 1,44 | 1,07 | +| MTK | 11,73 | 9,14 | 7,05 | 5,38 | 4,05 | 2,99 | 2,17 | 1,53 | 1,06 | 0,72 | +| ZTE | 6,12 | 5,01 | 4,16 | 3,32 | 2,85 | 2,27 | 1,83 | 1,17 | 0,80 | 0,50 | +| THALES | NA | 0,04 | 0,03 | 0,01 | 0,01 | 0 | 0 | 0 | 0 | 0 | +| Ericsson 1 | NA | NA | NA | NA | NA | NA | NA | NA | NA | 1,2 | + +NOTE 1: This result is derived by observing the NR sector having an NR-NTN transmitting UE at its sector edge. + +![Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for TN BS with non-AAS antenna. The graph plots five data series: Samsung (blue line with circles), MTK (orange line with circles), ZTE (grey line with circles), THALES (yellow line with circles), and Ericsson (light blue line with circles). The x-axis ranges from 12 to 28 dB ACIR, and the y-axis ranges from 0.00 to 14.00% loss. Samsung and MTK show the highest loss, starting around 11.73% and 10.85% respectively at 12 dB ACIR and decreasing to around 0.72% and 1.07% at 28 dB ACIR. ZTE shows a lower loss, starting around 6.12% at 12 dB ACIR and decreasing to 0.50% at 28 dB ACIR. THALES and Ericsson show zero loss across the entire range of ACIR values.](54d490f646eb3cc3b92ec4abf3030a85_img.jpg) + +| ACIR [dB] | Samsung (%) | MTK (%) | ZTE (%) | THALES (%) | Ericsson (%) | +|-----------|-------------|---------|---------|------------|--------------| +| 12 | 10.85 | 11.73 | 6.12 | NA | NA | +| 14 | 8.39 | 9.14 | 5.01 | 0.04 | NA | +| 16 | 6.50 | 7.05 | 4.16 | 0.03 | NA | +| 18 | 5.06 | 5.38 | 3.32 | 0.01 | NA | +| 20 | 3.96 | 4.05 | 2.85 | 0.01 | NA | +| 22 | 3.11 | 2.99 | 2.27 | 0 | NA | +| 24 | 2.43 | 2.17 | 1.83 | 0 | NA | +| 26 | 1.88 | 1.53 | 1.17 | 0 | NA | +| 28 | 1.44 | 1.06 | 0.80 | 0 | NA | +| 28 | 1.07 | 0.72 | 0.50 | 0 | 1.2 | + +Line graph showing simulation results for average throughput loss (%) versus ACIR [dB] for TN BS with non-AAS antenna. The graph plots five data series: Samsung (blue line with circles), MTK (orange line with circles), ZTE (grey line with circles), THALES (yellow line with circles), and Ericsson (light blue line with circles). The x-axis ranges from 12 to 28 dB ACIR, and the y-axis ranges from 0.00 to 14.00% loss. Samsung and MTK show the highest loss, starting around 11.73% and 10.85% respectively at 12 dB ACIR and decreasing to around 0.72% and 1.07% at 28 dB ACIR. ZTE shows a lower loss, starting around 6.12% at 12 dB ACIR and decreasing to 0.50% at 28 dB ACIR. THALES and Ericsson show zero loss across the entire range of ACIR values. + +**Figure 6.4.4-3: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +**Table 6.4.4-6: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | +|----------|-------|-------|-------|------|------|------|------|------|------|------| +| Samsung | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| MTK | 21,98 | 15,18 | 10,19 | 6,70 | 4,34 | 2,79 | 1,78 | 1,13 | 0,72 | 0,45 | +| ZTE | 1,53 | 1,08 | 0,47 | 0,30 | 0,19 | 0,03 | 0,00 | 0,00 | 0,00 | 0,00 | +| THALES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Ericsson | NA | NA | NA | NA | 12,2 | 9,7 | 8,3 | 7,4 | 6,1 | 4,4 | + +NOTE 1: This result is derived by observing the NR sector having an NR-NTN transmitting UE at its sector edge. + +![Line graph showing simulation results for 5%-tile throughput loss (%) versus ACIR [dB] for four manufacturers: MTK, ZTE, THALES, and Ericsson. The x-axis ranges from 20 to 38 dB ACIR, and the y-axis ranges from 0.00 to 25.00% loss. MTK shows the highest loss, starting at ~22% at 20 dB ACIR and decreasing to ~0.45% at 38 dB. Ericsson shows a significant loss at 20 dB ACIR (~12.2%) which decreases to ~4.4% at 38 dB. ZTE and THALES show very low loss, remaining near 0% across the entire range.](4908c132d4fbad657b6fc84561c43fbb_img.jpg) + +| ACIR [dB] | MTK [%] | ZTE [%] | THALES [%] | Ericsson [%] | +|-----------|---------|---------|------------|--------------| +| 20 | 21.98 | 1.53 | 0.00 | NA | +| 22 | 15.18 | 1.08 | 0.00 | NA | +| 24 | 10.19 | 0.47 | 0.00 | NA | +| 26 | 6.70 | 0.30 | 0.00 | NA | +| 28 | 4.34 | 0.19 | 0.00 | 12.2 | +| 30 | 2.79 | 0.03 | 0.00 | 9.7 | +| 32 | 1.78 | 0.00 | 0.00 | 8.3 | +| 34 | 1.13 | 0.00 | 0.00 | 7.4 | +| 36 | 0.72 | 0.00 | 0.00 | 6.1 | +| 38 | 0.45 | 0.00 | 0.00 | 4.4 | + +Line graph showing simulation results for 5%-tile throughput loss (%) versus ACIR [dB] for four manufacturers: MTK, ZTE, THALES, and Ericsson. The x-axis ranges from 20 to 38 dB ACIR, and the y-axis ranges from 0.00 to 25.00% loss. MTK shows the highest loss, starting at ~22% at 20 dB ACIR and decreasing to ~0.45% at 38 dB. Ericsson shows a significant loss at 20 dB ACIR (~12.2%) which decreases to ~4.4% at 38 dB. ZTE and THALES show very low loss, remaining near 0% across the entire range. + +**Figure 6.4.4-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna****Table 6.4.4-7: Interpolated ACIR values for Scenario 4 to meet the 5% throughput loss criteria - TN BS with non-AAS antenna** + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Samsung | Average | 16.11 | +| | 5%-tile | NA | +| MTK | Average | 16.57 | +| | 5%-tile | 27.44 1 | +| ZTE | Average | 12.02 | +| | 5%-tile | 15.46 | +| THALES | Average | NA | +| | 5%-tile | NA | +| Ericsson | Average | NA | +| | 5%-tile | 37.29 1 | + +NOTE 1: According to the principles, this value is not treated for later process. + +**Table 6.4.4-8: Average ACIR of 5%-tile values in the above worse case for Scenario 4 - TN BS with non-AAS antenna** + +| | Scenario 4 | +|-----------------|------------| +| ACIR value [dB] | 15.46 | + +### 6.4.5 Scenario 5: 2GHz NTN UL interfering TN DL + +The co-existence results from all concerned options in this scenario were evaluated, and it has been agreed to select the NR-NTN GEO UL interfering the NR DL equipped with both AAS and non-AAS antenna that deployed in rural environment as the most stringent case. + +**Table 6.4.5-1: Simulation results for average throughput loss - TN BS with AAS antenna** + +| ACIR[dB] | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | +|-------------------------|-------|-------|-------|-------|-------|-------|------|------|------|------| +| Qualcomm (1) | 7.32 | 5.28 | 3.78 | 2.81 | 1.84 | 1.42 | 0.99 | 0.68 | | | +| MTK | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| Xiaomi | 10.31 | 7.75 | 5.70 | 4.11 | 2.91 | 2.03 | 1.39 | 0.94 | | | +| Samsung (1) | 37.13 | 31.30 | 25.62 | 20.30 | 15.53 | 11.43 | 8.07 | 5.43 | 3.43 | 1.98 | +| Samsung (2) | 0.16 | 0.13 | 0.11 | 0.09 | 0.07 | 0.06 | 0.05 | 0.03 | 0.02 | 0.02 | +| Ericsson | 0.00 | | | | | | | | | | + +NOTE 1: These results were derived by adopting free-space path loss model for the links between NR UE and NR-NTN UE. + +NOTE 2: These results were derived by adopting path loss model from TR 38.901[10] for the links between NR UE and NR-NTN UE. + +NOTE3: In the meeting, views are expressed on which propagation model is more appropriate for the links between NR UE and NR-NTN UE. Due to the limited time and the fact that this scenario is not the worst case to determine the NR-NTN UE ACLR, this is not discussed nor concluded. + +![Line graph showing average throughput loss [%] vs ACIR [dB] for various manufacturers. The graph shows that throughput loss decreases as ACIR increases. Samsung (*) shows the highest loss, starting at 37.13% at 12 dB ACIR and dropping to 1.98% at 30 dB ACIR. Xiaomi and Qualcomm (*) show lower losses, starting at 10.31% and 7.32% respectively at 12 dB ACIR and dropping to near 0% at 30 dB ACIR. MTK, Samsung (**), and Ericsson show 0% loss across all ACIR values.](61c876684d8cc2ea8784b52440318350_img.jpg) + +| ACIR [dB] | Qualcomm (*) | MTK | Xiaomi | Samsung (*) | Samsung (**) | Ericsson | +|-----------|--------------|-----|--------|-------------|--------------|----------| +| 12 | 7.32 | NA | 10.31 | 37.13 | 0.16 | 0.00 | +| 14 | 5.28 | NA | 7.75 | 31.30 | 0.13 | 0.00 | +| 16 | 3.78 | NA | 5.70 | 25.62 | 0.11 | 0.00 | +| 18 | 2.81 | NA | 4.11 | 20.30 | 0.09 | 0.00 | +| 20 | 1.84 | NA | 2.91 | 15.53 | 0.07 | 0.00 | +| 22 | 1.42 | NA | 2.03 | 11.43 | 0.06 | 0.00 | +| 24 | 0.99 | NA | 1.39 | 8.07 | 0.05 | 0.00 | +| 26 | 0.68 | NA | 0.94 | 5.43 | 0.03 | 0.00 | +| 28 | | NA | | 3.43 | 0.02 | 0.00 | +| 30 | | NA | | 1.98 | 0.02 | 0.00 | + +Line graph showing average throughput loss [%] vs ACIR [dB] for various manufacturers. The graph shows that throughput loss decreases as ACIR increases. Samsung (\*) shows the highest loss, starting at 37.13% at 12 dB ACIR and dropping to 1.98% at 30 dB ACIR. Xiaomi and Qualcomm (\*) show lower losses, starting at 10.31% and 7.32% respectively at 12 dB ACIR and dropping to near 0% at 30 dB ACIR. MTK, Samsung (\*\*), and Ericsson show 0% loss across all ACIR values. + +**Figure 6.4.5-1: Simulation results for average throughput loss - TN BS with AAS antenna** + +Table 6.4.5-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +| ACIR[dB] | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | +|-------------------------|-------|-------|-------|-------|-------|-------|-------|------|------|------| +| Qualcomm (1) | 23.52 | 17.84 | 13.74 | 9.65 | 7.54 | 5.42 | 3.84 | | | | +| MTK | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | +| Xiaomi | 26.06 | 20.19 | 15.30 | 11.29 | 8.09 | 5.64 | 3.81 | | | | +| Samsung (1) | 72.82 | 63.00 | 52.03 | 40.90 | 30.57 | 21.66 | 14.49 | 9.03 | 5.09 | 2.36 | +| Samsung (2) | 0.99 | 0.82 | 0.66 | 0.53 | 0.41 | 0.30 | 0.21 | 0.14 | 0.08 | 0.04 | +| Ericsson | 0.0 | | | | | | | | | | + +NOTE 1: These results were derived by adopting free-space path loss model for the links between NR UE and NR-NTN UE. + +NOTE 2: These results were derived by adopting path loss model from TR 38.901[10] for the links between NR UE and NR-NTN UE. + +NOTE 3: In the meeting, views are expressed on which propagation model is more appropriate for the links between NR UE and NR-NTN UE. Due to the limited time and the fact that this scenario is not the worst case to determine the NR-NTN UE ACLR, this is not discussed nor concluded. + +![Line graph showing 5%-tile throughput loss [%] vs ACIR [dB] for various sources. The Y-axis ranges from 0.00 to 40.00. The X-axis ranges from 14 to 32. Data series include Qualcomm (*), MTK, Xiaomi, Samsung (*), Samsung (**), and Ericsson. Qualcomm, Xiaomi, and Samsung (*) show a decreasing trend in loss as ACIR increases. Samsung (**) and Ericsson show near-zero loss across the range.](bf5785e70ae74c9228ac60009aeb677e_img.jpg) + +| ACIR [dB] | Qualcomm (*) Loss [%] | Xiaomi Loss [%] | Samsung (*) Loss [%] | Samsung (**) Loss [%] | Ericsson Loss [%] | +|-----------|-----------------------|-----------------|----------------------|-----------------------|-------------------| +| 14 | 23.52 | 26.06 | 72.82 | 0.99 | 0.0 | +| 16 | 17.84 | 20.19 | 63.00 | 0.82 | | +| 18 | 13.74 | 15.30 | 52.03 | 0.66 | | +| 20 | 9.65 | 11.29 | 40.90 | 0.53 | | +| 22 | 7.54 | 8.09 | 30.57 | 0.41 | | +| 24 | 5.42 | 5.64 | 21.66 | 0.30 | | +| 26 | 3.84 | 3.81 | 14.49 | 0.21 | | +| 28 | | | 9.03 | 0.14 | | +| 30 | | | 5.09 | 0.08 | | +| 32 | | | 2.36 | 0.04 | | + +Line graph showing 5%-tile throughput loss [%] vs ACIR [dB] for various sources. The Y-axis ranges from 0.00 to 40.00. The X-axis ranges from 14 to 32. Data series include Qualcomm (\*), MTK, Xiaomi, Samsung (\*), Samsung (\*\*), and Ericsson. Qualcomm, Xiaomi, and Samsung (\*) show a decreasing trend in loss as ACIR increases. Samsung (\*\*) and Ericsson show near-zero loss across the range. + +Figure 6.4.5-2: Simulation results for 5%-tile throughput loss - TN BS with AAS antenna + +Table 6.4.5-3: Interpolated ACIR values for Scenario 5 to meet the 5% throughput loss criteria - TN BS with AAS antenna + +| Source | | Interpolated ACIR[dB] | +|--------------|---------|-----------------------| +| Qualcomm (*) | Average | 14.37 | +| | 5%-tile | 24.53 | +| MTK | Average | | +| | 5%-tile | | +| Xiaomi | Average | 16.88 | +| | 5%-tile | 24.70 | +| Samsung (*) | Average | 26.43 | +| | 5%-tile | 30.07 | +| Samsung (**) | Average | | +| | 5%-tile | | +| Ericsson | Average | | +| | 5%-tile | | + +**Table 6.4.5-4: Average ACIR of 5%-tile values in the above worse case for Scenario 5 - TN BS with AAS antenna** + +| | Scenario 5 | +|-----------------|------------| +| ACIR value [dB] | 26.43 | + +**Table 6.4.5-5: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 0 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16 | 18 | +|----------|------|------|------|------|------|------|------|------|------|------| +| MTK | 3,01 | 2,43 | 1,88 | 1,39 | 0,99 | 0,69 | 0,46 | 0,30 | 0,20 | 0,13 | +| Samsung | 0,32 | 0,27 | 0,23 | 0,20 | 0,17 | 0,14 | 0,12 | 0,10 | 0,08 | 0,06 | +| THALES | NA | NA | NA | NA | NA | NA | 0,07 | 0,06 | 0,05 | 0,04 | + +NOTE1: In the meeting, views are expressed on which propagation model is more appropriate for the links between NR UE and NR-NTN UE. Due to the limited time and the fact that this scenario is not the worst case to determine the NR-NTN UE ACLR, this is not discussed nor concluded. + +![Line graph showing average throughput loss [%] vs ACIR [dB] for MTK, Samsung, and THALES. MTK shows a significant decrease in loss as ACIR increases, while Samsung and THALES show much lower loss values.](e80df82d8dc91b2f758dad02fd449ebd_img.jpg) + +| ACIR [dB] | MTK [%] | Samsung [%] | THALES [%] | +|-----------|---------|-------------|------------| +| 0 | 3.01 | 0.32 | NA | +| 2 | 2.43 | 0.27 | NA | +| 4 | 1.88 | 0.23 | NA | +| 6 | 1.39 | 0.20 | NA | +| 8 | 0.99 | 0.17 | NA | +| 10 | 0.69 | 0.14 | NA | +| 12 | 0.46 | 0.12 | 0.07 | +| 14 | 0.30 | 0.10 | 0.06 | +| 16 | 0.20 | 0.08 | 0.05 | +| 18 | 0.13 | 0.06 | 0.04 | + +Line graph showing average throughput loss [%] vs ACIR [dB] for MTK, Samsung, and THALES. MTK shows a significant decrease in loss as ACIR increases, while Samsung and THALES show much lower loss values. + +**Figure 6.4.5-3: Simulation results for average throughput loss - TN BS with non-AAS antenna** + +**Table 6.4.5-6: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna** + +| ACIR[dB] | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | +|----------|-------|-------|------|------|------|------|------|------|------|------| +| MTK | 15,03 | 10,72 | 7,39 | 4,96 | 3,27 | 2,12 | 1,36 | 0,87 | 0,55 | 0,35 | +| Samsung | 1,07 | 0,92 | 0,77 | 0,65 | 0,53 | 0,44 | 0,34 | 0,27 | 0,20 | 0,15 | +| THALES | | | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +NOTE 1: In the meeting, views are expressed on which propagation model is more appropriate for the links between NR UE and NR-NTN UE. Due to the limited time and the fact that this scenario is not the worst case to determine the NR-NTN UE ACLR, this is not discussed nor concluded. + +![Figure 6.4.5-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna. The graph shows Loss [%] on the y-axis (0.00 to 16.00) versus ACIR [dB] on the x-axis (6 to 24). Three lines are plotted: MTK (blue circles), Samsung (orange diamonds), and THALES (grey squares). MTK shows a steep decline from ~15% loss at 6 dB ACIR to ~0.5% at 24 dB. Samsung and THALES remain near 0% loss across the entire range.](c742b64169a38a7f3f990172019878c8_img.jpg) + +| ACIR [dB] | MTK [%] | Samsung [%] | THALES [%] | +|-----------|---------|-------------|------------| +| 6 | 15.0 | 1.0 | 0.0 | +| 8 | 10.5 | 0.8 | 0.0 | +| 10 | 7.5 | 0.7 | 0.0 | +| 12 | 5.0 | 0.6 | 0.0 | +| 14 | 3.5 | 0.5 | 0.0 | +| 16 | 2.5 | 0.4 | 0.0 | +| 18 | 1.5 | 0.3 | 0.0 | +| 20 | 1.0 | 0.2 | 0.0 | +| 22 | 0.7 | 0.1 | 0.0 | +| 24 | 0.5 | 0.1 | 0.0 | + +Figure 6.4.5-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna. The graph shows Loss [%] on the y-axis (0.00 to 16.00) versus ACIR [dB] on the x-axis (6 to 24). Three lines are plotted: MTK (blue circles), Samsung (orange diamonds), and THALES (grey squares). MTK shows a steep decline from ~15% loss at 6 dB ACIR to ~0.5% at 24 dB. Samsung and THALES remain near 0% loss across the entire range. + +Figure 6.4.5-4: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +Table 6.4.5-7: Interpolated ACIR values for Scenario 5 to meet the 5% throughput loss criteria - TN BS with non-AAS antenna + +| Source | | Interpolated ACIR[dB] | +|-----------------------------------------------------------------------------------|---------|-----------------------| +| MTK | Average | 0 | +| | 5%-tile | 11.97 1 | +| Samsung | Average | 0 | +| | 5%-tile | 0 | +| THALES | Average | 0 | +| | 5%-tile | 0 | +| NOTE 1: According to the principles, this value is not treated for later process. | | | + +Table 6.4.5-8: Average ACIR of 5%-tile values in the above worse case for Scenario 5 - TN BS with non-AAS antenna + +| | Scenario 5 | +|-----------------|------------| +| ACIR value [dB] | 0 | + +### 6.4.6 Scenario 6: 2GHz TN DL interfering NTN UL + +The co-existence results from all concerned options in this scenario were evaluated, and the initial results suggested that the NR-NTN SAN would suffer more interference in urban deployment scenario, considering that the central beam of a GEO satellite (with the agreed minimum elevation angle of 45°) will be full of urban TNs. It was further discussed and agreed that simply using 20% active rate and assuming fully deployed NR stations with urban deployment assumptions in the whole NR-NTN beam coverage area would overestimate the density and aggregated interference from NR stations to NR-NTN in this scenario. In the end, the case of NR DL interfering the NR-NTN LEO-600 UL that deployed in a Rural environment has been selected as a representative one that could be used as basis to derive ACIR values. Further study could be considered base on a mixed Urban and Rural environment. + +Table 6.4.6-1: Simulation results for average throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | 40 | +|----------|-------|-------|-------|-------|-------|-------|------|------|------|------| +| THALES | 51.17 | 41.28 | 31.94 | 23.87 | 17.01 | 11.87 | 7.91 | 5.26 | 3.4 | 2.22 | +| MTK | 3.05 | 1.98 | 1.28 | 0.82 | 0.52 | 0.33 | 0.21 | 0.13 | 0.08 | 0.05 | + +![Figure 6.4.6-1: Simulation results for average throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0 to 40) versus ACIR [dB] on the x-axis (22 to 40). Two lines are plotted: THALES (orange line with circles) and MTK (grey line with circles). THALES shows a steep decrease in loss from approximately 40% at 24 dB ACIR to about 2% at 40 dB ACIR. MTK shows a much flatter line, starting at about 3% loss at 22 dB ACIR and remaining near 0% loss across the entire ACIR range.](509a054727400bc6d424bb2a559b8cfc_img.jpg) + +Figure 6.4.6-1: Simulation results for average throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0 to 40) versus ACIR [dB] on the x-axis (22 to 40). Two lines are plotted: THALES (orange line with circles) and MTK (grey line with circles). THALES shows a steep decrease in loss from approximately 40% at 24 dB ACIR to about 2% at 40 dB ACIR. MTK shows a much flatter line, starting at about 3% loss at 22 dB ACIR and remaining near 0% loss across the entire ACIR range. + +Figure 6.4.6-1: Simulation results for average throughput loss - TN BS with non-AAS antenna + +Table 6.4.6-2: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +| ACIR[dB] | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | 40 | +|----------|-------|-------|-------|-------|-------|-------|------|------|------|------| +| THALES | 53.49 | 43.02 | 33.72 | 25.58 | 17.44 | 12.79 | 8.14 | 5.81 | 3.49 | 2.33 | +| MTK | 8.85 | 5.78 | 3.73 | 2.39 | 1.52 | 0.97 | 0.61 | 0.39 | 0.24 | 0.15 | + +![Figure 6.4.6-2: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0 to 40) versus ACIR [dB] on the x-axis (22 to 40). Two lines are plotted: THALES (orange line with circles) and MTK (grey line with circles). THALES shows a steep decrease in loss from approximately 40% at 24 dB ACIR to about 2% at 40 dB ACIR. MTK shows a much flatter line, starting at about 9% loss at 22 dB ACIR and remaining near 0% loss across the entire ACIR range.](b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg) + +Figure 6.4.6-2: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna. A line graph showing Loss [%] on the y-axis (0 to 40) versus ACIR [dB] on the x-axis (22 to 40). Two lines are plotted: THALES (orange line with circles) and MTK (grey line with circles). THALES shows a steep decrease in loss from approximately 40% at 24 dB ACIR to about 2% at 40 dB ACIR. MTK shows a much flatter line, starting at about 9% loss at 22 dB ACIR and remaining near 0% loss across the entire ACIR range. + +Figure 6.4.6-2: Simulation results for 5%-tile throughput loss - TN BS with non-AAS antenna + +Table 6.4.6-3: Interpolated ACIR values for Scenario 5 to meet the 5% throughput loss criteria - TN BS with non-AAS antenna + +| Source | | Interpolated ACIR[dB] | +|--------|---------|-----------------------| +| THALES | Average | 36.69 | +| | 5%-tile | 36.7 | +| MTK | Average | 19.66 | +| | 5%-tile | 24.67 1 | + +NOTE 1: According to the principles, this value is not treated for later process. + +**Table 6.4.6-4: Average ACIR of 5%-tile values in the above worse case for Scenario 6 - TN BS with non-AAS antenna** + +| | Scenario 6 | +|-----------------|------------| +| ACIR value [dB] | 36.7 | + +### 6.4.7 Scenario 7: 2GHz HAPS DL interfering TN DL + +The co-existence results contributed have been collected and compared in the following. + +**Table 6.4.7-1: Simulation results for average throughput loss** + +| ACIR[dB] | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | +|----------|-------|-------|-------|------|------|------|------|------| +| Nokia | 28,80 | 16,80 | 8,10 | 3,30 | 1,10 | 0,30 | 0,10 | 0,10 | +| Qualcomm | 38,41 | 23,95 | 12,26 | 5,14 | 1,86 | 0,62 | 0,20 | 0,06 | + +![Line graph showing average throughput loss for Nokia and Qualcomm over ACIR values from 5 to 40 dB. The y-axis represents Loss from 0.00% to 40.00%.](812f92102114dc0fa8487e0bfc372472_img.jpg) + +The graph shows the average throughput loss for two manufacturers, Nokia and Qualcomm, across different ACIR values. The x-axis represents ACIR [dB] from 5 to 40 in increments of 5. The y-axis represents Loss from 0.00% to 40.00% in increments of 5.00%. The Nokia line (blue) starts at approximately 28.80% at 5 dB and decreases to about 0.10% at 40 dB. The Qualcomm line (orange) starts at approximately 38.41% at 5 dB and decreases to about 0.06% at 40 dB. Both lines show a sharp decrease in loss as ACIR increases, eventually plateauing near 0% loss for ACIR values of 30 dB and above. + +| ACIR[dB] | Nokia (%) | Qualcomm (%) | +|----------|-----------|--------------| +| 5 | 28,80 | 38,41 | +| 10 | 16,80 | 23,95 | +| 15 | 8,10 | 12,26 | +| 20 | 3,30 | 5,14 | +| 25 | 1,10 | 1,86 | +| 30 | 0,30 | 0,62 | +| 35 | 0,10 | 0,20 | +| 40 | 0,10 | 0,06 | + +Line graph showing average throughput loss for Nokia and Qualcomm over ACIR values from 5 to 40 dB. The y-axis represents Loss from 0.00% to 40.00%. + +**Figure 6.4.7-1: Simulation results for average throughput loss** + +**Table 6.4.7-2: Simulation results for 5%-tile throughput loss** + +| ACIR[dB] | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | +|----------|--------|-------|-------|-------|------|------|------|------| +| Nokia | 77,10 | 53,20 | 26,60 | 9,80 | 1,80 | 0,30 | 0,20 | 0,00 | +| Qualcomm | 100,00 | 68,11 | 39,34 | 17,38 | 6,66 | 2,37 | 0,77 | 0,21 | + +![Figure 6.4.7-2: Simulation results for 5%-tile throughput loss. A line graph showing Loss (Y-axis, 0.00% to 40.00%) versus ACIR [dB] (X-axis, 5 to 40). Two lines are plotted: Nokia (blue line with circles) and Qualcomm (orange line with circles). Both lines show a sharp decrease in loss as ACIR increases, with Nokia reaching 0% loss at approximately 30 dB ACIR and Qualcomm reaching 0% loss at approximately 35 dB ACIR.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +| ACIR [dB] | Nokia Loss (%) | Qualcomm Loss (%) | +|-----------|----------------|-------------------| +| 15 | 26.0 | 39.0 | +| 20 | 10.0 | 17.0 | +| 25 | 2.0 | 7.0 | +| 30 | 0.0 | 2.0 | +| 35 | 0.0 | 0.5 | +| 40 | 0.0 | 0.0 | + +Figure 6.4.7-2: Simulation results for 5%-tile throughput loss. A line graph showing Loss (Y-axis, 0.00% to 40.00%) versus ACIR [dB] (X-axis, 5 to 40). Two lines are plotted: Nokia (blue line with circles) and Qualcomm (orange line with circles). Both lines show a sharp decrease in loss as ACIR increases, with Nokia reaching 0% loss at approximately 30 dB ACIR and Qualcomm reaching 0% loss at approximately 35 dB ACIR. + +Figure 6.4.7-2: Simulation results for 5%-tile throughput loss + +Table 6.4.7-3: Interpolated ACIR values for Scenario 7 to meet the 5% throughput loss criteria + +| Source | | Interpolated ACIR[dB] | +|----------|---------|-----------------------| +| Nokia | Average | 18.22 | +| | 5%-tile | 23.00 | +| Qualcomm | Average | 20.10 | +| | 5%-tile | 26.93 | + +Table 6.4.7-4: Average ACIR of 5%-tile values in the above worse case for Scenario 7 + +| | Scenario 1 | +|-----------------|------------| +| ACIR value [dB] | 24.97 | + +### 6.4.8 Scenario 8: 2GHz TN UL interfering HAPS UL + +The co-existence results contributed have been collected and compared in the following. + +Table 6.4.8-1: Simulation results for average throughput loss + +| ACIR[dB] | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | +|----------|-------|------|------|------|------|------|------|------| +| Nokia | 14.4% | 7.2% | 3.0% | 1.4% | 0.7% | 0.6% | 0.1% | 0.0% | + +![Line graph showing average throughput loss for Nokia across ACIR values from 5 to 40 dB. The loss decreases from approximately 14.5% at 5 dB to 0% at 40 dB.](7c0a9511fa02b6c2c125ff5be465186e_img.jpg) + +| ACIR [dB] | Nokia (%) | +|-----------|-----------| +| 5 | 14.5 | +| 10 | 7.5 | +| 15 | 3.0 | +| 20 | 1.5 | +| 25 | 0.8 | +| 30 | 0.7 | +| 35 | 0.2 | +| 40 | 0.0 | + +Line graph showing average throughput loss for Nokia across ACIR values from 5 to 40 dB. The loss decreases from approximately 14.5% at 5 dB to 0% at 40 dB. + +Figure 6.4.8-1: Simulation results for average throughput loss + +Table 6.4.8-2: Simulation results for 5%-tile throughput loss + +| ACIR[dB] | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | +|----------|-------|-------|-------|-------|------|------|------|------| +| Nokia | 35.4% | 22.6% | 12.6% | 11.5% | 7.5% | 5.0% | 4.5% | 1.1% | + +![Line graph showing 5%-tile throughput loss for Nokia across ACIR values from 5 to 40 dB. The loss decreases from approximately 35.4% at 5 dB to 1.1% at 40 dB.](179c2b96202f20634ec21def17c1cd86_img.jpg) + +| ACIR [dB] | Nokia (%) | +|-----------|-----------| +| 5 | 35.4 | +| 10 | 22.6 | +| 15 | 12.6 | +| 20 | 11.5 | +| 25 | 7.5 | +| 30 | 5.0 | +| 35 | 4.5 | +| 40 | 1.1 | + +Line graph showing 5%-tile throughput loss for Nokia across ACIR values from 5 to 40 dB. The loss decreases from approximately 35.4% at 5 dB to 1.1% at 40 dB. + +Figure 6.4.8-2: Simulation results for 5%-tile throughput loss + +## 6.5 Summary of co-existence study + +### 6.5.1 Coexistence at 2GHz + +This sub-clause captures the summary of the co-existence studies. The averaged interpolate ACIR values for each scenario are presented in Table 6.5.1-1 below. + +**Table 6.5.1-1: Average ACIR values for each scenario** + +| Scenario | | 1 | 2 | 3
LEO | 3
GEO | 4 | 5 | 6 | +|--------------------|--------------------|-------|-------|----------|----------|-------|-------|-------| +| ACIR value
[dB] | TN BS with AAS | 27.83 | 28.03 | 23.32 | 13.35 | 28.11 | 26.43 | 36.70 | +| | TN BS with non-AAS | 28.31 | 29.22 | 22.66 | 12.85 | 15.46 | 0 | | + +Then, by considering the following ACLR and ACS of TN BS and UE in Table 6.5.1-2, the suggested ACLR and ACS of NTN SAN, HAPS and UE from each scenario are given in Table 6.5.1-3. It should be noted that the values in Table 6.5.1-3 are directly derived from the selected option of each scenario, and it is limited by the nature of assumptions and methodologies adopted in the co-existence studies. + +**Table 6.5.1-2: ACLR and ACS of TN** + +| TN | | Values | +|----|------|--------| +| BS | ACLR | 45 dB | +| | ACS | 46 dB | +| UE | ACLR | 30 dB | +| | ACS | 33 dB | + +**Table 6.5.1-3: Co-existence results suggested ACLR and ACS of NR-NTN** + +| Scenario | Contributing | ACLR ACS values | +|----------|--------------|--------------------------------| +| 1 | NTN UE ACS | 27.91 dB (AAS) | +| 2 | NTN SAN ACS | 37.06 dB (non-AAS) | +| 3 | NTN SAN ACLR | LEO: 23.81 dB
GEO: 13.39 dB | +| 4 | NTN UE ACLR | 28.18 dB (AAS) | +| 5 | NTN UE ACLR | 27.51 dB (AAS) | +| 6 | NTN SAN ACS | 37.4 dB | +| 7 | HAPS ACLR | 24.97 dB | +| 8 | HAPS ACS | 30 dB | + +Considering the above suggested values, the agreed ACLR and ACS of NR-NTN are given in Table 6.5.1-4. + +**Table 6.5.1-4: ACLR and ACS of NR-NTN** + +| NR-NTN | | | Values | +|-------------------------------------------------------------------------------------------------------------------------|------------------|-----|-----------------| +| SAN | ACLR | GEO | 14 dB | +| | | LEO | 24 dB | +| | ACS 1 | GEO | 38 dB | +| | | LEO | 38 dB | +| HAPS | ACLR | | 45 2 | +| | ACS | | 46 | +| UE | ACLR | | 30 dB | +| | ACS | | 33 dB | +| NOTE 1: The ACS values for SAN apply to both Rural and Urban environment. | | | | +| NOTE 2: This value could be further relaxed based on co-existence studies if it is found more stringent than necessary. | | | | + +# 7 RF requirements + +## 7.1 SAN Reference points for RF requirements + +### 7.1.1 General + +This section describes the SAN reference points for RF requirements with respect to different SAN types. + +### 7.1.2 SAN type 1-C + +This requirement is not applicable in Release 17. + +### 7.1.3 SAN type 1-H + +For SAN type 1-H, the requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Figure 7.1.3-1: Radiated and conducted reference points for SAN type 1-H. The diagram shows the internal architecture of a Satellite Access Node (SAN). On the left, 'Non-NTN infrastructure gNB functions' are connected to a 'Satellite Gateway' via a 'Feeder link'. The 'Satellite Gateway' is connected to the 'Satellite Payload RF' section. Inside the payload, a 'Transceiver unit array (TRXUA) 1 to M' is shown with multiple units labeled #1, #2, ..., #K. These units are connected to a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)', which together form a 'Composite antenna'. The 'Transceiver unit array' is bounded by a 'Transceiver array boundary'. Conducted reference points are marked as 'Transceiver array boundary connector (TAB)' at the interface between the TRXUA and the RDN. A 'Radiated interface boundary' is indicated by a dashed line on the right side of the antenna array.](728ce58d1dcdbbbd39b97904271326ca_img.jpg) + +Figure 7.1.3-1: Radiated and conducted reference points for SAN type 1-H. The diagram shows the internal architecture of a Satellite Access Node (SAN). On the left, 'Non-NTN infrastructure gNB functions' are connected to a 'Satellite Gateway' via a 'Feeder link'. The 'Satellite Gateway' is connected to the 'Satellite Payload RF' section. Inside the payload, a 'Transceiver unit array (TRXUA) 1 to M' is shown with multiple units labeled #1, #2, ..., #K. These units are connected to a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)', which together form a 'Composite antenna'. The 'Transceiver unit array' is bounded by a 'Transceiver array boundary'. Conducted reference points are marked as 'Transceiver array boundary connector (TAB)' at the interface between the TRXUA and the RDN. A 'Radiated interface boundary' is indicated by a dashed line on the right side of the antenna array. + +**Figure 7.1.3-1: Radiated and conducted reference points for SAN type 1-H** + +Radiated characteristics are defined over the air (OTA), where the *operating band* specific radiated interface is referred to as the *Radiated Interface Boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +Conducted characteristics are defined at individual or groups of *TAB connectors* at the *transceiver array boundary*, which is the conducted interface between the transceiver unit array and the composite antenna. + +The transceiver unit array is part of the composite transceiver functionality receiving and transmitting modulated signals to ensure radio links with ground base stations and users. + +The Non-NTN infrastructure gNB functions implement the modulation and demodulation functionalities of the NTN gNB. + +The Satellite NTN Gateway is part of the NTN ground infrastructure and is responsible for up- and down-converting, as well as transmitting and receiving modulated signals between the Non-NTN infrastructure gNB functions and the Satellite payload via the Feeder link. + +The satellite payload is composed by a transceiver unit array and a composite antenna array. The transceiver unit array contains an implementation of specific number of transmitter units and an implementation of specific number of receiver units. + +The composite antenna contains a radio distribution network (RDN) and an antenna array. The RDN is a linear passive network which distributes the RF power generated by the transceiver unit array to the transmit antenna array. + +How a conducted requirement is applied to the *transceiver array boundary* is detailed in the respective requirement clause. + +### 7.1.4 SAN type 1-O + +For SAN type 1-O the radiated characteristics are defined over the air (OTA), where the *operating band* specific radiated interface is referred to as the *Radiated Interface Boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +![Figure 7.1.4-1: Radiated reference points for SAN type 1-O. The diagram shows a 'SATELLITE ACCESS NODE (SAN)' containing three main components: 'Non-NTN infrastructure gNB functions', 'Satellite Gateway', and 'Satellite Payload RF'. The 'Satellite Gateway' is connected to the 'Non-NTN infrastructure gNB functions' and to the 'Satellite Payload RF' via a 'Feeder link'. The 'Satellite Payload RF' contains three sub-components: 'Transceiver unit array (TRXUA) 1 to P', 'Radio Distribution Network (RDN)', and 'Antenna Array (AA)'. A dashed line labeled 'Radiated interface boundary' and 'RIB' is shown to the right of the 'Antenna Array (AA)'.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +Figure 7.1.4-1: Radiated reference points for SAN type 1-O. The diagram shows a 'SATELLITE ACCESS NODE (SAN)' containing three main components: 'Non-NTN infrastructure gNB functions', 'Satellite Gateway', and 'Satellite Payload RF'. The 'Satellite Gateway' is connected to the 'Non-NTN infrastructure gNB functions' and to the 'Satellite Payload RF' via a 'Feeder link'. The 'Satellite Payload RF' contains three sub-components: 'Transceiver unit array (TRXUA) 1 to P', 'Radio Distribution Network (RDN)', and 'Antenna Array (AA)'. A dashed line labeled 'Radiated interface boundary' and 'RIB' is shown to the right of the 'Antenna Array (AA)'. + +Figure 7.1.4-1: Radiated reference points for SAN type 1-O + +The SAN type 1-O payload includes an active antenna with performances characterized in radiated mode (OTA). + +## 7.2 Common issues for satellite access node and NTN UE + +### 7.2.1 General + +This section aims to present the agreed definitions for the newly introduced NTN operating bands. The possible configurations in terms of channel bandwidth, SCS, channel and synchronization raster for NTN operations are introduced as well. + +### 7.2.2 Operating bands + +The following bands in Table 7.2.2-1 are agreed as exemplary NTN satellite bands in Release 17. Regarding the band numbering for NTN satellite bands, it is agreed to start from the largest band number in FR1 range for NTN satellite bands which fully within FR1 frequency ranges to better differentiate NTN satellite band and TN bands and ensure contiguous band number allocation for NTN satellite bands, the number can be taken in a decreased order with first come, first service. + +Table 7.2.2-1: NTN satellite bands in FR1 + +| NTN satellite band # | Uplink (UL) operating band
Satellite Access Node receive / UE transmit
$F_{UL,low} - F_{UL,high}$ | Downlink (DL) operating band
Satellite Access Node transmit / UE receive
$F_{DL,low} - F_{DL,high}$ | Duplex mode | +|----------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------| +| n256 | 1980MHz – 2010 MHz | 2170 MHz – 2200 MHz | FDD | +| n255 | 1626.5 MHz – 1660.5 MHz | 1525 MHz – 1559 MHz | FDD | + +NOTE: NTN bands are numbered in descending order from n256. + +### 7.2.3 Channel bandwidth, SCS and spectral utilization + +The common definition for channel bandwidth, transmission bandwidth configuration, minimum guard band, and RB alignment in TS 38.104[16] and TS 38.101-1[17] can be reused for NTN satellite system. + +The supported channel bandwidths per operating band should be defined based on NTN operator input. The details are given in Table 7.2.3-1. + +**Table 7.2.3-1: Channel bandwidths and SCS per NTN satellite operating band in FR1** + +| NTN satellite band # | SCS kHz | 5 MHz | 10 MHz | 15 MHz | 20 MHz | +|----------------------|---------|-------|--------|--------|--------| +| n256 | 15 | Yes | Yes | Yes | Yes | +| | 30 | | Yes | Yes | Yes | +| | 60 | | Yes | Yes | Yes | +| n255 | 15 | Yes | Yes | Yes | Yes | +| | 30 | | Yes | Yes | Yes | +| | 60 | | Yes | Yes | Yes | + +### 7.2.4 Channel raster and sync raster + +#### 7.2.4.1 Channel raster + +In order to be compatible with current design of sync raster below 3 GHz, the ARFCN parameters below 3000 MHz will be reused and 100 kHz was chosen as the channel raster for NR NTN satellite bands below 3 GHz. + +The applicable ARFCNs per operating and for satellite access node are defined in table 7.2.4.1-1. + +**Table 7.2.4.1-1: ARFCNs per operating band satellite access node** + +| NTN satellite band # | $\Delta F_{\text{Raster}}$ (kHz) | Uplink range of $N_{\text{REF}}$ (First – – Last) | Downlink range of $N_{\text{REF}}$ (First – – Last) | +|----------------------|----------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------| +| n256 | 100 | 396000 – <20> – 402000 | 434000 – <20> – 440000 | +| n255 | 100 | 325300 – <20> – 332100 | 305000 – <20> – 311800 | + +#### 7.2.4.2 Sync raster + +The applicable SS raster entries per operating band are defined in Table 7.2.4.2-1 + +**Table 7.2.4.2-1: Applicable SS raster entries per operating band** + +| NTN satellite band # | SS Block SCS | SS Block pattern | Range of GSCN (First – – Last) | +|----------------------|--------------|------------------|--------------------------------------------| +| n256 | 15 kHz | Case A | 5429 – <1> – 5494 | +| n255 | 15 kHz | Case A | 3818 – <1> – 3892 | +| | 30 kHz | Case B | 3824 – <1> – 3886 | + +## 7.3 Satellite Access Node requirements + +### 7.3.1 General + +This section aims to provide some recommendations for the Satellite Access Node RF requirements definition in TS 38.181 [25] and TS 38.108 [26]. The technical justifications which support the requirements definition are also presented in the following sub-clauses. + +NTN products are assumed to use AAS BS architecture, with both I-H and I-O being included in Release 17 WI. Therefore, both conducted, as well as radiated requirements are required to be considered. + +#### 7.3.1.1 SAN class + +The requirements in TS 38.108 [26] apply to Satellite Access Node otherwise stated. The associated deployment scenarios are exactly the same for SAN with and without connectors. + +For SAN type 1-O and SAN type 1-H, two SAN classes (LEO and GEO) are currently defined in Table 7.3.1.1-1. + +**Table 7.3.1.1-1: SAN classes** + +| SAN Class | Satellite Constellation | +|-----------|-----------------------------------------------| +| GEO class | GEO satellite | +| LEO class | LEO 600 km satellite
LEO 1200 km satellite | + +The classification is based on the requirements associated with SAN classes in case-by-case manner including [IoT level/ICS, NF, ACLR/ACS, Emission] requirements. The satellite altitude or orbit type were not identified as part of the class differentiation, and for this reason LEO at 600 km and LEO at 1200 km were grouped together in the same class. At least NF, ACLR and ACS values are the same for LEO 600 km and LEO 1200 km and therefore are not requiring class differentiation. On the other hand, as resulted from the coexistence studies, ACLR requirement values are different between GEO and LEO constellations, requiring a class differentiation. Differences exist as well in terms of emission requirements (e.g. Out-of-band emissions and spurious emissions) between GEO and LEO. At the same time, ACS requirement values from the coexistence studies are the same between GEO and LEO constellations. + +### 7.3.2 Transmission characteristics + +#### 7.3.2.1 General + +Radiated characteristics are defined over the air (OTA), where the radiated interface is referred to as the *Radiated Interface Boundary* (RIB) as shown in Figure 7.3.2.1-1. + +Conducted characteristics are defined at individual or groups of *TAB connectors* at the *transceiver array boundary*, which is the conducted interface between the transceiver unit array and the composite antenna. The TAB connector is shown in Figure 7.3.2.1-1. + +![Figure 7.3.2.1-1: Reference point for SAN type 1-H. The diagram shows the internal architecture of a Satellite Access Node (SAN). On the left, 'Non-NTN infrastructure gNB functions' are connected to a 'Gateway'. The 'Gateway' is connected to the 'NTN Payload RF' section. Inside the 'NTN Payload RF' section, there is a 'Transceiver unit array (TRXUA) 1 to M' which connects to a 'Radio Distribution Network (RDN)' via multiple 'TAB connector' points (labeled #1, #2, ..., #C). The 'RDN' is connected to an 'Antenna Array (AA)'. The 'Composite antenna' is shown as a dashed box containing the 'RDN' and 'AA'. Two boundaries are indicated: the 'Transceiver array boundary' (a dashed line between the TRXUA and the RDN) and the 'Radiated interface boundary' (a dashed line between the RDN and the AA).](df94f7807f02e218ee3c66b9cbd829e5_img.jpg) + +Figure 7.3.2.1-1: Reference point for SAN type 1-H. The diagram shows the internal architecture of a Satellite Access Node (SAN). On the left, 'Non-NTN infrastructure gNB functions' are connected to a 'Gateway'. The 'Gateway' is connected to the 'NTN Payload RF' section. Inside the 'NTN Payload RF' section, there is a 'Transceiver unit array (TRXUA) 1 to M' which connects to a 'Radio Distribution Network (RDN)' via multiple 'TAB connector' points (labeled #1, #2, ..., #C). The 'RDN' is connected to an 'Antenna Array (AA)'. The 'Composite antenna' is shown as a dashed box containing the 'RDN' and 'AA'. Two boundaries are indicated: the 'Transceiver array boundary' (a dashed line between the TRXUA and the RDN) and the 'Radiated interface boundary' (a dashed line between the RDN and the AA). + +**Figure 7.3.2.1-1: Reference point for SAN type 1-H** + +#### 7.3.2.2 Conducted transmitter requirements + +##### 7.3.2.2.1 SAN output power + +The SAN conducted output power requirement applies at *TAB connector* for SAN type 1-H. + +The *rated carrier output power* of the SAN type 1-H shall be as specified in Table 7.3.2.2.1-1. + +**Table 7.3.2.2.1-1: SAN type 1-H rated output power limits for SAN classes** + +| SAN class | Prated,c,sys | Prated,c,TABC | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------| +| SAN GEO class | (NOTE) | (NOTE) | +| SAN LEO class | (NOTE) | (NOTE) | +| NOTE: P rated,c,sys or P rated,c,TABC of SAN shall be based on manufacture declaration and comply with regulation requirement. | | | + +In normal conditions, Pmax,c,TABC shall remain within +2 dB and -2 dB of the *rated carrier output power* Prated,c,TABC for each *TAB connector* as declared by the manufacturer. + +In extreme conditions, Pmax,c,TABC shall remain within +2.5 dB and -2.5 dB of the *rated carrier output power* Prated,c,TABC for each *TAB connector* as declared by the manufacturer. + +##### 7.3.2.2.2 Output power dynamics + +###### 7.3.2.2.2.1 RE power dynamic range + +The RE power control dynamic range is the difference between the power of an RE and the average RE power for a SAN at maximum output power for a specified reference condition. + +RE power control dynamic range requirement is define in Table 7.3.2.2.2.1-1. + +**Table 7.3.2.2.2.1-1: RE power control dynamic range** + +| Modulation scheme used on the RE | RE power control dynamic range (dB) | | +|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------| +| | (down) | (up) | +| QPSK (PDCCH) | -6 | +4 | +| QPSK (PDSCH) | -6 | +3 | +| 16QAM (PDSCH) | -3 | +3 | +| NOTE: The output power per carrier shall always be less or equal to the maximum output power of the satellite access node. | | | + +###### 7.3.2.2.2.2 Total power dynamic range + +Total power dynamic range for SAN will reuse the requirement from TN BS for the same channel bandwidth. + +The downlink (DL) total power dynamic range for each carrier shall be larger than or equal to the level in table 7.3.2.2.2.2-1. + +**Table 7.3.2.2.2.2-1: Total power dynamic range** + +| SAN channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|------------------------------------|---------------------------------------|-------------------|-------------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 5 | 13.9 | 10.4 | N/A | +| 10 | 17.1 | 13.8 | 10.4 | +| 15 | 18.9 | 15.7 | 12.5 | +| 20 | 20.2 | 17 | 13.8 | + +##### 7.3.2.2.3 Transmitted signal quality + +###### 7.3.2.2.3.1 Frequency error + +For SAN type 1-H, the modulated carrier frequency of each carrier configured by the satellite access node shall be accurate to within 0.05ppm observed over 1 ms. + +###### 7.3.2.2.3.2 Modulation quality (EVM) + +It is agreed to support QPSK and 16QAM for SAN. 64QAM will be optionally supported based on manufacture declaration. + +For SAN type 1-H, the EVM levels of each carrier for different modulation schemes on PDSCH outlined in table 7.3.2.2.3.2-1 shall be met. + +**Table 7.3.2.2.3.2-1: EVM requirements for *satellite access node type 1-H*** + +| Modulation scheme for PDSCH | Required EVM | +|------------------------------------------------------------|--------------| +| QPSK | 17.5 % | +| 16QAM | 12.5 % | +| 64QAM 1 | 8 % | +| NOTE: Support of 64QAM is based on manufacture declaration | | + +##### 7.3.2.2.4 Unwanted emissions + +###### 7.3.2.2.4.1 ACLR + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. + +From *Section 6.5 Summary of co-existence study* (see TR 38.863 related section), it can be observed in *Table 6.5.1-3 Co-existence results suggested ACLR and ACS of NR-NTN* the resulted study value of NTN SAN ACLR: + +**Table 7.3.2.2.4.1-1: NTN SAN ACLR** + +| | | +|--------------------|----------| +| NTN LEO class ACLR | 23.81 dB | +| NTN GEO class ACLR | 13.39 dB | + +Therefore, the value of 24 dB is the ACLR LEO class limit for the conducted transmitter requirements of SAN as shown in Table 7.3.2.2.4.1-2 and the value 14 dB is the ACLR GEO class limit for the conducted transmitter requirements of SAN as shown in Table 7.3.2.2.4.1-3: + +**Table 7.3.2.2.4.1-2: Satellite Access Node LEO class ACLR limit** + +| SAN channel bandwidth of lowest/highest carrier transmitted BW Channel (MHz) | SAN adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| | BW Channel | | | | +| 5, 10, 15, 20 | 2 x BW Channel | NR of same BW 2 | Square (BW Config ) 1 | 24 dB | +| | BW Channel | NR of same BW 2 | Square (BW Config ) 1 | 24 dB | +| NOTE 1: BW Channel and BW Config are the SAN channel bandwidth and transmission bandwidth configuration of the lowest/highest carrier transmitted on the assigned channel frequency. | | | | | +| NOTE 2: With SCS that provides largest transmission bandwidth configuration (BW Config ). | | | | | + +**Table 7.3.2.2.4.1-3: Satellite Access Node GEO class ACLR limit** + +| SAN channel bandwidth of lowest/highest carrier transmitted BW Channel (MHz) | SAN adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| | BW Channel | | | | +| 5, 10, 15, 20 | 2 x BW Channel | NR of same BW 2 | Square (BW Config ) 1 | 14 dB | +| | BW Channel | NR of same BW 2 | Square (BW Config ) 1 | 14 dB | +| NOTE 1: BW Channel and BW Config are the SAN channel bandwidth and transmission bandwidth configuration of the lowest/highest carrier transmitted on the assigned channel frequency. | | | | | +| NOTE 2: With SCS that provides largest transmission bandwidth configuration (BW Config ). | | | | | + +###### 7.3.2.2.4.2 Out-of-band emissions + +The SAN out-of-band emissions requirements for GEO and LEO classes are therefore defined as described in Table 7.3.2.2.4.2-1. + +Table 7.3.2.2.4.2-1: SAN out-of-band emissions basic limits + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits dBm | Measurement bandwidth | +|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 2 \times \text{BW}_{\text{Channel}}$ | $0.002 \text{ MHz} \leq f\_offset < 2 \times \text{BW}_{\text{Channel}} + 0.002 \text{ MHz}$ | $\max \left( \begin{aligned} &SE \text{ limit, } PSD_{\text{channel}} - \Delta_{\text{Sat\_Type}}[\text{dB}] \\ &- 40 \times \log_{10} \left( \frac{f\_offset - 0.002}{\text{BW}_{\text{channel}}} * 2 + 1 \right) \end{aligned} \right) \text{ dBm}$ | 4kHz | + +NOTE 1: $PSD_{\text{channel}} = P_{\text{rated,c,sys}} - 10 \log_{10}(\text{BW}_{\text{Channel}}) - 24$ , unit dBm/4kHz. +NOTE 2: SE limit is spurious emission limit specified in spurious emission clause. +NOTE 3: PSD attenuation as in Recommendation ITU-R SM.1541-6[29], Annex 5 OoB domain emission limits for space services. +NOTE 4: $\Delta_{\text{Sat\_Type}}=0 \text{ dB}$ for GEO class and $\Delta_{\text{Sat\_Type}}=3 \text{ dB}$ for LEO class. + +Recommendation ITU-R SM.1541-6 [29] specifies the OoB mask requirements. The OoB domain emission as attached Annex 5 should be attenuated below the maximum psd by the following and the attenuation can't be greater than the spurious emission limit. + +The OoB domain emissions of a station operating in the bands allocated to the FSS and MSS should be attenuated below the maximum psd, in a reference bandwidth of 4 kHz (for systems operating above 15 GHz a reference bandwidth of 1 MHz may be used in place of 4 kHz) within the necessary bandwidth, by the following: + +$$40 \log \left( \frac{F}{50} + 1 \right) \text{ dBsd}$$ + +where F is the frequency offset from the edge of the total assigned band, expressed as a percentage of necessary bandwidth. It is noted that the OoB emission domain starts at the edges of the total assigned band. + +![Graph showing Attenuation (dBsd) vs Frequency separation, F from edge of total assigned band (per cent of necessary bandwidth). The curve starts at 0 dBsd at 0% separation and decreases linearly until it reaches a horizontal 'Spurious limit' at 25 dBsd, starting at approximately 160% separation. A vertical dashed line at 200% separation marks the 'Spurious boundary'. The graph is titled '(attenuation no greater than the spurious limit)'.](0359ec7c5451731a6096ae08ce715586_img.jpg) + +The graph plots Attenuation (dBsd) on the y-axis (0 to 30) against Frequency separation, F from edge of total assigned band (per cent of necessary bandwidth) on the x-axis (0 to 300). A solid curve starts at (0, 0) and descends linearly. At approximately F=160, the curve reaches a horizontal dashed line labeled 'Spurious limit' at 25 dBsd. A vertical dashed line at F=200 is labeled 'Spurious boundary'. The area above the curve and to the left of the boundary is labeled '(attenuation no greater than the spurious limit)'. A small note at the bottom left indicates the start of the curve as the 'Edge of total assigned band'. + +Graph showing Attenuation (dBsd) vs Frequency separation, F from edge of total assigned band (per cent of necessary bandwidth). The curve starts at 0 dBsd at 0% separation and decreases linearly until it reaches a horizontal 'Spurious limit' at 25 dBsd, starting at approximately 160% separation. A vertical dashed line at 200% separation marks the 'Spurious boundary'. The graph is titled '(attenuation no greater than the spurious limit)'. + +Figure 7.3.2.2.4.2-1: Example of OoB mask assuming the spurious limit is equivalent to 25 dBsd + +The “F” = Frequency offset / channel bandwidth $\times$ 100 can be get as above. Thus, the OoB mask requirements can be specified as below based on the ITU regulation when we use $f_{\text{offset}}$ and $BW_{\text{channel}}$ to replace “F”. + +##### 7.3.2.2.5 Transmitter spurious emission + +Transmitter basic limits for spurious emissions are presented in Table 7.3.2.2.5-1. + +**Table 7.3.2.2.5-1: SAN transmitter spurious emission limits** + +| Spurious frequency range | Basic limit GEO class (dBm) | Basic limit LEO class (dBm) | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------|-------------------------| +| 30 MHz – 5 th harmonic (NOTE 2, 4, 5) | When $P_{\text{rated,c,sys}} \leq 47\text{dBm}$ :
-13
When $P_{\text{rated,c,sys}} > 47\text{dBm}$ :
$P_{\text{rated,c,sys}} - 60$
(NOTE 3) | | 4 kHz
(NOTE 1) | See NOTES 1, 2, 3, 4, 5 | +| NOTE 1: Measurement bandwidths as in Recommendation ITU-R SM.329 [30], s4.1.
NOTE 2: Lower and Upper frequency as in Recommendation ITU-R SM.329 [30], s2.5, Table 1. Applies only for the fundamental frequency range 600 MHz - 5.2 GHz (e.g. for n255 and n256 frequency bands).
NOTE 3: Values as in Recommendation ITU-R SM.329 [30], Table 10.
NOTE 4: Lower frequency limit is replaced by 0.7 times the waveguide cut-off frequency, according to ITU-R SM.329-12[30], for systems having an integral antenna incorporating a waveguide section, or with an antenna connection in such form, and of unperturbed length equal to at least twice the cut-off
NOTE 5: This spurious frequency range applies only to SAN type 1-H. | | | | | + +Recommendation ITU-R SM.329 [30] defines Unwanted emissions in the spurious domain. Measurement bandwidth is listed in section 4.1, lower and upper frequencies are specified in the Table 1 of section 2.5 and the values are taken from the table 10. + +#### 7.3.2.3 Radiated transmitter requirements + +7.3.2.3.1 Reserved + +7.3.2.3.2 Reserved + +7.3.2.3.3 Reserved + +7.3.2.3.4 Reserved + +7.3.2.3.5 Reserved + +7.3.2.3.6 Reserved + +7.3.2.3.7 Reserved + +7.3.2.3.7.1 Reserved + +7.3.2.3.7.2 Reserved + +7.3.2.3.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) + +7.3.2.3.7.3.1 General + +OTA Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. The measured power is TRP. + +##### 7.3.2.3.7.3.2 Minimum requirement for SAN type 1-O + +The OTA ACLR limit requirement for SAN type 1-O is the same as the ACLR limit defined in *Section 7.3.2.2.4.1 ACLR* of TR 38.863. For the OTA SAN ACLR limit refer to Table 7.3.2.2.4.1-2: Satellite Access Node ACLR limit. + +The OTA SAN ACLR absolute basic limit from Table 7.3.2.2.4.1-3: SAN ACLR absolute basic limit does not apply to SAN type 1-O. + +###### 7.3.2.3.7.3.3 Minimum requirement for SAN type 2-O + +This requirement is not applicable in Release 17. + +### 7.3.3 Receiver characteristics + +#### 7.3.3.1 General + +For Rx requirements, the TAB connector is located in the satellite payload, while the throughput measurement is done in the “non-NTN infrastructure gNB”, as shown in the Figure 7.3.3.1-1 for reference sensitivity requirement.[18][19] + +![Figure 7.3.3.1-1: Reference points for measurement of Rx requirements. The diagram shows a signal flow from a UE (User Equipment) through an NTN Channel Emulator (part of a Signal Generator for the wanted signal) to an NTN-Payload RF. The signal then passes through a Feederlink Emulator, a GW (Gateway), and finally to a Non-NTN infrastructure gNB. Two measurement points are indicated: REFSSENS Measurement Point is located at the input of the NTN-Payload RF, and Throughput Measurement Point is located at the output of the Non-NTN infrastructure gNB. The entire sequence from NTN-Payload RF to Non-NTN infrastructure gNB is labeled as DUT (Device Under Test).](cdc21bbfcba380e98ece42e5b8da50bb_img.jpg) + +Figure 7.3.3.1-1: Reference points for measurement of Rx requirements. The diagram shows a signal flow from a UE (User Equipment) through an NTN Channel Emulator (part of a Signal Generator for the wanted signal) to an NTN-Payload RF. The signal then passes through a Feederlink Emulator, a GW (Gateway), and finally to a Non-NTN infrastructure gNB. Two measurement points are indicated: REFSSENS Measurement Point is located at the input of the NTN-Payload RF, and Throughput Measurement Point is located at the output of the Non-NTN infrastructure gNB. The entire sequence from NTN-Payload RF to Non-NTN infrastructure gNB is labeled as DUT (Device Under Test). + +**Figure 7.3.3.1-1: Reference points for measurement of Rx requirements** + +The FRCs specified in TS 38.104[16] shall be re-used to specify the satellite access node Rx requirements. Further revisit is not precluded if the spectrum utilization (SU) would be different. + +For derivation of the Rx requirements, the following assumptions were made: + +- The FRCs specified in TS 38.104 [16] for NR BS were re-used to specify the NTN SAN Rx requirements. +- The Implementation Margin (IM) value was assumed to be 2 dB for NTN SAN. +- The following Noise Figure (NF) values were used for the derivation of Rx requirements for NTN SAN: + +**Table 7.3.3.1-1: NF values for NTN SAN requirements derivation** + +| | GEO | LEO 600 | LEO 1200 | +|---------------------------|-----|---------|----------| +| G/T (dB K -1 ) | 19 | 1.1 | 1.1 | +| G Rx (dBi) | 51 | 30 | 30 | +| NF (dB) | 7.4 | 4.3 | 4.3 | + +#### 7.3.3.2 Conducted receiver characteristics + +##### 7.3.3.2.1 Reference sensitivity level + +The following equation was used to derive the reference sensitivity for NTN SAN requirement development, reusing the same methodology for the reference sensitivity derivation as done for the NR BS, as captured in TR 38.817-02 [31]: + +$$P_{\text{REFSENS}} = -174 \text{ dBm/Hz} + 10 * \log_{10} \text{ BW} + \text{NF} + \text{IM} + \text{SNR} \text{ [dBm]}$$ + +Where: + +- BW is the maximum transmission bandwidth, +- NF is noise figure of NTN SAN receiver in dB, +- IM is implementation margin reserved for NTN SAN manufacturer in dB; +- SNR is the value to satisfy the 95% throughput of the FRC channel. + +##### 7.3.3.2.2 Dynamic range + +The Rx dynamic range is specified as a measure of the capability of the receiver to receive a wanted signal in the presence of an interfering signal at the *TAB connector* for *SAN type 1-H* inside the received SAN channel bandwidth. In this condition, a throughput requirement shall be met for a specified reference measurement channel. As the Rx dynamic range requirement measures the effects of NTN SAN receiver's impairments, the uncertainty due to the receiver's own thermal noise floor should be minimized. Therefore, the interference level should be increased by a certain amount of margin to mask the receiver's own noise floor, represented by Interference over Thermal (IoT). + +In order to define the dynamic range requirement, both wanted and interfering signal power levels need to be defined. The mean power levels of interfering and the wanted signals were defined in the following method: + +$$P_{\text{Intf}} = -174 \text{ dBm/Hz} + 10 * \log_{10}(N_{\text{RB}} * \text{SCS} * 12) + \text{NF} + \text{IoT}$$ + +$$P_{\text{wanted}} = -174 \text{ dBm/Hz} + 10 * \log_{10}(N_{\text{RB}} * \text{SCS} * 12) + \text{NF} + \text{IoT} + \text{SNR} + \text{IM}$$ + +Where: + +- $N_{\text{RB}}$ is the transmission bandwidth configuration of the lowest SCS defined for SAN for each *BS channel bandwidth*; +- SCS is the lowest sub-carrier spacing defined for SAN for each *BS channel bandwidth*; +- NF is noise figure of SAN receiver in dB as defined in table 6.2.2.1-5, +- IoT: during the discussion various values of the IoT were considered for the definition of the dynamic range requirement. In case of LEO600, IoT values in range of 15-18 dB were collected based on the simulation results. In case of LEO1200, IoT values in range of 10-15 dB were collected based on the simulation results, as captured in annex D. +- SNR is the value to satisfy the 95% throughput of measurement channel. As the derivation methodology and the FRC's from the NR BS was reused, more details on the SNR simulation results can be found in TR 38.817-02 [31]; +- IM is implementation margin reserved for SAN manufacturer in dB. The IM values was reused from the NR BS as 2 dB; + +For SAN it was agreed to define a single dynamic range requirement for LEO SAN (both 600 and 1200) based on the IoT value of 15 dB. Based on the collected simulation results for NTN scenarios, it was decided not to define dynamic range requirement for SAN GEO class. + +The interfering signal for the dynamic range requirement was defined as AWGN signal, same as for NR BS requirements. + +##### 7.3.3.2.3 In-band selectivity and blocking + +###### 7.3.3.2.3.1 Adjacent Channel Selectivity (ACS) + +###### 7.3.3.2.3.1.1 General + +Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency at the *antenna connector* for *NTN Satellite Access Node (SAN)* in the presence of an adjacent channel signal with a specified centre frequency offset of the interfering signal to the band edge of a victim system. + +The ACS value is coming from coexistence analysis. A worst case value of 38 dB ACS is found in GEO case and the interfering signal mean power (dBm) is computed given a NF 7.4 dB for a 5 MHz band. + +It is worth noting that OFDM is considered as interfering waveform (rather than DFT-s-OFDM) corresponding to a coexistence scenario 6 for the MSS S-band where TN BS DL is interfering with SAN UL. + +###### 7.3.3.2.3.1.2 Minimum requirements for Satellite Access Node + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For SAN, the wanted and the interfering signal coupled to the *antenna connector* are specified in table 7.3.3.2.3.1.2-1 and table 7.3.3.2.3.1.2-2 and the frequency offset between the wanted and interfering signal in table 7.3.3.2.3.1.2-3 for ACS. + +The ACS requirement is applicable outside the *SAN RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *SAN RF Bandwidth* edges or *Radio Bandwidth* edges. + +Minimum conducted requirement is defined at the *antenna connector*. + +**Table 7.3.3.2.3.1.2-1: SAN GEO class ACS requirement** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------| +| 5, 10, 15, 20 (NOTE 1) | $P_{\text{REFSENS}} + 6$ dB | -57 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the SAN for that bandwidth. | | | +| NOTE 2: For SAN, $P_{\text{REFSENS}}$ depends on the SAN channel bandwidth . | | | + +**Table 7.3.3.2.3.1.2-2: SAN LEO class ACS requirement** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------| +| 5, 10, 15, 20 (NOTE 1) | $P_{\text{REFSENS}} + 6$ dB | -60 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the SAN for that bandwidth. | | | +| NOTE 2: For SAN, $P_{\text{REFSENS}}$ depends on the SAN channel bandwidth . | | | + +The wanted signal and interfering signal power level are calculated in the following way in FR1: + +$$\text{Wanted signal power level} = \text{REFSENS} + 6 \text{ dB}$$ + +$$\text{Interfering signal power level} = \text{SAN noise floor} + \text{ACS} + 4.7 \text{ dB} = -174 \text{ dBm/Hz} + 10 \cdot \log_{10}(\text{BW}) + \text{NF} + \text{ACS} + 4.7 \text{ dB}$$ + +Where: + +- BW is wanted signal bandwidth in Hz, e.g. 25 PRB for 5 MHz SCS 15 kHz; +- NF is noise figure which is agreed as 7.4 dB for GEO, 4.3 dB for LEO@600, 4.3 dB for LEO@1200; +- SAN ACS is agreed as 38 dBc (more precisely according to coexistence Scenario 6, it has been noticed from the coexistence simulations that the required SAN ACS is in the order of 38 dBc ACS); +- 4.7 dB is calculated from $10 \log_{10}(10^{(6/10)} - 1)$ . + +If the equation considers the worst case of 38 dB ACS, with NF of 7.4 dB for GEO class and NF of 4.3 dB for LEO class, for 5 MHz signal bandwidth (as for TS 38.104[16]), the interfering signal mean power level is: + +$$-174 + 10 \cdot \log_{10}(5 \cdot 10^6) + 7.4 + 38 + 4.7 = \mathbf{-57 \text{ dBm}}$$ + +for GEO class, according to the interfering signal mean power value from Table 7.4.1.2-1. + +$-174+10\cdot\log_{10}(5\cdot 10^6)+4.3+38+4.7=-60\text{dBm}$ for LEO class, according to the interfering signal mean power value from Table 7.4.1.2-2. + +**Table 7.3.3.2.3.1.2-3: SAN ACS interferer frequency offset values** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper SAN RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 5 | $\pm 2.5025$ | 5 MHz OFDM NR signal
15 kHz SCS, 25 RBs | +| 10 | $\pm 2.5075$ | | +| 15 | $\pm 2.5125$ | | +| 20 | $\pm 2.5025$ | | + +###### **7.3.3.2.3.2 In-band blocking** + +No In-band blocker is considered for SAN. + +##### **7.3.3.2.4 Out-of-band blocking** + +###### **7.3.3.2.4.1 General** + +The out-of-band blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel at the *TAB connector* for *SAN type 1-H* in the presence of an unwanted interferer out of the *operating band*, which is a CW signal for out-of-band blocking. + +![Frequency band diagram showing uplink and downlink bands for Terrestrial IMT, Satellite IMT, and Space Operations. The uplink diagram shows bands from 1920 to 2110 MHz, with Terrestrial IMT uplink (1920-1800 MHz), Uplink Satellite IMT (1800-2000 MHz), 3G/Mobile (2000-2010 MHz), MSS Reg2 (2010-2025 MHz), MSS North-Am (2025-2040 MHz), and Space Ops (TC) (2040-2110 MHz). The downlink diagram shows bands from 2160 to 2200 MHz, with Terrestrial IMT downlink (2160-2170 MHz), MSS Reg2 (2170-2180 MHz), Downlink Satellite IMT (2180-2190 MHz), MSS North-Am (2190-2200 MHz), and Space Ops (TM) (2200-2210 MHz).](6c3063f123860b89793e4fee0d6b4150_img.jpg) + +Frequency band diagram showing uplink and downlink bands for Terrestrial IMT, Satellite IMT, and Space Operations. The uplink diagram shows bands from 1920 to 2110 MHz, with Terrestrial IMT uplink (1920-1800 MHz), Uplink Satellite IMT (1800-2000 MHz), 3G/Mobile (2000-2010 MHz), MSS Reg2 (2010-2025 MHz), MSS North-Am (2025-2040 MHz), and Space Ops (TC) (2040-2110 MHz). The downlink diagram shows bands from 2160 to 2200 MHz, with Terrestrial IMT downlink (2160-2170 MHz), MSS Reg2 (2170-2180 MHz), Downlink Satellite IMT (2180-2190 MHz), MSS North-Am (2190-2200 MHz), and Space Ops (TM) (2200-2210 MHz). + +**Figure 7.3.3.2.4.1-1: Band of concern to determine OOB blocking** + +The identified worst case is for the band n256 with the SpaceOps TC (TeleCommand) band between 2025 and 2110 MHz. This band is used to send commands to the satellite platform, taking into account the fact that a very robust radio link is established. To do so, the maximum EIRP of SpaceOps (Space Operations) TC (TeleCommand) stations is 80 dBW. + +For a LEO satellite at 600 km (LEO@600km), in a worst case scenario (i.e. SpaceOps TC station at satellite Nadir), the free space losses are 154 dB. + +Therefore, the signal level at satellite level is -44 dBm. + +###### **7.3.3.2.4.2 Minimum requirements for Satellite Access Node** + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to *SAN type 1-H TAB connector* using the parameters in table 7.3.3.2.4.2-1. + +The out-of-band blocking requirement apply from 1 MHz to $F_{UL,low} - \Delta f_{OOB}$ and from $F_{UL,high} + \Delta f_{OOB}$ up to 12750 MHz, including the downlink frequency range of the FDD *operating band*. + +Minimum conducted requirement is defined at the *antenna connector* at the *TAB connector* for *SAN type 1-H*. + +**Table 7.3.3.2.4.2-1: Out-of-band blocking performance requirement for NR** + +| Wanted Signal mean power (dBm) | Interfering Signal mean power (dBm) | Type of Interfering Signal | +|------------------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------| +| P REFSENS +6 dB (NOTE) | -44 | CW carrier | +| NOTE: P REFSENS depends on the RAT. For NR, P REFSENS depends also on the SAN channel bandwidth. | | | + +##### 7.3.3.2.5 Receiver spurious emissions + +The requirement is not applicable in this version of the specification. + +##### 7.3.3.2.6 Receiver intermodulation + +The requirement is not applicable in this version of the specification. + +##### 7.3.3.2.7 In-channel selectivity + +The requirement framework from terrestrial network (TN) NR specification is agreed to be reused. + +#### 7.3.3.3 Radiated receiver characteristics + +##### 7.3.3.3.1 OTA sensitivity + +On the same principle as for the NR TN BS Specification TS 38.104[16], the SAN OTA sensitivity testing procedure should be based on SAN manufacturer declarations of sensitivity direction and EIS level. + +##### 7.3.3.3.2 OTA reference sensitivity level + +OTA reference sensitivity level is a directional requirement specified as an EIS level. On the same principle as for the NR TN BS specification TS38.104[16], the SAN OTA reference sensitivity EISREFSENS requirements should be derived from: + +- the conducted reference sensitivity PREFSENS which can be calculated based on the formula presented in Section 7.3.3.2.1; +- a hypothetical antenna gain of a passive satellite antenna; +- some implementation margin reserved for the NTN SAN manufacturer. + +The last two contributions are both taken into account under ΔOTAREFSENS parameter. + +As OTA reference sensitivity is used as a reference for many of the interference requirements where it is important that the interferer is polarization matched to the receiver antenna it is also important that the wanted signal is polarization matched. Hence OTA reference sensitivity is specifically declared per polarization and the EIS values are under the assumption of *polarization match*. + +For SAN type 1-O, OTA reference sensitivity is intended to provide equivalent protection and performance as the conducted reference sensitivity level. The OTA reference sensitivity level is calculated based on the conducted reference sensitivity level for SAN type 1-H and antenna gain of a passive antenna which would be used with a non-AAS SAN in the same deployment scenario. + +##### 7.3.3.3.3 OTA dynamic range + +The requirement assumes that the wanted signal and interfering signal come from the same direction. And since both wanted signal and AWGN will be transmitted from the test equipment in the same direction, the same combining gain will be achieved for both wanted signal and the AWGN. Hence, the OTA dynamic range for FR1 can be defined based on conductive requirements plus an offset, i.e., ΔOTAREFSENS. + +##### 7.3.3.3.4 OTA in-band selectivity and blocking + +###### 7.3.3.3.4.1 OTA adjacent channel selectivity + +OTA Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive an OTA wanted signal at its assigned channel frequency in the presence of an OTA adjacent channel signal with a specified centre frequency offset of the interfering signal to the band edge of a victim system. For SAN type 1-O, interfering signal mean power should be offset by the value $\Delta_{\min\text{SENS}}$ , other parameters could be reused from SAN type 1-H and respective ACS clause. + +##### 7.3.3.3.5 OTA out-of-band blocking + +###### 7.3.3.3.5.1 General + +The OTA out-of-band blocking characteristics are a measure of the receiver unit ability to receive a wanted signal at the RIB at its assigned channel in the presence of an unwanted interferer. + +###### 7.3.3.3.5.2 Minimum requirement for SAN type 1-O + +###### 7.3.3.3.5.2.1 General minimum requirement + +The requirement shall apply at the RIB when the AoA of the incident wave of the received signal and the interfering signal are from the same direction and are within the *minSENS RoAoA*. + +The wanted signal applies to each supported polarization, under the assumption of *polarization match*. The interferer shall be *polarization matched* in-band and the polarization maintained for out-of-band frequencies. + +The values for the minimum requirements have been obtained with the hypothesis from section 7.3.3.2.4 Out-of-band blocking, considering the maximum EIRP of SpaceOps (Space Operations) TC (TeleCommand) stations of 80 dBW, and the interfering signal mean power of -44 dBm, for a LEO satellite at 600 km of altitude (LEO@600km). + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 7.3.5.6.2.1-1, the following requirements shall be met: + +- The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For SAN type 1-O the OTA out-of-band blocking requirement apply from $F_{\text{UL,low}} - \Delta f_{\text{OOB}}$ and from $F_{\text{UL,high}} + \Delta f_{\text{OOB}}$ up to 12750 MHz, including the downlink frequency range of the FDD operating band. + +**Table 7.3.3.3.5.2.1-1: OTA out-of-band blocking performance requirement** + +| Wanted signal mean power (dBm) | Interfering signal RMS field-strength (V/m) | Type of interfering Signal | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|----------------------------| +| EIS minSENS + 6 dB
(NOTE 1) | 0.091 | CW carrier | +| NOTE 1: EIS minSENS depends on the channel bandwidth .
NOTE 2: The RMS field-strength level in V/m is related to the interferer EIRP level at a distance described as $E = \frac{\sqrt{30\text{EIRP}}}{r}$ , where EIRP is in W and r is in m. | | | + +###### 7.3.3.3.5.2.2 Co-location minimum requirement + +This requirement is not applicable in Release 17. + +##### 7.3.3.3.6 OTA receiver spurious emissions + +The requirement is not applicable in this version of the specification. + +##### 7.3.3.3.7 OTA receiver intermodulation + +This requirement is not applicable in Release 17. + +##### 7.3.3.3.8 OTA in-channel selectivity + +For SAN type 1-O, power level of wanted signal and interfering signal should be offset by the value $\Delta_{\min\text{SENS}}$ . Other parameters could be reused from SAN type 1-H and respective in-channel selectivity (ICS) clause. + +### 7.3.4 Others + +[To be updated] + +## 7.4 NTN UE requirements + +### 7.4.1 General + +In general, NTN UE products are assumed to meet TN UE requirements as specified in TS 38.101-1[17]. The structure and content of the NTN UE specification TS 38.101-5 should be based on TS 38.101-1[17]. The development of TS 38.101-5 should follow the set of conditions that were agreed at the RAN#94e meeting in RP-213618[27]. + +### 7.4.2 UE Transmission characteristics for satellite access + +#### 7.4.2.1 General + +Unless otherwise stated, the transmitter characteristics are specified at the antenna connector of the UE with a single or multiple transmit antenna(s). For UE with integral antenna only, a reference antenna with a gain of 0dBi is assumed. Handheld PC3 UE is assumed in Release 17 for satellite access. + +#### 7.4.2.2 Conducted transmitter characteristics + +##### 7.4.2.2.1 Maximum output power + +The following UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth of NR carrier unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). + +**Table 7.4.2.2.1-1: UE Power Class** + +| NTN satellite band # | Class 3 (dBm) | Tolerance (dB) | +|----------------------|---------------|----------------| +| n256 | 23 | $\pm 2$ | +| n255 | 23 | $+2$ | + +NOTE 1: $P_{\text{PowerClass}}$ is the maximum UE power specified without taking into account the tolerance +NOTE 2: Power class 3 is default power class unless otherwise stated + +##### 7.4.2.2.2 MPR/AMPR + +###### 7.4.2.2.2.1 MPR + +UE is allowed to reduce the maximum output power (MPR) due to higher order modulations and transmit bandwidth configurations to meet the general transmission requirements which includes in-band emission, ACLR, out-of-band emission and general spurious emission. As it was agreed those general transmission requirements can be reused from TN, the same requirements specified in Table 6.2.2-1 in TS 38.101-1 [17] can be reused for NTN satellite access UEs. + +###### 7.4.2.2.2.2 A-MPR + +A-MPR is band specific requirement which is used to meet the additional requirements indicated by network signalling (NS) value. + +For n256, based on the regulation conclusion in section 5.2, the A-MPR requirements for n65 could be as starting point. From TS 38.101-1, since the maximum carrier centre frequency of NS\_05 and NS\_05U is lower than 1960 MHz and the maximum carrier centre frequency of NS\_51 is lower than 1980 MHz, it is proposed NS\_05, NS\_05U and NS\_51 don't need to be considered for n256. The requirements of NS\_01, NS\_24 and NS\_100 specified in Table 6.2.3.1-1 in TS 38.101-1 [17] for band n65 can be reused for n256 + +For n255, based on regulatory requirements, a new NS is required. The following observations were made from the measurement results using an LTE modem and transceiver supporting 1626.5 – 1656.5 MHz: + +- For 5 MHz channel, PA emissions for DFT-s-OFDM are below the spurious emission limits between 1559 and 1606 MHz. +- For 10 MHz channel, PA emissions for DFT-s-OFDM are exceeding the spurious emission limits for 1 MHz MBW by 5 dB between 1604 and 1606 MHz. +- For 15 MHz channel, PA emissions for DFT-s-OFDM are exceeding the spurious emission limits for 1 MHz MBW by 9 dB between 1599 and 1606 MHz. +- For 20 MHz channel, PA emissions for DFT-s-OFDM are exceeding the spurious emission limits by 9 dB between 1584 and 1606 MHz. +- For 700 Hz MBW, PA emissions for all channel bandwidths are below the spurious emission limits between 1559 and 1606 MHz. + +A n255 duplexer with rejection of more than 10 dB will be a sufficient to satisfy the spurious emission limits specified in Table 7.4.2.2.8-1. + +Based on this measurement observations, the expected filter attenuation of more than 10 dB below 1610 MHz is going to be adequate to meet the additional emissions requirements between 1559 – 1610 MHz, and therefore, no A-MPR needs to be specified for n255. + +In view of the above, the additional requirements with their associated network signalling values and the allowed A-MPR and applicable operating band(s) for each NS value shall be specified in Table 7.4.2.2.2.2-1 and the mapping of NR satellite band numbers and values of the *additionalSpectrumEmission* to network signalling labels is specified in Table 7.4.2.2.2.2-1A. + +**Table 7.4.2.2.2.2-1: Additional maximum power reduction (A-MPR)** + +| Network signalling label | Requirements (clause) | NR satellite Band | Channel bandwidth (MHz) | Resources blocks ( $N_{RB}$ ) | A-MPR (dB) | +|--------------------------|---------------------------|-------------------|-------------------------|---------------------------------|--------------------------------------------| +| NS_01 | | Table 5.2.1-1 | 5, 10, 15, 20 | Table 5.3.2-1 in TS 38.101-1 | N/A | +| NS_24 | 6.5.3.3.13 in TS 38.101-1 | n256 | 5, 10, 15, 20 | Table 6.2.3.15-1 in TS 38.101-1 | Clause 6.2.3.7 in TS 38.101-1 2 | +| NS_57N | 6.5.3.3.1 | n255 | 5, 10, 15, 20 | | N/A | +| NS_100 | 6.5.2.4.2 in TS 38.101-1 | n256 1 | | | Table 6.2.3.1-2 in TS 38.101-1 | + +NOTE 1: This NS can be signalled for NTN satellite bands that have UTRA services deployed. +NOTE 2: A-MPR for the upper 5 MHz is not specified, and therefore shall be used as a guard band. + +**Table 7.4.2.2.2.2-1A: Mapping of network signalling label** + +| NTN satellite band | Value of additionalSpectrumEmission | | | | | | | | +|--------------------|-------------------------------------|--------|--------|---|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| n256 | NS_01 | NS_24 | NS_100 | | | | | | +| n255 | NS_01 | NS_57N | | | | | | | + +NOTE: *additionalSpectrumEmission* corresponds to an information element of the same name defined in clause 6.3.2 of TS 38.331. + +For n256, FFS for how to protect n2, n25, n70 and whether A-MPR required. + +##### 7.4.2.2.3 Output power dynamics + +For Transmit OFF power and Power control, the framework and requirements for existing TN UE can be reused for satellite UE. The transmit OFF power is -50 dBm for 20MHz. + +Since handheld UE always transmits the maximum output power for satellite access scenario based on the NR NTN calibration summary in R4-2115628, FFS whether relaxed value needed or not based on existing TN UE requirements + +##### 7.4.2.2.4 Frequency error + +The UE basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of UE modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 ms of cumulated measurement intervals compared to the carrier frequency received from the Satellite Access Node. + +NOTE: The requirements is applicable only when PVT ephemeris updated at least once [10] seconds. + +##### 7.4.2.2.5 Transmit modulation quality + +For the EVM (Error Vector Magnitude), the same requirements specified in TS 38.101-1 [17] sub-clause 6.4.2.1 for QPSK, 16QAM, and 64QAM can be reused for NTN satellite access UEs. NTN satellite access UEs support UL/DL 64QAM for NTN operation as optional with per band. + +For the carrier leakage, the same requirements specified in TS 3.101-1 [17] sub-clause 6.4.2.2 can be reused for NTN satellite access UEs. + +For the in-band emission, the same requirements specified in TS 3.101-1 [17] sub-clause 6.4.2.3 can be reused for NTN satellite access UEs. + +##### 7.4.2.2.6 Spectrum emission mask + +For SEM of NTN satellite access UEs, the same requirements of TN UE specified in TS 38.101-1 [17] sub-clause 6.5.2.2 can be reused. + +##### 7.4.2.2.7 ACLR + +For ACLR, the same ACLR for TN NR UE which is specified in TS 3.101-1 [17] sub-clause 6.5.2.4.1 can be applied for NTN satellite access UEs. + +The requirement of ALCR is specified in Table 7.4.2.2.7-1. + +**Table 7.4.2.2.7-1: NTN satellite access UE ACLR requirement** + +| | Power class 3 | +|-------------|---------------| +| NTN UE ALCR | 30dB | + +##### 7.4.2.2.8 Spurious emissions + +The spurious emissions limits specified in TS 38.101-1[17] sub-clause 6.5.3 would also be applicable to NTN satellite access UEs referring to the ERC Recommendation 74-01[28] Annex 3 item 3.1.4 for Mobile Earth Stations (MES) (see Note 1bis) transmitting in the Mobile Satellite Service between 1 GHz and 3 GHz. + +Considering FCC rule 47 C.F.R § 25.216 (h) [23], TN UE's general spurious emission requirements will be inadequate for L-band NTN satellite UE operation in the US. A new NS value and a subclause with Table 7.4.2.2.8-1 needs to be specified for n255 for NTN satellite operations in the US. + +**Table 7.4.2.2.8-1: Additional requirements for NS\_57N** + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit 1 (dBW) | Measurement bandwidth | NOTE | +|---------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------|--------------------------------------------------------------| +| | 5 MHz, 10 MHz, 15 MHz, 20 MHz | | | +| $1559 \leq f \leq 1605$ | -80 | 700 Hz | Averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-80 + 24/5 (f - 1605)$ | 700Hz | | +| $1559 \leq f \leq 1605$ | -70 | 1MHz | Averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-70 + 24/5 (f - 1605)$ | 1MHz | | +| NOTE 1: The EIRP requirement in regulation is converted to conducted requirement using a 0 dBi antenna. | | | | + +##### 7.4.2.2.9 Transmit intermodulation + +The transmit intermodulation limits specified in TS 38.101-1[17] sub-clause 6.5.4 (Table 7.4.2.2.9-1) would also be applicable to NTN satellite access UEs. + +The requirement of transmit intermodulation is specified in Table 7.4.2.2.9-1. + +**Table 7.4.2.2.9-1: Transmit Intermodulation** + +| | | | +|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Wanted signal channel bandwidth | $BW_{\text{Channel}}$ | | +| Interference signal frequency offset from channel center | $BW_{\text{Channel}}$ | $2 * BW_{\text{Channel}}$ | +| Interference CW signal level | -40 dBc | | +| Intermodulation product | $< -29$ dBc | $< -35$ dBc | +| Measurement bandwidth | The maximum transmission bandwidth configuration among the different SCS's for the channel BW as defined in Table 6.5.2.4.1-1 from TS 38.101-1[17] | | +| Measurement offset from channel center | $BW_{\text{Channel}}$ and $2 * BW_{\text{Channel}}$ | $2 * BW_{\text{Channel}}$ and $4 * BW_{\text{Channel}}$ | + +##### 7.4.2.2.10 UE to UE coexistence issues between NTN and TN + +In recent RAN4#102 and RAN4#103 meetings, the spurious emissions requirements ( $-50$ dBm/MHz) for protected bands UE co-existence (especially for band n256 UL: 1980~2010MHz DL: 2170~2200MHz) were widely discussed. The adjacent/overlapping TN bands to NTN band n256 are shown in Figure 5.2.1-1. + +###### 1) Coexistence protection for band n34 DL + +The NS\_24 including associated A-MPR value as specified in TS 38.101-1[17] is reused to solve this issue in Release 17. However, other companies pointed out the n256 UL frequency range can't be leveraged due to 5MHz guard band at the upper of n256 UL frequency range to protect band n34. If NS\_24 is used, n256 will be reduced due to the 5 MHz guard band that has been considered with NS\_24, frequency range 2005-2010 MHz can not be used anymore. Besides, when NS\_24 is indicated to protect the DL frequency range of band n34, satellite UE has to reduce the out power in band n256. It will lead to UL throughput loss and even UL radio link failure for some UL RB configurations. + +###### 2) Coexistence protection for band n39 DL + +$-50$ dBm/MHz co-existence requirement can be met considering 20MHz channel bandwidth for band n256 without A-MPR requirement, even if a band n65 duplexer is reused for band n256. + +Based on extrapolating the SEM mask to the ACLR4 region which overlaps n39 for the lowest n256 20MHz channel it is feasible to specify $-50$ dBm/MHz protection level for n39 by n256 even when using n65 duplexer (no filter help assumed). This assumes the maximum n256 bandwidth is 20MHz. + +![Figure 7.4.2.2.10-1: Coexistence analysis based on SEM mask extension for band n256. The figure is a complex frequency domain diagram showing various radio bands and their coexistence. The top section shows frequency ranges in MHz (1805 to 2300) and identifies bands like n101, n33DL, n65UL, n256UL, n34DL, n65DL, n1DL, n256DL, n3DL, n39UDL, n1UL, n2UL, n25DL, n70DL, n23, n25UL, n37UDL, n2DL, n23, n25DL, n70DL, n23. Below this, there are rows for 'band/CBW', 'dBm/MHz', and 'band/CBW' again, with color-coded blocks (green, yellow, red) indicating different power levels or interference regions. A central block shows '20MHz Bot' and '20MHz Top' with a 5 MHz gap between them. The bottom section shows 'band/CBW', 'dBm/MHz', and 'band/CBW' again, with a 5 MHz gap and color-coded blocks.](41cd1b0cca77430b41ab28d088e82259_img.jpg) + +Figure 7.4.2.2.10-1: Coexistence analysis based on SEM mask extension for band n256. The figure is a complex frequency domain diagram showing various radio bands and their coexistence. The top section shows frequency ranges in MHz (1805 to 2300) and identifies bands like n101, n33DL, n65UL, n256UL, n34DL, n65DL, n1DL, n256DL, n3DL, n39UDL, n1UL, n2UL, n25DL, n70DL, n23, n25UL, n37UDL, n2DL, n23, n25DL, n70DL, n23. Below this, there are rows for 'band/CBW', 'dBm/MHz', and 'band/CBW' again, with color-coded blocks (green, yellow, red) indicating different power levels or interference regions. A central block shows '20MHz Bot' and '20MHz Top' with a 5 MHz gap between them. The bottom section shows 'band/CBW', 'dBm/MHz', and 'band/CBW' again, with a 5 MHz gap and color-coded blocks. + +Figure 7.4.2.2.10-1: Coexistence analysis based on SEM mask extension for band n256 + +###### 3) Coexistence protection for band n2, n25, n70 DL + +From RAN4 perspective, UE co-existence requirements can't be fulfilled (-50dBm/MHz) for the TN bands (i.e., n2, n25 and n70) which are overlapping n256. In Release 17, it is RAN4 understanding that the co-existence issue between n256 and those TN bands shall rely on regional or national regulation. + +###### Other proposals: + +Other proposals were submitted to solve the UE to UE coexistence issues between NTN and TN especially for the protected DL frequency range which is overlapping with UL frequency range of band n256 or next to the edge of band n256 UL filter. + +For example: + +- Isolation regions could be defined between NTN and TN coverage. And a corresponding signaling could be designed by RAN2. +- Before transmitting UL band n256 signals, satellite UE should determine (or be informed) whether the IMT services exist for the protected DL frequency range in the vicinity. +- Other potential mechanisms/solutions are not precluded. + +Considering these proposals will have impacts on RAN1/RAN2 specifications, these proposals were not further discussed in Release 17. + +#### 7.4.2.3 “Reserved” (for Radiated transmitter Characteristics) + +### 7.4.3 UE Receiver characteristics for satellite access + +#### 7.4.3.1 General + +Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the UE. For UE(s) with an integral antenna only, a reference antenna(s) with a gain of 0 dBi is assumed for each antenna port(s). UE with an integral antenna(s) may be taken into account by converting these power levels into field strength requirements, assuming a 0 dBi gain antenna. For UEs with more than one receiver antenna connector, identical interfering signals shall be applied to each receiver antenna port if more than one of these is used (diversity). + +#### 7.4.3.2 Conducted receiver characteristics + +##### 7.4.3.2.1 General and diversity characteristics + +Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the UE for satellite access. + +The handheld UE for satellite access is required to be equipped with a minimum of two Rx antenna ports in all NTN satellite operating bands in FR1. + +##### 7.4.3.2.2 Reference sensitivity + +The reference sensitivity power level REFSENS is the minimum mean power applied to each one of the UE antenna ports for all UE categories, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. For below 6GHz, the REFSENS level can be calculated by the equation below in TR 38.817-01[32]: + +$$\text{Sensitivity} = -174\text{dBm(kT)} + 10 \cdot \log(\text{RX BW}) + \text{NF} + \text{SNR} + \text{IM} - \text{diversity gain}$$ + +It is noted that the Rx BW is identical to the transmission bandwidth configuration, which is determined by the spectrum utilization. The RB values in the analysis of this contribution are based on the agreed SU for NR. + +SNR in Nagoya meeting was agreed as -1dB for NR. + +The REFSENS for E-UTRA assumes that the receiver is equipped with two Rx port as a baseline. If 2Rx is considered, the diversity gain is 3dB and the Implementation Margin (IM) uses 2.5dB. In the following calculation, same assumptions are used for NR NTN satellite bands. + +For band n255, 9dB noise figure is assumed which is aligned with band n24. + +Both dedicate 30MHz duplexer and n65 duplexer are allowed to be used for band n256. Finally, 9dB noise figure is assumed for band n256 as well. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2.2 and A.3.2 from TS 38.101-1 [17] (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1 from TS 38.101-1 [17]) with parameters specified in Table 7.4.3.2.2-1 and Table 7.4.3.2.2-2. + +**Table 7.4.3.2.2-1: Two antenna port reference sensitivity QPSK REFSENS** + +| Operating band / SCS / Channel bandwidth / Duplex-mode | | | | | | | +|--------------------------------------------------------|---------|-------------|--------------|--------------|--------------|-------------| +| NTN satellite band # | SCS kHz | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | Duplex Mode | +| n255 | 15 | -100.0 | -96.8 | -95.0 | -93.8 | FDD | +| | 30 | | -97.1 | -95.1 | -94.0 | | +| | 60 | | -97.5 | -95.4 | -94.2 | | +| n256 | 15 | -100.0 | -96.8 | -95.0 | -93.8 | FDD | +| | 30 | | -97.1 | -95.1 | -94.0 | | +| | 60 | | -97.5 | -95.4 | -94.2 | | + +**Table 7.4.3.2.2-2: Uplink configuration for reference sensitivity** + +| Operating band / SCS / Channel bandwidth / Duplex-mode | | | | | | | +|--------------------------------------------------------|---------|-------------|--------------|--------------|--------------|-------------| +| NTN satellite band # | SCS kHz | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | Duplex Mode | +| n255 | 15 | 25 | 50 | 75 | 100 | FDD | +| | 30 | | 24 | 36 | 50 | | +| | 60 | | 10 | 18 | 24 | | +| n256 | 15 | 25 | 50 | 75 | 100 | FDD | +| | 30 | | 24 | 36 | 50 | | +| | 60 | | 10 | 18 | 24 | | + +##### 7.4.3.2.3 Maximum input level + +Maximum input level is defined as the maximum mean power received at the UE antenna port, at which the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel. In defining requirements for maximum input level, there are two effects should be considered. One is the dynamic range + +for Rx link since the maximum input level would determine the high limit of dynamic range. The other is the maximum received input power at UE in real deployment. If the maximum received input signal level is increased, then pre-LNA attenuation is required, which adds complexity to UE RX chain. Similar as the method in TN system, in order to evaluate the level of maximum received power, the Min distance for consideration is given in Table 7.4.3.2.3-1. + +**Table 7.4.3.2.3-1: Min distance for consideration** + +| | Parameters | Satellite Type | | | +|-------|----------------------------------------|----------------|----------|---------| +| | | GEO | LEO 1200 | LEO 600 | +| | Carrier frequency [GHz] | 2 | 2 | 2 | +| | Min Distance from Satellite D_Min [Km] | 35786 | 1200 | 600 | +| | The free space path loss (FSPL) (dB) | 189.5 | 160.1 | 154.0 | +| SET 1 | Satellite EIRP density (dBW/MHz) | 59 | 40 | 34 | +| | Bandwidth (15kHz SCS) (MHz) | | 20 | | +| | Rx signal at min Distance (dBm) | -87.7 | -77.2 | -77.2 | +| SET 2 | Satellite EIRP density (dBW/MHz) | 53.3 | 34 | 28 | +| | Bandwidth (15kHz SCS) (MHz) | | 20 | | +| | Rx signal at min Distance (dBm) | -93.4 | -83.2 | -83.2 | + +From above table, the maximum received power is -77.2 dBm for 20 MHz which is very lower than -25dBm in TN. It is therefore the maximum input level can be relaxed by 15 dB compared with TN requirement. + +##### 7.4.3.2.4 Adjacent channel selectivity + +For ACS, the coexistence studies outcome shows that the same ACS values as for NR TN UE are appropriate, and therefore reused. + +ACS test parameters in case 1 is applied. ACS requirements in case 2 can be specified based on the maximum input level of -40dBm. + +##### 7.4.3.2.5 Blocking characteristics + +For blocking characteristics, it is agreed, the same requirements as for NR TN UEs are applicable, and therefore reused. For NR satellite band n255, OOB requirements of n24 are reused. For n256, to keep UE implementation freedom with both options (i.e., reusing n65 duplexer or dedicated 30MHz duplexer) is agreed. FFS for n256 OOB requirements if the same hardware of n65 is expected to be reused. + +##### 7.4.3.2.6 Spurious response + +Spurious response is a measure of the ability of the receiver to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency for which a response is obtained, i.e. for which the out-of-band blocking limit is not met. To assume the same interfering signals for guaranteeing TN and NTN UE performance, TN spurious response requirements in section 7.7 of TS 38.101-1[17] could be applicable to NTN satellite access UEs. + +##### 7.4.3.2.7 Intermodulation characteristics + +Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal. To assume the same interfering signals for guaranteeing TN and NTN UE performance, TN wide-band intermodulation parameters in Table 7.8.2-1 of TS 38.101-1[17] could be applicable to NTN satellite access UEs. + +##### 7.4.3.2.8 Rx Spurious emissions + +The spurious emissions limits specified in TS 38.101-1[17] sub-clause 7.9 would also be applicable to NTN satellite access UEs referring to the ERC Recommendation 74-01[28] Annex 3 item 3.1.5 for Mobile Earth Stations (MES) (see Note 1bis) operating below 3 GHz: receivers, receive only MES and transmitters in the carrier-off state. + +##### 7.4.3.2.9 Void + +#### 7.4.3.3 “Reserved” (for Radiated receiver characteristics) + +[To be updated] + +### 7.4.4 UE antenna characteristics for satellite access + +#### 7.4.4.1 Handheld UE antenna characteristics for satellite access + +In Release 17, a reference antenna with a gain of 0dBi is assumed for handheld UE. However, the actual antenna gain can't meet 0dBi in each direction considering the antenna efficiency which is not 100%. Since all the Tx and Rx requirements are specified at conduct connector for handheld UE, the actual antenna characteristic will have no impact on the RF specification for Release 17 handheld UE. + +# --- 8 Conclusion + +It is recommended to take due consideration of contents in Chapter 6 and Chapter 7 when developing Technical Specifications of RF requirements for SAN, HAPS and UE using NR to support non-terrestrial networks (NTN). + +# Annex A: Calibration results of NTN components + +## A.1 Calibration assumptions at 2GHz + +Assumptions in Section 6.2 are adopted as the baseline for calibration. It should be noted there are different parts which are listed in Table A.1-1. + +**Table A.1-1: NTN Assumptions for calibration** + +| | | | +|------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------------| +| Propagation model 38.811[5] considerations | Basic path loss | Yes | +| | Atmospheric loss | 0 | +| | Ionospheric or scintillation loss | 0 | +| | O2I / building-entry loss | N/A | +| NTN SINR | SINR statistics target | Central beam (UL/DL) | +| | Interference | Co-channel interference from 6 adjacent beams | +| | BW / #UE | 20MHz / 1 DL, 3UL | +| | Polarization gain with 3dB | not considered | +| | Elevation angle | 90 degrees for GEO and LEO | +| HAPS SINR | SINR statistics target | 7 cells for DL and UL, HAPS UE is uniformly distributed in 7 cells | +| | Interference | Co- channel interference from other 6 cells | +| | BW / #UE | 20MHz/1DL, 3UL and each UE BW is 0.36MHz | +| | Polarization gain with 3dB | considered | +| Propagation model 38.811[5] considerations for HAPS | Basic path loss | yes | +| | Atmospheric loss | 0 | +| | Ionospheric or scintillation loss | 0 | +| | O2I / building-entry loss | 0 | +| HAPS | power control parameter | gamma =1, CL-ile = 121.45 | +| | rural vs. urban difference | only reflect on the propagation model. Other assumptions are the same. | + +## A.2 Calibration results at 2GHz + +The calibration results include SINR and coupling loss distributions in DL, and SINR, coupling loss and transmit power distributions in UL. Both rural and urban propagation models defined in TR 38.811[5] are considered. For NTN simulation, HAPS, LEO-600, LEO-1200 and GEO are calibrated and results are summarized in Table A.2-1, 2-2, 2-3 and 2-4. + +NOTE: The “-” means the data was not provided by its corresponding contributor. + +Table A.2-1: Calibration summary for NTN DL Rural cases + +| Calibration metrics | | DL Coupling Loss | | | DL Geometry SINR | | | +|---------------------|----------|------------------|--------|--------|------------------|-------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | +| LEO-600 | Samsung | 123.60 | 125.25 | 126.98 | -2.49 | -0.41 | 2.23 | +| | Qualcomm | 123.69 | 125.38 | 127.13 | -2.72 | -0.72 | 2.16 | +| | CATT | 123.59 | 125.21 | 127.10 | -3.07 | -0.84 | 2.22 | +| | THALES | 123.75 | 125.84 | 127.90 | -3.86 | -1.40 | 2.17 | +| | Huawei | 123.54 | 125.63 | 129.16 | 7.44 | 10.91 | 12.97 | +| | Xiaomi | 123.61 | 125.15 | 126.93 | -3.01 | -0.59 | 2.02 | +| | ZTE | 123.66 | 125.57 | 127.64 | -3.05 | -0.22 | 3.65 | +| | Nokia | 123.68 | 125.33 | 127.05 | -3.10 | -1.16 | 0.94 | +| | Ericsson | - | - | - | -2.58 | 6.97 | 9.95 | +| | FhG | 123.61 | 125.37 | 127.07 | -3.48 | -1.19 | 1.36 | +| | Variance | 0.00 | 0.04 | 0.46 | 10.03 | 16.13 | 14.92 | +| | Mean | 123.64 | 125.41 | 127.44 | -1.99 | 1.14 | 3.97 | +| LEO-1200 | Samsung | 129.61 | 131.27 | 132.99 | -2.47 | -0.40 | 2.23 | +| | Qualcomm | 129.60 | 131.21 | 132.91 | -2.35 | -0.42 | 2.13 | +| | CATT | 129.56 | 131.20 | 132.86 | -2.21 | -0.54 | 2.08 | +| | THALES | 129.68 | 131.51 | 133.28 | -2.91 | -0.79 | 2.27 | +| | Huawei | 129.48 | 131.28 | 133.83 | 1.47 | 7.62 | 12.76 | +| | Xiaomi | 129.68 | 131.21 | 132.94 | -2.55 | -0.70 | 1.65 | +| | ZTE | 129.71 | 131.53 | 133.31 | -2.42 | -0.18 | 3.66 | +| | Nokia | 129.70 | 131.36 | 133.10 | -3.09 | -1.20 | 0.94 | +| | Ericsson | - | - | - | -3.04 | 6.14 | 10.22 | +| | FhG | 129.75 | 131.30 | 132.97 | -3.36 | -1.11 | 1.20 | +| | Variance | 0.01 | 0.01 | 0.08 | 1.70 | 9.31 | 15.16 | +| | Mean | 129.64 | 131.32 | 133.13 | -2.29 | 0.84 | 3.91 | +| GEO | Samsung | 138.15 | 139.85 | 141.61 | -3.77 | -1.79 | 0.50 | +| | Qualcomm | 138.11 | 139.76 | 141.49 | -3.75 | -1.97 | 0.29 | +| | CATT | 137.97 | 139.80 | 141.51 | -3.74 | -2.08 | 0.36 | +| | THALES | 138.23 | 140.07 | 141.90 | -3.86 | -1.85 | 1.05 | +| | Huawei | 139.45 | 140.61 | 142.00 | -1.04 | 0.26 | 1.27 | +| | Xiaomi | 138.54 | 140.07 | 141.77 | -3.76 | -1.94 | 0.23 | +| | ZTE | 137.81 | 140.36 | 142.92 | -3.81 | -2.24 | -0.02 | +| | Nokia | 137.95 | 140.21 | 142.49 | -3.91 | -2.06 | -0.08 | +| | Ericsson | - | - | - | -6.62 | -0.18 | 3.60 | +| | FhG | 138.43 | 139.99 | 141.80 | -5.18 | -2.75 | -0.59 | +| | Variance | 0.21 | 0.07 | 0.20 | 1.72 | 0.79 | 1.22 | +| | Mean | 138.29 | 140.08 | 141.94 | -3.94 | -1.66 | 0.66 | +| HAPS | Nokia | 112.15 | 118.78 | 142.92 | -7.82 | 10.20 | 17.05 | +| | Qualcomm | 114.14 | 118.70 | 141.92 | -12.54 | 10.19 | 18.46 | +| | Variance | 0.99 | 0.00 | 0.25 | 5.58 | 0.00 | 0.50 | +| | Mean | 113.14 | 118.74 | 142.42 | -10.18 | 10.20 | 17.75 | + +**Table A.2-2: Calibration summary for NTN DL Urban cases** + +| Calibration metrics | | DL Coupling Loss | | | DL Geometry SINR | | | +|---------------------|----------|------------------|--------|--------|------------------|--------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | +| LEO-600 | Samsung | 118.57 | 125.31 | 132.31 | -2.67 | -0.50 | 2.17 | +| | Qualcomm | 118.56 | 125.21 | 132.93 | -2.94 | -0.84 | 2.12 | +| | CATT | 118.94 | 125.50 | 132.25 | -2.51 | -0.35 | 2.25 | +| | THALES | 119.00 | 125.67 | 132.50 | -3.93 | -1.50 | 2.13 | +| | Huawei | 120.16 | 125.74 | 131.63 | 1.80 | 9.01 | 15.14 | +| | Xiaomi | 119.19 | 125.45 | 132.56 | -2.69 | -0.79 | 1.57 | +| | ZTE | 118.90 | 125.58 | 132.40 | -3.05 | -0.61 | 3.37 | +| | Ericsson | - | - | - | -3.66 | 4.92 | 13.77 | +| | Nokia | 118.71 | 125.16 | 131.68 | -3.53 | -1.15 | 2.42 | +| | FhG | 119.50 | 125.89 | 133.01 | -11.24 | -3.00 | 3.96 | +| | Variance | 0.23 | 0.05 | 0.20 | 9.11 | 11.73 | 23.37 | +| | Mean | 119.06 | 125.50 | 132.36 | -3.44 | 0.52 | 4.89 | +| LEO-1200 | Samsung | 124.61 | 131.33 | 138.34 | -2.64 | -0.50 | 2.17 | +| | Qualcomm | 124.35 | 131.34 | 138.33 | -2.49 | -0.50 | 2.12 | +| | CATT | 125.02 | 131.78 | 137.85 | -2.63 | -0.37 | 2.23 | +| | THALES | 124.60 | 131.40 | 138.00 | -3.00 | -0.88 | 2.23 | +| | Huawei | 123.64 | 131.62 | 139.59 | -4.73 | 6.35 | 14.64 | +| | Xiaomi | 125.02 | 131.28 | 138.73 | -2.62 | -0.77 | 1.57 | +| | ZTE | 124.71 | 131.52 | 138.22 | -2.40 | -0.32 | 3.45 | +| | Ericsson | - | - | - | -3.67 | 4.81 | 14.30 | +| | Nokia | 123.97 | 130.42 | 136.92 | -3.58 | -1.27 | 2.28 | +| | FhG | 125.31 | 131.45 | 138.08 | -10.40 | -2.51 | 4.21 | +| | Variance | 0.25 | 0.13 | 0.45 | 5.29 | 7.18 | 23.32 | +| | Mean | 124.58 | 131.35 | 138.23 | -3.82 | 0.40 | 4.92 | +| GEO | Samsung | 133.18 | 139.90 | 146.93 | -5.72 | -2.09 | 1.10 | +| | Qualcomm | 132.93 | 139.89 | 146.94 | -5.83 | -2.21 | 0.92 | +| | CATT | 132.50 | 139.69 | 146.40 | -5.39 | -2.16 | 1.03 | +| | THALES | 133.30 | 139.97 | 146.60 | -4.97 | -2.16 | 1.34 | +| | Huawei | 132.43 | 138.44 | 145.29 | -5.93 | -0.54 | 6.53 | +| | Xiaomi | 133.23 | 139.68 | 146.97 | -5.24 | -2.63 | -0.56 | +| | ZTE | 133.72 | 140.50 | 146.99 | -5.23 | -2.51 | -0.11 | +| | Ericsson | - | - | - | -7.49 | -0.59 | 7.41 | +| | FhG | 132.74 | 139.69 | 146.97 | -11.58 | -3.57 | 4.35 | +| | Variance | 0.17 | 0.30 | 0.30 | 3.86 | 0.81 | 7.54 | +| | Mean | 133.00 | 139.72 | 146.64 | -6.38 | -2.05 | 2.45 | +| HAPS | Nokia | 111.39 | 145.66 | 164.30 | -29.10 | -10.47 | 16.29 | +| | Qualcomm | 112.00 | 143.12 | 159.76 | -30.86 | -10.70 | 20.84 | +| | Variance | 0.09 | 1.61 | 5.14 | 0.77 | 0.01 | 5.17 | +| | Mean | 111.69 | 144.39 | 162.03 | -29.98 | -10.58 | 18.57 | + +Table A.2-3: Calibration summary for NTN UL Rural cases + +| Calibration metrics | | UL Coupling Loss | | | UL Geometry SINR | | | UL UE Tx Power | | | +|---------------------|----------|------------------|--------|--------|------------------|--------|--------|----------------|-------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | @5% | @50% | @95% | +| LEO-600 | Samsung | 123.60 | 125.25 | 126.98 | -5.51 | -3.07 | -0.70 | 23.00 | 23.00 | 23.00 | +| | Qualcomm | 123.64 | 125.37 | 127.14 | -5.43 | -2.92 | -0.42 | 23.00 | 23.00 | 23.00 | +| | CATT | 123.68 | 125.47 | 127.29 | -7.22 | -1.78 | 0.42 | - | - | - | +| | THALES | 123.75 | 125.84 | 127.90 | -6.16 | -3.76 | -1.31 | 23.00 | 23.00 | 23.00 | +| | Huawei | 123.54 | 125.63 | 129.16 | -5.12 | -1.31 | 0.60 | 23.00 | 23.00 | 23.00 | +| | Xiaomi | 123.66 | 125.22 | 126.92 | -5.14 | -2.60 | 0.18 | 23.00 | 23.00 | 23.00 | +| | ZTE | 123.83 | 125.65 | 127.46 | -5.45 | -3.04 | -0.55 | 23.00 | 23.00 | 23.00 | +| | Ericsson | - | - | - | -14.64 | -8.63 | -3.87 | - | - | - | +| | FhG | 123.85 | 125.27 | 127.12 | -5.98 | -3.47 | -1.38 | 23.00 | 23.00 | 23.00 | +| | Variance | 0.01 | 0.04 | 0.48 | 8.19 | 3.96 | 1.63 | 0.00 | 0.00 | 0.00 | +| | Mean | 123.69 | 125.46 | 127.50 | -6.74 | -3.40 | -0.78 | 23.00 | 23.00 | 23.00 | +| LEO-1200 | Samsung | 129.62 | 131.27 | 132.99 | -9.44 | -7.60 | -5.83 | 23.00 | 23.00 | 23.00 | +| | Qualcomm | 129.56 | 131.18 | 132.89 | -9.40 | -7.61 | -5.78 | 23.00 | 23.00 | 23.00 | +| | CATT | 129.72 | 131.31 | 132.85 | -8.84 | -6.97 | -5.28 | - | - | - | +| | THALES | 129.68 | 131.51 | 133.28 | -9.46 | -7.68 | -5.75 | 23.00 | 23.00 | 23.00 | +| | Huawei | 129.48 | 131.28 | 133.83 | -9.48 | -6.85 | -5.18 | 23.00 | 23.00 | 23.00 | +| | Xiaomi | 129.61 | 131.23 | 132.93 | -7.97 | -6.09 | -4.20 | 23.00 | 23.00 | 23.00 | +| | ZTE | 129.60 | 131.38 | 133.25 | -9.27 | -7.32 | -5.63 | 23.00 | 23.00 | 23.00 | +| | Ericsson | - | - | - | -19.05 | -13.42 | -9.84 | - | - | - | +| | FhG | 129.68 | 131.28 | 133.06 | -9.51 | -7.69 | -5.98 | 23.00 | 23.00 | 23.00 | +| | Variance | 0.01 | 0.01 | 0.09 | 9.87 | 4.03 | 2.16 | 0.00 | 0.00 | 0.00 | +| | Mean | 129.62 | 131.31 | 133.14 | -10.27 | -7.91 | -5.94 | 23.00 | 23.00 | 23.00 | +| GEO | Samsung | 138.15 | 139.85 | 141.59 | -20.31 | -18.54 | -16.85 | 23.00 | 23.00 | 23.00 | +| | Qualcomm | 138.06 | 139.73 | 141.47 | -20.21 | -18.47 | -16.78 | 23.00 | 23.00 | 23.00 | +| | CATT | 138.07 | 139.61 | 141.26 | -19.86 | -18.24 | -16.70 | - | - | - | +| | THALES | 138.23 | 140.07 | 141.90 | -20.37 | -18.55 | -16.68 | 23.00 | 23.00 | 23.00 | +| | Huawei | 139.45 | 140.61 | 142.00 | -17.89 | -16.73 | -15.61 | 23.00 | 23.00 | 23.00 | +| | Xiaomi | 138.10 | 139.59 | 141.16 | -18.98 | -17.45 | -15.92 | 23.00 | 23.00 | 23.00 | +| | ZTE | 137.76 | 140.33 | 142.91 | -18.35 | -15.72 | -13.37 | 23.00 | 23.00 | 23.00 | +| | Ericsson | - | - | - | -30.59 | -25.37 | -21.63 | - | - | - | +| | FhG | 138.33 | 139.76 | 141.56 | -20.26 | -18.49 | -17.06 | 23.00 | 23.00 | 23.00 | +| | Variance | 0.22 | 0.12 | 0.27 | 12.84 | 6.56 | 4.15 | 0.00 | 0.00 | 0.00 | +| | Mean | 138.27 | 139.94 | 141.73 | -20.76 | -18.62 | -16.73 | 23.00 | 23.00 | 23.00 | +| HAPS | Nokia | 112.20 | 118.96 | 143.51 | -11.47 | 10.01 | 14.49 | 13.75 | 20.51 | 23.00 | +| | Qualcomm | 114.14 | 118.70 | 141.92 | -9.93 | 10.59 | 14.85 | 15.69 | 20.25 | 23.00 | +| | Variance | 0.94 | 0.02 | 0.64 | 0.60 | 0.09 | 0.03 | 0.93 | 0.02 | 0.00 | +| | Mean | 113.17 | 118.83 | 142.72 | -10.70 | 10.30 | 14.67 | 14.72 | 20.38 | 23.00 | + +Table A.2-4: Calibration summary for NTN UL Urban cases + +| Calibration metrics | | UL Coupling Loss | | | UL Geometry SINR | | | UL UE Tx Power | | | +|---------------------|----------|------------------|--------|--------|------------------|--------|--------|----------------|-------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | @5% | @50% | @95% | +| LEO-600 | Samsung | 118.58 | 125.30 | 132.31 | -11.38 | -3.64 | 3.57 | 23.00 | 23.00 | 23.00 | +| | Qualcomm | 118.71 | 125.16 | 132.66 | -11.83 | -3.91 | 2.64 | 23.00 | 23.00 | 23.00 | +| | CATT | 118.41 | 125.45 | 132.54 | -11.13 | -3.89 | 2.97 | - | - | - | +| | THALES | 119.00 | 125.67 | 132.50 | -11.15 | -3.92 | 2.70 | 23.00 | 23.00 | 23.00 | +| | Huawei | 120.16 | 125.74 | 131.63 | -11.52 | -4.25 | 1.70 | 23.00 | 23.00 | 23.00 | +| | Xiaomi | 118.63 | 125.29 | 132.62 | -11.20 | -3.19 | 4.57 | 23.00 | 23.00 | 23.00 | +| | ZTE | 118.92 | 125.71 | 132.43 | -11.19 | -3.75 | 3.56 | 23.00 | 23.00 | 23.00 | +| | Ericsson | - | - | - | -17.17 | -8.77 | 0.15 | - | - | - | +| | FhG | 117.88 | 125.14 | 132.15 | -11.34 | -4.04 | 3.87 | 23.00 | 23.00 | 23.00 | +| | Variance | 0.37 | 0.05 | 0.10 | 3.40 | 2.49 | 1.52 | 0.00 | 0.00 | 0.00 | +| | Mean | 118.79 | 125.43 | 132.35 | -11.99 | -4.37 | 2.86 | 23.00 | 23.00 | 23.00 | +| LEO-1200 | Samsung | 124.60 | 131.32 | 138.32 | -15.10 | -7.94 | -1.13 | 23.00 | 23.00 | 23.00 | +| | Qualcomm | 124.40 | 131.30 | 138.36 | -15.23 | -8.01 | -0.95 | 23.00 | 23.00 | 23.00 | +| | CATT | 123.95 | 131.27 | 137.95 | -13.61 | -6.83 | -0.26 | - | - | - | +| | THALES | 124.60 | 131.40 | 138.00 | -14.36 | -7.79 | -1.27 | 23.00 | 23.00 | 23.00 | +| | Huawei | 123.64 | 131.62 | 139.59 | -16.30 | -7.25 | -0.41 | 23.00 | 23.00 | 23.00 | +| | Xiaomi | 124.84 | 131.32 | 138.61 | -13.72 | -6.53 | 0.40 | 23.00 | 23.00 | 23.00 | +| | ZTE | 124.73 | 131.47 | 138.22 | -14.30 | -7.40 | -0.51 | 23.00 | 23.00 | 23.00 | +| | Ericsson | - | - | - | -21.09 | -13.52 | -5.47 | - | - | - | +| | FhG | 124.30 | 130.66 | 137.02 | -14.02 | -7.35 | -0.89 | 23.00 | 23.00 | 23.00 | +| | Variance | 0.15 | 0.07 | 0.45 | 4.83 | 3.93 | 2.55 | 0.00 | 0.00 | 0.00 | +| | Mean | 124.38 | 131.30 | 138.26 | -15.30 | -8.07 | -1.17 | 23.00 | 23.00 | 23.00 | +| GEO | Samsung | 133.17 | 139.89 | 146.92 | -25.64 | -18.62 | -11.90 | 23.00 | 23.00 | 23.00 | +| | Qualcomm | 132.96 | 139.86 | 146.90 | -25.69 | -18.61 | -11.73 | 23.00 | 23.00 | 23.00 | +| | CATT | 133.28 | 139.84 | 147.04 | -24.99 | -18.36 | -11.24 | - | - | - | +| | THALES | 133.30 | 139.97 | 146.60 | -25.25 | -18.47 | -11.80 | 23.00 | 23.00 | 23.00 | +| | Huawei | 132.43 | 138.44 | 145.29 | -24.06 | -17.38 | -11.26 | 23.00 | 23.00 | 23.00 | +| | Xiaomi | 133.03 | 139.55 | 146.75 | -24.19 | -17.39 | -10.63 | 23.00 | 23.00 | 23.00 | +| | ZTE | 133.58 | 140.24 | 146.91 | -22.79 | -15.32 | -8.86 | 23.00 | 23.00 | 23.00 | +| | Ericsson | - | - | - | -32.17 | -25.29 | -17.44 | - | - | - | +| | FhG | 133.46 | 140.15 | 147.08 | -25.79 | -18.93 | -12.26 | 23.00 | 23.00 | 23.00 | +| | Variance | 0.11 | 0.28 | 0.30 | 6.22 | 6.50 | 4.73 | 0.00 | 0.00 | 0.00 | +| | Mean | 133.15 | 139.74 | 146.69 | -25.62 | -18.71 | -11.90 | 23.00 | 23.00 | 23.00 | +| HAPS | Nokia | 111.39 | 145.66 | 164.30 | -28.44 | -10.17 | 14.88 | 12.94 | 23.00 | 23.00 | +| | Qualcomm | 111.89 | 143.11 | 158.93 | -26.02 | -8.42 | 14.90 | 13.44 | 23.00 | 23.00 | +| | Variance | 0.06 | 1.62 | 7.21 | 1.46 | 0.76 | 0.00 | 0.06 | 0.00 | 0.00 | +| | Mean | 111.64 | 144.38 | 161.61 | -27.23 | -9.29 | 14.89 | 13.19 | 23.00 | 23.00 | + +# Annex B: Calibration results of TN components + +## B.1 Calibration assumptions at 2GHz + +Assumptions in Section 6.2 are adopted as the baseline for calibration. It should be noted there are different parts which are listed in Table B.1-1. + +**Table B.1-1: TN Assumptions for calibration** + +| Calibration assumptions | | | +|-------------------------|---------------------|------------------------------| +| TN AAS | Rural | Element gain: 7.1 dBi | +| | | 3dB: H 90 / V 54 | +| | | Front-back: 30 H/V | +| | | Array: 8x8 | +| | | Element spacing: H 0.5/V 0.9 | +| | | Conducted Tx: 25 dBm | +| | | Ohmic loss: 2 dB | +| | | Mechanical downtilt: 3 deg | +| | | Polarization gain 3 dB | +| | | #UE: 1 DL/ 3 UL | +| | | 100% Outdoor | +| | Urban | ISD 7.5 KM | +| | | Element gain: 6.4 dBi | +| | | 3dB: H 90 / V 65 | +| | | Front-back: 30 H/V | +| | | Array: 8x8 | +| | | Element spacing: H 0.5/V 0.7 | +| | | Conducted Tx: 25 dBm | +| | | Ohmic loss: 2 dB | +| | | Mechanical downtilt: 10 deg | +| | | Polarization gain 3 dB | +| | | #UE: 1 DL/ 3 UL | +| | | 100% Outdoor | +| | | ISD 0.75 KM | +| TN non-AAS | Antenna gain | 17 dBi | +| | Conducted Tx | 46 dBm | +| | 3dB | R4-2108645 Section 2.4.2 | +| | Front-back | | +| | Mechanical downtilt | Rural 3 / Urban 10 | + +## B.2 Calibration results at 2GHz + +The calibration results include SINR and coupling loss distributions in DL, and SINR, coupling loss and transmit power distributions in UL. Both rural macro and urban macro propagation models defined in TR 38.901[10] are considered. NR BS with AAS and non-AAS antennas are calibrated separately and results are summarized in Table B.2-1, 2-2 and 2-3. NB-IoT scenarios are not calibrated. + +NOTE: The “-” means the data was not provided by its corresponding contributor. + +**Table B.2-1: Calibration summary for TN NR AAS DL cases** + +| Calibration metrics | | DL Coupling Loss | | | DL Geometry SINR | | | +|---------------------|----------|------------------|--------|--------|------------------|-------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | +| Urban Macro | Samsung | 60.05 | 88.58 | 98.98 | 8.47 | 24.01 | 45.77 | +| | Huawei | 52.84 | 85.79 | 103.53 | 5.75 | 22.23 | 43.40 | +| | Qualcomm | 57.89 | 87.11 | 100.61 | 5.08 | 19.51 | 43.65 | +| | Nokia | 59.04 | 87.59 | 99.32 | 12.42 | 20.15 | 36.50 | +| | Ericsson | - | - | - | 6.66 | 19.58 | 39.57 | +| | ZTE | 58.76 | 86.90 | 99.74 | 5.63 | 20.56 | 45.14 | +| | Variance | 6.42 | 0.83 | 2.69 | 6.35 | 2.62 | 10.70 | +| | Mean | 57.72 | 87.19 | 100.44 | 7.33 | 21.01 | 42.34 | +| Rural Macro | Samsung | 78.09 | 116.25 | 127.96 | 4.52 | 16.53 | 37.71 | +| | Huawei | 77.53 | 114.99 | 128.13 | 3.02 | 15.15 | 31.35 | +| | Qualcomm | 78.27 | 116.81 | 131.58 | 0.17 | 12.60 | 35.83 | +| | Nokia | 78.55 | 116.18 | 127.72 | 5.60 | 14.93 | 28.23 | +| | Ericsson | - | - | - | 10.03 | 20.17 | 37.72 | +| | Variance | 0.14 | 0.44 | 2.51 | 10.51 | 6.21 | 14.21 | +| | Mean | 78.11 | 116.06 | 128.85 | 4.67 | 15.87 | 34.17 | + +**Table B.2-2: Calibration summary for TN NR non-AAS DL cases** + +| Calibration metrics | | DL Coupling Loss | | | DL Geometry SINR | | | +|---------------------|----------|------------------|--------|--------|------------------|------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | +| Urban Macro | Samsung | 73.23 | 99.36 | 110.33 | -1.76 | 6.99 | 14.85 | +| | Huawei | 70.73 | 99.50 | 113.81 | -5.02 | 5.47 | 14.44 | +| | Qualcomm | 71.85 | 99.44 | 113.47 | -4.03 | 4.52 | 14.81 | +| | ZTE | 71.00 | 99.00 | 112.09 | -2.89 | 5.24 | 14.99 | +| | THALES | 71.84 | 100.22 | 112.26 | -3.03 | 4.25 | 14.40 | +| | Variance | 0.95 | 0.04 | 1.88 | 1.50 | 0.81 | 0.04 | +| | Mean | 71.73 | 99.50 | 112.39 | -3.35 | 5.29 | 14.70 | +| Rural Macro | Samsung | 87.82 | 125.94 | 138.22 | -4.25 | 5.77 | 15.42 | +| | Huawei | 93.87 | 126.75 | 141.60 | -8.93 | 1.10 | 15.33 | +| | Qualcomm | 89.63 | 127.43 | 142.65 | -7.37 | 2.54 | 15.47 | +| | THALES | 88.83 | 127.81 | 139.57 | -5.31 | 2.57 | 15.24 | +| | Variance | 6.43 | 0.37 | 3.58 | 3.78 | 3.81 | 0.00 | +| | Mean | 90.04 | 126.98 | 140.51 | -6.47 | 3.00 | 15.37 | + +Table B.2-3: Calibration summary for TN NR AAS UL cases + +| Calibration metrics | | UL Coupling Loss | | | UL Geometry SINR | | | UL UE Tx Power | | | +|---------------------|----------|------------------|--------|--------|------------------|-------|-------|----------------|-------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | @5% | @50% | @95% | +| Urban Macro | Samsung | 60.00 | 88.58 | 99.02 | 3.42 | 14.01 | 14.96 | -25.77 | 2.81 | 13.25 | +| | Huawei | 52.84 | 85.79 | 103.53 | 7.53 | 13.89 | 14.89 | -31.46 | 4.14 | 16.51 | +| | Qualcomm | 62.00 | 91.09 | 104.80 | 1.33 | 10.10 | 13.87 | -23.77 | 5.32 | 19.03 | +| | Nokia | 59.04 | 87.59 | 99.32 | 10.98 | 14.55 | 15.10 | -27.23 | 1.32 | 13.05 | +| | Ericsson | - | - | - | 6.83 | 12.94 | 15.08 | -28.52 | -1.70 | 13.98 | +| | ZTE | 58.43 | 87.22 | 98.46 | 5.47 | 13.42 | 14.81 | -27.59 | 1.20 | 12.44 | +| | Variance | 9.37 | 3.11 | 6.81 | 9.41 | 2.11 | 0.18 | 5.61 | 5.14 | 5.41 | +| | Mean | 58.46 | 88.05 | 101.03 | 5.93 | 13.15 | 14.78 | -27.39 | 2.18 | 14.71 | +| Rural Macro | Samsung | 78.00 | 116.25 | 127.95 | -4.86 | 7.03 | 14.96 | -7.77 | 23.00 | 23.00 | +| | Huawei | 77.53 | 114.99 | 128.13 | -10.84 | 4.42 | 14.86 | -3.46 | 23.00 | 23.00 | +| | Qualcomm | 82.05 | 120.47 | 135.46 | -13.41 | 2.07 | 14.69 | -3.72 | 23.00 | 23.00 | +| | Nokia | 78.42 | 116.20 | 127.85 | -4.15 | 7.69 | 15.17 | -7.85 | 22.99 | 22.99 | +| | Ericsson | - | - | - | 3.30 | 13.55 | 15.14 | -8.00 | 21.55 | 23.00 | +| | Variance | 3.20 | 4.32 | 10.50 | 33.91 | 14.88 | 0.03 | 4.41 | 0.34 | 0.00 | +| | Mean | 79.00 | 116.98 | 129.85 | -5.99 | 6.95 | 14.96 | -6.16 | 22.71 | 23.00 | + +Table B.2-4: Calibration summary for TN NR non-AAS UL cases + +| Calibration metrics | | UL Coupling Loss | | | UL Geometry SINR | | | UL UE Tx Power | | | +|---------------------|----------|------------------|--------|--------|------------------|-------|-------|----------------|-------|-------| +| CDF percentile | | @5% | @50% | @95% | @5% | @50% | @95% | @5% | @50% | @95% | +| Urban Macro | Samsung | 73.18 | 99.31 | 110.33 | -10.99 | 4.31 | 9.49 | -12.59 | 13.54 | 23.00 | +| | Huawei | 70.73 | 99.50 | 113.81 | -6.46 | 3.08 | 8.88 | -10.26 | 18.51 | 23.00 | +| | Qualcomm | 71.53 | 99.51 | 113.45 | -3.52 | 3.36 | 8.00 | -14.24 | 13.74 | 23.00 | +| | ZTE | 70.11 | 98.57 | 111.77 | -1.39 | 3.87 | 8.01 | -16.23 | 12.57 | 23.00 | +| | THALES | 71.84 | 100.22 | 112.26 | -0.01 | 4.13 | 6.80 | -14.05 | 14.90 | 22.76 | +| | Variance | 1.32 | 0.15 | 1.94 | 12.98 | 0.22 | 0.39 | 4.79 | 5.32 | 0.00 | +| | Mean | 71.48 | 99.42 | 112.32 | -4.48 | 3.75 | 8.24 | -13.47 | 14.65 | 22.95 | +| Rural Macro | Samsung | 87.78 | 125.93 | 138.22 | -17.23 | -3.82 | 14.65 | 2.01 | 23.00 | 23.00 | +| | Huawei | 93.87 | 126.75 | 141.60 | -24.83 | -9.72 | 14.75 | 12.88 | 23.00 | 23.00 | +| | Qualcomm | 89.53 | 127.64 | 142.62 | -21.39 | -5.65 | 14.33 | 3.76 | 23.00 | 23.00 | +| | THALES | 88.83 | 127.81 | 139.57 | -17.29 | -5.16 | 14.26 | 3.55 | 22.42 | 22.94 | +| | Variance | 6.55 | 0.49 | 3.54 | 9.66 | 6.07 | 0.03 | 22.71 | 0.00 | 0.00 | +| | Mean | 90.00 | 127.03 | 140.50 | -20.18 | -6.09 | 14.50 | 5.55 | 22.86 | 22.99 | + +# --- Annex C: Summary of NR-NTN co-existence study + +All NR-NTN co-existence study results have been captured in the list as attached. + +![Icon representing an Excel spreadsheet, showing a green 'X' on a document with a grid pattern.](ca6d62cc69ec88d9b5dc227b2dac7bc9_img.jpg) + +Icon representing an Excel spreadsheet, showing a green 'X' on a document with a grid pattern. + +Summary of +NR-NTN co-existence + +# --- Annex D: Summary of simulation results for the IoT derivation + +In this annex, simulations results used to derive the IoT value were collected. +[To be updated] + +# --- Annex EChange history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-11 | RAN4#101-e | R4-2120776 | | | | Added approved TPs in RAN4#101-e including:
R4-2120759, draft TP to TR 38.863: Operating bands and channel arrangements
R4-2120760, TP for 38.863 on system parameters on satellite bands
R4-2120761, TP to TR 38.863 – Regulatory aspects
R4-2120762, TP to TR 38.863: node class, RF RX (6.2)
R4-2120763, TP for 38.863 on NTN UE transmission characteristics
R4-2120772, Draft text proposal to update TR 38.863 NTN related RF and co-existence aspects | 0.1.0 | +| 2022-01 | RAN4#101-bis-e | | | | | Added approved TPs in RAN4#101-bis-e including:
R4-2201257, TP for 38.863 on system parameters to clarify “NTN satellite bands”
R4-2201838, Draft proposal to update TR 38.863 NTN related RF and co-existence aspects
R4-2202988, Draft Text Proposal for TR 38.863
R4-2203037, TP for 38.863 on UE transmission characteristics for satellite access
R4-2203038, TP for 38.863 on maximum input level for NTN UE
R4-2203039, TP for 38.863 on UE Receiver characteristics for satellite access
R4-2203040, TP to TR 38.863 on transmitter characteristics for satellite access node
R4-2203081, Draft text proposal to update TR 38.863 Chapter 3
R4-2203082, TP to TR 38.863 on channel raster and sync raster
R4-2203084, TP to TR 38.863 Regulatory aspects for HAPS
R4-2203085, TP to TR 38.863 on general aspects
R4-2203129, TP to TR 38.863 – Regulatory aspects | 0.2.0 | +| 2022-03 | RAN4#102-e | | | | | Added approved TPs in RAN4#102-e including:
R4-2205557,
R4-2207330, TP TR 38.863 7.4.1 NTN UE Requirement (General)
R4-2207333, TP to TR 38.863 on Section 5.2 NTN Satellite band
R4-2207338, TP for TR 38.863: Regulatory aspects for NTN satellite access nodes and UEs operating in UL1626.5-1660.5 MHz and DL 1525-1559 MHz frequencies ranges
R4-2207339, TP to TR 38.863 Regulatory aspects for HAPS
R4-2207345, Draft text proposal for Clauses 7, 7.1, 7.2, 7.3 in TR 38.863
R4-2207351, Draft text proposal to update TR 38.863 Chapter 6
R4-2207353, Draft text proposal for Clauses 6.4 and 6.5 in TR 38.863 to include simulation results based on Non-AAS antenna assumption
R4-2207360, Draft text proposal for Clause 7.3.4.7.3 OTA ACLR in TR 38.863
R4-2207367, Draft text proposal for Clause 7.3.5.6 OTA Out-of-band blocking in TR 38.863
R4-2207379, Draft text proposal for Clause 7.3.3.2.4 Out-of-band blocking in TR 38.863
R4-2207381, Draft text proposal for Clauses 7.3.3.2.3.1 Adjacent Channel Selectivity (ACS) and 7.3.3.2.3.2 In-band blocking in TR 38.863
R4-2207397, TP on TR 38.863 for NTN UE Tx requirements
R4-2207398, Draft TP to update TR 38.863 clause 7.4.3.2 on NTN UE ACS
R4-2207399, Draft TP to update TR 38.863 clause 7.4.3.2 on Blocking characteristics
R4-2207401, TP for TR38.863 on Intermodulation characteristics for NTN UE
R4-2207402, TP for 38.863 on spurious response for NTN UE
R4-2207403, TP for TR 38.863: Unwanted emissions for NTN satellite UEs transmitting in 1626.5 to 1660.5 MHz
R4-2207406, TP for TR 38.863: Updates to UE Maximum Output Power for n255
R4-2207414, TP for 38.863 on UE Receiver characteristics for satellite access
R4-2207460, Draft text proposal for Clause 7.3.2.2.4.1 ACLR in TR 38.863 | 0.3.0 | + +| | | | | | | | | +|---------|------------|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 2022-05 | RAN4#103-e | | | | | Added approved TPs in RAN4#103e including:
R4-2209089, TP for 38.863 on general part for NTN UE conducted receiver characteristics
R4-2209364, TP for 38.863 on UE Rx spurious emission requirements for satellite access
R4-2209365, TP for 38.863 on UE antenna characteristics for satellite access
R4-2210228, Draft text proposal for Clauses 6.4 and 6.5 Corrections Typo - TR 38.863
R4-2210636, TP to TR 38.863: coexistence issues between NTN and TN from Rel-17 RAN4 study.
R4-2210847, TP to TR 38.863 - Updates
R4-2210848, Draft text proposal for Clause 6.1 Coexistence Figures - TR 38.863
R4-2210853, TP for 38.863: clause 7.3.2 Conducted transmission characteristics
R4-2210858, TP to TR 38.863: Conducted reference sensitivity
R4-2210859, TP to TR 38.863: Conducted Rx dynamic range
R4-2210860, Draft text proposal for Clause 7.3.2.2.5 Transmitter spurious emissions - TR38.863
R4-2210865, Tentative draft pCR for Clause 7.3.2.2.4.2 Operating band unwanted emissions - TR 38.863
R4-2210866, Draft text proposal for Clause 7.3.2.2.1 SAN output power - TR 38.863
R4-2210867, Draft text proposal for Clause 7.3.3.3.1 OTA sensitivity - TR 38.863
R4-2210868, Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863
R4-2210869, Draft text proposal for Clause 7.3.3.3.3 OTA dynamic range - TR 38.863
R4-2210870, Draft text proposal for Clause 7.3.3.3.7 OTA receiver intermodulation - TR 38.863
R4-2210871, Draft text proposal for Clause 7.3.3.3.8 OTA in-channel selectivity - TR 38.863
R4-2210872, Draft text proposal for Clause 7.3.3.3.4 OTA in-band selectivity and blocking - TR 38.863
R4-2210875, TP for TR 38.863: Updates to n255 A-MPR Clause
R4-2211133, Draft Text Proposal to Update TR 38.863 Chapter 3,6 and 8
R4-2211134, Draft Text Proposal to Update TR 38.863 structure
R4-2211146, Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863 | 0.4.0 | +|---------|------------|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-06 | RAN#96 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-09 | RAN#97 | RP-222035 | 0001 | | F | CR for 38.863 to maintain UE RF parts | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0002 | 1 | F | Correction to TR 38.863 on Regulatory aspects for HAPS | 17.1.0 | +| 2023-03 | RAN#99 | RP-230516 | 0005 | | F | CR for TR 38.863 to maintain SAN parts | 17.2.0 | +| 2023-12 | RAN#102 | RP-233349 | 0009 | 1 | F | CR for TR 38.863, Correction on Satellite and UE Antenna and beam forming pattern modelling | 17.3.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233362 | 0010 | | B | NTN enhancement: CR to TR 38.863 NTN Ka-band Regulatory aspects | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38864/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38864/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38 --- /dev/null +++ b/marked/Rel-18/38_series/38864/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5 +size 9571 diff --git a/marked/Rel-18/38_series/38864/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38864/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d11a84925375a7bfe4c4cb5df0df597b8b8e3ae4 --- /dev/null +++ b/marked/Rel-18/38_series/38864/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd04f99d8abca3de3f4ec7ee170aceee8d0dd26cd26ae07c05bf12b3b39e2df1 +size 5687 diff --git a/marked/Rel-18/38_series/38864/raw.md b/marked/Rel-18/38_series/38864/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4a7e228451f8e4fcdf518c34a935273815865e11 --- /dev/null +++ b/marked/Rel-18/38_series/38864/raw.md @@ -0,0 +1,2232 @@ + + +# 3GPP TR 38.864 V18.1.0 (2023-03) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on network energy savings for NR (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Introduction..... | 9 | +| 5 Modeling and evaluation methodology..... | 10 | +| 5.1 Energy consumption model for BS ..... | 10 | +| 5.2 Evaluation methodology ..... | 13 | +| 6 Techniques to improve network energy savings..... | 13 | +| 6.1 Techniques in time domain ..... | 14 | +| 6.1.1 Technique A-1 Adapting transmission/reception of common channels/signals ..... | 14 | +| 6.1.1.1 Description of technique..... | 14 | +| 6.1.1.2 Analysis of NW energy saving and performance impact ..... | 14 | +| 6.1.1.3 Legacy UE and RAN1 specification impacts ..... | 23 | +| 6.1.2 Technique A-2 Adaptation of UE specific signals and channels ..... | 24 | +| 6.1.2.1 Description of technique..... | 24 | +| 6.1.2.2 Analysis of NW energy saving and performance impact ..... | 24 | +| 6.1.2.3 Legacy UE and RAN1 specification impacts ..... | 24 | +| 6.1.3 Technique A-3 UE wake up signal (WUS) for gNB..... | 24 | +| 6.1.3.1 Description of technique..... | 24 | +| 6.1.3.2 Analysis of NW energy saving and performance impact ..... | 25 | +| 6.1.3.3 Legacy UE and RAN1 specification impacts ..... | 31 | +| 6.1.4 Technique A-4 Adaptation of DTX/DRX..... | 31 | +| 6.1.4.1 Description of technique..... | 31 | +| 6.1.4.2 Analysis of NW energy saving and performance impact ..... | 31 | +| 6.1.4.3 Legacy UE and RAN1 specification impacts ..... | 34 | +| 6.1.4.4 Higher layer procedures..... | 34 | +| 6.1.5 Technique A-5 adaptation of SSB/SIB1 including on-demand SSB/SIB1 ..... | 35 | +| 6.1.5.1 Description of technique..... | 35 | +| 6.1.5.2 Analysis of NW energy saving and performance impact ..... | 35 | +| 6.1.5.3 Legacy UE and RAN1 specification impacts ..... | 36 | +| 6.1.6.1 Description of technique..... | 36 | +| 6.1.6.2 Analysis of NW energy saving and performance impact ..... | 37 | +| 6.1.6.3 Legacy UE and RAN1 specification impacts ..... | 37 | +| 6.1.7.1 Description of technique..... | 37 | +| 6.1.7.2 Analysis of NW energy saving and performance impact ..... | 37 | +| 6.1.7.3 Legacy UE and RAN1 specification impacts ..... | 37 | +| 6.2 Techniques in frequency domain ..... | 38 | +| 6.2.1 Technique B-1 Multi-carrier energy savings enhancements ..... | 38 | +| 6.2.1.1 Description of technique..... | 38 | +| 6.2.1.2 Analysis of NW energy saving and performance impact ..... | 38 | +| 6.2.1.3 Legacy UE and RAN1 specification impacts ..... | 45 | +| 6.2.2 Technique B-2 Adaptation of bandwidth part of UE(s) within a carrier..... | 45 | +| 6.2.2.1 Description of technique..... | 45 | +| 6.2.2.2 Analysis of NW energy saving and performance impact ..... | 45 | +| 6.2.2.3 Legacy UE and RAN1 specification impacts ..... | 46 | +| 6.2.3 Technique B-3 Adaptation of bandwidth of UE(s) within a BWP..... | 46 | +| 6.2.3.1 Description of technique..... | 46 | +| 6.2.3.2 Analysis of NW energy saving and performance impact ..... | 46 | +| 6.2.3.3 Legacy UE and RAN1 specification impacts ..... | 47 | + +| | | | +|-----------------|-----------------------------------------------------------------------------|-----------| +| 6.3 | Techniques in spatial domain..... | 47 | +| 6.3.1 | Technique C-1 Adaptation of spatial elements..... | 47 | +| 6.3.1.1 | Description of technique..... | 47 | +| 6.3.1.2 | Analysis of NW energy saving and performance impact ..... | 47 | +| 6.3.1.3 | Legacy UE and RAN1 specification impacts ..... | 55 | +| 6.3.2 | Technique C-2 Adaptation of TRPs in mTRP operation..... | 55 | +| 6.3.2.1 | Description of technique..... | 55 | +| 6.3.2.2 | Analysis of NW energy saving and performance impact ..... | 55 | +| 6.3.2.3 | Legacy UE and RAN1 specification impacts ..... | 56 | +| 6.4 | Techniques in power domain ..... | 56 | +| 6.4.1 | Technique D-1 Adaptation of transmission power of signals and channels..... | 56 | +| 6.4.1.1 | Description of technique..... | 56 | +| 6.4.1.2 | Analysis of NW energy saving and performance impact ..... | 56 | +| 6.4.1.3 | Legacy UE and RAN1 specification impacts ..... | 60 | +| 6.4.2 | Technique D-2 Over the air digital pre-distortion ..... | 60 | +| 6.4.2.1 | Description of technique..... | 60 | +| 6.4.2.2 | Analysis of NW energy saving and performance impact ..... | 60 | +| 6.4.2.3 | Legacy UE and RAN1 specification impacts ..... | 60 | +| 6.4.3 | Technique D-3 Tone reservation ..... | 61 | +| 6.4.3.1 | Description of technique..... | 61 | +| 6.4.3.2 | Analysis of NW energy saving and performance impact ..... | 61 | +| 6.4.3.3 | Legacy UE and RAN1 specification impacts ..... | 61 | +| 6.4.4 | Technique D-4 PA power bias adaptation..... | 61 | +| 6.4.4.1 | Description of technique..... | 61 | +| 6.4.4.2 | Analysis of NW energy saving and performance impact ..... | 62 | +| 6.4.4.3 | Legacy UE and RAN1 specification impacts ..... | 62 | +| 6.4.5 | Technique D-5 UE post-distortion ..... | 62 | +| 6.4.5.1 | Description of technique..... | 62 | +| 6.4.5.2 | Analysis of NW energy saving and performance impact ..... | 62 | +| 6.4.5.3 | Legacy UE and RAN1 specification impacts ..... | 62 | +| 6.5 | Higher layer aspects for network energy savings..... | 63 | +| 6.5.1 | Cell selection/reselection..... | 63 | +| 6.5.2 | Connected mode mobility..... | 63 | +| 6.5.3 | Inter-node Beam Activation ..... | 63 | +| 6.5.4 | Paging Enhancements..... | 63 | +| 7 | Conclusions..... | 63 | +| Annex A: | Evaluation scenarios, traffic models and loads ..... | 67 | +| Annex B: | Simulation assumptions ..... | 67 | +| Annex C: | Change history ..... | 72 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document captures the findings from the study item of "Study on network energy savings for NR" [2]. + +The study includes how to model network energy consumption especially for a base station, and evaluations of network energy saving gains as well as impact to network and user performance, by reusing existing KPI whenever applicable or new KPIs as needed. The study is also to identify techniques on gNB and UE side that can improve the network energy savings in various domains, potentially with UE feedback/assistance information and information exchange over network interfaces. + +The study prioritizes idle/empty and low/medium load scenarios, allow different loads among carriers and neighbor cells, allows legacy UEs to be able to continue accessing a network implementing Rel-18 network energy savings techniques, with the possible exception of techniques developed specifically for greenfield deployments. The study does not include aspects related to IAB. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP RP-220297: "Revised SI: Study on network energy savings for NR". +- [3] GSMA, 5G energy efficiencies: Green is the new black, . +- [4] 3GPP R1-2205551: "FL summary#4 for performance evaluation for NR NW energy savings". +- [5] 3GPP R1-2208216: "FL summary#3 for EVM for NR NW energy savings". +- [6] 3GPP R1-2213006: "FL summary for Post-110-R18- NW\_ES2". +- [7] 3GPP R1-2210592: "FL summary#4 for R18 NW\_ES". +- [8] 3GPP R1-2213013: "Simulation results summary for NW Energy Savings". +- [9] 3GPP R1-2210858: "Evaluation results and other performance aspects for network energy savings". +- [10] 3GPP R1-2211018: "Discussions on NW energy savings performance evaluation". +- [11] 3GPP R1-2211085: "Discussion on NW energy saving performance evaluation". +- [12] 3GPP R1-2211097: "NW energy savings performance evaluation". +- [13] 3GPP R1-2211241: "Discussion on performance evaluation of network energy savings". +- [14] 3GPP R1-2211458: "Discussion on NW energy savings performance evaluation". +- [15] 3GPP R1-2211903: "Evaluation results of NW energy saving techniques". +- [16] 3GPP R1-2211994: "Discussion on NW energy saving performance evaluation". + +- [17] 3GPP R1-2212128: "NW energy savings performance evaluation". +- [18] 3GPP R1-2212154: "Evaluations for network energy savings techniques". +- [19] 3GPP R1-2212259: "NW energy savings performance evaluation". +- [20] 3GPP R1-2212541: "Discussions on NW energy savings performance evaluation". +- [21] 3GPP R1-2212543: "NW energy savings performance evaluation". +- [22] 3GPP R1-2212563: "Discussion on Network energy saving performance evaluations". +- [23] 3GPP R1-2211692: "Discussion on network energy saving techniques". +- [24] 3GPP R1-2212429: "Discussion on Network energy saving techniques". +- [25] 3GPP R1-2211210: "Network energy saving techniques in time, frequency, and spatial domain". +- [26] 3GPP R1-2212129: "Network energy saving techniques". +- [27] 3GPP R1-2212765: "Discussion on Network energy saving techniques". +- [28] 3GPP R1-2212745: "NW energy savings performance evaluation". +- [29] 3GPP R1-2209996: "NW energy savings performance evaluation". +- [30] 3GPP R1-2213000: "NW energy savings performance evaluation". +- [31] 3GPP R1-2212814: "Discussion on Network energy saving techniques". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------| +| A | The ratio between dynamic power consumption of the antenna part and the dynamic DL power consumption of BS in active state; see clause 5.1 | +| E | Additional transition energy | +| P | Relative power | +| $s_a$ | The scaling factor for the fraction of active TRxRUs | +| $s_f$ | The scaling factor for the ratio between the RF bandwidth and the maximum system BW | +| $s_p$ | The scaling factor for the ratio of PSD per TxRU between the DL transmission and reference configuration | +| T | Total transition time | +| $\eta$ | The factor related to PA efficiency | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] + +| | | +|----------|------------------------------------| +| AAU | Active Antenna Unit | +| BM | Beam Management | +| BS | Base Station | +| BWP | Bandwidth Part | +| CC | Component Carrier | +| CHO | Conditional Handover | +| EE | Energy Efficiency | +| EIRP | Effective Isotropic Radiated Power | +| (N)ES | (Network) Energy Saving | +| FR | Frequency Range | +| FTP | File Transfer Protocol | +| IAB | Integrated Access and Backhaul | +| LLS | Link-level Simulation | +| OPEX | Operating Expenses | +| PF | Paging Frame | +| PO | Paging Occasion | +| PSD | Power Spectral Density | +| PSS | Primary Synchronization Signal | +| RB | Resource Block | +| RLM | Radio Link Monitoring | +| RO | RACH Occasion | +| SLS | System-level Simulation | +| SSB | Synchronization Signal Block | +| SSS | Secondary Synchronization Signal | +| TRP | Transmission/reception Point | +| T(R)x RU | Transmitter(receiver) Radio Unit | +| UPT | User Perceived Throughput | +| WUS | Wake-up Signal | +| XR | Extended Reality | + +# --- 4 Introduction + +Network energy saving is of great importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. As 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring very high data rates (e.g. XR), networks are being denser, use more antennas, larger bandwidths and more frequency bands. The environmental impact of 5G needs to stay under control, and novel solutions to improve network energy savings need to be developed. + +Energy consumption has become a key part of the operators' OPEX. According to the report from GSMA [3], the energy cost on mobile networks accounts for ~23% of the total operator cost. Most of the energy consumption comes from the radio access network and in particular from the AAU, with data centres and fibre transport accounting for a smaller share. The power consumption of a radio access can be split into two parts: the dynamic part which is only consumed when data transmission/reception is ongoing, and the static part which is consumed all the time to maintain the necessary operation of the radio access devices, even when the data transmission/reception is not on-going. + +Therefore, there is a need to study and develop a network energy consumption model especially for the base station (a UE power consumption model was already defined in TR38.840), KPIs, an evaluation methodology and to identify and study network energy savings techniques in targeted deployment scenarios. The study investigates how to achieve more efficient operation dynamically and/or semi-statically and finer granularity adaptation of transmissions and/or receptions in one or more of network energy saving techniques in time, frequency, spatial, and power domains, with potential support/feedback from UE, potential UE assistance information, and information exchange/coordination over network interfaces. + +The study not only evaluates the potential network energy consumption gains, but also assesses and balances the impact on network and user performance, e.g. by looking at KPIs such as spectral efficiency, capacity, UPT, latency, UE power + +consumption, complexity, handover performance, call drop rate, initial access performance, SLA assurance related KPIs, etc. The techniques studied could avoid having a large impact to such KPIs. + +# 5 Modeling and evaluation methodology + +## 5.1 Energy consumption model for BS + +For evaluation purpose, the energy consumption modeling for a BS for evaluation includes: + +- Reference configuration +- Multiple power state(s) including sleep or non-sleep modes with relative power, and associated transition time/energy +- Scaling method to be applied. + +For reference configuration, the following is considered for single CC case. + +**Table 5.1-1: Reference configuration for BS power consumption model** + +| | Set 1 FR1 | Set 2 FR1 | Set 3 FR2 | +|---------------------------|-----------|-----------|-----------| +| Duplex | TDD | FDD | TDD | +| System BW | 100 MHz | 20 MHz | 100 MHz | +| SCS | 30 kHz | 15 kHz | 120 kHz | +| Number of TRP | 1 | 1 | 1 | +| Total number of DL TX RUs | 64 | 32 | 2 | +| Total DL power level | 55 dBm | 49 dBm | 33 dBm* | +| Total number of UL Rx RUs | 64 | 32 | 2 | + +\*Note: EIRP limit is 63 dBm for the reference configuration. The EIRP value is scaled with the number of TxRUs. + +For power states, for non-sleep mode and TDD, the BS power consumption for DL and UL are separately modelled, allowing DL-only transmission or UL-only reception. The relative power value in power consumption model tables for UL reception and/or DL transmission is provided based on the reference configurations. For simultaneous DL and UL transmission for FDD, the power for UL reception is neglected in this study. + +The power states of power consumption model are provided as Table 5.1-2. Note: The BS power model defined in this study is a simplified model for the purposes of evaluations, considering single-RAT NR BSs only. This does not mean a BS cannot benefit from the identified techniques when serving multi-RAT. Transition among power states, transition time, are implementation specific, and different BS types may support a different number of power states with different characteristics, i.e., power consumption values and required transition time. + +During the transition time period, relative power of sleep mode $i$ is assumed to be consumed. For RAN1 evaluation purpose, the values of relative power $P$ for BS Category 1 and BS Category 2 for respective set of reference configurations are provided in Table 5.1-3. + +Additional transition energy $E$ and total transition time $T$ also include energy and time for both ramping down and ramping up. The values of total transition time for BS power state transition are given in Table 5.1-4, which are the same across different sets of reference configurations for a given BS Category. The values of additional transition energy for reference configuration Set 1, Set 2 and Set 3, with unit in (relative power) \* (duration in msec), are provided in Table 5.1-5. + +For background and discussion related to the power models as well as the corresponding values for relative power, transition time and additional transition energy, see [4][5][6][7] and references therein. + +**Table 5.1-2: Power states of BS power consumption model** + +| Power state | Characteristic | Relative Power $P$ | Additional transition energy 2 $E$ | Total transition time $T$ | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------------------------|---------------------------| +| Deep sleep 1 | There is neither DL transmission nor UL reception. Time interval for the sleep should be larger than the total transition time entering and leaving this state. | P1 | E1 | T1 | +| Light sleep | There is neither DL transmission nor UL reception. Time interval for the sleep should be larger than the total transition time entering and leaving this state. | P2 | E2 | T2 | +| Micro sleep | There is neither DL transmission nor UL reception. Immediate transition is assumed for network energy saving study purpose from or to a non-sleep state. | P3 | 0 | 0 | +| Active DL | There is only DL transmission. | P4 | N.A. | | +| Active UL | There is only UL reception. | P5 | | | + +Note 1: Depending on implementations, there could be a state that the power is lower than deep sleep and requires larger total transition time, e.g. hibernating sleep or Quasi-off, which is not explicitly modelled in this study for evaluation purpose. +Note 2: Unit in relative power times duration. + +**Table 5.1-3: Relative power values $P$ for reference configuration Set 1, Set 2 and Set 3** + +| Power state | BS Category 1 | | | BS Category 2 | | | +|-------------|---------------|-------|-------|---------------|-------|-------| +| | Set 1 | Set 2 | Set 3 | Set 1 | Set 2 | Set 3 | +| Deep sleep | 1 | | | 1 | | | +| Light sleep | 25 | | | 2.1 | | | +| Micro sleep | 55 | 50 | 38 | 5.5 | 5 | 3 | +| Active DL | 280 | 200 | 152 | 32 | 26 | 17.6 | +| Active UL | 110 | 90 | 80 | 6.5 | 5.8 | 4.2 | + +**Table 5.1-4: Total transition time $T$ for reference configuration Set 1, Set 2 and Set 3** + +| Power state | BS Category 1 | BS Category 2 | +|-------------|---------------|---------------| +| Deep sleep | 50 ms | 10 s | +| Light sleep | 6 ms | 640 ms | + +**Table 5.1-5: Additional transition energy $E$ for reference configuration Set 1, Set 2 and Set 3** + +| Power state | BS Category 1 | BS Category 2 | +|-------------|---------------|---------------| +| Deep sleep | 1000 | 17000 | +| Light sleep | 90 | 1088 | + +For scaling method, for non-sleep mode, the scaling can be based on one or more of the following: + +- number of used physical antenna elements, or TX/RX RUs +- occupied BW/RBs for DL and/or UL in a slot/symbol in one CC +- number of CCs in CA +- number of TRPs +- PSD or transmit power +- number of DL and/or UL symbols occupied within a slot. + +For active DL transmission, the BS power consumption is provided by + +$$P^{DL} = P_{static}^{DL} + P_{dynamic}^{DL}$$ + +where + +- $P_{static}^{DL}$ is a static part of power for BS in active, which is not scaled based on reference configurations. + - Baseline: $P_{static}^{DL} = P_3$ + - Optional: $P_{static}^{DL} = 1.5 * P_3$ +- $P_{dynamic}^{DL}$ is a dynamic part of power for BS in active, which is scaled based on reference configuration. + - Baseline: $P_{dynamic}^{DL} = s_a * \left( P_{dyn,ante} + \frac{s_f * s_p}{\eta(s_f, s_p)} * P_{dyn,joint} \right)$ , where $s_a, s_f, s_p$ is the fraction of active TRxRUs, the ratio between the RF bandwidth and the maximum system BW, and the ratio of PSD per TRxRU between the DL transmission and reference configuration, respectively. + +$$\begin{cases} P_{dyn,ante} = \mathbf{A} * (P_4 - P_{static}^{DL}) \\ P_{dyn,joint}/\eta(s_f = 1, s_p = 1) = (1 - \mathbf{A}) * (P_4 - P_{static}^{DL}) \end{cases}$$ + +- $P_{dyn,joint}/\eta(s_f, s_p)$ is the power part related to PA. +- For simplicity + - $\mathbf{A}$ = baseline: 0.4; optional: 0.1, 0.7; + - For $\eta(s_f, s_p)$ , in evaluation, company to report the assumption from below: + - If one value of $\eta(s_f, s_p)$ is used for evaluation, $\eta(s_f, s_p) = 1$ for any $s_f, s_p$ ; + - If two values of $\eta(s_f, s_p)$ are used for evaluation, $\eta(s_f, s_p) = 0.76$ if $s_f * s_p < 0.5$ ; otherwise, $\eta(s_f, s_p) = 1$ . + +For active UL transmission, the BS power consumption for is provided by + +$$P^{UL} = P_{static}^{UL} + P_{dynamic}^{UL}$$ + +where + +- $P_{static}^{UL}$ is a static part of power for BS in active, which is not scaled based on reference configurations. +- $P_{dynamic}^{UL} = s_a * P_{dyn,ante}^{UL}$ is a dynamic part of power for BS in active, which is scaled based on reference configuration, and $s_a$ is the fraction of active TRxRUs. +- Baseline: + - $P_{static}^{UL} = P_3$ + - $P_{dyn,ante}^{UL} = P_5 - P_3$ when no scaling is applied (i.e. scaling factor is 1). + +Note, + +- For multi-carrier, the total power consumption of BS is calculated as is the sum of the power consumption of each CC; for intra-band multi-carrier with contiguous CCs, the power consumption of each additional CC is scaled by 0.7. +- For multi-TRP, the total power consumption of BS is assumed as is the sum of the power consumption of each TRP. Company to report whether $P_{static}$ is shared among TRPs (if shared, $P_{static}$ is accounted once). +- Company to additionally report the assumption for antenna adaptation delay, e.g. immediate adaptation, or with a transition time of 1-3 ms, etc. +- In time domain, the power consumption in a slot is the sum of the power consumption associated with symbols in the slot. The symbol may correspond to uplink symbol, downlink symbol, or symbol without uplink and downlink. Company to report how the summation is performed along with evaluation results. + +Other values for the above scaling formula, and other scaling approaches can be optionally reported, including + +- $P_{DL} = P_4 \left( (0.4 + 0.6 * s_f * s_p * \eta(s_f, s_p)) (0.4 + 0.6 * s_a) \right)$ . At least $\eta(s_f, s_p) = 1$ is supported. +- $P_{UL} = P_5 (0.8 + 0.2 * s_f) (0.4 + 0.6 * s_a)$ , with $s_f$ being the ratio of RF BW to the maximum system BW. + +## 5.2 Evaluation methodology + +For evaluation, the BS energy consumption model at least include the power consumption of BS on slot-level, and symbol-level power consumption to reflect different BW (or RB utilization)/time-occupancy/tx-rx direction of different symbols in a slot is considered. System simulation evaluations can be per slot regardless of detailed approach for calculating symbol-level power consumption. All calculation of energy consumption is to use the same time unit. Companies are to indicate which time unit is used. + +The evaluation baseline includes at least NR R15 mandatory without capability features. Optional features from R15 onwards (e.g. CA, MIMO) as well as implementation-based energy saving techniques are to be explicitly reported and described if used in the evaluation baseline. + +SLS is considered as baseline evaluation method. Other method, including numerical analysis and LLS can also be considered. At least one of the methods is to be selected and used for evaluation of a specific technique (selection and criteria is up to proponent). + +For evaluation purpose, network energy saving gain is computed based on the energy consumptions for a technique and the baseline over the same duration. Percentage of energy consumption reduction from the baseline is used to express BS energy saving gain. In addition to the BS energy saving gain, at least UPT/UE power consumption/access delay/latency is to be considered for performance impact evaluation. Other KPIs can be optionally reported, conditioned with clear definition/descriptions provided. Note for potential new channel/signals, e.g. WUS from UE, the assumption for detection reliability at BS side is to be reported (performance and complexity impact would subject to results and further discussion). + +For initial evaluations, there is always a non-sleep mode assumed between adjacent sleep modes. + +System level evaluation assumptions are provided in Annex A and B. + +Companies are to report the assumption details for the reception of a low-power UL channel/signal, if used, including power states, additional transition energy, and transition times, receiver details (e.g. architecture and receiver sensitivity), and other impact/change on the power consumption model. + +# --- 6 Techniques to improve network energy savings + +Various techniques in time, frequency, spatial and power domains are studied. Companies' simulation results as well as evaluation assumption details are gathered in [8]. In this document, results as well as some notable assumptions and setting are explicitly present in relevant tables. Also, the categorization of techniques in terms of technical domain and results presentation/tabulation are for study/evaluation purpose. This does not preclude to further merge or combine certain techniques. + +For analysis of impact on legacy UE and RAN1 specification, the list described in corresponding clauses is not an exhaustive list. RAN1 may identify additional impact and determine that the listed impact may no longer apply to the described technique(s) as specification is further developed. + +## 6.1 Techniques in time domain + +### 6.1.1 Technique A-1 Adapting transmission/reception of common channels/signals + +#### 6.1.1.1 Description of technique + +In Rel-15 NR, time-domain positions of transmitted SSBs within a half frame are semi-statically configured. Further, UE assumes a single periodicity for the transmitted SSBs. The transmission of common signal and channels or reception of random-access signals may limit the gNB ability to use (deeper) sleep modes to save energy. Currently, system information (SI) update mechanism can adapt the parameters in the cell, such as those associated with downlink common and broadcast signals, such as SSB/SI/paging/cell common PDCCH, and/or the periodicity/availability of uplink random access resources. + +Technique A-1 adapts the transmission pattern (when applicable) of downlink common and broadcast signals, such as SSB/SI/paging/cell common PDCCH, and/or the transmission pattern/availability of uplink random access opportunities. Adaptation of the transmission pattern includes changes to periodicity, time resource locations, and omitting of specific signals/channels. The transmission pattern can be adapted semi-statically or dynamically. + +#### 6.1.1.2 Analysis of NW energy saving and performance impact + +The following table captures the simulation results for the technique A-1-1 that use simplified version of SSB, such as only PSS, only PSS and SSS without PBCH, or PSS and SSS with partial PBCH. + +Based on the simulation results, at empty load, one source shows that BS energy saving gain can be achieved by 15.7%~28.3% with only PSS and SSS transmitted from SSB, and half-reduced SIB1 transmission. One source shows that the gain from light SSB only ranges from 0.7% to 4.4%, which slightly increases as the listening periodicity of WUS from UE becomes larger. One source shows that with simplified SSB of PSS, SSS and partial PBCH, for empty load and Set 1 reference configuration, 2.4% BS energy savings can be achieved. One source shows 30.49% BS energy savings with 2-symbol simplified SSB for FR2. + +No impact on UPT was observed due to empty load. + +**Table 6.1.1.2-1: BS energy savings by simplified SSB** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT/access delay/latency/ UE power consumption (%: loss w.r.t. baseline) | Reference configuration | Baseline configuration/assumption | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------|-------------|--------------------------------------------------------------------------|-------------------------|-------------------------------------------------------------------------------| +| CMCC
[9] | SSB and SIB1 repetition period 40ms, for other 20ms occasions, only PSS and SSS are transmitted. | cat.2 | Zero | 15.7% | / | Set 1 | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | +| | SSB and SIB1 repetition period 40ms, for other 20ms occasions, only PSS and SSS are transmitted. | cat.1 | Zero | 28.3% | / | | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | +| vivo
[10] [20] | SSB structure adaptation including light SSB (ES scheme: 20ms light-SSB and SIB1, 20ms RACH listening only PSS and SSS for light-SSB) | Cat1 | Zero | 0.9% | 0% | Set 1 | Baseline scheme: 20ms SSB and SIB1, 20ms RACH listening | +| | SSB structure adaptation including light SSB (ES scheme: 160ms light-SSB, 20ms UEWUS listening only PSS and SSS for light-SSB) | Cat1 | Zero | 1.2% | 0% | Set 1 | Baseline scheme: 160ms SSB, 20ms UEWUS listening | +| | SSB structure adaptation including light SSB (ES scheme: 160ms light-SSB, 80ms UEWUS listening only PSS and SSS for light-SSB) | Cat1 | Zero | 2.4% | 0% | | Baseline scheme: 160ms SSB, 80ms UEWUS listening | +| | SSB structure adaptation including light SSB (ES scheme: 160ms light-SSB, | Cat1 | Zero | 4.4% | 0% | | Baseline scheme: 160ms SSB, 160ms UEWUS listening | + +| | | | | | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------|------|---------|----|-------|-------------------------------------------------------------------------------| +| | 160ms UEWUS listening only PSS and SSS for light-SSB | | | | | | | +| | SSB structure adaptation including light SSB (ES scheme: 20ms light-SSB and SIB1, 20ms RACH listening only PSS and SSS for light-SSB) | Cat2 | Zero | 0.7% | 0% | | Baseline scheme: 20ms SSB and SIB1, 20ms RACH listening | +| | SSB structure adaptation including light SSB (ES scheme: 160ms light-SSB, 20 UEWUS listening only PSS and SSS for light-SSB) | Cat2 | Zero | 0.8% | 0% | | Baseline scheme: 160ms SSB, 20ms UEWUS listening | +| | SSB structure adaptation including light SSB (ES scheme: 160ms light-SSB, 80ms UEWUS listening only PSS and SSS for light-SSB) | Cat2 | Zero | 0.8% | 0% | | Baseline scheme: 160ms SSB, 80ms UEWUS listening | +| | SSB structure adaptation including light SSB (ES scheme: 160ms light-SSB, 160ms UEWUS listening only PSS and SSS for light-SSB) | Cat2 | Zero | 0.8% | 0% | | Baseline scheme: 160ms SSB, 160ms UEWUS listening | +| CEWIT [24] | simplified SSB with repetition period 20ms, only PSS and SSS with partial PBCH are transmitted in simplified SSB | Cat.1 | Zero | 2.4% | | Set 1 | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | +| Qualcomm [30] | Simple SSB with 2 OFDM symbols and a transmission period of 20 ms | Cat 1 | Zero | 30.49 % | / | Set 3 | Baseline: normal SSB with 20ms repetition period; FR2 with 32 beams per cell. | + +The following table captures the simulation results for the technique A-1-2 by which transmission occasion of one or more common signals/channels, which are SIB1 and SSB based on the submitted results, can be skipped. + +Based on the results, + +- One source observed that statically skipping certain SIB1 transmission occasions under Set 1 reference configuration for BS Category 1 can achieve energy saving gain by 2.6%~3.9% compared to the baseline of 20ms SSB&SIB1 repetition periodicity at low load. No impact to UPT was observed. There is no random-access procedure modelled in the simulation, therefore the impact on access delay/latency is not shown. +- One source observed that static adaptation of number of SSB can achieve energy saving gain by 0.3%~25.4% at different scenarios with FTP3 model. The gain generally increases when the traffic load becomes lighter while decreases as the SSB periodicity becomes larger. For a same traffic load and SSB periodicity, the gain increases as the number of SSB can be reduced. For FR2 with larger number of SSB for baseline, there is generally larger gain observed than FR1. Due to reduced number of SSB, access delay is increased. Performance of dynamic adaptation of SSB numbers is not provided. There is no random-access procedure modelled in the simulation, therefore the impact on access delay/latency is not shown. + +**Table 6.1.1.2-2: BS energy savings by skipping one or more common signals/channels** + +| Company | ES scheme | Load scenario | ES gain (%) | BS Category/Reference configuration/Baseline configuration/assumption | Other evaluation methodology/assumption details/other performance impact | +|---------------------|----------------------------------------------------------------------------|----------------------|------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| OPPO [14] | Transmission occasion of SIB1 with 24 RBs for 20 ms periodicity is skipped | low load(RU-10%) | 2.6% | Cat 1
Set 1
SIB1 with 24 RBs for 20 ms periodicity, SSB with 20 RBs for 20 ms periodicity | SLS
FTP3 (0.5MB as packet size, 200ms as mean inter-arrival time)
UPT/Access delay/Latency: almost similar with the baseline | +| | | low load(RU-0.2%) | 3.9% | | SLS
IM (0.1MB as packet size, 2s as mean inter-arrival time)
UPT/Access delay/Latency: almost similar with the baseline | +| Samsung [21] | the number of SSB adaptation | Medium load: 42 % RU | 1.9%, 2.8%, 3.3% | Cat 1
Set 1 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | | Light load: 24 % RU | 3.1%, 6.1%, 7.6% | | | + +| | | | | +|----------------------|-----------------------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Low load: 7.5 % RU | 5.5%, 11.0%, 13.8% | 8 SSBs for FR1 and ssb-periodicity = 20 | | +| | Low load: 2 % RU | | | +| Medium load: 42 % RU | 7.2%, 14.3%, 17.9% | Cat 2
Set 1
8 SSBs for FR1 and ssb-periodicity = 20 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | 2.0%, 3.0%, 3.5% | | | +| Light load: 24 % RU | 2.8%, 4.2%, 4.9% | | | +| | Low load: 7.5 % RU | | | +| Low load: 2 % RU | 4.4%, 6.6%, 7.7% | | | +| | 5.3%, 7.9%, 9.2% | | | +| Medium load: 42 % RU | 3.3%, 5.0%, 5.8%, 6.3%, 6.5%, 6.6% | Cat 1
Set 3
64 SSBs for FR2 and ssb-periodicity = 20 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Light load: 24 % RU | | | +| Low load: 7.5 % RU | 4.3%, 17.6%, 19.5%, 20.5%, 21.0%, 21.3% | | | +| | 7.1%, 13.6%, 16.9%, 18.5%, 19.3%, 19.7% | | | +| Low load: 2 % RU | 8.3%, 15.9%, 19.7%, 21.6%, 22.6%, 23.0% | | | +| | Medium load: 42 % RU | | | +| Medium load: 42 % RU | 4.0%, 5.9%, 6.9%, 7.4%, 7.7%, 7.8% | Cat 2
Set 3
64 SSBs for FR2 and ssb-periodicity = 20 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Light load: 24 % RU | | | +| Low load: 7.5 % RU | 5.4%, 8.1%, 9.5%, 10.2%, 10.5%, 10.7% | | | +| | 8.2%, 12.2%, 14.3%, 15.3%, 15.8%, 16.1% | | | +| Low load: 2 % RU | 9.6%, 14.4%, 16.8%, 18.0%, 18.6%, 18.9% | | | +| | Medium load: 42 % RU | | | +| Medium load: 42 % RU | 1.1%, 2.2%, 2.7% | Cat 1
Set 1
8 SSBs for FR1 and ssb-periodicity = 40 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | Light load: 24 % RU | | | +| Low load: 7.5 % RU | 1.6%, 3.2%, 4.0% | | | +| | 3.1%, 6.1%, 7.7% | | | +| Low load: 2 % RU | 4.2%, 8.3%, 10.3% | | | +| | Medium load: 42 % RU | | | +| Medium load: 42 % RU | 1.0%, 1.6%, 1.8% | Cat 2
Set 1
8 SSBs for FR1 and ssb-periodicity = 40 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | Light load: 24 % RU | | | +| Low load: 7.5 % RU | 1.5%, 2.2%, 2.5% | | | +| | 2.3%, 3.5%, 4.0% | | | +| Low load: 2 % RU | 2.8%, 4.2%, 4.9% | | | +| | Medium load: 42 % RU | | | +| Medium load: 42 % RU | 1.9%, 3.6%, 4.4%, 4.8%, 5.0%, 5.2% | Cat 1
Set 3
64 SSBs for FR2 and ssb-periodicity = 40 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Light load: 24 % RU | | | +| Low load: 7.5 % RU | 2.6%, 5.0%, 6.1%, 6.7%, 7.0%, 7.2% | | | +| | 4.0%, 7.6%, 9.4%, 10.4%, 10.8%, 11.0% | | | +| Low load: 2 % RU | 4.8%, 9.2%, 11.4%, 12.5%, 13.1%, 13.3% | | | +| | Medium load: 42 % RU | | | +| Medium load: 42 % RU | 2.1%, 3.1%, 3.6%, 3.9%, 4.0%, 4.1% | Cat 2 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | + +| | | | | +|----------------------|-----------------------------------------------------------|-------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Light load: 24 % RU | 2.9%, 4.3%, 5.1%, 5.4%, 5.6%, 5.7% | Set 3
64 SSBs for FR2 and ssb-periodicity = 40 | | +| | Low load: 7.5 % RU
4.4%, 6.7%, 7.8%, 8.3%, 8.6%, 8.8% | | | +| | Low load: 2 % RU
5.4%, 8.1%, 9.4%, 10.1%, 10.4%, 10.6% | | | +| Medium load: 42 % RU | 0.6%, 1.1%, 1.4% | Cat 1
Set 1
8 SSBs for FR1 and ssb-periodicity = 80 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | Light load: 24 % RU
1.0%, 2.3%, 3.0% | | | +| | Low load: 7.5 % RU
2.5%, 5.9%, 7.6% | | | +| Medium load: 42 % RU | Low load: 2 % RU
4.5%, 10.7%, 13.8% | Cat 2
Set 1
8 SSBs for FR1 and ssb-periodicity = 80 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | 0.5%, 0.8%, 0.9% | | | +| | Light load: 24 % RU
0.7%, 1.1%, 1.3% | | | +| Medium load: 42 % RU | Low load: 7.5 % RU
1.2%, 1.8%, 2.1% | Cat 1
Set 3
64 SSBs for FR2 and ssb-periodicity = 80 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Low load: 2 % RU
1.4%, 2.1%, 2.5% | | | +| | 1.0%, 1.8%, 2.3%, 2.5%, 2.6%, 2.6% | | | +| Medium load: 42 % RU | Light load: 24 % RU
1.3%, 2.6%, 3.2%, 3.5%, 3.7%, 3.7% | Cat 2
Set 3
64 SSBs for FR2 and ssb-periodicity = 80 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Low load: 7.5 % RU
2.1%, 4.1%, 5.0%, 5.5%, 5.8%, 5.9% | | | +| | Low load: 2 % RU
2.6%, 5.0%, 6.2%, 6.8%, 7.1%, 7.2% | | | +| Medium load: 42 % RU | 1.1%, 1.6%, 1.8%, 2.0%, 2.0%, 2.1% | Cat 1
Set 3
64 SSBs for FR2 and ssb-periodicity = 80 | FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Light load: 24 % RU
1.5%, 2.2%, 2.6%, 2.8%, 2.9%, 2.9% | | | +| | Low load: 7.5 % RU
2.3%, 3.5%, 4.1%, 4.4%, 4.5%, 4.6% | | | +| Medium load: 42 % RU | Low load: 2 % RU
2.9%, 4.3%, 5.0%, 5.4%, 5.5%, 5.6% | Cat 1
Set 1
8 SSBs for FR1 and ssb-periodicity = 160 | FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | 0.3%, 0.6%, 0.7% | | | +| | Light load: 24 % RU
0.5%, 1.3%, 1.6% | | | +| Medium load: 42 % RU | Low load: 7.5 % RU
1.5%, 3.5%, 4.5% | Cat 2
Set 1
8 SSBs for FR1 and ssb-periodicity = 160 | FTP3 model. For each load, reduced the number of SSB transmissions: 4, 2, 1 | +| | Low load: 2 % RU
3.3%, 7.8%, 10.1% | | | +| | 0.3%, 0.4%, 0.5% | | | +| Medium load: 42 % RU | Light load: 24 % RU
0.4%, 0.6%, 0.7% | Cat 1
Set 3
64 SSBs for FR2 and ssb-periodicity = 160 | FTP3 model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Low load: 7.5 % RU
0.6%, 0.9%, 1.0% | | | +| | Low load: 2 % RU
0.7%, 1.1%, 1.3% | | | +| Medium load: 42 % RU | 0.5%, 0.9%, 1.1%, 1.3%, 1.3%, 1.3% | Cat 1
Set 3
64 SSBs for FR2 and ssb-periodicity = 160 | FTP3 model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Light load: 24 % RU
0.7%, 1.3%, 1.6%, 1.8%, 1.9%, 1.9% | | | + +| | | | | | +|--|----------------------|-----------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| | Low load: 7.5 % RU | 2.6%, 7.1%, 9.3%, 10.4%, 11.0%, 11.2% | Cat 2
Set 3
64 SSBs for FR2 and ssb-periodicity = 160 | FTP3 model.
For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 | +| | Low load: 2 % RU | 6.0%, 16.0%, 21.0%, 23.5%, 24.8%, 25.4% | | | +| | Medium load: 42 % RU | 0.5%, 0.8%, 0.9%, 1.0%, 1.0%, 1.1% | | | +| | Light load: 24 % RU | 0.8%, 1.1%, 1.3%, 1.4%, 1.5%, 1.5% | | | +| | Low load: 7.5 % RU | 1.2%, 1.8%, 2.1%, 2.2%, 2.3%, 2.3% | | | +| | Low load: 2 % RU | 1.5%, 2.2%, 2.6%, 2.8%, 2.8%, 2.9% | | | + +The following show the BS energy savings by technique A-1-3, i.e. configuration/adaptation of longer periodicity of common signals and/or uplink random access opportunities. + +Based on the results with static configurations from 9 sources, it can be observed that longer SSB/SIB1 periodicity can bring BS with significant energy savings in most cases (with gains up to 84.8%), compared to a selected baseline, for both BS Categories, under all reference configurations. When other configurations/settings are the same, the saving gain generally increase as the periodicity becomes larger, and decrease as the traffic load increases or the number of SSBs increases. Particularly, there are two sources providing results with SSB periodicity larger than 160ms which is the maximum value that is currently supported, i.e., being 640ms and 1280ms, and observed that together with longer SIB1/RACH/RO monitoring periodicities, then depending on the traffic load, the BS energy saving gain can be 53.6%~7.1% and 83.6%~3.4%, respectively, compared to a baseline with 20ms SSB periodicity. + +The scheme does not affect the UPT for empty load case. When traffic occurs and load increases, the UPT also significantly decreases. The latency/access delay/UE power consumption increases proportionally as the periodicity of SSB/SIB increases compared to a corresponding baseline. + +Performance of dynamic SSB/SIB1 periodicity adaptation is not provided. + +**Table 6.1.1.2-3: BS energy savings by adapting SSB/SIB1 periodicities** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT/Access delay/latency/UE power consumption, etc. (loss w.r.t. baseline) | Baseline configuration/assumption/Other notable setting | +|----------------|--------------------------------------------------------------------------------------------------------|-------------|--------------------------|----------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| CMCC [23] | SSB periodicity 20ms, SIB repetition period 40ms. | cat.2 | Zero | 13.7% | | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | +| | SSB and SIB1 repetition period 40ms. | | | 17.6% | | | +| | SSB periodicity 20ms, SIB repetition period 40ms. | cat.1 | Zero | 25.7% | | | +| | SSB and SIB1 repetition period 40ms. | | | 28.7% | | | +| vivo [10] [20] | Period adaptation of common signals and channels (ES scheme: 160ms SSB and SIB1, 160ms RACH listening) | Cat1 | Zero | 78.8% | UE power consumption: 0% | Baseline scheme: 20ms SSB and SIB1, 20ms RACH listening | +| | | Cat2 | | 16.6% | UE power consumption: 0% | | +| NOKIA/NSB [12] | SSB/SIB1/RO monitoring period= 160ms | Cat 2 | Zero, Low, Light, Medium | 48.4%, 44.3%, 43.7%, 39.9% | UPT: 0 Mbps, 83 Mbps, 70 Mbps, 55 Mbps | SSB/SIB1/random-access occasion (RO) monitoring periodicity @ 20ms
UEs are initially in RRC_idle state | +| | SSB/SIB1/RO monitoring period= 640ms | | Zero, Low, Light, Medium | 53.6%, 49.0%, 48.8%, 46.1% | UPT: 0 Mbps, 29 Mbps, 27 Mbps, 25 Mbps | | + +| | | | | | | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------|-----------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | SSB/SIB1/RO monitoring period= 1280ms | | Zero, Low, Light, Medium | 83.6%, 51.3%, 51.7%, 50.6% | UPT: 0 Mbps, 11.2 Mbps, 11 Mbps, 10.5 Mbps | | +| Spreadtrum [13] | Prolonging the periodicity of SSB/SIB1/paging:
1) SSB burst periodicity is 160ms, and SIB1 repetition periodicity is 160ms.
2) PF periodicity at gNB side is 160ms (T=1280ms, N=8).
3) gNB can enter light sleep for Cat 1, but can only enter micro sleep for Cat 2. | Cat 1 | Zero | Set 1- Set 3: 23.8%, 19.6%, 16.3% | | 1) SSB burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms.
2) PF periodicity at gNB side is 20ms (T=1280ms, N=64).
3) gNB can enter light sleep for Cat 1, but can only enter micro sleep for Cat 2. | +| | | Cat 2 | | Set 1- Set 3: 9.3%, 8.3%, 9.4% | | | +| | Transmission window of SSB/SIB1/paging:
1) SSB burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms.
2) PF periodicity at gNB side is 20ms (T=1280ms, N=64).
3) gNB can enter light sleep for Cat 1, but can only enter micro sleep for Cat 2. | Cat 1 | | Set 1- Set 3: 23.8%, 19.6%, 16.3% | | 1) The transmission window periodicity is 1280ms, and the transmission window duration is 160ms.
2) SSB burst periodicity is 20ms within the transmission window, and SIB1 repetition periodicity is 20ms within the transmission window.
3) PF periodicity at gNB side is 160ms (T=1280ms, N=8) within the transmission window.
4) gNB can enter light sleep for Cat 1, and can enter both light sleep and micro sleep for Cat 2 (at the tail of the transmission window). | +| | | Cat 2 | | Set 1- Set 3: 51.5%, 47.3%, 20.6% | | | +| Intel [22] | Increasing the common channel/signal periodicity | Cat 1 | Low | 40.1% | UPT: 819.66 Mbps

Avg EE* (baseline): 5.10
Avg EE (ES scheme): 9.17 | Baseline:
SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 160 msec periodicity.

EE* is defined as cell throughput (in Mbps) / average power consumption (in relative power), and averaged from all BS. | +| | | | | 45.0% | UPT: 819.66 Mbps

Avg EE (baseline): 5.10
Avg. EE (ES scheme): 10.60 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 640 msec periodicity | +| | | | | 14.6% | UPT: 611.45Mbps

Avg EE (baseline): 2.66
Avg. EE (ES scheme): 3.31 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 160 msec periodicity | +| | | | | 16.8% | UPT: 611.45Mbps

Avg EE (baseline): 2.66
Avg. EE (ES scheme): 3.46 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 640 msec periodicity | +| | | | Medium | 6.2% | UPT: 457.92Mbps

Avg EE (baseline): 1.50
Avg. EE (ES scheme): 1.63 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 160 msec periodicity | +| | | | | 7.1% | UPT: 457.92Mbps

Avg EE (baseline): 1.50
Avg. EE (ES scheme): 1.65 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 640 msec periodicity | +| | | | | 8.2% | UPT: 819.66Mbps

Avg EE (baseline): 35.82
Avg. EE (ES scheme): 39.23 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 160 msec periodicity | +| | | Cat2 | Low | 10.9% | UPT: 819.66Mbps

Avg EE (baseline): 35.82
Avg. EE (ES scheme): 40.09 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 1280 msec periodicity | +| | | | | 5.1% | UPT: 611.45Mbps

Avg EE (baseline): 20.75
Avg. EE (ES scheme): 22.00 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 160 msec periodicity | +| | | | Light | | | | + +| | | | | | | | +|---------------|-------------------------------------------|------------|--------------------------|----------------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | 5.8% | UPT: 611.45Mbps
Avg. EE (baseline): 20.75
Avg. EE (ES scheme): 22.19 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 1280 msec periodicity | +| | | | Medium | 3.0% | UPT: 457.92Mbps
Avg. EE (baseline): 12.44
Avg. EE (ES scheme): 12.89 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms
ES scheme: SSB/SIB1/PRACH: 160 msec periodicity | +| | | | | 3.4% | UPT: 457.92Mbps
Avg. EE (baseline): 12.44
Avg. EE (ES scheme): 12.96 | Baseline: SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms.
ES scheme: SSB/SIB1/PRACH: 1280 msec periodicity | +| CATT [25] | Adaptation of common signals and channels | Cat 1 | Zero load | 10.2%, 72.7%, 84.8% | | Baseline: 20ms SSB;

ES scheme: SSB: 40ms, 80ms, 160ms for each load | +| | | | Low load | 3.4%, 18.8%, 19.7% | | Baseline: SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms;

ES scheme: SSB: 40ms, 80ms, 160ms for each load | +| | | | Light load | 1.9%, 5.2%, 5.6% | | Baseline: SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms;

ES scheme: SSB: 40ms, 80ms, 160ms for each load | +| | | | Medium load | 1.3%, 2.2%, 2.6% | | Baseline: SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms;

ES scheme: SSB: 40ms, 80ms, 160ms for each load | +| Fujitsu [11] | SSB/SIB1 period= 40ms | Cat2 | Zero, low, light, medium | 17.9%, 13.7%, 11.1%, 8.6% | | Baseline scheme: 20 ms SSB/SIB1 period | +| | SSB/SIB1 period= 80ms | | Zero, low, light, medium | 26.8%, 20.6%, 16.7%, 12.8% | | | +| | SSB/SIB1 period= 160ms | | Zero, low, light, medium | 31.4%, 24.1%, 19.4%, 15.0% | | | +| | SSB/SIB1 period= 40ms | | Zero, low, light, medium | 18.3%, 12.6%, 9.4%, 6.9% | | | +| | SSB/SIB1 period= 80ms | | Zero, low, light, medium | 27.4%, 18.8%, 14.1%, 10.4% | | | +| | SSB/SIB1 period= 160ms | | Zero, low, light, medium | 32.0%, 22.0%, 16.5%, 12.1% | | | +| Ericsson [18] | 40ms SSB+SIB1 | Cat1 | Zero | 0.9% | | Baseline scheme: 20ms SSB + 160ms SIB1 | +| | 80ms SSB+SIB1 | | | 48.5% | | ES: one SSB. Energy calculation: per symbol energy consumption is modeled. | +| | 160ms SSB+SIB1 | | | 72.6% | | | +| | 40ms SSB+SIB1 | | | -6.2% | | Baseline scheme: 20ms SSB + 160ms SIB1 | +| | 80ms SSB+SIB1 | | | 43.8% | | ES: Four SSBs. Energy calculation: per symbol energy consumption is modeled. | +| | 160ms SSB+SIB1 | | | 70.5% | | | +| Qualcomm [17] | Adaptation of Common Signals and Channels | Category 1 | No Load | 13.9% | Access delay/latency: additional 20 ms;

UE power consumption increment: 99% | Note: "SSB period of 40 ms" without any network traffic either in DL or UL. Therefore, there are no statistics for UPT, latency, etc.. | + +The following show the BS energy savings by technique A-1-4, configuration/adaptation of transmission patterns of common signals, i.e. Paging or SSB based on the submitted results. + +Based on the results, + +- One source observed that for BS category 1 and at empty load case, statically adapting paging configuration could provide BS energy savings by 0.2%~6.7% when paging load (resource used for paging) is 0.2%~0.5%, and the gain can be up to 42.3% when paging load is increased up to 3.6%. The gain could also increase as the number of SSB increases. Performance of dynamically adapting paging configurations is not provided. The above energy saving gains were achieved with SSB periodicity of 80ms or 160ms. +- One source observed that having compact SSB (i.e., no time gap between consecutive SSBs) could provide 10.3% network energy saving for BS category 1 and at empty load case in FR2 when SSB periodicity is 20ms. Furthermore, UE power saving can be improved by 4%. + +**Table 6.1.1.2-4: BS energy savings by adapting Paging/SSB transmission patterns** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT/access delay/latency/ UE power consumption (%: loss w.r.t. baseline) | Reference configuration | Baseline configuration /assumption | Other evaluation methodology/assumption details/notable settings | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------|-------------|--------------------------------------------------------------------------|-------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Intel [22] | Enhanced Paging by increasing the number of consecutive POs within a PF by factor of M while reducing PF density by a factor of M. This keeps the total number of POs same within the DRX cycle. | Cat1 | Zero, Paging load 2% | 21.2% | | Set 1 | Paging Parameters: N = T/4; Ns = 4; Enh. Paging†: N = T/4; Ns = 4; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 80 msec periodicity; Number of SSB: 1

Paging load is the average load per simulation run time.

Paging events were randomly generated.

Same as below results. The value of T is larger than 160ms. | +| | | | Zero, Paging load 0.2% | 4.0% | | | Paging Parameters: N = T/16; Ns = 2; Enh. Paging†: N = T/16; Ns = 2; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 80 msec periodicity; Number of SSB: 1 | +| | | | Zero, Paging load 2% | 42.3% | | | Paging Parameters: N = T/4; Ns = 4; Enh. Paging†: N = T/4; Ns = 4; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 160 msec periodicity; Number of SSB: 1; | +| | | | Zero, Paging load 0.2% | 6.7% | | | Paging Parameters: N = T/16; Ns = 2; Enh. Paging†: N = T/16; Ns = 2; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 160 msec periodicity; Number of SSB: 1; | +| | | | Zero, Paging load 3.6% | 18.9% | | | Paging Parameters: N = T/4; Ns = 4; Enh. Paging†: N = T/4; Ns = 4; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 80 msec periodicity; Number of SSB: 4; SSB and SIB1 contained in same slot. 1 SSB per slot along with SIB1 to maximize SSB/SIB1 packing; | +| | | | Zero, Paging load 0.5% | 0.2% | | | Paging Parameters: N = T/16; Ns = 2; Enh. Paging†: N = T/16; Ns = 2; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 80 msec periodicity; Number of SSB: 4; SSB and SIB1 contained in same slot. 1 SSB per slot along with SIB1 to maximize SSB/SIB1 packing; | +| | | | Zero, Paging load 3.6% | 26.4% | | | Paging Parameters: N = T/4; Ns = 4; Enh. Paging†: N = T/4; Ns = 4; M = 4 | No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; SSB/PRACH/SIB1: 160 msec periodicity; Number of SSB: 4; SSB and SIB1 contained in same slot. 1 SSB per slot along with SIB1 to maximize SSB/SIB1 packing; | + +| | | | | | | | | | +|----------------------|-------------------------------------------|------------|------------------------|-------|---------------------------|-----------|-------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Zero, Paging load 0.5% | 0.3 % | | | Paging Parameters:
N = T/16;
Ns = 2;
Enh. Paging†:
N = T/16;
Ns = 2; M = 4 | No C-DRX used for UEs;
CSI feedback based on SRS;
SIB1 BW: 48 PRB;
SSB/PRACH/SIB1: 160 msec periodicity;
Number of SSB: 4;
SSB and SIB1 contained in same slot. 1 SSB per slot along with SIB1 to maximize SSB/SIB1 packing; | +| Qualcomm [17] | Adaptation of Common Signals and Channels | Category 1 | No Load | 10.3% | UE power consumption: -4% | FR2 Set 3 | | "Compact SSB" without any network traffic either in DL or UL. Therefore, there are no statistics for UPT, latency, etc.. | + +The following show the BS energy savings by the technique A-1-5, adapting common signals, i.e. RACH based on the submitted results. + +Based on the results with multiple static RACH occasion configurations, one source observed that adaptation of RACH occasions can achieve BS energy savings by 14.4%~24.9% for BS Category 1 at empty load case under FR1 TDD compared to 10ms RACH periodicity without adaptation. The gain generally increases as PRACH periodicity increases for the same number of SSBs. Performance of dynamic RACH configuration is not provided. + +On UPT/access delay/latency, this scheme increases access delay/latency from 10ms to 70ms, proportional to the increased PRACH periodicity. + +**Table 6.1.1.2-5: BS energy savings by adapting RACH periodicity/occasions** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT/access delay/latency/UE power consumption (w.r.t. baseline) | Reference configuration | Baseline configuration/assumption/notable settings | Other evaluation methodology/assumption details | +|----------------------|-------------------------|-------------|---------------|-------------|-----------------------------------------------------------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Ericsson [18] | PRACH periodicity= 20ms | Cat1 | Zero | 14.4% | Access delay/latency: 10ms increase | Set 1 | Baseline scheme: 20 ms SSB, 40ms SIB1 period, 10ms PRACH periodicity.

Per symbol energy consumption is modeled. | 1 SSB | +| | PRACH periodicity= 40ms | | | 20.9% | Access delay/latency: 30ms increase | | ES scheme: adapting PRACH periodicity for energy efficiency via dynamic PRACH occasions adaptation. Note separate evaluation performed for different PRACH periodicities (i.e. no switching between these settings). | four SSBs | +| | PRACH periodicity= 80ms | | | 22.2% | Access delay/latency: 70ms increase | | | | +| | PRACH periodicity= 20ms | | | 17.3% | Access delay/latency: 10ms increase | | | | +| | PRACH periodicity= 40ms | | | 23.9% | Access delay/latency: 30ms increase | | | | +| | PRACH periodicity= 80ms | | | 24.9% | Access delay/latency: 70ms increase | | | | + +The following show the BS energy savings by technique A-1-6, scheduling of SIB1 by SSB, without PDCCH for SIB1, with repetition period 20ms. + +It is observed by one source that using SSB to schedule SIB1 can obtain 4.8%~14.8% BS energy savings for Set 1 reference configuration for BS Category 1, compared to SSB/SIB1 periodicity of 20ms for both. + +**Table 6.1.1.2-6: BS energy savings by scheduling of SIB1 by SSB** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT/access delay/latency/UE power consumption/Other KPI(s), if any | Reference configuration | Baseline configuration/assumption | Traffic model | Other evaluation methodology/assumption details - Part 1 (other than power modeling aspects) | Other evaluation methodology/assumption details - Part 2 (power modeling aspects) | +|---------|-----------|-------------|---------------|-------------|--------------------------------------------------------------------|-------------------------|-----------------------------------|---------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +|---------|-----------|-------------|---------------|-------------|--------------------------------------------------------------------|-------------------------|-----------------------------------|---------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| + +| | | | | | | | | | | | +|--------------------|-----------------------------------------------------------------------------------------|-------|------|--------|--|-------|-------------------------------------------------------------------------------|--|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CEWIT
[24] [27] | Scheduling of SIB1 by SSB, without PDCCH for SIB1, with repetition period 20ms | Cat.1 | Zero | 4.8% | | Set 1 | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | | numerical analysis |
  • •SIB1: PDCCH: 3 symbols; PDSCH: 12 OFDM symbols including DMRS.
  • •\eta=1, A=0.4.
  • •Time unit for power model is ms. power consumption is calculated in a 20ms long period
| +| | Scheduling of SIB1 by SSB, without PDCCH for SIB1, 4 beams, with repetition period 20ms | Cat.1 | Zero | 11.4 % | | Set 1 | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | | numerical analysis |
  • •SIB1: PDCCH: 3 symbols; PDSCH: 12 OFDM symbols including DMRS.
  • •\eta=1, A=0.4.
  • •Time unit for power model is ms. power consumption is calculated in a 20ms long period
| +| | Scheduling of SIB1 by SSB, without PDCCH for SIB1, 8 beams, with repetition period 20ms | Cat.1 | Zero | 14.8 % | | Set 1 | Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. | | numerical analysis |
  • •SIB1: PDCCH: 3 symbols; PDSCH: 12 OFDM symbols including DMRS.
  • •\eta=1, A=0.4.
  • •Time unit for power model is ms. power consumption is calculated in a 20ms long period
| + +#### 6.1.1.3 Legacy UE and RAN1 specification impacts + +The access latency of legacy UEs may be impacted. + +Specification impact of the technique(s) may include the following. + +For (technique A-1-1) simplified version of SSB, such as only PSS, only PSS and SSS without PBCH, or PSS and SSS with partial PBCH: + +- signaling mechanism to inform the UE about the use of simplified version of SSB, if needed, +- changes to SSB may have impact on SI acquisition, initial access, RRM/RLM measurements, and mobility for legacy UEs and UEs that may not support the technique, +- technique may be enabled for a carrier only when legacy UEs are not using the carrier. + +For (technique A-1-2) skipping of SSB/SIB1 transmission occasion: + +- signaling mechanism to inform the UE about the skipping of SSB/SIB transmission occasions, if needed, +- skipping of common signals and channels, such as SSB and SIB1, may have impact on initial access, RRM/RLM/BM measurements, and performance for legacy UEs and UEs that may not support the technique, +- technique may be enabled for a carrier only when legacy UEs are not using the carrier. + +For (technique A-1-3) configuration/adaptation of longer periodicity of SSB/SIB1 and/or uplink random access opportunities: + +- signaling mechanism to inform the UE about the configuration/adaptation, +- adaption of common signals and channels may have impact on SI acquisition, initial access, RRM/RLM/BM measurements, and performance for legacy UEs and UEs that may not support the technique. + +For (technique A-1-4) the paging enhancement where paging resources are grouped in a compact manner, potential specification impact of the enhancements from paging transmission includes the following: + +- paging reception procedure (RAN2), i.e., identification of POs and PFs for Rel-18 UEs, + +- UEs that do not support the technique are expected to follow legacy paging reception procedure in the cell. + +For (technique A-1-5) dynamically adapting PRACH periodicity and occasions: + +- signaling mechanism to inform the UE about the RACH enhancement resources, +- preparation procedure time for dynamic PRACH adaptation, +- UEs that do not support the technique are expected to use legacy RACH resources in the cell. + +For (technique A-1-6) scheduling of SIB1 without PDCCH: + +- signaling mechanism to inform the UE about the use of SIB1 without PDCCH, if needed, +- changes to PDCCH of SIB1 may have impact on initial access, and system information acquisition for legacy UEs and UEs that may not support the technique, +- the specification impacts may include signalling mechanism to inform the UE about SIB1 transmissions, details of SI acquisition, +- technique may be enabled for a carrier only when legacy UEs are not using the carrier. + +### 6.1.2 Technique A-2 Adaptation of UE specific signals and channels + +#### 6.1.2.1 Description of technique + +The semi-static configured UE specific channels/signals may require the gNB to perform periodic transmission or reception if they are activated. Except for positioning RS (PRS), the configurations for the listed UE-specific signals/channels are BWP-specific. Current specification allows gNB to dynamically activate/deactivate CG-PUSCH/SPS/CSI-RS/CSI report/SRS using DCI (i.e., PDCCH transmission) in UE specific manner. + +Technique A-2 aims to reduce or omit time occasions for the UE specific resources during low activity/non-active periods of the cell. The potential list of UE specific resources includes periodic/semi-static CSI-RS, group-common/UE-specific PDCCH, SPS PDSCH, PUCCH carrying SR, PUCCH/PUSCH carrying CSI reports, PUCCH carrying HARQ-ACK for SPS, CG-PUSCH, SRS, positioning RS (PRS). + +UEs may assist the network with information related to the traffic (e.g., about which resources are necessary or unnecessary) so that the network can optimize its scheduling and achieve more sleep opportunities. + +#### 6.1.2.2 Analysis of NW energy saving and performance impact + +No evaluations of this technique are available. + +#### 6.1.2.3 Legacy UE and RAN1 specification impacts + +Reducing or omitting time occasions for the UE specific resources during low activity/non-active periods of the cell are not expected to impact UEs that do not support the technique. + +Specification impact of the technique may include at least: + +- mechanisms to configure and/or inform UEs about the resource availability, +- UE behavior and procedures when configuration and/or information of the resource availability of cell is provided. + +### 6.1.3 Technique A-3 UE wake up signal (WUS) for gNB + +#### 6.1.3.1 Description of technique + +Technique A-3 enables the UE to send an uplink wake-up signal to request transitioning of a cell from no or reduced transmission/reception activity to active transmission or reception of a channel/signal. The technique can be applied to UEs in one or more RRC states. The UE wake up signal (WUS) by technique A-3-1 may be used to trigger the SSB/SIB + +transmission. It can be used to trigger SSB/SIB1 transmissions with technique A-5. It can also be used to trigger gNB to wake up with technique A-4. + +With the support of WUS, the gNB might be inactive (e.g., where it does not transmit nor receive signal/channel or where it only transmits and receives limited signals). A gNB can transit to become active for transmitting or receiving a channel/signal upon reception of an uplink signal from the UE, referred to as technique A-3-2. + +#### 6.1.3.2 Analysis of NW energy saving and performance impact + +The following capture the results for waking up gNB triggered by UE WUS. + +**Table 6.1.3.2-1: BS energy savings by UE wake up signal (WUS)** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT (%: loss) | Access delay/latency (%: increase) | UE power consumption (%: increase) | Reference configuration | Baseline configuration/assumption | Traffic model | Other evaluation methodology/assumption details/notable settings | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------|-------------|---------------|------------------------------------|------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTK
[19] | UE can wake up gNB | Cat 1 | Low | 49.3 % | 0.00 % | 0.00% | 0.07% | Set 1 | All 21 cells active | VoIP | SLS; DRX (40, 4, 10); 9 out of 21 cells remain active. BS power consumption value is sum of 21 cells. | +| | | Cat 2 | | 51.9 % | 0.00 % | 0.00% | 0.07% | | | | | +| ZTE, Sanechips
[15] | UE WUS is used to wake up a gNB in an energy saving state without DL transmission including SSB/SIB1 | 1 | low | 7.4% | 0.66 % | | | Set 1 | no WUS, cell is in a normal state with {20ms/40ms} SSB/SIB periodicity | FTP3 | UE mobility, slot-level; Pstatic=P3, η(s_f,s_p)=1; time-domain scaling for SSB; time and frequency domain scaling for SIB.

WUS period=20ms/80ms/160ms for each load. | +| | | | | 19.6 % | 2.59 % | | | | | | | +| | | | | 23.8 % | 5.04 % | | | | | | | +| | | | light | 4.9% | 0.11 % | | | | | | | +| | | | | 12.7 % | 0.43 % | | | | | | | +| | | | | 15.5 % | 0.86 % | | | | | | | +| | | 2 | low | 6.2% | 0.66 % | | | | | | | +| | | | | 6.4% | 2.59 % | | | | | | | +| | | | | 6.5% | 5.04 % | | | | | | | +| | | | light | 4.5% | 0.11 % | | | | | | | +| | | | | 4.6% | 0.43 % | | | | | | | +| | | | | 4.7% | 0.86 % | | | | | | | +| vivo
[10] [20] | UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: 160ms SSB, 20ms/80ms/160ms UEWUS) | Cat 1 | 0% | 29.7 % | | | 0.00% | Set 1 | legacy BS, where all cells are always in the normal mode. Normal mode: 20ms SSB and SIB1, 20ms RACH listening | NaN | SLS
No UE DRX
100% detection reliability | +| | | | | 66.6 % | | | 0.00% | | | | | +| | | | | 80.7 % | | | 0.00% | | | | | +| | | | 0.002 % | 27.3 % | 0.8% | 5.68% | 0.00% | | | FTP3, mean packet interval of 10s, packet size of 100bytes | | +| | | | | 60.4 % | 15.5 % | 38.73% | 0.00% | | | | | +| | | | | 72.8 % | 21.7 % | 39.53% | 0.00% | | | | | + +| | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--|---------|----------------------------|--------------------------|----------------------------|-------------------------|--|--|---------------------------------------------------------------| +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: 160ms SSB, 20ms/80ms/160ms UEWUS) | | | 20.55 % | 0.8%
4.3%
6.0% | 3.4%
4.5%
8.6% | 9.70%
20.72%
32.51% | 0.98%
1.46%
1.66% | | | FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes | +| | | | 20.81 % | | | | | | | | +| | | | 20.49 % | | | | | | | | +| | | | 41.79 % | -
2.4% | 2.7%
6.0% | 8.95%
14.55% | 1.13%
1.51% | | | | +| | | | 41.17 % | 0.3%
0.1% | 7.2% | 20.53% | 1.97% | | | | +| | | | 41.35 % | | | | | | | | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: no SSB, 20ms/80ms/160ms UEWUS) | | | 0% | 32.1 %
69.6 %
83.7 % | | | 0.00%
0.00%
0.00% | | | NaN
NaN
NaN | +| | | | 0.002 % | 29.4 %
63.3 %
75.6 % | 0.8%
16.5 %
24.2 % | 4.17%
38.05%
39.53% | 0.00%
0.00%
0.00% | | | | +| | | | 20.71 % | -
0.1%
6.4%
6.6% | 3.9%
7.0%
8.7% | 11.04%
20.31%
29.07% | 1.08%
1.33%
1.65% | | | | +| | | | 20.51 % | | | | | | | | +| | | | 20.66 % | | | | | | | | +| | | | | | | | | | | | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: no SSB, 20ms/80ms/160ms UEWUS) | | | 41.74 % | -
2.2%
0.7%
0.6% | 1.3%
6.6%
7.5% | 10.32%
16.58%
18.21% | 1.13%
1.63%
1.84% | | | FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes | +| | | | 41.91 % | | | | | | | | +| | | | 42.07 % | | | | | | | | +| | | | | | | | | | | | +| | | | | | | | | | | | +| | | | | | | | | | | | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: 160ms SSB, Cat 2) | Cat 2 | | 0% | 19.1 %
19.4 %
19.4 % | | | 0.00%
0.00%
0.00% | | | NaN
NaN
NaN | +| | | | | | | | | | | | +| | | | | | | | | | | | +| | | | | | | | | | | | +| | | | | | | | | | | | +| | | | | | | | | | | | + +| | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------------------------|-------------------------------------|-----------------------------|---------------------------|-------------------------|--|--|--|---------------------------------------------------------------| +| 20ms/80ms/160ms UEWUS) | | | | | | | | | | | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: 160ms SSB, 20ms/80ms/160ms UEWUS) | | 0.002 % | 18.1 %
18.3 %
18.3 % | 0.76 %
5.40 %
11.79 % | 0.58%
8.98%
20.16% | 0.00%
0.00%
0.00% | | | | FTP3, mean packet interval of 10s, packet size of 100bytes | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: 160ms SSB, 20ms/80ms/160ms UEWUS) | | 20.58 %
20.28 %
20.76 % | 0.5%
1.0%
-
0.4% | 0.69 %
1.02 %
2.88 % | 7.93%
9.93%
17.27% | 0.64%
0.56%
0.99% | | | | FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: 160ms SSB, 20ms/80ms/160ms UEWUS) | | 41.46 %
41.22 %
41.04 % | -
2.4%
-
2.1%
-
1.8% | 0.05 %
0.30 %
0.45 % | 5.94%
10.07%
11.62% | 0.99%
1.10%
0.96% | | | | | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: no SSB, 20ms/80ms/160ms UEWUS) | | 0% | 20.3 %
20.6 %
20.6 % | | | 0.00%
0.00%
0.00% | | | | NaN
NaN
NaN | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: no SSB, 20ms/80ms/160ms UEWUS) | | 0.002 % | 19.2 %
19.4 %
19.5 % | 0.85 %
4.17 %
10.53 % | 2.63%
9.83%
20.86% | 0.00%
0.00%
0.00% | | | | FTP3, mean packet interval of 10s, packet size of 100bytes | +| UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: no SSB, 20ms/80ms/160ms UEWUS) | | 20.55 %
20.61 %
21.26 % | 0.5%
0.3%
-
1.0% | 0.36 %
0.61 %
2.21 % | 8.30%
10.14%
17.32% | 0.71%
0.73%
1.11% | | | | FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes | + +| | | | | | | | | | | | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----|---------|------------|--------|--------|-------|-------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | UE WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring (the cells without traffic are switching to ES mode ES mode: no SSB, 20ms/80ms/160ms UEWUS) | | | 42.05 % | - 3.1% | 0.10 % | 7.48% | 1.26% | | | | +| | | | | 41.38 % | - 2.3% | 0.21 % | 9.16% | 0.98% | | | | +| | | | | 41.74 % | - 2.9% | 0.36 % | 10.22% | 1.04% | | | | +| NOKIA/N SB [12] | Wake up of gNB triggered by UE wake up signal (WUS) @ 20ms | Cat 2 | Low | 45.6 % | 13,01 Mbps | | | | Set 1 | SSB/SIB1s/RO monitoring @ 20ms default periodicity UEs are initially in RRC_idle state | UL - IM SLS+Post-processing | +| | Wake up of gNB triggered by UE wake up signal (WUS) @ 160ms | | | 51.9 % | 6,08 Mbps | | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS) @ 640ms | | | 52.5 % | 2,15 Mbps | | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS) @ 1280ms | | | 66.7 % | 1,16 Mbps | | | | | | | +| Samsung [21] | Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicity | Cat 1 | Low | 70.3 % | | 0.00% | | | Set 2 | SR periodicity = 10ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE SLS No UE DRX 100% detection reliability (one shot transmission). slot level, WUS detection power is 90. | +| | | | | 64.0 % | | 0.00% | | | | | | +| | | | | 57.2 % | | 0.00% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @15 ms WUS periodicity | | | 76.4 % | | 0.00% | | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | +| | | | | 69.4 % | | 0.00% | | | | | | +| | | | | 61.8 % | | 0.00% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicity | | | 80.1 % | | 0.00% | | | | SR periodicity = 10ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE SLS No UE DRX 100% detection reliability (one shot transmission). slot level, WUS detection power is 55. | +| | | | | 73.7 % | | 0.00% | | | | | | +| | | | | 66.7 % | | 0.00% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @15 ms WUS periodicity | | | 83.7 % | | 0.00% | | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | +| | | | | 76.5 % | | 0.00% | | | | | | +| | | | | 68.8 % | | 0.00% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicity | | | 92.8 % | | 0.00% | | | | SR periodicity = 10ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE SLS No UE DRX 100% detection reliability (one shot transmission). slot level, WUS detection power is 10. | +| | | | | 86.2 % | | 0.00% | | | | | | +| | | | | 79.0 % | | 0.00% | | | | | | + +| | | | | | | | | | | | | +|--|-----------------------------------------------------------------------------|--|--|--------|--|---------|--|--|-----------------------|--------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| | Wake up of gNB triggered by UE wake up signal (WUS), @15 ms WUS periodicity | | | 93.0 % | | 0.00% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | | +| | | | | 85.7 % | | 0.00% | | | | | | +| | | | | 77.8 % | | 0.00% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicity | | | 45.0 % | | -29.56% | | | SR periodicity = 10ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | SLS
No UE DRX
100% detection reliability (one shot transmission).
slot level, WUS detection power is 90. | +| | | | | 39.2 % | | -28.9% | | | | | | +| | | | | 32.8 % | | -29.41% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicity | | | 39.1 % | | -45.37% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | | +| | | | | 32.6 % | | -45.15% | | | | | | +| | | | | 25.7 % | | -45.51% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicity | | | 67.1 % | | -22.44% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | | +| | | | | 60.2 % | | -22.85% | | | | | | +| | | | | 52.7 % | | -22.79% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicity | | | 64.7 % | | -29.56% | | | SR periodicity = 10ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | SLS
No UE DRX
100% detection reliability (one shot transmission).
slot level, WUS detection power is 55. | +| | | | | 58.5 % | | -28.9% | | | | | | +| | | | | 51.8 % | | -29.41% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicity | | | 60.8 % | | -45.37% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | | +| | | | | 54.1 % | | -45.15% | | | | | | +| | | | | 46.7 % | | -45.51% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicity | | | 78.0 % | | -22.44% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | | +| | | | | 70.9 % | | -22.85% | | | | | | +| | | | | 63.2 % | | -22.79% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicity | | | 90.0 % | | -29.56% | | | SR periodicity = 10ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | SLS
No UE DRX
100% detection reliability (one shot transmission).
slot level, WUS detection power is 10. | +| | | | | 83.4 % | | -28.9% | | | | | | +| | | | | 76.3 % | | -29.41% | | | | | | +| | Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicity | | | 88.9 % | | -45.37% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | | +| | | | | 81.6 % | | -45.15% | | | | | | +| | | | | 73.8 % | | -45.51% | | | | | | + +| | | | | | | | | | | | +|---------------|-----------------------------------------------------------------------------|------------|---------|----------------------------|--|-------------------------------|--|-----------|------------------------------------------------------|--------------------------------------------------------------| +| | Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicity | | | 92.0 %
84.7 %
76.8 % | | -22.44%
-22.85%
-22.79% | | | SR periodicity = 15ms | FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE | +| Qualcomm [17] | Wake up of gNB triggered by UE two symbol wake up signal (WUS) | Category 1 | No Load | 18.7 % | | | | FR2 Set 3 | "light SSB" combined with UL WUS and on demand SIB 1 | | + +For UE WUS triggering SSB/SIB1/RACH for RRC IDLE/INACTIVE/CONNECTED mode by technique A-3-1, based on results from 4 sources, it is observed that, with UE WUS signal triggering a BS of 100% detection assumption, + +- With C-DRX, at low load, one source observed about 50% network energy savings with marginal UE power increment, without UPT loss observed. The scheduling delay when switching to a new gNB is not modelled. +- For the evaluations with assumption of RRC\_IDLE/INACTIVE mode without C-DRX, + - without DL transmission including DL common signals before gNB reception of WUS, with WUS period of 20ms, 80ms and 160ms, at zero or low load, the network energy savings could be 7.4%~32.1% (6.2%~45.6%), 19.6%~69.6% (6.4%~51.9%), 23.8%~ 83.7% (6.5%~52.5%) respectively by using Category 1 (Category 2) BS power model. The savings can increase as the WUS period increases, and decrease as the traffic load increases. When WUS period is 20ms, marginal UPT loss, access delay/latency increment and UE power consumption increment are observed. The UPT loss and access delay/latency increases as WUS periodicity increases, while there is marginal UE power consumption increment. + - With sparse SSB of 160ms periodicity transmitted before gNB reception of WUS, at zero or low load, 27.3%~29.7% (18.1%~19.1%), 60.4%~66.6% (18.3%~19.4%), 72.8%~80.7% (18.3%~19.4%) network energy savings can be achieved with WUS period of 20ms, 80ms and 160ms respectively by using Category 1 (Category 2) BS power model. When WUS period is 20ms, marginal UPT loss, access delay/latency increment and UE power consumption increment are observed. The UPT loss and access delay/latency increases as WUS periodicity increases, while there is marginal UE power consumption increment. +- Note: gNB coordination for WUS reception is assumed. Resource configuration for WUS is not specifically modelled, while one source assumes the configuration of WUS can be obtained from a camping cell. For the case of no DL transmission, gNB synchronization is further assumed. +- Note: For evaluation results from 2 sources, it is assumed that UE achieves timing for the UL WUS transmission from the other cell. For evaluation results from 2 sources, it is assumed that UE achieves synchronization with the gNB targeting for energy saving by utilizing discovery signal from the same cell, and one source assumed the discovery signal contains PSS only and its use is to help the UE to get synchronized and to be able to transmit an uplink triggering signal. The differentiation of multiple gNBs which have detected the WUS is not modelled. +- The detection of WUS is assumed to be ideal. False triggering for detection of targeting gNB is not considered. + +For UE WUS triggering gNB to wake up in case of uplink traffic arrival by technique A-3-2, for RRC\_CONNECTED without C-DRX, and without DL common signals/DL transmission other than PDCCH carrying UL grant, with the assumption of a separate receiver used and 100% detection assumption, at low load, 1 source observed that, + +- With WUS detection power of 10, 55 or, with 90 which has the same active UL power, + - When the WUS periodicity is same as the baseline of SR periodicity, 77.8%~93%, 66.7%~92.8% or 57.2%~76.4% network energy savings could be achieved respectively; + - When the WUS periodicity is smaller than the SR periodicity of the baseline, 76.3%~92%, 46.7%~78% or 25.7%~67.1% network energy savings could be achieved respectively; + - For each case, the gain generally increases as the WUS periodicity increases and decreases as the traffic load increases. The gain could also increase as the gNB detection power decreases. + +- There is latency reduction observed, which could increase as the periodicity of WUS decreases. The gain can be up to 45%. +- The assumption is that gNB needs to wake up to detect SR but can detect WUS during sleep state. gNB is assumed to be in a state such that the main UL receiver is still in deep sleep when detecting wake-up signal and gNB is able to wake up from deep sleep to active in one slot after WUS detection. The WUS receiver is assumed to be active only when detection of WUS signal and becomes 0 power in other time. + +When technique A-3-1 is combined with a light version of SSB and on demand SIB1, one source observed 18.7% network energy savings at low load for FR2, assuming the light version of SSB contains PSS only and its use is to help the UE to get synchronized and to be able to transmit an uplink trigger signal. + +#### 6.1.3.3 Legacy UE and RAN1 specification impacts + +Legacy UEs and UEs that do not support this technique cannot wake up a cell that is inactive. Legacy UEs and UEs that do not support this technique are not provided with expected transmission from the cell, therefore they cannot operate in the cell. + +Specification impact of the technique may include: + +- design of uplink wake-up signal/channel, +- signaling details of wake-up signal/channel and if needed, downlink signal/channel design/procedure for carrying information regarding the wake-up configuration, +- conditions for triggering WUS, +- mechanisms for DL synchronization and UE measurements needed prior to WUS transmission, +- UE's assistance information to aid wake up operations by gNB, +- UE behavior/procedure after transmitting WUS, +- mechanism on how the UE can be informed about cell activity or lack of activity. + +### 6.1.4 Technique A-4 Adaptation of DTX/DRX + +#### 6.1.4.1 Description of technique + +Currently, the gNB can use reduced downlink transmission/uplink reception activity without an explicit cell DTX/DRX pattern with restrictions due to UE DRX configurations and any configured transmission/reception, e.g., common channels/signals. Currently C-DRX is configured per UE. The alignment of the DRX cycles or offsets for different UEs can be done only via RRC. During UE DRX off period, the UE does not expect to monitor PDCCH, but it is allowed to initiate UL transmission according to the configured resources (e.g. using PUCCH, RACH, SR, or CG-PUSCH). Aligning/Omitting of DRX patterns across multiple UE's can be achieved via gNB implementation. + +Technique A-4 aims at providing mechanisms informing UE whether the cell stays inactive. This may include enhancements to UE DRX configuration, e.g. to align/omit DRX cycles or start offsets of DRX, for UEs in connected mode or idle/inactive mode, potentially allowing longer opportunities for cell inactivity. During a cell DTX/DRX, the cell may have no transmission/reception or only keep limited transmission/reception. For example, the cell does not need to transmit or receive some periodic signals/channels, such as common channels/signals or UE specific signals/channels. + +#### 6.1.4.2 Analysis of NW energy saving and performance impact + +The following captures the results for adaptation of UE DTX/DRX. + +**Table 6.1.4.2-1: BS energy savings by adaptation of UE DTX/DRX** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT (%: loss) | Access delay/latency/UE power consumption/Othe | a) Reference configuration | +|---------|-----------|-------------|---------------|-------------|---------------|------------------------------------------------|--------------------------------------| +| | | | | | | | b) Baseline configuration/assumption | + +| r KPI(s), if any:
(%: increase) | | | | | | | c) Traffic model | | | +|---------------------------------------------------------------------|----------------------------------------------------------|-------|---------------------|----------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------| +| d) Other evaluation methodology/assumption details/notable settings | | | | | | | | | | +| MTK
[19] | DRX offset alignment | Cat 1 | Low | 29.8 % | 0.91% | Access delay/latency: 0.92% | Set 1

Random DRX offset (granularity = 5 ms)

VoIP

SLS; DRX (40, 4, 10); DRX offset aligned to 0 | | | +| | | Cat 2 | | 13.7 % | 0.91% | UE power consumption: 2.17% | | | | +| OPPO
[14] | DRX align | Cat 1 | low load(RU -9.3%) | 4.7% | 361.08Mbps (15.5%) | Access delay/latency: 78.03ms(+50%) | Set 1

UE-specific DRX, SSB with 20 RBs for 20 ms periodicity | FTP (0.5MB as packet size, 200ms as mean inter-arrival time) | SLS, C-DRX config: FTP (160,100,8), DRX align | +| | | | low load(RU -0.15%) | 6.7% | 85.91Mbps (8.7%) | Access delay/latency: 143.55ms(+3.83%) | | IM (0.1MB as packet size, 2s as mean inter-arrival time) | SLS, C-DRX config: IM (320,80,10), DRX align | +| | DRX align and dropping SSB outside UE active time | Cat 1 | low load(RU -9.3%) | 14.4 % | 361.08Mbps (15.5%) | Access delay/latency: 78.03ms(+50%) | | FTP (0.5MB as packet size, 200ms as mean inter-arrival time) | SLS, C-DRX config: FTP (160,100,8), DRX align and dropping SSB outside UE active time | +| | | | low load(RU -0.15%) | 70.1 % | 85.91Mbps (8.7%) | Access delay/latency: 143.55ms(+3.83%) | | IM (0.1MB as packet size, 2s as mean inter-arrival time) | SLS, C-DRX config: IM (320,80,10), DRX align and dropping SSB outside UE active time | +| ZTE, Sanechips [15] | DRX alignment | 1 | low | 0.3%
0.9% | 5%
1.30% | unfinished packet ratio=(total number of unfinished packet for baseline-total number of unfinished packet for enhanced)/total number of unfinished packet for baseline: 50%, 54.5% for each BS category | Set 1

UE-specific CDRX

FTP3

CDRX pattern for FTP3

CDRX alignment in a cell | | | +| | | 2 | | 0.2%
0.4% | 5%
1.30% | | | | | +| Spreadtrum [13] | traffic concentration (in a transmission window) | Cat 1 | Low | 37.8 %
34.9 %
30.9 % | | | a) For each BS Category: Set 1, Set 2, Set 3
b)- 1) There are 5% load (UE specific data) in 40 slots every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) Scaling: Sf=0.21 in 2 slots every 20ms, and Sf=0.05 in 38 slots every 20ms
c)-1) The load is concentrated in first 10ms. There are 10% load (UE specific data) in the first 20 slots every 20ms, zero load in the last 20 slots every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) gNB can enter light sleep for Cat 1, but can only enter micro sleep for Cat 2. 3) Scaling: Sf=0.26 in 2 slots every 20ms, and Sf=0.1 in 18 slots every 20ms
d)- 1) 160ms duration in total. 2) SSB burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms. Two SSBs and the corresponding SIB1 share a slot. SSB burst and SIB1 take 40 PRBs. 3) PF periodicity at gNB side is 20ms (T=1280ms, N=64). Paging is transmitted in another slot every PF assuming one PO is effective in each PF. Paging takes 40 PRBs. 4) Scaling: Sa=1, Sp=1, P_static=P3.
Numerical evaluation results. | | | +| | | Cat 2 | | 31.1 %
27.7 %
29.2 % | | | | | | +| | Offload between cells (the offloaded cell is turned off) | Cat 1 | Low | 57.7 %
53.5 %
47.9 % | | | a) For each BS Category: Set 1, Set 2, Set 3
b)-1) Cell #1 and cell #2: There are 5% load (UE specific data) in 40 slots every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) Scaling: Sf=0.21 in 2 slots every 20ms, and Sf=0.05 in 38 slots every 20ms
c)-1) The load in cell #1 is shifted to cell #2.
1.1) Cell #1: There are zero load. There are only SSB burst and | | | + +| | | | | | | | | | | +|------------|-----------------------|-------|-------------|----------------------------|----------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Cat 2 | | 46.5 %
44.3 %
46.6 % | | | |

SIB1 in 2 slots every 20ms. gNB can enter light sleep for Cat 1, but can only enter micro sleep for Cat 2. 1.2) Cell #2: There are 10% load (UE specific data) every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) Scaling: 2.1) Cell #1: Sf=0.16; 2.2) Cell #2: Sf=0.26 in 2 slots every 20ms, and Sf=0.1 in 38 slots every 20ms

d)-1) 160ms duration in total. 2) SSB burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms. Two SSBs and the corresponding SIB1 share a slot. SSB burst and SIB1 take 40 PRBs. 3) PF periodicity at gNB side is 20ms (T=1280ms, N=64). Paging is transmitted in another slot every PF assuming one PO is effective in each PF. Paging takes 40 PRBs. 4) Scaling: Sa=1, Sp=1, P_{static}=P3. Numerical evaluation results.

| | +| Intel [22] | Enhanced C-DRX | Cat1 | Light | 2.8% % | Baseline: 122.3 Mbps
ES: 86.4 Mbps | Avg EE (baseline): 5.20
Avg EE (ES): 4.82 | a)Set1
c) FTP3 |

Baseline DRX Parameters:
DRX Cycle: 80 msec; ON duration 4ms, Inactivity Timer: 40msec
For Enh C-DRX, cycle is 80ms and gNB is active for 20ms.

| | +| | | | Medium | 29.7 % | Baseline: 93.2 Mbps
ES: 29.6 Mbps | Avg EE (baseline): 1.87
Avg EE (ES): 2.33 | d) SLS
CSI feedback based on SRS;
SIB1 BW: 48 PRB;
SSB/PRACH/SIB1 : 160 msec periodicity;
Number of SSB: 1;
Slot-level model
For scaling:
$A = 0.4$ ;
$\eta(s, f, s_p) = 1$ for any sf, sp; |

Baseline DRX Parameters:
DRX Cycle: 160 msec; ON duration 8ms, Inactivity Timer: 100msec
For Enh C-DRX, cycle is 160ms and gNB is active for 80ms

| | +| | | | Low | 2.3% | Baseline: 111.2 Mbps
ES: 186.5 Mbps | Avg EE (baseline): 8.81
Avg EE (ES): 9.37 | |

Baseline DRX Parameters:
DRX Cycle: 160 msec; ON duration 8ms, Inactivity Timer: 100msec
For Enh C-DRX, cycle is 160ms and gNB is active for 40ms

| | +| | | | Light | 2.3% | Baseline: 98.1 Mbps
ES: 66.6 Mbps | Avg EE (baseline): 5.31
Avg EE (ES): 4.66 | |

Baseline DRX Parameters:
DRX Cycle: 160 msec; ON duration 8ms, Inactivity Timer: 100msec
For Enh C-DRX, cycle is 160ms and gNB is active for 40ms

| | +| | | | Light | 2.6% | Baseline: 98.1 Mbps
ES: 164.3 Mbps | Avg EE (baseline): 5.31
Avg EE (ES): 5.31 | |

Baseline DRX Parameters:
DRX Cycle: 160 msec; ON duration 8ms, Inactivity Timer: 100msec
For Enh C-DRX, cycle is 160ms and gNB is active for 80ms

| | +| | | | Medium | 30.9 % | Baseline: 75.0 Mbps
ES: 28.2 Mbps | Avg EE (baseline): 1.97
Avg EE (ES): 2.54 | |

Baseline DRX Parameters:
DRX Cycle: 160 msec; Inactivity Timer: 100msec
For Enh C-DRX, cycle is 160ms and gNB is active for 40ms

| | +| | | | Medium | 4.8% | Baseline: 75.0 Mbps
ES: 116.6 Mbps | Avg EE (baseline): 1.97
Avg EE (ES): 2.04 | |

Baseline DRX Parameters:
DRX Cycle: 160 msec; Inactivity Timer: 100msec
For Enh C-DRX, cycle is 160ms and gNB is active for 80ms

| | +| CATT [25] | Adaptation of DTX/DRX | Cat 1 | Low load | 71.4 % | | | Set1 |

SLs; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);
SSB periodicity 20ms;
CSI-RS/TRS 10ms;

|

FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes

| +| | | | Light load | 62.6 % | | | | |

SLs; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); DTX configuration : gNB starting offset of DTX on locate before UE DRX on duration in order to support UE wakeup; SSB periodicity: 20ms; CSI-RS/TRS periodicity: 10ms.

| +| | | | Medium load | 47.8 % | | | | |

FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes

| + +Based on 6 sources results, semi-static UE C-DRX alignment achieves BS energy savings gain by 0.2%~71.4% depending on the traffic, UE DRX configurations, and the assumed baseline, e.g. random DRX offset per UE, or gNB is always ON to provide service to the UE. At low or light traffic load cases, 4 sources show that the gain can be 14.4%~71.4%, while 3 sources show less than 6.7% gain, depending on whether BS and UE active duration are aligned or not; at medium load case, 2 sources show network energy saving gain can be 4.8%~47.8%. According to one source, dropping SSB outside UE active time can achieve the energy savings by 14.4%~70.1% and it is assumed that the UE + +active durations are aligned and the potential impact on synchronization and UE measurement outside the UE duration is not considered. + +On UPT, one source shows there is marginal negative impact while one source shows it can be up to 15.5%. Also, one source shows that the impact on UPT varies: when the UE DRX cycle is 160ms and gNB active time is 80ms, the UPT is increased while in other configurations, there can be large UPT loss. + +On access delay/latency, one source shows marginal increment while one source shows the increment can be up to 50%. Also, about 50% unfinished packet ratio is observed from one source compared to the baseline without UE C-DRX alignment during the evaluation period. The increments are related to the DRX configuration. + +Additionally, one source shows that at low and medium load, the average EE is increased by up to 28.93% when UE DRX alignment is assumed, whereas for light load case, average EE decreases by up to 12.24% when UE DRX alignment is assumed. + +#### 6.1.4.3 Legacy UE and RAN1 specification impacts + +For the cell DTX/DRX cases, depending on DTX/DRX occasions, legacy UEs and UEs that do not support the technique may not have impact to idle/inactive/connected mode operations. For example, if DTX/DRX are not applied to common signals and channel required for idle/inactive/connected modes or applied in UE specific manner, legacy UEs and UEs that do not support the technique may not be impacted. + +Specification impact of the technique may include: + +- design of cell DTX/DRX pattern/timers/parameters/procedure, if needed, +- configuration and indication of cell DTX/DRX information to UE, if needed and applicable, +- UE behavior and procedures when cell DTX/DRX is in operation and/or when UE DRX is configured, if needed, +- potential channel/signal design and mechanism and uplink procedure (e.g., UE request or assistance feedback) related to cell DTX/DRX, +- enhancements to UE DRX configuration +- enhancements to UE DRX parameter adaptation. + +#### 6.1.4.4 Higher layer procedures + +Cell DTX/DRX is applied to at least UEs in RRC\_CONNECTED state. A periodic Cell DTX/DRX (i.e., active and non-active periods) can be configured by gNB via UE-specific RRC signalling per serving cell. Below examples on Cell DTX/DRX behaviour during non-active periods are assumed to be possible options, and the UE behaviour/impact will be studied: + +- Example 1: gNB is expected to turn off all transmission and reception for data traffic and reference signal during Cell DTX/DRX non-active periods. +- Example 2: gNB is expected to turn off its transmission/reception only for data traffic during Cell DTX/DRX non-active periods (i.e., gNB will still transmit/receive reference signals) +- Example 3: gNB is expected to turn off its dynamic data transmission/reception during Cell DTX/DRX non-active periods (i.e., gNB is expected to still perform transmission/reception in periodic resources, including SPS, CG-PUSCH, SR, RACH, and SRS). +- Example 4: gNB is expected to only transmit reference signals (e.g., CSI-RS for measurement). + +The study focus on UE behavior when at any point in time the cell activates a single DTX/DRX configuration. It is up to NW whether legacy UEs can access cells with Cell DTX/DRX. + +The Cell DTX/DRX mode can be activated/de-activated via dynamic L1/L2 signalling and UE-specific RRC signaling. Both UE specific and common L1/L2 signalling can be considered for activating/deactivating the Cell DTX/DRX mode. + +Cell DTX and Cell DRX modes can be configured and operated separately (e.g., one RRC configuration set for DL and another for UL). Cell DTX/DRX can also be configured and operated together. At least the following parameters can be configured per Cell DTX/DRX configuration: periodicity, start slot/offset, on duration. Details related to UE behaviour + +can be discussed during WI phase. Whether to support multiple Cell DTX/DRX configurations can be discussed later in the WI phase. + +It is beneficial to align UE DRX with Cell DTX and DRX alignment among multiple UEs. The alignment mechanism can be discussed during the WI phase. + +From RAN2 perspective, Cell DTX/DRX is feasible. + +#### 6.1.4.5 Impacts on network interfaces + +The cell DTX/DRX information is considered necessary to be exchanged and coordinated between neighbour gNBs. The gNB can use the received cell DTX/DRX information to determine its own cell DTX/DRX configuration for network energy saving purpose. + +Note: The details of cell DTX/DRX is finally up to RAN1 and RAN2. + +### 6.1.5 Technique A-5 adaptation of SSB/SIB1 including on-demand SSB/SIB1 + +#### 6.1.5.1 Description of technique + +Current specification supports SSB/SIB1-less operation for intra-band CA, where UE retrieves system information from and can perform synchronization based on another intra-band cell that transmits SSB and SIB1. Current specification supports SSB periodicity configuration up to 160 msec. + +For technique A-5-1 for non-CA, the UE may obtain system information from other associated carriers/cells and synchronize from other associated carriers/cells and/or synchronize from signal(s) transmitted on the cell. + +Technique A-5-2 also supports on-demand SSB/SIB1 transmissions and enable longer periods of cell inactivity to achieve network energy saving. SSB/SIB1 transmission at the serving cell can be triggered on-demand, e.g. by the UE. + +#### 6.1.5.2 Analysis of NW energy saving and performance impact + +The following capture the results for adaptation of SSB and/or SIB1, with focus on on-demand operation. + +**Table 6.1.5.2-1: BS energy savings by on-demand SSB and/or SIB1** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT | Access delay/latency/UE power consumption/Other KPI(s), if any | Reference configuration | Baseline configuration/assumption | Traffic model/Other evaluation methodology/assumption details/notable settings | +|---------------|---------------------------------------------|-------------|---------------|-------------|-----|----------------------------------------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CATT [25] | Adaptation of SSB/SIB1 | Cat 1 | Low load | 22.0% | | | set1 | SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms; | FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes.
SLS; Cell OFF: Without normal SSB/SIB/CSI-RS transmission within Cell off duration; On demand SSB transmission is trigger by neighbour cell with 300ms transmission duration and 20ms SSB.
For the case with DRX, DTX configuration: gNB starting offset of DTX on locate before UE DRX on duration in order to support UE wakeup; $A=0.4; \eta(s\_f, s\_p)=1$ . | +| | | | | 43.4% | | | | SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms; DTX configuration: gNB starting offset of DTX on locate before UE DRX on duration in order to support UE wakeup; | | +| Ericsson [18] | 20ms Discovery signal (4 symbols) + no SIB1 | Cat1 | Zero | 2.6% / 5.9% | | | Set 1 | Baseline scheme: 20ms SSB + 160ms SIB1 | one SSB/ four SSBs
Energy calculation: per symbol energy consumption is modeled.
According to Rel-15 specification, SIB1 can be transmitted with variable transmission repetition periodicity within a 160 ms period, including one SIB1 PD SCH transmission every 160ms or even sparser. | + +| | | | | | | | | | | +|---------------|----------------|-------|------------|-----------------------|--|--|-------|--------------------------------------------------------------------------------------------------------------------------------------|--| +| Qualcomm [17] | on-demand SIB1 | Cat 1 | Empty load | 5.8% / 7.7% / 8.6% | | | Set 1 | Baseline: 20ms periodicity for SSB/SIB1/RO, one beam
Enhanced: 20%/10%/5% SIB1 Tx rate, C-WUS with 20ms periodicity | | +| | | | | 32.1% / 36.6% / 38.8% | | | | Baseline: 20ms periodicity for SSB/SIB1/RO, 8 beams
Enhanced: 20%/10%/5% SIB1 Tx rate, C-WUS with 20ms periodicity | | + +One source shows that with a 4-symbol Discover signal (DRS), and without SIB1 transmission and for on-demand SIB1, 2.6% and 5.9% energy savings can be achieved for one SSB and four SSB respectively, at empty load with baseline of 20ms SSB/160ms SIB1 periodicity. + +One source shows on-demand SSB can achieve BS energy savings by 22.0% or 43.4% at low load compared to a baseline of 20ms SSB/SIB1 periodicity, for without or with gNB DTX configuration respectively. + +One source is provided with on-demand SIB1 at empty load with baseline of 20ms SSB/SIB1 periodicity, 5.8%~8.6% BS energy savings can be achieved at SIB1 transmission rate of 20%~5% for one SSB beam, and the gains can increase to 32.1%~38.8% for 8 beams case for a same SIB1 transmission rate range. + +Performance impact of on demand SSB/SIB was not provided. + +#### 6.1.5.3 Legacy UE and RAN1 specification impacts + +For on-demand SSB, if no SSB or simplified SSB is transmitted and normal SSB transmission is triggered upon reception of UE WUS, legacy UEs and UEs that do not support this technique may not be able to operate in this cell. + +- Technique may be enabled for a carrier only when legacy UEs are not using the carrier. + +For on-demand SIB1, if no SIB1 is transmitted and normal SIB1 transmission is triggered upon reception of UE WUS, legacy UEs and UEs that do not support this technique may not be able to operate in this cell. + +- Technique may be enabled for a carrier only when legacy UEs are not using the carrier. + +For technique where UE may obtain system information from other associated carriers/cells, cell without a SSB cannot be used as PCell/PSCell/inter-band SCell for legacy UEs and UEs that do not support this technique. + +For technique where UE may obtain system information from other associated carriers/cells, cell without a SIB1 cannot be used as PCell for legacy UEs and UEs that do not support this technique. + +Specification impact of the technique may include: + +- channel/signal design and behavior and procedures of on-demand SSBs/SIB1 and any related signaling, +- random access related enhancement including procedures and configuration for UEs to access the SSB/SIB1-less carrier/cell, +- mobility support or paging for the cell that does not transmit SSB and/or SIB1, +- design for new signal/channel (if any) and related procedures. + +### 6.1.6 SCell without SSB in inter-band CA (RAN2) + +From RAN2 perspective, the technique is studied from time domain. The description of this technique, analysis of network energy saving and performance impact as well as impact on legacy UE and RAN1 specification, can be found in clause 6.1.5 for Technique A-5-1 and in clause 6.2.1 for Technique B-1-1. + +#### 6.1.6.1 Description of technique + +Refer to clause 6.1.5 for Technique A-5-1 and clause 6.2.1 for Technique B-1-1. + +#### 6.1.6.2 Analysis of NW energy saving and performance impact + +Refer to clause 6.1.5 for Technique A-5-1 and clause 6.2.1 for Technique B-1-1. + +#### 6.1.6.3 Legacy UE and RAN1 specification impacts + +Refer to clause 6.1.5 for Technique A-5-1 and clause 6.2.1 for Technique B-1-1. + +#### 6.1.6.4 Higher layer procedures + +The SCell without SSB in intra-band CA is considered as baseline, i.e., for a serving cell without transmission of SS/PBCH blocks, a UE acquires time and frequency synchronization with the serving cell based on receptions of SS/PBCH blocks on the SpCell or the SCell, of the cell group. + +More detailed discussion on higher layer procedures for RAN2 may be needed in WI phase according to the other WGs input. + +Feasibility of this solution is in RAN1 scope. + +### 6.1.7 NES Cell without SIB/SSB (RAN2) + +From RAN2 perspective, the technique is studied from time domain. The description of this technique, analysis of network energy saving and performance impact as well as impact on legacy UE and RAN1 specification, can be found in clause 6.1.5 for Technique A-5-1 and in clause 6.2.1 for Technique B-1-1. + +#### 6.1.7.1 Description of technique + +Refer to clause 6.1.5 for Technique A-5-1 and clause 6.2.1 for Technique B-1-1. + +#### 6.1.7.2 Analysis of NW energy saving and performance impact + +Refer to clause 6.1.5 for Technique A-5-1 and clause 6.2.1 for Technique B-1-1. + +#### 6.1.7.3 Legacy UE and RAN1 specification impacts + +Refer to clause 6.1.5 for Technique A-5-1 and clause 6.2.1 for Technique B-1-1. + +#### 6.1.7.4 Higher layer procedures + +The concept of non-anchor NES cell without SIB is only applicable in multi-carrier scenario, where the UE is in coverage of an anchor cell and one or multiple non-anchor NES cell(s). + +Anchor cell is a cell where a UE is capable of receiving SSB, system information and paging. + +A non-anchor NES cell without SIB is a cell where the UE cannot receive SIB. + +A non-anchor NES cell without SSB and SIB is a cell where a UE can receive neither SSB nor SIB. + +Depending on the design, the access may occur only via anchor cell or also directly in the non-anchor NES cell. If access directly to a non-anchor NES cell is supported, the SIB transmitted by anchor cell may also include the necessary information to access the non-anchor NES cell. + +How and whether the timing, synchronization and QCL relationship of the non-anchor NES cell without SSB and SIB can be determined via another cell is decided within WI. + +UE camps on an anchor cell, not on a non-anchor NES cell without SIB (or without SSB and SIB). + +Paging on a non-anchor NES cell without SIB or a non-anchor NES cell without SSB and SIB is not supported. + +Feasibility of this solution is in RAN1 scope. + +## 6.2 Techniques in frequency domain + +### 6.2.1 Technique B-1 Multi-carrier energy savings enhancements + +#### 6.2.1.1 Description of technique + +Intra-band SSB-less SCell operation is supported by the current specification. PCell switching is supported by handover command according to current specification. + +Technique B-1-1 for CA supports inter-band CA with SSB-less SCell. No SSB transmission in some inter-band SCell(s). The synchronization is acquired from other cell with SSB transmission or same cell with simplified signal transmission, also in order for fast activation and deactivation of SCell. Enabling of inter-band SSB-less SCell operation that may include mechanism for UE/gNB to trigger normal SSB transmission and/or reference signals, if needed, on a SCell for fast access, where the on-demand uplink triggering signal can be received either at inter-band SSB-less cell or another carrier/cell. RACH transmission opportunity may be supported in SSB-less SCell. + +Technique B-1-2 supports dynamic PCell switching in which a common primary cell may be dynamically indicated for a group of UEs. + +#### 6.2.1.2 Analysis of NW energy saving and performance impact + +The following capture the results by multi-carrier energy savings enhancements. + +**Table 6.2.1.2-1: (a) BS energy savings by multi-carrier enhancements for results submitted to Technique B-1-1 [8]** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | KPI | Baseline configuration/assumption | +|-----------------------|--------------------------------|-------------|------------------|-------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Huawei, HiSilicon [9] | Inter-band SSB-less on SCell | Cat 2 | 0% load(zero) | 14.4% | | 4 SSB beams with 20ms period, 20RB

2 SSB per slot, and 4 symbols for each SSB, when the SSB is transmitted on a carrier | +| | | | 10% load(low) | 9.3% | | | +| | | | 20% load(light) | 7.4% | | | +| | | | 30% load(medium) | 5.7% | | | +| ZTE, Sanechips [15] | SSB-less SCell | 1 | zero load | 97.4% | | SSB20ms for baseline; set 1; | +| | | | | 93.9% | | SSB80ms for baseline; set 1; | +| | | | | 88.4% | | SSB160ms for baseline; set 1; | +| | | | | 83.8% | | SSB20ms for baseline; set 1; | +| | | 2 | zero load | 82.4% | | SSB80ms for baseline; set 1; | +| | | | | 82.1% | | SSB160ms for baseline; set 1; | +| | | | | 97.3% | | SSB20ms for baseline; set 2; | +| | | | | 93.8% | | SSB80ms for baseline; set 2; | +| | | 1 | zero load | 88.3% | | SSB160ms for baseline; set 2; | +| | | | | 82.1% | | SSB20ms for baseline; set 2; | +| | | 2 | zero load | 80.7% | | SSB80ms for baseline; set 2; | +| | | | | 80.4% | | SSB160ms for baseline; set 2; | +| | SSB-less SCell with DL traffic | 1 | low | 58.4% | UPT:801.79, SSB-less UPT : 812.57

UPT gain: 1.3%;

SCell activation delay reduced by 6ms | SSB20ms for baseline; set 1; with DL traffic;

SCell activation delay =12 ms | +| | | | | 35.2% | UPT:804.41, SSB-less UPT : 812.57 | SSB80ms for baseline; set 1; with DL traffic;

SCell activation delay =12 ms | +| | | | | | | | + +| | | | | | | | +|--------------------------------|---|-----|--|-------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| | | | | | UPT gain: 1.0%;
SCell activation delay reduced by 6ms | | +| | | | | 21.2% | UPT:804.54, SSB-less UPT : 812.57
UPT gain: 1.0%
SCell activation delay reduced by 6ms | SSB160ms for baseline; set 1; with DL traffic;
SCell activation delay =12 ms | +| | | | | 15.2% | UPT:801.79, SSB-less UPT : 812.57
UPT gain: 1.3%;
SCell activation delay reduced by 6ms | SSB20ms for baseline; set 1; with DL traffic;
SCell activation delay =12 ms | +| | | | | 7.4% | UPT:804.41, SSB-less UPT : 812.57
UPT gain: 1.0%;
SCell activation delay reduced by 6ms | SSB80ms for baseline; set 1; with DL traffic;
SCell activation delay =12 ms | +| | | | | 6.1% | UPT:804.54, SSB-less UPT : 812.57
UPT gain: 1.0%;
SCell activation delay reduced by 6ms | SSB160ms for baseline; set 1; with DL traffic;
SCell activation delay =12 ms | +| | | | | 72.7% | UPT:115.80, SSB-less UPT : 119.41
UPT gain: 3.1%;
SCell activation delay reduced by 6ms | SSB20ms for baseline; set 2; with DL traffic;
SCell activation delay =12 ms | +| | | | | 51.7% | UPT:118.20, SSB-less UPT : 119.41
UPT gain: 1.0%;
SCell activation delay reduced by 6ms | SSB80ms for baseline; set 2; with DL traffic;
SCell activation delay =12 ms | +| | | | | 34.9% | UPT:118.70, SSB-less UPT : 119.41
UPT gain: 0.6%;
SCell activation delay reduced by 6ms | SSB160ms for baseline; set 2; with DL traffic;
SCell activation delay =12 ms | +| | | | | 24.9% | UPT:115.80, SSB-less UPT : 119.41
UPT gain: 3.1%;
SCell activation delay reduced by 6ms | SSB20ms for baseline; set 2; with DL traffic;
SCell activation delay =12 ms | +| | | | | 16.9% | UPT:118.20, SSB-less UPT : 119.41
UPT gain: 1.0%;
SCell activation delay reduced by 6ms | SSB80ms for baseline; set 2; with DL traffic;
SCell activation delay =12 ms | +| | | | | 15.5% | UPT:118.70, SSB-less UPT : 119.41
UPT gain: 0.6%
SCell activation delay reduced by 6ms | SSB160ms for baseline; set 2; with DL traffic;
SCell activation delay =12 ms | +| | | | | 39.4% | SCell activation delay reduced by 6ms | SSB20ms for baseline; set1; with UL traffic;
SCell activation delay =12 ms | +| SSB-less SCell with UL traffic | 2 | low | | | | | + +| | | | | | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------------------------------------------|-------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | 22.4% | | SSB80ms for baseline; set1; with UL traffic;
SCell activation delay = 12 ms | +| | | | | 18.7% | | SSB160ms for baseline; set1; with UL traffic;
SCell activation delay = 12 ms | +| Vivo
[10] [20] | Inter-band CA with SSB-less carriers/SCell (ES scheme:
CC 1: 20ms SSB and SIB1(with 48 PRB), 20ms RACH listening;
CC 2: neither transmission nor reception) | Cat 1 | 0% | 14.7% | UE power consumption increase: 0% | Baseline scheme:
CC 1: 20ms SSB and SIB1(with 48 PRB), 20ms RACH listening;
CC 2: only 20ms SSB | +| | | Cat 2 | 0% | 5.1% | | | +| Intel
[22] | inter-band SSB-less SCell | Cat1 | Low | 3.0% | UPT: 1639.3 Mbps; Avg EE (baseline): 6.56;
Avg EE (ES): 6.81 | Baseline: CC# 2 (SCell): 160 msec SSB, no SIB1/PRACH,
ES: CC# 2 (SCell): no SSB/SIB1/PRACH, | +| | | Cat1 | Light | 1.0% | UPT: 1222.9 Mbps; Avg EE (baseline): 2.96;
Avg EE (ES): 3.00 | | +| | | Cat1 | Medium | 0.3% | UPT: 915.8 Mbps; Avg EE (baseline): 1.57;
Avg EE (ES): 1.57 | | +| MTK
[19] | SCell_w/o_SIB1 | Cat 1 | Light | 2.3% | UPT loss: 0.00%; Access delay/latency increase: 0%;
UE power consumption increase: 0% | SCell has SSB and SIB1 | +| | | Cat 2 | | 1.1% | | | +| | SCell_w/o_SSB_SIB1 | Cat 1 | | 7.9% | | | +| | | Cat 2 | | 1.3% | | | +| CMCC
[23] | SCell with simplified SSB: SCell with only PSS/SSS, with 20ms periodicity.
PCell with normal SSB, SIB1 and also SIB information for SCell. | Cat.2 | Zero | 5.7% | N/A | Baseline: normal SSB on SCell. PCell with normal SSB, SIB1 and also SIB1 information for SCell. | +| | | Cat.1 | | 10.5% | | | +| Vivo
[10] [20] | SSB/SIB-less carrier operation with assistance of anchor carrier (ES scheme:
CC 1: 20ms SSB and SIB1(with 72 PRB), 20ms RACH listening;
CC 2: only 20ms RACH listening) | Cat 1 | 0% | 14.8% | | Baseline scheme:
CC 1: 20ms SSB and SIB1(with 48 PRB), 20ms RACH listening;
CC 2: 20ms SSB and SIB1(with 48 PRB), 20ms RACH listening | +| | | Cat 2 | 0% | 9.1% | | | +| CATT
[25] | Multi-carrier energy savings enhancements | Cat 1 | Low load | 25.7% | | SLS: (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms; Rel-17 SCell activation/deactivation; | +| | | | Light load | 24.1% | | | +| | | | Medium load | 15.5% | | | +| | | | Low load | 30.3% | | | +| | | | Light load | 29.1% | | | +| | | | Medium load | 20.3% | | | +| Qualcomm
[17] | Dynamic UE-group PCell switching | Cat 1 | Medium (39% RU for 1 CC; 22% RU across 2 CCs) | 37.5% | UPT loss: 14% | Assumption: Number of Ues changes from 25 to 20
Baseline: Keep 2 CCs activated
Enhancement: deactivate 1 CC and keep 1 CC activated | + +##### (b) BS energy savings by multi-carrier enhancements for results submitted to Technique A-5-1 [8] + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT | Access delay/latency/UE power consumption/Other KPI(s), if any | Reference configuration | Baseline configuration/assumption | Traffic model/Other evaluation methodology/assumption details/notable settings | +|---------|-----------|-------------|---------------|-------------|-----|----------------------------------------------------------------|-------------------------|-----------------------------------|--------------------------------------------------------------------------------| +|---------|-----------|-------------|---------------|-------------|-----|----------------------------------------------------------------|-------------------------|-----------------------------------|--------------------------------------------------------------------------------| + +| | | | | | | | | | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------|--------|-----|-----------------------------------------------------------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CMCC [23] | SSB/SIB1-less scheme:
gNB has 2 co-deployed CCs, both of them are available for UE with single carrier operation to access, but only CC1 has normal SSB and SIB1 with default 20ms transmission period. CC2 only has PSS/SSS for synchronization. | cat.2 | Zero | 31.4% | / | CC1 carries SIB1 of CC2, the power consumption of CC1 increases 1.73% for FDM SIB of both CC. | set 1 | Baseline scheme:
gNB has 2 co-deployed CCs, both of them are available for UE with single carrier operation to access, so both CC1 and CC2 has SSB and SIB1 with default 20ms transmission period. As shown in Figure.5 (a). | numerical analysis.

  • SIB1:
    -Baseline: for both CC1 and CC2, PDCCH: 2 symbols, 48RB; PDSCH: 12RBs, 12 OFDM symbols including DMRS.
    -SSB/SIB1-less scheme: no SIB1 on CC2, but CC1 carries SIB1 for CC2, so the TBS will be doubled. The number of PDSCH PRBs is 24 RBs, 12OFDM symbols. PDCCH still occupies 2 OFDM symbols, 48 PRBs.
  • SSB1 and SSB are transmitted in different slots, e.g. value in Table 13-11 is assumed to be 5ms.
  • \eta=1, A=0.4.
  • Time unit for power model is slot.
  • power consumption is calculated in a 40ms long period
| +| | | cat.1 | | 56.5% | / | CC1 carries SIB1 of CC2, the power consumption of CC1 increases 1.41% for FDM SIB of both CC. | | | | +| Huawei, HiSilicon [9] | SIB-less on ES CC | Cat 2 | 0% load(zero) | 33.6% | N/A | N/A | Set 2 | 4 SIB1 with 20ms period,20RB | FTP3 IM.

NO C-DRX; Subband based CSI-feedback in every 5 slots.

slot level with time-domain scaling; $A=0.4$ ; $\eta=1$ , $0.76(s\_f^s\_p < 0.5)$ | +| | | | 10% load(low) | 26.2% | N/A | N/A | | | | +| | | | 20% load(light) | 19.0% | N/A | N/A | | | | +| | | | 30% load(medium) | 16.0% | N/A | N/A | | | | +| | dual SIB on Anchor CC | | 0% load(zero) | -7.5% | N/A | N/A | | 4 SIB1 with 20ms period,20RB | | +| | | | 10% load(low) | -6.7% | N/A | N/A | | | | +| | | | 20% load(light) | -6.1% | N/A | N/A | | | | +| | | | 30% load(medium) | -5.5% | N/A | N/A | | | | +| | SIB-less on ES CC | | 0% load(zero) | 20.2% | N/A | N/A | | 4 SIB1 with 40ms period,20RB | | +| | | | | 11.2% | N/A | N/A | | 4 SIB1 with 80ms period,20RB | | +| | | | | 5.9% | N/A | N/A | | 4 SIB1 with 160ms period,20RB | | +| | | | 10% load(low) | 15.7% | N/A | N/A | | 4 SIB1 with 40ms period,20RB | | +| | | | | 9.3% | N/A | N/A | | 4 SIB1 with 80ms period,20RB | | +| | | | | 4.0% | N/A | N/A | | 4 SIB1 with 160ms period,20RB | | +| ZTE, Sanechips [15] | (SSB and SIB)-less cell | 1 | zero | 97.9% | | | Set 1 | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; Enhanced: (SSB+SIB)-less for non-anchor cell | FTP3 for Set 1. IM for Set 2.

slot-level; $P_{static}=P_3$ , $\eta(s\_f^s\_p)=1$ ;

time-domain scaling for SSB;

time and frequency domain scaling for SIB.

For the multiplexing pattern of two SIBs in the anchor cell (when applicable), TDM is considered in the evaluations. | +| | | | | 95.4% | | | | | | +| | | | | 91.1% | | | | | | +| | | | | | | | | | | +| | | | low | 64.3% | | | | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; Enhanced: SIB1-less for non-anchor cell | | +| | | | | 43.6% | | | | | | +| | | | | 28.0% | | | | | | +| | | | | | | | | | | +| | SIB-less cell | | zero | 19.3% | | | | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; Enhanced: SIB1-less for non-anchor cell | | +| | | | | 24.6% | | | | | | +| | | | | 23.5% | | | | | | +| | | | low | 15.5% | | | | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; Enhanced: SIB1-less for non-anchor cell | | +| | | | | 13.6% | | | | | | +| | | | | 8.8% | | | | | | +| | anchor cell with dual SIB transmission | | zero | -14.1% | | energy increase for anchor cell with SIB1 transmission for SIB1-less cell | | | | +| | | | | -18.9% | | | | | | +| | | | | -18.1% | | | | | | + +| | | | | | | | | | | | | | +|--|----------------------------------------|--|------|----------------------------|--|---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| +| | (SSB and SIB)-less cell | | low | -11.6%
-10.5%
-6.8% | | | Set 2 | anchor cell;
Enhanced: (SSB+SIB1)-less for non-anchor cell, anchor cell with SIB1 transmission for SIB1-less cell | | | | | +| | | | zero | 98.4%
96.2%
92.6% | | | | Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: (SSB+SIB1)-less for non-anchor cell | | | | | +| | | | low | 80.3%
59.4%
42.4% | | | | | | | | | +| | | | zero | 40.7%
38.4%
37.0% | | | | Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: SIB1-less for non-anchor cell | | | | | +| | | | low | 28.0%
16.0%
11.5% | | | | | | | | | +| | | | zero | -17.6%
-12.4%
-12.0% | | | | Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: (SSB+SIB1)-less for non-anchor cell, anchor cell with SIB1 transmission for SIB1-less cell | | | | | +| | SIB-less cell | | low | -17.8%
-10.8%
-7.7% | | | | | | | | | +| | | | zero | 85.8%
83.6%
82.8% | | | Set 1 | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: (SSB+SIB1)-less for non-anchor cell | | | | | +| | | | low | 24.5%
13.4%
9.4% | | | | | | | | | +| | | | zero | 12.1%
7.0%
3.7% | | | | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: SIB1-less for non-anchor cell | | | | | +| | | | low | 10.8%
6.2%
3.3% | | | | | | | | | +| | anchor cell with dual SIB transmission | | zero | -8.0%
-4.6%
-2.4% | | energy increase for anchor cell with SIB1 transmission for SIB1-less cell | | Baseline: SSB+SIB: {20ms+40ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: (SSB+SIB1)-less for non-anchor cell, anchor cell with SIB1 transmission for SIB1-less cell | | | | | +| | | | low | -7.5%
-4.3%
-2.3% | | | | | | | | | +| | (SSB and SIB)-less cell | | zero | 87.5%
82.6%
81.4% | | Set 2 | Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: (SSB+SIB1)-less for non-anchor cell | | | | | | +| | | | low | 42.9%
23.6%
19.1% | | | | | | | | | +| | | | zero | 28.2%
9.8%
5.3% | | | Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell;
Enhanced: SIB1-less for non-anchor cell | | | | | | +| | | | low | 23.9%
8.0%
4.3% | | | | | | | | | + +| | | | | | | | | | | +|-----------------------|----------------------------------------|------|--------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| | anchor cell with dual SIB transmission | | zero | -14.1%
-4.9%
-2.6% | | energy increase for anchor cell with SIB1 transmission for SIB1-less cell | | Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; Enhanced: (SSB+SIB1)-less for non-anchor cell, anchor cell with SIB1 transmission for SIB1-less cell | | +| | | | low | -13.8%
-4.6%
-2.5% | | | | | | +| NOKIA/NSB [12] | SSB-less at 20 ms period of RO | CAT2 | Unloaded/Low/Light/Medium | 27.5%
26.1%
26.0%
22.7% | /
135 Mbps
105 Mbps
74 Mbps | | SET 1 | Intra-band/collocated cells with non-CA case, consisting of:
* Coverage cell with 20 ms periodicity of SSB/SIB1 Tx and RO monitoring
* Capacity cell with 20 ms periodicity of SSB/SIB1 Tx and RO monitoring
UEs initially in RRC Idle state. | DL-FTP3, SLS+Post-processing | +| | SSB-less at 160 ms period of RO | | Unloaded/Low/Light/Medium | 51.8%
48.2%
47.3%
43.2% | /
85 Mbps
72 Mbps
56 Mbps | | | | | +| | SIB1-less at 20 ms period of RO | | Unloaded/Low/Light/Medium | 43.1%
40.5%
40.1%
36.5% | /
132 Mbps
104 Mbps
73 Mbps | | | | | +| | SIB1-less at 160 ms period of RO | | Unloaded/Low/Light/Medium | 53.8%
51.2%
47.3%
43.2% | /
84 Mbps
72 Mbps
56 Mbps | | | | | +| | SSB&SIB1-less at 20 ms period of RO | | Unloaded/Low/Light/Medium | 52.7%
50.6%
52.7%
44.4% | /
135 Mbps
105 Mbps
74 Mbps | | | | | +| | SSB&SIB1-less at 160 ms period of RO | | Unloaded/Low/Light/Medium | 55.1%
53.1%
54.9%
46.8% | /
85 Mbps
72 Mbps
56 Mbps | | | | | +| Fujitsu [11] | SSB&SIB-less | Cat2 | Zero
low
light
medium | 34.5%
27.0%
21.7%
16.7% | | | Set 1 | Baseline scheme: 20 ms SSB/SIB1 period | BS goes into micro-sleep on symbolic w/o TX/RX simplified SSB which contains SSS and PSS is transmitted with periodicity of 160 ms No UE DRX. A=0.4, η=1 | +| | | | Zero
low
light
medium | 36.0%
24.7%
18.4%
13.5% | | | Set 2 | | | + +Observation includes the results for techniques that are also evaluated under technique A-5 for non-CA. The following is observed. + +In general, for SSB and/or SIB saved from one carrier of two carriers, 8 resources observed BS energy savings gain, by 5.1%~98.4% for empty load, 3.0%~58.4% for low load, and 1.0%~7.9% for light load, 0.3%~5.7% for medium load. When traffic load is low, network may turn off SCell for energy saving. The results are for FR1 only. + +With one of two carriers having simplified SSB and no SIB1, one source shows BS energy saving gain can be achieved by 31.4%~56.5% compared with a baseline of both carriers having SSB and SIB1 periodicity of 20ms; the same source also shows that with CA configured where SIB1 is already carried by PCell, compared with normal SSB on SCell, the gain of simplified SSB on SCell can be 5.7%~10.5%. + +With SIB-less only from one of two carriers and SSB is still transmitted, + +- one source shows that 33.6%~16.0% BS energy saving gain can be achieved compared with a carrier has 20ms SIB1 periodicity and both SSB and SIB1 are transmitted, and the gain decreases as the traffic load increases. Meanwhile, the SIB1 carried on another carrier increase the energy of that carrier by 7.5%~5.5%, resulting a total saving across two carriers by 26.1%~10.5%. The gain decreases to 4.0% when the baseline SIB1 periodicity increases to 160ms; +- one source shows BS energy saving gain can be 3.3%~40.7% compared with baseline of SSB+SIB periodicity of {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; meanwhile, the SIB1 carried on another carrier increase the energy of that carrier by 2.3%~17.8%, resulting a total saving across two carriers by 1%~22.9%; +- one source shows at different loads, compared to baseline of 20ms SSB/SIB1 periodicity, that BS energy savings can be achieved by 53.8%~36.5% with RO periodicity of 20ms and 160ms; +- also one source shows less than 2.3% BS energy savings when compared with a baseline of SCell having SIB1. + +With SSB-less only from one of two carriers, in which case the SIB is already saved from SCell, with assumption that UE is able to acquire sync from a carrier of another band, + +- for non-CA at different loads, compared to a baseline of 20ms SSB/SIB1 periodicity, one source shows BS energy savings by 27.5%~22.7% and 51.8%~43.2% when the RO periodicity is 20ms and 160ms respectively; +- for CA, two sources show that BS energy savings can be 5.1%~14.7% at different loads, compared to a baseline of 20ms SSB periodicity; +- for CA, one source shows, BS energy saving gain can be 80.4%~97.4% at empty load, 6.1%~72.7% at low load for DL traffic, or 18.7%~39.4% at low load for UL traffic compared with baseline of SSB periodicity of {20ms, 80ms, 160ms}. The BS energy saving gain from SSB-less cell with UL traffic is 12.6%~24.2% larger than SSB-less cell with DL traffic for BS category 2. +- for CA, one source also shows that when the baseline SCell SSB periodicity is 160ms, only 0.3%~3% BS energy savings can be achieved, and one another shows BS energy savings by less than 7.9% if compared with SCell having SIB1; +- UE measurement is based on SSB(s) transmitted in the other carrier of the two carriers. + +With both SSB-less and SIB1-less from one of two carriers for non-CA operation, with assumption that UE is able to acquire sync from a carrier from another band, + +- compared to baseline of 20ms SSB/SIB1 periodicity on both carriers, one source shows BS energy savings by 55.1%~44.4% with RO periodicity of 20ms~160ms at different loads, and one source shows 9.1%~14.8% energy savings at empty load if an anchor carrier carries additional SIB1 for another carrier; +- at different loads, compared to baseline of 20ms SSB/SIB1 periodicity, one source shows BS energy savings by 36.0%~13.5% when combined with simplified SSB (i.e. PSS and SSS only); +- one source shows that with baseline of SSB+SIB periodicity of {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell, BS energy savings can be 9.4%~98.4% if an anchor carrier carries the SSB and SIB1 for another carrier depending on the traffic load. Meanwhile, the SIB1 carried on another carrier increase the energy of that carrier by 2.3%~17.8%, resulting a total saving across two carriers by 7.1%~80.6%. +- Comparison with CA is not provided. +- UE measurement is not considered. + +For results where SSB is not transmitted in SCell, performance impact(s) due to lack of AGC and cell measurement results before SCell access and activation is not provided. + +For results where SSB is not transmitted in neighbour cell, mobility performance impact(s) due to SSB-less operation in neighbour cell(s) is not provided. + +In results for SSB and/or SIB saved from one carrier of two carriers, the UPT is not negatively impacted while one source shows slightly increased UPT. One source shows that the SCell activation delay can also be reduced to 6ms from the baseline. + +No negative impact observed on UE power consumption for the above schemes. + +Additionally, SSB-less SCell for CA can slightly improve the average EE, as observed by one source. + +One source showed that UE-group PCell switching together with SCell dormancy could provide network energy saving by up to 37.5% for two-CC CA scenario with FR1 Set 1. However, UPT degrades by 14% if one SCell goes to dormant state. + +#### 6.2.1.3 Legacy UE and RAN1 specification impacts + +Legacy UEs or UEs that do not support this feature may not be able to operate inter-band CA with SSB-less SCells. A carrier without SSB cannot be operated as a PCell/PSCell for legacy UEs. The carrier cannot be operated as an SCell for legacy UEs if another intra-band carrier with SSB is not present. At least the feasibility and/or potential requirements of acquiring synchronization/measurements (including AGC aspects) from other cell with SSB transmission in inter-band CA needs study. + +For SSB-less inter-band CA, specification impact of the technique may include: + +- RACH procedures in SSB-less SCell for inter-band CA, +- enhancement on SCell activation procedure, +- enhancements on SCell dormancy operation, +- design for new simplified signal/channel (if supported) and related procedures. + +For UE-group PCell switching, specification impact may include: + +- mechanism to signal PCell switching, +- UE behavior based on indicated signalling. + +### 6.2.2 Technique B-2 Adaptation of bandwidth part of UE(s) within a carrier + +#### 6.2.2.1 Description of technique + +In Rel-17, UE-specific BWP configuration and switching is supported. For SPS PDSCH reception, type-2 CG PUSCH transmission, and SP-CSI reporting on PUSCH, once BWP is switched, they should be reactivated by activation DCI. + +Technique B-2 supports enhancements to enable UE group-common or cell-specific BWP configuration and/or switching. Also supports enhancements to enable SPS PDSCH reception/Type-2 CG PUSCH transmission/SP-CSI reporting on PUSCH without reactivation after the BWP switching. + +#### 6.2.2.2 Analysis of NW energy saving and performance impact + +The following capture the results for semi-statically configured bandwidth part of UEs within a carrier. The evaluation is performed with different traffic, e.g. medium traffic to light traffic for Set 1, and low traffic to very low traffic for Set 3, and the reduced BW of 80 MHz is applied as NES mode compared with baseline BW of 100 MHz. + +**Table 6.2.2.2-1: BS energy savings by BWP adaptation within carrier** + +| Company | BS Category | Load scenario | ES gain (%) | KPI (%: loss w.r.t. baseline) | Reference configuration | Baseline configuration/assumption | +|-----------------|-------------|------------------------------------------------------------|-------------|---------------------------------------------------------------------|-------------------------|-----------------------------------| +| Samsung
[21] | Cat 1 | Baseline traffic: 42.8 % RU
Reduced traffic: 28.47 % RU | 38.2% | UPT: 6.05%; Packet latency: 6.44%; Scheduling latency: No increase | Set1 | Baseline: full 100MHz with 55 dBm | +| | Cat 2 | | 27.8% | | | NES mode: 80 MHz with 54 dBm | +| | Cat 1 | Baseline traffic: 7.5 % RU
Reduced traffic: 2.75 % RU | 52.2% | UPT: 14.67%; Packet latency: 17.2%; Scheduling latency: No increase | Set3 | Baseline: full 100MHz with 49 dBm | +| | Cat 2 | | 17.6% | | | NES mode: 80 MHz with 48 dBm | +| | Cat 1 | Baseline traffic: 32.1 %
Reduced traffic: 25.7 % | 17.4% | UPT: 28.24%; Packet latency: 39.4%; Scheduling latency: No increase | Set3 | Baseline: full 100MHz with 49 dBm | +| | Cat 2 | | 17.8% | | | NES mode: 80 MHz with 48 dBm | + +One source observed BS energy savings by 17.4%~52.2% at the expense of UPT loss by 28.4%~14.47%, and packet latency increases by 6.44%~39.4% when traffic is reduced compared to corresponding baseline. BWP switching delay is not modelled. + +On scheduling latency, no negative impact is observed from the same source. + +#### 6.2.2.3 Legacy UE and RAN1 specification impacts + +Legacy UEs and UEs that do not support the technique are not able to change the BWP using the enhanced signaling mechanisms. + +Specification impact of the technique may include signaling and procedure to support UE group-common or cell-specific BWP configuration and/or switching of BWP. + +### 6.2.3 Technique B-3 Adaptation of bandwidth of UE(s) within a BWP + +#### 6.2.3.1 Description of technique + +Currently, a bandwidth of a BWP is semi-statically configured, and the bandwidth of the given BWP cannot be dynamically changed. The current BWP framework allows the UEs to be configured with a default BWP and switching to a default BWP based on timer. Reduction of the frequency resources within a BWP can be achieved via configuration and scheduling at the gNB. + +Technique B-3 supports enhancements to enable group-common signaling to adapt the bandwidth of active BWP and continue operating in same BWP. Some frequency resources within the active BWP may be deactivated. + +#### 6.2.3.2 Analysis of NW energy saving and performance impact + +The following captures the results for dynamic / (semi)-static adaptation of bandwidth of active BWP. + +**Table 6.2.3.2-1: BS energy savings by BW adaptation within BWP** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | KPI | Baseline configuration/assumption | +|------------|------------------------------------------------------------------------------|-------------|-------------------|-------------|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| OPPO [14] | adaptation of bandwidth of active BWP of UEs | Cat 1 | low load(RU-10%) | 1.4% | UPT: 554.74Mbps(-46.8%); Access delay/latency: 9.35ms(+86.3%) | system BW of 100MHz, 64T: (M, N, P, Mg, Ng, MP, NP,) = (8, 8, 2, 1, 1, 4, 8) | +| | | | low load(RU-0.2%) | 1.3% | UPT: 513.43Mbps(-52%); Access delay/latency: 1.78ms(+48.3%) | | +| Intel [22] | intra-carrier BWP adaptation | | Low | -20.6% | UPT: Baseline (819.7Mbps), ES (346.8 Mbps); Avg EE (baseline): 5.10; Avg EE (ES): 1.87 | Baseline: Full BW ES: 50% BW | +| | | | | -75.4% | UPT: Baseline (819.7Mbps), ES (99.4 Mbps); Avg EE (baseline): 5.10; Avg EE (ES): 0.54 | Baseline: Full BW ES: 25% BW | +| | | | Light | -45.9% | UPT: Baseline (611.5Mbps), ES (155.2Mbps); Avg EE (baseline): 2.66; Avg EE (ES): 0.69 | Baseline: Full BW ES: 50% BW | +| | | | | -61.8% | UPT: Baseline (611.5Mbps), ES (25.7Mbps); Avg EE (baseline): 2.66; Avg EE (ES): 0.26 | Baseline: Full BW ES: 25% BW | +| | | | Medium | -27.6% | UPT: Baseline (457.9Mbps), ES (50.5Mbps); Avg EE (baseline): 1.50; Avg EE (ES): 0.44 | Baseline: Full BW ES: 50% BW | +| | | | | -13.5% | UPT: Baseline (457.9Mbps), ES (12.3Mbps); Avg EE (baseline): 1.50; Avg EE (ES): 0.44 | Baseline: Full BW ES: 25% BW | +| CEWIT [31] | Dynamic adaptation of bandwidth of active BWP of UEs with dynamic indication | Cat 1 | Medium | 1.75% | | Baseline: Full BW of 100MHz, 32 ports ES: 50% BW | + +3 sources show different observations. + +One source shows small BW energy saving gain by 1.3%/1.4% at the expense of about 50% UPT loss and increased access delay/latency by 48.3%/86.3%. One source shows BW energy saving gain of 1.75%. One source shows BS power consumption increases with BWP size reduction in a carrier and negative energy saving gain in the range of -13.5%~ -75.4% is observed, together with significantly reduced UPT, and additionally reduced average EE. + +#### 6.2.3.3 Legacy UE and RAN1 specification impacts + +Specification impact of the technique may include behaviour, procedure, and signalling related to enabling group-common adaptation of the bandwidth of active BWP. + +## 6.3 Techniques in spatial domain + +### 6.3.1 Technique C-1 Adaptation of spatial elements + +#### 6.3.1.1 Description of technique + +According to legacy MIMO procedures, the adaptation of spatial elements can be achieved by RRC (re-)configurations updating, such as CSI-RS (re-)configurations, in a semi-static manner. Moreover, the current framework allows UE to be configured with multiple CSI-RS resources, where these CSI-RS configurations may be with respect to different numbers of spatial antenna ports or antenna elements. With CSI reports respect to different number of spatial elements available, gNB is able to dynamically adjust the number of spatial elements for PDSCH transmission in current specification. CSI-RS and CSI reporting configurations are BWP-specific, and BWP adaptation framework can be utilized for the adaptation for a UE capable of multiple BWPs and dynamic BWP switching. + +Indication for potential enhancements related to spatial element adaptation may help the UEs to adapt the already configured CSI-RS configuration such as dynamic/semi-persistent ON-OFF of CSI-RS or to reconfigure the CSI-RS configuration, with respect to adapted number of spatial elements/ports. + +Technique C-1 aims to enhance dynamically adaptation of spatial elements such as the number of active transceiver chains or the number of active antenna panels at gNB in transmitting and/or receiving channels and signals. + +#### 6.3.1.2 Analysis of NW energy saving and performance impact + +The following captures the results for (dynamic) adaptation of spatial elements. + +**Table 6.3.1.2-1: BS energy savings by adaptation of spatial elements** + +| Company | ES scheme | BS Category & Reference configuration | Load scenario | ES gain (%) | UPT/latency/UE power/ Other KPIs | Baseline configuration/assumption | Evaluation methodology/assumption details/traffic model | +|-------------|-----------|---------------------------------------|---------------|-------------|--------------------------------------------------------------------------|-----------------------------------|---------------------------------------------------------| +| MTK
[19] | #TxRU_32 | Cat 1, Set 1 | Light | 15.8% | UPT loss:4.54%;
latency increase:4.76%;
UE power increase:3.48% | BS #TxRU 64 | SLS; DRX (160, 8, 100);
FTP3 traffic | +| | | Cat 2, Set 1 | | 15.8% | UPT loss:4.54%;
latency increase:4.76%;
UE power increase:3.48% | | | +| | #TxRU_16 | Cat 1, Set 1 | | 19.2% | UPT loss:16.92%;
latency increase:20.36%;
UE power increase:14.70% | | | +| | | Cat 2, Set 1 | | 22.1% | UPT loss:16.92%; | | | + +| | | | | | | | | +|---------------------|-----------------------------------------|--------------|------------------|-------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | latency increase:20.36%;
UE power increase:14.70% | | | +| | #TxRU_8 | Cat 1, Set 1 | | 22.1% | UPT loss:47.48%;
latency increase:90.42%;
UE power increase:47.94% | | | +| | | Cat 2, Set 1 | | 24.9% | UPT loss:47.48%;
latency increase:90.42%;
UE power increase:47.94% | | | +| | #TxRU_32 | Cat 1, Set 1 | Medium | 25.3% | UPT loss:6.39%;
latency increase:6.83%;
UE power increase:4.20% | | | +| | | Cat 2, Set 1 | | 26.6% | UPT loss:6.39%;
latency increase:6.83%;
UE power increase:4.20% | | | +| | #TxRU_16 | Cat 1, Set 1 | | 31.4% | UPT loss:44.78%;
latency increase:81.08%;
UE power increase:32.85% | | | +| | | Cat 2, Set 1 | | 36.7% | UPT loss:44.78%;
latency increase:81.08%;
UE power increase:32.85% | | | +| | #TxRU_8 | Cat 1, Set 1 | | 36.0% | UPT loss:87.08%;
latency increase:647.07%;
UE power increase:79.99% | | | +| | | Cat 2, Set 1 | | 45.2% | UPT loss:87.08%;
latency increase:647.07%;
UE power increase:79.99% | | | +| | #TxRU_32_PDSCH_PowOffset_-3dB | Cat 1, Set 1 | Light | 18.8% | UPT loss:9.06%;
latency increase:9.96%;
UE power increase:7.62% | BS #TxRU 64; PDSCH power offset 0 dB | SLS; DRX (160, 8, 100);
FTP3 traffic model;
Single value $\eta$ (=1) | +| | | Cat 2, Set 1 | | 19.7% | UPT loss:9.06%;
latency increase:9.96%;
UE power increase:7.62% | | | +| OPPO
[14] | Dynamic adaptation of spatial elements. | Cat 1, Set 1 | low load(RU-10%) | 22.1% | UPT: 550Mbps (47.2% loss);
latency: 12.41ms (+147%) | system BW of 100MHz, 64T: (M, N, P, Mg, Ng, MP, NP s ) = (8, 8, 2, 1, 1, 4, 8) | SLS, 8T: (M, N, P, Mg, Ng, MP, NP s ) = (4, 2, 2, 1, 1, 2, 2) is used for evaluation;
FTP3 traffic model;
A = 0.4 and $\eta$ =1 | + +| | | | | | | | | +|----------------------|-----------------------------------------|--------------|---------------------|-------|-----------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | low load(RU-0.2%) | 13.7% | UPT: 782.56Mbps (21.2% loss);
latency: 1.79ms(+49.1% ) | | SLS, 8T: (M, N, P, Mg, Ng, MP, NP,) = (4, 2, 2, 1, 1, 2, 2) is used for ES evaluation;

FTP3 IM traffic model;

A = 0.4 and $\eta=1$ | +| Huawei,HiSilicon [9] | Dynamic TRX adaption with Multiple CSIs | Cat 2, Set 1 | 10% load(low) | 7.7% | 0% UPT loss | Dynamic TRX adaption with Single 64T CSI; | NO C-DRX;

Subband based CSI-feedback in every 5 slots;

FTP3 IM traffic model;

A=0.4; $\eta=1, 0.76$ | +| | | | | 4.0% | 5% UPT loss | | | +| | | | | 3.4% | 10% UPT loss | | | +| | | | 30% load(medium) | 13.0% | 0% UPT loss | | | +| | | | | 11.3% | 5% UPT loss | | | +| | | | | 9.6% | 10% UPT loss | | | +| | | | 10% load(low) | 7.5% | 0% UPT loss | | | +| | | Cat 2, Set 2 | 30% load(medium) | 10.9% | 0% UPT loss | | C-DRX with (cycle, on-duration, inactivity timer) = (320, 10, 80) ms;

Subband based CSI-feedback in every 5 slots;

FTP3 IM traffic model;

A=0.4; $\eta=1, 0.76$ | +| | | | | 7.5% | 0% UPT loss | | | +| | | | | 13.2% | 5% UPT loss | | | +| | | | | 10.2% | 10% UPT loss | | | +| | | | | 10.3% | 0% UPT loss | | | +| | | | | 19.2% | 5% UPT loss | | | +| | | | | 14.8% | 10% UPT loss | | | +| ZTE,Sanechips [15] | TxRU reduction 48TxRU | Cat 2, Set 1 | Low load(RU=8.8% ) | 7.8% | 1.5% UPT loss | Baseline: 64TxRU | FTP3: 20K packet size; $\eta=1$ | +| | | | Low load(RU=8.8% ) | 15.5% | 4.47% UPT loss | | | +| | | | Low load(RU=8.8% ) | 23.5% | 11.06% UPT loss | | | +| | | | light load(RU=20%) | 10.8% | 1.5% UPT loss | | | +| | | | light load(RU=20%) | 21.7% | 7.06% UPT loss | | | +| | | | light load(RU=20%) | 33.7% | 15.31% UPT loss | | | +| | | | medium load(RU=32%) | 12.5% | 3.34% UPT loss | | | +| | | | medium load(RU=32%) | 24.6% | 10.44% UPT loss | | | +| | | | Low load(RU=8.8% ) | 27.1% | 0.9% UPT loss | | | +| | | | light load(RU=20%) | 28.7% | 1.5% UPT loss | | | +| | | | light load(RU=20%) | 31.3% | 7% UPT loss | | | +| | | | medium load(RU=32%) | 23.8% | 1.17% UPT loss | | | +| | | | Low load(RU=10%) | 5.6% | 6.89% UPT loss | | FTP3: 0.1M packet size, $\eta=1$ | + +| | | | | | | | | +|----------------------------------------|--------------|---------------------|-------|------------------|------------------|---------------------------------|--| +| TxRU reduction 32TxRU | | Low load(RU=10%) | 11.0% | 18.39% UPT loss | | | | +| TxRU reduction 48TxRU | | light load(RU=20%) | 9.1% | 6.32% UPT loss | | | | +| TxRU reduction 32TxRU | | light load(RU=20%) | 18.6% | 14.88% UPT loss | | | | +| TxRU reduction 48TxRU | | Medium load(RU=40%) | 11.8% | 8.01% UPT loss | | | | +| TxRU reduction 32TxRU | | Medium load(RU=40%) | 25.0% | 20.88% UPT loss | | | | +| Dynamic TxRUs adaptation via multi-CSI | | Low load(RU=10%) | 7.6% | 3.1% UPT loss | | | | +| | | Low load(RU=10%) | 11.1% | 5.04% UPT loss | | | | +| | | Low load(RU=10%) | 12.7% | 6.03% UPT loss | | | | +| | | light load(RU=20%) | 13.8% | 2.52% UPT loss | | | | +| | | light load(RU=20%) | 16.3% | 4.13% UPT loss | | | | +| | | light load(RU=20%) | 18.7% | 5.15% UPT loss | | | | +| | | light load(RU=20%) | 21.1% | 6.96% UPT loss | | | | +| | | Medium load(RU=40%) | 15.7% | 2.89% UPT loss | | | | +| | | Medium load(RU=40%) | 17.1% | 4.16% UPT loss | | | | +| TxRU reduction 24TxRU | Cat 2, Set 2 | Low load(RU=5%) | 4.8% | 2.03% UPT loss | Baseline: 32TxRU | FTP3: 20K packet size, $\eta=1$ | | +| TxRU reduction 16TxRU | | Low load(RU=5%) | 9.6% | 5.61% UPT loss | | | | +| TxRU reduction 8TxRU | | Low load(RU=5%) | 14.8% | 12.5% UPT loss | | | | +| TxRU reduction 24TxRU | | Low load(RU=11%) | 8.0% | 3.07% UPT loss | | | | +| TxRU reduction 16TxRU | | Low load(RU=11%) | 15.9% | 9.75% UPT loss | | | | +| TxRU reduction 8TxRU | | Low load(RU=11%) | 25.3% | 19.36% UPT loss | | | | +| TxRU reduction 24TxRU | | light load(RU=20%) | 9.6% | 5.19% UPT loss | | | | +| TxRU reduction 16TxRU | | light load(RU=20%) | 19.7% | 12.87% UPT loss | | | | +| TxRU reduction 8TxRU | | light load(RU=20%) | 32.1% | 23.931% UPT loss | | | | +| TxRU reduction 24TxRU | | Low load(RU=5%) | 7.9% | 0.42% UPT loss | | | | +| TxRU reduction 16TxRU | | Low load(RU=5%) | 15.8% | 1.72% UPT loss | | FTP3: 4K packet size, $\eta=1$ | | +| TxRU reduction 8TxRU | | Low load(RU=5%) | 24.3% | 3.54% UPT loss | | | | +| TxRU reduction 24TxRU | | Low load(RU=13%) | 11.2% | 0.67% UPT loss | | | | + +| | | | | | | | | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------|-------|---------------------------------------------------------------------------|---------------------------------------|----------------------------------------------------|--| +| | TxRU reduction 16TxRU | | Low load(RU=13%) | 22.7% | 1.5% UPT loss | | | | +| | TxRU reduction 8TxRU | | Low load(RU=13%) | 35.0% | 3.84% UPT loss | | | | +| | TxRU reduction 24TxRU | | light load(RU=28%) | 14.0% | 1.86% UPT loss | | | | +| | TxRU reduction 16TxRU | | light load(RU=28%) | 27.8% | 6.16% UPT loss | | | | +| | TxRU reduction 8TxRU | | light load(RU=28%) | 43.4% | 14.15% UPT loss | | | | +| | TxRU reduction 24TxRU | | Medium load(RU=48%) | 14.3% | 5.07% UPT loss | | | | +| | TxRU reduction 16TxRU | | Medium load(RU=48%) | 29.4% | 14.63% UPT loss | | | | +| | Dynamic TxRUs adaptation via multi-CSI | | Low load(RU=5%) | 18.1% | 0.62% UPT loss | | | | +| | | | Low load(RU=13%) | 23.7% | 0.16% UPT loss | | | | +| | | | light load(RU=28%) | 19.4% | 0.74% UPT loss | | | | +| | | | Medium load(RU=48%) | 13.7% | 1.01% UPT loss | | | | +| Vivo
[10] [20] | Dynamic antenna port adaptation (antenna ports are dynamically adapted (between 64 ports and 8 ports) according to the cell traffic load, in every slot) | Cat 1, Set 1 | 12.38% | 9.4% | UPT loss:0.36%;
latency increase: 0.08%;
UE power increase: 0.02% | Baseline: antenna ports are always 64 | SLS; No UE DRX; FTP3 traffic model,A=0.4, $\eta=1$ | | +| | | | 12.57% | 9.4% | UPT loss:1.98%;
latency increase: 2.20%;
UE power increase: 0.04% | | | | +| | | | 15.31% | 6.8% | UPT loss:12.26%;
latency increase: 14.20%;
UE power increase: 1.35% | | | | +| | | Cat 2, Set 1 | 12.52% | 8.1% | UPT loss:2.12%;
latency increase: 2.35%;
UE power increase: 0.17% | | | | +| | | | 13.16% | 8.1% | UPT loss:6.48%;
latency increase:8.25%;
UE power increase:0.45% | | | | +| | | | 16.42% | 6.7% | UPT loss:18.50%;
latency increase:38.22%;
UE power increase:1.96% | | | | +| | Dynamic antenna port adaptation (between 64 ports and 8 ports) with multi-CSI | Cat 1, Set 1 | 15.33% | 12.8% | UPT loss:0.02%;
latency increase: 0.05%;
UE power increase: 0.01% | Baseline: antenna ports are always 64 | SLS; No UE DRX; FTP3 traffic model,A=0.4, $\eta=1$ | | +| | | | | | | | | | +| | | | | | | | | | +| | | | | | | | | | + +| | | | | | | | | +|--------------------------|----------------------------------------|--------------|-------------|-------|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOKIA/NSB
[12] | Reduced number of TX to 32 | Cat 2, Set 1 | Low | 27.6% | UPT: 163,26 Mbps | Single cell operation as per SET1 (64 TRX).
UEs are initially in RRC_CONNECTED state | SLS+Post-processing; FTP3 traffic model; A=0,4; Single value $\eta$ (=1) | +| | | | Light | 28.5% | UPT: 117,64 Mbps | | | +| | | | Medium | 29.5% | UPT: 75,47 Mbps | | | +| Intel
[22] | Antenna port adaptation | Cat 1, Set 1 | Low | 19.1% | UPT Baseline: 819.7Mbps
UPT ES: 731.1Mbps;

Avg EE (baseline): 5.11
Avg EE (ES): 5.46 | Baseline: 64Tx (fixed)
ES: 32Tx (fixed) | SLS
No C-DRX used for UEs;
CSI feedback based on SRS;
FTP3 traffic model; A = 0.4;
$\eta(s\_f, s\_p)=1$ for any sf, sp; | +| | | | | 27.3% | UPT Baseline: 819.7Mbps
UPT ES: 585.5Mbps;

Avg EE (baseline): 5.11
Avg EE (ES): 4.81 | Baseline: 64Tx (fixed)
ES: 16Tx (fixed) | | +| | | | | 4.5% | UPT Baseline: 819.7Mbps
UPT ES: 801.8Mbps;

Avg EE (baseline): 5.11
Avg EE (ES): 5.07 | Baseline: 64Tx (fixed)
ES: variable | | +| | | | Light | 25.7% | UPT Baseline: 611.5Mbps
UPT ES: 539.8Mbps;

Avg EE (baseline): 2.67
Avg EE (ES): 3.11 | Baseline: 64Tx (fixed)
ES: 32Tx (fixed) | | +| | | | | 35.7% | UPT Baseline: 611.5Mbps
UPT ES: 400.3Mbps;

Avg EE (baseline): 2.67
Avg EE (ES): 2.73 | Baseline: 64Tx (fixed)
ES: 16Tx (fixed) | | +| | | | | 1.9% | UPT Baseline: 611.5Mbps
UPT ES: 606.7Mbps;

Avg EE (baseline): 2.67
Avg EE (ES): 2.71 | Baseline: 64Tx (fixed)
ES: variable | | +| | | | Medium | 29.6% | UPT Baseline: 457.9Mbps
UPT ES: 389.3Mbps;

Avg EE (baseline): 1.5
Avg EE (ES): 1.84 | Baseline: 64Tx (fixed)
ES: 32Tx (fixed) | | +| | | | | 41.8% | UPT Baseline: 457.9Mbps
UPT ES: 243.9Mbps;

Avg EE (baseline): 1.5
Avg EE (ES): 1.67 | Baseline: 64Tx (fixed)
ES: 16Tx (fixed) | | +| | | | | 0.0% | UPT Baseline: 457.9Mbps
UPT ES: 457.8Mbps;

Avg EE (baseline): 1.5
Avg EE (ES): 1.50 | Baseline: 64Tx (fixed)
ES: variable | | +| | | | | | | | | +| CATT
[25] | Dynamic adaptation of spatial elements | Cat 1, Set 1 | Low load | 6.8% | UPT loss:0.32% | SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms;CSI-RS/TRS 10ms;TxRU= 64. | SLS; (cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);

SSB periodicity 20ms;
CSI-RS/TRS 10ms;
dynamic spatial antenna adaptation:

gNB dynamic adaptation of the number of TxRU from 64TxRU to 32 TxRU;

FTP3 traffic model; A=0,4; $\eta(s\_f, s\_p)=1$ . | +| | | | Light load | 12.2% | UPT loss:0.62% | | | +| | | | Medium load | 18.0% | UPT loss:3.8% | | | + +| | | | | | | | | | +|-------------------------|----------------------------|--------------|-------------|---------|------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | Low load | 6.9% | UPT loss:1.5% | SLS; SSB periodicity 20ms; CSI-RS/TRS 10ms; TxRU= 64. | SLS; No DRX;

SSB periodicity 20ms; CSI-RS/TRS 10ms; dynamic spatial antenna adaptation:

gNB dynamic adaptation of the number of TxRU from 64TxRU to 32 TxRU;

$A=0.4; \eta(s\_f, s\_p)=1$ . | | +| | | | Light load | 12.3% | UPT loss:1.6% | | | | +| | | | Medium load | 19.6% | UPT loss:1.8% | | | | +| Fujitsu
[11] | Dynamic TxRU adaptation | Cat 2, Set 1 | low | 24.1% | 5.7% average UPT loss | BS #TxRU=64 | CSI feedback period = 20ms, feedback delay = 4ms,

immediate antenna adaptation delay
gNB dynamically turns out half of the TxRUs if the DL data in the buffer is expected to be transmitted in the next slot;

FTP3 traffic model; $A=0.4$ ; Single value $\eta (=1)$ | | +| | | | light | 18.6% | 4.1% average UPT loss | | | | +| | | | medium | 12.0% | 2.3% average UPT loss | | | | +| | | Cat 2, Set 2 | low | 26.5% | 0.6% average UPT loss | BS #TxRU=32 | | | +| | | | light | 20.0% | 0.5% average UPT loss | | | | +| | | | medium | 12.8% | 0.3% average UPT loss | | | | +| Ericsson
[18] | BS #TxRU 32 | Cat1, Set 1 | Low | 15.0% | UPT loss of 1% for 95-%,
UPT loss of 2% for 50-%
UPT loss of 8% for 5-% | BS #TxRU 64 | 1 SSB
Single value $\eta (=1)$

FTP3 traffic model

Dynamic switching applied, i.e. adapting number of antennas for energy efficiency in durations when only users in good channel condition are scheduled. Note separate evaluation performed for different number of antennas (i.e. no switching between these settings). | | +| | | | Light | 21.2% | UPT loss of 3% for 95-%,
UPT loss of 6% for 50-%
UPT loss of 12% for 5-% | | | | +| | | | Medium | 22.4% | UPT loss of 3% for 95-%,
UPT loss of 14% for 50-%
UPT loss of 22% for 5-% | | | | +| | BS #TxRU 16 | | Low | 21.4% | UPT loss of 3% for 95-%,
UPT loss of 5% for 50-%
UPT loss of 14% for 5-% | | | | +| | | | Light | 31.6% | UPT loss of 6% for 95-%,
UPT loss of 15% for 50-%
UPT loss of 44% for 5-% | | | | +| | | | Medium | 36.6% | UPT loss of 8% for 95-%,
UPT loss of 25% for 50-%
UPT loss of 33% for 5-% | | | | +| Qualcomm
[17] | #TxRU reduction (64 to 32) | Cat 1, Set 1 | Low | 29.4% | UPT loss at 50%tile: 31%; DL SINR loss at 5% tile: 4.5dB | BS #TxRU 64 | FTP3 traffic model | | +| | | | Light | 28.6% | UPT loss at 50%tile: 30%; DL SINR loss at 5% tile: 6.5dB | | | | +| Samsung
[21] | #TxRU reduction (64 to 32) | Cat 1, Set 1 | Medium | 28.82 % | UPT loss: 12.97%;
latency increase: 16.69%

Baseline traffic: 27.87 % RU
Changed traffic: 32.28 % RU | BS #TxRU 64 | FR1, Port adaptation from 64 to 32 TxRU
FTP3 traffic model | | +| | | | Light | 25.3% | UPT loss: 14.70%;
latency increase: 16.84%;

Baseline traffic: 14.21 % RU | | | | + +| | | | | | | | | +|----------------------------|--------------|--------|-------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|--|---------------------------------------------------------------| +| | | | | | Changed traffic: 16.94 % RU | | | +| | | | Low | 19.47 % | UPT loss: 19.19%;
latency increase: 17.46%

Baseline traffic: 3.48 % RU
Changed traffic: 4.05 % RU | | | +| | | | Low | 10.93 % | UPT loss: 25.12%;
latency increase: 16.66%

Baseline traffic: 1.29 % RU
Changed traffic: 1.56 % RU | | | +| #TxRU reduction (32 to 16) | Cat 1, Set 3 | Medium | 31.9% | UPT loss: 10.37%;
latency increase: 4.58%

Baseline traffic: 21.69 % RU
Changed traffic: 22.56 % RU | BS #TxRU 32 | | FR2, Port adaptation from 32 to 16 TxRU
FTP3 traffic model | +| | | Low | 26.8% | UPT loss: 13.42%;
latency increase: 15.54%

Baseline traffic: 7.23 % RU
Changed traffic: 7.5 % RU | | | | +| #TxRU reduction (32 to 8) | Cat 1, Set 3 | Medium | 48.2% | UPT loss: 7.6%;
latency increase: 12.47%

Baseline traffic: 21.69 % RU
Changed traffic: 23.31 % RU | BS #TxRU 32 | | FR2, Port adaptation from 32 to 8 TxRU
FTP3 traffic model | +| | | Low | 40.5% | UPT loss: 13.7%;
latency increase: 26.4%

Baseline traffic: 7.23 % RU
Changed traffic: 7.76 % RU | | | | + +12 sources observed that BS energy savings can be achieved, at all loads for different sets of reference configurations with FTP3 for FTP3 IM traffic models, with or without UE C-DRX configuration. The gain depends on whether there is multiple CSI report assistance, the number of antenna ports that can be adapted, the load scenarios, and UPT loss. No performance analysis was provided for broadcast and common channels with dynamic antenna adaptation. + +With dynamic/semi-static adaptation of spatial elements, + +- One source shows that BS energy saving for UE specific PDSCH for FR1 can be achieved by 3.4%~19.6% with dynamic adaptation and multi-CSI, compared to dynamic adaptation of spatial elements with single CSI report. The UPT loss was observed by less than 10%; +- 3 sources show that the gain for UE specific PDSCH for FR1 can be 6.8%~31.3% with dynamic adaptation and multi-CSI, compared with no adaptation, with UPT loss of 0.02%~7%; +- 2 sources show that the gain can be 6.7%~26.5% with dynamic adaptation without multi-CSI, compared to no adaptation, with UPT loss of 0.3%~18.5%; +- 9 sources show that the gain can be 4.8%~48.2% with static adaptation without multi-CSI, compared to no adaptation, with UPT loss of 0.02%~87.08%. One source observed that the downlink coverage is reduced by 4.5dB ~ 6.5dB when reducing the number of TxRUs from 64 to 32 in Set 1 FR1 configuration; +- One source shows that when dynamic antenna adaptation is variably changed, the gain is reduced to a range of 0~4.5% with 0.02%~2.18% UPT loss; + +- One source shows BS energy saving can be 18.8%~19.7% that additional gain can be obtained when this scheme is combined with PDSCH power offset. The UPT loss is observed by 9.06%; +- More number of elements are reduced, more gain can be generally obtained. + +On latency, there is negative impact observed in three sources and the increment becomes larger as the number of reduced antenna ports becomes larger. + +On UE power consumption, 2 sources show that there is increase by up to 79.99% (when number of TX RU is reduced from 64 to 8). + +Additionally, one source shows that the average EE can be generally increased except for the low load case where number of antennas is reduced from 64 to 16, and the case of antenna number variably changing. + +#### 6.3.1.3 Legacy UE and RAN1 specification impacts + +There is no impact for legacy UEs if the spatial element adaptation is used on a UE-specific basis, i.e., applied only for UEs supporting the technique. + +Specification impact of the technique may include: + +- mechanisms to indicate spatial element adaptation to the UE, +- signaling to update the active CSI-RS configurations, +- enhancements on CSI-RS (re)configuration, CSI/RRM/RLM measurements, CSI reporting (e.g., multiple CSI reports), and beam management for gNB to switch between different spatial domain configurations, +- associated UE behavior in case of spatial element adaptation occurs, if needed, e.g., measurements, CSI feedback, power control, PUSCH/PDSCH repetition, SRS transmission, TCI configuration, beam management, beam failure recovery, radio link monitoring, cell (re)selection, handover, initial access, etc. + +### 6.3.2 Technique C-2 Adaptation of TRPs in mTRP operation + +#### 6.3.2.1 Description of technique + +Technique C-2 aims to support TRP activation/deactivation that can be informed to the UE when a UE is configured with multiple TRPs. The technique aims to dynamically adapt the number of TRPs transmitting and/or receiving signals and channels. + +#### 6.3.2.2 Analysis of NW energy saving and performance impact + +The following capture the results for TRP muting in multi-TRP operation. + +**Table 6.3.2.2-1: BS energy savings by TRP muting in multi-TRP operation** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | UPT/latency/UE power consumption/Other KPIs | Baseline configuration/assumption | Evaluation methodology/assumption details | +|-------------------|------------------------------------------------------|--------------|---------------|-------------|---------------------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOKIA/NSB
[12] | Semi-static reduced number of TRPs | Cat 2, Set 1 | Low | 38.8% | UPT loss: -14.49% | 2 TRPs are assumed. UEs are initially in RRC_CONNECTED state. | SLS+Post-processing,
FTP3 traffic model; A=0.4; Single value $\eta$ (=1).
70% of the P_Static among TRPs | +| | | | Light | 37.2% | UPT loss: -14.14% | | | +| | | | Medium | 36.9% | UPT loss: -7.27% | | | +| CATT
[25] | Dynamic TRP muting/adaptation in multi-TRP operation | Cat 1, Set 1 | Low load | 28.4% | UE power: 50.6;
UE ESG:12.7% | M-TRP configuration:

One cell is configured with 2TRPs;

Both of TRP are activated. | SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);
SSB periodicity 20ms;
CSI-RS/TRS 10ms;
TRP OFF: 160ms SSB/CSI-RS transmission. | +| | | | Light load | 28.7% | UE power: 50.6;
UE ESG:12.7% | | | + +| | | | | | | | | +|------------------|------------------------------------|--------------|-------------|-------|----------------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Medium load | 19.7% | UE power: 51.6;
UE ESG: 12.4% | | When TRP is activated, additional CSI-RS/TRS is transmitted before data scheduling. FTP3 traffic model; $A=0.4$ ; $\eta(s\_f, s\_p)=1$ . | +| Qualcomm
[17] | Semi-static TRP reduction (2 to 1) | Cat 1, Set 1 | Low | 41.6% | UPT loss at 50%-tile: 16% | 2 TRPs, each with 64 TxRUs | FTP3 traffic model | +| | | | Light | 39.0% | UPT loss at 50%-tile: 22% | | | + +For two TRP configuration case at different loads, + +- (2 sources) with semi-static TRP reduction, BS energy saving gain can be achieved by 36.9%~41.6% compared to no TRP reduction, with UPT loss of 7.27%~22%; +- (one source) with dynamic TRP reduction, compared to no TRP reduction, BS energy saving gain can be achieved by 19.7%~28.7%, without reported UPT impact. It assumes two TRP are always transmitting CSI-RS. + +For the BS energy saving gain around 19.7%~28.7%, it is also observed from one source that UE power savings can be achieved by about 12%. + +#### 6.3.2.3 Legacy UE and RAN1 specification impacts + +There is no impact for legacy UEs if the spatial element adaptation is used on a UE-specific basis, i.e., applied only for UEs supporting the technique. + +Specification impact of the technique may include: + +- UE-specific/group-level/cell common signaling for indicating adaptation of TRPs and TRP-related parameters (e.g. TRP index or CORESET pool index) in mTRP, +- enhancements to UE behaviours due to dynamic adaptation of TRPs, e.g., measurements, CSI feedback, power control, PDCCH/PUCCH/PUSCH/PDSCH repetition, single-DCI based scheduling, multi-DCI based scheduling, SRS transmission, TCI configuration, beam management, beam failure recovery, radio link monitoring, cell (re)selection, handover, initial access, etc. + +## 6.4 Techniques in power domain + +### 6.4.1 Technique D-1 Adaptation of transmission power of signals and channels + +#### 6.4.1.1 Description of technique + +As per current specification, the SSB reference power, *ss-PBCH-BlockPower* is defined in SIB1. The *powerControlOffsetSS* that is the power offset between (NZP)CSI-RS and SSB, and the *powerControlOffset* that is the power offset of PDSCH and (NZP) CSI-RS, are semi-statically configured via RRC signaling. The power offset configurations for PDSCH and CSI-RS are BWP-specific. Current specification allows gNB to adapt the PDSCH transmission power. + +Technique D-1 aims at adapting the transmission power or PSD of downlink signals and channels dynamically, by enhancing the related configuration to the UE (e.g. considering power offsets that account for potential power adaptation) and/or enhancing the UE feedback (e.g. CSI report) to assist NW energy saving operation. The technique may be applicable to one or more of PDSCH, CSI-RS, DMRS, broadcast channels/signals (e.g., SSB/SI/paging). Enhancements for updating the power offset values between various signals and channels, e.g., CSI-RS to SSB, or PDSCH to CSI-RS include using lower layer signaling. + +#### 6.4.1.2 Analysis of NW energy saving and performance impact + +The following capture the results for adaptation of transmission power of signals and channels. + +Table 6.4.1.2-1: BS energy savings by (dynamic) transmission power adaptation + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | Baseline configuration/assumption | Other KPI (%: loss w.r.t. baseline) | | +|-----------------------------|-------------------------------------------|-------------|---------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| MTK
[19] | PDSCH_PowOffset_-3dB | Cat 1 | Light | 8.7% | Baseline: PDSCH power offset 0 dB
ES scheme: PDSCH power offset -3/-6/-9 dB
reference configuration: Set1
FTP3, DRX (160, 8, 100), Single value $\eta (=1)$ | UPT:2.03%,UE power consumption:1.80%,latency:2.07% | | +| | PDSCH_PowOffset_-6dB | | | 11.1% | | UPT:5.66%,UE power consumption:4.47%,latency:6.00% | | +| | PDSCH_PowOffset_-9dB | | | 9.0% | | UPT:10.80%,UE power consumption:9.17%,latency:12.11% | | +| | PDSCH_PowOffset_-3dB | Cat 1 | Medium | 13.9% | | UPT:3.28%,UE power consumption:2.46%,latency:3.39% | | +| | PDSCH_PowOffset_-6dB | | | 18.7% | | UPT:8.97%,UE power consumption:6.80%,latency:9.85% | | +| | PDSCH_PowOffset_-9dB | | | 17.7% | | UPT:19.49%,UE power consumption:14.78%,latency:24.21% | | +| | PDSCH_PowOffset_-3dB | Cat 2 | Light | 8.7% | | UPT:2.03%,UE power consumption:1.80%,latency:2.07% | | +| | PDSCH_PowOffset_-6dB | | | 11.8% | | UPT:5.66%,UE power consumption:4.47%,latency:6.00% | | +| | PDSCH_PowOffset_-9dB | | | 11.2% | | UPT:10.80%,UE power consumption:9.17%,latency:12.11% | | +| | PDSCH_PowOffset_-3dB | Cat 2 | Medium | 14.7% | | UPT:3.28%,UE power consumption:2.46%,latency:3.39% | | +| | PDSCH_PowOffset_-6dB | | | 20.6% | | UPT:8.97%,UE power consumption:6.80%,latency:9.85% | | +| | PDSCH_PowOffset_-9dB | | | 21.0% | | UPT:19.49%,UE power consumption:14.78%,latency:24.21% | | +| | #TxRU_32_PDSCH_PowOffset_-3dB | Cat 1 | Light | 18.8% | | Baseline: PDSCH power offset 0 dB,BS #TxRU 64
ES scheme: PDSCH power offset -3 dB, BS #TxRU 32
reference configuration: Set1
FTP3, DRX (160, 8, 100), Single value $\eta (=1)$ | UPT:9.06%,UE power consumption:7.62%,latency:9.96% | +| | | Cat 2 | | 19.7% | | | UPT:9.06%,UE power consumption:7.62%,latency:9.96% | +| Huawei,
HiSilicon
[9] | Dynamic Power back-off with Multiple CSIs | Cat 2 | 30% load(medium) | 5.3% | baseline: Dynamic Power back-off with Single CSI
ES scheme: Dynamic Power back-off with Multiple CSIs
reference configuration: Set1
FTP3 IM, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; $\eta=1$ , $0.76(s\_f^s\_p<0.5)$ | UPT: 0% loss | | +| | | | | 7.3% | baseline: Dynamic Power back-off with Single CSI
ES scheme: Dynamic Power back-off with Multiple CSIs
reference configuration: Set1
VoIP, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; $\eta=1$ , $0.76(s\_f^s\_p<0.5)$ | | | +| | | | | 6.9% | baseline: Dynamic Power back-off with Single CSI
ES scheme: Dynamic Power back-off with Multiple CSIs
reference configuration: Set2
VoIP, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; $\eta=1$ , $0.76(s\_f^s\_p<0.5)$ | | | +| | | | | 11.5% | baseline: Dynamic Power back-off with Single CSI
ES scheme: Dynamic Power back-off with Multiple CSIs
reference configuration: Set2
VoIP, 4T for Set 2,NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; $\eta=1$ , $0.76(s\_f^s\_p<0.5)$ | | | +| | | | | 5.3% | baseline: Dynamic Power back-off with Single CSI
ES scheme: Dynamic Power back-off with Multiple CSIs
reference configuration: Set2
FTP3 IM, 4T for Set 2, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; $\eta=1$ , $0.76(s\_f^s\_p<0.5)$ | | | +| ZTE,Sanechips
[15] | PDSCH PSD reduction 53.75dBm | Cat 2 | Low load(RU=10%) | 2.3% | Baseline: 55dBm
reference configuration:Set 1: FR1 TDD, FTP3: 20K packet size, slot-level,Pstatic=P3, $\eta=1$ | 0.56% UPT loss | | +| | | | light load(RU=20%) | 4.4% | | 1.82% UPT loss | | +| | | | Medium load(RU=31%) | 6.0% | | 3.8% UPT loss | | +| | PDSCH PSD reduction 52dBm | | Low load(RU=10%) | 6.4% | | 1.26% UPT loss | | +| | | | light load(RU=20%) | 10.1% | | 1.83% UPT loss | | + +| | | | | | | | +|---------------------------|----------------------------------------------------------|-------|-----------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| | | | Medium load(RU=31%) | 12.9% | Baseline: 55dBm
reference configuration:Set 1: FR1 TDD,
FTP3: 0.5M packet size, slot-level, $P_{static}=P3$ , $\eta=1$ | 2.38% UPT loss | +| | | | Low load(RU=4.7%) | 3.9% | | 5.74% UPT loss | +| | | | Low load(RU=9.6%) | 7.0% | | 4.32% UPT loss | +| | | | light load(RU=23.5%) | 12.2% | | 5.48% UPT loss | +| | | | Medium load(RU=38.4%) | 16.6% | | 9.81% UPT loss | +| | PDSCH PSD reduction
47.75dBm | | Low load(RU=13%) | 5.9% | Baseline: 49dBm
reference configuration:Set 2: FR1 FDD,
FTP3: 0.1M packet size, slot-level, $P_{static}=P3$ , $\eta=1$ | 0.64% UPT loss | +| | | | light load(RU=29%) | 8.6% | | 0.05% UPT loss | +| | PDSCH PSD reduction
46dBm | | Low load(RU=13%) | 11.8% | | 1.56% UPT loss | +| | | | light load(RU=29%) | 17.0% | | 0.75% UPT loss | +| | Dynamic PDSCH PSD adaptation
via multi-CSI | | Low load(RU=10%) | 12.1% | Baseline: 55dBm
reference configuration:Set 1: FR1 TDD,
FTP3: 20K packet size, slot-level, $P_{static}=P3$ , $\eta=1$ | 0.38% UPT loss | +| | | | light load(RU=20%) | 16.6% | | 0.35% UPT loss | +| | | | Medium load(RU=31%) | 23.8% | | 1.17% UPT loss | +| | | | Medium load(RU=31%) | 16.4% | | 0.27% UPT loss | +| NOKIA/NSB
[12] | Reduced DL transmit power by 3dB | Cat 2 | Low | 9.8% | Baseline: MaximumTx power of 49 dBm.UEs are initially in RRC_CONNECTED state
reference configuration:Set 2, DL-FTP3,
A=0.4; Single value $\eta (=1)$
SLS | UPT:144 Mbps | +| | Reduced DL transmit power by 6dB | | | 12.2% | | UPT:134 Mbps | +| | Reduced DL transmit power by 9dB | | | 13.4% | | UPT:119 Mbps | +| | Reduced DL transmit power by 3dB | | Light | 15.4% | | UPT:104 Mbps | +| | Reduced DL transmit power by 6dB | | | 19.7% | | UPT:97 Mbps | +| | Reduced DL transmit power by 9dB | | | 17.9% | | UPT:88 Mbps | +| | Reduced DL transmit power by 3dB | | Medium | 16.2% | | UPT:76 Mbps | +| | Reduced DL transmit power by 6dB | | | 23.4% | | UPT:70 Mbps | +| | Reduced DL transmit power by 9dB | | | 24.7% | | UPT:63 Mbps | +| DCM
[16] | PDSCH_PowOffset -6dB | Cat 1 | Light | 6.6% | Baseline:PDSCH power offset 0 dB
reference configuration:Set 1,FTP3,
A=0.4, Single value $\eta (=1)$ | 1.00% UPT loss | +| | PDSCH_PowOffset -12dB | | | 8.3% | | 2.60% UPT loss | +| | PDSCH_PowOffset -18dB | | | 8.7% | | 5.70% UPT loss | +| | PDSCH_PowOffset -6dB | | Medium | 15.5% | | 2.50% UPT loss | +| | PDSCH_PowOffset -12dB | | | 19.5% | | 2.00% UPT loss | +| | PDSCH_PowOffset -18dB | | | 20.4% | | 5.80% UPT loss | +| | PDSCH_PowOffset -6dB | | High | 24.1% | | -3.10% UPT loss | +| | PDSCH_PowOffset -12dB | | | 29.9% | | -0.70% UPT loss | +| | PDSCH_PowOffset -18dB | | | 31.4% | | 0% UPT loss | +| Intel
[22] | Transmit Power Adaptation/ -12dB power | Cat1 | Low | 19.2% | Baseline: Full power
SLS; No C-DRX used for UEs;
CSI feedback based on SRS;
SIB1 BW: 48 PRB;
No paging overhead;
1 SSB beam;
SSB/PRACH periodicity: 20msec;
SIB1 periodicity: 40msec;
Slot level model
For scaling:
$A = 0.4$ ;
$\eta(s\_f, s\_p)=1$ for any sf, sp; | Baseline: 819.7 Mbps
ES: 746 Mbps
Avg EE (Baseline): 5.10
Avg EE (ES) : 5.43 | +| | | | Light | 28.2% | | Baseline: 611.5 Mbps
ES: 567.5 Mbps
Avg EE (Baseline): 2.66
Avg EE (ES) : 3.25 | +| | | | Medium | 34.3% | | Baseline: 457.9 Mbps
ES: 415.1 Mbps
Avg EE (Baseline): 1.5
Avg EE (ES) : 2.03 | +| | Transmit Power Adaptation/ -6dB power | | Low | 17.6% | | Baseline: 819.7 Mbps
ES: 798.5 Mbps
Avg EE (Baseline): 5.10
Avg EE (ES) : 5.83 | +| | | | Light | 25.4% | | Baseline: 611.5 Mbps
ES: 604.8 Mbps
Avg EE (Baseline): 2.66
Avg EE (ES) : 3.41 | +| | | | Medium | 30.0% | | Baseline: 457.9 Mbps
ES: 450.7 Mbps
Avg EE (Baseline): 1.5
Avg EE (ES) : 2.06 | +| CATT
[25] | Adaptation of transmission power of signals and channels | Cat 1 | Low load | 3.9% | Baseline:SSB periodicity 20ms;CSI-RS/TRS 10ms;Transmission power:55dBm;
reference configuration:Set 1, FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes;
$A=0.4$ ; $\eta(s\_f, s\_p)=1$ . | UPTloss:1.6% | +| | | | Light load | 7.7% | | UPTloss:1.8% | +| | | | Medium load | 9.1% | | UPTloss:2.8% | +| | | | Low load | 4.1% | Baseline: SSB periodicity 20ms;CSI-RS/TRS 10ms;(DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);Power domain adaptation;
reference configuration:Set 1, FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes; | UPTloss:1.9% | +| | | | Light load | 7.7% | | UPTloss:3.9% | +| | | | Medium load | 11.2% | | UPTloss:3.1% | + +| | | | | | | | | +|---------------|---------------------------------------------|-------|----------------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|--| +| | | | | | A=0.4; $\eta(s\_f, s\_p)=1$ . | | | +| Ericsson [18] | Tx power adaptation (reduction up to 12 dB) | Cat1 | Low | 20.9% | Baseline: BS Tx power 55 dBm reference configuration: Set 1, FTP3 1 SSB
Single value $\eta (=1)$ .
For ES scheme: dynamic switching applied, i.e. adapting DL Tx power for energy efficiency in durations when only users in good channel condition are scheduled. Note separate evaluation performed for different power settings (i.e. no switching between these settings) | UPT loss of 1% for 95-% UE,
UPT loss of 3% for 50-% UE
UPT loss of 22% for 5-% UE | | +| | | | Light | 40.5% | | UPT loss of 1% for 95-% UE,
UPT loss of 8% for 50-% UE
UPT loss of 36% for 5-% UE | | +| | | | Medium | 47.6% | | UPT loss of 0% for 95-% UE,
UPT loss of 9% for 50-% UE
UPT loss of 13% for 5-% UE | | +| | Tx power adaptation (reduction up to 6 dB) | | Low | 17.7% | | UPT loss of 1% for 95-% UE,
UPT loss of 1% for 50-% UE
UPT loss of 2% for 5-% UE | | +| | | | Light | 33.0% | | UPT loss of 0% for 95-% UE,
UPT loss of 4% for 50-% UE
UPT loss of 7% for 5-% UE | | +| | | | Medium | 38.5% | | UPT loss of 2% for 95-% UE,
UPT loss of 9% for 50-% UE
UPT loss of 7% for 5-% UE | | +| Samsung [21] | Transmission power adaptation | Cat 1 | Reference traffic:
7.5 % RU
Reduced traffic:
4.4 % RU | 51.5% | Baseline: BS Tx power 55 dBm reference configuration: Set 1, FTP3 a static part of power for BS: P_3 A: 0.4
For eta, If two values of $\eta(s\_f, s\_p)$ are used for evaluation, $\eta(s\_f, s\_p) = 0.76$ if $s\_f \cdot s\_p < 0.5$ ; otherwise, $\eta(s\_f, s\_p) = 1$ .
46.5 and 5.2 relative power per a SSB for Cat 1 and Cat 2 | UPT: 10.40%, Packet latency: 24.7%
Scheduling latency: No increase | | +| | | Cat 2 | | 17.5% | | UPT: 10.40%, Packet latency: 24.7%
Scheduling latency: No increase | | +| Qualcomm [17] | Tx power reduction (55dBm to 52dBm) | Cat 1 | Low | 13.1% | Baseline: BS BS #TxRU 64 with 55dBm Tx power
reference configuration: Set 1, FTP3 | UPT loss at 50%-tile: 10%,
DL SINR loss at 5% tile: 4dB | | +| | | | Light | 6.6% | | UPT loss at 50%-tile: 16%,
DL SINR loss at 5% tile: 3dB | | + +With transmission power reduction on PDSCH, 10 sources show that it can achieve BS energy savings gain at all load cases for both Set 1 FR1 TDD and Set 2 FR1 FDD including 4Tx BS antenna configuration, for both BS categories with FTP3 or FTP3 IM model, with or without UE C-DRX configuration. + +With dynamic power reduction assisted by multi-CSI, + +- For UE specific PDSCH in FR1, one source observed BS energy saving gain by 5.3%~11.5%, compared to dynamic power reduction without multi-CSI report; one source observed BS energy savings by 12.1%~23.8%, compared to no power reduction baseline; +- The gain generally increases when the traffic load increases; +- The UPT loss is less than 1.17%; +- No performance analysis was provided for broadcast and common channels with dynamic downlink transmission power adaptation. + +With semi-static power reduction of 3~18dB in 6 sources and two other sources, compared to a baseline without power reduction, network energy saving can be achieved by 2.3%~51.5%, + +- The gain can increase as the traffic load increases in most cases while one source observed a reduced gain, for BS category 1 with power reduction of 3 dB; +- The UPT loss is observed by 2.03%~19.49%. + +One source observed that the latency can be increased by up to 24.21% when the power reduction level is up to 9 dB; one source observed that packet latency can be increased by 24.7% while scheduling delay is not increased. + +On UE power consumption, one source shows that less than 10% increment is observed in most cases. + +One source also observed that when combined with spatial element reduction, in the case of 3 dB power reduction, the network energy savings can be further increased by about 10%, while together with UPT loss/UE power consumption increase/latency increase of 9.06%/7.62%/9.96% respectively. + +One source shows this scheme can increase the average EE. One source observed that the downlink SINR is reduced by 3dB~ 4dB when reducing the downlink transmission power from 55dBm to 52dBm in Set 1 FR1 configuration. + +#### 6.4.1.3 Legacy UE and RAN1 specification impacts + +There is no impact for legacy UEs and UEs that do not support the technique if the signaling of modified power ratio between CSI-RS and PDSCH/SSB or between SSB and CSI-RS, enhancements on CSI measurement and reporting are used on a UE-specific basis, i.e., applied only for UEs supporting the enhancement. + +Specification impact of the technique may include: + +- signaling of modified power of SSB or power ratio between CSI-RS and PDSCH/SSB to provide adaptation of power ratio values, e.g. by utilizing UE-specific, group-level or cell common signaling, +- enhancements on RRM measurements, beam management, beam failure recovery, radio link monitoring, cell (re)selection and handover procedure, +- enhancements to CSI measurements and reporting, e.g. multiple CSI reports in a single report. + +### 6.4.2 Technique D-2 Over the air digital pre-distortion + +#### 6.4.2.1 Description of technique + +gNB may implement digital pre-distortion (DPD) to compensate for the non-linear impairments of the transmitter in standard transparent manner. + +Technique D-2 supports over the air digital pre-distortion at the gNB. In gNB digital pre-distortion over the air, the UEs assist the gNB in reducing nonlinear impairments introduced by the PA, by processing on training signals, and reporting the information needed for gNB digital pre-distortion. + +#### 6.4.2.2 Analysis of NW energy saving and performance impact + +The following capture the results by over the air DPD. + +**Table 6.4.2.2-1: BS energy savings by over the air DPD** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | Baseline configuration/assumption | Other KPI | Note | +|---------------|----------------------------|-------------|---------------|-------------|-----------------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Qualcomm [28] | Over the air DPD (DPD-OTA) | Cat 1 | | 8.9% | Set 3 | UPT loss: 0.00%
Latency increase: 0% | Evaluation showing utilization of PAPR reduction, where the PAPR reduction is used to reduce the backoff PA attribute (Pmax) while maintaining the TX power and signal EVM
Note: $\eta$ was calculated corresponding to the backoff reduction as was provided by a formula [29]. | + +One source observed that DPD-OTA can achieve BS energy saving by 8.9% for Set 3 reference configuration. Note PA scaling values used for this NW ES scheme are not covered by RAN1 power consumption scaling model. On UPT/latency, no negative impact is observed. + +Additional UE power consumption is considered to be negligible due to the low report periodicity expected. + +#### 6.4.2.3 Legacy UE and RAN1 specification impacts + +Legacy UEs and UEs that do not support providing assistance information for gNB digital pre-distortion (DPD) may not be able to contribute to improvement of the DPD. + +Specification impact of the technique may include: + +- signaling/configuration for supporting gNB digital pre-distortion, +- introduction of training signals/CSI-RS enhancements, +- signaling for reporting assistance information for gNB digital pre-distortion, +- indication to the UE of whether it needs to apply non-linear equalization for a transmission. + +### 6.4.3 Technique D-3 Tone reservation + +#### 6.4.3.1 Description of technique + +Technique D-3 supports tone reservation that decreases PAPR, potentially taking into account channel conditions and characteristics. Tone reservation (TR) exploits the channel nulls to carry TR tones, potentially taking into account channel conditions and characteristics. The UE is to be notified of the sub-carriers carrying the TR signal for rate matching purposes only if UE performs transmission or reception of the resource including sub-carriers carrying the TR signal. + +gNB may be able to implement PAPR reduction including tone reservations via implementation with appropriate scheduling of signals and channels. + +#### 6.4.3.2 Analysis of NW energy saving and performance impact + +The following capture the results by channel aware tone reservation. + +**Table 6.4.3.2-1: BS energy savings by Channel Aware Tone reservation** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | Baseline configuration/assumption | Other KPI | Note | | +|---------------|-----------------------------------------------------------------------------------------|-------------|---------------|-------------|-----------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Qualcomm [26] | PA Backoff reduction of 1-3dB due to PAPR reduction from Channel Aware Tone reservation | Cat 1 | | 9.5% | Set 3 | UPT loss: 0.00%
latency increase: 0% | Evaluation showing utilization of PAPR reduction, where the PAPR reduction is used to reduce the backoff PA attribute (Pmax) while maintaining the TX power and signal EVM

The Backoff also compensates for the tones used for the TR signal, thus no UPT loss occurs

Comparing Channel Aware Tone Reservation to Transparent Tone Reservation
Note: $\eta$ was calculated corresponding to the backoff reduction as was provided by a formula [29]. | | +| | | | | 2.1% | Set 1 | | | | +| | | | | 4.4% | UE power consumption increase: 0% | | | | +| | | | | 2.1% | | | | | + +One source observed that channel aware tone reservation can achieve PA back-off reduction of 1~3 dB which leads to 2.1%~9.5% BS energy saving gains depending on configurations, compared with transparent tone reservation. Note PA scaling values used for this NW ES scheme are not covered by RAN1 power consumption scaling model. + +On UPT/latency, no negative impact is observed. + +No impact on UE power consumption is observed. + +#### 6.4.3.3 Legacy UE and RAN1 specification impacts + +Legacy UEs and UEs that do not support the technique may not be aware of tone reservation positions. + +Specification impact of the technique may include: + +- assistance information from the UE to help gNB determine tone reservation positions, +- mechanism to convey information about tone reservation positions to the UE, +- behavior associated with handling of resources with tone reservation positions. + +### 6.4.4 Technique D-4 PA power bias adaptation + +#### 6.4.4.1 Description of technique + +In case of low load, the PA can adapt/reduce its backoff thus reduce the PA power consumption. PA backoff impacts unwanted in-band and out-of-band emissions. gNB may be able to implement PA backoff adaptation in a specification transparent manner. + +Technique D-4 supports modification and/or reduction of the power amplifier (PA) backoff in cases of no or low load. This technique enables PA backoff adaptation for few msec and coordinate PA backoff adaptation among neighbouring cells. + +#### 6.4.4.2 Analysis of NW energy saving and performance impact + +No evaluations of this technique are available. + +#### 6.4.4.3 Legacy UE and RAN1 specification impacts + +Specification impact of the technique may include enhancements to UE measurements for assessing the impact from the PA backoff adaptation of neighbour cells. + +### 6.4.5 Technique D-5 UE post-distortion + +#### 6.4.5.1 Description of technique + +Technique D-5 supports the UE performing received signal post-distortion processing (e.g. non-linear equalization stage that will "invert" the non-linearity) to combat non-linear impairments from the transmitter. The technique also considers enhancements to transmission of reference signals or information to aid the UE to perform post-distortion processing. + +#### 6.4.5.2 Analysis of NW energy saving and performance impact + +The following capture the results for UE post-distortion. + +**Table 6.4.5.2-1: BS energy savings by UE post-distortion** + +| Company | ES scheme | BS Category | Load scenario | ES gain (%) | Baseline configuration/assumption | Other KPI | Note | +|---------------|--------------------|-------------|---------------|-------------|-----------------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Qualcomm [26] | UE post-distortion | Cat 1 | | 16.1% | Set 3 | UPT loss: 0.00%
latency increase: 0% |

Evaluation showing utilization of PAPR reduction, where the PAPR reduction is used to reduce the backoff PA attribute (Pmax) while maintaining the TX power and signal EVM

The Backoff also compensates for the tones used for the TR signal, thus no UPT loss occurs

Processing and power consumption of the UE depends on the UE receiver's design for DPoD.

Note: \eta was calculated corresponding to the backoff reduction as was provided by a formula [29].

| + +One source observed that UE post-distortion can achieve BS energy saving by 16.1% for Set 3 reference configuration. Note PA scaling values used for this NW ES scheme are not covered by RAN1 power consumption scaling model. + +On UPT or latency, there is no negative impact observed. + +The impact on UE power consumption depends on UE receiver's design for DPoD. + +#### 6.4.5.3 Legacy UE and RAN1 specification impacts + +Legacy UEs and UEs that do not support the technique are not able to compensate the received signal distortions based on this enhancement mechanism. + +Specification impact of the technique may include: + +- mechanism and signalling to enable operation of UE post distortion, +- enhancements to reference signals to aid UE post distortion, +- signaling/configuration for supporting UE digital post-distortion, +- introduction of activation of UE post distortion, notification of selected power amplifier model, and possibly configuration of training reference signals, + +- signaling for indicating to the UE of whether it needs to apply non-linear equalization for a downlink transmission. + +## 6.5 Higher layer aspects for network energy savings + +From RAN3 perspective, the following candidate techniques (i.e., those described in clause 6.5.3 and 6.5.4) should be evaluated in terms of energy saving gain at the normative phase. Other candidate techniques discussed are not excluded. + +### 6.5.1 Cell selection/reselection + +For backward compatibility, there is a need to allow NES cells to prevent legacy UEs from camping. NES cells should be able to configure whether to prevent legacy UEs, while allowing NES-capable UEs to camp on. Possible solutions may include but not limited to: + +- Use IntraFreqExcludedCellList/InterFreqExcludedCellList +- Use the cellBarred or cell reservation fields in MIB/SIB + +The definition of NES cell will be discussed in the WI phase. + +The NW should be able to configure NES-capable UEs to prioritize/down-prioritize a specific NES cell or NES cells on a specific frequency. It is left to the WI phase whether the existing mechanism for cell (re)selection is sufficient according to the NES techniques specified. + +From RAN2 perspective, legacy UEs and NES-capable UEs can be handled via cell selection/reselection techniques in the presence of NES cells. + +### 6.5.2 Connected mode mobility + +During the switching of NES modes, it is possible to handover the UEs faster by enhancing the CHO framework with: + +1. Evaluation of conditional handover conditions depending on the NES mode of source/target cell, +2. How to indicate to UE the triggering of the CHO evaluation is up to the WI phase. + +Whenever mobility from source cell is triggered, the NES mode of the target cell could also be considered, e.g., to avoid UEs selecting cells operating in NES mode if any other cell is available. + +From RAN2 perspective, CHO enhancements are feasible. + +Group HO (optimizing the Rel-15 HO procedure) and BWP adaptation with group signalling are not considered by RAN2. + +### 6.5.3 Inter-node Beam Activation + +This mechanism allows an NG-RAN node to request a neighbouring NG-RAN node to switch on certain SSB beams which have been deactivated e.g., in the capacity layer. With this mechanism, the NG-RAN node (e.g., in the coverage-layer) can request the re-activation of SSB beams that are deactivated before. + +### 6.5.4 Paging Enhancements + +This mechanism allows an NG-RAN node to page, e.g. the stationary UEs in a restricted area. For example, paging can be done in certain SSB(s) instead of all the SSBs within a cell. + +# --- 7 Conclusions + +Network energy savings for NR have been studied for both FDD and TDD, both FR1 and FR2. Power model comprised of different BS power states/modes for BS power consumption is defined in clause 5 for evaluation purpose by using relative power, which includes different sleep and active states (including DL transmission and UL reception), and two types of BS categories. A scaling approach considering BS power split by a static part of power and a dynamic part of + +power is established for evaluation purpose, reflecting the relationship of BS power consumption with respect to transmission resources/configurations in time, frequency, spatial and power domain. + +The potential techniques for enabling/improving network energy savings in various domains are evaluated and analysed, as documented in clause 6.1- 6.4. Techniques description, performed evaluations and performance impact on selected KPIs including UPT, access delay, latency, UE power consumption, or on averaged energy efficiency etc., as well as legacy UE impact and specification impact are summarized therein. The relevant higher layer procedures and analysis for some techniques are also included in clause 6.1. Other common aspects from higher layer are studied and the outcome is documented in clause 6.5. + +The study of time domain techniques can be summarized as follows. + +Depending on factors such as selected baselines, BS categories, SLS configurations (including reference configurations, traffic models, number/periodicity of reference signals), scaling parameters, and UE profiles (including UE RRC\_IDLE/INACTIVE/CONNECTED mode, DRX configurations), as well as conditions (such as gNB detection, gNB coordination, UE ability of synchronization) etc., + +- 4 sources show technique A-1-1 of simplified SSB without PBCH or with partial PBCH could achieve BS energy savings by 0.7%~30.49% in range, with no observed impact on UPT due to empty load. +- 2 sources show technique A-1-2 of static skipping one or more of SSB/SIB1 transmission could achieve BS energy savings by 0.3%~25.4% in range, meanwhile the impact on access delay/latency is not provided in the simulation. +- 9 sources show technique A-1-3 of statically adapting the periodicity of SSB longer than 20ms up to 1280ms (with current maximum periodicity being 160ms) could achieve BS energy savings by 0.9%~84.8% in range, meanwhile when traffic occurs and load increases, the UPT significantly decreases and the latency/access delay/UE power consumption increases proportionally as the periodicity of SSB/SIB increases compared to a corresponding baseline. +- 2 sources show technique A-1-4 of statically adapting Paging (by 1 source) or SSB transmission patterns (by 1 source), could achieve BS energy savings by 0.2%~42.3% in range for Paging enhancement or 10.3% for SSB enhancement, meanwhile UPT/latency impact are not reported. +- 1 source shows technique A-1-5 of statically adapting RACH periodicity/occasions could achieve BS energy savings by 14.4%~24.9% in range, meanwhile access delay/latency is increased from 10ms to 70ms, proportional to the increased PRACH periodicity. +- 1 source shows technique A-1-6 of scheduling SIB1 by SSB could achieve BS energy savings by 4.8%~14.8% in range without report of impact on UPT/latency as irrelevant to the technique. +- 5 sources show technique A-3-1 of UE WUS triggering gNB for SSB/SIB/RACH, with the assumption of ideal detection of UE WUS, could achieve BS energy savings by 6.2%~80.7% in range with UPT loss by 0%~24.2%, while 1 source shows technique A-3-2 of UE WUS triggering gNB to wake up in case of uplink traffic arrival could achieve BS energy savings by 25.7%~93% in range, with latency reduction of 0%~45.5% depending on the SR periodicity assumed in the baseline, + - Note technique A-3-2 of UE WUS triggering gNB to wake up in case of uplink traffic arrival assumes that gNB can detect WUS during sleep state. +- 6 sources show technique A-4 of semi-static UE C-DRX alignment could achieve BS energy savings by 0.2%~71.4% in range, meanwhile, 3 sources show that there is negative impact on UPT with loss from 0.91% to 15.5%, and 1 source shows that when the UE DRX cycle is 160ms and gNB active time is 80ms the UPT is increased while in other configurations there can be large UPT loss (up to 62.4%), 1 source shows marginal increment on latency while 1 source show up to 50% latency increase. +- 3 sources show technique A-5-2 of on-demand SSB/SIB1 could achieve BS energy savings by 2.6%~43.4% in range, meanwhile performance impact of on demand SSB/SIB was not provided. +- Technique A-1-4 of adapting Paging and technique A-1-5 of adapting RACH periodicity/occasions may be used in a cell where legacy UE can still use legacy Paging/RACH resources with negative impact on latency for legacy UEs, while other techniques except technique A-3 and A-4 may be enabled for a carrier only when legacy UEs are not using the carrier. + +- For technique A-3, legacy UEs cannot wake up a cell that is inactive, and cannot operate in the cell if not provided with expected transmission from the cell; for technique A-4, depending on DTX/DRX configuration, legacy UEs may not be impacted. +- Technique A-4 of adaptation of Cell DTX/DRX is also studied in higher layer. From RAN2 perspective, technique A-4 is considered feasible and it is also beneficial to align UE DRX durations with Cell DTX and DRX durations among multiple UEs. +- Technique A-3 of UE WUS is also discussed in higher layer and from RAN2 perspective, it is feasible if RAN1 agrees to support WUS, and details can be discussed in normative phase if supported. + +For techniques in frequency domain, the study can be summarized as follows. + +Under various conditions, + +- 8 sources show technique A-5-1 (for non-CA) or B-1-1 (for CA) of SSB- and/or SIB1-less operation in two carriers deployment could achieve BS energy savings by 0.3%~98.4% in range on the energy saving cell/carrier and if more information, such as system information, needs to be transmitted at the anchor carrier then 2.3%~18.9% BS energy increases on the associated cell/carrier, meanwhile the UPT/UE power consumption is not negatively impacted while 1 source shows slightly increased UPT and 1 source shows reduced SCell activation delay, assuming UE sync is based on SSB from anchor carrier and UE measurement is not considered, +- A cell without SSB (or SIB1) cannot be operated as PCell/PSCell/inter-band SCell (or PCell for SIB1-less) for legacy UEs. Mobility performance impact(s) (for techniques A-5-1 of SSB-less operation in non-CA), or performance impact(s) due to lack of AGC and cell measurement (for techniques B-1-1 of SSB-less operation in CA) is not provided. For non-CA operation with both SSB-less and SIB1-less, comparison to CA is not provided. +- 1 source shows technique B-1-2 of dynamic UE-group PCell switching could achieve BS energy savings by 5.8%~37.5% in range, meanwhile UPT degrades by 14% if one SCell goes to dormant state. +- 1 source shows technique B-2 of statically BWP adaptation of BW reduction for multiple UEs within a carrier could achieve BS energy savings by 17.4%~52.2% in range, while the reported UPT loss ranges from 6.1%~28.2%. +- 2 source show technique B-3 of BW adaptation of multiple UEs within a BWP could achieve BS energy savings by up to 1.75%, and 1 source shows negative energy saving gains (i.e. energy consumption increase) up to 75.4% with significant UPT loss (up to 88%). +- Evaluation of all techniques is based on the baseline BS power model in Clause 5. +- From RAN2 perspective, technique A-5-1/B-1-1 of SCell without SSB in inter-band CA and NES cell without SSB/SIB may need more detailed study in normative phase (if supported) with feasibility up to RAN1. From RAN2 perspective, techniques B-2 is not considered. + +Based on the study and summary, from time and frequency domain, + +- Technique A-4 of adaptation of DTX/DRX, including the alignment of Cell DTX/DRX with UE DRX, is beneficial for network energy savings. +- Adaptation/reduction/elimination of common channels/signals (UE WUS can also be considered) in single or multi-carrier operation are beneficial for network energy savings. + +For techniques in spatial domain, over baseline of 32/64 TxRU for a gNB/TRP, the study can be summarized as follows, + +- 12 sources show technique C-1 of adaptation of spatial elements could achieve BS energy savings by 0~48.2% in range, with legacy UE co-existence, at the expense of small (less than 10% for dynamic adaptation with multi-CSI) to large (up to 87.08% for static adaptation) negative impact on UPT. 4 sources provide evaluation results for dynamic adaptation while 9 sources provide evaluation result for static adaptation. +- 3 sources show technique C-2 of TRP muting in multi-TRP operation could achieve BS energy savings by 19.7%~41.6% in range, at the expense of UPT loss of 7.27%~22% for static TRP muting. 1 source provides evaluation results for dynamic adaptation while 2 sources provide evaluation results for static adaptation. + +Based on the study, at least a technique based on C-1 is beneficial for network energy savings, and can be recommended. Technique C-2 also has the potential to provide large network energy saving gain. + +For techniques in power domain, the study can be summarized as follows, + +- 10 source show technique D-1 of transmission power reduction on PDSCH could achieve BS energy savings by 2.3%~51.5% in range, with legacy UE co-existence, with UPT loss of 0~19.49%/latency increment of up to 24.21%/UE power consumption increment of up to 14.78%. 2 sources provide evaluation results for dynamic adaptation while 8 sources provide evaluation results for static adaptation. +- 1 source shows technique D-2 of over the air digital pre-distortion, technique D-3 of channel aware tone reservation, and technique D-5 of UE post-distortion, could achieve BS energy savings by 8.9%, by 2.1%~9.5%, and by 16.1% respectively, with no/negligible negative impact on UPT/UE power consumption, with PA scaling values not covered by the scaling of power model in clause 5. + +Based on the study, at least a technique based on D-1 is beneficial for network energy savings. + +For other higher layer aspects for network energy savings, from their perspective, the study can be summarized as follows. + +- It is feasible to handle legacy UEs and NES-capable UEs via cell (re-)selection techniques. It is also feasible and possible to enhance the CHO framework to handover UEs faster. +- Group HO is not considered. +- Inter-node beam activation and paging enhancement need more study in normative phase, if supported. +- A means that one can prevent legacy UEs from camping on NES cells (of which definition can be left to WI phase), and/or allow NES-capable UEs to (down-)prioritize specific NES cell(s) on specific frequency, is needed, which is left to the WI phase depending on whether the existing mechanism for cell (re)selection is sufficient according to the NES techniques specified. + +It is recommended that the normative phase includes not only energy saving techniques (the necessary enhancements would need to be further identified during the normative phase) but also the mitigation of their impacts when network applies network energy savings technique(s). + +# Annex A: Evaluation scenarios, traffic models and loads + +For FR1, at least urban macro is prioritized. Urban micro can be optionally considered. For FR2, urban micro is prioritized. + +FTP3 (0.5MB as packet size, 200ms as mean inter-arrival time), FTP3 IM (0.1MB as packet size, 2s as mean inter-arrival time) and VOIP can be considered in the evaluation. It is up to company report which traffic model is used among the agreed three traffic models in their evaluations. Other models may be used as well, and parameter (e.g. packet size and arrival rate) adjustment can be optionally considered and reported. + +In the evaluation, + +- a load (L)% of a cell is a percentage of resources used for UE specific PDSCH/PUSCH. +- The following load scenarios are considered. + +**Table A-1** + +| Load scenario | Characteristics | +|------------------------------------------------------------------------------------|------------------------------------------------------------------| +| Idle/empty load | Include cell-specific signals and channels, and $L = 0$ | +| low load | Include cell-specific signals and channels, and $0 < L \leq 15$ | +| Light load | Include cell-specific signals and channels, and $15 < L \leq 30$ | +| Medium load | Include cell-specific signals and channels, and $30 < L \leq 50$ | +| For CA, the companies report whether the load is defined per CC or across all CCs. | | + +It is up to company report the use of UE C-DRX. + +- the baseline configuration (for alignment/calibration) for C-DRX, if reported, can be as below; +- Other inactivity timer values can be optionally reported. + +**Table A-2** + +| Traffic type | FTP | IM | VoIP | +|-------------------------|------------------------|-------------------------|---------------------------------| +| Model | FTP model 3 | FTP model 3 | As defined in R1-070674. | +| Packet size | 0.5 Mbytes | 0.1 Mbytes | Assume max two packets bundled. | +| Mean inter-arrival time | 200 ms | 2 sec | | +| DRX Period | 160 ms | 320 ms | 40 ms | +| DRX Inactivity timer | 100 ms | 80 ms | 10 ms | +| On duration | FR1: 8 ms
FR2: 4 ms | FR1: 10 ms
FR2: 5 ms | FR1: 4 ms
FR2: 2 ms | + +# Annex B: Simulation assumptions + +For FR1, the baseline SLS assumptions is provided as below. Other carrier frequencies can be optionally considered. + +**Table B-1: Baseline SLS assumptions for FR1 Set 1 and Set 2** + +| | | Parameters | | +|-------------------------|----------------------------------------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| | | Set 2 | Set 1 | +| Basic parameters | Channel model | 3D-Uma as in TR 38.901 (low-loss O2I penetration model) | 3D-Uma as in TR 38.901 (low-loss O2I penetration model) | +| | Percentage of high loss and low loss building type | 100% low loss | 100% low loss | +| | Device deployment | 80% indoor, 20% outdoor | 80% indoor, 20% outdoor | +| | Inter-site distance | 500m | 500m | +| | Network Topology | 7*3 Sector | 7*3 Sector | +| | Carrier Frequency | 2.1GHz | 4.0GHz or 2.6GHz | +| | Multiple access | OFDMA | OFDMA | +| | Duplexing | FDD | TDD | +| | Numerology | 15KHz, 14 OFDM symbol slot | 30KHz, 14 OFDM symbol slot | +| | Guard band ratio on simulation bandwidth | FDD: 6.4% (104RB for 15kHz SCS and 20 MHz BW) | TDD: 2.08% (272 RB for 30kHz SCS and 100 MHz bandwidth) | +| | Simulation bandwidth | Follow reference configuration, (equal split of 10 MHz for UL and DL) | Follow reference configuration | +| | Frame structure | / | DDDSU (S slot is assumed as 10D:2G:2U) | +| | UT attachment | Based on RSRP | Based on RSRP | +| | Wrapping around method | Geographical distance based wrapping | Geographical distance based wrapping | +| | Traffic model | Follow previous RAN1 agreements | Follow previous RAN1 agreements | +| BS parameters | BS antenna height | 25 m | 25 m | +| | BS noise figure | 5 dB | 5 dB | +| | BS antenna element gain | 8 dBi | 8 dBi | +| | Antenna configuration at TRxP | For 32T: (M,N,P,Mg,Ng; Mp,Np) = (8,8,2,1,1;2,8)
(dH, dV)=(0.5, 0.8) $\lambda$ | For 64T:
(M, N, P, Mg, Ng, Mp, Np) = (8, 8, 2, 1, 1, 4, 8).
based on 38.802 | +| UE parameters | UE power class | 23dBm | 23dBm | +| | UE noise figure | 9 dB | 9 dB | +| | UE antenna element gain | 0 dBi | 0 dBi | +| | UE antenna height | Outdoor UEs: 1.5 m; Indoor UEs: 1.5m or consider floor height | Outdoor UEs: 1.5 m; Indoor UEs: 1.5m or consider floor height | +| | Antenna configuration at UE | For 4R: (M,N,P,Mg,Ng; Mp,Np)= (1,2,2,1,1; 1,2)
(dH, dV)=(0.5, N/A) $\lambda$ | For 4R: (M,N,P,Mg,Ng; Mp,Np)= (1,2,2,1,1; 1,2)
(dH, dV)=(0.5, N/A) $\lambda$ | +| Transmission parameters | Modulation | Up to 256 QAM | Up to 256 QAM | +| | Transmission scheme | SU-MIMO | SU-MIMO | +| | SU dimension | For 4Rx: Up to 4 layers | For 4Rx: Up to 4 layers | +| | DL CSI measurement | Non-precoded CSI-RS based | Precoded CSI-RS based | +| | DL codebook | Type I/II codebook | non-PMI transmission | +| | SRS transmission | N/A | For UE 4 Tx ports: Non-precoded SRS | +| | CSI feedback | Company to report the assumptions | Company to report the assumptions | +| | Interference measurement | SU-CQI; CSI-IM for inter-cell interference measurement | SU-CQI; CSI-IM for inter-cell interference measurement | +| | Scheduling | PF | PF | +| | Receiver | MMSE-IRC | MMSE-IRC | +| | Channel estimation | Non-ideal | Non-ideal | +| | HARQ scheme | Ideal | Ideal | +| | Max HARQ retransmission | 3 | 3 | +| | Target BLER | 10% of first transmission | 10% of first transmission | +| | Power control parameters | Open loop, P0=-80dBm, alpha=0.8 | Open loop, P0=-80dBm, alpha=0.8 | +| Common RS | SSB period | 20ms | 20ms | +| | SS blocks per SSB burst | Up to 4 | Up to 8 | +| | SSB time resource | 4 symbols for each SSB | 4 symbols for each SSB | + +| | | | | +|--|------------------------|--------|--------| +| | SSB frequency resource | 20 RBs | 20 RBs | +|--|------------------------|--------|--------| + +For FR2, the baseline SLS assumptions is provided as below. Other carrier frequencies can be optionally considered. + +**Table B-2: Baseline SLS assumptions for FR2 Set 3** + +| | | | | +|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------------------------------------------------| +| BS type | Micro | UE BWP | 100 Mhz | +| Network layout and inter-site distance | 21 cells Wraparound (ISD=200m) | UE height | 1.5m | +| Channel model | UMi | UE noise figure | 13 dB | +| Link direction | Downlink | UE antenna element gain | 5 dBi | +| Frequency range | 30GHz | UE receiver | MMSE-IRC | +| Duplex | TDD | UE deployment | 20% Outdoor in cars: 30km/h, 80% Indoor in houses: 3km/h | +| Frame structure | DDDSU (S slot is assumed as 10D:2G:2U) | Traffic model and C-DRx configuration | follow previous RAN1 agreement | +| Subcarrier spacing | 120 kHz | UE density/NW Load | Follow previous RAN1 agreements | +| Simulation bandwidth | 100 MHz | Maximum supported Modulation and coding scheme | Up to 256QAM | +| Number of carriers | 1 CC | Guard band ratio on simulation bandwidth | 7.8% (64 RB for 120kHz SCS and 100 MHz bandwidth) | +| Slot size | 14 OFDM symbols | Channel estimation | Ideal | +| BS antenna configuration | 2 TxRU:
Baseline:
(M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1;1,1); (dH, dV) = (0.5 $\lambda$ , 0.5 $\lambda$ ) (dg,H, dg,V) = (2.5 $\lambda$ , 2.5 $\lambda$ )
Optional:
(M, N, P, Mg, Ng)=(8:16:2:2:2) | HARQ scheme | Ideal | +| Total Tx power | 33 dBm, EIRP limited to 63 dBm (as agreed in ref. conf. set 3) | Max HARQ retransmission | 3 | +| BS height | 10m | Target BLER | 10% of first transmission | +| BS noise figure | 7 dB | Power control parameters | Open loop, Alpha=1, P0=-106 dBm | +| BS antenna element gain | 8 dBi | Scheduling algorithm | PF | +| UE antenna configuration | 2T/4R, (M, N, P, Mg, Ng; Mp, Np) = (1,2,2,1,1;1,2), (dH, dV) = (0.5 $\lambda$ , N/A $\lambda$ ) | Cell selection algorithm | RSRP Slow Fading | +| UE max transmit power | 23 dBm | SS blocks per SSB burst | Up to 64 | + +(M, N, P, Mg, Ng; Mp, Np) + +- M: Number of vertical antenna elements within a panel, on one polarization +- N: Number of horizontal antenna elements within a panel, on one polarization +- P: Number of polarizations +- Mg: Number of panels in a column; +- Ng: Number of panels in a row; +- Mp: Number of vertical TXRUs within a panel, on one polarization +- Np: Number of horizontal TXRUs within a panel, on one polarization. + +Other parameters can be optionally reported. + +Company can also optionally report the actual total DL transmit power allocation for the baseline and the proposed technique, if different from the agreed reference configuration. + +Additionally, for FR1, the following SLS assumptions can be optionally included: + +- BS antenna configuration: 4T +- BS Total Tx power: derived based on the scaling in clause 5.1 +- SS blocks per SSB burst: reduced to 1 +- Other assumptions are same as those corresponding to Set 2 reference configuration +- Additional transition energy is calculated taken into account the additional transition energy for Set 1/Set 2/Set 3 in clause 5.1 +- Company to report the details. + +# Annex C: Change history + +| Change history | | | | | | | | +|----------------|---------------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN1#109-e | R1-2205307 | | | | TR Skeleton | 0.0.1 | +| 2022-05 | RAN1#109-e | R1-2205694 | | | | Endorsed TR Skeleton | 0.0.2 | +| 2022-08 | RAN1#110 | R1-2208315 | | | | TR update per agreements in RAN1#109-e and RAN1#110, and skeleton of TR 38.864 for NR network energy savings approved in RAN3 per R1-2207999. | 0.1.0 | +| 2022-10 | RAN1#110bis-e | R1-2209679 | | | | TR update per agreements in post RAN1#110 email discussion and some editorials. | 0.2.0 | +| 2022-10 | RAN1#110bis-e | R1-2210792 | | | | TR update per agreements during RAN1#110bis-e. | 0.3.0 | +| 2022-11 | RAN1#111 | R1-2212483 | | | | TR update for inclusion of agreements made in R2-2211067 in RAN2 #119bis-e and in R3-226001 in RAN3 #117bis-e. | 0.4.0 | +| 2022-11 | RAN1#111 | R1-2213007 | | | | TR update for reflection of agreements made in RAN1#111, and post meeting email discussion of RAN1, RAN2#120 (R2-2213041) and RAN3#118 (R3-226898). | 0.5.0 | +| 2022-12 | RAN#98e | RP-222821 | | | | TR presented in RAN for one-step approval | 1.0.0 | +| 2022-12 | RAN#98e | | | | | TR under change control further the approval for inclusion in Rel-18 by RAN | 18.0.0 | +| 2023-03 | RAN#99 | RP-230455 | 0001 | | F | Addition of abbreviations and symbols to TR 38.864 | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38865/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38865/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7962e29dbdcacf8dc588b7babecca45f1687403a --- /dev/null +++ b/marked/Rel-18/38_series/38865/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:689723c0690823310ce5004907bfdc8e0be551702a82812f9978abfd0bed498c +size 9792 diff --git a/marked/Rel-18/38_series/38865/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38865/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c80959c6876e13095edc745e423306bec848efeb --- /dev/null +++ b/marked/Rel-18/38_series/38865/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85de6d2292be5a2bfa0bd2566807928bae238750555656085fd9ed0d0c930da2 +size 5687 diff --git a/marked/Rel-18/38_series/38865/raw.md b/marked/Rel-18/38_series/38865/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5b502b3d940d50c0558601b61d231723a9c3693a --- /dev/null +++ b/marked/Rel-18/38_series/38865/raw.md @@ -0,0 +1,1919 @@ + + +# 3GPP TR 38.865 V18.0.0 (2022-09) --- + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on further NR RedCap UE complexity reduction (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +A GLOBAL INITIATIVE + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Introduction..... | 6 | +| 5 Study objectives ..... | 7 | +| 6 Evaluation methodology ..... | 7 | +| 6.1 Evaluation methodology for UE complexity reduction ..... | 7 | +| 6.2 Evaluation methodology for coverage impact ..... | 8 | +| 7 UE complexity reduction features..... | 12 | +| 7.1 Introduction to UE complexity reduction features ..... | 12 | +| 7.2 Further UE bandwidth reduction..... | 12 | +| 7.2.1 Description of feature ..... | 12 | +| 7.2.2 Analysis of UE complexity reduction ..... | 13 | +| 7.2.3 Analysis of performance impacts ..... | 17 | +| 7.2.4 Analysis of network deployment and coexistence impacts ..... | 17 | +| 7.2.5 Analysis of specification impacts..... | 17 | +| 7.3 Further UE peak rate reduction ..... | 17 | +| 7.3.1 Description of feature ..... | 17 | +| 7.3.2 Analysis of UE complexity reduction ..... | 18 | +| 7.3.3 Analysis of performance impacts ..... | 21 | +| 7.3.4 Analysis of network deployment and coexistence impacts ..... | 21 | +| 7.3.5 Analysis of specification impacts..... | 21 | +| 7.4 Relaxed UE processing timeline ..... | 21 | +| 7.4.1 Description of feature ..... | 21 | +| 7.4.2 Analysis of UE complexity reduction ..... | 22 | +| 7.4.3 Analysis of performance impacts ..... | 22 | +| 7.4.4 Analysis of network deployment and coexistence impacts ..... | 22 | +| 7.4.5 Analysis of specification impacts..... | 23 | +| 7.5 Combinations of UE complexity reduction features ..... | 23 | +| 7.5.1 Description of feature combinations..... | 23 | +| 7.5.2 Analysis of UE complexity reduction ..... | 23 | +| 7.5.3 Analysis of performance impacts ..... | 24 | +| 7.5.4 Analysis of network deployment and coexistence impacts ..... | 24 | +| 7.5.5 Analysis of specification impacts..... | 24 | +| 8 Coverage impact ..... | 25 | +| 8.1 Introduction to coverage impact..... | 25 | +| 8.2 Coverage impact evaluation..... | 25 | +| 8.2.1 Urban scenario at 2.6 GHz ..... | 25 | +| 8.2.2 Rural scenario at 0.7 GHz ..... | 34 | +| 8.2.3 Urban scenario at 4 GHz ..... | 40 | +| 8.2.4 Summary of coverage impact evaluation ..... | 47 | +| 9 Conclusions and recommendations..... | 50 | +| Annex A: Change history ..... | 52 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +This document captures the findings from the study item "Study on further NR RedCap UE complexity reduction" [2]. + +The study concerns potential solutions for reducing UE complexity further compared to the RedCap UE type introduced in Rel-17 [3], providing NR support for low-tier devices between existing LPWA UEs and Rel-17 RedCap UEs to further expand the market for RedCap use cases with relatively low cost, low energy consumption, and low data rate requirements, targeting 10 Mbps peak rate. + +The study focuses on UE bandwidth reduction to 5 MHz and/or UE peak rate reduction to 10 Mbps, possibly in combination with relaxed UE processing timeline. The scope of the study includes support for FR1 bands for FDD and TDD and coexistence with Rel-15/16/17 UEs. The scope of the study does not include LPWA use cases. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP RP-213661: "New SID on Study on further NR RedCap UE complexity reduction". +- [3] 3GPP RP-221163: "Summary of WI on support of reduced capability (RedCap) NR devices" +- [4] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities". +- [5] 3GPP TR 38.875: "Study on support of reduced capability NR devices". +- [6] 3GPP TR 38.830: "Study on NR coverage enhancements". +- [7] 3GPP R1-2207981: "FL summary #2 for collection of evaluation results for Rel-18 RedCap SI". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**RedCap UE:** A UE with reduced capabilities as specified in clause 4.2.21.1 in TS 38.306 [4]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +      + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +      + +# --- 4 Introduction + +5G aims to accelerate industrial transformation and digitalization, which improve flexibility, enhance productivity and efficiency, reduce maintenance, and improve operational safety. Industrial sensors play an important role for realizing such a vision. Not only widely used in industrial automation and digitalization use cases, industrial sensors are also widely used in the general environmental monitoring use cases such as monitoring of critical infrastructure (e.g., buildings, bridges, water dams, etc.) or monitoring for natural disasters (e.g., wild fire, flood, tsunami, earthquake, etc.). + +Another emerging new class of new 5G use cases is the smart city vertical, which covers data collection and processing to more efficiently monitor and control city resources, and to provide services to city residents. Especially, the deployment of surveillance cameras is an essential part of the smart city but also of factories and industries. + +Furthermore, there have been increasing interests in wearables use cases such as smart watches, eHealth related devices, and medical monitoring devices. These use cases call for different design considerations and have different requirements in terms of form factor, UE complexity and energy efficiency, compared to eMBB devices. + +The support of industrial sensors, video surveillance, and wearables were the motivations behind Rel-17 RedCap. Through the Rel-17 NR RedCap work item, 3GPP has established a framework for enabling reduced capability NR devices suitable for a range of use cases, including the industrial sensors, video surveillance, and wearables use cases, with requirements on low UE complexity and sometimes also on low UE power consumption. + +Now when the foundation has been laid in Rel-17 [3], enhancements can be considered to improve the support for the mentioned use cases and also to expand RedCap into a new range of use cases such as smart grid. + +To further expand the market for RedCap use cases with relatively low cost, low energy consumption, and low data rate requirements, e.g., industrial wireless sensor network use cases, some further complexity reduction enhancements should be considered. + +Rel-18 RedCap should provide NR support for low-tier devices between existing LPWA UEs and the capabilities of Rel-17 RedCap UEs. The supported peak data rate for Rel-18 RedCap targets to 10Mbps. Rel-18 RedCap should not overlap with existing LPWA solutions. + +The enhancements should be introduced while maintaining the integrity of the RedCap ecosystem and maximizing the benefit of economies of scale. The SI targets enhancements applicable to the RedCap framework defined in Rel-17, including principles of network awareness of device capabilities. + +# 5 Study objectives + +The study includes the following objectives: + +- Study further UE complexity reduction techniques based on Rel-17 evaluation methodology in TR 38.875. + - Consider network impact, coexistence of Rel-17 and Rel-18 RedCap and non-RedCap UEs in a cell, UE impact, specification impact. +- Potential solutions, which may complement each other, for reducing device complexity are focusing on: + - UE bandwidth reduction to 5MHz in FR1, + - Possibly in combination with relaxed UE processing timeline for PDSCH and/or PUSCH and/or CSI + - Reduced UE peak data rate in FR1, + - Possibly including restricted bandwidth for PDSCH and/or PUSCH + - Possibly in combination with relaxed UE processing timeline for PDSCH and/or PUSCH and/or CSI +- Notes: + - Rel-15 SSB should be reused and L1 changes minimized. + - Operation in BWP with/without SSB and without/with RF retuning should be considered. + - It is not precluded that some solutions for FR1 can be applied to FR2 in WI stage. + - Aim to define a single Rel-18 RedCap UE type for further UE complexity reduction. + +# 6 Evaluation methodology + +## 6.1 Evaluation methodology for UE complexity reduction + +For complexity evaluation of UE complexity reduction techniques, the methodology used in TR 38.875 was used as a starting point. + +The reference NR devices were defined for FR1 FDD and FR1 TDD in clause 6.1 in TR 38.875 and are reused in this study. For complexity reduction estimation, the detailed complexity breakdown for the Rel-15 reference NR devices according to Table 6.1-1 is reused, where the RF-to-baseband complexity ratio is assumed to be 40:60 for an FR1 UE. + +For comparison with a Rel-17 baseline when evaluating the potential Rel-18 UE complexity reduction features, the Rel-17 RedCap UE supports 20 MHz, 1 Rx, 1 layer, DL 64QAM, UL 64QAM, FDD or TDD. In addition, cases with 2 Rx, 2 MIMO layers, and HD-FDD features are optionally evaluated. In all comparisons, the Rel-17 RedCap UEs and the potential Rel-18 UEs being compared have the same number of antenna branches, the same number of layers, the same maximum supported modulation order, and the same duplex mode (among HD-FDD, FD-FDD, and TDD). + +NOTE: This study assesses, from a 3GPP standpoint, the technical feasibility of further reducing the complexity of RedCap devices. Given that factors outside 3GPP responsibility influence the cost of a modem/device, this study item (and this study report) cannot guarantee, or be used as a guarantee, that such modem/device will be low-cost in the market. + +**Table 6.1-1: Detailed complexity breakdown for the FR1 reference NR devices** + +| Functional block | FR1 FDD (2Rx) | FR1 TDD (4Rx) | +|-------------------------------------------------------------|---------------|---------------| +| RF | | | +| Power amplifier | ~25% | ~25% | +| Filters | ~10% | ~15% | +| RF transceiver
(incl. LNAs, mixer, and local oscillator) | ~45% | ~55% | +| Duplexer / Switch | ~20% | ~5% | +| Baseband | | | +| ADC / DAC | ~10% | ~9% | +| FFT/IFFT | ~4% | ~4% | +| Post-FFT data buffering | ~10% | ~10% | +| Receiver processing block | ~24% | ~29% | +| LDPC decoding | ~10% | ~9% | +| HARQ buffer | ~14% | ~12% | +| DL control processing & decoder | ~5% | ~4% | +| Synchronization / cell search block | ~9% | ~9% | +| UL processing block | ~5% | ~5% | +| MIMO specific processing blocks | ~9% | ~9% | + +## 6.2 Evaluation methodology for coverage impact + +Coverage recovery evaluation is based on link budget evaluations. + +The evaluation methodology and assumptions in the Rel-17 RedCap SI [5] are reused by default, with the revision or addition described below. + +The channels and messages used in link budget evaluations primarily include PBCH, PDCCH CSS, and SIB1. Sourcing companies can additionally provide evaluation results of other channels and messages such as PDCCH USS, PRACH, Msg2, Msg3, Msg4, PDSCH, PUCCH and PUSCH. + +The impact of small form factor can be considered for all the uplink and downlink channels. To reflect such an impact, a 3dB loss of antenna gain can be optionally included in link budget calculation for the FR1 bands by sourcing companies. + +The assumptions in the Rel-17 RedCap SI regarding link budget templates and antenna array gain are reused [5]. Furthermore, the Rel-17 RedCap SI assumptions on gNB antenna configuration, # gNB Tx and Rx chains, channel model and delay spread are reused as shown in Table 6.2-1. + +**Table 6.2-1: Assumptions used for coverage impact evaluation** + +| Parameters | FR1 values | +|-----------------------------------|---------------------------------------------------------------------------| +| Deployment scenario and frequency | Urban: 2.6GHz (TDD), 4GHz (TDD, optional)
Rural: (FDD) | +| Frame structure for TDD | DDDDDDDSUU (S: 6D:4G:4U) for 2.6GHz
DDDSUDDSUU (S: 10D:2G:2U) for 4GHz | +| Channel model | TDL-C | +| Delay spread | 300ns | +| UE velocity | 3 km/h | +| Antenna correlation | Low | +| # gNB Tx chains | 2 or 4 | +| # gNB Rx chains | 2 or 4 | + +For coverage evaluation, the assumptions for reference NR UE, reference Rel-17 RedCap UE, and the potential Rel-18 UE are shown in Tables 6.2-2, 6.2-3 and 6.2-4, respectively. + +**Table 6.2-2: Assumptions for reference NR UE** + +| Parameters | FR1 values | +|----------------|-------------------------------------------------------------------------------| +| # UE Tx chains | 1 | +| # UE Rx chains | Urban: 4 and Rural: 2 | +| UE bandwidth | Urban: 100 MHz (273 PRBs, 30 kHz SCS)
Rural: 20 MHz (106 PRBs, 15 kHz SCS) | + +**Table 6.2-3: Assumptions for reference Rel-17 RedCap UE** + +| Parameters | FR1 values | +|----------------|-----------------------------------------------------------------------------| +| # UE Tx chains | 1 | +| # UE Rx chains | 1 | +| UE bandwidth | Urban: 20 MHz (51 PRBs, 30 kHz SCS)
Rural: 20 MHz (106 PRBs, 15 kHz SCS) | + +**Table 6.2-4: Assumptions for the potential Rel-18 UE** + +| Parameters | FR1 values | +|----------------|------------------------------------------------------------------------------------------------| +| # UE Tx chains | 1 | +| # UE Rx chains | 1 | +| UE bandwidth | Urban: 5 MHz (11 PRBs or 12 PRBs (optional), 30 kHz SCS)
Rural: 5 MHz (25 PRBs, 15 kHz SCS) | + +The assumptions for channel specific parameters are also based on reusing the Rel-17 RedCap SI agreements [5], with the revision or addition described below. + +For PBCH, the assumptions listed in Table A.1-8 from TR 38.830 [6] were adopted for reference NR UE, reference Rel-17 RedCap UE, and the potential Rel-18 UE. + +For SIB1, the assumptions listed in Table 6.2-5 were adopted for reference NR UE, and reference Rel-17 RedCap UE. For the potential Rel-18 UE, the assumptions listed in Table 6.2-6 were adopted. + +**Table 6.2-5: Assumptions for SIB1 for reference NR UE and reference Rel-17 RedCap UE** + +| Parameters | Values | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRBs/TBS/MCS | TBS is 1256 bits. SIB1 bandwidth is larger than 5MHz, e.g. 48PRBs. Companies to report the used number of PRBs, corresponding MCS, and whether interleaving mapping is assumed. | + +**Table 6.2-6: Assumptions for SIB1 for the potential Rel-18 UE** + +| Parameters | Values | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRBs/TBS/MCS | TBS is 1256 bits. Other TBS are not precluded.
For PRB numbers, two options are assumed:
  • - Option 1: SIB1 bandwidth is larger than 5MHz, e.g. 48PRBs.
  • - Option 2: SIB1 bandwidth is within 5MHz.
Companies to report the used number of PRBs, corresponding MCS, and whether interleaving mapping is assumed. | + +For PDCCH common search space (PDCCH CSS), the assumptions listed in Table 6.2-7 were adopted for reference NR UE and reference Rel-17 RedCap UE. + +**Table 6.2-7: Assumptions for PDCCH Common Search Space (PDCCH CSS) for reference NR UE and reference Rel-17 RedCap UE** + +| Parameters | Values | +|-------------------------------------------------------|------------------------------------------------------| +| DCI format and payload size | DCI format 1_0 with payload of 40bits | +| CORESET size and aggregation level (AL) configuration | The CORESET size is 2 symbols and 48 PRBs. AL is 16. | + +For PDCCH common search space (PDCCH CSS), the assumptions listed in Table 6.2-8 were adopted for the potential Rel-18 UE. + +**Table 6.2-8: Assumptions for PDCCH Common Search Space (PDCCH CSS) for the potential Rel-18 UE** + +| Parameters | Values | +|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DCI format and payload size | DCI format 1_0 with payload of 40bits | +| CORESET size and aggregation level (AL) configuration |

For 15kHz SCS, the following options are assumed.

  • - Option 1: The CORESET size is 2 symbols and 48 PRBs. AL is 16.
  • - Option 2: The CORESET size is 3 symbols and 24 PRBs. AL is 8.

For 30kHz SCS, the following options are assumed.

  • - Option 1: The CORESET size is 2 symbols and 24 PRBs. AL is 8.
  • - Option 2: The CORESET size is 3 symbols and 6 PRBs. AL is 2.
  • - Option 3: The CORESET size is 3 symbols and 12 PRBs. AL is 4.

Other configurations can be optionally evaluated and reported by companies.

| + +For Msg2, the assumptions for reference NR UE, reference Rel-17 RedCap UE, and the potential Rel-18 UE listed in Table 6.2-9 were adopted. + +**Table 6.2-9: Assumptions for Msg2** + +| Parameters | Values | +|--------------|-----------------------------------------------------------------------------------| +| PRBs/TBS/MCS | TBS is 72bits. Companies to report the used number of PRBs and corresponding MCS. | + +For Msg4, the assumptions for reference NR UE, reference Rel-17 RedCap UE, and the potential Rel-18 UE listed in Table 6.2-10 were adopted. + +**Table 6.2-10: Assumptions for Msg4** + +| Parameters | Values | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRBs/TBS/MCS | TBS is 1040bits. Companies to report the used number of PRBs and corresponding MCS.
A smaller TBS can be optionally evaluated and reported by companies. | + +For PRACH, the assumptions for reference NR UE, reference Rel-17 RedCap UE, and the potential Rel-18 UE listed in Table 6.2-11 were adopted. + +**Table 6.2-11: Assumptions for PRACH** + +| Parameters | Values | +|--------------|-------------------------------------------------------------------------------------------------------------| +| PRACH format | Urban: Format B4
Rural: Format 0

Format C2 can be optionally evaluated and reported by companies. | + +The target data rates for the potential Rel-18 UEs are: + +- FR1 Rural: 250 kbps on DL and 25 kbps in UL +- FR1 Urban: 500 kbps on DL and 250 kbps in UL +- Note: The target data rates are the scaled value in the Rel-17 RedCap SI by a factor of 0.25 + +The TBS, PRB, and MCS of PDSCH and PUSCH for the potential Rel-18 UE are based on the agreed target data rates or message sizes and reported by sourcing companies. + +For all channels affected by reduced UE complexity including prioritized broadcast channels and optionally evaluated channels, the following methodology is used to evaluate the coverage impact in terms of coverage margins: + +- Step 1: Obtain the link budget performance of the channel based on link budget evaluation +- Step 2: Obtain the target performance requirement for the potential Rel-18 UE within a deployment scenario +- Step 3: Find the coverage margin for the channel by comparing the link budget performance with the target performance requirement. + +For step 2, the study applied the following option for determining the target performance for coverage impact evaluation in terms of coverage margins. + +- The target performance requirement for each channel is identified by the link budget of the bottleneck channel for the reference UE within the same deployment scenario. The "bottleneck channel" is the physical channel that has the lowest MIL value. The reference UE is an NR UE with mandatory features only as defined in Clause 6.1 of [5]. + +In this coverage impact evaluation in terms of coverage margins, a single coverage target based on the same bottleneck channel is used for all channels including the prioritized broadcast channels and optionally evaluated channels of the potential Rel-18 UE. Each sourcing company reports a sourcing-company-specific coverage margin for each channel by comparing the link budget of the channel with the link budget of the bottleneck channel for the reference UE. + +A representative value of the coverage margin for a channel is derived by taking the mean value (in dB domain) from the coverage margins from all sourcing companies, including both negative and non-negative values based on the following adjustments. + +- Excluding the highest & the lowest values when the number of samples is more than 3. +- If the number of samples is less than 4 for a channel in a scenario, no representative value is provided. + +The representative value of a channel is used for identifying whether the channel has coverage margin compared to the bottleneck channel of the reference NR UE. + +In Step 2 in the above methodology for determining coverage margins, a sourcing company might not be able to identify a bottleneck channel for the reference NR UE and the corresponding MIL link budget if it had not evaluated all channels for the reference NR UE, especially if it had not evaluated uplink channels since uplink channels were often the bottleneck channels for the reference NR UE. For such a sourcing company, a bottleneck channel and the corresponding link budget for the reference NR UE can be determined based on evaluation results of the identified bottleneck channels and MIL values from the Rel-17 RedCap SI in [5] for a scenario. Specifically, for an evaluated scenario, a bottleneck channel is determined by the one identified by most sourcing companies and its corresponding MIL value is derived by taking the mean value (in dB domain) from the MIL values from all sourcing companies after excluding the highest & the lowest values. For the evaluated scenarios, the following tables from Rel-17 RedCap SI in [5] are used: + +- For Urban scenario at 2.6GHz, Table 9.1.1-1 in [5] is used for determining a bottleneck channel and MIL value for the reference NR UE by such a sourcing company. +- For Rural scenario at 0.7GHz, Table 9.1.2-1 in [5] is used. +- For Urban scenario at 4 GHz, Table 9.1.3-1 in [5] is used. + +For each table of coverage margins of evaluated channels in a deployment scenario shown in Clause 8.2.1 through Clause 8.2.3, the rows of the table are composed of sourcing companies' names, representative value 1, number of samples 1, representative value 2, and number of samples 2. For an evaluated channel in the scenario, + +- the representative value 1 is derived from the coverage margins only from sourcing companies who had provided uplink coverage evaluation results for the reference NR UE +- the number of samples 1 is the total number of sourcing companies that had provided uplink coverage evaluation results for the reference NR UE +- the representative value 2 is derived from the coverage margins from all sourcing companies regardless of whether or one had provided uplink coverage evaluation results for the reference NR UE +- the number of samples 2 is the total number of all sourcing companies + +Besides comparing link budgets of all evaluated channels to that of the bottleneck channel for the reference NR UE and deriving coverage margins for all channels, comparisons of the coverage differences between the potential Rel-18 UE and the reference NR UE in addition to comparisons of the coverage differences between the potential Rel-18 UE and the reference Rel-17 RedCap UE were carried out for the broadcast channels including PBCH, PDCCH CSS, and SIB1 in Urban scenario at 2.6 GHz. For PDCCH CSS and SIB1, the comparisons were also carried out for Rural scenario at 0.7 GHz. Detailed comparisons and assumptions are provided in Clause 8.2.1 and Clause 8.2.2 for Urban at 2.6 GHz and Rural at 0.7 GHz, respectively. + +# --- 7 UE complexity reduction features + +## 7.1 Introduction to UE complexity reduction features + +The following UE complexity reduction techniques have been studied: + +- Further UE bandwidth reduction ("BW" for short) +- Further UE peak rate reduction ("PR" for short) +- Relaxed UE processing timeline ("PT" for short) + +The evaluation results for each one of the studied individual UE complexity reduction techniques are captured in clauses 7.2 through 7.4, respectively. For relaxed UE processing timeline, analysis is provided in clause 7.4, while complexity evaluations are provided only in combination with other techniques in clause 7.5 where the properties of combinations of different individual UE complexity reduction techniques are described. The evaluation of the potential coverage impacts is described in clause 8. Recommendations based on the evaluations are captured in clause 9. + +## 7.2 Further UE bandwidth reduction + +### 7.2.1 Description of feature + +In the study, the main UE bandwidth reduction options considered for FR1 are as follows: + +- Option BW1: Both RF and BB bandwidths are 5 MHz for UL and DL. +- Option BW2 (optionally considered for evaluations): 5 MHz BB bandwidth for all signals and channels with 20 MHz RF bandwidth for UL and DL. + +- Option BW3: 5 MHz BB bandwidth only for PDSCH (for both unicast and broadcast) and PUSCH with 20 MHz RF bandwidth for UL and DL. The other physical channels and signals are still allowed to use a BWP up to the 20 MHz maximum UE RF+BB bandwidth. + +For the above bandwidth reduction options, the following aspects are considered: + +- The resource allocation spans a bandwidth of maximum 5 MHz. +- The same option is used for UL and DL. +- The same option is used for idle/inactive and connected mode. +- Note: As part of study of above options, it is not precluded to indicate that an observation is relevant for UL only or DL only. +- For 15 kHz SCS, 25 contiguous RBs are assumed to fit within the 5 MHz. +- For 30 kHz SCS, 11 contiguous RBs are assumed to fit within the 5 MHz. +- Note: For 30 kHz SCS, 12 contiguous RBs are also optionally studied. + +The evaluation results for each one of the studied individual UE complexity reduction techniques are captured in clauses 7.2 through 7.4, respectively. The properties of combinations of different individual UE complexity reduction techniques are described in clause 7.5. Recommendations based on the evaluations are captured in clause 9. + +### 7.2.2 Analysis of UE complexity reduction + +For BW1, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: ADC/DAC +- Baseband: FFT/IFFT +- Baseband: Post-FFT data buffering +- Baseband: Receiver processing block +- Baseband: LDPC decoding +- Baseband: HARQ buffer +- Baseband: DL control processing & decoder +- Baseband: UL processing block + +For BW2, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: Post-FFT data buffering +- Baseband: Receiver processing block +- Baseband: LDPC decoding +- Baseband: HARQ buffer +- Baseband: DL control processing & decoder +- Baseband: UL processing block + +For BW3, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: Post-FFT data buffering +- Baseband: Receiver processing block +- Baseband: LDPC decoding + +- Baseband: HARQ buffer +- Baseband: UL processing block + +Note 1: BW3 may have different degrees of impacts on the post-FFT data buffering depending on the scheduling aspects (cross-slot scheduling, RF retuning, etc.). + +Note 2: For BW2, some sources have indicated that the complexity of the ADC/DAC and FFT/IFFT blocks might also be reduced. + +Note 3: For BW1, one source shows complexity reduction for RF filters and one source shows complexity reduction for MIMO specific processing block. + +Note 4: BW1 and BW2 may have different degrees of impacts on the downlink control processing and decoder depending on the CCE and BD complexity reduction. + +For the UE bandwidth reduction options BW1, BW2, and BW3, the complexity reduction is mainly in the BB part, and although there may be a possibility to reduce RF complexity, there is no significant complexity reduction in the RF part. + +The tables below show the average value of the initial complexity evaluation results captured in [7]. Specifically, results are provided for Rel-17 RedCap and potential Rel-18 RedCap cases with FD-FDD 1Rx, TDD 1Rx, HD-FDD 1Rx, FD-FDD 2Rx, TDD 2Rx, and HD-FDD 2Rx. + +Note that the reference Rel-15 NR UE has the following features: + +- FDD: 100 MHz, 2 Rx, 2 layers, DL 256QAM, FD-FDD +- TDD: 100 MHz, 4 Rx, 4 layers, DL 256QAM + +**Table 7.2.2-1: Average UE complexity reduction achieved by BW reduction options for FD-FDD 1Rx** + +| Reduced UE bandwidth | Rel-15 reference | Rel-17 RedCap | BW1 | BW2 | BW3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.12% | 24.02% | 24.64% | 24.09% | +| RF: Filters | 10% | 5.06% | 4.72% | 5.12% | 5.06% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 23.76% | 23.52% | 24.30% | 23.76% | +| RF: Duplexer / Switch | 20% | 19.52% | 19.52% | 19.57% | 19.52% | +| RF: Total | 100% | 72.46% | 71.78% | 73.63% | 72.43% | +| BB: ADC / DAC | 10% | 1.30% | 0.50% | 0.99% | 1.27% | +| BB: FFT/IFFT | 4% | 0.67% | 0.21% | 0.45% | 0.65% | +| BB: Post-FFT data buffering | 10% | 1.05% | 0.36% | 0.46% | 0.67% | +| BB: Receiver processing block | 24% | 4.42% | 2.00% | 1.86% | 2.07% | +| BB: LDPC decoding | 10% | 1.29% | 0.51% | 0.50% | 0.51% | +| BB: HARQ buffer | 14% | 1.46% | 0.45% | 0.45% | 0.45% | +| BB: DL control processing & decoder | 5% | 4.73% | 3.98% | 3.95% | 4.52% | +| BB: Synchronization / cell search block | 9% | 4.61% | 4.55% | 4.59% | 4.58% | +| BB: UL processing block | 5% | 2.69% | 1.55% | 1.54% | 1.69% | +| BB: MIMO specific processing blocks | 9% | 4.04% | 3.77% | 3.85% | 3.91% | +| BB: Total | 100% | 26.26% | 17.88% | 18.65% | 20.31% | +| RF+BB: Total | 100% | 44.74% | 39.44% | 40.65% | 41.15% | + +**Table 7.2.2-2: Average UE complexity reduction achieved by BW reduction options for TDD 1Rx** + +| Reduced UE bandwidth | Rel-15 reference | Rel-17 RedCap | BW1 | BW2 | BW3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.08% | 23.97% | 24.56% | 24.05% | +| RF: Filters | 15% | 3.94% | 3.86% | 4.08% | 3.94% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 55% | 19.05% | 18.78% | 19.98% | 19.05% | +| RF: Duplexer / Switch | 5% | 4.97% | 4.97% | 4.98% | 4.97% | +| RF: Total | 100% | 52.04% | 51.58% | 53.59% | 52.01% | +| BB: ADC / DAC | 9% | 0.76% | 0.30% | 0.57% | 0.73% | + +| | | | | | | +|-----------------------------------------|-------------|---------------|---------------|---------------|---------------| +| BB: FFT/IFFT | 4% | 0.40% | 0.14% | 0.27% | 0.38% | +| BB: Post-FFT data buffering | 10% | 0.59% | 0.22% | 0.28% | 0.36% | +| BB: Receiver processing block | 29% | 3.21% | 1.54% | 1.48% | 1.56% | +| BB: LDPC decoding | 9% | 0.79% | 0.33% | 0.34% | 0.33% | +| BB: HARQ buffer | 12% | 0.79% | 0.40% | 0.23% | 0.40% | +| BB: DL control processing & decoder | 4% | 3.68% | 3.15% | 3.19% | 3.55% | +| BB: Synchronization / cell search block | 9% | 2.49% | 2.44% | 2.45% | 2.45% | +| BB: UL processing block | 5% | 2.69% | 1.54% | 1.50% | 1.70% | +| BB: MIMO specific processing blocks | 9% | 2.27% | 2.04% | 2.07% | 2.21% | +| BB: Total | 100% | 17.66% | 12.08% | 12.40% | 13.68% | +| RF+BB: Total | 100% | 31.41% | 27.88% | 28.88% | 29.01% | + +Table 7.2.2-3: Average UE complexity reduction achieved by BW reduction options for HD-FDD 1Rx + +| Reduced UE bandwidth | Rel-15 reference | Rel-17 RedCap | BW1 | BW2 | BW3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.50% | 24.50% | 24.50% | 24.50% | +| RF: Filters | 10% | 5.17% | 4.64% | 5.17% | 5.17% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 24.46% | 24.06% | 24.46% | 24.46% | +| RF: Duplexer / Switch | 20% | 3.68% | 3.68% | 3.68% | 3.68% | +| RF: Total | 100% | 57.81% | 56.87% | 57.81% | 57.81% | +| BB: ADC / DAC | 10% | 1.25% | 0.54% | 1.03% | 1.26% | +| BB: FFT/IFFT | 4% | 0.71% | 0.25% | 0.44% | 0.72% | +| BB: Post-FFT data buffering | 10% | 1.10% | 0.42% | 0.50% | 0.66% | +| BB: Receiver processing block | 24% | 4.22% | 1.92% | 1.92% | 2.04% | +| BB: LDPC decoding | 10% | 1.41% | 0.58% | 0.58% | 0.58% | +| BB: HARQ buffer | 14% | 1.61% | 0.52% | 0.52% | 0.52% | +| BB: DL control processing & decoder | 5% | 4.70% | 3.84% | 3.84% | 4.49% | +| BB: Synchronization / cell search block | 9% | 4.68% | 4.63% | 4.63% | 4.68% | +| BB: UL processing block | 5% | 3.10% | 1.79% | 1.78% | 1.91% | +| BB: MIMO specific processing blocks | 9% | 3.81% | 3.56% | 3.58% | 3.81% | +| BB: Total | 100% | 26.58% | 18.05% | 18.82% | 20.70% | +| RF+BB: Total | 100% | 39.07% | 33.58% | 34.41% | 35.60% | + +Table 7.2.2-4: Average UE complexity reduction achieved by BW reduction options for FD-FDD 2Rx + +| Reduced UE bandwidth | Rel-15 reference | Rel-17 RedCap | BW1 | BW2 | BW3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.87% | 24.87% | 25.00% | 24.87% | +| RF: Filters | 10% | 10.00% | 9.02% | 9.49% | 9.56% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 42.47% | 41.51% | 42.63% | 42.47% | +| RF: Duplexer / Switch | 20% | 20.00% | 20.00% | 20.00% | 20.00% | +| RF: Total | 100% | 97.33% | 95.40% | 97.12% | 96.90% | +| BB: ADC / DAC | 10% | 2.12% | 1.03% | 1.52% | 2.13% | +| BB: FFT/IFFT | 4% | 1.25% | 0.47% | 0.86% | 1.28% | +| BB: Post-FFT data buffering | 10% | 2.17% | 0.84% | 1.11% | 1.52% | +| BB: Receiver processing block | 24% | 8.97% | 4.47% | 4.78% | 4.60% | +| BB: LDPC decoding | 10% | 2.71% | 1.18% | 1.19% | 1.18% | +| BB: HARQ buffer | 14% | 2.53% | 0.97% | 0.91% | 0.97% | +| BB: DL control processing & decoder | 5% | 4.93% | 4.13% | 4.25% | 4.93% | +| BB: Synchronization / cell search block | 9% | 8.61% | 8.47% | 8.38% | 8.61% | +| BB: UL processing block | 5% | 3.20% | 1.99% | 2.04% | 2.08% | +| BB: MIMO specific processing blocks | 9% | 7.33% | 6.01% | 6.48% | 7.33% | +| BB: Total | 100% | 43.84% | 29.57% | 31.52% | 34.65% | +| RF+BB: Total | 100% | 65.24% | 55.90% | 57.76% | 59.55% | + +**Table 7.2.2-5: Average UE complexity reduction achieved by BW reduction options for TDD 2Rx** + +| Reduced UE bandwidth | Rel-15 reference | Rel-17 RedCap | BW1 | BW2 | BW3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.44% | 24.44% | 25.00% | 24.44% | +| RF: Filters | 15% | 7.69% | 7.11% | 7.75% | 7.69% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 55% | 33.61% | 31.83% | 33.90% | 33.14% | +| RF: Duplexer / Switch | 5% | 4.99% | 4.99% | 5.00% | 4.99% | +| RF: Total | 100% | 70.72% | 68.36% | 71.65% | 70.25% | +| BB: ADC / DAC | 9% | 1.13% | 0.56% | 0.89% | 1.13% | +| BB: FFT/IFFT | 4% | 0.66% | 0.25% | 0.52% | 0.70% | +| BB: Post-FFT data buffering | 10% | 1.17% | 0.47% | 0.52% | 0.83% | +| BB: Receiver processing block | 29% | 5.82% | 3.08% | 3.34% | 3.15% | +| BB: LDPC decoding | 9% | 1.33% | 0.64% | 0.67% | 0.64% | +| BB: HARQ buffer | 12% | 1.16% | 0.44% | 0.43% | 0.44% | +| BB: DL control processing & decoder | 4% | 3.75% | 3.10% | 3.13% | 3.75% | +| BB: Synchronization / cell search block | 9% | 4.50% | 4.56% | 4.50% | 4.63% | +| BB: UL processing block | 5% | 2.83% | 1.76% | 1.82% | 1.83% | +| BB: MIMO specific processing blocks | 9% | 3.82% | 3.05% | 3.26% | 3.75% | +| BB: Total | 100% | 26.17% | 17.90% | 19.09% | 20.85% | +| RF+BB: Total | 100% | 43.99% | 38.08% | 40.12% | 40.61% | + +**Table 7.2.2-6: Average UE complexity reduction achieved by BW reduction options for HD-FDD 2Rx** + +| Reduced UE bandwidth | Rel-15 reference | Rel-17 RedCap | BW1 | BW2 | BW3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 25.00% | 25.00% | 25.00% | 25.00% | +| RF: Filters | 10% | 10.00% | 9.03% | 10.00% | 10.00% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 43.04% | 41.51% | 43.04% | 43.04% | +| RF: Duplexer / Switch | 20% | 4.33% | 4.33% | 4.33% | 4.33% | +| RF: Total | 100% | 82.38% | 79.88% | 82.38% | 82.38% | +| BB: ADC / DAC | 10% | 2.06% | 1.09% | 1.52% | 2.07% | +| BB: FFT/IFFT | 4% | 1.15% | 0.49% | 0.73% | 1.18% | +| BB: Post-FFT data buffering | 10% | 2.14% | 0.90% | 1.10% | 1.40% | +| BB: Receiver processing block | 24% | 9.01% | 4.78% | 4.78% | 4.78% | +| BB: LDPC decoding | 10% | 2.69% | 1.19% | 1.19% | 1.19% | +| BB: HARQ buffer | 14% | 2.41% | 0.91% | 0.91% | 0.91% | +| BB: DL control processing & decoder | 5% | 5.00% | 4.25% | 4.25% | 5.00% | +| BB: Synchronization / cell search block | 9% | 8.55% | 8.38% | 8.38% | 8.55% | +| BB: UL processing block | 5% | 3.17% | 2.04% | 2.04% | 2.04% | +| BB: MIMO specific processing blocks | 9% | 7.23% | 6.48% | 6.48% | 7.23% | +| BB: Total | 100% | 43.39% | 30.52% | 31.39% | 34.36% | +| RF+BB: Total | 100% | 58.99% | 50.26% | 51.79% | 53.57% | + +For comparison, the average complexity reduction estimates from [7] for different BW reduction options compared to the corresponding Rel-17 RedCap baselines are presented in the table below. + +**Table 7.2.2-7: Average UE complexity reduction achieved by BW reduction options compared to corresponding Rel-17 baselines** + +| Option | FD-FDD 1Rx | TDD 1Rx | HD-FDD 1Rx | FD-FDD 2Rx | TDD 2Rx | HD-FDD 2Rx | +|--------|------------|---------|------------|------------|---------|------------| +| BW1 | 11.85% | 11.25% | 14.06% | 14.31% | 13.42% | 14.79% | +| BW2 | 9.15% | 8.08% | 11.92% | 11.46% | 8.81% | 12.21% | +| BW3 | 8.02% | 7.66% | 8.90% | 8.72% | 7.68% | 9.19% | + +### 7.2.3 Analysis of performance impacts + +#### Peak data rate: + +Reducing the UE bandwidth leads to peak data rate reduction, but the reduced peak data rate can still fulfill the targeted data rate in Rel-18. In TDD, with 5 MHz UE bandwidth (for all BW options), the achievable peak data rate for UL or DL can be less than 10 Mbps depending on the TDD pattern. + +#### Coverage: + +For all BW options, there is link performance impact for SIB1 PDSCH if the bandwidth allocation for SIB1 PDSCH exceeds 5 MHz. However, in all scenarios except for 4 GHz with 24 dBm PSD, there is no or negligible coverage impact for SIB1 PDSCH even if the bandwidth allocation for SIB1 PDSCH exceeds 5 MHz. + +Furthermore, for BW1/BW2, there is link performance degradation for PDCCH due to reduced maximum AL in a 5-MHz CORESET, and for PBCH (30 kHz SCS). + +For a more detailed description of the coverage impacts, see clause 8.2.4. + +#### Latency: + +The impact of further UE bandwidth reduction on the latency is insignificant, and 5 MHz UE bandwidth (for all BW options) can sufficiently fulfil relaxed latency requirements of RedCap use cases. + +### 7.2.4 Analysis of network deployment and coexistence impacts + +If the common channels such as SIB1, OSI, RAR, MSG3 etc. are scheduled within 5MHz, then none of the UE bandwidth reduction options (BW1, BW2, BW3) have coexistence issues with legacy UEs, but otherwise there are some coexistence issues with legacy UEs. + +BW1 and BW2 are expected to have the largest coexistence impacts among the evaluated options, whereas the expected coexistence impacts for BW3 are smaller. BW1 and BW2 can have coexistence impacts in terms of support of SSB/CORESET #0 configurations (especially 30 kHz SCS) and limitations of RACH configurations and PRACH sharing procedure. Furthermore, BW1 has impact on SSB transmissions (e.g., NCD-SSB overhead) and BWP operation. + +Early indication (through Msg1/MsgA) might be needed for all BW options. + +### 7.2.5 Analysis of specification impacts + +BW1 and BW2 can have significant specification impacts, considering the impacts on initial access, random access, and SSB/CORESET #0 configurations (especially 30 kHz SCS). For BW1, the specification impacts may also include SSB presence requirements. BW3 has smaller specification impacts compared to BW1 and BW2. + +## 7.3 Further UE peak rate reduction + +### 7.3.1 Description of feature + +In the study, the main UE peak rate reduction options considered for FR1 are as follows: + +- Option PR1: Relaxation of the constraint $(v_{Layers}^{(j)} \cdot Q_m^{(j)} \cdot f^{(j)} \geq 4)$ for peak data rate reduction. + - The relaxed constraint is 1 (instead of 4). + - The parameters $(v_{Layers}^{(1)}, Q_m^{(1)}, f^{(1)})$ can be as in Rel-17 RedCap [4]. +- Option PR2: Restriction of maximum TBS for PDSCH and PUSCH. + - For 15 kHz SCS, the maximum TBS is 10000 bits per TB and per slot. + - For 30 kHz SCS, the maximum TBS is 5000 bits per TB and per slot. + +- Option PR3: Restriction of maximum number of PRBs for PDSCH and PUSCH. + - For 15 kHz SCS, the maximum number of RBs is 25. + - For 30 kHz SCS, the maximum number of RBs is 11. + - The restricted number of PRBs in Option PR3 is a hardcoded limit. + +For the above peak rate reduction options, the following aspects are considered: + +- The studied peak rate reduction applies to both UE-specific (unicast) and common (broadcast) channels. +- The resource allocation spans a bandwidth of maximum 20 MHz (maximum UE channel bandwidth). +- The same option is used for UL and DL. +- The same option is used for idle/inactive and connected mode. +- Note: As part of study of above options, it is not precluded to indicate that an observation is relevant for UL only or DL only. + +### 7.3.2 Analysis of UE complexity reduction + +For PR1 and PR2, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: LDPC decoding +- Baseband: HARQ buffer +- Baseband: UL processing block + +For PR3, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: Receiver processing block +- Baseband: LDPC decoding +- Baseband: HARQ buffer +- Baseband: UL processing block + +The tables below show the average value of the initial complexity evaluation results captured in [7]. Specifically, results are provided for Rel-17 RedCap and potential Rel-18 RedCap cases with FD-FDD 1Rx, TDD 1Rx, HD-FDD 1Rx, FD-FDD 2Rx, TDD 2Rx, and HD-FDD 2Rx. + +Note that the reference Rel-15 NR UE has the following features: + +- FDD: 100 MHz, 2 Rx, 2 layers, DL 256QAM, FD-FDD +- TDD: 100 MHz, 4 Rx, 4 layers, DL 256QAM + +**Table 7.3.2-1: Average UE complexity reduction achieved by PR reduction options for FD-FDD 1Rx** + +| Reduced UE peak rate | Rel-15 reference | Rel-17 RedCap | PR1 | PR2 | PR3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.12% | 24.12% | 24.12% | 24.12% | +| RF: Filters | 10% | 5.06% | 5.06% | 5.06% | 5.06% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 23.76% | 23.76% | 23.76% | 23.76% | +| RF: Duplexer / Switch | 20% | 19.52% | 19.52% | 19.52% | 19.52% | +| RF: Total | 100% | 72.46% | 72.46% | 72.46% | 72.46% | +| BB: ADC / DAC | 10% | 1.30% | 1.26% | 1.26% | 1.26% | +| BB: FFT/IFFT | 4% | 0.67% | 0.65% | 0.65% | 0.65% | +| BB: Post-FFT data buffering | 10% | 1.05% | 1.07% | 1.07% | 1.01% | +| BB: Receiver processing block | 24% | 4.42% | 4.21% | 4.21% | 2.46% | + +| | | | | | | +|-----------------------------------------|-------------|---------------|---------------|---------------|---------------| +| BB: LDPC decoding | 10% | 1.29% | 0.45% | 0.44% | 0.49% | +| BB: HARQ buffer | 14% | 1.46% | 0.43% | 0.41% | 0.43% | +| BB: DL control processing & decoder | 5% | 4.73% | 4.67% | 4.67% | 4.55% | +| BB: Synchronization / cell search block | 9% | 4.61% | 4.58% | 4.58% | 4.58% | +| BB: UL processing block | 5% | 2.69% | 1.94% | 1.89% | 1.66% | +| BB: MIMO specific processing blocks | 9% | 4.04% | 3.91% | 3.91% | 3.91% | +| BB: Total | 100% | 26.26% | 23.18% | 23.09% | 21.00% | +| RF+BB: Total | 100% | 44.74% | 42.89% | 42.84% | 41.58% | + +Table 7.3.2-2: Average UE complexity reduction achieved by PR reduction options for TDD 1Rx + +| Reduced UE peak rate | Rel-15 reference | Rel-17 RedCap | PR1 | PR2 | PR3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.08% | 24.08% | 24.08% | 24.08% | +| RF: Filters | 15% | 3.94% | 3.94% | 3.94% | 3.94% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 55% | 19.05% | 19.05% | 19.05% | 19.05% | +| RF: Duplexer / Switch | 5% | 4.97% | 4.97% | 4.97% | 4.97% | +| RF: Total | 100% | 52.04% | 52.04% | 52.04% | 52.04% | +| BB: ADC / DAC | 9% | 0.76% | 0.73% | 0.73% | 0.73% | +| BB: FFT/IFFT | 4% | 0.40% | 0.39% | 0.39% | 0.39% | +| BB: Post-FFT data buffering | 10% | 0.59% | 0.57% | 0.57% | 0.56% | +| BB: Receiver processing block | 29% | 3.21% | 3.03% | 3.03% | 1.84% | +| BB: LDPC decoding | 9% | 0.79% | 0.30% | 0.29% | 0.32% | +| BB: HARQ buffer | 12% | 0.79% | 0.39% | 0.38% | 0.39% | +| BB: DL control processing & decoder | 4% | 3.68% | 3.58% | 3.58% | 3.58% | +| BB: Synchronization / cell search block | 9% | 2.49% | 2.45% | 2.45% | 2.45% | +| BB: UL processing block | 5% | 2.69% | 1.91% | 1.85% | 1.66% | +| BB: MIMO specific processing blocks | 9% | 2.27% | 2.21% | 2.21% | 2.22% | +| BB: Total | 100% | 17.66% | 15.56% | 15.49% | 14.14% | +| RF+BB: Total | 100% | 31.41% | 30.15% | 30.11% | 29.30% | + +Table 7.3.2-3: Average UE complexity reduction achieved by PR reduction options for HD-FDD 1Rx + +| Reduced UE peak rate | Rel-15 reference | Rel-17 RedCap | PR1 | PR2 | PR3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.50% | 24.50% | 24.50% | 24.50% | +| RF: Filters | 10% | 5.17% | 5.17% | 5.17% | 5.17% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 24.46% | 24.46% | 24.46% | 24.46% | +| RF: Duplexer / Switch | 20% | 3.68% | 3.68% | 3.68% | 3.68% | +| RF: Total | 100% | 57.81% | 57.81% | 57.81% | 57.81% | +| BB: ADC / DAC | 10% | 1.25% | 1.25% | 1.25% | 1.25% | +| BB: FFT/IFFT | 4% | 0.71% | 0.71% | 0.71% | 0.71% | +| BB: Post-FFT data buffering | 10% | 1.10% | 1.10% | 1.10% | 1.04% | +| BB: Receiver processing block | 24% | 4.22% | 4.05% | 4.04% | 2.37% | +| BB: LDPC decoding | 10% | 1.41% | 0.50% | 0.49% | 0.56% | +| BB: HARQ buffer | 14% | 1.61% | 0.48% | 0.46% | 0.49% | +| BB: DL control processing & decoder | 5% | 4.70% | 4.70% | 4.70% | 4.49% | +| BB: Synchronization / cell search block | 9% | 4.68% | 4.68% | 4.68% | 4.68% | +| BB: UL processing block | 5% | 3.10% | 2.07% | 2.00% | 1.77% | +| BB: MIMO specific processing blocks | 9% | 3.81% | 3.81% | 3.81% | 3.81% | +| BB: Total | 100% | 26.58% | 23.33% | 23.24% | 21.20% | +| RF+BB: Total | 100% | 39.07% | 37.12% | 37.06% | 35.90% | + +Table 7.3.2-4: Average UE complexity reduction achieved by PR reduction options for FD-FDD 2Rx + +| Reduced UE peak rate | Rel-15 reference | Rel-17 RedCap | PR1 | PR2 | PR3 | +|-----------------------------------------------------------|------------------|---------------|--------|--------|--------| +| RF: Power amplifier | 25% | 24.87% | 24.87% | 24.87% | 24.87% | +| RF: Filters | 10% | 10.00% | 9.56% | 9.29% | 9.29% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 42.47% | 42.47% | 40.32% | 40.32% | + +| | | | | | | +|-----------------------------------------|-------------|---------------|---------------|---------------|---------------| +| oscillator) | | | | | | +| RF: Duplexer / Switch | 20% | 20.00% | 20.00% | 20.00% | 20.00% | +| RF: Total | 100% | 97.33% | 96.90% | 94.48% | 94.48% | +| BB: ADC / DAC | 10% | 2.12% | 2.05% | 2.05% | 2.05% | +| BB: FFT/IFFT | 4% | 1.25% | 1.20% | 1.20% | 1.20% | +| BB: Post-FFT data buffering | 10% | 2.17% | 2.11% | 2.11% | 2.08% | +| BB: Receiver processing block | 24% | 8.97% | 8.68% | 8.68% | 5.31% | +| BB: LDPC decoding | 10% | 2.71% | 0.93% | 0.90% | 1.08% | +| BB: HARQ buffer | 14% | 2.53% | 0.84% | 0.80% | 0.88% | +| BB: DL control processing & decoder | 5% | 4.93% | 4.93% | 4.93% | 4.93% | +| BB: Synchronization / cell search block | 9% | 8.61% | 8.36% | 8.36% | 8.36% | +| BB: UL processing block | 5% | 3.20% | 2.12% | 2.12% | 2.11% | +| BB: MIMO specific processing blocks | 9% | 7.33% | 7.08% | 7.08% | 7.08% | +| BB: Total | 100% | 43.84% | 38.30% | 38.23% | 35.07% | +| RF+BB: Total | 100% | 65.24% | 61.74% | 60.73% | 58.83% | + +Table 7.3.2-5: Average UE complexity reduction achieved by PR reduction options for TDD 2Rx + +| Reduced UE peak rate | Rel-15 reference | Rel-17 RedCap | PR1 | PR2 | PR3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 24.44% | 24.44% | 24.44% | 24.44% | +| RF: Filters | 15% | 7.69% | 7.69% | 7.69% | 7.69% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 55% | 33.61% | 33.14% | 33.14% | 33.14% | +| RF: Duplexer / Switch | 5% | 4.99% | 4.99% | 4.99% | 4.99% | +| RF: Total | 100% | 70.72% | 70.25% | 70.25% | 70.25% | +| BB: ADC / DAC | 9% | 1.13% | 1.13% | 1.13% | 1.13% | +| BB: FFT/IFFT | 4% | 0.66% | 0.68% | 0.68% | 0.68% | +| BB: Post-FFT data buffering | 10% | 1.17% | 1.21% | 1.19% | 1.20% | +| BB: Receiver processing block | 29% | 5.82% | 5.71% | 5.71% | 3.55% | +| BB: LDPC decoding | 9% | 1.33% | 0.54% | 0.53% | 0.61% | +| BB: HARQ buffer | 12% | 1.16% | 0.41% | 0.40% | 0.43% | +| BB: DL control processing & decoder | 4% | 3.75% | 3.75% | 3.75% | 3.75% | +| BB: Synchronization / cell search block | 9% | 4.50% | 4.63% | 4.63% | 4.63% | +| BB: UL processing block | 5% | 2.83% | 1.93% | 1.90% | 1.91% | +| BB: MIMO specific processing blocks | 9% | 3.82% | 3.76% | 3.76% | 3.76% | +| BB: Total | 100% | 26.17% | 23.75% | 23.68% | 21.65% | +| RF+BB: Total | 100% | 43.99% | 42.35% | 42.31% | 41.09% | + +Table 7.3.2-6: Average UE complexity reduction achieved by PR reduction options for HD-FDD 2Rx + +| Reduced UE peak rate | Rel-15 reference | Rel-17 RedCap | PR1 | PR2 | PR3 | +|-----------------------------------------------------------|------------------|---------------|---------------|---------------|---------------| +| RF: Power amplifier | 25% | 25.00% | 25.00% | 25.00% | 25.00% | +| RF: Filters | 10% | 10.00% | 10.00% | 10.00% | 10.00% | +| RF: Transceiver (incl. LNAs, mixer, and local oscillator) | 45% | 43.04% | 43.04% | 43.04% | 43.04% | +| RF: Duplexer / Switch | 20% | 4.33% | 4.33% | 4.33% | 4.33% | +| RF: Total | 100% | 82.38% | 82.38% | 82.38% | 82.38% | +| BB: ADC / DAC | 10% | 2.06% | 2.04% | 2.04% | 2.04% | +| BB: FFT/IFFT | 4% | 1.15% | 1.15% | 1.15% | 1.15% | +| BB: Post-FFT data buffering | 10% | 2.14% | 2.14% | 2.14% | 2.09% | +| BB: Receiver processing block | 24% | 9.01% | 8.77% | 8.77% | 5.43% | +| BB: LDPC decoding | 10% | 2.69% | 0.94% | 0.90% | 1.11% | +| BB: HARQ buffer | 14% | 2.41% | 0.82% | 0.78% | 0.87% | +| BB: DL control processing & decoder | 5% | 5.00% | 5.00% | 5.00% | 5.00% | +| BB: Synchronization / cell search block | 9% | 8.55% | 8.55% | 8.55% | 8.55% | +| BB: UL processing block | 5% | 3.17% | 2.09% | 2.09% | 2.07% | +| BB: MIMO specific processing blocks | 9% | 7.23% | 7.23% | 7.23% | 7.23% | +| BB: Total | 100% | 43.39% | 38.74% | 38.65% | 35.55% | +| RF+BB: Total | 100% | 58.99% | 56.19% | 56.14% | 54.28% | + +For comparison, the average complexity reduction estimates from [7] for different peak rate reduction options compared to the corresponding Rel-17 RedCap baselines are presented in the table below. + +**Table 7.3.2-7: Average UE complexity reduction achieved by PR reduction options compared to corresponding Rel-17 baselines** + +| Option | FD-FDD 1Rx | TDD 1Rx | HD-FDD 1Rx | FD-FDD 2Rx | TDD 2Rx | HD-FDD 2Rx | +|--------|------------|---------|------------|------------|---------|------------| +| PR1 | 4.13% | 4.02% | 4.99% | 5.36% | 3.73% | 4.74% | +| PR2 | 4.26% | 4.16% | 5.14% | 6.91% | 3.82% | 4.82% | +| PR3 | 7.06% | 6.74% | 8.12% | 9.81% | 6.59% | 7.98% | + +### 7.3.3 Analysis of performance impacts + +#### Peak data rate: + +The UE peak rate reduction options (PR1/PR2/PR3) can all fulfil the data rate requirements. + +#### Coverage: + +For the UE peak rate reduction options PR1 and PR2, no coverage loss is expected. + +For PR3, the coverage impacts are similar as for BW3, see clause 7.2.3. + +For a more detailed description of the coverage impacts, see clause 8.2.4. + +### 7.3.4 Analysis of network deployment and coexistence impacts + +For UE peak rate reduction options PR1 and PR2, there is no or small coexistence issue. + +For UE peak rate reduction option PR3 (in the same way as for UE bandwidth reduction option BW3 described in clause 7.2), SIB1, OSI, RAR and MSG4 need to be scheduled within 5 MHz, otherwise there may be coexistence impacts on legacy UEs. + +Early indication (through Msg1/MsgA) might be needed for PR3. + +### 7.3.5 Analysis of specification impacts + +The UE peak rate reduction options (PR1/PR2/PR3) all have minimal specification impact. + +## 7.4 Relaxed UE processing timeline + +### 7.4.1 Description of feature + +In the study, relaxed UE processing timeline is considered for FR1. The main options for the study are as follows: + +- Option PT1: Relaxation of UE processing time for PDSCH/PUSCH in terms of $N_1$ and $N_2$ (as defined in TS 38.214) compared to those of UE processing time capability 1 + - The relaxation factor for $N_1$ and $N_2$ is assumed to be 2 in the study. +- Option PT2: Relaxation of UE processing time for CSI in terms of $Z$ and $Z'$ compared to the values defined in TS 38.214 clause 5.4 + - The relaxation factor for $Z$ and $Z'$ is assumed to be 2 in the study. + +For the above relaxed UE processing timeline options, the following aspects are considered: + +- The combination of Options PT1 and PT2 is also studied. +- UE complexity reduction estimates for relaxed UE processing timeline are only reported for combinations with UE bandwidth reduction or UE peak rate reduction. + +### 7.4.2 Analysis of UE complexity reduction + +For PT1, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: Receiver processing block +- Baseband: LDPC decoding +- Baseband: DL control processing & decoder +- Baseband: UL processing block + +For PT2, the main contributors of the complexity reduction are the following functional blocks: + +- Baseband: DL control processing & decoder (when both PT1 and PT2 are supported) +- Baseband: UL processing block +- Baseband: MIMO specific processing block + +Whether PT1 or PT2 may reduce the complexity in the 'DL control processing & decoder' block depends on the UE implementation. Complexity evaluations are provided only in combination with other techniques in clause 7.5. + +### 7.4.3 Analysis of performance impacts + +#### Coverage: + +No coverage impact is expected from PT1 and PT2. + +#### Data rate: + +No impact on instantaneous peak data rate is expected from PT1 and PT2. + +#### Latency: + +Both PT1 and PT2 have impact on latency. For downlink transmission, relaxed $N_1$ value in PT1 impacts how fast HARQ-ACK feedback can be sent after the reception of PDSCH. For uplink transmission, relaxed $N_2$ value in PT1 impacts how fast PUSCH can be scheduled with respect to the UL grant and relaxed $Z/Z'$ in PT2 impacts the scheduling of a PUSCH traffic that arrives after the DCI triggering A-CSI is sent since such PUSCH TB cannot be scheduled to be transmitted before the A-CSI is transmitted. How significant the impact on latency depends on use cases and scheduled number of retransmissions. + +Note: For information on other performance impacts (throughput, power consumption), see TR 38.875 clause 7.5.3 [5]. + +### 7.4.4 Analysis of network deployment and coexistence impacts + +For PT1, i.e., relaxed UE processing time in terms of $N_1$ and $N_2$ : + +- In scenarios where Rel-18 RedCap UEs coexist with legacy UEs, PT1 may increase the complexity for the scheduling. +- PT1 may have an impact on scheduling flexibility as several timing requirements are related to $N_1/N_2$ values. +- If PT1 is applicable during the initial/random access, it may cause potential coexistence issues with legacy UEs if early identification of Rel-18 RedCap UEs prior to Msg2 scheduling is not supported, or conservative scheduling is not possible. If gNB schedules all UEs according to relaxed timing relationships for Rel-18 RedCap UEs, legacy UEs may experience an increase in control plane latency. + +For PT2, i.e., relaxed UE processing time in terms of Z and Z': + +- PT2 may have impacts on scheduling flexibility and potentially make the scheduler more complex. +- PT2 may impact the scheduler's ability to track the channel when making scheduling decisions, especially in a fast-varying channel condition. +- No coexistence impact is expected from PT2. + +### 7.4.5 Analysis of specification impacts + +A new UE processing time capability needs to be defined if relaxed UE processing time in terms of N1 and N2 is introduced. New values of N1 and N2, as well as how the PDSCH processing time and PUSCH preparation time are determined by N1 and N2, need to be defined. Depending on the degree of relaxation of the N1 and N2 values, specification details on scheduling timing may be updated, such as HARQ-ACK timing range. Moreover, PT1 may introduce a need for early indication in Msg1. And PT1 does not need to define new default TDRA table for downlink. + +New CSI computation delay requirements need to be defined if relaxed UE processing time in terms of Z and Z' is introduced. New values of Z and Z', as well as how the CSI computation time is determined by Z and Z', need to be defined. + +## 7.5 Combinations of UE complexity reduction features + +### 7.5.1 Description of feature combinations + +The evaluation results for the studied individual UE complexity reduction techniques are captured in clauses 7.2 through 7.4. In this clause, the properties of combinations of different individual UE complexity reduction techniques are described. + +### 7.5.2 Analysis of UE complexity reduction + +The table below show the average value of the UE complexity reduction evaluation results for different combinations of UE complexity reduction features captured in [7]. + +Furthermore, all BW and PR reduction options that correspond to target max 10 Mbps data rate result in reduction of memory size, although these aspects are not captured in the complexity reduction evaluation results in the table. The required L2 buffer size at the UE scales linearly with the UE peak data rate and with the UE bandwidth. + +**Table 7.5.2-1: Average complexity reduction achieved by combinations of UE complexity reduction features compared to corresponding Rel-17 baselines** + +| Option | FD-FDD 1Rx | TDD 1Rx | HD-FDD 1Rx | FD-FDD 2Rx | TDD 2Rx | HD-FDD 2Rx | +|-----------------|------------|---------|------------|------------|---------|------------| +| BW1 | 11.85% | 11.25% | 14.06% | 14.31% | 13.42% | 14.79% | +| BW1 + PT1 | 12.44% | 11.64% | 14.30% | 17.65% | 14.58% | 16.38% | +| BW1 + PT1 + PT2 | 14.75% | 14.73% | 17.51% | 19.10% | 15.80% | 17.89% | +| BW2 | 9.15% | 8.08% | 11.92% | 11.46% | 8.81% | 12.21% | +| BW2 + PT1 + PT2 | 11.54% | 10.91% | 15.27% | 16.70% | 10.99% | 15.18% | +| BW3 | 8.02% | 7.66% | 8.90% | 8.72% | 7.68% | 9.19% | +| BW3+PT1 | 8.70% | 7.84% | 10.15% | 12.48% | 8.98% | 10.77% | +| BW3 + PT1 + PT2 | 11.55% | 11.50% | 12.92% | 14.59% | 10.82% | 12.76% | +| PR1 | 4.13% | 4.02% | 4.99% | 5.36% | 3.73% | 4.74% | +| PR1 + PT1 | 5.40% | 4.85% | 6.58% | 8.80% | 5.49% | 6.54% | +| PR1 + PT1 + PT2 | 7.88% | 8.67% | 9.33% | 10.99% | 6.76% | 8.63% | +| PR2 | 4.26% | 4.16% | 5.14% | 6.91% | 3.82% | 4.82% | +| PR2 + PT1 + PT2 | 7.17% | 6.23% | 9.48% | 10.89% | 6.81% | 8.70% | +| PR3 | 7.06% | 6.74% | 8.12% | 9.81% | 6.59% | 7.98% | +| PR3 + PT1 | 7.69% | 7.23% | 9.32% | 11.49% | 8.11% | 9.67% | +| PR3 + PT1 + PT2 | 10.22% | 10.70% | 12.07% | 13.55% | 9.88% | 11.60% | + +### 7.5.3 Analysis of performance impacts + +For performance impacts for each UE complexity reduction technique, refer to clauses 7.2 through 7.4. + +### 7.5.4 Analysis of network deployment and coexistence impacts + +For network deployment and coexistence impacts for each UE complexity reduction technique, refer to clauses 7.2 through 7.4. + +### 7.5.5 Analysis of specification impacts + +For specification impacts for each UE complexity reduction technique, refer to clauses 7.2 through 7.4. + +# 8 Coverage impact + +## 8.1 Introduction to coverage impact + +Potential coverage reduction due to the device complexity reduction was studied. The evaluation methodology is described in clause 6.2. Evaluation results for different scenarios are described in clause 8.2.1 through clause 8.2.3 where it was assumed the potential Rel-18 UE had the maximum bandwidth reduced to 5MHz in both RF and BB. In other words, the complexity reduction option BW1 from clause 7.2 was assumed for the coverage impact evaluation in clause 8.2.1 through clause 8.2.3. Starting from the coverage evaluation results for BW1, clause 8.2.4 presents a summary of observations on coverage impact evaluation for different complexity reduction options particularly BW1, BW2, BW3, and PR3. + +## 8.2 Coverage impact evaluation + +### 8.2.1 Urban scenario at 2.6 GHz + +For Urban scenario at 2.6 GHz, the bottleneck channel for the reference NR UE and the corresponding maximum isotropic loss (MIL) value by the sourcing companies [7] are shown in Table 8.2.1-1. For this Urban scenario at 2.6 GHz, the study primarily evaluated the potential Rel-18 UE with 11-PRB UE bandwidth. Sourcing companies could additionally report evaluation results with 12-PRB UE bandwidth. + +As can be seen from Table 8.2.1-1, for Urban scenario at 2.6GHz, PUSCH is the bottleneck channel for the reference NR UE. + +**Table 8.2.1-1: Bottleneck channels and MIL values for the reference R15 NR UE in Urban scenario at 2.6GHz** + +| Company | Bottleneck Channel | MIL (dB) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------| +| MediaTek | PUSCH (*) | 142.55 | +| Spreadtrum | PUSCH | 145.74 | +| ZTE | PUSCH | 141.43 | +| Ericsson | PUSCH | 137.14 | +| Samsung | PUSCH | 139.44 | +| vivo | PUSCH | 139.57 | +| Nokia | PUSCH | 140.02 | +| CMCC | PUSCH | 141.01 | +| NTT DOCOMO | PUSCH | 145.46 | +| CATT | PUSCH | 144.34 | +| OPPO | PUSCH | 145.14 | +| Panasonic | PUSCH (*) | 142.55 | +| Mavenir | PUSCH (*) | 142.55 | +| Xiaomi | PUSCH | 146.85 | +| Huawei | PUSCH | 138.95 | +| Lenovo | PUSCH | 142.96 | +| Intel | PUSCH | 140.35 | +| Qualcomm | PUSCH | 139.37 | +| NOTE: For a sourcing company labeled with (*) that did not provide evaluation results for uplink channels for the reference NR UE, the bottleneck channel and its MIL value were derived from Table 9.1.1-1 of TR 38.875 [5] based on the methodology in Clause 6.2. | | | + +For the potential Rel-18 UE with maximum 11-PRB bandwidth, the coverage margins relative to the bottleneck channel of the reference NR UE are summarized in Table 8.2.1-2 (part 1 and part 2) and Table 8.2.1-3 (part 1 and part 2). In Table 8.2.1-2, no UE antenna efficiency loss is assumed for the potential Rel-18 UE with maximum 11-PRB bandwidth. In Table 8.2.1-3, UE antenna efficiency loss of 3dB is assumed in both DL and UL for the potential Rel-18 UE with maximum 11-PRB bandwidth. For every sourcing-company result, the coverage margin for each channel that has MIL below the bottleneck channel for the reference NR UE is highlighted in red. + +The representative value 1, number of samples 1, representative value 2, and number of samples 2 in the last four rows of Table 8.2.1-2 and Table 8.2.1-3 are determined according to the methodology described in clause 6.2. A negative representative value for a channel of the potential Rel-18 UE indicates the coverage of the channel is worse than that of the bottleneck channel of the reference NR UE. + +As can be seen from the representative values in Table 8.2.1-2 and Table 8.2.1-3, for Urban scenario at 2.6 GHz with DL PSD of 33 dBm/MHz and maximum 11-PRB UE bandwidth: + +- Without 3-dB UE antenna efficiency loss: the representative values of the coverage margins for the potential Rel-18 UE with 11-PRB BW for all channels are positive. +- With 3-dB UE antenna efficiency loss: the representative values of the coverage margins for the potential Rel-18 UE with 11-PRB BW for all channels are positive except for PDCCH CSS with AL2 and certain configuration of SIB1. The coverage of PDCCH CSS with AL2 has worse coverage by less than 1 dB than the bottleneck channel of the reference NR UE. A similar observation applies to SIB1. It should be noted that the reception schemes for SIB1 coverage simulations have different assumptions among sourcing companies. For example, some punctured the bits transmitted outside the potential Rel-18 UE's bandwidth while some performed soft combining the bits transmitted outside the potential Rel-18 UE's bandwidth by RF retuning at UE side. + +As can be seen from the representative values in Table 8.2.1-2 and Table 8.2.1-3, PUSCH for the potential Rel-18 UE with maximum 11-PRB bandwidth, with or without 3dB UE antenna efficiency loss, has better coverage than the bottleneck channel of the reference NR UE and hence coverage recovery is not needed for PUSCH. This is because the cell-edge target data rates are scaled by a factor of 0.25 for the potential Rel-18 UE compared to the reference Rel-17 RedCap UE. + +**Table 8.2.1-2 (part 1): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin (dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | SIB1 (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 11 PRBs; TBS 72 bits) | Msg4 (BW1, 11 PRBs; TBS 1040 bits) | +|----------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| MediaTek | 13.42 | - | 8.32 | 7.72 | 3.62 | 2.72 | 5.52 | 10.12 | 6.32 | +| Spreadtrum | - | 7.23 | 4.73 | 4.03 | 0.53 | -0.57 | 0.83 | 11.23 | 4.83 | +| ZTE | - | 10.90 | 0.90 | -4.00 | -2.80 | -1.70 | 4.10 | 10.60 | 5.50 | +| Ericsson | 8.53 | - | 6.53 | 6.03 | -0.67 | -2.23 | 1.04 | 6.69 | 2.01 | +| Samsung | - | - | - | - | 7.43 | - | 5.53 | 14.13 | 7.33 | +| vivo | 7.80 | 12.92 | 11.38 | 9.39 | 7.36 | 8.92 | 8.53 | - | - | +| Nokia | 18.19 | - | 15.19 | 15.19 | 11.19 | 11.89 | 11.39 | 24.59 | 10.69 | +| CMCC | 12.62 | - | 3.44 | 3.44 | -0.32 | 5.35 | 7.85 | 18.75 | 14.95 | +| NTT DOCOMO | 10.33 | - | 6.02 | 6.02 | 1.50 | -3.64 | 3.04 | 8.96 | 4.16 | +| CATT | 10.93 | - | 5.53 | 3.13 | -0.17 | 0.93 | 2.73 | 6.23 | 3.93 | +| OPPO | 7.92 | - | 8.02 | 7.42 | 4.02 | 6.12 | 9.32 | 10.64 | 10.32 | +| Panasonic | - | - | -2.58 | -3.38 | -8.98 | -3.68 | -4.38 | - | - | + +| | | | | | | | | | | +|-------------------------------|--------------|--------------|-------------|-------------|--------------|--------------|--------------|--------------|-------------| +| Mavenir | - | - | - | 4.16 | 2.51 | -0.58 | 0.91 | - | - | +| Xiaomi | 4.30 | - | - | 4.37 | -1.78 | -3.58 | -1.08 | 5.72 | 1.79 | +| Huawei | 13.81 | - | 9.61 | 9.21 | 5.31 | 15.61 | 11.11 | 12.31 | 7.81 | +| Lenovo | 8.7 | - | - | - | 5.01 | - | 4.3 | - | - | +| Intel | 17.43 | - | 11.13 | 9.93 | 6.43 | 2.13 | 5.83 | 12.53 | 7.43 | +| Qualcomm | 14.89 | - | 5.87 | - | 3.17 | 4.89 | 5.19 | 11.69 | 6.59 | +| Representative value 1 | 11.30 | 10.90 | 7.23 | 6.30 | 2.91 | 2.92 | 5.34 | 11.25 | 6.42 | +| # of samples 1 | 12 | 3 | 12 | 12 | 15 | 13 | 15 | 13 | 13 | +| Representative value 2 | 11.49 | 10.90 | 6.79 | 5.50 | 2.57 | 2.19 | 4.67 | 11.16 | 6.41 | +| # of samples 2 | 13 | 3 | 14 | 15 | 18 | 16 | 18 | 14 | 14 | + +Table 8.2.1-2 (part 2): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin (dB) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 11 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 11 PRBs) | PRACH C2 (BW1, 11 PRBs) | Msg3 (BW1, 11 PRBs) | PUSCH (BW1, 11 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 11 PRBs) | PUCCH 11bit (BW1, 11 PRBs) | PUCCH 22 bits (BW1, 11 PRBs) | +|-------------------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| MediaTek | 6.02 | 12.22 | 15.92 | - | - | - | - | - | - | - | +| Spreadtrum | 4.53 | 9.93 | 12.53 | 7.06 | 5.06 | 7.76 | 4.06 | 11.47 | 12.37 | 9.97 | +| ZTE | 0.33 | 10.43 | 21.03 | - | - | 13.76 | 5.06 | 21.27 | 18.67 | 16.67 | +| Ericsson | 3.33 | 8.13 | 11.98 | 17.96 | - | 14.06 | 5.46 | 13.07 | 18.56 | 16.63 | +| Samsung | 11.53 | 16.73 | 17.33 | - | - | 10.56 | 4.97 | 20.17 | 15.37 | 13.17 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| Nokia | 11.19 | 15.69 | 18.59 | - | - | 11.86 | 3.94 | - | - | - | +| CMCC | 5.68 | 11.27 | 19.35 | 14.74 | 12.77 | 11.70 | 4.44 | 15.60 | 13.75 | 11.84 | +| NTT DOCOMO | 5.50 | - | 14.17 | - | - | 9.37 | 5.35 | 17.53 | 17.58 | - | +| CATT | 3.83 | 8.03 | 12.43 | 10.56 | 10.26 | 8.46 | 4.36 | 15.87 | 14.47 | 12.47 | +| OPPO | - | - | - | - | - | - | - | - | - | - | +| Panasonic | - | - | - | - | - | - | - | - | - | - | +| Mavenir | - | - | - | - | - | - | - | - | - | - | +| Xiaomi | 2.22 | - | 10.90 | - | - | 8.19 | 5.04 | - | - | - | +| Huawei | 8.31 | 13.41 | 15.91 | 6.28 | 6.38 | 11.66 | 3.68 | 21.63 | 19.33 | - | +| Lenovo | - | - | - | - | - | 11.24 | - | - | - | - | +| Intel | 7.69 | 13.09 | 14.19 | - | - | 7.14 | 5.63 | - | - | - | +| Qualcomm | - | - | 17.39 | - | - | 8.86 | 4.87 | - | - | 7.16 | +| Representative value 1 | 5.81 | 11.71 | 15.39 | 10.79 | 8.32 | 10.31 | 4.76 | 17.25 | 16.40 | 12.82 | +| # of samples 1 | 11 | 9 | 12 | 5 | 4 | 13 | 12 | 8 | 8 | 7 | +| Representative value 2 | 5.83 | 11.77 | 15.44 | 10.79 | 8.32 | 10.31 | 4.76 | 17.25 | 16.40 | 12.82 | +| # of samples 2 | 12 | 10 | 13 | 5 | 4 | 13 | 12 | 8 | 8 | 7 | + +Table 8.2.1-3 (part 1): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin (dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | SIB1 (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 11 PRBs; TBS 72 bits) | Msg4 (BW1, 11 PRBs; TBS 1040 bits) | +|-------------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| MediaTek | 10.42 | - | 5.32 | 4.72 | 0.62 | -0.28 | 2.52 | 7.12 | 3.32 | +| Spreadtrum | - | 4.23 | 1.73 | 1.03 | -2.47 | -3.57 | -2.17 | 8.23 | 1.83 | +| ZTE | - | 7.90 | -2.10 | -7.00 | -5.80 | -4.70 | 1.10 | 7.60 | 2.50 | +| Ericsson | 5.53 | - | 3.53 | 3.03 | -3.67 | -5.23 | -1.96 | 3.69 | -0.99 | +| Samsung | - | - | - | - | 4.43 | - | 2.53 | 11.13 | 4.33 | +| vivo | 4.80 | 9.92 | 8.38 | 6.39 | 4.36 | 5.92 | 5.53 | - | - | +| Nokia | 15.19 | - | 12.19 | 12.19 | 8.19 | 8.89 | 8.39 | 21.59 | 7.69 | +| CMCC | 9.62 | - | 0.44 | 0.44 | -3.32 | 2.35 | 4.85 | 15.75 | 11.95 | +| NTT DOCOMO | 7.33 | - | 3.02 | 3.02 | -1.50 | -6.64 | 0.04 | 5.96 | 1.16 | +| CATT | 7.93 | - | 2.53 | 0.13 | -3.17 | -2.07 | -0.27 | 3.23 | 0.93 | +| OPPO | 4.92 | - | 5.02 | 4.42 | 1.02 | 3.12 | 6.32 | 7.64 | 7.32 | +| Panasonic | - | - | -5.58 | -6.38 | -11.98 | -6.68 | -7.38 | - | - | +| Mavenir | - | - | - | 1.16 | -0.49 | -3.58 | -2.09 | - | - | +| Xiaomi | 1.30 | - | - | 1.37 | -4.78 | -6.58 | -4.08 | 2.72 | -1.21 | +| Huawei | 10.81 | - | 6.61 | 6.21 | 2.31 | 12.61 | 8.11 | 9.31 | 4.81 | +| Lenovo | 5.7 | - | - | - | 2.01 | - | 1.3 | - | - | +| Intel | 14.43 | - | 8.13 | 6.93 | 3.43 | -0.87 | 2.83 | 9.53 | 4.43 | +| Qualcomm | 11.89 | - | 2.87 | - | 0.17 | 1.89 | 2.19 | 8.69 | 3.59 | +| Representative value 1 | 8.30 | N/A | 4.23 | 3.30 | -0.09 | -0.08 | 2.34 | 8.25 | 3.42 | +| # of samples 1 | 12 | 3 | 12 | 12 | 15 | 13 | 15 | 13 | 13 | +| Representative value 2 | 8.49 | N/A | 3.79 | 2.50 | -0.43 | -0.81 | 1.67 | 8.16 | 3.41 | +| # of samples 2 | 13 | 3 | 14 | 15 | 18 | 16 | 18 | 14 | 14 | + +Table 8.2.1-3 (part 2): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin (dB) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 11 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 11 PRBs) | PRACH C2 (BW1, 11 PRBs) | Msg3 (BW1, 11 PRBs) | PUSCH (BW1, 11 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 11 PRBs) | PUCCH 11bit (BW1, 11 PRBs) | PUCCH 22 bits (BW1, 11 PRBs) | +|----------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| MediaTek | 3.02 | 9.22 | 12.92 | - | - | - | - | - | - | - | +| Spreadtrum | 1.53 | 6.93 | 9.53 | 4.06 | 2.06 | 4.76 | 1.06 | 8.47 | 9.37 | 6.97 | +| ZTE | -2.67 | 7.43 | 18.03 | - | - | 10.76 | 2.06 | 18.27 | 15.67 | 13.67 | + +| | | | | | | | | | | | +|-------------------------------|--------------|-------------|--------------|-------------|-------------|-------------|-------------|--------------|--------------|-------------| +| Ericsson | 0.33 | 5.13 | 8.98 | 14.96 | - | 11.06 | 2.46 | 10.07 | 15.56 | 13.63 | +| Samsung | 8.53 | 13.73 | 14.33 | - | - | 7.56 | 1.97 | 17.17 | 12.37 | 10.17 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| Nokia | 8.19 | 12.69 | 15.59 | - | - | 8.86 | 0.94 | - | - | - | +| CMCC | 2.68 | 8.27 | 16.35 | 11.74 | 9.77 | 8.70 | 1.44 | 12.60 | 10.75 | 8.84 | +| NTT DOCOMO | 2.50 | - | 11.17 | - | - | 6.37 | 2.35 | 14.53 | 14.58 | - | +| CATT | 0.83 | 5.03 | 9.43 | 7.56 | 7.26 | 5.46 | 1.36 | 12.87 | 11.47 | 9.47 | +| OPPO | - | - | - | - | - | - | - | - | - | - | +| Panasonic | - | - | - | - | - | - | - | - | - | - | +| Mavenir | - | - | - | - | - | - | - | - | - | - | +| Xiaomi | -0.78 | - | 7.90 | - | - | 5.19 | 2.04 | - | - | - | +| Huawei | 5.31 | 10.41 | 12.91 | 3.28 | 3.38 | 8.66 | 0.68 | 18.63 | 16.33 | - | +| Lenovo | - | - | - | - | - | 8.24 | - | - | - | - | +| Intel | 4.69 | 10.09 | 11.19 | - | - | 4.14 | 2.63 | - | - | - | +| Qualcomm | - | - | 14.39 | - | - | 5.86 | 1.87 | - | - | 4.16 | +| Representative value 1 | 2.81 | 8.71 | 12.39 | 7.79 | 5.32 | 7.31 | 1.76 | 14.25 | 13.40 | 9.82 | +| # of samples 1 | 11 | 9 | 12 | 5 | 4 | 13 | 12 | 8 | 8 | 7 | +| Representative value 2 | 2.83 | 8.77 | 12.44 | 7.79 | 5.32 | 7.31 | 1.76 | 14.25 | 13.40 | 9.82 | +| # of samples 2 | 12 | 10 | 13 | 5 | 4 | 13 | 12 | 8 | 8 | 7 | + +For the potential Rel-18 UE with maximum 12-PRB bandwidth, the coverage margins relative to the bottleneck channel of the reference NR UE are summarized in Table 8.2.1-4 (part 1 and part 2) and Table 8.2.1-5 (part 1 and part 2). In Table 8.2.1-4, no UE antenna efficiency loss is assumed for the potential Rel-18 UE with maximum 12-PRB bandwidth. In Table 8.2.1-5, the 3dB UE antenna efficiency loss is assumed in both DL and UL for the potential Rel-18 UE with maximum 12-PRB bandwidth. For every sourcing-company result, the coverage margin for each channel that has MIL below the bottleneck channel for the reference NR UE is highlighted in red. + +The representative value 1, number of samples 1, representative value 2, and number of samples 2 in the last four rows of Table 8.2.1-4 and Table 8.2.1-5 are determined according to the methodology described in clause 6.2. A negative representative value for a channel of the potential Rel-18 UE indicates the coverage of the channel is worse than that of the bottleneck channel of the reference NR UE. + +For Urban scenario at 2.6 GHz with DL PSD of 33 dBm/MHz and maximum 12-PRB UE bandwidth: + +- Without 3-dB UE antenna efficiency loss: the representative values of the coverage margins for Rel-18 UE with maximum 12-PRB bandwidth for all channels are positive. +- With 3-dB UE antenna efficiency loss: the representative values of the coverage margins for Rel-18 UE with maximum 12-PRB bandwidth for all channels are positive. Again, it is noted that the reception schemes for SIB1 coverage simulations have different assumptions among sourcing companies. For example, some punctured the bits transmitted outside the potential Rel-18 UE's bandwidth while some performed soft combining the bits transmitted outside the potential Rel-18 UE's bandwidth by retuning RF. + +As can be seen from the representative values in Table 8.2.1-4 and Table 8.2.1-5, PUSCH for the potential Rel-18 UE with maximum 12-PRB bandwidth, with or without 3dB UE antenna efficiency loss, has better coverage than the bottleneck channel of the reference NR UE and hence coverage recovery is not needed for PUSCH. This is because the cell-edge target data rates are scaled by a factor of 0.25 for the potential Rel-18 RedCap UE compared to the reference Rel-17 RedCap UE. + +**Table 8.2.1-4 (part 1): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 12-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 12 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 12 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 12 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | SIB1 (BW1, 12 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 12 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 12 PRBs; TBS 72 bits) | Msg4 (BW1, 12 PRBs; TBS 1040 bits) | +|-------------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| MediaTek | 13.42 | - | 9.02 | 8.42 | 9.92 | 3.82 | 5.52 | 10.12 | 6.62 | +| Spreadtrum | - | 7.93 | 5.33 | 4.53 | 6.03 | 0.23 | 0.83 | 11.23 | 5.23 | +| Ericsson | 8.53 | - | 7.33 | 6.43 | 4.43 | -0.37 | 1.91 | 6.69 | 3.07 | +| vivo | 5.80 | 13.07 | 11.81 | 10.51 | 12.22 | 9.90 | 8.53 | - | - | +| CMCC | 12.82 | - | 4.54 | 4.53 | 5.27 | 6.75 | 9.15 | 18.75 | 15.95 | +| CATT | 11.53 | - | 6.23 | 4.53 | 5.43 | 2.13 | 3.23 | 6.23 | 4.33 | +| Xiaomi | 4.67 | - | - | 4.84 | 4.48 | -0.96 | 1.47 | 5.54 | 3.50 | +| Huawei | 14.21 | - | 10.41 | 10.01 | 10.81 | 15.91 | 12.51 | 12.31 | 8.81 | +| Intel | 18.33 | - | 11.93 | 10.93 | 11.83 | 4.23 | 6.83 | 12.53 | 8.33 | +| Qualcomm | 15.49 | - | - | - | 6.27 | - | 6.89 | - | - | +| Representative value 1 | 11.40 | N/A | 8.22 | 6.81 | 7.16 | 3.81 | 5.43 | 9.80 | 6.04 | +| # of samples 1 | 8 | 2 | 7 | 8 | 9 | 8 | 9 | 7 | 7 | +| Representative value 2 | 11.69 | N/A | 8.36 | 7.04 | 7.51 | 3.81 | 5.44 | 9.85 | 6.14 | +| # of samples 2 | 9 | 2 | 8 | 9 | 10 | 9 | 10 | 8 | 8 | + +**Table 8.2.1-4 (part 2): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 12-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin (dB) | PDCCH USS (BW1, 12 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 12 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 12 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 12 PRBs) | PRACH C2(BW1, 12 PRBs) | Msg3 (BW1, 12 PRBs) | PUSCH (BW1, 12 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 12 PRBs) | PUCCH 11bit (BW1, 12 PRBs) | PUCCH 22 bits (BW1, 12 PRBs) | +|-------------------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| MediaTek | 6.02 | 12.92 | 15.92 | - | - | - | - | - | - | - | +| Spreadtrum | 4.53 | 10.83 | 12.63 | 6.83 | 4.83 | 7.76 | 3.68 | 11.47 | 12.37 | 9.97 | +| Ericsson | 3.33 | 8.43 | 12.02 | 17.93 | - | 14.06 | 5.38 | 13.07 | 18.57 | 16.64 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| CMCC | 5.68 | 11.27 | 19.05 | 14.62 | 12.77 | 11.70 | 4.45 | 15.53 | 13.79 | 11.82 | +| CATT | 3.83 | 9.43 | 14.13 | 13.43 | 8.93 | 8.46 | 4.28 | 15.87 | 14.47 | 12.47 | +| Xiaomi | 2.22 | 8.48 | 12.62 | - | - | 8.13 | 5.25 | - | - | - | +| Huawei | 8.21 | 13.81 | 16.91 | 6.35 | 6.45 | 11.66 | 4.10 | 21.63 | 19.33 | - | +| Intel | 7.69 | 13.09 | 14.19 | - | - | 7.14 | 5.63 | - | - | - | +| Qualcomm | - | - | - | - | - | - | - | - | - | - | +| Representative value 1 | 5.01 | 10.62 | 14.10 | 11.63 | 7.69 | 9.54 | 4.69 | 14.82 | 15.61 | 12.15 | + +| | | | | | | | | | | | +|------------------------|------|-------|-------|-------|------|------|------|-------|-------|-------| +| # of samples 1 | 7 | 7 | 7 | 5 | 4 | 7 | 7 | 5 | 5 | 4 | +| Representative value 2 | 5.18 | 11.00 | 14.40 | 11.63 | 7.69 | 9.54 | 4.69 | 14.82 | 15.61 | 12.15 | +| # of samples 2 | 8 | 8 | 8 | 5 | 4 | 7 | 7 | 5 | 5 | 4 | + +Table 8.2.1-5 (part 1): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 12-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin (dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 12 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 12 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 12 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | SIB1 (BW1, 12 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 12 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 12 PRBs; TBS 72 bits) | Msg4 (BW1, 12 PRBs; TBS 1040 bits) | +|-------------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| MediaTek | 10.42 | - | 6.02 | 5.42 | 6.92 | 0.82 | 2.52 | 7.12 | 3.62 | +| Spreadtrum | - | 4.93 | 2.33 | 1.53 | 3.03 | -2.77 | -2.17 | 8.23 | 2.23 | +| Ericsson | 5.53 | - | 4.33 | 3.43 | 1.43 | -3.37 | -1.09 | 3.69 | 0.07 | +| vivo | 2.80 | 10.07 | 8.81 | 7.51 | 9.22 | 6.90 | 5.52 | - | - | +| CMCC | 9.82 | - | 1.54 | 1.53 | 2.27 | 3.75 | 6.15 | 15.75 | 12.95 | +| CATT | 8.53 | - | 3.23 | 1.53 | 2.43 | -0.87 | 0.23 | 3.23 | 1.33 | +| Xiaomi | 1.67 | - | - | 1.84 | 1.48 | -3.96 | -1.53 | 2.54 | 0.50 | +| Huawei | 11.21 | - | 7.41 | 7.01 | 7.81 | 12.91 | 9.51 | 9.31 | 5.81 | +| Intel | 15.33 | - | 8.93 | 7.93 | 8.83 | 1.23 | 3.83 | 9.53 | 5.33 | +| Qualcomm | 12.49 | - | - | - | 3.27 | - | 3.89 | - | - | +| Representative value 1 | 8.40 | N/A | 5.22 | 3.81 | 4.16 | 0.81 | 2.43 | 6.80 | 3.04 | +| # of samples 1 | 8 | 2 | 7 | 8 | 9 | 8 | 9 | 7 | 7 | +| Representative value 2 | 8.69 | N/A | 5.36 | 4.04 | 4.51 | 0.81 | 2.44 | 6.85 | 3.14 | +| # of samples 2 | 9 | 2 | 8 | 9 | 10 | 9 | 10 | 8 | 8 | + +Table 8.2.1-5 (part 2): In Urban scenario at 2.6GHz with DL 33dBm/MHz PSD, coverage margins for the potential Rel-18 UE with maximum 12-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.1-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin (dB) | PDCCH USS (BW1, 12 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 12 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 12 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 12 PRBs) | PRACH C2(BW1, 12 PRBs) | Msg3 (BW1, 12 PRBs) | PUSCH (BW1, 12 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 12 PRBs) | PUCCH 11bit (BW1, 12 PRBs) | PUCCH 22 bits (BW1, 12 PRBs) | +|----------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| MediaTek | 3.02 | 9.92 | 12.92 | - | - | - | - | - | - | - | +| Spreadtrum | 1.53 | 7.83 | 9.63 | 3.83 | 1.83 | 4.76 | 0.68 | 8.47 | 9.37 | 6.97 | +| Ericsson | 0.33 | 5.43 | 9.02 | 14.93 | - | 11.06 | 2.38 | 10.07 | 15.57 | 13.64 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| CMCC | 2.68 | 8.27 | 16.05 | 11.62 | 9.77 | 8.70 | 1.45 | 12.53 | 10.79 | 8.82 | +| CATT | 0.83 | 6.43 | 11.13 | 10.43 | 5.93 | 5.46 | 1.28 | 12.87 | 11.47 | 9.47 | + +| | | | | | | | | | | | +|-------------------------------|--------------|-------------|--------------|-------------|-------------|-------------|-------------|--------------|--------------|-------------| +| Xiaomi | -0.78 | 5.48 | 9.62 | - | - | 5.13 | 2.25 | - | - | - | +| Huawei | 5.21 | 10.81 | 13.91 | 3.35 | 3.45 | 8.66 | 1.10 | 18.63 | 16.33 | - | +| Intel | 4.69 | 10.09 | 11.19 | - | - | 4.14 | 2.63 | - | - | - | +| Qualcomm | - | - | - | - | - | - | - | - | - | - | +| Representative value 1 | 2.01 | 7.62 | 11.10 | 8.63 | 4.69 | 6.54 | 1.69 | 11.82 | 12.61 | 9.15 | +| # of samples 1 | 7 | 7 | 7 | 5 | 4 | 7 | 7 | 5 | 5 | 4 | +| Representative value 2 | 2.18 | 8.00 | 11.40 | 8.63 | 4.69 | 6.54 | 1.69 | 11.82 | 12.61 | 9.15 | +| # of samples 2 | 8 | 8 | 8 | 5 | 4 | 7 | 7 | 5 | 5 | 4 | + +In Urban scenario at 2.6GHz with maximum 11-PRB UE bandwidth, for evaluation of PBCH coverage impact, the comparison between the potential Rel-18 UE and the reference NR UE in addition to the comparison between the potential Rel-18 UE and the Rel-17 RedCap UE by sourcing companies are summarized in Table 8.2.1-6. + +The representative values in the last row of Table 8.2.1-6 are derived by taking the mean value (in dB domain) from all the companies results after excluding the highest and the lowest values. + +Different PBCH decoding schemes were evaluated in the study. Some companies evaluated soft combining of same portion of PBCH within 11 PRBs without performing RF retuning. Some companies evaluated soft combining of different portions of PBCH by performing RF retuning. Some companies performed RF retuning for receiving different portions of PBCH for each decoding trial but without soft combining. + +The following are observed on PBCH coverage impact from the representative values in the last row of Table 8.2.1-6: + +- Compared to Rel-15 NR UE with soft/selective combining, the PBCH performance degradation of the potential Rel-18 UE by soft/selective combining without RF retuning is 11.87 dB. +- Compared to Rel-15 NR UE with soft/selective combining, the PBCH performance degradation of the potential Rel-18 UE with soft/selective combining and RF retuning is 9.3 dB. +- Compared to Rel-17 RedCap UE with soft/selective combining, the PBCH performance degradation of the potential Rel-18 UE with soft/selective combining without RF retuning is 5.05dB. +- Compared to Rel-17 RedCap UE with soft/selective combining, the PBCH performance degradation of the potential Rel-18 UE with soft/selective combining and RF retuning is 2.51dB. + +**Table 8.2.1-6: In Urban scenario at 2.6GHz with a target BLER of 1% for PBCH, coverage differences between a potential Rel-18 UE with maximum 11-PRB UE BW and the reference NR UE and between the potential Rel-18 UE and the Rel-17 RedCap UE** + +| Coverage difference (dB) | | Comparison with Rel-15 Reference UE (MIL) | | Comparison with Rel-17 RedCap UE (MIL) | | +|----------------------------------|------------|-----------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------|--------------------------------------------------------| +| | | 5MHz UE with soft/selective combining without RF retuning | 5MHz UE with soft/selective combining with RF retuning | 5MHz UE with soft/selective combining without RF retuning | 5MHz UE with soft/selective combining with RF retuning | +| Intel | R1-2207740 | -11 | | -4.9 | | +| Ericsson | R1-2207741 | - | -14.1 | - | -7.4 | +| Nokia, NSB | R1-2206444 | -12.9 | | -5.7 | | +| ZTE | R1-2207058 | -16 | -9.3 | -9.4 | -2.7 | +| vivo | R1-2206052 | | | | -2.32 | +| Qualcomm | R1-2207244 | -11.7 | -9.2 | -4.25 | -1.75 | +| MediaTek | R1-2207003 | -10.5 | | -4.6 | | +| Representative value (dB) | | -11.87 | -9.3 | -5.05 | -2.51 | + +In Urban scenario at 2.6GHz with maximum 11-PRB UE bandwidth for the potential Rel-18 UE, for evaluation of broadcast channels PDCCH CSS and SIB1 coverage impact particularly from the coexistence perspective, the comparison between the potential Rel-18 UE and the reference NR UE in addition to the comparison between the potential Rel-18 UE and the Rel-17 RedCap UE by sourcing companies are summarized in Table 8.2.1-7. It is noted that the target BLER of PDCCH CSS is 1% and the target BLER of SIB1 is 10% in the evaluation. In addition, one-shot decoding is assumed for both PDCCH CSS and SIB1 in all cases in Table 8.2.1-7. + +For the comparison of PDCCH CSS and SIB1 coverage differences between the potential Rel-18 UE and the reference Rel-17 RedCap UE, the configurations and evaluations assumptions are listed in the following. + +- The potential Rel-18 UE is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- The reference Rel-17 RedCap UE for comparison is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- The potential Rel-18 UE is scheduled with SIB1 larger than 5MHz. + - The reference Rel-17 RedCap UE for comparison is scheduled with SIB1 larger than 5MHz. + - For both cases, the exact PRB numbers and MCS values are reported by sourcing companies in [7]. +- The potential Rel-18 UE is scheduled with SIB1 within 5MHz. + - The reference Rel-17 RedCap UE for comparison is scheduled with SIB1 larger than 5MHz. + - For both cases, the exact PRB numbers and MCS values are reported by sourcing companies in [7]. + - It is noted this pair of comparison can provide the following two aspects: + - The SIB1 coverage difference between the potential Rel-18 UE and the reference Rel-17 RedCap if a dedicated SIB1 within 5MHz is transmitted for the potential Rel-18 UE. + - The SIB1 coverage loss for the reference Rel-17 RedCap UE if a universal SIB1 that is confined within 5MHz to accommodate the maximum bandwidth of the potential Rel-18 UE is transmitted for both the potential Rel-18 UE and the reference Rel-17 RedCap UE. + +For all the cases listed above, one-shot decoding without any soft combining was assumed for this evaluation to represent the coverage differences between the potential Rel-18 UE and the reference Rel-15 NR UE and between the potential Rel-18 UE and the reference Rel-17 RedCap UE before applying any coverage enhancement schemes. + +The representative values in the last row of Table 8.2.1-7 are derived by taking the mean value (in dB domain) from all the companies results after excluding the highest and the lowest values. + +In Urban scenario at 2.6GHz with maximum 11-PRB UE bandwidth for the potential Rel-18 UE, from the representative values in the last row of Table 8.2.1-7, the following observations can be made: + +- Observation 1: for PDCCH CSS with AL16 and 48PRB and 2 symbols, performance degradation of the potential Rel-18 UE is 15.26 dB and 8.91 dB compared with Rel-15 NR UE and Rel-17 RedCap UE, respectively. +- Observation 2: for SIB1 greater than 5MHz, performance degradation of the potential Rel-18 UE is 17.50 dB and 11.24 dB compared with Rel-15 NR UE and Rel-17 RedCap UE, respectively. + +**Table 8.2.1-7: In Urban scenario at 2.6GHz with 30kHz SCS, the comparisons of PDCCH CSS and SIB1 coverage differences between the potential Rel-18 UE and reference Rel-15 NR UE as well as those between the potential Rel-18 UE and the reference Rel-17 RedCap UE where one-shot decoding is assumed for all cases and maximum UE bandwidth of 11 PRBs is assumed for the potential Rel-18 UE. (Unit: dB)** + +| Coverage Difference (dB) | | Comparison with reference Rel-15 NR UE (MIL) | | Comparison with reference Rel-17 RedCap UE (MIL) | | | +|----------------------------------|------------|-----------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------| +| | | PDCCH CSS AL16 | SIB1 > 5MHz | PDCCH CSS (48 RBs) with 1% BLER | SIB1 (>5 MHz) with 10% BLER | SIB1 (<5 MHz) with 10% BLER | +| Sourcing company | T-doc | 5MHz-UE (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | 5MHz-UE (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | 5MHz-UE (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | 5MHz-UE (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | 5MHz-UE (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | +| CATT | R1-2207969 | -14.90 | -17.00 | -8.70 | -10.90 | -9.10 | +| Intel | R1-2207740 | -12.98 | -20.20 | -7.50 | -14.20 | -10.50 | +| Ericsson | R1-2207741 | -14.30 | -20.27 | -7.60 | -13.21 | -9.94 | +| NTT DOCOMO | R1-2207692 | -14.16 | -22.71 | -7.92 | -16.24 | -9.56 | +| Nokia NSB | R1-2206444 | -15.90 | -15.90 | -9.20 | -9.30 | -9.80 | +| ZTE | R1-2207058 | -14.70 | -19.30 | -8.50 | -14.60 | -8.80 | +| vivo | R1-2206052 | -13.62 | -12.53 | -7.97 | -4.77 | -5.16 | +| Qualcomm | R1-2207244 | -16.10 | | -9.60 | -10.10 | -9.80 | +| MediaTek | R1-2207003 | -14.80 | -17.50 | -9.20 | -11.50 | -8.70 | +| OPPO | R1-2206304 | -15.90 | -15.50 | -9.60 | -10.90 | -7.70 | +| CMCC | R1-2206294 | -17.59 | -12.20 | -10.25 | -6.40 | -3.90 | +| Huawei, Hisilicon | R1-2205874 | -16.43 | | -10.31 | | | +| Xiaomi | R1-2206654 | | -19.32 | | -12.42 | -9.92 | +| Panasonic | R1-2206437 | -17.10 | -17.5 | -9.5 | -10.10 | -10.80 | +| Representative value (dB) | | -15.26 | -17.50 | -8.91 | -11.24 | -9.00 | + +### 8.2.2 Rural scenario at 0.7 GHz + +For Rural scenario at 0.7 GHz, the bottleneck channel for the reference NR UE and the corresponding maximum isotropic loss (MIL) value by the sourcing companies [7] are shown in Table 8.2.2-1. The coverage margins for the potential Rel-18 UE in Rural scenario at 0.7 GHz, relative to the bottleneck channel of the reference NR UE are summarized in Table 8.2.2-2 and Table 8.2.2-3. In Table 8.2.2-2, no UE antenna efficiency loss is assumed for the potential Rel-18 UE with maximum 25-PRB bandwidth. In Table 8.2.1-3, UE antenna efficiency loss of 3dB is assumed in both DL and UL for the potential Rel-18 UE with maximum 25-PRB bandwidth. For every sourcing-company result, the coverage margin for each channel that has MIL below the bottleneck channel for the reference NR UE is highlighted in red. + +The representative value 1, number of samples 1, representative value 2, and number of samples 2 in the last four rows of Table 8.2.2-2 and Table 8.2.2-3 are determined according to the methodology described in clause 6.2. A negative representative value for a channel of the potential Rel-18 UE indicates the coverage of the channel is worse than that of the bottleneck channel of the reference NR UE. + +As can be seen from Table 8.2.2-1, for Rural scenario at 0.7GHz, PUSCH is the bottleneck channel for reference NR UE. + +**Table 8.2.2-1: Bottleneck channels and MIL values for reference NR UE in Rural scenario at 0.7GHz** + +| Company | Bottleneck Channel | MIL (dB) | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| MediaTek | PUSCH (*) | 145.36 | +| Spreadtrum | PUSCH | 146.46 | +| ZTE | Msg3 | 142.12 | +| Ericsson | PUSCH | 142.96 | +| Samsung | PUSCH | 146.56 | +| vivo | PUSCH | 140.30 | +| Nokia | PUSCH | 141.59 | +| CMCC | PUSCH | 136.35 | +| NTT DOCOMO | PUSCH | 146.70 | +| CATT | PUSCH | 146.46 | +| OPPO | PUCCH PF3 22 bits | 148.95 | +| Panasonic | PUSCH (*) | 145.36 | +| Mavenir | PUSCH (*) | 145.36 | +| Xiaomi | PUSCH | 148.99 | +| Huawei | PUSCH | 141.78 | +| Lenovo | PUSCH | 144.82 | +| Intel | PUSCH | 145.96 | +| Qualcomm | PUSCH | 141.29 | +| NOTE: | For a sourcing company labeled with (*) that did not provide evaluation results for uplink channels for the reference NR UE, the bottleneck channel and its MIL value were derived from Table 9.1.2-1 in TR 38.875 based on the methodology in Clause 6.2. | | + +For Rural scenario at 0.7 GHz, as can be seen from the representative values in Table 8.2.2-2 and Table 8.2.2-3: + +- Without 3-dB UE antenna efficiency loss: the representative values of the coverage margins for the potential Rel-18 UE for all channels are positive and all channels have better coverage than reference NR UE. +- With 3-dB UE antenna efficiency loss: except for Msg3, the representative values of the coverage margins for a potential Rel-18 RedCap UE for all channels are positive. For Msg3, its coverage is slightly worse than the bottleneck channel of the reference NR UE. It is also noted that PUSCH for the potential Rel-18 UE has similar coverage as the bottleneck channel for the reference NR UE. + +As can be seen from the representative values in Table 8.2.2-2 and Table 8.2.2-3, PUSCH for the potential Rel-18 UE with maximum 25-PRB bandwidth, with or without 3dB UE antenna efficiency loss, has similar or better coverage than the bottleneck channel of the reference NR UE. This is because the cell-edge target data rates are scaled by a factor of 0.25 for the potential Rel-18 RedCap UE compared to the reference Rel-17 RedCap UE. + +**Table 8.2.2-2 (part 1): In Rural scenario at 0.7GHz, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.2-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 25 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 25 PRBs; CORESET: 3 symbols, 24 PRBs; AL8) | SIB1 (BW1, 25 PRBs; SIB1 > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 25 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 25 PRBs; TBS 72 bits) | Msg4 (BW1, 25 PRBs; TBS 1040 bits) | +|---------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| MediaTek | 13.47 | - | 10.17 | 10.27 | 6.47 | 6.37 | 7.17 | 8.87 | + +| | | | | | | | | | +|-------------------------------|--------------|------------|-------------|-------------|--------------|--------------|--------------|-------------| +| Spreadtrum | - | 9.57 | 8.57 | 10.37 | 6.27 | 6.97 | 8.47 | 6.57 | +| ZTE | - | 11.66 | 8.06 | 5.26 | 6.56 | 7.66 | 6.56 | 9.16 | +| Ericsson | 9.97 | - | 3.57 | 5.17 | 4.61 | 5.59 | 5.49 | 6.93 | +| Samsung | - | - | - | 8.27 | - | 5.27 | 5.67 | 6.27 | +| vivo | 9.50 | 13.21 | 11.20 | 10.16 | 9.46 | 6.51 | - | - | +| Nokia | 14.63 | - | 11.83 | 11.23 | 9.03 | 7.53 | 14.73 | 8.93 | +| CMCC | 15.75 | - | 11.75 | 11.93 | 12.67 | 16.47 | 14.87 | 17.47 | +| NTT DOCOMO | - | - | 9.40 | 9.10 | 6.18 | 6.70 | 6.96 | 8.03 | +| CATT | 11.47 | - | 7.17 | 5.67 | 4.37 | 6.37 | 2.87 | 6.17 | +| OPPO | 10.17 | - | 10.07 | 10.37 | 9.87 | 10.77 | 6.20 | 10.27 | +| Panasonic | - | - | 10.08 | 9.68 | 9.18 | 9.48 | - | - | +| Mavenir | - | - | - | 6.45 | 4.16 | 3.58 | - | - | +| Xiaomi | 2.39 | - | 3.53 | 3.03 | -1.47 | -2.17 | -1.25 | 1.48 | +| Huawei | 4.53 | - | 8.63 | 8.53 | 8.33 | 3.93 | 3.93 | 5.13 | +| Lenovo | 8.50 | - | - | 11.21 | - | 8.61 | - | - | +| Intel | 14.37 | - | 8.47 | 7.97 | 5.47 | 6.07 | 6.47 | 6.87 | +| Qualcomm | 14.11 | - | 9.41 | 9.31 | 7.31 | 8.61 | 7.11 | 6.91 | +| Representative value 1 | 10.81 | N/A | 8.75 | 8.66 | 7.04 | 6.97 | 6.77 | 7.39 | +| # of samples 1 | 11 | 3 | 13 | 15 | 13 | 15 | 13 | 13 | +| Representative value 2 | 11.07 | N/A | 8.97 | 8.69 | 6.95 | 6.88 | 6.80 | 7.51 | +| # of samples 2 | 12 | 3 | 15 | 18 | 16 | 18 | 14 | 14 | + +Table 8.2.2-2 (part 2): In Rural scenario at 0.7GHz, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.2-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PDCCH USS (BW1, 25 PRBs; CORESET: 3 symbols, 24 PRBs; AL8) | PDSCH (BW1, 25 PRBs; 0.25 Mbps) | PRACH Format 0 (BW1, 25 PRBs) | Msg3 (BW1, 25 PRBs) | PUSCH (BW1, 25 PRBs; 25 kbps) | PUCCH 2bit (BW1, 25 PRBs) | PUCCH 11bit (BW1, 25 PRBs) | PUCCH 22 bits (BW1, 25 PRBs) | +|---------------------|------------------------------------------------------------|---------------------------------|-------------------------------|---------------------|-------------------------------|---------------------------|----------------------------|------------------------------| +| MediaTek | 9.17 | 8.87 | - | - | - | - | - | - | +| Spreadtrum | 10.57 | 9.07 | 6.37 | 5.11 | 0.00 | 7.42 | 6.12 | 4.92 | +| ZTE | 9.15 | 17.95 | - | 0.40 | 5.58 | 10.70 | 8.20 | 5.70 | +| Ericsson | 5.17 | 7.43 | 4.97 | 2.01 | 3.22 | 4.90 | 6.91 | 4.39 | +| Samsung | 8.27 | 6.17 | - | 3.01 | 3.41 | 12.22 | 7.62 | 5.32 | +| vivo | - | - | - | - | - | - | - | - | +| Nokia | 11.23 | 9.13 | - | 2.31 | 3.52 | - | - | - | +| CMCC | 11.93 | 17.37 | 9.64 | 7.54 | 4.95 | 11.45 | 9.84 | 7.54 | +| NTT DOCOMO | 9.10 | 9.08 | - | 2.82 | 4.36 | 6.92 | 10.78 | - | +| CATT | 5.67 | 8.07 | 3.77 | 1.21 | 0.00 | 10.22 | 7.42 | 4.72 | +| OPPO | - | - | - | - | - | - | - | - | +| Panasonic | - | - | - | - | - | - | - | - | +| Mavenir | - | - | - | - | - | - | - | - | +| Xiaomi | 3.03 | 0.93 | - | 2.09 | 2.69 | - | - | - | +| Huawei | 8.53 | 4.73 | 9.27 | 3.52 | 2.91 | 11.02 | 8.77 | - | +| Lenovo | - | - | - | 4.25 | - | - | - | - | + +| | | | | | | | | | +|-------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| Intel | 7.97 | 6.57 | - | 3.86 | 5.32 | - | - | - | +| Qualcomm | - | 8.61 | - | 2.51 | 3.02 | - | - | 2.5 | +| Representative value 1 | 8.41 | 8.62 | 6.87 | 2.97 | 3.84 | 9.62 | 8.13 | 5.01 | +| # of samples 1 | 11 | 12 | 5 | 13 | 10 | 8 | 8 | 7 | +| Representative value 2 | 8.48 | 8.65 | 6.87 | 2.97 | 3.34 | 9.62 | 8.13 | 5.01 | +| # of samples 2 | 12 | 13 | 5 | 13 | 12 | 8 | 8 | 7 | + +Table 8.2.2-3 (part 1): In Rural scenario at 0.7GHz, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.2-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 25 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 25 PRBs; CORESET: 3 symbols, 24 PRBs; AL8) | SIB1 (BW1, 25 PRBs; SIB1 > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 25 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 25 PRBs; TBS 72 bits) | Msg4 (BW1, 25 PRBs; TBS 1040 bits) | +|-------------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| MediaTek | 10.47 | - | 7.17 | 7.27 | 3.47 | 3.37 | 4.17 | 5.87 | +| Spreadtrum | - | 6.57 | 5.57 | 7.37 | 3.27 | 3.97 | 5.47 | 3.57 | +| ZTE | - | 8.66 | 5.06 | 2.26 | 3.56 | 4.66 | 3.56 | 6.16 | +| Ericsson | 6.97 | - | 0.57 | 2.17 | 1.61 | 2.59 | 2.49 | 3.93 | +| Samsung | - | - | - | 5.27 | - | 2.27 | 2.67 | 3.27 | +| vivo | 6.50 | 10.21 | 8.20 | 7.16 | 6.46 | 3.51 | - | - | +| Nokia | 11.63 | - | 8.83 | 8.23 | 6.03 | 4.53 | 11.73 | 5.93 | +| CMCC | 12.75 | - | 8.75 | 8.93 | 9.67 | 13.47 | 11.87 | 14.47 | +| NTT DOCOMO | - | - | 6.40 | 6.10 | 3.18 | 3.70 | 3.96 | 5.03 | +| CATT | 8.47 | - | 4.17 | 2.67 | 1.37 | 3.37 | -0.13 | 3.17 | +| OPPO | 7.17 | - | 7.07 | 7.37 | 6.87 | 7.77 | 3.20 | 7.27 | +| Panasonic | - | - | 7.08 | 6.68 | 6.18 | 6.48 | - | - | +| Mavenir | - | - | - | 3.45 | 1.16 | 0.58 | - | - | +| Xiaomi | -0.61 | - | 0.53 | 0.03 | -4.47 | -5.17 | -4.25 | -1.52 | +| Huawei | 1.53 | - | 5.63 | 5.53 | 5.33 | 0.93 | 0.93 | 2.13 | +| Lenovo | 5.50 | - | - | 8.21 | - | 5.61 | - | - | +| Intel | 11.37 | - | 5.47 | 4.97 | 2.47 | 3.07 | 3.47 | 3.87 | +| Qualcomm | 11.11 | - | 6.41 | 6.31 | 4.31 | 5.61 | 4.11 | 3.91 | +| Representative value 1 | 7.81 | N/A | 5.75 | 5.66 | 4.04 | 3.97 | 3.77 | 4.39 | +| # of samples 1 | 11 | 3 | 13 | 15 | 13 | 15 | 13 | 13 | +| Representative value 2 | 8.07 | N/A | 5.97 | 5.69 | 3.95 | 3.88 | 3.80 | 4.51 | +| # of samples 2 | 12 | 3 | 15 | 18 | 16 | 18 | 14 | 14 | + +**Table 8.2.2-3 (part 2): In Rural scenario at 0.7GHz, coverage margins for the potential Rel-18 UE with maximum 11-PRB bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.2-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin(dB) | PDCCH USS (BW1, 25 PRBs; CORESET: 3 symbols, 24 PRBs; AL8) | PDSCH (BW1, 25 PRBs; 0.25 Mbps) | PRACH Format 0 (BW1, 25 PRBs) | Msg3 (BW1, 25 PRBs) | PUSCH (BW1, 25 PRBs; 25 kbps) | PUCCH 2bit (BW1, 25 PRBs) | PUCCH 11bit (BW1, 25 PRBs) | PUCCH 22 bits (BW1, 25 PRBs) | +|-------------------------------|------------------------------------------------------------|---------------------------------|-------------------------------|---------------------|-------------------------------|---------------------------|----------------------------|------------------------------| +| MediaTek | 6.17 | 5.87 | - | - | - | - | - | - | +| Spreadtrum | 7.57 | 6.07 | 3.37 | 2.11 | -3.00 | 4.42 | 3.12 | 1.92 | +| ZTE | 6.15 | 14.95 | - | -2.60 | 2.58 | 7.70 | 5.20 | 2.70 | +| Ericsson | 2.17 | 4.43 | 1.97 | -0.99 | 0.22 | 1.90 | 3.91 | 1.39 | +| Samsung | 5.27 | 3.17 | - | 0.01 | 0.41 | 9.22 | 4.62 | 2.32 | +| vivo | - | - | - | - | - | - | - | - | +| Nokia | 8.23 | 6.13 | - | -0.69 | 0.52 | - | - | - | +| CMCC | 8.93 | 14.37 | 6.64 | 4.54 | 1.95 | 8.45 | 6.84 | 4.54 | +| NTT DOCOMO | 6.10 | 6.08 | - | -0.18 | 1.36 | 3.92 | 7.78 | - | +| CATT | 2.67 | 5.07 | 0.77 | -1.79 | -3.00 | 7.22 | 4.42 | 1.72 | +| OPPO | - | - | - | - | - | - | - | - | +| Panasonic | - | - | - | - | - | - | - | - | +| Mavenir | - | - | - | - | - | - | - | - | +| Xiaomi | 0.03 | -2.07 | - | -0.91 | -0.31 | - | - | - | +| Huawei | 5.53 | 1.73 | 6.27 | 0.52 | -0.09 | 8.02 | 5.77 | - | +| Lenovo | - | - | - | 1.25 | - | - | - | - | +| Intel | 4.97 | 3.57 | - | 0.86 | 2.32 | - | - | - | +| Qualcomm | - | 5.61 | - | -0.49 | 0.02 | - | - | -0.5 | +| Representative value 1 | 5.41 | 5.62 | 3.87 | -0.03 | 0.34 | 6.62 | 5.13 | 2.01 | +| # of samples 1 | 11 | 12 | 5 | 13 | 12 | 8 | 8 | 7 | +| Representative value 2 | 5.48 | 5.65 | 3.87 | -0.03 | 0.34 | 6.62 | 5.13 | 2.01 | +| # of samples 2 | 12 | 13 | 5 | 13 | 12 | 8 | 8 | 7 | + +In Rural scenario at 0.7GHz with maximum 25-PRB UE bandwidth for the potential Rel-18 UE, for evaluation of PDCCH CSS/SIB1 coverage impact particularly from the coexistence perspective, the comparison between the potential Rel-18 UE and the reference NR UE in addition to the comparison between the potential Rel-18 UE and the Rel-17 RedCap UE by sourcing companies are summarized in Table 8.2.2-6. It is noted that the target BLER of PDCCH CSS is 1% and the target BLER of SIB1 is 10% in the evaluation. In addition, one-shot decoding is assumed for both PDCCH CSS and SIB1 in all cases in Table 8.2.2-6. + +For the comparison of PDCCH CSS/SIB1 coverage differences between the potential Rel-18 UE with maximum 25-PRB UE bandwidth and the reference Rel-15 NR UE, the configurations and evaluation assumptions are listed as in the following. + +- The potential Rel-18 UE is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- The reference Rel-15 NR UE for comparison is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- The potential Rel-18 UE is scheduled with SIB1 larger than 5MHz. +- The reference Rel-15 NR UE for comparison is scheduled with SIB1 larger than 5MHz. + +- The exact PRB numbers and MCS values are reported by sourcing companies in [7]. + +For the comparison of PDCCH CSS/SIB1 coverage differences between the potential Rel-18 UE and the reference Rel-17 RedCap UE, the configurations and evaluations assumptions are listed in the following. + +- The potential Rel-18 UE is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- The reference Rel-17 RedCap UE for comparison is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- The potential Rel-18 UE is configured with PDCCH CSS with AL8 and CORESET of 24 PRBs and 3 OFDM symbols. +- The reference Rel-17 RedCap UE for comparison is configured with PDCCH CSS with AL16 and CORESET of 48 PRBs and 2 OFDM symbols. +- It is noted this pair of comparison can provide the following two aspects: + - The PDCCH CSS coverage difference between the potential Rel-18 UE and the reference Rel-17 RedCap if a dedicated PDCCH CSS that is confined within 5MHz is transmitted for the potential Rel-18 UE. + - The PDCCH CSS coverage loss for the reference Rel-17 RedCap UE if a universal PDCCH CSS that is confined within 5MHz to accommodate the maximum bandwidth of the potential Rel-18 UE is transmitted for both the potential Rel-18 UE and the reference Rel-17 RedCap UE. +- The potential Rel-18 UE is scheduled with SIB1 larger than 5MHz. + - The reference Rel-17 RedCap UE for comparison is scheduled with SIB1 larger than 5MHz. + - For both cases, the exact PRB numbers and MCS values are reported by sourcing companies in [7]. +- The potential Rel-18 UE is scheduled with SIB1 within 5MHz. + - The reference Rel-17 RedCap UE for comparison is scheduled with SIB1 larger than 5MHz. + - For both cases, the exact PRB numbers and MCS values are reported by sourcing companies in [7]. + - It is noted this pair of comparison can provide the following two aspects: + - The SIB1 coverage difference between the potential Rel-18 UE and the reference Rel-17 RedCap if a dedicated SIB1 within 5MHz is transmitted for the potential Rel-18 UE. + - The SIB1 coverage loss for the reference Rel-17 RedCap UE if a universal SIB1 that is confined within 5MHz to accommodate the maximum bandwidth of the potential Rel-18 UE is transmitted for both the potential Rel-18 UE and the reference Rel-17 RedCap UE. + +For all the cases listed above, one-shot decoding without any soft combining was assumed for this evaluation to represent the coverage differences between the potential Rel-18 UE and the reference Rel-15 NR UE and between the potential Rel-18 UE and the reference Rel-17 RedCap UE before applying any coverage enhancement schemes. + +The representative values in the last row of Table 8.2.2-6 are derived by taking the mean value (in dB domain) from all the companies results after excluding the highest and the lowest values. In Rural scenario at 0.7GHz with maximum 25-PRB UE bandwidth for the potential Rel-18 UE, from the representative values in the last row of Table 8.2.2-6, the following observations can be made: + +- Observation 1: for PDCCH CSS with AL16 and 48PRB and 2 symbols, performance degradation of the potential Rel-18 UE is 7.30 dB and 3.53 dB compared with Rel-15 NR UE and Rel-17 RedCap UE, respectively. +- Observation 2: for SIB1 greater than 5MHz, performance degradation of the potential Rel-18 UE is 7.57 dB and 3.93 dB compared with Rel-15 NR UE and Rel-17 RedCap UE, respectively. + +**Table 8.2.2-6: In Rural scenario at 0.7GHz with 15kHz SCS, the comparisons of PDCCH CSS and SIB1 coverage differences between the potential Rel-18 UE and reference Rel-15 NR UE as well as those between the potential Rel-18 UE and the reference Rel-17 RedCap UE where one-shot decoding is assumed for all cases and maximum UE bandwidth of 25 PRBs is assumed for the potential Rel-18 UE. (Unit: dB)** + +| Coverage Difference (dB) | | Comparison with reference Rel-15 NR UE (MIL) | | Comparison with reference Rel-17 RedCap UE (MIL) | | | | +|----------------------------------|------------|-----------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------| +| | | PDCCH CSS AL16 | SIB1 > 5MHz | PDCCH CSS (48 RBs) with 1% BLER | PDCCH CSS (24 RBs) with 1% BLER | SIB1 (>5 MHz) with 10% BLER | SIB1 (<5 MHz) with 10% BLER | +| Sourcing company | T-doc | 5MHz-UE (BW1, 25 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | 5MHz-UE (BW1, 25 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | 5MHz-UE (BW1, 25 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | 5MHz-UE (BW1, 25 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | 5MHz-UE (BW1, 25 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | 5MHz-UE (BW1, 25 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | +| CATT | R1-2207969 | -8.40 | -8.00 | -4.70 | -6.20 | -4.90 | -2.90 | +| Intel | R1-2207740 | -6.50 | -7.60 | -3.10 | -3.60 | -4.20 | -3.60 | +| Ericsson | R1-2207741 | -10.10 | -8.54 | -6.30 | -4.70 | -4.57 | -3.59 | +| NTT DOCOMO | R1-2207692 | -6.39 | -7.92 | -3.08 | -3.38 | -4.41 | -3.89 | +| Nokia NSB | R1-2206444 | -7.10 | -6.40 | -3.40 | -4.00 | -2.90 | -4.4 | +| ZTE | R1-2207058 | -4.80 | -6.70 | -1.40 | -4.20 | -3.00 | -1.90 | +| Qualcomm | R1-2207244 | -7.70 | | -3.90 | -4.00 | -3.80 | -3.80 | +| vivo | R1-2206052 | -6.31 | -6.77 | -2.94 | -3.98 | -2.67 | -5.62 | +| OPPO | R1-2206304 | -7.68 | -7.00 | -3.08 | -2.78 | -3.60 | -2.70 | +| MediaTek | R1-2207003 | -6.90 | -7.30 | -3.00 | -2.90 | -3.80 | -3.90 | +| CMCC | R1-2206294 | -8.31 | -8.90 | -4.25 | -5.36 | -5.30 | -1.50 | +| Huawei, Hisilicon | R1-2205874 | -6.83 | | -3.48 | | | | +| Panasonic | R1-2206437 | -8.2 | -8.3 | -3.9 | | -4.1 | -3.8 | +| Representative value (dB) | | -7.30 | -7.57 | -3.53 | -4.52 | -3.93 | -3.45 | + +### 8.2.3 Urban scenario at 4 GHz + +For this Urban scenario at 4 GHz, sourcing companies could optionally report evaluation results with maximum 11-PRB UE bandwidth under different under different downlink power spectrum density (PSD) assumptions of 33dBm/MHz and/or 24dBm/MHz . + +For Urban scenario at 4 GHz with downlink power spectrum density of 33dBm/MHz, the bottleneck channel for the reference NR UE and the corresponding maximum isotropic loss (MIL) value by the sourcing companies [7] are shown in Table 8.2.3-1. + +As can be seen from Table 8.2.3-1, for Urban scenario at 4 GHz, PUSCH is the bottleneck channel for the reference NR UE. + +**Table 8.2.3-1: Bottleneck channels and MIL values for the reference NR UE in Urban scenario at 4GHz with downlink power spectrum density of 33 dBm/MHz** + +| Company | Bottleneck Channel | MIL (dB) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------| +| Ericsson | PUSCH | 139.24 | +| Samsung | PUSCH | 142.04 | +| vivo | PUSCH | 139.62 | +| Nokia | PUSCH | 142.12 | +| MediaTek | PUSCH (*) | 143.54 | +| CATT | PUSCH | 145.14 | +| Huawei | PUSCH | 140.03 | +| Lenovo | PUSCH | 143.53 | +| Intel | PUSCH | 141.19 | +| Qualcomm | PUSCH | 139.99 | +| NOTE: For a sourcing company labeled with (*) that did not provide evaluation results for uplink channels for the reference NR UE, the bottleneck channel and its representative MIL value were derived from Table 9.1.3-1 of TR 38.875 based on the methodology in Clause 6.2. | | | + +In Urban scenario at 4 GHz with DL PSD of 33dBm/MHz, for the potential Rel-18 UE with maximum 11-PRB bandwidth, the coverage margins relative to the bottleneck channel of the reference NR UE are summarized in Table 8.2.3-2 (part 1 and part 2) and Table 8.2.3-3 (part 1 and part 2). In Table 8.2.3-2, no UE antenna efficiency loss is assumed for the potential Rel-18 UE. In Table 8.2.3-3, UE antenna efficiency loss of 3dB is assumed in both DL and UL for the potential Rel-18 UE. For every sourcing-company result, the coverage margin for each channel that has MIL below the bottleneck channel for the reference NR UE is highlighted in red. + +The representative value 1, number of samples 1, representative value 2, and number of samples 2 in the last four rows of Table 8.2.3-2 and Table 8.2.3-3 are determined according to the methodology described in clause 6.2. A negative representative value for a channel of the potential Rel-18 UE indicates the coverage of the channel is worse than that of the bottleneck channel of the reference NR UE. + +As can be seen from the representative values in Table 8.2.3-2 and Table 8.2.2-3, for Urban scenario at 4 GHz with DL PSD of 33 dBm/MHz and maximum 11-PRB UE bandwidth: + +- Without 3-dB UE antenna efficiency loss: the representative values of the coverage margins for the potential Rel-18 UE with 11-PRB BW for all channels are positive. +- With 3-dB UE antenna efficiency loss: the representative values of the coverage margins for the potential Rel-18 UE with 11-PRB BW for all channels are positive. It is noted that PDCCH CSS with AL2, SIB1 and PUSCH have slightly better coverage by less than 2dB than the bottleneck channel of the reference NR UE. + +It is noted that results of individual sourcing companies show that Urban scenario at 4 GHz with 33 dBm/MHz DL PSD follows similar trend as the Urban scenario at 2.6 GHz with 33 dBm/MHz DL PSD. + +As can be seen from the representative values in Table 8.2.3-2 and Table 8.2.3-3, PUSCH for the potential Rel-18 UE, with or without 3dB UE antenna efficiency loss, has better coverage than the bottleneck channel of the reference NR UE and hence coverage recovery is not needed for PUSCH. This is because the cell-edge target data rates are scaled by a factor of 0.25 for the potential Rel-18 UE compared to the reference Rel-17 RedCap UE. + +Table 8.2.3-2 (part 1): In Urban scenario at 4GHz with DL PSD of 33 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | SIB1 BW>5MHz (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 11 PRBs; TBS 72 bits) | Msg4 (BW1, 11 PRBs; TBS 1040 bits) | +|-------------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| Ericsson | 6.63 | - | 4.63 | 4.53 | -2.37 | -4.33 | -1.02 | 4.78 | -0.07 | +| Samsung | - | - | - | - | 4.93 | - | 2.93 | 11.53 | 4.73 | +| vivo | 7.56 | 12.71 | 10.87 | 9.38 | 7.31 | 8.85 | 8.52 | - | - | +| Nokia | 16.09 | - | 13.09 | 13.09 | 9.09 | 9.79 | 9.29 | 22.49 | 8.59 | +| MediaTek | 12.43 | - | 7.33 | 6.73 | 2.63 | 1.73 | 4.53 | 9.13 | 5.33 | +| CATT | 10.13 | - | 4.73 | 2.33 | -1.17 | 0.13 | 1.93 | 5.43 | 3.13 | +| Huawei | 15.53 | - | 11.73 | 11.43 | 7.23 | 17.53 | 13.33 | 14.23 | 9.53 | +| Lenovo | 8.13 | - | - | - | 4.44 | - | 3.63 | - | - | +| Intel | 16.82 | - | 4.05 | - | 5.07 | 0.87 | 4.57 | 11.27 | 6.17 | +| Qualcomm | 12.15 | - | - | - | 2.55 | 2.15 | 2.45 | 8.95 | 3.85 | +| Representative value 1 | 11.60 | N/A | 7.99 | 8.45 | 4.34 | 4.36 | 4.76 | 10.28 | 5.29 | +| # of samples 1 | 8 | 1 | 6 | 5 | 9 | 7 | 9 | 7 | 7 | +| Representative value 2 | 11.72 | N/A | 7.86 | 8.02 | 4.12 | 3.92 | 4.73 | 10.09 | 5.30 | +| # of samples 2 | 9 | 1 | 7 | 6 | 10 | 8 | 10 | 8 | 8 | + +Table 8.2.3-2 (part 2): In Urban scenario at 4GHz with DL PSD of 33 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-1 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin (dB) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 11 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 11 PRBs) | PRACH C2 (BW1, 11 PRBs) | Msg3 (BW1, 11 PRBs) | PUSCH (BW1, 11 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 11 PRBs) | PUCCH 11bit (BW1, 11 PRBs) | PUCCH 22 bits (BW1, 11 PRBs) | +|----------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| Ericsson | 1.63 | 5.73 | 9.92 | 15.56 | - | 11.96 | 5.66 | 11.05 | 16.48 | 14.55 | +| Samsung | 8.93 | 14.13 | 15.93 | - | - | 7.96 | 3.64 | 17.57 | 12.87 | 10.47 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| Nokia | 9.09 | 13.59 | 15.79 | - | - | 9.76 | 4.04 | - | - | - | +| MediaTek | 5.03 | 11.23 | 14.93 | - | - | - | - | - | - | - | +| CATT | 2.83 | 7.23 | 11.63 | 9.76 | - | 7.66 | 5.36 | 15.07 | 13.67 | 11.87 | +| Huawei | 7.23 | 12.13 | 14.73 | 8.30 | 8.40 | 13.63 | 5.40 | 20.49 | 18.19 | - | +| Lenovo | - | - | - | - | - | 10.67 | - | - | - | - | +| Intel | 6.24 | 11.74 | 10.24 | - | - | 12.30 | 5.59 | - | - | - | +| Qualcomm | - | - | 14.65 | - | - | 7.04 | 4.51 | - | - | 6.55 | + +| | | | | | | | | | | | +|------------------------|------|-------|-------|-----|-----|-------|------|-------|-------|-------| +| Representative value 1 | 6.31 | 11.17 | 13.41 | N/A | N/A | 10.05 | 4.98 | 16.32 | 15.08 | 11.17 | +| # of samples 1 | 6 | 6 | 7 | 3 | 1 | 8 | 7 | 4 | 4 | 4 | +| Representative value 2 | 6.05 | 11.18 | 13.66 | N/A | N/A | 10.05 | 4.98 | 16.32 | 15.08 | 11.17 | +| # of samples 2 | 7 | 7 | 8 | 3 | 1 | 8 | 7 | 4 | 4 | 4 | + +Table 8.2.3-3 (part 1): In Urban scenario at 4GHz with DL PSD of 33 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | SIB1 BW>5MHz (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 11 PRBs; TBS 72 bits) | Msg4 (BW1, 11 PRBs; TBS 1040 bits) | +|------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| Ericsson | 3.63 | - | 1.63 | 1.53 | -5.37 | -7.33 | -4.02 | 1.78 | -3.07 | +| Samsung | - | - | - | - | 1.93 | - | -0.07 | 8.53 | 1.73 | +| vivo | 4.56 | 9.71 | 7.87 | 6.38 | 4.31 | 5.85 | 5.52 | - | - | +| Nokia | 13.09 | - | 10.09 | 10.09 | 6.09 | 6.79 | 6.29 | 19.49 | 5.59 | +| MediaTek | 9.43 | - | 4.33 | 3.73 | -0.37 | -1.27 | 1.53 | 6.13 | 2.33 | +| CATT | 7.13 | - | 1.73 | -0.67 | -4.17 | -2.87 | -1.07 | 2.43 | 0.13 | +| Huawei | 12.53 | - | 8.73 | 8.43 | 4.23 | 14.53 | 10.33 | 11.23 | 6.53 | +| Lenovo | 5.13 | - | - | - | 1.44 | - | 0.63 | - | - | +| Intel | 13.82 | - | 1.05 | - | 2.07 | -2.13 | 1.57 | 8.27 | 3.17 | +| Qualcomm | 9.15 | - | - | - | -0.45 | -0.85 | -0.55 | 5.95 | 0.85 | +| Representative value 1 | 8.60 | N/A | 4.99 | 5.45 | 1.34 | 1.36 | 1.76 | 7.28 | 2.29 | +| # of samples 1 | 8 | 1 | 6 | 5 | 9 | 7 | 9 | 7 | 7 | +| Representative value 2 | 8.72 | N/A | 4.86 | 5.02 | 1.12 | 0.92 | 1.73 | 7.09 | 2.30 | +| # of samples 2 | 9 | 1 | 7 | 6 | 10 | 8 | 10 | 8 | 8 | + +Table 8.2.3-4 (part 2): In Urban scenario at 4GHz with DL PSD of 33 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-1 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 11 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 11 PRBs) | PRACH C2 (BW1, 11 PRBs) | Msg3 (BW1, 11 PRBs) | PUSCH (BW1, 11 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 11 PRBs) | PUCCH 11bit (BW1, 11 PRBs) | PUCCH 22 bits (BW1, 11 PRBs) | +|---------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| Ericsson | -1.37 | 2.73 | 6.92 | 12.56 | - | 8.96 | 2.66 | 8.05 | 13.48 | 11.55 | +| Samsung | 5.93 | 11.13 | 12.93 | - | - | 4.96 | 0.64 | 14.57 | 9.87 | 7.47 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| Nokia | 6.09 | 10.59 | 12.79 | - | - | 6.76 | 1.04 | - | - | - | +| MediaTek | 2.03 | 8.23 | 11.93 | - | - | - | - | - | - | - | + +| | | | | | | | | | | | +|-------------------------------|--------------|-------------|--------------|------------|------------|-------------|-------------|--------------|--------------|-------------| +| CATT | -0.17 | 4.23 | 8.63 | 6.76 | - | 4.66 | 2.36 | 12.07 | 10.67 | 8.87 | +| Huawei | 4.23 | 9.13 | 11.73 | 5.30 | 5.40 | 10.63 | 2.40 | 17.49 | 15.19 | - | +| Lenovo | - | - | - | - | - | 7.67 | - | - | - | - | +| Intel | 3.24 | 8.74 | 7.24 | - | - | 9.30 | 2.59 | - | - | - | +| Qualcomm | - | - | 11.65 | - | - | 4.04 | 1.51 | - | - | 3.55 | +| Representative value 1 | 3.31 | 8.17 | 10.41 | N/A | N/A | 7.05 | 1.98 | 13.32 | 12.08 | 8.17 | +| # of samples 1 | 6 | 6 | 7 | 3 | 1 | 8 | 7 | 4 | 4 | 4 | +| Representative value 2 | 3.05 | 8.18 | 10.66 | N/A | N/A | 7.05 | 1.98 | 13.32 | 12.08 | 8.17 | +| # of samples 2 | 7 | 7 | 8 | 3 | 1 | 8 | 7 | 4 | 4 | 4 | + +For Urban scenario at 4 GHz with downlink power spectrum density of 24 dBm/MHz, the bottleneck channel for the reference NR UE and the corresponding maximum isotropic loss (MIL) value by the sourcing companies [7] are shown in Table 8.2.3-4. For the potential Rel-18 UE with maximum 11-PRB bandwidth, the coverage margins relative to the bottleneck channel of the reference NR UE are summarized in Table 8.2.3-5 (part 1 and part 2) and Table 8.2.3-6 (part 1 and part 2). In Table 8.2.3-5, no UE antenna efficiency loss is assumed for the potential Rel-18 UE. In Table 8.2.3-6, UE antenna efficiency loss of 3dB is assumed in both DL and UL for the potential Rel-18 UE. For every sourcing-company result, the coverage margin for each channel that has MIL below the bottleneck channel for the reference NR UE is highlighted in red. + +As can be seen from Table 8.2.3-1 and Table 8.2.3-4, for Urban scenario at 4 GHz, when DL PSD is reduced from 33dBm/MHz to 24dBm/MHz, PUSCH is still the bottleneck channel for the reference NR UE. This implies for the reference NR UE all downlink channels have more link budgets than PUSCH by at least 9dB when DL PSD is 33dBm/MHz. + +**Table 8.2.3-4: Bottleneck channels and MIL values for the reference NR UE in Urban scenario at 4GHz with downlink power spectrum density of 24 dBm/MHz** + +| Company | Bottleneck Channel | MIL (dB) | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Ericsson | PUSCH | 139.24 | +| Samsung | PUSCH | 142.04 | +| vivo | PUSCH | 139.62 | +| MediaTek | PUSCH (*) | 143.54 | +| CATT | PUSCH | 145.14 | +| Huawei | PUSCH | 140.03 | +| Intel | PUSCH | 141.19 | +| Qualcomm | PUSCH | 139.99 | +| NOTE: | For a sourcing company labeled with (*) that did not provide evaluation results for uplink channels for the reference NR UE, the bottleneck channel and its MIL value were derived from Table 9.1.3-1 of TR 38.875 based on the methodology in Clause 6.2. | | + +As can be seen from the representative values in Table 8.2.3-5 and Table 8.2.3-6, for Urban scenario at 4 GHz with DL PSD of 24 dBm/MHz and maximum 11-PRB UE bandwidth: + +- Without 3-dB UE antenna efficiency loss: PDCCH CSS, SIB1, Msg4, and PDCCH USS with AL2 have worse coverage than the bottleneck channel of the reference NR UE. For other downlink channels, PBCH, Msg2, and PDCCH USS with AL4, the coverage margins are less than 3dB. Only PDSCH has a coverage margin slightly more than 3dB than the bottleneck channel. +- With 3-dB UE antenna efficiency loss: PBCH, PDCCH CSS, SIB1, Msg2, Msg4, and PDCCH USS all show worse coverage than the bottleneck channel of the reference NR UE. PDSCH has a similar coverage to the bottleneck channel. + +Like other scenario, it again can be seen from the representative values in Table 8.2.3-5 and Table 8.2.3-6, PUSCH for the potential Rel-18 UE, with or without 3dB UE antenna efficiency loss, has better coverage than the bottleneck channel of the reference NR UE and hence coverage recovery is not needed for PUSCH. This is because the cell-edge target data rates are scaled by a factor of 0.25 for the potential Rel-18 UE compared to the reference Rel-17 RedCap UE. + +**Table 8.2.3-5 (part 1): In Urban scenario at 4GHz with DL PSD of 24 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-4 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | SIB1 BW>5MHz (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 11 PRBs; TBS 72 bits) | Msg4 (BW1, 11 PRBs; TBS 1040 bits) | +|-------------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| Ericsson | -2.37 | - | -4.37 | -4.47 | -11.37 | -13.33 | - | -4.22 | -9.07 | +| Samsung | - | - | - | - | -4.07 | - | -6.07 | 2.53 | -4.27 | +| vivo | -1.44 | 3.71 | 1.87 | 0.38 | -1.69 | -0.15 | -0.48 | - | - | +| MediaTek | 3.43 | - | -1.67 | -2.27 | -6.37 | -7.27 | -4.47 | 0.13 | -3.67 | +| CATT | 1.13 | - | -4.27 | -6.67 | -10.17 | -8.87 | -7.07 | -3.57 | -5.87 | +| Huawei | 6.53 | - | 2.73 | 2.43 | -1.77 | 8.53 | 4.33 | 5.23 | 0.53 | +| Intel | 7.82 | - | 0.97 | -0.13 | -3.93 | -8.13 | -4.43 | 2.27 | -2.83 | +| Representative value 1 | 2.07 | N/A | -0.48 | -1.41 | -4.99 | -5.72 | -3.66 | 0.41 | -4.32 | +| # of samples 1 | 5 | 1 | 5 | 5 | 6 | 5 | 5 | 5 | 5 | +| Representative value 2 | 2.41 | N/A | -0.78 | -1.62 | -5.26 | -6.11 | -3.86 | 0.34 | -4.16 | +| # of samples 2 | 6 | 1 | 6 | 6 | 7 | 6 | 6 | 6 | 6 | + +**Table 8.2.3-5 (part 2): In Urban scenario at 4GHz with DL PSD of 24 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-4 when no UE antenna efficiency loss is assumed for the potential Rel-18 UE.** + +| Coverage margin (dB) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 11 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 11 PRBs) | PRACH C2 (BW1, 11 PRBs) | Msg3 (BW1, 11 PRBs) | PUSCH (BW1, 11 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 11 PRBs) | PUCCH 11bit (BW1, 11 PRBs) | PUCCH 22 bits (BW1, 11 PRBs) | +|-------------------------------|-----------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| Ericsson | -7.37 | -3.27 | 0.92 | 15.56 | - | 11.96 | 5.66 | 11.05 | 16.48 | 14.55 | +| Samsung | -0.07 | 5.13 | 6.93 | - | - | 7.96 | 3.64 | 17.57 | 12.87 | 10.47 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| MediaTek | -3.97 | 2.23 | 5.93 | - | - | - | - | - | - | - | +| CATT | -6.17 | -1.77 | 2.63 | 9.76 | - | 7.66 | 5.36 | 15.07 | 13.67 | 11.67 | +| Huawei | -1.77 | 3.13 | 5.73 | 8.30 | 8.40 | 13.63 | 5.40 | 20.49 | 18.19 | - | +| Intel | -2.76 | 2.74 | 1.24 | - | - | 12.30 | 5.59 | - | - | - | +| Representative value 1 | -3.57 | 1.37 | 3.20 | N/A | N/A | 10.74 | 5.45 | 16.32 | 15.08 | N/A | + +| | | | | | | | | | | | +|------------------------|-------|------|------|-----|-----|-------|------|-------|-------|-----| +| # of samples 1 | 5 | 5 | 5 | 3 | 1 | 5 | 5 | 4 | 4 | 3 | +| Representative value 2 | -3.67 | 1.58 | 3.88 | N/A | N/A | 10.74 | 5.45 | 16.32 | 15.08 | N/A | +| # of samples 2 | 6 | 6 | 6 | 3 | 1 | 5 | 5 | 4 | 4 | 3 | + +Table 8.2.3-6 (part 1): In Urban scenario at 4GHz with DL PSD of 24 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-4 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PBCH target BLER1% | PBCH target BLER10% | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | PDCCH CSS (BW1, 11 PRBs; CORESET: 2 symbols, 24 PRBs; AL8) | PDCCH CSS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2) | SIB1 BW>5MHz (BW1, 11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | SIB1 (BW1, 11 PRBs; SIB1 BW < 5 MHz; TBS 1256 bits) | Msg2 (BW1, 11 PRBs; TBS 72 bits) | Msg4 (BW1, 11 PRBs; TBS 1040 bits) | +|------------------------|--------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------|-------------------------------------------------------------|-----------------------------------------------------|----------------------------------|------------------------------------| +| Ericsson | -5.37 | - | -7.37 | -7.47 | -14.37 | -16.33 | - | -7.22 | -12.07 | +| Samsung | - | - | - | - | -7.07 | - | -9.07 | -0.47 | -7.27 | +| vivo | -4.44 | 0.71 | -1.13 | -2.62 | -4.69 | -3.15 | -3.48 | - | - | +| MediaTek | 0.43 | - | -4.67 | -5.27 | -9.37 | -10.27 | -7.47 | -2.87 | -6.67 | +| CATT | -1.87 | - | -7.27 | -9.67 | -13.17 | -11.87 | -10.07 | -6.57 | -8.87 | +| Huawei | 3.53 | - | -0.27 | -0.57 | -4.77 | 5.53 | 1.33 | 2.23 | -2.47 | +| Intel | 4.82 | - | -2.03 | -3.13 | -6.93 | -11.13 | -7.43 | -0.73 | -5.83 | +| Representative value 1 | -0.93 | N/A | -3.48 | -4.41 | -7.99 | -8.72 | -6.66 | -2.59 | -7.32 | +| # of samples 1 | 5 | 1 | 5 | 5 | 6 | 5 | 5 | 5 | 5 | +| Representative value 2 | -0.59 | N/A | -3.78 | -4.62 | -8.26 | -9.11 | -6.86 | -2.66 | -7.16 | +| # of samples 2 | 6 | 1 | 6 | 6 | 7 | 6 | 6 | 6 | 6 | + +Table 8.2.3-6 (part 2): In Urban scenario at 4GHz with DL PSD of 24 dBm/MHz, the coverage margins of the potential Rel-18 UE with maximum 11-PRB UE bandwidth compared to the bottleneck channel for the reference NR UE in Table 8.2.3-4 when 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE. + +| Coverage margin(dB) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 6 PRBs; AL2; baseline) | PDCCH USS (BW1, 11 PRBs; CORESET: 3 symbols, 12 PRBs; AL4) | PDSCH (BW1, 11 PRBs; 0.5 Mbps) | PRACH B4 (BW1, 11 PRBs) | PRACH C2 (BW1, 11 PRBs) | Msg3 (BW1, 11 PRBs) | PUSCH (BW1, 11 PRBs; 0.25 Mbps) | PUCCH 2bit (BW1, 11 PRBs) | PUCCH 11bit (BW1, 11 PRBs) | PUCCH 22 bits (BW1, 11 PRBs) | +|------------------------|---------------------------------------------------------------------|------------------------------------------------------------|--------------------------------|-------------------------|-------------------------|---------------------|---------------------------------|---------------------------|----------------------------|------------------------------| +| Ericsson | -10.37 | -6.27 | -2.08 | 12.56 | - | 8.96 | 2.66 | 8.05 | 13.48 | 11.55 | +| Samsung | -3.07 | 2.13 | 3.93 | - | - | 4.96 | 0.64 | 14.57 | 9.87 | 7.47 | +| vivo | - | - | - | - | - | - | - | - | - | - | +| MediaTek | -6.97 | -0.77 | 2.93 | - | - | - | - | - | - | - | +| CATT | -9.17 | -4.77 | -0.37 | 6.76 | - | 4.66 | 2.36 | 12.07 | 10.67 | 8.67 | +| Huawei | -4.77 | 0.13 | 2.73 | 5.30 | 5.40 | 10.63 | 2.40 | 17.49 | 15.19 | - | +| Intel | -5.76 | -0.26 | -1.76 | - | - | 9.30 | 2.59 | - | - | - | +| Representative value 1 | -6.57 | -1.63 | 0.20 | N/A | N/A | 7.74 | 2.45 | 13.32 | 12.08 | N/A | +| # of samples 1 | 5 | 5 | 5 | 3 | 1 | 5 | 5 | 4 | 4 | 3 | + +| | | | | | | | | | | | +|-------------------------------|--------------|--------------|-------------|------------|------------|-------------|-------------|--------------|--------------|------------| +| Representative value 2 | -6.67 | -1.42 | 0.88 | N/A | N/A | 7.74 | 2.45 | 13.32 | 12.08 | N/A | +| # of samples 2 | 6 | 6 | 6 | 3 | 1 | 5 | 5 | 4 | 4 | 3 | + +### 8.2.4 Summary of coverage impact evaluation + +In the coverage evaluation in Clause 8.2.1 through Clause 8.2.3, we have assumed the potential Rel-18 is a UE with maximum bandwidth reduced to 5MHz in both RF and BB, i.e., the BW1 complexity reduction option described in Clause 7.2, and have studied the corresponding coverage impact in different deployment scenarios. + +When comparing to the bottleneck channels of the reference NR UE, the evaluation results on coverage margins in clauses 8.2.1 through 8.2.3 can be summarized as follows for the potential Rel-18 UE with BW1 complexity reduction option. + +- For Urban scenario at 2.6 GHz with 11-PRB UE BW and DL PSD of 33 dBm/MHz: + - Without 3dB antenna efficiency loss: all channels have positive coverage margins + - With 3dB antenna efficiency loss: all channels have positive coverage margins except for PDCCH CSS with AL2 and SIB1. Both are slightly worse than the bottleneck channel of the reference NR UE by less than 1dB. +- For Urban scenario at 2.6 GHz with 12-PRB UE BW and DL PSD of 33 dBm/MHz: + - All channels have positive coverage margins with or without 3dB antenna efficiency loss. +- For Rural scenario at 0.7 GHz: + - Without 3dB antenna efficiency loss: all channels have positive coverage margins + - With 3dB antenna efficiency loss: all channels have positive coverage margins except for Msg3 which is worse than the bottleneck channel by less than 0.1dB. +- For Urban scenario at 4 GHz with 11-PRB UE BW and DL PSD of 33 dBm/MHz + - Without 3dB UE antenna efficiency loss: all channels have positive coverage margins. + - With 3dB UE antenna efficiency loss: all channels have positive coverage margins. It is noted that PDCCH CSS with AL2, SIB1 and PUSCH have slightly better coverage by less than 2dB than the bottleneck channel of the reference NR UE. + - It is noted that results of individual sourcing companies show that Urban scenario at 4 GHz with 33 dBm/MHz DL PSD follows similar trends as the Urban scenario at 2.6 GHz with 33 dBm/MHz DL PSD. +- For Urban scenario at 4 GHz with 11-PRB UE BW and DL PSD of 24 dBm/MHz: + - Without 3dB antenna efficiency loss: PDCCH CSS, SIB1, Msg4, and PDCCH USS with AL2 have worse coverage than the bottleneck channel of the reference NR UE. + - With 3dB UE antenna efficiency loss: PBCH, PDCCH CSS, SIB1, Msg2, Msg4, and PDCCH USS all show worse coverage than the bottleneck channel of the reference NR UE. + +Based on the above summary on coverage margins for complexity reduction option BW1, we know that the determination of which channels have worse coverage than the bottleneck channel of reference NR UE, and the amount of coverage margins, would depend on the deployment scenario, on whether the 3dB UE antenna efficiency loss is assumed for the potential Rel-18 UE, and the value of DL PSD. It is also noted that PUSCH for the potential Rel-18 UE, with or without 3dB UE antenna efficiency loss, has better coverage than the bottleneck channel of the reference NR UE. This is because the cell-edge target data rates are scaled by a factor of 0.25 for the potential Rel-18 UE compared to the reference Rel-17 RedCap UE. + +The coverage evaluation results based on complexity reduction option BW1 are further extended to other complexity reduction options introduced in Clause 7. It is noted in Clause 7.3.3 that PR1 and PR2 are not expected to have coverage impact. It is also noted in Clause 7.4.3 that PT1 and PT2 are not expected to impact coverage. Therefore, in the rest of this clause, the potential coverage impact in terms of coverage margins and broadcast channel coverage differences are summarized for complexity reduction options BW1, BW2, BW3 and PR3. It is noted that BW3 and PR3 + +are not expected to have coverage impact on PDCCH and PBCH since the bandwidth of channels other than PDSCH/PUSCH can be up to 20MHz with BW3 and PR3. It should be also noted that in the following comparison results, contiguous resource allocation has been assumed for PR3 which hence has same coverage impact results as BW3. Finally, no frequency hopping has been assumed for BW2 in the following evaluation results. + +For complexity reduction options, BW1, BW2, BW3 and PR3, channels with negative representative coverage margins are summarized in Table 8.2.4-1. It is noted that results of individual sourcing companies show that Urban scenario at 4 GHz with 33 dBm/MHz DL PSD and maximum 11-PRB UE BW follows a similar trend as the Urban scenario at 2.6 GHz with 33 dBm/MHz DL PSD and maximum 11-PRB UE BW. However, Table 8.2.4-1 does not present the same results for these two scenarios. This is because Table 8.2.4-1 is summarized based on representative values which are determined by inputs of sourcing companies. And the number of sourcing companies for these two scenarios is different. + +**Table 8.2.4-1: Channels with negative representative coverage margins for different complexity reductions options and different deployment scenarios** + +| Deployment scenario and frequency (and UE bandwidth, and DL PSD) | 3dB antenna efficiency loss? | Complexity reduction options in Clause 7 | | | | +|------------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------|----------------------------| +| | | BW1 | BW2 | BW3 | PR3 | +| Urban at 2.6 GHZ with 11 PRBs | w/o 3dB ant. eff. loss | None | None | None | None | +| | with 3dB ant. eff. loss | PDCCH CSS w/ AL2 (<1dB)
SIB1(<1dB) | PDCCH CSS w/ AL2 (<1dB)
SIB1(<1dB) | SIB1(<1dB) | SIB1(<1dB) | +| Urban at 2.6 GHZ with 12 PRBs | w/o 3dB ant. eff. loss | None | None | None | None | +| | with 3dB ant. eff. loss | None | None | None | None | +| Rural at 0.7 GHz | w/o 3dB ant. eff. loss | None | None | None | None | +| | with 3dB ant. eff. loss | Msg3 (<0.1dB) | Msg3 (<0.1dB) | None | None | +| Urban at 4 GHz with 11 PRBs and DL PSD of 33dBm/MHz | w/o 3dB ant. eff. loss | None | None | None | None | +| | with 3dB ant. eff. loss | None | None | None | None | +| Urban at 4 GHz with 11 PRBs and DL PSD of 24dBm/MHz | w/o 3dB ant. eff. loss | - PDCCH CSS (w/ AL16, AL8 and AL2)
- PDCCH USS with AL2
- SIB1
- Msg4 | - PDCCH CSS (w/ AL16, AL8 and AL2)
- PDCCH USS with AL2
- SIB1
- Msg4 | - SIB1
- Msg4 | - SIB1
- Msg4 | +| | with 3dB ant. eff. loss | - PBCH
- PDCCH CSS
- PDCCH USS
- SIB1
- Msg2
- Msg4 | - PBCH
- PDCCH CSS
- PDCCH USS
- SIB1
- Msg2
- Msg4 | - SIB1
- Msg2
- Msg4 | - SIB1
- Msg2
- Msg4 | + +Based on the evaluation results on coverage difference in Clause 8.2.1 and 8.2.2 based on the complexity reduction option BW1 and the description of the complexity reduction options in Clause 7, the following tables show the coverage differences with respective to the reference NR UE and the Rel-17 RedCap UEs for the complexity reduction options, BW1, BW2, BW3, and PR3, over the considered scenarios. + +If not otherwise notified, 2.6GHz is assumed for Urban scenario since Urban scenario at 4GHz with DL PSD of 33dBm/MHz shares a similar trend with 2.6 GHz with 33dBm/MHz regarding broadcast channel coverage difference + +comparison between the potential Rel-18 UE and the reference NR UE/the Rel-17 RedCap UE. For Rural scenario, the coverage difference for PBCH is not available in the captured tables since bandwidth of PBCH is confined with the potential Rel-18 UE's maximum BW for all complexity reduction options evaluated. + +For a potential Rel-18 UE with BW3 or PR3, it should be noted no PBCH and PDCCH CSS coverage differences are observed compared to the reference Rel-17 RedCap UE. When compared to the reference Rel-15 NR UE, PDCCH CSS coverage differences of -5.18 dB and -3.04 dB are observed for Urban at 2.6 GHz and Rural scenario at 0.7 GHz, respectively. PBCH coverage difference of 6.8 dB is observed for Urban scenario at 2.6GHz. The observed differences also represent for the differences between the reference Rel-17 RedCap UE and the reference Rel-15 NR UE. Furthermore, the observed differences are mainly resulted in the different numbers of receive antennas. + +**Table 8.2.4-2: In Urban scenario at 2.6GHz with 30kHz SCS, coverage differences of broadcast channels including PBCH, PDCCH CSS, and SIB1 between the potential Rel-18 UE and the reference Rel-15 NR/Rel-17 RedCap UEs with complexity reduction options BW1, BW2, BW3 and PR3.** + +| Coverage difference (dB) | Compared with reference Rel-15 NR UE (MIL) | | | | Compared with reference Rel-17 RedCap UE (MIL) | | | | +|--------------------------|-------------------------------------------------------------|----------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------|-------------------------------------------------------------|----------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------| +| | PBCH (20 RBs) with 1% BLER | | PDCCH CSS (48 RBs) with 1% BLER | SIB1 (>5 MHz) with 10% BLER | PBCH (20 RBs) with 1% BLER | | PDCCH CSS (48 RBs) with 1% BLER | SIB1 (>5 MHz) with 10% BLER | +| | Rel-18 UE with soft/selective combining without RF retuning | Rel-18 UE with soft/selective combining with RF retuning | Rel-18 UE (11 PRBs; CORESE: 2 symbols, 48 PRBs; AL16) | Rel-18 UE (11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | Rel-18 UE with soft/selective combining without RF retuning | Rel-18 UE with soft/selective combining with RF retuning | Rel-18 UE (11 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | Rel-18 UE (11 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | +| | | | | | | | | | +| BW1 | -11.87 | -9.3 | -15.26 | -17.50 | -5.05 | -2.51 | -8.91 | -11.24 | +| BW2 | -11.87 | -9.3 | -15.26 | -17.50 | -5.05 | -2.51 | -8.91 | -11.24 | +| BW3 | | -6.8 | -6.28 | -17.50 | | 0 | 0 | -11.24 | +| PR3 | | -6.8 | -6.28 | -17.50 | | 0 | 0 | -11.24 | + +**Table 8.2.4-3: In Rural scenario at 0.7 GHz with 15kHz SCS, coverage differences of broadcast channels including PDCCH CSS and SIB1 between the potential Rel-18 UE and the reference Rel-15 NR/Rel-17 RedCap UEs with complexity reduction options BW1, BW2, BW3 and PR3** + +| Coverage difference (dB) | Compared with reference Rel-15 NR UE (MIL) | | Compared with Rel-17 RedCap UE (MIL) | | +|--------------------------|-------------------------------------------------------|-----------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------| +| | PDCCH CSS (48 RBs) with 1% BLER | SIB1 (>5 MHz) with 10% BLER | PDCCH CSS (48 RBs) with 1% BLER | SIB1 (>5 MHz) with 10% BLER | +| | Rel-18 UE (25 PRBs; CORESE: 2 symbols, 48 PRBs; AL16) | Rel-18 UE (25 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | Rel-18 UE (25 PRBs; CORESET: 2 symbols, 48 PRBs; AL16) | Rel-18 UE (25 PRBs; SIB1 BW > 5 MHz; TBS 1256 bits) | +| BW1 | -7.30 | -7.57 | -3.53 | -3.93 | +| BW2 | -7.30 | -7.57 | -3.53 | -3.93 | +| BW3 | -3.71 | -7.57 | 0 | -3.93 | +| PR3 | -3.71 | -7.57 | 0 | -3.93 | + +From the above comparison on broadcast channel coverage differences between the potential Rel-18 UE and the reference Rel-15 NR/Rel-17 RedCap UEs, the following observations can be made for complexity reduction options BW1, BW2, BW3, and PR3: + +- Coverage difference is larger in Urban scenario (30 kHz SCS) than in Rural scenario (15 kHz SCS) due to a smaller RB number with 30 kHz SCS within 5MHz bandwidth. + +- In Urban scenario (30 kHz SCS), the coverage difference is the largest for SIB1 and the smallest for PBCH, with PDCCH CSS (48 RBs) in the middle. +- For SIB1 (>5MHz), coverage degradation of 11.24 dB is observed with BW1, BW2, BW3 and PR3 options compared to Rel-17 RedCap UE. +- For PDCCH (AL16 and 48 RBs), coverage degradation of 8.91 dB is observed with BW1 and BW2 options compared to Rel-17 RedCap UE +- For PBCH (20 RBs), coverage degradation of 5.05 dB (2.51 dB) is observed with BW1 and BW2 options without RF retuning (with RF retuning) compared to Rel-17 RedCap UE. +- It is noted that BW3 and PR3 do not cause coverage degradation to PBCH and PDCCH compared to Rel-17 RedCap UE. + +For broadcast channels with large coverage differences such as SIB1, the potential Rel-18 UE may utilize additional processing/combining to compensate the coverage difference when considering coexistence and minimizing impact on legacy UEs. + +# 9 Conclusions and recommendations + +Further NR RedCap UE complexity reduction techniques have been analyzed individually in clauses 7.2 through 7.4 as well as in different combinations in clause 7.5. The coverage impacts of the complexity reduction techniques have been analyzed in clause 8. The main observations from the coverage impact evaluations are summarized in clause 8.2.4. + +Based on the analysis of the studied UE complexity reduction options, most companies in RAN1 recommend that a single option is down-selected from a list of options as the main Rel-18 RedCap UE complexity reduction option at RAN plenary. The list includes the following options. + +- Option BW3: + - 5 MHz BB bandwidth only for PDSCH (for both unicast and broadcast) and PUSCH with 20 MHz RF bandwidth for UL and DL. + - The other physical channels and signals are still allowed to use a BWP up to the 20 MHz maximum UE RF+BB bandwidth. +- Option PR3: + - Restriction of maximum number of PRBs for PDSCH and PUSCH. + - For 15 kHz SCS, the maximum number of RBs is 25. + - For 30 kHz SCS, the maximum number of RBs is 11 or 12. + - The restricted number of PRBs in Option PR3 is a hardcoded limit. + +Some of the companies who participated in the study also wanted to include one or both of the following options in the above list, for RAN plenary to assess the trade-off between degree of complexity reduction and specification impact. + +- Option PR1: + - Relaxation of the constraint $(v_{Layers}^{(j)} \cdot Q_m^{(j)} \cdot f^{(j)} \geq 4)$ for peak data rate reduction. + - The relaxed constraint is, e.g., 1 (instead of 4). + - The parameters $(v_{Layers}^{(1)}, Q_m^{(1)}, f^{(1)})$ can be as in Rel-17 RedCap [4]. +- Option BW1: + - Both RF and BB bandwidths are 5 MHz for UL and DL. + +Furthermore, RAN1 recommends that Option PR1 is considered as a potential add-on. Whether to adopt this potential add-on can be decided during WI phase. + +Whether or not to also introduce support for option PT1 and/or PT2 for a Rel-18 RedCap UE can be decided at RAN plenary. + +- Option PT1: + - Relaxation of UE processing time for PDSCH/PUSCH in terms of N1 and N2 (as defined in TS 38.214) compared to those of UE processing time capability 1 + - The relaxation factor for N1 and N2 is assumed to be 2 in the study. +- Option PT2: + - Relaxation of UE processing time for CSI in terms of Z and Z' compared to the values defined in TS 38.214 clause 5.4 + - The relaxation factor for Z and Z' is assumed to be 2 in the study. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|------------|------------|----|-----|-----|-------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN1#109-e | R1-2205621 | | | | TR skeleton | 0.0.0 | +| 2022-05 | RAN1#109-e | R1-2205693 | | | | Endorsed TR skeleton | 0.0.1 | +| 2022-09 | RAN1#110 | R1-2208316 | | | | Endorsed TR | 0.1.0 | +| 2022-09 | RAN#97-e | RP-222207 | | | | TR for one-step approval | 1.0.0 | +| 2022-09 | RAN#97-e | | | | | TR under change control further to RAN approval as part of Rel-18 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38891/02ab1c6abcb5a2d487a30d019a5454b6_img.jpg b/marked/Rel-18/38_series/38891/02ab1c6abcb5a2d487a30d019a5454b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..260b67148ebd2d1355d68b1ef58ccac6b28b4280 --- /dev/null +++ b/marked/Rel-18/38_series/38891/02ab1c6abcb5a2d487a30d019a5454b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd4fcd9f2581913458512f3c9eed1f41dee7f6b9b78dfa9c326d253e678ae72d +size 48844 diff --git a/marked/Rel-18/38_series/38891/031e354d9de9563c9f650e3e4fcba16d_img.jpg b/marked/Rel-18/38_series/38891/031e354d9de9563c9f650e3e4fcba16d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52cde3ab65817009bea9513be33465545a6cb5b8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/031e354d9de9563c9f650e3e4fcba16d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c29c11ac1d1e6b816e87f34d3ba5fb1e761e7642a4fdb719954822d34f859faf +size 26715 diff --git a/marked/Rel-18/38_series/38891/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg b/marked/Rel-18/38_series/38891/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67889d0b6fcbf882571964da41af519ff8c9ee76 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7eb6bad5e0d74b84bdd53c1657042ec6312e5dc9df386fa564a30d2594c600af +size 23877 diff --git a/marked/Rel-18/38_series/38891/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg b/marked/Rel-18/38_series/38891/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbc45f84989a1f8d4c7db784302d866ee520e5c9 --- /dev/null +++ b/marked/Rel-18/38_series/38891/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14c546e85ad005accd0127faabb6051cde97f5f872a67a061bee8c457b2565ef +size 78619 diff --git a/marked/Rel-18/38_series/38891/0881dba5224c95f05eeaf56c545ebddd_img.jpg b/marked/Rel-18/38_series/38891/0881dba5224c95f05eeaf56c545ebddd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5e1cb4b528b01c247872e699a03ca7d1a9b16c6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0881dba5224c95f05eeaf56c545ebddd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:931f18dfd7e97da041a6864518a4ecf701541390d87231a196d5e187d9f1e037 +size 28569 diff --git a/marked/Rel-18/38_series/38891/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-18/38_series/38891/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed7b9ac7035e230736cfb6dffd471ec4bc099d37 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca368657a1a38d77d9c4bafb9e7accaa5dd323e40b91295ccdf6f363c1c36f7d +size 28580 diff --git a/marked/Rel-18/38_series/38891/0a8d173734e4e46c344178e8d21bcbc3_img.jpg b/marked/Rel-18/38_series/38891/0a8d173734e4e46c344178e8d21bcbc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7b9a01018fef597c16531e3df323cef622597a4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0a8d173734e4e46c344178e8d21bcbc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6aec4f49cc97818ae93accdfd7f0e4bf9b8c5965fda59e492e0bdd50f1db3521 +size 21557 diff --git a/marked/Rel-18/38_series/38891/0aa15f5c9c3edae230985491199cfe8b_img.jpg b/marked/Rel-18/38_series/38891/0aa15f5c9c3edae230985491199cfe8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..280efcf38c782cc7ba8a2211e3f3c96bfa34928b --- /dev/null +++ b/marked/Rel-18/38_series/38891/0aa15f5c9c3edae230985491199cfe8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ef60fc41257c087e18e54477fa5f3cdce3702bcfd6d22bd519500ddebc97308 +size 103350 diff --git a/marked/Rel-18/38_series/38891/0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg b/marked/Rel-18/38_series/38891/0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0deb2f35dd171ebd400f6b7d4c1b1c04c1769bc8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:732d7cd87351a50031c99ecfc2361d0aab99487544af4e7d952fc64264557aee +size 117894 diff --git a/marked/Rel-18/38_series/38891/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg b/marked/Rel-18/38_series/38891/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd5bb337ef2a750b3686bd6c7f1362499c0a8cf9 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9032c42ee8013d3bfaff06e92667d7c3440e5dc670ffa0a48635272be64c938e +size 25889 diff --git a/marked/Rel-18/38_series/38891/0eab48b5b15f7316f5c2521e7ba93b52_img.jpg b/marked/Rel-18/38_series/38891/0eab48b5b15f7316f5c2521e7ba93b52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89fb8767ac3c5dfc4caa176d9c7fda6cd16dc0a5 --- /dev/null +++ b/marked/Rel-18/38_series/38891/0eab48b5b15f7316f5c2521e7ba93b52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59a0654308b07e07967e80d2c6e5b7881d3377b3d575986b8cdf07a9df78b557 +size 89755 diff --git a/marked/Rel-18/38_series/38891/1033ab90cd19fd4c5901966aeec07a86_img.jpg b/marked/Rel-18/38_series/38891/1033ab90cd19fd4c5901966aeec07a86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffa5781a44a344ab14f7071840ec33b4987da6e2 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1033ab90cd19fd4c5901966aeec07a86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bcc45b7bcd257802e9e3dfacffa64456ff74c32a26e1190b1eb4761e6d7c744 +size 19752 diff --git a/marked/Rel-18/38_series/38891/114a0f7c7ac69ab82f03d68650cf8e88_img.jpg b/marked/Rel-18/38_series/38891/114a0f7c7ac69ab82f03d68650cf8e88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33ac7e9e5e0cc73ec73fee761b14f80f158e95f7 --- /dev/null +++ b/marked/Rel-18/38_series/38891/114a0f7c7ac69ab82f03d68650cf8e88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ff423640e3206695c6e272a76780321f2b3573a5b6c949f93cb770760e03934 +size 36627 diff --git a/marked/Rel-18/38_series/38891/123e1675d910a1beab564c5fec9548e2_img.jpg b/marked/Rel-18/38_series/38891/123e1675d910a1beab564c5fec9548e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b723d882311ba6ee1d275d5405b52a3ad51db4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/123e1675d910a1beab564c5fec9548e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d0bd93bb648334ceb5839dbcc2ace33b4ac8946f017ab02773b57ba8403d31f +size 77675 diff --git a/marked/Rel-18/38_series/38891/1326773262ea98ffa5f525b048dc04e3_img.jpg b/marked/Rel-18/38_series/38891/1326773262ea98ffa5f525b048dc04e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae088da2a30bbda05e215f0895ab2c00f1cc3c1b --- /dev/null +++ b/marked/Rel-18/38_series/38891/1326773262ea98ffa5f525b048dc04e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f38c83afe58d2bc8bf66bc61ec17e72024b983d3194619a4fd6452426dcebc93 +size 99110 diff --git a/marked/Rel-18/38_series/38891/1383c500c5d34fbc2c535226f0f64fa9_img.jpg b/marked/Rel-18/38_series/38891/1383c500c5d34fbc2c535226f0f64fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a450b0f1b29eb29ffb5c56f529338ce41ac8654 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1383c500c5d34fbc2c535226f0f64fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e001c64d0be692f72a5aeb48ad08dcbbe230a93cfadacc64dd1b819f139b396 +size 50839 diff --git a/marked/Rel-18/38_series/38891/14d3e9dab6175ecd808705b6548b8f9a_img.jpg b/marked/Rel-18/38_series/38891/14d3e9dab6175ecd808705b6548b8f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8430115e4fbd451ae88732ffb3142c5936148479 --- /dev/null +++ b/marked/Rel-18/38_series/38891/14d3e9dab6175ecd808705b6548b8f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e7908efe1c115c8ebb27a19ae8931255c066e60c844f2258bb2b8e02163a00b +size 27660 diff --git a/marked/Rel-18/38_series/38891/155bd5ec49c26532be9f04b06904002e_img.jpg b/marked/Rel-18/38_series/38891/155bd5ec49c26532be9f04b06904002e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c10e093837e6ae47d72e4e0a010cb998a3a726 --- /dev/null +++ b/marked/Rel-18/38_series/38891/155bd5ec49c26532be9f04b06904002e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d36ddb584e241a84965d3cdf6528bb078151aa020ab5b9cd3ea8140ed2f7fb11 +size 38510 diff --git a/marked/Rel-18/38_series/38891/1640ec1dfae8bdfa5af950db7623febc_img.jpg b/marked/Rel-18/38_series/38891/1640ec1dfae8bdfa5af950db7623febc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8521a84642f8134d81dcb3ded702fde4c3ee954 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1640ec1dfae8bdfa5af950db7623febc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87e32339d214d1defb2459444f2ab99f7d9a9fad5ea4458f2a7e3f485ce91fae +size 42622 diff --git a/marked/Rel-18/38_series/38891/16f235bb59e360d10bb35e523d3946b2_img.jpg b/marked/Rel-18/38_series/38891/16f235bb59e360d10bb35e523d3946b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7611694be466ff58250eb48a25d65c03a9c24df8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/16f235bb59e360d10bb35e523d3946b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01878a493b366502aa955934e7362c4d1413daf48497291d8acad7f24008d900 +size 37473 diff --git a/marked/Rel-18/38_series/38891/198d076da025c516aec8122a6ab7db20_img.jpg b/marked/Rel-18/38_series/38891/198d076da025c516aec8122a6ab7db20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceb1acc1481609c426378638fa8e84dc34fbe4e1 --- /dev/null +++ b/marked/Rel-18/38_series/38891/198d076da025c516aec8122a6ab7db20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a38b1d8e2628d91924762c825de2e020156720111d5803fe0695bd6076138574 +size 27477 diff --git a/marked/Rel-18/38_series/38891/1a6a826cc13d4e964b7bda69508d78e6_img.jpg b/marked/Rel-18/38_series/38891/1a6a826cc13d4e964b7bda69508d78e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22185d8c14d47445e1ba78ff6da444fdc8fee984 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1a6a826cc13d4e964b7bda69508d78e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87bdc31704d771b3ffa5c5fdbe5f791c3c5bb445eb0016d97b08dbc960752a39 +size 45851 diff --git a/marked/Rel-18/38_series/38891/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-18/38_series/38891/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5e069624fb4e421cbde4f5d1cd896860bc946d2 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17e055c0f5af5b0ed956ff11d02d2fc4d6670d106cc0f852c0d541244d0ff921 +size 19157 diff --git a/marked/Rel-18/38_series/38891/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-18/38_series/38891/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92554fd44abd8c517d0f2ac4b95010384d5cb5f3 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:659b79c181a140c33af19cfb71955c3137c62312c1bf6cea4c2be588685ec2f7 +size 113075 diff --git a/marked/Rel-18/38_series/38891/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-18/38_series/38891/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e050e6cee40a431c4a7390412a6ce9e469bcca84 --- /dev/null +++ b/marked/Rel-18/38_series/38891/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70416e1df4501a73c9b3dd89ab59930beac01939e5df1467ff147544f36f8290 +size 27712 diff --git a/marked/Rel-18/38_series/38891/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg b/marked/Rel-18/38_series/38891/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b66c5caa16401c9ad42720f0f7c11e818a7c0b4c --- /dev/null +++ b/marked/Rel-18/38_series/38891/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a00983e29f1748269af9320f5c9715c58d7b9b8e43933184f1f24051a4cb680 +size 28425 diff --git a/marked/Rel-18/38_series/38891/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-18/38_series/38891/201de44da5d99899a8cf58eac2fa7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bf31117cc947e70a6788d00f17a4a3cfe824b82 --- /dev/null +++ b/marked/Rel-18/38_series/38891/201de44da5d99899a8cf58eac2fa7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:819ee611b9e0a23c34c312839d47d61e2b324032613baf98cde1acf91bddc9a7 +size 264454 diff --git a/marked/Rel-18/38_series/38891/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-18/38_series/38891/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1780173c2a25f23698d4ca18c2b8812c25eb85a2 --- /dev/null +++ b/marked/Rel-18/38_series/38891/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:314f5104495e288b32178604a65fa32828dfe028e6d5843bdf5d47cb01517de3 +size 38651 diff --git a/marked/Rel-18/38_series/38891/21998d5161d55a19df06b0ea8d3b4e59_img.jpg b/marked/Rel-18/38_series/38891/21998d5161d55a19df06b0ea8d3b4e59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fe5fbdc47df8460cf77de7166937792864a3463 --- /dev/null +++ b/marked/Rel-18/38_series/38891/21998d5161d55a19df06b0ea8d3b4e59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518dd045218e1212afba92134b739b7015c38451ac54b119262130ffdb63ce91 +size 130119 diff --git a/marked/Rel-18/38_series/38891/23816aaa8e6defc50fc888da62fd59cc_img.jpg b/marked/Rel-18/38_series/38891/23816aaa8e6defc50fc888da62fd59cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdcbe16f598b5ed269f169a8d236ea6aaa611df4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/23816aaa8e6defc50fc888da62fd59cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e79e58a1b0728b0cbf7d009f25086d330e63b95115052377692e07dedd07d89 +size 18295 diff --git a/marked/Rel-18/38_series/38891/239211fa511b4ffa685b54b5132ec927_img.jpg b/marked/Rel-18/38_series/38891/239211fa511b4ffa685b54b5132ec927_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c038b5e7698f9fc68ff7fd6a7a2aac9b06aef35 --- /dev/null +++ b/marked/Rel-18/38_series/38891/239211fa511b4ffa685b54b5132ec927_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:706ffecd4ee1609cb11bb359c7e8ab6396c767c98ac4bfd2780a5a108cce5324 +size 21619 diff --git a/marked/Rel-18/38_series/38891/2405d03fe11cb841e2b5155d3d86b1af_img.jpg b/marked/Rel-18/38_series/38891/2405d03fe11cb841e2b5155d3d86b1af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe298e3c0b3a325625e9a8ef40cfc378cbbf1484 --- /dev/null +++ b/marked/Rel-18/38_series/38891/2405d03fe11cb841e2b5155d3d86b1af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6670993d22936ccb0eb8c14889f0f87b37bb010922ae76ebfe9aa2a6707b5920 +size 124032 diff --git a/marked/Rel-18/38_series/38891/245e13acc2712dcc66009c4c2f5b0247_img.jpg b/marked/Rel-18/38_series/38891/245e13acc2712dcc66009c4c2f5b0247_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fd3c8fb0736a5b5983cdc5a34f8860fe9ccbdc8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/245e13acc2712dcc66009c4c2f5b0247_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77bbfa3a08f6dc8ec1fc4b012d1cfa98d135ba4d0e6699045d287f0d6ff4426c +size 57426 diff --git a/marked/Rel-18/38_series/38891/26ba4afd729749f66bf8314d9d676041_img.jpg b/marked/Rel-18/38_series/38891/26ba4afd729749f66bf8314d9d676041_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d80110a4513bbc69dd5c05be1e7ac1184ed0ca1 --- /dev/null +++ b/marked/Rel-18/38_series/38891/26ba4afd729749f66bf8314d9d676041_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28cf2c2be29b88a0d52de20b611c2a45799f433f73256eaa50d759dd27a6834f +size 43656 diff --git a/marked/Rel-18/38_series/38891/26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg b/marked/Rel-18/38_series/38891/26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6caf64c714b2176a6f4899f17c350574f6cf2de3 --- /dev/null +++ b/marked/Rel-18/38_series/38891/26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776c932c06bc77a18661cd6fc3573e6567b0bd1b3d3637fb10464247011066a2 +size 75221 diff --git a/marked/Rel-18/38_series/38891/282b054897a74f36790420bcf6568656_img.jpg b/marked/Rel-18/38_series/38891/282b054897a74f36790420bcf6568656_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23ce838e3633cef23df1125e977fe65debd02b2c --- /dev/null +++ b/marked/Rel-18/38_series/38891/282b054897a74f36790420bcf6568656_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70c5af5d331c83d81d12a51ed98aa8d489709622f30ea4a70b8dfdc91059db1b +size 28502 diff --git a/marked/Rel-18/38_series/38891/28639a75145506e46966c11c1b995dd2_img.jpg b/marked/Rel-18/38_series/38891/28639a75145506e46966c11c1b995dd2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc84d33b13fb0e60f290d5ccd7371cc7ae5b03bd --- /dev/null +++ b/marked/Rel-18/38_series/38891/28639a75145506e46966c11c1b995dd2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66a909e8807e16fa132a580ecdabe58c34fe7f590368d5ae59e38d4773d9108c +size 81521 diff --git a/marked/Rel-18/38_series/38891/293fb0a508d182b518ea429927dfd343_img.jpg b/marked/Rel-18/38_series/38891/293fb0a508d182b518ea429927dfd343_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd60032f91e85c62004f9425b95b2c103da5d4f0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/293fb0a508d182b518ea429927dfd343_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffd1d26799234fd99424c76b6d074a2ac2cba3440c8f0e767ebda8d7d7eec975 +size 88383 diff --git a/marked/Rel-18/38_series/38891/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg b/marked/Rel-18/38_series/38891/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce96dc3156e0db4403baad189d0799878625cd5b --- /dev/null +++ b/marked/Rel-18/38_series/38891/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7758e2b1ba947c3f5ba722612de9076729c6a2ce3cfced4e43f0c33ad8981452 +size 73976 diff --git a/marked/Rel-18/38_series/38891/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-18/38_series/38891/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd71b59072fe30f0e7fae1887521a893dd4fea34 --- /dev/null +++ b/marked/Rel-18/38_series/38891/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e528210351dfbdfb2ecafb4b903630d6f7cf8e83622028fd8c208508de0139b +size 241899 diff --git a/marked/Rel-18/38_series/38891/2ee4eab0a7ac079c4858483ede251b76_img.jpg b/marked/Rel-18/38_series/38891/2ee4eab0a7ac079c4858483ede251b76_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e8b2a24b982fdba7a43c7d8d2a687001af632af --- /dev/null +++ b/marked/Rel-18/38_series/38891/2ee4eab0a7ac079c4858483ede251b76_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7a064cb2924f5670a8e41832e1e04dc5bb0f3642698de09d26fb16b54d53530 +size 58119 diff --git a/marked/Rel-18/38_series/38891/33228b4227fa57e1477b27b9e07483e6_img.jpg b/marked/Rel-18/38_series/38891/33228b4227fa57e1477b27b9e07483e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca193cc2f90db26fb59aee37c8f9e66f74a2b736 --- /dev/null +++ b/marked/Rel-18/38_series/38891/33228b4227fa57e1477b27b9e07483e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6167471b56a3c6fa61fa0518a7803030f8ebfeb90d370f3c556eb057f475ffc7 +size 22032 diff --git a/marked/Rel-18/38_series/38891/3579cd5f679b4532a727bfacc823ea7d_img.jpg b/marked/Rel-18/38_series/38891/3579cd5f679b4532a727bfacc823ea7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e60b96ac6a65b7130646943a361d91562bf0626f --- /dev/null +++ b/marked/Rel-18/38_series/38891/3579cd5f679b4532a727bfacc823ea7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fde93aa73fa653882233b35eb5a9ae45a4b7293af1c424753f2d4e7efc1c10c3 +size 46840 diff --git a/marked/Rel-18/38_series/38891/3881b390d52f27a35faedfc170916c86_img.jpg b/marked/Rel-18/38_series/38891/3881b390d52f27a35faedfc170916c86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf518a2e130d400c2047e6740ada9c503b8ca85b --- /dev/null +++ b/marked/Rel-18/38_series/38891/3881b390d52f27a35faedfc170916c86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fdf3a9848213eeff5566f70f7a639ead4bed05def5e9cb2d4380334879e09d0 +size 75170 diff --git a/marked/Rel-18/38_series/38891/38ddc1935b2416f874d07574fe8fc005_img.jpg b/marked/Rel-18/38_series/38891/38ddc1935b2416f874d07574fe8fc005_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f05ae63d2749e4ccb05caabe50209bbe8dbd2ba4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/38ddc1935b2416f874d07574fe8fc005_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63780fb0dfa8850c685791f6fdb5b5ff356d7256324b48154d44a6fed99710c0 +size 43389 diff --git a/marked/Rel-18/38_series/38891/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg b/marked/Rel-18/38_series/38891/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98491bd520f04ec7110d5b5a9a5a827e98afdf49 --- /dev/null +++ b/marked/Rel-18/38_series/38891/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4bcad6d06735819096deb051788a5e6cd0f4c0ea24b8621183e914016a1f23a +size 71866 diff --git a/marked/Rel-18/38_series/38891/3c2744b5b1ad3baef441546b0bf157ca_img.jpg b/marked/Rel-18/38_series/38891/3c2744b5b1ad3baef441546b0bf157ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..710218574aa4ec3fe818fae1f99d4a8663ba68df --- /dev/null +++ b/marked/Rel-18/38_series/38891/3c2744b5b1ad3baef441546b0bf157ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f38a91610df20a73e96c2cd229561c5d2b637b6014a08b1655a18f25664eb027 +size 17974 diff --git a/marked/Rel-18/38_series/38891/3cebe0a635150ad48f69392301b0c157_img.jpg b/marked/Rel-18/38_series/38891/3cebe0a635150ad48f69392301b0c157_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f73386f8d17c22f273ea56a884e45264f794bdb8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/3cebe0a635150ad48f69392301b0c157_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b53c4b4bc955f9664c28089d69c6cf42afd1fc597a25c54531ad4cc33cb55035 +size 47682 diff --git a/marked/Rel-18/38_series/38891/40fa7d84ea1c6bb38863689c3a0590fa_img.jpg b/marked/Rel-18/38_series/38891/40fa7d84ea1c6bb38863689c3a0590fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f8807e48048562af4dfb0e1ea47003a9ae23c23 --- /dev/null +++ b/marked/Rel-18/38_series/38891/40fa7d84ea1c6bb38863689c3a0590fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b53d52599a977524d2eadbc85df1ed0ef6eef25bf6c8bd0f08d20fdb8a279d8f +size 73732 diff --git a/marked/Rel-18/38_series/38891/411fa16c3211377525ba37c57784fee0_img.jpg b/marked/Rel-18/38_series/38891/411fa16c3211377525ba37c57784fee0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e699f9dc546ade70bffc0d721fd84c4989ccf429 --- /dev/null +++ b/marked/Rel-18/38_series/38891/411fa16c3211377525ba37c57784fee0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07aed6691d98dc34669934264671d3f1e6589cb39dbacb70014f928fafd2b4aa +size 22060 diff --git a/marked/Rel-18/38_series/38891/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg b/marked/Rel-18/38_series/38891/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fad056dfad9c5f2ce5023a9ddc602175ef1172c6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21af68cf9193a8f40a03e3d68bdb940a86171517da273c462ac9bbae45d9b94c +size 43210 diff --git a/marked/Rel-18/38_series/38891/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg b/marked/Rel-18/38_series/38891/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75968556ac5fcd48fce8ad53c45913590e462a0a --- /dev/null +++ b/marked/Rel-18/38_series/38891/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b56e50d2abdf2e55cec9199e3bf18fda60fd72297876f54a6d313b1b6f5aeb66 +size 68782 diff --git a/marked/Rel-18/38_series/38891/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg b/marked/Rel-18/38_series/38891/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9764307715b14630aee823a98cd0baaa2610d6f7 --- /dev/null +++ b/marked/Rel-18/38_series/38891/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf840e58fac5aac1771308d5d8d6f6677d48b1020a728f2f40a758735e882072 +size 32279 diff --git a/marked/Rel-18/38_series/38891/4a343290f76ae7922954fa3e2b9c59ce_img.jpg b/marked/Rel-18/38_series/38891/4a343290f76ae7922954fa3e2b9c59ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c61abcdf85410a198d3d635611f5e79970b6924 --- /dev/null +++ b/marked/Rel-18/38_series/38891/4a343290f76ae7922954fa3e2b9c59ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80a5605327e97cb31ab252845ab07cb2f84c13c999520b36673eb415864a2e61 +size 66362 diff --git a/marked/Rel-18/38_series/38891/4a8f09807c20be2a38e37e719a575eac_img.jpg b/marked/Rel-18/38_series/38891/4a8f09807c20be2a38e37e719a575eac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40bd5cfe6f3d207a20ee2ca9dd5a1be8738e23a6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/4a8f09807c20be2a38e37e719a575eac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:255c3e0f7234f114ac65e81dc030aaf63e7e0eb618838f9c85bd608b196355ea +size 56056 diff --git a/marked/Rel-18/38_series/38891/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-18/38_series/38891/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e4abbb70b283e976539a3c30c3d5c8d08b035a0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f60037193c509819ec7412e2a86a9550ce0063669b4109848536781c912ddfd +size 27529 diff --git a/marked/Rel-18/38_series/38891/4f90ddf705239c0ca535c91179212420_img.jpg b/marked/Rel-18/38_series/38891/4f90ddf705239c0ca535c91179212420_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f813e404119a870cdad6b1c04784fdecf2701891 --- /dev/null +++ b/marked/Rel-18/38_series/38891/4f90ddf705239c0ca535c91179212420_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f9f078082285f0d2234cc30a1d6992fc39c38480dd876a10665f30fd42b490c +size 28928 diff --git a/marked/Rel-18/38_series/38891/509a054727400bc6d424bb2a559b8cfc_img.jpg b/marked/Rel-18/38_series/38891/509a054727400bc6d424bb2a559b8cfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e0911ab6097c3398cc6b2d7b1a5e70ee48f7a70 --- /dev/null +++ b/marked/Rel-18/38_series/38891/509a054727400bc6d424bb2a559b8cfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c92a9439337fefd5361a9ca136be186b9a1117afd2ffbc9295d2e5ae64dd204d +size 49593 diff --git a/marked/Rel-18/38_series/38891/51536f203c07ce20ce119e7e09b11cb6_img.jpg b/marked/Rel-18/38_series/38891/51536f203c07ce20ce119e7e09b11cb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d61f4c8201d6ae320bb0116f73c80eb5822f562 --- /dev/null +++ b/marked/Rel-18/38_series/38891/51536f203c07ce20ce119e7e09b11cb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:918efda310a3686b9f6a172428a9d43dd260894e9cabd0ee4ef2ccc683469d33 +size 19305 diff --git a/marked/Rel-18/38_series/38891/524cc6038f81916add4e259efa7e780b_img.jpg b/marked/Rel-18/38_series/38891/524cc6038f81916add4e259efa7e780b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fe52bf6668eb7683779540885cd533ae34693dd --- /dev/null +++ b/marked/Rel-18/38_series/38891/524cc6038f81916add4e259efa7e780b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77c40c60eb7a1022d18d1db13488cebaab2804af7ece268364f9124d6e4ffe38 +size 42730 diff --git a/marked/Rel-18/38_series/38891/52727a1fec40059356483552cc6dba2b_img.jpg b/marked/Rel-18/38_series/38891/52727a1fec40059356483552cc6dba2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59ed7b1ca86bb80e9724f62cb08beda7222f2590 --- /dev/null +++ b/marked/Rel-18/38_series/38891/52727a1fec40059356483552cc6dba2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0292fe35138b97a4eacfb32012a30a9c9f3ee52e02b63e19247b109c2be25dc4 +size 60388 diff --git a/marked/Rel-18/38_series/38891/52f284e10be4323639b32fdd60e463db_img.jpg b/marked/Rel-18/38_series/38891/52f284e10be4323639b32fdd60e463db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb8b98618ad6b7b64ae107aac0440da071e4d2af --- /dev/null +++ b/marked/Rel-18/38_series/38891/52f284e10be4323639b32fdd60e463db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6efaab6b5026a9631dd4bdf1ba39cf050b9f584ba9c825a0c2443eba79ad52cc +size 26232 diff --git a/marked/Rel-18/38_series/38891/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38891/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7c46dcc179ff57c93dba6049fd8f55407077382 --- /dev/null +++ b/marked/Rel-18/38_series/38891/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:241ed5991171d0e2cb2754b5875892ac67199c592d8e3ab3169d9a5085318281 +size 49003 diff --git a/marked/Rel-18/38_series/38891/58de972a8c79c238b69cbeeafcc8d5fb_img.jpg b/marked/Rel-18/38_series/38891/58de972a8c79c238b69cbeeafcc8d5fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcec4f098a64f11d49bee101e11820ba8e63426a --- /dev/null +++ b/marked/Rel-18/38_series/38891/58de972a8c79c238b69cbeeafcc8d5fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecdc99def75dc5044ed1f7e9236080038129b7ccde1e71e556b387164e68ac7d +size 23654 diff --git a/marked/Rel-18/38_series/38891/58f883d880e744531c77ddfd50af87bf_img.jpg b/marked/Rel-18/38_series/38891/58f883d880e744531c77ddfd50af87bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63278de9662fdd9071489e33532b23094f6ed2e4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/58f883d880e744531c77ddfd50af87bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f76316263ffa378617fb4766e8776052501dcc49c3ea735fe5585b445939df3 +size 63183 diff --git a/marked/Rel-18/38_series/38891/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg b/marked/Rel-18/38_series/38891/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43024029fd7e96b0400ba42372b53dfc92d11e35 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5138037667441574f2308fa1613bcd191435ded2a79eefe14380681afbe94ba +size 37024 diff --git a/marked/Rel-18/38_series/38891/5b5673c03e7b6fc921c4a944dabf891e_img.jpg b/marked/Rel-18/38_series/38891/5b5673c03e7b6fc921c4a944dabf891e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc4a88f5284adff603a634fe320c9ce949554c21 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5b5673c03e7b6fc921c4a944dabf891e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bd501d68d5aa4ddb7d9f09e20111438141c82679930bc7d44061dd7d323760b +size 122962 diff --git a/marked/Rel-18/38_series/38891/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg b/marked/Rel-18/38_series/38891/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea0db3702998f5b1479fb8f83bde6d3a928865d --- /dev/null +++ b/marked/Rel-18/38_series/38891/5bf611979ab0126ebd219a1c6eda6b1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d5ab5ec2d2207b7b428d83d2d98f03ed50103074adcb99e1862ab9fd552e9b5 +size 24964 diff --git a/marked/Rel-18/38_series/38891/5c962f53272b4722e5d88f049e25084f_img.jpg b/marked/Rel-18/38_series/38891/5c962f53272b4722e5d88f049e25084f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6d917719ffb4deed446c763bc4da5f5c90afb06 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5c962f53272b4722e5d88f049e25084f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:610b7ef7bfc26a34f672cdcf8579370c246447c173d98cd3a33fcd72aa054ff5 +size 21432 diff --git a/marked/Rel-18/38_series/38891/5e7b93195badf89e1fb645ae53d619bb_img.jpg b/marked/Rel-18/38_series/38891/5e7b93195badf89e1fb645ae53d619bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fc8e0d7e6add72d902fd48ed768671c3b38bc74 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5e7b93195badf89e1fb645ae53d619bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37cfcd6432cf8df1e862522897c55e82b3284d09309df10dc5a5c41f83e92c00 +size 76873 diff --git a/marked/Rel-18/38_series/38891/5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg b/marked/Rel-18/38_series/38891/5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee160d641d3938b733fc558658413357c2979365 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa73bc2aead152aba4a201d61cf76f2c74a0131fdddef811d36bee72ec44abaf +size 32170 diff --git a/marked/Rel-18/38_series/38891/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38891/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baaf92bcbc94f772430a2b2a29af597f3f8cfac0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99d769ddd57b244333b192a549ab4b1a775459b8b3b7ca5c891c4f8a2ab7849a +size 9271 diff --git a/marked/Rel-18/38_series/38891/5fc9d10a31977210e289bf770051feff_img.jpg b/marked/Rel-18/38_series/38891/5fc9d10a31977210e289bf770051feff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..283ff8933106976079fe338506ebe3d57e2fe7f7 --- /dev/null +++ b/marked/Rel-18/38_series/38891/5fc9d10a31977210e289bf770051feff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f2d2815b72e4b98890a7fc2158f8647356d63ba0f4fc9c313ac8097d1f6487b +size 78541 diff --git a/marked/Rel-18/38_series/38891/624646367ef6cd220973a363f00310a0_img.jpg b/marked/Rel-18/38_series/38891/624646367ef6cd220973a363f00310a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d80f64b404da68d7000231d1bbdae1589c1f6f5e --- /dev/null +++ b/marked/Rel-18/38_series/38891/624646367ef6cd220973a363f00310a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be64157886a47bffcf04e1eec0b386a7d71f5ef0054e435f1ed411d07bbf93a7 +size 68415 diff --git a/marked/Rel-18/38_series/38891/624d9669faa18991d525fea5f0e03269_img.jpg b/marked/Rel-18/38_series/38891/624d9669faa18991d525fea5f0e03269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8113f34fc61a99c419b63266303d69a55494a50b --- /dev/null +++ b/marked/Rel-18/38_series/38891/624d9669faa18991d525fea5f0e03269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca1c7f22048aa161f188172dac481d03d945a8d8d4195cd605b6a9a2eb550073 +size 43101 diff --git a/marked/Rel-18/38_series/38891/62a4c9055642dbb00663e633332f04d3_img.jpg b/marked/Rel-18/38_series/38891/62a4c9055642dbb00663e633332f04d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7dbfc75e01925d0501f372de43d7c7f87165c87 --- /dev/null +++ b/marked/Rel-18/38_series/38891/62a4c9055642dbb00663e633332f04d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d411e1f3ad9cffe715f505b0f84b30ffdb8f9d207954676ad9fe828734a88498 +size 32892 diff --git a/marked/Rel-18/38_series/38891/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg b/marked/Rel-18/38_series/38891/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd9b2a0558c5b41a1cb8466e3685d02ffac43ffa --- /dev/null +++ b/marked/Rel-18/38_series/38891/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d576a5a50230f0cdd388814bf2d614e64b0d6ee4000f6226fbd6cb4e7172c65e +size 39817 diff --git a/marked/Rel-18/38_series/38891/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38891/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61b912518698903ccba95a45b545aff271a035b4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a4d93c7c6e89c8d4e68e2105d88f6060649ff59694ded2970ea6ce3eec282f9 +size 6200 diff --git a/marked/Rel-18/38_series/38891/65f66758012e229247953202e8adf35d_img.jpg b/marked/Rel-18/38_series/38891/65f66758012e229247953202e8adf35d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bb78ee0672850070cec71bb8e47fb450c1219dd --- /dev/null +++ b/marked/Rel-18/38_series/38891/65f66758012e229247953202e8adf35d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa0b6e19ffe8df33c10ad8f2b44e8cfa8e75506f1643c0254613a0449b7e045d +size 46527 diff --git a/marked/Rel-18/38_series/38891/6682c4376efdda007851175f3014eca3_img.jpg b/marked/Rel-18/38_series/38891/6682c4376efdda007851175f3014eca3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f24525b8b61353d06dc610c7849ec63cb1157e2e --- /dev/null +++ b/marked/Rel-18/38_series/38891/6682c4376efdda007851175f3014eca3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3156bd20533e4d4f0ff135e969aa4c2ed12a954f81fb8ebeee88051ff5a44478 +size 30461 diff --git a/marked/Rel-18/38_series/38891/66c6cb4ec14805010fceaba7baa26183_img.jpg b/marked/Rel-18/38_series/38891/66c6cb4ec14805010fceaba7baa26183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a04cf2a059f7d28a1f34132dd954e297f724eeb --- /dev/null +++ b/marked/Rel-18/38_series/38891/66c6cb4ec14805010fceaba7baa26183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a59afbc886196fd03c723e720cdb8701714cde36cace290588ff78c6b1b9cdb6 +size 30741 diff --git a/marked/Rel-18/38_series/38891/671a9a08b8506e113012e056945fd8f3_img.jpg b/marked/Rel-18/38_series/38891/671a9a08b8506e113012e056945fd8f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09cd543da0f734488a14d0e6f095cc2524e9fccb --- /dev/null +++ b/marked/Rel-18/38_series/38891/671a9a08b8506e113012e056945fd8f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efd85215590164847900b5e7ffd5dd5a627cf4a2c16bbeae89716f55f6551ddb +size 95563 diff --git a/marked/Rel-18/38_series/38891/6752cee124f693bc4cebc66180f4f91f_img.jpg b/marked/Rel-18/38_series/38891/6752cee124f693bc4cebc66180f4f91f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48cfb571cf2d7ce8f415c8e72c825570f6534776 --- /dev/null +++ b/marked/Rel-18/38_series/38891/6752cee124f693bc4cebc66180f4f91f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcacdd276009584aa91708988d9b0ced064df3f799832f33d33113a3c24add7f +size 116092 diff --git a/marked/Rel-18/38_series/38891/68f0e97e094e315c0ed95a24eb0585c3_img.jpg b/marked/Rel-18/38_series/38891/68f0e97e094e315c0ed95a24eb0585c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b92734d348ad0fd0f6e2a6bb37fe3b97ad0328d --- /dev/null +++ b/marked/Rel-18/38_series/38891/68f0e97e094e315c0ed95a24eb0585c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4845268a7e2db1e5d11ebd73a2e23038d1f630f01dd445de0e40203417288440 +size 107467 diff --git a/marked/Rel-18/38_series/38891/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg b/marked/Rel-18/38_series/38891/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3176c20421a346254db699dc165a536b6bfc05a --- /dev/null +++ b/marked/Rel-18/38_series/38891/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1fb78a5eab581d8b4c0bf82b0f931d24abf1e73e26c214b2d87b479df361694 +size 21918 diff --git a/marked/Rel-18/38_series/38891/6d7be4b2b402e079f97685869580c864_img.jpg b/marked/Rel-18/38_series/38891/6d7be4b2b402e079f97685869580c864_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f507639c71092a9836f580a2334abdae4175bc7 --- /dev/null +++ b/marked/Rel-18/38_series/38891/6d7be4b2b402e079f97685869580c864_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f65a29b9826f24bdfb48d5e784a129d1151812b7b91707c9db177c6e84bfbddb +size 27338 diff --git a/marked/Rel-18/38_series/38891/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-18/38_series/38891/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba2b61570bb8c3ed6cfdc40f50666b9d4717c4c9 --- /dev/null +++ b/marked/Rel-18/38_series/38891/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03f75462ca6f88f6fe288e69ed833401e9340278d31ec86f2649036f7250ff50 +size 27713 diff --git a/marked/Rel-18/38_series/38891/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-18/38_series/38891/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ef5da86e3345b1e4489d438f5984a5cc6d2038f --- /dev/null +++ b/marked/Rel-18/38_series/38891/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7297ce9ed80462e5f157bfc8c89942ce52637ceb35bb9056f8778f1f59a8829d +size 69657 diff --git a/marked/Rel-18/38_series/38891/71d82d389da5fe06a4aefb661ea17af9_img.jpg b/marked/Rel-18/38_series/38891/71d82d389da5fe06a4aefb661ea17af9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a949bb909346263cc8fb645638f251301595af5 --- /dev/null +++ b/marked/Rel-18/38_series/38891/71d82d389da5fe06a4aefb661ea17af9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d9a2d061345ca767461b904e4de70943a798f2b714fa4a78b26bbd3deda5c79 +size 21840 diff --git a/marked/Rel-18/38_series/38891/723827e0738d2743c3b3423760a5c48e_img.jpg b/marked/Rel-18/38_series/38891/723827e0738d2743c3b3423760a5c48e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0d02b955cf796eca49a7b5a8fb6a81fa032d4b4 --- /dev/null +++ b/marked/Rel-18/38_series/38891/723827e0738d2743c3b3423760a5c48e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdb724360a636f9dd52e795f3a26992eb38084d53856714ce0bed619f1f0a4bc +size 31625 diff --git a/marked/Rel-18/38_series/38891/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-18/38_series/38891/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..127ef05368184b953eeb8b17b591f5dc2a9a4d9f --- /dev/null +++ b/marked/Rel-18/38_series/38891/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:101914a926e9e8e794f136beb4d0fbfde5d625c284821c91dbeefde85ffdb90a +size 122425 diff --git a/marked/Rel-18/38_series/38891/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-18/38_series/38891/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1e9d330e4809bad420284bb7c5e179fc0494423 --- /dev/null +++ b/marked/Rel-18/38_series/38891/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67e98f286ff7ca3ee78b29f5943406f017a7de4dafe6fdafa7d93c2cc399b6b8 +size 98633 diff --git a/marked/Rel-18/38_series/38891/77a781dfb114c3e2b399f876f1808cfd_img.jpg b/marked/Rel-18/38_series/38891/77a781dfb114c3e2b399f876f1808cfd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..964e9349895cc392142ef9d01a965409da01c735 --- /dev/null +++ b/marked/Rel-18/38_series/38891/77a781dfb114c3e2b399f876f1808cfd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d31bbb1085f53c1da9e40bc4fbe6a857316e628e00295e293d53c17a3ab0c532 +size 74774 diff --git a/marked/Rel-18/38_series/38891/79bd707e4636b9a1d4dbd443ef857814_img.jpg b/marked/Rel-18/38_series/38891/79bd707e4636b9a1d4dbd443ef857814_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dbf8bfa52982a7da359213a845b3d568bfd4017 --- /dev/null +++ b/marked/Rel-18/38_series/38891/79bd707e4636b9a1d4dbd443ef857814_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc9211d196130cd95fc5c8f28e56a2c1ebc24abc418f282f99798dd70db8141b +size 27950 diff --git a/marked/Rel-18/38_series/38891/7a0663ba11ddcae06cc5a490f81a7243_img.jpg b/marked/Rel-18/38_series/38891/7a0663ba11ddcae06cc5a490f81a7243_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6511fb5e2fb450fcfdb38760ac192061acbd4dfb --- /dev/null +++ b/marked/Rel-18/38_series/38891/7a0663ba11ddcae06cc5a490f81a7243_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1e6da3097a36407fde51324d28120664d5cdb61c67bce33c0f542d50d804d69 +size 26042 diff --git a/marked/Rel-18/38_series/38891/7a427d3f02cc89bd23f77068e257e90f_img.jpg b/marked/Rel-18/38_series/38891/7a427d3f02cc89bd23f77068e257e90f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c593609ac1bf3506477c1b186e71d88007e2636 --- /dev/null +++ b/marked/Rel-18/38_series/38891/7a427d3f02cc89bd23f77068e257e90f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1600fbb075d26c2a24d600bd4f13b433202ea74f984488dd9ea4f71ab98045a8 +size 126447 diff --git a/marked/Rel-18/38_series/38891/7bbc8cb3417e534d01e969cbc5f3d891_img.jpg b/marked/Rel-18/38_series/38891/7bbc8cb3417e534d01e969cbc5f3d891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19d13bb25ac6fcbae3e14ed07c28117c2b145c04 --- /dev/null +++ b/marked/Rel-18/38_series/38891/7bbc8cb3417e534d01e969cbc5f3d891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a71bf041644fdc92e2c46ce86cd5e7be0afea46c167d724d58d65ff4f8fa9dd +size 119707 diff --git a/marked/Rel-18/38_series/38891/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38891/7c0a9511fa02b6c2c125ff5be465186e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d19b5f3a1a923feac5e1b01120e28a8d3e562713 --- /dev/null +++ b/marked/Rel-18/38_series/38891/7c0a9511fa02b6c2c125ff5be465186e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9d1c70507a2f84c0d9e58516a4b25b8db52b82950618bc0e84b1143841c207 +size 49047 diff --git a/marked/Rel-18/38_series/38891/7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg b/marked/Rel-18/38_series/38891/7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6cb1e2dd1f430d35f38823b12fa77ddbe6ba792 --- /dev/null +++ b/marked/Rel-18/38_series/38891/7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:366c1f56ae17a1970d646368e17ed9e04d47058ac441ae6cf99f3243d45475dc +size 22724 diff --git a/marked/Rel-18/38_series/38891/7f687094e6abe34a9cf491942b296d9a_img.jpg b/marked/Rel-18/38_series/38891/7f687094e6abe34a9cf491942b296d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d69906be0a7cbd98d99d2297ba0e1c9d45539d0f --- /dev/null +++ b/marked/Rel-18/38_series/38891/7f687094e6abe34a9cf491942b296d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28f9e148d38087c876ef000601ad28144984af232bdfdd908f9f4b5ae995bb63 +size 53598 diff --git a/marked/Rel-18/38_series/38891/835ebc0e9ec15eea8eadc15448249226_img.jpg b/marked/Rel-18/38_series/38891/835ebc0e9ec15eea8eadc15448249226_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06d4b36dea2d9d10370ffb65bf921aecf995c7c8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/835ebc0e9ec15eea8eadc15448249226_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b8a66aacaf323f83dc4331dd9b8bb6beb09f7d6efcf09de63e0b855f4e092f6 +size 45633 diff --git a/marked/Rel-18/38_series/38891/84b564808c370adacae8a814707fb071_img.jpg b/marked/Rel-18/38_series/38891/84b564808c370adacae8a814707fb071_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c63e76f8608c33bbe4bcb8a325e6b229700038e0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/84b564808c370adacae8a814707fb071_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11bedcf6e72935d8f45dfe70fe1a5c74f66b4584b022e67e7802f908c881213e +size 83506 diff --git a/marked/Rel-18/38_series/38891/85b10db535b22e64c7d37f362705ddbf_img.jpg b/marked/Rel-18/38_series/38891/85b10db535b22e64c7d37f362705ddbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d2b9df6cb42296583a0963dc24689908fe6f57a --- /dev/null +++ b/marked/Rel-18/38_series/38891/85b10db535b22e64c7d37f362705ddbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c719926870ee4e05214dd7025b622371e07012a9489bcc59aac33bdb6a01f16a +size 37813 diff --git a/marked/Rel-18/38_series/38891/87c8b2afac072caf8623e534f71fcfa1_img.jpg b/marked/Rel-18/38_series/38891/87c8b2afac072caf8623e534f71fcfa1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0612e44ba9c6b5d9cf70c83cd4d4f9dacd0c3432 --- /dev/null +++ b/marked/Rel-18/38_series/38891/87c8b2afac072caf8623e534f71fcfa1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c2467f143f8282473eced034ef32d94a99a2fb1484c6601f872b776d2b86b00 +size 45815 diff --git a/marked/Rel-18/38_series/38891/87dfa94e14e0a4089d677c36b602c793_img.jpg b/marked/Rel-18/38_series/38891/87dfa94e14e0a4089d677c36b602c793_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7867b55f619591ebbad0c8a797e0dca3428d51d --- /dev/null +++ b/marked/Rel-18/38_series/38891/87dfa94e14e0a4089d677c36b602c793_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:679e5924932b3cbcb8490ce9a061e4c8419f26a864e76ac006e6d54b8946c56e +size 23113 diff --git a/marked/Rel-18/38_series/38891/89dcb02be40d2949bb93de93bbf213d5_img.jpg b/marked/Rel-18/38_series/38891/89dcb02be40d2949bb93de93bbf213d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66ec0d1549f2a760d643c220807f199725d0909d --- /dev/null +++ b/marked/Rel-18/38_series/38891/89dcb02be40d2949bb93de93bbf213d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be66fe850e8d78dad199f9a99bfae3c1ff7b88f2158896cd59ff4f60de164f29 +size 23110 diff --git a/marked/Rel-18/38_series/38891/8ba6b5c123d6a3d796c2570e5975cff5_img.jpg b/marked/Rel-18/38_series/38891/8ba6b5c123d6a3d796c2570e5975cff5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0419b924ff01ef7bcbb8e8595fc10af99d4cefe --- /dev/null +++ b/marked/Rel-18/38_series/38891/8ba6b5c123d6a3d796c2570e5975cff5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c78a5a4d04f22ba30927e76053a9753088beadf71a8e36a1ec9b888acae64b0d +size 38432 diff --git a/marked/Rel-18/38_series/38891/8e21461e0c9384ec60322bedb1b1ab17_img.jpg b/marked/Rel-18/38_series/38891/8e21461e0c9384ec60322bedb1b1ab17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c90bacaab23f1d6d35227a7555279773a6b7d333 --- /dev/null +++ b/marked/Rel-18/38_series/38891/8e21461e0c9384ec60322bedb1b1ab17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bac2ca41b52c1496a2c5ba2a105fc001a64add4495a34dccbf2a32a175bd1abd +size 36662 diff --git a/marked/Rel-18/38_series/38891/8fe46741a1476acebc88235e1b6e0f0b_img.jpg b/marked/Rel-18/38_series/38891/8fe46741a1476acebc88235e1b6e0f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50e160d3cb7b10702736e22fe30f37fd3670316f --- /dev/null +++ b/marked/Rel-18/38_series/38891/8fe46741a1476acebc88235e1b6e0f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5505345d7641da35be2e8ab028a8394e0d47d89317223f6ca7a9243240d28f4 +size 27134 diff --git a/marked/Rel-18/38_series/38891/91f1a66918183ac1f85c438198c09376_img.jpg b/marked/Rel-18/38_series/38891/91f1a66918183ac1f85c438198c09376_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..026f6c7cea006307ad12668bc6ca0d32a51f1556 --- /dev/null +++ b/marked/Rel-18/38_series/38891/91f1a66918183ac1f85c438198c09376_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbfc854f752e56ecf878e0aff011cff5f48ec8c406bda249a666f04eea8ee6c6 +size 109293 diff --git a/marked/Rel-18/38_series/38891/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-18/38_series/38891/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7398d5839499e19a916dd30511ec509e88002960 --- /dev/null +++ b/marked/Rel-18/38_series/38891/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5b56e30ce2cd262b5ae46505964a41ab1ad3430857918ab22b7e74c309a7e44 +size 32256 diff --git a/marked/Rel-18/38_series/38891/933151db66eefe2e64a0a4da5d37e05e_img.jpg b/marked/Rel-18/38_series/38891/933151db66eefe2e64a0a4da5d37e05e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b322a0c0d22b1f527226e208a87b62e84513dbd0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/933151db66eefe2e64a0a4da5d37e05e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed94673349c48c5deef0579cf8af3c25dc9ddb1d4a84cdd129a6ac4f02bf6f6e +size 27139 diff --git a/marked/Rel-18/38_series/38891/93587f920736a2fdcefeba94b29f302a_img.jpg b/marked/Rel-18/38_series/38891/93587f920736a2fdcefeba94b29f302a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9ed1d4e47fae2c3ca220b5203e17ce6b6f4dcc6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/93587f920736a2fdcefeba94b29f302a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd9a22b42ae011cac1d12effde71d4348771dc52f02f319cf679a3915880c867 +size 31427 diff --git a/marked/Rel-18/38_series/38891/94389c644d3c25d99db7bc6d87bf5779_img.jpg b/marked/Rel-18/38_series/38891/94389c644d3c25d99db7bc6d87bf5779_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40e330f1cad692cfb399e7bd589794904f6622c1 --- /dev/null +++ b/marked/Rel-18/38_series/38891/94389c644d3c25d99db7bc6d87bf5779_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f10b2427e354561339fdc23e3b5f45abc62adeb46941e7a7513d80a5149e58f5 +size 26020 diff --git a/marked/Rel-18/38_series/38891/986edc52e3746371694590f8f64685a2_img.jpg b/marked/Rel-18/38_series/38891/986edc52e3746371694590f8f64685a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44c21cb4d109d8c13ffd27ee697fb829bc6c933e --- /dev/null +++ b/marked/Rel-18/38_series/38891/986edc52e3746371694590f8f64685a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4551bbbd258e99164a43aad0e32ab214ee8b5fe3070f17259d537234c55ac6d2 +size 37097 diff --git a/marked/Rel-18/38_series/38891/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-18/38_series/38891/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a858bf8eb64cf2ca0dea63cd9b398ba93b04aaf --- /dev/null +++ b/marked/Rel-18/38_series/38891/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b12425f96a9bd99aaa713bda09c5552ca569cd200d396a4c5ed4385baf931c1e +size 92183 diff --git a/marked/Rel-18/38_series/38891/9b00c87003f634db9c30ca1d94fd932d_img.jpg b/marked/Rel-18/38_series/38891/9b00c87003f634db9c30ca1d94fd932d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af5b84efeb81c606c42f73c3e69a28698684eb76 --- /dev/null +++ b/marked/Rel-18/38_series/38891/9b00c87003f634db9c30ca1d94fd932d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0f2b905eaeaeb415e55453c229462c76c1d51299c2d36cd3320c362265cdcd9 +size 43795 diff --git a/marked/Rel-18/38_series/38891/9b608887301fdfd2a3ccc9ae2b9bdb07_img.jpg b/marked/Rel-18/38_series/38891/9b608887301fdfd2a3ccc9ae2b9bdb07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bc798783a33892beabc37fb20b3e699a89b62ac --- /dev/null +++ b/marked/Rel-18/38_series/38891/9b608887301fdfd2a3ccc9ae2b9bdb07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4e10946bae8dc5af4870a9a64848811999866a330acc246281708c865364422 +size 54132 diff --git a/marked/Rel-18/38_series/38891/9c8070d46f1d2480a875239e792f1ef6_img.jpg b/marked/Rel-18/38_series/38891/9c8070d46f1d2480a875239e792f1ef6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..660af573f7c16a6371f47df072acf9f876c5b1ce --- /dev/null +++ b/marked/Rel-18/38_series/38891/9c8070d46f1d2480a875239e792f1ef6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61c6837ab81a8d29df3de152539823c9d3d1a71cad4d1b45a12d3a7a2fb94041 +size 38666 diff --git a/marked/Rel-18/38_series/38891/9d1abc573e35610946ece87a18cbe862_img.jpg b/marked/Rel-18/38_series/38891/9d1abc573e35610946ece87a18cbe862_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ac0bd0680e7bf8c212bb54d89f55e68494dedab --- /dev/null +++ b/marked/Rel-18/38_series/38891/9d1abc573e35610946ece87a18cbe862_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c2ca26455a820ce8317b45dbcbc02c822fa4bc1b832a2c44db4a8d941d17efb +size 45172 diff --git a/marked/Rel-18/38_series/38891/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg b/marked/Rel-18/38_series/38891/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c21ed35f6689220e1b5e3b8adb606d80b777187 --- /dev/null +++ b/marked/Rel-18/38_series/38891/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4dad0e8dd6c6c970484de92d7e827be910297f2d493ea31472a12cc70790de4 +size 67778 diff --git a/marked/Rel-18/38_series/38891/9e4179ffe4701bec67534299c4935049_img.jpg b/marked/Rel-18/38_series/38891/9e4179ffe4701bec67534299c4935049_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba6a6e2d2d5f425b68a91674c2f10315dd3e0c7a --- /dev/null +++ b/marked/Rel-18/38_series/38891/9e4179ffe4701bec67534299c4935049_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc8e4c1b582cc4ca3a1e759112e96852e579c2fb43055f7128dc83aebb19eae +size 52612 diff --git a/marked/Rel-18/38_series/38891/9e424b8261c786a419e456b01fae29ff_img.jpg b/marked/Rel-18/38_series/38891/9e424b8261c786a419e456b01fae29ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94596c8e2a36e61f523c81cc41a77ee85677cdc1 --- /dev/null +++ b/marked/Rel-18/38_series/38891/9e424b8261c786a419e456b01fae29ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e892ec5033255251ea0061b287cfb0c363dfa8cede1c2264ef24d5c89b53b5aa +size 27451 diff --git a/marked/Rel-18/38_series/38891/a01cde7cbe4b1f1e275f4bcfce07433e_img.jpg b/marked/Rel-18/38_series/38891/a01cde7cbe4b1f1e275f4bcfce07433e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e4928be8243dc9e58b730157f4f6f9b8495d380 --- /dev/null +++ b/marked/Rel-18/38_series/38891/a01cde7cbe4b1f1e275f4bcfce07433e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f237a6275c3d2c2b00233c12bebfb20abd860b2f4c7a24b9efa3a2dfb3623f69 +size 115071 diff --git a/marked/Rel-18/38_series/38891/a1545557e366b6302109d13360b199c3_img.jpg b/marked/Rel-18/38_series/38891/a1545557e366b6302109d13360b199c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9054d8c5ac5661adadbc33e20f32a3c8e696f44 --- /dev/null +++ b/marked/Rel-18/38_series/38891/a1545557e366b6302109d13360b199c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e5b22ad3ea833bb09f7e5b7fe2e9412fa1b9ae6aae5be3e02468e9b7bd7d9f4 +size 26770 diff --git a/marked/Rel-18/38_series/38891/a26b4f52392209236513dd503db41339_img.jpg b/marked/Rel-18/38_series/38891/a26b4f52392209236513dd503db41339_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..762e96d70b1ed1b373591a0e9edb7387c276b202 --- /dev/null +++ b/marked/Rel-18/38_series/38891/a26b4f52392209236513dd503db41339_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bb00ce9f86ebd765cc1923f664d94aaddfae75833efb0799b1c12507845980c +size 108072 diff --git a/marked/Rel-18/38_series/38891/a3010506e5136b6642bb97f569dc52a3_img.jpg b/marked/Rel-18/38_series/38891/a3010506e5136b6642bb97f569dc52a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6378be8ea34e1febb465fa73ed1102b027853fae --- /dev/null +++ b/marked/Rel-18/38_series/38891/a3010506e5136b6642bb97f569dc52a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9c33abb6071eec0f6419fcb71ff2abc85f0a7aef3865de37d613ec6255baf4 +size 37318 diff --git a/marked/Rel-18/38_series/38891/a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg b/marked/Rel-18/38_series/38891/a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f90747b229c032886fbbd344fa0a6ad7cef48229 --- /dev/null +++ b/marked/Rel-18/38_series/38891/a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09b952714abd3620eb55a19c80ddc579494fce745ed34823ba6f232a3c04b5b8 +size 65923 diff --git a/marked/Rel-18/38_series/38891/a7a4135af81158a102df055b2138f981_img.jpg b/marked/Rel-18/38_series/38891/a7a4135af81158a102df055b2138f981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a612cd7b1588584b0e9b131f037ce8ec0a6a6aa0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/a7a4135af81158a102df055b2138f981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a06630d6eddf426d648a8a4c50c72755a1f3f760145a16413965d9da169ff8cc +size 98607 diff --git a/marked/Rel-18/38_series/38891/a96c7e19f53f2350db97a90738a6fb51_img.jpg b/marked/Rel-18/38_series/38891/a96c7e19f53f2350db97a90738a6fb51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba9502c09953a82e622c876d000a4db8d89bbf6c --- /dev/null +++ b/marked/Rel-18/38_series/38891/a96c7e19f53f2350db97a90738a6fb51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41dd49fb40c3602b66954fc51aaa4d766a1fa4b899c077474421bf6605e0f7d4 +size 132624 diff --git a/marked/Rel-18/38_series/38891/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg b/marked/Rel-18/38_series/38891/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cef9874c56db4bac3278f7528663a2ead9f2e91d --- /dev/null +++ b/marked/Rel-18/38_series/38891/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fd5ad9afa395cc38aa6e3b7cb4feabc8ed50668babe4379cb38810b9efaa028 +size 68645 diff --git a/marked/Rel-18/38_series/38891/aefc1d56f34faf0b81de8302e695340e_img.jpg b/marked/Rel-18/38_series/38891/aefc1d56f34faf0b81de8302e695340e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7da3537767414c1d04f5b517ba65b261b7b9700d --- /dev/null +++ b/marked/Rel-18/38_series/38891/aefc1d56f34faf0b81de8302e695340e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce0b0074ebec591cf4bc3b86665d21bdb13a2a6cf2de00c70760198efb1bb969 +size 89151 diff --git a/marked/Rel-18/38_series/38891/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg b/marked/Rel-18/38_series/38891/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05d61fe825a3b3e6e9beb0f172f0285397cc46dc --- /dev/null +++ b/marked/Rel-18/38_series/38891/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81ccef02204536d7a4d476df1be065c3e8da43465345707de2fdb66a63a02697 +size 37503 diff --git a/marked/Rel-18/38_series/38891/b387daba28c5aa523b84b26d6ba3d177_img.jpg b/marked/Rel-18/38_series/38891/b387daba28c5aa523b84b26d6ba3d177_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ef89eb81b53ed7d330483db8f0fe7d2eeba19a6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/b387daba28c5aa523b84b26d6ba3d177_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7f61d7bd83f42277613c3bd49dfd1c0ea2c9dae0cb5f959d9761eaaca2138b8 +size 56351 diff --git a/marked/Rel-18/38_series/38891/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg b/marked/Rel-18/38_series/38891/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be1f71133497e3c08fcfe2f754e0ebdb9c6b15ff --- /dev/null +++ b/marked/Rel-18/38_series/38891/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c4f25e39a17eb7d92a2de4f0ce301b089de7958a39093c3d1fa16ee6d868c37 +size 111265 diff --git a/marked/Rel-18/38_series/38891/b5cea511e0342583600125d1ccbec500_img.jpg b/marked/Rel-18/38_series/38891/b5cea511e0342583600125d1ccbec500_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d81526aaa00b44787004d2620e93965cbaa35b8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/b5cea511e0342583600125d1ccbec500_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:660a12ccb28db64bc55696527c64efe94f94ee6444447554933a24399fae9da4 +size 28602 diff --git a/marked/Rel-18/38_series/38891/b71190d39f5e641548d0f091e94e663d_img.jpg b/marked/Rel-18/38_series/38891/b71190d39f5e641548d0f091e94e663d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..136c0b2cf8b553d5e0db5075c0df62e0c0446d10 --- /dev/null +++ b/marked/Rel-18/38_series/38891/b71190d39f5e641548d0f091e94e663d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:018f4567c7389eb5a48214125d036c17e3d63208e7199e22ae55639c45100e1f +size 102873 diff --git a/marked/Rel-18/38_series/38891/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg b/marked/Rel-18/38_series/38891/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f88f2afc3d93556c6b1ff6736a0c527779e95d62 --- /dev/null +++ b/marked/Rel-18/38_series/38891/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be903bd722a6c9df66e19651a615752af04da23c45c4f87ef29d42135a4c03c3 +size 60980 diff --git a/marked/Rel-18/38_series/38891/ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg b/marked/Rel-18/38_series/38891/ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce648402a2969f9e23cbbd31cc25312a9692766e --- /dev/null +++ b/marked/Rel-18/38_series/38891/ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb907bf18207694aeb85f8c283f1e783066571fc5f34e323f60c613c3b60c83d +size 21949 diff --git a/marked/Rel-18/38_series/38891/bac21fd48fcd7f025c723590e07d1823_img.jpg b/marked/Rel-18/38_series/38891/bac21fd48fcd7f025c723590e07d1823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a22c1004522af0052340660aeb6c0351e69083c7 --- /dev/null +++ b/marked/Rel-18/38_series/38891/bac21fd48fcd7f025c723590e07d1823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d94a34f36f92cb7b1330852a6927e8299c79d4c7773208cabe63b0d398d96062 +size 36073 diff --git a/marked/Rel-18/38_series/38891/bc3afa6786f4e6e882edded4b64a3ed0_img.jpg b/marked/Rel-18/38_series/38891/bc3afa6786f4e6e882edded4b64a3ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37dd688641082322f0406ae5fc5a767bcba49bc6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/bc3afa6786f4e6e882edded4b64a3ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c0c078ee943f6611cf5a87c1f806c74b97ee53ed92ca3b4feea1b37f98c7b2d +size 33821 diff --git a/marked/Rel-18/38_series/38891/bf5785e70ae74c9228ac60009aeb677e_img.jpg b/marked/Rel-18/38_series/38891/bf5785e70ae74c9228ac60009aeb677e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd64d122ccee860f90759c7c8d43b44134953c03 --- /dev/null +++ b/marked/Rel-18/38_series/38891/bf5785e70ae74c9228ac60009aeb677e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b891194bab5ab0cea118ec82d0c0977bf3cc8bfe6363af8a801467ae2552ac8a +size 49781 diff --git a/marked/Rel-18/38_series/38891/bfde27036f8cdbc8ed561e547f0a9483_img.jpg b/marked/Rel-18/38_series/38891/bfde27036f8cdbc8ed561e547f0a9483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fe8e10b7cb24bf9af25c3b6bea424fe3b60d4ac --- /dev/null +++ b/marked/Rel-18/38_series/38891/bfde27036f8cdbc8ed561e547f0a9483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59d82fa0404bad0ebb7a4a14ed9dbc4f3a160a275593b89f1a9e0f5090d07333 +size 50961 diff --git a/marked/Rel-18/38_series/38891/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-18/38_series/38891/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44c4813d459a8f1eaeb1146a3ee65beeac0e48eb --- /dev/null +++ b/marked/Rel-18/38_series/38891/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbcd906aaf76d0ffc82d4fa503c01c326bca372f8b7767d12ed95bc4ec7a3ce3 +size 30873 diff --git a/marked/Rel-18/38_series/38891/c21fe89d8034ec5b80bd47c1cd710202_img.jpg b/marked/Rel-18/38_series/38891/c21fe89d8034ec5b80bd47c1cd710202_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85fc56ae96062d6f51ae5eb3fe7ad852a292fea2 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c21fe89d8034ec5b80bd47c1cd710202_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:445fb90864cdf6c5769204fe33850e797f9d128e7fac6a3351f8b3766d73eb9d +size 73607 diff --git a/marked/Rel-18/38_series/38891/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg b/marked/Rel-18/38_series/38891/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c7df3275f2f1085e9a45692cc3a52e429a737fd --- /dev/null +++ b/marked/Rel-18/38_series/38891/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be58c258683b4b42cc95d4d77024e009c033aa60d60699bf5415e6c0c7fb50db +size 44387 diff --git a/marked/Rel-18/38_series/38891/c22de2cf24282469c2a2cf1018928116_img.jpg b/marked/Rel-18/38_series/38891/c22de2cf24282469c2a2cf1018928116_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8766bd41b914f563d1b9579b3dbf8e165ccf94b --- /dev/null +++ b/marked/Rel-18/38_series/38891/c22de2cf24282469c2a2cf1018928116_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d69fc3653d00b63c1d0ae3fc173112273112f082046d85b77b62ec317e557b52 +size 131894 diff --git a/marked/Rel-18/38_series/38891/c2358318fd81a98b7f4eb656e6d67c7a_img.jpg b/marked/Rel-18/38_series/38891/c2358318fd81a98b7f4eb656e6d67c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eac0b813d469f98f3cc82fd24b2556e0145cc809 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c2358318fd81a98b7f4eb656e6d67c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1803059e25395c439f71c76cb7ca6f13256fb469b65f84262750d94c9638e26a +size 45525 diff --git a/marked/Rel-18/38_series/38891/c5616180b57a463028fe4da4a404d4c1_img.jpg b/marked/Rel-18/38_series/38891/c5616180b57a463028fe4da4a404d4c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34a2a5aff18ebb5f45d1934813b92ace0f51bab2 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c5616180b57a463028fe4da4a404d4c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:290680a3f47ae574cc771fa5f6951178af6653fb60800f05cf7b7a7a8a8fd919 +size 57890 diff --git a/marked/Rel-18/38_series/38891/c654787c0bbc1559e1c194ab74987529_img.jpg b/marked/Rel-18/38_series/38891/c654787c0bbc1559e1c194ab74987529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a22b7cb587ecef593db3b952e0abd756437f4171 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c654787c0bbc1559e1c194ab74987529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59764bad71a24da7e9c40c60cfa9ea8d8aa2c564719b6f5e492b35900ce29ca9 +size 64338 diff --git a/marked/Rel-18/38_series/38891/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38891/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaeb5f02364808b896583aeb23803b58face3079 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bb98aaf8f224c348b0c2ed6996edfdd2c68ab20b34e30037a5b6e416128bb19 +size 25769 diff --git a/marked/Rel-18/38_series/38891/c742b64169a38a7f3f990172019878c8_img.jpg b/marked/Rel-18/38_series/38891/c742b64169a38a7f3f990172019878c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b75b51ace8bd486b298fba821e903de67ccb01e7 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c742b64169a38a7f3f990172019878c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f00f213bb2eb9d232a4c432360a22a7a889a9009ca2a10c45509aa92c650bd57 +size 39544 diff --git a/marked/Rel-18/38_series/38891/c8380fb19e591e67d5e053b03ae58f32_img.jpg b/marked/Rel-18/38_series/38891/c8380fb19e591e67d5e053b03ae58f32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd254a131f32457f40d7989aa5b32cda650ab2c9 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c8380fb19e591e67d5e053b03ae58f32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2565412d799869e9190a15505ce6691c2effc52b8462f68e28455a69f4caaa5a +size 79924 diff --git a/marked/Rel-18/38_series/38891/c90b2604dca3815ab852de4349790ebb_img.jpg b/marked/Rel-18/38_series/38891/c90b2604dca3815ab852de4349790ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dbe0edca6c5a71a80ed8b1520d60d627398dab8 --- /dev/null +++ b/marked/Rel-18/38_series/38891/c90b2604dca3815ab852de4349790ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d4f2ecd2fee7d6e78ecc77005b212142c90e967b2319317955c4685f39f28c4 +size 56792 diff --git a/marked/Rel-18/38_series/38891/caeb46d58919c727aa9d338ae9492077_img.jpg b/marked/Rel-18/38_series/38891/caeb46d58919c727aa9d338ae9492077_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b33b9dd02de68182faf9317caaacef38cbdab8f --- /dev/null +++ b/marked/Rel-18/38_series/38891/caeb46d58919c727aa9d338ae9492077_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daa00cdef8bd7b38339542d39223ec791f1aca969229b22d824b5120349906b9 +size 137316 diff --git a/marked/Rel-18/38_series/38891/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Rel-18/38_series/38891/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bfafea4e58c6944db1a093b1926203f75994342 --- /dev/null +++ b/marked/Rel-18/38_series/38891/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fce8111a281c489f11f64118a545b6d2369945717208b0442e9e9720eeffcbc2 +size 43016 diff --git a/marked/Rel-18/38_series/38891/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg b/marked/Rel-18/38_series/38891/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b449b1b95064e3ff4e466d63892e9ba3864d53d6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:182dcee73f23384c49d3b8812682df7243fdd87e28a07538652780f2a13379ea +size 21579 diff --git a/marked/Rel-18/38_series/38891/ccb9204e004de0c9e190f4773e940efd_img.jpg b/marked/Rel-18/38_series/38891/ccb9204e004de0c9e190f4773e940efd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a44e5e70112f36d5a25f5e38d215f3617d2a419f --- /dev/null +++ b/marked/Rel-18/38_series/38891/ccb9204e004de0c9e190f4773e940efd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af15b163338d70126f77d24444ca1c78f88c87ede7c11aac261ee79f1626f1da +size 79719 diff --git a/marked/Rel-18/38_series/38891/cd31d0e7e4b524e074808154dd279205_img.jpg b/marked/Rel-18/38_series/38891/cd31d0e7e4b524e074808154dd279205_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a2841ce217f103e39c043b51c126906b2f0d6e6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/cd31d0e7e4b524e074808154dd279205_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:561d0a28101c62e3cb244f0f353424b4c6832d02d372442d51396cf2c90272af +size 30655 diff --git a/marked/Rel-18/38_series/38891/cd965c09af15211ca52d38d49be7b515_img.jpg b/marked/Rel-18/38_series/38891/cd965c09af15211ca52d38d49be7b515_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfe6bca3b9d6c4716d141901f3e849c7cfb7ab2e --- /dev/null +++ b/marked/Rel-18/38_series/38891/cd965c09af15211ca52d38d49be7b515_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1a77f39767d72db7a66901a76fab378ebe48431e7965ab681a111368b158c58 +size 28488 diff --git a/marked/Rel-18/38_series/38891/cfc852835f2d91bea8dc074568937e22_img.jpg b/marked/Rel-18/38_series/38891/cfc852835f2d91bea8dc074568937e22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aa0a21ca59ef2cf264ab9ee9a0abf6ee0284530 --- /dev/null +++ b/marked/Rel-18/38_series/38891/cfc852835f2d91bea8dc074568937e22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c33d6ac5afdab41d067aba71c25e09297ca9b116480aab339a146fe70b3ca483 +size 142815 diff --git a/marked/Rel-18/38_series/38891/da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg b/marked/Rel-18/38_series/38891/da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597933ad81b188ca7325ad0e4305a8e0de55ace5 --- /dev/null +++ b/marked/Rel-18/38_series/38891/da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2cf30f51ee4b9c9b4e94a1e54b9bde69e1a801596c88ddff18b32ee661e7c5d +size 60512 diff --git a/marked/Rel-18/38_series/38891/dbc1673750fd53d4203f4d93963fdab6_img.jpg b/marked/Rel-18/38_series/38891/dbc1673750fd53d4203f4d93963fdab6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00b9b2f4a2a707ab85622eb2ae906554f44d6a32 --- /dev/null +++ b/marked/Rel-18/38_series/38891/dbc1673750fd53d4203f4d93963fdab6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f868edf3b89953f1c6a2bdb8645c1cbf680d88d45ecbf448201ca068c505a3f +size 45469 diff --git a/marked/Rel-18/38_series/38891/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg b/marked/Rel-18/38_series/38891/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15d5164006e708b5de44791385d0bc42f96099f5 --- /dev/null +++ b/marked/Rel-18/38_series/38891/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76493ed432e547014b20cb8e0196148d9719bac3a5d3b275071bc5bf71fa167b +size 43065 diff --git a/marked/Rel-18/38_series/38891/decf37f29e8a82a8d6a742351ab68a24_img.jpg b/marked/Rel-18/38_series/38891/decf37f29e8a82a8d6a742351ab68a24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb822420611c70d5f1011c58b04e5c7e4049715e --- /dev/null +++ b/marked/Rel-18/38_series/38891/decf37f29e8a82a8d6a742351ab68a24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:737d61c3bd2aa08064b80826ed7224c32d4c532ab0c6ed1517117609bcba7e76 +size 93491 diff --git a/marked/Rel-18/38_series/38891/dffea0f06bd8a4658bc3394c7dbfdb5c_img.jpg b/marked/Rel-18/38_series/38891/dffea0f06bd8a4658bc3394c7dbfdb5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11249ecf5fbe7e438d85f6e07eb11339e9dc0a6a --- /dev/null +++ b/marked/Rel-18/38_series/38891/dffea0f06bd8a4658bc3394c7dbfdb5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdfd8c4a9c56050cfc42d6c95d5d7a57d8cab85c12eda0cb435627672f507403 +size 30498 diff --git a/marked/Rel-18/38_series/38891/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-18/38_series/38891/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcb471d1a5abd777bd04c45880317fedecb745ed --- /dev/null +++ b/marked/Rel-18/38_series/38891/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b20cdb7c21460e9801f4b58aea29adaee87d20b7d529446b79514c117691e038 +size 48163 diff --git a/marked/Rel-18/38_series/38891/e01c6273c4177746475715ee9c17a882_img.jpg b/marked/Rel-18/38_series/38891/e01c6273c4177746475715ee9c17a882_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a00b96324126dc9b459f980ccab7295aaf4b4bab --- /dev/null +++ b/marked/Rel-18/38_series/38891/e01c6273c4177746475715ee9c17a882_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d191d6ada1b5b10355bd81f88284c4e09537479ea5889be46a96894fd6cc86b +size 65803 diff --git a/marked/Rel-18/38_series/38891/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg b/marked/Rel-18/38_series/38891/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccec7f7de4ea28adfa7006fc6fe8423f4f12ac45 --- /dev/null +++ b/marked/Rel-18/38_series/38891/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcf7dbb48898c34259b8e2c5577aa059e4ed8fabf67b457a874c856ab1bb28f6 +size 75691 diff --git a/marked/Rel-18/38_series/38891/e046996962d6740cf050a5640e0c6b40_img.jpg b/marked/Rel-18/38_series/38891/e046996962d6740cf050a5640e0c6b40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23dcdf51e6b44d8b8c054cf997b659daab0f47ec --- /dev/null +++ b/marked/Rel-18/38_series/38891/e046996962d6740cf050a5640e0c6b40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ae0c6bb2581329efaa4d463665a5480535bae0dede1de1a684f3e3a19abffda +size 25975 diff --git a/marked/Rel-18/38_series/38891/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg b/marked/Rel-18/38_series/38891/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be156aad7207f0ff7e6ce6e69da23efaaeae02a0 --- /dev/null +++ b/marked/Rel-18/38_series/38891/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:326511498de26177312705324837b453325615dd974fb5b076aadc403c42c272 +size 133572 diff --git a/marked/Rel-18/38_series/38891/e51f9764097b236acbf8f544491dd24f_img.jpg b/marked/Rel-18/38_series/38891/e51f9764097b236acbf8f544491dd24f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98c6cd06fc100b1a6d427e3c5d7c8ca4ed93c286 --- /dev/null +++ b/marked/Rel-18/38_series/38891/e51f9764097b236acbf8f544491dd24f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6f4110b3071bf3654715c1786969c4440009ae67d7f8e5edb20d83497ea1840 +size 28442 diff --git a/marked/Rel-18/38_series/38891/e91633da5160c8af51a4ace6d3347f53_img.jpg b/marked/Rel-18/38_series/38891/e91633da5160c8af51a4ace6d3347f53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..347cdd8d0d616d06d3059c620146090c1863ae48 --- /dev/null +++ b/marked/Rel-18/38_series/38891/e91633da5160c8af51a4ace6d3347f53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fbe8ce242a0e0286e8cb4847d3c229665c6d81e43155f8937d2a55ea5d603bc +size 227562 diff --git a/marked/Rel-18/38_series/38891/ead8d1841c351608343c98f30e5f3f07_img.jpg b/marked/Rel-18/38_series/38891/ead8d1841c351608343c98f30e5f3f07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb483987025b6a6b0b6dca3b3f814c741be91bb5 --- /dev/null +++ b/marked/Rel-18/38_series/38891/ead8d1841c351608343c98f30e5f3f07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1327f5d2475f3ad52d669be560c02216d2b63b20ab499764b51479041143bebf +size 64308 diff --git a/marked/Rel-18/38_series/38891/eb6482b0b8b6063abda95a4465019f68_img.jpg b/marked/Rel-18/38_series/38891/eb6482b0b8b6063abda95a4465019f68_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff6ac07245775692030f417507842c6b82264b6 --- /dev/null +++ b/marked/Rel-18/38_series/38891/eb6482b0b8b6063abda95a4465019f68_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b95a5eaa598c6415d78c975695378763457581ca9de46e7cd71556acdd9caf6d +size 26543 diff --git a/marked/Rel-18/38_series/38891/ebce355620876e10f907f8b71926c112_img.jpg b/marked/Rel-18/38_series/38891/ebce355620876e10f907f8b71926c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dc95a4e0c26e6f22ae9ce035f1b17422213247c --- /dev/null +++ b/marked/Rel-18/38_series/38891/ebce355620876e10f907f8b71926c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4272c0342a48640080944458d7bbee286cdbd55b14c0e946828fbee2efdac501 +size 29839 diff --git a/marked/Rel-18/38_series/38891/ed2c3e8ce1a7479b617b38a843c6b782_img.jpg b/marked/Rel-18/38_series/38891/ed2c3e8ce1a7479b617b38a843c6b782_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..819e726ef954339bbefb642c27205249dc08b017 --- /dev/null +++ b/marked/Rel-18/38_series/38891/ed2c3e8ce1a7479b617b38a843c6b782_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca9f4b2ca15a0d01371de8392b50b92a3fc03e80ce1482e42256b96886a60b25 +size 43596 diff --git a/marked/Rel-18/38_series/38891/f329aa6f0e390067766cb33dd5ddf93a_img.jpg b/marked/Rel-18/38_series/38891/f329aa6f0e390067766cb33dd5ddf93a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aa88a3bc2fd52aebb24d5861cba73b169229f1e --- /dev/null +++ b/marked/Rel-18/38_series/38891/f329aa6f0e390067766cb33dd5ddf93a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16cac07bc30ca7f5467916148bfc848c0e091f2958bcdd960bcb6c11ad8183d6 +size 61082 diff --git a/marked/Rel-18/38_series/38891/f3c5e85b70f94b9c3c521f594d69539f_img.jpg b/marked/Rel-18/38_series/38891/f3c5e85b70f94b9c3c521f594d69539f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abe14495d94fd9bf5027126ddfad866263ebf011 --- /dev/null +++ b/marked/Rel-18/38_series/38891/f3c5e85b70f94b9c3c521f594d69539f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e59f471f54d85b07afb4cbea6ab6a4c7fb6bf214a1c01d3e2a33b89d0c4c7f0d +size 20833 diff --git a/marked/Rel-18/38_series/38891/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-18/38_series/38891/f455955c4bc84005728b4138f19098dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12e487a43a93900ce39e00b1be6e8d2a432c2cc2 --- /dev/null +++ b/marked/Rel-18/38_series/38891/f455955c4bc84005728b4138f19098dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8411958dab5332c45bc3edc2dd4fe03566f6cfd4973825a989ca181a6e5f47cd +size 43788 diff --git a/marked/Rel-18/38_series/38891/f519a5be118c846f631c992412353fb9_img.jpg b/marked/Rel-18/38_series/38891/f519a5be118c846f631c992412353fb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a8fb861ca77526f06da6826b0fc17701b77385d --- /dev/null +++ b/marked/Rel-18/38_series/38891/f519a5be118c846f631c992412353fb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d339017f133c4caf732a9be8454198cbcb2d97ded6adff7e737f0894edaaa1d5 +size 23235 diff --git a/marked/Rel-18/38_series/38891/f68421f5d184c116a7061977a9057e63_img.jpg b/marked/Rel-18/38_series/38891/f68421f5d184c116a7061977a9057e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f29fe118385441e221801c51ec51db45fd5bd593 --- /dev/null +++ b/marked/Rel-18/38_series/38891/f68421f5d184c116a7061977a9057e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781770ddfc7822a6c07b2c2416f17e222a9b23f6a2d03a9c6ec88833dcffa012 +size 83038 diff --git a/marked/Rel-18/38_series/38891/f6eaafb7dc1fa9a73c518dca33bc801b_img.jpg b/marked/Rel-18/38_series/38891/f6eaafb7dc1fa9a73c518dca33bc801b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92f07ff0b185c7d4607691348e7cd620d5570358 --- /dev/null +++ b/marked/Rel-18/38_series/38891/f6eaafb7dc1fa9a73c518dca33bc801b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8c3e0ae3f3b3e0cb518acf63f4cd40ecd7d90dae74f6b3a5d6ed8569aac5421 +size 83910 diff --git a/marked/Rel-18/38_series/38891/fa46b2ae8b3e08aaf2e6a0d53decd363_img.jpg b/marked/Rel-18/38_series/38891/fa46b2ae8b3e08aaf2e6a0d53decd363_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d35ffdad40d0fcc69d7d05185bf1ce9ef474150c --- /dev/null +++ b/marked/Rel-18/38_series/38891/fa46b2ae8b3e08aaf2e6a0d53decd363_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67a247e2618f4618186898d97c95c032114f3d5df822680fa21b045a8acdf31f +size 41075 diff --git a/marked/Rel-18/38_series/38891/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg b/marked/Rel-18/38_series/38891/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49c3968553875b1e1acc1bda63c45444fd757fff --- /dev/null +++ b/marked/Rel-18/38_series/38891/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3514ca282402e77784cc4cb0a270b84b87205ec60a1844df27d15f87143e145c +size 54137 diff --git a/marked/Rel-18/38_series/38891/fd188843e5acb8e0d76372860b5f5962_img.jpg b/marked/Rel-18/38_series/38891/fd188843e5acb8e0d76372860b5f5962_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..825d70bc84935a8f69cd1952c6685fa7aa0fcac5 --- /dev/null +++ b/marked/Rel-18/38_series/38891/fd188843e5acb8e0d76372860b5f5962_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61ef8cb09812f69844cbe611599781e7f26004fc872b88ec179022ded0c3f24d +size 22628 diff --git a/marked/Rel-18/38_series/38891/fdae4b1c1863349bc913d92f62cc2eee_img.jpg b/marked/Rel-18/38_series/38891/fdae4b1c1863349bc913d92f62cc2eee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fe3d90c7d868cd3d05a4302ad320c2eb8dcdb7f --- /dev/null +++ b/marked/Rel-18/38_series/38891/fdae4b1c1863349bc913d92f62cc2eee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2447d2abab9ed60b16d5f699ddbca08c2f6ec7783376286a863f8c33e273a96 +size 75373 diff --git a/marked/Rel-18/38_series/38891/fe753d01ad5fe6cf150018c958173c6d_img.jpg b/marked/Rel-18/38_series/38891/fe753d01ad5fe6cf150018c958173c6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f95a351b7906ffd7c0d6dd5b662c314c573c482 --- /dev/null +++ b/marked/Rel-18/38_series/38891/fe753d01ad5fe6cf150018c958173c6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f1f349de2a5b8314b1bfe6bea0c0797071e382202fc47060965276700674d9 +size 21583 diff --git a/marked/Rel-18/38_series/38891/fed39b841ae2dce01088b84bfc1e2789_img.jpg b/marked/Rel-18/38_series/38891/fed39b841ae2dce01088b84bfc1e2789_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b32677dc383382833b97e85ed9ec6a2cea50418 --- /dev/null +++ b/marked/Rel-18/38_series/38891/fed39b841ae2dce01088b84bfc1e2789_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e7279190ddfe537b4af9dbbbdb7a6efc24b1438fc78934c8321e5b7cb661c42 +size 47854 diff --git a/marked/Rel-18/38_series/38891/ff2492be4fa814905acbad18f261b8a5_img.jpg b/marked/Rel-18/38_series/38891/ff2492be4fa814905acbad18f261b8a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f208abfc235e9f59324711d010e55821e2e99bd --- /dev/null +++ b/marked/Rel-18/38_series/38891/ff2492be4fa814905acbad18f261b8a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57dfe32b991d004bda319fcb2e5d3422a0bab8b48dd24cb170f133ed19030a07 +size 45466 diff --git a/marked/Rel-18/38_series/38891/ffa757b152f924c42ca8c3141fc3f562_img.jpg b/marked/Rel-18/38_series/38891/ffa757b152f924c42ca8c3141fc3f562_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd8826720d18ed1af6c7938de79a7053512aa4b1 --- /dev/null +++ b/marked/Rel-18/38_series/38891/ffa757b152f924c42ca8c3141fc3f562_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b270eddc320af1e8ad74e75f41e7df15f3af6323b8311475da15a6030c8570d3 +size 52897 diff --git a/marked/Rel-18/38_series/38891/raw.md b/marked/Rel-18/38_series/38891/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..94f8cc5cb941b80a8e297331c99f6aa1aa86d809 --- /dev/null +++ b/marked/Rel-18/38_series/38891/raw.md @@ -0,0 +1,5665 @@ + + +# 3GPP TR 38.891 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) Further enhancements of NR RF requirements for frequency range 2 (FR2) for Rel-18 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------|-----| +| Foreword..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations..... | 8 | +| 4 Background..... | 8 | +| 5 Study for FR2 UL 256QAM..... | 8 | +| 5.1 General..... | 8 | +| 5.2 Simulation..... | 9 | +| 5.2.1 System level simulation..... | 9 | +| 5.2.1.1 Simulation assumptions..... | 9 | +| 5.2.1.2 Simulation results from Nokia..... | 9 | +| 5.2.1.3 Simulation results from ZTE..... | 18 | +| 5.2.1.4 Simulation results from vivo..... | 21 | +| 5.2.1.5 Simulation results from Ericsson..... | 23 | +| 5.2.1.6 Simulation results from Xiaomi..... | 27 | +| 5.2.1.7 Simulation results from LG Electronics..... | 30 | +| 5.2.1.8 Simulation results from Sony..... | 32 | +| 5.2.1.9 Summary for system level simulation results..... | 34 | +| 5.2.2 Link level simulation..... | 36 | +| 5.2.2.1 Simulation assumptions..... | 36 | +| 5.2.2.2 Simulation results from Nokia..... | 37 | +| 5.2.2.3 Simulation results from LG Electronics..... | 40 | +| 5.2.2.4 Simulation results from vivo..... | 49 | +| 5.2.2.5 Simulation results from Huawei..... | 57 | +| 5.2.2.6 Simulation results from Sony..... | 60 | +| 5.2.2.7 Simulation results from Xiaomi..... | 63 | +| 5.2.2.8 Simulation results from ZTE..... | 73 | +| 5.2.2.9 Simulation results from Ericsson..... | 81 | +| 5.2.2.10 Summary for 29GHz simulation results..... | 84 | +| 5.2.2.11 Summary for 39GHz simulation results..... | 85 | +| 5.2.2.12 Summary for 48GHz simulation results..... | 86 | +| 5.2.3 Phase noise profiles evaluation..... | 87 | +| 5.2.3.1 Simulation assumptions..... | 87 | +| 5.2.3.2 Phase noise profiles..... | 87 | +| 5.2.3.3 Simulation results from Xiaomi..... | 88 | +| 5.2.3.4 Simulation results from vivo..... | 90 | +| 5.2.3.5 Simulation results from Anritsu Limited..... | 91 | +| 5.2.3.6 Simulation results from MediaTek Inc..... | 93 | +| 5.2.3.7 Simulation results from LG Electronics..... | 94 | +| 5.2.3.8 Simulation results from Sony..... | 97 | +| 5.2.3.9 Simulation results from Qualcomm..... | 97 | +| 5.2.3.10 Simulation results from ZTE..... | 99 | +| 5.2.3.11 Summary the simulation results for 29GHz phase noise profile evaluation..... | 101 | +| 5.2.3.12 Summary the simulation results for 39GHz phase noise profile evaluation..... | 102 | +| 5.2.4 MPR simulation..... | 104 | +| 5.2.4.1 Simulation assumptions..... | 104 | +| 5.2.4.2 Simulation results from LGE..... | 106 | +| 5.2.4.3 Simulation results from Nokia..... | 116 | +| 5.2.4.4 Simulation results from ZTE..... | 118 | +| 5.2.4.5 Simulation results from vivo..... | 121 | +| 5.2.4.6 Simulation results from Xiaomi..... | 124 | +| 5.2.4.7 Simulation results from Sony..... | 131 | + +| | | | +|---------------------------------------------------|-----------------------------------------------------------------------|------------| +| 5.2.4.8 | Simulation results from MediaTek..... | 132 | +| 5.2.4.9 | Simulation results from Qualcomm..... | 134 | +| 5.2.4.10 | Simulation results from Huawei..... | 138 | +| 5.2.4.11 | Summary of the simulation results for 29GHz MPR..... | 139 | +| 5.2.4.12 | Summary of the simulation results for 39GHz MPR..... | 142 | +| 5.2.5 | Simulation for PTRS configurations..... | 142 | +| 5.2.5.1 | Simulation results from Qualcomm..... | 142 | +| 5.2.5.2 | Simulation results from vivo..... | 143 | +| 5.2.5.3 | Simulation results from Xiaomi..... | 144 | +| 5.2.5.4 | Simulation results from ZTE..... | 155 | +| 5.2.5.5 | Summary the CP-OFDM simulation results for PTRS configuration..... | 157 | +| 5.2.5.6 | Summary the DFT-s-OFDM simulation results for PTRS configuration..... | 158 | +| 5.3 | EVM test..... | 162 | +| 5.3.1 | CPE compensation methods..... | 162 | +| 5.3.2 | PTRS correction methods..... | 162 | +| 5.3.3 | EVM calculation flow with PTRS..... | 162 | +| 5.4 | Implementation impact for UE..... | 163 | +| 5.5 | Specification impact..... | 163 | +| 5.6 | Conclusion..... | 163 | +| 6 | Study for beam correspondence..... | 167 | +| 6.1 | General..... | 167 | +| 6.2 | Implementation impact to UE..... | 167 | +| 6.3 | Specification Impact..... | 169 | +| 6.3.1 | RF..... | 169 | +| 6.3.2 | RRM..... | 170 | +| 6.4 | Testing impact..... | 170 | +| Annex A (informative): Change history..... | | 171 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +*In drafting the TS/TR, pay particular attention to the use of modal auxiliary verbs! TRs shall not contain any normative provisions.* + +In the present document, modal verbs have the following meanings: + +**shall** indicates a mandatory requirement to do something + +**shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +**should** indicates a recommendation to do something + +**should not** indicates a recommendation not to do something + +**may** indicates permission to do something + +**need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +**can** indicates that something is possible + +**cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document captures findings of the study on FR2 UL 256QAM and beam correspondence for RRC\_INACTIVE and initial access. The purpose of this TR is to study the performance gain and implementation aspects for FR2 UL 256QAM and to ensure good UE RACH msg1 performance and UL coverage in FR2 deployments by specifying the beam correspondence requirements for RRC\_INACTIVE and initial access as defined in Work Item “NR RF requirements enhancement for frequency range 2 (FR2), Phase 3” [2]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] RP-220967, “new WID: NR RF requirements enhancement for frequency range 2 (FR2), Phase 3”, Nokia, Xiaomi +- [3] 3GPP TR 38.803: "Study on new radio access technology: RF and co-existence aspects". + +# --- 3 Definitions of terms, symbols and abbreviations + +*This clause and its three subclauses are mandatory. The contents shall be shown as "void" if the TS/TR does not define any terms, symbols, or abbreviations.* + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +# --- 4 Background + +At the 3GPP RAN #95 meeting, the Work Item on “NR RF requirements enhancement for frequency range 2 (FR2), Phase 3” was approved for Rel-18. The objectives of the core part in the Work Item are as follows: + +## UL 256QAM + +- Investigate and enable UL 256QAM for FR2-1 [RAN4] + - Study the gain, operating SNR, phase noise model and implementation aspects + - Specify the UE RF requirements + - First priority: Targeted power classes are PC1, PC2 and PC5 + - Second priority: Targeted power class is PC3 + +### Beam correspondence requirements for RRC\_INACTIVE and initial access + +- Specify UE beam correspondence requirements for initial access and RRC\_INACTIVE state, for SSB-based beam correspondence without UL beam sweeping [RAN4 RF] +- For RRC\_INACTIVE specify at least requirements for Random Access SDT and Configured Grant SDT +- Requirements for other transmission within RRC\_INACTIVE state are not precluded. +- For initial access, specify requirements and verification of beam correspondence requirements based on msg1 spherical coverage (at least) + +Study the potential impact on testability aspects (i.e., test time). + +This TR aims to study the objectives and further capture the impact on the specification if applicable. + +# --- 5 Study for FR2 UL 256QAM + +*Editor's note: This clause collects the simulation results and implementation aspects for FR2 UL 256QAM study for Rel-18. If necessary, new agenda can be assigned.* + +## 5.1 General + +The study for FR2-1 UL 256QAM are carried out based on following parts: + +- Feasibility study for PC1/2/5 based on system level simulation and link level simulation +- Evaluation of Phase noise profile based on simulation. +- MPR evaluation based on simulation. +- PTRS configuration study based on simulation. +- EVM test. + +## 5.2 Simulation + +### 5.2.1 System level simulation + +The system level simulation as supplementary for link level simulation is to check whether the UE working on FR2 UL 256QAM can achieve target SNR at BS side and to further confirm FR2 UL 256QAM is feasible. + +#### 5.2.1.1 Simulation assumptions + +**Table 5.2.1.1-1 System level simulation assumptions** + +| Parameters | Urban macro | Indoor | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------| +| Network layout | hexagonal grid, 19 macro sites, 3 sectors per site with wrap around | 50m x 120m, 12BSs | | +| Inter-site distance | 200m (baseline)
300m (optional) | 20m | | +| BS antenna height | 25 m | 3 m | | +| UE location | Outdoor/indoor | Outdoor and indoor | Indoor | +| | Indoor UE ratio | 20% | | +| | Low/high Penetration loss ratio | 50% low loss, 50% high loss | | +| | LOS/NLOS | LOS and NLOS | LOS and NLOS | +| | UE antenna height | Same as 3D-Uma in TR 36.873 | 1.5 m | +| UE distribution (horizontal) | Uniform | | | +| Minimum BS – UE distance (2D) | 35 m | 0 m | | +| Shadowing correlation | Between cells: 1.0
Between sites: 0.5 | | | +| Pathloss | Uma LOS and NLOS in table 5.2.2.1-1 of 38.803 | InH – Office LOS and NLOS in table 5.2.2.1-1 of 38.803 | | +| Carrier frequency | 29GHz, 39GHz | | | +| BS antenna configuration | (Mg, Ng, M, N, P) = (1, 1, 8, 16, 2)
(dv, dh) = (0.5λ, 0.5λ)
GE,max = 8 dBi | (Mg, Ng, M, N, P) = (1, 1, 8, 16, 2)
(dv, dh) = (0.5λ, 0.5λ)
GE,max = 5 dBi | | +| UE antenna configuration | First priority:
PC1/PC2/PC5:
(Mg, Ng, M, N, P) = (1, 1, 4, 4, 2) (dv, dh) = (0.5λ, 0.5λ)
GE,max = 5 dBi
Second priority:
PC3:
(Mg, Ng, M, N, P) = (1, 1, 2, 2, 2) (dv, dh) = (0.5λ, 0.5λ)
GE,max = 5 dBi | | | +| System bandwidth | 200MHz | | | +| Target SNR at BS side | 28dB for 29GHz
30dB for 39GHz | | | +| UE max output power | PC1: 35 dBm/PC2: 23dBm/PC3: 23 dBm/PC5: 23 dBm | | | +| UE Min peak EIRP | n257 PC1:40.0 dBm/PC2:29 dBm/PC3:22.4 dBm/PC5: 30dBm | | | +| Power control | Power control parameters set to achieve the target SNR at BS side. | | | + +#### 5.2.1.2 Simulation results from Nokia + +[R4-2218327](#) + +The UE transmit power and UL SINR CDF at 29 GHz (n257) and 39 GHz (n260) using the agreed parameters in urban macro scenario (with the target SNR at BS side of 28 dB and 25 dB, respectively, at 29 GHz and 39 GHz) are shown in figures 5.2.1.2-1 and 5.2.1.2-2, respectively. + +![CDF plot of UE transmit power for Victim UE (PC1).](f519a5be118c846f631c992412353fb9_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot for UE transmit power (dBm) for a Victim UE with PC1. The x-axis ranges from -15 to 35 dBm with major ticks every 5 dBm. The y-axis represents the CDF (%) from 0 to 100 with major ticks every 10%. A single blue curve, labeled 'Victim UE' in the legend, starts at 0% CDF at -15 dBm and rises to nearly 100% at 35 dBm, showing a relatively smooth S-shape. + +CDF plot of UE transmit power for Victim UE (PC1). + +![CDF plot of UL SINR for Without Interfering UE (PC1).](6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg) + +This figure is a CDF plot of UL SINR of victim UE (dB) for the 'Without Interfering UE' scenario with PC1. The x-axis ranges from -40 to 30 dB with major ticks every 10 dB. The y-axis represents the CDF (%) from 0 to 100 with major ticks every 10%. A single blue curve, labeled 'Without Interfering UE' in the legend, remains near 0% CDF until approximately 10 dB, after which it rises sharply to reach 100% at about 28 dB. + +CDF plot of UL SINR for Without Interfering UE (PC1). + +**a) PC1 UE with 35 dBm maximum output power** + +![CDF plot of UE transmit power for Victim UE (PC2/5).](33228b4227fa57e1477b27b9e07483e6_img.jpg) + +This figure is a CDF plot for UE transmit power (dBm) for a Victim UE with PC2/5. The x-axis ranges from -15 to 25 dBm with major ticks every 5 dBm. The y-axis represents the CDF (%) from 0 to 100 with major ticks every 10%. A single blue curve, labeled 'Victim UE' in the legend, starts at 0% CDF at -15 dBm and rises to nearly 100% at 25 dBm, with a slight step-like feature around 22 dBm. + +CDF plot of UE transmit power for Victim UE (PC2/5). + +![CDF plot of UL SINR for Without Interfering UE (PC2/5).](7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg) + +This figure is a CDF plot of UL SINR of victim UE (dB) for the 'Without Interfering UE' scenario with PC2/5. The x-axis ranges from -50 to 30 dB with major ticks every 10 dB. The y-axis represents the CDF (%) from 0 to 100 with major ticks every 10%. A single blue curve, labeled 'Without Interfering UE' in the legend, remains near 0% CDF until approximately 10 dB, after which it rises sharply to reach 100% at about 28 dB. + +CDF plot of UL SINR for Without Interfering UE (PC2/5). + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-1. Urban macro simulation results at 29 GHz (n257)** + +![CDF plot of UE transmit power for Victim UE (PC1).](58de972a8c79c238b69cbeeafcc8d5fb_img.jpg) + +This figure is a CDF plot for UE transmit power (dBm) for a Victim UE with PC1. The x-axis ranges from -15 to 35 dBm with major ticks every 5 dBm. The y-axis represents the CDF (%) from 0 to 100 with major ticks every 10%. A single blue curve, labeled 'Victim UE' in the legend, starts at 0% CDF at -15 dBm and rises to nearly 100% at 35 dBm, showing a relatively smooth S-shape. + +CDF plot of UE transmit power for Victim UE (PC1). + +![CDF plot of UL SINR for Without Interfering UE (PC1).](71d82d389da5fe06a4aefb661ea17af9_img.jpg) + +This figure is a CDF plot of UL SINR of victim UE (dB) for the 'Without Interfering UE' scenario with PC1. The x-axis ranges from -40 to 30 dB with major ticks every 10 dB. The y-axis represents the CDF (%) from 0 to 100 with major ticks every 10%. A single blue curve, labeled 'Without Interfering UE' in the legend, remains near 0% CDF until approximately 10 dB, after which it rises sharply to reach 100% at about 28 dB. + +CDF plot of UL SINR for Without Interfering UE (PC1). + +**a) PC1 UE with 35 dBm maximum output power** + +![CDF plots for PC2/5 UE at 39 GHz (n260). Left plot: CDF (%) vs UE transmit power (dBm) for Victim UE. Right plot: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE.](ff2492be4fa814905acbad18f261b8a5_img.jpg) + +The figure contains two plots. The left plot shows the CDF (%) of UE transmit power (dBm) for a Victim UE, ranging from -15 to 25 dBm. The curve rises from 0% at -15 dBm to approximately 75% at 22 dBm, then jumps to 100% at 23 dBm. The right plot shows the CDF (%) of UL SINR of victim UE (dB) for a scenario 'Without Interfering UE', ranging from -50 to 30 dB. The curve remains below 10% until about 10 dB, then rises sharply to 100% at approximately 25 dB. + +CDF plots for PC2/5 UE at 39 GHz (n260). Left plot: CDF (%) vs UE transmit power (dBm) for Victim UE. Right plot: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE. + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-2. Urban macro simulation results at 39 GHz (n260)** + +It can be observed from figures 5.2.1.2-1 and 5.2.1.2-2 that at both 29 GHz (n257) and 39 GHz (n260): + +- The target SNR at BS side (of 28 dB and 25 dB, respectively, at 29 GHz and 39 GHz) can be achieved by ~70% of PC1 UE and ~60% of PC2/5 UE. +- ~15% of PC1 UE and ~25% of PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +The UE transmit power and UL SINR CDF at 29 GHz (n257) and 39 GHz (n260) using the agreed parameters in indoor scenario (with the target SNR at BS side of 28 dB and 25 dB, respectively, at 29 GHz and 39 GHz) are shown in figures 5.2.1.2-3 and 5.2.1.2-4, respectively. + +![CDF plots for PC1 UE at 29 GHz (n257). Left plot: CDF (%) vs UE transmit power (dBm) for Victim UE. Right plot: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE.](1640ec1dfae8bdfa5af950db7623febc_img.jpg) + +The figure contains two plots. The left plot shows the CDF (%) of UE transmit power (dBm) for a Victim UE, ranging from -40 to 20 dBm. The curve rises from 0% at -40 dBm to approximately 95% at 0 dBm, then reaches 100% at 10 dBm. The right plot shows the CDF (%) of UL SINR of victim UE (dB) for a scenario 'Without Interfering UE', ranging from 0 to 30 dB. The curve remains below 10% until about 15 dB, then rises sharply to 100% at approximately 28 dB. + +CDF plots for PC1 UE at 29 GHz (n257). Left plot: CDF (%) vs UE transmit power (dBm) for Victim UE. Right plot: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE. + +**a) PC1 UE with 35 dBm maximum output power** + +![CDF plots for PC2/5 UE at 29 GHz. Left: CDF (%) vs UE transmit power (dBm) for Victim UE. Right: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE.](42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg) + +The figure contains two plots for 29 GHz (n257). The left plot shows the Cumulative Distribution Function (CDF) of UE transmit power (dBm) for a Victim UE. The x-axis ranges from -40 to 20 dBm, and the y-axis (CDF (%)) ranges from 0 to 100. The curve starts at 0% at -40 dBm and reaches 100% at approximately 10 dBm. The right plot shows the CDF of UL SINR of victim UE (dB) for the case 'Without Interfering UE'. The x-axis ranges from 0 to 30 dB, and the y-axis (CDF (%)) ranges from 0 to 100. The curve starts at 0% at 0 dB and reaches 100% at approximately 28 dB. + +CDF plots for PC2/5 UE at 29 GHz. Left: CDF (%) vs UE transmit power (dBm) for Victim UE. Right: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE. + +b) PC2/5 UE with 23 dBm maximum output power + +**Figure 5.2.1.2-3. Indoor simulation results at 29 GHz (n257)** + +![CDF plots for PC1 UE at 39 GHz. Left: CDF (%) vs UE transmit power (dBm) for Victim UE. Right: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE.](dd330f8b8f6c16eae20c3a676b4eb804_img.jpg) + +The figure contains two plots for 39 GHz (n260). The left plot shows the CDF of UE transmit power (dBm) for a Victim UE. The x-axis ranges from -40 to 20 dBm, and the y-axis (CDF (%)) ranges from 0 to 100. The curve starts at 0% at -40 dBm and reaches 100% at approximately 10 dBm. The right plot shows the CDF of UL SINR of victim UE (dB) for the case 'Without Interfering UE'. The x-axis ranges from -5 to 25 dB, and the y-axis (CDF (%)) ranges from 0 to 100. The curve starts at 0% at -5 dB and reaches 100% at approximately 24 dB. + +CDF plots for PC1 UE at 39 GHz. Left: CDF (%) vs UE transmit power (dBm) for Victim UE. Right: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE. + +a) PC1 UE with 35 dBm maximum output power + +![CDF plots for PC2/5 UE at 39 GHz. Left: CDF (%) vs UE transmit power (dBm) for Victim UE. Right: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE.](624d9669faa18991d525fea5f0e03269_img.jpg) + +The figure contains two plots for 39 GHz (n260). The left plot shows the CDF of UE transmit power (dBm) for a Victim UE. The x-axis ranges from -40 to 20 dBm, and the y-axis (CDF (%)) ranges from 0 to 100. The curve starts at 0% at -40 dBm and reaches 100% at approximately 10 dBm. The right plot shows the CDF of UL SINR of victim UE (dB) for the case 'Without Interfering UE'. The x-axis ranges from -5 to 25 dB, and the y-axis (CDF (%)) ranges from 0 to 100. The curve starts at 0% at -5 dB and reaches 100% at approximately 24 dB. + +CDF plots for PC2/5 UE at 39 GHz. Left: CDF (%) vs UE transmit power (dBm) for Victim UE. Right: CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE. + +b) PC2/5 UE with 23 dBm maximum output power + +**Figure 5.2.1.2-4. Indoor simulation results at 39 GHz (n260)** + +It can be observed from figures 5.2.1.2-3 and 5.2.1.2-4 that at both 29 GHz (n257) and 39 GHz (n260): + +- The target SNR at BS side (of 28 dB and 25 dB, respectively, at 29 GHz and 39 GHz) can be achieved by ~70% of PC1 UE and PC2/5 UE. +- Almost none of PC1 UE and PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +##### R4-2300193 + +The UE transmit power and UL SINR CDF at 29 GHz (n257) and 39 GHz (n260) using the agreed parameters in urban macro scenario (with the target SNR at BS side of 27 dB at both 29 GHz and 39 GHz) are shown in figures 5.2.1.2-5 and 5.2.1.2-6, respectively. + +![CDF plots for PC1 UE transmit power and UL SINR at 29 GHz.](c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg) + +Two cumulative distribution function (CDF) plots for PC1 UE at 29 GHz. The left plot shows 'CDF (%)' on the y-axis (0-100) versus 'UE transmit power (dBm)' on the x-axis (-20 to 40). A blue curve labeled 'Victim UE' rises from 0% at -15 dBm to 100% at 35 dBm. The right plot shows 'CDF (%)' on the y-axis (0-100) versus 'UL SINR of victim UE (dB)' on the x-axis (-40 to 30). A blue curve labeled 'Without Interfering UE' remains near 0% until about 10 dB, then rises sharply to 100% at 28 dB. + +CDF plots for PC1 UE transmit power and UL SINR at 29 GHz. + +**a) PC1 UE with 35 dBm maximum output power** + +![CDF plots for PC2/5 UE transmit power and UL SINR at 29 GHz.](9d1abc573e35610946ece87a18cbe862_img.jpg) + +Two cumulative distribution function (CDF) plots for PC2/5 UE at 29 GHz. The left plot shows 'CDF (%)' on the y-axis (0-100) versus 'UE transmit power (dBm)' on the x-axis (-20 to 25). A blue curve labeled 'Victim UE' rises from 0% at -10 dBm to 100% at 23 dBm. The right plot shows 'CDF (%)' on the y-axis (0-100) versus 'UL SINR of victim UE (dB)' on the x-axis (-50 to 30). A blue curve labeled 'Without Interfering UE' remains near 0% until about 0 dB, then rises sharply to 100% at 27 dB. + +CDF plots for PC2/5 UE transmit power and UL SINR at 29 GHz. + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-5. Urban macro simulation results at 29 GHz (n257)** + +![CDF plot for PC1 UE transmit power](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg) + +This is a cumulative distribution function (CDF) plot for PC1 UE transmit power. The x-axis is labeled 'UE transmit power (dBm)' and ranges from -15 to 35. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100. A single blue curve, labeled 'Victim UE' in the legend, shows the cumulative distribution of transmit powers. The curve starts at 0% at -15 dBm, rises steeply between 0 and 20 dBm, and reaches approximately 85% at 35 dBm. + +CDF plot for PC1 UE transmit power + +![CDF plot for PC1 UE UL SINR](411fa16c3211377525ba37c57784fee0_img.jpg) + +This is a cumulative distribution function (CDF) plot for PC1 UE UL SINR. The x-axis is labeled 'UL SINR of victim UE (dB)' and ranges from -40 to 30. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100. A single blue curve, labeled 'Without Interfering UE' in the legend, shows the cumulative distribution of UL SINR values. The curve remains near 0% until about 10 dB, then rises sharply to reach 100% at approximately 28 dB. + +CDF plot for PC1 UE UL SINR + +**a) PC1 UE with 35 dBm maximum output power** + +![CDF plot for PC2/5 UE transmit power](fd188843e5acb8e0d76372860b5f5962_img.jpg) + +This is a cumulative distribution function (CDF) plot for PC2/5 UE transmit power. The x-axis is labeled 'UE transmit power (dBm)' and ranges from -15 to 25. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100. A single blue curve, labeled 'Victim UE' in the legend, shows the cumulative distribution of transmit powers. The curve starts at 0% at -15 dBm, rises between 0 and 20 dBm, and reaches about 75% at 23 dBm, with a vertical jump to 100% at 25 dBm. + +CDF plot for PC2/5 UE transmit power + +![CDF plot for PC2/5 UE UL SINR](89dcb02be40d2949bb93de93bbf213d5_img.jpg) + +This is a cumulative distribution function (CDF) plot for PC2/5 UE UL SINR. The x-axis is labeled 'UL SINR of victim UE (dB)' and ranges from -60 to 30. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100. A single blue curve, labeled 'Without Interfering UE' in the legend, shows the cumulative distribution of UL SINR values. The curve stays near 0% until about 0 dB, then rises to reach 100% at approximately 28 dB. + +CDF plot for PC2/5 UE UL SINR + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-6. Urban macro simulation results at 39 GHz (n260)** + +It can be observed from figures 5.2.1.2-5 and 5.2.1.2-6 that at both 29 GHz (n257) and 39 GHz (n260): + +- The target SNR at BS side of 27 dB can be achieved by ~70% of PC1 UE and ~60% of PC2/5 UE. +- Less than 15% of PC1 UE and less than 30% of PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +The UE transmit power and UL SINR CDF at 29 GHz (n257) and 39 GHz (n260) using the agreed parameters in indoor scenario (with the target SNR at BS side of 27 dB at both 29 GHz and 39 GHz) are shown in figures 5.2.1.2-7 and 5.2.1.2-8, respectively. + +![CDF plot of UE transmit power for PC1 UE with 35 dBm maximum output power.](0a8d173734e4e46c344178e8d21bcbc3_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UE transmit power for a PC1 UE with a maximum output power of 35 dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 20. The y-axis represents 'CDF (%)' ranging from 0 to 100. A single blue curve, labeled 'Victim UE' in the legend, starts at 0% CDF at -40 dBm and rises to 100% CDF at approximately 10 dBm. + +CDF plot of UE transmit power for PC1 UE with 35 dBm maximum output power. + +![CDF plot of UL SINR of victim UE without interfering UE for PC1 UE with 35 dBm maximum output power.](fe753d01ad5fe6cf150018c958173c6d_img.jpg) + +This figure is a CDF plot showing the distribution of UL SINR of the victim UE without interfering UE for a PC1 UE with a maximum output power of 35 dBm. The x-axis represents 'UL SINR of victim UE (dB)' ranging from 0 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. A single blue curve, labeled 'Without Interfering UE' in the legend, remains below 20% CDF until about 25 dB, then rises sharply to 100% CDF at approximately 27 dB. + +CDF plot of UL SINR of victim UE without interfering UE for PC1 UE with 35 dBm maximum output power. + +**a) PC1 UE with 35 dBm maximum output power** + +![CDF plot of UE transmit power for PC2/5 UE with 23 dBm maximum output power.](239211fa511b4ffa685b54b5132ec927_img.jpg) + +This figure is a CDF plot showing the distribution of UE transmit power for a PC2/5 UE with a maximum output power of 23 dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 20. The y-axis represents 'CDF (%)' ranging from 0 to 100. A single blue curve, labeled 'Victim UE' in the legend, starts at 0% CDF at -40 dBm and rises to 100% CDF at approximately 10 dBm. + +CDF plot of UE transmit power for PC2/5 UE with 23 dBm maximum output power. + +![CDF plot of UL SINR of victim UE without interfering UE for PC2/5 UE with 23 dBm maximum output power.](cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg) + +This figure is a CDF plot showing the distribution of UL SINR of the victim UE without interfering UE for a PC2/5 UE with a maximum output power of 23 dBm. The x-axis represents 'UL SINR of victim UE (dB)' ranging from 0 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. A single blue curve, labeled 'Without Interfering UE' in the legend, remains below 20% CDF until about 25 dB, then rises sharply to 100% CDF at approximately 27 dB. + +CDF plot of UL SINR of victim UE without interfering UE for PC2/5 UE with 23 dBm maximum output power. + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-7. Indoor simulation results at 29 GHz (n257)** + +![CDF plot of UE transmit power for PC1 UE with 35 dBm maximum output power.](ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg) + +This figure is a CDF plot showing the distribution of UE transmit power for a PC1 UE with a maximum output power of 35 dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. A single blue curve, labeled 'Victim UE' in the legend, starts at 0% CDF at -40 dBm and rises to 100% CDF at approximately 10 dBm. + +CDF plot of UE transmit power for PC1 UE with 35 dBm maximum output power. + +![CDF plot of UL SINR of victim UE without interfering UE for PC1 UE with 35 dBm maximum output power.](5c962f53272b4722e5d88f049e25084f_img.jpg) + +This figure is a CDF plot showing the distribution of UL SINR of the victim UE without interfering UE for a PC1 UE with a maximum output power of 35 dBm. The x-axis represents 'UL SINR of victim UE (dB)' ranging from -5 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. A single blue curve, labeled 'Without Interfering UE' in the legend, remains below 20% CDF until about 25 dB, then rises sharply to 100% CDF at approximately 27 dB. + +CDF plot of UL SINR of victim UE without interfering UE for PC1 UE with 35 dBm maximum output power. + +**a) PC1 UE with 35 dBm maximum output power** + +![Figure 5.2.1.2-8: Indoor simulation results at 39 GHz (n260). The figure contains two plots. The left plot shows the CDF (%) of UE transmit power (dBm) for a Victim UE, with the curve rising from 0% at -30 dBm to 100% at 10 dBm. The right plot shows the CDF (%) of UL SINR of victim UE (dB) for a scenario Without Interfering UE, with the curve rising sharply from 0% at 25 dB to 100% at 27 dB.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg) + +Figure 5.2.1.2-8: Indoor simulation results at 39 GHz (n260). The figure contains two plots. The left plot shows the CDF (%) of UE transmit power (dBm) for a Victim UE, with the curve rising from 0% at -30 dBm to 100% at 10 dBm. The right plot shows the CDF (%) of UL SINR of victim UE (dB) for a scenario Without Interfering UE, with the curve rising sharply from 0% at 25 dB to 100% at 27 dB. + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-8. Indoor simulation results at 39 GHz (n260)** + +Note that the results for PC1 and PC2/5 UE are alike in figures 5.2.1.2-7 and 5.2.1.2-8 as the higher PC1 UE transmit power is not required in indoor scenario. It can be observed from figures 5.2.1.2-7 and 5.2.1.2-8 that at both 29 GHz (n257) and 39 GHz (n260): + +- The target SNR at BS side of 27 dB can be achieved by ~70% of PC1 UE and PC2/5 UE. +- Almost none of PC1 UE and PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +R4-2307231 + +The UE transmit power and UL SINR CDF at 39 GHz (n260) using the agreed parameters in urban macro scenario (with the target SNR at BS side of 30 dB) are shown in figure 5.2.1.2-9. + +![Figure 5.2.1.2-9: Urban macro scenario results at 39 GHz (n260). The figure contains two plots. The left plot shows the CDF (%) of UE transmit power (dBm) for a Victim UE, with the curve rising from 0% at -10 dBm to 100% at 35 dBm. The right plot shows the CDF (%) of UL SINR of victim UE (dB) for a scenario Without Interfering UE, with the curve rising sharply from 0% at 25 dB to 100% at 30 dB.](02ab1c6abcb5a2d487a30d019a5454b6_img.jpg) + +Figure 5.2.1.2-9: Urban macro scenario results at 39 GHz (n260). The figure contains two plots. The left plot shows the CDF (%) of UE transmit power (dBm) for a Victim UE, with the curve rising from 0% at -10 dBm to 100% at 35 dBm. The right plot shows the CDF (%) of UL SINR of victim UE (dB) for a scenario Without Interfering UE, with the curve rising sharply from 0% at 25 dB to 100% at 30 dB. + +**a) PC1 UE with 35 dBm maximum output power** + +![Two line graphs showing CDF (%) vs UE transmit power (dBm) and UL SINR of victim UE (dB) for PC2/5 UE with 23 dBm maximum output power.](fed39b841ae2dce01088b84bfc1e2789_img.jpg) + +The figure contains two line graphs. The left graph plots the Cumulative Distribution Function (CDF) in percentage on the y-axis (0 to 100) against UE transmit power in dBm on the x-axis (-10 to 25). A single blue curve labeled 'Victim UE' shows a steady increase, reaching approximately 70% at 22.5 dBm and 100% at 25 dBm. The right graph plots the CDF in percentage on the y-axis (0 to 100) against the UL SINR of the victim UE in dB on the x-axis (-60 to 30). A single blue curve labeled 'Without Interfering UE' shows a sharp increase starting around 10 dB, reaching 100% at 30 dB. + +Two line graphs showing CDF (%) vs UE transmit power (dBm) and UL SINR of victim UE (dB) for PC2/5 UE with 23 dBm maximum output power. + +**b) PC2/5 UE with 23 dBm maximum output power** + +**Figure 5.2.1.2-9. Urban macro simulation results at 39 GHz (n260)** + +It can be observed from figure 5.2.1.2-9 that at 39 GHz (n260): + +- The target SNR at BS side of 30 dB can be achieved by ~60% of PC1 UE and ~50% of PC2/5 UE. +- ~18% of PC1 UE and ~32% of PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +The UE transmit power and UL SINR CDF at 39 GHz (n260) using the agreed parameters in indoor scenario (with the target SNR at BS side of 30 dB) are shown in figure 5.2.1.2-10. + +![Two line graphs showing CDF (%) vs UE transmit power (dBm) and UL SINR of victim UE (dB) for PC1 UE with 35 dBm maximum output power.](dbc1673750fd53d4203f4d93963fdab6_img.jpg) + +The figure contains two line graphs. The left graph plots the CDF in percentage on the y-axis (0 to 100) against UE transmit power in dBm on the x-axis (-30 to 30). A single blue curve labeled 'Victim UE' shows a steep increase between -10 dBm and 10 dBm, reaching nearly 100% by 15 dBm. The right graph plots the CDF in percentage on the y-axis (0 to 100) against the UL SINR of the victim UE in dB on the x-axis (-5 to 30). A single blue curve labeled 'Without Interfering UE' shows a sharp increase starting around 15 dB, reaching 100% at 30 dB. + +Two line graphs showing CDF (%) vs UE transmit power (dBm) and UL SINR of victim UE (dB) for PC1 UE with 35 dBm maximum output power. + +**a) PC1 UE with 35 dBm maximum output power** + +![Two CDF plots for indoor simulation at 39 GHz (n260). The left plot shows CDF (%) vs UE transmit power (dBm) for Victim UE, with a curve rising from 0% at -30 dBm to 100% at 10 dBm. The right plot shows CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE, with a curve rising from 0% at -5 dB to 100% at 30 dB.](1a6a826cc13d4e964b7bda69508d78e6_img.jpg) + +Two CDF plots for indoor simulation at 39 GHz (n260). The left plot shows CDF (%) vs UE transmit power (dBm) for Victim UE, with a curve rising from 0% at -30 dBm to 100% at 10 dBm. The right plot shows CDF (%) vs UL SINR of victim UE (dB) for Without Interfering UE, with a curve rising from 0% at -5 dB to 100% at 30 dB. + +b) PC2/5 UE with 23 dBm maximum output power + +Figure 5.2.1.2-10. Indoor simulation results at 39 GHz (n260) + +It can be observed from figure 5.2.1.2-10 that at 39 GHz (n260): + +- The target SNR at BS side of 30 dB can be achieved by ~60% of PC1 UE and PC2/5 UE. +- Almost none of PC1 UE and PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +Therefore, from the observations above, it can be concluded: + +- In all simulated scenarios, a significant percentage of PC1/PC2/PC5 UE can achieve the target SNR at BS side above which 256QAM provides throughput gain over 64QAM at both 29 GHz (n257) and 39 GHz (n260). + +#### 5.2.1.3 Simulation results from ZTE + +R4-2218595 + +In order to check whether the UE working on FR2 UL 256QAM can achieve target SNR at BS side we provide some system level simulation results with target SNR of 31dB and proposed Min peak EIRP. Figure 5.2.1.3-1~figure 5.2.1.3-4 show the CDF of SINR for PC1, PC2, PC3 and PC5 in band n257. + +![CDF of SINR for PC1 under Urban Macro @29GHz plot. The x-axis is SINR (0 to 30) and the y-axis is CDF (0 to 1). The curve shows that at SINR 30, the CDF is approximately 0.95. Two data points are highlighted: (30.9907, 0.95018) and (30.2136, 0.50263).](6682c4376efdda007851175f3014eca3_img.jpg) + +CDF of SINR for PC1 under Urban Macro @29GHz plot. The x-axis is SINR (0 to 30) and the y-axis is CDF (0 to 1). The curve shows that at SINR 30, the CDF is approximately 0.95. Two data points are highlighted: (30.9907, 0.95018) and (30.2136, 0.50263). + +Figure 5.2.1.3-1, CDF of SINR for PC1 under Urban Macro with Fc = 29GHz + +![CDF of SINR for PC2 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (24.6052, 0.49842) and (30.9927, 0.9507).](1c427123350e0e73e2a109b79069314b_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot for PC2 under an Urban Macro scenario at 29GHz. The x-axis represents the SINR (Signal-to-Interference-plus-Noise Ratio) ranging from 0 to 35, and the y-axis represents the CDF ranging from 0.1 to 1. The plot shows a blue curve representing the CDF. Two specific data points are highlighted with callout boxes: one at X = 24.6052, Y = 0.49842, and another at X = 30.9927, Y = 0.9507. + +| SINR (X) | CDF (Y) | +|----------|---------| +| 24.6052 | 0.49842 | +| 30.9927 | 0.9507 | + +CDF of SINR for PC2 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (24.6052, 0.49842) and (30.9927, 0.9507). + +Figure 5.2.1.3-2, CDF of SINR for PC2 under Urban Macro with Fc = 29GHz + +![CDF of SINR for PC3 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (18.4769, 0.50267) and (30.7884, 0.95014).](93587f920736a2fdcefeba94b29f302a_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot for PC3 under an Urban Macro scenario at 29GHz. The x-axis represents the SINR (Signal-to-Interference-plus-Noise Ratio) ranging from 0 to 30, and the y-axis represents the CDF ranging from 0.1 to 1. The plot shows a blue curve representing the CDF. Two specific data points are highlighted with callout boxes: one at X = 18.4769, Y = 0.50267, and another at X = 30.7884, Y = 0.95014. + +| SINR (X) | CDF (Y) | +|----------|---------| +| 18.4769 | 0.50267 | +| 30.7884 | 0.95014 | + +CDF of SINR for PC3 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (18.4769, 0.50267) and (30.7884, 0.95014). + +Figure 5.2.1.3-3, CDF of SINR for PC3 under Urban Macro with Fc = 29GHz + +![CDF of SINR for PC5 under Urban Macro @29GHz](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg) + +A cumulative distribution function (CDF) plot for PC5 under Urban Macro conditions at 29GHz. The x-axis is labeled 'SINR' and ranges from 0 to 35. The y-axis is labeled 'CDF' and ranges from 0.1 to 1. The plot shows a blue curve representing the CDF. Two data points are highlighted with callout boxes: one at (30.9925, 0.95018) and another at (25.5704, 0.5014). + +| SINR | CDF | +|---------|---------| +| 25.5704 | 0.5014 | +| 30.9925 | 0.95018 | + +CDF of SINR for PC5 under Urban Macro @29GHz + +Figure 5.2.1.3-4, CDF of SINR for PC5 under Urban Macro with $F_c = 29\text{GHz}$ + +From figure 5.2.1.3-1~figure 5.2.1.3-4 we can find that 5% UE can achieve above 30dB SINR which show that PC1, PC2 and PC5 @29GHz are feasible for UL 256QAM. If the operating SNR is smaller than 30dB, then the percentage of UE meet the target SNR will increase, for example, ~10% UE can achieve above 28dB SINR even for PC3. + +**Observation 3: PC1, PC2, PC3 and PC5 are feasible for UL 256QAM for 29GHz if the operating SNR is not higher than 28dB.** + +R4-2301235 + +In last meeting, we provided SLS results for UL 256QAM for PC1/2/3/5 UEs of 29GHz in R4-2218595, in terms of the simulations, which are shown below: + +![CDF of SINR for PC2 under Urban Macro @29GHz](9e424b8261c786a419e456b01fae29ff_img.jpg) + +A cumulative distribution function (CDF) plot for PC2 under Urban Macro conditions at 29GHz. The x-axis is labeled 'SINR' and ranges from 0 to 35. The y-axis is labeled 'CDF' and ranges from 0.1 to 1. The plot shows a blue curve representing the CDF. Two data points are highlighted with callout boxes: one at (24.6052, 0.49842) and another at (30.9927, 0.9507). + +| SINR | CDF | +|---------|---------| +| 24.6052 | 0.49842 | +| 30.9927 | 0.9507 | + +CDF of SINR for PC2 under Urban Macro @29GHz + +Figure 5.2.1.3-5, CDF of SINR for PC2 under Urban Macro with $F_c = 29\text{GHz}$ + +![CDF of SINR for PC3 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (18.4769, 0.50267) and (30.7884, 0.95014).](ebce355620876e10f907f8b71926c112_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot for PC3 under an Urban Macro scenario at 29GHz. The x-axis represents the SINR (ranging from 0 to 30) and the y-axis represents the CDF (ranging from 0.1 to 1.0). The plot shows a blue curve representing the CDF. Two specific data points are highlighted with callout boxes: one at X = 18.4769, Y = 0.50267, and another at X = 30.7884, Y = 0.95014. + +| SINR (X) | CDF (Y) | +|----------|---------| +| 18.4769 | 0.50267 | +| 30.7884 | 0.95014 | + +CDF of SINR for PC3 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (18.4769, 0.50267) and (30.7884, 0.95014). + +Figure 5.2.1.3-6, CDF of SINR for PC3 under Urban Macro with Fc = 29GHz + +![CDF of SINR for PC5 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (25.5704, 0.5014) and (30.9925, 0.95018).](723827e0738d2743c3b3423760a5c48e_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot for PC5 under an Urban Macro scenario at 29GHz. The x-axis represents the SINR (ranging from 0 to 35) and the y-axis represents the CDF (ranging from 0.1 to 1.0). The plot shows a blue curve representing the CDF. Two specific data points are highlighted with callout boxes: one at X = 25.5704, Y = 0.5014, and another at X = 30.9925, Y = 0.95018. + +| SINR (X) | CDF (Y) | +|----------|---------| +| 25.5704 | 0.5014 | +| 30.9925 | 0.95018 | + +CDF of SINR for PC5 under Urban Macro @29GHz plot showing SINR vs CDF with data points at (25.5704, 0.5014) and (30.9925, 0.95018). + +Figure 5.2.1.3-7, CDF of SINR for PC5 under Urban Macro with Fc = 29GHz + +From figure 5.2.1.3-5, 5.2.1.3-6 and 5.2.1.3-7, we can find that 5% UE can achieve above 30dB SINR which show that PC2 and PC5 @29GHz are feasible for UL 256QAM. If the operating SNR is smaller than 30dB, then the percentage of UE meet the target SNR will increase. Even ~10% UE can achieve above 28dB SINR even for PC3. + +#### 5.2.1.4 Simulation results from vivo + +[R4-2218869](#) + +The SINR distribution for Indoor and Uma are shown in Figure 5.2.1.4-1: + +![Two CDF plots showing SINR distribution for 29GHz Indoor and 29GHz Uma scenarios. The x-axis is SINR and the y-axis is CDF. Three curves are shown: PC1 (blue), PC2/PC5 (orange), and PC3 (yellow). In the Indoor plot, PC3 reaches a CDF of 1 at approximately 20 dB, while PC1 reaches it at approximately 35 dB. In the Uma plot, all three curves reach a CDF of 1 at approximately 35 dB.](7f687094e6abe34a9cf491942b296d9a_img.jpg) + +Two CDF plots showing SINR distribution for 29GHz Indoor and 29GHz Uma scenarios. The x-axis is SINR and the y-axis is CDF. Three curves are shown: PC1 (blue), PC2/PC5 (orange), and PC3 (yellow). In the Indoor plot, PC3 reaches a CDF of 1 at approximately 20 dB, while PC1 reaches it at approximately 35 dB. In the Uma plot, all three curves reach a CDF of 1 at approximately 35 dB. + +Figure 5.2.1.4-1 SINR distribution + +Except for PC1, The SINR of UE is hard to larger than 25 dB at the BS side. + +##### Observation 1: + +- For PC1, 20% of UE's SINR can be larger than 25 dB. +- For PC2/PC3/PC5, <5% UE's SINR can larger than 25 dB. + +We further counted the percentage of UEs that had used 256QAM in the simulation and the throughput performance gain. The throughput gain is derived from comparing whether the 256QAM is allowed. The results are shown in below: + +![Two bar charts comparing PC1, PC2/PC5, and PC3 across Indoor and Uma scenarios. The left chart shows the 'Proportion of UEs using 256QAM' and the right chart shows the 'Cell average throughput gain'.](fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg) + +| Scenario | Power Class | Proportion of UEs using 256QAM (%) | Cell average throughput gain (%) | +|----------|-------------|------------------------------------|----------------------------------| +| Indoor | PC1 | ~70% | ~10% | +| | PC2/PC5 | 12.00% | -1.00% | +| | PC3 | 2.50% | -4.30% | +| Uma | PC1 | ~40% | ~2.40% | +| | PC2/PC5 | 17.90% | 1.00% | +| | PC3 | 16.00% | 0.80% | + +Two bar charts comparing PC1, PC2/PC5, and PC3 across Indoor and Uma scenarios. The left chart shows the 'Proportion of UEs using 256QAM' and the right chart shows the 'Cell average throughput gain'. + +Figure 5.2.1.4-2 proportion and performance gain for 256 QAM + +For the indoor scenario, PC1 UE can have obvious performance gain, and about 70% UE is once scheduled with 256QAM during the simulation time, but for other power classes, the throughput performance even become worse, this is because the SINR for these UE cannot support such high MCS and the BLER is bad. For the Uma scenario, even though there are many UEs scheduled with 256 QAM, the performance gain is tiny. + +##### Observation 2: + +- For the indoor scenario, only PC1 shows obvious throughput gain, and about 69.3%UEs are scheduled with 256 QAM. +- For the Uma scenario, the performance gain of all PC UEs is tiny. + +##### R4-2301569 + +The simulation assumption for SLS was revised to add minimum EIRP and power control formula, and our simulation results based on such new assumptions are shown in Figure 5.2.1.4-3. The operating SNR is used as the target SNR at the BS side, and the minimum EIRP is used to calculate the conducted power level which means deducting antenna gain (including array gain). + +![Figure 5.2.1.4-3: SINR distribution based on SLS. The figure contains three subplots showing the Cumulative Distribution Function (CDF) of SINR for Indoor (blue line) and Uma (orange line) scenarios. The left plot is for PC2/PC5 SINR in 29 GHz, the middle plot is for PC1 SINR in 39 GHz, and the right plot is for PC2/PC5 SINR in 39 GHz. In all cases, the Indoor scenario shows a higher SINR distribution than the Uma scenario.](65f66758012e229247953202e8adf35d_img.jpg) + +Figure 5.2.1.4-3: SINR distribution based on SLS. The figure contains three subplots showing the Cumulative Distribution Function (CDF) of SINR for Indoor (blue line) and Uma (orange line) scenarios. The left plot is for PC2/PC5 SINR in 29 GHz, the middle plot is for PC1 SINR in 39 GHz, and the right plot is for PC2/PC5 SINR in 39 GHz. In all cases, the Indoor scenario shows a higher SINR distribution than the Uma scenario. + +**Figure 5.2.1.4-3 SINR distribution based on SLS** + +For the Indoor scenario, all cases above have more than 10% UE can achieve operating SNR, but for the Uma scenario, the ratio is much lower, especially in PC2/PC5 in the 39GHz case, only about 2% UE can achieve operating SNR. + +##### **Observation 1:** + +- In 29GHz, 14% in Indoor and 5% in Uma PC2/PC5 UE can archive 28 dB SNR. +- In 39GHz, 12% in Indoor and 10% in Uma PC1 UE can archive 30 dB SNR; 10% in Indoor and 2% in Uma PC2/PC5 UE can archive 30 dB SNR. + +#### 5.2.1.5 Simulation results from Ericsson + +##### R4-2220036 + +On Figure 5.2.1.5-1 we show the results of system-level simulations for 29 GHz carrier frequency and FTP traffic model of both 10% and 30%. + +![Figure 5.2.1.5-1: System-level simulation results on 256QAM feasibility for PC1 UE in FR2-1 for 29 GHz carrier frequency. The graph shows the Cumulative Distribution Function (CDF) of SINR [dB] for UL. The x-axis ranges from -10 to 40 dB, and the y-axis ranges from 0 to 100%. Two curves are shown: 10% load (solid blue line) and 30% load (dashed blue line). The 30% load curve is above the 10% load curve, indicating better performance. At 30 dB SINR, approximately 35% of UEs for 10% load and 30% of UEs for 30% load achieve the target SNR.](45329c7d9aa2bd1290af5b2027f08d7e_img.jpg) + +UL + +CDF [%] + +SINR [dB] + +10% load + +30% load + +Figure 5.2.1.5-1: System-level simulation results on 256QAM feasibility for PC1 UE in FR2-1 for 29 GHz carrier frequency. The graph shows the Cumulative Distribution Function (CDF) of SINR [dB] for UL. The x-axis ranges from -10 to 40 dB, and the y-axis ranges from 0 to 100%. Two curves are shown: 10% load (solid blue line) and 30% load (dashed blue line). The 30% load curve is above the 10% load curve, indicating better performance. At 30 dB SINR, approximately 35% of UEs for 10% load and 30% of UEs for 30% load achieve the target SNR. + +**Figure 5.2.1.5-1: System-level simulation results on 256QAM feasibility for PC1 UE in FR2-1 for 29 GHz carrier frequency** + +Note that in the simulations results, no sophisticated model was used for the misalignment between BS and UE beam directions. So, in the simulations the ideal beam management was assumed, and the impairment offset of 10 dB was added in the last stage. + +By looking at the results, we can see that around 30% of UEs can achieve the operating SNR of 30 dB for FTP with 30% load and around 35% of UEs can achieve the operating SNR of 30 dB for FTP with 10% load, which means that 256 QAM for PC1 UEs in FR2-1 and 29 GHz carrier frequency is feasible. + +R4-2302734 + +## 2.1 29GHz carrier frequency + +### 2.1.1 Indoor scenario for PC2/PC5 + +![Figure 5.2.1.5-2: System-level simulation results on 256QAM feasibility for PC2/PC5 UE in FR2-1 for 29 GHz carrier frequency. The graph shows the Cumulative Distribution Function (CDF) of SINR [dB] for UL SINR for PC2/5 on 29GHz (Indoor). The x-axis ranges from 5 to 25 dB, and the y-axis ranges from 0 to 100%. Two curves are shown: 10% load (solid blue line) and 30% load (dashed blue line). The 30% load curve is above the 10% load curve. At 28 dB SINR, approximately 60% of UEs for 10% load and 15% of UEs for 30% load achieve the target SNR.](87dfa94e14e0a4089d677c36b602c793_img.jpg) + +UL SINR for PC2/5 on 29GHz (Indoor) + +CDF [%] + +SINR [dB] + +10% load + +30% load + +Figure 5.2.1.5-2: System-level simulation results on 256QAM feasibility for PC2/PC5 UE in FR2-1 for 29 GHz carrier frequency. The graph shows the Cumulative Distribution Function (CDF) of SINR [dB] for UL SINR for PC2/5 on 29GHz (Indoor). The x-axis ranges from 5 to 25 dB, and the y-axis ranges from 0 to 100%. Two curves are shown: 10% load (solid blue line) and 30% load (dashed blue line). The 30% load curve is above the 10% load curve. At 28 dB SINR, approximately 60% of UEs for 10% load and 15% of UEs for 30% load achieve the target SNR. + +Observation 1: For 29GHz carrier frequency, indoor scenario and PC2/PC5, around 60% of users with FTP 10% load and 15% of users with FTP 30% load can reach the operating SNR of 28dB. + +### 2.1.2 UMa scenario for PC2/PC5 + +![CDF plot of UL SINR for PC2/5 on 29GHz (UMa) for 10% and 30% load.](a1545557e366b6302109d13360b199c3_img.jpg) + +UL SINR for PC2/5 on 29GHz (UMa) + +This figure is a Cumulative Distribution Function (CDF) plot showing the UL SINR for PC2/5 on 29GHz in a UMa scenario. The x-axis represents the SINR [dB] from -20 to 25, and the y-axis represents the CDF [%] from 0 to 100. Two curves are plotted: a solid blue line for 10% load and a dashed blue line for 30% load. Both curves show a rapid increase in CDF starting around -5 dB, reaching approximately 50% at 15 dB, and approaching 100% at 25 dB. The 30% load curve is slightly higher than the 10% load curve in the middle range. + +| SINR [dB] | CDF [%] (10% load) | CDF [%] (30% load) | +|-----------|--------------------|--------------------| +| -20 | 0 | 0 | +| -15 | 0 | 0 | +| -10 | 0 | 0 | +| -5 | 2 | 2 | +| 0 | 10 | 10 | +| 5 | 20 | 22 | +| 10 | 35 | 38 | +| 15 | 50 | 52 | +| 20 | 70 | 72 | +| 25 | 95 | 98 | + +CDF plot of UL SINR for PC2/5 on 29GHz (UMa) for 10% and 30% load. + +Observation 2: For 29GHz carrier frequency, UMa scenario and PC2/PC5, around 30% of users with FTP 10% load and 28% of users with FTP 30% load can reach the operating SNR of 28dB. + +### 2.2 39GHz carrier frequency + +#### 2.2.1 Indoor scenario for PC2/PC5 + +![CDF plot of UL SINR for PC2/5 on 39GHz (Indoor) for 10% and 30% load.](cd31d0e7e4b524e074808154dd279205_img.jpg) + +UL SINR for PC2/5 on 39GHz (Indoor) + +This figure is a Cumulative Distribution Function (CDF) plot showing the UL SINR for PC2/5 on 39GHz in an indoor scenario. The x-axis represents the SINR [dB] from 5 to 30, and the y-axis represents the CDF [%] from 0 to 100. Two curves are plotted: a solid blue line for 10% load and a dashed blue line for 30% load. The 30% load curve shows a much steeper increase, reaching about 50% CDF at 25 dB and nearly 100% at 30 dB. The 10% load curve increases more gradually, reaching about 10% at 25 dB and about 50% at 30 dB. + +| SINR [dB] | CDF [%] (10% load) | CDF [%] (30% load) | +|-----------|--------------------|--------------------| +| 5 | 0 | 0 | +| 10 | 0 | 1 | +| 15 | 1 | 5 | +| 20 | 2 | 20 | +| 25 | 10 | 50 | +| 30 | 50 | 95 | + +CDF plot of UL SINR for PC2/5 on 39GHz (Indoor) for 10% and 30% load. + +Observation 3: For 39GHz carrier frequency, indoor scenario and PC2/PC5, around 50% of users with FTP 10% load and 12% of users with FTP 30% load can reach the operating SNR of 30dB. + +### 2.2.2 UMa scenario for PC2/PC5 + +![UL SINR for PC2/5 on 39GHz (UMa) plot showing CDF [%] vs SINR [dB] for 10% and 30% load.](c17eaf807acd5faec68da19dd16929be_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot titled "UL SINR for PC2/5 on 39GHz (UMa)". The x-axis represents the SINR [dB] ranging from -30 to 30, and the y-axis represents the CDF [%] ranging from 0 to 100. Two curves are plotted: a solid blue line for "10% load" and a dashed blue line for "30% load". Both curves show a sharp increase in CDF starting around 0 dB SINR. At 30 dB SINR, the 10% load curve reaches approximately 90% CDF, while the 30% load curve reaches approximately 85% CDF. + +| SINR [dB] | 10% load CDF [%] | 30% load CDF [%] | +|-----------|------------------|------------------| +| -30 | 0 | 0 | +| -20 | 1 | 1 | +| -10 | 3 | 3 | +| 0 | 10 | 8 | +| 10 | 35 | 25 | +| 20 | 60 | 55 | +| 30 | 90 | 85 | + +UL SINR for PC2/5 on 39GHz (UMa) plot showing CDF [%] vs SINR [dB] for 10% and 30% load. + +Observation 4: For 39GHz carrier frequency, UMa scenario and PC2/PC5, around 17% of users with FTP 10% load and 15% of users with FTP 30% load can reach the operating SNR of 30dB. + +### 2.2.3 Indoor scenario for PC1 + +![UL SINR for PC1 on 39GHz (Indoor) plot showing CDF [%] vs SINR [dB] for 10% and 30% load.](62a4c9055642dbb00663e633332f04d3_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot titled "UL SINR for PC1 on 39GHz (Indoor)". The x-axis represents the SINR [dB] ranging from 5 to 30, and the y-axis represents the CDF [%] ranging from 0 to 100. Two curves are plotted: a solid blue line for "10% load" and a dashed blue line for "30% load". The 30% load curve shows a more gradual increase in CDF compared to the 10% load curve. At 30 dB SINR, the 30% load curve reaches approximately 95% CDF, while the 10% load curve reaches approximately 80% CDF. + +| SINR [dB] | 10% load CDF [%] | 30% load CDF [%] | +|-----------|------------------|------------------| +| 5 | 0 | 0 | +| 10 | 0 | 1 | +| 15 | 0 | 5 | +| 20 | 1 | 20 | +| 25 | 5 | 50 | +| 30 | 80 | 95 | + +UL SINR for PC1 on 39GHz (Indoor) plot showing CDF [%] vs SINR [dB] for 10% and 30% load. + +Observation 5: For 39GHz carrier frequency, indoor scenario and PC1, around 55% of users with FTP 10% load and 12% of users with FTP 30% load can reach the operating SNR of 30dB. + +#### 2.2.4 UMa scenario for PC1 + +![UL SINR for PC1 on 39GHz (UMa) plot showing CDF [%] vs SINR [dB] for 10% and 30% load.](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot titled "UL SINR for PC1 on 39GHz (UMa)". The x-axis represents the SINR in dB, ranging from -15 to 30. The y-axis represents the CDF in percentage, ranging from 0 to 100. Two curves are plotted: a solid blue line for 10% load and a dashed blue line for 30% load. Both curves show a sharp increase in CDF as SINR approaches 30 dB, with the 30% load curve reaching higher CDF values at lower SINR levels compared to the 10% load curve. + +| SINR [dB] | CDF [%] (10% load) | CDF [%] (30% load) | +|-----------|--------------------|--------------------| +| -10 | 0 | 0 | +| 0 | 10 | 5 | +| 10 | 15 | 12 | +| 20 | 30 | 35 | +| 25 | 40 | 45 | +| 28 | 50 | 55 | +| 30 | 100 | 100 | + +UL SINR for PC1 on 39GHz (UMa) plot showing CDF [%] vs SINR [dB] for 10% and 30% load. + +Observation 6: For 39GHz carrier frequency, UMa scenario and PC1, around 50% of users with FTP 10% load and 38% of users with FTP 30% load can reach the operating SNR of 30dB. + +#### 5.2.1.6 Simulation results from Xiaomi + +R4-2301620 + +In last meeting, it is verified that the UL 256QAM for PC1 UE of 29GHz is feasible based on system simulation, but whether UL 256QAM for PC2/5 UE of 29GHz and PC1/2/5 UE of 39GHz can achieve target SNR at BS side need further confirm by system simulation. Hence, we provide the system level simulation results with the agreed target SNR of 28dB and 30dB for PC1/2/5 UE of 29GHz and 39GHz. + +The UE transmit power and UL SINR CDF at 29 GHz and 39 GHz in urban macro scenario are shown in figure 5.2.1.6-1 and figure 5.2.1.6-2, respectively. + +![Two side-by-side plots: UE TX Power CDF for PC1 under UMa @29GHz and UL SINR CDF for PC1 under UMa @29GHz.](155bd5ec49c26532be9f04b06904002e_img.jpg) + +This figure contains two side-by-side plots. The left plot is titled "UE TX Power CDF for PC1 under UMa @29GHz" and shows the CDF of UE transmit power in dBm, ranging from -10 to 30. The right plot is titled "UL SINR CDF for PC1 under UMa @29GHz" and shows the CDF of UL SINR in dB, ranging from -40 to 30. Both plots feature a single red curve labeled "PC1". + +| UE TX Power (dBm) | CDF (%) | +|-------------------|---------| +| -10 | 0 | +| 0 | 10 | +| 10 | 40 | +| 20 | 70 | +| 30 | 90 | +| 35 | 100 | + +| UL SINR (dB) | CDF (%) | +|--------------|---------| +| -40 | 0 | +| -30 | 0 | +| -20 | 0 | +| -10 | 0 | +| 0 | 5 | +| 10 | 10 | +| 20 | 20 | +| 25 | 50 | +| 28 | 100 | +| 30 | 100 | + +Two side-by-side plots: UE TX Power CDF for PC1 under UMa @29GHz and UL SINR CDF for PC1 under UMa @29GHz. + +PC1 UE with 35dBm maximum output power (n257) + +![Two CDF plots for 29 GHz simulation results. The left plot shows 'UE TX Power CDF for PC2/PC5 under UMa @29GHz' with a red curve for PC2/PC5. The x-axis is 'UE TX Power (dBm)' from -20 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. The right plot shows 'UL SINR CDF for PC2/PC5 under UMa @29GHz' with a blue curve for PC2/PC5. The x-axis is 'UL SINR (dB)' from -60 to 20, and the y-axis is 'CDF' from 0.0 to 1.0.](85b10db535b22e64c7d37f362705ddbf_img.jpg) + +Two CDF plots for 29 GHz simulation results. The left plot shows 'UE TX Power CDF for PC2/PC5 under UMa @29GHz' with a red curve for PC2/PC5. The x-axis is 'UE TX Power (dBm)' from -20 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. The right plot shows 'UL SINR CDF for PC2/PC5 under UMa @29GHz' with a blue curve for PC2/PC5. The x-axis is 'UL SINR (dB)' from -60 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. + +**b. PC2/5 UE with 23dBm maximum output power (n257)** + +**Figure 5.2.1.6-1 Urban macro simulation results at 29 GHz** + +![Two CDF plots for 39 GHz simulation results for PC1. The left plot shows 'UE TX Power CDF for PC1 under UMa @39GHz' with a red curve for PC1. The x-axis is 'UE TX Power (dBm)' from -10 to 30, and the y-axis is 'CDF' from 0.0 to 1.0. The right plot shows 'UL SINR CDF for PC1 under UMa @39GHz' with a blue curve for PC1. The x-axis is 'UL SINR (dB)' from -40 to 20, and the y-axis is 'CDF' from 0.0 to 1.0.](114a0f7c7ac69ab82f03d68650cf8e88_img.jpg) + +Two CDF plots for 39 GHz simulation results for PC1. The left plot shows 'UE TX Power CDF for PC1 under UMa @39GHz' with a red curve for PC1. The x-axis is 'UE TX Power (dBm)' from -10 to 30, and the y-axis is 'CDF' from 0.0 to 1.0. The right plot shows 'UL SINR CDF for PC1 under UMa @39GHz' with a blue curve for PC1. The x-axis is 'UL SINR (dB)' from -40 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. + +**c. PC1 UE with 35 dBm maximum output power (n260)** + +![Two CDF plots for 39 GHz simulation results for PC2/PC5. The left plot shows 'UE TX Power CDF for PC2/PC5 under UMa @39GHz' with a red curve for PC2/PC5. The x-axis is 'UE TX Power (dBm)' from -15 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. The right plot shows 'UL SINR CDF for PC2/PC5 under UMa @39GHz' with a blue curve for PC2/PC5. The x-axis is 'UL SINR (dB)' from -60 to 20, and the y-axis is 'CDF' from 0.0 to 1.0.](9c8070d46f1d2480a875239e792f1ef6_img.jpg) + +Two CDF plots for 39 GHz simulation results for PC2/PC5. The left plot shows 'UE TX Power CDF for PC2/PC5 under UMa @39GHz' with a red curve for PC2/PC5. The x-axis is 'UE TX Power (dBm)' from -15 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. The right plot shows 'UL SINR CDF for PC2/PC5 under UMa @39GHz' with a blue curve for PC2/PC5. The x-axis is 'UL SINR (dB)' from -60 to 20, and the y-axis is 'CDF' from 0.0 to 1.0. + +**d. PC2/5 UE with 23dBm maximum output power (n259)** + +**Figure 5.2.1.6-2 Urban macro simulation results at 39 GHz** + +The UE transmit power and UL SINR CDF at 29 GHz and 39 GHz in indoor hotspot scenario are shown in figures 5.2.1.6-3 and 5.2.1.6-4, respectively. + +![UE TX Power CDF for PC1 under InH @29GHz. The plot shows a red curve for PC1, starting at approximately (-12, 0.58) and reaching a CDF of 1.0 at 20 dBm.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +UE TX Power CDF for PC1 under InH @29GHz + +CDF + +UE TX Power (dBm) + +PC1 + +UE TX Power CDF for PC1 under InH @29GHz. The plot shows a red curve for PC1, starting at approximately (-12, 0.58) and reaching a CDF of 1.0 at 20 dBm. + +![UL SINR CDF for PC1 under InH @29GHz. The plot shows a blue curve for PC1, starting at (0, 0.0) and reaching a CDF of 1.0 at approximately 45 dB.](23816aaa8e6defc50fc888da62fd59cc_img.jpg) + +UL SINR CDF for PC1 under InH @29GHz + +CDF + +UL SINR (dB) + +PC1 + +UL SINR CDF for PC1 under InH @29GHz. The plot shows a blue curve for PC1, starting at (0, 0.0) and reaching a CDF of 1.0 at approximately 45 dB. + +**e. PC1 UE with 35 dBm maximum output power (n257)** + +![UE TX Power CDF for PC2/PC5 under InH @29GHz. The plot shows a red curve for PC2/PC5, starting at (-30, 0.0) and reaching a CDF of 1.0 at 20 dBm.](1033ab90cd19fd4c5901966aeec07a86_img.jpg) + +UE TX Power CDF for PC2/PC5 under InH @29GHz + +CDF + +UE TX Power (dBm) + +PC2/PC5 + +UE TX Power CDF for PC2/PC5 under InH @29GHz. The plot shows a red curve for PC2/PC5, starting at (-30, 0.0) and reaching a CDF of 1.0 at 20 dBm. + +![UL SINR CDF for PC2/PC5 under InH @29GHz. The plot shows a blue curve for PC2/PC5, starting at (0, 0.0) and reaching a CDF of 1.0 at approximately 28 dB.](51536f203c07ce20ce119e7e09b11cb6_img.jpg) + +UL SINR CDF for PC2/PC5 under InH @29GHz + +CDF + +UL SINR (dB) + +PC2/PC5 + +UL SINR CDF for PC2/PC5 under InH @29GHz. The plot shows a blue curve for PC2/PC5, starting at (0, 0.0) and reaching a CDF of 1.0 at approximately 28 dB. + +**f. PC2/5 UE with 23dBm maximum output power (n257)** + +**Figure 5.2.1.6-3 Indoor hotspot simulation results at 29 GHz** + +![UE TX Power CDF for PC1 under InH @39GHz. The plot shows a red curve for PC1, starting at (-12, 0.28) and reaching a CDF of 1.0 at 25 dBm.](f3c5e85b70f94b9c3c521f594d69539f_img.jpg) + +UE TX Power CDF for PC1 under InH @39GHz + +CDF + +UE TX Power (dBm) + +PC1 + +UE TX Power CDF for PC1 under InH @39GHz. The plot shows a red curve for PC1, starting at (-12, 0.28) and reaching a CDF of 1.0 at 25 dBm. + +![UL SINR CDF for PC1 under InH @39GHz. The plot shows a blue curve for PC1, starting at (0, 0.0) and reaching a CDF of 1.0 at approximately 45 dB.](3c2744b5b1ad3baef441546b0bf157ca_img.jpg) + +UL SINR CDF for PC1 under InH @39GHz + +CDF + +UL SINR (dB) + +PC1 + +UL SINR CDF for PC1 under InH @39GHz. The plot shows a blue curve for PC1, starting at (0, 0.0) and reaching a CDF of 1.0 at approximately 45 dB. + +**g. PC1 UE with 35 dBm maximum output power (n260)** + +![Figure 5.2.1.6-4: Indoor hotspot simulation results at 39 GHz. The figure contains two plots. The left plot is titled 'UE TX Power CDF for PC2/PC5 under InH @39GHz' and shows the cumulative distribution function (CDF) of UE transmit power (dBm) for PC2/PC5. The x-axis ranges from -20 to 20 dBm, and the y-axis (CDF) ranges from 0.0 to 1.0. The curve for PC2/PC5 (red line) starts at 0.0 at -20 dBm and reaches 1.0 at approximately 10 dBm. The right plot is titled 'UL SINR CDF for PC2/PC5 under InH @39GHz' and shows the CDF of UL SINR (dB) for PC2/PC5. The x-axis ranges from 0 to 30 dB, and the y-axis (CDF) ranges from 0.0 to 1.0. The curve for PC2/PC5 (blue line) starts at 0.0 at 0 dB and reaches 1.0 at approximately 30 dB.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +Figure 5.2.1.6-4: Indoor hotspot simulation results at 39 GHz. The figure contains two plots. The left plot is titled 'UE TX Power CDF for PC2/PC5 under InH @39GHz' and shows the cumulative distribution function (CDF) of UE transmit power (dBm) for PC2/PC5. The x-axis ranges from -20 to 20 dBm, and the y-axis (CDF) ranges from 0.0 to 1.0. The curve for PC2/PC5 (red line) starts at 0.0 at -20 dBm and reaches 1.0 at approximately 10 dBm. The right plot is titled 'UL SINR CDF for PC2/PC5 under InH @39GHz' and shows the CDF of UL SINR (dB) for PC2/PC5. The x-axis ranges from 0 to 30 dB, and the y-axis (CDF) ranges from 0.0 to 1.0. The curve for PC2/PC5 (blue line) starts at 0.0 at 0 dB and reaches 1.0 at approximately 30 dB. + +##### h. PC2/5 UE with 23dBm maximum output power (n259) + +Figure 5.2.1.6-4 Indoor hotspot simulation results at 39 GHz + +##### Observation: + +It can be observed from figure 5.2.1.6-1, figure 5.2.1.6-2, figure 5.2.1.6-3 and figure 5.2.1.6-4 that at both 29 GHz (n257) and 39 GHz (n259 and n260): + +For urban macro scenario: + +- The target SNR of 28dB for 29 GHz at BS side can be achieved by 86.95% of PC1 UE and 73.26% of PC2/5 UE. +- The target SNR of 30dB for 39 GHz at BS side can be achieved by 82.82% of PC1 UE and 62.31% of PC2/5 UE. +- ~13% of PC1 UE and ~26% of PC2/5 UE are transmitting at maximum output power at 29 GHz (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). +- 17% of PC1 UE and ~27% of PC2/5 UE are transmitting at maximum output power at 39 GHz (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE). + +For indoor hotspot scenario: + +- The target SNR of 28dB for 29 GHz at BS side can be achieved by 100% of PC1 UE and 100% of PC2/5 UE. +- The target SNR of 30dB for 39 GHz at BS side can be achieved by 100% of PC1 UE and 99.99% of PC2/5 UE. +- The transmitting power of all PC1/PC2/PC5 UE are less than 20 dBm at 29 GHz. +- The transmitting power of ~ 99% PC1/PC2/PC5 UE are less than 13 dBm at 39 GHz. + +#### 5.2.1.7 Simulation results from LG Electronics + +R4-2300821 + +**-29 GHz UL 256QAM SLS** + +![CDF of SINR @29GHz in Urban Macro plot for PC2 and PC5.](4dfe30ac5a87d018364a0ac42ea533fe_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot titled "CDF of SINR @29GHz in Urban Macro". The x-axis is labeled "SINR [dB]" and ranges from -10 to 35. The y-axis is labeled "CDF" and ranges from 0 to 100. Two curves are plotted: a blue line for PC2 and an orange line for PC5. Both curves start near 0 at -10 dB and rise steeply between 20 dB and 30 dB. A vertical dashed yellow line is drawn at approximately 28 dB SINR. PC2 reaches a CDF of 100 at about 30 dB, while PC5 reaches it at about 32 dB. + +CDF of SINR @29GHz in Urban Macro plot for PC2 and PC5. + +Fig.5.2.1.7-1 CDF of SINR for PC2/PC5 in urban macro scenario at 29 GHz + +![CDF of SINR @29GHz in Indoor plot for PC2 and PC5.](8fe46741a1476acebc88235e1b6e0f0b_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot titled "CDF of SINR @29GHz in Indoor". The x-axis is labeled "SINR [dB]" and ranges from 0 to 40. The y-axis is labeled "CDF" and ranges from 0 to 100. Two curves are plotted: a blue line for PC2 and an orange line for PC5. Both curves start near 0 at 0 dB and rise steeply between 25 dB and 35 dB. A vertical dashed yellow line is drawn at approximately 28 dB SINR. PC2 reaches a CDF of 100 at about 35 dB, while PC5 reaches it at about 38 dB. + +CDF of SINR @29GHz in Indoor plot for PC2 and PC5. + +Fig. 5.2.1.7-2 CDF of SINR for PC2/PC5 in indoor scenario at 29 GHz + +Fig. 5.2.1.7-1 and Fig. 5.2.1.7-2 show CDF of SINR for PC2/PC5 in urban macro scenario and indoor scenario at 29 GHz respectively. + +Based on the SLS results, UL 256QAM at 29 GHz is feasible for both PC2 and PC5. + +**Observation 1:** From the 29 GHz 256QAM SLS results, PC2 and PC5 can achieve SINR of 28dB in both urban macro scenario and indoor scenario. + +##### **-39 GHz UL 256QAM SLS** + +![CDF of SINR @39GHz in Urban Macro plot for PC1, PC2, and PC5.](14d3e9dab6175ecd808705b6548b8f9a_img.jpg) + +This figure is a Cumulative Distribution Function (CDF) plot titled "CDF of SINR @39GHz in Urban Macro". The x-axis is labeled "SINR [dB]" and ranges from -10 to 40. The y-axis is labeled "CDF" and ranges from 0 to 100. Three curves are plotted: a blue line for PC1, an orange line for PC2, and a yellow line for PC5. All three curves start near 0 at -10 dB and rise steeply between 20 dB and 35 dB. A vertical dashed purple line is drawn at approximately 30 dB SINR. PC2 and PC5 reach a CDF of 100 at about 35 dB, while PC1 reaches it at about 38 dB. + +CDF of SINR @39GHz in Urban Macro plot for PC1, PC2, and PC5. + +**Fig. 5.2.1.7-3 CDF of SINR for PC1/PC2/PC5 in urban macro scenario at 39 GHz** + +![CDF of SINR @39GHz in Indoor scenario for PC1, PC2, and PC5. The plot shows the cumulative distribution function (CDF) of SINR [dB] on the x-axis (0 to 40) and CDF on the y-axis (0 to 100). Three curves are shown: PC1 (blue solid), PC2 (orange solid), and PC5 (yellow solid). All curves show a sharp increase in CDF between 25 dB and 35 dB. A vertical dashed line is drawn at 30 dB SINR. PC2 and PC5 reach a CDF of 100% around 35 dB, while PC1 reaches about 65% at 40 dB.](5bf611979ab0126ebd219a1c6eda6b1e_img.jpg) + +CDF of SINR @39GHz in Indoor scenario for PC1, PC2, and PC5. The plot shows the cumulative distribution function (CDF) of SINR [dB] on the x-axis (0 to 40) and CDF on the y-axis (0 to 100). Three curves are shown: PC1 (blue solid), PC2 (orange solid), and PC5 (yellow solid). All curves show a sharp increase in CDF between 25 dB and 35 dB. A vertical dashed line is drawn at 30 dB SINR. PC2 and PC5 reach a CDF of 100% around 35 dB, while PC1 reaches about 65% at 40 dB. + +**Fig. 5.2.1.7-4 CDF of SINR for PC1/PC2/PC5 in indoor scenario at 39 GHz** + +Fig. 5.2.1.7-3 and Fig. 5.2.1.7-4 show CDF of SINR for PC1/PC2/PC5 in urban macro scenario and indoor scenario at 39 GHz respectively. + +Based on the SLS results, UL 256QAM at 39GHz is feasible for PC1, PC2, and PC5 UEs. + +**Observation 2:** From the 39 GHz 256QAM SLS results, PC1, PC2 and PC5 can achieve SINR of 30dB in both urban macro scenario and indoor scenario. + +#### 5.2.1.8 Simulation results from Sony + +R4-2302240 + +The SLS simulation results at 29 GHz for the indoor scenario are shown in Fig. 5.2.1.8-1. Since PC1 has been concluded to be feasible, only results of PC2/5 have been provided here. + +![The system level simulation at 29 GHz for the indoor scenario with PC2/5. The plot shows the probability that SINR is less than or equal to a certain value (Prob(SINR) ≤ x) on the y-axis (0 to 1) against SINR [dB] on the x-axis (0 to 30). Two curves are shown: 1 UE (solid blue line) and 3 UE (dashed blue line). Both curves show a sharp increase in probability between 20 dB and 28 dB. A vertical dashed line is drawn at approximately 28 dB SINR. At 28 dB, the probability for 3 UE is about 0.75 and for 1 UE is about 0.65.](fa46b2ae8b3e08aaf2e6a0d53decd363_img.jpg) + +The system level simulation at 29 GHz for the indoor scenario with PC2/5. The plot shows the probability that SINR is less than or equal to a certain value (Prob(SINR) ≤ x) on the y-axis (0 to 1) against SINR [dB] on the x-axis (0 to 30). Two curves are shown: 1 UE (solid blue line) and 3 UE (dashed blue line). Both curves show a sharp increase in probability between 20 dB and 28 dB. A vertical dashed line is drawn at approximately 28 dB SINR. At 28 dB, the probability for 3 UE is about 0.75 and for 1 UE is about 0.65. + +**Figure 5.2.1.8-1 The system level simulation at 29 GHz for the indoor scenario with PC2/5.** + +As explained, a power control scheme is adopted in the simulation, and thus the CDF plot is “capped” by the target SNR. Based on the simulation results, it can be observed that about 35% of UE can reach the target SNR, which is a significant portion of total devices. Therefore, it can be concluded that it is feasible for PC2 and PC5 to support 256 QAM at 29 GHz. + +Observation 1: 35% of UE can reach the target SNR condition of PC2 and PC5 at indoor scenario at 29 GHz. + +Further simulations have also been performed for 39GHz for the indoor scenario, including PC1 as well, where the simulation results are shown in Fig. 5.2.1.8-2 (PC1) and Fig. 5.2.1.8-3 (PC2/5), respectively. + +![Figure 5.2.1.8-2: System level simulation at 39 GHz for the indoor scenario with PC1. The graph plots the probability of SINR being less than or equal to a certain value (Prob(SINR) ≤ abscissas) against SINR in dB. Two curves are shown: 1 UE (solid line) and 3 UE (dashed line). The 3 UE curve is higher than the 1 UE curve, indicating better performance. At 30 dB SINR, the 3 UE curve reaches approximately 0.55, while the 1 UE curve reaches approximately 0.22.](bac21fd48fcd7f025c723590e07d1823_img.jpg) + +| SINR / dB | Prob(SINR) ≤ abscissas (1 UE) | Prob(SINR) ≤ abscissas (3 UE) | +|-----------|-------------------------------|-------------------------------| +| 0 | 0.00 | 0.00 | +| 5 | 0.00 | 0.01 | +| 10 | 0.00 | 0.05 | +| 15 | 0.00 | 0.10 | +| 20 | 0.00 | 0.18 | +| 25 | 0.05 | 0.35 | +| 30 | 0.22 | 0.55 | + +Figure 5.2.1.8-2: System level simulation at 39 GHz for the indoor scenario with PC1. The graph plots the probability of SINR being less than or equal to a certain value (Prob(SINR) ≤ abscissas) against SINR in dB. Two curves are shown: 1 UE (solid line) and 3 UE (dashed line). The 3 UE curve is higher than the 1 UE curve, indicating better performance. At 30 dB SINR, the 3 UE curve reaches approximately 0.55, while the 1 UE curve reaches approximately 0.22. + +Figure 5.2.1.8-2 The system level simulation at 39 GHz for the indoor scenario with PC1. + +![Figure 5.2.1.8-3: System level simulation at 39 GHz for the indoor scenario with PC2/5. The graph plots the probability of SINR being less than or equal to a certain value (Prob(SINR) ≤ abscissas) against SINR in dB. Two curves are shown: 1 UE (solid line) and 3 UE (dashed line). The 3 UE curve is higher than the 1 UE curve, indicating better performance. At 30 dB SINR, the 3 UE curve reaches approximately 0.95, while the 1 UE curve reaches approximately 0.90.](645cfdb7a7e02c3b04b20d83aed890c3_img.jpg) + +| SINR / dB | Prob(SINR) ≤ abscissas (1 UE) | Prob(SINR) ≤ abscissas (3 UE) | +|-----------|-------------------------------|-------------------------------| +| 0 | 0.00 | 0.00 | +| 5 | 0.00 | 0.02 | +| 10 | 0.00 | 0.05 | +| 15 | 0.05 | 0.15 | +| 20 | 0.25 | 0.45 | +| 25 | 0.75 | 0.85 | +| 30 | 0.90 | 0.95 | + +Figure 5.2.1.8-3: System level simulation at 39 GHz for the indoor scenario with PC2/5. The graph plots the probability of SINR being less than or equal to a certain value (Prob(SINR) ≤ abscissas) against SINR in dB. Two curves are shown: 1 UE (solid line) and 3 UE (dashed line). The 3 UE curve is higher than the 1 UE curve, indicating better performance. At 30 dB SINR, the 3 UE curve reaches approximately 0.95, while the 1 UE curve reaches approximately 0.90. + +Figure 5.2.1.8-3 The system level simulation at 39 GHz for the indoor scenario with PC2/5. + +Based on the results shown in Fig. 5.2.1.8-2 and Fig. 5.2.1.8-3, though the target SNR and path loss have been increased, a significant portion of UE (45% for PC1 and 10% for PC2/5) can still meet the target SINR. Again, such simulation results demonstrate that a system-level gain can be obtained by supporting 256 QAM for uplink, which suggests that it is feasible to support 256 QAM in uplink is feasible for PC1/2/5 at 39 GHz. + +Observation 2: 45% of PC1 UE and 10% of PC2/5 UE can meet the target SNR condition for the indoor scenario at 39 GHz. + +#### 5.2.1.9 Summary for system level simulation results + +| Companies | Urban macro | Indoor | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Nokia
(R4-2300193) |

The target SNR at BS side of 27 dB can be achieved by ~70% of PC1 UE and ~60% of PC2/5 UE.

Less than 15% of PC1 UE and less than 30% of PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE).

|

The target SNR at BS side of 27 dB can be achieved by ~70% of PC1 UE and ~60% of PC2/5 UE.

Almost none of PC1 UE and PC2/5 UE are transmitting at maximum output power (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE).

| +| LG Electronics
(R4-2300821) |

For 29GHz:
The target SNR at BS side of 28 dB can be achieved by ~77% of PC2 UE and ~65% of PC5 UE.

For 39GHz:
The target SNR at BS side of 30 dB can be achieved by ~40% of PC1 UE, ~85% of PC2 UE and 70% of PC5.

|

For 29GHz:
The target SNR at BS side of 28 dB can be achieved by ~41% of PC2 UE and ~40% of PC5 UE.

For 39GHz:
The target SNR at BS side of 30 dB can be achieved by ~37% of PC1 UE, ~75% of PC2 UE and 50% of PC5.

| +| ZTE
(R4-2301235) |

For 29GHz
5% UE can achieve above 30dB SINR for PC2 and PC5.
Even ~10% UE can achieve above 28dB SINR even for PC3.
Thus we observed PC2 and PC5 are feasible for UL 256QAM for 29GHz, and PC3 is also feasible if the operating SNR is not higher than 28dB.

For 39GHz:
For PC1, ~55% of UE can reach the operating SNR
For PC2, ~8% of UE can reach the operating SNR
For PC5 , ~15% of UE can reach the operating SNR
For PC3, ~2% of UE can reach the operating SNR

|

for 39GHz:
For PC1, PC2 and PC5, ~86% of UE can reach the operating SNR
For PC3, ~75% of UE can reach the operating SNR

| +| vivo
(R4-2301569) |

In 29GHz:
5% in Uma PC2/PC5 UE can archive 28 dB SNR.

In 39GHz:
10% in Uma PC1 UE can archive 30 dB SNR
2% in Uma PC2/PC5 UE can archive 30 dB SNR.

|

In 29GHz:
14% in Indoor PC2/PC5 UE can archive 28 dB SNR.

In 39GHz:
12% in Indoor PC1 UE can archive 30 dB SNR;
10% in Indoor PC2/PC5 UE can archive 30 dB SNR.

| +| Xiaomi
(R4-2301620) |

For 29GHz:
The target SNR of 28dB for 29 GHz at BS side can be achieved by 86.95% of PC1 UE and 73.26% of PC2/5 UE.
~13% of PC1 UE and ~26% of PC2/5 UE are transmitting at maximum output power at 29 GHz (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE).

For 39GHz:
The target SNR of 30dB for 39 GHz at BS side can be achieved by 82.82% of PC1 UE and 62.31% of PC2/5 UE.
~17% of PC1 UE and ~27% of PC2/5 UE are transmitting at maximum output power at 39 GHz (of 35 dBm and 23 dBm, respectively, for PC1 UE and PC2/5 UE).

|

For 29GHz:
The target SNR of 28dB for 29 GHz at BS side can be achieved by 100% of PC1 UE and 100% of PC2/5 UE.
The transmitting power of all PC1/PC2/PC5 UE are less than 20 dBm at 29 GHz.

For 39GHz:
The target SNR of 30dB for 39 GHz at BS side can be achieved by 100% of PC1 UE and 99.99% of PC2/5 UE.
The transmitting power of ~ 99% PC1/PC2/PC5 UE are less than 13 dBm at 39 GHz.

| +| Sony
(R4-2302240) | |

For 29GHz:
35% of UE can reach the target SNR condition of PC2 and PC5 at indoor scenario at 29 GHz.

For 39GHz:
45% of PC1 UE and 10% of PC2/5 UE can meet the target SNR condition for the indoor scenario at 39 GHz.

| +| Ericsson
(R4-2302734) |

For 29GHz:
UMa scenario and PC2/PC5, around 30% of users with FTP 10% load and 28% of users with FTP 30% load can reach the operating SNR of 28dB.

|

For 29GHz:
Indoor scenario and PC2/PC5, around 60% of users with FTP 10% load and 15% of users with FTP 30% load can reach the operating SNR of 28dB.

| + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

For 39GHz:
UMa scenario and PC2/PC5, around 17% of users with FTP 10% load and 15% of users with FTP 30% load can reach the operating SNR of 30dB.
UMa scenario and PC1, around 50% of users with FTP 10% load and 38% of users with FTP 30% load can reach the operating SNR of 30dB.

|

For 39GHz:
Indoor scenario and PC2/PC5, around 50% of users with FTP 10% load and 12% of users with FTP 30% load can reach the operating SNR of 30dB.
Indoor scenario and PC1, around 55% of users with FTP 10% load and 12% of users with FTP 30% load can reach the operating SNR of 30dB.

| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.2 Link level simulation + +Link level simulation is targeted as mainstream way to evaluate if FR2 256QAM can achieve benefit by comparing to 64QAM. + +#### 5.2.2.1 Simulation assumptions + +The link level simulation assumptions are listed as in table 5.2.2.1-1, based on which, to evaluate the throughput difference between 64QAM and 256QAM. The study aims to identify conditions where UL 256QAM provides performance benefits, does not reflect side conditions for setting the UE RF requirement for UL 256QAM. + +**Table 5.2.2.1-1 link level simulation assumptions** + +| Parameter | Value | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Carrier frequency | 29 GHz (n257), 39 GHz (n260) and 48GHz (n262) | +| CBW | 50 MHz, 100MHz | +| SCS | 120 kHz | +| Allocated RBs | Full allocation | +| Propagation | TDL-A 30ns delay spread, 35Hz Doppler frequency
TDL-D 30ns delay spread, 35Hz Doppler frequency
Static (AWGN) | +| MCS | 64QAM:
CP-OFDM: MCS 23, 24 in TS 38.214 Table 5.1.3.1-1, other MCSs are not precluded.
DFT-s-OFDM: MCS 22, 23 in TS 38.214 Table 6.1.4.1-1, other MCSs are not precluded.
256QAM:
CP-OFDM/DFT-s-OFDM: MCS 21, 23 in TS 38.214 Table 5.1.3.1-2, other MCSs are not precluded.
Baseline: fixed MCSs | +| Symbol type | CP-OFDM; DFT-s-OFDM | +| HARQ | 8, None | +| Antenna configuration | Fading channel: 2x2 for Rank1 and Rank2, Low correlation
Static channel: 1x2 for Rank1, 2x2 for Rank2 (using the diagonal matrix) | +| Channel estimation | Practical | +| Receiver type | MMSE | +| PUSCH configuration | Type A mapping, Start symbol 0, Duration 14 | +| DMRS configuration | Type 1, Single symbol, 1 additional DMRS | +| PTRS configuration | CP-OFDM: KPTRS : 2 (every 2 RBs), LPTRS : 1 (every 1 symbol)
DFT-s-OFDM: ( $N_{\text{group}}^{\text{PTRS}}$ , )=(4, 4), LPTRS : 1 (every 1 symbol) | +| Phase noise compensation | Practical based on PTRS | +| Phase noise model | TR 38.803 model (in section 6.1.10 and section 6.1.11)
modelled Phase noise for TX and RX
Option a): example1 (UE) + example1(BS)
Option b): example2 (UE) + example2(BS)
Option d): example1 (UE) + example2(BS) | +| txEVM + rxEVM excluding phase noise for 256QAM | txEVM: 3%, 3.5%, 4%, rxEVM: 3%, 3.5%, 4%
Option 1: txEVM >= rxEVM; | +| Other parameters | follow assumptions in TS38.104 Section 11.2.2 . | + +#### 5.2.2.2 Simulation results from Nokia + +R4-2215577 + +The link level simulation results at 29 GHz (n257) and 39 GHz (n260) using the highlighted parameters in table 1 are shown in figures 5.2.2.2-1 and 5.2.2.2-2, respectively. + +![Figure 5.2.2.2-1: Simulation results at 29 GHz (n257). A line graph showing Throughput vs SNR [dB] for 29 GHz, TDL-D 30ns, 50MHz. The y-axis is logarithmic, ranging from 10^6 to 10^8. The x-axis ranges from 18 to 40 dB. Multiple curves represent different MCS indices (21, 23, 24) and EVM levels (3, 3.5, 4) for 256QAM and 64QAM. The legend indicates: BW=50 MHz, SCS=120 kHz. The graph shows that higher MCS indices and lower EVM levels result in higher throughput. 256QAM generally outperforms 64QAM, especially at higher SNR and lower EVM.](771c18f874d31c59c3b8c4e247be16ca_img.jpg) + +Figure 5.2.2.2-1: Simulation results at 29 GHz (n257). A line graph showing Throughput vs SNR [dB] for 29 GHz, TDL-D 30ns, 50MHz. The y-axis is logarithmic, ranging from 10^6 to 10^8. The x-axis ranges from 18 to 40 dB. Multiple curves represent different MCS indices (21, 23, 24) and EVM levels (3, 3.5, 4) for 256QAM and 64QAM. The legend indicates: BW=50 MHz, SCS=120 kHz. The graph shows that higher MCS indices and lower EVM levels result in higher throughput. 256QAM generally outperforms 64QAM, especially at higher SNR and lower EVM. + +Figure 5.2.2.2-1. Simulation results at 29 GHz (n257) + +![Figure 5.2.2.2-2: Simulation results at 39 GHz (n260). A line graph showing Throughput vs SNR [dB] for 39 GHz, TDL-D 30ns, 50MHz. The y-axis is logarithmic, ranging from 10^6 to 10^8. The x-axis ranges from 18 to 40 dB. Multiple curves represent different MCS indices (21, 23, 24) and EVM levels (0, 3, 3.5, 4) for 256QAM and 64QAM. The legend indicates: BW=50 MHz, SCS=120 kHz. The graph shows that at 39 GHz, the performance of 256QAM and 64QAM is more similar than at 29 GHz. Only with an EVM of 0% does MCS21 for 256QAM seem to win over 64QAM at around 36 dB SNR.](0aa15f5c9c3edae230985491199cfe8b_img.jpg) + +Figure 5.2.2.2-2: Simulation results at 39 GHz (n260). A line graph showing Throughput vs SNR [dB] for 39 GHz, TDL-D 30ns, 50MHz. The y-axis is logarithmic, ranging from 10^6 to 10^8. The x-axis ranges from 18 to 40 dB. Multiple curves represent different MCS indices (21, 23, 24) and EVM levels (0, 3, 3.5, 4) for 256QAM and 64QAM. The legend indicates: BW=50 MHz, SCS=120 kHz. The graph shows that at 39 GHz, the performance of 256QAM and 64QAM is more similar than at 29 GHz. Only with an EVM of 0% does MCS21 for 256QAM seem to win over 64QAM at around 36 dB SNR. + +Figure 5.2.2.2-2. Simulation results at 39 GHz (n260) + +It can be observed from figure 5.2.2.2-1 that at 29 GHz (n257): + +- If MCS index is 21, 256QAM goes over 64QAM in around 24-25 dB for all simulated EVMs. +- If MCS index is 23, 256QAM goes over 64QAM in around 28 dB for (transmit and receive) EVM of 3%, around 32 dB for (transmit and receive) EVM of 3.5%, and loses for (transmit and receive) EVM of 4%. + +On the other hand, it can be observed from figure 5.2.2.2-2 that at 39 GHz (n260): + +- Only with (transmit and receive) EVM of 0%, MCS21 for 256QAM seems to win 64QAM in around 36 dB. + +Note that the PN is challenging case at 39 GHz (n260), and due to small allocation, the number of PTRS symbols is quite low so even higher complexity ICI compensation would not really help here. + +R4-2218326 + +The link level simulation results at 48 GHz (n262) using the highlighted parameters in table 1 with phase noise model option a and option d are shown in figures 5.2.2.2-3 and 5.2.2.2-4, respectively. + +![Line graph titled '48GHz, TDL-D 30ns, 50MHz' showing Throughput vs SNR [dB]. The y-axis is logarithmic from 10^6 to 10^8. The x-axis is linear from 20 to 40 dB. Multiple data series are plotted with different markers and line styles, representing various configurations of bandwidth (BW), subcarrier spacing (SCS), modulation and coding scheme (MCS) index, MCS table, and error vector magnitude (EVM). All series show a sharp increase in throughput from 10^6 at 15 dB SNR to approximately 1.5 x 10^8 at 20 dB SNR, then plateau. The EVM 0 series (blue) generally achieve higher throughput than EVM 3 and EVM 3.5 series (red and green respectively). Within each EVM group, higher MCS index and MCS table 2 (256QAM) result in higher throughput compared to MCS table 1 (64QAM).](e51925aa86bb1cd1ea891dbb493caa4f_img.jpg) + +Line graph titled '48GHz, TDL-D 30ns, 50MHz' showing Throughput vs SNR [dB]. The y-axis is logarithmic from 10^6 to 10^8. The x-axis is linear from 20 to 40 dB. Multiple data series are plotted with different markers and line styles, representing various configurations of bandwidth (BW), subcarrier spacing (SCS), modulation and coding scheme (MCS) index, MCS table, and error vector magnitude (EVM). All series show a sharp increase in throughput from 10^6 at 15 dB SNR to approximately 1.5 x 10^8 at 20 dB SNR, then plateau. The EVM 0 series (blue) generally achieve higher throughput than EVM 3 and EVM 3.5 series (red and green respectively). Within each EVM group, higher MCS index and MCS table 2 (256QAM) result in higher throughput compared to MCS table 1 (64QAM). + +Figure 5.2.2.2-3. Simulation results with phase noise model option a + +![Line graph titled '48GHz, TDL-D 30ns, 50MHz' showing Throughput vs SNR [dB]. The y-axis is logarithmic from 10^6 to 10^8. The x-axis is linear from 20 to 40 dB. Multiple lines represent different configurations of BW=50 MHz, SCS=120 kHz, MCS index (21, 23, 24), MCS table (1: 64QAM, 2: 256QAM), and EVM (0, 3, 3.5). Solid lines represent EVM 0, dashed lines represent EVM 3, and dotted lines represent EVM 3.5. Blue lines are MCS index 21, red lines are MCS index 23, and green lines are MCS index 24. Squares represent MCS table 2 (256QAM) and circles represent MCS table 1 (64QAM).](cfc852835f2d91bea8dc074568937e22_img.jpg) + +Line graph titled '48GHz, TDL-D 30ns, 50MHz' showing Throughput vs SNR [dB]. The y-axis is logarithmic from 10^6 to 10^8. The x-axis is linear from 20 to 40 dB. Multiple lines represent different configurations of BW=50 MHz, SCS=120 kHz, MCS index (21, 23, 24), MCS table (1: 64QAM, 2: 256QAM), and EVM (0, 3, 3.5). Solid lines represent EVM 0, dashed lines represent EVM 3, and dotted lines represent EVM 3.5. Blue lines are MCS index 21, red lines are MCS index 23, and green lines are MCS index 24. Squares represent MCS table 2 (256QAM) and circles represent MCS table 1 (64QAM). + +Figure 5.2.2.2-4. Simulation results with phase noise model option d + +It can be observed from figures 5.2.2.2-3 and 5.2.2.2-4 that at 48 GHz (n262): + +- 256QAM does not provide any throughput gain over 64QAM below 40 dB SNR. + +#### 5.2.2.3 Simulation results from LG Electronics + +[R4-2215920](#) + +Table 5.2.2.3-1 shows the cross throughput point, where the cross throughput point indicates the SNR value at which the throughput of 64QAM and 256QAM is same, that is, after the corresponding SNR, the throughput of 256QAM is higher than 64QAM. + +**Table 5.2.2.3-1 Cross throughput point (29 GHz and 48 GHz, CBW:100 MHz, EVM:Tx=Rx)** + +**Reference: MCS24(64QAM, PUSCH Table 1, OFDM)** + +| Propagation
MCS
Mode | EVM: 2% | | EVM: 3% | | EVM: 3.5% | | +|------------------------------------------------------------|---------|---------|---------|--------|-----------|--------| +| | 29 GHz | 48 GHz | 29 GHz | 48 GHz | 29 GHz | 48 GHz | +| TDL-A
MCS 21
(256 QAM, PDSCH Table 2, OFDM) | 24.5 dB | N/A | 27 dB | N/A | 30 dB | N/A | +| TDL-A
MCS 23
(256 QAM, PDSCH Table 2, OFDM) | 29 dB | N/A | N/A | N/A | N/A | N/A | +| TDL-D
MCS 21
(256 QAM, PDSCH Table 2, OFDM) | 18.5 dB | 30 dB | 20 dB | N/A | 21 dB | N/A | +| TDL-D
MCS 23
(256 QAM, PDSCH Table 2, OFDM) | 23 dB | N/A | 24.5 dB | N/A | 27 dB | N/A | +| AWGN
MCS 21
(256 QAM, PDSCH Table 2, OFDM) | 16 dB | 22.5 dB | 16.5 dB | 24 dB | 17 dB | 27.5dB | +| AWGN
MCS 23
(256 QAM, PDSCH Table 2, OFDM) | 19 dB | N/A | 20 dB | N/A | 21 dB | N/A | + +**29 GHz (n257), EVM(Tx=Rx):3.5%** + +![Throughput performance graph for TDL-A channel showing 256QAM and 64QAM curves with a cross point at 30 dB SNR.](7a0663ba11ddcae06cc5a490f81a7243_img.jpg) + +This graph shows the throughput performance for the TDL-A channel at 29 GHz (n257) with an EVM of 3.5%. The x-axis represents SNR in dB, ranging from 10 to 35. The y-axis represents Throughput in Mbps, ranging from 0 to 400. There are four data series: 256-QAM (MCS21, PDSCH2) PTRS K=2, CPE (red line with triangles); 256-QAM (MCS23, PDSCH2) PTRS K=2, CPE (magenta line with triangles); 64-QAM (MCS22, PDSCH1) PTRS K=2, CPE (blue line with triangles); and 64-QAM (MCS24, PDSCH1) PTRS K=2, CPE (green line with triangles). The 64-QAM curves show a sharp increase in throughput starting around 15 dB SNR, while the 256-QAM curves start increasing around 20 dB SNR. A red arrow points to the intersection of the 256-QAM (MCS21) and 64-QAM (MCS24) curves, labeled 'Cross point:30 dB'. + +Throughput performance graph for TDL-A channel showing 256QAM and 64QAM curves with a cross point at 30 dB SNR. + +**Fig 5.2.2.3-1. Throughput performance between 256QAM and 64QAM in TDL-A** + +![Throughput performance graph for TDL-D channel showing 256QAM and 64QAM curves with cross points at 21 dB and 27 dB SNR.](cd965c09af15211ca52d38d49be7b515_img.jpg) + +This graph shows the throughput performance for the TDL-D channel at 29 GHz (n257) with an EVM of 3.5%. The x-axis represents SNR in dB, ranging from 10 to 35. The y-axis represents Throughput in Mbps, ranging from 0 to 450. The same four data series as in Figure 5.2.2.3-1 are plotted. The 64-QAM curves show a sharp increase in throughput starting around 12 dB SNR. The 256-QAM curves show two distinct cross points: one at approximately 21 dB SNR (indicated by a red arrow and 'Cross point:21 dB') and another at approximately 27 dB SNR (indicated by a red arrow and 'Cross point:27 dB'). + +Throughput performance graph for TDL-D channel showing 256QAM and 64QAM curves with cross points at 21 dB and 27 dB SNR. + +**Fig 5.2.2.3-2. Throughput performance between 256QAM and 64QAM in TDL-D** + +![Throughput performance graph for AWGN channel. Y-axis: Throughput, Mbps (0-500). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotations: Cross point: 21 dB, Cross point: 17 dB.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +CP-OFDM, 2x2 rank1, SCS 120 kHz, AWGN, BW 100MHz + +Throughput, Mbps + +SNR, dB + +Legend: + - 256-QAM (MCS21/PDSCH2), PTRS K=2, CPE (Red triangles) + - 256-QAM (MCS23/PDSCH2), PTRS K=2, CPE (Magenta triangles) + - 64-QAM (MCS23/PDSCH1), PTRS K=2, CPE (Blue triangles) + - 64-QAM (MCS24/PDSCH1), PTRS K=2, CPE (Green triangles) + +Cross point: 21 dB + +Cross point: 17 dB + +Throughput performance graph for AWGN channel. Y-axis: Throughput, Mbps (0-500). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotations: Cross point: 21 dB, Cross point: 17 dB. + +Fig 5.2.2.3-3. Throughput performance between 256QAM and 64QAM in AWGN + +29 GHz (n257), EVM(Tx=Rx):3% + +![Throughput performance graph for TDL-A channel. Y-axis: Throughput, Mbps (0-450). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotation: Cross point: 27 dB.](031e354d9de9563c9f650e3e4fcba16d_img.jpg) + +CP-OFDM, 2x2 rank1, SCS 120 kHz, TDLA30-35, BW 100MHz + +Throughput, Mbps + +SNR, dB + +Legend: + - 256-QAM (MCS21/PDSCH2), PTRS K=2, CPE (Red triangles) + - 256-QAM (MCS23/PDSCH2), PTRS K=2, CPE (Magenta triangles) + - 64-QAM (MCS23/PDSCH1), PTRS K=2, CPE (Blue triangles) + - 64-QAM (MCS24/PDSCH1), PTRS K=2, CPE (Green triangles) + +Cross point: 27 dB + +Throughput performance graph for TDL-A channel. Y-axis: Throughput, Mbps (0-450). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotation: Cross point: 27 dB. + +Fig 5.2.2.3-4. Throughput performance between 256QAM and 64QAM in TDL-A + +![Throughput performance graph for TDL-D channel. Y-axis: Throughput, Mbps (0-500). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotations: Cross point: 24.5 dB, Cross point: 20 dB.](e51f9764097b236acbf8f544491dd24f_img.jpg) + +CP-OFDM, 2x2 rank1, SCS 120 kHz, TDLD30-35, BW 100MHz + +Throughput, Mbps + +SNR, dB + +Legend: + - 256-QAM (MCS21/PDSCH2), PTRS K=2, CPE (Red triangles) + - 256-QAM (MCS23/PDSCH2), PTRS K=2, CPE (Magenta triangles) + - 64-QAM (MCS23/PDSCH1), PTRS K=2, CPE (Blue triangles) + - 64-QAM (MCS24/PDSCH1), PTRS K=2, CPE (Green triangles) + +Cross point: 24.5 dB + +Cross point: 20 dB + +Throughput performance graph for TDL-D channel. Y-axis: Throughput, Mbps (0-500). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotations: Cross point: 24.5 dB, Cross point: 20 dB. + +Fig 5.2.2.3-5. Throughput performance between 256QAM and 64QAM in TDL-D + +![Throughput performance graph for AWGN channel. Y-axis: Throughput, Mbps (0-500). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotations: Cross point: 20 dB, Cross point: 16.5 dB.](282b054897a74f36790420bcf6568656_img.jpg) + +CP-OFDM, 2x2 rank1, SCS 120 kHz, AWGN, BW 100MHz + +Throughput, Mbps + +SNR, dB + +Legend: + - 256-QAM (MCS21/PDSCH2), PTRS K=2, CPE (Red triangles) + - 256-QAM (MCS23/PDSCH2), PTRS K=2, CPE (Magenta triangles) + - 64-QAM (MCS23/PDSCH1), PTRS K=2, CPE (Blue triangles) + - 64-QAM (MCS24/PDSCH1), PTRS K=2, CPE (Green triangles) + +Cross point: 20 dB + +Cross point: 16.5 dB + +Throughput performance graph for AWGN channel. Y-axis: Throughput, Mbps (0-500). X-axis: SNR, dB (10-35). Legend: 256-QAM (MCS21/PDSCH2), 256-QAM (MCS23/PDSCH2), 64-QAM (MCS23/PDSCH1), 64-QAM (MCS24/PDSCH1). Annotations: Cross point: 20 dB, Cross point: 16.5 dB. + +Fig 5.2.2.3-6. Throughput performance between 256QAM and 64QAM in AWGN + +##### **29 GHz (n257), EVM(Tx=Rx):2%** + +![Throughput performance between 256QAM and 64QAM in TDL-A channel model.](1eb72b1e2fe3920b483f6245e5d477e8_img.jpg) + +This graph shows the throughput performance for the TDL-A channel model. The x-axis represents SNR in dB, ranging from 10 to 35. The y-axis represents Throughput in Mbps, ranging from 0 to 450. The legend indicates four configurations: 256-QAM (MCS21\_PDSCH2), 256-QAM (MCS23\_PDSCH2), 64-QAM (MCS23\_PDSCH1), and 64-QAM (MCS24\_PDSCH1). The 64-QAM (MCS24\_PDSCH1) curve (green triangles) reaches a plateau of approximately 340 Mbps. The 64-QAM (MCS23\_PDSCH1) curve (blue triangles) reaches a plateau of approximately 320 Mbps. The 256-QAM (MCS21\_PDSCH2) curve (red triangles) reaches a plateau of approximately 420 Mbps. The 256-QAM (MCS23\_PDSCH2) curve (magenta triangles) reaches a plateau of approximately 440 Mbps. Two cross points are marked: one at 24.5 dB SNR where the 64-QAM (MCS24\_PDSCH1) and 256-QAM (MCS21\_PDSCH2) curves intersect, and another at 29 dB SNR where the 64-QAM (MCS23\_PDSCH1) and 256-QAM (MCS23\_PDSCH2) curves intersect. + +Throughput performance between 256QAM and 64QAM in TDL-A channel model. + +**Fig 5.2.2.3-7. Throughput performance between 256QAM and 64QAM in TDL-A** + +![Throughput performance between 256QAM and 64QAM in TDL-D channel model.](4f90ddf705239c0ca535c91179212420_img.jpg) + +This graph shows the throughput performance for the TDL-D channel model. The x-axis represents SNR in dB, ranging from 10 to 35. The y-axis represents Throughput in Mbps, ranging from 0 to 500. The legend indicates four configurations: 256-QAM (MCS21\_PDSCH2), 256-QAM (MCS23\_PDSCH2), 64-QAM (MCS23\_PDSCH1), and 64-QAM (MCS24\_PDSCH1). The 64-QAM (MCS24\_PDSCH1) curve (green triangles) reaches a plateau of approximately 340 Mbps. The 64-QAM (MCS23\_PDSCH1) curve (blue triangles) reaches a plateau of approximately 320 Mbps. The 256-QAM (MCS21\_PDSCH2) curve (red triangles) reaches a plateau of approximately 420 Mbps. The 256-QAM (MCS23\_PDSCH2) curve (magenta triangles) reaches a plateau of approximately 480 Mbps. Two cross points are marked: one at 18.5 dB SNR where the 64-QAM (MCS24\_PDSCH1) and 256-QAM (MCS21\_PDSCH2) curves intersect, and another at 23 dB SNR where the 64-QAM (MCS23\_PDSCH1) and 256-QAM (MCS23\_PDSCH2) curves intersect. + +Throughput performance between 256QAM and 64QAM in TDL-D channel model. + +**Fig 5.2.2.3-8. Throughput performance between 256QAM and 64QAM in TDL-D** + +![Throughput performance between 256QAM and 64QAM in AWGN channel model.](79bd707e4636b9a1d4dbd443ef857814_img.jpg) + +This graph shows the throughput performance for the AWGN channel model. The x-axis represents SNR in dB, ranging from 10 to 35. The y-axis represents Throughput in Mbps, ranging from 0 to 500. The legend indicates four configurations: 256-QAM (MCS21\_PDSCH2), 256-QAM (MCS23\_PDSCH2), 64-QAM (MCS23\_PDSCH1), and 64-QAM (MCS24\_PDSCH1). The 64-QAM (MCS24\_PDSCH1) curve (green triangles) reaches a plateau of approximately 340 Mbps. The 64-QAM (MCS23\_PDSCH1) curve (blue triangles) reaches a plateau of approximately 320 Mbps. The 256-QAM (MCS21\_PDSCH2) curve (red triangles) reaches a plateau of approximately 420 Mbps. The 256-QAM (MCS23\_PDSCH2) curve (magenta triangles) reaches a plateau of approximately 480 Mbps. Two cross points are marked: one at 16 dB SNR where the 64-QAM (MCS24\_PDSCH1) and 256-QAM (MCS21\_PDSCH2) curves intersect, and another at 19 dB SNR where the 64-QAM (MCS23\_PDSCH1) and 256-QAM (MCS23\_PDSCH2) curves intersect. + +Throughput performance between 256QAM and 64QAM in AWGN channel model. + +**Fig 5.2.2.3-9. Throughput performance between 256QAM and 64QAM in AWGN** + +##### **48 GHz (n262), EVM(Tx=Rx):3.5%** + +![Throughput performance graph for TDL-A channel showing 256QAM and 64QAM configurations.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +This graph shows the throughput performance for the TDL-A channel. The x-axis represents SNR in dB from 10 to 35, and the y-axis represents Throughput in Mbps from 0 to 350. The legend indicates four configurations: 256-QAM (MCS21, PD SCH2), PTRS K=2, CPE (red triangles); 256-QAM (MCS23, PD SCH2), PTRS K=2, CPE (green triangles); 64-QAM (MCS23, PD SCH1), PTRS K=2, CPE (blue triangles); and 64-QAM (MCS24, PD SCH1), PTRS K=2, CPE (yellow triangles). The 64-QAM configurations show a sharp increase in throughput starting around 15 dB SNR, reaching a plateau of approximately 320-340 Mbps. The 256-QAM configurations show significantly lower throughput, remaining below 50 Mbps across the entire SNR range. + +Throughput performance graph for TDL-A channel showing 256QAM and 64QAM configurations. + +Fig 5.2.2.3-10. Throughput performance between 256QAM and 64QAM in TDL-A + +![Throughput performance graph for TDL-D channel showing 256QAM and 64QAM configurations.](198d076da025c516aec8122a6ab7db20_img.jpg) + +This graph shows the throughput performance for the TDL-D channel. The axes and legend are identical to Fig 5.2.2.3-10. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 12 dB SNR, reaching a plateau of approximately 320-340 Mbps. The 256-QAM configurations (red and green lines) show a much lower throughput, with the red line (MCS21) increasing to about 240 Mbps at 35 dB SNR, while the green line (MCS23) remains near zero. + +Throughput performance graph for TDL-D channel showing 256QAM and 64QAM configurations. + +Fig 5.2.2.3-11. Throughput performance between 256QAM and 64QAM in TDL-D + +![Throughput performance graph for AWGN channel showing 256QAM and 64QAM configurations with a cross-point annotation.](94389c644d3c25d99db7bc6d87bf5779_img.jpg) + +This graph shows the throughput performance for the AWGN channel. The axes and legend are identical to Fig 5.2.2.3-10. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 320-340 Mbps. The 256-QAM configurations (red and green lines) show a lower throughput, with the red line (MCS21) increasing to about 360 Mbps at 35 dB SNR. A red arrow points to the intersection of the red and blue lines at approximately 27.5 dB SNR, labeled 'Cross point: 27.5 dB'. + +Throughput performance graph for AWGN channel showing 256QAM and 64QAM configurations with a cross-point annotation. + +Fig 5.2.2.3-12. Throughput performance between 256QAM and 64QAM in AWGN + +48 GHz (n262), EVM(Tx=Rx):3% + +![Throughput performance graph for TDL-A channel at 48 GHz showing 256QAM and 64QAM configurations.](eb6482b0b8b6063abda95a4465019f68_img.jpg) + +This graph shows the throughput performance for the TDL-A channel at 48 GHz. The axes and legend are identical to Fig 5.2.2.3-10. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 15 dB SNR, reaching a plateau of approximately 320-340 Mbps. The 256-QAM configurations (red and green lines) show significantly lower throughput, with the red line (MCS21) increasing to about 80 Mbps at 35 dB SNR, while the green line (MCS23) remains near zero. + +Throughput performance graph for TDL-A channel at 48 GHz showing 256QAM and 64QAM configurations. + +Fig 5.2.2.3-13. Throughput performance between 256QAM and 64QAM in TDL-A + +![Throughput performance graph for TDL-D channel at 48 GHz showing 256QAM and 64QAM configurations.](b5cea511e0342583600125d1ccbec500_img.jpg) + +This graph shows the throughput performance for the TDL-D channel at 48 GHz. The axes and legend are identical to Fig 5.2.2.3-10. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 12 dB SNR, reaching a plateau of approximately 320-340 Mbps. The 256-QAM configurations (red and green lines) show a lower throughput, with the red line (MCS21) increasing to about 300 Mbps at 35 dB SNR, while the green line (MCS23) remains near zero. + +Throughput performance graph for TDL-D channel at 48 GHz showing 256QAM and 64QAM configurations. + +Fig 5.2.2.3-14. Throughput performance between 256QAM and 64QAM in TDL-D + +![Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, AWGN, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 380 Mbps. A 'Cross point: 24 dB' is marked where the 64-QAM and 256-QAM curves intersect.](0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg) + +Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, AWGN, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 380 Mbps. A 'Cross point: 24 dB' is marked where the 64-QAM and 256-QAM curves intersect. + +Fig 5.2.2.3-15. Throughput performance between 256QAM and 64QAM in AWGN + +48 GHz (n262), EVM(Tx=Rx):2% + +![Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-A30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 15 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 200 Mbps.](933151db66eefe2e64a0a4da5d37e05e_img.jpg) + +Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-A30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 15 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 200 Mbps. + +Fig 5.2.2.3-16. Throughput performance between 256QAM and 64QAM in TDL-A + +![Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 380 Mbps. A 'Cross point: 30 dB' is marked where the 64-QAM and 256-QAM curves intersect.](e046996962d6740cf050a5640e0c6b40_img.jpg) + +Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 380 Mbps. A 'Cross point: 30 dB' is marked where the 64-QAM and 256-QAM curves intersect. + +Fig 5.2.2.3-17. Throughput performance between 256QAM and 64QAM in TDL-D + +![Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, AWGN, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 400 Mbps. A 'Cross point: 22.5 dB' is marked where the 64-QAM and 256-QAM curves intersect.](52f284e10be4323639b32fdd60e463db_img.jpg) + +Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, AWGN, BW 100MHz. The graph compares 256-QAM and 64-QAM configurations. The 64-QAM configurations (blue and yellow lines) show a sharp increase in throughput starting around 10 dB SNR, reaching a plateau of approximately 340 Mbps. The 256-QAM configurations (red and green lines) show a more gradual increase, with the red line reaching a plateau of approximately 400 Mbps. A 'Cross point: 22.5 dB' is marked where the 64-QAM and 256-QAM curves intersect. + +Fig 5.2.2.3-18. Throughput performance between 256QAM and 64QAM in AWGN + +From the simulation results, the followings are observed for UL 256QAM performance gain, + +**Observation1:** In 29 GHz & TDL-A, + +There is the performance gain in MCS21 when EVM $\geq 3.0\%$ + +There is no performance gain in MCS23 + +**Observation2:** In 29 GHz & TDL-D + +There is the performance gain when EVM = 3.5% + +**Observation3:** In 29 GHz & AWGN + +There is the performance gain at a relatively low SNR when EVM = 3.5%. + +**Observation4:** In 48 GHz, + +There is no performance gain in most cases + +[R4-2218681](#) + +**Table 5.2.2.3-2 Cross throughput point (29 GHz and 39 GHz, CBW:100 MHz, EVM:Tx=Rx=3.5%)** + +**Reference: MCS24(64QAM, PUSCH Table 1, OFDM)** + +| Propagation Mode | 29 GHz | | | | 39 GHz | | | | +|----------------------------------------------------------|--------|--------|--------|--------|--------|--------|--------|--------| +| | MCS 20 | MCS 21 | MCS 22 | MCS 23 | MCS 20 | MCS 21 | MCS 22 | MCS 23 | +| TDL-A
(256 QAM, PDSCH Table 2, OFDM)
(dB) | 25.5 | 30 | N/A | N/A | N/A | N/A | N/A | N/A | +| TDL-D
(256 QAM, PDSCH Table 2, OFDM)
(dB) | 18.5 | 21 | 23 | 27 | 21 | 24 | 30 | N/A | + +**29 GHz (n257)** + +![Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-A30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM performance across various MCS and PTRS configurations.](77a781dfb114c3e2b399f876f1808cfd_img.jpg) + +CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-A30-35, BW 100MHz + +Throughput, Mbps + +SNR, dB + +Legend: + +- 256-QAM (MCS20,PDSCH2), PTRS K=2, CPE +- 256-QAM (MCS21,PDSCH2), PTRS K=2, CPE +- 256-QAM (MCS22,PDSCH2), PTRS K=2, CPE +- 256-QAM (MCS23,PDSCH2), PTRS K=2, CPE +- 64-QAM (MCS23,PUSCH1), PTRS Ng x Ns=4x4Linear +- 64-QAM (MCS24,PDSCH1), PTRS K=2, CPE + +| SNR (dB) | 256-QAM (MCS20) | 256-QAM (MCS21) | 256-QAM (MCS22) | 256-QAM (MCS23) | 64-QAM (MCS23) | 64-QAM (MCS24) | +|----------|-----------------|-----------------|-----------------|-----------------|----------------|----------------| +| 10 | 0 | 0 | 0 | 0 | 0 | 0 | +| 15 | 0 | 0 | 0 | 0 | 20 | 20 | +| 20 | 40 | 10 | 0 | 0 | 280 | 310 | +| 25 | 310 | 170 | 70 | 0 | 340 | 340 | +| 30 | 390 | 340 | 230 | 30 | 390 | 390 | +| 35 | 400 | 390 | 310 | 60 | 400 | 400 | + +Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-A30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM performance across various MCS and PTRS configurations. + +Fig5.2.2.3-19. Throughput performance between 256QAM and 64QAM in TDL-A + +![Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM performance across various MCS and PTRS configurations.](07c5a1c0fddd7da92a8427f5af840ffa_img.jpg) + +CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz + +Throughput, Mbps + +SNR, dB + +Legend: + +- 256-QAM (MCS20,PDSCH2), PTRS K=2, CPE +- 256-QAM (MCS21,PDSCH2), PTRS K=2, CPE +- 256-QAM (MCS22,PDSCH2), PTRS K=2, CPE +- 256-QAM (MCS23,PDSCH2), PTRS K=2, CPE +- 64-QAM (MCS23,PUSCH1), PTRS Ng x Ns=4x4Linear +- 64-QAM (MCS24,PDSCH1), PTRS K=2, CPE + +| SNR (dB) | 256-QAM (MCS20) | 256-QAM (MCS21) | 256-QAM (MCS22) | 256-QAM (MCS23) | 64-QAM (MCS23) | 64-QAM (MCS24) | +|----------|-----------------|-----------------|-----------------|-----------------|----------------|----------------| +| 10 | 0 | 0 | 0 | 0 | 0 | 0 | +| 15 | 0 | 0 | 0 | 0 | 0 | 330 | +| 20 | 390 | 260 | 50 | 0 | 0 | 345 | +| 25 | 405 | 415 | 430 | 210 | 0 | 430 | +| 30 | 405 | 425 | 450 | 410 | 405 | 430 | +| 35 | 405 | 425 | 450 | 440 | 405 | 430 | + +Line graph showing Throughput (Mbps) vs SNR (dB) for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz. The graph compares 256-QAM and 64-QAM performance across various MCS and PTRS configurations. + +Fig5.2.2.3-20. Throughput performance between 256QAM and 64QAM in TDL-D + +39 GHz (n260) + +![Throughput performance graph for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDLA30-35, BW 100MHz. The graph shows throughput in Mbps vs SNR in dB for various MCS and QAM configurations.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +This graph shows the throughput performance for CP-OFDM with 2x2 rank1, SCS 120 kHz, TDLA30-35, and BW 100MHz. The y-axis represents Throughput in Mbps, ranging from 0 to 350. The x-axis represents SNR in dB, ranging from 10 to 35. The legend identifies seven data series: 256-QAM (MCS20, PDSCH2), 256-QAM (MCS21, PDSCH2), 256-QAM (MCS22, PDSCH2), 256-QAM (MCS23, PDSCH2), 64-QAM (MCS23, PDSCH1), 64-QAM (MCS24, PDSCH1), and 64-QAM (MCS24, PDSCH1). The 64-QAM (MCS23, PDSCH1) series (black line with triangles) shows the highest performance, reaching a plateau of approximately 320 Mbps. The 64-QAM (MCS24, PDSCH1) series (green line with triangles) follows, reaching approximately 340 Mbps. The 256-QAM (MCS20, PDSCH2) series (red line with triangles) reaches approximately 340 Mbps. The 256-QAM (MCS21, PDSCH2) series (light green line with triangles) reaches approximately 200 Mbps. The 256-QAM (MCS22, PDSCH2) series (blue line with triangles) reaches approximately 60 Mbps. The 256-QAM (MCS23, PDSCH2) series (yellow line with triangles) remains near 0 Mbps. + +Throughput performance graph for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDLA30-35, BW 100MHz. The graph shows throughput in Mbps vs SNR in dB for various MCS and QAM configurations. + +Fig5.2.2.3-21. Throughput performance between 256QAM and 64QAM in TDL-A + +![Throughput performance graph for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz. The graph shows throughput in Mbps vs SNR in dB for various MCS and QAM configurations.](e01f9228a215e26c8b62ad471c9d7a7f_img.jpg) + +This graph shows the throughput performance for CP-OFDM with 2x2 rank1, SCS 120 kHz, TDL-D30-35, and BW 100MHz. The y-axis represents Throughput in Mbps, ranging from 0 to 450. The x-axis represents SNR in dB, ranging from 10 to 35. The legend identifies seven data series: 256-QAM (MCS20, PDSCH2), 256-QAM (MCS21, PDSCH2), 256-QAM (MCS22, PDSCH2), 256-QAM (MCS23, PDSCH2), 64-QAM (MCS23, PDSCH1), 64-QAM (MCS24, PDSCH1), and 64-QAM (MCS24, PDSCH1). The 64-QAM (MCS23, PDSCH1) series (black line with triangles) shows the highest performance, reaching a plateau of approximately 320 Mbps. The 64-QAM (MCS24, PDSCH1) series (green line with triangles) follows, reaching approximately 410 Mbps. The 256-QAM (MCS20, PDSCH2) series (red line with triangles) reaches approximately 400 Mbps. The 256-QAM (MCS21, PDSCH2) series (light green line with triangles) reaches approximately 410 Mbps. The 256-QAM (MCS22, PDSCH2) series (blue line with triangles) reaches approximately 380 Mbps. The 256-QAM (MCS23, PDSCH2) series (yellow line with triangles) reaches approximately 80 Mbps. + +Throughput performance graph for CP-OFDM, 2x2 rank1, SCS 120 kHz, TDL-D30-35, BW 100MHz. The graph shows throughput in Mbps vs SNR in dB for various MCS and QAM configurations. + +Fig5.2.2.3-22. Throughput performance between 256QAM and 64QAM in TDL-D + +**Observation 2:** In 29GHz TDL-A, the throughput gain of 256QAM is shown in MCS index 20 and 21, and operating SNR can vary from 25.5dB to 30dB depending on the MCS index number. + +**Observation 3:** In 29GHz TDL-D, the throughput gain of 256QAM is shown in MCS index 20~23, and operating SNR can vary from 18.5dB to 27dB depending on the MCS index number. + +**Observation 4:** In 39GHz TDL-A, no throughput gain of 256QAM is shown in MCS index 20~23. + +**Observation 5:** In 39GHz TDL-D, the throughput gain of 256QAM is shown in MCS index 20 ~22, and operating SNR can vary from 21dB to 30dB depending on the MCS index number. + +**Observation 6:** If the operating SNR is considered based on TDL-A, SNR of 25.5 dB or more need to be set for operation at 29GHz, however it is not practical. And N/A is shown at 39GHz, so it is also not practical. + +**Observation 7:** If the operating SNR is considered based on TDL-D with limited MCS, an operating SNR value of 18.5dB to 27dB at 29GHz may be considered, and an operating SNR value of 21dB to 30dB at 39GHz may be considered. + +#### 5.2.2.4 Simulation results from vivo + +R4-2216128 + +- 29 GHz +- TDL-A + +![Graph titled 'TDL-A BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-A configurations. The y-axis is scaled by 10^8. The graph shows multiple curves for different MCS and EVM settings, with higher MCS and lower EVM generally resulting in higher throughput at a given SNR.](a01cde7cbe4b1f1e275f4bcfce07433e_img.jpg) + +This graph displays the throughput performance for a 50MHz bandwidth configuration. The x-axis represents the SNR in dB, ranging from 14 to 34. The y-axis represents the throughput in bit/s, scaled by 10^8, ranging from 0 to 2.5. The legend identifies 16 different simulation scenarios based on 29GHz TDL-A channel, modulation (256-QAM or 64-QAM), scheme (CP-OFDM or DFT-s-OFDM), MCS index (21, 22, 23, 24), and EVM (3%, 3.5%, 4%). The curves show that throughput increases with SNR and is higher for more advanced modulation and coding schemes. + +Graph titled 'TDL-A BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-A configurations. The y-axis is scaled by 10^8. The graph shows multiple curves for different MCS and EVM settings, with higher MCS and lower EVM generally resulting in higher throughput at a given SNR. + +![Graph titled 'TDL-A BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-A configurations. The y-axis is scaled by 10^8. The graph shows multiple curves for different MCS and EVM settings, with higher MCS and lower EVM generally resulting in higher throughput at a given SNR.](2405d03fe11cb841e2b5155d3d86b1af_img.jpg) + +This graph displays the throughput performance for a 100MHz bandwidth configuration. The x-axis represents the SNR in dB, ranging from 14 to 34. The y-axis represents the throughput in bit/s, scaled by 10^8, ranging from 0 to 4.5. The legend is identical to the one in the previous graph. The overall throughput levels are significantly higher than in the 50MHz configuration, reaching up to approximately 4.2 x 10^8 bit/s at 34 dB SNR. + +Graph titled 'TDL-A BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-A configurations. The y-axis is scaled by 10^8. The graph shows multiple curves for different MCS and EVM settings, with higher MCS and lower EVM generally resulting in higher throughput at a given SNR. + +- TDL-D + +![Line graph titled 'TDL-D BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-D configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +**TDL-D BW:50MHz SCS:120kHz 2x2 Rank1** + +This graph shows the throughput performance for a 50MHz bandwidth, 120kHz subcarrier spacing, 2x2 MIMO rank 1 scenario. The y-axis represents Throughput in bit/s, scaled by $10^8$ , ranging from 0 to 2.5. The x-axis represents SNR in dB, ranging from 14 to 34. The legend identifies 20 different configurations based on modulation (256-QAM, 64-QAM), waveform (CP-OFDM, DFT-s-OFDM), MCS (21, 22, 23, 24), and EVM (3%, 3.5%, 4%). Generally, higher MCS and lower EVM result in higher throughput. CP-OFDM with 256-QAM achieves the highest throughput, reaching approximately $2.1 \times 10^8$ bit/s at 34 dB SNR. + +Line graph titled 'TDL-D BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-D configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels. + +![Line graph titled 'TDL-D BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-D configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels.](c22de2cf24282469c2a2cf1018928116_img.jpg) + +**TDL-D BW:100MHz SCS:120kHz 2x2 Rank1** + +This graph shows the throughput performance for a 100MHz bandwidth, 120kHz subcarrier spacing, 2x2 MIMO rank 1 scenario. The y-axis represents Throughput in bit/s, scaled by $10^8$ , ranging from 0 to 4.5. The x-axis represents SNR in dB, ranging from 14 to 34. The legend is identical to the top graph. Due to the doubled bandwidth, the throughput is roughly doubled compared to the 50MHz scenario. The highest throughput is achieved with CP-OFDM and 256-QAM, reaching approximately $4.1 \times 10^8$ bit/s at 34 dB SNR. + +Line graph titled 'TDL-D BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput (bit/s) vs SNR (dB) for various 29GHz TDL-D configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels. + +- AWGN + +![Two line graphs showing Throughput (bit/s) vs SNR (dB) for AWGN channels. The top graph is for BW:50MHz and the bottom graph is for BW:100MHz. Both graphs compare CP-OFDM and DFT-s-OFDM waveforms across various MCS and EVM levels at 29GHz. The 100MHz graph shows higher throughput than the 50MHz graph.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +The figure contains two line graphs. The top graph is titled 'AWGN BW:50MHz SCS:120kHz 1x2 Rank1' and the bottom graph is titled 'AWGN BW:100MHz SCS:120kHz 1x2 Rank1'. Both graphs plot 'Throughput(bit/s)' on the y-axis (scaled by 108) against 'SNR(dB)' on the x-axis. The x-axis ranges from 14 to 34 dB. The y-axis for the top graph ranges from 0 to 2.5, and for the bottom graph from 0 to 4.5. Both graphs show a sharp increase in throughput as SNR increases, eventually reaching a plateau. The bottom graph (100MHz) shows significantly higher throughput than the top graph (50MHz). The legend for both graphs lists 20 different configurations for 29GHz AWGN, including CP-OFDM and DFT-s-OFDM waveforms, MCS-21, 23, and 24, and EVM levels of 3%, 3.5%, and 4%. + +Two line graphs showing Throughput (bit/s) vs SNR (dB) for AWGN channels. The top graph is for BW:50MHz and the bottom graph is for BW:100MHz. Both graphs compare CP-OFDM and DFT-s-OFDM waveforms across various MCS and EVM levels at 29GHz. The 100MHz graph shows higher throughput than the 50MHz graph. + +The simulation results above are summarized as follows. + +**Observation 1 :** The UL 256 QAM under 29 GHz can achieve performance gain at: + +| Tx_EVM = Rx_EVM =3% | TDL-A | | TDL-D | | AWGN | | +|---------------------|---------|---------|---------|---------|---------|---------| +| | 50 MHz | 100MHz | 50 MHz | 100MHz | 50 MHz | 100MHz | +| DFT-s-OFDM | 22.0 dB | 22.8 dB | 20 dB | 21 dB | 18 dB | 19.2 dB | +| CP-OFDM | 22.5 dB | 23.8 dB | 20.3 dB | 21.5 dB | 19.2 dB | 19.7 dB | + +| Tx_EVM = Rx_EVM =3.5% | TDL-A | | TDL-D | | AWGN | | +|-----------------------|---------|---------|---------|---------|---------|---------| +| | 50 MHz | 100MHz | 50 MHz | 100MHz | 50 MHz | 100MHz | +| DFT-s-OFDM | 22.2 dB | 23.1 dB | 20.3 dB | 21.2 dB | 18.5 dB | 19.5 dB | +| CP-OFDM | 22.7 dB | 24 dB | 20.8 dB | 21.8 dB | 19.5 dB | 19.7 dB | + +| Tx_EVM = Rx_EVM =4% | TDL-A | | TDL-D | | AWGN | | +|---------------------|--------|--------|--------|--------|--------|--------| +| | 50 MHz | 100MHz | 50 MHz | 100MHz | 50 MHz | 100MHz | + +| | | | | | | | +|-------------------|---------|---------|---------|---------|---------|---------| +| DFT-s-OFDM | 22.9 dB | 23.5 dB | 20.6 dB | 21.5 dB | 19.2 dB | 19.7 dB | +| CP-OFDM | 23.2 dB | 24.7 dB | 21.2 dB | 22 dB | 19.8 dB | 19.9 dB | + +- 39 GHz +- TDL-A + +![Throughput vs SNR plot for TDL-A 50MHz bandwidth. The y-axis is Throughput (bits/s) scaled by 10^8, ranging from 0 to 2. The x-axis is SNR (dB) from 14 to 34. Multiple curves represent different MCS and EVM levels for 256-QAM and 64-QAM CP-OFDM and DFT-s-OFDM. Higher MCS and lower EVM result in higher throughput.](a96c7e19f53f2350db97a90738a6fb51_img.jpg) + +TDL-A BW:50MHz SCS:120kHz 2x2 Rank1 + +Throughput vs SNR plot for TDL-A 50MHz bandwidth. The y-axis is Throughput (bits/s) scaled by 10^8, ranging from 0 to 2. The x-axis is SNR (dB) from 14 to 34. Multiple curves represent different MCS and EVM levels for 256-QAM and 64-QAM CP-OFDM and DFT-s-OFDM. Higher MCS and lower EVM result in higher throughput. + +![Throughput vs SNR plot for TDL-A 100MHz bandwidth. The y-axis is Throughput (bits/s) scaled by 10^8, ranging from 0 to 4. The x-axis is SNR (dB) from 14 to 34. Similar to the 50MHz plot, it shows various curves for different MCS and EVM configurations. The overall throughput is higher than in the 50MHz case.](caeb46d58919c727aa9d338ae9492077_img.jpg) + +TDL-A BW:100MHz SCS:120kHz 2x2 Rank1 + +Throughput vs SNR plot for TDL-A 100MHz bandwidth. The y-axis is Throughput (bits/s) scaled by 10^8, ranging from 0 to 4. The x-axis is SNR (dB) from 14 to 34. Similar to the 50MHz plot, it shows various curves for different MCS and EVM configurations. The overall throughput is higher than in the 50MHz case. + +- TDL-D + +![Line graph titled 'TDL-D BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 39GHz configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels.](6752cee124f693bc4cebc66180f4f91f_img.jpg) + +This graph shows the throughput performance for a 50MHz bandwidth, 120kHz subcarrier spacing, 2x2 MIMO rank 1 scenario. The x-axis represents SNR(dB) from 14 to 34, and the y-axis represents Throughput(bit/s) scaled by 10^8. The legend includes 16 different configurations based on modulation (256-QAM, 64-QAM), waveform (CP-OFDM, DFT-s-OFDM), MCS (21, 23, 24), and EVM (3%, 3.5%, 4%). + +Line graph titled 'TDL-D BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 39GHz configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels. + +![Line graph titled 'TDL-D BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 39GHz configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels.](7a427d3f02cc89bd23f77068e257e90f_img.jpg) + +This graph shows the throughput performance for a 100MHz bandwidth, 120kHz subcarrier spacing, 2x2 MIMO rank 1 scenario. The x-axis represents SNR(dB) from 14 to 34, and the y-axis represents Throughput(bit/s) scaled by 10^8. The legend is identical to the top graph, showing 16 different configurations. + +Line graph titled 'TDL-D BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 39GHz configurations. The y-axis is scaled by 10^8. The graph compares CP-OFDM and DFT-s-OFDM with 256-QAM and 64-QAM modulations across different MCS and EVM levels. + +- AWGN + +![Two line graphs showing Throughput (bit/s) vs SNR (dB) for AWGN channels. The top graph is for BW:50MHz, SCS:120kHz, 1x2 Rank1, with throughput up to 2.0 x 10^8 bit/s. The bottom graph is for BW:100MHz, SCS:120kHz, 1x2 Rank1, with throughput up to 4.0 x 10^8 bit/s. Both graphs compare various 39GHz AWGN configurations (256-QAM, 64-QAM, CP-OFDM, DFT-s-OFDM) across different MCS and EVM levels (3%, 3.5%, 4%).](201de44da5d99899a8cf58eac2fa7bc9_img.jpg) + +Two line graphs showing Throughput (bit/s) vs SNR (dB) for AWGN channels. The top graph is for BW:50MHz, SCS:120kHz, 1x2 Rank1, with throughput up to 2.0 x 10^8 bit/s. The bottom graph is for BW:100MHz, SCS:120kHz, 1x2 Rank1, with throughput up to 4.0 x 10^8 bit/s. Both graphs compare various 39GHz AWGN configurations (256-QAM, 64-QAM, CP-OFDM, DFT-s-OFDM) across different MCS and EVM levels (3%, 3.5%, 4%). + +Observation 2 : The UL 256 QAM under 39 GHz can achieve performance gain at: + +| Tx_EVM = Rx_EVM =3% | TDL-A | | TDL-D | | AWGN | | +|---------------------|--------|--------|---------|---------|---------|--------| +| | 50 MHz | 100MHz | 50 MHz | 100MHz | 50 MHz | 100MHz | +| DFT-s-OFDM | 24 dB | 27 dB | 22.3 dB | 25.8 dB | 19.9 dB | 22 dB | +| CP-OFDM | 28 dB | N/A | 24 dB | N.A. | 21.5 dB | 26 dB | + +| Tx_EVM = Rx_EVM =3.5% | TDL-A | | TDL-D | | AWGN | | +|-----------------------|---------|---------|--------|--------|---------|--------| +| | 50 MHz | 100MHz | 50 MHz | 100MHz | 50 MHz | 100MHz | +| DFT-s-OFDM | 24.4 dB | 27.5 dB | 23 dB | 26 dB | 20 dB | 23 dB | +| CP-OFDM | 29.2 dB | N/A | 25 dB | N.A. | 21.8 dB | 28 dB | + +| Tx_EVM = Rx_EVM =4% | TDL-A | | TDL-D | | AWGN | | +|---------------------|---------|---------|---------|--------|---------|--------| +| | 50 MHz | 100MHz | 50 MHz | 100MHz | 50 MHz | 100MHz | +| DFT-s-OFDM | 24.8 dB | 28.2 dB | 23.3 dB | 28 dB | 20.3 dB | 23 dB | +| CP-OFDM | 34 dB | N/A | 25.8 dB | N.A. | 22 dB | 30 dB | + +- 48 GHz +- TDL-A + +![Throughput vs SNR plot for TDL-A BW:50MHz SCS:120kHz 2x2 Rank1. The y-axis is Throughput (bits) scaled by 10^8, ranging from 0 to 1.6. The x-axis is SNR (dB) from 14 to 34. The plot shows multiple curves for different modulation and coding schemes (MCS) and error vector magnitude (EVM) levels (3%, 3.5%, 4%).](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +**TDL-A BW:50MHz SCS:120kHz 2x2 Rank1** + +Throughput(bits) $\times 10^8$ + +SNR(dB) + +Legend: + +- 48GHz TDL-A 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-24 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% + +Throughput vs SNR plot for TDL-A BW:50MHz SCS:120kHz 2x2 Rank1. The y-axis is Throughput (bits) scaled by 10^8, ranging from 0 to 1.6. The x-axis is SNR (dB) from 14 to 34. The plot shows multiple curves for different modulation and coding schemes (MCS) and error vector magnitude (EVM) levels (3%, 3.5%, 4%). + +![Throughput vs SNR plot for TDL-A BW:100MHz SCS:120kHz 2x2 Rank1. The y-axis is Throughput (bits) scaled by 10^8, ranging from 0 to 3.5. The x-axis is SNR (dB) from 14 to 34. The plot shows multiple curves for different modulation and coding schemes (MCS) and error vector magnitude (EVM) levels (3%, 3.5%, 4%).](91f1a66918183ac1f85c438198c09376_img.jpg) + +**TDL-A BW:100MHz SCS:120kHz 2x2 Rank1** + +Throughput(bits) $\times 10^8$ + +SNR(dB) + +Legend: + +- 48GHz TDL-A 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3.5% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-A 256-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-A 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM CP-OFDM MCS-24 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 4% +- 48GHz TDL-A 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% + +Throughput vs SNR plot for TDL-A BW:100MHz SCS:120kHz 2x2 Rank1. The y-axis is Throughput (bits) scaled by 10^8, ranging from 0 to 3.5. The x-axis is SNR (dB) from 14 to 34. The plot shows multiple curves for different modulation and coding schemes (MCS) and error vector magnitude (EVM) levels (3%, 3.5%, 4%). + +- TDL-D + +![Line graph titled 'TDL-D BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 48GHz configurations. The y-axis is scaled by 10^8. The graph shows that higher MCS and lower EVM lead to higher throughput. CP-OFDM generally outperforms DFT-s-OFDM at the same MCS and EVM.](b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg) + +**TDL-D BW:100MHz SCS:120kHz 2x2 Rank1** + +Throughput(bit/s) $\times 10^8$ + +SNR(dB) + +Legend: + +- 48GHz TDL-D 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-24 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% + +Line graph titled 'TDL-D BW:100MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 48GHz configurations. The y-axis is scaled by 10^8. The graph shows that higher MCS and lower EVM lead to higher throughput. CP-OFDM generally outperforms DFT-s-OFDM at the same MCS and EVM. + +![Line graph titled 'TDL-D BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 48GHz configurations. The y-axis is scaled by 10^8. The graph shows that higher MCS and lower EVM lead to higher throughput. CP-OFDM generally outperforms DFT-s-OFDM at the same MCS and EVM.](7bbc8cb3417e534d01e969cbc5f3d891_img.jpg) + +**TDL-D BW:50MHz SCS:120kHz 2x2 Rank1** + +Throughput(bit/s) $\times 10^8$ + +SNR(dB) + +Legend: + +- 48GHz TDL-D 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-24 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 3.5% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 3.5% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-D 256-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-21 RANK1 EVM = 4% +- 48GHz TDL-D 256-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-23 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM CP-OFDM MCS-24 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-22 RANK1 EVM = 4% +- 48GHz TDL-D 64-QAM DFT-s-OFDM MCS-23 RANK1 EVM = 4% + +Line graph titled 'TDL-D BW:50MHz SCS:120kHz 2x2 Rank1' showing Throughput(bit/s) vs SNR(dB) for various 48GHz configurations. The y-axis is scaled by 10^8. The graph shows that higher MCS and lower EVM lead to higher throughput. CP-OFDM generally outperforms DFT-s-OFDM at the same MCS and EVM. + +- AWGN + +![Two line graphs showing Throughput (bit/s) vs SNR (dB) for 48GHz AWGN scenarios. The top graph is for BW:100MHz and the bottom graph is for BW:50MHz. Both graphs compare 256-QAM and 64-QAM with CP-OFDM and DFT-s-OFDM across various MCS and EVM levels. In both cases, 256-QAM configurations achieve significantly higher throughput than 64-QAM configurations as SNR increases.](e91633da5160c8af51a4ace6d3347f53_img.jpg) + +The figure contains two line graphs. The top graph is titled 'AWGN BW:100MHz SCS:120kHz 1x2 Rank1' and the bottom graph is titled 'AWGN BW:50MHz SCS:120kHz 1x2 Rank1'. Both graphs plot 'Throughput(bit/s)' on the y-axis (scaled by 108) against 'SNR(dB)' on the x-axis (ranging from 14 to 34). The legend for both graphs lists 24 different simulation scenarios for 48GHz AWGN, comparing 256-QAM and 64-QAM with CP-OFDM and DFT-s-OFDM across various MCS (21, 22, 23, 24) and EVM (3%, 3.5%, 4%) levels. In both graphs, the 256-QAM configurations (red and blue lines) show a sharp increase in throughput starting around 20 dB SNR, while the 64-QAM configurations (green lines) show a more gradual increase. The 256-QAM configurations consistently achieve higher throughput than the 64-QAM configurations across the entire SNR range. + +Two line graphs showing Throughput (bit/s) vs SNR (dB) for 48GHz AWGN scenarios. The top graph is for BW:100MHz and the bottom graph is for BW:50MHz. Both graphs compare 256-QAM and 64-QAM with CP-OFDM and DFT-s-OFDM across various MCS and EVM levels. In both cases, 256-QAM configurations achieve significantly higher throughput than 64-QAM configurations as SNR increases. + +**Observation 3 :** The UL 256 QAM is hard to bring performance gain under 48 GHz + +#### 5.2.2.5 Simulation results from Huawei + +R4-2216245 + +The link lever simulation results are shown in Figure 5.2.2.5-1, Figure 5.2.2.5-2 and Figure 5.2.2.5-3 for TDL-D in different frequency ranges. From the simulation results, it is shown that support 256 QAM can provide significant performance gain over 64QAM where the UE is in good propagation condition. + +![Figure 5.2.2.5-1: Throughput comparison of 256QAM and 64QAM for RANK1_29 GHz. The graph shows BLER vs SNR for 29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3% and 4%) and 64QAM719 (EVM 3% and 3.5%).](3881b390d52f27a35faedfc170916c86_img.jpg) + +29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 +Rank 1, option d + +BLER + +SNR + +Legend: +256QAM711 EVM3% (solid blue line with circles) +256QAM711 EVM4% (solid blue line with triangles) +64QAM719 EVM3 % (solid red line with circles) +64QAM719 EVM3.5 % (dashed red line with circles) + +| SNR | 256QAM711 EVM3% | 256QAM711 EVM4% | 64QAM719 EVM3 % | 64QAM719 EVM3.5 % | +|-----|-----------------|-----------------|-----------------|-------------------| +| 16 | - | - | 140 | - | +| 17 | - | - | 148 | - | +| 18 | - | - | 152 | - | +| 19 | 142 | 138 | 155 | - | +| 20 | 158 | 152 | 155 | - | +| 21 | 175 | 168 | 155 | - | +| 22 | 188 | 178 | 155 | - | +| 23 | 195 | 188 | - | - | +| 24 | 200 | 195 | - | - | +| 25 | 205 | 200 | - | - | +| 26 | 205 | 202 | - | - | + +Figure 5.2.2.5-1: Throughput comparison of 256QAM and 64QAM for RANK1\_29 GHz. The graph shows BLER vs SNR for 29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3% and 4%) and 64QAM719 (EVM 3% and 3.5%). + +Figure 5.2.2.5-1 Throughput comparison of 256QAM and 64QAM for RANK1\_29 GHz + +![Figure 5.2.2.5-2: Throughput comparison of 256QAM and 64QAM for RANK1_39GHz. The graph shows Throughput(Mbps) vs SNR for 39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3%, 3.5%, and 4%) and 64QAM719 (EVM 3%).](2c5884241ad393e03dd8e4ea25ff74a2_img.jpg) + +39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 +Rank 1, option d + +Throughput(Mbps) + +SNR + +Legend: +256QAM711 EVM3% (solid blue line with circles) +256QAM711 EVM3.5% (dashed blue line with circles) +256QAM711 EVM4% (solid blue line with triangles) +64QAM719 EVM3 % (solid red line with circles) + +| SNR | 256QAM711 EVM3% | 256QAM711 EVM3.5% | 256QAM711 EVM4% | 64QAM719 EVM3 % | +|-----|-----------------|-------------------|-----------------|-----------------| +| 15 | - | - | - | 125 | +| 16 | - | - | - | 138 | +| 17 | - | - | - | 148 | +| 18 | - | - | - | 152 | +| 19 | - | - | - | 155 | +| 20 | 145 | 140 | 138 | 155 | +| 21 | 160 | 155 | 152 | 155 | +| 22 | 175 | 170 | 165 | 155 | +| 23 | 185 | 180 | 175 | 155 | +| 24 | 195 | 190 | 185 | 155 | +| 25 | 200 | 195 | 190 | 155 | +| 26 | 202 | 198 | 195 | 155 | +| 27 | 205 | 202 | 198 | 155 | +| 28 | 205 | 202 | 198 | 155 | +| 29 | 205 | 202 | 198 | 155 | +| 30 | 205 | 202 | 198 | 155 | + +Figure 5.2.2.5-2: Throughput comparison of 256QAM and 64QAM for RANK1\_39GHz. The graph shows Throughput(Mbps) vs SNR for 39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3%, 3.5%, and 4%) and 64QAM719 (EVM 3%). + +Figure 5.2.2.5-2 Throughput comparison of 256QAM and 64QAM for RANK1\_39GHz + +![Figure 5.2.2.5-3: Throughput comparison of 256QAM and 64QAM for RANK1_48GHz. The graph shows BLER vs SNR for 48GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3% and 3.5%).](ead8d1841c351608343c98f30e5f3f07_img.jpg) + +48GHz TDL-D, FR2, CBW 50MHz, 120kHz, +2x2 Rank 1, option d + +BLER + +SNR + +Legend: +256QAM711 EVM3% (solid blue line with circles) +256QAM711 EVM3.5% (dashed blue line with circles) + +| SNR | 256QAM711 EVM3% | 256QAM711 EVM3.5% | +|-----|-----------------|-------------------| +| 15 | - | - | +| 16 | 125 | 125 | +| 17 | 135 | 135 | +| 18 | 142 | 142 | +| 19 | 148 | 148 | +| 20 | 152 | 152 | +| 21 | 155 | 155 | +| 22 | 155 | 155 | +| 23 | 155 | 155 | +| 24 | 155 | 155 | +| 25 | 175 | 170 | +| 26 | 180 | 175 | +| 27 | 185 | 180 | +| 28 | 190 | 185 | +| 29 | 192 | 188 | +| 30 | 195 | 190 | +| 31 | 195 | 190 | + +Figure 5.2.2.5-3: Throughput comparison of 256QAM and 64QAM for RANK1\_48GHz. The graph shows BLER vs SNR for 48GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3% and 3.5%). + +Figure 5.2.2.5-3 Throughput comparison of 256QAM and 64QAM for RANK1\_48GHz + +##### R4-2219144 + +The link level simulation results are shown in Figure 5.2.2.5-4, Figure 5.2.2.5-5, Figure 5.2.2.5-6 and Figure 5.2.2.5-7 for TDL-D in different frequency ranges. From the simulation results, it is shown that support 256 QAM can provide significant performance gain over 64QAM where the UE is in good propagation condition. + +![Figure 5.2.2.5-4: Throughput comparison of MCS 21 256QAM and 64QAM for RANK1_29 GHz. The chart shows BLER vs SNR for 29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3%, 3.5%, 4%) and 64QAM719 (EVM 3%, 3.5%, 4%).](671a9a08b8506e113012e056945fd8f3_img.jpg) + +29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d + +| SNR | 256QAM711 EVM3% | 256QAM711 EVM4% | 64QAM719 EVM3 % | 64QAM719 EVM3.5 % | 64QAM719 EVM4% | 256QAM711 EVM3.5% | +|-----|-----------------|-----------------|-----------------|-------------------|----------------|-------------------| +| 16 | - | - | 140 | 140 | 140 | - | +| 17 | - | - | 148 | 148 | 148 | - | +| 18 | - | - | 153 | 153 | 153 | - | +| 19 | 142 | 138 | 155 | 155 | 155 | 135 | +| 20 | 158 | 155 | 156 | 156 | 156 | 152 | +| 21 | 173 | 168 | 156 | 156 | 156 | 165 | +| 22 | 187 | 182 | - | - | - | 180 | +| 23 | 195 | 190 | - | - | - | 188 | +| 24 | 200 | 195 | - | - | - | 195 | +| 25 | 203 | 200 | - | - | - | 200 | +| 26 | 204 | 201 | - | - | - | 201 | + +Figure 5.2.2.5-4: Throughput comparison of MCS 21 256QAM and 64QAM for RANK1\_29 GHz. The chart shows BLER vs SNR for 29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM711 (EVM 3%, 3.5%, 4%) and 64QAM719 (EVM 3%, 3.5%, 4%). + +Figure 5.2.2.5-4 Throughput comparison of MCS 21 256QAM and 64QAM for RANK1\_29 GHz + +![Figure 5.2.2.5-5: Throughput comparison of MCS 23 256QAM and 64QAM for RANK1_29 GHz. The chart shows BLER vs SNR for 29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM797 (EVM 3%, 3.5%) and 64QAM772 (EVM 3%, 3.5%, 4%).](a26b4f52392209236513dd503db41339_img.jpg) + +29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d + +| SNR | 64QAM772 EVM3 % | 64QAM772 EVM3.5 % | 64QAM772 EVM4% | 256QAM797 EVM3% | 256QAM797 EVM3.5% | +|-----|-----------------|-------------------|----------------|-----------------|-------------------| +| 20 | 168 | 168 | 168 | 118 | 118 | +| 21 | 168 | 168 | 168 | 122 | 130 | +| 22 | 168 | 168 | 168 | 138 | 148 | +| 23 | 168 | 168 | 168 | 158 | 172 | +| 24 | 168 | 168 | 168 | 172 | 180 | +| 25 | 168 | 168 | 168 | 182 | 192 | +| 26 | 168 | 168 | 168 | 195 | 202 | +| 27 | 168 | 168 | 168 | 202 | 212 | +| 28 | 168 | 168 | 168 | 212 | 220 | + +Figure 5.2.2.5-5: Throughput comparison of MCS 23 256QAM and 64QAM for RANK1\_29 GHz. The chart shows BLER vs SNR for 29GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d. It compares 256QAM797 (EVM 3%, 3.5%) and 64QAM772 (EVM 3%, 3.5%, 4%). + +Figure 5.2.2.5-5 Throughput comparison of MCS 23 256QAM and 64QAM for RANK1\_29 GHz + +![Line graph titled '39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d'. The Y-axis is 'Throughput(Mbps)' ranging from 100 to 220. The X-axis is 'SNR' ranging from 15 to 29. The graph compares five configurations: 256QAM711 EVM3% (solid blue line with circles), 256QAM711 EVM3.5% (dashed blue line with circles), 256QAM711 EVM4% (solid blue line with triangles), 64QAM719 EVM3% (solid red line with circles), and 64QAM719 EVM3.5% (dashed red line with circles). The 64QAM configurations show a sharp increase in throughput from SNR 15 to 19, then plateau around 155-160 Mbps. The 256QAM configurations show a more gradual increase, starting around SNR 20, and reaching a plateau around 205 Mbps from SNR 27 onwards.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg) + +Line graph titled '39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d'. The Y-axis is 'Throughput(Mbps)' ranging from 100 to 220. The X-axis is 'SNR' ranging from 15 to 29. The graph compares five configurations: 256QAM711 EVM3% (solid blue line with circles), 256QAM711 EVM3.5% (dashed blue line with circles), 256QAM711 EVM4% (solid blue line with triangles), 64QAM719 EVM3% (solid red line with circles), and 64QAM719 EVM3.5% (dashed red line with circles). The 64QAM configurations show a sharp increase in throughput from SNR 15 to 19, then plateau around 155-160 Mbps. The 256QAM configurations show a more gradual increase, starting around SNR 20, and reaching a plateau around 205 Mbps from SNR 27 onwards. + +Figure 5.2.2.5-6 Throughput comparison of MCS 21 256QAM and 64QAM for RANK1\_39GHz + +![Line graph titled '39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d'. The Y-axis is 'BLER' ranging from 80 to 220. The X-axis is 'SNR' ranging from 20 to 28. The graph compares two configurations: 256QAM797 EVM3% (solid blue line with circles) and 256QAM797 EVM3.5% (dashed blue line with triangles). Both lines are nearly horizontal and very close to each other, starting around BLER 165 at SNR 20 and slightly increasing to approximately 168 at SNR 28.](293fb0a508d182b518ea429927dfd343_img.jpg) + +Line graph titled '39GHz TDL-D, FR2, CBW 50MHz, 120kHz, 2x2 Rank 1, option d'. The Y-axis is 'BLER' ranging from 80 to 220. The X-axis is 'SNR' ranging from 20 to 28. The graph compares two configurations: 256QAM797 EVM3% (solid blue line with circles) and 256QAM797 EVM3.5% (dashed blue line with triangles). Both lines are nearly horizontal and very close to each other, starting around BLER 165 at SNR 20 and slightly increasing to approximately 168 at SNR 28. + +Figure 5.2.2.5-7 Throughput comparison of MCS 23 256QAM and 64QAM for RANK1\_39GHz + +#### 5.2.2.6 Simulation results from Sony + +[R4-2216251](#) + +We performed simulations and compared the throughput between 64QAM and 256QAM for three different transmit and receive EVM values (3%, 3.5%, and 4%). TX EVM has been the same as RX EVM in each simulation. The simulations are done according to the agreed simulation assumptions [3]. Only Rank-1, and AWGN for 29 GHz, respectively 48 GHz, are simulated so far. 100MHz channel BW and no HARQ have been used. Phase noise is added according to option 2 in the simulation assumptions, i.e., example2, at both the UE and BS. + +- 29 GHz + +We performed simulations to address whether 256-QAM works in FR2-1 and to demonstrate its performance gain. The result is shown in Figure 5.2.2.6-1. + +![Figure 5.2.2.6-1: Throughput comparing 64QAM and 256QAM with AWGN for 29GHz, EVM 3%, 3.5% and 4%.](da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg) + +The graph shows Throughput / Mbps on the y-axis (0 to 400) versus SNR / dB on the x-axis (16 to 32). The title is 'AWGN (29 GHz / lower MCS)'. The legend indicates six data series: 256QAM, MCS21, 3.0% (blue line with circles); 256QAM, MCS21, 3.5% (blue line with circles); 256QAM, MCS21, 4.0% (blue line with triangles); 64QAM, MCS23, 3.0% (red line with circles); 64QAM, MCS23, 3.5% (red line with circles); and 64QAM, MCS23, 4.0% (red line with triangles). The 64QAM series are flat at approximately 320 Mbps. The 256QAM series show a sharp increase in throughput starting around 20 dB SNR, with the 3.0% EVM series reaching the highest throughput of about 410 Mbps at 32 dB SNR. + +| SNR / dB | 64QAM, MCS23, 3.0% (Mbps) | 256QAM, MCS21, 3.0% (Mbps) | +|----------|---------------------------|----------------------------| +| 16 | 320 | 0 | +| 18 | 320 | 0 | +| 20 | 320 | 100 | +| 22 | 320 | 280 | +| 24 | 320 | 380 | +| 26 | 320 | 400 | +| 28 | 320 | 410 | +| 30 | 320 | 410 | +| 32 | 320 | 410 | + +Figure 5.2.2.6-1: Throughput comparing 64QAM and 256QAM with AWGN for 29GHz, EVM 3%, 3.5% and 4%. + +**Figure 5.2.2.6-1 Throughput comparing 64QAM and 256QAM with AWGN for 29GHz, EVM 3%, 3.5% and 4%.** + +Figure 5.2.2.6-1 shows that throughput for 64QAM (red curve) has already saturated at an SNR level of 16dB. For 256QAM, SNR levels of 22 dB (EVM=3%), 23 dB (3.5%) and 24 dB (EVM=4%) are required to exceed the throughput performance of 64QAM. The simulations have been carried out with a simple receiver, and further studies of advanced receivers are needed to determine whether the above results could be improved. + +Observation1: For 256QAM to exceed throughput performance of 64QAM SNR levels of 22 dB (EVM=3%) to 24 dB (EVM=4%) are required. + +R4-2218753 + +We performed simulations to determine whether 256-QAM works for FR2-1 and demonstrate its performance gain. Figure 5.2.2.6-2 shows the results. + +![Figure 5.2.2.6-2: Throughput comparing 64QAM and 256QAM with AWGN for 29GHz, EVM 3.5%. The graph shows throughput in Mbps vs SNR in dB for four configurations: 256QAM (MCS21) solid blue, 256QAM (MCS23) dashed blue, 64QAM (MCS23) solid red, and 64QAM (MCS24) dashed red. 64QAM curves saturate at ~155-165 Mbps from 16 dB SNR. 256QAM (MCS21) saturates at ~205 Mbps from 21 dB SNR. 256QAM (MCS23) saturates at ~215 Mbps from 28 dB SNR.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +| SNR / dB | 256QAM (MCS21) [Mbps] | 256QAM (MCS23) [Mbps] | 64QAM (MCS23) [Mbps] | 64QAM (MCS24) [Mbps] | +|----------|-----------------------|-----------------------|----------------------|----------------------| +| 16 | 0 | 0 | 155 | 165 | +| 18 | 0 | 0 | 155 | 165 | +| 20 | 165 | 0 | 155 | 165 | +| 22 | 205 | 0 | 155 | 165 | +| 24 | 205 | 125 | 155 | 165 | +| 26 | 205 | 210 | 155 | 165 | +| 28 | 205 | 215 | 155 | 165 | + +Figure 5.2.2.6-2: Throughput comparing 64QAM and 256QAM with AWGN for 29GHz, EVM 3.5%. The graph shows throughput in Mbps vs SNR in dB for four configurations: 256QAM (MCS21) solid blue, 256QAM (MCS23) dashed blue, 64QAM (MCS23) solid red, and 64QAM (MCS24) dashed red. 64QAM curves saturate at ~155-165 Mbps from 16 dB SNR. 256QAM (MCS21) saturates at ~205 Mbps from 21 dB SNR. 256QAM (MCS23) saturates at ~215 Mbps from 28 dB SNR. + +**Figure 5.2.2.6-2 Throughput comparing 64QAM and 256QAM with AWGN for 29GHz, EVM 3.5%.** + +Figure 5.2.2.6-2 shows that throughput for 64QAM (red curves) has already saturated at an SNR level of 16dB. For 256QAM, SNR levels of 20 dB for MCS21 and 25 dB for MCS23 (EVM 3.5%) are required to exceed the throughput performance of 64QAM. To reach throughput saturation for 256QAM, SNR levels of 21dB for MCS21 and 28 dB for MCS23 are needed. + +Observation 1: For 256QAM, to reach saturation in throughput performance, SNR levels of 21dB for MCS21 and 28dB for MCS23 are needed for 29GHz. + +Simulations have also been performed for 39GHz with the same setup as for 29GHz. Figure 5.2.2.6-3 shows the results. + +![Figure 5.2.2.6-3: Throughput comparing 64QAM and 256QAM with AWGN for 39GHz, EVM 3.5%. The graph shows throughput in Mbps vs SNR in dB for the same four configurations as Figure 5.2.2.6-2. 64QAM curves saturate at ~155-165 Mbps from 16 dB SNR. 256QAM (MCS21) saturates at ~205 Mbps from 21 dB SNR. 256QAM (MCS23) saturates at ~175 Mbps from 38 dB SNR.](bf5785e70ae74c9228ac60009aeb677e_img.jpg) + +| SNR / dB | 256QAM (MCS21) [Mbps] | 256QAM (MCS23) [Mbps] | 64QAM (MCS23) [Mbps] | 64QAM (MCS24) [Mbps] | +|----------|-----------------------|-----------------------|----------------------|----------------------| +| 18 | 0 | 0 | 155 | 165 | +| 20 | 10 | 0 | 155 | 165 | +| 22 | 180 | 0 | 155 | 165 | +| 24 | 205 | 0 | 155 | 165 | +| 26 | 205 | 35 | 155 | 165 | +| 28 | 205 | 90 | 155 | 165 | +| 30 | 205 | 130 | 155 | 165 | +| 32 | 205 | 155 | 155 | 165 | +| 34 | 205 | 165 | 155 | 165 | +| 36 | 205 | 170 | 155 | 165 | +| 38 | 205 | 175 | 155 | 165 | + +Figure 5.2.2.6-3: Throughput comparing 64QAM and 256QAM with AWGN for 39GHz, EVM 3.5%. The graph shows throughput in Mbps vs SNR in dB for the same four configurations as Figure 5.2.2.6-2. 64QAM curves saturate at ~155-165 Mbps from 16 dB SNR. 256QAM (MCS21) saturates at ~205 Mbps from 21 dB SNR. 256QAM (MCS23) saturates at ~175 Mbps from 38 dB SNR. + +**Figure 5.2.2.6-3 Throughput comparing 64QAM and 256QAM with AWGN for 39GHz, EVM 3.5%.** + +Figure 5.2.2.6-3 shows 256QAM performance for 39GHz compared to 64QAM. SNR levels of 21.5dB are needed to exceed the throughput performance of 64QAM for MCS21. For MCS23, an SNR of 36dB is required to exceed the throughput performance of 64QAM. An SNR level of 24dB is needed to reach throughput saturation for 256QAM for MCS21. For MCS23, we didn't see saturation within the simulated SNR range. + +Observation 2: For 256QAM, to reach saturation in throughput performance, SNR levels of 24dB for MCS21 are needed for 39GHz. To exceed the performance of 64QAM, an SNR of 21.5dBm is required. + +#### 5.2.2.7 Simulation results from Xiaomi + +R4-2216350 + +We compare the UL 256QAM and UL 64QAM performance under different channel conditions and carrier frequencies to determine whether UL 256QAM can provide gains over UL 64QAM for FR2-1. For all simulation, we assumed 50MHz channel bandwidth with 120kHz SCS and phase noise model of example2 (UE) + example2(BS) based on above simulation assumptions. + +- CP-OFDM +- 29GHz + +![Figure 5.2.2.7-1: Throughput performance for 29GHz under AWGN, CP-OFDM. The graph shows throughput (bits) on the y-axis (0 to 2.5 x 10^6) versus SNR (dB) on the x-axis (16 to 28). It compares 64QAM and 256QAM for MCS21, 23, and 24. 256QAM generally achieves higher throughput than 64QAM at the same MCS and SNR, especially at higher SNR values.](0881dba5224c95f05eeaf56c545ebddd_img.jpg) + +Figure 5.2.2.7-1: Throughput performance for 29GHz under AWGN, CP-OFDM. The graph shows throughput (bits) on the y-axis (0 to 2.5 x 10^6) versus SNR (dB) on the x-axis (16 to 28). It compares 64QAM and 256QAM for MCS21, 23, and 24. 256QAM generally achieves higher throughput than 64QAM at the same MCS and SNR, especially at higher SNR values. + +Figure 5.2.2.7-1 Throughput performance for 29GHz under AWGN, CP-OFDM + +![Figure 5.2.2.7-2: Throughput performance for 29GHz under TDL-D, CP-OFDM. The graph shows throughput (bits) on the y-axis (0 to 2.5 x 10^6) versus SNR (dB) on the x-axis (16 to 28). It compares 64QAM and 256QAM for MCS21, 23, and 24. In this channel condition, the performance gap between 64QAM and 256QAM is narrower than in the AWGN case, with some 64QAM configurations achieving similar or slightly higher throughput than 256QAM at lower SNR levels.](87c8b2afac072caf8623e534f71fcfa1_img.jpg) + +Figure 5.2.2.7-2: Throughput performance for 29GHz under TDL-D, CP-OFDM. The graph shows throughput (bits) on the y-axis (0 to 2.5 x 10^6) versus SNR (dB) on the x-axis (16 to 28). It compares 64QAM and 256QAM for MCS21, 23, and 24. In this channel condition, the performance gap between 64QAM and 256QAM is narrower than in the AWGN case, with some 64QAM configurations achieving similar or slightly higher throughput than 256QAM at lower SNR levels. + +Figure 5.2.2.7-2 Throughput performance for 29GHz under TDL-D, CP-OFDM + +![Figure 5.2.2.7-3: Throughput performance for 29GHz under TDL-A, CP-OFDM. The graph shows throughput (bps x 10^8) vs SNR (dB) ranging from 16 to 28 dB. The title is 'TDL-A 29G CP-OFDM BW:50MHz SCS:120kHz 2x2 Rank1'. The legend includes various 64QAM and 256QAM configurations with different TxEVM and RxEVM percentages (e.g., 3%, 3.5%, 4%). Most curves show a steady increase in throughput as SNR increases, with some reaching a plateau around 1.5 to 2.0 x 10^8 bps.](c742b64169a38a7f3f990172019878c8_img.jpg) + +Figure 5.2.2.7-3: Throughput performance for 29GHz under TDL-A, CP-OFDM. The graph shows throughput (bps x 10^8) vs SNR (dB) ranging from 16 to 28 dB. The title is 'TDL-A 29G CP-OFDM BW:50MHz SCS:120kHz 2x2 Rank1'. The legend includes various 64QAM and 256QAM configurations with different TxEVM and RxEVM percentages (e.g., 3%, 3.5%, 4%). Most curves show a steady increase in throughput as SNR increases, with some reaching a plateau around 1.5 to 2.0 x 10^8 bps. + +**Figure 5.2.2.7-3 Throughput performance for 29GHz under TDL-A, CP-OFDM** + +- 39GHz + +![Figure 5.2.2.7-4: Throughput performance for 39GHz under AWGN, CP-OFDM. The graph shows throughput (bps x 10^8) vs SNR (dB) ranging from 16 to 26 dB. The title is 'AWGN 39G CP-OFDM BW:50MHz SCS:120kHz 1x2 Rank1'. The legend lists configurations for 64QAM and 256QAM with varying EVM. In this AWGN channel, several configurations reach their maximum throughput plateau (around 1.6 x 10^8 bps) very quickly, while others show a sharp transition between 18 and 22 dB SNR.](5f7d01d7025c1fb35ed8adf53f9fd8e5_img.jpg) + +Figure 5.2.2.7-4: Throughput performance for 39GHz under AWGN, CP-OFDM. The graph shows throughput (bps x 10^8) vs SNR (dB) ranging from 16 to 26 dB. The title is 'AWGN 39G CP-OFDM BW:50MHz SCS:120kHz 1x2 Rank1'. The legend lists configurations for 64QAM and 256QAM with varying EVM. In this AWGN channel, several configurations reach their maximum throughput plateau (around 1.6 x 10^8 bps) very quickly, while others show a sharp transition between 18 and 22 dB SNR. + +**Figure 5.2.2.7-4 Throughput performance for 39GHz under AWGN, CP-OFDM** + +![Figure 5.2.2.7-5: Throughput performance for 39GHz under TDL-D, CP-OFDM. The graph shows throughput (bps x 10^8) vs SNR (dB) ranging from 16 to 28 dB. The title is 'TDL-D 39G CP-OFDM BW:50MHz SCS:120kHz 2x2 Rank1'. The y-axis scale goes up to 2.2 x 10^8. The legend includes 64QAM and 256QAM MCS levels with different EVM values. The curves show a gradual increase in throughput with SNR, with peak values reaching between 1.4 and 1.8 x 10^8 bps at 28 dB SNR.](26ba4afd729749f66bf8314d9d676041_img.jpg) + +Figure 5.2.2.7-5: Throughput performance for 39GHz under TDL-D, CP-OFDM. The graph shows throughput (bps x 10^8) vs SNR (dB) ranging from 16 to 28 dB. The title is 'TDL-D 39G CP-OFDM BW:50MHz SCS:120kHz 2x2 Rank1'. The y-axis scale goes up to 2.2 x 10^8. The legend includes 64QAM and 256QAM MCS levels with different EVM values. The curves show a gradual increase in throughput with SNR, with peak values reaching between 1.4 and 1.8 x 10^8 bps at 28 dB SNR. + +**Figure 5.2.2.7-5 Throughput performance for 39GHz under TDL-D, CP-OFDM** + +![Figure 5.2.2.7-6: Throughput performance for 39GHz under TDL-A, CP-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS levels and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 28 dB SNR. The legend includes 64QAM and 256QAM MCS23-31 with TxEVM 3.5% and 4%.](509a054727400bc6d424bb2a559b8cfc_img.jpg) + +This graph shows the throughput performance for 39GHz under TDL-A channel conditions using CP-OFDM. The x-axis represents the SNR in dB, ranging from 16 to 28. The y-axis represents the throughput in bps, scaled by 108. The legend indicates various Modulation and Coding Scheme (MCS) levels (MCS23 to MCS31) for both 64QAM and 256QAM, with two Transmit Error Vector Magnitude (TxEVM) levels: 3.5% and 4%. The 64QAM configurations generally achieve higher throughput than the 256QAM configurations. The throughput increases with SNR and reaches a plateau for higher SNR values. The 256QAM MCS31 3.5% TxEVM configuration shows the highest performance, reaching approximately 1.7 x 108 bps at 28 dB SNR. + +Figure 5.2.2.7-6: Throughput performance for 39GHz under TDL-A, CP-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS levels and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 28 dB SNR. The legend includes 64QAM and 256QAM MCS23-31 with TxEVM 3.5% and 4%. + +Figure 5.2.2.7-6 Throughput performance for 39GHz under TDL-A, CP-OFDM + +- 48GHz + +![Figure 5.2.2.7-7: Throughput performance for 48GHz under AWGN, CP-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS levels and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 28 dB SNR. The legend includes 64QAM and 256QAM MCS23-31 with TxEVM 3.5% and 4%.](16f235bb59e360d10bb35e523d3946b2_img.jpg) + +This graph shows the throughput performance for 48GHz under AWGN channel conditions using CP-OFDM. The x-axis represents the SNR in dB, ranging from 16 to 28. The y-axis represents the throughput in bps, scaled by 108. The legend is identical to Figure 5.2.2.7-6, showing 64QAM and 256QAM MCS23-31 with TxEVM 3.5% and 4%. In the AWGN channel, the performance of the different configurations is more distinct than in the TDL-A channel. The 64QAM MCS31 3.5% TxEVM configuration again shows the highest performance, reaching approximately 1.7 x 108 bps at 28 dB SNR. The 256QAM configurations show lower throughput, with the 256QAM MCS31 3.5% TxEVM configuration reaching approximately 1.5 x 108 bps at 28 dB SNR. + +Figure 5.2.2.7-7: Throughput performance for 48GHz under AWGN, CP-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS levels and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 28 dB SNR. The legend includes 64QAM and 256QAM MCS23-31 with TxEVM 3.5% and 4%. + +Figure 5.2.2.7-7 Throughput performance for 48GHz under AWGN, CP-OFDM + +- DFT-s-OFDM + +- 29GHz + +![Line graph showing Throughput (bps) vs SNR (dB) for AWGN 29G DFT-s-OFDM. The graph shows performance for various MCS levels (22, 23, 24) and TUEVM configurations (3%, 3.5%, 4%) under Rank 1. Throughput increases sharply with SNR, reaching a plateau around 2.0 x 10^5 bps for higher SNR values.](835ebc0e9ec15eea8eadc15448249226_img.jpg) + +Figure 5.2.2.7-8: Throughput performance for 29GHz under AWGN, DFT-s-OFDM. The graph plots Throughput (bps) on the y-axis (scaled by 10^5) against SNR (dB) on the x-axis (16 to 28). The legend identifies 12 series: 64QAM MCS22-3% TUEVM-3% REVM, 64QAM MCS22-3.5% TUEVM-3.5% REVM, 64QAM MCS22-4% TUEVM-4% REVM, 256QAM MCS21-3% TUEVM-3% REVM, 256QAM MCS21-3.5% TUEVM-3.5% REVM, 256QAM MCS21-4% TUEVM-4% REVM, 64QAM MCS23-3% TUEVM-3% REVM, 64QAM MCS23-3.5% TUEVM-3.5% REVM, 64QAM MCS23-4% TUEVM-4% REVM, 256QAM MCS23-3% TUEVM-3% REVM, 256QAM MCS23-3.5% TUEVM-3.5% REVM, and 256QAM MCS23-4% TUEVM-4% REVM. The 256QAM series show a sharp increase in throughput starting around 18 dB SNR, while the 64QAM series show a more gradual increase, plateauing at lower throughput values. + +Line graph showing Throughput (bps) vs SNR (dB) for AWGN 29G DFT-s-OFDM. The graph shows performance for various MCS levels (22, 23, 24) and TUEVM configurations (3%, 3.5%, 4%) under Rank 1. Throughput increases sharply with SNR, reaching a plateau around 2.0 x 10^5 bps for higher SNR values. + +Figure 5.2.2.7-8 Throughput performance for 29GHz under AWGN, DFT-s-OFDM + +![Line graph showing Throughput (bps) vs SNR (dB) for TDL-D 29G DFT-s-OFDM. The graph shows performance for various MCS levels (22, 23, 24) and TUEVM configurations (3%, 3.5%, 4%) under Rank 2. Throughput increases with SNR, but the overall performance is lower than in the AWGN case, with a more gradual increase and lower plateau values.](1383c500c5d34fbc2c535226f0f64fa9_img.jpg) + +Figure 5.2.2.7-9: Throughput performance for 29GHz under TDL-D, DFT-s-OFDM. The graph plots Throughput (bps) on the y-axis (scaled by 10^5) against SNR (dB) on the x-axis (16 to 28). The legend is identical to Figure 5.2.2.7-8. The throughput performance is generally lower than in the AWGN case, with a more gradual increase and lower plateau values. The 256QAM series reach a plateau around 1.8 x 10^5 bps, while the 64QAM series plateau around 1.5 x 10^5 bps. + +Line graph showing Throughput (bps) vs SNR (dB) for TDL-D 29G DFT-s-OFDM. The graph shows performance for various MCS levels (22, 23, 24) and TUEVM configurations (3%, 3.5%, 4%) under Rank 2. Throughput increases with SNR, but the overall performance is lower than in the AWGN case, with a more gradual increase and lower plateau values. + +Figure 5.2.2.7-9 Throughput performance for 29GHz under TDL-D, DFT-s-OFDM + +![Figure 5.2.2.7-10: Throughput performance for 29GHz under TDL-A, DFT-s-OFDM. The graph shows throughput (bits) vs SNR (dB) for various MCS and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 28 dB SNR. The legend lists 12 configurations: 64QAM-MCS22-3% TxEVM-3% RxEVM, 64QAM-MCS22-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS22-4% TxEVM-4% RxEVM, 256QAM-MCS21-3% TxEVM-3% RxEVM, 256QAM-MCS21-3.5% TxEVM-3.5% RxEVM, 256QAM-MCS21-4% TxEVM-4% RxEVM, 64QAM-MCS23-3% TxEVM-3% RxEVM, 64QAM-MCS23-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS23-4% TxEVM-4% RxEVM, 256QAM-MCS23-3% TxEVM-3% RxEVM, 256QAM-MCS23-3.5% TxEVM-3.5% RxEVM, and 256QAM-MCS23-4% TxEVM-4% RxEVM.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +Figure 5.2.2.7-10: Throughput performance for 29GHz under TDL-A, DFT-s-OFDM. The graph shows throughput (bits) vs SNR (dB) for various MCS and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 28 dB SNR. The legend lists 12 configurations: 64QAM-MCS22-3% TxEVM-3% RxEVM, 64QAM-MCS22-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS22-4% TxEVM-4% RxEVM, 256QAM-MCS21-3% TxEVM-3% RxEVM, 256QAM-MCS21-3.5% TxEVM-3.5% RxEVM, 256QAM-MCS21-4% TxEVM-4% RxEVM, 64QAM-MCS23-3% TxEVM-3% RxEVM, 64QAM-MCS23-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS23-4% TxEVM-4% RxEVM, 256QAM-MCS23-3% TxEVM-3% RxEVM, 256QAM-MCS23-3.5% TxEVM-3.5% RxEVM, and 256QAM-MCS23-4% TxEVM-4% RxEVM. + +Figure 5.2.2.7-10 Throughput performance for 29GHz under TDL-A, DFT-s-OFDM + +- 39GHz + +![Figure 5.2.2.7-11: Throughput performance for 39GHz under AWGN, DFT-s-OFDM. The graph shows throughput (bits) vs SNR (dB) for various MCS and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 26 dB SNR. The legend lists 12 configurations: 64QAM-MCS22-3% TxEVM-3% RxEVM, 64QAM-MCS22-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS22-4% TxEVM-4% RxEVM, 256QAM-MCS21-3% TxEVM-3% RxEVM, 256QAM-MCS21-3.5% TxEVM-3.5% RxEVM, 256QAM-MCS21-4% TxEVM-4% RxEVM, 64QAM-MCS23-3% TxEVM-3% RxEVM, 64QAM-MCS23-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS23-4% TxEVM-4% RxEVM, 256QAM-MCS23-3% TxEVM-3% RxEVM, 256QAM-MCS23-3.5% TxEVM-3.5% RxEVM, and 256QAM-MCS23-4% TxEVM-4% RxEVM.](524cc6038f81916add4e259efa7e780b_img.jpg) + +Figure 5.2.2.7-11: Throughput performance for 39GHz under AWGN, DFT-s-OFDM. The graph shows throughput (bits) vs SNR (dB) for various MCS and TxEVM configurations. The y-axis is scaled by 10^8. The x-axis ranges from 16 to 26 dB SNR. The legend lists 12 configurations: 64QAM-MCS22-3% TxEVM-3% RxEVM, 64QAM-MCS22-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS22-4% TxEVM-4% RxEVM, 256QAM-MCS21-3% TxEVM-3% RxEVM, 256QAM-MCS21-3.5% TxEVM-3.5% RxEVM, 256QAM-MCS21-4% TxEVM-4% RxEVM, 64QAM-MCS23-3% TxEVM-3% RxEVM, 64QAM-MCS23-3.5% TxEVM-3.5% RxEVM, 64QAM-MCS23-4% TxEVM-4% RxEVM, 256QAM-MCS23-3% TxEVM-3% RxEVM, 256QAM-MCS23-3.5% TxEVM-3.5% RxEVM, and 256QAM-MCS23-4% TxEVM-4% RxEVM. + +Figure 5.2.2.7-11 Throughput performance for 39GHz under AWGN, DFT-s-OFDM + +![Figure 5.2.2.7-12: Throughput performance for 39GHz under TDL-D, DFT-s-OFDM. The graph plots Throughput (bps) on the y-axis (scaled by 10^8) against SNR (dB) on the x-axis ranging from 16 to 26. Multiple data series are shown for different MCS and EVM combinations. The legend includes: 64QAM-MCS22-3%TxEVM+3%RxEVM, 64QAM-MCS22-3.5%TxEVM+3.5%RxEVM, 64QAM-MCS22-4%TxEVM+4%RxEVM, 256QAM-MCS21-3%TxEVM+3%RxEVM, 256QAM-MCS21-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS21-4%TxEVM+4%RxEVM, 64QAM-MCS23-3%TxEVM+3%RxEVM, 64QAM-MCS23-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS23-3%TxEVM+3%RxEVM, 256QAM-MCS23-4%TxEVM+4%RxEVM.](7c0a9511fa02b6c2c125ff5be465186e_img.jpg) + +Figure 5.2.2.7-12: Throughput performance for 39GHz under TDL-D, DFT-s-OFDM. The graph plots Throughput (bps) on the y-axis (scaled by 10^8) against SNR (dB) on the x-axis ranging from 16 to 26. Multiple data series are shown for different MCS and EVM combinations. The legend includes: 64QAM-MCS22-3%TxEVM+3%RxEVM, 64QAM-MCS22-3.5%TxEVM+3.5%RxEVM, 64QAM-MCS22-4%TxEVM+4%RxEVM, 256QAM-MCS21-3%TxEVM+3%RxEVM, 256QAM-MCS21-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS21-4%TxEVM+4%RxEVM, 64QAM-MCS23-3%TxEVM+3%RxEVM, 64QAM-MCS23-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS23-3%TxEVM+3%RxEVM, 256QAM-MCS23-4%TxEVM+4%RxEVM. + +**Figure 5.2.2.7-12 Throughput performance for 39GHz under TDL-D, DFT-s-OFDM** + +![Figure 5.2.2.7-13: Throughput performance for 39GHz under TDL-A, DFT-s-OFDM. The graph plots Throughput (bps) on the y-axis (scaled by 10^8) against SNR (dB) on the x-axis ranging from 16 to 26. The performance curves show lower throughput compared to TDL-D for the same SNR. The legend includes the same MCS and EVM configurations as Figure 5.2.2.7-12: 64QAM-MCS22-3%TxEVM+3%RxEVM, 64QAM-MCS22-3.5%TxEVM+3.5%RxEVM, 64QAM-MCS22-4%TxEVM+4%RxEVM, 256QAM-MCS21-3%TxEVM+3%RxEVM, 256QAM-MCS21-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS21-4%TxEVM+4%RxEVM, 64QAM-MCS23-3%TxEVM+3%RxEVM, 64QAM-MCS23-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS23-3%TxEVM+3%RxEVM, 256QAM-MCS23-4%TxEVM+4%RxEVM.](bfde27036f8cdbc8ed561e547f0a9483_img.jpg) + +Figure 5.2.2.7-13: Throughput performance for 39GHz under TDL-A, DFT-s-OFDM. The graph plots Throughput (bps) on the y-axis (scaled by 10^8) against SNR (dB) on the x-axis ranging from 16 to 26. The performance curves show lower throughput compared to TDL-D for the same SNR. The legend includes the same MCS and EVM configurations as Figure 5.2.2.7-12: 64QAM-MCS22-3%TxEVM+3%RxEVM, 64QAM-MCS22-3.5%TxEVM+3.5%RxEVM, 64QAM-MCS22-4%TxEVM+4%RxEVM, 256QAM-MCS21-3%TxEVM+3%RxEVM, 256QAM-MCS21-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS21-4%TxEVM+4%RxEVM, 64QAM-MCS23-3%TxEVM+3%RxEVM, 64QAM-MCS23-3.5%TxEVM+3.5%RxEVM, 256QAM-MCS23-3%TxEVM+3%RxEVM, 256QAM-MCS23-4%TxEVM+4%RxEVM. + +**Figure 5.2.2.7-13 Throughput performance for 39GHz under TDL-A, DFT-s-OFDM** + +- 48GHz + +![Figure 5.2.2.7-14: Throughput performance for 39GHz under TDL-A, DFT-s-OFDM. The graph shows Throughput (Gbps) on the y-axis (0 to 2) versus SNR (dB) on the x-axis (16 to 26). The legend indicates various configurations: 64QAM MCS22-3% TUEVM+3% REVM, 64QAM MCS23-3.5% TUEVM+3.5% REVM, 64QAM MCS23-4% TUEVM+4% REVM, 256QAM MCS21-3% TUEVM+3% REVM, 256QAM MCS21-3.5% TUEVM+3.5% REVM, 256QAM MCS21-4% TUEVM+4% REVM, 256QAM MCS23-3% TUEVM+3% REVM, 256QAM MCS23-3.5% TUEVM+3.5% REVM, 256QAM MCS23-4% TUEVM+4% REVM, 256QAM MCS23-3% TUEVM+3.5% REVM, 256QAM MCS23-3.5% TUEVM+4% REVM. The 256QAM configurations show significantly higher throughput than the 64QAM configurations as SNR increases.](f455955c4bc84005728b4138f19098dc_img.jpg) + +Figure 5.2.2.7-14: Throughput performance for 39GHz under TDL-A, DFT-s-OFDM. The graph shows Throughput (Gbps) on the y-axis (0 to 2) versus SNR (dB) on the x-axis (16 to 26). The legend indicates various configurations: 64QAM MCS22-3% TUEVM+3% REVM, 64QAM MCS23-3.5% TUEVM+3.5% REVM, 64QAM MCS23-4% TUEVM+4% REVM, 256QAM MCS21-3% TUEVM+3% REVM, 256QAM MCS21-3.5% TUEVM+3.5% REVM, 256QAM MCS21-4% TUEVM+4% REVM, 256QAM MCS23-3% TUEVM+3% REVM, 256QAM MCS23-3.5% TUEVM+3.5% REVM, 256QAM MCS23-4% TUEVM+4% REVM, 256QAM MCS23-3% TUEVM+3.5% REVM, 256QAM MCS23-3.5% TUEVM+4% REVM. The 256QAM configurations show significantly higher throughput than the 64QAM configurations as SNR increases. + +Figure 5.2.2.7-14 Throughput performance for 39GHz under TDL-A, DFT-s-OFDM + +From the simulation results, table 5.2.2.7-1 summary the SNR required to achieve gains for 256QAM compare to 64QAM: + +Table 5.2.2.7-1 UL 256QAM required SNR to achieve gains compare to 64QAM + +| Parameters for UL 256QAM | | | SNR required to achieve gains for 256QAM [dB] | | | | | | | | | +|--------------------------|-------|----------|-----------------------------------------------|---------------|-----------|-----------|---------------|-----------|-------|---------------|-----------| +| | | | 29GHz | | | 39GHz | | | 48GHz | | | +| Channel | MCS | | 3%
+3% | 3.5%
+3.5% | 4%
+4% | 3%
+3% | 3.5%
+3.5% | 4%
+4% | 3%+3% | 3.5%
+3.5% | 4%
+4% | +| AWGN
1x2
RANK1 | MCS21 | CP-OFDM | 19.3 | 19.5 | 19.6 | 20 | 21.5 | 22 | 24 | 25 | 28 | +| | | DFT-OFDM | 19.3 | 19.5 | 19.6 | 20.1 | 21.1 | 21.7 | 22.5 | 23.6 | 25 | +| | MCS23 | CP-OFDM | 23 | 23.5 | 25.5 | NA | NA | NA | NA | NA | NA | +| | | DFT-OFDM | 22.5 | 23.5 | 24.7 | NA | NA | NA | NA | NA | NA | +| TDL-D
2x2
RANK2 | MCS21 | CP-OFDM | 21.8 | 22.5 | 23.1 | 24.1 | 25.2 | 28 | - | - | - | +| | | DFT-OFDM | 22 | 22.6 | 23.3 | 24.1 | 25.7 | 28 | - | - | - | +| | MCS23 | CP-OFDM | 25.8 | 27.3 | NA | NA | NA | NA | - | - | - | +| | | DFT-OFDM | 25.7 | 26.1 | 28 | NA | NA | NA | - | - | - | +| TDL-A
2x2
RANK2 | MCS21 | CP-OFDM | 21.8 | 22.7 | 23.8 | 25.2 | 26.7 | NA | - | - | - | +| | | DFT-OFDM | 21.8 | 22.7 | 23.8 | NA | NA | NA | - | - | - | +| | MCS23 | CP-OFDM | 26.5 | 28 | NA | NA | NA | NA | - | - | - | +| | | DFT-OFDM | 25.8 | 27.5 | NA | NA | NA | NA | - | - | - | + +- means the related simulations haven't been done due to time limit. + +Observation: + +And it is shown that supporting UL 256 QAM can provide significant performance gain over UL 64QAM for 3.5% EVM. + +For AWGN channel with 3.5% Tx EVM+3.5% Rx EVM, a SNR of >19.5 dB is needed for 29GHz, a SNR of >21.1 dB is needed for 39GHz and a SNR of >23.6 dB is needed for 48GHz. + +For TDL-A and TDL-D fading channel with 3.5% Tx EVM+3.5% Rx EVM, a SNR of >22.5 dB is needed for 29GHz, a SNR of >25.2 dB is needed for 39GHz, due to time limit, the related simulation for 48GHz haven't been done. + +##### R4-2219075 + +We further compare the UL 256QAM and UL 64QAM performance under different channel conditions and carrier frequencies to determine whether UL 256QAM can provide gains over UL 64QAM for 48GHz. For all simulations, we assumed 50MHz channel bandwidth with 120kHz SCS and phase noise model of example2 (UE) + example2(BS) based on the agreed simulation assumptions [2]. + +##### CP-OFDM + +![Figure 5.2.2.7-15: Throughput performance for 48GHz under AWGN, CP-OFDM. The graph shows throughput (bps) on the y-axis (scaled by 10^8) versus SNR (dB) on the x-axis (16 to 26). Multiple curves represent different modulation and coding schemes (MCS) for 64QAM and 256QAM with various Tx and Rx EVM levels. 256QAM curves show higher throughput than 64QAM curves at higher SNR values.](3579cd5f679b4532a727bfacc823ea7d_img.jpg) + +Figure 5.2.2.7-15: Throughput performance for 48GHz under AWGN, CP-OFDM. The graph shows throughput (bps) on the y-axis (scaled by 10^8) versus SNR (dB) on the x-axis (16 to 26). Multiple curves represent different modulation and coding schemes (MCS) for 64QAM and 256QAM with various Tx and Rx EVM levels. 256QAM curves show higher throughput than 64QAM curves at higher SNR values. + +Figure 5.2.2.7-15 Throughput performance for 48GHz under AWGN, CP-OFDM + +![Figure 5.2.2.7-16: Throughput performance for 48GHz under TDL-D, CP-OFDM. The graph shows throughput (bps) on the y-axis (scaled by 10^8) versus SNR (dB) on the x-axis (16 to 26). Multiple curves represent different modulation and coding schemes (MCS) for 64QAM and 256QAM with various Tx and Rx EVM levels. The performance is generally lower than in the AWGN case, but the relative ranking of 256QAM over 64QAM remains.](52727a1fec40059356483552cc6dba2b_img.jpg) + +Figure 5.2.2.7-16: Throughput performance for 48GHz under TDL-D, CP-OFDM. The graph shows throughput (bps) on the y-axis (scaled by 10^8) versus SNR (dB) on the x-axis (16 to 26). Multiple curves represent different modulation and coding schemes (MCS) for 64QAM and 256QAM with various Tx and Rx EVM levels. The performance is generally lower than in the AWGN case, but the relative ranking of 256QAM over 64QAM remains. + +Figure 5.2.2.7-16 Throughput performance for 48GHz under TDL-D, CP-OFDM + +![Figure 5.2.2.7-17: Throughput performance for 48GHz under TDL-D, CP-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. Throughput increases with SNR and plateaus around 1.6-1.7 x 10^8 bps for most configurations.](b90dcb4c35f1875e19ca312a6cf4adae_img.jpg) + +This line graph shows the throughput performance for 48GHz under TDL-D, CP-OFDM. The x-axis represents SNR (dB) from 16 to 26. The y-axis represents Throughput(bps) from 0 to 2.2 x 108. The legend lists 12 configurations: 64QAM-MCS23-3%TxEVM-3%RxEVM, 64QAM-MCS23-3%TxEVM-3.5%RxEVM, 64QAM-MCS23-4%TxEVM-4%RxEVM, 256QAM-MCS21-3%TxEVM-3%RxEVM, 256QAM-MCS21-3.5%TxEVM-3.5%RxEVM, 256QAM-MCS21-4%TxEVM-4%RxEVM, 64QAM-MCS24-3%TxEVM-3%RxEVM, 64QAM-MCS24-3%TxEVM-3.5%RxEVM, 64QAM-MCS24-4%TxEVM-4%RxEVM, 256QAM-MCS23-3%TxEVM-3%RxEVM, 256QAM-MCS23-3.5%TxEVM-3.5%RxEVM, and 256QAM-MCS23-4%TxEVM-4%RxEVM. Most curves show a sharp increase in throughput between 16 dB and 22 dB SNR, then plateau. The 256QAM configurations (red lines) plateau at lower throughput values (around 0.7-1.1 x 108 bps) compared to the 64QAM and 256QAM-MCS23 configurations (blue and green lines) which plateau around 1.6-1.7 x 108 bps. The 256QAM-MCS23-4%TxEVM-4%RxEVM configuration (purple line) remains near zero throughout. + +Figure 5.2.2.7-17: Throughput performance for 48GHz under TDL-D, CP-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. Throughput increases with SNR and plateaus around 1.6-1.7 x 10^8 bps for most configurations. + +Figure 5.2.2.7-17 Throughput performance for 48GHz under TDL-D, CP-OFDM + +DFT-s-OFDM + +![Figure 5.2.2.7-18: Throughput performance for 48GHz under AWGN, DFT-s-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. Throughput increases with SNR and plateaus around 1.6-1.7 x 10^8 bps for most configurations.](9b00c87003f634db9c30ca1d94fd932d_img.jpg) + +This line graph shows the throughput performance for 48GHz under AWGN, DFT-s-OFDM. The x-axis represents SNR (dB) from 16 to 26. The y-axis represents Throughput(bps) from 0 to 2 x 108. The legend is identical to Figure 5.2.2.7-17. In this scenario, the throughput for most configurations remains low (below 0.5 x 108 bps) until an SNR of approximately 20 dB. Above 20 dB, the throughput increases sharply. The 256QAM configurations (red lines) reach higher throughput values (up to 1.9 x 108 bps) than the 64QAM configurations (green lines, plateauing around 1.6 x 108 bps). The 256QAM-MCS23-4%TxEVM-4%RxEVM configuration (purple line) shows a slight increase at high SNR, reaching about 0.2 x 108 bps at 26 dB. + +Figure 5.2.2.7-18: Throughput performance for 48GHz under AWGN, DFT-s-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. Throughput increases with SNR and plateaus around 1.6-1.7 x 10^8 bps for most configurations. + +Figure 5.2.2.7-18 Throughput performance for 48GHz under AWGN, DFT-s-OFDM + +![Figure 5.2.2.7-19: Throughput performance for 48GHz under TDL-D, DFT-s-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. The legend includes 64QAM and 256QAM for MCS21, 23, and 24 with 3%, 3.5%, and 4% TxEVM. Performance generally increases with SNR, with 64QAM configurations reaching higher throughput plateaus (around 1.5-1.6 x 10^8 bps) compared to 256QAM configurations (around 1.0-1.3 x 10^8 bps).](9e4179ffe4701bec67534299c4935049_img.jpg) + +Figure 5.2.2.7-19: Throughput performance for 48GHz under TDL-D, DFT-s-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. The legend includes 64QAM and 256QAM for MCS21, 23, and 24 with 3%, 3.5%, and 4% TxEVM. Performance generally increases with SNR, with 64QAM configurations reaching higher throughput plateaus (around 1.5-1.6 x 10^8 bps) compared to 256QAM configurations (around 1.0-1.3 x 10^8 bps). + +Figure 5.2.2.7-19 Throughput performance for 48GHz under TDL-D, DFT-s-OFDM + +![Figure 5.2.2.7-20: Throughput performance for 48GHz under TDL-A, DFT-s-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. The legend is identical to Figure 5.2.2.7-19. The performance trends are similar, with 64QAM configurations achieving higher throughput than 256QAM configurations across the SNR range from 16 dB to 26 dB.](b387daba28c5aa523b84b26d6ba3d177_img.jpg) + +Figure 5.2.2.7-20: Throughput performance for 48GHz under TDL-A, DFT-s-OFDM. The graph shows throughput (bps) vs SNR (dB) for various MCS and TxEVM configurations. The legend is identical to Figure 5.2.2.7-19. The performance trends are similar, with 64QAM configurations achieving higher throughput than 256QAM configurations across the SNR range from 16 dB to 26 dB. + +Figure 5.2.2.7-20 Throughput performance for 48GHz under TDL-A, DFT-s-OFDM + +From the simulation results for 48GHz, table 5.2.2.7-2 updated the SNR required to achieve gains for 256QAM compare to 64QAM: + +Table 5.2.2.7-2 UL 256QAM required SNR to achieve gains compare to 64QAM + +| Parameters for UL 256QAM | | | 48GHz SNR required to achieve gains for 256QAM [dB] | | | +|--------------------------|-------|----------|-----------------------------------------------------|-----------|-------| +| Channel | MCS | | 3%+3% | 3.5%+3.5% | 4%+4% | +| AWGN
1x2 RANK1 | MCS21 | CP-OFDM | 24 | 25 | 28 | +| | | DFT-OFDM | 22.5 | 23.6 | 25 | +| | MCS23 | CP-OFDM | NA | NA | NA | +| | | DFT-OFDM | NA | NA | NA | + +| | | | | | | +|--------------------|-------|----------|----|----|----| +| TDL-D
2x2 RANK2 | MCS21 | DFT-OFDM | NA | NA | NA | +| | | CP-OFDM | NA | NA | NA | +| | | DFT-OFDM | NA | NA | NA | +| | MCS23 | CP-OFDM | NA | NA | NA | +| | | DFT-OFDM | NA | NA | NA | +| | | CP-OFDM | NA | NA | NA | +| TDL-A
2x2 RANK2 | MCS21 | CP-OFDM | NA | NA | NA | +| | | DFT-OFDM | NA | NA | NA | +| | MCS23 | CP-OFDM | NA | NA | NA | +| | | DFT-OFDM | NA | NA | NA | + +#### 5.2.2.8 Simulation results from ZTE + +R4-2216426 + +To study the gain and operating SNR, link level simulation approach was adopted to compare 256QAM with 64QAM. The simulation assumptions are from 5.2.2.1, and the parameters used in this simulation are marked in red. The throughput curves for CP-OFDM Rank1 transmission are listed in figure 5.2.2.8-1~ figure 5.2.2.8-9 for reference. + +![Line graph titled 'CP-OFDM AWGN @29GHz' showing Throughput vs SNR for various modulation and coding schemes (MCS) using 64QAM and 256QAM. The graph compares performance across different EVM levels (EVM3, EVM3.5, EVM4).](58f883d880e744531c77ddfd50af87bf_img.jpg) + +The graph displays throughput performance for CP-OFDM in an AWGN channel at 29GHz. The x-axis represents SNR from 18 to 36, and the y-axis represents Throughput from 0 to 5 x 108. The legend identifies several data series: + + +- 64qam MCS23 EVM3 (blue circles) +- 64qam MCS24 EVM3 (blue crosses) +- 256qam MCS21 EVM3 (red circles) +- 256qam MCS23 EVM3 (red crosses) +- 64qam MCS23 EVM3.5 (blue plus signs) +- 64qam MCS24 EVM3.5 (blue asterisks) +- 256qam MCS21 EVM3.5 (red plus signs) +- 256qam MCS23 EVM3.5 (red asterisks) +- 64qam MCS23 EVM4 (blue upward triangles) +- 64qam MCS24 EVM4 (blue downward triangles) +- 256qam MCS21 EVM4 (red upward triangles) +- 256qam MCS23 EVM4 (red downward triangles) + + The 256QAM series (red lines) show significantly higher throughput than the 64QAM series (blue lines) across the SNR range, especially at higher SNR values. The 256QAM MCS23 EVM3.5 and 256QAM MCS21 EVM3.5 series reach the highest throughput, approaching 4.5 x 108 at SNR 36. + +Line graph titled 'CP-OFDM AWGN @29GHz' showing Throughput vs SNR for various modulation and coding schemes (MCS) using 64QAM and 256QAM. The graph compares performance across different EVM levels (EVM3, EVM3.5, EVM4). + +Figure 5.2.2.8-1: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @29GHz AWGN channel + +![Line graph titled 'CP-OFDM TDLD @29GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations.](449dd9d482c5b47f1c013ce3e18b09e6_img.jpg) + +This line graph, titled "CP-OFDM TDLD @29GHz", plots Throughput (y-axis, scaled by $10^8$ ) against SNR (x-axis, ranging from 18 to 36). The graph compares the performance of 64QAM and 256QAM modulations across different Error Vector Magnitude (EVM) levels and Modulation and Coding Scheme (MCS) values. The legend identifies twelve data series: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, and 256qam MCS23 EVM4. The 256QAM configurations (red lines) show a significant increase in throughput as SNR increases, eventually plateauing between $3.5 \times 10^8$ and $4.2 \times 10^8$ . The 64QAM configurations (blue lines) show much lower throughput, plateauing around $3.1 \times 10^8$ to $3.3 \times 10^8$ . + +Line graph titled 'CP-OFDM TDLD @29GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations. + +Figure 5.2.2.8-2: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @29GHz TDLD channel + +![Line graph titled 'CP-OFDM TDLA @29GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations.](123e1675d910a1beab564c5fec9548e2_img.jpg) + +This line graph, titled "CP-OFDM TDLA @29GHz", plots Throughput (y-axis, scaled by $10^8$ ) against SNR (x-axis, ranging from 22 to 40). It follows the same format and legend as Figure 5.2.2.8-2, comparing 64QAM and 256QAM modulations. The 256QAM configurations (red lines) show a sharp increase in throughput starting from an SNR of 22, plateauing between $3.8 \times 10^8$ and $4.1 \times 10^8$ . The 64QAM configurations (blue lines) plateau at a lower throughput level, around $3.1 \times 10^8$ to $3.3 \times 10^8$ . + +Line graph titled 'CP-OFDM TDLA @29GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations. + +Figure 5.2.2.8-3: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @29GHz TDLA channel + +![Figure 5.2.2.8-4: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz AWGN channel. The graph shows throughput (x 10^8) vs SNR for various MCS and EVM levels in an AWGN channel.](26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg) + +This line graph, titled "CP-OFDM AWGN @39GHz", compares the throughput performance of 64QAM and 256QAM modulations in an Additive White Gaussian Noise (AWGN) channel at 39GHz. The y-axis represents Throughput in units of $10^8$ , ranging from 0 to 5. The x-axis represents the Signal-to-Noise Ratio (SNR) from 18 to 36. The legend identifies 12 data series: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, and 256qam MCS23 EVM4. Blue lines represent 64QAM and red lines represent 256QAM. In this AWGN channel, 256QAM generally achieves higher throughput than 64QAM for the same MCS and EVM level, especially at higher SNR values. + +Figure 5.2.2.8-4: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz AWGN channel. The graph shows throughput (x 10^8) vs SNR for various MCS and EVM levels in an AWGN channel. + +**Figure 5.2.2.8-4: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz AWGN channel** + +![Figure 5.2.2.8-5: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz TDLD channel. The graph shows throughput (x 10^8) vs SNR for various MCS and EVM levels in a TDLD channel.](624646367ef6cd220973a363f00310a0_img.jpg) + +This line graph, titled "CP-OFDM TDLD @39GHz", compares the throughput performance of 64QAM and 256QAM modulations in a Time Domain Limited Dispersion (TDLD) channel at 39GHz. The y-axis represents Throughput in units of $10^8$ , ranging from 0 to 4. The x-axis represents the SNR from 18 to 36. The legend is identical to the previous figure. Blue lines represent 64QAM and red lines represent 256QAM. In this TDLD channel, the performance is more complex. At lower SNR, 64QAM often achieves higher throughput than 256QAM. As SNR increases, 256QAM's performance improves significantly, eventually surpassing 64QAM at higher SNR values for most MCS and EVM configurations. + +Figure 5.2.2.8-5: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz TDLD channel. The graph shows throughput (x 10^8) vs SNR for various MCS and EVM levels in a TDLD channel. + +**Figure 5.2.2.8-5: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz TDLD channel** + +![Line graph titled 'CP-OFDM TDLA @39GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations.](c21fe89d8034ec5b80bd47c1cd710202_img.jpg) + +This line graph, titled "CP-OFDM TDLA @39GHz", plots Throughput (y-axis, scaled by $10^8$ ) against SNR (x-axis, ranging from 22 to 40). The graph compares the performance of 64QAM and 256QAM modulations across different Modulation and Coding Scheme (MCS) values and Error Vector Magnitude (EVM) levels. The legend identifies 12 data series: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, and 256qam MCS23 EVM4. Blue lines represent 64QAM configurations, which show higher throughput at lower SNR values, plateauing between $3.0 \times 10^8$ and $3.3 \times 10^8$ . Red lines represent 256QAM configurations, which show lower throughput at low SNR but increase and plateau at higher SNR values, with the highest performing 256QAM configuration reaching approximately $3.6 \times 10^8$ at SNR 40. + +Line graph titled 'CP-OFDM TDLA @39GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations. + +Figure 5.2.2.8-6: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @39GHz TDLA channel + +![Line graph titled 'CP-OFDM AWGN @48GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations.](38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg) + +This line graph, titled "CP-OFDM AWGN @48GHz", plots Throughput (y-axis, scaled by $10^8$ ) against SNR (x-axis, ranging from 22 to 40). It follows the same legend and data series as the previous graph. In the AWGN channel, the 64QAM configurations (blue lines) maintain a constant throughput across the entire SNR range, with values around $3.0 \times 10^8$ and $3.3 \times 10^8$ . The 256QAM configurations (red lines) start with near-zero throughput at low SNR and increase as SNR increases, eventually plateauing at higher SNR values. The best-performing 256QAM configuration reaches about $2.6 \times 10^8$ at SNR 40, which is lower than the plateau values achieved by the 64QAM configurations. + +Line graph titled 'CP-OFDM AWGN @48GHz' showing Throughput vs SNR for various 64QAM and 256QAM configurations. + +Figure 5.2.2.8-7: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz AWGN channel + +![Figure 5.2.2.8-8: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz TDLD channel. The graph shows throughput (x 10^8) vs SNR (22 to 40). Blue lines represent 64QAM and red lines represent 256QAM. Legend includes: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, 256qam MCS23 EVM4.](a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg) + +Figure 5.2.2.8-8 is a line graph titled "CP-OFDM TDLD @48GHz" showing throughput performance. The y-axis is labeled "Throughput" and scaled by $\times 10^8$ , ranging from 0 to 3.5. The x-axis is labeled "SNR" and ranges from 22 to 40. The graph compares 64QAM (blue lines) and 256QAM (red lines) across various MCS and EVM settings. 64QAM configurations (MCS23, MCS24) show higher throughput, plateauing around $3.0 \times 10^8$ to $3.3 \times 10^8$ . 256QAM configurations (MCS21, MCS23) show lower throughput, plateauing around $1.5 \times 10^8$ to $2.4 \times 10^8$ . The legend lists 12 series: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, and 256qam MCS23 EVM4. + +Figure 5.2.2.8-8: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz TDLD channel. The graph shows throughput (x 10^8) vs SNR (22 to 40). Blue lines represent 64QAM and red lines represent 256QAM. Legend includes: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, 256qam MCS23 EVM4. + +Figure 5.2.2.8-8: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz TDLD channel + +![Figure 5.2.2.8-9: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz TDLA channel. The graph shows throughput (x 10^8) vs SNR (22 to 40). Blue lines represent 64QAM and red lines represent 256QAM. Legend includes: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, 256qam MCS23 EVM4.](9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg) + +Figure 5.2.2.8-9 is a line graph titled "CP-OFDM TDLA @48GHz" showing throughput performance. The y-axis is labeled "Throughput" and scaled by $\times 10^8$ , ranging from 0 to 3.5. The x-axis is labeled "SNR" and ranges from 22 to 40. The graph compares 64QAM (blue lines) and 256QAM (red lines) across various MCS and EVM settings. 64QAM configurations (MCS23, MCS24) show higher throughput, plateauing around $3.0 \times 10^8$ to $3.3 \times 10^8$ . 256QAM configurations (MCS21, MCS23) show lower throughput, plateauing around $1.5 \times 10^8$ to $1.8 \times 10^8$ . The legend lists 12 series: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, and 256qam MCS23 EVM4. + +Figure 5.2.2.8-9: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz TDLA channel. The graph shows throughput (x 10^8) vs SNR (22 to 40). Blue lines represent 64QAM and red lines represent 256QAM. Legend includes: 64qam MCS23 EVM3, 64qam MCS24 EVM3, 256qam MCS21 EVM3, 256qam MCS23 EVM3, 64qam MCS23 EVM3.5, 64qam MCS24 EVM3.5, 256qam MCS21 EVM3.5, 256qam MCS23 EVM3.5, 64qam MCS23 EVM4, 64qam MCS24 EVM4, 256qam MCS21 EVM4, 256qam MCS23 EVM4. + +Figure 5.2.2.8-9: Throughput performance comparison between FR2 UL 256QAM and FR2 UL 64QAM @48GHz TDLA channel + +The target SNR values are summarized in table 5.2.2.8-1, where “-” means that 256QAM can not provide better performance in the given SNR range compared to 64QAM. + +**Table 5.2.2.8-1. Target SNR for CP-OFDM, Rank 1 transmission** + +| index | frequency | Channel | Test setup
(64QAM/256QAM) | Target SNR | | | +|-------|-----------|---------|------------------------------|-------------|----------------|-------------| +| | | | | EVM 3.0+3.0 | EVM
3.5+3.5 | EVM 4.0+4.0 | +| 1 | 29GHz | AWGN | MCS23/21 | 21.31 | 21.71 | 22.19 | +| 2 | | | MCS24/23 | 25.92 | 27.66 | 31.06 | +| 3 | | TDL-D | MCS23/21 | 23.42 | 23.73 | 24.16 | +| 4 | | | MCS24/23 | 28.44 | 30.10 | 34.28 | +| 5 | | TDL-A | MCS23/21 | 25.90 | 26.45 | 27.23 | +| 6 | | | MCS24/23 | 31.49 | 34.31 | - | +| 7 | 39GHz | AWGN | MCS23/21 | 21.28 | 21.64 | 21.95 | +| 8 | | | MCS24/23 | 25.86 | 27.64 | 30.62 | +| 9 | | TDL-D | MCS23/21 | 26.36 | 27.50 | 29.23 | +| 10 | | | MCS24/23 | - | - | - | +| 11 | | TDL-A | MCS23/21 | 30.48 | 32.35 | 36.62 | +| 12 | | | MCS24/23 | - | - | - | +| 13 | 48GHz | AWGN | MCS23/21 | - | - | - | +| 14 | | | MCS24/23 | - | - | - | +| 15 | | TDL-D | MCS23/21 | - | - | - | +| 16 | | | MCS24/23 | - | - | - | +| 17 | | TDL-A | MCS23/21 | - | - | - | +| 18 | | | MCS24/23 | - | - | - | + +Based on the simulation results, the following observations are given: + +##### **Observation 1:** For 29GHz: + +256QAM performance gain can be expected in the following cases: + +AWGN and TDL-D channel, + +TDL-A channel when MCS21(256QAM)/MCS23(64QAM) are selected, + +TDL-A channel when MCS23(256QAM)/MCS24(64QAM) and EVM3.0+3.0 or EVM3.5+3.5 are selected + +However, 256QAM performance gain can not be expected in the following cases: + +TDL-A channel when MCS23(256QAM)/MCS24(64QAM) and EVM4.0+4.0 are selected. + +##### **Observation 2:** For 39GHz: + +256QAM performance gain can be expected in the following cases: + +AWGN + +TDL-D and TDL-A channel when MCS21(256QAM)/MCS23(64QAM) are selected + +However, 256QAM performance gain can not be expected in the following cases: + +TDL-D and TDL-A channel when MCS23(256QAM)/MCS24(64QAM) are selected. + +For 48GHz, using the same phase noise model, the phase noise becomes larger as frequency increases. + +##### **Observation 3:** For 48GHz: + +256QAM performance gain can not be expected for AWGN, TDL-D and TDL-A channel for all the MCS. + +R4-2218595 + +For MCS22 evaluation, the simulation assumptions are 5.2.2.1, and the parameters used in this simulation are marked in red. The throughput curves for MCS22 for CP-OFDM Rank1 transmission are listed in figure 5.2.2.8-10~figure 5.2.2.8-12. + +![Line graph titled 'CP-OFDM AWGN @39GHz' showing Throughput vs SNR for 64qam and 256qam configurations.](b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg) + +This line graph, titled "CP-OFDM AWGN @39GHz", plots Throughput (y-axis, scaled by $10^8$ ) against SNR (x-axis, ranging from 20 to 38). Two data series are shown: 64qam MCS24 (blue line with circles) and 256qam MCS22 (red line with circles). The 64qam series maintains a constant throughput of approximately $3.3 \times 10^8$ across all SNR values. The 256qam series starts at 0 throughput at SNR 20, rises sharply between SNR 22 and 28, and plateaus at approximately $4.2 \times 10^8$ for SNR values of 32 and above. + +| SNR | 64qam MCS24 Throughput ( $\times 10^8$ ) | 256qam MCS22 Throughput ( $\times 10^8$ ) | +|-----|------------------------------------------|-------------------------------------------| +| 20 | 3.3 | 0 | +| 22 | 3.3 | 0.1 | +| 24 | 3.3 | 1.6 | +| 26 | 3.3 | 3.1 | +| 28 | 3.3 | 3.7 | +| 30 | 3.3 | 3.9 | +| 32 | 3.3 | 4.1 | +| 34 | 3.3 | 4.2 | +| 36 | 3.3 | 4.2 | +| 38 | 3.3 | 4.2 | + +Line graph titled 'CP-OFDM AWGN @39GHz' showing Throughput vs SNR for 64qam and 256qam configurations. + +Figure 5.2.2.8-10, Throughput performance comparison between FR2 UL 256QAM MCS 22 and FR2 UL 64QAM MCS24 @39GHz AWGN channel + +![Line graph titled 'CP-OFDM TDL-D @39GHz' showing Throughput vs SNR for 64qam and 256qam configurations.](5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg) + +This line graph, titled "CP-OFDM TDL-D @39GHz", plots Throughput (y-axis, scaled by $10^8$ ) against SNR (x-axis, ranging from 22 to 40). Two data series are shown: 64qam MCS24 (blue line with circles) and 256qam MCS22 (red line with circles). The 64qam series maintains a constant throughput of approximately $3.3 \times 10^8$ across all SNR values. The 256qam series starts at approximately $0.5 \times 10^8$ at SNR 22, rises to about $3.4 \times 10^8$ at SNR 30, and plateaus at approximately $4.1 \times 10^8$ for SNR values of 38 and above. + +| SNR | 64qam MCS24 Throughput ( $\times 10^8$ ) | 256qam MCS22 Throughput ( $\times 10^8$ ) | +|-----|------------------------------------------|-------------------------------------------| +| 22 | 3.1 | 0.5 | +| 24 | 3.2 | 1.3 | +| 26 | 3.2 | 2.2 | +| 28 | 3.3 | 2.9 | +| 30 | 3.3 | 3.4 | +| 32 | 3.3 | 3.7 | +| 34 | 3.3 | 3.9 | +| 36 | 3.3 | 4.0 | +| 38 | 3.3 | 4.1 | +| 40 | 3.3 | 4.1 | + +Line graph titled 'CP-OFDM TDL-D @39GHz' showing Throughput vs SNR for 64qam and 256qam configurations. + +Figure 5.2.2.8-12, Throughput performance comparison between FR2 UL 256QAM MCS 22 and FR2 UL 64QAM MCS24 @39GHz TDL-D channel + +![Figure 5.2.2.8-12: Throughput performance comparison between FR2 UL 256QAM MCS 22 and FR2 UL 64QAM MCS 24 @39GHz TDL-A channel. The graph shows Throughput (x 10^8) vs SNR. The 256QAM MCS 22 (red line with circles) starts at ~0.4 at SNR 22 and increases to ~4.1 at SNR 40. The 64QAM MCS 24 (blue line with circles) starts at ~3.0 at SNR 22 and increases to ~3.3 at SNR 40. The 256QAM MCS 22 performance is significantly better than the 64QAM MCS 24 performance in the given SNR range.](8e21461e0c9384ec60322bedb1b1ab17_img.jpg) + +| SNR | 64QAM MCS24 Throughput (x 10 8 ) | 256QAM MCS22 Throughput (x 10 8 ) | +|-----|---------------------------------------------|----------------------------------------------| +| 22 | 3.0 | 0.4 | +| 24 | 3.1 | 1.0 | +| 26 | 3.2 | 1.8 | +| 28 | 3.3 | 2.5 | +| 30 | 3.3 | 3.2 | +| 32 | 3.3 | 3.5 | +| 34 | 3.3 | 3.8 | +| 36 | 3.3 | 4.0 | +| 38 | 3.3 | 4.1 | +| 40 | 3.3 | 4.1 | + +Figure 5.2.2.8-12: Throughput performance comparison between FR2 UL 256QAM MCS 22 and FR2 UL 64QAM MCS 24 @39GHz TDL-A channel. The graph shows Throughput (x 10^8) vs SNR. The 256QAM MCS 22 (red line with circles) starts at ~0.4 at SNR 22 and increases to ~4.1 at SNR 40. The 64QAM MCS 24 (blue line with circles) starts at ~3.0 at SNR 22 and increases to ~3.3 at SNR 40. The 256QAM MCS 22 performance is significantly better than the 64QAM MCS 24 performance in the given SNR range. + +**Figure 5.2.2.8-12, Throughput performance comparison between FR2 UL 256QAM MCS 22 and FR2 UL 64QAM MCS 24 @39GHz TDL-A channel** + +The updated target SNR values are summarized in table 5.2.2.8-2, where “-” means that 256QAM can not provide better performance in the given SNR range compared to 64QAM. As EVM was reached in last meeting so the simulation results of EVM 3.0% and EVM 4.0% are not provided. + +**Table 5.2.2.8-2. Target SNR for CP-OFDM, Rank 1 transmission** + +| index | frequency | Channel | Test setup (64QAM/256QAM) | Target SNR | +|-------|-----------|---------|---------------------------|-------------------| +| | | | | EVM 3.5%
+3.5% | +| 1 | 29GHz | AWGN | MCS23/21 | 20.80 | +| 2 | | | MCS24/23 | 27.47 | +| 3 | | TDL-D | MCS23/21 | 22.42 | +| 4 | | | MCS24/23 | 27.71 | +| 5 | | TDL-A | MCS23/21 | 24.03 | +| 6 | | | MCS24/23 | 29.07 | +| 7 | 39GHz | AWGN | MCS23/21 | 22.00 | +| 8 | | | MCS24/22 | 27.55 | +| 9 | | | MCS24/23 | - | +| 10 | | TDL-D | MCS23/21 | 26.00 | +| 11 | | | MCS24/22 | 29.61 | +| 12 | | | MCS24/23 | - | +| 13 | | TDL-A | MCS23/21 | 26.09 | +| 14 | | | MCS24/22 | 30.70 | +| 15 | | | MCS24/23 | - | +| 16 | | AWGN | MCS23/21 | - | +| 17 | | | MCS24/23 | - | +| 18 | | | MCS23/21 | - | + +Based on the simulation results, the following observations are given: + +##### **Observation 1: For 39GHz:** + +UL 256QAM performance gain can be expected in the following cases: + +AWGN, TDL-D and TDL-A channel when MCS21(256QAM)/MCS23(64QAM) are selected + +AWGN, TDL-D and TDL-A channel when MCS22(256QAM)/MCS24(64QAM) are selected + +##### **Observation 2: UL 256QAM performance gain can not be expected for 48GHz.** + +#### 5.2.2.9 Simulation results from Ericsson + +R4-2220036 + +On Figure 5.2.2.9-1 – Figure 5.2.2.9-8 we provide simulation results for various scenarios described in figure captions and figure legends. + +![Figure 5.2.2.9-1: ul sch throughput vs SNR [dB] for AWGN 2x2 Rank 1 channel. The graph shows three data series: 256qamMcs21 (green circles), 64qamMcs23 (magenta squares), and 64qamMcs24 (yellow diamonds). Throughput increases sharply between 15 dB and 30 dB SNR, with the 256qamMcs21 series reaching the highest plateau around 4.2 x 10^8.](28639a75145506e46966c11c1b995dd2_img.jpg) + +Figure 5.2.2.9-1 is a line graph titled "ul sch throughput" showing the relationship between SNR [dB] (x-axis, 10 to 40) and ul sch throughput (y-axis, -0.5 to 4.5 x 108). The graph compares three scenarios for an AWGN 2x2 Rank 1 channel. The 256qamMcs21 scenario (green circles) shows a sharp increase in throughput starting around 25 dB SNR, reaching a plateau of approximately 4.2 x 108 at 30 dB SNR. The 64qamMcs23 (magenta squares) and 64qamMcs24 (yellow diamonds) scenarios show a sharp increase in throughput starting around 15 dB SNR, reaching plateaus of approximately 3.2 x 108 and 3.5 x 108 respectively by 20 dB SNR. + +| SNR [dB] | 256qamMcs21 (x10 8 ) | 64qamMcs23 (x10 8 ) | 64qamMcs24 (x10 8 ) | +|----------|---------------------------------|--------------------------------|--------------------------------| +| 10 | 0.0 | 0.0 | 0.0 | +| 15 | 0.0 | 0.0 | 0.0 | +| 20 | 0.0 | 3.2 | 3.5 | +| 25 | 1.0 | 3.2 | 3.5 | +| 30 | 4.2 | 3.2 | 3.5 | +| 35 | 4.2 | 3.2 | 3.5 | +| 40 | 4.2 | 3.2 | 3.5 | + +Figure 5.2.2.9-1: ul sch throughput vs SNR [dB] for AWGN 2x2 Rank 1 channel. The graph shows three data series: 256qamMcs21 (green circles), 64qamMcs23 (magenta squares), and 64qamMcs24 (yellow diamonds). Throughput increases sharply between 15 dB and 30 dB SNR, with the 256qamMcs21 series reaching the highest plateau around 4.2 x 10^8. + +Figure 5.2.2.9-1: 29GHz, 100MHz, No HARQ, AWGN 2x2 Rank 1 channel, txEVM= rxEVM=3.5% + +![Figure 5.2.2.9-2: ul sch throughput vs SNR [dB] for Fading 2x2 Rank 1 channel. The graph shows three data series: 256qamMcs21 (green circles), 64qamMcs23 (magenta squares), and 64qamMcs24 (blue triangles). Throughput increases between 15 dB and 30 dB SNR, with the 256qamMcs21 series reaching the highest plateau around 4.2 x 10^8.](f6eaafb7dc1fa9a73c518dca33bc801b_img.jpg) + +Figure 5.2.2.9-2 is a line graph titled "ul sch throughput" showing the relationship between SNR [dB] (x-axis, 10 to 40) and ul sch throughput (y-axis, -0.5 to 4.5 x 108). The graph compares three scenarios for a Fading 2x2 Rank 1 channel. The 256qamMcs21 scenario (green circles) shows a sharp increase in throughput starting around 25 dB SNR, reaching a plateau of approximately 4.2 x 108 at 30 dB SNR. The 64qamMcs23 (magenta squares) and 64qamMcs24 (blue triangles) scenarios show a sharp increase in throughput starting around 15 dB SNR, reaching plateaus of approximately 3.2 x 108 and 3.5 x 108 respectively by 20 dB SNR. + +| SNR [dB] | 256qamMcs21 (x10 8 ) | 64qamMcs23 (x10 8 ) | 64qamMcs24 (x10 8 ) | +|----------|---------------------------------|--------------------------------|--------------------------------| +| 10 | 0.0 | 0.0 | 0.0 | +| 15 | 0.0 | 0.0 | 0.0 | +| 20 | 0.0 | 3.2 | 3.5 | +| 25 | 1.0 | 3.2 | 3.5 | +| 30 | 4.2 | 3.2 | 3.5 | +| 35 | 4.2 | 3.2 | 3.5 | +| 40 | 4.2 | 3.2 | 3.5 | + +Figure 5.2.2.9-2: ul sch throughput vs SNR [dB] for Fading 2x2 Rank 1 channel. The graph shows three data series: 256qamMcs21 (green circles), 64qamMcs23 (magenta squares), and 64qamMcs24 (blue triangles). Throughput increases between 15 dB and 30 dB SNR, with the 256qamMcs21 series reaching the highest plateau around 4.2 x 10^8. + +Figure 5.2.2.9-2: 29GHz, 100MHz, No HARQ, Fading 2x2 Rank 1 channel, txEVM= rxEVM=3.5% + +![Line graph titled 'ul sch throughput' showing throughput (x 10^8) vs SNR [dB] for AWGN 2x2 Rank 2 channel. Legend: red 'x' for 2tx2rxAWGN 29G 120k 100M 256qamMcs21 2layer noICI; blue 'v' for 2tx2rxAWGN 35 29G 120k 100M 64qamMcs23 2layer noICI; green 'triangle' for 2tx2rxAWGN 35 29G 120k 100M 64qamMcs24 2layer noICI.](f68421f5d184c116a7061977a9057e63_img.jpg) + +Line graph titled 'ul sch throughput' showing throughput (x 10^8) vs SNR [dB] for AWGN 2x2 Rank 2 channel. Legend: red 'x' for 2tx2rxAWGN 29G 120k 100M 256qamMcs21 2layer noICI; blue 'v' for 2tx2rxAWGN 35 29G 120k 100M 64qamMcs23 2layer noICI; green 'triangle' for 2tx2rxAWGN 35 29G 120k 100M 64qamMcs24 2layer noICI. + +**Figure 5.2.2.9-3: 29GHz, 100MHz, No HARQ, AWGN 2x2 Rank 2 channel, txEVM= rxEVM=3.5%** + +![Line graph titled 'ul sch throughput' showing throughput (x 10^8) vs SNR [dB] for Fading 2x2 Rank 2 channel. Legend: red 'x' for 2tx2rxTDLD30 35 29G 120k 100M 256qamMcs21 2layer noICI; yellow 'diamond' for 2tx2rxTDLD30 35 29G 120k 100M 64qamMcs23 2layer noICI; green 'triangle' for 2tx2rxTDLD30 35 29G 120k 100M 64qamMcs24 2layer noICI.](c8380fb19e591e67d5e053b03ae58f32_img.jpg) + +Line graph titled 'ul sch throughput' showing throughput (x 10^8) vs SNR [dB] for Fading 2x2 Rank 2 channel. Legend: red 'x' for 2tx2rxTDLD30 35 29G 120k 100M 256qamMcs21 2layer noICI; yellow 'diamond' for 2tx2rxTDLD30 35 29G 120k 100M 64qamMcs23 2layer noICI; green 'triangle' for 2tx2rxTDLD30 35 29G 120k 100M 64qamMcs24 2layer noICI. + +**Figure 5.2.2.9-4: 29GHz, 100MHz, No HARQ, Fading 2x2 Rank 2 channel, txEVM= rxEVM=3.5%** + +![Line graph titled 'ul sch throughput' showing throughput (x 10^8) vs SNR [dB] for AWGN 2x2 Rank 1 channel with HARQ=8. Legend: green 'circle' for 2tx2rxAWGN 29G 120k 100M 256qamMcs21 1layer noICI; magenta 'square' for 2tx2rxAWGN 29G 120k 100M 64qamMcs23 1layer noICI; yellow 'diamond' for 2tx2rxAWGN 29G 120k 100M 64qamMcs24 1layer noICI.](40fa7d84ea1c6bb38863689c3a0590fa_img.jpg) + +Line graph titled 'ul sch throughput' showing throughput (x 10^8) vs SNR [dB] for AWGN 2x2 Rank 1 channel with HARQ=8. Legend: green 'circle' for 2tx2rxAWGN 29G 120k 100M 256qamMcs21 1layer noICI; magenta 'square' for 2tx2rxAWGN 29G 120k 100M 64qamMcs23 1layer noICI; yellow 'diamond' for 2tx2rxAWGN 29G 120k 100M 64qamMcs24 1layer noICI. + +**Figure 5.2.2.9-5: 29GHz, 100MHz, HARQ=8, AWGN 2x2 Rank 1 channel, txEVM= rxEVM=3.5%** + +![Figure 5.2.2.9-6: ul sch throughput vs SNR [dB] for 29GHz, 100MHz, HARQ=8, Fading 2x2 Rank 1 channel. The graph shows three curves: 2b2rxTDL30 35 29G 120k 100M 256qamMcs21 1layer noCI (green circles), 2b2rxTDL30 35 29G 120k 100M 64qamMcs23 1layer noCI (magenta squares), and 2b2rxTDL30 35 29G 120k 100M 64qamMcs24 1layer noCI (blue triangles). The green curve reaches the highest throughput of approximately 4.2 x 10^8 at SNR 30 dB.](5e7b93195badf89e1fb645ae53d619bb_img.jpg) + +Figure 5.2.2.9-6: ul sch throughput vs SNR [dB] for 29GHz, 100MHz, HARQ=8, Fading 2x2 Rank 1 channel. The graph shows three curves: 2b2rxTDL30 35 29G 120k 100M 256qamMcs21 1layer noCI (green circles), 2b2rxTDL30 35 29G 120k 100M 64qamMcs23 1layer noCI (magenta squares), and 2b2rxTDL30 35 29G 120k 100M 64qamMcs24 1layer noCI (blue triangles). The green curve reaches the highest throughput of approximately 4.2 x 10^8 at SNR 30 dB. + +Figure 5.2.2.9-6: 29GHz, 100MHz, HARQ=8, Fading 2x2 Rank 1 channel, txEVM= rxEVM=3.5% + +![Figure 5.2.2.9-7: ul sch throughput vs SNR [dB] for 29GHz, 100MHz, HARQ=8, AWGN 2x2 Rank 2 channel. The graph shows three curves: 2b2rxAWGN 29G 120k 100M 256qamMcs21 2layer noCI (red crosses), 2b2rxAWGN 35 29G 120k 100M 64qamMcs23 2layer noCI (blue triangles), and 2b2rxAWGN 35 29G 120k 100M 64qamMcs24 2layer noCI (green triangles). The red curve reaches the highest throughput of approximately 8.5 x 10^8 at SNR 35 dB.](84b564808c370adacae8a814707fb071_img.jpg) + +Figure 5.2.2.9-7: ul sch throughput vs SNR [dB] for 29GHz, 100MHz, HARQ=8, AWGN 2x2 Rank 2 channel. The graph shows three curves: 2b2rxAWGN 29G 120k 100M 256qamMcs21 2layer noCI (red crosses), 2b2rxAWGN 35 29G 120k 100M 64qamMcs23 2layer noCI (blue triangles), and 2b2rxAWGN 35 29G 120k 100M 64qamMcs24 2layer noCI (green triangles). The red curve reaches the highest throughput of approximately 8.5 x 10^8 at SNR 35 dB. + +Figure 5.2.2.9-7: 29GHz, 100MHz, HARQ=8, AWGN 2x2 Rank 2 channel, txEVM= rxEVM=3.5% + +![Figure 5.2.2.9-8: ul sch throughput vs SNR [dB] for 29GHz, 100MHz, HARQ=8, Fading 2x2 Rank 2 channel. The graph shows three curves: 2b2rxTDL30 35 29G 120k 100M 256qamMcs21 2layer noCI (red crosses), 2b2rxTDL30 35 29G 120k 100M 64qamMcs23 2layer noCI (yellow diamonds), and 2b2rxTDL30 35 29G 120k 100M 64qamMcs24 2layer noCI (green triangles). The red curve reaches the highest throughput of approximately 8.2 x 10^8 at SNR 40 dB.](ccb9204e004de0c9e190f4773e940efd_img.jpg) + +Figure 5.2.2.9-8: ul sch throughput vs SNR [dB] for 29GHz, 100MHz, HARQ=8, Fading 2x2 Rank 2 channel. The graph shows three curves: 2b2rxTDL30 35 29G 120k 100M 256qamMcs21 2layer noCI (red crosses), 2b2rxTDL30 35 29G 120k 100M 64qamMcs23 2layer noCI (yellow diamonds), and 2b2rxTDL30 35 29G 120k 100M 64qamMcs24 2layer noCI (green triangles). The red curve reaches the highest throughput of approximately 8.2 x 10^8 at SNR 40 dB. + +Figure 5.2.2.9-8: 29GHz, 100MHz, HARQ=8, Fading 2x2 Rank 2 channel, txEVM= rxEVM=3.5% + +In Table 5.2.2.9-1 we have summarized results where we indicate two operating SNR points where 256QAM MCS21 outperforms 64QAM MCS23 and 64QAM MCS24, respectively. + +**Table 5.2.2.9-1: Summary of link-level simulation results** + +| HARQ Type | Channel type | Cross-point between 256QAM MCS21 and 64QAM MCS23 | Cross-point between 256QAM MCS21 and 64QAM MCS24 | +|----------------|-------------------|--------------------------------------------------|--------------------------------------------------| +| No HARQ | AWGN 2x2 Rank 1 | 26.2 dB | 26.8 dB | +| | AWGN 2x2 Rank 2 | 28.7 dB | 29 dB | +| | Fading 2x2 Rank 1 | 27.9 dB | 28.1 dB | +| | Fading 2x2 Rank 2 | 32.4 dB | 33.2 dB | +| HARQ=8 | AWGN 2x2 Rank 1 | 26 dB | 26.4 dB | +| | AWGN 2x2 Rank 2 | 28.1 dB | 28.8 dB | +| | Fading 2x2 Rank 1 | 27.1 dB | 27.8 dB | +| | Fading 2x2 Rank 2 | 31.2 dB | 32.2 dB | + +We conclude first that between not having HARQ and having HARQ=8 repetitions there are no big differences when it comes to the cross-point (operating SNR) between 256QAM MCS21 and 64QAM MCS23/MCS24, respectively. For the AWGN channel, the operating SNR is lower by 0.3 dB in average in the “No HARQ” case compared with “HARQ=8” case, while for the TDL-D fading channel the operating SNR is lower by 0.8 dB in the “No HARQ” case compared with “HARQ=8” case. + +For “No HARQ” case, for AWGN channel the average operating SNR is equal to 27.7 dB. + +For “No HARQ” case, for TDL-D fading channel the average operating SNR is equal to 30.4 dB. + +#### 5.2.2.10 Summary for 29GHz simulation results + +| Parameter | | | Nokia R4-2215577 | LG Electronics R4-2215920 R4-2218681 | vivo R4-2216128 | Huawei R4-2216245 R4-2219144 | Sony R4-2216251 R4-2218753 | Xiaomi R4-2216350 | ZTE R4-2216426 R4-2218595 | Ericsson R4-2220036 | +|-------------------|-------|-------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------| +| Carrier frequency | | | 29 GHz | 29 GHz | 29 GHz | 29 GHz | 29 GHz | 29 GHz | 29 GHz | 29 GHz | +| CBW | | | 50MHz | 100MHz | 50MHz/100MHz | 50MHz | 100MHz | 50MHz | 100MHz | 100MHz | +| SCS | | | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | +| HARQ | | | none | none | | none | none | none | none | none/8 | +| RANK | | | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | +| Phase noise model | | | Option a):
example1 (UE) +
example1(BS) | Option b):
example2 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option d):
example1 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option a):
example1 (UE) +
example1(BS) | +| Tx EVM=Rx EVM | | | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | +| Target SNR(dB) | TDL-A | MCS20 | | 25.5 | | | | | | | +| | | MCS21 | | 30 | 22.7/24 | | | 22.7 | 26.45/24.03 | | +| | | MCS22 | | NA | | | | | | | +| | | MCS23 | | NA | 26.3/28.4 | | | 28 | 34.31/29.07 | | +| | TDL-D | MCS20 | | 18.5 | | | | | | | +| | | MCS21 | 24-25 | 21 | 20.8/21.8 | 20.1 | 23 | 22.5 | 23.73/22.42 | 27.9/27.1 | +| | | MCS22 | | 23 | | | | | | | +| | | MCS23 | 32 | 27 | 25.7/28 | 23 | | 27.3 | 30.10/27.71 | | +| | AWGN | MCS21 | | 17 | 19.5/19.7 | | 20 | 19.5 | 21.71/20.8 | 26.2/26 | +| | | MCS23 | | 21 | 22.2/23.8 | | 25 | 23.5 | 27.66/27.47 | | + +Average value for 29GHz operating SNR based on TDL-D: + +| | Operating SNR (dB) with EVM 3.5% | | | | +|----------|----------------------------------|--------------|--------------|--------------| +| | TDL-D, MCS20 | TDL-D, MCS21 | TDL-D, MCS22 | TDL-D, MCS23 | +| Nokia | - | 25 | - | 32 | +| LGE | 18.5 | 21 | 23 | 27 | +| vivo | - | 21.8 | - | 28 | +| Huawei | - | 20.1 | - | 23 | +| Xiaomi | - | 22.5 | - | 27.3 | +| ZTE | - | 22.42 | - | 27.71 | +| Ericsson | - | 27.9 | - | - | +| Average | 18.5 | 23 | 23 | 27.5 | + +#### 5.2.2.11 Summary for 39GHz simulation results + +| Parameter | | Nokia
R4-2215577 | LG Electronics
R4-2218681 | vivo
R4-2216128 | Huawei
R4-2216245
R4-2219144 | Sony
R4-2218753 | Xiaomi
R4-2216350 | ZTE
R4-2216426
R4-2218595 | +|-------------------|-------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------| +| Carrier frequency | | 39 GHz | 39 GHz | 39 GHz | 39 GHz | 39 GHz | 39 GHz | 39 GHz | +| CBW | | 50MHz | 100MHz | 50MHz/100MHz | 50MHz | 50MHz | 50MHz | 100MHz | +| SCS | | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | +| HARQ | | none | none | none | none | none | none | none | +| RANK | | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | +| Phase noise model | | Option a):
example1
(UE) +
example1(BS) | Option b):
example2 (UE)
+
example2(BS) | Option b):
example2 (UE)
+
example2(BS) | Option d):
example1 (UE)
+
example2(BS) | Option b):
example2 (UE)
+
example2(BS) | Option b):
example2 (UE)
+
example2(BS) | Option b):
example2 (UE)
+
example2(BS) | +| Tx EVM=Rx EVM | | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | +| Target
SNR(dB) | TDL-A | MCS20 | NA | | | | | | +| | | MCS21 | NA | 29.2/NA | | | 26.7 | 32.35/26.09 | +| | | MCS22 | NA | | | | | 30.70 | +| | | MCS23 | NA | NA | | | NA | NA | +| | TDL-D | MCS20 | 21 | | | | | | +| | | MCS21 | 36 | 24 | 25/NA | 21 | 25.2 | 27.50/26 | +| | | MCS22 | 30 | | | | | 29.61 | +| | | MCS23 | NA | NA | 25.4 | | NA | NA | +| | AWGN | MCS21 | | 21.8/28 | | 21.5 | 21.5 | 21.64/22 | +| | | MCS22 | | | | | | 27.55 | +| | | MCS23 | | NA | | 36 | NA | 27.64 | + +Average value for 39GHz operating SNR based on TDL-D: + +| | Operating SNR (dB) with EVM 3.5% | | | | +|-------|----------------------------------|--------------|--------------|--------------| +| | TDL-D, MCS20 | TDL-D, MCS21 | TDL-D, MCS22 | TDL-D, MCS23 | +| Nokia | - | 36 | - | - | +| LGE | 21 | 24 | 30 | NA | +| vivo | - | 25 | - | NA | + +| | | | | | +|---------|----|------|-------|------| +| Huawei | - | 21 | - | 25.4 | +| Xiaomi | - | 25.2 | - | NA | +| ZTE | - | 26 | 29.21 | NA | +| Average | 21 | 26.2 | 29.6 | NA | + +#### 5.2.2.12 Summary for 48GHz simulation results + +| Parameter | | LG Electronics
R4-2215920 | vivo
R4-2216128 | Huawei
R4-2216245 | Xiaomi
R4-2216350
R4-2219075 | ZTE
R4-2216426
R4-2219595 | Nokia
R4-2218326 | | +|-------------------|-------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|--------------------------------------------------|--------------------------------------------------| +| Carrier frequency | | 48 GHz | 48 GHz | 48 GHz | 48 GHz | 48 GHz | 48 GHz | | +| CBW | | 100MHz | 50MHz/100MHz | 50MHz | 50MHz | 100MHz | 50MHz | | +| SCS | | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | 120kHz | | +| HARQ | | none | none | none | none | none | none | | +| RANK | | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | RANK1 | | +| Phase noise model | | Option b):
example2 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option d):
example1 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option b):
example2 (UE) +
example2(BS) | Option a):
example1
(UE) +
example1(BS) | Option d):
example1
(UE) +
example2(BS) | +| Tx EVM=Rx EVM | | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | 3.5% | +| Target
SNR(dB) | TDL-A | MCS21 | NA | NA | NA | NA | | | +| | | MCS23 | NA | NA | NA | NA | | | +| | TDL-D | MCS21 | NA | NA | 22.6 | NA | NA | NA | +| | | MCS23 | NA | NA | NA | NA | NA | NA | +| | AWGN | MCS21 | 27.5 | NA | 25 | NA | | | +| | | MCS23 | NA | NA | NA | NA | | | + +### 5.2.3 Phase noise profiles evaluation + +#### 5.2.3.1 Simulation assumptions + +| Parameters | Value | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency | 29, 39 GHz | +| SCS | 60kHz, 120kHz | +| BW | 100MHz | +| RB Size | 128RB for 60kHz, 64RB for 120kHz | +| Background AWGN | No additional noise | +| Time offset/Frequency offset | 0 | +| Antenna configuration | 1T1R | +| Modulation | 256QAM | +| Waveform type | CP-OFDM / DFT-s-OFDM | +| DMRS | 3 symbols per slot (UL DMRS add-pos = 2) | +| PTRS configuration | OFF/ON
For CP-OFDM:
L-PTRS (Time density) = 1 (every 1 symbol)
K-PTRS (Freq density) = 2 (every 2 RBs)
For DFTs-OFDM:
L-PTRS (Time density) = 1 (every symbol)
N_group = 8, N_samp = 4
Other PTRS configurations can be considered for narrow RB allocations, especially for DFT-s-OFDM. | +| EVM measurement | Data aided EVM calculation, based on ideal data signal | +| Phase noise profiles | Refer to clause 5.2.3.2 | + +#### 5.2.3.2 Phase noise profiles + +The phase noise profiles in TS 38.803 [3] (“UE example 1” and “UE example 2”) don’t have good enough EVM for higher modulations, i.e., 256QAM with the typical 3.5% EVM requirement. In the discussion progress, some candidate phase noise profiles for 29GHz and 39GHz for UL 256QAM are proposed as following options: + +For 29GHz: + +Option1: Example 1 in TR38.803 for 29 GHz. + +Option 2: Example 2 in TR38.803. + +New phase noise model using the pole-zero method based on following function: + +Option 3: Parameters from Qualcomm + +| PSD0 | 32 dB | | | | +|--------|-----------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 6e5 | 4.7 | 8e5 | 5.3 | +| 3 | 8e5 | 2.0 | 1.1e6 | 2.5 | + +Option 4: Parameters from MTK + +Parameters for 29.55 GHz PLL phase noise model + +| PSD0 | 860.4 (29.35dB) | | | | +|--------|-----------------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 660e3 | 2.7 | 1.6e6 | 3.3 | +| 3 | 182e6 | 2.53 | 30e6 | 1 | + +For 39GHz: + +Option 1: Example 1-based using following function: + +Parameters from vivo + +Parameters for 39 GHz PLL phase noise model valid from 100 Hz and upwards + +| PSD0 | 2761 (34.41dB) | | | | +|------------|------------------------|------------------------|------------------------|------------------------| +| n,m | fz,n | αz,n | fp,m | αp,m | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 494e3 | 2.7 | 1.58e6 | 3.3 | +| 3 | 418e6 | 2.53 | 30e6 | 1 | + +Parameters from Anritsu + +| PSD0 | 2760.85 (34.4dB) | | | | +|------------|------------------------|------------------|------------------------|------------------| +| n,m | fz,n | Alpha z,n | fp,m | Alpha p,m | +| 1 | 3.00E+03 | 2.37 | 1 | 3.3 | +| 2 | 4.99E+05 | 2.7 | 1.54E+06 | 3.3 | +| 3 | 3.90E+08 | 2.53 | 3.00E+07 | 1 | + +Table 3 – 39GHz + +Option 2: Example 2 in TR38.803. + +New phase noise model using the pole-zero method based on following function: + +Option 3: Parameters from MTK + +Parameters for 39 GHz PLL phase noise model + +| PSD0 | 1498.7 (31.76dB) | | | | +|------------|------------------------|------------------------|------------------------|------------------------| +| n,m | fz,n | αz,n | fp,m | αp,m | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 620e3 | 2.7 | 1.6e6 | 3.3 | +| 3 | 240e6 | 2.53 | 30e6 | 1 | + +Option 4: Adopt min(example1, example2) as the phase noise profile for UL256QAM, where ‘example2’ refers to the example phase noise profiles in TR38.803 and ‘example1’ refers to Example 1-based for 39GHz. + +#### 5.2.3.3 Simulation results from Xiaomi + +R4-2308805/R4-2318876 + +Based on the agreed simulation assumptions and candidate phase noise profiles, the EVM floor is further evaluated for CP- OFDM and DFT-s-OFDM. + +For 29GHz: + +Table 5.2.3.3-1 EVM floor and benefit for with PTRS CP-OFDM at 29GHz + +| CP-OFDM with phase noise, 29GHz, 120kHz, 64RB, K-PTRS=2 | | | | +|---------------------------------------------------------|-----------------------------------|--------------------|---------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS | Net benefit of PTRS | +| Example 1 from TR38.803 | -28.1 | -28.5 | 0.4 | +| Example 2 from TR38.803 | -23.6 | -25.3 | 1.7 | +| Phase noise Profile from Qualcomm | -31.9 | -33.1 | 1.2 | +| Phase noise Profile from MTK | -32.4 | -33.0 | 0.6 | + +**Table 5.2.3.3-2 EVM floor and benefit for with PTRS DFT-s-OFDM at 29GHz** + +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 64RB, N_group = 8, N_samp = 4 | | | | +|----------------------------------------------------------------------------------|-----------------------------------|--------------------|---------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS | Net benefit of PTRS | +| Example 1 from TR38.803 | -28.2 | -27.1 | -1.1 | +| Example 2 from TR38.803 | -23.1 | -27.2 | 4.1 | +| Phase noise Profile from Qualcomm | -31.8 | -32.0 | 0.2 | +| Phase noise Profile from MTK | -32.4 | -31.7 | -0.7 | + +From table 5.2.3.3-1 and table 5.2.3.3-2 for 29GHz, we can see no matter for CP- OFDM and DFT-s-OFDM: + +The EVM floors for new phase noise profiles from QC and MTK are reduced obviously compared to Example 1 and Example 2. + +Further compared new phase noise profiles from QC and MTK, we can see the EVM floor of MTK's phase noise profile is lower than Qualcomm's when without PTRS correction. And they have similar EVM floor when adding PTRS correction. Since the CPE (common phase error) impacts is closely related to the performance of phase noise profile, it will get less benefit from PTRS correction if the phase noise profile introduce less CPE (common phase error). + +Therefore, we can't only judge the phase noise profile according to the net benefit but also need consider the performance without PTRS correction. + +These two new phase noise profiles have similar performance after PTRS correction for both of CP-OFDM and DFT-S-OFDM, from this point, both of them can be used in MPR simulation. + +For 39GHz: + +**Table 5.2.3.3-3 EVM floor and benefit for with PTRS CP-OFDM at 39GHz** + +| CP-OFDM with phase noise, 39GHz, 120kHz, 64RB, K-PTRS=2 | | | | +|--------------------------------------------------------------------|-----------------------------------|--------------------|---------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS | Net benefit of PTRS | +| Example 1:VIVO parameter | -24.8 | -25.1 | 0.3 | +| Example 1:Anritsu parameter | -25.1 | -25.5 | 0.4 | +| Example 2 from TR38.803 | -20.9 | -22.7 | 1.8 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -29.2 | -30.3 | 1.1 | +| Phase noise Profile from Qualcomm Min(Example1- Anritsu, Example2) | -29.3 | -30.3 | 1.0 | +| Phase noise Profile from MTK | -29.4 | -30.0 | 0.6 | + +**Table 5.2.3.3-4 EVM floor and benefit for with PTRS DFT-s-OFDM at 39GHz** + +| CP-OFDM with phase noise, 39GHz, 120kHz, 64RB, N_group = 8, N_samp = 4 | | | | +|-------------------------------------------------------------------------------|-----------------------------------|--------------------|---------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS | Net benefit of PTRS | +| Example 1:VIVO parameter | -24.8 | -23.7 | -1.1 | +| Example 1:Anritsu parameter | -25.2 | -24.0 | -1.2 | +| Example 2 from TR38.803 | -20.5 | -24.4 | 3.9 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -29.2 | -29.1 | -0.1 | +| Phase noise Profile from Qualcomm Min(Example1- Anritsu, Example2) | -29.2 | -29.2 | 0.0 | +| Phase noise Profile from MTK | -29.5 | -28.7 | -0.8 | + +From table 5.2.3.3-3 and table 5.2.3.3-4 for 39GHz, we can see no matter for CP- OFDM and DFT-s-OFDM: + +The EVM floors of Example 1-based from vivo and Anritsu is better than example 2, but still worse than -29.1 dB EVM requirement for 256QAM. + +And the EVM floors of the new phase noise profiles that adopting min(Example 1-based, Example 2) and from MTK are reduced obviously compared to Example 1-based and Example 2. + +Further compared new phase noise profiles from adopting min(Example 1-based, Example 2) and MTK, we can see the EVM floor of MTK's phase noise profile is better a little than that adopting min(Example 1-based, Example 2) a little when without PTRS correction. But the EVM floor of MTK's phase noise profile is worse a little than that adopting min(Example 1-based, Example 2) when with PTRS correction. + +These two new phase noise profiles that adopting min(Example 1-based, Example 2) and from MTK have better EVM floor than -29.1 dB EVM requirement for 256QAM whether adding PTRS correction or not for both of CP-OFDM and DFT-S-OFDM, from this point, both of them can be used in MPR simulation. + +But considering phase noise profiles that adopting min(Example 1-based, Example 2) hasn't clearly physical description, we can use the new phase noise profile from MTK in MPR simulation. + +#### 5.2.3.4 Simulation results from vivo + +R4-2308227 + +In the simulation, distortion other than phase noise is not considered, e.g., PA non-linearity, transceiver impairment, etc., to ensure the results only show the feasibility of different phase noise profiles. + +The simulation results for 29GHz bands are shown in Table 5.2.3.4-1 + +**Table 5.2.3.4-1 simulation results for 29GHz band** + +| 64RB | | EVM no correction | EVM with correction | benefit | +|------------|----------|-------------------|---------------------|---------| +| CP-OFDM | Option 1 | -28.3288 | -28.9129 | 0.5841 | +| | Option 2 | -25.3244 | -25.5883 | 0.2639 | +| | Option 3 | -31.7997 | -33.0798 | 1.2801 | +| | Option 4 | -33.0942 | -33.3608 | 0.2666 | +| DFT-s-OFDM | Option 1 | -28.8567 | -27.1551 | -1.7016 | +| | Option 2 | -25.4507 | -28.9614 | 3.5107 | +| | Option 3 | -32.8215 | -29.8556 | -2.9659 | +| | Option 4 | -33.2358 | -30.0408 | -3.195 | + +Based on the simulation results, we have the following observations: + +**Observation 1: The phase noise profile described in option 1 and option 2 is not feasible for the 29GHz band.** + +**Observation 2: CP-OFDM can benefit from PTRS correction in UL 256QAM but DFT-s-OFDM can't.** + +The simulation results for 39GHz are shown in Table 5.2.3.4-2. + +**Table 5.2.3.4-2 simulation results for the 39GHz band** + +| 64RB | | EVM no correction | EVM with correction | benefit | +|------------|----------|-------------------|---------------------|---------| +| CP-OFDM | Option 1 | -25.1733 | -25.3235 | 0.1502 | +| | Option 2 | -22.7246 | -22.9743 | 0.2497 | +| | Option 3 | -29.8719 | -30.2049 | 0.333 | +| | Option 4 | -29.9468 | -30.182 | 0.2352 | +| DFT-s-OFDM | Option 1 | -25.3171 | -23.5189 | -1.7982 | +| | Option 2 | -22.8672 | -26.3839 | 3.5167 | +| | Option 3 | -30.0035 | -28.8569 | -1.1466 | +| | Option 4 | -30.0888 | -28.5366 | -1.5522 | + +It is noted that only phase noise is considered in the simulation and when other distortion needs to be counted in MPR evaluation, even under option 3 or option 4 phase noise, it is still challenging to achieve the 29.1 dB EVM requirement for UE. + +**Observation 5: Either option 3 or option 4 may still be infeasible for MPR evaluation in the 39GHz band.** + +#### 5.2.3.5 Simulation results from Anritsu Limited + +R4-2307043 + +![Line graph comparing four phase noise profiles for 29.55GHz carrier frequency. The y-axis is Phase noise (dBc/Hz) from -140.0 to -60.0. The x-axis is Frequency offset (Hz) from 1.E+03 to 1.E+09. The profiles are: 38.803 Example 1 (grey circles), 38.803 Example 2 (green squares), R4-2306603 Qualcomm Min(Example1,Example2) using pole-zero model (blue triangles), and R4-2306603 Mediatek (yellow squares). All profiles show a general downward trend as frequency offset increases, with Example 2 and Qualcomm Min showing the lowest phase noise at higher offsets.](fdae4b1c1863349bc913d92f62cc2eee_img.jpg) + +Comparison of the various phase noise profiles proposed for 29.55GHz carrier frequency + +| Frequency offset (Hz) | 38.803 Example 1 (dBc/Hz) | 38.803 Example 2 (dBc/Hz) | Qualcomm Min (dBc/Hz) | Mediatek (dBc/Hz) | +|-----------------------|---------------------------|---------------------------|-----------------------|-------------------| +| 1.E+03 | -70 | -70 | -70 | -70 | +| 1.E+04 | -80 | -80 | -85 | -85 | +| 1.E+05 | -85 | -85 | -95 | -95 | +| 1.E+06 | -100 | -100 | -105 | -105 | +| 1.E+07 | -115 | -120 | -125 | -125 | +| 1.E+08 | -130 | -135 | -140 | -140 | +| 1.E+09 | -140 | -140 | -140 | -140 | + +Line graph comparing four phase noise profiles for 29.55GHz carrier frequency. The y-axis is Phase noise (dBc/Hz) from -140.0 to -60.0. The x-axis is Frequency offset (Hz) from 1.E+03 to 1.E+09. The profiles are: 38.803 Example 1 (grey circles), 38.803 Example 2 (green squares), R4-2306603 Qualcomm Min(Example1,Example2) using pole-zero model (blue triangles), and R4-2306603 Mediatek (yellow squares). All profiles show a general downward trend as frequency offset increases, with Example 2 and Qualcomm Min showing the lowest phase noise at higher offsets. + +**Figure 5.2.3.5-1 Comparison of simulation results****Table 5.2.3.5-1: Simulation results for UE example 2 phase noise profile.** + +| Phase noise profile at 29.55GHz | 38_803 Example1 [5] | | 38_803 Example2 [5] | | Qualcomm Min (38_803 Example1, 38_803 Example2) using pole-zero model [7] | | MediaTek [7] | | +|---------------------------------|---------------------|---------|---------------------|---------|---------------------------------------------------------------------------|---------|--------------|---------| +| | SNR (dB) | EVM (%) | SNR (dB) | EVM (%) | SNR (dB) | EVM (%) | SNR (dB) | EVM (%) | +| Fmin used in integration (Hz) | | | | | | | | | +| 1.00E+03 | 26.05 | 5.0 | 28.2 | 3.9 | 27.8 | 4.1 | 29.4 | 3.4 | +| 1.00E+04 | 28.34 | 3.8 | 28.5 | 3.8 | 31.8 | 2.6 | 32.3 | 2.4 | +| 1.00E+05 | 28.65 | 3.7 | 28.6 | 3.7 | 32.5 | 2.4 | 32.7 | 2.3 | +| 1.00E+06 | 29.08 | 3.5 | 31.9 | 2.5 | 33.7 | 2.1 | 33.3 | 2.2 | +| 1.00E+07 | 33.3 | 2.2 | 41.6 | 0.8 | 41.9 | 0.8 | 37.5 | 1.3 | + +Note: Fmax is fixed to 100MHz in the calculations. + +The phase noise profiles from MediaTek and Qualcomm improves the SNR by about 3.5dB compare to the case of the Example 1 and Example phase noise profiles. + +**Observation 1: Both the MediaTek and Qualcomm phase noise profiles allow UL 256QAM to be feasible in terms of phase noise profile at 29.55GHz.** + +![Line graph comparing four phase noise profiles at 39GHz carrier frequency. The x-axis is Frequency offset (Hz) from 1.E+03 to 1.E+09. The y-axis is Phase noise (dBc/Hz) from -60.0 to -140.0. The profiles are: 38.803 Example 1 (grey circles), 38.803 Example 2 (green squares), Min(Example1, Example2) (blue triangles), and R4-2306603 Mediatek (yellow diamonds). All profiles show a general downward trend as frequency offset increases, with the Mediatek profile generally showing the lowest phase noise at higher offsets.](0eab48b5b15f7316f5c2521e7ba93b52_img.jpg) + +Comparison of the various phase noise profiles proposed for 39GHz carrier frequency + +| Frequency offset (Hz) | 38.803 Example 1 (dBc/Hz) | 38.803 Example 2 (dBc/Hz) | Min(Example1, Example2) (dBc/Hz) | R4-2306603 Mediatek (dBc/Hz) | +|-----------------------|---------------------------|---------------------------|----------------------------------|------------------------------| +| 1.E+03 | -65 | -68 | -70 | -72 | +| 1.E+04 | -78 | -80 | -82 | -85 | +| 1.E+05 | -85 | -88 | -90 | -92 | +| 1.E+06 | -95 | -98 | -100 | -102 | +| 1.E+07 | -105 | -108 | -110 | -112 | +| 1.E+08 | -115 | -118 | -120 | -122 | +| 1.E+09 | -130 | -130 | -132 | -135 | + +Line graph comparing four phase noise profiles at 39GHz carrier frequency. The x-axis is Frequency offset (Hz) from 1.E+03 to 1.E+09. The y-axis is Phase noise (dBc/Hz) from -60.0 to -140.0. The profiles are: 38.803 Example 1 (grey circles), 38.803 Example 2 (green squares), Min(Example1, Example2) (blue triangles), and R4-2306603 Mediatek (yellow diamonds). All profiles show a general downward trend as frequency offset increases, with the Mediatek profile generally showing the lowest phase noise at higher offsets. + +Figure 5.2.3.5-2 Comparison of simulation results – 2nd set of results + +**Table 5.2.3.5-2 Simulation results for UE example 2 phase noise profile.** + +| Phase noise profile at 39GHz | 38_803 Example1 [5] | | 38_803 Example2 [5] | | Qualcomm Min (38_803 Example1, 38_803 Example2) [2] – Option1 [6] | | MediaTek [7] | | +|-------------------------------|---------------------|---------|---------------------|---------|-------------------------------------------------------------------|---------|--------------|---------| +| | SNR (dB) | EVM (%) | SNR (dB) | EVM (%) | SNR (dB) | EVM (%) | SNR (dB) | EVM (%) | +| Fmin used in integration (Hz) | | | | | | | | | +| 1.00E+03 | 23.1 | 7.0 | 25.8 | 5.1 | 27.3 | 4.3 | 26.7 | 4.6 | +| 1.00E+04 | 25.0 | 5.6 | 26.1 | 5.0 | 28.7 | 3.7 | 29.4 | 3.4 | +| 1.00E+05 | 25.2 | 5.5 | 26.2 | 4.9 | 29.3 | 3.4 | 29.7 | 3.3 | +| 1.00E+06 | 25.6 | 5.3 | 29.5 | 3.3 | 30.3 | 3.1 | 30.2 | 3.1 | +| 1.00E+07 | 29.8 | 3.3 | 39.2 | 1.1 | 39.2 | 1.1 | 34.4 | 1.9 | + +Note: Fmax is fixed to 100MHz in the calculations. + +Using Min() phase noise profile improves the SNR by about 3.5dB compare to the case of the Example 1 and Example phase noise profiles. The phase noise profile by MediaTek is also giving about 2.5dB improvement of the SNR. + +**Observation 2: Both the MediaTek and Qualcomm phase noise profiles allow UL 256QAM to be feasible in terms of phase noise profile at 39GHz.** + +#### 5.2.3.6 Simulation results from MediaTek Inc. + +R4-2307931 + +To isolate the EVM impact of phase noise, no other types of impairments were added to the waveform. Table 5.2.3.6-1 and Table 5.2.3.6-2 show the initial simulated results. + +**Table 5.2.3.6-1 Benefit of PTRS in 256QAM, 64RB, 100MHz, SCS= 120kHz, CP-OFDM @29GHz** + +| CP-OFDM w/ phase noise, 256QAM, 120kHz, 64RB, DMRS based CPE removal | | | | | +|----------------------------------------------------------------------|--------------------|--------------------|-----------------------------------|---------------------| +| Phase noise model | PTRS configuration | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| TR38.803: UE example 1 | L = 1, K = 2 | -28.3 | -27.7 | 0.6 | +| Our proposal | L = 1, K = 2 | -32.7 | -31.6 | 1.1 | +| Qualcomm's proposal | L = 1, K = 2 | -32.5 | -30.7 | 1.8 | + +**Table 5.2.3.6-2 Benefit of PTRS in 256QAM, 64RB, 100MHz, SCS= 120kHz, CP-OFDM @39GHz** + +| CP-OFDM w/ phase noise, 256QAM, 120kHz, 64RB, DMRS based CPE removal | | | | | +|----------------------------------------------------------------------|--------------------|--------------------|-----------------------------------|---------------------| +| Phase noise model | PTRS configuration | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| TR38.803: UE example 1 | L = 1, K = 2 | -25.7 | -25.3 | 0.4 | +| Our proposal | L = 1, K = 2 | -29.6 | -28.7 | 0.9 | + +From Table 5.2.3.6-1, we can find that the EVM performance with our proposed phase noise profile is very close to Qualcomm's proposal at 29GHz after PTRS processing. Therefore, our proposal and Qualcomm's proposal for the phase noise profile can be used in 256QAM MPR evaluation for FR2-1. + +**Observation 1: EVM performance with our proposed phase noise profile is very close to Qualcomm's proposal at 29GHz after PTRS processing.** + +#### 5.2.3.7 Simulation results from LG Electronics + +R4-2308223 + +**Table 5.2.3.7-1 simulation assumption for phase noise** + +| Parameters | Value | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency | 29, 39 GHz | +| SCS | 120kHz | +| BW | 100MHz | +| RB Size | 64RB for 120kHz | +| Background AWGN | No additional noise | +| Time offset/Frequency offset | 0 | +| Antenna configuration | 1T1R | +| Modulation | 256QAM | +| Waveform type | CP-OFDM | +| DMRS | 3 symbols per slot (UL DMRS add-pos = 2) | +| PTRS configuration | ON
For CP-OFDM:
L-PTRS (Time density) = 1 (every 1 symbol)
K-PTRS (Freq density) = 2 (every 2 RBs) | +| EVM measurement | Data aided EVM calculation, based on ideal data signal | +| Phase noise profiles | For 29 GHz
Case 1:
Example 1 in TR 38.803 for 29 GHz
% fz = [3e3 550e3 280e6];
% fp = [1 1.6e6 30e6];
% alphaz = [2.37 2.7 2.53];
% alphap = [3.3 3.3 1];
% PSD0 = 29.35;

Case2:
Parameters from QC
% fz = [3e3 7e5 9e5];
% fp = [1 1e6 1.1e6];
% alphaz = [2.37 4.7 2];
% alphap = [3.3 5.3 2.5];
% PSD0 = 33;

Case 3:
Prameters from MTK
% fz = [3e3 550e3 280e6];
% fp = [1 1.6e6 30e6];
% alphaz = [2.37 2.7 2.53];
% alphap = [3.3 3.3 1];
% PSD0 = 29.35;

For 39 GHz
Case 4:
Parameters from Vivo
% fz = [3e3 494e3 418e6];
% fp = [1 1.58e6 30e6];
% alphaz = [2.37 2.7 2.53];
% alphap = [3.3 3.3 1];
% PSD0 = 34.41;

Case 5:
Parameters from Anritsu
% fz = [3e3 499e3 3.9e8];
% fp = [1 1.54e6 3e7];
% alphaz = [2.37 2.7 2.53];
% alphap = [3.3 3.3 1];
% PSD0 = 34.4;

Case 6:
Parameters from MTK
% fz = [3e3 620e3 240e6];
% fp = [1 1.6e6 30e6]; | + +| | | | +|--|---|---------------------------| +| | % | alphaz = [2.37 2.7 2.53]; | +| | % | alphap = [3.3 3.3 1]; | +| | % | PSD0 = 31.76; | + +**Table 5.2.3.7-2 CP-OFDM [29 GHz, 120KHZ, 100 MHz, 64RBs, (L=1, K=2)]** + +| | EVM (dB) | +|--------|----------| +| Case 1 | -30.75 | +| Case 2 | -31.57 | +| Case 3 | -31.37 | + +**Table 5.2.3.7-3 CP-OFDM [39 GHz, 120KHZ, 100 MHz, 64RBs, (L=1, K=2)]** + +| | EVM (dB) | +|--------|----------| +| Case 4 | -28.56 | +| Case 5 | -28.77 | +| Case 6 | -30.96 | + +We simulate EVM according to phase noise profiles and simulation results are shown in table 5.2.3.7-2 and table 5.2.3.7-3. + +For 29 GHz simulation results, we can observe the feasibility in case 1, case 2 and case 3. But, case 2 and case 3 phase noise profiles can achieve more EVM margin than case 1. + +**Observation 1:** For 29 GHz simulation results, we can observe the feasibility in case 1, case 2 and case 3. But, case 2 and case 3 phase noise profiles can achieve more EVM margin than case 1. + +For 39 GHz simulation results, we can observe the feasibility in only case 6. Case 4 and case 5 can not achieve below 3.5% EVM. + +**Observation 2:** For 39 GHz simulation results, we can observe the feasibility in only case 6. Case 4 and case 5 can not achieve below 3.5% EVM. + +#### 5.2.3.8 Simulation results from Sony + +R4-2309028 + +Multiple phase noise models have been proposed in the last few RAN4 meetings, and their contribution to the EVM noise floor based on the agreed simulation assumption in [1] is provided in table 5.2.3.8-1. Only results for 120 kHz SCS (64 RB) at 28 GHz are presented here, but other combinations of numerologies show a similar trend. + +**Table 5.2.3.8-1 The EVM performance with different phase noise profile in [1] for 120 kHz SCS at 28 GHz** + +| | CP-OFDM | DFTs-OFDM | +|-----------------------|----------|-----------| +| Ex.1 from TR 38.803 | -28.3 dB | -26.9 dB | +| Model proposed by QC | -32.9 dB | -31.4 dB | +| Model proposed by MTK | -33 dB | -31.4 dB | + +Reusing example 1 in TR 38.803 may cause an excessive EVM floor, which is not feasible for MPR evaluation for 256 QAM in our view. In addition, we shall notice that the 256 QAM is mainly targeted for FWA/CPE type of devices, which shall be capable of taking advantage of better-performed RF components than mobile handsets. Meanwhile, to leave sufficient EVM margin for other components, e.g., PA, IQ imbalance, it is necessary for the device to strive to achieve a better phase noise performance. + +Observation 1: the phase noise examples in TR38.803 does not leave enough EVM margin for 256QAM evaluation. + +Physical-wise, the phase noise at different frequency offsets is usually dominated by various components inside a PLL, including the VCO, the reference clock, and other associated circuitry. In our view, combining different phase noise + +profiles is physically viable. Therefore, it is proposed to adopt the improved phase noise model as a baseline for MPR evaluation. + +#### 5.2.3.9 Simulation results from Qualcomm + +R4-2300707 + +The penalties from PTRS corrections work against any benefit the PTRS brings in reducing the impact of phase noise. The benefit is a strong function of the phase noise profile, due to the nature of PTRS corrections. The variable benefit cannot be generalized across implementations. The net benefit is the EVM benefit when PTRS processing is enabled despite the penalties discussed previously. The phase noise profiles used below are merely examples for calibration across companies, neither seems particularly worthy of 256QAM. + +In the presence of phase noise, the DMRS symbols themselves have some CPE associated with them. The EVM algorithm can either ignore them and find the best channel estimate despite the phase noise, or it can de-rotate each DMRS symbol to nominal phase, along with the PUSCH symbols around the DMRS symbol. This latter variant is termed ‘DMRS based CPE removal’ in the tables below. + +Tables 5.2.3.9-1 and -2 shows the net impact of PTRS calculations in the presence of phase noise for CP-OFDM with 64 RBs. + +**Table 5.2.3.9-1: Net benefit for CP-OFDM with PTRS correction, DMRS based CPE removal** + +| CP-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal | | | | +|---------------------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile from TR38.803 | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE example 2 @ 45 GHz | -21.8 | -20.6 | 1.2 | +| UE example 1 @ 45 GHz | -24.8 | -24.5 | 0.3 | + +**Table 5.2.3.9-2: Net benefit for CP-OFDM with PTRS correction** + +| CP-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, no DMRS based CPE removal | | | | +|------------------------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile from TR38.803 | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE example 2 @ 45 GHz | -20.8 | -19.1 | 1.7 | +| UE example 1 @ 45 GHz | -23.8 | -23.0 | 0.8 | + +**Table 5.2.3.9-3: 30 GHz EVM floor in relation to -29.2 dB EVM requirement for 256QAM** + +| CP-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal | | | | +|---------------------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile from TR38.803 | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE example 1 @ 30 GHz | -30.1 | -29.7 | 0.4 | +| UE example 2 @ 30 GHz | -25.5 | -24.2 | 1.3 | + +Tables 5.2.3.9-4 and -5 shows the net impact of PTRS calculations in the presence of phase noise for DFT-s-OFDM. These projections are somewhat revised from earlier estimates due to algorithm development. + +**Table 5.2.3.9-4: Net benefit for DFT-s-OFDM with PTRS correction, DMRS based CPE removal** + +| DFT-s-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal | | | | +|------------------------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile from TR38.803 | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE example 2 @ 45 GHz | -24.6 | -20.5 | 4.1 | +| UE example 1 @ 45 GHz | -23.5 | -24.6 | -1.1 | + +**Table 5.2.3.9-5: Net benefit for DFT-s-OFDM with PTRS correction** + +| DFT-s-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, no DMRS based CPE removal | | | | +|---------------------------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile from TR38.803 | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE example 2 @ 45 GHz | -23.8 | -19.2 | 4.6 | +| UE example 1 @ 45 GHz | -22.5 | -23.0 | -0.5 | + +**Table 5.2.3.9-6: 30 GHz EVM floor in relation to -29.2 dB EVM requirement for 256QAM** + +| DFT-s-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal | | | | +|------------------------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile from TR38.803 | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE example 1 @ 30 GHz | -28.9 | -29.7 | -0.8 | +| UE example 2 @ 30 GHz | -28.0 | -24.2 | 3.8 | + +##### **R4-2304601** + +In R4-2300707, we proposed an UL256QAM-worthy phase noise profile out of the profiles in TR38.803 as follows: + +$$F_{\text{hybrid}}(f) = \min[F_{\text{ex1}}(f), F_{\text{ex2}}(f)]$$ + +The WF R4-2303491 also recorded another phase noise profile as a candidate, referred to simply as ‘option 2’ for brevity. Figures 2.1-1 shows the proposed profiles in relation to the phase noise profile in the TR. + +These profiles were evaluated with test signals with no impairment other than phase noise. While impractical, this simplification is useful to isolate the EVM impact due to phase noise and associated processing. Tables below summarize findings. Constellation diagrams are included in the Annex. + +![Figure 5.2.3.9-1: Proposed phase noise profiles for UL256QAM. The graph shows FR2 30G PN profiles (dBc/Hz) versus Offset frequency (Hz) on a log-log scale. Four curves are plotted: 3GPP 30 GHz ex1 (blue solid line), 3GPP 30 GHz ex2 (orange solid line), option2 (yellow solid line), and hybrid 3GPP 30 (black dashed line with asterisks). The hybrid profile follows the minimum of ex1 and ex2, showing a sharp drop around 10^6 Hz offset frequency.](38ddc1935b2416f874d07574fe8fc005_img.jpg) + +Figure 5.2.3.9-1: Proposed phase noise profiles for UL256QAM. The graph shows FR2 30G PN profiles (dBc/Hz) versus Offset frequency (Hz) on a log-log scale. Four curves are plotted: 3GPP 30 GHz ex1 (blue solid line), 3GPP 30 GHz ex2 (orange solid line), option2 (yellow solid line), and hybrid 3GPP 30 (black dashed line with asterisks). The hybrid profile follows the minimum of ex1 and ex2, showing a sharp drop around 10^6 Hz offset frequency. + +**Figure 5.2.3.9-1: Proposed phase noise profiles for UL256QAM** + +| CP-OFDM, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal | | | | +|------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| 30G Hybrid | -33.5 | -32.7 | 0.8 | +| 40G Hybrid | -30.1 | -29.2 | 0.9 | +| Option 2 | -28.4 | -28.1 | 0.3 | + +| DFT-s-OFDM, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal | | | | +|---------------------------------------------------------------------|--------------------|-----------------------------------|---------------------| +| Phase noise profile | EVM (dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| 30G Hybrid | -32.7 | -32.8 | -0.1 | +| 40G Hybrid | -29.4 | -29.2 | 0.2 | +| Option 2 | -26.9 | -28.1 | -1.2 | + +Given the EVM requirement of -29.1 dB, FR2-1 UEs that can reasonably support UL256QAM seem to be limited to 24-30 GHz. It further appears that the ‘Option 2’ profile has too much high-offset phase noise to support 256QAM. We therefore propose to adopt the only phase noise profile that seems able to support UL256QAM among the WF options. A further consideration is to use the favorable 30 GHz phase noise assumption to establish requirements that advanced UEs in the future can support in higher bands. + +**Observation 1: UL256QAM looks infeasible with the ‘Option 2’ profile [WF R4-2303491] even for n257, n258 and n261.** + +#### 5.2.3.10 Simulation results from ZTE + +R4-2304689 + +There were two new phase noise models proposed in last meeting, one is to adopt (example 1, example 2), and the other one is to adopt new parameters based on the multi-pole/zero model. By considering the existing two ones, there are four phase noise model alternatives as below: + +Alternative 1. example 1 defined in 38803 + +Alternative 2. example 2 defined in 38803 + +Alternative 3. min(example 1, example 2) + +Alternative 4. example 1 defined in 38803 with parameters updated + +Figure 5.2.3.10-1 shows the phase noise profiles for different alternatives. + +![Figure 5.2.3.10-1: Phase noise profile comparison between different alternatives. The graph shows UE phase noise @45GHz (PSD in dBc/Hz) versus Frequency (Hz) on a log-log scale. Four curves are plotted: alt1 (red solid line), alt2 (blue solid line), alt3 (black asterisks), and alt4 (cyan solid line). alt3 and alt4 show the lowest phase noise across the frequency range from 10^2 Hz to 10^10 Hz, with alt3 being slightly lower than alt4. alt1 and alt2 show higher phase noise, with alt2 being the highest.](4a343290f76ae7922954fa3e2b9c59ce_img.jpg) + +Figure 5.2.3.10-1: Phase noise profile comparison between different alternatives. The graph shows UE phase noise @45GHz (PSD in dBc/Hz) versus Frequency (Hz) on a log-log scale. Four curves are plotted: alt1 (red solid line), alt2 (blue solid line), alt3 (black asterisks), and alt4 (cyan solid line). alt3 and alt4 show the lowest phase noise across the frequency range from 10^2 Hz to 10^10 Hz, with alt3 being slightly lower than alt4. alt1 and alt2 show higher phase noise, with alt2 being the highest. + +**Figure 5.2.3.10-1. Phase noise profile comparison between different alternatives** + +From figure 5.2.3.10-1 we can find that lower phase noise can be achieved by alternative 3 and alternative 4 compared to the example 1 and example 2. In table 5.2.3.10-1, we compare the EVM performance for the above alternatives for CP-OFDM@45GHz, which is same conditions as in companies' paper in last meeting. + +**Table 5.2.3.10-1 EVM comparison between different alternatives** + +| CP-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal@45GHz | | | | +|--------------------------------------------------------------------------------|-------------------|-----------------------------------|---------------------| +| Phase noise | EVM(dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE alt 1 | -24.7 | -24.5 | 0.2 | +| UE alt 2 | -21.5 | -20.4 | 1.1 | +| UE alt 3 | -30.4 | -28 | 2.4 | +| UE alt 4 | -27.3 | -27.1 | 0.2 | + +From table 5.2.3.10-1 we can find that alt 3 can achieve much smaller phase noise which means much smaller EVM can be expected @ 45GHz. Although the simulation is for 45GHz, it is reasonable to expect that the same results can be applied for other millimeter wave frequency. + +For alt 3, although smallest phase noise can be achieved, the logic to minimize both example 1 and example 2 may not be clear. As explained in TS38.803, example 1 is based upon measurements made on a prototype CMOS device, with a larger PLL bandwidth, and example 2 is based on recent research on technology capabilities for UE and BS where CMOS is considered for the UE and GaAs is considered for the BS, so a lower PLL bandwidth than example 1 can be assumed for + +example2. It is clearly that Example 2 distinguishes UE and BS while example 1 is the common model for both UE and BS, from this perspective, the reasons for directly taking the minimum value of both, min(Ex 1, Ex 2), are not very clear. Nevertheless, we still believe the lower phase noise can not only improve the EVM performance, but also improve the MPR requirements. + +**Observation 1: Smallest phase noise can be achieved for Alt 3, i.e. min(Ex1, Ex2), and lower EVM caused by phase noise can be expected.** + +#### 5.2.3.11 Summary the simulation results for 29GHz phase noise profile evaluation + +CP-OFDM: + +| Companies | Waveform | Phase noise model @29GHz | SCS, NRB | PTRS configuration | EVM (dB) with no PTRS | EVM (dB) with PTRS corrections | Net benefit of PTRS | +|--------------------|----------|--------------------------|--------------|--------------------|-----------------------|--------------------------------|---------------------| +| Xiaomi R4-2308805 | CP-OFDM | UE example 1 | 120kHz, 64RB | L = 1, K = 2 | -28.1 | -28.5 | 0.4 | +| | | UE example 2 | | | -23.6 | -25.3 | 1.7 | +| | | From Qualcomm | | | -31.9 | -33.1 | 1.2 | +| | | From MTK | | | -32.4 | -33.0 | 0.6 | +| Vivo R4-2308227 | CP-OFDM | UE example 1 | 120kHz, 64RB | L = 1, K = 2 | -28.3288 | -28.9129 | 0.5841 | +| | | UE example 2 | | | -25.3244 | -25.5883 | 0.2639 | +| | | From Qualcomm | | | -31.7997 | -33.0798 | 1.2801 | +| | | From MTK | | | -33.0942 | -33.3608 | 0.2666 | +| Anritsu R4-2307043 | CP-OFDM | UE example 1 | 120kHz, 64RB | | -28.65 | | | +| | | UE example 2 | | | -28.6 | | | +| | | From Qualcomm | | | -32.5 | | | +| | | From MTK | | | -32.7 | | | +| MTK R4-2307931 | CP-OFDM | UE example 1 | 120kHz, 64RB | L = 1, K = 2 | -27.7 | -28.3 | 0.6 | +| | | From Qualcomm | | | -30.7 | -32.5 | 1.8 | +| | | From MTK | | | -31.6 | -32.7 | 1.1 | +| LGE R4-2308223 | CP-OFDM | UE example 1 | 120kHz, 64RB | L = 1, K = 2 | | -30.75 | | +| | | From Qualcomm | | | | -31.57 | | +| | | From MTK | | | | -31.37 | | +| Sony R4-2309028 | CP-OFDM | UE example 1 | 120kHz, 64RB | | -28.3 dB | | | +| | | From Qualcomm | | | -32.9 dB | | | +| | | From MTK | | | -33 dB | | | + +DFT-s-OFDM: + +| Companies | Waveform | Phase noise model @29GHz | SCS, NRB | PTRS configuration | EVM (dB) with no PTRS | EVM (dB) with PTRS corrections | Net benefit of PTRS | +|-------------------|------------|--------------------------|--------------|-------------------------|-----------------------|--------------------------------|---------------------| +| Xiaomi R4-2308805 | DFT-s-OFDM | UE example 1 | 120kHz, 64RB | N_group = 8, N_samp = 4 | -28.2 | -27.1 | -1.1 | +| | | UE example 2 | | | -23.1 | -27.2 | 4.1 | +| | | From Qualcomm | | | -31.8 | -32.0 | 0.2 | +| | | From MTK | | | -32.4 | -31.7 | -0.7 | +| Vivo R4-2308227 | DFT-s-OFDM | UE example 1 | 120kHz, 64RB | N_group = 8, N_samp = 4 | -28.8567 | -27.1551 | -1.7016 | +| | | UE example 2 | | | -25.4507 | -28.9614 | 3.5107 | +| | | From Qualcomm | | | -32.8215 | -29.8556 | -2.9659 | +| | | From MTK | | | -33.2358 | -30.0408 | -3.195 | +| Sony R4-2309028 | DFT-s-OFDM | UE example 1 | 120kHz, 64RB | | -26.9 dB | | | +| | | From Qualcomm | | | -31.4 dB | | | +| | | From MTK | | | -31.4 dB | | | + +5.2.3.12 Summary the simulation results for 39GHz phase noise profile evaluation +CP-OFDM + +| Companies | Waveform | Phase noise model @39GHz | SCS, NRB | PTRS configuration | EVM (dB) with no PTRS | EVM (dB) with PTRS corrections | Net benefit of PTRS | +|--------------------|----------|---------------------------------|--------------|--------------------|-----------------------|--------------------------------|---------------------| +| Xiaomi R4-2308805 | CP-OFDM | Example 1 from VIVO | 120kHz, 64RB | L = 1, K =2 | -24.8 | -25.1 | 0.3 | +| | | Example 1 from Anritsu | | | -25.1 | -25.5 | 0.4 | +| | | Example 2 from TR38.803 | | | -20.9 | -22.7 | 1.8 | +| | | Min(Example1-VIVO, Example2) | | | -29.2 | -30.3 | 1.1 | +| | | Min(Example1-Anritsu, Example2) | | | -29.3 | -30.3 | 1.0 | +| | | From MTK | | | -29.4 | -30.0 | 0.6 | +| Vivo R4-2308227 | CP-OFDM | UE example 1 | 120kHz, 64RB | L = 1, K =2 | -25.1733 | -25.3235 | 0.1502 | +| | | UE example 2 | | | -22.7246 | -22.9743 | 0.2497 | +| | | From Qualcomm | | | -29.8719 | -30.2049 | 0.333 | +| | | From MTK | | | -29.9468 | -30.182 | 0.2352 | +| Anritsu R4-2307043 | CP-OFDM | UE example 1 | 120kHz, 64RB | | -25.2 | | | +| | | UE example 2 | | | -26.2 | | | +| | | From Qualcomm | | | -29.3 | | | +| | | From MTK | | | -29.7 | | | +| MTK R4-2307931 | CP-OFDM | UE example 1 | 120kHz, 64RB | L = 1, K =2 | -25.3 | -25.7 | 0.4 | +| | | From MTK | | | -28.7 | -29.6 | 0.9 | +| LGE R4-2308223 | CP-OFDM | Example 1 from VIVO | 120kHz, 64RB | L = 1, K =2 | | -28.56 | | +| | | Example 1 from Anritsu | | | | -28.77 | | +| | | From MTK | | | | -30.96 | | + +DFT-s-OFDM + +| Companies | Waveform | Phase noise model @39GHz | SCS, NRB | PTRS configuration | EVM (dB) with no PTRS | EVM (dB) with PTRS corrections | Net benefit of PTRS | +|-------------------|------------|---------------------------------|--------------|-------------------------|-----------------------|--------------------------------|---------------------| +| Xiaomi R4-2308805 | DFT-s-OFDM | Example 1 from VIVO | 120kHz, 64RB | N_group = 8, N_samp = 4 | -24.8 | -23.7 | -1.1 | +| | | Example 1 from Anritsu | | | -25.2 | -24.0 | -1.2 | +| | | Example 2 from TR38.803 | | | -20.5 | -24.4 | 3.9 | +| | | Min(Example1-VIVO, Example2) | | | -29.2 | -29.1 | -0.1 | +| | | Min(Example1-Anritsu, Example2) | | | -29.2 | -29.2 | 0.0 | +| | | From MTK | | | -29.5 | -28.7 | -0.8 | +| Vivo R4-2308227 | DFT-s-OFDM | UE example 1 | 120kHz, 64RB | N_group = 8, N_samp = 4 | -25.3171 | -23.5189 | -1.7982 | +| | | UE example 2 | | | -22.8672 | -26.3839 | 3.5167 | +| | | From Qualcomm | | | -30.0035 | -28.8569 | -1.1466 | +| | | From MTK | | | -30.0888 | -28.5366 | -1.5522 | + +### 5.2.4 MPR simulation + +#### 5.2.4.1 Simulation assumptions + +Antenna configuration and PA calibration point for MPR simulation + +The MPR evaluation was performed by using 32 PAs, 16 for each polarizations within an antenna array for PC1/2/5 keeping align with the antenna configuration agreed in system level simulation. + +PA calibration point should follow current definition in Spec 38.101-2: + +The waveform defined by BW = 100 MHz, SCS = 120 kHz, DFT-S-OFDM QPSK, 20RB23 is the reference waveform with 0 dB MPR and is used for the power class definition. + +Calculate MPR as total backoff needed for 256QAM from this calibration point. + +Emission requirements for MPR simulation + +Follow the current Spec 38.101-2, otherwise specified + +Occupied bandwidth (Table 6.5.1-1 in TS 38.101-2) + +General NR spectrum emission mask for FR2-1 (Table 6.5.2.1-1 in TS 38.101-2) + +NR ACLR1 for FR2-1 (Table 6.5.2.3-1 in TS 38.101-2) + +General in-band emissions limit for FR2-1 (Tables 6.4.2.3.2-1 for PC1, 6.4.2.3.3-1 for PC2, 6.4.2.3.6-1 for PC5 in TS 38.101-2) + +General NR spurious emission limits for FR2-1 (Table 6.5.3-2 in TS 38.101-2) + +Maximum error vector magnitude (EVM) 3.5% for 29GHz and 39GHz as agreed in RAN4 #104-bis-e meeting. + +-25dB/-20dB IQ image and -25dBc/-20dBc carrier leakage should be improved for UE supporting UL 256QAM. + +There is no change of the requirements for other modulation orders + +It shall be better than -36dB IQ image and -36dBc carrier leakage for UL 256QAM. + +EVM budget for MPR evaluation: + +Only consider the total value of 3.5% for Tx EVM + +Companies need to clarify the components of Tx EVM in their simulation results, including + +Phase noise + +Value for IQ imbalance + +PA and transmitter non-linearity + +Phase noise profiles for MPR simulation: + +For 29GHz: + +Both of new phase noise profiles from Qualcomm and MTK for 29GHz are feasible for MPR simulation. + +New phase noise profiles using the pole-zero method based on following function: + +Parameters from Qualcomm + +| PSD0 | 32 dB | | | | +|--------|-----------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 6e5 | 4.7 | 8e5 | 5.3 | +| 3 | 8e5 | 2.0 | 1.1e6 | 2.5 | + +Parameters from MTK + +Parameters for 29.55 GHz PLL phase noise model + +| PSD0 | 860.4 (29.35dB) | | | | +|--------|-----------------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 660e3 | 2.7 | 1.6e6 | 3.3 | +| 3 | 182e6 | 2.53 | 30e6 | 1 | + +For 39GHz: + +The new phase noise profile from MTK for 39GHz is feasible for MPR simulation. + +New phase noise profile using the pole-zero method based on following function: + +Parameters from MTK + +Parameters for 39 GHz PLL phase noise model + +| PSD0 | 1498.7 (31.76dB) | | | | +|--------|------------------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 620e3 | 2.7 | 1.6e6 | 3.3 | +| 3 | 240e6 | 2.53 | 30e6 | 1 | + +PTRS configuration for MPR simulation: + +For CP-OFDM + +No PTRS configuration. + +For DFT-s-OFDM + +No PTRS configuration. + +#### 5.2.4.2 Simulation results from LGE + +R4-2304634 MPR simulation for PC1 and PC2 + +Clarification of EVM budget, PA model, Phase noise profile, PTRS configuration for CPE correction: + +##### EVM budget + +- For CP-OFDM (L=1, K=2), (64 RB, 120 kHz) + +| Tx EVM contributor | EVM (%) | SNR (dB) | +|--------------------------------|---------|----------| +| Phase Noise+IQ Imbalance | 2.95 | 30.6 | +| PA Non-linearity & Transmitter | 1.88 | 34.5 | +| Total | 3.50 | 29.1 | + +![Constellation diagram for CP-OFDM showing EVM_C = 2.95% / EVM_A = 2.98%](6d7be4b2b402e079f97685869580c864_img.jpg) + +Constellation diagram for CP-OFDM. The plot shows a dense cloud of orange points representing the received signal constellation. The axes are labeled 'Re[I]' (horizontal) and 'Im[I]' (vertical), ranging from -1.5 to 1.5. The title of the plot is $EVM_C = 2.95\% / EVM_A = 2.98\%$ . + +Constellation diagram for CP-OFDM showing EVM\_C = 2.95% / EVM\_A = 2.98% + +- For DFT-s-OFDM (no PTRS correction), (64 RB, 120 kHz) + +| Tx EVM contributor | EVM (%) | SNR (dB) | +|--------------------------------|---------|----------| +| Phase Noise+IQ Imbalance | 2.30 | 32.8 | +| PA Non-linearity & Transmitter | 2.64 | 31.6 | +| Total | 3.50 | 29.1 | + +![Constellation diagram for DFT-s-OFDM showing EVM_C = 2.30% / EVM_A = 2.30%](dffea0f06bd8a4658bc3394c7dbfdb5c_img.jpg) + +Constellation diagram for DFT-s-OFDM. The plot shows a dense cloud of orange points representing the received signal constellation. The axes are labeled 'Re[I]' (horizontal) and 'Im[I]' (vertical), ranging from -1.5 to 1.5. The title of the plot is $EVM_C = 2.30\% / EVM_A = 2.30\%$ . + +Constellation diagram for DFT-s-OFDM showing EVM\_C = 2.30% / EVM\_A = 2.30% + +- Using the 39 dBm PA model considering the Tx post loss for PC1 +- Using the 27 dBm PA model considering the Tx post loss for PC2 + +##### Phase noise profile + +- Using the example 1 in TR38.803. + +##### PTRS configuration for CPE correction + +- Using the PTRS (K=2, L=1) for CP-OFDM +- No PTRS for DFT-s-OFDM + +**Table 5.2.4.2-1 RB allocations** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| For PC1
Considered RB allocation for 100 MHz in FR2-1 256QAM MPR simulation
Region 1
DFT-s-OFDM : [Start RB position:22, allocated RB: 20]
CP-OFDM : [Start RB position:22, allocated RB: 22]
Region 2
DFT-s-OFDM : [Start RB position:16, allocated RB: 32]
CP-OFDM : [Start RB position:16, allocated RB: 32]
Outer RB allocations
DFT-s-OFDM : MAX([Start RB position:0, allocated RB: 64], [Start RB position:0, allocated RB: 10])
CP-OFDM : MAX([Start RB position:0, allocated RB: 66], [Start RB position:0, allocated RB: 10])

Considered RB allocation for 400 MHz in FR2-1 256QAM MPR simulation
Region 1
DFT-s-OFDM : [Start RB position:60, allocated RB: 60]
CP-OFDM : [Start RB position:66, allocated RB: 60]
Region 2
DFT-s-OFDM : [Start RB position:60, allocated RB: 120]
CP-OFDM : [Start RB position:66, allocated RB: 132]
Outer RB allocations
DFT-s-OFDM : MAX([Start RB position:0, allocated RB: 264], [Start RB position:0, allocated RB: 40])
CP-OFDM : MAX([Start RB position:0, allocated RB: 264], [Start RB position:0, allocated RB: 40])

For PC2
Considered RB allocation for 100 MHz in FR2-1 256QAM MPR simulation
Region 1 inner RB allocation
DFT-s-OFDM : [Start RB position:22, allocated RB: 20]
CP-OFDM : [Start RB position:23, allocated RB: 20]
Edge RB allocations
DFT-s-OFDM : MAX([Start RB position:0, allocated RB: 64], [Start RB position:0, allocated RB: 1], [Start RB position:0, allocated RB: 20])
CP-OFDM : MAX([Start RB position:0, allocated RB: 66], [Start RB position:0, allocated RB: 1], [Start RB position:0, allocated RB: 20])

Considered RB allocation for 400 MHz in FR2-1 256QAM MPR simulation
Region 1 inner RB allocation
DFT-s-OFDM : [Start RB position:88, allocated RB: 80] | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +CP-OFDM : [Start RB position:88, allocated RB: 88] + +Edge RB allocations + +DFT-s-OFDM : MAX([Start RB position:0, allocated RB: 240], [Start RB position:0, allocated RB: 1], [Start RB position:0, allocated RB: 80]) + +CP-OFDM : MAX([Start RB position:0, allocated RB: 264], [Start RB position:0, allocated RB: 1], [Start RB position:0, allocated RB: 80]) + +**Table 5.2.4.2-2 Simulated MPR results for PC1 UL256QAM** + +| CBW (100 MHz) | Region 1 [22, 20] | Limiting factor | Region 2 [16, 32] | Limiting factor | Outter 1 [0, 64] | Limiting factor | Outter 2 [0, 10] | Limiting factor | +|---------------|-------------------|-----------------|--------------------|-----------------|-------------------|-----------------|------------------|-----------------| +| DFT-s-OFDM | 8.04 | EVM | 8.05 | EVM | 8.38 | EVM | 6.68 | SEM | +| CBW (100 MHz) | Region 1 [22, 22] | Limiting factor | Region 2 [16, 32] | Limiting factor | Outter 1 [0, 66] | Limiting factor | Outter 2 [0, 10] | Limiting factor | +| CP-OFDM | 10.44 | EVM | 9.86 | EVM | 10.31 | EVM | 9.01 | EVM | +| CBW (400 MHz) | Region 1 [60, 60] | Limiting factor | Region 2 [60, 120] | Limiting factor | Outter 1 [0, 264] | Limiting factor | Outter 2 [0, 40] | Limiting factor | +| DFT-s-OFDM | 8.44 | EVM | 9.28 | EVM | 9.40 | EVM | 8.44 | EVM | +| CBW (400 MHz) | Region 1 [66, 60] | Limiting factor | Region 2 [66, 132] | Limiting factor | Outter 1 [0, 264] | Limiting factor | Outter 2 [0, 40] | Limiting factor | +| CP-OFDM | 10.86 | EVM | 11.96 | EVM | 10.76 | EVM | 11.96 | EVM | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-3 Simulated MPR results for PC2 UL256QAM** + +| CBW (100 MHz) | Region 1 [22, 20] | Limiting factor | Outter1 [0, 64] | Limiting factor | Outter 2 [0, 1] | Limiting factor | Outter 3 [0, 20] | Limiting factor | +|---------------|-------------------|-----------------|------------------|-----------------|-----------------|-----------------|------------------|-----------------| +| DFT-s-OFDM | 7.54 | EVM | 7.54 | EVM | 6.21 | EVM | 6.50 | EVM | +| CBW (100 MHz) | Region 1 [23, 20] | Limiting factor | Outter1 [0, 66] | Limiting factor | Outter 2 [0, 1] | Limiting factor | Outter 3 [0, 20] | Limiting factor | +| CP-OFDM | 9.48 | EVM | 9.50 | EVM | 8.27 | EVM | 9.05 | EVM | +| CBW (400 MHz) | Region 1 [88, 80] | Limiting factor | Outter1 [0, 240] | Limiting factor | Outter 2 [0, 1] | Limiting factor | Outter 3 [0, 80] | Limiting factor | +| DFT-s-OFDM | 8.91 | EVM | 8.91 | EVM | 7.19 | EVM | 7.84 | EVM | +| CBW (400 MHz) | Region 1 [88, 88] | Limiting factor | Outter1 [0, 264] | Limiting factor | Outter 2 [0, 1] | Limiting factor | Outter 3 [0, 80] | Limiting factor | +| CP-OFDM | 10.96 | EVM | 10.84 | EVM | 9.04 | EVM | 10.09 | EVM | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-4 Proposed MPRWT for power class 1, BWchannel ≤ 200 MHz, FR2-1** + +| Modulation | | MPR WT (dB), BWchannel ≤ 200 MHz | | | +|-----------------------------------------------------------------------------------------------------------|---------|---------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | 256 QAM | ≤ 10 | ≤ 9.5 | ≤ 9.5 | +| CP-OFDM | 256QAM | ≤ 12 | ≤ 12 | ≤ 11.5 | +| Note: 256 QAM MPR WT requirements can be applied for operating band n256, n258, n259 and n261. | | | | | + +**Table 5.2.4.2-5 Proposed MPRWT for power class 1, BWchannel = 400 MHz** + +| Modulation | | MPR WT (dB), BW channel = 400 MHz | | | +|------------|---------|---------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | 256 QAM | ≤ 11 | ≤ 10 | ≤ 11 | +| CP-OFDM | 256 QAM | ≤ 13.5 | ≤ 12.5 | ≤ 13.5 | + +Note: 256 QAM MPRWT requirements can be applied for operating band n256, n258, n259 and n261. + +**Table 5.2.4.2-6 Proposed MPRWT for power class 2, BWchannel ≤ 200 MHz, FR2-1** + +| Modulation | | MPR WT , BW channel ≤ 200 MHz | | +|------------|---------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 256 QAM | ≤ 9 | ≤ 9 | +| CP-OFDM | 256 QAM | ≤ 11 | ≤ 11 | + +Note: 256 QAM MPRWT requirements can be applied for operating band n256, n258, n259 and n261. + +**Table 5.2.4.2-7 Proposed MPRWT for power class 2, BWchannel = 400 MHz, FR2-1** + +| Modulation | | MPR WT , BW channel ≤ 400 MHz | | +|------------|---------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 256 QAM | ≤ 10.5 | ≤ 10.5 | +| CP-OFDM | 256 QAM | ≤ 12.5 | ≤ 12.5 | + +Note: 256 QAM MPRWT requirements can be applied for operating band n256, n258, n259 and n261. + +R4-2308223 MPR simulation for PC2 + +**Table 5.2.4.2-8 Simulated MPR results for 29 GHz PC2 UL256QAM** + +| CBW (100 MHz) | PN profile | Region 1 [22, 20] | Outer1 [0, 64] | Outter 2 [0, 1] | Outter 3 [0, 20] | +|---------------|------------|-------------------|-----------------|-----------------|------------------| +| DFT-s-OFDM | Case 1 | 7.54 | 7.54 | 6.21 | 6.50 | +| | Case 2 | 7.22 | 7.34 | 5.96 | 6.18 | +| | Case 3 | 7.22 | 7.22 | 6.00 | 6.19 | +| CBW (100 MHz) | PN profile | Region 1 [23, 20] | Outer1 [0, 66] | Outter 2 [0, 1] | Outter 3 [0, 20] | +| CP-OFDM | Ex1 | 9.48 | 9.50 | 8.27 | 9.05 | +| | QC's | 9.26 | 9.27 | 8.04 | 8.72 | +| | MDK's | 9.26 | 9.26 | 7.74 | 8.83 | +| CBW (400 MHz) | PN profile | Region 1 [88, 80] | Outer1 [0, 240] | Outter 2 [0, 1] | Outter 3 [0, 80] | +| DFT-s-OFDM | Ex1 | 8.91 | 8.91 | 7.19 | 7.84 | +| | QC's | 8.06 | 8.06 | 7.10 | 7.33 | +| | MDK's | 8.48 | 8.06 | 7.11 | 7.44 | +| CBW (400 MHz) | PN profile | Region 1 [88, 88] | Outer1 [0, 264] | Outter 2 [0, 1] | Outter 3 [0, 80] | +| CP-OFDM | Ex1 | 10.96 | 10.84 | 9.04 | 10.09 | +| | QC's | 10.30 | 10.30 | 9.10 | 9.76 | +| | MDK's | 10.19 | 10.30 | 8.96 | 9.75 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-9 MPR results for 29 GHz PC2 UL256QAM with margin** + +| CBW
(100 MHz) | | Inner RB allocations,
Region 1 | Edge RB allocations | +|--------------------------|----------|-------------------------------------------|----------------------------| +| DFT-s-OFDM | Example1 | 9 | 9 | +| | QC | 8.5 | 9 | +| | MDK | 8.5 | 8.5 | +| CP-OFDM | Example1 | 11 | 11 | +| | QC | 11 | 11 | +| | MDK | 11 | 11 | +| CBW
(400 MHz) | | Inner RB allocations,
Region 1 | Edge RB allocations | +| DFT-s-OFDM | Example1 | 10.5 | 10.5 | +| | QC | 9.5 | 9.5 | +| | MDK | 10 | 9.5 | +| CP-OFDM | Example1 | 12.5 | 12.5 | +| | QC | 12 | 12 | +| | MDK | 11.5 | 12 | + +In the last meeting, there was a concern that EVM 3.5% could not be achieved due to phase noise, or even if it was achieved, it would have a very large MPR, so new phase noise profiles that are more relaxed than the existing phase noise profile were proposed. In this clause, the simulated MPR values of PC2 UL 256QAM according to the phase noise profile are shown in Table 5 and Table 6. It was found that the MPR value for 29 GHz can be improved by 0~1 dB by using the phase noise profile of case 2 and case 3 compared to the existing case 1. + +**Observation 3:** The MPR value for 29 GHz can be improved by 0~1 dB by using the phase noise profile of case 2 and case 3 compared to the case 1. + +R4-2312237 MPR simulation for PC2 with low AM-PM distortion PA + +Table 5.2.4.2-10 phase noise profiles + +| | +|----------------------------------------------| +| For 29 GHz phase noise profile | +| option 1 (TR 38.803 Example 1) | +| % fz = [3e3 550e3 280e6]; | +| % fp = [1 1.6e6 30e6]; | +| % alphaz = [2.37 2.7 2.53]; | +| % alphap = [3.3 3.3 1]; | +| % PSD0 = 32; | +| option 2 (QC's) | +| % fz = [3e3 7e5 9e5]; | +| % fp = [1 1e6 1.1e6]; | +| % alphaz = [2.37 4.7 2]; | +| % alphap = [3.3 5.3 2.5]; | +| % PSD0 = 33; | +| option 3 (MTK's) | +| % fz = [3e3 550e3 280e6]; | +| % fp = [1 1.6e6 30e6]; | + +``` + +% alphaz = [2.37 2.7 2.53]; +% alphas = [3.3 3.3 1]; +% PSD0 = 29.35; +For 39 GHz phase noise profile +option 4 (MTK's) +% fz = [3e3 620e3 240e6]; +% fp = [1 1.6e6 30e6]; +% alphaz = [2.37 2.7 2.53]; +% alphas = [3.3 3.3 1]; +% PSD0 = 31.76; + +``` + +We recognize the AM-PM distortion is the key factor for the MPR value based on our mmWave transceiver system. So, we performed MPR simulation with low AM-PM distortion PA. The low AM-PM distortion PA has only few degrees distortion until the AM-AM drops. The MPR result comparison between general PA and Low AM-PM distortion PA are showed in table 2 for 29 GHz and table 3 for 39 GHz. + +##### **-DFT-s-OFDM for 100 MHz CBW** + +MPR value with Option2 phase noise profile and low AM-PM distortion PA **is improved about 1~1.5 dB** over MPR with Option2 phase noise profile only. + +##### **-CP-OFDM for 100 MHz CBW** + +MPR value with Option2 phase noise profile and low AM-PM distortion PA **is improved about 0.5~1 dB** over MPR using only Option2 phase noise profile. The CP-OFDM waveform has a high PAPR, so the AM-AM distortion is more critical to the MPR value. That's why the MPR improvement is less than DFT-s-OFDM when the lower AM-PM distortion PA is applied. + +##### **-DFT-s-OFDM for 400 MHz CBW** + +The MPR value with Option2 phase noise profile and low AM-PM distortion PA **is improved about 0~0.5 dB**. The limiting factor for 400 MHz DFT-s-OFDM is IBE&EVM, so it has low improvement. + +##### **-CP-OFDM for 400 MHz CBW** + +The MPR value with Option2 phase noise profile and low AM-PM distortion PA **is improved about 0~1 dB** over MPR using only Option2 phase noise profile. + +**Observation 1:** The lower MPR value with low AM-PM distortion PA than MPR value with general PA is observed. + +**Table 5.2.4.2-11 Simulated MPR results for 29 GHz PC2 UL256QAM** + +| | PA model | PN Profile | Region 1 [22, 20] | Outer1 [0, 64] | Outer 2 [0, 1] | Outer 3 [0, 20] | +|----------------------------------|----------------------|--------------------------|--------------------------|-----------------------|------------------------|------------------------| +| DFT-s-OFDM (CBW: 100 MHz) | General | Option 1 | 7.54 | 7.54 | 6.21 | 6.50 | +| | General | Option 2 | 7.22 | 7.34 | 5.96 | 6.18 | +| | General | Option 3 | 7.22 | 7.22 | 6.00 | 6.19 | +| | Low AM-PM distortion | Option 2 | 5.86 | 5.97 | 5.60 | 5.78 | +| CP-OFDM (CBW: 100 MHz) | General | Option 1 | 9.48 | 9.50 | 8.27 | 9.05 | +| | General | Option 2 | 9.26 | 9.27 | 8.04 | 8.72 | +| | General | Option 3 | 9.26 | 9.26 | 7.74 | 8.83 | +| | Low AM-PM distortion | Option 2 | 8.39 | 8.29 | 7.51 | 8.18 | +| | PN profile | Region 1 [88, 80] | Outer1 [0, 240] | Outer 2 [0, 1] | Outer 3 [0, 80] | Outer 3 [0, 20] | +| DFT-s-OFDM (CBW: 400 MHz) | General | Option 1 | 8.91 | 8.91 | 7.19 | 7.84 | +| | General | Option 2 | 8.48 | 8.06 | 7.10 | 7.33 | +| | General | Option 3 | 8.48 | 8.06 | 7.11 | 7.44 | +| | Low AM-PM distortion | Option 2 | 8.26 | 7.54 | 7.06 | 7.23 | +| CP-OFDM (CBW: 400 MHz) | General | Option 1 | 10.96 | 10.84 | 9.04 | 10.09 | +| | General | Option 2 | 10.30 | 10.30 | 9.10 | 9.76 | +| | General | Option 3 | 10.19 | 10.30 | 8.96 | 9.75 | +| | Low AM-PM distortion | Option 2 | 9.44 | 9.86 | 8.76 | 9.44 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-12 Simulated MPR results for 39 GHz PC2 UL256QAM** + +| | PA model | PN Profile | Region 1 [22, 20] | Outer1 [0, 64] | Outer 2 [0, 1] | Outer 3 [0, 20] | +|----------------------------------|----------------------|--------------------------|--------------------------|-----------------------|------------------------|------------------------| +| DFT-s-OFDM (CBW: 100 MHz) | General | Option 4 | 7.44 | 7.33 | 6.01 | 6.37 | +| | Low AM-PM distortion | Option 4 | 5.97 | 6.17 | 5.54 | 5.86 | +| CP-OFDM (CBW: 100 MHz) | General | Option 4 | 9.27 | 9.48 | 8.00 | 8.83 | +| | Low AM-PM distortion | Option 4 | 8.37 | 8.39 | 7.49 | 8.31 | +| | PN profile | Region 1 [88, 80] | Outer1 [0, 240] | Outer 2 [0, 1] | Outer 3 [0, 80] | Outer 3 [0, 20] | +| DFT-s-OFDM (CBW: 400 MHz) | General | Option 4 | 8.47 | 8.48 | 7.00 | 7.54 | +| | Low AM-PM distortion | Option 4 | 8.48 | 7.64 | 6.84 | 7.33 | +| CP-OFDM (CBW: 400 MHz) | General | Option 4 | 10.73 | 10.85 | 9.13 | 9.82 | +| | Low AM-PM distortion | Option 4 | 10.19 | 10.30 | 8.78 | 9.54 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-13 MPR results for 29 GHz PC2 UL256QAM with margin** + +| CBW
(100 MHz) | PA model | P/N profile | Inner RB allocations,
Region 1 | Edge RB allocations | +|--------------------------|----------------------|--------------------|-------------------------------------------|----------------------------| +| DFT-s-OFDM | General | Option 1 | 9 | 9 | +| | General | Option 2 | 8.5 | 9 | +| | General | Option 3 | 8.5 | 8.5 | +| | Low AM-PM distortion | Option 2 | 7.5 | 7.5 | +| CP-OFDM | General | Option 1 | 11 | 11 | +| | General | Option 2 | 11 | 11 | +| | General | Option 3 | 11 | 11 | +| | Low AM-PM distortion | Option 2 | 10 | 10 | +| CBW
(400 MHz) | PA model | P/N profile | Inner RB allocations,
Region 1 | Edge RB allocations | +| DFT-s-OFDM | General | Option 1 | 10.5 | 10.5 | +| | General | Option 2 | 9.5 | 9.5 | +| | General | Option 3 | 10 | 9.5 | +| | Low AM-PM distortion | Option 2 | 10 | 9 | +| CP-OFDM | General | Option 1 | 12.5 | 12.5 | +| | General | Option 2 | 12 | 12 | +| | General | Option 3 | 11.5 | 12 | +| | Low AM-PM distortion | Option 2 | 11 | 11.5 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-14 MPR results for 39 GHz PC2 UL256QAM with margin** + +| CBW
(100 MHz) | PA model | P/N profile | Inner RB allocations,
Region 1 | Edge RB allocations | +|--------------------------|----------------------|--------------------|-------------------------------------------|----------------------------| +| DFT-s-OFDM | General | Option 4 | 9 | 9 | +| | Low AM-PM distortion | Option 4 | 7.5 | 7.5 | +| CP-OFDM | General | Option 4 | 11 | 11 | +| | Low AM-PM distortion | Option 4 | 10 | 10 | +| CBW
(400 MHz) | PA model | P/N profile | Inner RB allocations,
Region 1 | Edge RB allocations | +| DFT-s-OFDM | General | Option 4 | 10 | 10 | +| | Low AM-PM distortion | Option 4 | 10 | 9 | +| CP-OFDM | General | Option 4 | 12 | 12.5 | +| | Low AM-PM distortion | Option 4 | 11.5 | 12 | + +[start RB position, allocated RB number] + +Table 4 and table 5 show the MPR value with the margin. We observed the MPR values using Low AM-PM distortion PA are lower than MPR value with general PA model. But, the characteristic of low AM-PM distortion PA is from our mmWave products, so we need to more margin for the MPR value with low AM-PM distortion. So, we propose the MPR value as the average of the MPR results using the general PA and the MPR results using the low AM-PM distortion PA. + +R4-2315540 MPR simulation for PC1 with low AM-PM distortion PA + +At the last RAN4#108 meeting, we provided our MPR simulation results R4-2312237 for FR2-1 UL256QAM PC2. We also ran the MPR simulation for PC1 in a similar manner, and the results are shown in Table 5.2.4.2-15 and 5.2.4.2-16. + +**Observation 1:** The lower MPR value with low AM-PM distortion PA than MPR value with general PA is observed. + +**Table 5.2.4.2-15 Simulated MPR results for 29 GHz PC1 UL256QAM** + +| | PA model | PN Profile | Region 1 [22, 20] | Region 2 [16, 32] | Outer 1 [0, 64] | Outer 2 [0, 10] | +|----------------------------------|----------------------|-------------------|--------------------------|---------------------------|-------------------------|------------------------| +| DFT-s-OFDM (CBW: 100 MHz) | General | Option 2 | 7.52 | 7.30 | 7.73 | 6.89 | +| | Low AM-PM distortion | Option 2 | 6.03 | 6.02 | 6.04 | 6.36 | +| | PA model | PN Profile | Region 1 [22, 22] | Region 2 [16, 32] | Outer 1 [0, 66] | Outer 2 [0, 10] | +| CP-OFDM (CBW: 100 MHz) | General | Option 2 | 8.89 | 9.54 | 9.53 | 8.90 | +| | Low AM-PM distortion | Option 2 | 8.67 | 8.67 | 8.67 | 8.05 | +| | PA model | PN Profile | Region 1 [60, 60] | Region 2 [60, 120] | Outer 1 [0, 240] | Outer 2 [0, 40] | +| DFT-s-OFDM (CBW: 400 MHz) | General | Option 2 | 8.03 | 8.44 | 8.86 | 7.93 | +| | Low AM-PM distortion | Option 2 | 7.62 | 7.82 | 7.52 | 8.03 | +| | PA model | PN Profile | Region 1 [60, 60] | Region 2 [60, 132] | Outer 1 [0, 264] | Outer 2 [0, 40] | +| CP-OFDM (CBW: 400 MHz) | General | Option 2 | 10.43 | 11.08 | 10.75 | 10.34 | +| | Low AM-PM distortion | Option 2 | 10.11 | 10.65 | 10.65 | 10.12 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-16 Simulated MPR results for 39 GHz PC1 UL256QAM** + +| | PA model | PN Profile | Region 1 [22, 20] | Region 2 [16, 32] | Outer 1 [0, 64] | Outer 2 [0, 10] | +|--|----------------------------------|-------------------|--------------------------|---------------------------|-------------------------|------------------------| +| | DFT-s-OFDM (CBW: 100 MHz) | General | Option 4 | 7.62 | 7.62 | 7.73 | +| | Low AM-PM distortion | Option 4 | 6.25 | 5.83 | 6.25 | 6.36 | +| | PA model | PN Profile | Region 1 [22, 22] | Region 2 [16, 32] | Outer 1 [0, 66] | Outer 2 [0, 10] | +| | CP-OFDM (CBW: 100 MHz) | General | Option 4 | 9.75 | 9.75 | 9.65 | +| | Low AM-PM distortion | Option 4 | 9.32 | 8.55 | 9.10 | 8.15 | +| | PA model | PN Profile | Region 1 [60, 60] | Region 2 [60, 120] | Outer 1 [0, 240] | Outer 2 [0, 40] | +| | DFT-s-OFDM (CBW: 400 MHz) | General | Option 4 | 8.13 | 8.86 | 9.18 | +| | Low AM-PM distortion | Option 4 | 7.82 | 8.13 | 8.44 | 7.72 | +| | PA model | PN Profile | Region 1 [60, 60] | Region 2 [60, 132] | Outer 1 [0, 264] | Outer 2 [0, 40] | +| | CP-OFDM (CBW: 400 MHz) | General | Option 4 | 10.64 | 11.38 | 11.96 | +| | Low AM-PM distortion | Option 4 | 10.32 | 10.87 | 10.86 | 10.22 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-17 MPR results for 29 GHz PC1 UL256QAM with margin** + +| CBW (100 MHz) | PA model | P/N profile | Region 1 | Region 2 | Outer | +|----------------------|----------------------|--------------------|-----------------|-----------------|--------------| +| DFT-s-OFDM | General | Option 2 | 9 | 9 | 9 | +| | Low AM-PM distortion | Option 2 | 7.5 | 7.5 | 8 | +| CP-OFDM | General | Option 2 | 10.5 | 11 | 11 | +| | Low AM-PM distortion | Option 2 | 10 | 10 | 10 | +| CBW (400 MHz) | PA model | P/N profile | Region 1 | Region 2 | Outer | +| DFT-s-OFDM | General | Option 2 | 9.5 | 10 | 10.5 | +| | Low AM-PM distortion | Option 2 | 9 | 9.5 | 9.5 | +| CP-OFDM | General | Option 2 | 12 | 12.5 | 12.5 | +| | Low AM-PM distortion | Option 2 | 11.5 | 12 | 12 | + +[start RB position, allocated RB number] + +**Table 5.2.4.2-18 MPR results for 39 GHz PC1 UL256QAM with margin** + +| CBW
(100 MHz) | PA model | P/N profile | Region 1 | Region 2 | Outer | +|--------------------------|----------------------|--------------------|-----------------|-----------------|--------------| +| DFT-s-OFDM | General | Option 4 | 9 | 9 | 9 | +| | Low AM-PM distortion | Option 4 | 8 | 7.5 | 8 | +| CP-OFDM | General | Option 4 | 11.5 | 11.5 | 11 | +| | Low AM-PM distortion | Option 4 | 11 | 10 | 10.5 | +| CBW
(400 MHz) | PA model | P/N profile | Region 1 | Region 2 | Outer | +| DFT-s-OFDM | General | Option 4 | 9.5 | 10.5 | 10.5 | +| | Low AM-PM distortion | Option 4 | 9.5 | 9.5 | 10 | +| CP-OFDM | General | Option 4 | 12 | 13 | 13.5 | +| | Low AM-PM distortion | Option 4 | 12 | 12.5 | 12.5 | + +[start RB position, allocated RB number] + +Table 5.2.4.2-17 and table 5.2.4.2-18 show the MPR value with the margin. We observed the MPR values using Low AM-PM distortion PA are lower than MPR value with general PA model. But, the characteristic of low AM-PM distortion PA is from our mmWave products, so we need to more margin for the MPR value with low AM-PM distortion. So, we propose the MPR value as the average of the MPR results using the general PA and the MPR results using the low AM-PM distortion PA. + +#### 5.2.4.3 Simulation results from Nokia + +R4-2311665 simulation results for DFT-s-OFDM PC1/PC2/PC5 + +To simulate the MPR we used the maximum allocation placed at the center of the channel. The phase noise is expected to increase with increasing size of the allocation, and the effect of the IQ imbalance is maximized at the center of the channel. + +In the simulations we use the multi-zero/pole model with Qualcomm's parameters. + +In all cases in the tables below we see the transmit power is limited by the EVM. This explains why the MPR is very similar for all the simulated power classes. + +The MPR simulation results with different PCs are provided in Tables 1-3, and the EVM budget is provided in Table 4. + +**Table 5.2.4.3-1. MPR simulation results for 256QAM with PC1.** + +| Waveform | SCS
[kHz] | Required back-off [dB] | | | | | +|-------------------|----------------------|--------------------------------|------------|------------|------------|------------| +| | | Channel bandwidth [MHz] | | | | Max | +| | | 50 | 100 | 200 | 400 | | +| DFT-S-OFDM | 60 | 7.1 | 7.1 | 7.2 | | 7.2 | +| | 120 | 7.1 | 7.0 | 7.1 | 7.2 | | + +**Table 5.2.4.3-2. MPR simulation results for 256QAM with PC2.** + +| Waveform | SCS
[kHz] | Required back-off [dB] | | | | | +|-------------------|----------------------|--------------------------------|------------|------------|------------|------------| +| | | Channel bandwidth [MHz] | | | | Max | +| | | 50 | 100 | 200 | 400 | | +| DFT-S-OFDM | 60 | 7.0 | 7.0 | 7.1 | | 7.1 | +| | 120 | 7.0 | 6.9 | 7.0 | 7.0 | | + +**Table 5.2.4.3-3. MPR simulation results for 256QAM with PC5.** + +| Waveform | SCS [kHz] | Required back-off [dB] | | | | Max | | +|------------|-----------|-------------------------|-----|-----|-----|-----|--| +| | | Channel bandwidth [MHz] | | | | | | +| | | 50 | 100 | 200 | 400 | | | +| DFT-S-OFDM | 60 | 7.1 | 7.3 | 7.3 | | 7.3 | | +| | 120 | 7.0 | 7.0 | 7.1 | 7.1 | | | + +**Table 5.2.4.3-4. EVM budget for DFT-s-OFDM at 29 GHz. RB start position 0, number of RBs 64, SCS 120 kHz.** + +| Tx EVM contributor | EVM (%) | +|--------------------------------|---------| +| Phase Noise+IQ Imbalance | 2.79 | +| PA Non-linearity & Transmitter | 2.11 | +| Total | 3.50 | + +R4-2315265 simulation results for CP-OFDM PC1/PC2/PC5 + +To simulate the MPR we used the full allocation as the phase noise is expected to increase with increasing size of the allocation. + +In the simulations at 29 GHz we use the multi-zero/pole model with Qualcomm's parameters. We do not use PTRS. + +In all cases in the tables below we see the transmit power is limited by the EVM. This explains why the MPR is very similar for all the simulated power classes. + +The MPR simulation results with different PCs are provided in Tables 5.2.4.3-5 to 5.2.4.3-7, and the EVM budget is provided in Table 5.2.4.3-8. + +**Table 5.2.4.3-5 MPR simulation results for 256QAM with PC1 at 29 GHz.** + +| Waveform | SCS [kHz] | Required back-off [dB] | | | | Max | | +|----------|-----------|-------------------------|-----|-----|-----|-----|--| +| | | Channel bandwidth [MHz] | | | | | | +| | | 50 | 100 | 200 | 400 | | | +| CP-OFDM | 60 | 8.8 | 8.8 | 8.9 | | 8.9 | | +| | 120 | 8.7 | 8.7 | 8.6 | 8.7 | | | + +**Table 5.2.4.3-6 MPR simulation results for 256QAM with PC2 at 29 GHz.** + +| Waveform | SCS [kHz] | Required back-off [dB] | | | | Max | | +|----------|-----------|-------------------------|-----|-----|-----|-----|--| +| | | Channel bandwidth [MHz] | | | | | | +| | | 50 | 100 | 200 | 400 | | | +| CP-OFDM | 60 | 8.9 | 8.9 | 8.8 | | 8.9 | | +| | 120 | 8.7 | 8.8 | 8.8 | 8.8 | | | + +**Table 5.2.4.3-7 MPR simulation results for 256QAM with PC5 at 29 GHz.** + +| Waveform | SCS [kHz] | Required back-off [dB] | | | | Max | | +|----------|------------|-------------------------|-----|-----|-----|------------|--| +| | | Channel bandwidth [MHz] | | | | | | +| | | 50 | 100 | 200 | 400 | | | +| CP-OFDM | 60 | 8.9 | 8.9 | 8.9 | | 8.9 | | +| | 120 | 8.7 | 8.7 | 8.8 | 8.9 | | | + +**Table 5.2.4.3-8 EVM budget for CP-OFDM at 29 GHz. RB start position 0, number of RBs 64, SCS 120 kHz.** + +| Tx EVM contributor | EVM (%) | +|--------------------------------|-------------| +| Phase Noise+IQ Imbalance | 2.81 | +| PA Non-linearity & Transmitter | 2.09 | +| Total | 3.50 | + +We notice that the backoff values from our simulations are smaller than other companies. This could result from differences in the linearity of the used power amplifier. We also studied the effect of the IQ imbalance that affects the EVM quota left for PA non-linearity and other transmitter impairments. For our results above we used IQ imbalance of -37.3dBc and carrier leakage of -31.6 dBc. When we used -36 dBc for both we obtained about 0.5 dB larger MPR values for CP-OFDMA. + +We also studied the phase noise contribution to EVM at 39 GHz without PTRS. We used the phase noise model from MTK. The results are presented in Table 5.2.4.3-9. + +**Table 5.2.4.3-9 Contribution of phase noise to EVM at 39 GHz. RB start position 0, number of RBs 64, SCS 120 kHz. PTRS was not used.** + +| waveform | EVM (%) | EVM (dB) | +|-------------------|---------|----------| +| DFT-s-OFDM | 3.26 | -29.74 | +| CP-OFDM | 3.27 | -29.71 | + +#### 5.2.4.4 Simulation results from ZTE + +R4-2314619 simulation results for PC1 + +Some initial MPR simulation results for 29GHz PC1 100MHz 256QAM DFT-s-OFDM and CP-OFDM are shown in Fig 5.2.4.4-1. + +![Figure 5.2.4.4-1: 29GHz PC1 MPR for 256QAM 100MHz. The figure contains two heatmaps. The left heatmap is for DFT-s-OFDM and the right is for CP-OFDM. Both plots show the relationship between 'Start RB' (x-axis, 0 to 60) and 'LCRB' (y-axis, 0 to 60). The color scale represents the MPR value in dB, ranging from 0 (blue) to 8 (red) for DFT-s-OFDM and 0 (blue) to 12 (red) for CP-OFDM. The DFT-s-OFDM plot shows a diagonal band of high MPR values, while the CP-OFDM plot shows a more extensive triangular region of high MPR values.](5b5673c03e7b6fc921c4a944dabf891e_img.jpg) + +Figure 5.2.4.4-1: 29GHz PC1 MPR for 256QAM 100MHz. The figure contains two heatmaps. The left heatmap is for DFT-s-OFDM and the right is for CP-OFDM. Both plots show the relationship between 'Start RB' (x-axis, 0 to 60) and 'LCRB' (y-axis, 0 to 60). The color scale represents the MPR value in dB, ranging from 0 (blue) to 8 (red) for DFT-s-OFDM and 0 (blue) to 12 (red) for CP-OFDM. The DFT-s-OFDM plot shows a diagonal band of high MPR values, while the CP-OFDM plot shows a more extensive triangular region of high MPR values. + +**Fig 5.2.4.4-1. 29GHz PC1 MPR for 256QAM 100MHz, DFT-s-OFDM(Left) and CP-OFDM (Right)** + +The maximum MPR@outer RB is 8.375dB and the maximum MPR@inner RB is 8.875dB for DFT-s-OFDM and 12.125dB for CP-OFDM. + +The EVM budget for the 64RB0 is provided in Table 5.2.4.4-2. + +**Table 5.2.4.4-2 EVM budget for PC1 256QAM 100MHz, DFT-s-OFDM, 64RB0** + +| Tx EVM contributor | EVM (%) | +|--------------------------------|---------| +| Phase Noise+IQ Imbalance | 2.93 | +| PA Non-linearity & Transmitter | 1.90 | +| Total | 3.50 | + +Therefore, the MPR requirements for 29GHz PC1 256QAM DFT-s-OFDM are proposed: + +**Table 5.2.4.4-3 MPR requirements for 29GHz PC1 256QAM DFT-s-OFDM ( $BW_{channel} \leq 200$ MHz)** + +| Modulation | | MPR WT (dB), $BW_{channel} \leq 200$ MHz | | | +|------------|-----------|-----------------------------------------------------|----------------------|-------------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 5.5$ | 0.0 | $\leq 3.0$ | +| | QPSK | $\leq 6.5$ | 0.0 | $\leq 3.0$ | +| | 16 QAM | $\leq 6.5$ | $\leq 4.0$ | $\leq 4.0$ | +| | 64 QAM | $\leq 6.5$ | $\leq 5.0$ | $\leq 5.0$ | +| | 256QAM | $\leq 8.5$ | $\leq 9.0$ | $\leq 9.0$ | +| CP-OFDM | QPSK | $\leq 7.0$ | $\leq 4.5$ | $\leq 4.5$ | +| | 16 QAM | $\leq 7.0$ | $\leq 5.5$ | $\leq 5.5$ | +| | 64 QAM | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | $\leq 12.5$ | $\leq 12.5$ | $\leq 12.5$ | + +R4-2315563 simulation results for PC1 using modified IQ image + +We update our simulation with better IQ image and carrier leakage value assumption, which are approximately -38dB IQ image and -38dBc carrier leakage. Besides, based on the conclusions in [1], neither DFT-s-OFDM nor CP-OFDM configures PT-RS. + +Except the above assumption updates for IQ image, carrier leakage and PT-RS, the other assumptions are kept which are from TR38.891. + +The updates for MPR simulation results for 29GHz PC1 100MHz 256QAM DFT-s-OFDM and CP-OFDM are shown in Fig 5.2.4.4-2. + +![Figure 5.2.4.4-2: 29GHz PC1 MPR for 256QAM 100MHz. The figure contains two heatmaps. The left heatmap is for DFT-s-OFDM and the right is for CP-OFDM. Both plots show LCRB (0 to 60) on the y-axis and Start RB (0 to 60) on the x-axis. The color scale for the left plot ranges from 0 to 7, and for the right plot from 0 to 10. The DFT-s-OFDM plot shows a diagonal band of high values, while the CP-OFDM plot shows a more complex pattern with multiple diagonal bands.](21998d5161d55a19df06b0ea8d3b4e59_img.jpg) + +Figure 5.2.4.4-2: 29GHz PC1 MPR for 256QAM 100MHz. The figure contains two heatmaps. The left heatmap is for DFT-s-OFDM and the right is for CP-OFDM. Both plots show LCRB (0 to 60) on the y-axis and Start RB (0 to 60) on the x-axis. The color scale for the left plot ranges from 0 to 7, and for the right plot from 0 to 10. The DFT-s-OFDM plot shows a diagonal band of high values, while the CP-OFDM plot shows a more complex pattern with multiple diagonal bands. + +Fig 5.2.4.4-2 29GHz PC1 MPR for 256QAM 100MHz, DFT-s-OFDM(Left) and CP-OFDM (Right) + +The EVM budget for the 64RB0 is provided in Table 5.2.4.4-4. + +Table 5.2.4.4-4 EVM budget for PC1 256QAM 100MHz, DFT-s-OFDM, 64RB0 + +| Tx EVM contributor | EVM (%) | +|--------------------------------|---------| +| Phase Noise+IQ Imbalance | 3.03 | +| PA Non-linearity & Transmitter | 1.83 | +| Total | 3.50 | + +The MPR simulation results for 29GHz PC1 400MHz 256QAM DFT-s-OFDM and CP-OFDM are shown in Fig 5.2.4.4-3. + +![Figure 5.2.4.4-3: 29GHz PC1 MPR for 256QAM 400MHz. The figure contains two heatmaps. The left heatmap is for DFT-s-OFDM and the right is for CP-OFDM. Both plots show LCRB (0 to 250) on the y-axis and Start RB (0 to 250) on the x-axis. The color scale for the left plot ranges from 0 to 7, and for the right plot from 0 to 10. The DFT-s-OFDM plot shows a diagonal band of high values, while the CP-OFDM plot shows a more complex pattern with multiple diagonal bands.](1326773262ea98ffa5f525b048dc04e3_img.jpg) + +Figure 5.2.4.4-3: 29GHz PC1 MPR for 256QAM 400MHz. The figure contains two heatmaps. The left heatmap is for DFT-s-OFDM and the right is for CP-OFDM. Both plots show LCRB (0 to 250) on the y-axis and Start RB (0 to 250) on the x-axis. The color scale for the left plot ranges from 0 to 7, and for the right plot from 0 to 10. The DFT-s-OFDM plot shows a diagonal band of high values, while the CP-OFDM plot shows a more complex pattern with multiple diagonal bands. + +Fig 5.2.4.4-3 29GHz PC1 MPR for 256QAM 400MHz, DFT-s-OFDM(Left) and CP-OFDM (Right) + +Therefore, the MPR requirements for 29GHz PC1 256QAM DFT-s-OFDM and CP-OFDM are proposed as follows. + +Table 5.2.4.4-5 MPR requirements for 29GHz PC1 256QAM DFT-s-OFDM and CP-OFDM ( $BW_{channel} \leq 200$ MHz) + +| Modulation | $MPR_{WT}$ (dB), $BW_{channel} \leq 200$ MHz | | | +|------------|----------------------------------------------|----------------------|----------| +| | Outer RB allocations | Inner RB allocations | | +| | | Region 1 | Region 2 | + +| | | | | | +|------------|-----------|-------------|-------------|-------------| +| DFT-s-OFDM | Pi/2 BPSK | $\leq 5.5$ | 0.0 | $\leq 3.0$ | +| | QPSK | $\leq 6.5$ | 0.0 | $\leq 3.0$ | +| | 16 QAM | $\leq 6.5$ | $\leq 4.0$ | $\leq 4.0$ | +| | 64 QAM | $\leq 6.5$ | $\leq 5.0$ | $\leq 5.0$ | +| | 256QAM | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| CP-OFDM | QPSK | $\leq 7.0$ | $\leq 4.5$ | $\leq 4.5$ | +| | 16 QAM | $\leq 7.0$ | $\leq 5.5$ | $\leq 5.5$ | +| | 64 QAM | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | $\leq 10.5$ | $\leq 10.5$ | $\leq 10.5$ | + +**Table 5.2.4.4-6 MPR requirements for 29GHz PC1 256QAM DFT-s-OFDM and CP-OFDM ( $BW_{channel} = 400$ MHz)** + +| Modulation | | $MPR_{WT}$ (dB), $BW_{channel} = 400$ MHz | | | +|------------|-----------|-------------------------------------------|----------------------|-------------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 5.5$ | 0.0 | $\leq 3.0$ | +| | QPSK | $\leq 6.5$ | 0.0 | $\leq 3.5$ | +| | 16 QAM | $\leq 6.5$ | $\leq 4.5$ | $\leq 4.5$ | +| | 64 QAM | $\leq 6.5$ | $\leq 6.5$ | $\leq 6.5$ | +| | 256QAM | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| CP-OFDM | QPSK | $\leq 7.0$ | $\leq 5.0$ | $\leq 5.0$ | +| | 16 QAM | $\leq 7.0$ | $\leq 6.5$ | $\leq 6.5$ | +| | 64 QAM | $\leq 9.0$ | $\leq 9.0$ | $\leq 9.0$ | +| | 256QAM | $\leq 10.5$ | $\leq 10.5$ | $\leq 10.5$ | + +#### 5.2.4.5 Simulation results from vivo + +R4-2312574 simulation results for PC1 + +The EVM budget for this simulation is shown in Table 5.2.4.5-1: + +**Table 5.2.4.5-1 EVM budget for 256QAM MPR evaluation** + +| Tx EVM budget | EVM (%) | +|--------------------------------|---------| +| Phase Noise & IQ Imbalance | 2.99 | +| PA Non-linearity & Transmitter | 1.82 | +| Total | 3.50 | + +In our simulation, the PTRS is only configured for CP-OFDM with $L = 1$ , $K = 2$ , and the 29GHz phase noise profile from MTK in [1] is used for all waveforms. + +$BW = 200$ MHz $SCS = 120$ kHz + +The simulation results are shown in Figure 5.2.4.5-1 + +![Figure 5.2.4.5-1: MPR simulation results for 256QAM when BW = 200MHz. The figure contains two plots. The left plot is for DFT-s-OFDM with 256QAM, SCS=120kHz, BW=200MHz. The right plot is for CP-OFDM with 256QAM, SCS=120kHz, BW=200MHz. Both plots show L_Carb (Y-axis, 0 to 120) versus RB_start (X-axis, 0 to 120). The legend indicates two regions: MPR < 8.6 dB (green) and MPR < 7.8 dB (blue) for DFT-s-OFDM, and MPR < 11.4 dB (green) and MPR < 10 dB (blue) for CP-OFDM.](4a8f09807c20be2a38e37e719a575eac_img.jpg) + +Figure 5.2.4.5-1: MPR simulation results for 256QAM when BW = 200MHz. The figure contains two plots. The left plot is for DFT-s-OFDM with 256QAM, SCS=120kHz, BW=200MHz. The right plot is for CP-OFDM with 256QAM, SCS=120kHz, BW=200MHz. Both plots show L\_Carb (Y-axis, 0 to 120) versus RB\_start (X-axis, 0 to 120). The legend indicates two regions: MPR < 8.6 dB (green) and MPR < 7.8 dB (blue) for DFT-s-OFDM, and MPR < 11.4 dB (green) and MPR < 10 dB (blue) for CP-OFDM. + +**Figure 5.2.4.5-1 MPR simulation results for 256QAM when BW = 200MHz** + +BW = 400 MHz SCS = 120kHz + +Due to time constraints, we don't finish all cases and as an alternative, we only give simulation results for cases that need to be verified in the test, which are specified in TS38.521-2 Table 6.2.2.4.1-3. + +| MPR (dB) | DFT-s-OFDM | CP-OFDM | +|-------------------------------------------------------------------|------------|---------| +| Outer_Full (DFT-s-OFDM: 256@0
CP-OFDM: 264@0) | 7.94 | 10.12 | +| Inner_Full_Region2(DFT-s-OFDM: 128@66
CP-OFDM: 132@66) | 8.51 | 10.64 | +| 8@0 | 7.76 | 9.18 | +| 8@NRB-8 | 7.74 | 9.64 | + +In our simulation, we find that the sole gating factor for 256QAM is EVM, and it is hard to further differentiate regions for MPR value since the inner region may require higher MPR due to the impact of the phase noise, carrier leakage, etc., so in our view, same MPR value can be applied to all regions which is similar to 64QAM with CP-OFDM. + +##### **Observation 2: The gating factor for 256 QAM is EVM only.** + +Another thing we noticed in the simulation results is that the MPR results are insensitive to the channel bandwidth. However, considering the challenge for real wideband device design, e.g., the droop effect at the bandwidth edge, the EVM of 400MHz may be further degraded which leads to higher MPR than previous simulation results, so it is proposed to reserve 1.5 dB margin for 400MHz case compared to 200MHz. + +##### **Observation 3: The 256QAM MPR simulation results are insensitive to the channel bandwidth but the challenge of wideband device design should be considered in MPR requirement.** + +##### **R4-2315808** + +In the last meeting, many simulation results of FR2 256QAM are provided, but one interesting issue was raised in the last meeting R4-2314677: + +##### **New issue: What's about the MPR for 39GHz?** + +Proposals + +Option 1: Defined the same MPR with 29GHz + +Option 2: Consider some margin for 39GHz because the phase noise profile performance between 29GHz and 39GHz is different + +Option 3: Others + +**Agreement:** + +##### FFS + +For other lower modulation orders, either PTRS configuration or phase noised is not considered in MPR evaluation and the evaluation results can be frequency agnostic, but in FR2 256QAM, the phase noise, which is closely related to the frequency, is inserted, so the MPR value may be different for different band. + +**Observation 1: The phase noise is not considered in the modulation order other than 256QAM in FR2.** + +**Observation 2: The phase noise profile is closely related to the frequency.** + +To compare the difference, the MPR simulation results are shown in following figures: + +![Figure 5.2.4.5-2: MPR simulation results for 256QAM without phase noise. The figure contains two plots. The left plot is titled 'DFT-s-OFDM 256QAM SCS = 120kHz BW = 200MHz' and the right plot is titled 'CP-OFDM 256QAM SCS = 120 kHz BW = 200MHz'. Both plots show the relationship between RB_start (x-axis, 0 to 120) and L_CRB (y-axis, 0 to 120). The legend indicates two regions: MPR < 7.7 dB (green) and MPR < 6.8 dB (blue) for DFT-s-OFDM, and MPR < 10.8 dB (green) and MPR < 9 dB (blue) for CP-OFDM. The plots show that without phase noise, the MPR is relatively low and stable across different resource block allocations.](c654787c0bbc1559e1c194ab74987529_img.jpg) + +Figure 5.2.4.5-2: MPR simulation results for 256QAM without phase noise. The figure contains two plots. The left plot is titled 'DFT-s-OFDM 256QAM SCS = 120kHz BW = 200MHz' and the right plot is titled 'CP-OFDM 256QAM SCS = 120 kHz BW = 200MHz'. Both plots show the relationship between RB\_start (x-axis, 0 to 120) and L\_CRB (y-axis, 0 to 120). The legend indicates two regions: MPR < 7.7 dB (green) and MPR < 6.8 dB (blue) for DFT-s-OFDM, and MPR < 10.8 dB (green) and MPR < 9 dB (blue) for CP-OFDM. The plots show that without phase noise, the MPR is relatively low and stable across different resource block allocations. + +**Figure 5.2.4.5-2 MPR simulation results for 256QAM without phase noise** + +![Figure 5.2.4.5-3: MPR simulation results for 256QAM with 28GHz phase noise. The figure contains two plots. The left plot is titled 'DFT-s-OFDM 256QAM SCS = 120kHz BW=200MHz' and the right plot is titled 'CP-OFDM 256QAM SCS=120kHz BW = 200MHz'. Both plots show the relationship between RB_start (x-axis, 0 to 120) and L_CRB (y-axis, 0 to 120). The legend indicates two regions: MPR < 8.6 dB (green) and MPR < 7.8 dB (blue) for DFT-s-OFDM, and MPR < 11.4 dB (green) and MPR < 10 dB (blue) for CP-OFDM. The plots show that with 28GHz phase noise, the MPR values are higher and more varied compared to the case without phase noise.](9b608887301fdfd2a3ccc9ae2b9bdb07_img.jpg) + +Figure 5.2.4.5-3: MPR simulation results for 256QAM with 28GHz phase noise. The figure contains two plots. The left plot is titled 'DFT-s-OFDM 256QAM SCS = 120kHz BW=200MHz' and the right plot is titled 'CP-OFDM 256QAM SCS=120kHz BW = 200MHz'. Both plots show the relationship between RB\_start (x-axis, 0 to 120) and L\_CRB (y-axis, 0 to 120). The legend indicates two regions: MPR < 8.6 dB (green) and MPR < 7.8 dB (blue) for DFT-s-OFDM, and MPR < 11.4 dB (green) and MPR < 10 dB (blue) for CP-OFDM. The plots show that with 28GHz phase noise, the MPR values are higher and more varied compared to the case without phase noise. + +**Figure 5.2.4.5-3 MPR simulation results for 256QAM with 28GHz phase noise** + +![Figure 5.2.4.5-4: MPR simulation results for 256QAM with 39GHz phase noise. The figure contains two plots. The left plot is for DFT-s-OFDM 256QAM SCS=120kHz BW=200MHz, showing L_CRB (0 to 120) vs RB_start (0 to 120). The right plot is for CP-OFDM 256QAM SCS=120kHz BW=200MHz, showing L_CRB (0 to 120) vs RB_start (0 to 120). Both plots show MPR values for different RB_start and L_CRB combinations, with color-coded regions for MPR < 11.5 dB (green) and MPR < 10.5 dB (blue) for DFT-s-OFDM, and MPR < 14 dB (green) and MPR < 12.5 dB (blue) for CP-OFDM.](a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg) + +Figure 5.2.4.5-4: MPR simulation results for 256QAM with 39GHz phase noise. The figure contains two plots. The left plot is for DFT-s-OFDM 256QAM SCS=120kHz BW=200MHz, showing L\_CRB (0 to 120) vs RB\_start (0 to 120). The right plot is for CP-OFDM 256QAM SCS=120kHz BW=200MHz, showing L\_CRB (0 to 120) vs RB\_start (0 to 120). Both plots show MPR values for different RB\_start and L\_CRB combinations, with color-coded regions for MPR < 11.5 dB (green) and MPR < 10.5 dB (blue) for DFT-s-OFDM, and MPR < 14 dB (green) and MPR < 12.5 dB (blue) for CP-OFDM. + +**Figure 5.2.4.5-4 MPR simulation results for 256QAM with 39GHz phase noise** + +Obviously the MPR value increase when phase noise is inserted and the value will be larger when frequency become higher, so we think it is reasonable to introduce $\Delta$ MPR to show the difference and the MPR table will defined based on the assumption without phase noise. + +#### 5.2.4.6 Simulation results from Xiaomi + +R4-2312686 simulation results for PC1 + +And the EVM budget is shown in Table 5.2.4.6-1: + +**Table 5.2.4.6-1 EVM budget in MPR simulation for 256QAM** + +| Tx EVM contributor | EVM (%) | SNR (dB) | +|--------------------------------|---------|----------| +| Phase Noise | 1.41 | 37 | +| IQ Imbalance(w/ compensation) | 1.70 | 35.4 | +| PA Non-linearity & Transmitter | 2.70 | 31.4 | +| Total | 3.49 | 29.1 | + +Based on above simulation parameters, we simulated different configurations: + +PC1 100MHz without PN and PTRS. + +PC1 100MHz with PN and PTRS. + +PC1 100MHz with PN and without PTRS. + +The simulation results for DFT-s-OFDM are shown in figure 5.2.4.6-1 to figure 5.2.4.6-3: + +![Heatmap titled 'DFT-s-OFDM 256QAM wo PN wo PT-RS' showing PC1 100MHz MPR for 256QAM without PN and PTRS for DFT-s-OFDM. The x-axis is RBstart (0-60) and the y-axis is LCRB (0-60). A color bar on the right indicates values from 0 to 12.](0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg) + +This heatmap displays the Power Management Ratio (PMR) for DFT-s-OFDM with 256QAM modulation, without Phase Noise (PN) and Phase Tracking Reference Signals (PTRS). The x-axis represents the starting Resource Block (RBstart) from 0 to 60, and the y-axis represents the Lowest Contiguous Resource Block (LCRB) from 0 to 60. The color scale on the right indicates PMR values ranging from 0 (dark blue) to 12 (yellow). The plot shows a diagonal band of higher PMR values (yellow/green) starting from the bottom-left and extending towards the top-right, indicating that the PMR is generally higher for configurations with lower RBstart and LCRB values. + +Heatmap titled 'DFT-s-OFDM 256QAM wo PN wo PT-RS' showing PC1 100MHz MPR for 256QAM without PN and PTRS for DFT-s-OFDM. The x-axis is RBstart (0-60) and the y-axis is LCRB (0-60). A color bar on the right indicates values from 0 to 12. + +Figure 5.2.4.6-1 PC1 100MHz MPR for 256QAM without PN and PTRS for DFT-s-OFDM + +![Heatmap titled 'DFT-s-OFDM 256QAM w PN w PT-RS' showing PC1 100MHz MPR for 256QAM with PN and PTRS for DFT-s-OFDM. The x-axis is RBstart (0-60) and the y-axis is LCRB (0-60). A color bar on the right indicates values from 0 to 12.](68f0e97e094e315c0ed95a24eb0585c3_img.jpg) + +This heatmap displays the Power Management Ratio (PMR) for DFT-s-OFDM with 256QAM modulation, with Phase Noise (PN) and Phase Tracking Reference Signals (PTRS). The axes and color scale are identical to Figure 5.2.4.6-1. The distribution of PMR values is similar, with a diagonal band of higher values (yellow/green) concentrated in the lower-left region of the plot. The presence of PN and PTRS appears to have a minimal impact on the overall PMR distribution compared to the case without them. + +Heatmap titled 'DFT-s-OFDM 256QAM w PN w PT-RS' showing PC1 100MHz MPR for 256QAM with PN and PTRS for DFT-s-OFDM. The x-axis is RBstart (0-60) and the y-axis is LCRB (0-60). A color bar on the right indicates values from 0 to 12. + +Figure 5.2.4.6-2 PC1 100MHz MPR for 256QAM with PN and PTRS for DFT-s-OFDM + +![Heatmap titled 'DFT-s-OFDM 256QAM w PN wo PT-RS' showing PC1 100MHz MPR for 256QAM with PN without PTRS for DFT-s-OFDM. The x-axis is RBstart (0 to 60) and the y-axis is LCRB (0 to 60). A color bar on the right indicates values from 0 to 12.](b71190d39f5e641548d0f091e94e663d_img.jpg) + +This heatmap displays the Power Management Ratio (PMR) for DFT-s-OFDM with 256QAM, Phase Noise (PN), and no Phase Tracking Reference Signals (PTRS). The x-axis represents the Resource Block start (RBstart) from 0 to 60, and the y-axis represents the Lowest Contiguous Resource Block (LCRB) from 0 to 60. The color scale ranges from 0 (dark blue) to 12 (yellow). The plot shows a diagonal band of higher PMR values (yellow/green) starting from the bottom-left and extending towards the top-right, indicating that PMR increases with both RBstart and LCRB. + +Heatmap titled 'DFT-s-OFDM 256QAM w PN wo PT-RS' showing PC1 100MHz MPR for 256QAM with PN without PTRS for DFT-s-OFDM. The x-axis is RBstart (0 to 60) and the y-axis is LCRB (0 to 60). A color bar on the right indicates values from 0 to 12. + +Figure 5.2.4.6-3 PC1 100MHz MPR for 256QAM with PN without PTRS for DFT-s-OFDM + +The simulation results for CP-OFDM are shown in figure 5.2.4.6-4 to figure 5.2.4.6-6: + +![Heatmap titled 'CP-OFDM 256QAM wo PN wo PT-RS' showing PC1 100MHz MPR for 256QAM without PN and PTRS for CP-OFDM. The x-axis is RBstart (0 to 60) and the y-axis is LCRB (0 to 60). A color bar on the right indicates values from 0 to 12.](a7a4135af81158a102df055b2138f981_img.jpg) + +This heatmap displays the Power Management Ratio (PMR) for CP-OFDM with 256QAM, without Phase Noise (PN) and without Phase Tracking Reference Signals (PTRS). The x-axis represents the Resource Block start (RBstart) from 0 to 60, and the y-axis represents the Lowest Contiguous Resource Block (LCRB) from 0 to 60. The color scale ranges from 0 (dark blue) to 12 (yellow). The plot shows a diagonal band of higher PMR values (yellow/green) starting from the bottom-left and extending towards the top-right, indicating that PMR increases with both RBstart and LCRB. + +Heatmap titled 'CP-OFDM 256QAM wo PN wo PT-RS' showing PC1 100MHz MPR for 256QAM without PN and PTRS for CP-OFDM. The x-axis is RBstart (0 to 60) and the y-axis is LCRB (0 to 60). A color bar on the right indicates values from 0 to 12. + +Figure 5.2.4.6-4 PC1 100MHz MPR for 256QAM without PN and PTRS for CP-OFDM + +![Figure 5.2.4.6-5: Heatmap titled 'CP-OFDM 256QAM w PN w PT-RS'. The x-axis is 'RBstart' (0 to 60) and the y-axis is 'LCRB' (10 to 60). A color bar on the right indicates values from 0 to 14. The heatmap shows a dense pattern of yellow and green horizontal bars, indicating high MPR values across most resource blocks.](decf37f29e8a82a8d6a742351ab68a24_img.jpg) + +Figure 5.2.4.6-5: Heatmap titled 'CP-OFDM 256QAM w PN w PT-RS'. The x-axis is 'RBstart' (0 to 60) and the y-axis is 'LCRB' (10 to 60). A color bar on the right indicates values from 0 to 14. The heatmap shows a dense pattern of yellow and green horizontal bars, indicating high MPR values across most resource blocks. + +Figure 5.2.4.6-5 PC1 100MHz MPR for 256QAM with PN and PTRS for CP-OFDM + +![Figure 5.2.4.6-6: Heatmap titled 'CP-OFDM 256QAM w PN wo PT-RS'. The x-axis is 'RBstart' (0 to 60) and the y-axis is 'LCRB' (10 to 60). A color bar on the right indicates values from 0 to 14. The heatmap shows a similar pattern to Figure 5.2.4.6-5 but with slightly fewer yellow and green bars, indicating lower MPR values in some regions.](aefc1d56f34faf0b81de8302e695340e_img.jpg) + +Figure 5.2.4.6-6: Heatmap titled 'CP-OFDM 256QAM w PN wo PT-RS'. The x-axis is 'RBstart' (0 to 60) and the y-axis is 'LCRB' (10 to 60). A color bar on the right indicates values from 0 to 14. The heatmap shows a similar pattern to Figure 5.2.4.6-5 but with slightly fewer yellow and green bars, indicating lower MPR values in some regions. + +Figure 5.2.4.6-6 PC1 100MHz MPR for 256QAM with PN without PTRS for CP-OFDM + +Table 5.2.4.6-2 shows the largest MPR values in each regions based on above figure 5.2.4.6-1 to figure 5.2.4.6-6. + +Table 5.2.4.6-2 MPRwt for power class 1, BWchannel =100 MHz in FR2-1 + +| Modulation | | MPR wt (dB), BW channel =100 MHz | | | +|------------|----------------|--------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | w/o PN | 11.7 | 11.7 | 11.4 | +| | w/ PN w/ PTRS | 12.8 | 12.3 | 11.4 | +| | w/ PN w/o PTRS | 13 | 12.8 | 12.1 | +| CP-OFDM | w/o PN | 12.4 | 13.2 | 12.5 | +| | w/ PN w/ PTRS | 14.9 | 14.5 | 14.1 | +| | w/ PN w/o PTRS | 14.5 | 13.9 | 13.9 | + +From Table 5.2.4.6-2, we can see the impact of phase noise to MPR value is about 1dB. And for DFT-s-OFDM, we can see about 0.5dB benefit when introducing the PTRS correction. But for CP-OFDM, there is no the benefit when introducing PTRS correction. + +R4-2315437 simulation results for PC1 using modified IQ image + +Based on above simulation parameters with modified IQ image -36dB, we simulated different configurations: + +PC1 200MHz and 400MHz with PN and no PTRS for 29GHz. + +And the EVM budget is shown in Table 5.2.4.6-3: + +**Table 5.2.4.6-3 EVM budget in MPR simulation for 256QAM** + +| Tx EVM contributor | EVM (%) | SNR (dB) | +|--------------------------------------------|---------|----------| +| IQ Imbalance(w/ compensation)+ Phase Noise | 2.8 | 31 | +| PA Non-linearity & Transmitter | 2.1 | 33 | +| Total | 3.5 | 29.1 | + +The simulation results for 200MHz channel bandwidth are shown in figure 5.2.4.6-7 and figure 5.2.4.6-8: + +![Heatmap titled 'DFT-s-OFDM 256QAM' showing MPR values across RBstart (0 to 120) and LCstart (0 to 120). The color scale ranges from 2 (blue) to 8 (red). The plot shows a diagonal band of higher values (yellow/red) starting from the bottom-left and extending towards the top-right, indicating a relationship between RBstart and LCstart.](a3010506e5136b6642bb97f569dc52a3_img.jpg) + +Heatmap titled 'DFT-s-OFDM 256QAM' showing MPR values across RBstart (0 to 120) and LCstart (0 to 120). The color scale ranges from 2 (blue) to 8 (red). The plot shows a diagonal band of higher values (yellow/red) starting from the bottom-left and extending towards the top-right, indicating a relationship between RBstart and LCstart. + +**Figure 5.2.4.6-7 PC1 200MHz MPR for 256QAM with PN and no PTRS for 29GHz DFT-s-OFDM** + +![Heatmap titled 'CP-OFDM 256QAM' showing MPR values across RBstart (0 to 120) and LCstart (0 to 120). The color scale ranges from 5 (blue) to 10 (red). Similar to the DFT-s-OFDM plot, it shows a diagonal band of higher values (yellow/red) indicating a relationship between RBstart and LCstart.](8ba6b5c123d6a3d796c2570e5975cff5_img.jpg) + +Heatmap titled 'CP-OFDM 256QAM' showing MPR values across RBstart (0 to 120) and LCstart (0 to 120). The color scale ranges from 5 (blue) to 10 (red). Similar to the DFT-s-OFDM plot, it shows a diagonal band of higher values (yellow/red) indicating a relationship between RBstart and LCstart. + +**Figure 5.2.4.6-8 PC1 200MHz MPR for 256QAM with PN and no PTRS for 29GHz CP-OFDM** + +Based on RB allocations regions of the channel bandwidths less than 200MHz for FR2-1 defined in current Spec as below: + +$N_{RB}$ is the maximum number of RBs for a given Channel bandwidth and sub-carrier spacing defined in Table 5.3.2-1 of TS 38.101-2. + +$$RB_{end} = RB_{Start} + L_{CRB} - 1$$ + +$$RB_{Start,Low} = \text{Max}(1, \text{Floor}(L_{CRB}/2))$$ + +$$RB_{Start,High} = N_{RB} - RB_{Start,Low} - L_{CRB}$$ + +An RB allocation is an Outer RB allocation if + +$$RB_{Start} < RB_{Start,Low} \text{ OR } RB_{Start} > RB_{Start,High} \text{ OR } L_{CRB} > \text{Ceil}(N_{RB}/2)$$ + +An RB allocation in the channel bandwidths less than 200MHz is a Region 1 inner RB allocation if + +$$RB_{start} \geq \text{Ceil}(1/3 N_{RB}) \text{ AND } RB_{end} < \text{Ceil}(2/3 N_{RB})$$ + +An RB allocation is a Region 2 inner allocation if it is NOT an Outer allocation AND NOT a Region 1 inner allocation. + +The MPR values of 200MHz channel bandwidths for different regions are shown in Table 5.2.4.6-4 based on the simulation results of figure 5.2.4.6-7 and figure 2.1-8: + +**Table 5.2.4.6-4** $MPR_{WT}$ for power class 1, $BW_{channel} \leq 200 \text{ MHz}$ in FR2-1 + +| Modulation | | $MPR_{WT}$ (dB), $BW_{channel} \leq 200 \text{ MHz}$ | | | +|------------|--------|------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | 256QAM | 8.7 | 8.5 | 8.1 | +| CP-OFDM | | 10.9 | 10.2 | 10.7 | + +The simulation results for 400MHz channel bandwidth are shown in figure 2.1-9 to figure 2.1-10: + +![Heatmap titled 'DFT-s-OFDM 256QAM 400MHz' showing MPR values across RBstart (0 to 250) and LCRB (0 to 250). The color scale ranges from 1 (blue) to 8 (red). The plot shows horizontal bands of color, indicating different MPR levels for different LCRB values.](ffa757b152f924c42ca8c3141fc3f562_img.jpg) + +Heatmap titled 'DFT-s-OFDM 256QAM 400MHz' showing MPR values across RBstart (0 to 250) and LCRB (0 to 250). The color scale ranges from 1 (blue) to 8 (red). The plot shows horizontal bands of color, indicating different MPR levels for different LCRB values. + +**Figure 5.2.4.6-9** PC1 400MHz MPR for 256QAM with PN and no PTRS for 29GHz DFT-s-OFDM + +![Figure 5.2.4.6-10: A heatmap titled 'CP-OFDM 256QAM 400MHz' showing the Power Management Requirement (PMR) for 256QAM modulation. The x-axis is labeled 'RBstart' and ranges from 0 to 250. The y-axis is labeled 'LCRB' and ranges from 0 to 250. The color scale on the right ranges from 2 (blue) to 10 (red). The plot shows a series of horizontal lines, with the highest values (red/orange) concentrated in the lower-left region (low RBstart, low LCRB), indicating higher PMR requirements for those allocations.](ed2c3e8ce1a7479b617b38a843c6b782_img.jpg) + +Figure 5.2.4.6-10: A heatmap titled 'CP-OFDM 256QAM 400MHz' showing the Power Management Requirement (PMR) for 256QAM modulation. The x-axis is labeled 'RBstart' and ranges from 0 to 250. The y-axis is labeled 'LCRB' and ranges from 0 to 250. The color scale on the right ranges from 2 (blue) to 10 (red). The plot shows a series of horizontal lines, with the highest values (red/orange) concentrated in the lower-left region (low RBstart, low LCRB), indicating higher PMR requirements for those allocations. + +**Figure 5.2.4.6-10 PC1 400MHz MPR for 256QAM with PN and no PTRS for 29GHz CP-OFDM** + +Based on RB allocations regions of 400 MHz channel bandwidths for FR2-1 defined in current Spec as below: + +$N_{RB}$ is the maximum number of RBs for a given Channel bandwidth and sub-carrier spacing defined in Table 5.3.2-1 of TS 38.101-2. + +$$RB_{end} = RB_{start} + L_{CRB} - 1$$ + +$$RB_{start,Low} = \text{Max}(1, \text{Floor}(L_{CRB}/2))$$ + +$$RB_{start,High} = N_{RB} - RB_{start,Low} - L_{CRB}$$ + +An RB allocation is an Outer RB allocation if + +$$RB_{start} < RB_{start,Low} \text{ OR } RB_{start} > RB_{start,High} \text{ OR } L_{CRB} > \text{Ceil}(N_{RB}/2)$$ + +An RB allocation in 400 MHz channel bandwidth is a Region 1 inner RB allocation if + +$$RB_{start} \geq \text{Ceil}(1/4 N_{RB}) \text{ AND } RB_{end} < \text{Ceil}(3/4 N_{RB}) \text{ AND } L_{CRB} \leq \text{Ceil}(1/4 N_{RB})$$ + +An RB allocation is a Region 2 inner allocation if it is NOT an Outer allocation AND NOT a Region 1 inner allocation + +The MPR values of 400MHz channel bandwidths for different regions are shown in Table 5.2.4.6-5 based on the simulation results of figure 5.2.4.6-9 and figure 5.2.4.6-10: + +**Table 5.2.4.6-5 $MPR_{WT}$ for power class 1, $BW_{channel} = 400$ MHz in FR2-1** + +| Modulation | | $MPR_{WT}$ (dB), $BW_{channel} = 400$ MHz | | | +|------------|--------|-------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | 256QAM | 8.5 | 7.5 | 7.6 | +| CP-OFDM | | 10.7 | 10.7 | 10.3 | + +In our simulations, we can see the limit factor for 256QAM MPR is EVM, and the larger MPR are need for the RB allocations which are overlap with the IQ image and mainly located around the carrier leakage. If we don't redefine the RB allocation regions, the MPR values for outer allocation, region 1 inner allocation and region 2 inner allocation are almost same. + +Due to time constraints, we don't finish the simulation for PC1 all RB allocations of 39GHz, to compare the MPR difference of 39GHz with 29GHz due to the difference of phase noise profiles, we only give simulation results for some + +RB allocations based CP-OFDM of 200MHz channel bandwidth with 120kHz SCS, Table 2.1-5 gave the simulation results based on different IQ images: + +**Table 5.2.4.6-6 MPR values of 39GHz and 29GHz for PC1** + +| Modulation | Frequency | IQ image | MPR | | | | | | | +|------------|-----------|----------|-------|-------|--------|-------|-------|-------|-------| +| | | | 132@0 | 120@6 | 100@17 | 80@27 | 60@40 | 40@52 | 20@61 | +| CP-OFDM | 29GHz | -36dB | 10.6 | 10.4 | 10.6 | 10.3 | 9.8 | 9.8 | 9.7 | +| | 39GHz | -40dB | 14.3 | 14 | 14.2 | 14.3 | 12.8 | 12.6 | 11.7 | +| | | -50dB | 12.6 | 13.1 | 12.8 | 12.4 | 11.7 | 11.4 | 10.6 | + +Due to we used 28GHz PA model, the MPR values are larger for 39GHz than the values of 29GHz. In additional, we simulation the MPR values for 39GHz with different IQ image values, from table 2.1-5, we can see, the MPR value will be reduced when we using smaller IQ image. So, the MPR values of 39GHz are related not only to phase noise profile but also to PA model. Therefore, the MPR values of 39GHz could be modified by choosing suitable PA model. + +#### 5.2.4.7 Simulation results from Sony + +R4-2313190 simulation results for PC1 + +To investigate the feasibility of confining the MPR for UL 256QAM, the MPR for CP-OFDM for 100 MHz and 400 MHz BW are simulated for PC1 with 120 kHz SCS. The power amplifier is modeled based on a couple different III-V semiconductor PA models and the RB allocation is referred from contributions in last RAN4 meeting [2]. Other simulation assumptions are listed below and the simulated MPR is shown in Table 5.2.4.7-1. + +- The phase noise model proposed by QC has been adopted in the simulation [1], where the EVM budget for Phase noise + IQ imbalance is -30.8 dB. +- L-PTRS = 1 K-PTRS =2 are adopted as PTRS configuration for CP-OFDM. + +**Table 5.2.4.7-1. The MPR simulation results for CP-OFDM with 120 kHz SCS for PC1** + +| Waveform | BW channe | Outer RB allocations | Inner RB allocations | | +|----------|----------------------|----------------------|----------------------|----------| +| | | | Region 1 | Region 2 | +| CP-OFDM | 100 MHz | 10.4 | 11.4 | 11.2 | +| | 400 MHz | 11 | 10.2 | 10.8 | + +Based on the simulated results, it can be observed that for 400 MHz, the MPR values are well below the “64QAM MPR + 3dB” range. Though not all cases (inner region of 100 MHz) can be well-fitted within the proposed range, the values are not far from the proposed limits for narrower BW. In addition, it is worth mentioning that no advanced linearity technologies, e.g., DPD or APD, have been included in such a simulation. Therefore, it can be expected that the MPR confinement, as mentioned above, is feasible to be used to define the MPR values for 256 QAM. + +R4-2315561 simulation results for PC1 + +The MPR for CP-OFDM for 100 MHz and 400 MHz BW are simulated for PC1 with 120 kHz SCS. The power amplifier is modeled based on a couple of different III-V semiconductor PA models. Other simulation assumptions are listed below, and the simulated MPR is shown in Table. 5.2.4.7-2. + +The phase noise model proposed by QC has been adopted in the simulation R4-2314677, where the EVM budget for Phase noise + IQ imbalance is -30.8 dB. + +Both simulation results with PTRS (L-PTRS = 1 K-PTRS =2) and no PTRS are provided in Table. 5.2.4.7-2 and Table. 5.2.4.7-3, respectively. In general, the results without PTRS for CP-OFDM are 1 to 0.5 dB worse than the PTRS configuration (L-PTRS = 1 K-PTRS =2). + +**Table 5.2.4.7-2 The MPR simulation results for CP-OFDM with 120 kHz SCS for PC1 with PTRS L- PTRS = 1 K-PTRS =2** + +| Waveform | BW chann | Outer RB allocations | Inner RB allocations | | +|----------|---------------------|----------------------|----------------------|----------| +| | | | Region 1 | Region 2 | +| CP-OFDM | 100 MHz | 10.4 | 11.4 | 11.2 | +| | 400 MHz | 11 | 10.2 | 10.8 | + +**Table 5.2.4.7-3 The MPR simulation results for CP-OFDM with 120 kHz SCS for PC1 without PTRS** + +| Waveform | BW chann | Outer RB allocations | Inner RB allocations | | +|----------|---------------------|----------------------|----------------------|----------| +| | | | Region 1 | Region 2 | +| CP-OFDM | 100 MHz | 11.2 | 11.6 | 11.5 | +| | 400 MHz | 12 | 10.7 | 11.3 | + +#### 5.2.4.8 Simulation results from MediaTek + +R4-2313417 simulation results for PC2 + +In the Tx, the EVM performance is determined by many factors including baseband clipping and quantization, transmitter non-linearity, IQ imbalance, phase noise, PA non-linearity, etc. In RAN4 #106, the approved agreement for EVM budget is listed below: + +EVM budget for MPR evaluation: + +- Only consider the total value of 3.5% for Tx EVM +- Companies need to clarify the components of Tx EVM in their simulation results, including + - Phase noise + - Value for IQ imbalance + - PA and transmitter non-linearity + +**Table 5.2.4.8-1 EVM budget for FR2-1 UL 256QAM MPR at 29GHz and 39GHz** + +| EVM Contributor | 29GHz | | 39GHz | | +|---------------------------|--------|---------|--------|---------| +| | EVM(%) | SNR(dB) | EVM(%) | SNR(dB) | +| Transmitter +IQ Imbalance | 1.7 | 35.3 | 1.7 | 35.3 | +| Phase Noise | 2.2 | 33.15 | 2.95 | 30.6 | +| PA Non-linearity | 2.1 | 33.56 | 0.8 | 41.93 | +| Total | 3.5 | 29.1 | 3.5 | 29.1 | + +In the FR2-1 UL 256QAM MPR simulation, we propose the EVM budget with approved phase noise profiles in the last meeting summarized in Table 1. With current 39GHz phase noise profile, it should be noted that the phase noise performance of 39GHz dominates the EVM budget for 3.5% EVM. PA requires more back-off power to compensate the quality of the transmitting signal. In our initial simulations, MPR for 29GHz UL 256QAM could achieve reasonable MPR value. However, the MPR value for 39GHz UL 256QAM could be too large and this will result in insufficient dynamic range. + +**Observation 1: With current 39GHz phase noise profile, it should be noted that the phase noise performance of 39GHz dominates the EVM budget for 3.5% EVM. PA requires more back-off power to compensate the quality of the transmitting signal. In our initial simulations, MPR for 29GHz UL 256QAM could achieve reasonable MPR value. However, the MPR value for 39GHz UL 256QAM could be too large and this will result in insufficient dynamic range.** + +In FR1, the MPR of 256QAM is entirely determined by the EVM. This could be also expected for FR2-1. Therefore, in this contribution, we provide our initial MPR simulation for the EVM by using our phase noise model and Qualcomm's phase noise model with full RB allocation in 100 MHz BW with 120 kHz SCS. + +**Table 5.2.4.8-2. PC2 MPR simulated results** + +| Modulation | | PTRS CPE compensation | MPR (dB) | | | +|------------|---------|-----------------------|------------------|--------------------|-------------------| +| | | | 100MHz (full RB) | MTK's model @29GHz | QC's model @29GHz | +| DFT-s-OFDM | 256 QAM | Off | | 7.2 | 7.4 | +| DFT-s-OFDM | 256 QAM | On | | 8 | 7.8 | +| CP-OFDM | 256 QAM | Off | | 9.9 | 10.1 | +| CP-OFDM | 256 QAM | On | | 9.7 | 9.7 | + +R4-2315559 simulation results for PC1 and PC2/5 + +In the last meeting, RAN4 reached an agreement that there would be no PTRS configuration for EVM testing in both DFT-S-OFDM and CP-OFDM. In R4-2313417, and we also presented our initial MPR simulation by utilizing both MTK's phase noise model and Qualcomm's phase noise model, with full RB allocation in a 100 MHz bandwidth and 120 kHz SCS. Based on the simulation results, we observed that the MPR requirements, without PTRS compensation, using both MTK's and Qualcomm's phase noise models, were almost identical. Therefore, for further MPR evaluation, we just considered MTK's phase noise model. + +**Observation 1: For MPR requirements without PTRS compensation, both MTK's and Qualcomm's phase noise models are nearly identical. It is sufficient to just use one of these two models for further evaluation.** + +MPR simulations were conducted for both CP-OFDM and DFT-s-OFDM with 100 MHz and 400 MHz bandwidth for PC1/2/5 using a 120 kHz SCS. In our simulation, it is important to note that the MPR requirements for 256QAM are solely determined by the EVM. Additionally, if taking into account droop effects from the circuits between the baseband BB, IF, and RF, a 1.5dB MPR margin should be reserved for the 400 MHz bandwidth. + +**Observation 2: MPR requirements for 256QAM are solely determined by the EVM.** + +Based on the simulation results and analysis, we propose the FR2-1 256QAM MPR values for PC1/2/5 as shown in Table 2-5. + +**Table 5.2.4.8-3 MPRWT for power class 1, BWchannel ≤ 200 MHz** + +| Modulation | | MPR WT (dB), BW channel ≤ 200 MHz | | | +|------------|-----------|---------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.5 | 0.0 | ≤ 3.0 | +| | QPSK | ≤ 6.5 | 0.0 | ≤ 3.0 | +| | 16 QAM | ≤ 6.5 | ≤ 4.0 | ≤ 4.0 | +| | 64 QAM | ≤ 6.5 | ≤ 5.0 | ≤ 5.0 | +| | 256 QAM | ≤ 9.0 | ≤ 9.0 | ≤ 9.0 | +| CP-OFDM | QPSK | ≤ 7.0 | ≤ 4.5 | ≤ 4.5 | +| | 16 QAM | ≤ 7.0 | ≤ 5.5 | ≤ 5.5 | +| | 64 QAM | ≤ 7.5 | ≤ 7.5 | ≤ 7.5 | +| | 256 QAM | ≤ 11.5 | ≤ 11.5 | ≤ 11.5 | + +**Table 5.2.4.8-4** MPRWT for power class 1, BWchannel = 400 MHz + +| Modulation | | MPR WT (dB), BW channel = 400 MHz | | | +|------------|-----------|---------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.5 | 0.0 | ≤ 3.0 | +| | QPSK | ≤ 6.5 | 0.0 | ≤ 3.5 | +| | 16 QAM | ≤ 6.5 | ≤ 4.5 | ≤ 4.5 | +| | 64 QAM | ≤ 6.5 | ≤ 6.5 | ≤ 6.5 | +| | 256 QAM | ≤ 10.5 | ≤ 10.5 | ≤ 10.5 | +| CP-OFDM | QPSK | ≤ 7.0 | ≤ 5.0 | ≤ 5.0 | +| | 16 QAM | ≤ 7.0 | ≤ 6.5 | ≤ 6.5 | +| | 64 QAM | ≤ 9.0 | ≤ 9.0 | ≤ 9.0 | +| | 256 QAM | ≤ 13 | ≤ 13 | ≤ 13 | + +**Table 5.2.4.8-5** MPRWT for power class 2/5, BWchannel ≤ 200 MHz + +| Modulation | | MPR WT , BW channel ≤ 200 MHz | | +|------------|-----------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | 0.0 | ≤ 2.0 | +| | QPSK | 0.0 | ≤ 2.0 | +| | 16 QAM | ≤ 3.0 | ≤ 3.5 | +| | 64 QAM | ≤ 5.0 | ≤ 5.5 | +| | 256 QAM | ≤ 9.0 | ≤ 9.0 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 4.0 | +| | 16 QAM | ≤ 5.0 | ≤ 5.0 | +| | 64 QAM | ≤ 7.5 | ≤ 7.5 | +| | 256 QAM | ≤ 11.5 | ≤ 11.5 | + +**Table 5.2.4.8-6** MPRWT for power class 2/5, BWchannel = 400 MHz + +| Modulation | | MPR WT , BW channel = 400 MHz | | +|------------|-----------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | 0.0 | ≤ 3.0 | +| | QPSK | 0.0 | ≤ 3.0 | +| | 16 QAM | ≤ 4.5 | ≤ 4.5 | +| | 64 QAM | ≤ 6.5 | ≤ 6.5 | +| | 256 QAM | ≤ 10.5 | ≤ 10.5 | +| CP-OFDM | QPSK | ≤ 5.0 | ≤ 5.0 | +| | 16 QAM | ≤ 6.5 | ≤ 6.5 | +| | 64 QAM | ≤ 9.0 | ≤ 9.0 | +| | 256 QAM | ≤ 13 | ≤ 13 | + +#### 5.2.4.9 Simulation results from Qualcomm + +R4-2315054 simulation results for PC1/PC5 + +In the discussion below, we assume mass producible and commercially feasible UEs assuming best possible design practices. In this context, among current UL waveforms, 256QAM remains distinct from the others on account of the proximity of the EVM requirement (-29.1 dB) to the floors introduced by multiple impairment mechanisms in the Tx chain. In contrast, lower modulation complexity waveforms are limited principally by PA distortion. The aforementioned sensitivities to various assumptions like phase noise floor, image levels, and various floors from stages preceding the PA can cause large variation in MPR projections for 256QAM. This effect is demonstrated below in figure 5.2.4.9-1 for PC5 CP-OFDM 256QAM UL. See Annex for calibration details. + +![Three heatmaps showing Required-MPR sensitivity for 256QAM. The first two plots show 'MPR, -36 dBc Image, RAN4 256QAM profile phase noise' and 'MPR, -38 dBc Image, RAN4 256QAM profile phase noise' respectively. The third plot shows 'MPR, -38 dBc Image, implementation phase noise'. All plots have RBstart on the x-axis (0-60) and LCRB on the y-axis (0-60). A color bar on the right of each plot indicates MPR values from 0 to 12 dB. Each plot contains two lines: a red line for 'Outer RB allocation' and a green line for 'Inner RB allocation'. The plots show that MPR increases as RBstart and LCRB increase, and is higher for the -38 dBc implementation phase noise assumption compared to the RAN4 profile assumptions.](c5616180b57a463028fe4da4a404d4c1_img.jpg) + +Three heatmaps showing Required-MPR sensitivity for 256QAM. The first two plots show 'MPR, -36 dBc Image, RAN4 256QAM profile phase noise' and 'MPR, -38 dBc Image, RAN4 256QAM profile phase noise' respectively. The third plot shows 'MPR, -38 dBc Image, implementation phase noise'. All plots have RBstart on the x-axis (0-60) and LCRB on the y-axis (0-60). A color bar on the right of each plot indicates MPR values from 0 to 12 dB. Each plot contains two lines: a red line for 'Outer RB allocation' and a green line for 'Inner RB allocation'. The plots show that MPR increases as RBstart and LCRB increase, and is higher for the -38 dBc implementation phase noise assumption compared to the RAN4 profile assumptions. + +**Figure 5.2.4.9-1: Required-MPR sensitivity to image and phase noise floor assumptions for 256QAM** + +From the examples above, projected MPR can vary from ~8 dB to ~ 12 dB just by manipulating image suppression levels between 36 and 38 dBc and substituting a conservative (padded) estimate of implementation-worthy phase noise in place of the profile RAN4 has identified as suitable for 256QAM [5]. Further variation is likely when varying assumptions for other impairment floors are considered. + +**Observation 1: MPR projections for 256QAM can be very sensitive to estimates of impairment floors from multiple mechanisms in the Tx chain of the UE.** + +Observation 1 demonstrates that MPR determination from UE performance projections can be even more challenging than for other modulation types. It may be necessary to view each proposal paired with the associated floor assumptions. For the remainder of the contribution, we assume implementation quality impairments (image level and other floors are chosen from realistic projections). + +##### **PC5** + +Figures 5.2.4.9-2 and -3 shows the MPR difference between 256QAM and 64QAM for CP-OFDM and DFT-s-OFDM respectively for devices limited to 23 dBm TRP (includes PC5 as well as PC2/3/4/6). + +![Two heatmaps comparing MPR for 64QAM and 256QAM. The left plot is 'MPR, -38 dBc Image' for 64QAM, and the right plot is 'MPR, -38 dBc Image, implementation phase noise' for 256QAM. Both plots have RBstart on the x-axis (0-60) and LCRB on the y-axis (0-60). A color bar on the right of each plot indicates MPR values from 0 to 12 dB. Each plot contains two lines: a red line for 'Outer RB allocation' and a green line for 'Inner RB allocation'. A red text overlay in the center reads 'Max(MPR_256)-Max(MPR_64) = 2.9 dB', indicating the maximum difference in MPR between the two modulation schemes.](3cebe0a635150ad48f69392301b0c157_img.jpg) + +Two heatmaps comparing MPR for 64QAM and 256QAM. The left plot is 'MPR, -38 dBc Image' for 64QAM, and the right plot is 'MPR, -38 dBc Image, implementation phase noise' for 256QAM. Both plots have RBstart on the x-axis (0-60) and LCRB on the y-axis (0-60). A color bar on the right of each plot indicates MPR values from 0 to 12 dB. Each plot contains two lines: a red line for 'Outer RB allocation' and a green line for 'Inner RB allocation'. A red text overlay in the center reads 'Max(MPR\_256)-Max(MPR\_64) = 2.9 dB', indicating the maximum difference in MPR between the two modulation schemes. + +**Figure 5.2.4.9-2: PC2/3/4/5/6 MPR delta between 256 and 64QAM, CP-OFDM** + +![Two heatmaps comparing MPR for 64QAM and 256QAM in DFT-s-OFDM. The left plot for 64QAM shows a peak MPR around 10 dB, while the right plot for 256QAM shows a peak MPR around 11 dB. A red text overlay indicates a difference of 1.9 dB.](c90b2604dca3815ab852de4349790ebb_img.jpg) + +Figure 5.2.4.9-3 displays two heatmaps showing the Maximum Power Ratio (MPR) for DFT-s-OFDM. The left plot is for 64QAM and the right plot is for 256QAM. Both plots show LCRB (0 to 60) on the Y-axis and RBstart (0 to 60) on the X-axis. The color scale represents MPR values from 0 to 12 dB. The plots indicate that the MPR is generally higher for 256QAM than for 64QAM. A red text overlay indicates the difference: $\text{Max(MPR\_256) - Max(MPR\_64)} = 1.9 \text{ dB}$ . + +Two heatmaps comparing MPR for 64QAM and 256QAM in DFT-s-OFDM. The left plot for 64QAM shows a peak MPR around 10 dB, while the right plot for 256QAM shows a peak MPR around 11 dB. A red text overlay indicates a difference of 1.9 dB. + +Figure 5.2.4.9-3: PC2/3/4/5/6 MPR delta between 256 and 64QAM, DFT-s-OFDM + +An interesting observation is that it takes less than 3 dB of additional back off to seemingly improve EVM 6 dB (the difference between the EVM requirements for 64 and 256 QAM). To resolve this potentially problematic observation, we studied the gating mechanisms for each case, and found that they indeed change. In the 64QAM case, the MPR allowance is driven by IBE compliance for some corner waveforms and for 256, MPR allowance is driven by EVM compliance. i.e the results do not imply inconsistency or other unphysical behavior. + +**Observation 2: With implementation-grade assumptions for a UE limited to 23 dBm TRP, the additional MPR for 256QAM over that of 64 QAM is 3 dB or less.** + +##### PC1 + +Figures 5.2.4.9-4 and -5 shows the MPR difference between 256QAM and 64QAM for CP-OFDM and DFT-s-OFDM respectively for devices limited to 35 dBm TRP (example: PC1). + +![Two heatmaps comparing MPR for 64QAM and 256QAM in CP-OFDM. The left plot for 64QAM shows a peak MPR around 10 dB, while the right plot for 256QAM shows a peak MPR around 12.4 dB. A red text overlay indicates a difference of 2.4 dB.](c2358318fd81a98b7f4eb656e6d67c7a_img.jpg) + +Figure 5.3.4.9-4 displays two heatmaps showing the Maximum Power Ratio (MPR) for CP-OFDM. The left plot is for 64QAM and the right plot is for 256QAM. Both plots show LCRB (0 to 60) on the Y-axis and RBstart (0 to 60) on the X-axis. The color scale represents MPR values from 0 to 12 dB. The plots indicate that the MPR is generally higher for 256QAM than for 64QAM. A red text overlay indicates the difference: $\text{Max(MPR\_256) - Max(MPR\_64)} = 2.4 \text{ dB}$ . + +Two heatmaps comparing MPR for 64QAM and 256QAM in CP-OFDM. The left plot for 64QAM shows a peak MPR around 10 dB, while the right plot for 256QAM shows a peak MPR around 12.4 dB. A red text overlay indicates a difference of 2.4 dB. + +Figure 5.3.4.9-4: PC1 MPR delta between 256 and 64QAM, CP-OFDM + +![Figure 5.2.4.9-5: PC1 MPR delta between 256 and 64QAM, DFT-s-OFDM. The figure contains two heatmaps. The left heatmap is for MOD = 64QAM and the right is for MOD = 256QAM. Both plots show MPR on the y-axis (0 to 60) versus RBstart on the x-axis (0 to 60). A color bar on the right of each plot indicates MPR values from 0 to 12 dB. A red text annotation 'Max(MPR_256)-Max(MPR_64) = 2.7 dB' is centered between the plots, with arrows pointing to the peak values in each heatmap. The legend for both plots includes: BW = 100, Subcarrier spacing = 120, DFT spread = 1, and three allocation types: Outer RB allocation (red line), Edge RB allocation (green line), and Inner RB allocation (blue line).](245e13acc2712dcc66009c4c2f5b0247_img.jpg) + +Figure 5.2.4.9-5: PC1 MPR delta between 256 and 64QAM, DFT-s-OFDM. The figure contains two heatmaps. The left heatmap is for MOD = 64QAM and the right is for MOD = 256QAM. Both plots show MPR on the y-axis (0 to 60) versus RBstart on the x-axis (0 to 60). A color bar on the right of each plot indicates MPR values from 0 to 12 dB. A red text annotation 'Max(MPR\_256)-Max(MPR\_64) = 2.7 dB' is centered between the plots, with arrows pointing to the peak values in each heatmap. The legend for both plots includes: BW = 100, Subcarrier spacing = 120, DFT spread = 1, and three allocation types: Outer RB allocation (red line), Edge RB allocation (green line), and Inner RB allocation (blue line). + +**Figure 5.2.4.9-5: PC1 MPR delta between 256 and 64QAM, DFT-s-OFDM** + +It is evident that for PC1, the pattern of variation is like that of PC5. + +**Observation 3: With implementation-grade assumptions for a UE limited to 35 dBm, the additional MPR for 256QAM over that of 64 QAM can be conservatively considered to be 3 dB or less.** + +Annex, calibration condition for PA model + +The calibration condition for the PA used for MPR projections is shown below – 20RB23 DFT-s-QPSK is expected to operate with no more than 23 dBm TRP for PC5 and 35 dBm for PC1. This is a worst-case scenario for SEM compliance. + +![Figure 5.2.4.9-6: Overall Power vs RBstart and LCRB plot for 23 dBm TRP calibration. The plot shows power levels across resource blocks with a color scale from 22 to 24 dBm. A red arrow points to a specific allocation labeled '20RB23' with a value of 23.07 dBm.](2ee4eab0a7ac079c4858483ede251b76_img.jpg) + +**Overall Power** + +BW = 100 +Subcar spacing = 120 +MOD = QPSK +DFT spread = 1 + +— Outer RB allocation +— Inner RB allocation + +20RB23 +23.07 dBm + +LCRB + +RBstart + +Figure 5.2.4.9-6: Overall Power vs RBstart and LCRB plot for 23 dBm TRP calibration. The plot shows power levels across resource blocks with a color scale from 22 to 24 dBm. A red arrow points to a specific allocation labeled '20RB23' with a value of 23.07 dBm. + +Figure 5.2.4.9-6: Calibration condition for devices limited to 23 dBm TRP (PC5 FWA for example) + +![Figure 5.2.4.9-7: Overall Power vs RBstart and LCRB plot for 35 dBm TRP calibration. The plot shows power levels across resource blocks with a color scale from 32 to 36 dBm. A red arrow points to a specific allocation labeled '20RB23' with a value of 35.07 dBm.](f329aa6f0e390067766cb33dd5ddf93a_img.jpg) + +**Overall Power** + +BW = 100 +Subcar spacing = 120 +MOD = QPSK +DFT spread = 1 + +— Outer RB allocation +— Inner RB allocation + +20RB23 +35.07 dBm + +LCRB + +RBstart + +Figure 5.2.4.9-7: Overall Power vs RBstart and LCRB plot for 35 dBm TRP calibration. The plot shows power levels across resource blocks with a color scale from 32 to 36 dBm. A red arrow points to a specific allocation labeled '20RB23' with a value of 35.07 dBm. + +Figure 5.2.4.9-7: Calibration condition for devices limited to 35 dBm TRP (PC1 FWA for example) + +#### 5.2.4.10 Simulation results from Huawei + +R4-2316379 simulation results for PC1 + +We use the following EVM budget for our further MPR simulation. + +**Table 5.2.4.10-1 EVM budget in MPR simulation for 256QAM** + +| EVM Contributor | EVM(%) | SNR(dB) | +|------------------|--------|---------| +| Transmitter | 1 | -40 | +| Phase Noise | 1.8 | -34.9 | +| IQ Imbalance | 1.45 | -36.8 | +| PA Non-linearity | 2.5 | -32 | +| Total | 3.5 | -29.1 | + +The simulation results is shown in Table 5.2.4.10-1. + +**Table 5.2.4.10-1: MPR simulation for 256QAM** + +| Modulation | | Companies | $MPR_{WT}$ (dB), $BW_{channel} \leq 100$ MHz/200MHz | | | +|------------|--------|-----------|-----------------------------------------------------|----------------------|------------| +| | | | Outer RB allocations | Inner RB allocations | | +| | | | | Region 1 | Region 2 | +| DFT-s-OFDM | 64 QAM | - | $\leq 6.5$ | $\leq 5.0$ | $\leq 5.0$ | +| | 256QAM | Huawei | | 9.1 | | +| CP-OFDM | 64 QAM | - | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | Huawei | | 11.8 | | + +#### 5.2.4.11 Summary of the simulation results for 29GHz MPR + +Based on the simulation results from companies, below tables list the average values for 29GHz PC1/PC2/PC5 MPR: + +**Table 5.2.4.11-1 PC1 UL 256QAM MPR summary for 29 GHz with $BW_{channel} \leq 200$ MHz and 120kHz SCS** + +| Modulation | Companies | $MPR_{WT}$ (dB), $BW_{channel} \leq 100/200$ MHz | +|------------|-----------|--------------------------------------------------| +|------------|-----------|--------------------------------------------------| + +| | | | Outer RB allocations | Inner RB allocations | | +|------------|--------|----------------------|----------------------|----------------------|------------| +| | | | | Region 1 | Region 2 | +| DFT-s-OFDM | 64 QAM | - | $\leq 6.5$ | $\leq 5.0$ | $\leq 5.0$ | +| | 256QAM | Xiaomi(R4-2315437) | 9 | 9 | 9 | +| | | MediaTek(R4-2315559) | 9 | 9 | 9 | +| | | ZTE(R4-2315563) | 7.5 | 7.5 | 7.5 | +| | | LGE(R4-2315540) | 8.5 | 8.5 | 8 | +| | | vivo(R4-2315808) | 8 | 8 | 8 | +| | | Qualcomm(R4-2315054) | 9.5 | 8 | 8 | +| | | Huawei(R4-2316379) | 9.1 | | | +| | | Nokia (R4-2311665) | 7.2 | | | +| | | Average | 8.5 | 8.3 | 8.2 | +| CP-OFDM | 64 QAM | - | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | Nokia (R4-2315265) | 8.6 | | | +| | | Xiaomi(R4-2315437) | 11 | 11 | 11 | +| | | MediaTek(R4-2315559) | 11.5 | 11.5 | 11.5 | +| | | ZTE(R4-2315563) | 10.5 | 10.5 | 10.5 | +| | | vivo(R4-2315808) | 11 | 11 | 11 | +| | | LGE(R4-2315540) | 10.5 | 10.5 | 10.5 | +| | | Sony(R4-2315561) | 11.2 | 11.6 | 11.5 | +| | | Qualcomm(R4-2315054) | 10.5 | 10.5 | 10.5 | +| | | Huawei(R4-2316379) | 11.8 | | | +| | | Average | 10.7 | 10.8 | 10.8 | + +**Table 5.2.4.11-2 PC1 UL 256QAM MPR summary for 29 GHz with $BW_{\text{channel}} = 400$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{WT}}$ (dB), $BW_{\text{channel}} = 400$ MHz | | | +|------------|--------|----------------------|---------------------------------------------------------|----------------------|------------| +| | | | Outer RB allocations | Inner RB allocations | | +| | | | | Region 1 | Region 2 | +| DFT-s-OFDM | 64 QAM | | $\leq 6.5$ | $\leq 6.5$ | $\leq 6.5$ | +| | 256QAM | Xiaomi(R4-2315437) | 9 | 9 | 9 | +| | | LGE(R4-2315540) | 10 | 9.5 | 9.5 | +| | | MediaTek(R4-2315559) | 10.5 | 10.5 | 10.5 | +| | | ZTE(R4-2315563) | 7.5 | 7.5 | 7.5 | +| | | vivo(R4-2315808) | 9.5 | 9.5 | 9.5 | +| | | Nokia (R4-2311665) | 7.2 | | | +| | | Average | 9 | 8.9 | 8.9 | +| CP-OFDM | 64 QAM | | $\leq 9.0$ | $\leq 9.0$ | $\leq 9.0$ | +| | 256QAM | Nokia (R4-2315265) | 8.7 | | | +| | | Xiaomi(R4-2315437) | 11 | 11 | 11 | +| | | LGE(R4-2315540) | 12 | 12 | 12.5 | +| | | MediaTek(R4-2315559) | 13 | 13 | 13 | +| | | Sony(R4-2315561) | 12 | 10.7 | 11.3 | +| | | ZTE(R4-2315563) | 10.5 | 10.5 | 10.5 | +| | | vivo(R4-2315808) | 12.5 | 12.5 | 12.5 | +| | | Average | 11.4 | 11.2 | 11.4 | + +**Table 5.2.4.11-3 PC2 UL 256QAM MPR summary for 29 GHz with $BW_{\text{channel}} \leq 200$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{wr}}, BW_{\text{channel}} \leq 100/200$ MHz | | +|------------|--------|----------------------|---------------------------------------------------------|---------------------| +| | | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 64 QAM | | $\leq 5.0$ | $\leq 5.5$ | +| | 256QAM | MediaTek(R4-2315559) | 9 | 9 | +| | | LGE(R4-2315540) | 8 | 8 | +| | | Qualcomm(R4-2315054) | 8 | 8.5 | +| | | Nokia (R4-2311665) | 7.1 | | +| | | Average | 8 | 8.2 | +| CP-OFDM | 64 QAM | | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | Nokia (R4-2315265) | 8.8 | | +| | | MediaTek(R4-2315559) | 11.5 | 11.5 | +| | | LGE(R4-2315540) | 10.5 | 10.5 | +| | | Qualcomm(R4-2315054) | 10.5 | 10.5 | +| | | Average | 10.3 | 10.3 | + +**Table 5.2.4.11-4 PC2 UL 256QAM MPR summary for 29 GHz with $BW_{\text{channel}} = 400$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{wr}}, BW_{\text{channel}} = 400$ MHz | | +|------------|--------|----------------------|--------------------------------------------------|---------------------| +| | | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 64 QAM | | $\leq 6.5$ | $\leq 6.5$ | +| | 256QAM | LGE(R4-2315540) | 10 | 9.5 | +| | | MediaTek(R4-2315559) | 10.5 | 10.5 | +| | | Nokia (R4-2311665) | 7.0 | | +| | | Average | 9.2 | 9.2 | +| CP-OFDM | 64 QAM | | $\leq 9$ | $\leq 9$ | +| | 256QAM | Nokia (R4-2315265) | 8.8 | | +| | | LGE(R4-2315540) | 11.5 | 11.5 | +| | | MediaTek(R4-2315559) | 13 | 13 | +| | | Average | 11.1 | 11.1 | + +**Table 5.2.4.11-5 PC5 UL 256QAM MPR summary for 29 GHz with $BW_{\text{channel}} \leq 200$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{wr}}, BW_{\text{channel}} \leq 100/200$ MHz | | +|------------|--------|----------------------|---------------------------------------------------------|---------------------| +| | | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 64 QAM | | $\leq 5.0$ | $\leq 5.5$ | +| | 256QAM | MediaTek(R4-2315559) | 9 | 9 | +| | | Qualcomm(R4-2315054) | 8 | 8.5 | +| | | Nokia (R4-2311665) | 7.3 | | +| | | Average | 8.1 | 8.3 | +| CP-OFDM | 64 QAM | | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | Nokia (R4-2315265) | 8.8 | | +| | | MediaTek(R4-2315559) | 11.5 | 11.5 | +| | | Qualcomm(R4-2315054) | 10.5 | 10.5 | +| | | Average | 10.3 | 10.3 | + +**Table 5.2.4.11-6 PC5 UL 256QAM MPR summary for 29 GHz with $BW_{\text{channel}} = 400$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{WT}}$ , $BW_{\text{channel}} = 400$ MHz | | +|------------|--------|----------------------|-----------------------------------------------------|---------------------| +| | | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 64 QAM | | $\leq 6.5$ | $\leq 6.5$ | +| | 256QAM | MediaTek(R4-2315559) | 10.5 | 10.5 | +| | | Nokia (R4-2311665) | | 7.1 | +| | | Average | | 8.8 | +| CP-OFDM | 64 QAM | | $\leq 9$ | $\leq 9$ | +| | 256QAM | Nokia (R4-2315265) | | 8.9 | +| | | MediaTek(R4-2315559) | 13 | 13 | +| | | Average | 11 | 11 | + +#### 5.2.4.12 Summary of the simulation results for 39GHz MPR + +Based on the simulation results from companies, below tables list the values for 39GHz PC1 MPR: + +**Table 5.2.4.12-1 PC1 UL 256QAM MPR summary for 39 GHz with $BW_{\text{channel}} \leq 200$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{WT}}$ (dB), $BW_{\text{channel}} \leq 100$ MHz | | | +|------------|--------|-----------------|------------------------------------------------------------|----------------------|------------| +| | | | Outer RB allocations | Inner RB allocations | | +| | | | | Region 1 | Region 2 | +| DFT-s-OFDM | 64 QAM | - | $\leq 6.5$ | $\leq 5.0$ | $\leq 5.0$ | +| | 256QAM | LGE(R4-2315540) | 8.5 | 8.5 | 8 | +| CP-OFDM | 64 QAM | - | $\leq 7.5$ | $\leq 7.5$ | $\leq 7.5$ | +| | 256QAM | LGE(R4-2315540) | 11 | 11 | 10.5 | + +**Table 5.2.4.12-2 PC1 UL 256QAM MPR summary for 39 GHz with $BW_{\text{channel}} = 400$ MHz and 120kHz SCS** + +| Modulation | | Companies | $MPR_{\text{WT}}$ (dB), $BW_{\text{channel}} = 400$ MHz | | | +|------------|--------|-----------------|---------------------------------------------------------|----------------------|------------| +| | | | Outer RB allocations | Inner RB allocations | | +| | | | | Region 1 | Region 2 | +| DFT-s-OFDM | 64 QAM | | $\leq 6.5$ | $\leq 6.5$ | $\leq 6.5$ | +| | 256QAM | LGE(R4-2315540) | 10.5 | 9.5 | 10 | +| CP-OFDM | 64 QAM | | $\leq 9.0$ | $\leq 9.0$ | $\leq 9.0$ | +| | 256QAM | LGE(R4-2315540) | 13 | 12 | 12.5 | + +### 5.2.5 Simulation for PTRS configurations + +#### 5.2.5.1 Simulation results from Qualcomm + +[R4-2304601](#) + +The desired waveform was 256QAM of various allocation sizes and 120 kHz SCS. To isolate the EVM impact of phase noise, no AWGN, image, LO or non-linear distortion products accompanied the signal. The phase noise profile is chosen as the hybrid 30G profile (Proposal 1: Adopting $\min(\text{example1}, \text{example2})$ as the phase noise profile for UL256QAM, where 'example' refers to the example phase noise profiles in TR38.803 for n257, n258 and n261.) + +##### CP-OFDM + +For CP-OFDM, PTRS density ranged from no correction to frequency density $k=2$ and $k=4$ . Time density was fixed at $L=1$ . Table 5.2.5.1-1 summarizes the EVM + +**Table 5.2.5.1-1: EVM penalty for CP-OFDM with PTRS correction** + +| 'hybrid 30' profile | | EVM from floor (dBc) | | | +|---------------------|-----|----------------------|-------|-------| +| | | No PTRS | K=4 | K=2 | +| $L_{CRB}$ | 4 | -33.7 | -34.0 | -34.4 | +| | 16 | -33.0 | -33.6 | -33.9 | +| | 64 | -32.7 | -33.5 | -33.5 | +| | 256 | -32.5 | -33.3 | -33.4 | + +Results show that PTRS corrections seem to help the EVM floor in proportion to the density of PTRS. The effectiveness tapers off for wider allocations, so there is room for optimization in the field. + +**Observation 2: A fixed PTRS configuration of K=2, L=1 benefits EVM for CP-OFDM waveforms with the phase noise profile of proposal 1.** + +##### DFT-s-OFDM + +For DFT-s-OFDM, the configuration ( $(N_{group}^{samp}, N_{group}^{PT-RS})$ ) are chosen amongst this set: {[4 2], [4 4], [4 8]}. The # of groups was maximized while ensuring there were fewer PTRS data symbols than PDSCH symbols. For all cases, number of PTRS samples per group was limited to 4. The group count is recorded in that tables below. + +**Table 5.2.5.1-2: EVM penalty for DFT-s-OFDM with PTRS correction** + +| 'hybrid 30' profile | | # PTRS groups | EVM from floor (dBc) | | +|---------------------|-----|---------------|----------------------|--------------| +| | | | No PTRS | PTRS enabled | +| $L_{CRB}$ | 4 | 4 | -33.8 | -35.3 | +| | 16 | 8 | -32.9 | -33.6 | +| | 64 | 8 | -32.7 | -32.7 | +| | 256 | 8 | -32.5 | -32.3 | + +Results show that PTRS corrections in the configuration above only help narrow allocations (~ 20 or less) of DFT-s-OFDM. PTRS seems like wasted overhead for medium sized allocations (20-64) and can be detrimental for very wide allocations. Here too there is room for optimization in the field. + +**Observation 3: Assuming the phase noise profile of proposal 1, only narrow allocations of DFT-s-OFDM waveforms (~20RB or narrower) benefit from PTRS.** + +**Observation 4: Assuming the phase noise profile of proposal 1, the network is better off not configuring PTRS for allocations wider than 20 RBs.** + +The analysis assumed a certain strategy of how the number of PTRS groups must be reduced in keeping with narrower allocations. Specifically, the total number of symbols available per OFDM symbol is $12 * L_{CRB}$ . Of these, $N_{group}^{samp} * N_{group}^{PT-RS}$ symbols are occupied by PTRS symbols. When the latter product gets comparable to the total number of symbols available per OFDM symbol, PTRS starts to represent a significant overhead. It is also self-evident that 4 symbols per group and 8 groups per OFDM symbol is physically impossible to fit into a 2RB allocation. RAN4 must therefore determine this strategy. + +**Observation 5: Unlike CP-OFDM, it is not clear how to adjust PTRS parameters when the number of symbols in each OFDM symbol ( $12 * L_{CRB}$ ) starts to become comparable to the product $N_{group}^{samp} * N_{group}^{PT-RS}$ .** + +#### 5.2.5.2 Simulation results from vivo + +##### R4-2308227 + +To further investigate PTRS configuration under different RB allocations, the simulation is performed and the results are shown in Table 5.2.5.2-1. Considering that Option 1 and Option 2 are not feasible, only Option 3 and Option 4 are evaluated. + +**Table 5.2.5.2-1 PTRS correction benefit evaluation for different RB allocation** + +| | | | EVM no correction | EVM with correction | benefit | +|------|------------|----------|--------------------------|----------------------------|----------------| +| 32RB | CP-OFDM | Option 3 | -32.5213 | -34.0762 | 1.5549 | +| | | Option 4 | -33.2888 | -34.1761 | 0.8873 | +| | DFT-s-OFDM | Option 3 | -32.6484 | -30.7554 | -1.893 | +| | | Option 4 | -33.4813 | -31.4505 | -2.0308 | +| 16RB | CP-OFDM | Option 3 | -33.4905 | -33.9333 | 0.4428 | +| | | Option 4 | -33.9908 | -34.2379 | 0.2471 | +| | DFT-s-OFDM | Option 3 | -35.5055 | -33.3672 | -2.1383 | +| | | Option 4 | -34.1009 | -32.5789 | -1.522 | +| 8RB | CP-OFDM | Option 3 | -33.3388 | -33.9874 | 0.6486 | +| | | Option 4 | -34.4442 | -34.8899 | 0.4457 | +| | DFT-s-OFDM | Option 3 | -33.3038 | -32.9937 | -0.3101 | +| | | Option 4 | -34.5513 | -34.0163 | -0.535 | +| 4RB | CP-OFDM | Option 3 | -33.9173 | -35.0024 | 1.0851 | +| | | Option 4 | -35.6699 | -36.7056 | 1.0357 | +| | DFT-s-OFDM | Option 3 | -34.7217 | -34.3119 | -0.4098 | +| | | Option 4 | -36.4809 | -35.7798 | -0.7011 | + +**Observation 3: Even under narrow RB allocation, the DFT-s-OFDM still hard to benefit from PTRS correction.** + +Take the 8RB case as an example, we further evaluated DFT-s-OFDM with different PTRS configurations, and the simulation results are shown in Table 5.2.5.2-2: + +**Table 5.2.5.2-2 PTRS correction benefit evaluation for DFT-s-OFDM with narrow RB allocation under different PTRS configurations.** + +| PTRS configuration | | EVM no correction | EVM with correction | benefit | +|---------------------------------------|----------|--------------------------|----------------------------|----------------| +| L-PTRS = 1
N_group = 4, N_samp = 4 | Option 3 | -33.3038 | -33.946 | 0.6422 | +| | Option 4 | -34.5513 | -34.7963 | 0.245 | +| L-PTRS = 1
N_group = 2, N_samp = 4 | Option 3 | -33.3038 | -32.8345 | -0.4693 | +| | Option 4 | -34.5513 | -34.022 | -0.5293 | +| L-PTRS = 1
N_group = 2, N_samp = 2 | Option 3 | -33.3038 | -32.9937 | -0.3101 | +| | Option 4 | -34.5513 | -34.0163 | -0.535 | + +**Observation 4: Only configuration L-PTRS = 1, (N\_group = 4, N\_samp = 4) can make narrow RB allocation benefit from PTRS correction.** + +#### 5.2.5.3 Simulation results from Xiaomi + +[R4-2308805/R4-2318876](#) + +To further evaluate the effects of different PTRS configurations for CP- OFDM and DFT-s-OFDM, the simulations are done for different RBs allocation (4RBs, 16RBs, 64RBs) separately. + +Table 5.2.5.3-1 and table 5.2.5.3-2 show the simulation results for CP- OFDM at 29GHz and 39GHz. Table 5.2.5.3-3 and table 5.2.5.3-4 show the simulation results for DFT-s- OFDM at 29GHz and 39GHz. + +For CP- OFDM: + +**Table 5.2.5.3-1 EVM floor and benefits with different PTRS configurations for CP-OFDM at 29GHz** + +| CP-OFDM with phase noise, 29GHz, 120kHz, 4RB, | | | | | | +|-------------------------------------------------------|-----------------------------------|-----------------------------|-----------------------------|------------------------------|------------------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K-PTRS=2 | EVM (dB) with PTRS K-PTRS=4 | Net benefit of PTRS K-PTRS=2 | Net benefit of PTRS K-PTRS=4 | +| Example 1 from TR38.803 | -31.0 | -31.2 | -30.5 | 0.2 | -0.5 | +| Example 2 from TR38.803 | -23.9 | -25.1 | -24.7 | 1.2 | 0.8 | +| Phase noise Profile from Qualcomm | -32.9 | -33.9 | -33.4 | 1.0 | 0.5 | +| Phase noise Profile from MTK | -34.8 | -35.4 | -34.8 | 0.6 | 0.0 | +| CP-OFDM with phase noise, 29GHz, 120kHz, 16RB, | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K-PTRS=2 | EVM (dB) with PTRS K-PTRS=4 | Net benefit of PTRS K-PTRS=2 | Net benefit of PTRS K-PTRS=4 | +| Example 1 from TR38.803 | -28.9 | -29.3 | -29.0 | 0.4 | 0.1 | +| Example 2 from TR38.803 | -23.6 | -25.3 | -25.1 | 1.7 | 1.5 | +| Phase noise Profile from Qualcomm | -32.1 | -33.2 | -33.0 | 1.1 | 0.9 | +| Phase noise Profile from MTK | -33.0 | -33.7 | -33.4 | 0.7 | 0.4 | +| CP-OFDM with phase noise, 29GHz, 120kHz, 64RB, | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K-PTRS=2 | EVM (dB) with PTRS K-PTRS=4 | Net benefit of PTRS K-PTRS=2 | Net benefit of PTRS K-PTRS=4 | +| Example 1 from TR38.803 | -28.1 | -28.5 | -28.5 | 0.4 | 0.4 | +| Example 2 from TR38.803 | -23.6 | -25.3 | -25.2 | 1.7 | 1.6 | +| Phase noise Profile from Qualcomm | -31.9 | -33.1 | -33.0 | 1.2 | 1.1 | +| Phase noise Profile from MTK | -32.4 | -33.0 | -33.0 | 0.6 | 0.6 | + +**Table 5.2.5.3-2 EVM floor and benefits with different PTRS configurations for CP-OFDM at 39GHz** + +| CP-OFDM with phase noise, 39GHz, 120kHz, 4RB | | | | | | +|---------------------------------------------------------------------|-----------------------------------|-----------------------------|-----------------------------|------------------------------|------------------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K-PTRS=2 | EVM (dB) with PTRS K-PTRS=4 | Net benefit of PTRS K-PTRS=2 | Net benefit of PTRS K-PTRS=4 | +| Example 1: VIVO parameter | -27.8 | -27.9 | -27.2 | 0.1 | -0.6 | +| Example 1:Anritsu parameter | -28.0 | -28.2 | -27.5 | 0.2 | -0.5 | +| Example 2 from TR38.803 | -21.2 | -22.4 | -22.1 | 1.2 | 0.9 | +| Phase noise Profile from Qualcomm; Min(Example1-VIVO, Example2) | -30.2 | -31.0 | -30.5 | 0.8 | 0.3 | +| Phase noise Profile from Qualcomm; Min(Example1- Anritsu, Example2) | -30.3 | -31.1 | -30.6 | 0.8 | 0.3 | +| Phase noise Profile from MTK | -32.0 | -32.5 | -31.8 | 0.5 | -0.2 | +| CP-OFDM with phase noise, 39GHz, 120kHz, 16RB | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K-PTRS=2 | EVM (dB) with PTRS K-PTRS=4 | Net benefit of PTRS K-PTRS=2 | Net benefit of PTRS K-PTRS=4 | +| Example 1:VIVO parameter | -25.6 | -25.9 | -25.6 | 0.3 | 0.0 | +| Example 1:Anritsu parameter | -25.9 | -26.2 | -25.9 | 0.3 | 0.0 | +| Example 2 from TR38.803 | -21.3 | -22.8 | -22.5 | 1.5 | 1.2 | +| Phase noise Profile from Qualcomm; Min(Example1-VIVO, Example2) | -29.4 | -30.5 | -30.2 | 1.1 | 0.8 | +| Phase noise Profile from Qualcomm; Min(Example1- Anritsu, Example2) | -29.5 | -30.5 | -30.2 | 1.0 | 0.7 | +| Phase noise Profile from MTK | -30.1 | -30.7 | -30.4 | 0.6 | 0.3 | +| CP-OFDM with phase noise, 39GHz, 120kHz, 64RB | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K-PTRS=2 | EVM (dB) with PTRS K-PTRS=4 | Net benefit of PTRS K-PTRS=2 | Net benefit of PTRS K-PTRS=4 | +| Example 1:VIVO parameter | -24.8 | -25.1 | -25.0 | 0.3 | 0.2 | +| Example 1:Anritsu parameter | -25.1 | -25.5 | -25.4 | 0.4 | 0.3 | +| Example 2 from TR38.803 | -20.9 | -22.7 | -22.7 | 1.8 | 1.8 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -29.2 | -30.3 | -30.2 | 1.1 | 1.0 | +| Phase noise Profile from Qualcomm Min(Example1- Anritsu, Example2) | -29.3 | -30.3 | -30.3 | 1.0 | 1.0 | +| Phase noise Profile from MTK | -29.4 | -30.0 | -29.9 | 0.6 | 0.5 | + +From Table 5.2.5.3-1 and table 5.2.5.3-2 for CP-OFDM, we can see although the benefits are different for different phase noise profile: + +- The benefits with PTRS correction for all candidate phase noise profiles are monotonously increased with the increase of the density of PTRS configurations. +- The benefits with PTRS correction for all candidate phase noise profiles are monotonously increased with the number of RBs allocation. For the narrow RBs allocation, the benefits with PTRS correction is comparable with 64RBs allocation for 120kHz SCS. + +For DFT-S-OFDM: + +**Table 5.2.5.3-3 EVM floor and benefits with different PTRS configurations for DFT-S-OFDM at 29GHz** + +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 4RB | | | | | | | | +|---------------------------------------------------------|------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1 from TR38.803 | -31.0 | -30.7 | -31.3 | -31.3 | -0.3 | 0.3 | 0.3 | +| Example 2 from TR38.803 | -23.7 | -27.9 | -25.9 | -23.9 | 4.2 | 2.2 | 0.2 | +| Phase noise Profile from Qualcomm | -33.0 | -33.7 | -33.9 | -33.6 | 0.7 | 0.9 | 0.6 | +| Phase noise Profile from MTK | -34.9 | -35.1 | -35.6 | -35.4 | 0.2 | 0.7 | 0.5 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 10RB | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1 from TR38.803 | -29.4 | -29.1 | -29.2 | -29.1 | -0.3 | -0.2 | -0.3 | +| Example 2 from TR38.803 | -23.2 | -26.7 | -24.8 | -23.1 | 3.5 | 1.6 | -0.1 | +| Phase noise Profile from Qualcomm | -32.2 | -32.6 | -32.5 | -32.2 | 0.4 | 0.3 | 0.0 | +| Phase noise Profile from MTK | -33.5 | -33.6 | -33.6 | -33.4 | 0.1 | 0.1 | -0.1 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 16RB | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1 from TR38.803 | -28.9 | -28.4 | -28.4 | -28.3 | -0.5 | -0.5 | -0.6 | +| Example 2 from TR38.803 | -23.1 | -26.9 | -24.9 | -23.0 | 3.8 | 1.8 | -0.1 | +| Phase noise Profile from Qualcomm | -32.0 | -32.4 | -32.1 | -31.8 | 0.4 | 0.1 | -0.2 | +| Phase noise Profile from MTK | -33.0 | -32.9 | -32.8 | -32.6 | -0.1 | -0.2 | -0.4 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 64RB | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1 from TR38.803 | -28.2 | -27.1 | -27.0 | -26.9 | -1.1 | -1.2 | -1.3 | +| Example 2 from TR38.803 | -23.1 | -27.2 | -24.8 | -22.9 | 4.1 | 1.7 | -0.2 | +| Phase noise Profile from Qualcomm | -31.8 | -32.0 | -31.6 | -31.1 | 0.2 | -0.2 | -0.7 | +| Phase noise Profile from MTK | -32.4 | -31.7 | -31.6 | -31.3 | -0.7 | -0.8 | -1.1 | + +**Table 5.2.5.3-4 EVM floor and benefits with different PTRS configurations for DFT-S-OFDM at 39GHz** + +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 4RB | | | | | | | | +|-------------------------------------------------------------------|------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1:VIVO parameter | -27.9 | -27.3 | -28.0 | -28.0 | -0.6 | 0.1 | 0.1 | +| Example 1: Anritsu parameter | -28.1 | -27.5 | -28.2 | -28.2 | -0.6 | 0.1 | 0.1 | +| Example 2 from TR38.803 | -21.2 | -25.3 | -23.3 | -21.2 | 4.1 | 2.1 | 0.0 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -30.3 | -30.6 | -31.0 | -30.7 | 0.3 | 0.7 | 0.4 | +| Phase noise Profile from Qualcomm Min(Example1-Anritsu, Example2) | -30.3 | -30.7 | -31.0 | -30.7 | 0.4 | 0.7 | 0.4 | +| Phase noise Profile from MTK | -32.1 | -32.1 | -32.6 | -32.5 | 0.0 | 0.5 | 0.4 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 10RB | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1:VIVO parameter | -26.2 | -25.7 | -25.8 | -25.7 | -0.5 | -0.4 | -0.5 | +| Example 1: Anritsu parameter | -26.5 | -26.0 | -26.2 | -26.0 | -0.5 | -0.3 | -0.5 | +| Example 2 from TR38.803 | -20.6 | -24.3 | -22.3 | -20.5 | 3.7 | 1.7 | -0.1 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -29.5 | -29.7 | -29.6 | -29.3 | 0.2 | 0.1 | -0.2 | +| Phase noise Profile from Qualcomm Min(Example1-Anritsu, Example2) | -29.6 | -29.7 | -29.6 | -29.4 | 0.1 | 0 | -0.2 | +| Phase noise Profile from MTK | -30.6 | -30.6 | -30.6 | -30.4 | 0.0 | 0.0 | -0.2 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 16RB | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1: VIVO parameter | -25.7 | -24.9 | -25.0 | -25.0 | -0.8 | -0.7 | -0.7 | +| Example 1: Anritsu parameter | -26.0 | -25.3 | -25.4 | -25.2 | -0.7 | -0.6 | -0.8 | +| Example 2 from TR38.803 | -20.6 | -24.3 | -22.3 | -20.4 | 3.7 | 1.7 | -0.2 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -29.3 | -29.5 | -29.2 | -28.9 | 0.2 | -0.1 | -0.4 | + +| | | | | | | | | +|-------------------------------------------------------------------|------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------| +| Phase noise Profile from Qualcomm Min(Example1-Anritsu, Example2) | -29.4 | -29.5 | -29.3 | -29.0 | 0.1 | -0.1 | -0.4 | +| Phase noise Profile from MTK | -30.1 | -29.9 | -29.8 | -29.7 | -0.2 | -0.3 | -0.4 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 64RB | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS N_group = 8, N_samp = 4 | EVM (dB) with PTRS N_group = 4, N_samp = 4 | EVM (dB) with PTRS N_group = 2, N_samp = 4 | Net benefit of PTRS N_group = 8, | Net benefit of PTRS N_group = 4, | Net benefit of PTRS N_group = 2, | +| Example 1: VIVO parameter | -24.8 | -23.7 | -23.5 | -23.4 | -1.1 | -1.3 | -1.4 | +| Example 1: Anritsu parameter | -25.2 | -24.0 | -24.0 | -23.9 | -1.2 | -1.2 | -1.3 | +| Example 2 from TR38.803 | -20.5 | -24.4 | -22.1 | -20.3 | 3.9 | 1.6 | -0.2 | +| Phase noise Profile from Qualcomm Min(Example1-VIVO, Example2) | -29.2 | -29.1 | -28.8 | -28.3 | -0.1 | -0.4 | -0.9 | +| Phase noise Profile from Qualcomm Min(Example1-Anritsu, Example2) | -29.2 | -29.2 | -28.8 | -28.3 | 0.0 | -0.4 | -0.9 | +| Phase noise Profile from MTK | -29.5 | -28.7 | -28.5 | -28.3 | -0.8 | -1.0 | -1.2 | + +From Table 5.2.5.3-3 and table 5.2.5.3-4 for DFT-s-OFDM at 29GHz and 39GHz, we can see although the benefits are different for different phase noise profile: + +The benefits with PTRS correction for all candidate phase noise profiles are monotonously increased with the increase of the density of PTRS configurations. + +The benefits with PTRS correction for all candidate phase noise profiles are monotonously reduced with the number of RBs allocation. + +There is obvious benefit with PTRS correction only for example 2 new phase noise profiles. + +There is no obvious benefits with PTRS correction for the RBs allocation larger than 10RBs for new phase noise profiles from Qualcomm and MTK, even some PTRS configurations have the penalty for the new phase noise profiles. + +There is obvious benefits with PTRS correction for the RBs allocation less than 10RBs for new phase noise profiles from Qualcomm and MTK, especially for (N\_group = 4, N\_samp = 4) PTRS configuration, i.e., 1dB and 0.7dB benefits for 29GHz for 4RBs allocation for 120kHz SCS, 0.8dB and 0.6dB for 39GHz for 4RBs allocation for 120kHz SCS. + +As we know, introducing PTRS will increase the data code rate, especially for narrow RB allocation. In order to check the impact of PTRS, we further compare the BLER performance between PTRS off and PTRS on with different RB allocation for DFT-S-OFDM waveform. The simulation assumption is same with the agreed for evaluation of phase noise profiles in lasting meeting and QC phase noise profile at 29GHz is applied. The background noise is set to -35dB. As we can see from above simulation results, the BLER increase for both 4RB and 64RB allocation when PTRS is configured shown as Table 5.2.5.3-5. For 4RB allocation, although there is EVM benefit as previous analysis, the BLER increase due to high PTRS overhead. For 64RB, the BLER increase due to the joint effect of EVM penalty and overhead of PTRS. For 10RB, maybe there is a trade-off between PTRS overhead and EVM benefit, the BLER is same for PTRS on/off. In short, except for the case that example 2 phase noise profile is applied for MPR simulation, it may not be recommended to configure PTRS. + +**Table 5.2.5.3-5 the BLER for different RBs allocation with/without PTRS corrections** + +| BLER | 4 RBs | 10 RBs | 64 RBs | +|---------------------------------|--------------|---------------|---------------| +| Without PTRS corrections | 0.5 | 0.5 | 0.6680 | +| With PTRS correction | 0.75 | 0.5 | 0.7075 | + +R4-2312686/R4-2318876 + +For CP-OFDM, based on the submitted simulation results in last meeting [R4-2308805], we can see the benefits with PTRS correction are monotonously increased with the number of RBs allocation. If adopting the fixed PTRS configuration of L-PTRS = 1 K-PTRS = 2, it is good for full RBs allocation in EVM test, but the overhead for partial RBs allocation need consider. + +**Table 5.2.5.3-6: PT-RS group pattern as a function of scheduled bandwidth** + +| Scheduled bandwidth | Number of PT-RS groups | Number of samples per PT-RS group | +|---------------------------------|-------------------------------|------------------------------------------| +| $N_{RB0} \leq N_{RB} < N_{RB1}$ | 2 | 2 | +| $N_{RB1} \leq N_{RB} < N_{RB2}$ | 2 | 4 | +| $N_{RB2} \leq N_{RB} < N_{RB3}$ | 4 | 2 | +| $N_{RB3} \leq N_{RB} < N_{RB4}$ | 4 | 4 | +| $N_{RB4} \leq N_{RB}$ | 8 | 4 | + +For DFT-s-OFDM, based PTRS group pattern in Table 5.2.5.3-6, we introduced more simulation cases and the simulation results for some PTRS configurations under different RB allocations are shown in Table 5.2.5.3-7 and Table 5.2.5.3-8. + +**Table 5.2.5.3-7 EVM floor and benefits with different PTRS configurations for DFT-S-OFDM at 29GHz** + +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 4RB | | | | | | | | | | | | +|---------------------------------------------------------|-----------------------------------|--------------------------------------|--------|--------|--------|--------|---------------------------------------|--------|--------|--------|--------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from Qualcomm | -33.0 | -33.2 | -33.6 | -33.5 | -33.9 | -33.7 | 0.2 | 0.6 | 0.5 | 0.9 | 0.7 | +| Phase noise Profile from MTK | -34.9 | -35.0 | -35.4 | -35.2 | -35.6 | -35.1 | 0.1 | 0.5 | 0.3 | 0.7 | 0.2 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 8RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from Qualcomm | -32.4 | -32.1 | -32.5 | -32.5 | -32.8 | -32.9 | -0.3 | 0.1 | 0.1 | 0.4 | 0.5 | +| Phase noise Profile from MTK | -33.8 | -33.3 | -33.8 | -33.5 | -34.0 | -34.0 | -0.5 | 0.0 | -0.3 | 0.2 | 0.2 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 10RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from Qualcomm | -32.2 | -31.8 | -32.2 | -32.2 | -32.5 | -32.6 | -0.4 | 0.0 | 0.0 | 0.3 | 0.4 | +| Phase noise Profile from MTK | -33.5 | -32.8 | -33.4 | -33.0 | -33.6 | -33.6 | -0.7 | -0.1 | -0.5 | 0.1 | 0.1 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 16RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from Qualcomm | -32.0 | -31.3 | -31.8 | -31.8 | -32.1 | -32.4 | -0.7 | -0.2 | -0.2 | 0.1 | 0.4 | +| Phase noise Profile from MTK | -33.0 | -32.0 | -32.6 | -32.3 | -32.8 | -32.9 | -1.0 | -0.4 | -0.7 | -0.2 | -0.1 | +| DFT-S-OFDM with phase noise, 29GHz, 120kHz, 20RB | | | | | | | | | | | | +| Phase | EVM (dB) | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | + +| noise model | with no PTRS corrections | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +|-----------------------------------|--------------------------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------| +| Phase noise Profile from Qualcomm | -32.0 | -31.3 | -31.6 | -31.8 | -32.0 | -32.3 | -0.7 | -0.4 | -0.2 | 0.0 | 0.3 | +| Phase noise Profile from MTK | -32.9 | -31.8 | -32.4 | -32.1 | -32.6 | -32.6 | -1.1 | -0.5 | -0.8 | -0.3 | -0.3 | + +**Table 5.2.5.3-8 EVM floor and benefits with different PTRS configurations for DFT-S-OFDM at 39GHz** + +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 4RB | | | | | | | | | | | | +|---------------------------------------------------------|-----------------------------------|--------------------------------------|--------|--------|--------|--------|---------------------------------------|--------|--------|--------|--------| +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from MTK | -32.1 | -32.1 | -32.5 | -32.2 | -32.6 | -32.1 | 0.0 | 0.4 | 0.1 | 0.5 | 0.0 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 8RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from MTK | -30.9 | -30.3 | -30.8 | -30.5 | -31.0 | -31.0 | -0.6 | -0.1 | -0.4 | 0.1 | 0.1 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 10RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from MTK | -30.6 | -29.8 | -30.4 | -30.0 | -30.6 | -30.6 | -0.8 | -0.2 | -0.6 | 0.0 | 0.0 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 16RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from MTK | -30.1 | -29.0 | -29.7 | -29.3 | -29.8 | -29.9 | -1.1 | -0.4 | -0.8 | -0.3 | -0.2 | +| DFT-S-OFDM with phase noise, 39GHz, 120kHz, 20RB | | | | | | | | | | | | +| Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS (N_group, N_samp) | | | | | Net benefit of PTRS (N_group, N_samp) | | | | | +| | | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | (2, 2) | (2, 4) | (4, 2) | (4, 4) | (8, 4) | +| Phase noise Profile from MTK | -30.0 | -28.8 | -29.4 | -29.1 | -29.5 | -29.6 | -1.2 | -0.6 | -0.9 | -0.5 | -0.4 | + +From above tables for DFT-s-OFDM at 29GHz and 39GHz, we can see: + +- The benefits with PTRS correction are monotonously increased with the increase of the density of PTRS configurations. +- The benefits with PTRS correction are monotonously reduced with the number of RBs allocation. +- There is no obvious benefits with PTRS correction for the RBs allocation larger than 10RBs, even some PTRS configurations have the penalty. +- There is obvious benefits with PTRS correction for the RBs allocation less than 10RBs, especially for ( $N\_group = 4$ , $N\_samp = 4$ ) PTRS configuration. + +#### 5.2.5.4 Simulation results from ZTE + +R4-2314619 + +For DFT-s-OFDM waveform, the results for EVM comparison between different RB allocations are summarized in Table 5.2.5.4-1, in which the phase noise model for 29GHz (i.e. option 1.) agreed in the WF R4-2310260 is used. + +**Table 5.2.5.4-1 EVM comparison between different configurations for DFT-s-OFDM waveform** + +| DFT-s-OFDM w/ phase noise, 256QAM, 120k SCS, w/ CPE vs w/o CPE @29GHz | | | | | +|-----------------------------------------------------------------------|--------------------------------------|------------------|----------------------|--------------------| +| Scheduled BW (RB) | PTRS config [PTRS/group, PTRS group] | EVM(dB) with CPE | EVM (dB) without CPE | Net benefit of CPE | +| 8 | [2, 2] | -31.4 | -31.9 | -0.5 | +| 20 | [4, 4] | -31.5 | -31.6 | -0.1 | +| 20 | [2, 4] | -30.8 | -30.7 | 0.1 | +| 66 | [4, 8] | -30.9 | -30.8 | 0.1 | + +From table 5.2.5.4-1, it can be seen that the net benefit of CPE is only 0.1dB for full RB allocation, however, for partial RB allocation, even negative net benefits is found. It would be foreseen that this tendency can be applied to all the start allocation for the partial RB. Therefore, we think PTRS for CPE will not provide EVM benefit for all RB allocation cases for DFT-s-OFDM. + +**Observation 1: Introducing PTRS for CPE for DFT-s-OFDM may not improve EVM or the improvement is very small.** + +With regard to the PTRS configuration for EVM test for CP-OFDM, we can see that the difference between the two options is whether to configure PTRS for EVM test based on the UEs declaration or to configure the same PTRS without considering UE declaration. Currently, how UEs declare whether they need PTRS or not is FFS. In our contribution[R4-2304689], we compared net benefit of PTRS for CPE for different UE phase noise model alternatives for CP-OFDM, we copy the results in table 5.2.5.4-2 for convenience. + +**Table 5.2.5.4-2. EVM comparison between different alternatives** + +| CP-OFDM w/ phase noise, 64 RBs, 256QAM, 120k SCS, DMRS based CPE removal@45GHz | | | | +|--------------------------------------------------------------------------------|-------------------|-----------------------------------|---------------------| +| Phase noise | EVM(dB) with PTRS | EVM (dB) with no PTRS corrections | Net benefit of PTRS | +| UE alt 1 | -24.7 | -24.5 | 0.2 | +| UE alt 2 | -21.5 | -20.4 | 1.1 | +| UE alt 3 | -30.4 | -28 | 2.4 | +| UE alt 4 | -27.3 | -27.1 | 0.2 | + +The four phase noise options in the above table are: + +- Alt 1. example 1 defined in 38803 +- Alt 2. example 2 defined in 38803 +- Alt 3. min(example 1, example 2) + +- Alt 4. example 1-based + +In table 5.2.5.4-2, when the low phase noise model (i.e. alt 3.) is adopted, the net benefit of PTRS is promising. But companies have different views of the PTRS configuration, e.g., some companies prefer to use PTRS for all device and others prefer to use PTRS if UE declare to use it. From the contributions [3][4] provided by companies we can see that PTRS based CPE can improve EVM at least for CP-OFDM waveform. If most companies believe that PTRS based CPE can improve EVM for CP-OFDM waveform, then we tend to use the same PTRS configuration for all devices. + +**Observation 2: Introducing PTRS for CPE can improve EVM for CP-OFDM waveform.** + +#### 5.2.5.5 Summary the CP-OFDM simulation results for PTRS configuration + +For CP-OFDM at 29GHz: + +**Table 5.2.5.5-1: For CP-OFDM at 29GHz** + +| | | Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS K- PTRS=2 | EVM (dB) with PTRS K- PTRS=4 | Net benefit of PTRS K- PTRS=2 | Net benefit of PTRS K- PTRS=4 | +|---------------------|----------------|-------------------------|-----------------------------------|------------------------------|------------------------------|-------------------------------|-------------------------------| +| Qualcomm R4-2304601 | 120kHz, 4RBs | min(example1, example2) | -33.7 | -34.4 | -34.0 | 0.7 | 0.3 | +| | 120kHz, 16RBs | | -33.0 | -33.9 | -33.6 | 0.9 | 0.6 | +| | 120kHz, 64RBs | | -32.7 | -33.5 | -33.5 | 0.8 | 0.8 | +| | 120kHz, 256RBs | | -32.5 | -33.4 | -33.3 | 0.9 | 0.8 | +| Xiaomi R4-2308805 | 120kHz, 4RBs | UE example 1 | -31.0 | -31.2 | -30.5 | 0.2 | -0.5 | +| | | UE example 2 | -23.9 | -25.1 | -24.7 | 1.2 | 0.8 | +| | | From Qualcomm | -32.9 | -33.9 | -33.4 | 1.0 | 0.5 | +| | | From MTK | -34.8 | -35.4 | -34.8 | 0.6 | 0.0 | +| | 120kHz, 16RBs | UE example 1 | -28.9 | -29.3 | -29.0 | 0.4 | 0.1 | +| | | UE example 2 | -23.6 | -25.3 | -25.1 | 1.7 | 1.5 | +| | | From Qualcomm | -32.1 | -33.2 | -33.0 | 1.1 | 0.9 | +| | | From MTK | -33.0 | -33.7 | -33.4 | 0.7 | 0.4 | +| | 120kHz, 64RBs | UE example 1 | -28.1 | -28.5 | -28.5 | 0.4 | 0.4 | +| | | UE example 2 | -23.6 | -25.3 | -25.2 | 1.7 | 1.6 | +| | | From Qualcomm | -31.9 | -33.1 | -33.0 | 1.2 | 1.1 | +| | | From MTK | -32.4 | -33.0 | -33.0 | 0.6 | 0.6 | +| Vivo R4-2308227 | 120kHz, 4RBs | From Qualcomm | -33.9173 | -35.0024 | | 1.0851 | | +| | | From MTK | -35.6699 | -36.7056 | | 1.0357 | | +| | 120kHz, 8RBs | From Qualcomm | -33.3388 | -33.9874 | | 0.6486 | | +| | | From MTK | -34.4442 | -34.8899 | | 0.4457 | | +| | 120kHz, 16RBs | From Qualcomm | -33.4905 | -33.9333 | | 0.4428 | | +| | | From MTK | -33.9908 | -34.2379 | | 0.2471 | | +| | 120kHz, 32RBs | From Qualcomm | -32.5213 | -34.0762 | | 1.5549 | | +| | | From MTK | -33.2888 | -34.1761 | | 0.8873 | | +| | 120kHz, 64RBs | From Qualcomm | -31.7997 | -33.0798 | | 1.2801 | | +| | | From MTK | -33.0942 | -33.3608 | | 0.2666 | | + +#### 5.2.5.6 Summary the DFT-s-OFDM simulation results for PTRS configuration + +For DFT-s-OFDM at 29GHz: + +**Table 5.2.5.6-1: For DFT-s-OFDM at 29GHz** + +| | | Phase noise model | EVM (dB) with no PTRS corrections | EVM (dB) with PTRS | EVM (dB) with PTRS | EVM (dB) with PTRS | EVM (dB) with PTRS | Net benefit of PTRS | Net benefit of PTRS | Net benefit of PTRS | Net benefit of PTRS | +|---------------------|----------------|-------------------------|-----------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------| +| | | | | N group = 8,
N samp = 4 | N group = 4,
N samp = 4 | N group = 2,
N samp = 4 | N group = 2,
N samp = 2 | N group = 8,
N samp = 4 | N group = 4,
N samp = 4 | N group = 2,
N samp = 4 | N group = 2,
N samp = 2 | +| Qualcomm R4-2304601 | 120kHz, 4RBs | min(example1, example2) | -33.8 | | -35.3 | | | | 1.5 | | | +| | 120kHz, 16RBs | | -32.9 | -33.6 | | | | 0.7 | | | | +| | 120kHz, 64RBs | | -32.7 | -32.7 | | | | 0 | | | | +| | 120kHz, 256RBs | | -32.5 | -32.3 | | | | -0.2 | | | | +| Xiaomi R4-2308805 | 120kHz, 4RBs | UE example 1 | -31.0 | -30.7 | -31.3 | -31.3 | | -0.3 | 0.3 | 0.3 | | +| | | UE example 2 | -23.7 | -27.9 | -25.9 | -23.9 | | 4.2 | 2.2 | 0.2 | | +| | | From Qualcomm | -33.0 | -33.7 | -33.9 | -33.6 | -33.2 | 0.7 | 0.9 | 0.6 | 0.2 | +| | | From MTK | -34.9 | -35.1 | -35.6 | -35.4 | -35.0 | 0.2 | 0.7 | 0.5 | 0.1 | +| | 120kHz, 10RBs | UE example 1 | -29.4 | -29.1 | -29.2 | -29.1 | | -0.3 | -0.2 | -0.3 | | +| | | UE example 2 | -23.2 | -26.7 | -24.8 | -23.1 | | 3.5 | 1.6 | -0.1 | | +| | | From Qualcomm | -32.2 | -32.6 | -32.5 | -32.2 | -31.8 | 0.4 | 0.3 | 0.0 | -0.4 | +| | | From MTK | -33.5 | -33.6 | -33.6 | -33.4 | -32.8 | 0.1 | 0.1 | -0.1 | -0.7 | +| | 120kHz, 16RBs | UE example 1 | -28.9 | -28.4 | -28.4 | -28.3 | | -0.5 | -0.5 | -0.6 | | +| | | UE example 2 | -23.1 | -26.9 | -24.9 | -23.0 | | 3.8 | 1.8 | -0.1 | | +| | | From Qualcomm | -32.0 | -31.3 | -31.8 | -31.8 | -31.3 | 0.4 | 0.1 | -0.2 | -0.7 | +| | | From MTK | -33.0 | -32.9 | -32.8 | -32.6 | -32.0 | -0.1 | -0.2 | -0.4 | -1 | +| | 120kHz, 64RBs | UE example 1 | -28.2 | -27.1 | -27.0 | -26.9 | | -1.1 | -1.2 | -1.3 | | +| | | UE example 2 | -23.1 | -27.2 | -24.8 | -22.9 | | 4.1 | 1.7 | -0.2 | | +| | | From Qualcomm | -31.8 | -32.0 | -31.6 | -31.1 | | 0.2 | -0.2 | -0.7 | | +| | | From MTK | -32.4 | -31.7 | -31.6 | -31.3 | | -0.7 | -0.8 | -1.1 | | +| Vivo R4-2308227 | 120kHz, 4RBs | From Qualcomm | -34.7217 | -34.3119 | | | | -0.4098 | | | | +| | | From MTK | -36.4809 | -35.7798 | | | | -0.7011 | | | | +| | 120kHz, 8RBs | From Qualcomm | -33.3038 | -32.9937 | -33.946 | -32.8345 | | -0.3101 | 0.6422 | -0.4693 | | +| | | From MTK | -34.5513 | -34.0163 | -34.7963 | -34.022 | | -0.535 | 0.245 | -0.5293 | | +| | 120kHz, 16RBs | From Qualcomm | -35.5055 | -33.3672 | | | | -2.1383 | | | | + +| | | | | | | | | | | | | +|----------------|-------------------|---------------|----------|----------|-------|-------|-------|---------|------|--|------| +| | 120kHz
, 32RBs | From MTK | -34.1009 | -32.5789 | | | | -1.522 | | | | +| | | From Qualcomm | -32.6484 | -30.7554 | | | | -1.893 | | | | +| | | From MTK | -33.4813 | -31.4505 | | | | -2.0308 | | | | +| | 120kHz
, 64RBs | From Qualcomm | -32.8215 | -29.8556 | | | | -2.9659 | | | | +| | | From MTK | -33.2358 | -30.0408 | | | | -3.195 | | | | +| ZTE R4-2314619 | 120kHz
, 8RBs | From MTK | -31.9 | | | | -31.4 | | | | -0.5 | +| | 120kHz
, 20RBs | | -31.6 | | -31.5 | | | | -0.1 | | | +| | 120kHz
, 20RBs | | -30.7 | | | -30.8 | | | 0.1 | | | +| | 120kHz
, 66RBs | | -30.8 | -30.9 | | | | | 0.1 | | | + +## 5.3 EVM test + +### 5.3.1 CPE compensation methods + +To compensate CPE for 256QAM EVM testing, the DMRS based channel estimation and PTRS extraction shall be as below: + +- The DMRS based channel estimate in the PTRS-ready EVM calculator shall utilize CPE-corrected DMRS symbols. +- The PTRS extraction and correction stage in the PTRS-ready EVM calculator is the final refinement of the received signal. + +### 5.3.2 PTRS correction methods + +- For CP-OFDM + - PTRS correction is implemented by de-rotation of each sub carrier in an OFDM symbol. The de-rotation angle is estimated as the frequency domain average of the phase rotation of all the PTRS tones in the allocation. +- For DFT-s-OFDM: + - PTRS correction is implemented by de-rotation of each time-domain symbol by the estimated instantaneous phase deviation. + - The instantaneous phase deviation impacting a data symbol due to DUT phase noise is estimated by linearly interpolating between the phase deviations determined for the nearest neighbouring PTRS groups. The phase deviation for each PTRS group is determined as the time domain arithmetic mean phase deviation of all PTRS symbols in the group. + +### 5.3.3 EVM calculation flow with PTRS + +Figure 5.3.3-1 shows a generalized EVM calculator signal flow with PTRS processing. In the flow chart, for CP-OFDM, the DFT and IDFT blocks are replaced by unity blocks; For DFT-s-OFDM, all blocks pertaining to layer 2 signals are disabled due to RAN1 has not introduced rank 2 UL. In Rel-18, there is no PTRS configuration for UL 256QAM EVM test, Figure 5.3.3-1 is just for reference. + +![Figure 5.3.3-1: A generalized 2-Rx EVM calculator with PTRS processing. The diagram shows two receive paths (Port 1 and Port 2) entering RF CORRECTION blocks. The outputs are split: one path goes through FFT @ Δf to DMRS based MIMO channel estimation, then MIMO equalization, then IDFT, then PTRS Extraction + de-rotation of symbols, then DFT, resulting in NS1 and NS2 signals. These are used for LSE channel estimate for L1 and L2. The other path from RF CORRECTION goes through FFT @ timing to MIMO equalization, then L1 equalization and L2 equalization, then IDFT, then PTRS Extraction + de-rotation of symbols. The outputs are combined with NS1 and NS2 signals at summation nodes to produce EVM1 and EVM2 outputs. Red dashed lines indicate feedback loops from the LSE channel estimates back to the DMRS based MIMO channel estimation and MIMO equalization blocks.](5fc9d10a31977210e289bf770051feff_img.jpg) + +Figure 5.3.3-1: A generalized 2-Rx EVM calculator with PTRS processing. The diagram shows two receive paths (Port 1 and Port 2) entering RF CORRECTION blocks. The outputs are split: one path goes through FFT @ Δf to DMRS based MIMO channel estimation, then MIMO equalization, then IDFT, then PTRS Extraction + de-rotation of symbols, then DFT, resulting in NS1 and NS2 signals. These are used for LSE channel estimate for L1 and L2. The other path from RF CORRECTION goes through FFT @ timing to MIMO equalization, then L1 equalization and L2 equalization, then IDFT, then PTRS Extraction + de-rotation of symbols. The outputs are combined with NS1 and NS2 signals at summation nodes to produce EVM1 and EVM2 outputs. Red dashed lines indicate feedback loops from the LSE channel estimates back to the DMRS based MIMO channel estimation and MIMO equalization blocks. + +Figure 5.3.3-1: A generalized 2-Rx EVM calculator with PTRS processing + +## 5.4 Implementation impact for UE + +The UE EVM consists of several contributing impairments such as phase noise, PA non-linearity, digital impairments etc. It is worth to note that examples of improved phase noise profile, PA non-linearity and IQ image reflect different implementations. Actually, in a practical implementation process the impact of each of the EVM contributors need to be traded off with each other to meet the final EVM requirement. In the MPR study, the limit factor is EVM for FR2-1 UL 256QAM, in order to achieve the target EVM limit (3.5%), some power back-off is needed, and it can be optimized by adopting different UE implementations. + +## 5.5 Specification impact + +The specification impacts for UE part include MPR, EVM and related parameters, this new feature will be introduced in the corresponding clause 6.1, 6.2.2, 6.4.2.1 for single carrier operation, and 6.2A.2.2, 6.2A.2.3, 6.2A.2.6 for intra-band CA of TS 38.101-2. + +About the MPR of both intra-band contiguous and non-contiguous CA, considering the worst situation for PA in wider channel bandwidth for 256 QAM, the additional relaxation is needed based on the 3 dB relaxation for 29GHz and 4dB relaxation for 39GHz compared to the MPR of intra-band CA in 64QAM. + +## 5.6 Conclusion + +The feasibility of FR2-1 UL 256QAM has been evaluated, including link level simulation, system level simulation and implementation study. Based on the study output, it can be concluded that FR2-1 UL 256QAM is feasible and beneficial for PC1/2/5, and corresponding requirements has been specified and introduced TS 38.101-2 v18.3.0. + +And during the meetings discussion, some agreements are achieved as following: + +Key agreements: + +R4-2214453 WF in RAN4 #104e + +- First focus on PC1, PC2, PC5. +- Discussion on PC3 is not precluded and handled as second priority. + +R4-2217729 WF in RAN4 #104 bis + +- 3.5% EVM for 29GHz, FFS for operating SNR. +- The target power class is PC1, PC2, and PC5. +- 3.5% EVM for 39GHz and using average value FFS for operating SNR with limited MCS. +- The limited MCS is the subset of MCS with 256QAM +- FFS on the list of MCS +- Decide the operating SNR based on list of MCS +- The target power class is PC1, PC2, and PC5. +- To consider ICI compensation only if sufficient performance improvement is shown by proponent with explanation of the underlying algorithm. + +R4-2220810 WF in RAN4 #105 + +- Consider operating SNR as 28 dB with MCS 20~23 for 29GHz averaged based on the submitted results from these two meetings. +- Consider operating SNR as 30 dB with limited MCS 20~22 for 39GHz averaged based on the submitted results from two meetings. +- UL 256QAM is unfeasible for 48GHz in Rel-18 + +- The capability for support of UL256QAM is defined as per band per band combinations + +### R4-2303709 WF in RAN4 #106 + +- For 29GHz, UL 256 QAM for PC1/PC2/PC5 UEs is feasible. +- For 39GHz, UL 256 QAM for PC1/PC2/PC5 UEs is feasible. +- Limit MCS with 256QAM for 29GHz to the range of MCS#20, #21, #22 and #23. +- Limit MCS with 256QAM for 39GHz to the range of MCS#20, #21 and #22. +- Adopt 28 dB as operating SNR for 29GHz. +- Adopt 30 dB as operating SNR for 39GHz. +- For MPR evaluation, only consider the total value of 3.5% for Tx EVM. + - Companies need to clarify the components of Tx EVM in their simulation results, including + - Phase noise + - Value for IQ imbalance + - PA and transmitter non-linearity + - PTRS correction methods +- For CP-OFDM + - PTRS correction is implemented by de-rotation of each sub carrier in an OFDM symbol. The de-rotation angle is estimated as the frequency domain average of the phase rotation of all the PTRS tones in the allocation. +- For DFT-s-OFDM: + - PTRS correction is implemented by de-rotation of each time-domain symbol by the estimated instantaneous phase deviation. + - The instantaneous phase deviation impacting a data symbol due to DUT phase noise is estimated by linearly interpolating between the phase deviations determined for the nearest neighbouring PTRS groups. The phase deviation for each PTRS group is determined as the time domain arithmetic mean phase deviation of all PTRS symbols in the group. + - The EVM calculation signal flow including PTRS processing shall be included in the annex of 38.101-2 as normative content. + +![Block diagram of a MIMO receiver processing pipeline. It shows two ports (Port 1 and Port 2) entering RF CORRECTION blocks. The outputs go to FFT @ ADR blocks and then to DMRS based MIMO channel estimation. This is followed by MIMO equalization. The signal then splits into two paths: one for data (IDFT, PTRS Extraction + de-rotation of symbols, DFT, LSE channel estimate for L1/L2) and one for timing (FFT @ timing, MIMO equalization, L1/L2 equalization, IDFT, PTRS Extraction + de-rotation of symbols). The timing path outputs are combined with NS1 and NS2 signals to produce EVML1 and EVML2 outputs.](e01c6273c4177746475715ee9c17a882_img.jpg) + +Block diagram of a MIMO receiver processing pipeline. It shows two ports (Port 1 and Port 2) entering RF CORRECTION blocks. The outputs go to FFT @ ADR blocks and then to DMRS based MIMO channel estimation. This is followed by MIMO equalization. The signal then splits into two paths: one for data (IDFT, PTRS Extraction + de-rotation of symbols, DFT, LSE channel estimate for L1/L2) and one for timing (FFT @ timing, MIMO equalization, L1/L2 equalization, IDFT, PTRS Extraction + de-rotation of symbols). The timing path outputs are combined with NS1 and NS2 signals to produce EVML1 and EVML2 outputs. + +R4-2306603 WF in RAN4 #106 bis + +R4-2310260 WF in RAN4 #107 + +- Phase noise profiles evaluation for 29GHz + - Both of new phase noise profiles from Qualcomm and MTK for 29GHz are feasible for MPR simulation. + - New phase noise profiles using the pole-zero method based on following function: +- Parameters from Qualcomm + +| PSD0 | 32 dB | | | | +|--------|-----------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 6e5 | 4.7 | 8e5 | 5.3 | +| 3 | 8e5 | 2.0 | 1.1e6 | 2.5 | + +- Parameters from MTK + +Parameters for 29.55 GHz PLL phase noise model + +| PSD0 | 860.4 (29.35dB) | | | | +|--------|-----------------|----------------|-----------|----------------| +| $n, m$ | $f_{z,n}$ | $\alpha_{z,n}$ | $f_{p,m}$ | $\alpha_{p,m}$ | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 660e3 | 2.7 | 1.6e6 | 3.3 | +| 3 | 182e6 | 2.53 | 30e6 | 1 | + +- Phase noise profiles evaluation for 39GHz + - The new phase noise profile from MTK for 39GHz is feasible for MPR simulation. + - New phase noise profile using the pole-zero method based on following function: +- Parameters from MTK + +### Parameters for 39 GHz PLL phase noise model + +| PSD0 | 1498.7 (31.76dB) | | | | +|-------------|------------------------|------------------------|------------------------|------------------------| +| n,m | fz,n | az,n | fp,m | ap,m | +| 1 | 3e3 | 2.37 | 1 | 3.3 | +| 2 | 620e3 | 2.7 | 1.6e6 | 3.3 | +| 3 | 240e6 | 2.53 | 30e6 | 1 | + +- The minimum EIRP requirements for EVM test + - For PC1, PC2 and PC5: + - The minimum EIRP for UL 256 QAM for EVM test is relaxed by 14 dB compared to QPSK (or more than 7dB compared to 64QAM) + +### R4-2314677 WF in RAN4 #108 + +- -25dB/-20dB IQ image and -25dBc/-20dBc carrier leakage should be improved for UE supporting UL 256QAM. +- There is no change of the requirements for other modulation orders +- It shall be better than -36dB IQ image and -36dBc carrier leakage for UL 256QAM. +- No PTRS configuration for EVM test for CP-OFDM and DFI-s-OFDM. + +### R4-2317596 WF in RAN4 #108bis + +- The single CC MPR for PC1 in 256QAM operation shall be 3 dB more than that of 64QAM. +- The single CC MPR for PC2 in 256QAM operation shall be 3 dB more than that of 64QAM. +- The single CC MPR for PC5 in 256QAM operation shall be 3 dB more than that of 64QAM. +- The single CC MPR for PC1/2/5 in 256QAM operation shall be 4 dB more than that of 64QAM for 39 GHz band. +- No special treatment is necessary for inter-band CA MPRs for UL256QAM. +- No special treatment is necessary for UL MIMO MPRs for UL256QAM. +- RAN4 suggests to remove PC3 from the object of FR2-1 UL 256QAM in the WID + +#### Agreement in RAN4 #109: + +- The MPR of both intra-band contiguous and non-contiguous CA for PC1/2/5 in 256QAM operation shall be X dB more than that of intra-band CA in 64QAM operation for 29GHz bands, the X shall be as following: + - 3.5 dB up to 1400MHz aggregated channel bandwidths. + - 4 dB from 1400MHz aggregated channel bandwidths up to 2400MHz aggregated channel bandwidths. +- The MPR of both intra-band contiguous and non-contiguous CA for PC1/2/5 in 256QAM operation shall be X dB more than that of intra-band CA in 64QAM operation for 39GHz bands, the X shall be as following: + - 4.5 dB up to 1400MHz aggregated channel bandwidths. + - 5 dB from 1400MHz aggregated channel bandwidths up to 2400MHz aggregated channel bandwidths. + +# 6 Study for beam correspondence + +## 6.1 General + +3GPP defined 5G NR Frequency Range 2 bands with huge bandwidths which can cater 5G NR use cases requiring higher data rates. However, these bands are also subject to challenging propagating conditions such as high path loss, absorption from the environment, penetration losses to name a few. To overcome these, beam management procedures have been defined in 3GPP and beam correspondence is one of the main aspects of beam management. Beam correspondence is the ability of the UE to determine its uplink transmit beam based on downlink measurements on one or more Rx beams. UE beam correspondence functionality for RRC\_CONNECTED, RRC\_INACTIVE and initial access in IDLE have already been specified in the RAN1 and RAN2 specifications in Release 15 but FR2 UE beam correspondence requirements have not yet been defined for RRC\_INACTIVE and initial access in IDLE. + +Without UE beam correspondence requirements for initial access and RRC\_INACTIVE it is not possible to ensure good UE Random access Msg1/Msg A performance and uplink coverage in FR2 deployments due to varying UE performances. + +Rel-15 RRC\_INACTIVE and Rel-17 Small data transmission (SDT) have a large potential in UE power efficiency, latency and signalling overhead reduction. RRC\_INACTIVE allows for reduced latency and UE power saving, while SDT further enhances this for small data sessions. Considering that UE power savings are especially important for successful FR2 operations and good end-user experience, it would be important that the networks could efficiently utilize RRC\_INACTIVE and Small Data Transmissions for FR2 as well. + +Small data transmission procedures have been defined in 3GPP Rel-17 for SDT-RA for both two step and four step RA during RRC Inactive with a view of providing power saving opportunities and reducing overhead signalling. Without well performing UE beam correspondence support, wide usage of RRC\_INACTIVE and Small Data Transmission may not be feasible in practical FR2 deployments. To enable efficient use of RRC\_INACTIVE and Small Data Transmission in FR2 deployments to save UE power with reasonable latencies it is important to develop FR2 UE beam correspondence requirements for RRC\_INACTIVE in Rel-18. + +## 6.2 Implementation impact to UE + +One of the main characteristics of 5G NR beam management procedures is using directive beams hence requiring beam alignment between the UE and the base station. In FR2, the UE uses the beam refinement procedure to have narrow highly directive beams towards the gNodeB thereby increasing the uplink coverage. During a Random access procedure, the UE could use both the rough and fine beams. An example of UE simulated at 28 GHz (band n257) with 1x4 array placed on the sides of a smart phone in free space (no user presence). We assume all the UE surroundings, UE model, and antenna model are the same, only change the beam width. The simulation results in Figure 6.2-1 and Figure 6.2-2 show the EIRP coverage curves (using different simulation assumptions, UE surroundings, UE model, and antenna model may cause different results). + +![Figure 6.2-1: EIRP spherical coverage for single and multiple broad beams (Nokia). The graph shows Coverage [%] vs EIRP [dBm] for broad beams. Three curves are shown: Single-panel active (blue), Two simultaneously active panels (purple), and Three simultaneously active panels (red). A grey box indicates the 50%-ile requirement at 11.5 dBm. Coverage at 11.5 dBm is 100% for all cases. Coverage at 50% is marked at 16.5 dBm, 18 dBm, and 19 dBm for the single, two, and three panel cases respectively.](986edc52e3746371694590f8f64685a2_img.jpg) + +Figure 6.2-1 is a line graph titled "Broad UE beam with single element activation - Coverage at EIRP 11.5 dB for PC3". The y-axis represents Coverage [%] from 0 to 100, and the x-axis represents EIRP [dBm] from -2 to 23. A grey shaded region on the left indicates the 50%-ile requirement at 11.5 dBm. Three curves are plotted: a blue curve for "Single-panel active", a purple curve for "Two simultaneously active panels", and a red curve for "Three simultaneously active panels". All curves start at 100% coverage at 11.5 dBm. The blue curve drops to 50% coverage at 16.5 dBm, the purple curve at 18 dBm, and the red curve at 19 dBm. The graph also shows coverage levels of 98% and 87%. + +Figure 6.2-1: EIRP spherical coverage for single and multiple broad beams (Nokia). The graph shows Coverage [%] vs EIRP [dBm] for broad beams. Three curves are shown: Single-panel active (blue), Two simultaneously active panels (purple), and Three simultaneously active panels (red). A grey box indicates the 50%-ile requirement at 11.5 dBm. Coverage at 11.5 dBm is 100% for all cases. Coverage at 50% is marked at 16.5 dBm, 18 dBm, and 19 dBm for the single, two, and three panel cases respectively. + +Figure 6.2-1. EIRP spherical coverage for single and multiple broad beams (Nokia) + +![Figure 6.2-2: EIRP spherical coverage for envelope of narrow beams (Nokia). The graph shows Coverage [%] vs Gain [dB] for narrow beams. Three curves are shown: Single-panel active (blue), Two simultaneously active panels (purple), and Three simultaneously active panels (red). A grey box indicates the 50%-ile requirement at 11.5 dBm. Coverage at 11.5 dBm is 100% for all cases. Coverage at 50% is marked at 21.4 dB, 23.3 dB, and 24.2 dB for the single, two, and three panel cases respectively.](bc3afa6786f4e6e882edded4b64a3ed0_img.jpg) + +Figure 6.2-2 is a line graph titled "Narrow UE beams with 4 elements activation - Coverage at EIRP 11.5 dB for PC3". The y-axis represents Coverage [%] from 0 to 100, and the x-axis represents Gain [dB] from 8 to 28. A grey shaded region on the left indicates the 50%-ile requirement at 11.5 dBm. Three curves are plotted: a blue curve for "Single-panel active", a purple curve for "Two simultaneously active panels", and a red curve for "Three simultaneously active panels". All curves start at 100% coverage at 11.5 dBm. The blue curve drops to 50% coverage at 21.4 dB, the purple curve at 23.3 dB, and the red curve at 24.2 dB. + +Figure 6.2-2: EIRP spherical coverage for envelope of narrow beams (Nokia). The graph shows Coverage [%] vs Gain [dB] for narrow beams. Three curves are shown: Single-panel active (blue), Two simultaneously active panels (purple), and Three simultaneously active panels (red). A grey box indicates the 50%-ile requirement at 11.5 dBm. Coverage at 11.5 dBm is 100% for all cases. Coverage at 50% is marked at 21.4 dB, 23.3 dB, and 24.2 dB for the single, two, and three panel cases respectively. + +Figure 6.2-2. EIRP spherical coverage for envelope of narrow beams (Nokia) + +In this example, the current requirements in RRC\_CONNECTED mode of 11.5 dBm EIRP at 50MHz CBW and at 50%-ile is represented with the grey box. In Figure 6.2-1, the blue curve, purple curve, and red curve represent the spherical coverage of a broad beam from one panel, the sum of spherical coverages of 2 broad beams from two 2 panels, and the sum of spherical coverages of 3 broad beams from two 3 panels. In Figure 6.2-2, the blue curve represents the envelope of narrow beams with a single panel with 4 elements active. The purple curve represents the sum of envelopes of narrow beams from two 2 panels, and each with 4 elements active. The red curve represents the sum of envelopes of narrow beams from two 3 panels, and each with 4 elements active. + +As illustrated above, the spherical coverage at the 50%-ile is 16.5 – 19 dBm in Figure 6.2-1 and 21.4 – 24.2 dBm in Figure 6.2-2. The choice of using narrow beams and using broad beams has a big impact to the EIRP spherical coverage of a UE. We can also observe that the EIRP spherical coverage increases as the number of panels increases. + +During random access procedure for Initial access or even handovers, cell reselection and other scenarios where Random access is required, the 3GPP standards do not mandate the beam type the UE used. This is up to UE implementation if a rough beam or a narrow beam is to be used and how to achieve beam refinement. + +When UE needs to use a refined beam towards the gNodeB to increase the uplink coverage, UE can use SSB during the beam refinement procedure, which is periodically broadcasted every 20 ms. Alternatively, some companies think that UE can also use Tracking reference signal (TRS) signals defined in 3GPP Rel-17 in IDLE and INACTIVE modes. The TRS has a QCL relation to the SSB which can be configured in SIB17. The highest configurable allocation of TRS is two consecutive slots with 2 symbols per slot TRS for IDLE mode and a periodicity of 10 slots, which amounts to 4 occasions to refine UE beam every 1.25 ms in FR2 120 KHz SCS. UE has many more occasions to refine its beams using the IDLE/INACTIVE mode TRS as compared to when it uses SSB. + +## 6.3 Specification Impact + +### 6.3.1 RF + +In RRC connected state, beam correspondence requirement is considered as fulfilled if the UE meets the corresponding minimum peak EIRP and spherical coverage requirement for that power class with its chosen UL beams with or without relying on uplink beam sweeping. Beam correspondence tolerance requirement could also be considered for UE supporting beam management relying on UL beam sweeping. + +While in initial access and RRC\_INACTIVE state, UL beam sweeping is not available. The focus is how to specify UE beam correspondence requirements for SSB-based beam correspondence without UL beam sweeping as well as the implication to legacy UE capabilities. + +RAN4 discussion is mainly focused on minimum peak EIRP and spherical coverage requirement for beam correspondence in initial access and RRC\_INACTIVE state in R18. Since the UE behavior for beam management in initial access, RA-SDT and CG-SDT in RRC\_INACTIVE state is the same, common set of beam correspondence requirement can be defined to well accommodate these scenarios. To save test effort, the beam correspondence requirement only needs to be tested for initial access based on Msg1 which is thought to be the most critical scenario. + +#### 1. Minimum peak EIRP + +SSB based beam correspondence requirement for minimum peak for RRC\_CONNECTED state is based on fine beam implementation which is considered as too restrictive and not applicable for initial access from the perspective of addressing different beam type implementation. + +Minimum peak EIRP will not be considered for initial access. + +#### 2. Spherical coverage requirement at 50%-tile + +SSB-based spherical coverage requirement in RRC\_CONNECTED state is considered as the starting point for beam correspondence requirement in initial access. The impact of power control is further considered for beam correspondence requirement in initial access. + +Power tolerance is not considered in existing beam correspondence requirements. The main reason is the existing beam correspondence tests are specified in CONNECTED STATE, where there are multiple UL transmission opportunities and closed-loop power control is also available. In this case, UE has sufficient opportunity during the test to ramp up the power and make MOP accurate. + +In contrast, only open loop power control is possible for random access during initial access and UE may not have opportunity to transmit and complete the power control, i.e., precisely transmit at MOP, before sending Msg1. + +A simulation is performed to show the impact of power accuracy. Assuming that the maximum power deviation $\Delta P$ is 3.5 dB with a uniform distribution, the results show that when $\Delta P \sim U(-3.5, 3.5)$ , the performance degradation of 50%-tile spherical coverage is 0.3 dB. + +![Figure 6.3.1-1: Spherical coverage with ΔP~U (-3.5, 3.5). The graph shows the Cumulative Distribution Function (CDF) of Output Power (dBm) for 28 GHz. The x-axis ranges from 0 to 30 dBm, and the y-axis ranges from 0 to 1. Three curves are plotted: 'Original' (black), '50%@CDFOriginal case' (blue). An inset zooms in on the 0.5 CDF point, showing a 0.3 dB difference between the original case and the cases with power deviation.](66c6cb4ec14805010fceaba7baa26183_img.jpg) + +Figure 6.3.1-1: Spherical coverage with ΔP~U (-3.5, 3.5). The graph shows the Cumulative Distribution Function (CDF) of Output Power (dBm) for 28 GHz. The x-axis ranges from 0 to 30 dBm, and the y-axis ranges from 0 to 1. Three curves are plotted: 'Original' (black), '50%@CDFOriginal case' (blue). An inset zooms in on the 0.5 CDF point, showing a 0.3 dB difference between the original case and the cases with power deviation. + +Figure 6.3.1-1 Spherical coverage with $\Delta P \sim U(-3.5, 3.5)$ + +To accommodate this concern, RAN4 agreed that the spherical coverage requirement for beam correspondence in initial access is specified the same as the requirements in TABLE 6.2.1.3-3 in TS 38.101-2 with 2 dB power tolerance (e.g., min EIRP at 50%-tile CDF in initial access is up to 2dB less than the requirements specified in table 6.2.1.3-3 with its autonomously chosen UL beams and without uplink beam sweeping). + +The related feature is defined as mandatory for R18 onward UE. + +Side conditions + +For the beam correspondence in initial access and RRC\_INACTIVE, UE shall meet the spherical coverage requirement with the same side conditions for the SSB based enhanced beam correspondence. + +### 6.3.2 RRM + +No RRM specification impact is identified. + +## 6.4 Testing impact + +Unlike traditional RF requirements defined in the RRC\_CONNECTED state, beam correspondence for initial access needs to be verified in RRC\_IDLE, and several potential testability issues were raised during the discussion. The following aspects of test related issues were identified: + +- Verification in RRC\_IDLE + +In general, the power test needs to be averaged over a period, which requires the UE to remain in RRC\_IDLE and multiple PRACH transmission need to be triggered, so testing mode including holding RAR should be considered. The accumulative period of measurement for PRACH transmission shall be at least 1 ms. + +- Maximum output power for PRACH + +To guarantee stable test results, the requirement is defined and verified under maximum output power (MOP). Since the open loop power control is used for PRACH, how to ensure that the UE reaches and maintains MOP is a problem that has to be faced. During the initial access, the UE measures the RSRP and estimates the PL based on the broadcasted DL RS power at first. The required power for PRACH transmission will be calculated based on the estimated PL and the target Rx power at gNB and compares with the Pmax if configured. The power control for PRACH is defined in [1] as: + +$$P_{\text{PRACH},b,f,c}(i) = \min \left\{ P_{\text{CMAX},f,c}(i), P_{\text{PRACH,target},f,c} + PL_{b,f,c} \right\} \text{ [dBm]},$$ + +where $PL_{b,f,c}$ is a pathloss calculated by the UE in dB as *referenceSignalPower* – higher layer filtered RSRP in dBm, and *referenceSignalPower* is provided by *ss-PBCH-BlockPower*. The parameter $P_{\text{PRACH,target},f,c}$ is the PRACH target reception power *PREAMBLE\_RECEIVED\_TARGET\_POWER* provided by higher layers as specified in clause 5.1.3 of [2]: + +The MAC entity shall, for each Random Access Preamble: + +- 1> if *PREAMBLE\_TRANSMISSION\_COUNTER* is greater than one; and +- 1> if the notification of suspending power ramping counter has not been received from lower layers; and +- 1> if LBT failure indication was not received from lower layers for the last Random Access Preamble transmission; and +- 1> if SSB or CSI-RS selected is not changed from the selection in the last Random Access Preamble transmission; +- 2> increment *PREAMBLE\_POWER\_RAMPING\_COUNTER* by 1. +- 1> select the value of *DELTA\_PREAMBLE* according to clause 7.3; + +- 1) set PREAMBLE\_RECEIVED\_TARGET\_POWER to preambleReceivedTargetPower + DELTA\_PREAMBLE + (PREAMBLE\_POWER\_RAMPING\_COUNTER - 1) × PREAMBLE\_POWER\_RAMPING\_STEP + POWER\_OFFSET\_2STEP\_RA; + +UE can ramp up its power when RAR is held since it will trigger PRACH retransmission, and adjusting each individual RA response window may affect the overall test time. UE may also achieve MOP quickly by setting the *preambleReceivedTargetPower* properly with as few as possible PRACH re-transmission. Based on the analysis above, The PRACH can achieve MOP by holding RAR with well-defined parameters. In addition, during the initial access, UE might start transmitting preamble once it detects the SSB RSRP higher than preconfigured threshold on one RX beam, even if this RX beam is not the optimal one that UE could form, so the test function need to be considered. The details of test function and the details of the parameter configured in the test can be left to RAN5. + +- Beam lock function + +Currently, the beam lock function is only available in the RRC\_CONNECTED state, and if the beam lock function is absent during the verification in RRC\_IDLE, many complex issues will appear, e.g., when the RAR is held to trigger PRACH retransmission, UE may attempt other beams since the RAR is not received which may lead to unstable test. It also will be difficult to measure the $\theta$ (or $\phi$ ) component EIRP under $\phi$ (or $\theta$ ) link polarization without beam lock function. In [3], the LS from RAN5 concludes it is feasible to introduce beam lock function for RRC\_IDLE, so the concern above can be solved. RAN4 concludes that dedicated beam lock function for RRC\_IDLE state is needed, and the details of new beam lock function design can be left to RAN5. + +- Impact of power control accuracy + +[TBA] + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|-----------------------|-----------------|-------------|-----------|------------|------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN4 #104-e | R4-2212590 | | | | TR skeleton | 0.0.1 | +| 2022-10 | RAN4 #104-bis-e | R4-2217730 | | | | TP for TR 38.891 on link level simulation assumptions for FR2 UL 256QAM | 0.1.0 | +| 2022-11 | RAN4 #105 | R4-2219122 | | | | TP for TR 38.891 on link level simulation results and system level simulation assumption for FR2 UL 256QAM | 0.2.0 | +| 2023-02 | RAN4 #106 | R4-2303490 | | | | TP for TR 38.891 on simulation results and system level simulation assumptions for FR2 UL 256QAM | 0.3.0 | +| 2023-04 | RAN4 #106bis-e | R4-2305067 | | | | TP for TR 38.891 on system level simulation results for FR2 UL 256QAM | 0.4.0 | +| 2023-04 | RAN4 #106bis-e | R4-2306602 | | | | TP for TR 38.891: General and specification impact | 0.4.0 | +| 2023-05 | RAN4 #107 | R4-2308804 | | | | TP for TR 38.891 on simulation assumptions for phase noise profiles evaluation and MPR simulation results for FR2 UL 256QAM | 0.5.0 | +| 2023-05 | RAN4 #107 | R4-2307231 | | | | TP to TR 38.891: System level simulation results for FR2-1 UL 256QAM | 0.5.0 | +| 2023-05 | RAN4 #107 | R4-2310291 | | | | TP for TR 38.891: General and Specification impact | 0.5.0 | +| 2023-05 | RAN4 #107 | R4-2310292 | | | | TP for TR 38.891: Beam type and DRX implications | 0.5.0 | +| 2023-05 | RAN4 #107 | R4-2310293 | | | | TP for test related issue of beam correspondence in initial access | 0.5.0 | +| 2023-08 | RAN4 #108 | R4-2312684 | | | | TP for TR 38.891 on simulation results of phase noise profiles evaluation and MPR for FR2 UL 256QAM | 0.6.0 | +| 2023-10 | RAN4 #108bis | R4-2315435 | | | | TP for TR 38.891 on simulation results of phase noise profiles evaluation and MPR for FR2 UL 256QAM | 0.7.0 | +| 2023-11 | RAN4 #109 | R4-2321717 | | | | TP for TR 38.891 to capture the simulation results of MPR and introduce the general description for FR2 UL 256 QAM | 0.8.0 | +| 2023-11 | RAN4 #109 | R4-2321719 | | | | TP for TR 38.891 on impact of power control tolerance | 0.8.0 | +| 2023-11 | RAN4 #109 | R4-2318484 | | | | Text Proposal for TR 38.891 on Implementation impact to UE | 0.8.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38903/0087be03fe64bdec0075ae6ebde7bb34_img.jpg b/marked/Rel-18/38_series/38903/0087be03fe64bdec0075ae6ebde7bb34_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22ac12c2cd969419c886bc83ed8afc1da3a33c26 --- /dev/null +++ b/marked/Rel-18/38_series/38903/0087be03fe64bdec0075ae6ebde7bb34_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e3f863e321fa56c1851c9a88b285b67d1bfd44c1e0f0f0ca5ea28c964a4e2f0 +size 141976 diff --git a/marked/Rel-18/38_series/38903/12ee52d07df077addb627226083e63b8_img.jpg b/marked/Rel-18/38_series/38903/12ee52d07df077addb627226083e63b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b523990b6c0526d1bd8c788cb3155e191da63a34 --- /dev/null +++ b/marked/Rel-18/38_series/38903/12ee52d07df077addb627226083e63b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d653263ee9268fd6204a61ed2957c35c46e618d215bed1fc066f49dae59e5402 +size 109964 diff --git a/marked/Rel-18/38_series/38903/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-18/38_series/38903/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f032a23d25bf401f5b71fbaa1020e9c689d02d4 --- /dev/null +++ b/marked/Rel-18/38_series/38903/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1c3810fee9a0b03cf89a6e6499b61c6e0ffd23dceefca5aa6797e10733c1ed6 +size 21379 diff --git a/marked/Rel-18/38_series/38903/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-18/38_series/38903/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a1bdee3ed8a2388cf55f3b22281982c5aced0bb --- /dev/null +++ b/marked/Rel-18/38_series/38903/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26604dccb5d2439d73f0f2f798da5bc8ff5627de50f7efb76e36a4ac5c8a1028 +size 61212 diff --git a/marked/Rel-18/38_series/38903/390120de4fe440c42fea8154fcaad334_img.jpg b/marked/Rel-18/38_series/38903/390120de4fe440c42fea8154fcaad334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e650d576b0982b493902cd8b77dbe982526f138a --- /dev/null +++ b/marked/Rel-18/38_series/38903/390120de4fe440c42fea8154fcaad334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c7f130e879906ecd33138d296639faa73faf66a718087e428b5baa96b116ed0 +size 10092 diff --git a/marked/Rel-18/38_series/38903/44ffa7f0e6419d046ab4fed0faaf7738_img.jpg b/marked/Rel-18/38_series/38903/44ffa7f0e6419d046ab4fed0faaf7738_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ab8181b259ac0a4fe9f88b1082fbdc8ca476f4a --- /dev/null +++ b/marked/Rel-18/38_series/38903/44ffa7f0e6419d046ab4fed0faaf7738_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11ed530bc97ba16cc3bec3fef5d43152dffaa7360b2eb75c5657998293283e9f +size 18113 diff --git a/marked/Rel-18/38_series/38903/45fba45707b417219df161f8bce0f75a_img.jpg b/marked/Rel-18/38_series/38903/45fba45707b417219df161f8bce0f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33b869a7330d809068f0b3a5c67791c91e52669f --- /dev/null +++ b/marked/Rel-18/38_series/38903/45fba45707b417219df161f8bce0f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0ea40fd604db8b794300f0c548e756ba91644f3fbf41c6042555bc476609a49 +size 21937 diff --git a/marked/Rel-18/38_series/38903/58f42a91047786934d8a7e258d581ca2_img.jpg b/marked/Rel-18/38_series/38903/58f42a91047786934d8a7e258d581ca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1de200534f4c82e87b6e275ac68b5e9527e9b332 --- /dev/null +++ b/marked/Rel-18/38_series/38903/58f42a91047786934d8a7e258d581ca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22f1554e55f94fea5b272d7398e5899058c207b86863727074526fcbe62c52b0 +size 18363 diff --git a/marked/Rel-18/38_series/38903/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38903/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63b037f4a2274941a348bb4436411e3bc8031fac --- /dev/null +++ b/marked/Rel-18/38_series/38903/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:118b63541b3afa80a167750ea0cb0f8634c1a9d8ac60d1808bd8259ea674da82 +size 5670 diff --git a/marked/Rel-18/38_series/38903/812b773680b611c18d49243e102b895a_img.jpg b/marked/Rel-18/38_series/38903/812b773680b611c18d49243e102b895a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..693e4d089cfd2862a54d704ef0f9c9b315cf3956 --- /dev/null +++ b/marked/Rel-18/38_series/38903/812b773680b611c18d49243e102b895a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a2dae99d1f8e69587da8522f59a1d6a8e9954619ea7815c54708eb4ef2c4cf9 +size 18101 diff --git a/marked/Rel-18/38_series/38903/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg b/marked/Rel-18/38_series/38903/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dcdb429e28dd4e5aa62a08fc948254f575e785b --- /dev/null +++ b/marked/Rel-18/38_series/38903/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55310bac8e2c4ffcd4b39fd0664f441c27215c576557eb583a0b6a9735540609 +size 10747 diff --git a/marked/Rel-18/38_series/38903/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-18/38_series/38903/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a765b3e64f35f5fabe6a2db1b9280e77c31db21 --- /dev/null +++ b/marked/Rel-18/38_series/38903/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:510d18e491de46ce4ea1001e3323bd7a4804f947265a8e3ba426920d068de274 +size 18445 diff --git a/marked/Rel-18/38_series/38903/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg b/marked/Rel-18/38_series/38903/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26ca1b9420c6025c50d8b18e7bca40ea6b37d07b --- /dev/null +++ b/marked/Rel-18/38_series/38903/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623d6f78c2d0a5f25ec58822aa5e63817d460a783442f007da8d6b83f22be1a6 +size 41069 diff --git a/marked/Rel-18/38_series/38903/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg b/marked/Rel-18/38_series/38903/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38162ed24f9ec8a51bdc3dc2263975a0503d78da --- /dev/null +++ b/marked/Rel-18/38_series/38903/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9448f6aa9983d1b0ff12728f2f59ea6f97fb3a6d49bf3d605becc50896475b9 +size 15319 diff --git a/marked/Rel-18/38_series/38903/ac42de838505beb048fb1267c46de428_img.jpg b/marked/Rel-18/38_series/38903/ac42de838505beb048fb1267c46de428_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dd962a9bcb7b9d1a3b3c8b430b73cb92ebc109b --- /dev/null +++ b/marked/Rel-18/38_series/38903/ac42de838505beb048fb1267c46de428_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce216f1c6da1ea71313a4d8b89e7f8775079a6e7a5e314da6420224ec82fd328 +size 21296 diff --git a/marked/Rel-18/38_series/38903/b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg b/marked/Rel-18/38_series/38903/b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccbe05e3975b598f32baac7a5861b33e1561d30d --- /dev/null +++ b/marked/Rel-18/38_series/38903/b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a374efe7982fd00297cbc4d24cdddcf2deb6b36b0daff3b8305c3716c30e71e +size 30244 diff --git a/marked/Rel-18/38_series/38903/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg b/marked/Rel-18/38_series/38903/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a64199a6f5004ec287789f2654964d5ccd1d56cd --- /dev/null +++ b/marked/Rel-18/38_series/38903/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dba923e4f8c7a35fbf0fda307bdc48d0d4c9f50516a14865d577b809f420649b +size 21039 diff --git a/marked/Rel-18/38_series/38903/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg b/marked/Rel-18/38_series/38903/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..982a7eeb562cc3a49b36fe0e54208e8f8c72d0b3 --- /dev/null +++ b/marked/Rel-18/38_series/38903/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea8a78e8319a5df0517b824f95a2ec592308385836c29df0ce62518335c92006 +size 23725 diff --git a/marked/Rel-18/38_series/38903/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-18/38_series/38903/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35483bb2bfc2f6e4cb9a6c8ce4b34a754d906234 --- /dev/null +++ b/marked/Rel-18/38_series/38903/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7e2b3701b1654fad362cfc0baa854ea973c5eb0b338a0d381b638e279aae1a5 +size 39466 diff --git a/marked/Rel-18/38_series/38903/c6e0b9030f9fb81435eaf9cb71532614_img.jpg b/marked/Rel-18/38_series/38903/c6e0b9030f9fb81435eaf9cb71532614_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e6b15c0f71d4ae12874a42ffbd67b24722e1622 --- /dev/null +++ b/marked/Rel-18/38_series/38903/c6e0b9030f9fb81435eaf9cb71532614_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e47a23c003eebdfffdbaa1b8c3a5604f540939d54515134d48bf6d0f817b5333 +size 10592 diff --git a/marked/Rel-18/38_series/38903/d16e5a3857155ee2837d851305ee8036_img.jpg b/marked/Rel-18/38_series/38903/d16e5a3857155ee2837d851305ee8036_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..904374be00bbdeb511e80181d32338034018a6de --- /dev/null +++ b/marked/Rel-18/38_series/38903/d16e5a3857155ee2837d851305ee8036_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85198c81e84e4d46ef5e67fa7c31506a4fa6ee3132a0b0f59039042d45803f1a +size 5170 diff --git a/marked/Rel-18/38_series/38903/df743a70d0295e880847c81ef47df4b5_img.jpg b/marked/Rel-18/38_series/38903/df743a70d0295e880847c81ef47df4b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecd42cb29aee2a27fd04cc2051d11ddb72ef7118 --- /dev/null +++ b/marked/Rel-18/38_series/38903/df743a70d0295e880847c81ef47df4b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:390395b8456fce2ba88abc318fdfd73f686b19a2d92e4f8b6c0a0a7b22588466 +size 21871 diff --git a/marked/Rel-18/38_series/38903/e466e4c4fb08567a109bb959a765225c_img.jpg b/marked/Rel-18/38_series/38903/e466e4c4fb08567a109bb959a765225c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..717806fc0457516009e5d22c5d198453b485a923 --- /dev/null +++ b/marked/Rel-18/38_series/38903/e466e4c4fb08567a109bb959a765225c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b888d6af930fcd13ee8fca6ba1371a7932d54e6d67e29c52adeb8704d3f2128 +size 77954 diff --git a/marked/Rel-18/38_series/38903/e985b32357f2d9ebae5f53130132dd37_img.jpg b/marked/Rel-18/38_series/38903/e985b32357f2d9ebae5f53130132dd37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86141e3102d410aaff5e66863f6757006b64ace6 --- /dev/null +++ b/marked/Rel-18/38_series/38903/e985b32357f2d9ebae5f53130132dd37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c516bfd7f650d17f561c250ce9a767e33655eadc4bc92463103b2e7823e0d76 +size 139145 diff --git a/marked/Rel-18/38_series/38903/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg b/marked/Rel-18/38_series/38903/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2089b85a348247113f72ba7ca5cf86f1722e9a1 --- /dev/null +++ b/marked/Rel-18/38_series/38903/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a1a2735faedbbcac0813f6f0861952e5903567bd2def5b9ebff2ae6735f1603 +size 6146 diff --git a/marked/Rel-18/38_series/38903/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-18/38_series/38903/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..740de548f39f71cd717bd4259cf236f2377a29c6 --- /dev/null +++ b/marked/Rel-18/38_series/38903/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c998933ad00a48a3c178bfe14271e6f76e82734ceab261dc3956b2a2c63d4b6 +size 11119 diff --git a/marked/Rel-18/38_series/38903/f63b26e4e96e0f42eb14f1ad67838ec5_img.jpg b/marked/Rel-18/38_series/38903/f63b26e4e96e0f42eb14f1ad67838ec5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e226786bb2effb55afbadef4aace35e3ea9bb3ce --- /dev/null +++ b/marked/Rel-18/38_series/38903/f63b26e4e96e0f42eb14f1ad67838ec5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46151d1f95a56aa717ba79623519824ccddebf4cd94a057c42442ccf0a87fadc +size 27179 diff --git a/marked/Rel-18/38_series/38903/faff5ea2bac20b616b62b35da5a5d67c_img.jpg b/marked/Rel-18/38_series/38903/faff5ea2bac20b616b62b35da5a5d67c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8509f214a3c5a3d950ab5f21b82119f012f46421 --- /dev/null +++ b/marked/Rel-18/38_series/38903/faff5ea2bac20b616b62b35da5a5d67c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ba84e467c7fe11a5a5da7f96787ef2cb1abdd992ff9c7a3d4708a07852f1328 +size 65085 diff --git a/marked/Rel-18/38_series/38903/fbdb9a4a74e70721e19f3d576ba7b651_img.jpg b/marked/Rel-18/38_series/38903/fbdb9a4a74e70721e19f3d576ba7b651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e356cb83b917026b5c8d3e2bcf3de09e6c7683b --- /dev/null +++ b/marked/Rel-18/38_series/38903/fbdb9a4a74e70721e19f3d576ba7b651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdedc5b1155186b3d9b3f5af9a49b26ea8806a245107fa052840cc9057ff5621 +size 9449 diff --git a/marked/Rel-18/38_series/38903/ff4ed9c9daa873625e772a2f5e9a6a6e_img.jpg b/marked/Rel-18/38_series/38903/ff4ed9c9daa873625e772a2f5e9a6a6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fdaed343c72c949da44857a7b2ba3064e07c79c --- /dev/null +++ b/marked/Rel-18/38_series/38903/ff4ed9c9daa873625e772a2f5e9a6a6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8ff10242304221f6c487b1c9bb2edd02cc51e25f47ac24681a2800d37fdf48e +size 99782 diff --git a/marked/Rel-18/38_series/38903/raw.md b/marked/Rel-18/38_series/38903/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d0c6fd371d0a088f696c7a1f1fea1ed8222e44fa --- /dev/null +++ b/marked/Rel-18/38_series/38903/raw.md @@ -0,0 +1,10493 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR;** + +# **Derivation of test tolerances and measurement uncertainty for User Equipment (UE) conformance test cases (Release 18)** + +![5G logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](390120de4fe440c42fea8154fcaad334_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text are three red, curved lines representing signal waves. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## Keywords + +5G + +## **3GPP** + +## Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +## **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword..... | 9 | +| Introduction..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Symbols..... | 11 | +| 3.3 Abbreviations..... | 11 | +| 4 General Principles..... | 12 | +| 4.1 Principle of Superposition..... | 12 | +| 4.2 Sensitivity analysis..... | 12 | +| 4.3 Statistical combination of uncertainties..... | 12 | +| 4.4 Correlation between uncertainties..... | 13 | +| 4.4.1 Uncorrelated uncertainties..... | 13 | +| 4.4.2 Positively correlated uncertainties..... | 14 | +| 4.4.3 Negatively correlated uncertainties..... | 14 | +| 4.4.4 Treatment of uncorrelated uncertainties..... | 15 | +| 4.4.5 Treatment of positively correlated uncertainties with adverse effect..... | 15 | +| 4.4.6 Treatment of positively correlated uncertainties with beneficial effect..... | 15 | +| 4.4.7 Treatment of negatively correlated uncertainties..... | 15 | +| 5 Determination of Test System Uncertainties..... | 16 | +| 5.1 General..... | 16 | +| 5.2 Uncertainty figures..... | 16 | +| 6 Determination of Test Tolerances..... | 16 | +| 6.1 General..... | 16 | + +| | | | +|--------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------| +| 7 | Grouping of test cases defined in TS 38.521-4..... | 16 | +| 8 | Grouping of test cases defined in TS 38.533..... | 17 | +| 9 | Grouping of test cases defined in TS 37.571-1..... | 37 | +| Annex A: Derivation documents for test tolerance..... | | 40 | +| A.1 | Void..... | 40 | +| A.2 | Handling of common Test Tolerance topics for radiated test cases defined in TS 38.533..... | 40 | +| A.2.1 | Angles of Arrival..... | 40 | +| A.2.1.1 | Relevant core requirements..... | 40 | +| A.2.1.2 | Modelling of variation within spherical coverage directions..... | 41 | +| A.2.1.3 | Principles for Test Tolerance analysis..... | 41 | +| A.2.2 | UE Fine beams and Rough beams..... | 41 | +| A.2.2.1 | Relevant core requirements..... | 41 | +| A.2.2.2 | Modelling of Fine beams and Rough beams..... | 43 | +| A.2.2.3 | Principles for Test Tolerance analysis..... | 43 | +| A.2.3 | UE internal noise..... | 43 | +| A.2.3.1 | Relevant core requirements..... | 43 | +| A.2.3.2 | Calculation method..... | 44 | +| A.2.3.3 | Principles for Test Tolerance analysis..... | 44 | +| A.2.4 | Calculation of Es/Iot at UE baseband..... | 44 | +| A.2.4.1 | Relevant core requirements..... | 44 | +| A.2.4.2 | Calculation method..... | 45 | +| A.2.4.3 | Principles for Test Tolerance analysis..... | 46 | +| A.2.5 | Calculation of Applied Io..... | 46 | +| A.2.5.1 | Relevant core requirements..... | 46 | +| A.2.5.2 | Calculation method..... | 46 | +| A.2.5.3 | Principles for Test Tolerance analysis..... | 47 | +| A.2.6 | UE Reported RSRP and UE gain..... | 47 | +| A.2.6.1 | Relevant core requirements..... | 47 | + +| | | | +|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------| +| A.2.6.2 | Absolute RSRP..... | 47 | +| A.2.6.3 | Relative RSRP, 2 levels on same cell, same Angle of Arrival..... | 49 | +| A.2.6.4 | Relative RSRP, 2 intra-frequency cells, same Angle of Arrival..... | 49 | +| A.2.6.5 | Relative RSRP, 2 inter-frequency cells, same Angle of Arrival..... | 49 | +| A.2.6.6 | Relative RSRP, 2 cells, different Angles of Arrival..... | 50 | +| A.2.6.7 | Principles for Test Tolerance analysis..... | 50 | +| A.2.7 | Intra-frequency cells without AWGN, same Angle of Arrival..... | 51 | +| A.2.7.1 | Test system..... | 51 | +| A.2.7.2 | Calculation method for Es/Iot at UE baseband..... | 51 | +| A.2.7.3 | Calculation method for Applied Io..... | 52 | +| A.2.7.4 | Principles for Test Tolerance analysis..... | 52 | +| A.3 | Test Tolerance analysis templates for radiated test cases awaiting completion..... | 53 | +| A.4 | Design of radiated test cases defined in TS 38.533..... | 53 | +| A.4.1 | Downlink considerations..... | 53 | +| A.4.1.1 | Side conditions for Rx Beam Peak angle of arrival..... | 53 | +| A.4.1.2 | Side conditions for Spherical Coverage angle of arrival..... | 53 | +| A.4.1.3 | Test case design options to increase downlink dB range..... | 54 | +| Annex B: Acceptable uncertainty of test system for test cases defined in TS 38.521-2 for radiative testing..... | | 57 | +| B.1 | Uncertainty budget calculation principle..... | 57 | +| B.1.1 | Uncertainty budget calculation principle for DFF..... | 57 | +| B.1.2 | Uncertainty budget calculation principle for IFF..... | 58 | +| B.1.3 | Uncertainty budget calculation principle for NFTF..... | 58 | +| B.2 | Measurement error contribution descriptions..... | 58 | +| B.2.1 | Measurement error contribution descriptions for DFF..... | 58 | +| B.2.1.1 | Positioning misalignment..... | 58 | +| B.2.1.2 | Measure distance uncertainty..... | 58 | +| B.2.1.3 | Quality of quiet zone..... | 58 | +| B.2.1.4 | Mismatch..... | 58 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------------------------|----| +| B.2.1.5 | Standing Wave Between the DUT and measurement antenna..... | 60 | +| B.2.1.6 | Uncertainty of the RF power measurement equipment..... | 60 | +| B.2.1.7 | Phase curvature..... | 61 | +| B.2.1.8 | Amplifier uncertainties..... | 61 | +| B.2.1.9 | Random uncertainty..... | 61 | +| B.2.1.10 | Influence of the XPD..... | 62 | +| B.2.1.11 | Insertion loss Variation..... | 66 | +| B.2.1.12 | RF leakage (from measurement antenna to receiver/transmitter)..... | 66 | +| B.2.1.13 | Misalignment of positioning System..... | 66 | +| B.2.1.14 | Uncertainty of the Network Analyzer..... | 66 | +| B.2.1.15 | Uncertainty of the absolute gain of the calibration antenna..... | 66 | +| B.2.1.16 | Positioning and pointing misalignment between the reference antenna and the measurement antenna..... | 66 | +| B.2.1.17 | gNB emulator uncertainty..... | 66 | +| B.2.1.18 | Phase centre offset of calibration..... | 67 | +| B.2.1.19 | Quality of quiet zone for calibration process..... | 67 | +| B.2.1.20 | Standing wave between reference calibration antenna and measurement antenna..... | 67 | +| B.2.1.21 | Influence of the calibration antenna feed cable (Flexing cables, adapters, attenuators, connector
repeatability)..... | 68 | +| B.2.1.22 | Influence of TRP measurement grid..... | 68 | +| B.2.1.23 | Influence of beam peak search grid..... | 68 | +| B.2.1.24 | Systematic error due to TRP calculation/quadrature..... | 68 | +| B.2.1.25 | Multiple measurement antenna uncertainty..... | 68 | +| B.2.1.26 | DUT repositioning..... | 68 | +| B.2.1.27 | Influence of noise..... | 68 | +| B.2.1.28 | Systematic error related to beam peak search..... | 69 | +| B.2.1.29 | Influence of spherical coverage grid..... | 69 | +| B.2.1.30 | Systematic error related to EIS spherical coverage..... | 69 | +| B.2.1.31 | Misalignment of DUT due to change of DUT orientation..... | 69 | +| B.2.1.32 | Additional Impact of Interferer ACLR..... | 69 | +| B.2.1.33 | Modulated Interferer uncertainty..... | 69 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------------------|----| +| B.2.1.34 | Void..... | 69 | +| B.2.1.35 | Influence of offset antenna for blocker signal..... | 69 | +| B.2.1.36 | Uncertainty of the RF relative power measurement equipment..... | 70 | +| B.2.2 | Measurement error contribution descriptions for IFF..... | 70 | +| B.2.2.1 | Positioning misalignment..... | 70 | +| B.2.2.2 | Measure distance uncertainty..... | 70 | +| B.2.2.3 | Quality of Quiet Zone..... | 71 | +| B.2.2.4 | Mismatch..... | 72 | +| B.2.2.5 | Standing wave between DUT and measurement antenna..... | 73 | +| B.2.2.6 | Uncertainty of the RF power measurement equipment..... | 74 | +| B.2.2.7 | Phase Curvature..... | 74 | +| B.2.2.8 | Amplifier Uncertainties..... | 74 | +| B.2.2.9 | Random uncertainty..... | 75 | +| B.2.2.10 | Influence of XPD..... | 75 | +| B.2.2.11 | Insertion Loss Variation..... | 76 | +| B.2.2.12 | RF leakage (from measurement antenna to receiver/transmitter)..... | 76 | +| B.2.2.13 | Misalignment of positioning system..... | 77 | +| B.2.2.14 | Uncertainty of the Network Analyzer..... | 77 | +| B.2.2.15 | Uncertainty of the absolute gain of the calibration antenna..... | 77 | +| B.2.2.16 | Positioning and pointing misalignment between the reference antenna and the measurement antenna..... | 78 | +| B.2.2.17 | gNB emulator uncertainty..... | 78 | +| B.2.2.18 | Phase centre offset of calibration..... | 78 | +| B.2.2.19 | Quality of the Quiet Zone for Calibration Process..... | 78 | +| B.2.2.20 | Standing wave between reference calibration antenna and measurement antenna..... | 79 | +| B.2.2.21 | Influence of the calibration antenna feed cable (Flexing cables, adapters, attenuators, connector repeatability)..... | 79 | +| B.2.2.22 | Influence of TRP measurement grid..... | 80 | +| B.2.2.23 | Influence of beam peak search grid..... | 80 | +| B.2.2.24 | Systematic error due to TRP calculation/quadrature..... | 80 | +| B.2.2.25 | Multiple measurement antenna uncertainty..... | 81 | + +| | | | +|----------|------------------------------------------------------------------|----| +| B.2.2.26 | DUT repositioning..... | 81 | +| B.2.2.27 | Influence of noise..... | 81 | +| B.2.2.28 | Systematic error related to beam peak search..... | 87 | +| B.2.2.29 | Influence of spherical coverage grid..... | 88 | +| B.2.2.30 | Systematic error related to EIS spherical coverage..... | 88 | +| B.2.2.31 | Misalignment of DUT due to change of DUT orientation..... | 88 | +| B.2.2.32 | Additional Impact of Interferer ACLR..... | 88 | +| B.2.2.33 | Modulated Interferer uncertainty..... | 89 | +| B.2.2.34 | Void..... | 89 | +| B.2.2.35 | Influence of offset antenna for blocker signal..... | 89 | +| B.2.2.36 | Uncertainty of the RF relative power measurement equipment..... | 89 | +| B.2.3 | Measurement error contribution descriptions for NFTF..... | 89 | +| B.2.3.1 | Axes Alignment..... | 89 | +| B.2.3.2 | Measurement Distance uncertainty..... | 89 | +| B.2.3.3 | Quality of the Quiet Zone..... | 90 | +| B.2.3.4 | Mismatch..... | 90 | +| B.2.3.5 | Multiple Reflections: Coupling Measurement Antenna and DUT..... | 90 | +| B.2.3.6 | Uncertainty of the RF power measurement equipment..... | 90 | +| B.2.3.7 | Phase curvature..... | 90 | +| B.2.3.8 | Amplifier uncertainties..... | 90 | +| B.2.3.9 | Random uncertainty..... | 90 | +| B.2.3.10 | Influence of the XPD..... | 90 | +| B.2.3.11 | NF to FF truncation..... | 90 | +| B.2.3.12 | Probe Polarization Amplitude and Phase..... | 90 | +| B.2.3.13 | Probe Array Uniformity (for multi-probe systems only)..... | 90 | +| B.2.3.14 | Uncertainty of the Network Analyzer..... | 91 | +| B.2.3.15 | Uncertainty of the absolute gain of the calibration antenna..... | 91 | +| B.2.3.16 | Phase Recovery Non-Linearity over signal bandwidth..... | 91 | +| B.2.3.17 | Probe Pattern Effect..... | 91 | +| B.2.3.18 | Phase centre offset of calibration..... | 91 | + +| | | | +|----------|-----------------------------------------------------------------|-----| +| B.2.3.19 | Quality of the Quiet Zone for Calibration Process..... | 91 | +| B.2.3.20 | Phase Drift and Noise..... | 91 | +| B.2.3.21 | Mismatch in the connection of the calibration antenna..... | 91 | +| B.2.3.22 | Influence of TRP measurement grid..... | 91 | +| B.2.3.23 | 91 | | +| B.2.3.24 | 91 | | +| B.2.3.25 | Leakage and Crosstalk..... | 91 | +| B.2.3.26 | Systematic error due to TRP calculation/quadrature..... | 92 | +| B.2.3.27 | Multiple measurement antenna uncertainty..... | 92 | +| B.2.3.28 | DUT repositioning..... | 92 | +| B.2.3.29 | Influence of noise..... | 92 | +| B.2.3.30 | Uncertainty of the RF relative power measurement equipment..... | 92 | +| B.3 | UE maximum output power..... | 92 | +| B.3.1 | Uncertainty budget format and assessment for DFF..... | 93 | +| B.3.2 | Uncertainty budget format and assessment for IFF..... | 96 | +| B.3.3 | Uncertainty budget format and assessment for NFTF..... | 109 | +| B.4 | UE maximum output power for modulation / channel bandwidth..... | 111 | +| B.4.1 | Uncertainty budget format and assessment for DFF..... | 111 | +| B.4.2 | Uncertainty budget format and assessment for IFF..... | 112 | +| B.4.3 | Uncertainty budget format and assessment for NFTF..... | 114 | +| B.5 | UE maximum output power with additional requirements..... | 114 | +| B.6 | Configured transmitted power with Power Boost..... | 115 | +| B.6.1 | Uncertainty budget format and assessment for DFF..... | 115 | +| B.6.2 | Uncertainty budget format and assessment for IFF..... | 117 | +| B.6.3 | Uncertainty budget format and assessment for NFTF..... | 126 | +| B.7 | Minimum Output power..... | 127 | +| B.7.1 | Uncertainty budget format and assessment for DFF..... | 128 | +| B.7.2 | Uncertainty budget format and assessment for IFF..... | 131 | + +| | | | +|----------|--------------------------------------------------------|-----| +| B.8 | Transmit OFF power..... | 140 | +| B.8.1 | Uncertainty budget format and assessment for DFF..... | 140 | +| B.8.2 | Uncertainty budget format and assessment for IFF..... | 143 | +| B.9 | ON/OFF time mask..... | 147 | +| B.9.1 | ON power subtest..... | 147 | +| B.9.1.1 | Uncertainty budget format and assessment for DFF..... | 147 | +| B.9.1.2 | Uncertainty budget format and assessment for IFF..... | 147 | +| B.9.2 | OFF power subtest..... | 147 | +| B.9.2.1 | Uncertainty budget format and assessment for DFF..... | 147 | +| B.9.2.2 | Uncertainty budget format and assessment for IFF..... | 148 | +| B.9a | Power control..... | 152 | +| B.9a.1 | Absolute power tolerance..... | 152 | +| B.9a.2 | Relative power control tolerance..... | 152 | +| B.9a.2.1 | Uncertainty budget format and assessment for DFF..... | 152 | +| B.9a.2.2 | Uncertainty budget format and assessment for IFF..... | 153 | +| B.9a.2.3 | Uncertainty budget format and assessment for NFTF..... | 154 | +| B.9a.3 | Aggregate Power control tolerance..... | 155 | +| B.9a.3.1 | Uncertainty budget format and assessment for DFF..... | 155 | +| B.9a.3.2 | Uncertainty budget format and assessment for IFF..... | 156 | +| B.9a.3.3 | Uncertainty budget format and assessment for NFTF..... | 157 | +| B.10 | Frequency error..... | 158 | +| B.10.1 | Uncertainty budget format and assessment for DFF..... | 158 | +| B.10.2 | Uncertainty budget format and assessment for IFF..... | 158 | +| B.11 | Carrier leakage..... | 159 | +| B.11.1 | Uncertainty budget format and assessment for DFF..... | 159 | +| B.11.2 | Uncertainty budget format and assessment for IFF..... | 162 | +| B.12 | Error Vector Magnitude..... | 167 | +| B.12.1 | Uncertainty budget format and assessment for DFF..... | 167 | + +| | | | +|-------------------|--------------------------------------------------------|-----| +| B.12.2 | Uncertainty budget format and assessment for IFF..... | 167 | +| B.13 to B.14..... | | 170 | +| B.15 | Occupied bandwidth..... | 170 | +| B.15.1 | Uncertainty budget format and assessment for DFF..... | 170 | +| B.15.2 | Uncertainty budget format and assessment for IFF..... | 170 | +| B.16 | Spectrum emission mask..... | 170 | +| B.16.1 | Uncertainty budget format and assessment for DFF..... | 171 | +| B.16.2 | Uncertainty budget format and assessment for IFF..... | 174 | +| B.17 | Adjacent Channel Leakage Ratio..... | 178 | +| B.17.1 | Uncertainty budget format and assessment for DFF..... | 179 | +| B.17.2 | Uncertainty budget format and assessment for IFF..... | 182 | +| B.18 | Spurious emissions..... | 186 | +| B.18.1 | Uncertainty budget format and assessment for DFF..... | 188 | +| B.18.2 | Uncertainty budget format and assessment for IFF..... | 191 | +| B.18.3 | Uncertainty budget format and assessment for NFTF..... | 214 | +| B.18a | Beam correspondence - EIRP..... | 214 | +| B.18a.1 | Uncertainty budget format and assessment for DFF..... | 214 | +| B.18a.2 | Uncertainty budget format and assessment for IFF..... | 215 | +| B.18a.3 | Uncertainty budget format and assessment for NFTF..... | 216 | +| B.19 | Reference Sensitivity..... | 217 | +| B.19.1 | Uncertainty budget format and assessment for DFF..... | 218 | +| B.19.2 | Uncertainty budget format and assessment for IFF..... | 218 | +| B.20 | 227 | | +| B.21 | Adjacent Channel Selectivity..... | 227 | +| B.21.1 | Uncertainty budget format and assessment for DFF..... | 227 | +| B.21.2 | Uncertainty budget format and assessment for IFF..... | 227 | + +| | | +|------------------------------------------------------------------------------------------------------------------------|------------| +| B.22 In-Band Blocking..... | 234 | +| B.22.1 Uncertainty budget format and assessment for DFF..... | 234 | +| B.22.2 Uncertainty budget format and assessment for IFF..... | 234 | +| B.23 235 | | +| B.24 235 | | +| B.25 Receiver spurious emissions..... | 235 | +| B.25.1 Uncertainty budget format and assessment for DFF..... | 236 | +| B.25.2 Uncertainty budget format and assessment for IFF..... | 239 | +| Annex C: Acceptable uncertainty of test system for test cases defined in TS 38.521-3 for radiative testing..... | 260 | +| Annex D: Acceptable uncertainty of test system for test cases defined in TS 38.521-4 for radiative testing..... | 261 | +| D.1 Uncertainty budget calculation principle..... | 266 | +| D.1.1 Uncertainty budget calculation principle for DNF..... | 266 | +| D.1.2 Uncertainty budget calculation principle for DFF..... | 266 | +| D.1.3 Uncertainty budget calculation principle for IFF..... | 266 | +| D.2 Measurement error contribution descriptions..... | 266 | +| D.2.1 Measurement error contribution descriptions for DNF..... | 266 | +| D.2.1.1 gNB emulator SNR uncertainty..... | 266 | +| D.2.1.2 gNB emulator Downlink EVM..... | 266 | +| D.2.1.3 gNB emulator fading model impairments..... | 267 | +| D.2.2 Measurement error contribution descriptions for DFF..... | 267 | +| D.2.2.1 gNB emulator SNR uncertainty..... | 267 | +| D.2.2.2 gNB emulator Downlink EVM..... | 267 | +| D.2.2.3 gNB emulator fading model impairments..... | 267 | +| D.2.3 Measurement error contribution descriptions for IFF..... | 267 | +| D.2.3.1 gNB emulator SNR uncertainty..... | 267 | +| D.2.3.2 gNB emulator Downlink EVM..... | 267 | +| D.2.3.3 gNB emulator fading model impairments..... | 267 | + +| | | | +|---------|----------------------------------------------------------------------------------------------|-----| +| D.3 | Assessment of testable DL SNR range and accuracy..... | 267 | +| D.3.1 | Method and Parameters..... | 267 | +| D.3.2.1 | SNR range for $\text{SNR}_{\text{RP}} - \text{SNR}_{\text{BB}} \leq 1\text{dB}$ for DFF..... | 268 | +| D.3.2.2 | SNR range for $\text{SNR}_{\text{RP}} - \text{SNR}_{\text{BB}} \leq 1\text{dB}$ for IFF..... | 268 | +| D.4 | Simulation results..... | 272 | + +# **Annex E: Acceptable uncertainty of test system for test cases defined in TS 38.533 for radiative testing..... 275** + +| | | | +|---------|-------------------------------------------------------------------------------------------|-----| +| E.1 | Uncertainty budget calculation principle..... | 275 | +| E.1.1 | Uncertainty budget calculation principle for DFF..... | 275 | +| E.1.2 | Uncertainty budget calculation principle for IFF..... | 276 | +| E.2 | Measurement error contribution descriptions..... | 276 | +| E.2.1 | Measurement error contribution descriptions for DFF..... | 276 | +| E.2.1.1 | gNB emulator SNR uncertainty..... | 276 | +| E.2.1.2 | gNB emulator Downlink EVM..... | 276 | +| E.2.1.3 | gNB emulator fading model impairments..... | 276 | +| E.2.2 | Measurement error contribution descriptions for IFF..... | 276 | +| E.2.2.1 | gNB emulator SNR uncertainty..... | 276 | +| E.2.2.2 | gNB emulator Downlink EVM..... | 276 | +| E.2.2.3 | gNB emulator fading model impairments..... | 276 | +| E.3 | Uncertainty assessment for RRM MU quantities..... | 277 | +| E.3.1 | Uncertainty assessment for DL AWGN absolute power or wanted DL signal absolute power..... | 277 | +| E.3.1.1 | Uncertainty budget format and assessment for DFF test setup..... | 277 | +| E.3.1.2 | Uncertainty budget format and assessment for Simplified DFF test setup..... | 280 | +| E.3.1.3 | Uncertainty budget format and assessment for IFF test setup..... | 280 | +| E.3.1.4 | Uncertainty budget format and assessment for Enhanced IFF test setup..... | 283 | +| E.3.1.5 | Uncertainty budget format and assessment for IFF+DFF Hybrid test setup..... | 286 | +| E.3.2 | Uncertainty assessment for DL applied SNR..... | 286 | +| E.3.3 | Uncertainty assessment for DL Fading profile uncertainty..... | 286 | +| E.3.4 | Uncertainty assessment for DL AWGN and signal flatness..... | 286 | + +E.3.5 Uncertainty assessment for UL absolute power measurement.....286 + +E.3.5.1 Uncertainty budget format and assessment for DFF.....286 + +E.3.5.2 TBD.....289 + +E.3.5.3 Uncertainty budget format and assessment for IFF.....289 + +E.3.5.4 Uncertainty budget format and assessment for Enhanced IFF test setup.....291 + +E.3.5.5 Uncertainty budget format and assessment for IFF+DFF Hybrid test setup.....293 + +E.3.6 Uncertainty assessment for UL relative power measurement.....293 + +E.3.7 Uncertainty assessment for UL signal transmit timing relative to DL.....293 + +E.3.8 Uncertainty assessment for Relative transmit timing accuracy during UE timing adjustment.....293 + +**Annex F: Applicable MTSU for Different QZ/Device Sizes.....293** + +**Annex G: Acceptable uncertainty of test system for test cases defined in TS 37.571-1 for radiative testing.....295** + +**Annex H: Change history .....296** + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +FFS + +# --- 1 Scope + +The present document specifies a general method used to derive Measurement Uncertainties and Test Tolerances for UE conformance tests. The acceptable uncertainties for each test case are documented and establish a system for relating the Test Tolerances to the measurement uncertainties of the Test System. + +For UE radio transmitting and reception tests, only FR2 is considered in this document. For UE RRM and Demodulation tests, both FR1 and FR2 are considered in this document. + +The test cases which have been analysed to determine Test Tolerances are included as .zip files. + +The present document is applicable from Release 15 up to the release indicated on the front page of the present Terminal conformance specifications. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 36.903: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test tolerances for Radio Resource Management (RRM) conformance tests". +- [3] 3GPP TS 36.904: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test tolerances for User Equipment (UE) radio reception conformance tests". +- [4] ETSI ETR 273-1-2: "Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [5] 3GPP TS 36.521-1: "User Equipment (UE) conformance specification, Radio transmission and reception Part 1: conformance testing". +- [6] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone". +- [7] 3GPP TS 38.521-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". +- [8] 3GPP TS 38.521-3: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: NR interworking between NR range1 + NR range2; and between NR and LTE". + +- [9] 3GPP TS 38.521-4: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 4: Performance requirements". +- [10] 3GPP TS 38.533: "NR; User Equipment (UE) conformance specification; Radio Resource Management (RRM)". +- [11] ETSI TR 102 273-1-1 V1.2.1 (2001-12): "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 1: Introduction". +- [12] 3GPP TR 25.914: "Measurement of Radio Performances for UMTS terminals in speech mode". +- [13] 3GPP TR 38.810: "Study on test methods for New Radio". +- [14] CTIA OTA Test Plan version 3.7, . +- [15] 3GPP TS 36.521-3: "User Equipment (UE) conformance specification, Radio transmission and reception Part 3: Radio Resource Management (RRM) conformance testing." +- [16] 3GPP TS 38.101-2: "User Equipment (UE) radio transmission and reception Part 2: Range 2 Standalone" +- [17] 3GPP TS 38.133: "Requirements for support of radio resource management" +- [18] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment" +- [19] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements" +- [20] 3GPP TS 37.571-1: User Equipment (UE) conformance specification for UE positioning; Part 1: Conformance test specification. + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---|------------------------| +| D | DUT radiating aperture | +|---|------------------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-----|---------------------------------| +| AoA | Angle of Arrival | +| DFF | Direct Far Field | +| EIS | Effective Isotropic Sensitivity | + +| | | +|------|----------------------------------------------------| +| EIRP | Effective (or equivalent) isotropic radiated power | +| FF | Far Field | +| FR1 | Frequency Range 1 | +| FR2 | Frequency Range 2 | +| FWA | Fixed Wireless Access | +| IFF | Indirect Far Field | +| MBW | Maximum Bandwidth | +| MU | Measurement Uncertainty | +| NFTF | Near Field To Far-field | +| NR | New Radio | +| SNR | Signal-to-Noise Ratio | +| TRP | Total Radiated Power | +| TT | Test Tolerance | + +# 4 General Principles + +## 4.1 Principle of Superposition + +For multi-cell tests there are several cells each generating various Physical channels. In general cells are combined along with AWGN, so the signal and noise seen by the UE may be determined by more than one cell. + +Since several cells may contribute towards the overall power applied to the UE, a number of test system uncertainties affect the signal and noise seen by the UE. The aim of the superposition method is to vary each controllable parameter of the test system separately, and to establish its effect on the critical parameters as seen by the UE receiver. The superposition principle then allows the effect of each test system uncertainty to be added, to calculate the overall effect. + +The contributing test system uncertainties shall form a minimum set for the superposition principle to be applicable. + +## 4.2 Sensitivity analysis + +A change in any one channel level or channel ratio generated at source does not necessarily have a 1:1 effect at the UE. The effect of each controllable parameter of the test system on the critical parameters as seen by the UE receiver shall therefore be established. As a consequence of the sensitivity scaling factors not necessarily being unity, the test system uncertainties cannot be directly applied as test tolerances to the critical parameters as seen by the UE. + +**EXAMPLE:** In many of the tests described, the $\hat{E}_s / I_{ot}$ is one of the critical parameters at the UE. Scaling factors are used to model the sensitivity of the $\hat{E}_s / I_{ot}$ to each test system uncertainty. When the scaling factors have been determined, the superposition principle then allows the effect of each test system uncertainty to be added, to give the overall variability in the critical parameters as seen at the UE. + +There are often constraints on several parameters at the UE. The aim of the sensitivity analysis, together with the acceptable test system uncertainties, is to ensure that the variability in each of these parameters is controlled within the limits necessary for the specification to apply. The test has then been conducted under valid conditions. + +## 4.3 Statistical combination of uncertainties + +The acceptable uncertainties of the test system are specified as the measurement uncertainty tolerance interval for a specific measurement that contains 95 % of the performance of a population of test equipment. In the RRM and UE radio transmission and reception conformance tests covered by the present document, the Test System shall enable the stimulus signals in the test case to be adjusted to within the specified range, with an uncertainty not exceeding the specified values. + +The method given in the present document combines the acceptable uncertainties of the test system, to give the overall variability in the critical parameters as seen at the UE. Since the process does not add any new uncertainties, the method of combination should be chosen to maintain the same tolerance interval for the combined uncertainty as is already specified for the contributing test system uncertainties. + +The basic principle for combining uncertainties is in accordance with ETR 273-1-2 [4]. In summary, the process requires 3 steps: + +- a) Express the value of each contributing uncertainty as a one standard deviation figure, from knowledge of its numeric value and its distribution. +- b) Combine all the one standard deviation figures as root-sum-squares, to give the one standard deviation value for the combined uncertainty. +- c) Expand the combined uncertainty by a coverage factor, according to the tolerance interval required. + +Provided that the contributing uncertainties have already been obtained using this method, using a coverage factor of 2, further stages of combination can be achieved by performing step b) alone, since steps a) and c) simply divide by 2 and multiply by 2 respectively. + +The root-sum-squares method is therefore used to maintain the same tolerance interval for the combined uncertainty as is already specified for the contributing test system uncertainties. In some cases where correlation between contributing uncertainties has an adverse effect, the method is modified in accordance with clause 4.4.5 of the present document. + +In each analysis, the uncertainties are assumed to be uncorrelated, and are added result root-sum-square unless otherwise stated. + +The combination of uncertainties is performed using dB values for simplicity. It has been shown that using dB uncertainty values gives a slightly worse combined uncertainty result than using linear values for the uncertainties. The analysis method therefore errs on the safe side. + +## 4.4 Correlation between uncertainties + +The statistical (root-sum-square) addition of uncertainties is based on the assumption that the uncertainties are independent of each other. For realisable test systems, the uncertainties may not be fully independent. The validity of the method used to add uncertainties depends on both the type of correlation and on the way in which the uncertainties affect the test requirements. + +Clauses 4.4.1 to 4.4.3 give examples to illustrate different types of correlation. + +Clauses 4.4.4 to 4.4.7 show how the scenarios applicable to multi-cell RRM tests are treated. + +### 4.4.1 Uncorrelated uncertainties + +The graph shows an example of two test system uncertainties, A and B, which affect a test requirement. Each sample from a population of test systems has a specific value of error in parameter A, and a specific value of error in parameter B. Each dot on the graph represents a sample from a population of test systems, and is plotted according to its error values for parameters A and B. + +![Scatter plot showing uncorrelated errors in parameters A and B.](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg) + +A scatter plot illustrating the relationship between errors in two parameters, A and B. The horizontal axis is labeled "Error in parameter A" and the vertical axis is labeled "Error in parameter B". The plot shows a cloud of points that are roughly circularly distributed around the origin, indicating that the errors in parameter A and parameter B are uncorrelated. The points are spread out in all directions from the center, with no discernible linear trend. + +Scatter plot showing uncorrelated errors in parameters A and B. + +**Figure 4.4.1-1: Example of two test system uncertainties affecting a test requirement** + +It can be seen that a positive value of error in parameter A, for example, is equally likely to occur with either a positive or a negative value of error in parameter B. This is expected when two parameters are uncorrelated, such as two uncertainties which arise from different and unrelated parts of the test system. + +### 4.4.2 Positively correlated uncertainties + +The graph shows an example of two test system uncertainties, A and B, which affect a test requirement. Each sample from a population of test systems has a specific value of error in parameter A, and a specific value of error in parameter B. Each dot on the graph represents a sample from a population of test systems, and is plotted according to its error values for parameters A and B. + +![Scatter plot showing positively correlated errors in parameters A and B.](58f42a91047786934d8a7e258d581ca2_img.jpg) + +A scatter plot illustrating the relationship between errors in two parameters, A and B. The horizontal axis is labeled "Error in parameter A" and the vertical axis is labeled "Error in parameter B". The plot shows a cloud of points that are roughly elliptically distributed around the origin, elongated along the line y=x, indicating that the errors in parameter A and parameter B are positively correlated. The points are more densely packed along the diagonal line where the errors in both parameters are of the same sign and magnitude. + +Scatter plot showing positively correlated errors in parameters A and B. + +**Figure 4.4.2-1: Example of two test system uncertainties affecting a test requirement** + +It can be seen that a positive value of error in parameter A, for example, is more likely to occur with a positive value of error in parameter B and less likely to occur with a negative value of error in parameter B. This can occur when the two + +uncertainties arise from similar parts of the test system, or when one component of the uncertainty affects both parameters in a similar way. + +In an extreme case, if the error in parameter A and the error in parameter B came from the same sources of uncertainty, and no others, the dots would lie on a straight line of slope +1. + +### 4.4.3 Negatively correlated uncertainties + +The graph shows an example of two test system uncertainties, A and B, which affect a test condition. Each sample from a population of test systems has a specific value of error in parameter A, and a specific value of error in parameter B. Each dot on the graph represents a sample from a population of test systems, and is plotted according to its error values for parameters A and B. + +![Scatter plot showing negatively correlated uncertainties for parameters A and B.](812b773680b611c18d49243e102b895a_img.jpg) + +A scatter plot illustrating negatively correlated uncertainties. The horizontal axis is labeled 'Error in parameter A' and the vertical axis is labeled 'Error in parameter B'. The plot shows a cluster of black dots that exhibit a negative correlation, sloping downwards from the top-left towards the bottom-right. This indicates that as the error in parameter A increases, the error in parameter B tends to decrease. + +Scatter plot showing negatively correlated uncertainties for parameters A and B. + +**Figure 4.4.3-1: Example of two test system uncertainties affecting a test condition** + +It can be seen that a positive value of error in parameter A, for example, is more likely to occur with a negative value of error in parameter B and less likely to occur with a positive value of error in parameter B. This effect can theoretically occur, and is included for completeness, but is unlikely in a practical test system. + +### 4.4.4 Treatment of uncorrelated uncertainties + +If two uncertainties are uncorrelated, they are added statistically in the analysis. Provided that each uncertainty is already expressed as an expanded uncertainty with coverage factor 2, the contributing uncertainties are added root-sum-squares to give a combined uncertainty which also has coverage factor 2, and the 95% tolerance interval is maintained. + +This is the default assumption. + +### 4.4.5 Treatment of positively correlated uncertainties with adverse effect + +If two test system uncertainties are positively correlated, and if they affect the value of a critical parameter in the same direction, the combined effect may be greater than predicted by adding the contributing uncertainties root-sum-squares. + +In this scenario the two uncertainties are added worst-case in the analysis. Provided that each uncertainty is already expressed as an expanded uncertainty with coverage factor 2, the combined uncertainty will cover a 95% tolerance interval even when the two contributing uncertainties are fully correlated. If the two contributing uncertainties are less than fully correlated, the combined uncertainty will cover a tolerance interval greater than 95%. + +## 4.4.6 Treatment of positively correlated uncertainties with beneficial effect + +If two test system uncertainties are positively correlated, and if they affect the value of a critical parameter in opposite directions, the combined effect will be less than predicted by adding the contributing uncertainties root-sum-squares. + +In this scenario the two uncertainties are added statistically in the analysis. Provided that each uncertainty is already expressed as an expanded uncertainty with coverage factor 2, the combined uncertainty will cover a 95% tolerance interval when the two contributing uncertainties are uncorrelated. If the two contributing uncertainties are positively correlated, the combined uncertainty will cover a tolerance interval greater than 95%. + +#### 4.4.7 Treatment of negatively correlated uncertainties + +Negatively correlated uncertainties are excluded by the assumptions. This has been agreed as an acceptable restriction on practical test systems, as the mechanisms which produce correlation generally arise from similarities between two parts of the test system, and therefore produce positive correlation. + +--- + +## 5 Determination of Test System Uncertainties + +### 5.1 General + +The uncertainty of a test system when making measurements reduces the ability of the test system to distinguish between conformant and non-conformant test subjects. The aim is therefore to minimise uncertainty, subject to a number of practical constraints: + +- a) A vendor's test system should be reproducible in the required quantities. +- b) A choice of test systems should be available from different vendors. +- c) The uncertainties should allow reasonable freedom of test system implementation +- d) The test system can be run automatically +- e) The test system may include several radio access technologies +- f) It should be possible to maintain calibration of deployed test systems over reasonable spans of time and environmental conditions + +In practice therefore within 3GPP the acceptable uncertainty of the test system is the smallest value that can be agreed between the test system vendors represented, consistent with the above constraints. The uncertainty will not therefore be as low as could be achieved, for example, by a national standards laboratory. + +### 5.2 Uncertainty figures + +The actual figures for the acceptable uncertainty of a test system are defined in Annex F of 38.521-1, Annex F of 38.521-2, Annex F of 38.521-3, Annex F of TS 38.521-4, Annex F of TS 38.533 and Annex C of 37.571-1. To avoid maintenance issues with figures in separate specifications, the uncertainties are not formally defined within the present document, but informative guidelines are provided in Annex B to Annex E of the present document. + +--- + +## 6 Determination of Test Tolerances + +### 6.1 General + +The general principles given in the present document are applied to each test case, according to the applicable uncertainties and requirements to obtain a correct verdict. + +The test cases which have been analysed to determine Test Tolerances are included the present document as .zip files. The name of the zip file indicates the specification and the test cases covered. + +Annex A gives the rationale for their inclusion. + +--- + +## 7 Grouping of test cases defined in TS 38.521-4 + +*Editor's note: intended to capture grouping of demodulation test cases.* + +--- + +## 8 Grouping of test cases defined in TS 38.533 + +**Table 8-1: Grouping of FR1 test cases defined in Clauses 4, 4A, 6, 8, 16 and 18 of TS 38.533** + +| Group | Test Case Numbers | .zip file name | Comments | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCell_Activation_01 | 4.5.3.1
4.5.3.2
4.5.3.3

6.5.3.1
6.5.3.2
6.5.3.3 | "38.533 4.5.3 +6.5.3 TT.zip" | "2 Inter Frequency NR Cells,
3 time periods,
Various number of sub-tests,
No fading" | +| SCell_Activation_02 | 4.5.3.5
6.5.3.4 | "38.533 4.5.3.5 +6.5.3.4 TT.zip" | "2 Inter Frequency NR Cells,
2 time periods,
Various number of sub-tests,
No fading"
Direct SCell activation configurations | +| PSCell_Activation | 4.5.10.1 | "38.533 4.5.10.1 TT.zip" | 1 NR Cell, no fading | +| PSCell_Activation | 5.5.12.1 | "38.533 5.5.12.1 TT.zip" | 1 NR Cell, no fading | +| SCell_Activation_03 | 6.5.3.5 | "38.533 6.5.3.5 TT.zip" | "3 Cells with 2 Intra frequency and 3 rd cell with Inter Frequency NR FR1 Cells,
Various number of sub-tests,
No fading"
direct SCell activation configurations | +| SCell_Activation_04 | 4.5.3.6
4.5.3.7
6.5.3.10
6.5.3.11 | "38.533 4.5.3.6+4.5.3.7 +6.5.3.10+6.5.3.11 TT.zip" | "2 Inter Frequency NR Cells,
2 time periods,
Various number of sub-tests,
No fading"
Fast SCell activation configurations | +| FastSCell_Activation | 7.5.3.14 | "38.533 7.5.3.14 TT.zip" | "2 Inter Frequency NR FR2 Cells,
2 time periods,
No fading" | +| Intra_Freq_Meas_01 | 4.6.1.1
4.6.1.2
4.6.1.3
4.6.1.4
4.6.1.5
4.6.1.6
4.6.1.7

6.6.1.1
6.6.1.2
6.6.1.3
6.6.1.4
6.6.1.5
6.6.1.6
6.6.1.7
6.6.19.1
16.6.1.2
16.6.1.4
16.6.1.6 | "38.533 4.6.1.1+4.6.1.2+4.6.1.3+4.6.1.4 TT v5.zip" | "2 Intra Frequency NR Cells,
2 time periods,
Various number of sub-tests,
No fading"
Note: The spreadsheet "16.6.1.4-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | + +| | | | | +|--|------------------------------------------------|--|--| +| | 16.6.1.8
16.6.1.10
16.6.1.12
16.6.7.2 | | | +|--|------------------------------------------------|--|--| + +| | | | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Intra_Freq_MG_Enh | 6.6.17.1
6.6.17.2 | "38.533 6.6.17.1+6.6.17.2 TT.zip" | "2 Intra Frequency NR Cells,
3 time periods,
Various number of sub-tests,
No fading" | +| Intra_Freq_Meas_RedCap_1Rx_01 | 16.6.1.1
16.6.1.3
16.6.1.5
16.6.1.7
16.6.1.9
16.6.1.11
16.6.7.1 | "38.533
16.6.1.1+16.6.1.3+16.6.1.5+16.6.1.7
TT.zip" | "2 Intra Frequency NR Cells,
2 time periods,
Various number of sub-tests,
No fading" | +| Intra_Freq_HST_Meas_01 | 4.6.1.8
6.6.1.8
6.6.19.4 | "38.533 4.6.1.8+6.6.1.8 TT" | "3 NR cells on 2 channels (2 Intra Frequency NR Cells),
2 time periods,
Various number of sub-tests,
No fading" | +| Inter_Freq_Meas_01 | 4.6.2.1
4.6.2.2
4.6.2.5
4.6.2.6
4.6.2.9

6.6.2.1
6.6.2.2
6.6.2.5
6.6.2.6
6.6.2.12
6.6.19.2
16.6.2.2
16.6.2.4
16.6.2.6
16.6.2.8
16.6.2.10
16.6.2.12 | "4.6.2.1+4.6.2.2+4.6.2.5+4.6.2.6 TT v4.zip" | "2 Inter Frequency NR Cells,
2 time periods,
Various number of sub-tests,
No fading"

Note: The spreadsheet "16.6.2.2-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations | +| Inter_Freq_MG_Enh | 6.6.18.1
6.6.18.2 | "6.6.18.1+6.6.18.2 TT.zip" | "3 Inter Frequency NR Cells,
2 time periods,
Various number of sub-tests,
No fading" | +| Intra_Reselection_01 | 6.1.1.1
16.1.1.2 | 38.533 6.1.1.1 + 16.1.1.2 TT | "2 Intra Frequency NR Cells,
3 time periods,
No fading"
The spreadsheet "16.1.1.2-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| Inter_Reselection_01 | 6.1.1.2
6.1.1.8
16.1.1.4 | 38.533 6.1.1.2 + 16.1.1.4 TT | "2 Inter Frequency NR Cells,
3 time periods,
No fading" | + +| | | | | +|--|--|--|------------------------------------------------------------------------------------------------| +| | | | The spreadsheet "16.1.1.4-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +|--|--|--|------------------------------------------------------------------------------------------------| + +| | | | | +|--------------------------------------|-------------------------------------------------------|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InterRAT_Higher_Reselection_01 | 6.1.2.1
16.1.2.2 | 38.533 6.1.2.1+16.1.2.2 | “1 E-UTRAN Cell,
1 NR Cells,
3 time periods,
No fading”
The spreadsheet
“16.1.2.2-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| InterRAT_Lower_Reselection_01 | 6.1.2.2
6.1.2.3
6.1.2.5
16.1.2.4
16.1.2.6 | 38.533
6.1.2.2+6.1.2.3+6.1.2.5+16.1.2.4 | “1 E-UTRAN Cell,
1 NR Cells,
2 time periods,
No fading”
The spreadsheet
“16.1.2.4-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| InterRAT_Lower_Reselection_02 | 6.1.2.4 | “38.533 6.1.2.4 TT.zip” | “1 E-UTRAN Cell,
1 NR Cells,
2 time periods,
No fading” | +| InterRAT_Known_Handover_01_
1Rx | 16.3.1.7 | ”38.533 16.3.1.7 TT.zip” | “1 E-UTRAN Cell,
1 NR Cells,
3 time periods,
No fading” | +| InterRAT_Known_Handover_01 | 6.3.1.4
16.3.1.8 | ”38.533 6.3.1.4+16.3.1.8 TT.zip” | “1 E-UTRAN Cell,
1 NR Cells,
3 time periods,
No fading”
Note: The
spreadsheet
“16.3.1.8-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| InterRAT_Unknown_Handover_0
1_1Rx | 16.3.1.9 | ”38.533 16.3.1.9 TT.zip” | “1 E-UTRAN Cell,
1 NR Cells,
2 time periods,
No fading” | +| InterRAT_Unknown_Handover_0
1 | 6.3.1.5
16.3.1.10 | “38.533 6.3.1.5+16.3.1.10 TT.zip” | “1 E-UTRAN Cell,
1 NR Cells,
2 time periods,
No fading”
Note: The
spreadsheet
“16.3.1.10-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| Intra_RRC_re-establishment_01 | 6.3.2.1.1
16.3.2.1.1
16.3.2.1.2 | “38.533
6.3.2.1.1+16.3.2.1.1+16.3.2.1.2
TT.zip” | “2 Intra Frequency
NR Cells,
3 time periods,
No fading”
Note: The | + +| | | | | +|--|--|--|-------------------------------------------------------------------------------------------------------------| +| | | | spreadsheet
"16.3.2.1.2-3" only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +|--|--|--|-------------------------------------------------------------------------------------------------------------| + +| | | | | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Intra_SS-RSRP_Abs_Acc_01 | 4.7.1.1.1
6.7.1.1.1 | "38.533 4.7.1.1.1+6.7.1.1.1 TT v2.zip" | "2 Intra-Frequency NR Cells, 3 Sub-tests, periodic reporting, No fading" | +| Intra_SS-RSRP_Rel_Acc_01 | 4.7.1.1.2
6.7.1.1.2 | "38.533 4.7.1.1.2+6.7.1.1.2 TT v2.zip" | "2 Intra-Frequency NR Cells, 3 Sub-tests, periodic reporting, No fading" | +| Inter_RRC_re-establishment_01 | 6.3.2.1.2
16.3.2.1.3
16.3.2.1.4 | "38.533
6.3.2.1.2+16.3.2.1.3+16.3.2.1.4
TT.zip" | "2 Inter Frequency NR Cells, 3 time periods, No fading"
Note: The spreadsheet "16.3.2.1.4-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| Inter_RRC_redirection_01 | 6.3.2.3.1
16.3.2.3.1
16.3.2.3.2
18.2.2.1 | "38.533
6.3.2.3.1+16.3.2.3.1+16.3.2.3.2+18.2.2.1 TT.zip" | "2 Inter Frequency NR Cells, 2 time periods, No fading"
Note: The spreadsheet "16.3.2.3.2-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| InterRAT_RRC_redirection_01 | 6.3.2.3.2
16.3.2.3.3
16.3.2.3.4 | "38.533
6.3.2.3.2+16.3.2.3.3+16.3.2.3.4
TT.zip" | "1 E-UTRAN Cell, 1 NR Cells, 2 time periods, No fading"
Note: The spreadsheet "16.3.2.3.4-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| RLM_InSync_01 | 4.5.1.2
4.5.1.4
6.5.1.2
6.5.1.4

4.5.1.6
4.5.1.8
6.5.1.6
6.5.1.8

16.5.1.3
16.5.1.4
16.5.1.7
16.5.1.8
16.5.1.11
16.5.1.12 | "38.533
4.5.1.2+4.5.1.4+6.5.1.2+6.5.1.4 TT v4.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), 1 sub-test, Fading, 5 Time Periods"
Note: The spreadsheet "16.5.1.4-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | + +| | | | | +|--|------------------------|--|--| +| | 16.5.1.15
16.5.1.16 | | | +|--|------------------------|--|--| + +| | | | | +|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RLM_Out_of_Sync_01 | 4.5.1.1
4.5.1.3
6.5.1.1
6.5.1.3

4.5.1.5
4.5.1.7
6.5.1.5
6.5.1.7

16.5.1.1
16.5.1.2
16.5.1.5
16.5.1.6
16.5.1.9
16.5.1.10
16.5.1.13
16.5.1.14 | “38.533
4.5.1.1+4.5.1.3+6.5.1.1+6.5.1.3 TT
v5.zip” | “1 NR Cell (1 E-UTRA
Cell for NSA case), 1
sub-test, Fading, 3
Time Periods”
Note: The
spreadsheet
“16.5.1.2-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| UE_Timing_Advance_01 | 4.4.3.1
6.4.3.1
16.4.3.1
16.4.3.2 | “38.533
4.4.3.1+6.4.3.1+16.4.3.1+16.4.3.2
TT.zip” | “1 NR Cell (1 E-UTRA
Cell for NSA case),
No Fading” | +| UE_Transmit_Timing_01 | 4.4.1.1
6.4.1.1
16.4.1.1
16.4.1.2 | “38.533
4.4.1.1+6.4.1.1+16.4.1.1+16.4.1.2
TT.zip” | “1 NR Cell (1 E-UTRA
Cell for NSA case), 2
sub-tests, No Fading” | +| RRC_reconfiguration_delay_01 | 4.5.4.1
6.5.4.1 | “38.533 4.5.4.1+6.5.1.1 TT.zip” | “1 E-UTRA Cell, 2 NR
Cells”, 3 Time
Periods, No Fading” | +| Intra_Freq_HO_Known_Target | 6.3.1.1
16.3.1.2 | “38.533 6.3.1.1+16.3.1.2 TT.zip” | “2 Intra-Freq NR
Cells, 3 Time Periods,
No Fading”
Note: The
spreadsheet
“16.3.1.2-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| Intra_Freq_HO_Known_Target_1
Rx_RedCap | 16.3.1.1 | “38.533 16.3.1.1 TT.zip” | “2 Intra-Freq NR
Cells, 3 Time Periods,
No Fading” | +| Intra_Freq_HO_Unknown_Target | 6.3.1.2
16.3.1.3
16.3.1.4 | “38.533 6.3.1.2+16.3.1.4 TT.zip” | “2 Intra-Freq NR
Cells, 2 Time Periods,
No Fading”
Note: The
spreadsheet
“16.3.1.4-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| Inter_Freq_HO | 6.3.1.3
16.3.1.5
16.3.1.6 | “38.533 6.3.1.3+16.3.1.6 TT.zip” | “2 Inter-Freq NR
Cells, 2 Time Periods,
No Fading”
Note: The
spreadsheet
“16.3.1.6-3” only
applies to 30kHz SCS | + +| | | | | +|--|--|--|-----------------------------------------------| +| | | | + 20MHz CBW
RedCap test
configurations. | +|--|--|--|-----------------------------------------------| + +| | | | | +|-----------------------------------|------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InterRAT_Meas_01 | 6.6.3.1
6.6.3.2
6.6.19.3 | "38.533 6.6.3.1+6.6.3.2 TT v2.zip" | "1 E-UTRAN Cell,
1 NR Cell,
2 time periods" | +| Interruption_Transition_01 | 4.5.2.1
4.5.2.2 | "38.533 4.5.2.1+4.5.2.2 TT.zip" | "1 E-UTRAN Cell,
1 NR Cells,
1 time period,
No fading" | +| Interruption_meas_NR_SCC_01 | 4.5.2.3
4.5.2.4
6.5.2.1 | "38.533 4.5.2.3+4.5.2.4+6.5.2.1 TT.zip" | "1 E-UTRAN Cell,
2 NR Cells (2 NR Cells for SA case),
1 time period,
No fading" | +| Interruption_meas_NR_SCC_01 | 4.5.2.5
4.5.2.6 | "38.533 4.5.2.5+4.5.2.6 TT.zip" | "2 E-UTRAN Cell,
1 NR Cells,
1 time period,
No fading" | +| Interruption_meas_NR_PSCell | 4.5.2.10 | "38.533 4.5.2.10 TT.zip" | "1 E-UTRAN Cell,
1 NR Cells,
1 time period,
No fading" | +| Inter_SS-RSRP_Abs_Acc_01 | 4.7.1.2.1
6.7.1.2.1 | "38.533 4.7.1.2.1+6.7.1.2.1 TT v3.zip" | "2 Inter-Frequency NR Cells,
periodic reporting,
No fading" | +| Inter_SS-RSRP_Rel_Acc_01 | 4.7.1.2.2
6.7.1.2.2 | "38.533 4.7.1.2.2+6.7.1.2.2 TT v2.zip" | "2 Inter-Frequency NR Cells,
periodic reporting,
No fading" | +| Intra_SS-SINR_Acc_01 | 4.7.3.1
6.7.3.1 | "38.533 4.7.3.1+6.7.3.1 TT.zip" | "2 Intra-Frequency NR Cells,
periodic reporting,
No fading" | +| SSB_Based_L1-RSRP-Meas | 4.6.4.1
4.6.4.2
4.6.4.5
6.6.4.1
6.6.4.2
6.6.4.5
16.6.4.2
16.6.4.4 | "38.533 4.6.4.1+4.6.4.2+6.6.4.1+6.6.4.2 TT v4.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), 2 time periods, No fading"
Note: The spreadsheet "16.6.4.2-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| SSB_Based_L1-RSRP-Meas_RedCap_1Rx | 16.6.4.1
16.6.4.3 | "38.533 16.6.4.1+16.6.4.3 TT.zip" | "1 NR Cell, 2 time periods, No fading" | +| CSI-RS_Based_L1-RSRP-Meas | 4.6.4.3
4.6.4.4
6.6.4.3
6.6.4.4
16.6.4.5
16.6.4.6
16.6.4.7
16.6.4.8 | "38.533 4.6.4.3+4.6.4.4+6.6.4.3+6.6.4.4 TT v5.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading"
Note: The spreadsheet "16.6.4.6-3" only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| CSI-RS_WithoutIMR_L1-SINR-Meas | 4.6.7.1
6.6.8.1 | "38.533 4.6.7.1+6.6.8.1 TT.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading" | + +| | | | | +|--|--|--|---------| +| | | | fading" | +|--|--|--|---------| + +| | | | | +|----------------------------------|------------------------|----------------------------------------|----------------------------------------------------------------------------------| +| SSB_WithCSI-IM_L1-SINR-Meas | 4.6.7.2
7.6.3.6 | “38.533 4.6.7.2 TT.zip” | “1 E-UTRA Cell, 1 NR Cell, 2 time periods, No fading” | +| CSI-RS_WithCSI-IM_L1-SINR-Meas | 4.7.7.3.1
6.7.9.3.1 | “38.533 4.7.7.3.1+6.7.9.3.1 TT.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading” | +| CSI-RS_WithCSI-IM_L1-SINR-Meas | 4.7.7.3.2
6.7.9.3.2 | “38.533 4.7.7.3.2+6.7.9.3.2 TT.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading” | +| CSI-RS_Based_L1-SINR-Meas | 4.7.7.1.1
6.7.7.9.1 | “38.533 4.7.7.1.1+6.7.9.1.1 TT.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading” | +| L1-SINR_Accuracy_3 | 7.7.6.2 | “38.533 7.7.6.2 TT.zip” | 1 NR FR2 Cell, 2 SSB and 2 CSI-RS, 1 subtests, 1 AoA in Rx peak and rough beam | +| L1-SINR_Accuracy_4 | 7.7.6.3 | “38.533 7.7.6.3 TT.zip” | 1 NR FR2 Cell, 2 CSI-RS and 2 CSI-IM, 1 subtest, 1 AoA in Rx peak and rough beam | +| CSI-RS_WithNZP_L1-SINR-Meas | 4.6.7.3 | “38.533 4.6.7.3 TT.zip” | “1 E-UTRA Cell, 1 NR Cell, one time period, No fading” | +| Intra_SS-RSRQ_Acc_01 | 4.7.2.1
6.7.2.1 | “38.533 4.7.2.1+6.7.2.1 TT v2.zip” | “2 Intra-Frequency NR Cells, periodic reporting, No fading” | +| Inter_SS-RSRQ_Abs_Acc_01 | 4.7.2.2.1
6.7.2.2.1 | “38.533 4.7.2.2.1+6.7.2.2.1 TT v2.zip” | “2 Inter-Frequency NR Cells, periodic reporting, No fading” | +| Inter_SS-RSRQ_Rel_Acc_01 | 4.7.2.2.2
6.7.2.2.2 | “38.533 4.7.2.2.2+6.7.2.2.2 TT v2.zip” | “2 Inter-Frequency NR Cells, periodic reporting, No fading” | +| Inter_SS-SINR_Abs_Acc_01 | 4.7.3.2.1
6.7.3.2.1 | “38.533 4.7.3.2.1+6.7.3.2.1 TT.zip” | “2 Inter-Frequency NR Cells, periodic reporting, No fading” | +| Inter_SS-SINR_Rel_Acc_01 | 4.7.3.2.2
6.7.3.2.2 | “38.533 4.7.3.2.2+6.7.3.2.2 TT.zip” | “2 Inter-Frequency NR Cells, periodic reporting, No fading” | +| Inter_RAT_SS-RSRP_LTE_Serving_01 | 8.5.2.1.1.1 | “38.533 8.5.2.1.1.1 TT.zip” | 1 NR Cell, 1 LTE serving cell, periodic SS-RSRP reporting, No fading | +| Inter_RAT_SS-RSRQ_LTE_Serving_01 | 8.5.2.2.1 | “38.533 8.5.2.2.1 TT.zip” | 1 NR Cell, 1 LTE serving cell, periodic SS-RSRQ reporting, No fading | +| Inter_RAT_SS-SINR_LTE_Serving_01 | 8.5.2.3.1 | “38.533 8.5.2.3.1 TT.zip” | 1 NR Cell, 1 LTE serving cell, periodic SS-SINR reporting, No fading | + +| | | | | +|--------------------------------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| L1-RSRP_Abs_Acc_01 | 4.7.4.1.1
6.7.4.1.1
4.7.4.2.1
6.7.4.2.1 | “38.533
4.7.4.1.1+4.7.4.2.1+6.7.4.1.1+6.7.4.2.1
1 TT.zip” | 1 NR Cell, periodic L1-RSRP reporting, No fading | +| L1-RSRP_Rel_Acc_01 | 4.7.4.1.2
6.7.4.1.2
4.7.4.2.2
6.7.4.2.2 | “38.533
4.7.4.1.2+4.7.4.2.2+6.7.4.1.2+6.7.4.2.2
2 TT v2.zip” | 1 NR Cell with 2 Beams, periodic L1-RSRP reporting, No fading | +| SSB_Based_BFR | 4.5.5.1
4.5.5.2
6.5.5.1
6.5.5.2
16.5.2.2
16.5.2.4 | “38.533
4.5.5.1+4.5.5.2+6.5.5.1+6.5.5.2 TT v4.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading”
Note: The spreadsheet “16.5.2.2-3” only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| TRP specific SSB_Based_BFR | 4.5.5.7 | 38.533 4.5.5.7 TT.zip | 1 NR Cell 1 E-UTRA Cell PCell, 5 time periods, Fading” | +| SSB_Based_BFR_RedCap_1Rx_01 | 16.5.2.116
.5.2.3 | “38.533 16.5.2.3 TT.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading” | +| CSI-RS_Based_BFR | 4.5.5.3
4.5.5.4
6.5.5.3
6.5.5.4
16.5.2.5
16.5.2.6
16.5.2.7
16.5.2.8 | “38.533
4.5.5.3+4.5.5.4+6.5.5.3+6.5.5.4 TT v3.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading”
Note: The spreadsheet “16.5.2.6-3” only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| TRP specific CSI-RS_Based_BFR | 6.5.5.7 | “38.533 6.5.5.7 TT.zip” | “1 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading” | +| CSI-RS_Based_BFD_SSB_Based_FR | 4.5.5.5
4.5.5.6
6.5.5.5
6.5.5.6 | For SSB refer to “38.533 4.5.5.1+4.5.5.2+6.5.5.1+6.5.5.2 TT v2.zip”
For CSI-RS refer to “38.533 4.5.5.3+4.5.5.4+6.5.5.3+6.5.5.4 TT v2.zip” | “2 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading” | +| TRP specific CSI-RS_Based_BFD_SSB_Based_FR | 4.5.5.8 | 38.533 4.5.5.8 TT.zip | “2 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading” | +| DCI_Based_BWP_Switch | 4.5.6.1.1
4.5.6.1.2
6.5.6.1.1
6.5.6.1.2
16.5.3.1.1
16.5.3.1.2 | “38.533
4.5.6.1.1+4.5.6.1.2+6.5.6.1.1+6.5.6.1.2
2 TT v2.zip” | “1 NR Cell (2NR Cells for Scell case, 1 E-UTRA Cell for NSA case), 3 time periods, No fading” | +| RRC_Based_BWP_Switch | 4.5.6.2.1 | “38.533 | “1 NR Cell (1 E-UTRA | + +| | | | | +|--|---------------------------------------|-------------------------------------------------------|------------------------------------------------------| +| | 6.5.6.2.1
16.5.3.2.1
16.5.3.2.2 | 4.5.6.2.1+6.5.6.2.1+16.5.3.2.1+16.5.3
.2.2 TT.zip" | Cell for NSA case),
3 time periods,
No fading" | +|--|---------------------------------------|-------------------------------------------------------|------------------------------------------------------| + +| | | | | +|---------------------------------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Intra_RRC_re-establishment_without_timing | 6.3.2.1.3
16.3.2.1.5
16.3.2.1.6 | “38.533
6.3.2.1.3+16.3.2.1.5+16.3.2.1.6
TT.zip” | “2 Intra Frequency
NR Cells,
3 time periods,
No fading”
Note: The
spreadsheet
“16.3.2.1.6-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| InterRAT_re-selection_LTE_Serving | 8.2.1.1 | “38.533 8.2.1.1 TT.zip” | “1 NR Cell, 1 LTE
serving cell,
3 time periods
No fading” | +| InterRAT_HO_LTE_Serving | 8.3.1.1
18.2.1.1 | “38.533 8.3.1.1+18.2.1.1 TT.zip” | “1 NR Cell, 1 LTE
serving cell,
3 time periods
No fading”
Note: The
spreadsheet
“18.2.1.1-3” only
applies to 30kHz SCS
+ 20MHz CBW
RedCap test
configurations. | +| InterRAT_SFTD_Meas_LTE_Serving | 8.4.1.1
8.4.1.2 | “38.533 8.4.1.1+8.4.1.2 TT.zip” | “1 NR Cell, 1 LTE
serving cell,
1 time period
No fading” | +| InterRAT_Meas_LTE_Serving | 8.4.2.1
8.4.2.2
8.4.2.3
8.4.2.4
18.3.1.1
18.3.1.2
18.3.1.3
18.3.1.4 | “38.533
8.4.2.1+8.4.2.2+8.4.2.3+8.4.2.4 TT
v3.zip” | “1 NR Cell, 1 LTE
serving cell,
2 time periods,
No Fading” | +| PSCell_Addition | 4.5.7.1 | “38.533 4.5.7.1 TT.zip” | 1 NR Cell, no fading | +| PSCell_Addition_01 | 4.5.11.1 | “38.533 4.5.11.1 TT.zip” | 1 NR Cell, no fading | +| SFTD_Accuracy | 4.7.5.1 | “38.533 4.7.5.1 TT.zip” | 1 E-UTRA Cell, 1 NR
Cell, no fading | +| SSB_WithNZP-IMR_L1-SINR-Meas | 6.6.8.2 | “38.533 6.6.8.2 TT.zip” | “1 NR Cell, 2 time
periods, No fading” | +| CSI-RS_WithCSI-IM_L1-SINR-Meas | 6.6.8.3 | “38.533 6.6.8.3 TT.zip” | “1 NR Cell, one time
period, No fading” | +| RLM_Out_of_Sync_PowerSaving
Enh | 4.5.1.9
6.5.1.9 | 38.533 4.5.1.9+6.5.1.9 TT.zip | 1 NR Cell (1 E-UTRA
Cell for NSA case), 1
sub-test, Fading, 3
Time Periods | +| iRAT_E-UTRA_RSRP_Accuracy | 6.7.5.1 | “38.533 6.7.5.1 TT.zip” | 1 E-UTRA Cell, 1 NR
Cell, no fading | +| iRAT_E-UTRA_RSRQ_Accuracy | 6.7.6.1 | “38.533 6.7.6.1 TT.zip” | 1 E-UTRA Cell, 1 NR
Cell, no fading | +| iRAT_E-UTRA_RS-SINR_Accuracy | 6.7.7.1 | “38.533 6.7.7.1 TT.zip” | 1 E-UTRA Cell, 1 NR
Cell, no fading | +| InterRAT_SFTD_Meas_Accuracy
_LTE_Serving | 8.5.1.1 | “38.533 8.5.1.1 TT.zip” | 1 E-UTRA Cell, 1 NR
Cell, no fading | +| Inter_Freq_HO_DAPS | 6.3.1.9 | “38.533 6.3.1.9+6.3.1.10 TT.zip” | “2 Inter-Freq NR | + +| | | | | +|--|----------|--|--------------------------------------| +| | 6.3.1.10 | | Cells, 5 Time Periods,
No Fading” | +|--|----------|--|--------------------------------------| + +| | | | | +|---------------------------------------|----------------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DL_Interruption_UL_Switching | 4.5.8.1 | "38.533 4.5.8.1 TT.zip" | 1 E-UTRA Cell, 1 NR Cell, no fading | +| Intra_Reselection_Low_Mobility | 6.1.1.3
16.1.1.6 | 38.533 6.1.1.3+16.1.1.6 TT | "2 Intra Frequency NR Cells,
2 time periods,
No fading"
The spreadsheet "16.1.1.6-3" only applies to 30kHz SCS + 20MHz CBW
RedCap test configurations. | +| Intra_Reselection_Not_cell_edge | 6.1.1.4 | "38.533 6.1.1.4 TT.zip" | "2 Intra Frequency NR Cells,
2 time periods,
No fading" | +| Inter_Reselection_Low_mobility | 6.1.1.5
16.1.1.8 | 38.533 6.1.1.5+16.1.1.8 TT | "2 Inter Frequency NR Cells,
2 time periods,
No fading"
The spreadsheet "16.1.1.8-3" only applies to 30kHz SCS + 20MHz CBW
RedCap test configurations. | +| Inter_Reselection_Not_cell_edge | 6.1.1.6 | "38.533 6.1.1.6 TT.zip" | "2 Inter Frequency NR Cells,
2 time periods,
No fading" | +| Intra_Reselection_HST | 6.1.1.7 | "38.533 6.1.1.7 TT.zip" | "2 Intra Frequency NR Cells,
3 time periods,
No fading" | +| InterRAT_HO_UTRA_FDD | 6.3.1.6 | "38.533 6.3.1.6 TT.zip" | "1 UTRA Cell,
1 NR Cell,
3 time periods,
No fading" | +| InterRAT_Meas_UTRA_FDD | 6.6.5.1 | "38.533 6.6.5.1 TT.zip" | "1 UTRA Cell,
1 NR Cell,
2 time periods,
No fading" | +| InterRAT_Meas_HST | 6.6.3.3 | "38.533 6.6.3.3 TT.zip" | 1 E-UTRA Cell, 1 NR Cell, no fading | +| InterRAT_re-selection_LTE_Serving_HST | 8.2.1.2 | "38.533 8.2.1.2 TT.zip" | 1 E-UTRA Cell, 1 NR Cell, no fading | +| InterRAT_Meas_LTE_Serving_HST | 8.4.2.9 | "38.533 8.4.2.9 TT.zip" | 1 E-UTRA Cell, 1 NR Cell, no fading | +| Intra_Freq_HO_DAPS | 6.3.1.7
6.3.1.8 | "38.533 6.3.1.7+6.3.1.8 TT.zip" | "2 Intra-Freq NR Cells,
5 Time Periods,
No Fading" | +| Inter_Freq_HO_DAPS | 6.3.1.9
6.3.1.10 | "38.533 6.3.1.9+6.3.1.10 TT.zip" | "2 Inter-Freq NR Cells,
5 Time Periods,
No Fading" | +| Inter_Freq_HO_DAPS | 6.3.1.11
6.3.1.12 | "38.533 6.3.1.11+6.3.1.12 TT.zip" | "2 Inter-band Inter-Freq NR Cells,
5 Time Periods,
No Fading" | + +| | | | | +|--|--|--|--------------------------| +| | | | Time Periods, No Fading” | +|--|--|--|--------------------------| + +| | | | | +|-------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Intra_Freq_CHO | 6.3.3.1 | “38.533 6.3.3.1 TT.zip” | “2 Intra-Freq NR Cells, 2 Time Periods, No Fading” | +| Inter_Freq_CHO | 6.3.3.2 | “38.533 6.3.3.2 TT.zip” | “2 Inter-Freq NR Cells, 2 Time Periods, No Fading” | +| Intra_Freq_CLI_SRS-RSRP | 4.6.5.1
6.6.6.1 | “38.533 4.6.5.1+6.6.6.1 TT.zip” | “1 E-UTRA Cell (clause 4 test only), 1 NR Cell, 1 Virtual UE, 2 Time Periods, no fading” | +| Intra_Freq_CLI_RSSI | 4.6.5.2 | “38.533 4.6.5.2 TT.zip” | “1 E-UTRA Cell, 1 NR Cell, 2 Time Periods, no fading” | +| Intra_Freq_CLI_SRS-RSRP_Accuracy | 4.7.6.1
6.7.8.1 | “38.533 4.7.6.1+6.7.8.1 TT.zip” | “1 E-UTRA Cell (clause 4 test only), 1 NR Cell, 1 Virtual UE, 1 Time Period, no fading” | +| DL_Interruption_UL_Switching_S A_01 | 6.5.7.1
6.5.7.2
6.5.7A.2 | “38.533 6.5.7.1+6.5.7.2+6.5.7A.2 TT.zip” | “2 NR Cells, 1 time period, no fading” | +| DL_Interruption_UL_Switching_S A_02 | 6.5.7B.2
6.5.7C.2 | “38.533 6.5.7B.2 TT.zip” | “3 NR Cells, 1 time period, no fading” | +| DL_Interruption_UL_Switching_S A_03 | 6.5.7C.1 | “38.533 6.5.7C.1 TT.zip” | “3 NR Cells, 1 time period, no fading” | +| PRACH_01_1RX | 16.3.2.2.1
16.3.2.2.3
16.3.2.2.5
16.3.2.2.7 | “38.533 16.3.2.2.1+16.3.2.2.3+16.3.2.2.5+16.3.2.2.7 TT” | “1 NR Cell, PRACH measurements, no fading” | +| PRACH_01 | 4.3.2.2.1
4.3.2.2.2
6.3.2.2.1
6.3.2.2.2
16.3.2.2.2
16.3.2.2.4 | “38.533 4.3.2.2.1+4.3.2.2.2+6.3.2.2.1+6.3.2.2.2 v2 TT.zip” | “1 NR Cell, PRACH measurements, no fading”

Note: The spreadsheet “16.3.2.2.2-3” only applies to 30kHz SCS + 20MHz CBW RedCap test configurations. | +| PRACH_02 | 4.3.2.2.3
4.3.2.2.4
6.3.2.2.3
6.3.2.2.4
16.3.2.2.6
16.3.2.2.8 | “38.533 4.3.2.2.3+4.3.2.2.4+6.3.2.2.3+6.3.2.2.4 TT v2.zip” | “1 NR Cell, PRACH measurements, no fading”

Note: The spreadsheet “16.3.2.2.6-3” only applies to 30kHz SCS + 20MHz CBW RedCap test | + +| | | | | +|--|--|--|-----------------| +| | | | configurations. | +|--|--|--|-----------------| + +| | | | | +|-----------------------------------------------|----------------------------------|-----------------------------------------------------|------------------------------------------------------------------------| +| Idle_CADC_meas | 6.6.9.1 | "38.533 6.6.9.1 TT.zip" | "2 NR Cells, 5 time periods, no fading" | +| CBW_change | 6.5.8.1
16.5.4.1
16.5.4.2 | "38.533 6.5.8.1+16.5.4.1+16.5.4.2 TT.zip" | "1 NR Cell, 1 time period, no fading" | +| NE-DC PSCell addition | 4A.1.1.1 | "38.533 4A.1.1.1 TT.zip" | "1 E-UTRA Cell, no fading" | +| NE-DC SFTD accuracy | 4A.2.1.1 | "38.533 4A.2.1.1 TT.zip" | "1 NR Cell, 1 E-UTRA Cell, no fading" | +| InterRAT_Idle_CADC_meas | 6.6.15.1 | "38.533 6.6.15.1 TT.zip" | "1 NR Cell, 1 E-UTRA Cell, 3 time periods, no fading" | +| InterRAT_LTE_Idle_CADC_meas | 8.2.2.1 | "38.533 8.2.2.1 TT.zip" | "1 E-UTRA Cell, 1 NR Cell, 3 time periods, no fading" | +| UE_Rx_Tx_difference_PDC_01 | 6.6.20.1
6.6.21.1 | "38.533 6.6.20+6.6.21 TT.zip" | "1 NR Cell, 2 time periods, no fading" | +| Inter_Reselection_RedCap_1Rx | 16.1.1.1 | 38.533 16.1.1.1 TT | "2 Intra Frequency NR Cells, 3 time periods, No fading, 1Rx RedCap UE" | +| Inter_Reselection_RedCap_1Rx | 16.1.1.3 | 38.533 16.1.1.3 TT | "2 Inter Frequency NR Cells, 3 time periods, No fading, 1Rx RedCap UE" | +| Intra_Reselection_Low_Mobility_RedCap_1Rx | 16.1.1.5 | 38.533 16.1.1.5 TT | "2 Intra Frequency NR Cells, 2 time periods, No fading, 1Rx RedCap UE" | +| Inter_Reselection_Low_mobility_RedCap_1Rx | 16.1.1.7 | 38.533 16.1.1.7 TT | "2 Inter Frequency NR Cells, 2 time periods, No fading, 1Rx RedCap UE" | +| InterRAT_Higher_Reselection_RedCap_1Rx | 16.1.2.1 | 38.533 16.1.2.1 TT | "1 E-UTRAN Cell, 1 NR Cells, 3 time periods, No fading, 1Rx RedCap UE" | +| InterRAT_Lower_Reselection_RedCap_1Rx | 16.1.2.3 | 38.533 16.1.2.3 TT | "1 E-UTRAN Cell, 1 NR Cells, 2 time periods, No fading, 1Rx RedCap UE" | +| InterRAT_Lower_Reselection_RedCap_Relaxed_1Rx | 16.1.2.5 | 38.533 16.1.2.5 TT | "1 E-UTRAN Cell, 1 NR Cells, 2 time periods, No fading, 1Rx RedCap UE" | +| Inter_Freq_Meas_01 | 16.6.2.1
16.6.2.3
16.6.2.5 | 38.533
16.6.2.1+16.6.2.3+16.6.2.5+16.6.2.7
TT | "2 Inter Frequency NR Cells, 2 time periods," | + +| | | | | +|--------|-----------------------------------|-----------------|--------------------------------------------------------------| +| | 16.6.2.7
16.6.2.9
16.6.2.11 | | Various number of sub-tests,
No fading, 1Rx
RedCap UE" | +| CG-SDT | 6.2.1 | 38.533 6.2.1 TT | "1 NR Cell, 6 time periods, no fading" | + +**Table 8-2: Grouping of FR2 test cases defined in Clauses 5, 7, 8 and 17 of TS 38.533** + +| Group | Test Case Numbers | .zip file name | Comments | +|-----------------------------|-------------------------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| Transmit_Timing_01 | 5.4.1.1
7.4.1.1 | "38.533 5.4.1.1+7.4.1.1 TT.zip" | 1 NR FR2 cell, no fading | +| Timing_Advance_01 | 5.4.3.1
7.4.3.1 | "38.533 5.4.3.1+7.4.3.1 TT.zip" | 1 NR FR2 cell, no fading | +| iRAT_meas_LTE_Serving | 8.4.2.5
18.3.1.5 | "38.533 8.4.2.5+18.3.1.5 TT.zip" | "1 NR FR2 cell, 1 E-UTRA serving cell, 2 time periods, No fading" | +| iRAT_meas_LTE_Serving_01 | 8.4.2.6
8.4.2.7
8.4.2.8
18.3.1.6
18.3.1.7
18.3.1.8 | "38.533 8.4.2.6+8.4.2.7+8.4.2.8+18.3.1.6 TT.zip" | "1 NR FR2 cell, 1 E-UTRA serving cell, 2 time periods, No fading" | +| iRAT_SS-RSRP_01 | 8.5.2.1.2 | "38.533 8.5.2.1.2 TT.zip" | "1 NR FR2 cell, 1 E-UTRA serving cell, 2 sub-tests, No fading" | +| iRAT_SS-RSRQ_01 | 8.5.2.2.2 | "38.533 8.5.2.2.2 TT.zip" | "1 NR FR2 cell, 1 E-UTRA serving cell, 2 sub-tests, No fading" | +| iRAT_SS-SINR_01 | 8.5.2.3.2 | "38.533 8.5.2.3.2 TT.zip" | "1 NR FR2 cell, 1 E-UTRA serving cell, 2 sub-tests, No fading" | +| Interruption_Transition_01 | 5.5.2.1
5.5.2.2 | "38.533 5.5.2.1+5.5.2.2 TT.zip" | "1 E-UTRAN Cell, 1 NR FR2 Cell, 1 time period, No fading" | +| Interruption_meas_NR_SCC_01 | 5.5.2.3
5.5.2.4
7.5.2.1 | "38.533 5.5.2.3+5.5.2.4+7.5.2.1 TT.zip" | "1 E-UTRAN Cell, 2 NR Cells (2 NR Cells for SA case), 1 time period, No fading" | +| SCell_Activation_01 | 5.5.3.1
5.5.3.7 | "38.533 5.5.3.1 TT.zip" | "2 Inter Frequency NR FR2 Cells, 3 time periods, Various number of sub-tests, No fading" | +| SCell_Activation_02 | 7.5.3.3 | "38.533 7.5.3.3 TT.zip" | "2 Inter Frequency NR FR2 Cells, 3 time periods, Various number of sub-tests, No fading" | +| SCell_Activation_02 | 7.5.3.4 | "38.533 7.5.3.4 TT.zip" | "2 Inter Frequency NR FR2 Cells, 3 time periods, Various number of sub-tests, No fading" direct SCell activation configurations | +| SCell_Activation_03 | 7.5.3.5 | "38.533 7.5.3.5 TT.zip" | "3 Cells with 2 Intra frequency and 3 rd cell" | + +| | | | | +|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | with Inter Frequency
NR FR2 Cells,
3 time periods,
Various number of
sub-tests,
No fading"
direct Scell activation
with handover test
case | +|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | +|------------------------|------------------------------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| SCell_Activation_04 | 5.5.3.8
7.5.3.13 | "38.533 5.5.3.8+7.5.3.13 TT.zip" | "2 Inter Frequency NR FR2 Cells, 2 time periods, Various number of sub-tests, No fading" fast SCell activation configurations | +| Intra_Freq_Meas_01 | 5.6.1.1
5.6.1.3
7.6.1.1
7.6.1.3
17.6.1.1
17.6.1.3 | "38.533 5.6.1.1+5.6.1.3+7.6.1.1+5.6.1.3 TT_v3.zip " | 2 NR FR2 Cells (1 E-UTRA Cell for NSA case), 2 SSBs, 2 time periods, no fading, 2 AoAs, both are in EIS spherical coverage and rough beams | +| Intra_Freq_Meas_02 | 5.6.1.2
5.6.1.4
7.6.1.2
7.6.1.4
17.6.1.2
17.6.1.4 | "38.533 5.6.1.2+5.6.1.4+7.6.1.2+5.6.1.4 TT.zip " | 2 NR FR2 Cells (1 E-UTRA Cell for NSA case), 2 SSBs, 2 time periods, no fading, 1 AoA in Rx peak and rough beam | +| Inter_Freq_Meas_01 | 5.6.2.1
5.6.2.3
7.6.2.1
7.6.2.3 | "38.533 5.6.2.1+5.6.2.3+7.6.2.1+7.6.2.3 TT v2.zip" | "2 Inter Frequency NR FR2 Cells, 2 time periods, Various number of sub-tests, No fading" | +| Inter_Freq_Meas_02 | 5.6.2.5
5.6.2.7
7.6.2.5
7.6.2.7 | "38.533 5.6.2.5+5.6.2.7+7.6.2.5+7.6.2.7 TT.zip" | "2 Inter Frequency NR Cells (Cell 1 on FR1 and Cell 2 on FR2), 2 time periods, Various number of sub-tests, No fading" | +| Inter_Freq_Meas_03 | 5.6.2.6
5.6.2.8
7.6.2.6
7.6.2.8 | "38.533 5.6.2.6+5.6.2.8+7.6.2.6+7.6.2.8 TT.zip" | "2 Inter Frequency NR Cells (Cell 1 on FR1 and Cell 2 on FR2), 2 time periods, Various number of sub-tests, No fading" | +| Inter_Freq_Meas_04 | 5.6.2.2
5.6.2.4
7.6.2.2
7.6.2.4 | "38.533 5.6.2.2+5.6.2.4+7.6.2.2+7.6.2.4 TT.zip" | "2 Inter Frequency NR Cells (both on FR2), 2 time periods, Various number of sub-tests, No fading" | +| SSB_Based_L1-RSRP-Meas | 5.6.3.1
5.6.3.2
7.6.3.1
7.6.3.2
17.6.3.1
17.6.3.2 | "38.533 5.6.3.1+5.6.3.2+7.6.3.1+7.6.3.2 TT.zip" | "1 NR FR2 Cell (1 E-UTRA Cell for NSA case), 2 time periods, No fading" | +| SS-RSRP_01 | 5.7.1.1
7.7.1.1 | "38.533 5.7.1.1+7.7.1.1 TT v2.zip" | "2 Intra-Frequency NR FR2 Cells, 2 sub-tests, No fading" | + +| | | | | +|---------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| SS-RSRP_02 | 5.7.1.2
7.7.1.2 | "38.533 5.7.1.2+7.7.1.2 TT v4.zip" | "2 Inter-Frequency NR FR2 Cells, 2 sub-tests, No fading" | +| SS-RSRP_03 | 5.7.1.3
7.7.1.3 | "38.533 5.7.1.3+7.7.1.3 TT.zip" | "1 NR FR1 Cell, 1 NR FR2 Cell, 2 sub-tests, No fading" | +| SS-RSRQ_01 | 5.7.2.1
7.7.2.1 | "38.533 5.7.2.1+7.7.2.1 TT.zip" | "2 Intra-Frequency NR FR2 Cells, 2 sub-tests, No fading" | +| SS-RSRQ_02 | 5.7.2.2
7.7.2.2 | "38.533 5.7.2.2+7.7.2.2 TT.zip" | "2 Inter-Frequency NR FR2 Cells, 2 sub-tests, No fading" | +| SS-SINR_01 | 5.7.3.1
7.7.3.1 | "38.533 5.7.3.1+7.7.3.1 TT.zip" | "2 Intra-Frequency NR FR2 Cells, 2 sub-tests, No fading" | +| SS-SINR_02 | 5.7.3.2
7.7.3.2 | "38.533 5.7.3.2+7.7.3.2 TT v2.zip" | "2 Inter-Frequency NR FR2 Cells, 3 sub-tests, No fading" | +| CSI-RS_Based_L1-RSRP-Meas | 5.6.3.3
5.6.3.4
7.6.3.3
7.6.3.4
17.6.3.3
17.6.3.4 | "38.533 5.6.3.3+5.6.3.4+7.6.3.3+7.6.3.4 TT.zip" | "1 NR FR2 Cell (1 E-UTRA Cell for NSA case), 1 time period, No fading" | +| SSB_Based_BFD | 5.5.5.1
5.5.5.2
5.5.5.5
7.5.5.1
7.5.5.2
7.5.5.5
17.5.2.5 | "38.533 5.5.5.1+5.5.5.2+7.5.5.1+7.5.5.2 TT.zip " | "1 NR FR2 Cell (1 E-UTRA Cell for NSA case), 2 SSBs, 5 time periods, fading, 1AoA Rx peak, Rough beam" | +| CSI-RS Based BFD and BFR | 5.5.5.3
5.5.5.4
7.5.5.3
7.5.5.4
17.5.2.3
17.5.2.4 | "38.533 5.5.5.3+5.5.5.4+7.5.5.3+7.5.5.4 TT v2.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading" | +| CSI-RS Based SCell BFD and BFR | 5.5.5.6
5.5.5.7
7.5.5.6
7.5.5.7 | "38.533 5.5.5.3+5.5.5.4+7.5.5.3+7.5.5.4 TT v2.zip" | "2 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading" | +| TRP specific CSI-RS Based BFD and BFR | 5.5.5.8
7.5.5.9 | "38.533 5.5.5.8+7.5.5.9 TT.zip" | "2 NR Cell (1 E-UTRA Cell for NSA case), 5 time periods, Fading" | +| SSB_Based_BFD_Relaxed_Meas | 5.5.5.9 | "38.533 5.5.5.9 TT.zip " | "1 NR FR2 Cell (1 E-UTRA Cell for NSA case), 2 SSBs, 5 time periods, fading, 1AoA Rx peak, Rough beam" | +| TRP specific SSB_Based_BFD | 7.5.5.10 | "38.533 7.5.5.10 TT.zip" | "2 NR FR2 Cell, 2 SSBs, 5 time periods, fading" | +| CSI-RS_WithoutIMR_L1-SINR-Meas | 5.6.6.1
7.6.6.1 | "38.533 5.6.6.1+7.6.6.1 TT.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading" | +| CSI-RS_WithCSI-IM_L1-SINR- | 5.6.6.3 | "38.533 5.6.6.3 TT.zip" | "1 E-UTRA Cell, 1 NR | + +| | | | | +|------------------------------------|-------------------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Meas | | | Cell, one time period, No fading" | +| Inter_Reselection_low_mobility | 7.1.1.5
17.1.1.4 | "38.533 7.1.1.5 TT.zip" | "2 NR FR2 Cells, 2 SSBs, 2 time periods, 1 AoA in Rx peak and rough beam" | +| CSI-RS_RLM_Out_of_Sync_02 | 5.5.1.7
7.5.1.7 | "38.533 5.5.1.7+7.5.1.7 TT.zip" | 1 NR FR2 Cell (1 E-UTRA cell), 2 CSI-RSs, 3 time periods, 1AoA beam peak directions and rough beam, fading. | +| CSI-RS_RLM_InSync_02 | 5.5.1.8
7.5.1.8 | "38.533 5.5.1.8+7.5.1.8 TT.zip" | 1 NR FR2 Cell (1 E-UTRA cell), 2 CSI-RSs, 5 time periods, 1AoA in beam peak directions and rough beam, fading. | +| SSB_WithNZP-IMR_L1-SINR-Meas | 5.6.6.2 | "38.533 5.6.6.2 TT.zip" | "1 E-UTRA Cell, 1 NR Cell, 2 time periods, No fading" | +| Inter_band_DAPS_HO | 7.3.1.4
7.3.1.5 | "38.533 7.3.1.4+7.3.1.5 TT.zip " | "1 NR FR2 Cell, 1 SSB, 5 time periods, 1 AoA in Rx peak and rough beam" | +| Intra_Freq_RRC_re-establishment_01 | 7.3.2.1.1
17.3.2.1.1 | "38.533 7.3.2.1.1+17.3.2.1.1 TT" | "2 Intra Frequency NR Cells, 3 time periods, No fading" | +| Inter_Freq_RRC_re-establishment_01 | 7.3.2.1.2
17.3.2.1.2 | "38.533 7.3.2.1.2+17.3.2.1.2 TT" | "2 Inter Frequency NR Cells, 3 time periods, No fading" | +| Intra_freq_HO | 7.3.1.2 | "38.533 7.3.1.2 TT.zip" | 2 NR FR2 intra-frequency Cells, 2 time periods, no fading | +| Inter_freq_HO | 7.3.1.3 | "38.533 7.3.1.3+7.3.2.3.1 TT.zip" | 2 NR FR2 inter-frequency Cells, 2 time periods, no fading | +| Inter_freq_redirection | 7.3.2.3.1 | "38.533 7.3.1.3+7.3.2.3.1 TT.zip" | 2 NR FR2 inter-frequency Cells, 2 time periods, no fading | +| Intra_freq_CHO | 7.3.3.1 | "38.533 7.3.3.1 TT.zip " | 2 NR FR2 Cells, 2 SSBs, 2 time periods, 1 AoA in Rx peak and rough beam | +| CSI-RS_RLM_Out_of_Sync_01 | 5.5.1.5
7.5.1.5 | "38.533 5.5.1.5+7.5.1.5 TT.zip" | 1 NR FR2 Cell (1 E-UTRA cell), 2 CSI-RSs, 3 time periods, 2AoA spherical coverage directions and rough beam, fading. | +| CSI-RS_RLM_InSync_01 | 5.5.1.6
7.5.1.6 | "38.533 5.5.1.6+7.5.1.6 TT.zip" | 1 NR FR2 Cell (1 E-UTRA cell), 2 CSI-RSs, 5 time periods, | + +| | | | | +|--|--|--|---------------------------------------------------------------| +| | | | 2AoA in spherical coverage directions and rough beam, fading. | +|--|--|--|---------------------------------------------------------------| + +| | | | | +|------------------------------------|------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------| +| SSB_RLM_Out_of_Sync_02 | 5.5.1.10 | "38.533 5.5.1.10 TT.zip" | 1 NR FR2 Cell (1 E-UTRA cell), 3 time periods, 1AoA in Rx peak and rough beam, fading. | +| CSI-RS_WithNZP_L1-SINR-Meas | 7.6.6.3 | "38.533 7.6.6.3 TT.zip" | "1 NR Cell, one time period, No fading" | +| L1-RSRP_Accuracy_1 | 5.7.4.1
7.7.4.1 | "38.533 5.7.4.1+7.7.4.1 TT.zip" | 1 NR FR2 Cell, 2 SSBs, 2 subtests, 1 AoA in Rx peak and rough beam | +| L1-RSRP_Accuracy_2 | 5.7.4.2
7.7.4.2 | "38.533 5.7.4.2+7.7.4.2 TT.zip" | 1 NR FR2 Cell, 2 CSI-RS, 2 subtests, 1 AoA in Rx peak and rough beam | +| SSB_WithCSI-IM_L1-SINR-Meas | 7.6.6.2 | "38.533 7.6.6.2 TT.zip" | "1 NR Cell, 2 time periods, No fading" | +| L1-SINR_Accuracy_1 | 5.7.6.1
7.7.6.1 | "38.533 5.7.6.1+7.7.6.1 TT.zip" | 1 NR FR2 Cell, 2 CSI-RSs, 1 subtest, 1 AoA in Rx peak and rough beam | +| L1-SINR_Accuracy_2 | 5.7.6.2 | "38.533 5.7.6.2 TT.zip" | 1 NR FR2 Cell, 2 SSB and 2 CSI-RS, 1 subtests, 1 AoA in Rx peak and rough beam | +| L1-SINR_Accuracy_3 | 5.7.6.3 | "38.533 5.7.6.3 TT.zip" | 1 NR FR2 Cell, 2 CSI-RS and 2 CSI-IM, 1 subtests, 1 AoA in Rx peak and rough beam | +| Inter_Reselection_not_at_cell_edge | 7.1.1.6 | "38.533 7.1.1.6 TT.zip" | "2 NR FR2 Cells, 2 SSBs, 2 time periods, 1 AoA in Rx peak and rough beam" | +| SSB_WithCSI-IM_L1-SINR-Meas | 4.7.7.2
6.7.9.2 | "38.533 4.7.7.2+6.7.9.2 TT.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading" | +| Intra_Reselection | 7.1.1.1
17.1.1.1 | "38.533 7.1.1.1 TT.zip" | "2 NR FR2 Cells, 2 SSBs, 3 time periods, 1 AoA in Rx peak and rough beam" | +| Inter_Reselection | 7.1.1.2
17.1.1.2 | "38.533 7.1.1.2 TT.zip" | "2 NR FR2 Cells, 2 SSBs, 3 time periods, 1 AoA in Rx peak and rough beam" | +| CSI-RS_Based_L1-SINR-Meas | 4.7.7.1.2
6.7.7.9.2 | "38.533 4.7.7.1.2+6.7.7.9.2 TT.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading" | +| RRC_Based_BWP_Switch | 5.5.6.2.1
7.5.6.2.1 | "38.533 5.5.6.2.1+7.5.6.2.1 TT.zip" | "1 NR Cell (1 E-UTRA Cell for NSA case), one time period, No fading" | +| TCI_State_Switch | 7.5.8.1.1
7.5.8.2.1 | "38.533 7.5.8.1.1+7.5.8.2.1 TT.zip" | 1 NR FR2 Cell, 2 SSBs, 2 time periods, no fading, 2AoA in spherical coverage directions and rough | + +| | | | | +|--|--|--|------| +| | | | beam | +|--|--|--|------| + +| | | | | +|------------------------------------|----------------------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Intra_Freq_CLI_SRS-RSRP_Meas | 5.6.4.1
7.6.4.1 | "38.533 5.6.4.1+7.6.4.1 TT.zip" | Cell 1 and Neighbor Cell UE on f1, T1 and T2. | +| Intra_Freq_CLI_SRS-RSRP_Meas_Accu | 5.7.5.1
7.7.5.1 | "38.533 5.7.5.1+7.7.5.1 TT.zip" | Cell 1 and Neighbor Cell UE on f1, T1 and T2. | +| InterRAT_LTE_Idle_CADC_meas | 8.2.2.2 | "38.533 8.2.2.2 TT.zip" | "1 E-UTRA Cell, 1 NR Cell, 3 time periods, no fading" | +| UE_Rx_Tx_difference_PDC_02 | 7.6.13.1
7.6.13.2 | "38.533 7.6.13.1 TT.zip" | "1 NR FR2 Cell, 2 time periods, no fading" | +| RRC_reconfiguration_delay_01 | 7.5.11.1 | "38.533 7.5.11.1 TT.zip" | "2 NR Cells, 3 Time Periods, No Fading" | +| Intra_Reselection_not_at_cell_edge | 7.1.1.4 | "38.533 7.1.1.4 TT.zip" | "2 NR FR2 Cells, 2 SSBs, 2 time periods, 1 AoA in Rx peak and rough beam" | +| Intra_Reselection_low_mobility | 7.1.1.3
17.1.1.3 | "38.533 7.1.1.3 TT.zip" | "2 NR FR2 Cells, 2 SSBs, 2 time periods, 1 AoA in Rx peak and rough beam" | +| RLM_Out_of_Sync_01 | 5.5.1.1
7.5.1.1
17.5.1.1 | 38.533 5.5.1.1+7.5.1.1+17.5.1.1 TT.zip | 1 NR FR2 Cell (1 E-UTRA cell), 2 SSBs, 3 time periods, 2AoA spherical coverage directions and rough beam, fading. | +| RLM_Out_of_Sync_02 | 5.5.1.3
7.5.1.3 | 38.533 5.5.1.3+7.5.1.3 TT.zip | 1 NR FR2 Cell (1 E-UTRA cell), 2 SSBs, 3 time periods, 1AoA in Rx beam peak and rough beam, fading. | +| RLM_InSync_01 | 5.5.1.2
7.5.1.2
17.5.1.2 | 38.533 5.5.1.2+7.5.1.2+17.5.1.2 TT_v2.zip | 1 NR FR2 Cell (1 E-UTRA cell), 2 SSBs, 5 time periods, 2AoA in spherical coverage directions and rough beam, fading. | +| RLM_InSync_02 | 5.5.1.4
7.5.1.4
17.5.1.4 | 38.533 5.5.1.4+7.5.1.4+17.5.1.4 TT.zip | 1 NR FR2 Cell (1 E-UTRA cell), 2 SSBs, 5 time periods, 1AoA in Rx beam peak direction and rough beam, fading. | +| RRC_reconfiguration_delay_01 | 7.5.11.1 | "38.533 7.5.11.1 TT.zip" | "2 NR Cells, 3 Time Periods, No Fading" | +| UE_Rx_Tx_difference_PDC_02 | 7.6.13.1 | "38.533 7.6.13.1 TT.zip" | "1 NR FR2 Cell, 2 time periods, no fading" | +| MAC-CE_Based_Uplink_Spatial_Switch | 5.5.9.1.1
7.5.9.1.1 | "38.533 5.5.9.1.1+7.5.9.1.1 TT.zip" | "1 NR Cell, 2 time periods, no fading" | +| RRC_Based_Uplink_Spatial_Switch | 5.5.9.2.1
7.5.9.2.1 | "38.533 5.5.9.2.1+7.5.9.2.1 TT.zip" | "1 NR Cell, 2 time periods, no fading" | +| Unified_TCI_Switch_01 | 5.5.11.1
5.5.11.2
7.5.13.2 | 38.533 5.5.11.1 + 5.5.11.2 + 7.5.13.2 TT.zip | "1 NR Cell, 2 time periods, no fading" | +| Unified_TCI_Switch_02 | 5.5.11.3 | 38.533 5.5.11.3 + 7.5.13.1 + 7.5.13.3 | "1 NR Cell, 2 time | + +| | | | | +|------------------------|----------------------|-----------------------------------|-------------------------------------------------------------------------------| +| | 7.5.13.1
7.5.13.3 | TT.zip | periods, no fading” | +| Conditional_PSCell_Add | 5.5.13.1
7.5.12.1 | “38.533 5.5.13.1+7.5.12.1 TT.zip” | “1 NR FR2 Cell (1 E-UTRA Cell for NSA case),
4 time periods,
No fading” | +| PSCell_activate | 7.5.14 | “38.533 7.5.14 TT.zip” | “1 NR FR1 Cell, 1 NR FR2 Cell, 4 time periods, no fading” | + +**Table 8-3: Grouping of FR1 NR sidelink test cases defined in Clauses 9 of TS 38.533** + +| Group | Test Case Numbers | .zip file name | Comments | +|-----------------------|--------------------|---------------------------------|----------------------------------------------| +| SL_Timing_Accuracy_01 | 9.1.1.1 | “38.533 9.1.1.1 TT.zip” | 1 time period , no fading | +| SL_Timing_Accuracy_02 | 9.1.1.2 | “38.533 9.1.1.2 TT.zip” | 1 sidelink UE, 1 time period, no fading | +| SL_Timing_Accuracy_03 | 9.1.1.3 | “38.533 9.1.1.3 TT.zip” | 1 Cell, 1 time period, no fading | +| SL_SSB_Tx_01 | 9.1.2.1 | “38.533 9.1.2.1 TT.zip” | 1 Cell, 3 time periods, no fading” | +| SL_SSB_Tx_02 | 9.1.2.2 | “38.533 9.1.2.2 TT.zip” | 1 sidelink UE, 3 time periods, no fading” | +| SyncREF_Reselect_01 | 9.1.3.1 | “38.533 9.1.3.1 TT.zip” | 3 sidelink UEs, 3 time periods, no fading | +| SyncREF_Reselect_02 | 9.1.3.2 | “38.533 9.1.3.2 TT.zip” | 2 sidelink UEs, 3 time periods, no fading | +| SL-RSRP_01 | 9.1.4.1 | “38.533 9.1.4.1 TT.zip” | 50 sidelink UEs, 2 time periods, no fading | +| SL-RSRP_02 | 9.1.4.2 | “38.533 9.1.4.2 TT.zip” | 1 sidelink UE, 2 time periods, no fading” | +| SL-RSRP_03 | 9.1.4.3 | “38.533 9.1.4.3 TT.zip” | 130 sidelink UEs, 2 time periods, no fading” | +| SL-RSSI | 9.1.5.1
9.1.5.2 | “38.533 9.1.5.1+9.1.5.2 TT.zip” | 4 sidelink UEs, 2 time periods, no fading” | +| WAN_Interruption | 9.1.6.1 | “38.533 9.1.6.1 TT.zip” | 8 sidelink UEs, 3 time periods, no fading” | + +--- + +## 9 Grouping of test cases defined in TS 37.571-1 + +**Table 9-1: Grouping of positioning test cases defined in TS 37.571-1** + +| Group | Test Case Numbers | .zip file name | Comments | +|-----------------------------|-------------------|-----------------------------|----------------------------------------------------------------------------| +| RSTD_reporting_1 | 14.2.1 | "37.571-1 14.2.1 TT.zip" | 3cells, RSTD reporting delay
Single positioning frequency layer
FR1 | +| RSTD_Accuracy_1 | 14.3.1 | "37.571-1 14.3.1 TT.zip" | RSTD accuracy
Single positioning frequency layer
FR1 | +| RSTD_reporting_2 | 14.2.2 | "37.571-1 14.2.2 TT.zip" | 3 cells, 2 PFLs, reporting delay, FR1 | +| RSTD_accuracy_2 | 14.3.2 | "37.571-1 14.3.2 TT v2.zip" | 3 cells, 2 PFLs, RSTD accuracy, FR1 | +| RSTD_accuracy_3 | 14.3.3 | "37.571-1 14.3.3 TT.zip" | RSTD accuracy
Single positioning frequency layer
FR2 | +| RSTD_accuracy_4 | 14.3.4 | "37.571-1 14.3.4 TT.zip" | RSTD accuracy
Dual positioning frequency layer
FR2 | +| RSTD_reporting_3 | 14.2.3 | "37.571-1 14.2.3 TT.zip" | 3 cells, RSTD reporting delay
Single positioning frequency layer
FR2 | +| RSTD_reporting_4 | 14.2.4 | "37.571-1 14.2.4 TT.zip" | 3 cells, RSTD reporting delay
Dual positioning frequency layer
FR2 | +| PRP_reporting_1 | 16.2.3 | "37.571-1 16.2.3 TT.zip" | PRP reporting delay,
Single positioning frequency layer
FR2 | +| PRP_reporting_2 | 16.2.4 | "37.571-1 16.2.4 TT.zip" | PRP reporting delay,
Dual positioning frequency layer
FR2 | +| PRP_reporting_3 | 16.2.1 | "37.571-1 16.2.1 TT.zip" | PRP reporting delay,
Single positioning frequency layer
FR1 | +| PRP_reporting_4 | 16.2.2 | "37.571-1 16.2.2 TT.zip" | PRP reporting delay, | +| PRP_accuracy_1 | 16.3.1 | "37.571-1 16.3.1 TT.zip" | PRP reporting accuracy,
Single positioning frequency layer
FR1 | +| PRP_accuracy_1 | 16.3.2 | "37.571-1 16.3.2 TT.zip" | PRP accuracy,
Single positioning frequency layer
FR2 | +| UE_RxTxTimeDiff_reporting_1 | 15.2.1 | "37.571-1 15.2.1 TT.zip" | UE Rx-Tx time difference reporting delay,
Single positioning | + +| | | | | +|--|--|--|------------------------| +| | | | frequency layer
FR1 | +|--|--|--|------------------------| + +| | | | | +|-----------------------------|---------|---------------------------|----------------------------------------------------------------------------------------------------| +| UE_RxTxTimeDiff_reporting_2 | 15.2.2 | "37.571-1 15.2.2 TT.zip" | UE Rx-Tx time difference reporting delay, Dual positioning frequency layer FR1 | +| UE_RxTxTimeDiff_reporting_3 | 15.2.3 | "37.571-1 15.2.3 TT.zip" | UE Rx-Tx time difference reporting delay, Single positioning frequency layer FR2 | +| UE_RxTxTimeDiff_reporting_4 | 15.2.4 | "37.571-1 15.2.4 TT.zip" | UE Rx-Tx time difference reporting delay, Dual positioning frequency layer FR2 | +| UE_RxTxTimeDiff_accuracy_1 | 15.3.1 | "37.571-1 15.3.1 TT.zip" | UE Rx-Tx time difference accuracy, Single positioning frequency layer FR1 | +| UE_RxTxTimeDiff_accuracy_2 | 15.3.2 | "37.571-1 15.3.2 TT.zip" | UE Rx-Tx time difference accuracy, Single positioning frequency layer FR2 | +| UE_RxTxTimeDiff_accuracy_3 | 15.3.5 | "37.571-1 15.3.5 TT.zip" | UE Rx-Tx time difference accuracy, reduce number of samples Single positioning frequency layer FR2 | +| UE_RxTxTimeDiff_accuracy_4 | 15.3.6 | "37.571-1 15.3.6 TT.zip" | UE Rx-Tx time difference accuracy, Same RxTx TEG Single positioning frequency layer FR2 | +| RSTD_reporting_5 | 14.2.8 | "37.571-1 14.2.8 TT.zip" | 3 cells, RSTD reporting delay, reduce number of samples, Single positioning frequency layer FR2 | +| RSTD_reporting_6 | 14.2.9 | "37.571-1 14.2.9 TT.zip" | 3 cells, RSTD reporting delay, without MG, Single positioning frequency layer FR2 | +| RSTD_reporting_7 | 14.2.10 | "37.571-1 14.2.10 TT.zip" | 3 cells, RSTD reporting delay, reduce number of samples, Single positioning | + +| | | | | +|-----------------|--------|--------------------------|------------------------------------------------------------------------------------------| +| | | | frequency layer
FR2 | +| RSTD_accuracy_5 | 14.3.7 | "37.571-1 14.3.7 TT.zip" | 2 cells, RSTD accuracy, reduce number of samples, Single positioning frequency layer FR2 | +| RSTD_accuracy_6 | 14.3.8 | "37.571-1 14.3.8 TT.zip" | 2 cells, RSTD accuracy, same Rx TEG, Single positioning frequency layer FR2 | + +## Annex A: Derivation documents for test tolerance + +The documents (and spreadsheets where applicable) used to derive the test tolerances for each test case are included in the present document as zip files. + +The aim is to provide a reference to completed test cases, so that test tolerances for similar test cases can be derived on a common basis. The information on test case grouping in clauses 7 and 8 can be used to identify similarities. + +### A.1 Void + +### A.2 Handling of common Test Tolerance topics for radiated test cases defined in TS 38.533 + +The basic principles of Test Tolerance analysis are the same for conducted testing and radiated testing, but for radiated testing additional topics are taken into account. This annex contains methods to handle common additional topics, to allow re-use and to avoid the need for each test case analysis to repeat the same detail. + +Individual test case analyses are expected to follow the methods contained here where applicable, and to refer to relevant clauses in this Annex. + +#### A.2.1 Angles of Arrival + +##### A.2.1.1 Relevant core requirements + +In FR2, the performance of the UE depends on the downlink signal angle of arrival, and is characterised by two parameters: + +- Refsens: lowest signal level for a given demodulation performance in the UE Rx beam peak direction, specified in TS 38.101-2 [16] clause 7.3.2 according to UE Power class, Channel bandwidth and operating band +- EIS spherical coverage: lowest signal level for a given demodulation performance in a specified percentile of other directions, specified in TS 38.101-2 [16] clause 7.3.4 according to UE Power class, Channel bandwidth and operating band + +As both of these requirements are defined in the context of a throughput requirement, the UE is assumed to be using fine beams. Note that for directions outside the specified percentile of spherical coverage directions, there are no requirements. Testing must therefore be carried out within the spherical coverage directions. For testing, direction is 3-dimensional, but the principle can be illustrated in a 2-dimensional diagram: + +![Diagram illustrating UE Rx Beam-peak and spherical coverage directions. A central blue rectangle represents the UE. A green horizontal oval represents the Rx Beam peak direction, with an arrow pointing to it from the left labeled 'Rx Beam peak direction'. A dashed circle represents the spherical coverage area, with a green arc on the right labeled 'Spherical coverage %ile met'. A text box on the right indicates 'X = -10.9dB Spherical coverage gain difference for PC3, n257'.](ac42de838505beb048fb1267c46de428_img.jpg) + +The diagram shows a central blue rectangle labeled 'UE'. A green horizontal oval represents the 'Rx Beam peak direction', with an arrow pointing to it from the left. A dashed circle represents the 'Spherical coverage %ile met' area. A green arc on the right side of the circle is labeled 'Spherical coverage %ile met'. A text box on the right indicates 'X = -10.9dB Spherical coverage gain difference for PC3, n257'. + +Diagram illustrating UE Rx Beam-peak and spherical coverage directions. A central blue rectangle represents the UE. A green horizontal oval represents the Rx Beam peak direction, with an arrow pointing to it from the left labeled 'Rx Beam peak direction'. A dashed circle represents the spherical coverage area, with a green arc on the right labeled 'Spherical coverage %ile met'. A text box on the right indicates 'X = -10.9dB Spherical coverage gain difference for PC3, n257'. + +Figure A.2.1.1-1: UE Rx Beam-peak and spherical coverage directions, Fine beams + +### A.2.1.2 Modelling of variation within spherical coverage directions + +Within the spherical coverage directions, a signal may be anywhere from near Rx Beam Peak (high gain direction, close to Refsens) to the worst of the allowed percentile (low gain direction, close to EIS spherical coverage requirement value). This is modelled by taking the midpoint of the Spherical coverage range as the nominal value, and then adding a variation of $\pm$ (half the difference between Refsens and Spherical coverage). + +UE Spherical coverage gain midpoint in dB is derived as $(\text{UE Refsens} - \text{UE Spherical coverage})/2$ + +Figure A.2.1.2-1 shows an example for UE Power class 3, Channel bandwidth 100MHz and operating band n257. In this example the UE Spherical coverage gain midpoint would be -80.45dB, as the gain is lower than in the Rx Beam peak direction. Variation about the midpoint is handled as a UE uncertainty. + +![Figure A.2.1.2-1: Example modelling of variation within spherical coverage directions, Fine beams. The diagram shows a vertical scale with values -74.4, -80, -85.3, and -90 dBm/Ch BW. The top level is labeled 'EIS Spherical coverage -74.4dBm/Ch BW for PC3, n257, 100MHz'. The bottom level is labeled 'Refsens -85.3dBm/Ch BW for PC3, n257, 100MHz'. A green double-headed arrow between these two levels is labeled 'Variation of Spherical coverage ±5.45dB'. A blue double-headed arrow from the Refsens level to a dashed line halfway between the top and bottom levels is labeled 'Midpoint of Spherical coverage 5.45dB relative to Refsens'.](b7ba15a6ada4aa0d16e79ef30b2ae494_img.jpg) + +Figure A.2.1.2-1: Example modelling of variation within spherical coverage directions, Fine beams. The diagram shows a vertical scale with values -74.4, -80, -85.3, and -90 dBm/Ch BW. The top level is labeled 'EIS Spherical coverage -74.4dBm/Ch BW for PC3, n257, 100MHz'. The bottom level is labeled 'Refsens -85.3dBm/Ch BW for PC3, n257, 100MHz'. A green double-headed arrow between these two levels is labeled 'Variation of Spherical coverage ±5.45dB'. A blue double-headed arrow from the Refsens level to a dashed line halfway between the top and bottom levels is labeled 'Midpoint of Spherical coverage 5.45dB relative to Refsens'. + +**Figure A.2.1.2-1: Example modelling of variation within spherical coverage directions, Fine beams** + +### A.2.1.3 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- The Angle of Arrival for each downlink signal shall be defined: either from UE Rx beam peak direction or from a direction within the EIS spherical coverage +- Variations over the EIS spherical coverage directions shall be included, using the method shown in A.2.1.2. + +Variations over the EIS spherical coverage directions do not directly affect signals applied to the UE, but they do affect the SS-RSRP level measured by the UE, and the Es/Iot at UE baseband. Where the test case has requirements on UE baseband Es/IotBB, UE internal noise calculation is given in clause A.2.3, and calculation of Es/Iot at UE baseband is given in clauses A.2.4 and A.2.7. + +## A.2.2 UE Fine beams and Rough beams + +### A.2.2.1 Relevant core requirements + +UE requirements such as Refsens in TS 38.101-2 [16], assume that the UE is using a fine beam which has higher antenna gain to give good demodulation performance. However, in some RRM scenarios where the UE is for example searching for or measuring other cells, the UE uses rough beams which have lower antenna gain. The difference in gain is specified depending on the Angle of Arrival: + +- The Gain difference $Y$ between fine and rough beams in the UE Rx beam peak direction is specified in TS 38.133 [17] Table B.2.1.3.1-1 according to UE Power class +- The Gain difference $Z$ between fine and rough beams in the UE Spherical coverage directions is specified in TS 38.133 [17] Table B.2.1.3.2-1 according to UE Power class + +The Gain differences $Y$ and $Z$ are not dependent on Channel bandwidth or operating band. The concept is illustrated in Figures A.2.2.1-1 and A.2.2.1-2. + +![Figure A.2.2.1-1: Fine and rough beams, Rx Beam peak direction. The diagram shows a User Equipment (UE) represented by a blue rectangle. A green arrow points to the UE from the left, labeled 'Rx Beam peak direction'. A yellow oval (Rough beam) and a green oval (Fine beam) are shown. Concentric dashed circles represent the beam coverage. Text indicates 'Y = 7dB gain difference, fine/rough PC3, all bands'. A legend on the right shows a green oval labeled 'Fine beam' and a yellow oval labeled 'Rough beam'.](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +Figure A.2.2.1-1: Fine and rough beams, Rx Beam peak direction. The diagram shows a User Equipment (UE) represented by a blue rectangle. A green arrow points to the UE from the left, labeled 'Rx Beam peak direction'. A yellow oval (Rough beam) and a green oval (Fine beam) are shown. Concentric dashed circles represent the beam coverage. Text indicates 'Y = 7dB gain difference, fine/rough PC3, all bands'. A legend on the right shows a green oval labeled 'Fine beam' and a yellow oval labeled 'Rough beam'. + +Figure A.2.2.1-1: Fine and rough beams, Rx Beam peak direction + +![Figure A.2.2.1-2: Fine and rough beams, spherical coverage directions. The diagram shows a User Equipment (UE) represented by a blue rectangle. A green arrow points to the UE from the left, labeled 'Rx Beam peak direction'. Concentric dashed circles represent the beam coverage. A green arc on the outer circle is labeled 'Spherical coverage %ile met'. Text indicates 'Z = 7dB gain difference, fine/rough PC3, all bands'. A legend on the right shows a green oval labeled 'Fine beam' and a yellow oval labeled 'Rough beam'.](b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg) + +Figure A.2.2.1-2: Fine and rough beams, spherical coverage directions. The diagram shows a User Equipment (UE) represented by a blue rectangle. A green arrow points to the UE from the left, labeled 'Rx Beam peak direction'. Concentric dashed circles represent the beam coverage. A green arc on the outer circle is labeled 'Spherical coverage %ile met'. Text indicates 'Z = 7dB gain difference, fine/rough PC3, all bands'. A legend on the right shows a green oval labeled 'Fine beam' and a yellow oval labeled 'Rough beam'. + +Figure A.2.2.1-2: Fine and rough beams, spherical coverage directions + +When the Rx Beam Peak is selected and defined based on Fine Beams, the rough beam gain in that direction may be lower than the largest rough beam gain in another direction within Spherical Coverage. The term “D” is the maximum allowed rough beam gain reduction and is specified in TS 38.133 [17] Table B.2.1.5.3-1 for each power class. D parameter is applicable only to RSRP relative accuracy test cases. + +![Diagram illustrating fine and rough beams alignment for a User Equipment (UE). The UE is shown as a grey rectangle at the top. Below it, a green oval represents the coverage area. A dashed line indicates the peak direction of the 'Rx fine beam', which is a narrow, elongated green shape. A solid line indicates the peak direction of the 'Rx rough beam', which is a wider, more circular green shape. The angle between the two beams is labeled 'D'.](fbdb9a4a74e70721e19f3d576ba7b651_img.jpg) + +Diagram illustrating fine and rough beams alignment for a User Equipment (UE). The UE is shown as a grey rectangle at the top. Below it, a green oval represents the coverage area. A dashed line indicates the peak direction of the 'Rx fine beam', which is a narrow, elongated green shape. A solid line indicates the peak direction of the 'Rx rough beam', which is a wider, more circular green shape. The angle between the two beams is labeled 'D'. + +**Figure A.2.2.1-3: Fine and rough beams alignment, Rx Beam peak direction** + +## A.2.2.2 Modelling of Fine beams and Rough beams + +Where the UE is assumed to use fine beams, the scenario is already covered in the Refsens and EIS spherical coverage requirements, and no further modifications are needed. + +Where the UE is assumed to use rough beams, the effect is modelled as a reduction in gain of YdB or ZdB, according to the Angle of Arrival of each downlink signal. The reduction in gain translates to a higher UE internal noise seen at the Reference point where the downlink signals are applied. UE noise calculated from Refsens or from EIS spherical coverage requirements is increased by YdB or ZdB respectively. UE internal noise calculation is given in clause A.2.3. + +## A.2.2.3 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- The Type of beam assumed to be used by the UE for each downlink signal shall be defined: either Fine Beam or Rough Beam +- Where UE internal noise is relevant, and the UE is assumed to be using Rough Beams, it is increased by the value of Y or Z, selected according to UE Power class and Angle of Arrival. + +UE internal noise calculation is given in clause A.2.3. + +## A.2.3 UE internal noise + +### A.2.3.1 Relevant core requirements + +The relevant Core requirements are: + +- Refsens or EIS spherical coverage, specified in TS 38.101-2 [16] clauses 7.3.2 and 7.3.4 respectively +- UE baseband SNR at which Refsens or EIS spherical coverage is specified, in TS 38.133 [17] clause B.2.1.3 +- $N_{RB}$ in channel BW at which Refsens or EIS spherical coverage is specified, in TS 38.101-2 [16] Table 5.3.2-1 +- Gain difference between fine and rough beams, in TS 38.133 [17] clause B.2.1.3 +- UE multi-band relaxation factors, in TS 38.101-2 [16] Table 6.2.1.3-4 + +### A.2.3.2 Calculation method + +For signals arriving from Rx Beam Peak direction: + +$$\text{Noise in dBm/SCS} = \text{Refsens}_{\text{PC, band, Ch BW}} - \text{SNR}_{\text{Refsens}} - 10\text{Log}_{10}(\text{N}_{\text{RB\_Ch BW, SCS}} \times 12) + Y_{\text{PC}} + \Sigma\text{MB}_p$$ + +where: + +$\text{Refsens}_{\text{PC, band, Ch BW}}$ is the reference sensitivity value in dBm specified in TS 38.101-2 [16] clause 7.3.2 according to Power Class, Operating band and Channel bandwidth + +$\text{SNR}_{\text{Refsens}}$ is the SNR used for simulation of Refsens and EIS spherical coverage, and is -1 dB + +$\text{N}_{\text{RB\_Ch BW, SCS}}$ is the number of PRBs specified in TS 38.101-2 [16] Table 5.3.2-1 according to Channel bandwidth and subcarrier spacing (not necessarily equal to the number of PRBs used in the test case) + +12 is the number of subcarriers in a PRB + +$Y_{\text{PC}}$ is the gain difference in dB specified in TS 38.133 [17] Table B.2.1.3.1-1, according to Power Class, and is only applied when the UE is assumed to be using rough beams. Otherwise, use 0dB + +$\Sigma\text{MB}_p$ is the UE multi-band relaxation factor value in dB specified in TS 38.101-2 [16] clause 6.2.1 + +For signals arriving from Spherical coverage directions: + +$$\text{Noise in dBm/SCS} = \text{EIS spherical coverage}_{\text{PC, band, Ch BW}} - \text{SNR}_{\text{Refsens}} - 10\text{Log}_{10}(\text{N}_{\text{RB\_Ch BW, SCS}} \times 12) + Z_{\text{PC}} + \Sigma\text{MB}_s$$ + +where: + +$\text{EIS spherical coverage}_{\text{PC, band, Ch BW}}$ is the EIS spherical coverage value in dBm specified in TS 38.101-2 [16] clause 7.3.4 according to Power Class, Operating band and Channel bandwidth + +$\text{SNR}_{\text{Refsens}}$ is the SNR used for simulation of Refsens and EIS spherical coverage, and is -1 dB + +$\text{N}_{\text{RB\_Ch BW, SCS}}$ is the number of PRBs specified in TS 38.101-2 [16] Table 5.3.2-1 according to Channel bandwidth and subcarrier spacing (not necessarily equal to the number of PRBs used in the test case) + +12 is the number of subcarriers in a PRB + +$Z_{\text{PC}}$ is the gain difference in dB specified in TS 38.133 [17] Table B.2.1.3.2-1, according to Power Class, and is only applied when the UE is assumed to be using rough beams. Otherwise, use 0dB + +$\Sigma\text{MB}_s$ is the UE multi-band relaxation factor value in dB specified in TS 38.101-2 [16] clause 6.2.1 + +The analysis spreadsheet converts dBm/SCS to linear power in pW/SCS for ease of further calculations. + +### A.2.3.3 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- Where the test case has requirements on UE baseband $E_s/I_{\text{ot, BB}}$ , the Test Tolerance analysis should include UE internal noise in the calculation +- UE internal noise is calculated using the method in A.2.3.2 + +## A.2.4 Calculation of Es/Iot at UE baseband + +### A.2.4.1 Relevant core requirements + +Core requirements applicable to RRM test cases depend on the test purpose, and should be selected for each test case. For test cases where the UE makes a measurement, the following are relevant: + +- Measurement Performance requirements are specified in TS 38.133 [17] clause 10, and side conditions such as Es/Iot are included in the core requirements for each measurement. For FR2, notes in tables clarify that Es/Iot is at UE baseband. +- Operating band specific conditions for RRM requirements are specified in TS 38.133 [17] Annex B, and side conditions such as Es/Iot are included for each measurement. For FR2, notes in tables clarify that Es/Iot is at UE baseband. + +Other UE core requirements may also have conditions on Es/Iot. + +### A.2.4.2 Calculation method + +An example is provided here for a scenario with applied AWGN and two intra-frequency cells. SSB Es/Iot at UE baseband is calculated for Cell 1. Interference to Cell 1 comes from the applied AWGN, from the UE internal noise, and from Cell 2. The values are chosen for illustration, and not taken from any specific test case. + +$$\text{Cell 1 SSB Es/Iot}_{\text{BB}} = 10\text{Log}_{10}((\text{Cell 1 SSB power}) / (\text{Applied AWGN power} + \text{UE internal noise} + \text{Cell 2 SSB power}))$$ + +Where Applied AWGN power, UE internal noise, Cell 1 power and Cell 2 power are linear powers in W, per subcarrier. + +![Figure A.2.4.2-1: Example Es/IotBB scenario, applied AWGN and two intra-frequency cells. The figure consists of a pie chart and a legend box. The pie chart shows the power distribution: Cell 1 (46.1%, light blue), Cell 2 (23.1%, light green), Applied AWGN (18.4%, light grey), and UE internal noise (12.4%, dark grey). The legend box lists the absolute power values: Cell 1: 0.139 pW/SCS, Cell 2: 0.070 pW/SCS, Applied AWGN: 0.055 pW/SCS, UE internal noise: 0.037 pW/SCS.](f63b26e4e96e0f42eb14f1ad67838ec5_img.jpg) + +| Source | Power (pW/SCS) | Percentage | +|-------------------|----------------|------------| +| Cell 1 | 0.139 | 46.1% | +| Cell 2 | 0.070 | 23.1% | +| Applied AWGN | 0.055 | 18.4% | +| UE internal noise | 0.037 | 12.4% | + +Figure A.2.4.2-1: Example Es/IotBB scenario, applied AWGN and two intra-frequency cells. The figure consists of a pie chart and a legend box. The pie chart shows the power distribution: Cell 1 (46.1%, light blue), Cell 2 (23.1%, light green), Applied AWGN (18.4%, light grey), and UE internal noise (12.4%, dark grey). The legend box lists the absolute power values: Cell 1: 0.139 pW/SCS, Cell 2: 0.070 pW/SCS, Applied AWGN: 0.055 pW/SCS, UE internal noise: 0.037 pW/SCS. + +**Figure A.2.4.2-1: Example Es/IotBB scenario, applied AWGN and two intra-frequency cells** + +In this case, the calculation gives $\text{Cell 1 SSB Es/Iot}_{\text{BB}} = 10\text{Log}_{10}(0.139 / (0.055 + 0.037 + 0.070)) = -0.67\text{dB}$ + +The main point is that the Es/Iot at UE baseband is lower than the applied Es/Iot, because the UE internal noise adds to the interference, and can be a significant contribution for the parameters used in some test cases. + +The presence of UE internal noise also affects the calculation of Es/Iot sensitivity factors in the Test Tolerance analysis. The UE internal noise is a fixed (worst) value, being based on the UE minimum requirement, and is taken into account in the scaling which uses linear powers: + +- Cell 1 SSB Es/IotBB sensitivity to applied AWGN absolute power = UE internal noise / (Applied AWGN power + UE internal noise + Cell 2 SSB power). In this example, $(0.037 / (0.055 + 0.037 + 0.070)) = +0.230$ +- Cell 1 SSB Es/IotBB sensitivity to Cell 1 Es/Noc = +1.000 + +- Cell 1 SSB $E_s/I_{ot_{BB}}$ sensitivity to Cell 2 $E_s/N_{oc} = -\text{Cell 2 SSB power} / (\text{Applied AWGN power} + \text{UE internal noise} + \text{Cell 2 SSB power})$ . In this example, $(0.070 / (0.055 + 0.037 + 0.070)) = -0.429$ + +A positive sensitivity factor is used where an increase in the quantity produces an increase in Cell 1 SSB $E_s/I_{ot_{BB}}$ , for example increasing Cell 1 $E_s/N_{oc}$ . A negative sensitivity factor is used where an increase in the quantity produces a decrease in Cell 1 SSB $E_s/I_{ot_{BB}}$ , for example increasing Cell 2 $E_s/N_{oc}$ . The sensitivity factors are used to scale the uncertainties. + +Where the uncertainties are uncorrelated, as here, they are added root-sum-square so the sign of the sensitivity factor does not have any effect. In special cases where the uncertainties are correlated, they may be added arithmetically and the sign affects the result, as in clause A.2.7. + +### A.2.4.3 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- UE internal noise is included in the interference when calculating $E_s/I_{ot_{BB}}$ +- $E_s/I_{ot_{BB}}$ sensitivity factors are calculated using the method in A.2.4.2 + +## A.2.5 Calculation of Applied $I_o$ + +### A.2.5.1 Relevant core requirements + +Core requirements applicable to RRM test cases depend on the test purpose, and should be selected for each test case. For test cases where the UE makes a measurement, the following are relevant: + +- Measurement Performance requirements are specified in TS 38.133 [17] clause 10, and side conditions such as $I_o$ are included in the core requirements for each measurement. Normally the maximum $I_o$ condition is specified in the channel bandwidth, whereas the minimum $I_o$ condition is specified as a power density per subcarrier. + +### A.2.5.2 Calculation method + +An example is provided here for a scenario with applied AWGN and two intra-frequency cells. $I_o$ applied to the UE is the arithmetic sum of linear powers in the channel bandwidth. UE internal noise is not counted, as it is not applied to the UE. The values are chosen for illustration, and not taken from any specific test case. + +$$\text{Channel } I_o = 10\text{Log}_{10}(\text{Applied AWGN power} + \text{Cell 1 power} + \text{Cell 2 power}) + 10\text{Log}_{10}(N_{\text{RB\_TC}} \times 12)$$ + +where: + +AWGN, Cell 1 power and Cell 2 power are linear powers in W, per subcarrier + +$N_{\text{RB\_TC}}$ is the number of PRBs allocated in the test case (not necessarily equal to the number of PRBs in the channel bandwidth) + +12 is the number of subcarriers in a PRB + +![Pie chart showing the power distribution for an example Io scenario. The chart is divided into three segments: Cell 1 (52.6%, light blue), Cell 2 (26.4%, light green), and Applied AWGN (21%, grey). A legend box to the right of the chart lists the power values: Cell 1: 0.139 pW/SCS, Cell 2: 0.070 pW/SCS, and Applied AWGN: 0.055 pW/SCS.](b90dcb4c35f1875e19ca312a6cf4adae_img.jpg) + +| | +|----------------------------| +| Cell 1: 0.139 pW/SCS | +| Cell 2: 0.070 pW/SCS | +| Applied AWGN: 0.055 pW/SCS | + +Pie chart showing the power distribution for an example Io scenario. The chart is divided into three segments: Cell 1 (52.6%, light blue), Cell 2 (26.4%, light green), and Applied AWGN (21%, grey). A legend box to the right of the chart lists the power values: Cell 1: 0.139 pW/SCS, Cell 2: 0.070 pW/SCS, and Applied AWGN: 0.055 pW/SCS. + +**Figure A.2.5.2-1: Example Io scenario, applied AWGN and two intra-frequency cells** + +With 24 PRBs allocated, the example gives $I_o = 10\text{Log}_{10}((0.055 + 0.139 + 0.070) \times 10^{-9}) + 10\text{Log}_{10}(24 \times 12) = -71.2\text{dBm}$ + +Io sensitivity factors in the Test Tolerance analysis are based on linear powers: + +- Io sensitivity to applied AWGN absolute power = **+1.000** +- Io sensitivity to Cell 1 $E_s/N_{oc} = \text{Cell 1 power} / (\text{Applied AWGN power} + \text{Cell 1 power} + \text{Cell 2 power})$ . In this example, $(0.139 / (0.055 + 0.139 + 0.070)) = +0.527$ +- Io sensitivity to Cell 2 $E_s/N_{oc} = \text{Cell 2 power} / (\text{Applied AWGN power} + \text{Cell 1 power} + \text{Cell 2 power})$ . In this example, $(0.070 / (0.055 + 0.139 + 0.070)) = +0.264$ + +All the sensitivity factors are positive, as an increase in the quantity produces an increase in $I_o$ . The sensitivity factors are used to scale the uncertainties. + +### A.2.5.3 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- Io is calculated using the method in A.2.5.2 +- Io sensitivity factors are calculated using the method in A.2.5.2 + +## A.2.6 UE Reported RSRP and UE gain + +### A.2.6.1 Relevant core requirements + +SS-RSRP is defined to be measured based on the combined signal from antenna elements corresponding to a given receiver branch. The reference point for requirement parameters from the UE perspective is the input of the UE antenna array. The UE gain “G” relates the combined signal from antenna elements corresponding to a given receiver branch to the reference point for requirement parameters. + +For test cases where the UE reports a measured value, or compares a measured value to a signalled threshold, the UE Gain “G” affects the SS-RSRP level measured by the UE + +- The UE Gain from the reference point (where test case parameters are specified) to the SS-RSRP measurement point is specified in TS 38.133 [17] clause B.2.1.5. As the UE gain “G” is specified for Rx Beam Peak angle of arrival, it does not include effects related to spherical coverage. +- Measurement Performance requirements are specified in TS 38.133 [17] clause 10, and include accuracy requirements as +/-dB values. For FR2, the accuracy is considered to apply at the combined signal from antenna elements corresponding to a given receiver branch, and does not include the UE gain “G”. + +The specified range of UE Gain “G” allows the UE to use either Rough beams or Fine beams, so no further allowance is required for the parameters Y or Z in A.2.2. + +In any specific direction, the UE gain G may be different depending on frequencies. The UE gain difference between inter-frequencies “Ginter” affects relative signal level values reported by the UE when measuring between different frequencies and is specified in TS 38.133 [17] Table B.2.1.5.2-1 for each power class. Ginter parameter is applicable only to RSRP relative accuracy test cases. + +## A.2.6.2 Absolute RSRP + +An example is provided here for a scenario where the UE reports SS-RSRP for a signal arriving from a direction within the UE spherical coverage, to illustrate variation from both UE spherical coverage and variation from UE gain “G”. + +$$\text{UE-measured SS-RSRP}_{\text{nom}} = \text{Applied SSB\_RP} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +where: + +Applied SSB\_RP is specified in the test case, either directly as Es or derived from Noc and Es/Noc, and is in dBm per subcarrier + +UE Spherical coverage gain midpoint in dB is derived as (UE Refsens - UE Spherical coverage)/2 + +UE gain G midpoint in dB is derived as (Min value of G + Max value of G)/2 + +As an example for a UE power class 3 in band n257, measuring SS\_RSRP from a spherical coverage direction, UE-measured SS-RSRPnom = Applied SSB\_RP -5.45dB +5.0dB. + +Figure A.2.1.2-1 shows the derivation of UE Spherical coverage gain midpoint. Variation about the midpoint is handled as a UE uncertainty. For signals arriving from Rx Beam Peak direction, this gain is 0dB and does not vary. + +Figure A.2.6.2-1 shows the derivation of UE gain G midpoint. Variation about the midpoint is handled as a UE uncertainty. + +![Figure A.2.6.2-1: Example modelling of UE Gain “G” variation. The diagram shows a vertical scale for gain in dB, ranging from -10 to +20. The maximum gain is labeled as +20 dB for PC3, and the minimum gain is labeled as -10 dB for PC3. The midpoint of the gain is indicated at +5 dB. A green double-headed arrow shows the variation of gain, labeled as ±15 dB, centered around the midpoint. A blue arrow points to the midpoint at +5 dB.](df743a70d0295e880847c81ef47df4b5_img.jpg) + +The figure illustrates the modeling of UE Gain “G” variation. It features a vertical axis representing gain in dB, with major tick marks at -10, 0, +10, and +20. The top of the axis is labeled “Maximum gain “G” +20dB for PC3” and the bottom is labeled “Minimum gain “G” -10dB for PC3”. A horizontal dashed line at +5 dB is labeled “Midpoint of Gain +5dB” with a blue arrow pointing to it. A vertical green double-headed arrow spans from -10 dB to +20 dB, centered on the +5 dB midpoint, and is labeled “Variation of gain ±15dB”. Dashed horizontal lines extend from the maximum and minimum gain values to the right side of the axis. + +Figure A.2.6.2-1: Example modelling of UE Gain “G” variation. The diagram shows a vertical scale for gain in dB, ranging from -10 to +20. The maximum gain is labeled as +20 dB for PC3, and the minimum gain is labeled as -10 dB for PC3. The midpoint of the gain is indicated at +5 dB. A green double-headed arrow shows the variation of gain, labeled as ±15 dB, centered around the midpoint. A blue arrow points to the midpoint at +5 dB. + +Figure A.2.6.2-1: Example modelling of UE Gain “G” variation + +To calculate the range of valid SS-RSRP values that can be reported by the UE, contributions from Spherical coverage gain variation, UE gain variation and UE reporting accuracy are considered: + +![Figure A.2.6.2-2: modelling of contributions affecting SS-RSRP reported values. The diagram illustrates the signal path from a base station to a User Equipment (UE). On the left, a circular diagram shows the UE's spherical coverage gain, with a 'Rx Beam peak direction' indicated by an arrow. A note specifies 'Xmin = -10.9dB for PC3, n257'. A green arrow points to the outer ring of the circle, labeled 'Spherical coverage directions with lower gain'. The middle section shows the UE's internal components: an 'Array' of antenna elements, an 'RF' block, and a 'Baseband' block. The 'Array' is connected to the 'RF' block, which is connected to the 'Baseband' block. The 'Baseband' block outputs 'Reported SS-RSRP values'. Above the 'Array' is a label 'UE Gain ](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +Figure A.2.6.2-2: modelling of contributions affecting SS-RSRP reported values. The diagram illustrates the signal path from a base station to a User Equipment (UE). On the left, a circular diagram shows the UE's spherical coverage gain, with a 'Rx Beam peak direction' indicated by an arrow. A note specifies 'Xmin = -10.9dB for PC3, n257'. A green arrow points to the outer ring of the circle, labeled 'Spherical coverage directions with lower gain'. The middle section shows the UE's internal components: an 'Array' of antenna elements, an 'RF' block, and a 'Baseband' block. The 'Array' is connected to the 'RF' block, which is connected to the 'Baseband' block. The 'Baseband' block outputs 'Reported SS-RSRP values'. Above the 'Array' is a label 'UE Gain + +**Figure A.2.6.2-2: modelling of contributions affecting SS-RSRP reported values** + +$$\text{Reported SS-RSRP} = \text{UE measured SS-RSRP}_{\text{nom}} \pm \text{Spherical coverage gain variation} \pm \text{UE gain variation} \pm \text{UE accuracy}$$ + +where: + +UE measured SS-RSRPnom is the nominal value derived from Applied SSB\_RP, UE Spherical coverage gain midpoint and UE gain G midpoint + +Spherical coverage gain variation is derived from Refsens and Spherical coverage, as shown in Figure A.2.1.2-1 + +UE gain variation is derived from Minimum and maximum values of G, as shown in Figure A.2.6.2-1 + +UE accuracy is the absolute accuracy from the core requirement referred to in A.2.6.1 + +As an example for a UE power class 3 in band n257, measuring SS\_RSRP from a spherical coverage direction with applied Io > -70dBm, the variation would be $(\pm 5.45\text{dB} \pm 15\text{dB} \pm 8\text{dB}) = \pm 28.45\text{dB}$ + +These variations are added arithmetically in the test case analysis, as each could be systematic and not random. For signals arriving from Rx Beam Peak direction, spherical coverage gain variation is 0dB. + +### A.2.6.3 Relative RSRP, 2 levels on same cell, same Angle of Arrival + +An example is provided here for a scenario where the test case require the UE to report SS-RSRP for the same cell at two different levels, with the signal arriving from the same direction. The Angle of Arrival may be within the UE spherical coverage, or from Rx Beam peak direction. + +$$\text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP1} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} = \text{Applied SSB\_RP2} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP2} - \text{Applied SSB\_RP1}$$ + +where: + +Applied SSB\_RP1 and Applied SSB\_RP2 are specified in the test case, either directly as Es or derived from Noc and Es/Noc, and are in dBm per subcarrier + +It can be seen that UE Spherical coverage gain midpoint and UE gain G midpoint cancel out for this relative measurement, as they remain the same for a signal from the same Angle of Arrival. + +$$\text{Reported SS-RSRP2} - \text{Reported SS-RSRP1} = \text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} \pm \text{UE accuracy}$$ + +where: + +UE accuracy is the relative accuracy from the core requirement referred to in A.2.6.1 + +#### A.2.6.4 Relative RSRP, 2 intra-frequency cells, same Angle of Arrival + +An example is provided here for a scenario where the test case require the UE to report SS-RSRP for two different cells, with the signals arriving from the same direction. The Angle of Arrival may be within the UE spherical coverage, or from Rx Beam peak direction. + +$$\text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP1} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} = \text{Applied SSB\_RP2} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP2} - \text{Applied SSB\_RP1}$$ + +where: + +Applied SSB\_RP1 and Applied SSB\_RP2 are specified in the test case, either directly as Es or derived from Noc and Es/Noc, and are in dBm per subcarrier + +It can be seen that UE Spherical coverage gain midpoint and UE gain G midpoint cancel out for this relative measurement, as they are the same for signals from the same Angle of Arrival. + +$$\text{Reported SS-RSRP2} - \text{Reported SS-RSRP1} = \text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} \pm \text{UE accuracy}$$ + +where: + +UE accuracy is the relative accuracy from the core requirement referred to in A.2.6.1 + +#### A.2.6.5 Relative RSRP, 2 inter-frequency cells, same Angle of Arrival + +[FFS] + +#### A.2.6.6 Relative RSRP, 2 cells, different Angles of Arrival + +Examples are provided here for scenarios where the test case requires the UE to report SS-RSRP for two different cells, with the signals arriving from different directions. + +For both Angles of Arrival from UE spherical coverage directions: + +$$\text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP1} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} = \text{Applied SSB\_RP2} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP2} - \text{Applied SSB\_RP1}$$ + +where: + +Applied SSB\_RP1 and Applied SSB\_RP2 are specified in the test case, either directly as Es or derived from Noc and Es/Noc, and are in dBm per subcarrier + +For the nominal values, UE Spherical coverage gain midpoint and UE gain G midpoint cancel out for this relative measurement. For the variations, UE gain variation cancels out as the same value affects both cells, but Spherical coverage gain variation applies separately to each Angle of Arrival. + +$$\text{Reported SS-RSRP2} - \text{Reported SS-RSRP1} = \text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} \pm \text{Spherical coverage gain variation}_{\text{AoA1}} \pm \text{Spherical coverage gain variation}_{\text{AoA2}} \pm \text{UE accuracy}$$ + +where: + +Spherical coverage gain variationAoA1 is derived from Refsens and Spherical coverage, as in Figure A.2.1.2-1 + +Spherical coverage gain variationAoA2 is derived from Refsens and Spherical coverage, as in Figure A.2.1.2-1 + +UE accuracy is the relative accuracy from the core requirement referred to in A.2.6.1 + +For one Angle of Arrival from UE spherical coverage directions, and one from Rx Beam peak direction: + +$$\text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP1} + \text{UE Spherical coverage gain midpoint} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} = \text{Applied SSB\_RP2} + \text{UE gain G midpoint}$$ + +$$\text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} = \text{Applied SSB\_RP2} - \text{Applied SSB\_RP1} - \text{UE Spherical coverage gain midpoint}$$ + +where: + +Applied SSB\_RP1 and Applied SSB\_RP2 are specified in the test case, either directly as Es or derived from Noc and Es/Noc, and are in dBm per subcarrier + +UE Spherical coverage gain midpoint in dB is derived as (UE Refsens - UE Spherical coverage)/2 + +For the nominal values, UE gain G midpoint cancels out for this relative measurement, but UE Spherical coverage gain midpoint applies to one Angle of Arrival. For the variations, UE gain variation cancels out as the same value affects both cells, but Spherical coverage gain variation applies to one Angle of Arrival. + +$$\text{Reported SS-RSRP2} - \text{Reported SS-RSRP1} = \text{UE-measured SS-RSRP2}_{\text{nom}} - \text{UE-measured SS-RSRP1}_{\text{nom}} \pm \text{Spherical coverage gain variation}_{\text{AoA1}} \pm \text{UE accuracy}$$ + +where: + +Spherical coverage gain variationAoA1 is derived from Refsens and Spherical coverage, as in Figure A.2.1.2-1 + +UE accuracy is the relative accuracy from the core requirement referred to in A.2.6.1 + +## A.2.6.7 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- UE-measured SS-RSRPnom is calculated using the relevant method in A.2.6.2 to A.2.6.6 +- The range of SS-RSRP reported values is calculated using the relevant methods in A.2.6.2 to A.2.6.6 + +## A.2.7 Intra-frequency cells without AWGN, same Angle of Arrival + +### A.2.7.1 Test system + +In a practical test system running a test case where Intra-frequency cells come from the same Angle of Arrival, the level uncertainties for all cells will be highly correlated. If the test case has applied AWGN, it will specify Noc and Es/Noc, and the absolute uncertainty for applied AWGN will be the dominant contribution to the overall Es uncertainty for each cell. As AWGN is common to all cells on that frequency, the correlation is already included. + +If the test case does not have applied AWGN, it will specify $E_s$ for each cell, with an absolute $E_s$ uncertainty for each cell. The method of handling the effect of correlation in the Test Tolerance analysis is given in A.2.7.2 and A.2.7.3. + +## A.2.7.2 Calculation method for $E_s/I_{ot}$ at UE baseband + +An example is provided here for a scenario with two intra-frequency cells, without applied AWGN. SSB $E_s/I_{ot}$ at UE baseband is calculated for Cell 1. Interference to Cell 1 comes from the UE internal noise and from Cell 2. The values are chosen for illustration, and not taken from any specific test case. + +$$\text{Cell 1 SSB } E_s/I_{ot_{BB}} = 10\text{Log}_{10}((\text{Cell 1 SSB power}) / (\text{UE internal noise} + \text{Cell 2 SSB power}))$$ + +Where UE internal noise, Cell 1 power and Cell 2 power are linear powers in W, per subcarrier. + +![Figure A.2.7.2-1: Example Es/IotBB scenario, two intra-frequency cells. A pie chart shows the power distribution: Cell 1 (56.5%, light blue), Cell 2 (28.3%, light green), and UE internal noise (15.2%, grey). A legend box lists the power values: Cell 1: 0.139 pW/SCS, Cell 2: 0.070 pW/SCS, UE internal noise: 0.037 pW/SCS.](45fba45707b417219df161f8bce0f75a_img.jpg) + +| Component | Power (pW/SCS) | Percentage | +|-------------------|----------------|------------| +| Cell 1 | 0.139 | 56.5% | +| Cell 2 | 0.070 | 28.3% | +| UE internal noise | 0.037 | 15.2% | + +Figure A.2.7.2-1: Example Es/IotBB scenario, two intra-frequency cells. A pie chart shows the power distribution: Cell 1 (56.5%, light blue), Cell 2 (28.3%, light green), and UE internal noise (15.2%, grey). A legend box lists the power values: Cell 1: 0.139 pW/SCS, Cell 2: 0.070 pW/SCS, UE internal noise: 0.037 pW/SCS. + +**Figure A.2.7.2-1: Example $E_s/I_{ot_{BB}}$ scenario, two intra-frequency cells** + +In this case, the calculation gives $\text{Cell 1 SSB } E_s/I_{ot_{BB}} = 10\text{Log}_{10}(0.139 / (0.037 + 0.070)) = \mathbf{1.14\text{dB}}$ + +The presence of UE internal noise also affects the calculation of $E_s/I_{ot}$ sensitivity factors in the Test Tolerance analysis. The UE internal noise is a fixed (worst) value, being based on the UE minimum requirement, and is taken into account in the scaling which uses linear powers: + +- Cell 1 SSB $E_s/I_{ot_{BB}}$ sensitivity to Cell 1 $E_s = +1.000$ +- Cell 1 SSB $E_s/I_{ot_{BB}}$ sensitivity to Cell 2 $E_s = -\text{Cell 2 SSB power} / (\text{UE internal noise} + \text{Cell 2 SSB power})$ . In this example, $(0.070 / (0.037 + 0.070)) = -0.651$ + +A positive sensitivity factor is used where an increase in the quantity produces an increase in Cell 1 SSB $E_s/I_{ot_{BB}}$ , for example increasing Cell 1 $E_s$ . A negative sensitivity factor is used where an increase in the quantity produces a decrease in Cell 1 SSB $E_s/I_{ot_{BB}}$ , for example increasing Cell 2 $E_s$ . The sensitivity factors are used to scale the uncertainties. + +Where the uncertainties are correlated, as here, they are added arithmetically and the sign affects the result. In this example, increasing Cell 1 $E_s$ increases the Cell 1 SSB $E_s/I_{ot_{BB}}$ , but the correlated increase in Cell 2 $E_s$ decreases the Cell 1 SSB $E_s/I_{ot_{BB}}$ . The overall effect is smaller, and depends on the ratios of linear powers. + +## A.2.7.3 Calculation method for Applied $I_o$ + +An example is provided here for a scenario with two intra-frequency cells, without applied AWGN. $I_o$ applied to the UE is the arithmetic sum of linear powers in the channel bandwidth. UE internal noise is not counted, as it is not applied to the UE. The values are chosen for illustration, and not taken from any specific test case. + +$$\text{Channel } I_o = 10\text{Log}_{10}(\text{Cell 1 power} + \text{Cell 2 power}) + 10\text{Log}_{10}(N_{RB\_TC} \times 12)$$ + +where: + +Cell 1 power and Cell 2 power are linear powers in W, per subcarrier + +$N_{RB\_TC}$ is the number of PRBs allocated in the test case (not necessarily equal to the number of PRBs in the channel bandwidth) + +12 is the number of subcarriers in a PRB + +![Figure A.2.7.3-1: Example Io scenario, two intra-frequency cells. A pie chart shows Cell 1 at 66.7% (cyan) and Cell 2 at 33.3% (green). A text box indicates Cell 1: 0.139 pW/SCS and Cell 2: 0.070 pW/SCS.](9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg) + +| | +|----------------------| +| Cell 1: 0.139 pW/SCS | +| Cell 2: 0.070 pW/SCS | + +Figure A.2.7.3-1: Example Io scenario, two intra-frequency cells. A pie chart shows Cell 1 at 66.7% (cyan) and Cell 2 at 33.3% (green). A text box indicates Cell 1: 0.139 pW/SCS and Cell 2: 0.070 pW/SCS. + +**Figure A.2.7.3-1: Example Io scenario, two intra-frequency cells** + +With 24 PRBs allocated, the example gives $I_o = 10\text{Log}_{10} ((0.139 + 0.070) \times 10^{-9}) + 10\text{Log}_{10} (24 \times 12) = -72.2\text{dBm}$ + +$I_o$ sensitivity factors in the Test Tolerance analysis are based on linear powers: + +- $I_o$ sensitivity to Cell 1 $E_s = \text{Cell 1 power} / (\text{Cell 1 power} + \text{Cell 2 power})$ . In this example, $(0.139 / (0.139 + 0.070)) = +0.667$ +- $I_o$ sensitivity to Cell 2 $E_s = \text{Cell 2 power} / (\text{Cell 1 power} + \text{Cell 2 power})$ . In this example, $(0.070 / (0.139 + 0.070)) = +0.333$ + +All the sensitivity factors are positive, as an increase in the quantity produces an increase in $I_o$ . The sensitivity factors are used to scale the uncertainties. + +Where the uncertainties are correlated, as here, they are added arithmetically, and the sign affects the result. In this example increasing Cell 1 $E_s$ increases $I_o$ , and the correlated increase in Cell 2 $E_s$ also increases $I_o$ . The overall effect of scaling adds up to 1, as expected. + +## A.2.7.4 Principles for Test Tolerance analysis + +The following principles shall be followed in the test case analysis: + +- For Intra-frequency cells from the same Angle of Arrival without AWGN, $E_s/I_{ot_{BB}}$ is calculated using the method in A.2.7.2. +- For Intra-frequency cells from the same Angle of Arrival without AWGN, $E_s/I_{ot_{BB}}$ sensitivity factors are calculated using the method in A.2.7.2. +- For Intra-frequency cells from the same Angle of Arrival without AWGN, $I_o$ is calculated using the method in A.2.7.3. +- For Intra-frequency cells from the same Angle of Arrival without AWGN, $I_o$ sensitivity factors are calculated using the method in A.2.7.3. + +--- + +## A.3 Test Tolerance analysis templates for radiated test cases awaiting completion + +Test Tolerance analyses for Radiated testing listed below are not yet complete, but contain the main features for the test cases covered and can be used as templates. For each analysis, the missing aspects are listed. + +The analysis documents (and spreadsheets where applicable) are included in the present document as zip files with “draft” at the end of the filename. When the test case analyses are complete, the draft versions and listing in this clause should be removed. + +38.533 5.3.2.2.1+5.3.2.2.2+7.3.2.2.1+7.3.2.2.2 TT draft + +*Editor's note: This test tolerance analysis is incomplete. The following aspects are missing:* + +- Settable window for first preamble uplink power and the uplink calibration process* +- Derivation of test requirement for absolute uplink power after uplink calibration process* +- Derivation of test requirement for relative uplink power* +- The uncertainty value and test requirement for PRACH timing are in [ ] and not yet finalised* +- The results of the TT analysis are provisional until the corresponding MU values are agreed* + +--- + +## A.4 Design of radiated test cases defined in TS 38.533 + +The design of radiated test cases defined in TS 38.533 is more challenging than for conducted test cases, because the over-the-air path loss reduces the downlink power seen by the UE, and reduces the uplink power received by the test system. + +The achievable downlink power in a practical test system is restricted, and there is less dB range between the lowest and highest power that can be applied within the UE Core requirement side conditions. + +The range of uplink power that can be measured by a practical test system is also restricted, by signal-to-noise ratio considerations at the low end, and by the UE output power at the high end. + +For both downlink and uplink, the achievable dB range is most restricted when the signal arrives from the UE Spherical coverage direction. In a test case it is further restricted by downlink power level uncertainty or uplink power measurement uncertainty, which are both larger for radiated signals than for conducted signals. This Annex considers the effect of restricted dB range on radiated RRM test case design. + +### A.4.1 Downlink considerations + +#### A.4.1.1 Side conditions for Rx Beam Peak angle of arrival + +Side conditions for Rx Beam Peak angle of arrival are less stringent than for Spherical Coverage angle of arrival. They are not directly analysed here, but the same principles apply as for Spherical Coverage in clause A.4.1.2. + +#### A.4.1.2 Side conditions for Spherical Coverage angle of arrival + +As an example, consider a test case where the UE makes measurements on the downlink signal, for example in Event-triggered reporting. Some side condition values are band-dependent, and also depend on whether the cell being measured is intra-frequency or inter-frequency. An adverse case is chosen for illustration: + +- Spherical Coverage angle of arrival +- Inter-frequency +- UE Power Class 3 +- Band n259 + +- Maximum multi-band relaxation +- Full RB allocation +- UE is required to make measurements, so side conditions apply + +The scenario is however best case on two points: + +- Applied Es only, without Noc (only UE internal noise) +- Only one cell on the frequency (no other intra-frequency cells) + +![Figure A.4.1.2-1: Example side conditions when UE is making measurements. This is a vertical scale diagram showing power levels in dBm/SCS. The scale ranges from -110 to -80 dBm/SCS. Key levels include: -50 dBm/Ch BW (Maximum Io side condition), -87 to -85 dBm/SCS (Applied level range), -93.7 dBm/SCS (Minimum SSB_RP side condition, Inter-f), and -95.7 dBm/SCS (Minimum SSB_RP side condition, Intra-f). The diagram also shows the 'Applied SSB_RP dBm/SCS' range and 'Test System DL absolute uncertainty ±6dB'.](faff5ea2bac20b616b62b35da5a5d67c_img.jpg) + +Maximum Io side condition +-50dBm/Ch BW + +Scale for Max #RBs: + $+10\log_{10}(66\text{RBs} \times 12\text{ SC}) = +29.0\text{dB}$ + +Applied level range: +-87 to -85dBm/SCS + +Minimum SSB\_RP side condition, Spherical coverage +(-93.7dBm+0.7dB)/SCS +(Inter-f, PC3, n259, $\Delta\text{MB}_s$ ) + +Minimum SSB\_RP side condition, Spherical coverage +(-95.7dBm+0.7dB)/SCS +(Intra-f, PC3, n259, $\Delta\text{MB}_s$ ) + +Test System DL absolute uncertainty $\pm 6\text{dB}$ + +Applied SSB\_RP dBm/SCS + +Figure A.4.1.2-1: Example side conditions when UE is making measurements. This is a vertical scale diagram showing power levels in dBm/SCS. The scale ranges from -110 to -80 dBm/SCS. Key levels include: -50 dBm/Ch BW (Maximum Io side condition), -87 to -85 dBm/SCS (Applied level range), -93.7 dBm/SCS (Minimum SSB\_RP side condition, Inter-f), and -95.7 dBm/SCS (Minimum SSB\_RP side condition, Intra-f). The diagram also shows the 'Applied SSB\_RP dBm/SCS' range and 'Test System DL absolute uncertainty ±6dB'. + +Figure A.4.1.2-1: Example side conditions when UE is making measurements + +It can be seen that when uncertainties are taken into account (an indicative value of $\pm 6\text{dB}$ is used), the applied level range can be from $-87\text{dBm/SCS}$ to $-85\text{dBm/SCS}$ , a range of only $2\text{dB}$ . This is very restrictive for the test case design. + +### A.4.1.3 Test case design options to increase downlink dB range + +A number of options are available to increase the dB range of the applied downlink signal, if necessary. For a specific test case, only some may be available, for example in a test case such as Radio Link Monitoring, it would not be possible to use applied Es only, because the test case relies on a well-defined SNR at the UE baseband. + +**Table A.4.1.3-1: Options to increase downlink dB range** + +| Option | Applicability | Comments | +|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| Reduce number of allocated RBs | All Test cases | 120kHz SSB SCS, use 24RBs
240kHz SSB SCS, use 48RBs
Allocated RBs must include CORESET | +| Use applied Es only, without applied Noc | Test cases where $E_s/I_{ot_{SSB}}$ requirement is to be $\geq$ defined value | Maximises Es contribution to Io. Not suitable for test cases where $E_s/I_{ot_{SSB}}$ is intended as well-defined SNR. | +| If applied Noc is used, reduce margin above UE internal noise | Test cases where $E_s/I_{ot_{SSB}}$ requirement is to be $\geq$ defined value | Not suitable for test cases where $E_s/I_{ot_{SSB}}$ is intended as well-defined SNR. | +| Use time-division multiplexing with SSB#0, SSB#1 | Test cases using SSB#0, SSB#1 | Avoids intra-frequency interference and degradation of $E_s/I_{ot_{SSB}}$ | +| Use Rx Beam Peak AoA instead of Spherical Coverage | Test cases where using Rx Beam Peak for one or both AoA, instead of Spherical Coverage, would provide adequate test coverage | Adequate test coverage may be achievable across several Test cases | +| Allow Io > -50dBm | Test cases where measurement side conditions are not applicable | Test system may not be able to deliver >-50dBm | +| Restrict to 120kHz SSB SCS | Test cases with a 240kHz SSB SCS Configuration | Adequate test coverage of 120kHz and 240kHz SSB SCS may be achievable across several Test cases | + +![A vertical scale diagram illustrating the downlink dB range for SSB_RP. The scale ranges from -110 to -80 dBm/SCS. It shows various conditions and adjustments: Maximum Io side condition at -50dBm/Ch BW; Scale for Max #RBs for 66RBs (+29.0dB) and 24RBs (+24.6dB); a reduction to 24RBs (+4.4dB); Test System DL absolute uncertainty (±6dB); Applied level range from -87 to -85dBm/SCS; Minimum SSB_RP side conditions for spherical coverage (-93.7dBm and -95.7dBm); Intra-freq: +2dB; and Rx Beam Peak (+12.8dB).](e466e4c4fb08567a109bb959a765225c_img.jpg) + +Maximum Io side condition +-50dBm/Ch BW + +Scale for Max #RBs: + $+10\log_{10}(66\text{RBs} \times 12\text{ SC}) = +29.0\text{dB}$ + +Scale for Max #RBs: + $+10\log_{10}(24\text{RBs} \times 12\text{ SC}) = +24.6\text{dB}$ + +Reduce to 24RBs: +4.4dB + +Test System DL absolute uncertainty $\pm 6\text{dB}$ + +Applied level range: +-87 to -85dBm/SCS { + +Minimum SSB\_RP side condition, Spherical coverage +(-93.7dBm+0.7dB)/SCS +(Inter-f, PC3, n259, $\Delta\text{MB}_s$ ) + +Test System DL absolute uncertainty $\pm 6\text{dB}$ + +Intra-freq: +2dB + +Minimum SSB\_RP side condition, Spherical coverage +(-95.7dBm+0.7dB)/SCS +(Intra-f, PC3, n259, $\Delta\text{MB}_s$ ) + +Rx Beam Peak: ++12.8dB (n259) + +**Applied SSB\_RP dBm/SCS** + +-80 + +-90 + +-100 + +-110 + +A vertical scale diagram illustrating the downlink dB range for SSB\_RP. The scale ranges from -110 to -80 dBm/SCS. It shows various conditions and adjustments: Maximum Io side condition at -50dBm/Ch BW; Scale for Max #RBs for 66RBs (+29.0dB) and 24RBs (+24.6dB); a reduction to 24RBs (+4.4dB); Test System DL absolute uncertainty (±6dB); Applied level range from -87 to -85dBm/SCS; Minimum SSB\_RP side conditions for spherical coverage (-93.7dBm and -95.7dBm); Intra-freq: +2dB; and Rx Beam Peak (+12.8dB). + +Figure A.4.1.3-1: Example illustration of selected options to increase downlink dB range + +## Annex B: Acceptable uncertainty of test system for test cases defined in TS 38.521-2 for radiative testing + +This annex contains suggested uncertainties for each test case in TS 38.521-2. + +### B.1 Uncertainty budget calculation principle + +Three permitted test methodologies, DFF, IFF and NFTF, have been identified for UE RF FR2 test cases defined in TS 38.521-2. + +This Annex is deriving Total expanded Measurement Uncertainties per test case for each test methodology. + +Threshold MU is equivalent to Total expanded uncertainty of the reference methodology which has been defined as IFF. + +If the Total expanded Measurement Uncertainty per test case of a permitted test method is lower than or equal to the threshold MU, then that test method is applicable to the respective test cases defined in TS 38.521-2. + +#### B.1.1 Uncertainty budget calculation principle for DFF + +The uncertainty tables should be presented with two stages: + +- Stage 1: the calibration of the absolute level of the DUT measurement results is performed by means of using a calibration antenna whose absolute gain is known at the frequencies of measurement +- Stage 2: the actual measurement with the DUT as either the transmitter or receiver is performed. + +The MU budget should comprise the following headings: + +- 1) The uncertainty source. Compile a complete list of the individual measurement uncertainty elements that contribute to a measurement +- 2) Determine the maximum value of each uncertainty +- 3) Determine the distribution of each uncertainty (rectangular, U-shaped, etc.), +- 4) Calculate (if necessary) the standard deviation of each uncertainty, $u_i$ , (NOTE 1) for each uncertainty element, +- 5) Convert the units (if necessary) of each uncertainty element into the chosen unit, i.e., dB, +- 6) Combine ALL the standard uncertainties by the root-sum-squares method to derive the 'combined standard uncertainty', +- 7) Multiply the resulting combined standard uncertainty by an expansion factor ' $k$ ' to derive the 'expanded uncertainty' for a given confidence level. All expanded uncertainties are quoted to 95% confidence level, so $k$ is taken as 1.96. This gives 95% confidence that the true value is within 1.96 times the combined standard uncertainty of the measured value to derive the 'expanded uncertainty'. +- 8) Any systematic errors are added to the expanded uncertainty to derive the 'total expanded uncertainty', i.e., + +$$u_{c, \text{total expanded}} = u_{c, \text{expanded}} + u_{c, \text{systematic}} = 1.96 \sqrt{\sum u_i^2} + \sum u_{i, \text{systematic}}$$ + +NOTE 1: The standard deviation from a data set of $N$ samples is defined as + +$$u_i = \sqrt{\frac{1}{N-1} \sum_{k=1}^N |s_k - \bar{s}|^2}$$ + +where $s_k$ are the respective sample results and $\bar{s}$ the mean of all $N$ samples. For an uncertainty $u_i$ in dB, the dB values (instead of the linear powers) of $s_k$ and $\bar{s}$ are used. + +## B.1.2 Uncertainty budget calculation principle for IFF + +The same as defined in B.1.1. + +## B.1.3 Uncertainty budget calculation principle for NFTF + +The same as defined in B.1.1 with the exception of Stage 2, only the measurement of the DUT transmitter is performed. + +# B.2 Measurement error contribution descriptions + +## B.2.1 Measurement error contribution descriptions for DFF + +### B.2.1.1 Positioning misalignment + +This contribution originates from the misalignment of the testing direction and the beam peak direction of the measurement antenna due to imperfect rotation operation. The pointing misalignment may happen in both azimuth and vertical directions and the effect of the misalignment depends highly on the beam width of the beam under test. The same level of misalignment results in a larger measurement error for a narrower beam. + +### B.2.1.2 Measure distance uncertainty + +The cause of this uncertainty contributor is due to the reduction of distance between the measurement antenna and the DUT. If the distance of separation is $2D^2/\lambda$ based on $D$ being the entire device size, then the phase variation is 22.5deg. Whether this is the minimum acceptable criteria of phase taper over the entire DUT is FFS and shall be assessed during final MU definition for the test method. Any reduction in the distance of separation increases the phase variation and creates an error which is DUT dependant. Determination of limit of the error shall be done during final MU definition for the test method. + +### B.2.1.3 Quality of quiet zone + +The quality of the quiet zone procedure characterizes the quiet zone performance of the anechoic chamber, specifically the effect of reflections within the anechoic chamber including any positioners and support structures. The MU term additionally includes the amplitude variations effect of offsetting the directive antenna array inside a DUT from the centre of the quiet zone as well as the directivity MU, i.e., the variation of antenna gains in the different direct line-of-sight links. An additional MU term related to phase variation and phase ripple effects which depends on measurement distance is FFS, and shall be assessed during final MU definition for the test method. This might require an augmentation of the quality of the quiet zone validation procedure. + +### B.2.1.4 Mismatch + +Mismatch uncertainty occurs when; + +- Changing the signal path between the measurement and calibration procedure +- Evaluating the insertion loss of a signal path + +The mismatch uncertainty for a system consisting of a generator, a load and a component in between is defined as + +$$\text{Mismatch contribution (standard deviation)} = \frac{|\Gamma_{\text{generator}}| \cdot |\Gamma_{\text{load}}| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2} \cdot 11.5} \text{ dB}$$ + +Where $\Gamma$ denotes the reflection coefficient and $S_{21}$ is the transmission coefficient, both in linear voltage ratios. + +For a cascade of several components, the interactions between all components have to be evaluated. For example, for four devices in a row (shown in Figure B.2.1.4-1) the following contributions have to be accounted for: AB, BC, CD, ABC, BCD, ABCD. The term ABCD represents the interaction between A and D (generator and load) with the components B and C in between. + +![Figure B.2.1.4-1: Cascade of components. A block diagram showing four rectangular blocks labeled A, B, C, and D connected in series from left to right.](f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg) + +Figure B.2.1.4-1: Cascade of components. A block diagram showing four rectangular blocks labeled A, B, C, and D connected in series from left to right. + +**Figure B.2.1.4-1: Cascade of components** + +The combined mismatch uncertainty is given by the root sum square of the individual contributions: + +$$\text{combined mismatch uncertainty} = \sqrt{(AB)^2 + (BC)^2 + (CD)^2 + (ABC)^2 + (BCD)^2 + (ABCD)^2}$$ + +In an optimized test procedure, the overall mismatch uncertainty is smaller when matching pairs of mismatches exist in the calibration and measurement stage since these pairs cancel each other out. Figure B.2.1.4-2 displays a calibration setup, where device D is replaced by device F. The mismatch contributions for this path are AB, BC, CE, ABC, BCE and ABCE. For a result based on the measurement and calibration stage, the mismatch contributions AB, BC, and ABC are matching pairs as they occur both in the measurement and calibration stage. Thus, they can be eliminated [11], and the system mismatch uncertainty is obtained as $\sqrt{(CD)^2 + (CE)^2 + (BCD)^2 + (BCE)^2 + (ABCD)^2 + (ABCE)^2}$ + +![Figure B.2.1.4-2: Sketch of a calibration path. A block diagram showing four rectangular blocks labeled A, B, C, and E connected in series from left to right.](d16e5a3857155ee2837d851305ee8036_img.jpg) + +Figure B.2.1.4-2: Sketch of a calibration path. A block diagram showing four rectangular blocks labeled A, B, C, and E connected in series from left to right. + +**Figure B.2.1.4-2: Sketch of a calibration path** + +In the following, an example mismatch uncertainty calculation for a TX/RX patch from the measurement equipment to the measurement antenna is performed for a frequency of 43.5GHz. The example path under investigation consists of four SPDT switches, one SP6T switch and one DPDT switch and microwave cable interconnects with PC2.4 mm connectors. The attenuation and reflectance of typical components suitable for frequencies ranging up to 43.5 GHz have been considered in the calculation of the mismatch uncertainty. + +Figure B1.1.4-3 shows a sample system setup for an EIRP/EIS test case with rather simple complexity of the switch box similar to a current sub 6GHz test setup. It should be noted that the switch unit is significantly less complex than a state-of-the-art switch unit currently used for conformance tests. + +![Block Diagram of an EIRP/EIS test case showing components from the gNB to the antenna. The diagram includes a gNB connected via cable C1 to a SwitchUnit. The SwitchUnit contains various switches (K1, K2, K3, K4, K5, K6, K7, K8, K9, K10) and feedthroughs (F1, F2, F3). The output of the SwitchUnit is connected via cable C9 to a Chamber, which contains a Meas. Ant. The diagram also shows various cables (C2, C3, C4, C5, C6, C7, C8, C10) and connectors (THETA, PHI).](c07e21a8d65991db04263322f859c94f_img.jpg) + +Block Diagram of an EIRP/EIS test case showing components from the gNB to the antenna. The diagram includes a gNB connected via cable C1 to a SwitchUnit. The SwitchUnit contains various switches (K1, K2, K3, K4, K5, K6, K7, K8, K9, K10) and feedthroughs (F1, F2, F3). The output of the SwitchUnit is connected via cable C9 to a Chamber, which contains a Meas. Ant. The diagram also shows various cables (C2, C3, C4, C5, C6, C7, C8, C10) and connectors (THETA, PHI). + +**Figure B.2.1.4-3: Block Diagram of an EIRP/EIS test case with components from the gNB to the antenna (only portion of switch unit shown)** + +**Table B.2.1.4-1: comprises the reflection and transmission properties of the components of the example path at a frequency of 43.5 GHz** + +| Device / Component | VSWR | Transmission (dB) | Identifier in Figure B.2.1.4-3 | Additional Comment/ Assumption | +|--------------------|------|-------------------|--------------------------------|---------------------------------| +| System Simulator | 3.5 | | gNB | | +| Cable | 1.5 | -5.38 | C1 | Length: 1.5m
Loss: 3.59dB/m | +| Cable | 1.5 | -0.61 | C2, C3, C4, C5, C6, C7, C8 | Length: 0.17m
Loss: 3.59dB/m | +| Cable | 1.5 | -7.18 | C9, C10 | Length: 2.0m
Loss: 3.59dB/m | +| Feedthrough | 1.3 | -0.66 | F1, F2, F3 | | +| SPDT switch | 1.9 | -1.10 | K1, K3, K5, K7 | | +| SP6T switch | 2.2 | -1.20 | K9 | | +| Transfer switch | 2.0 | -1.10 | K10 | | +| Antenna | 2.0 | | Meas. Ant. | | + +The calculation of the overall mismatch uncertainty for a frequency of 43.5 GHz results in a value of 2.7 dB for the standard deviation, i.e., the expanded uncertainty is 5.3 dB. + +Figure B.2.1.4-4 depicts a possible calibration for a part of the setup. + +![Block Diagram of the calibration stage. It shows a VNA connected via cable C1 to a SwitchUnit. The SwitchUnit contains various switches (K1, K2, K3, K4, K5, K6, K7, K8, K9, K10) and feedthroughs (F1, F2, F3). The output of the SwitchUnit is connected via cable C9 to a Chamber, which contains a Meas. Ant. The diagram also shows various cables (C2, C3, C4, C5, C6, C7, C8, C10) and connectors (THETA, PHI).](99e9a4791d2e5bb5afa1bb884652d4db_img.jpg) + +Block Diagram of the calibration stage. It shows a VNA connected via cable C1 to a SwitchUnit. The SwitchUnit contains various switches (K1, K2, K3, K4, K5, K6, K7, K8, K9, K10) and feedthroughs (F1, F2, F3). The output of the SwitchUnit is connected via cable C9 to a Chamber, which contains a Meas. Ant. The diagram also shows various cables (C2, C3, C4, C5, C6, C7, C8, C10) and connectors (THETA, PHI). + +**Figure B.2.1.4-4: Block Diagram of the calibration stage** + +For the VNA a return loss of 30 dB is assumed after a full two-port calibration. The calculation of the system mismatch uncertainty applying the elimination of matching pairs results in a value of 1.0 dB (standard deviation) with an expanded value of 1.9 dB. + +Since the overall mismatch uncertainty value is already a standard deviation, which is RSS of values divided by the divisor ( $\sqrt{2}$ ), the overall mismatch uncertainty value should be divided by actual divisor 1 when calculating total mismatch. + +### B.2.1.5 Standing Wave Between the DUT and measurement antenna + +This uncertainty term is related to the amplitude ripple coming from the standing waves between the DUT and measurement antenna. If this term is not considered to be negligible one method to obtain this value is to slide the DUT $\lambda/4$ towards the measurement antenna while measuring the amplitude. The uncertainty term can be derived by performing the standard deviation on the results. + +### B.2.1.6 Uncertainty of the RF power measurement equipment + +The receiving device is used to measure the received signal level in the EIRP tests as an absolute level. These receiving devices are spectrum analysers, communication analysers, or power meters. The uncertainty value will be indicated in the manufacturer's data sheet. It needs to be ensured that appropriate manufacturer's uncertainty contributions are specified for the settings used such as bandwidth and absolute level. If a power meter is used zero offset, zero drift and measurement noise need to be included. + +### B.2.1.7 Phase curvature + +This contribution originates from the finite far field measurement distance, which causes phase curvature across the antenna of UE/reference antenna. At a measurement distance of $2D^2/\lambda$ the phase curvature is 22.5 degrees. The impact of this factor shall be assessed during final MU definition for the test method. + +### B.2.1.8 Amplifier uncertainties + +Any components in the setup can potentially introduce measurement uncertainty. It is then needed to determine the uncertainty contributors associated with the use of such components. For the case of external amplifiers, the following uncertainties should be considered but the applicability is contingent to the measurement implementation and calibration procedure. + +- Stability + - An uncertainty contribution comes from the output level stability of the amplifier. Even if the amplifier is part of the system for both measurement and calibration, the uncertainty due to the stability shall be considered. This uncertainty can be either measured or determined by the manufacturers' data sheet for the operating conditions in which the system will be required to operate. +- Linearity + - An uncertainty contribution comes from the linearity of the amplifier since in most cases calibration and measurements are performed at two different input/output power levels. This uncertainty can be either measured or determined by the manufacturers' data sheet. +- Noise Figure + - When the signal goes into an amplifier, noise is added so that the SNR at the output is reduced with regard to the SNR of the signal at the input. This added noise introduces error on the signal which affects the Error Rate of the receiver thus the EVM (Error Vector Magnitude). An uncertainty can be calculated through the following formula: + +$$\varepsilon_{EVM} = 20 \log_{10} \text{mJ} + 10^{\frac{-\text{SNR}}{20}} \text{J}$$ + +- Where SNR is the signal to noise ratio in dB at the signal level used during the sensitivity measurement. +- Mismatch + - If the external amplifier is used for both stages, measurement and calibration the uncertainty contribution associated with it can be considered systematic and constant -> 0dB. If it is not the case, the mismatch uncertainty at its input and output shall be either measured or determined by the method described in [12]. +- Gain + - If the external amplifier is used for both stages, measurement and calibration the uncertainty contribution associated with it can be considered systematic and constant -> 0dB. If it is not the case, this uncertainty shall be considered. + +### B.2.1.9 Random uncertainty + +This contribution is used to account for all the unknown, unquantifiable, etc. uncertainties associated with the measurements. + +Random uncertainty MU contributions are normally distributed. + +The random uncertainty term, by definition, cannot be measured, or even isolated completely. However, past system definitions provide an empirical basis for a value. Current LTE SISO OTA measurements have random uncertainty contributions of ~0.2dB. A value of 0.5dB is suggested due to increased sensitivity to random effects in more complex, higher frequency NR test systems. + +### B.2.1.10 Influence of the XPD + +This factor takes into account the uncertainty caused due to the finite cross polar discrimination (XPD) between the two polarization ports of the measurement probe. The XPD of the probe antenna shall be take into account during final MU definition for the test method. + +A typical probe antenna can have XPD of 30dB. + +A transmission matrix and calibration setup as shown in Figure B.2.1.10-1 is considered here. Typically, a single-polarized reference antenna with known gain is placed at the centre of the quiet zone and the total attenuation, $L$ , between the reference antenna terminal and the feed antenna terminals is determined as part of the range reference calibration procedure. + +![Figure B.2.1.10-1: Calibration Setup diagram showing a transmission matrix between two antennas. The diagram illustrates the signal paths and attenuation factors (L) between the reference antenna (left) and the probe antenna (right). The reference antenna has two ports, P_OZ,θ and P_OZ,φ, and the probe antenna has two ports, P_Probe,θ and P_Probe,φ. The signal paths are labeled with attenuation factors: L_θθ, L_θφ, L_φθ, and L_φφ. The diagram also shows the polarization states θ and φ for both antennas.](44ffa7f0e6419d046ab4fed0faaf7738_img.jpg) + +The diagram illustrates a calibration setup involving two antennas. On the left, a reference antenna is shown with two ports: $P_{OZ,\theta}$ (top) and $P_{OZ,\phi}$ (bottom). On the right, a probe antenna is shown with two ports: $P_{Probe,\theta}$ (top) and $P_{Probe,\phi}$ (bottom). The signal paths between the ports are labeled with attenuation factors: $L_{\theta\theta}$ (top-left to top-right), $L_{\theta\phi}$ (top-left to bottom-right), $L_{\phi\theta}$ (bottom-left to top-right), and $L_{\phi\phi}$ (bottom-left to bottom-right). The polarization states $\theta$ and $\phi$ are indicated for both antennas. + +Figure B.2.1.10-1: Calibration Setup diagram showing a transmission matrix between two antennas. The diagram illustrates the signal paths and attenuation factors (L) between the reference antenna (left) and the probe antenna (right). The reference antenna has two ports, P\_OZ,θ and P\_OZ,φ, and the probe antenna has two ports, P\_Probe,θ and P\_Probe,φ. The signal paths are labeled with attenuation factors: L\_θθ, L\_θφ, L\_φθ, and L\_φφ. The diagram also shows the polarization states θ and φ for both antennas. + +Figure B.2.1.10-1: Calibration Setup + +Since the reference antenna is considered a single-polarized antenna, the XPD effect is negligible. Since the measurement probe is assumed to be a dual-linearly polarized antenna, leakage from one terminal/polarization to the other, i.e., XPD, needs to be considered. + +The dual-linearly polarized measurement probe has two terminals corresponding to a set of orthogonal polarizations, $\theta$ and $\phi$ which match the orientations of the reference antenna. The most thorough calibration procedure would determine the path losses between the four different combinations of signal paths: $\theta\theta$ , $\theta\phi$ , $\phi\theta$ , and $\phi\phi$ , e.g., the power received by the measurement probe at the $\theta$ polarization/terminal, $P_{\text{Feed},\theta}$ , is attenuated by $L_{\phi\theta}$ with respect to the power delivered to the reference antenna oriented in the $\phi$ polarization and placed in the centre of quiet zone, $P_{\text{QZ},\phi}$ . + +The most common calibration approach, however, is based on calibrating the polarization matched paths in Figure B.2.1.10-1 (thick solid lines), i.e., $\theta\theta$ and $\phi\phi$ . In this case, as illustrated in Figure B.2.1.10-2, the normalized pathlosses $L_{\theta\theta}$ and $L_{\phi\phi}$ are 1 and the pathlosses of the crossed components become the XPD terms of the measurement probe: + +$$\alpha_{\theta\phi} = 10^{\frac{XPD_{\theta\phi}}{10}} \quad (1.1)$$ + +and + +$$\alpha_{\phi\theta} = 10^{\frac{XPD_{\phi\theta}}{10}} \quad (1.2)$$ + +![Figure B.2.1.10-2: Common calibration approach based on calibrating the polarization matched signal paths. The diagram shows four nodes: P_QZ,θ (top left), P_Probe,θ (top right), P_QZ,φ (bottom left), and P_Probe,φ (bottom right). Thick solid lines connect P_QZ,θ to P_Probe,θ (labeled '1') and P_QZ,φ to P_Probe,φ (labeled '1'). Thin lines cross between P_QZ,θ to P_Probe,φ (labeled α_θφ) and P_QZ,φ to P_Probe,θ (labeled α_φθ).](c6e0b9030f9fb81435eaf9cb71532614_img.jpg) + +Figure B.2.1.10-2: Common calibration approach based on calibrating the polarization matched signal paths. The diagram shows four nodes: P\_QZ,θ (top left), P\_Probe,θ (top right), P\_QZ,φ (bottom left), and P\_Probe,φ (bottom right). Thick solid lines connect P\_QZ,θ to P\_Probe,θ (labeled '1') and P\_QZ,φ to P\_Probe,φ (labeled '1'). Thin lines cross between P\_QZ,θ to P\_Probe,φ (labeled α\_θφ) and P\_QZ,φ to P\_Probe,θ (labeled α\_φθ). + +**Figure B.2.1.10-2: Common calibration approach based on calibrating the polarization matched signal paths** + +In the remainder of this analysis, it is assumed that the leakage between the two polarization ports of the measurement probe is assumed to be the same, i.e., $XPD = XPD_{\theta\phi} = XPD_{\phi\theta}$ and $\alpha = \alpha_{\theta\phi} = \alpha_{\phi\theta}$ . + +The normalized powers at the measurement probe terminals can then be written as + +$$P_{\text{Probe},\theta} = P_{\text{QZ},\theta} + \alpha P_{\text{QZ},\phi} \quad (1.3)$$ + +$$P_{\text{Probe},\phi} = P_{\text{QZ},\phi} + \alpha P_{\text{QZ},\theta} \quad (1.4)$$ + +The normalized ratio of total powers at measurement probe and the centre of the quiet zone is therefore + +$$\frac{P_{\text{Probe}}}{P_{\text{QZ}}} = \frac{P_{\text{Probe},\theta} + P_{\text{Probe},\phi}}{P_{\text{QZ},\theta} + P_{\text{QZ},\phi}} = \frac{(P_{\text{QZ},\theta} + P_{\text{QZ},\phi})(1 + \alpha)}{P_{\text{QZ},\theta} + P_{\text{QZ},\phi}} = 1 + \alpha \quad (1.5)$$ + +This simple analysis shows that the XPD of the measurement probe introduces a small error of the total power measured by the measurement probe and that the conservation of measured powers is not guaranteed, i.e., the MU based on the XPD can be expressed as + +$$MU_{XPD} [dB] = 10 \log_{10} (1 + \alpha) = 10 \log_{10} \left( 1 + 10^{\frac{XPD}{10}} \right) \quad (1.6)$$ + +This XPD MU is tabulated for different levels of XPD in Table B.2.1.10-1. + +**Table B.2.1.10-1: XPD MU for different XPD values** + +| XPD [dB] | MU XPD [dB] | +|----------|------------------------| +| -20 | 0.043 | +| -25 | 0.014 | +| -30 | 0.004 | +| -35 | 0.001 | +| -40 | 0.000 | + +When the range reference calibration is based on a full matrix-based approach, i.e., all signal paths are calibrated, the conservation of measured powers is guaranteed. As shown in Figure B.2.1.10-3, the polarization-matched signal paths take into account the leakage of power into the cross paths. + +![Figure B.2.1.10-3: Calibration approach based on calibrating all signal paths. The diagram shows two input ports on the left, P_QZ,θ and P_QZ,φ, and two output ports on the right, P_Probe,θ and P_Probe,φ. The signal from P_QZ,θ splits: a portion (1-α) goes to P_Probe,θ and a portion (α) goes to P_Probe,φ. The signal from P_QZ,φ also splits: a portion (1-α) goes to P_Probe,φ and a portion (α) goes to P_Probe,θ.](8a0a9aa5fac5d73eefb772afd44649f6_img.jpg) + +Figure B.2.1.10-3: Calibration approach based on calibrating all signal paths. The diagram shows two input ports on the left, P\_QZ,θ and P\_QZ,φ, and two output ports on the right, P\_Probe,θ and P\_Probe,φ. The signal from P\_QZ,θ splits: a portion (1-α) goes to P\_Probe,θ and a portion (α) goes to P\_Probe,φ. The signal from P\_QZ,φ also splits: a portion (1-α) goes to P\_Probe,φ and a portion (α) goes to P\_Probe,θ. + +**Figure B.2.1.10-3: Calibration approach based on calibrating all signal paths** + +The powers at the measurement probe can now be written as + +$$P_{Probe,\theta} = (1 - \alpha)P_{QZ,\theta} + \alpha P_{QZ,\phi} \quad (1.7)$$ + +$$P_{Probe,\phi} = (1 - \alpha)P_{QZ,\phi} + \alpha P_{QZ,\theta} \quad (1.8)$$ + +The normalized ratio of total powers at measurement probe and the centre of the quiet zone is then + +$$\frac{P_{Probe}}{P_{QZ}} = \frac{P_{Probe,\theta} + P_{Probe,\phi}}{P_{QZ,\theta} + P_{QZ,\phi}} = \frac{P_{QZ,\theta} + P_{QZ,\phi}}{P_{QZ,\theta} + P_{QZ,\phi}} = 1 \quad (1.9)$$ + +This simple analysis now shows that for a matrix-based calibration of all signal paths the XPD of the measurement probe no longer introduces any error and that the conservation of measured powers is guaranteed, i.e., the MU based on the XPD is 0dB. + +The derivation of the XPD MU based on powers is a more straightforward and less complex approach than with electric fields as attempted in [2]. This annex shows that the same XPD MU result as derived in (1.5) can be derived using electric fields. + +The corresponding signal paths are illustrated in Figure B.2.1.10-4. + +![Diagram showing signal paths for electric fields. Two input ports on the left, E_QZ,θ and E_QZ,φ, are connected to two output ports on the right, E_Probe,θ and E_Probe,φ. The direct paths (θ to θ and φ to φ) are labeled with a gain of 1. The cross paths (θ to φ and φ to θ) are labeled with gains ae^{jb} and ce^{jd}.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +Diagram showing signal paths for electric fields. Two input ports on the left, E\_QZ,θ and E\_QZ,φ, are connected to two output ports on the right, E\_Probe,θ and E\_Probe,φ. The direct paths (θ to θ and φ to φ) are labeled with a gain of 1. The cross paths (θ to φ and φ to θ) are labeled with gains ae^{jb} and ce^{jd}. + +**Figure B.2.1.10-4: Signal paths for electric fields (based on calibrating the polarization matched signal paths)** + +The normalized fields at the measurement probe terminals can then be written as + +$$E_{\text{Probe},\theta} = E_{\text{QZ},\theta} + ce^{jd} E_{\text{QZ},\phi} \quad (1.10)$$ + +$$E_{\text{Probe},\phi} = E_{\text{QZ},\phi} + ae^{jb} E_{\text{QZ},\theta} \quad (1.11)$$ + +The transmission matrix can be defined as H + +$$\begin{bmatrix} E_{\text{Probe},\theta} \\ E_{\text{Probe},\phi} \end{bmatrix} = H \begin{bmatrix} E_{\text{QZ},\theta} \\ E_{\text{QZ},\phi} \end{bmatrix} \quad (1.12)$$ + +$$H = \begin{bmatrix} 1 & ae^{jb} \\ ce^{jd} & 1 \end{bmatrix} \quad (1.13)$$ + +The total magnitude component of the electric field including coherence/interference terms at the probe is + +$$\begin{aligned} E_{\text{Probe},T} &= \sqrt{|E_{\text{Probe},\theta}|^2 + |E_{\text{Probe},\phi}|^2} = \sqrt{|E_{\text{QZ},\theta} + ce^{jd} E_{\text{QZ},\phi}|^2 + |E_{\text{QZ},\phi} + ae^{jb} E_{\text{QZ},\theta}|^2} \\ &= \sqrt{\left[ (E_{\text{QZ},\theta} + cE_{\text{QZ},\phi} \cos(d))^2 + (cE_{\text{QZ},\phi} \sin(d))^2 \right] + \left[ (E_{\text{QZ},\phi} + aE_{\text{QZ},\theta} \cos(b))^2 + (aE_{\text{QZ},\theta} \sin(b))^2 \right]} \\ &= \sqrt{\left[ E_{\text{QZ},\theta}^2 + 2cE_{\text{QZ},\theta} E_{\text{QZ},\phi} \cos(d) + c^2 E_{\text{QZ},\phi}^2 \cos^2(d) + c^2 E_{\text{QZ},\phi}^2 \sin^2(d) \right] +} \\ &\quad \sqrt{\left[ E_{\text{QZ},\phi}^2 + 2aE_{\text{QZ},\theta} E_{\text{QZ},\phi} \cos(b) + a^2 E_{\text{QZ},\theta}^2 \cos^2(b) + a^2 E_{\text{QZ},\theta}^2 \sin^2(b) \right]} \\ &= \sqrt{E_{\text{QZ},\theta}^2 (1 + a^2) + E_{\text{QZ},\phi}^2 (1 + c^2) + 2E_{\text{QZ},\theta} E_{\text{QZ},\phi} (c \cos(d) + a \cos(b))} \end{aligned} \quad (1.14)$$ + +When it is assumed that leakage between the two polarization ports of the measurement probe is assumed to be the same, then $a=c=10^{\text{XPD}/20}$ in (1.14). Additionally, it has to be assumed that $d=b+\pi$ which guarantees the orthogonality between the two field vectors, i.e., the dot product between the vectors has to be zero. With these assumptions, Equation (1.14) will become + +$$E_{\text{Probe},T} = \sqrt{(E_{\text{QZ},\theta}^2 + E_{\text{QZ},\phi}^2)(1 + a^2)} \quad (1.15)$$ + +The normalized ratio of total powers at measurement probe and the centre of the quiet zone is therefore + +$$\frac{P_{\text{Probe}}}{P_{\text{QZ}}} \propto \frac{E_{\text{Probe},T}^2}{E_{\text{QZ},T}^2} = 1 + a^2 = 1 + 10^{\frac{2\text{XPD}}{20}} = 1 + 10^{\frac{\text{XPD}}{10}} \quad (1.16)$$ + +The derived XPD MU based on electric fields which included the coherence/interference terms in (1.16) is the same as in (1.6). + +The XPD of the measurement system shall be determined from the quality of quiet zone measurements, see clause O.2 of [7], at the 7 reference points, P1 through P7, specifically with reference AUT orientations $\gamma=\beta=0^\circ$ for distributed axes systems, Section O.2.6.1 [7], or reference AUT orientations $\beta=\alpha=0^\circ$ for combined-axes systems, Section O.2.6.2 [7]. Alternatively, it can be determined using a reference antenna optimized for XPD measurements and with the corresponding alignment to achieve optimal polarization matching between the reference and the measurement antenna. + +The XPD for each reference point shall be calculated as the ratio of cross-polarized to co-polarized measured powers and the largest XPD from the 7 different reference points shall be used to determine the XPD MU, i.e., + +$$MU_{XPD} [dB] = 10 \log_{10} (1 + \alpha_{max}) = 10 \log_{10} \left( 1 + 10^{\frac{XPD_{max}}{10}} \right) \quad (1-17)$$ + +where + +$$XPD_{max} [dB] = 10 \log_{10} \left[ \max \left( \left. \frac{P_{cross-pol}}{P_{co-pol}} \right|_{P1, \gamma_{rot}=0^\circ}, \left. \frac{P_{cross-pol}}{P_{co-pol}} \right|_{P1, \gamma_{rot}=90^\circ}, \dots, \left. \frac{P_{cross-pol}}{P_{co-pol}} \right|_{P7, \gamma_{rot}=0^\circ}, \left. \frac{P_{cross-pol}}{P_{co-pol}} \right|_{P7, \gamma_{rot}=90^\circ} \right) \right] \quad (1-18)$$ + +### B.2.1.11 Insertion loss Variation + +This uncertainty contribution comes from introducing an additional cable which is not present for both the calibration and DUT measurement. If the cables remain the same for the calibration and DUT measurement, then the contribution should be set to zero. + +If an additional cable is added for one part of the test, the insertion loss must be accounted for in the measurement results. If the insertion loss is measured the uncertainty contribution will be the combined uncertainty related to the insertion loss measurement. The insertion loss can also be taken from the datasheet and assumed to have a rectangular distribution. + +### B.2.1.12 RF leakage (from measurement antenna to receiver/transmitter) + +This contribution denotes noise leaking in to connector and cable(s) between measurement antenna and receiving/transmitting equipment. The contribution also includes the noise leakage between the connector and cable(s) between reference antenna and transmitting equipment for the calibration phase. This uncertainty contributor is contained in the contributor quality of quiet zone described in clause B.2.1.3 and its value therefore is set to zero. + +### B.2.1.13 Misalignment of positioning System + +This contribution originates from uncertainty in sliding position and turn table angle/tilt accuracy. If the calibration antenna is aligned to the beam peak this contribution can be considered negligible and therefore set to zero. + +### B.2.1.14 Uncertainty of the Network Analyzer + +This contribution originates from all uncertainties involved transmission magnitude measurement with a network analyser, for example: drift, frequency flatness, temperature variation from kit calibration to path losses measurement as well as interpolation of calibration data if test frequencies were not calibrated during path loss characterization. The + +uncertainty value will be indicated in the manufacturer's data sheet. It needs to be ensured that appropriate manufacturer's uncertainty contribution is specified for the absolute levels measured. + +When an end-to-end system calibration approach is used, the absolute levels are related to the total system losses of the measurement path. When a split calibration approach is used, separate MU contributions need to be determined + +- $u\_cond$ : transmission magnitude uncertainty for the conducted portion of the calibration; the absolute levels are related to the total system losses for the portion of the system calibrated +- $u\_rad$ : transmission magnitude uncertainty for the radiated portion of the calibration; the absolute levels are related to the total system losses for the portion of the system calibrated + +The total MU of the network analyser for the split calibration is the RSS'ed value of $u\_cond$ and $u\_rad$ . + +### B.2.1.15 Uncertainty of the absolute gain of the calibration antenna + +The calibration antenna only appears in Stage 2. Therefore, the gain uncertainty has to be taken into account. This uncertainty will come from a calibration report with traceability to a National Metrology Institute with measurement uncertainty budgets generated following the guidelines outlined in internationally accepted standards. + +### B.2.1.16 Positioning and pointing misalignment between the reference antenna and the measurement antenna + +This contribution originates from reference antenna alignment and pointing error. In this measurement if the maximum gain direction of the reference antenna and the transmitting antenna are aligned to each other, this contribution can be considered negligible and therefore set to zero. + +### B.2.1.17 gNB emulator uncertainty + +gNB emulator is used to drive a signal to the horn antenna (via multiple external components such as a switch box, an amplifier and a circulator, etc.) in sensitivity tests either as an absolute level or as a relative level. Receiving device used is typically a UE/phablet/tablet/FWA. Generally there occurs uncertainty contribution from absolute level accuracy, non-linearity and frequency characteristic of the gNB emulator. + +For practical reasons, in a case that a VNA is used as calibration equipment, gNB emulator is connected to the system after the calibration measurement (Stage 2) is performed by the VNA. Hence, the uncertainty on the absolute level of gNB emulator (transmitter device) cannot be assumed as systematic. This uncertainty should be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed. Furthermore, the uncertainty of the non-linearity is included in the absolute level uncertainty. + +### B.2.1.18 Phase centre offset of calibration + +Gain is defined at the phase centre of the antenna. If the phase centre of the calibration antenna is not aligned at the centre of the set up during the calibration, then there will be uncertainty related to the measurement distance. + +The phase centre of a horn antenna moves with frequency along the taper length of the antenna therefore during the calibration the phase centre of all frequencies will not be aligned with the setup centre. The associated uncertainty term can be estimated using the following formula [14]: + +$$\pm 20 \log_{10} \frac{d_m - d_p}{d_m}$$ + ++/-20log((measurement distance – d)/measurement distance) [14] + +Where $d_m$ is the measurement distance and $d_p$ is the maximum positional uncertainty. For a Horn antenna this is equal to 0.5 the length of the taper. This uncertainty is considered to have a rectangular distribution so the standard uncertainty is calculated by dividing the uncertainty by $\sqrt{3}$ . + +The same equation applies to log periodic antennas with $d_m$ being 0.5 the length of the boom. + +For a dipole antenna, given that the phase centre of the antenna is easily aligned with the centre of the set up the measurement uncertainty is zero. + +If the calibration antenna (i.e. horn) is adjusted during the calibration to align the phase centre to the setup centre then this uncertainty term can be considered to be zero. + +As an example a horn with a taper length of 50 mm, at 43.5 GHz and a measurement distance of 72.55 cm the uncertainty term is 0.62, with a rectangular distribution the standard uncertainty is 0.358 dB. + +For DFF systems this uncertainty contribution must be included. + +### **B.2.1.19 Quality of quiet zone for calibration process** + +During the calibration process the calibration antenna will be placed at the centre of the quiet zone. Therefore, only point P1 from the procedure outlined in B.2.1.3 needs to be considered for the quality of the quiet zone validation measurement. + +For gain calibrations, the standard uncertainty of the EIRP results obtained following the method outlined in 2.10 shall be used. For efficiency calibrations, the standard uncertainty of the TRP result obtained following the method outlined in 2.9 shall be used. + +### **B.2.1.20 Standing wave between reference calibration antenna and measurement antenna** + +This term comes from the amplitude ripple caused by the standing waves between the reference antenna and measurement antenna. This value can be captured by sliding ( $\lambda/4$ ) the reference antenna towards the measurement antenna as the standing waves go in and out of phase causing a ripple in amplitude. The uncertainty term can be derived by performing the standard deviation on the results. + +### **B.2.1.21 Influence of the calibration antenna feed cable (Flexing cables, adapters, attenuators, connector repeatability)** + +During the calibration measurement a cable (adapters, attenuators) is used to feed the calibration antenna. This uncertainty captures any influence the cable may have on the measurements result. This term can be assessed by repeating measurements while flexing the cables and rotary joints and using the largest difference between the results as the uncertainty. For some calibration test configurations this uncertainty can be considered to be zero. + +### **B.2.1.22 Influence of TRP measurement grid** + +This contributor describes the uncertainty of the measured TRP value due to the finite number of measurement grid points. + +### **B.2.1.23 Influence of beam peak search grid** + +This contributor describes the uncertainty of absolute TX power beam peak measurements, e.g., EIRP in beam peak direction, due to the finite number of measurement points in the beam peak search grid. + +#### B.2.1.24 Systematic error due to TRP calculation/quadrature + +When calculating TRP using different quadrature of constant step size data, a mean error shall be taken into account. The value of this contributor depends on the number of measurement grid points and the quadrature technique used. + +No mean error has to be taken into account for constant density approach (using the charged particle or the golden spiral implementation) for non-sparse antenna arrays. + +This measurement uncertainty contributor represents a systematic uncertainty and must not be root sum squared with contributors described by standard deviation. + +#### B.2.1.25 Multiple measurement antenna uncertainty + +This contributor describes the uncertainty caused by switching multiple measurement antennas either by mechanically or electrically to measure TRx spurious emission. + +A frequency range of spurious tests (e.g. general spurious emission) is defined from 6 GHz to second harmonic of FR2 bands such as 80 GHz. Since that frequency range is quite wide, it is impossible to cover the whole range only by one measurement antenna. Therefore to provide a feature of the spurious emission measurement by FR2 test system, the system has to equip a capability to switch corresponding measurement antennas in an anechoic chamber. One of the mechanical antenna switching methods can be a structure of a slider. Then a repeatability of a bending loss of a feeder cable which is connected to the measurement antennas shall be taken into account. On the other hand for electrical antenna switching, since multiple antennas need to be aligned in a chamber with a different position, the quiet zone characteristics might receive an influence by a displacement from the ideal focal point. In a case of electrical switching system, if the measurement antenna configuration is the same for the quality of the quiet zone measurement and the DUT measurement, then this uncertainty term is encompassed in the quality of the quiet zone results. + +#### B.2.1.26 DUT repositioning + +This contributor describes the uncertainty due to a displacement of a DUT. The DUT may need to be re-positioned between measurements, for instance when the battery runs low in charge. + +#### B.2.1.27 Influence of noise + +This contributor describes an offset uncertainty factor caused by a noise floor especially in a case of low SNR. This contributor works as a bias to measured results only to a direction to increase values and thus this shall be included in the uncertainty budget table as a systematic uncertainty. The uncertainty value can be derived by the following equation. + +#### B.2.1.28 Systematic error related to beam peak search + +When calculating beam peak search a systematic error shall be taken into account. The value of this contributor depends on the number of measurement grid points. + +This measurement uncertainty contributor represents a systematic uncertainty and must not be root sum squared with contributors described by standard deviation. + +### B.2.1.29 Influence of spherical coverage grid + +This contributor describes the uncertainty of spherical measurements, due to the finite number of measurement points in the spherical coverage grid. + +### B.2.1.30 Systematic error related to EIS spherical coverage + +When calculating EIS spherical coverage, a mean error shall be taken into account. The value of this contributor depends on the DL power step size used for the EIS search and then number of measurement grid points. + +This measurement uncertainty contributor represents a systematic uncertainty and must not be root sum squared with contributors described by standard deviation. + +### B.2.1.31 Misalignment of DUT due to change of DUT orientation + +This contributor describes the uncertainty due to a mis-alignment of a DUT after a change of DUT orientations described in Tables J.2-1 through J.2-3 in [3] during spurious emission and spherical coverage measurements. This contribution is negligible with spherical coverage TC as far as the misalignment is within the accuracy of DUT re-positioning. + +### B.2.1.32 Additional Impact of Interferer ACLR + +This contribution describes the effect of the interferer ACLR over the wanted signal channel when testing ACS and in-band blocking. Even if power is set perfectly in the configured transmission bandwidth, interferer power will leak in the wanted signal channel due to its ACLR. + +### B.2.1.33 Modulated Interferer uncertainty + +Modulated Interferer is used to drive a signal to the horn antenna (via multiple external components such as a switch box, an amplifier and a circulator, etc.) in ACS and In-band Blocking tests either as an absolute level or as a relative level. Receiving device used is typically a UE/phablet/tablet/FWA. Generally, there occurs uncertainty contribution from absolute level accuracy, non-linearity and frequency characteristic of the interferer generator. + +For practical reasons, in a case that a VNA is used as calibration equipment, Modulated Interferer is connected to the system after the calibration measurement (Stage 2) is performed by the VNA. Hence, the uncertainty on the absolute level of Modulated Interferer (transmitter device) cannot be assumed as systematic. This uncertainty should be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed. Furthermore, the uncertainty of the non-linearity is included in the absolute level uncertainty. + +### B.2.1.34 Void + +### B.2.1.35 Influence of offset antenna for blocker signal + +This MU term describes the additional uncertainty caused by using offset antenna for blocker signal for FR2 blocking test cases. The cause of additional MU using offset antenna is the difference of UE antenna's gain between beam peak direction and offset beam peak direction, which will cause the error for the ACS or IBB performance requirement which is given by the power ratio of the wanted signal power and blocker signal power. Such difference of the UE antenna gain can be compensated by increasing the blocker signal power by the measured EIS difference at beam peak direction and at offset beam peak. Despite this compensation, there still is a residual error corresponding to the antenna gain difference due to different frequency of wanted and blocker signal. Table B.2.1.35-1 summarizes the residual error after compensation for various offset angle assumption. + +**Table B.2.1.35-1: Residual error when offset antenna is used for FR2 blocking test** + +| offset angle[deg] | Mean error[dB] | Std.dev[dB] | Mean error[dB] | Std.dev[dB] | +|-------------------|----------------|-------------|----------------|-------------| +| | 2x8 Assumption | | 1x4 Assumption | | +| 0 | 0.000 | 0.000 | 0.000 | 0.000 | +| 0.5 | 0.001 | 0.001 | 0.000 | 0.000 | +| 1 | 0.004 | 0.003 | 0.001 | 0.001 | +| 1.5 | 0.010 | 0.006 | 0.002 | 0.002 | +| 2 | 0.018 | 0.011 | 0.004 | 0.003 | +| 2.5 | 0.028 | 0.018 | 0.006 | 0.004 | +| 3 | 0.041 | 0.026 | 0.009 | 0.006 | +| 3.5 | 0.057 | 0.036 | 0.013 | 0.009 | +| 4 | 0.075 | 0.048 | 0.016 | 0.011 | +| 4.5 | 0.096 | 0.062 | 0.021 | 0.015 | +| 5 | 0.120 | 0.078 | 0.026 | 0.018 | +| 5.5 | 0.147 | 0.096 | 0.031 | 0.022 | +| 6 | 0.178 | 0.117 | 0.038 | 0.026 | +| 6.5 | 0.213 | 0.142 | 0.044 | 0.031 | +| 7 | 0.252 | 0.170 | 0.051 | 0.036 | + +NOTE 1: For MU assessment of the test system, the MU values should be taken from the row corresponding to the test system's offset antenna angle. + +NOTE 2: Mean error should be counted as systematic offset and Std.dev should be counted as a random uncertainty in the MU budget table. + +NOTE 3: For PC3 UE testing, the values for 2x8 Assumption should be used. + +NOTE 4: EIS step size used for compensation should be added as mean error. + +## B.2.1.36 Uncertainty of the RF relative power measurement equipment + +The receiving device is used to measure the received signal level in the EIRP tests as a relative level. These receiving devices are spectrum analysers, communication analysers, or power meters. The uncertainty value will be indicated in the manufacturer's data sheet. Basically, the linearity and impact of the averaging time needs to be considered in this MU term. + +## B.2.2 Measurement error contribution descriptions for IFF + +### B.2.2.1 Positioning misalignment + +See B.2.1.1. + +The uncertainty value of positioning misalignment is estimated as below table and used across clause B. + +**Table B.2.2.1-1: Uncertainty value for positioning misalignment for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC5 | 0.02 | Normal | 2.00 | 0.01 | +| PC3 | 0.00 | Normal | 2.00 | 0.00 | +| PC6 | FFS | FFS | FFS | FFS | + +## B.2.2.2 Measure distance uncertainty + +See B.2.1.2. For IFF1 this can be considered to be zero. + +The uncertainty value of measure distance uncertainty is estimated as below table and used across clause B. + +**Table B.2.2.2-1: Uncertainty value for measure distance uncertainty for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC3, PC5, PC6 | 0.00 | Rectangular | 1.73 | 0.00 | + +## B.2.2.3 Quality of Quiet Zone + +See B.2.1.3. + +The uncertainty value of quality of quiet zone is estimated as below table and used across clause B. + +**Table B.2.2.3-1: Uncertainty value for quality of quiet zone for IFF** + +| QZ size | Power class | Condition | Test case | Frequency range | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|--------------------|-----------|-----------------------------|---------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| All | All | All | ACLR (relative measurement) | FR2a, FR2b, FR2c | 0.52 | Actual | 1.00 | 0.52 | +| $\leq 30\text{cm}$ | PC1, PC3, PC5, PC6 | NC | NOTE1 | FR2a, FR2b | 0.6 | Actual | 1.00 | 0.6 | +| | | | | FR2c | 0.7 | Actual | 1.00 | 0.7 | +| | | | SE | 6GHz to 12.75GHz | 0.7 | Actual | 1.00 | 0.7 | +| | | | | 12.75GHz to 23.45GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | | | 23.45GHz to 40.8GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | | | 40.8GHz to 66GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | | | 66GHz to 80GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | ETC | NOTE1 | FR2a, FR2b, FR2c (NOTE 3) | 0.9 | Actual | 1.00 | 0.9 | +| 40cm | PC1, PC3, PC5, PC6 | NC | NOTE1 | FR2a, FR2b | 0.7 (NOTE 2) | Actual | 1.00 | 0.7 | +| | | | | FR2c | 0.8 (NOTE 2) | Actual | 1.00 | 0.8 | +| | | | SE | 6GHz to 12.75GHz | TBD | Actual | 1.00 | TBD | +| | | | | 12.75GHz to 23.45GHz | TBD | Actual | 1.00 | TBD | +| | | | | 23.45GHz to 40.8GHz | TBD | Actual | 1.00 | TBD | +| | | | | 40.8GHz to 66GHz | TBD | Actual | 1.00 | TBD | +| | | | | 66GHz to 80GHz | TBD | Actual | 1.00 | TBD | +| | | ETC | NOTE1 | FR2a, FR2b | TBD | Actual | 1.00 | TBD | + +NOTE 1: The uncertainty in current row applies to maximum output power with EIRP and TRP, EIRP spherical coverage, MPR, configured output power with power boost, minimum output power, transmit OFF power, spectrum emission mask, reference sensitivity, adjacent selectivity, in-band blocking. + +NOTE 2: For Uncertainty assessment in tables across clause B and MTSU calculation, QoQZ uncertainty value for QZ $\leq 30\text{cm}$ is used also for 40cm. + +NOTE 3: For FR2c in ETC, QoQZ uncertainty value only defined for EIRP/EIS. + +## B.2.2.4 Mismatch + +See B.2.1.4. + +The uncertainty value of mismatch is estimated as below table and used across clause B. + +**Table B.2.2.4-2: Uncertainty value for mismatch for IFF** + +| QZ size | Power class | Condition | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty (\sigma) [dB] | +|-----------------------------------------|-----------------------------|------------------|------------------------------------------|--------------------------|----------------------------------------|----------------|--------------------------------------------------------| +| Stage 2: DUT measurement | | | | | | | | +| <= 30cm | PC1,
PC3,
PC5,
PC6 | NC | Default (FR2a, FR2b) | 1.30 | Actual | 1.00 | 1.30 | +| | | | Default (FR2c) | 1.70 | Actual | 1.00 | 1.70 | +| | | | ACLR (relative measurement) (FR2a, FR2b) | 1.84 | Actual | 1.00 | 1.84 | +| | | | ACLR (relative measurement) (FR2c) | 2.4 | Actual | 1.00 | 2.4 | +| | | | Tx SE (6GHz to 12.75GHz) | 1.5 | Actual | 1.00 | 1.5 | +| | | | Tx SE (12.75GHz to 23.45GHz) | 1.5 | Actual | 1.00 | 1.5 | +| | | | Tx SE (23.45GHz to 40.8GHz) | 1.4 | Actual | 1.00 | 1.4 | +| | | | Tx SE (40.8GHz to 66GHz) | 2.3 | Actual | 1.00 | 2.3 | +| | | | Tx SE (66GHz to 80GHz) | 2.3 | Actual | 1.00 | 2.3 | +| | | | Rx SE (6GHz to 12.75GHz) | 1.6 | Actual | 1.00 | 1.6 | +| | | | Rx SE (12.75GHz to 23.45GHz) | 1.6 | Actual | 1.00 | 1.6 | +| | | | Rx SE (23.45GHz to 40.8GHz) | 1.5 | Actual | 1.00 | 1.5 | +| | | | Rx SE (40.8GHz to 66GHz) | 2.3 | Actual | 1.00 | 2.3 | +| | | | Rx SE (66GHz to 80GHz) | 2.3 | Actual | 1.00 | 2.3 | +| | | ETC | Default | 1.30 | Actual | 1.00 | 1.30 | +| | | | ACLR (relative measurement) | 1.84 | Actual | 1.00 | 1.84 | +| | | | SE | | | | | +| Stage 1: Calibration measurement | | | | | | | | +| <= 30cm | PC1,
PC3,
PC5,
PC6 | NC | All | 0.00 | U-shaped | 1.41 | 0.00 | +| | | ETC | All | 0.00 | U-shaped | 1.41 | 0.00 | + +## B.2.2.5 Standing wave between DUT and measurement antenna + +See B.2.1.5. + +The uncertainty value of standing wave between the DUT and measurement antenna is estimated as below table and used across clause B. + +**Table B.2.2.5-1: Uncertainty value for standing wave between the DUT and measurement antenna for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC3, PC5, PC6 | 0.00 | U-shaped | 1.41 | 0.00 | + +## B.2.2.6 Uncertainty of the RF power measurement equipment + +See B.2.1.6. + +The uncertainty value of RF power measurement equipment is estimated as below table and used across clause B. + +**Table B.2.2.6-1: Uncertainty value for RF power measurement equipment for IFF** + +| Power class | Test case | Frequency range | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|---------------------------------------------------------------|----------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC3, PC5, PC6 | MOP, MPR, Configured output power with power boost, SEM, ACLR | FR2a, FR2b | 2.16 | Normal | 2.00 | 1.08 | +| | Minimum output power, OFF power | FR2a, FR2b | 2.50 | Normal | 2.00 | 1.25 | +| | SE | 6GHz to 12.75GHz | 2.00 | Normal | 2.00 | 1.00 | +| | | 12.75GHz to 23.45GHz | 2.16 | Normal | 2.00 | 1.08 | +| | | 23.45GHz to 40.8GHz | 2.73 | Normal | 2.00 | 1.37 | +| | | 40.8GHz to 66GHz | 4.00 | Normal | 2.00 | 2.00 | +| | | 66GHz to 80GHz | 4.00 | Normal | 2.00 | 2.00 | +| PC3 | MOP | FR2c | 3.6 | Normal | 2.00 | 1.8 | + +## B.2.2.7 Phase Curvature + +See B.2.1.7. For IFF1 this can be considered to be zero. + +The uncertainty value of phase curvature is estimated as below table and used across clause B. + +**Table B.2.2.7-1: Uncertainty value for phase curvature for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | 0.00 | U-shaped | 1.41 | 0.00 | + +## B.2.2.8 Amplifier Uncertainties + +See B.2.1.8. + +The uncertainty value of amplifier uncertainties is estimated as below table and used across clause B. + +**Table B.2.2.8-1: Uncertainty value for amplifier uncertainties for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|--------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| PC1,
PC5 | Default | 2.10 | Normal | 2.00 | 1.05 | +| | Relative power tolerance | TBD | Rectangular | 1.73 | TBD | +| | SE (66GHz to 80GHz) | 3.0 | Normal | 2.00 | 1.50 | +| PC3 | Default | 2.10 | Normal | 2.00 | 1.05 | +| | Relative power tolerance | 0.5 | Rectangular | 1.73 | 0.29 | +| | SE (66GHz to 80GHz) | 3.0 | Normal | 2.00 | 1.50 | +| PC6 | Default | 2.10 | Normal | 2.00 | 1.05 | +| | Relative power tolerance | TBD | Rectangular | 1.73 | TBD | +| | SE (66GHz to 80GHz) | 3.0 | Normal | 2.00 | 1.50 | +| Stage 1: Calibration measurement | | | | | | +| PC1,
PC3,
PC5,
PC6 | Default | 0.00 | Normal | 2.00 | 0.00 | + +## B.2.2.9 Random uncertainty + +See B.2.1.9. + +The uncertainty value of random uncertainty is estimated as below table and used across clause B. + +**Table B.2.2.9-1: Uncertainty value for random uncertainty for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | 0.5 | Normal | 2.00 | 0.25 | + +## B.2.2.10 Influence of XPD + +See B.2.1.10. + +The uncertainty value of influence of the XPD is estimated as below table and used across clause B. + +**Table B.2.2.10-2: Uncertainty value for influence of the XPD for IFF** + +| QZ size | Power class | Test case | Frequency range | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|-----------------------------|-----------|----------------------|-------------------|---------------------------------|---------|----------------------------------------| +| All | All | ACLR | FR2a, FR2b, FR2c | 0.00 | U-shaped | 1.41 | 0.00 | +| $\leq 30\text{cm}$ | PC1,
PC3,
PC5,
PC6 | Default | FR2a, FR2b, FR2c | 0.01 | U-shaped | 1.41 | 0.00 | +| | | SE | 6GHz to 12.75GHz | 0.09 | U-shaped | 1.41 | 0.064 | +| | | | 12.75GHz to 23.45GHz | 0.09 | U-shaped | 1.41 | 0.064 | +| | | | 23.45GHz to 40.8GHz | 0.01 | U-shaped | 1.41 | 0.00 | +| | | | 40.8GHz to 66GHz | 0.09 | U-shaped | 1.41 | 0.064 | +| | | | 66GHz to 87GHz | 0.09 | U-shaped | 1.41 | 0.064 | +| $40\text{cm}$ | PC1,
PC3,
PC5,
PC6 | Default | FR2a, FR2b, FR2c | 0.07
(NOTE 1) | U-shaped | 1.41 | 0.02 | +| | | SE | 6GHz to 12.75GHz | TBD | U-shaped | 1.41 | TBD | +| | | | 12.75GHz to 23.45GHz | TBD | U-shaped | 1.41 | TBD | +| | | | 23.45GHz to 40.8GHz | TBD | U-shaped | 1.41 | TBD | +| | | | 40.8GHz to 66GHz | TBD | U-shaped | 1.41 | TBD | +| | | | 66GHz to 87GHz | TBD | U-shaped | 1.41 | TBD | + +NOTE 1: For Uncertainty assessment in tables across clause B and MTSU calculation, influence of the XPD uncertainty value for $\text{QZ} \leq 30\text{cm}$ is used also for $40\text{cm}$ . + +## B.2.2.11 Insertion Loss Variation + +See B.2.1.11. + +The uncertainty value of insertion loss variation is estimated as below table and used across clause B. + +**Table B.2.2.11-1: Uncertainty value for insertion loss variation for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | +| PC1,
PC3,
PC5,
PC6 | 0.00 | Rectangular | 1.73 | 0.00 | +| Stage 1: Calibration measurement | | | | | +| PC1,
PC3,
PC5,
PC6 | 0.00 | Rectangular | 1.73 | 0.00 | + +## B.2.2.12 RF leakage (from measurement antenna to receiver/transmitter) + +See B.2.1.12. + +The uncertainty value of RF leakage is estimated as below table and used across clause B. + +**Table B.2.2.12-1: Uncertainty value for RF leakage for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | 0.00 | Actual | 1.00 | 0.00 | + +## B.2.2.13 Misalignment of positioning system + +See B.2.1.13. + +The uncertainty value of misalignment of positioning system is estimated as below table and used across clause B. + +**Table B.2.2.13-1: Uncertainty value for misalignment of positioning system for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | 0.00 | Normal | 2.00 | 0.00 | + +## B.2.2.14 Uncertainty of the Network Analyzer + +See B.2.1.14. + +The uncertainty value of uncertainty of the network analyzer is estimated as below table and used across clause B. + +**Table B.2.2.14-1: Uncertainty value for uncertainty of the network analyser for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|---------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| All | Default (6GHz to 40.8GHz) | 1.50 | Normal | 2.00 | 0.75 | +| | SE (40.8GHz to 80GHz) | 1.70 | Normal | 2.00 | 0.85 | + +## B.2.2.15 Uncertainty of the absolute gain of the calibration antenna + +See B.2.1.15. + +The uncertainty value of uncertainty of the absolute gain of the calibration antenna is estimated as below table and used across clause B. + +**Table B.2.2.15-1: Uncertainty value for uncertainty of the absolute gain of the calibration antenna for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-----------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | Default | 0.60 | Normal | 2.00 | 0.30 | +| | SE (40.8GHz to 66GHz) | 1.70 | Normal | 2.00 | 0.85 | +| | SE (66GHz to 87GHz) | 1.70 | Normal | 2.00 | 0.85 | + +## B.2.2.16 Positioning and pointing misalignment between the reference antenna and the measurement antenna + +See B.2.1.16. + +The uncertainty value of positioning and pointing misalignment between the reference antenna and the measurement antenna is estimated as below table and used across clause B. + +**Table B.2.2.16-1: Uncertainty value for positioning and pointing misalignment between the reference antenna and the measurement antenna for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-----------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | Default | 0.01 | Rectangular | 1.73 | 0.00 | +| | ACLR | 0.00 | Rectangular | 1.73 | 0.00 | +| | SE | 0.05 | Rectangular | 1.73 | 0.03 | + +## B.2.2.17 gNB emulator uncertainty + +See B.2.1.17. + +The uncertainty value of gNB emulator uncertainty is estimated as below table and used across clause B. + +**Table B.2.2.17-1: Uncertainty value for gNB emulator uncertainty for IFF** + +| Power class | Uncertainty value | Frequency range | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------|-----------------|---------------------------------|---------|----------------------------------------| +| PC1, PC5 | 2.9 | FR2a, FR2b | Normal | 2.00 | 1.45 | +| PC3 | 2.9 | FR2a, FR2b | Normal | 2.00 | 1.45 | +| | 3.6 | FR2c | Normal | 2.00 | 1.8 | +| PC6 | 2.9 | FR2a, FR2b | Normal | 2.00 | 1.45 | + +## B.2.2.18 Phase centre offset of calibration + +See B.2.1.18. For IFF1 this can be considered to be zero. + +The uncertainty value of phase centre offset of calibration is estimated as below table and used across clause B. + +**Table B.2.2.18-1: Uncertainty value for phase centre offset of calibration for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC3, PC5, PC6 | 0.00 | Rectangular | 1.73 | 0.00 | + +## B.2.2.19 Quality of the Quiet Zone for Calibration Process + +See B.2.1.19. + +The uncertainty value of quality of quiet zone for calibration process is estimated as below table and used across clause B. + +**Table B.2.2.19-1: Uncertainty value for quiet zone for calibration process for IFF** + +| QZ size | Power class | Condition | Test case | Frequency range | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|--------------------|-----------|-----------------------------|---------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| All | All | All | ACLR (relative measurement) | FR2a, FR2b, FR2c | 0.32 | Actual | 1.00 | 0.32 | +| $\leq 40\text{cm}$ | PC1, PC3, PC5, PC6 | NC | NOTE1 | FR2a, FR2b | 0.4 | Actual | 1.00 | 0.4 | +| | | | | FR2c | 0.5 | Actual | 1.00 | 0.5 | +| | | | SE | 6GHz to 12.75GHz | 0.7 | Actual | 1.00 | 0.7 | +| | | | | 12.75GHz to 23.45GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | | | 23.45GHz to 40.8GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | | | 40.8GHz to 66GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | | | 66GHz to 80GHz | 0.6 | Actual | 1.00 | 0.6 | +| | | ETC | NOTE1 | FR2a, FR2b, FR2c (NOTE 2) | 0.6 | Actual | 1.00 | 0.6 | + +NOTE 1: The uncertainty in current row applies to maximum output power with EIRP and TRP, EIRP spherical coverage, MPR, configured output power with power boost, minimum output power, transmit OFF power, spectrum emission mask, reference sensitivity, adjacent selectivity, in-band blocking. + +NOTE 2: For FR2c in ETC, QoQZ uncertainty value only defined for EIRP/EIS. + +## B.2.2.20 Standing wave between reference calibration antenna and measurement antenna + +See B.2.1.20. + +The uncertainty value of standing wave between reference calibration antenna and measurement antenna is estimated as below table and used across clause B. + +**Table B.2.2.20-1: Uncertainty value for standing wave between reference calibration antenna and measurement antenna for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC3, PC5, PC6 | 0.00 | U-shaped | 1.41 | 0.00 | + +## B.2.2.21 Influence of the calibration antenna feed cable (Flexing cables, adapters, attenuators, connector repeatability) + +See B.2.1.21. + +The uncertainty value of influence of the calibration antenna feed cable is estimated as below table and used across clause B. + +**Table B.2.2.21-1: Uncertainty value for influence of the calibration antenna feed cable for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|--------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | Default | 0.14 | Normal | 2.00 | 0.07 | +| | SE
(40.8GHz to 66GHz) | 0.28 | Normal | 2.00 | 0.14 | +| | SE (66GHz to 87GHz) | 0.28 | Normal | 2.00 | 0.14 | + +## B.2.2.22 Influence of TRP measurement grid + +See B.2.1.22. + +The uncertainty value of influence of TRP measurement grid is estimated as below table and used across clause B. + +**Table B.2.2.22-1: Uncertainty value for influence of TRP measurement grid for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------|-----------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC5
(Note 1) | Default | 0.25 | Actual | 1.00 | 0.25 | +| | SE | 0.25 | Actual | 1.00 | 0.25 | +| PC3 | Default | 0.25 | Actual | 1.00 | 0.25 | +| | SE | 0.32 | Actual | 1.00 | 0.32 | +| PC6 | Default | FFS | FFS | FFS | FFS | +| | SE | FFS | FFS | FFS | FFS | + +Note 1: A finer measurement grid for SE (when compared to default) is required near the harmonic region, i.e., a constant-step size grid with 2522 unique grid points ( $\Delta\theta=\Delta\phi=5^\circ$ ) or a constant-density grid with 1600 grid points. + +## B.2.2.23 Influence of beam peak search grid + +See B.2.1.23. + +The uncertainty value of influence of beam peak search grid is estimated as below table and used across clause B. + +**Table B.2.2.23-1: Uncertainty value for influence of beam peak search grid for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1,
PC3,
PC5,
PC6 | 0.00 | Actual | 1.00 | 0.00 | + +## B.2.2.24 Systematic error due to TRP calculation/quadrature + +See B.2.1.24. + +The uncertainty value of systematic error due to TRP calculation/quadrature is estimated as below table and used across clause B. + +**Table B.2.2.24-1: Uncertainty value for systematic error due to TRP calculation/quadrature for IFF** + +| Power class | Uncertainty value | +|--------------------|-------------------| +| PC1, PC3, PC5, PC6 | 0.00 | + +## B.2.2.25 Multiple measurement antenna uncertainty + +See B.2.1.25. + +The uncertainty value of multiple measurement antenna uncertainty is estimated as below table and used across clause B. + +**Table B.2.2.25-1: Uncertainty value for multiple measurement antenna uncertainty for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC3, PC5, PC6 | 0.15 | Actual | 1.00 | 0.15 | + +## B.2.2.26 DUT repositioning + +See B.2.1.26. + +The uncertainty value of DUT repositioning is estimated as below table and used across clause B. + +**Table B.2.2.26-1: Uncertainty value for DUT repositioning for IFF** + +| Power class | Test case | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC5 | TRP, spherical coverage | 0.00 | Rectangular | 1.73 | 0.00 | +| | EIRP, EIS | 0.35 | Rectangular | 1.73 | 0.20 | +| PC3 | TRP, spherical coverage | 0.00 | Rectangular | 1.73 | 0.00 | +| | EIRP, EIS | 0.08 | Rectangular | 1.73 | 0.05 | +| PC6 | TRP, spherical coverage | FFS | FFS | FFS | FFS | +| | EIRP, EIS | FFS | FFS | FFS | FFS | + +## B.2.2.27 Influence of noise + +See B.2.1.27. + +The uncertainty value of influence of noise is estimated as below table and used across clause B. + +**Editor's Note:** For ACLR, all applicable configurations need to be added. + +**Table B.2.2.27-1: Uncertainty value for influence of noise for PC3, SISO for IFF** + +| Test case | Frequency range | Noise floor | Minimum requirement | Estimated SNR total [dB/400MHz] | Relaxation | Influence of noise | +|------------------------------------------|------------------------------|-----------------|--------------------------------------------------|--------------------------------------------|------------|-----------------------| +| MOP-EIRP | FR2a | N/A | 20.7dBm/ChBW (22.4-1.7) | 16.33 (NOTE 1) | 0 | 0.1 | +| | FR2b | N/A | 18.9dBm/ChBW (20.6-1.7) | 11.45 (NOTE 1) | 0 | 0.3 | +| | FR2c | N/A | 18.2dBm/ChBW (18.7-0.5) | 11.45 (NOTE 1) | 0 | 0.3 | +| MOP-TRP | FR2a | N/A | 23dBm/ChBW | 16.33 (NOTE 1) | 0 | 0.1 | +| | FR2b, FR2c | N/A | 23dBm/ChBW | 11.45 (NOTE 1) | 0 | 0.3 | +| MOP-Spherical | FR2a | N/A | 9.75dBm/ChBW (Spherical – MBR= 11.5-1.75) | 11.45 (NOTE 1) | 0 | 0.3 | +| | FR2b | N/A | 7.6dBm/ChBW (Spherical – MBR=8-0.4) | 6.37 (NOTE 1) | 0 | 0.9 | +| MPR | FR2a | -7.6dBm/400MHz | 7.65dBm/ChBW (EIRP-MPB-MPR-T(MPR)=22.4-0.75-9-5) | 15.17 (NOTE 1) | 0 | 0.13 | +| | FR2b | -5.5dBm/400MHz | 5.85dBm/ChBW (EIRP-MPB-MPR-T(MPR)=20.6-0.75-9-5) | 11.30 (NOTE 1) | 0 | 0.31 | +| Configured output power with power boost | FR2a | N/A | 21.7dBm/ChBW (22.4-1.7+1) | 16.33 (NOTE 1) | 0 | 0.1 | +| | FR2b | N/A | 19.9dBm/ChBW (20.6-1.7+1) | 11.45 (NOTE 1) | 0 | 0.3 | +| Minimum output power | FR2a | -10.6dBm/400MHz | -13dBm | -2.54 (NOTE 1) | 8.4 | 1.0 (with relaxation) | +| | FR2b | -5.5dBm/400MHz | -13dBm | -7.64 (NOTE 1) | 13.5 | 1.0 (with relaxation) | +| OFF power – TRP | FR2a | N/A | -35dBm/ChBW | -24.54 (NOTE 2) | 30.4 | 1.0 (with relaxation) | +| | FR2b | N/A | | <-24.54 (NOTE 2) | N/A | Propose not to test | +| OFF power – EIRP | FR2a | -7.6dBm/400MHz | -30dBm/ChBW | -22.54 (NOTE 2) | 28.4 | 1.0 (with relaxation) | +| | FR2b | -5.5dBm/400MHz | | -24.64 (NOTE 2) | 30.5 | 1.0 (with relaxation) | +| Absolute power tolerance | Same as Minimum output power | | | | | | +| Relative power tolerance | FR2a | -13.6dBm/100MHz | -7.6dBm/100MHz | 5.86 (NOTE 1) | 0 | 1.0 | +| | FR2b | -11.5dBm/100MHz | -5.5dBm/100MHz | 5.86 (NOTE 1) | 0 | 1.0 | + +| | | | | | | | +|---------------------------|----------------------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---|------| +| Aggregate power tolerance | Same as Relative power tolerance | | | | | | +| Aggregate power tolerance | FR2a | -13.6dBm/100MHz | -7.6dBm/100MHz | 5.86 (NOTE 1) | 0 | 1.0 | +| | FR2b | -11.5dBm/100MHz | -5.5dBm/100MHz | 5.86 (NOTE 1) | 0 | 1.0 | +| SEM | FR2a | N/A | -13dBm/1MHz | 8.14 (NOTE 1) | 0 | 0.62 | +| | FR2b | N/A | | 5.86 (NOTE 1) | 0 | 1.0 | +| ACLR (CP) | FR2a | -7.6dBm/400MHz | Highest testable MPR for 400MHz: 3dB
16.65dBm/ChBW
(EIRP-MPB-MPR-T(MPR)
=22.4-0.75-3-2)

Actual lowest:
7.65dBm/ChBW
(EIRP-MPB-MPR-T(MPR)=22.4-0.75-9-5) | 22.86 (with 3dB MPR) (NOTE 1) | 0 | N/A | +| | FR2b | -5.5dBm/400MHz | Highest testable MPR for 400MHz: 2dB
16.35dBm/ChBW
(EIRP-MPB-MPR-T(MPR)
=20.6-0.75-2-1.5)

Actual lowest:
5.85dBm/ChBW
(EIRP-MPB-MPR-T(MPR)=20.6-0.75-9-5) | 21.86 (with 2dB MPR) (NOTE 1) | 0 | N/A | +| ACLR (ACP) | FR2a | -7.6dBm/400MHz | Highest testable MPR for 400MHz: 3dB
-0.35dBm/ChBW
(EIRP-MPB-MPR-T(MPR)-ACLR=22.4-0.75-3-2-17)

Actual lowest:
-9.35 dBm/ChBW
(EIRP-MPB-MPR-T(MPR)-ACLR=22.4-0.75-9-5-17) | 5.86 (NOTE 1) | 0 | 1.0 | + +| | | | | | | | +|------------------------------|---------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------|-----------------------------------------| +| | FR2b | -5.5dBm/400MHz | Highest testable MPR for 400MHz: 2dB
0.35dBm/ChBW
(EIRP-MPB-MPR-T(MPR)-ACLR=20.6-0.75-2-1.5-16)

Actual lowest:
-10.15 dBm/ChBW
(EIRP-MPB-MPR-T(MPR)-ACLR=20.6-0.75-9-5-16) | 5.86 (with 2dB MPR) (NOTE 1) | 0 | 1.0 | +| General Tx spurious | 6GHz <=f<=23.45GHz | N/A | -13dBm/1MHz | 10.0 (NOTE 1) | 0 | 0.41 | +| | 23.45GHz<=f<=40GHz | N/A | -13dBm/1MHz | 10.0 (NOTE 1) | 0 | | +| | 40GHz<=f<=80GHz | N/A | -13dBm/1MHz | 10.0 (NOTE 1) | 0 | | +| Tx spurious Co-existence | n260
(Aggressor band : n257, n261) | -23 | -2dBm/100MHz
(-22dBm/MHz) | 0.86 (NOTE 2) | 5 | 1.0
(with relaxation) | +| | n257, n261
(Aggressor band : n260) | -27.7 | -5dBm/100MHz
(-25dBm/MHz) | 2.56 (NOTE 2) | 3.3 | 1.0
(with relaxation) | +| | 23.6 GHz ≤ f ≤ 24.0GHz | -27.7 | 1dBm/200MHz
(-22 dBm/MHz) | 5.56 (NOTE 2) | 0.3 | 1.0
(with relaxation) | +| | 36 GHz ≤ f ≤ 37GHz | -23dBm/MHz | 7dBm/1000MHz
(-23dBm/MHz) | -0.14 (NOTE 2) | 6 | 1.0
(with relaxation) | +| | 57 GHz ≤ f ≤ 66GHz | N/A | 2dBm/100MHz
(-18dBm/MHz) | 5.86 (NOTE 1) | 0 | 1.0 | +| Additional spurious emission | NS_202
(7.25GHz <=f <=12.75GHz) | -40 dBm/MHz | -10dBm/100MHz
(-30 dBm/MHz) | 10 (NOTE 1) | 0 | 0.41 | +| | NS_202
(12.75GHz <=f <=23.45GHz) | -23 dBm/MHz | -10dBm/100MHz
(-30 dBm/MHz) | -7.14 (NOTE 2) | 13 | 1.0
(with relaxation) | +| | NS_202
(23.6GHz <=f <=24.0GHz) | -27.7 dBm/MHz | 1dBm/200MHz
(-22 dBm/MHz) | 5.56 (NOTE 2) | 0.3 | 1.0
(with relaxation) | +| | NS_202
(23.45GHz <=f <=40.8GHz) | -23 dBm/MHz | -10dBm/100MHz
(-30 dBm/MHz) | -7.14 (NOTE 2) | 13 | 1.0
(with relaxation) | +| | NS_202
(40.8GHz <=f <=66GHz) | -23 dBm/MHz | -10dBm/100MHz
(-30 dBm/MHz) | -7.14 (NOTE 2) | 13 | 1.0
(with relaxation) | +| | NS_203
(23.6GHz <=f <=24.0GHz) | -27.7 dBm/MHz | +1dBm/200MHz
(-22dBm/MHz) | 5.56 (NOTE 2) | 0.3 | 1.0
(with relaxation) | +| Rx spurious | 6GHz <=f<=20GHz | | -47dBm/1MHz | -2.2 (NOTE 3) | 10.2 | 1.0 dB for 23.45~40.8GHz,
0.64dB for | +| | 20GHz<=f<=40GHz | | -47dBm/1MHz | -11.34 (NOTE 2) | 17.2 | | + +| | | | | | | | +|-----------------|--|--|-------------|----------------|------|--------------------------| +| 40GHz<=f<=80GHz | | | -47dBm/1MHz | -25.1 (NOTE 3) | 33.1 | 6~23.45 and 40.8~80 GHz. | +|-----------------|--|--|-------------|----------------|------|--------------------------| + +NOTE 1: Estimated SNR is calculated based on agreed influence of noise. +NOTE 2: Estimated SNR is calculated based on agreed relaxation value: Estimated SNR = 6dB - relaxation. +NOTE 3: Estimated SNR is calculated based on agreed relaxation value: Estimated SNR = 8dB - relaxation. + +**Table B.2.2.27-1a: Uncertainty value for influence of noise for PC3, MIMO for IFF** + +| Test case | Frequency range | Noise floor | Minimum requirement | Estimated SNR total [dB/400MHz] | Relaxation | Influence of noise | +|----------------------|-----------------|-----------------|---------------------|--------------------------------------------|------------|-----------------------| +| MOP-EIRP | FR2a | N/A | 22.4 dBm/ChBW | 16.33 (NOTE 1) | 0 | 0.1 | +| | FR2b | N/A | 20.6 dBm/ChBW | 11.45 (NOTE 1) | 0 | 0.3 | +| | FR2c | N/A | 18.7 dBm/ChBW | 11.45 (NOTE 1) | 0 | 0.3 | +| MOP-TRP | FR2a | N/A | 23 dBm/ChBW | 16.33 (NOTE 1) | 0 | 0.1 | +| | FR2b, FR2c | N/A | 23 dBm/ChBW | 11.45 (NOTE 1) | 0 | 0.3 | +| MOP-Spherical | FR2a | N/A | 11.5 dBm/ChBW | 11.45 (NOTE 1) | 0 | 0.3 | +| | FR2b | N/A | 8 dBm/ChBW | 6.37 (NOTE 1) | 0 | 0.9 | +| Minimum output power | FR2a | -10.6dBm/400MHz | -10 dBm | -0.46 (NOTE 1) | 5.4 | 1.0 (with relaxation) | +| | FR2b | -5.5dBm/400MHz | -10 dBm | -4.64 (NOTE 1) | 10.5 | 1.0 (with relaxation) | +| OFF power – TRP | FR2a | N/A | -35dBm/ChBW | -24.54 (NOTE 2) | 30.4 | 1.0 (with relaxation) | +| | FR2b | N/A | | <-24.54 (NOTE 2) | N/A | Propose not to test | + +NOTE 1: Estimated SNR is calculated based on agreed influence of noise. + +**Table B.2.2.27-2: Uncertainty value for influence of noise for PC1, SISO for IFF** + +| Test case | Frequency range | Relaxation [dB] | Influence of noise [dB] | +|------------------------------|--------------------------------------------|---------------------------------------------|-------------------------| +| MOP-EIRP | FR2a | 0 | 0.13 | +| | FR2b | 0 | 0.2 | +| MOP-TRP | FR2a | 0 | 0.13 | +| | FR2b | 0 | 0.27 | +| MOP-Spherical | FR2a | 0 | 0.2 | +| | FR2b | 0 | 0.35 | +| MPR | FR2a | 0 | 0.13 | +| | FR2b | 0 | 0.3 | +| Minimum output power | FR2a | 0 | 0.3 | +| | FR2b | 0 | 0.6 | +| OFF power – TRP | FR2a | Same as defined for PC3 in Table B.2.2.27-1 | | +| | FR2b | Same as defined for PC3 in Table B.2.2.27-1 | | +| SEM | FR2a | 0 | 1.81 (NOTE 1, 2) | +| | FR2b | 0 | TBD | +| ACLR (ACP) | FR2a | 0 | 0.95 | +| | FR2b | 0 | 0.95 | +| General Tx spurious | 6GHz <=f<12.75GHz | Same as defined for PC3 in Table B.2.2.27-1 | | +| | 12.75GHz<=f<66GHz | 0 | 1.08 (NOTE 1, 3) | +| | 66GHz<=f<=80GHz | Same as defined for PC3 in Table B.2.2.27-1 | | +| Tx spurious Co-existence | n260
(Aggressor band : n257, n261) | 5 (Same as PC3) | 2.34 (NOTE 1, 4) | +| | n257, n261
(Aggressor band : n260) | 3.3 (Same as PC3) | 2.34 (NOTE 1, 4) | +| | 23.6 GHz ≤ f ≤ 24.0GHz | 0.3 (Same as PC3) | 2.34 (NOTE 1, 4) | +| | 57 GHz ≤ f ≤ 66GHz | Same as defined for PC3 in Table B.2.2.27-1 | | +| Additional spurious emission | NS_202
(7.25GHz <=f <=12.75GHz) | Same as defined for PC3 in Table B.2.2.27-1 | | +| | NS_202
(12.75GHz <=f <=23.45GHz) | 13 (Same as PC3) | 2.34 (NOTE 1, 4) | +| | NS_202, NS_203
(23.6 GHz ≤ f ≤ 24.0GHz) | 0.3 (Same as PC3) | 2.34 (NOTE 1, 4) | +| | NS_202
(23.45GHz <=f <=40.8GHz) | 13 (Same as PC3) | 2.34 (NOTE 1, 4) | +| | NS_202
(40.8GHz <=f <=66GHz) | 13 (Same as PC3) | 2.34 (NOTE 1, 4) | +| Rx spurious | 6GHz <=f<=20GHz | Same as defined for PC3 in Table B.2.2.27-1 | | +| | 20GHz<=f<=40GHz | Same as defined for PC3 in Table B.2.2.27-1 | | +| | 40GHz<=f<=80GHz | Same as defined for PC3 in Table B.2.2.27-1 | | + +NOTE 1: values assuming up to 6% of grid points with EIRP > 43dBm. + +NOTE 2: values assuming SNR = -7.9dB for points with EIRP > 43dBm / SNR = 8.14dB otherwise. + +NOTE 3: values assuming SNR = -5dB for points with EIRP > 43dBm / SNR = 10dB otherwise. + +NOTE 4: values assuming SNR = -9dB for points with EIRP > 43dBm / SNR = 6dB otherwise and considering the proposed relaxation. + +**Table B.2.2.27-2a: Uncertainty value for influence of noise for PC1, MIMO for IFF** + +| Test case | Frequency range | Relaxation [dB] | Influence of noise [dB] | +|---------------|-----------------|-----------------|-------------------------| +| MOP-EIRP | FR2a | 0 | 0.13 | +| | FR2b | 0 | 0.2 | +| MOP-TRP | FR2a | 0 | 0.13 | +| | FR2b | 0 | 0.27 | +| MOP-Spherical | FR2a | 0 | 0.2 | +| | FR2b | 0 | 0.35 | + +**Table B.2.2.27-3: Uncertainty value for influence of noise for PC5, SISO for IFF** + +| Test case | Frequency range | Relaxation [dB] | Influence of noise [dB] | +|----------------------|-----------------|-----------------------------------|-------------------------| +| MOP-EIRP | FR2a | 0 | 0.13 | +| MOP-TRP | FR2a | 0 | 0.13 | +| MOP-Spherical | FR2a | 0 | 0.2 | +| MPR | FR2a | 0 | 0.13 | +| Minimum output power | FR2a | 1.4dB for 400MHz
0dB otherwise | 1 | +| ACLR (ACP) | FR2a | 0 | 0.95 | + +**Table B.2.2.27-3a: Uncertainty value for influence of noise for PC5, MIMO for IFF** + +| Test case | Frequency range | Relaxation [dB] | Influence of noise [dB] | +|---------------|-----------------|-----------------|-------------------------| +| MOP-EIRP | FR2a | 0 | 0.13 | +| MOP-TRP | FR2a | 0 | 0.13 | +| MOP-Spherical | FR2a | 0 | 0.2 | + +**Table B.2.2.27-4: Uncertainty value for influence of noise for PC6 for IFF** + +| Test case | Frequency range | Relaxation | Influence of noise | +|------------------------------|------------------------------------------|------------|--------------------| +| MOP-EIRP | FR2a | FFS | FFS | +| MOP-TRP | FR2a | FFS | FFS | +| MOP-Spherical | FR2a | FFS | FFS | +| MPR | FR2a | FFS | FFS | +| Minimum output power | FR2a | FFS | FFS | +| OFF power – TRP | FR2a | FFS | | +| SEM | FR2a | FFS | FFS | +| ACLR (ACP) | FR2a | FFS | FFS | +| | 12.75GHz <= f < 66GHz | FFS | FFS | +| Tx spurious Co-existence | n260
(Aggressor band :
n257, n261) | FFS | FFS | +| | n257, n261
(Aggressor band :
n260) | FFS | FFS | +| | 23.6 GHz ≤ f ≤ 24.0GHz | FFS | FFS | +| Additional spurious emission | 23.6 GHz ≤ f ≤ 24.0GHz | FFS | FFS | +| | 20GHz <= f <= 40GHz | FFS | | + +## B.2.2.28 Systematic error related to beam peak search + +See B.2.1.28. + +The uncertainty value of systematic error related to beam peak search is estimated as below table and used across clause B. + +**Table B.2.2.28-1: Uncertainty value for systematic error related to beam peak search for IFF** + +| Power class | Uncertainty value | +|-------------|-------------------| +| PC1, PC5 | 0.7 | +| PC3 | 0.5 | +| PC6 | FFS | + +## B.2.2.29 Influence of spherical coverage grid + +See B.2.1.29. + +The uncertainty value of influence of spherical coverage grid is estimated as below table and used across clause B. + +**Table B.2.2.29-1: Uncertainty value for influence of spherical coverage grid for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC5 | 0.13 | Actual | 1.00 | 0.13 | +| PC3 | 0.12 | Actual | 1.00 | 0.12 | +| PC6 | FFS | Actual | FFS | FFS | + +## B.2.2.30 Systematic error related to EIS spherical coverage + +See B.2.1.30. + +The uncertainty value of systematic error related to EIS spherical coverage is estimated as below table and used across clause B. + +**Table B.2.2.30-1: Uncertainty value for systematic error related to EIS spherical coverage for IFF** + +| Power class | Uncertainty value | +|-------------|-------------------------| +| PC1, PC5 | DL power step size, 0.2 | +| PC3 | DL power step size, 0.2 | +| PC6 | DL power step size, 0.2 | + +## B.2.2.31 Misalignment of DUT due to change of DUT orientation + +See B.2.1.31. + +The uncertainty value of misalignment of DUT due to change of DUT orientation is estimated as below table and used across clause B. + +**Table B.2.2.31-1: Uncertainty value for misalignment of DUT due to change of DUT orientation for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC5 | 0.10 | Actual | 1.00 | 0.10 | +| PC3 | 0.10 | Actual | 1.00 | 0.10 | +| PC6 | 0.10 | Actual | 1.00 | 0.10 | + +## B.2.2.32 Additional Impact of Interferer ACLR + +See B.2.1.32. + +The uncertainty value of additional Impact of Interferer ACLR is estimated as below table and used across clause B. + +**Table B.2.2.32-1: Uncertainty value for additional Impact of Interferer ACLR for IFF** + +| Power class | Uncertainty value | +|--------------------|-------------------| +| PC1, PC3, PC5, PC6 | 0.7 | + +## B.2.2.33 Modulated Interferer uncertainty + +See B.2.1.33. + +The uncertainty value of modulated Interferer uncertainty is estimated as below table and used across clause B. + +**Table B.2.2.33-1: Uncertainty value for modulated Interferer uncertainty for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1, PC5 | 2.9 | Normal | 2 | 1.45 | +| PC3 | 2.9 | Normal | 2 | 1.45 | +| PC6 | 2.9 | Normal | 2 | 1.45 | + +## B.2.2.34 Void + +## B.2.2.35 Influence of offset antenna for blocker signal + +See B.2.1.35. + +## B.2.2.36 Uncertainty of the RF relative power measurement equipment + +See B.2.1.36. + +The uncertainty value of uncertainty of the RF relative power measurement equipment is estimated as below table and used across clause B. + +**Table B.2.2.36-1: Uncertainty value for uncertainty of the RF relative power measurement equipment for IFF** + +| Power class | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------|-------------------|---------------------------------|---------|----------------------------------------| +| PC1 | TBD | Normal | 2 | TBD | +| PC3 | [0.4] | Normal | 2 | [0.2] | +| PC6 | TBD | Normal | 2 | TBD | + +## B.2.3 Measurement error contribution descriptions for NFTF + +### B.2.3.1 Axes Alignment + +Includes the following mechanical alignment errors: + +- The uncertainty related with the lateral displacement between the horizontal and vertical axes of the DUT positioner. +- The differences from 90° of the angle between the horizontal and vertical axes. +- The horizontal mis-pointing of the horizontal axis to the probe reference point for $\Theta=0^\circ$ . + +These mechanical errors can result in sampling the field on a non-ideal sphere. This uncertainty can be considered to have a normal distribution. + +### B.2.3.2 Measurement Distance uncertainty + +See B.2.1.2. + +### B.2.3.3 Quality of the Quiet Zone + +See B.2.1.3. + +### B.2.3.4 Mismatch + +See B.2.1.4. + +### B.2.3.5 Multiple Reflections: Coupling Measurement Antenna and DUT + +The multiple reflections occur when a portion of the transmitted signal is reflected from the receiving antenna back to the transmitting antenna and re-reflected by the transmitting antenna back to the receiving antenna. This uncertainty can be determined by multiple measurements of the DUT when at different distance from the probes. This uncertainty is assumed to have a U-shaped distribution. + +### B.2.3.6 Uncertainty of the RF power measurement equipment + +See B.2.1.6. + +### B.2.3.7 Phase curvature + +See B.2.1.7. + +### **B.2.3.8 Amplifier uncertainties** + +See B.2.1.8. + +### **B.2.3.9 Random uncertainty** + +See B.2.1.9. + +### **B.2.3.10 Influence of the XPD** + +Refer to B.2.1.10. If the Probe Polarization Amplitude and Phase is measured and corrected for then this uncertainty term can be considered to be zero. + +### **B.2.3.11 NF to FF truncation** + +The measured near field is expanded using a finite set of spherical modes. The number of modes is linked to number of samples. The filtering effect generated by the finite number of modes can improve measurement results by removing signals from outside the physical area of the DUT. Care must be taken in order to make sure the removed signals are not from the DUT itself. This term also includes the uncertainty related to the scan area truncation. This uncertainty is usually negligible. This uncertainty is assumed to have a normal distribution. + +### **B.2.3.12 Probe Polarization Amplitude and Phase** + +The amplitude and phase of the probe polarization coefficients should be measured. This uncertainty is assumed to have a normal distribution. + +### **B.2.3.13 Probe Array Uniformity (for multi-probe systems only)** + +This is the uncertainty due to the fact that different probes are used for each physical position. Different probes have different radiation patterns. Generally, the probe array is calibrated so that the uniformity of the probes is achieved. This uncertainty term must be considered if the amplitude and phase of each probe is not identical or corrected for. This uncertainty is assumed to have a normal distribution + +### **B.2.3.14 Uncertainty of the Network Analyzer** + +See B.2.1.14. + +### **B.2.3.15 Uncertainty of the absolute gain of the calibration antenna** + +See B.2.1.15. + +### **B.2.3.16 Phase Recovery Non-Linearity over signal bandwidth** + +This uncertainty originates from the non-linearity of the phase recovery for wide band signal. The phase recovery can be due to either phase non-linearity of the receiver and/or the DUT itself. The method to quantify the non-linearities is not defined. + +### **B.2.3.17 Probe Pattern Effect** + +The probe/s pattern/s is assumed to be known so that the DUT measurement in near field can be corrected when performing the near field to far field transform. If the probe pattern is known, then the uncertainty term is zero. There is + +no direct dependence between the DUT pattern and the probe pattern in near field measurements. This uncertainty is assumed to have a normal distribution. + +### **B.2.3.18 Phase centre offset of calibration** + +See B.2.1.18. + +### **B.2.3.19 Quality of the Quiet Zone for Calibration Process** + +See B.2.1.19. + +### **B.2.3.20 Phase Drift and Noise** + +This uncertainty is due to the noise level and drift of the test range and should be determined or measured at the DUT location. The noise level is usually measured with a Spectrum Analyzer. This uncertainty is assumed to have a normal distribution. + +### **B.2.3.21 Mismatch in the connection of the calibration antenna** + +See B.2.1.4. + +### **B.2.3.22 Influence of TRP measurement grid** + +See B.2.1.22. + +### **B.2.3.23** + +### **B.2.3.24** + +### **B.2.3.25 Leakage and Crosstalk** + +This uncertainty can be addressed by measurements on the actual system setup. The leakage and crosstalk cannot be separated from the random amplitude and phase errors so that the relative importance should be determined. This uncertainty is assumed to have a normal distribution. + +### **B.2.3.26 Systematic error due to TRP calculation/quadrature** + +See B.2.1.24. + +### **B.2.3.27 Multiple measurement antenna uncertainty** + +See B.2.1.25. + +### **B.2.3.28 DUT repositioning** + +See B.2.1.26. + +### **B.2.3.29 Influence of noise** + +See B.2.1.27. + +### B.2.3.30 Uncertainty of the RF relative power measurement equipment + +See B.2.1.36. + +## B.3 UE maximum output power + +Following tables summarize the MU threshold for EIRP and TRP measurements for UE maximum output power. The origin MU values for different test setups with varies parameters can be found in following clauses. + +**Table B.3-1: MU threshold for EIRP measurement for UE maximum output power** + +| Power Class | Diversity | Frequency | MBW | Power (NOTE2) | Threshold MU value for NTC [dB] (NOTE1) | Threshold MU value for ETC [dB] (NOTE1) | +|-------------|------------|----------------------------|--------------|----------------------|-----------------------------------------|-----------------------------------------| +| PC3 | SISO, MIMO | 23.45GHz <= f <= 32.125GHz | BW <= 400MHz | P = Max Output Power | 5.08 | 5.35 | +| | | 32.125GHz < f <= 40.8GHz | | | 5.28 | 5.55 | +| | | 40.8GHz < f <= 44.3GHz | | | 6.64 | 6.78 | +| PC1 | SISO, MIMO | 23.45GHz <= f <= 32.125GHz | BW <= 400MHz | P = Max Output Power | 5.33 | 5.60 | +| | | 32.125GHz < f <= 40.8GHz | | | 5.40 | 5.67 | +| PC5 | SISO, MIMO | 23.45GHz <= f <= 32.125GHz | BW <= 400MHz | P = Max Output Power | 5.33 | 5.60 | + +NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.3.2-2 for PC3 UEs (NTC), in Table B.3.2-8 for PC3 UEs (ETC) and B.3.2-6 (NTC) and B.3.2-9 (ETC) for PC1 and PC5 UEs. + +NOTE 2: Max output power level for device with corresponding power class. + +**Table B.3-2: MU threshold for TRP measurement for UE maximum output power** + +| Power Class | Diversity | Frequency | MBW | Power (NOTE2) | Threshold MU value for NTC [dB] (NOTE 1) | Threshold MU value for ETC [dB] (NOTE 1) | +|-------------|------------|-----------------------------------------|-------------------------|----------------------|------------------------------------------|------------------------------------------| +| PC3 | SISO, MIMO | 23.45GHz $\leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = Max Output Power | 4.61 | 4.87 | +| | | 32.125GHz $< f \leq 40.8\text{GHz}$ | | | 4.81 | 5.07 | +| | | 40.8GHz $< f \leq 44.3\text{GHz}$ | | | 6.16 | TBD | +| PC1 | SISO, MIMO | 23.45GHz $\leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = Max Output Power | 4.64 | 4.90 | +| | | 32.125GHz $< f \leq 40.8\text{GHz}$ | | | 4.78 | 5.04 | +| PC5 | SISO, MIMO | 23.45GHz $\leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = Max Output Power | 4.64 | 4.90 | + +NOTE 1: Total TRP Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.3.2-2 for PC3 UEs (NTC), in Table B.3.2-8 for PC3 UEs (ETC) and B.3.2-6 (NTC) and B.3.2-9 (ETC) for PC1 and PC5 UEs. +NOTE 2: Max output power level for device with corresponding power class. + +**Table B.3-3: MU threshold for Spherical coverage measurement for UE maximum output power** + +| Power Class | Diversity | Frequency | MBW | Power | Threshold MU value (NOTE 1) | +|-------------|------------|-----------------------------------------|-------------------------|---------|-----------------------------| +| PC3 | SISO, MIMO | 23.45GHz $\leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = TBD | 4.78 | +| | | 32.125GHz $< f \leq 40.8\text{GHz}$ | | | 5.38 | +| | | 40.8GHz $< f \leq 44.3\text{GHz}$ | | | TBD | +| PC1 | SISO, MIMO | 23.45GHz $\leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = TBD | 4.69 | +| | | 32.125GHz $< f \leq 40.8\text{GHz}$ | | | 4.84 | +| PC5 | SISO, MIMO | 23.45GHz $\leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = TBD | 4.69 | + +NOTE 1: Total Spherical coverage Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Tables B.3.2-4 for PC3 UEs and B.3.2-7 for PC1 and PC5 UEs + +### B.3.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.3.1-1. + +**Table B.3.1-1: Uncertainty contributions for EIRP and TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| 17 | Influence of spherical coverage grid | B.2.1.29 | +| Stage 1: Calibration measurement | | | +| 18 | Mismatch | B.2.1.4 | +| 19 | Amplifier uncertainties | B.2.1.8 | +| 20 | Misalignment of positioning System | B.2.1.13 | +| 21 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 24 | Phase centre offset of calibration antenna | B.2.1.18 | +| 25 | Quality of quiet zone for calibration process | B.2.1.19 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 27 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 28 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 29 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 30 | Influence of noise | B.2.1.27 | +| 31 | Systematic error related to beam peak search | B.2.1.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{22.65\text{GHz}, 31.1\text{GHz}, 45.1\text{GHz}\}$ , $P = [\text{maximum output power}]$ . +- The uncertainty assessment for EIRP and TRP is provided in Table B.3.1-2. + +**Table B.3.1-2: Uncertainty assessment for EIRP and TRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | | | | | | | | | +| 2 | Measure distance uncertainty | | | | | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | | | | | +| 4 | Mismatch (NOTE 3) | | | | | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | | | | | +| 7 | Phase curvature | | | | | | | | | +| 8 | Amplifier uncertainties | | | | | | | | | +| 9 | Random uncertainty | | | | | | | | | +| 10 | Influence of the XPD | | | | | | | | | +| 11 | Insertion Loss Variation | | | | | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | | | | | +| 13 | Influence of TRP measurement grid (NOTE 5) | 0.25 | Actual | 1 | 0.25 | | | | | +| 14 | Influence of beam peak search grid (NOTE 6) | 0.0 | Actual | 1 | 0.0 | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | | | | | +| 16 | DUT repositioning | | | | | | | | | +| 17 | Influence of spherical coverage grid (NOTE 8) | 0.12 | Actual | 1 | 0.12 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 18 | Mismatch | | | | | | | | | +| 19 | Amplifier uncertainties | | | | | | | | | +| 20 | Misalignment of positioning System | | | | | | | | | +| 21 | Uncertainty of the Network Analyzer | | | | | | | | | +| 22 | Uncertainty of the absolute gain of the calibration antenna | | | | | | | | | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | | | | | +| 24 | Phase centre offset of calibration antenna | | | | | | | | | +| 25 | Quality of quiet zone for calibration process (NOTE 2) | | | | | | | | | +| 26 | Standing wave between reference calibration antenna and measurement antenna | | | | | | | | | +| 27 | Influence of the calibration antenna feed cable | | | | | | | | | +| 28 | Insertion Loss Variation | | | | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | | | | | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 5) | | | | 0.00 | | | | | +| 30 | Influence of noise | | | | | | | | | +| 31 | Systematic error related to beam peak search (NOTE 6) | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ – confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| TRP Expanded uncertainty ( $1.96\sigma$ – confidence interval of 95 %) [dB] | | | | | TBD | | | | | + +- NOTE 1: The impact of phase variation on EIRP shall be taken into account during final MU definition for the test method. +- NOTE 2: The quality of quiet zone is different for EIRP and TRP in normal temperature conditions. For TRP, the standard uncertainty is FFS; for EIRP, the standard uncertainty of quiet zone is FFS. +- NOTE 3: The analysis was done only for the case of operating at max output power, in-band, non-CA. +- NOTE 4: The assessment assumes maximum DUT output power. +- NOTE 5: This contributor shall only be considered for TRP measurements. +- NOTE 6: This contributor shall only be considered for EIRP measurements. +- NOTE 7: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 8: This contributor shall only be considered for spherical EIRP measurements + +## B.3.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.3.2-1. + +**Table B.3.2-1: Uncertainty contributions for EIRP and TRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| 17 | Influence of spherical coverage grid | B.2.2.29 | +| Stage 1: Calibration measurement | | | +| 18 | Mismatch | B.2.2.4 | +| 19 | Amplifier Uncertainties | B.2.2.8 | +| 20 | Misalignment of positioning System | B.2.2.13 | +| 21 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 24 | Phase centre offset of calibration antenna | B.2.2.18 | +| 25 | Quality of quiet zone for calibration process | B.2.2.19 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 27 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 28 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 29 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 30 | Influence of noise | B.2.1.27 | +| 31 | Systematic error related to beam peak search | B.2.2.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , $[P = \text{maximum output power}]$ . +- The uncertainty assessment for EIRP and TRP in normal temperature conditions is provided in Table B.3.2-2 for PC3 UEs and in Table B.3.2-6 for PC1 and PC5 UEs. +- The uncertainty assessment for EIRP and TRP in extreme temperature conditions is provided in Table B.3.2-8 for PC3 UEs and in Table B.3.2-9 for PC1 and PC5 UEs. +- The uncertainty assessment for Spherical coverage is provided in Table B.3.2-4 for PC3 UEs in Table B.3.2-7 for PC1 and PC5 UEs. + +**Table B.3.2-2: Uncertainty assessment for EIRP and TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 1)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 3 | Quality of Quiet Zone (NOTE 1)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 4 | Mismatch
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3)
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.16 | Normal | 2.00 | 1.08 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3)
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 4) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 5) | 0.00 | Actual | 1 | 0.00 | +| 15 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 (NOTE 4)
0.08 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.05 (NOTE 5) | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 20 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | + +| | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------|-------------|------|--------------|--|--|--|--| +| 24 | Quality of quiet zone for calibration process (NOTE 1)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 1)
(40.8GHz $< f \leq 44.3$ GHz) | 0.5 | Actual | 1.00 | 0.5 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 6) | | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 4) | | | | 0.00 | | | | | +| 29 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 0.1 | | | | | +| 29 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | 0.3 | | | | | +| 29 | Influence of noise (40.8GHz $< f \leq 44.3$ GHz) | | | | 0.3 | | | | | +| 30 | Systematic error related to beam peak search (NOTE 5) | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.08 | | | | | +| EIRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.28 | | | | | +| EIRP Expanded uncertainty (40.8GHz $< f \leq 44.3$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.64 | | | | | +| TRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 4.61 | | | | | +| TRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 4.81 | | | | | +| TRP Expanded uncertainty (40.8GHz $< f \leq 44.3$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.16 | | | | | +| NOTE 1: The quality of quiet zone is the same for EIRP and TRP. Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | | | | | | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA and is valid for SISO and MIMO. | | | | | | | | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | | | | | | | | +| NOTE 4: This contributor shall only be considered for TRP measurements. | | | | | | | | | | +| NOTE 5: This contributor shall only be considered for EIRP measurements. | | | | | | | | | | +| NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | +| NOTE 7: Void. | | | | | | | | | | +| NOTE 8: Void | | | | | | | | | | +| NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | | | | | | | | | | + +**Table B.3.2-3: Void** + +**Table B.3.2-4: Uncertainty assessment for Spherical coverage measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 1)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 3 | Quality of Quiet Zone (NOTE 1)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 4 | Mismatch
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3)
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.16 | Normal | 2.00 | 1.08 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3)
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 14 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 15 | Influence of spherical coverage grid | 0.12 | Actual | 1 | 0.12 | +| Stage 1: Calibration measurement | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 19 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 23 | Quality of quiet zone for calibration process (NOTE 1)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | + +| | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------|-------------|------|--------------|--|--|--|--| +| 23 | Quality of quiet zone for calibration process (NOTE 1)
(40.8GHz < f <= 44.3GHz) | 0.5 | Actual | 1.00 | 0.5 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise (23.45GHz <= f <= 32.125GHz) | | | | 0.3 | | | | | +| 27 | Influence of noise (32.125GHz < f <= 40.8GHz) | | | | 0.9 | | | | | +| 27 | Influence of noise (40.8GHz < f <= 44.3GHz) | | | | TBD | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| Spherical coverage Expanded uncertainty (23.45GHz <= f <= 32.125GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 4.78 | | | | | +| Spherical coverage Expanded uncertainty (32.125GHz < f <= 40.8GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.38 | | | | | +| Spherical coverage Expanded uncertainty (40.8GHz < f <= 44.3GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| NOTE 1: The quality of quiet zone is the same for EIRP and TRP. Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | | | | | | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA and is valid for SISO and MIMO. | | | | | | | | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | | | | | | | | +| NOTE 4: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | | | | | | | | + +**Table B.3.2-5: Void** + +**Table B.3.2-6: Uncertainty assessment for EIRP and TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | 2.16 | Normal | 2.00 | 1.08 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 4) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 5) | 0.00 | Actual | 1 | 0.00 | +| 15 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 (NOTE 4)
0.35 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.20 (NOTE 5) | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 24 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | 0.4 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Systematic uncertainties (NOTE 6) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 4) | | | | 0.00 | +| 29 | Influence of noise (23.45GHz $\leq f \leq$ 32.125GHz) | | | | 0.13 | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| 29 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | 0.27 (NOTE 4)
0.20 (NOTE 5) | +| 30 | Systematic error related to beam peak search (NOTE 5) | 0.7 | +| | Total measurement uncertainty | Value | +| | EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 5.33 | +| | EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 5.40 | +| | TRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 4.64 | +| | TRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 4.78 | +| NOTE 1: The quality of quiet zone is the same for EIRP and TRP. Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA and is valid for SISO and MIMO. | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | +| NOTE 4: This contributor shall only be considered for TRP measurements. | | | +| NOTE 5: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 7: Void. | | | +| NOTE 8: Void | | | +| NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.3.2-7: Uncertainty assessment for Spherical coverage measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.60 | Actual | 1.00 | 0.60 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | 2.16 | Normal | 2.00 | 1.08 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | | | | | +| 14 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 15 | Influence of spherical coverage grid | 0.13 | Actual | 1 | 0.13 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.40 | Actual | 1.00 | 0.40 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.20 | | | | | +| 27 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 0.35 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| Spherical coverage Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 4.69 | | | | | +| Spherical coverage Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 4.84 | | | | | + +- NOTE 1: The quality of quiet zone is the same for EIRP and TRP. Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. +- NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA and is valid for SISO and MIMO. +- NOTE 3: The assessment assumes maximum DUT output power. +- NOTE 4: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.3.2-8: Uncertainty assessment for EIRP and TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 1) (NOTE 8) | 0.9 | Actual | 1.00 | 0.9 | +| 4 | Mismatch (23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch (40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) (23.45GHz $\leq f \leq 40.8$ GHz) | 2.16 | Normal | 2.00 | 1.08 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) (40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 4) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 5) | 0.00 | Actual | 1 | 0.00 | +| 15 | Multiple measurement antenna uncertainty (NOTE 7) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 (NOTE 4)
0.08 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.05 (NOTE 5) | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Uncertainty of the Network Analyzer (23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 20 | Uncertainty of the Network Analyzer (40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 24 | Quality of quiet zone for calibration process (NOTE 1) (NOTE 8) | 0.6 | Actual | 1.00 | 0.6 | + +| | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|------|-------------|------|--------------|--|--|--|--| +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| | Systematic uncertainties (NOTE 6) | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 4) | | | | 0.00 | | | | | +| 29 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.1 | | | | | +| 29 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 0.3 | | | | | +| 30 | Systematic error related to beam peak search (NOTE 5) | | | | 0.5 | | | | | +| | Total measurement uncertainty | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.35 | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.55 | | | | | +| EIRP Expanded uncertainty ( $40.8\text{GHz} < f \leq 44.3\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.78 | | | | | +| TRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 4.87 | | | | | +| TRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.07 | | | | | +| TRP Expanded uncertainty ( $40.8\text{GHz} < f \leq 44.3\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| NOTE 1: The quality of quiet zone is the same for EIRP and TRP. Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. The ETC QoQZ MU and ETC calibration path losses shall be applied to the NTC test cases if the ETC environment is used for NTC test cases. | | | | | | | | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA and is valid for SISO and MIMO. | | | | | | | | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | | | | | | | | +| NOTE 4: This contributor shall only be considered for TRP measurements. | | | | | | | | | | +| NOTE 5: This contributor shall only be considered for EIRP measurements. | | | | | | | | | | +| NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | +| NOTE 7: Applies to the system which has a structure of mechanical feed antenna positioning. | | | | | | | | | | +| NOTE 8: For n259 in ETC, QoQZ MU factor only defined for EIRP. | | | | | | | | | | + +**Table B.3.2-9: Uncertainty assessment for EIRP and TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.90 | Actual | 1.00 | 0.90 | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | 2.16 | Normal | 2.00 | 1.08 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 4) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 5) | 0.00 | Actual | 1 | 0.00 | +| 15 | Multiple measurement antenna uncertainty (NOTE 7) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 (NOTE 4)
0.35 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.20 (NOTE 5) | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 24 | Quality of quiet zone for calibration process (NOTE 1) | 0.60 | Actual | 1.00 | 0.60 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Systematic uncertainties (NOTE 6) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 4) | | | | 0.00 | +| 29 | Influence of noise (23.45GHz $\leq f \leq$ 32.125GHz) | | | | 0.13 | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| 29 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | 0.27 (NOTE 4)
0.20 (NOTE 5) | +| 30 | Systematic error related to beam peak search (NOTE 5) | 0.7 | +| | Total measurement uncertainty | Value | +| | EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 5.60 | +| | EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 5.67 | +| | TRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 4.90 | +| | TRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | 5.04 | +| NOTE 1: The quality of quiet zone is the same for EIRP and TRP. Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. The ETC QoQZ MU and ETC calibration path losses shall be applied to the NTC test cases if the ETC environment is used for NTC test cases. | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA and is valid for SISO and MIMO. | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | +| NOTE 4: This contributor shall only be considered for TRP measurements. | | | +| NOTE 5: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 7: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +### B.3.3 Uncertainty budget format and assessment for NFTF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.3.3-1. + +**Table B.3.3-1: Uncertainty contributions for EIRP and TRP measurement** + +| UID | Description of uncertainty contribution | Details in paragraph | +|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------| +| Stage 2: EIRP Near Field Radiation Pattern Measurement and EIRP Near Field DUT power measurement | | | +| 1 | Axis Alignment | B.2.3.1 | +| 2 | Measurement Distance Uncertainty | B.2.3.2 | +| 3 | Quality of the Quiet Zone | B.2.3.3 | +| 4 | Mismatch | B.2.3.4 | +| 5 | Multiple Reflections: Coupling between Measurement Antenna and DUT | B.2.3.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.3.6 | +| 7 | Phase curvature | B.2.3.7 | +| 8 | Amplifier uncertainties | B.2.3.8 | +| 9 | Random uncertainty | B.2.3.9 | +| 10 | Influence of the XPD | B.2.3.10 | +| 11 | NF to FF truncation | B.2.3.11 | +| 12 | Probe Polarization Amplitude and Phase | B.2.3.12 | +| 13 | Probe Array Uniformity (for multi-probe systems only) | B.2.3.13 | +| 14 | Phase Recovery Non-Linearity over signal bandwidth | B.2.3.16 | +| 15 | Probe Pattern Effect | B.2.3.17 | +| 16 | Phase Drift and Noise | B.2.3.20 | +| 17 | Leakage and Crosstalk | B.2.3.25 | +| Stage 1: Calibration measurement | | | +| 18 | Mismatch | B.2.3.4 | +| 19 | Amplifier uncertainties | B.2.3.8 | +| 20 | Uncertainty of the Network Analyzer | B.2.3.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.3.15 | +| 22 | Phase centre offset of calibration | B.2.3.18 | +| 23 | Quality of the Quiet Zone for Calibration Process | B.2.3.19 | +| 24 | Mismatch in the connection of the calibration antenna | B.2.3.21 | + +The uncertainty assessment table is organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{22.65\text{GHz}, 31.1\text{GHz}, 45.1\text{GHz}\}$ , $P = [\text{maximum output power}]$ . +- The uncertainty assessment for EIRP and TRP is provided in Table B.3.1-2. + +**Table B.3.3-2: Uncertainty assessment for EIRP and TRP measurement (f=TBD, D=TBD)** + +| UID | Description of uncertainty contribution | Uncertainty Value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: EIRP Near Field Radiation Pattern Measurement and EIRP Near Field DUT power measurement | | | | | | +| 1 | Axis Alignment | | | | | +| 2 | Measurement Distance Uncertainty | | | | | +| 3 | Quality of the Quiet Zone | | | | | +| 4 | Mismatch | | | | | +| 5 | Multiple Reflections: Coupling between Measurement Antenna and DUT | | | | | +| 6 | Uncertainty of the RF power measurement equipment | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | NF to FF truncation | | | | | +| 12 | Probe Polarization Amplitude and Phase | | | | | +| 13 | Probe Array Uniformity (for multi-probe systems only) | | | | | +| 14 | Phase Recovery Non-Linearity over signal bandwidth | | | | | +| 15 | Probe Pattern Effect | | | | | +| 16 | Phase Drift and Noise | | | | | +| 17 | Leakage and Crosstalk | | | | | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | | | | | +| 19 | Amplifier uncertainties | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Phase centre offset of calibration | | | | | +| 23 | Quality of the Quiet Zone for Calibration Process | | | | | +| 24 | Mismatch in the connection of the calibration antenna | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| TRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| NOTE 1: The impact of phase variation on EIRP shall be taken into account during final MU definition for the test method. | | | | | | +| NOTE 2: The quality of quiet zone is different for EIRP and TRP. For TRP, the standard uncertainty is FFS; for EIRP FFS. | | | | | | +| NOTE 3: The analysis was done only for the case of operating at max output power, in-band, non-CA | | | | | | +| NOTE 4: The assessment assumes maximum DUT output power. | | | | | | +| NOTE 5: The Phase Recovery Non-Linearity over signal bandwidth is shall be taken into account during final MU definition for the test method. | | | | | | + +## B.4 UE maximum output power for modulation / channel bandwidth + +Following tables summarize the MU threshold for EIRP measurements for UE maximum output power for modulation / channel bandwidth (a.k.a Maximum Power Reduction/MPR). The origin MU values for different test setups with varies parameters can be found in following clauses. + +**Table B.4-1: MU threshold for EIRP measurement for UE maximum output power for modulation / channel bandwidth** + +| Power Class | Frequency | MBW | Power (NOTE2) | Threshold MU value for NTC [dB] (NOTE1) | Threshold MU value for ETC [dB] (NOTE1) | +|-------------|----------------------------------------|---------------------|------------------------------------------|-----------------------------------------|-----------------------------------------| +| PC3 | 23.45GHz
$\leq f \leq$
32.125GHz | BW $\leq$
400MHz | P = Max Output Power –MBR – MPR – T(MPR) | 5.11 | 5.38 | +| | 32.125GHz
$z < f \leq$
40.8GHz | | | 5.29 | 5.56 | +| | 40.8GHz $< f \leq$
44.3GHz | | | TBD | TBD | +| PC1 | 23.45GHz
$\leq f \leq$
32.125GHz | BW $\leq$
400MHz | P = Max Output Power –MPR – T(MPR) | 5.33 | 5.60 | +| | 32.125GHz
$z < f \leq$
40.8GHz | | | 5.50 | 5.77 | +| PC5 | 23.45GHz
$\leq f \leq$
32.125GHz | BW $\leq$
400MHz | P = Max Output Power –MPR – T(MPR) | 5.33 | 5.60 | + +NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.4.2-2 and Table B.4.2-3 for PC3 UEs and Table B.4.2-4 and Table B.4.2-5 for PC1 and PC5 UEs. +NOTE 2: Max output power level for device with corresponding power class. + +### B.4.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.4.1-1. + +**Table B.4.1-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----|-----------------------------------------|------------------| +| | Same as Table 3.1-1 for EIRP | | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of $D = 5$ cm, $f = \{22.65\text{GHz}, 31.1\text{GHz}, 45.1\text{GHz}\}$ , $P = \text{maximum output power} - \text{MBR} - \text{MPR} - T(\text{MPR})$ . +- The uncertainty assessment for EIRP is provided in Table B.4.1-2. + +**Table B.4.1-2: Uncertainty assessment for EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 to 17 | Same as Stage 2 of Table 3.1-2 for EIRP | | | | | +| Stage 1: Calibration measurement | | | | | | +| 18 to 28 | Same as Stage 1 of Table 3.1-2 for EIRP | | | | | +| | Systematic uncertainties | | | | Value | +| 29 | Systematic error due to TRP calculation/quadrature | | | | N/A | +| 30 | Influence of noise | | | | | +| 31 | Systematic error related to beam peak search | | | | Same as Table 3.1-2 | +| | Total measurement uncertainty | | | | Value | +| | EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | TBD | +| | TRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | TBD | +| NOTE 1: The assessment assumes maximum DUT output power – MBR – MPR – T(MPR) | | | | | | + +## B.4.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.4.2-1. + +**Table B.4.2-1: Uncertainty contributions for EIRP and TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----|-----------------------------------------|------------------| +| | Same as Stage 2 of Table 3.2-1 for EIRP | | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , $P = \text{maximum output power} - \text{MPR} - T(\text{MPR})$ . +- The uncertainty assessment for EIRP and TRP is provided in Table B.3.2-2 for PC3 UEs and in Table B.4.2-x for PC1 UEs. + +**Table B.4.2-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 to 16 | Same as Stage 2 of Table B.3.2-2 for EIRP | | | | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 to 27 | Same as Stage 1 of Table B.3.2-2 for EIRP | | | | | | | | | +| | Systematic uncertainties | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature | | | | N/A | | | | | +| 29 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 0.13 | | | | | +| 29 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | 0.31 | | | | | +| 29 | Influence of noise (40.8GHz $< f \leq 44.3$ GHz) | | | | TBD | | | | | +| 30 | Systematic error related to beam peak search | | | | Same as Table B.3.2-2 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.11 | | | | | +| EIRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.29 | | | | | +| EIRP Expanded uncertainty (40.8GHz $< f \leq 44.3$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| NOTE 1: The assessment assumes maximum DUT output power – MBR - MPR – T(MPR) | | | | | | | | | | + +**Table B.4.2-3: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 to 16 | Same as Stage 2 of Table B.3.2-8 for EIRP | | | | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 to 27 | Same as Stage 1 of Table B.3.2-8 for EIRP | | | | | | | | | +| | Systematic uncertainties | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature | | | | N/A | | | | | +| 29 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 0.13 | | | | | +| 29 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | 0.31 | | | | | +| 30 | Systematic error related to beam peak search | | | | Same as Table B.3.2-8 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.38 | | | | | +| EIRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.56 | | | | | +| NOTE 1: The assessment assumes maximum DUT output power – MBR - MPR – T(MPR) | | | | | | | | | | + +**Table B.4.2-4: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 to 16 | Same as Stage 2 of Table B.3.2-6 for EIRP | | | | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 to 27 | Same as Stage 1 of Table B.3.2-6 for EIRP | | | | | | | | | +| | Systematic uncertainties | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature | | | | N/A | | | | | +| 29 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 0.13 | | | | | +| 29 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | 0.3 | | | | | +| 30 | Systematic error related to beam peak search | | | | Same as Table B.3.2-6 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.33 | | | | | +| EIRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.50 | | | | | +| NOTE 1: The assessment assumes maximum DUT output power – MPR – T(MPR) | | | | | | | | | | + +**Table B.4.2-5: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 to 16 | Same as Stage 2 of Table B.3.2-9 for EIRP | | | | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 to 27 | Same as Stage 1 of Table B.3.2-9 for EIRP | | | | | | | | | +| | Systematic uncertainties | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature | | | | N/A | | | | | +| 29 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 0.13 | | | | | +| 29 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | 0.3 | | | | | +| 30 | Systematic error related to beam peak search | | | | Same as Table B.3.2-9 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.60 | | | | | +| EIRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.77 | | | | | +| NOTE 1: The assessment assumes maximum DUT output power – MPR – T(MPR) | | | | | | | | | | + +### B.4.3 Uncertainty budget format and assessment for NFTF + +FFS + +## B.5 UE maximum output power with additional requirements + +FFS + +## B.6 Configured transmitted power with Power Boost + +Following tables summarize the MU threshold for EIRP measurements for UE maximum output power. The origin MU values for different test setups with varies parameters can be found in following clauses. + +**Table B.6-1: MU threshold for EIRP measurement for Configured transmitted power with Power Boost** + +| Power Class | Frequency | MBW | Power (NOTE2) | Threshold MU value for NTC [dB] (NOTE1) | Threshold MU value for ETC [dB] (NOTE1) | +|-------------|-------------------------------------|------------------|----------------------|-----------------------------------------|-----------------------------------------| +| PC3 | 23.45GHz
$\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.08 | 5.35 | +| | 32.125GHz
$z < f \leq 40.8GHz$ | | | 5.28 | 5.55 | +| PC1 | 23.45GHz
$\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | FFS | FFS | +| | 32.125GHz
$z < f \leq 40.8GHz$ | | | FFS | FFS | + +NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30cm$ in Table B.6.2-2 for PC3 UEs (NTC), in Table B.6.2-8 for PC3 UEs (ETC) and B.6.2-6 for PC1 UEs. +NOTE 2: Max output power level for device with corresponding power class. + +### B.6.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.6.1-1. + +**Table B.6.1-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of beam peak search grid | B.2.1.23 | +| 14 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 15 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.1.4 | +| 17 | Amplifier uncertainties | B.2.1.8 | +| 18 | Misalignment of positioning System | B.2.1.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 22 | Phase centre offset of calibration antenna | B.2.1.18 | +| 23 | Quality of quiet zone for calibration process | B.2.1.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 26 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 27 | Influence of noise | B.2.1.27 | +| 28 | Systematic error related to beam peak search | B.2.1.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of D = [5 cm], f = {22.65GHz, 31.1GHz, 45.1GHz}, P = [maximum output power]. +- The uncertainty assessment for EIRP is provided in Table B.6.1-2. + +**Table B.6.1-2: Uncertainty assessment for EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | | | | | | | | | +| 2 | Measure distance uncertainty | | | | | | | | | +| 3 | Quality of quiet zone | | | | | | | | | +| 4 | Mismatch (NOTE 2) | | | | | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | | | | | | | | | +| 7 | Phase curvature | | | | | | | | | +| 8 | Amplifier uncertainties | | | | | | | | | +| 9 | Random uncertainty | | | | | | | | | +| 10 | Influence of the XPD | | | | | | | | | +| 11 | Insertion Loss Variation | | | | | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | | | | | +| 13 | Influence of beam peak search grid | 0.0 | Actual | 1 | 0.0 | | | | | +| 14 | Multiple measurement antenna uncertainty | | | | | | | | | +| 15 | DUT repositioning | | | | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | | | | | | | | | +| 17 | Amplifier uncertainties | | | | | | | | | +| 18 | Misalignment of positioning System | | | | | | | | | +| 19 | Uncertainty of the Network Analyzer | | | | | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | | | | | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | | | | | +| 22 | Phase centre offset of calibration antenna | | | | | | | | | +| 23 | Quality of quiet zone for calibration process | | | | | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | | | | | | | | | +| 25 | Influence of the calibration antenna feed cable | | | | | | | | | +| 26 | Insertion Loss Variation | | | | | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise | | | | | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| NOTE 1: The impact of phase variation on EIRP shall be taken into account during final MU definition for the test method. | | | | | | | | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA. | | | | | | | | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | | | | | | | | +| NOTE 4: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | + +## B.6.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.6.2-1. + +**Table B.6.2-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of beam peak search grid | B.2.2.23 | +| 14 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 15 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.2.4 | +| 17 | Amplifier Uncertainties | B.2.2.8 | +| 18 | Misalignment of positioning System | B.2.2.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 22 | Phase centre offset of calibration antenna | B.2.2.18 | +| 23 | Quality of quiet zone for calibration process | B.2.2.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 26 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 27 | Influence of noise | B.2.1.27 | +| 28 | Systematic error related to beam peak search | B.2.2.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ , $[P = \text{maximum output power}]$ . +- The uncertainty assessment for EIRP is provided in Table B.6.2-2 for PC3 UEs and in Table B.6.2-6 for PC1 UEs. + +**Table B.6.2-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | 2.16 | Normal | 2.00 | 1.08 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.1 | | | | | +| 27 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 0.3 | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.08 | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.28 | | | | | + +- NOTE 1: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. +- NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA. +- NOTE 3: The assessment assumes maximum DUT output power. +- NOTE 4: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.6.2-3: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | FFS | Rectangular | 1.73 | FFS | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | FFS | Actual | 1.00 | FFS | | | | | +| 4 | Mismatch | FFS | Actual | 1.00 | FFS | | | | | +| 5 | Standing wave between the DUT and measurement antenna | FFS | U-shaped | 1.41 | FFS | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | FFS | Normal | 2.00 | FFS | | | | | +| 7 | Phase curvature | FFS | U-shaped | 1.41 | FFS | | | | | +| 8 | Amplifier uncertainties | FFS | Normal | 2.00 | FFS | | | | | +| 9 | Random uncertainty | FFS | Normal | 2.00 | FFS | | | | | +| 10 | Influence of the XPD | FFS | U-shaped | 1.41 | FFS | | | | | +| 11 | Insertion Loss Variation | FFS | Rectangular | 1.73 | FFS | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | FFS | Actual | 1.00 | FFS | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 5) | FFS | Actual | 1 | FFS | | | | | +| 15 | DUT repositioning | 0.35 | Rectangular | 1.73 | 0.20 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | FFS | U-shaped | 1.41 | FFS | | | | | +| 17 | Amplifier Uncertainties | FFS | Normal | 2.00 | FFS | | | | | +| 18 | Misalignment of positioning System | FFS | Normal | 2.00 | FFS | | | | | +| 19 | Uncertainty of the Network Analyzer | FFS | Normal | 2.00 | FFS | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | FFS | Normal | 2.00 | FFS | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | FFS | Rectangular | 1.73 | FFS | | | | | +| 22 | Phase centre offset of calibration antenna | FFS | Rectangular | 1.73 | FFS | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | FFS | Actual | 1.00 | FFS | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | FFS | U-shaped | 1.41 | FFS | | | | | +| 25 | Influence of the calibration antenna feed cable | FFS | Normal | 2.00 | FFS | | | | | +| 26 | Insertion Loss Variation | FFS | Rectangular | 1.73 | FFS | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | FFS | | | | | +| 27 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | FFS | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.7 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | | | | | + +- NOTE 1: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. +- NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA. +- NOTE 3: The assessment assumes maximum DUT output power. +- NOTE 4: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.6.2-4: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.9 | Actual | 1.00 | 0.9 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | 2.16 | Normal | 2.00 | 1.08 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.1 | | | | | +| 27 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 0.3 | | | | | +| 28 | Systematic error related to beam peak search (NOTE 5) | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.35 | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.55 | | | | | + +- NOTE 1: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. The ETC QoQZ MU and ETC calibration path losses shall be applied to the NTC test cases if the ETC environment is used for NTC test cases. +- NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA. +- NOTE 3: The assessment assumes maximum DUT output power. +- NOTE 4: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.6.2-5: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | FFS | Rectangular | 1.73 | FFS | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | FFS | Actual | 1.00 | FFS | | | | | +| 4 | Mismatch | FFS | Actual | 1.00 | FFS | | | | | +| 5 | Standing wave between the DUT and measurement antenna | FFS | U-shaped | 1.41 | FFS | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3) | FFS | Normal | 2.00 | FFS | | | | | +| 7 | Phase curvature | FFS | U-shaped | 1.41 | FFS | | | | | +| 8 | Amplifier uncertainties | FFS | Normal | 2.00 | FFS | | | | | +| 9 | Random uncertainty | FFS | Normal | 2.00 | FFS | | | | | +| 10 | Influence of the XPD | FFS | U-shaped | 1.41 | FFS | | | | | +| 11 | Insertion Loss Variation | FFS | Rectangular | 1.73 | FFS | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | FFS | Actual | 1.00 | FFS | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 5) | FFS | Actual | 1 | FFS | | | | | +| 15 | DUT repositioning | 0.35 | Rectangular | 1.73 | 0.20 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | FFS | U-shaped | 1.41 | FFS | | | | | +| 17 | Amplifier Uncertainties | FFS | Normal | 2.00 | FFS | | | | | +| 18 | Misalignment of positioning System | FFS | Normal | 2.00 | FFS | | | | | +| 19 | Uncertainty of the Network Analyzer | FFS | Normal | 2.00 | FFS | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | FFS | Normal | 2.00 | FFS | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | FFS | Rectangular | 1.73 | FFS | | | | | +| 22 | Phase centre offset of calibration antenna | FFS | Rectangular | 1.73 | FFS | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | FFS | Actual | 1.00 | FFS | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | FFS | U-shaped | 1.41 | FFS | | | | | +| 25 | Influence of the calibration antenna feed cable | FFS | Normal | 2.00 | FFS | | | | | +| 26 | Insertion Loss Variation | FFS | Rectangular | 1.73 | FFS | | | | | +| Systematic uncertainties (NOTE 4) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | FFS | | | | | +| 27 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | FFS | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.7 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | +| NOTE 2: | The analysis was done only for the case of operating at max output power, in-band, non-CA. | +| NOTE 3: | The assessment assumes maximum DUT output power. | +| NOTE 4: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 5: | Applies to the system which has a structure of mechanical feed antenna positioning. | + +### B.6.3 Uncertainty budget format and assessment for NFTF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.6.3-1. + +**Table B.6.3-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in paragraph | +|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------| +| Stage 2: EIRP Near Field Radiation Pattern Measurement and EIRP Near Field DUT power measurement | | | +| 1 | Axis Alignment | B.2.3.1 | +| 2 | Measurement Distance Uncertainty | B.2.3.2 | +| 3 | Quality of the Quiet Zone | B.2.3.3 | +| 4 | Mismatch | B.2.3.4 | +| 5 | Multiple Reflections: Coupling between Measurement Antenna and DUT | B.2.3.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.3.6 | +| 7 | Phase curvature | B.2.3.7 | +| 8 | Amplifier uncertainties | B.2.3.8 | +| 9 | Random uncertainty | B.2.3.9 | +| 10 | Influence of the XPD | B.2.3.10 | +| 11 | NF to FF truncation | B.2.3.11 | +| 12 | Probe Polarization Amplitude and Phase | B.2.3.12 | +| 13 | Probe Array Uniformity (for multi-probe systems only) | B.2.3.13 | +| 14 | Phase Recovery Non-Linearity over signal bandwidth | B.2.3.16 | +| 15 | Probe Pattern Effect | B.2.3.17 | +| 16 | Phase Drift and Noise | B.2.3.20 | +| 17 | Leakage and Crosstalk | B.2.3.25 | +| Stage 1: Calibration measurement | | | +| 18 | Mismatch | B.2.3.4 | +| 19 | Amplifier uncertainties | B.2.3.8 | +| 20 | Uncertainty of the Network Analyzer | B.2.3.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.3.15 | +| 22 | Phase centre offset of calibration | B.2.3.18 | +| 23 | Quality of the Quiet Zone for Calibration Process | B.2.3.19 | +| 24 | Mismatch in the connection of the calibration antenna | B.2.3.21 | + +The uncertainty assessment table is organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{22.65\text{GHz}, 31.1\text{GHz}, 45.1\text{GHz}\}$ , $P = [\text{maximum output power}]$ . +- The uncertainty assessment for EIRP is provided in Table B.6.1-2. + +**Table B.6.3-2: Uncertainty assessment for EIRP measurement (f=TBD, D=TBD)** + +| UID | Description of uncertainty contribution | Uncertainty Value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: EIRP Near Field Radiation Pattern Measurement and EIRP Near Field DUT power measurement | | | | | | +| 1 | Axis Alignment | | | | | +| 2 | Measurement Distance Uncertainty | | | | | +| 3 | Quality of the Quiet Zone | | | | | +| 4 | Mismatch | | | | | +| 5 | Multiple Reflections: Coupling between Measurement Antenna and DUT | | | | | +| 6 | Uncertainty of the RF power measurement equipment | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | NF to FF truncation | | | | | +| 12 | Probe Polarization Amplitude and Phase | | | | | +| 13 | Probe Array Uniformity (for multi-probe systems only) | | | | | +| 14 | Phase Recovery Non-Linearity over signal bandwidth | | | | | +| 15 | Probe Pattern Effect | | | | | +| 16 | Phase Drift and Noise | | | | | +| 17 | Leakage and Crosstalk | | | | | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | | | | | +| 19 | Amplifier uncertainties | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Phase centre offset of calibration | | | | | +| 23 | Quality of the Quiet Zone for Calibration Process | | | | | +| 24 | Mismatch in the connection of the calibration antenna | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| NOTE 1: The impact of phase variation on EIRP shall be taken into account during final MU definition for the test method. | | | | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA | | | | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | | | | +| NOTE 4: The Phase Recovery Non-Linearity over signal bandwidth shall be taken into account during final MU definition for the test method. | | | | | | + +## B.7 Minimum Output power + +Following tables summarize the MU threshold for EIRP measurements for Minimum Output Power. The origin MU values for different test setups can be found in following clauses. + +**Table B.7-1: MU threshold for EIRP measurement for Minimum output power** + +| Power Class | Diversity | Frequency | MBW | Power | Threshold MU value for NTC [dB] (NOTE1) | Threshold MU value For ETC [dB] (NOTE1) | +|-------------|------------|------------------------------------------------|--------------------------------|--------------------------|-----------------------------------------|-----------------------------------------| +| PC1 | SISO | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | $\text{BW} \leq 400\text{MHz}$ | P = Minimum Output Power | 5.66 | 5.92 | +| | | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | 5.96 | 6.22 | +| PC3 | SISO, MIMO | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | $\text{BW} \leq 400\text{MHz}$ | P = Minimum Output Power | 6.15 | 6.41 | +| | | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | 6.15 | 6.41 | +| | | $40.8\text{GHz} < f \leq 44.3\text{GHz}$ | | | TBD | TBD | +| PC5 | SISO, MIMO | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | $\text{BW} \leq 400\text{MHz}$ | P = Minimum Output Power | 6.36 | 6.62 | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.7.2-2 and Table B.7.2-5 for PC3 UEs and Table B.7.2-3 and Table B.7.2-6 for PC1 and PC5 UEs. + +## B.7.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.7.1-1. + +**Table B.7.1-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of beam peak search grid | B.2.1.23 | +| 14 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 15 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.1.4 | +| 17 | Amplifier uncertainties | B.2.1.8 | +| 18 | Misalignment of positioning System | B.2.1.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 22 | Phase centre offset of calibration antenna | B.2.1.18 | +| 23 | Quality of quiet zone for calibration process | B.2.1.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 26 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 27 | Systematic error related to beam peak search | B.2.1.28 | +| 28 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}, 44.3 \text{ GHz}\}$ , $P = [\text{Minimum output power}]$ . +- The uncertainty assessment for EIRP is provided in Table B.7.1-2. + +**Table B.7.1-2: Uncertainty assessment for EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | +| 4 | Mismatch (NOTE 3) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of beam peak search grid (NOTE 6) | | | | | +| 14 | Multiple measurement antenna uncertainty | | | | | +| 15 | DUT repositioning | | Actual | 1 | | +| Stage 1: Calibration measurement | | | | | | +| 16 | Mismatch | | | | | +| 17 | Amplifier uncertainties | | | | | +| 18 | Misalignment of positioning System | | | | | +| 19 | Uncertainty of the Network Analyzer | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 22 | Phase centre offset of calibration antenna | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 2) | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 25 | Influence of the calibration antenna feed cable | | | | | +| 26 | Insertion Loss Variation | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | +| 27 | Systematic error related to beam peak search | | | | | +| 28 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| EIRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The analysis was done only for the case of operating at Minimum output power, in-band, non-CA. | +| NOTE 2: | The assessment assumes DUT Minimum output power. | +| NOTE 3: | This contributor shall only be considered for EIRP measurements. | +| NOTE 4: | Void | +| NOTE 5: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 6: | Void. | +| NOTE 7: | Void | +| NOTE 8: | Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | +| NOTE 9: | Applies to the system which has a structure of mechanical feed antenna positioning. | + +## B.7.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.7.2-1. + +**Table B.7.2-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of beam peak search grid | B.2.2.23 | +| 14 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 15 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.2.4 | +| 17 | Amplifier Uncertainties | B.2.2.8 | +| 18 | Misalignment of positioning System | B.2.2.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 22 | Phase centre offset of calibration antenna | B.2.2.18 | +| 23 | Quality of quiet zone for calibration process | B.2.2.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 26 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 27 | Systematic error related to beam peak search | B.2.2.28 | +| 28 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , P = Minimum output power. +- The uncertainty assessment for EIRP is provided in Table B.7.2-2 for PC3 UEs and in Table B.7.2-3 for PC1 UEs. + +**Table B.7.2-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 8)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 3 | Quality of Quiet Zone (NOTE 8)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 4 | Mismatch (NOTE 1)
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch (NOTE 1)
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2)
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.50 | Normal | 2.00 | 1.25 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2)
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of beam peak search grid (NOTE 3) | 0.00 | Actual | 1 | 0.00 | +| 14 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | +| 15 | DUT repositioning (NOTE 3) | 0.08 | Rectangular | 1.73 | 0.05 | +| Stage 1: Calibration measurement | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 19 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 23 | Quality of quiet zone for calibration process (NOTE 8)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | + +| | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------|-------------|------|--------------|--|--|--|--| +| 23 | Quality of quiet zone for calibration process (NOTE 8)
(40.8GHz < f <= 44.3GHz) | 0.5 | Actual | 1.00 | 0.5 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| 28 | Influence of noise (23.45GHz <= f <= 32.125GHz) | | | | 1.0 | | | | | +| 28 | Influence of noise (32.125GHz < f <= 40.8GHz) | | | | 1.0 | | | | | +| 28 | Influence of noise (40.8GHz < f <= 44.3GHz) | | | | TBD | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz <= f <= 32.125GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.15 | | | | | +| EIRP Expanded uncertainty (32.125GHz < f <= 40.8GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.15 | | | | | +| EIRP Expanded uncertainty (40.8GHz < f <= 44.3GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| NOTE 1: The analysis was done only for the case of operating at Minimum output power, in-band, non-CA and is valid for SISO and MIMO. | | | | | | | | | | +| NOTE 2: The assessment assumes DUT Minimum output power. | | | | | | | | | | +| NOTE 3: This contributor shall only be considered for EIRP measurements. | | | | | | | | | | +| NOTE 4: Void | | | | | | | | | | +| NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | +| NOTE 6: Void. | | | | | | | | | | +| NOTE 7: Void | | | | | | | | | | +| NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | | | | | | | | +| NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | | | | | | | | | | + +**Table B.7.2-3: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.60 | Actual | 1.00 | 0.60 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid (NOTE 3) | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning (NOTE 3) | 0.35 | Rectangular | 1.73 | 0.20 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 8) | 0.40 | Actual | 1.00 | 0.40 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search | | | | 0.7 | | | | | +| 28 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) (PC1) | | | | 0.30 | | | | | +| 28 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) (PC5) | | | | 1.00 | | | | | +| 28 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) (PC1) | | | | 0.60 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] (PC1) | | | | | 5.66 | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] (PC5) | | | | | 6.36 | | | | | + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] (PC1) | 5.96 | +| NOTE 1: The analysis was done only for the case of operating at Minimum output power, in-band, non-CA and is valid for SISO and for PC5 also for MIMO. For PC1 and MIMO the analysis is FFS.
NOTE 2: The assessment assumes DUT Minimum output power.
NOTE 3: This contributor shall only be considered for EIRP measurements.
NOTE 4: Void
NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 6: Void.
NOTE 7: Void
NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm.
NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | | + +NOTE: MU assessment in Table B.7.2-2 and Table B.7.2-3 is based on the following relaxations for 400MHz BW: + +**Table B.7.2-4: Minimum output power requirement relaxation considered in MU assessment for 400 MHz EIRP measurement ( $f=23.45\text{GHz}$ , $32.125\text{GHz}$ , $40.8\text{GHz}$ , $44.3\text{GHz}$ , Quiet Zone size $\leq 30\text{ cm}$ )** + +| Power Class | Diversity | Frequency Range | Relaxation (dB) | +|-------------|------------|-----------------|-----------------| +| PC1 | SISO | FR2a | 0 | +| | | FR2b | 0 | +| PC2 | SISO | FR2a | FFS | +| | | FR2b | FFS | +| PC3 | SISO | FR2a | 8.4 | +| | | FR2b | 13.5 | +| | | FR2c | FFS | +| PC3 | MIMO | FR2a | 5.4 | +| | | FR2b | 10.5 | +| | | FR2c | FFS | +| PC4 | SISO | FR2a | FFS | +| | | FR2b | FFS | +| PC5 | SISO, MIMO | FR2a | 1.4 | + +**Table B.7.2-5: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.9 | Actual | 1.00 | 0.9 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid (NOTE 3) | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning (NOTE 3) | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 8) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| 28 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 1.0 | | | | | +| 28 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | 1.0 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.41 | | | | | +| EIRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.41 | | | | | + +- | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: The analysis was done only for the case of operating at Minimum output power, in-band, non-CA and is valid for SISO and MIMO.
NOTE 2: The assessment assumes DUT Minimum output power.
NOTE 3: This contributor shall only be considered for EIRP measurements.
NOTE 4: Void
NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 6: Void.
NOTE 7: Void
NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm.
NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: MU assessment in Table B.7.2-5 is based on the relaxations for 400MHz BW in Table B.7.2-4. + +**Table B.7.2-6: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.90 | Actual | 1 | 0.90 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1 | 0.00 | | | | | +| 13 | Influence of beam peak search grid (NOTE 3) | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning (NOTE 3) | 0.35 | Rectangular | 1.73 | 0.20 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 8) | 0.60 | Actual | 1 | 0.60 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search | | | | 0.70 | | | | | +| 28 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) (PC1) | | | | 0.30 | | | | | +| 28 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) (PC5) | | | | 1.00 | | | | | +| 28 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) (PC1) | | | | 0.60 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] (PC1) | | | | | 5.92 | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] (PC5) | | | | | 6.62 | | | | | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] (PC1) | 6.22 | +| NOTE 1: The analysis was done only for the case of operating at Minimum output power, in-band, non-CA and is valid for SISO and for PC5 also for MIMO. For PC1 and MIMO the analysis is FFS.. | | +| NOTE 2: The assessment assumes DUT Minimum output power. | | +| NOTE 3: This contributor shall only be considered for EIRP measurements. | | +| NOTE 4: Void | | +| NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | +| NOTE 6: Void. | | +| NOTE 7: Void | | +| NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | +| NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | | + +## B.8 Transmit OFF power + +Following tables summarize the MU threshold for TRP measurements for Transmit OFF power. The origin MU values for different test setups can be found in following clauses. + +**Table B.8-1: MU threshold for TRP measurement for Transmit OFF power** + +| Power Class | Diversity | Frequency | MBW | Power | Threshold MU value (NOTE1) | +|------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------|-------------------------|---------------|----------------------------| +| PC3 | SISO, MIMO | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = Off Power | 5.67 | +| | | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | N/A | +| PC1 | SISO, MIMO | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | P = Off Power | 5.67 | +| | | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | N/A | +| NOTE 1: Total TRP Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.8.2-2 for PC3 UEs and Table B.8.2-6 for PC1 UEs. | | | | | | + +**Table B.8-2: Void** + +### B.8.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.8.1-1. + +**Table B.8.1-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.1.4 | +| 18 | Amplifier uncertainties | B.2.1.8 | +| 19 | Misalignment of positioning System | B.2.1.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 23 | Phase centre offset of calibration antenna | B.2.1.18 | +| 24 | Quality of quiet zone for calibration process | B.2.1.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 27 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 29 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}\}$ , $P = [\text{Off power}]$ . +- The uncertainty assessment for TRP is provided in Table B.8.1-2. + +**Table B.8.1-2: Uncertainty assessment for TRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | +| 4 | Mismatch (NOTE 3) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of TRP measurement grid (NOTE 5) | | | | | +| 14 | Influence of beam peak search grid (NOTE 6) | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | +| 16 | DUT repositioning | | Actual | 1 | | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | | | | | +| 18 | Amplifier uncertainties | | | | | +| 19 | Misalignment of positioning System | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 23 | Phase centre offset of calibration antenna | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 2) | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 26 | Influence of the calibration antenna feed cable | | | | | +| 27 | Insertion Loss Variation | | | | | +| TRP Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 5) | | | | | +| 29 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| TRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The impact of phase variation on EIRP is FFS. | +| NOTE 2: | The quality of quiet zone is different for EIRP and TRP. For TRP, the standard uncertainty is FFS; for EIRP, the standard uncertainty of quiet zone is FFS. | +| NOTE 3: | The analysis was done only for the case of operating at max output power, in-band, non-CA. | +| NOTE 4: | The assessment assumes maximum DUT output power. | +| NOTE 5: | This contributor shall only be considered for TRP measurements. | +| NOTE 6: | This contributor shall only be considered for EIRP measurements. | +| NOTE 7: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | + +## B.8.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.8.2-1. + +**Table B.8.2-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.2.4 | +| 18 | Amplifier Uncertainties | B.2.2.8 | +| 19 | Misalignment of positioning System | B.2.2.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 23 | Phase centre offset of calibration antenna | B.2.2.18 | +| 24 | Quality of quiet zone for calibration process | B.2.2.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 27 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 29 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ , $P = \text{Off power}$ . +- The uncertainty assessment for TRP is provided in Table B.8.2-2 for PC3 UEs and Table B.8.2-6 for PC1 UEs. + +**Table B.8.2-2: Uncertainty assessment for TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of TRP measurement grid (NOTE 3) | 0.25 | Actual | 1 | 0.25 | | | | | +| 14 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 15 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 8) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 3) | | | | 0.0 | | | | | +| 29 | Influence of noise (23.45GHz $\leq f \leq 32.125$ GHz) | | | | 1.0 | | | | | +| 29 | Influence of noise (32.125GHz $< f \leq 40.8$ GHz) | | | | N/A | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| TRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.67 | | | | | +| TRP Expanded uncertainty (32.125GHz $< f \leq 40.8$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | N/A | | | | | + +- NOTE 1: The analysis was done only for the case of operating at TX OFF power, in-band, non-CA and is valid for SISO and MIMO. +- NOTE 2: The assessment assumes DUT Off power. +- NOTE 3: This contributor shall only be considered for TRP measurements. +- NOTE 4: Void +- NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 6: Void. +- NOTE 7: Void +- NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. +- NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.8.2-3: Void** + +**Table B.8.2-4: Void** + +**Table B.8.2-5: Void** + +**Table B.8.2-6: Uncertainty assessment for TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, +Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of TRP measurement grid (NOTE 3) | 0.25 | Actual | 1 | 0.25 | | | | | +| 14 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 15 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 8) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 3) | | | | 0.0 | | | | | +| 29 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 1.0 | | | | | +| 29 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | N/A | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| TRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.67 | | | | | +| TRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | N/A | | | | | + +- NOTE 1: The analysis was done only for the case of operating at TX OFF power, in-band, non-CA and is valid for SISO and MIMO. +- NOTE 2: The assessment assumes DUT Off power. +- NOTE 3: This contributor shall only be considered for TRP measurements. +- NOTE 4: Void +- NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 6: Void. +- NOTE 7: Void +- NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. +- NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. + +NOTE: MU assessment in Table B.8.2-2 and Table B.8.2-6 for FR2a is based on the relaxation of 30.4dB for 400MHz BW. + +## B.9 ON/OFF time mask + +### B.9.1 ON power subtest + +MU threshold for EIRP measurements in the ON power subtest in the Transmit ON/OFF time mask test case is specified in Table B.3-1. The origin MU values for different test setups can be found in following subclauses. + +#### B.9.1.1 Uncertainty budget format and assessment for DFF + +Uncertainty budget format and assessment for IFF for EIRP measurement is contained in clause B.3.1. + +#### B.9.1.2 Uncertainty budget format and assessment for IFF + +Uncertainty budget format and assessment for IFF for EIRP measurement is contained in clause B.3.2. + +### B.9.2 OFF power subtest + +MU threshold for EIRP measurements in the OFF power subtest in the Transmit ON/OFF time mask test case. The origin MU values for different test setups can be found in following subclauses. + +**Table B.9.2-1: MU threshold for EIRP measurement for Transmit OFF power** + +| Frequency | CBW | Power | Threshold MU value for NTC [dB] (NOTE1) | Threshold MU value for ETC [dB] (NOTE1) | +|-------------------------------------------------------------------------------------------------------|--------|---------------|-----------------------------------------|-----------------------------------------| +| 23.45GHz <= f <= 32.125GHz | 50MHz | P = Off Power | 6.15 | 6.41 | +| | 100MHz | | | | +| | 200MHz | | | | +| | 400MHz | | | | +| 32.125GHz < f <= 40.8GHz | 50MHz | P = Off Power | 6.15 | 6.41 | +| | 100MHz | | | | +| | 200MHz | | | | +| | 400MHz | | | | +| NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.8.2-4 for PC3 UEs | | | | | + +### B.9.2.1 Uncertainty budget format and assessment for DFF + +FFS + +### B.9.2.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9.2.2-1. + +**Table B.9.2.2-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.2.4 | +| 18 | Amplifier Uncertainties | B.2.2.8 | +| 19 | Misalignment of positioning System | B.2.2.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 23 | Phase centre offset of calibration antenna | B.2.2.18 | +| 24 | Quality of quiet zone for calibration process | B.2.2.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 27 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 29 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ , P = Off power. + +**Table B.9.2.2-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid (NOTE 3) | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning (NOTE 3) | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 8) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| 28 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 1 | | | | | +| 28 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 1 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.15 | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.15 | | | | | + +- NOTE 1: The analysis was done only for the case of operating at TX OFF power, in-band, non-CA. +- NOTE 2: The assessment assumes DUT Off power. +- NOTE 3: This contributor shall only be considered for EIRP measurements. +- NOTE 4: Void +- NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 6: Void. +- NOTE 7: Void +- NOTE 8: Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. +- NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.9.2.2-3: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 8) | 0.9 | Actual | 1.00 | 0.9 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid (NOTE 3) | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 9) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning (NOTE 3) | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 8) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| 28 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 1 | | | | | +| 28 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 1 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.41 | | | | | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.41 | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The analysis was done only for the case of operating at TX OFF power, in-band, non-CA. | +| NOTE 2: | The assessment assumes DUT Off power. | +| NOTE 3: | This contributor shall only be considered for EIRP measurements. | +| NOTE 4: | Void | +| NOTE 5: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 6: | Void. | +| NOTE 7: | Void | +| NOTE 8: | Value based on procedure defined in Annex D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | +| NOTE 9: | Applies to the system which has a structure of mechanical feed antenna positioning. | + +NOTE: MU assessment in Table B.9.2.2-2 and Table B.9.2.2-3 is based on the relaxation in Table B.9.2.2-4. + +**Table B.9.2.2-4: Transmit OFF power (EIRP) requirement relaxation considered in MU assessment (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm)** + +| Frequency | Power Class | Relaxation | | | | +|-----------------------------------|-------------|------------|-------------|-------------|-------------| +| | | CHBW 50MHz | CHBW 100MHz | CHBW 200MHz | CHBW 400MHz | +| 23.45GHz $\leq f \leq 32.125$ GHz | PC1 | EIRP - 1dB | EIRP + 2dB | EIRP + 5dB | EIRP + 8dB | +| | PC2 | FFS | FFS | FFS | FFS | +| | PC3 | EIRP - 1dB | EIRP + 2dB | EIRP + 5dB | EIRP + 8dB | +| | PC4 | FFS | FFS | FFS | FFS | +| 32.125GHz $\leq f \leq 40.8$ GHz | PC1 | EIRP + 2dB | EIRP + 5dB | EIRP + 8dB | EIRP + 11dB | +| | PC2 | FFS | FFS | FFS | FFS | +| | PC3 | EIRP + 2dB | EIRP + 5dB | EIRP + 8dB | EIRP + 11dB | +| | PC4 | FFS | FFS | FFS | FFS | + +NOTE: EIRP is the measured UE rms ON power level in ON/OFF time mask testing. + +## B.9a Power control + +### B.9a.1 Absolute power tolerance + +### B.9a.2 Relative power control tolerance + +#### B.9a.2.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9a.2.1-1. + +**Table B.9a.2.1-1: Uncertainty contributions for EIRP relative power control tolerance measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.1.36 | +| 2 | Amplifier uncertainties | B.2.1.8 | +| 3 | Impact of frequency response | FFS | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 4 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of D = [5 cm], f = {22.65GHz, 31.1GHz, 45.1GHz}, P = [maximum output power]. +- The uncertainty assessment for EIRP relative power control tolerance is provided in Table B.9a.2.1-2. + +**Table B.9a.2.1-2: Uncertainty assessment for EIRP relative power control tolerance measurement +(f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | FFS | FFS | FFS | FFS | +| 2 | Amplifier uncertainties | FFS | FFS | FFS | FFS | +| 3 | Impact of frequency response | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 4 | Influence of noise | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +## B.9a.2.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9a.2.2-1. + +**Table B.9a.2.2-1: Uncertainty contributions for EIRP relative power control tolerance measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.2.36 | +| 2 | Amplifier uncertainties | B.2.2.8 | +| 3 | Impact of frequency response | FFS | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 4 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment for EIRP relative power control tolerance is provided in Table B.9a.2.2-2. for PC3 UEs and in Table B.9a.2.2-3 for PC1 UEs. + +**Table B.9a.2.2-2: Uncertainty assessment for EIRP relative power control tolerance measurement ( $f=23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}$ , Quiet Zone size $\leq 30 \text{ cm}$ ) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | [0.4] | Normal | 2.00 | [0.2] | +| 2 | Amplifier uncertainties | 0.5 | Rectangular | 1.73 | 0.29 | +| 3 | Impact of frequency response | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 4 | Influence of noise ( $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ ) | | | | 1.0 | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | [1.7] | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | +| NOTE 2: Power step size assumed $\Delta P = 1 \text{ dB}$ . | | | | | | +| NOTE 3: Measurement uncertainties in this table assume absolute power measurements involved in the same relative power measurement are performed over the same RF path. | | | | | | + +**Table B.9a.2.2-3: Uncertainty assessment for EIRP relative power control tolerance measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Uncertainty of the RF power measurement equipment | FFS | Normal | 2.0 | FFS | | | | | +| 2 | Amplifier uncertainties | FFS | Rectangular | 1.73 | FFS | | | | | +| 3 | Impact of frequency response | FFS | FFS | FFS | FFS | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| | N/A | | | | | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | | | | | +| 4 | Influence of noise (23.45GHz $\leq f \leq 40.8$ GHz) | | | | FFS | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | | | | | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | + +### B.9a.2.3 Uncertainty budget format and assessment for NFTF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9a.2.3-1. + +**Table B.9a.2.3-1: Uncertainty contributions for EIRP relative power control tolerance measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.3.30 | +| 2 | Amplifier uncertainties | B.2.3.8 | +| 3 | Impact of frequency response | FFS | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 4 | Influence of noise | B.2.3.29 | + +The uncertainty assessment table is organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of D = [5 cm], f = {22.65GHz, 31.1GHz, 45.1GHz}, P = [maximum output power]. +- The uncertainty assessment for EIRP relative power control tolerance is provided in Table B.9a.2.3-2 + +**Table B.9a.2.3-2: Uncertainty assessment for EIRP relative power control tolerance measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | FFS | FFS | FFS | FFS | +| 2 | Amplifier uncertainties | FFS | FFS | FFS | FFS | +| 3 | Impact of frequency response | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 4 | Influence of noise | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +## B.9a.3 Aggregate Power control tolerance + +### B.9a.3.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9a.3.1-1. + +**Table B.9a.3.1-1: Uncertainty contributions for EIRP aggregate power control tolerance measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.1.36 | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 2 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{22.65\text{GHz}, 31.1\text{GHz}, 45.1\text{GHz}\}$ , $P = [\text{maximum output power}]$ . +- The uncertainty assessment for EIRP aggregate power control tolerance is provided in Table B.9a.3.1-2. + +**Table B.9a.3.1-2: Uncertainty assessment for EIRP aggregate power control tolerance measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 2 | Influence of noise | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +### B.9a.3.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9a.3.2-1. + +**Table B.9a.3.2-1: Uncertainty contributions for EIRP aggregate power control tolerance measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.2.36 | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 2 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment for EIRP aggregate power control tolerance is provided in Table B.9a.3.2-2 for PC3 UEs and in Table B.9a.3.2-3 for PC1 UEs. + +**Table B.9a.3.2-2: Uncertainty assessment for EIRP aggregate power control tolerance measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | 0.4 | Normal | 2.00 | 0.2 | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 2 | Influence of noise (23.45GHz $\leq f \leq 40.8$ GHz) | | | | 1.0 | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 1.4 | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 2: Power step size assumed $\Delta P = 1$ dB.
NOTE 3: Measurement uncertainties in this table assume absolute power measurements involved in the same relative power measurement are performed over the same RF path. | | | | | | + +**Table B.9a.3.2-3: Uncertainty assessment for EIRP aggregate power control tolerance measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF power measurement equipment | FFS | Normal | 2.0 | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 2 | Influence of noise (23.45GHz $\leq f \leq 40.8$ GHz) | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty (23.45GHz $\leq f \leq 32.125$ GHz) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +### B.9a.3.3 Uncertainty budget format and assessment for NFTF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.9a.3.3-1. + +**Table B.9a.3.3-1: Uncertainty contributions for EIRP aggregate power control tolerance measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.3.30 | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 2 | Influence of noise | B.2.3.29 | + +The uncertainty assessment table is organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of D = [5 cm], f = {22.65GHz, 31.1GHz, 45.1GHz}, P = [maximum output power]. +- The uncertainty assessment for EIRP aggregate power control tolerance is provided in Table B.9a.3.3-2 + +**Table B.9a.3.3-2: Uncertainty assessment for EIRP aggregate power control tolerance measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 2 | Influence of noise | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +## B.10 Frequency error + +Following tables summarize the MU threshold for EIRP measurements for Frequency error. The origin MU values for different test setups can be found in following subclauses. + +**Table B.10-1: MU threshold for beam peak measurement for Frequency error** + +| Power Class | Frequency | MBW | Power | Threshold MU value for NTC and ETC (NOTE1) | +|-------------|-----------------------------------|-------------------|----------------------|--------------------------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | +/- 0.01 ppm | +| | 32.125GHz $< f \leq 40.8$ GHz | | | +/- 0.01 ppm | +| | 40.8GHz $< f \leq 44.3$ GHz | | | | +| PC1 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | +/- 0.01 ppm | +| | 32.125GHz $< f \leq 40.8$ GHz | | | +/- 0.01 ppm | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30$ cm in section B.10.2 + +## B.10.1 Uncertainty budget format and assessment for DFF + ++/- 0.01 ppm + +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}, 44.3 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . This uncertainty has no dependency with extreme temperature conditions. + +## B.10.2 Uncertainty budget format and assessment for IFF + ++/- 0.01 ppm + +- The uncertainty assessment has been derived for the case of Quiet zone size $\leq [30 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}, 44.3 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . + +## B.11 Carrier leakage + +**Editor's Note: MU value analysis for PC1, 2 and 4 are not complete.** + +Following tables summarize the MU threshold for EIRP measurements for carrier leakage. The origin MU values for different test setups can be found in following subclauses. + +**Table B.11-1: MU threshold for EIRP measurement for carrier leakage** + +| Power Class | Frequency | MBW | Power (NOTE2) | Threshold MU value for NTC [dB] (NOTE 1) | +|-------------|-----------------------------------|-------------------|---------------------------------------------------------------|------------------------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = 0 + MU to 0 + (MU + Uplink power control window size) dBm | 5.44 | +| | 32.125GHz $< f \leq 40.8$ GHz | | | 5.57 | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------|-----|-----| +| PC1 | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | BW $\leq 400\text{MHz}$ | FFS | FFS | +| | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | FFS | +| NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.11.2-2 for PC3 UEs and FFS for PC1 UEs | | | | | + +## B.11.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.11.1-1. + +**Table B.11.1-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.1.4 | +| 18 | Amplifier uncertainties | B.2.1.8 | +| 19 | Misalignment of positioning System | B.2.1.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 23 | Phase centre offset of calibration antenna | B.2.1.18 | +| 24 | Quality of quiet zone for calibration process | B.2.1.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 27 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 29 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D + +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . +- The uncertainty assessment is provided in Table B.11.1-2. + +**Table B.11.1-2: Uncertainty assessment for EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | +| 4 | Mismatch (NOTE 3) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of TRP measurement grid (NOTE 5) | | | | | +| 14 | Influence of beam peak search grid (NOTE 6) | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | +| 16 | DUT repositioning | | | | | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | | | | | +| 18 | Amplifier uncertainties | | | | | +| 19 | Misalignment of positioning System | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 23 | Phase centre offset of calibration antenna | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 2) | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 26 | Influence of the calibration antenna feed cable | | | | | +| 27 | Insertion Loss Variation | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 5) | | | | | +| 29 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| EIRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The impact of phase variation on EIRP is FFS. | +| NOTE 2: | The quality of quiet zone is different for EIRP and TRP. For TRP, the standard uncertainty is FFS; for EIRP, the standard uncertainty of quiet zone is FFS. | +| NOTE 3: | The analysis was done only for the case of operating at 0dBm output power, in-band, non-CA. | +| NOTE 4: | The assessment assumes 0 dBm UE output power – carrier leakage requirement. | +| NOTE 5: | This contributor shall only be considered for TRP measurements. | +| NOTE 6: | This contributor shall only be considered for EIRP measurements. | +| NOTE 7: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 8: | Void | + +## B.11.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.12.2-1. + +**Table B.11.2-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.2.4 | +| 18 | Amplifier Uncertainties | B.2.2.8 | +| 19 | Misalignment of positioning System | B.2.2.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 23 | Phase centre offset of calibration antenna | B.2.2.18 | +| 24 | Quality of quiet zone for calibration process | B.2.2.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 27 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 29 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ , for PC3 with measured UE power in the range $0\text{dBm} + \text{MU}$ to $0\text{dBm} + \text{MU} + \text{uplink power control window size}$ , where + - MU is the test system uplink absolute power measurement uncertainty for minimum output power in Table B.7.2-2. + - Uplink power control window size = 1dB (UE power step size) + 5 dB (UE power step tolerance) + (Test system uplink relative power measurement uncertainty), where, the UE power step tolerance is specified in TS 38.101-1 [2], Table 6.3.4.3-1 and is 5dB for 1dB power step size, and the Test system uplink relative power measurement uncertainty is specified in Table F.1.2-1 in TS 38.521-2 for TC 6.4.2.2 with a value of 1.4 dB. +- The uncertainty assessment for EIRP is provided in Table B.17.2-2 for PC3 UEs and Table B.17.2-3 for PC1 UEs. + +**Table B.11.2-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|--------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 10) | 0.52 | Actual | 1.00 | 0.52 | | | | | +| 4 | Mismatch (NOTE 2) | 1.84 | Actual | 1.00 | 1.84 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3, 7) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of TRP measurement grid (NOTE 4) | 0.0 | Actual | 1 | 0.0 | | | | | +| 14 | Influence of beam peak search grid (NOTE 5) | 0.00 | Actual | 1 | 0.00 | | | | | +| 15 | Multiple measurement antenna uncertainty (NOTE 9) | 0.0 | Actual | 1 | 0.0 | | | | | +| 16 | DUT repositioning (NOTE 4) | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 10) | 0.32 | Actual | 1.00 | 0.32 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.24 | | | | | +| Systematic uncertainties (NOTE 6) | | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 4) | | | | 0.00 | | | | | +| 29 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.20 | | | | | +| 29 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 0.33 | | | | | +| 30 | Beam peak search | | | | 0.00 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP total measurement uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) [dB] | | | | | 5.44 | | | | | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| EIRP total measurement uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) [dB] | 5.57 | +| NOTE 1: Void | | +| NOTE 2: The analysis was done only for the case of measured UE power in the range from 0dBm + MU to 0dBm + MU + uplink power control window size, in-band, non-CA. | | +| NOTE 3: The assessment assumes measured power in the range from 0dBm + MU – carrier leakage requirement to 0dBm + MU + uplink power control window – carrier leakage requirement. | | +| NOTE 4: This contributor shall only be considered for TRP measurements. | | +| NOTE 5: Void | | +| NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | +| NOTE 7: Void | | +| NOTE 8: Void | | +| NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. | | +| NOTE 10: Defined as fixed value MU contributor. | | + +**Table B.11.2-3: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | FFS | Rectangular | 1.73 | FFS | +| 3 | Quality of Quiet Zone (NOTE 10) | FFS | Actual | 1.00 | FFS | +| 4 | Mismatch (NOTE 2, NOTE 7) | FFS | Actual | 1.00 | FFS | +| 5 | Standing wave between the DUT and measurement antenna | FFS | U-shaped | 1.41 | FFS | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3, 7) | FFS | Normal | 2.00 | FFS | +| 7 | Phase curvature | FFS | U-shaped | 1.41 | FFS | +| 8 | Amplifier uncertainties | FFS | Normal | 2.00 | FFS | +| 9 | Random uncertainty | FFS | Normal | 2.00 | FFS | +| 10 | Influence of the XPD | FFS | U-shaped | 1.41 | FFS | +| 11 | Insertion Loss Variation | FFS | Rectangular | 1.73 | FFS | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | FFS | Actual | 1.00 | FFS | +| 13 | Influence of TRP measurement grid (NOTE 4) | 0.00 | Actual | 1 | 0.00 | +| 14 | Influence of beam peak search grid (NOTE 5) | 0.00 | Actual | 1 | 0.00 | +| 15 | Multiple measurement antenna uncertainty (NOTE 9) | FFS | Actual | 1 | FFS | +| 16 | DUT repositioning (NOTE 4) | 0.00 | Rectangular | 1.73 | 0.00 | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | FFS | U-shaped | 1.41 | FFS | +| 18 | Amplifier Uncertainties | FFS | Normal | 2.00 | FFS | +| 19 | Misalignment of positioning System | FFS | Normal | 2.00 | FFS | +| 20 | Uncertainty of the Network Analyzer | FFS | Normal | 2.00 | FFS | +| 21 | Uncertainty of the absolute gain of the calibration antenna | FFS | Normal | 2.00 | FFS | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | FFS | Rectangular | 1.73 | FFS | +| 23 | Phase centre offset of calibration antenna | FFS | Rectangular | 1.73 | FFS | +| 24 | Quality of quiet zone for calibration process (NOTE 10) | FFS | Actual | 1.00 | FFS | +| 25 | Standing wave between reference calibration antenna and measurement antenna | FFS | U-shaped | 1.41 | FFS | +| 26 | Influence of the calibration antenna feed cable | FFS | Normal | 2.00 | FFS | +| 27 | Insertion Loss Variation | FFS | Rectangular | 1.73 | FFS | +| TRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| Systematic uncertainties (NOTE 6) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 4) | | | | 0.00 | +| 29 | Influence of noise | | | | FFS | +| 30 | Beam peak search | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP total measurement uncertainty [dB] | | | | | FFS | + +- NOTE 1: Void +- NOTE 2: The analysis was done only for the case of measured UE power in the range from FFS to FFS, in-band, non-CA. +- NOTE 3: The assessment assumes measured power in the range from FFS to FFS. +- NOTE 4: This contributor shall only be considered for TRP measurements. +- NOTE 5: Void +- NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 7: Void. +- NOTE 8: Void. +- NOTE 9: Applies to the system which has a structure of mechanical feed antenna positioning. +- NOTE 10: Defined as fixed value MU contributor. + +## B.12 Error Vector Magnitude + +Following tables summarize the MU threshold for Error Vector Magnitude (EVM) measurements. The origin MU values for different test setups can be found in following subclauses. + +**Table B.12-1: MU threshold for beam peak measurement for Frequency error** + +| Power Class | Frequency | MBW | Power | Threshold MU value for NTC and ETC (NOTE1) | +|-------------|------------------------------------------------|--------------------------------|-------------------------------|--------------------------------------------| +| PC3 | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | $\text{BW} \leq 400\text{MHz}$ | $P = \text{Max Output Power}$ | PUSCH:
Table B.12.2-1. | +| | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | Otherwise:
FFS | +| PC1 | $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ | $\text{BW} \leq 400\text{MHz}$ | $P = \text{Max Output Power}$ | PUSCH:
Table B.12.2-5 | +| | $32.125\text{GHz} < f \leq 40.8\text{GHz}$ | | | Otherwise:
FFS | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in section B.10.2 + +### B.12.1 Uncertainty budget format and assessment for DFF + +FFS + +## B.12.2 Uncertainty budget format and assessment for IFF + +Table B.12.2-1: Measurement Uncertainty (MU) for PUSCH, PC3, FR2a (23.45GHz $\leq f \leq 32.125$ GHz) + +| Test ID | Modulation | RB alloc. | 50MH z | 100M Hz | 200MH z | 400MH z | +|---------|----------------------|------------|--------|---------|---------|---------| +| 1 | DFT-s-OFDM PI/2 BPSK | Inner_Full | 2.78% | 3.85% | 5.44% | 7.69% | +| 2 | DFT-s-OFDM PI/2 BPSK | Outer_Full | 3.10% | 4.16% | 5.88% | 8.99% | +| 3 | DFT-s-OFDM QPSK | Inner_Full | 2.78% | 3.85% | 5.44% | 7.69% | +| 4 | DFT-s-OFDM QPSK | Outer_Full | 3.10% | 4.16% | 5.88% | 8.99% | +| 5 | DFT-s-OFDM 16 QAM | Inner_Full | 3.31% | 4.50% | 6.36% | 11.21% | +| 6 | DFT-s-OFDM 16 QAM | Outer_Full | 3.60% | 4.73% | 6.68% | 11.21% | +| 7 | DFT-s-OFDM 64 QAM | Inner_Full | 4.26% | 5.96% | 8.41% | 15.84% | +| 8 | DFT-s-OFDM 64 QAM | Outer_Full | 5.01% | 7.08% | 9.99% | 15.84% | +| 9 | CP-OFDM QPSK | Inner_Full | 3.60% | 4.73% | 6.68% | 11.89% | +| 10 | CP-OFDM QPSK | Outer_Full | 3.71% | 4.99% | 7.07% | 11.89% | +| 11 | CP-OFDM 16 QAM | Inner_Full | 4.26% | 5.96% | 8.41% | 15.84% | +| 12 | CP-OFDM 16 QAM | Outer_Full | 4.26% | 5.96% | 8.41% | 15.84% | +| 13 | CP-OFDM 64 QAM | Inner_Full | 6.31% | 8.91% | 12.59% | 21.13% | +| 14 | CP-OFDM 64 QAM | Outer_Full | 6.31% | 8.91% | 12.59% | 21.13% | + +Table B.12.2-2: Measurement Uncertainty (MU) for PUSCH, PC3, FR2b (32.125GHz $< f \leq 40.8$ GHz) + +| Test ID | Modulation | RB alloc. | 50MH z | 100MH z | 200MH z | 400MH z | +|---------|----------------------|------------|---------|---------|---------|---------| +| 1 | DFT-s-OFDM PI/2 BPSK | Inner_Full | 3.56% | 4.83% | 6.91% | 9.65% | +| 2 | DFT-s-OFDM PI/2 BPSK | Outer_Full | 4.15% | 5.69% | 8.11% | 12.50% | +| 3 | DFT-s-OFDM QPSK | Inner_Full | 3.56% | 4.83% | 6.91% | 9.65% | +| 4 | DFT-s-OFDM QPSK | Outer_Full | 4.15% | 5.69% | 8.11% | 12.50% | +| 5 | DFT-s-OFDM 16 QAM | Inner_Full | 4.54% | 6.26% | 8.91% | 18.06% | +| 6 | DFT-s-OFDM 16 QAM | Outer_Full | 5.09% | 7.19% | 10.15% | 18.06% | +| 7 | DFT-s-OFDM 64 QAM | Inner_Full | 6.78% | 9.58% | 13.54% | 25.50% | +| 8 | DFT-s-OFDM 64 QAM | Outer_Full | 8.06% | 11.38% | 16.09% | 25.50% | +| 9 | CP-OFDM QPSK | Inner_Full | 5.09% | 7.19% | 10.15% | 19.13% | +| 10 | CP-OFDM QPSK | Outer_Full | 5.39% | 7.61% | 10.75% | 19.13% | +| 11 | CP-OFDM 16 QAM | Inner_Full | 6.78% | 9.58% | 13.54% | 25.50% | +| 12 | CP-OFDM 16 QAM | Outer_Full | 6.78% | 9.58% | 13.54% | 25.50% | +| 13 | CP-OFDM 64 QAM | Inner_Full | 10.14 % | 14.33% | 20.25% | 34.01% | +| 14 | CP-OFDM 64 QAM | Outer_Full | 10.14 % | 14.33% | 20.25% | 34.01% | + +- The uncertainty assessment has been derived for the case of Quiet zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ , $P = [\text{Maximum output power}]$ . +- Values above are calculated considering a TE noise floor assumption of $-10.6 \text{ dBm}/400 \text{ MHz}$ for FR2a and $-8.5 \text{ dBm}/400 \text{ MHz}$ for FR2b and additional TE measurement uncertainty (not related to TE noise floor) as shown in Table B.12-2-3 and Table B.12-2-4 added quadratically. + +**Table B.12.2-3: Additional TE EVM MU (not related to TE noise floor) for PUSCH, PC3, FR2a +( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ )** + +| Test ID | Modulation | RB alloc. | 50MH
z | 100M
Hz | 200MH
z | 400MH
z | +|----------------|----------------------|------------------|-------------------|--------------------|--------------------|--------------------| +| 1 | DFT-s-OFDM PI/2 BPSK | Inner_Full | 2.50% | 3.44% | 4.86% | 6.87% | +| 2 | DFT-s-OFDM PI/2 BPSK | Outer_Full | 2.50% | 3.26% | 4.61% | 6.58% | +| 3 | DFT-s-OFDM QPSK | Inner_Full | 2.50% | 3.44% | 4.86% | 6.87% | +| 4 | DFT-s-OFDM QPSK | Outer_Full | 2.50% | 3.26% | 4.61% | 6.58% | +| 5 | DFT-s-OFDM 16 QAM | Inner_Full | 2.50% | 3.29% | 4.65% | 6.45% | +| 6 | DFT-s-OFDM 16 QAM | Outer_Full | 2.50% | 3.01% | 4.25% | 6.45% | +| 7 | DFT-s-OFDM 64 QAM | Inner_Full | 2.50% | 3.43% | 4.84% | 9.12% | +| 8 | DFT-s-OFDM 64 QAM | Outer_Full | 2.88% | 4.07% | 5.75% | 9.12% | +| 9 | CP-OFDM QPSK | Inner_Full | 2.50% | 3.01% | 4.25% | 6.85% | +| 10 | CP-OFDM QPSK | Outer_Full | 2.50% | 3.16% | 4.48% | 6.85% | +| 11 | CP-OFDM 16 QAM | Inner_Full | 2.50% | 3.43% | 4.84% | 9.12% | +| 12 | CP-OFDM 16 QAM | Outer_Full | 2.50% | 3.43% | 4.84% | 9.12% | +| 13 | CP-OFDM 64 QAM | Inner_Full | 3.63% | 5.12% | 7.25% | 12.16% | +| 14 | CP-OFDM 64 QAM | Outer_Full | 3.63% | 5.12% | 7.25% | 12.16% | + +**Table B.12.2-4: Additional TE EVM MU (not related to TE noise floor) for PUSCH, PC3, FR2b +( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ )** + +| Test ID | Modulation | RB alloc. | 50MH
z | 100M
Hz | 200MH
z | 400MH
z | +|----------------|----------------------|------------------|-------------------|--------------------|--------------------|--------------------| +| 1 | DFT-s-OFDM PI/2 BPSK | Inner_Full | 3.00% | 4.00% | 5.75% | 8.00% | +| 2 | DFT-s-OFDM PI/2 BPSK | Outer_Full | 3.00% | 4.00% | 5.75% | 8.00% | +| 3 | DFT-s-OFDM QPSK | Inner_Full | 3.00% | 4.00% | 5.75% | 8.00% | +| 4 | DFT-s-OFDM QPSK | Outer_Full | 3.00% | 4.00% | 5.75% | 8.00% | +| 5 | DFT-s-OFDM 16 QAM | Inner_Full | 3.00% | 4.00% | 5.75% | 10.93% | +| 6 | DFT-s-OFDM 16 QAM | Outer_Full | 3.08% | 4.35% | 6.14% | 10.93% | +| 7 | DFT-s-OFDM 64 QAM | Inner_Full | 4.10% | 5.79% | 8.19% | 15.44% | +| 8 | DFT-s-OFDM 64 QAM | Outer_Full | 4.87% | 6.88% | 9.73% | 15.44% | +| 9 | CP-OFDM QPSK | Inner_Full | 3.08% | 4.35% | 6.14% | 11.58% | +| 10 | CP-OFDM QPSK | Outer_Full | 3.26% | 4.60% | 6.50% | 11.58% | +| 11 | CP-OFDM 16 QAM | Inner_Full | 4.10% | 5.79% | 8.19% | 15.44% | +| 12 | CP-OFDM 16 QAM | Outer_Full | 4.10% | 5.79% | 8.19% | 15.44% | +| 13 | CP-OFDM 64 QAM | Inner_Full | 6.12% | 8.66% | 12.25% | 20.59% | +| 14 | CP-OFDM 64 QAM | Outer_Full | 6.12% | 8.66% | 12.25% | 20.59% | + +**Table B.12.2-5: Measurement Uncertainty (MU) for PUSCH, PC1, FR2a (23.45GHz $\leq f \leq 32.125\text{GHz}$ )** + +| 50MH | 100MH | 200MH | 400MH | +|-------------|--------------|--------------|--------------| +| Z | Z | Z | Z | +| 2.48% | 3.50% | 4.95% | 7.00% | + +- The uncertainty assessment has been derived for the case of Quiet zone size $\leq [30\text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}\}$ , $P = [\text{Maximum output power}]$ . +- Values above are calculated considering a TE noise floor assumption of -10.6 dBm/400 MHz for FR2a and additional TE measurement uncertainty (not related to TE noise floor) as shown in Table B.12.2-3 added quadratically. + +**Table B.12.2-6: Additional TE EVM MU (not related to TE noise floor) for PUSCH, PC1, FR2a (23.45GHz $\leq f \leq 32.125\text{GHz}$ )** + +| 50MH | 100MH | 200MH | 400MH | +|-------------|--------------|--------------|--------------| +| Z | Z | Z | Z | +| 2.40% | 3.39% | 4.79% | 6.68% | + +## B.13 to B.14 + +## B.15 Occupied bandwidth + +Following tables summarize the MU threshold for EIRP measurements for Occupied bandwidth. The origin MU values for different test setups can be found in following subclauses. + +**Table B.15-1: MU threshold for beam peak measurement for Occupied bandwidth** + +| Power Class | Frequency | Power | BW | Threshold MU value (NOTE1) [%CBW] | +|--------------------|--------------------------------------------------|-------------------------------|-----------|------------------------------------------| +| PC3, PC1 | $23.45\text{ GHz} \leq f \leq 32.125\text{ GHz}$ | $P = \text{Max Output Power}$ | 50 MHz | $\pm 0.4$ | +| | | | 100 MHz | $\pm 0.4$ | +| | | | 200 MHz | $\pm 1.2$ | +| | | | 400 MHz | $\pm 1.2$ | +| | $32.125\text{ GHz} < f \leq 40.8\text{ GHz}$ | $P = \text{Max Output Power}$ | 50 MHz | $\pm 0.4$ | +| | | | 100 MHz | $\pm 0.4$ | +| | | | 200 MHz | $\pm 1.3$ | +| | | | 400 MHz | $\pm 1.3$ | +| PC3 | $40.8\text{GHz} < f \leq 44.3\text{GHz}$ | $P = \text{Max Output Power}$ | 50 MHz | TBD | +| | | | 100 MHz | TBD | +| | | | 200 MHz | TBD | +| | | | 400 MHz | TBD | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ . + +## B.15.1 Uncertainty budget format and assessment for DFF + +FFS + +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . + +## B.15.2 Uncertainty budget format and assessment for IFF + +FFS + +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30 \text{ cm}$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}\}$ , $P = \text{Maximum output power}$ . + +--- + +## B.16 Spectrum emission mask + +Following tables summarize the MU threshold for TRP measurements for Spectrum emission mask. The origin MU values for different test setups can be found in following subclauses. + +**Table B.16-1: MU threshold for TRP measurement for Spectrum emission mask** + +| Power Class | Frequency | MBW | Power | Threshold MU value (NOTE 1) | +|-------------|----------------------------------------------------|---------------------------|-------------------------------|-----------------------------| +| PC3 | $23.45 \text{ GHz} \leq f \leq 32.125 \text{ GHz}$ | $BW \leq 400 \text{ MHz}$ | $P = \text{Max Output Power}$ | 5.13 | +| | $32.125 \text{ GHz} < f \leq 40.8 \text{ GHz}$ | | | 5.51 | +| | $40.8 \text{ GHz} < f \leq 44.3 \text{ GHz}$ | | | TBD | +| PC1 | $23.45 \text{ GHz} \leq f \leq 32.125 \text{ GHz}$ | $BW \leq 400 \text{ MHz}$ | $P = \text{Max Output Power}$ | 6.32 | +| | $32.125 \text{ GHz} < f \leq 40.8 \text{ GHz}$ | | | FFS | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30 \text{ cm}$ in Table B.16.2-2 for PC3 UEs and in Table B.16.2-4 for PC1 UEs + +## B.16.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.16.1-1. + +**Table B.16.1-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.1.4 | +| 18 | Amplifier uncertainties | B.2.1.8 | +| 19 | Misalignment of positioning System | B.2.1.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 23 | Phase centre offset of calibration antenna | B.2.1.18 | +| 24 | Quality of quiet zone for calibration process | B.2.1.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 27 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 29 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . +- The uncertainty assessment for TRP is provided in Table B.16.1-2. + +**Table B.16.1-2: Uncertainty assessment for TRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | +| 4 | Mismatch (NOTE 3) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of TRP measurement grid (NOTE 5) | | | | | +| 14 | Influence of beam peak search grid (NOTE 6) | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | +| 16 | DUT repositioning | | | | | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | | | | | +| 18 | Amplifier uncertainties | | | | | +| 19 | Misalignment of positioning System | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 23 | Phase centre offset of calibration antenna | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 2) | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 26 | Influence of the calibration antenna feed cable | | | | | +| 27 | Insertion Loss Variation | | | | | +| TRP Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 5) | | | | | +| 29 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| TRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The impact of phase variation on EIRP is FFS. | +| NOTE 2: | The quality of quiet zone is different for EIRP and TRP. For TRP, the standard uncertainty is FFS; for EIRP, the standard uncertainty of quiet zone is FFS. | +| NOTE 3: | The analysis was done only for the case of operating at max output power, in-band, non-CA. | +| NOTE 4: | The assessment assumes maximum DUT output power. | +| NOTE 5: | This contributor shall only be considered for TRP measurements. | +| NOTE 6: | This contributor shall only be considered for EIRP measurements. | +| NOTE 7: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | + +## B.16.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.16.2-1. + +**Table B.16.2-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.2.4 | +| 18 | Amplifier Uncertainties | B.2.2.8 | +| 19 | Misalignment of positioning System | B.2.2.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 23 | Phase centre offset of calibration antenna | B.2.2.18 | +| 24 | Quality of quiet zone for calibration process | B.2.2.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 27 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 29 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , $P = [\text{Maximum output power}]$ . +- The uncertainty assessment for TRP is provided in Table B.16.2-2 for PC3 UEs and in Table B.16.2-4 for PC1 UEs. + +**Table B.16.2-2: Uncertainty assessment for TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 9)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 3 | Quality of Quiet Zone (NOTE 1)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 4 | Mismatch (NOTE 1)
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2)
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.16 | Normal | 2.00 | 1.08 | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 3)
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 3) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 4) | 0.00 | Actual | 1 | 0.00 | +| 15 | Multiple measurement antenna uncertainty (NOTE 8) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning (NOTE 3) | 0.00 | Rectangular | 1.73 | 0.00 | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 20 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 24 | Quality of quiet zone for calibration process (NOTE 9)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | + +| | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------|-------------|------|--------------|--|--|--|--| +| 24 | Quality of quiet zone for calibration process (NOTE 9) (40.8GHz < f <= 44.3GHz) | 0.5 | Actual | 1.00 | 0.5 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 3) | | | | 0.00 | | | | | +| 29 | Influence of noise (23.45GHz <= f <= 32.125GHz) | | | | 0.62 | | | | | +| 29 | Influence of noise (32.125GHz < f <= 40.8GHz) | | | | 1.00 | | | | | +| 29 | Influence of noise (40.8GHz < f <= 44.3GHz) | | | | TBD | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| TRP total measurement uncertainty (23.45GHz <= f <= 32.125GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.13 | | | | | +| TRP total measurement uncertainty (32.125GHz < f <= 40.8GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.51 | | | | | +| TRP Expanded uncertainty (40.8GHz < f <= 44.3GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | +| NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA. | | | | | | | | | | +| NOTE 2: The assessment assumes maximum DUT output power. | | | | | | | | | | +| NOTE 3: This contributor shall only be considered for TRP measurements. | | | | | | | | | | +| NOTE 4: This contributor shall only be considered for EIRP measurements. | | | | | | | | | | +| NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | +| NOTE 6: Values extracted from TR 38.810 v2.6.1 in square brackets pending for further analysis. | | | | | | | | | | +| NOTE 7: Void. | | | | | | | | | | +| NOTE 8: Applies to the system which has a structure of mechanical feed antenna positioning. | | | | | | | | | | +| NOTE 9: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | | | | | | | | + +**Table B.16.2-3: Void** + +**Table B.16.2-4: Uncertainty assessment for TRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.02 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 9) | 0.60 | Actual | 1.00 | 0.60 | | | | | +| 4 | Mismatch (NOTE 1) | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.16 | Normal | 2.00 | 1.08 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of TRP measurement grid (NOTE 3) | 0.25 | Actual | 1 | 0.25 | | | | | +| 14 | Influence of beam peak search grid (NOTE 4) | 0.00 | Actual | 1 | 0.00 | | | | | +| 15 | Multiple measurement antenna uncertainty (NOTE 8) | 0.15 | Actual | 1 | 0.15 | | | | | +| 16 | DUT repositioning (NOTE 3) | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 9) | 0.40 | Actual | 1.00 | 0.40 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | | | | | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 3) | | | | 0.00 | | | | | +| 29 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 1.81 | | | | | +| 29 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | FFS | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| TRP total measurement uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.32 | | | | | +| TRP total measurement uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | | | | | + +- NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA. +- NOTE 2: The assessment assumes maximum DUT output power. +- NOTE 3: This contributor shall only be considered for TRP measurements. +- NOTE 4: This contributor shall only be considered for EIRP measurements. +- NOTE 5: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 6: Values extracted from TR 38.810 v2.6.1 in square brackets pending for further analysis. +- NOTE 7: Void. +- NOTE 8: Applies to the system which has a structure of mechanical feed antenna positioning. +- NOTE 9: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. + +## B.17 Adjacent Channel Leakage Ratio + +Editor's Note: MU value analysis for PC1, 2 and 4 are not complete. + +Following tables summarize the MU threshold for EIRP measurements for Adjacent Channel Leakage Ratio. The origin MU values for different test setups can be found in following subclauses. + +**Table B.17-1: MU threshold for TRP measurement for Spectrum emission mask** + +| Power Class | Frequency | MBW | Power | Threshold MU value (NOTE 1) | +|------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------|----------------------|-----------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | TBD | +| | 32.125GHz $< f \leq 40.8$ GHz | | | TBD | +| | 40.8GHz $< f \leq 44.3$ GHz | | | TBD | +| PC1 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | TBD | +| | 32.125GHz $< f \leq 40.8$ GHz | | | TBD | +| PC5 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | TBD | +| NOTE 1: Total Expanded MU for IFF for a Quiet Zone size $\leq 30$ cm in Table B.17.2-2 for PC3 UEs and B.17.2-3 for PC1 UEs. | | | | | + +**Table B.17-1B: MU threshold for EIRP measurement for Adjacent Channel Leakage Ratio** + +| Power Class | Frequency | CBW | Power | Threshold MU value for NTC and ETC (NOTE 1) | +|-------------|-----------------------------------|-------------------|----------------------|---------------------------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125$ GHz | 50MHz | P = Max Output Power | 5.63 | +| | | 100MHz | | 6.09 | +| | | 200MHz | | 6.09 (NOTE5) | +| | | 400MHz | | 6.09 (NOTE2) | +| | 32.125GHz $< f \leq 40.8$ GHz | 50MHz | P = Max Output Power | 6.09 (NOTE7) | +| | | 100MHz | | 6.09 (NOTE6) | +| | | 200MHz | | 6.09 (NOTE3) | +| | | 400MHz | | 6.09 (NOTE4) | +| | 40.8GHz $< f \leq 44.3$ GHz | 50MHz | P = Max Output Power | TBD | +| | | 100MHz | | TBD | +| | | 200MHz | | TBD | +| | | 400MHz | | TBD | +| PC1 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 6.04 | +| | 32.125GHz $< f \leq 40.8$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 6.04 | +| PC5 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 6.04 | + +NOTE 1: Total Expanded MU for IFF for a Quiet Zone size $\leq 30$ cm in Table B.17.2-2 for PC3 UEs and Table B.17.2-3 for PC1 and PC5 UEs. + +NOTE 2: This value is based on the relaxation of (MPR – 3.0) dB for MPR $> 3.0$ dB. + +NOTE 3: Not applicable for MPR $> 3.5$ dB + +NOTE 4: Not applicable for MPR $> 2.0$ dB + +NOTE 5: This value is based on the relaxation of (MPR – 5.0) dB for MPR $> 5.0$ dB. + +NOTE 6: Not applicable for MPR $> 5.0$ dB + +NOTE 7: Not applicable for MPR $> 7.5$ dB + +## B.17.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.17.1-1. + +**Table B.17.1-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.1.4 | +| 18 | Amplifier uncertainties | B.2.1.8 | +| 19 | Misalignment of positioning System | B.2.1.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 23 | Phase centre offset of calibration antenna | B.2.1.18 | +| 24 | Quality of quiet zone for calibration process | B.2.1.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 27 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 29 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{23.45 \text{ GHz}, 32.125 \text{ GHz}, 40.8 \text{ GHz}, 44.3 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . +- The uncertainty assessment for TRP is provided in Table B.17.1-2. + +**Table B.17.1-2: Uncertainty assessment for EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | +| 4 | Mismatch (NOTE 3) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of TRP measurement grid (NOTE 5) | | | | | +| 14 | Influence of beam peak search grid (NOTE 6) | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | +| 16 | DUT repositioning | | | | | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | | | | | +| 18 | Amplifier uncertainties | | | | | +| 19 | Misalignment of positioning System | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 23 | Phase centre offset of calibration antenna | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 2) | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 26 | Influence of the calibration antenna feed cable | | | | | +| 27 | Insertion Loss Variation | | | | | +| EIRP Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 5) | | | | | +| 29 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| TRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The impact of phase variation on EIRP is FFS. | +| NOTE 2: | The quality of quiet zone is different for EIRP and TRP. For TRP, the standard uncertainty is FFS; for EIRP, the standard uncertainty of quiet zone is FFS. | +| NOTE 3: | The analysis was done only for the case of operating at max output power, in-band, non-CA. | +| NOTE 4: | The assessment assumes maximum DUT output power. | +| NOTE 5: | This contributor shall only be considered for TRP measurements. | +| NOTE 6: | This contributor shall only be considered for EIRP measurements. | +| NOTE 7: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 8: | Void | + +## B.17.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.17.2-1. + +**Table B.17.2-1: Uncertainty contributions for EIRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-----------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Quality of Quiet Zone | B.2.2.3 | +| 2 | Mismatch | B.2.2.4 | +| 3 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 4 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 5 | Phase curvature | B.2.2.7 | +| 6 | Amplifier uncertainties | B.2.2.8 | +| 7 | Random uncertainty | B.2.2.9 | +| 8 | Influence of the XPD | B.2.2.10 | +| 9 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 10 | Multiple measurement antenna uncertainty | B.2.2.25 | +| Stage 1: Calibration measurement | | | +| 11 | Mismatch | B.2.2.4 | +| 12 | Amplifier Uncertainties | B.2.2.8 | +| 13 | Misalignment of positioning System | B.2.2.13 | +| 14 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 15 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 16 | Phase centre offset of calibration antenna | B.2.2.18 | +| 17 | Quality of quiet zone for calibration process | B.2.2.19 | +| 18 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 19 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 20 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 21 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , $P = \text{Maximum output power} - \text{MPR} - \text{MBR}(\text{Multi-band relaxation})$ . +- The uncertainty assessment for EIRP is provided in Table B.17.2-2 for PC3 UEs and Table B.17.2-3 for PC1 UEs. + +**Table B.17.2-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Quality of Quiet Zone (NOTE 10) | 0.52 | Actual | 1.00 | 0.52 | +| 2 | Mismatch (NOTE 2)
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.84 | Actual | 1.00 | 1.84 | +| 2 | Mismatch (NOTE 2)
(40.8GHz $< f \leq 44.3$ GHz) | 2.40 | Actual | 1.00 | 2.40 | +| 3 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 4 | Uncertainty of the RF power measurement equipment (NOTE 3, 7)
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.16 | Normal | 2.00 | 1.08 | +| 4 | Uncertainty of the RF power measurement equipment (NOTE 3, 7)
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 5 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 7 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 8 | Influence of the XPD | 0.00 | U-shaped | 1.41 | 0.00 | +| 9 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 10 | Multiple measurement antenna uncertainty (NOTE 9) | 0.0 | Actual | 1 | 0.0 | +| Stage 1: Calibration measurement | | | | | | +| 11 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 12 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 13 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 14 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.5 | Normal | 2.00 | 0.75 | +| 14 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.7 | Normal | 2.00 | 0.85 | +| 15 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 16 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Quality of quiet zone for calibration process (NOTE 10) | 0.32 | Actual | 1.00 | 0.32 | +| 18 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Influence of the calibration antenna feed cable | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| EIRP Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] (23.45GHz $\leq f \leq 40.8$ GHz) | | | | | 5.09 | +| EIRP Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] (40.8GHz $< f \leq 44.3$ GHz) | | | | | 6.61 | +| Systematic uncertainties (NOTE 6) | | | | | Value | +| 21 | Influence of noise | | | | Table B.17.2-4 | +| Total measurement uncertainty | | | | | Value | + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| EIRP total measurement uncertainty [dB] ( $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ ) | 5.09 +
Influence of
Noise | +| EIRP total measurement uncertainty [dB] ( $40.8\text{GHz} < f \leq 44.3\text{GHz}$ ) | 6.61 +
Influence of
Noise | +| NOTE 1: Void
NOTE 2: The analysis was done only for the case of operating at max output power – MPR – MBR(Multi-band relaxation)., in-band, non-CA.
NOTE 3: The assessment assumes maximum DUT output power – MPR – MBR(Multi-band relaxation).
NOTE 4: Void
NOTE 5: Void
NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 7: Void
NOTE 8: Void
NOTE 9: Void
NOTE 10: Defined as fixed value MU contributor. | | + +**Table B.17.2-3: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Quality of Quiet Zone (NOTE 10) | 0.52 | Actual | 1.00 | 0.52 | | | | | +| 2 | Mismatch (NOTE 2, NOTE 7) | 1.84 | Actual | 1.00 | 1.84 | | | | | +| 3 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 4 | Uncertainty of the RF power measurement equipment (NOTE 3, 7) | 2.16 | Normal | 2.00 | 1.08 | | | | | +| 5 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | | | | | +| 7 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 8 | Influence of the XPD | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 9 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 10 | Multiple measurement antenna uncertainty (NOTE 9) | 0.00 | Actual | 1 | 0.00 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 11 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 12 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 13 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 14 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | | | | | +| 15 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 16 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 17 | Quality of quiet zone for calibration process (NOTE 10) | 0.32 | Actual | 1.00 | 0.32 | | | | | +| 18 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 19 | Influence of the calibration antenna feed cable | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.09 | | | | | +| Systematic uncertainties (NOTE 6) | | | | | Value | | | | | +| 21 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.95 | | | | | +| 21 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 0.95 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP total measurement uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) [dB] | | | | | 6.04 | | | | | +| EIRP total measurement uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) [dB] | | | | | 6.04 | | | | | +| NOTE 1: Void | | | | | | | | | | +| NOTE 2: The analysis was done only for the case of operating at max output power, in-band, non-CA. | | | | | | | | | | +| NOTE 3: The assessment assumes maximum DUT output power. | | | | | | | | | | +| NOTE 4: Void | | | | | | | | | | +| NOTE 5: Void | | | | | | | | | | +| NOTE 6: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | | | | +| NOTE 7: Values extracted from TR 38.810 v2.6.1 in square brackets pending for further analysis. | | | | | | | | | | +| NOTE 8: Void. | | | | | | | | | | +| NOTE 9: Void | | | | | | | | | | +| NOTE 10: Defined as fixed value MU contributor. | | | | | | | | | | + +**Table B.17.2-4: Influence of noise measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| | FR2a | FR2b | FR2c | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|------| +| ChBW (50MHz) | 0.54 | 1.0 (NOTE 6) | TBD | +| ChBW (100MHz) | 1.0 | 1.0 (NOTE 5) | TBD | +| ChBW (200MHz) | 1.0 (NOTE 4) | 1.0 (NOTE 2) | TBD | +| ChBW (400MHz) | 1.0 (NOTE 1) | 1.0 (NOTE 3) | TBD | +| NOTE 1: This value is based on the relaxation of (MPR – 3.0) dB for MPR > 3.0dB.
NOTE 2: Not applicable for MPR > 3.5dB
NOTE 3: Not applicable for MPR > 2.0dB
NOTE 4: This value is based on the relaxation of (MPR – 5.0) dB for MPR > 5.0dB.
NOTE 5: Not applicable for MPR > 5.0dB
NOTE 6: Not applicable for MPR > 7.5dB | | | | + +## B.18 Spurious emissions + +Editor's Note: + +- MU value analysis and offset value analysis for PC1, 2 and 4 are not complete. +- MU offset value analysis for PC2 and 4 are not complete. +- MU value analysis for various test setups in clause B.18.x is not complete for above 80 GHz. + +Test procedure of general spurious emission comprises 2 stages: coarse TRP measurement and fine TRP measurement BW. Coarse TRP measurement is introduced to reduce the measurement time by applying sparser grids and/or wider measurement BW than fine TRP measurement while having offset dB more stringent test requirement in order not to cause additional misjudgement risk. For the frequency ranges for which coarse TRP measurement does not PASS, the measurement is continued with fine TRP measurement procedure. + +Tables B.18-1, B.18-1a, B.18-1b summarizes the MU threshold for fine TRP measurements for General spurious emissions, spurious emission band UE co-existence and additional spurious emission, respectively. The origin MU values for fine TRP measurement for different test setups can be found in following subclauses. + +**Table B.18-1: MU threshold for TRP measurement for general spurious emission** + +| Power Class | Frequency | In-band BW | In-band Power (NOTE2) | Threshold MU value [dB] (NOTE1) | +|-------------|-----------------------------------|-------------------|-----------------------|---------------------------------| +| PC3 | 6 GHz $\leq f \leq 12.75$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 5.29 | +| | 12.75 GHz $\leq f \leq 23.45$ GHz | | | 5.25 | +| | 23.45 GHz $\leq f \leq 40.8$ GHz | | | 5.41 | +| | 40.8 GHz $\leq f \leq 66$ GHz | | | 7.42 | +| | 66 GHz $\leq f \leq 80$ GHz | | | 7.72 | +| PC1 | 6 GHz $\leq f \leq 12.75$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 5.28 | +| | 12.75 GHz $\leq f \leq 23.45$ GHz | | | 5.91 | +| | 23.45 GHz $\leq f \leq 40.8$ GHz | | | 6.07 | +| | 40.8 GHz $\leq f \leq 66$ GHz | | | 8.09 | +| | 66 GHz $\leq f \leq 80$ GHz | | | 7.71 | + +NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30$ cm in Table B.18.2-3 to Table B.18.2-11 for PC3 UEs and in Table B.18.2-12 to Table B.18.2-16 for PC1 UEs. +NOTE 2: Max output power level for device with corresponding power class. + +**Table B.18-1a: MU threshold for TRP measurement for spurious emission band UE co-existence** + +| Power Class | Frequency | In-band BW | In-band Power (NOTE2) | Threshold MU value [dB] (NOTE1) | +|-------------|------------------------------|-------------------|-----------------------|---------------------------------| +| PC3 | n257, n260, n261 | BW $\leq 400$ MHz | P = Max Output Power | 6.00 | +| | 23.6 GHz $< f \leq 24.0$ GHz | | | 6.00 | +| | 36 GHz $\leq f \leq 37$ GHz | | | 6.00 | +| | 57 GHz $\leq f \leq 66$ GHz | | | 8.01 | +| PC1 | n257, n261 | BW $\leq 400$ MHz | P = Max Output Power | 7.32 | +| | n260 | | | 7.32 | +| | 23.6 GHz $< f \leq 24.0$ GHz | | | 7.32 | +| | 57 GHz $\leq f \leq 66$ GHz | | | 8.00 | + +NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30$ cm in Table B.18.2-3 to Table B.18.2-11 for PC3 UEs and in Table B.18.2-12 to Table B.18.2-16 for PC1 UEs. +NOTE 2: Max output power level for device with corresponding power class. + +**Table B.18-1b: MU threshold for TRP measurement for additional spurious emission** + +| Power Class | Frequency | In-band BW | In-band Power (NOTE2) | Threshold MU value [dB] (NOTE1) | +|-------------|-----------------------------------------------------------------------------------------------------|-------------------|-----------------------|---------------------------------| +| PC3 | 6 GHz $\leq f \leq 12.75$ GHz
NS_202 | BW $\leq 400$ MHz | P = Max Output Power | 5.29 | +| | 12.75 GHz $\leq f \leq 23.45$ GHz
NS_202 | | | 5.84 | +| | 23.45 GHz $\leq f \leq 40.8$ GHz
NS_202,
NS_203 | | | 6.00 | +| | 40.8 GHz $\leq f \leq 2$ nd harmonic of the upper frequency edge of the UL operating band
NS_202 | | | 8.01 | +| PC1 | 6 GHz $\leq f \leq 12.75$ GHz
NS_202 | BW $\leq 400$ MHz | P = Max Output Power | 5.28 | +| | 12.75 GHz $\leq f \leq 23.45$ GHz
NS_202 | | | 7.16 | +| | 23.45 GHz $\leq f \leq 40.8$ GHz
NS_202,
NS_203 | | | 7.32 | +| | 40.8 GHz $\leq f \leq 2$ nd harmonic of the upper frequency edge of the UL operating band
NS_202 | | | 9.34 | + +NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30$ cm in Table B.18.2-3 to Table B.18.2-11 for PC3 UEs and in Table B.18.2-12 to Table B.18.2-16 for PC1 UEs. + +NOTE 2: Max output power level for device with corresponding power class. + +## B.18.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.18.1-1. + +**Table B.18.1-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.1.4 | +| 18 | Amplifier uncertainties | B.2.1.8 | +| 19 | Misalignment of positioning System | B.2.1.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 23 | Phase centre offset of calibration antenna | B.2.1.18 | +| 24 | Quality of quiet zone for calibration process | B.2.1.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 27 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 29 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{6 \text{ GHz to } 80 \text{ GHz}\}$ , $P = [\text{Maximum output power}]$ . +- The uncertainty assessment for TRP is provided in Table B.18.1-2 to B.18.1-xx + +**Table B.18.1-2: Uncertainty assessment for TRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone (NOTE 2) | | | | | +| 4 | Mismatch (NOTE 3) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 4) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of TRP measurement grid (NOTE 5) | | | | | +| 14 | Influence of beam peak search grid (NOTE 6) | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | +| 16 | DUT repositioning | | | | | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | | | | | +| 18 | Amplifier uncertainties | | | | | +| 19 | Misalignment of positioning System | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 23 | Phase centre offset of calibration antenna | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 2) | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 26 | Influence of the calibration antenna feed cable | | | | | +| 27 | Insertion Loss Variation | | | | | +| TRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 7) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 5) | | | | | +| 29 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| TRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The impact of phase variation on EIRP is FFS. | +| NOTE 2: | The quality of quiet zone is different for EIRP and TRP. For TRP, the standard uncertainty is FFS; for EIRP, the standard uncertainty of quiet zone is FFS. | +| NOTE 3: | The analysis was done only for the case of operating at max output power, in-band, non-CA. | +| NOTE 4: | The assessment assumes maximum DUT output power. | +| NOTE 5: | This contributor shall only be considered for TRP measurements. | +| NOTE 6: | This contributor shall only be considered for EIRP measurements. | +| NOTE 7: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 8: | Void | + +## B.18.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.18.2-1. + +**Table B.18.2-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| 17 | Misalignment of DUT due to change of DUT orientation | B.2.2.31 | +| Stage 1: Calibration measurement | | | +| 18 | Mismatch | B.2.2.4 | +| 19 | Amplifier Uncertainties | B.2.2.8 | +| 20 | Misalignment of positioning System | B.2.2.13 | +| 21 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 24 | Phase centre offset of calibration antenna | B.2.2.18 | +| 25 | Quality of quiet zone for calibration process | B.2.2.19 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 27 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 28 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 29 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 30 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of Quiet zone size $\leq 30$ cm, $f = \{6 \text{ GHz to } 80 \text{ GHz}\}$ , $P = \text{Maximum output power}$ . +- The uncertainty assessment for TRP is provided from Table B.18.2-2 to Table B.18.2-11 for PC3 UEs and from Table B.18.2-12 to Table B.18.2-16 for PC1 UEs. + +**Table B.18.2-2: Void** + +**Table B.18.2-3: Uncertainty assessment for TRP measurement (f=6 GHz to 12.75GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 4 | Mismatch | 1.50 | Actual | 1.00 | 1.50 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.00 | Normal | 2.00 | 1.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty (6 GHz < f ≤ 12.75 GHz) [dB] (a) | 4.88 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | General spurious emissions Influence of noise (c 1 )
(6 GHz < f ≤ 12.75 GHz) | 0.41 | +| 30 | Additional spurious emissions Influence of noise (c 2 )
NS_202 (6 GHz < f ≤ 12.75 GHz) | 0.41 | +| | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
(6 GHz < f ≤ 12.75 GHz) | 5.29 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
NS_202 (6 GHz < f ≤ 12.75 GHz) | 5.29 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.18.2-4: Void** + +**Table B.18.2-5: Uncertainty assessment for TRP measurement (f=12.75 GHz to 23.45 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 4 | Mismatch | 1.50 | Actual | 1.00 | 1.50 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.16 | Normal | 2.00 | 1.08 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty (12.75 GHz < f <= 23.45 GHz) [dB] (a) | 4.84 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | General spurious emissions Influence of noise (c 1 )
(12.75 GHz < f <= 23.45 GHz) | 0.41 | +| 30 | Additional spurious emissions Influence of noise (c 2 )
NS_202 (12.75 GHz < f <= 23.45 GHz) | 1.0 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
(12.75 GHz < f <= 23.45 GHz) | 5.25 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
NS_202 (12.75 GHz < f <= 23.45 GHz) | 5.84 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.18.2-6: Void** + +**Table B.18.2-7: Uncertainty assessment for TRP measurement (f=23.45 GHz to 40.8 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 1.40 | Actual | 1.00 | 1.40 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.73 | Normal | 2.00 | 1.37 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.6 | Normal | 2.00 | 0.3 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|----|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty (23.45 GHz < f <= 40.8 GHz) [dB] (a) | 5.00 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | General spurious emissions Influence of noise (c 1 )
(23.45 GHz < f <= 40.8 GHz) | 0.41 | +| 30 | Spurious emission band UE co-existence Influence of noise (c 2 )
(f within NR Bands n257, n260 or n261) | 1.0 | +| 30 | Spurious emission band UE co-existence Influence of noise (c 3 )
(36 GHz <= f <= 37 GHz) | 1.0 | +| 30 | Additional spurious emissions Influence of noise (c 4 )
NS_202 (23.6 GHz < f <= 24.0 GHz) | 1.0 | +| 30 | Additional spurious emissions Influence of noise (c 5 )
NS_202 (23.45 GHz < f <= 40.8 GHz) | 1.0 | +| 30 | Additional spurious emissions Influence of noise (c 6 )
NS_203 (23.6 GHz < f <= 24.0 GHz) | 1.0 | +| 30 | Spurious emission band UE co-existence Influence of noise (c 7 )
(23.6 GHz < f <= 24.0 GHz) | 1.0 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
(23.45 GHz < f <= 40.8 GHz) | 5.41 | +| | Spurious emission band UE co-existence Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
(f within NR Bands n257, n260 or n261) | 6.00 | +| | Spurious emission band UE co-existence Total measurement uncertainty (a)+(b)+(c 3 ) [dB]
(36 GHz <= f <= 37 GHz) | 6.00 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 4 ) [dB]
NS_202 (23.6 GHz < f <= 24.0 GHz) | 6.00 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 5 ) [dB]
NS_202 (23.45 GHz < f <= 40.8 GHz) | 6.00 | + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 6 ) [dB]
NS_203 (23.6 GHz < f <= 24.0 GHz) | 6.00 | +| Spurious emission band UE co-existence Total measurement uncertainty (a)+(b)+(c 7 ) [dB]
(23.6 GHz < f <= 24.0 GHz) | 6.00 | +| NOTE 1: This contributor shall only be considered for TRP measurements.
NOTE 2: This contributor shall only be considered for EIRP measurements.
NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm.
NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | + +**Table B.18.2-8: Void** + +**Table B.18.2-9: Uncertainty assessment for TRP measurement (f= 40.8 GHz to 66 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.0 | Normal | 2.00 | 0.0 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.0 | Normal | 2.00 | 2.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.7 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) [dB] (a) | 7.01 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | General spurious emissions Influence of noise ( $c_1$ )
( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) | 0.41 | +| 30 | Spurious emission band UE co-existence Influence of noise ( $c_2$ )
( $57 \text{ GHz} \leq f \leq 66 \text{ GHz}$ ) | 1.0 | +| 30 | Additional spurious emissions Influence of noise ( $c_3$ )
NS_202 ( $40.8 \text{ GHz} < f \leq 2\text{nd harmonic of the upper frequency edge of the UL operating band}$ ) | 1.0 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) | 7.42 | +| | Spurious emission band UE co-existence Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
( $57 \text{ GHz} \leq f \leq 66 \text{ GHz}$ ) | 8.01 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 3 ) [dB]
NS_202 ( $40.8 \text{ GHz} < f \leq 2\text{nd harmonic of the upper frequency edge of the UL operating band}$ ) | 8.01 | +| NOTE 1: This contributor shall only be considered for TRP measurements.
NOTE 2: This contributor shall only be considered for EIRP measurements.
NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm.
NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning.
NOTE 6: Void | | | + +**Table B.18.2-10: Void** + +**Table B.18.2-11: Uncertainty assessment for TRP measurement (f= 66 GHz to 80 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.00 | Normal | 2.00 | 2.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 3.0 | Normal | 2.00 | 1.50 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.70 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | +| TRP Expanded uncertainty ( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) [dB] (a) | | | | | 7.31 | + +| | Systematic uncertainties (NOTE 3) | Value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|--------------| +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | General spurious emissions Influence of noise ( $c_1$ )
( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) | 0.41 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| Total measurement uncertainty | | Value | +| General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) | | 7.72 | +| NOTE 1: This contributor shall only be considered for TRP measurements.
NOTE 2: This contributor shall only be considered for EIRP measurements.
NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm.
NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.18.2-12: Uncertainty assessment for TRP measurement (f=6 GHz to 12.75GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 4 | Mismatch | 1.50 | Actual | 1.00 | 1.50 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.00 | Normal | 2.00 | 1.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | +| TRP Expanded uncertainty ( $6\text{ GHz} < f \leq 12.75\text{ GHz}$ ) [dB] (a) | | | | | 4.87 | + +| | Systematic uncertainties (NOTE 3) | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | General spurious emissions Influence of noise ( $c_1$ )
( $6\text{ GHz} < f \leq 12.75\text{ GHz}$ ) | 0.41 | +| 30 | Additional spurious emissions Influence of noise ( $c_2$ )
NS_202 ( $6\text{ GHz} < f \leq 12.75\text{ GHz}$ ) | 0.41 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
( $6\text{ GHz} < f \leq 12.75\text{ GHz}$ ) | 5.28 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
NS_202 ( $6\text{ GHz} < f \leq 12.75\text{ GHz}$ ) | 5.28 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.18.2-13: Uncertainty assessment for TRP measurement (f=12.75 GHz to 23.45 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 4 | Mismatch | 1.50 | Actual | 1.00 | 1.50 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.16 | Normal | 2.00 | 1.08 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | +| TRP Expanded uncertainty ( $12.75 \text{ GHz} < f \leq 23.45 \text{ GHz}$ ) [dB] (a) | | | | | 4.83 | + +| | Systematic uncertainties (NOTE 3) | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------------| +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | General spurious emissions Influence of noise ( $c_1$ )
(12.75 GHz < f ≤ 23.45 GHz) | 1.08 | +| e30 | Additional spurious emissions Influence of noise ( $c_2$ )
NS_202 (12.75 GHz < f ≤ 23.45 GHz) | 2.34 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c) [dB]
(12.75 GHz < f ≤ 23.45 GHz) | 5.91 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
NS_202 (12.75 GHz < f ≤ 23.45 GHz) | 7.16 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.18.2-14: Uncertainty assessment for TRP measurement (f=23.45 GHz to 40.8 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 1.40 | Actual | 1.00 | 1.40 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.73 | Normal | 2.00 | 1.37 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.6 | Normal | 2.00 | 0.3 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | +| TRP Expanded uncertainty ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) [dB] (a) | | | | | 4.99 | + +| | Systematic uncertainties (NOTE 3) | Value | +|----|---------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | General spurious emissions Influence of noise ( $c_1$ )
( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) | 1.08 | +| 30 | Spurious emission band UE co-existence Influence of noise ( $c_2$ )
(f within NR Bands n257, n260 or n261) | 2.34 | +| 30 | Additional spurious emissions Influence of noise ( $c_4$ )
NS_202 ( $23.6 \text{ GHz} < f \leq 24.0 \text{ GHz}$ ) | 2.34 | +| 30 | Additional spurious emissions Influence of noise ( $c_5$ )
NS_202 ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) | 2.34 | +| 30 | Additional spurious emissions Influence of noise ( $c_6$ )
NS_203 ( $23.6 \text{ GHz} < f \leq 24.0 \text{ GHz}$ ) | 2.34 | +| 30 | Spurious emission band UE co-existence Influence of noise ( $c_7$ )
( $23.6 \text{ GHz} < f \leq 24.0 \text{ GHz}$ ) | 2.34 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) | 6.07 | +| | Spurious emission band UE co-existence Total measurement uncertainty (a)+(b)+(c 2 ) [dB]
(f within NR Bands n257, n260 or n261) | 7.32 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 4 ) [dB]
NS_202 ( $23.6 \text{ GHz} < f \leq 24.0 \text{ GHz}$ ) | 7.32 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 5 ) [dB]
NS_202 ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) | 7.32 | +| | Additional spurious emissions Total measurement uncertainty (a)+(b)+(c 6 ) [dB]
NS_203 ( $23.6 \text{ GHz} < f \leq 24.0 \text{ GHz}$ ) | 7.32 | +| | Spurious emission band UE co-existence Total measurement uncertainty (a)+(b)+(c 7 ) [dB]
( $23.6 \text{ GHz} < f \leq 24.0 \text{ GHz}$ ) | 7.32 | + +- NOTE 1: This contributor shall only be considered for TRP measurements. +- NOTE 2: This contributor shall only be considered for EIRP measurements. +- NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +- NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. +- NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. + +**Table B.18.2-15: Uncertainty assessment for TRP measurement (f= 40.8 GHz to 66 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.0 | Normal | 2.00 | 2.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.7 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | +| TRP Expanded uncertainty ( 40.8 GHz < f <= 66 GHz) [dB] (a) | | | | | 7.00 | + +| | Systematic uncertainties (NOTE 3) | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | General spurious emissions Influence of noise ( $c_1$ )
( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) | 1.08 | +| 30 | Spurious emission band UE co-existence Influence of noise ( $c_2$ )
( $57 \text{ GHz} \leq f \leq 66 \text{ GHz}$ ) | 1 | +| 30 | Additional spurious emissions Influence of noise ( $c_3$ )
NS_202 ( $40.8 \text{ GHz} < f \leq 2\text{nd harmonic of the upper frequency edge of the UL operating band}$ ) | 2.34 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | General spurious emissions Total measurement uncertainty $(a)+(b)+(c_1)$ [dB]
( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) | 8.09 | +| | Spurious emission band UE co-existence Total measurement uncertainty $(a)+(b)+(c_2)$ [dB]
( $57 \text{ GHz} \leq f \leq 66 \text{ GHz}$ ) | 8.00 | +| | Additional spurious emissions Total measurement uncertainty $(a)+(b)+(c_3)$ [dB]
NS_202 ( $40.8 \text{ GHz} < f \leq 2\text{nd harmonic of the upper frequency edge of the UL operating band}$ ) | 9.34 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | +| NOTE 6: Void | | | + +**Table B.18.2-16: Uncertainty assessment for TRP measurement (f= 66 GHz to 80 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.00 | Normal | 2.00 | 2.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 3.00 | Normal | 2.00 | 1.50 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.06 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.70 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | +| TRP Expanded uncertainty ( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) [dB] (a) | | | | | 7.30 | + +| | Systematic uncertainties (NOTE 3) | Value | +|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|--------------| +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0 | +| 30 | General spurious emissions Influence of noise (c 1 )
(66 GHz < f ≤ 80 GHz) | 0.41 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| Total measurement uncertainty | | Value | +| General spurious emissions Total measurement uncertainty (a)+(b)+(c 1 ) [dB]
(66 GHz < f ≤ 80 GHz) | | 7.71 | + +NOTE 1: This contributor shall only be considered for TRP measurements. +NOTE 2: This contributor shall only be considered for EIRP measurements. +NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. +NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. + +NOTE: MU assessment for additional spurious in Table B.18.2-3 to Table B.18.2-16 is based on the following relaxations: + +**Table B.18.2-17: Transmitter Spurious emissions relaxation considered in MU assessment (Quiet Zone size ≤ 30 cm)** + +| Power Class | Frequency | Relaxation | +|--------------------|---------------------------|-------------------| +| PC1 | 6 GHz < f ≤ 12.75 GHz | 0 dB | +| | 12.75 GHz < f ≤ 23.45 GHz | 0 dB | +| | 23.45GHz ≤ f ≤ 40.8GHz | 0 dB | +| | 40.8 GHz < f ≤ 66 GHz | 0 dB | +| | 66 GHz < f ≤ 80 GHz | 0 dB | +| PC2 | 6 GHz < f ≤ 12.75 GHz | FFS | +| | 12.75 GHz < f ≤ 23.45 GHz | FFS | +| | 23.45GHz ≤ f ≤ 40.8GHz | FFS | +| | 40.8 GHz < f ≤ 66 GHz | FFS | +| | 66 GHz < f ≤ 80 GHz | FFS | +| PC3 | 6 GHz < f ≤ 12.75 GHz | 0 dB | +| | 12.75 GHz < f ≤ 23.45 GHz | 0 dB | +| | 23.45GHz ≤ f ≤ 40.8GHz | 0 dB | +| | 40.8 GHz < f ≤ 66 GHz | 0 dB | +| | 66 GHz < f ≤ 80 GHz | 0 dB | +| PC4 | 6 GHz < f ≤ 12.75 GHz | FFS | +| | 12.75 GHz < f ≤ 23.45 GHz | FFS | +| | 23.45GHz ≤ f ≤ 40.8GHz | FFS | +| | 40.8 GHz < f ≤ 66 GHz | FFS | +| | 66 GHz < f ≤ 80 GHz | FFS | + +**Table B.18.2-18: Spurious emissions band UE co-existence relaxation considered in MU assessment (Quiet Zone size $\leq 30$ cm)** + +| Power Class | Frequency | Relaxation | +|-------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| PC1 | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | 3.3 dB (for protected bands n257, n261)
5 dB (for protected band n260)
0.3 dB (for $23.6\text{ GHz} \leq f \leq 24.0\text{ GHz}$ ) | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | 0 dB (for $57.0\text{ GHz} \leq f \leq 66.0\text{ GHz}$ ) | +| PC2 | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | FFS | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | FFS | +| PC3 | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | 3.3 dB (for protected bands n257, n261)
5 dB (for protected band n260)
0.3 dB (for $23.6\text{ GHz} \leq f \leq 24.0\text{ GHz}$ ) | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | 6 dB (for $36.0\text{ GHz} \leq f \leq 37.0\text{ GHz}$ )
0 dB (for $57.0\text{ GHz} \leq f \leq 66.0\text{ GHz}$ ) | +| PC4 | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | FFS | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | FFS | + +**Table B.18.2-19: Additional Spurious emissions relaxation considered in MU assessment (Quiet Zone size $\leq 30$ cm)** + +| Power Class | Frequency | Relaxation | +|-------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| PC1 | $6\text{ GHz} < f \leq 12.75\text{ GHz}$ | 0 dB (NS_202) | +| | $12.75\text{ GHz} < f \leq 23.45\text{ GHz}$ | 13 dB (NS_202) | +| | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | 13 dB (whole frequency range for NS_202)
0.3 dB (for $23.6\text{ GHz} \leq f \leq 24.0\text{ GHz}$ for NS_202 & NS_203) | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | 13 dB (NS_202) | +| | $66\text{ GHz} < f \leq 80\text{ GHz}$ | FFS | +| PC2 | $6\text{ GHz} < f \leq 12.75\text{ GHz}$ | FFS | +| | $12.75\text{ GHz} < f \leq 23.45\text{ GHz}$ | FFS | +| | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | FFS | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | FFS | +| | $66\text{ GHz} < f \leq 80\text{ GHz}$ | FFS | +| PC3 | $6\text{ GHz} < f \leq 12.75\text{ GHz}$ | 0 dB (NS_202) | +| | $12.75\text{ GHz} < f \leq 23.45\text{ GHz}$ | 13 dB (NS_202) | +| | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | 13 dB (whole frequency range for NS_202)
0.3 dB (for $23.6\text{ GHz} \leq f \leq 24.0\text{ GHz}$ for NS_202 & NS_203) | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | 13 dB (NS_202) | +| PC4 | $6\text{ GHz} < f \leq 12.75\text{ GHz}$ | FFS | +| | $12.75\text{ GHz} < f \leq 23.45\text{ GHz}$ | FFS | +| | $23.45\text{GHz} \leq f \leq 40.8\text{GHz}$ | FFS | +| | $40.8\text{ GHz} < f \leq 66\text{ GHz}$ | FFS | +| | $66\text{ GHz} < f \leq 80\text{ GHz}$ | FFS | + +## B.18.3 Uncertainty budget format and assessment for NFTF + +FFS + +## B.18a Beam correspondence - EIRP + +### B.18a.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.18a.1-1. + +**Table B.18a.1-1: Uncertainty contributions for Beam correspondence - EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.1.36 | +| 2 | Amplifier uncertainties | B.2.1.8 | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 3 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of D = [5 cm], f = {22.65GHz, 31.1GHz, 45.1GHz}, P = [maximum output power]. +- The uncertainty assessment for Beam correspondence - EIRP is provided in Table B.18a.1-2. + +**Table B.18a.1-2: Uncertainty assessment for Beam correspondence - EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | FFS | FFS | FFS | FFS | +| 2 | Amplifier uncertainties | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 3 | Influence of noise | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +### B.18a.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.18a.2-1. + +**Table B.18a.2-1: Uncertainty contributions for Beam correspondence - EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.2.36 | +| 2 | Amplifier uncertainties | B.2.2.8 | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 3 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment for Beam Correspondence - EIRP is provided in Table B.18a.2-2.for PC3. + +**Table B.18a.2-2: Uncertainty assessment for Beam correspondence - EIRP measurement +(f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30 \text{ cm}$ ) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | 0.4 | Normal | 2.00 | [0.2] | +| 2 | Amplifier uncertainties | 2.1 | Rectangular | 1.73 | 1.05 | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 3 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | 0.58 | +| 3 | Influence of noise ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | 1.71 | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 2.67 | +| EIRP Expanded uncertainty ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 3.80 | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 2: Power step size assumed to be no higher than 3.2 dB in 85% of the measurement grid points.
NOTE 3: Measurement uncertainties in this table assume absolute power measurements involved in the same relative power measurement are performed over the same RF path. | | | | | | + +### B.18a.3 Uncertainty budget format and assessment for NFTF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.18a.3-1. + +**Table B.18a.3-1: Uncertainty contributions for Beam correspondence - EIRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Uncertainty of the RF relative power measurement equipment | B.2.3.30 | +| 2 | Amplifier uncertainties | B.2.3.8 | +| Stage 1: Calibration measurement | | | +| | N/A | | +| Systematic uncertainties | | | +| 3 | Influence of noise | B.2.3.29 | + +The uncertainty assessment table is organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of D = [5 cm], f = {22.65GHz, 31.1GHz, 45.1GHz}, P = [maximum output power]. +- The uncertainty assessment for Beam correspondence - EIRP is provided in Table B.18a.3-2 + +**Table B.18a.3-2: Uncertainty assessment for Beam correspondence - EIRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Uncertainty of the RF relative power measurement equipment | FFS | FFS | FFS | FFS | +| 2 | Amplifier uncertainties | FFS | FFS | FFS | FFS | +| Stage 1: Calibration measurement | | | | | | +| | N/A | | | | | +| Systematic uncertainties (NOTE 1) | | | | | Value | +| 3 | Influence of noise | | | | FFS | +| Total measurement uncertainty | | | | | Value | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | FFS | +| NOTE 1: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | + +## B.19 Reference Sensitivity + +Following tables summarize the MU threshold for EIS measurements for Reference Sensitivity. The origin MU values for different test setups with varies parameters can be found in following subclauses. + +**Table B.19-1: MU threshold for EIS for Reference Sensitivity** + +| Power Class | Frequency | MBW | Power | Threshold MU value for NTC (NOTE 1) | Threshold MU value for ETC (NOTE 1) | +|-------------|----------------------------------|------------------|----------------------|-------------------------------------|-------------------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.36 | 5.61 | +| | 32.125GHz $< f \leq 40.8GHz$ | | | 5.36 | 5.61 | +| | 40.8GHz $< f \leq 44.3GHz$ | | | 6.34 | 6.48 | +| PC1 | 23.45GHz $\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.58 | 5.83 | +| | 32.125GHz $< f \leq 40.8GHz$ | | | 5.58 | 5.83 | +| PC5 | 23.45GHz $\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.58 | 5.83 | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30cm$ in Table B.19.2-2 for PC3 UEs (NTC), in Table B.19.2-4 for PC3 UEs (ETC), and Table B.19.2-3 for PC1 UEs + +**Table B.19-2: MU threshold for Spherical coverage measurement for Reference Sensitivity** + +| Power Class | Frequency | MBW | Power | Threshold MU value (NOTE 1) | +|-------------|----------------------------------|------------------|----------------------|-----------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.07 | +| | 32.125GHz $< f \leq 40.8GHz$ | | | 5.07 | +| | 40.8GHz $< f \leq 44.3GHz$ | | | 6.04 | +| PC1 | 23.45GHz $\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.07 | +| | 32.125GHz $< f \leq 40.8GHz$ | | | 5.07 | +| PC5 | 23.45GHz $\leq f \leq 32.125GHz$ | BW $\leq 400MHz$ | P = Max Output Power | 5.07 | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30cm$ in Table B.19.2-2 for PC3 UEs and Table B.19.2-3 for PC1 UEs + +## B.19.1 Uncertainty budget format and assessment for DFF + +FFS + +## B.19.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.19.2-1. + +**Table B.19.2-1: Uncertainty contributions for EIS measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | gNB emulator uncertainty | B.2.2.17 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 14 | DUT repositioning | B.2.2.26 | +| 15 | Influence of spherical coverage grid | B.2.2.29 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.2.4 | +| 17 | Amplifier Uncertainties | B.2.2.8 | +| 18 | Misalignment of positioning System | B.2.2.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 22 | Phase centre offset of calibration antenna | B.2.2.18 | +| 23 | Quality of quiet zone for calibration process | B.2.2.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 26 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 27 | Systematic error related to beam peak search | B.2.2.28 | +| 28 | Systematic error related to EIS spherical coverage | B.2.2.30 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , [P = maximum output power]. +- The uncertainty assessment for EIS is provided in Table B.19.2-2 for PC3 UEs and Table B.19.2-3 for PC1 UEs. + +**Table B.19.2-2: Uncertainty assessment for EIS measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 7)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 3 | Quality of Quiet Zone (NOTE 7)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 4 | Mismatch
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | gNB uncertainty on absolute level
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.9 | Normal | 2.00 | 1.45 | +| 6 | gNB uncertainty on absolute level
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Multiple measurement antenna uncertainty (NOTE 6) | 0.15 | Actual | 1.00 | 0.15 | +| 14 | DUT repositioning | 0.00 (NOTE 4)
0.08 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.05 (NOTE 5) | +| 15 | Influence of spherical coverage grid (NOTE 4) | 0.12 | Actual | 1 | 0.12 | +| Stage 1: Calibration measurement | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 19 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 23 | Quality of quiet zone for calibration process (NOTE 7)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------|-------------|------|-------------------------| +| 23 | Quality of quiet zone for calibration process (NOTE 7)
(40.8GHz < f <= 44.3GHz) | 0.5 | Actual | 1.00 | 0.5 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Systematic uncertainties (NOTE 3) | | | | | Value | +| 27 | Systematic error related to beam peak search (NOTE 5) | | | | | +| 28 | Systematic error related to EIS spherical coverage (NOTE 4) | | | | | +| | | | | | DL power step size, 0.2 | +| Total measurement uncertainty | | | | | Value | +| EIS Expanded uncertainty (23.45GHz <= f <= 40.8GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.36 | +| EIS Expanded uncertainty (40.8GHz < f <= 44.3GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.34 | +| EIS Spherical coverage Expanded uncertainty (23.45GHz <= f <= 40.8GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.07 | +| EIS Spherical coverage Expanded uncertainty (40.8GHz < f <= 44.3GHz) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.04 | +| NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA.
NOTE 2: Void.
NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 4: This contributor shall only be considered for spherical EIS measurements.
NOTE 5: This contributor shall only be considered for EIS measurements.
NOTE 6: Applies to the system which has a structure of mechanical feed antenna positioning.
NOTE 7: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | | | | + +**Table B.19.2-3: Uncertainty assessment for EIS measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 7) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 6) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.00 (NOTE 4)
0.35 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.20 (NOTE 5) | | | | | +| 15 | Influence of spherical coverage grid (NOTE 4) | 0.13 | Actual | 1 | 0.13 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 7) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 3) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search (NOTE 5) | | | | 0.7 | | | | | +| 28 | Systematic error related to EIS spherical coverage (NOTE 4) | | | | DL power step size, 0.2 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIS Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.58 | | | | | +| EIS Spherical coverage Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.07 | | | | | + +NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA. +NOTE 2: Void. +NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. +NOTE 4: This contributor shall only be considered for spherical EIS measurements. +NOTE 5: This contributor shall only be considered for EIS measurements. +NOTE 6: Applies to the system which has a structure of mechanical feed antenna positioning. +NOTE 7: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. + +**Table B.19.2-4: Uncertainty assessment for EIS measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 7) | 0.9 | Actual | 1.00 | 0.9 | +| 4 | Mismatch
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | gNB uncertainty on absolute level
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.9 | Normal | 2.00 | 1.45 | +| 6 | gNB uncertainty on absolute level
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Multiple measurement antenna uncertainty (NOTE 6) | 0.15 | Actual | 1.00 | 0.15 | +| 14 | DUT repositioning | 0.00 (NOTE 4)
0.08 (NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.05 (NOTE 5) | +| 15 | Influence of spherical coverage grid (NOTE 4) | 0.12 | Actual | 1 | 0.12 | +| Stage 1: Calibration measurement | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 19 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 19 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 23 | Quality of quiet zone for calibration process (NOTE 7) | 0.6 | Actual | 1.00 | 0.6 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | + +| | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|------|-------------|------|-------------------------|--|--|--|--| +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 3) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search (NOTE 5) | | | | 0.5 | | | | | +| 28 | Systematic error related to EIS spherical coverage (NOTE 4) | | | | DL power step size, 0.2 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIS Expanded uncertainty (23.45GHz $\leq f \leq 40.8\text{GHz}$ ) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.61 | | | | | +| EIS Expanded uncertainty (40.8GHz $< f \leq 44.3\text{GHz}$ ) (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 6.48 | | | | | +| NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA.
NOTE 2: Void.
NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 4: This contributor shall only be considered for spherical EIS measurements.
NOTE 5: This contributor shall only be considered for EIS measurements.
NOTE 6: Applies to the system which has a structure of mechanical feed antenna positioning.
NOTE 7: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. The ETC QoQZ MU and ETC calibration path losses shall be applied to the NTC test cases if the ETC environment is used for NTC test cases. | | | | | | | | | | + +**Table B.19.2-5: Uncertainty assessment for EIS measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs and extreme temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 7) | 0.90 | Actual | 1.00 | 0.90 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.90 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 6) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.00 (NOTE 4)
0.35(NOTE 5) | Rectangular | 1.73 | 0.00 (NOTE 4)
0.20 (NOTE 5) | | | | | +| 15 | Influence of spherical coverage grid (NOTE 4) | 0.13 | Actual | 1 | 0.13 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 7) | 0.60 | Actual | 1.00 | 0.60 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 3) | | | | | Value | | | | | +| 27 | Systematic error related to beam peak search (NOTE 5) | | | | 0.7 | | | | | +| 28 | Systematic error related to EIS spherical coverage (NOTE 4) | | | | DL power step size, 0.2 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIS Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.83 | | | | | + +NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA. + NOTE 2: Void. + NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. + NOTE 4: This contributor shall only be considered for spherical EIS measurements. + NOTE 5: This contributor shall only be considered for EIS measurements. + NOTE 6: Applies to the system which has a structure of mechanical feed antenna positioning. + NOTE 7: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. The ETC QoQZ MU and ETC calibration path losses shall be applied to the NTC test cases if the ETC environment is used for NTC test cases. + +## B.20 + +## B.21 Adjacent Channel Selectivity + +Following tables summarize the MU threshold for Adjacent Channel Selectivity measurement. The origin MU values for different test setups with varies parameters can be found in following subclauses. + +**Table B.21-1: MU threshold for Adjacent Channel Selectivity** + +| Power Class | Frequency | MBW | Power | Threshold MU value (NOTE 1) | +|-------------|-----------------------------------|-------------------|----------------------|-----------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 8.08 | +| | 32.125GHz $< f \leq 40.8$ GHz | | | 8.08 | +| | 40.8GHz $< f \leq 44.3$ GHz | | | TBD | +| PC1 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 8.31 | +| | 32.125GHz $< f \leq 40.8$ GHz | | | 8.31 | +| PC5 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | P = Max Output Power | 8.31 | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30$ cm in Table B.21.2-2 for PC3 UEs and Table B.21.2-3 for PC1 UEs. + +### B.21.1 Uncertainty budget format and assessment for DFF + +FFS + +### B.21.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.21.2-1. + +**Table B.21.2-1: Total Uncertainty contributions for Adjacent Channel Selectivity measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement (Wanted Signal contributions) | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | gNB emulator uncertainty | B.2.2.17 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 14 | DUT repositioning | B.2.2.26 | +| Stage 2: DUT measurement (Modulated Interferer Signal specific contributions) | | | +| 15 | Positioning misalignment | B.2.2.1 | +| 16 | Measure distance uncertainty | B.2.2.2 | +| 17 | Quality of Quiet Zone | B.2.2.3 | +| 18 | Mismatch | B.2.2.4 | +| 19 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 20 | Modulated Interferer uncertainty | B.2.2.33 | +| 21 | Phase curvature | B.2.2.7 | +| 22 | Amplifier uncertainties | B.2.2.8 | +| 23 | Random uncertainty | B.2.2.9 | +| 24 | Influence of the XPD | B.2.2.10 | +| 25 | Insertion Loss Variation | B.2.2.11 | +| 26 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 27 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 28 | DUT repositioning | B.2.2.26 | +| 29 | Influence of offset antenna (Std.Dev) | B.2.2.35 | +| Stage 1: Calibration measurement (Wanted Signal contributions) | | | +| 30 | Mismatch | B.2.2.4 | +| 31 | Amplifier Uncertainties | B.2.2.8 | +| 32 | Misalignment of positioning System | B.2.2.13 | +| 33 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 34 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 35 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 36 | Phase centre offset of calibration antenna | B.2.2.18 | +| 37 | Quality of quiet zone for calibration process | B.2.2.19 | +| 38 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 39 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 40 | Insertion Loss Variation | B.2.2.11 | +| Stage 1: Calibration measurement (Modulated Interferer Signal contributions) | | | +| 41 | Mismatch | B.2.2.4 | +| 42 | Amplifier Uncertainties | B.2.2.8 | +| 43 | Misalignment of positioning System | B.2.2.13 | +| 44 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 45 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 46 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 47 | Phase centre offset of calibration antenna | B.2.2.18 | + +| | | | +|---------------------------------|-----------------------------------------------------------------------------|----------| +| 48 | Quality of quiet zone for calibration process | B.2.2.19 | +| 48 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 50 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 51 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 52 | Systematic error related to beam peak search | B.2.2.28 | +| 53 | Additional impact of interferer ACLR | B.2.2.32 | +| 54 | Influence of offset antenna (mean error) | B.2.2.35 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}, 44.3\text{GHz}\}$ , [P = maximum output power]. +- The uncertainty assessment for ACS is provided in Table B.21.2-2 for PC3 UEs and Table B.21.2-3 for PC1 and PC5 UEs. + +**Table B.21.2-2: Uncertainty assessment for Adjacent Channel Selectivity measurement (f=23.45GHz, 32.125GHz, 40.8GHz, 44.3GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------------------------------------------------------------------------|------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement (Wanted Signal contributions) | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 3 | Quality of Quiet Zone (NOTE 4)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 4 | Mismatch
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 4 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | gNB uncertainty on absolute level
(23.45GHz $\leq f \leq 40.8$ GHz) | 2.9 | Normal | 2.00 | 1.45 | +| 6 | gNB uncertainty on absolute level
(40.8GHz $< f \leq 44.3$ GHz) | 3.6 | Normal | 2.00 | 1.8 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | +| 14 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | +| Stage 2: DUT measurement (Modulated Interferer Signal specific contributions) | | | | | | +| 15 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 16 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Quality of Quiet Zone (NOTE 4)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.6 | Actual | 1.00 | 0.6 | +| 17 | Quality of Quiet Zone (NOTE 4)
(40.8GHz $< f \leq 44.3$ GHz) | 0.7 | Actual | 1.00 | 0.7 | +| 18 | Mismatch
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.30 | Actual | 1.00 | 1.30 | +| 18 | Mismatch
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Actual | 1.00 | 1.70 | +| 19 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 20 | Modulated Interferer uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | +| 21 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 22 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 23 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 24 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 25 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 26 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 27 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | +| 28 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | +| 29 | Influence of offset antenna (Std.Dev) (NOTE 5) | 0.00 | Normal | 2.00 | 0.00 | + +| Stage 1: Calibration measurement (Wanted Signal contributions) | | | | | | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------|-------------|------|------| +| 30 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 31 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 32 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 33 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 33 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 34 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 35 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 36 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 37 | Quality of quiet zone for calibration process (NOTE 4)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | +| 37 | Quality of quiet zone for calibration process (NOTE 4)
(40.8GHz $< f \leq 44.3$ GHz) | 0.5 | Actual | 1.00 | 0.5 | +| 38 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 39 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 40 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Stage 1: Calibration measurement (Modulated Interferer Signal contributions) | | | | | | +| 41 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 42 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 43 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 44 | Uncertainty of the Network Analyzer
(23.45GHz $\leq f \leq 40.8$ GHz) | 1.50 | Normal | 2.00 | 0.75 | +| 44 | Uncertainty of the Network Analyzer
(40.8GHz $< f \leq 44.3$ GHz) | 1.70 | Normal | 2.00 | 0.85 | +| 45 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 46 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 47 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 48 | Quality of quiet zone for calibration process (NOTE 4)
(23.45GHz $\leq f \leq 40.8$ GHz) | 0.4 | Actual | 1.00 | 0.4 | +| 48 | Quality of quiet zone for calibration process (NOTE 4)
(40.8GHz $< f \leq 44.3$ GHz) | 0.5 | Actual | 1.00 | 0.5 | + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|------|-------------|------|--------------| +| 48 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 50 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 51 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| | Systematic uncertainties (NOTE 2) | | | | Value | +| 52 | Systematic error related to beam peak search | | | | 0.5 | +| 53 | Additional impact of interferer ACLR | | | | 0.7 | +| 54 | Influence of offset antenna (mean error) (NOTE 5) | | | | 0.00 | +| | Total measurement uncertainty | | | | Value | +| | ACS Expanded uncertainty (23.45GHz $\leq f \leq 40.8\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | 8.08 | +| | ACS Expanded uncertainty (40.8GHz $< f \leq 44.3\text{GHz}$ ) ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | TBD | +| NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA.
NOTE 2: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 3: Applies to the system which has a structure of mechanical feed antenna positioning.
NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm.
NOTE 5: For MTSU derivation purpose, this value is set to 0.0 (no offset antenna case). | | | | | | + +**Table B.21.2-3: Uncertainty assessment for Adjacent Channel Selectivity measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC1 and PC5 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement (Wanted Signal contributions) | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | +| 14 | DUT repositioning | 0.35 | Rectangular | 1.73 | 0.20 | +| Stage 2: DUT measurement (Modulated Interferer Signal specific contributions) | | | | | | +| 15 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 16 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 18 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | +| 19 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 20 | Modulated Interferer uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | +| 21 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 22 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 23 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | +| 24 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 25 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 26 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 27 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | +| 28 | DUT repositioning | 0.35 | Rectangular | 1.73 | 0.20 | +| 29 | Influence of offset antenna (Std.Dev) (NOTE 5) | 0.00 | Normal | 2.00 | 0.00 | +| Stage 1: Calibration measurement (Wanted Signal contributions) | | | | | | +| 30 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 31 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 32 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 33 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 34 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 35 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | +| 36 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | + +| | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------|-------------|------|--------------|------| +| 37 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | +| 38 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | +| 39 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | +| 40 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | +| Stage 1: Calibration measurement (Modulated Interferer Signal contributions) | | | | | | | +| 41 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | +| 42 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | +| 43 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | +| 44 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | +| 45 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | +| 46 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | +| 47 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | +| 48 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | +| 48 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | +| 50 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | +| 51 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | +| Systematic uncertainties (NOTE 2) | | | | | Value | | +| 52 | Systematic error related to beam peak search | | | | | 0.7 | +| 53 | Additional impact of interferer ACLR | | | | | 0.7 | +| 54 | Influence of offset antenna (mean error) (NOTE 5) | | | | | 0.00 | +| Total measurement uncertainty | | | | | Value | | +| ACS Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | | 8.31 | | +| ACS Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] ( $32.125\text{GHz} < f \leq 40.8\text{GHz}$ ) | | | | | 8.31 | | +| NOTE 1: The analysis was done only for the case of operating at max output power, in-band, non-CA. | | | | | | | +| NOTE 2: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | | | | | +| NOTE 3: Applies to the system which has a structure of mechanical feed antenna positioning. | | | | | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | | | | | | | +| NOTE 5: For MTSU derivation purpose, this value is set to 0.0 (no offset antenna case). | | | | | | | + +## B.22 In-Band Blocking + +See B.21. + +## B.22.1 Uncertainty budget format and assessment for DFF + +See B.21.1. + +## B.22.2 Uncertainty budget format and assessment for IFF + +See B.21.2. + +--- + +## B.23 + +## B.24 + +## B.25 Receiver spurious emissions + +Editor's Note: + +- MU value analysis and offset value analysis for PC1, 2 and 4 are not complete. +- MU value analysis for various test setups in subsection B.25.x is not complete for above 80 GHz for PC3 +- Offset value analysis is not complete as it is derived from MU value analysis for above 80 GHz for PC3 + +Test procedure of general spurious emission comprises 2 stages: coarse TRP measurement and fine TRP measurement BW. Coarse TRP measurement is introduced to reduce the measurement time by applying sparser grids and/or wider measurement BW than fine TRP measurement while having offset dB more stringent test requirement in order not to cause additional misjudgement risk. For the frequency ranges for which coarse TRP measurement does not PASS, the measurement is continued with fine TRP measurement procedure. + +Table B.25-1 summarizes the MU threshold for fine TRP measurements for General spurious emissions. The origin MU values for fine TRP measurement for different test setups can be found in following subclauses. + +**Table B.25-1: MU threshold for TRP measurement for Rx spurious emission** + +| Power Class | Frequency | In-band BW | In-band Power (NOTE2) | Threshold MU value [dB] (NOTE1) | +|-------------|-----------------------------|--------------|-----------------------|---------------------------------| +| PC3 | 6 GHz <= f <= 12.75 GHz | BW <= 400MHz | P = Max Output Power | 5.64 | +| | 12.75 GHz <= f <= 23.45 GHz | | | 5.60 | +| | 23.45 GHz <= f <= 40.8 GHz | | | 6.11 | +| | 40.8 GHz <= f <= 66 GHz | | | 7.65 | +| | 66 GHz <= f <= 80 GHz | | | 7.95 | +| PC1 | 6 GHz <= f <= 12.75 GHz | BW <= 400MHz | P = Max Output Power | 5.63 | +| | 12.75 GHz <= f <= 23.45 GHz | | | 5.59 | +| | 23.45 GHz <= f <= 40.8 GHz | | | 6.10 | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--|------| +| | 40.8 GHz <= f <= 66 GHz | | 7.64 | +| | 66 GHz <= f <= 80 GHz | | 7.95 | +| NOTE 1: Total EIRP Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.25.2-3 to Table B.25.2-11 for PC3 UEs and in Table B.25.2-12 to Table B.25.2-16 for PC1 UEs. | | | | + +Table B.25-2 provides valid coarse TRP measurement grids and corresponding offset dB value that may be used for UE general spurious emission test case. The offset value is derived as 95%-tile TRP measurement uncertainty including the effect from uncertainty due to Coarse TRP measurement grid, excluding influence of noise. + +**Table B.25-2: Coarse TRP measurement grids and offset values for UE Rx spurious emission** + +| Power Class | Coarse TRP measurement grid | Frequency | Min Number of measurement points on the grid | Influence of coarse TRP measurement grid (dB) | Systematic error due to coarse TRP calculation/quadrature (dB) | Offset value (dB) | +|-------------|------------------------------------------------|-----------------------------|----------------------------------------------|-----------------------------------------------|----------------------------------------------------------------|-------------------| +| PC3 | Constant density grid (charged particle based) | 6 GHz <= f <= 12.75 GHz | 35 | 0.94 | 0.09 | 5.38 | +| | | 12.75 GHz <= f <= 23.45 GHz | | | | 5.35 | +| | | 23.45 GHz <= f <= 40.8 GHz | | | | 5.49 | +| | | 40.8 GHz <= f <= 66 GHz | | | | 7.31 | +| | | 66 GHz <= f <= 80 GHz | | | | 7.61 | +| | Constant step size grid | 6 GHz <= f <= 12.75 GHz | 62 | 0.97 | 0.2 | 5.51 | +| | | 12.75 GHz <= f <= 23.45 GHz | | | | 5.48 | +| | | 23.45 GHz <= f <= 40.8 GHz | | | | 5.62 | +| | | 40.8 GHz <= f <= 66 GHz | | | | 7.43 | +| | | 66 GHz <= f <= 80 GHz | | | | 7.73 | +| PC1 | Constant density grid (charged particle based) | 6 GHz <= f <= 12.75 GHz | FFS | FFS | FFS | FFS | +| | | 12.75 GHz <= f <= 23.45 GHz | | | | FFS | +| | | 23.45 GHz <= f <= 40.8 GHz | | | | FFS | +| | | 40.8 GHz <= f <= 66 GHz | | | | FFS | +| | | 66 GHz <= f <= 80 GHz | | | | FFS | +| | Constant step size grid | 6 GHz <= f <= 12.75 GHz | FFS | FFS | FFS | FFS | +| | | 12.75 GHz <= f <= 23.45 GHz | | | | FFS | +| | | 23.45 GHz <= f <= 40.8 GHz | | | | FFS | + +| | | | | | | | +|--|--|-----------------------------------------------|--|--|--|-----| +| | | $f \leq 40.8 \text{ GHz}$ | | | | | +| | | $40.8 \text{ GHz} \leq f \leq 66 \text{ GHz}$ | | | | FFS | +| | | $66 \text{ GHz} \leq f \leq 80 \text{ GHz}$ | | | | FFS | + +NOTE 1: Based on Total TRP Expanded MU for IFF for Quiet Zone size $\leq 30\text{cm}$ in Table B.25.2-3 to Table B.25.2-11, replacing “Influence of TRP measurement grid” and “Systematic error due to TRP calculation/quadrature” by the values for coarse TRP grid, and excluding “Influence of noise”. + +## B.25.1 Uncertainty budget format and assessment for DFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.25.1-1. + +**Table B.25.1-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of TRP measurement grid | B.2.1.22 | +| 14 | Influence of beam peak search grid | B.2.1.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 16 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 17 | Mismatch | B.2.1.4 | +| 18 | Amplifier uncertainties | B.2.1.8 | +| 19 | Misalignment of positioning System | B.2.1.13 | +| 20 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 21 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 23 | Phase centre offset of calibration antenna | B.2.1.18 | +| 24 | Quality of quiet zone for calibration process | B.2.1.19 | +| 25 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 26 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 27 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 28 | Systematic error due to TRP calculation/quadrature | B.2.1.24 | +| 29 | Influence of noise | B.2.1.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D + +- The uncertainty assessment has been derived for the case of $D = [5 \text{ cm}]$ , $f = \{6 \text{ GHz to } 80 \text{ GHz}\}$ , $P = [\text{Off power}]$ . +- The uncertainty assessment for TRP is provided in Table B.25.1-2 to B.25.1-xx + +**Table B.25.1-2: Uncertainty assessment for TRP measurement (f=TBD, D=TBD)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | | | | +| 2 | Measure distance uncertainty | | | | | +| 3 | Quality of quiet zone | | | | | +| 4 | Mismatch (NOTE 1) | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | | | | | +| 7 | Phase curvature | | | | | +| 8 | Amplifier uncertainties | | | | | +| 9 | Random uncertainty | | | | | +| 10 | Influence of the XPD | | | | | +| 11 | Insertion Loss Variation | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | | | | +| 13 | Influence of TRP measurement grid (NOTE 3) | | | | | +| 14 | Influence of beam peak search grid (NOTE 4) | | | | | +| 15 | Multiple measurement antenna uncertainty | | | | | +| 16 | DUT repositioning | | | | | +| Stage 1: Calibration measurement | | | | | | +| 17 | Mismatch | | | | | +| 18 | Amplifier uncertainties | | | | | +| 19 | Misalignment of positioning System | | | | | +| 20 | Uncertainty of the Network Analyzer | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | | | | +| 23 | Phase centre offset of calibration antenna | | | | | +| 24 | Quality of quiet zone for calibration process | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | | | | | +| 26 | Influence of the calibration antenna feed cable | | | | | +| 27 | Insertion Loss Variation | | | | | +| TRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | | +| Systematic uncertainties (NOTE 5) | | | | | Value | +| 28 | Systematic error due to TRP calculation/quadrature (NOTE 3) | | | | | +| 29 | Influence of noise | | | | | +| Total measurement uncertainty | | | | | | +| TRP total measurement uncertainty [dB] | | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The analysis was done only for the case of operating at max output power, in-band, non-CA. | +| NOTE 2: | The assessment assumes maximum DUT output power. | +| NOTE 3: | This contributor shall only be considered for TRP measurements. | +| NOTE 4: | This contributor shall only be considered for EIRP measurements. | +| NOTE 5: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 6: | Void | + +## B.25.2 Uncertainty budget format and assessment for IFF + +The uncertainty contributions that may impact the overall MU value are listed in Table B.25.2-1. + +**Table B.25.2-1: Uncertainty contributions for TRP measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of TRP measurement grid | B.2.2.22 | +| 14 | Influence of beam peak search grid | B.2.2.23 | +| 15 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 16 | DUT repositioning | B.2.2.26 | +| 17 | Misalignment of DUT due to change of DUT orientation | B.2.2.31 | +| Stage 1: Calibration measurement | | | +| 18 | Mismatch | B.2.2.4 | +| 19 | Amplifier Uncertainties | B.2.2.8 | +| 20 | Misalignment of positioning System | B.2.2.13 | +| 21 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 24 | Phase centre offset of calibration antenna | B.2.2.18 | +| 25 | Quality of quiet zone for calibration process | B.2.2.19 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 27 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 28 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 29 | Systematic error due to TRP calculation/quadrature | B.2.2.24 | +| 30 | Influence of noise | B.2.2.27 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as $D$ +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{6 \text{ GHz to } 80 \text{ GHz}\}$ , $P = \text{Receiver Spurious Core Requirement Level} + \text{Relaxation}$ (For n257, 10.2dB for $6\text{GHz} \leq f < 20\text{GHz}$ , 17.2 dB for $20\text{GHz} \leq f < 40\text{GHz}$ , 33.1dB for $40\text{GHz} \leq f \leq 2^{\text{nd}}$ harmonic) +- The uncertainty assessment for TRP is provided from Table B.25.2-2 to Table B.25.2-11 for PC3 UEs and from Table B.25.2-12 to Table B.25.2-16 for PC1 UEs. + +**Table B.25.2-2: Void** + +**Table B.25.2-3: Uncertainty assessment for TRP measurement (f=6 GHz to 12.75 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 4 | Mismatch | 1.60 | Actual | 1.00 | 1.60 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.00 | Normal | 2.00 | 1.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $6 \text{ GHz} < f \leq 12.75 \text{ GHz}$ ) [dB] (a) | 5.00 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | Influence of noise ( $6 \text{ GHz} < f \leq 12.75 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 5.64 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-4: void** + +**Table B.25.2-5: Uncertainty assessment for TRP measurement (f=12.75 GHz to 23.45 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 4 | Mismatch | 1.60 | Actual | 1.00 | 1.60 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.16 | Normal | 2.00 | 1.08 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty (12.75 GHz < f <= 23.45 GHz) [dB] (a) | 4.96 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | Influence of noise (12.75 GHz < f <= 23.45 GHz) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 5.60 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-6: Void** + +**Table B.25.2-7: Uncertainty assessment for TRP measurement (f=23.45 GHz to 40.8 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 1.50 | Actual | 1.00 | 1.50 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.73 | Normal | 2.00 | 1.37 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.6 | Normal | 2.00 | 0.3 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) [dB] (a) | 5.11 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | Influence of noise ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) (c) | 1.0 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 6.11 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-8: Void** + +**Table B.25.2-9: Uncertainty assessment for TRP measurement (f= 40.8 GHz to 66 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.0 | Normal | 2.00 | 0.0 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.0 | Normal | 2.00 | 2.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.7 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) [dB] (a) | 7.01 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | Influence of noise ( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 7.65 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-10: Void** + +**Table B.25.2-11: Uncertainty assessment for TRP measurement (f= 66 GHz to 80 GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.0 | Normal | 2.00 | 2.0 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 3.0 | Normal | 2.00 | 1.50 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.32 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.7 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) [dB] (a) | 7.31 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.0 | +| 30 | Influence of noise ( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 7.95 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-12: Uncertainty assessment for TRP measurement (f=6 GHz to 12.75 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 4 | Mismatch | 1.60 | Actual | 1.00 | 1.60 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.00 | Normal | 2.00 | 1.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.70 | Actual | 1.00 | 0.70 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $[6] \text{ GHz} < f \leq [12.75] \text{ GHz}$ ) [dB] (a) | 4.99 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | Influence of noise ( $6 \text{ GHz} < f \leq 12.75 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 5.63 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-13: Uncertainty assessment for TRP measurement (f=12.75 GHz to 23.45 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 4 | Mismatch | 1.60 | Actual | 1.00 | 1.60 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.16 | Normal | 2.00 | 1.08 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $12.75 \text{ GHz} < f \leq 23.45 \text{ GHz}$ ) [dB] (a) | 4.95 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | Influence of noise ( $12.75 \text{ GHz} < f \leq 23.45 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 5.59 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-14: Uncertainty assessment for TRP measurement (f=23.45 GHz to 40.8 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 1.50 | Actual | 1.00 | 1.50 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 2.73 | Normal | 2.00 | 1.37 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.5 | Normal | 2.00 | 0.75 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 0.6 | Normal | 2.00 | 0.3 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) [dB] (a) | 5.10 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | Influence of noise ( $23.45 \text{ GHz} < f \leq 40.8 \text{ GHz}$ ) (c) | 1.0 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 6.10 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-15: Uncertainty assessment for TRP measurement (f= 40.8 GHz to 66 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.0 | Normal | 2.00 | 2.00 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.25 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/AN/A | Actual | 1 | N/AN/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.7 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) [dB] (a) | 7.00 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | Influence of noise ( $40.8 \text{ GHz} < f \leq 66 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 7.64 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +**Table B.25.2-16: Uncertainty assessment for TRP measurement (f= 66 GHz to 80 GHz, Quiet Zone size $\leq 30$ cm) for PC1 UEs** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | +| 4 | Mismatch | 2.30 | Actual | 1.00 | 2.30 | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 6 | Uncertainty of the RF power measurement equipment | 4.0 | Normal | 2.00 | 2.0 | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | +| 8 | Amplifier uncertainties | 3.0 | Normal | 2.00 | 1.50 | +| 9 | Random uncertainty | 0.5 | Normal | 2.00 | 0.25 | +| 10 | Influence of the XPD | 0.09 | U-shaped | 1.41 | 0.064 | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | +| 13 | Influence of TRP measurement grid (NOTE 1) | 0.25 | Actual | 1 | 0.32 | +| 14 | Influence of beam peak search grid (NOTE 2) | N/A | Actual | 1 | N/A | +| 15 | Multiple measurement antenna uncertainty (NOTE 5) | 0.15 | Actual | 1 | 0.15 | +| 16 | DUT repositioning | 0.00 | Rectangular | 1.73 | 0.00 | +| 17 | Misalignment of DUT due to change of DUT orientation | 0.10 | Actual | 1 | 0.10 | +| Stage 1: Calibration measurement | | | | | | +| 18 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | +| 19 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | +| 20 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | +| 21 | Uncertainty of the Network Analyzer | 1.7 | Normal | 2.00 | 0.85 | +| 22 | Uncertainty of the absolute gain of the calibration antenna | 1.70 | Normal | 2.00 | 0.85 | +| 23 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.05 | Rectangular | 1.73 | 0.03 | +| 24 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | +| 25 | Quality of quiet zone for calibration process (NOTE 4) | 0.60 | Actual | 1.00 | 0.60 | +| 26 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | +| 27 | Influence of the calibration antenna feed cable | 0.28 | Normal | 2.00 | 0.14 | +| 28 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | +| Expanded uncertainty (1.96\sigma - confidence interval of 95 %) | | | | | Value | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|--------------| +| | TRP Expanded uncertainty ( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) [dB] (a) | 7.31 | +| | Systematic uncertainties (NOTE 3) | Value | +| 29 | Systematic error due to TRP calculation/quadrature (NOTE 1) (b) | 0.00 | +| 30 | Influence of noise ( $66 \text{ GHz} < f \leq 80 \text{ GHz}$ ) (c) | 0.64 | +| 31 | Systematic error related to beam peak search (NOTE 2) | N/A | +| | Total measurement uncertainty | Value | +| | Total measurement uncertainty (a)+(b)+(c) [dB] | 7.95 | +| NOTE 1: This contributor shall only be considered for TRP measurements. | | | +| NOTE 2: This contributor shall only be considered for EIRP measurements. | | | +| NOTE 3: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | | | +| NOTE 4: Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size of less or equal to 30 cm. | | | +| NOTE 5: Applies to the system which has a structure of mechanical feed antenna positioning. | | | + +--- + +## Annex C: Acceptable uncertainty of test system for test cases defined in TS 38.521-3 for radiative testing + +FFS + +--- + +## Annex D: Acceptable uncertainty of test system for test cases defined in TS 38.521-4 for radiative testing + +Editor's note: The MU tables in D-1, D-2, and D-3 serve as sample, consolidated baseline tables for demodulation test cases and can be removed once the MU tables customized for each TS 38.521-4 test case have been finalized. + +This annex contains suggested uncertainties for each test case in TS 38.521-4. + +The baseline MU table for Mode 1 (conditions with external noise) is shown in Table D-1 for baseband-combining implementation and in Table D-2 for external-combining implementation. + +**Table D-1: Uncertainty Contributions for Mode 1 Demodulation Test Cases for PC1 and PC3 +(Baseband-Combining Implementation)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|----------------------------|---------------------------------|---------|----------------------------------------| +| Signal-to-noise ratio uncertainty | | | | | | +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | N/A | N/A | | +| 2 | Measure distance uncertainty | | N/A | N/A | | +| 3 | Quality of Quiet Zone | | N/A | N/A | | +| 4 | Mismatch | | N/A | N/A | | +| 5 | Standing wave between the DUT and measurement antenna | | N/A | N/A | | +| 6 | gNB emulator SNR uncertainty | 0.3 | Note 3 | 1.96 | 0.153 | +| 7 | Phase curvature | | N/A | N/A | | +| 8 | Amplifier uncertainties | | N/A | N/A | | +| 9 | Random uncertainty | | N/A | N/A | | +| 10 | Influence of the XPD | | N/A | N/A | | +| 11 | Insertion Loss Variation | | N/A | N/A | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | N/A | N/A | | +| 13 | Multiple measurement antenna uncertainty | | N/A | N/A | | +| 14 | DUT repositioning | | N/A | N/A | | +| Stage 1: Calibration measurement | | | | | | +| 15 | Mismatch | | N/A | N/A | | +| 16 | Amplifier Uncertainties | | N/A | N/A | | +| 17 | Misalignment of positioning System | | N/A | N/A | | +| 18 | Uncertainty of the Network Analyzer | | N/A | N/A | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | | N/A | N/A | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | N/A | N/A | | +| 21 | Phase centre offset of calibration antenna | | N/A | N/A | | +| 22 | Quality of quiet zone for calibration process | | N/A | N/A | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | | N/A | N/A | | +| 24 | Influence of the calibration antenna feed cable | | N/A | N/A | | +| 25 | Insertion Loss Variation | | N/A | N/A | | +| Total Signal-to-Noise ratio uncertainty | | | | | 0.153 | +| Other contributors affecting test result | | | | | | +| 27 | gNB emulator fading model impairments | 0.5 for 1Tx
0.7 for 2Tx | Note 3 | 1.96 | 0.255 for 1Tx
0.357 for 2Tx | +| 28 | AWGN flatness and signal flatness, max deviation for any Resource Block, relative to average over BW Config (Note 4) | 3.6 | Note 3 | 1.96 | 1.837 | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|--------|------|-----------------------------------------------------------------------------------------------| +| 29 | SNR uncertainty due to finite test time | 0.3 for PDSCH and Doppler < 100 Hz
0.0 for PDSCH and Doppler ≥ 100 Hz
0.4 for PDCCH | Note 3 | 1.96 | 0.153 for PDSCH and Doppler < 100 Hz
0.0 for PDSCH and Doppler ≥ 100 Hz
0.204 for PDCCH | +| | Systematic uncertainties | | | | Value | +| 26 | Impact on non-ideal isolation between branches for the wireless cable mode | | | | 0.45 (Note 1)
0.60 (Note 2) | +| | Overall system uncertainty | | | | Value | +| | | | | | Note 5 | +|

Note 1: applies to Rank 2 test cases for FR2a, FR2b, and FR2c

Note 2: applies to Rank 1 test cases for FR2a, FR2b, and FR2c

Note 3: Divisor of 1.96 is applied as the uncertainty value is based on 95% confidence level k=1.96.

Note 4: AWGN flatness and signal flatness has x 0.25 effect on the required SNR. This sensitivity factor shall be considered in the calculation of the test case specific uncertainty.

Note 5: Example calculation for fading conditions:
Overall system uncertainty for fading conditions comprises five quantities:
1. Total Signal-to-noise ratio uncertainty
2. gNB emulator fading model impairments
3. Effect of AWGN flatness and signal flatness
4. SNR uncertainty due to finite test time
5. Impact on non-ideal isolation between branches for the wireless cable mode
Items 1, 2, 3 and 4 are assumed to be uncorrelated so can be root sum squared. Item 5 is systematic and is added:
AWGN flatness and signal flatness has x 0.25 effect on the required SNR, so use sensitivity factor of x 0.25 for the uncertainty contribution.
Overall system uncertainty = 1.96 \times \sqrt{(\text{Total Signal-to-noise ratio uncertainty})^2 + (\text{gNB emulator fading model impairments})^2 + (0.25 \times \text{AWGN flatness and signal flatness})^2 + (\text{SNR uncertainty due to finite test time})^2} + Impact on non-ideal isolation between branches for the wireless cable mode

| | | | | | + +**Table D-1a: Overall system uncertainty for Mode 1 Demodulation Test Cases for PC1 and PC3 (Baseband-Combining Implementation)** + +| Overall system uncertainty | Value | +|-----------------------------------------|--------------| +| PDSCH 1Tx with Doppler < 100 Hz | 1.71 | +| PDSCH 2Tx with Doppler < 100 Hz, rank 1 | 1.82 | +| PDSCH 2Tx with Doppler < 100 Hz, rank 2 | 1.67 | +| PDSCH 1Tx with Doppler ≥ 100 Hz | 1.67 | +| PDSCH 2Tx with Doppler ≥ 100 Hz, rank 1 | 1.78 | +| PDSCH 2Tx with Doppler ≥ 100 Hz, rank 2 | 1.63 | +| PDCCH 1Tx, rank 1 | 1.74 | +| PDCCH 2Tx, rank 1 | 1.84 | + +**Table D-2: Uncertainty Contributions for Mode 1 Demodulation Test Cases (External-Combining Implementation)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Signal-to-noise ratio uncertainty | | | | | | | | | | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | | [Normal] | [2.00] | | | | | | +| 2 | Measure distance uncertainty | | [Rectangular] | [1.73] | | | | | | +| 3 | Quality of Quiet Zone | | [Actual] | [1.00] | | | | | | +| 4 | Mismatch | | [Actual] | [1.00] | | | | | | +| 5 | Standing wave between the DUT and measurement antenna | | [U-shaped] | [1.41] | | | | | | +| 6 | gNB emulator SNR uncertainty | | [Normal] | [2.00] | | | | | | +| 7 | Phase curvature | | [U-shaped] | [1.41] | | | | | | +| 8 | Amplifier uncertainties | | [Normal] | [2.00] | | | | | | +| 9 | Random uncertainty | | [Normal] | [2.00] | | | | | | +| 10 | Influence of the XPD | | [U-shaped] | [1.41] | | | | | | +| 11 | Insertion Loss Variation | | [Rectangular] | [1.73] | | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | [Actual] | [1.00] | | | | | | +| 13 | Multiple measurement antenna uncertainty | | [Actual] | [1.00] | | | | | | +| 14 | DUT repositioning | | [Rectangular] | [1.73] | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 15 | Mismatch | | [U-shaped] | [1.41] | | | | | | +| 16 | Amplifier Uncertainties | | [Normal] | [2.00] | | | | | | +| 17 | Misalignment of positioning System | | [Normal] | [2.00] | | | | | | +| 18 | Uncertainty of the Network Analyzer | | [Normal] | [2.00] | | | | | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | | [Normal] | [2.00] | | | | | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | [Rectangular] | [1.73] | | | | | | +| 21 | Phase centre offset of calibration antenna | | [Rectangular] | [1.73] | | | | | | +| 22 | Quality of quiet zone for calibration process | | [Actual] | [1.00] | | | | | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | | [U-shaped] | [1.41] | | | | | | +| 24 | Influence of the calibration antenna feed cable | | [Normal] | [2.00] | | | | | | +| 25 | Insertion Loss Variation | | [Rectangular] | [1.73] | | | | | | +| Systematic uncertainties | | | | | Value | | | | | +| 26 | Impact on non-ideal isolation between branches for the wireless cable mode | | | | 0.45 (Note 1)
0.60 (Note 2) | | | | | +| Total Signal-to-Noise ratio uncertainty | | | | | | | | | | +| Other contributors affecting test result | | | | | | | | | | +| 27 | gNB emulator fading model impairments | | [Normal] | [2.00] | | | | | | +| 28 | AWGN flatness and signal flatness, max deviation for any Resource Block, relative to average over $BW_{Config}$ (Note 3) | | [Actual] | 1.00 | | | | | | +| 29 | Result variation due to finite test time | | [Actual] | [1.00] | | | | | | + +Note 1: applies to Rank 2 test cases for FR2a, FR2b, and FR2c + +Note 2: applies to Rank 1 test cases for FR2a, FR2b, and FR2c + +Note 3: AWGN flatness and signal flatness has $\times 0.25$ effect on the required SNR. This sensitivity factor shall be considered in the calculation of the test case specific uncertainty. + +The baseline MU table for Mode 2 (noise free conditions) is shown in Table D-3. + +**Table D-3: Uncertainty Contributions for Mode 2 Demodulation Test Cases** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | | [Normal] | [2.00] | | +| 2 | Measure distance uncertainty | | [Rectangular] | [1.73] | | +| 3 | Quality of Quiet Zone | | [Actual] | [1.00] | | +| 4 | Mismatch | | [Actual] | [1.00] | | +| 5 | Standing wave between the DUT and measurement antenna | | [U-shaped] | [1.41] | | +| 6 | gNB uncertainty on absolute level | | [Normal] | [2.00] | | +| 7 | Phase curvature | | [U-shaped] | [1.41] | | +| 8 | Amplifier uncertainties | | [Normal] | [2.00] | | +| 9 | Random uncertainty | | [Normal] | [2.00] | | +| 10 | Influence of the XPD | | [U-shaped] | [1.41] | | +| 11 | Insertion Loss Variation | | [Rectangular] | [1.73] | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | [Actual] | [1.00] | | +| 13 | Multiple measurement antenna uncertainty | | [Actual] | [1.00] | | +| 14 | DUT repositioning | | [Rectangular] | [1.73] | | +| Stage 1: Calibration measurement | | | | | | +| 15 | Mismatch | | [U-shaped] | [1.41] | | +| 16 | Amplifier Uncertainties | | [Normal] | [2.00] | | +| 17 | Misalignment of positioning System | | [Normal] | [2.00] | | +| 18 | Uncertainty of the Network Analyzer | | [Normal] | [2.00] | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | | [Normal] | [2.00] | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | [Rectangular] | [1.73] | | +| 21 | Phase centre offset of calibration antenna | | [Rectangular] | [1.73] | | +| 22 | Quality of quiet zone for calibration process | | [Actual] | [1.00] | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | | [U-shaped] | [1.41] | | +| 24 | Influence of the calibration antenna feed cable | | [Normal] | [2.00] | | +| 25 | Insertion Loss Variation | | [Rectangular] | [1.73] | | +| Systematic uncertainties | | | | | Value | +| 26 | Systematic error related to beam peak search | | | | | +| 27 | Impact on non-ideal isolation between branches for the wireless cable mode | | | | 0.45 (Note 1)
0.60 (Note 2) | +| Other contributors affecting test result | | | | | | +| 28 | Result variation due to finite test time | | [Actual] | [1.00] | | + +Note 1: applies to Rank 2 test cases for FR2a, FR2b, and FR2c + +Note 2: applies to Rank 1 test cases for FR2a, FR2b, and FR2c + + + +--- + +## D.1 Uncertainty budget calculation principle + +### D.1.1 Uncertainty budget calculation principle for DNF + +The uncertainty tables cover the actual measurement using the DUT receiver. If applicable, any uncertainty arising from a calibration or alignment process before the measurements should also be included. + +The MU budget should comprise of a minimum 5 headings: + +- 1) The uncertainty source, +- 2) Uncertainty value, +- 3) Distribution of the probability, +- 4) Divisor based on distribution shape, +- 5) Calculated standard uncertainty (based on uncertainty value and divisor). + +### D.1.2 Uncertainty budget calculation principle for DFF + +The same as defined in D.1.1. + +### D.1.3 Uncertainty budget calculation principle for IFF + +The same as defined in D.1.1. + +--- + +## D.2 Measurement error contribution descriptions + +### D.2.1 Measurement error contribution descriptions for DNF + +#### D.2.1.1 gNB emulator SNR uncertainty + +This contribution originates from setting the ratio of signal and noise in the conducted part of the test system. It is estimated to be the same as for LTE conducted testing in TS 36.521-1 Annex F, which is $\pm 0.3\text{dB}$ . The default for values in 36.521-1 Annex F is 95% confidence interval, normal distribution. + +#### D.2.1.2 gNB emulator Downlink EVM + +When simulations of demodulation performance are run, the downlink signal is modelled with a defined EVM, representing imperfections in the signal transmitted by the gNB. This EVM value is agreed across companies to align simulations, and is normally lower than the gNB EVM requirement, to represent “typical” conditions. The EVM used for simulations is therefore built in to the requirement points, normally specified as the SNR required to meet a specified throughput, with a defined modulation and Reference channel, under defined propagation conditions. + +For a conformance test, the EVM defined for the simulations is taken as a maximum allowed value for the test system, as a worse gNB emulator EVM would make the signal harder to demodulate, and disadvantage the UE. In a test system the EVM cannot normally be set to a specific value, but is specified to be no higher than a defined value. + +Following this approach, the uncertainty from gNB emulator Downlink EVM is a one-sided distribution, with beneficial effect. Without treating the positive and negative uncertainties separately, and as it would not make the SNR worse, the effective uncertainty is 0dB. + +### D.2.1.3 gNB emulator fading model impairments + +This contribution originates from imperfections in the gNB emulator fading model, compared to the applied fading model. It is estimated to be the same as for LTE conducted testing in TS 36.521-1 Annex F, which is $\pm 0.5\text{dB}$ . The default for values in 36.521-1 Annex F is 95% confidence interval, normal distribution. + +## D.2.2 Measurement error contribution descriptions for DFF + +### D.2.2.1 gNB emulator SNR uncertainty + +See D.2.1.1. + +### D.2.2.2 gNB emulator Downlink EVM + +See D.2.1.2. + +### D.2.2.3 gNB emulator fading model impairments + +See D.2.1.3. + +## D.2.3 Measurement error contribution descriptions for IFF + +The Measurement uncertainty contributions and uncertainty assessment are expected to be the same as for the Direct near field (DNF) setup in D.2.1. + +### D.2.3.1 gNB emulator SNR uncertainty + +See D.2.1.1. + +### D.2.3.2 gNB emulator Downlink EVM + +See D.2.1.2. + +### D.2.3.3 gNB emulator fading model impairments + +See D.2.1.3. + +## D.3 Assessment of testable DL SNR range and accuracy + +The signal and the noise provided by the test system are both attenuated by the over-the-air link loss. The UE noise then adds to the noise provided by the test system, hence degrading the SNR seen by the UE and potentially limiting the testable SNR range. The calculations and graphs in this clause allow this SNR degradation to be assessed over a range of scenarios. + +For conducted tests, the noise provided by the test system can be set much higher than the UE noise and the SNR degradation is negligible. However for over-the-air test systems, the power that can realistically be delivered into the + +test system probe antenna is limited, so the test point is likely to be closer to the UE noise and a small SNR degradation is allowable. + +### D.3.1 Method and Parameters + +The method is the same as in clause B.2.1.5.1 of TR 38.810 [13], but some values related to the test system are different. The calculation of noise level is described in clause 7.2.1.3 of TR 38.810 [13]. Under fading conditions the backoff is [17.71] dB instead of 13 dB when no fading applies. + +#### D.3.2.1 SNR range for $\text{SNR}_{\text{RP}} - \text{SNR}_{\text{BB}} \leq 1\text{dB}$ for DFF + +FFS + +#### D.3.2.2 SNR range for $\text{SNR}_{\text{RP}} - \text{SNR}_{\text{BB}} \leq 1\text{dB}$ for IFF + +Based on the method of setting the noise from the Test system to give a maximum of 1dB degradation in overall SNR between reference point and baseband, we can then work back through the signal chain to determine how high the SNR can be set. As the noise is set to a fixed level, the maximum SNR is set by the test system power amplifier and the channel bandwidth to be tested. + +The SNR upper bound depends on the type of test system. For the Indirect Far field (IFF) setup the diagram below illustrates the principle, and is based on the “IFF 100MHz ( n257, n258, n261)” tab of the accompanying spreadsheet. + +The process works back through the signal chain, from left to right in the diagram. + +![A detailed diagram showing the estimation of single band UE SNR range for Indirect far field (IFF) when no fading applies. It maps power levels from the test equipment (dBm/Ch BW) down to the UE antenna and RF (dBm/Hz), accounting for various gains and losses. Key components include TE amplifier 1dB compression (+23dBm), backoff (-17.7dB), available SNR range, scale for Ch BW (+80dB), cable loss (-6.3dB), free space path loss (-62.6 dB), TE DL setting uncertainty (± 5.19 dB), probe ant gain (12dB), and UE noise floor calculations. The diagram is divided into four vertical sections: UE Antenna and RF, Reference point, Over-the-air, and Test equipment, all under the heading Beam-peak AoA.](12ee52d07df077addb627226083e63b8_img.jpg) + +**dBm/Ch BW** + ++30 ++20 ++10 +0 +-10 +-90 +-100 +-110 +-120 +-130 +-140 +-150 +-160 +-170 + +TE amplifier 1dB compression +23dBm + +Backoff from 1dB compression -17.7dB + +Available SNR range + +Scale for Ch BW, 100MHz = +80dB + +Cable loss -6.3dB + +Free space path lossIFF, -62.6 dB + +TE DL setting uncertainty, $\pm 5.19$ dB + +Probe Ant gain 12dB + +**Noc** + +Total noise → + +1dB noise increase + +UE noise + +Wanted noise 6dB above UE noise + +Allow 0.75dB max UE multi-band relaxation + +UE RefsensSPC3, n257, 50MHz = -88.3 dBm - 10Log10(120kHz x 32 x 12) = -164.9 dBm/Hz @-1dB SNR + +**dBm/Hz** + +| | | | | +|-------------------|-----------------|--------------|----------------| +| UE Antenna and RF | Reference point | Over-the-air | Test equipment | +| Beam-peak AoA | | | | + +A detailed diagram showing the estimation of single band UE SNR range for Indirect far field (IFF) when no fading applies. It maps power levels from the test equipment (dBm/Ch BW) down to the UE antenna and RF (dBm/Hz), accounting for various gains and losses. Key components include TE amplifier 1dB compression (+23dBm), backoff (-17.7dB), available SNR range, scale for Ch BW (+80dB), cable loss (-6.3dB), free space path loss (-62.6 dB), TE DL setting uncertainty (± 5.19 dB), probe ant gain (12dB), and UE noise floor calculations. The diagram is divided into four vertical sections: UE Antenna and RF, Reference point, Over-the-air, and Test equipment, all under the heading Beam-peak AoA. + +**Figure D.3.2.2-1: Estimation of single band UE SNR range for Indirect far field (IFF) when no fading applies** + +The test equipment must supply at least the wanted noise level at the reference point. If the noise was lower, the degradation in SNR would be greater than 1dB, and may cause a conformant UE to fail. + +For mode2 (noise free) scenarios, the expected SNR at the UE reference point is determined by the level of wanted signal power set by the TE above the UE REFSENS point. + +The accuracy of setting the signal and noise levels has been taken as $\pm 5.19$ dB. + +Inclusion of this contribution directly reduces the maximum SNR that can be measured by a test system for a given channel bandwidth. + +To find the maximum SNR that can be measured by a test system with a specific Channel BW, the baseband SNR in the spreadsheet is increased until the value “Wanted signal + headroom, dBm/Ch BW” is just below the “Available DL power at CW 1dB compression at QZ, dBm” value. For fading conditions, the “Backoff from P1dB” with a value of $-11.08$ dB valid for modulations up to 64 QAM has been applied. In the case without fading with added noise, the “Backoff from P1dB” is $[-13]$ dB valid for modulations up to 64 QAM. The resulting values for $\text{SNR}_{\text{BB}}$ are given in Table D.3.2.2-1 for tests cases making use of fading, D.3.2.2-2 for test cases without fading with added Noise. + +Single band UE values are obtained by setting the UE multi-band relaxation factor to 0 dB. + +**Table D.3.2.2-1: Predicted $\text{SNR}_{\text{BB}}$ upper bound values for Indirect far field (IFF) with 30cm QZ, PC3, 100MHz CHBW, modulation up to 64 QAM under fading conditions** + +| | Operating Band | Maximum $\text{SNR}_{\text{BB}}$ (dB) | | | +|---------------------------------|----------------|---------------------------------------|--------------|--------------| +| | | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| Multi-band UE (Note) | n257 | 30.6 | 27.5 | 24.4 | +| | n258 | 30.6 | 27.5 | 24.4 | +| | n259 | 20.4 | 17.2 | 14.1 | +| | n260 | 24.4 | 21.2 | 18.2 | +| | n261 | 30.6 | 27.5 | 24.4 | + +Note: For $\sum \text{MBp}$ from TS 38.101-2 [16] Table 6.2.1.3-4 allow up to 0.75 dB in Rel-15. + +**Table D.3.2.2-2: Predicted $\text{SNR}_{\text{BB}}$ upper bound values for Indirect far field (IFF) with 30cm QZ, PC3, 100MHz CHBW, modulation up to 64 QAM when no fading conditions apply** + +| | Operating Band | Maximum $\text{SNR}_{\text{BB}}$ (dB) | | | +|---------------------------------|----------------|---------------------------------------|--------------|--------------| +| | | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| Multi-band UE (Note) | n257 | [28.7] | [25.5] | [22.5] | +| | n258 | [28.7] | [25.5] | [22.5] | +| | n259 | [18.4] | [15.2] | [12.1] | +| | n260 | [22.5] | [19.3] | [16.3] | +| | n261 | [28.7] | [25.5] | [22.5] | + +Note: For $\sum \text{MBp}$ from TS 38.101-2 [16] Table 6.2.1.3-4 allow up to 0.75 dB in Rel-15. + +For mode2 (noise free) scenarios, the maximum baseband SNR that can be achieved by a test system is calculated in the spreadsheet “Mode2 100MHz”. For other channel bandwidths the respective $\text{N}_{\text{RB}}$ and $\text{EIS}_{\text{PC3, band}}$ are to be used. + +For the “Backoff from P1dB” a value of $-13$ dB has been applied which is valid for modulations up to 64QAM. The resulting values for $\text{SNR}_{\text{BB}}$ are given in D.3.2.2-3 for test cases without fading and without added noise. + +**Table D.3.2.2-3: Predicted SNRBB upper bound values for Indirect far field (IFF) with 30cm QZ, PC3, 100MHz CHBW, modulation up to 64 QAM when no fading conditions and no added noise apply** + +| | Operating Band | Maximum SNR BB (dB) | | | +|----------------------|----------------|--------------------------------|--------------|--------------| +| | | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| Multi-band UE (Note) | n257 | [35.56] | [32.56] | [29.56] | +| | n258 | [35.56] | [32.56] | [29.56] | +| | n259 | [25.36] | [22.36] | [19.36] | +| | n260 | [29.36] | [26.36] | [23.36] | +| | n261 | [35.56] | [32.56] | [29.56] | + +Note1: For $\sum$ MBp from TS 38.101-2 [16] Table 6.2.1.3-4 allow up to 0.75 dB in Rel-15. + +Note that these are UE baseband SNR values (SNRBB), so the Reference point figures used in TS 38.101-4 [19] will be 1 dB higher. + +**Table D.3.2.2-4: Predicted SNRBB upper bound values for Indirect far field (IFF) with 30cm QZ, PC3, 100MHz CHBW, modulation up to 256 QAM under fading conditions for DEMOD scenarios** + +| Operating Band / Frequency | Maximum testable SNR BB (dB) | | | +|----------------------------|-----------------------------------------|--------------|--------------| +| | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| n257 mid | 29.1 | 25.9 | 22.9 | +| n258 mid | 29.1 | 25.9 | 22.9 | +| n259 mid | 18.8 | 15.6 | 12.5 | +| n260 mid | 22.9 | 19.7 | 16.6 | +| n261 mid | 29.1 | 25.9 | 22.9 | + +**Table D.3.2.2-5: Predicted SNRBB upper bound values for Indirect far field (IFF) with 30cm QZ, PC1, 100MHz CHBW, modulation up to 256 QAM under fading conditions for DEMOD scenarios** + +| Operating Band / Frequency | Maximum testable SNR BB (dB) | | | +|----------------------------|-----------------------------------------|--------------|--------------| +| | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| n257 mid | 39.0 | 35.9 | 32.9 | +| n258 mid | 39.0 | 35.9 | 32.9 | +| n259 mid | TBD | TBD | TBD | +| n260 mid | 32.4 | 29.3 | 26.3 | +| n261 mid | 39.0 | 35.9 | 32.9 | + +**Table D.3.2.2-6: Predicted SNRBB upper bound values for Indirect far field (IFF) with 30cm QZ, PC3, 100MHz CHBW, modulation up to 256 QAM under fading conditions for CSI scenarios** + +| Operating Band / Frequency | Maximum testable SNR BB (dB) | | | +|----------------------------|-----------------------------------------|--------------|--------------| +| | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| n257 mid | 26.3 | 23.2 | 20.1 | +| n258 mid | 26.3 | 23.2 | 20.1 | +| n259 mid | 16.0 | 12.8 | 9.6 | +| n260 mid | 20.1 | 16.9 | 13.8 | +| n261 mid | 26.3 | 23.2 | 20.1 | + +**Table D.3.2.2-7: Predicted SNRBB upper bound values for Indirect far field (IFF) with 30cm QZ, PC3, 100MHz CHBW, modulation up to 256 QAM with no fading conditions for CSI scenarios** + +| Operating Band / Frequency | Maximum testable SNR BB (dB) | | | +|----------------------------|-----------------------------------------|--------------|--------------| +| | CHBW 50 MHz | CHBW 100 MHz | CHBW 200 MHz | +| n257 mid | 28.7 | 25.5 | 22.5 | +| n258 mid | 28.7 | 25.5 | 22.5 | +| n259 mid | 18.4 | 15.2 | 12.1 | +| n260 mid | 22.5 | 19.3 | 16.3 | +| n261 mid | 28.7 | 25.5 | 22.5 | + +An example of SNR calculation for IFF method is provided in “38.521-4 Spreadsheet - Demod SNR range calculator.zip” file attached to the TR. + +## D.4 Simulation results + +During the MU discussions to determine the maximum testable SNR for IFF setup with PC3 30cm QZ, it was found that using a conservative “backoff from P1 dB” value (where signal backoff and fading crest factor were considerably independently), caused most of the RAN4 defined test points to be untestable. + +By simulating the CCDF of RAN4 defined signal waveform and faded signal waveform, it was concluded to consider the faded signal crest factor instead of independently adding signal crest factor and fading crest factor. + +Figure D.4-1 below captures the CCDF of test 2-6 from table 7.2.2.2.1\_1.4-2 of TS 38.521-4 which was considered as the scenario with highest faded signal crest factor for 64QAM. + +For the simulation, actual signal corresponding to the RAN4 defined scenarios was generated and the appropriate fading profile as specified in the requirement was applied. Simulations were run for $4 \cdot 10^8$ samples. + +In figure D.4-1, Hx denotes the actual RAN4 signal per Rx after fading is applied. The value in dB against each legend correspond to the computed PAPR for that signal and faded signal + +![Figure D.4-1: CCDF of Test2-6 signal power and signal power after fading. The plot shows the Complementary Cumulative Distribution Function (CCDF) on a logarithmic y-axis (from 10^-9 to 10^0) versus Power (dB) on a linear x-axis (from -40 to 20). Four curves are plotted: Signal Tx0 (blue), Signal Tx1 (red), Hx Rx0 (cyan), and Hx Rx1 (black). The curves show that the signal power after fading (Hx) is significantly lower than the original signal power (Tx).](ff4ed9c9daa873625e772a2f5e9a6a6e_img.jpg) + +The figure is a CCDF plot titled "100MHz, 120kHz, 2x2 TDLA30-75 ULA Low, MCS17, Rank2, NumSamples = 398010501". The y-axis is labeled "CCDF" and ranges from $10^{-9}$ to $10^0$ on a logarithmic scale. The x-axis is labeled "Power (dB)" and ranges from -40 to 20 on a linear scale. There are four data series: + + +- Signal Tx0** (blue line): Represents the transmit signal power for Tx0. It starts at approximately 13.77 dB. +- Signal Tx1** (red line): Represents the transmit signal power for Tx1. It starts at approximately 13.23 dB. +- Hx Rx0** (cyan line): Represents the received signal power for Rx0 after fading. It starts at approximately 17.71 dB. +- Hx Rx1** (black line): Represents the received signal power for Rx1 after fading. It starts at approximately 17.01 dB. + + The plot shows that the signal power after fading (Hx) is significantly lower than the original signal power (Tx). The curves for Hx Rx0 and Hx Rx1 are very close to each other, while the curves for Signal Tx0 and Signal Tx1 are also very close to each other. The Hx curves drop off more sharply than the Tx curves as power increases. + +Figure D.4-1: CCDF of Test2-6 signal power and signal power after fading. The plot shows the Complementary Cumulative Distribution Function (CCDF) on a logarithmic y-axis (from 10^-9 to 10^0) versus Power (dB) on a linear x-axis (from -40 to 20). Four curves are plotted: Signal Tx0 (blue), Signal Tx1 (red), Hx Rx0 (cyan), and Hx Rx1 (black). The curves show that the signal power after fading (Hx) is significantly lower than the original signal power (Tx). + +**Figure D.4-1: CCDF of Test2-6 signal power and signal power after fading** + +Considering the max PAPR value of the faded signal allowed some more test points to be testable. In order to make more test points testable, higher probability of saturation of faded signal needed to be considered. + +In order to determine how much faded signal clipping probability did not adversely impact the UE's capability to successfully decode the PDSCH signal, simulations were run for most of the 64QAM and 256QAM test points defined in TS 38.521-4. + +Two companies participated in providing the simulation results. Below tables and figures capture the simulation results from the 2 companies that was used to determine the faded signal clipping probability to be used for the "backoff from P1 dB" term. + +Table D.4-1: Faded signal PAPR at different clipping probability for all test points defined in TS 38.521-4 (Company 1) + +| | Test# | Fading | MCS | Test SNR | numSamples | Mean Signal Pwr (Rx0/Rx1) | Mean Faded signal Pwr (Rx0/Rx1) | Signal PAPR (Rx0/Rx1) | Faded Signal PAPR (Rx0/Rx1) | Faded Signal PAPR at 1e-6 clipping prob | Faded Signal PAPR at 1e-4 clipping prob | Faded Signal PAPR at 1e-3 clipping prob | +|----|-----------------|----------------------|--------|------------------------|------------|------------------------------------------------------|---------------------------------|-----------------------|-----------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------| +| 1 | 1-1 | TDLC60-300 Low | QPSK | 1.4 | 1.23E+08 | -4.44 -4.45 | -1.39 -1.37 | 12.89 13.08 | 16.87 17.40 | | | | +| 2 | 1-2 | TDLA30-300 Low | 16QAM | 3.6 | | | | | leverage from 2-2 | | | | +| 3 | 1-3 | TDLA30-300 XPL Med | 64QAM | 14.2 | 1.23E+08 | -4.44 -4.45 | -1.52 -1.39 | 13.04 13.15 | 17.78 18.20 | 15.72 16.21 | | 8.24 8.4 | +| 4 | 1-4 | TDLD30-75 Low | 256QAM | 21.9 | 9.22E+07 | -4.58 -4.59 | -1.72 -1.60 | 13.31 13.29 | 17.0 16.24 | 15.08 14.82 | 12.62 12.5 | 10.96 10.84 | +| 5 | 2-1 | TDLA30-75 Low | QPSK | 5.8 | | | | | leverage from 2-6 | | | | +| 6 | 2-2 | TDLA30-300 Low | 16QAM | 16 | 1.23E+08 | -4.44 -4.45 | -1.5 -1.43 | 12.95 12.96 | 16.37 16.52 | | | | +| 7 | 2-6 | TDLA30-75 Low | 64QAM | 20.3 | 3.98E+08 | -4.44 | -1.54 | 13.77 13.23 | 17.77 17.01 | 14.73 14.54 | | | +| 8 | 3-1 | TDLA30-75 ULA Medium | 16QAM | 20.7 | 1.23E+08 | -4.44 -4.45 | -1.71 -1.78 | 12.95 12.96 | 16.03 16.48 | 14.19 14.55 | | | +| 9 | 8.2.2.2.2 | TDLA30-35 ULA High | 256QAM | 6/7, 12/13, 7/8, 20/21 | 9.22E+07 | -4.59 -4.59 | -1.70 -1.90 | 12.86 12.82 | 19.24 20.72 | 17.69 19.05 | 14.74 15.36 | 12.64 12.96 | +| 10 | 8.3.2.2.1 | TDLA30-35 Low | 16QAM | | 1.23E+08 | -4.45 -4.45 | -1.86 -1.96 | 12.76 12.85 | 17.80 17.19 | 15.35 15.45 | | | +| 11 | 8.4.2.2 Test1/2 | TDLA30-35 Low | 64QAM | 0,16 | 1.23E+08 | -4.45 -4.45 | -1.86 -2.0 | 13.46 12.90 | 15.98 15.86 | | | | +| 12 | 8.4.2.2 Test3 | TDLA30-35 XP High | 64QAM | 16 | 1.23E+08 | -4.45 -4.45 | -1.80 -2.07 | 13.25 13.27 | 16.99 18.05 | 15.57 15.54 | | | +| 13 | 8.4.2.2 Test3 | TDLA30-35 XP High | 64QAM | 16 | 1.23E+08 | -4.45 -4.45 | -1.86 -2.08 | 13.46 12.90 | 15.42 15.77 | | | | +| 14 | 8.2.2.2.1.1 | AWGN only | 64QAM | 8/9, 14/15 | | Signal PAPR already available as part of other cases | | | | | | | + +**Table D.4-2: Throughput values for key test points at different faded signal clipping probabilities (Company 1)** + +| Test# | Test SNR | Scenario | 1E-06 | 1E-04 | 1E-03 | 1E-02 | +|-----------|----------|--------------|-------|-------|-------|-------| +| 1-3 | 14.2 | 64QAM Demod | 100% | 100% | 100% | 100% | +| 2-6 | 20.3 | 64QAM Demod | 100% | 100% | 100% | 100% | +| 1-4 | 22 | 256QAM Demod | 100% | 100% | 100% | 83% | +| 8.2.2.2.2 | 13 | 64QAM CSI | 100% | 100% | 100% | 98% | +| 8.2.2.2.2 | 21 | 256QAM CSI | 100% | 100% | 97% | 85% | + +Note: All throughput values normalized to the no faded signal clipping case + +**Table D.4-3: Faded signal PAPR at different clipping probability for 256QAM test 1-4 (Company 2)** + +| Clipping probability | PAPR (dB) | +|----------------------|-----------| +| 1e-6 | 15.43 | +| 1e-5 | 14.43 | +| 1e-4 | 13.18 | +| 1e-3 | 11.69 | +| 1e-2 | 9.79 | +| 1e-1 | 7.11 | + +![Line graph showing PDsch Throughput (Mbps) vs SNR (dB) per UE for 64QAM test 2-6. The graph compares 'No clipping' with various clipping levels (12.5+16.49dB, 12.5+15.49dB, 12.5+13.99dB, 12.5+12.25dB, 12.5+10.11dB, 12.5+7.23dB per branch). Throughput peaks around 20-22 dB SNR and then decreases, with higher clipping thresholds maintaining higher throughput at high SNR.](e985b32357f2d9ebae5f53130132dd37_img.jpg) + +**TDD SCS=120kHz, 100MHz, MCS17, Rank 2, 2x2 TDLA30-75** + +| SNR (dB) per UE | No clipping (Mbps) | Clip at 12.5+16.49dB (Mbps) | Clip at 12.5+15.49dB (Mbps) | Clip at 12.5+13.99dB (Mbps) | Clip at 12.5+12.25dB (Mbps) | Clip at 12.5+10.11dB (Mbps) | Clip at 12.5+7.23dB (Mbps) | +|-----------------|--------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|----------------------------| +| 10 | 120 | 120 | 120 | 120 | 120 | 120 | 120 | +| 12 | 135 | 135 | 135 | 135 | 135 | 135 | 135 | +| 14 | 155 | 155 | 155 | 155 | 155 | 155 | 155 | +| 16 | 205 | 205 | 205 | 205 | 205 | 205 | 205 | +| 18 | 255 | 255 | 255 | 255 | 255 | 255 | 255 | +| 20 | 270 | 270 | 270 | 270 | 270 | 270 | 270 | +| 22 | 275 | 275 | 275 | 275 | 275 | 275 | 275 | +| 24 | 275 | 275 | 275 | 275 | 275 | 275 | 275 | +| 26 | 275 | 275 | 275 | 275 | 275 | 275 | 275 | +| 28 | 275 | 275 | 275 | 275 | 275 | 275 | 275 | +| 30 | 275 | 275 | 275 | 275 | 275 | 275 | 275 | + +Line graph showing PDsch Throughput (Mbps) vs SNR (dB) per UE for 64QAM test 2-6. The graph compares 'No clipping' with various clipping levels (12.5+16.49dB, 12.5+15.49dB, 12.5+13.99dB, 12.5+12.25dB, 12.5+10.11dB, 12.5+7.23dB per branch). Throughput peaks around 20-22 dB SNR and then decreases, with higher clipping thresholds maintaining higher throughput at high SNR. + +**Figure D.4-2: Throughput vs SNR for 64QAM test 2-6 at different faded signal clipping probabilities (Company 2)** + +![Figure D.4-3: Throughput vs SNR for 256QAM test at different faded signal clipping probabilities (Company 2). The graph shows PDSCH Tput (Mbps) on the y-axis (40 to 140) versus SNR (dB) per UE on the x-axis (10 to 30). The title is 'TDD SCS=120kHz, 50MHz, MCS20, Rank 1, 2x2 TDL30-75'. The legend indicates seven scenarios: 'No clipping' (blue circles), 'Clip at 13+15.43dB (per branch)' (orange triangles), 'Clip at 13+14.43dB (per branch)' (yellow inverted triangles), 'Clip at 13+13.18dB (per branch)' (purple asterisks), 'Clip at 13+11.69dB (per branch)' (green diamonds), 'Clip at 13+9.79dB (per branch)' (light blue plus signs), and 'Clip at 13+7.11dB (per branch)' (red stars). The 'No clipping' scenario reaches a peak throughput of approximately 138 Mbps at 20 dB SNR and remains constant. As the clipping threshold decreases, the peak throughput drops and the performance degrades at higher SNR values. A horizontal line is drawn at 97 Mbps.](0087be03fe64bdec0075ae6ebde7bb34_img.jpg) + +| SNR (dB) per UE | No clipping (Mbps) | Clip at 13+15.43dB (Mbps) | Clip at 13+14.43dB (Mbps) | Clip at 13+13.18dB (Mbps) | Clip at 13+11.69dB (Mbps) | Clip at 13+9.79dB (Mbps) | Clip at 13+7.11dB (Mbps) | +|-----------------|--------------------|---------------------------|---------------------------|---------------------------|---------------------------|--------------------------|--------------------------| +| 10 | 60 | 60 | 60 | 60 | 60 | 60 | 60 | +| 12 | 65 | 65 | 65 | 65 | 65 | 65 | 65 | +| 14 | 68 | 68 | 68 | 68 | 68 | 68 | 68 | +| 16 | 93 | 93 | 93 | 93 | 93 | 93 | 93 | +| 18 | 132 | 132 | 132 | 132 | 132 | 132 | 132 | +| 20 | 138 | 138 | 138 | 138 | 138 | 138 | 138 | +| 22 | 138 | 138 | 138 | 138 | 128 | 118 | 118 | +| 24 | 138 | 138 | 138 | 128 | 82 | 78 | 78 | +| 26 | 138 | 138 | 138 | 82 | 65 | 62 | 62 | +| 28 | 138 | 138 | 102 | 65 | 65 | 62 | 58 | +| 30 | 138 | 138 | 68 | 65 | 60 | 52 | 42 | + +Figure D.4-3: Throughput vs SNR for 256QAM test at different faded signal clipping probabilities (Company 2). The graph shows PDSCH Tput (Mbps) on the y-axis (40 to 140) versus SNR (dB) per UE on the x-axis (10 to 30). The title is 'TDD SCS=120kHz, 50MHz, MCS20, Rank 1, 2x2 TDL30-75'. The legend indicates seven scenarios: 'No clipping' (blue circles), 'Clip at 13+15.43dB (per branch)' (orange triangles), 'Clip at 13+14.43dB (per branch)' (yellow inverted triangles), 'Clip at 13+13.18dB (per branch)' (purple asterisks), 'Clip at 13+11.69dB (per branch)' (green diamonds), 'Clip at 13+9.79dB (per branch)' (light blue plus signs), and 'Clip at 13+7.11dB (per branch)' (red stars). The 'No clipping' scenario reaches a peak throughput of approximately 138 Mbps at 20 dB SNR and remains constant. As the clipping threshold decreases, the peak throughput drops and the performance degrades at higher SNR values. A horizontal line is drawn at 97 Mbps. + +Figure D.4-3: Throughput vs SNR for 256QAM test at different faded signal clipping probabilities (Company 2) + +Based on the above simulation results, + +For 64QAM scenarios (both Demod and CSI), fading backoff margin of 11.08 dB corresponding to the 1e-3 faded signal clipping probability was considered. + +For 256QAM Demod, fading backoff margin of 12.62 dB corresponding to 1e-3 fading signal clipping probability was considered. + +For 256QAM CSI scenarios, fading backoff margin of 15.36 dB corresponding to 1e-4 fading signal clipping probability was considered. + +## Annex E: Acceptable uncertainty of test system for test cases defined in TS 38.533 for radiative testing + +This annex contains suggested uncertainties for each test case or MU quantity in TS 38.533 [10]. + +--- + +## E.1 Uncertainty budget calculation principle + +### E.1.1 Uncertainty budget calculation principle for DFF + +The uncertainty tables cover the actual measurement using the DUT. In some cases, uncertainty may also arise from a calibration or alignment process before the measurements. + +When a calibration process is used before the measurements, the uncertainty tables should be presented with two stages: + +- Stage 1: the calibration of the absolute level of the DUT measurement results is performed by means of using a calibration antenna whose absolute gain is known at the frequencies of measurement +- Stage 2: the actual measurement with the DUT as either the transmitter or receiver is performed. + +The MU budget should comprise of a minimum 5 headings: + +- 1) The uncertainty source, +- 2) Uncertainty value, +- 3) Distribution of the probability, +- 4) Divisor based on distribution shape, +- 5) Calculated standard uncertainty (based on uncertainty value and divisor). + +### E.1.2 Uncertainty budget calculation principle for IFF + +The same as defined in E.1.1. + +--- + +## E.2 Measurement error contribution descriptions + +### E.2.1 Measurement error contribution descriptions for DFF + +All the measurement error contributions defined in Section B.2.1, with the following additions. + +#### E.2.1.1 gNB emulator SNR uncertainty + +See D.2.1.1. + +#### E.2.1.2 gNB emulator Downlink EVM + +See D.2.1.2. + +#### E.2.1.3 gNB emulator fading model impairments + +See D.2.1.3. + +## E.2.2 Measurement error contribution descriptions for IFF + +All the measurement error contributions defined in Section B.2.2, with the following additions. + +### E.2.2.1 gNB emulator SNR uncertainty + +See D.2.1.1. + +### E.2.2.2 gNB emulator Downlink EVM + +See D.2.1.2. + +### E.2.2.3 gNB emulator fading model impairments + +See D.2.1.3. + +--- + +## E.3 Uncertainty assessment for RRM MU quantities. + +RRM measurement uncertainty analysis shall define the values for the following MU quantities: + +- DL AWGN absolute power or wanted DL signal absolute power +- DL applied SNR +- DL Fading profile uncertainty +- DL AWGN and signal flatness +- UL absolute power measurement +- UL relative power measurement +- UL signal transmit timing relative to DL +- Relative transmit timing accuracy during UE timing adjustment + +### E.3.1 Uncertainty assessment for DL AWGN absolute power or wanted DL signal absolute power + +Table E.3.1-1 summarizes the MU threshold for DL AWGN absolute power for RRM FR2 test cases. The origin MU values for different test setups with varies parameters can be found in following subclauses. + +**Table E.3.1-1: MU threshold for DL AWGN absolute power for RRM FR2** + +| Power Class | Frequency | MBW | Power | Threshold MU value (NOTE 1) | +|-------------|-----------------------------------|-------------------|--------------------------------|-----------------------------| +| PC3 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | As configured in the test case | 5.65 dB 2 | +| | 32.125GHz $< f \leq 40.8$ GHz | | | 5.65 dB 2 | +| PC1 | 23.45GHz $\leq f \leq 32.125$ GHz | BW $\leq 400$ MHz | As configured in the test case | FFS | +| | 32.125GHz $< f \leq 40.8$ GHz | | | FFS | + +NOTE 1: Total Expanded MU for IFF for Quiet Zone size $\leq 30$ cm in Table E.3.1.3-2 for PC3 UEs and Table FFS for PC1 UEs + +NOTE 2: If the TT analysis for a specific test case based on this MU value results in an unsolvable conflict, making the test case untestable, even after the alternative solutions listed in clause A.4 have been considered for the test case in TS 38.133 [6] Annex A, the TT analysis shall be repeated using a lower MU value, taking into account the lower values defined in this clause. The test case will be applicable for the subset of the test systems meeting this reduced MU Threshold. + +The types of test setup are defined in clause 7.1.3.2 of TS 38.508-1 [18] + +### E.3.1.1 Uncertainty budget format and assessment for DFF test setup + +The uncertainty contributions that may impact the overall MU value are listed in Table E.3.1.1-1. + +**Table E.3.1.1-1: Uncertainty contributions for DL AWGN absolute power or wanted DL signal absolute power** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of Quiet Zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.1.5 | +| 6 | gNB emulator uncertainty | B.2.1.17 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 14 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 15 | Mismatch | B.2.1.4 | +| 16 | Amplifier Uncertainties | B.2.1.8 | +| 17 | Misalignment of positioning System | B.2.1.13 | +| 18 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 19 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 21 | Phase centre offset of calibration antenna | B.2.1.18 | +| 22 | Quality of quiet zone for calibration process | B.2.1.19 | +| 23 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 24 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 25 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 26 | Systematic error related to beam peak search | B.2.1.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment is applicable for 1AoA and 2AoA test cases +- The uncertainty assessment is provided in Table E.3.1.1-2. + +**Table E.3.1.1-2: Uncertainty assessment for DL AWGN absolute power or wanted DL signal absolute power (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.15 | Rectangular | 1.73 | 0.08 | | | | | +| 3 | Quality of Quiet Zone (NOTE 4) | 1.2 | Actual | 1.00 | 1.2 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.06 | U-shaped | 1.41 | 0.043 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 15 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 16 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 17 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | 0.37 | | | | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 21 | Phase centre offset of calibration antenna | 0.47 | Rectangular | 1.73 | 0.27 | | | | | +| 22 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 24 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 25 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 2) | | | | | Value | | | | | +| 26 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| DL AWGN absolute power or wanted DL signal absolute power expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.65 | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The analysis was done only for the case of operating in-band, non-CA. | +| NOTE 2: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 3: | Applies to the system which has a structure of mechanical feed antenna positioning. | +| NOTE 4: | Value based on procedure defined in Annex D.2 of TR 38.810 [13] for Quiet Zone size less or equal to 30 cm. | +| NOTE 5: | The values in this table have been derived for DL powers above and equal to REFSENS. The values might need to be revisited for power levels below REFSENS | + +### E.3.1.2 Uncertainty budget format and assessment for Simplified DFF test setup + +[FFS] + +### E.3.1.3 Uncertainty budget format and assessment for IFF test setup + +The uncertainty contributions that may impact the overall MU value are listed in Table E.3.1.3-1. + +**Table E.3.1.3-1: Uncertainty contributions for DL AWGN absolute power or wanted DL signal absolute power** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | gNB emulator uncertainty | B.2.2.17 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 14 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 15 | Mismatch | B.2.2.4 | +| 16 | Amplifier Uncertainties | B.2.2.8 | +| 17 | Misalignment of positioning System | B.2.2.13 | +| 18 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 19 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 21 | Phase centre offset of calibration antenna | B.2.2.18 | +| 22 | Quality of quiet zone for calibration process | B.2.2.19 | +| 23 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 24 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 25 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 26 | Systematic error related to beam peak search | B.2.2.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment is applicable for 1AoA test cases- The uncertainty assessment is provided in Table E.3.1.3-2. + +**Table E.3.1.3-2: Uncertainty assessment for DL AWGN absolute power or wanted DL signal absolute power (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 15 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 16 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 17 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | 0.37 | | | | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 21 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 24 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 25 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 2) | | | | | Value | | | | | +| 26 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| DL AWGN absolute power expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.19 | | | | | + +- | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: The analysis was done only for the case of operating in-band, non-CA.
NOTE 2: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 3: Applies to the system which has a structure of mechanical feed antenna positioning.
NOTE 4: Value based on procedure defined in Annex D.2 of TR 38.810 [13] for Quiet Zone size less or equal to 30 cm.
NOTE 5: The values in this table have been derived for DL powers above and equal to REFSENS.
The values might need to be revisited for power levels below REFSENS | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table E.3.1.3-3: Uncertainty assessment for DL AWGN absolute power or wanted DL signal absolute power (f=23.45GHz, 32.125GHz, Quiet Zone size $\leq 30$ cm), PC1** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.01 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | [2.1] | Normal | 2.00 | [1.05] | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.35 | Rectangular | 1.73 | 0.20 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 15 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 16 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 17 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 21 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 24 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 25 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 2) | | | | | Value | | | | | +| 26 | Systematic error related to beam peak search | | | | 0.7 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| DL AWGN absolute power expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | [5.58] | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The analysis was done only for the case of operating in-band, non-CA. | +| NOTE 2: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 3: | Applies to the system which has a structure of mechanical feed antenna positioning. | +| NOTE 4: | Value based on procedure defined in Annex D.2 of TR 38.810 [13] for Quiet Zone size less or equal to 30 cm. | +| NOTE 5: | The values in this table have been derived for DL powers above and equal to REFSSENS. The values might need to be revisited for power levels below REFSSENS | + +### E.3.1.4 Uncertainty budget format and assessment for Enhanced IFF test setup + +The uncertainty contributions that may impact the overall MU value are listed in Table E.3.1.4-1. + +**Table E.3.1.4-1: Uncertainty contributions for DL AWGN absolute power or wanted DL signal absolute power** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-----------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 to 14 | See 1-14 of Table E.3.1.3-1 | N/A | +| Stage 1: Calibration measurement | | | +| 15 to 25 | See 15-25 of Table E.3.1.3-1 | N/A | +| Systematic uncertainties | | | +| 26 | See 26 of Table E.3.1.3-1 | N/A | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq [30 \text{ cm}]$ , $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment is applicable for 1AoA and 2AoA test cases +- The uncertainty assessment is provided in Table E.3.1.4-2. + +**Table E.3.1.4-2: Uncertainty assessment for fDL AWGN absolute power or wanted DL signal absolute power (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm)** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.7 | Actual | 1.00 | 0.7 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | 0.37 | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 2) | | | | | Value | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| DL AWGN absolute power expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | 5.25 | | | | | + +- | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: The analysis was done only for the case of operating in-band, non-CA.
NOTE 2: In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors.
NOTE 3: Applies to the system which has a structure of mechanical feed antenna positioning.
NOTE 4: Value based on procedure defined in Annex M of TR 38.521-2 [7] for Quiet Zone size less or equal to 30 cm.
NOTE 5: The values in this table have been derived for DL powers above and equal to REFSENS.
The values might need to be revisited for power levels below REFSENS | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table E.3.1.4-3: Uncertainty assessment for fDL AWGN absolute power or wanted DL signal absolute power (f=23.45GHz, 32.125GHz, Quiet Zone size $\leq 30$ cm) for PC1** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.02 | Normal | 2.00 | 0.02 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 4) | 0.7 | Actual | 1.00 | 0.7 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | 1.45 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | [2.1] | Normal | 2.00 | [1.05] | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Multiple measurement antenna uncertainty (NOTE 3) | 0.15 | Actual | 1.00 | 0.15 | | | | | +| 14 | DUT repositioning | 0.35 | Rectangular | 1.73 | 0.20 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 17 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 18 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 20 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | 0.75 | | | | | +| 21 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 22 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 24 | Quality of quiet zone for calibration process (NOTE 4) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 25 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 26 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 27 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 2) | | | | | Value | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.7 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| DL AWGN absolute power expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | [5.65] | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | The analysis was done only for the case of operating in-band, non-CA. | +| NOTE 2: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 3: | Applies to the system which has a structure of mechanical feed antenna positioning. | +| NOTE 4: | Value based on procedure defined in Annex M of TR 38.521-2 [7] for Quiet Zone size less or equal to 30 cm. | +| NOTE 5: | The values in this table have been derived for DL powers above and equal to REFSSENS. The values might need to be revisited for power levels below REFSSENS | + +### E.3.1.5 Uncertainty budget format and assessment for IFF+DFF Hybrid test setup + +For DFF probe, Uncertainty shall be evaluated using the Uncertainty budget format as specified in E.3.1.1. + +For IFF probe, Uncertainty shall be evaluated using the Uncertainty budget format as specified in E.3.1.3. + +The overall uncertainty of the IFF+DFF Hybrid test set up shall be calculated with the max(Total DFF probe MU, Total IFF probe MU). + +## E.3.2 Uncertainty assessment for DL applied SNR + +## E.3.3 Uncertainty assessment for DL Fading profile uncertainty + +## E.3.4 Uncertainty assessment for DL AWGN and signal flatness + +## E.3.5 Uncertainty assessment for UL absolute power measurement + +**Editor's Note :** Applicability of MU in this section for 2AoA Test Cases needs to be reassessed once 2AoA Test Cases requiring UL power measurement is defined. + +Following tables summarize the MU threshold for EIRP UL absolute power measurement in FR2 RRM test cases. The origin MU values for different test setups with varies parameters can be found in following clauses. + +**Table B.3.5-1: MU threshold for EIRP UL absolute power measurement** + +TBD + +### E.3.5.1 Uncertainty budget format and assessment for DFF + +**Editor's Note :** Applicability of MU in this section for 2AoA Test Cases needs to be reassessed once 2AoA Test Cases requiring UL power measurement is defined. + +The uncertainty contributions that may impact the overall MU value are listed in Table B.3.5.1-1. + +**Table B.3.5.1-1: Uncertainty contributions for EIRP UL absolute power measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.1.1 | +| 2 | Measure distance uncertainty | B.2.1.2 | +| 3 | Quality of quiet zone | B.2.1.3 | +| 4 | Mismatch | B.2.1.4 | +| 5 | Standing Wave Between the DUT and measurement antenna | B.2.1.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.1.6 | +| 7 | Phase curvature | B.2.1.7 | +| 8 | Amplifier uncertainties | B.2.1.8 | +| 9 | Random uncertainty | B.2.1.9 | +| 10 | Influence of the XPD | B.2.1.10 | +| 11 | Insertion Loss Variation | B.2.1.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.1.12 | +| 13 | Influence of beam peak search grid | B.2.1.23 | +| 14 | Multiple measurement antenna uncertainty | B.2.1.25 | +| 15 | DUT repositioning | B.2.1.26 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.1.4 | +| 17 | Amplifier uncertainties | B.2.1.8 | +| 18 | Misalignment of positioning System | B.2.1.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.1.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.1.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.1.16 | +| 22 | Phase centre offset of calibration antenna | B.2.1.18 | +| 23 | Quality of quiet zone for calibration process | B.2.1.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.1.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.1.21 | +| 26 | Insertion Loss Variation | B.2.1.11 | +| Systematic uncertainties | | | +| 27 | Influence of noise | B.2.1.27 | +| 28 | Systematic error related to beam peak search | B.2.1.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment is applicable for 1AoA and 2AoA test cases +- The uncertainty assessment is provided in Table B.3.5.1-2. + +**Table B.3.5.3-2: Uncertainty assessment for EIRP measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.15 | Rectangular | 1.73 | 0.08 | | | | | +| 3 | Quality of quiet zone (NOTE 1) | 1.2 | Actual | 1.00 | 1.2 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing Wave Between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.06 | U-shaped | 1.41 | 0.043 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 4) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | 0.37 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.47 | Rectangular | 1.73 | 0.27 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 3) | | | | | Value | | | | | +| 27 | Influence of noise | | | | TBD | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | +| NOTE 2: | The assessment assumes minimum output power level. | +| NOTE 3: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 4: | Applies to the system which has a structure of mechanical feed antenna positioning. | + +### E.3.5.2 TBD + +### E.3.5.3 Uncertainty budget format and assessment for IFF + +**Editor's Note :** Applicability of MU in this section for 2AoA Test Cases needs to be reassessed once 2AoA Test Cases requiring UL power measurement is defined. + +The uncertainty contributions that may impact the overall MU value are listed in Table B.3.5.3-1. + +**Table E.3.5.3-1: Uncertainty contributions for EIRP UL absolute power measurement** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|-------------------------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Positioning misalignment | B.2.2.1 | +| 2 | Measure distance uncertainty | B.2.2.2 | +| 3 | Quality of Quiet Zone | B.2.2.3 | +| 4 | Mismatch | B.2.2.4 | +| 5 | Standing wave between the DUT and measurement antenna | B.2.2.5 | +| 6 | Uncertainty of the RF power measurement equipment | B.2.2.6 | +| 7 | Phase curvature | B.2.2.7 | +| 8 | Amplifier uncertainties | B.2.2.8 | +| 9 | Random uncertainty | B.2.2.9 | +| 10 | Influence of the XPD | B.2.2.10 | +| 11 | Insertion Loss Variation | B.2.2.11 | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | B.2.2.12 | +| 13 | Influence of beam peak search grid | B.2.2.23 | +| 14 | Multiple measurement antenna uncertainty | B.2.2.25 | +| 15 | DUT repositioning | B.2.2.26 | +| Stage 1: Calibration measurement | | | +| 16 | Mismatch | B.2.2.4 | +| 17 | Amplifier Uncertainties | B.2.2.8 | +| 18 | Misalignment of positioning System | B.2.2.13 | +| 19 | Uncertainty of the Network Analyzer | B.2.2.14 | +| 20 | Uncertainty of the absolute gain of the calibration antenna | B.2.2.15 | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | B.2.2.16 | +| 22 | Phase centre offset of calibration antenna | B.2.2.18 | +| 23 | Quality of quiet zone for calibration process | B.2.2.19 | +| 24 | Standing wave between reference calibration antenna and measurement antenna | B.2.2.20 | +| 25 | Influence of the calibration antenna feed cable | B.2.2.21 | +| 26 | Insertion Loss Variation | B.2.2.11 | +| Systematic uncertainties | | | +| 27 | Influence of noise | B.2.2.27 | +| 28 | Systematic error related to beam peak search | B.2.2.28 | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment is applicable for 1AoA test cases + - The uncertainty assessment for EIRP is provided in Table B.3.5.3-2 for PC3 UEs + +**Table B.3.5.3-2: Uncertainty assessment for EIRP UL absolute power measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.6 | Actual | 1.00 | 0.6 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 4) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | 0.37 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 3) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | TBD | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | +| NOTE 2: | The assessment assumes minimum output power level. | +| NOTE 3: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 4: | Applies to the system which has a structure of mechanical feed antenna positioning. | + +### E.3.5.4 Uncertainty budget format and assessment for Enhanced IFF test setup + +Editor's Note : Applicability of MU in this section for 2AoA Test Cases needs to be reassessed once 2AoA Test Cases requiring UL power measurement is defined. + +The uncertainty contributions that may impact the overall MU value are listed in Table E.3.5.4-1. + +**Table E.3.5.4-1: Uncertainty contributions for EIRP UL absolute power measurement** + +| UID | Description of uncertainty contribution | Details in annex | +|-----------------------------------------|-----------------------------------------|------------------| +| Stage 2: DUT measurement | | | +| 1 to 15 | See 1-15 of Table E.3.5.3-1 | N/A | +| Stage 1: Calibration measurement | | | +| 16 to 26 | See 16-26 of Table E.3.5.3-1 | N/A | +| Systematic uncertainties | | | +| 27 to 28 | See 27-28 of Table E.3.5.3-1 | N/A | + +The uncertainty assessment tables are organized as follows: + +- For the purpose of uncertainty assessment, the radiating antenna aperture of the DUT is denoted as D +- The uncertainty assessment has been derived for the case of Quiet Zone size $\leq 30$ cm, $f = \{23.45\text{GHz}, 32.125\text{GHz}, 40.8\text{GHz}\}$ . +- The uncertainty assessment is applicable for 1AoA and 2AoA test cases +- The uncertainty assessment is provided in Table E.3.5.4-2. + +**Table B.3.5.4-2: Uncertainty assessment for EIRP UL absolute power measurement (f=23.45GHz, 32.125GHz, 40.8GHz, Quiet Zone size $\leq 30$ cm) for PC3 UEs and normal temperature condition** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.7 | Actual | 1.00 | 0.7 | | | | | +| 4 | Mismatch | 1.30 | Actual | 1.00 | 1.30 | | | | | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 6 | Uncertainty of the RF power measurement equipment (NOTE 2) | 2.50 | Normal | 2.00 | 1.25 | | | | | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 8 | Amplifier uncertainties | 2.10 | Normal | 2.00 | 1.05 | | | | | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | 0.25 | | | | | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | 0.00 | | | | | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | 0.00 | | | | | +| 13 | Influence of beam peak search grid | 0.00 | Actual | 1 | 0.00 | | | | | +| 14 | Multiple measurement antenna uncertainty (NOTE 4) | 0.15 | Actual | 1 | 0.15 | | | | | +| 15 | DUT repositioning | 0.08 | Rectangular | 1.73 | 0.05 | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | 0.00 | | | | | +| 19 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | 0.37 | | | | | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | 0.30 | | | | | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | 0.00 | | | | | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | 0.4 | | | | | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | 0.00 | | | | | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | 0.07 | | | | | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | 0.00 | | | | | +| Systematic uncertainties (NOTE 3) | | | | | Value | | | | | +| 27 | Influence of noise ( $23.45\text{GHz} \leq f \leq 32.125\text{GHz}$ ) | | | | TBD | | | | | +| 28 | Systematic error related to beam peak search | | | | 0.5 | | | | | +| Total measurement uncertainty | | | | | Value | | | | | +| EIRP Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | TBD | | | | | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Value based on procedure defined in clause D.2 of TR 38.810 for Quiet Zone size less or equal to 30 cm. | +| NOTE 2: | The assessment assumes minimum output power level. | +| NOTE 3: | In order to obtain the total measurement uncertainty, systematic uncertainties have to be added to the expanded root sum square of the standard deviations of the Stage 1 and Stage 2 contributors. | +| NOTE 4: | Applies to the system which has a structure of mechanical feed antenna positioning. | + +### E.3.5.5 Uncertainty budget format and assessment for IFF+DFF Hybrid test setup + +For DFF probe, Uncertainty shall be evaluated using the Uncertainty budget format as specified in E.3.5.1. + +For IFF probe, Uncertainty shall be evaluated using the Uncertainty budget format as specified in E.3.5.3. + +The overall uncertainty of the IFF+DFF Hybrid test set up shall be calculated with the max(Total DFF probe MU, Total IFF probe MU). + +### E.3.6 Uncertainty assessment for UL relative power measurement + +### E.3.7 Uncertainty assessment for UL signal transmit timing relative to DL + +### E.3.8 Uncertainty assessment for Relative transmit timing accuracy during UE timing adjustment + +--- + +## Annex F: Applicable MTSU for Different QZ/Device Sizes + +The applicability mapping between minimum QZ size, maximum device size and MTSU is outlined in Table F-1. The underlying assumptions for the mapping are as follows: + +- The maximum device size ranges/limits follow the currently defined quiet zone sizes, i.e., 20cm, 30cm, 40cm, and 55cm [7], [18] +- The applicable MTSU follows the max device size, e.g., a max device size of 30cm to 40cm yields an MTSU of MTSU40cm +- The applicable MTSU is the same regardless of whether a grey-box or black-box approach [7], [18] is selected to simplify the mapping and to prevent different test requirements for the same device depending on whether black or grey box is applied +- A maximum device size exceeding 55cm but with antenna separations of $\leq 55\text{cm}$ does not have an applicable MTSU given the lack of a larger QZ +- Devices with $>55\text{cm}$ maximum device size do not have an applicable MTSU given the lack of a larger QZ + +**Table F-1: Mapping between minimum QZ size, maximum device size, and applicable MTSU** + +| Minimum QZ required to contain all active antennas within the quiet zone (optional vendor declaration) | Max Device Size | Applicable MTSU | Note | +|--------------------------------------------------------------------------------------------------------|-----------------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 20cm | <20cm | MTSU 30cm | A system supporting a {20cm, 30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {20cm, 30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 30cm | +| 20cm | 20cm to 30cm | MTSU 30cm | A system supporting a {20cm, 30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {20cm, 30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 30cm | +| 20cm | 30cm to 40cm | MTSU 40cm | A system supporting a {20cm, 30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {20cm, 30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 40cm | +| 20cm | 40cm to 55cm | MTSU 55cm | A system supporting a {20cm, 30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {20cm, 30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 55cm | +| 20cm | >55cm | Not applicable until larger QZ is defined | Pending larger QZ (exceeding 55cm) definition | +| 30cm | $\leq$ 30cm | MTSU 30cm | A system supporting a {30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 30cm | +| 30cm | 30cm to 40cm | MTSU 40cm | A system supporting a {30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 40cm | +| 30cm | 40cm to 55cm | MTSU 55cm | A system supporting a {30cm, 40cm, 55cm} QZ can be used as long as the assessed MU with a {30cm, 40cm, 55cm} QoQZ validation is $\leq$ MTSU 55cm | +| 30cm | >55cm | Not applicable until larger QZ is defined | Pending larger QZ (exceeding 55cm) definition | +| 40cm | $\leq$ 40cm | MTSU 40cm | A system supporting a {40cm, 55cm} QZ can be used as long as the assessed MU with a {40cm, 55cm} QoQZ validation is $\leq$ MTSU 40cm | +| 40cm | 40cm to 55cm | MTSU 55cm | A system supporting a {40cm, 55cm} QZ can be used as long as the assessed MU with a {40cm, 55cm} QoQZ validation is $\leq$ MTSU 55cm | +| 40cm | >55cm | Not applicable until larger QZ is defined | Pending larger QZ (exceeding 55cm) definition | +| 55cm | 40cm to 55cm | MTSU 55cm | | +| 55cm | >55cm | Not applicable until larger QZ is defined | Pending larger QZ (exceeding 55cm) definition | + +| | | | | +|-------|-------|-------------------------------------------|---------------------------------------------------------------------------------| +| >55cm | >55cm | Not applicable until larger QZ is defined | Note: QZs exceeding 55cm cannot be declared due to lack of larger QZ definition | +|-------|-------|-------------------------------------------|---------------------------------------------------------------------------------| + +--- + +## Annex G: Acceptable uncertainty of test system for test cases defined in TS 37.571-1 for radiative testing + +This Annex is informative only, as the acceptable uncertainties of a test system are defined in Annex C of 37.571-1 [20]. + +--- + +## Annex H: Change history + +| Change history | | | | | | | | +|----------------|---------------------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-09 | RAN5 #76 | R5-174706 | | | | Initial skeleton | 0.0.1 | +| 2018-04 | RAN5 #2-5G-NR-Adhoc | R5-182093 | | | | Implementation of pCRs to TS 38.903 V0.0.1 | 0.1.0 | +| 2018-05 | RAN5#79 | R5-182670 | | | | Editorial update of TR 38.903. | 0.2.0 | +| 2018-09 | RAN5#80 | R5-185213 | | | | Making Measurement Uncertainty Terms Common between methods in TR 38.90 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185214 | | | | TP on Measurement Uncertainty Contributions in FR2 | 1.0.0 | +| 2018-09 | RAN5#80 | R5-185212 | | | | Adding MU values for EIRP/TRP measurements with Near Field test range (NFTF) at mmWave | 1.0.0 | +| 2018-09 | RAN#81 | - | - | - | - | raised to v15.0.0 with editorial changes only | 15.0.0 | +| 2018-12 | RAN#82 | R5-187023 | 0010 | - | F | Editorial update of Annex B | 15.1.0 | +| 2018-12 | RAN#82 | R5-187024 | 0011 | - | F | Addition of MU contribution for demodulation test cases | 15.1.0 | +| 2018-12 | RAN#82 | R5-187025 | 0012 | - | F | Addition of MU contribution for RRM test cases | 15.1.0 | +| 2018-12 | RAN#82 | R5-187148 | 0013 | - | F | General clauses updated for TR38.903 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187848 | 0008 | 1 | F | FR2 Spurious Emission measurement grids and offset values | 15.1.0 | +| 2018-12 | RAN#82 | R5-188060 | 0019 | 1 | F | Update of MU budget and contributor description to TR 38.903 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188224 | 0009 | 1 | F | Update MU budget in TR 38.903 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188225 | 0016 | 1 | F | Update of MU budget tables in TR 38.903 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188226 | 0017 | 2 | F | Addition of descriptions on new MU contributions | 15.1.0 | +| 2019-03 | RAN#83 | R5-192476 | 0030 | 1 | F | Addition of Test Tolerance analysis for FR1 PRACH Test cases | 15.2.0 | +| 2019-03 | RAN#83 | R5-192504 | 0038 | 1 | F | Addition of TT analysis for Transmit timing accuracy Tests | 15.2.0 | +| 2019-03 | RAN#83 | R5-192505 | 0031 | 1 | F | Addition common text for RRM | 15.2.0 | +| 2019-03 | RAN#83 | R5-192534 | 0039 | - | F | Addition of TT Analysis for Timing Advance Adjustment Accuracy 4.4.3.1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192671 | 0033 | 1 | F | Addition of TT analysis for event triggered test cases | 15.2.0 | +| 2019-03 | RAN#83 | R5-192679 | 0036 | 1 | F | Addition of TT analysis for handover with known cell | 15.2.0 | +| 2019-03 | RAN#83 | R5-192845 | 0029 | 1 | F | CR to update TR 38.903 | 15.2.0 | +| 2019-06 | RAN#84 | R5-193799 | 0048 | - | F | FR1 Test tolerance analysis for intra re-selection 6.1.1.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193800 | 0049 | - | F | FR1 Test tolerance analysis for inter re-selection 6.1.1.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193801 | 0050 | - | F | FR1 Test tolerance analysis for interRAT higher priority re-selection 6.1.2.1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193802 | 0051 | - | F | FR1 Test tolerance analysis for interRAT lower priority re-selection 6.1.2.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-193803 | 0052 | - | F | FR1 Test tolerance analysis for interRAT known handover 6.3.1.4 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194027 | 0057 | - | F | CR on spurious emission MU in FR2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194123 | 0058 | - | F | Definition of MU terminologies in TR 38.903 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195014 | 0054 | 1 | F | FR1 Test tolerance analysis for EN-DC SCell activation 4.5.3.1-4.5.3.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195015 | 0060 | 1 | F | Test Tolerance analysis for Inter-Freq measurement Test Cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-195159 | 0059 | 1 | F | CR to update TR 38.903 after RAN5#5-5GNR Adhoc | 15.3.0 | +| 2019-06 | RAN#84 | R5-195181 | 0055 | 1 | F | FR1 Test tolerance analysis for EN-DC measurement reporting 4.6.1.1-4.6.1.4 | 15.3.0 | +| 2019-06 | RAN#84 | - | - | - | - | Administrative release upgrade to match the release of 3GPP TS 38.521-1 which was upgraded at RAN#84 to Rel-16 due to Rel-16 relevant CR(s) | 16.0.0 | +| 2019-09 | RAN#85 | R5-195583 | 0061 | - | F | Update FR1 Test tolerance of 4.5.3.1-4.5.3.3 SCell activation | 16.1.0 | +| 2019-09 | RAN#85 | R5-195584 | 0062 | - | F | Update FR1 Test tolerance of 6.1.1.1 FR1 cell re-selection | 16.1.0 | +| 2019-09 | RAN#85 | R5-195585 | 0063 | - | F | Update FR1 Test tolerance of 6.1.1.2 FR1-FR1 cell re-selection | 16.1.0 | +| 2019-09 | RAN#85 | R5-195586 | 0064 | - | F | Update FR1 Test tolerance of 6.1.2.1 inter-RAT cell re-selection to higher priority | 16.1.0 | +| 2019-09 | RAN#85 | R5-195587 | 0065 | - | F | Update FR1 Test tolerance of 6.1.2.2 inter-RAT cell re-selection to lower priority | 16.1.0 | +| 2019-09 | RAN#85 | R5-195588 | 0066 | - | F | Update FR1 Test tolerance of 6.3.1.4 inter-RAT handover to known cell | 16.1.0 | +| 2019-09 | RAN#85 | R5-195589 | 0067 | - | F | Addition FR1 Test tolerance of 6.3.1.5 inter-RAT handover to unknown cell | 16.1.0 | +| 2019-09 | RAN#85 | R5-195590 | 0068 | - | F | Addition FR1 Test tolerance of 6.3.2.1.1 intra-freq RRC re- | 16.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|---------------|--| +| | | | | | | establishment | | +|--|--|--|--|--|--|---------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------|--------| +| 2019-09 | RAN#85 | R5-195591 | 0069 | - | F | Addition FR1 Test tolerance of 6.3.2.1.2 inter-freq RRC re-establishment | 16.1.0 | +| 2019-09 | RAN#85 | R5-195592 | 0070 | - | F | Addition FR1 Test tolerance of 6.3.2.3.1 NR RRC redirection | 16.1.0 | +| 2019-09 | RAN#85 | R5-195593 | 0071 | - | F | Addition FR1 Test tolerance of 6.3.2.3.2 inter-RAT RRC redirection | 16.1.0 | +| 2019-09 | RAN#85 | R5-197362 | 0072 | 1 | F | FR1 Test Tolerance Analysis for SSB-based RLM IS Tests | 16.1.0 | +| 2019-09 | RAN#85 | R5-197363 | 0073 | 1 | F | FR1 Test Tolerance Analysis for SA Tx Timing Accuracy 6.4.1.1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197365 | 0083 | 1 | F | TT_Analysis_ENDC_FR1_RLM_OOS | 16.1.0 | +| 2019-09 | RAN#85 | R5-197369 | 0087 | 1 | F | TT_Analysis_SA_FR1_TAAA | 16.1.0 | +| 2019-09 | RAN#85 | R5-197494 | 0077 | 1 | F | CR on DUT turnover and relations with QoQZ MU | 16.1.0 | +| 2019-09 | RAN#85 | R5-197505 | 0081 | 1 | F | Update of FR2 MUs in TR 38.903 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197571 | 0078 | 1 | F | TT Analysis for SS-RSRP FR1 tests | 16.1.0 | +| 2019-09 | RAN#85 | R5-197625 | 0080 | 1 | F | CR on FR2 OFF Power MU | 16.1.0 | +| 2019-09 | RAN#85 | R5-197659 | 0076 | 2 | F | CR on spurious emission MU in FR2 | 16.1.0 | +| 2019-12 | RAN#86 | R5-198260 | 0099 | - | F | CR to 38.903 to define Reference Methodology for SE | 16.2.0 | +| 2019-12 | RAN#86 | R5-198285 | 0100 | - | F | FR1 Test tolerance analysis for interRAT measurement | 16.2.0 | +| 2019-12 | RAN#86 | R5-198427 | 0101 | - | F | Correction to uncertainty budget calculation principles | 16.2.0 | +| 2019-12 | RAN#86 | R5-199070 | 0098 | 1 | F | Editorial corrections to FR1 Test Tolerance files | 16.2.0 | +| 2019-12 | RAN#86 | R5-199082 | 0104 | 2 | F | FR1 Test Tolerance : Addition of TT Analysis for 6.3.1.1 NR SA FR1 Intra-Freq Handover | 16.2.0 | +| 2019-12 | RAN#86 | R5-199083 | 0105 | 2 | F | FR1 Test Tolerance : Addition of TT Analysis for 6.3.1.2 NR SA FR1 Intra-Freq Handover | 16.2.0 | +| 2019-12 | RAN#86 | R5-199084 | 0106 | 2 | F | FR1 Test Tolerance : Addition of TT Analysis for 6.3.1.3 NR SA FR1 Inter-Freq Handover | 16.2.0 | +| 2019-12 | RAN#86 | R5-199091 | 0102 | 1 | F | Update on FR2 MUs in 38.903 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199092 | 0103 | 1 | F | Update on FR2 Spurious MUs in 38.903 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199362 | 0091 | 1 | F | FR1 Test tolerance analysis for interruptions active and non-active | 16.2.0 | +| 2019-12 | RAN#86 | R5-199363 | 0094 | 1 | F | FR1 Test tolerance analysis for CSI-RS based RLM | 16.2.0 | +| 2020-03 | RAN#87 | R5-200163 | 0107 | - | F | Add Annex A.2 handling of common Test Tolerance Topics for FR2 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200329 | 0112 | - | F | CR to 38.903 on XPD Verification | 16.3.0 | +| 2020-03 | RAN#87 | R5-200470 | 0114 | - | F | FR1 Test tolerance analysis for interruptions deactivated NR SCC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200918 | 0116 | 1 | F | Update to FR2 TRx Measurement Uncertainties | 16.3.0 | +| 2020-03 | RAN#87 | R5-201037 | 0108 | 1 | F | Test tolerance analysis inter-frequency SS-RSRP and intra-frequency SS-SINR | 16.3.0 | +| 2020-03 | RAN#87 | R5-201038 | 0109 | 1 | F | Test tolerance analysis SS-RSRQ and inter-frequency SS-SINR | 16.3.0 | +| 2020-03 | RAN#87 | R5-201042 | 0110 | 1 | F | Test Tolerance analysis for CSI-RS-Based L1-RSRP measurement test cases | 16.3.0 | +| 2020-03 | RAN#87 | R5-201043 | 0111 | 1 | F | Test Tolerance analysis for SSB-Based L1-RSRP measurement test cases | 16.3.0 | +| 2020-06 | RAN#88 | R5-201662 | 0118 | - | F | FR1 Test tolerance analysis for interruptions deactivated E-UTRAN SCC | 16.4.0 | +| 2020-06 | RAN#88 | R5-203094 | 0119 | 1 | F | FR1 Test tolerance analysis for SCell activation | 16.4.0 | +| 2020-06 | RAN#88 | R5-202104 | 0124 | - | F | Test tolerance correction for event triggered measurement test cases | 16.4.0 | +| 2020-06 | RAN#88 | R5-202105 | 0125 | - | F | Test tolerance correction for CSI-RS-based L1-RSRP measurement test cases | 16.4.0 | +| 2020-06 | RAN#88 | R5-202702 | 0130 | 1 | F | Test Tolerance analysis TC 4.5.4 and 6.5.4 RRC reconfiguration delay | 16.4.0 | +| 2020-06 | RAN#88 | R5-202769 | 0127 | 1 | F | CR to 38.903 to introduce baseline Demod MU tables | 16.4.0 | +| 2020-06 | RAN#88 | R5-202915 | 0117 | 1 | F | MU contributors for RRM FR2 TC 7.7.1.1 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202916 | 0126 | 1 | F | CR to 38.903 to introduce PC1 MU Tables | 16.4.0 | +| 2020-06 | RAN#88 | R5-202917 | 0128 | 1 | F | Update to FR2 Measurement Uncertainties | 16.4.0 | +| 2020-06 | RAN#88 | R5-202938 | 0129 | 1 | F | Addition of EIRP to Transmit OFF power MU analysis | 16.4.0 | +| 2020-09 | RAN#89 | R5-203231 | 0131 | - | F | TT analysis for RRM TC 8.5.2.1.1.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203232 | 0132 | - | F | TT analysis for RRM TC 8.5.2.2.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203233 | 0133 | - | F | TT analysis for RRM TC 8.5.2.3.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203237 | 0134 | - | F | TT analysis for RRM TC 4.7.4.1.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203238 | 0135 | - | F | TT analysis for RRM TC 4.7.4.1.2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203323 | 0140 | - | F | Add Draft Test Tolerance analysis for FR2 Tx Timing Test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-203324 | 0141 | - | F | Add Draft Test Tolerance analysis for FR2 Inter-freq Event-trig Test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-203325 | 0142 | - | F | Add Draft Test Tolerance analysis for FR2 Intra-freq SS-RSRP Test | 16.5.0 | + +| | | | | | | | | +|--|--|--|--|--|--|------|--| +| | | | | | | case | | +|--|--|--|--|--|--|------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------|--------| +| 2020-09 | RAN#89 | R5-203825 | 0149 | - | F | Addition of FR1 Test tolerance analysis for 6.3.2.1.3 RRC Re-establishment | 16.5.0 | +| 2020-09 | RAN#89 | R5-203826 | 0150 | - | F | Update of grouping of test cases in clause 8 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204190 | 0154 | - | F | On Standard Deviation Definition in 38.903 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204788 | 0138 | 1 | F | Correction to the extreme conditions in TT analysis of 4.7.1.2.1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204887 | 0139 | 1 | F | CR to update the DL AWGN absolute power for RRM test cases | 16.5.0 | +| 2020-09 | RAN#89 | R5-204888 | 0143 | 1 | F | Adjacent Channel Selectivity FR2 MU definition in 38.903 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204889 | 0144 | 1 | F | In-band Blocking FR2 MU definition in 38.903 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204890 | 0153 | 1 | F | CR to update MU in 38.903 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204891 | 0155 | 1 | F | FR2 Minimum output power measurement uncertainty | 16.5.0 | +| 2020-09 | RAN#89 | R5-204945 | 0152 | 1 | F | CR to 38.903 on some of the Transmit OFF power MU parameters | 16.5.0 | +| 2020-09 | RAN#89 | R5-204946 | 0156 | 1 | F | Update of AWGN flatness in TR 38.903 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204947 | 0157 | 1 | F | FR2 EIRP OFF power measurement uncertainty | 16.5.0 | +| 2020-09 | RAN#89 | R5-205001 | 0145 | 1 | F | Addition of FR1 Test tolerance analysis for DCI based BWP switch | 16.5.0 | +| 2020-09 | RAN#89 | R5-205002 | 0146 | 1 | F | Addition of FR1 Test tolerance analysis for RRC based BWP switch | 16.5.0 | +| 2020-09 | RAN#89 | R5-205003 | 0147 | 1 | F | Addition of FR1 Test tolerance analysis for SSB based BFR | 16.5.0 | +| 2020-09 | RAN#89 | R5-205004 | 0148 | 1 | F | Addition of FR1 Test tolerance analysis for CSI-RS based BFR | 16.5.0 | +| 2020-12 | RAN#90 | R5-205628 | 0174 | - | F | RRM FR2 DL AWGN absolute power MU | 16.6.0 | +| 2020-12 | RAN#90 | R5-205704 | 0176 | - | F | Update of demod MU | 16.6.0 | +| 2020-12 | RAN#90 | R5-205831 | 0177 | - | F | Editorial correction of clause 5.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205949 | 0183 | - | F | Update of grouping of test cases in clause 8 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206809 | 0158 | 1 | F | TT analysis for RRM 6.7.5.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206810 | 0159 | 1 | F | TT analysis for RRM 6.7.6.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206811 | 0160 | 1 | F | TT analysis for RRM 6.7.7.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206812 | 0161 | 1 | F | TT analysis for RRM 4.7.5.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206813 | 0163 | 1 | F | TT analysis for RRM 8.5.2.1.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206814 | 0166 | 1 | F | Add Draft Test Tolerance analysis for FR2 PRACH Test cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-206815 | 0178 | 1 | F | Addition of FR1 TT analysis for inter-RAT cell reselection | 16.6.0 | +| 2020-12 | RAN#90 | R5-206816 | 0179 | 1 | F | Addition of FR1 TT analysis for inter-RAT handover | 16.6.0 | +| 2020-12 | RAN#90 | R5-206817 | 0180 | 1 | F | Addition of FR1 TT analysis for inter-RAT SFTD measurement | 16.6.0 | +| 2020-12 | RAN#90 | R5-206818 | 0181 | 1 | F | Addition of FR1 TT analysis for inter-RAT event-triggered reporting | 16.6.0 | +| 2020-12 | RAN#90 | R5-206835 | 0184 | 1 | F | CR to 38.903 on ETC Testing | 16.6.0 | +| 2020-12 | RAN#90 | R5-206836 | 0185 | 1 | F | CR to add DFF MU Tables in 38.903 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206837 | 0187 | 1 | F | Update FR2 TRx MU in 38.903 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206838 | 0189 | 1 | F | FR2 Time masks updates | 16.6.0 | +| 2020-12 | RAN#90 | R5-206845 | 0164 | 1 | F | TT analysis for RRM 8.5.2.2.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206846 | 0167 | 1 | F | Update Draft Test Tolerance analysis for FR2 Tx Timing Test cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-206847 | 0169 | 1 | F | Add Draft Test Tolerance analysis FR2 RLM Peak Test cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-206848 | 0170 | 1 | F | Add Draft Test Tolerance analysis for FR2 Intra-freq Event-trig Test cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-206849 | 0171 | 1 | F | Update Draft Test Tolerance analysis for FR2 Inter-freq Event-trig Test cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-206850 | 0172 | 1 | F | Update Draft Test Tolerance analysis for FR2 Intra-freq SS-RSRP Test case | 16.6.0 | +| 2020-12 | RAN#90 | R5-206851 | 0173 | 1 | F | Add Draft Test Tolerance analysis for FR2 Inter-freq SS-RSRP Test case | 16.6.0 | +| 2020-12 | RAN#90 | R5-206852 | 0182 | 1 | F | Update of FR1 TT analysis for 6.1.1.1 intra-freq cell re-selection | 16.6.0 | +| 2020-12 | RAN#90 | R5-206911 | 0165 | 1 | F | TT analysis for RRM 8.5.2.3.2 | 16.6.0 | +| 2021-03 | RAN#91 | R5-210431 | 0193 | - | F | Test tolerance analysis for 7.4.3.1 and 5.4.3.1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210438 | 0195 | - | F | Update TT analyses for FR2 iRAT measurement accuracy test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210445 | 0197 | - | F | Update SS-RSRQ measurement accuracy TT analyses for SNR uncertainty change | 16.7.0 | +| 2021-03 | RAN#91 | R5-210815 | 0203 | - | F | Update Test Tolerance analyses for FR2 Tx Timing Test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210817 | 0204 | - | F | Update Test Tolerance analyses for FR2 RLM Test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210818 | 0205 | - | F | Update Test Tolerance analyses for FR2 Event-Trig Test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210819 | 0206 | - | F | Update Test Tolerance analyses for FR2 SS-RSRP Test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210820 | 0207 | - | F | Update Test Tolerance analyses for FR1 RLM Test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-210846 | 0210 | - | F | Update of grouping of test cases in clause 8 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211175 | 0216 | - | F | FR2 Minimum output power measurement uncertainty update | 16.7.0 | +| 2021-03 | RAN#91 | R5-211191 | 0218 | - | F | CR to 38.903 on PC1 Measurement Grid MUs | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------|---------| +| 2021-03 | RAN#91 | R5-211642 | 0194 | 1 | F | Test tolerance analysis for 4.5.7.1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211643 | 0196 | 1 | F | Update SS-RSRP measurement accuracy TT analyses for SNR uncertainty change | 16.7.0 | +| 2021-03 | RAN#91 | R5-211644 | 0199 | 1 | F | Update RRM MU values for FR2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211645 | 0211 | 1 | F | Update of FR1 TT for SCell activation | 16.7.0 | +| 2021-03 | RAN#91 | R5-211646 | 0212 | 1 | F | Update of FR1 TT for SSB based link recovery | 16.7.0 | +| 2021-03 | RAN#91 | R5-211647 | 0213 | 1 | F | Update of FR1 TT for CSI-RS based link recovery | 16.7.0 | +| 2021-03 | RAN#91 | R5-211648 | 0214 | 1 | F | Update of FR1 TT for RRC re-establishment | 16.7.0 | +| 2021-03 | RAN#91 | R5-211649 | 0219 | 1 | F | Update of Test Tolerance analysis for FR1 event triggered reporting test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211650 | 0220 | 1 | F | Update of Test Tolerance analysis for FR1 SSB-based L1-RSRP test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211651 | 0221 | 1 | F | Update of Test Tolerance analysis for FR1 CSI-RS based L1-RSRP test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211652 | 0224 | 1 | F | Test Tolerance analysis for FR2 event triggered reporting test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211732 | 0202 | 1 | F | Editorial correction to several MU factors | 16.7.0 | +| 2021-03 | RAN#91 | R5-211892 | 0198 | 1 | F | Correct 6.3.1.1 TT analysis | 16.7.0 | +| 2021-03 | RAN#91 | R5-211930 | 0191 | 1 | F | Adjacent Channel Selectivity FR2 MU definition in 38.903 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211931 | 0192 | 1 | F | In-band Blocking FR2 MU definition in 38.903 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211932 | 0208 | 1 | F | Update on FR2 Blocking Test MU | 16.7.0 | +| 2021-03 | RAN#91 | R5-211933 | 0209 | 1 | F | Update MU for FR2 RRM | 16.7.0 | +| 2021-03 | RAN#91 | R5-211934 | 0215 | 1 | F | Update FR2 MU and TT in 38.903 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211935 | 0217 | 1 | F | CR to 38.903 on ETC Testing | 16.7.0 | +| 2021-03 | RAN#91 | R5-211936 | 0222 | 1 | F | Update of demod SNR testability | 16.7.0 | +| 2021-06 | RAN#92 | R5-212352 | 0230 | - | F | ACS and IBB - FR2 MU definition in 38.903 | 16.8.0 | +| 2021-06 | RAN#92 | R5-213851 | 0228 | 1 | F | Update of demod SNR testability | 16.8.0 | +| 2021-06 | RAN#92 | R5-213852 | 0237 | 1 | F | Measurement uncertainties for FR2 Relative and aggregate power tolerance | 16.8.0 | +| 2021-06 | RAN#92 | R5-213940 | 0225 | 1 | F | Update TT analysis for 5.7.1.1 | 16.8.0 | +| 2021-06 | RAN#92 | R5-213941 | 0226 | 1 | F | New TT analysis for 5.7.2.1 | 16.8.0 | +| 2021-06 | RAN#92 | R5-213942 | 0227 | 1 | F | New TT analysis for 5.7.3.1 | 16.8.0 | +| 2021-06 | RAN#92 | R5-213943 | 0235 | 1 | F | Test Tolerance analysis for FR2 event triggered reporting test cases | 16.8.0 | +| 2021-06 | RAN#92 | R5-213944 | 0236 | 1 | F | Test Tolerance analysis for FR2 event triggered reporting test cases | 16.8.0 | +| 2021-06 | RAN#92 | R5-213945 | 0239 | 1 | F | Update of ACLR testability | 16.8.0 | +| 2021-06 | RAN#92 | R5-214069 | 0234 | 1 | F | Measurement Uncertainties updates for FR2 Extreme Testing Conditions | 16.8.0 | +| 2021-06 | RAN#92 | R5-214114 | 0231 | 1 | F | Add Test Tolerance analyses for FR2 RLM Test cases | 16.8.0 | +| 2021-06 | RAN#92 | R5-214115 | 0232 | 1 | F | Update and add Test Tolerance analysis for FR2 Intra-freq Event-trig Test cases | 16.8.0 | +| 2021-06 | RAN#92 | R5-214116 | 0233 | 1 | F | Update Test Tolerance analysis for FR2 Inter-freq SS-RSRP Test case | 16.8.0 | +| 2021-09 | RAN#93 | R5-214189 | 0240 | - | F | TT analysis for RRM test cases 5.7.2.2 and 7.7.2.2 | 16.9.0 | +| 2021-09 | RAN#93 | R5-214190 | 0241 | - | F | TT analysis for RRM test cases 5.7.3.2 and 7.7.3.2 | 16.9.0 | +| 2021-09 | RAN#93 | R5-214919 | 0247 | - | F | Update TT analysis for RRM test cases 5.7.1.2 and 7.7.1.2 | 16.9.0 | +| 2021-09 | RAN#93 | R5-215002 | 0248 | - | F | TT analysis for LTE SA TC 8.5.1.1-SFTD accuracy | 16.9.0 | +| 2021-09 | RAN#93 | R5-215330 | 0250 | - | F | Correction to MU for spurious emission band UE co-existence | 16.9.0 | +| 2021-09 | RAN#93 | R5-215433 | 0252 | - | F | Correction of Test Tolerance analysis for FR2 event triggered reporting in DRX test cases | 16.9.0 | +| 2021-09 | RAN#93 | R5-215834 | 0255 | 1 | F | Introduction of MTSU mapping related to Max Device Size | 16.9.0 | +| 2021-09 | RAN#93 | R5-216102 | 0242 | 1 | F | Update of demod SNR testability | 16.9.0 | +| 2021-09 | RAN#93 | R5-216103 | 0243 | 1 | F | Add Test Tolerance analyses for EN-DC FR2 interruptions at transitions between active and non-active during DRX Test cases | 16.9.0 | +| 2021-09 | RAN#93 | R5-216104 | 0244 | 1 | F | Introducing EIRP UL Absolute Power MU for FR2 RRM | 16.9.0 | +| 2021-09 | RAN#93 | R5-216105 | 0249 | 1 | F | Correction of power control in 38.903 | 16.9.0 | +| 2021-09 | RAN#93 | R5-216117 | 0256 | 1 | F | 38.903 CR FR2 ETC MU updates for new ETC test cases | 16.9.0 | +| 2021-09 | RAN#93 | R5-216362 | 0251 | 1 | F | Correction of Test Tolerance analysis for FR2 event triggered reporting in non-DRX test cases | 16.9.0 | +| 2021-09 | RAN#93 | R5-216363 | 0253 | 1 | F | Test Tolerance analysis for FR2 SSB-based L1-RSRP measurement for beam reporting test cases | 16.9.0 | +| 2021-12 | RAN#94 | R5-218208 | 0280 | - | F | Correct TT analysis for TC 5.7.3.2 and 7.7.3.2 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218242 | 0270 | 1 | F | TT analysis for Mob_enh RRM TC 6.3.1.9+6.3.1.10 | 16.10.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------|---------| +| 2021-12 | RAN#94 | R5-218262 | 0275 | 1 | F | Test Tolerance analysis for FR2 CSI-RS based L1-RSRP measurement for beam reporting test cases | 16.10.0 | +| 2021-12 | RAN#94 | R5-218295 | 0272 | 1 | F | Addition of test tolerance analysis for test cases of EN-DC FR1 DL Interruptions at switching between two uplink carriers | 16.10.0 | +| 2021-12 | RAN#94 | R5-218330 | 0261 | 1 | F | TT analysis for PS RRM TC 6.1.1.3 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218331 | 0262 | 1 | F | TT analysis for PS RRM TC 6.1.1.4 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218332 | 0263 | 1 | F | TT analysis for PS RRM TC 6.1.1.5 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218333 | 0264 | 1 | F | TT analysis for PS RRM TC 6.1.1.6 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218334 | 0273 | 1 | F | Addition of test tolerance analysis for test cases of inter-RAT cell re-selection with relaxed measurement criterion | 16.10.0 | +| 2021-12 | RAN#94 | R5-218337 | 0265 | 1 | F | TT analysis for SRVCC RRM TC 6.3.1.6 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218338 | 0266 | 1 | F | TT analysis for SRVCC RRM TC 6.6.5.1 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218353 | 0269 | 1 | F | TT analysis for HST RRM TC 6.1.2.5 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218354 | 0276 | 1 | F | Test Tolerance analysis for SA FR1 - E-UTRAN event-triggered reporting in DRX for HST | 16.10.0 | +| 2021-12 | RAN#94 | R5-218355 | 0277 | 1 | F | Test Tolerance analysis for E-UTRA - NR FR1 Cell reselection tests for HST | 16.10.0 | +| 2021-12 | RAN#94 | R5-218356 | 0278 | 1 | F | Test Tolerance analysis for SA FR1 - E-UTRAN event-triggered reporting in DRX for HST | 16.10.0 | +| 2021-12 | RAN#94 | R5-218394 | 0257 | 1 | F | TT analysis for Mob_enh RRM TC 6.3.1.7+6.3.1.8 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218395 | 0258 | 1 | F | TT analysis for Mob_enh RRM TC 6.3.3.1 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218396 | 0259 | 1 | F | TT analysis for Mob_enh RRM TC 6.3.3.2 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218397 | 0267 | 1 | F | TT analysis for HST RRM TC 4.6.1.7+6.6.1.7 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218398 | 0268 | 1 | F | TT analysis for HST RRM TC 4.6.4.5+6.6.4.5 | 16.10.0 | +| 2021-12 | RAN#94 | R5-218402 | 0274 | 1 | F | MU for Tx modulation quality test cases | 16.10.0 | +| 2021-12 | RAN#94 | R5-218408 | 0279 | 1 | F | 38.903 Beam correspondence Measurement Uncertainties | 16.10.0 | +| 2021-12 | RAN#94 | - | - | - | - | missing attachment file added | 16.10.1 | +| 2022-03 | RAN#95 | R5-220281 | 0285 | - | F | Test Tolerance analysis for FR1 CLI-RSSI measurement with non-DRX | 16.11.0 | +| 2022-03 | RAN#95 | R5-220718 | 0289 | - | F | TT analysis for FR2 SSB intra-freq measurement with DRX TCs | 16.11.0 | +| 2022-03 | RAN#95 | R5-220994 | 0295 | - | F | Addition of test tolerance analysis for 4.6.7.1 and 6.6.8.1 EN-DC and NR SA CSI-RS based L1-SINR measurement | 16.11.0 | +| 2022-03 | RAN#95 | R5-220995 | 0296 | - | F | Addition of test tolerance analysis for 4.6.7.2 EN-DC SSB based L1-SINR measurement | 16.11.0 | +| 2022-03 | RAN#95 | R5-220996 | 0297 | - | F | Addition of test tolerance analysis for 4.6.7.3 EN-DC CSI-RS based L1-SINR measurement | 16.11.0 | +| 2022-03 | RAN#95 | R5-220997 | 0298 | - | F | Addition of test tolerance analysis for 6.6.8.2 NR SA SSB based L1-SINR measurement | 16.11.0 | +| 2022-03 | RAN#95 | R5-220998 | 0299 | - | F | Addition of test tolerance analysis for 6.6.8.3 NR SA CSI-RS based L1-SINR measurement | 16.11.0 | +| 2022-03 | RAN#95 | R5-221286 | 0302 | - | F | Test Tolerance analysis for E-UTRA - NR FR1 Cell reselection tests for HST | 16.11.0 | +| 2022-03 | RAN#95 | R5-221287 | 0303 | - | F | Test Tolerance analysis for inter-frequency RRC re-establishment test case | 16.11.0 | +| 2022-03 | RAN#95 | R5-221304 | 0305 | - | F | Correction of clause 3 | 16.11.0 | +| 2022-03 | RAN#95 | R5-221629 | 0301 | 1 | F | 38.903 Beam correspondence Measurement Uncertainties | 16.11.0 | +| 2022-03 | RAN#95 | R5-221644 | 0304 | 1 | F | Test Tolerance analysis for inter-frequency RRC re-establishment test case | 16.11.0 | +| 2022-03 | RAN#95 | R5-221647 | 0281 | 1 | F | TT analysis for Mob_enh RRM TC 6.3.1.9+6.3.1.10 | 16.11.0 | +| 2022-03 | RAN#95 | R5-221648 | 0284 | 1 | F | TT analysis for Mob_enh RRM TC 6.3.1.11+6.3.1.12 | 16.11.0 | +| 2022-03 | RAN#95 | R5-221649 | 0290 | 1 | F | TT analysis for Mob_enh RRM TCs 7.3.1.4 and 7.3.1.5 | 16.11.0 | +| 2022-03 | RAN#95 | R5-221656 | 0294 | 1 | F | Add Test Tolerance analyses for NR SA FR1 cell re-selection for UE configured with highSpeedMeasFlag-r16 Test cases | 16.11.0 | +| 2022-03 | RAN#95 | R5-221743 | 0286 | 1 | F | FR2 EVM MU definition in 38.903 | 16.11.0 | +| 2022-03 | RAN#95 | R5-221744 | 0287 | 1 | F | TT analysis for FR2 SSB based BFD TCs | 16.11.0 | +| 2022-03 | RAN#95 | R5-221745 | 0288 | 1 | F | TT analysis for FR2 SSB intra-freq measurement without DRX TCs | 16.11.0 | +| 2022-03 | RAN#95 | R5-221746 | 0292 | 1 | F | Addition of summary table for MU factors | 16.11.0 | +| 2022-03 | RAN#95 | R5-221747 | 0300 | 1 | F | Update of predicted SNR upper bound for noise free SDR scenarios | 16.11.0 | +| 2022-03 | RAN#95 | R5-221814 | 0291 | 1 | F | TT analysis for Mob_enh RRM TCs 7.3.3.1 | 16.11.0 | +| 2022-03 | RAN#95 | R5-221840 | 0293 | 1 | F | Addition of TT analysis for FR2 BFR test cases | 16.11.0 | +| 2022-06 | RAN#96 | R5-223608 | 0306 | 1 | F | Add Test Tolerance analyses for EN-DC FR2 RLM tests for PSCell configured with CSI-RS-based RLM RS in non-DRX | 16.12.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------|---------| +| 2022-06 | RAN#96 | R5-223609 | 0320 | 1 | F | Test Tolerance analysis for FR2 CSI-RS based L1-RSRP measurement for beam reporting test cases | 16.12.0 | +| 2022-06 | RAN#96 | R5-223708 | 0315 | 1 | F | Addition of test tolerance analysis for 5.6.6.3 | 16.12.0 | +| 2022-06 | RAN#96 | R5-223709 | 0317 | 1 | F | Addition of test tolerance analysis for 7.6.6.3 | 16.12.0 | +| 2022-06 | RAN#96 | R5-223865 | 0308 | 1 | F | TT analysis for RRM test case 5.7.4.1 and 5.7.4.2 | 16.12.0 | +| 2022-06 | RAN#96 | R5-223866 | 0318 | 1 | F | Test Tolerances for Intra-frequency SS-RSRP measurement accuracy tests in FR2 | 16.12.0 | +| 2022-06 | RAN#96 | R5-223883 | 0313 | 1 | F | Addition of test tolerance analysis for 5.6.6.1 and 7.6.6.1 | 16.12.0 | +| 2022-06 | RAN#96 | R5-223884 | 0314 | 1 | F | Addition of test tolerance analysis for 5.6.6.2 | 16.12.0 | +| 2022-06 | RAN#96 | R5-223885 | 0316 | 1 | F | Addition of test tolerance analysis for 7.6.6.2 | 16.12.0 | +| 2022-09 | RAN#97 | R5-223964 | 0322 | - | F | TT analysis for 5.7.1.3 and 7.7.1.3 | 16.13.0 | +| 2022-09 | RAN#97 | R5-223975 | 0324 | - | F | TT analysis for 4.3.2.2.3 | 16.13.0 | +| 2022-09 | RAN#97 | R5-224412 | 0338 | - | F | Introduction of NR positioning test cases information | 16.13.0 | +| 2022-09 | RAN#97 | R5-224521 | 0341 | - | F | TT analysis for NR SL RRM TC 9.1.1.1 - GNSS | 16.13.0 | +| 2022-09 | RAN#97 | R5-224522 | 0342 | - | F | TT analysis for NR SL RRM TC 9.1.1.2 - SyncRef UE | 16.13.0 | +| 2022-09 | RAN#97 | R5-224523 | 0343 | - | F | TT analysis for NR SL RRM TC 9.1.1.3 - gNB | 16.13.0 | +| 2022-09 | RAN#97 | R5-224524 | 0344 | - | F | TT analysis for NR SL RRM TC 9.1.2.1 - S-SSB Tx gNB | 16.13.0 | +| 2022-09 | RAN#97 | R5-224525 | 0345 | - | F | TT analysis for NR SL RRM TC 9.1.2.2 - S-SSB Tx SyncRef UE | 16.13.0 | +| 2022-09 | RAN#97 | R5-224526 | 0346 | - | F | TT analysis for NR SL RRM TC 9.1.3.1 - GNSS highest priority | 16.13.0 | +| 2022-09 | RAN#97 | R5-224527 | 0347 | - | F | TT analysis for NR SL RRM TC 9.1.3.2 - Cell highest priority | 16.13.0 | +| 2022-09 | RAN#97 | R5-224528 | 0348 | - | F | TT analysis for NR SL RRM TC 9.1.4.1 - resource selection | 16.13.0 | +| 2022-09 | RAN#97 | R5-224529 | 0349 | - | F | TT analysis for NR SL RRM TC 9.1.4.2 - resource pre-emption | 16.13.0 | +| 2022-09 | RAN#97 | R5-224531 | 0351 | - | F | TT analysis for NR SL RRM TC 9.1.5.x - CBR | 16.13.0 | +| 2022-09 | RAN#97 | R5-224532 | 0352 | - | F | TT analysis for NR SL RRM TC 9.1.6.1 - WAN interruption | 16.13.0 | +| 2022-09 | RAN#97 | R5-224777 | 0365 | - | F | Addition of TT information for 6.5.5.5 and 6.5.5.6 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225137 | 0367 | - | F | Test Tolerances for Intra-frequency SS-RSRP measurement accuracy tests in FR2 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225612 | 0370 | 1 | F | Test Tolerances for DL Interruptions at switching between two uplink carriers test cases | 16.13.0 | +| 2022-09 | RAN#97 | R5-225616 | 0326 | 1 | F | TT analysis for positioning test case 15.2.1 and 15.2.2 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225618 | 0321 | 1 | F | Add Test Tolerance analyses for EN-DC FR2 RLM tests for PSCell configured with CSI-RS-based RLM RS in DRX | 16.13.0 | +| 2022-09 | RAN#97 | R5-225625 | 0329 | 1 | F | Addition of test tolerance analysis for 4.7.7.1.2 and 6.7.9.1.2 FR1 L1-SINR relative measurement accuracy | 16.13.0 | +| 2022-09 | RAN#97 | R5-225626 | 0333 | 1 | F | Addition of test tolerance analysis for 7.7.6.2 NR FR2 L1-SINR measurement accuracy test | 16.13.0 | +| 2022-09 | RAN#97 | R5-225627 | 0334 | 1 | F | Addition of test tolerance analysis for 7.7.6.3 NR FR2 L1-SINR measurement accuracy test | 16.13.0 | +| 2022-09 | RAN#97 | R5-225636 | 0366 | 1 | F | TT analysis update for FR2 RLM test cases 5.5.1.x and 7.5.1.x | 16.13.0 | +| 2022-09 | RAN#97 | R5-225637 | 0368 | 1 | F | Test Tolerances for SSB based L1-RSRP measurement accuracy tests in FR2 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225638 | 0369 | 1 | F | Test Tolerances for FR2 CSI-RS based L1-RSRPSS-RSRP measurement accuracy tests in FR2 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225663 | 0327 | 1 | F | Measurement uncertainties for test case 6.2.4_1 Configured transmitted power with Power Boost | 16.13.0 | +| 2022-09 | RAN#97 | R5-225671 | 0335 | 1 | F | PC1 MU - definition for MOP in 38.903 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225672 | 0336 | 1 | F | PC1 MU - definition for REFSENS in 38.903 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225673 | 0337 | 1 | F | PC1 MU - General Update in 38.903 section B.2.2 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225674 | 0359 | 1 | F | Definition of PC1 MU | 16.13.0 | +| 2022-09 | RAN#97 | R5-225675 | 0360 | 1 | F | Update FR2 TRx MU in 38.903 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225694 | 0328 | 1 | F | Addition of test tolerance analysis for 4.7.7.1.1 and 6.7.9.1.1 EN-DC FR1 L1-SINR absolute accuracy tests | 16.13.0 | +| 2022-09 | RAN#97 | R5-225695 | 0330 | 1 | F | Addition of test tolerance analysis for 4.7.7.2 and 6.7.9.2 FR1 L1-SINR absolute measurement accuracy | 16.13.0 | +| 2022-09 | RAN#97 | R5-225696 | 0331 | 1 | F | Addition of test tolerance analysis for 4.7.7.3.1 and 6.7.9.3.1 FR1 L1-SINR absolute measurement accuracy | 16.13.0 | +| 2022-09 | RAN#97 | R5-225697 | 0332 | 1 | F | Addition of test tolerance analysis for 4.7.7.3.2 and 6.7.9.3.2 EN-DC FR1 L1-SINR absolute measurement accuracy | 16.13.0 | +| 2022-09 | RAN#97 | R5-225854 | 0350 | 1 | F | TT analysis for NR SL RRM TC 9.1.4.3 - resource re-evaluation | 16.13.0 | +| 2022-09 | RAN#97 | R5-225860 | 0353 | 1 | F | TT analysis for NR PS RRM TC 7.1.1.3 - intra-freq reselection low mobility | 16.13.0 | +| 2022-09 | RAN#97 | R5-225861 | 0354 | 1 | F | TT analysis for NR PS RRM TC 7.1.1.4 - intra-freq reselection not- | 16.13.0 | + +| | | | | | | | | +|--|--|--|--|--|--|--------------|--| +| | | | | | | at-cell-edge | | +|--|--|--|--|--|--|--------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------|---------| +| 2022-09 | RAN#97 | R5-225862 | 0355 | 1 | F | TT analysis for NR PS RRM TC 7.1.1.5 - inter-freq reselection low mobility | 16.13.0 | +| 2022-09 | RAN#97 | R5-225863 | 0356 | 1 | F | TT analysis for NR PS RRM TC 7.1.1.6 - inter-freq reselection not-at-cell-edge | 16.13.0 | +| 2022-09 | RAN#97 | R5-225867 | 0357 | 1 | F | TT analysis for NR SA FR2 RRM TC 7.1.1.1 - intra-freq reselection | 16.13.0 | +| 2022-09 | RAN#97 | R5-225868 | 0358 | 1 | F | TT analysis for NR SA FR2 RRM TC 7.1.1.2 - inter-freq reselection | 16.13.0 | +| 2022-09 | RAN#97 | R5-225873 | 0361 | 1 | F | Addition of TT analysis for eMIMO L1-SINR test case 5.7.6.1 and 7.7.6.1 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225874 | 0362 | 1 | F | Addition of TT analysis for eMIMO L1-SINR test case 5.7.6.2 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225875 | 0363 | 1 | F | Addition of TT analysis for eMIMO L1-SINR test case 5.7.6.3 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225879 | 0323 | 1 | F | TT analysis for TS 37.571-1 TC 14.2.1 | 16.13.0 | +| 2022-09 | RAN#97 | R5-225880 | 0325 | 1 | F | TT analysis for TS 37.571-1 TC 14.3.1 | 16.13.0 | +| 2022-12 | RAN#98 | R5-225939 | 0372 | - | F | TT analysis for positioning test case 15.2.3 | 16.14.0 | +| 2022-12 | RAN#98 | R5-225940 | 0373 | - | F | TT analysis for positioning test case 15.2.4 | 16.14.0 | +| 2022-12 | RAN#98 | R5-225941 | 0374 | - | F | TT analysis for positioning test case 15.3.1 | 16.14.0 | +| 2022-12 | RAN#98 | R5-225942 | 0375 | - | F | TT analysis for positioning test case 15.3.2 | 16.14.0 | +| 2022-12 | RAN#98 | R5-226101 | 0378 | - | F | PC1 MU - definition for Frequency error in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-226213 | 0408 | - | F | TT analysis for Interruption TCs | 16.14.0 | +| 2022-12 | RAN#98 | R5-226214 | 0409 | - | F | TT analysis for SCell activation TCs | 16.14.0 | +| 2022-12 | RAN#98 | R5-226375 | 0410 | - | F | Test tolerance analysis for FR2 RRC-based DL active BWP switch | 16.14.0 | +| 2022-12 | RAN#98 | R5-226534 | 0438 | - | F | Update of MU for PC1 Demod | 16.14.0 | +| 2022-12 | RAN#98 | R5-226642 | 0439 | - | F | Capturing simulation results to derive the maximum testable SNR | 16.14.0 | +| 2022-12 | RAN#98 | R5-227646 | 0440 | 2 | F | PC1 update to Demod SNR range calculator | 16.14.0 | +| 2022-12 | RAN#98 | R5-227821 | 0437 | 1 | F | Update of MU for PC1 RRM | 16.14.0 | +| 2022-12 | RAN#98 | R5-227822 | 0447 | 1 | F | 40cm QoQZ and XPD MU in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227841 | 0448 | 1 | F | Test Tolerances for FR2 SRS-RSRP measurement in non-DRX | 16.14.0 | +| 2022-12 | RAN#98 | R5-227842 | 0449 | 1 | F | Test Tolerances for EN-DC FR2 SRS-RSRP measurement accuracy | 16.14.0 | +| 2022-12 | RAN#98 | R5-227869 | 0441 | 1 | F | Addition of TT analysis for 7.5.2.1 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227967 | 0376 | 1 | F | PC1 MU - definition for ACLR in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227968 | 0377 | 1 | F | PC1 MU - definition for ACS in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227969 | 0380 | 1 | F | PC1 MU - definition for MOP in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227970 | 0382 | 1 | F | PC1 MU - definition for OFF power in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227971 | 0383 | 1 | F | PC1 MU - definition for REFSENS in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227972 | 0384 | 1 | F | PC1 MU - definition for SEM in 38.903 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227973 | 0385 | 1 | F | PC1 MU - General Update in 38.903 section B.2.2 | 16.14.0 | +| 2022-12 | RAN#98 | R5-227974 | 0443 | 1 | F | Test Tolerances for Idle mode CA/DC measurement FR1 test case | 16.14.0 | +| 2022-12 | RAN#98 | R5-227989 | 0442 | 1 | F | Definition of PC1 MU | 16.14.0 | +| 2022-12 | RAN#98 | R5-228009 | 0433 | 1 | F | Update TT analysis for TC 14.2.1 | 16.14.0 | +| 2022-12 | RAN#98 | R5-228010 | 0434 | 1 | F | Update TT analysis for TC 14.3.1 | 16.14.0 | +| 2022-12 | RAN#98 | R5-228011 | 0435 | 1 | F | New TT analysis for TC 14.2.2 | 16.14.0 | +| 2022-12 | RAN#98 | R5-228012 | 0436 | 1 | F | New TT analysis for TC 14.3.2 | 16.14.0 | +| 2022-12 | RAN#98 | R5-226428 | 0420 | - | F | TT analysis for RedCap RRM TC 16.4.1.1 and 16.4.1.2 - Tx timing | 17.0.0 | +| 2022-12 | RAN#98 | R5-226434 | 0426 | - | F | TT analysis for RedCap RRM TC 17.3.2.1.1 - intra reestablish | 17.0.0 | +| 2022-12 | RAN#98 | R5-226435 | 0427 | - | F | TT analysis for RedCap RRM TC 17.3.2.1.2 - inter reestablish | 17.0.0 | +| 2022-12 | RAN#98 | R5-226436 | 0428 | - | F | TT analysis for RedCap RRM TC 17.5.1.1 - OOS non-DRX | 17.0.0 | +| 2022-12 | RAN#98 | R5-226437 | 0429 | - | F | TT analysis for RedCap RRM TC 17.5.1.2 - IS non-DRX | 17.0.0 | +| 2022-12 | RAN#98 | R5-226438 | 0430 | - | F | TT analysis for RedCap RRM TC 17.5.1.4 - IS DRX | 17.0.0 | +| 2022-12 | RAN#98 | R5-226439 | 0431 | - | F | TT analysis for RedCap RRM TC 17.6.1.1 - no gap non-DRX | 17.0.0 | +| 2022-12 | RAN#98 | R5-227846 | 0411 | 1 | F | TT analysis for RedCap RRM TC 16.3.1.8 - inter-RAT HO 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227847 | 0412 | 1 | F | TT analysis for RedCap RRM TC 16.3.1.10 - inter-RAT blind HO 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227848 | 0413 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.1.2 - intra reestablish 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227849 | 0414 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.1.4 - inter reestablish 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227850 | 0415 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.1.6 - no timing reestablish 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227851 | 0416 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.2.2 and 16.3.2.2.4 - 4 step RACH 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227852 | 0417 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.2.6 and 16.3.2.2.8 - 2 step RACH 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227853 | 0418 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.3.2 and 18.2.2.1 - NR redirection 2 Rx | 17.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98 | R5-227854 | 0419 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.3.4 - LTE redirection 2 Rx | 17.0.0 | +| 2022-12 | RAN#98 | R5-227855 | 0421 | 1 | F | TT analysis for RedCap RRM TC 16.5.1.2 - OOS SSB | 17.0.0 | +| 2022-12 | RAN#98 | R5-227856 | 0422 | 1 | F | TT analysis for RedCap RRM TC 16.5.1.4 and 16.5.1.8 - IS SSB | 17.0.0 | +| 2022-12 | RAN#98 | R5-227857 | 0423 | 1 | F | TT analysis for RedCap RRM TC 16.5.2.2 - SSB BFR | 17.0.0 | +| 2022-12 | RAN#98 | R5-227858 | 0424 | 1 | F | TT analysis for RedCap RRM TC 16.6.1.x - intra-freq | 17.0.0 | +| 2022-12 | RAN#98 | R5-227859 | 0425 | 1 | F | TT analysis for RedCap RRM TC 16.6.4.x - SSB L1-RSRP | 17.0.0 | +| 2022-12 | RAN#98 | R5-227860 | 0432 | 1 | F | TT analysis for RedCap RRM TC 18.2.1.1 - L2N HO | 17.0.0 | +| 2023-03 | RAN#99 | R5-230030 | 0450 | - | F | TT analysis for positioning test case 14.2.3 | 17.1.0 | +| 2023-03 | RAN#99 | R5-230031 | 0451 | - | F | TT analysis for positioning test case 14.2.4 | 17.1.0 | +| 2023-03 | RAN#99 | R5-230033 | 0453 | - | F | TT analysis for positioning test case 14.3.4 | 17.1.0 | +| 2023-03 | RAN#99 | R5-230034 | 0454 | - | F | TT analysis for positioning test case 16.2.3 | 17.1.0 | +| 2023-03 | RAN#99 | R5-230180 | 0465 | - | F | PC5 MU - definition for REFSSENS test case in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-230430 | 0469 | - | F | Addition of test tolerance analysis for 5.5.3.1 EN-DC FR2 SCell activation and deactivation intra-band in non-DRX | 17.1.0 | +| 2023-03 | RAN#99 | R5-230434 | 0471 | - | F | Addition of test tolerance analysis for 8.4.2.6 and 8.4.2.7 and 8.4.2.8 NR Inter-RAT event triggered reporting tests for FR2 test cases | 17.1.0 | +| 2023-03 | RAN#99 | R5-230517 | 0473 | - | F | TT analysis for RedCap RRM TC 16.3.1.4 - intra unknown HO 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230518 | 0474 | - | F | TT analysis for RedCap RRM TC 16.3.1.6 - inter unknown HO 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230519 | 0475 | - | F | TT analysis for RedCap RRM TC 16.4.3.1 and 16.4.3.2 - TA | 17.1.0 | +| 2023-03 | RAN#99 | R5-230520 | 0476 | - | F | TT analysis for RedCap RRM TC 16.5.1.10 and 16.5.1.14 - OOS 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230521 | 0477 | - | F | TT analysis for RedCap RRM TC 16.5.1.12 and 16.5.1.16 - IS 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230522 | 0478 | - | F | TT analysis for RedCap RRM TC 16.5.2.6 and 16.5.2.8 - BFR 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230523 | 0479 | - | F | TT analysis for RedCap RRM TC 16.6.1.x - intra meas 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230524 | 0480 | - | F | TT analysis for RedCap RRM TC 16.6.4.6 and 16.6.4.8 - CSI-RS L1-RSRP 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-230525 | 0481 | - | F | TT analysis for RedCap RRM TC 18.3.1.x - FR1 NR meas | 17.1.0 | +| 2023-03 | RAN#99 | R5-230531 | 0482 | - | F | TT analysis for RRM enhancement TC 6.5.8.1 - CBW change | 17.1.0 | +| 2023-03 | RAN#99 | R5-230925 | 0491 | - | F | New TT analysis for TC 4A.1.1.1 | 17.1.0 | +| 2023-03 | RAN#99 | R5-230926 | 0492 | - | F | New TT analysis for TC 4A.2.1.1 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231138 | 0494 | - | F | TT analysis for RedCap RRM TC 16.1.1.4 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231139 | 0495 | - | F | TT analysis for RedCap RRM TC 16.1.1.6 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231140 | 0496 | - | F | TT analysis for RedCap RRM TC 16.1.1.8 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231141 | 0497 | - | F | TT analysis for RedCap RRM TC 16.1.2.2 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231142 | 0498 | - | F | TT analysis for RedCap RRM TC 16.1.2.4 and 16.1.2.6 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231147 | 0499 | - | F | TT analysis for Idle mode Inter-RAT CA/DC measurement test case 6.6.15.1 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231148 | 0500 | - | F | TT analysis for E-UTRA - NR Early Measurement Reporting for NR in FR1 test case 8.2.2.1 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231345 | 0502 | - | F | Max testable SNR table updates | 17.1.0 | +| 2023-03 | RAN#99 | R5-231745 | 0501 | 1 | F | TT analysis for E-UTRA - NR Early Measurement Reporting for NR in FR2 test case 8.2.2.2 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231756 | 0452 | 1 | F | TT analysis for positioning test case 14.3.3 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231757 | 0455 | 1 | F | TT analysis for positioning test case 16.2.4 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231758 | 0490 | 1 | F | Update TT analysis for TC 14.3.2 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231762 | 0472 | 1 | F | TT analysis for RedCap RRM TC 16.3.1.2 - intra known HO 2Rx | 17.1.0 | +| 2023-03 | RAN#99 | R5-231763 | 0493 | 1 | F | TT analysis for RedCap RRM TC 16.1.1.2 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231765 | 0487 | 1 | F | Addition of TT analysis for 7.3.1.2 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231766 | 0488 | 1 | F | Addition of TT analysis for 7.3.1.3 and 7.3.2.3.1 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231784 | 0457 | 1 | F | PC1 MU - definition for ACLR test case in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231785 | 0459 | 1 | F | PC1 MU - definition for MOP test cases in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231786 | 0461 | 1 | F | PC1 MU - definition for REFSSENS test case in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231787 | 0463 | 1 | F | PC1 MU - definition for Tx spurious test cases in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231788 | 0466 | 1 | F | Definition of PC1 MU | 17.1.0 | +| 2023-03 | RAN#99 | R5-231844 | 0460 | 1 | F | PC1 MU - definition for MPR test case in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231849 | 0458 | 1 | F | PC1 MU - definition for Min power test case in 38.903 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231850 | 0464 | 1 | F | PC1 MU - General Update in 38.903 test case section B.2.2 | 17.1.0 | +| 2023-03 | RAN#99 | R5-231899 | 0470 | 1 | F | Addition of test tolerance analysis for 8.4.2.5 NR Inter-RAT event triggered reporting tests for FR2 test cases | 17.1.0 | +| 2023-03 | RAN#99 | R5-231966 | 0467 | 1 | F | Update of the uncertainty of the network analyzer | 17.1.0 | +| 2023-03 | RAN#99 | R5-231968 | 0468 | 1 | F | Update of PC1 MU | 17.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-06 | RAN#100 | R5-232078 | 0503 | - | F | TT analysis for positioning test case 16.3.2 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232164 | 0508 | - | F | PC1 MU - definition for ACS Case 1 and IBB test cases in 38.903 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232308 | 0513 | - | F | Update of Test Tolerance analyses for EN-DC FR2 RLM tests for PSCell configured with CSI-RS-based RLM RS | 17.2.0 | +| 2023-06 | RAN#100 | R5-232427 | 0514 | - | F | TT analysis for TC 16.2.1 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232428 | 0515 | - | F | TT analysis for TC 16.2.2 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232429 | 0516 | - | F | TT analysis for TC 16.3.1 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232483 | 0517 | - | F | TT analysis for RedCap RRM TC 17.6.1.2 and 17.6.1.4 intraFreq one AoA | 17.2.0 | +| 2023-06 | RAN#100 | R5-232484 | 0518 | - | F | TT analysis for RedCap RRM TC 17.6.1.3 intraFreq two AoAs | 17.2.0 | +| 2023-06 | RAN#100 | R5-232485 | 0519 | - | F | TT analysis for RedCap RRM TC 17.6.3.1 and 17.6.3.2 SSB L1RSRP | 17.2.0 | +| 2023-06 | RAN#100 | R5-232486 | 0520 | - | F | TT analysis for RedCap RRM TC 17.6.3.3 and 17.6.3.4 CSIRS L1RSRP | 17.2.0 | +| 2023-06 | RAN#100 | R5-232487 | 0521 | - | F | TT analysis for RedCap RRM TC 18.3.1.5 interRAT nonPeak | 17.2.0 | +| 2023-06 | RAN#100 | R5-232488 | 0522 | - | F | TT analysis for RedCap RRM TC 18.3.1.x interRAT peak | 17.2.0 | +| 2023-06 | RAN#100 | R5-232561 | 0523 | - | F | Test Tolerance analysis of FR1 PDC test cases | 17.2.0 | +| 2023-06 | RAN#100 | R5-232566 | 0524 | - | F | Test Tolerance analysis of FR2 PDC test cases | 17.2.0 | +| 2023-06 | RAN#100 | R5-232631 | 0525 | - | F | Removal of Offsets in B.18 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232657 | 0526 | - | F | Addition of TT analysis for 4.6.5.1 and 6.6.6.1 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232676 | 0529 | - | F | Addition of TT analysis for test cases 6.6.3.1 and 6.6.3.2 | 17.2.0 | +| 2023-06 | RAN#100 | R5-232757 | 0530 | - | F | Correction to test tolerance analysis for 5.6.6.1 and 7.6.6.1 | 17.2.0 | +| 2023-06 | RAN#100 | R5-233299 | 0538 | - | F | Addition of TT analysis for NR SA FR2 BFD and BFR for RedCap | 17.2.0 | +| 2023-06 | RAN#100 | R5-233632 | 0505 | 1 | F | PC5 MU - definition for MOP test cases in 38.903 | 17.2.0 | +| 2023-06 | RAN#100 | R5-233633 | 0535 | 1 | F | Updating for PC6 measurement error contribution descriptions for IFF | 17.2.0 | +| 2023-06 | RAN#100 | R5-233639 | 0506 | 1 | F | FR2 MUs - General Update in 38.903 section B.2.2 | 17.2.0 | +| 2023-06 | RAN#100 | R5-233640 | 0509 | 1 | F | FR2 PC3 - Network Analyzer MU update in 38.903 | 17.2.0 | +| 2023-06 | RAN#100 | R5-233646 | 0527 | 1 | F | Addition of TT analysis for 4.7.6.1 and 6.7.8.1 | 17.2.0 | +| 2023-06 | RAN#100 | R5-233653 | 0511 | 1 | F | Grouping of test tolerance analysis for test Case 5.5.3.7 with 5.5.3.1 | 17.2.0 | +| 2023-06 | RAN#100 | R5-233659 | 0534 | 1 | F | Test Tolerance analysis for HST event triggered test cases | 17.2.0 | +| 2023-06 | RAN#100 | R5-233664 | 0504 | 1 | F | TT analysis for FR2 UE UL carrier RRC reconfiguration delay test case | 17.2.0 | +| 2023-06 | RAN#100 | R5-233695 | 0537 | 1 | F | Editorial correction to Annex B | 17.2.0 | +| 2023-06 | RAN#100 | R5-233750 | 0510 | 1 | F | Addition of test tolerance analysis for test Case of 4.5.3.5 EN-DC FR1 direct SCell activation and test Case of 6.5.3.4 NR SA FR1 direct SCell activation | 17.2.0 | +| 2023-09 | RAN#101 | R5-233966 | 0542 | - | F | TT analysis for RRM test case 7.5.3.3 - SCell Activation and deactivation for SCell in FR2 inter-band in non-DR | 17.3.0 | +| 2023-09 | RAN#101 | R5-233968 | 0543 | - | F | Correction to Grouping of FR2 test case 7.5.11.1 | 17.3.0 | +| 2023-09 | RAN#101 | R5-233977 | 0545 | - | F | PC5 MU definition in 38.903 | 17.3.0 | +| 2023-09 | RAN#101 | R5-233982 | 0547 | - | F | Editorial correction Network Analyzer FR2 MU | 17.3.0 | +| 2023-09 | RAN#101 | R5-234221 | 0548 | - | F | Addition of missing group information for TS 37.571-1 UE Rx-Tx time difference positioning test cases | 17.3.0 | +| 2023-09 | RAN#101 | R5-234339 | 0550 | - | F | Test Tolerance analysis for FR2 PDC test case | 17.3.0 | +| 2023-09 | RAN#101 | R5-234345 | 0551 | - | F | Addition of test tolerance analysis for test Case of 6.5.3.5 NR SA FR1 direct SCell activation at handover | 17.3.0 | +| 2023-09 | RAN#101 | R5-234346 | 0552 | - | F | Addition of test tolerance analysis for test Case of 7.5.3.4 NR SA FR2 direct SCell activation | 17.3.0 | +| 2023-09 | RAN#101 | R5-234347 | 0553 | - | F | Addition of test tolerance analysis for test Case of 7.5.3.5 NR SA FR2 direct SCell activation at handover | 17.3.0 | +| 2023-09 | RAN#101 | R5-234349 | 0554 | - | F | Test Tolerances for NR SA FR1 DL interruptions at switching between two uplink carriers for 6.5.7A.2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234350 | 0555 | - | F | Test Tolerances for NR SA FR1 DL interruptions at switching between two uplink bands for 6.5.7B.2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234387 | 0556 | - | F | Update of Test Tolerance analysis for non-DRX SSB-based RLM In-sync tests in FR2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234389 | 0557 | - | F | Update of Test Tolerance analyses for non-DRX CSI-RS-based RLM In-sync tests in FR2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234421 | 0561 | - | F | TT analysis for RedCap RRM TC 16.5.1.x_RLM IS 1Rx | 17.3.0 | +| 2023-09 | RAN#101 | R5-234422 | 0562 | - | F | TT analysis for RedCap RRM TC 16.5.1.x_RLM OOS 1Rx | 17.3.0 | +| 2023-09 | RAN#101 | R5-234423 | 0563 | - | F | TT analysis for RedCap RRM TC 16.6.1.x_intraFreq 1Rx | 17.3.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-09 | RAN#101 | R5-234424 | 0564 | - | F | TT analysis for RedCap RRM TC 16.6.4.1 and 16.6.4.3_SSB L1 RSRP 1Rx | 17.3.0 | +| 2023-09 | RAN#101 | R5-234651 | 0567 | - | F | Addition of TT analysis for test case 5.5.1.10 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234663 | 0568 | - | F | Addition of TTs for RedCap RLM OOS test cases 16.5.1.5 and 16.5.1.6 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234665 | 0569 | - | F | Addition of TTs for RedCap BFR test case 16.5.2.4 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234666 | 0570 | - | F | Addition of TTs for RedCap BFR test cases 16.5.2.3 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234668 | 0571 | - | F | Addition of TTs for RedCap BWP Switch test cases 16.5.3.1.1 and 16.5.3.1.2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234669 | 0572 | - | F | Addition of TTs for RedCap BWP Switch test cases 16.5.3.2.1 and 16.5.3.2.2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234670 | 0573 | - | F | Update to TT analysis for L2N latency test cases 8.4.2.x and 18.3.1.x | 17.3.0 | +| 2023-09 | RAN#101 | R5-234678 | 0574 | - | F | Addition of TT analysis for TCI state switch test cases 7.5.8.1.1 and 7.5.8.2.1 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234882 | 0576 | - | F | Addition of TT analysis for FeMIMO RRM TC 4.5.5.8 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234966 | 0582 | - | F | Test Tolerance for NR SA FR1 Cell reselection RedCap test case 16.1.1.5 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234967 | 0583 | - | F | Test Tolerance for NR SA FR1 Cell reselection RedCap test case 16.1.1.7 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234969 | 0585 | - | F | Test Tolerance for NR - E-UTRA FR1 Cell reselection RedCap test cases 16.1.2.3 | 17.3.0 | +| 2023-09 | RAN#101 | R5-234970 | 0586 | - | F | Test Tolerance for NR - E-UTRA FR1 Cell reselection RedCap test case 16.1.2.5 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235103 | 0587 | - | F | TT analysis for FR1 Power saving Enh test cases 4.5.1.9 and 6.5.1.9 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235104 | 0588 | - | F | TT analysis for FR2 Power saving Enh test case 5.5.5.9 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235461 | 0577 | 2 | F | Addition of TT analysis for FeMIMO RRM TC 5.5.5.8& 7.5.5.9 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235462 | 0579 | 2 | F | Addition of TT analysis for FeMIMO RRM TC 7.5.5.10 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235467 | 0549 | 2 | F | Update to Demod SNR calculator for Agg BW up to 400MHz | 17.3.0 | +| 2023-09 | RAN#101 | R5-235731 | 0560 | 1 | F | TT analysis for RedCap RRM TC 16.3.1.x_intra and inter freq HO 1Rx | 17.3.0 | +| 2023-09 | RAN#101 | R5-235732 | 0565 | 1 | F | TT analysis for RedCap RRM TC 16.6.4.5 and 16.6.4.7_CSIRS L1 RSRP 1Rx | 17.3.0 | +| 2023-09 | RAN#101 | R5-235736 | 0589 | 1 | F | Addition of TT analysis grouping for test cases 5.5.9.1.1 and 7.5.9.1.1 to Table 8-2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235737 | 0590 | 1 | F | Addition of TT analysis grouping for test cases 5.5.9.2.1 and 7.5.9.2.1 to Table 8-2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235740 | 0540 | 1 | F | Addition of TT analysis for gap enhancement RRM test cases 6.6.18.1 and 6.6.18.2 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235743 | 0566 | 1 | F | TT analysis for FR1 L1 RSRP relative accuracy TCs | 17.3.0 | +| 2023-09 | RAN#101 | R5-235751 | 0544 | 1 | F | FR2c MU definition in 38.903 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235920 | 0584 | 1 | F | Test Tolerance for NR - E-UTRA FR1 Cell reselection RedCap test case 16.1.2.1 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235921 | 0581 | 1 | F | Test Tolerance for NR SA FR1 Cell reselection RedCap test case 16.1.1.3 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235923 | 0575 | 1 | F | Addition of TT analysis for FeMIMO RRM TC 4.5.5.7 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235925 | 0578 | 1 | F | Addition of TT analysis for FeMIMO RRM TC 6.5.5.7 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235930 | 0541 | 1 | F | Addition of TT analysis for NCSG RRM test cases 6.6.19.1,6.6.19.2, 6.6.19.3 and 6.6.19.4 | 17.3.0 | +| 2023-09 | RAN#101 | R5-235931 | 0539 | 1 | F | Addition of TT analysis for MG_enh RRM test cases 6.6.17.1 and 6.6.17.2 | 17.3.0 | +| 2023-09 | RAN#101 | - | - | - | - | Administrative release upgrade to match the release of 3GPP TS 38.521-3 and TS 38.522 which were upgraded at RAN#101 to Rel-18 due to Rel-18 relevant CR(s) | 18.0.0 | +| 2023-12 | RAN#102 | R5-236062 | 0598 | - | F | PC5 MU - ACS Case 1 and IBB update in 38.903 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236214 | 0602 | - | F | Addition of Test Tolerances analysis for TC 6.5.7C.1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236215 | 0603 | - | F | Addition of Test Tolerances analysis for TC 6.5.7C.2 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236221 | 0604 | - | F | Addition of test tolerances analysis for RedCap CGI identification test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236223 | 0605 | - | F | Addition of Test Tolerances analysis for TC 7.6.3.6 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236224 | 0606 | - | F | Addition of test tolerance analysis for fast SCell activation test cases of 4.5.3.6, 4.5.3.7, 6.5.3.10, 6.5.3.11 | 18.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-12 | RAN#102 | R5-236225 | 0607 | - | F | Addition of test tolerance analysis for CPAC test cases of 4.5.11.1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236226 | 0608 | - | F | Addition of test tolerance analysis for fast SCell activation test cases of 5.5.3.8 and 7.5.3.13 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236250 | 0609 | - | F | Removal of technical content in TR 38.903 v17.3.0 and substitution with pointer to the next Release | 18.1.0 | +| 2023-12 | RAN#102 | R5-236391 | 0611 | - | F | Addition of test tolerance analysis for 4.5.2.10 EN-DC FR1 interruptions due to RRM and RLM/BFD measurements on deactivated NR PSCell | 18.1.0 | +| 2023-12 | RAN#102 | R5-236393 | 0612 | - | F | Addition of test tolerance analysis for 4.5.10.1 EN-DC FR1 PSCell activation and deactivation delay | 18.1.0 | +| 2023-12 | RAN#102 | R5-236395 | 0613 | - | F | Addition of test tolerance analysis for 5.5.12.1 EN-DC FR2 PSCell activation and deactivation delay | 18.1.0 | +| 2023-12 | RAN#102 | R5-236740 | 0615 | - | F | TT analysis for RedCap RRM TC 16.3.1.9 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236741 | 0616 | - | F | TT analysis for RedCap RRM TC 16.3.2.1.1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236742 | 0617 | - | F | TT analysis for RedCap RRM TC 16.3.2.1.3 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236743 | 0618 | - | F | TT analysis for RedCap RRM TC 16.3.2.1.5 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236745 | 0620 | - | F | TT analysis for RedCap RRM TC 16.3.2.3.1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236746 | 0621 | - | F | TT analysis for RedCap RRM TC 16.3.2.3.3 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236747 | 0622 | - | F | TT analysis for RedCap RRM TC 16.5.2.x | 18.1.0 | +| 2023-12 | RAN#102 | R5-236792 | 0624 | - | F | Editorial correction for MU tables | 18.1.0 | +| 2023-12 | RAN#102 | R5-236872 | 0627 | - | F | Addition of test tolerance analysis for Conditional PSCell Addition FR2 test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236873 | 0628 | - | F | Addition of test tolerance analysis for 7.5.14 PSCell activation | 18.1.0 | +| 2023-12 | RAN#102 | R5-236989 | 0630 | - | F | Test Tolerance for NR SA FR1 2Rx event triggered measurement RedCap test cases 16.6.2.x | 18.1.0 | +| 2023-12 | RAN#102 | R5-236991 | 0632 | - | F | Test Tolerance analysis correction for FR2 Inter-freq accuracy measurement test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237013 | 0633 | - | F | Correction of UE gain parameters | 18.1.0 | +| 2023-12 | RAN#102 | R5-237734 | 0599 | 1 | F | FR2c MU definition in 38.903 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237735 | 0623 | 1 | F | Update for FR2c MU | 18.1.0 | +| 2023-12 | RAN#102 | R5-237736 | 0639 | 1 | F | Update of MU for FR2 UL MIMO | 18.1.0 | +| 2023-12 | RAN#102 | R5-237791 | 0629 | 1 | F | Test Tolerance for NR SA FR1 Cell reselection RedCap test case 16.1.1.1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237792 | 0631 | 1 | F | Test Tolerance for NR SA FR1 1Rx event triggered measurement RedCap test cases 16.6.2.x | 18.1.0 | +| 2023-12 | RAN#102 | R5-237796 | 0591 | 1 | F | Addition of TT analysis for positioning test case 14.2.8 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237797 | 0592 | 1 | F | Addition of TT analysis for positioning test case 14.2.9 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237798 | 0593 | 1 | F | Addition of TT analysis for positioning test case 14.2.10 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237799 | 0594 | 1 | F | Addition of TT analysis for positioning test case 14.3.7 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237800 | 0595 | 1 | F | Addition of TT analysis for positioning test case 14.3.8 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237801 | 0596 | 1 | F | Addition of TT analysis for positioning test case 15.3.5 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237802 | 0597 | 1 | F | Addition of TT analysis for positioning test case 15.3.6 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237812 | 0635 | 1 | F | Addition of TTs for test case 7.5.1.5 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237813 | 0636 | 1 | F | Addition of TTs for test case 7.5.1.6 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237814 | 0637 | 1 | F | Addition of TTs for test case 7.5.1.7 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237815 | 0638 | 1 | F | Addition of TTs for test case 7.5.1.8 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237928 | 0614 | 1 | F | TT analysis for RedCap RRM TC 16.3.1.7 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237929 | 0619 | 1 | F | TT analysis for RedCap RRM TC 16.3.2.2.x | 18.1.0 | +| 2023-12 | RAN#102 | R5-237952 | 0610 | 1 | F | MU and TT analysis for unified TCI state switching | 18.1.0 | +| 2023-12 | RAN#102 | R5-237956 | 0626 | 1 | F | Addition of test tolerance analysis for 7.5.3.14 Fast SCell activation | 18.1.0 | +| 2023-12 | RAN#102 | R5-237961 | 0634 | 1 | F | Addition of TTs for test case 6.2.1 | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38905/390120de4fe440c42fea8154fcaad334_img.jpg b/marked/Rel-18/38_series/38905/390120de4fe440c42fea8154fcaad334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4c6d747fe9d3c1d3029e4a7003df9e60ca98870 --- /dev/null +++ b/marked/Rel-18/38_series/38905/390120de4fe440c42fea8154fcaad334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a8a822226ad39a1a85669194e4a8b1774d9a503634d170882c66109236243a9 +size 9462 diff --git a/marked/Rel-18/38_series/38905/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38905/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eab79bf6d7b443a528fe0c0e801aa02e2e255b53 --- /dev/null +++ b/marked/Rel-18/38_series/38905/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b5fda866627c7cfd94a423da6f6d5460b13aa1be14c160f92decfdc45d3541d +size 5939 diff --git a/marked/Rel-18/38_series/38905/raw.md b/marked/Rel-18/38_series/38905/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b7d57daedded4027d5cabac4cc149037293c77d6 --- /dev/null +++ b/marked/Rel-18/38_series/38905/raw.md @@ -0,0 +1,3173 @@ + + +# 3GPP TR 38.905 V18.1.0 (2023-12) --- + +*Technical Specification* + +**3rd Generation Partnership Project; +Technical Specification Group Radio Access Network; +NR;** + +**Derivation of test points for radio transmission and reception +User Equipment (UE) conformance test cases +(Release 18)** + +--- + +![5G logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](390120de4fe440c42fea8154fcaad334_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text are three red curved lines representing signal waves. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## --- **Keywords** + +--- + +RAN, 5G, NR + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Test coverage analysis ..... | 7 | +| 4.1 Test point analysis for FR1 test cases in TS 38.521-1 ..... | 8 | +| 4.1.1 Test point analysis per test case..... | 8 | +| 4.1.1.1 FR1 single carrier, NR CA and UL MIMO test cases ..... | 8 | +| 4.1.1.2 FR1 SUL test cases ..... | 15 | +| 4.1.1.3 FR1 V2X test cases..... | 17 | +| 4.1.1.4 FR1 RedCap test cases..... | 17 | +| 4.1.1.5 FR1 TxD test cases ..... | 17 | +| 4.1.1.6 FR1 shared spectrum channel access test cases..... | 18 | +| 4.1.1.7 FR1 CA with UL MIMO test cases ..... | 19 | +| 4.1.2 Test point analysis per NS value ..... | 20 | +| 4.1.2.1 A-MPR, A-SEM and A-SE FR1 test cases for single carrier and UL MIMO..... | 20 | +| 4.1.2.2 A-MPR test cases for FR1 UL CA ..... | 22 | +| 4.1.3 Test point analysis per NR CA configuration ..... | 23 | +| 4.1.3.2 Spurious emissions test cases for FR1 UL CA ..... | 31 | +| 4.2 Test point analysis for FR2 test cases in TS 38.521-2 ..... | 32 | +| 4.2.2 Test point analysis per NS value ..... | 35 | +| 4.2.2.1 A-MPR and A-SE FR2 test cases for single carrier..... | 35 | +| 4.2.2.2 A-MPR and A-SE FR2 test cases for CA ..... | 36 | +| 4.2.3 Test point analysis per NR CA configuration ..... | 36 | +| 4.2.3.1 Reference Sensitivity test cases for FR2 NR CA ..... | 36 | +| 4.3 Test point analysis for test cases in TS 38.521-3 ..... | 37 | +| 4.3.1 Test point analysis per test case..... | 37 | +| 4.3.1.1 EN-DC test cases ..... | 37 | +| 4.3.1.2 V2X test cases..... | 40 | +| 4.3.2 Test point analysis per NS value ..... | 40 | +| 4.3.2.1 A-MPR and A-SE test cases for EN-DC ..... | 40 | +| 4.3.3 Test point analysis per EN-DC configuration ..... | 40 | +| 4.3.3.1 Reference sensitivity test cases for EN-DC ..... | 40 | +| 4.3.3.2 Spurious emissions test cases for EN-DC..... | 52 | +| 4.4 Test point analysis for satellite access test cases in TS 38.521-5 ..... | 54 | + +| | | +|------------------------------------------------------------------------------------------------------|-----------| +| Annex A: Derivation documents..... | 57 | +| Annex B: Principles for test point selection for NR CA reference sensitivity test cases..... | 57 | +| B.1 General..... | 57 | +| B.2 Test case structure..... | 58 | +| B.3 Test Environment..... | 59 | +| B.4 Test Frequencies selection ..... | 59 | +| B.4A Frequency relation for exception requirements ..... | 59 | +| B.5 Test Channel Bandwidth selection..... | 60 | +| B.6 Modulation selections ..... | 60 | +| B.7 Examples..... | 60 | +| B.8 Current test completion status per CA configuration..... | 61 | +| B.9 Reference Sensitivity checklist for CA..... | 61 | +| B.9.1 Checklist for two bands..... | 61 | +| B.9.2 Checklist for three bands..... | 62 | +| B.9.3 Checklist for four bands and five bands..... | 62 | +| Annex C: Principles for test point selection for FR2 NR CA reference sensitivity test cases..... | 62 | +| Annex D: Principles for test point selection for EN-DC reference sensitivity test cases ..... | 62 | +| D.1 General..... | 62 | +| D.2 Requirements ..... | 63 | +| D.2.1 Defined EN-DC configurations..... | 63 | +| D.2.2 Definition of exception requirements..... | 63 | +| D.2.3 Reference sensitivity ..... | 64 | +| D.2.4 Rx requirements other than reference sensitivity..... | 65 | +| D.2.5 Test case structure and test coverage ..... | 65 | +| D.2.6 EN-DC configurations to test..... | 66 | +| D.2.6.1 Lower order fallbacks..... | 66 | +| D.2.6.2 EN-DC configurations requiring testing and max number of CCs ..... | 67 | +| D.2.6.3 Test coverage..... | 67 | +| D.2.7 Test Environment..... | 71 | +| D.2.8 Test Frequencies selections for EN-DC ..... | 71 | +| D.2.9 Test EN-DC channel bandwidth ..... | 71 | +| D.2.9.1 Test point selection EN-DC configuration without exception ..... | 71 | +| D.2.9.2 Test point selection EN-DC configuration with exception ..... | 71 | +| D.2.10 RB allocation and RB location selections..... | 72 | +| D.2.10.1 Test point selection EN-DC configuration without exception ..... | 72 | +| D.2.10.2 Test point selection EN-DC configuration with exception when exception applies ..... | 72 | +| D.2.10.3 Test point selection EN-DC configuration with exception when exception does not apply ..... | 72 | +| D.2.11 Modulation scheme selections..... | 72 | +| D.2.12 Current test completion status per EN-DC configuration ..... | 73 | +| Annex E: Change history..... | 74 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document specifies and contains the derivation of Test Points for NR RF test cases, thereby 3GPP TSG RAN WG5 will have a way of storing the input contributions provided. The test cases are described in TS38.521-1[2], TS38.521-2[3] and TS38.521-3[4], + +The test cases which have been analysed to determine Test Points are included as .zip files. + +The present document is applicable from Release 15 up to the release indicated on the front page of the present Terminal conformance specifications. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.521-1: "NR; UE conformance specification; Radio transmission and reception; Part 1: NR range 1". +- [3] 3GPP TS 38.521-2: "NR; UE conformance specification; Radio transmission and reception; Part 2: NR range 2". +- [4] 3GPP TS 38.521-3: "NR; UE conformance specification; Radio transmission and reception; Part 3: NR interworking between NR range1 + NR range2 and between NR and LTE". +- [5] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [6] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [7] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- [8] 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [9] R5-206841: "Discussion on test points in Receiver test cases for EN-DC configurations with exception requirements". +- [10] 3GPP TS 38.521-5: "NR; UE conformance specification; Radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +Other definitions used in the present document are listed in 3GPP TS 38.521-1 [2], 3GPP TS 38.521-2 [3] or 3GPP TS 38.521-3 [4]. + +*Editor's note: intended to capture definitions* + +## 3.2 Symbols + +Symbols used in the present document are listed in 3GPP TR 21.905 [1], 3GPP TS 38.521-1 [2], 3GPP TS 38.521-2 [3] or 3GPP TS 38.521-3 [4]. + +*Editor's note: intended to capture definitions* + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +Other abbreviations used in the present document are listed in 3GPP TS 38.521-1 [2], or 3GPP, 3GPP TS 38.521-1 [2], 3GPP TS 38.521-2 [3] or 3GPP TS 38.521-3 [4]. + +| | | +|-------|-------------------------------| +| A-SE | Additional spurious emissions | +| A-SEM | Spectrum Emission Mask | + +# --- 4 Test coverage analysis + +This clause contains information on test point analysis and test point selection for RX and TX test configuration tables in [2], [3] and [4]. The test point analysis should include selection of: + +- Test environment +- Test frequencies +- Test channel bandwidth +- Test Subcarrier Spacing (SCS) +- Downlink configuration including modulation and RB allocation +- Uplink configuration including modulation and RB allocation +- Number of test points + +## 4.1 Test point analysis for FR1 test cases in TS 38.521-1 + +### 4.1.1 Test point analysis per test case + +#### 4.1.1.1 FR1 single carrier, NR CA and UL MIMO test cases + +This clause contains information on test point analysis and test point selection for single carrier, NR CA and UL MIMO test cases in [2] clause 6 and 7 with information about transmitting test point selection for FR1 listed in table 4.1.1.1-1 and receiver test point selection in table 4.1.1.1-2. + +Table 4.1.1.1-1: NR UE transmitter test point selection for FR1 + +| Subclause | Number of test points | Justification in attachment | Comments | +|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|---------------------| +| 6.2.1 UE maximum output power | 540 | "38.521-1_TPanalysis_6.2.1_MaxOP_v3.zip" | RAN5#89-e | +| 6.2.2 Maximum Output Power Reduction (MPR) | contiguous allocation: 920 (1040 1 , 1000 2,3 ) almost contiguous allocation: 120 | "38.521-1_TPanalysis_6.2.2_MPR_6.5.2.2_SEM_6.5.2.4.1_N_R_ACLR_v5.zip" | RAN5#99 | +| 6.2.3 UE A-MPR | See clause 4.1.2.1 | See clause 4.1.2.1 | See clause 4.1.2.1 | +| 6.2.4 Configured Transmitted Power | 30 | "38.521-1_TPanalysis_6.2.4_ConfigTP_v1.zip" | RAN5#91-e | +| 6.2A.1.1 UE maximum output power for CA (2UL CA) | 240 | "38.521-1_TPanalysis_6.2A.1_MOP" | RAN5#83 | +| 6.2A.2.1 Maximum power reduction (MPR) for CA (2UL CA) | For inter-band CA:1480
For intra-band contiguous CA: 720 (contiguous RB allocation) 1080 (non-contiguous RB allocation)
For intra-band non-contiguous CA: 2880 | "38.521-1_TPanalysis_6.2A.2_MPR_6.5A.2.4.1_ACLR_6.5A.2.2.1_SEM" | RAN5#98 | +| 6.2A.4 Configured transmitted power for CA | Inter-band CA:20
Intra-band contiguous CA: 20
Intra-band non-contiguous CA:20 | "38.521-1_TPanalysis_6.2A.4_ConfigTP_v2.zip" | RAN5#101 | +| 6.2C.1 Configured UE transmitted Output Power | 270 | "38.521-1_TPanalysis_6.2C.1_ConfigOPSUL.zip" | RAN5#80 | +| 6.2D.1 UE maximum output power for UL-MIMO | UL MIMO with ULFPTx: 540
UL MIMO with 2-layer: 0 | "38.521-1_TPanalysis_6.2.1_MaxOP_v3.zip" | RAN5#89-e | +| 6.2D.2 Maximum Power Reduction (MPR) for UL MIMO | UL MIMO with 2-layer: 400
UL MIMO with ULFPTx: 920 | "38.521-1_TPanalysis_6.2.2_MPR_6.5.2.2_SEM_6.5.2.4.1_N_R_ACLR_v5.zip" | RAN5#99 | +| 6.2D.3 UE additional maximum output power reduction for UL-MIMO | Table 4.1.2.1-1 | Table 4.1.2.1-1 | See Table 4.1.2.1-1 | +| 6.2D.4 Configured Transmitted Power for UL-MIMO | 15 | "38.521-1_TPanalysis_6.2.4_ConfigTP_v1.zip" | RAN5#91-e | +| 6.3.1 Minimum output power | 45 | "38.521-1_TPanalysis_6.3.1_MinOP_v3.zip" | RAN5#5-5G-NR Adhoc | +| 6.3.3.2 General ON/OFF time mask | 180 | "38.521-1_TPanalysis_6.3.3.2_OnOff_M_v2.zip" | RAN5#5-5G-NR Adhoc | +| 6.3.3.4 PRACH time mask | | "38.521-1_TPanalysis_6.3.3.4_PRACH.zip" | RAN5#96-e | +| 6.3.3.6 SRS time mask | 30 | "38.521-1_TPanalysis_6.3.3.3_SRS.zip" | RAN5#82 | +| 6.3.4.2 Absolute power tolerance | 6 | "38.521-1_TPanalysis_6.3.4.2_AbsPtol_v2.zip" | RAN5#83 | +| 6.3.4.3 Relative power | TBD | "38.521-1_TPanalysis_6.3.4.3_RelPtol_v2.zip" | RAN5#83 | + +| | | | | +|-------------------------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------|--------------------| +| tolerance | | | | +| 6.3.4.4 Aggregate power tolerance | PUCCH: 6
PUSCH: 6 | "38.521-1_TPAnalysis_6.3.4.4_AggPtol_v2.zip" | RAN5#83 | +| 6.3A.1.1 Minimum output power for CA (2UL CA) | 20 | 38.521-1_TPAnalysis_6.3A.1.1_MinOP_CA_v1.zip | RAN5#101 | +| 6.3A.3.1 Transmit ON/OFF time mask for CA (2UL CA) | 40 | "38.521-1_TPAnalysis_6.3A.3.1_OnOff_M_CA_v1.zip" | RAN5#99 | +| 6.3A.3.2 Time mask for switching between two uplink carriers | 1 | "38.521-1_TPAnalysis_6.3A.3.2_6.3A.3.3_TxSwitch_M.zip" | RAN5#100 | +| 6.3A.3.3 Time mask for switching between two uplink carriers | 1 | "38.521-1_TPAnalysis_6.3A.3.2_6.3A.3.3_TxSwitch_M.zip" | RAN5#100 | +| 6.3A.4.1 Absolute power tolerance for CA (2UL CA) | Intra-band contiguous CA:4
Intra-band non-contiguous CA:2 | "38.521-1_TPAnalysis_6.3A.4.1_Abs_Ptol_CA_v3.zip" | RAN5#95-e | +| 6.3A.4.2 Relative power tolerance for CA (2UL CA) | TBD | "38.521-1_TPAnalysis_6.3A.4.2_Rel_Ptol_CA_v1.zip" | RAN5#92-e | +| 6.3A.4.3 Aggregate power tolerance for CA (2UL CA) | PUCCH:4
PUSCH:4 | "38.521-1_TPAnalysis_6.3A.4.3_Agg_Ptol_CA_v1.zip" | RAN5#92-e | +| 6.3D.1 Minimum output power for UL-MIMO | 45 | "38.521-1_TPAnalysis_6.3.1_MinOP_v3.zip" | RAN5#5-5G-NR Adhoc | +| 6.3D.3 Transmit ON/OFF time mask for UL-MIMO | TBD | "38.521-1_TPAnalysis_6.3.3.2_OnOff_M_v2.zip" | RAN5#5-5G-NR Adhoc | +| 6.3D.4.1 Absolute Power tolerance for UL-MIMO | 6 | "38.521-1_TPAnalysis_6.3.4.2_AbsPtol_v2.zip" | RAN5#83 | +| 6.3D.4.2 Relative Power Tolerance for UL-MIMO | TBD | "38.521-1_TPAnalysis_6.3.4.3_RelPtol_v2.zip" | RAN5#83 | +| 6.3D.4.3 Aggregate Power tolerance for UL-MIMO | PUCCH: 6
PUSCH: 6 | "38.521-1_TPAnalysis_6.3.4.4_AggPtol_v2.zip" | RAN5#83 | +| 6.4.1 Frequency error | 5 | "38.521-1_TPAnalysis_6.4.1_FreqErr_v3.zip" | RAN5#84 | +| 6.4.2.1 Error Vector Magnitude | PUSCH: 252
PUCCH: 36
PRACH: 36 | "38.521-1_TPAnalysis_6.4.2.1_EVM_v3.zip" | RAN5#94-e | +| 6.4.2.1a Error Vector Magnitude including symbols with transient period | PUSCH: 36 | "38.521-1_TPAnalysis_6.4.2.1_EVM_v3.zip" | RAN5#94e | +| 6.4.2.2 Carrier leakage | 3 | "38.521-1_TPAnalysis_6.4.2.2_CarrLeak_v2.zip" | RAN5#84 | +| 6.4.2.3 In-band emissions | 36 | "38.521-1_TPAnalysis_6.4.2.3_IE_2.zip" | RAN5#84 | +| 6.4.2.4 EVM equalizer spectrum flatness | 90 | "38.521-1_TPAnalysis_6.4.2.4_EVMequalizerSpectrumFlatness_v3.zip" | RAN5#84 | +| 6.4.2.5 EVM equalizer spectrum flatness for Pi/2 BPSK | 9 | "38.521-1_TPAnalysis_6.4.2.5_EVMequalizerSpectrumFlatness_BPSK_v2.zip" | RAN5#92-e | +| 6.4.2.6 | 90 | 38.521-1_TPAnalysis_6.4.2.6_Phase_Continuity_v1.zip | RAN5#100 | +| 6.4A.1.1 Frequency error for CA (2UL CA) | Inter-band:5
Intra-band contiguous:5
Intra-band non-contiguous:5 | "38.521-1_TPAnalysis on 6.4A.1.1_FreqErr_v1.zip" | RAN5#101 | +| 6.4A.2.1.1 Error Vector Magnitude for CA (2UL | inter-band CA:112 | "38.521-1_TPAnalysis on 6.4A.2.1.1_EVM_v1.zip" | RAN5#100 | + +| | | | | +|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|---------------------| +| CA) | Intra-band CA:144 | | | +| 6.4A.2.2.1 Carrier leakage for CA (2UL CA) | 2 | "38.521-1_TPAnalysis on 6.4A.2.2.1_CarrLeak_v1.zip" | RAN5#101 | +| 6.4A.2.3.1 In-band emissions for CA (2UL CA) | 16 | "38.521-1_TPAnalysis on 6.4A.2.2.1_IBE_v1.zip" | RAN5#101 | +| 6.4D.1 Frequency error | 5 | "38.521-1_TPAnalysis_6.4.1_FreqErr_v3.zip" | RAN5#84 | +| 6.4D.2.1 Error Vector Magnitude for UL MIMO | PUSCH: 108 | "38.521-1_TPAnalysis on 6.4.2.1_EVM_v3.zip" | RAN5#94-e | +| 6.4D.2.2 Carrier leakage for UL MIMO | 3 | "38.521-1_TPAnalysis on 6.4.2.2_CarrLeak_v2.zip" | RAN5#84 | +| 6.4D.2.3 In-band emissions for UL MIMO | 18 | "38.521-1_TPAnalysis_6.4.2.3_IE_2.zip" | RAN5#84 | +| 6.4D.2.4 EVM equalizer spectrum flatness for UL MIMO | 45 | "38.521-1_TPAnalysis_6.4.2.4_EVMequalizerSpectrumFlatness_v3.zip" | RAN5#84 | +| 6.4D.3 Time alignment error for UL-MIMO | 6 | "38.521-1_TPAnalysis_6.4D.3_TAE_MIMO.zip" | RAN5#82 | +| 6.5.1 Occupied bandwidth | 10 | "38.521-1_TPAnalysis_6.5.1_OccBW_v3.zip" | RAN5#92-e | +| 6.5.2.2 Spectrum Emission Mask | contiguous allocation: 144 (168 1 , 160 2,3 ) almost contiguous allocation: 24 | "38.521-1_TPAnalysis_6.2.2_MPR_6.5.2.2_SEM_6.5.2.4.1_N_R_ACLR_v5.zip" | RAN5#99 | +| 6.5D.2.3 Additional spectrum emission mask for UL-MIMO | Table 4.1.2.1-1 | Table 4.1.2.1-1 | See Table 4.1.2.1-1 | +| 6.5.2.4.1 NR Adjacent channel leakage ratio | contiguous allocation: 920 (1040 1 , 1000 2,3 ) almost contiguous allocation: 120 | "38.521-1_TPAnalysis_6.2.2_MPR_6.5.2.2_SEM_6.5.2.4.1_N_R_ACLR_v5.zip" | RAN5#99 | +| 6.5.2.4.2 UTRA ACLR | Same as NS_3U, NS_5U, NS_43 U, and NS_100 in Table 4.1.1.1-1 | "38.521-1_TPAnalysis_6.5.2.4.2_UTRA_ACLR_v3.zip" | RAN5#91-e | +| 6.5.3.1 General spurious emissions | 27 | "38.521-1_TPanalysis_6.5.3.1_TX_Spurious_Emission_v1.zip" | RAN5#89-e | +| 6.5.3.2 Spurious emissions for UE co-existence | 27 | "38.521-1_TPanalysis_6.5.3.1_TX_Spurious_Emission_v1.zip" | RAN5#89-e | +| 6.5.3.3 Additional spurious emissions | See Table 4.1.2.1-1 | See Table 4.1.2.1-1 | See Table 4.1.2.1-1 | +| 6.5.4 Transmit intermodulation | 8 | "38.521-1_TPAnalysis_6.5.4_TxIm_v3.zip" | RAN5#100 | +| 6.5A.1.1 Occupied bandwidth for CA (2UL CA) | Inter-band: 2
Intra-band contiguous: 1
Intra-band non-contiguous: 1 | "38.521-1_TPAnalysis_6.5A.1.1_OccBW_v2.zip" | RAN5#92-e | +| 6.5A.2.2.1 Spectrum emission mask for CA (2UL CA) | Inter-band CA:112
Intra-band contiguous CA:72
Intra-band non-contiguous CA:72 | "38.521-1_TPAnalysis_6.2A.2_MPR_6.5A.2.4.1_ACLR_6.5A.2.2.1_SEM" | RAN5#98 | + +| | | | | +|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------| +| 6.5A.2.4.1.1 NR ACLR for CA (2UL CA) | For inter-band CA:1480
For intra-band contiguous CA: 720
(contiguous RB allocation)
1080 (non-contiguous RB allocation)
For intra-band non-contiguous CA: 2880 | "38.521-1_TPanalysis_6.2A.2_MPR_6.5A.2.4.1_ACLR_6.5A.2.2.1_SEM" | RAN5#98 | +| 6.5A.2.4.2.1 UTRA ACLR for CA (2UL CA) | 840 | "38.521-1_TPanalysis on 6.5A.2.4.2.1 UTRA ACLR .zip" | RAN5#82 | +| 6.5A.3.1.1 General spurious emissions for CA (2UL CA) | For inter-band CA: 12
For intra-band contiguous CA: 20
For intra-band non-contiguous CA: 12 | "38.521-1_TPanalysis_6.5A.3.1.1_Spurious_v3.zip" | RAN5#101 | +| 6.5A.3.2.1 Spurious emissions for UE co-existence for CA (2UL CA) | For inter-band CA See table 4.1.3.2-1
For intra-band contiguous CA: 8
For intra-band non-contiguous CA: 4 | "38.521-1_TPanalysis_6.5A.3.2.1_SECoex_v3.zip" | RAN5#100 | +| 6.5A.4.1 Transmit intermodulation for CA (2UL CA) | 16 | "38.521-1_TPanalysis on 6.5A.4.1_TxIM_v1.zip" | RAN5#101 | +| 6.5D.1 Occupied bandwidth for UL-MIMO | 10 | 38.521-1_TPanalysis_6.5.1_OBW_v3.zip | RAN5#92-e | +| 6.5D.2.2 Spectrum emission mask for UL MIMO | UL MIMO with 2-layer: 64
UL MIMO with ULFPTx: 144 | "38.521-1_TPanalysis_6.2.2_MPR_6.5.2.2_SEM_6.5.2.4.1_N_R_ACLR_v5.zip" | RAN5#99 | +| 6.5D.2.4.1 NR ACLR for UL-MIMO | UL MIMO with 2-layer: 400
UL MIMO with ULFPTx: 920 | "38.521-1_TPanalysis_6.2.2_MPR_6.5.2.2_SEM_6.5.2.4.1_N_R_ACLR_v5.zip" | RAN5#99 | +| 6.5D.2.4.2 UTRA ACLR for UL-MIMO | 96 for NS_3U | "38.521-1_TPanalysis_6.5D.2.4.2_UTRA_ALCR_NS_3U_v1.zip"
"38.521-1_TPanalysis_6.5.2.4.2_UTRA_ACLR_v3.zip" | RAN5#5-5G-NR Adhoc | +| 6.5D.2_1.4.2 UTRA ACLR for UL MIMO (Rel-16 onward) | 216 for NS_3U | "38.521-1_TPanalysis_6.5D.2.4.2_UTRA_ALCR_NS_3U_v1.zip"
"38.521-1_TPanalysis_6.5.2.4.2_UTRA_ACLR_v3.zip" | RAN5#90-e | +| 6.5D.3.1 General spurious emissions | 27 | "38.521-1_TPanalysis_6.5.3.1_TX_Spurious_Emission_v1.zip" | RAN5#89-e | +| 6.5D.3.2 Spurious emissions for UE co-existence for UL-MIMO | 27 | "38.521-1_TPanalysis_6.5.3.1_TX_Spurious_Emission_v1.zip" | RAN5#89-e | +| 6.5D.3.3 Additional spurious emissions for UL-MIMO | Table 4.1.2.1-1 | Table 4.1.2.1-1 | RAN5#5-5G-NR Adhoc | +| 6.5D.3_1.1 General spurious emissions (Rel-16 onward) | 27 | "38.521-1_TPanalysis_6.5.3.1_TX_Spurious_Emission_v1.zip" | RAN5#89-e | +| 6.5D.3_1.2 Spurious emissions for UE co-existence for UL-MIMO (Rel-16 onward) | 27 | "38.521-1_TPanalysis_6.5.3.1_TX_Spurious_Emission_v1.zip" | RAN5#89-e | +| 6.5D.3_1.3 Additional spurious | Table 4.1.1.1-1 | Table 4.1.1.1-1 | RAN5#89-e | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-----------------------------------------|---------| +| emissions for UL-MIMO (Rel-16 onward) | | | | +| 6.5D.4 Transmit intermodulation for UL-MIMO | | "38.521-1_TPanalysis_6.5.4_TxIm_v2.zip" | RAN5#82 | +| NOTE 1: For power class 3 UE operating in bands n40, n41, n77, n78 and n79.
NOTE 2: UE operating in FDD mode, or in TDD mode in bands other than n40, n41, n77, n78 and n79, or in TDD mode the IE powerBoostPi2BPSK is set to 0 for bands n40, n41, n77, n78 and n79.
NOTE 3: UEs supporting pi/2 BPSK DMRS and the corresponding IE [DMRSPi2BPSK] is set to 1.
NOTE 4: The maximum number of test point is 24 if only default points are applied. | | | | + +Table 4.1.1.1-2: NR UE receiver test point selection for FR1 + +| Subclause | Number of test points | Justification in attachment | Comments | +|------------------------------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------|------------------| +| 7.3 Reference sensitivity power level | symmetric channel bandwidths: 45
asymmetric channel bandwidths: 30 | "38.521-1_TPanalysis_7.3_RefSense_v4.zip" | RAN5#95-e | +| 7.3A Reference sensitivity for CA | See clause 4.1.3 | See clause 4.1.3 | See clause 4.1.3 | +| 7.3D.2 Reference sensitivity power level for UL-MIMO | 45 | "38.521-1_TPanalysis_7.3_RefSense_v4.zip" | RAN5#95-e | +| 7.4 Maximum input level | symmetric channel bandwidths: 9
asymmetric channel bandwidths: 6 | 38.521-1_TPanalysis_7.4_Maximun input level_v4.zip"" | RAN5#100 | +| 7.4A Maximum input level for CA | 2CC:3
3CC:3 | "38.521-1_TPanalysis 7.4A maxIL for CA_v2.zip" | RAN5#100 | +| 7.4D Maximum input level for UL-MIMO | 6 | "38.521-1_TPanalysis_7.4_Maximun input level_v3.zip" | RAN5#96-e | +| 7.5 Adjacent Channel Selectivity | symmetric channel bandwidths: 3
asymmetric channel bandwidths: 2 | "38.521-1_TPanalysis_7.5_ACS_v3.zip" | RAN5#96-e | +| 7.5A Adjacent channel selectivity for DL CA | intra-band contiguous CA: 2
inter-band CA: 1 | "38.521-1_TPanalysis_7.5A.1_ACS_2CA.zip" | RAN5#83 | +| 7.5D Adjacent Channel Selectivity for UL-MIMO | 3 | "38.521-1_TPanalysis_7.5_ACS_v2.zip" | RAN5#82 | +| 7.6.2 In Band Blocking | symmetric channel bandwidths: 3
asymmetric channel bandwidths: 2 | "38.521-1_TPanalysis_7.6.2_InB_Block_v3.zip" | RAN5#96-e | +| 7.6.3 Out-of-band blocking | symmetric channel bandwidths: 3
asymmetric channel bandwidths: 2 | "38.521-1_TPanalysis_7.6.3_OobBlocking_v3.zip" | RAN5#96-e | +| 7.6.4 Narrow band blocking | symmetric channel bandwidths: 3
asymmetric channel bandwidths: 2 | "38.521-1_TPanalysis_7.6.4_NarrowbBlocking_v3.zip" | RAN5#96-e | +| 7.6A.2 Inband blocking for CA 2CC: 3CC:1 | 1 | "38.521-1_TPanalysis 7.6A.2 IBB for CA_v1.zip" | RAN5#89-e | +| 7.6A.3 Out-of-band blocking for CA | 1 | "38.521-1_TPanalysis_7.6A.3 Out-of-band blocking for CA_v1.zip" | RAN5#86-e | +| 7.6A.4 Narrow band blocking for CA | 1 | "38.521-1_TPanalysis_7.6A.4 Narrow band blocking for CA_v1.zip" | RAN5#86-e | +| 7.6D.2 Inband blocking for UL-MIMO | 3 | "38.521-1_TPanalysis_7.6.2_InB_Block_v3.zip" | RAN5#96-e | +| 7.6D.3 Out-of-band blocking for UL-MIMO | 3 | "38.521-1_TPanalysis_7.6.3_OobBlocking_v3.zip" | RAN5#96-e | +| 7.6D.4 Narrow band blocking for UL-MIMO | 3 | "38.521-1_TPanalysis_7.6.4_NarrowbBlocking_v3.zip" | RAN5#96-e | + +| | | | | +|----------------------------------------------|---------------------------------------------------------------------|--------------------------------------------------------------------|-----------| +| 7.7 Spurious response | symmetric channel bandwidths: 3
asymmetric channel bandwidths: 2 | "38.521-1_TPanalysis_7.7_Spurious response_v2.zip" | RAN5#96-e | +| 7.7D Spurious response for UL-MIMO | 3 | "38.521-1_TPanalysis_7.7_Spurious response_v2.zip" | RAN5#96-e | +| 7.8.2 Wide band Intermodulation | symmetric channel bandwidths: 3
asymmetric channel bandwidths: 2 | "38.521-1_TPanalysis_7.8.2_WidebandIntermod_v3.zip" | RAN5#96-e | +| 7.8A Wide band Intermodulation for CA | 1 | "38.521-1_TPanalysis_7.8A Wide band Intermodulation for CA_v1.zip" | RAN5#86-e | +| 7.8D.2 Wide band Intermodulation for UL-MIMO | 3 | "38.521-1_TPanalysis_7.8.2_WidebandIntermod_v3.zip" | RAN5#96-e | +| 7.9 Spurious emissions | 3 | "38.521-1_TPanalysis_7.9_RxSpurious.zip" | RAN5#81 | + +#### 4.1.1.2 FR1 SUL test cases + +This section contains information on test point selection for SUL test cases in [2]. The basic principle is following the same rules for test point selection in single carrier test cases. In these SUL test cases, there are default test points to be used unless SUL configuration specific test points are over-ruling. + +##### Basic rules for Tx SUL test cases: + +For Test environment: Adopt the same selection of test environment in corresponding single carrier test cases. + +For Test frequency: Considering that Non-SUL carrier should have no impact on SUL carrier testing results, for any SUL configurations, Mid range is chosen as default for Non-SUL carrier. Select the same test frequency in corresponding single carrier test cases for SUL carrier. + +For Test SCS: Considering lowest supported SCS can obtain minimum guardband and maximum spectrum utilization, and only 15 kHz SCS is supported for SUL band in SUL configurations, it's reasonable to select 15 kHz SCS for SUL carrier and lowest supported SCS for Non-SUL carrier regardless of SUL configurations. + +For Test channel bandwidths: Under the limit of 15 kHz SCS, only the lowest channel bandwidth is supported for current Non-SUL bands in SUL configurations, which are band n78 and n79. Select the lowest channel bandwidth that support 15kHz SCS for Non-SUL carrier. Select the same test channel bandwidths as in corresponding single carrier test cases for SUL carrier. + +For waveform, modulation and RB allocations: Adopt the same selection of test configurations as in corresponding single carrier test cases for SUL carrier. + +##### Basic rules for Rx SUL test cases: + +In Rx testing for SUL, test point selection in clause 7.3C and 7.6C need to be defined. Considering the focus of Rx test cases is testing DL bands, the configuration of SUL carrier shall be selected to ensure the test coverage without costing too much testing time. The configuration of Non-SUL carrier shall be selected based on the same principle as single carrier test cases. The basic test point selection rule for Rx SUL test cases is specified as below: + +For Test environment: Adopt the same selection of test environment in corresponding single carrier test cases. + +For Test frequency: The Non-SUL carrier should select the same test frequency as corresponding single carrier test cases. Select Mid range as default for SUL carrier. + +For Test SCS: Since the REFSSENS requirement for SUL is specified for 15 kHz SCS for SUL band and the test point selection of clause 7.6C is also based on that of clause 7.3C, 15 kHz SCS should be selected for SUL carrier. For the Non-SUL carrier the SCS should be selected following the same rule as single carrier testing. + +For test channel bandwidths: Highest channel bandwidth when SCS =15 kHz for SUL shall be selected for SUL carrier. For the Non-SUL carrier the channel bandwidth should be selected following the same rule as single carrier testing. + +For waveform, modulation and RB allocations: Adopt the same selection of test configurations as single carrier test cases for Non-SUL carrier. SUL carrier select DFT-s-OFDM QPSK. The RB allocation of SUL carrier shall fulfill the requirement in clause 7.3C.0 in TS 38.521-1. + +Number of test points for SUL test cases in FR1 are listed in table 4.1.1.2-1 and table 4.1.1.2-2. + +**Table 4.1.1.2-1: Number of test points for SUL test cases in FR1 (NR UE Transmitter test)** + +| Subclause | Number of test points | Comments | +|-------------------------------------------------------------------------------------------|-------------------------------------|----------| +| 6.2C.1 Configured transmitted power for SUL | 30 | RAN5#86e | +| 6.2C.3 UE maximum output power for SUL | 270 | RAN5#86e | +| 6.2C.4 UE maximum output power reduction for SUL | 460 (500 1 ) | RAN5#90e | +| 6.2C.5 UE additional maximum output power reduction for SUL | Table 4.1.2.1-1 | RAN5#87e | +| 6.3C.1 Minimum output power for SUL | 45 | RAN5#87e | +| 6.3C.3.1 Transmit ON/OFF time mask for SUL | 45 | RAN5#87e | +| 6.3C.3.2 General transmit ON/OFF time mask for switching between two uplink carriers | 1 | RAN5#96e | +| 6.3C.4.1 Absolute power tolerance for SUL | 3 | RAN5#87e | +| 6.3C.4.2 Power Control Relative power tolerance for SUL | TBD | RAN5#87e | +| 6.3C.4.3 Aggregate power tolerance for SUL | PUCCH: 3
PUSCH: 3 | RAN5#87e | +| 6.4C.1 Frequency error for SUL | 5 | RAN5#86e | +| 6.4C.2.1 Error Vector Magnitude for SUL | PUSCH: 84
PUCCH: 24
PRACH: 12 | RAN5#86e | +| 6.4C.2.2 Carrier leakage for SUL | 3 | RAN5#90e | +| 6.4C.2.3 In-band emissions for SUL | 36 | RAN5#90e | +| 6.4C.2.4 EVM equalizer spectrum flatness for SUL | 90 | RAN5#90e | +| 6.4C.2.5 EVM equalizer spectrum flatness for Pi/2 BPSK for SUL | 9 | RAN5#90e | +| 6.5C.1 Occupied bandwidth for SUL | 18 | RAN5#86e | +| 6.5C.2.2 Spectrum Emission Mask for SUL | 72 (80 1 ) | RAN5#90e | +| 6.5C.2.3 Additional spectrum emission mask for SUL | Table 4.1.2.1-1 | RAN5#86e | +| 6.5C.2.4.1 NR ACLR for SUL | 460 (500 1 ) | RAN5#90e | +| 6.5C.2.4.2 UTRA ACLR for SUL | Table 4.1.2.1-1 | RAN5#86e | +| 6.5C.3.1 General spurious emissions for SUL | 27 | RAN5#86e | +| 6.5C.3.2 Spurious emission for UE co-existence for SUL | 27 | RAN5#86e | +| 6.5C.3.3 Additional spurious emissions for SUL | 115 for NS_05
28 for NS_43 | RAN5#87e | +| 6.5C.4 Transmit intermodulation for SUL | 4 | RAN5#86e | +| NOTE 1: UEs supporting pi/2 BPSK DMRS and the corresponding IE [DMRSPi2BPSK] is set to 1. | | | + +**Table 4.1.1.2-2: Number of test points for SUL test cases in FR1 (NR UE Receiver test)** + +| Subclause | Number of test points | Comments | +|--------------------------------------------------|--------------------------------------------------------------------------------------|----------| +| 7.3C.2 Reference sensitivity power level for SUL | General test points: 45
SUL configuration specific test points:
SUL_n78-n80: 2 | RAN5#90e | +| 7.6C.2 Inband Blocking for SUL | 3 | RAN5#87e | +| 7.6C.3 Out-of-band blocking for SUL | 3 | RAN5#87e | + +#### 4.1.1.3 FR1 V2X test cases + +This section contains information on test point selection for V2X test cases 6.2E, 6.3E, 6.4E, 6.5E, 7.3E, 7.4E, 7.5E, 7.6E, 7.7E and 7.8E in [2]. + +Number of test points for V2X test cases in FR1 are listed in table 4.1.1.3-1 and table 4.1.1.3-2. + +**Table 4.1.1.3-1: Number of test points for V2X test cases in FR1 (NR UE Transmitter test)** + +| Subclause | Number of test points | Justification in attachment | Comments | +|--------------------------------------------------|-----------------------|-------------------------------------------------------------------------|-----------| +| 6.2E.2 UE maximum output power reduction for V2X | 440 | '38.521-1_TP analysis_V2X_6.2E.2_MPR_6.5E.2.2_SEM_6.5E.2.4_ACLR_v3.zip' | RAN5#95-e | +| 6.3E.1 Minimum output power for V2X | 360 | '38.521-1_TP analysis_V2X_6.3E.1_MinOP_v1.zip' | RAN5#92-e | +| 6.5E.2.2 Spectrum emission mask for V2X | 88 | '38.521-1_TP analysis_V2X_6.2E.2_MPR_6.5E.2.2_SEM_6.5E.2.4_ACLR_v3.zip' | RAN5#95-e | +| 6.5E.2.4 Adjacent channel leakage ratio for V2X | 440 | '38.521-1_TP analysis_V2X_6.2E.2_MPR_6.5E.2.2_SEM_6.5E.2.4_ACLR_v3.zip' | RAN5#95-e | + +**Table 4.1.1.3-2: Number of test points for V2X test cases in FR1 (NR UE Receiver test)** + +| Subclause | Number of test points | Justification in attachment | Comments | +|-----------|-----------------------|-----------------------------|----------| +| FFS | | | | + +#### 4.1.1.4 FR1 RedCap test cases + +This section contains information on test point selection for RedCap test cases in [2]. The general rule in this section apply to all the RedCap test cases. Separate analysis is not provided for each single test case. + +For the Tx requirements, basic PC3 requirements apply with the exception that the maximum channel bandwidth is 20MHz. Regarding test point selection, the same test points for PC3 non-RedCap UE apply for RedCap UE, except that the Low, Mid, Hight test channel bandwidth shall be selected among channel bandwidths up to 20MHz. + +For the Rx REFSENS requirements, TDD/FDD 2Rx, TDD/FDD 1Rx, HD-FDD 2Rx and HD-FDD 1Rx requirements are specified separately. For test cases other than REFSENS, no exception requirements are specified, but considering those requirements have dependency on REFSENS, the UL/DL RB allocation would follow that of REFSENS. + +- For TDD/FDD 2Rx capable RedCap UE, the basic 2Rx REFSENS requirements apply with the exception that the maximum channel bandwidth is 20MHz. For all the Rx test cases, the same test points for non-RedCap UE apply except that the Low, Mid, Hight test channel bandwidth shall be selected among channel bandwidths up to 20MHz. +- For TDD/FDD 1Rx capable RedCap UE, the exceptional REFSENS requirements are specified for channel bandwidth up to 20MHz. The UL/DL configuration required for 1Rx are the same for 2Rx requirements. For all the Rx test cases, the same test points for non-RedCap UE apply except that the Low, Mid, Hight test channel bandwidth shall be selected among channel bandwidths up to 20MHz. +- For HD-FDD 2Rx and 1Rx capable RedCap UE, the exceptional REFSENS requirements are specified for channel bandwidth up to 20MHz, with specific UL configuration specified along. For all the Rx test cases, the same test points for non-RedCap UE apply except that the Low, Mid, Hight test channel bandwidth shall be selected among channel bandwidths up to 20MHz, and the UL configuration shall follow Table 7.31.2-5 in TS 38.101-1[2]. + +#### 4.1.1.5 FR1 TxD test cases + +This section contains information on test point selection for TxD test cases [2]. Except for test cases listed in Table 4.1.1.5-1, the test point selection principle in single carrier test cases applies to all TxD test cases in term of Test environment, Test SCS, Test channel bandwidths, modulation and RB allocations. + +Table 4.1.1.5-1: NR UE transmitter test point selection for TxD test cases in FR1 (test) + +| Subclause | Number of test points | Justification in attachment | Comments | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------| +| 6.2G.1 UE maximum output power for Tx Diversity | Power Class 2: 270
Power Class 1.5: 0 | "38.521-1_TPanalysis_6.2G.1_MaxOP_TxD.zip" | RAN5#95-e | +| 6.2G.2 Maximum Output Power Reduction for Tx Diversity | Power Class 2: 920 (contiguous allocation), 120 (almost contiguous allocation)
Power Class 1.5: 1080
Power Class 3: 1120 | "38.521-1_TPanalysis_6.2G.2_MPR_6.5G.2.1_SEM_6.5G.2.3.1_NR_ACLR_TxD_v1.zip" | RAN5#97 | +| 6.2G.3 UE additional maximum output power reduction for Tx Diversity | See clause 4.1.2.1 | See clause 4.1.2.1 | See clause 4.1.2.1 | +| 6.5G.2.3.1 NR ACLR for Tx diversity | power class 2: 920 (contiguous allocation), 120 (almost contiguous allocation)
power class 1.5: 1080 | "38.521-1_TPanalysis_6.2G.2_MPR_6.5G.2.1_SEM_6.5G.2.3.1_NR_ACLR_TxD.zip" | RAN5#95-e | + +#### 4.1.1.6 FR1 shared spectrum channel access test cases + +This section contains information on test point selection for shared spectrum channel access test cases in TS 38.521-1[2]. The general rule in this section apply to all test cases for shared spectrum channel access test cases. Separate analysis for each FR1 shared spectrum channel access test case is not provided, unless deemed necessary. + +From the latest core requirement for NR band with shared spectrum channel access, the frequency range are 5150 MHz – 5925 MHz for n46, and 5925 MHz – 7125 MHz for n96. Both bands support power class 5 operations with various channel bandwidths. + +For all Tx and Rx test requirements of NR unlicensed band, the selections of test point shall be the same as for regular NR band for Test Environment, Test frequency, Test channel bandwidths, Test Subcarrier Spacing, Test uplink/downlink modulations and Test RB configurations, unless shared spectrum channel access configuration specific test points are over-ruling. + +**Table 4.1.1.6-1: UE transmitter test point selection for FR1 shared spectrum channel access** + +| Subclause | Number of test points | Justification | Comments | +|-----------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------|----------| +| 6.2F.1 UE maximum output power for shared spectrum channel access | 800 | Same as 6.2.1 | RAN5#98 | +| 6.2F.2 Maximum Output Power Reduction | 600 | 38.521-1_TP analysis_NR-U_6.2F.3_MPR_6.5F.2.2_SEM_6.5F.2.4.1_ACLR_v1.zip | RAN5#101 | +| 6.2F.3 UE additional maximum output power reduction for shared spectrum access | 144 | 38.521-1_TPanalysis_6.2F.3_AMPR_NS_28_NS_29.zip | RAN5#101 | +| 6.4F.2.2 Carrier leakage | 3 | General rules of test point selection apply. Test points of TC 6.4.2.2 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 6.4F.2.4 EVM equalizer spectrum flatness | 90 | General rules of test point selection apply. Test points of TC 6.4.2.4 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 6.5F.1 Occupied bandwidth for shared spectrum channel access | | TBD | | +| 6.5F.2.2 Spectrum emission mask for operation with shared spectrum channel access | 600 | 38.521-1_TP analysis_NR-U_6.2F.3_MPR_6.5F.2.2_SEM_6.5F.2.4.1_ACLR_v1.zip | RAN5#101 | +| 6.5F.2.3 Additional spectrum emission mask | | TBD | | +| 6.5F.2.4.1 Shared spectrum channel access ACLR | 600 | 38.521-1_TP analysis_NR-U_6.2F.3_MPR_6.5F.2.2_SEM_6.5F.2.4.1_ACLR_v1.zip | RAN5#101 | +| 6.5F.2.4.2 Additional requirements for network signalled value "NS_29" | | TBD | | +| 6.5F.3.1 General spurious emissions | 27 | Test points of TC 6.5.3.1 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 6.5F.3.3 Additional spurious emissions | | TBD | | +| 6.5F.4 Transmit intermodulation for shared spectrum channel access | 8 | "38.521-1_TPanalysis_6.5.4_TxIm_v3.zip" | RAN5#100 | + +**Table 4.1.1.6-2: UE receiver test point selection for FR1 shared spectrum channel access** + +| Subclause | Number of test points | Justification | Comments | +|------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------|----------| +| 7.3F.2 Reference sensitivity power level | 45 | General rules of test point selection apply. Test points of TC 7.3.2 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 7.5F.1 Adjacent channel selectivity for shared spectrum channel access | 3 | General rules of test point selection apply. Test points of TC 7.5 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 7.6F.2.1 In-band blocking for shared spectrum channel access | 3 | General rules of test point selection apply. Test points of TC 7.6.2 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 7.6F.3 Out of band blocking | 3 | General rules of test point selection apply. Test points of TC 7.6.3 from TS 38.521-1 can be leveraged. | RAN5#97 | +| 7.7F.1 Spurious response for shared spectrum channel access | 7 | General rules of test point selection apply. Test points of TC 7. from TS 38.521-1 can be leveraged. | RAN5#97 | + +#### 4.1.1.7 FR1 CA with UL MIMO test cases + +This section contains information on test point selection for FR1 CA with UL MIMO test cases in TS 38.521-1[2]. The general rule in this section apply to all test cases for FR1 CA with UL MIMO test cases. Separate analysis for each FR1 CA with UL MIMO test case is not provided, unless deemed necessary. + +For Test Environment, Test frequency, Test channel bandwidths, Test Subcarrier Spacing, modulation and RB allocation: adopt the same selection as the corresponding FR1 NR CA test cases. + +As for waveform, CP-OFDM is mandatory in case of UL MIMO with two layer transmission and DFT-s-OFDM is not valid. Therefore CP-OFDM waveform is selected. + +The test point selection for FR1 CA with UL MIMO test cases in [2] clause 6 is listed in Table 4.1.1.7-1. + +**Table 4.1.1.7-1: UE receiver test point selection for FR1 shared spectrum channel access** + +| Subclause | Number of test points | Justification | Comments | +|-----------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 6.2H.1.2 UE maximum output power reduction for intra-band UL contiguous CA with UL MIMO | 320 | General rules of test point selection apply. Test points of TC 6.2A.2.1 for intra-band contiguous CA from TS 38.521-1 can be leveraged excluding DFT-s-OFDM test points. | RAN5#101 | +| 6.2H.1.4 Configured transmitted power for intra-band UL contiguous CA with UL MIMO | 10 | General rules of test point selection apply. Test points of TC 6.2A.4.1 for intra-band contiguous CA from TS 38.521-1 can be leveraged with CP-OFDM waveform replacement. | RAN5#101 | +| 6.3H.1.1 Minimum output power for intra-band UL contiguous CA with UL MIMO | 20 | General rules of test point selection apply. Test points of TC 6.3A.1.1 for intra-band contiguous CA from TS 38.521-1 can be leveraged with CP-OFDM waveform replacement. | RAN5#101 | +| 6.3H.1.3 Transmit ON/OFF time mask for intra-band UL contiguous CA with UL MIMO | 40 | General rules of test point selection apply. Test points of TC 6.3A.3.1 for intra-band contiguous CA from TS 38.521-1 can be leveraged with CP-OFDM waveform replacement. | RAN5#101 | +| 6.5H.1.2.1 Spectrum emission mask for intra-band UL contiguous CA for UL MIMO | 32 | General rules of test point selection apply. Test points of TC 6.5A.2.2.1 for intra-band contiguous CA from TS 38.521-1 can be leveraged excluding DFT-s-OFDM test points. | RAN5#101 | +| 6.5H.1.2.3 NR ACLR for intra-band UL contiguous CA for UL MIMO | 320 | General rules of test point selection apply. Test points of TC 6.5A.2.4.1.1 for intra-band contiguous CA from TS 38.521-1 can be leveraged excluding DFT-s-OFDM test points. | RAN5#101 | + +### 4.1.2 Test point analysis per NS value + +#### 4.1.2.1 A-MPR, A-SEM and A-SE FR1 test cases for single carrier and UL MIMO + +This section contains information on test point selection for single carrier test cases 6.2.3, Additional Maximum Power Reduction (A-MPR), 6.5.2.3 Additional spectrum emission mask (A-SEM) and 6.5.3.3 Additional spurious emissions (A-SE); and for correspondent UL-MIMO test cases in 6.2D.3 and 6.5D.3.3 in [2]. + +Selection of test points should include some possible worst combinations based on the A-MPR characteristics specified for each NS value and these shall be selected so that they match with corresponding spectrum emission requirements test points. The number of test points should be realistic. + +For pi/2 BPSK with Rel-16 DMRS, the correspondent A-MPR requirements are the same as that for Rel-15 DMRS but the PAPR is lower. Given the UE can pass the requirements using Rel-15 DMRS, it can be expected that the UE can pass the requirements using Rel-16 DMRS. Therefore there is no need to additionally test A-MPR, A-SEM and A-SE for Rel-16 DMRS. + +Table 4.1.2.1-1 lists number of test points for A-MPR, A-SEM and A-SE single carrier test cases and for different NS values. + +Table 4.1.2.1-1: NS value specific test points for A-MPR, A-SEM and A-SE single carrier + +| NS label | Number of test points for A-MPR | Number of test points A-SEM | Number of test points A-SE | Justification | Comments | +|------------------|-----------------------------------------------|-----------------------------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------| +| NS_03
NS_03U | 144 for Non-SUL testing
72 for SUL testing | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_03.zip" | RAN5#85 | +| NS_04 | 6.2.3: 120
6.2D.3: 112
6.5D.3.3: 112 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_04_v3.zip" | RAN5#93-e | +| NS_05 | 6.5.3.3: 432 | | | "38.521-1_TPAnalysis_6.5.3.3_TX_Additional_Spurious_Emission_NS_05.zip" | RAN5#87-e | +| NS_05,
NS_05U | 6.2.3: 288 for PC3
6.2.3: 396 for PC2 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_05_v3.zip" | RAN5#96-e | +| NS_06 | 6.2.3:
PC1 160
PC3 144 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_06_v2.zip" | RAN5#92-e | +| NS_07 | 162 | 162 | 162 | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_07.zip" | RAN5#99 | +| NS_12 | 48 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_12_13_14_15.zip" | RAN5#90-e | +| NS_13 | 21 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_12_13_14_15.zip" | RAN5#90-e | +| NS_14 | 6.2.3: 50
6.5.3.3: 25 | | 25 | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_12_13_14_15.zip"
"38.521-1_TPAnalysis_6.5.3.3_TX_Additional_Spurious_Emission_NS_14.zip" | RAN5#90-e
RAN5#96-e | +| NS_15 | 102 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_12_13_14_15.zip" | RAN5#90-e | +| NS_17 | 6.5.3.3: 4 | | | "38.521-1_TPAnalysis_6.5.3.3_TX_Additional_Spurious_Emission_NS_17_v2.zip" | RAN5#92-e | +| NS_18 | 88
6.2.3: 108
6.5.3.3: 54 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_6.5.3.3_ASE_NS_18_v3.zip" | RAN5#89-e | +| NS_21 | 180 | 180 | 180 | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_21_v1.zip" | RAN5#98 | +| NS_24 | 6.2.3: 300 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_24.zip" | RAN5#87 | +| NS_27 | 6.2.3: 360 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_27_v5.zip" | RAN5#98 | +| NS_35 | 6.2.3: 144
6.2.3: 72 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_35_v2.zip" | RAN5#5-5G-NR-Adhoc | +| NS_37 | 6.2.3: 48 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_37.zip" | RAN5#86 | +| NS_38 | 6.2.3: 96 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_38.zip" | RAN5#86 | +| NS_39 | 6.2.3: 54 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_39.zip" | RAN5#86 | +| NS_40 | 6.2.3: 24 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_40.zip" | RAN5#87 | +| NS_41 | 6.2.3: 72 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_41.zip" | RAN5#87 | +| NS_42 | 6.2.3: 108 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_42.zip" | RAN5#87 | +| NS_43 | 6.2.3: 28 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_43_v2.zip" | RAN5#86 | +| | 6.5.3.3: 81 | | | "38.521-1_TPAnalysis_6.5.3.3_TX_Additional_Spurious_Emission_NS_43.zip" | RAN5#87-e | +| NS_43U | 6.2.3: 72 | | | "38.521-1_TPAnalysis_6.2.3_AMPR_NS_43U.zip" | RAN5#85 | +| NS_44 | 360 | N/A | 180 | "38.521- | RAN5#90-e | + +| | | | | | | +|--------|---------------------------------------------------|-----|----------------------------|-----------------------------------------------------------|-----------| +| | | | | 1_TPanalysis_6.2.3_AMPR_6.5.3.3_ASE_NS_44.zip" | | +| NS_45 | 24 | | | "38.521-1_TPanalysis_6.2.3_AMPR_NS_45.zip" | RAN5#89-e | +| NS_46 | 176 | | | "38.521-1_TPanalysis_6.2.3_AMPR_NS_46.zip" | RAN5#89-e | +| NS_47 | 70 | | | "38.521-1_TPanalysis_6.2.3_AMPR_NS_47.zip" | RAN5#87 | +| NS_48 | 240 for PC3
384 for PC2 | N/A | 96 | "38.521-1_TPanalysis_6.2.3_AMPR_6.5.3.3_ASE_NS_48_v3.zip" | RAN5#96-e | +| NS_49 | 280 for PC3
392 for PC2 | N/A | 140 for PC3
191 for PC2 | "38.521-1_TPanalysis_6.2.3_AMPR_6.5.3.3_ASE_NS_49_v2.zip" | RAN5#98-e | +| NS_50 | 120 for PC3
288 for PC2 | | 120 for PC3
288 for PC2 | "38.521-1_TPanalysis_6.2.3_AMPR_6.5.3.3_ASE_NS_50.zip" | RAN5#99 | +| NS_56 | 175 | | 175 | 38.521-1_TPanalysis_6.2.3_AMPR_6.5.3.3_ASE_NS_56.zip | RAN5#93-e | +| NS_100 | 144 for Non-SUL testing

72 for SUL testing | | | "38.521-1_TPanalysis_6.2.3_AMPR_NS_100.zip" | RAN5#85 | + +#### 4.1.2.2 A-MPR test cases for FR1 UL CA + +This section contains information on test point selection for test case 6.2A.3.1 in [2], UE additional maximum output power reduction for CA. + +TS 38.101 [3] specifies band dependent NS-values, which in the inter-band UL CA test cases become a combination of two NS-values. Testing all possible combinations would lead to too excessive testing and the combinations that are realistic should therefore be prioritized. This selection is documented in table 4.1.1.1-1. + +Table 4.1.2.2-1: A-MPR test coverage per CA configuration for inter-band CA with 2 CC + +| CA config with UL CA support (Note 1) | NS values in same order as Uplink CA Configuration column | | Number of test points | Applicable test case | Justification | Comment | +|---------------------------------------|-----------------------------------------------------------|-------|-----------------------|----------------------|-----------------------------------------------|-----------| +| CA_n3-n78
CA_n8-n78 | NS_100 | NS_01 | 24 | N/A | "38.521-1_TPanalysis 6.2A.3 NS_100+NS_01.zip" | RAN5#87-e | +| CA_n8-n78 | NS_43 | NS_01 | 12 | N/A | "38.521-1_TPanalysis 6.2A.3 NS_43+NS_01.zip" | RAN5#88-e | +| CA_n8-n78 | NS_43U | NS_01 | 12 | N/A | "38.521-1_TPanalysis 6.2A.3 NS_43U+NS_01.zip" | RAN5#88-e | +| CA_n24-n41 | NS_56 | NS_04 | 24 | N/A | "38.521-1_TPanalysis_6.2A.3_NS_56+NS_04.zip" | RAN5#96-e | +| CA_n24-n48 | NS_56 | NS_27 | 24 | N/A | "38.521-1_TPanalysis_6.2A.3_NS_56+NS_27.zip" | RAN5#96-e | +| CA_n24-n77 | NS_56 | NS_55 | 24 | N/A | "38.521-1_TPanalysis_6.2A.3_NS_56+NS_55.zip" | RAN5#96-e | +| CA_n28-n78 | NS_17 | NS_01 | 12 | N/A | "38.521-1_TPanalysis_6.2A.3_NS_17+NS_01.zip" | RAN5#99 | +| CA_n41A-n79A | NS_47 | NS_01 | 3 | N/A | "38.521-1_TPanalysis_6.2A.3_NS_47+NS_01.zip" | RAN5#94-e | +| CA_n28A-n41A | NS_17 | NS_47 | 12 | N/A | "38.521-1_TPanalysis_6.2A.3_NS_17+NS_47.zip" | RAN5#101 | +| Note 1: As per TS 38.101. | | | | | | | + +The analyses are performed per NS-value and are stored as zip-files as defined in annex A. The general principle for selection of test points is: + +- Test the minimum Total power backoff value +- Test the maximum Total power backoff value +- Test the maximum unbalanced Total power backoff among CCs (max $P_{\text{CMAX,c}}$ difference). + +Where the Total power backoff value means: $\text{MAX}[\text{MPR, A-MPR}]$ + +### 4.1.3 Test point analysis per NR CA configuration + +#### 4.1.3.1 Reference Sensitivity test cases for FR1 NR CA + +Editor's note: + +- Not all CA configurations completed in TS 38.521-1 refsens test cases are listed in Table 4.1.3.1-1 through Table 4.1.3.1-5. + +This clause contains information on test point analysis, test frequency selection and status for FR1 NR CA test cases in TS 38.521-1 [2] clause 7. The analyses are performed per CA configuration in Table 4.1.3.1-1 through Table 4.1.3.1 4. The principles for selection of reference sensitivity test points for NR CA is given in Annex B including a test point analysis check list in B.9. + +**Table 4.1.3.1-1: Reference Sensitivity test cases per CA configuration (single band)** + +| CA config | Single band refsens exception, victim band (Note 2) | Requirement coverage (Note 2) | Test point analysis updated | +|------------|-----------------------------------------------------|-------------------------------|-----------------------------| +| CA_n2(2A) | – | NE | RAN5#100 | +| CA_n41C | – | NE | RAN5#89-e | +| CA_n48B | – | NE | RAN5#94-e | +| CA_n66B | – | NE | RAN5#86-e | +| CA_n66(2A) | – | NE | RAN5#86-e | +| CA_n66(3A) | – | NE | RAN5#100 | +| CA_n71(2A) | – | NE | RAN5#94-e | +| CA_n77(2A) | – | NE | RAN5#100 | +| CA_n77C | – | NE | RAN5#96e | +| CA_n78C | – | NE | RAN5#87-e | +| CA_n78(2A) | – | NE | RAN5#101 | + +NOTE 1: Void. + +NOTE 2: Notations used: +NE: Non-exception as defined in TS 38.101-1 [5], meaning single carrier NR requirements apply. +HD: UL Harmonic Distortion, as defined in TS 38.101-1 [5], 7.3A.4 +HM: RX Harmonic Mixing, as defined in TS 38.101-1 [5], 7.3A.4 +IMD: Intermodulation Distortion, as defined in TS 38.101-1 [5], 7.3A.5 +CBI: Cross Band Isolation, as defined in TS 38.101-1 [5], 7.3A.6 + +Table 4.1.3.1-2: Reference Sensitivity test cases per CA configuration (two bands) + +| CA config | Two band refsens exception, victim band (Note 1) | Requirement coverage (Note 1) | Test point analysis updated | +|-----------------|----------------------------------------------------------------------|-------------------------------|-----------------------------| +| CA_n1A-n3A | n1 (IMD3)
n3(CBI) | IMD,CBI | RAN5#95-e | +| CA_n1A-n8A | n1 (IMD4) | IMD | RAN5#95-e | +| CA_n1A-n28A | n1 (HD3) | HD | RAN5#101 | +| CA_n1A-n77A | n77 (HD2) | HD | RAN5#89-e | +| CA_n1A-n78A | n1 (IMD4) | IMD | RAN5#94 | +| CA_n2A-n48A | n48 (HD2), n2(IMD4) | HD, IMD | RAN5#96-e | +| CA_n2A-n5A | - | NE | RAN5#97 | +| CA_n2A-n14A | - | NE | RAN5#100 | +| CA_n2A-n48A | n48 (HD2), n2(IMD4) | HD, IMD | RAN5#100 | +| CA_n2A-n48B | (NOTE 2) | NE | RAN5#101 | +| CA_n2A-n66A | n2(IMD3), n66(IMD5) | IMD | RAN5#96-e | +| CA_n2A-n77A PC3 | n77 (HD2), n2 (HM), n2(IMD2),
n2(IMD4), n2(IMD5), n2(IMD7) | HD, HM, IMD, | RAN5#99 | +| CA_n2A-n77A PC2 | n77 (HD2), n2 (HM), n2(IMD2),
n2(IMD4) n2(CBI) | HD, HM, IMD, CBI | RAN5#99 | +| CA_n2A-n77C | (NOTE 2) | NE | RAN5#101 | +| CA_n3A-n5A | n3 (IMD4 2*fn3-2*fn5 )
n5 (IMD2 fn3-fn5 ) | IMD | RAN5#95-e | +| CA_n3A-n8A | n8(IMD4), n3(IMD5) | IMD | RAN5#100 | +| CA_n3A-n28A | - | NE | RAN5#101 | +| CA_n3A-n41A PC2 | n3 (IMD4), n3 (CBI) | IMD, CBI | RAN5#100 | +| CA_n3A-n41A PC3 | n3 (IMD4), n3 (CBI), n41 (CBI) | IMD, CBI | RAN5#100 | +| CA_n3A-n77A | n77 (HD2), n3 (IMD2), n3 (IMD4) | HD, IMD | RAN5#99 | +| CA_n3A-n77(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n3A-n78A PC3 | n3 (IMD2 fn78-fn3 )
n3 (IMD4 fn78-3*fn3 )
n78 (HD2) | HD, IMD | RAN5#101 | +| CA_n3A-n78A PC2 | n3 (IMD2 fn78-fn3 )
n3 (IMD4 fn78-3*fn3 )
n78 (HD2), n3 (HM) | HD, HM, IMD | RAN5#101 | +| CA_n5A-n66A | n5(IMD2) | IMD | RAN5#96-e | +| CA_n5A-n77A PC3 | n77 (HD4), n77 (HD5), n5 (HM),
n5(IMD4), n5(IMD5) | HD, HM, IMD | RAN5#99 | +| CA_n5A-n77A PC2 | n77 (HD4), n77 (HD5), n5 (HM),
n5(IMD4) | HD, HM, IMD | RAN5#99 | +| CA_n5A-n77C | (NOTE 2) | NE | RAN5#101 | +| CA_n5A-n78A | n78 (HD2) | HD | RAN5#94-e | +| CA_n7A-n78A | n7 and n78 (CBI) | CBI | RAN5#94-e | +| CA_n8A-n78A | n8 (IMD4 fn78-3*fn8 )
n78 (HD4) | HD, IMD | RAN5#87-e | +| CA_n14A-n30A | - | NE | RAN5#100 | +| CA_n14A-n66A | - | NE | RAN5#100 | +| CA_n14A-n77A | n77 (HD5), n14 (HM), n14 (IMD5) | HD, HM, IMD | RAN5#100 | +| CA_n20A-n78A | n78 (HD4), n20 (IMD4) | HD, IMD | RAN5#100 | +| CA_n25A-n66A | n25 (IMD3), n66 (IMD3), n66 (IMD5) | IMD | RAN5#101 | +| CA_n25A-n77A | n77 (HD2), n25 (HM), n25 (IMD2),
n25 (IMD4), n25 (IMD5) | HD, HM, IMD | RAN5#101 | +| CA_n25A-n77(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n25A-n78A | n78 (HD2), 25 (IMD2) | HD, IMD | RAN5#101 | +| CA_n25A-n78(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n26A-n66A | n26 (IMD2) | IMD | RAN5#94-e | +| CA_n26A-n70A | n26 (IMD2) | IMD | RAN5#94-e | +| CA_n28A-n41A | - | NE | RAN5#91-e | +| CA_n28A-n77A | n77 (HD5), n28 (IMD5) | HD, IMD | RAN5#99 | +| CA_n28A-n77(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n28A-n78A | n78 (HD5) | HD | RAN5#99 | +| CA_n28A-n79A | - | NE | RAN5#91-e | +| CA_n29A-n66A | - | NE | RAN5#94-e | +| CA_n29A-n70A | - | NE | RAN5#94-e | +| CA_n29A-n71A | n29 (CBI) | CBI | RAN5#95-e | +| CA_n39A-n41A | - | NE | RAN5#100 | + +| | | | | +|---------------------------|-------------------------------------------|--------------|-----------| +| CA_n41A-n66A 3 | n66 (CBI), n66 (IMD5) | CBI | RAN5#97 | +| CA_n41A-n71A 3 | n41(HD4), n71 (IMD4) | HD | RAN5#98 | +| CA_n41A-n79A PC3 | - | NE | RAN5#83 | +| CA_n41A-n79A PC2 | n41 (CBI), n79 (CBI) | CBI | RAN5#100 | +| CA_n48A-n66A | n48 (HD2), n66 (IMD5) | HD, IMD | RAN5#94-e | +| CA_n48A-n66(2A) | (NOTE 2) | NE | RAN5#95-e | +| CA_n48A-n70A | n70 (IMD2) | IMD | RAN5#94-e | +| CA_n48A-n71A | - | NE | RAN5#94-e | +| CA_n48A-n71(2A) | - | NE | RAN5#95-e | +| CA_n48A-n77A | - | NE | RAN5#97-e | +| CA_n48B-n66A | (NOTE 2) | NE | RAN5#95-e | +| CA_n48B-n70A | (NOTE 2) | NE | RAN5#95-e | +| CA_n48B-n71A | - | NE | RAN5#95-e | +| CA_n48(2A)-n66A | (NOTE 2) | NE | RAN5#95-e | +| CA_n48(2A)-n66(2A) | (NOTE 2) | NE | RAN5#96-e | +| CA_n48(2A)-n70A | (NOTE 2) | NE | RAN5#95-e | +| CA_n48(2A)-n71A | - | NE | RAN5#95-e | +| CA_n48(2A)-n71(2A) | - | NE | RAN5#96-e | +| CA_n66A-n70A | - | NE | RAN5#94-e | +| CA_n66A-n71A | n66 (IMD4) | IMD | RAN5#87-e | +| CA_n66A-n77A PC3 | n77 (HD2), n66(IMD2), n66(IMD5) | HD, IMD | RAN5#99 | +| CA_n66A-n77A PC2 | n77 (HD2), n66(IMD2), n66(IMD5), n66(CBI) | HD, IMD, CBI | RAN5#99 | +| CA_n66A-n77(2A) PC3 | (NOTE 2) | NE | RAN5#101 | +| CA_n66A-n77C | (NOTE 2) | NE | RAN5#101 | +| CA_n66A-n78A | n78 (HD2), n66(IMD5) | HD, IMD | RAN5#101 | +| CA_n66A-n78(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n70A-n71A | n70 (HD3), n70 (IMD4) | HD, IMD | RAN5#85 | +| CA_n71A-n77A | n71 (IMD5) | IMD | RAN5#97-e | + +NOTE 1: Notations used + +NE: Non-exception as defined in TS 38.101-1 [5], meaning single carrier NR requirements apply. + +HD: UL Harmonic Distortion, as defined in TS 38.101-1 [5], 7.3A.4 + +HM: RX Harmonic Mixing, as defined in TS 38.101-1 [5], 7.3A.4 + +IMD: Intermodulation Distortion, as defined in TS 38.101-1 [5], 7.3A.5 + +CBI: Cross Band Isolation, as defined in TS 38.101-1 [5], 7.3A.6 + +NOTE 2: Exception for this band is tested with two carrier case. + +NOTE 3: Only single uplink analysed. IMD exception not yet covered. + +**Table 4.1.3.1-3: Reference Sensitivity test cases per CA configuration (three bands)** + +| CA config | Three band refsens exception, victim band (Note 1) | Requirement coverage (Note 1) | Test point analysis updated | +|----------------------|------------------------------------------------------------------|-------------------------------|-----------------------------| +| CA_n1A-n3A-n28A | - | NE | RAN5#101 | +| CA_n1A-n3A-n78A | - | NE | RAN5#101 | +| CA_n1A-n3A-n78A | n3(IMD2), n78(IMD2, IMD4) | IMD | RAN5#101 | +| CA_n2A-n5A-n48A | n2(IMD3), n48(IMD3) | IMD | RAN5#100 | +| CA_n2A-n5A-n77A PC3 | n2(IMD3), n5 (IMD5), n77(IMD3) | IMD | RAN5#98 | +| CA_n2A-n5A-n77A PC2 | n2(IMD3), n5 (IMD5) | IMD | RAN5#100 | +| CA_n2A-n48A-n66A | n48(IMD2), n66 (IMD4), n2(IMD2) | IMD | RAN5#100 | +| CA_n2A-n48A-n77A | - | NE | RAN5#100 | +| CA_n2A-n66A-n77A PC3 | n2(IMD2, IMD4, IMD5), n66 (IMD2, IMD4, IMD5), n77(IMD2, IMD4) | IMD | RAN5#98 | +| CA_n2A-n66A-n77A PC2 | n2(IMD2), n66 (IMD2) | IMD | RAN5#100 | +| CA_n3A-n28A-n41A | n3(IMD2), n28(IMD2), n41(IMD2, IMD3) | IMD | RAN5#101 | +| CA_n3A-n28A-n77A | n3(IMD3), n28(IMD3), n77(IMD3) | IMD | RAN5#101 | +| CA_n3A-n28A-n78A | - | NE | RAN5#101 | +| CA_n5A-n48A-n66A | n48(IMD5) | IMD | RAN5#100 | +| CA_n5A-n48A-n77A | - | NE | RAN5#100 | +| CA_n5A-n66A-n77A PC3 | n66 (IMD3), n77(IMD3, IMD4, IMD5) | IMD | RAN5#98 | +| CA_n5A-n66A-n77A PC2 | n66 (IMD3) | IMD | RAN5#100 | +| CA_n25A-n66A-n77 | n25 (IMD2, IMD3, IMD4, IMD5), n66 (IMD2, IMD3, IMD4, IMD5, IMD7) | IMD | RAN5#101 | +| CA_n25A-n66A-n77(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n25A-n66A-n78 | n78(IMD2) | IMD | RAN5#101 | +| CA_n25A-n66A-n78(2A) | (NOTE 2) | NE | RAN5#101 | +| CA_n26A-n66A-n70A | - | NE | RAN5#94-e | +| CA_n26A-n66(2A)-n70A | - | NE | RAN5#96-e | +| CA_n28A-n41A-n79A | n28(IMD3), n41 (IMD4), n79(IMD3) | IMD | RAN5#100 | +| CA_n29A-n66A-n70A | - | NE | RAN5#89-e | +| CA_n41A-n66A-n71A | - | NE | RAN5#99 | +| CA_n48A-n66A-n71(2A) | - | NE | RAN5#96-e | +| CA_n48A-n66(2A)-n70A | - | NE | RAN5#96-e | +| CA_n48A-n66(2A)-n71A | - | NE | RAN5#96-e | +| CA_n48A-n70A-n71(2A) | - | NE | RAN5#96-e | +| CA_n48B-n66A-n70A | - | NE | RAN5#96-e | +| CA_n48B-n66A-n71A | - | NE | RAN5#96-e | +| CA_n48A-n66A-n77A | - | NE | RAN5#100 | +| CA_n48B-n70A-n71A | - | NE | RAN5#96-e | +| CA_n48(2A)-n66A-n70A | - | NE | RAN5#96-e | +| CA_n48(2A)-n66A-n71A | - | NE | RAN5#96-e | +| CA_n48(2A)-n70A-n71A | - | NE | RAN5#96-e | +| CA_n66A-n70A-n71A | - | NE | RAN5#87-e | + +NOTE 1: Notations used +NE: Non-exception as defined in TS 38.101-1 [5], meaning single carrier NR requirements apply. +HD: UL Harmonic Distortion, as defined in TS 38.101-1 [5], 7.3A.4 +HM: RX Harmonic Mixing, as defined in TS 38.101-1 [5], 7.3A.4 +IMD: Intermodulation Distortion, as defined in TS 38.101-1 [5], 7.3A.5 +CBI: Cross Band Isolation, as defined in TS 38.101-1 [5], 7.3A.6 +NOTE 2: Exception for this band is tested with three carrier case. + +**Table 4.1.3.1-4: Reference Sensitivity test cases per CA configuration (four bands)** + +| CA config | Four band refsens exception, victim band (Note 1) | Requirement coverage (Note 1) | Test point analysis updated | +|----------------------|---------------------------------------------------|-------------------------------|-----------------------------| +| CA_n1A-n3A-n28A-n78A | - | NE | RAN5#101 | + +NOTE 1: No exceptions can occur for four bands. +NE: Non-exception as defined in TS 38.101-1 [5], meaning single carrier NR requirements apply. + +**Table 4.1.3.1-5: Reference Sensitivity test cases per CA configuration (five bands)** + +| CA config | Five band refsens exception, victim band (Note 1) | Requirement coverage (Note 1) | Test point analysis updated | +|-------------------------------------------------|---------------------------------------------------|-------------------------------|-----------------------------| +| TBD | – | TBD | TBD | +| NOTE 1: No exceptions can occur for five bands. | | | | + +For CA configurations affected by exceptions the test frequency cannot be freely chosen. One test frequency per exception requirement is sufficient to test the requirement, in addition to testing the case where the exception is avoided. This is indicated in Table 4.1.3.1-6. Exceptions in TS 38.101-1 [5] clause 7.3A.5 (2UL intermodulation) and 7.3A.6 (cross band isolation) are not specified since the test frequency and channel bandwidth is already specified in TS 38.101-1 [5]. + +**Table 4.1.3.1-6: Test frequency selection per band pair for bands and test points with exceptions avoidable by test frequency setting (UL harmonics, Rx mixing)** + +| Band pair (Note 2) | Frequency | Channel BW [MHz] | Comment | +|--------------------|------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n1A / n28A | UL 713 MHz / DL 2139 MHz | 5/5 | Exception Note 3 of TS38.101 table 7.3A.4-1 | +| | UL 713 MHz / DL 2139 MHz | 50/5 | Exception Note 3 of TS38.101 table 7.3A.4-1 | +| n1A / n77A | Mid / Low | Highest(50)/Highest(100) | Non-exception. Not overlapping interference since $BWINT=2*50$ MHz, $FINT (550) \geq (100+100)/2$ . | +| | Mid / 3900 | 5/10 | Exception Note 2 of TS 38.101 table 7.3A.4-1 | +| | Mid / 3900 | 20/100 | Exception Note 2 of TS 38.101 table 7.3A.4-1 | +| | Mid / 3875 | 5/10 | Exception Note 6 of TS 38.101 table 7.3A.4-1 | +| n2A/n48A | Mid/Mid | Highest(40)/Highest(40) | Non-exception. Not overlapping interference since $BWINT=2*40$ MHz, $FINT (135) \geq (80+40)/2$ . | +| n2A/n48A | UL 1860 MHz / DL 3690 MHz | 5/10 | Exception Note 6 of TS 38.521 Table 7.3A.0.4-1 | +| n2A/n77A | Mid / 3850 Mhz | 20/100 | Non-exception. Not overlapping interference since $BWINT=2*20$ MHz, $FINT (90) \geq (40+100)/2$ . | +| | UL 1880 MHz / DL 3760 MHz | 5/10 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1880 MHz / DL 3760 MHz | 10/100 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1880 MHz / DL 3735 MHz | 5/10 | Exception Note 6 of TS 38.101 Table 7.3A.4-1 | +| | UL 3920 MHz/ Mid | 10/5 | Exception Note 7 of TS 38.101 Table 7.3A.4-4 | +| | UL 3920 MHz/ Mid | 20/20 | Exception Note 7 of TS 38.101 Table 7.3A.4-4 | +| n3A / n77A | Mid/High | Highest/Highest | Non-exception. | +| | Mid/3495 MHz | 5/10 | Exception Note 2 of TS38.101 table 7.3A.4-1 | +| | Mid/3495 MHz | 10/100 | Exception Note 2 of TS38.101 table 7.3A.4-1 | +| | Mid/3470 MHz | 5/10 | Exception Note 6 of TS38.101 table 7.3A.4-1 | +| n3A / n78A | Mid/High | Highest(50)/Highest(100) | Non-exception. Not overlapping interference since $BWINT=2*50$ MHz, $FINT (255) \geq (100+100)/2$ . | +| | Mid/3495 MHz | 5/10 | Exception Note 2 of TS38.101 table 7.3A.4-1 | +| | Mid/3465 | 10/100 | Exception Note 2 of TS38.101 table 7.3A.4-1 | +| | Mid/3470 MHz | 5/10 | Exception Note 6 of TS38.101 table 7.3A.4-1 | +| n5A/n77A | Mid/Mid | Highest(20)/Highest(100) | Non-exception. Not overlapping interference since $BWINT=5*20$ MHz, $FINT (432.5) \geq (100+100)/2$ for HD5 and $BWINT=4*20+100$ MHz, $FINT (224) \geq (180+100)/2$ for HM4. | +| | UL 836.5 MHz / DL 3346 MHz | 5/10 | Exception Note 4 of TS 38.101-1 table 7.3A.4-1 | +| | UL 846.5 MHz / DL 3386 MHz | 5/100 | Exception Note 4 of TS 38.101-1 table 7.3A.4-1 | +| | UL 826.5 MHz / DL 4132.5 MHz | 5/10 | Exception Note 5 TS 38.101-1 table 7.3A.4-1 | +| | UL 826.5 MHz / DL 4132.5 MHz | 5/100 | Exception Note 5 of TS 38.101-1 table 7.3A.4-1 | +| n5A/n77A | UL 3526 MHz / DL Mid | 20/20 | Exception Note 5 of TS 38.101 Table 7.3A.4-4 | +| | UL 3526 MHz / DL Mid | 10/10 | Exception Note 5 of TS 38.101 Table 7.3A.4-4 | +| n5A / n78A | Mid/High | Highest(20)/Highest(100) | Non-exception. Not overlapping interference since $BWINT=5*20$ MHz, $FINT (432.5) \geq (100+100)/2$ for HD5 and $BWINT=4*20+100$ MHz, $FINT (224) \geq (180+100)/2$ for HM4. | +| | Mid/3346 MHz | 5/10846.5 | Exception Note 4 of TS 38.101 [5] table 7.3A.4-1 | +| | /3386 MHz | 5/100 | Exception Note 4 of TS 38.101 [5] table 7.3A.4-1 | + +| | | | | +|--------------------|------------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| n8A / n78A | Mid/High | Highest(20)/Highest(100) | Non-exception. Not overlapping interference since $BW_{INT}=4*20$ MHz, $F_{INT} (160) \geq (80+100)/2$ . | +| | Mid/3590 MHz | 5/10 | Exception Note 4 of TS38.101 table 7.3A.4-1 | +| | Mid/3590 MHz | 5/100 | Exception Note 4 of TS38.101 table 7.3A.4-1 | +| n20 / n78A | Mid/High | 5/10 | Exception Note 4 of TS38.101 table 7.3A.4-1 | +| | Mid/3388 MHz | 5/100 | Exception Note 4 of TS38.101 table 7.3A.4-1 | +| n25A / n77A | Mid/High | Highest(45)/Highest(100) | Non-exception. Not overlapping interference since $BW_{INT}=2*45$ MHz, $F_{INT} (385) \geq (90+100)/2$ for HD2. | +| | UL 1882.5 MHz / DL 3765 MHz | 5/10 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1882.5 MHz / DL 3765 MHz | 10/100 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1852.5 MHz / DL 3680 MHz | 5/10 | Exception Note 6 of TS 38.101 Table 7.3A.4-1 | +| | UL 3925 MHz / DL 1962.5 MHz | 5/10 | Exception Note 7 of TS 38.101 Table 7.3A.4-4 | +| n25A / n77A | UL 3925 MHz / DL 1962.5 MHz | 40/20 | Exception Note 7 of TS 38.101 Table 7.3A.4-4 | +| | High/Low | Highest(45)/Highest(100) | Non-exception. Not overlapping interference since $BW_{INT}=2*45$ MHz, $F_{INT} (435) \geq (90+100)/2$ for HD2. | +| | UL 1882.5 MHz / DL 3765 MHz | 5/10 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1882.5 MHz / DL 3765 MHz | 10/100 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1852.5 MHz / DL 3680 MHz | 5/10 | Exception Note 6 of TS 38.101 Table 7.3A.4-1 | +| n28 / n77A | Low / Low | Highest/Highest | Non-exception | +| | UL 705.5 MHz / DL 3527.5 MHz | 5/10 | Exception Note 5 of TS38.101 table 7.3A.4-1 | +| | UL 705.5 MHz / DL 3527.5 MHz | 5/100 | Exception Note 5 of TS38.101 table 7.3A.4-1 | +| n28A / n78A | Mid/High | Highest(20)/Highest(100) | Non-exception. Not overlapping interference since $BW_{INT}=5*20$ MHz, $F_{INT} (110) \geq (100+100)/2$ for HD5 | +| | UL 713 MHz / DL 3565 MHz | 20/100 | Exception Note 6 of TS 38.101 [5] table 7.3A.4-1 | +| | UL 713 MHz / DL 3535 MHz | 20/20 | Exception Note 7 of TS 38.101 [5] table 7.3A.4-1 | +| n41A/n71A | UL Low/DL Low | Highest/Highest | Non-exception. Not overlapping interference since $BW_{INT}=4*20$ MHz, $F_{INT} (146) \geq (80+100)/2$ for HD4. To be used in test cases 7.3A.1 to 7.3A.4 | +| | UL Low / DL 2662 MHz | UL 5 / DL 10 | Exception Note 4 of TS 38.101 Table 7.3A.4-1 | +| | UL Low / DL High | UL 5 / DL 100 | Exception Note 4 of TS 38.101 Table 7.3A.4-1 | +| n66A/n77A | Mid/Mid | Highest(45)/Highest(100) | Non-exception. Not overlapping interference since $BW_{INT}=2*45$ MHz, $F_{INT} (260) \geq (90+100)/2$ . | +| | UL 1750 MHz / DL 3500 MHz | 5/10 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1750 MHz / DL 3500 MHz | 20/100 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1712.5 MHz / DL 3400 MHz | 5/10 | Exception Note 6 of TS 38.101 Table 7.3A.4-1 | +| n66A/n78A | Mid/Mid | Highest(45)/Highest(100) | Non-exception. Not overlapping interference since $BW_{INT}=2*45$ MHz, $F_{INT} (330) \geq (90+100)/2$ . | +| | UL 1750 MHz / DL 3500 MHz | 5/10 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1750 MHz / DL 3500 MHz | 20/100 | Exception Note 2 of TS 38.101 Table 7.3A.4-1 | +| | UL 1712.5 MHz / DL 3400 MHz | 5/10 | Exception Note 6 of TS 38.101 Table 7.3A.4-1 | +| n70A / n71A | Mid/High | Highest(25)/Highest(20) | Non-exception. Not overlapping interference since $BW_{INT}=3*20$ MHz, $F_{INT} (56.5) \geq (60+25)/2$ . | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--------------|---------------------------------------------------------------------------| +| | Low/Low | Highest / 10 | Exception Note 9 of TS38.101 table 7.3A.4-1
n71 UL RB allocation 20@10 | +| | Low/Low | 5 / 5 | Exception Note 9 of TS38.101 table 7.3A.4-1
n71 UL RB allocation 8@10 | +| NOTE 1: This selection is used in test case 7.3A.1_1 unless otherwise stated. | | | | +| NOTE 2: Aggressor band in bold. | | | | +| NOTE 3: Non-exception test frequencies are required to be used in test cases 7.3A.1, 7.3A.2, 7.3A.3, 7.3A.4 which are also referred to in other Rx test cases under chapter 7 of TS38.521-1 [2] | | | | + +#### 4.1.3.2 Spurious emissions test cases for FR1 UL CA + +In this case, it is sufficient to verify the minimum requirements in frequency ranges affected by 2nd and 3rd order intermodulation products. The frequency ranges and UL RB allocations used in the test are calculated here. + +The analyses are performed per CA configuration and are stored as zip-files as defined in annex A. + +**Table 4.1.3.2-1: Frequency range analysis availability per CA configuration** + +| CA config | Number of test point | Justification | Comments | +|--------------|----------------------|----------------------------------------------|----------| +| CA n1A-n3A | | 38.521-1_TpAnalysisSpur(CA n1A-n3A).zip | RAN5#99 | +| CA n1A-n8A | 1 | 38.521-1_TpAnalysisSpur(CA n1A-n8A).zip | RAN5#98 | +| CA n1A-n78A | 3 | 38.521-1_TpAnalysisSpur(CA n1A-n78A) v3.zip | RAN5#97 | +| CA n1A-n79A | 4 | 38.521-1_TpAnalysisSpur(CA n1A-n79A).zip | RAN5#97 | +| CA n2A-n14A | 2 | 38.521-1_TpAnalysisSpur(CA n2A-n14A).zip | RAN5#101 | +| CA n2A-n77A | 3 | 38.521-1_TpAnalysisSpur(CA n2A-n77A) v3.zip | RAN5#100 | +| CA n2A-n5A | 3 | 38.521-1_TpAnalysisSpur(CA n2A n5A) v1.zip | RAN5#100 | +| CA n2A-n48A | 3 | 38.521-1_TpAnalysisSpur(CA n2A n48A) v1.zip | RAN5#100 | +| CA n3A-n8A | 3 | 38.521-1_TpAnalysisSpur(CA n3A-n8A).zip | RAN5#100 | +| CA n3A-n28A | 3 | 38.521-1_TpAnalysisSpur(CA n3A-n28A).zip | RAN5#101 | +| CA n3A-n41A | 6 | 38.521-1_TpAnalysisSpur(CA n3A-n41A).zip | RAN5#97 | +| CA n3A-n77A | 1 | 38.521-1_TpAnalysisSpur(CA n3A-n77A).zip | RAN5#100 | +| CA n3A-n78A | 4 | 38.521-1_TpAnalysisSpur(CA n3A-n78A) v1.zip | RAN5#97 | +| CA n5A-n48A | 7 | 38.521-1_TpAnalysisSpur(CA n5A-n48A) v1.zip | RAN5#100 | +| CA n5A-n66A | 3 | 38.521-1_TpAnalysisSpur(CA n5A-n66A).zip | RAN5#100 | +| CA n5A-n77A | 7 | 38.521-1_TpAnalysisSpur(CA n5A-n77A) v3.zip | RAN5#100 | +| CA n8A-n78A | 5 | 38.521-1_TpAnalysisSpur(CA n8A-n78A) v1.zip | RAN5#97 | +| CA n14A-n30A | 2 | 38.521-1_TpAnalysisSpur(CA n14A-n30A).zip | RAN5#101 | +| CA n14A-n66A | 2 | 38.521-1_TpAnalysisSpur(CA n14A-n66A).zip | RAN5#101 | +| CA n14A-n77A | 2 | 38.521-1_TpAnalysisSpur(CA n14A-n77A).zip | RAN5#101 | +| CA n20A-n78A | 5 | 38.521-1_TpAnalysisSpur(CA n20A-n78A).zip | RAN5#100 | +| CA n24A-n41A | 5 | 38.521-1_TpAnalysisSpur(CA n24A-n41A).zip | RAN5#95e | +| CA n24A-n48A | 2 | 38.521-1_TpAnalysisSpur(CA n24A-n48A).zip | RAN5#95e | +| CA n24A-n77A | 4 | 38.521-1_TpAnalysisSpur(CA n24A-n77A).zip | RAN5#95e | +| CA n25A-n66A | 5 | 38.521-1_TpAnalysisSpur(CA n25A-n66A).zip | RAN5#101 | +| CA n25A-n77A | 3 | 38.521-1_TpAnalysisSpur(CA n25A-n77A).zip | RAN5#101 | +| CA n25A-n78A | 1 | 38.521-1_TpAnalysisSpur(CA n25A-n78A).zip | RAN5#101 | +| CA n26A-n66A | 1 | 38.521-1_TpAnalysisSpur(CA n26A-n66A).zip | RAN5#96e | +| CA n26A-n70A | 1 | 38.521-1_TpAnalysisSpur(CA n26A-n70A).zip | RAN5#96e | +| CA n28A-n41A | 4 | 38.521-1_TpAnalysisSpur(CA n28A-n41A) v1.zip | RAN5#97 | +| CA n28A-n77A | 1 | 38.521-1_TpAnalysisSpur(CA n28A-n77A).zip | RAN5#100 | +| CA n28A-n78A | 6 | 38.521-1_TpAnalysisSpur(CA n28A-n78A).zip | RAN5#99 | +| CA n28A-n79A | 1 | 38.521-1_TpAnalysisSpur(CA n28A-n79A).zip | RAN5#100 | +| CA n39A-n41A | 1 | 38.521-1_TpAnalysisSpur(CA n39A-n41A).zip | RAN5#97 | +| CA n41A-n79A | 8 | 38.521-1_TpAnalysisSpur(CA n41A-n79A) v1.zip | RAN5#97 | +| CA n48A-n66A | 1 | 38.521-1_TpAnalysisSpur(CA n48A-n66A) v1.zip | RAN5#97 | +| CA n48A-n70A | 2 | 38.521-1_TpAnalysisSpur(CA n48A-n70A).zip | RAN5#96e | +| CA n48A-n71A | 2 | 38.521-1_TpAnalysisSpur(CA n48A-n71A) v2.zip | RAN5#100 | +| CA n66A-n71A | 1 | 38.521-1_TpAnalysisSpur(CA n66A-n71A) v1.zip | RAN5#99 | +| CA n66A-n77A | 9 | 38.521-1_TpAnalysisSpur(CA n66A-n77A) v2.zip | RAN5#97 | +| CA n66A-n78A | 1 | 38.521-1_TpAnalysisSpur(CA n66A-n78A).zip | RAN5#101 | +| CA n70A-n71A | 1 | 38.521-1_TpAnalysisSpur(CA n70A-n71A).zip | RAN5#96e | +| CA n71A-n77A | 7 | 38.521-1_TpAnalysisSpur(CA n71A-n77A) v1.zip | RAN5#100 | + +## 4.2 Test point analysis for FR2 test cases in TS 38.521-2 + +### 4.2.1 Test point analysis per test case + +#### 4.2.1.1 FR2 single carrier, NR CA and UL MIMO test cases + +This clause contains information on test point analysis and test point selection for single carrier, NR CA and UL MIMO test cases in [3] clause 6 and 7 with information about transmitting test point selection for FR2 listed in table 4.2.1.1-1 and receiver test point selection in table 4.2.1.1-2. + +**Table 4.2.1.1-1: NR UE transmitter test point selection for FR2** + +| Subclause | Number of test points | Justification in attachment | Comments | +|--------------------------------------------------------------|----------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| 6.2.1 UE maximum output power | x | "38.521-2_TPanalysis_6.2.1_MOP_v3.zip" | RAN5#94-e | +| 6.2.2 UE maximum output power reduction | power class 1: 90
power class 2&3&4: 84 | "38.521-2_TPanalysis_6.2.2_MPR_6.5.2.1_SEM_6.5.2.3_NR_ACLR_v6.zip" | RAN5#89-e
RAN5#90-e
RAN5#91-e
RAN5#92-e
RAN5#94-e
RAN5#95-e
RAN5#98 | +| 6.2.4_1 Configured transmitted power with Power Boost | x | "38.521-2_TPanalysis_6.2.1_MOP_v3.zip" | RAN5#96-e | +| 6.2.5 UE Maximum Output Power – EIRP with UL Gaps | x | "38.521-2_TPanalysis_6.2.5_EIRP_UL-Gaps_v1.zip" | RAN5#99 | +| 6.2A.1.1 UE maximum output power - EIRP and TRP for CA | TRP: 4
EIRP: 20 | "38.521-2_TPanalysis_6.2A.1.x_MOP_Spherical Coverage_CA_v1" | RAN5#84 | +| 6.2A.1.2 UE maximum output power - Spherical coverage for CA | 20 | "38.521-2_TPanalysis_6.2A.1.x_MOP_Spherical Coverage_CA_v1" | RAN5#84 | +| 6.2A.2 UE maximum output power reduction for CA | FFS | "38.521-2_TPanalysis_6.2A.2_MPR_v3.zip" | RAN5#84
RAN5#96-e
RAN5#99 | +| 6.2D.1 UE maximum output power for UL MIMO | x | "38.521-2_TPanalysis_6.2.1_MOP_v3.zip" | RAN5#94-e | +| 6.2D.2 UE maximum output power reduction for UL MIMO | x | "38.521-2_TPanalysis_6.2.2_MPR_6.5.2.1_SEM_6.5.2.3_NR_ACLR_v6.zip" | RAN5#91-e
RAN5#92-e
RAN5#94-e
RAN5#95-e
RAN5#98 | +| 6.3.1 Minimum output power | 9 | "38.521-2_TPanalysis_6.3.1_MinOP_v2.zip" | RAN5#84 | +| 6.3.2 Transmit OFF power | 3 | "38.521-2_TPanalysis_6.3.2_Tx_OFF_power" | RAN5#83 | +| 6.3.3.2 General ON/OFF time mask | 9 | "38.521-2_TPanalysis_6.3.3.2_OnOff.zip" | RAN5#92-e | +| 6.3.4.2 Absolute power tolerance | 8 | "38.521-2_TPanalysis_6.3.4.2_AbsPtol.zip" | RAN5#91-e | +| 6.3.4.3 Relative power tolerance | Ramp up: 1
Ramp down: 1
Alternating: 1 | "38.521-2_TPanalysis_6.3.4.3_RelPtol_v3.zip" | RAN5#82
RAN5#91-e
RAN5#93-e | +| 6.3.4.4 Aggregate power tolerance | PUCCH: 6
PUSCH: 6 | "38.521-2_TPanalysis_6.3.4.4_AggPtol_2.zip" | RAN5#82
RAN5#91-e | +| 6.3A.1.1 Minimum output power for CA (2UL CA) | 4 | "38.521-2_TPanalysis_6.3A.1.1_MinOP.zip" | RAN5#83 | +| 6.3A.2.1 Transmit OFF power for CA (2UL CA) | 3 | "38.521-2_TPanalysis_6.3A.2.1_Tx_OFF_Power_CA.zip" | RAN5#88-e | + +| | | | | +|------------------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------|------------------------| +| 6.3A.4.2.1 Absolute power tolerance for CA (2UL CA) | 6 | 38.521-2_TPanalysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.2.2 Absolute power tolerance for CA (3UL CA) | 6 | 38.521-2_TPanalysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.2.3 Absolute power tolerance for CA (4UL CA) | 6 | 38.521-2_TPanalysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.2.4 Absolute power tolerance for CA (5UL CA) | 6 | 38.521-2_TPanalysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.2.5 Absolute power tolerance for CA (6UL CA) | 6 | 38.521-2_TP analysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.2.6 Absolute power tolerance for CA (7UL CA) | 6 | 38.521-2_TP analysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.2.7 Absolute power tolerance for CA (8UL CA) | 6 | 38.521-2_TPanalysis_6.3A.4.2.1_AbsPCTol_CA.zip | RAN5#85 | +| 6.3A.4.4 Aggregate power tolerance for CA | 1 | 38.521-2_TPanalysis_6.3A.4.4_Aggregate power tolerance for CA.zip | RAN5#92-e | +| 6.3D.1 Minimum output power for UL MIMO | 9 | "38.521-2_TPanalysis_6.3.1_MinOP_v2.zip" | RAN5#84 | +| 6.3D.3.4 SRS time mask for UL-MIMO | 18 | "38.521-2_TPanalysis_6.3.3.2_SRS_M_UL-MIMO.zip" | RAN5#85 | +| 6.4.1 Frequency error | 1 | "38.521-2_TPanalysis_6.4.1_FreqErr.zip" | RAN5#80 | +| 6.4.2.1 Error Vector Magnitude | PUSCH: 168
PUCCH: 24
PRACH: 24 | "38.521-2_TPanalysis_6.4.2.1_EVM.zip" | RAN5#3-5G-NR Adhoc | +| 6.4.2.1_1 Error vector magnitude with Power Boost | PUSCH: 36
PUCCH: 9 | "38.521-2_TPanalysis_6.2.1_MOP_v3.zip" | RAN5#97 | +| 6.4.2.2 Carrier leakage | 3 | "38.521-2_TPanalysis_6.4.2.2_CarrLeak_v3.zip" | RAN5#93-e | +| 6.4.2.3 In-band emissions | PUSCH: 36
PUCCH: 18 | "38.521-1_TPanalysis_6.4.2.3_IE_v2.zip" | RAN5#89-e | +| 6.4.2.4 EVM equalizer spectrum flatness | 18 | "38.521-2_TP analysis_6.4.2.4_6.4.2.5_EVMequalizerSpectrumFlatness.zip" | RAN5#3-5G-NR Adhoc | +| 6.4.2.5 EVM spectral flatness for pi/2 BPSK modulation with spectrum shaping | 9 | "38.521-2_TP analysis_6.4.2.4_6.4.2.5_EVMequalizerSpectrumFlatness.zip" | RAN5#3-5G-NR Adhoc | +| 6.4.2.6 Phase continuity requirements for DMRS bundling | 90 | "38.521-2_TPanalysis_6.4.2.6_Phase_Continuity_v1.zip" | RAN5#100 | +| 6.4A.1 Frequency error for CA | N (1 test point per UL carrier) | "38.521-2_TPanalysis_6.4A.1_FreqErr_CA_v2.zip" | RAN5#87-e
RAN5#90-e | +| 6.4A.2.1 Error Vector Magnitude for CA | 224 | "38.521-2_TPanalysis_6.4A.2.1_EVM_CA.zip" | RAN5#91-e | + +| | | | | +|-------------------------------------------------------------------|----------------------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 6.4A.2.2 Carrier leakage for CA | 2 | "38.521-2_TPanalysis_6.4A.2.2_CarrLeak_CA_v3.zip" | RAN5#93-e | +| 6.4D.3 Time alignment error for UL MIMO | 6 | "38.521-2_TPanalysis_6.4D.3_TAE_MIMO.zip" | RAN5#92-e | +| 6.5.1 Occupied Bandwidth | 12 | "38.521-2_TPanalysis_6.5.1_OccBW_v3.zip" | RAN5#89-e
RAN5#91-e | +| 6.5.2.1 Spectrum Emission Mask | 90 | "38.521-2_TPanalysis_6.2.2_MPR_6.5.2.1_SEM_6.5.2.3_NR_ACLR_v6.zip" | RAN5#2-5G-NR Adhoc
RAN5#79
RAN5#80
RAN5#89-e
RAN5#90-e
RAN5#91-e
RAN5#92-e
RAN5#94-e
RAN5#95-e
RAN5#98 | +| 6.5.2.1_1 Spectrum Emission Mask with Power Boost | x | "38.521-2_TPanalysis_6.5.2.1_1 SEM with Power Boost_v1.zip" | RAN5#97 | +| 6.5.2.3 Adjacent Channel Leakage Ratio | TBD | "38.521-2_TPanalysis_6.2.2_MPR_6.5.2.1_SEM_6.5.2.3_NR_ACLR_v6.zip" | RAN5#2-5G-NR Adhoc
RAN5#89-e
RAN5#90-e
RAN5#91-e
RAN5#92-e
RAN5#94-e
RAN5#95-e
RAN5#98 | +| 6.5.3.1 Spurious emissions | 4 | "38.521-2_TPanalysis_6.5.3_TxSpurious_v3.zip" | RAN5#94-e | +| 6.5.3.1_1 Transmitter Spurious emissions with Power Boost | x | "38.521-2_TPanalysis_6.5.3.1_1_6.5.3.2.1_1_6.5.3.3_1_TxSpurious with Power Boost_v1.zip" | RAN5#97 | +| 6.5.3.2 Spurious emissions UE band co-existence | 4 | "38.521-2_TPanalysis_6.5.3_TxSpurious_v3.zip" | RAN5#94-e | +| 6.5.3.2_1 Spurious emission band UE co-existence with Power Boost | x | "38.521-2_TPanalysis_6.5.3.1_1_6.5.3.2.1_1_6.5.3.3_1_TxSpurious with Power Boost_v1.zip" | RAN5#97 | +| 6.5.3.3 Additional spurious emission | NS202: 4
NS203: 4 | "38.521-2_TPanalysis_6.2.3_AMPR_NS_202.zip"
"38.521-2_TPanalysis_6.2.3_AMPR_NS_203.zip" | RAN5#90-e | +| 6.5.3.3_1 Additional spurious emissions with Power Boost | x | "38.521-2_TPanalysis_6.5.3.1_1_6.5.3.2.1_1_6.5.3.3_1_TxSpurious with Power Boost_v1.zip" | RAN5#97 | +| 6.5A.2.1 Spectrum Emission Mask for CA | 30 | "38.521-2_TPanalysis_6.5A.2.1_SEM for CA_v2.zip" | RAN5#89-e
RAN5#99 | +| 6.5A.2.2 Adjacent channel leakage ratio for CA | 52 | "38.521-2_TPanalysis_6.5A.2.2_ACLR for CA_v2.zip" | RAN5#89-e
RAN5#99 | +| 6.5A.3.1 Spurious emissions for CA | 4 | 38.521-2_TPanalysis_6.5A.3_Spur_CA_v2.zip | RAN5#91-e
RAN5#99 | +| 6.5A.3.2 Spurious emissions for CA | 4 | 38.521-2_TPanalysis_6.5A.3_SpurCoEx_CA_v2.zip | RAN5#93-e
RAN5#99 | + +| | | | | +|-------------------------------------------------------------|----------------------|--------------------------------------------------------------------------------------------|-------------------------------------------------------------| +| 6.5D.1 Occupied Bandwidth for UL MIMO | 12 | "38.521-2_TPanalysis_6.5.1_OccBW_v3.zip" | RAN5#91-e | +| 6.5D.2.1 Spectrum Emission Mask for UL MIMO | x | "38.521-2_TPanalysis_6.2.2_MPR_6.5.2.1_SEM_6.5.2.3_NR_ACLR_v6.zip" | RAN5#91-e
RAN5#92-e
RAN5#94-e
RAN5#95-e
RAN5#98 | +| 6.5D.2.2 Adjacent channel leakage ratio for UL MIMO | x | "38.521-2_TPanalysis_6.2.2_MPR_6.5.2.1_SEM_6.5.2.3_NR_ACLR_v6.zip" | RAN5#91-e
RAN5#92-e
RAN5#94-e
RAN5#95-e
RAN5#98 | +| 6.5D.3.1 Transmitter Spurious emissions for UL MIMO | 4 | "38.521-2_TPanalysis_6.5.3_TxSpurious_v3.zip" | RAN5#94-e | +| 6.5D.3.2 Spurious emission band UE co-existence for UL MIMO | 4 | "38.521-2_TPanalysis_6.5.3_TxSpurious_v3.zip" | RAN5#94-e | +| 6.5D.3.3 Additional spurious emissions for UL MIMO | NS202: 4
NS203: 4 | "38.521-2_TPanalysis_6.2.3_AMPR_NS_202.zip"
"38.521-2_TPanalysis_6.2.3_AMPR_NS_203.zip" | RAN5#94-e | +| 6.6 Beam Correspondence | 6 | "38.521-2_TPanalysis_6.6_Beam_Correspond_v1.zip" | RAN5#85 | + +Table 4.2.1.1-2: NR UE receiver test point selection for FR2 + +| Subclause | Number of test points | Justification in attachment | Comments | +|-----------------------------------|-----------------------|--------------------------------------------------------------|-----------| +| 7.3 Reference sensitivity | 9 | "38.521-2_TPanalysis_7.3_RefSense.zip" | RAN5#80 | +| 7.3A Reference sensitivity for CA | 9 | "38.521-2_TPanalysis_7.3A_RefSenseCA.zip" | RAN5#86-e | +| 7.4 Maximum input level | 6 | "38.521-2_TPanalysis_7.4_Maximum input level_v1.zip" | RAN5#93-e | +| 7.4A Maximum input level for CA | 2 | "38.521-2_TPanalysis_7.4A_Maximum input level for CA_v1.zip" | RAN5#93-e | +| 7.5 Adjacent channel selectivity | 3 | "38.521-2_TPanalysis_7.5_ACS_v1.zip" | RAN5#83 | +| 7.6.2 In Band Blocking | 3 | "38.521-2_TPanalysis_7.6.2_InB_Block_v1.zip" | RAN5#83 | + +### 4.2.2 Test point analysis per NS value + +#### 4.2.2.1 A-MPR and A-SE FR2 test cases for single carrier + +This section contains information on test point selection for test case 6.2.3 in [3] Additional Maximum Power Reduction (A-MPR) as well as the related spectrum emissions test case 6.5.3.3 in [3] Additional Spurious emission (A-SE). Selection of test points should include some possible worst combinations based on the A-MPR and spectrum emissions characteristics specified for each NS value. The number of test points should be realistic. + +Since A-MPR is defined by RAN4 together with A-Spurious requirements, a combined analysis is required. In general, the following non-compliant UE behaviours need to be checked: + +- UE apply too much A-MPR (more than RAN4 allow) +- UE apply to little A-MPR (causing too much spectrum emissions) + +Case A can be verified in A-MPR test case + +Case B can be verified in A-SE test case if it is ensured that the same test point is tested inside A-MPR test. Therefore, the test points in spectrum emissions test case must be a subset of the test points in the A-MPR test case. + +Note: Even if there are identical test points in the MPR test case the A-MPR test case is still needed to verify UE output power when NS-value is signalled. + +**Table 4.2.2.1-1: NS value specific test points for A-MPR single carrier** + +| NS label | Number of test points | Justification | Comments | +|-----------|----------------------------------------------------------------------------------------------|-------------------------------------------------|-----------| +| NS_202 | 6.2.3: 3
6.5.3.3: 3
6.2D.3: 3
6.5D.3.3: 3 | "38.521-2_TPanalysis_6.2.3_AMPR_NS_202_v3.zip" | RAN5#95-e | +| NS_203 | 6.2.3: 3
6.5.3.3: 3
6.2D.3: 3
6.5D.3.3: 3 | "38.521-2_TPanalysis_6.2.3_AMPR_NS_203_v3.zip" | RAN5#95-e | +| CA_NS_203 | 6.2A.3.1: 1
6.2A.3.2: 1
6.2A.3.3: 1
6.5A.3.3.1: 1
6.5A.3.3.2: 1
6.5A.3.3.3: 1 | "38.521-2_TPanalysis_6.2A.3_AMPR_CA_NS_203.zip" | RAN5#101 | + +#### 4.2.2.2 A-MPR and A-SE FR2 test cases for CA + +This section contains information on test point selection for test cases 6.2A.3.1, 6.2A.3.2, and 6.2A.3.3 in [3], UE additional maximum output power reduction for CA as well as the related spectrum emissions test case 6.5A.3.3.1, 6.5A.3.3.2, and 6.5A.3.3.3 in [3] Additional Spurious emission (A-SE) for CA. + +Selection of test points should include some possible worst combinations based on the A-MPR and spectrum emissions characteristics specified for each CA\_NS value. The number of test points should be realistic. + +Since A-MPR is defined by RAN4 together with A-Spurious requirements, a combined analysis is required. In general, the following non-compliant UE behaviours need to be checked: + +- a) UE apply too much A-MPR (more than RAN4 allow) +- b) UE apply too little A-MPR (causing too much spectrum emissions) + +Case A can be verified in A-MPR test case + +Case B can be verified in A-SE test case if it is ensured that the same test point is tested inside A-MPR test. Therefore, the test points in spectrum emissions test case must be a subset of the test points in the A-MPR test case. + +Note: Even if there are identical test points in the MPR test case the A-MPR test case is still needed to verify UE output power when NS-value is signalled. + +**Table 4.2.2.1-1: NS value specific test points for A-MPR single carrier** + +| NS label | Number of test points | Justification | Comments | +|-----------|----------------------------------------------------------------------------------------------|--------------------------------------------------|----------| +| CA_NS_202 | 6.2A.3.1: 4
6.2A.3.2: 4
6.2A.3.3: 4
6.5A.3.3.1: 4
6.5A.3.3.2: 4
6.5A.3.3.3: 4 | "38.521-2_TPanalysis_6.2.3_AMPR_CA_NS_202v1.zip" | RAN5#101 | + +### 4.2.3 Test point analysis per NR CA configuration + +#### 4.2.3.1 Reference Sensitivity test cases for FR2 NR CA + +Editor's note: TP analyses for FR2 NR CA will be added to this clause. + +## 4.3 Test point analysis for test cases in TS 38.521-3 + +### 4.3.1 Test point analysis per test case + +#### 4.3.1.1 EN-DC test cases + +Table 4.3.1.1-1: NR UE transmitter test point selection for EN-DC + +| Subclause | Number of test points | Justification in attachment | Comments | +|-------------------------------------------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------------------------|--------------------| +| 6.2B.1.1 UE Maximum Output Power for Intra-Band Contiguous EN-DC | 20 | "38.521-3_TPanalysis_6.2B.1.1_MOP_Intra_B_contig_v4.zip" | RAN5#88-e | +| 6.2B.1.2 UE Maximum Output Power for Intra-Band Non-Contiguous EN-DC | 40 | "38.521-3_TPanalysis_6.2B.1.2_MOP_Intra_B_non-contig_v2.zip" | RAN5#87-e | +| 6.2B.1.3 UE Maximum Output Power for Inter-Band EN-DC | 600 | "38.521-3_TPanalysis_6.2B.1.3_MOP_Inter_B_Config_v2.zip" | RAN5#86-e | +| 6.2B.1.3_1 UE Maximum Output Power for Inter-Band EN-DC within FR1 (2 E-UTRA CC, 1 NR CC) | 400 | "38.521-3_TPanalysis_6.2B.1.3_1_MOP_Inter_B_2_LTE_1NR.zip" | RAN5#95-e | +| 6.2B.2.1 UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | 1880 | "38.521-3_TPanalysis_6.2B.2.1_MPR_6.5B.2.1_SEM_6.5B.2.1.3_ACLR.zip" | RAN5#87-e | +| 6.2B.2.2 UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | 1140 | "38.521-3_TPanalysis_6.2B.2.2_MPR_6.5B.2.2.1_SEM_6.5B.2.2.3_ACLR_v1.zip" | RAN5#93-e | +| 6.2B.2.3 UE Maximum Output Power reduction for Inter-Band EN-DC within FR1 | Same as Table 4.1.1-1, test case 6.5.2 | Same as Table 4.1.1.1-1, test case 6.5.2. | RAN5#3-5G-NR Adhoc | +| 6.2B.2.4 UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 | Same as Table 4.1.1-1, test case 6.2.2 | Same as Table 4.1.1.1-1, test case 6.2.2 | RAN5#5-5G-NR-Adhoc | +| 6.2B.3.1 UE Additional Maximum Output Power reduction for Intra-band contiguous EN-DC | 340 | "38.521-3_TPanalysis_6.2B.3.1_AMPR_NS_04_v3.zip" | RAN5#81 | +| | 8 | "38.521-3_TPanalysis_6.2B.3.1_AMPR_NS_35.zip" | RAN5#3-5G-NR Adhoc | +| 6.2B.4.1.1 Configured Output Power Level for Intra-Band Contiguous EN-DC | -UE not supporting DPS: 90
-UE supporting DPS: 120 | "38.521-3_TPanalysis_6.2B.4.1.1_ConfiguredTP_Intra_B_Contig_v2.zip" | RAN5#86-e | +| 6.2B.4.1.2 Configured Output Power for Intra-Band Non-Contiguous EN-DC | -UE not supporting DPS: 70
-UE supporting DPS: 100 | "38.521-3_TPanalysis_6.2B.4.1.2_ConfiguredTP_Intra_B_Non-contig_v2.zip" | RAN5#86-e | +| 6.2B.4.1.3 Configured Output Power for Inter-Band EN-DC within FR1 | -UE not supporting DPS: 100
-UE supporting DPS: 140 | "38.521-3_TPanalysis_6.2B.4.1.3_ConfiguredTP_Inter_B_within_FR1_v3.zip" | RAN5#95-e | +| 6.2B.4.1.3_1 Configured Output Power for Inter-Band EN-DC within FR1 (2 E- | -UE not supporting DPS: 100
-UE supporting | "38.521-3_TPanalysis_6.2B.4.1.3_ConfiguredTP_Inter_B_within_FR1_v3.zip" | RAN5#95-e | + +| | | | | +|---------------------------------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------|--------------------| +| UTRA CCs, 1 NR CC) | DPS: 140 | | | +| 6.4B.2.1.3 In-band emissions for intra-band contiguous EN-DC | 36 | "38.521-3_TPanalysis_6.4B.2.1.3_IBE_Intra_B_contig_v1.zip" | RAN5#92-e | +| 6.5B.1.1 Occupied bandwidth for Intra-Band Contiguous EN-DC | X= intra-band ENDC channel BWs supported by UE | "38.521-3_TPanalysis_6.5B.1.1_OBW_Intra_B_contig.zip" | RAN5#3-5G-NR adhoc | +| 6.5B.2.1.1 Spectrum emissions mask for intra-band contiguous EN-DC | 304 | "38.521-3_TPanalysis_6.2B.2.1_MPR_6.5B.2.1_SEM_6.5B.2.1.3_ACLR.zip" | RAN5#87-e | +| 6.5B.2.1.3 Adjacent channel leakage ratio for intra-band contiguous EN-DC | 2160 | "38.521-3_TPanalysis_6.2B.2.1_MPR_6.5B.2.1_SEM_6.5B.2.1.3_ACLR.zip" | RAN5#87-e | +| 6.5B.2.2.1 Spectrum emissions mask for intra-band non-contiguous EN-DC | 228 | "38.521-3_TPanalysis_6.2B.2.2_MPR_6.5B.2.2.1_SEM_6.5B.2.2.3_ACLR_v1.zip" | RAN5#93-e | +| 6.5B.2.2.3 Adjacent channel leakage ratio for intra-band non-contiguous EN-DC | 1140 | "38.521-3_TPanalysis_6.2B.2.2_MPR_6.5B.2.2.1_SEM_6.5B.2.2.3_ACLR_v1.zip" | RAN5#93-e | +| 6.5B.3.1.2 Spurious emission band UE co-existence for intra-band contiguous EN-DC | 8 | "38.521-3_TP analysis_6.5B.3_TX_SpurEmission_Intra_B_EN-DC" | RAN5#91-e | +| 6.5B.3.2.2 Spurious emission band UE co-existence for intra-band non-contiguous EN-DC | 8 | "38.521-3_TP analysis_6.5B.3_TX_SpurEmission_Intra_B_EN-DC" | RAN5#91-e | +| 6.5B.3.3.1 General spurious emissions for Inter-band EN-DC within FR1 | 12 | "38.521-3_TP analysis_6.5B.3.3.1_TX_SpurEmission_Inter_B_EN-DC.zip" | RAN5#91-e | +| 6.5B.3.3.2 Spurious Emissions band UE co-existence for Inter-band within FR1 | Note 1 | "38.521-3_TP analysis_6.5B.3.3.2_TX_SpurEmission_Inter_B_EN-DC" | RAN5#91-e | +| Note 1: The maximum number of test point is 2 if only default points are applied. | | | | + +Table 4.3.1.1-2: NR UE receiver test point selection for EN-DC + +| Subclause | Number of test points | Justification in attachment | Comments | +|----------------------------------------------------------------------------------|------------------------------------------|-------------------------------------------------------------|-----------| +| 7.3B Reference sensitivity for EN-DC | | "38.521-3_TPanalysis_7.3B_RxSense_EN-DC with FR1_v2.zip" | RAN5#89-e | +| 7.4B.1 Maximum Input Level for Intra-Band Contiguous EN-DC | 6 | "38.521-3_TP analysis_7.4B.1.1_MaxIL_Intra_B_contig.zip" | RAN5#82 | +| 7.4B.2 Maximum Input Level for Intra-Band Non-Contiguous EN-DC | 6 | "38.521-3_TP analysis_7.4B.2_MaxIL_Intra_B_noncontig.zip" | RAN5#82 | +| 7.5B.1 Adjacent Channel Selectivity for intra-band contiguous EN-DC (2 CCs) | 2 | "38.521-3_TP analysis_7.5B.1_ACS_Intra_B_contig.zip" | RAN5#94-e | +| 7.5B.2 Adjacent Channel Selectivity for intra-band non-contiguous EN-DC (2 CCs) | 2 | Same as Table 4.1.1-1, test case 7.5 | RAN5#94-e | +| 7.5B.3 Adjacent Channel Selectivity for inter-band EN-DC (1 NR CC) | 3 | Same as Table 4.1.1-1, test case 7.5 | RAN5#94-e | +| 7.6B.2.1 Inband blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | 2 | "38.521-3_TP analysis_7.6B.2.1_IBB_Intra_B_contig.zip" | RAN5#87-e | +| 7.6B.2.2 Inband blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | 1 | "38.521-3_TPanalysis_7.6B.2.2_IBB_Intra_B_non-contig.zip" | RAN5#87-e | +| 7.6B.2.3 Inband blocking for inter-band EN-DC within FR1 (2 CCs) | Same as Table 4.1-2, test case 7.6.2. | Same as Table 4.1-2, test case 7.6.2. | RAN5#87-e | +| 7.6B.3.1 Out-of-band blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | 1 | "38.521-3_TP analysis_7.6B.3.1_OOBB_Intra_B_contig.zip" | RAN5#87-e | +| 7.6B.3.2 Out-of-band blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | 1 | "38.521-3_TPanalysis_7.6B.3.2_OOBB_Intra_B_non-contig.zip" | RAN5#87-e | +| 7.6B.3.3 Out-of-band blocking for inter-band EN-DC within FR1 (2 CCs) | 1 | "38.521-3_TP analysis_7.6B.3.3_OOBB_Inter_B_within FR1.zip" | RAN5#87-e | +| 7.6B.4.1 Narrow band blocking for intra-band contiguous EN-DC in FR1 (2 CCs) | 2 | "38.521-3_TP analysis_7.6B.4.1_NBB_Intra_B_contig.zip" | RAN5#87-e | +| 7.6B.4.2 Narrow band blocking for intra-band non-contiguous EN-DC in FR1 (2 CCs) | 1 | "38.521-3_TPanalysis_7.6B.4.2_NBB_Intra_B_non-contig.zip" | RAN5#87-e | +| 7.6B.4.3 Narrow band blocking for inter-band EN-DC within FR1 (2 CCs) | Same as Table 4.1-2, test case 7.6.4. | Same as Table 4.1-2, test case 7.6.4. | RAN5#87-e | +| 7.7B.1 Spurious Response for intra-band contiguous EN-DC in FR1 (2 CCs) | Same as Table 4.3-2, test case 7.6B.3.1. | Same as Table 4.3-2, test case 7.6B.3.1. | RAN5#87-e | +| 7.7B.2 Spurious Response for intra-band non-contiguous EN-DC | Same as Table 4.3-2, test case 7.6B.3.2. | Same as Table 4.3-2, test case 7.6B.3.2. | RAN5#87-e | + +| | | | | +|-------------------------------------------------------------------|------------------------------------------|--------------------------------------------------------|-----------| +| in FR1 (2 CCs) | | | | +| 7.7B.3 Spurious Response for inter-band EN-DC within FR1 (2 CCs) | Same as Table 4.3-2, test case 7.6B.3.3. | Same as Table 4.3-2, test case 7.6B.3.3. | RAN5#87-e | +| 7.8B.2.3 Wideband Intermodulation for inter-band EN-DC within FR1 | Same as Table 4.1-2, test case 7.8.2. | Same as Table 4.1-2, test case 7.8.2. | RAN5#81 | +| 7.9A.1 Spurious emission for 2DL CA | 3 | "38.521-1_TPanalysis_7.9A_Spurious Emission_DL CA.zip" | RAN5#82 | +| 7.9B.3 Spurious Emissions for inter-band EN-DC within FR1 | Same as Table 4.1-2, test case 7.9. | Same as Table 4.1-2, test case 7.9. | RAN5#81 | + +#### 4.3.1.2 V2X test cases + +**Table 4.3.1.2-1: UE transmitter test point selection for E-UTRA-NR V2X** + +| Subclause | Number of test points | Justification in attachment | Comments | +|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-----------| +| 6.2E.1 UE Maximum Output Power for V2X | Intra-band contiguous V2X: N/A
Intra-band non-contiguous V2X: N/A
Inter-band con-current V2X: 20 | "38.521-3_TPanalysis_V2X_6.2E.1_MOP.zip" | RAN5#93-e | +| 6.2E.2 UE maximum output power reduction for V2X | Intra-band contiguous V2X: N/A
Intra-band non-contiguous V2X: N/A
Inter-band con-current V2X:
- 80 for E-UTRA Uu + NR SL
- 220 for NR Uu + E-UTRA SL | "38.521-3_TPanalysis_V2X_6.2E.2_MPR_6.5E.2.1_SEM_6.5E.2.3_ACLR.zip" | RAN5#93-e | +| 6.5E.2.1 Spectrum emission mask for V2X | Intra-band contiguous V2X: N/A
Intra-band non-contiguous V2X: N/A
Inter-band con-current V2X:
- 8 for E-UTRA Uu + NR SL
- 28 for NR Uu + E-UTRA SL | "38.521-3_TPanalysis_V2X_6.2E.2_MPR_6.5E.2.1_SEM_6.5E.2.3_ACLR.zip" | RAN5#93-e | +| 6.5E.2.3 Adjacent channel leakage ratio for V2X | Intra-band contiguous V2X: N/A
Intra-band non-contiguous V2X: N/A
Inter-band con-current V2X:
- 80 for E-UTRA Uu + NR SL
- 220 for NR Uu + E-UTRA SL | "38.521-3_TPanalysis_V2X_6.2E.2_MPR_6.5E.2.1_SEM_6.5E.2.3_ACLR.zip" | RAN5#93-e | + +### 4.3.2 Test point analysis per NS value + +#### 4.3.2.1 A-MPR and A-SE test cases for EN-DC + +FFS + +### 4.3.3 Test point analysis per EN-DC configuration + +#### 4.3.3.1 Reference sensitivity test cases for EN-DC + +This clause contains information on test point analysis and status for FR1 EN-DC test cases in TS 38.521-3 [4] clause 7. The analyses are performed per EN-DC configuration in Table 4.3.3.1-1, Table 4.3.3.1-2 and Table 4.3.3.1-3. + +Table 4.3.3.1-1: Reference Sensitivity test cases per EN-DC configuration (2CC) + +| Band or band configuration | Single UL | Refsens exception, victim band (NOTE 2) | Requirement coverage (NOTE 2) | Comments | +|----------------------------|-------------------------------------|--------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------| +| DC (n)XAA | | | | | +| 5 | Only single UL requirements defined | 5 | Exception | RAN5#92-e | +| 12 | Only single UL requirements defined | 12 | Exception | RAN5#92-e | +| 38 | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| 41 | Yes | N/A | NE | RAN5#88-e | +| 48 | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| 71 | Yes | 71 | Exception | RAN5#88-e | +| DC_XA_nXA | | | | | +| DC_2A_n2A | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| DC_3A_n3A | Yes | 3 | Exception | RAN5#88-e | +| DC_5A_n5A | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| DC_7A_n7A | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| DC_41A_n41A | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| DC_48A_n48A | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| DC_66A_n66A | Only single UL requirements defined | N/A | NE | RAN5#88-e | +| DC_71A_n71A | Only single UL requirements defined | N/A | NE | RAN5#92-e | +| DC_XA_nYA (NOTE 1) | | | | | +| DC_1A_n3A | Yes | 1 (IMD3)
CBI | NE
IMD3
CBI, CBI avoid | RAN5#89-e | +| DC_1A_n7A | No | N/A | NE | RAN5#94-e | +| DC_1A_n8A | No | 1 (IMD4) | NE
IMD4 | RAN5#95-e | +| DC_1A_n28A | No | 1 (HD3) | NE
HD, HD avoid | RAN5#98 | +| DC_1A_n41A | No | 1 (CBI)
n41 (CBI) | NE
CBI | RAN5#98 | +| DC_1A_n77A | No | n77 (HD2)
B1 (IMD2)
B1 (IMD4) | NE
HD
IMD2
IMD4 | Added at RAN5#96-e | +| DC_1A_n78A | No | 1 (IMD4) | NE
IMD4 | RAN5#88-e | +| DC_2A_n41A | No | 2 (CBI) | NE
CBI | Added at RAN5#96-e | +| DC_2A_n66A | No | 3 (IMD3)
n66 (IMD5) | NE
IMD3
IMD5 | RAN5#94-e | +| DC_2A_n71A | No | 2 (HD3)
n71 (HM) | NE
HD
HM | RAN5#93-e | +| DC_2A_n77A | No | n77 (HD)
2 (HM)
2 (IMD2)
2 (IMD4)
2 (IMD5) | NE
HD, HD avoid
HM, HM avoid
IMD2
PC2&PC3
IMD4
PC2&PC3
IMD5 PC3 | RAN5#94-e | +| DC_2A_n78A | No | n78 (HD2)
2 (IMD2)
2 (IMD4) | NE
HD
IMD2
IMD4 | RAN5#94-e | +| DC_3A_n1A | Yes | 1 (IMD3)
CBI | NE
IMD3
CBI, CBI avoid | RAN5#89-e | +| DC_3A_n5A | Yes | 3 (IMD4)
n5 (IMD2) | NE
IMD2
IMD4 | RAN5#94-e | +| DC_3A_n8A | No | 3 (IMD5)
n8 (IMD4) | NE
IMD4 | RAN5#96-e | + +| | | | | | +|-------------|-----------------|----------------------------------------------------------|----------------------------------------------------------------|--------------------| +| | | | IMD5 | | +| DC_3A_n28A | No | N/A | NE | RAN5#95-e | +| DC_3A_n77A | No | n77 (HD2)
B3 (HM)
B3 (IMD2)
B3 (IMD4) | NE
HD
HM
IMD2
IMD4 | Added at RAN5#96-e | +| DC_3A_n78A | Yes | 3 (IMD2)
3 (IMD4)
3 (HD)
n78 (HM) | NE
IMD2
PC2&PC3
IMD4
PC2&PC3
HD
HM, HM avoid | RAN5#89-e | +| DC_5A_n66A | Yes | 5 (IMD2) | NE (anchor agnostic)
IMD2 | RAN5#93-e | +| DC_5A_n77A | No | n77 (HD)
5 (IMD4)
5 (IMD5) | NE
HD, HD avoid
IMD4
PC2&PC3
IMD5 PC3 | RAN5#94-e | +| DC_5A_n78A | No | n78 (HD4)
B5 (IMD4) | NE
HD, HD avoid
IMD4 | Added at RAN5#96-e | +| DC_7A_n1A | No | N/A | NE | RAN5#90-e | +| DC_7A_n3A | No | 7 (IMD4 3*fB3-1*fB7 ) | NE, IMD4 | RAN5#90-e | +| DC_7A_n5A | Yes | n5 (IMD3) | NE, IMD3 | RAN5#94-e | +| DC_7A_n8A | No | N/A | NE | RAN5#95-e | +| DC_7A_n28A | No | N/A | NE | RAN5#94-e | +| DC_7A_n66A | No | B7 (IMD4) | NE
IMD4 | RAN5#99 | +| DC_7A_n71A | No | B7 (HD) | NE
HD, HD avoid | RAN5#99 | +| DC_7A_n77A | No | B7 (IMD4) | NE
IMD4 | RAN5#99 | +| DC_7A_n78A | No | CBI | NE, CBI | RAN5#94-e | +| DC_8A_n1A | No | n1 (IMD4
2*fB1-2*fB8 ) | NE, IMD4 | RAN5#90-e | +| DC_8A_n3A | No | 8 (IMD4
3*fB8-1*fB3 ),
n3 (IMD5
4*fB8-1*fB3 ) | NE, IMD4,
IMD5 | RAN5#90-e | +| DC_8A_n20A | Yes | 8 (IMD3)
n20 (IMD3) | NE
IMD3 | RAN5#94-e | +| DC_8A_n28A | No | N/A | NE | RAN5#95-e | +| DC_8A_n41A | No | n41 (HD3),
8 (IMD3) | NE
HD, HD avoid
IMD3 | RAN5#98 | +| DC_8A_n77A | No | 8 (HD4),
8 (IMD4) | NE
HD, HD avoid
IMD4 | RAN5#92-e | +| DC_8A_n78A | No | N78 (HD4),
8 (IMD4) | NE
HD, HD avoid
IMD4 | Added at RAN5#96-e | +| DC_8A_n79A | No | n79 (HD5),
8 (IMD5) | NE
HD, HD avoid
IMD5 | Added at RAN5#96-e | +| DC_11A_n77A | No | N/A | NE | RAN5#91-e | +| DC_11A_n78A | No | N/A | NE | RAN5#91-e | +| DC_11A_n79A | No | 11 (HM) | NE
HM, HM avoid | RAN5#92-e | +| DC_12A_n2A | No | N/A | NE | RAN5#98 | +| DC_12A_n66A | No | N66 (HD3) | NE
HD, HD avoid | RAN5#97 | +| DC_12A_n78A | Yes (DC_12_n78) | n78 (HD5) | NE | RAN5#98 | + +| | | | | | +|-------------------------|----------|-------------------------------------|-------------------------------------------------------|-------------------| +| | | 12 (IMD5) | HD, HD avoid IMD5 | | +| DC_13A_n77A | No | n77 (HD)
13 (HM)
13 (IMD5) | NE
HD, HD avoid
HM, HM avoid
IMD5
PC2&PC3 | RAN5#94-e | +| DC_14A_n2A | No | N/A | NE | RAN5#98 | +| DC_18A_n77A | No | n77 (HD5) | NE
HD | RAN5#97 | +| DC_18A_n78A | No | N/A | NE | RAN5#97 | +| DC_19A_n77A | No | n77 (HD5) | NE
HD | RAN5#99 | +| DC_19A_n79A | No | 19 (HM
5*fB19DL-
1*fB79 ), | NE,
HM
PC2&PC3, HM
avoid | Added at RAN5#101 | +| DC_20A_n1A | No | N/A | NE | RAN5#90-e | +| DC_20A_n3A | No | n3 (IMD4),
20 (IMD4) | NE
IMD4 | RAN5#89-e | +| DC_20A_n7A | DC_20_n7 | 20 (IMD3) | NE
IMD3 | RAN5#94-e | +| DC_20A_n8A | DC_20_n8 | 20 (IMD3)
n8 (IMD3) | NE
IMD3 | RAN5#95-e | +| DC_20A_n78A | No | 20 (IMD4),
n78 (HD) | NE
IMD4,
HD, HD avoid | RAN5#88-e | +| DC_21A_n28A | Yes | 21 (IMD5) | NE, IMD5 | RAN5#99 | +| DC_21A_n79A | No | B21 HM
B21 IMD3 | NE
HM
PC2&PC3, HM
avoid
IMD3
PC2&PC3 | Added at RAN5#101 | +| DC_25A_n41A | No | B25 | CBI | RAN5#98 | +| DC_26A_n41A | No | n41 (HD3),
26 (IMD3) | NE
HD, HD avoid
IMD | RAN5#92-e | +| DC_26A_n77A | No | n77 (HD4),
26 (IMD4) | NE
HD, HD avoid
IMD | RAN5#92-e | +| DC_26A_n78A | No | n78 (HD4),
26 (IMD4) | NE
HD, HD avoid
IMD | RAN5#92-e | +| DC_26A_n79A | No | 26 (HM
4*fB26DL-
1*fB79 ) | NE
HM, HM avoid | RAN5#92-e | +| DC_28A_n5A | No | CBI | NE
CBI, CBI avoid | RAN5#94-e | +| DC_28A_n7A | No | N/A | NE | RAN5#94-e | +| DC_28A_n77A | No | n77 (HD),
n77 (HM),
28 (IMD5) | NE (HD avoid),
HD, HM, IMD5 | RAN5#92-e | +| DC_28A_n78A | No | n78 (HD),
28 (IMD5) | NE (HD avoid),
HD, IMD5 | RAN5#92-e | +| DC_30A_n66A | No | n66 (CBI) | NE
CBI | RAN5#97 | +| DC_38A_n78A | No | B38 (CBI) | NE
CBI | RAN5#99 | +| DC_40A_n1A | No | N/A | NE | RAN5#89-e | +| DC_40A_n78A | No | 40 (HM) | NE
HM, HM avoid | RAN5#89-e | +| DC_40A_n79A | No | N/A | NE | RAN5#94-e | +| DC_41A_n28A | No | N/A | NE | RAN5#98 | +| DC_41A_n77A
(NOTE 3) | No | 41 (HM
3*fB41DL-
2*fB77 ), | NE
HM
CBI | RAN5#92-e | + +| | | | | | +|----------------------|-------------------------------------|------------------------------------------------|----------------------------------------------------------|-----------| +| | | 41 (CBI), n77 (CBI) | | | +| DC_41A_n78A (NOTE 3) | No | 41 (HM 3*fB41DL-2*fB77 ), 41 (CBI), n78 (CBI) | NE
HM
CBI | RAN5#92-e | +| DC_42A_n77A | Only single UL requirements defined | N/A | NE | RAN5#91-e | +| DC_48A_n66A | No | 48 (HD2)
66 (IMD5) | NE (anchor agnostic)
HD2
IMD5 | RAN5#92-e | +| DC_66A_n2A | DC_66_n2 | n2 (IMD3)
66 (IMD5) | NE (anchor agnostic)
IMD3
IMD5 | RAN5#93-e | +| DC_66A_n5A | No | n5 (IMD2) | NE
IMD2 | RAN5#97 | +| DC_66A_n25A | No | B66, n25 (IMD3)
B66 (IMD5) | NE
IMD3
IMD5 | RAN5#99 | +| DC_66A_n41A | No | 66 (CBI) | NE
CBI | RAN5#98 | +| DC_66A_n71A | No | 66 (IMD4) | NE (anchor agnostic)
IMD4 | RAN5#93-e | +| DC_66A_n77A | No | n77 (HD)
66 (IMD2)
66 (IMD5) | NE
HD, HD avoid
IMD2
PC2&PC3
IMD5
PC2&PC3 | RAN5#94-e | +| DC_66A_n78A | No | n78 (HD2)
66 (IMD5) | NE (anchor agnostic)
HD2
IMD5 | RAN5#93-e | +| DC_71A_n2A | No | n78 (HD2)
66 (IMD5) | NE (anchor agnostic)
HD
HM HM avoid | RAN5#98 | +| DC_71A_n66A | No | n66 (IMD4) | NE (anchor agnostic)
IMD4 | RAN5#98 | + +NOTE 1: If single UL is allowed in a DC\_XA\_nYA configuration the IMD requirements does not apply for UEs supporting UE capability *singleUL-Transmission*. + +NOTE 2: Notations used + +NE: Non-exception as defined in TS 38.101-3 [7], meaning standalone LTE in TS 36.101 [8] and NR in 38.101-1 [5] requirements apply. + +HD: UL Harmonic Distortion, as defined in TS 38.101-3 [7], 7.3B.2.3.1 + +HM: RX Harmonic Mixing, as defined in TS 38.101-3 [7], 7.3B.2.3.2 + +IMD: Intermodulation Distortion, as defined in TS 38.101-3 [7], 7.3B.2.3.5 + +CBI: Cross Band Isolation, as defined in TS 38.101-3 [7], 7.3B.2.3.4 + +HD avoid: single carrier requirements apply with aggressor of UL Harmonic Distortion active. + +HM avoid: single carrier requirements apply with aggressor of RX Harmonic Mixing active. + +CBI avoid: single carrier requirements apply with aggressor of Cross Band Isolation active. + +NOTE 3: HM cannot be avoided with aggressor still active since CBI exception always exists. Therefore, no HM avoid test point is added. + +Table 4.3.3.1-2: Reference Sensitivity test cases per EN-DC configuration (3CC) + +| Band or band configuration | Single UL | UL config | Refsens exception, victim band | Requirement coverage (NOTE 2) | Fallback DC configurations | Comments | +|----------------------------|-------------------------------------|-------------|------------------------------------|-------------------------------|----------------------------|-----------| +| DC_(n)XCA | | | | | | | +| 41 | Yes | DC_(n)41AA | N/A | NE | DC_(n)41AA
DC_41A_n41A | RAN5#89-e | +| 41 | Yes | DC_41A_n41A | N/A | NE | DC_(n)41AA
DC_41A_n41A | RAN5#89-e | +| 48 | Only single UL requirements defined | DC_(n)48AA | N/A | NE | DC_(n)48AA
DC_48A_n48A | RAN5#89-e | +| 48 | Only single UL requirements defined | DC_48A_n48A | N/A | NE | DC_(n)48AA
DC_48A_n48A | RAN5#89-e | +| DC_XA_nYC | | | | | | | +| DC_3A_n78C | Yes | DC_3A_n78A | N/A | NE | | RAN5#93-e | +| DC_XA_nY(2A) | | | | | | | +| FFS | | | | | | | +| DC_XA_nYA-nZA | | | | | | | +| DC_1A_n28A-n78A | No | DC_1A_n28A | n78 (3 band IMD3) | NE, IMD3 | | RAN5#92-e | +| | No | DC_1A_n78A | n28 (3 band IMD5) | NE, IMD5 | | RAN5#92-e | +| DC_3A_n28A-n78A | No | DC_3A_n28A | n78 (3 band IMD5) | NE, IMD5 | | RAN5#92-e | +| | Yes | DC_3A_n78A | No 3CC exception | No test required | | | +| DC_7A_n5A-n78A | Yes | DC_7A_n5A | No 3CC exception | No test required | | RAN5#94-e | +| | No | DC_7A_n78A | No 3CC exception | No test required | | RAN5#94-e | +| DC_7A_n28A-n78A | No | DC_7A_n28A | n78 (3 band IMD2) | NE, IMD2 | | RAN5#92-e | +| | No | DC_7A_n78A | n28 (3 band IMD2) | NE, IMD2 | | | +| DC_20A_n28A-n78A | No | DC_20A_n28A | n78 (3 band IMD4) | NE, IMD4 | | RAN5#93-e | +| | No | DC_20A_n78A | n28 (3 band IMD4) | NE, IMD4 | | RAN5#93-e | +| DC_28A_n7A-n78A | No | DC_28A_n7A | n78 (3 band IMD2) | NE, IMD2 | | RAN5#94-e | +| | No | DC_28A_n78A | n7 (3 band IMD2) | NE, IMD2 | | RAN5#94-e | +| DC_XA-YA_nZA | | | | | | | +| DC_1A-3A_n28A | No | DC_1A_n28A | 3 (3 band IMD5) | IMD5 | | RAN5#92-e | +| | No | DC_3A_n28A | 1 (3 band IMD4) | IMD4 | | RAN5#92-e | +| DC_1A-3A_n41A | No | DC_1A_n41A | No 3CC exception | No test required | | RAN5#98 | +| | No | DC_3A_n41A | No 3CC exception | No test required | | RAN5#98 | +| DC_1A-3A_n77A | Yes | DC_1A_n77A | 3 (3 band IMD2)
3 (3 band IMD4) | IMD2, IMD4 | | RAN5#98 | +| | Yes | DC_3A_n77A | 1 (3 band IMD2) | IMD2 | | RAN5#98 | +| DC_1A-3A_n79A | No | DC_1A_n79A | No 3CC exception | No test required | | RAN5#101 | +| | No | DC_3A_n79A | 1 (3 band IMD5) | IMD5 | | RAN5#101 | +| DC_1A-7A_n3A | Yes | DC_1A_n3A | No 3CC exception | No test required | | | +| | No | DC_7A_n3A | | | | | +| DC_1A-7A_n28A | No | DC_1A_n28A | 7 (3 band IMD2) | IMD2 | | RAN5#92-e | +| | No | DC_7A_n28A | No 3 band exception | No test required | | RAN5#92-e | +| DC_1A-7A_n78A | No | DC_1A_n78A | 7 (IMD4 3*fB1-1*fB78 ) | IMD4 | | | +| | No | DC_7A_n78A | 1 (IMD4 2*fB7-2*fB78 ) | IMD4 | | | +| DC_1A-8A_n3A | Yes | DC_1A_n3A | No 3CC exception | No test required | | | +| | No | DC_8A_n3A | | | | | +| DC_1A-18A_n77A | No | DC_1A_n77A | 18 (3 band IMD5) | IMD5 | | RAN5#98 | +| | No | DC_18A_n77A | 1 (3 band IMD3) | IMD3 | | RAN5#98 | +| DC_1A-19A_n79A | No | DC_1A_n79A | 19 (3 band IMD3) | IMD3 | | RAN5#101 | +| | No | DC_19A_n79A | 1 (3 band IMD4) | IMD4 | | RAN5#101 | + +| | | | | | | | +|----------------|----------------|-------------|--------------------------------------------------------------|-------------------------|-------------|-----------| +| DC_1A-20A_n3A | Yes | DC_1A_n3A | No 3CC exception | No test required | | | +| | No | DC_20A_n3A | | | | | +| DC_1A-20A_n8A | No | DC_1A_n8A | 20 (3 band IMD4) | IMD4 | | RAN5#95-e | +| | Yes | DC_20A_n8A | No 3CC exception | - | | RAN5#95-e | +| DC_1A-20A_n28A | No | DC_1A_n28A | No 3CC exception | No test required | | RAN5#93-e | +| | No | DC_20A_n28A | No 3CC exception | No test required | | RAN5#93-e | +| DC_1A-20A_n78A | No | DC_1A_n78A | 20 (IMD5 | IMD5 | | | +| | No | DC_20A_n78A | 1 (IMD3 | IMD3 | | | +| DC_1A-21A_n78A | No | DC_1A_n78A | 21 (3 band IMD2) | IMD2, IMD5 | | RAN5#101 | +| | No | DC_21A_n78A | 1 (3 band IMD2) | IMD2, IMD5 | | RAN5#101 | +| DC_1A-21A_n79A | No | DC_1A_n79A | No 3CC exception | No test required | | RAN5#101 | +| | No | DC_21A_n79A | No 3CC exception | No test required | | RAN5#101 | +| DC_1A-28A_n3A | Yes | DC_1A_n3A | 1 (3 band IMD4) | IMD4 | Yes | RAN5#90-e | +| | No | DC_28A_n3A | No 3CC exception | - | No | | +| DC_1A-28A_n5A | No | DC_1A_n5A | No 3CC exception | No test required | | RAN5#95-e | +| | No | DC_28A_n5A | | | | | +| DC_1A-28A_n78A | No | DC_1A_n78A | 28 (3 band IMD3) | IMD3 | | RAN5#92-e | +| | No | DC_28A_n78A | 1 (3 band IMD5) | IMD5 | DC_28A_n78A | | +| DC_1A-41A_n28A | No | DC_1A_n28A | 41 (IMD2
1*fB1+1*fn28 ) | IMD2 | | RAN5#98 | +| | No | DC_41A_n28A | No 3CC exception | No test required | | RAN5#98 | +| DC_1A-41A_n41A | No | DC_1A_n41A | No 3CC exception | No test required | | RAN5#98 | +| DC_1A-41A_n77A | No | DC_1A_n77A | 41 (IMD4 1*fn77-
3*fB1 )
41 (IMD5 3*fB1-
2*fn77 ) | IMD4, IMD5 | | RAN5#98 | +| | No | DC_41A_n77A | No 3CC exception | No test required | | RAN5#98 | +| DC_1A-42A_n79A | No | DC_1A_n79A | 42 (3 band IMD5) | IMD5 | | RAN5#101 | +| | No | DC_42A_n79A | | | | RAN5#101 | +| DC_2A-66A_n5A | No | DC_2A_n5A | 66 (3 band IMD4) | IMD4 | | RAN5#98 | +| | Yes (DC_66_n5) | DC_66A_n5A | No 3CC exception | No test required | | | +| DC_2A_n5A-n77A | No | DC_2A_n5A | n77 (3 band
IMD3) | NE, IMD3 | | RAN5#101 | +| | No | DC_2A_n77A | No 3CC exception | NE | | | +| DC_2A-13A_n77A | No | DC_2A_n77A | No 3CC exception | NE | | RAN5#101 | +| | No | DC_13A_n77A | 2 (3 band IMD3) | NE, IMD3 | | | +| DC_2A-66A_n41A | No | DC_2A_n41A | 2 (3 band IMD4) | IMD4 | | RAN5#96-e | +| | No | DC_66A_n41A | No 3CC exception | | | | +| DC_2A-66A_n77A | No | DC_2A_n77A | 66 (3 band IMD2,
IMD4, IMD5) | NE, IMD2, IMD4,
IMD5 | | RAN5#101 | +| | No | DC_66A_n77A | 2(3 band IMD2) | NE, IMD2 | | | +| DC_3A-7A_n1A | Yes | DC_3A_n1A | No 3CC exception | No test required | | RAN5#90-e | +| | No | DC_7A_n1A | No 3CC exception | | | | +| DC_3A-7A_n5A | Yes | DC_3A_n5A | 7 (3 band IMD2) | IMD2 | | RAN5#95-e | +| | Yes | DC_7A_n5A | No 3CC exception | - | | RAN5#95-e | +| DC_3A-7A_n8A | No | DC_3A_n8A | 7 (3 band IMD2,
IMD3) | IMD2, IMD3 | | RAN5#96-e | +| | No | DC_7A_n8A | No 3CC exception | No test required | | RAN5#96-e | +| DC_3A-7A_n28A | No | DC_3A_n28A | 7 (3 band IMD3) | IMD3 | | RAN5#92-e | +| | No | DC_7A_n28A | 3 (3 band IMD2) | IMD2 | | RAN5#92-e | +| DC_3A-8A_n28A | No | DC_3A_n28A | No 3CC exception | No test required | | RAN5#95-e | +| | No | DC_8A_n28A | | | | | +| DC_3A-18A_n77A | Yes | DC_3A_n77A | No 3CC exception | No test required | | RAN5#98 | +| | No | DC_18A_n77A | No 3CC exception | No test required | | RAN5#98 | +| DC_3A-19A_n79A | No | DC_3A_n79A | 19 (3 band IMD3) | IMD3 | | RAN5#101 | +| | No | DC_19A_n79A | 3 (3 band IMD4) | IMD4 | | RAN5#101 | +| DC_3A-20A_n1 | Yes | DC_3A_n1A | No 3CC exception | No test required | | | +| | No | DC_20A_n1A | | | | | +| DC_3A-20A_n8A | No | DC_3A_n8A | No 3CC exception | No test required | | RAN5#96-e | +| | Yes (DC_20_n8) | DC_20A_n8A | 3 (3 band IMD4) | IMD4 | | RAN5#96-e | +| DC_3A-20A_n28A | No | DC_3A_n28A | No 3CC exception | No test required | | RAN5#92-e | +| | No | DC_20A_n28A | 3 (3 band IMD4) | IMD4 | | RAN5#92-e | +| DC_3A-20A_n78 | Yes | DC_3A_n78A | No 3CC exception | | | | +| | No | DC_20A_n78A | 3 (3 band IMD3) | IMD3 | | | +| DC_3A-21A_n78 | Yes | DC_3A_n78A | 21 (3 band IMD4) | IMD4 | | RAN5#101 | +| | No | DC_21A_n78A | 3 (3 band IMD2) | IMD2 | | RAN5#101 | + +| | | | | | | | +|-----------------|-----|--------------|----------------------------------------------------|-------------------------------|-------------|--------------------| +| DC_3A-21A_n79 | No | DC_3A_n79A | No 3CC exception | No test required | | RAN5#101 | +| | No | DC_21A_n79A | 3 (3 band IMD3) | IMD3 | | RAN5#101 | +| DC_3A-28A_n78A | Yes | DC_3A_n78A | No 3CC exception | | DC_3A_n78A | RAN5#92-e | +| | No | DC_28A_n78A | 3 (3 band IMD3) | IMD3 | DC_28A_n78A | | +| DC_3A-40A_n1A | Yes | DC_3A_n1A | 40 (3 band IMD5) | IMD5 if UE supporting dual UL | | | +| | No | DC_40A_n1A | No 3CC exception | | | | +| DC_3A-41A_n28A | No | DC_3A_n28A | 41 (IMD2 1*fB3+1*fn28)
41 (IMD3 2*fB3-fn28) | IMD2, IMD3 | | RAN5#98 | +| | No | DC_41A_n28A | 3 (IMD2 1*fB41-1*fn28) | IMD2 | | RAN5#98 | +| DC_3A-41A_n41A | No | DC_3A_n41A | No 3CC exception | No test required | | RAN5#98 | +| DC_3A-41A_n77A | Yes | DC_3A_n77A | 41 (IMD5 3*fB3-2*fB77) | IMD5 | | RAN5#97 | +| | No | DC_41A_n77A | 3 (IMD3 2*fB41-1*fB77) | IMD3 | | RAN5#97 | +| DC_7A-8A_n3A | No | DC_7A_n3A | 8 (3 band IMD3) | IMD3 | | RAN5#95-e | +| | No | DC_8A_n3A | 7 (3 band IMD2)
7 (3 band IMD3) | IMD2, IMD3 | | RAN5#95-e | +| DC_7A-20A_n1A | No | DC_20A_n1A | 20 (3 band IMD5) | IMD5 | | RAN5#90-e | +| | No | DC_7A_n1A | No 3CC exception | | | | +| DC_7A-20A_n3A | No | DC_7A_n3A | 20 (IMD2 1*fB7-1*fB3) | NE, IMD2 | | | +| | No | DC_20A_n3A | 7 (IMD2 1*fB3+1*fB20) | NE, IMD2 | | | +| DC_7A-20A_n8A | No | DC_7A_n8A | 20 (3 band IMD3) | IMD3 | | RAN5#95-e | +| | Yes | DC_20A_n8A | 7 (3 band IMD3) | IMD3 | | RAN5#95-e | +| DC_7A-20A_n28A | No | DC_7A_n28A | No 3CC exception | No test required | | RAN5#92-e | +| | No | DC_20A_n28A | 7 (3 band IMD5) | IMD5 | | | +| DC_7A-20A_n78A | No | DC_7A_n78A | 20 (3 band IMD2)
20 (3 band IMD5) | IMD2, IMD5 | | | +| | No | 2 DC_0A_n78A | 7 (3 band IMD2) | IMD2 | | | +| DC_7A-28A_n3A | No | DC_7A_n3A | 28 (3 band IMD2) | IMD2 | | RAN5#90-e | +| | No | DC_28A_n3A | 7 (3 band IMD3) | IMD3 | | | +| DC_7A-28A_n5A | Yes | DC_7A_n5A | 28 (3 band IMD5) | IMD5 | | RAN5#95-e | +| | No | DC_28A_n5A | 7 (3 band IMD5) | IMD5 | | RAN5#95-e | +| DC_7A-28A_n78A | No | DC_7A_n78A | 28 (3 band IMD2)
28 (3 band IMD5) | IMD2, IMD5 | | RAN5#92-e | +| | No | DC_28A_n78A | 7 (3 band IMD2) | IMD2 | DC_28A_n78A | | +| DC_13A_n2A-n77A | No | DC_13A_n2A | n77 (3 band IMD3) | NE, IMD3 | | RAN5#101 | +| | No | DC_13A_n77A | n2 (3 band IMD3) | NE, IMD3 | | | +| DC_13A-66A_n2A | No | DC_13A_n2A | 66 (3 band IMD4) | NE, IMD4 | | RAN5#101 | +| | No | DC_66A_n2A | No 3CC exception | NE | | | +| DC_13A-66A_n77A | No | DC_13A_n5A | 66 (3 band IMD3) | NE, IMD3 | | RAN5#101 | +| | No | DC_66A_n5A | No 3CC exception | NE | | | +| DC_18A-41A_n77A | No | DC_18A_n77A | No 3CC exception | No test required | | Added at RAN5#95-e | +| | No | DC_41A_n77A | 18 (IMD5 2*fB77-3*fB41) | IMD5 | | | +| DC_18A-41A_n78A | No | DC_18A_n78A | No 3CC exception | No test required | | Added at RAN5#95-e | +| | No | DC_41A_n78A | 18 (IMD5 2*fB78-3*fB41) | IMD5 | | | +| DC_19A-21A_n79A | No | DC_19A_n79A | 21 (3 band IMD5) | IMD5 | | RAN5#101 | +| | No | DC_21A_n79A | No 3CC exception | No test required | | RAN5#101 | + +| | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-------------|-------------------|----------|--|----------| +| DC_66A_n2A-n77A | No | DC_66A_n2A | No 3CC exception | NE | | RAN5#101 | +| | No | DC_66A_n77A | n2 (3 band IMD2) | NE, IMD2 | | | +| DC_66A_n5A-n77A | No | DC_66A_n5A | n77 (3 band IMD3) | NE, IMD3 | | RAN5#101 | +| | No | DC_66A_n77A | No 3CC exception | NE | | | +| DC_(n)XAA-nYA | | | | | | | +| FFS | | | | | | | +| DC_XA_nXA_nYA | | | | | | | +| FFS | | | | | | | +| NOTE 1: If single UL is allowed in a DC_XA_nYA configuration the IMD requirements does not apply for UEs supporting UE capability singleUL-Transmission . | | | | | | | +| NOTE 2: Notations used
NE: Non-exception as defined in TS 38.101-3 [7], meaning standalone LTE in TS 36.101 [8] and NR in 38.101-1 [5] requirements apply.
HD: UL Harmonic Distortion, as defined in TS 38.101-3 [7], 7.3B.2.3.1
HM: RX Harmonic Mixing, as defined in TS 38.101-3 [7], 7.3B.2.3.2
IMD: Intermodulation Distortion, as defined in TS 38.101-3 [7], 7.3B.2.3.5
CBI: Cross Band Isolation, as defined in TS 38.101-3 [7], 7.3B.2.3.4 | | | | | | | + +Table 4.3.3.1-3: Reference Sensitivity test cases per EN-DC configuration (4CC) + +| Band or band configuration | Single UL | UL config | Refsens exception, victim band | Requirement coverage (NOTE 2) | Fallback DC configurations | Comments | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------|--------------------------------|-------------------------------|----------------------------|-----------| +| DC_(n)XDA | | | | | | | +| 41 | Yes | DC_(n)41AA | N/A | NE | DC_(n)41CA
DC_41C_n41A | RAN5#89-e | +| 41 | Yes | DC_41A_n41A | N/A | NE | N/A | RAN5#89-e | +| 48 | Only single UL requirements defined | DC_(n)48AA | N/A | NE | DC_(n)48CA
DC_48C_n48A | RAN5#89-e | +| 48 | Only single UL requirements defined | DC_48A_n48A | N/A | NE | N/A | RAN5#89-e | +| DC_XA_nY(2A)-nZA | | | | | | | +| FFS | | | | | | | +| DC_XA_nYA-nZC | | | | | | | +| FFS | | | | | | | +| NOTE 1: If single UL is allowed in a DC_XA_nYA configuration the IMD requirements does not apply for UEs supporting UE capability singleUL-Transmission . | | | | | | | +| NOTE 2: Notations used
NE: Non-exception as defined in TS 38.101-3 [7], meaning standalone LTE in TS 36.101 [8] and NR in 38.101-1 [5] requirements apply.
HD: UL Harmonic Distortion, as defined in TS 38.101-3 [7], 7.3B.2.3.1
HM: RX Harmonic Mixing, as defined in TS 38.101-3 [7], 7.3B.2.3.2
IMD: Intermodulation Distortion, as defined in TS 38.101-3 [7], 7.3B.2.3.5
CBI: Cross Band Isolation, as defined in TS 38.101-3 [7], 7.3B.2.3.4 | | | | | | | + +For EN-DC configurations affected by exceptions, the test frequency cannot be freely chosen. One test frequency per exception requirement is sufficient to test the requirement. This is indicated in Table 4.3.3.1-4 following the frequency relation formulas defined in clause D.2.3. Exceptions in TS 38.101-3 clause 7.3A.5 (2UL intermodulation) are not specified since the test frequency and channel bandwidth is already specified in TS 38.101-1. + +**Table 4.3.3.1-4: Test frequency selection per band pair for bands and test points with exceptions avoidable by test frequency setting (UL harmonics, Rx mixing, cross band isolation)** + +| Band set (Note 2) | Frequency | Channel BW [MHz] | Exception type | Comments | +|------------------------|-------------------------------|--------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------| +| 1A / n3A | Mid/Mid | Highest/Highest | - | Non-Exception. | +| | Low/High | 20 / 40 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 1A / n28A | DL 2140 / UL 713 MHz | 20/10 | UL Harmonic Interference HD3 | Exception Note 9 of TS 38.101-3 Table 7.3B.2.3.1-1 | +| | DL 2160 / UL 708 MHz | 20/10 | UL Harmonic avoiding | Exception avoiding. Not overlapping interference since $BW_{INT}=30$ MHz, $ F_{INT} = 36$ , $ F_{INT} > (30+20)/2$ | +| 1A/77A | UL 1950/ DL 3900 | 20/100 | UL Harmonic Interference | Exception Note 2 and 13 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 1950/ DL 3870 | 20/20 | UL Harmonic Interference | Exception Note 3 and 13 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 1950/UL 4090.005 | 5/5 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| | UL 1950/ UL3709.005 | 5/5 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 2A / n41A | High/Low | 20/100 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 2A/71A | DL1980 MHz/ UL665.5 MHz | 20/5 | UL Harmonic Interference | Exception Note 11 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | DL1980 MHz/ UL673 MHz | 20/10 | UL Harmonic Interference | Exception Note 12 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL1881 MHz/UL Low | 20/20 | Receiver Harmonic Mixing | Exception Note 4 in TS 38.101-3 Table 7.3B.2.3.2-1 | +| 2A/n77A | UL 1860 MHz / DL 3720 MHz | 20/100 | UL Harmonic Interference | Exception Note 2, 13 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 1860 MHz / DL 3690 MHz | 20/20 | UL Harmonic Interference | Exception Note 3 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | DL Mid (1960) / UL 3920 | 20/100 | Receiver harmonic mixing HM2 | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | UL 1860 MHz / DL 3850 MHz | 20/100 | | HD avoid | +| | DL Mid / UL Mid | 20/100 | | HM avoid | +| 2A/78A | DL 3740 MHz / UL 1870 MHz | Highest (20 MHz) / Highest (100 MHz) | UL Harmonic Interference HD2 | Exception Note 2, 13 of TS38.101-3 table 7.3B.2.3.1-1 | +| | DL 3740 MHz / UL 1885 MHz | 20 MHz) / Highest (20 MHz) | UL Harmonic Interference HD2 | Exception Note 3 of TS38.101-3 table 7.3B.2.3.1-1 | +| 3A / n1A | Mid/Mid | Highest/Highest | - | Non-Exception. | +| | High/Low | 20 / 20 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 3A / n41A | | | | CMCC CR R5-205929 | +| 3A / n77A
3A / n78A | Mid/High | Highest/Highest | - | Non-Exception. | +| | Mid/3495 | Highest/Highest | UL Harmonic Interference | Exception Note 2 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | Mid/3525 | 20/20 | UL Harmonic Interference | Exception Note 3 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | Mid /3685.005 | 20/20 | Receiver Harmonic Mixing | Receiver Harmonic Mixing Exception in TS 38.101-3 Table 7.3B.2.3.2-1 | +| | Low/High | 20/20 | | Receiver Harmonic Mixing avoided | +| | UL 1740/ UL3574.995 | 5/10 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| | UL 1765/ UL 3435 | 5/10 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 5A/n77A | UL 837.5 MHz / DL 3350.01 MHz | 10/100 | UL Harmonic Interference | Exception Note 6, 7, 17 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 829 MHz / DL | 10/100 | UL Harmonic | Exception Note 4, 5, 17 of TS | + +| | | | | | +|---------------------|----------------------------------|--------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------| +| | 4145.01 MHz | | Interference | 38.101-3 table 7.3B.2.3.1-1 | +| | UL Mid/DL Mid | 10/100 | | HD avoid | +| | UL 844 MHz/DL 3421.005 MHz | 5/10 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| | UL 826.5 MHz/DL 4177.5 MHz | 5/10 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| | | | | | +| 5A/n78A | UL 840 MHz / DL 3360 MHz | 10/100 | UL Harmonic Interference | Exception Note 6, 7, 17 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 840 MHz / DL 3560.01 MHz | 10/100 | | HD avoid | +| | UL 844 MHz/UL 3421.005 MHz | 5/10 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 7A / n66A | UL2535 MHz/ UL 1730 MHz | 10/5 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 7A / n71A | UL 668 MHz/ DL 2672 MHz | 20/5 | UL Harmonic Interference | Exception Note 6, 7, 17 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 668 MHz/ DL 2620 MHz | 20/5 | UL Harmonic avoiding | HD avoid | +| 7A / n77A | UL2540 MHz/ UL 3870 MHz | 5/10 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 7A / n78A | High/Low | 20/100 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 8A / n41A | UL 885 / DL 2655 MHz | 10/100 | UL Harmonic Interference HD3 | Exception Note 9 of TS 38.101-3 Table 7.3B.2.3.1-1 | +| | UL 885 / DL 2546 MHz | 10/100 | UL Harmonic avoiding | Exception avoiding. Not overlapping interference since $BW_{INT}=30$ MHz, $ F_{INT} = 109$ , $ F_{INT} > (30+100)/2$ | +| 8A /n77A
8A/n78A | Mid (UL 897.5 MHz) / 3590.01 | Highest (10 MHz) / Highest (100 MHz) | UL Harmonic Interference HD4 | Exception Note 7 of TS38.101-3 table 7.3B.2.3.1-1 | +| | Mid (UL 897.5 MHz) / 3520.005 | Highest (10 MHz) / Highest (100 MHz) | | Non-Exception. Not overlapping interference since $BW_{INT}=40$ MHz, $F_{INT} = (40+100)/2 = 70$ | +| | UL 897.5/ UL 3634.995 | 5/40 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 8A / n79A | UL 900/DL 4500 | 10/100 | UL Harmonic Interference | Exception Note 4 nad 5 of TS38.101-3 table 7.3B.2.3.1-1 | +| | UL 900/DL 4299.99 | 10/100 | | HD avoid | +| | UL 897.5/ UL 4532.505 | 5/40 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 11A / n79A | Mid (DL 1485.9 MHz) / 4457.7 | Highest (10 MHz) / Highest (100 MHz) | Receiver Harmonic Mixing HM3 | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | Mid (DL 1485.9 MHz) / 4512.7 MHz | Highest (10 MHz) / Highest (100 MHz) | | Non-Exception. Not overlapping interference since $BW_{INT}=100$ MHz, $F_{INT} = (100+10)/2 = 55$ | +| 12A/n66A | UL 710/DL 2130 | 10/40 | UL Harmonic Interference | Exception Note 4 nad 5 of TS38.101-3 table 7.3B.2.3.1-1 | +| | UL 710/DL 2165 | 10/40 | UL Harmonic avoid | Non-Exception. Not overlapping interference since $BW_{INT}=30$ MHz, $F_{INT} = (30+40)/2 = 35$ | +| 12A / n78A | UL 707 / DL 3535 MHz | 10/100 | UL Harmonic Interference HD5 | Exception Note 5 of TS 38.101-3 Table 7.3B.2.3.1-1 | +| | UL 707 / DL 3750 MHz | 10/100 | UL Harmonic avoiding | Exception avoiding. Not overlapping interference since $BW_{INT}=50$ MHz, $ F_{INT} = 215$ , $ F_{INT} > (50+100)/2$ | +| 13A/n77A | UL 782 MHz / DL 3910 MHz | 10/100 | UL Harmonic Interference | Exception Note 4, 5 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | DL Mid (751) / UL 3755 | 10/100 | Receiver harmonic mixing | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | UL 782 MHz /DL Mid | 10/100 | | HD avoid | + +| | | | | | +|--------------------------|-----------------------------------|--------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------| +| | DL Mid / UL 3850 | 10/100 | | HM avoid | +| 18A/ n77A | UL 820MHz/
DL 4100 MHz | 10/40 | UL Harmonic Interference | Exception Note 4, 5 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 820MHz/
DL 4000 MHz | 10/40 | UL Harmonic avoiding | HD avoid | +| 19A/ n77A | UL 835MHz/
DL 4175 MHz | 10/40 | UL Harmonic Interference | Exception Note 4, 5 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL 835MHz/
DL 4100 MHz | 10/40 | UL Harmonic avoiding | HD avoid | +| 19A / n79A | DL 884 MHz / Low (4420.02 MHz) | 10 MHz / 40 MHz | Receiver Harmonic Mixing HM3 | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | DL 884 MHz / Low (4445.02 MHz) | 10 MHz / 40 MHz | | Non-Exception. Not overlapping interference since $BW_{INT}=40$ MHz, $F_{INT} = (40+10)/2 = 25$ | +| 20A / n78A | Mid/Mid | Highest/Highest | - | Non-Exception. | +| | Mid/3388 | Highest/Highest | UL Harmonic Interference | Exception Note 7 of TS 38.101-3 table 7.3B.2.3.1-1 | +| 21A / n79A | DL 1506/UL4518 | 20/100 | Receiver Harmonic Mixing HM3 | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | DL 1506/ UL 4800 | 20/100 | | Receiver Harmonic Mixing avoid | +| | UL 1457.5/UL 4420.5 | 5/40 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 26A / n41A | High (UL 841.5 MHz) / 2524.5 MHz) | Highest (15 MHz) / 50 MHz | UL Harmonic Interference HD3 | Exception Note 9 of TS38.101-3 table 7.3B.2.3.1-1 | +| | High (UL 841.5 MHz) / 2572 MHz | Highest (15 MHz) / 50 MHz | | Non-Exception. Not overlapping interference since $BW_{INT}=45$ MHz, $F_{INT} = (45+50)/2 = 47.5$ | +| 26A / n77A
26A / n78A | High (UL 841.5 MHz) / 3366 MHz | Highest (15 MHz) / Highest (100 MHz) | UL Harmonic Interference HD4 | Exception Note 7 of TS38.101-3 table 7.3B.2.3.1-1 | +| | High (UL 841.5 MHz) / 3446 MHz | Highest (15 MHz) / Highest (100 MHz) | | Non-Exception. Not overlapping interference since $BW_{INT}=60$ MHz, $F_{INT} = (60+100)/2 = 80$ | +| 26A / n79A | High (DL 886.5 MHz) / 4432.5 MHz) | Highest (15 MHz) / 60 MHz | Receiver Harmonic Mixing HM5 | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | High (DL 886.5 MHz) / 4470.5 MHz) | Highest (15 MHz) / 60 MHz | | Non-Exception. Not overlapping interference since $BW_{INT}=60$ MHz, $F_{INT} = (60+15)/2 = 37.5$ | +| 30A/n66A | Low/High | 10/40 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 38A/n78A | DL High/UL Low | 10/20 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 40A / n78A | Low/Mid | Highest/Highest | - | Non-Exception. | +| | Mid/3525 | 20/20 | Receiver Harmonic Mixing | Receiver Harmonic Mixing Exception Note 8 in TS38.101-3 Table 7.3B.2.3.2-1 | +| 41A / n77A
41A / n78A | Low (DL 2593 MHz) / 3750 MHz) | Highest (20 MHz) / Highest (100 MHz) | Receiver Harmonic Mixing HM4 | Receiver Harmonic Mixing Exception in TS38.101-3 Table 7.3B.2.3.2-1 | +| | Mid (DL 2593 MHz) / 3974.5 MHz) | Highest (20 MHz) / Highest (100 MHz) | Cross band isolation | Not overlapping HM interference since $BW_{INT}=240$ MHz, $F_{INT} = (240+100)/2 = 170$ | +| | Mid / Mid | Highest / Highest | - | Non-Exception only possible with 1UL in band 41 | +| 48A/n66A | DL 3555 MHz/ UL 1777.5 MHz | 10/20 | UL Harmonic Interference HD2 | Exception Note 2, 13 of TS38.101-3 table 7.3B.2.3.1-1 | +| | DL 3565 MHz/ UL 1770 MHz | 10/20 | UL Harmonic Interference HD2 | Exception Note 3 of TS38.101-3 table 7.3B.2.3.1-1 | +| 66A/n25A | UL 1775 MHz / UL 1855 MHz | 5/5 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 66A/n25A | UL 1712.5 MHz / UL 1912.5 MHz | 5/5 | Dual UL intermodulation | Exception in TS 38.101-3 Table 7.3B.2.3.5.1-1 | +| 66A/n25A | UL 1750 MHz / UL | 5/5 | Dual UL | Exception in TS 38.101-3 Table | + +| | | | | | +|-------------------------------|---------------------------|--------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------| +| | 1883.3 MHz | | intermodulation | 7.3B.2.3.5.1-1 | +| 66A/n77A | UL 1720 MHz / DL 3440 MHz | 20/100 | UL Harmonic Interference | Exception Note 2, 13 of TS38.101-3 table 7.3B.2.3.1-1 | +| | UL 1720 MHz / DL 3420 MHz | 20/20 | UL Harmonic Interference | Exception Note 3 of TS38.101-3 table 7.3B.2.3.1-1 | +| | UL Mid / DL Mid | 20/100 | | HD avoid | +| 66A/n78A | DL 3510 MHz/ UL 1755 MHz | Highest (20 MHz) / Highest (100 MHz) | UL Harmonic Interference HD2 | Exception Note 2, 13 of TS38.101-3 table 7.3B.2.3.1-1 | +| | DL 3480 MHz/ UL 1755 MHz | Highest (20 MHz) / Highest (100 MHz) | UL Harmonic Interference HD2 | Exception Note 3 of TS38.101-3 table 7.3B.2.3.1-1 | +| 66A/n41A (PC2 and PC3) | High/Low | 20/100 | Cross band isolation | Exception in TS 38.101-3 table 7.3B.2.3.4-1 | +| 71A/n2A | UL665.5 MHz/ DL1987.5 MHz | 5/5 | UL Harmonic Interference | Exception Note 11 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | UL673 MHz/ DL1980 MHz | 20/10 | UL Harmonic Interference | Exception Note 12 of TS 38.101-3 table 7.3B.2.3.1-1 | +| | DL Low / UL1881 MHz | 20/20 | Receiver Harmonic Mixing | Exception Note 4 in TS 38.101-3 Table 7.3B.2.3.2-1 | +| | DL High / UL1881 MHz | 20/20 | HM avoid | Exception avoiding. Not overlapping interference since $BW_{INT}=20$ MHz, $ F_{INT} = 45$ , $ F_{INT} > (20+20)/2$ | + +NOTE 1: This selection is used in test case 7.3B.2.3 unless otherwise stated + +NOTE 2: Aggressor band in bold + +NOTE 3: Test frequencies defined in this table are required to be used in test cases 7.3B.2.3 and 7.3B.2.3\_1.1 of TS38.521-1 [2] + +#### 4.3.3.2 Spurious emissions test cases for EN-DC + +In this case, it is sufficient to verify the minimum requirements in frequency ranges affected by 2nd and 3rd order intermodulation products. The frequency ranges and UL RB allocations used in the test are calculated here. + +The analyses are performed per EN-DC configuration and are stored as zip-files as defined in annex A. + +Table 4.3.3.2-1: Frequency range analysis availability per EN-DC configuration + +| EN-DC config | Justification | Comments | +|--------------|---------------------------------------------|--------------------| +| DC 1A n3A | 38.521-3 TpAnalysisSpur(DC 1A-n3A).zip | RAN5#89-e | +| DC 1A n5A | 38.521-3 TpAnalysisSpur(DC 1A n5A).zip | RAN5#94-e | +| DC 1A n7A | 38.521-3 TpAnalysisSpur(DC 1A n7A).zip | RAN5#94-e | +| DC 1A n8A | 38.521-3 TpAnalysisSpur(DC 1A n8A).zip | RAN5#95-e | +| DC 1A n28A | 38.521-3 TpAnalysisSpur(DC 1A n28A).zip | RAN5#92-e | +| DC 1A n41A | 38.521-3 TpAnalysisSpur(DC 1A n41A).zip | RAN5#98 | +| DC 1A n77A | 38.521-3 TpAnalysisSpur(DC 1A n77A).zip | RAN5#92-e | +| DC 1A n78A | 38.521-3 TpAnalysisSpur(DC 1A n78A) v1.zip | RAN5#92-e | +| DC 1A n79A | 38.521-3 TpAnalysisSpur(DC 1A n79A).zip | RAN5#92-e | +| DC 2A n5A | 38.521-3 TpAnalysisSpur(DC 2A n5A) v1.zip | RAN5#100 | +| DC 2A n41A | 38.521-3 TpAnalysisSpur(DC 2A n41A) v2.zip | RAN5#100 | +| DC 2A n48A | 38.521-3 TpAnalysisSpur(DC 2A n48A).zip | RAN5#100 | +| DC 2A n66A | 38.521-3 TpAnalysisSpur(DC 2A n66A).zip | RAN5#88-e | +| DC 2A n71A | 38.521-3 TpAnalysisSpur(DC 2A n71A) v3.zip | RAN5#100 | +| DC 2A n77A | 38.521-3 TpAnalysisSpur(DC 2A n77A) v3.zip | RAN5#100 | +| DC 2A n78A | 38.521-3 TpAnalysisSpur(DC 2A n78A).zip | RAN5#88-e | +| DC 3A n1A | 38.521-3 TpAnalysisSpur(DC 3A n1A).zip | RAN5#88-e | +| DC 3A n5A | 38.521-3 TpAnalysisSpur(DC 3A n5A).zip | RAN5#94-e | +| DC 3A n7A | 38.521-3 TpAnalysisSpur(DC 3A n7A) v1.zip | RAN5#91-e | +| DC 3A n8A | 38.521-3 TpAnalysisSpur(DC 3A n8A).zip | Added at RAN5#96-e | +| DC 3A n28A | 38.521-3 TpAnalysisSpur(DC 3A n28A).zip | RAN5#92-e | +| DC 3A n41A | 38.521-3 TpAnalysisSpur(DC 3A n41A) v3.zip | RAN5#94-e | +| DC 3A n77A | 38.521-3 TpAnalysisSpur(DC 3A n77A).zip | RAN5#92-e | +| DC 3A n78A | 38.521-3 TpAnalysisSpur(DC 3A n78A) v1.zip | RAN5#91-e | +| DC 3A n79A | 38.521-3 TpAnalysisSpur(DC 3A-n79A) v1.zip | RAN5#83 | +| DC 5A n2A | 38.521-3 TpAnalysisSpur(DC 5A n2A) v3.zip | RAN5#100 | +| DC 5A n66A | 38.521-3 TpAnalysisSpur(DC 5A n66A) v2.zip | RAN5#92-e | +| DC 5A n77A | 38.521-3 TpAnalysisSpur(DC 5A n77A) v3.zip | RAN5#100 | +| DC 5A n78A | 38.521-3 TpAnalysisSpur(DC 5A n78A) v2.zip | RAN5#92-e | +| DC 7A n1A | 38.521-3 TpAnalysisSpur(DC 7A n1A).zip | RAN5#88-e | +| DC 7A n3A | 38.521-3 TpAnalysisSpur(DC 7A n3A) v1.zip | RAN5#96-e | +| DC 7A 5A | 38.521-3 TpAnalysisSpur(DC 7A n5A).zip | RAN5#94-e | +| DC 7A n8A | 38.521-3 TpAnalysisSpur(DC 7A n8A).zip | RAN5#95-e | +| DC 7A n28A | 38.521-3 TpAnalysisSpur(DC 7A n28A).zip | RAN5#92-e | +| DC 7A n66A | 38.521-3 TpAnalysisSpur(DC 7A n66A).zip | RAN5#88-e | +| DC 7A n78A | 38.521-3 TpAnalysisSpur(DC 7A n78A) v1.zip | RAN5#92-e | +| DC 8A n1A | 38.521-3 TpAnalysisSpur(DC 8A n1A).zip | RAN5#88-e | +| DC 8A n3A | 38.521-3 TpAnalysisSpur(DC 8A n3A) v2.zip | RAN5#96-e | +| DC 8A n20A | 38.521-3 TpAnalysisSpur(DC 8A n20A) v1.zip | RAN5#96-e | +| DC 8A n28A | 38.521-3 TpAnalysisSpur(DC 8A n28A).zip | RAN5#95-e | +| DC 8A n41A | 38.521-3 TpAnalysisSpur(DC 8A n41A) v4.zip | RAN5#100 | +| DC 8A n77A | 38.521-3 TpAnalysisSpur(DC 8A n77A) v2.zip | RAN5#100 | +| DC 8A n78A | 38.521-3 TpAnalysisSpur(DC 8A n78A) v1.zip | RAN5#93-e | +| DC 11A n77A | 38.521-3 TpAnalysisSpur(DC 11A n77A) v1.zip | RAN5#92-e | +| DC 11A n78A | 38.521-3 TpAnalysisSpur(DC 11A n78A) v1.zip | RAN5#92-e | +| DC 11A n79A | 38.521-3 TpAnalysisSpur(DC 11A n79A) v1.zip | RAN5#92-e | +| DC 12A n2A | 38.521-3 TpAnalysisSpur(DC 12A n2A) v1.zip | RAN5#100 | +| DC 12A n66A | 38.521-3 TpAnalysisSpur(DC 12A n66A) v1.zip | RAN5#91-e | +| DC 12A n77A | 38.521-3 TpAnalysisSpur(DC 12A n77A).zip | RAN5#101 | +| DC 12A n78A | 38.521-3 TpAnalysisSpur(DC 12A n78A) v1.zip | RAN5#92-e | +| DC 13A n2A | 38.521-3 TpAnalysisSpur(DC 13A n2A) v4.zip | RAN5#100 | +| DC 13A n66A | 38.521-3 TpAnalysisSpur(DC 13A n66A).zip | RAN5#89-e | +| DC 13A n77A | 38.521-3 TpAnalysisSpur(DC 13A n77A) v3.zip | RAN5#100 | +| DC 14A n2A | 38.521-3 TpAnalysisSpur(DC 14A n2A) v5.zip | RAN5#100 | +| DC 14A n66A | 38.521-3 TpAnalysisSpur(DC 14A n66A) v4.zip | RAN5#95-e | +| DC 14A n77A | 38.521-3 TpAnalysisSpur(DC 14A n77A).zip | RAN5#101 | +| DC 18A n77A | 38.521-3 TpAnalysisSpur(DC 18A n77A).zip | RAN5#97 | +| DC 18A n78A | 38.521-3 TpAnalysisSpur(DC 18A n78A).zip | RAN5#97 | +| DC 19A n1A | 38.521-3 TpAnalysisSpur(DC 19A n1A).zip | RAN5#94-e | +| DC 19A n77A | 38.521-3 TpAnalysisSpur(DC 19A n77A).zip | RAN5#92-e | +| DC 19A n78A | 38.521-3 TpAnalysisSpur(DC 19A n78A).zip | RAN5#92-e | +| DC 19A n79A | 38.521-3 TpAnalysisSpur(DC 19A n79A).zip | RAN5#92-e | + +| | | | | +|-------------|----------|---------------------------------|-----------| +| DC 20A n1A | 38.521-3 | TpAnalysisSpur(DC 20A n1A).zip | RAN5#96-e | +| DC 20A n3A | 38.521-3 | TpAnalysisSpur(DC 20A n3A).zip | RAN5#96-e | +| DC 20A n7A | 38.521-3 | TpAnalysisSpur(DC 20A n7A).zip | RAN5#94-e | +| DC 20A n8A | 38.521-3 | TpAnalysisSpur(DC 20A n8A).zip | RAN5#95-e | +| DC 20A n78A | 38.521-3 | TpAnalysisSpur(DC 20A n78A).zip | RAN5#92-e | +| DC 20A n28A | 38.521-3 | TpAnalysisSpur(DC 20A n28A).zip | RAN5#92-e | +| DC 21A n1A | 38.521-3 | TpAnalysisSpur(DC 21A n1A).zip | RAN5#94-e | +| DC 21A n28A | 38.521-3 | TpAnalysisSpur(DC 21A n28A).zip | RAN5#99 | +| DC 21A n77A | 38.521-3 | TpAnalysisSpur(DC 21A n77A).zip | RAN5#92-e | +| DC 21A n78A | 38.521-3 | TpAnalysisSpur(DC 21A n78A).zip | RAN5#92-e | +| DC 21A n79A | 38.521-3 | TpAnalysisSpur(DC 21A n79A).zip | RAN5#92-e | +| DC 25A n41A | 38.521-3 | TpAnalysisSpur(DC 25A n41A).zip | RAN5#100 | +| DC 25A n77A | 38.521-3 | TpAnalysisSpur(DC 25A n77A).zip | RAN5#100 | +| DC 26A n41A | 38.521-3 | TpAnalysisSpur(DC 26A n41A).zip | RAN5#100 | +| DC 26A n77A | 38.521-3 | TpAnalysisSpur(DC 26A n77A).zip | RAN5#100 | +| DC 26A n78A | 38.521-3 | TpAnalysisSpur(DC 26A n78A).zip | RAN5#92-e | +| DC 26A n79A | 38.521-3 | TpAnalysisSpur(DC 26A n79A).zip | RAN5#91-e | +| DC 28A n3A | 38.521-3 | TpAnalysisSpur(DC 28A n3A).zip | RAN5#92-e | +| DC 28A n5A | 38.521-3 | TpAnalysisSpur(DC 28A n5A).zip | RAN5#94-e | +| DC 28A n7A | 38.521-3 | TpAnalysisSpur(DC 28A n7A).zip | RAN5#94-e | +| DC 28A n78A | 38.521-3 | TpAnalysisSpur(DC 28A n78A).zip | RAN5#92-e | +| DC 28A n77A | 38.521-3 | TpAnalysisSpur(DC 28A n77A).zip | RAN5#92-e | +| DC 28A n79A | 38.521-3 | TpAnalysisSpur(DC 28A n79A).zip | RAN5#92-e | +| DC 30A n2A | 38.521-3 | TpAnalysisSpur(DC 30A n2A).zip | RAN5#101 | +| DC 30A n5A | 38.521-3 | TpAnalysisSpur(DC 30A n5A).zip | RAN5#100 | +| DC 30A n77A | 38.521-3 | TpAnalysisSpur(DC 30A n77A).zip | RAN5#100 | +| DC 39A n41A | 38.521-3 | TpAnalysisSpur(DC 39A n41A).zip | RAN5#94-e | +| DC 39A n79A | 38.521-3 | TpAnalysisSpur(DC 39A n79A).zip | RAN5#92-e | +| DC 40A n1A | 38.521-3 | TpAnalysisSpur(DC 40A n1A).zip | RAN5#92-e | +| DC 40A n41A | 38.521-3 | TpAnalysisSpur(DC 40A n41A).zip | RAN5#94-e | +| DC 40A n78A | 38.521-3 | TpAnalysisSpur(DC 40A n78A).zip | RAN5#92-e | +| DC 40A n79A | 38.521-3 | TpAnalysisSpur(DC 40A n79A).zip | RAN5#94-e | +| DC 41A n28A | 38.521-3 | TpAnalysisSpur(DC 41A n28A).zip | RAN5#98 | +| DC 41A n77A | 38.521-3 | TpAnalysisSpur(DC 41A n77A).zip | RAN5#100 | +| DC 41A n78A | 38.521-3 | TpAnalysisSpur(DC 41A n78A).zip | RAN5#92-e | +| DC 41A n79A | 38.521-3 | TpAnalysisSpur(DC 41A n79A).zip | RAN5#92-e | +| DC 42A n77A | 38.521-3 | TpAnalysisSpur(DC 42A n77A).zip | RAN5#92-e | +| DC 48A n5A | 38.521-3 | TpAnalysisSpur(DC 48A n5A).zip | RAN5#100 | +| DC 48A n66A | 38.521-3 | TpAnalysisSpur(DC 48A n66A).zip | RAN5#96-e | +| DC 66A n2A | 38.521-3 | TpAnalysisSpur(DC 66A n2A).zip | RAN5#88-e | +| DC 66A n5A | 38.521-3 | TpAnalysisSpur(DC 66A n5A).zip | RAN5#92-e | +| DC 66A n41A | 38.521-3 | TpAnalysisSpur(DC 66A n41A).zip | RAN5#96-e | +| DC 66A n71A | 38.521-3 | TpAnalysisSpur(DC 66A n71A).zip | RAN5#92-e | +| DC 66A n77A | 38.521-3 | TpAnalysisSpur(DC 66A n77A).zip | RAN5#94-e | +| DC 66A n78A | 38.521-3 | TpAnalysisSpur(DC 66A n78A).zip | RAN5#92-e | +| DC 71A n2A | 38.521-3 | TpAnalysisSpur(DC 71A n2A).zip | RAN5#100 | +| DC 71A n66A | 38.521-3 | TpAnalysisSpur(DC 71A n66A).zip | RAN5#98 | + +## 4.4 Test point analysis for satellite access test cases in TS 38.521-5 + +This section contains information on test point selection for NR NTN test cases in [10]. The general rules in this section apply to all the NR NTN test cases. Separate analysis is not provided for each single test case unless specific test requirement deviates from the general rules. + +General rules of test point selection: + +Considering that NR NTN operating bands are defined like FR1 FDD bands, test environment, frequencies, SCSs, channel bandwidths, waveforms, and modulations of a Tx or Rx test for an NR NTN band should be selected based on the same principles of the corresponding single carrier test for an FR1 FDD band. + +Table 4.4-1: NR UE transmitter test point selection for NTN + +| Subclause | Number of test points | Justification | Comments | +|----------------------------------------------------|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 6.2.1 UE maximum output power | 540 | General rules of test point selection apply. Test points of TC 6.2.1 from TS 38.521-1 can be leveraged. | RAN5#98 | +| 6.2.2 Maximum Output Power Reduction (MPR) | contiguous allocation: 1000 | General rules of test point selection apply. Test points of TC 6.2.2 from TS 38.521-1 can be leveraged except for the test point for almost contiguous allocation.

Note: There is no test point for almost contiguous allocation because test channel bandwidth for almost contiguous resource allocation should be greater than 20MHz, which is not supported by NR NTN operating bands. | RAN5#98 | +| 6.2.3 UE additional maximum output power reduction | 216 for NS_100; 264 for NS_24 | General rules of test point selection apply. AMPR test points for NS_100 and NS_24 in TC 6.2.3 of TS 38.521-1 can be leveraged. | RAN5#100 | +| 6.2.4 Configured transmitted power | 30 | General rules of test point selection apply. Test points of TC 6.2.4 from TS 38.521-1 can be leverageage except for Test ID 3, which applies to TDD bands only. | RAN5#99 | +| 6.3.1 Minimum output power | 45 | General rules of test point selection apply. Test points of TC 6.3.1 from TS 38.521-1 can be leveraged. | RAN5#98 | +| 6.3.3 Transmit On/OFF Time Mask | 40 | General rules of test point selection apply. Test points of TC 6.3.3 from TS 38.521-1 can be leveraged. | RAN5#100 | +| 6.4.1 Frequency error | 15 | 38.521-5_TPanalysis_6.4.1_FreqErr_v1.zip | RAN5#101 | +| 6.5.2.2 Spectrum emission mask | contiguous allocation: 144 | General rules of test point selection apply. Test points applicable to PC3 from TC 6.5.2.2 of TS 38.521-1 can be leveraged except for:

-: Test IDs for almost contiguous allocation because test channel bandwidth for almost contiguous resource allocation should be greater than 20MHz, which is not supported by NR NTN operating bands.
- Test IDs that are specified with NOTE 3 in Table 6.5.2.2.4.1-1 of TS 38.521-1, which applies to TDD bands only
- [Test IDs listed as applicable to UEs indicating support for UE capability lowPAPR-DMRS-PUSCHwithPrecoding-r16 ] | RAN5#100 | +| 6.5.2.4 Adjacent channel leakage ratio | contiguous allocation: 1000 | General rules of test point selection apply. Test points of TC 6.5.2.4 which are derived from Table 6.2.2.4.1-1 of TS 38.521-1, applicable to PC3, can be leveraged except for:

- Test IDs for almost contiguous allocation because test channel bandwidth for almost contiguous resource allocation should be greater than 20MHz, which is not supported by NR NTN operating bands.
- Test IDs that are specified with NOTE 3 in Table 6.2.2.4.1-1 of TS 38.521-1, which applies to TDD bands only | RAN5#100 | +| 6.5.3.1 General spurious emission | 27 | General rules of test point selection apply. Test points of TC 6.5.3.1 from TS 38.521-1 can be leveraged | RAN5#100 | +| 6.5.3.2 Spurious emissions for UE co-existence | 27 | General rules of test point selection apply. Test points of TC 6.5.3.2 from TS 38.521-1 can be leveraged | RAN5#100 | +| 6.5.4 Transmit intermodulation | 8 | General rules of test point selection apply. Test points of TC 6.5.4 from TS 38.521-1 can be leveraged | RAN5#100 | + +**Table 4.4-2: NR UE receiver test point selection for NTN** + +| Subclause | Number of test points | Justification | Comments | +|----------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------| +| 7.3.2 Reference sensitivity power level | 45 | General rules of test point selection apply. Test points of TC 7.3.2 from TS 38.521-1 can be leveraged | RAN5#100 | +| 7.4 Maximum input level | 3 | General rules of test point selection apply. Test points of TC 7.4 from TS 38.521-1 can be leveraged limiting the modulation to 64QAM. | RAN5#99 | +| 7.5 Adjacent channel selectivity
7.5 Adjacent channel selectivity | 3 | General rules of test point selection apply. Test points of TC 7.5 from TS 38.521-1 can be leveraged. | RAN5#101 | +| 7.6.2 In-band blocking | 3 | General rules of test point selection apply. Test points of TC 7.6.2 from TS 38.521-1 can be leveraged. | RAN5#101 | +| 7.6.3 Out of Band Blocking | 3 | General rules of test point selection apply. Test points of TC 7.6.3 from TS 38.521-1 can be leveraged. | RAN5#101 | +| 7.6.4 Narrow band blocking | 3 | General rules of test point selection apply. Test points of TC 7.6.4 from TS 38.521-1 can be leveraged. | RAN5#101 | +| 7.7 Spurious response | 3 | Same test points as TC 7.6.3 of TS 38.521-5. | RAN5#101 | +| 7.8.2 Wide band Intermodulation | 3 | General rules of test point selection apply. Test points of TC 7.8.2 from TS 38.521-1 can be leveraged. | RAN5#101 | +| 7.9 Spurious emissions | 3 | General rules of test point selection apply. Test points of TC 7.9 from TS 38.521-1 can be leveraged. | RAN5#101 | + +# Annex A: Derivation documents + +The documents and spreadsheets used to give the background for the selected test points for each test case are included in the present document as zip files. + +The name of the zip shall: + +- Include a prefix allowing easier grouping of file “38.521-1\_TPanalysis”, “38.521-2\_TPanalysis” or “38.521-3\_TPanalysis”. Files in the same area, e.g. . +- Include Test Case Number(s) and an abbreviation Test Case Name, e.g. “6.2.1\_MOP”, “7.6.2.InB\_Block” or “6.2.1\_MOP+6.2.2\_MPR”. +- In cases where multiple analysis is needed per test cases, e.g. for different CA configurations, include the CA band combination applicable in the parentheses, e.g. add “(1A-3A)” for CA\_1A-3A. + +Concatenated example file name: “38.521-1\_TPanalysis\_6.2.1\_MOP.zip”. + +If there is an update of test points for a test case the old corresponding zip file shall be replaced with a new zip file with a version stepping in the file name. e.g. “nnn\_v2.zip”. The aim is to provide a reference to completed test cases, so that test points for similar test cases can be selected on a common basis. + +For cases when no spreadsheet is used then the principles for selecting reference sensitivity test points are described in Annex B, C or D. + +# Annex B: Principles for test point selection for NR CA reference sensitivity test cases + +## B.1 General + +From TS 38.521-1 [2] (Table 7.3.2.4.1-1), the initial conditions used for NR RX reference sensitivity is given below. + +| Initial Conditions | | | | | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------|----------------------|-----------------------------------| +| Test Environment as specified in TS 38.508-1 [5] subclause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [5] subclause 4.3.1 | Low range, Mid range, High range (NOTE 4) | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [5] subclause 4.3.1 | Lowest, Mid, Highest (NOTE 4)
Lowest UL / Lowest DL, Lowest UL / Highest DL (NOTE 3) | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest | | | | +| Test Parameters | | | | | +| Test ID | Downlink Configuration | | Uplink Configuration | | +| | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM
QPSK | Full RB (NOTE 1) | DFT-s-OFDM QPSK | REFERENCE
SENSITIVITY (NOTE 2) | + +NOTE 1: Full RB allocation shall be used per each SCS and channel BW as specified in Table 7.3.2.4.1-2. +NOTE 2: REFERENCE SENSITIVITY refers to Table 7.3.2.4.1-3 which defines uplink RB configuration and start RB location for each SCS, channel BW and NR band. +NOTE 3: According to asymmetric channel bandwidths specified in clause 5.3.6. +NOTE 4: For n70, in addition to default test configurations, additional configurations shall be used to verify reference sensitivity requirements with the UE TX-RX frequency separation of 295MHz (table 5.4.4-1): +5 MHz CH BW with DL @ low range, UL @ mid range +5 MHz CH BW with DL @ mid range, UL @ high range +10 MHz CH BW with DL @ low range, UL @ high range + +For reference, the initial test condition for E-UTRA-CA (inter-band DL CA and UL CA) is listed below: (Table 7.3B.4.1-1 in TS 38.521-1 [2]) + +| Initial Conditions | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-------------------------|---------------|---------------------------------------------------------------|-------------------------------------------------------|---|---|---|--|--|--|--|--| +| Test Environment as specified in TS 36.508[7] subclause 4.1 | | | | | NC, TL/VL, TL/VH, TH/VL, TH/VH | | | | | | | | | | +| Test Frequencies as specified in TS36.508 [7] subclause 4.3.1 for different CA bandwidth classes, and PCC and SCCs are mapped onto physical frequencies according to Table 7.1-2 | | | | | B: Low range, High range
C: Low range, High range (Note 4) | | | | | | | | | | +| Test CC Combination setting ( $N_{RB\_agg}$ ) as specified in subclause 5.4.2A.1 for the CA Configuration across bandwidth combination sets supported by the UE. | | | | | Lowest $N_{RB\_agg}$ , Highest $N_{RB\_agg}$
(Notes 3, 4) | | | | | | | | | | +| Test Parameters for CA Configurations | | | | | | | | | | | | | | | +| CA Configuration / $N_{RB\_agg}$ | | DL Allocation | | UL Allocation | | | | | | | | | | | +| PCC $N_{RB}$ | SCCs $N_{RB}$ | CC MOD | PCC & SCC RB allocation | CC MOD | $N_{RB\_alloc}$ | PCC & SCC RB allocations ( $L_{CRB}$ @ $RB_{start}$ ) | | | | | | | | | +| 6 | 25 | QPSK | 6+25 | QPSK | 6 | P 6@0 | - | - | - | | | | | | +| 15 | 50 | QPSK | 15+50 | QPSK | 15 | P 15@0 | - | - | - | | | | | | +| 25 | 25 | QPSK | 25+25 | QPSK | 20 | P 20@0 | - | - | - | | | | | | + +## B.2 Test case structure + +This approach which is described in this clause is relying on certain properties of the RAN4 CA requirements and applies to both NR CA and EN-DC. + +1. For E-UTRA, fallbacks are skipped unless there is a documented exception in TS36.521-2. This may cause that a fallback is skipped even if no technical analysis has been made leading to insufficient testing of demanding CA configurations. For NR fallback can only be skipped if there has been a technical analysis performed in TR 38.905. +2. The RAN4 decision to only specify the affected (aggressor and victim) bands for an exception enables a different approach than in E-UTRA that in most cases makes fallback analysis redundant. This is not entirely true for requirements under clause 7.3A.5 and 7.3A.6 of TS38.101-1 [5] but it is assumed that the same approach can be used also in those cases as it greatly simplifies test cases. +3. Test cases can be split into *default* and *additional* test cases where default test cases only test where there is no exception (single carrier requirements apply), and additional only test the exceptions in TS 38.101-1 [5] clause 7.3A. +4. *Default* test cases need to be defined from 2 up to 5 CCs. Since they cover no exception, no fallback analysis is required, and the applicability rule should say that only highest CC number is required (similar to other Rx tests). +5. As the *default* test cases are not covering any CA exceptions, there is no need to configure UL CA in these test cases. Single UL configuration is sufficient to fulfil the test purpose. +6. *Additional* test cases only need to be defined for 2CC (and for intermodulation also 3CC) since this is sufficient for testing the exception. Adding more CCs is not considered to affect the test result and does not add any value. +7. *Additional* test cases only need to consider pure inter-band configurations since requirements are the same for intra-band contiguous or non-contiguous, and the essential aspect to test is the interference between bands. +8. It is important for sufficient test coverage to ensure that all band combinations with the highest number of CCs supported in the UE can always be tested. +9. The highest supported CC number may be with a band including an exception that can be avoided by setting a different test frequency (e.g. harmonic interference). In such cases, there is a need to include test points in the *default* test case so that this CA configuration can be tested without an exception (see example 1 below). +10. The highest supported CC number may be with a band including an exception that cannot be avoided by setting a different test frequency (e.g. cross band isolation). In this case the test requirements of the *default* test that are normally general for any CA config need to include this specific exception requirement. In addition, one + +fallback configuration needs to be tested to ensure test coverage of the single carrier requirement for the victim band that applies in this case. In order to simplify test applicability this fallback configuration will be specified inside the higher order test case (see example 2 below). + +11. The highest supported CC number may be with a band including a limitation that is not present in the lower order fallback (e.g. UL is not possible in one of the bands). In this case, one fallback configuration needs to be tested to ensure test coverage of the single carrier requirement with UL active in the band. In order to simplify test applicability this fallback configuration will be specified inside the higher order test case. + +12. To ensure that it has been checked that the CA configuration has been fully analysed with regard to test configuration and fallback testing, the CA configuration is listed in TR 38.905. + +## --- B.3 Test Environment + +Reference sensitivity is one of the critical test cases for NR. Considering NR CA testing scenario is very similar to E-UTRA\_CA test case, similar Test Environment shall be used for NR CA testing, i.e. NC, TL/VL, TL/VH, TH/VL, TH/VH. + +## --- B.4 Test Frequencies selection + +In E-UTRA DL CA and UL CA reference sensitivity testing, Low range and High range are selected for intra-band CA testing. Mid range is selected for inter band E-UTRA CA testing. + +Considering NR CA testing scenario is very similar to E-UTRA\_CA test case, similar Test Frequencies should be used for NR CA default case. + +It is proposed that Low and High Range are tested as default for intra-band and mid range for inter-band. For CA combinations containing intra-band configuration in an inter-band CA configuration it is proposed that low and high range are tested for intra-band CA and mid channel for inter-band without intra-band component. It is also proposed that the fallback configurations from intra-band configuration to single carrier component do not need to be tested even if the test frequency would differ (e.g. XA-YC -> XA-YA fallback does not need to be tested even if YC is tested with low/high frequency and YA would be tested with mid frequency). + +**Table B.4-1: Void** + +**Proposal 2a:** Low range and high range for intra band CA and mid range for inter-band CA shall be selected for NR in *default* test cases 7.3A.1 to 7.3A.4 in general, but final selection is band dependent. For CA combinations containing intra-band configuration in an inter-band CA configuration low and high range shall be selected for intra-band CA and mid channel for inter-band without intra-band component. The fallback configurations from intra-band configuration to single carrier component do not need to be tested even if the test frequency would differ. + +**Proposal 2b:** In the *additional* test case, one test frequency per exception is selected. + +### --- B.4A Frequency relation for exception requirements + +#### Intra-band + +No exceptions are applicable. + +#### Inter-band + +There are 4 different types of interference related to inter-band operation that results in refsens exception if the frequency relation of the exception is fulfilled. + +**Table B.4A-1: Exception types for inter-band (2 bands)** + +| Exception types | Aggressor | Victim | Frequency relation | +|------------------------------------------|---------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------| +| UL harmonic interference (HD) | Low band UL | High band DL | $a \cdot f_{UL\_LB} = f_{DL\_HB}$ | +| Receiver Harmonic Mixing (HM) | Low band DL LO and High band UL | Low band DL | $b \cdot f_{DL\_LB} + c \cdot f_{UL\_HB} = f_{DL\_LB}$ | +| Intermodulation due to Dual uplink (IMD) | Low band UL and High band UL | DL | $a \cdot f_{UL\_LB} + c \cdot f_{UL\_HB} = f_{DL\_LB}$
or
$a \cdot f_{UL\_LB} + c \cdot f_{UL\_HB} = f_{DL\_HB}$ | +| Cross band isolation (CBI) | UL on other than victim band | DL | | + +The exception requirements for dual uplink intermodulation apply only for a specified test frequency setting per UL configuration in TS 38.101-1 [5]. + +More details on how the exception requirements were derived can be found in TR series 37.865 (Rel-15), TR 38.716 (Rel-16) and TR 38.717 (Rel-17). These TRs can be used to identify all the applicable requirements for a certain EN-DC configuration which are otherwise spread out over multiple sections in TS 38.101-1 [5]. + +Some terminology from the RAN4 TRs for EN-DC that is listed in clause D.2.3 are re-used here to calculate test frequency for avoiding the exceptions, namely: + +$BW_{INT}$ : Effective bandwidth of the interference falling into the victim band which is $|a| \cdot BW_{LB} + |c| \cdot BW_{HB}$ , where a and c are factors from Table B.4A-1. + +$F_{INT}$ : Interference centre frequency within the victim band which is the offset from the frequency relation in Table B.4A-1. If $|F_{INT}| \geq (BW_{INT} + BW_{victim})/2$ the interference is not overlapping the victim carrier and exception requirements do not apply. + +## B.5 Test Channel Bandwidth selection + +The objective is how to verify the NR CA reference sensitivity. In intra-band E-UTRA CA reference sensitivity testing, two extreme bandwidth combinations corresponding to Lowest $NRB\_agg$ Highest $NRB\_agg$ are selected. Highest $NRB\_agg$ is selected for inter band E-UTRA CA testing. + +As a simplification the highest aggregated channel bandwidth is proposed to test NR CA reference sensitivity. + +**Proposal 3:** Highest aggregated channel bandwidth combinations shall be selected for NR CA reference sensitivity measurement. (Highest $NRB\_agg$ ). + +## B.6 Modulation selections + +QPSK is used for both uplink and downlink modulations for E-UTRA reference sensitivity measurement which is the same as for E-UTRA standalone reference sensitivity testing. There is no particular reason to deviate from current E-UTRA configurations of modulation scheme selection. NR modulations shall also follow what is selected in standalone NR testing. + +## B.7 Examples + +**Example 1** (highest CC number has an exception that can be avoided): + +- UE supports CA\_XA-YA-ZA-RA (4DL CA) + - CA\_X-Y has an exception if testing Low+Low freq + - CA\_X-Y has no exception if testing Mid+Mid freq + - Other bands pairs have no exception + +Applicable Test cases for the example: + +7.3A.1 2CC non-exception/“default” + +Skip test (no fallback analysis required) + +7.3B 3CC non-exception/“default” + +Skip test (no fallback analysis required) + +7.3A.3 4CC non-exception/“default” + +Test CA\_XA-YA-ZA-RA in Mid+Mid freq in bands X and Y respectively avoiding the exception + +7.3A.1\_1 2CC exception/“additional” + +Test CA\_X-Y in Low+Low freq + +**Example 2 (highest CC number has an exception that cannot be avoided):** + +- UE supports CA\_XA-YA-ZA-RA (4DL CA) + - CA\_X-Y has an exception always (e.g. cross band isolation) with band Y being the victim + - Other bands pairs have no exception + +Applicable Test cases for the example: + +7.3A.1 2CC non-exception/“default” + +Skip test (no fallback analysis required) + +7.3A.2 3CC non-exception/“default” + +Skip test (no fallback analysis required) + +7.3A.3 4CC non-exception/“default” + +Test CA\_XA-YA-ZA-RA and add exception in test requirements + +Add test points for 3CC fallback avoiding the exception CA\_YA-ZA-RA + +7.3A.1\_1 2CC exception/“additional” + +Test CA\_X-Y + +## --- B.8 Current test completion status per CA configuration + +The completion status per EN-DC configuration is documented in clause 4.3.3.1. + +## --- B.9 Reference Sensitivity checklist for CA + +The purpose of this annex is to facilitate the reference sensitivity test point analysis in TR 38.905 for NR CA configurations. + +### B.9.1 Checklist for two bands + +- 1) Check if the 2 DL band configuration has reference sensitivity exceptions in the tables listed below: + - UL Harmonic Distortion (HD), as defined in TS 38.101-1 [5], Table 7.3A.4-1. + - RX Harmonic Mixing (HM), as defined in TS 38.101-1 [5], Table 7.3A.4-4 to Table 7.3A.4-4a. + +- Intermodulation Distortion (IMD), as defined in TS 38.101-1 [5], Table 7.3A.5-1 to Table 7.3A.5-1a. + - Cross Band Isolation (CBI), as defined in TS 38.101-1 [5], Table 7.3A.6-1 to Table 7.3A.6-1b. +- 2) If reference sensitivity exceptions are found for two bands above: +- Add test frequencies for HD, HM and CBI to Table 4.1.3.1-6.. + - Add two band test points to test case in TS 38.521-1 [2] Table 7.3A.1\_1.4.1-1. +- 3) Add the result from the check to Table 4.1.3.1-2 for 2CC if they do not already exist. +- If there are no sensitivity exceptions then still add the band configuration to Table 4.1.3.1-2 with +NE: (Non-exception as defined in TS 38.101-1 [5], meaning single carrier NR requirements apply). +- 4) Add the 2 DL band configuration in TS 38.521-1 [2] Table 7.3A.1.5-1 + +### B.9.2 Checklist for three bands + +- 1) Check all three band fallback configurations in accordance to B.9.1. +- 2) Check for any 3DL/2UL IMD reference sensitivity exceptions in TS 38.101-1 [5], Table 7.3A.5-2 to Table 7.3A.5-2a. +- 3) If exceptions are found for three bands above: + - Add three band test points to test case in TS 38.521-1 [2] Table 7.3A.2\_1.4.1-1. +- 4) Add the result from the check to Table 4.1.3.1.3-3 for the three bands if they not already exist. + - If there are no sensitivity exceptions then still add the band configuration to Table 4.1.3.1-3 with +NE: (Non-exception as defined in TS 38.101-1 [5], meaning single carrier NR requirements apply). +- 5) Add the 3 DL band configuration in TS 38.521-1 [2] Table 7.3A.2.5-1 + +### B.9.3 Checklist for four bands and five bands + +- 1) Check all two band and three band fall backs in accordance to B.9.1 and B.9.2 above. + +No reference sensitivity exceptions exists for four bands and five bands in TS 38.101-1 [5]. + +# --- Annex C: Principles for test point selection for FR2 NR CA reference sensitivity test cases + +FFS + +# --- Annex D: Principles for test point selection for EN-DC reference sensitivity test cases + +## D.1 General + +The purpose of this Annex is to describe the test point selection of NR and E-UTRA carriers for RX sensitivity testing within FR1. Considering the high number of EN-DC band combinations, the procedure has been developed to carefully reduce the number of test points. Since the objective of TS 38.521-3 [4] specification is providing conformance testing requirement for NR in the case of EN-DC scenarios, the number of E-UTRA test points can be reduced. + +TS 38.521-3 [4] include exception test cases and non-exception test cases for inter-band EN-DC with FR1. The exceptional test cases must be tested as per configurations defined in TS 38.521-3 [4]. The procedure covers selection of both non-exceptional case and exception cases. + +When no NR or E-UTRA exception or additional requirements exist, the E-UTRA anchor is configured such that it does not interfere with NR operation (based on TS 38.101-3 [7] clause 6.1 and 7.1). The EN-DC testing is performed in E-UTRA anchor-agnostic mode. NR is tested but in SA as per TS 38.521-1 [2]. + +General initial conditions to be used for NR RX sensitivity testing are: + +**Table D.1-1: Initial test condition for standalone NR RX sensitivity** + +| Initial Conditions | | | | | +|-------------------------------------------------------------------------|------------------------------------------|------------------|----------------------|--------------------------------| +| Test Environment as specified in TS 38.508-1 [5] subclause 4.1 | Normal, TL/VL, TL/VH, TH/VL, TH/VH | | | | +| Test Frequencies as specified in TS 38.508-1 [5] subclause 4.3.1 | Low range, Mid range, High range | | | | +| Test Channel Bandwidths as specified in TS 38.508-1 [5] subclause 4.3.1 | Lowest, Mid, Highest | | | | +| Test SCS as specified in Table 5.3.5-1 | Lowest supported SCS per test channel BW | | | | +| Test Parameters | | | | | +| Test ID | Downlink Configuration | | Uplink Configuration | | +| | Modulation | RB allocation | Modulation | RB allocation | +| 1 | CP-OFDM QPSK | Full RB (Note 1) | DFT-s-OFDM QPSK | REFERENCE SENSITIVITY (Note 2) | + +## D.2 Requirements + +### D.2.1 Defined EN-DC configurations + +Downlink EN-DC configurations in 38.101-3 V16.5.0 clause 5.5B are: + +Currently defined downlink EN-DC configurations in 38.101-3 [7] V16.6.0 clause 5.5B are: + +- Intra-band contiguous EN-DC configurations within a single band includes max 2 NR CCs and max 3 E-UTRA CC, but in total max 4 CCs. +- Intra-band non-contiguous EN-DC configurations within a single band does not include NR CA (max 1NR CC), only E-UTRA CA (max 3 E-UTRA CC) +- Inter-band EN-DC configurations include up to 6 bands and 8 CCs but for NR the maximum is: + - 2 NR CCs in 1 band (nXC or nX(2A)) + - 4 NR CCs in 2 bands (nXA-nYA, nXA-nYC, nXA-nY(2A), nX(2A)-nY(2A)) +- Combinations of intra-band contiguous EN-DC + inter-band E-UTRA/NR CA. +- Combinations of intra-band non-contiguous EN-DC + inter-band E-UTRA/NR CA. + +Currently defined uplink EN-DC configurations in TS 38.101-3 [7] V16.6.0 clause 5.5B are: + +- The UL configuration contains at least 1 E-UTRA CC and 1 NR CC, meaning 2 UL CC. +- 3 UL CC configurations are also defined only with intra-band contiguous CA on either E-UTRA or NR (DC\_XA-nYC or DC\_XC-nYA). + +### D.2.2 Definition of exception requirements + +Before going into the test case details, the term “exception” needs to be clarified since it is different for EN-DC compared to SA. We can have the following situations: + +1. EN-DC config without exception + - a. Anchor agnostic, only need to be tested for UE not supporting SA + +2. EN-DC config with exception when the exception applies + - b. Need to be tested for all EN-DC UEs +3. EN-DC config with exception when the exception does not apply (single carrier requirement applies) + - c. Need to be tested for some exception types. Which exception types that need to this test coverage is defined in clause D.2.10.3. + - d. In some cases, it is not possible to avoid the exception. + - e. Anchor agnostic approach shall not be followed. It is important that E-UTRA aggressor is active to test performance when the interferer falls outside of the victim carrier + +### D.2.3 Reference sensitivity + +#### Intra-band + +Unlike for standalone NR, there are exceptions for intra-band operation, currently limited to band 3 for non-contiguous operation and band 71 for contiguous operation. + +The exceptions in band 3 is due to 2UL intermodulation interference making it similar to the corresponding inter-band intermodulation case. This scenario did not happen in standalone NR mode due to that there is no UL CA defined for CA\_n3(2A). + +It can therefore be treated in the same way as inter-band intermodulation and added in the “additional” test case. + +The intra-band contiguous exceptions are not expected to be very common. Currently only band 71 is affected, which can be added in the “additional” test case. + +#### Inter-band + +For both SA and NSA there are 4 different types of interference related to inter-band operation that results in refsens exception if the frequency relation of the exception is fulfilled. + +**Table D.2.3-1: Exception types for inter-band (2 bands)** + +| Exception types | Aggressor | Victim | Frequency relation | +|------------------------------------------|---------------------------------|--------------|--------------------------------------------------------------------------------------------------------| +| UL harmonic interference (HD) | Low band UL | High band DL | $a * f_{UL\_LB} = f_{DL\_HB}$ | +| Receiver Harmonic Mixing (HM) | Low band DL LO and High band UL | Low band DL | $b * f_{DL\_LB} + c * f_{UL\_HB} = f_{DL\_LB}$ | +| Intermodulation due to Dual uplink (IMD) | Low band UL and High band UL | DL | $a * f_{UL\_LB} + c * f_{UL\_HB} = f_{DL\_LB}$
or
$a * f_{UL\_LB} + c * f_{UL\_HB} = f_{DL\_HB}$ | +| Cross band isolation (CBI) | UL on other than victim band | DL | | + +The exception requirements for dual uplink intermodulation apply only for a specified test frequency setting per UL configuration in TS 38.101-3 [7]. + +More details on how the exception requirements were derived can be found in TR 37.863 (Rel-15), TR 37.716 (Rel-16) and TR 37.817 (Rel-17). These TRs can be used to identify all the applicable requirements for a certain EN-DC configuration which are otherwise spread out over multiple sections in TS 38.101-3 [7]. Additionally, the TRs specify exactly which aggressors that contribute to the exception for IMD which is not defined in the TS. Some terminology from the mentioned TRs are re-used here to calculate test frequency for avoiding the exceptions, namely: + +BWINT: Effective bandwidth of the interference falling into the victim band which is $|a| * BW_{LB} + |c| * BW_{HB}$ , where a and c are factors from Table D.2.3-1. + +FINT: Interference centre frequency within the victim band which is the offset from the frequency relation in Table D.2.3-1. If $|F_{INT}| \geq (BW_{INT} + BW_{victim})/2$ the interference is not overlapping the victim carrier and exception requirements do not apply. + +It has been agreed that for SA tests all the interference types except intermodulation can be tested with 1UL. Doing the same for NSA would simplify the test cases and would also mean that the main interferer (the aggressor) can be tested with higher power. + +Most other Rx requirements than reference sensitivity in intra-band contiguous EN-DC configuration require a configuration with 2UL however, meaning the “default” test cases need to be tested with 2UL active in this scenario + +There are combinations of intra-band contiguous/non-contiguous EN-DC + inter-band E-UTRA/NR CA which are listed in the inter-band EN-DC configuration tables of TS 38.101-3 [7]. These configurations do not add any exception requirements and are therefore proposed not to be tested unless they contain maximum number of NR CCs supported by the UE. + +### D.2.4 Rx requirements other than reference sensitivity + +The requirements are in some cases referring back to standalone requirements in TS 36.101/ TS 38.101-1. In other cases, specific exceptions for EN-DC are defined in TS 38.101-3 [7]. This is summarized in Table 2.1.3-1. + +**Table D.2.4-1: Rx requirements** + +| Clause | Title | Requirement | | | +|--------|-------------------|-----------------------|---------------------------|---------------------------------| +| | | Intra-band contiguous | Intra-band non-contiguous | Inter-band | +| 7.4B | Max input level | Exception with 2UL | Standalone | Standalone | +| 7.5B | ACS | Exception with 2UL | Standalone | Standalone | +| 7.6B.2 | IBB | Exception with 2UL | Standalone | Standalone | +| 7.6B.3 | OOBB | Exception with 2UL | Standalone | Standalone (only 2 band needed) | +| 7.6B.4 | NBB | Exception with 2UL | Standalone | Standalone | +| 7.7B | Spurious response | Exception with 2UL | Standalone | Standalone (only 2 band needed) | +| 7.8B | Intermodulation | Exception with 2UL | Standalone | Standalone | +| 7.9B | Rx spurious | Standalone | Standalone | Standalone | + +### D.2.5 Test case structure and test coverage + +As seen above, the EN-DC requirements are similar to the SA requirements from a structure point of view. Therefore, the same test case structure as for SA where test cases are separated into “default” and “additional” test cases can be considered for EN-DC which can greatly reduce complexity in TS 38.521-3[4] as well as reducing the need to complicated fallback test analysis. However, the additional complexity of EN-DC requirements means that a clear separation between exception (“additional”) test cases and “default” test cases is not as straightforward. + +The following principles are suggested for EN-DC Rx test cases: + +1. Let the 2CC test cases cover all reference sensitivity exceptions. Include test coverage of reference sensitivity when exception is avoided. +2. The 2CC test cases always need to be tested even for UE supporting more CCs since some of the exceptions are not covered in >2CC test cases. +3. Let the 3CC-5CC test cases cover mainly non-exception testing (anchor agnostic), including EN-DC not affected by exceptions and EN-DC affected by exceptions. 2UL 3 band intermodulation exceptions are tested in the 3CC test. Exceptions that 2CC fallback cannot cover are tested in 3CC test. +4. Highest number of NR CCs per band combination supported in the UE need to be tested. Anchor agnostic testing unless the EN-DC configuration has an exception requirement. Only 1 E-UTRA CC need to be tested for intra-band non-contiguous EN-DC and inter-band EN-DC. Maximum number of E-UTRA CCs need to be tested for intra-band contiguous EN-DC (1 band). This is further explained in clause 3.2.6. +5. Since requirements for 3UL and 2UL for the Rel-16 EN-DC configurations are the same there is no technical reason to test receiver requirements with 3UL configured. This may change in Rel-17 but will not have an impact on structure if we can add 3UL as new test points in existing tests. + +6. The test configuration shall be with 1UL or 2UL active depending on the exception type as indicated in Table D.2.5-1. + +**Table D.2.5-1: UL configuration to test** + +| Exception type | Intra-band contiguous EN-DC | Intra-band non-contiguous EN-DC | Inter-band EN-DC | +|-----------------------------------------------|-----------------------------|------------------------------------|-----------------------| +| Intra-band contiguous (band 71) | 2UL 1 | - | - | +| Intra-band non-contiguous (band 3) | - | 2UL 1 | - | +| UL harmonics, Rx mixing, cross band isolation | - | - | 1UL | +| 2UL Intermodulation | - | - | 2UL 1 | +| EN-DC config w/o exception | 2UL 2 | 1UL (anchor agnostic) 3 | 1UL (anchor agnostic) | + +NOTE 1: Exception requirements apply only with 2UL and apply only for one test frequency/BW setting. +NOTE 2: Other than refsens requirements in this configuration mandate 2UL +NOTE 3: Requirements in this configuration mandate 2UL (TS 38.101-3, 7.1) unless UE supports only single UL. +However, there is no Rel-16 configuration w/o exception where 2UL is supported meaning only 1UL is configured in the test case + +7. Void +8. Other than reference sensitivity test cases should use the MSD=0 test points defined in reference sensitivity test case, or minimum achievable MSD. This is currently ensured by using anchor agnostic configuration for inter-band EN-DC, but other solutions are not precluded. +9. Test cases need to be defined from 2 up to 5 CCs for Rel-16. The number of CCs may increase in Rel-17. The reason for not needing more than 5CC is that it is sufficient to test max number of NR CCs as well as all defined exceptions. + +### D.2.6 EN-DC configurations to test + +#### D.2.6.1 Lower order fallbacks + +In E-UTRA specifications, the lower order CA fallback cases are important in the test point analysis. If requirements are the same in the lower order fallback, then the fallback can be skipped to save test time. The same principle can be applied for EN-DC, but there is a need to keep in mind that this is only for CA fallback and not EN-DC fallback. Additionally, lower order CA fallbacks can be split into E-UTRA CA fallbacks and NR CA fallbacks. + +##### EN-DC fallback + +EN-DC fallback does not need to be handled since this would mean falling back to pure E-UTRA operation, which is covered by TS 36.521-1 test cases. + +##### E-UTRA CA fallback + +Since it has been agreed to use anchor agnostic approach for EN-DC test cases (TS 38.521-3 [4], clause 4.6), it is enough to test with 1 E-UTRA CC unless more CCs are needed to test an exception requirement in TS 38.101-3 [7]. + +There are exception requirements in TS 38.101-3 [7] for intra-band-contiguous EN-DC (not reference sensitivity, but other Rx requirements as shown in clause D.2.3) meaning the maximum number of E-UTRA CCs need to be tested in this scenario. + +E-UTRA CA fallback in intra-band contiguous EN-DC can result in change of EN-DC config from contiguous to non-contiguous (e.g. DC\_(n)41DA -> DC\_41C\_n41A). This change means requirements are different, but since the non-contiguous requirement is same as the standalone requirement it does not need to be tested. + +E-UTRA CA fallback in inter-band contiguous EN-DC can result in change of EN-DC config to intra-band contiguous (e.g. DC\_1A-(n)41AA->DC\_(n)41AA). This change means requirements are different, implying that both EN-DC config types may need to be tested. See clause D.2.6.2. + +##### NR CA fallback + +As shown in clause D.2.1, the maximum number of NR CCs for Rel-16 is 4, which only occurs in inter-band EN-DC (2 NR bands). The fallback to 2-3 NR CCs (2 bands) don't need to be tested since requirements are still the same. The fallback to single NR band with 1CC may need to be tested in the cases where the 2CC configuration had a reference sensitivity exception that is avoided in the higher order case. + +**Table D.2.6.1-1: EN-DC configurations requiring testing and max number of CCs** + +| Clause number | Title | Requirement coverage | EN-DC configuration type | | | +|---------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------|-------------------------------------------| +| | | | Intra-band cont EN-DC | Intra-band non-cont EN-DC | Inter-band EN-DC | +| 7.3B.2.1 | Reference sensitivity for Intra-band Contiguous EN-DC (2 CCs) | 1. Band n71 exceptions
2. standalone NR requirements | Yes | - | - | +| 7.3B.2.2 | Reference sensitivity for Intra-band non-contiguous EN-DC (2 CCs) | 1. Band n3 exceptions
2. standalone NR requirements | - | Yes | - | +| 7.3B.2.3 | Reference sensitivity for Inter-band EN-DC within FR1 (2 CCs) | 1. UL harmonics, harmonic mixing, cross band isolation, 2UL intermodulation (2 band)
2. standalone NR requirements | - | - | Yes | +| 7.3B.2.3_1.1 | Reference sensitivity for EN-DC within FR1 (3 CCs) | 1. standalone NR requirements,
2. 2UL intermodulation (3 band) | Yes
(2E-UTRA+1NR, Note 1) | - | Yes
(1E-UTRA+2NR, 2E-UTRA+1NR, Note 2) | +| 7.3B.2.3_1.2 | Reference sensitivity for EN-DC within FR1 (4 CCs) | standalone NR requirements | Yes
(3E-UTRA+1NR, Note 1) | - | Yes (
1E-UTRA+3NR, Note 4) | +| 7.3B.2.3_1.2 | Reference sensitivity for EN-DC within FR1 (5 CCs) | standalone NR requirements | - | - | Yes
(1E-UTRA+4NR, Note 4) | + +NOTE 1: This is needed for other than refsens Rx test case that refers back to refsens test config table +NOTE 2: For EN-DC configs affected by 2UL intermodulation, 2E-UTRA+1NR may need to be tested when E-UTRA CC1 is aggressor and E-UTRA CC2 is victim or when E-UTRA CC1 and CC2 are aggressors and NR CC is victim) +NOTE 3: Void +NOTE 4: Test of max number of NR CCs. Anchor agnostic testing. + +#### D.2.6.2 EN-DC configurations requiring testing and max number of CCs + +There is an issue in only requiring highest CC number to be tested, since this rule can only be applied within one EN-DC configuration type. For example, if the UE supports 3E-UTRA+1NR intra-band contiguous EN-DC and 1E-UTRA+2NR inter-band EN-DC, both configurations need to be tested for sufficient test coverage of core requirements. Another problem is that highest CC number to test within Inter-band EN-DC is not easy to determine it shall include 1 or 2 E-UTRA CCs, not more. + +#### D.2.6.3 Test coverage + +As explained in clause D.2.1 only certain configurations are specified in TS 38.101-3 [7]. + +Additionally, some configurations may not need to be tested for reasons like: + +- 1) To test an exception, it is sufficient to test with fewer CCs ("No test needed" in tables below) +- 2) No exception requirement exists ("N/A" in tables below) +- 3) No such configuration is defined in TS 38.101-3[7] clause 5.5B ("N/A" in tables below) + +For configurations that need to be tested, anchor agnostic approach can be used for E-UTRA when testing a non-exception requirement. In other cases, the E-UTRA carrier need to be fully configured. + +The different cases that may happen for 3CC and 4CC configurations, and the proposed test coverage are listed in the tables below where the following general rules have been applied: + +- Harmonic exceptions are only tested in the 2CC test and need not be considered in >2CC test cases. 2CC test cases are always run. +- Any inter-band EN-DC configuration with more than 2 E-UTRA bands will not be tested. +- Any inter-band EN-DC configuration with more than 1 E-UTRA CC per band will not be tested. + +**Table D.2.6.3-1: 3CC test coverage** + +| EN-DC type | E-UTRA CA | NR CA | Notation | Test coverage | | | +|------------|-----------|-------|----------|------------------------------------|-----------------------------------------------------|---------------------| +| | | | | Non-exception test points (NOTE 4) | Exception test points (NOTE 5) | | +| | | | | No exception | UL harmonics, harmonic mixing, cross band isolation | 2UL intermodulation | + +| | | | | | | | +|-------------------------------------------------------|----------------------|----------------------|------------------------------|---------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------| +| Intra-band contiguous EN-DC (1 band) | No | Yes | DC_(n)XAB | N/A | N/A | N/A | +| | Yes | No | DC_(n)XCA | Test needed due to other than refsens exception in intra-band EN-DC | N/A | N/A | +| Intra-band non-contiguous EN-DC (1 band) | Yes (cont) | No | DC_XC_nXA | No test needed. Only 2CC need to be tested | N/A | N/A | +| | Yes (non-cont) | No | DC_XA-XA_nXA
DC_XA_(n)XAA | No test needed. Only 2CC need to be tested | N/A | N/A | +| | No | Yes (cont) | Note 1 | N/A | N/A | N/A | +| | No | Yes (non-cont) | Note 1 | N/A | N/A | N/A | +| Inter-band EN-DC | No | Yes (intra-cont) | DC_XA_nYC | Test needed (if max NR CC) – anchor agnostic | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | No | Yes (intra-non-cont) | DC_XA_nY(2A) | Test needed (if max NR CC) – anchor agnostic | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | No | Yes (inter) | DC_XA_nYA-nZA | Test needed (if max NR CC) – anchor agnostic | Test needed (if exception involving 2 NR bands). 2CC need to be tested | Test needed (if IMD 3 band). 2CC need to be tested | +| | Yes (intra-cont) | No | DC_XC_nYA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | Yes (intra-non-cont) | No | DC_XA-XA_nYA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | Yes (inter) | No | DC_XA-YA_nZA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | Test needed if IMD(3 band). 2CC need to be tested. | +| Inter-band + Intra-band contiguous EN-DC (2 band) | No | Yes | DC_(n)XAA-nYA | Test needed (if max NR CC) – anchor agnostic | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | Yes | No | DC_XA-(n)YAA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| Inter-band + Intra-band non-contiguous EN-DC (2 band) | No | Yes | DC_XA_nXA-nYA | Test needed (if max NR CC) – anchor agnostic | Test needed (if exception involving 2 NR bands). 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | Yes | No | DC_XA-YA_nYA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | + +NOTE 1: No such config in TS 38.101-3 [7] V16.5.0 + +NOTE 2: CC BW class C is indicated in the table. The same rules apply to BW class B + +NOTE 3: Different test coverage is indicated by colour coding in this table. + +NOTE 4: Applicable to both EN-DC configurations not affected by any exception and EN-DC configurations affected by exceptions, corresponding to Table 7.3B.2.3\_1.1.4.1-0 in TS 38.521-3. + +NOTE 5: Only applicable to EN-DC configurations affected by exceptions, including UL harmonics, harmonic mixing, cross band isolation and 2UL intermodulation, corresponding to Table 7.3B.2.3\_1.1.4.1-1 in TS 38.521-3. + +Table D.2.6.3-2: 4CC test coverage + +| EN-DC type | E-UTRA CA | NR CA | Notation | Test coverage | | +|------------|-----------|-------|----------|------------------------------------|----------------------------------------------------| +| | | | | Non-exception test points (NOTE 4) | Exception test points (NOTE 5) | +| | | | | No exception | UL harmonics, harmonic mixing, 2UL intermodulation | + +| | | | | | cross band isolation | | +|---------------------------------------------------------|-----------------|----------------|-----------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------|-----------------------------------------------------------------------------| +| Intra-band contiguous EN-DC (1 band) | No | Yes | NOTE 1 | N/A | N/A | N/A | +| | Yes | No | DC_(n)XDA | Test needed due to other than refsens exception in intra-band EN-DC | N/A | N/A | +| Intra-band non-contiguous EN-DC (1 band) | Yes (cont) | No | DC_XD_nXA | No test needed. Only 2CC need to be tested | N/A | N/A | +| | Yes (non-cont) | No | NOTE 1 | N/A | N/A | N/A | +| | No | Yes (cont) | NOTE 1 | N/A | N/A | N/A | +| | No | Yes (non-cont) | NOTE 1 | N/A | N/A | N/A | +| Inter-band EN-DC | No | Yes (cont) | NOTE 1 | N/A | N/A | N/A | +| | No | Yes | DC_XA_nY(2A)-nZA | Test needed (if max NR CC) – anchor agnostic | No test needed. Only 2CC need to be tested | No test needed. 2CC need to be tested. 3CC need to be tested if IMD(3 band) | +| | No | Yes | DC_XA_nYA-nZC | Test needed (if max NR CC) – anchor agnostic | No test needed. Only 2CC need to be tested | No test needed. 2CC need to be tested. 3CC need to be tested if IMD(3 band) | +| | Yes (all types) | No | DC_XD_nYA, DC_XA-YC_nZA, DC_XA-XA-YA_nZA, DC_XA-YA-ZA_nRA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. 2CC need to be tested. 3CC need to be tested if IMD(3 band) | +| | Yes (all types) | Yes (cont) | DC_XC_nYC, DC_XA-XA_nYC, DC_XA-YA_nYC | No test needed. 3CC need to be tested if max NR CC | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | | Yes (non-cont) | DC_XC_nY(2A), DC_XA-YA_nY(2A) | No test needed. 3CC need to be tested if max NR CC | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | | Yes (inter) | DC_XC_nYA-nZA, DC_XA-XA_nYA-nZA, DC_XA-YA_nZA-nRA | No test needed. 3CC need to be tested if max NR CC | No test needed. Only 2CC need to be tested | No test needed. 2CC need to be tested. 3CC need to be tested if IMD(3 band) | +| Inter-band + Intra-band contiguous EN-DC (2-3 band) | No | Yes | NOTE 1 | N/A | N/A | N/A | +| | Yes | No | DC_XA-YA_(n)ZAA, DC_XC_(n)YAA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| | Yes | Yes | DC_(n)XCA-nYA | No test needed. 3CC need to be tested if max NR CC | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | +| Inter-band + Intra-band non-contiguous EN-DC (2-3 band) | No | Yes | NOTE 1 | N/A | N/A | N/A | +| | Yes | No | DC_XA-YA-ZA_nZA | No test needed. Only 2CC need to be tested | No test needed. Only 2CC need to be tested | No test needed. 2CC need to be tested. 3CC need to be tested if IMD(3 band) | +| | Yes | Yes | DC_XA-YA_nYA-nZA | No test needed. 3CC need to be tested if max NR CC | No test needed. Only 2CC need to be tested | No test needed. 2CC need to be tested. 3CC need to be tested if IMD(3 band) | + +NOTE 1: No such config in TS 38.101-3 [7] V16.5.0 + +NOTE 2: 2CC BW class C is indicated in the table. The same rules apply to BW class B + +NOTE 3: Different test coverage is indicated by colour coding in this table. + +NOTE 4: Applicable to both EN-DC configurations not affected by any exception and EN-DC configurations affected by exceptions, corresponding to Table 7.3B.2.3\_1.2.4.1-1. + +NOTE 5: Only applicable to EN-DC configurations affected by exceptions, including UL harmonics, harmonic mixing, cross band isolation and 2UL intermodulation. + +### D.2.7 Test Environment + +The test environment for FR1 EN-DC RX sensitivity measurement is Normal, TL/VL, TL/VH, TH/VL, TH/VH (same as for NR CA). + +### D.2.8 Test Frequencies selections for EN-DC + +In E-UTRA DL CA and UL CA reference sensitivity testing, Low range and High range are selected for intra-band CA testing. Mid-range is selected for inter band E-UTRA CA testing. + +In standalone NR CA reference sensitivity testing, Low and High Range are tested as default for intra-band and Mid-range for inter-band. For CA combinations containing intra-band configuration in an inter-band CA configuration, low and high range are tested for intra-band CA and mid channel for inter-band without intra-band component. + +The same principle shall apply for EN-DC testing. + +**Table D.2.8-1: Void** + +For EN-DC configurations affected by IMD exceptions where the exception is avoided, the test frequency and bandwidth are FFS. + +### D.2.9 Test EN-DC channel bandwidth + +#### D.2.9.1 Test point selection EN-DC configuration without exception + +Follow similar arguments for frequency selection, for regular inter-band EN-DC and intra-band non-contiguous testing, the NR channel bandwidths shall follow what is specified in SA scenario. Since the objective is to test NR performance, it is sufficient to select 5 MHz channel bandwidth for E-UTRA carrier, which is common for all E-UTRA bands. + +For intra-band contiguous EN-DC testing, the highest bandwidth is selected for E-UTRA carrier and NR carrier, respectively. + +#### D.2.9.2 Test point selection EN-DC configuration with exception + +For inter-band EN-DC configuration with exception requirement due to UL harmonics, Rx mixing and cross band isolation, the highest channel bandwidth shall be tested for E-UTRA and NR carrier. + +For inter-band EN-DC configuration with exception requirement due to 2UL intermodulation, the test channel bandwidth selection for both NR and E-UTRA are EN-DC combo dependent. There are fixed channel bandwidth pairs required for these exceptional test scenarios. + +For intra-band EN-DC configuration with exception requirement, the test channel bandwidth selection for both NR and E-UTRA are EN-DC combo dependent. There are fixed channel bandwidth pairs required for these exceptional test scenarios. + +Only 5 MHz channel bandwidth shall be employed by E-UTRA band, Lowest, Mid, Highest channel bandwidth shall be selected for NR carrier for EN-DC non-exceptional testing. + +### D.2.10 RB allocation and RB location selections + +#### D.2.10.1 Test point selection EN-DC configuration without exception + +Following the E-UTRA anchor-agnostic proposed in R5-185916 [6], E-UTRA operation does not interfere with NR connection, 0 RB were proposed for both UL and DL channels for non-exceptional test scenarios. + +There is no reason to deviate from current NR configurations for RB allocation selection employed in standalone testing. + +#### D.2.10.2 Test point selection EN-DC configuration with exception when exception applies + +For EN-DC inter-band and intra-band EN-DC exceptional test scenarios, the RB allocation for both NR and E-UTRA are selected as specified in TS 38.101-3 [7] for the EN-DC band combination. + +Based on the E-UTRA anchor-agnostic approach, 0 RB shall be used for both UL and DL channels for non-exceptional test scenarios. RB allocation for NR carrier in inter-band EN-DC non-exceptional testing shall follow what is selected for standalone testing. + +#### D.2.10.3 Test point selection EN-DC configuration with exception when exception does not apply + +According to the test principle outlined in clause D.2.5, there is a need to verify the UE performance when the exception is avoided and MSD=0 dB applies. Detailed background can be found in [9]. + +The calculation of test frequency for avoiding exceptions is presented in clause 2.5. The UL configuration also need to be determined and may be with one or two simultaneous UL CCs depending on the scenario. + +For HD and HM exceptions when the victim band is TDD there is no need from an interference point of view to have UL active on the victim band, meaning this can be verified with 1UL. The same can apply for EN-DC configurations where single switched Tx is allowed. In the case of FDD victim band when 2UL Is mandatory, both UL CCs should be active since this represents the worst case. + +For CBI exceptions the requirements are defined in two different ways depending on the EN-DC configuration: + +1. Exception applies for any frequency separation as long as aggressor UL is active. In this case, the only way to avoid the exception is to not have UL active on the aggressor band. The test point then becomes very similar to the standalone test and then does not need to be tested for a SA and NSA capable UE. Therefore, CBI exception avoiding could not be tested for this kind of combinations. +2. Exception applies only if separation is small. Just like for HD and HM exceptions, the exception can be avoided by configuring a larger separation with aggressor signal still active. + +For 2-band IMD exceptions, the exception is avoided by changing the frequency of one of the CCs such that the intermodulation does not overlap with the victim CC anymore. In the case of multiple IMD affecting the same victim band, only the worst case IMD may be tested. However, in TS 38.101-3[7], there is no general criteria in which REFSENS can be fulfilled with MSD=0 for the EN-DC combinations which have MSD exceptions due to IMD interference (2 UL active). The 2-band IMD exception avoiding testing is still FFS in TS 38.521-3[4]. + +For 3-band IMD exceptions there are a separate set of IMD depending on the UL configuration (selecting 2UL among 3 bands gives two cases). Within a UL configuration, the same test point selection as for 2-band IMD can be used. + +### D.2.11 Modulation scheme selections + +The modulation scheme for both non-exceptional and exceptional EN-DC intra-band and inter-band test scenarios are selected as: + +- For E-UTRA: QPSK (same as used for E-UTRA reference sensitivity testing in TS 36-521-1 [9]) +- For NR: Use same modulation scheme as used for NR standalone testing. + +### D.2.12 Current test completion status per EN-DC configuration + +The completion status per EN-DC configuration is documented in clause 4.3.3.1. + +# Annex E: Change history + +| Change history | | | | | | | | | +|----------------|--------------------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2017-09 | RAN5#76 | R5-174704 | - | - | - | Draft skeleton TR 38.905 | 0.0.1 | | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-181954 | - | - | - | Agreed Text Proposal in RAN5#2-5G-NR Adhoc:
R5-181889 , " TP to update TR 38.905 with information on test point analysis "

Agreed Test Point Analysis in RAN5#78:
R5-180885 , "Discussion on test point selection for NR Occupied Bandwidth in FR1"
R5-180886 , "Discussion on test point selection for NR SEM in FR1"
R5-180887 , "Discussion on test point selection for NR ACLR in FR1"
R5-181524 , "Discussion on test point selection for Absolute Power Tolerance in FR1"
R5-181525 , "Discussion on test point selection for Aggregate Power Tolerance in FR1"

Agreed Test Point Analysis in RAN5#2-5G-NR Adhoc:
R5-182019 , "Discussion of NR FR1 Test Point for TX Spurious Emission test cases "
R5-182024 , "Discussion on test point selection for NR Frequency Error in FR1"
R5-181830 , "Discussion on test point selection for Maximum Output Power in FR1"
R5-181831 , "Discussion on test point selection for Minimum Output Power in FR1"
R5-181832 , "Discussion on test point selection for General ON/OFF Time Mask in FR1"
R5-181879 , "Discussion on test point selection for NR In-Band in FR1"
R5-181880 , "Discussion on test point selection for NR ACS in FR1"
R5-182025 , "Discussion on test point selection for NR Frequency Error in FR1"

R5-181905 , "Discussion on test point selection for NR Occupied Bandwidth in FR2"
R5-182030 , "Discussion on test point selection for NR ACLR in FR2"
R5-182042 , "Discussion on test point selection for NR In-Band blocking in FR2"
R5-182044 , "Discussion on test point selection for NR ACS in FR2" | 0.1.0 | | +| 2018-05 | RAN5#79 | R5-183078 | - | - | - | Document title corrected.

Agreed Text Proposal in RAN WG5#79:
R5-183963 , "Test Point analysis for FR1 RefSens test case" | 0.2.0 | | +| 2018-08 | RAN5#80 | R5-185134 | - | - | - | R5-184923 , "Test Point analysis for FR2 RefSense test case"
R5-184961 , "TP for updating TR 38.905 with FR2 Frequency Error test point analysis"
R5-185307 , "TP for updating TR38.905 with FR1 AMPR test point analyses with NS_35"
R5-185309 , "Test Point analysis for FR1 Configured Output Power for SUL"
R5-185311 , "TP for updating TR 38.905 with FR1 Carrier Leakage test point analysis"
R5-185314 , "TP for updating TR 38.905 with FR1 EVM equalizer spectrum flatness test point analysis"
R5-185316 , "TP for updating TR 38.905 with FR1 Frequency Error test point analysis"
R5-185412 , "TP for updating TR 38.905 with EVM test point analysis"
R5-185491 , "Test Point analysis for FR2 TxSpurious test case"
R5-185215 , "TP for updating TR 38.905 with FR2 SEM test point analysis"
R5-185334 , "Discussion of LTE Test point selection for EN-DC with FR1 Tx Spurious emission Test"
R5-185301 , "Discussion on test point selection for NR Out-of-band in FR1"
R5-185423 , "Discussion on Uplink configuration for NR Transmit Intermodulation in FR1"
R5-185216 , "TP for updating TR38.905 with UE AMPR for NS_04 Intra-band contiguous EN-DC"
R5-185319 , "TP for updating TR 38.905 with FR1 In-band Emissions test point analysis" | 1.0.0 | | +| 2018-09 | RAN#81 | - | - | - | - | raised to v15.0.0 with editorial changes only | 15.0.0 | | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | RAN#82 | R5-186454 | 0016 | - | F | TP analysis for test case 6.5.2.4.2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186455 | 0017 | - | F | TP analysis for EN-DC test case 6.2B.2.3 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186609 | 0018 | - | F | TP analysis for TX spurious emission UE co-existence for intra-band contiguous EN-DC with FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186610 | 0019 | - | F | TP analysis for Reference sensitivity for Intra-band Contiguous EN-DC with FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186611 | 0020 | - | F | TP analysis for Reference sensitivity for Inter-band EN-DC with FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186674 | 0021 | - | F | Test point analysis for AMPR Intra-band contiguous EN-DC in FR1 for NS_35 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186710 | 0022 | - | F | TP analysis for test case 6.2B.2.4, UE Maximum Output Power reduction for Inter-Band EN-DC including FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-186791 | 0028 | - | F | TP analysis OBW intraband contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-186792 | 0029 | - | F | TP analysis SEM intraband contiguous EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187035 | 0031 | - | F | Update test points analysis for multiple FR1 test cases | 15.1.0 | +| 2018-12 | RAN#82 | R5-187396 | 0037 | - | F | Update of TR 38.905 with SA FR1 A-MPR test point analyses, NS_04 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188240 | 0039 | 1 | F | Update of TR 38.905 with EN-DC A-MPR test point analyses, NS_04 | 15.1.0 | +| 2018-12 | RAN#82 | R5-188227 | 0041 | 1 | F | Test Point analysis for FR2 Maximum Output Power | 15.1.0 | +| 2018-12 | RAN#82 | R5-187489 | 0042 | - | F | TP analysis for FR1 test case 6.3.4.3, relative power tolerance | 15.1.0 | +| 2018-12 | RAN#82 | R5-187582 | 0043 | - | F | Discussion on test point selection for EVM in FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187583 | 0044 | - | F | Discussion on test point selection for Carrier Leakage in FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187584 | 0045 | - | F | Update of test point selection for EVM equalizer spectrum flatness in FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187587 | 0046 | - | F | Discussion on test point selection for In-band Emissions in FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187589 | 0047 | - | F | Discussion on test point selection for EVM equalizer spectrum flatness in FR2 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187593 | 0048 | - | F | Discussion on test point selection for EVM equalizer spectrum flatness for Pi/2 BPSK in FR1 | 15.1.0 | +| 2018-12 | RAN#82 | R5-187806 | 0023 | 1 | F | Test Point analysis for FR1 7.4 Maximum input level | 15.1.0 | +| 2018-12 | RAN#82 | R5-187808 | 0035 | 1 | F | TP analysis for receiver spurious emission tests for FR1 SA | 15.1.0 | +| 2018-12 | RAN#82 | R5-187809 | 0036 | 1 | F | TP analysis for wideband intermodulation tests for FR1 SA | 15.1.0 | +| 2018-12 | RAN#82 | R5-187817 | 0033 | 1 | F | TP analysis for receiver spurious emission tests for FR1 inter-band EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187818 | 0034 | 1 | F | TP analysis for wideband intermodulation tests for FR1 inter-band EN-DC | 15.1.0 | +| 2018-12 | RAN#82 | R5-187836 | 0025 | 1 | F | Test Point analysis for FR2 7.4 Maximum input level | 15.1.0 | +| 2018-12 | RAN#82 | R5-187907 | 0024 | 1 | F | Test Point analysis for FR1 MPR test case | 15.1.0 | +| 2019-03 | RAN#83 | R5-191257 | 0077 | - | F | Test Point analysis for TC 6.3.3.4 PRACH time mask in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191260 | 0078 | - | F | Test Point analysis for NR Narrow band in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191261 | 0079 | - | F | Test Point analysis for NR spurious response in FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191337 | 0081 | - | F | Adding test case 6.2B.2.1 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-191678 | 0086 | - | F | Addition of TP analysis of FR2 6.3.1 Minimum output power | 15.2.0 | +| 2019-03 | RAN#83 | R5-191811 | 0087 | - | F | Test Point analysis update for FR2 TxSpurious test case | 15.2.0 | +| 2019-03 | RAN#83 | R5-191855 | 0091 | - | F | TP analysis 38.905 6.5.3.1 TX SpurEmission | 15.2.0 | +| 2019-03 | RAN#83 | R5-192002 | 0104 | - | F | Adding test case 7.4B.1 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192003 | 0105 | - | F | Adding test case 7.4B.2 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192007 | 0106 | - | F | Adding test case 6.2B.1.1 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192008 | 0107 | - | F | Adding test case 6.2B.1.2 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192009 | 0108 | - | F | Adding test case 6.2B.1.3 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192239 | 0116 | - | F | TP analysis of FR1 time alignment error for UL MIMO | 15.2.0 | +| 2019-03 | RAN#83 | R5-192401 | 0085 | 1 | F | Addition of TP analysis of FR1 6.2.4 Configured transmitted power | 15.2.0 | +| 2019-03 | RAN#83 | R5-192404 | 0099 | 1 | F | TP analysis for FR1 6.5A.2.4.1.1 NR ACLR for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192405 | 0100 | 1 | F | TP analysis for FR1 6.5A.2.4.2.1 UTRA ACLR for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192406 | 0103 | 1 | F | TP analysis for FR1 6.5A.4.1 Transmit intermodulation for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192410 | 0110 | 1 | F | Update of TP analysis of FR1 6.3.1 Minimum Output Power | 15.2.0 | +| 2019-03 | RAN#83 | R5-192444 | 0113 | 1 | F | Addition of TP analysis for EN-DC 6.2B.4.1.3 Configured transmitted power inter-band within FR1 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192449 | 0080 | 1 | F | Adding FR2 test case 6.3.4.3 to 38.905 | 15.2.0 | +| 2019-03 | RAN#83 | R5-192546 | 0082 | 1 | F | Test Point analysis for FR1 6.3.3.6 SRS time mask | 15.2.0 | +| 2019-03 | RAN#83 | R5-192568 | 0095 | 1 | F | TP analysis for FR1 6.4A.2.1.1 Error Vector Magnitude for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192569 | 0094 | 1 | F | TP analysis for FR1 6.4A.1.1 Frequency error for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192571 | 0096 | 1 | F | TP analysis for FR1 6.4A.2.2.1 Carrier leakage for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192572 | 0097 | 1 | F | TP analysis for FR1 6.4A.2.3.1 In-band emissions for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192573 | 0098 | 1 | F | TP analysis for FR1 6.5A.2.2.1 Spectrum emission mask for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192574 | 0101 | 1 | F | TP analysis for FR1 6.5A.3.1.1 General spurious emissions for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192575 | 0102 | 1 | F | TP analysis for FR1 6.5A.3.2.1 Spurious emissions for UE co-existence for CA (2UL CA) | 15.2.0 | +| 2019-03 | RAN#83 | R5-192582 | 0109 | 1 | F | Add Tp analysis statements for MIMO tests | 15.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | RAN#83 | R5-192599 | 0084 | 1 | F | Update of TP analysis of FR1 6.2.1 MOP | 15.2.0 | +| 2019-03 | RAN#83 | R5-192624 | 0115 | 1 | F | TP analysis 38.905 6.5B.3 TX SpurEmission | 15.2.0 | +| 2019-03 | RAN#83 | R5-192647 | 0092 | 1 | F | Addition of Test Point analysis of FR2 6.3.4.4 Aggregate power tolerance | 15.2.0 | +| 2019-03 | RAN#83 | R5-192684 | 0073 | 1 | F | TP analysis for FR1 Rx 7.9A.1 Spurious Emission for 2DL CA | 15.2.0 | +| 2019-03 | RAN#83 | R5-192691 | 0111 | 1 | F | Addition of TP analysis for EN-DC 6.2B.4.1.1 Configured transmitted power Intra-band contiguous | 15.2.0 | +| 2019-03 | RAN#83 | R5-192692 | 0112 | 1 | F | Addition of TP analysis for EN-DC 6.2B.4.1.2 Configured transmitted power Intra-band non-contiguous | 15.2.0 | +| 2019-03 | RAN#83 | R5-192846 | 0114 | 2 | F | Introduction of new section for Tp analysis of Tx spurious | 15.2.0 | +| 2019-06 | RAN#84 | R5-193543 | 0137 | - | F | Additional TT analysis for 38.521-3 MPR intra-band contiguous | 15.3.0 | +| 2019-06 | RAN#84 | R5-193808 | 0147 | - | F | Addition of TP analysis for power control for UL-MIMO | 15.3.0 | +| 2019-06 | RAN#84 | R5-193916 | 0148 | - | F | Update of TP analysis of 6.2D.3 A-MPR for UL-MIMO | 15.3.0 | +| 2019-06 | RAN#84 | R5-193919 | 0149 | - | F | Add SA FR1 RF 6.5D.2.4.2 to 38.905 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194010 | 0151 | - | F | Test Point analysis update for FR2 TxSpurious UE coexistence test case | 15.3.0 | +| 2019-06 | RAN#84 | R5-194168 | 0152 | - | F | Updating Annex A; Derivation documents | 15.3.0 | +| 2019-06 | RAN#84 | R5-194169 | 0153 | - | F | Update of test points analysis for NS 35 A-MPR FR1 test case | 15.3.0 | +| 2019-06 | RAN#84 | R5-194170 | 0154 | - | F | Test point analysis for A-MPR Intra-band contiguous EN-DC; NS_04 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194257 | 0155 | - | F | TP analysis for Asymmetric CH BWs in Reference Sensitivity Requirements in FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194402 | 0158 | - | F | Test Point analysis for EN-DC In-band emissions for intra-band contiguous | 15.3.0 | +| 2019-06 | RAN#84 | R5-194459 | 0160 | - | F | Update to TP analysis for FR2 Maximum Output Power | 15.3.0 | +| 2019-06 | RAN#84 | R5-194904 | 0142 | 1 | F | Addition of TP analysis for 38.521-1 7.6D.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194907 | 0163 | 1 | F | Addition of TP analysis for 38.521-1 6.3A.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194909 | 0164 | 1 | F | Addition of TP analysis for 38.521-1 6.3A.1 FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194913 | 0165 | - | F | Addition of TP analysis for ACS for 2DL CA in FR1 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194914 | 0166 | - | F | Addition of TP analysis for FR1 MOP for CA | 15.3.0 | +| 2019-06 | RAN#84 | R5-194927 | 0162 | 1 | F | Addition of test frequency selection of spurious co-existence inter-band for DC 3-n79 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194931 | 0141 | 1 | F | Addition of TP analysis for 38.521-1 7.6D.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194932 | 0143 | 1 | F | Addition of TP analysis for 38.521-1 7.6D.4 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194933 | 0144 | 1 | F | Addition of TP analysis for 38.521-1 7.8D.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194959 | 0167 | - | F | Addition of TP analysis for UL-MIMO cases of 6.3D.1 and 6.3D.3 | 15.3.0 | +| 2019-06 | RAN#84 | R5-194961 | 0157 | 1 | F | TP analysis for FR2 Tx 6.3A.1.1 Minimum output power for CA 2UL CA | 15.3.0 | +| 2019-06 | RAN#84 | R5-194963 | 0161 | 1 | F | Update SCS test points for FR2 ACS and Inband blocking test cases | 15.3.0 | +| 2019-06 | RAN#84 | R5-195146 | 0138 | 1 | F | Addition of TP analysis for SA FR2 6.2.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195148 | 0139 | 1 | F | Addition of TP analysis for SA FR2 6.3.2 | 15.3.0 | +| 2019-06 | RAN#84 | R5-195190 | 0145 | 1 | F | TPanalysis of 7.7D Spurious response for UL-MIMO | 15.3.0 | +| 2019-06 | RAN#84 | R5-193730 | 0146 | - | F | Addition of test frequency selection of 6.5A.3.2 for Rel-16 CA_n41A-n79A | 16.0.0 | +| 2019-06 | RAN#84 | R5-195055 | 0150 | 1 | F | Addition of test frequency selection of 6.5B.3.3.2 spurious co-existence inter-band for Rel-16 DC configurations | 16.0.0 | +| 2019-09 | RAN#85 | R5-196435 | 0184 | - | F | Update of TP analysis of FR2 minimum output power to add UL MIMO | 16.1.0 | +| 2019-09 | RAN#85 | R5-196445 | 0185 | - | F | Correction of 4.5 to add DC_3A-n41 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197315 | 0175 | 1 | F | Addition of TP analysis for FR1 MPR for CA | 16.1.0 | +| 2019-09 | RAN#85 | R5-197317 | 0176 | 1 | F | Addition of TP analysis for FR1 ConfigTP for CA | 16.1.0 | +| 2019-09 | RAN#85 | R5-197320 | 0179 | 1 | F | Addition of TP analysis of FR1 6.4D.2.1 EVM for UL MIMO | 16.1.0 | +| 2019-09 | RAN#85 | R5-197322 | 0180 | 1 | F | Addition of TP analysis of FR1 6.4D.2.2 Carrier leakage for UL MIMO | 16.1.0 | +| 2019-09 | RAN#85 | R5-197323 | 0181 | 1 | F | Addition of TP analysis of FR1 6.4D.2.3 Inband emission for UL MIMO | 16.1.0 | +| 2019-09 | RAN#85 | R5-197325 | 0182 | 1 | F | Addition of TP analysis of FR1 6.4D.2.4 EVM equalizer spectrum flatness for UL MIMO | 16.1.0 | +| 2019-09 | RAN#85 | R5-197326 | 0186 | 1 | F | Test Point analysis for Occupied bandwidth for 2UL CA in FR1 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197524 | 0187 | 1 | F | TP analysis 38.905 7.3A_ CA_ref_sensitivity | 16.1.0 | +| 2019-09 | RAN#85 | R5-197589 | 0168 | 1 | F | New addition of TP analysis for MOP & MOP Spherical Coverage for UL CA in SA FR2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197590 | 0169 | 1 | F | New addition of TP analysis for Carrier leakage for UL CA in SA FR2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197591 | 0170 | 1 | F | Adding test case 6.5B.2.1.3 to 38.905 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197592 | 0173 | 1 | F | Addition of TP analysis of FR2 6.6 Beam Correspondence | 16.1.0 | +| 2019-09 | RAN#85 | R5-197593 | 0174 | 1 | F | Test Point analysis update for FR2 Tx Spurious test case | 16.1.0 | +| 2019-09 | RAN#85 | R5-197594 | 0177 | 1 | F | Addition of TP analysis of FR1 Maximum input level for CA | 16.1.0 | +| 2019-09 | RAN#85 | R5-197595 | 0178 | 1 | F | Addition of TP analysis of FR1 6.4D.1 Frequency error for UL MIMO | 16.1.0 | +| 2019-09 | RAN#85 | R5-197596 | 0183 | 1 | F | Addition of TP analysis of FR2 6.2A.2 MPR for 2 UL CA | 16.1.0 | +| 2019-09 | RAN#85 | R5-197597 | 0191 | 1 | F | Addition of TP analysis for FR2 AMPR with NS_201 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197628 | 0192 | 2 | F | Updates of TP analysis for EN-DC MPR test case 6.2.B.2.1 | 16.1.0 | +| 2019-12 | RAN#86 | R5-198384 | 0203 | - | F | Addition of TP analysis of FR2 6.6 Beam Correspondence v1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198392 | 0205 | - | F | Addition of TP analysis of FR2 6.3D.3.4 SRS time mask for UL- | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | MIMO | | +| 2019-12 | RAN#86 | R5-198490 | 0206 | | F | TPanalysis of TC 7.5B.1 ACS for intra-band contiguous EN-DC 2CCs | 16.2.0 | +| 2019-12 | RAN#86 | R5-198523 | 0208 | | F | Test points analysis for NS_03 A-MPR FR1 test case | 16.2.0 | +| 2019-12 | RAN#86 | R5-198527 | 0210 | | F | Test points analysis for NS_43 and NS_43U A-MPR FR1 test case | 16.2.0 | +| 2019-12 | RAN#86 | R5-199326 | 0209 | 1 | F | Test points analysis for NS_05 and NS_05U A-MPR FR1 test case | 16.2.0 | +| 2019-12 | RAN#86 | R5-199327 | 0211 | 1 | F | Test points analysis for NS_100 A-MPR FR1 test case | 16.2.0 | +| 2019-12 | RAN#86 | R5-199328 | 0200 | 1 | F | Addition of test point analysis for SA FR1 TC 7.6A.3 Out-of-band blocking for CA | 16.2.0 | +| 2019-12 | RAN#86 | R5-199372 | 0197 | 1 | F | Update of test point analysis for SA FR2 TC 6.2.2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199410 | 0199 | 1 | F | Update of test point analysis for SA FR1 TC 6.2.2 to add almost contiguous allocation test points | 16.2.0 | +| 2019-12 | RAN#86 | R5-199487 | 0202 | 1 | F | Addition of test point analysis for SA FR1 TC 7.8A Wide band Intermodulation for CA | 16.2.0 | +| 2019-12 | RAN#86 | R5-199488 | 0201 | 1 | F | Addition of test point analysis for SA FR1 TC 7.6A.4 Narrow band blocking for CA | 16.2.0 | +| 2019-12 | RAN#86 | R5-199489 | 0207 | 1 | F | Addition of TP analysis for ACS for 3DL CA in FR1 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199501 | 0198 | 1 | F | Update of test point analysis for SA FR1 TC 6.5.2.4.2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-199507 | 0196 | 1 | F | TP analysis for test case 6.2B.2.2, UE Maximum Output Power reduction for Intra-Band Non-Contiguous EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199509 | 0194 | 1 | F | TP analysis for MOP for EN-DC | 16.2.0 | +| 2019-12 | RAN#86 | R5-199549 | 0204 | 1 | F | Addition to TP analysis of FR2 TC 6.3A.4.2.1 Absolute Power Control for CA | 16.2.0 | +| 2020-03 | RAN#87 | R5-200402 | 0215 | - | F | Updating TP of MOP for inter-band EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-200412 | 0221 | - | F | Editorial change of replacing zip file of FR2 6.3.1 by v2 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200419 | 0222 | - | F | Update of test point analysis for 7.6A.3 Out-of-band blocking for CA | 16.3.0 | +| 2020-03 | RAN#87 | R5-200459 | 0223 | - | F | Update of test point analysis for 7.6A.4 Narrow band blocking for CA | 16.3.0 | +| 2020-03 | RAN#87 | R5-200460 | 0224 | - | F | Update of test point analysis for 7.8A Wide band Intermodulation for CA | 16.3.0 | +| 2020-03 | RAN#87 | R5-200574 | 0226 | - | F | Addition of Test point selection for FR1 in SUL test cases | 16.3.0 | +| 2020-03 | RAN#87 | R5-200603 | 0227 | - | F | Test Point analysis for FR2 ref sens for CA | 16.3.0 | +| 2020-03 | RAN#87 | R5-200758 | 0229 | - | F | Correction of NS_05 test points analysis | 16.3.0 | +| 2020-03 | RAN#87 | R5-200762 | 0231 | - | F | Test points analysis for NS_38 A-MPR FR1 test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200764 | 0232 | - | F | Test points analysis for NS_39 A-MPR FR1 test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200766 | 0233 | - | F | Test points analysis for NS_43 A-MPR FR1 test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200768 | 0234 | - | F | Test points analysis for NS_43U A-MPR FR1 test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200799 | 0236 | - | F | Updated test point analysis for FR2 A-MPR test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-200815 | 0237 | - | F | Update of Test Point Analysis for UE Coexistence for DC_3A-n41A and DC_8A-n41A | 16.3.0 | +| 2020-03 | RAN#87 | R5-200990 | 0238 | 1 | F | Addition of TP analysis for FR1 In-band blocking for CA | 16.3.0 | +| 2020-03 | RAN#87 | R5-201182 | 0216 | 1 | F | Updating TP of configured output power for inter-band EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-201184 | 0218 | 1 | F | Updating TP of configured output power for intra-band contiguous EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-201186 | 0220 | 1 | F | Updating TP of configured output power for intra-band non-contiguous EN-DC | 16.3.0 | +| 2020-03 | RAN#87 | R5-201237 | 0230 | 1 | F | Test points analysis for NS_37 A-MPR FR1 test case | 16.3.0 | +| 2020-03 | RAN#87 | R5-201239 | 0235 | 1 | F | Test points analysis for NS_18 A-MPR FR1 test case | 16.3.0 | +| 2020-06 | RAN#88 | R5-201746 | 0242 | - | F | Addition of Number of test points for FR1 in SUL test cases | 16.4.0 | +| 2020-06 | RAN#88 | R5-201747 | 0243 | - | F | Addition of TP analysis for FR1 A-MPR for CA | 16.4.0 | +| 2020-06 | RAN#88 | R5-201765 | 0246 | - | F | Test points analysis for NS_27 A-MPR FR1 test case | 16.4.0 | +| 2020-06 | RAN#88 | R5-201767 | 0247 | - | F | Test points analysis for NS_40 A-MPR FR1 test case | 16.4.0 | +| 2020-06 | RAN#88 | R5-201773 | 0250 | - | F | Test points analysis for NS_47 A-MPR FR1 test case | 16.4.0 | +| 2020-06 | RAN#88 | R5-201871 | 0253 | - | F | Update of test points analysis in UE co-existence for inter-band EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-201872 | 0254 | - | F | Update of Test Point Analysis for UE Co-existence for DC_5A-n66A | 16.4.0 | +| 2020-06 | RAN#88 | R5-201873 | 0255 | - | F | Update of Test Point Analysis for UE Co-existence for DC_5A-n78A | 16.4.0 | +| 2020-06 | RAN#88 | R5-201874 | 0256 | - | F | Update of Test Point Analysis for UE Co-existence for DC_66A-n5A | 16.4.0 | +| 2020-06 | RAN#88 | R5-201875 | 0257 | - | F | Update of Test Point Analysis for UE Co-existence for DC_66A-n78A | 16.4.0 | +| 2020-06 | RAN#88 | R5-201929 | 0258 | - | F | Cleanup in 38.905 | 16.4.0 | +| 2020-06 | RAN#88 | R5-201931 | 0260 | - | F | Combined TP analysis for MPR, ACLR and SEM intra-band contiguous EN-DC test cases | 16.4.0 | +| 2020-06 | RAN#88 | R5-202029 | 0261 | - | F | Introduction of test point analysis for 2CCs EN-DC TCs in FR1 in 7.6B Blocking characteristics for DC and 7.7B Spurious response for DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202111 | 0262 | - | F | NS_24 TP analysis to TR 38.905 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202524 | 0267 | - | F | TP analysis 6.5.3.3 TX Additional SpurEmission NS_43 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202755 | 0248 | 1 | F | Test points analysis for NS_41 A-MPR FR1 test case | 16.4.0 | +| 2020-06 | RAN#88 | R5-202756 | 0249 | 1 | F | Test points analysis for NS_42 A-MPR FR1 test case | 16.4.0 | +| 2020-06 | RAN#88 | R5-202757 | 0264 | 1 | F | TP analysis 6.5.3.3 TX Additional SpurEmission NS_05 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202918 | 0239 | 1 | F | Test Point analysis for FR2 Frequency Error for CA | 16.4.0 | +| 2020-06 | RAN#88 | R5-202926 | 0266 | 1 | F | Addition of TPanalysis 6.5A.3.2.1 SECoex for CA_n1A-n78A | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | R5-202932 | 0244 | 1 | F | Addition of TP analysis for FR1 Maximum input level for 3DL CA | 16.4.0 | +| 2020-06 | RAN#88 | R5-202933 | 0245 | 1 | F | Addition of TP analysis for FR1 In-band blocking for 3DL CA | 16.4.0 | +| 2020-06 | RAN#88 | R5-202952 | 0251 | 1 | F | Updating TP of MOP for intra-band contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202953 | 0252 | 1 | F | Updating TP of MOP for intra-band non-contiguous EN-DC | 16.4.0 | +| 2020-06 | RAN#88 | R5-202954 | 0259 | 1 | F | Combined TP analysis for MPR, NR ACLR and SEM FR1 test cases | 16.4.0 | +| 2020-06 | RAN#88 | R5-202955 | 0263 | 1 | F | Updated TP analysis for 7.3A Reference sensitivity for CA | 16.4.0 | +| 2020-09 | RAN#89 | R5-203642 | 0269 | - | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_40A_n1A | 16.5.0 | +| 2020-09 | RAN#89 | R5-203643 | 0270 | - | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_40A_n78A | 16.5.0 | +| 2020-09 | RAN#89 | R5-203751 | 0275 | - | F | Editorial correction to references to EN-DC configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-204720 | 0299 | 1 | F | Add TP analysis table for TX spurious emission | 16.5.0 | +| 2020-09 | RAN#89 | R5-204726 | 0278 | 1 | F | Addition of test point analysis in Tx spurious emissions | 16.5.0 | +| 2020-09 | RAN#89 | R5-204727 | 0273 | 1 | F | Updating TP analysis for 6.2A.2-MPR for CA | 16.5.0 | +| 2020-09 | RAN#89 | R5-204728 | 0279 | 1 | F | Update of test point analysis of MOP for intra-band contiguous EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204789 | 0271 | 1 | F | Update of TP analysis for NS_43 and NS_01 in FR1 A-MPR for CA | 16.5.0 | +| 2020-09 | RAN#89 | R5-204790 | 0272 | 1 | F | Update of TP analysis for NS_43U and NS_01 in FR1 A-MPR for CA | 16.5.0 | +| 2020-09 | RAN#89 | R5-204791 | 0280 | 1 | F | Updating test point analysis for DC_1A-n78A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204792 | 0281 | 1 | F | Updating test point analysis for DC_2A-n66A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204793 | 0282 | 1 | F | Updating test point analysis for DC_2A-n78A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204794 | 0283 | 1 | F | Updating test point analysis for DC_3A-n7A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204795 | 0284 | 1 | F | Updating test point analysis for DC_3A-n78A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204796 | 0285 | 1 | F | Updating test point analysis for DC_7A-n78A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204797 | 0292 | 1 | F | Correction to test point analysis for spurious emissions UE co-existence for a few inter-band EN-DC configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-204817 | 0286 | 1 | F | Updating test point analysis for DC_3A-n1A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204818 | 0287 | 1 | F | Updating test point analysis for DC_7A-n1A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204819 | 0288 | 1 | F | Updating test point analysis for DC_7A-n66A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204820 | 0289 | 1 | F | Updating test point analysis for DC_8A-n1A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204821 | 0290 | 1 | F | Updating test point analysis for DC_12A-n78A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204822 | 0291 | 1 | F | Updating test point analysis for DC_28A-n3A for spurious emissions UE co-existence | 16.5.0 | +| 2020-09 | RAN#89 | R5-204829 | 0293 | 1 | F | Addition of test point analysis for AMPR NS_48 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204838 | 0274 | 1 | F | Updating TP analysis for 6.2A.4-Configured output power for CA | 16.5.0 | +| 2020-09 | RAN#89 | R5-204948 | 0295 | 1 | F | Addition of Test Point analysis for FR2 Transmit OFF Power for CA | 16.5.0 | +| 2020-09 | RAN#89 | R5-204949 | 0298 | 1 | F | TP analysis 6.5B.3 TX SpurEmission EN-DC V2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204950 | 0300 | 1 | F | Updated TP analysis for 7.3B Reference sensitivity for EN-DC in FR1 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204959 | 0301 | 1 | F | Update of TP analysis 6.5A.3.2.1 SECoex for CA n1A-n78A | 16.5.0 | +| 2020-09 | RAN#89 | R5-204963 | 0276 | 1 | F | Update test point analysis for A-MPR NS_18 with CBW being 30MHz | 16.5.0 | +| 2020-09 | RAN#89 | R5-204964 | 0294 | 1 | F | Addition of test point analysis for additional spurious emission with NS_17 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204982 | 0268 | 2 | F | Updated TP analysis for 7.3A | 16.5.0 | +| 2020-12 | RAN#90 | R5-205264 | 0303 | - | F | Addition of Test Point analysis for 6.3A.4.1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205265 | 0304 | - | F | Addition of Test Point analysis for 6.3A.4.2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205267 | 0305 | - | F | Addition of Test Point analysis for 6.3A.4.3 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205558 | 0309 | - | F | Adding test point analysis for A-MPR test of band n30 with NS_21 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205619 | 0312 | - | F | Addition of TP Analysis for TC 6.5A.2.1 Spectrum Emission Mask for CA in FR2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205630 | 0313 | - | F | Addition of TP Analysis for TC 6.5A.2.2 Adjacent channel leakage ratio for CA in FR2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-205780 | 0318 | - | F | Addition of test point analysis for DC_2A_n5A in Tx spurious emissions cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-205781 | 0319 | - | F | Addition of test point analysis for DC_8A_n78A in Tx spurious emissions cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-205782 | 0320 | - | F | Addition of test point analysis for DC_12A_n66A in Tx spurious emissions cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-205783 | 0321 | - | F | Addition of test point analysis for DC_30A_n5A in Tx spurious emissions cases | 16.6.0 | +| 2020-12 | RAN#90 | R5-205785 | 0322 | - | F | Addition of test point analysis for DC_13A_n66A in Tx spurious | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------|--------| +| | | | | | | emissions cases | | +| 2020-12 | RAN#90 | R5-205885 | 0329 | - | F | Addition of test point analysis for A-MPR NS_46 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206037 | 0333 | - | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_20A_n3A | 16.6.0 | +| 2020-12 | RAN#90 | R5-206729 | 0332 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_1A_n3A | 16.6.0 | +| 2020-12 | RAN#90 | R5-206752 | 0302 | 1 | F | Addition of test point analysis for A-MPR NS_45 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206769 | 0325 | 1 | F | Update of test point analysis for Tx spurious emissions in NR FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206853 | 0328 | 1 | F | Update to test point analysis for A-MPR NS_18 with 30MHz | 16.6.0 | +| 2020-12 | RAN#90 | R5-206854 | 0314 | 1 | F | Updating TP analysis for OBW for CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206855 | 0316 | 1 | F | Updating TP analysis for Maximum input level for 3DL CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206856 | 0317 | 1 | F | Updating TP analysis for Inband blocking for 3DL CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206857 | 0323 | 1 | F | Update of test point analysis for MPR, SEM and ACLR in NR FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206858 | 0324 | 1 | F | Update of test point analysis for MOP in FR1 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206873 | 0310 | 1 | F | Restructuring of TR 38.905. | 16.6.0 | +| 2020-12 | RAN#90 | R5-206874 | 0311 | 1 | F | Combined TP analysis for FR2 test cases MPR, ACLR and SEM | 16.6.0 | +| 2020-12 | RAN#90 | R5-206875 | 0331 | 1 | F | Update of TPA for in-band emission and carrier leakage TCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206876 | 0336 | 1 | F | Update of test point analysis for occupied bandwidth in FR2 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206893 | 0315 | 1 | F | Updating TP analysis for REFSSENS for CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206917 | 0330 | 1 | F | Updated TP analysis for 7.3B Reference sensitivity for EN-DC in FR1 | 16.6.0 | +| 2021-03 | RAN#91 | R5-210383 | 0343 | - | F | Correct a typo of 6.3A.4.2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210512 | 0344 | - | F | Introduction of test point analysis for SA FR2 7.4A Maximum input level for CA | 16.7.0 | +| 2021-03 | RAN#91 | R5-210740 | 0347 | - | F | Updating TP analysis of FR1 A-MPR for NS_48 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210742 | 0348 | - | F | Adding TP analysis of FR1 A-MPR for NS_49 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210743 | 0349 | - | F | Resubmitting TP analysis of FR1 A-MPR for NS_44 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210791 | 0353 | - | F | Adding TP selection for 6.4C.2 Transmit modulation quality for SUL | 16.7.0 | +| 2021-03 | RAN#91 | R5-210900 | 0354 | - | F | Updating TP analysis for Spurious Emissions for CA in FR1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210905 | 0356 | - | F | Updating TP analysis for FR1 REFSSENS for SUL testing | 16.7.0 | +| 2021-03 | RAN#91 | R5-210963 | 0362 | - | F | Spur emission TP analysis R16 DC_5A_n2A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211018 | 0368 | - | F | TP analysis for test case 6.5D.2_1.4.2, UTRA ACLR for UL MIMO (Rel-16 onward) | 16.7.0 | +| 2021-03 | RAN#91 | R5-211134 | 0380 | - | F | TP analysis for ULFPTx in MPR test case | 16.7.0 | +| 2021-03 | RAN#91 | R5-211230 | 0389 | - | F | NS_12, NS_13, NS_14, NS_15 TP analysis to 38.905 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211733 | 0340 | 1 | F | Updated TP analysis for 7.3B Reference sensitivity for EN-DC in FR1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211734 | 0341 | 1 | F | TP analysis for 38.521-3 test case 6.5B.2.2.1 SEM Intra-band non-contiguous | 16.7.0 | +| 2021-03 | RAN#91 | R5-211735 | 0342 | 1 | F | TP analysis for 38.521-3 test case 6.5B.2.2.3 ACLR Intra-band non-contiguous | 16.7.0 | +| 2021-03 | RAN#91 | R5-211736 | 0345 | 1 | F | Update of test point analysis for FR2 UL CA frequency error test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211737 | 0369 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_8A_n77A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211738 | 0370 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_11A_n77A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211739 | 0371 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_11A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211740 | 0372 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_11A_n79A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211741 | 0373 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_25A_n41A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211742 | 0374 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_26A_n41A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211743 | 0375 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_26A_n77A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211744 | 0376 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_26A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211745 | 0377 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_26A_n79A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211746 | 0378 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_41A_n77A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211747 | 0379 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_41A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211748 | 0388 | 1 | F | Test Point analysis update for FR2 Tx additional spurious emission test case | 16.7.0 | +| 2021-03 | RAN#91 | R5-211774 | 0337 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_7A_n3A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211775 | 0338 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_8A_n3A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211776 | 0339 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_20A_n1A | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91 | R5-211777 | 0361 | 1 | F | Spur emission TP analysis R16 DC_2A_n41A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211778 | 0363 | 1 | F | Spur emission TP analysis R16 DC_13A_n2A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211779 | 0364 | 1 | F | Spur emission TP analysis R16 DC_48A_n5A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211780 | 0365 | 1 | F | Spur emission TP analysis R16 DC_48A_n66A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211781 | 0366 | 1 | F | Spur emission TP analysis R16 DC_66A_n41A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211809 | 0350 | 1 | F | Adding TP analysis for Rel-16 DMRS in A-MPR test case | 16.7.0 | +| 2021-03 | RAN#91 | R5-211810 | 0351 | 1 | F | Update of TP analysis for EVM equalizer spectrum flatness for half Pi BPSK | 16.7.0 | +| 2021-03 | RAN#91 | R5-211811 | 0352 | 1 | F | Update of TP analysis for FR1 SUL test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211893 | 0346 | 1 | F | Update of test point analysis for FR2 MPR, SEM and ACLR test cases | 16.7.0 | +| 2021-03 | RAN#91 | R5-211894 | 0359 | 1 | F | Addition of reference sensitivity test point analyses for FR1 NR CA and EN-DC | 16.7.0 | +| 2021-03 | RAN#91 | R5-211895 | 0360 | 1 | F | Moving of principles for reference sensitivity test point selection from attachments to annexes | 16.7.0 | +| 2021-03 | RAN#91 | R5-211897 | 0382 | 1 | F | TP analysis for DC_8A_n77A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211898 | 0383 | 1 | F | TP analysis for DC_11A_n79A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211899 | 0384 | 1 | F | TP analysis for DC_26A_n41A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211900 | 0385 | 1 | F | TP analysis for DC_26A_n77A and DC_26A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211901 | 0386 | 1 | F | TP analysis for DC_26A_n79A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211902 | 0387 | 1 | F | TP analysis for DC_41A_n77A and DC_41A_n78A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211906 | 0390 | 1 | F | Reference sensitivity TP analysis for DC_1A-28A_n3A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211907 | 0391 | 1 | F | Reference sensitivity analysis for DC_3A-7A_n1A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211908 | 0392 | 1 | F | Reference sensitivity TP analysis for DC_7A-20A_n1A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211909 | 0393 | 1 | F | Reference sensitivity TP analysis for DC_7A-28A_n3A | 16.7.0 | +| 2021-03 | RAN#91 | R5-211914 | 0358 | 1 | F | Adding TP analysis for NR test case-Time mask for UL carrier switching | 16.7.0 | +| 2021-03 | RAN#91 | - | - | - | - | Administrative release upgrade to match the release of TS 38.508-1, TS 38.508-2 and TS 38.521-1 which were upgraded at RAN#91 to Rel-17 due to Rel-17 relevant CRs | 17.0.0 | +| 2021-06 | RAN#92 | R5-212519 | 0397 | - | F | Update of test point analysis for FR2 Occupied Bandwidth for UL MIMO test case | 17.1.0 | +| 2021-06 | RAN#92 | R5-212524 | 0400 | - | F | Spurious emission TP analysis for Rel-15 EN-DC configuration DC_66A_n71A | 17.1.0 | +| 2021-06 | RAN#92 | R5-212929 | 0405 | - | F | Addition of TP analysis of V2X MPR, SEM and ACLR non-concurrent | 17.1.0 | +| 2021-06 | RAN#92 | R5-212930 | 0406 | - | F | Addition of TP analysis of 6.3E.1 V2X minimum output power non-concurrent | 17.1.0 | +| 2021-06 | RAN#92 | R5-212982 | 0407 | - | F | Addition of TP analysis for CA_n28A-n41A in Tx Spurious Emission cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-212990 | 0409 | - | F | Updating TP analysis for UTRA ACLR MIMO testing for band n1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213024 | 0411 | - | F | Correction to test points selection for intra-band EN-DC spurious emissions testing | 17.1.0 | +| 2021-06 | RAN#92 | R5-213053 | 0421 | - | F | TP analysis for 6.2.4 updated for eMIMO | 17.1.0 | +| 2021-06 | RAN#92 | R5-213114 | 0428 | - | F | Correction of test coverage clause numbering | 17.1.0 | +| 2021-06 | RAN#92 | R5-213946 | 0396 | 1 | F | Introduction of test point analysis for FR2 CA Error Vector Magnitude test case | 17.1.0 | +| 2021-06 | RAN#92 | R5-213947 | 0401 | 1 | F | Spurious emission TP analysis for Rel-15 EN-DC configuration DC_2A_n71A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213948 | 0403 | 1 | F | Addition of test points analysis for NS_06 FR1 test cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-213949 | 0413 | 1 | F | Correction to test points selection for inter-band EN-DC co-existence spurious emissions testing | 17.1.0 | +| 2021-06 | RAN#92 | R5-213950 | 0414 | 1 | F | Update of TP analysis for general spurious emissions for DC_3A_n7A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213951 | 0415 | 1 | F | Update of TP analysis for general spurious emissions for DC_3A_n78A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213952 | 0416 | 1 | F | Update of TP analysis for general spurious emissions for DC_8A_n77A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213953 | 0417 | 1 | F | Update of TP analysis for general spurious emissions for DC_12A_n66A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213954 | 0418 | 1 | F | Update of TP analysis for general spurious emissions for DC_26A_n41A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213955 | 0419 | 1 | F | Update of TP analysis for general spurious emissions for DC_26A_n79A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213956 | 0420 | 1 | F | Update of TP analysis for general spurious emissions for DC_30A_n5A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213957 | 0422 | 1 | F | Update of test point analysis for FR2 MPR SEM and ACLR UL-MIMO test cases | 17.1.0 | +| 2021-06 | RAN#92 | R5-213958 | 0423 | 1 | F | TP analysis for DC_11A_n77A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213959 | 0424 | 1 | F | TP analysis for DC_11A_n78A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213960 | 0425 | 1 | F | TP analysis for DC_25A_n41A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213961 | 0426 | 1 | F | TP analysis for DC_42A_n77A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213962 | 0427 | 1 | F | General TP analysis update for NR CA refsens | 17.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------|--------| +| 2021-06 | RAN#92 | R5-214070 | 0402 | 1 | F | Correction of power control in 38.905 | 17.1.0 | +| 2021-06 | RAN#92 | R5-214071 | 0429 | 1 | F | Test Point analysis for FR2 Tx spurious emission CA test case | 17.1.0 | +| 2021-06 | RAN#92 | R5-214073 | 0398 | 1 | F | Spurious emission TP analysis for Rel-16 EN-DC configuration DC_14A_n2A | 17.1.0 | +| 2021-06 | RAN#92 | R5-214074 | 0399 | 1 | F | Spurious emission TP analysis for Rel-16 EN-DC configuration DC_14A_n66A | 17.1.0 | +| 2021-06 | RAN#92 | R5-214093 | 0412 | 1 | F | Correction to test points selection for inter-band EN-DC general spurious emissions testing | 17.1.0 | +| 2021-09 | RAN#93 | R5-214245 | 0431 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_1A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214246 | 0432 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_1A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214247 | 0433 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_3A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214248 | 0434 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_3A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214249 | 0435 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_7A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214250 | 0436 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_19A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214251 | 0437 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_19A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214252 | 0438 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_19A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214253 | 0439 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_20A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214255 | 0441 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_21A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214256 | 0442 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_21A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214257 | 0443 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_21A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214258 | 0444 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_28A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214260 | 0446 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_28A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214261 | 0447 | - | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_42A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214262 | 0448 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_1A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214263 | 0449 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_3A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214264 | 0450 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_5A_n66A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214265 | 0451 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_5A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214266 | 0452 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_7A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214267 | 0453 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_11A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214268 | 0454 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_11A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214269 | 0455 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_11A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214271 | 0457 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_26A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214272 | 0458 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_26A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214273 | 0459 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_39A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214274 | 0460 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_41A_n77A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214275 | 0461 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_41A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214276 | 0462 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_41A_n79A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214277 | 0463 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_66A_n5A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214278 | 0464 | - | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_66A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214315 | 0465 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_40A_n1A | 17.2.0 | +| 2021-09 | RAN#93 | R5-214316 | 0466 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_40A_n78A | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-214385 | 0467 | - | F | Introduction of NR FR2 Test Points For Aggregate power tolerance for CA | 17.2.0 | +| 2021-09 | RAN#93 | R5-214721 | 0468 | - | F | Adding TP analysis for test case 6.5D.1_1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-214907 | 0469 | - | F | Introduction of test point analysis for FR2 Time alignment error for UL MIMO test case | 17.2.0 | +| 2021-09 | RAN#93 | R5-215076 | 0473 | - | F | Addition of TP analysis of V2X MPR, SEM and ACLR non-concurrent with SL-MIMO | 17.2.0 | +| 2021-09 | RAN#93 | R5-215077 | 0474 | - | F | Addition of TP analysis of V2X minimum output power for non-concurrent with SL-MIMO | 17.2.0 | +| 2021-09 | RAN#93 | R5-215164 | 0475 | - | F | Addition of test points analysis for NS_06 power class 1 test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215219 | 0479 | - | F | Update of TP analysis for general spurious emissions for DC_12A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215220 | 0480 | - | F | Update of TP analysis for general spurious emissions for DC_28A_n3A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215229 | 0483 | - | F | Correction to TP analysis for in-band emission for intra-band contiguous EN-DC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215236 | 0484 | - | F | Addition of reference sensitivity TP analysis for DC_1A_n28A-n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215237 | 0485 | - | F | Addition of reference sensitivity TP analysis for DC_1A-3A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215238 | 0486 | - | F | Addition of reference sensitivity TP analysis for DC_1A-7A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215239 | 0487 | - | F | Addition of reference sensitivity TP analysis for DC_3A-7A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215293 | 0492 | - | F | Updating Test point analysis for DC_3A-20A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215302 | 0495 | - | F | Updating TP analysis for Relative power tolerance for CA | 17.2.0 | +| 2021-09 | RAN#93 | R5-215304 | 0496 | - | F | Updating TP analysis for Aggregate power tolerance for CA | 17.2.0 | +| 2021-09 | RAN#93 | R5-215306 | 0497 | - | F | Updating TP analysis for Occupied bandwidth for CA | 17.2.0 | +| 2021-09 | RAN#93 | R5-215327 | 0498 | - | F | TP analysis for FR2 General ON OFF time mask | 17.2.0 | +| 2021-09 | RAN#93 | R5-215336 | 0499 | - | F | Correction to TP analysis for FR1 A-SPR with NS_17 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215543 | 0502 | - | F | Update TP analysis for Rel_16 DC_14A_n2A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215545 | 0503 | - | F | Update TP analysis for Rel_16 DC_13A_n2A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215547 | 0504 | - | F | Update TP analysis for Rel_15 DC_2A_n71A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215550 | 0505 | - | F | Update TP analysis for Rel_15 DC_66A_n71A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215919 | 0440 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_20A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215920 | 0456 | 1 | F | Update of spurious emission TP analysis for Rel-15 EN-DC configuration DC_25A_n41A | 17.2.0 | +| 2021-09 | RAN#93 | R5-215921 | 0471 | 1 | F | Addition of TP analysis for spurious emissions for DC_28A_n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216014 | 0430 | 1 | F | Introduction of spurious emission TP analysis for Rel-15 EN-DC configuration DC_1A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216017 | 0477 | 1 | F | Update of TP analysis for general spurious emissions for DC_3A_n41A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216018 | 0481 | 1 | F | Update of TP analysis for general spurious emissions for DC_39A_n41A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216019 | 0482 | 1 | F | Update of TP analysis for general spurious emissions for DC_40A_n41A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216020 | 0507 | 1 | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_8A_n41A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216056 | 0472 | 1 | F | Addition of TP for REFSENS for inter-band EN-DC 2CC and 3CC combos | 17.2.0 | +| 2021-09 | RAN#93 | R5-216057 | 0488 | 1 | F | Correction to TP analysis for reference sensitivity per EN-DC configuration | 17.2.0 | +| 2021-09 | RAN#93 | R5-216058 | 0489 | 1 | F | Correction to Annex D Principles for test point selection for EN-DC reference sensitivity test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-216059 | 0490 | 1 | F | Updating Test point analysis for DC_3A_n28A-n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216060 | 0491 | 1 | F | Updating Test point analysis for DC_7A_n28A-n78A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216061 | 0493 | 1 | F | Updating Test point analysis for DC_7A-20A_n28A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216062 | 0501 | 1 | F | Defining TP analysis for MPR, SEM and ACLR for FR2 UL MIMO | 17.2.0 | +| 2021-09 | RAN#93 | R5-216064 | 0500 | 1 | F | Update TP analysis for Rel_16 DC_14A_n66A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216068 | 0494 | 1 | F | Updating TP analysis for Absolute power tolerance for CA | 17.2.0 | +| 2021-09 | RAN#93 | R5-216109 | 0506 | 1 | F | TP analysis for ref sensitivity DC_48A_n66A | 17.2.0 | +| 2021-09 | RAN#93 | R5-216142 | 0476 | 1 | F | Correction to IE and UE capability for low PAPR DMRS in test point analysis | 17.2.0 | +| 2021-12 | RAN#94 | R5-216513 | 0508 | - | F | TP analysis update for FR1 6.2.3 AMPR NS_27 | 17.3.0 | +| 2021-12 | RAN#94 | R5-216516 | 0509 | - | F | TP analysis update for IBNC EN-DC 6.2B.2.2_MPR 6.5B.2.2.1_SEM 6.5B.2.2.3_ACLR | 17.3.0 | +| 2021-12 | RAN#94 | R5-216547 | 0511 | - | F | TP analysis for FR2 DL 256QAM to Maximum input level | 17.3.0 | +| 2021-12 | RAN#94 | R5-216548 | 0512 | - | F | TP analysis for FR2 DL 256QAM to Maximum input level for CA | 17.3.0 | +| 2021-12 | RAN#94 | R5-217164 | 0515 | - | F | TP analysis for ref sensitivity for DC_66A_n2A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217165 | 0516 | - | F | TP analysis for ref sensitivity for DC_66A_n78A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217166 | 0517 | - | F | TP analysis for ref sensitivity for DC_66A_n71A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217190 | 0520 | - | F | Test Point analysis for FR2 Tx spur emission coex CA test case | 17.3.0 | +| 2021-12 | RAN#94 | R5-217301 | 0521 | - | F | Addition of reference sensitivity TP analysis for DC_1A-20A_n28A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217302 | 0522 | - | F | Addition of reference sensitivity TP analysis for DC_3A_n78C | 17.3.0 | +| 2021-12 | RAN#94 | R5-217303 | 0523 | - | F | Addition of reference sensitivity TP analysis for DC_20A_n28A-n78A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217306 | 0524 | - | F | Editorial correction to Annex 2.10.3 test point selection EN-DC | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| | | | | | | reference sensitivity | | +| 2021-12 | RAN#94 | R5-217307 | 0525 | - | F | Update of TP analysis for general spurious emissions for DC_8A_n78A | 17.3.0 | +| 2021-12 | RAN#94 | R5-217561 | 0526 | - | F | Update of test point analysis for carrier leakage in FR2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217604 | 0527 | - | F | Addition of TP analysis of V2X MOP 6.2E.1.x | 17.3.0 | +| 2021-12 | RAN#94 | R5-218200 | 0532 | - | F | TP analysis for ref sensitivity for DC_41A_n77A and DC_41A_n78A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218276 | 0513 | 1 | F | Update TP analysis for Rel 16 DC 14A n2A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218277 | 0514 | 1 | F | Update TP analysis for Rel 16 DC 14A n66A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218306 | 0528 | 1 | F | Addition of TP analysis of V2X MPR 6.2E.2.x | 17.3.0 | +| 2021-12 | RAN#94 | R5-218364 | 0510 | 1 | F | Addition of TP analysis of A-MPR and ASE for NS 56 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218409 | 0531 | 1 | F | Update of test point analysis for relative power tolerance in FR2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218445 | 0518 | 1 | F | TP analysis for ref sensitivity for DC_2A_n71A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218446 | 0519 | 1 | F | TP analysis for ref sensitivity for DC_5A_n66A | 17.3.0 | +| 2021-12 | RAN#94 | R5-218447 | 0530 | 1 | F | TP analysis update for A-MPR and A-Spurious test cases | 17.3.0 | +| 2021-12 | RAN#94 | R5-218487 | 0529 | 1 | F | Update of TR 38.905 with EN DC A MPR test point analyses, NS_04 | 17.3.0 | +| 2022-03 | RAN#95 | R5-220321 | 0537 | - | F | Adding Reference sensitivity Test point analysis for Rel-16 inter-band EN-DC FR1 two band combinations | 17.4.0 | +| 2022-03 | RAN#95 | R5-220363 | 0541 | - | F | Update TP analysis for Rel-17 DC_2A_n77A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220364 | 0542 | - | F | Update TP analysis for Rel-17 DC_5A_n77A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220365 | 0543 | - | F | Update TP analysis for Rel-17 DC_13A_n77A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220366 | 0544 | - | F | Update TP analysis for Rel-17 DC_66A_n77A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220377 | 0545 | - | F | Introduction of reference sensitivity test point analysis for DC_1A-n7A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220378 | 0546 | - | F | Introduction of reference sensitivity test point analysis for DC_28A_n7A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220379 | 0547 | - | F | Introduction of reference sensitivity test point analysis for DC_1A_n5A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220381 | 0548 | - | F | Introduction of reference sensitivity test point analysis for DC_3A_n5A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220383 | 0549 | - | F | Introduction of reference sensitivity test point analysis for DC_7A-n5A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220385 | 0550 | - | F | Introduction of reference sensitivity test point analysis for DC_7A_n28A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220388 | 0552 | - | F | Introduction of reference sensitivity test point analysis for DC_7A_n5A-n78A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220389 | 0553 | - | F | Introduction of reference sensitivity test point analysis for DC_28A_n7A-n78A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221748 | 0555 | 1 | F | Addition of Test Point analysis for FR1 Spurious emission for UE co-existence for DC_19_n1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221749 | 0556 | 1 | F | Addition of Test Point analysis for FR1 Spurious emission for UE co-existence for DC_21_n1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220794 | 0558 | - | F | TP analysis for 6.2D.1 for ULFPTx | 17.4.0 | +| 2022-03 | RAN#95 | R5-220982 | 0561 | - | F | Update of test point analysis for Adjacent Channel Selectivity for EN-DC within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221115 | 0562 | - | F | Updating TP analysis for FR1 AMPR for CA_n41A-n79A testing | 17.4.0 | +| 2022-03 | RAN#95 | R5-221123 | 0563 | - | F | Updating TP analysis for FR1 MPR for intra-band CA test case | 17.4.0 | +| 2022-03 | RAN#95 | R5-221125 | 0564 | - | F | Updating TP analysis for FR1 Absolute power tolerance CA test case | 17.4.0 | +| 2022-03 | RAN#95 | R5-221127 | 0565 | - | F | Updating TP analysis for FR1 ACLR for intra-band CA test case | 17.4.0 | +| 2022-03 | RAN#95 | R5-221129 | 0566 | - | F | Updating TP analysis for FR1 SEM for intra-band CA test case | 17.4.0 | +| 2022-03 | RAN#95 | R5-221313 | 0573 | - | F | TP analysis for ref sensitivity for DC_2A_n78A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221320 | 0575 | - | F | TP analysis for ref sensitivity for 4 Rel-17 ENDC combos | 17.4.0 | +| 2022-03 | RAN#95 | R5-221327 | 0577 | - | F | TP analysis for ref sensitivity for DC_2A_n66A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221602 | 0580 | - | F | Correction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_8A_n3A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221603 | 0581 | - | F | Correction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_20A_n3A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221631 | 0583 | - | F | Update of spurious emission TP analysis for DC_3A_n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221632 | 0584 | - | F | Update of spurious emission TP analysis for DC_8A_n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221633 | 0585 | - | F | Update of spurious emission TP analysis for DC_25A_n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221634 | 0582 | - | F | Update of spurious emission TP analysis for DC_26A_n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221635 | 0586 | - | F | Update of spurious emission TP analysis for DC_39A_n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221636 | 0587 | - | F | Update of spurious emission TP analysis for DC_40A_n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221750 | 0574 | 1 | F | Update TP analysis for EVM | 17.4.0 | +| 2022-03 | RAN#95 | R5-221751 | 0576 | 1 | F | Test Point analysis for FR2 Tx spur emission UL MIMO tests | 17.4.0 | +| 2022-03 | RAN#95 | R5-221752 | 0578 | 1 | F | Addition of reference sensitivity checklist for CA reference sensitivity test point analysis | 17.4.0 | +| 2022-03 | RAN#95 | R5-221753 | 0579 | 1 | F | Modification of test point analysis clause for FR1 NR CA | 17.4.0 | +| 2022-03 | RAN#95 | R5-221774 | 0533 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_8A_n20A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221775 | 0534 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_20A_n7A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221776 | 0535 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------|--------| +| | | | | | | configuration DC_28A n5A | | +| 2022-03 | RAN#95 | R5-221777 | 0536 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_40A n79A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221778 | 0551 | 1 | F | Introduction of reference sensitivity test point analysis for DC_7A n78A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221779 | 0567 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_1A n5A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221780 | 0568 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_1A n7A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221781 | 0569 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_3A n5A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221782 | 0570 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_7A n5A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221783 | 0571 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_28A n7A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221829 | 0557 | 1 | F | TP analysis for 6.2E.2.2 MPR for concurrent operation | 17.4.0 | +| 2022-03 | RAN#95 | R5-221841 | 0559 | 1 | F | TP analysis for 6.2D.2 for ULFPTx | 17.4.0 | +| 2022-06 | RAN#96 | R5-222187 | 0588 | - | F | Correction of Number of test points for V2X SEM and V2X ACLR in 38.521-1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222188 | 0589 | - | F | Correction of Justification in attachment for UL MIMO MPR and ACLR in 38.521-1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222189 | 0590 | - | F | Correction of test points analysis of 2UL CA ACLR test case in 38.521-1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222420 | 0602 | - | F | Update of R17 Reference Sensitivity test point analysis for FR1 NR CA | 17.5.0 | +| 2022-06 | RAN#96 | R5-222429 | 0603 | - | F | Test point analysis update for FR1 test case 6.3A.4.1.1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222574 | 0606 | - | F | Addition of test analysis for several CA combinations | 17.5.0 | +| 2022-06 | RAN#96 | R5-222682 | 0613 | - | F | Update of test points analysis for CA n1A-n3A refsens test case | 17.5.0 | +| 2022-06 | RAN#96 | R5-222733 | 0614 | - | F | Update for 38.521-1 TPanalysis_7.3 RefSense | 17.5.0 | +| 2022-06 | RAN#96 | R5-222734 | 0615 | - | F | Update TpAnalysisSpur_DC_14A_n2A | 17.5.0 | +| 2022-06 | RAN#96 | R5-222735 | 0616 | - | F | Update TpAnalysisSpur_DC_14A_n66A | 17.5.0 | +| 2022-06 | RAN#96 | R5-222831 | 0617 | - | F | Addition of test point analysis for 6.2B.1.3_1 Maximum Output Power | 17.5.0 | +| 2022-06 | RAN#96 | R5-222886 | 0619 | - | F | Update to TP analysis of A-MPR to add ULFPTx | 17.5.0 | +| 2022-06 | RAN#96 | R5-222903 | 0620 | - | F | Addition of TP analysis for FR1 RedCap requirements | 17.5.0 | +| 2022-06 | RAN#96 | R5-222915 | 0621 | - | F | Removing test case 6.5D.1_1 Occupied bandwidth for UL MIMO (Rel-16 onward) from 38.905 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222927 | 0622 | - | F | Addition of test point analysis for new test case 6.2G.1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222928 | 0623 | - | F | Addition of test point analysis for new test cases 6.2G.2 and 6.5G.2.3.1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-222929 | 0624 | - | F | Addition of test point analysis for new test case 6.2G.3 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223017 | 0625 | - | F | Update of test point analysis for MPR, SEM and NR ACLR for UL MIMO | 17.5.0 | +| 2022-06 | RAN#96 | R5-223050 | 0626 | - | F | Update of test points analysis per CA configuration Table | 17.5.0 | +| 2022-06 | RAN#96 | R5-223682 | 0591 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_1A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223683 | 0592 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_7A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223684 | 0593 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_8A_n28A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223685 | 0594 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223686 | 0595 | 1 | F | Introduction of reference sensitivity test point analysis for DC_1A-20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223687 | 0596 | 1 | F | Introduction of reference sensitivity test point analysis for DC_1A-28A_n5A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223688 | 0597 | 1 | F | Introduction of reference sensitivity test point analysis for DC_3A-7A_n5A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223689 | 0598 | 1 | F | Introduction of reference sensitivity test point analysis for DC_3A-8A_n28A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223690 | 0599 | 1 | F | Introduction of reference sensitivity test point analysis for DC_7A-8A_n3A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223691 | 0600 | 1 | F | Introduction of reference sensitivity test point analysis for DC_7A-20A_n8A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223692 | 0601 | 1 | F | Introduction of reference sensitivity test point analysis for DC_7A-28A_n5A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223696 | 0628 | 1 | F | Update_TP_analysis for AMPR NS_27 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223732 | 0627 | 1 | F | Updating A-MPR and A-SE TP analysis for NS_48 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223745 | 0607 | 1 | F | Tx spurious emission TP analysis for Rel-17 CA_n24-n41 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223746 | 0608 | 1 | F | Tx spurious emission TP analysis for Rel-17 CA_n24-n48 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223747 | 0609 | 1 | F | Tx spurious emission TP analysis for Rel-17 CA_n24-n77 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223771 | 0618 | 1 | F | Addition of test point analysis for 6.2B.4.1.3_1 Configured Output Power | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-06 | RAN#96 | R5-223867 | 0604 | 1 | F | Updating TP analysis for MPR, SEM and ACLR for FR2 | 17.5.0 | +| 2022-09 | RAN#97 | R5-224158 | 0631 | - | F | Introduction of reference sensitivity test point analysis for DC_3A-7A-20A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224207 | 0633 | - | F | Adding test point analysis for A_MPR NS_27 with 30 MHz channel bandwidth | 17.6.0 | +| 2022-09 | RAN#97 | R5-224254 | 0634 | - | F | Correction of test points analysis of some Rx test cases in 38.521-1 for the addition of test points for asymmetric channel bandwidths and UL-MIMO | 17.6.0 | +| 2022-09 | RAN#97 | R5-224792 | 0640 | - | F | Addition of test point analysis for TxD test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224872 | 0646 | - | F | A-MPR TP analysis for Rel-17 CA_n24-n48 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224873 | 0647 | - | F | A-MPR TP analysis for Rel-17 CA_n24-n77 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224886 | 0649 | - | F | TP analysis for additional spurious emission for NS_14 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224901 | 0657 | - | F | General rule for TP selection for NR_U test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-224938 | 0658 | - | F | Editorial corrections to the timeline for introduction of test points | 17.6.0 | +| 2022-09 | RAN#97 | R5-224940 | 0659 | - | F | Introduction of reference sensitivity test point analysis for DC_2A-66A_n41A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224944 | 0660 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_2A_n41A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224945 | 0661 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_7A_n3A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224947 | 0662 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_8A_n41A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224948 | 0663 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_13A_n2A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224949 | 0664 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_20A_n1A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224951 | 0665 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_48A_n5A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224953 | 0666 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_48A_n66A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224955 | 0667 | - | F | Update of spurious emission TP analysis for Rel-16 EN-DC configuration DC_66A_n41A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224959 | 0668 | - | F | Editorial corrections to spurious emission test cases for DC_8A_n3A, DC_8A_n20A and DC_20A_n3A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224965 | 0669 | - | F | Incorrect TP analysis revision for test case 6.2D.2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225065 | 0670 | - | F | Updating test point selection criteria for FR1 SUL test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225074 | 0671 | - | F | Adding TP analysis for new FR1 test case 6.3C.3.2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225076 | 0672 | - | F | Updating TP analysis for FR1 test case 6.3A.3.1_1 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225108 | 0673 | - | F | Editorial correction for DC_1A_n5A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225711 | 0630 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 EN-DC configuration DC_3A_n8A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225712 | 0635 | 1 | F | Update TP analysis for Rel-16 CA_n2A_n77A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225713 | 0636 | 1 | F | Update TP analysis for Rel-16 CA_n5A_n77A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225714 | 0637 | 1 | F | Update TP analysis for Rel-16 CA_n66A_n77A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225715 | 0638 | 1 | F | TP analysis for ref sensitivity for Rel-16 NR CA combos | 17.6.0 | +| 2022-09 | RAN#97 | R5-225716 | 0650 | 1 | F | Update Spurious emission TP R16 DC_5A_n2A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225737 | 0643 | 1 | F | Tx Spurious emissions test point analysis for many UL CA combos | 17.6.0 | +| 2022-09 | RAN#97 | R5-225738 | 0644 | 1 | F | Test point analysis for reference sensitivity for many 4CA combos | 17.6.0 | +| 2022-09 | RAN#97 | R5-225739 | 0645 | 1 | F | A-MPR TP analysis for Rel-17 CA_n24-n41 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225745 | 0629 | 1 | F | Test point analysis for test 6.2.4_1 Configured transmitted power with Power Boost | 17.6.0 | +| 2022-09 | RAN#97 | R5-225746 | 0641 | 1 | F | Update TP analysis for AMPR NS_05 and NS_05U | 17.6.0 | +| 2022-09 | RAN#97 | R5-225749 | 0632 | 1 | F | Introduction of spurious emission TP analysis for CA_n48A-n70A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225779 | 0642 | 1 | F | Update to MPR for CA TP analysis to add PC2 requirements | 17.6.0 | +| 2022-09 | RAN#97 | R5-225825 | 0648 | 1 | F | Ref sensitivity TP selection for DC_2A_n41A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225826 | 0651 | 1 | F | Ref sensitivity TP selection for DC_1A_n77A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225827 | 0652 | 1 | F | Ref sensitivity TP selection for DC_3A_n77A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225828 | 0653 | 1 | F | Ref sensitivity TP selection for DC_8A_n78A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225829 | 0654 | 1 | F | Ref sensitivity TP selection for DC_5A_n78A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225830 | 0655 | 1 | F | Ref sensitivity TP selection for DC_8A_n79A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225831 | 0656 | 1 | F | Ref sensitivity TP selection for DC_21A_n79A | 17.6.0 | +| 2022-09 | RAN#97 | R5-225832 | 0674 | 1 | F | Updated TP analysis MPR for CA in FR2 | 17.6.0 | +| 2022-12 | RAN#98 | R5-226298 | 0679 | | F | Addition of NS_03U in Table 4.1.2.1-1 and correction of number of test points for NS_03 and NS_100 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226519 | 0683 | | F | Addition of reference sensitivity test point analysis for three bands within FR1 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226521 | 0684 | | F | Update of spurious emission TP analysis for Rel-15 NR CA configuration CA_n3A-n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-226522 | 0685 | | F | Update of spurious emission TP analysis for Rel-15 NR CA configuration CA_n8A-n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-226585 | 0689 | | F | Ref sense TP analysis for DC_30A_n66A | 17.7.0 | +| 2022-12 | RAN#98 | R5-226589 | 0693 | | F | Update test frequency for DC_5A_n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-226701 | 0695 | | F | Addition of CA_n41-n66/- in sensitivity test case config table. | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98 | R5-226830 | 0706 | | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n66A-n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227228 | 0718 | | F | Update of spurious emission TP analysis for Rel-17 NR CA configuration CA_n48A-n71A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227294 | 0720 | | F | Editorial corrections on TpAnalysisSpur filename | 17.7.0 | +| 2022-12 | RAN#98 | R5-227711 | 0676 | 1 | F | Spur_TpAnalysis for CA_n2A_n5A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227712 | 0677 | 1 | F | Spur_TpAnalysis for CA_n2A_n48A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227713 | 0694 | 1 | F | Ref_sense_TpAnalysis for CA_n2A_n5A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227714 | 0682 | 1 | F | Update TP analysis for reference sensitivity frequency selections | 17.7.0 | +| 2022-12 | RAN#98 | R5-227715 | 0686 | 1 | F | Introduction of spurious emissions TP analysis for 18A_n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227716 | 0687 | 1 | F | Introduction of spurious emissions TP analysis for 18A_n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227717 | 0688 | 1 | F | Addition of reference sensitivity test point analysis for 18A_n77A and 18A_n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227718 | 0696 | 1 | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n1A-n78A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227719 | 0697 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 NR CA configuration CA_n1A-n79A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227720 | 0698 | 1 | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n28A-n41A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227721 | 0699 | 1 | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n2A-n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227722 | 0700 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 NR CA configuration CA_n39A-n41A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227723 | 0701 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 NR CA configuration CA_n3A-n41A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227724 | 0702 | 1 | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n41A-n79A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227725 | 0703 | 1 | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n48A-n66A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227726 | 0704 | 1 | F | Update of spurious emission TP analysis for Rel-16 NR CA configuration CA_n5A-n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227727 | 0719 | 1 | F | Introduction of CA_n48A-n77A and CA_n71A-n77A test point analyses | 17.7.0 | +| 2022-12 | RAN#98 | R5-227895 | 0680 | 1 | F | Update TP analysis of reference sensitivity for CA_n66A-n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227897 | 0681 | 1 | F | Update TP analysis for ref sensitivity for Rel-16 NR CA combos | 17.7.0 | +| 2022-12 | RAN#98 | R5-227904 | 0709 | 1 | F | Updating TP analysis for NS_49 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227907 | 0692 | 1 | F | Update test frequency for DC_48A_n66A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227909 | 0710 | 1 | F | Test point analysis for mpr-PowerBoost tests 6.4.2.1_1, 6.5.2.1_1, 6.5.3.1_1, 6.5.3.2_1 and 6.5.3.3_1 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227912 | 0711 | 1 | F | Updating TP analysis for 6.2G.2 to add power class 3 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227914 | 0690 | 1 | F | Ref sense TP analysis for DC_66A_n5A | 17.7.0 | +| 2022-12 | RAN#98 | R5-227915 | 0691 | 1 | F | Ref sense TP analysis for DC_12A_n66A | 17.7.0 | +| 2023-03 | RAN#99 | R5-230215 | 0724 | - | F | Correction of TP analysis for FR2 ACLR for SCS 60 kHz | 17.8.0 | +| 2023-03 | RAN#99 | R5-230281 | 0725 | - | F | Update reference sensitivity test cases for three bands configurations of CA_n2A-n5A-n77A, CA_n2A-n66A-n77A, and CA_n5A-n66A-n77A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230320 | 0728 | - | F | Addition of reference sensitivity test point analysis for new EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230944 | 0744 | - | F | Addition of reference sensitivity test point analysis for DC_1A_n28A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230945 | 0745 | - | F | Addition of reference sensitivity test point analysis for DC_8A_n41A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230946 | 0746 | - | F | Addition of reference sensitivity test point analysis for DC_12A_n78A | 17.8.0 | +| 2023-03 | RAN#99 | R5-230947 | 0747 | - | F | Addition of reference sensitivity test point analysis for DC_2A-n66A_n5A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231241 | 0750 | - | F | Test point analysis update for A-MPR test for NS_21 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231311 | 0754 | - | F | Updated TP analysis for DC_25A_n41A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231608 | 0727 | 1 | F | Addition of reference sensitivity test point analysis for new 3CC EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231609 | 0738 | 1 | F | Ref sensitivity TP selection for DC_71A_n66A DC_14A_n2A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231610 | 0742 | 1 | F | Adding Spurious emission TP for DC_71A_n66A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231611 | 0743 | 1 | F | Adding Spurious emission TP for DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231612 | 0739 | 1 | F | Update Ref sensitivity TP selection for DC_21A_n79A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231613 | 0740 | 1 | F | Ref sensitivity TP selection for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231614 | 0741 | 1 | F | Adding Spurious emission TP for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231615 | 0748 | 1 | F | Update of spurious emission TP analysis for CA_n1A-n8A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231616 | 0752 | 1 | F | Reference sensitivity TP analysis for DC_66A_n41A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231620 | 0733 | 1 | F | Adding TP for CA_AMPR CA_NS_04 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231621 | 0734 | 1 | F | Merging TP analysis of CA_MPR, ACLR and SEM | 17.8.0 | +| 2023-03 | RAN#99 | R5-231622 | 0735 | 1 | F | Adding TP for CA spurious emission for PC2 and PC3 intra-band contiguous | 17.8.0 | +| 2023-03 | RAN#99 | R5-231623 | 0731 | 1 | F | Update to TP analysis of 6.2.3 NS_27 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231624 | 0736 | 1 | F | Adding TP for CA spurious emission co-existence for PC2 and PC3 intra-band contiguous | 17.8.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------|---------| +| 2023-03 | RAN#99 | R5-231625 | 0732 | 1 | F | Adding 45MHz PC2 TP analysis to 6.2.3 NS_49 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231633 | 0749 | 1 | F | Addition of CA_n41A-n71A. | 17.8.0 | +| 2023-03 | RAN#99 | R5-231833 | 0737 | 2 | F | NTN test point analysis | 17.8.0 | +| 2023-03 | RAN#99 | R5-231865 | 0753 | 1 | F | Clarifications and alignment of REFSENS TP analysis for EN-DC and NR CA | 17.8.0 | +| 2023-03 | RAN#99 | R5-231879 | 0729 | 1 | F | Addition of spurious emissions TP analysis for 1A_n41A and 41A_n28A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231880 | 0730 | 1 | F | Addition of spurious emissions TP analysis for 21A_n28A | 17.8.0 | +| 2023-06 | RAN#100 | R5-232114 | 0755 | - | F | Introduction of MOP test point analysis for CA_n28A-n78A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232115 | 0756 | - | F | Introduction of spurious emission TP analysis for CA_n28A-n78A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232116 | 0757 | - | F | Introduction of reference sensitivity test point analysis for CA_n28A-n78A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232347 | 0759 | - | F | TP analysis updated for NTN maximum input level test case 7.4 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232424 | 0763 | - | F | Addition of spurious emission TP analysis for CA_n1A-n3A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232608 | 0766 | - | F | Ref sensitivity TP selection for DC_7A_n66A DC_7A_n77A and DC_66A_n25A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232707 | 0768 | - | F | Addition of reference sensitivity test point analysis for n3A-n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232709 | 0769 | - | F | Addition of reference sensitivity test point analysis for n28A-n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232718 | 0770 | - | F | Addition of reference sensitivity test point analysis for DC_21A_n28A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232876 | 0775 | - | F | Editorial in Table 4.1.3.1-2 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232878 | 0776 | - | F | Addition of CA_n41A-n66A-n71A in sensitivity test case config table. | 17.9.0 | +| 2023-06 | RAN#100 | R5-232976 | 0778 | - | F | Introduction of TP analysis for A-MPR - New NR band n13 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233094 | 0780 | - | F | Updating TP analysis for Transmit ON/OFF time mask for CA | 17.9.0 | +| 2023-06 | RAN#100 | R5-233171 | 0782 | - | F | Addition of Test Point Analysis for CA_NS_202 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233256 | 0783 | - | F | TP Analysis for FR2 RF test case involving EIRP with UL-Gaps | 17.9.0 | +| 2023-06 | RAN#100 | R5-233512 | 0762 | 1 | F | Correction to spurious emissions TP analysis for 21A_n28A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233513 | 0767 | 1 | F | Spur_TpAnalysis for CA_n5A_n48A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233514 | 0764 | 1 | F | TP analysis for NR NTN configured transmission power tests | 17.9.0 | +| 2023-06 | RAN#100 | R5-233518 | 0760 | 1 | F | TP analysis update for FR2 2 UL CA Tx tests to support PHR method | 17.9.0 | +| 2023-06 | RAN#100 | R5-233519 | 0765 | 1 | F | Ref sensitivity TP selection for DC_38A_n78A DC_18A_n77A and DC_19A_n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233521 | 0761 | 1 | F | FR1 MPR - ACLR - SEM - TP analysis update for almost contiguous RB allocation | 17.9.0 | +| 2023-06 | RAN#100 | R5-233522 | 0772 | 1 | F | Correction to test point analysis for FR1 test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233523 | 0777 | 1 | F | Clarification/improvement of clause B9. | 17.9.0 | +| 2023-06 | RAN#100 | R5-233526 | 0779 | 1 | F | Updating REFSENS exception test frequency selection for CA_n7A-n78A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233528 | 0773 | 2 | F | TP analysis for PC2 PC3 n39 A-MPR and A-SE | 17.9.0 | +| 2023-06 | RAN#100 | R5-233530 | 0781 | 1 | F | Correction of test point analysis for CA_n66A-n71A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233713 | 0758 | 1 | F | Update inter-band NR CA reference sensitivity exception cases due to UL PC2 | 17.9.0 | +| 2023-09 | RAN#101 | R5-233948 | 0784 | - | F | Introduction of spurious emission TP analysis for CA_n20A-n78A | 17.10.0 | +| 2023-09 | RAN#101 | R5-234200 | 0789 | - | F | Update reference sensitivity test cases for additional three bands configurations | 17.10.0 | +| 2023-09 | RAN#101 | R5-234204 | 0790 | - | F | Update reference sensitivity test cases for a few PC2 three band configurations | 17.10.0 | +| 2023-09 | RAN#101 | R5-234450 | 0792 | - | F | Test point analysis for reference sensitivity for several NR CA combos | 17.10.0 | +| 2023-09 | RAN#101 | R5-234590 | 0795 | - | F | Update 38.521-1 TPanalysis_6.5.4_TxIm_v3 for NR-U | 17.10.0 | +| 2023-09 | RAN#101 | R5-234630 | 0798 | - | F | TP analysis for NR NTN AMPR tests | 17.10.0 | +| 2023-09 | RAN#101 | R5-234728 | 0800 | - | F | Introduction of TP analysis of CA_n3A_n41A Ref Sense exception | 17.10.0 | +| 2023-09 | RAN#101 | R5-234730 | 0801 | - | F | Introduction of TP analysis of CA_n28A-n41A-n79A Ref Sense exception | 17.10.0 | +| 2023-09 | RAN#101 | R5-234839 | 0803 | - | F | Addition of TP analysis of SE-coex for intra-band non-contiguous CA | 17.10.0 | +| 2023-09 | RAN#101 | R5-234846 | 0804 | - | F | Addition of TP analysis of spurious emission co-existence for CA_n28-n79 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234849 | 0805 | - | F | Addition of TP analysis of 6.3A.3.3 2Tx-2Tx UL switching for inter-band CA | 17.10.0 | +| 2023-09 | RAN#101 | R5-235015 | 0807 | - | F | Addition of spurious emission TP analysis for CA_n3A-n8A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235041 | 0808 | - | F | Updating test frequency selection for REFSENS exception testing for CA | 17.10.0 | +| 2023-09 | RAN#101 | R5-235620 | 0793 | 1 | F | Introduction of spurious emission TP analysis for Rel-16 NR CA configuration CA_n5A-n66A. | 17.10.0 | +| 2023-09 | RAN#101 | R5-235622 | 0809 | 1 | F | Updating REFSENS test point selection for CA_n39A-n41A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235626 | 0802 | 1 | F | Update TP analysis of Ref sense exception of NR CA PC2 configs | 17.10.0 | +| 2023-09 | RAN#101 | R5-235632 | 0794 | 1 | F | Update 38.905 for NR-U | 17.10.0 | +| 2023-09 | RAN#101 | R5-235649 | 0791 | 1 | F | Addition of spurious emissions TP analysis for new NRCA comb within FR1 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235680 | 0813 | 1 | F | TP analysis for NTN TC 6.3.3 on Tx on-off time mask | 17.10.0 | +| 2023-09 | RAN#101 | R5-235682 | 0814 | 1 | F | TP analysis for NTN TC 6.5.2.4 on ACLR | 17.10.0 | +| 2023-09 | RAN#101 | R5-235684 | 0815 | 1 | F | TP analysis for NTN TC 6.5.2.2 on Spectrum emission mask | 17.10.0 | +| 2023-09 | RAN#101 | R5-235848 | 0785 | 1 | F | Introduction of reference sensitivity test point analysis for CA_n20A- | 17.10.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| | | | | | | n78A | | +| 2023-09 | RAN#101 | R5-235855 | 0817 | 1 | F | TP analysis for FR2 RF phase continuity test | 17.10.0 | +| 2023-09 | RAN#101 | R5-235856 | 0786 | 1 | F | Update TP analysis for 7.4 | 17.10.0 | +| 2023-09 | RAN#101 | R5-235857 | 0787 | 1 | F | Update TP analysis for 7.4A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235858 | 0799 | 1 | F | TP analysis update for NTN | 17.10.0 | +| 2023-09 | RAN#101 | R5-235937 | 0816 | 1 | F | TP analysis for FR1 RF phase continuity test | 17.10.0 | +| 2023-09 | RAN#101 | R5-234619 | 0796 | - | F | Updates to TP analyses for spurious emissions UE coexistence for CA combinations as part of the introduction of LTE TDD Band 54 | 18.0.0 | +| 2023-09 | RAN#101 | R5-235860 | 0797 | 1 | F | Updates and additions to TP analyses for spurious emissions UE coexistence for EN-DC combinations as part of the introduction of LTE TDD Band 54 | 18.0.0 | +| 2023-12 | RAN#102 | R5-236074 | 0818 | - | F | Introduction of reference sensitivity test point analysis for CA_n1A-n3A-n28A-n78A | 18.1.0 | +| 2023-12 | RAN#102 | R5-236081 | 0820 | - | F | Introduction of spurious emission TP analysis for CA_n25A-n66A, CA_n25A-n77A, CA_n25A-n78A, CA_n66A-n78A | 18.1.0 | +| 2023-12 | RAN#102 | R5-236251 | 0824 | - | F | Removal of technical content in TR 38.905 v17.10.0 and substitution with pointer to the next Release | 18.1.0 | +| 2023-12 | RAN#102 | R5-236287 | 0825 | - | F | Addition of inter-band NR CA reference sensitivity PC2 exception cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-236356 | 0826 | - | F | Test point analysis for several EN-DC and NR CA combos for spurious emissions | 18.1.0 | +| 2023-12 | RAN#102 | R5-236371 | 0827 | - | F | Update reference sensitivity test cases for additional three bands ENDC configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-236377 | 0828 | - | F | Update test point analysis clause for additional NR CA band configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-236482 | 0832 | - | F | Updated TP analysis for NR-U test cases SEM, MPR and ACLR | 18.1.0 | +| 2023-12 | RAN#102 | R5-236504 | 0834 | - | F | Addition of REFSENS TP analysis for 2CC EN-DC for n79 in PC2 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236632 | 0836 | - | F | Update to TP analysis for FR2 CA_NS_202 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236953 | 0838 | - | F | Update reference sensitivity test cases for CA_n1A-n3A-n78A | 18.1.0 | +| 2023-12 | RAN#102 | R5-237049 | 0839 | - | F | Updating TP analysis for Configured output power for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237052 | 0840 | - | F | Updating TP analysis for Minimum output power for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237054 | 0841 | - | F | Updating TP analysis for Frequency error testing for intra-band UL CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237056 | 0842 | - | F | Updating TP analysis for Spurious emission for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237059 | 0843 | - | F | Updating TP analysis for FR1 test case Transmit intermodulation for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237061 | 0844 | - | F | Updating TP analysis for FR1 test case EVM for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237065 | 0846 | - | F | Updating TP analysis for FR1 test case Inband emissions for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237070 | 0847 | - | F | Updating TP analysis for AMPR for CA testing for NS_17 NS_47 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237615 | 0821 | 1 | F | Addition of reference sensitivity and spurious emissions TP analysis for new R16 NR CA comb within FR1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237617 | 0819 | 1 | F | Introduction of reference sensitivity test point analysis for CA_n25A-n66A-n77(2A) and CA_n25A-n66A-n78(2A) | 18.1.0 | +| 2023-12 | RAN#102 | R5-237619 | 0822 | 1 | F | Addition of reference sensitivity TP analysis for new R17 NR CA comb within FR1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237622 | 0829 | 1 | F | Remove Editors Notes and made the necessary changes for Table 4.1.3.1-3 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237630 | 0845 | 1 | F | Updating TP analysis for FR1 test case Carrier Leakage for CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237633 | 0835 | 1 | F | TP analyze 6.2F.3 shared spectrum access NS_28 and NS_29 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237635 | 0833 | 1 | F | Addition of REFSENS TP analysis for 3CC EN-DC for n78 and n79 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237901 | 0849 | 1 | F | TP analysis for FR2 CA_NS_203 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237930 | 0823 | 1 | F | Test point analysis for NR NTN test cases from 7.5 to 7.9 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237931 | 0848 | 1 | F | Adding Test point analysis for NR NTN frequency error test case | 18.1.0 | +| 2023-12 | RAN#102 | R5-237935 | 0837 | 1 | F | Addition of test point analysis for FR1 CA with UL MIMO test cases | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38918/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/38_series/38918/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43dc3dff93be5a0d5c8ee65f67d9b20b23b20028 --- /dev/null +++ b/marked/Rel-18/38_series/38918/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56fd673b0ee8e0fa233cc1f9e65d0c493c17762f8fecb5f372310082b7ba8acd +size 58415 diff --git a/marked/Rel-18/38_series/38918/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38918/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38 --- /dev/null +++ b/marked/Rel-18/38_series/38918/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5 +size 9571 diff --git a/marked/Rel-18/38_series/38918/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38918/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..738b2be52eb38ad22d39a215e0b1fb73f6870840 --- /dev/null +++ b/marked/Rel-18/38_series/38918/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:417534555b0105b8aa97114cf9e8019b12a5f0d60256e8f3f7559b046c38526c +size 5672 diff --git a/marked/Rel-18/38_series/38918/raw.md b/marked/Rel-18/38_series/38918/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d25b0071a944e17e30163c04f1acb41a13e3c3f6 --- /dev/null +++ b/marked/Rel-18/38_series/38918/raw.md @@ -0,0 +1,2054 @@ + + +# 3GPP TR 38.918 V18.1.0 (2022-09) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on 5G NR User Equipment (UE) Full Stack Testing for Network Slicing Technical Report (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------|-----------| +| Foreword ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 General..... | 9 | +| 4.1 Background ..... | 9 | +| 4.2 Study Item Objective..... | 9 | +| 5 Study on 5G NR UE Full Stack Testing for Network Slicing ..... | 10 | +| 5.1 Definition of 5G NR UE Full Stack Testing for Network Slicing..... | 10 | +| 5.1.1 Definition of Full Stack ..... | 10 | +| 5.2 Test Configurations..... | 10 | +| 5.2.1 UE Full Stack Network Slicing Test Equipment..... | 10 | +| 5.2.2 UE Full Stack Network Slicing Test Equipment Connection Diagrams..... | 10 | +| 5.2.3 Network Slicing Configurations..... | 11 | +| 5.2.4 Message and Information Elements Contents ..... | 11 | +| 5.2.5 UE Specific Items..... | 12 | +| 5.3 Application Simulation ..... | 13 | +| 5.3.1 Application Client Simulator..... | 13 | +| 5.3.2 Test Models ..... | 13 | +| 5.4 Statistical Analysis ..... | 14 | +| 5.4.1 Overview of Mapping Application to Network Slicing ..... | 14 | +| 5.4.2 Overview of Application Layer Throughput With Network Slicing..... | 14 | +| 5.4.3 Overview of Application Layer Latency With Network Slicing..... | 14 | +| 5.5 Test System Uncertainty and Test Tolerance..... | 15 | +| 5.5.1 Test System Uncertainty and Test Tolerance for FR1 testing..... | 15 | +| 5.5.1.1 Recommended Uncertainty of Test System..... | 15 | +| 5.5.1.2 Test Tolerances ..... | 15 | +| 5.5.1.3 Impact of Test System Uncertainty on Test Results..... | 15 | +| 6 Conclusions..... | 15 | +| Annex A: Test Procedures..... | 17 | +| A.1 Purpose of annex..... | 17 | +| A.2 5G NR /URSP Configuration and Application Mapping..... | 17 | +| A.2.1 5G NR /URSP Configuration ..... | 17 | +| A.2.1.1 5G NR / URSP Configuration / Signalling..... | 17 | +| A.2.1.1.1 Definition ..... | 17 | +| A.2.1.1.2 Test Purpose..... | 17 | +| A.2.1.1.3 Test Parameters..... | 17 | +| A.2.1.1.4 Test Description..... | 17 | +| A.2.1.1.4.1 Initial Conditions..... | 17 | +| A.2.1.1.4.2 Test Procedure..... | 17 | +| A.2.2 5G NR / Mapping Application to Network Slicing..... | 20 | +| A.2.2.1 5G NR / Mapping Application to Network Slicing / DNN..... | 20 | +| A.2.2.1.1 Definition ..... | 20 | +| A.2.2.1.2 Test Purpose..... | 20 | +| A.2.2.1.3 Test Parameters..... | 20 | +| A.2.2.1.4 Test Description..... | 20 | +| A.2.2.1.4.1 Initial Conditions..... | 20 | +| A.2.2.1.4.2 Test Procedure..... | 20 | + +| | | | +|-------------|----------------------------------------------------------------------------------------|----| +| A.2.2.2 | 5G NR / Mapping Application to Network Slicing / APP ID ..... | 22 | +| A.2.2.2.1 | Definition ..... | 22 | +| A.2.2.2.2 | Test Purpose..... | 22 | +| A.2.2.2.3 | Test Parameters..... | 22 | +| A.2.2.2.4 | Test Description..... | 22 | +| A.2.2.2.4.1 | Initial Conditions..... | 22 | +| A.2.2.2.4.2 | Test Procedure..... | 22 | +| A.2.2.3 | 5G NR / Mapping Application to Network Slicing / FQDN..... | 24 | +| A.2.2.3.1 | Definition ..... | 24 | +| A.2.2.3.2 | Test Purpose..... | 24 | +| A.2.2.3.3 | Test Parameters..... | 24 | +| A.2.2.3.4 | Test Description..... | 24 | +| A.2.2.3.4.1 | Initial Conditions..... | 24 | +| A.2.2.3.4.2 | Test Procedure..... | 24 | +| A.2.2.4 | 5G NR / Mapping Application to Network Slicing / IP 3 Tuples ..... | 26 | +| A.2.2.4.1 | Definition ..... | 26 | +| A.2.2.4.2 | Test Purpose..... | 26 | +| A.2.2.4.3 | Test Parameters..... | 26 | +| A.2.2.4.4 | Test Description..... | 26 | +| A.2.2.4.4.1 | Initial Conditions..... | 26 | +| A.2.2.4.4.2 | Test Procedure..... | 26 | +| A.2.2.5 | 5G NR / Mapping Application to Network Slicing / Connection Capabilities ..... | 28 | +| A.2.2.5.1 | Definition ..... | 28 | +| A.2.2.5.2 | Test Purpose..... | 28 | +| A.2.2.5.3 | Test Parameters..... | 28 | +| A.2.2.5.4 | Test Description..... | 28 | +| A.2.2.5.4.1 | Initial Conditions..... | 28 | +| A.2.2.5.4.2 | Test Procedure..... | 28 | +| A.2.2.6 | 5G NR / Mapping Application to Network Slicing / URSP Update ..... | 30 | +| A.2.2.6.1 | Definition ..... | 30 | +| A.2.2.6.2 | Test Purpose..... | 30 | +| A.2.2.6.3 | Test Parameters..... | 30 | +| A.2.2.6.4 | Test Description..... | 30 | +| A.2.2.6.4.1 | Initial Conditions..... | 30 | +| A.2.2.6.4.2 | Test Procedure..... | 30 | +| A.3 | 5G NR / Service Performance Testing with Network Slicing ..... | 32 | +| A.3.1 | 5G NR / Service Performance / Single Network Slicing ..... | 32 | +| A.3.1.1 | 5G NR / Service Performance / Single Application with Single Network Slicing ..... | 32 | +| A.3.1.1.1 | Definition ..... | 32 | +| A.3.1.1.2 | Test Purpose..... | 32 | +| A.3.1.1.3 | Test Parameters..... | 32 | +| A.3.1.1.4 | Test Description..... | 32 | +| A.3.1.1.4.1 | Initial Conditions..... | 32 | +| A.3.1.1.4.2 | Test Procedure..... | 33 | +| A.3.1.2 | 5G NR / Service Performance / Multiple Applications with Single Network Slicing ..... | 34 | +| A.3.1.2.1 | Definition ..... | 34 | +| A.3.1.2.2 | Test Purpose..... | 34 | +| A.3.1.2.3 | Test Parameters..... | 34 | +| A.3.1.2.4 | Test Description..... | 35 | +| A.3.1.2.4.1 | Initial Conditions..... | 35 | +| A.3.1.2.4.2 | Test Procedure..... | 35 | +| A.3.2 | 5G NR / Service Performance / Multiple Network Slicing..... | 37 | +| A.3.2.1 | 5G NR / Service Performance / Multiple Applications with Multiple Network Slicing..... | 37 | +| A.3.2.1.1 | Definition ..... | 37 | +| A.3.2.1.2 | Test Purpose..... | 37 | +| A.3.2.1.3 | Test Parameters..... | 37 | +| A.3.2.1.4 | Test Description..... | 37 | +| A.3.2.1.4.1 | Initial Conditions..... | 37 | +| A.3.2.1.4.2 | Test Procedure..... | 37 | +| A.3.3 | 5G NR / Service Performance / URSP Update ..... | 41 | +| A.3.3.1 | 5G NR / Service Performance / Single Network Slicing / URSP update..... | 41 | + +| | | | +|--------------------------------------|----------------------------------------------------------------------------|-----------| +| A.3.3.1.1 | Definition ..... | 41 | +| A.3.3.1.2 | Test Purpose..... | 41 | +| A.3.3.1.3 | Test Parameters..... | 41 | +| A.3.3.1.4 | Test Description..... | 41 | +| A.3.3.1.4.1 | Initial Conditions..... | 41 | +| A.3.3.1.4.2 | Test Procedure..... | 41 | +| A.3.3.2 | 5G NR / Service Performance / Multiple Network Slicing / URSP update ..... | 43 | +| A.3.3.2.1 | Definition ..... | 43 | +| A.3.3.2.2 | Test Purpose..... | 43 | +| A.3.3.2.3 | Test Parameters..... | 43 | +| A.3.3.2.4 | Test Description..... | 43 | +| A.3.3.2.4.1 | Initial Conditions..... | 43 | +| A.3.2.2.4.2 | Test Procedure..... | 43 | +| Annex B: Applicability..... | | 48 | +| Annex C: Change history ..... | | 49 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document contains the findings of the Study on 5G NR UE full stack testing of network slicing and the proposed test procedures. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". +- [3] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [4] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification". +- [5] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification". +- [6] 3GPP TS 38.508-1: "5GS;User Equipment (UE) conformance specification; Part 1: Common test environment". +- [7] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [8] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [9] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); stage 3". +- [10] 3GPP TS 24.526: "UE policies for 5G System (5GS); Stage 3". +- [11] 3GPP TS 23.003: "Numbering, addressing and identification". +- [12] 3GPP TS 38.521-4: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 4: Performance requirements". +- [13] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +Void + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 General + +## 4.1 Background + +5G Network Slicing is one of the most distinctive features provided by 5G NR and is key to meet diversified services requirements in 5G era. With the introduction of 5G network slicing technology, operators will be able to provide network capabilities with different functional characteristics, which will provide e.g. "exclusive" network for users with different KPI requirements to ensure a high-quality of service and meet differentiated scenario requirements. 5G network slicing can also help to achieve the goal of improving the efficiency of network resource utilization, optimizing the network construction investment of operators, and building a flexible and agile 5G network. + +The user experience resulting from the use of 5G network slicing is critical for commercial success, and therefore testing the operation of 5G network slicing is necessary to ensure consistent predictable behaviour. To enable testing the 5G UEs supporting network slicing as they are used in the field the application layer at the device side needs to be included in the testing, as URSP based network slice selection and traffic routing procedures are based on traffic descriptor components (see TS 24.526) passed on by the application layer to the UE protocol stack. The traffic descriptor components that are passed onto the UE protocol stack to be used as a base for the network slice selection when a specific application requests a PDU session are configured within the device. There is a strong industry demand to define the test methods and test procedures that include the full related UE application layer in the testing of the network slice selection functionality for 5G UE supporting network slicing. + +## 4.2 Study Item Objective + +The technical objectives of this study item are: + +- To study how to define test procedures that will allow the full protocol stack testing of a 5G NR UE supporting network slicing. The test procedures for full protocol stack testing of the network slicing functionality, e.g. how the UE uses configurations matching UE application to traffic descriptor components to select S-NSSAI, will be provided. +- To study how to define test procedures that will allow the service performance testing of a 5G NR UE supporting network slicing. The test procedures for performance testing of the network slicing service, e.g. application layer throughput and latency, will be provided. + +NOTE 1: The Study Item should take into account industry recommendation from relevant organizations such as GSMA, NGMN and GTI pending on RAN5's decision on a case by case basis. + +NOTE 2: The Study Item should take into account the User Privacy and/or implementation confidentiality. + +NOTE 3: The Study Item will not define the specific traffic descriptor or related mapping mechanism. + +# 5 Study on 5G NR UE Full Stack Testing for Network Slicing + +## 5.1 Definition of 5G NR UE Full Stack Testing for Network Slicing + +### 5.1.1 Definition of Full Stack + +The test procedures defined will allow the full stack testing of a 5G NR UE supporting network slicing. The term "full stack" means multilayer combined performance of the following layers: + +- 1 UE's Radio link protocol data processing performance (PHY, MAC, RLC, PDCP) +- 2 UE's Radio link protocol signalling processing capability (RRC, NAS) +- 3 UE's TCP/IP processing performance +- 4 UE's Internet Application processing performance + +## 5.2 Test Configurations + +### 5.2.1 UE Full Stack Network Slicing Test Equipment + +The test equipment utilized for 5G NR UE Full Stack Testing for Network Slicing should consist of the following items: + +- System Simulator(s) is used to simulate the 5G network for network slicing testing. System simulator(s) could receive network slice configuration scheme from main controller and send network slicing related configuration to UE via signalling. System simulator(s) could receive application data from UE and send application data to application server simulator(s). +- Application Server Simulator(s) is used to simulate the service in application layer for receiving application data from UE via system simulator(s) and handling the received application data. Application Server Simulator(s) could be either implemented in Main Controller or implemented as an independent unit. +- Main Controller is used to get and configure the type of traffic descriptor to be tested to Application Client Simulator, generate network slice configuration scheme and configure the network slice configuration scheme to System Simulator(s). +- Application Client Simulator(s) suitable for generating Traffic Descriptor of application(s) and corresponding application data on UE side. + +### 5.2.2 UE Full Stack Network Slicing Test Equipment Connection Diagrams + +The UE Full Stack Network Slicing Test Equipment connection diagram is shown in Figure 5.2.2-1. + +![Figure 5.2.2-1: UE Full Stack Network Slicing Test Equipment Connection Diagram. The diagram shows a User Equipment (UE) on the left connected via an NR interface to a System Simulator(s) on the right. The UE contains an Operating System with layers: Application Client Simulator(s), Transport TCP/UDP, Network IP, and PHY. The System Simulator(s) contains layers: Transport TCP/UDP, Network IP, and PHY. A Main Controller is connected to the System Simulator(s). An Application Server Simulator(s) is also connected to the System Simulator(s). Dashed lines represent data flow between the UE and the System Simulator(s).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 5.2.2-1: UE Full Stack Network Slicing Test Equipment Connection Diagram. The diagram shows a User Equipment (UE) on the left connected via an NR interface to a System Simulator(s) on the right. The UE contains an Operating System with layers: Application Client Simulator(s), Transport TCP/UDP, Network IP, and PHY. The System Simulator(s) contains layers: Transport TCP/UDP, Network IP, and PHY. A Main Controller is connected to the System Simulator(s). An Application Server Simulator(s) is also connected to the System Simulator(s). Dashed lines represent data flow between the UE and the System Simulator(s). + +Figure 5.2.2-1: UE Full Stack Network Slicing Test Equipment Connection Diagram + +### 5.2.3 Network Slicing Configurations + +Unless otherwise stated, following application information and corresponding S-NSSAI will be used as default network slicing configurations. + +Table 5.2.3-1: Network Slicing Configurations + +| Application | OS App id | DNN | FQDN | IP 3 Tuples | S-NSSAI | | +|-------------|------------------|------------------------|-------------|------------------------------------------------------|-------------|----------| +| | | | | | SST | SD | +| APP A | pc_OS_App_ID | pc_APN_ID_Specific | pc_Des_FQDN | pc_IP_Address, pc_Protocol_ID, pc_Single_Remote_Port | '00000001'B | 0x000001 | +| APP B | pc_OS_App_ID_2nd | pc_APN_ID_Specific_2nd | Void | Void | '00000010'B | 0x000001 | + +### 5.2.4 Message and Information Elements Contents + +The common message and information elements contents are defined in TS 38.508-1 [6] clause 4. In addition, the following message and information elements contents apply: + +#### MANAGE UE POLICY COMMAND + +Table 5.2.4-1: MANAGE UE POLICY COMMAND + +| Derivation Path: TS 24.501 Table D.5.1.1.1 | | | | +|--------------------------------------------|-------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| PTI | Any value from 1 to 254 | | | +| MANAGE UE POLICY COMMAND message identity | '0000 0001'B | | | +| UE policy section management list | See Table 5.2.4-2 | | | + +UE policy section management list + +**Table 5.2.4-2: UE policy section management list** + +| Derivation Path: TS 24.501 Figure D.6.2.1 | | | | +|------------------------------------------------------|-----------------------------------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UE policy section management list IEI | | | | +| Length of UE policy section management list contents | Set to the actual length of 'UE policy section management list contents' in bytes | | | +| UE policy section management list contents | | | | +| UE policy section management sublist (PLMN-1) | | | | +| Length of UE policy section management sublist | Set to the actual length of 'UE policy section management sublist' in bytes | | | +| PLMN ID | Set to the PLMN value used in the test procedure | | | +| UE policy section management sublist contents | | | | +| Instruction contents length | Set to the actual length of 'Instruction contents' in bytes | | | +| UE policy section contents | | | | +| UE policy part | See Table 5.2.4-3 | | | + +UE policy part + +**Table 5.2.4-3: UE policy part with UE policy part type = {URSP}** + +| Derivation Path: TS 24.501 Figure D.6.2.7 | | | | +|-------------------------------------------|----------------------------------------------------------------|---------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part contents length | Set to the actual length of 'UE policy part contents' in bytes | | | +| Spare | '0000'B | | | +| UE policy part type | '0001'B | | URSP | +| UE policy part contents | | | | +| URSP rule 1 | See Table 4.8.5.2-1 in TS 38.508-1 | | | +| URSP rule 2 | See Table 4.8.5.2-1 in TS 38.508-1 | | | + +### 5.2.5 UE Specific Items + +The following parameters are recommended to be provided by UE or application supplier to indicate the information of application using network slicing during test. + +Table 5.2.5-1: UE specific Items + +| Parameter Name | Parameter Type | Description | +|------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pc_APN_ID_Specific | charstring | APN/DNN value of the simulation application client defined in clause 5.3.1
The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [11], subclause 9.1 | +| pc_OS_App_ID | charstring | OS App Id value of the simulation application client defined in clause 5.3.1
The coding of OS App Id is up to UE implementation | +| pc_Des_FQDN | charstring | The destination FQDN value of Application Server Simulator(s) defined in clause 5.2.1
The destination FQDN as defined in subclause 28.3.2.1 in TS 23.003 [11] | +| pc_IP_Address | charstring | The IP address of Application Server Simulator(s) defined in clause 5.2.1
The coding of IP address is four octet IPv4 address and 4 octet IPv4 address mask for IPv4 or sixteen octet IPv6 address and one octet prefix length for IPv6 | +| pc_Protocol_ID | charstring | The IPv4 protocol identifier or IPv6 next header of Application Server Simulator(s) defined in clause 5.2.1 | +| pc_Sinlge_Remote_Port | charstring | The port number of Application Server Simulator(s) defined in clause 5.2.1 | +| pc_APN_ID_Specific_2nd | charstring | APN/DNN value of the second application simulated by simulation application client in the scenario of two applications running in parallel
The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [11], subclause 9.1 | +| pc_OS_App_ID_2nd | charstring | OS App Id value of the second application simulated by simulation application client in the scenario of two applications running in parallel
The coding of OS App Id is up to UE implementation | + +## 5.3 Application Simulation + +### 5.3.1 Application Client Simulator + +To enable testing an Application Client Simulator on device is used to simulate the application which configured with network slicing. The following functionality is recommended for the Application Client Simulator to support. + +- The Application Client Simulator is installed on device. +- The Application Client Simulator may start automatically on device power-up or manually be started by the operator at the beginning of the test campaign. +- The Application Client Simulator could receive the type of traffic descriptor to be tested and generate the corresponding traffic descriptor which conform to Network Slicing Configurations defined in clause 5.2.3. +- The Application Client Simulator could generate data packets matching the traffic descriptor in Network Slicing Configurations and transfer data packets to operating system and communication unit on device. +- The Application Client Simulator could directly send the generated data packets to application server simulator via cable connection. + +### 5.3.2 Test Models + +There is no specific Test Models identified at this time. + +## 5.4 Statistical Analysis + +### 5.4.1 Overview of Mapping Application to Network Slicing + +When the mapping of applications to network slicing is tested, the fundamental goal is to verify the procedure of associating applications to PDU sessions based on URSP rules. URSP rules contain Traffic Descriptors determining which URSP rule is applicable for the specific application and a list of Route Selection Descriptors determining the corresponding PDU session. + +With this knowledge, the following aspects are recommended to be checked to verify the procedure of mapping application to Network Slicing: + +- The selection of applicable URSP rule according to the Traffic descriptors in UE Route Selection Policy Rule within URSP rules and information from the specific application. +- The selection of existing PDU session or establishment of new PDU session for specific application based on the selected Route Selection Descriptors within the applicable URSP rule. + +The way to trigger URSP rule selection is UE implementation specific and driven by application. To enable testing then the UE is recommended to be equipped with the application simulation client defined in clause 5.3.1 to trigger the required selection procedures + +### 5.4.2 Overview of Application Layer Throughput With Network Slicing + +In general, the application layer throughput is impacted by variations mainly at the physical layer and MAC layer. Thus, a variety of test points should be picked across different physical layer conditions (doppler, signal-to-noise ratio, antenna configurations, etc.). + +There can be multiple usages of network slicing with different needs such as mission critical ultra-reliable low latency slice, massive machine to machine type communication slice, extreme high throughput mobile broadband slice. Depending on the use case, channel requirements will be different and accordingly the application layer performance will also be benchmarked. + +During the application layer throughput measurement, ACK, NACK and DTX can also be recorded in order to calculate the L1 payload bit throughput, although this is not the main target of the test procedure. The measured throughput and its comparison to an expected throughput value can be evaluated. However, the parameters for this measurement are not as controlled as in the case of L1 throughput. + +For fixed reference channel testing, the UE is compared against a predefined limit at the physical layer. Therefore, statistics can be derived to determine the minimum number of samples for a given confidence level for the pass/fail decision. While the application layer data throughput is of a statistical nature, in case of fixed reference channel testing, it is possible to set a lower bound for the achievable throughput by computing the overhead due to upper layer payload headers. + +### 5.4.3 Overview of Application Layer Latency With Network Slicing + +In order to measure the application layer latency for a Standardized Slice Type (SST) or a non-standardized slice type, some important factors which needs to be considered may involve network node delay in time, jitter experienced based on channel bandwidth and network propagation conditions. Each such conditions can be evaluated against the QoS requirements and delay sensitivity of the data being transmitted. The end goal here is to optimize the utilization of the allocation of network resources and the quality of service metrics. + +For fixed or variable reference channel and an SST, the UE latency for each data traffic session per slice needs to be captured and evaluated against the required maximum delay in reception of the desired data packet. Based on the measured packet delay and jitter experienced e2e evaluation of the layer latency can be derived and benchmarked. Important aspect here to consider would be to adjust the tolerance +/- of the latency and jitter in percentage terms to define a final evaluation criterion as per testing needs and network traffic type usage. + +## 5.5 Test System Uncertainty and Test Tolerance + +### 5.5.1 Test System Uncertainty and Test Tolerance for FR1 testing + +#### 5.5.1.1 Recommended Uncertainty of Test System + +For service performance test procedure in Annex A, the test system should fulfil the 3GPP test system uncertainty values specified in Annex F of TS 38.521-4 [12]. If a test system cannot fulfil the 3GPP test system uncertainty requirements, then the test system vendor shall declare its test system uncertainty values. + +#### 5.5.1.2 Test Tolerances + +Since there are no absolute minimum requirements nor PASS/FAIL requirements in tests specified in the present TR the test tolerances are not defined which should be understood as the applicable test tolerance being set to zero in all tests. If PASS/FAIL requirements are recommended, appropriate analysis of test tolerance shall be considered. + +#### 5.5.1.3 Impact of Test System Uncertainty on Test Results + +Test system uncertainties play a big role in application layer throughput results. The tighter the uncertainty requirements are the more re-producible and comparable the results are. + +In TS 38.521-4 [12] applicable test system uncertainty has been specified. Test System Uncertainty is a measure how accurately tester can setup the certain parameter/signal level to the specified level. In 5G NR UE Full Stack Testing for Network Slicing, for service performance test procedure the most meaningful test system uncertainties are listed in Annex F of 38.521-4[12]. + +These specified test system uncertainties are very tight requirements for test systems. Typically the specified uncertainty values are the best that test system vendors can achieve when their test systems are fully calibrated. Full calibration means that each individual device, signal route and cable has to be calibrated. Hence the calibration costs take quite a big share of total costs of 3GPP compliant test systems. + +# --- 6 Conclusions + +The UE full stack testing for network slicing study item was initiated by RAN5 to include UE full stack network slicing capability. The following aspects were included as part of the present document: + +- Definition of UE Full Stack Testing for Network Slicing + +- Test configurations + +- Application Simulation + +- Statistical analysis + +- Test uncertainty and test tolerance + +The following items have been identified at the conclusion of the study item: + +- Definition of UE Full Stack Testing for Network Slicing and identification + +- Identification of the test configuration to include test equipment, test equipment connection diagrams, network slicing configurations, message and information elements and UE specific items + +Identification of the application client simulator + +Completion of the analysis for mapping between application to network slicing, application throughput and application latency with network slicing + +Consideration about the impact of test system uncertainty on test results and confirmation of the Test System Uncertainty Recommendations + +Identification of the test procedures for URSP Configuration and application mapping to network slicing + +Identification of the test procedure for service performance testing with network slicing + +The present document includes a set of recommended test procedures for UE supporting network slicing that is in-line with the study item objectives identified in clause 4. + +The test procedures are contained in Annex A. + +# --- Annex A: Test Procedures + +## A.1 Purpose of annex + +This annex specifies the test procedures for 5G NR UE Full Stack Testing for Network Slicing. The test procedures are the result of the study item and are the recommended test procedures to be used when evaluating UE capability of supporting network slicing. The use of "shall" in the test procedures listed herein is only used to indicate that the test purpose, procedure, and/or result may not be as expected if the specified "shall" or "must" item is not used or followed. As the Technical Report is informative in nature, the use of "shall" or "must" in the test procedures is not meant to imply a specific requirement. Their use is meant to indicate instances where the test objectives of the recommended test procedures may not be achieved. + +## --- A.2 5G NR /URSP Configuration and Application Mapping + +### A.2.1 5G NR /URSP Configuration + +#### A.2.1.1 5G NR / URSP Configuration / Signalling + +##### A.2.1.1.1 Definition + +The provisioning of URSP rules from network to UE is one of the fundamental functional requirements for network slicing. + +##### A.2.1.1.2 Test Purpose + +To verify that UE could support the provisioning of URSP rules from network to UE over NAS messages. + +##### A.2.1.1.3 Test Parameters + +Void. + +##### A.2.1.1.4 Test Description + +###### A.2.1.1.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.1.1.4.2 Test Procedure + +1. UE is switched on. + +2. Steps 2 to 13 of the generic procedure for NR RRC\_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed. +3. The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI and Configured NSSAI. +4. The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message. +5. The SS transmits a DL NAS TRANSPORT message including UE Policy Container and MANAGE UE POLICY COMMAND message to configure URSP rules. +6. The UE transmits an UL NAS TRANSPORT message including UE Policy Container and a MANAGE UE POLICY COMPLETE message is included. +7. The SS transmits an RRC Release message. + +**Table A.2.1.1.4.2-1: REGISTRATION ACCEPT (step 3)** + +| Derivation path: TS 38.508-1 Table 4.7.1-7 | | | | +|--------------------------------------------|--------------|-----------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| 5GS registration result value | '001'B | 3GPP access | | +| Allowed NSSAI | | | | +| S-NSSAI IEI | | S-NSSAI value 1 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | 1 | | +| SD | 0x000001 | | | +| Mapped configured SST | Not Present | | | +| Mapped configured SD | Not Present | | | +| S-NSSAI IEI | | S-NSSAI value 2 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | 1 | | +| SD | 0x000002 | | | +| Mapped configured SST | Not Present | | | +| Mapped configured SD | Not Present | | | +| Configured NSSAI | | | | +| S-NSSAI IEI | | S-NSSAI value 1 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | +| Mapped configured SST | Not Present | | | +| Mapped configured SD | Not Present | | | +| S-NSSAI IEI | | S-NSSAI value 2 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | 1 | | +| SD | 0x000002 | | | +| Mapped configured SST | Not Present | | | +| Mapped configured SD | Not Present | | | + +**Table A.2.1.1.4.2-2: DL NAS TRANSPORT (step 5)** + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-11 | | | | +|--------------------------------------------------|-------------------------|---------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0101'B | UE policy container | | +| Payload container | See Table A.2.1.1.4.2-3 | | | + +Table A.2.1.1.4.2-3: MANAGE UE POLICY COMMAND (step 5) + +| Information Element | Value/remark | Comment | Condition | +|------------------------------------------------|--------------------------------------------------|------------|----------------| +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | | DNN Type | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| Route selection descriptor 2 | | | | +| Precedence value of route selection descriptor | 1 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000100'B | | DNN type | +| Route selection descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | | OS App Id type | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id' in bytes | | | +| OS App Id | pc_OS_App_ID | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | +| Route selection descriptor 2 | | | | +| Precedence value of route selection descriptor | 1 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000100'B | | DNN type | +| Route selection descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +### A.2.2 5G NR / Mapping Application to Network Slicing + +#### A.2.2.1 5G NR / Mapping Application to Network Slicing / DNN + +##### A.2.2.1.1 Definition + +The UE procedure for associating applications to PDU sessions based on URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.2.2.1.2 Test Purpose + +To verify that UE could support the mapping of applications to URSP rules and the establishment of PDU sessions based on the Traffic Descriptor of DNN. + +##### A.2.2.1.3 Test Parameters + +Unless otherwise stated, refer to the test frequency and common test parameters for signalling conformance testing defined in TS 38.508-1 [6]. + +##### A.2.2.1.4 Test Description + +###### A.2.2.1.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.2.1.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.1.4.2-1. +2. Using the Application Client Simulator, generate traffic matching DNN value in Traffic descriptor in URSP rule provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI and DNN value are selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +6. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. + +Table A.2.2.1.4.2-1: MANAGE UE POLICY COMMAND (step 1) + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------------------------------------------|------------|----------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | | DNN Type | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| Route selection descriptor 2 | | | | +| Precedence value of route selection descriptor | 1 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000100'B | | DNN type | +| Route selection descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | | Match-all type | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | + +Table A.2.2.1.4.2-2: UL NAS Transport (step 3) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------------------------------------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +**Table A.2.2.1.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4)** + +| Information Element | Value/remark | Comment | Condition | +|----------------------------|--------------------------------------------------|------------|-----------| +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc APN ID Specific | | | + +#### A.2.2.2 5G NR / Mapping Application to Network Slicing / APP ID + +##### A.2.2.2.1 Definition + +The UE procedure for associating applications to PDU sessions based on URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.2.2.2.2 Test Purpose + +To verify that UE could support the mapping of applications to URSP rules and the establishment of PDU sessions based on the Traffic Descriptor of OS App Id. + +##### A.2.2.2.3 Test Parameters + +Unless otherwise stated, refer to the test frequency and common test parameters for signalling conformance testing defined in TS 38.508-1 [6]. + +##### A.2.2.2.4 Test Description + +###### A.2.2.2.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.2.2.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.2.4.2-1. +2. Using the Application Client Simulator, generate traffic matching OS App Id value in Traffic descriptor in URSP rule provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI is selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. + +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +6. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. + +**Table A.2.2.2.4.2-1: MANAGE UE POLICY COMMAND (step 1)** + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|---------------------------------------------------------|------------|----------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | | OS App Id type | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value ' in bytes | | | +| OS App Id value | pc_OS_App_ID | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | | Match-all type | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | + +**Table A.2.2.2.4.2-2: UL NAS Transport (step 3)** + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +**Table A.2.2.2.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4)** + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +#### A.2.2.3 5G NR / Mapping Application to Network Slicing / FQDN + +##### A.2.2.3.1 Definition + +The UE procedure for associating applications to PDU sessions based on URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.2.2.3.2 Test Purpose + +To verify that UE could support the mapping of applications to URSP rules and the establishment of PDU sessions based on the Traffic Descriptor of destination FQDN. + +##### A.2.2.3.3 Test Parameters + +Unless otherwise stated, refer to the test frequency and common test parameters for signalling conformance testing defined in TS 38.508-1 [6]. + +##### A.2.2.3.4 Test Description + +###### A.2.2.3.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration. + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.2.3.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.3.4.2-1. +2. Using the Application Client Simulator, generate traffic matching destination FQDN value in Traffic descriptor in URSP rule provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI is selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +6. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. + +Table A.2.2.3.4.2-1: MANAGE UE POLICY COMMAND (step 1) + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|---------------------------------------------------------------|------------|------------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10010001'B | | Destination FQDN | +| Traffic descriptor component | | | | +| destination FQDN length | Set to the actual length of 'destination FQDN value' in bytes | | | +| destination FQDN value | pc_Des_FQDN | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | | Match-all type | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | + +Table A.2.2.3.4.2-2: UL NAS Transport (step 3) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +Table A.2.2.3.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4) + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +#### A.2.2.4 5G NR / Mapping Application to Network Slicing / IP 3 Tuples + +##### A.2.2.4.1 Definition + +The UE procedure for associating applications to PDU sessions based on URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.2.2.4.2 Test Purpose + +To verify that UE could support the mapping of applications to URSP rules and the establishment of PDU sessions based on the Traffic Descriptor of IP 3 Tuples. + +##### A.2.2.4.3 Test Parameters + +Unless otherwise stated, refer to the test frequency and common test parameters for signalling conformance testing defined in TS 38.508-1 [6]. + +##### A.2.2.4.4 Test Description + +###### A.2.2.4.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.2.4.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.4.4.2-1. +2. Using the Application Client Simulator, generate traffic matching IP 3 tuples value in Traffic descriptor in URSP rule provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI is selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +6. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. + +Table A.2.2.4.4.2-1: MANAGE UE POLICY COMMAND (step 1) + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|-----------------------|------------|-----------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '01010010'B | | IP 3 tuple type | +| Traffic descriptor component | | | | +| Information Bitmap | '00001101'B | | IPv4 | +| | '00001110'B | | IPv6 | +| IP Address | pc_IP_Address | | | +| Protocol identifier/next header type | pc_Protocol_ID | | | +| Single remote port | pc_Sinlge_Remote_Port | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | | Match-all type | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | + +Table A.2.2.4.4.2-2: UL NAS Transport (step 3) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +Table A.2.2.4.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4) + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +#### A.2.2.5 5G NR / Mapping Application to Network Slicing / Connection Capabilities + +##### A.2.2.5.1 Definition + +The UE procedure for associating applications to PDU sessions based on URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.2.2.5.2 Test Purpose + +To verify that UE could support the mapping of applications to URSP rules and the establishment of PDU sessions based on the Traffic Descriptor of Connection Capabilities. + +##### A.2.2.5.3 Test Parameters + +Unless otherwise stated, refer to the test frequency and common test parameters for signalling conformance testing defined in TS 38.508-1 [6]. + +##### A.2.2.5.4 Test Description + +###### A.2.2.5.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.2.5.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.5.4.2-1. +2. Using the Application Client Simulator, generate data traffic. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI is selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +6. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. + +Table A.2.2.5.4.2-1: MANAGE UE POLICY COMMAND (step 1) + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------|------------------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10010000'B | Connection capabilities type | | +| Traffic descriptor component | | | | +| Connection capabilities | '00001000'B | Internet | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | Match-all type | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | + +Table A.2.2.5.4.2-2: UL NAS Transport (step 3) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +Table A.2.2.5.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4) + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | + +#### A.2.2.6 5G NR / Mapping Application to Network Slicing / URSP Update + +##### A.2.2.6.1 Definition + +The UE procedure for receiving and utilizing updated URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.2.2.6.2 Test Purpose + +To verify that UE could support the update of URSP rules and the mapping of applications to right network slicing based on the updated URSP rules. + +##### A.2.2.6.3 Test Parameters + +Unless otherwise stated, refer to the test frequency and common test parameters for signalling conformance testing defined in TS 38.508-1 [6]. + +##### A.2.2.6.4 Test Description + +###### A.2.2.6.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration. + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.2.2.6.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.1.4.2-1. +2. Using the Application Client Simulator, generate traffic matching DNN value in Traffic descriptor in URSP rule provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI and DNN value are selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +6. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. +7. The SS transmits a DL NAS TRANSPORT message including UE Policy Container and MANAGE UE POLICY COMMAND message to update URSP rules. +8. The UE transmits an UL NAS TRANSPORT message including a MANAGE UE POLICY COMPLETE message. +9. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI and DNN value are selected. +10. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. + +11. Observe that the data received in Application Server Simulator via PDU session is consistent with the data generated by Application Client Simulator. + +**Table A.2.2.6.4.2-1: UL NAS Transport (step 3)** + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------------------------------------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +**Table A.2.2.6.4.2-2: PDU SESSION ESTABLISHMENT ACCEPT (step 4, step 10)** + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------------------------------------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000001 | | step 4 | +| | 0x000003 | | step 19 | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +**Table A.2.2.6.4.2-3: MANAGE UE POLICY COMMAND (step 7)** + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------------------------------------------|------------|--------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | | DNN Type | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000003 | | | +| Route selection descriptor 2 | | | | +| Precedence value of route selection descriptor | 1 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000100'B | | DNN type | +| Route selection descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | + +| | | | | +|-----------|--------------------|--|--| +| DNN value | pc_APN_ID_Specific | | | +|-----------|--------------------|--|--| + +**Table A.2.2.6.4.2-4: UL NAS Transport (step 9)** + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------------------------------------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | 1 | | +| SD | 0x000003 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +## A.3 5G NR / Service Performance Testing with Network Slicing + +### A.3.1 5G NR / Service Performance / Single Network Slicing + +#### A.3.1.1 5G NR / Service Performance / Single Application with Single Network Slicing + +##### A.3.1.1.1 Definition + +The service performance of 5G NR UE with network slicing is determined by the UE operating system and communication unit. + +##### A.3.1.1.2 Test Purpose + +To measure the performance of single service in application layer of the 5G NR UE with single network slicing. + +##### A.3.1.1.3 Test Parameters + +The common test parameters are defined in TS 38.521-4 [12] Table 5.5.1.3-1. The parameters specified in TS 38.521-4 [12] Table 5.5.1.3-2 are applicable for tests on FDD bands and parameters specified in TS 38.521-4 [12] Table 5.5.1.3-3 are applicable for tests on TDD bands. + +Configurations of PUSCH and PUCCH are specified in TS 38.521-1 [13] Annex G. Configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2 for UL. + +Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 4.3.1.1. + +##### A.3.1.1.4 Test Description + +###### A.3.1.1.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration. + +Preamble: + +- The UE is in state Switched OFF (state ON-B) according to TS 38.508-1 [6]. + +###### A.3.1.1.4.2 Test Procedure + +1. UE is switched on. +2. Steps 2 to 15 of the generic procedure for NR RRC\_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed. +3. Using the Application Client Simulator, begin uplink data transfer. Wait for 15 seconds and then start to measure the throughput result and latency in [transport layer]. (This is iteration 1) Continue data transfer for 1 minutes. +4. Repeat step 3 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +5. Calculate and record the average application layer data throughput and latency across three iterations. +6. Switch off procedure in RRC\_IDLE specified in TS 38.508-1 subclause 4.9.6.1 is performed. +7. UE is brought back to operation. +8. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed except the MANAGE UE POLICY COMMAND message is defined in Table A.3.1.1.4.2-1. +9. Using the Application Client Simulator, generate traffic matching DNN value in Traffic descriptor in URSP rule provisioned to the UE in step 8. +10. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI and DNN value are selected. +11. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +12. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +13. Wait for 15 seconds and then start to measure the throughput result and latency in [transport layer] in parallel (This is iteration 1). Continue data transfer for 1 minute. +14. Repeat step 3 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +15. Calculate and record the average application layer data throughput and latency across three iterations. +16. Observe that the throughput in step 15 is not lower than the throughput benchmark in step 5 and the latency in step 15 is not higher than the latency benchmark in step 5. + +**Table A.3.1.1.4.2-1: MANAGE UE POLICY COMMAND (step 8)** + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------------------------------------------|------------|--------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | | DNN Type | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| Route selection descriptor 2 | | | | +| Precedence value of route selection descriptor | 1 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000100'B | | DNN type | +| Route selection descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +#### A.3.1.2 5G NR / Service Performance / Multiple Applications with Single Network Slicing + +##### A.3.1.2.1 Definition + +The service performance of 5G NR UE with network slicing is determined by the UE operating system and communication unit. + +##### A.3.1.2.2 Test Purpose + +To measure the performance of multiple services in application layer of the 5G NR UE with single network slicing. + +##### A.3.1.2.3 Test Parameters + +The common test parameters are defined in TS 38.521-4 [12] Table 5.5.1.3-1. The parameters specified in TS 38.521-4 [12] Table 5.5.1.3-2 are applicable for tests on FDD bands and parameters specified in TS 38.521-4 [12] Table 5.5.1.3-3 are applicable for tests on TDD bands. + +Configurations of PUSCH and PUCCH are specified in TS 38.521-1 [13] Annex G. For single APP A at step 5-8 configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2 with the exception of using half of the allocated resource block. For APP A and APP B running simultaneously at step 9-11 configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2. + +Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 4.3.1.1. + +##### A.3.1.2.4 Test Description + +###### A.3.1.2.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.3.1.2.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed except the MANAGE UE POLICY COMMAND message is defined in Table A.3.2.1.4.2-2. +2. Using the Application Client Simulator to simulate APP A, generate traffic matching DNN value in Traffic descriptor in URSP rule 1 provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI is selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the simulated APP A, begin uplink data transfer from UE to the Application Server Simulator. +6. Wait for 15 seconds and then start to measure the throughput result in application layer (This is iteration 1). Continue data transfer for 1 minute. +7. Repeat step 6 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +8. Calculate and record the average application layer data throughput across three iterations. +9. Using the Application Client Simulator to simulate APP B, generate traffic matching OS App Id value in Traffic descriptor in URSP rule 2 provisioned to the UE in step 1. +10. Using the simulated APP B, begin uplink data transfer from UE to the Application Server Simulator. +11. Repeat steps 6-8 to get the average application layer data throughput of the data traffic of simulated APP A. +12. Observe that the throughput in step 11 is not lower than the throughput benchmark in step 8. + +**Table A.3.1.2.4.2-1: MANAGE UE POLICY COMMAND (step 1)** + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------------------------------------------------|----------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | OS App Id type | | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value' in bytes | | | +| OS App Id value | pc_OS_App_ID | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | + +| | | | | +|------------------------------------------------|--------------------------------------------------------|----------------|--| +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | OS App Id type | | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value' in bytes | | | +| OS App Id value | pc_OS_App_ID_2nd | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 3 | | | | +| Precedence value of URSP rule | 2 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | Match-all type | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000002 | | | + +Table A.3.1.2.4.2-2: UL NAS Transport (step 3) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | 1 | | +| SD | 0x000001 | | | + +Table A.3.1.2.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4) + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | 1 | | +| SD | 0x000001 | | | + +### A.3.2 5G NR / Service Performance / Multiple Network Slicing + +#### A.3.2.1 5G NR / Service Performance / Multiple Applications with Multiple Network Slicing + +##### A.3.2.1.1 Definition + +The service performance of 5G NR UE with network slicing is determined by the UE operating system and communication unit. + +##### A.3.2.1.2 Test Purpose + +To measure the performance of multiple services in application layer of the 5G NR UE with multiple network slicing. + +##### A.3.2.1.3 Test Parameters + +The common test parameters are defined in TS 38.521-4 [12] Table 5.5.1.3-1. The parameters specified in TS 38.521-4 [12] Table 5.5.1.3-2 are applicable for tests on FDD bands and parameters specified in TS 38.521-4 [12] Table 5.5.1.3-3 are applicable for tests on TDD bands. + +Configurations of PUSCH and PUCCH are specified in TS 38.521-1 [13] Annex G. For single APP A or APP B at step 8-15 configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2 with the exception of using half of the allocated resource block. For APP A and APP B running simultaneously at step 16-19 configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2. + +Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 4.3.1.1. + +##### A.3.2.1.4 Test Description + +###### A.3.2.1.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.3.2.1.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed except the REGISTRATION ACCEPT message is defined in Table A.3.2.1.4.2-1 and MANAGE UE POLICY COMMAND message is defined in Table A.3.2.1.4.2-2. +2. Using the Application Client Simulator to simulate APP A, generate traffic matching DNN value in Traffic descriptor in URSP rule 1 provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI and DNN value are selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator to simulate APP B, generate traffic matching DNN value in Traffic descriptor in URSP rule 2 provisioned to the UE in step 1. + +6. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI and DNN value are selected. +7. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +8. Using the simulated APP A, begin uplink data transfer from UE to the Application Server Simulator. +9. Wait for 15 seconds and then start to measure the throughput result in application layer (This is iteration 1). Continue data transfer for 1 minute. +10. Repeat step 9 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +11. Calculate and record the average application layer data throughput across three iterations. +12. Stop the data transfer with simulated APP A. +13. Using the simulated APP B, begin uplink data transfer from UE to the Application Server Simulator. +14. Wait for 15 seconds and then start to measure the latency in application layer (This is iteration 1). Continue data transfer for 1 minute. +15. Repeat step 14 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +16. Calculate and record the average application layer latency across three iterations. +17. Restart the data traffic of APP A. APP A and APP B generate data traffic simultaneously. +18. Repeat steps 9 to 11 to get the average application layer data throughput of the data traffic of simulated APP A +19. Repeat steps 14 to 16 to get the average application layer latency of the data traffic of simulated APP B in parallel with step 18. +20. Observe that the throughput in step 18 is not lower than the throughput benchmark in step 11 and the latency in step 19 is not higher than the latency benchmark in step 16. + +**Table A.3.2.1.4.2-1: REGISTRATION ACCEPT (step 1)** + +| Derivation path: TS 38.508-1 Table 4.7.1-7 | | | | +|--------------------------------------------|--------------|-----------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| 5GS registration result value | '001'B | 3GPP access | | +| Allowed NSSAI | | | | +| S-NSSAI IEI | | S-NSSAI value 1 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | eMBB | | +| SD | 0x000001 | | | +| S-NSSAI IEI | | S-NSSAI value 2 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | URLLC | | +| SD | 0x000001 | | | +| S-NSSAI IEI | | default S-NSSAI | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000002 | | | +| Configured NSSAI | | | | +| S-NSSAI IEI | | S-NSSAI value 1 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | eMBB | | +| SD | 0x000001 | | | +| S-NSSAI IEI | | S-NSSAI value 2 | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | URLLC | | +| SD | 0x000001 | | | +| S-NSSAI IEI | | default S-NSSAI | | +| Length of S-NSSAI contents | '00000100'B | | | + +| | | | | +|-----|-------------|--|--| +| SST | '00000001'B | | | +| SD | 0x000002 | | | + +Table A.3.2.1.4.2-2: MANAGE UE POLICY COMMAND (step 1) + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------------------------------------------|----------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | DNN Type | | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | DNN Type | | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific_2nd | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | URLLC | | +| SD | 0x000001 | | | +| URSP rule 3 | | | | +| Precedence value of URSP rule | 2 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | Match-all type | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000002 | | | + +Table A.3.2.1.4.2-3: UL NAS Transport (step 3) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------------------------------------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | eMBB | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +Table A.3.2.1.4.2-4: PDU SESSION ESTABLISHMENT ACCEPT (step 4) + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------------------------------------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | eMBB | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | + +Table A.3.2.1.4.2-5: UL NAS Transport (step 6) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------------------------------------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-2 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | URLLC | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific 2nd | | | + +Table A.3.2.1.4.2-6: PDU SESSION ESTABLISHMENT ACCEPT (step 7) + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------------------------------------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | URLLC | | +| SD | 0x000001 | | | +| DNN | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific 2nd | | | + +### A.3.3 5G NR / Service Performance / URSP Update + +#### A.3.3.1 5G NR / Service Performance / Single Network Slicing / URSP update + +##### A.3.3.1.1 Definition + +The UE procedure for receiving and utilizing updated URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.3.3.1.2 Test Purpose + +To measure the performance of single services in application layer of the 5G NR UE with the change of network slicing. + +##### A.3.3.1.3 Test Parameters + +The common test parameters are defined in TS 38.521-4 [12] Table 5.5.1.3-1. The parameters specified in TS 38.521-4 [12] Table 5.5.1.3-2 are applicable for tests on FDD bands and parameters specified in TS 38.521-4 [12] Table 5.5.1.3-3 are applicable for tests on TDD bands. + +Configurations of PUSCH and PUCCH are specified in TS 38.521-1 [13] Annex G. Configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2 with the exception of using half of the allocated resource block for step 5-7. For APP A and APP B running simultaneously at step 16-19 configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2 for step 12-13. + +Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 4.3.1.1. + +##### A.3.3.1.4 Test Description + +###### A.3.3.1.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration. + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.3.3.1.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed, except the MANAGE UE POLICY COMMAND message is defined in Table A.2.2.2.4.2-1. +2. Using the Application Client Simulator, generate traffic matching OS App Id in Traffic descriptor in URSP rule provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI value is selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +5. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. + +6. Wait for 15 seconds and then start to measure the throughput result in transport layer (This is iteration 1). Continue data transfer for 1 minute. +7. Repeat step 6 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +8. Calculate and record the average application layer data throughput across three iterations. +9. The SS transmits a DL NAS TRANSPORT message including UE Policy Container and MANAGE UE POLICY COMMAND message to update URSP rules. +10. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI is selected. +11. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +12. Using the Application Client Simulator, begin uplink data transfer from UE to the Application Server Simulator. +13. Repeat steps 6-8 to get the average application layer data throughput of the data traffic of simulated APP A. +14. Observe that the throughput in step 13 is not lower than the throughput benchmark in step 8. + +**Table A.3.3.1.4.2-1: UL NAS Transport (step 3, 10)** + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | step 3 | +| | 0x000003 | | step 10 | + +**Table A.3.3.1.4.2-2: PDU SESSION ESTABLISHMENT ACCEPT (step 4, step 11)** + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | step 4 | +| | 0x000003 | | step 11 | + +**Table A.3.3.1.4.2-3: MANAGE UE POLICY COMMAND (step 9)** + +| Derivation Path: Table 5.2.4-1 | | | | +|------------------------------------------------|--------------------------------------------------|---------|--------------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10001000'B | | DNN Type | +| Traffic descriptor component | | | | +| DNN length | Set to the actual length of 'DNN value' in bytes | | | +| DNN value | pc_APN_ID_Specific | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | | S-NSSAI type | + +| | | | | +|--------------------------------------|-------------|------------|--| +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000003 | | | + +#### A.3.3.2 5G NR / Service Performance / Multiple Network Slicing / URSP update + +##### A.3.3.2.1 Definition + +The UE procedure for receiving and utilizing updated URSP rules is one of the fundamental functional requirements for network slicing. + +##### A.3.3.2.2 Test Purpose + +To measure the performance of multiple services in application layer of the 5G NR UE with the change of network slicing. + +##### A.3.3.2.3 Test Parameters + +The common test parameters are defined in TS 38.521-4 [12] Table 5.5.1.3-1. The parameters specified in TS 38.521-4 [12] Table 5.5.1.3-2 are applicable for tests on FDD bands and parameters specified in TS 38.521-4 [12] Table 5.5.1.3-3 are applicable for tests on TDD bands. + +Configurations of PUSCH and PUCCH are specified in TS 38.521-1 [13] Annex G. Configure the TBsize, UL RMC, PDCP size from TS 38.521-4 [12] Annex A.2 for UL. + +Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 4.3.1.1. + +##### A.3.3.2.4 Test Description + +###### A.3.3.2.4.1 Initial Conditions + +System Simulator: + +- NGC Cell A is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [6]. + +UE: + +- Empty URSP Configuration. + +Preamble: + +- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [6]. + +###### A.3.2.2.4.2 Test Procedure + +1. Steps 1 to 6 of the test procedure specified in subclause A.2.1.1.4.2 are performed except the REGISTRATION ACCEPT message is defined in Table A.3.2.1.4.2-1 and MANAGE UE POLICY COMMAND message is defined in Table A.3.2.2.4.2-1. +2. Using the Application Client Simulator to simulate APP A, generate traffic matching OS App Id value in Traffic descriptor in URSP rule 1 provisioned to the UE in step 1. +3. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI value are selected. +4. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. + +5. Using the Application Client Simulator to simulate APP B, generate traffic matching OS App Id value in Traffic descriptor in URSP rule 2 provisioned to the UE in step 1. +6. The UE transmits an UL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT REQUEST message. Observe the right S-NSSAI value are selected. +7. The SS transmits a DL NAS TRANSPORT message and PDU SESSION ESTABLISHMENT ACCEPT message. +8. Using the simulated APP A and APP B, begin uplink data transfer from UE to the Application Server Simulator. +9. Wait for 15 seconds and then start to measure the throughput result of simulated APP A and latency result of simulated APP B in application layer (This is iteration 1). Continue data transfer for 1 minute. +10. Repeat step 6 for 3 iterations within the same call as the first iteration. Wait for at least 5 seconds between each iteration of the data transfer. +11. Calculate and record the average application layer data throughput of simulated APP A and latency of simulated APP B across three iterations. +12. The SS transmits a DL NAS TRANSPORT message including UE Policy Container and MANAGE UE POLICY COMMAND message to update URSP rules. +13. Repeat step 2-4 with the message exception defined in Table A.3.2.2.4.2-5 and A.3.2.2.4.2-6 +14. Repeat step 5-7 with the message exception defined in Table A.3.2.2.4.2-5 and A.3.2.2.4.2-6 +15. Repeat step 8-11 to get the average application layer data throughput of simulated APP A and latency of simulated APP B in parahell. +16. Observe that the throughput in step 15 is not lower than the throughput benchmark in step 11 and the latency in step 15 is not higher than the latency benchmark in step 11. + +**Table A.3.2.2.4.2-1: MANAGE UE POLICY COMMAND (step 1)** + +| Derivation Path: Table 5.2.4-1 | | | | +|----------------------------------------------|---------------------------------------------------------|----------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | OS App Id type | | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value ' in bytes | | | +| OS App Id value | pc OS App ID | | | + +| | | | | +|------------------------------------------------|--------------------------------------------------------|----------------|--| +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | OS App Id type | | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value' in bytes | | | +| OS App Id value | pc OS App ID 2nd | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000010'B | | | +| SD | 0x000001 | | | +| URSP rule 3 | | | | +| Precedence value of URSP rule | 2 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '00000001'B | Match-all type | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000002 | | | + +Table A.3.2.2.4.2-2: UL NAS Transport (step 3, step 6) + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | step 3 | +| | '00000010'B | | step 6 | +| SD | 0x000001 | | | + +**Table A.3.2.2.4.2-3: PDU SESSION ESTABLISHMENT ACCEPT (step 4, step 7)** + +| Information Element | Value/remark | Comment | Condition | +|----------------------------|--------------|------------|-----------| +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | step 4 | +| | '00000010'B | | step 7 | +| SD | 0x000001 | | | + +**Table A.3.2.2.4.2-4: MANAGE UE POLICY COMMAND (step 12)** + +| Information Element | Value/remark | Comment | Condition | +|------------------------------------------------|--------------------------------------------------------|----------------|-----------| +| UE policy part | | | | +| URSP rule 1 | | | | +| Precedence value of URSP rule | 0 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | OS App Id type | | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value' in bytes | | | +| OS App Id value | pc_OS_App_ID | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000002 | | | +| URSP rule 2 | | | | +| Precedence value of URSP rule | 1 | | | +| Traffic descriptor | | | | +| Traffic descriptor component type identifier | '10100000'B | OS App Id type | | +| Traffic descriptor component | | | | +| OS App Id length | Set to the actual length of 'OS App Id value' in bytes | | | +| OS App Id value | pc_OS_App_ID_2nd | | | +| Route selection descriptor list | | | | +| Route selection descriptor 1 | | | | +| Precedence value of route selection descriptor | 0 | | | +| Route selection descriptor contents | | | | +| Route selection descriptor component type | '00000010'B | S-NSSAI type | | +| Route selection descriptor component | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | | + +**Table A.3.2.2.4.2-5: UL NAS Transport (step 13, step 14)** + +| Derivation path: TS 38.508-1 [4], Table 4.7.1-10 | | | | +|--------------------------------------------------|--------------|-------------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| Payload container type | '0001'B | N1 SM information | | +| PDU session ID | PSI-1 | | | +| Request type | '001'B | Initial request | | +| S-NSSAI | Not Present | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | step 13 | +| | 0x000002 | | step 14 | + +**Table A.3.2.2.4.2-6: PDU SESSION ESTABLISHMENT ACCEPT (step 13, step 14)** + +| Derivation path: TS 38.508-1 clause 4.7.2-2 | | | | +|---------------------------------------------|--------------|------------|-----------| +| Information Element | Value/remark | Comment | Condition | +| S-NSSAI | | | | +| Length of S-NSSAI contents | '00000100'B | SST and SD | | +| SST | '00000001'B | | | +| SD | 0x000001 | | step 13 | +| | 0x000002 | | step 14 | + +# --- Annex B: Applicability + +Void + +# Annex C: Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|----------|-----------|------|-----|-------------------------------------------------------------------------------------|--------| +| 2021-05 | RAN5#91e | R5-213433 | - | - | Draft skeleton | 0.1.0 | +| 2021-05 | RAN5#91e | R5-213433 | - | - | Text Proposal for TR 38.918 on Definition of Full Stack Testing for Network Slicing | 0.1.0 | +| 2021-05 | RAN5#91e | R5-213434 | - | - | Text Proposal for TR 38.918 on Test Equipment | 0.1.0 | +| 2021-05 | RAN5#91e | R5-213435 | - | - | Text Proposal for TR 38.918 on Test Equipment Connection Diagrams | 0.1.0 | +| 2021-08 | RAN5#92e | R5-216352 | - | - | Text Proposal on Test Configuration | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215247 | - | - | Text Proposal on Application Simulation | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215248 | - | - | Text Proposal on Analysis of mapping application to network slicing | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215249 | - | - | Text Proposal on Test Procedure A.2.1.1 | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215250 | - | - | Text Proposal on Test Procedure A.2.2.1 | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215251 | - | - | Text Proposal to Update References | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215252 | - | - | Editorial changes on wording | 0.2.0 | +| 2021-08 | RAN5#92e | R5-215283 | - | - | Text Proposal on Test Procedure A.3.1.1 | 0.2.0 | +| 2021-11 | RAN5#93e | R5-217264 | - | - | Text Proposal on Test Procedure A.2.2.2 | 0.3.0 | +| 2021-11 | RAN5#93e | R5-217265 | - | - | Text Proposal to Update Message Contents | 0.3.0 | +| 2021-11 | RAN5#93e | R5-217266 | - | - | Text Proposal to Update Network Slicing Configurations | 0.3.0 | +| 2021-11 | RAN5#93e | R5-217267 | - | - | Editorial changes on wording | 0.3.0 | +| 2022-03 | RAN5#94e | R5-220177 | - | - | Text Proposal on Test Procedure A.2.2.3 | 0.4.0 | +| 2022-03 | RAN5#94e | R5-220178 | - | - | Text Proposal on Test Procedure A.2.2.4 | 0.4.0 | +| 2022-03 | RAN5#94e | R5-220179 | - | - | Updates to Test Configurations | 0.4.0 | +| 2022-03 | RAN5#94e | R5-220180 | - | - | Updates to message contents in A.2.1.1 | 0.4.0 | +| 2022-03 | RAN5#94e | R5-220181 | - | - | Addition of default URSP rule to Test Procedure A.2.2.1 | 0.4.0 | +| 2022-03 | RAN5#94e | R5-220182 | - | - | Addition of default URSP rule to Test Procedure A.2.2.2 | 0.4.0 | +| 2022-03 | RAN5#94e | R5-221035 | - | - | Text Proposal to update 5.4.2 and 5.4.3 | 0.4.0 | +| 2022-05 | RAN5#95e | R5-222860 | - | - | Updates to Test Configurations | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222861 | - | - | Updates to Uncertainty and TT Analysis | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222862 | - | - | Updates to References | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222863 | - | - | Updates to Test Model | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222864 | - | - | Updates to Test Parameters | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222865 | - | - | Text Proposal on Test Procedure A.2.2.5 | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222866 | - | - | Text Proposal on Test Procedure A.2.2.6 | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222867 | - | - | Text Proposal on Test Procedure A.3.1.2 | 0.5.0 | +| 2022-05 | RAN5#95e | R5-222868 | - | - | Text Proposal on Test Procedure A.3.2.1 | 0.5.0 | +| 2022-06 | RAN5#96 | RP-221383 | - | - | Presentation of Specification/Report to TSG: TR 38.918 Version 1.0.0 | 1.0.0 | +| 2022-06 | RAN5#96 | - | - | - | upgrade to v18.0.0 with editorial changes | 18.0.0 | +| 2022-09 | RAN5#97 | R5-225017 | 0001 | - | Updates to TR 38.918 | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/45_series/45004/011fecb4a85637472f0c697a6cbdb15d_img.jpg b/marked/Rel-18/45_series/45004/011fecb4a85637472f0c697a6cbdb15d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67ab540239ba41ff861935cfa19e8deafd88ffef --- /dev/null +++ b/marked/Rel-18/45_series/45004/011fecb4a85637472f0c697a6cbdb15d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cb9a439c0636457037bdc3ef2dbc97a21c436a8708720ce9112e0a02259509c +size 18901 diff --git a/marked/Rel-18/45_series/45004/0f3e3ea50bcceb86f6c524ab2b6f3e7a_img.jpg b/marked/Rel-18/45_series/45004/0f3e3ea50bcceb86f6c524ab2b6f3e7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9375d56e503934f15c2ccab7354dacf51b81d986 --- /dev/null +++ b/marked/Rel-18/45_series/45004/0f3e3ea50bcceb86f6c524ab2b6f3e7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b8f612d24a6f032fba170e7b25973ce90fbb1afe16e069a97918fa6aaeb6931 +size 16418 diff --git a/marked/Rel-18/45_series/45004/573c8f9e728e343b6864e1070c14b8cf_img.jpg b/marked/Rel-18/45_series/45004/573c8f9e728e343b6864e1070c14b8cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f59eeba04d377f3064ebfd7b1fabcfae2202ef --- /dev/null +++ b/marked/Rel-18/45_series/45004/573c8f9e728e343b6864e1070c14b8cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2664f24095acf3868a7df66f19143cf978cb4fb06a028530953a68c71942230 +size 34798 diff --git a/marked/Rel-18/45_series/45004/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/45_series/45004/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ece0d2f7d78cbe6f1473430d497932ea370e473 --- /dev/null +++ b/marked/Rel-18/45_series/45004/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:024abd160be6d6d53ad8ea7e0d9a5cbf54c73675d583267f33d1a064c4584329 +size 8053 diff --git a/marked/Rel-18/45_series/45004/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/45_series/45004/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22fb09324b1c2436894f41ebcba9a213f4b835ff --- /dev/null +++ b/marked/Rel-18/45_series/45004/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2398b461d6c04d4d15ea87da69a3198ed8ea1d12f47f392d04a1cfba34aa96b +size 14890 diff --git a/marked/Rel-18/45_series/45004/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-18/45_series/45004/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d18312db88cb09bdb128eaef15c0da405951f17 --- /dev/null +++ b/marked/Rel-18/45_series/45004/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8064009665bbdfcb9156d37fbb71b77ce8938aacc846f76256fdbc3c9dc7e6c +size 33212 diff --git a/marked/Rel-18/45_series/45004/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-18/45_series/45004/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..964df9a64a7fc20c7ffd9f1100a44f242e75b934 --- /dev/null +++ b/marked/Rel-18/45_series/45004/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dba5e872187cd3c68eefacbcb650a0d2e66fa579dd7bfcf2fc9a0b3190b0cf1 +size 34522 diff --git a/marked/Rel-18/45_series/45004/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-18/45_series/45004/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be6de36845436094c29c23c870109849194bf29f --- /dev/null +++ b/marked/Rel-18/45_series/45004/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df97b283b4e8a2611f73dcfb669e612df75b3b9b4db05187e3b08f405e6ad02f +size 26457 diff --git a/marked/Rel-18/45_series/45004/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/45_series/45004/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0b0c750aeecb2328172bdb46216b2f1e89cef86 --- /dev/null +++ b/marked/Rel-18/45_series/45004/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86e34aafd1205292e251a63d6704453bbafb3d410cd8a115ff528d742f93161e +size 23318 diff --git a/marked/Rel-18/45_series/45004/raw.md b/marked/Rel-18/45_series/45004/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b15faf5a249fbec0fbf6542a26282f8773ecf85e --- /dev/null +++ b/marked/Rel-18/45_series/45004/raw.md @@ -0,0 +1,685 @@ + + +# 3GPP TS 45.004 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; GSM/EDGE Modulation (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +The GSM logo consists of the letters 'GSM' in a stylized blue font. The 'G' and 'S' are connected at the top by a single horizontal bar. The 'M' is composed of two 'A'-like shapes joined at the top. Below the letters, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller, blue, sans-serif font. A registered trademark symbol (®) is located to the right of the 'M'. + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +The 3GPP logo features the text '3GPP' in a bold, black, sans-serif font. The '3' is stylized with a red signal wave icon at its base. The 'G', 'P', and 'P' are in a standard font. A trademark symbol (™) is located to the upper right of the 'P'. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +GSM, radio, Modulation + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|----------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 1.1 References..... | 5 | +| 1.2 Abbreviations ..... | 5 | +| 2 Modulation format for GMSK ..... | 5 | +| 2.1 Modulating symbol rate ..... | 5 | +| 2.2 Start and stop of the burst..... | 6 | +| 2.3 Differential encoding..... | 6 | +| 2.4 Filtering ..... | 6 | +| 2.5 Output phase..... | 7 | +| 2.6 Modulation ..... | 7 | +| 2.7 Overlaid CDMA..... | 8 | +| 3 Modulation format for 8PSK ..... | 8 | +| 3.1 Modulating symbol rate ..... | 8 | +| 3.2 Symbol mapping ..... | 8 | +| 3.3 Start and stop of the burst..... | 9 | +| 3.4 Symbol rotation ..... | 10 | +| 3.5 Pulse shaping..... | 10 | +| 3.6 Modulation ..... | 10 | +| 4 Modulation format for 16QAM and 32QAM at the normal symbol rate ..... | 11 | +| 4.1 Modulating symbol rate ..... | 11 | +| 4.2 Symbol mapping ..... | 11 | +| 4.3 Start and stop of the burst..... | 12 | +| 4.4 Symbol rotation ..... | 13 | +| 4.5 Pulse shaping..... | 13 | +| 4.6 Modulation ..... | 13 | +| 5 Modulation format for QPSK, 16QAM and 32QAM at the higher symbol rate ..... | 13 | +| 5.1 Modulating symbol rate ..... | 13 | +| 5.2 Symbol mapping ..... | 14 | +| 5.3 Start and stop of the burst..... | 14 | +| 5.4 Symbol rotation ..... | 14 | +| 5.5 Pulse shaping..... | 14 | +| 5.6 Modulation ..... | 15 | +| 6 Modulation format for AQPSK..... | 15 | +| 6.1 Modulating symbol rate ..... | 15 | +| 6.2 Symbol mapping ..... | 15 | +| 6.3 Start and stop of the burst..... | 16 | +| 6.4 Symbol rotation ..... | 17 | +| 6.5 Pulse shaping..... | 17 | +| 6.6 Modulation ..... | 17 | +| Annex A (normative): Tx filter coefficients for the spectrally wide pulse shape ..... | 18 | +| Annex B (informative): Change history ..... | 19 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The modulator receives the bits from the encryption unit, see 3GPP TS 45.001, and produces an RF signal. The filtering of the Radio Frequency (RF) signal necessary to obtain the spectral purity is not defined, neither are the tolerances associated with the theoretical filter requirements specified. These are contained in 3GPP TS 45.005. + +## --- 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 45.001: "Physical Layer on the Radio Path (General Description)". +- [3] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [4] 3GPP TS 45.005: "Radio transmission and reception". +- [5] 3GPP TS 45.010: "Radio subsystem synchronization". +- [6] 3GPP TS 44.060: "Radio Link Control/ Medium Access Control (RLC/MAC) protocol". +- [7] 3GPP TS 43.064: "General Packet Radio Service (GPRS)". +- [8] 3GPP TS 45.003: "Channel Coding". + +## --- 1.2 Abbreviations + +Abbreviations used in this specification are listed in 3GPP TR 21.905. In addition to abbreviations in 3GPP TR 21.905 the following abbreviation apply: + +| | | +|-------|----------------------------------------| +| AQPSK | Adaptive Quadrature Phase Shift Keying | +| EC | Extended Coverage | +| ESAB | Extended Synchronization Access Burst | + +# --- 2 Modulation format for GMSK + +## 2.1 Modulating symbol rate + +The modulating symbol rate is the normal symbol rate which is defined as $1/T = 1\,625/6$ ksymb/s (i.e. approximately 270.833 ksymb/s), which corresponds to 1 625/6 kbit/s (i.e. 270.833 kbit/s). T is the normal symbol period (see 3GPP TS 45.010). + +## 2.2 Start and stop of the burst + +Before the first bit of the bursts as defined in 3GPP TS 45.002 enters the modulator, the modulator has an internal state as if a modulating bit stream consisting of consecutive ones ( $d_i = 1$ ) had entered the differential encoder. Also after the last bit of the time slot, the modulator has an internal state as if a modulating bit stream consisting of consecutive ones ( $d_i = 1$ ) had continued to enter the differential encoder. These bits are called dummy bits and define the start and the stop of the active and the useful part of the burst as illustrated in figure 1. Nothing is specified about the actual phase of the modulator output signal outside the useful part of the burst. In case of EC operation, the phase during the useful part of contiguous bursts, belonging to the same blind physical layer transmissions within a TDMA frame, has a fixed relation, see subclauses 2.6 and 2.7. + +![Figure 1: Relation between active part of burst, tail bits and dummy bits. The diagram shows a sequence of bits: dummy bits (.....111111), 3 tail bits (000.....), a large block of 'Output phase' containing 'The useful part' and 'The active part', 3 tail bits (.....000), and dummy bits (111111.....). The 'active part' is the innermost section, and 'The useful part' is a slightly larger section containing the active part. Arrows indicate the start and end of these parts, with '1/2 bit' markers at the boundaries.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) + +The diagram illustrates the structure of a burst. It shows a sequence of bits: dummy bits (.....111111), 3 tail bits (000.....), a large block of 'Output phase' containing 'The useful part' and 'The active part', 3 tail bits (.....000), and dummy bits (111111.....). The 'active part' is the innermost section, and 'The useful part' is a slightly larger section containing the active part. Arrows indicate the start and end of these parts, with '1/2 bit' markers at the boundaries. + +Figure 1: Relation between active part of burst, tail bits and dummy bits. The diagram shows a sequence of bits: dummy bits (.....111111), 3 tail bits (000.....), a large block of 'Output phase' containing 'The useful part' and 'The active part', 3 tail bits (.....000), and dummy bits (111111.....). The 'active part' is the innermost section, and 'The useful part' is a slightly larger section containing the active part. Arrows indicate the start and end of these parts, with '1/2 bit' markers at the boundaries. + +**Figure 1: Relation between active part of burst, tail bits and dummy bits. For the normal burst the useful part lasts for 147 modulating bits.** + +## 2.3 Differential encoding + +Each data value $d_i = [0, 1]$ is differentially encoded. The output of the differential encoder is: + +$$\hat{d}_i = d_i \oplus d_{i-1} \quad (d_i \in \{0, 1\})$$ + +where $\oplus$ denotes modulo 2 addition. + +The modulating data value $\alpha_i$ input to the modulator is: + +$$\alpha_i = 1 - 2\hat{d}_i \quad (\alpha_i \in \{-1, +1\})$$ + +## 2.4 Filtering + +The modulating data values $\alpha_i$ as represented by Dirac pulses excite a linear filter with impulse response defined by: + +$$g(t) = h(t) * rect\left(\frac{t}{T}\right)$$ + +where the function $rect(x)$ is defined by: + +$$rect\left(\frac{t}{T}\right) = \frac{1}{T} \quad \text{for } |t| < \frac{T}{2}$$ + +$$\text{rect}\left(\frac{t}{T}\right) = 0 \quad \text{otherwise}$$ + +and \* means convolution. $h(t)$ is defined by: + +$$h(t) = \frac{\exp\left(\frac{-t^2}{2\delta^2 T^2}\right)}{\sqrt{(2\pi)} \cdot \delta T}$$ + +where + +$$\delta = \frac{\sqrt{\ln(2)}}{2\pi BT} \quad \text{and } BT = 0.3$$ + +where B is the 3 dB bandwidth of the filter with impulse response $h(t)$ . This theoretical filter is associated with tolerances defined in 3GPP TS 45.005. + +## 2.5 Output phase + +The phase of the modulated signal is: + +$$\varphi(t') = \sum_i \alpha_i \pi h \int_{-\infty}^{t'-iT} g(u) du$$ + +where the modulating index $h$ is 1/2 (maximum phase change in radians is $\pi/2$ per data interval). + +The time reference $t' = 0$ is the start of the active part of the burst as shown in figure 1. This is also the start of the bit period of bit number 0 (the first tail bit) as defined in 3GPP TS 45.002. + +## 2.6 Modulation + +The modulated RF carrier, except for start and stop of the TDMA burst, or ESAB (see 3GPP TS 45.002 [3]) may therefore be expressed as: + +$$x(t') = \sqrt{\frac{2E_c}{T}} \cdot \cos(2\pi f_0 t' + \varphi(t') + \varphi_0)$$ + +where $E_c$ is the energy per modulating bit, $f_0$ is the centre frequency and $\varphi_0$ is a random phase and is constant during one burst or ESAB (see 3GPP TS 45.002 [3]). + +In case of EC operation when using blind physical layer transmissions (see 3GPP TS 43.064 [7]), the modulated RF carrier, except for start and stop of the burst, may, for each blind physical layer transmission of a burst for which phase and amplitude coherency is required (see 3GPP TS 45.005 [4]), be expressed as: + +$$x(t') = \sqrt{\frac{2E_c}{T}} \cdot \cos(2\pi f_0 (t' + t_0) + \varphi(t') + \varphi_{157} + \varphi_0)$$ + +where + +- $t_0$ is a burst-specific time offset, constant during one burst, and is defined as the time difference between the start of the active part (time instant $t' = 0$ ) of the current burst and the start of the active part ( $t' = 0$ ) of the first transmission of the same burst in the current TDMA frame. +- $\varphi_{157}$ is a phase shift of either 0 or $\pi h$ , and is constant during one burst. + +- $\varphi_0$ is a random phase and is constant during all blind physical layer transmissions of the same burst within the same TDMA frame. + +For EC-GSM-IoT, only integer timeslot lengths are allowed (see 3GPP TS 45.010 [5]). If any blind physical layer transmission is transmitted in the uplink on timeslot 0 or timeslot 4, which are 157 symbols long, all following blind physical layer transmissions of the same burst in that TDMA frame shall be shifted in phase by $\pi h$ , i.e. $\varphi_{157} = \pi h$ , otherwise $\varphi_{157} = 0$ . For the downlink this phase shift shall not be applied, i.e. $\varphi_{157} = 0$ . + +## 2.7 Overlaid CDMA + +In the case of Overlaid CDMA, the modulated RF carrier may be expressed with an additional term compared to subclause 2.6 representing the Overlaid CDMA code: + +$$x(t') = \sqrt{\frac{2E_c}{T}} \cdot \cos(2\pi f_0(t'+t_0) + \varphi(t') + \varphi_{157} + \varphi_0 + OC \cdot \pi)$$ + +where $OC$ equals 0 or 1 in accordance with the applied Overlaid CDMA code (see 3GPP TS 45.002 [3]) and is constant during one burst. For each blind physical layer transmission within a TDMA frame, $OC$ equals its respective Overlaid CDMA code element. For example for Overlaid CDMA code sequence '0011', $OC$ equals 0 for the first two blind physical layer transmissions and 1 for the last two blind physical layer transmissions within a TDMA frame. + +NOTE: If the blind physical layer transmissions within a TDMA frame are continuously modulated, a phase shift of $\pi$ for bursts with $OC=1$ can be well approximated by inverting all the data values $d_i$ (cf. subclause 2.3), i.e. replacing their data values by $1-d_i$ , including three to five guard bits preceding and following the tail bits, respectively. + +# 3 Modulation format for 8PSK + +## 3.1 Modulating symbol rate + +The modulating symbol rate is the normal symbol rate which is defined as $1/T = 1\,625/6$ ksymb/s (i.e. approximately 270.833 ksymb/s), which corresponds to $3 \cdot 1\,625/6$ kbit/s (i.e. 812.5 kbit/s). $T$ is the normal symbol period (see 3GPP TS 45.010). + +## 3.2 Symbol mapping + +The modulating bits are Gray mapped in groups of three to 8PSK symbols by the rule + +$$s_i = e^{j2\pi l/8}$$ + +where $l$ is given by table 1. + +Table 1: Mapping between modulating bits and the 8PSK symbol parameter $l$ . + +| Modulating bits
$d_{3i}, d_{3i+1}, d_{3i+2}$ | Symbol parameter $l$ | +|-------------------------------------------------|----------------------| +| (1,1,1) | 0 | +| (0,1,1) | 1 | +| (0,1,0) | 2 | +| (0,0,0) | 3 | +| (0,0,1) | 4 | +| (1,0,1) | 5 | +| (1,0,0) | 6 | +| (1,1,0) | 7 | + +This is illustrated in figure 2. + +![Figure 2: Symbol mapping of modulating bits into 8PSK symbols. A circular diagram showing 8 points on a circle in the I-Q plane. The points are labeled with bit triplets (d_{3i}, d_{3i+1}, d_{3i+2}) and their corresponding symbol parameters l. The points are: (1,1,1) at 0 degrees (right), (0,1,1) at 45 degrees, (0,1,0) at 90 degrees (top), (0,0,0) at 135 degrees, (0,0,1) at 180 degrees (left), (1,0,1) at 225 degrees, (1,0,0) at 270 degrees (bottom), and (1,1,0) at 315 degrees.](0f3e3ea50bcceb86f6c524ab2b6f3e7a_img.jpg) + +Figure 2: Symbol mapping of modulating bits into 8PSK symbols. A circular diagram showing 8 points on a circle in the I-Q plane. The points are labeled with bit triplets (d\_{3i}, d\_{3i+1}, d\_{3i+2}) and their corresponding symbol parameters l. The points are: (1,1,1) at 0 degrees (right), (0,1,1) at 45 degrees, (0,1,0) at 90 degrees (top), (0,0,0) at 135 degrees, (0,0,1) at 180 degrees (left), (1,0,1) at 225 degrees, (1,0,0) at 270 degrees (bottom), and (1,1,0) at 315 degrees. + +Figure 2: Symbol mapping of modulating bits into 8PSK symbols. + +## 3.3 Start and stop of the burst + +Before the first bit of the bursts as defined in 3GPP TS 45.002 enters the modulator, the state of the modulator is undefined. Also after the last bit of the burst, the state of the modulator is undefined. The tail bits (see 3GPP TS 45.002) define the start and the stop of the active and the useful part of the burst as illustrated in figure 3. Nothing is specified about the actual phase of the modulator output signal outside the useful part of the burst. + +![Figure 3: Relation between active part of burst and tail bits. A diagram showing the structure of a burst. It consists of three horizontal layers: 'Output phase' at the top, 'The useful part' in the middle, and 'The active part' at the bottom. The 'Output phase' layer contains '9 tail bits' at both ends, represented by the sequence '111 111 111.....' at the start and '.....111 111 111' at the end. The 'The useful part' layer is a long horizontal bar. The 'The active part' layer is also a long horizontal bar, slightly shorter than the useful part. On the left and right sides, there are arrows indicating a '1/2 symbol' offset between the start/stop of the active part and the start/stop of the useful part.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +Figure 3: Relation between active part of burst and tail bits. A diagram showing the structure of a burst. It consists of three horizontal layers: 'Output phase' at the top, 'The useful part' in the middle, and 'The active part' at the bottom. The 'Output phase' layer contains '9 tail bits' at both ends, represented by the sequence '111 111 111.....' at the start and '.....111 111 111' at the end. The 'The useful part' layer is a long horizontal bar. The 'The active part' layer is also a long horizontal bar, slightly shorter than the useful part. On the left and right sides, there are arrows indicating a '1/2 symbol' offset between the start/stop of the active part and the start/stop of the useful part. + +Figure 3: Relation between active part of burst and tail bits. For the normal burst the useful part lasts for 147 modulating symbols + +## 3.4 Symbol rotation + +The 8PSK symbols are continuously rotated with $3\pi/8$ radians per symbol before pulse shaping. The rotated symbols are defined as + +$$\hat{s}_i = s_i \cdot e^{j3\pi/8}$$ + +## 3.5 Pulse shaping + +The modulating 8PSK symbols $\hat{s}_i$ as represented by Dirac pulses excite a linear pulse shaping filter. This filter is a linearised GMSK pulse, i.e. the main component in a Laurent decomposition of the GMSK modulation. The impulse response is defined by: + +$$c_0(t) = \begin{cases} \prod_{i=0}^3 S(t+iT), \text{ for } 0 \leq t \leq 5T \\ 0, \text{ else} \end{cases}$$ + +where + +$$S(t) = \begin{cases} \sin(\pi \int_0^t g(t') dt'), \text{ for } 0 \leq t \leq 4T \\ \sin(\frac{\pi}{2} - \pi \int_0^{t-4T} g(t') dt'), \text{ for } 4T < t \leq 8T \\ 0, \text{ else} \end{cases}$$ + +$$g(t) = \frac{1}{2T} \left( Q\left(2\pi \cdot 0.3 \frac{t-5T/2}{T\sqrt{\log_e(2)}}\right) - Q\left(2\pi \cdot 0.3 \frac{t-3T/2}{T\sqrt{\log_e(2)}}\right) \right)$$ + +and + +$$Q(t) = \frac{1}{\sqrt{2\pi}} \int_t^\infty e^{-\frac{\tau^2}{2}} d\tau.$$ + +The base band signal is + +$$y(t') = \sum_i \hat{s}_i \cdot c_0(t'-iT + 2T)$$ + +The time reference $t' = 0$ is the start of the active part of the burst as shown in figure 3. This is also the start of the symbol period of symbol number 0 (containing the first tail bit) as defined in 3GPP TS 45.002. + +## 3.6 Modulation + +The modulated RF carrier during the useful part of the burst is therefore: + +$$x(t') = \sqrt{\frac{2E_s}{T}} \operatorname{Re}[y(t') \cdot e^{j(2\pi f_0 t' + \phi_0)}]$$ + +where $E_s$ is the energy per modulating symbol, $f_0$ is the centre frequency and $\phi_0$ is a random phase and is constant during one burst. + +# 4 Modulation format for 16QAM and 32QAM at the normal symbol rate + +## 4.1 Modulating symbol rate + +The modulating symbol rate is the normal symbol rate which is defined as $1/T = 1625/6$ ksymb/s (i.e. approximately 270.833 ksymb/s), which corresponds to $4 \cdot 1625/6$ kbit/s (i.e. approximately 1083.3 kbit/s) for 16QAM and to $5 \cdot 1625/6$ kbit/s (i.e. approximately 1354.2 kbit/s) for 32QAM. $T$ is the normal symbol period (see 3GPP TS 45.010). + +## 4.2 Symbol mapping + +The modulating bits are mapped to symbols according to Table 2 for 16QAM and Table 3 for 32QAM. + +**Table 2: Mapping between modulating bits and 16QAM symbols.** + +| Modulating bits
$d_{4i}, d_{4i+1}, d_{4i+2}, d_{4i+3}$ | 16QAM symbol
$s_i$ | | +|-----------------------------------------------------------|-----------------------|----------------| +| | I | Q | +| (0,0,0,0) | $1/\sqrt{10}$ | $1/\sqrt{10}$ | +| (0,0,0,1) | $1/\sqrt{10}$ | $3/\sqrt{10}$ | +| (0,0,1,0) | $3/\sqrt{10}$ | $1/\sqrt{10}$ | +| (0,0,1,1) | $3/\sqrt{10}$ | $3/\sqrt{10}$ | +| (0,1,0,0) | $1/\sqrt{10}$ | $-1/\sqrt{10}$ | +| (0,1,0,1) | $1/\sqrt{10}$ | $-3/\sqrt{10}$ | +| (0,1,1,0) | $3/\sqrt{10}$ | $-1/\sqrt{10}$ | +| (0,1,1,1) | $3/\sqrt{10}$ | $-3/\sqrt{10}$ | +| (1,0,0,0) | $-1/\sqrt{10}$ | $1/\sqrt{10}$ | +| (1,0,0,1) | $-1/\sqrt{10}$ | $3/\sqrt{10}$ | +| (1,0,1,0) | $-3/\sqrt{10}$ | $1/\sqrt{10}$ | +| (1,0,1,1) | $-3/\sqrt{10}$ | $3/\sqrt{10}$ | +| (1,1,0,0) | $-1/\sqrt{10}$ | $-1/\sqrt{10}$ | +| (1,1,0,1) | $-1/\sqrt{10}$ | $-3/\sqrt{10}$ | +| (1,1,1,0) | $-3/\sqrt{10}$ | $-1/\sqrt{10}$ | +| (1,1,1,1) | $-3/\sqrt{10}$ | $-3/\sqrt{10}$ | + +Table 3: Mapping between modulating bits and 32QAM symbols. + +| Modulating bits
$d_{5i}, d_{5i+1}, d_{5i+2}, d_{5i+3}, d_{5i+4}$ | 32QAM symbol
$s_i$ | | +|---------------------------------------------------------------------|-----------------------|----------------| +| | I | Q | +| (0,0,0,0,0) | $-3/\sqrt{20}$ | $-5/\sqrt{20}$ | +| (0,0,0,0,1) | $-1/\sqrt{20}$ | $-5/\sqrt{20}$ | +| (0,0,0,1,0) | $-3/\sqrt{20}$ | $5/\sqrt{20}$ | +| (0,0,0,1,1) | $-1/\sqrt{20}$ | $5/\sqrt{20}$ | +| (0,0,1,0,0) | $-5/\sqrt{20}$ | $-3/\sqrt{20}$ | +| (0,0,1,0,1) | $-5/\sqrt{20}$ | $-1/\sqrt{20}$ | +| (0,0,1,1,0) | $-5/\sqrt{20}$ | $3/\sqrt{20}$ | +| (0,0,1,1,1) | $-5/\sqrt{20}$ | $1/\sqrt{20}$ | +| (0,1,0,0,0) | $-1/\sqrt{20}$ | $-3/\sqrt{20}$ | +| (0,1,0,0,1) | $-1/\sqrt{20}$ | $-1/\sqrt{20}$ | +| (0,1,0,1,0) | $-1/\sqrt{20}$ | $3/\sqrt{20}$ | +| (0,1,0,1,1) | $-1/\sqrt{20}$ | $1/\sqrt{20}$ | +| (0,1,1,0,0) | $-3/\sqrt{20}$ | $-3/\sqrt{20}$ | +| (0,1,1,0,1) | $-3/\sqrt{20}$ | $-1/\sqrt{20}$ | +| (0,1,1,1,0) | $-3/\sqrt{20}$ | $3/\sqrt{20}$ | +| (0,1,1,1,1) | $-3/\sqrt{20}$ | $1/\sqrt{20}$ | +| (1,0,0,0,0) | $3/\sqrt{20}$ | $-5/\sqrt{20}$ | +| (1,0,0,0,1) | $1/\sqrt{20}$ | $-5/\sqrt{20}$ | +| (1,0,0,1,0) | $3/\sqrt{20}$ | $5/\sqrt{20}$ | +| (1,0,0,1,1) | $1/\sqrt{20}$ | $5/\sqrt{20}$ | +| (1,0,1,0,0) | $5/\sqrt{20}$ | $-3/\sqrt{20}$ | +| (1,0,1,0,1) | $5/\sqrt{20}$ | $-1/\sqrt{20}$ | +| (1,0,1,1,0) | $5/\sqrt{20}$ | $3/\sqrt{20}$ | +| (1,0,1,1,1) | $5/\sqrt{20}$ | $1/\sqrt{20}$ | +| (1,1,0,0,0) | $1/\sqrt{20}$ | $-3/\sqrt{20}$ | +| (1,1,0,0,1) | $1/\sqrt{20}$ | $-1/\sqrt{20}$ | +| (1,1,0,1,0) | $1/\sqrt{20}$ | $3/\sqrt{20}$ | +| (1,1,0,1,1) | $1/\sqrt{20}$ | $1/\sqrt{20}$ | +| (1,1,1,0,0) | $3/\sqrt{20}$ | $-3/\sqrt{20}$ | +| (1,1,1,0,1) | $3/\sqrt{20}$ | $-1/\sqrt{20}$ | +| (1,1,1,1,0) | $3/\sqrt{20}$ | $3/\sqrt{20}$ | +| (1,1,1,1,1) | $3/\sqrt{20}$ | $1/\sqrt{20}$ | + +## 4.3 Start and stop of the burst + +Before the first bit of the bursts as defined in 3GPP TS 45.002 enters the modulator, the state of the modulator is undefined. Also after the last bit of the burst, the state of the modulator is undefined. The tail symbols (see 3GPP TS 45.002) define the start and the stop of the active and the useful part of the burst as illustrated in figure 4. Nothing is specified about the actual phase of the modulator output signal outside the useful part of the burst. + +![Figure 4: Relation between active part of burst and tail symbols. The diagram shows a sequence of symbols s0, s1, s2, ..., s145, s146, s147. The first three symbols (s0, s1, s2) and the last three symbols (s145, s146, s147) are labeled as '3 tail symbols'. The symbols between them are labeled as 'The useful part'. The entire sequence from s0 to s147 is labeled as 'The active part'. Vertical lines at the beginning and end of the sequence indicate a '1/2 symbol' offset from the start and end of the active part respectively. A horizontal line labeled 'Output phase' is shown above the symbols.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 4: Relation between active part of burst and tail symbols. The diagram shows a sequence of symbols s0, s1, s2, ..., s145, s146, s147. The first three symbols (s0, s1, s2) and the last three symbols (s145, s146, s147) are labeled as '3 tail symbols'. The symbols between them are labeled as 'The useful part'. The entire sequence from s0 to s147 is labeled as 'The active part'. Vertical lines at the beginning and end of the sequence indicate a '1/2 symbol' offset from the start and end of the active part respectively. A horizontal line labeled 'Output phase' is shown above the symbols. + +Figure 4: Relation between active part of burst and tail symbols. For the normal burst the useful part lasts for 147 modulating symbols. + +## 4.4 Symbol rotation + +The symbols are continuously rotated with $\varphi$ radians per symbol before pulse shaping, where $\varphi = \pi/4$ and $-\pi/4$ for 16QAM and 32QAM respectively. The rotated symbols are defined as + +$$\hat{s}_i = s_i \cdot e^{j i \varphi}$$ + +## 4.5 Pulse shaping + +The modulating symbols $\hat{s}_i$ as represented by Dirac pulses excite a linear pulse shaping filter. This filter is the linearised GMSK pulse as defined in 3.5. + +## 4.6 Modulation + +The modulated RF carrier during the useful part of the burst is: + +$$x(t') = \sqrt{\frac{2E_s}{T}} \operatorname{Re}[y(t') \cdot e^{j(2\pi f_0 t' + \varphi_0)}]$$ + +where $y(t')$ is the base band signal (see 3.5), $E_s$ is the energy per modulating symbol, $f_0$ is the centre frequency and $\varphi_0$ is a random phase and is constant during one burst. + +# 5 Modulation format for QPSK, 16QAM and 32QAM at the higher symbol rate + +## 5.1 Modulating symbol rate + +The modulating symbol rate is the higher symbol rate which is defined as $1/T = 325$ ksymb/s, which corresponds to 650 kbit/s for QPSK, to 1300 kbit/s for 16QAM and to 1625 kbit/s for 32QAM. $T$ is the reduced symbol period (see 3GPP TS 45.010). + +## 5.2 Symbol mapping + +The modulating bits are mapped to symbols according to Table 4 for QPSK, Table 2 for 16QAM and Table 3 for 32QAM.. + +**Table 4: Mapping between modulating bits and QPSK symbols.** + +| Modulating bits
$d_{2i}, d_{2i+1}$ | QPSK symbol
$s_i$ | | +|---------------------------------------|----------------------|---------------| +| | I | Q | +| (0,0) | $1/\sqrt{2}$ | $1/\sqrt{2}$ | +| (0,1) | $1/\sqrt{2}$ | $-1/\sqrt{2}$ | +| (1,0) | $-1/\sqrt{2}$ | $1/\sqrt{2}$ | +| (1,1) | $-1/\sqrt{2}$ | $-1/\sqrt{2}$ | + +## 5.3 Start and stop of the burst + +Before the first bit of the bursts as defined in 3GPP TS 45.002 enters the modulator, the state of the modulator is undefined. Also after the last bit of the burst, the state of the modulator is undefined. The tail symbols (see 3GPP TS 45.002) define the start and the stop of the active and the useful part of the burst as illustrated in figure 5. Nothing is specified about the actual phase of the modulator output signal outside the useful part of the burst. + +![Figure 5: Relation between active part of burst and tail symbols. The diagram shows a horizontal timeline of symbols. On the left, there are 4 tail symbols labeled s0, s1, s2, s3, followed by an ellipsis. On the right, there are 4 tail symbols labeled s173, s174, s175, s176, preceded by an ellipsis. The symbols between the ellipses represent the 'useful part'. The 'active part' is indicated by a double-headed arrow spanning from the start of the useful part to the end of the useful part. The 'output phase' is indicated by a double-headed arrow spanning the entire burst from s0 to s176. Vertical lines mark the start and end of the burst. Horizontal arrows at the ends indicate a 1/2 symbol offset from the start and end of the active part to the start and end of the burst.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +Figure 5: Relation between active part of burst and tail symbols. The diagram shows a horizontal timeline of symbols. On the left, there are 4 tail symbols labeled s0, s1, s2, s3, followed by an ellipsis. On the right, there are 4 tail symbols labeled s173, s174, s175, s176, preceded by an ellipsis. The symbols between the ellipses represent the 'useful part'. The 'active part' is indicated by a double-headed arrow spanning from the start of the useful part to the end of the useful part. The 'output phase' is indicated by a double-headed arrow spanning the entire burst from s0 to s176. Vertical lines mark the start and end of the burst. Horizontal arrows at the ends indicate a 1/2 symbol offset from the start and end of the active part to the start and end of the burst. + +Figure 5: Relation between active part of burst and tail symbols. For the higher symbol rate burst (see 3GPP TS 45.001) the useful part lasts for 176 modulating symbols. + +## 5.4 Symbol rotation + +The symbols are continuously rotated with $\phi$ radians per symbol before pulse shaping, where $\phi = 3\pi/4, \pi/4$ and $-\pi/4$ for QPSK, 16QAM and 32QAM respectively. The rotated symbols are defined as + +$$\hat{s}_i = s_i \cdot e^{ji\phi}$$ + +## 5.5 Pulse shaping + +The modulating symbols $\hat{s}_i$ as represented by Dirac pulses excite one of the following linear pulse shaping filters: + +- A spectrally wide pulse shape $c'(t)$ , where $c'(t)$ is the continuous time representation of a discrete time pulse shape $c_n = c'((n-1)T_s)$ , which is defined in Annex A, where $T_s$ is the sampling period which for the purpose of the pulse shape definition, is $T/16$ , and $n = 1, 2, \dots, 97$ . + +The base band signal is + +$$y(t') = \sum_i \hat{s}_i \cdot c'(t' - iT + 2.5T)$$ + +NOTE: A closed-form expression of $c'(t)$ is not available because the spectrally wide pulse shape was numerically optimised based on a set of discrete filter coefficients. The continuous time function can be obtained by: + +- low-pass filtering the discrete time function with a pass-band of 400 kHz and a stop-band beginning at 2600 kHz and; +- truncating the duration to the time interval $[0, 6T]$ . + +An example for such a low-pass filter is a raised cosine filter with the impulse response + +$$r(t) = \text{si}(2\pi t \cdot 2600 \text{ kHz}) \cdot \cos(2\pi t \cdot 2200 \text{ kHz}) / (1 - (4 t \cdot 2200 \text{ kHz})^2)$$ + +with $\text{si}(x) = \sin(x)/x$ , + +$$\text{resulting in } c'(t) = \sum_{n=1}^{97} c_n r(t - (n-1)T_s) \text{ for } 0 \leq t \leq 6T \text{ and } c'(t) = 0 \text{ for } t < 0 \text{ or } t > 6T.$$ + +- A spectrally narrow pulse shape, $c_0(t)$ , which is the linearised GMSK pulse as defined in subclause 3.5 for the normal symbol period. + +NOTE: The linearised GMSK pulse is not scaled to the reduced symbol period. Hence its duration in terms of the reduced symbol period is $6T$ . + +The base band signal is + +$$y(t') = \sum_i \hat{s}_i \cdot c_0(t' - iT + 2.5T)$$ + +The time reference $t' = 0$ is the start of the active part of the burst as shown in figure 3. This is also the start of the symbol period of symbol number 0 (containing the first tail bit) as defined in 3GPP TS 45.002. + +For the uplink, the pulse shape that shall be used when transmitting a burst is dependent on the parameter 'Pulse format' that is sent during assignment (see 3GPP TS 44.060). For the downlink the spectrally narrow pulse shape shall be used. + +## 5.6 Modulation + +The modulated RF carrier during the useful part of the burst is: + +$$x(t') = \sqrt{\frac{2E_s}{T}} \text{Re}[y(t') \cdot e^{j(2\pi f_0 t' + \phi_0)}]$$ + +where $E_s$ is the energy per modulating symbol, $f_0$ is the centre frequency and $\phi_0$ is a random phase and is constant during one burst. + +# 6 Modulation format for AQPSK + +## 6.1 Modulating symbol rate + +The modulating symbol rate is the normal symbol rate which is defined as $1/T = 1\,625/6$ ksymb/s (i.e. approximately 270,833 ksymb/s), which corresponds to $2 \cdot 1\,625/6$ kbit/s (i.e. 541,666 kbit/s). $T$ is the normal symbol period (see 3GPP TS 45.010). + +## 6.2 Symbol mapping + +The modulating bits are mapped to the quaternary symbols according to Table 5. + +**Table 5: Mapping between modulating bits and quaternary symbols.** + +| Modulating bits for
$a_i, b_i$ | AQPSK symbol in polar notation
$s_i$ | +|-----------------------------------|-----------------------------------------| +| (0,0) | $e^{j\alpha}$ | +| (0,1) | $e^{-j\alpha}$ | +| (1,0) | $-e^{-j\alpha}$ | +| (1,1) | $-e^{j\alpha}$ | + +This is illustrated in Figure 5. + +![Figure 5: Mapping of modulating bits to AQPSK symbols. A constellation diagram on a circle in the complex plane with axes I (horizontal) and Q (vertical). Four points are marked: (0,0) at angle alpha from the I-axis, (0,1) at angle -alpha from the I-axis, (1,0) at angle 180-alpha from the I-axis, and (1,1) at angle 180+alpha from the I-axis. The angle alpha is also indicated between the Q-axis and the lines to (0,0) and (1,0).](011fecb4a85637472f0c697a6cbdb15d_img.jpg) + +Figure 5: Mapping of modulating bits to AQPSK symbols. A constellation diagram on a circle in the complex plane with axes I (horizontal) and Q (vertical). Four points are marked: (0,0) at angle alpha from the I-axis, (0,1) at angle -alpha from the I-axis, (1,0) at angle 180-alpha from the I-axis, and (1,1) at angle 180+alpha from the I-axis. The angle alpha is also indicated between the Q-axis and the lines to (0,0) and (1,0). + +**Figure 5: Mapping of modulating bits to AQPSK symbols** + +The ratio of power between the Q and I channels is defined as the Subchannel Power Imbalance Ratio (SCPIR). + +The value of the SCPIR is given by + +$$SCPIR = 20 \times \log_{10}(\tan(\alpha)) \text{ dB}.$$ + +The value of $\alpha$ shall be chosen such that $|SCPIR| \leq 10 \text{ dB}$ . + +## 6.3 Start and stop of the burst + +Before the first bit of the burst as defined in 3GPP TS 45.002 enters the modulator, the state of the modulator is undefined. Also after the last bit of the burst, the state of the modulator is undefined. The tail symbols (see 3GPP TS 45.002) define the start and the stop of the active and the useful part of the burst as illustrated in Figure 6. Nothing is specified about the actual phase of the modulator output signal outside the useful part of the burst. + +![Figure 6: Relation between active part of burst and tail symbols. The diagram shows a burst structure with '6 tail bits' at both ends, represented as '00 00 00 .....'. The 'Output phase' is the top section. Below it is 'The useful part', which is flanked by '1/2 symbol' on each side. The bottom section is 'The active part', which is also flanked by '1/2 symbol' on each side. The '1/2 symbol' labels are positioned between the 'Output phase' and 'The useful part' on the left and right sides.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 6: Relation between active part of burst and tail symbols. The diagram shows a burst structure with '6 tail bits' at both ends, represented as '00 00 00 .....'. The 'Output phase' is the top section. Below it is 'The useful part', which is flanked by '1/2 symbol' on each side. The bottom section is 'The active part', which is also flanked by '1/2 symbol' on each side. The '1/2 symbol' labels are positioned between the 'Output phase' and 'The useful part' on the left and right sides. + +**Figure 6: Relation between active part of burst and tail symbols. For the normal burst (see 3GPP TS 45.001) the useful part lasts for 147 modulating symbols.** + +## 6.4 Symbol rotation + +The symbols are continuously rotated with $\phi$ radians per symbol before pulse shaping, where $\phi = \pi/2$ . The rotated symbols are defined as + +$$\hat{s}_i = s_i \cdot e^{j i \phi}$$ + +## 6.5 Pulse shaping + +The modulating symbols $\hat{s}_i$ as represented by Dirac pulses excite the following linear pulse shaping filter: + +- $c_0(t)$ , which is the linearised GMSK pulse as defined in subclause 3.5 for the normal symbol period. + +The base band signal is + +$$y(t') = \sum_i \hat{s}_i \cdot c_0(t' - iT + 2T)$$ + +The time reference $t' = 0$ is the start of the active part of the burst as shown in figure 6. This is also the start of the symbol period of symbol number 0 (containing the first tail bit) as defined in 3GPP TS 45.002. + +## 6.6 Modulation + +The modulated RF carrier during the useful part of the burst is: + +$$x(t') = \sqrt{\frac{2E_s}{T}} \operatorname{Re} \left[ y(t') \cdot e^{j(2\pi f_0 t' + \phi_0)} \right]$$ + +where $E_s$ is the energy per modulating symbol, $f_0$ is the centre frequency and $\phi_0$ is a random phase and is constant during one burst. + +# --- Annex A (normative): Tx filter coefficients for the spectrally wide pulse shape + +For an oversampling factor of 16, i.e. 5200 ksamples/s, there are 97 Tx filter coefficients $c_1$ to $c_{97}$ for the spectrally wide pulse shape. The coefficients are symmetric to $c_{49}$ , i.e. $c_{49-k} = c_{49+k}$ . The coefficients of $c_1$ to $c_{49}$ are listed: + +0.00225918460000 +0.00419757900000 +0.00648420700000 +0.00931957020000 +0.01259397500000 +0.01605878900000 +0.01959156100000 +0.02292214900000 +0.02570190500000 +0.02767928100000 +0.02852115300000 +0.02791904300000 +0.02568913000000 +0.02166792700000 +0.01579963100000 +0.00821077000000 +-0.00089211394000 +-0.01114601700000 +-0.02201830600000 +-0.03289439200000 +-0.04302811700000 +-0.05156392200000 +-0.05764086800000 +-0.06034025400000 +-0.05876224400000 +-0.05209962100000 +-0.03961692000000 +-0.02072323500000 +0.00496039200000 +0.03765364500000 +0.07732192300000 +0.12369249000000 +0.17639444000000 +0.23478700000000 +0.29768326000000 +0.36418213000000 +0.43311409000000 +0.50316152000000 +0.57298225000000 +0.64120681000000 +0.70645485000000 +0.76744762000000 +0.82295721000000 +0.87187027000000 +0.91325439000000 +0.94628290000000 +0.97030623000000 +0.98493838000000 +0.99006899000000 + +# Annex B (informative): Change history + +| SMG | SPEC | VERS | NEW_VE | PHA | SUBJECT | +|------|--------|-------|--------|-------|-----------------------------------------------------------| +| S27 | 05.04 | 5.0.1 | 6.0.0 | R97 | Conversion to Release 97 EN | +| S28 | 05.04 | 6.0.0 | 8.0.0 | R99 | Introduction of 8PSK for EDGE | +| S30b | 05.04 | 8.0.0 | 8.1.0 | R99 | Correction of mistake for range alpha-sub-i in Clause 2.3 | +| | | 8.1.0 | 8.1.1 | | Figure 3 replaced (as it was corrupted) | +| G03 | 05.04 | 8.1.1 | 8.2.0 | R99 | Correction of symbol period notation | +| G04 | 45.004 | 8.2.0 | 4.0.0 | Rel-4 | New version for Release 4 | +| G05 | 45.004 | 4.0.0 | 4.1.0 | Rel-4 | Correction of Timing Alignment for GMSK and 8-PSK Signals | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2001-11 | 07 | GP-012359 | 002 | | Correction of tail bits for 8PSK normal burst | 4.1.0 | 4.2.0 | +| 2001-11 | 07 | GP-012372 | 004 | | Correction of references to relevant 3GPP TSs | 4.1.0 | 4.2.0 | +| 2001-11 | 07 | GP-012360 | 003 | | Correction of tail bits for 8PSK normal burst | 4.2.0 | 5.0.0 | +| 2002-06 | 10 | GP-021436 | 005 | | Corrections and clean up | 5.0.0 | 5.1.0 | +| 2003-09 | | | | | Correction of wrong Release number in the front page | 5.1.0 | 5.1.1 | +| 2005-01 | 23 | | | | Version for Release 6 | 5.1.1 | 6.0.0 | +| 2007-08 | 35 | GP-071544 | 0006 | 2 | Introduction of QPSK, 16QAM and 32QAM for RED HOT and HUGE | 6.0.0 | 7.0.0 | +| 2007-11 | 36 | GP-072015 | 0008 | | Spectrally wide pulse shape for HUGE B | 7.0.0 | 7.1.0 | +| 2008-02 | 37 | GP-080105 | 0009 | | Spectrally wide pulse shape for HUGE B | 7.1.0 | 7.2.0 | +| 2008-08 | 39 | GP-081068 | 0010 | | Correction of modulating bit rate for 32QAM at the higher symbol rate | 7.2.0 | 7.3.0 | +| 2008-12 | 40 | | | | Version for Release 8 | 7.3.0 | 8.0.0 | +| 2009-12 | 44 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 2010-05 | 46 | GP-101048 | 0017 | 1 | Introduction of VAMOS modulation | 9.0.0 | 9.1.0 | +| 2011-03 | 49 | | | | Version for Release 10 | 9.1.0 | 10.0.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 2014-09 | 63 | | | | Version for Release 12 (frozen at SP-65) | 11.0.0 | 12.0.0 | +| 2015-12 | 68 | | | | Version for Release 13 (frozen at SP-70) | 12.0.0 | 13.0.0 | +| 2016-02 | 69 | GP-160178 | 0020 | 5 | Introduction of EC-EGPRS | 13.0.0 | 13.1.0 | +| 2016-02 | 69 | GP-160195 | 0023 | | Corrections to Overlaid CDMA | 13.0.0 | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-05 | 70 | GP-160286 | 0024 | - | F | Clarifications and miscellaneous corrections to EC-GSM-IoT (including name change) | 13.2.0 | +| 2016-09 | 73 | RP-161392 | 0025 | 2 | F | Corrections to EC-GSM-IoT | 13.3.0 | +| 2016-12 | 74 | RP-162070 | 0026 | 1 | F | Correction to Overlaid CDMA realisation | 13.4.0 | +| 2017-03 | 75 | | | | | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2017-06 | 76 | RP-170924 | 0027 | 2 | B | Introduction of ESAB | 14.1.0 | +| 2018-06 | 80 | | | | | Release 15 version (frozen at TSG-80) | 15.0.0 | +| 2019-03 | 83 | RP-190061 | 0028 | - | F | Correction to Overlaid CDMA requirements for EC-GSM-IoT | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/45_series/45009/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-18/45_series/45009/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3158ecb078cf144a72975a5f601560777903a26 --- /dev/null +++ b/marked/Rel-18/45_series/45009/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:590ad9803a1a82d6cde7fa3e894bd6aadb8a7f66d4c37805ed88e8948e1ba5cb +size 44899 diff --git a/marked/Rel-18/45_series/45009/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/45_series/45009/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..050a4e3cf153138bc9b9265d2b534903dd05afd9 --- /dev/null +++ b/marked/Rel-18/45_series/45009/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:525cd511b7275dfc1f24137e86bee90b32cc42d6e7a056a1a8569a8ace587431 +size 8101 diff --git a/marked/Rel-18/45_series/45009/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/45_series/45009/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22fb09324b1c2436894f41ebcba9a213f4b835ff --- /dev/null +++ b/marked/Rel-18/45_series/45009/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2398b461d6c04d4d15ea87da69a3198ed8ea1d12f47f392d04a1cfba34aa96b +size 14890 diff --git a/marked/Rel-18/45_series/45009/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/45_series/45009/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f0aa35d54d378571f9f4c56f8e4048e6cb9c958 --- /dev/null +++ b/marked/Rel-18/45_series/45009/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b84db87de893f923e790ff96ddb9289e9ceef772f9844729af700fe580ad06a +size 84528 diff --git a/marked/Rel-18/45_series/45009/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-18/45_series/45009/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1489508c35164785e65b016aa874be5b4cb85d43 --- /dev/null +++ b/marked/Rel-18/45_series/45009/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:034df0864945e119373913a6f39ddabc78bfa84b40956594d3fda57b86726359 +size 60819 diff --git a/marked/Rel-18/45_series/45009/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-18/45_series/45009/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06614a9b7471074c569817247a0d4376779a4b0c --- /dev/null +++ b/marked/Rel-18/45_series/45009/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b66dd4090401eb98b07775317e427013dbabc74c04e7445a1f9f8a0f39d0d396 +size 72907 diff --git a/marked/Rel-18/45_series/45009/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-18/45_series/45009/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36794b073cf32bd342ae5558e603f9edd3f092cb --- /dev/null +++ b/marked/Rel-18/45_series/45009/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8fc35966497ba01b4b169f2c249a0744fc1d32e723ac8b0fe593f109c795d4e +size 71042 diff --git a/marked/Rel-18/45_series/45009/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-18/45_series/45009/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f5899b0b3e55de43001c9d120ac4240a9b06eb6 --- /dev/null +++ b/marked/Rel-18/45_series/45009/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f4ae926d4e9fe30c09c47c555819e2bb1610b35978e173bbed84c3a2c86238d +size 61619 diff --git a/marked/Rel-18/45_series/45009/raw.md b/marked/Rel-18/45_series/45009/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b9c70ad1d3bef6fc61ce08fa0e3e1cc8ecba4df8 --- /dev/null +++ b/marked/Rel-18/45_series/45009/raw.md @@ -0,0 +1,863 @@ + + +# 3GPP TS 45.009 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; GSM/EDGE Link adaptation (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, radio + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 1.1 References ..... | 5 | +| 1.2 Abbreviations ..... | 5 | +| 2 General..... | 5 | +| 3 Adaptive Multi-Rate inband control and link adaptation..... | 6 | +| 3.1 General operation ..... | 6 | +| 3.1.1 Operation without Tandem Free Operation..... | 6 | +| 3.1.2 Operation with ongoing Tandem Free Operation..... | 7 | +| 3.1.3 Operation at handover with ongoing Tandem Free Operation..... | 7 | +| 3.2 Inband Signalling ..... | 7 | +| 3.2.1 Frequent inband signalling for AMR codec mode adaptation..... | 8 | +| 3.2.1.1 General aspects ..... | 8 | +| 3.2.1.2 Operation with DTX enabled..... | 8 | +| 3.2.1.3 Transmitter/Receiver Synchronisation ..... | 8 | +| 3.2.2 Robust inband signalling for AMR configuration modification ..... | 9 | +| 3.2.2.1 General aspects ..... | 9 | +| 3.2.2.2 RATSCCH protocol..... | 10 | +| 3.2.2.3 RATSCCH messages..... | 11 | +| 3.2.2.3.1 ACK_OK message ..... | 11 | +| 3.2.2.3.2 ACK_ERR message ..... | 11 | +| 3.2.2.3.3 ACK_UNKNOWN message..... | 11 | +| 3.2.2.3.4 CMI_PHASE_REQ message ..... | 12 | +| 3.2.2.3.5 AMR_CONFIG_REQ message ..... | 12 | +| 3.2.2.3.6 THRESH_REQ message..... | 13 | +| 3.3 Codec mode adaptation ..... | 13 | +| 3.3.1 Channel quality measure ..... | 13 | +| 3.3.2 Generation of Codec Mode Commands and Requests ..... | 14 | +| 3.3.3 Performance requirements..... | 14 | +| 3.3.3.1 MS response to the Codec Mode Command ..... | 14 | +| 3.3.3.2 BTS response to the Codec Mode Request..... | 14 | +| 3.3.3.3 Performance of the Codec Mode Request Generation..... | 15 | +| 3.4 Setup procedures ..... | 15 | +| 3.4.1 Definition of the AMR Active Codec Set ..... | 15 | +| 3.4.2 Definition of Codec Mode Command/Request decision thresholds ..... | 15 | +| 3.4.3 Initial Codec Mode Selection at Call Setup and Handover ..... | 17 | +| Annex A (informative): Example Solution for Link quality estimation ..... | 18 | +| Annex B (informative): Example Definition of Mode Command/Request decision thresholds ..... | 19 | +| Annex C (informative): Principles for AMR codec mode adaptation with TFO ..... | 21 | +| C.1 Downgrading..... | 21 | +| C.1.1 Uplink downgrading..... | 21 | +| C.1.2 Downlink downgrading..... | 22 | +| C.2 Upgrading..... | 23 | +| C.2.1 Downlink upgrading..... | 23 | +| C.2.2 Uplink upgrading..... | 24 | +| Annex D (informative): Change history..... | 25 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 8.x.y + +where: + +- 8 indicates release 1999. +- x the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- y the third digit is incremented when editorial only changes have been incorporated in the specification. + +# --- 1 Scope + +The requirements described in the present document are mandatory for implementation in all GSM MSs and BSSs capable of supporting the Adaptive Multi-Rate speech traffic channel, unless otherwise stated. + +Unless otherwise specified, references to GSM include GSM at any frequency band. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 44.018: "Mobile radio interface layer 3 specification, Radio Resource Control Protocol". +- [3] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [4] 3GPP TS 45.003: "Channel Coding". +- [5] 3GPP TS 45.005: "Radio transmission and reception". +- [6] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface, Layer 3 specification". +- [7] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of Speech Codecs". + +## 1.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply. Further GSM related abbreviations are listed in 3GPP TR 21.905. + +| | | +|---------|-------------------------------------------------| +| AMR | Adaptive Multi-Rate | +| AMR-WB | Adaptive Multi-Rate Wideband | +| ACS | Active Codec Set | +| CMC | Codec Mode Command | +| CMI | Codec Mode Indication | +| CMR | Codec Mode Request | +| ICM | Initial Codec Mode | +| RATSCCH | Robust AMR Traffic Synchronized Control Channel | + +# --- 2 General + +The present document gives the detailed requirements for the correct operation of in call service specific link adaptation and control for GSM services implemented in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s. + +In this specification the term AMR refers to both narrow-band and wide-band AMR codecs if not otherwise stated. + +For the Adaptive Multi-Rate (AMR) speech service, the detailed description and requirements for the associated inband signaling, AMR codec mode adaptation, and AMR codec configuration are given. + +An inband signalling channel is defined for AMR which enables the MS and the BTS to exchange messages on applied or requested speech and channel codec modes. Codec mode adaptation for AMR is based on received channel quality estimation in both MS and BTS, followed by a decision on the most appropriate speech and channel codec mode to apply at a given time. + +The overall operation of AMR, in terms of used codec modes as well as general adaptation behaviour is controlled by the network. + +# --- 3 Adaptive Multi-Rate inband control and link adaptation + +## 3.1 General operation + +### 3.1.1 Operation without Tandem Free Operation + +A high-level block diagram of the complete AMR system is depicted in figure 1. The system consists of the major components TRAÜ and BTS on the network side and the MS. On the network side, speech encoder (SPE) and channel encoder (CHE) as well as channel decoder (CHD) and speech decoder (SPD) are connected via the serial A-bis interface. For each link, quality information is derived by estimating the current channel state. Based on the channel state, and also taking into consideration possible constraints from network control, the codec mode control, which is located on the network side, selects the codec modes to be applied. + +The channel mode to use (TCH/AFS, TCH/AHS, O-TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS) is controlled by the network. Uplink and downlink always apply the same channel mode. + +For codec mode adaptation the receiving side performs link quality measurements of the incoming link. The measurements are processed yielding a Quality Indicator. For uplink adaptation, the Quality Indicator is directly fed into the UL mode control unit. This unit compares the Quality Indicator with certain thresholds and generates, also considering possible constraints from network control, a Codec Mode Command indicating the codec mode to be used on the uplink. The Codec Mode Command is then transmitted inband to the mobile side where the incoming speech signal is encoded in the corresponding codec mode. For downlink adaptation, the DL Mode Request Generator within the mobile compares the DL Quality indicator with certain thresholds and generates a Codec Mode Request indicating the preferred codec mode for the downlink. The Codec Mode Request is transmitted inband to the network side where it is fed into the DL Mode Control unit. This unit generally grants the requested mode. However, considering possible constraints from network control, it may also override the request. The resulting codec mode is then applied for encoding of the incoming speech signal in downlink direction. Both for uplink and downlink, the presently applied codec mode is transmitted inband as Codec Mode Indication together with the coded speech data. At the decoder, the Codec Mode Indication is decoded and applied for decoding of the received speech data. + +![Figure 1: High level AMR block diagram. The diagram shows three main entities: TRAUs, BTS, and MS. The TRAUs contain SPE (Speech Encoder) and SPD (Speech Decoder) blocks. The BTS contains CHE (Codec Handling Entity), DL-Mode Ctrl (Downlink Mode Control), UL-Mode Ctrl (Uplink Mode Control), network control, and UL-Meas. (Uplink Measurements) blocks. The MS contains CHD (Codec Handling Entity), SPD, DL-Meas. (Downlink Measurements), DL-Req.Gen (Downlink Request Generator), CHE, and SPE blocks. Arrows indicate the flow of speech data, DL/UL codec modes, DL/UL Mode Commands/Requests, and Quality Indicators between these components across the radio links.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Figure 1: High level AMR block diagram. The diagram shows three main entities: TRAUs, BTS, and MS. The TRAUs contain SPE (Speech Encoder) and SPD (Speech Decoder) blocks. The BTS contains CHE (Codec Handling Entity), DL-Mode Ctrl (Downlink Mode Control), UL-Mode Ctrl (Uplink Mode Control), network control, and UL-Meas. (Uplink Measurements) blocks. The MS contains CHD (Codec Handling Entity), SPD, DL-Meas. (Downlink Measurements), DL-Req.Gen (Downlink Request Generator), CHE, and SPE blocks. Arrows indicate the flow of speech data, DL/UL codec modes, DL/UL Mode Commands/Requests, and Quality Indicators between these components across the radio links. + +Figure 1: High level AMR block diagram + +Codec mode selection is done from a set of codec modes (ACS, Active Codec Set), which may include 1 to 4 AMR codec modes. Associated with this set is a list of 1 to 3 switching thresholds and hysteresis used by the DL Mode Request Generator and the UL mode control unit to generate the Codec Mode Requests and Codec Mode Commands. These configuration parameters (ACS, thresholds, hysteresis) are defined at call set-up and can be modified at handover or during a call. + +### 3.1.2 Operation with ongoing Tandem Free Operation + +If tandem free operation is ongoing (see 3GPP TS 28.062) then the speech signal has to be transmitted over two radio links, first uplink (MS1 to BTS1) and then downlink (BTS2 to MS2), respectively symmetrically in the reverse direction. The optimal Codec Mode in direction MS1 to MS2 shall be derived from the Codec Mode Command for the first uplink (CMC1, within BTS1) and the Codec Mode Request derived for the second downlink (CMR2 within MS2) in the following way: MS2 shall send the CMR2 back to BTS2 in the usual way. BTS2 shall either accept this CMR2 (default) or may modify it according to network control needs: CMR2'. Then BTS2 shall send the CMR2' further uplink to its TRAUs, to TRAUs and downlink to BTS1 (see 3GPP TS 28.062 on how this transmission shall be handled on Abis and A interfaces). BTS1 combines the received CMR2' with its own derived CMC1 by taking the minimum of both values. If needed, BTS1 may modify this minimum value according to own network control (→ CMC1') and shall send it finally downlink to MS1 as CMC. The identical procedure shall be performed in the reverse direction. Annex C gives an informative description. + +### 3.1.3 Operation at handover with ongoing Tandem Free Operation + +Before and during an handover at one or both sides of the MS-to-MS connection, it may be needed to freeze the codec mode adaptation for a short while, e.g. to optimise the common Active Codec Set, or to allow fast (re-)synchronisation between BTS and TRAUs or to optimise the CMI Phase in downlink. Both BTSs may therefore enable or disable the codec mode adaptation (see 3GPP TS 28.062). As long as the codec mode adaptation is frozen to a specific codec mode, then this codec mode shall be used in both directions as long as tandem free operation is ongoing, or tandem free operation shall be discontinued. The Codec Mode Requests from the MSs may be taken into account to decide whether to continue TFO or not, but not for codec mode adaptation. + +## 3.2 Inband Signalling + +The AMR inband signalling consists of two parts: + +- Frequent signalling, used for Codec Mode Indication and Codec Mode Command/Request. +- Robust, less frequent signalling, based on frame stealing, used for changing the AMR configuration (RATSCCH). + +### 3.2.1 Frequent inband signalling for AMR codec mode adaptation + +#### 3.2.1.1 General aspects + +The codec mode information, which has to be transmitted on each link, consists of Codec Mode Indications and Codec Mode Commands in the downlink, respectively Codec Mode Indications and Codec Mode Requests in the uplink. Codec Mode Indications inform the receiver about the currently applied codec mode. Codec Mode Commands inform the other end about the codec mode to be applied on the other link. Codec Mode Requests inform the other end about the preferred codec mode on the other link. + +Codec mode information is transmitted inband in the speech traffic channel, using a part of its transmission capacity. The coding of codec modes in the inband signalling is given in subclause 3.4.1. Channel coding of codec mode information is specified in 3GPP TS 45.003 [4] for all frame types. + +Codec modes are constrained to change only every second speech frame. Codec Mode Commands/Requests and Codec Mode Indications are sub-sampled such that they occur only every second frame. Codec Mode Indications and Codec Mode Commands/Requests shall be transmitted alternating within consecutive speech frames. + +Both, Codec Mode Indication and Codec Mode Command/Request, shall be transmitted together within every RATSCCH frame. + +#### 3.2.1.2 Operation with DTX enabled + +For SID\_FIRST frames, the Codec Mode Indication or Codec Mode Command/Request in phase with the alternating transmission shall be transmitted (same phase as in speech frames). + +Both, Codec Mode Indication and Codec Mode Command/Request, shall be transmitted together in every SID\_UPDATE frame (as in RATSCCH frames). + +For ONSET frames the Codec Mode Indication for the subsequent speech frame shall be transmitted, regardless of the phase of the inband signalling. The general phase of the inband signalling shall not be changed by that. + +#### 3.2.1.3 Transmitter/Receiver Synchronisation + +The alternating transmission of the codec mode information requires synchronisation of transmitting and receiving ends, such that Codec Mode Indications and Codec Mode Commands/Requests are decoded in correct order. To ensure proper synchronisation, the codec mode information shall be transmitted aligned to the 26-multiframe structure of the GSM system. + +The default transmission phase for TCH/AFS, TCH/WFS, and O-TCH/WFS shall be such that Codec Mode Indications are sent with speech frames having their first burst sent on TDMA frames according to table 3.2.1.3-1. + +**Table 3.2.1.3-1. TDMA frames for Codec Mode Indication for TCH/AFS, TCH/WFS and O-TCH/WFS.** + +| Downlink | Uplink | +|----------------------------------------------------------|----------------------| +| 4, 13, 21 (modulo 26) | 0, 8, 17 (modulo 26) | +| NOTE: TDMA frame numbering defined in 3GPP TS 45.002 [3] | | + +The default transmission phase for TCH/AHS, O-TCH/AHS, and O-TCH/WHS shall be such that Codec Mode Indications are sent with speech frames having their first burst sent on TDMA frames according to table 3.2.1.3-2. + +**Table 3.2.1.3-2. TDMA frames for Codec Mode Indication for TCH/AHS, O-TCH/AHS and O-TCH/WHS.** + +| Downlink (1) | Uplink (1) | +|--------------------------------------------------------------------------------------|---------------------------------------------------| +| 4, 13, 21 (modulo 26), or,
5, 14, 22 (modulo 26) | 0, 8, 17 (modulo 26), or,
1, 9, 18 (modulo 26) | +| NOTE 1: The mapping is dependent on the subchannel as defined in 3GPP TS 45.002 [3]. | | +| NOTE 2: TDMA frame numbering defined in 3GPP TS 45.002 [3] | | + +For a mobile station indicating support for VAMOS, the default transmission phase for TCH/AFS and TCH/WFS shall be such that Codec Mode Indications are sent with speech frames having their first burst sent on TDMA frames according to table 3.2.1.3-3. + +**Table 3.2.1.3-3. TDMA frames for Codec Mode Indication for TCH/AFS, TCH/WFS for VAMOS.** + +| VAMOS mobile support level | Assigned TSC set | Transmission phase (1) | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------------|----------------------|--|--| +| | | Downlink | Uplink | | | +| VAMOS I | Set 1, 2, 3 or 4 | 4, 13, 21 (modulo 26) | 0, 8, 17 (modulo 26) | | | +| VAMOS II/III | Set 1 or 3 | | | | | +| VAMOS II/III | Set 2 or 4 | | | | | +| NOTE 1: TDMA frame numbering defined in 3GPP TS 45.002 [3] | | | | | | +| NOTE 2: The use of TSC set 3 and TSC set 4 is only applicable for mobile stations indicating support for Extended TSC sets, see 3GPP TS 24.008. | | | | | | + +For a mobile station indicating support for VAMOS, the default transmission phase for TCH/AHS shall be such that Codec Mode Indications are sent with speech frames having their first burst sent on TDMA frames according to table 3.2.1.3-4. + +**Table 3.2.1.3-4. TDMA frames for Codec Mode Indication for TCH/AHS for VAMOS.** + +| VAMOS mobile support level | Assigned TSC set | Transmission phase (1) (2) | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------|----------------------------------------------------|--|--| +| | | Downlink | Uplink | | | +| VAMOS I | Set 1, 2, 3 or 4 | 4, 13, 21 (modulo 26)
or
5, 14, 22 (modulo 26) | 0, 8, 17 (modulo 26)
or
1, 9, 18 (modulo 26) | | | +| VAMOS II/III | Set 1 or 3 | | | | | +| VAMOS II/III | Set 2 or 4 | | | | | +| NOTE 1: TDMA frame numbering defined in 3GPP TS 45.002 [3] | | | | | | +| NOTE 2: Depending on the half-rate subchannel as defined in 3GPP TS 45.002 [3] | | | | | | +| NOTE 3: The use of TSC set 3 and TSC set 4 is only applicable for mobile stations indicating support for Extended TSC sets, see 3GPP TS 24.008. | | | | | | + +This default phase of the Codec Mode Indication in downlink direction is called "odd", the alternative phase, one speech frame shifted, is called "even". The phase in uplink is always the same and is never changed. + +At call set-up, after a channel mode modify with consistent MultiRate configuration IE and after each reallocation of the circuit switched channel, the default phase (odd) shall be used in downlink direction. During a call, the phase of Codec Mode Indication may be changed in downlink by using a RATSCCH message. In case of reallocation failure and fall back to the channel before the reallocation attempt, the phase before the channel reallocation attempt shall be used again (except if a RATSCCH procedure is pending, see section 3.2.2.2 bullet 6). + +### 3.2.2 Robust inband signalling for AMR configuration modification + +#### 3.2.2.1 General aspects + +The RATSCCH mechanism may be used in case of Tandem Free Operation to modify the AMR Configuration on the radio interface without interruption of the speech transmission. Its application for TFO is described in 3GPP TS 28.062. This recommendation defines the RATSCCH protocol and the RATSCCH messages. The channel coding is defined in 3GPP TS 45.003 and the receiver performance in 3GPP TS 45.005. RATSCCH handling is mandatory for MS and optional for BTS. + +RATSCCH is based on frame stealing. On TCH/AFS, TCH/WFS and O-TCH/WFS, one speech frame is stolen for each RATSCCH message, and on TCH/AHS, O-TCH/AHS and O-TCH/WHS two speech frames are stolen. In TCH/AHS and O-TCH/AHS RATSCCH is mapped onto two consecutive speech frames, the RATSCCH\_MARKER and the RATSCCH\_DATA. Both shall be sent always as one pair. + +FACCH frames have higher priority than RATSCCH frames. If FACCH and RATSCCH are scheduled for transmission for the same speech frame, then the FACCH shall be sent first, followed by the RATSCCH. If the RATSCCH is delayed due to FACCH, then the appropriate counters shall also be started as per section 3.2.2.2, based on actual transmission of the RATSCCH on the radio interface. If in the case of TCH/AHS, O-TCH/AHS and O-TCH/WHS, FACCH steals the second frame of one RATSCCH message (RATSCCH\_DATA), the complete RATSCCH message (RATSCCH\_MARKER and RATSCCH\_DATA) shall be sent following the FACCH frame. + +#### 3.2.2.2 RATSCCH protocol + +The RATSCCH protocol elements consist of a number of REQuest Messages and three ACKnowledgement Messages. One information exchange consists typically of one REQ-ACK cycle between the "Initiator" and the "Addressee". While the Initiator is waiting for an ACK, it shall not send any new REQ message, i.e. transmission and acknowledgement of one REQ-ACK cycle shall be completed before the next cycle is started. ACK messages, as reaction to received REQ messages, shall always be sent back as soon as possible, and latest within 3 speech frames. Both sides shall continuously monitor the radio reception for the RATSCCH pattern and decode the RATSCCH message. + +The typical REQ-ACK cycle is defined as: + +- 1) If one side ("Initiator") wants to initiate the information exchange, it shall send the desired REQ message. At the same time the Initiator shall start two counters: +ACK\_Timeout that shall count the elapsed speech frames occurrences (after REQ) in receive direction and +REQ\_Activation that shall count the elapsed speech frames occurrences (after REQ) in send direction. +- 2) If the REQ message was decoded error-free (by CRC check, see 3GPP TS 45.003 [4]) and is defined (see section 3.2.2.3) at receiver side ("Addressee"), then the Addressee shall send an ACK\_OK message back. At the same time the Addressee shall start two own counters: +REQ\_Activation that shall count the elapsed speech frames occurrences after REQ in receive direction and +ACK\_Activation that shall count the elapsed speech frames occurrences after ACK in send direction. +- 3) If the Initiator receives an ACK\_OK, then it shall ignore its ACK\_Timeout counter and shall start an ACK\_Activation counter instead that shall count the elapsed speech frames after ACK\_OK in receive direction. +- 4) The contents of the REQ messages shall become valid in the direction from Initiator to Addressee exactly in that frame, where the REQ\_Activation counters reach the value 12 and for all following frames. +The contents of the REQ message shall become valid in the direction from Addressee to Initiator exactly in that frame, where the ACK\_Activation counters reach the value 12 and for the following frames. +Note: Due to the transmission delay and the reaction time within the Addressee (REQ to ACK) the activation takes place in general at four different points in time, but exactly synchronised and defined in both directions. +- 5) If another REQ message is received by the Addressee before REQ\_Activation has elapsed, the Addressee shall ignore the message. +- 6) If, following a L3 message (e.g. ASSIGNMENT COMMAND or HANDOVER COMMAND) the physical layer is disconnected and re-established on a new channel, any pending RATSCCH procedure shall be cancelled in the MS: the timers REQ\_Activation and ACK\_Activation are stopped and the configuration change required by the RATSCCH procedure is not performed. +In the case the L3 procedure fails and the MS comes back to the original channel, any pending acknowledged REQ message shall be applied regardless the values of REQ\_Activation and ACK\_Activation. +- 7) If a L3 message CHANNEL MODE MODIFY with consistent MultiRate IE is received (see 3GPP TS 44.018), any pending RATSCCH procedure shall be cancelled in the MS: the timers REQ\_Activation and ACK\_Activation are stopped and the configuration change required by the RATSCCH procedure is not performed. + +Note: a speech frame occurrence is the part of the multiframe that is used by a speech frame or that could have been used by a speech frame (e.g. in the case of speech frame stolen by FACCH or during silence periods when DTX is active). + +Error Handling: + +- 1) If the REQ message was decoded error-free (no CRC error), but the message is not defined at the Addressee side, then the Addressee shall send an ACK\_UNKNOWN message back. No counters are needed in this case. +The Initiator, when receiving this ACK\_UNKNOWN message shall terminate the exchange for this type of REQ message. +- 2) If the RATSCCH message was detected, but could not be decoded correctly (CRC failure), or its contents was not consistent, then the Addressee shall send an ACK\_ERR message back. No counters are needed in this case. + +- 3) If the Initiator does not receive an ACK\_OK or ACK\_UNKNOWN before the ACK\_Timeout counter reaches 10, or it receives an ACK\_ERR instead, then it shall initiate the exchange again by resending the REQ and starting the timers anew. +- 4) If the Initiator has sent the REQ unsuccessfully for three times, the retransmission shall be stopped. +- 5) If at either side an ACK\_ERR or ACK\_UNKNOWN is received although no corresponding REQ has been sent before, this ACK messages shall be ignored. + +If the BTS receives an ACK\_OK although it has not sent a corresponding REQ before, then the BTS shall initiate the sending of the used AMR Configuration down to the MS. + +#### 3.2.2.3 RATSCCH messages + +Each RATSCCH message consists of its RATSCCH message identifier and potentially message parameters. In total 35 net bits are available for each message. They are numbered 34...0 in the message descriptions below, and correspond to d(34) ... d(0) in 3GPP TS 45.003. Three different ACKnowledgement message are defined. + +##### 3.2.2.3.1 ACK\_OK message + +The ACK\_OK message serves as an acknowledgement that a RATSCCH REQ message has been detected, correctly decoded (no CRC error) and that it is defined for the Addressee. It defines the exact activation time in direction from Addressee to Initiator. Table 3.2.2.3.1 shows the definition of the ACK\_OK. + +**Table 3.2.2.3.1: Definition of the ACK\_OK message** + +| | | +|--------------|---------------------| +| Bit | 34 ... 2 1 0 | +| Value | 0 ... 0 0 1 | + +##### 3.2.2.3.2 ACK\_ERR message + +The ACK\_ERR message serves as a negative acknowledgement that a RATSCCH REQ message has been detected, i.e. the RATSCCH pattern was detected, but either could not be decoded correctly (CRC error) or its content is not understandable by the addressee. Table 3.2.2.3.2 shows the definition of the ACK\_ERR. + +**Table 3.2.2.3.2: Definition of the ACK\_ERR message** + +| | | +|--------------|---------------------| +| Bit | 34 ... 2 1 0 | +| Value | 0 ... 0 1 0 | + +##### 3.2.2.3.3 ACK\_UNKNOWN message + +The ACK\_UNKNOWN message serves as an acknowledgement that a RATSCCH REQ message has been detected and correctly decoded, but was unknown to the Addressee. Table 3.2.2.3.3 shows the definition of the ACK\_UNKNOWN. + +**Table 3.2.2.3.3: Definition of the ACK\_UNKNOWN message** + +| | | +|--------------|---------------------| +| Bit | 34 ... 2 1 0 | +| Value | 0 ... 0 1 1 | + +ACKnowledge messages shall only be sent in response to a REQuest message. + +##### 3.2.2.3.4 CMI\_PHASE\_REQ message + +The CMI\_PHASE\_REQ message may be sent by the BTS to change the phase of the Codec Mode Indication in downlink. CMI\_PHASE\_REQ has only parameter, Codec Mode Indication Phase (CMIP). Table 3.2.2.3.4a shows the format. + +**Table 3.2.2.3.4a: Format of the CMI\_PHASE\_REQ message** + +| | | | +|--------------|------------------|-------------| +| Bit | 34 ... 21 | 0 | +| Value | 0 ... 1 0 | CMIP | + +Assuming the CMI\_PHASE\_REQ message replaces DL speech frame $N$ (frames $N-1$ and $N$ for TCH/AHS, O-TCH/AHS and O-TCH/WHS), then the new phase shall be used starting with DL speech frame $N+12$ . The CMI Phase in uplink shall not be affected. The new CMI phase in downlink shall be active until it is modified by a new CMI\_PHASE\_REQ or until a handover is successfully executed. + +Table 3.2.2.3.4b shows how Codec Mode Indications and Codec Mode Commands shall be transmitted in even and odd speech frames depending on the value of MIP. See section 3.2.1.3 for the definition of even and odd speech frames. + +**Table 3.2.2.3.4b: Phase of Codec Mode Indication/Command in DL depending on CMIP** + +| Value of CMIP | Information transmitted in even speech frames | Information transmitted in odd speech frames | +|----------------------|------------------------------------------------------|-----------------------------------------------------| +| 0 | Codec Mode Indication | Codec Mode Command | +| 1 (default) | Codec Mode Command | Codec Mode Indication | + +##### 3.2.2.3.5 AMR\_CONFIG\_REQ message + +The AMR\_CONFIG\_REQ message may be sent by the BTS during a call to change the AMR configuration on the radio interface without interruption of the speech transmission. AMR\_CONFIG\_REQ contains several parameters: Active Codec Set (ACS), Initial Codec Mode (ICM), and a pair of threshold and hysteresis values (THRESH $j$ and HYST $j$ ). Table 3.2.2.3.5a shows the format. + +**Table 3.2.2.3.5a: Main Format of the AMR\_CONFIG\_REQ message** + +| | | | | | | | | | | +|--------------|----------------|-----------|-----------|------------------|------------------|------------------|------------------|----------------|----------------| +| Bit | 34...32 | 31 | 30 | 29 ... 28 | 27 ... 20 | 19 ... 16 | 15 ... 10 | 9 ... 6 | 5 ... 0 | +| Value | 0 0 1 | 1 | 1 | ICM | ACS | HYST2 | THRESH2 | HYST1 | THRESH1 | + +The ACS and ICM parameters are coded in the same way as defined in 3GPP TS 44.018 [2]. + +All threshold and hysteresis parameters in the AMR\_CONFIG\_REQ are valid only for downlink direction. The coding of these parameters is given in section 3.4.2. + +If the ACS consists of $n$ modes ( $n=1,2,3$ ), then only THRESH $1 \dots$ THRESH $n-1$ and HYST $1 \dots$ HYST $n-1$ are defined. The remaining bits are reserved for future use and shall be set to "1". + +If the ACS consists of four modes, then the complete set of thresholds/hysteresis can not be sent with this message. In that case, all THRESH $j$ and HYST $j$ fields are reserved for future use and shall be set to "1". Similar, if the BTS has no threshold and hysteresis parameters for the given configuration, then all THRESH $j$ and HYST $j$ field bits shall be set to "1" to indicate that they are undefined. The THRESH\_REQ message shall be used to transmit these parameters at a later point in time. As long as the MS has no defined threshold and hysteresis parameters it shall use the Initial Codec Mode for the Codec Mode Request. + +Alternatively, in case of four codec modes, the BTS may send the three threshold and hysteresis parameters as shown in table 3.2.2.3.5.b. The coding of HYST $c$ is given in section 3.4.2. All three hysteresis values (HYST $1/2/3$ ) are in that case represented by one common HYST $c$ value (HYST $1 =$ HYST $2 =$ HYST $3 =$ HYST $c$ ). + +**Table 3.2.2.3.5b: Alternative Format of the AMR\_CONFIG\_REQ message for four modes** + +| Bit | 34...32 | 31 | 30 | 29 ... 28 | 27 ... 20 | 19 ... 18 | 17 ... 12 | 11 ... 6 | 5 ... 0 | +|-------|---------|----|----|-----------|-----------|-----------|-----------|----------|---------| +| Value | 0 0 1 | 1 | 1 | ICM | ACS | HYSTc | THRESH3 | THRESH2 | THRESH1 | + +In this way the ACS and the associated thresholds may be sent in one single message, allowing an immediate Codec Mode Request generation within the MS for the new configuration. If needed the hysteresis parameters may be modified in a later THRESH\_REQ message. + +The normal completion of an AMR\_CONFIG\_REQ procedure is then: + +- Assuming that the AMR\_CONFIG\_REQ message replaces DL speech frame $N$ (speech frames $N-1$ and $N$ for TCH/AHS, O-TCH/AHS and O-TCH/WHS), then the BTS and MS shall use the new ACS and ICM starting with DL speech frame $N+12$ . This means that from that speech frame on, Mode Indications on the DL and DL Mode Requests on the UL shall be interpreted relative to the new ACS. +- Assuming that the ACK\_OK to the AMR\_CONFIG\_REQ message replaces UL speech frame $M$ (speech frames $M-1$ and $M$ for TCH/AHS, O-TCH/AHS and O-TCH/WHS), then the BTS and MS shall use the new ACS and ICM starting with UL speech frame $M+12$ . This means that from that speech frame on, Mode Indications on the UL and UL Mode Commands on the DL shall be interpreted relative to the new ACS. + +NOTE: During a short time in the transition period the configuration is different in uplink and downlink direction. + +##### 3.2.2.3.6 THRESH\_REQ message + +The THRESH\_REQ message may be sent by the BTS to change the thresholds in the DL Mode Request Generator. The THRESH\_REQ message contains up to three pairs of threshold and hysteresis values (THRESH $j$ and HYST $j$ ). Table 3.2.2.3.6 shows the format. + +**Table 3.2.2.3.6: Format of the THRESH\_REQ message** + +| Bit | 34...30 | 29 ... 26 | 25 ... 20 | 19 ... 16 | 15 ... 10 | 9 ... 6 | 5 ... 0 | +|-------|-----------|-----------|-----------|-----------|-----------|---------|---------| +| Value | 0 0 0 0 1 | HYST3 | THRESH3 | HYST2 | THRESH2 | HYST1 | THRESH1 | + +The coding of the THRESH $j$ and HYST $j$ values is given in section 3.4.2. If the ACS consists of $n$ ( $n=1,2,3,4$ ) modes, only THRESH1...THRESH $n-1$ and HYST1...HYST $n-1$ are defined. The remaining THRESH $j$ and HYST $j$ fields are reserved for future use and shall be set to "1". + +The normal completion of a THRESH\_REQ procedure is then: + +- Assuming that the THRESH\_REQ message replaces DL speech frame $N$ (speech frames $N-1$ and $N$ for TCH/AHS, O-TCH/AHS and O-TCH/WHS), then the MS shall use the new thresholds and hysteresis starting with measurements of DL speech frame $N+12$ . + +## 3.3 Codec mode adaptation + +### 3.3.1 Channel quality measure + +Codec mode adaptation is based on a normalized, one-dimensional measure of the channel quality, called the Quality Indicator. For reference purposes, the Quality Indicator is defined as an equivalent carrier to interferer ratio, $C/I_{norm}$ . The reference channel conditions for the normalized Quality Indicator $C/I_{norm}$ shall be Typical Urban 3 km/h with ideal frequency hopping at 900 MHz. The corresponding reference receiver performance is specified as the minimum performance requirement in 3GPP TS 45.005. The MS and BSSs shall continuously update the Quality Indicator estimates. + +The Quality Indicator may be derived from an estimate of the current carrier to interferer ratio, $C/I_{est}$ , or an estimate of the current raw bit error rate ( $BER_{est}$ ). A normalization factor $>0$ dB may be applied between the estimate ( $C/I_{est}$ or $BER_{est}$ ) and the Quality Indicator to compensate for higher receiver performance than the minimum performance requirement in 3GPP TS 45.005. This normalization factor may be dependent on the $C/I$ at the antenna connector. + +The MS shall apply a second normalization factor be applied to normalize the estimate with respect to different channel types, such that, with given $C/I_{norm}$ and given codec mode, the FER after channel decoding becomes independent of the channel type. + +An example of channel quality measuring for the case of an Ideal Frequency Hopping channel in a Typical Urban Environment is given in Annex A. + +### 3.3.2 Generation of Codec Mode Commands and Requests + +For codec mode adaptation, the channel Quality Indicators are mapped to Codec Mode Commands/Requests, by quantizing the Quality Indicators. The output values of the quantizer shall represent the different codec modes. + +Hysteresis in the mapping from Quality Indicators to Codec Mode Commands/Requests should be used to prevent undesirable fast switching of CodecMode Commands/Requests. The hysteresis in the mapping is defined in the following way. The previously sent Codec Mode Command, CMC' (respectively Codec Mode Request, CMR') is used as the current state of the adaptation logic. For each state, lower and upper thresholds THR\_MC\_Dn(CMC') and THR\_MC\_Up(CMC') for the downlink, and THR\_MR\_Dn(CMR') and THR\_MR\_Up(CMR') for the uplink are defined. If the measure falls below the lower threshold, the next lower Codec Mode Command/Request commanding/requesting a more robust codec mode shall be generated. If the measure exceeds the upper threshold, then the next higher Codec Mode Command/Request commanding/requesting a less robust codec mode shall be issued. Otherwise, the previous Codec Mode Command/Request shall be repeated. + +The degree of hysteresis is controlled by appropriately setting the upper and lower decision thresholds. The thresholds shall be defined by layer 3 signalling, as described in subclause 3.4.2, or by RATSCCH messages. An example of decision thresholds for the case of an Ideal Frequency Hopping channel in a Typical Urban Environment is given in Annex B. + +For reasons of channel error robustness of the codec mode information, the Codec Mode Commands/Requests and Codec Mode Indication shall be restricted to change at maximum to their nearest neighbours within the Active Codec Set. This means that mode switches to modes that are not direct neighbours to the previously transmitted mode shall be avoided. + +Nevertheless, the transitions may span more than one step in several situations : + +- after handover, (where the MS shall start with the Initial Codec Mode, regardless, which codec mode was used before) +- when a distant MS has performed a handover while TFO is active + +when the AMR configuration is changed by an AMR\_CONFIG\_REQ message. + +### 3.3.3 Performance requirements + +#### 3.3.3.1 MS response to the Codec Mode Command + +The MS shall after the reception of a Codec Mode Command apply the corresponding codec mode in uplink direction for the next possible speech frame and, and no more than three speech frames later. If the Codec Mode Command would require a change of the uplink codec mode by more than one step within the defined Active Codec Set, then the MS shall perform the transition from the currently used codec mode into the commanded codec mode in several steps, one step every second speech frame. Exceptions may occur only at call set-up and after handover, (where the MS shall start with the Initial Codec Mode, regardless, which codec mode was used before), and when the AMR configuration is modified with an AMR\_CONFIG\_REQ message. + +#### 3.3.3.2 BTS response to the Codec Mode Request + +The BTS should apply the requested mode for the earliest possible speech frame, unless the BTS intends to override the Codec Mode Request from the MS due to network control needs. + +#### 3.3.3.3 Performance of the Codec Mode Request Generation + +For TU3 channel conditions with ideal frequency hopping without DTX activated in GSM900 and GSM850, the MS shall produce Codec Mode Requests with the following accuracy: + +- When a carrier to interferer ratio 4 dB higher than a defined upper threshold is applied to the antenna connector, the MS shall request a higher mode with a probability exceeding 90%. This shall be measured immediately after a settling-time of 200 ms. +- When a carrier to interferer ratio 4 dB lower than a defined lower threshold is applied to the antenna connector, the MS shall request a lower mode with a probability exceeding 90%. This shall be measured immediately after a settling-time of 200 ms. + +If required, the above test levels shall be reduced by the normalization factor defined in sub-clause 3.3.1 to account for potential improved receiver performances. + +For other frequency bands, the propagation profile should be adjusted to: TU1.5 for DCS1800 and PCS1900, TU6 for GSM400 and TU3.6 for GSM700. + +Note 1: Ideal frequency hopping assumes perfect decorrelation between bursts. For the propagation profile TU3, this is not easily achievable due to the high number of hopping frequencies required. Therefore, performance tests should be performed under ideal frequency hopping conditions for the following propagation profiles: TU50 for GSM900 and GSM850, TU25 for DCS1800 and PCS1900, TU100 for GSM400, and TU60 for GSM700. + +Note 2: Receivers with improved performance may exceed the minimum requirements reflected by the normalisation factor defined in sub-clause 3.3.1. The normalisation factor, reflecting the improved performance, may depend on the carrier to interference ratio (C/I). Therefore, the conformance test of these receivers may require normalisation factors to be provided for each nominal C/I of the test. + +## 3.4 Setup procedures + +### 3.4.1 Definition of the AMR Active Codec Set + +AMR codec mode adaptation is done within a set of up to four codec modes. The codec mode set (Active Codec Set) to be used by the BSS and the MS is defined during call set-up and/or handover by layer 3 signalling defined in 3GPP TS 44.018 [2]. The Active Codec Set (ACS) can be changed during a call using a RATSCCH message. + +The following convention (see table 3.4.1) applies for the coding of the codec modes for the inband signalling (Codec Mode Indications, Codec Mode Commands/ Requests). + +**Table 3.4.1: Identification of the codec modes within the Active Codec Set** + +| Identifier | Legend | +|--------------|---------------------------------------------------------------------------| +| CODEC_MODE_1 | Represents the lowest codec mode (lowest bit-rate) of the ACS | +| CODEC_MODE_2 | Represents the second lowest mode, if the ACS includes more than one mode | +| CODEC_MODE_3 | Represents the third lowest mode, if the ACS includes more than two modes | +| CODEC_MODE_4 | Represents the highest mode, if the ACS includes four modes | + +If less than four Codec Modes are defined in the ACS, the unused codec Mode Indications and Mode Commands/Mode Requests shall not be signalled. Unused codec modes shall not be detected by the inband signalling decoder. + +### 3.4.2 Definition of Codec Mode Command/Request decision thresholds + +The Codec Mode Command/Request decision thresholds shall be defined at call set-up and/or handover by layer 3 signalling as defined in 3GPP TS 44.018 [2]. The decision thresholds may be changed during a call using a RATSCCH message. The decision thresholds shall apply to the reference channel conditions TU3 ideal frequency hopping at 900 MHz. For each pair of neighbouring codec modes in the Active Codec Set, a threshold and a hysteresis value in terms of normalized carrier to interference ratio ( $C/I_{norm}$ ), is defined. The lower decision threshold for switching from mode j to mode j-1 is given by the signalled threshold. The threshold is referred to as THR\_MC\_Dn(j) or, THR\_MR\_Dn(j) in subclause 3.3.2. + +The sum of the signalled threshold and hysteresis constitutes the upper threshold between the codec modes, referred to as $THR\_MC\_Up(j-1)$ or, $THR\_MR\_Up(j-1)$ . The figure below illustrates the definition of the decision thresholds, and the operational range of the Codec Modes. + +![Figure 2: Definition of Threshold and Hysteresis for codec mode adaptation. The diagram shows a vertical axis labeled C/I with four horizontal lines representing thresholds. From top to bottom, the thresholds are labeled: THR_3 + HYST_3 = THR_MX_Up(3), THR_3 = THR_MX_Dn(4), THR_2 + HYST_2 = THR_MX_Up(2), THR_2 = THR_MX_Dn(3), THR_1 + HYST_1 = THR_MX_Up(1), and THR_1 = THR_MX_Dn(2). The regions between these thresholds are labeled CODEC_MODE_4, CODEC_MODE_3, CODEC_MODE_2, and CODEC_MODE_1 from top to bottom. Vertical double-headed arrows indicate the hysteresis gaps between the upper and lower thresholds for each mode transition.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Figure 2: Definition of Threshold and Hysteresis for codec mode adaptation. The diagram shows a vertical axis labeled C/I with four horizontal lines representing thresholds. From top to bottom, the thresholds are labeled: THR\_3 + HYST\_3 = THR\_MX\_Up(3), THR\_3 = THR\_MX\_Dn(4), THR\_2 + HYST\_2 = THR\_MX\_Up(2), THR\_2 = THR\_MX\_Dn(3), THR\_1 + HYST\_1 = THR\_MX\_Up(1), and THR\_1 = THR\_MX\_Dn(2). The regions between these thresholds are labeled CODEC\_MODE\_4, CODEC\_MODE\_3, CODEC\_MODE\_2, and CODEC\_MODE\_1 from top to bottom. Vertical double-headed arrows indicate the hysteresis gaps between the upper and lower thresholds for each mode transition. + +**Figure 2: Definition of Threshold and Hysteresis for codec mode adaptation** + +The switching thresholds shall be given by the network in a consistent order, i.e. such that: + +- $THR\_1 \leq THR\_2 \leq THR\_3$ , and +- $THR\_1 + HYST\_1 \leq THR\_2 + HYST\_2 \leq THR\_3 + HYST\_3$ . + +| Parameter name | Description | Range | Bits | +|----------------|----------------------------------------------------------------------------------------|-------|------| +| THR_1/2/3 | Lower thresholds for switching between mode j and j-1 | 0-63 | 6 | +| HYST_1/2/3 | Hysteresis values to obtain the higher thresholds for switching between mode j and j+1 | 0-15 | 4 | + +A threshold (THR) is given as an absolute value in 0.5 dB steps. The THR values between 0 and 63 shall be mapped to normalized C/I values as follows: + +| | | | | +|-----------|----|---|---------| +| THR 1/2/3 | 0 | = | 0.0 dB | +| THR 1/2/3 | 1 | = | 0.5 dB | +| THR 1/2/3 | 2 | = | 1.0 dB | +| | ⋮ | | | +| THR 1/2/3 | 62 | = | 31.0 dB | +| THR 1/2/3 | 63 | = | 31.5 dB | + +NOTE: The threshold for codec mode j should be set to such a normalized C/I value that codec mode j starts to degrade and that a FER of less than 1% is observed. + +When using the RATSCH format defined by table 3.2.2.3.5a or table 3.2.2.3.6 or when using layer 3 signalling for the definition of the threshold and hysteresis parameters, the HYST1/2/3 shall be coded in 0,5 dB steps as follows: + +| | | | | +|------------|----|---|--------| +| HYST 1/2/3 | 0 | = | 0.0 dB | +| HYST 1/2/3 | 1 | = | 0.5 dB | +| HYST 1/2/3 | 2 | = | 1.0 dB | +| | | : | | +| | | : | | +| HYST 1/2/3 | 14 | = | 7.0 dB | +| HYST 1/2/3 | 15 | = | 7.5 dB | + +When using the RATSCCH format defined by table 3.2.2.3.5b for the definition of the threshold and hysteresis parameters, HYSTC shall be coded in 1 dB steps as follows: + +| | | | | +|-------|---|---|--------| +| HYSTc | 0 | = | 1.0 dB | +| HYSTc | 1 | = | 2.0 dB | +| HYSTc | 2 | = | 3.0 dB | +| HYSTc | 3 | = | 4.0 dB | + +### 3.4.3 Initial Codec Mode Selection at Call Setup and Handover + +The Initial Codec Mode (ICM), to start the speech coding operation with at call set-up and after handover may be signalled by layer 3 signalling. It may also be signalled by a RATSCCH message. This explicitly signalled ICM shall have preference over the default ICM, as describe below: + +If the Initial Codec Mode is not signalled, then the default Initial Codec Mode is given by the following implicit rule. If the Active Codec Set contains: + +- 1 mode, then this shall be the Initial Codec Mode; +- 2 or 3 modes, then the Initial Codec mode shall be the most robust mode of the set (with lowest bit rate); +- 4 modes, then the Initial Codec Mode shall be the second most robust mode of the set (with second lowest bit rate. If the Active Codec Set is changed during the call, then this default Initial Codec Mode shall used until an other ICM is explicitly signalled. + +# Annex A (informative): Example Solution for Link quality estimation + +Link adaptation is based on a normalized measure $C/I_{norm}$ of the carrier to interferer ratio. This measure is composed of an estimate of the actual carrier to interferer ratio $C/I_{est}$ (or equivalently the actual C/N). For ideal FH-hopping channels in a typical urban environment no further adjustment or normalization is required, as described in section 3.3.1. + +C/I estimates are derived by taking C and I measurements burst by burst from the equaliser algorithm. Intermediate processing results of the equaliser are estimates of the "useful" received signal and the received noise or interference signal. Taking the ratio of the energies of both signals gives a C/I estimate for the present burst. + +The further processing of the burst-wise C/I estimates is as follows: + +- The C/I estimates are converted to dB. +- Then FIR filtering is done with non-adaptive filters of order 100 for FR and 50 for HR channels (Filter coefficients are given in Table 1 and Table 2, which is read left to right line by line). The purpose of the filter is smoothing and prediction such that the filter output is an estimate of the expected C/I at the time instant for which the link adaptation operation, i.e. the codec mode selection, becomes effective. + +**Table 1: Filter coefficients of C/I measuring filter for TCH/AFS, TCH/WFS, and O-TCH/WFS** + +| | | | | | | | | | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| 0.02737 | 0.02692 | 0.02643 | 0.02573 | 0.02527 | 0.02499 | 0.02448 | 0.02393 | 0.02335 | 0.02286 | +| 0.02240 | 0.02203 | 0.02158 | 0.02106 | 0.02072 | 0.02032 | 0.01993 | 0.01956 | 0.01923 | 0.01877 | +| 0.01825 | 0.01782 | 0.01743 | 0.01715 | 0.01682 | 0.01642 | 0.01614 | 0.01566 | 0.01520 | 0.01489 | +| 0.01465 | 0.01422 | 0.01382 | 0.01340 | 0.01303 | 0.01273 | 0.01236 | 0.01205 | 0.01178 | 0.01141 | +| 0.01102 | 0.01068 | 0.01031 | 0.00998 | 0.00958 | 0.00928 | 0.00909 | 0.00882 | 0.00854 | 0.00827 | +| 0.00800 | 0.00784 | 0.00757 | 0.00729 | 0.00693 | 0.00659 | 0.00629 | 0.00601 | 0.00586 | 0.00565 | +| 0.00540 | 0.00510 | 0.00491 | 0.00473 | 0.00464 | 0.00443 | 0.00424 | 0.00397 | 0.00385 | 0.00360 | +| 0.00351 | 0.00311 | 0.00290 | 0.00269 | 0.00232 | 0.00204 | 0.00180 | 0.00165 | 0.00137 | 0.00119 | +| 0.00098 | 0.00073 | 0.00052 | 0.00031 | 0.00006 | -0.00018 | -0.00027 | -0.00034 | -0.00043 | -0.00064 | +| -0.00079 | -0.00104 | -0.00107 | -0.00122 | -0.00146 | -0.00162 | -0.00183 | -0.00195 | -0.00208 | -0.00232 | +| -0.00253 | | | | | | | | | | + +**Table 2: Filter coefficients of C/I measuring filter for TCH/AHS, O-TCH/AHS and O-TCH/WHS** + +| | | | | | | | | | | +|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| +| 0.03998 | 0.03903 | 0.03781 | 0.03650 | 0.03513 | 0.03406 | 0.03296 | 0.03223 | 0.03116 | 0.03036 | +| 0.02911 | 0.02832 | 0.02756 | 0.02682 | 0.02585 | 0.02524 | 0.02441 | 0.02368 | 0.02277 | 0.02194 | +| 0.02118 | 0.02032 | 0.01923 | 0.01837 | 0.01788 | 0.01712 | 0.01636 | 0.01544 | 0.01474 | 0.01431 | +| 0.01370 | 0.01297 | 0.01263 | 0.01221 | 0.01181 | 0.01135 | 0.01080 | 0.00974 | 0.00919 | 0.00836 | +| 0.00790 | 0.00748 | 0.00681 | 0.00647 | 0.00613 | 0.00558 | 0.00534 | 0.00494 | 0.00436 | 0.00403 | +| 0.00351 | | | | | | | | | | + +# Annex B (informative): Example Definition of Mode Command/Request decision thresholds + +Following Table 3 gives an example definition of Mode Command/Request decision thresholds for the TCH/AFS traffic channel employing a codec mode set which contains the 12.2 kbit/s, the 7.95 kbit/s, and the 5.9 kbit/s codec modes. Table 4 gives an example definition of Mode Command/Request decision thresholds for the TCH/AHS traffic channel employing a codec mode set which contains the 7.95 kbit/s, the 6.7 kbit/s, the 5.9 kbit/s, and the 5.15 kbit/s codec modes. Table 5 gives an example definition of Mode Command/Request decision thresholds for the TCH/WFS traffic channel employing a codec mode set which contains the 12.65 kbit/s, the 8.85 kbit/s, and the 6.60 kbit/s codec modes. Table 6 gives an example definition of Mode Command/Request decision thresholds for the O-TCH/AHS traffic channel employing a codec mode set which contains the [tbd] kbit/s, the [tbd] kbit/s, the [tbd] kbit/s, and the [tbd] kbit/s codec modes. Table 7 gives an example definition of Mode Command/Request decision thresholds for the O-TCH/WFS traffic channel employing a codec mode set which contains the 23.85 kbit/s, the 15.85 kbit/s, the 12.65 kbit/s, and the 6.60 kbit/s codec modes. Table 8 gives an example definition of Mode Command/Request decision thresholds for the O-TCH/WHS traffic channel employing a codec mode set which contains the 12.65 kbit/s, the 8.8kbit/s, and the 6.60 kbit/s codec modes. + +**Table 3: MC/MR decision thresholds for TCH/AFS** + +| MC'/MR' | THR_MC_Dn(MC')/
THR_MR_Dn(MR') | THR_MC_Up(MC')/
THR_MR_Up(MR') | +|-------------|-----------------------------------|-----------------------------------| +| 12.2 kbit/s | 11.5 dB | + ∞ | +| 7.95 kbit/s | 6.5 dB | 13.5 dB | +| 5.9 kbit/s | – ∞ | 8.5 dB | + +**Table 4: MC/MR decision thresholds for TCH/AHS** + +| MC'/MR' | THR_MC_Dn(MC')/
THR_MR_Dn(MR') | THR_MC_Up(MC')/
THR_MR_Up(MR') | +|-------------|-----------------------------------|-----------------------------------| +| 7.95 kbit/s | 15.0 dB | + ∞ | +| 6.7 kbit/s | 12.5 dB | 17.0 dB | +| 5.9 kbit/s | 11.0 dB | 15.0 dB | +| 5.15 kbit/s | – ∞ | 13.0 dB | + +**Table 5: MC/MR decision thresholds for TCH/WFS** + +| MC'/MR' | THR_MC_Dn(MC')/
THR_MR_Dn(MR') | THR_MC_Up(MC')/
THR_MR_Up(MR') | +|--------------|-----------------------------------|-----------------------------------| +| 12.65 kbit/s | 10.0 dB | + ∞ | +| 8.85 kbit/s | 7.0 dB | 12.0 dB | +| 6.60 kbit/s | – ∞ | 9.0 dB | + +**Table 6: MC/MR decision thresholds for O-TCH/AHS** + +| MC'/MR' | THR_MC_Dn(MC')/
THR_MR_Dn(MR') | THR_MC_Up(MC')/
THR_MR_Up(MR') | +|--------------|-----------------------------------|-----------------------------------| +| [tbd] kbit/s | [tbd] dB | + ∞ | +| [tbd] kbit/s | [tbd] dB | [tbd] dB | +| [tbd] kbit/s | [tbd] dB | [tbd] dB | +| [tbd] kbit/s | – ∞ | [tbd] dB | + +**Table 7: MC/MR decision thresholds for O-TCH/WFS** + +| MC'/MR' | THR_MC_Dn(MC')/
THR_MR_Dn(MR') | THR_MC_Up(MC')/
THR_MR_Up(MR') | +|--------------|-----------------------------------|-----------------------------------| +| 23.85 kbit/s | [tbd] dB | + ∞ | +| 15.85 kbit/s | [tbd] dB | [tbd] dB | +| 12.65 kbit/s | [tbd] dB | [tbd] dB | +| 6.6 kbit/s | – ∞ | [tbd] dB | + +**Table 8: MC/MR decision thresholds for O-TCH/WHS** + +| MC'/MR' | THR_MC_Dn(MC')/
THR_MR_Dn(MR') | THR_MC_Up(MC')/
THR_MR_Up(MR') | +|--------------|-----------------------------------|-----------------------------------| +| 12.65 kbit/s | [tbd] dB | + ∞ | +| 8.85 kbit/s | [tbd] dB | [tbd] dB | +| 6.6 kbit/s | – ∞ | [tbd] dB | + +# --- Annex C (informative): Principles for AMR codec mode adaptation with TFO + +This annex C describes the procedures that are used for the codec mode adaptation of an Adaptive Multi-Rate (AMR) call over two radio links when Tandem Free Operation (TFO) is active between them. The mechanism to initiate TFO between AMR calls is described in 3GPP TS 28.062. It is considered as a prerequisite that a common Active Codec Set has been defined between the BSSs (by the TFO\_Protocol) and that TFO is ongoing with the same Active Codec Set on each side. + +The codec mode used in one direction may be different from the one used in the other direction, but for one direction the same codec mode is used from one MS to the other MS. The codec mode adaptation is performed independently on each direction, but in one direction the codec mode adaptation is triggered by both radio interfaces. + +The principle for codec mode adaptation in ongoing TFO is always that the BTS controlling the MS takes the final decision to upgrade or downgrade its local uplink direction. This BTS sends the Codec Mode Command downlink. + +The Codec Mode Request for the local uplink direction is taken directly into account and the effective delay is not higher than in normal connections. + +The Codec Mode Request from the remote side in the remote downlink direction is also taken into account, but it becomes active with a reaction time increased by the round trip delay between both BTSs. + +Upgrading is possible only if both radio links in one direction (first uplink then downlink) are good enough. + +Downgrading is necessary already if one (or both) radio link is not good enough. + +## --- C.1 Downgrading + +For an active AMR call without TFO, the codec mode is downgraded when the quality of the radio link decreases. In that case the codec bit rate is reduced so that more throughput is left on the radio interface to add protection. The principle when TFO is active is that as soon as one side detects the need to downgrade the codec rate, it informs the other side and the codec mode is immediately downgraded. There is no negotiation before downgrading. + +### C.1.1 Uplink downgrading + +The following figure shows the uplink adaptation due to detection by the BTS1 of a bad quality in the uplink from the MS1. In that case the round trip delay between BTS1 and BTS2 has no impact, as the uplink codec adaptation is decided immediately by BTS1 and performed by the MS1. + +![Sequence diagram for Uplink Downgrading showing the adaptation from an original codec to a new lower-rate codec across MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the uplink downgrading process. It begins with a horizontal line labeled "TFO established with original codec" spanning from MS1 to MS2. The sequence of events is as follows: + +- The BTS detects a bad uplink quality* (text annotation near BTS1). +- A message "CMC: new codec (lower rate)" is sent from BTS1 to MS1. +- The MS1 uses immediately the new codec* (text annotation near MS1). +- A message "CMI: new codec" is sent from MS1 to BTS1. +- Subsequent "CMI: new codec" messages are forwarded from BTS1 to TRAU1, TRAU1 to TRAU2, TRAU2 to BTS2, and finally from BTS2 to MS2. +- A second horizontal line at the bottom is labeled "TFO established with new codec" spanning from MS1 to MS2. + +Sequence diagram for Uplink Downgrading showing the adaptation from an original codec to a new lower-rate codec across MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2. + +Figure C.1.1: Uplink Downgrading + +### C.1.2 Downlink downgrading + +The following figure C.1.2 shows the downlink adaptation due to detection by the MS1 of a bad quality of the downlink from the BTS1. The codec mode adaptation must be performed on the far end MS (MS2), where the source encoder is located. In that case the round trip delay before the downlink adaptation is effective has an high impact. If TFO would not be active, the round trip delay would be smaller, because the Codec Mode Request sent by the BTS1 to the TRAU1 would be immediately taken into account by the TRAU1 and the new codec mode applied in downlink: without TFO ongoing the (tandem) source encoder is located in TRAU1. + +![Sequence diagram for Downlink Downgrading showing the adaptation from an original codec to a new lower-rate codec across MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +The diagram illustrates the downlink downgrading process. It begins with a horizontal line labeled "TFO established with original codec" spanning from MS1 to MS2. The sequence of events is as follows: + +- The MS detects a bad downlink quality* (text annotation near MS1). +- A message "CMR: new codec (lower rate)" is sent from MS1 to BTS1. +- The BTS decides to adapt downlink codec* (text annotation near BTS1). +- A message "CMR: new codec" is sent from BTS1 to TRAU1. +- Subsequent "CMR: new codec" messages are forwarded from TRAU1 to TRAU2, TRAU2 to BTS2, and finally from BTS2 to MS2. +- The MS2 uses immediately the new codec* (text annotation near MS2). +- A message "CMI: new codec" is sent from MS2 to BTS2. +- Subsequent "CMI: new codec" messages are forwarded from BTS2 to TRAU2, TRAU2 to TRAU1, TRAU1 to BTS1, and finally from BTS1 to MS1. +- A second horizontal line at the bottom is labeled "TFO established with new codec" spanning from MS1 to MS2. + +Sequence diagram for Downlink Downgrading showing the adaptation from an original codec to a new lower-rate codec across MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2. + +Figure C.1.2: Downlink Downgrading + +## C.2 Upgrading + +When the radio quality becomes better in one direction on both BSSs, then the signal on the radio interfaces needs less protection and consequently the useful speech information can be increased: the codec can be changed to a codec with a higher bit rate. The principle when TFO is active is that the decision to upgrade the codec is taken by the side that monitors the uplink quality. If a good quality has been detected in the uplink direction by this BTS2, then this BTS2 upgrades the Codec Mode, if the Code Mode Request from the peer MS1 allows that (when the downlink of the other side is also good). + +### C.2.1 Downlink upgrading + +In the following figure, the downlink is monitored by MS1 and the uplink by BTS2. + +![Sequence diagram illustrating Downlink Upgrading. The diagram shows the interaction between MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2. It starts with TFO established with the original codec. MS1 detects good downlink quality and sends a CMR: new codec to BTS1. BTS1 decides to adapt the downlink codec and sends CMR: new codec to TRAU1, which then sends it to TRAU2 and then to BTS2. BTS2 measures good uplink quality and sends CMC: new codec to MS2. MS2 uses the new codec immediately and sends CMI: new codec to BTS2. BTS2 sends CMI: new codec to TRAU2, which sends it to TRAU1 and then to BTS1. Finally, TFO is established with the new codec.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` + +sequenceDiagram + participant MS1 + participant BTS1 + participant TRAU1 + participant TRAU2 + participant BTS2 + participant MS2 + + Note over all: TFO established with original codec + + MS1->>BTS1: CMR: new codec +Note left of MS1: The MS detects good downlink quality + Note over BTS1: The BTS decides to adapt the downlink codec + BTS1->>TRAU1: CMR: new codec + TRAU1->>TRAU2: CMR: new codec + TRAU2->>BTS2: CMR: new codec + Note over BTS2: BTS2 has measured good uplink quality + BTS2->>MS2: CMC: new codec + Note over MS2: MS2 uses immediately the new codec + MS2->>BTS2: CMI: new codec + BTS2->>TRAU2: CMI: new codec + TRAU2->>TRAU1: CMI: new codec + TRAU1->>BTS1: CMI: new codec + BTS1->>MS1: CMI: new codec + Note over all: TFO established with new codec + +``` + +Sequence diagram illustrating Downlink Upgrading. The diagram shows the interaction between MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2. It starts with TFO established with the original codec. MS1 detects good downlink quality and sends a CMR: new codec to BTS1. BTS1 decides to adapt the downlink codec and sends CMR: new codec to TRAU1, which then sends it to TRAU2 and then to BTS2. BTS2 measures good uplink quality and sends CMC: new codec to MS2. MS2 uses the new codec immediately and sends CMI: new codec to BTS2. BTS2 sends CMI: new codec to TRAU2, which sends it to TRAU1 and then to BTS1. Finally, TFO is established with the new codec. + +Figure C.2.1: Downlink Upgrading + +In that case the round trip delay from BTS1 to BTS2 before the codec adaptation is effective in downlink to MS1 has an high impact. The delay from the BTS2 to the MS2 before the codec adaptation is effective in uplink is small. The "effective" round trip delay may even be "indefinite" if either MS1 or BTS2 is not able to upgrade its codec mode. + +In the figure above, if BTS2 had not measured a good uplink radio quality, then no adaptation would have been performed. The MS1 respectively BTS1 would go on sending continuously Codec Mode Request for the higher codec mode. + +### C.2.2 Uplink upgrading + +In the following figure, the downlink is monitored by BTS 2. + +![Sequence diagram illustrating Uplink Upgrading between MS1 and MS2 via BTS1, TRAU1, TRAU2, and BTS2.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +The sequence diagram illustrates the process of uplink upgrading. The participants are MS1, BTS1, TRAU1, TRAU2, BTS2, and MS2. The process begins with the TFO established with the original codec. The sequence of events is as follows: + +- TFO established with original codec**: A horizontal arrow points from BTS1 to MS2. +- BTS1 has measured good uplink quality, waits for a CMR from BTS2**: A note above BTS1. +- The MS detects good uplink quality**: A note above MS2. +- CMR : new codec**: A message from MS2 to BTS2. +- CMR : new codec**: A message from BTS2 to TRAU2. +- CMR : new codec**: A message from TRAU2 to TRAU1. +- CMR : new codec**: A message from TRAU1 to BTS1. +- BTS1 orders MS1 to upgrade the uplink codec**: A note above BTS1. +- CMC : new codec**: A message from BTS1 to MS1. +- MS1 uses immediately the new codec**: A note below MS1. +- CMI : new codec**: A message from MS1 to BTS1. +- CMI : new codec**: A message from BTS1 to TRAU1. +- CMI : new codec**: A message from TRAU1 to TRAU2. +- CMI : new codec**: A message from TRAU2 to BTS2. +- CMI : new codec**: A message from BTS2 to MS2. +- TFO established with new codec**: A horizontal arrow points from BTS1 to MS2. + +Sequence diagram illustrating Uplink Upgrading between MS1 and MS2 via BTS1, TRAU1, TRAU2, and BTS2. + +**Figure C.2.2: Uplink Upgrading** + +The round trip delay before the codec adaptation is effective has a low impact, if the peer MS is able to upgrade its downlink codec mode. The round trip delay may even be indefinite if the peer MS is not able to upgrade its downlink codec mode. + +In the figure above, if MS2 had not measured a good downlink radio quality, then no adaptation would have been performed. + +# Annex D (informative): Change history + +| SPEC | SMG# | CR | PHS | VERS | NEW_V | SUBJECT | +|--------|------|------|------|-------|-------|------------------------------------------------------------------------------------| +| 05.09 | s30 | A001 | R98 | 7.0.1 | 7.1.0 | Transmission Phase of AMR Inband Information | +| 05.09 | s30 | A004 | R98 | 7.0.1 | 7.1.0 | Introduction of RATSCCH for AMR | +| 05.09 | s31 | A005 | R98 | 7.1.0 | 7.2.0 | Clarification of the identification of the codec modes within the active codec set | +| 05.09 | s31 | | | 7.2.0 | 8.0.0 | Version 8.0.0 for Release 1999 | +| 05.09 | s32 | A008 | R99 | 8.0.0 | 8.1.0 | Clarification on the allowed transitions of the Codec Mode Indication | +| | | | | | | TSG-GERAN#2 - November 2000 | +| 05.09 | G02 | A014 | R99 | 8.1.0 | 8.2.0 | Clarification on decision thresholds | +| 05.09 | G02 | A016 | R99 | 8.1.0 | 8.2.0 | Alignment of ACS change with Layer 3 signalling | +| | | | | | | TSG-GERAN#3 - January 2001 | +| 05.09 | G03 | A018 | R99 | 8.2.0 | 8.3.0 | Clarification in Transmitter/Receiver Synchronisation | +| 45.009 | G03 | | Rel4 | 8.3.0 | 4.0.0 | Release 4 version | + +| Change history | | | | | | | | +|----------------|------------|-----------|------|-----|--------------------------------------------------------------------------|--------|--------| +| Date | TSG GERAN# | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2001-01 | 03 | GP-010332 | A017 | 1 | Changes to link adaptation for AMR wideband codec on GSMK TCH | 4.0.0 | 5.0.0 | +| 2001-08 | 06 | GP-011948 | 002 | 2 | RATSCCH protocol: repetition of REQ messages and other corrections | 5.0.0 | 5.1.0 | +| 2001-11 | 07 | GP-012354 | 003 | | Introduction of adaptive half rate speech channels with 8-PSK modulation | 5.1.0 | 5.2.0 | +| 2001-11 | 07 | GP-012378 | 005 | | Correction of references to relevant 3GPP specification | 5.1.0 | 5.2.0 | +| 2001-11 | 07 | GP-012744 | 007 | 1 | CHANNEL MODE MODIFY, phase and RATSCCH | 5.1.0 | 5.2.0 | +| 2002-02 | 08 | GP-020463 | 009 | 2 | Clarification on MS response to the Codec Mode Command | 5.2.0 | 5.3.0 | +| 2002-04 | 09 | GP-020648 | 011 | | Active codec set after a RATSCCH AMR_CONFIG REQ message | 5.3.0 | 5.4.0 | +| 2002-04 | 09 | GP-021171 | 012 | 1 | Alignment of number of codecs for WB-AMR to proposed set | 5.3.0 | 5.4.0 | +| 2002-04 | 09 | GP-021207 | 013 | 1 | Introduction of AMR-WB on 8PSK modulated speech traffic channels | 5.3.0 | 5.4.0 | +| 2002-06 | 10 | GP-021414 | 015 | | Editorial clean up of references | 5.4.0 | 5.5.0 | +| 2003-11 | 17 | GP-032775 | 016 | 1 | DTM assignment & AMR default inband signalling phase | 5.5.0 | 6.0.0 | +| 2004-02 | 18 | GP-040168 | 017 | | Reference channel for AMR codec mode adaptation | 6.0.0 | 6.1.0 | +| 2005-06 | 25 | GP-051770 | 018 | 2 | Re-definition of channel quality measure used for AMR link adaptation | 6.1.0 | 6.2.0 | +| 2007-08 | 35 | | | | Version for Release 7 | 6.2.0 | 7.0.0 | +| 2008-12 | 40 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | 44 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 2010-05 | 46 | GP-100762 | 0021 | | Introduction of Shifted SACCH for VAMOS | 9.0.0 | 9.1.0 | +| 2011-03 | 49 | | | | Version for Release 10 | 9.1.0 | 10.0.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 2013-08 | 59 | GP-130681 | 0022 | | Introduction of VAMOS III MS | 11.0.0 | 12.0.0 | +| 2014-11 | 64 | GP-140877 | 0024 | 3 | Introduction of extended TSC sets | 12.0.0 | 12.1.0 | +| 2015-12 | 68 | | | | Version for Release 13 (frozen at SP-70) | 12.1.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Version for Release 15 (frozen at TSG-80) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/45_series/45015/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/45_series/45015/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de4b0e3462467229572432178e98689f17f74a6f --- /dev/null +++ b/marked/Rel-18/45_series/45015/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96ad596f084c01dd846c30eae9bcc3f7a153f95fc50d66749fc8459a76c66a26 +size 8593 diff --git a/marked/Rel-18/45_series/45015/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/45_series/45015/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b632375bc3d2c71da1094020e31c012f233a9b2 --- /dev/null +++ b/marked/Rel-18/45_series/45015/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51f069a3a1077d48ddef3bf9887471884fafe16fc0b35768de474e632369eda5 +size 14995 diff --git a/marked/Rel-18/45_series/45015/raw.md b/marked/Rel-18/45_series/45015/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..11b1dbee49e46cb76ad56950a04f487590664474 --- /dev/null +++ b/marked/Rel-18/45_series/45015/raw.md @@ -0,0 +1,170 @@ + + +# 3GPP TS 45.015 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; GSM/EDGE Release independent Downlink Advanced Receiver Performance (DARP); Implementation guidelines (Release 18)** + +![GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS'](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for the Global System for Mobile Communications (GSM) is displayed in blue. It features the letters 'GSM' in a stylized font, with a small red square above the 'M'. Below the letters, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller, blue, sans-serif font. + +GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The logo for the 3rd Generation Partnership Project (3GPP) is displayed in black. It features the letters '3GPP' in a stylized font, with a small red signal icon below the 'P'. A small 'TM' symbol is located to the top right of the 'P'. + +3GPP logo + +## --- **Keywords** + +GSM, radio + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +### --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +- Foreword ..... 4 +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Definitions and abbreviations ..... 5 + - 3.1 Abbreviations ..... 5 +- 4 Void..... 5 +- 5 DARP Phase II MS Independent of Release..... 6 + - 5.1 RF Requirements..... 6 + - 5.2 Signalling Requirements ..... 6 +- Annex A (informative): Change history..... 7** + +## --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +## --- 1 Scope + +The present document specifies requirements on MSs supporting Downlink Advanced Receiver Performance (DARP) that are independent of release. TSG GERAN has agreed that the standardisation of DARP be independent of a release. However, in order to implement an MS that conforms to a particular release but supports DARP, which is specified in a later release, it is necessary to specify some extra requirements. + +DARP - phase II is contained in the Release 7 specifications. In order to implement an MS conforming to Release 5 but supporting DARP – phase II, it is necessary for the MS to additionally conform to some parts of the Release 7 specifications, such as the radio frequency requirements for DARP and some signalling extensions relating to the MS Classmark and radio access capabilities. + +## --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] (void) +- [2] (void) +- [3] 3GPP TS 45.005: "Radio transmission and reception (Release 7)". +- [4] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core Network protocols; Stage 3 (Release 7)". + +## --- 3 Definitions and abbreviations + +Unless listed below, all definitions and abbreviations used in the present document are listed in documents referenced in clause 2. + +## 3.1 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|------------------------------------------------------------------------| +| DARP | Downlink Advanced Receiver Performance | +| SAIC | Single Antenna Interference Cancellation, also known as DARP - phase I | +| MSRD | Mobile Station Receive Diversity, also known as DARP - phase II | + +## --- 4 Void + +## 5 DARP Phase II MS Independent of Release + +MSs that conform to Release 5 and support DARP - phase II shall support the following requirements in Release 7. + +## 5.1 RF Requirements + +The MS shall comply with the RF requirements for DARP - phase II specified in [3]. These requirements are: + +Section 6.2: Reference sensitivity level. + +Section 6.3: Reference interference level. + +## 5.2 Signalling Requirements + +The MS shall support the following information elements specified in [4]: + +Section 10.5.1.7 Mobile Station Classmark 3, with the following exceptions: + +- Fields T-GSM 400 Bands Supported / T-GSM 400 Associated Radio Capability, T-GSM 900 Associated Radio Capability, DTM GPRS High Multi Slot Class / Offset required / DTM EGPRS High Multi Slot Class, GSM 710 Associated Radio Capability, T-GSM 810 Associated Radio Capability, and Multislot Capability Reduction for Downlink Dual Carrier shall be indicated as not present since they are not defined in Release 5. This is done by setting the related indication bit to '0'. +- Parameter DTM Enhancement Capability, Repeated ACCH Capability and Ciphering Mode Setting Capability shall be indicated as not supported since it is not defined in Release 5. This is done by setting the bit value '0' for this parameter. + +Section 10.5.5.12a MS Radio Access Capability, with the following exceptions: + +- Fields DTM GPRS High Multi Slot Class / DTM EGPRS High Multi Slot Class, Multislot Capability Reduction for Downlink Dual Carrier, and Downlink Dual Carrier for DTM Capability shall be indicated as not present since they are not defined in Release 5. This is done by setting the related indication bit to '0'. +- Parameters Multiple TBF Capability, Extended RLC/MAC Control Message Segmentation Capability, DTM Enhancements Capability, PS Handover Capability, and DTM Handover Capability shall be indicated as not supported since they are not defined in Release 5. This is done by setting the bit value '0' for each of these parameters. +- In addition, for Access Technology Type, the values '1001' through to '1101' shall not be used since GSM T 380, GSM T 410, GSM T 900, GSM 710 and GSM T 810 are not supported in Release 5. + +NOTE: The lack of one or more of the fields following the Downlink Advanced Receiver Performance field in Mobile Station Classmark 3 IE or MS Radio Access Capability IE should not be considered as an error by the network. In this case the meaning "not supported" or "not present" should be assumed as indicated above. + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-11 | 22 | GP-042854 | | | Version for Release 5 | | 5.0.0 | +| 2006-01 | 28 | GP-060330 | 0004 | 2 | Release independent DARP Implementation guidelines update | 5.0.0 | 5.1.0 | +| 2007-05 | 34 | GP-071051 | 0005 | 1 | Release independent DARP Implementation guidelines update | 5.1.0 | 5.2.0 | +| 2007-05 | 34 | GP-07105 | 0006 | 1 | Release independent DARP Implementation guidelines update | 5.2.0 | 6.1.0 | +| 2007-08 | 35 | | | | Version for Release 7 | 6.1.0 | 7.0.0 | +| 2008-12 | 40 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | 44 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 2011-03 | 49 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 2014-09 | 63 | | | | Version for Release 12 (frozen at SP-65) | 11.0.0 | 12.0.0 | +| 2015-12 | 68 | | | | Version for Release 13 (frozen at SP-70) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Version for Release 15 (frozen at TSG-80) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/45_series/45022/051638d871c75230edb3d005fa668810_img.jpg b/marked/Rel-18/45_series/45022/051638d871c75230edb3d005fa668810_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6eaba3941c7c0d01abaaf03c7186cace50dfb51 --- /dev/null +++ b/marked/Rel-18/45_series/45022/051638d871c75230edb3d005fa668810_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c61e4b232633a019f954a6609a11ee65c5b81bc6093a25fc0826ae87b1c69c2 +size 53302 diff --git a/marked/Rel-18/45_series/45022/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Rel-18/45_series/45022/1dbb1d90b2022a3a765c85929a515cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b95f2721e51287f93d5c44856216dde45fa8c62 --- /dev/null +++ b/marked/Rel-18/45_series/45022/1dbb1d90b2022a3a765c85929a515cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82dbcf83bf5cb34889e80cd362b2f52aa595476d6acbf6a69d3ed5c5daec323f +size 11222 diff --git a/marked/Rel-18/45_series/45022/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg b/marked/Rel-18/45_series/45022/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f5aa6b087eeebb431050fc8eb06c7a127c11ef3 --- /dev/null +++ b/marked/Rel-18/45_series/45022/1eb72b1e2fe3920b483f6245e5d477e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f55dbeed06f38dd9b274806b42bcbc71593886bda28e6b6c63b7a68cf498943b +size 61167 diff --git a/marked/Rel-18/45_series/45022/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg b/marked/Rel-18/45_series/45022/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e382f9dfebf089e2ec3231551af8d5f22fc2fa97 --- /dev/null +++ b/marked/Rel-18/45_series/45022/24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e3ee323b35fbe993eff0142edab7af5891b3e4bb17b1e4a49f852127d7ede40 +size 33131 diff --git a/marked/Rel-18/45_series/45022/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg b/marked/Rel-18/45_series/45022/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65e1db678a107cb5357f2d683aa5bde97502469e --- /dev/null +++ b/marked/Rel-18/45_series/45022/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca28180e13a79c4853c7386dccbc75038823f1c237084dd8ce2be1298b7e1170 +size 8309 diff --git a/marked/Rel-18/45_series/45022/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/45_series/45022/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69bbce34cb2dd0e4daa9954624b5c1b1b20e7c36 --- /dev/null +++ b/marked/Rel-18/45_series/45022/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd3017aec3544c92abbd53276c979d686b93fc1fed6dae3eece08c72918a1af4 +size 81948 diff --git a/marked/Rel-18/45_series/45022/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/45_series/45022/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10fe296eafb228c1e10fbc8f48a66e870a188f4a --- /dev/null +++ b/marked/Rel-18/45_series/45022/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a87fa4519ab0df624d34924762e4a9e74523a230462ff442ba04515dfab49a84 +size 114543 diff --git a/marked/Rel-18/45_series/45022/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-18/45_series/45022/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b97c74eeb815bebe3e6f944fac60da71f5d3776 --- /dev/null +++ b/marked/Rel-18/45_series/45022/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e51a8ee45b7a7bd08f32f5d4dbe7facb922a9a5c0d34b6d2576d45f61aa81be9 +size 84713 diff --git a/marked/Rel-18/45_series/45022/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-18/45_series/45022/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17175a187042d0e3bcc81b6e2d9619bddbcaabb6 --- /dev/null +++ b/marked/Rel-18/45_series/45022/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:771476589ec42efbbb8be3746f07c7ccb3fcc67d7f8d3cb522b8a17fbb1a9680 +size 62108 diff --git a/marked/Rel-18/45_series/45022/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-18/45_series/45022/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbe62fad51dd2fa28a0f9829e9ac033d47d593ab --- /dev/null +++ b/marked/Rel-18/45_series/45022/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:135a95793bf8fbeebee70e4a164477efe2a78ad8159f432037f4371b2a296b09 +size 19593 diff --git a/marked/Rel-18/45_series/45022/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/45_series/45022/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..695c090bc4049761aa3c4addfe490883c6c6b991 --- /dev/null +++ b/marked/Rel-18/45_series/45022/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0afdf9c7a1c7e58b184cf7c82221bd552c195f9bf5d4a36fed702d079526ce32 +size 8727 diff --git a/marked/Rel-18/45_series/45022/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-18/45_series/45022/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a6385e34770a76fcf48dfc27b8861bf696ead66 --- /dev/null +++ b/marked/Rel-18/45_series/45022/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dd23a64745bdac1dee6a783e30118ce5ad78768d12436ad36c6e70f9bab1507 +size 31529 diff --git a/marked/Rel-18/45_series/45022/62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg b/marked/Rel-18/45_series/45022/62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd6f1914ab51625be6c4ef2c672986ba0f12efc4 --- /dev/null +++ b/marked/Rel-18/45_series/45022/62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f725655c149b9a400e290d8b50745d91aefe86d331dd1d0c4afa54a6c585a44d +size 62470 diff --git a/marked/Rel-18/45_series/45022/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/45_series/45022/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac55d01af2599d55f833d5ac4a047bba969f4e8c --- /dev/null +++ b/marked/Rel-18/45_series/45022/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cb23fa3b12a8d1e9cb4b9293eb744fe8ec93ee9273094b1909b9cc693e510ca +size 14671 diff --git a/marked/Rel-18/45_series/45022/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-18/45_series/45022/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d21ee1e30e6b91b0b6ec9d0f61c89ed95373f1b --- /dev/null +++ b/marked/Rel-18/45_series/45022/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2731b6df4ad8b6e758deb45b6dedc30007f3d3f2dbd93955a10396bb53d98239 +size 41548 diff --git a/marked/Rel-18/45_series/45022/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-18/45_series/45022/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01108ae9db1114bea134d5a240ccad77dc8507ea --- /dev/null +++ b/marked/Rel-18/45_series/45022/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623aa042913b75143df8eb74b16c2784ed7f49abb51a354cbcd5463e287b61e4 +size 77964 diff --git a/marked/Rel-18/45_series/45022/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/45_series/45022/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cad9a591a1773d41b513b92cceeb8d50e0b282e0 --- /dev/null +++ b/marked/Rel-18/45_series/45022/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afccb1a206bb1fe6b3f05ebcad1dbcd95aaba70fc30d25922634c3709b1a4a0f +size 63939 diff --git a/marked/Rel-18/45_series/45022/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-18/45_series/45022/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4f1d158f590ffe51478dc5abc5f972c23622ffc --- /dev/null +++ b/marked/Rel-18/45_series/45022/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:501d76c92e642b2891d8111dda78b807d7ba71dd53210fcb08a344edb4e0196b +size 84179 diff --git a/marked/Rel-18/45_series/45022/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-18/45_series/45022/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2e935e1a465a9df4fbea1a3a7dfc41fa0364a2b --- /dev/null +++ b/marked/Rel-18/45_series/45022/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa22ec04bbeb1e763ad1b4ba8b5c7808dbd3645890651af11a0035d82105edd4 +size 81092 diff --git a/marked/Rel-18/45_series/45022/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/45_series/45022/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1554dde8ce23ec333ab05a0651362290d6c00c13 --- /dev/null +++ b/marked/Rel-18/45_series/45022/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1d391a5408a1ad976bd7da299fb3b43f63232de2311052a5c3d0e0980ad5c3c +size 34467 diff --git a/marked/Rel-18/45_series/45022/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/Rel-18/45_series/45022/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c77c17ef27a0230113a40b4260037980717b5c5 --- /dev/null +++ b/marked/Rel-18/45_series/45022/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25a1196f5bc52844313732100a93f714a786b18e1b8d793bbefb3757e0f20ca6 +size 85081 diff --git a/marked/Rel-18/45_series/45022/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg b/marked/Rel-18/45_series/45022/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..025d46cfd82af0e9548171d43196460ba9db24e3 --- /dev/null +++ b/marked/Rel-18/45_series/45022/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b5086ce23fd38e0824a5096b5a26d412372e2827029eb87db3a2c19e6001eb +size 55347 diff --git a/marked/Rel-18/45_series/45022/bac21fd48fcd7f025c723590e07d1823_img.jpg b/marked/Rel-18/45_series/45022/bac21fd48fcd7f025c723590e07d1823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..704dc6ce0671d7499c637d1a0f80a2b93977f810 --- /dev/null +++ b/marked/Rel-18/45_series/45022/bac21fd48fcd7f025c723590e07d1823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf77506b255ada74576c9668628383da41f5420ef683f74c538440d06e3f9b47 +size 59515 diff --git a/marked/Rel-18/45_series/45022/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/marked/Rel-18/45_series/45022/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4d4dd464f1ccee0c7aea61e8351a9c61ba9400a --- /dev/null +++ b/marked/Rel-18/45_series/45022/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd4b0a1e1f6106def0a6db5871abea934847ec0f7903bdfbb3af79aa8cb6957a +size 11999 diff --git a/marked/Rel-18/45_series/45022/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-18/45_series/45022/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaf94c1a86d3b43bd3f9d60eddaaa2df73982ea1 --- /dev/null +++ b/marked/Rel-18/45_series/45022/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67596c94330877fe98bca0e9103961324a9c8aea9a0154d25b7bbc3454153efe +size 72674 diff --git a/marked/Rel-18/45_series/45022/raw.md b/marked/Rel-18/45_series/45022/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..85f19dde28d19ea9266fea7e7a1ad69c743b4ddf --- /dev/null +++ b/marked/Rel-18/45_series/45022/raw.md @@ -0,0 +1,1698 @@ + + +# 3GPP TS 45.022 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; GSM/EDGE Radio link management in hierarchical networks (Release 18)** + +![GSM logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +**GSM**® +GLOBAL SYSTEM FOR +MOBILE COMMUNICATIONS + +GSM logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +**3GPP**™ + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, radio, management + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|-------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Abbreviations ..... | 7 | +| 4 General ..... | 7 | +| 5 Hierarchical networks ..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 Cell types..... | 8 | +| 5.2.1 Large cells ..... | 8 | +| 5.2.2 Small cells ..... | 8 | +| 5.2.3 Microcells ..... | 8 | +| 6 Idle mode procedures..... | 9 | +| 7 Examples of handover and RF power control algorithms..... | 9 | +| 7.1 General ..... | 9 | +| Annex A (informative): Example 1 (Siemens AG) ..... | 10 | +| A.1 Introduction..... | 10 | +| A.2 Functional requirements..... | 10 | +| A.3 BSS pre-processing and threshold comparisons ..... | 11 | +| A.3.1 Measurement averaging process ..... | 11 | +| A.3.2 Handover threshold comparison process..... | 11 | +| A.4 BSS decision algorithm..... | 12 | +| A.5 Additional O&M parameters stored for handover purposes in hierarchical networks ..... | 12 | +| A.6 Bibliography..... | 13 | +| Annex B (informative): Example 2 (DeTeMobil)..... | 14 | +| B.1 Introduction..... | 14 | +| B.2 Definitions..... | 14 | +| B.2.1 Categories of cells ..... | 14 | +| B.2.2 Classification of MS in connected mode..... | 15 | +| B.2.2.1 Classification in the lower layer..... | 15 | +| B.2.2.2 Classification in the middle layer or the upper layer..... | 15 | +| B.2.2.3 Loss of the "slow MS" or "quasi-stationary MS" status..... | 16 | +| B.3 Power Control Algorithm..... | 16 | +| B.3.1 MS connected over a cell of the lower layer..... | 16 | +| B.3.2 MS connected over a cell of the middle layer or the upper layer..... | 16 | +| B.4 Handover algorithm in a hierarchical cell structure..... | 16 | +| B.4.1 MS connected over a cell of the lower layer..... | 16 | +| B.4.2 MS connected over a cell of the middle layer or the upper layer..... | 17 | +| B.4.3 Handover at borders of different cell structures..... | 17 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------|-----------| +| B.5 | O&M-Parameter..... | 17 | +| B.6 | State diagrams..... | 18 | +| Annex C (informative): | Example 3 (Alcatel) ..... | 21 | +| C.1 | General description ..... | 21 | +| C.1.1 | Speed discrimination..... | 21 | +| C.2 | Handover causes ..... | 22 | +| C.2.1 | Emergency causes ..... | 22 | +| C.2.2 | Better cell causes..... | 22 | +| C.3 | Dwell time in lower layer cells: ..... | 22 | +| C.3.1 | Serving cell = lower layer cell..... | 22 | +| C.3.2 | Serving cell = upper layer cell..... | 22 | +| C.3.3 | Mechanism of increasing / decreasing tdwell ..... | 22 | +| C.4 | Speed discrimination process:..... | 23 | +| C.4.1 | Serving cell = upperlayer cell..... | 23 | +| C.4.2 | Serving cell = lower layer cell..... | 23 | +| C.5 | Representation of handovers..... | 24 | +| C.5.1 | Ideal behaviour: target cells are available..... | 24 | +| C.5.2 | Real behaviour: target cells may not be available..... | 24 | +| C.6 | Emergency handover..... | 25 | +| C.6.1 | Target cell = upper layer cell..... | 25 | +| C.7 | Upper layer to lower layer cells handover ..... | 26 | +| C.7.1 | General principles ..... | 26 | +| C.7.2 | Homogeneity of speed discrimination in lower layer and upper layer cells ..... | 26 | +| C.8 | Minicells..... | 26 | +| C.8.1 | Handover diagrams ..... | 26 | +| C.9 | O&M parameters..... | 27 | +| Annex D (informative): | Example 4 (France Telecom/CNET) ..... | 28 | +| D.1 | Introduction..... | 28 | +| D.2 | Descriptions of the algorithm..... | 29 | +| D.3 | Handover causes ..... | 29 | +| D.3.1 | emergency handover causes..... | 29 | +| D.3.2 | mobile speeds estimation causes..... | 29 | +| D.4 | Mobile speeds estimations ..... | 30 | +| D.4.1 | Estimation of the field strength variations ..... | 30 | +| D.5 | BSS decision algorithm..... | 31 | +| D.6 | O&M parameters..... | 31 | +| D.7 | Examples..... | 32 | +| D.8 | State diagrams..... | 35 | +| D.8.1 | Case of a three layers hierarchical network ..... | 35 | +| D.8.2 | Case of a two layers hierarchical network ..... | 36 | +| Annex E (informative): | Simulation Model for Handover Performance Evaluation in Hierarchical Cell Structures ..... | 38 | +| E.1 | Introduction..... | 38 | +| E.2 | Mobile Environment ..... | 38 | +| E.3 | Radio Network Model..... | 38 | +| E.3.1 | Scenario 1: Hot Spot ..... | 38 | + +| | | | +|-------------------------------|-----------------------------------------------------------|-----------| +| E.3.2 | Scenario 2: Line of Cells..... | 39 | +| E.3.3 | Scenario 3: Manhattan Coverage ..... | 39 | +| E.4 | Propagation Model..... | 39 | +| E.4.1 | Upper Layer Path Loss..... | 39 | +| E.4.1.1 | Macrocells ..... | 39 | +| E.4.1.2 | Small cells ..... | 40 | +| E.4.2 | Lower Layer Path Loss ..... | 41 | +| E.4.2.1 | Line-of-sight Case ..... | 41 | +| E.4.2.2 | Non Line-of-sight Case ..... | 42 | +| E.4.2.3 | Shape of the level with the proposed path loss model..... | 42 | +| E.4.3 | Fading..... | 43 | +| E.5 | Motion Model ..... | 43 | +| E.6 | Handover Algorithms..... | 44 | +| E.7 | Measurement Reporting..... | 44 | +| E.8 | Performance Criteria..... | 44 | +| E.9 | Open Issues ..... | 44 | +| Annex F (informative): | Change history..... | 45 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document gives examples for the Radio sub-system link control to be implemented in the Base Station System (BSS) and Mobile Switching Centre (MSC) of the GSM and DCS 1 800 systems in case hierarchical cell structures are employed. + +Unless otherwise specified, references to GSM also include DCS 1 800, and multiband systems if operated by a single operator. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 03.22 (ETS 300 930): "Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [2] 3GPP TR 03.30 (ETR 364): "Radio network planning aspects". +- [3] 3GPP TS 45.008: "Radio subsystem link control". +- [4] 3GPP TR 01.04 (ETR 350): "Abbreviations and acronyms". + +# --- 3 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 01.04 [4]. + +# --- 4 General + +ETS 300 911 (GSM 05.08 [3]) specifies the radio sub system link control implemented in the Mobile Station (MS), Base Station System (BSS) and Mobile Switching Centre (MSC) of the GSM and DCS 1 800 systems of the European digital cellular telecommunications system (Phase 2). + +The present document gives several examples of how the basic handover and RF power control algorithm as contained in (informative) annex A to ETS 300 911 [3] can be enhanced to cope with the requirements on the radio subsystem link control in hierarchical networks. + +A hierarchical network is a network consisting of multiple layers of cells, allowing for an increased traffic capacity and performance compared to a single layer network. + +The radio sub-system link control aspects that are addressed are as follows: + +- Handover; +- RF Power control. + +# --- 5 Hierarchical networks + +## 5.1 General + +In a hierarchical, or microcellular network, traffic is supported on multiple layers of cells. Typically, a network operator could implement a layer consisting of microcells as a second layer in his existing network consisting of large or small cells. The addition of this second layer would improve the capacity and coverage of his network. + +In the present document the following naming convention is used for the different layers. For a network consisting of three layers the layer using the biggest cells is the "upper layer", followed by the "middle layer", and then the "lower layer" which has the smallest cells. For a network consisting of two layers, only "upper layer" and "lower layer" are used. + +The intention in a hierarchical network is to use the radio link control procedures to handle the majority of the traffic in the lower layer, i.e. the smallest cells, as this will limit interference and therefore improve the frequency reuse. + +However, a part of the traffic cannot always efficiently be handled in the lower layer. Examples are cases where the MS is moving fast (relative to the cell range), or where the coverage is insufficient, or where a cell to make a handover to on the same level may not be available fast enough (going around corners, entering/leaving buildings). + +## 5.2 Cell types + +GSM 03.30 [2] distinguishes between three kinds of cells: large cells, small cells and micro cells. The main difference between these kinds lies in the cell range, the antenna installation site, and the propagation model applying: + +### 5.2.1 Large cells + +In large cells the base station antenna is installed above the maximum height of the surrounding roof tops; the path loss is determined mainly by diffraction and scattering at roof tops in the vicinity of the mobile i.e. the main rays propagate above the roof tops; the cell radius is minimally 1 km and normally exceeds 3 km. Hata's model and its extension up to 2 000 MHz (COST 231-Hata model) can be used to calculate the path loss in such cells (GSM 03.30 [2] annex B). + +### 5.2.2 Small cells + +For small cell coverage the antenna is sited above the median but below the maximum height of the surrounding roof tops and so therefore the path loss is determined by the same mechanisms as stated in subclause 5.1.1. However large and small cells differ in terms of maximum range and for small cells the maximum range is typically less than 1-3 km. In the case of small cells with a radius of less than 1 km the Hata model cannot be used. + +The COST 231-Walfish-Ikegami model (see GSM 03.30 [2] annex B) gives the best approximation to the path loss experienced when small cells with a radius of less than 5 km are implemented in urban environments. It can therefore be used to estimate the BTS ERP required in order to provide a particular cell radius (typically in the range 200 m - 3 km). + +### 5.2.3 Microcells + +COST 231 defines a microcell as being a cell in which the base station antenna is mounted generally below roof top level. Wave propagation is determined by diffraction and scattering around buildings i.e. the main rays propagate in street canyons. COST 231 proposes an experimental model for microcell propagation when a free line of sight exists in a street canyon (see GSM 03.30 [2]). + +The propagation loss in microcells increases sharply as the receiver moves out of line of sight, for example, around a street corner. This can be taken into account by adding 20 dB to the propagation loss per corner, up to two or three corners (the propagation being more of a guided type in this case). Beyond, the complete COST231-Walfish-Ikegami model as presented in annex B of GSM 03.30 [2] should be used. + +Microcells have a radius in the region of 200 to 300 metres and therefore exhibit different usage patterns from large and small cells. + +# --- 6 Idle mode procedures + +GSM 03.22 [1] outlines how idle mode operation shall be implemented. Further details are given in Technical Specifications GSM 04.08 and GSM 05.08 [3]. + +A useful feature for hierarchical networks is that cell prioritization, for Phase 2 MS, can be achieved during cell reselection by the use of the reselection parameters optionally broadcast on the BCCH. Cells are reselected on the basis of a parameter called C2 and the C2 value for each cell is given a positive or negative offset (CELL\_RESELECT\_OFFSET) to encourage or discourage MSs to reselect that cell. A full range of positive and negative offsets is provided to allow the incorporation of this feature into already operational networks. + +The parameters used to calculate C2 are as follows: + +- a) CELL\_RESELECT\_OFFSET; +- b) PENALTY\_TIME; + +When the MS places the cell on the list of the strongest carriers as specified in GSM 05.08 [3], it starts a timer which expires after the PENALTY\_TIME. This timer will be reset when the cell is taken off the list. For the duration of this timer, C2 is given a negative offset. This will tend to prevent fast moving MSs from selecting the cell. + +- c) TEMPORARY\_OFFSET; + +This is the amount of the negative offset described in (ii) above. An infinite value can be applied, but a number of finite values are also possible. + +The permitted values of these parameters and the way in which they are combined to calculate C2 are defined in GSM 05.08 [3]. + +# --- 7 Examples of handover and RF power control algorithms. + +## 7.1 General + +In the following annexes four examples of handover and power control algorithms are presented. All of these are considered sufficient to allow successful implementation in hierarchical or microcellular networks. None of these solutions is mandatory. + +The "**Description of algorithm**" of each annex, contains a text as provided by the authors of the algorithm. Any discussion on the algorithms is contained in a separate clause, "**Discussion of algorithm**". + +# --- Annex A (informative): Example 1 (Siemens AG) + +## Description of algorithm + +Source: Siemens AG + +Date: 23.08.95 + +Subject: Fast Moving Mobiles + +## --- A.1 Introduction + +This annex specifies an enhanced handover algorithm that may be implemented in GSM or DCS 1 800 hierarchical networks. In accordance with clause 5 of this annex a hierarchical network is understood as a network utilizing large cells for the upper layer for wide area coverage, and a lower layer structure of small or micro cells for capacity reasons. For the sake of simplicity the algorithm is described for hierarchical networks consisting of two layers. Nevertheless the algorithm can be extended to a hierarchy comprising several layers. + +The algorithm is based upon the basic handover process, as described in GSM 05.08 [3], annex A. Only differences and supplements to the standard algorithms are explicitly described. + +The aim of this annex is to show, how in hierarchical networks useless handovers can be avoided by allocating the mobiles, according to their speed, to the appropriate cell type. This goal is achieved by steering the fast mobile stations to the upper layer structure (e.g. large cells), while ensuring that slow mobile subscribers are served by the lower layer structure (e.g. small or micro cells). A mobile station is considered as fast, if its sojourn time in a cell is short compared to a mean call holding time. + +An important aspect of this advanced algorithm is, that there is no implication on the MS type. The procedures described in this annex, work in the same manner for Phase 2 as well as Phase 1 MS types. + +A more comprehensive description of the advanced algorithm along with some investigation results based on handover emulations in typical mixed cell scenarios is given in "Mobile Speed Sensitive Handover in a Mixed Cell Environment" (see Bibliography). + +## --- A.2 Functional requirements + +The present algorithm is based on the following additional assumptions: + +- the upper layer structure (e.g. large cells) provides a contiguous wide area coverage for all MS power classes to be supported by the network; +- the lower layer structure (e.g. small or micro cells) is fully embedded in the coverage area of upper layer structure (e.g. large cells); +- the algorithm is based on both a power budget and absolute level criterion. Therefore both criteria shall be enabled simultaneously, giving a higher priority to the absolute level criterion. + +## A.3 BSS pre-processing and threshold comparisons + +### A.3.1 Measurement averaging process + +In a mixed cell environment one should take into account the different propagation conditions in large and small or micro cells, and the requirement for speeding up the handover decision, when a handover out of a small cell is pending (especially, with the street corner effect in micro cells), an excessive delay of the handover detection can cause a loss of the connection. Regarding this, the following items are recommended: + +- apply different values for the averaging parameters in large and small or micro cells, respectively; +- define separate averaging parameters applicable to RXLEV and RXLEV\_NCELL(n), respectively; +- the BSS shall evaluate the Power Budget PBGT(n) using the averaging process defined for RXLEV\_NCELL(n). + +### A.3.2 Handover threshold comparison process + +The Handover threshold comparison process is similar to the process described in GSM 05.08 [3], annex A, except for section e) in A.3.2.2, which is modified as follows: + +- Comparison of PBGT(n) with the variable hysteresis margin HO\_MARGIN\_TIME(n). If the process is employed, the action to be taken is as follows: + +If PBGT(n) > HO\_MARGIN\_TIME(n) a handover, cause PBGT(n), might be required. + +In a hierarchical network this comparison enables handover into the lower layer structure (e.g. small or micro cells) to be performed for slow mobile stations, while fast-moving ones remain served by the upper layer structure (e.g. large cells). + +The variable hysteresis margin is defined by: + +$$HO\_MARIGIN\_TIME(n) = HO\_MARIGIN(n) + HO\_STATIC\_OFFSET(n) - HO\_DYNAMIC\_OFFSET(n) * H(T(n) - DELAY\_TIME(n)).$$ + +In addition to the HO\_MARGIN(n) as defined in table A.1 of GSM 05.08 [3] except that the range has been extended to (-24, 24 dB), the variable hysteresis margin comprises: + +- a static offset, HO\_STATIC\_OFFSET(n); +- a dynamic offset, HO\_DYNAMIC\_OFFSET(n); and +- a delay time interval, DELAY\_TIME(n). + +The parameters are related to cells of the lower layer structure only. + +T(n) is the time that has elapsed since the point at which the mobile station has entered the coverage area of cell n in the lower layer structure. + +The function H(x) is defined by: + +$$H(x) = \begin{cases} 0 & \text{for } x < 0 \\ 1 & \text{for } x \geq 0 \end{cases}, \text{ with } x = T(n) - DELAY\_TIME(n).$$ + +The simultaneous fulfilment of the following conditions indicates that the mobile station has entered the coverage area of cell n in the lower layer structure: + +**Condition 1:** RXLEV\_NCELL(n) > RXLEV\_MIN(n) + Max(0, Pa) + +**Condition 2:** PBGT(n) > HO\_MARGIN(n), + +where Pa = MS\_TXPWR\_MAX(n) - P. + +If both conditions are true, a timer $T(n)$ shall be started. If any of these conditions gets false, before the timer expiry, the timer shall be stopped and reset. + +NOTE 1: $HO\_MARGIN\_TIME(n) = HO\_MARGIN(n) + HO\_STATIC\_OFFSET(n)$ for those cells of the lower layer structure, whose timer has not yet been started or is still running. A high value of $HO\_STATIC\_OFFSET$ effectively prevents a handover into the respective cell of the lower layer structure during the run time of the timer for that cell. + +NOTE 2: $HO\_MARGIN\_TIME(n) = HO\_MARGIN(n) + HO\_STATIC\_OFFSET(n) - HO\_DYNAMIC\_OFFSET(n)$ + +for those cells of the lower layer structure, whose timer has expired. This is the margin fixing the cell borders and replacing the usual $HO\_MARGIN(n)$ within the standard handover of GSM 05.08 [3], annex A. + +On timer expiry the reduced $HO\_MARGIN\_TIME(n)$ allows for a power budget handover into a cell of the lower layer structure for a slow moving mobile which is expected to be still in the coverage area of that cell. + +On the contrary, a fast moving mobile is expected to have left the coverage area of an embedded cell of the lower layer structure while the timer for that cell is still running and therefore Condition 1 or 2 (or both) will be violated, thus preventing a handover request for a fast moving mobile into that cell of the lower layer structure. Consequently, fast moving mobiles are kept on the upper layer structure. + +NOTE 3: A fast moving mobile connected to a cell of the lower layer structure (e.g. a phase 1 mobile being not able to run the reselection algorithm in idle mode or a mobile having changed its speed) is steered to the upper layer structure by requesting for it a rescue handover based on the absolute level criterion. + +NOTE 4: $HO\_MARGIN(n)$ defines the location of timer start. Choosing small or even negative values results in an early timer start and thereby avoiding cell border displacement and interference problems. Setting $HO\_MARGIN(n)$ to large negative values effectively cancels Condition 2, and consequently the timer start is triggered only by Condition 1 such that the cell borders on the lower layer structure are independent of the cell site positions with respect to the cell sites in the upper layer structure. + +## A.4 BSS decision algorithm + +The BSS decision algorithm described in GSM 05.08 [3], annex A, may be employed after replacing $HO\_MARGIN(n)$ by the corresponding $HO\_MARGIN\_TIME(n)$ in equation (2) of annex A. In combination with suitable parameter settings this results in the mobile speed sensitive handover functionality referenced above. + +## A.5 Additional O&M parameters stored for handover purposes in hierarchical networks + +$HO\_STATIC\_OFFSET(n)$ A parameter used to apply a positive offset to $HO\_MARGIN(n)$ in order to prevent a handover request into cell $n$ of the lower layer structure. + +Range: 0 - 127 dB + +Step Size: 1 dB. + +Admin. for: $HO\_STATIC\_OFFSET(n)$ for each neighbour cell of the lower layer structure ( $n = 1 - 32$ ) + +HO\_DYNAMIC\_OFFSET(n) A parameter used to partially or fully compensate the HO\_STATIC\_OFFSET(n) for cell n of the lower layer structure. This parameter gets active after the time interval DELAY\_TIME(n). + +Range: 0 - 127 dB + +Step Size: 1 dB. + +Admin. for: HO\_DYNAMIC\_OFFSET(n) for each neighbour cell of the lower layer structure (n = 1 - 32) + +DELAY\_TIME(n) Time interval used to delay the handover decision into cell n of the lower layer structure to enable differentiation between fast and slow mobile stations in the handover decision process. + +Range: 0 - 255 Tsacch + +Step Size: 1 Tsacch + +Admin. for: DELAY\_TIME(n) for each neighbour cell of the lower layer structure (n = 1 - 32) + +NOTE: These parameters apply only for cells of the lower layer structure. + +## --- A.6 Bibliography + +- 1) K. Ivanov, G. Spring, "Mobile Speed Sensitive Handover in a Mixed Cell Environment", in Proc. IEEE 45th Veh. Technol. Conf., VTC 1995, pp. 892-896. + +# --- Annex B (informative): Example 2 (DeTeMobil) + +## Description of algorithm + +Source: DeTeMobil + +Date: 21.08.1995 + +Subject: High speed MS + +## --- B.1 Introduction + +In order to provide significantly more traffic capacity in GSM networks, the average cell size has to become smaller. The reduction in cell size, however, should neither limit the mobility of the MS nor the MS speed. On the one hand problems will occur if the MS are so fast, that the time they stay in a small cell is too short for the radio link control procedures to be carried out efficiently and effectively and on the other hand if it is necessary to handover a MS to predetermined target cells very quickly if the received RF signal level of a radio connection is changing rapidly in a radio environment of small cells. + +To give good performance to all MS, the network has to be built up using cells of different sizes at one place, i.e. a hierarchical cell structure. The network provides a multi-coverage. Dependent on the MS speed, the MS shall be handled by a cell with a suitable size. + +The procedures to achieve this for an MS in idle mode are described in GSM 03.22 [1]. + +The radio link control procedures in the concept of a hierarchical cell structure are independent of the connections to MSC and BSC. + +In the following the procedures to handle MS in connected mode for a hierarchical cell structure are given. + +## --- B.2 Definitions + +### B.2.1 Categories of cells + +A hierarchical cell structure is built up from different layers of cells. The structure shall allow at least three layers: the lower layer, the middle layer and the upper layer (see note). If only two layers are planned, the lower layer and middle layer are used. It is emphasized that the relation to other cells determines the assignment to a layer in the hierarchical cell structure. The absolute size of a cell is not a criterion. + +NOTE 1: An example for the use of middle and upper layer is as follows: + +- Middle layer: Layer with sufficient capacity to handle the traffic for fast moving MS. +- Upper layer: "Umbrella Cells" of the middle layer, here only handover traffic shall be supported, when cells of the middle layer are not available. + +The layer to which a cell in a hierarchical cell structure is assigned is set by the O&M-parameter CELL\_LEVEL. + +Cells that do not belong into a hierarchical structure (single layer) have the CELL\_LEVEL "standard layer" that is the default level if details concerning the CELL\_LEVEL are missing. + +The parameter CELL\_LEVEL has a range from 0 to 15 (see note) and is allocated for each radio cell. The coding is given in clause B.5. In each radio cell the own level, and the levels for all neighbour cells, as in the BA(SACCH), are known. + +NOTE 2: Possible reasons to introduce new layers may be: pico cells, specific services supported only in one layer, multiband systems etc. + +### B.2.2 Classification of MS in connected mode + +For radio link control purposes in a hierarchical cell structure, an MS in connected mode is classified by a set of at least eight status-fields. The set is called MS\_STATUS. With one of these fields: MS\_SPEED, MS are distinguished between "fast MS", "slow MS" and "quasi-stationary MS". All other fields of the set are for future use (see note) + +NOTE: Possible details given in the fields that are for future use are: multiple band, GPRS, EFR etc.. + +MS\_STATUS is used in decisions of the power control process. + +At the establishment of an RR-connection MS\_SPEED is set to the default value "fast MS", except for Phase 2 MS if establishment is in cells of the lower layer in which the path loss criterion C2 is activated. Then MS\_SPEED is set to "slow MS". + +The speed classification can be enabled/disabled by the flag EN\_MS\_SPEED. + +If the flag EN\_MS\_SPEED is set to 0 (disabled) in a cell of the lower layer the classification is omitted, and the status of the MS in this cell will not be changed. At the establishment of an RR-connection all MS are set to the MS\_SPEED default value "fast MS". During handover the MS shall keep the status of the previous cell. + +In cells of the middle layer or the upper layer, all cells of the lower layer with the flag EN\_MS\_SPEED disabled, are excluded from the classification procedure as described in subclause B.2.2.2. + +#### B.2.2.1 Classification in the lower layer + +For each RR-connection supported by a cell of the lower layer a counter $C_{s(tay)}$ is started. The counter $C_s$ has an initial value 0, and is incremented by 1 with every SACCH-multiframe. When the value of counter $C_s$ equals the threshold C\_SLOW\_STAT and the MS has MS\_SPEED "fast MS", the MS MS\_SPEED is set to "slow MS". If the value of the counter $C_s$ satisfies the condition $C_s \leq C\_QS\_STAT$ the MS MS\_SPEED is set from "slow MS" to "quasi-stationary MS". + +Both parameters C\_SLOW\_STAT and C\_QS\_STAT are adjustable by O&M (see clause B.5), subject to the condition: $C\_SLOW\_STAT < C\_QS\_STAT$ . It is envisaged that an adaptive procedure is developed for this adjustment to handle the inherent complexity of this procedure. The operator shall have the possibility to select between both the setting per O&M and by procedure. + +The counter $C_s$ is stopped and reset to 0 when the call is released or an intercell handover is performed. The counter shall go on in case of a successful intracell channel change. The MS\_SPEED status of the MS is kept during handover or intracell channel change independent of where the handover is controlled (MSC or BSC). + +#### B.2.2.2 Classification in the middle layer or the upper layer + +During a call supported by a cell of the middle layer or the upper layer a counter $C_{a(vailable)(n)}$ is started for each cell of the lower layer with the flag EN\_MS\_SPEED set to 1 (enabled), that is reported in the measurement reports, and fulfils the following equation: + +$$RXLEV\_NCELL(n) > RXLEV\_MIN(n) + LAYER\_HYST(n) + \text{Max}\{0, MS\_TXPWR\_MAX(n) - P\}$$ + +where n is the respective adjacent cell "n". + +With every measurement report the counter $C_a(n)$ is incremented by 1 for each reported cell of the lower layer which still fulfils the inequation, otherwise $C_a(n)$ is decremented by 1. All counters $C_a(n)$ are stopped and reset to 0 when the call is finished in that cell. + +When at least p (with $p = 1, \dots, 4$ , see clause B.5) counters $C_a(n)$ reach the value C\_SLOW\_STAT(n) the MS is estimated to be slow enough to be supported by cells of the lower layer. The MS MS\_SPEED is set to "slow MS". A handover to a cell of the lower layer is initiated (see subclause B.4.2). The value $p = 1$ should be used as default value. + +NOTE: $p \geq 1$ gives the possibility in special cases, where information on the velocity of MS is not reliable, e.g. in the surroundings of traffic lights, to tighten the requirement for the handover towards the lower layer of MS. $p=1$ is sufficient in most cases. + +#### B.2.2.3 Loss of the "slow MS" or "quasi-stationary MS" status + +During an RR-connection, when a handover from a cell of the lower layer to a cell of the middle layer or the upper layer is performed, the MS MS\_SPEED is set to "fast MS". This happens when a handover with cause RXLEV, RXQUAL or distance occurs before the counter $C_s$ reaches the value C\_SLOW\_STAT. + +Furthermore, in the case that no radio resource is available in one of the higher layers, and the handover is performed to a cell of the lower layer, the MS MS\_SPEED is set to "fast MS". + +## --- B.3 Power Control Algorithm + +### B.3.1 MS connected over a cell of the lower layer + +In cells of the lower layer the power control algorithm shall be dependent on the MS MS\_SPEED. + +For a "fast MS" power control shall be [disabled]. The maximum allowed power level for that cell and for the class of MS has to be used by MS and BSS. + +For MS with MS\_SPEED "slow MS" or "quasi-stationary MS" the power control process as described in annex A of 05.08 [3] is used, with the following proviso: + +In case of a MS with MS\_SPEED "quasi-stationary MS" the power control ranges and the averaging periods are the same as used in the middle layer/upper layer or standard layer. + +For MS with MS\_SPEED "slow MS" the maximum allowed power in uplink and downlink may be reduced only by [five] 2 dB steps. For slow MS an separate set of power control parameters, for example for POW\_INCR/RED\_STEP\_SIZE and P\_CON\_INTERVAL shall be used. + +### B.3.2 MS connected over a cell of the middle layer or the upper layer + +For all MS connected via the middle- or upper layer the power control process as described in the 05.08 [3] are used. + +## --- B.4 Handover algorithm in a hierarchical cell structure + +### B.4.1 MS connected over a cell of the lower layer + +After the successful establishment of an RR-connection in a cell of the lower layer, the counter $C_s$ is started for this connection. In addition to the classification of MS (see subclause B.2.2), the counter is used to measure the time an MS stays in the cell of the lower layer. + +If a handover with cause RXLEV, RXQUAL or distance occurs before $C_s$ has reached the threshold C\_SLOW\_STAT, the handover is performed with preference to a cell of the middle layer. Only if no TCH is available in the middle layer, a cell of the upper layer is selected as handover-candidate. In case there is no cell or TCH available in the higher layers, the handover candidate shall be a cell from the lower layer. As long as the value of $C_s$ is smaller than C\_SLOW\_STAT a handover cause PBGT is not possible. + +When $C_s$ is equal or greater than C\_SLOW\_STAT all handover types are possible to all cells of the lower layer regardless of the MS MS\_SPEED ("slow MS" or "quasi-stationary MS"). If no cell of the lower layer is available for a forced handover, the handover candidate shall be a cell from the middle layer or in case of unavailability from the upper + +layer. Only under this condition the MS retains MS\_SPEED "slow MS" or "quasi-stationary MS" during a handover from lower layer to either middle layer or upper layer. In case of a PBGT-handover, the handover candidate list may only contain cells from the lower layer. + +### B.4.2 MS connected over a cell of the middle layer or the upper layer + +For RR-connections supported by cells of the middle layer or the upper layer a standard handover procedure as specified e.g. in annex A of 05.08 [3] is used with the additions and restrictions as follows. + +The counter $C_a(n)$ that is started for each cell of the lower layer (see subclause B.2.2), is used to trigger a handover from an actual serving cell of a higher level to a cell of the lower layer. + +When at least $p$ counters $C_a(n)$ reach the value $C\_SLOW\_STAT(n)$ the MS is estimated to be slow enough, so that it can be supported by cells of the lower layer. + +As long as the above condition is not fulfilled, the handover from a cell of the middle layer/upper layer to a cell of the lower layer is not allowed with the exception for the handover causes RXLEV, RXQUAL or DISTANCE that only the lower layer has free resources. + +When $C_a(n)$ reaches the value $C\_SLOW\_STAT(n)$ for at least $p$ cells of the lower layer, a handover is initiated towards the lower layer. All available cells of the lower layer are possible handover candidates. The handover shall be performed to that cell of the lower layer which has the best PBGT. + +If the $p$ -th counter $C_a(n)$ reaches the value $C\_SLOW\_STAT(n)$ at the same time that a handover cause PBGT is recognized, the PBGT-handover has to be performed. + +### B.4.3 Handover at borders of different cell structures + +A border appears where an area with an hierarchical cell structure adjoins an area consisting of a single layer of cells. + +For an MS that moves from the area with an hierarchical cell structure into the area with a single layer of cells, these cells of the standard layer are treated like cells of the middle layer. + +In case of an MS moving from the single standard layer towards the hierarchical cell structure, for the purpose of radio link purposes there is no distinction between the cells of the hierarchical cell structure. This is because no information is available on the hierarchical structure in the standard layer. + +## B.5 O&M-Parameter + +| | | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CELL_LEVEL | Hierarchy level of serving cell
Range: 0 - 15
Step size: 1
Coding:
0: standardlayer
1: lower layer
2: middle layer
3: upper layer
4 - 15: for future use
Used in: BSC
Admin. for: CELL_LEVEL for each cell | +| CELL_LEVEL_NC(n) | Hierarchy level of n-th neighbour cell
n: 1 - 32
Range: 0 - 15
Step size: 1
Coding:
0: standardlayer
1: lower layer
2: middle layer
3: upper layer
4 - 15: for future use | + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Used in: BSC
Admin. for: CELL_LEVEL_NC(n) for each adjacent cell n of a radio cell | +| EN_MS_SPEED | ENable classification of MS regarding SPEED
Coding: 1: enable feature
0: disable feature
Used in: BSC
Admin. for: each cell | +| C_SLOW_STAT | Time an MS has to stay in a cell of the lower layer until MS_SPEED is set to "slow MS"
Range: 0 - 255 T SACCH
Step Size: 1 T SACCH
Used in: BSC
Admin. for: C_SLOW_STAT for each cell of the lower layer
Conditions: 1. C_SLOW_STAT < C_QS_STAT
2. C_SLOW_STAT = C_SLOW_STAT(n) related to one cell | +| C_SLOW_STAT(n) | Time neighbour cell n of the lower layer has to be reported as suitable by an MS supported by the middle layer or upper layer until MS_SPEED is set to "slow MS"
Range: 0 - 255 T SACCH
Step Size: 1 T SACCH
Used in: BSC
Admin. for: C_SLOW_STAT(n) for each adjacent lower layer cell n of a middle layer or upper layer cell (n = 1 - 32)
Conditions: 1. C_SLOW_STAT < C_QS_STAT
2. C_SLOW_STAT = C_SLOW_STAT(n) related to one cell | +| C_QS_STAT | Time an MS has to stay in a cell of the lower layer until MS_SPEED is set to "Quasi-stationary MS"
Range: 0 - 510 T SACCH
Step Size: 2 T SACCH
Used in: BSC
Admin. for: each cell
Condition: C_QS_STAT > C_SLOW_STAT | +| LAYER_HYST(n) | Hysteresis for handover from the middle layer/upper layer to the lower layer
Range: 0 - [31] dB
Step Size: 1 dB
Used in: BSC
Admin. for: each neighbour cell | +| p | number of cells that has to fulfil the inequation to estimate an MS as slow
Range: 1 - 4
Step Size: 1
Used in: BSC
Admin. for: each cell of the middle layer or upper layer | + +## B.6 State diagrams + +### Radio Resource Establishment: + +![Flowchart showing Idle Mode transitions to different cell layers based on RR estimates.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +graph TD + IdleMode[Idle Mode] -- "RR est. Ph.2-MS" --> LLC1[Lower Layer Cell MS Status: slow] + IdleMode -- "RR est. Ph.1-MS" --> LLC2[Lower Layer Cell MS Status: fast] + IdleMode -- "RR est. Ph.1/2-MS" --> MUC[Middle Layer/ Upper Layer Cell MS Status: fast] + +``` + +Flowchart showing Idle Mode transitions to different cell layers based on RR estimates. + +### Handover Cases to the preferred cell layer: + +![Complex state transition diagram for handover cases between cell layers and MS statuses.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` + +stateDiagram-v2 + [*] --> LLC1[Lower Layer Cell MS Status: fast] + [*] --> LLC2[Lower Layer Cell MS Status: slow] + [*] --> LLC3[Lower Layer Cell MS Status: qs] + LLC1 --> LLC2 : status change: C_SLOW_STAT ≤ Cs < C_QS_STAT + LLC2 --> LLC1 : status change: Cs ≥ C_QS_STAT + LLC2 --> LLC3 : status change: Cs ≥ C_QS_STAT + LLC3 --> LLC2 : status change: C_SLOW_STAT ≤ Cs < C_QS_STAT + LLC1 --> MUC1[Middle Layer/ Upper Layer Cell MS Status: fast] : HO necessary* Cs < C_SLOW_STAT + LLC2 --> MUC2[Middle Layer/ Upper Layer Cell MS Status: slow] : HO necessary* Cs < C_SLOW_STAT + LLC3 --> MUC3[Middle Layer/ Upper Layer Cell MS Status: qs] : HO necessary* Cs < C_SLOW_STAT + MUC1 --> LLC1 : HO necessary Ca fulfilled** + MUC1 --> LLC2 : HO necessary Ca fulfilled** + MUC2 --> LLC2 : HO: Ca fulfilled** + MUC3 --> LLC3 : HO: Ca fulfilled** + MUC1 --> MUC1 : HO necessary Ca not fulfilled** + MUC2 --> MUC1 : HO necessary Ca not fulfilled** + MUC3 --> MUC1 : HO necessary Ca not fulfilled** + MUC1 --> LLC1 : HO necessary* Cs < C_SLOW_STAT + MUC2 --> LLC2 : HO necessary* Cs < C_SLOW_STAT + MUC3 --> LLC3 : HO necessary* Cs < C_SLOW_STAT + LLC1 --> [*] : HO necessary* Cs < C_SLOW_STAT + LLC2 --> [*] : HO necessary* Cs < C_SLOW_STAT + LLC3 --> [*] : HO necessary* Cs < C_SLOW_STAT + +``` + +Complex state transition diagram for handover cases between cell layers and MS statuses. + +Notes: + \* all handover types except PBGT-HO + \*\* Ca fulfilled: Ca(n) ≥ C\_SLOW\_STAT(n) for at least p cells + +#### Handover Cases, that occur if no resources in the preferred cell layer are available: + +![State transition diagram for MS Status (fast, slow, qs) across Middle/Upper Layer Cells and Lower Layer Cells. Transitions are labeled with HO necessary* and Ca fulfilled** conditions.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MLC_fast: Middle Layer/Upper Layer Cell MS Status: fast + [*] --> MLC_slow: Middle Layer/Upper Layer Cell MS Status: slow + [*] --> MLC_qs: Middle Layer/Upper Layer Cell MS Status: qs + + MLC_fast --> MLC_fast: Status change: Ca fulfilled** + MLC_fast --> MLC_slow: HO necessary* Cs = C_SLOW_STAT + MLC_fast --> MLC_qs: HO necessary* Cs = C_QS_STAT + MLC_fast --> LLC_fast: HO necessary* Ca not fulfilled** + MLC_fast --> LLC_slow: HO necessary* Ca fulfilled** + MLC_fast --> LLC_qs: HO necessary* Ca fulfilled** + + MLC_slow --> MLC_slow: HO necessary Ca fulfilled** + MLC_slow --> MLC_fast: HO necessary* Ca not fulfilled** + MLC_slow --> MLC_qs: HO necessary* Ca fulfilled** + MLC_slow --> LLC_fast: HO necessary* Cs < C_SLOW_STAT + MLC_slow --> LLC_slow: HO necessary* C_SLOW_STAT ≤ Cs < C_QS_STAT + MLC_slow --> LLC_qs: HO necessary* Cs ≥ C_QS_STAT + + MLC_qs --> MLC_qs: HO necessary Ca fulfilled** + MLC_qs --> MLC_fast: HO necessary* Ca not fulfilled** + MLC_qs --> MLC_slow: HO necessary* Ca fulfilled** + MLC_qs --> LLC_fast: HO necessary* Cs < C_SLOW_STAT + MLC_qs --> LLC_slow: HO necessary* C_SLOW_STAT ≤ Cs < C_QS_STAT + MLC_qs --> LLC_qs: HO necessary* Cs ≥ C_QS_STAT + + LLC_fast --> LLC_fast: HO necessary* Cs < C_SLOW_STAT + LLC_fast --> LLC_slow: HO necessary* Cs = C_SLOW_STAT + LLC_fast --> LLC_qs: HO necessary* Cs < C_SLOW_STAT + LLC_fast --> MLC_fast: HO necessary* Ca not fulfilled** + LLC_fast --> MLC_slow: HO necessary* Ca fulfilled** + LLC_fast --> MLC_qs: HO necessary* Ca fulfilled** + + LLC_slow --> LLC_slow: HO necessary* C_SLOW_STAT ≤ Cs < C_QS_STAT + LLC_slow --> LLC_fast: HO necessary* Cs < C_SLOW_STAT + LLC_slow --> LLC_qs: HO necessary* Cs ≥ C_QS_STAT + LLC_slow --> MLC_fast: HO necessary* Ca not fulfilled** + LLC_slow --> MLC_slow: HO necessary* Ca fulfilled** + LLC_slow --> MLC_qs: HO necessary* Ca fulfilled** + + LLC_qs --> LLC_qs: HO necessary* Cs ≥ C_QS_STAT + LLC_qs --> LLC_fast: HO necessary* Cs < C_SLOW_STAT + LLC_qs --> LLC_slow: HO necessary* C_SLOW_STAT ≤ Cs < C_QS_STAT + LLC_qs --> MLC_fast: HO necessary* Ca not fulfilled** + LLC_qs --> MLC_slow: HO necessary* Ca fulfilled** + LLC_qs --> MLC_qs: HO necessary* Cs < C_QS_STAT + +``` + +State transition diagram for MS Status (fast, slow, qs) across Middle/Upper Layer Cells and Lower Layer Cells. Transitions are labeled with HO necessary\* and Ca fulfilled\*\* conditions. + +Notes: + +\* all handover types except PBGT-HO + +\*\* Ca fulfilled: Ca(n) ≥ C\_SLOW\_STAT(n) for at least p cells + +# Annex C (informative): Example 3 (Alcatel) + +## Description of algorithm + +## C.1 General description + +This annex describes a handover algorithm in hierarchical networks, i.e. with 2 layers of cells. The lower layer cells may be minicells or microcells, as expressed in the following figures. + +![Diagram of the first scenario: microcells below existing cells.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +The diagram illustrates two layers of cells. The top layer consists of several large, overlapping ellipses representing "existing cells" with a radius range of $1 < R < 2$ km. Below this, there is a dense, regular grid of much smaller ellipses representing "microcells" with a radius $R < 300$ m. The microcells are arranged in a repeating pattern of three-lobed clusters. + +Diagram of the first scenario: microcells below existing cells. + +**Figure C.1: First scenario: microcells below existing cells** + +![Diagram of the second scenario: 'super umbrella cell' above existing minicells.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +The diagram illustrates a different hierarchy. At the top is a single, very large ellipse representing a "Super umbrella cell" with a radius of $R \sim 20$ km. Below it is a layer of "existing cells" (or minicells) represented by overlapping ellipses with a radius range of $1 < R < 2$ km, similar to the top layer in Figure C.1. + +Diagram of the second scenario: 'super umbrella cell' above existing minicells. + +**Figure C.2: Second scenario: "super umbrella cell" above existing minicells** + +This annex deals mainly with microcells below upper layer cells. The case of mini cells is expressed in clause C.8. The general philosophy of this algorithm is to handle a maximum of traffic in the lower layer cells. The upper layer cell is used as a "rescue" cell when a problem occurs. This will be detailed in clause C.6. + +### C.1.1 Speed discrimination + +To avoid a high rate of handovers fast moving mobiles are sent and kept in the upperlayer cells. This speed discrimination is based on the dwell time of a mobile in a lower layer cell. A mobile handled by lower layer cells is sent to the upper layer cell if the delay between successive handovers becomes small. Furthermore a mobile handled by an upper layer cell is sent to a lower layer cell if it receives from this cell a high level of signal for a sufficient time. This is based on a "leaky bucket" mechanism which is described in clause C.3. + +## --- C.2 Handover causes + +These causes are classified in two classes: **emergency** causes, which should remain exceptional and request a quick and safe reaction, and "**better cell**" causes. + +### C.2.1 Emergency causes + +An emergency handover is due to a problem in the serving cell and a handover is necessary in a short delay in order not to lose the call. Emergency handover causes can be: + +- too low quality on either direction (uplink or downlink), +- too low received level in either direction, +- distance too long. + +This list is not necessarily exhaustive. + +### C.2.2 Better cell causes + +A "better cell" handover is triggered when the call would be better handled by another cell, to optimize interferences, or reduce the signalling load of the network, or separate fast/slow moving mobiles. This list is not necessarily exhaustive. + +Traditional "Better cell" causes are: + +- PBGT - power budget for neighbour cell greater than a threshold. PBGT is checked only between cells of the same layer. +- Upper layer to lower layer cell - good received level in neighbour lower layer cell, with slow MS, when the serving cell is an upper layer cell. + +The only cause which is described in details in the present document is the "upper layer to lower layer" cause which is new. The other ones are well known (see annex A of GSM 05.08 [3]) and are not described here. + +## --- C.3 Dwell time in lower layer cells: + +The speed discrimination process is based on the dwell time in a lower layer cell. This time is expressed by $tdwell$ or by $cdwell$ ( $c$ for counter): $cdwell = 2 * tdwell$ . + +This relation comes from the fact that $tdwell$ (external parameter) is in seconds when $cdwell$ (internal parameter) is in SACCH frames. + +### C.3.1 Serving cell = lower layer cell + +The observed dwell time is the dwell time in the serving cell: $tdwell(s)$ - $s$ : serving cell, or $tdwell(0)$ + +### C.3.2 Serving cell = upper layer cell + +The dwell time is observed in each of the neighbour lower layer cells: $tdwell(n)$ - $1 \leq n \leq 64$ + +### C.3.3 Mechanism of increasing / decreasing $tdwell$ + +- $tdwell(s)$ + +$tdwell(s)$ starts at 0 when the call begins in the cell (after call set-up or intercell handover). + +Each SACCH period $tdwell$ is incremented by 0.5. + +$tdwell(s)$ is maintained after an intracell handover. + +- $tdwell(n)$ - "Leaky bucket" mechanism + +When a channel (SDCCH or TCH) is allocated in an upper layer cell (after call set-up or handover), the following process starts: + +A counter $tdwell(n)$ is set to 0 for each neighbour cell $n$ . + +Each time a measurement result is received , for each of the declared $n$ neighbour cells: + +- If the reported raw received level $RXLEV\_NCELL(n)$ of the $BTS(n)$ is above a threshold $L\_RXLEV\_OCHO(n)$ , the counter $tdwell(n)$ is incremented by 0.5. +- Each time the received level is below this limit or no measurement is received, the counter $tdwell(n)$ is decreased by 0,5 with a minimum value of 0. + +## --- C.4 Speed discrimination process: + +### C.4.1 Serving cell = upperlayer cell + +A handover is realized if the dwell time of a mobile in lower layer cell is above a threshold: + +$$tdwell(n) \geq MIN\_DWELL\_TIME$$ + +This will forbid a fast moving mobile being sent to lower layer cell as the dwell time for each of the crossed cells never reaches the threshold. The handover is realized toward the lower layer cell which has triggered the handover cause. + +### C.4.2 Serving cell = lower layer cell + +- Emergency handover: + +Whatever the time elapsed in the serving cell, any emergency handover sends the call to the upper layer cell which is considered as a "rescue" cell. + +- PBGT + +Depending on the time elapsed in the serving cell, the call is transferred to the lower layer cell or to the upper layer cell. + +If the dwell time in the serving cell is high enough ( $tdwell(0) \geq MIN\_CONNECT\_TIME$ ), the mobile may be considered as a slow moving mobile and the call is sent to the lower layer cell which has triggered the cause. + +If the dwell time is low (below the threshold), the mobile is considered as a fast moving mobile. To avoid a high number of handovers, the call is sent preferentially to the upper layer cell. + +This test on the dwell time is realized only if there has already been a PBGT handover from another lower layer cell. This is to avoid sending a call to the upper layer cell in the following cases + +- call initiated at the limit of the lower layer cell, +- call transferred from the upper layer cell to the lower layer cell just before reaching the limit of the lower layer cell, +- after external handover: no information on the precedent cell and on the handover cause. This will be the case for all interlayer handovers when both layers are provided by different manufacturers. + +## C.5 Representation of handovers + +### C.5.1 Ideal behaviour: target cells are available + +![State diagram showing handover transitions between an Upper layer cell and two Microcells. Transitions include RACH, external HO, HO emergency, PBGT, and conditions based on dwell time.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +The diagram illustrates the state transitions between an **Upper layer cell** and two **Microcell** units. The **Upper layer cell** is at the top, and the two **Microcell** units are at the bottom. Transitions are as follows: + +- RACH** and **external HO** are external inputs to the **Upper layer cell**. +- A self-loop on the **Upper layer cell** is labeled "emergency HO + PBGT". +- A transition from **Upper layer cell** to the left **Microcell** is labeled "upper to lower: $Tdwell(n) > MIN\_DWELL\_TIME$ ". +- A transition from the left **Microcell** to the **Upper layer cell** is labeled "HO emergency". +- A transition from the **Upper layer cell** to the right **Microcell** is labeled "HO emergency". +- A transition from the right **Microcell** to the **Upper layer cell** is labeled "PBGT and $tdwell < MIN\_CONNECT\_TIME$ ". +- A transition from the left **Microcell** to the right **Microcell** is labeled "PBGT". +- A self-loop on the right **Microcell** is labeled "PBGT and $tdwell > MIN\_CONNECT\_TIME$ ". +- RACH** and **external HO** are external inputs to the left **Microcell**. + +State diagram showing handover transitions between an Upper layer cell and two Microcells. Transitions include RACH, external HO, HO emergency, PBGT, and conditions based on dwell time. + +Figure C.3: Handovers in case of availability of the target cell + +### C.5.2 Real behaviour: target cells may not be available + +The handover that may occur to non preferred target cells due to the unavailability of TCH resources are indicated with dotted line arrows in the state diagram. + +![Figure C.4: state diagram showing handover logic between an Upper layer cell and two Microcells. Transitions include RACH, external HO, HO emergency, PBGT, and conditions like Tdwell(n) > MIN_DWELL_TIME or tdwell < MIN_CONNECT_TIME. A legend indicates dashed arrows are used in case of non availability of the preferred cell.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates the state transitions between an Upper layer cell and two Microcells. The Upper layer cell has self-loops for 'emergency HO + PBGT'. Transitions from the Upper layer cell to a Microcell are labeled 'HO emergency' and 'upper to lower: Tdwell(n) > MIN\_DWELL\_TIME'. Transitions between the two Microcells are labeled 'PBGT' and 'HO emergency'. Transitions from a Microcell back to the Upper layer cell are labeled 'HO emergency'. External HO and RACH inputs are shown for both the Upper layer cell and the Microcells. A legend at the bottom left shows a dashed arrow pointing to the text 'in case of non availability of the preferred cell'. + +Figure C.4: state diagram showing handover logic between an Upper layer cell and two Microcells. Transitions include RACH, external HO, HO emergency, PBGT, and conditions like Tdwell(n) > MIN\_DWELL\_TIME or tdwell < MIN\_CONNECT\_TIME. A legend indicates dashed arrows are used in case of non availability of the preferred cell. + +Figure C.4: state diagram + +## C.6 Emergency handover + +### C.6.1 Target cell = upper layer cell + +When the serving cell is a microcell, the preferred target cell is always an upper layer cell. If another microcell was accepted as target cell, there would be an important risk to choose the wrong cell (the adjacent cell when the right one is the perpendicular cell) and thus to lose the call. + +![Figure C.5: diagram showing a mobile station (MS) moving from microcell μBTS1 towards a street corner. μBTS3 is the upper layer cell at the corner, and μBTS2 is an adjacent microcell. The MS is shown moving from μBTS1 towards μBTS3.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +The diagram shows a mobile station (MS) moving from microcell μBTS1 towards a street corner. At the corner is an upper layer cell μBTS3. An adjacent microcell μBTS2 is located on the other side of the corner. The MS is shown moving from μBTS1 towards μBTS3, illustrating the potential for an emergency handover. + +Figure C.5: diagram showing a mobile station (MS) moving from microcell μBTS1 towards a street corner. μBTS3 is the upper layer cell at the corner, and μBTS2 is an adjacent microcell. The MS is shown moving from μBTS1 towards μBTS3. + +Figure C.5: + +In the figure above, let us suppose that the mobile is initially connected to the $\mu$ BTS1. When it turns at the street corner, depending on its speed, there is a high probability it does not trigger a PBGT on the $\mu$ BTS 3 before detecting an emergency handover cause (crossing the high threshold). If a microcell was possible as a target cell, the $\mu$ BTS 2 would be chosen as the mobile receives good measurement reports from this cell for a while. The $\mu$ BTS 3 is either still not reported (due to the delay necessary in the mobile to get synchronization on a new cell), or reported for a short time with an insufficient average level. + +The choice of $\mu$ BTS 2 is of course very bad. + +## C.7 Upper layer to lower layer cells handover + +### C.7.1 General principles + +- based on the dwell time in a lower layer cell: it depends on the reported measurements from neighbour lower layer cells. + +The counter used to estimate this dwell time is based on a "leaky bucket" mechanism, as described in clause C.3. + +### C.7.2 Homogeneity of speed discrimination in lower layer and upper layer cells + +Theoretically the dwell time limit in a lower layer cell should be the same when this cell is the serving cell or the neighbour cell: $MIN\_CONNECT\_TIME = MIN\_DWELL\_TIME$ . + +To avoid Ping-Pong effect there must be the following relationship: + +$$MIN\_CONNECT\_TIME \leq MIN\_DWELL\_TIME$$ + +This is to avoid the MS to be declared fast by the microcell and slow by the upper layer cell. + +## C.8 Minicells + +With minicells there are some differences compared to microcells: there is no street corner effect. Thus there is no risk in sending a mobile to another minicell when an emergency handover is triggered. The diagram of handovers becomes the following: + +### C.8.1 Handover diagrams + +![Simplified handover diagram for minicells showing transitions between an Upper layer cell and two Minicells with various triggers like RACH, external HO, and dwell time conditions.](62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg) + +The diagram illustrates handover logic for minicells. At the top is an 'Upper layer cell'. It receives 'RACH' and 'external HO' inputs. It has a self-loop labeled 'all HO causes \*'. Below it are two 'Minicell' boxes. A diagonal arrow points from the 'Upper layer cell' to the left 'Minicell', labeled 'upper to lower: $T_{dwell}(n) > MIN\_DWELL\_TIME$ '. The left 'Minicell' receives 'RACH' and 'external HO' inputs and has a self-loop labeled 'all HO causes \*: except cause umbrella to minicell'. A horizontal arrow labeled 'PBGT' points from the left 'Minicell' to the right 'Minicell'. A diagonal arrow points from the right 'Minicell' back to the 'Upper layer cell', labeled 'all HO causes \* and $t_{dwell} < MIN\_CONNECT\_TIME$ '. The right 'Minicell' has a self-loop labeled 'all HO causes \* and $t_{dwell} > MIN\_CONNECT\_TIME$ '. + +Simplified handover diagram for minicells showing transitions between an Upper layer cell and two Minicells with various triggers like RACH, external HO, and dwell time conditions. + +Figure C.6: Simplified handover diagram for minicells + +![Complete handover diagram for minicells showing transitions between an Upper layer cell and two Minicells with various triggers and conditions.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +The diagram illustrates the handover logic for minicells. At the top is an 'Upper layer cell' box. It receives 'RACH' and 'external HO' inputs. It has a self-loop labeled 'all HO causes \*'. Below it are two 'Minicell' boxes. The left Minicell receives 'RACH' and 'external HO' inputs. A solid arrow points from the Upper layer cell to the left Minicell, labeled 'upper to lower: $Tdwell(n) > MIN\_DWELL\_TIME$ '. A dashed arrow points from the left Minicell back to the Upper layer cell, labeled 'HO emergency'. A solid arrow points from the left Minicell to the right Minicell, labeled 'PBGT'. A dashed arrow points from the right Minicell back to the Upper layer cell, labeled 'Emergency HO and $tdwell > MIN\_CONNECT\_TIME$ '. A solid arrow points from the right Minicell back to the Upper layer cell, labeled 'all HO causes \* and $tdwell < MIN\_CONNECT\_TIME$ '. The right Minicell has a dashed self-loop labeled 'HO emergency and $tdwell < MIN\_CONNECT\_TIME$ '. Below the right Minicell is a solid self-loop labeled 'all HO causes \* and $tdwell > MIN\_CONNECT\_TIME$ '. A legend at the bottom left shows a dashed arrow pointing to the text 'in case of non availability of the preferred cell'. A note below the left Minicell states 'all HO causes \*: except cause umbrella to minicell'. + +Complete handover diagram for minicells showing transitions between an Upper layer cell and two Minicells with various triggers and conditions. + +**Figure C.7: Complete handover diagram for minicells** + +## C.9 O&M parameters + +- MIN\_CONNECT\_TIME: + +Minimum time the mobile has to stay in the lower layer cell to be considered as slow, when the serving cell is the microcell. + +- MIN\_DWELL\_TIME: + +Value of the timer MIN\_DWELL\_TIME to send a call from an upper layer cell to a lower layer cell. + +- L\_RXLEV\_OCHO(n): + +Minimum receive LEVel on downlink for upper layer to neighbour lower layer Cell n HandOver. + +# Annex D (informative): Example 4 (France Telecom/CNET) + +## Description of algorithm + +Source: France Telecom/CNET + +Date: 22.06.95 + +Subject: Informative annex for high speed MS + +## D.1 Introduction + +In order to increase the capacity of an existent GSM mobile network (composed with large cells), the total number of cell has to be increased and the average cell radius has to be decreased (-> small cells). If this solution is not sufficient to provide the required capacity, a hierarchical network can be developed by adding antenna on the streets. Such cells are called microcell and the corresponding layer is called lowerlayer. + +Nevertheless to optimize the quality of service for high speed mobiles, large cells or small cells are still used as an overlay which is called upperlayer. + +The algorithm presented below (gradient algorithm) provides a mean to spread mobiles on the layers depending of their speed. + +Figure D.1 features different kinds of cells and layers. + +![Diagram illustrating a hierarchical network with three layers: Upperlayer, Middlelayer, and Lowerlayer. The Upperlayer contains a 'Large cell' and two 'Small cell' units. The Middlelayer contains two 'Microcell' units. The Lowerlayer contains two 'Microcell' units. A red car is shown in the Middlelayer, and a person is shown in the Lowerlayer.](ead623e6a8ec701df64567695a57d01c_img.jpg) + +The diagram illustrates a hierarchical network structure with three layers represented by overlapping ellipses. The top layer, labeled 'Upperlayer', contains a 'Large cell' and two 'Small cell' units. The middle layer, labeled 'Middlelayer', contains two 'Microcell' units. The bottom layer, labeled 'Lowerlayer', contains two 'Microcell' units. A red car is shown in the Middlelayer, and a person is shown in the Lowerlayer. The background features stylized buildings. + +Diagram illustrating a hierarchical network with three layers: Upperlayer, Middlelayer, and Lowerlayer. The Upperlayer contains a 'Large cell' and two 'Small cell' units. The Middlelayer contains two 'Microcell' units. The Lowerlayer contains two 'Microcell' units. A red car is shown in the Middlelayer, and a person is shown in the Lowerlayer. + +**Figure D.1: Representation of the different kinds of cells and layers** + +In the case of a two layers hierarchical network, the uppest layer is called upperlayer whatever the type of its cells (large cell or small cell). + +## D.2 Descriptions of the algorithm + +Mobile speed is estimated from the variation of the field strength received by the mobile from the target cell. + +This method of estimation is based on the computation of the gradient between two averages of the field strength received by the mobile from the target cell (see subclause D.4.1 Estimation of the field strength variations). This algorithm can be used in any kind of multicellular network (composed with two layers or more than two layers). + +Considering the case of a network composed with three layers. + +A "fast" mobile connected to a cell of the lowerlayer must handover towards a cell of the middlelayer. Nevertheless the field strength received from the cell of the middlelayer must be high enough to trigger the handover. + +A "slow" mobile connected to the lowerlayer must handover towards a cell of the same layer. + +In both cases the estimation of mobile speeds are based on the field strength received from a cell of the lowerlayer. + +A "fast" mobile connected to a cell of the upperlayer must handover towards a cell of the same layer. + +A "slow" mobile connected to a cell of the upperlayer must handover to a cell of the middlelayer. In both cases the estimation of mobile speeds are based on the field strength received from a cell of the middlelayer. + +A "fast" mobile connected to a cell of the middlelayer must handover towards a cell of the upperlayer. Nevertheless the field strength received from the cell of the upperlayer must be high enough to trigger the handover. + +The estimation of mobile speeds are based on the field strength received from a cell of the middlelayer. + +A "slow" mobile connected to a cell of the middlelayer must handover towards a cell of the lowerlayer. The estimation of mobile speeds are based on the field strength received from a cell of the lowerlayer + +## D.3 Handover causes + +Some causes trigger emergency handovers, others trigger computations of the estimation of the mobile speed. + +### D.3.1 emergency handover causes + +An emergency handover is performed as soon as the quality of service become too low (RXQUAL and RXLEV causes), the handover has to be fast and secured. Target cells are ordinated depending on the value of PBGT(n), nevertheless cells of the directly upper layer have priority. + +ex: in a hierarchical network composed with two layers, emergency handovers in cells of the lowerlayer are performed in priority towards cells of the upperlayer. + +- a) Comparison of RXLEV\_XX with L\_RXLEV\_XX\_H (XX = DL or UL) + +$$\text{RXLEV\_XX} < \text{L\_RXLEV\_HH\_H}$$ + +- b) Comparison of RXQUAL\_XX with L\_RXQUAL\_XX\_H (XX = DL or UL) + +$$\text{RXQUAL\_XX} > \text{L\_RXQUAL\_XX\_H}$$ + +### D.3.2 mobile speeds estimation causes + +Mobile speeds are estimated as soon as a non emergency handover is required. Two handover causes, which depend of the target cell type, provide a computation of the estimation of mobile speeds. + +A PBGT criteria is used in the case of a target cell of the same layer as the source one. + +A CATCH criteria is used in the case of a target cell of a lower layer than the source one. + +The PBGT(n) criteria if defined as in the appendix A of recommendation GSM 05.08 [3] i.e.: + +$$1) \text{RXLEV\_NCELL}(n) > \text{RXLEV\_MIN}(n) + \text{Max}(0, P_a)$$ + +where $P_a = (\text{MS\_TXPWR\_MAX}(n) - P)$ + +$$2) \text{PBGT}(n) - \text{HO\_MARGIN}(n1, n2) > 0$$ + +where n1: source cell + +n2: target cell + +The CATCH criteria is defined as follow: + +$$\text{RXLEV\_NCELL}(0, n) > \text{CATCH}(0, n)$$ + +where $\text{RXLEV\_NCELL}(0, n)$ : RXLEV assessed on the BCCH carrier of the cell n + +$\text{CATCH}(0, n)$ : field strength threshold + +This comparison enables handover to be performed towards a cell of a lower layer whom received field strength is considered to be high enough. + +## D.4 Mobile speeds estimations + +As soon as one of the two causes described above is triggered (PBGT, CATCH) a process of computation of the estimation of the mobile speed is performed. + +The method of estimation of the field strength variations is based on the computation of the gradient between two averages of field strengths received by the mobile from the target cell. + +### D.4.1 Estimation of the field strength variations + +The first of the two averages of field strength used in the gradient computation is the one computed from measurements received from the target cell which has verified the handover criteria. + +The handover cause can be either a PBGT or a CATCH one (see subclause D.3.2 mobile speeds estimation causes). + +The second of the two field strength averages used in the gradient computation is the latest one for which the gaps between all the previous averages and the straight line passing-by the two averages defined above is lower than **Emax** ( $E < E_{\text{max}}$ ). + +**Emax** is one of the parameters of the handover algorithm. + +The gradient is then computed as follow: + +$$1) \text{GRAD} = ((\text{RXLEV\_NCELL}(n, N_o) - \text{RXLEV\_NCELL}(n, N_o - m)) / m$$ + +where: + +- n is the respective adjacent cell "n" +- $N_o$ is the index of reference of the average for which the handover criteria has been verified +- m is the last average for which $E < E_{\text{max}}$ +- $\text{RXLEV\_NCELL}(0, n)$ is the RXLEV assessed on the BCCH carrier of the cell n + +In order to ensure an efficiency estimation of the mobile speeds a minimum number of averages ( $N_{\text{Amin}}$ ) are necessary to trigger the computation of the gradient. + +To avoid high computed time and high memory size a maximum number of averages ( $N_{\text{Amax}}$ ) has to be kept. + +The number of averages to take into account shall verified the following condition: + +#### 2) $N_{\min} < N < N_{\max}$ + +where: + +- $N_{\min}$ is the minimum number of averages necessary to compute the gradient; +- $N_{\max}$ is the maximum number of averages necessary to compute the gradient. + +If the number of averages is not high enough ( $N < N_{\min}$ ) a default handover algorithm is used. + +The handover towards an upper layer is performed only if the above conditions are verified and if the field strength received from the target cell verified the following condition: + +#### 3) $RXLEV > U\_RXLEV\_NCELL(0,n)$ + +where: + +- $U\_RXLEV\_NCELL(0,n)$ is the minimum field strength assessed from the BCCH carrier of the upper layer target cell to perform a handover towards it. + +## --- D.5 BSS decision algorithm + +The BSS decision algorithm is the classical one as described in the appendix A of the recommendation GSM 05.08 [3]. Nevertheless in the case of an emergency handover, cells of the directly upper layer has priority. If no cell of the directly upper layer is available, cells of the same layer are ordering depending of the PBGT( $n2$ ) - HO\_MARGIN( $n1,n2$ ) values. + +## --- D.6 O&M parameters + +**CELL\_TYPE:** Hierarchy level of serving cell + +Range 0-7 + +Step size 1 + +Coding 0: microcell + +1: small cell + +2: large cell + +3-7: for future use + +**NCELL\_TYPE( $n$ ):** Hierarchy level of $n$ -th neighbour cell + +$n$ 1-32 + +Range 0-7 + +Step size 1 + +Coding 0: microcell + +1: small cell + +2: large cell + +3-7: for future use + +**EN\_MS\_SPEED:** Enable/Disable classification of MS regarding SPEED + +Coding 0: disable feature + +1: enable feature + +**NAmax:** Maximum number of averages necessary to compute the gradient. + +Range 0 - 63 (SACCH) + +Step size 1 + +**Namin:** Minimum number of averages necessary to compute the gradient. + +Range 0 - 63 (SACCH) + +Step size 1 + +**Emax:** Maximum gap allowed between a computed average and the straight line considered. + +Range 0 - 15 (dB) + +Step size 1 + +**GRAD:** Gradient threshold. It depends of the mobile speed threshold. Middlelayers have two Grad thresholds (Gradmin & Gradmax), the upperlayer and the lowerlayer has one threshold (Grad). + +Range 0 - 255 + +Step size 1 + +**CATCH(n):** Minimum field strength threshold. This is the minimum field strength the mobile has to receive from a cell of the directly lower layer to perform a handover. + +Range 0 - 63 (dB) + +Step size 1 + +**U\_RXLEV\_NCELL(0,n):** Field strength threshold. This is the minimum field strength necessary to receive from the upper layer cell to performed a handover towards it. + +Range 0 - 63 + +Step size 1 + +## --- D.7 Examples + +Figure D.2 features a field strength variations, and its associate averages, measured by a mobile moving away from its source base station. + +In this particular case the average window size is four measurements length and the number of measurements kept is equal to nineteen (-> NAmax = 16). + +![Figure D.1: Field strength samples and averages. A graph showing field strength samples (dots) and averages (squares) over 18 SACCH periods (No-18 to No). The field strength generally increases over time, with a notable dip at No-4. A horizontal line indicates the average for which the handover criteria is verified. The legend defines the symbols: a dot for a field strength sample, a square for the field strength average, and a horizontal bar for the number of samples taken into account in the average computation.](051638d871c75230edb3d005fa668810_img.jpg) + +Average for which the handover criteria is verified + +No-18 No-17 No-16 No-15 No-14 No-13 No-12 No-11 No-10 No-9 No-8 No-7 No-6 No-5 No-4 No-3 No-2 No-1 No + +SACCH periods + +- Field strength sample measured by the mobile from the target cell +- Field strength average +- ▬ Number of samples taken into account in the average computation + +Figure D.1: Field strength samples and averages. A graph showing field strength samples (dots) and averages (squares) over 18 SACCH periods (No-18 to No). The field strength generally increases over time, with a notable dip at No-4. A horizontal line indicates the average for which the handover criteria is verified. The legend defines the symbols: a dot for a field strength sample, a square for the field strength average, and a horizontal bar for the number of samples taken into account in the average computation. + +Averages are calculated according to the sliding window technique. + +![Figure D.2: Field strength samples and averages. This graph is identical to Figure D.1, showing field strength samples and averages over 18 SACCH periods. It includes the same legend and annotations, illustrating the sliding window technique for average calculation.](bac21fd48fcd7f025c723590e07d1823_img.jpg) + +Average for which the handover criteria is verified + +No-18 No-17 No-16 No-15 No-14 No-13 No-12 No-11 No-10 No-9 No-8 No-7 No-6 No-5 No-4 No-3 No-2 No-1 No + +SACCH periods + +- Field strength sample measured by the mobile from the target cell +- Field strength average +- ▬ Number of samples taken into account in the average computation + +Figure D.2: Field strength samples and averages. This graph is identical to Figure D.1, showing field strength samples and averages over 18 SACCH periods. It includes the same legend and annotations, illustrating the sliding window technique for average calculation. + +**Figure D.2: Field strength samples and averages** + +In some particular and rare cases the target cell may have a decreasing field strength. In most of the cases that means that it is the "best" cell but that the mobile is moving away from it. + +It is even also necessary to take into account the gradient of the field strength in the mobile speeds estimation. For that reason it is necessary to compute the absolute values of gaps and of the gradient. + +Figure D.3 features an example of gaps computation. + +![Figure D.3: Gap computation. A graph showing field strength values over SACCH periods. The y-axis represents field strength, and the x-axis represents SACCH periods from No-15 to No. A vertical line marks Emax. A horizontal line marks the threshold for the handover criteria. Two straight lines, No-14 and No-10, are shown. Data points are represented by squares (Neighbour field strength averages) and asterisks (Field strength values computed from the straight line). The gap between a square and an asterisk is labeled 'Gap taken into account'. Labels indicate 'Emax_computed < Emax' and 'Emax_computed > Emax'.](b9d879f357d5f15fac9ea8585b87d0a2_img.jpg) + +Average for which the handover criteria is verified + +Emax + +Straight line No-14 + +Emax\_computed < Emax + +Straight line No-10 + +Emax\_computed > Emax + +Gap taken into account + +SACCH Periods + +No-15 No-14 No-13 No-12 No-11 No-10 No-9 No-8 No-7 No-6 No-5 No-4 No-3 No-2 No-1 No + +■ Neighbour field strength averages + +✱ Field strength values computed from the straight line + +Figure D.3: Gap computation. A graph showing field strength values over SACCH periods. The y-axis represents field strength, and the x-axis represents SACCH periods from No-15 to No. A vertical line marks Emax. A horizontal line marks the threshold for the handover criteria. Two straight lines, No-14 and No-10, are shown. Data points are represented by squares (Neighbour field strength averages) and asterisks (Field strength values computed from the straight line). The gap between a square and an asterisk is labeled 'Gap taken into account'. Labels indicate 'Emax\_computed < Emax' and 'Emax\_computed > Emax'. + +**Figure D.3: Gap computation** + +For each average computed (■), from the latest to the oldest, the algorithm determines the maximum gap with the corresponding field strength computed from the straight line (✱). + +Considering the average computed at date $N_0-10$ in the particular case of figure D.3. The maximum gap computed **Emax\_computed**, between the nine previous averages (from $N_0-1$ to $N_0-9$ ) and the straight line $N_0-10$ , is lower than the maximum gap allowed **Emax**. + +On the other hand considering the average computed at date $N_0-14$ . The gap computed between the average on date $N_0-10$ and the straight line $N_0-14$ is higher than the maximum gap allowed **Emax**. + +In this case the last average for which the maximum gap computed is lower than **Emax** is the one computed on date **$N_0-13$** . + +In this case the gradient of the field strength is equal to: + +$$GRAD = (RXLEV_NCELL(n, N_0) - RXLEV_NCELL(n, N_0-13))/13$$ + +where: + +**$RXLEV\_NCELL(n, N_0)$** : RXLEV assessed on the BCCH carrier of the cell n, which has verified the handover criteria (date $N_0$ ). + +**$RXLEV\_NCELL(n, N_0-13)$** : RXLEV assessed on the BCCH carrier of the cell, computed on date $N_0-13$ . + +In the case of figure D.3, averages are almost constants from date $N_0-10$ to $N_0-15$ , it can be the case for example for a mobile stopped at a traffic light . The parameter **Emax** avoid to take into account these averages in the estimation of the mobile speeds. + +## D.8 State diagrams + +### D.8.1 Case of a three layers hierarchical network + +Ideal behaviour: target cells are available + +![Figure D.4: Handovers in case of availability of the target cell](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +The diagram shows three states: **Upperlayer**, **Middlelayer**, and **Lowerlayer**, arranged vertically. Transitions between them are triggered by various conditions: + +- Inputs to all layers:** RACH and external handover arrows point into each layer from the left. +- Upperlayer:** + - Self-loop (Emergency HO): + + PBGT + + CATCH & $N < N_{Amin}$ + + CATCH & $N_{Amin} < N < N_{Amax}$ & $G > Grad$ + - Transition to Middlelayer: PBGT & $N < N_{Amin}$ +- Middlelayer:** + - Self-loop (Emergency HO): + PBGT & $N_{Amin} < N < N_{Amax}$ & $G < Gradmax$ + + CATCH & $N_{Amin} < N < N_{Amax}$ & $G > Gradmin$ + + CATCH & $N < N_{Amin}$ + - Transition to Upperlayer (Emergency HO): + + PBGT + & $N_{Amin} < N < N_{Amax}$ + & $G > Gradmax$ & $RXLEV\_NCELL(0,n) > U\_RXLEV\_NCELL(0,n)$ + - Transition to Lowerlayer: PBGT & $N < N_{Amin}$ +- Lowerlayer:** + - Self-loop (Emergency HO): + PBGT + & $N_{Amin} < N < N_{Amax}$ + & $G < Grad$ + - Transition to Middlelayer (Emergency HO): + + PBGT + & $N_{Amin} < N < N_{Amax}$ + & $G > Grad$ & $RXLEV\_NCELL(0,n) > U\_RXLEV\_NCELL(0,n)$ + +Vertical arrows labeled "Emergency HO" indicate transitions between layers. Conditions involving CATCH, PBGT, N (number of cells), and G (gradient) determine the handover logic. + +Figure D.4: Handovers in case of availability of the target cell + +**Figure D.4: Handovers in case of availability of the target cell** + +Non ideal behaviour: target cells may not be available + +The handover that may occur to non preferred target cells due to the unavailability of TCH resources are indicated with dotted line arrows in the state diagram. + +![Diagram of handover logic for a three-layer hierarchical network (Upperlayer, Middlelayer, Lowerlayer) in case of non availability of the target cell. It shows various triggers like RACH, external handover, and Emergency HO with associated conditions for PBGT, CATCH, and N (number of cells).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates the handover logic for a three-layer hierarchical network (Upperlayer, Middlelayer, Lowerlayer) in the case of non availability of the target cell. The layers are stacked vertically. Arrows indicate the flow of handover requests and responses between layers and to external entities. + +- Upperlayer:** + - Receives **RACH** and **external handover** from the left. + - Has an internal **Emergency HO** loop with conditions: + - + PBGT + - + CATCH & $N < N_{Amin}$ + - + CATCH & $N_{Amin} < N < N_{Amax}$ & $G > Grad$ + - Has an outgoing **HO** arrow to Middlelayer with condition: $PBGT \text{ & } N < N_{Amin}$ + - Has an **Emergency HO** arrow to Middlelayer. +- Middlelayer:** + - Receives **RACH** and **external handover** from the left. + - Has an internal **Emergency HO** loop with conditions: + - + PBGT + - & $N_{Amin} < N < N_{Amax}$ + - & $G > Gradmax \text{ & } RXLEV\_NCELL(0,n) > U\_RXLEV\_NCELL(0,n)$ + - Has an outgoing **HO** arrow to Upperlayer with conditions: + - $PBGT \text{ & } N_{Amin} < N < N_{Amax} \text{ & } G < Gradmax$ + - + $CATCH \text{ & } N_{Amin} < N < N_{Amax} \text{ & } G > Gradmin$ + - + $CATCH \text{ & } N < N_{Amin}$ + - Has an outgoing **HO** arrow to Lowerlayer with conditions: + - $PBGT \text{ & } N < N_{Amin}$ + - + PBGT & $N_{Amin} < N < N_{Amax}$ & $G > Grad \text{ & } RXLEV\_NCELL(0,n) > U\_RXLEV\_NCELL(0,n)$ +- Lowerlayer:** + - Receives **RACH** and **external handover** from the left. + - Has an internal **HO** loop with conditions: + - PBGT & $N_{Amin} < N < N_{Amax}$ & $G < Grad$ + - Has an **Emergency HO** arrow to Middlelayer. + +A legend box indicates: "In case of non availability of the preferred cell". + +Diagram of handover logic for a three-layer hierarchical network (Upperlayer, Middlelayer, Lowerlayer) in case of non availability of the target cell. It shows various triggers like RACH, external handover, and Emergency HO with associated conditions for PBGT, CATCH, and N (number of cells). + +Figure D.5: Handover in case of non availability of the target cell + +### D.8.2 Case of a two layers hierarchical network + +Ideal behaviour: target cells are available + +![Diagram of handover logic for a two-layer hierarchical network (Upperlayer, Lowerlayer) in case of availability of the target cell.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +The diagram illustrates the handover logic for a two-layer hierarchical network (Upperlayer, Lowerlayer) in the case of availability of the target cell. + +- Upperlayer:** + - Receives **RACH** and **external handover**. + - Internal **Emergency HO** conditions: + - + PBGT + - + CATCH & $N < N_{Amin}$ + - + CATCH & $N_{Amin} < N < N_{Amax}$ & $G > Grad$ + - Outgoing **HO** to Lowerlayer conditions: + - $PBGT \text{ & } N < N_{Amin}$ + - + PBGT & $N_{Amin} < N < N_{Amax}$ & $G > Grad \text{ & } RXLEV\_NCELL(0,n) > U\_RXLEV\_NCELL(0,n)$ +- Lowerlayer:** + - Receives **RACH** and **external handover**. + - Internal **HO** conditions: $PBGT \text{ & } N_{Amin} < N < N_{Amax} \text{ & } G < Grad$ + - Outgoing **Emergency HO** to Upperlayer. + +Diagram of handover logic for a two-layer hierarchical network (Upperlayer, Lowerlayer) in case of availability of the target cell. + +Figure D.6: Handovers in case of availability of the target cell + +Non ideal behaviour: target cells may not be available + +![State diagram showing handover logic between Upperlayer and Lowerlayer. It includes transitions for RACH, external handover, CATCH, PBGT, and Emergency HO with specific conditions. A legend indicates that dotted arrows represent non-availability of the preferred cell.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +The diagram illustrates the handover logic between the Upperlayer and Lowerlayer. It features two main states: 'Upperlayer' and 'Lowerlayer'. + +- Upperlayer Transitions:** + - External Handover:** Indicated by a solid arrow from the left. + - RACH:** Indicated by a solid arrow from the left. + - Emergency HO (to Lowerlayer):** Indicated by a solid downward arrow. + - Emergency HO (from Lowerlayer):** Indicated by a solid upward arrow. + - Self-loops:** + - Emergency HO:** Conditions include '+ PBGT', '+ CATCH & N < N Amin', and '+ CATCH & N Amin < N < N Amax & G > Grad'. + - PBGT:** Condition is 'PBGT & N < N Amin'. + - CATCH:** Conditions include '+ PBGT', '& N Amin < N < N Amax', '& G > Grad', and 'RXLEV\_NCELL(0,n) > U\_RXLEV\_NCELL(0,n)'. +- Lowerlayer Transitions:** + - External Handover:** Indicated by a solid arrow from the left. + - RACH:** Indicated by a solid arrow from the left. + - Emergency HO (to Upperlayer):** Indicated by a solid upward arrow. + - Emergency HO (from Upperlayer):** Indicated by a solid downward arrow. + - Self-loop:** + - Emergency HO:** Condition is 'PBGT & N Amin < N < N Amax & G < Grad'. + +**Legend:** A box with a dotted arrow indicates 'In case of non availability of the preferred cell'. + +State diagram showing handover logic between Upperlayer and Lowerlayer. It includes transitions for RACH, external handover, CATCH, PBGT, and Emergency HO with specific conditions. A legend indicates that dotted arrows represent non-availability of the preferred cell. + +The handover that may occur to non preferred target cells due to the unavailability of TCH resources are indicated with dotted line arrows in the state diagram. + +**Figure D.7: Handover in case of non availability of the target cell** + +# --- Annex E (informative): Simulation Model for Handover Performance Evaluation in Hierarchical Cell Structures + +## E.1 Introduction + +In this annex, the general requirements of a simulation model for handover performance evaluation in hierarchical cell structures are specified. + +The following criteria are considered fundamental for the design of the overall simulation model: + +- Mobile environment; +- Radio network model; +- Propagation model; +- Motion model; +- Handover algorithms; +- Measurement reporting; +- Performance criteria. + +## --- E.2 Mobile Environment + +The single mobile environment is taken to allow relatively simple simulations and easier interpretation of the performance results. + +In order to simulate the interference that may occur, a detailed frequency allocation pattern and a large number of cells are required. In the single mobile environment, the interference situation is not taken into account. Therefore, handovers due to quality are not simulated. However, this enables the very evaluation of the handover algorithm, and not the evaluation of the frequency pattern. + +## --- E.3 Radio Network Model + +The radio network model represents the network layout. It should allow the definition of the following parameters: + +- Number of layers; +- Number of cells on each layer; +- BTS site pattern; +- BTS separation. + +Three network model scenarios are proposed. + +### E.3.1 Scenario 1: Hot Spot + +One cell in the upper layer, one cell in the lower layer. + +### E.3.2 Scenario 2: Line of Cells + +Two cell in the upper layer, 5 cells in the lower layer. Lower layer cell distance: 400 m. Upper layer cell distance: 2 km. + +![Figure E.1: Diagram of Scenario 2: Line of Cells. The top part shows five overlapping circles representing cells in the lower layer, with a horizontal line passing through their centers. The bottom part shows a horizontal line with five vertical lines representing base stations. The first and last vertical lines are labeled 'macrocell', and the three intermediate ones are labeled 'microcell'. A double-headed arrow between the second and third vertical lines is labeled '400 m'.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +Figure E.1: Diagram of Scenario 2: Line of Cells. The top part shows five overlapping circles representing cells in the lower layer, with a horizontal line passing through their centers. The bottom part shows a horizontal line with five vertical lines representing base stations. The first and last vertical lines are labeled 'macrocell', and the three intermediate ones are labeled 'microcell'. A double-headed arrow between the second and third vertical lines is labeled '400 m'. + +Figure E.1 + +### E.3.3 Scenario 3: Manhattan Coverage + +Four cells in the upper layer, 13 cells in the lower layer. Lower layer cell distance between BTS: 400 m. Upper layer cell distance: 2 km. The cells in the lower layer are situated at alternate crossings. + +![Figure E.2: Diagram of Scenario 3: Manhattan Coverage. The diagram shows a grid of squares representing cells. There are 13 squares in the lower layer, arranged in a pattern where they are at alternate crossings of a grid. Four larger squares, one at each corner of the grid, are labeled 'Umbrella Cell'. A horizontal double-headed arrow between two adjacent squares in the lower layer is labeled '400 m'. A vertical double-headed arrow between two adjacent squares in the upper layer is labeled '200 m'.](24b1ac9eb58a2f22801620b9e2ea8bd3_img.jpg) + +Figure E.2: Diagram of Scenario 3: Manhattan Coverage. The diagram shows a grid of squares representing cells. There are 13 squares in the lower layer, arranged in a pattern where they are at alternate crossings of a grid. Four larger squares, one at each corner of the grid, are labeled 'Umbrella Cell'. A horizontal double-headed arrow between two adjacent squares in the lower layer is labeled '400 m'. A vertical double-headed arrow between two adjacent squares in the upper layer is labeled '200 m'. + +Figure E.2 + +## E.4 Propagation Model + +### E.4.1 Upper Layer Path Loss + +#### E.4.1.1 Macrocells + +For macrocells the GSM 03.30 Hata model is used to simulate this layer. + +Table E.1: Validity domain of Hata's model for GSM 900 MHz + +| Parameter | Validity range | +|--------------------------|---------------------| +| Frequency (f) | 150 MHz - 1 000 MHz | +| Base station height (Hb) | 30 - 200 m | +| MS height (Hm) | 1 - 10 m | +| Distance (d) | 1 - 20 km | + +For DCS 1800 the model is different and not given in the present document. + +##### Hata's model + +###### For urban environment, the formula is given by: + +$$L_u = 69.55 + 26.16 \cdot \log(f) - 13.82 \cdot \log(H_b) - a(H_m) + [44.9 - 6.55 \cdot \log(H_b)] \cdot \log(d)$$ + +the corrective term $a(H_m)$ is zero for MS antenna height of 1.5 m, which is assumed. + +For suburban, rural quasi-open and rural open environment there are corrective terms. Since microcellular approach is not assumed in these environments, these terms are not given. + +###### Simulation Profile + +A typical profile at 900 MHz for urban environment is given in the table below: + +**Table E.2** + +| | | | | +|------------------------|------------------------------|------------------------------|------------------------------| +| BTS antenna height (m) | 30 | 50 | 100 | +| MS antenna height (m) | 1.5 | 1.5 | 1.5 | +| Hata's loss (d in km) | $126.4 + 35.2 \cdot \log(d)$ | $123.3 + 33.7 \cdot \log(d)$ | $119.2 + 31.8 \cdot \log(d)$ | + +For the simulation a base station antenna height of 30 m is used. + +#### E.4.1.2 Small cells + +The propagation model for small cells, with a typical maximum range of 1-3 km, can be derived also from GSM 03.30. Therefore COST 231 Walfish-Ikegami model can be utilized. + +**Table E.3: Validity domain of COST 231 Walfish Ikegami model** + +| Parameter | Validity range | +|--------------------------------------------------------------|---------------------| +| Frequency (f) | 800 MHz - 2 000 MHz | +| BTS antenna height (Hb) | 4 - 50 m | +| MS antenna height (Hm) | 1 - 3 m | +| Distance (d) | 0.02 - 5 km | +| Height of buildings (Hroof, in m) | | +| Width of road (w, in m) | | +| Building separation (b, in m) | | +| Road orientation with respect to the direct path (Phi, in °) | | +| Urban areas | | + +###### COST 231 Walfish Ikegami model + +Two profiles are defined: with and without line of sight. + +###### Line of sight formula + +The COST 231 Walfish-Ikegami formula for urban environment with line-of-sight (Street Canyon) is + +$$L_b = 42.6 + 26 \cdot \log(d) + 20 \cdot \log(f)$$ + +for $d \geq 0.020$ km + +Note that this equation is not valid in the case of line of sight in a microcell because of the canyon effect in a microcell. + +###### Non line-of-site formula + +$$L_b = L_o + L_{rts} + L_{msd}$$ + +with $L_o$ free-space loss + +$$L_o = 32.4 + 20 \cdot \log(d) + 20 \cdot \log(f)$$ + +with Lrst (roof-top-to-street diffraction and scatter loss) + +$$L_{rst} = -16.9 - 10 \cdot \log(w) + 10 \cdot \log(f) + 20 \cdot \log(H_r - H_m) + L_{cri}$$ + +with + +$$L_{cri} = -10 + 0.354 \cdot \Phi \quad \text{for } 0^\circ \leq \Phi < 35^\circ$$ + +$$L_{cri} = 2.5 + 0.075 \cdot (\Phi - 35) \quad \text{for } 35^\circ \leq \Phi < 55^\circ$$ + +$$L_{cri} = 4.0 - 0.114 \cdot (\Phi - 55) \quad \text{for } 55^\circ \leq \Phi < 90^\circ$$ + +with Lmsd a parameter that will be given for metropolitan centres. + +###### Simulation profile + +A typical profile at 900 MHz for urban environment that can be used in the simulations is given in the table below: + +Width of the road, $w = 20$ m + +Height of building roof tops, $H_{roof} = 15$ m + +Height of BTS antenna, $H_b = 17$ m + +Road orientation to direct radio path, $\phi = 90^\circ$ + +Building separation, $b = 40$ m + +$$Loss(dB) = 132.8 + 38 \cdot \log(d)$$ + +where $d$ is in km. + +NOTE: It is not possible to use this model in the case of antenna height just below roof top. In this environment an additional term is required, which is not given in order not to complexify the simulations. + +### E.4.2 Lower Layer Path Loss + +The lower layer uses an outdoor propagation model, called dual slope model. It is based on a model used in "Path Loss and Fading in Microcells", COST231 TD 65, Darmstadt, 12th September 1990. + +The values of the different parameters were determined by field measurements considering a street width of 18,5 metres. + +#### E.4.2.1 Line-of-sight Case + +In the line-of-sight case, the path loss $L$ is given by: + +$$L(d) = 27 + 10 \log \left[ \left( d^{n_1} \right)^p + \left( d^{n_1} (d / d_L)^{n_2 - n_1} \right)^p \right]^{1/p}$$ + +with the parameters: + +$d$ : distance transmitter-receiver *in metres* + +$d_L$ : distance between transmitting antenna and breakpoint (m) 500 m + +$n_1$ : slope factor of path loss before breakpoint 2.6 + +$n_2$ : slope factor of path loss after breakpoint 4.0 + +$p$ : shape factor 4 + +#### E.4.2.2 Non Line-of-sight Case + +In the non line-of-sight case, the supplementary path loss introduced is: + +$$L'(y) = 10 \log \left[ \left( \left( \frac{y}{y_{E1}} + 1 \right)^{n_{E1}} \right)^p + \left( \left( \frac{y^{E2}}{y^{E1}} + 1 \right)^{n_{E1}} \times \left( \frac{y + y_{E1}}{y_{E1} + y_{E2}} \right)^{n_{E2}} \right)^p \right]^{1/p}$$ + +with the parameters: + +$y$ : distance in non-line-of-sight from the BTS *in meters* + +$y_{E1}$ : distance from corner to virtual position of transmitter (m) 2.6 + +$y_{E2}$ : breakpoint distance 65.3 m + +$n_{E1}$ : slope factor of path loss before breakpoint 2.34 + +$n_{E2}$ : slope factor of path loss after breakpoint 2.84 + +$p$ : shape factor 4 + +For instance, with the following configuration: + +![Diagram of a non-line-of-sight path loss configuration. A Mobile Station (MS) is at the bottom left, and a Base Transceiver Station (BTS) is at the top right. A rectangular building is between them. The path from MS to the building is labeled d2, and the path from the building to BTS is labeled d1. The formula Path Loss = L(d1) + L'(d2) is shown to the right.](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +Diagram of a non-line-of-sight path loss configuration. A Mobile Station (MS) is at the bottom left, and a Base Transceiver Station (BTS) is at the top right. A rectangular building is between them. The path from MS to the building is labeled d2, and the path from the building to BTS is labeled d1. The formula Path Loss = L(d1) + L'(d2) is shown to the right. + +Figure E.3 + +#### E.4.2.3 Shape of the level with the proposed path loss model + +We considered the following scenario: + +![Diagram of a grid layout with four buildings arranged in a 2x2 square. The grid is defined by two horizontal and two vertical lines. Four points are marked: 1 on the left, 2 on the right, 3 at the top, and 4 at the bottom. A horizontal double-headed arrow between the vertical lines is labeled 200 m.](265d5cb06b401cf460a20fd2c93fd6d5_img.jpg) + +Diagram of a grid layout with four buildings arranged in a 2x2 square. The grid is defined by two horizontal and two vertical lines. Four points are marked: 1 on the left, 2 on the right, 3 at the top, and 4 at the bottom. A horizontal double-headed arrow between the vertical lines is labeled 200 m. + +Figure E.4 + +When the MS goes from BTS 1 to BTS 3, the path losses of the different BTSs have the following shape: + +![Figure E.5: Path loss from the different BTS (dB) vs Distance from BTS1 (m). The graph shows four curves representing path loss from BTS1, BTS2, BTS3, and BTS4 as a function of distance from BTS1. The x-axis ranges from 0 to 400 m, and the y-axis ranges from 50 to 140 dB. The curves show that path loss from BTS1 increases with distance, while path loss from BTS3 decreases. Path loss from BTS2 and BTS4 remains relatively constant, with a slight dip at 200 m.](1eb72b1e2fe3920b483f6245e5d477e8_img.jpg) + +| Distance from BTS1 (m) | BTS1 Path Loss (dB) | BTS2 Path Loss (dB) | BTS3 Path Loss (dB) | BTS4 Path Loss (dB) | +|------------------------|---------------------|---------------------|---------------------|---------------------| +| 0 | 55 | 95 | 135 | 130 | +| 50 | 70 | 93 | 128 | 125 | +| 100 | 80 | 91 | 120 | 120 | +| 150 | 85 | 89 | 110 | 115 | +| 200 | 88 | 87 | 100 | 110 | +| 250 | 90 | 85 | 90 | 105 | +| 300 | 92 | 83 | 80 | 100 | +| 350 | 94 | 81 | 70 | 95 | +| 400 | 96 | 79 | 60 | 90 | + +Figure E.5: Path loss from the different BTS (dB) vs Distance from BTS1 (m). The graph shows four curves representing path loss from BTS1, BTS2, BTS3, and BTS4 as a function of distance from BTS1. The x-axis ranges from 0 to 400 m, and the y-axis ranges from 50 to 140 dB. The curves show that path loss from BTS1 increases with distance, while path loss from BTS3 decreases. Path loss from BTS2 and BTS4 remains relatively constant, with a slight dip at 200 m. + +Figure E.5 + +### E.4.3 Fading + +Fast (Rayleigh) fading is neglected as the values considered are averaged over at least 0.5 ms. + +Slow fading (shadowing) is modelled by a Gaussian distributed random variable $F$ to the path loss level value. The model is characterized by two parameters: + +- the standard deviation of the Gaussian distribution, Macrocell: 6 dB, Microcell: 4 dB, +- the correlation length, $d_{cor}=10$ metres. + +The correlation function between two positions of the MS $x_1$ and $x_2$ can be written: + +$$\text{corr}( F(x_1) F(x_2) ) = \exp\left(-\frac{\lambda | x_1 - x_2 |}{d_{cor}}\right)$$ + +where $\lambda$ is a constant. Note that for $\lambda = \ln 2$ , the correlation function equals 0.5 at the correlation distance. + +## E.5 Motion Model + +The MS can either go straight or turn at the corner of a street. + +Four constant speeds shall be considered: 3, 36, 54 and 72 km/h. In the turning around the corner case, only the speeds 3 km/h and 36 km/h shall be considered. + +The two motion models should be simulated for the three radio network scenarios proposed. + +## --- E.6 Handover Algorithms + +As per annex A-D. + +The late handover decision and the delay between handover decision and execution shall be considered, which could lead to dropped calls. + +## --- E.7 Measurement Reporting + +This effect, especially for corner effects, of the time delay between receiving and no longer receiving a neighbour cell, and reporting to the BTS plus the BTS handling time has to be accounted for. + +## --- E.8 Performance Criteria + +The following performance criteria will be taken: + +- Percentage of time a call is handled on the different layers; +- Distribution of the position where the handover takes place; +- Number of handovers; +- Number of dropped calls. + +## --- E.9 Open Issues + +- Location of call set up and termination. +- ###How to simulate the measurement reporting? + +It was proposed to simulate the delay in the measurement reporting either by a constant or by a random variable between 0 and a value to be determined. + +# Annex F (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2001-04 | 4 | | | | Version for Release 4 | | 4.0.0 | +| 2002-06 | 10 | | | | Version for Release 5 | 4.0.0 | 5.0.0 | +| 2005-01 | 23 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 2007-08 | 35 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 2008-12 | 40 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | 44 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 2011-03 | 49 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 2014-09 | 63 | | | | Version for Release 12 (frozen at SP-65) | 11.0.0 | 12.0.0 | +| 2015-12 | 68 | | | | Version for Release 13 (frozen at SP-70) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Version for Release 15 (frozen at TSG-80) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/45_series/45056/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/45_series/45056/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c6677052983623c70fbbc89876aa7eec16d1e9e --- /dev/null +++ b/marked/Rel-18/45_series/45056/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5d75494e908e301a072e7cf904a277130cf7f743fc51938695555c3ba1eedf1 +size 8810 diff --git a/marked/Rel-18/45_series/45056/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/45_series/45056/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac55d01af2599d55f833d5ac4a047bba969f4e8c --- /dev/null +++ b/marked/Rel-18/45_series/45056/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cb23fa3b12a8d1e9cb4b9293eb744fe8ec93ee9273094b1909b9cc693e510ca +size 14671 diff --git a/marked/Rel-18/45_series/45056/939b79420df0cf962959ccef56f3371f_img.jpg b/marked/Rel-18/45_series/45056/939b79420df0cf962959ccef56f3371f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ee7a9072d95d4e13fef39ea461b005b64f2fabf --- /dev/null +++ b/marked/Rel-18/45_series/45056/939b79420df0cf962959ccef56f3371f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56eaece76e971c8a350c25b89513c74c3c5c7f2281ca9b929341d660ae50c1cf +size 38676 diff --git a/marked/Rel-18/45_series/45056/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-18/45_series/45056/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47de08df149017e689462ec7dd251f65cd67bd17 --- /dev/null +++ b/marked/Rel-18/45_series/45056/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ced17b2de9d46e25211c67fc5ba76474f20f61a7ea773d841fabc254b275a9e8 +size 114593 diff --git a/marked/Rel-18/45_series/45056/cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg b/marked/Rel-18/45_series/45056/cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77c93d9bc600ab4cdbd438547bc7de8d75ac075d --- /dev/null +++ b/marked/Rel-18/45_series/45056/cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69a628b25ae8d477a3b997b0d835772eefeac522b34af2cddf743c994ce54ced +size 127835 diff --git a/marked/Rel-18/45_series/45056/raw.md b/marked/Rel-18/45_series/45056/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d4a76c0a01e8b0bf99912787a439586fb8066727 --- /dev/null +++ b/marked/Rel-18/45_series/45056/raw.md @@ -0,0 +1,976 @@ + + +# 3GPP TS 45.056 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; GSM Cordless Telephony System (CTS), Phase 1; CTS-FP Radio subsystem (Release 18)** + +![GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS'](64662465bba247703fdec49c8f3309f9_img.jpg) + +The GSM logo consists of the letters 'GSM' in a stylized blue font, with a small red square above the 'M'. Below the logo, the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' is written in a smaller blue font. + +GSM logo with the text 'GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS' + +![3GPP logo with the text '3GPP™'](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo features the letters '3GPP' in a bold, black, stylized font. The '3' and 'G' are connected at the top, and the 'P' has a small red signal icon below it. The letters '3GPP' are followed by a small 'TM' symbol. + +3GPP logo with the text '3GPP™' + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +GSM, radio, CTS + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|-------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Radio transmission and reception ..... | 7 | +| 4.1 Frequency band and channels arrangements..... | 7 | +| 4.2 Reference configuration..... | 8 | +| 4.3 Transmitter characteristics ..... | 8 | +| 4.3.1 Output power ..... | 8 | +| 4.3.2 Output RF spectrum ..... | 9 | +| 4.3.2.1 Spectrum due to the modulation and wide band noise ..... | 9 | +| 4.3.2.2 Spectrum due to switching transient..... | 10 | +| 4.3.3 Spurious emission..... | 11 | +| 4.3.3.1 Principle of the specification ..... | 11 | +| 4.3.3.2 Requirements ..... | 11 | +| 4.3.4 Radio frequency tolerance..... | 12 | +| 4.3.5 Output level dynamic operation ..... | 12 | +| 4.3.6 Phase accuracy..... | 12 | +| 4.3.7 Intermodulation attenuation..... | 12 | +| 4.4 Receiver characteristics..... | 12 | +| 4.4.1 Blocking characteristics..... | 13 | +| 4.4.2 AM suppression characteristics..... | 14 | +| 4.4.3 Intermodulation characteristics..... | 14 | +| 4.5 Transmitter / receiver performance ..... | 15 | +| 4.5.1 Nominal error rate ..... | 15 | +| 4.5.2 Reference sensitivity level..... | 15 | +| 4.5.3 Reference interference level ..... | 16 | +| 4.5.4 Erroneous frame indication performance ..... | 16 | +| 4.5.5 Access performance at high input levels ..... | 17 | +| 4.5.6 Frequency hopping performance under interference conditions ..... | 17 | +| 5 Radio subsystem frequency control ..... | 21 | +| 5.1 Void..... | 21 | +| 5.2 General ..... | 21 | +| 5.3 Adaptive Frequency Allocation (AFA)..... | 21 | +| 5.4 TFH carrier list selection..... | 21 | +| 5.4.1 Acceptance procedure..... | 21 | +| 5.4.1.1 Basic threshold..... | 21 | +| 5.4.1.2 Sliding window technique ..... | 22 | +| 5.4.1.3 Fixed window technique ..... | 22 | +| 5.4.1.4 List extension check..... | 22 | +| 5.4.2 Parameters ..... | 22 | +| 5.4.3 AFA and TFH selection performance requirements..... | 22 | +| 5.5 CTS Beacon channel carrier selection ..... | 23 | +| 5.6 Timeslot assignment for dedicated connection ..... | 23 | +| 5.7 Frequency control parameters ..... | 23 | + +**Annex A (informative): Spectrum characteristics (spectrum due to the modulation) ..... 25** + +**Annex B (normative): Transmitted power level versus time..... 27** + +**Annex C (normative): Environmental conditions..... 28** + +C.1 General..... 28 + +C.2 Temperature ..... 28 + +C.3 Voltage..... 28 + +**Annex D (informative): Change history..... 29** + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the requirements for the CTS-Fixed Part (CTS-FP) transceiver of the digital mobile cellular and personal communication systems operating in the 900 MHz (P-GSM and E-GSM) and 1 800 MHz band (GSM 900 and DCS 1 800), and specifies the Radio subsystem frequency control implemented in the CTS-Fixed Part. + +Unless otherwise stated, the requirements defined in the present document apply to the full range of environmental conditions specified for the CTS-FP equipment (see annex C). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [3] GSM 03.52 : "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); Lower layers of the CTS radio interface; Stage 2". +- [4] GSM 04.56 : "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); CTS radio interface layer 3 specification". +- [5] GSM 05.01: "Digital cellular telecommunications system (Phase 2+); Physical layer on the radio path General description". +- [6] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". +- [7] GSM 05.04: "Digital cellular telecommunications system (Phase 2+); Modulation". +- [8] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [9] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". +- [10] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization". +- [11] GSM 11.56: "Digital cellular telecommunications system (Phase 2+); CTS-Fixed Part conformance specification". +- [12] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); CTS Architecture Description; Stage 2". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**CTS Mobile Station:** GSM-MS supporting CTS. + +**CTS Fixed Part:** CTS-FP is a device which acts as a link between the CTS-MS and the fixed network. + +**GSM-CTS:** Cordless Telephony System based on GSM. + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in GSM 01.04. In addition, the following abbreviations are used: + +| | | +|--------|-------------------------------| +| AFA | Adaptive Frequency Allocation | +| CTS | Cordless Telephony System | +| CTS-FP | CTS-Fixed Part | +| CTS-MS | CTS-Mobile Station | +| GFL | Generic Frequency List | +| TFH | Total Frequency Hopping | + +# 4 Radio transmission and reception + +## 4.1 Frequency band and channels arrangements + +i) Standard or primary GSM 900 Band, P-GSM: + +- for Standard GSM 900 band, the CTS-FP is required to operate in the following frequency band: + - 890 MHz to 915 MHz: CTS-FP receive; + - 935 MHz to 960 MHz: CTS-FP transmit. + +ii) Extended GSM 900 Band, E-GSM (includes Standard GSM 900 band): + +- for Extended GSM 900 band, the CTS-FP is required to operate in the following frequency band: + - 880 MHz to 915 MHz: CTS-FP receive; + - 925 MHz to 960 MHz: CTS-FP transmit. + +iii) DCS 1 800 Band: + +- for DCS 1 800 band, the CTS-FP is required to operate in the following band: + - 1 710 MHz to 1 785 MHz: CTS-FP receive; + - 1 805 MHz to 1 880 MHz: CTS-FP transmit. + +The carrier spacing is 200 kHz. + +The carrier frequency is designated by the absolute radio frequency channel number (ARFCN) as specified in GSM 05.05 clause 2. + +## 4.2 Reference configuration + +The reference configuration for the CTS-FP radio subsystem is described in GSM 05.01. + +## 4.3 Transmitter characteristics + +Throughout this clause, unless otherwise stated, requirements are given in terms of power levels at the antenna connector of the equipment. If an active device is added to the CTS-FP antenna connector, the requirements of this clause shall also be met at the output of this active device. For equipment with integral antenna only, a reference antenna with 0 dBi gain shall be assumed. + +The term output power refers to the measure of the power when averaged over the useful part of the burst (see annex B). + +The term peak hold refers to a measurement where the maximum is taken over a sufficient time that the level would not significantly increase if the holding time were longer. + +### 4.3.1 Output power + +The CTS-FP maximum output power and lowest nominal output power shall be, as defined in the following table. + +| | GSM 900 | DCS 1 800 | Tolerance (dB) for conditions | | +|------------------------------|---------|-----------|-------------------------------|-----------| +| | | | normal | extreme | +| Maximum Nominal output power | 11 dBm | 12 dBm | +0/-2 | +0,5/-2,5 | +| Lowest Nominal output power | -9 dBm | -8 dBm | ±4 | ±5 | + +The different power control levels needed to support downlink adaptive RF power control (see GSM 05.08) shall have the nominal output power as defined in the table below, starting from the power control level for the lowest nominal output power up to the power control level for the maximum nominal output power as defined in the table above. + +| GSM 900 | | | | +|---------------------|----------------------------|-------------------------------|-----------| +| Power control level | Nominal Output power (dBm) | Tolerance (dB) for conditions | | +| | | normal | extreme | +| 1 | 11 | +0/-2 | +0,5/-2,5 | +| 2 | 9 | ±2 | ±3 | +| 3 | 7 | ±3 | ±4 | +| 4 | 5 | ±3 | ±4 | +| 5 | 3 | ±3 | ±4 | +| 6 | 1 | ±3 | ±4 | +| 7 | -1 | ±3 | ±4 | +| 8 | -3 | ±4 | ±5 | +| 9 | -5 | ±4 | ±5 | +| 10 | -7 | ±4 | ±5 | +| 11-14 | -9 | ±4 | ±5 | + +| DCS 1 800 | | | | +|---------------------|----------------------------|-------------------------------|-----------| +| Power control level | Nominal Output power (dBm) | Tolerance (dB) for conditions | | +| | | normal | extreme | +| 1-4 | 12 | +0/-2 | +0,5/-2,5 | +| 5 | 10 | $\pm 2$ | $\pm 3$ | +| 6 | 8 | $\pm 3$ | $\pm 4$ | +| 7 | 6 | $\pm 3$ | $\pm 4$ | +| 8 | 4 | $\pm 3$ | $\pm 4$ | +| 9 | 2 | $\pm 3$ | $\pm 4$ | +| 10 | 0 | $\pm 3$ | $\pm 4$ | +| 11 | -2 | $\pm 4$ | $\pm 5$ | +| 12 | -4 | $\pm 4$ | $\pm 5$ | +| 13 | -6 | $\pm 4$ | $\pm 5$ | +| 14 | -8 | $\pm 4$ | $\pm 5$ | + +NOTE: The above definition of the power control levels for GSM 900 and DCS 1800 allows to have an equivalent indoor coverage when the same power control level is applied in GSM 900 and DCS 1800. + +Furthermore, the difference in output power actually transmitted by the CTS-FP between two power control levels where the difference in nominal output power indicates an increase of 2 dB (taking into account the restrictions due to nominal maximum and lowest output powers), shall be $+2 \pm 1,5$ dB. Similarly, if the difference in output power actually transmitted by the CTS-FP between two power control levels where the difference in nominal output power indicates a decrease of 2 dB (taking into account the restrictions due to nominal maximum and lowest output powers), shall be $-2 \pm 1,5$ dB. + +### 4.3.2 Output RF spectrum + +The specifications contained in this clause apply to CTS-FP, in frequency hopping as well as in non frequency hopping mode. + +Due to the bursty nature of the signal, the output RF spectrum results from two effects: + +- the modulation process; +- the power ramping up and down (switching transients). + +The two effects are specified separately; the measurement method used to analyse separately those two effects is specified in GSM 11.56. It is based on the "ringing effect" during the transients, and is a measurement in the time domain, at each point in frequency. + +The limits specified thereunder are based on a 5-pole synchronously tuned measurement filter. + +#### 4.3.2.1 Spectrum due to the modulation and wide band noise + +The output RF modulation spectrum is specified in the following tables. A mask representation of the present document is shown in annex A. The present document applies for all RF channels supported by the equipment. + +The specification applies to the entire of the relevant transmit band and up to 2 MHz either side. + +The specification shall be met under the following measurement conditions: + +- zero frequency scan, filter bandwidth and video bandwidth of 30 kHz up to 1800 kHz from the carrier and 100 kHz at 1800 kHz and above from the carrier, with averaging done over 50 % to 90 % of the useful part of the transmitted bursts, excluding the midamble, and then averaged over at least 200 such burst measurements. Above 1800 kHz from the carrier only measurements centred on 200 kHz multiples are taken with averaging over 50 bursts; + +- when tests are done in frequency hopping mode, the averaging shall include only bursts transmitted when the hopping carrier corresponds to the nominal carrier of the measurement. The specifications then apply to the measurement results for any of the hopping frequencies. + +The power level is the "actual absolute output power" defined in clause 4.3.1. + +The figures in tables a) and b) below, at the horizontally listed frequency offset from the carrier (kHz), are then the maximum allowed level (dB) relative to a measurement in 30 kHz on the carrier. + +a) GSM 900 CTS-FP: + +| | 100 | 200 | 250 | 400 | $\geq 600$
$< 1\,800$ | $\geq 1\,800$
$< 6\,000$ | $\geq 6\,000$ | +|-----|------|-----|-----|-----|--------------------------|-----------------------------|---------------| +| dBc | +0,5 | -30 | -33 | -60 | -60 | -68 | -71 | + +b) DCS 1800 CTS-FP: + +| | 100 | 200 | 250 | 400 | $\geq 600$
$< 1\,800$ | $\geq 1\,800$
$< 6\,000$ | $\geq 6\,000$ | +|-----|------|-----|-----|-----|--------------------------|-----------------------------|---------------| +| dBc | +0,5 | -30 | -33 | -60 | -60 | -63 | -67 | + +The following exceptions shall apply, using the same measurement conditions as specified above: + +- in the combined range 600 kHz to 6 MHz above and below the carrier, in up to three bands of 200 kHz width centred on a frequency which is an integer multiple of 200 kHz, exceptions at up to -36 dBm are allowed; +- above 6 MHz offset from the carrier in up to 12 bands of 200 kHz width centred on a frequency which is an integer multiple of 200 kHz, exceptions at up to -36 dBm are allowed. For the BTS only one transmitter is active for this test. + +Using the same measurement conditions as specified above, if a requirement in tables a) and b) is tighter than the limit given in the following, the latter shall be applied instead. + +| Frequency offset from the carrier | GSM 900 | DCS 1 800 | +|-----------------------------------|---------|-----------| +| $< 1\,800$ kHz | -69 dBm | -64 dBm | +| $\geq 1\,800$ kHz | -64 dBm | -59 dBm | + +#### 4.3.2.2 Spectrum due to switching transient + +Those effects are also measured in the time domain and the specifications assume the following measurement conditions: zero frequency scan, filter bandwidth 30 kHz, peak hold, and video bandwidth 100 kHz. + +The example of a waveform due to a burst as seen in a 30 kHz filter offset from the carrier is given in the figure 1 of GSM 05.05. + +The maximum level measured, after any filters and combiners, at the indicated offset from the carrier, shall be: + +| | Maximum level measured | | | | +|---------------------|------------------------|---------|-----------|-----------| +| | 400 kHz | 600 kHz | 1 200 kHz | 1 800 kHz | +| GSM 900 / DCS 1 800 | -36 dBm | -36 dBm | -36 dBm | -36 dBm | + +### 4.3.3 Spurious emission + +The limits specified thereunder are based on a 5-pole synchronously tuned measurement filter. + +#### 4.3.3.1 Principle of the specification + +In this clause, the spurious transmissions (whether modulated or unmodulated) and the switching transients are specified together by measuring the peak power in a given bandwidth at various frequencies. The bandwidth is increased as the frequency offset between the measurement frequency and, either the carrier, or the edge of the CTS-FP transmit band, increases. The effect for spurious signals of widening the measurement bandwidth is to reduce the allowed total spurious energy per MHz. The effect for switching transients is to effectively reduce the allowed level of the switching transients (the peak level of a switching transient increases by 6 dB for each doubling of the measurement bandwidth). The conditions are specified in the following table, a peak-hold measurement being assumed. + +The measurement conditions for radiated and conducted spurious are specified separately in GSM 11.56. The frequency bands where these are actually measured may differ from one type to the other (see GSM 11.56). + +a) + +| Band | Frequency offset
(offset from carrier) | Measurement bandwidth | +|-------------------|-------------------------------------------|-----------------------| +| relevant transmit | $\geq 1,8$ MHz | 30 kHz | +| band | $\geq 6$ MHz | 100 kHz | + +b) + +| Band | Frequency offset | Measurement bandwidth | +|--------------------------------------------------|-----------------------------------------------|-----------------------| +| 100 kHz to 50 MHz | - | 10 kHz | +| 50 MHz to 500 MHz | - | 100 kHz | +| above 500 MHz outside the relevant transmit band | (offset from edge of the relevant above band) | | +| | $\geq 2$ MHz | 30 kHz | +| | $\geq 5$ MHz | 100 kHz | +| | $\geq 10$ MHz | 300 kHz | +| | $\geq 20$ MHz | 1 MHz | +| | $\geq 30$ MHz | 3 MHz | + +The measurement settings assumed correspond, for the resolution bandwidth to the value of the measurement bandwidth in the table, and for the video bandwidth to approximately three times this value. + +#### 4.3.3.2 Requirements + +The power measured in the conditions specified in clause 4.3.3.1a, for a CTS-FP when allocated a channel, shall be no more than -36 dBm. + +The power measured in the conditions specified in clause 4.3.3.1b for a CTS-FP, when allocated a channel, shall be no more than: + +- 250 nW (-36 dBm) in the frequency band 9 kHz to 1 GHz; +- 1 µW (-30 dBm) in the frequency band 1 GHz to 12,75 GHz. + +When allocated a channel, the power emitted by the CTS-FP, when measured using the measurement conditions specified in 4.3.2.1, but with averaging over at least 50 burst measurements, with a filter and video bandwidth of 100 kHz, for measurements centred on 200 kHz multiples, in the band 880 MHz to 915 MHz shall be no more than -75 dBm, and in the band 1 710 MHz to 1 785 MHz, shall be no more than -69 dBm. + +As exceptions up to five measurements with a level up to -36 dBm are permitted in each of the bands 880 MHz to 915 MHz and 1 710 MHz to 1 785 MHz for each ARFCN used in the measurements. + +When hopping, this applies to each set of measurements, grouped by the hopping frequencies as described in clause 4.3.2.1. + +### 4.3.4 Radio frequency tolerance + +The radio frequency tolerance for the CTS-FP is defined in GSM 05.10. + +### 4.3.5 Output level dynamic operation + +NOTE: The term "any transmit band channel" is used here to mean: + +any RF channel of 200 kHz bandwidth centred on a multiple of 200 kHz which is within the relevant transmit band. + +The output power can be reduced by steps of 2 dB as defined in clause 4.3.1. + +The transmitted power level relative to time when sending a burst is shown in annex B. The timing of the transmitted burst is specified in GSM 05.10. Between the active bursts, the residual output power shall be maintained at, or below, the level of: + +- -59 dBc or -54 dBm, whichever is the greater for GSM 900; +- -48 dBc or -48 dBm, whichever is the greater for DCS 1 800; + +in any transmit band channel. + +A measurement bandwidth of at least 300 kHz is assumed. + +### 4.3.6 Phase accuracy + +The same requirements as defined in GSM 05.05 clause 4.6 shall apply. + +### 4.3.7 Intermodulation attenuation + +The intermodulation attenuation is the ratio of the power level of the wanted signal to the power level of an intermodulation component. It is a measure of the capability of the transmitter to inhibit the generation of signals in its non-linear elements caused by the presence of the carrier and an interfering signal reaching the transmitter via the antenna. + +The maximum level of any intermodulation product, when measured as peak hold in a 300 kHz bandwidth, shall be 50 dB below the wanted signal when an interfering CW signal is applied within the DCS 1 800 CTS-FP transmit band at a frequency offset of 800 kHz with a power level 40 dB below the power level of the wanted (DCS 1 800 modulated) signal. + +## 4.4 Receiver characteristics + +In this clause, the requirements are given in terms of power levels at the antenna connector of the receiver. Equipment with integral antenna may be taken into account by converting these power level requirements into field strength requirements, assuming a 0 dBi gain antenna. This means that the tests on equipment on integral antenna will consider + +fields strengths (E) related to the power levels (P) specified, by the following formula (derived from the formula $E = P + 20\log F_{(\text{MHz})} + 77.2$ ): + +assuming $F = 925$ MHz : $E$ (dB $\mu$ V/m) = $P$ (dBm) + 136.5 for GSM 900 + +assuming $F = 1\,795$ MHz : $E$ (dB $\mu$ V/m) = $P$ (dBm) + 142.3 for DCS 1 800 + +Static propagation conditions are assumed in all cases, for both wanted and unwanted signals. For clauses 4.4.1 and 4.4.2, values given in dBm are indicative, and calculated assuming a 50 ohms impedance. + +### 4.4.1 Blocking characteristics + +The blocking characteristics of the receiver are specified separately for in-band and out-of-band performance as identified in the following tables. + +| Frequency band | Frequency range (MHz) | | +|-----------------|-----------------------|---------------------| +| | GSM 900
CTS-FP | GSM 1 800
CTS-FP | +| in-band | 860 - 925 | 1 690 - 1 805 | +| out-of-band (a) | 0.1 - < 860 | 0.1 - 1 610 | +| out-of-band (b) | N/A | > 1 610 - < 1 690 | +| out-of band (c) | N/A | > 1 805 - 1 865 | +| out-of band (d) | > 925 - 12,750 | > 1 865 - 12,750 | + +The reference sensitivity performance as specified in table 1 shall be met when the following signals are simultaneously input to the receiver: + +- a useful signal at frequency $f_0$ , 3 dB above the reference sensitivity level as specified in clause 4.5.2; +- a continuous, static sine wave signal at a level as in the table below and at a frequency ( $f$ ) which is an integer multiple of 200 kHz; + +with the following exceptions, called spurious response frequencies: + +- GSM 900: in band, for a maximum of six occurrences (which if grouped shall not exceed three contiguous occurrences per group); +DCS 1 800: in band, for a maximum of twelve occurrences (which if grouped shall not exceed three contiguous occurrences per group); +- out of band, for a maximum of 24 occurrences (which if below $f_0$ and grouped shall not exceed three contiguous occurrences per group). + +where the above performance shall be met when the continuous sine wave signal ( $f$ ) is set to a level of 70 dB $\mu$ V (emf) (i.e. -43 dBm). + +| Frequency
band | GSM 900 | | DCS 1 800 | | +|----------------------------------|---------------|-----|---------------|-----| +| | CTS-FP | | CTS-FP | | +| | dBμV
(emf) | dBm | dBμV
(emf) | dBm | +| in-band | | | | | +| 600 kHz $\leq f-f_0 < 800$ kHz | 70 | -43 | 70 | -43 | +| 800 kHz $\leq f-f_0 < 1.6$ MHz | 70 | -43 | 70 | -43 | +| 1.6 MHz $\leq f-f_0 < 3$ MHz | 80 | -33 | 80 | -33 | +| 3 MHz $\leq f-f_0 $ | 90 | -23 | 87 | -26 | +| out-of-band | | | | | +| (a) | 113 | 0 | 113 | 0 | +| (b) | - | - | 101 | -12 | +| (c) | - | - | 101 | -12 | +| (d) | 113 | 0 | 113 | 0 | + +The following exceptions to the level of the sine wave signal (f) in the above table shall apply: + +| | | +|---------------------------------------------|---------------| +| for E-GSM CTS-FP, in the band 925 - 935 MHz | -5 dBm | +|---------------------------------------------|---------------| + +### 4.4.2 AM suppression characteristics + +The reference sensitivity performance as specified in table 1 shall be met when the following signals are simultaneously input to the receiver. + +- A useful signal at $f_0$ , 3dB above reference sensitivity level as specified in clause 4.5.2. +- A single frequency (f), in the relevant receive band, $|f-f_0| > 6$ MHz, which is an integer multiple of 200 kHz, a GSM TDMA signal modulated by any 148-bit sequence of the 511-bit pseudo random bit sequence, defined in CCITT Recommendation O.153 fascicle IV.4, at a level as defined in the table below. The interferer shall have one timeslot active and the frequency shall be at least 2 channels separated from any identified spurious response. The transmitted bursts shall be synchronized to but delayed in time between 61 and 86 bit periods relative to the bursts of the wanted signal. + +NOTE: When testing this requirement, a notch filter may be necessary to ensure that the co-channel performance of the receiver is not compromised. + +| | CTS-FP
(dBm) | +|-----------|-----------------| +| GSM 900 | -31 | +| DCS 1 800 | -31 | + +### 4.4.3 Intermodulation characteristics + +The reference sensitivity performance as specified in table 1 shall be met when the following signals are simultaneously input to the receiver: + +- a useful signal at frequency $f_0$ , 3 dB above the reference sensitivity level as specified in clause 4.5.2; +- a continuous, static sine wave signal at frequency $f_1$ and a level of 64 dBμV (emf) (i.e. -49 dBm); +- any 148-bits subsequence of the 511-bits pseudo-random sequence, defined in CCITT Recommendation O.153 fascicle IV.4 modulating a signal at frequency $f_2$ , and a level of 64 dBμV (emf) (i.e. -49 dBm); + +such that $f_0 = 2f_1 - f_2$ and $|f_2 - f_1| = 800$ kHz. + +NOTE: For clauses 4.4.2 and 4.4.3 instead of any 148-bits subsequence of the 511-bits pseudo-random sequence, defined in CCITT Recommendation O.153 fascicle IV.4, it is also allowed to use a more random pseudo-random sequence. + +## 4.5 Transmitter / receiver performance + +In order to assess the error rate performance that is described in this clause it is required for a CTS-FP equipment to have a "loop back" facility by which the equipment transmits back the same information that it decoded, in the same mode. This facility is specified in GSM 11.56. + +This clause aims at specifying the receiver performance, taking into account that transmitter errors must not occur, and that the transmitter shall be tested separately (see clause 4.3.6). All the values given are valid if any of the features: discontinuous transmission (DTx), discontinuous reception (DRx), or frequency hopping (FH) are used or not. The received power levels under multipath fading conditions given are the mean powers of the sum of the individual paths. + +In this clause power levels are given also in terms of field strength, assuming a 0 dBi gain antenna, to apply for the test of CTS-FPs with integral antennas. + +According to the CTSARCH operation specified in GSM 05.02 clause 6.5.1 ix), the receiver performance specified in this clause for the CTSARCH shall be met for at least one of the two bursts sent on the CTSARCH. + +### 4.5.1 Nominal error rate + +This clause describes the transmission requirements in terms of error rates in nominal conditions i.e. without interference and with an input level of 20 dB above the reference sensitivity level. The relevant propagation conditions appear in GSM 05.05 annex C. + +Under the following propagation conditions, the chip error rate, equivalent to the bit error rate of the non protected bits (TCH/FS, class II) shall have the following limits: + +- static channel: $BER \leq 10^{-4}$ . + +This performance shall be maintained up to -40 dBm input level for static and multipath conditions. + +Furthermore, for static conditions, a bit error rate of $10^{-3}$ shall be maintained up to -15 dBm for GSM 900, -23 dBm for DCS 1 800. + +### 4.5.2 Reference sensitivity level + +The reference sensitivity performance in terms of frame erasure, bit error, or residual bit error rates (whichever appropriate) is specified in table 1, according to the type of channel and the propagation condition. Propagation conditions other than static and TI5 no FH are for CTS-FP not relevant and need not be tested. + +The actual sensitivity level is defined as the input level for which this performance is met. The actual sensitivity level shall be less than a specified limit, called the reference sensitivity level. The reference sensitivity level shall be: + +- | | | | | +|---|----------------------|---|----------| +| - | for GSM 900 CTS-FP | : | -102 dBm | +| - | for DCS 1 800 CTS-FP | : | -102 dBm | + +The reference sensitivity performance specified above need not be met in the following cases: + +- for CTS-FP at the static channel, if the received level on either of the two adjacent timeslots to the wanted exceed the wanted timeslot by more than 20 dB. + +The interfering adjacent time slots shall be static with valid GSM signals in all cases. + +NOTE: in the TI5 no FH propagation channel, the CTS-FP shall meet a performance equal to that for the TU50 no FH (900MHz) for a useful signal 3dB greater than the relevant reference sensitivity. + +### 4.5.3 Reference interference level + +The reference interference performance (for cochannel, $C/I_c$ , or adjacent channel, $C/I_a$ ) in terms of frame erasure, bit error or residual bit error rates (whichever appropriate) is specified in table 2, according to the type of channel. Propagation conditions other than static and TI5 no FH are for CTS-FP not relevant and need not be tested. + +The actual interference ratio is defined as the interference ratio for which this performance is met. The actual interference ratio shall be less than a specified limit, called the reference interference ratio. The reference interference ratio shall be: + +- | | | | | | | +|---|-------------------------------------|---|------------|---|--------| +| - | for cochannel interference | : | $C/I_c$ | = | 9 dB | +| - | for adjacent (200 kHz) interference | : | $C/I_{a1}$ | = | -9 dB | +| - | for adjacent (400 kHz) interference | : | $C/I_{a2}$ | = | -41 dB | +| - | for adjacent (600 kHz) interference | : | $C/I_{a3}$ | = | -49 dB | + +These specifications apply for a wanted signal input level of 20 dB above the reference sensitivity level, and for a random, continuous, GSM-modulated interfering signal. However, the CTS-FP 900MHz and 1800MHz need only meet, measured in the TI5 no FH propagation channel, an interference performance equal to that for the TU50 no FH channel (900MHz) with a useful $C/I$ of 4dB greater than the relevant interference performance. + +In any case the wanted and interfering signals shall be subject to the same propagation profiles (see GSM 05.05 annex C), independent on the two channels. + +For adjacent channel interference, if in order to ease measurement, a TI5 (no FH) faded wanted signal, and a static adjacent channel interferer are used, the interference performance shall be: + +#### GSM 900 DCS 1 800 + +| | | | +|------------------|------------------|------------------| +| TCH/FS (FER): | 10,2 $\alpha$ % | 5,1 $\alpha$ % | +| Class Ib (RBER): | 0,72/ $\alpha$ % | 0,45/ $\alpha$ % | +| Class II (RBER): | 8,8 % | 8,9 % | +| FACCH (FER): | 17,1 % | 6,1 % | + +when a margin of 4dB above reference sensitivity is included. + +### 4.5.4 Erroneous frame indication performance + +- On a speech TCH (TCH/FS or TCH/HS) with a random RF input, of the frames believed to be FACCH or SACCH, the overall reception performance shall be such that no more than 0,002 % of the frames are assessed to be error free. +- On a speech TCH (TCH/FS or TCH/HS) with a random RF input, the overall reception performance shall be such that, on average, less than one undetected bad speech frame (false bad frame indication BFI) shall be measured in one minute. +- On a speech TCH (TCH/FS or TCH/HS), when DTX is activated with SID frames and SACCH frames received 20 dB above the reference sensitivity level and with no transmission at the other bursts of the TCH, the overall reception shall be such that, on average, less than one undetected bad speech frame (false bad frame indication BFI) shall be measured in one minute for CTS-FP. +- For a CTS-FP on a CTSARCH with a random RF input, the overall reception performance shall be such that less than 0,02 % of frames are assessed to be error free. + +### 4.5.5 Access performance at high input levels + +Under static propagation conditions with a received input level from 20 dB above the reference sensitivity level up to -15 dBm for GSM900 and -23 dBm for DCS1800, and a single CTS-MS sending an access request, the CTS-FP FER shall be less than 1% for CTSARCH. + +### 4.5.6 Frequency hopping performance under interference conditions + +Under the following conditions: + +- a useful signal, cyclic frequency hopping over four carriers under static conditions, with equal input levels 20 dB above reference sensitivity level; +- a random, continuous, GMSK-modulated interfering signal on only one of the carriers at a level 10 dB higher than the useful signal. + +The FER for TCH/FS shall be less than 5%. + +**Table 1: Reference sensitivity performance** + +| GSM 900 | | | +|----------------------------------|-------------------------------|------------------------| +| Type of channel | Propagation conditions | | +| | static | TI5
(no FH) | +| FACCH/H (FER) | 0,1 % | 6,9 % | +| FACCH/F (FER) | 0,1 % | 8,0 % | +| CTSAGCH, (FER) | 0,1 % | 13 % | +| CTSPCH, SACCH | | | +| CTSBCH-SB, (FER) | 1 % | 16 % | +| CTSARCH | | | +| TCH/FS (FER) | 0,1 $\alpha$ % | 6 $\alpha$ % | +| class Ib (RBER) | 0,4/ $\alpha$ % | 0,4/ $\alpha$ % | +| class II (RBER) | 2 % | 8 % | +| TCH/EFS (FER) | < 0,1 % | 8 % | +| (RBER Ib) | < 0,1 % | 0,21 % | +| (RBER II) | 2,0 % | 7 % | +| TCH/HS (FER) | 0,025 % | 4,1 % | +| class Ib (RBER, BFI=0) | 0,001 % | 0,36 % | +| class II (RBER, BFI=0) | 0,72 % | 6,9 % | +| (UFR) | 0,048 % | 5,6 % | +| class Ib (RBER,(BFI or UFI)=0) | 0,001 % | 0,24 % | +| (EVSIDR) | 0,06 % | 6,8 % | +| (RBER, SID=2 and (BFI or UFI)=0) | 0,001 % | 0,01 % | +| (ESIDR) | 0,01 % | 3,0 % | +| (RBER, SID=1 or SID=2) | 0,003 % | 0,3 % | +| DCS 1 800 | | | +| Type of channel | Propagation conditions | | +| | static | TI5
(no FH) | +| FACCH/H (FER) | 0,1 % | 7,2 % | +| FACCH/F (FER) | 0,1 % | 3,9 % | +| CTSAGCH, (FER) | 0,1 % | 9 % | +| CTSPCH, SACCH | | | +| CTSBCH-SB, (FER) | 1 % | 19 % | +| CTSARCH | | | +| TCH/FS (FER) | 0,1 $\alpha$ % | 3 $\alpha$ % | +| class Ib (RBER) | 0,4/ $\alpha$ % | 0,3/ $\alpha$ % | +| class II (RBER) | 2 % | 8 % | +| TCH/EFS (FER) | < 0,1 % | 4 % | +| (RBER Ib) | < 0,1 % | 0,12 % | +| (RBER II) | 2,0 % | 8 % | +| (continued) | | | + +Table 1 (concluded): Reference sensitivity performance + +| DCS 1 800 | | | +|----------------------------------|------------------------|----------------| +| Type of Channel | Propagation conditions | | +| | static | TI5
(no FH) | +| TCH/HS (FER) | 0,025 % | 4,2 % | +| class Ib (RBER, BFI=0) | 0,001 % | 0,38 % | +| class II (RBER, BFI=0) | 0,72 % | 6,9 % | +| (UFR) | 0,048 % | 5,7 % | +| class Ib (RBER, (BFI or UFI)=0) | 0,001 % | 0,26 % | +| (EVSIDR) | 0,06 % | 7,0 % | +| (RBER, SID=2 and (BFI or UFI)=0) | 0,001 % | 0,01 % | +| (ESIDR) | 0,01 % | 3,0 % | +| (RBER, SID=1 or SID=2) | 0,003 % | 0,33 % | + +NOTE 1: Definitions: +FER: Frame erasure rate (frames marked with BFI=1). +UFR: Unreliable frame rate (frames marked with (BFI or UFI)=1). +EVSIDR: Erased Valid SID frame rate (frames marked with (SID=0) or (SID=1) or ((BFI or UFI)=1) if a valid SID frame was transmitted). +ESIDR: Erased SID frame rate (frames marked with SID=0 if a valid SID frame was transmitted). +BER: Bit error rate. +RBER, BFI=0: Residual bit error rate (defined as the ratio of the number of errors detected over the frames defined as "good" to the number of transmitted bits in the "good" frames). RBER, (BFI or UFI)=0: Residual bit error rate (defined as the ratio of the number of errors detected over the frames defined as "reliable" to the number of transmitted bits in the "reliable" frames). +RBER, SID=2 and (BFI or UFI)=0: Residual bit error rate of those bits in class I which do not belong to the SID codeword (defined as the ratio of the number of errors detected over the frames that are defined as "valid SID frames" to the number of transmitted bits in these frames, under the condition that a valid SID frame was sent). +RBER, SID=1 or SID=2: Residual bit error rate of those bits in class I which do not belong to the SID codeword (defined as the ratio of the number of errors detected over the frames that are defined as "valid SID frames" or as "invalid SID frames" to the number of transmitted bits in these frames, under the condition that a valid SID frame was sent). + +NOTE 2: $1 \leq \alpha \leq 1,6$ . The value of $\alpha$ can be different for each channel condition but must remain the same for FER and class Ib RBER measurements for the same channel condition. + +NOTE 3: FER for CTSCCHs takes into account frames which are signalled as being erroneous (by the FIRE code, parity bits, or other means) or where the stealing flags are wrongly interpreted. + +Table 2: Reference interference performance + +| GSM 900 | | | +|----------------------------------|-----------|------------------------| +| Type of channel | | Propagation conditions | +| | | TI5 (no FH) | +| FACCH/H | (FER) | 6,7 % | +| FACCH/F | (FER) | 9,5 % | +| CTSAGCH, CTSPCH, SACCH | (FER) | 13 % | +| CTSBCH-SB, CTSARCH | (FER) | 17 % | +| TCH/FS | (FER) | 6 $\alpha$ % | +| class Ib (RBER) | | 0,4/ $\alpha$ % | +| class II (RBER) | | 8 % | +| TCH/EFS | (FER) | 9 % | +| | (RBER Ib) | 0,20 % | +| | (RBER II) | 7 % | +| TCH/HS | (FER) | 5,0 % | +| class Ib (RBER, BFI=0) | | 0,29 % | +| class II (RBER, BFI=0) | | 7,1 % | +| | (UFR) | 6,1 % | +| class Ib (RBER, (BFI or UFI)=0) | | 0,21 % | +| | (EVSIDR) | 7,0 % | +| (RBER, SID=2 and (BFI or UFI)=0) | | 0,01 % | +| | (ESIDR) | 3,6 % | +| (RBER, SID=1 or SID=2) | | 0,26 % | +| DCS 1 800 | | | +| Type of channel | | Propagation conditions | +| | | TI5 (no FH) | +| FACCH/H | (FER) | 6,9 % | +| FACCH/F | (FER) | 3,4 % | +| CTSAGCH, CTSPCH, SACCH | (FER) | 9 % | +| CTSBCH-SB, CTSARCH | (FER) | 19 % | +| TCH/FS | (FER) | 3 $\alpha$ % | +| class Ib (RBER) | | 0,25/ $\alpha$ % | +| class II (RBER) | | 8,1 % | +| TCH/EFS | (FER) | 3 % | +| | (RBER Ib) | 0,10 % | +| | (RBER II) | 8 % | +| (continued) | | | + +**Table 2 (concluded): Reference interference performance** + +| DCS 1 800 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| Type of channel | Propagation conditions | +| | TI5 (no FH) | +| TCH/HS (FER) | 5,0 % | +| class Ib (RBER, BFI=0) | 0,29 % | +| class II (RBER, BFI=0) | 7,2 % | +| (UFR) | 6,1 % | +| class Ib (RBER, (BFI or UFI)=0) | 0,21 % | +| (EVSIDR) | 7,0 % | +| (RBER, SID=2 and (BFI or UFI)=0) | 0,01 % | +| (ESIDR) | 3,6 % | +| (RBER, SID=1 or SID=2) | 0,26 % | +| NOTE 1: Definitions:
FER: Frame erasure rate (frames marked with BFI=1).
UFR: Unreliable frame rate (frames marked with (BFI or UFI)=1).
EVSIDR: Erased Valid SID frame rate (frames marked with (SID=0) or (SID=1) or ((BFI or UFI)=1) if a valid SID frame was transmitted).
ESIDR: Erased SID frame rate (frames marked with SID=0 if a valid SID frame was transmitted).
BER: Bit error rate.
RBER, BFI=0: Residual bit error rate (defined as the ratio of the number of errors detected over the frames defined as "good" to the number of transmitted bits in the "good" frames).
RBER, (BFI or UFI)=0: Residual bit error rate (defined as the ratio of the number of errors detected over the frames defined as "reliable" to the number of transmitted bits in the "reliable" frames).
RBER, SID=2 and (BFI or UFI)=0: Residual bit error rate of those bits in class I which do not belong to the SID codeword (defined as the ratio of the number of errors detected over the frames that are defined as "valid SID frames" to the number of transmitted bits in these frames, under the condition that a valid SID frame was sent).
RBER, SID=1 or SID=2: Residual bit error rate of those bits in class I which do not belong to the SID codeword (defined as the ratio of the number of errors detected over the frames that are defined as "valid SID frames" or as "invalid SID frames" to the number of transmitted bits in these frames, under the condition that a valid SID frame was sent). | | +| NOTE 2: $1 \leq \alpha \leq 1,6$ . The value of $\alpha$ can be different for each channel condition but must remain the same for FER and class Ib RBER measurements for the same channel condition. | | +| NOTE 3: FER for CTSCCHs takes into account frames which are signalled as being erroneous (by the FIRE code, parity bits, or other means) or where the stealing flags are wrongly interpreted. | | + +# 5 Radio subsystem frequency control + +Procedures shall be implemented in the CTS-FP by which it manages the radio frequency channels used for traffic or signalling between the CTS-FP and its attached CTS-MS. Those procedures shall be: + +- adaptive Frequency Allocation (AFA) algorithm; +- TFH carrier list selection; +- CTS Beacon channel carrier selection; +- timeslot assignment for dedicated connection. + +## 5.1 Void + +## 5.2 General + +The list of carriers on which the CTS-FP and CTS-MS are allowed to operate is called the Generic Frequency List (GFL). Different mechanisms are specified, in order to ensure that the CTS-FP and CTS-MS are using the most appropriate frequencies for transmission and reception. + +## 5.3 Adaptive Frequency Allocation (AFA) + +An Adaptive Frequency Allocation (AFA) algorithm shall be implemented in the CTS-FP. The input of the AFA algorithm shall be the table of interference levels measured by the CTS-MS during the AFA monitoring procedure (see GSM 05.08) on a subset of carriers of the GFL. These interference levels shall be filtered by the AFA algorithm, so that an ordered list of frequency carriers called the AFA table is generated. + +The use of the AFA algorithm shall be controlled by the parameter AFA\_USE; in the case where the AFA algorithm is not used, the AFA table shall contain the complete GFL. + +## 5.4 TFH carrier list selection + +A set of frequencies shall be selected from the AFA table by the CTS-FP for effective use by the CTS-FP and CTS-MS performing frequency hopping. This subset of frequencies is called the TFH carrier list. The decision for the carriers to be included in the TFH carrier list shall be defined by performing the acceptance procedure, which is controlled by the parameters given in table 3. + +In the case where the AFA algorithm is not used, the TFH carrier list shall contain the complete GFL. + +### 5.4.1 Acceptance procedure + +The absolute received signal level of a carrier shall be considered by defining different ranges in which different approaches with different parameters shall be applied. The algorithm shall start at the lowest range up to the highest until the stop condition of the applied criteria is reached. If the upper bound of the range is reached, the next range shall be processed. When one approach stops or the last range is finished, the list extension check shall be performed. The following approaches are defined. + +#### 5.4.1.1 Basic threshold + +The basic threshold approach shall always start from the carrier with the lowest interference level in the AFA table. All carriers below the higher bound of this range shall be included in the TFH carrier list. The second purpose is to assure that a minimum number of carriers is used. Therefore, the maximum from both conditions shall be used. + +#### 5.4.1.2 Sliding window technique + +Within a window containing a fixed number (SWT\_SIZE\_WIN) of the last carriers which were accepted, the average interference level shall be calculated. The interference level of the next carrier to be added shall be compared with the calculated average interference level. If the difference exceeds a distinct threshold INTERF\_THRESHOLD, the stop condition is reached, otherwise the carrier shall be added to the TFH carrier list. + +#### 5.4.1.3 Fixed window technique + +Within a window initially containing a fixed number (FWT\_SIZE\_WIN) of the last carriers which were accepted, the average interference level shall be calculated. The interference level of the next carrier to be added shall be compared with the calculated average interference level. If the difference exceeds a distinct threshold INTERF\_THRESHOLD, the stop condition is reached. Otherwise, the carrier shall be added to the TFH carrier list and the window size shall be increased. + +#### 5.4.1.4 List extension check + +After one of the other techniques stopped, the next carriers shall be compared with the last added carrier where the stop condition occurs. If the difference does not exceed a distinct threshold INTERF\_THRESHOLD, the carrier shall be added to the TFH carrier list. + +### 5.4.2 Parameters + +At least one range shall be defined by using the parameters given in the table 3. When only one range is defined the basic threshold approach shall be applied. The sliding and fixed window technique can be used in more than only one range with a separate parameter set for each. + +The first range defined shall start at a received signal level of -110 dBm and stop the upper bound defined in the parameter SEL\_RANGE(1). The range k shall start at the upper bound of the previous range (k-1) and stop at the upper bound defined in the parameter SEL\_RANGE(k). + +### 5.4.3 AFA and TFH selection performance requirements + +Considering the following scenario: + +- the GFL of the CTS-FP shall be a list of 9 carriers ( $f_1$ to $f_9$ ); +- a table of received interference levels measured by the CTS-MS shall be reported to the CTS-FP (see GSM 05.08) with the following values: + +| | Received interference level (in dBm) | +|-------|--------------------------------------| +| $f_1$ | -95 dBm | +| $f_2$ | -80 dBm | +| $f_3$ | -95 dBm | +| $f_4$ | -85 dBm | +| $f_5$ | -80 dBm | +| $f_6$ | -95 dBm | +| $f_7$ | -95 dBm | +| $f_8$ | -95 dBm | +| $f_9$ | -85 dBm | + +- the signal levels received by the CTS-FP on the 9 carriers of the GFL shall be less than -95 dBm; + +- the parameters of the TFH carrier list selection shall be set as follows: + +| Parameter name | Value | +|----------------------|----------| +| SEL_RANGE (1) | -108 dBm | +| APPROACH_TYPE (1) | BASIC | +| MIN_NB_FREQ | 4 | +| SEL_RANGE (2) | -102 dBm | +| APPROACH_TYPE (2) | SWT | +| SWT_SIZE_WIN (2) | 4 | +| INTERF_THRESHOLD (2) | 5 dB | +| SEL_RANGE (3) | -94 dBm | +| APPROACH_TYPE (3) | FWT | +| SWT_SIZE_WIN (3) | 3 | +| INTERF_THRESHOLD (3) | 4 dB | +| SEL_RANGE (4) | -48 dBm | +| APPROACH_TYPE (4) | EXT | +| SWT_SIZE_WIN (4) | 1 | +| INTERF_THRESHOLD (4) | 1 dB | + +With this scenario, after 6 successive AFA monitoring reports sent by the CTS-MS with the received interference levels specified above, the AFA and TFH carrier list selection procedures shall have selected the following TFH carrier list: (f1, f3, f6, f7, f8). + +## 5.5 CTS Beacon channel carrier selection + +A particular carrier shall be selected from the TFH carrier list : the CTS Beacon channel carrier. This carrier shall be used for the transmission of the CTSBCH in the downlink as well as for the transmission of other channels, as specified in GSM 05.02. + +Two selection techniques shall be used: + +- a random carrier from the TFH carrier list shall be selected; +- the carrier of the TFH carrier list showing the lowest interference level shall be selected. + +The specification of the selection technique to use shall be indicated in the CTSBCH\_SEL\_MODE parameter. + +## 5.6 Timeslot assignment for dedicated connection + +When the CTS-FP is attempting to establish a dedicated connection with a CTS-MS, the CTS-FP should select the timeslot showing the lowest received interference level. The selection should be based on measurements of received interference level performed by the CTS-FP on the uplink : a running average on at least 5 collected measurement samples should be maintained by the CTS-FP for each of the 8 timeslots of a TDMA frame, in order to assess the received interference level per timeslot. + +## 5.7 Frequency control parameters + +The parameters employed to control in frequency the radio link are shown in table 3. + +**Table 3: Radio sub-system frequency control parameters** + +| Parameter name | Description | Range | Bits | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------| +| GFL (1-m) | Generic Frequency List: contains m carriers represented by their ARFCN | 0-1023 | 10 | +| AFA_USE | Enable the use of the AFA algorithm:
0: used
1: not used | 0-1 | 1 | +| SEL_RANGE (1-n) | Upper bound of TFH carrier list selection range n°:
-110, -108, ..., -48 dBm in steps of 2 dBm | 0-31 | 5 | +| APPROACH_TYPE (1-n) | Type of approach used in selection range n°:
00: Basic threshold (BASIC)
01: Sliding window technique (SWT)
10: Fixed window technique (FWT)
11: List extension check (EXT) | 0-3 | 2 | +| MIN_NB_FREQ | Minimum number of carrier which shall be selected for the TFH carrier list by the Basic threshold approach | 0-31 | 5 | +| FWT_SIZE_WIN (1-n) | Minimum size of the window to compute the average for the FWT | 0-31 | 5 | +| SWT_SIZE_WIN (1-n) | Fixed size of the window to compute the average for the SWT | 0-31 | 5 | +| INTERF_THRESHOLD (1-n) | Maximum allowed difference between the current carrier to add, and the average value for SWT, FWT, and EXT:
0, 2, ..., 62 dB in steps of 2 dB | 0-31 | 5 | +| CTSBCH_SEL_MODE | CTSBCH carrier selection mode:
0: best carrier of TFH carrier list
1: random carrier from TFH carrier list | 0-1 | 1 | + +# Annex A (informative): Spectrum characteristics (spectrum due to the modulation) + +![Graph showing Relative power (dB) vs Frequency from the carrier (kHz) for GSM 900 CTS-FP spectrum due to modulation. The graph shows a sharp drop in power from 0 dB at 0 kHz to -60 dB at 400 kHz, followed by a stepped decrease in power levels at higher frequencies. A vertical dotted line at 1800 kHz separates the 'measurement bandwidth 30 kHz' (left) and 'measurement bandwidth 100k Hz' (right) regions.](cb74fd9f5ec715dd3e2e325b864b48bc_img.jpg) + +The graph illustrates the relative power (dB) of the GSM 900 CTS-FP spectrum due to modulation across a range of frequencies from the carrier (kHz). The y-axis represents Relative power (dB) from 0 to -80. The x-axis represents Frequency from the carrier (kHz) with markers at 0, 200, 400, 600, 1200, 1800, 3000, and 6000. A vertical dotted line at 1800 kHz divides the graph into two measurement bandwidth regions: 'measurement bandwidth 30 kHz' on the left and 'measurement bandwidth 100k Hz' on the right. The spectrum shows a sharp drop from 0 dB at 0 kHz to -60 dB at 400 kHz, then a stepped decrease in power levels at higher frequencies. + +| Frequency from the carrier (kHz) | Relative power (dB) | +|----------------------------------|---------------------| +| 0 | 0 | +| 100 | 0 | +| 200 | -30 | +| 300 | -33 | +| 400 | -60 | +| 600 | -67 | +| 1200 | -67 | +| 1800 | -67 | +| 3000 | -72 | +| 6000 | -77 | + +Graph showing Relative power (dB) vs Frequency from the carrier (kHz) for GSM 900 CTS-FP spectrum due to modulation. The graph shows a sharp drop in power from 0 dB at 0 kHz to -60 dB at 400 kHz, followed by a stepped decrease in power levels at higher frequencies. A vertical dotted line at 1800 kHz separates the 'measurement bandwidth 30 kHz' (left) and 'measurement bandwidth 100k Hz' (right) regions. + +Figure A.1: GSM 900 CTS-FP spectrum due to modulation + +![Graph of Relative power (dB) vs Frequency from the carrier (kHz) for DCS 1 800 CTS-FP spectrum. The graph shows a sharp drop from 0 dB at 0 kHz to -60 dB at 400 kHz, then a flat section until 1800 kHz, followed by two rectangular blocks representing measurement bandwidths of 30 kHz and 100 kHz.](c17eaf807acd5faec68da19dd16929be_img.jpg) + +The graph illustrates the DCS 1 800 CTS-FP spectrum due to modulation. The y-axis represents Relative power in dB, ranging from 0 to -80. The x-axis represents Frequency from the carrier in kHz, with a non-linear scale. The spectrum starts at 0 dB at 0 kHz, drops sharply to -30 dB at 200 kHz, -40 dB at 300 kHz, and -60 dB at 400 kHz. It remains at -60 dB until 1800 kHz. At 1800 kHz, there are two rectangular blocks: one from 1800 kHz to 5000 kHz at -60 dB, and another from 5000 kHz to 6000 kHz at -70 dB. A vertical dotted line at 1800 kHz is labeled 'measurement bandwidth 100kHz'. Another vertical dotted line at 400 kHz is labeled 'measurement bandwidth 30 kHz'. The x-axis has labels at 0, 200, 400, 600, 1200, 1800, and 6000 kHz. The label 'Edge of TX band + 2 MHz' is at the far right of the x-axis. There are break symbols (//) on the x-axis between 600 and 1200 kHz, and between 1800 and 6000 kHz. + +| Frequency from the carrier (kHz) | Relative power (dB) | +|----------------------------------|---------------------| +| 0 | 0 | +| 100 | 0 | +| 200 | -30 | +| 300 | -40 | +| 400 | -60 | +| 1800 | -60 | +| 5000 | -60 | +| 5000 | -70 | +| 6000 | -70 | + +Graph of Relative power (dB) vs Frequency from the carrier (kHz) for DCS 1 800 CTS-FP spectrum. The graph shows a sharp drop from 0 dB at 0 kHz to -60 dB at 400 kHz, then a flat section until 1800 kHz, followed by two rectangular blocks representing measurement bandwidths of 30 kHz and 100 kHz. + +Figure A.2: DCS 1 800 CTS-FP spectrum due to modulation + +# Annex B (normative): Transmitted power level versus time + +![Graph showing transmitted power level (dB) versus time (t) for normal duration bursts. The y-axis has markers at +4, +1, -1, -6 (**), and -30 (***). The x-axis shows time intervals of 10 μs, 8 μs, 10 μs, followed by a break labeled (147 bits) and 7056/13 (542.8) μs, then 10 μs, 8 μs, 10 μs. The power level steps up from a baseline (*) to -30 dB (***) during the first 10 μs, then to -6 dB (**) during the next 8 μs, peaks at +1 dB during the 10 μs, and then steps down back to -30 dB (***) after the break, returning to the baseline (*) at the end.](939b79420df0cf962959ccef56f3371f_img.jpg) + +Graph showing transmitted power level (dB) versus time (t) for normal duration bursts. The y-axis has markers at +4, +1, -1, -6 (\*\*), and -30 (\*\*\*). The x-axis shows time intervals of 10 μs, 8 μs, 10 μs, followed by a break labeled (147 bits) and 7056/13 (542.8) μs, then 10 μs, 8 μs, 10 μs. The power level steps up from a baseline (\*) to -30 dB (\*\*\*) during the first 10 μs, then to -6 dB (\*\*) during the next 8 μs, peaks at +1 dB during the 10 μs, and then steps down back to -30 dB (\*\*\*) after the break, returning to the baseline (\*) at the end. + +Time mask for normal duration bursts (NB, FB, dB and SB): + +- (\*) For GSM 900 CTS-FP : -59 dBc or -54 dBm, whichever is the higher. +For DCS 1 800 CTS-FP : -48 dBc or -48 dBm, whichever is the higher. +- (\*\*) For GSM 900 CTS-FP : -4 dBc for power control level 8, +: -2 dBc for power level 9, +: -1 dBc for power level controls levels 10 to 14. +For DCS 1 800 CTS-FP : -4dBc for power control level 11, +: -2dBc for power level 12, +: -1dBc for power control levels 13 and 14. +- (\*\*\*) For GSM 900 CTS-FP : -30 dBc or -27 dBm, whichever is the higher. +For DCS 1 800 CTS-FP : -30dBc or -30dBm, whichever is the higher. + +# --- Annex C (normative): Environmental conditions + +## C.1 General + +This normative annex specifies the environmental requirements of GSM 900 and DCS 1 800 CTS-FP equipment. Within these limits the requirements of the GSM specifications shall be fulfilled. + +## --- C.2 Temperature + +The CTS-FP shall fulfil all the requirements in the full temperature range of: + ++15°C - +35°C for normal conditions (with relative humidity of 25 % to 75 %); + ++10°C - +40°C for extreme conditions; + +Outside this temperature range the CTS-FP, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the CTS-FP exceed the output power levels as defined in GSM 05.56 for extreme operation. + +## --- C.3 Voltage + +The CTS-FP shall fulfil all the requirements in the full voltage range, i.e. the voltage range between the extreme voltages. + +The manufacturer shall declare the lower and higher extreme voltages and the approximate shut-down voltage. + +| Power source | Lower extreme
voltage | Higher extreme
voltage | Normal cond.
voltage | +|---------------------|----------------------------------|-----------------------------------|---------------------------------| +| AC mains | 0,9 * nominal | 1,1 * nominal | nominal | + +Outside this voltage range the CTS-FP, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the CTS-FP exceed the output power levels as defined in GSM 05.56 for extreme operation. In particular, the CTS-FP shall inhibit all RF transmissions when the power supply voltage is below the manufacturer declared shut-down voltage. + +# Annex D (informative): Change history + +| SPEC | SMG# | CR | PHASE | VERS | NEW_ | SUBJECT | +|-------|------|------|-------|-------|-------|----------------------------------------------------------------| +| 05.56 | s29 | A004 | R98 | 7.0.1 | 7.1.0 | Environmental conditions for the CTS-FP | +| 05.56 | s29 | A005 | R98 | 7.0.1 | 7.1.0 | Clarification of AFA and TFH selection performance requirement | +| 05.56 | s29 | A006 | R98 | 7.0.1 | 7.1.0 | Modification of receiver performance for CTSARCH | +| 05.56 | s31 | | | 7.1.0 | 8.0.0 | Version for Release 1999 | +| 05.56 | | | | 8.0.0 | 8.0.1 | Update to Version 8.0.1 for Publication | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2001-04 | 4 | | | | | Version for Release 4 | | 4.0.0 | +| 2002-06 | 10 | | | | | Version for Release 5 | | 5.0.0 | +| 2005-01 | 23 | | | | | Version for Release 6 | | 6.0.0 | +| 2007-08 | 35 | | | | | Version for Release 7 | | 7.0.0 | +| 2008-12 | 40 | | | | | Version for Release 8 | | 8.0.0 | +| 2009-12 | 44 | | | | | Version for Release 9 | | 9.0.0 | +| 2011-03 | 49 | | | | | Version for Release 10 | | 10.0.0 | +| 2012-09 | 55 | | | | | Version for Release 11 | | 11.0.0 | +| 2014-09 | 63 | | | | | Version for Release 12 (frozen at SP-65) | | 12.0.0 | +| 2015-12 | 68 | | | | | Version for Release 13 (frozen at SP-70) | | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Version for Release 15(frozen at TSG-80) | | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | | 16.0.0 | +| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | | 17.0.0 | +| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | | 18.0.0 | \ No newline at end of file